Method and system for collecting and managing vehicle-generated data

By adding salt value processing and separate database storage of the data generated by the vehicle in the cloud system, the integrity and privacy protection issues in the vehicle data storage are solved, centralized management and analysis of vehicle data is realized, and the law and privacy are met. Protection needs.

CN115210783BActive Publication Date: 2024-11-29HYUNDAI MOTOR CO LTD +1
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202180018851.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-02-26
Publication Date
2024-11-29
Estimated Expiration
2041-02-26

AI Technical Summary

Technical Problem

In the prior art, data generated by vehicles has data integrity problems during storage and management, especially in evidence collection investigations, data is easily damaged or tampered, and personal privacy protection is difficult to guarantee, especially when using ADAS or autonomous driving. When functional, data sensitivity increases the need for privacy protection.

Method used

By designing a method in the cloud system, receiving event report messages and interactive report messages from vehicles, using salt value to generate link data, and storing vehicle identification information, event data and interaction data in different databases respectively to ensure the data to decorate and delete data and manage permissions according to the settings of the car owner to ensure the security and privacy of the data.

Benefits of technology

Realize centralized management of vehicle-generated data in cloud storage systems, ensuring that the data recorder is not limited by storage space, and can collect and analyze vehicle data more comprehensively, ensure data integrity and privacy, and meet the data within legal boundaries. Utilize requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115210783B_ABST
    Figure CN115210783B_ABST
Patent Text Reader

Abstract

A centralized cloud storage system for collecting and managing vehicle-generated data from multiple vehicles is disclosed. In the proposed system, EDR / DSSAD data recorded in each vehicle is separated from the vehicle identification information (VII) that enables third parties to identify or track the associated vehicle and is stored and managed in a database on the network together with linking data. The linking data can be cryptographically generated and reconstructed based on the VII and a salt value. Therefore, the association between the VII and the EDR / DSSAD data can be disassociated by deleting the salt value from the database.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to collecting and managing data generated by multiple vehicles. Background Art

[0002] The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.

[0003] An event data recorder (EDR) is configured to detect an accident, etc. and store information related to the driving state of the vehicle or the driver's operation within a predetermined time before and after the accident. Several parameters including speed, seat belt status, and airbag deployment status are stored for reconstruction during forensic investigation.

[0004] Forensic investigations are usually performed using a vehicle diagnostic link connector (e.g., an onboard computer (OBD)-II port) or by physically extracting the EDR data storage and reading data from it. Data in the EDR is easily corrupted or altered by faulty reading techniques and can be maliciously tampered with or deleted after storage, making it difficult to fully guarantee the data integrity of the stored data.

[0005] As the application of ADAS (Advanced Driver Assistance Systems) or autonomous driving functions expands, additional information indicating the operating status of the ADAS or autonomous driving functions, the vehicle system's judgment of sensor inputs, etc., in addition to the EDR data recorded in the past by the event data recorder (EDR), may help to identify the causes of these accidents.

[0006] With the development of information and communication technology, such vehicle-generated data can be collected in various forms by data servers on the Internet and provided to various service providers. Some of the information collected by the data servers may be sensitive in terms of personal privacy. Since operators have actual control and sales rights over the personal information in these data servers, individuals have to bear great risks.

[0007] Furthermore, with the implementation of privacy protection regulations such as the European General Data Protection Regulation (GDPR), there is a need to introduce systems that can effectively collect and utilize vehicle-generated data within legal boundaries. Summary of the invention

[0008]

Technical issues

[0009] The present disclosure shows the general concept of a data storage system for a vehicle with communication capabilities and a cloud storage system for collecting and managing vehicle-generated data. The concept focuses on overcoming the limitations of onboard data storage and maximizing user access to vehicle-generated data. In particular, the present disclosure shows a data storage and management method that can protect personal privacy in a cloud system.

[0010]

Technical solution

[0011] According to one aspect of the present disclosure, a method for collecting and managing vehicle-generated data from a vehicle is performed by at least one server on a network, the method comprising the steps of receiving an event report message and an interaction report message from the vehicle. The event report message comprises vehicle identification information and event data stored by an event data recorder of the vehicle, and the interaction report message comprises vehicle identification information and interaction data indicating an interaction between an autonomous driving system of the vehicle and a driver. The method further comprises the steps of: generating link data based on the vehicle identification information and a salt value; storing the vehicle identification information and the salt value in a first database; storing the event data and the link data in a second database, and storing the interaction data and the link data in a third database.

[0012] Embodiments of the method may include one or more of the following features.

[0013] In some embodiments, the method further comprises the following steps: when it is necessary to remove the association between the vehicle identification information and the event data and the association between the vehicle identification information and the interaction data, deleting the vehicle identification information or the salt value from the first database.

[0014] In some embodiments, the method further comprises the steps of: in response to expiration of a validity period set by an owner of the vehicle, maintaining the event data and interaction data in the second database and the third database, and deleting the vehicle identification information or salted value of the vehicle from the first database.

