A diagnostic method, device, electronic device and storage medium based on fault tree

Abstract

The present application relates to the field of vehicle technology, and discloses a fault tree-based diagnostic method, device, electronic device and storage medium, the method comprising: if it is detected that the recorded target initial fault message meets the preset alarm condition, then a corresponding target alarm record is generated according to the recorded target initial fault message; wherein the target alarm record corresponds to a target preset fault tree; based on the target alarm record, a target bottom event set is determined from the bottom event set corresponding to the target preset fault tree; a target diagnostic report including a target processing strategy is generated according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event. The target processing strategy of the present application is composed of sub-processing strategies corresponding to each target bottom event, so the target processing strategy in the target diagnostic report is targeted at a wider range, and exhausts a variety of processing strategies applicable to the target fault to the greatest extent, so that users can perform fault inspection and repair.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a fault tree-based diagnosis method, device, electronic device and storage medium. Background Art

[0002] If a vehicle breaks down, it generally requires an experienced technician to perform a precise diagnosis. Some faults may not be intuitive and require a lot of time and effort to troubleshoot. In addition, some faults may be caused by multiple factors, requiring careful analysis and troubleshooting to find the root cause.

[0003] Currently, when a vehicle breaks down, the fault code will be proactively reported to the cloud. However, the cloud cannot accurately diagnose the specific cause of the failure based on the fault code alone, and users cannot intuitively know the cause of the vehicle failure and the corresponding handling strategy. Summary of the invention

[0004] In view of the above problems, the present application provides a fault tree-based diagnostic method, device, electronic device and storage medium for accurately diagnosing vehicle faults to provide corresponding fault handling strategies.

[0005] According to one aspect of the present application, a fault tree-based diagnostic method is provided, the diagnostic method comprising: if it is detected that a recorded target initial fault message satisfies a preset alarm condition, a corresponding target alarm record is generated according to the recorded target initial fault message; wherein the target alarm record corresponds to a target preset fault tree; based on the target alarm record, a target bottom event set is determined from the bottom event set corresponding to the target preset fault tree; a target diagnostic report including a target processing strategy is generated according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event.

[0006] In an optional manner, the diagnostic method further includes: generating an initial fault tree based on the type events selected by the user and the logical relationship between the events; detecting whether the initial fault tree includes at least one top event and at least one bottom event; if so, traversing each event link starting from the top event in the initial fault tree, and detecting whether the logical relationship between adjacent events in each event link holds, so as to generate a preset fault tree based on the event links in which the logical relationship holds.

[0007] In an optional manner, the target alarm record includes a target fault code; determining a target bottom event set from a bottom event set corresponding to the target preset fault tree based on the target alarm record further includes: obtaining a bottom event that matches the target fault code; traversing each matching bottom event, and taking the traversed matching bottom event as a designated bottom event; detecting whether the corresponding target evaluation parameter in the target alarm record satisfies the preset condition corresponding to the designated bottom event; if so, taking the designated bottom event as the target bottom event to determine the target bottom event set.

[0008] In an optional manner, the target evaluation parameters include a target evaluation period and a target cumulative number; the detection of whether the corresponding target evaluation parameters in the target alarm record meet the preset conditions corresponding to the specified bottom event further includes: detecting whether the target evaluation period is less than the preset period, and whether the target cumulative number is greater than the preset number; if both are yes, it is determined that the corresponding evaluation parameters in the target alarm record meet the preset conditions corresponding to the specified bottom event; if either is no, it is determined that the corresponding evaluation parameters in the target alarm record do not meet the preset conditions corresponding to the specified bottom event.

[0009] In an optional manner, generating a target diagnostic report including a target processing strategy based on the target bottom event set further includes: obtaining a triggering cause and a maintenance strategy corresponding to each target bottom event in the target bottom event set; generating a target processing strategy based on the maintenance strategy corresponding to each target bottom event, and generating a target diagnostic report based on the target processing strategy, the triggering cause and the fault code corresponding to each target bottom event.

