Vehicle-mounted event data record testing method and device

Abstract

The invention provides a method and a device for testing vehicle-mounted event data records. The method comprises the following steps that: a signal simulation system obtains field values of a plurality of fields recorded by vehicle-mounted event data, generates scene simulation data based on the plurality of field values, and transmits the scene simulation data to a signal reporting system; the signal reporting system uploads the scene simulation data to an Internet of Vehicles platform; the analysis system obtains a pull value of the scene simulation data from the Internet of Vehicles platform, and obtains an expected value of the scene simulation data from the signal simulation system; and comparing the expected value with the pull value to generate a comparison report. In the mode, all-around test support can be provided for research and development improvement, type authentication and quality control of the EDR product, the reliability and data recording quality of the EDR product can be improved, and a more reliable data basis is provided for automobile safety accident analysis and responsibility confirmation.

Description

Technical Field

[0001] This invention relates to the field of automotive safety testing technology, and in particular to a testing method and apparatus for recording vehicle event data. Background Technology

[0002] The onboard event data recorder (EDR) can record vehicle operating status information and driver operation information before and after a collision or other specific event, which is of great significance for accident analysis, liability determination, and vehicle safety improvement. EDR needs to record numerous fields, including vehicle motion parameters (such as longitudinal velocity change delta-V, lateral acceleration, etc.), driver operation parameters (such as brake pedal position, accelerator pedal position, etc.), safety system status (such as seat belt status, airbag deployment time, etc.), and system information (such as ECU (Electronic Control Unit) number, vehicle identification number, etc.). Developing an automated tool can comprehensively cover field verification and improve testing efficiency.

[0003] Existing EDR testing methods mainly suffer from the following shortcomings: (1) The test coverage is not comprehensive, often focusing on some parameters related to collision, while ignoring the testing of multiple fields such as system status and driver operation; (2) Lack of validation of the logical relationships between fields makes it impossible to detect abnormal data records caused by logical errors; (3) The test scenario is too simple, making it difficult to verify the recording performance of EDR in various complex driving events.

[0004] Therefore, a testing system and method are needed that can comprehensively cover all record fields of EDR, verify the logical relationships between fields, adapt to various test scenarios, and have high-precision synchronization capabilities. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a testing method and apparatus for vehicle event data recording, so as to solve the problems of incomplete coverage of EDR test fields, missing logic verification, and limited scenarios in the prior art.

[0006] In a first aspect, embodiments of the present invention provide a testing method for vehicle-mounted event data recording. The method includes: a signal simulation system acquiring field values ​​of multiple fields of the vehicle-mounted event data recording, generating scenario simulation data based on the multiple field values, and transmitting the scenario simulation data to a signal reporting system; the signal reporting system uploading the scenario simulation data to a vehicle-to-everything (V2X) platform; an analysis system acquiring retrieved values ​​of the scenario simulation data from the V2X platform and acquiring expected values ​​of the scenario simulation data from the signal simulation system; and comparing the expected values ​​and retrieved values ​​to generate a comparison report.

[0007] In an optional embodiment of this application, the development tool design interface of the above-mentioned signal simulation system is pre-configured with multiple field management units; the step of the signal simulation system obtaining the field values ​​of multiple fields of the vehicle event data record includes: the signal simulation system obtaining the field values ​​input or selected by the user in the multiple field management units.

[0008] In an optional embodiment of this application, after the step of obtaining the field value input or selected by the user in multiple field management units, the method further includes: if the user does not input or select a field value in the field management unit, the signal simulation system determines the field value based on the number of bytes occupied by the field in the field management unit.

[0009] In an optional embodiment of this application, the step of generating scenario simulation data based on multiple field values ​​includes: the signal simulation system converting multiple field values ​​into hexadecimal data, assembling the hexadecimal data into a byte string based on the requirements of the fields in the preset signal document, and using the byte string as scenario simulation data.

[0010] In an optional embodiment of this application, the step of the signal reporting system uploading scenario simulation data to the vehicle network platform includes: the signal reporting system encrypting and encapsulating a byte string into a vehicle event data recording message using hash encryption; the signal reporting system encapsulating multiple specified fields in the byte string into a login message; the signal reporting system uploading the login message to the vehicle network platform via message queue telemetry transmission; and if the login message is successfully uploaded, the signal reporting system uploading the vehicle event data recording message to the vehicle network platform.