[0015] In some embodiments, the method further includes the following steps: receiving a request message from the owner of the vehicle, the request message requesting deletion of at least one of the vehicle identification information, event data and interaction data; in response to receiving the request message, deleting at least one of the vehicle identification information, link data, event data and interaction data from the relevant database.

[0016] In some embodiments, the method further comprises the following steps: when the vehicle identification information or the salt value is deleted from the first database, the security level of the permission to use the relevant event data and interaction data stored in the second database and the third database is reduced.

[0017] In some embodiments, event data or interaction data whose security level has not been reduced can be searched from the second database or the third database based on the link data reconstructed according to the relevant vehicle identification information and the salt value stored in the first database, and event data or interaction data whose security level has been reduced can be searched directly from the second database or the third database without the reconstructed link data.

[0018] In some embodiments, the linking data is generated by applying a one-way hash function to the vehicle identification information and the salt value.

[0019] In some embodiments, the vehicle identification information is a vehicle identification number (VIN), and the linking data is a de-identified version of the VIN generated from the salt value and the VIN. The de-identified version of the VIN is generated by applying a one-way hash function to a concatenation of some bits of the salt value and the VIN of the vehicle to generate a hash value, and replacing some bits of the VIN with the hash value.

[0020] According to one aspect of the present disclosure, there is provided a cloud storage system for collecting and managing vehicle-generated data from a vehicle and implemented by at least one server on a network, the system comprising a device for receiving event report messages and interaction report messages from a vehicle. The event report message comprises vehicle identification information and event data stored by an event data recorder of the vehicle, and the interaction report message comprises vehicle identification information and interaction data indicating the interaction between the vehicle's autonomous driving system and the driver. The system further comprises: a device for generating link data based on the vehicle identification information and a salt value; a device for storing the vehicle identification information and the salt value in a first database; a device for storing the event data and the link data in a second database and storing the interaction data and the link data in a third database.

[0021]

Beneficial Effects

[0022] A centralized system for collecting and managing EDR / DSSAD data from vehicles can free the vehicle's data recorder from storage space constraints. For example, the event data recorder can be designed to use more trigger conditions than traditional methods to collect EDR data related to minor accidents that were previously ignored, and can be designed to collect a wider range of data elements that can further facilitate post-event analysis of the event (e.g., radar / lidar data obtained before and after the event, V2X messages, etc.).

[0023] Individuals or organizations can easily obtain EDR / DSSAD data of interest from a centralized system in a timely manner. In addition, EDR / DSSAD data stored in a storage location on a trusted network may be helpful for forensic investigations that require ensuring data integrity. EDR data and DSSAD data are complementary, and in particular, DSSAD data helps identify the subject who was in control of the vehicle at the time of a collision.

[0024] In the proposed centralized system, the EDR / DSSAD data recorded in each vehicle is separated from the vehicle identification information (VII) that enables a third party to identify or track the relevant vehicle, and is stored and managed in a database on the network together with the linking data. The linking data can be (re)generated cryptographically based on the vehicle identification information and the salt value stored in the VII database. Therefore, by deleting the vehicle identification information or the salt value from the VII database, the association between the vehicle identification information and the relevant EDR / DSSAD data can be removed. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 is a schematic diagram illustrating a centralized system for collecting and managing event data from vehicles according to an embodiment of the present disclosure.

[0026] Figure 2 is a conceptual diagram illustrating an exemplary method for separately storing vehicle identification information (VII), EDR data, and DSSAD data in a database according to an embodiment of the present disclosure.

[0027] Figure 3 is a diagram for explaining detailed information of a vehicle identification number (VIN).

[0028] Figure 4 An example of a de-identified version of a VIN and an EDR identified thereby is shown according to an embodiment of the present disclosure.

[0029] Figure 5 is a conceptual diagram illustrating an exemplary method for querying EDR / DSSAD data of a specific vehicle through a cloud storage system and providing the data according to an embodiment of the present disclosure.

[0030] Figure 6 is a conceptual diagram illustrating an exemplary method in which a cloud storage system deletes VII / EDR / DSSAD data according to a request of a vehicle owner according to an embodiment of the present disclosure.

[0031] Figure 7 The present invention is a diagram showing an embodiment of the present invention. Figure 1 Flowchart of the EDR data collection process of the system shown. DETAILED DESCRIPTION

[0032] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. When the components of the various figures are labeled, the same reference numerals represent the same components, although the components are shown in different figures. Further, in the following description of some embodiments, when it is determined that the specific description of the relevant known structure or function will confuse the subject matter of the present invention, the detailed description thereof will be omitted.

[0033] Figure 1is a schematic diagram illustrating a centralized system for collecting and managing vehicle-generated data from vehicles according to an embodiment of the present disclosure.

[0034] The system 100 includes an onboard data recording system 10 provided in a vehicle and a cloud storage system 20 implemented as a server on a network. The server implementing the cloud storage system 20 may be a server operated by a vehicle manufacturer or a server operated by an operator independent of the vehicle manufacturer, or may include a combination thereof.

