Fault filtering and integrating method for health management of IMA platform
By implementing fault filtering and integration for health management on the IMA platform through configuration files, the problem of the large number of fault inputs and outputs and the complexity of logic on the IMA platform is solved, the code maintenance cost is reduced, and the accuracy and scalability of fault reports are improved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- XIAN AVIATION COMPUTING TECH RES INST OF AVIATION IND CORP OF CHINA
- Filing Date
- 2025-12-09
- Publication Date
- 2026-04-14
AI Technical Summary
The large number and complex logic of fault inputs and outputs in the IMA platform's health management result in high code implementation and maintenance costs, making it difficult to extend to fault management of other devices.
Fault filtering and integration are achieved through configuration files. Fault mapping tables, message index tables, and fault filtering threshold tables are defined, and XML and binary configuration files are generated. Fault filtering and integration are then performed using health management software.
It reduces the amount of code, lowers design and maintenance costs, improves the accuracy and reliability of fault reports, and has good scalability.
Smart Images
Figure CN121858490A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of airborne avionics technology, specifically to a fault filtering and integration method for health management of the IMA platform. Background Technology
[0002] The IMA (Integrated Modular Arionics) platform consists of numerous networked devices, including two cabinets, 12-20 general-purpose processing modules, 8-10 switches, and 16-20 remote data processing units. The health management function collects fault monitoring reports from various devices within the IMA platform, filters and integrates these reports, and then sends the integrated platform fault report to the airborne maintenance system and the aircraft control panel signal system.
[0003] According to the definitions of input / output messages and their fields in the functional interface control document issued by the host, the logical integration function of the IMA health management function has at least 10,000 fault inputs and at least 8,500 fault outputs. Each fault output corresponds to one or more fault inputs, with a maximum of 40 fault inputs. Therefore, the fault logic is cumbersome and complex. Furthermore, to prevent false alarms, the IMA health management function needs to filter faults before sending fault reports.
[0004] If all fault and integration processing logic is implemented in the executable code, subsequent modifications become cumbersome, costly, and difficult to maintain. Therefore, a configuration file can be introduced to implement fault filtering and integration. Fault inputs, fault outputs, fault logic, and filtering attributes are written into the configuration file and converted into executable object code. The health management software loads and parses this object code, implementing fault filtering and integration functions based on the configuration file content. Summary of the Invention
[0005] In view of this, this application provides a fault filtering and integration method for health management of the IMA platform, which ensures that fault inputs and outputs can be mapped to the message fields defined in the functional interface control document, and that fault filtering and integration logic can be implemented in the configuration file, reducing the early coding work and the later maintenance and modification costs.
[0006] This application provides the following technical solution: a fault filtering and integration method for health management of an IMA platform, comprising: The fault input and output fields are mapped to the field format "message.dataset.field" according to the message structure in the functional interface control document. Based on each field in the fault output message, the fault input field corresponding to the fault output field is analyzed through the field format to generate a fault mapping table. Assign a unique message identifier MsgId to each input and output message in the fault mapping table, and generate a message index table; Define a fault filtering threshold table, classify faults according to their urgency and set corresponding reporting thresholds; Based on the fault mapping table, the message index table, and the fault filtering threshold table, a binary document format for the configuration file is defined; Based on the required information in the binary document format of the configuration file, define the XML document format of the configuration file, and combine the fault mapping table, the message index table, the fault filtering threshold table, and the function interface control document issued by the host to fill in the fault logic and parameter information in the XML document to obtain the configuration file in XML format. Convert the XML-formatted configuration file into a binary configuration file; The binary configuration file is loaded and parsed by the health management software, and the faults are filtered and integrated based on the configuration information.
[0007] According to one embodiment of this application, in the fault mapping table, each fault output corresponds to one or more fault inputs, the fault input values include active, inactive, and not concerned, and the fault output value is active or inactive.
[0008] According to one embodiment of this application, in the fault filtering threshold table, faults are divided into three levels according to their urgency: urgent, relatively urgent, and general, and each level corresponds to a different reporting threshold.
[0009] According to one embodiment of this application, the binary document format of the configuration file includes a fault input / output relationship table and a fault logic table, wherein: the fault input / output relationship table includes a fault input parameter table and a fault output parameter table; the fault logic table includes a fault logic index and corresponding fault integration logic.
[0010] According to one embodiment of this application, in the fault input-output relationship table, each fault output parameter corresponds to a fault logic index, which is used to look up the corresponding fault integration logic in the fault logic table.
[0011] According to one embodiment of this application, the XML-formatted configuration file includes a fault input / output relationship node and a fault logic node; the fault input / output relationship node includes attribute definitions of fault input parameters and output parameters, and the fault logic node includes a fault logic index and several logical detail sub-nodes.
[0012] According to one embodiment of this application, the attributes of the fault input parameters and output parameters include parameter name, message identifier MsgId, parameter value, byte offset, bit offset, and parameter size.
[0013] According to one embodiment of this application, the positions of the fault input parameters and output parameters in the message are determined by byte offset and bit offset.
[0014] Compared with the prior art, the beneficial effects that at least one technical solution adopted in the embodiments of this specification can achieve include at least: (1) The fault input and output fields in the configuration file are defined according to the message structure definition in the functional interface control document, which fully realizes the mapping between the functional interface file and the configuration file, and ensures the consistency between the health management software receiving and sending messages and the functional interface control document.
[0015] (2) Due to the large number of input and output parameters and the complexity of fault logic, the fault logic is implemented using configuration files, which greatly reduces the amount of code.
[0016] (3) The fault mapping table contains the mapping between fault outputs and multiple fault inputs under all conditions, and the values in the table have only three cases. Each parameter occupies only 2 bits in the binary file. The message index table maps each message name to a number, and the fault input / output relationship table uses byte offset and bit offset to obtain the position of the parameter in the message. All of these convert the string to an integer, which greatly saves space in the configuration file binary document.
[0017] (4) Because the fault filtering and integration logic is configurable, the cost of changing the design, integration and validation process of health management functions can be minimized.
[0018] (5) It has strong scalability. Each device in the IMA also needs to report fault monitoring reports, and the underlying fault input needs to be filtered and integrated. Therefore, the fault filtering and integration method based on configuration files proposed in this invention can be extended to the fault management of other devices.
[0019] (6) An additional fault filtering mechanism was designed under the fault integration logic, which improved the ability of the health management function to prevent false alarms and increased the accuracy and credibility of the fault reports. Attached Figure Description
[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 This is a diagram showing the relationship between the health management fault filtering and integration configuration file and the health management software according to an embodiment of the present invention. Figure 2This is a diagram showing the relationship between the binary format definition and the XML document format definition of the health management fault filtering and integration configuration file in this embodiment of the invention. Figure 3 This is a flowchart of the health management fault filtering and integrated configuration file generation process according to an embodiment of the present invention. Detailed Implementation
[0022] The embodiments of this application will now be described in detail with reference to the accompanying drawings.
[0023] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. This application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, in the absence of conflict, the following embodiments and features in the embodiments can be combined with each other. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0024] This invention provides a fault filtering and integration method for health management of an IMA platform, including: The fault input and output fields are mapped to the field format "message.dataset.field" according to the message structure in the functional interface control document. Based on each field in the fault output message, the fault input field corresponding to the fault output field is analyzed through the field format to generate a fault mapping table. Assign a unique message identifier MsgId to each input and output message in the fault mapping table, and generate a message index table; Define a fault filtering threshold table, classify faults according to their urgency and set corresponding reporting thresholds; Based on the fault mapping table, the message index table, and the fault filtering threshold table, a binary document format for the configuration file is defined; Based on the required information in the binary document format of the configuration file, define the XML document format of the configuration file, and combine the fault mapping table, the message index table, the fault filtering threshold table, and the function interface control document issued by the host to fill in the fault logic and parameter information in the XML document to obtain the configuration file in XML format. Convert the XML-formatted configuration file into a binary configuration file; The binary configuration file is loaded and parsed by the health management software, and the faults are filtered and integrated based on the configuration information.
[0025] This invention implements an IMA health management fault filtering and integration method through configuration files, which solves the problem that fault logic is difficult to implement and modify in code due to the large number of fault inputs and outputs and the complexity of fault logic.
[0026] In some embodiments, in the fault mapping table, each fault output corresponds to one or more fault inputs, and the fault input values include active, inactive, and unconcerned, while the fault output value is active or inactive.
[0027] In some embodiments, the fault filtering threshold table categorizes faults into three levels based on their urgency: urgent, relatively urgent, and general, each corresponding to a different reporting threshold.
[0028] In some embodiments, the binary document format of the configuration file includes a fault input / output relationship table and a fault logic table, wherein: the fault input / output relationship table includes a fault input parameter table and a fault output parameter table; the fault logic table includes a fault logic index and corresponding fault integration logic. In the fault input / output relationship table, each fault output parameter corresponds to a fault logic index, which is used to look up the corresponding fault integration logic in the fault logic table.
[0029] In some embodiments, the XML-formatted configuration file includes fault input / output relationship nodes and fault logic nodes. The fault input / output relationship nodes include attribute definitions for fault input parameters and output parameters, and the fault logic nodes include a fault logic index and several logical detail sub-nodes. The attributes of the fault input parameters and output parameters include parameter name, message identifier MsgId, parameter value, byte offset, bit offset, and parameter size. The position of the fault input parameters and output parameters within the message is determined by byte offset and bit offset.
[0030] like Figures 1-3 As shown in the figure, a fault filtering and integration method for health management of an IMA platform according to an embodiment of the present invention specifically includes the following steps: 1. Since the fault inputs and outputs of the health management function all originate from the message fields defined in the function interface control document, a mapping is established between the fault inputs and outputs and the function interface control document. The input and output fields are organized into the format "message.dataset.field" for a one-to-one mapping between fault inputs and outputs and the function interface control document.
[0031] 2. Based on each field in the fault output message, analyze its corresponding fault input message and fault input fields using the "message.dataset.field" format from step 1 to obtain a fault mapping table. For each fault output field, analyze the output value corresponding to all fault input fields under different scenarios and with different values.
[0032] 3. Organize the input and output messages involved in the fault mapping table in step 2, number all messages, that is, each message has a fixed MsgId, and form a message index table.
[0033] 4. Define a fault filtering threshold table to classify reported faults into three categories: urgent, relatively urgent, and general. Define a reporting threshold for each fault; for general urgent faults, the reporting threshold is higher. Based on the classification, the fault filtering thresholds can be divided into: 1 (urgent), 2 (relatively urgent), and 3 (general).
[0034] 5. Based on the fault mapping table, message index table, and fault filtering threshold table obtained in steps 2, 3, and 4, jointly define the binary document format of the configuration file. The binary document format definition of the configuration file includes the definitions of the fault input / output relationship table and the fault logic table. The fault input / output relationship table contains input parameters and output parameters; defining these two parameters separately yields the fault input parameter table and the fault output parameter table. For example... Figure 2 As shown.
[0035] 6. Based on the required information for the binary configuration file format in step 5, define the format of the XML configuration file. The XML document consists of nodes and attributes. The XML document mainly includes two nodes: the fault input / output relationship node and the fault logic node.
[0036] 7. Based on the configuration file XML document format defined in step 6, and combining the fault mapping table, message index table, fault filtering threshold table from steps 2, 3, and 4, as well as the functional interface control document issued by the host, fill in the XML document to obtain the health management fault filtering and integration configuration file XML document. For example... Figure 3 As shown.
[0037] 8. Use a tool to convert the XML configuration file obtained in step 7 into a final binary format health management fault filtering and integration configuration file.
[0038] 9. The health management software loads and parses the health management fault filtering and integration configuration file (binary format). Based on the configuration information, it reads the mapping information between fault outputs and inputs, logical information, and filtering threshold information, and performs fault filtering and integration according to the configuration information. For example... Figure 1 As shown.
[0039] In one specific embodiment, the fault filtering and integration method for health management of the IMA platform of this embodiment specifically includes the following steps: Step 1: Since the fault inputs and outputs of the health management function all originate from the message fields defined in the function interface control document, it is necessary to map the fault inputs and outputs to the function interface control document. In the function interface control document, the message structure involved in fault filtering and integration of the health management function is fixed; that is, one message contains several datasets, and one dataset contains several fields. Therefore, the input and output fields are organized into the form of "message.dataset.field" for a one-to-one mapping between fault inputs and outputs and the function interface control document.
[0040] Step 2: Based on each field in the fault output message, analyze its corresponding fault input message and fault input field using the "message.dataset.field" format from Step 1 to obtain a fault mapping table. For each fault output field, it is necessary to analyze the output value corresponding to all fault input fields under different scenarios and with different values. Input values include three types: active (1), inactive (0), and uninterested (X). Output values include two types: active (1) and inactive (0). Table 1 shows an example of the corresponding value table between fault output A and multiple fault inputs.
[0041] Table 1. Examples of corresponding values for fault output A and its fault input.
[0042] Step 3: Organize the input and output messages involved in the fault mapping table in Step 2, number all messages, that is, each message has a fixed MsgId, and form a message index table.
[0043] Step 4: Since the IMA health management function reports a wide variety of faults, the reported faults are classified into different levels for the airborne maintenance system and the aircraft control board signal system. Some faults will have a significant impact on the aircraft and require the crew and maintenance personnel to respond as soon as possible. Some faults are of relatively low urgency and therefore need to be filtered before being reported.
[0044] Therefore, reported faults are classified into three categories: urgent, relatively urgent, and general. A reporting threshold value is defined for each fault; for general urgent faults, the reporting threshold value is higher. Based on the classification, the fault filtering threshold values can be divided into: 1 (urgent), 2 (relatively urgent), and 3 (general). That is, for general urgent faults, the fault must be detected three times consecutively before it is confirmed as a fault and can be reported. From this, a fault filtering threshold value table can be obtained.
[0045] Step 5: The fault filtering and integration configuration file should be loaded onto the device. The configuration file is loaded and its contents are read when the health management function is running; therefore, the configuration file should be a binary document. For example... Figure 2As shown, based on the fault mapping table, message index table, and fault filtering threshold table obtained in steps 2, 3, and 4, the format definition of the binary document for the configuration file is jointly defined. The format definition of the binary document for the configuration file includes the definitions of the fault input / output relationship table and the fault logic table.
[0046] Step 5.1: Design the fault input / output relationship table. The fault input / output relationship table describes the correspondence between one or more fault inputs and one fault output. As shown in Table 2, the fault input / output relationship table is defined.
[0047] Table 2 Fault Input / Output Relationship Definition
[0048] The fault input-output relationship table contains input parameters and output parameters. By defining these two parameters, we can obtain the fault input parameter table and the fault output parameter table.
[0049] Step 5.1.1: Define the fault input parameter table, with attributes and descriptions as shown in Table 3. These attributes determine the location of the fault input parameters in the received message.
[0050] Table 3 Binary Document Fault Input Parameter Table
[0051] Step 5.1.2: Define the fault output parameter table, with attributes and descriptions shown in Table 4 below. These attributes determine the position of the fault output parameters in the transmitted message and their corresponding fault logic index.
[0052] Table 4 Binary Document Fault Output Parameter Table
[0053] Step 5.2: Define the fault logic table, including: index (fault logic index value) and fault_logic (fault integration logic). Since faults may occur under various conditions, and a fault output may correspond to multiple inputs, the fault logic table consists of multiple two-dimensional arrays. Each two-dimensional array corresponds to the fault integration logic of a certain fault and has a unique index value.
[0054] Step 6: Based on the information required for the binary document format of the configuration file in Step 5, define the format of the XML document configuration file. As an editable and easily understood document format, XML documents can be converted into binary format documents using tools. Therefore, it is necessary to design an XML document configuration file for fault filtering and integration logic. The XML document consists of nodes and attributes. The XML document mainly includes two nodes: the fault input / output relationship node and the fault logic node.
[0055] Step 6.1: The fault input / output relationship node includes multiple sets of correspondences between output parameters and input parameters, and one output can correspond to multiple inputs. The attributes included in the output parameter node in the XML document format definition are the same as in Table 4, with the addition of an "OutputName" attribute for easier editing by designers. The attributes included in the input parameter node in the XML document format definition are the same as in Table 3, with the addition of an "InputName" attribute. Table 5 below shows the fault input and output parameter table in the configuration file XML document.
[0056] Table 5 XML Document Fault Input Parameter Table
[0057] Table 6 XML Document Fault Output Parameters Table
[0058] Step 6.2: Each fault logic node corresponds to a fault integration logic with an output parameter, including an index (fault logic index value) and several LogicDetail child nodes. Each LogicDetail node represents the input parameter value under a certain condition.
[0059] Step 7: Based on the configuration file XML document format defined in Step 6, and combined with the fault mapping table, message index table, fault filtering threshold value table and function interface control document issued by the host in Steps 2, 3 and 4, fill in the XML document to obtain the health management fault filtering and integration configuration file XML document.
[0060] Step 7.1: Fill in the value and InputName attributes of the input parameter node defined in the XML document format in Step 6.1 according to the input parameters in the fault mapping table in Step 2. Fill in the value and OutputName attributes of the output parameter node in the XML document in Step 6.1 according to the output parameters in the fault mapping table in Step 2.
[0061] Step 7.2: Fill in the fault logic node in the XML document in Step 6.2 according to the fault mapping table in Step 2.
[0062] Step 7.3: Fill in the MsgId attribute of the input and output parameter nodes in the XML document in Step 6.1 according to Step 3 and the InputName and OutputName attributes.
[0063] Step 7.4: Fill in the threshold attribute of the output parameter node in the XML document in Step 6.1 according to Step 4 and the OutputName attribute.
[0064] Step 7.5: Fill in the logic_index attribute of the output parameter node in the XML document in Step 6.1 according to Step 7.2 and the OutputName attribute.
[0065] Step 7.6: Based on the functional interface control document and the InputName and OutputName attributes, fill in the input_offset_byte, input_offset_bit, and input_bit_size attributes of the input parameter node and the output_offset_byte, output_offset_bit, and output_bit_size attributes of the output parameter node in the XML document.
[0066] Step 8: Use a tool to convert the XML configuration file obtained in Step 7 into a final binary format file for health management fault filtering and integration configuration.
[0067] Step 9: As attached Figure 1 As shown, the health management software loads and parses the binary format file of the health management fault filtering and integration configuration file, reads the mapping information, logic information and filtering threshold information of fault output and fault input according to the configuration information, and performs fault filtering and integration according to the configuration information.
[0068] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A fault filtering and integration method for health management on an IMA platform, characterized in that, include: The fault input and output fields are mapped to the field format "message.dataset.field" according to the message structure in the functional interface control document. Based on each field in the fault output message, the fault input field corresponding to the fault output field is analyzed through the field format to generate a fault mapping table. Assign a unique message identifier MsgId to each input and output message in the fault mapping table, and generate a message index table; Define a fault filtering threshold table, classify faults according to their urgency and set corresponding reporting thresholds; Based on the fault mapping table, the message index table, and the fault filtering threshold table, a binary document format for the configuration file is defined; Based on the required information in the binary document format of the configuration file, define the XML document format of the configuration file, and combine the fault mapping table, the message index table, the fault filtering threshold table, and the function interface control document issued by the host to fill in the fault logic and parameter information in the XML document to obtain the configuration file in XML format. Convert the XML-formatted configuration file into a binary configuration file; The binary configuration file is loaded and parsed by the health management software, and the faults are filtered and integrated based on the configuration information.
2. The fault filtering and integration method for IMA platform health management according to claim 1, characterized in that, In the fault mapping table, each fault output corresponds to one or more fault inputs. The fault input values include active, inactive, and uninterested, and the fault output values are active or inactive.
3. The fault filtering and integration method for IMA platform health management according to claim 1, characterized in that, In the fault filtering threshold table, faults are divided into three levels according to their urgency: urgent, relatively urgent, and general, and each level corresponds to a different reporting threshold.
4. The fault filtering and integration method for IMA platform health management according to claim 1, characterized in that, The binary document format of the configuration file includes a fault input / output relationship table and a fault logic table, wherein: the fault input / output relationship table includes a fault input parameter table and a fault output parameter table; the fault logic table includes a fault logic index and the corresponding fault integration logic.
5. The fault filtering and integration method for IMA platform health management according to claim 4, characterized in that, In the fault input-output relationship table, each fault output parameter corresponds to a fault logic index, which is used to find the corresponding fault integration logic in the fault logic table.
6. The fault filtering and integration method for IMA platform health management according to claim 1, characterized in that, The XML-formatted configuration file includes fault input / output relationship nodes and fault logic nodes; the fault input / output relationship nodes include attribute definitions for fault input parameters and output parameters, and the fault logic nodes include fault logic indexes and several logic detail sub-nodes.
7. The fault filtering and integration method for IMA platform health management according to claim 6, characterized in that, The attributes of the fault input and output parameters include parameter name, message identifier MsgId, parameter value, byte offset, bit offset, and parameter size.
8. The fault filtering and integration method for IMA platform health management according to claim 7, characterized in that, The positions of the fault input and output parameters in the message are determined by byte offset and bit offset.