Data backup method and system, storage medium, and vehicle

Abstract

A data backup method and system, a storage medium, and a vehicle. The data backup method comprises: acquiring related data of a target vehicle; on the basis of the related data, determining whether a preset triggering condition is satisfied; and when the preset triggering condition is satisfied, determining target data on the basis of the related data, and backing up the target data.

Description

Data backup method, system, storage medium and vehicle

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese patent application number 202311292008.5, filed with the China Patent Office on September 28, 2023, entitled “Data backup method, system, storage medium and vehicle,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0003] The present disclosure relates to the field of vehicle control technology, and in particular to a data backup method, system, storage medium, and vehicle. Background Art

[0004] A vehicle's Event Data Recorder (EDR) system is a flight data recorder similar to an aircraft's "black box." It monitors, collects, and records data related to the vehicle and its protective systems before, during, and after a crash. By analyzing the data recorded by the EDR, the cause of the accident can be determined.

[0005] Summary of the Invention

[0006] The purpose of the present disclosure is to provide a data backup method, system, storage medium and vehicle to solve the technical problem that data backup cannot be performed when EDR fails or is abnormal.

[0007] To achieve the above objectives, in a first aspect, the present disclosure provides a data backup method, comprising:

[0008] Obtain relevant data of the target vehicle;

[0009] Determining whether a preset trigger condition is met based on the relevant data;

[0010] When a preset trigger condition is met, target data is determined based on the relevant data, and the target data is backed up.

[0011] Optionally, backing up the target data includes:

[0012] storing the target data in a local memory;

[0013] and / or,

[0014] The target data is uploaded to the cloud.

[0015] Optionally, the target data includes information data and video data, and storing the target data in a local storage includes:

[0016] Obtaining first backup data according to the information data, wherein the first backup data includes data in a first data format obtained by encapsulating and encrypting the information data;

[0017] storing the first backup data and the video data in a local storage;

[0018] The uploading of the target data to the cloud includes:

[0019] Obtaining second backup data according to the information data, wherein the second backup data includes data in a second data format obtained by encapsulating and encrypting the information data;

[0020] Upload the second backup data and the video data to the cloud.

[0021] Optionally, the first data format includes a data format that is convenient for local storage, and the second data format includes a data format that is convenient for uploading to the cloud, and the first data format is different from the second data format.

[0022] Optionally, the data backup method further includes:

[0023] receiving a backup instruction, the backup instruction being used to instruct to back up the target data, the backup instruction including at least one of a first backup instruction issued by the cloud and a second backup instruction sent by the terminal device;

[0024] decrypting the first backup data according to the backup instruction and repackaging the data to obtain third backup data, where the third backup data has the same data format as the second backup data;

[0025] The third backup data and the video data are uploaded to the cloud.

[0026] Optionally, the data backup method further includes:

[0027] receiving a backup feedback signal sent by the cloud, wherein the backup feedback signal is used to indicate whether the target data fails to be uploaded;

[0028] When the backup feedback signal indicates that the target data has failed to be uploaded, obtaining fourth backup data based on the first backup data, the fourth backup data including data in a second data format obtained by decrypting and repackaging the first backup data;

[0029] The fourth backup data and the video data are uploaded to the cloud.

[0030] Optionally, the data backup method further includes:

[0031] In response to a user operation, generate an authorization request, send the authorization request to a terminal device, and receive an authorization result fed back by the terminal device based on the authorization request, wherein the authorization request is used to instruct the terminal device to determine the user's authorization result;

[0032] When the authorization result is successful, the download permission is opened, and the download permission is used to allow the terminal device to obtain the target data.

[0033] Optionally, the open download permission includes:

[0034] Opening download permission for a preset hardware interface on the target vehicle, where the preset hardware interface is used to download the target data;

[0035] and / or,

[0036] When the target data is uploaded to the cloud for backup, a control instruction is generated and sent to the cloud. The control instruction is used to instruct the cloud to open the download permission for the target data.

[0037] Optionally, the data backup method further includes:

[0038] If the authorization result is successful, sending the target data to the terminal device by means of highlight transmission;

[0039] The wireless transmission includes at least one of Bluetooth transmission, cellular transmission, WIFI transmission, wireless carrier communication transmission and near field communication transmission.

[0040] Optionally, obtaining relevant data of the target vehicle includes:

[0041] After the target vehicle is powered on, obtaining initial relevant data of the target vehicle;

[0042] The initial relevant data is filtered to obtain relevant data of the target vehicle.

[0043] Optionally, the target vehicle includes a vehicle, and obtaining initial relevant data of the target vehicle includes:

[0044] Obtain data as initial vehicle-related data in at least one of the following ways:

[0045] acquiring initial operating data via a flexible data rate bus or Ethernet in a control domain network of the vehicle;

[0046] Acquiring initial driving perception data through the autonomous driving domain controller of the vehicle;

[0047] Initial video data is acquired through the autonomous driving system of the vehicle.

[0048] Optionally, determining the target data according to the relevant data includes:

[0049] The target data is determined from the related data according to a preset backup data type.

[0050] Optionally, the preset backup data type includes signals, parameters, and videos, and determining the target data from the relevant data according to the preset backup data type includes:

[0051] Determining a first moment that meets a preset trigger condition, and determining a first duration based on the first moment;

[0052] The signals, parameters and videos within the first time period are determined from the relevant data to obtain target data.

[0053] In a second aspect, the present disclosure provides a vehicle backup method, comprising:

[0054] receiving target data, where the target data is determined based on relevant data when a preset trigger condition is satisfied by the target vehicle, and the relevant data is obtained after the target vehicle is powered on;

[0055] The target data is backed up and stored.

[0056] In a third aspect, the present disclosure provides an autonomous driving domain controller, comprising:

[0057] a first memory having a computer program stored thereon;

[0058] The first processor is used to execute the computer program in the first memory, so that the autonomous driving domain controller executes the data backup method described in the first aspect.

