Fault diagnosis method, device, equipment and medium based on vehicle system log

By constructing a fault diagnosis method for vehicle system logs, and using the first correspondence and fault diagnosis graph to analyze the log text of logical links and sub-node events, the problem of quickly and accurately determining the cause of vehicle faults is solved, thereby improving fault repair speed and customer satisfaction.

CN118646637BActive Publication Date: 2024-11-05JIANGXI JINGWEI HENGRUN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411095872.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-09
Publication Date
2024-11-05
Estimated Expiration
2044-08-09

AI Technical Summary

Technical Problem

Existing technologies make it difficult to quickly and accurately determine the cause of vehicle malfunctions, which affects vehicle operation and customer satisfaction.

Method used

By constructing a fault diagnosis method based on vehicle system logs, the system event set is determined using the first correspondence relationship, and the log text of logical links and sub-node events is analyzed in conjunction with the fault diagnosis graph to determine the cause of the fault.

Benefits of technology

It improved the speed of fault repair and customer satisfaction, and achieved rapid and accurate fault diagnosis.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118646637B_ABST
    Figure CN118646637B_ABST
Patent Text Reader

Abstract

The present application discloses a fault diagnosis method, device, equipment and medium based on a vehicle-mounted system log, and relates to the field of communication technology. Specifically, it includes: based on the target fault and the first corresponding relationship, determining multiple root node system events corresponding to the target fault as a system event set; based on the system event set and the fault diagnosis map, determining multiple logical links corresponding to each root node system event in the system event set as a logical link set; wherein each logical link connects in series the sub-node events with a logical relationship that cause the corresponding root node system event to occur; analyzing the log text corresponding to the sub-node events involved in each logical link in the logical link set to determine the cause of the target fault. The method in the present application can efficiently determine the cause of the target fault, thereby increasing the speed of repairing the target fault and improving customer satisfaction.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a fault diagnosis method, device, equipment and medium based on a vehicle-mounted system log. Background Art

[0002] During the use of vehicles, vehicle failures are inevitable, such as abnormal sound, abnormal navigation, abnormal lights or abnormal fuel consumption, which affect the operation of the vehicle. With the development of automobile technology, more and more vehicles are equipped with on-board systems, such as one or more of navigation systems, reversing systems, automatic driving systems and braking systems. How to quickly and accurately determine the cause of vehicle failures based on on-board system logs has become an urgent problem to be solved. Summary of the invention

[0003] Based on the above problems, the present application provides a fault diagnosis method based on the vehicle system log, which is used to quickly and accurately determine the cause of the vehicle failure based on the vehicle system log, thereby improving the fault repair speed and improving customer satisfaction.

[0004] The embodiments of the present application disclose the following technical solutions:

[0005] The first aspect of the present application provides a fault diagnosis method based on a vehicle system log, comprising:

[0006] Based on the target fault and the first corresponding relationship, a plurality of root node system events corresponding to the target fault are determined as a system event set; the first corresponding relationship represents a plurality of root node system events corresponding to each vehicle fault among a plurality of vehicle faults; the root node system event is an event generated by the vehicle system and perceptible to the outside world; the target fault is any one of the plurality of vehicle faults;

[0007] Based on the system event set and the fault diagnosis map, multiple logical links corresponding to each root node system event in the system event set are determined as a logical link set; each logical link is connected in series with logically related sub-node events that cause the corresponding root node system event to occur; the fault diagnosis map includes a root node system event, multiple sub-node events that participate in the generation of the root node system event, and the logical relationship between the multiple sub-node events; the sub-node event is an event generated by a subsystem of the vehicle-mounted system and perceivable by other subsystems;

[0008] Analyze the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target failure.

[0009] In an optional implementation, analyzing the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target fault includes:

[0010] Determining the priority of each logical link in the logical link set;

[0011] According to the order of priority of the logical links from high to low, the log texts of the sub-node events involved in the corresponding logical links are analyzed to determine the cause of the target failure.

[0012] In an optional implementation, constructing the fault diagnosis map includes:

[0013] Constructing a software behavior graph of the software in the vehicle system; the software behavior graph includes a software event, multiple software behaviors involved in the generation of the software event, and a logical relationship between the multiple software behaviors involved in the generation of the software event; the software behavior is each operation performed inside the software; the software event is an event generated by the software and perceivable by other software in the vehicle system;

[0014] Based on the prior relationship between the software in the vehicle system, constructing a priori relationship model; the priori relationship is a logical relationship between the software known before building the vehicle system;

[0015] The fault diagnosis graph is constructed by connecting a plurality of the software behavior graphs and the prior relationship model through the software events.

[0016] In an optional implementation, the step of constructing a software behavior graph of the software in the vehicle-mounted system includes:

[0017] Determine the target software; the target software is any software in the vehicle system;

[0018] Determine a plurality of software behaviors, a plurality of software events, and a log matching pattern corresponding to each software behavior of the target software; the log matching pattern refers to a log template corresponding to the software behavior;

[0019] Based on the correspondence between the software events and software behaviors of the target software, multiple software behaviors of the target software, multiple software events and log matching patterns corresponding to each software behavior, a software behavior graph of the target software is constructed.

[0020] In an optional implementation, the vehicle-mounted system includes a plurality of subsystems, and the constructing of the prior relationship model based on the prior relationship between software in the vehicle-mounted system includes:

