Fault state processing method and device of vehicle-mounted equipment
By processing fault status data of on-board equipment in the cloud according to custom rules, the problems of inefficient and insufficient accuracy of fault detection and risk identification in the prior art are solved, and higher accuracy of driving risk identification and system reliability are achieved.
Patent Information
- Application Number
- CN202411893994.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-20
- Publication Date
- 2025-04-18
AI Technical Summary
In the prior art, fault detection and risk identification of on-board equipment have problems such as inefficient and insufficient accuracy, especially due to the lack of effective risk control safety management and redundant fault reporting links.
A fault status processing method for on-board equipment is proposed. By processing fault status data in the cloud according to custom rules and performing feedback analysis, the accuracy of driving risk identification is improved. The method includes obtaining fault status data from the message middleware, applying fault judgment rules to process, and conducting statistical analysis based on the fault reporting rules.
Through this method, the accuracy of driving risk identification can be improved, false alarms and unnecessary maintenance work can be reduced, resource allocation can be optimized, and the overall reliability and maintenance efficiency of the system can be improved.
Smart Images

Figure CN119848663A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a method for processing a fault state of an on-board device, a device for processing a fault state of an on-board device, a computer-readable storage medium, and a computer device. Background Art
[0002] In related technologies, in order to further improve and enhance driving safety awareness, more and more vehicles have installed smart devices on the terminals to identify driving risks. For example, smart devices can be used to identify smoking, making phone calls, fatigue driving, speeding, obstacles, etc. while driving, so as to remind the driver in time and reduce the risk of accidents.
[0003] However, the current driving risk identification in the industry cannot guarantee the integrity of vehicle-mounted equipment under normal circumstances. Due to the lack of a risk control and safety management role, the safety risk cannot be minimized. Moreover, if a module in the vehicle-mounted equipment fails, the above functions will also fail. In addition, the fault reporting link is very redundant and complicated, resulting in low efficiency. Summary of the invention
[0004] The present application aims to solve at least one of the technical problems in the above-mentioned technology to a certain extent. To this end, one purpose of the present application is to propose a method for processing the fault state of an on-board device, which can process the fault state data in the cloud according to custom rules and perform feedback analysis on the final processed data, thereby improving the accuracy of driving risk identification.
[0005] A second object of the present application is to provide a computer-readable storage medium.
[0006] The third objective of the present application is to provide a computer device.
[0007] The fourth objective of the present application is to provide a fault status processing device for vehicle-mounted equipment.
[0008] To achieve the above-mentioned objectives, the first aspect of the present application proposes a method for processing a fault status of an on-board device, the method comprising the following steps: obtaining the fault status data of each module in the on-board device from the message middleware; obtaining a fault judgment rule, and judging and processing the fault status data within a time window according to the fault judgment rule to obtain corresponding fault result data, and storing the fault result data in the message middleware; obtaining a fault reporting rule and the fault result data, and reporting the fault result data according to the fault reporting rule, so as to perform statistical analysis on the reported fault result data.
[0009] According to the above-mentioned technical means, the embodiment of the present application can process the fault status data in the cloud according to custom rules, and perform feedback analysis on the final processed data, thereby improving the accuracy of driving risk identification.
[0010] In addition, the fault state processing method of the vehicle-mounted device proposed in the above embodiment of the present application may also have the following additional technical features:
[0011] Optionally, before obtaining the fault status data of each module in the vehicle-mounted device from the message middleware, it also includes: using the device network access load to obtain the fault status data of each module in the vehicle-mounted device to be decoded; forwarding the fault status data to the device protocol encoding and decoding service for message decoding to obtain the decoded fault status data of each module in the vehicle-mounted device, and storing it in the message middleware.
[0012] According to the above technical means, the embodiment of the present application uses the message middleware as the buffer and distribution center of the data flow, which helps to achieve the decoupling and scalability of the system, making the data processing flow more flexible and reliable.
[0013] Optionally, the fault status data within the time window is judged and processed according to the fault judgment rule to obtain corresponding fault result data, including: obtaining a fault threshold; within the time window, comparing the current fault status data corresponding to each module with the previous fault status data, and recording the number of consecutive faults; if the number of consecutive faults reaches the fault threshold, it is judged that the corresponding module within the time window has failed; otherwise, it is judged that the corresponding module within the time window has not failed.
[0014] According to the above technical means, the embodiments of the present application can help distinguish normal fluctuations from actual faults through fault judgment rules, reduce false alarms caused by accidental events, and ensure that real faults are not missed.
[0015] Optionally, the fault status data within the time window is judged and processed according to the fault judgment rule to obtain corresponding fault result data, including: obtaining the combination relationship of each module in the vehicle-mounted device, wherein each combination relationship includes at least one module in the vehicle-mounted device; within the time window, judging the fault status corresponding to all modules in the combination relationship according to the fault status data of each module; if the fault status corresponding to all modules in the combination relationship are all faults, judging that the corresponding combination relationship within the time window has a fault; otherwise, judging that the corresponding combination relationship within the time window has not a fault.
[0016] According to the above-mentioned technical means, the embodiment of the present application can comprehensively consider the status of multiple modules, identify real system-level faults, and eliminate occasional or non-critical problems, thereby improving the accuracy of fault detection, reducing false alarms and unnecessary maintenance work, while optimizing resource allocation and improving the overall reliability and maintenance efficiency of the system.
[0017] To achieve the above-mentioned purpose, the second aspect embodiment of the present application proposes a computer-readable storage medium, on which a fault state handling program of a vehicle-mounted device is stored. When the fault state handling program of the vehicle-mounted device is executed by a processor, the fault state handling method of the vehicle-mounted device as described above is implemented.
[0018] To achieve the above-mentioned objectives, the third aspect embodiment of the present application proposes a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the fault state processing method of the vehicle-mounted equipment as described above is implemented.
[0019] To achieve the above-mentioned objectives, the fourth aspect of the present application proposes a fault status processing device for a vehicle-mounted device, including: an acquisition module, used to obtain the fault status data of each module in the vehicle-mounted device from the message middleware; a judgment and processing module, used to obtain the fault judgment rules, and judge and process the fault status data within the time window according to the fault judgment rules to obtain the corresponding fault result data, and store the fault result data in the message middleware; a reporting and analysis module, used to obtain the fault reporting rules and the fault result data, and report the fault result data according to the fault reporting rules, so as to perform statistical analysis on the reported fault result data.
[0020] According to the above-mentioned technical means, the embodiment of the present application can process the fault status data in the cloud according to custom rules, and perform feedback analysis on the final processed data, thereby improving the accuracy of driving risk identification.
[0021] In addition, the fault state processing device of the vehicle-mounted device proposed in the above embodiment of the present application may also have the following additional technical features:
[0022] Optionally, the acquisition module is also used to use the device network access load to obtain the fault status data of each module in the vehicle-mounted device to be decoded; forward the fault status data to the device protocol encoding and decoding service for message decoding to obtain the decoded fault status data of each module in the vehicle-mounted device, and store it in the message middleware.
[0023] Optionally, the judgment and processing module is also used to obtain a fault threshold; within a time window, compare the current fault status data corresponding to each module with the previous fault status data, and record the number of consecutive faults; if the number of consecutive faults reaches the fault threshold, it is judged that the corresponding module within the time window has failed; otherwise, it is judged that the corresponding module within the time window has not failed.
[0024] Optionally, the judgment and processing module is also used to obtain the combination relationship of each module in the vehicle-mounted device, wherein each combination relationship includes at least one module in the vehicle-mounted device; within the time window, the fault status corresponding to all modules in the combination relationship is judged according to the fault status data of each module; if the fault status corresponding to all modules in the combination relationship are all faults, it is judged that the corresponding combination relationship within the time window has a fault; otherwise, it is judged that the corresponding combination relationship within the time window has not a fault. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 It is a flowchart of a method for handling a fault state of an on-board device according to an embodiment of the present application;
[0026] Figure 2 A schematic diagram of a flow chart of a method for handling a fault state of an on-vehicle device according to an embodiment of the present application;
[0027] Figure 3 4 is a block diagram of a fault status processing device for an on-vehicle device according to an embodiment of the present application. DETAILED DESCRIPTION
[0028] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.
[0029] In order to better understand the above technical solution, exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.
[0030] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the accompanying drawings and specific implementation methods.
[0031] like Figure 1As shown, the fault state processing method of the vehicle-mounted device in the embodiment of the present application includes the following steps:
[0032] S101, obtaining fault status data of each module in the vehicle-mounted device from the message middleware.
[0033] It should be noted that the real-time computing engine is connected to the message middleware, and the fault status data of each module in the vehicle-mounted device stored in the message middleware is obtained through the real-time computing engine, so that the real-time computing engine can process these data according to preset rules and algorithms.
[0034] As an embodiment, before obtaining the fault status data of each module in the vehicle-mounted device from the message middleware, it also includes: using the device network access load to obtain the fault status data of each module in the vehicle-mounted device to be decoded; forwarding the fault status data to the device protocol encoding and decoding service for message decoding to obtain the decoded fault status data of each module in the vehicle-mounted device, and storing it in the message middleware.
[0035] As a specific example, Figure 2 As shown in the figure, a device network access load with high concurrency and high throughput is used to obtain the fault status data set generated by the self-test module on the vehicle-mounted device. In other words, the device network access load is connected to multiple vehicle-mounted devices, and the fault status data set reported by the GPS module corresponding to each vehicle-mounted device is received through the device network access load. After receiving the data, it is forwarded to the corresponding device protocol encoding and decoding service, the device's message is decoded, and forwarded to a message middleware with distributed and high throughput capabilities, realizing the decoupling of the stable load of traffic and the logical processing link.
[0036] It should be noted that the device message refers to the data packet sent by the device. These data are encoded into a specific format (message) and sent to the cloud or data center through a wireless or wired network. Including timestamps, device identifiers, event types, etc., to facilitate real-time computing and fault detection in the cloud. The device protocol encoding and decoding service is responsible for decoding these messages to extract useful information and store it in the message middleware.
[0037] Therefore, the embodiment of the present application uses the message middleware as the buffer and distribution center of the data flow, which helps to achieve the decoupling and scalability of the system and makes the data processing flow more flexible and reliable.
[0038] S102, obtaining fault judgment rules, judging and processing the fault status data within the time window according to the fault judgment rules to obtain corresponding fault result data, and storing the fault result data in the message middleware.
[0039] As a specific embodiment, the real-time computing engine monitors the message queue in the message middleware and waits for new messages to arrive; when new messages (fault status data) arrive, the real-time computing engine obtains these messages from the queue; after obtaining the messages, the real-time computing engine processes these data according to preset rules and algorithms; after processing, the real-time computing engine sends a confirmation signal to the message middleware, indicating that the message has been successfully processed to ensure that the message is not processed repeatedly.
[0040] There are multiple ways to judge and process the fault status data within the time window according to the fault judgment rules.
[0041] As an example, the fault status data within the time window is judged and processed according to the fault judgment rules to obtain the corresponding fault result data, including: obtaining the fault threshold; within the time window, comparing the current fault status data corresponding to each module with the previous fault status data, and recording the number of consecutive faults; if the number of consecutive faults reaches the fault threshold, it is judged that the corresponding module within the time window has a fault; otherwise, it is judged that the corresponding module within the time window has not a fault.
[0042] That is to say, it is determined that a module actually fails only when the number of consecutive failures of any module within a time interval reaches a failure threshold.
[0043] As a specific example, assuming that the time window is defined as one minute, the vehicle-mounted device reports a camera failure once, but reports that the camera is normal ten seconds later, then it is considered that the state of the camera is normal within the time window. In this way, some occasional equipment failures can be ruled out, and some occasional problems, such as poor line contact, can be ruled out, so as to find the real problem, and the workload of operators can be further reduced.
[0044] As another example, the fault status data within the time window is judged and processed according to the fault judgment rules to obtain the corresponding fault result data, including: obtaining the combination relationship of each module in the vehicle-mounted device, wherein each combination relationship includes at least one module in the vehicle-mounted device; within the time window, judging the fault status corresponding to all modules in the combination relationship according to the fault status data of each module; if the fault status corresponding to all modules in the combination relationship are all faults, judging that the corresponding combination relationship within the time window has a fault; otherwise, judging that the corresponding combination relationship within the time window has not a fault.
[0045] In other words, the modules can be freely combined according to actual needs to obtain fault judgment faults corresponding to multiple large modules. For example, according to the fault judgment rules, if the camera fails and the microphone fails at the same time, it is considered an audio and video fault; then an audio and video fault data will be obtained and written to the downstream.
[0046] Specifically, the real-time computing engine will calculate according to the fault judgment rules to obtain the final fault result data. For example, the result of "audio and video failure" and the camera reporting an abnormality, but "camera normal" within the time window is written into the message middleware.
[0047] S103, acquiring fault reporting rules and fault result data, and reporting the fault result data according to the fault reporting rules, so as to perform statistical analysis on the reported fault result data.
[0048] Specifically, Figure 2 As shown, the final fault result data is obtained through the operation system, and a decision is made to report the fault reporting center, wherein the equipment fault handling process is performed according to certain fault reporting rules, which may be thresholds, the addition of fault level labels, and the like.
[0049] Data statistics systems (such as driving behavior data monitoring systems) match different rules based on fault status data (for example, if the camera module of a certain device has failed, then this device should be excluded from the calculation of image recognition accuracy statistics to obtain data that is more in line with actual conditions, etc.), and make data calculations and statistics that are more in line with the actual status of the device.
[0050] In summary, according to the fault status processing method of the vehicle-mounted equipment of the embodiment of the present application, it is possible to monitor the status of each module on the equipment in real time, and identify and report the real fault according to the combination of modules and the rules customized by the operator. The equipment status data is received through the high-concurrency, high-throughput equipment network access load, and then the data is processed through the equipment protocol encoding and decoding service and distributed message middleware. The real-time computing engine compares the status changes according to the configured rules, eliminates occasional faults, and finally writes the fault result data into the message middleware for consumption by the operation system and reporting to the equipment fault processing center, thereby improving the efficiency and accuracy of fault processing.
[0051] In addition, the present application also proposes a computer-readable storage medium on which a fault state processing program of an onboard device is stored. When the fault state processing program of the onboard device is executed by a processor, the fault state processing method of the onboard device as described above is implemented.
[0052] According to the computer-readable storage medium of the embodiment of the present application, by storing the fault status processing program of the vehicle-mounted equipment, the fault status processing method of the vehicle-mounted equipment as described above is implemented when the fault status processing program of the vehicle-mounted equipment is executed by the processor. As a result, the fault status data can be processed in the cloud according to custom rules, and the final processed data can be fed back and analyzed, thereby improving the accuracy of driving risk identification.
[0053] In addition, an embodiment of the present application also proposes a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the fault state processing method of the vehicle-mounted device as described above is implemented.
[0054] According to the computer device of the embodiment of the present application, the fault state processing program of the vehicle-mounted equipment is stored in the memory, so that when the fault state processing program of the vehicle-mounted equipment is executed by the processor, the fault state processing method of the vehicle-mounted equipment as described above is implemented. As a result, the fault state data can be processed in the cloud according to custom rules, and the final data after processing can be fed back and analyzed, thereby improving the accuracy of driving risk identification.
[0055] Figure 3 FIG. 1 is a block diagram of a fault state processing device for an on-board device according to an embodiment of the present application. Figure 3 As shown, the fault status processing device of the vehicle-mounted equipment includes: an acquisition module 10, a judgment processing module 20 and a reporting analysis module 30;
[0056] Among them, the acquisition module 10 is used to obtain the fault status data of each module in the vehicle-mounted equipment from the message middleware; the judgment and processing module 20 is used to obtain the fault judgment rules, and judge and process the fault status data within the time window according to the fault judgment rules to obtain the corresponding fault result data, and store the fault result data in the message middleware; the reporting and analysis module 30 is used to obtain the fault reporting rules and fault result data, and report the fault result data according to the fault reporting rules, so as to perform statistical analysis on the reported fault result data.
[0057] As an embodiment, the acquisition module 10 is also used to use the device network access load to obtain the fault status data of each module in the vehicle-mounted device to be decoded; forward the fault status data to the device protocol encoding and decoding service for message decoding to obtain the decoded fault status data of each module in the vehicle-mounted device, and store it in the message middleware.
[0058] As an embodiment, the judgment processing module 20 is also used to obtain a fault threshold; within a time window, the current fault status data corresponding to each module is compared with the previous fault status data, and the number of consecutive faults is recorded; if the number of consecutive faults reaches the fault threshold, it is judged that the corresponding module within the time window has failed; otherwise, it is judged that the corresponding module within the time window has not failed.
[0059] As an embodiment, the judgment processing module 20 is also used to obtain the combination relationship of each module in the vehicle-mounted device, wherein each combination relationship includes at least one module in the vehicle-mounted device; within the time window, the fault status corresponding to all modules in the combination relationship is judged according to the fault status data of each module; if the fault status corresponding to all modules in the combination relationship are all faults, it is judged that the corresponding combination relationship within the time window has a fault; otherwise, it is judged that the corresponding combination relationship within the time window has not a fault.
[0060] According to the fault status processing device of the vehicle-mounted equipment provided in the embodiment of the present application, it is possible to process the fault status data in the cloud according to custom rules, and perform feedback analysis on the final processed data, thereby improving the accuracy of driving risk identification.
[0061] It should be noted that the above explanations and descriptions of the embodiment of the method for handling a fault state of an on-board device are also applicable to the device for handling a fault state of an on-board device of this embodiment, and will not be repeated here.
[0062] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0063] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0064] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0065] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0066] It should be noted that in the claims, any reference signs placed between brackets shall not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The present application may be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.
[0067] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.
[0068] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
[0069] In the description of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the feature. In the description of the present application, "plurality" means two or more, unless otherwise clearly and specifically defined.
[0070] In this application, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.
[0071] In the present application, unless otherwise clearly specified and limited, a first feature being “above” or “below” a second feature may mean that the first and second features are in direct contact, or the first and second features are in indirect contact through an intermediate medium. Moreover, a first feature being “above”, “above”, and “above” a second feature may mean that the first feature is directly above or obliquely above the second feature, or simply means that the first feature is higher in level than the second feature. A first feature being “below”, “below”, and “below” a second feature may mean that the first feature is directly below or obliquely below the second feature, or simply means that the first feature is lower in level than the second feature.
[0072] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms should not be understood as necessarily being directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.
[0073] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.
Claims
1. A method for handling a fault state of an on-vehicle device, characterized in that: The following steps are involved: Obtain the fault status data of each module in the vehicle-mounted equipment from the message middleware; Obtaining a fault judgment rule, judging and processing the fault status data within the time window according to the fault judgment rule to obtain corresponding fault result data, and storing the fault result data in the message middleware; Acquire a fault reporting rule and the fault result data, and report the fault result data according to the fault reporting rule, so as to perform statistical analysis on the reported fault result data.
2. The method for handling a fault state of an on-vehicle device according to claim 1, characterized in that: Before obtaining the fault status data of each module in the vehicle-mounted device from the message middleware, it also includes: Use the device network to access the load to obtain the fault status data of each module in the vehicle-mounted device to be decoded; The fault status data is forwarded to the device protocol encoding and decoding service for message decoding to obtain the decoded fault status data of each module in the vehicle-mounted device, and the decoded fault status data is stored in the message middleware.
3. The method for handling a fault state of an on-vehicle device according to claim 1, characterized in that: The fault state data within the time window is judged and processed according to the fault judgment rule to obtain corresponding fault result data, including: Get the fault threshold; Within the time window, the current fault status data corresponding to each module is compared with the previous fault status data, and the number of consecutive faults is recorded; If the number of consecutive failures reaches the failure threshold, it is determined that the corresponding module fails within the time window; otherwise, it is determined that the corresponding module does not fail within the time window.
4. The method for handling a fault state of an on-vehicle device according to claim 1, characterized in that: The fault state data within the time window is judged and processed according to the fault judgment rule to obtain corresponding fault result data, including: Acquire a combination relationship of each module in the vehicle-mounted device, wherein each combination relationship includes at least one module in the vehicle-mounted device; In the time window, the fault status corresponding to all modules in the combination relationship is determined according to the fault status data of each module; If the fault states corresponding to all modules in the combination relationship are all faulty, it is determined that the corresponding combination relationship in the time window fails; otherwise, it is determined that the corresponding combination relationship in the time window does not fail.
5. A computer-readable storage medium, characterized in that: A fault state processing program of the vehicle-mounted device is stored thereon, and when the fault state processing program of the vehicle-mounted device is executed by the processor, a fault state processing method of the vehicle-mounted device as described in any one of claims 1 to 4 is implemented.
6. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the fault state processing method of the vehicle-mounted device according to any one of claims 1 to 4 is implemented.
7. A fault state processing device for vehicle-mounted equipment, characterized in that: include: An acquisition module is used to obtain the fault status data of each module in the vehicle-mounted device from the message middleware; A judgment processing module is used to obtain a fault judgment rule, judge and process the fault status data within the time window according to the fault judgment rule to obtain corresponding fault result data, and store the fault result data in the message middleware; The reporting and analysis module is used to obtain the fault reporting rules and the fault result data, and report the fault result data according to the fault reporting rules so as to perform statistical analysis on the reported fault result data.
8. The fault state processing device of the vehicle-mounted equipment according to claim 7, characterized in that: The acquisition module is also used to use the device network access load to obtain the fault status data of each module in the vehicle-mounted device to be decoded; forward the fault status data to the device protocol encoding and decoding service for message decoding to obtain the decoded fault status data of each module in the vehicle-mounted device, and store it in the message middleware.
9. The fault state processing device of the vehicle-mounted equipment according to claim 7, characterized in that: The judgment processing module is also used to obtain a fault threshold; compare the current fault status data corresponding to each module with the previous fault status data within the time window, and record the number of consecutive faults; If the number of consecutive failures reaches the failure threshold, it is determined that the corresponding module fails within the time window; Otherwise, it is determined that the corresponding module has not failed within the time window.
10. The fault state processing device of the vehicle-mounted equipment according to claim 7, characterized in that: The judgment and processing module is also used to obtain the combination relationship of each module in the vehicle-mounted device, wherein each combination relationship includes at least one module in the vehicle-mounted device; within a time window, the fault status corresponding to all modules in the combination relationship is judged according to the fault status data of each module; if the fault status corresponding to all modules in the combination relationship are all faults, it is judged that the corresponding combination relationship within the time window has a fault; otherwise, it is judged that the corresponding combination relationship within the time window has not a fault.