[0011] In optional embodiments of this application, after the above-mentioned signal reporting system uploads the login message to the vehicle network platform via message queue telemetry transmission, the method further includes: if the login message upload fails, the signal reporting system transmits the login message upload failure error information to the analysis system; after the above-mentioned signal reporting system uploads the vehicle event data recording message to the vehicle network platform, the method further includes: if the vehicle event data recording message upload fails, the signal reporting system transmits the vehicle event data recording message upload failure error information to the analysis system.

[0012] In an optional embodiment of this application, the step of the signal reporting system uploading vehicle event data recording messages to the vehicle network platform includes: the signal reporting system pushing vehicle event data recording messages to the cluster in an asynchronous sending mode so that the cluster can distribute and store the vehicle event data recording messages; and the vehicle network platform subscribing to vehicle event data recording messages from the cluster.

[0013] In optional embodiments of this application, the above method further includes: the vehicle networking platform determining the pull value based on the scenario simulation data and displaying the pull value on the page; and the signal simulation system determining the expected value based on the scenario simulation data.

[0014] In an optional embodiment of this application, the step of the analysis system comparing the expected value and the retrieved value to generate a comparison report includes: the analysis system performing field-level comparison and overall comparison on the expected value and the retrieved value; wherein the field-level comparison includes: numerical field comparison, time-based field comparison, and status or identifier-based field comparison, and the overall comparison characterizes the overall pass rate of the expected value and the retrieved value; the analysis system generates a comparison report based on the results of the field-level comparison and the overall comparison; wherein the comparison report includes: full results, abnormal data, and data index.

[0015] Secondly, embodiments of the present invention also provide a testing device for recording vehicle event data. The device includes: a scenario simulation data generation module, used by a signal simulation system to obtain field values ​​of multiple fields of the vehicle event data record, generate scenario simulation data based on the multiple field values, and transmit the scenario simulation data to a signal reporting system; a scenario simulation data uploading module, used by the signal reporting system to upload the scenario simulation data to a vehicle networking platform; and a scenario simulation data comparison module, used to analyze the retrieved values ​​of the scenario simulation data obtained by the system from the vehicle networking platform and obtain the expected values ​​of the scenario simulation data from the signal simulation system; compare the expected values ​​and the retrieved values ​​to generate a comparison report.

[0016] The embodiments of the present invention bring the following beneficial effects: This invention provides a testing method and apparatus for vehicle-mounted event data recording. A signal simulation system acquires field values ​​from multiple fields of the vehicle-mounted event data record, generates scenario simulation data based on these values, and transmits the scenario simulation data to a signal reporting system. The signal reporting system uploads the scenario simulation data to a vehicle-to-everything (V2X) platform. An analysis system retrieves the pulled values ​​of the scenario simulation data from the V2X platform and obtains the expected values ​​of the scenario simulation data from the signal simulation system. The expected values ​​and pulled values ​​are compared to generate a comparison report. This method provides comprehensive testing support for the research and development, type certification, and quality control of EDR products, helping to improve the reliability and data recording quality of EDR products and providing more reliable data for automotive safety accident analysis and liability determination.

[0017] Other features and advantages of this disclosure will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the techniques described above.

[0018] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0019] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0020] Figure 1 A flowchart illustrating a testing method for recording vehicle-mounted event data, provided as an embodiment of the present invention; Figure 2 A flowchart of another test method for recording vehicle event data provided in an embodiment of the present invention; Figure 3 A schematic diagram of the system framework for a test method for recording vehicle event data provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of a test device for recording vehicle event data provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0022] Currently, existing EDR testing methods mainly suffer from the following shortcomings: (1) The test coverage is not comprehensive, often focusing on some parameters related to collision, while ignoring the testing of multiple fields such as system status and driver operation; (2) Lack of validation of the logical relationships between fields makes it impossible to detect abnormal data records caused by logical errors; (3) The test scenario is too simple, making it difficult to verify the recording performance of EDR in various complex driving events.

[0023] Based on this, the present invention provides a testing method and apparatus for vehicle event data recording, specifically providing a vehicle EDR data recording and verification testing system and method based on full field coverage, which can solve the problems of incomplete EDR test field coverage, missing logic verification, and single scenario in the prior art.

