Vehicle event data recording method and apparatus, device, system, vehicle, and medium

Abstract

A vehicle event data recording method and apparatus, a device, a system, a vehicle, and a medium. The method comprises: when it is recognized that a vehicle has experienced a collision event, sending collision event information and storage synchronization policy information to a data recording end, thereby storing a first data set in a first non-volatile storage region at a target moment on the basis of the collision event information and the storage synchronization policy information (S10); at the target moment, storing a second data set in a second non-volatile storage region (S20); and in response to a diagnosis reading instruction sent by the data recording end, sending to the data recording end vehicle event record data in the second data set, performing event diagnosis, and recording vehicle collision event record data (S30). According to the described method, once the collision event has occurred, the data recording end first completes recording of vehicle data, and then the data recording end performs diagnosis and again saves the vehicle collision event record data, so as to avoid the problem of loss of collision event data after the data recording end is damaged.

Description

Automobile event data recording method, device, equipment, system, vehicle and medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 24, 2023, with application number 2023115913435 and application name “Automobile Event Data Recording Method, System and Vehicle”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the technical field of automobile accident data recording, and in particular to an automobile event data recording method, device, equipment, system, vehicle and medium. Background Art

[0003] GB 39732-2020, "Vehicle Event Data Recorder (EDR) System," defines a vehicle event data recorder (VEDR) system as a device or system consisting of one or more onboard electronic modules that monitors, collects, and records data from the vehicle and occupant protection systems before, during, and after a collision. EDR devices are increasingly being installed in vehicles.

[0004] The related art method of recording automobile event data is to use a specially designed single on-board electronic module (such as an airbag controller) to meet regulatory requirements. However, the single on-board electronic module requires real-time updates, has high maintenance costs, and has no backup.

[0005] Summary of the Invention

[0006] The main purpose of this application is to provide a method, device, equipment, system, vehicle and medium for recording automobile event data, aiming to solve the technical problem that automobile accident data recording cannot be backed up and is difficult to update in related technologies.

[0007] To achieve the above objectives, the present application provides a method for recording automobile event data, which is applied to an event recording terminal and includes the following steps:

[0008] When a vehicle collision event is identified, sending collision event information and storage synchronization strategy information to a data recording end, so that the data recording end stores a first data set in a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information;

[0009] At the target moment, storing a second data set in a second non-volatile storage area, wherein the second data set represents vehicle collision event record data, and the first data set represents vehicle data;

[0010] In response to the diagnostic read instruction sent by the data recording end, the automobile event record data in the second data set is sent to the data recording end, so that the data recording end performs event diagnosis and records the automobile collision event record data according to the diagnosis result.

[0011] Optionally, when a vehicle collision event is identified, sending collision event information and storing synchronization strategy information to a data recording end includes:

[0012] When a vehicle collision event is identified, the collision event information is sent to the data recording end;

[0013] Sending the storage matching attribute value of the second non-volatile storage area via the CAN bus;

[0014] The storage matching attribute value is sent to the data recording end as storage synchronization strategy information.

[0015] Optionally, before the step of sending the collision event information and storing the synchronization strategy information to the data recording end when a collision event of the vehicle is identified, the step further includes:

[0016] The storage matching attribute value of the second non-volatile storage area is sent to the data recording end via the CAN bus at a preset period, so that the data recording end performs matching based on the storage matching attribute value to determine whether a collision event occurs in the vehicle.

[0017] In addition, to achieve the above-mentioned purpose, the present application also proposes a method for recording automobile event data, which is applied to a data recording terminal and includes:

[0018] Receive collision event information sent by the event recording end and store synchronization strategy information;

[0019] The first data set is stored in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information.

[0020] Optionally, storing the first data set in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information includes:

[0021] Obtaining a storage matching attribute value of a second non-volatile storage area according to the storage synchronization strategy information;

[0022] matching the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area;

[0023] When the storage matching attribute value of the second non-volatile storage area is inconsistent with the storage matching attribute value of the first non-volatile storage area, the first data set is stored in the corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area, and the number of storage areas in the first non-volatile storage area and the second non-volatile storage area are the same and match one to one.

[0024] Optionally, matching the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area includes:

[0025] Obtaining a second storage sequence number attribute value and a second locking state of the data recording end based on the storage matching attribute value of the second non-volatile storage area;

[0026] querying the first non-volatile storage area for the attribute value and the first locking state of the corresponding first storage sequence number according to the second storage sequence number of the data recording end;

[0027] The attribute value of the first storage sequence number and the first locking state are matched with the attribute value of the second storage sequence number and the second locking state.

[0028] Optionally, storing the first data set in a corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area includes:

[0029] determining a target storage area in the first non-volatile storage area according to the second storage sequence number;

[0030] The first data set is stored in the target storage area, and the target area is marked as a locked state based on the second locking state.

[0031] Optionally, after storing the first data set in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information, the method further includes:

[0032] Initiating a diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event record data in the second data set based on the diagnostic read instruction;

[0033] Receiving and reading the automobile event record data sent by the event recording terminal;

[0034] Determining response information of the event recording end;

[0035] When the response information is a positive response, the collision event record data in the automobile event record data is stored in a corresponding storage area in the first non-volatile storage area.

[0036] Optionally, after determining the response information of the event recording end, the method further includes:

