Fault Code Generation Result Monitoring Method, Device, Equipment and Readable Storage Medium

Abstract

A method, device, equipment and readable storage medium for monitoring the generation result of a fault code, which relates to the technical field of fault injection testing. When receiving fault code information sent by a vehicle body positioning software and containing the fault codes generated by the vehicle body positioning software, a target fault code is determined based on the target fault sensor type and the target fault type corresponding to the target fault; it is judged whether the fault code information contains the target fault code; if it contains, according to the sending moment corresponding to the fault code information, the fault injection start moment corresponding to the target fault and a preset standard output time threshold range, it is determined that the monitoring result of the fault code generation result of the vehicle body positioning software is timely output or delayed output; if it does not contain, it is determined that the monitoring result of the fault code generation result of the vehicle body positioning software is not output. Through the present application, the monitoring of the fault code generation result of the vehicle body positioning software is realized, and further the speed and accuracy of the vehicle body positioning software providing fault codes are effectively determined.

Description

Technical Field

[0001] This application relates to the technical field of fault injection testing, and specifically relates to a method, device, equipment and readable storage medium for monitoring the generation result of fault codes. Background Art

[0002] When the vehicle body positioning software faces various abnormal data, it not only needs to have stable processing capabilities, but also needs to provide various fault codes in a timely manner to assist in determining whether to trust the relevant data results. During the simulation test of the vehicle body positioning software, a large amount of abnormal data that meets the requirements of various fault types in FEMA (Failure Mode and Effects Analysis) analysis is required to generate faults according to the abnormal data and inject them into the vehicle body positioning software for simulation testing. Among them, since the speed and accuracy of the vehicle body positioning software in providing fault codes will affect the reliability and accuracy of the vehicle body positioning software, it is very important to monitor the result of the vehicle body positioning software generating fault codes based on the injected faults after the faults are injected into the vehicle body positioning software, so as to judge the speed and accuracy of the vehicle body positioning software in providing fault codes.

[0003] However, in the related art, the generation result of the fault codes of the vehicle body positioning software is not monitored, so that the speed and accuracy of the vehicle body positioning software in providing fault codes cannot be determined. Summary of the Invention

[0004] This application provides a method, device, equipment and readable storage medium for monitoring the generation result of fault codes, so as to realize the monitoring of the generation result of the fault codes of the vehicle body positioning software, and further determine the speed and accuracy of the vehicle body positioning software in providing fault codes.

[0005] In a first aspect, an embodiment of this application provides a method for monitoring the generation result of fault codes. The method for monitoring the generation result of fault codes includes:

[0006] When receiving the fault code information sent by the vehicle body positioning software, determine the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault. The fault code information includes the fault codes generated by the vehicle body positioning software;

[0007] Judge whether the target fault code is included in the fault code information;

[0008] If it is included, determine whether the monitoring result of the generation result of the fault codes of the vehicle body positioning software is timely output or delayed output according to the sending time corresponding to the fault code information, the fault injection start time corresponding to the target fault, and the preset standard output time threshold range;

[0009] If not included, it is determined that the monitoring result of the fault code generation result of the vehicle body positioning software is not output.

[0010] Combined with the first aspect, in an implementation, the determining the monitoring result of the fault code generation result of the vehicle body positioning software as timely output or delayed output according to the sending time corresponding to the fault code information, the fault injection start time corresponding to the target fault, and a preset standard output time threshold includes:

[0011] Determine whether the difference between the sending time and the fault injection start time is within the range of the standard output time threshold;

[0012] If the difference is within the range of the standard output time threshold, it is determined that the monitoring result of the fault code generation result is timely output;

[0013] If the difference is outside the range of the standard output time threshold, it is determined that the monitoring result of the fault code generation result is delayed output.

[0014] Combined with the first aspect, in an implementation, before the step of determining the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault, it further includes:

[0015] Select target fault records from multiple fault records according to the sending time, the fault record generation time corresponding to each fault record, and a preset monitoring duration. The target fault records include the target fault and its corresponding fault sensor type, fault type, and fault injection start time.