[0021] For each subsystem of the plurality of subsystems, constructing a sub-a priori relationship model based on a priori relationships between software included in the subsystem;

[0022] The priori relationship model is constructed based on the priori relationships between the multiple subsystems and the priori relationship model of each subsystem.

[0023] In an optional implementation, the method further includes:

[0024] Acquire a second corresponding relationship; the second corresponding relationship represents the corresponding relationship between the vehicle faults other than the multiple vehicle faults and the multiple system events;

[0025] The second corresponding relationship is added to the first corresponding relationship to obtain an updated first corresponding relationship.

[0026] A second aspect of the present application provides a fault diagnosis device based on a vehicle-mounted system log, comprising:

[0027] A system event set determination module, configured to determine, based on a target fault and a first corresponding relationship, a plurality of root node system events corresponding to the target fault as a system event set; the first corresponding relationship represents a plurality of root node system events corresponding to each vehicle fault among a plurality of vehicle faults; the root node system event is an event generated by an onboard system and perceptible to the outside world; the target fault is any one of the plurality of vehicle faults;

[0028] A logic link set determination module is used to determine, based on the system event set and the fault diagnosis map, a plurality of logic links corresponding to each root node system event in the system event set as a logic link set; each logic link is connected in series with a logically related sub-node event that causes the corresponding root node system event to occur; the fault diagnosis map includes a root node system event, a plurality of sub-node events that participate in the generation of the root node system event, and a logical relationship between the plurality of sub-node events; the sub-node event is an event generated by a subsystem of the vehicle-mounted system and perceivable by other subsystems;

[0029] The fault cause determination module is used to analyze the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target fault.

[0030] In an optional implementation, the fault cause determination module includes:

[0031] A priority determination unit, used to determine the priority of each logical link in the logical link set;

[0032] The fault cause determination unit is used to analyze the log text of the software events involved in the corresponding logical link in the order of the priority of the logical link from high to low, and determine the cause of the target fault.

[0033] A third aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method introduced in any implementation manner of the first aspect.

[0034] A fourth aspect of the present application provides an electronic device, including:

[0035] a memory having a computer program stored thereon;

[0036] A processor is used to execute the computer program in the memory to implement the steps of the method introduced in any implementation manner of the first aspect.

[0037] Compared with the prior art, this application has the following beneficial effects:

[0038] The fault diagnosis method based on the vehicle system log disclosed in the present application determines the system event set corresponding to the target fault through a first corresponding relationship; determines the logical link set corresponding to each root node system event in the system event set based on the root node system event included in the fault diagnosis map, multiple sub-node events participating in the generation of the root node system event, and the logical relationship between the multiple sub-node events; each logical link in the logical link set connects in series multiple sub-node events with a logical relationship that cause the root node system event to occur; and ultimately determines the cause of the target fault by analyzing the log text corresponding to the sub-node events involved in each logical link in the logical link set.

[0039] Because in the present application, the system event set corresponding to the target fault can be determined efficiently and accurately through the first corresponding relationship; the logical link set corresponding to each root node system event in the system event set can be determined efficiently and accurately through the fault diagnosis map, that is, the multiple sub-node events that may cause each root node system event to occur can be determined; by analyzing the log text corresponding to the sub-node events, the cause of the target fault can be efficiently determined, thereby improving the repair speed of the target fault and improving customer satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0041] Figure 1 A flowchart of a fault diagnosis method based on a vehicle system log provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of a structure of a node relationship provided in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of the structure of a software behavior model provided in an embodiment of the present application;

[0044] Figure 4 A schematic diagram of the structure of a sub-prior relationship model provided in an embodiment of the present application;

[0045] Figure 5 A schematic diagram of the structure of a log diagnosis tree model of a node provided in an embodiment of the present application;

[0046] Figure 6 A schematic diagram of the structure of a fault diagnosis device based on a vehicle system log provided in an embodiment of the present application;

[0047] Figure 7 A schematic structural diagram of another vehicle-mounted system log-based fault diagnosis device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] As mentioned above, vehicle failures are inevitable during vehicle use, such as abnormal sound, navigation, lights, or fuel consumption, which affect vehicle operation. With the development of automotive technology, more and more vehicles are equipped with onboard systems, such as one or more of navigation systems, reversing systems, automatic driving systems, and braking systems. How to quickly and accurately determine the cause of vehicle failures based on onboard system logs has become an urgent problem to be solved.

[0049] The fault diagnosis method based on the vehicle system log disclosed in the present application determines the system event set corresponding to the target fault through a first corresponding relationship; determines the logical link set corresponding to each root node system event in the system event set based on the root node system event included in the fault diagnosis map, multiple sub-node events participating in the generation of the root node system event, and the logical relationship between the multiple sub-node events; each logical link in the logical link set connects in series multiple sub-node events with a logical relationship that cause the root node system event to occur; and ultimately determines the cause of the target fault by analyzing the log text corresponding to the sub-node events involved in each logical link in the logical link set.

[0050] Because in the present application, the system event set corresponding to the target fault can be determined efficiently and accurately through the first corresponding relationship; the logical link set corresponding to each root node system event in the system event set can be determined efficiently and accurately through the fault diagnosis map, that is, the multiple sub-node events that may cause each root node system event to occur can be determined; by analyzing the log text corresponding to the sub-node events, the cause of the target fault can be efficiently determined, thereby improving the repair speed of the target fault and improving customer satisfaction.