[0059] In a fourth aspect, the present disclosure provides a cloud device, comprising:

[0060] a second memory having a computer program stored thereon;

[0061] The second processor is used to execute the computer program in the second memory, so that the cloud device executes the data backup method described in the second aspect.

[0062] In a fifth aspect, the present disclosure provides a data backup system, comprising the autonomous driving domain controller described in the third aspect and the cloud device described in the fourth aspect.

[0063] In a sixth aspect, the present disclosure provides a vehicle comprising the autonomous driving domain controller described in the fifth aspect.

[0064] In a seventh aspect, the present disclosure provides a non-volatile storage medium having a computer program stored thereon. When the program is executed by a processor, a device equipped with the non-volatile storage medium executes the steps of the data backup method described in the first aspect.

[0065] The above technical solution can acquire relevant data about a target vehicle and, if the relevant data determines that a preset trigger condition has been met, determine the target data based on the relevant data and then back up the target data. This allows for backup of target data in the event of a malfunction or anomaly in the vehicle's event data recorder (EDR). Furthermore, the entire backup process is implemented using existing vehicle components, eliminating the need for system redesign, resulting in low costs and ensuring the reliability of the backed-up target data.

[0066] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following detailed description, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings:

[0068] FIG1 is a flow chart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0069] FIG2 is a block diagram of a vehicle event data recording system.

[0070] FIG. 3 is another flow chart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0071] FIG. 4 is another flow chart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0072] FIG. 5 is another flow chart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0073] FIG6 is another flow chart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0074] FIG. 7 is another flow chart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0075] FIG8 is a flowchart showing a data backup method according to an exemplary embodiment of the present disclosure.

[0076] FIG9 is a block diagram of an autonomous driving domain controller according to an exemplary embodiment of the present disclosure.

[0077] FIG10 is a block diagram of a cloud device according to an exemplary embodiment of the present disclosure.

[0078] FIG. 11 is a block diagram showing a data backup system according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0079] The following describes the specific embodiments of the present disclosure in detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to illustrate and explain the present disclosure and are not intended to limit the present disclosure.

[0080] Vehicles are typically equipped with an EDR (Event Data Recording) system (EDR) to record data. While EDRs have strict safety and stability requirements, they cannot record vehicle event data if they malfunction or fail. Furthermore, EDRs are expensive. Adding another EDR to a vehicle not only increases the cost of acquiring vehicle event data, but also complicates system design and increases power consumption, compromising EDR system stability and reducing the reliability of the captured vehicle event data.

[0081] Referring to Figure 2, the inventors also found that it is very inconvenient to read data from the EDR. For example, when reading the vehicle event data recorded in the EDR, it is often necessary to connect the vehicle end to the on-board diagnostic interface through a dedicated reading device, and then read the vehicle event data. The dedicated reading device is expensive, and the process of reading data through the dedicated reading device is cumbersome, resulting in the owner being unable to obtain the data recorded in the EDR. Secondly, the EDR does not support uploading vehicle event data to the cloud, and cannot be obtained through remote control and downloaded through the cloud. Secondly, whether it is a stand-alone EDR device or a common integrated module, it mainly interacts with other external sensors through the CAN bus, and the type of data that can be obtained is limited. Among them, other integrated modules such as the Auxiliary Control Module (ACM), the Powertrain Control Module (PCM), the Roll Over Sensor (ROS), etc. As the number of autonomous driving functions on vehicles continues to increase, vehicles will continue to be empowered with OTA (Over-The-Air Technology) upgrades to the vehicle software after delivery. However, the data recorded by EDR cannot meet the requirements for additional recorded content of the vehicle, resulting in EDR being unable to support the expansion of vehicle functions.

[0082] In view of this, the present disclosure provides a data backup method, system, storage medium and vehicle to address the shortcomings of data backup through EDR.

[0083] FIG1 is a flow chart of a data backup method according to an exemplary embodiment of the present disclosure. The data backup method can be applied to a vehicle, such as a car, an airplane, a ship, a bicycle, a motorcycle, etc. This embodiment uses the vehicle as an example. The data backup method can be applied to an autonomous driving domain controller on the vehicle, or can be applied to other controllers on the vehicle, which is not limited in the embodiment of the present disclosure. Referring to FIG1 , the data backup method may include the following steps:

[0084] In step S11 , relevant data of the target vehicle is obtained.

[0085] Among them, when the target vehicle is a vehicle, the relevant data may include relevant data of the vehicle and vehicle protection system before, during and after the incident, such as: the time of collision, the location of collision, the speed, acceleration, airbag information, brake status, accelerator pedal position of the vehicle at the time of collision, and status information of the automatic driving system of the vehicle with automatic driving function, etc. It can also be the time of collision, the location of collision, basic information of the vehicle at the time of collision, vehicle status and dynamic information, operation information of the auxiliary driving system or automatic driving system, driving environment information, such as video, driver operation information, etc.

[0086] Among them, relevant data can cover three categories of data. The first category is information data that can be used as judgment data for preset trigger conditions and to record vehicle status; the second category is information data only used to record vehicle status; and the third category is video data.

[0087] In step S12, it is determined whether a preset trigger condition is met based on relevant data.

[0088] In step S13, when the preset trigger condition is met, target data is determined according to the relevant data, and the target data is backed up.

[0089] It is worth noting that the preset trigger conditions can be the trigger recording conditions specified in the EDR national standard, and can also be preset according to the activation, shutdown, failure and access request of the autonomous driving function, etc. This disclosure does not limit this.

[0090] The backup conditions can be preset based on the trigger conditions specified in the national EDR standard, ensuring that the backup is initiated when the EDR records data on the vehicle. The backup conditions can also be preset based on the user's backup needs.

[0091] In the embodiment of the present disclosure, relevant data of the target vehicle is obtained. When it is determined that the preset trigger conditions are met based on the relevant data, the target data is determined based on the relevant data and the target data is backed up. The vehicle event data can also be backed up when the EDR on the vehicle is abnormal or fails.