[0016] Combined with the first aspect, in an implementation, the fault code generation result monitoring method further includes:

[0017] For each fault, generate fault data and its corresponding fault record based on the multi-sensor fusion data corresponding to the fault, the fault sensor type, the fault duration, the fault type, the fault error range, and whether to enable fault generation, and inject the fault data into the vehicle body positioning software for the vehicle body positioning software to perform fault simulation tests based on the fault data and generate fault codes.

[0018] Combined with the first aspect, in an implementation, the fault data is injected into the vehicle body positioning software by a real-time injection method or a fault file injection method.

[0019] In a second aspect, an embodiment of the present application provides a monitoring device for the fault code generation result. The monitoring device for the fault code generation result includes:

[0020] The first processing module is configured to, when receiving the fault code information sent by the vehicle body positioning software, determine a target fault code based on the target fault sensor type and the target fault type corresponding to the target fault, where the fault code information includes the fault code generated by the vehicle body positioning software;

[0021] The second processing module is configured to determine whether the target fault code is included in the fault code information;

[0022] The third processing module is configured to, if included, determine whether the monitoring result of the fault code generation result of the vehicle body positioning software is timely output or delayed output according to the sending moment corresponding to the fault code information, the fault injection start moment corresponding to the target fault, and a preset standard output time threshold range; if not included, determine that the monitoring result of the fault code generation result of the vehicle body positioning software is not output.

[0023] Combined with the second aspect, in an implementation manner, the first processing module is specifically configured to:

[0024] Determine whether the difference between the sending moment and the fault injection start moment is within the standard output time threshold range;

[0025] If the difference is within the standard output time threshold range, determine that the monitoring result of the fault code generation result is timely output;

[0026] If the difference is outside the standard output time threshold range, determine that the monitoring result of the fault code generation result is delayed output.

[0027] Combined with the second aspect, in an implementation manner, the fault code generation result monitoring device further includes a fault record screening module, which is configured to:

[0028] Screen out target fault records from multiple fault records according to the sending moment, the fault record generation moment corresponding to each fault record, and a preset monitoring duration, where the target fault records include the target fault and its corresponding fault sensor type, fault type, and fault injection start moment.

[0029] Combined with the second aspect, in an implementation manner, the fault code generation result monitoring device further includes a fault data generation and injection module, which is configured to:

[0030] For each fault, generate fault data and its corresponding fault record based on the multi-sensor fusion data corresponding to the fault, the fault sensor type, the fault duration, the fault type, the fault error range, and whether to enable the fault, and inject the fault data into the vehicle body positioning software for the vehicle body positioning software to perform fault simulation tests based on the fault data and generate fault codes.

[0031] In a second aspect, in one implementation, the fault data is injected into the vehicle body positioning software through a real-time injection method or a fault file injection method.

[0032] In a third aspect, an embodiment of the present application provides a fault code generation result monitoring device, which includes a processor, a memory, and a fault code generation result monitoring program stored on the memory and executable by the processor. When the fault code generation result monitoring program is executed by the processor, the steps of the fault code generation result monitoring method as described above are implemented.

[0033] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a fault code generation result monitoring program is stored. When the fault code generation result monitoring program is executed by a processor, the steps of the fault code generation result monitoring as described above are implemented.

[0034] The beneficial effects brought by the technical solutions provided by the embodiments of the present application at least include:

[0035] When receiving fault code information including the fault codes generated by the vehicle body positioning software sent by the vehicle body positioning software, the target fault code corresponding to the target fault is determined through the target fault sensor type and the target fault type; then it is judged whether the fault code information contains the target fault code. If it contains, it means that the vehicle body positioning software accurately identifies the fault code of the target fault and outputs it, so the fault code provided by the vehicle body positioning software is accurate; if it does not contain, it means that the vehicle body positioning software does not identify the fault code of the target fault, so the fault code provided by the vehicle body positioning software is inaccurate; at the same time, for the accurate fault code, it is also determined whether it is output in a timely manner or with a delay according to the sending moment corresponding to the fault code information, the fault injection start moment corresponding to the target fault, and the preset standard output time threshold range, thereby realizing the monitoring of the speed at which the vehicle body positioning software provides fault codes. Thus, it can be seen that the embodiments of the present application realize the monitoring of the fault code generation result of the vehicle body positioning software, and effectively determine the speed and accuracy of the fault codes provided by the vehicle body positioning software. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is a schematic flowchart of an embodiment of the fault code generation result monitoring method of the present application;

[0037] Figure 2 It is a schematic diagram of the functional modules of an embodiment of the fault code generation result monitoring device of the present application;

[0038] Figure 3 It is a schematic diagram of the hardware structure of the fault code generation result monitoring device involved in the solution of the embodiment of the present application. DETAILED DESCRIPTION

[0039] To enable those skilled in the art to better understand the solution of this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the scope of protection of this application.

[0040] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned accompanying drawings are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or devices. The descriptions such as "first", "second", and "third" are used to distinguish different objects, etc., and do not represent a sequential order, nor do they limit that "first", "second", and "third" are of different types.

[0041] In the description of the embodiments of this application, "exemplary", "for example" or "for instance" etc. are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary", "for example" or "for instance" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary", "for example" or "for instance" is intended to present the relevant concepts in a specific manner.

[0042] In the description of the embodiments of this application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B; "and / or" in the text is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "a plurality of" means two or more than two.

[0043] In some processes described in the embodiments of this application, there are multiple operations or steps that appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of this application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the following will further describe the embodiments of this application in detail with reference to the accompanying drawings.

[0045] In a first aspect, an embodiment of this application provides a method for monitoring the generation result of a fault code.

[0046] In one embodiment, referring to Figure 1 , Figure 1 is a schematic flowchart of an embodiment of the method for monitoring the generation result of a fault code in this application. As Figure 1 shown, the method for monitoring the generation result of a fault code includes:

[0047] Step S10: When receiving the fault code information sent by the vehicle body positioning software, determine the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault, where the fault code information includes the fault code generated by the vehicle body positioning software;

[0048] Exemplarily, in this embodiment, during the simulation test of the vehicle body positioning software, when the fault data corresponding to a certain fault is injected into the vehicle body positioning software, the vehicle body positioning software will generate a fault code based on the fault data and output it at a fixed frequency. It should be noted that the setting of the time interval corresponding to the fixed-frequency output can be determined according to actual needs and is not limited herein; for example, if the time interval corresponding to the fixed-frequency output is T1, then the vehicle body positioning software will output the fault code generated within the T1 time period in the form of fault code information every T1 time. Specifically, assuming that within the T1 time period, the vehicle body positioning software generates fault code A, fault code B, and fault code C respectively, then after the T1 time is reached, the fault code information including fault code A, fault code B, and fault code C will be output.

[0049] After receiving the fault code information sent by the vehicle body positioning software in this embodiment, the monitoring of the generation result of the fault code output by the vehicle body positioning software will be started, that is, continuously monitor whether the vehicle body positioning software issues a fault code within the specified processing time after the fault data is injected. In this embodiment, the fault code of the target fault in the current time period will be determined, that is, the target fault code corresponding to the target fault is determined according to the target fault sensor type and the target fault type corresponding to the target fault. It should be noted that when generating fault data for each fault in this embodiment, information such as the fault sensor type, fault type, and fault injection start time corresponding to the fault will be automatically recorded; in addition, the method of determining the fault code according to the fault sensor type and the fault type is common knowledge and can be specifically designed according to actual needs and corresponding one by one, which will not be elaborated herein.

[0050] In addition, it should be understood that this embodiment will also provide a fault code display UI (User Interface) interface for real-time display of fault codes. Specifically, after this embodiment receives the fault code information sent by the vehicle body positioning software, the fault code display UI will display the fault codes sent by the vehicle body positioning software in real time. And when there is a change in the fault codes sent by the vehicle body positioning software, it will also display the updated content, such as the sending time and specific content of the new fault code, etc.