[0024] To facilitate understanding of this embodiment, a test method for recording vehicle event data disclosed in this embodiment of the invention will first be described in detail.

[0025] Example 1: This invention provides a testing method for recording vehicle event data. See [link to relevant documentation]. Figure 1 The flowchart shown illustrates a test method for vehicle-mounted event data recording, which includes the following steps: In step S102, the signal simulation system obtains the field values ​​of multiple fields from the vehicle event data record, generates scenario simulation data based on the multiple field values, and transmits the scenario simulation data to the signal reporting system.

[0026] In this embodiment, over 70 fields of EDR can be set in the interface of the signal simulation system. Each field has a default value, and users can also input or select field values. For example, the default value for vertical delta-V is FF, and users can also input numbers as field values. The signal simulation system can generate scenario simulation data based on the selected field values ​​of all EDR record fields in this scenario, which will serve as a reference standard for subsequent verification.

[0027] In step S104, the signal reporting system uploads the scene simulation data to the vehicle network platform.

[0028] In this embodiment, the signal reporting system can receive the scene simulation data output by the signal simulation system and upload the scene simulation data to the vehicle network platform, such as NTSP (Network Telematics Service Platform).

[0029] Step S106: The analysis system obtains the retrieved values ​​of the scenario simulation data from the vehicle network platform and the expected values ​​of the scenario simulation data from the signal simulation system; the expected values ​​and the retrieved values ​​are compared to generate a comparison report.

[0030] In this embodiment, the system can obtain the retrieved values ​​of the scenario simulation data from the vehicle-to-everything (V2X) platform and the expected values ​​of the scenario simulation data from the signal simulation system, and then compare the expected values ​​with the retrieved values. If the expected values ​​and retrieved values ​​match, the comparison passes; otherwise, the comparison fails. The system can also record the expected values, retrieved values, and comparison results, and output a comparison report.

[0031] This invention provides a testing method for vehicle-mounted event data recording. A signal simulation system acquires the field values ​​of multiple fields from the vehicle-mounted event data record, generates scenario simulation data based on these values, and transmits the scenario simulation data to a signal reporting system. The signal reporting system then uploads the scenario simulation data to a vehicle-to-everything (V2X) platform. An analysis system retrieves the pulled values ​​of the scenario simulation data from the V2X platform and obtains the expected values ​​of the scenario simulation data from the signal simulation system. The expected values ​​and pulled values ​​are compared to generate a comparison report. This method provides comprehensive testing support for the research and development, type certification, and quality control of EDR products, helping to improve the reliability and data recording quality of EDR products and providing more reliable data for automotive safety accident analysis and liability determination.

[0032] Example 2: This invention provides another testing method for recording vehicle event data, implemented based on the above embodiments. See [link to relevant documentation]. Figure 2 The flowchart shown represents another test method for vehicle event data recording, which includes the following steps: In step S202, the signal simulation system obtains the field values ​​of multiple fields from the vehicle event data record, generates scenario simulation data based on the multiple field values, and transmits the scenario simulation data to the signal reporting system.

[0033] In some embodiments, the development tool design interface of the signal simulation system is pre-configured with multiple field management units; the signal simulation system obtains the field values ​​input or selected by the user in the multiple field management units.

[0034] In some embodiments, if the user does not input or select a field value in the field management unit, the signal simulation system determines the field value based on the number of bytes occupied by the field in the field management unit.

[0035] See also Figure 3 The diagram shows a system framework for a test method of vehicle-mounted event data recording. The signal simulation system can transmit scenario simulation data to the signal reporting system.

[0036] In this embodiment, the interface can be designed using development tools. According to the signal document fields, 70 field management units such as longitudinal delta-V, vehicle speed, and service braking (on or off) can be designed. Users can enter content and select content from drop-down menus under the field management units. If the user does not perform any operation, the number of bytes occupied by the field in the field management unit determines the field value as a default value and displays it on the interface.

[0037] In some embodiments, the signal simulation system converts multiple field values ​​into hexadecimal data, assembles the hexadecimal data into a byte string based on the requirements of the fields in the preset signal document, and uses the byte string as scenario simulation data.