[0037] When the response information is a negative response, the step of re-initiating a diagnostic read instruction to the event recording end, and returning the initiated diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event recording data in the second data set based on the diagnostic read instruction.

[0038] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle event data recording device, which is applied to an event recording end. The vehicle event data recording device includes:

[0039] an identification module configured to, upon identifying a vehicle collision event, send collision event information and storage synchronization strategy information to a data recording terminal, so that the data recording terminal stores a first data set in a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information;

[0040] a second storage module, configured to store a second data set in a second non-volatile storage area at the target time, wherein the second data set represents vehicle collision event record data, and the first data set represents vehicle data;

[0041] The sending module is used to send the automobile event record data in the second data set to the data recording end in response to the diagnostic read instruction sent by the data recording end, so that the data recording end performs event diagnosis and records the automobile collision event record data according to the diagnosis result.

[0042] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle event data recording device, which is applied to a data recording end. The vehicle event data recording device includes:

[0043] A receiving module is used to receive the collision event information sent by the event recording end and store the synchronization strategy information;

[0044] The first storage module is configured to store the first data set in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information.

[0045] In addition, to achieve the above-mentioned purpose, the present application also proposes an automobile event data recording system, which includes an event recording end and a data recording end. The event recording end executes the automobile event data recording method described above, and the data recording end executes the automobile event data recording method described above.

[0046] In addition, to achieve the above-mentioned purpose, the present application also proposes an automobile event data recording device, which includes: a memory, a processor, and an automobile event data recording program stored on the memory and runnable on the processor. The automobile event data recording program is configured to implement the automobile event data recording method applied to the event recording end or the steps of the automobile event data recording method applied to the data recording end as described above.

[0047] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, on which a car event data recording program is stored. When the car event data recording program is executed by a processor, it implements the car event data recording method applied to the event recording end or the steps of the car event data recording method applied to the data recording end as described above.

[0048] In addition, to achieve the above-mentioned purpose, the present application also proposes an automobile event data recording system, the automobile event data recording system comprising an event recording end and a data recording end, the event recording end and the data recording end being connected via a CAN bus, the data recording end comprising a plurality of first non-volatile storage areas, and the event recording end comprising a plurality of second non-volatile storage areas;

[0049] The event recording end is used to send collision event information and storage synchronization strategy information to the data recording end when a collision event of the vehicle is identified, and store the second data set in the plurality of second non-volatile storage areas at a target time;

[0050] The data recording end is used to store the first data set in the plurality of first non-volatile storage areas at a target time according to the collision event information and the storage synchronization strategy information.

[0051] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle, which includes an electric power steering system, a vehicle controller, an electronic stability system, a diagnostic system and the automobile event data recording system mentioned above, and the electric power steering system, the vehicle controller, the electronic stability system and the diagnostic system are respectively connected to the data recording end of the automobile event data recording system through a CAN bus.

[0052] The automobile event data recording method of the present application is applied to an event recording end. When a collision event is identified in a vehicle, the collision event information and storage synchronization strategy information are sent to the data recording end, so that the data recording end stores a first data set to a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information; at the target time, a second data set is stored in a second non-volatile storage area, the second data set representing automobile collision event recording data, and the first data set representing automobile data; in response to a diagnostic read instruction sent by the data recording end, the automobile event recording data in the second data set is sent to the data recording end, so that the data recording end performs event diagnosis and records automobile collision event recording data according to the diagnosis result. In the present application, after a collision event occurs, the data recording end first completes the data recording, and then the data recording end reads the diagnostic instruction and saves the record again, thereby realizing the backup of the event data, which can conveniently and quickly update the collision event data, and avoid the problem of collision event data loss after the data recording end is damaged.

[0053] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] The above and other objects, features and advantages of the present application will become more apparent through a more detailed description of exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0055] FIG1 is a schematic diagram of the structure of a vehicle event data recording device in a hardware operating environment according to an embodiment of the present application;

[0056] FIG2 is a flow chart of a method for recording automobile event data applied to an event recording terminal according to an embodiment of the present application;

[0057] FIG3 is a schematic structural diagram of an automobile event data recording system according to an embodiment of the present application;

[0058] FIG4 is another flow chart of a method for recording automobile event data applied to an event recording terminal;

[0059] FIG5 is a flow chart of a method for recording automobile event data applied to a data recording terminal according to an embodiment of the present application;

[0060] FIG6 is another flow chart of a method for recording automobile event data applied to a data recording terminal according to an embodiment of the present application;

[0061] FIG7 is another flow chart of a method for recording automobile event data applied to a data recording terminal according to an embodiment of the present application;

[0062] FIG8 is a schematic diagram of the overall flow of an embodiment of a method for recording automobile event data of the present application;

[0063] FIG9 is a schematic structural diagram of an automobile event data recording device applied to an event recording terminal according to an embodiment of the present application;

[0064] FIG10 is a schematic structural diagram of an automobile event data recording device applied to a data recording end according to an embodiment of the present application. DETAILED DESCRIPTION

[0065] The following describes embodiments of the present application in more detail with reference to the accompanying drawings. Although the accompanying drawings illustrate embodiments of the present application, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. Rather, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0066] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0067] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0068] Refer to Figure 1, which is a schematic diagram of the structure of a car event data recording device in the hardware operating environment involved in an embodiment of the present application.

