218 to produce Anonymized Data 232, the weather data is able to be accessed because the weather data is in the database maintained by the Server 214.

The Anonymized Data 232 is used to generate Data for Simulation 234 used to create Files 236, e.g., simulation files. The Files 236 are stored in a Database (DB) 238. Thus, users without access approval are able to access the data in the DB 238, whereas only users with access approval are able to access the Data 212 (L4 Data) on the Server 214. The Anonymized Data 232 is Anonymized Protected Data 242.

FIG. 4 is a flow chart 400 of a method for anonymizing data to create simulation files according to at least one embodiment.

In FIG. 4, the method starts S402 and data obtained from a vehicle is stored in a database of a server S410. Referring to FIG. 2, Sensitive Data with Personally Identifiable Information 210 is obtained from a vehicle and is stored as Data 212 in the Server 214, e.g., hash data. The Data 212 is able to be raw data or pre-processed data. The Data 212 in Server 214 is data acquired by sensors of vehicles while driving and has not gone through the Data Lens 216 for processing before being provided to the Server 214.

A request for data acquisition is received from a user S420. Referring to FIG. 2, a request for data acquisition to the data in the Server 214 is received from the Vehicle Data API 218. The Vehicle Data API 218 captures the Data 212 that was captured from a test vehicle through the Ego Vehicle API. The Vehicle Data API 218 thus enables users to find and use the desired Anonymized Data 232.

A vehicle identification number is removed from the data S430. Referring to FIG. 2, a vehicle identification number is removed from the data.

Referring to FIG. 3, the data obtained by Ego Vehicle API 310 and Actors Data API 340 from testing vehicles are stored in database on a server. The data stored in the server is able to be raw data or pre-processed data. However, the data in a database on the server includes sensitive data, i.e., PII (Personally Identifiable Information), such as timestamp information. PII is any information about an individual including any information that is able to be used to distinguish or trace an individual's identity, and any other information that is linked or linkable to an individual. Therefore, sensitive data in the database on the server is only accessible by users that have special authorization, and files are not able to be created based on the data that includes PII.

At least one specific parameter included in the at least one subset of the data is changed to create anonymized data S440. Referring to FIG. 2, the Vehicle Data API 218 captures the Data 212 that was captured from a test vehicle through the Ego Vehicle API. The Vehicle Data API 218 thus enables users to find and use the desired Anonymized Data 232. A vehicle identification number is removed from the data. Data 212 is anonymized by changing at least one specific parameter in the Data 212 in the Server 214 to create Anonymized Data 232. Highly Confidential Data 220 is changed to Anonymized Data 232 to reduce access constraints for a user. The changing of the at least one specific parameter included in the subset of the Data 212 includes changing the timestamp value of an initial frame from frames in the data to make the timestamp value of the initial frame (e.g., first event) in the subset of the Data 212 to be at time zero with subsequent frames in the at least one subset of data having a relative offset from the initial frame. Thus, the authorization for the users is able to be reduced as the users do not have access to sensitive data. The Anonymized Data 232 is created with remaining GPS coordinates to provide information about the vehicle passing through a specific time and place. The Anonymized Data 232 is created with kinematic and positional data of the vehicle. The Anonymized Data 232 is created with kinematic and positional data of the vehicle that includes velocity data, acceleration data, latitude data, longitude data, orientation data, and a relative time offset. The Vehicle Data API 218 provides access to the kinematic and positional data of the vehicle. The Anonymized Data 232 that is created is also able to include one or more of weather data or terrain data. The Anonymized Data 232 that is created includes geographic context information. Other factors involved in the simulations include weather. Another factor is the particular terrain, which is able to have an impact on the overall shape of the trajectory. Thus, instead of removing time stamps, the GPS position could be altered. However, this is more complicated than providing anonymization by removing the timestamp information. The goal of a simulation is to analyze how the vehicle responded to some specific situation. To join geographic context information, like weather, the absolute GPS is used. When dealing with absolute GPS coordinates, data from outside of what the vehicle itself senses, e.g., rain data, is able to be included. When data is anonymized by the Vehicle Data API 218 to produce Anonymized Data 232, the weather data is able to be accessed because the weather data is in the database maintained by the Server 214.

User access is provided to the at least one anonymized subset of the data S450. Referring to FIG. 2, to be able to use the Anonymized Data 232, Data without Personally Identifiable Information (PII) is provided the Users Without Access Approval 240. Thus, Users Without Access Approval 240 are able to submit a request for data acquisition to the Data 212 in the database in the Server 214.

Files are created for a simulation using the at least one anonymized subset of the data S460. Referring to FIG. 2, the Anonymized Data 232 is used to generate simulation data used to create Data for Simulation 234 for Files 236, e.g., simulation files. The Files 236 are stored in a Database (DB) 238. Based on the anonymized data, the simulation teamwork uses the Files 236 to create a specification that describes what happened with the vehicle, e.g., replicate exactly what the vehicle did in real life.

The process then terminates S470.

At least one embodiment of the method for anonymizing data in a database on a server includes storing data obtained from a vehicle in a database of a server, removing a vehicle identification number from the data in the database, and changing at least one specific parameter included in data in the database to create anonymized data.

FIG. 5 is a high-level functional block diagram of a processor-based system 500 according to at least one embodiment.

In at least one embodiment, processing circuitry 500 for anonymizing data to create simulation files for creating vehicle test simulations. Processing circuitry 500 implements anonymizing data to create simulation files using Processor 502