[0051] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0052] The vehicle-mounted system in this application is the whole vehicle system. Specifically, if the vehicle is equipped with an intelligent driving system, a reversing system and a navigation system, the vehicle-mounted system in this application includes the intelligent driving system, the reversing system and the navigation system. Therefore, the vehicle-mounted system in this application is the sum of all the systems installed on the vehicle; the system installed on the vehicle is a subsystem of the whole vehicle system.

[0053] It is understandable that each subsystem in the vehicle system includes multiple small systems, and each small system can also include a lot of software. For example, if the intelligent driving system is a subsystem of the vehicle system, the radar system, vision system, high-performance computing system, etc. included in the intelligent driving system are all small systems included in the subsystem. The radar system includes multiple software, and through the mutual cooperation of multiple software, the radar system ultimately realizes specific functions.

[0054] Figure 1 A flowchart of a fault diagnosis method based on a vehicle system log provided in an embodiment of the present application. Figure 1 As shown, the fault diagnosis method based on the vehicle system log in the present application includes:

[0055] Step 101: Based on a target fault and a first corresponding relationship, a plurality of root node system events corresponding to the target fault are determined as a system event set.

[0056] The root node system event is a user-perceivable event generated by the vehicle system in this application. The root node system event can represent what went wrong in the vehicle system. If the vehicle system is an autonomous driving system, the root node system event is a user-perceivable event generated by the autonomous driving system. For example, the vehicle automatically wakes up, starts and sleeps, automatically enters and exits the parking lot, automatically drives, automatically parks, and automatically opens and closes the door.

[0057] The target fault is one of the multiple vehicle faults. The first corresponding relationship represents multiple root node system events corresponding to each of the multiple vehicle faults.

[0058] In an optional implementation, a problem translation model can be constructed based on the first corresponding relationship, and the model includes a fault list, a root node system event set, and a mapping relationship set between the two. The fault list includes multiple vehicle fault problems, and the content in the fault list can be adjusted based on actual conditions. Each vehicle fault problem in the multiple vehicle fault problems has a corresponding relationship with multiple root node system events in the root node system event set.

[0059] When the target fault is a problem in the fault list, multiple root node system events corresponding to the target fault can be determined as the system event set based on the correspondence between the faults in the fault list recorded in the problem translation model and the root node system events in the root node system event set.

[0060] Step 102: Based on the system event set and the fault diagnosis map, a plurality of logical links corresponding to each root node system event in the system event set are determined as a logical link set.

[0061] The fault diagnosis map is also called a log diagnosis tree model. The fault diagnosis map includes a root node system event, multiple sub-node system events that participate in the generation of the root node system event, and the logical relationship between the multiple sub-node system events that participate in the generation of the root node system event. Among them, the sub-node event is an event generated by a subsystem of the vehicle system and can be perceived by other subsystems. The subsequent embodiments of this application will introduce in detail the specific method of constructing a log diagnosis tree model.

[0062] As mentioned above, if the vehicle system includes the intelligent driving system, the reversing system and the navigation system, then the intelligent driving system, the reversing system and the navigation system are subsystems of the vehicle system. The events generated by the vehicle system that can be perceived by the user are root node events; the intelligent driving system is a subsystem, and the events generated by it that can be perceived by other subsystems such as the reversing system and the navigation system are subnode events.

[0063] It can be understood that if the on-board system only includes an intelligent driving system, then the events generated by the intelligent driving system as a whole vehicle system are root node system events; the radar system, vision system and high-performance computing system included in the intelligent driving system are all subsystems of the whole vehicle system, and the events generated by subsystems such as the radar system that can be perceived by other subsystems such as the vision system or the high-performance system are sub-node events.

[0064] Since the fault diagnosis map clarifies the logical relationship between each root node system event and the multiple sub-node events that generate the root node system event, after determining the root node system event, by parsing the fault diagnosis map, multiple logical links corresponding to each root node system event in the system event set can be obtained as a logical link set. Among them, each logical link is connected in series with the sub-node events with logical relationships that cause the corresponding root node system event to occur.

[0065] Figure 2 A schematic diagram of a structure of a node relationship provided in an embodiment of the present application. Figure 2 As can be seen from the figure, the events of node A and node B are used as inputs of node C, and the events of node C, node D, and node E are used as inputs of node F. If node F is a root node, the event of node F is a root node system event.

[0066] Further, if it is determined that the root node system event corresponding to the target fault is the system event of node F, then Figure 2 The node relationship can determine the logical link set corresponding to the system event of node F. The logical links in the logical link set can be: node F-node C-node A; node F-node C-node B; node F-node D; node F-node E; node F-node D and node E, etc.

[0067] Furthermore, the logical links in the logical link set can be analyzed to analyze the search width and search depth of each logical link. The search width represents the number of nodes included in the corresponding logical link, that is, the number of nodes that need to be searched; the search depth represents the level of the root node in the corresponding logical link. For example, if the logical link is node F-node C-node A, the corresponding search width is 3 and the search depth is 3; if node F-node D and node E, the corresponding search width is 3 and the search depth is 2.

[0068] To summarize, after the system event set determined in step 101 is input into the fault diagnosis map, since the fault diagnosis map includes the correspondence between sub-node events and root node system events, multiple logical links that lead to the occurrence of the root node system event can be determined; each logical link is connected in series with multiple sub-nodes with a logical relationship that lead to the occurrence of the root node system event.