[0092] In order to facilitate those skilled in the art to better understand the data backup method provided by the present disclosure, the relevant steps involved in the data backup method are described in detail below with examples.

[0093] In a possible embodiment, referring to FIG. 3 , in step S11 , obtaining relevant vehicle data after the vehicle is powered on may include:

[0094] In step S21 , after the target vehicle is powered on, initial relevant data of the target vehicle is acquired.

[0095] For example, after the vehicle is powered on, the data generated by each component on the vehicle is recorded, where the components may include engine accessories, such as the valve mechanism, intake system and exhaust system; transmission system accessories, such as the transmission, drive shaft, clutch and flywheel; braking system accessories, such as the brake pedal, brake disc, ABS (Antilock Brake System) pump and vacuum booster; steering system accessories, such as steering knuckle, steering gear, steering wheel and tie rod; driving system accessories and suspension accessories, such as tires, front axle, rear axle, swing arm, shock absorber and coil spring.

[0096] In step S22, the initial relevant data is filtered to obtain vehicle relevant data.

[0097] It is worth noting that the initial relevant data is filtered by removing useless data such as incomplete data and abnormal data. Therefore, it is necessary to remove useless data such as incomplete data and abnormal data to improve the accuracy of the vehicle's relevant data and further reduce the amount of relevant data.

[0098] For example, data analysis is performed on the initial relevant data to determine the signals used for judgment, the parameters used for recording, and the video; the data analysis results are then judged, and useless data such as incomplete data, abnormal data, or dirty data are eliminated to obtain relevant data; and the relevant data is timestamped and temporarily stored according to a preset frequency.

[0099] In a possible embodiment, when the target vehicle includes a vehicle, in step S21, obtaining initial relevant data of the target vehicle may include:

[0100] Obtain data as initial vehicle-related data in at least one of the following ways:

[0101] Initial vehicle operation data is obtained through the vehicle's Control Area Network Flexible Data Rate bus (CANFD bus) or Ethernet.

[0102] Initial driving perception data is obtained through the vehicle's autonomous driving domain controller (DC).

[0103] Initial video data is obtained through the vehicle's automatic operation (AO) system.

[0104] It is worth noting that because the EDR configured on the vehicle mainly interacts with other external sensors through the CANFD bus, the type of data that can be obtained is limited and cannot meet the vehicle's requirements for increased recorded content, resulting in the EDR being unable to support vehicle function expansion. The disclosed embodiment, based on the CANFD bus, can also obtain vehicle event data through the autonomous driving domain controller and the autonomous driving system, expanding the type of data obtained, thereby storing data that the EDR cannot obtain, and can meet the vehicle's requirements for increased recorded content as it upgrades via OTA, thereby supporting vehicle function expansion.

[0105] It is worth noting that when acquiring relevant data, the data obtained from the components will be parsed according to the CANFD bus signal, the autonomous driving domain controller, and the internally defined data format of the autonomous driving system, and converted into a data format that meets the backup requirements, so as to facilitate the subsequent backup of the target data determined based on the relevant data. This data format generally strictly follows the data format for recording data specified in the EDR national standard. If the data obtained from the component is not required to be recorded in the EDR national standard, a custom data format can be determined based on storage or upload requirements, and the data obtained from the component will be parsed and converted into the custom data format.

[0106] In a possible embodiment, in step S13, determining target data according to relevant data may include:

[0107] According to the preset backup data type, target data is determined from related data.

[0108] It is worth noting that the preset backup data type can be preset according to the backup requirements, and this disclosure does not limit it.

[0109] In a possible embodiment, when the preset backup data types include signals, parameters, and videos, determining target data from relevant data according to the preset backup data types may include:

[0110] Determine a first moment when a preset trigger condition is satisfied, and determine a first duration based on the first moment;

[0111] Signals, parameters, and videos within a first time period are determined from the relevant data to obtain target data.

[0112] Among them, the first time length includes the second time length before the first moment and the third time length after the first moment. The second time length and the third time length can be preset according to the time length of vehicle event data that may be involved in the vehicle collision event, or can be preset according to the time length specified by the EDR national standard. The embodiment of the present disclosure does not limit this.

[0113] For example, the second duration can be 15 seconds, and the third duration can be 5 seconds. Then, the first duration includes the duration between 15 seconds before the first moment and 5 seconds after the first moment. Accordingly, when the first moment is 14:30:20, the first duration can be 20 seconds between 14:30:05 and 14:30:25. That is, based on the timestamps of the signals, parameters, and videos when they are temporarily stored, the signals, parameters, and videos within the 20 seconds between 14:30:05 and 14:30:25 are determined from the relevant data as the target data.

[0114] It is worth noting that the duration specified in the EDR national standard is generally 15 seconds before the first moment to the first moment, or from the first moment to 5 seconds after the first moment. This does not guarantee that the acquired vehicle event data covers all data corresponding to the vehicle event. In the disclosed embodiment, however, the target data corresponding to the first duration can cover all data corresponding to the vehicle event, thereby ensuring the integrity of the vehicle event data.

[0115] In a possible embodiment, in step S13, backing up the target data may include:

[0116] Storing target data in local storage;

[0117] and / or,

[0118] Upload the target data to the cloud.

[0119] The present disclosure implements the backup of target data by at least one of storing in a local memory and uploading to the cloud, thereby avoiding the situation where the vehicle event data cannot be backed up due to EDR failure or abnormality.

[0120] In a possible embodiment, when the target data includes information data and video data, storing the target data in a local memory may include:

[0121] First backup data is obtained according to the information data, and the first backup data includes data in a first data format obtained by encapsulating and encrypting the information data.

[0122] The first backup data and the video data are stored in a local storage.

[0123] Upload target data to the cloud, which may include:

[0124] Obtaining second backup data according to the information data, the second backup data including data in a second data format obtained by encapsulating and encrypting the information data;

[0125] Upload the second backup data and video data to the cloud.

[0126] For example, the information data is encapsulated and encrypted into first backup data in a first data format, the first backup data and the video data are stored in a local memory, the information data is encapsulated and encrypted into second backup data in a second data format, and the second backup data and the video data are uploaded to the cloud.

[0127] Through the above method, backup can be performed through local storage and / or the cloud, and information data can be encapsulated into a data format that is convenient for backup on different devices, thereby improving the accuracy and reliability of the backup results.

[0128] In a possible embodiment, the first data format includes a data format that is convenient for local storage, and the second data format includes a data format that is convenient for uploading to the cloud, and the first data format is different from the second data format.

[0129] It is worth noting that the first data format can be a data format that is easy to compress, easy to read by a computer, and does not cause garbled characters or tampering during transmission or storage. For example, the first data format can be a bin format. Accordingly, the information data can be encapsulated in the bin format and encrypted to obtain first backup data, and the first backup data and the video data can be stored in the local storage.

[0130] It is worth noting that the second data format can be a data format that facilitates data exchange between servers, is easy to read, and is easy to write and parse. For example, the second data format can be JSON format. Accordingly, the information data can be encapsulated in JSON format and encrypted to obtain second backup data, and the second backup data and video data can be uploaded to the cloud.

[0131] In a possible embodiment, referring to FIG4 , the data backup method may further include:

[0132] In step S31, a backup instruction is received, where the backup instruction is used to instruct to back up target data. The backup instruction includes at least one of a first backup instruction sent from the cloud and a second backup instruction sent from the terminal device.

[0133] In step S32, the first backup data is decrypted and repackaged according to the backup instruction to obtain third backup data. The data format of the third backup data is consistent with that of the second backup data.

[0134] In step S33, the third backup data and the video data are uploaded to the cloud.

[0135] Therefore, it is possible to support the cloud and the terminal device bound to the vehicle to trigger backup by sending backup instructions, so that users can remotely control the vehicle to back up data through the cloud and / or terminal device according to backup requirements, thereby improving user convenience.

[0136] In a possible embodiment, referring to FIG5 , the data backup method may further include:

[0137] In step S41, a backup feedback signal sent from the cloud is received, where the backup feedback signal is used to indicate whether the target data fails to be uploaded.

[0138] In step S42, when the backup feedback signal indicates that the target data upload fails, fourth backup data is obtained based on the first backup data. The fourth backup data includes data in the second data format obtained by decrypting and repackaging the first backup data.

[0139] In step S43, the fourth backup data and the video data are uploaded to the cloud.

[0140] It is worth noting that when uploading target data to the cloud, network problems may cause the target data to fail to be uploaded to the cloud. In the disclosed embodiment, the cloud device can generate a backup feedback signal and send it to the vehicle to facilitate the vehicle to upload the target data again, thereby reducing the possibility of target data failing to be uploaded to the cloud due to network problems.

[0141] It is worth noting that, when the backup feedback signal indicates that the target data has failed to be uploaded, the file name that has not been successfully uploaded can be recorded to facilitate uploading to the cloud again.

[0142] It's worth noting that you can query the network status. When the network is communicating normally and is idle, you can decrypt the first backup data in bin format and repackage it into the fourth backup data in json format. Then, you can upload the fourth backup data and the video data to the cloud again. This can improve the success rate of uploading the target data to the cloud and the reliability of the backup results.

[0143] In a possible embodiment, referring to FIG6 , the data backup method may further include:

[0144] In step S51, in response to the user operation, an authorization request is generated, the authorization request is sent to the terminal device, and the authorization result fed back by the terminal device according to the authorization request is received. The authorization request is used to instruct the terminal device to confirm the user's authorization result.

[0145] The user operation may be inserting a USB drive into a preset hardware interface for downloading target data, or may be a download request sent by the user through a terminal device. The terminal device may communicate with the vehicle via Bluetooth or Wi-Fi, which is not limited in this disclosure.

[0146] It is worth noting that the terminal device is a terminal device authorized by the car owner, such as the car owner's mobile phone, tablet computer, laptop computer, etc. Authorization verification is performed through the terminal device authorized by the car owner to avoid target data leakage.

[0147] In step S52, when the authorization result is successful, the download permission is opened, and the download permission is used to allow the terminal device to obtain the target data.

[0148] For example, in response to a user action, an authorization request can be generated and then sent to a terminal device authorized by the vehicle owner. The user can verify the authorization through the terminal device and provide feedback on the verification result. The vehicle then receives the authorization result from the terminal device and, if the authorization result is successful, grants download permission for the target data.

[0149] In a possible embodiment, opening download permissions may include:

[0150] Open download permissions for a preset hardware interface on the target vehicle, where the preset hardware interface is used to download target data; and / or, when uploading the target data to the cloud for backup, generate a control instruction, send the control instruction to the cloud, and instruct the cloud to open download permissions for the target data.

[0151] Among them, when the target transportation tool is a vehicle, the preset hardware interface can be an existing hardware interface on the vehicle that can read data, such as a USB (Universal Serial Bus) interface, an OBD (On Board Diagnostics) interface, etc.

[0152] It's worth noting that if the terminal device has a small amount of memory, it can be used only for authentication based on the authorization request, with the backed-up target data accessible via a separate reader. For example, a mobile phone can authenticate itself based on the authorization request sent by the vehicle, and upon successful authorization, access the backed-up target data on the vehicle via a USB drive.

[0153] For example, a USB flash drive can be inserted into the USB interface, and the vehicle sends an authorization request to the mobile phone connected to its Bluetooth. The mobile phone performs authentication in response to the user's operation on it, generates an authorization result and feeds it back to the vehicle. If the authorization result is successful, the vehicle opens the download permission of the USB interface on the vehicle, and the USB flash drive reads the target data backed up on the vehicle through the USB interface.

