An automobile intelligent driving EDR data cloud uploading method and system, device and medium

Abstract

This invention provides a method, system, device, and medium for uploading EDR data to the cloud for intelligent driving vehicles, belonging to the field of intelligent driving vehicle technology. The method includes: real-time acquisition of EDR data and writing it into a buffer; continuous monitoring of the vehicle's dynamic state and the working state of the active safety system; sending a trigger command when a collision or potential collision event meeting preset conditions is detected; according to the trigger command, storing the EDR data in the buffer for a first preset time period before the trigger command occurs on a disk, and continuously storing the EDR data for a second preset time period after the trigger command occurs on a disk, performing data compression during the disk storage process; and uploading the stored EDR data to the cloud. This invention achieves autonomous and controllable uploading of EDR data to the cloud, enabling efficient data retrieval, and allowing for in-depth analysis and playback of accidents based on cloud platform data management combined with real-time data acquired at the time of EDR triggering, without relying on locally stored data.

Description

Technical Field

[0001] This invention relates to the field of intelligent driving vehicle technology, and in particular to a method, system, and equipment medium for uploading EDR data of intelligent driving vehicles to the cloud. Background Technology

[0002] The background for uploading EDR data to the cloud in intelligent driving vehicles is the combined effect of the transformation towards intelligent and connected vehicles and the upgrading of safety protection requirements:

[0003] 1. Traditional automotive EDR systems mostly use local storage, which has many limitations;

[0004] 2. Intelligent driving relies on a large amount of real road condition data to train algorithm models. EDR data (including vehicle status, driving operation, environmental perception, etc.) is the core material for algorithm iteration. After being uploaded to the cloud, multi-vehicle data can be aggregated and shared, providing a massive number of samples for the optimization of autonomous driving systems. At the same time, intelligent driving vehicles face new risks such as network attacks and functional safety failures. The cloud needs to analyze multi-vehicle EDR data in real time to achieve cross-vehicle collaborative early warning and rapid response.

[0005] 3. Countries are gradually introducing regulations on data security for intelligent connected vehicles, requiring EDR data to be traceable and auditable, and to be stored in the cloud with encrypted storage and complete log records after being uploaded, in order to meet the needs of accident tracing and compliant evidence collection. At the same time, regulatory authorities need to conduct industry safety situation analysis by aggregating EDR data from multiple vehicles, and promote the improvement of intelligent driving safety standards.

[0006] However, traditional automotive EDR systems mostly use local storage, storing data on fixed hard drives / memory / disks. The drawbacks of this technology are: offline data storage; data is stored on physical data, making it potentially irreparable if damaged; limited storage capacity (only able to retain critical data for a few hours to a few days), failing to meet the long-term storage needs of massive sensor data (cameras, radar, lidar, etc.) for intelligent driving; and a lack of powerful local computing capabilities, making it difficult to conduct in-depth analysis of complex driving behaviors, abnormal operating conditions, and potential safety risks (such as autonomous driving system malfunctions and cyberattacks), thus failing to fully unlock the value of the data. Summary of the Invention

[0007] This invention aims to solve at least one of the aforementioned problems in the prior art by proposing a technical solution for cloud storage of EDR data. It utilizes a design method and rules for real-time collection, caching, triggering, storage, encryption, and uploading of key vehicle data during operation to achieve targeted data uploading and cloud-based traceability. In cases of severe vehicle damage, it can also rapidly provide cloud data for quick accident reconstruction analysis. Furthermore, it provides a secure data encryption and decryption process to ensure network data security.

[0008] In a first aspect, embodiments of the present invention provide a method for uploading EDR data of intelligent driving vehicles to the cloud, including:

[0009] Real-time acquisition of EDR data and writing to the buffer;

[0010] It continuously monitors the vehicle's dynamic status and the operational status of the active safety system, and sends a trigger command when a collision or potential collision event that meets preset conditions is detected.

[0011] According to the trigger command, the EDR data in the buffer within a first preset time before the trigger command occurs is written to disk and stored continuously within a second preset time after the trigger command occurs. Data compression is performed during the disk writing process.