[0069] Step 103: Analyze the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target failure.

[0070] As mentioned above, subnode events are events generated by a subsystem of the vehicle system and can be perceived by other subsystems in the vehicle system. Since a subsystem can include multiple small systems, and each small system can include multiple software, subnode events are events generated based on multiple logically related software events. Software events are events generated by software and can be perceived by other software in the small system.

[0071] Since each software behavior has a corresponding log matching pattern, the log matching pattern can be used to analyze the content of the obtained log text to determine whether the behavior in the target software occurs, and finally determine the cause of the target failure. Among them, the log matching pattern can also be called the software matching pattern, which is an abstract expression of multiple software logs with the same points, and is a log template.

[0072] In summary, in the present application, the first corresponding relationship can be used to efficiently and accurately determine the set of system events corresponding to the target fault; the fault diagnosis map can be used to efficiently and accurately determine the set of logical links corresponding to each root node system event in the system event set, that is, to determine multiple sub-node events that may cause each root node system event to occur; by analyzing the log text corresponding to the sub-node events, the cause of the target fault can be efficiently determined, thereby improving the speed of repairing the target fault and improving customer satisfaction.

[0073] In an optional implementation, the log text corresponding to the sub-node events involved in each logical link in the logical link set is analyzed to determine the cause of the target failure, including: determining the priority of each logical link in the logical link set; and analyzing the log text of the sub-node events involved in the corresponding logical links in order of the priority of the logical links from high to low to determine the cause of the target failure.

[0074] Since the logical link set determined by the method in steps 101 to 103 may include multiple logical links and each logical link may include multiple sub-node events, in order to improve the efficiency of determining the cause of the target failure, a priority may be configured for each logical link in the logical link set; then, the log text of the sub-node events involved in the corresponding logical link is analyzed in order of priority from high to low, so as to determine the cause of the target failure.

[0075] It should be noted that the present application is not limited to the specific implementation method of configuring the priority of the logical link; after determining the cause of the target failure in order of priority from high to low, the technical personnel in this field can also suspend the analysis of the log text of the sub-node events in the logical links with lower priority and not yet analyzed according to actual work needs; of course, the technical personnel in this field can continue the analysis until the log text analysis of the sub-node events involved in all logical links is completed.

[0076] To summarize, by configuring a priority for each logical link and analyzing the log text of the sub-node events involved in the corresponding logical link in order of priority from high to low, that is, first analyzing the log text corresponding to the sub-node events in the logical link that is more likely to cause the root node system event, the efficiency of determining the cause of the target fault can be improved, the speed of repairing the target fault can be further improved, and customer satisfaction can be improved.

[0077] In one possible implementation, a software behavior graph (also called a "software behavior model") of the software in the vehicle system can be constructed first; then a priori relationship model between software can be constructed; finally, the software behavior graph and the priori relationship model can be connected through software events to obtain a fault diagnosis graph.

[0078] Figure 3 A schematic diagram of the structure of a software behavior model provided in an embodiment of the present application. Figure 3 As shown, the software behavior model of the present application includes: multiple software behaviors, such as software behavior 1 and software behavior n, where n is a positive integer greater than or equal to 1; multiple log matching patterns, such as log matching pattern 1 and log matching pattern n; multiple software events, such as software event 1 and software event m, where m is a positive integer greater than or equal to 1; and the corresponding relationship between software events and software behaviors.

[0079] Software behavior refers to the operations performed by the software. For example, if software A reads file 1, then the action of reading file 1 is a behavior of software A. After software A successfully reads file 1, it will output a log of successful reading of file 1. Each software behavior corresponds to a software log. It should be noted that each line of code in the software represents a software behavior. This application focuses on the effective software behaviors that need to be focused on to solve the target problem, rather than all software behaviors of the software.

[0080] from Figure 3It can be seen that the log matching pattern and the software behavior are one-to-one corresponding; for example, software behavior 1 corresponds to log matching pattern 1, and software behavior n corresponds to log matching pattern n. The software log is introduced in the above embodiment. It should be noted that the software matching pattern and the software log are not the same. The software matching pattern is an abstract expression of multiple software logs with the same points, and is a log template. The software behavior and the log matching pattern are one-to-one corresponding. Each software behavior has a corresponding log matching pattern.

[0081] For example, software A has two software behaviors, namely software behavior 1 and software behavior 2. Software behavior 1 is that software A successfully reads file 1 and outputs a software log (also called "text log" or "log text") that software A successfully reads file 1; software behavior 2 is that software A successfully reads file 2 and outputs that software A successfully reads file 2; then the log matching pattern for the corresponding software behavior (including software behavior 1 and software behavior 2) is: reading "something" successfully. "Something" can be file 1 or file 2.

[0082] Software events refer to events that software exposes to the outside world. As mentioned above, each software has many behaviors. For example, after obtaining the sound source to be processed, a sound processing software will perform various processes such as noise reduction and filtering on the sound source to be processed, that is, multiple software behaviors will occur to obtain processed sound source data. Since the sound processing software ultimately exposes the processed sound source data to the outside world, the processed sound source data is the event exposed by the sound processing software to the outside world.

[0083] Software events are related to various software behaviors. The software behavior model also includes the corresponding relationship between software events and software behaviors. Figure 3 The curly brackets in indicate that software behavior 1 and software behavior n occur together or successively, resulting in the occurrence of software event 1. It should be noted that the software behavior model is configured in the form of a configuration file.