[0051] Step S20: Determine whether the target fault code is included in the fault code information;

[0052] Exemplarily, in this embodiment, after determining the target fault code of the target fault, it will be determined whether the fault code information sent by the vehicle body positioning software includes the target fault code, that is, it is determined whether the vehicle body positioning software has generated a fault code corresponding to the target fault, so as to further determine whether the vehicle body positioning software has accurately identified the fault code, thereby realizing the accuracy monitoring of the fault codes provided by the vehicle body positioning software.

[0053] Step S30: If it is included, determine whether the monitoring result of the fault code generation result of the vehicle body positioning software is output on time or with a delay according to the sending moment corresponding to the fault code information, the fault injection start moment corresponding to the target fault, and the preset standard output time threshold range;

[0054] Exemplarily, in this embodiment, if it is detected that the fault codes generated by the vehicle body positioning software include the target fault code, it means that the vehicle body positioning software has accurately identified the fault code of the target fault and output it, that is, the fault codes provided by the vehicle body positioning software are accurate, and the fault type has been accurately identified and relevant warning information has been provided to the downstream in a timely manner; at the same time, this embodiment will also determine whether the fault codes output by the vehicle body positioning software are output on time or with a delay according to the sending moment corresponding to the fault code information sent by the vehicle body positioning software, the fault injection start moment corresponding to the target fault, and the preset standard output time threshold range, so as to realize the speed monitoring of the fault codes provided by the vehicle body positioning software.

[0055] It should be noted that the standard output time threshold range is used to characterize whether the vehicle body positioning software has output the fault code on time within the specified time, and its specific value can be determined according to the characteristics and requirements of different faults, which is not limited here.

[0056] Step S40: If it is not included, determine that the monitoring result of the fault code generation result of the vehicle body positioning software is not output.

[0057] Exemplarily, in this embodiment, if it is detected that the fault codes generated by the vehicle body positioning software do not include the target fault code, it indicates that the vehicle body positioning software fails to identify the fault code of the target fault. Then, the fault codes provided by the vehicle body positioning software are inaccurate and the fault type is not recognized, that is, the reliability and accuracy of the vehicle body positioning software do not meet the requirements. Thus, this embodiment realizes the monitoring of the fault code generation result of the vehicle body positioning software, and further effectively determines the speed and accuracy of the fault codes provided by the vehicle body positioning software.

[0058] In addition, in this embodiment, the fallback time corresponding to each fault can be preset, so as to fallback the system node according to the fallback time, and then repeat the test for the fault. It can be understood that when the system needs to repeat the test for a certain fault at a certain time, in order to ensure the successful restart of the system, it is necessary to make the monitoring node fallback to a certain moment before the injection of the fault data corresponding to the fault. Then, the fallback time refers to the difference between this moment and the moment when the fault data starts to be injected.

[0059] Further, in an embodiment, determining that the monitoring result of the fault code generation result of the vehicle body positioning software is timely output or delayed output according to the sending moment corresponding to the fault code information, the fault injection start moment corresponding to the target fault, and the preset standard output time threshold range includes:

[0060] Judging whether the difference between the sending moment and the fault injection start moment is within the standard output time threshold range;

[0061] If the difference is within the standard output time threshold range, it is determined that the monitoring result of the fault code generation result is timely output;

[0062] If the difference is outside the standard output time threshold range, it is determined that the monitoring result of the fault code generation result is delayed output.

[0063] Exemplarily, in this embodiment, it is judged whether the difference between the sending moment and the fault injection start moment is within the standard output time threshold range. If the difference is within the standard output time threshold range, it indicates that the vehicle body positioning software outputs the fault code corresponding to the target fault within the specified time, and it is determined that the monitoring result of the fault code generation result of the vehicle body positioning software is timely output; if it is outside the standard output time threshold range, it indicates that the vehicle body positioning software does not output the fault code corresponding to the target fault within the specified time, and it is determined that the monitoring result of the fault code generation result of the vehicle body positioning software is delayed output.