[0012] Upload the EDR data stored on disk to the cloud.

[0013] In a preferred embodiment, the step of real-time acquisition of EDR data and writing it to the buffer includes:

[0014] The raw data message is obtained by subscribing to the corresponding topic of EDR data through the API of RSCL middleware;

[0015] The received raw data message will undergo preliminary format conversion and validity verification;

[0016] After the validity verification is passed, the EDR data is written to the circular buffer in real time;

[0017] The EDR data includes at least one of the following: full CANbus data, intelligent sensing data, and PNC data.

[0018] In a preferred embodiment, after the step of real-time acquisition of EDR data and writing to the buffer, the method further includes: packaging the data in the buffer every third preset time period to generate a file with a timestamp and storing it on disk.

[0019] In a preferred embodiment, the step of continuously detecting the vehicle's dynamic state and the operating state of the active safety system, and sending a trigger command when a collision or potential collision event meeting preset conditions is as follows:

[0020] The collision or potential collision events that meet the preset conditions include at least one of the following: function-triggered events and physical quantity-triggered events;

[0021] The function triggering events include at least one of the following: automatic emergency braking event, automatic emergency steering event, and emergency steering assist event actively issued by the active safety system when it detects a hazard;

[0022] The physical quantity triggering events include at least one of the following: longitudinal velocity change event, high deceleration event, and airbag deployment event.

[0023] In a preferred embodiment, the step of writing EDR data to disk within a first preset time period before the trigger instruction occurs, and continuously writing EDR data to disk within a second preset time period after the trigger instruction occurs, includes the following steps after performing a data compression step during the disk writing process: reading and parsing the file written to disk, and performing desensitization processing on the privacy information in the file.

[0024] In a preferred embodiment, the step of uploading the EDR data stored on disk to the cloud includes: obtaining the EDR data stored on disk, encrypting it using an encryption algorithm, and storing the encrypted EDR data.

[0025] In a preferred embodiment, the step of uploading the EDR data stored on disk to the cloud includes:

[0026] Initialize the HTTPS link, maintain the upload task queue, and use a sequential execution strategy to upload the encrypted EDR data to the cloud through the HTTPS link.

[0027] In a second aspect, embodiments of the present invention provide a vehicle intelligent driving EDR data cloud uploading system, the system being configured to implement any of the methods described in the first aspect, the system comprising:

[0028] The acquisition module is used to acquire EDR data in real time and write it to the buffer;

[0029] The trigger module is used to continuously monitor the vehicle's dynamic status and the working status of the active safety system. When a collision or potential collision event that meets the preset conditions is detected, a trigger command is sent.

[0030] The storage module is used to write the EDR data of the buffer to disk within a first preset time before the trigger instruction occurs, and to continuously write the EDR data to disk within a second preset time after the trigger instruction occurs, and to perform data compression during the disk writing process.

[0031] The upload module is used to upload EDR data stored on disk to the cloud.

[0032] Thirdly, embodiments of the present invention provide an electronic device, including:

[0033] One or more processors;

[0034] Memory, used to store one or more programs;

[0035] When the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described in the first aspect.

[0036] Fourthly, embodiments of the present invention provide a computer-readable medium storing a computer program that, when executed by a processor, implements the steps of any of the methods described in the first aspect.

[0037] Beneficial effects of this invention:

[0038] This invention enables autonomous and controllable cloud uploading of EDR data, allowing for efficient data retrieval. It can perform in-depth analysis and playback of incidents based on cloud platform data management combined with real-time data collected when EDR is triggered, without relying on local storage data, and uses encryption protocols to protect user data security. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of a cloud-based intelligent driving EDR data upload system for automobiles, provided as an embodiment of the present invention.

[0040] Figure 2 This is a schematic diagram of the data acquisition and storage processing flow provided in an embodiment of the present invention.

[0041] Figure 3 This is a schematic diagram of the data processing flow of the data desensitization module provided in an embodiment of the present invention.

[0042] Figure 4 This is a schematic diagram of the data processing flow of the encryption module provided in an embodiment of the present invention.

[0043] Figure 5 This is a schematic diagram of the data processing flow of the upload module provided in an embodiment of the present invention.