[0084] In an optional implementation, constructing a software behavior graph of the software in the vehicle system includes: determining the target software; the target software is any software in the vehicle system; determining multiple software behaviors, multiple software events and log matching patterns corresponding to each software behavior of the target software; the log matching pattern refers to a log template corresponding to the software behavior; based on the correspondence between the software events and software behaviors of the target software, the multiple software behaviors and multiple software events of the target software, constructing the software behavior graph of the target software.

[0085] Specifically, a software behavior model (software behavior graph) of each software is constructed based on the behavior of each software, the log matching pattern corresponding to the behavior of each software, the events exposed to the outside world by each software (software events), and the correspondence between software behavior and software events.

[0086] In an optional implementation, the vehicle-mounted system includes multiple subsystems, and the prior relationship model is constructed based on the prior relationship between the software in the vehicle-mounted system, including: for each subsystem in the multiple subsystems, based on the prior relationship between the software included in the subsystem, a sub-prior relationship model is constructed; based on the prior relationship between the subsystems in the multiple subsystems and the subsystem prior relationship model, a prior relationship model is constructed.

[0087] Specifically, the prior relationship models between multiple software constitute the subsystem prior relationship model; after the child node is abstracted as the subsystem prior relationship model, it is connected to the node of the previous level through system events (the node of the previous level is called the parent node of the child node); the parent node forms the parent node prior relationship model based on the combination of the software behavior model within the node and the subsystem prior relationship model, and in this way, it is configured upward to the root node in sequence to obtain the prior relationship model.

[0088] by Figure 2 For example, node A and node B are child nodes, then node C is the node of the upper level of node A and node B, that is, node C is the parent node of node A and node B. After obtaining the child prior relationship model of node A and the child prior relationship model of node B, connect with node C through the node event of node A and the node event of node B; combine the software behavior model and the subsystem prior relationship model in node C into the parent node prior relationship model of node C, and in this way, go up to the root node F in sequence to obtain the prior relationship model.

[0089] The sub-prior relationship model includes the set of all software events of the two software and the set of all system events that can be mapped by the two software, the relationship between software events (including but not limited to equivalence relationship, causal relationship, sequential relationship, mutual exclusion relationship, inclusion relationship, combination relationship, etc.), the mapping relationship between software events or software event combinations and system events, and the mapping relationship priority (multiple software behaviors may be mapped to the same software event, or one software behavior may be mapped to multiple software events, so it is necessary to set the priority and select the logical link with the highest comprehensive priority for problem log diagnosis when diagnosing the problem).

[0090] Figure 4 A schematic diagram of the structure of a sub-prior relationship model provided in an embodiment of the present application. Figure 4Taking the sub-a priori relationship model composed of software 1 and software 2 as an example, the specific structure of the sub-a priori relationship model is introduced. The sub-a priori relationship model includes: software 1 software event set (a set of all software events exposed to the outside world by software 1), software 2 software event set (a set of all software events exposed to the outside world by software 2); software 1 and software 2 can correspond to multiple system events through various logical relationships included in the mapping relationship set, including but not limited to equivalence relationship, causal relationship, sequential relationship, mutual exclusion relationship, inclusion relationship, combination relationship, etc., such as system event 1, system event 2, and system event n1, where n1 is a positive integer greater than or equal to 2.

[0091] It is understandable that the vehicle system includes multiple subsystems, each subsystem includes multiple software, and each software can expose multiple software events. Through the software set between two software, the mapping relationship set between the two software, and the multiple system events that the two software can cause, the prior relationship model between the two software can be constructed, that is, the sub-prior relationship model is obtained; based on multiple sub-prior relationship models, the subsystem prior relationship model is obtained; multiple subsystem prior relationship models can eventually obtain the system prior relationship model.

[0092] It should be noted that the a priori relationship in the a priori relationship model in this application refers to the correspondence between software and system events known to technical personnel in this field when making the system, as well as the correspondence between subsystem events and root node system events.

[0093] It should be noted that the significance of constructing a priori relationship model is to further simplify software events into sub-node events, and simplify sub-node events into root-node system events. Because for the vehicle system, the root-node system events are the events exposed to users.

[0094] After clarifying the relationship between the software behavior model of the child node and the child prior relationship model, the subsystem prior relationship model and the system prior relationship model, a log diagnosis tree model can be constructed based on the correspondence between nodes, that is, the correspondence between child nodes, parent nodes and root nodes (also called the inheritance relationship between models).

[0095] Figure 5 A schematic diagram of the structure of a log diagnosis tree model of a node provided in an embodiment of the present application. Figure 5 As shown, the log diagnosis tree model of the node includes: behavior model-1 of software-1, behavior model-2 of software-2 and behavior model-3 of software-3; prior relationship model 1, prior relationship model 2, prior relationship model 3 and sub-node system prior relationship model (i.e., subsystem prior relationship model).

[0096] Through the software events exposed by each software, the software behavior model and the prior relationship model are connected, and finally the Figure 5 Log diagnostic tree model of the nodes shown in .

[0097] Since the vehicle system is ultimately abstracted to the root node system event, the root node system event is limited, and new vehicle faults that occur during use can be continuously added to the fault list. Therefore, when the vehicle fault (i.e., the fault problem) is not in the fault list, multiple root node system events corresponding to the fault problem can be determined through analysis; and the above fault problem can be added to the fault list, and the corresponding relationship between the fault problem and multiple root node system events can be added to the first relationship.