[0010] In an optional manner, generating a corresponding target alarm record based on the recorded target initial fault message further includes: obtaining a target fault code corresponding to the recorded target initial fault message, the number of the target initial fault messages, and a start timestamp and an end timestamp of the recorded target initial fault message; performing a difference operation between the end timestamp and the start timestamp, and using the calculated difference as the record duration corresponding to the target initial fault message; generating a corresponding target alarm record based on the record duration, the target fault code and the number of the target initial fault messages.

[0011] In an optional manner, the diagnostic method further includes: if a display instruction from a user to obtain the details of the target diagnostic report is detected, the target preset fault tree is displayed in response to the display instruction, and the event links corresponding to each target bottom event in the target bottom event set are displayed in the target preset fault tree; wherein the top of each event link is the top event.

[0012] According to another aspect of the present application, a fault tree-based diagnostic device is provided, the diagnostic device comprising: a generation module, for generating a corresponding target alarm record according to the recorded target initial fault message if it is detected that the recorded target initial fault message meets a preset alarm condition; wherein the target alarm record corresponds to a target preset fault tree; a determination module, for determining a target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record; a diagnostic module, for generating a target diagnostic report including a target processing strategy according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event.

[0013] According to one aspect of the present application, an electronic device is provided, including: a controller; and a memory for storing one or more programs, which, when executed by the controller, perform the above-mentioned diagnostic method.

[0014] According to one aspect of the present application, a computer-readable storage medium is also provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the above-mentioned diagnostic method.

[0015] According to one aspect of the present application, a computer program product or computer program is also provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the above-mentioned diagnostic method.

[0016] This application introduces preset alarm conditions as a precondition for generating alarm records. When the preset alarm conditions are met, the corresponding target alarm record is generated according to the recorded target initial fault message, and the target bottom event set is determined from the bottom event set corresponding to the target preset fault tree based on the target alarm record to determine the bottom event that meets the triggering target fault, and then quickly generate a target diagnosis report including the target processing strategy. Because the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event, the target processing strategy in the target diagnosis report is targeted at a wider range, and exhausts a variety of processing strategies applicable to the target fault to the greatest extent, so that users can perform fault troubleshooting.

[0017] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 It is a flowchart of a fault tree-based diagnosis method shown in an exemplary embodiment of the present application.

[0020] Figure 2 is based on Figure 1 The exemplary embodiment shown is a flow chart of another fault tree-based diagnosis method.

[0021] Figure 3 It is a schematic diagram of a preset fault tree editing page shown in an exemplary embodiment of the present application.

[0022] Figure 4 is based on Figure 1 The exemplary embodiment shown is a flow chart of another fault tree-based diagnosis method.

[0023] Figure 5 is based on Figure 1 The exemplary embodiment shown is a flow chart of another fault tree-based diagnosis method.

[0024] Figure 6 It is a schematic diagram of displaying detailed information of a target diagnosis report shown in an exemplary embodiment of the present application.

[0025] Figure 7 It is a schematic diagram of an application scenario of the fault tree-based diagnostic method of the present application.

[0026] Figure 8 It is a structural schematic diagram of a fault tree-based diagnostic device shown in an exemplary embodiment of the present application.

[0027] Fig. 9 It is a structural diagram of a computer system of an electronic device shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0028] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0029] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0030] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0031] The term "multiple" as used in this application refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0032] When an existing vehicle breaks down, the fault code will be proactively reported to the cloud. However, the cloud cannot accurately diagnose the specific cause of the failure based on the fault code alone, and users cannot intuitively know the cause of the vehicle failure and the corresponding handling strategy.

[0033] To this end, one aspect of the present application provides a fault tree-based diagnostic method. Figure 1 , Figure 1 1 is a flow chart of a fault tree-based diagnostic method according to an exemplary embodiment of the present application. The diagnostic method at least includes S110 to S130, which are described in detail as follows:

[0034] S110: If it is detected that the recorded target initial fault message meets the preset alarm condition, a corresponding target alarm record is generated according to the recorded target initial fault message; wherein the target alarm record corresponds to a target preset fault tree.

[0035] The target initial fault message is an original fault message generated by the vehicle end and includes a target fault code, which includes but is not limited to the target fault code, occurrence identifier and occurrence timestamp. An example of the target initial fault message is as follows:

[0036]

[0037]

[0038] It is worth noting that there are multiple types of initial fault messages, and different initial fault messages record different fault codes for characterizing the faulty components, locations, etc. In this embodiment, the initial message recording the target fault code is used as the target initial fault message to perform subsequent diagnosis on an initial fault message.

[0039] The target alarm record is a record generated based on multiple target fault messages. The target alarm record can be a record generated when the number of target fault messages or other variables meet preset conditions. In this embodiment, the target initial fault message is detected according to the preset alarm condition. For example, the preset alarm condition includes the preset number of messages. If the number of recorded target initial fault messages reaches the preset number of messages, it is determined that the preset alarm condition is met, and the corresponding target alarm record can be generated.

[0040] Exemplarily, an initial fault message recording the same target fault code 0010 is used as a target initial fault message. If the number of target initial fault messages reaches a preset number, or the number reaches a preset number within a preset time period, a target alarm record is generated; wherein the target alarm record records information such as the target fault code, the timestamp of the first receipt of the initial fault message with the target fault code 0010, and the timestamp of the last receipt of the initial fault message with the target fault code 0010 when the target alarm record is generated.

[0041] S120: Determine a target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record.

[0042] The relevant parameters in the target alarm record are matched with the bottom events in the target preset fault tree, so that the bottom events with successful matching of the relevant parameters are taken as the target bottom events, thereby obtaining the target bottom event set.

[0043] S130: Generate a target diagnosis report including a target processing strategy according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event.

[0044] The subsets in the target bottom event set are the target bottom events. Each target bottom event corresponds to a corresponding sub-processing strategy. The sub-processing strategies are summarized to obtain the target processing strategy, so that the target processing strategy has a wider scope and exhausts a variety of processing strategies applicable to the target fault to the greatest extent, so as to facilitate users without professional knowledge reserves to perform fault inspection and repair.

[0045] This embodiment introduces preset alarm conditions as a precondition for generating alarm records. When the preset alarm conditions are met, a corresponding target alarm record is generated according to the recorded target initial fault message, and a target bottom event set is determined from the bottom event set corresponding to the target preset fault tree based on the target alarm record to determine the bottom event that meets the triggering target fault, and then quickly generate a target diagnosis report including a target processing strategy. Because the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event, the target processing strategy in the target diagnosis report is targeted at a wider range, and exhausts a variety of processing strategies applicable to the target fault to the greatest extent, so that users can perform fault troubleshooting.

[0046] In another exemplary embodiment of the present application, how to construct a preset fault tree is described in detail. Figure 2 , Figure 2 is based on Figure 1 The exemplary embodiment shown is a flow chart of another fault tree-based diagnostic method. Figure 1 Based on the S110 to S130 shown, S210 to S230 are also included, which are described in detail as follows:

[0047] S210: Generate an initial fault tree according to the type of events selected by the user and the logical relationship between the events.

[0048] The fault tree uses a tree structure to represent the various combinations and logical relationships of possible system failures. By gradually decomposing the failure events, the root cause of the system failure can be found.

[0049] In fault tree analysis, the fault phenomenon is usually represented as the root node of the tree, and then decomposed into more specific fault events step by step until it can no longer be decomposed. The logical relationship between each fault event is described by logic gates (such as AND gates, OR gates, etc.), so as to determine the most important event or condition that causes the system failure.