[0035] The vehicle is configured to operate in full or partial autonomous driving mode and may therefore be referred to as an “autonomous driving vehicle.” For example, the autonomous driving system 14 may receive information from the sensor system 13 and, based on the received information, execute one or more control processes in an autonomous manner (e.g., setting a steering position to avoid a detected obstacle).

[0036] The vehicle may be fully autonomous or partially autonomous. In a partially autonomous vehicle, some functions may be temporarily or continuously manually controlled by the driver. Further, a partially autonomous vehicle may be configured to switch between a fully manual operating mode, a partially autonomous operating mode, and / or a fully autonomous operating mode.

[0037] The vehicle data recording system 10 can be configured to generate, record or store various types of data related to vehicle operation or driver behavior. The vehicle data recording system 10 includes two types of data recorders: an event data recorder (EDR) 11 and a self-driving vehicle data storage system (DSSAD) 12. They record vehicle-generated data for different purposes.

[0038] The purpose of the EDR 11 is to store vehicle information for specific events such as airbag deployment. Data from the EDR 11 is used for crash analysis and reconstruction. The purpose of the DSSAD 12 is to record all predefined interactions between the driver and the automated driving system. Data from the DSSAD 12, which is usually stored in a timestamp format, is used to identify the subject in control of the vehicle at a specific point in time. The data from the EDR 11 and the data from the DSSAD 12 are used complementary in forensic investigations, in particular, the data from the DSSAD 12 helps to identify the subject in control of the vehicle at the time of the crash.

[0039] The EDR 11 may be configured to receive data from various sensors and / or electronic control units (ECUs) mounted on the vehicle. In the volatile memory of the EDR 11, data is temporarily stored for a certain period of time while being continuously updated. When the EDR 11 detects the occurrence of one or more predefined events, the data recorded in the volatile memory within a predetermined time before and after the detection of the predefined event is stored in an internal non-volatile memory. Specifically, such an event may be a traffic collision. For example, a traffic collision may be detected when an irreversible deployment of a safety device such as an airbag or a seat belt preload device is triggered. A traffic collision may also be detected when an acceleration / deceleration exceeds a predetermined threshold (e.g., a speed change of 8 km / h or more within approximately 150 milliseconds). Predefined events may further include failures of major functions of the vehicle.

[0040] The EDR 11 may be configured to receive a trigger signal notifying the occurrence of an event from an electronic control unit such as an airbag control unit ACU. The EDR 11 may access a value measured by at least one sensor included in the sensor system 13. The at least one sensor may be configured to detect vehicle speed / acceleration / deceleration / travel distance / geographic location, etc. The EDR 11 may be included in the airbag control unit (ACU) as a module.

[0041] The data recorded and stored by the EDR 11 may be data suitable for analyzing traffic collisions, such as data on vehicle dynamics, driver behavior, and the operating status of vehicle safety systems. The EDR 11 may be configured to transmit the stored data (hereinafter referred to as "EDR data" or "event data") to the telecommunications device 15 for transmission to the cloud storage system 20.

[0042] The autonomous driving system 14 may be configured to generate interaction signals indicating the interaction between the driver and the autonomous driving system 14. These interaction signals may include signals indicating whether one or more autonomous driving functions are currently in an activated state. For example, the autonomous driving system 14 may generate a signal indicating whether the adaptive cruise control (ACC) function is currently in an activated state. As another example, the autonomous driving system 14 may generate a signal indicating whether the driving of the vehicle is currently fully automatically controlled rather than manually controlled. In addition, these interaction signals may further include a signal indicating a need to convert control to indicate to the driver the need to take over the driving task, and a signal indicating that the driver has taken over the control of the driving task. The autonomous driving system 14 may provide interaction signals to the DSSAD 12 via a data bus (e.g., a CAN bus, an Ethernet bus, etc.).

[0043] The DSSAD 12 can store interaction data representing the interaction between the driver and the automatic driving system in an internal non-volatile memory based on the interaction signal received from the automatic driving system 14. The DSSAD 12 is installed on a vehicle equipped with a highly automated driving system (e.g., SAE Level 3, 4, 5), and is a data storage system intended to clarify the "subject requesting driving" and the "subject actually driving". During the transition process (i.e., after the transition request is issued and until the driver actually takes over the control), the "subject requesting driving" and the "subject actually driving" may be different from each other.

[0044] The interaction data may include time-stamped data elements representing specific interaction events such as, for example, changing the state of the automated driving system (off, activated, transition request, override), the automated driving system initiating and ending a minimum risk maneuver (MRM), and the driver taking over control of the driving task. The DSSAD 12 may provide the stored interaction data (hereinafter also referred to as "DSSAD data") to the telecommunication device 15 for transmission to the cloud storage system 20.

[0045] DSSAD data can have three fields, including a timestamp, a type flag, and a cause field. The timestamp field indicates the time when a specific interaction between the driver and the system occurred. To this end, DSSAD data requires a high-precision timestamp. The type flag field indicates the type of interaction between the driver and the system, such as a conversion requirement or a minimum risk maneuver. The cause field indicates the reason for the interaction. The cause field can be an optional field.