[0069] As shown in FIG1 , the automobile event data recording device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to implement communication between these components. The user interface 1003 may include a display screen and an input unit such as a keyboard. Optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a wireless fidelity (Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as a disk storage device. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0070] Those skilled in the art will appreciate that the structure shown in FIG. 1 does not limit the automobile event data recording device, and may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0071] As shown in FIG. 1 , the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a vehicle event data recording program.

[0072] In the automobile event data recording device shown in Figure 1, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the automobile event data recording device of the present application can be set in the automobile event data recording device, and the automobile event data recording device calls the automobile event data recording program stored in the memory 1005 through the processor 1001, and executes the automobile event data recording method provided in the embodiment of the present application.

[0073] This embodiment of the present application provides a method for recording automobile event data. Referring to FIG. 2 , FIG. 2 is a flow chart illustrating a method for recording automobile event data applied to an event recording terminal according to an embodiment of the present application. The method is applied to the event recording terminal and includes:

[0074] Step S10: When a vehicle collision event is identified, collision event information and storage synchronization strategy information are sent to a data recording end, so that the data recording end stores a first data set in a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information.

[0075] It should be noted that the event recording end can be an EDR (Event Data Recorder) device. The automobile event data recording system includes an event recording end and a data recording end. The data recording end can be a central gateway or another ECU (electronic control unit) controller with data recording capabilities, such as a TBOX (Telematics Box). As shown in Figure 3, Figure 3 is a schematic structural diagram of the automobile event data recording system. The automobile event data recording system includes an event recording end and a data recording end. The central gateway is connected to the OBD interface (On-Board Diagnostics) in the automobile system via a CAN bus. The central gateway is equipped with multiple non-volatile storage areas, and the EDR device is equipped with multiple non-volatile storage areas. The storage areas of the central gateway and the storage areas of the EDR device correspond one-to-one. The central gateway and EDR device are connected through the CAN bus and hard wires. The central gateway is also connected to the ECU controllers of the vehicle through the CAN bus, such as EPS (Electric Power Steering, electric power steering system), ESP (Electronic Stability Program, electronic body stability system), VCU (Vehicle Control Unit, vehicle controller), etc.

[0076] In a specific implementation, the EDR device can identify whether a vehicle has been involved in a collision event. When a collision occurs, it immediately sends the collision event information and storage synchronization strategy information to the data recording end, i.e., the central gateway, via the CAN bus. This allows the central gateway to store a first data set in the first non-volatile storage area at the target time based on the collision event information and storage synchronization strategy information. The first data set represents vehicle data, including pre-collision data, collision data, and post-collision data. The first data set is an extended element data set that can be customized by automobile manufacturers. The first non-volatile storage area is located inside the data recording end and can be a hard disk drive, solid-state drive, programmable read-only memory (EPROM), and erasable programmable read-only memory (EEPROM).

[0077] Optionally, if no collision event occurs, the EDR device may also periodically send data or information to the data recording end, so as to determine whether the vehicle is abnormal through the data recording end. Before step S10, it may also include: sending the storage matching attribute value of the second non-volatile storage area to the data recording end through the CAN bus at a preset period, so that the data recording end performs matching based on the storage matching attribute value to determine whether a collision event occurs in the vehicle.

[0078] In a specific implementation, the preset period can be set based on demand or the memory size of the non-volatile storage area, for example, every 20ms or 25ms, etc., which is not limited in this embodiment. The EDR device periodically transmits the storage matching attribute value of the second non-volatile storage area via the CAN bus. The second non-volatile storage area is located within the EDR device and can be a programmable read-only memory (EPROM) or an erasable programmable read-only memory (EEPROM). The first and second non-volatile storage areas have the same number of storage blocks and both define data matching identification attributes. Therefore, the storage matching attribute value of the second non-volatile storage area can be sent to the data recording end. The data recording end can match the storage matching attribute value of the second non-volatile storage area with the matching attribute value of its own storage area. If the match is consistent, it is considered that no EDR collision event has occurred on the EDR device. If the match is inconsistent, it is considered that an EDR collision event has occurred on the EDR device, and corresponding processing can be performed, such as updating and backing up the data.

[0079] Step S20: At the target moment, a second data set is stored in a second non-volatile storage area, wherein the second data set represents vehicle collision event record data, and the first data set represents vehicle data.

[0080] It should be noted that while the data recording end stores the first data set in the first non-volatile storage area at the target time based on the collision event information and the storage synchronization strategy information, the EDR device also needs to store the second data set in the second non-volatile storage area. The first data set and the second data set are both defined sets of data elements. The second data set is the car collision event record data when a collision event occurs. The second data set is the minimum data set defined in the regulatory standards. The first data set is stored in the first non-volatile storage area, and the first non-volatile storage area matches the second non-volatile storage area one-to-one, that is, the data area where the central gateway stores the collision event each time is determined by the storage matching attribute value sent by the EDR device. The second data set may be a subset of the first data set.

[0081] Step S30: In response to the diagnostic read instruction sent by the data recording end, the automobile event record data in the second data set is sent to the data recording end, so that the data recording end performs event diagnosis and records the automobile collision event record data according to the diagnosis result.