[0064] Further, in an embodiment, before the step of determining the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault, it further includes:

[0065] Screen out target fault records from multiple fault records according to the sending time, the fault record generation time corresponding to each fault record, and a preset monitoring duration. The target fault records include target faults and their corresponding fault sensor types, fault types, and fault injection start times.

[0066] Exemplarily, it should be understood that each fault code has a time limit. That is, the system requires the vehicle body positioning software to report the fault within the corresponding duration after receiving the fault data and feedback it to the downstream. That is, the fault code output within this duration is generated based on the current few frames of fault data, rather than the fault data from a previous period. Therefore, this embodiment also records the continuous monitoring duration corresponding to each fault. Among them, the continuous monitoring duration represents the continuous time for monitoring whether a fault code is generated after each fault is injected. Since the durations corresponding to different faults are different, the specific value setting of the monitoring duration corresponding to each fault can be determined according to actual needs and is not limited here.

[0067] At the same time, when generating fault data for each fault, this embodiment will automatically record information such as the fault sensor type, fault type, and fault injection start time corresponding to the fault to form corresponding fault records. Therefore, when it is necessary to monitor the fault code generation result, the corresponding target fault records will be screened out from all the fault records to determine the fault code of the target fault according to the target fault sensor type and target fault type stored in the target fault records.

[0068] Specifically, when receiving the fault code information sent by the vehicle body positioning software, traverse each fault record, that is, calculate the time difference by subtracting the fault record generation time corresponding to each fault record from the sending time corresponding to the fault code information. If the time difference is less than the corresponding preset monitoring duration, then this fault record is used as the target fault record. For example, taking the preset monitoring duration corresponding to fault A as t1 and the fault record generation time of fault record X corresponding to fault A as t2 as an example, assuming that the difference between the sending time and t2 is less than t1, then fault record X is used as the target fault record. If the difference between the sending time and t2 is not less than t1, it means that the vehicle body positioning software has not recognized fault A, and it is determined that fault A has not been output.

[0069] Further, in one embodiment, the fault code generation result monitoring method further includes:

[0070] For each fault, fault data and its corresponding fault record are generated based on multi-sensor fusion data corresponding to the fault, the type of faulty sensor, the fault duration, the fault type, the fault error range, and whether the fault is enabled, and the fault data is injected into the vehicle body positioning software for the vehicle body positioning software to perform fault simulation testing based on the fault data and generate fault codes.

[0071] Exemplarily, in this embodiment, the multi-sensor fusion data is transmitted to the fault data generation and injection module through the data playback module. The data playback module may include a data playback UI, a speed setting UI, a file loading UI, and data processing modules corresponding to each type of faulty sensor. The original data packet to be played back is selected and loaded through the file loading UI. The data playback UI is used to control the playback and pause of the original data packet, and the playback position of the original data packet can be controlled by dragging the progress bar. The speed setting UI is used to set the playback speed of the original data packet. The data playback module is responsible for receiving and parsing the multi-sensor fusion data. When there is no fault to be injected, the parsed data is directly sent to the vehicle body positioning software; when there is a fault to be injected, the parsed data is sent to the data processing module corresponding to the type of faulty sensor for processing, and then the processed multi-sensor fusion data is transmitted to the fault data generation and injection module by the data processing module.

[0072] For each fault, the fault data generation and injection module will generate fault data and its corresponding fault record according to the received multi-sensor fusion data and the preset type of faulty sensor, fault duration, fault type, fault error range, and whether the fault is enabled. Specifically, when the fault is enabled, the multi-sensor fusion data is added with the fault error or the fault error range to generate the fault data and its corresponding fault record, and the fault data is injected into the vehicle body positioning software for the vehicle body positioning software to perform fault simulation testing based on the fault data and generate fault codes. Thus, it can be seen that this embodiment can generate fault data that meets the requirements of various fault types, has good scalability, can automatically monitor whether various fault codes are generated in a timely and accurate manner, and effectively improves the automation performance and efficiency in the simulation testing process.

