Method and system for managing vehicle generated data
A system for collecting and managing vehicle-generated data from multiple vehicles are provided. The vehicle-generated data is pseudonymized by pseudonymized identifiers, and the pseudonymized vehicle-generated data is collected and managed by a neutral data server operated by an operator who is independent of vehicle manufacturers. Vehicle manufacturers can reestablish the link of the pseudonymized event data with the vehicle that had generated the event data and the vehicle driver.
1. A method of operating a vehicle to process vehicle-generated data, comprising:
applying, by a controller of a vehicle, a hash function to a combination of a first salt and a personally identifiable information that uniquely identifies a driver to generate a driver pseudonymized identifier,
applying, by the controller, the hash function to a combination of a second salt and a vehicle identification information that uniquely identifies the vehicle to generate a vehicle pseudonymized identifier;
transmitting, by the controller, a salt generation information for a reconstruction of the first salt and the second salt to a vehicle manufacturer server having the personally identifiable information and the vehicle identification information; and
transmitting, by the controller, pseudonymized vehicle-generated data identified by the driver pseudonymized identifier and the vehicle pseudonymized identifier to a data server different from the vehicle manufacturer server.
2. The method of claim 1 , wherein
the first salt and the second salt are generated using at least one seed selected from an indexed list of seeds shared by the vehicle manufacturer server and the vehicle, and
the salt generation information contains an index of the at least one seed used to generate the first salt and the second salt.
3. The method of claim 1 , wherein the transmitting of the salt generation information includes:
transmitting, by the controller, to the vehicle manufacturer server, sequence numbers indicating a number of times the driver pseudonymized identifier is generated and a number of times the vehicle pseudonymized identifier is generated.
4. The method of claim 1 , wherein the driver pseudonymized identifier and the vehicle pseudonymized identifier are generated in response to the driver logging in to the vehicle and succeeding in a driver authentication.
5. The method of claim 1 , wherein the driver pseudonymized identifier and the vehicle pseudonymized identifier are discarded when a vehicle operation by the driver is terminated.
6. The method of claim 1 , wherein the personally identifiable information includes:
an identification of the driver including at least one of a resident registration number or social security number, a driver's license number, a mobile phone number, or biometric data, or a unique identifier assigned to a fob key possessed by the driver in connection with the vehicle, or a user ID of the driver, which is assigned from the vehicle manufacturer server.
7. The method of claim 1 , wherein the vehicle identification information includes:
a vehicle identification number (VIN), a vehicle registration number, or a unique identifier used by an in-vehicle telecommunication device of the vehicle to communicate with an external network.
8. The method of claim 1 , wherein the vehicle-generated data includes:
data recorded by an event data recorder (EDR) mounted on the vehicle.
9. The method of claim 1 , wherein the vehicle-generated data includes:
autonomous driving data recorded by a data storage system mounted on the vehicle.
10. A method performed by a vehicle manufacturer server for obtaining vehicle-generated data associated with a specific driver or a specific vehicle from a data server storing pseudonymized vehicle-generated data collected from a plurality of vehicles, the pseudonymized vehicle-generated data in the data server being identified by a vehicle pseudonym identifier and a driver pseudonym identifier which are generated in an associated vehicle, the method comprising:
generating, by a controller, at least one of a first salt or a second salt using a salt generation information received from the specific vehicle;
reconstructing, by the controller, at least one of a driver pseudonymized identifier for the specific driver or a vehicle pseudonymized identifier the for the specific vehicle, wherein the driver pseudonymized identifier is reconstructed by applying a hash function to a combination of the first salt and a personally identifiable information uniquely identifying the specific driver is reconstructed, and the vehicle pseudonymized identifier is reconstructed by applying the hash function to a combination of the second salt and a vehicle identification information uniquely identifying the specific vehicle;
requesting, by the controller, the data server to provide pseudonymized vehicle-generated data corresponding to at least one of the reconstructed driver pseudonymized identifier or the reconstructed vehicle pseudonymized identifier; and
receiving, by the controller, the pseudonymized vehicle-generated data corresponding to the at least one of the reconstructed driver pseudonymized identifier or the reconstructed vehicle pseudonymized identifier from the data server.
11. The method of claim 10 , wherein the salt generation information contains an index of a pair of seeds, the index identifying the pair of seeds in an indexed list of seeds shared between the vehicle manufacturer server and the specific vehicle, and the first salt and the second salt are bitstrings randomly generated by using the pair of seeds.
12. The method of claim 10 , wherein the vehicle-generated data includes:
data recorded by an event data recorder (EDR) mounted on the specific vehicle.
13. The method of claim 10 , wherein the vehicle-generated data includes:
autonomous driving data recorded by a data storage system mounted on the specific vehicle.