[0082] It is understood that after storing the first and second data sets, a diagnostic read instruction can be sent to the event recording end at intervals, for example, a diagnosis can be performed at the target time + 50ms. The data recording end actively acts as the diagnostic party and sends a diagnostic read instruction to the event recording end. After the event recording end receives the diagnostic read instruction, it responds to the diagnostic read instruction sent by the data recording end and sends the vehicle event record data in the second data set to the data recording end. The diagnostic read instruction can be 22FA 13. When the EDR device receives 22FA 13, it sends the vehicle event record data to the data recording end.

[0083] The data recording terminal can read the most recent automobile event record data, diagnose the automobile event record data, and obtain the diagnosis result. According to the diagnosis result, the automobile collision event record data is recorded, such as storing the corresponding data, etc., to realize data backup.

[0084] The automobile event data recording method of this embodiment is applied to an event recording end. When a vehicle collision event is identified, collision event information and storage synchronization strategy information are sent to the data recording end, so that the data recording end stores a first data set in a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information; at the target time, a second data set is stored in a second non-volatile storage area, the second data set represents automobile collision event recording data, and the first data set represents automobile data; in response to a diagnostic read instruction sent by the data recording end, the automobile event recording data in the second data set is sent to the data recording end, so that the data recording end performs event diagnosis, and records automobile collision event recording data according to the diagnosis result. After the collision event occurs, the data recording end first completes the data recording, and then the data recording end reads the diagnostic instruction and saves the record again, thereby realizing the backup of event data, and can quickly and conveniently update the collision event data, avoiding the problem of collision event data loss after the data recording end is damaged.

[0085] As shown in FIG4 , FIG4 is another flow chart of a method for recording automobile event data applied to an event recording terminal. The method is applied to an event recording terminal, and step S10 of the method for recording automobile event data may include:

[0086] Step S101: When a vehicle collision event is identified, collision event information is sent to a data recording terminal.

[0087] It should be noted that when the EDR device identifies a vehicle collision event, it can generate collision event information and send the collision event information to the data recording end.

[0088] Step S102: sending the storage matching attribute value of the second non-volatile storage area via the CAN bus.

[0089] Since a collision event occurs in the EDR device, data loss may occur. Therefore, the storage matching attribute value of the second non-volatile storage area can be sent to the data recording end via the CAN bus. For example, if the second non-volatile storage area includes storage area 1, storage area 2, and storage area 3, the storage matching attribute value of storage area 1 or the storage matching attribute values ​​of storage area 1 and storage area 2 can be sent. This embodiment does not limit this.

[0090] Step S103: sending the storage matching attribute value as storage synchronization policy information to the data recording end.

[0091] In a specific implementation, the storage matching attribute value can be sent to the data recording end as storage synchronization policy information, so that the data recording end matches the storage matching attribute value of the EDR device storage area with the storage matching attribute value of its own storage area. If the match is inconsistent, data storage is required.

[0092] As an implementation method, before recording vehicle event data, the data recording terminal will also proactively collect and cache vehicle data for a certain period of time. The specific period can be set according to needs. The data recording terminal can collect vehicle data through the data acquisition module, thereby collecting vehicle data in advance to avoid lack of available data when an accident occurs. The data acquisition module may include a CAN / ETH bus, etc.

[0093] When this embodiment identifies a vehicle collision event, it sends collision event information to the data recording end; sends the storage matching attribute value of the second non-volatile storage area via the CAN bus; and sends the storage matching attribute value as storage synchronization strategy information to the data recording end. Data matching can be performed through the storage matching attribute value, which facilitates the recording and storage of the same event and improves data security.

[0094] Accordingly, Figure 5 shows a flow chart of a method for recording automobile event data applied to a data recording terminal according to an embodiment of the present application. Referring to Figure 5 , the method is applied to the data recording terminal and includes: Step S11: receiving collision event information sent by the event recording terminal and storing synchronization strategy information.

[0095] It should be noted that the data recording end can be a central gateway, which can collect CAN (Controller Area Network) / LIN (Local Interconnect Network) data of each vehicle controller in real time and store vehicle data within a certain period of time in real time.

[0096] In a specific implementation, the storage synchronization policy information includes storage matching attribute values ​​of each region.

[0097] Step S12: storing the first data set into a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information.

[0098] It should be understood that after receiving the collision information, the data in the first data set can be stored in the corresponding storage area of ​​the first non-volatile storage area by storing the matching attribute value in the synchronization strategy information. In this way, the defined vehicle data element set is stored in each storage block of the first non-volatile storage area.

[0099] This embodiment receives collision event information and storage synchronization strategy information sent by the event recording end; based on the collision event information and the storage synchronization strategy information, the first data set is stored in the corresponding storage area of ​​the first non-volatile storage area, and data can be quickly stored according to the received collision information and storage synchronization strategy information, thereby avoiding the problem of collision event data loss after the EDR device is damaged.

[0100] As shown in Figure 6, Figure 6 is another flow chart of the method for recording automobile event data applied to the data recording end. The method is applied to the data recording end, and step S12 of the method for recording automobile event data may include:

[0101] Step S121: obtaining a storage matching attribute value of the second non-volatile storage area according to the storage synchronization policy information.

[0102] It should be noted that the storage matching attribute value of the second non-volatile storage area can be obtained by storing synchronization strategy information, as shown in Table 1 below. Table 1 is a data matching strategy table for the event recording end and the data recording end.