[0046] The telecommunication device 15 may be a wired or wireless telecommunication device that connects the internal network of the vehicle to an external communication network. The telecommunication device 15 may be, for example, a telematics unit (TMU) or a wired / wireless dongle plugged into an OBD-II port. For example, the telecommunication device 15 may include a wireless transceiver capable of cellular communications such as GSM / WCDMA / LTE / 5G or short-range wireless communications such as WLAN, c-V2X, WAVE, DSRC, Bluetooth, etc.

[0047] The telecommunications device 15 may be configured to generate an event report message upon receiving EDR data from the EDR 11. The telecommunications device 15 may be configured to transmit the event report message to the cloud storage system 20 via a communication network. The event report message may include vehicle identification information (VII) and the EDR data received from the EDR 11. In a typical embodiment, VII may be a vehicle identification number (VIN), which is a 17-digit unique identifier consisting of numbers and letters assigned to each vehicle by the vehicle manufacturer. Alternatively, VII may be a vehicle registration number (or license plate information), a unique identifier used by the telecommunications device 15 for communication, a (long-term or short-term) certificate assigned to the vehicle for V2X communication, and the like. The event report message may further include additional information such as the geographic location, date, and time of the event.

[0048] The telecommunication device 15 may generate an interactive report message upon receiving the DSSAD data from the DSSAD 12. The telecommunication device 15 may transmit the interactive report message to the cloud storage system 20 via the communication network. The interactive report message may include the vehicle identification information (VII) and the DSSAD data received from the DSSAD 12.

[0049] The cloud storage system 20 is a data management system implemented using a server on a network, which collects and manages EDR data and DSSAD data from a plurality of vehicles.

[0050] The cloud storage system 20 can receive event report messages and interaction report messages from multiple vehicles. For the report messages received from the vehicles, the cloud storage system 20 separates the VII and EDR / DSSAD data that can be used by a third party to identify or track the relevant vehicle or relevant individual, so that the VII and EDR / DSSAD data can be stored in different databases.

[0051] In response to a request from a user 30 who wants to use the EDR / DSSAD data, the cloud storage system 20 can provide anonymous EDR / DSSAD data that cannot identify a specific vehicle or individual, or provide EDR / DSSAD data that can identify a specific vehicle or individual. The user 30 may be a vehicle owner, driver, insurance company, government agency, researcher, or vehicle manufacturer who wants to utilize the EDR / DSSAD data. Unless otherwise authorized by a court order, search warrant, and / or other applicable laws and regulations, the cloud storage system 20 only needs to provide EDR / DSSAD data that identifies a specific vehicle or individual to investigators or other users authorized by the relevant vehicle owner.

[0052] The cloud storage system 20 may be implemented to include a service manager 21, a rule / policy manager 23, a repository coordinator 25, a cloud interface 27, and a data repository 29. The data repository 29 may be implemented by at least one data server.

[0053] The service manager 21 is a functional entity that collects EDR / DSSAD data from vehicles, manages the EDR / DSSAD data, and provides users with anonymous EDR / DSSAD data that cannot identify a specific vehicle or individual, or EDR / DSSAD data that identifies a specific vehicle or individual. The rule / policy manager 23 is a functional entity for managing user profiles and privacy policies stored in the data repository 29. The repository coordinator 25 is a functional entity for storing EDR data, DSSAD data, and VII data separately in the database of the data repository 29 and searching for EDR data, DSSAD data, and VII data from the database of the data repository 29. The cloud interface 27 is a functional entity that serves as a gateway for the cloud storage system 20.

[0054] The data repository 29 has a database that records user profiles, privacy policies, VII data, EDR data, and DSSAD data. The user profile includes the joining information of individuals, companies, or organizations that have joined the cloud storage system 20. The privacy policy includes a set of privacy rules that are applied to the collection and management procedures of EDR / DSSAD data for each vehicle.

[0055] The rule / policy manager 23 can be configured to receive privacy option settings for personal data (VII / EDR / DSSAD data) collected from the vehicle owner from the vehicle owner, and generate a set of privacy rules (i.e., privacy policies) based on the received privacy option settings to be applied to the collection, management and use of personal data.

[0056] Reference Figure 2 , describes an exemplary method in which the cloud storage system 20 stores VII, EDR data, and DSSAD data included in a report message received from a vehicle separately in a database.

[0057] The cloud interface 27 can receive an event report message or an interactive report message from the vehicle through a secure channel. Each report message may include EDR data and VII, or may include DSSAD data and VII.

[0058] The repository coordinator 25 may generate link data for maintaining the association between the EDR / DSSAD data stored in the different databases and the VII. The link data may be generated based at least in part on the VII and a randomly generated value (hereinafter referred to as a "salt"). However, the link data itself does not include any meaningful information that identifies a vehicle or an individual.