[0098] In an optional implementation, a second correspondence may be obtained; the second correspondence represents the correspondence between vehicle faults outside the fault list and multiple system events; the second correspondence is added to the first correspondence to obtain an updated first correspondence. The problems in the fault list are continuously enriched.

[0099] To sum up, the fault diagnosis method based on the vehicle system log disclosed in the present application is scalable, that is, it can be gradually expanded from the log diagnosis tree model of a single software to the log diagnosis tree model of the entire vehicle; it has instant problem analysis, and for new problems, it is only necessary to identify the root node system events related to the problem to diagnose the problem, and the root node system events are abstract problems facing users. The correspondence between new problems and root node system events is usually obvious or easy to identify, so new problems can be analyzed instantly.

[0100] The fault diagnosis method based on the vehicle system log disclosed in this application has good loose coupling properties, which is conducive to the collaboration between different manufacturers and reduces the difficulty and cost of building a log diagnosis tree model. Specifically, the parent node does not need to care about the internal software implementation of the child node, but only needs to know the system events exposed by the child node. The set of system events exposed by the node is usually defined by the parent node, so the log diagnosis tree model (log diagnosis map) of the child node and the parent node can be built in parallel.

[0101] The fault diagnosis method based on the vehicle system log disclosed in this application can be applied to various stages of the project life cycle. For example, in the project development stage, the behavior model corresponding to a single software in the controller is the log diagnosis tree of the software; in the project testing stage, each software in the vehicle ECU (Electronic Control Unit) is abstracted as a software behavior model (software behavior map), and the relationship between each software behavior model is mapped to the ECU system event through the prior relationship model, forming a tree with the controller system as the root node and each software as the end node. The tree is the log analysis model of the controller. Software testing problems can be quickly diagnosed through the log diagnosis tree model to find specific failed software and possible software failure causes, which is convenient for testers to attribute problems and formulate test plans, and also convenient for developers to locate program vulnerabilities and save development time; in the project mass production and maintenance stage, the log diagnosis tree model of each ECU is connected and combined through the prior relationship model between each ECU, and finally forms a tree with the root node as the whole vehicle, each controller as a child node, and the controlled software as the end node. The whole vehicle fault problem can be quickly located through the log diagnosis tree model, shortening the problem solving time and reducing customer complaints.

[0102] Based on the fault diagnosis method based on the vehicle-mounted system log provided in the aforementioned embodiment, the present application also provides a fault diagnosis device based on the vehicle-mounted system log. Figure 6 A schematic diagram of the structure of a fault diagnosis device based on a vehicle system log provided in an embodiment of the present application.

[0103] Combination Figure 6 As shown, the fault diagnosis device based on the vehicle system log in the present application includes: a log collection unit, a problem translation unit, a log diagnosis tree unit, a parsing unit, and a problem input and configuration unit.

[0104] Among them, the log collection unit is used to collect log files; the problem translation unit is used to translate vehicle faults into corresponding system event sets; the log diagnosis tree unit is used to store pre-configured behavior model maps (i.e., software behavior maps) and prior relationship models; the parsing unit is used to parse the system event set obtained by the problem translation unit according to the content stored in the log diagnosis tree unit, obtain the software behavior that needs to be observed and the corresponding log matching pattern, and retrieve the required log files from the log files collected by the log collection unit according to the obtained log matching pattern, and then analyze the retrieved log files to obtain the cause of the vehicle fault; the cause of the vehicle fault is output to the interactive interface where the problem input and configuration unit is located, and presented to the user to complete the diagnosis of the vehicle fault.

[0105] Figure 6The relationship between the various units in the fault diagnosis device is: the behavior model map and the prior relationship model in the log diagnosis tree unit that the parsing unit needs to use are set through the problem input and configuration unit. Among them, the behavior model map and the prior relationship model can be configured through the configuration file, and can also be tailored through the interactive interface where the problem input and configuration unit are located to avoid retrieving software behaviors that are irrelevant to the problem of concern.

[0106] During use, the vehicle fault is transmitted to the problem translation unit through the problem input and configuration unit. For the problem that the problem translation unit cannot translate, the user can manually configure the root node system event corresponding to the problem in the problem input and configuration unit; the problem translation unit translates the problem into a system event set, and inputs the system set to the parsing unit; the parsing unit parses the software behavior that ultimately needs to be observed and the corresponding log matching pattern based on the input system event set and the content stored in the log diagnosis tree unit, and retrieves the required log file from the log file collected by the log collection unit based on the obtained log matching pattern; the parsing unit then analyzes the retrieved log file to obtain the cause of the vehicle fault, and outputs the analysis result to the interactive interface where the problem input and configuration unit is located to complete the problem diagnosis.

[0107] Figure 7 A schematic diagram of the structure of another fault diagnosis device based on a vehicle system log provided in an embodiment of the present application. Figure 7 As shown, the fault diagnosis device 700 in the present application includes:

[0108] The system event set determination module 701 is used to determine, based on the target fault and the first corresponding relationship, a plurality of root node system events corresponding to the target fault as the system event set; the first corresponding relationship represents a plurality of root node system events corresponding to each vehicle fault among the plurality of vehicle faults; the root node system event is an event generated by the vehicle system and perceptible to the outside world; the target fault is any one of the plurality of vehicle faults;

