Failure message storage and display method and system based on combinational logic

Abstract

The invention relates to a failure message storage and display method and system based on combinational logic. In the technical scheme of the invention, after a root cause is periodically received, whether an activation state exists in the root cause is judged, and if the activation state exists, whether the state of a failure message associated with the activation state is changed is determined; and under the condition of change, a new trigger record is added in the storage table or the number of times of triggering of the existing trigger record is increased progressively, and the updated trigger record is output to the display unit and the storage unit.

Description

Technical Field

[0001] The present invention relates to the field of onboard health management of civil aircraft, and in particular to a method and system for storing and displaying failure messages based on combinational logic. Background Art

[0002] With the operation of commercial aircraft, airlines are paying more and more attention to the accuracy of problem location and the improvement of maintenance efficiency. Due to the complexity of fault logic and the repeated occurrence of failure information, the demand for hierarchical display and storage of failure / fault information and update efficiency is gradually increasing. When the combination logic failure message equation is satisfied and the state of the failure message (FailureMessage) changes, the onboard maintenance system should update the display and storage of the failure message and related root causes. With the increase of operation time, the following three situations arise regarding the display and storage of failure / fault information:

[0003] 1) If failure messages occur repeatedly (the failure status changes: 0-1, 1-0, 0-1, ...), how many records does the system display and store?

[0004] 2) The failure message always exists (the failure status is always 1), but the root fault that triggers the failure message changes. How many records does the system display and store?

[0005] 3) When displaying and storing failure messages, how do you display and store the root causes? Do you display and store all the root causes in the fault equation, or only the root cause that triggered the failure information?

[0006] According to the current operating status of domestic large aircraft, the onboard maintenance system of domestic large aircraft displays and stores a single failure message each time a failure occurs, but does not display or store the specific number of occurrences; for failures that have always existed (the failure status is always 1), the onboard maintenance system of domestic large aircraft only displays and stores the root cause of the first triggered root fault on the Details page. In response to this situation, maintenance personnel perform all operations of the fault isolation procedure one by one through the FIM code.

[0007] Based on the research on the failure / fault information display function of today's international advanced civil aircraft, a certain type of aircraft will display the triggering number of the failure message of the entire flight segment. When the failure message persists, there is no change in the state of the root cause displayed on the failure details page. Another type of aircraft does not display the triggering number of the failure message; when the failure message persists, there is no change in the state of the root cause displayed.

[0008] It can be seen that there is currently no relevant patent that proposes a solution for the situation when the failure message status is always 1 but the status of the root cause changes. The existing technology has a system displaying and storing the failure message trigger record when the failure message changes, and when displaying and storing the failure message, only the triggered root cause is displayed and stored on the details page, and when the failure message status remains unchanged, the details page does not display the status change of the root cause.

[0009] Therefore, when the failure message always exists, if the root fault that triggers the failure message changes, only the root cause of the root fault that first triggered the failure message will be displayed and stored on the details page, that is, when the failure message status is always 1, it changes from being triggered by root fault 1 to being triggered by root fault 2, and the system only records the root cause of root fault 1, not the root cause of root fault 2. This approach can easily lead to the loss of root cause information, resulting in inaccurate fault location, and further inaccurate maintenance instructions. In this case, maintenance personnel need to perform all operations of the fault isolation procedure one by one, reducing maintenance efficiency.

[0010] In addition, currently, for recurring failures, a single failure message is displayed and stored each time it occurs, and the number of failure message occurrences is not displayed or stored. In view of the current false alarm problem of domestic large aircraft, when the failure message is repeatedly triggered multiple times, the system displays and stores too many identical failure messages, causing inconvenience to maintenance personnel in browsing and maintenance, and also brings certain pressure to storage and calculation.

[0011] Therefore, there is an urgent need for a system and method that improves the prior art. Summary of the invention

[0012] This Summary is provided to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0013] In view of the problems in the prior art, the present invention proposes a method and system for storing and displaying failure messages based on combinational logic, optimizes the logical algorithm for storing and displaying fault information, and improves the accuracy of fault information and the overall maintenance efficiency.