[0038] In this embodiment, the user can click the button of the scene simulation data generation unit to obtain 70 field values ​​on the interface, convert them into hexadecimal data, and assemble them into a 771-byte string as scene simulation data according to the requirements of the fields in the signal document, and transmit it to the signal reporting system.

[0039] In step S204, the signal reporting system encrypts and encapsulates the byte string into a vehicle event data recording message using hash encryption; the signal reporting system encapsulates multiple specified fields in the byte string into a login message; the signal reporting system uploads the login message to the vehicle network platform via message queue telemetry transmission; if the login message is successfully uploaded, the signal reporting system uploads the vehicle event data recording message to the vehicle network platform.

[0040] like Figure 3 As shown, the signal reporting system can transmit scenario simulation data to the vehicle network platform.

[0041] In some embodiments, if the login message upload fails, the signal reporting system will transmit the error message of the login message upload failure to the analysis system; In some embodiments, if the vehicle event data recording message fails to upload, the signal reporting system transmits the error message of the failure to upload the vehicle event data recording message to the analysis system.

[0042] The signal reporting system can call the interface to cyclically encapsulate messages. Upon receiving 771 bytes, it encrypts and encapsulates them into EDR messages (i.e., vehicle event data record messages) using the hash (SHA-256) encryption algorithm. The signal reporting system can then encapsulate login messages based on the vin, iccid, and tboxsn fields in the 771 bytes.

[0043] Before sending messages, the signal reporting system can complete the format specification and serialization to ensure that it is compatible with the Kafka (publish-subscribe) transmission specification. The signal reporting system connects to MQTT (Message Queuing Telemetry Transport). If the connection is successful, the system will report the login message. If the connection fails, the system will send the information to the analysis system.

[0044] After the signal reporting system successfully reports the login message and receives a response, it reports an EDR message. If no response is received after reporting the login message, the system directly sends an error message to the analysis system. If the EDR message is successfully reported, the system calls the interface to listen for the next round of messages. If no response is received after reporting the EDR message, the system sends an error message to the analysis system and starts listening for the next round.

[0045] In some embodiments, the signal reporting system pushes vehicle event data recording messages to the cluster in an asynchronous sending mode, so that the cluster can distribute and store the vehicle event data recording messages; the vehicle networking platform subscribes to the vehicle event data recording messages from the cluster.

[0046] In this embodiment, the Kafka Producer of the signal reporting system pushes EDR messages to the cluster in an asynchronous sending mode. After receiving the EDR messages, the Kafka Broker (the broker of the Kafka cluster) cluster uses a distributed storage mechanism. The Kafka Consumer (the client of the Kafka cluster) of the vehicle networking platform subscribes to EDR messages from the cluster, processes them, and displays them on the vehicle networking platform's page.

[0047] Step S206: The analysis system obtains the pulled values ​​of the scenario simulation data from the vehicle network platform and the expected values ​​of the scenario simulation data from the signal simulation system; the expected values ​​and the pulled values ​​are compared to generate a comparison report.

[0048] In some embodiments, the vehicle-to-everything (V2X) platform determines the pull value based on scenario simulation data and displays the pull value on the page; the signal simulation system determines the expected value based on scenario simulation data.

[0049] like Figure 3 As shown, the signal simulation system can calculate the expected values ​​of scenario simulation data. For example, the signal simulation system parses 70 fields into their corresponding expected values ​​and transmits these expected values ​​to the analysis system.

[0050] like Figure 3 As shown, the vehicle networking platform can calculate and display the retrieved values ​​of the scenario simulation data on the page, and transmit the retrieved values ​​to the analysis system.

[0051] The analysis system in this embodiment can call the data retrieval interface of the vehicle network platform to obtain the information displayed on the page. The specific operation is as follows: (1) Construct pull parameters: Use message_id (unique identifier) ​​and vin (vehicle identification number) in the Kafka message as keywords to generate the interface request body of the vehicle network platform; (2) Data retrieval and retry: After sending the request, wait for the response. If the timeout (>30 seconds) occurs, automatically retry twice. If the retry fails, mark "Failed to retrieve data from the Internet of Vehicles platform" and trigger an alarm (such as an interface pop-up window + email notification). (3) Data retrieval and parsing: Map the JSON format data returned by the vehicle network platform to the EDR standard fields according to the field name (such as mapping "brake_state" in the vehicle network platform to "driving brake, on or off") to ensure field alignment.