[0109] The logical link set determination module 702 is used to determine, based on the system event set and the fault diagnosis map, a plurality of logical links corresponding to each root node system event in the system event set as a logical link set; each logical link is connected in series with the logically related sub-node events that cause the corresponding root node system event to occur; the fault diagnosis map includes the root node system event, a plurality of sub-node events that participate in the generation of the root node system event, and the logical relationship between the plurality of sub-node events; the sub-node event is an event generated by a subsystem of the vehicle-mounted system and perceivable by other subsystems;

[0110] The fault cause determination module 703 is used to analyze the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target fault.

[0111] In an optional implementation, the fault cause determination module 703 includes:

[0112] A priority determination unit, used to determine the priority of each logical link in the logical link set;

[0113] The fault cause determination unit is used to analyze the log text of the software events involved in the corresponding logical link in the order of the priority of the logical link from high to low, and determine the cause of the target fault.

[0114] In an optional implementation, the fault diagnosis device 700 further includes a fault diagnosis map construction module, and the fault diagnosis map construction module includes:

[0115] A software behavior graph construction submodule is used to construct a software behavior graph of the software in the vehicle system; the software behavior graph includes a software event, a plurality of software behaviors involved in the generation of the software event, and a logical relationship between the plurality of software behaviors involved in the generation of the software event; the software behavior is each operation performed inside the software; the software event is an event generated by the software and perceivable by other software in the vehicle system;

[0116] A priori relationship building submodule, used to build a priori relationship model based on the priori relationship between the software in the vehicle system; the priori relationship is a logical relationship between the software known before building the vehicle system;

[0117] The fault diagnosis graph construction submodule is used to connect a plurality of the software behavior graphs and the prior relationship model through the software events to construct the fault diagnosis graph.

[0118] In an optional implementation, the software behavior graph construction submodule includes:

[0119] Determine the target software; the target software is any software in the vehicle system;

[0120] A first data acquisition unit is used to determine a plurality of software behaviors, a plurality of software events and a log matching pattern corresponding to each software behavior of the target software; the log matching pattern refers to a log template corresponding to the software behavior;

[0121] The software behavior graph construction unit is used to construct a software behavior graph of the target software based on the correspondence between the software events and software behaviors of the target software, multiple software behaviors of the target software, multiple software events and log matching patterns corresponding to each software behavior.

[0122] In an optional implementation, the prior relationship construction submodule includes:

[0123] A sub-a priori relationship model construction unit, configured to construct a sub-a priori relationship model for each of the plurality of subsystems based on the a priori relationship between software included in the subsystem;

[0124] The prior relationship model construction unit is used to construct the prior relationship model based on the prior relationship between the multiple subsystems and the prior relationship model of each subsystem.

[0125] In an optional implementation, the fault diagnosis device 700 further includes:

[0126] A second correspondence acquisition unit, configured to acquire a second correspondence; the second correspondence represents a correspondence between a vehicle fault other than the multiple vehicle faults and multiple system events;

[0127] The first correspondence updating unit is configured to add the second correspondence to the first correspondence to obtain an updated first correspondence.

[0128] Based on the fault diagnosis method and device based on the vehicle system log provided in the aforementioned embodiments, accordingly, the present application also provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements some or all of the steps in the fault diagnosis method based on the vehicle system log mentioned above.

[0129] Based on the fault diagnosis method and device based on the vehicle system log provided in the above-mentioned embodiment, the present application further provides an electronic device, including:

[0130] a memory having a computer program stored thereon;

[0131] The processor is used to execute the computer program in the memory to implement part or all of the steps in the fault diagnosis method based on the vehicle system log provided in the above embodiment.

[0132] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely schematic, in which the unit described as a separate component may or may not be physically separated, and the component prompted as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0133] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A fault diagnosis method based on vehicle system log, It is characterized in that The method comprises: Based on the target fault and the first corresponding relationship, a plurality of root node system events corresponding to the target fault are determined as a system event set; the first corresponding relationship represents a plurality of root node system events corresponding to each vehicle fault among a plurality of vehicle faults; the root node system event is an event generated by the vehicle system and perceptible to the outside world; the target fault is any one of the plurality of vehicle faults; Based on the system event set and the fault diagnosis map, multiple logical links corresponding to each root node system event in the system event set are determined as a logical link set; each logical link is connected in series with logically related sub-node events that cause the corresponding root node system event to occur; the fault diagnosis map includes a root node system event, multiple sub-node events that participate in the generation of the root node system event, and the logical relationship between the multiple sub-node events; the sub-node event is an event generated by a subsystem of the vehicle-mounted system and perceivable by other subsystems; Analyze the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target failure; Constructing the fault diagnosis map includes: constructing a software behavior map of the software in the vehicle system; the software behavior map includes a software event, a plurality of software behaviors involved in the generation of the software event, and a logical relationship between the plurality of software behaviors involved in the generation of the software event; the software behavior is each operation performed inside the software; the software event is an event generated by the software and perceivable by other software in the vehicle system; constructing a priori relationship model based on the priori relationship between the software in the vehicle system; the priori relationship is a logical relationship between the software known before the vehicle system is built; connecting a plurality of the software behavior maps and the priori relationship model through the software event to construct the fault diagnosis map; The constructing of a software behavior graph of the software in the vehicle system includes: Determine the target software; the target software is any software in the vehicle system; Determine a plurality of software behaviors, a plurality of software events, and a log matching template corresponding to each software behavior of the target software; the log matching template refers to a log template corresponding to the software behavior; Constructing a software behavior graph of the target software according to the multiple software behaviors of the target software, the log matching template corresponding to each software behavior of the target software, the multiple software events of the target software, and the corresponding relationship between the multiple software behaviors of the target software and the multiple software events of the target software; The vehicle-mounted system includes a plurality of subsystems, and the prior relationship model is constructed based on the prior relationship between the software in the vehicle-mounted system, including: For each subsystem of the plurality of subsystems, constructing a sub-a priori relationship model based on a priori relationships between software included in the subsystem; Each subsystem of the vehicle-mounted system is taken as a child node. For each child node of the vehicle-mounted system, based on the child node event of the child node, a node in the upper layer that is connected to the child node is determined as the parent node of the child node, thereby obtaining multiple parent nodes of the vehicle-mounted system; one parent node corresponds to multiple child nodes; For each parent node of the vehicle-mounted system, constructing a parent node priori relationship model corresponding to the parent node based on a child priori relationship model of each child node among a plurality of child nodes corresponding to the parent node; Based on multiple parent node prior relationship models, a root node prior relationship model corresponding to the root node is determined, and the root node prior relationship model is used as the prior relationship model; the root node is the top-level node in the vehicle system that has a connection relationship with the child node and the parent node.