[0154] It is worth noting that if the terminal device has a large memory, in addition to performing identity authentication based on the authorization request, the terminal device can also directly access the backed-up target data if authorization is successful. For example, a laptop user can perform identity authentication based on the authorization request sent by the vehicle and directly access the backed-up target data in the cloud if authorization is successful.

[0155] For example, a laptop computer establishes a communication connection with a vehicle, and the vehicle sends an authorization request to the laptop computer. The laptop computer performs authentication in response to the user's operation on it, generates an authorization result and feeds it back to the vehicle. If the authorization result is successful, the vehicle opens the download permission in the cloud, and the laptop computer reads the target data backed up in the cloud.

[0156] It is worth noting that the present disclosure can back up the target data in two ways: local storage and uploading to the cloud. Therefore, opening download permissions can include opening download permissions for the local storage and download permissions for the cloud. When users download the target data in the local storage, they need to implement it through the hardware interface. Therefore, the download permissions of the preset hardware interface and the download permissions of the cloud can be opened. Thus, users can obtain target data in two different ways. Among them, the method of obtaining target data through the hardware interface is convenient, fast and low-cost, and remotely obtaining target data through the cloud improves the convenience of users downloading target data. In addition, both methods do not require dedicated reading equipment to complete the reading operation of vehicle event data, which enables the car owner to obtain event data in a convenient and fast way, and the operation process is simple.

[0157] In a possible embodiment, the data backup method may further include:

[0158] If the authorization result is successful, the target data is sent to the terminal device via wireless transmission;

[0159] The wireless transmission includes at least one of Bluetooth transmission, cellular transmission, WIFI transmission, wireless carrier communication transmission and near field communication transmission.

[0160] It's worth noting that if the terminal device has a large memory, it can access the backed-up target data via wireless transmission if authorization is successful. For example, a laptop user authenticates based on the authorization request sent by the vehicle. If authorization is successful, the vehicle can then transmit the target data to the laptop via Bluetooth, cellular, Wi-Fi, Ultra Wide Band (UWB), or Near Field Communication (NFC).

[0161] For example, a laptop computer establishes a Bluetooth communication connection with a vehicle, and the vehicle sends an authorization request to the laptop computer. The laptop computer performs authentication in response to the user's operation on it, generates an authorization result and feeds it back to the vehicle. If the authorization result is successful, the vehicle transmits the target data to the laptop computer via Bluetooth transmission.

[0162] Through the above method, different methods can be used to obtain the backed-up target data according to the memory size of the terminal device or the communication method between the terminal device and the vehicle, thereby improving the convenience of users in obtaining the target data.

[0163] For example, referring to FIG7 , the embodiment of the present disclosure takes the data backup method applied to a vehicle as an example, which may include the following steps:

[0164] In step S61 , after the vehicle is powered on, initial relevant data of the vehicle is acquired.

[0165] In step S62, the initial relevant data is filtered to obtain relevant data.

[0166] In step S63, it is determined whether the preset trigger condition is met according to the relevant data. If so, step S64 is executed; if not, the process returns to step S61.

[0167] In step S64 , a first moment that satisfies a preset trigger condition is determined, and a first duration is determined according to the first moment.

[0168] In step S65, target data within the first duration is determined from the relevant data, the target data including information data and video data. Steps S66 to S67, and steps S68 to S69 are executed respectively.

[0169] In step S66, the target data is encapsulated and encrypted into a first data format to obtain first backup data.

[0170] In step S67, the first backup data and the video data are stored in the memory.

[0171] In step S68, the target data is encapsulated and encrypted into a second data format to obtain second backup data.

[0172] In step S69, the second backup data and the video data are uploaded to the cloud.

[0173] The specific implementation methods of the above steps have been described in detail above and will not be repeated here. In addition, it should be understood that for the above method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should know that the present disclosure is not limited to the order of the actions described above. Secondly, those skilled in the art should also know that the embodiments described above are preferred embodiments, and the steps involved are not necessarily required by the present disclosure.

[0174] The above technical solution enables backup of target data when the vehicle's event data recording (EDR) system fails or experiences an anomaly. Furthermore, the entire backup process is implemented using existing vehicle components, eliminating the need for system redesign and reducing costs. It ensures the reliability of the backed-up target data and supports expansion beyond EDR functionality to include recording important event data for assisted driving or autonomous driving, supporting multiple data acquisition methods.

[0175] Based on the same concept, the present disclosure also provides a data backup method, which can be applied to cloud devices. Referring to FIG8 , the data backup method may include the following steps:

[0176] In step S71 , target data is received. The target data is determined based on relevant data when a target vehicle meets a preset trigger condition. The relevant data is obtained after the target vehicle is powered on.

[0177] In step S72, the target data is backed up and stored.

[0178] Through the above method, target data can be backed up. The target data is determined based on relevant data when the vehicle meets the preset trigger conditions. The relevant data is obtained after the vehicle is powered on. In this way, vehicle event data can be backed up even when the EDR on the vehicle is abnormal or malfunctioning.

[0179] In a possible embodiment, the data backup method may further include:

[0180] Sending a first backup instruction to the vehicle and receiving target data uploaded by the vehicle according to the first backup instruction, wherein the first backup instruction is used to instruct the vehicle to back up the target data;

[0181] Back up the target data.

[0182] The present disclosure can also support triggering backup by sending backup instructions through the cloud, so that users can back up through the cloud according to backup needs, improving user convenience, so that data that cannot be obtained by EDR can be more conveniently stored in the cloud, and reducing the situation where vehicle event data cannot be backed up when EDR is abnormal or fails on the vehicle.

[0183] In a possible embodiment, the data backup method may further include:

[0184] Generate a backup feedback signal based on the result of backing up the target data, send the backup feedback signal to the vehicle, and receive the target data uploaded again by the vehicle based on the backup feedback signal. The backup feedback signal is used to instruct the vehicle to upload the target data again if the target data upload fails;