[0103] Table 1

[0104] In a specific implementation, the storage areas in the data recording end and the event recording end correspond one to one, for example, both include storage area 1, storage area 2 and storage area 3. The event recording end is used to store the second data set, and the data recording end is used to store the first data set and the second data set. The storage area matching value includes the attribute value (Storing signal) and locking status (Locking status) of the storage sequence number. For example, in storage area 1, the attribute value of the storage sequence number of the event recording end is EDRRecordCnt1, and the locking status is EDRRecordLockSt1. The attribute value of the storage sequence number of the data recording end is GWRecordCnt1, and the locking status is GWRecordLockSt1.

[0105] Step S122: Match the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area.

[0106] In a specific implementation, the storage matching attribute value of the second non-volatile storage area can be matched with the storage matching attribute value of the first non-volatile storage area to determine whether they are consistent. The matching process may include: obtaining the attribute value and the second locking state of the second storage sequence number of the data recording end based on the storage matching attribute value of the second non-volatile storage area; querying the corresponding attribute value and the first locking state of the first storage sequence number in the first non-volatile storage area according to the second storage sequence number of the data recording end; matching the attribute value and the first locking state of the first storage sequence number with the attribute value and the second locking state of the second storage sequence number.

[0107] It should be noted that the attribute value and second lock state of the second storage sequence number of the data recording end can be obtained based on the storage matching attribute value of the second non-volatile storage area. For example, if the storage sequence number is 1, the storage area is storage area 1, the attribute value of storage area 1 is EDRRecordCnt1=10, and the second lock state is EDRRecordLockSt1=Not Active. When a collision event occurs, the event recording end immediately sends the attribute value of the second storage sequence number as EDRRecordCnt1==11 and the second lock state is EDRRecordLockSt1==Active via the CAN bus. After receiving the attribute value and second lock state of the second storage sequence number, the data recording end can query the attribute value and lock state of its own storage area based on the second storage sequence number, namely, the attribute value and first lock state of the first storage sequence number in storage area 1. The attribute value and first lock state of the first storage sequence number are then compared with the attribute value and second lock state of the second storage sequence number, thereby achieving a storage matching attribute value matching process.

[0108] Step S123: When the storage matching attribute value of the second non-volatile storage area is inconsistent with the storage matching attribute value of the first non-volatile storage area, the first data set is stored in the corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area, and the number of storage areas of the first non-volatile storage area and the second non-volatile storage area are the same and match one to one.

[0109] In a specific implementation, if the attribute value of the second storage sequence number in the storage matching attribute value of the second non-volatile storage area is inconsistent with the attribute value of the first storage sequence number of the first non-volatile storage area, and the second lock state in the storage matching attribute value of the second non-volatile storage area is inconsistent with the first lock state in the first non-volatile storage area, then it is recognized that a jump has occurred in the corresponding storage area, and it is determined that a collision event has occurred at the event recording end. Then, according to the storage sequence number in the storage matching attribute value of the second non-volatile storage area, the first data set is stored in the storage area of ​​the corresponding storage sequence number in the first non-volatile storage area. The first non-volatile storage area and the second non-volatile storage area have the same number of storage areas and are one-to-one matched. For example, the first non-volatile storage area includes storage area 1, storage area 2, and storage area 3, and the second non-volatile storage area also includes storage area 1, storage area 2, and storage area 3. Storage area 1 in the first non-volatile storage area corresponds to storage area 1 in the second non-volatile storage area. Similarly, storage area 2 and storage area 3 are also one-to-one matched.

[0110] Furthermore, the step of storing the first data set in the corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area includes: determining the target storage area in the first non-volatile storage area according to the second storage sequence number; storing the first data set in the target storage area, and marking the target area as a latched state based on the second locking state.

[0111] It should be noted that the target storage area in the first non-volatile storage area can be determined based on the second storage sequence number. For example, if the second storage sequence number is 1, the target storage area is storage area 1. The first data set can be stored in storage area 1 in the first non-volatile storage area, and based on the second locking state, the locking state is determined to be not allowed to be overwritten, and the storage area 1 is marked as a locked state (not allowed to be overwritten).

[0112] This embodiment obtains a storage matching attribute value of the second non-volatile storage area according to the storage synchronization policy information; matches the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area; when the storage matching attribute value of the second non-volatile storage area is inconsistent with the storage matching attribute value of the first non-volatile storage area, stores the first data set in the corresponding storage area of ​​the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area. The number of storage areas of the first non-volatile storage area and the second non-volatile storage area are the same and are matched one to one. Matching and identification can be performed through the storage matching attribute value to quickly determine whether the storage area of ​​the event recording end has jumped, thereby performing data storage and improving data backup efficiency.

[0113] As shown in FIG7 , FIG7 is another flow chart of a method for recording automobile event data applied to a data recording terminal. The method is applied to a data recording terminal, and the method for recording automobile event data further includes:

[0114] Step S40: initiating a diagnosis reading instruction to the event recording end, so that the event recording end sends the automobile event recording data in the second data set based on the diagnosis reading instruction.

[0115] It should be understood that after storing the data set, the data recording end actively acts as the diagnostic party and initiates a diagnostic read instruction, such as 22FA 13 to the event recording end, so that the event recording end sends the vehicle event record data to the data recording end based on the diagnostic read instruction.