[0073] Further, in one embodiment, the fault data is injected into the vehicle body positioning software by a real-time injection method or a fault file injection method.

[0074] Exemplarily, in this embodiment, the fault data generation and injection module may include a fault data human-computer interaction UI and a fault data display UI, etc. Among them, when injecting the fault data into the vehicle body positioning software by the real-time injection method, it can be realized through the fault data human-computer interaction UI; while when injecting the fault data into the vehicle body positioning software by the fault file injection method, it can be realized through the fault data display UI.

[0075] Specifically, the human-machine interaction UI for fault data provides a setting interface for real-time injecting fault data. Through this interface, users can select the configuration parameters for fault injection, including but not limited to the type of fault sensor, fault duration, fault type, fault error range, and whether to enable the fault. Among them, the type of fault sensor includes but not limited to RTK (Real-time kinematic) data fault, vehicle body data fault, perception data fault, IMU (Inertial Measurement Unit) data fault, high-precision map data fault, and other sensor data faults.

[0076] The fault types include generation error, signal shielding, and time-delay faults. The way of generating error is to perform bias addition processing on the received sensor data according to the set fault error range and replace the original data for sending; among them, the bias addition processing is divided into fixed bias addition and random bias addition. Fixed bias addition means using the original data and the bias value and calculating the fault data according to a specific formula. Random bias addition means generating a random variable with specific digital characteristics within the fault error range and calculating the fault data; it should be noted that the bias addition type can be selected when setting the fault error range. The way of signal shielding is to stop sending relevant data within a specified time period; the time-delay fault is to calculate the sending interval of each data in a specific way within a specified time range and simulate the signal blockage situation by changing the sending time of the data; when the fault is selected to be enabled, the selected fault data starts to be generated and sent continuously within the fault duration.

[0077] It should be understood that in this embodiment, fault data of multiple sensors can be generated simultaneously, and the fault data of each sensor can be injected with multiple faults; among the multiple faults of the same sensor, the signal shielding fault has the highest priority, and the error generation fault has the lowest priority.

[0078] The fault data display UI provides a data display interface for injecting fault data according to the fault file, that is, before starting the test, the fault data can be directly written in batches according to the instruction document. Among them, the configuration parameters that need to be written in this scheme include the starting moment of fault data generation (i.e., the starting moment of fault injection), fault duration, fault sensor type, fault type, and fault error range, etc.; it should be noted that this embodiment will also record the difference between the starting moment of fault data generation and the starting moment of the data packet, so that the repeated use of the fault file can be realized, that is, when reading the fault file, this embodiment will automatically calculate the corresponding time of the starting moment of fault data generation in the data packet according to this difference, and then only load the fault records within this time range in the data packet.

[0079] In a second aspect, the embodiment of the present application also provides a fault code generation result monitoring device.

[0080] In one embodiment, referring to Figure 2 , Figure 2 , it is a schematic diagram of the functional modules of an embodiment of the fault code generation result monitoring device of the present application. As Figure 2 shown, the fault code generation result monitoring device includes:

[0081] A first processing module, which is configured to determine a target fault code based on the target fault sensor type and the target fault type corresponding to the target fault when receiving fault code information sent by the vehicle body positioning software, where the fault code information includes the fault code generated by the vehicle body positioning software;

[0082] A second processing module, which is configured to determine whether the target fault code is included in the fault code information;

[0083] A third processing module, which is configured to, if included, determine whether the monitoring result of the fault code generation result of the vehicle body positioning software is timely output or delayed output according to the sending time corresponding to the fault code information, the fault injection start time corresponding to the target fault, and a preset standard output time threshold range; if not included, determine that the monitoring result of the fault code generation result of the vehicle body positioning software is not output.

[0084] Further, in one embodiment, the first processing module is specifically configured to:

[0085] Determine whether the difference between the sending time and the fault injection start time is within the standard output time threshold range;

[0086] If the difference is within the standard output time threshold range, determine that the monitoring result of the fault code generation result is timely output;

[0087] If the difference is outside the standard output time threshold range, determine that the monitoring result of the fault code generation result is delayed output.

[0088] Further, in one embodiment, the fault code generation result monitoring device further includes a fault record screening module, which is configured to:

[0089] Screen out target fault records from multiple fault records according to the sending time, the fault record generation time corresponding to each fault record, and a preset monitoring duration, where the target fault records include the target fault and its corresponding fault sensor type, fault type, and fault injection start time.

[0090] Further, in one embodiment, the fault code generation result monitoring device further includes a fault data generation and injection module, which is configured to:

[0091] For each fault, fault data and its corresponding fault record are generated based on multi-sensor fusion data corresponding to the fault, the type of faulty sensor, the fault duration, the fault type, the fault error range, and whether the fault is enabled, and the fault data is injected into the vehicle body positioning software for the vehicle body positioning software to perform fault simulation testing based on the fault data and generate a fault code. Among them, the multi-sensor fusion data is processed by the data playback module and transmitted to the fault data generation and injection module.

[0092] Further, in one embodiment, the fault data is injected into the vehicle body positioning software by a real-time injection method or a fault file injection method.

[0093] Among them, the function implementation of each module in the above fault code generation result monitoring device corresponds to each step in the above embodiment of the fault code generation result monitoring method, and its function and implementation process will not be elaborated here one by one.

[0094] In a third aspect, an embodiment of the present application provides a fault code generation result monitoring device, and the fault code generation result monitoring device can be a device with data processing functions such as a personal computer (PC), a laptop computer, a server, etc.

[0095] Referring to Figure 3 , Figure 3 is a schematic hardware structure diagram of the fault code generation result monitoring device involved in the embodiment of the present application. In the embodiment of the present application, the fault code generation result monitoring device may include a processor, a memory, a communication interface, and a communication bus.

[0096] Among them, the communication bus can be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0097] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces, etc., which are used to implement the interconnection of components inside the fault code generation result monitoring device, and interfaces for implementing the interconnection of the fault code generation result monitoring device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display (Display), a keyboard (Keyboard), etc.

[0098] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical memory, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0099] The processor can be a general-purpose processor, which can call the fault code generation result monitoring program stored in the memory and execute the fault code generation result monitoring method provided by the embodiments of the present application. For example, the general-purpose processor can be a central processing unit (CPU). Among them, the method executed when the fault code generation result monitoring program is called can refer to the various embodiments of the fault code generation result monitoring method of the present application, which will not be elaborated here.

[0100] Those skilled in the art can understand that Figure 3 the hardware structure shown in does not constitute a limitation to the present application, and may include more or fewer components than shown in the figure, or combine some components, or arrange different components.

[0101] In a fourth aspect, the embodiments of the present application further provide a computer-readable storage medium.

[0102] The fault code generation result monitoring program is stored on the readable storage medium of the present application. When the fault code generation result monitoring program is executed by a processor, the steps of the fault code generation result monitoring method as described above are implemented.

[0103] Among them, the method implemented when the fault code generation result monitoring program is executed can refer to the various embodiments of the fault code generation result monitoring method of the present application, which will not be elaborated here.