[0044] Figure 6 This is a schematic diagram of a method for uploading EDR data of intelligent driving vehicles to the cloud, provided as an embodiment of the present invention.

[0045] Figure 7 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0046] To enable those skilled in the art to better understand the technical solutions of the present invention, exemplary embodiments of the present invention are described below in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0047] Where there is no conflict, the various embodiments of the present invention and the features thereof may be combined with each other.

[0048] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0049] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Terms such as “connected” or “linked” are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.

[0050] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art and the invention, and will not be interpreted as having an idealized or overly formal meaning unless expressly so defined herein.

[0051] In the technical solution of this invention, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information all comply with relevant laws and regulations and do not violate public order and good morals. The use of user data in this technical solution follows relevant national laws and regulations (e.g., the "Information Security Technology - Personal Information Security Specification"). For example: appropriate measures are taken for personal information access control; restrictions are imposed on the display of personal information; the purpose of using personal information does not exceed the scope of direct or reasonable association; and explicit identity targeting is eliminated when using personal information to avoid precisely locating a specific individual.

[0052] Definitions of abbreviations and key terms:

[0053] EDR: Event Data Recorder, is a system used to record critical vehicle data before, during, and after a collision event.

[0054] HTTPS: Hypertext Transfer Protocol Secure, is a secure version of the Hypertext Transfer Protocol that protects the security of communication between the client and the server through encryption mechanisms.

[0055] DCL: Data Closed Loop, refers to data collection and uploading to the cloud.

[0056] Figure 1 This is a schematic diagram of a cloud-based EDR (Electronic Data Recording) system architecture for intelligent driving in automobiles, provided as an embodiment of the present invention. Figure 1 As shown, the system includes: a data acquisition module, a triggering module, a storage module, an image (data) desensitization module, an encryption module, and an upload module.

[0057] The overall process of the system is as follows: data acquisition is based on RSCL middleware to subscribe to data, collect and cache the data; data processing involves parsing and compressing the data, as well as desensitizing some of the data; data uploading is based on data encryption scheme and data upload protocol, and is encrypted and uploaded to the cloud.

[0058] The data processing flow of the acquisition module includes:

[0059] 1) During module initialization, the list of topics to be subscribed to is obtained from the configuration module;

[0060] 2) Subscribe to these topics via the RSCL middleware API;

[0061] 3) When a data message arrives, the acquisition module performs preliminary format conversion and validity verification on the received raw message msg;

[0062] 4) After the verification is successful, the data is forwarded to the storage module, which then writes it into the circular buffer in real time.

[0063] in, Figure 2 This is a schematic diagram of the data acquisition and storage processing flow provided in an embodiment of the present invention. Figure 2 As shown, the data acquisition and storage process includes: determining the unified channel to be acquired based on the configuration issued by Yunrui and the configuration of Cherui; calculating the size of the circular buffer space; creating all channels; starting acquisition; circular storage; stopping acquisition when the data loop service terminates; closing the channel and reclaiming resources.

[0064] The EDR trigger module is used to monitor the vehicle's dynamic status and the operational status of the active safety system in real time. When a collision or potential collision event that meets preset conditions is detected, the data recording process is immediately initiated. The EDR trigger module listens for two types of trigger events in real time: functional trigger events and physical quantity trigger events.

[0065] Function Trigger Events: The EDR trigger module listens for trigger signal topics from the active safety system when it detects a hazard, including AEB (Automatic Emergency Braking), AES (Automatic Emergency Steering), and ESA (Emergency Steering Assist) function trigger signals. When an active safety function is triggered, it sends a trigger message to the EDR trigger module according to the communication protocol. Upon receiving the trigger message, the EDR trigger module sends a trigger command to the storage module. The trigger message communication protocol uses RSCL service-client communication, with the active safety function sender acting as the client and the EDR trigger module receiver acting as the server.

[0066] Physical quantity triggering events: The EDR triggering module listens to the / canbus / vehicle_report and / MCU / vehicle_processing topics published by the RSCL middleware. When the relevant signals meet the triggering conditions, it sends a triggering command to the storage module.