[0116] Step S50: receiving and reading the automobile event record data sent by the event record terminal.

[0117] In a specific implementation, after receiving the automobile event record data, data diagnosis may be performed on the automobile event record data to determine whether the data needs to be saved again.

[0118] Step S60: Determine the response information of the event recording end.

[0119] It should be noted that the response information fed back by the event recording end can be obtained for diagnosis. The response information of the event recording end includes positive response and negative response.

[0120] Optionally, when the response information is a negative response, the diagnostic read instruction is re-initiated to the event recording end, and the initiation of the diagnostic read instruction is returned to the event recording end, so that the event recording end sends the automobile event recording data in the second data set based on the diagnostic read instruction.

[0121] It should be noted that the number of times the diagnostic read instruction is initiated can be defined, for example 10 times, 15 times, etc., so that when the response information is a negative response, the diagnostic read instruction is re-initiated to the event recording end, so that the event recording end sends the automobile event record data in the second data set to the data recording end based on the diagnostic read instruction.

[0122] Step S70: When the response information is a positive response, the collision event record data in the automobile event record data is stored in a corresponding storage area in the first non-volatile storage area.

[0123] When the response information is a positive response, the collision event record data in the automobile event record data is stored in the corresponding storage area in the first non-volatile storage area, so that after the collision event occurs, the data of the event recording end is backed up to the data recording end in time to avoid the problem of loss of collision event data due to damage to the event recording end.

[0124] As shown in Figure 8, Figure 8 is an overall flow chart of the automobile event data recording method, including: Step S01: the central gateway caches the entire vehicle data within a certain period of time in real time; Step S02: at time T0, the EDR device recognizes the collision, and immediately notifies the central gateway of the collision event and storage synchronization strategy information; Step S03: at time T1, the EDR device records the second data set in the non-volatile storage area; the central gateway records the first data set in the non-volatile storage area of ​​the gateway according to the EDR device storage synchronization strategy information; Step S04: at time T2, the central gateway, as the diagnostic party, initiates a diagnosis to read the data elements recorded by the EDR device; Step S05: at time T3, the central gateway records the data returned by the EDR device diagnosis in the non-volatile storage area corresponding to time T1.

[0125] This embodiment initiates a diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event record data in the second data set based on the diagnostic read instruction; receives and reads the automobile event record data sent by the event recording end; determines the response information of the event recording end; when the response information is a positive response, stores the collision event record data in the automobile event record data to the corresponding storage area in the first non-volatile storage area, and after the collision event occurs, backs up the data of the event recording end to the data recording end in time to avoid the problem of loss of collision event data due to damage to the event recording end.

[0126] 9, FIG9 is a schematic diagram of the structure of an automobile event data recording device 100 applied to an event recording terminal according to an embodiment of the present application. The device 100 includes:

[0127] The identification module 110 is used to send collision event information and storage synchronization strategy information to the data recording end when a vehicle collision event is identified, so that the data recording end stores the first data set in the first non-volatile storage area at the target time according to the collision event information and the storage synchronization strategy information.

[0128] The second storage module 120 is configured to store a second data set in a second non-volatile storage area at the target moment, wherein the second data set represents vehicle collision event record data, and the first data set represents vehicle data.

[0129] The sending module 130 is used to send the automobile event record data in the second data set to the data recording end in response to the diagnostic read instruction sent by the data recording end, so that the data recording end performs event diagnosis and records the automobile collision event record data according to the diagnosis result.

[0130] This embodiment sends collision event information and storage synchronization strategy information to the data recording end when a vehicle collision event is identified, so that the data recording end stores a first data set in a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information; at the target time, stores a second data set in a second non-volatile storage area, the second data set representing the automobile collision event record data, and the first data set representing the automobile data; in response to a diagnostic read instruction sent by the data recording end, the automobile event record data in the second data set is sent to the data recording end, so that the data recording end performs event diagnosis, and records the automobile collision event record data according to the diagnosis result. After the collision event occurs, the data recording end first completes the data recording, and then the data recording end reads the diagnostic instruction for the record and saves it again, so that the collision event data can be updated quickly and conveniently, avoiding the problem of collision event data loss after the data recording end is damaged.

[0131] In an optional embodiment, the identification module 110 is further used to send collision event information to the data recording end when a vehicle collision event is identified; send the storage matching attribute value of the second non-volatile storage area through the CAN bus; and send the storage matching attribute value as storage synchronization strategy information to the data recording end.

[0132] In an optional embodiment, the identification module 110 is further configured to send the storage matching attribute value of the second non-volatile storage area to the data recording end via the CAN bus at a preset period, so that the data recording end performs matching based on the storage matching attribute value to determine whether a collision event occurs in the vehicle.

[0133] Accordingly, the embodiment of the present application further provides a vehicle event data recording device applied to a data recording terminal. Referring to FIG10 , the vehicle event data recording device 200 applied to a data recording terminal includes:

[0134] The receiving module 210 is configured to receive the collision event information sent by the event recording end and store the synchronization strategy information.

[0135] The first storage module 220 is configured to store the first data set in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information.