[0050] See also Figure 3 , Figure 3 is a schematic diagram of a preset fault tree editing page shown in an exemplary embodiment of the present application. The user can select a type event ( Figure 3 The top event, middle event, bottom event in the event) and the logical relationship between events ( Figure 3 In the editing area, the user can construct an initial fault tree by using the "and" and "or" in the editing area. At the same time, the user can set the properties of the corresponding components in the specified definition area, such as setting the fault code, evaluation cycle and cumulative number corresponding to the bottom event E, and can also set the fault cause and corresponding maintenance plan that triggers the bottom event E.

[0051] S220: Detect whether the initial fault tree includes at least one top event and at least one bottom event.

[0052] The initial fault tree is not necessarily a standard fault tree and needs to be tested accordingly to ensure that it meets the basic standards.

[0053] Among them, the top event is the final result or main event of the entire fault tree, usually representing a fault or accident phenomenon. The intermediate event is the event that causes the top event to occur, usually indicating the failure or failure of a component or subsystem in the system. The intermediate event can be further decomposed into more intermediate events or bottom events. The bottom event is the most basic event of the fault tree, which cannot be further decomposed and is the cause of the intermediate event.

[0054] Fault tree maintenance is mainly divided into two parts, one is the maintenance of the tree structure, and the other is the maintenance of the bottom event rules. The tree structure mainly shows the various causes of the top event, that is, it lists the various logical relationships between the top event and the intermediate events and bottom events. It is worth noting that a fault tree that meets the basic standards includes at least one top event and one bottom event.

[0055] S230: If yes, traverse each event link starting from the top event in the initial fault tree, and detect whether the logical relationship between adjacent events in each event link is established, so as to generate a preset fault tree according to the event links with established logical relationships.

[0056] Exemplarily, the event chain of "top event → middle event A → bottom event C" is traversed. If the logical relationship between the adjacent events is established, the next event chain is traversed, and all event chains are traversed to determine the event chain with a established logical relationship, and a preset fault tree is generated based on the event chain with a established logical relationship. If the logical relationship between adjacent events is not established, the adjacent event can be highlighted in the constructed initial fault tree, so that the user can quickly know the error location, so that it can be adjusted and modified in a targeted manner.

[0057] The constructed preset fault tree is shown in Table 1:

[0058] Table 1: Example information table of preset fault tree

[0059]

[0060]

[0061] This embodiment provides a method for constructing a preset fault tree, and provides a virtual page that can be edited by the user, so as to quickly construct an initial fault tree according to the user's selection and input information, and automatically perform logic detection on the initial fault tree to ensure that the constructed preset fault tree can be used normally.

[0062] In another exemplary embodiment of the present application, it is described in detail how to determine the target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record. For details, please refer to Figure 4 , Figure 4 is based on Figure 1 The exemplary embodiment shown is a flow chart of another fault tree-based diagnostic method. Figure 1 The S120 shown further includes S410 to S440; wherein the target alarm record includes a target fault code, which is described in detail as follows:

[0063] S410: Acquire a bottom event matching the target fault code.

[0064] The fault codes corresponding to the bottom events in each preset fault tree are not necessarily the same. This embodiment preliminarily screens the bottom events in the target preset fault tree by the target fault code to determine the bottom events matching the target fault code.

[0065] S420: traverse each matching bottom event, and use the traversed matching bottom event as the designated bottom event.

[0066] This embodiment adopts a method of traversing each matching bottom event to ensure that all matching bottom events are detected without omission, so as to ensure the integrity of the detection result and accurately determine the target bottom event set.

[0067] S430: Detect whether the corresponding target evaluation parameter in the target alarm record satisfies the preset condition corresponding to the specified bottom event.

[0068] Exemplarily, when a matching second bottom event is traversed, the target evaluation parameter is compared with the corresponding preset condition to detect whether the target evaluation parameter satisfies the preset condition, so as to determine whether the second bottom event is the target bottom event based on the detection result.

[0069] S440: If satisfied, the designated bottom event is used as the target bottom event to determine a target bottom event set.

[0070] If not, the specified bottom event cannot be used as the target bottom event, and the next matching bottom event is traversed to determine at least one target bottom event, thereby obtaining a target bottom event set.

[0071] In another exemplary embodiment of the present application, how to detect whether the corresponding target evaluation parameter in the target alarm record satisfies the preset condition corresponding to the specified bottom event is described in detail, that is, the above S430 further includes S431 to S433; wherein the target evaluation parameter includes the target evaluation period and the target cumulative number of times, which are described in detail as follows:

[0072] S431: Detect whether the target evaluation period is less than the preset period, and whether the target cumulative number is greater than the preset number.

[0073] The target evaluation period is less than the preset period, indicating that the target evaluation frequency is higher than the preset evaluation frequency. For example, the target evaluation period is 2 seconds, the target cumulative number is 2 times, the preset period is 3 seconds, and the preset number is 1 time. Obviously, the corresponding evaluation parameters in the target alarm record meet the preset conditions corresponding to the specified bottom event.

[0074] S432: If both are yes, it is determined that the corresponding evaluation parameter in the target alarm record satisfies the preset condition corresponding to the specified bottom event.

[0075] S433: If any one of the conditions is no, it is determined that the corresponding evaluation parameter in the target alarm record does not satisfy the preset condition corresponding to the specified bottom event.

[0076] This embodiment performs conditional judgment on the target alarm record through evaluation cycle and cumulative number of times, and uses different types of preset parameters to determine whether the corresponding evaluation parameters in the target alarm record meet the preset conditions corresponding to the specified bottom event, thereby accurately determining the target bottom event to improve the accuracy of conditional judgment.

[0077] In another exemplary embodiment of the present application, a detailed description is given of how to generate a target diagnosis report including a target processing strategy according to a target bottom event set. Figure 5 , Figure 5 is based on Figure 1 The exemplary embodiment shown is a flow chart of another fault tree-based diagnostic method. Figure 1 The S130 shown further includes S510 to S520, which are described in detail as follows:

[0078] S510: Obtain the triggering cause and maintenance strategy corresponding to each target bottom event in the target bottom event set.

[0079] S520: Generate a target processing strategy according to the maintenance strategy corresponding to each target bottom event, and generate a target diagnosis report according to the target processing strategy, the triggering cause and the fault code corresponding to each target bottom event.

[0080] For example, the target bottom event set includes bottom event A and bottom event B. The triggering cause corresponding to bottom event A is a, and the corresponding maintenance strategy is strategy 1; the triggering cause corresponding to bottom event B is b, and the corresponding maintenance strategy is strategy 2. The triggering cause recorded in the target diagnosis report generated based on them is "a+b", and the target processing strategy is "strategy 1+strategy 2". At the same time, the fault codes corresponding to bottom event A and bottom event B are recorded in the target diagnosis report.

[0081] This embodiment provides a method for generating a target diagnostic report, mainly based on the parameters corresponding to each bottom event in the target bottom event set. The target diagnostic report can be quickly combined based on the parameters corresponding to each bottom event without a complicated report generation process.

[0082] In another exemplary embodiment of the present application, how to generate a corresponding target alarm record according to the recorded target initial fault message is described in detail. Figure 1 The S110 shown further includes S111 to S113, which are described in detail as follows:

[0083] S111: Obtain a target fault code corresponding to the recorded target initial fault message, the number of target initial fault messages, and a start timestamp and an end timestamp of the recorded target initial fault message.

[0084] S112: performing a difference operation on the end timestamp and the start timestamp, and using the calculated difference as the recording duration corresponding to the target initial fault message.

[0085] In some embodiments, the recording duration may be used as the evaluation period described in the above exemplary embodiments, and the number of target initial fault messages may be used as the cumulative number of recorded target initial fault messages.

[0086] Exemplarily, the end timestamp is 10:00, the start timestamp is 9:30, and a difference operation is performed between the two. The recording duration corresponding to the target initial fault message is 30 minutes.

[0087] S113: Generate a corresponding target alarm record according to the recording duration, the target fault code and the number of target initial fault messages.

[0088] The target alarm record includes but is not limited to the target fault code, the number of target initial fault messages and the recording duration, and may also include the identifier of the corresponding preset fault tree, the end timestamp and the start timestamp, etc.

[0089] This embodiment further illustrates the specific parameters included in the target alarm record, and based on the specific parameters, a target preset fault tree can be further determined, and then a target bottom event combination can be determined, thereby quickly determining a target diagnosis report.

[0090] In another exemplary embodiment of the present application, how to display the detailed data expected by the user based on the target diagnosis report is described in detail. Based on the diagnosis method shown in any of the above exemplary embodiments, the diagnosis method of this embodiment further includes S140, which is described in detail as follows:

[0091] S140: If a display instruction for obtaining target diagnostic report details from the user is detected, a target preset fault tree is displayed in response to the display instruction, and event links corresponding to each target bottom event in the target bottom event set are displayed in the target preset fault tree; wherein the top of each event link is a top event.

[0092] See also Figure 6 , Figure 6 6(a) is a schematic diagram showing detailed information of a target diagnostic report according to an exemplary embodiment of the present application. The user clicks the target diagnostic report in the virtual page 6(a) with the mouse, and the virtual page pops up as shown in FIG. Figure 6 (b) shows the details page, and displays the corresponding complete fault tree on the details page. Figure 6 The bold event links in (b) highlight the event links corresponding to the target bottom events that constitute the target diagnosis report, so that users can intuitively know all the diagnosis links, trace the source, and facilitate subsequent vehicle maintenance.

[0093] In another exemplary embodiment of the present application, the application scenarios of the above multiple diagnostic methods are exemplarily described. Figure 7 , Figure 7 It is a schematic diagram of an application scenario of the fault tree-based diagnostic method of the present application, wherein the vehicle end 100 and the server 200 are included, and the two ends can be connected by wireless communication, and the present application does not limit the connection method between them.

[0094] The vehicle end 100 may report the initial fault message to the server 200 in real time, and the server 200 may be used as the execution subject of the diagnostic method shown in any of the above exemplary embodiments, as exemplified below:

[0095] If server 200 detects that the recorded target initial fault message meets the preset alarm condition, it generates a corresponding target alarm record based on the recorded target initial fault message; wherein the target alarm record corresponds to a target preset fault tree; server 200 determines a target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record; server 200 generates a target diagnostic report including a target processing strategy based on the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event.

[0096] Server 200 can be an independent physical server or a server cluster or distributed system composed of multiple physical servers, wherein multiple servers can form a blockchain, and the server is a node on the blockchain. Server 200 can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network) and big data and artificial intelligence platforms, and this is not restricted here.