[0014] In the technical solution of the present invention, in the same flight segment, when the same failure message occurs repeatedly, displaying and storing the triggering times can reduce the number of effective failure messages and reduce the workload of maintenance personnel. At the same time, the storage and display of the root fault information that triggers the failure message plays an even more important role in the operation of the aircraft, which is mainly reflected in the following aspects:

[0015] 1) The storage and display of root fault information is of great importance to fault location and maintenance accuracy. Its logical integrity needs to be improved to improve maintenance efficiency;

[0016] 2) Ensure the integrity and reliability of the storage and display of root fault information, so that faults can be exposed to maintenance personnel in a timely manner, reducing the potential risks of aircraft operations.

[0017] 3) The root cause is associated with the corresponding fault isolation program and feature extraction is performed to display the extracted fault isolation program, thereby avoiding the need to operate the entire fault isolation program. Only the fault isolation program after feature extraction needs to be operated, which greatly shortens the maintenance time and improves the maintenance efficiency.

[0018] Specifically, in one embodiment of the present invention, a method for storing and displaying an invalidation message based on combinational logic is disclosed, the method comprising:

[0019] Periodically receive root causes;

[0020] Determine whether there is an activation state in the root cause;

[0021] In the presence of the activation state, determining that a deactivation message associated with the activation state is triggered;

[0022] Determine whether the invalidation message has a status change compared with the previous cycle;

[0023] When the invalidation message changes state, the trigger record of the invalidation message is updated, including:

[0024] Determine whether there is a trigger record of the invalidation message in the invalidation message storage table;

[0025] If the trigger record exists, the trigger count of the trigger record is incremented;

[0026] Adding a trigger record of the invalidation message in the invalidation message storage table if the trigger record does not exist; and

[0027] The updated trigger record of the invalidation message is output to a display unit and a storage unit.

[0028] In one embodiment of the present invention, the method further includes continuing to receive the root cause in the next cycle in the absence of the activation state.

[0029] In one embodiment of the present invention, the state change of the invalidation message includes that the invalidation state corresponding to the invalidation message changes from an untriggered state in a previous cycle to a triggered state in a current cycle.

[0030] In one embodiment of the present invention, the method further comprises:

[0031] When the failure message does not change state, determining whether the root cause changes state compared with the previous cycle;

[0032] updating the root cause when a state change occurs in the root cause and outputting the updated root cause to the display unit and the storage unit;

[0033] In response to a selection of the FIM code in the fault detail page displayed by the display unit, jumping to a maintenance manual page including a manual module having an associated manual module ID based on an association between a root cause ID of the received root cause and a manual module ID in the maintenance manual; and

[0034] If the state of the root cause does not change, the root cause continues to be received in the next cycle.

[0035] In the above embodiment of the present invention, the state change of the root cause includes that the root fault in the root cause that triggers the failure corresponding to the failure message is different in the previous cycle and in the current cycle.

[0036] In one embodiment of the present invention, a system for storing and displaying failure messages based on combinational logic is disclosed, the system comprising:

[0037] a root cause receiving module configured to periodically receive a root cause;

[0038] The invalidation message logic processing module is configured to:

[0039] Determine whether there is an activation state in the root cause;

[0040] In the presence of the activation state, determining that a deactivation message associated with the activation state is triggered;

[0041] Determine whether the invalidation message has a status change compared with the previous cycle;

[0042] When the invalidation message changes state, the trigger record of the invalidation message is updated, including:

[0043] Determine whether there is a trigger record of the invalidation message in the invalidation message storage table;

[0044] If the trigger record exists, the trigger count of the trigger record is incremented;

[0045] Adding a trigger record of the invalidation message in the invalidation message storage table if the trigger record does not exist; and

[0046] The processing result output module is configured to output the updated trigger record of the invalidation message to a display unit and a storage unit.

[0047] In one embodiment of the present invention, the root cause receiving module is further configured to continue receiving the root cause in the next cycle when the activation state does not exist.