[0052] In some embodiments, the analysis system performs field-level and overall-level comparisons between expected values ​​and retrieved values; wherein field-level comparisons include: numerical field comparisons, time-based field comparisons, and status or identifier-based field comparisons, and overall-level comparisons characterize the overall pass rate of expected values ​​and retrieved values; the analysis system generates a comparison report based on the results of field-level and overall-level comparisons; wherein the comparison report includes: full results, abnormal data, and data index.

[0053] The analysis system in this embodiment can perform field-level and overall-level comparisons between expected values ​​and retrieved values. The specific operations are as follows: (1) Field-level comparison: Traverse more than 70 fields and compare the "expected value" with the "pulled value" one by one: Numerical fields: Calculate the absolute error (|pulled value - expected value|) and the relative error (|pulled value - expected value| / expected value × 100%). If both are ≤ the preset threshold, mark "pass"; otherwise, mark "fail" and record the deviation value. Time field: Calculate the time difference (|retrieved timestamp - expected timestamp|), pass if ≤10ms; Status / identification fields (such as VIN, ECU number): Directly compare whether the strings match; if they match, the comparison is successful. (2) Overall comparison: count the number of "passed fields" and "failed fields", and calculate the overall pass rate (number of passed fields / total number of fields × 100%).

[0054] The analysis system in this embodiment can store the comparison results, and the specific operation is as follows: (1) Full result storage: Write information such as "message ID, task ID, field comparison details, and overall pass rate" into a relational database (such as MySQL) and associate it with the corresponding Kafka message raw data and pulled data; (2) Abnormal data marking: For data that does not pass the field, add labels (such as "numerical deviation exceeds the standard" or "data missing") and record the abnormal level (general / important / urgent, based on the field importance preset, such as airbag time deviation as "urgent"). (3) Data indexing: A composite index is established based on “task ID + message ID + exception tag” to facilitate quick querying and tracing in the future.

[0055] In the analysis system of this embodiment, users can click the "Generate Comparison Report" button to generate an analysis report. The analysis report may include "basic message information (message_id, vin)," "field comparison details table," "summary of abnormal fields," and "pass and fail" flags.

[0056] The method provided in the embodiments of the present invention has the following main advantages: 1. Full field coverage: This invention can comprehensively test more than 70 fields that need to be recorded in EDR, including vehicle motion parameters, driver operation parameters, safety system status and system information, to ensure the integrity of EDR records.

[0057] 2. Logical Relationship Validation: Innovatively introduces logical relationship validation between fields, which can discover logical errors that cannot be identified by simple numerical validation, and comprehensively evaluate the data record quality of EDR.

[0058] 3. Multi-scenario support: It has a rich library of standard test scenarios and supports custom scenarios, which can comprehensively verify the recording performance of EDR in various driving events and improve the comprehensiveness of the test.

[0059] 4. Automation: Enables full automation of the entire process from scenario configuration, signal generation, data acquisition to verification and analysis, significantly improving testing efficiency and accuracy and reducing manual intervention.

[0060] In summary, the methods provided by the embodiments of the present invention can provide comprehensive testing support for the research and development, type certification, and quality control of EDR products, which helps to improve the reliability of EDR products and the quality of data recording, and provides more reliable data for the analysis of automotive safety accidents and the determination of liability.

[0061] Example 3: Corresponding to the above method embodiments, this invention provides a testing device for recording vehicle event data. See [link to relevant documentation]. Figure 4 The diagram shows a structural schematic of a test device for recording vehicle-mounted event data. The test device includes: The scenario simulation data generation module 41 is used by the signal simulation system to obtain the field values ​​of multiple fields of the vehicle event data record, generate scenario simulation data based on the multiple field values, and transmit the scenario simulation data to the signal reporting system. The scene simulation data upload module 42 is used by the signal reporting system to upload scene simulation data to the vehicle network platform; The scenario simulation data comparison module 43 is used to analyze the pulled values ​​of scenario simulation data obtained by the system from the vehicle network platform and the expected values ​​of scenario simulation data obtained from the signal simulation system; compare the expected values ​​and the pulled values ​​to generate a comparison report.