[0067] A physical quantity triggers an event log if any of the following conditions are met:

[0068] Sudden longitudinal velocity change: Within 150 milliseconds, the absolute value of the change in the vehicle's longitudinal (x-axis) velocity is greater than 8 km / h, which typically corresponds to a violent impact or sudden braking;

[0069] High deceleration: The longitudinal deceleration of the vehicle is greater than 11 m / s² for three consecutive frames (each frame period is usually 10ms, totaling 30ms). This signal is usually provided by the airbag controller (ACU) and is a key indicator for judging the severity of a collision.

[0070] Airbag deployment: The airbag controller (ACU) issues an ignition command for any airbag.

[0071] The storage module is used for data caching, packaging, compression, and local persistent storage. It is the core data processing unit of the EDR system. The storage module continuously receives message data from the acquisition module and writes it to the buffer. When an EDR trigger message is received, it writes the data in the buffer to an rsclbag data packet with a timestamp. Corresponding to the EDR event-triggered storage is the VHR regular storage. The VHR function packages the data in the buffer every 60 seconds, generates an rsclbag file with a timestamp, and writes it to disk.

[0072] The main functions of the storage module include:

[0073] Data buffer: Continuously receive data from the acquisition module and write it into a fixed-size circular buffer, which can hold at least 10 seconds of full data;

[0074] EDR Event Triggered Storage: Upon receiving a trigger signal from the trigger module, the storage module immediately stops writing data to the current buffer. The system extracts historical data from the buffer for the 10 seconds prior to the event. Simultaneously, it continues to collect and record new data for the 5 seconds following the event. These two data segments (a total of 15 seconds) are merged, compressed, and packaged into a complete event data packet.

[0075] in, Figure 3 This is a schematic diagram of the data processing flow of the data desensitization module provided in an embodiment of the present invention. Figure 3 As shown, the data anonymization module is used to meet regulatory requirements by anonymizing privacy information such as facial recognition data and license plate numbers. The data processing flow of the data anonymization module includes: reading the file to disk and parsing to obtain the raw H265 stream; H265 / H264 decoding; preprocessing and model inference; post-processing and MOSI encoding; H265 / H264 encoding; and packet assembly and file writing.

[0076] in, Figure 4 This is a schematic diagram of the data processing flow of the encryption module provided in an embodiment of the present invention. Figure 4 As shown, the data processing flow of the encryption module includes: loading the file to be encrypted; obtaining the DERK key; encrypting the original data using the AES-256-CBC encryption algorithm; obtaining the platform public key; encrypting the key using the platform public key; and storing the encrypted data in the file.

[0077] in, Figure 5 This is a schematic diagram of the data processing flow of the upload module provided in an embodiment of the present invention. Figure 5 As shown, the data processing flow of the upload module includes: initializing HttpsDev and the upload task queue; starting the upload; retrieving a task from the upload task queue; performing a single file upload; two-way authentication; file fragmentation, filling in the upload data protocol and uploading; determining if the upload was successful; retrying at intervals if the upload is unsuccessful, up to the maximum number of retries (MaxRetryTimes); if the upload is successful, determining if all fragments have been uploaded; if any fragment upload is incomplete, continuing to upload that fragment; if all fragment uploads are complete, returning to the step of retrieving a task from the upload task queue, retrieving the next task and continuing execution.

[0078] The upload module is responsible for transmitting the event data packets recorded by EDR to the cloud server. The module maintains an upload task queue, adopts a sequential execution strategy, and has retry and breakpoint resume mechanisms.

[0079] In the following embodiments of the present invention, for ease of description, the vehicle-mounted controller is used as the execution subject. The execution subject may also be a software module, or other electronic devices capable of performing the following functions.

[0080] Figure 6 This is a flowchart illustrating a method for uploading EDR data from an intelligent driving system to the cloud, provided by an embodiment of the present invention; as shown below. Figure 6 As shown, the method includes:

[0081] Step S102: Collect EDR data in real time and write it to the buffer;

[0082] Step S104: Continuously monitor the vehicle's dynamic status and the working status of the active safety system. When a collision or potential collision event that meets the preset conditions is detected, send a trigger command.