[0048] In one embodiment of the present invention, the failure message logic processing module is further configured to:

[0049] If the failure message does not change state, determining whether the root cause changes state compared to the previous cycle; and

[0050] The root cause is updated when a state change occurs to the root cause.

[0051] In the above-mentioned embodiment of the present invention, the processing result output module is further configured to output the updated root cause to the display unit and the storage unit; and in response to the selection of the FIM code in the fault details page displayed by the display unit, jump to the maintenance manual page including the manual module with the associated manual module ID based on the association between the root cause ID of the received root cause and the manual module ID in the maintenance manual.

[0052] In the above embodiment of the present invention, the root cause receiving module is further configured to continue receiving the root cause in the next cycle when the state of the root cause does not change.

[0053] In yet another embodiment of the present invention, a computer storage medium is disclosed, which stores instructions for storing and displaying failure messages based on combinational logic, including:

[0054] Instructions for periodically receiving root causes;

[0055] Instructions for determining whether an active state exists in the root cause;

[0056] Instructions for determining that a deactivation message associated with the activation state is triggered if the activation state exists;

[0057] An instruction for determining whether the invalidation message has a state change compared to a previous cycle;

[0058] The instruction for updating the trigger record of the invalidation message when the invalidation message changes state includes:

[0059] An instruction for determining whether the trigger record of the invalidation message exists in the invalidation message storage table; an instruction for incrementing the trigger count of the trigger record if the trigger record exists;

[0060] An instruction for adding the trigger record of the invalidation message in the invalidation message storage table if the trigger record does not exist; and

[0061] Instructions for outputting an updated trigger record of the invalidation message to a display unit and a storage unit.

[0062] After studying the description of the specific exemplary embodiments of the present invention below in conjunction with the accompanying drawings, other aspects, features and embodiments of the present invention will be apparent to those of ordinary skill in the art. Although features of the present invention may be discussed below with respect to certain embodiments and accompanying drawings, all embodiments of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed to have certain advantageous features, one or more of such features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be appreciated that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to understand in detail the manner in which the above-stated features of the present disclosure are used, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0064] Figure 1 A schematic block diagram of a system for storing and displaying invalidation messages based on combinatorial logic according to an embodiment of the present invention is shown.

[0065] Figure 2 A fault detail page of a display unit according to an embodiment of the present invention is shown.

[0066] Figure 3 A flowchart of a method for storing and displaying invalidation messages based on combinatorial logic according to an embodiment of the present disclosure is shown.

[0067] Figure 4 A detailed flow chart of the step of updating the trigger record of the invalidation message in the invalidation message storage and display method based on combinatorial logic according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0068] The various embodiments will be described in more detail below with reference to the accompanying drawings that form part of the present invention and illustrate various specific exemplary embodiments. However, the various embodiments can be implemented in many different forms and should not be interpreted as limiting the various embodiments set forth herein; on the contrary, these embodiments are provided to make the present disclosure thorough and complete, and to fully convey the scope of these embodiments to those of ordinary skill in the art. The various embodiments may be implemented in accordance with methods, systems, or devices. Therefore, these embodiments may be implemented in hardware, in full software, or in a combination of software and hardware. Therefore, the following specific embodiments are not limiting.

[0069] The steps in each flow chart may be performed by hardware (e.g., processor, engine, memory, circuit), software (e.g., operating system, application, driver, machine / processor executable instructions), or a combination thereof. As will be appreciated by those skilled in the art, the methods involved in each embodiment may include more or fewer steps than shown.

[0070] Based on the analysis of the logical architecture of the storage and display of failure messages in the maintenance system of the current mainstream civil aircraft, and in view of the technical problems in the prior art, the present invention proposes a method and system for storing and displaying failure messages based on combinational logic. In the present invention, the existing logical algorithm is optimized to improve the integrity and accuracy of the storage and display of fault information, and further improve the maintenance efficiency and the convenience of maintenance personnel.