[0059] The repository coordinator 25 may divide the information included in each report message into two data sets. The first data set includes the EDR / DSSAD data but does not include the VII, and the second data set includes the VII but does not include the EDR / DSSAD data. In other words, the vehicle identification number (VIN) or any other unique data that can identify or track the associated vehicle or individual is separate from the EDR / DSSAD data.

[0060] The repository coordinator 25 may store the first data set (ie, the link data and the EDR / DSSAD data) with the link data added in the EDR / DSSAD database. The repository coordinator 25 may store the second data set (ie, the salt value and the VII) with the salt value added in the VII database.

[0061] The link data may be a pseudo-identifier generated at least in part based on the VII. In some embodiments, the pseudo-identifier may be generated by applying a one-way hash function to the VII. The one-way hash function makes it impossible to extract the VII or other useful information from the pseudo-identifier. Preferably, the pseudo-identifier may be generated by applying a one-way hash function to the concatenation of the VII and a salt value. The salt value used to generate the pseudo-identifier may be stored in the VII database together with the associated VII. In this article, a one-way hash function has been described as an example, but other types of cryptographic algorithms for generating pseudo-identifiers may be used.

[0062] In some embodiments, the linking data may be a de-identified version of a vehicle identification number (VIN). As described above, a VIN may be a 17-digit unique identifier consisting of numbers and letters assigned to each vehicle by the vehicle manufacturer. The de-identified version of the VIN may be generated by cryptographically de-identifying at least some of the digits in the original VIN including the production serial number.

[0063] As described below, each bit of the VIN has a specific purpose.

[0064] Figure 3 is a diagram for explaining detailed information of a vehicle identification number (VIN).

[0065] The first three digits of the VIN, known as the World Manufacturer Identifier (WMI) or WMI code, provide information about the vehicle's manufacturer and geographic location of manufacture.

[0066] The first digit of the VIN indicates the country where the vehicle was manufactured. This digit can be a letter or a number. For example, a "1," "4," or "5" in the first digit indicates that the country of origin is the United States. "2" indicates Canada, "3" indicates Mexico, "6" indicates Australia, "A" indicates South Africa, "J" indicates Japan, "L" indicates China, and "K" indicates South Korea.

[0067] The second digit of the VIN indicates the vehicle manufacturer, but should be paired with the first digit (indicating the country of manufacture) to accurately decode the manufacturer. For example, a VIN beginning with "1C" indicates a vehicle manufactured by Chrysler in the United States, and a VIN beginning with "AC" indicates a vehicle manufactured by Hyundai in South Africa.

[0068] The third digit indicates the vehicle type or manufacturing division. In a VIN beginning with "WV1", the "W" indicates that the country of manufacture is Germany, and the "V" indicates that the manufacturer is Volkswagen. "1" indicates a commercial vehicle of Volkswagen. A VIN for a Volkswagen passenger car or van begins with "WV2", and a VIN for a Volkswagen truck begins with "WV3".

[0069] Bits 4 through 8 of the VIN make up the Vehicle Descriptor Section (VDS) and represent vehicle characteristics such as body style, engine type, model, and series. Each manufacturer uses these five-bit fields in its own way.

[0070] The ninth digit is a checksum value used to identify invalid VINs. This value is determined based on a mathematical formula using the values ​​from the first and last eight digits.

[0071] Digits 10 through 17 of the VIN are called the Vehicle Identifier Section (VIS). They provide a more detailed description of the specific vehicle.

[0072] The tenth digit indicates the model year of the vehicle. Letters from B to Y correspond to models between 1981 and 2000. The VIN does not use I, O, Q, U, or Z. Between 2001 and 2009, numbers 1 to 9 are used instead of letters. The English alphabet starting with A is used for 2010 to 2030. Models from 2000 or later are as follows: Y = 2000, 1 = 2001, 2 = 2002, 3 = 2003, ..., 9 = 2009, A = 2010, B = 2011, C = 2012, ..., K = 2019, and L = 2020.

[0073] The 11th digit indicates the factory where the car was assembled. Each VM has its own factory code. The last six digits (from the 12th to the 17th) indicate the production serial number of the vehicle.

[0074] The repository coordinator 25 parses the VIN to extract the serial number and applies a one-way hash function to the concatenation of the salt value and the serial number to generate a hash value. The repository coordinator 25 may generate a de-identified version of the VIN by replacing the serial number of the VIN with the generated hash value. In other words, the de-identified version of the VIN may have a hidden production serial number.

[0075] Figure 4 An example of a de-identified version of a VIN is shown. In the de-identified version of the VIN, the bits other than the production serial number are plain text, so that meaningful statistical analysis can be performed on EDR data collected from multiple vehicles. For example, EDR data generated by vehicles with a "2018 Avante model manufactured in North America" ​​can be analyzed.

[0076] In the case of models produced in very small quantities, information such as the model, series, and model year of the vehicle may enable tracking of the vehicle or the associated owner. Therefore, in the case of such models, a process similar to the anti-identification process performed on the production serial number may be further performed on at least some of the 10th to 17th digits of the VIN as the VIS and the 4th to 8th digits of the VIN as the VDS.