[0083] Step S106: According to the trigger command, the EDR data in the buffer within a first preset time (e.g., 10 seconds) before the trigger command occurs is written to disk and stored continuously, and the EDR data within a second preset time (e.g., 5 seconds) after the trigger command occurs is written to disk. Data compression is performed during the disk writing process.

[0084] Step S108: Upload the EDR data stored on disk to the cloud.

[0085] This invention, through the aforementioned steps, collects full CAN data, sensing data, PNC data, etc., in real time. When a collision event or collision risk occurs, the first 10 seconds of cached data are written to disk, and the next 5 seconds of data are continuously stored. Data compression is performed during the disk writing process, and the data packets after disk writing are encrypted and uploaded to the cloud via an HTTPS link. Therefore, this invention achieves efficient cloud uploading of EDR data, without relying on local data storage. The encryption protocol protects user data security, and after EDR data is uploaded to the cloud, data review can be performed efficiently. In-depth analysis and playback of incidents can be conducted based on the cloud platform's data management combined with the real-time data collected at the time of EDR triggering.

[0086] In some embodiments, step S102, the step of real-time acquisition of EDR data and writing it to the buffer, includes:

[0087] The raw data message is obtained by subscribing to the corresponding topic of EDR data through the API of RSCL middleware;

[0088] The received raw data message msg undergoes preliminary format conversion and validity verification;

[0089] After the validity verification is passed, the EDR data is written to the circular buffer in real time;

[0090] The EDR data includes at least one of the following: full CANbus data, intelligent sensing data, and PNC data.

[0091] In some embodiments, after step S102, which involves real-time acquisition of EDR data and writing it to the buffer, the method further includes step 103, which involves packaging the data in the buffer every third preset time interval (e.g., 60 seconds) to generate a timestamped file and storing it on disk.

[0092] In some embodiments, step S104 involves continuously monitoring the vehicle's dynamic state and the operating state of the active safety system. When a collision or potential collision event that meets preset conditions is detected, a trigger command is sent.

[0093] The collision or potential collision events that meet the preset conditions include at least one of the following: function-triggered events and physical quantity-triggered events;

[0094] The function triggering events include at least one of the following: automatic emergency braking event, automatic emergency steering event, and emergency steering assist event actively issued by the active safety system when it detects a hazard;

[0095] The physical quantity triggering events include at least one of the following: longitudinal velocity change event, high deceleration event, and airbag deployment event.

[0096] In some embodiments, step S106, according to the trigger instruction, involves writing EDR data from the buffer to disk for a first preset time period before the trigger instruction occurs, and continuously writing EDR data to disk for a second preset time period after the trigger instruction occurs. The data compression step is performed during the disk writing process, followed by:

[0097] Step S107: Read and parse the file stored on disk, and desensitize the privacy information in the file.

[0098] In some embodiments, step S108, which involves uploading the EDR data stored on disk to the cloud, includes:

[0099] The EDR data obtained from disk storage is encrypted using an encryption algorithm, and the encrypted EDR data is then stored.

[0100] In some embodiments, step S108, which involves uploading the EDR data stored on disk to the cloud, includes:

[0101] Initialize the HTTPS link, maintain the upload task queue, and use a sequential execution strategy to upload the encrypted EDR data to the cloud through the HTTPS link.

[0102] Based on the same inventive concept, this invention also provides another vehicle intelligent driving EDR data cloud uploading system, the system being configured to implement any of the methods described in the above embodiments, the system comprising:

[0103] The acquisition module is used to acquire EDR data in real time and write it to the buffer;

[0104] The trigger module is used to continuously monitor the vehicle's dynamic status and the working status of the active safety system. When a collision or potential collision event that meets the preset conditions is detected, a trigger command is sent.

[0105] The storage module is used to write the EDR data of the buffer to disk within a first preset time before the trigger instruction occurs, and to continuously write the EDR data to disk within a second preset time after the trigger instruction occurs, and to perform data compression during the disk writing process.

[0106] The upload module is used to upload EDR data stored on disk to the cloud.