[0185] Back up the target data.

[0186] The present disclosure improves the probability of uploading target data to the cloud and the reliability of the backup results by monitoring the backup storage results.

[0187] In a possible embodiment, the data backup method may further include:

[0188] Receive control instructions sent by the vehicle;

[0189] The download permission of the target data is opened according to the control instruction.

[0190] In the present disclosure, users can remotely obtain target data through the cloud, which improves the convenience of users downloading target data and eliminates the need to use dedicated reading equipment to complete the reading operation of vehicle event data. This enables vehicle owners to obtain event data in a convenient and fast manner, and the operation process is simple.

[0191] Based on the same concept, the present disclosure also provides a vehicle autonomous driving domain controller, comprising:

[0192] a first memory having a computer program stored thereon;

[0193] The first processor is used to execute the computer program in the first memory, so that the autonomous driving domain controller executes the above-mentioned data backup method applied to the vehicle.

[0194] In this way, vehicle event data can be backed up when the EDR on the vehicle is abnormal or fails.

[0195] FIG9 is a block diagram of a vehicle autonomous driving domain controller shown in an exemplary embodiment of the present disclosure. Referring to FIG9 , the vehicle autonomous driving domain controller includes a data backup system, a data exchange module, and a microcontroller unit (MCU). The MCU obtains the vehicle's initial relevant data from the CANFD bus and sends this initial relevant data to the data backup system through the data exchange module. The data backup system directly reads the initial driving perception data inside the vehicle autonomous driving domain controller (DC) and controls the automatic operation system (AO) to obtain initial video data. The data backup system uses the initial vehicle operation data, initial driving perception data, and initial video data as the vehicle's initial relevant data. Based on the relevant data, it determines whether a preset backup condition is triggered. If the preset backup condition is triggered, the target data is determined based on the relevant data and backed up. The target data can be vehicle event data.

[0196] The data backup system includes a process health management module (SMHM), a data abstraction module, a data analysis and management module, a data assembly and decryption module, a data forwarding module, a data file management module, and a diagnostic reading module (DIAG). The data abstraction module converts the initial relevant data into a storage format that meets the EDR national standard and forwards the converted initial relevant data to the data analysis and management module. The data analysis and management module analyzes, classifies, and calculates the converted initial relevant data, determining the signals used for judgment, parameters used for recording, and video. The module then evaluates the data analysis results, eliminating useless data such as incomplete, abnormal, or dirty data to obtain relevant data. The module then timestamps the relevant data and temporarily stores the most recent 15 seconds of relevant data according to a preset frequency.

[0197] For example, when the data abstraction module determines that a preset backup condition has been triggered based on relevant data, it controls the data assembly and decryption module to encapsulate the relevant data into two backup formats: a first backup data in .bin format, which is encrypted, and a second backup data in .json format. The data file management module then controls the recording of the encrypted first backup data to the autonomous driving domain controller's memory, and the data forwarding module controls the uploading of the second backup data to a cloud device, thus backing up vehicle event data.

[0198] For example, when the data abstraction module determines to trigger the preset backup conditions based on relevant data, it also controls the data analysis and management module to analyze the relevant data to obtain the trigger signal time T0, event type and event name corresponding to this vehicle event, and controls the data reading module to send the trigger signal, event type and event name of this vehicle event to the automatic driving system, and controls the automatic driving system to obtain video images from the front, rear, left and right four cameras on the vehicle, save the video data to the designated directory and notify the data forwarding module, which will immediately trigger the video data to be uploaded to the cloud.

[0199] For example, the data abstraction module controls the data forwarding module to upload the vehicle event data recorded in the memory to the cloud device through the communication channel of the cockpit domain on the vehicle at the trigger moment, and then uploads it every 500ms until the relevant data recorded for this event is completed and the cloud is notified to lock the uploaded data corresponding to this event. The recorded video data is mainly uploaded in two parts, one part is from 15s before the trigger moment to the trigger moment, and the other part is 5s after the trigger moment.

[0200] For example, the data backup system is initialized and runs for a long time after the autonomous driving domain controller is powered on. After the data backup system is started, the data abstraction module collects the signals and data that need to be collected from the CANFD bus and the autonomous driving domain controller in real time, and attaches a timestamp when temporarily storing the acquired signals and data. Then, it parses and converts them into the target data format required by the data backup system according to the bus signal and the data format defined inside the autonomous driving domain controller. Among them, the data format required by the data backup system generally strictly refers to the recording format specified by the EDR national standard. If the data to be recorded is not specified in the EDR national standard, the data format is defined by itself.

[0201] It's worth noting that the data analysis and management module analyzes and categorizes vehicle data in the target data format to generate relevant data. There are two main types of vehicle data: signal data that serves as both a trigger and a record, such as speed, acceleration, airbag collision signals, faults, and the activation and deactivation of autonomous driving functions; and data that is recorded solely, such as videos and images.

[0202] For example, the data analysis management module needs to analyze and filter the acquired data, eliminate abnormal data in the initial relevant data, obtain relevant data, and record the relevant data of the last 15 seconds according to the timestamp of the relevant data. If the recorded relevant data exceeds 15 seconds, the relevant data with the earliest recording time will be cleared according to the timestamp of the relevant data.

[0203] For example, while recording and managing data in memory, the data analysis and management module will continuously analyze relevant data to determine whether the preset trigger conditions are met. If the preset trigger conditions are met, the analysis will determine T0, event type, and event recording start and end points. For the EDR national standard event type T0, the national standard provisions are followed. For newly added event types such as autonomous driving function activation, deactivation, failure, and request for intervention, T0 is the time of occurrence. The event recording start and end points are both specified as 15 seconds before T0 and 5 seconds after T0.