[0077] The linked data (particularly the pseudo-identifier) ​​itself does not include any meaningful information that identifies a vehicle or individual, but the linked data can be cryptographically reconstructed based on the vehicle identification information (VII) stored in the VII database and a salt value. Therefore, the relationship between the VII and the EDR / DSSAD data can be traced from the VII database to the EDR / DSSAD database, but not the other way around. It should be noted that in some embodiments, the operator of the EDR / DSSAD database can be a service provider independent of the operators of the other functional elements of the cloud storage system 20 including the VII database. In such an embodiment, as long as the VII database is securely managed, such an independent service provider can use or distribute the EDR / DSSAD data with little risk to the privacy of the vehicle owner.

[0078] Further, by deleting the vehicle identification information or salt value used to reconstruct the link data from the VII database, the association between the vehicle identification information and the related EDR / DSSAD data can be released. When it is necessary to release the association between the vehicle identification information and the EDR / DSSAD data, the repository coordinator 25 maintains the EDR / DSSAD data in the related database, but deletes the vehicle identification information or salt value from the VII database. This may be useful when the operating entities of the VII database and the EDR / DSSAD database are different from each other.

[0079] Reference Figure 5, describes an exemplary method by which the cloud storage system 20 queries and provides EDR / DSSAD data for a particular vehicle.

[0080] When a data request message requesting EDR / DSSAD data for a specific vehicle is received through a secure channel, the cloud interface 27 can authenticate whether the requester is the owner of the vehicle as the data subject or a third party with legal authority. The data request message may include authentication information and the VII of the specific vehicle. When the authentication is successful, the repository coordinator 25 can obtain the salt value stored with the vehicle's VII by querying the VII database. The repository coordinator 25 can reconstruct the link data based on the VII and the salt value. The repository coordinator 25 can use the link data to search for EDR data and DSSAD data from the EDR database and the DSSAD database, respectively. The repository coordinator can record logs of data requests and subsequent query tasks, and reply the EDR data and DSSAD data to the requester.

[0081] Most privacy-related regulations (such as GDPR) ensure that data subjects have the right to control the use, management, and disposal of data. To this end, the cloud storage system 20 can establish a privacy policy including a set of privacy rules that will be applied in the process of collecting EDR / DSSAD data from each vehicle and managing EDR / DSSAD data.

[0082] The rule / policy manager 23 may operate a web server that provides a graphical user interface through which the vehicle owner may select one or more privacy options to apply to the EDR / DSSAD data. The rule / policy manager 23 of the cloud storage system 20 may receive from the vehicle owner a selection of privacy options for the vehicle's EDR / DSSAD data. The privacy options may be selected when the vehicle owner joins the cloud storage system 20 or registers his / her vehicle, or at some point after registration. The following are exemplary privacy options that may be selected.

[0083] - Opt-out: An option for a vehicle owner to specify that one or more data elements should not be collected from the vehicle owner

[0084] -- Opt-in: An option for a vehicle owner to specify one or more data elements that are permitted to be collected from the vehicle owner

[0085] - Limit Use: Option for vehicle owners to limit permitted uses of data collected from their vehicle

[0086] De-identification: An option for car owners to allow data to be collected from their vehicle, but to remove any association with the vehicle or individual before allowing third parties to use the data

[0087] The rule / policy manager 23 can generate a set of privacy rules applicable to the EDR / DSSAD data of the vehicle according to the selection (or private option) made by the vehicle owner, and store the generated set of privacy rules in a privacy policy related database. The set of privacy rules can be defined in a markup language such as Extensible Markup Language (XML).

[0088] Even after joining the cloud storage system 20, the car owner has the right to request the cloud storage system to delete personal data (VII / EDR / DSSAD data), and in response to the request, the cloud storage system 20 is obliged to delete the personal data without undue delay.

[0089] Reference Figure 6 , describes an exemplary method in which the cloud storage system 20 deletes VII / EDR / DSSAD data at the request of a vehicle owner.

[0090] When a deletion request message requesting the deletion of vehicle-generated data is received through a secure channel, the cloud interface 27 can authenticate that the requesting party is the owner of the vehicle as the data subject. The deletion request message may include the VII of the vehicle related to the authentication information. When the authentication is successful, the repository coordinator 25 can obtain the salt value stored together with the VII of the vehicle by querying the VII database. The repository coordinator 25 can rebuild the link data based on the VII and the salt value. The repository coordinator 25 can use the link data to search for EDR data and DSSAD data from the EDR database and the DSSAD database respectively, and delete the EDR / DSSAD data corresponding to the link data. The repository coordinator can record the log of the deletion request and the corresponding deletion task, and respond to the requesting party with the operation results.

[0091] The deletion request from the car owner may further include selecting data to be deleted from the VII and EDR / DSSAD data. According to the car owner's selection, the cloud storage system 20 may selectively delete the VII and EDR / DSSAD data from the database.