[0097] Another aspect of the present application also provides a fault tree-based diagnostic device, such as Figure 8 As shown, Figure 8 It is a structural schematic diagram of a fault tree-based diagnostic device shown in an exemplary embodiment of the present application. The diagnostic device 800 includes: a generation module 810, which is used to generate a corresponding target alarm record according to the recorded target initial fault message if it is detected that the recorded target initial fault message meets the preset alarm condition; wherein the target alarm record corresponds to a target preset fault tree; a determination module 830, which is used to determine a target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record; a diagnostic module 850, which is used to generate a target diagnostic report including a target processing strategy according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event.

[0098] In an optional manner, the diagnostic device 800 also includes: an initial fault tree generation module, which is used to generate an initial fault tree based on the type events selected by the user and the logical relationship between the events; a fault tree detection module, which is used to detect whether the initial fault tree includes at least one top event and at least one bottom event; and a traversal module, which is used to traverse each event link starting from the top event in the initial fault tree if yes, and detect whether the logical relationship between adjacent events in each event link is established, so as to generate a preset fault tree based on the event links in which the logical relationship is established.

[0099] In an optional manner, the target alarm record includes a target fault code; the determination module 830 further includes: a bottom event acquisition unit, used to acquire a bottom event that matches the target fault code; a traversal unit, used to traverse each matching bottom event, and use the traversed matching bottom event as the designated bottom event; a detection unit, used to detect whether the corresponding target evaluation parameter in the target alarm record satisfies the preset condition corresponding to the designated bottom event; and a determination unit, used to use the designated bottom event as the target bottom event if satisfied, so as to determine a target bottom event set.