[0204] When the preset trigger conditions are met, the data assembly and decryption module will encapsulate the target data in combination with T0, event type, event record starting point and event record end point. On the one hand, the relevant data will be encapsulated into the second backup data in json format and uploaded to the cloud device. On the other hand, the relevant data will be encapsulated into the first backup data in bin format and encrypted and stored in the memory of the autonomous driving domain controller.

[0205] While triggering the preset backup conditions, the autonomous driving system obtains the initial video data of 15 seconds before and 5 seconds after T0 from the camera on the vehicle, desensitizes and compresses the initial video data to obtain video data, where the vehicle includes four cameras: front, rear, left and right, and at least the front camera.

[0206] For example, the data forwarding module uploads the second backup data and video data to the cloud device. When the second backup data and video data are not successfully uploaded due to network reasons, the data forwarding module will inform the data file management module to record the file name that was not successfully uploaded. When the data forwarding module queries that the network is restored and idle, it will decrypt the encrypted first backup data in bin format, and re-encapsulate it into the third backup data in json format, and re-upload the third backup data and video data to the cloud device.

[0207] Among them, the data file management module stores the encrypted first backup data in bin format in the non-volatile memory of the autonomous driving domain controller, manages the first backup data and video data, and records the event file name of the failed upload, etc.

[0208] Among them, in addition to uploading vehicle data to the cloud device when the preset trigger conditions are met, the data backup system also supports two ways to trigger upload: sending backup instructions through the cloud device and / or the APP on the terminal device connected to the vehicle. Both methods are to decrypt the first backup data in bin format stored locally by the data backup system, and re-encapsulate it into the third backup data in json format, and upload the third backup data and video data to the cloud device. The cloud device parses the third backup data in json format into a readable file in CSV (Comma Separated Values) format for backup and storage.

[0209] It is worth noting that the working principle of the above data backup system is only a reference design. The data backup system's startup strategy, event type, backup conditions, and data type of recorded events need to be adjusted in accordance with the EDR national standard. At the same time, it supports the expansion of functions, recording event types, and recording data elements as autonomous driving functions increase, and upgrades the data backup system to increase functions as the autonomous driving system OTA upgrades the software version.

[0210] In addition, the data forwarding module, data assembly and decryption module, and data file management module are also used to jointly support the reading of vehicle event data stored in the autonomous driving domain controller through a USB flash drive based on the cockpit PAD (Portable Android Devic, tablet computer) and mobile phone APP.

[0211] It is worth noting that in addition to supporting reading by dedicated reading devices, the vehicle event data stored in the non-volatile memory in the vehicle's autonomous driving domain controller can also be read through a USB flash drive.

[0212] For example, a USB flash drive is plugged into the vehicle's central control USB port, ensuring a proper connection between the USB flash drive and the vehicle. Meanwhile, the driver's personal phone is connected to the vehicle via Bluetooth. The driver selects "Read vehicle event data from the data backup system" on the central control PAD screen. The central control PAD then reconfirms the Bluetooth connection with the personal phone. If the Bluetooth connection between the PAD and the personal phone is established, it generates an authorization request and sends it to the personal phone, requesting authentication based on the authorization request. The authorization request includes authentication information such as the driver's name, address, and ID number. The driver authenticates the user through the app on their phone. If successful, the app will provide a confirmation that the PAD has authenticated. Otherwise, authentication fails. The autonomous driving system notifies the data backup system in the autonomous driving domain controller of a compressed (ZIP) package of vehicle event data to be uploaded. The ZIP package contains the vehicle event data in local storage, decrypted and packaged into a CSV file, along with video data. The data forwarding module forwards the ZIP package data to the PAD via the DOIP (Diagnostic Over Internet Protocol) protocol, a diagnostic protocol based on TCP / IP. The AO performs an integrity check on the received ZIP and forwards the ZIP package to the USB flash drive. If the integrity check passes, it indicates that the vehicle event data has been successfully read; if the integrity check fails, it indicates that the vehicle event data has failed to be read. The integrity check principle can be as follows: when the PAD sends the vehicle event data, it performs an integrity check to obtain a first verification result; when the AO receives the vehicle event data, it performs an integrity check to obtain a second verification result. If the first and second verification results are consistent, the integrity check passes and the vehicle event data has been successfully read. Integrity checking can also be implemented using other verification methods, such as MB5 (Message-Digest Algorithm 5).

[0213] It is worth noting that the method of reading vehicle event data with a USB flash drive is convenient, fast and low-cost, eliminating the need for the use of dedicated reading equipment in related technologies to complete the reading operation of vehicle event data. This enables car owners to obtain vehicle event data in a convenient and fast manner.

[0214] Based on the same concept, referring to FIG10 , the present disclosure further provides a cloud device 900 , including:

[0215] A second memory 902 on which a computer program is stored;

[0216] The second processor 901 is used to execute the computer program in the second memory, so that the cloud device executes the data backup method.

[0217] In this way, vehicle event data can be backed up when the EDR on the vehicle is abnormal or fails.

[0218] Based on the same concept, the present disclosure also provides a data backup system 1000, see Figure 11, which includes the above-mentioned autonomous driving domain controller 800 and cloud device 900.

[0219] In this way, vehicle event data can be backed up when the EDR on the vehicle is abnormal or fails.

[0220] Based on the same inventive concept, the present disclosure provides a vehicle comprising the above-mentioned autonomous driving domain controller.

[0221] In this way, vehicle event data can be backed up when the EDR on the vehicle is abnormal or fails.

[0222] The present disclosure also provides a non-volatile storage medium having a computer program stored thereon. When the program is executed by a processor, the device in which the non-volatile storage medium is installed performs the steps of the above-mentioned data backup method. For example, the computer-readable storage medium can be the above-mentioned first memory including program instructions, and the above-mentioned program instructions can be executed by the first processor of the vehicle's autonomous driving domain controller to complete the above-mentioned data backup method for the vehicle. The computer-readable storage medium can also be the above-mentioned second memory including program instructions, and the above-mentioned program instructions can be executed by the second processor of the cloud device to complete the above-mentioned data backup method for the cloud device.