[0092] The car owner can request to delete only the VII or the linked data to allow a third party to use EDR / DSSAD data that is not related to the vehicle or individual. When only the VII or the linked data is deleted, the cloud storage system 20 can reduce the security level of the privacy rules (e.g., usage rights or access rights) of the relevant EDR / DSSAD data. For example, the cloud storage system 20 can retain the EDR / DSSAD data with the VII deleted, use it for research purposes, or provide it to a third party without being restricted by the purpose or time period of use set by the car owner. Therefore, it is possible to allow event data or interaction data with a reduced security level to be searched directly from the second database or the third database without reconstructing the linked data.

[0093] In some embodiments, when the valid period set by the car owner expires, the cloud storage system 20 can retain the relevant EDR / DSSAD data in the EDR / DSSAD database, but can delete the relevant VII or salt value from the VII database. Therefore, even after the valid period set by the car owner expires, the EDR / DSSAD data can be used for statistical analysis unrelated to the VII data. Even in this case, when an explicit deletion request is received from the car owner, the cloud storage system 20 needs to delete the EDR / DSSAD data. In some other embodiments, when the usage period set by the car owner expires, the cloud storage system can selectively delete only the EDR / DSSAD data whose usage period has expired, while retaining the relevant VII data.

[0094] In the following, reference is made to Figure 7 , will describe the use of Figure 1 The process of collecting and storing EDR data in the system shown. A similar process can be performed to collect and store DSSAD data.

[0095] Figure 7 It is shown Figure 1 Flowchart of the EDR data collection process of the system shown.

[0096] In S702, the telecommunication device 15 of the vehicle data recording system 10 obtains event data from at least one module, ECU, component, program, etc. including the EDR 11. For example, the telecommunication device 15 may receive EDR data recorded when an event is triggered from the EDR 11, and may additionally collect the geographic location, date, time, etc. of the event.

[0097] In S704, the telecommunication device 15 generates an event report message and transmits the event report message to the cloud storage system 20 on the network in a wireless manner. The event report message may include EDR data and vehicle identification information. The event report message may further include additional information such as the geographic location, date, time, vehicle model, year of manufacture, and manufacturer of the event.

[0098] In S706, the repository coordinator 25 of the cloud storage system 20 obtains privacy rules related to the vehicle from the privacy policy-related database of the data repository 29. According to the privacy rules, the repository coordinator 25 can be configured to perform pre-processing (i.e., data filtering) on ​​the event report message, such as extracting data elements that are allowed to be collected or deleting data elements that are not allowed to be collected from the event report message received from the vehicle.

[0099] In S708, for the pre-processed event report message, the repository coordinator 25 may generate link data for maintaining the association between the EDR data to be stored in different databases and the vehicle identification information (VII). The link data may be generated based on the VII and a salt value as a randomly generated value.

[0100] In S710, the repository coordinator 25 may store a first data set including the VII and the salted value in the VII database. In addition, the repository coordinator 25 may store a second data set including the link data in the event database.

[0101] In S712 , the cloud storage system 20 may send a response message indicating that the event data storage is successful to the in-vehicle data recording system 10 .

[0102] It should be understood that the above exemplary embodiments can be implemented in a variety of different ways. In some examples, the various methods, devices, servers, (sub) systems described in the present disclosure can be implemented by at least one general-purpose computer having a processor, memory, disk or other large-capacity memory, communication interface, input / output (I / O) device and other peripheral devices. A general-purpose computer can be used as a device, server, system, etc. that performs the above methods by loading software instructions into a processor and then running the instructions to perform the functions described in the present disclosure.

[0103] On the other hand, various methods or functions described in the present disclosure can be implemented using instructions stored in a non-transitory recording medium that can be read and executed by one or more processors. Non-transitory recording media include, for example, all types of recording devices that store data in a form readable by a computer system. For example, non-transitory recording media include storage media such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash drives, optical devices, magnetic hard drives, and solid-state drives (SSD).

[0104] Although exemplary embodiments of the present disclosure are described for illustrative purposes, it will be understood by those skilled in the art that various modifications, additions and substitutions may be made without departing from the concept and scope of the claimed invention. Therefore, exemplary embodiments of the present disclosure have been described for the sake of brevity and clarity. The scope of the technical concept of the present embodiment is not limited by the diagrams. Therefore, it will be understood by those of ordinary skill that the scope of the claimed invention is not limited by the embodiments explicitly described above, but by the claims and their equivalents.

[0105] CROSS-REFERENCE TO RELATED APPLICATIONS

[0106] This application claims priority based on Korean Patent Application No. 10-2020-0027455 filed on March 4, 2020 and Korean Patent Application No. 10-2021-0025820 filed on February 25, 2021, the entire disclosures of which are incorporated herein by reference in their entirety.

Claims