2. The method according to claim 1, It is characterized in that The analyzing the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target fault includes: Determining the priority of each logical link in the logical link set; According to the order of priority of the logical links from high to low, the log texts of the sub-node events involved in the corresponding logical links are analyzed to determine the cause of the target failure.

3. The method according to claim 1, It is characterized in that The method further comprises: Acquire a second corresponding relationship; the second corresponding relationship represents the corresponding relationship between the vehicle faults other than the multiple vehicle faults and the multiple system events; The second corresponding relationship is added to the first corresponding relationship to obtain an updated first corresponding relationship.

4. A fault diagnosis device based on vehicle system log, It is characterized in that The device comprises: A system event set determination module, configured to determine, based on a target fault and a first corresponding relationship, a plurality of root node system events corresponding to the target fault as a system event set; the first corresponding relationship represents a plurality of root node system events corresponding to each vehicle fault among a plurality of vehicle faults; the root node system event is an event generated by an onboard system and perceptible to the outside world; the target fault is any one of the plurality of vehicle faults; A logic link set determination module is used to determine, based on the system event set and the fault diagnosis map, a plurality of logic links corresponding to each root node system event in the system event set as a logic link set; each logic link is connected in series with a logically related sub-node event that causes the corresponding root node system event to occur; the fault diagnosis map includes a root node system event, a plurality of sub-node events that participate in the generation of the root node system event, and a logical relationship between the plurality of sub-node events; the sub-node event is an event generated by a subsystem of the vehicle-mounted system and perceivable by other subsystems; A fault cause determination module, used to analyze the log text corresponding to the sub-node event involved in each logical link in the logical link set to determine the cause of the target fault; A fault diagnosis graph construction module is used to construct a software behavior graph of the software in the vehicle system; the software behavior graph includes a software event, multiple software behaviors involved in the generation of the software event, and the logical relationship between the multiple software behaviors involved in the generation of the software event; the software behavior is each operation performed inside the software; the software event is an event generated by the software and perceivable by other software in the vehicle system; based on the prior relationship between the software in the vehicle system, a priori relationship model is constructed; the prior relationship is a logical relationship between the software known before the vehicle system is built; the fault diagnosis graph is constructed by connecting multiple software behavior graphs and the priori relationship model through the software event; A software behavior graph construction submodule is used to determine the target software; the target software is any software in the vehicle-mounted system; determine multiple software behaviors of the target software, multiple software events and a log matching template corresponding to each software behavior; the log matching template refers to a log template corresponding to the software behavior; based on the multiple software behaviors of the target software, the log matching template corresponding to each software behavior of the target software, the multiple software events of the target software, the multiple software behaviors of the target software and the corresponding relationship between the multiple software events of the target software, construct a software behavior graph of the target software; A priori relationship construction submodule is used to construct a sub-prior relationship model for each subsystem in the multiple subsystems based on the prior relationship between the software included in the subsystem; each subsystem of the vehicle-mounted system is taken as a child node, and for each child node of the vehicle-mounted system, based on the child node event of the child node, the upper layer node that has a connection relationship with the child node is determined as the parent node of the child node, and multiple parent nodes of the vehicle-mounted system are obtained; one parent node corresponds to multiple child nodes; for each parent node of the vehicle-mounted system, based on the sub-prior relationship model of each child node in the multiple child nodes corresponding to the parent node, a parent node prior relationship model corresponding to the parent node is constructed; based on the multiple parent node prior relationship models, a root node prior relationship model corresponding to the root node is determined, and the root node prior relationship model is used as the prior relationship model; the root node is the top-level node in the vehicle-mounted system that has a connection relationship with the child node and the parent node.

5. The device according to claim 4, It is characterized in that The fault cause determination module comprises: A priority determination unit, used to determine the priority of each logical link in the logical link set; The fault cause determination unit is used to analyze the log text of the software events involved in the corresponding logical link in the order of the priority of the logical link from high to low, and determine the cause of the target fault.

6. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the program is executed by a processor, the steps of the method described in any one of claims 1 to 3 are implemented.

7. An electronic device, It is characterized in that include: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1 to 3.