[0100] In an optional manner, the target evaluation parameters include a target evaluation period and a target cumulative number; the detection unit further includes: a detection section, used to detect whether the target evaluation period is less than a preset period, and whether the target cumulative number is greater than a preset number; a first determination section, used to determine that the corresponding evaluation parameters in the target alarm record meet the preset conditions corresponding to the specified bottom event if both are yes; a second determination section, used to determine that the corresponding evaluation parameters in the target alarm record do not meet the preset conditions corresponding to the specified bottom event if any one is no.

[0101] In an optional manner, the diagnosis module 850 further includes: a cause strategy acquisition unit, which is used to obtain the trigger cause and maintenance strategy corresponding to each target bottom event in the target bottom event set; a diagnosis unit, which is used to generate a target processing strategy according to the maintenance strategy corresponding to each target bottom event, and generate a target diagnosis report according to the target processing strategy, the trigger cause and fault code corresponding to each target bottom event.

[0102] In an optional manner, the generation module 810 further includes: a parameter acquisition unit, used to obtain the target fault code corresponding to the recorded target initial fault message, the number of target initial fault messages, and the start timestamp and end timestamp of the recorded target initial fault message; a calculation unit, used to perform a difference operation on the end timestamp and the start timestamp, and use the calculated difference as the record duration corresponding to the target initial fault message; a target alarm record generation unit, used to generate a corresponding target alarm record according to the record duration, the target fault code and the number of target initial fault messages.