1. A method for collecting and managing vehicle-generated data, the method being executed by at least one server on a network for collecting and managing vehicle-generated data from a vehicle, the method include: receiving an event report message and an interaction report message from a vehicle, the event report message including vehicle identification information and event data stored by an event data recorder of the vehicle, and the interaction report message including the vehicle identification information and interaction data indicating an interaction between an automated driving system of the vehicle and a driver; Generate link data according to the vehicle identification information and the salt value; storing the vehicle identification information and the salted value in a first database; as well as storing the event data and the link data in a second database, and storing the interaction data and the link data in a third database, It is characterized in that generating the linking data by applying a one-way hash function to the vehicle identification information and the salt value, and The vehicle identification information is a vehicle identification number (VIN), and the linking data is a de-identified version of the VIN generated based on the salted value and the VIN.

2. The method according to claim 1, further comprising: include: When it is necessary to remove the association between the vehicle identification information and the event data and the association between the vehicle identification information and the interaction data, the vehicle identification information or the salted value is deleted from the first database.

3. The method according to claim 1, further comprising: include: In response to expiration of a validity period set by an owner of the vehicle, the event data and the interaction data in the second database and the third database are maintained, and the vehicle identification information or the salted value of the vehicle is deleted from the first database.

4. The method according to claim 1, further comprising: receiving a request message from an owner of the vehicle, the request message requesting deletion of at least one of the vehicle identification information, the event data, and the interaction data; and In response to receiving the request message, at least one of the vehicle identification information, the link data, the event data, and the interaction data is deleted from a related database.

5. The method according to any one of claims 2 to 4, further comprising: include: When the vehicle identification information or the salt value is deleted from the first database, the security level of the authority to use the relevant event data and interaction data stored in the second database and the third database is reduced.

6. The method according to claim 5, It is characterized in that Based on the link data reconstructed according to the relevant vehicle identification information stored in the first database and the salt value, searching the second database or the third database for event data or interaction data whose security level is not reduced, and This allows directly searching the second database or the third database for event data or interaction data with a reduced security level without reconstructed link data.

7. The method according to claim 1, It is characterized in that The linking data is a de-identified version of a vehicle identification number (VIN), which is generated by generating a hash value by applying a one-way hash function to a concatenation of the salt value and some bits in the VIN of the vehicle, and replacing the some bits of the VIN with the hash value.

8. The method according to claim 7, It is characterized in that The bits include at least a production serial number.

9. A cloud storage system for collecting and managing vehicle-generated data from a vehicle and implemented by at least one server on a network, include: means for receiving an event report message and an interaction report message from a vehicle, the event report message comprising vehicle identification information and event data stored by an event data recorder of the vehicle, and the interaction report message comprising the vehicle identification information and interaction data indicating an interaction between an automated driving system of the vehicle and a driver; means for generating link data based on the vehicle identification information and the salt value; means for storing said vehicle identification information and said salted value in a first database; as well as means for storing said event data and said link data in a second database and storing said interaction data and said link data in a third database, It is characterized in that generating the linking data by applying a one-way hash function to the vehicle identification information and the salt value, and The vehicle identification information is a vehicle identification number (VIN), and the linking data is a de-identified version of the VIN generated based on the salted value and the VIN.

10. The system according to claim 9 further comprises a device for the following operation: when it is necessary to remove the association between the vehicle identification information and the event data and the association between the vehicle identification information and the interaction data, deleting the vehicle identification information or the salted value from the first database.

11. The system according to claim 9, further comprising means for performing the following operations: in response to expiration of a validity period set by an owner of the vehicle, maintaining the event data and the interaction data in the second database and the third database and deleting the vehicle identification information or the salted value of the vehicle from the first database.

12. The system according to claim 9, further comprising: means for receiving a request message from an owner of the vehicle, the request message requesting deletion of at least one of the vehicle identification information, the event data, and the interaction data; and Means for deleting at least one of the vehicle identification information, the link data, the event data, and the interaction data from a relevant database in response to receiving the request message.

13. A system according to any one of claims 10 to 12, It is characterized in that When the vehicle identification information or the salt value is deleted from the first database, the security level of the authority to use the relevant event data and interaction data stored in the second database and the third database is reduced.

14. The system according to claim 13, Features: Based on the link data reconstructed according to the relevant vehicle identification information stored in the first database and the salt value, searching the second database or the third database for event data or interaction data whose security level is not reduced, and It allows to search the event data or interaction data with reduced security level directly from the second database or the third database without reconstructed link data.

15. The system according to claim 9, It is characterized in that The linking data is a de-identified version of a vehicle identification number (VIN), which is generated by generating a hash value by applying a one-way hash function to the concatenation of the salt value and some bits of the VIN of the vehicle, and replacing the some bits of the VIN with the hash value.

16. The system according to claim 15, It is characterized in that The bits include at least a production serial number.

Citation Information

Patent Citations

  • Dishwasher system and control method

    KR1020210025820A

  • Anti-theft system and method for rental car

    CN107323418A

  • Cooperative Adaptive Cruise Control based on Driving Pattern of Target Vehicle

    CN108263382A