[0062] This invention provides a testing method for vehicle-mounted event data recording. A signal simulation system acquires the field values ​​of multiple fields from the vehicle-mounted event data record, generates scenario simulation data based on these values, and transmits the scenario simulation data to a signal reporting system. The signal reporting system then uploads the scenario simulation data to a vehicle-to-everything (V2X) platform. An analysis system retrieves the pulled values ​​of the scenario simulation data from the V2X platform and obtains the expected values ​​of the scenario simulation data from the signal simulation system. The expected values ​​and pulled values ​​are compared to generate a comparison report. This method provides comprehensive testing support for the research and development, type certification, and quality control of EDR products, helping to improve the reliability and data recording quality of EDR products and providing more reliable data for automotive safety accident analysis and liability determination.

[0063] The development tool interface of the aforementioned signal simulation system has multiple pre-selected field management units; the aforementioned scenario simulation data generation module is used by the signal simulation system to obtain the field values ​​input or selected by the user in the multiple field management units.

[0064] The scenario simulation data generation module described above is also used to determine the field value based on the number of bytes occupied by the field in the field management unit if the user does not input or select a field value in the field management unit.

[0065] The aforementioned scenario simulation data generation module is used by the signal simulation system to convert multiple field values ​​into hexadecimal data, assemble the hexadecimal data into byte strings based on the requirements of the fields in the preset signal document, and use the byte strings as scenario simulation data.

[0066] The above-described scenario simulates a data upload module, which is used by the signal reporting system to encrypt and encapsulate byte strings into vehicle event data record messages using hash encryption; the signal reporting system encapsulates multiple specified fields in the byte strings into login messages; the signal reporting system uploads the login messages to the vehicle network platform via message queue telemetry transmission; if the login message is successfully uploaded, the signal reporting system uploads the vehicle event data record messages to the vehicle network platform.

[0067] The scenario simulation data upload module described above is also used to transmit error information about the login message upload failure to the analysis system if the login message upload fails; the scenario simulation data upload module described above is also used to transmit error information about the vehicle event data recording message upload failure to the analysis system if the vehicle event data recording message upload fails.

[0068] The above-mentioned scenario simulates a data upload module, which is used by the signal reporting system to push vehicle event data recording messages to the cluster in an asynchronous sending mode, so that the cluster can distribute and store the vehicle event data recording messages; the vehicle networking platform subscribes to vehicle event data recording messages from the cluster.

[0069] The aforementioned device also includes: a pull value and expected value calculation module, used by the vehicle networking platform to determine the pull value based on scenario simulation data and display the pull value on the page; and a signal simulation system to determine the expected value based on scenario simulation data.

[0070] The aforementioned scenario simulation data comparison module is used by the analysis system to perform field-level and overall-level comparisons between expected values ​​and retrieved values. Field-level comparisons include numerical field comparisons, time-based field comparisons, and status or identifier-based field comparisons. Overall-level comparisons represent the overall pass rate of expected values ​​and retrieved values. The analysis system generates a comparison report based on the results of field-level and overall-level comparisons. The comparison report includes full results, abnormal data, and data indexes.

[0071] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the vehicle event data recording test device described above can be referred to the corresponding process in the embodiments of the aforementioned vehicle event data recording test method, and will not be repeated here.

[0072] Example 4: This invention also provides an electronic device for running the above-described test method for recording vehicle event data; see also Figure 5 The diagram shows the structure of an electronic device, which includes a memory 100 and a processor 101. The memory 100 is used to store one or more computer instructions, which are executed by the processor 101 to implement the above-mentioned test method for recording vehicle event data.

[0073] Furthermore, Figure 5 The electronic device shown also includes a bus 102 and a communication interface 103, with the processor 101, the communication interface 103 and the memory 100 connected via the bus 102.

[0074] The memory 100 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 103 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 102 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0075] Processor 101 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 101 or by instructions in software form. Processor 101 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a readily available storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 100, and processor 101 reads information from memory 100 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.

[0076] This invention also provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are called and executed by a processor, they cause the processor to implement the aforementioned test method for recording vehicle event data. For specific implementation details, please refer to the method embodiments, which will not be repeated here.