[0103] In an optional manner, the diagnostic device 800 also includes: a details display module, which is used to display the target preset fault tree in response to the display instruction if a display instruction for obtaining the details of the target diagnostic report from the user is detected, and to display the event links corresponding to each target bottom event in the target bottom event set in the target preset fault tree; wherein the top of each event link is the top event.

[0104] The diagnostic device of the present application introduces preset alarm conditions as a precondition for generating alarm records. When the preset alarm conditions are met, the corresponding target alarm record is generated according to the recorded target initial fault message, and the target bottom event set is determined from the bottom event set corresponding to the target preset fault tree based on the target alarm record to determine the bottom event that meets the triggering target fault, and then quickly generate a target diagnostic report including the target processing strategy. Because the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event, the target processing strategy in the target diagnostic report is targeted at a wider range, and exhausts a variety of processing strategies applicable to the target fault to the greatest extent, so as to facilitate the user to perform fault troubleshooting.

[0105] It should be noted that the diagnostic device provided in the above embodiment and the diagnostic method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment and will not be repeated here.

[0106] Another aspect of the present application provides an electronic device, comprising: a controller; and a memory for storing one or more programs, which, when executed by the controller, perform the above-mentioned diagnostic method.

[0107] See also Fig. 9 , Fig. 9 1 is a schematic diagram of the structure of a computer system of an electronic device shown in an exemplary embodiment of the present application, which shows a schematic diagram of the structure of a computer system of an electronic device suitable for implementing an embodiment of the present application.

[0108] It should be noted that Fig. 9 The computer system 900 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0109] like Fig. 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 902 or the program loaded from the storage part 908 to the random access memory (RAM) 903, such as executing the method in the above embodiment. In the RAM 903, various programs and data required for system operation are also stored. The CPU 901, ROM 902 and RAM 903 are connected to each other through a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0110] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.

[0111] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 909, and / or installed from a removable medium 911. When the computer program is executed by a central processing unit (CPU) 901, various functions defined in the system of the present application are executed.

[0112] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as a part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0113] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0114] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0115] Another aspect of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned diagnostic method is implemented. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.

[0116] Another aspect of the present application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the diagnostic method provided in each of the above embodiments.

[0117] According to one aspect of an embodiment of the present application, a computer system is also provided, including a central processing unit (CPU), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage portion into a random access memory (RAM), such as executing the method in the above embodiment. In RAM, various programs and data required for system operation are also stored. CPU, ROM and RAM are connected to each other via a bus. An input / output (I / O) interface is also connected to the bus.

[0118] The following components are connected to the I / O interface: an input part including a keyboard, a mouse, etc.; an output part including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage part including a hard disk, etc.; and a communication part including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication part performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface as needed. Removable media, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., are installed on the drive as needed so that the computer program read therefrom is installed into the storage part as needed.

[0119] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.

Claims

1. A fault tree-based diagnostic method, characterized in that: The diagnostic method comprises: If it is detected that the recorded target initial fault message meets the preset alarm condition, a corresponding target alarm record is generated according to the recorded target initial fault message; wherein the target alarm record corresponds to a target preset fault tree, and the target alarm record includes a target fault code; Determine a target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record, wherein the target bottom events in the target bottom event set match the target fault code; Generate a target diagnosis report including a target processing strategy according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event; and determine the target bottom event set from the bottom event set corresponding to the target preset fault tree based on the target alarm record, further comprising: Acquire a bottom event matching the target fault code; Traverse each matching bottom event, and use the traversed matching bottom event as the designated bottom event; Detecting whether the corresponding target evaluation parameter in the target alarm record satisfies the preset condition corresponding to the specified bottom event; If satisfied, the designated bottom event is used as the target bottom event to determine a target bottom event set.