[0107] Based on the same inventive concept, embodiments of the present invention also provide an electronic device. Figure 7 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Figure 7 As shown, an embodiment of the present invention provides an electronic device including: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement any of the methods described in the above embodiments; the one or more I / O interfaces 103 are connected between the processor and the memory, configured to enable information interaction between the processor and the memory.

[0108] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0109] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0110] In some embodiments, the one or more processors 101 include a field-programmable gate array.

[0111] Based on the same inventive concept, embodiments of the present invention also provide a computer-readable medium. This computer-readable medium stores a computer program, wherein, when executed by a processor, the program implements the steps of any of the methods described in the above embodiments. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0112] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0113] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0114] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0115] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing state information from the computer-readable program instructions. This electronic circuitry can execute the computer-readable program instructions to implement various aspects of the invention.

[0116] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0117] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0118] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0119] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0120] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0121] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A method for uploading EDR data of intelligent driving vehicles to the cloud, characterized in that, include: Real-time acquisition of EDR data and writing to the buffer; It continuously monitors the vehicle's dynamic status and the operational status of the active safety system, and sends a trigger command when a collision or potential collision event that meets preset conditions is detected. According to the trigger command, the EDR data in the buffer within a first preset time before the trigger command occurs is written to disk and stored continuously within a second preset time after the trigger command occurs. Data compression is performed during the disk writing process. Upload the EDR data stored on disk to the cloud.

2. The method according to claim 1, characterized in that, The step of real-time acquisition of EDR data and writing it to the buffer includes: The raw data message is obtained by subscribing to the corresponding topic of EDR data through the API of RSCL middleware; The received raw data message will undergo preliminary format conversion and validity verification; After the validity verification is passed, the EDR data is written to the circular buffer in real time; The EDR data includes at least one of the following: full CANbus data, intelligent sensing data, and PNC data.

3. The method according to claim 1, characterized in that, After the step of real-time acquisition of EDR data and writing it to the buffer, the method further includes: every third preset time, packaging the data in the buffer, generating a file with a timestamp, and storing it on disk.

4. The method according to claim 1, characterized in that, In the step of continuously monitoring the vehicle's dynamic state and the operational status of the active safety system, and sending a trigger command when a collision or potential collision event meeting preset conditions is detected: The collision or potential collision events that meet the preset conditions include at least one of the following: function-triggered events and physical quantity-triggered events; The function triggering events include at least one of the following: automatic emergency braking event, automatic emergency steering event, and emergency steering assist event actively issued by the active safety system when it detects a hazard; The physical quantity triggering events include at least one of the following: longitudinal velocity change event, high deceleration event, and airbag deployment event.

5. The method according to claim 1, characterized in that, The step involves storing EDR data in the buffer for a first preset time period before the trigger command occurs, and continuously storing EDR data for a second preset time period after the trigger command occurs. After performing a data compression step during the disk storage process, the step includes: reading and parsing the file stored on disk, and desensitizing the privacy information in the file.

6. The method according to claim 1, characterized in that, The step of uploading the EDR data stored on disk to the cloud includes: obtaining the EDR data stored on disk, encrypting it using an encryption algorithm, and storing the encrypted EDR data.

7. The method according to claim 6, characterized in that, The step of uploading the EDR data stored on disk to the cloud includes: Initialize the HTTPS link, maintain the upload task queue, and use a sequential execution strategy to upload the encrypted EDR data to the cloud through the HTTPS link.

8. A cloud-based intelligent driving EDR data uploading system for automobiles, characterized in that, The system is configured to implement the method as described in any one of claims 1 to 7, the system comprising: The acquisition module is used to acquire EDR data in real time and write it to the buffer; The trigger module is used to continuously monitor the vehicle's dynamic status and the working status of the active safety system. When a collision or potential collision event that meets the preset conditions is detected, a trigger command is sent. The storage module is used to write the EDR data of the buffer to disk within a first preset time before the trigger instruction occurs, and to continuously write the EDR data to disk within a second preset time after the trigger instruction occurs, and to perform data compression during the disk writing process. The upload module is used to upload EDR data stored on disk to the cloud.

9. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 7.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images