[0071] The present invention proposes a method and system for storing and displaying failure messages based on combinational logic, which is characterized in that: the method for storing and displaying failure messages is applicable to fault diagnosis functions, and the method for storing and displaying failure messages implements the update of failure messages based on the judgment of failure state changes. Furthermore, the present invention also proposes to implement the update of storage and display of the root cause of the failure message based on the state change of the root cause of the failure message.

[0072] Various aspects of the present invention will be described in detail below.

[0073] Figure 1 A schematic block diagram of a system 100 for storing and displaying invalidation messages based on combinatorial logic according to an embodiment of the present invention is shown.

[0074] like Figure 1 As shown, the system 100 may include a root cause receiving module 102 , a failure message logic processing module 104 , and a processing result output module 106 . Figure 2 FIG. 1 shows a fault detail page of a display unit according to an embodiment of the present invention. Figure 2 Describe each aspect of these modules in detail.

[0075] In one embodiment of the present invention, the root cause receiving module 102 may be configured to periodically receive the root cause. In this embodiment, the root cause receiving module 102 may be configured to periodically receive the root fault (such as Figure 2 The root cause corresponding to Fault1, Fault2, etc. Figure 2 Each of the five rows (as an example and not a limitation) shown in , each root cause has a corresponding root cause ID ( Figure 2 not shown).

[0076] In one embodiment of the present invention, the failure message logic processing module 104 may be configured to determine whether there is an active state (ACTIVE, i.e. Figure 2 ), and if the activation state exists, it is determined that the failure message associated with the activation state is triggered. In various embodiments, when the activation state does not exist, the root cause receiving module 102 may be further configured to continue to receive the root cause in the next cycle.

[0077] In the above embodiment, the invalidation message logic processing module 104 may also be configured to determine whether the invalidation message has a state change compared to the previous cycle, and update the trigger record of the invalidation message when the invalidation message has a state change. In this embodiment, the state change of the invalidation message may include that the invalidation state corresponding to the invalidation message changes from the untriggered state in the previous cycle to the triggered state in the current cycle. In other words, when the invalidation message is not triggered in the previous cycle (that is, the state value of the invalidation message is 0), the invalidation message logic processing module 104 may determine that the invalidation message triggered in the current cycle (that is, the state value of the invalidation message is 1) has changed compared to the previous cycle, that is, determine that the invalidation message has a state change from 0-1. As can be understood by those skilled in the art, judging whether a state change occurs by using a state value is merely exemplary and non-restrictive, and any other suitable method may be used to judge whether a state change occurs in the invalidation message compared to the previous cycle.

[0078] In one embodiment of the present invention, the invalidation message logic processing module 104 may be further configured to update the trigger record of the invalidation message by the following operations: determining whether there is a trigger record of the invalidation message in the invalidation message storage table; if there is such a trigger record, incrementing the trigger count of the trigger record; if there is no such trigger record, adding the trigger record of the invalidation message in the invalidation message storage table. Figure 2 As shown, the "Count" shown in the upper right corner indicates that the trigger record of the invalidation message is 2, that is, 2 times, and Figure 2In the example, there are two failure messages for the equipment (Equipment) "CLIMB" (as an example and not a limitation), that is, there are two trigger records (the first to the second rows in the five rows are the first, and the third to the fifth rows are the second). The second failure message is triggered when the status of the first failure message becomes 1 again after becoming 0.

[0079] In one embodiment of the present invention, the processing result output module 106 may be configured to output the updated trigger record of the failure message to a display unit and a storage unit. In this embodiment, the display unit may be an HMI (human-machine interface) or any other suitable display device.

[0080] In another embodiment of the present invention, the failure message logic processing module 104 may be optionally configured to determine whether the state of the root cause received in the current cycle has changed compared with the previous cycle when the failure message has not changed, and update the root cause when the state of the root cause has changed. In this embodiment, after the root cause update is completed, the root cause of the root fault may continue to be received in the next cycle via the root cause receiving module 102.

[0081] In this embodiment, the state change of the root cause may include that the root fault in the root cause that triggers the failure corresponding to the failure message is different in the previous cycle and in the current cycle. In other words, the state change of the root cause may include but is not limited to: in the case where the failure has always existed, the failure (Failure) was triggered by a certain root fault in the previous cycle, but is no longer or no longer only triggered by this root fault in the current cycle. Figure 2 As shown, as an example but not a limitation, there are two root causes in the first failure message, corresponding to failures caused by different root faults in different cycles (from Fault 1 to Fault 2, that is, no longer caused by Fault 1); there are three root causes in the second failure message, corresponding to failures caused by different root faults in different cycles (from Fault 1 to Fault 1 and Fault 2, that is, no longer caused by Fault 1 alone).

[0082] In the above embodiment of the present invention, the processing result output module 106 may be further configured to output the updated root cause to the display unit and the storage unit, and the root cause receiving module 102 may be further configured to continue receiving the root cause in the next cycle if the root cause has no state change.

[0083] like Figure 2As shown in FIG. 1 , the fault details page also displays the fault information associated with these failure messages. The fault information includes FIM code, Failure Name, Equipment Name, and Count. When FIM code is selected, the processing result output module 106 can also be optionally configured to jump to the maintenance manual page including the manual module with the associated manual module ID based on the association between the root cause ID of the root cause included in the fault information and the manual module ID in the maintenance manual ( Figure 2 not shown).

[0084] Figure 3 A flowchart of a method 300 for storing and displaying invalidation messages based on combinatorial logic according to an embodiment of the present disclosure is shown.

[0085] The method 300 begins at step 302 by periodically receiving root causes.

[0086] Next, the method 300 proceeds to the decision step 304 to determine whether there is an activation state in the root cause. If yes, the method 300 proceeds to the step 306 to determine whether the deactivation message associated with the activation state is triggered; if not, the method 300 returns to the step 302 to continue receiving the root cause in the next cycle.

[0087] Then, the method 300 proceeds to the decision step 308 to determine whether the invalidation message has a state change compared to the previous cycle. If yes, the method 300 proceeds to step 310 to update the trigger record of the invalidation message. In one embodiment of the present invention, the state change of the invalidation message may include that the invalidation state corresponding to the invalidation message changes from the untriggered state in the previous cycle to the triggered state in the current cycle.

[0088] Figure 4 A detailed flow chart of the step of updating the trigger record of the invalidation message in the invalidation message storage and display method 300 based on combinational logic according to an embodiment of the present invention is shown.

[0089] like Figure 4 As shown, updating the trigger record of the invalidation message may include determining whether there is a trigger record of the invalidation message in the invalidation message storage table at step 402. If yes, proceed to step 404 to increment the trigger count of the trigger record; if not, proceed to step 406 to add the trigger record of the invalidation message in the invalidation message storage table.

[0090] Back to Figure 3, the method 300 continues to step 312, outputting the updated trigger record of the failure message to the display unit and the storage unit. After step 312 is completed, the method 300 returns to step 302 to continue receiving the root cause in the next cycle.

[0091] In another embodiment of the present invention, when it is determined in the determination step 308 that the failure message has not changed in state, the method 300 may further optionally include (continue to) the determination step 314 (indicated by a dotted box), determining whether the root cause has changed in state compared with the previous cycle. If yes, the method 300 may optionally include (continue to) step 316 (indicated by a dotted box), updating the root cause and outputting the updated root cause to the display unit and the storage unit (after completion, the method 300 returns to step 302 to continue receiving the root cause in the next cycle) and in response to the selection of the FIM code in the fault details page displayed by the display unit, jumping to the maintenance manual page including the manual module with the associated manual module ID based on the association between the root cause ID of the received root cause and the manual module ID in the maintenance manual; if not, the method 300 returns to step 302 to continue receiving the root cause in the next cycle. In the above embodiment of the present invention, the state change of the root cause may include that the root fault in the root cause that triggers the failure corresponding to the failure message is different in the previous cycle and in the current cycle.

[0092] In summary, in the presence of a failure message of a logical combination equation, the present invention, in response to the technical problems in the prior art and in combination with the existing design experience, designs a method and system for storing and displaying failure messages based on combinational logic, optimizes the logic of storage and display of failure / fault information, further improves the integrity and accuracy of the information, and improves the reliability of storage and display of the root cause, which makes it convenient for maintenance personnel to directly operate the isolation procedures related to the recorded and stored root causes without completing all the fault isolation program operations, effectively reducing the troubleshooting program operations, improving maintenance efficiency, shortening maintenance time, and reducing operating costs.

[0093] Embodiments of the present invention have been described above with reference to block diagrams and / or the operating instructions of methods, systems, and computer program products according to embodiments of the present invention. Each function / action noted in the frame may occur in an order different from that shown in any flow chart. For example, depending on the function / action involved, two frames shown in succession may actually be performed substantially simultaneously, or these frames may sometimes be performed in an opposite order.

[0094] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention 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 by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for storing and displaying failure messages based on combinational logic, the method comprising: Periodically receive root causes; determining whether an activation state exists in the root cause; determining, in the presence of the activation state, that a deactivation message associated with the activation state is triggered; Determine whether the invalidation message has a state change compared with the previous cycle; When the invalidation message changes state, updating the trigger record of the invalidation message includes: Determine whether there is the trigger record of the invalidation message in the invalidation message storage table; Incrementally increase the triggering count of the triggering record if the triggering record exists; adding the trigger record of the invalidation message to the invalidation message storage table if the trigger record does not exist; and The updated trigger record of the invalidation message is output to a display unit and a storage unit. 2 . The method of claim 1 , further comprising continuing to receive the root cause in a next cycle in the absence of the activation state. 3 . The method of claim 1 , wherein the state change of the invalidation message comprises a change in the invalidation state corresponding to the invalidation message from an untriggered state in a previous cycle to a triggered state in a current cycle.

4. The method of claim 1, further comprising: When the invalidation message does not change state, determining whether the root cause changes state compared with the previous cycle; updating the root cause when a state change occurs to the root cause and outputting the updated root cause to the display unit and the storage unit; In response to a selection of a FIM code in a fault detail page displayed by the display unit, jumping to a maintenance manual page including a manual module having an associated manual module ID based on an association between a root cause ID of the received root cause and a manual module ID in the maintenance manual; and If the state of the root cause does not change, the root cause continues to be received in the next cycle. 5 . The method of claim 4 , wherein the state change of the root cause comprises that a root fault in the root cause that triggers the failure corresponding to the failure message is different in a previous cycle and in a current cycle.

6. A system for storing and displaying failure messages based on combinational logic, the system comprising: a root cause receiving module configured to periodically receive a root cause; The invalidation message logic processing module is configured to: determining whether an activation state exists in the root cause; determining, in the presence of the activation state, that a deactivation message associated with the activation state is triggered; Determine whether the invalidation message has a state change compared with the previous cycle; When the invalidation message changes state, updating the trigger record of the invalidation message includes: Determine whether there is the trigger record of the invalidation message in the invalidation message storage table; Incrementally increase the triggering count of the triggering record if the triggering record exists; adding the trigger record of the invalidation message to the invalidation message storage table if the trigger record does not exist; and The processing result output module is configured to output the updated trigger record of the invalidation message to a display unit and a storage unit. 7 . The system of claim 6 , wherein the root cause receiving module is further configured to continue receiving the root cause in a next cycle in the absence of the activation state.

8. The system of claim 6, wherein the invalidation message logic processing module is further configured to: If the invalidation message does not change state, determining whether the root cause changes state compared to the previous cycle; and The root cause is updated when a state change occurs to the root cause.

9. The system of claim 8, wherein the processing result output module is further configured to: outputting the updated root cause to the display unit and the storage unit; and In response to selection of the FIM code in the fault detail page displayed by the display unit, jumping to a maintenance manual page including a manual module with an associated manual module ID is performed based on an association between a root cause ID of the received root cause and a manual module ID in the maintenance manual. 10 . The system of claim 8 , wherein the root cause receiving module is further configured to continue receiving the root cause in a next cycle if the root cause has no state change.

Images