2. The diagnostic method according to claim 1, characterized in that The diagnostic method further comprises: Generate an initial fault tree based on the type of events selected by the user and the logical relationship between the events; Detecting whether the initial fault tree includes at least one top event and at least one bottom event; If yes, each event link is traversed starting from the top event in the initial fault tree, and whether the logical relationship between adjacent events in each event link is established is detected, so as to generate a preset fault tree according to the event links with established logical relationships.

3. The diagnostic method according to claim 1, characterized in that: The target evaluation parameters include the target evaluation period and the target cumulative number of times; The detecting whether the target evaluation parameter corresponding to the target alarm record satisfies the preset condition corresponding to the specified bottom event further includes: Detecting whether the target evaluation period is less than a preset period, and whether the target cumulative number is greater than a preset number; If both are yes, it is determined that the corresponding evaluation parameter in the target alarm record satisfies the preset condition corresponding to the specified bottom event; If any one of them is no, it is determined that the corresponding evaluation parameter in the target alarm record does not satisfy the preset condition corresponding to the specified bottom event.

4. The diagnostic method according to claim 1, characterized in that: The generating of a target diagnosis report including a target processing strategy according to the target bottom event set further comprises: Obtaining the triggering cause and maintenance strategy corresponding to each target bottom event in the target bottom event set; A target processing strategy is generated according to the maintenance strategy corresponding to each target bottom event, and a target diagnosis report is generated according to the target processing strategy, the triggering cause and the fault code corresponding to each target bottom event.

5. The diagnostic method according to any one of claims 1 to 4, characterized in that: The generating a corresponding target alarm record according to the recorded target initial fault message further includes: Obtaining a target fault code corresponding to the recorded target initial fault message, the number of the target initial fault messages, and a start timestamp and an end timestamp of the recorded target initial fault message; Performing a difference operation on the end timestamp and the start timestamp, and using the calculated difference as the recording duration corresponding to the target initial fault message; A corresponding target alarm record is generated according to the recording duration, the target fault code and the number of the target initial fault messages.

6. The diagnostic method according to any one of claims 1 to 4, characterized in that: The diagnostic method further comprises: If a display instruction from the user to obtain the details of the target diagnostic report is detected, the target preset fault tree is displayed in response to the display instruction, and the event links corresponding to each target bottom event in the target bottom event set are displayed in the target preset fault tree; wherein the top of each event link is the top event.

7. A fault tree-based diagnostic device, characterized in that: The diagnostic device comprises: A generating module, configured to generate a corresponding target alarm record according to the recorded target initial fault message if it is detected that the recorded target initial fault message meets a preset alarm condition; wherein the target alarm record corresponds to a target preset fault tree, and the target alarm record includes a target fault code; A determination module, configured to determine a target bottom event set from a bottom event set corresponding to the target preset fault tree based on the target alarm record, wherein the target bottom events in the target bottom event set match the target fault code; A diagnosis module, used to generate a target diagnosis report including a target processing strategy according to the target bottom event set; wherein the target processing strategy is composed of sub-processing strategies corresponding to each target bottom event; the determination module further includes: A bottom event acquisition unit, used to acquire a bottom event matching the target fault code; A traversal unit, used for traversing each matching bottom event, and taking the traversed matching bottom event as the designated bottom event; A detection unit, used to detect whether the target evaluation parameter corresponding to the target alarm record satisfies the preset condition corresponding to the specified bottom event; The determination unit is used to take the specified bottom event as the target bottom event if the conditions are met, so as to determine a target bottom event set.

8. An electronic device, characterized in that: include: Controller; A memory for storing one or more programs, which, when executed by a controller, enables the controller to implement the diagnostic method described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the diagnostic method according to any one of claims 1 to 6.

Images