[0136] This embodiment receives collision event information and storage synchronization strategy information sent by the event recording end; based on the collision event information and the storage synchronization strategy information, the first data set is stored in the corresponding storage area in the first non-volatile storage area, and data can be quickly stored according to the received collision information and storage synchronization strategy information, avoiding the problem of collision event data loss after the EDR device is damaged.

[0137] In an optional embodiment, the first storage module 220 is further used to obtain a storage matching attribute value of the second non-volatile storage area based on the storage synchronization policy information; match the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area; when the storage matching attribute value of the second non-volatile storage area is inconsistent with the storage matching attribute value of the first non-volatile storage area, store the first data set in the corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area, and the number of storage areas of the first non-volatile storage area and the second non-volatile storage area are the same and matched one to one.

[0138] In an optional embodiment, the first storage module 220 is further used to obtain the attribute value and the second locking state of the second storage sequence number of the data recording end based on the storage matching attribute value of the second non-volatile storage area; query the corresponding attribute value and the first locking state of the first storage sequence number in the first non-volatile storage area according to the second storage sequence number of the data recording end; and match the attribute value and the first locking state of the first storage sequence number with the attribute value and the second locking state of the second storage sequence number.

[0139] In an optional embodiment, the first storage module 220 is further used to determine a target storage area in the first non-volatile storage area according to the second storage sequence number; store the first data set in the target storage area, and mark the target area as a latched state based on the second locking state.

[0140] In an optional embodiment, the first storage module 220 is further used to initiate a diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event record data in the second data set based on the diagnostic read instruction; receives and reads the automobile event record data sent by the event recording end; determines the response information of the event recording end; and when the response information is a positive response, stores the collision event record data in the automobile event record data to the corresponding storage area in the first non-volatile storage area.

[0141] In an optional embodiment, the first storage module 220 is also used to re-initiate a diagnostic read instruction to the event recording end when the response information is a negative response, and return the initiated diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event recording data in the second data set based on the diagnostic read instruction.

[0142] In addition, an embodiment of the present application further proposes a storage medium, on which a car event data recording program is stored. When the car event data recording program is executed by a processor, the steps of the car event data recording method described above are implemented.

[0143] Since the storage medium adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought by the technical solutions of the above embodiments, which will not be described one by one here.

[0144] In addition, to achieve the above-mentioned purpose, the present application also proposes an automobile event data recording system, the automobile event data recording system comprising an event recording end and a data recording end, the event recording end and the data recording end being connected via a CAN bus, the data recording end comprising a plurality of first non-volatile storage areas, and the event recording end comprising a plurality of second non-volatile storage areas;

[0145] The event recording end is used to send collision event information and storage synchronization strategy information to the data recording end when a collision event of the vehicle is identified, and store the second data set in the plurality of second non-volatile storage areas at a target time;

[0146] The data recording end is used to store the first data set in the plurality of first non-volatile storage areas at a target time according to the collision event information and the storage synchronization strategy information.

[0147] Since the automobile event data recording system adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought by the technical solutions of the above embodiments, which will not be described one by one here.

[0148] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle, which includes an electric power steering system, a vehicle controller, an electronic stability system, a diagnostic system and the automobile event data recording system mentioned above, and the electric power steering system, the vehicle controller, the electronic stability system and the diagnostic system are respectively connected to the data recording end of the automobile event data recording system through a CAN bus.

[0149] It should be understood that the above is only an example and does not constitute any limitation to the technical solution of the present application. In specific applications, technicians in this field can make settings as needed, and the present application does not impose any restrictions on this.

[0150] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this application. In actual applications, technicians in this field can select part or all of it according to actual needs to achieve the purpose of this embodiment scheme, and no restrictions are imposed here.

[0151] In addition, for technical details not fully described in this embodiment, please refer to the automobile event data recording method provided in any embodiment of the present application, and will not be repeated here.

[0152] In addition, it should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0153] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0154] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product, which is stored in a storage medium (such as read-only memory (ROM) / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0155] The embodiments of the present application have been described above. The above description is illustrative and not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or improvements to the technology in the market, or to enable other persons skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for recording automobile event data, characterized in that: The automobile event data recording method is applied to an event recording end, and the method comprises: When a collision event of the vehicle is identified, the collision event information and the storage synchronization strategy information are sent to the data recording end, so that the data recording end stores the first data set in the first non-volatile storage area at the target time according to the collision event information and the storage synchronization strategy information; At the target time, storing a second data set in a second non-volatile storage area, wherein the second data set represents vehicle collision event record data, and the first data set represents vehicle data; In response to the diagnostic read instruction sent by the data recording end, the automobile event record data in the second data set is sent to the data recording end, so that the data recording end performs event diagnosis and records the automobile collision event record data according to the diagnosis result.

2. The automobile event data recording method according to claim 1, characterized in that: When a collision event is identified, sending the collision event information and storing the synchronization strategy information to the data recording end includes: When a vehicle collision event is identified, the collision event information is sent to the data recording end; Sending the storage matching attribute value of the second non-volatile storage area via the CAN bus; The storage matching attribute value is sent to the data recording end as storage synchronization strategy information.

3. The automobile event data recording method according to claim 1, characterized in that: The method further includes: before sending the collision event information and storing the synchronization strategy information to the data recording end when a collision event of the vehicle is identified, the method further includes: The storage matching attribute value of the second non-volatile storage area is sent to the data recording end through the CAN bus at a preset period, so that the data recording end performs matching based on the storage matching attribute value to determine whether a collision event occurs in the vehicle.