[0223] The preferred embodiments of the present disclosure are described in detail above in conjunction with the accompanying drawings. However, the present disclosure is not limited to the specific details of the above embodiments. Within the technical concept of the present disclosure, various simple modifications can be made to the technical solutions of the present disclosure, and these simple modifications all fall within the scope of protection of the present disclosure.

[0224] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, the present disclosure will not further describe various possible combinations.

[0225] In addition, the various embodiments of the present disclosure may be arbitrarily combined, and as long as they do not violate the concept of the present disclosure, they should also be regarded as the contents disclosed by the present disclosure.

Claims

1. A data backup method, characterized in that: include: Obtain relevant data of the target vehicle; Determining whether a preset trigger condition is met according to the relevant data; When the preset trigger condition is met, target data is determined according to the relevant data, and the target data is backed up.

2. The data backup method according to claim 1, characterized in that: The backing up of the target data includes: storing the target data in a local storage; and / or, The target data is uploaded to the cloud.

3. The data backup method according to claim 2, characterized in that: The target data includes information data and video data, and storing the target data in a local memory includes: Obtain first backup data according to the information data, wherein the first backup data includes data in a first data format obtained by encapsulating and encrypting the information data; storing the first backup data and the video data in a local storage; The uploading of the target data to the cloud comprises: Obtain second backup data according to the information data, wherein the second backup data includes data in a second data format obtained by encapsulating and encrypting the information data; The second backup data and the video data are uploaded to the cloud.

4. The data backup method according to claim 3, characterized in that: The first data format includes a data format that is convenient for local storage, and the second data format includes a data format that is convenient for uploading to the cloud, and the first data format is different from the second data format.

5. The data backup method according to claim 3 or 4, characterized in that: The data backup method further includes: receiving a backup instruction, the backup instruction being used to instruct to back up the target data, the backup instruction comprising at least one of a first backup instruction issued by the cloud and a second backup instruction sent by the terminal device; According to the backup instruction, the first backup data is decrypted and repackaged to obtain third backup data, wherein the third backup data has a consistent data format with the second backup data; The third backup data and the video data are uploaded to the cloud.

6. The data backup method according to claim 3 or 4, characterized in that: The data backup method further includes: Receiving a backup feedback signal sent by the cloud, wherein the backup feedback signal is used to indicate whether the target data fails to be uploaded; In a case where the backup feedback signal indicates that the target data has failed to be uploaded, fourth backup data is obtained according to the first backup data, the fourth backup data including data in a second data format obtained by decrypting and repackaging the first backup data; The fourth backup data and the video data are uploaded to the cloud.

7. The data backup method according to any one of claims 1 to 6, characterized in that: The data backup method further includes: In response to a user operation, generate an authorization request, send the authorization request to a terminal device, and receive an authorization result fed back by the terminal device according to the authorization request, wherein the authorization request is used to instruct the terminal device to confirm the authorization result of the user; When the authorization result is successful, the download permission is opened, and the download permission is used to allow the terminal device to obtain the target data.

8. The data backup method according to claim 7, characterized in that: The open download permissions include: Opening download permission for a preset hardware interface on the target vehicle, where the preset hardware interface is used to download the target data; and / or, When the target data is uploaded to the cloud for backup, a control instruction is generated and sent to the cloud, wherein the control instruction is used to instruct the cloud to open the download permission for the target data.

9. The data backup method according to claim 7, characterized in that: The data backup method further includes: When the authorization result is successful, the target data is sent to the terminal device by wireless transmission; The wireless transmission includes at least one of Bluetooth transmission, cellular transmission, WIFI transmission, wireless carrier communication transmission and near field communication transmission.

10. The data backup method according to any one of claims 1 to 9, characterized in that: The obtaining of relevant data of the target vehicle includes: After the target vehicle is powered on, obtaining initial relevant data of the target vehicle; The initial relevant data is filtered to obtain relevant data of the target vehicle.

11. The data backup method according to claim 10, characterized in that: The target vehicle includes a vehicle, and the obtaining of initial relevant data of the target vehicle includes: Obtain data as initial vehicle-related data in at least one of the following ways: acquiring initial operation data via a control domain network flexible data rate bus or Ethernet of the vehicle; Acquiring initial driving perception data through the autonomous driving domain controller of the vehicle; Initial video data is acquired through the autonomous driving system of the vehicle.

12. The data backup method according to any one of claims 1 to 9, characterized in that: The determining the target data according to the relevant data comprises: The target data is determined from the related data according to a preset backup data type.

13. The data backup method according to claim 12, characterized in that: The preset backup data types include signals, parameters, and videos, and determining the target data from the related data according to the preset backup data types includes: Determine a first moment that satisfies a preset trigger condition, and determine a first duration according to the first moment; The signal, parameter and video within the first duration are determined from the relevant data to obtain target data.

14. A data backup method, characterized in that: include: Receiving target data, where the target data is determined based on relevant data when a preset trigger condition is met by the target vehicle, and the relevant data is obtained after the target vehicle is powered on; The target data is backed up and stored.

15. An autonomous driving domain controller, characterized in that: include: a first memory having a computer program stored thereon; The first processor is used to execute the computer program in the first memory so that the autonomous driving domain controller executes the data backup method described in any one of claims 1-13.

16. A cloud device, characterized in that: include: a second memory having a computer program stored thereon; The second processor is used to execute the computer program in the second memory, so that the cloud device executes the data backup method described in claim 14.

17. A data backup system, characterized in that: It includes the autonomous driving domain controller as described in claim 15 and the cloud device as described in claim 16.

18. A vehicle, characterized in that: Including the autonomous driving domain controller as described in claim 15.

19. A non-volatile storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the device installed with the non-volatile storage medium executes the steps of the data backup method according to any one of claims 1 to 14.

Images