[0104] It should be noted that the serial numbers of the above embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0105] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium as described above (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal device to execute the methods described in various embodiments of the present application.

[0106] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A method for monitoring the generation result of fault codes, characterized in that, The method for monitoring the fault code generation result includes: When receiving the fault code information sent by the vehicle body positioning software, determining the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault, where the fault code information includes the fault code generated by the vehicle body positioning software; Judging whether the target fault code is included in the fault code information; If it is included, determining whether the monitoring result of the fault code generation result of the vehicle body positioning software is output on time or with a delay according to the sending time corresponding to the fault code information, the fault injection start time corresponding to the target fault, and the preset standard output time threshold range; If it is not included, determining that the monitoring result of the fault code generation result of the vehicle body positioning software is not output; Among them, determining whether the monitoring result of the fault code generation result of the vehicle body positioning software is output on time or with a delay according to the sending time corresponding to the fault code information, the fault injection start time corresponding to the target fault, and the preset standard output time threshold includes: Judging whether the difference between the sending time and the fault injection start time is within the standard output time threshold range; If the difference is within the standard output time threshold range, determining that the monitoring result of the fault code generation result is output on time; If the difference is outside the standard output time threshold range, determining that the monitoring result of the fault code generation result is output with a delay; The method further includes: performing a rollback on the system node based on the rollback time corresponding to the target fault to perform repeated tests on the target fault, where the rollback time is the difference between a certain moment before the start of injection of the target fault data and the start time of injection of the target fault data.

2. The method for monitoring the generation result of fault codes according to claim 1, wherein Before the step of determining the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault, it further includes: Screening out the target fault record from multiple fault records according to the sending time, the fault record generation time corresponding to each fault record, and the preset monitoring duration, where the target fault record includes the target fault and its corresponding fault sensor type, fault type, and fault injection start time.

3. The fault code generation result monitoring method according to claim 2, wherein The method for monitoring the fault code generation result further includes: For each fault, generating fault data and its corresponding fault record based on the multi-sensor fusion data, fault sensor type, fault duration, fault type, fault error range, and whether to enable the fault corresponding to the fault, and injecting the fault data into the vehicle body positioning software for the vehicle body positioning software to perform a fault simulation test based on the fault data and generate a fault code.

4. The method for monitoring the fault code generation result according to claim 3, wherein: Injecting the fault data into the vehicle body positioning software through a real-time injection method or a fault file injection method.

5. A fault code generation result monitoring device, characterized in that, The device for monitoring the fault code generation result includes: A first processing module, which is used to determine the target fault code based on the target fault sensor type and the target fault type corresponding to the target fault when receiving the fault code information sent by the vehicle body positioning software, where the fault code information includes the fault code generated by the vehicle body positioning software; A second processing module, which is used to judge whether the target fault code is included in the fault code information; A third processing module, which is configured to, if included, determine whether the monitoring result of the fault code generation result of the vehicle body positioning software is output on time or with a delay according to the transmission time corresponding to the fault code information, the fault injection start time corresponding to the target fault, and a preset standard output time threshold range; if not included, determine that the monitoring result of the fault code generation result of the vehicle body positioning software is not output. Wherein, the third processing module is specifically configured to: Determine whether the difference between the transmission time and the fault injection start time is within the standard output time threshold range. If the difference is within the standard output time threshold range, determine that the monitoring result of the fault code generation result is output on time. If the difference is outside the standard output time threshold range, determine that the monitoring result of the fault code generation result is output with a delay. The first processing module is further configured to roll back the system node based on the rollback time corresponding to the target fault to repeatedly test the target fault, where the rollback time is the difference between a certain moment before the start of injection of the target fault data and the start time of injection of the target fault data.

6. The fault code generation result monitoring device according to claim 5, characterized in that, The fault code generation result monitoring device further includes a fault record screening module, which is configured to: Screen out target fault records from multiple fault records according to the transmission time, the fault record generation time corresponding to each fault record, and a preset monitoring duration, where the target fault records include the target fault and its corresponding fault sensor type, fault type, and fault injection start time.

7. A fault code generation result monitoring device, characterized in that The fault code generation result monitoring device includes a processor, a memory, and a fault code generation result monitoring program stored on the memory and executable by the processor. When the fault code generation result monitoring program is executed by the processor, the steps of the fault code generation result monitoring method according to any one of claims 1 to 4 are implemented.

8. A computer-readable storage medium, characterized in that, A fault code generation result monitoring program is stored on the computer-readable storage medium. When the fault code generation result monitoring program is executed by a processor, the steps of the fault code generation result monitoring according to any one of claims 1 to 4 are implemented.

Images