[0077] The computer program product of the vehicle event data recording test method and apparatus provided in the embodiments of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0078] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and / or device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0079] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0080] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0081] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0082] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A test method for recording vehicle-mounted event data, characterized in that, The method includes: The signal simulation system acquires the field values ​​of multiple fields from the vehicle event data record, generates scenario simulation data based on the multiple field values, and transmits the scenario simulation data to the signal reporting system. The signal reporting system uploads the scenario simulation data to the vehicle network platform; The analysis system obtains the pull value of the scenario simulation data from the vehicle network platform and the expected value of the scenario simulation data from the signal simulation system; it compares the expected value and the pull value to generate a comparison report.

2. The method according to claim 1, characterized in that, The development tool design interface for the signal simulation system has multiple pre-selected field management units; The steps for a signal simulation system to obtain field values ​​for multiple fields from an onboard event data record include: The signal simulation system acquires field values ​​that the user inputs or selects in multiple field management units.

3. The method according to claim 2, characterized in that, After obtaining the field values ​​entered or selected by the user in the multiple field management units, the method further includes: If the user does not input or select a field value in the field management unit, the signal simulation system determines the field value based on the number of bytes occupied by the field in the field management unit.

4. The method according to claim 1, characterized in that, The steps for generating scenario simulation data based on multiple field values ​​include: The signal simulation system converts multiple field values ​​into hexadecimal data, assembles the hexadecimal data into a byte string based on the requirements of the fields in the preset signal document, and uses the byte string as scene simulation data.

5. The method according to claim 4, characterized in that, The steps by which the signal reporting system uploads the scenario simulation data to the vehicle-to-everything (V2X) platform include: The signal reporting system encrypts the byte string and encapsulates it into a vehicle event data record message based on hash encryption. The signal reporting system encapsulates multiple specified fields in the byte string into a login message; The signal reporting system uploads the login message to the vehicle network platform via message queue telemetry transmission; If the login message is successfully uploaded, the signal reporting system will upload the vehicle event data record message to the vehicle network platform.

6. The method according to claim 5, characterized in that, After the step of the signal reporting system uploading the login message to the vehicle network platform via message queue telemetry transmission, the method further includes: If the login message fails to upload, the signal reporting system will transmit the error message of the login message upload failure to the analysis system; After the signal reporting system uploads the vehicle event data recording message to the vehicle network platform, the method further includes: If the vehicle event data recording message fails to upload, the signal reporting system will transmit the error message of the failure to upload the vehicle event data recording message to the analysis system.

7. The method according to claim 5, characterized in that, The steps of the signal reporting system uploading the vehicle event data recording message to the vehicle network platform include: The signal reporting system pushes the vehicle event data recording message to the cluster in an asynchronous sending mode, so that the cluster can distribute the vehicle event data recording message. The vehicle networking platform subscribes to the vehicle event data recording messages from the cluster.

8. The method according to claim 1, characterized in that, The method further includes: The vehicle networking platform determines the retrieved value based on the scenario simulation data and displays the retrieved value on the page; The signal simulation system determines the expected value based on the scenario simulation data.

9. The method according to claim 1, characterized in that, The analysis system compares the expected value and the retrieved value to generate a comparison report, including the following steps: The analysis system performs field-level and overall-level comparisons between the expected value and the retrieved value; wherein the field-level comparisons include: numerical field comparisons, time-based field comparisons, and status or identifier-based field comparisons, and the overall-level comparisons characterize the overall pass rate of the expected value and the retrieved value; The analysis system generates a comparison report based on the results of field-level comparison and overall comparison; wherein, the comparison report includes: full results, abnormal data, and data index.

10. A testing device for recording vehicle-mounted event data, characterized in that, The device includes: The scenario simulation data generation module is used to obtain the field values ​​of multiple fields from the vehicle event data record of the signal simulation system, generate scenario simulation data based on the multiple field values, and transmit the scenario simulation data to the signal reporting system. A scene simulation data upload module is used by the signal reporting system to upload the scene simulation data to the vehicle network platform. The scenario simulation data comparison module is used to analyze the retrieved values ​​of the scenario simulation data obtained by the system from the vehicle network platform, and the expected values ​​of the scenario simulation data obtained from the signal simulation system; compare the expected values ​​and the retrieved values, and generate a comparison report.

Images