4. A method for recording automobile event data, characterized in that: The automobile event data recording method is applied to a data recording end, and the method comprises: Receive collision event information sent by the event recording end and store synchronization strategy information; Based on the collision event information and the storage synchronization strategy information, the first data set is stored in a corresponding storage area in the first non-volatile storage area.

5. The automobile event data recording method according to claim 4, characterized in that: The storing the first data set into a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information includes: Obtaining a storage matching attribute value of a second non-volatile storage area according to the storage synchronization strategy information; matching the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area; When the storage matching attribute value of the second non-volatile storage area is inconsistent with the storage matching attribute value of the first non-volatile storage area, the first data set is stored in the corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area, and the number of storage areas in the first non-volatile storage area and the second non-volatile storage area are the same and match one by one.

6. The automobile event data recording method according to claim 5, characterized in that: The matching of the storage matching attribute value of the second non-volatile storage area with the storage matching attribute value of the first non-volatile storage area includes: Obtaining the attribute value of the second storage sequence number and the second locking state of the data recording end based on the storage matching attribute value of the second non-volatile storage area; querying the first non-volatile storage area for the attribute value and the first locking state of the corresponding first storage sequence number according to the second storage sequence number of the data recording end; The attribute value of the first storage sequence number and the first locking state are matched with the attribute value of the second storage sequence number and the second locking state.

7. The automobile event data recording method according to claim 6, characterized in that: The storing the first data set into a corresponding storage area in the first non-volatile storage area according to the storage matching attribute value of the second non-volatile storage area comprises: determining a target storage area in the first non-volatile storage area according to the second storage sequence number; A first data set is stored in the target storage area, and the target area is marked as a locked state based on the second locking state.

8. The automobile event data recording method according to claim 4, characterized in that: After storing the first data set in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information, the method further includes: Initiating a diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event record data in the second data set based on the diagnostic read instruction; Receiving and reading the automobile event record data sent by the event record terminal; Determining response information of the event recording end; When the response information is a positive response, the collision event record data in the automobile event record data is stored in a corresponding storage area in the first non-volatile storage area.

9. The automobile event data recording method according to claim 8, characterized in that: After determining the response information of the event recording end, the method further includes: When the response information is a negative response, the step of re-initiating a diagnostic read instruction to the event recording end, and returning the initiated diagnostic read instruction to the event recording end, so that the event recording end sends the automobile event recording data in the second data set based on the diagnostic read instruction.

10. An automobile event data recording device, characterized in that: Applied to the event recording end, the automobile event data recording device comprises: an identification module, configured to send collision event information and storage synchronization strategy information to a data recording end when a collision event of a vehicle is identified, so that the data recording end stores a first data set in a first non-volatile storage area at a target time according to the collision event information and the storage synchronization strategy information; A second storage module is used to store a second data set in a second non-volatile storage area at the target time, wherein the second data set represents vehicle collision event record data and the first data set represents vehicle data; The sending module is used to respond to the diagnostic reading instruction sent by the data recording end, send the automobile event record data in the second data set to the data recording end, so that the data recording end performs event diagnosis and records the automobile collision event record data according to the diagnosis result.

11. An automobile event data recording device, characterized in that: Applied to the data recording end, the automobile event data recording device comprises: A receiving module, used for receiving collision event information sent by the event recording end and storing synchronization strategy information; The first storage module is used to store the first data set in a corresponding storage area in the first non-volatile storage area based on the collision event information and the storage synchronization strategy information.

12. An automobile event data recording system, characterized in that: The automobile event data recording system comprises an event recording end and a data recording end, wherein the event recording end and the data recording end are connected via a CAN bus, the data recording end comprises a plurality of first non-volatile storage areas, and the event recording end comprises a plurality of second non-volatile storage areas; The event recording end is used to send collision event information and storage synchronization strategy information to the data recording end when a collision event of the vehicle is identified, and store a second data set in a plurality of the second non-volatile storage areas at a target time, wherein the second data set represents the automobile collision event record data; The data recording end is used to store a first data set to a plurality of the first non-volatile storage areas at a target time according to the collision event information and the storage synchronization strategy information, wherein the first data set represents vehicle data.

13. A vehicle, characterized in that: The vehicle includes an electric power steering system, a vehicle controller, an electronic stability system, a diagnostic system and the automobile event data recording system as described in claim 12. The electric power steering system, the vehicle controller, the electronic stability system and the diagnostic system are respectively connected to the data recording end of the automobile event data recording system through a CAN bus.

14. An automobile event data recording device, characterized in that: The automobile event data recording device comprises: a memory, a processor, and an automobile event data recording program stored in the memory and operable on the processor. The automobile event data recording program is configured to implement the application for event recording as claimed in any one of claims 1 to 3. A method for recording automobile event data at a data recording end or steps for implementing the method for recording automobile event data applied to a data recording end as described in any one of claims 4 to 9.

15. A storage medium, characterized in that: The storage medium stores an automobile event data recording program, which, when executed by a processor, implements the automobile event data recording method applied to the event recording end as described in any one of claims 1 to 3 or implements the steps of the automobile event data recording method applied to the data recording end as described in any one of claims 4 to 9.

Images