Fault modeling method based on interactive structured data design

Abstract

One aspect of the disclosure relates to a fault modeling method comprising determining one or more signals corresponding to one or more onboard interface data associated with a fault; constructing one or more corresponding bottom fault logic units based on the one or more signals; based on the bottom layer fault logic unit and one or more logic operators, constructing fault combinational logic comprising zero layer, one layer or multiple layers of nesting; generating a fault combinatorial logic expression based on the constructed fault combinatorial logic; and generating at least one of a corresponding extensible markup language file and a binary file based on the generated fault combinatorial logic expression.

Description

Technical Field

[0001] This application generally relates to data modeling, and more particularly to a fault modeling method based on interactive structured data design. Background Technology

[0002] In aircraft onboard maintenance systems, the aircraft health management unit needs to perform fault modeling for each component system of the aircraft. These fault models are the foundation for the onboard maintenance system to make accurate judgments on the health status of the aircraft. However, existing fault modeling methods cannot directly generate fault models for onboard systems for some complex faults, requiring a large amount of manual verification and data conversion before they can be used in aircraft onboard maintenance systems.

[0003] Therefore, there is a need in this field for improved schemes and systems for fault modeling of airborne maintenance systems. Summary of the Invention

[0004] One aspect of this disclosure relates to a fault modeling method, comprising: determining one or more signals corresponding to one or more airborne interface data related to a fault; constructing one or more corresponding underlying fault logic units based on the one or more signals; constructing fault combination logic including zero-level, one-level, or multi-level nested layers based on the underlying fault logic units and one or more logic operators; generating fault combination logic expressions based on the constructed fault combination logic; and generating at least one of a corresponding Extensible Markup Language file and a binary file based on the generated fault combination logic expressions.

[0005] According to some exemplary embodiments, determining one or more signals corresponding to one or more airborne interface data related to a fault includes acquiring a signal information mapping table, the signal information mapping table including an identifier of the signal and the signal information; and selecting the one or more signals using the identifier as a primary key.

[0006] According to some exemplary embodiments, the fault modeling method further includes establishing the signal information mapping table, wherein establishing the signal information mapping table includes converting an interface file into an object structure; and performing recursive operations on the object structure to store the obtained information into the signal information mapping table.

[0007] According to some exemplary embodiments, the identifier is a globally unique identifier.

[0008] According to some exemplary embodiments, constructing fault combination logic including zero-level, one-level, or multi-level nested fault logic based on the underlying fault logic unit and one or more logic operators also includes modifying the fault combination logic based on the fault logic interaction interface.

[0009] According to some exemplary embodiments, the fault logic interaction interface includes: a signal information operation area, a logic operation area, and a nested operation area, wherein modifying the fault combination logic based on the fault logic interaction interface includes one or more of the following or any combination thereof: modifying the fault logic unit by performing an operation in the signal information operation area; modifying the logic operator by performing an operation in the logic operation area; and modifying the nesting of the fault combination logic by performing an operation in the nested operation area.

[0010] According to some exemplary embodiments, the fault modeling method further includes generating a modified fault combination logic expression based on the fault combination logic that needs to be modified whenever the fault combination logic is modified based on the fault logic interaction interface.

[0011] Another exemplary aspect of this disclosure relates to a fault logic interaction interface for fault modeling, comprising: a signal information operation area, a logic operation area, and a nested operation area, wherein operations performed in the signal information operation area correspond to modifying fault logic units; operations performed in the logic operation area correspond to modifying logic operators; and operations performed in the nested operation area correspond to modifying the nesting of fault combination logic, wherein the fault combination logic is constructed based on a lower-level fault logic unit and one or more logic operators, and includes zero-level, one-level, or multi-level nesting; and wherein the lower-level fault logic unit is constructed by determining one or more signals corresponding to one or more airborne interface data related to a fault.

[0012] Other aspects of this disclosure include corresponding apparatus, devices, and computer-readable media. Attached Figure Description

[0013] This article will become better understood by referring to the detailed description in conjunction with the accompanying drawings, in which: Figure 1 A schematic diagram of a fault modeling scheme based on interactive structured data design according to an exemplary aspect of this disclosure is shown.

[0014] Figure 2 A schematic diagram of a fault logic interaction interface according to an exemplary aspect of this disclosure is shown.

[0015] Figure 3 A flowchart is shown of a fault modeling method based on interactive structured data design according to an exemplary aspect of this disclosure. Detailed Implementation

[0016] This disclosure proposes a fault modeling method based on interactive structured data design, which can realize the modeling of complex airborne fault models and directly generate model data that can be used for airborne systems, effectively reducing the cost of manual verification and improving the accuracy of airborne maintenance systems.

[0017] The present disclosure will now be described with reference to the embodiments shown in the accompanying drawings. It should be understood that the blocks and logic components in the drawings can be implemented by various hardware and software components that perform specific functions. For the sake of brevity, the embodiments herein can be implemented based on the blocks, logic components, and processing steps in the drawings, or based on other reasonable orders, modifications, combinations, etc.

[0018] Figure 1 A schematic diagram of a fault modeling scheme 100 based on interactive structured data design according to an exemplary aspect of this disclosure is shown.

[0019] like Figure 1 As shown, fault-related signals can be selected from the signal information mapping table 104. According to some exemplary embodiments, the signal information mapping table 104 may be stored in the database 102. According to other exemplary embodiments, the signal information mapping table 104 may also be obtained from other internal or external sources.

[0020] According to some exemplary embodiments, the signal information map 104 may include one or more entries, each entry may include a unique identifier for the signal, and signal information required for fault modeling. This will be described in further detail below. Selecting fault-related signals from the signal information map 104 may include selecting from the one or more entries in the signal information map 104 to select, for example, entries for all signals related to the fault.

[0021] According to an exemplary embodiment, one or more fault logic units are then constructed based on the selected signals, and a basic fault model is built based on these one or more fault logic units. A fault logic unit may include at least one of signal information and / or logical operators, and the fault logic unit may also include a nested structure. In other words, the lowest-level fault logic unit may include a single signal information or a single logical operator. According to an exemplary embodiment, through nesting, a fault logic unit may include a combination of one or more signal information, one or more logical operators, and one or more fault logic units. For example, signal 1 may be a fault logic unit, and signal 2 may be another fault logic unit. The union operation may be a fault logic unit. Thus, ((signal 1) AND (signal 2)) can be a nested fault logic unit, and this nested fault logic unit can further nest with other lower-level (i.e., non-nested) fault logic units and / or nested fault logic units through fault logic units including logical operators.

[0022] According to an exemplary embodiment, a fault logic interaction interface 106 can be generated based on fault logic units to visualize the fault model. The fault logic interaction interface includes a human-computer interaction interface (HCI) for users to edit fault logic units to modify the fault model. For example, editing fault logic units may include, but is not limited to, adding, deleting, and modifying fault logic units and logical operators. Editing fault logic units may also include, but is not limited to, editing nested relationships, such as deleting nested elements, adding nested elements, and modifying nested elements.

[0023] At the same time, whenever human-computer interaction causes a change in the structure of the fault logic unit, resulting in a change in the fault model, it triggers the generation of a structured fault logic expression to express the real-time logical operation results.

[0024] Once the final fault model and its logical expression 108 are determined, since they are all structured data, they can be directly converted into an Extensible Markup Language file 110 and / or a binary file. The binary file can be directly used as input to the airborne maintenance system, eliminating the need for manual verification or error correction using auxiliary tools, thus improving data accuracy and reducing the workload and difficulty for operators.

[0025] The following describes a fault modeling scheme based on interactive structured data design according to another exemplary aspect of this disclosure.

[0026] This exemplary aspect of the fault modeling scheme based on interactive structured data design can model airborne faults. Specifically, the fault modeling scheme based on interactive structured data design may include establishing a signal information mapping table.

[0027] According to some exemplary embodiments, establishing a signal information mapping table may include processing all airborne interface data to obtain a table structure that maps the globally unique identifier of a signal to all the required information of the signal, thereby enabling rapid retrieval and location of airborne data signals.

[0028] According to some exemplary embodiments, establishing a signal information mapping table may include converting the interface file into an object structure and storing it in memory, then recursively operating on the memory object to obtain all signal information. The signal information is then stored in the table, and a globally unique identifier for the signal information is used as the primary key for quick signal location.

[0029] According to some exemplary embodiments, for example, converting interface files into an object structure programmatically may include first parsing all interface control files, where the interface control files are all Extensible Markup Language (XML) files. According to some exemplary embodiments, converting interface files into an object structure programmatically may include then converting these files into data objects in memory and recursively obtaining information about all signals. According to some exemplary embodiments, the interface control files may include a tree structure. In such embodiments, recursion may include traversing the tree structure to recursively obtain information about all signals. In other exemplary embodiments, the interface control files may include other data structures, and recursion may include recursively traversing the data structure using other algorithms to obtain information about all signals.

[0030] According to some exemplary embodiments, establishing a signal information mapping table may further include storing signal information into a table structure, such as the signal information mapping table shown in Table 1 below.

[0031] Table 1 illustrates an example of a signal information mapping table structure according to an exemplary embodiment of the present disclosure. As shown in Table 1, an example of a signal information mapping table structure according to an exemplary embodiment of the present disclosure may include one or more entries, each entry of which may correspond to a signal, for example.

[0032] Table 1. Structure of Signal Information Mapping Table

[0033] According to an exemplary embodiment, the signal information mapping table structure may include at least a globally unique identifier of the signal information as a primary key for quick signal location, and may also include the signal information of the corresponding signal. According to an exemplary embodiment, the globally unique identifier of the signal information may include, but is not limited to, hexadecimal numbers as shown in Table 1. According to an exemplary embodiment, the signal information of the corresponding signal may include, but is not limited to, for example, signal name, signal type, signal length, signal offset, etc. Specific signal information may be added, deleted, or modified as needed.

[0034] This fault modeling scheme based on interactive structured data design may include the construction of fault logic unit components. As previously mentioned, a fault logic unit may include at least one of signal information and / or logical operators, and the fault logic unit may also include a nested structure. In other words, the lowest-level fault logic unit may include a single signal information or a single logical operator. According to an exemplary embodiment, through nesting, a combination of one or more signal information, one or more logical operators, and one or more fault logic units may be included.

[0035] According to an exemplary embodiment, the fault modeling scheme based on interactive structured data design may further include selecting signals from a signal information mapping table as fault logic units to construct a basic fault model.

[0036] According to an exemplary embodiment, a fault logic unit refers to a nested structure composed of signal information or logical operators, which is the basic structure of a fault model. Each fault logic unit includes a type, a name, and an array of nested sub-units. The type of a fault logic unit includes operators and signal information, the name of the fault logic unit refers to the name of the signal information or the name of the operator, and the array of nested sub-units refers to the sub-fault logic units under this fault logic unit that perform logical operations. Each fault logic unit may have zero or more sub-units.

[0037] Next, the fault modeling scheme based on interactive structured data design may further include selecting all fault-related signals from a signal information mapping table, and constructing fault logic units based on these signals. According to some exemplary embodiments, the structure of the fault logic unit may be as shown in Table 2. Signal-type logic units are the innermost nested units, and operator-type logic units contain several logic units performing this operation, including signal-type logic units and nested fault logic units of operator type containing several other signal units.

[0038] Table 2 below illustrates the fault logic unit structure according to exemplary embodiments of the present disclosure.

[0039] Table 2 Fault Logic Unit Structure

[0040] As shown in Table 2, the fault logic unit structure may include signal types and logic operator types. For signal types, their sub-units can be empty. On the other hand, for logic operator types, their sub-units may include signal 1 logic units, nested logic units of operator types, etc.

[0041] Then, the fault modeling scheme based on interactive structured data design can further include the establishment of a fault logic interaction interface, which is an interaction interface generated based on fault logic unit components to generate a visual fault model. Figure 2 A schematic diagram of a fault logic interaction interface 200 according to an exemplary aspect of this disclosure is shown. Figure 2 As shown, the fault logic interaction interface 200 is a human-machine interface generated based on fault logic units, which can be divided into a signal information operation area 202, a logic operation area 204, and a nested operation area 206. The signal operation area 202 corresponds to fault logic units with operation type of signal information, and this logic unit can be deleted from the human-machine interface; the logic operation area 204 corresponds to fault logic units with type of operator, and logical operators such as "AND" or "OR" can be selected; the nested operation area 206 is the area for performing nested logical operations, and dragging one logic unit into another logic unit will trigger the operation.

[0042] According to an exemplary embodiment, to perform an operation between one logic unit and another logic unit (such as logic units represented by signal 1 and signal 2), simply drag signal 2 to the nested operation area at the lower right of signal 1. A logical judgment is triggered by a human-machine interface event, generating a logic unit of type operator. This logic unit contains two sub-units, namely two signal-type logic units named signal 1 and signal 2. The generated nested logic unit can then continue to perform operations with other signals.

[0043] According to an exemplary embodiment, the fault modeling scheme based on interactive structured data design may further include the generation of fault combination logic expressions. The fault combination logic expressions can be structured combination logic results generated in real time based on information from the fault logic interactive interface. For example, in... Figure 2 The fault logic interaction interface 200 may or may not include a fault combination logic expression display area 208. The fault combination logic expression display area 208 can display the fault combination logic expressions of the visualized fault models included in the signal information operation area 202, logic operation area 204, and nested operation area 206 of the fault logic interaction interface 200. The fault combination logic expression is a type of structured data. The fault combination logic expression can be generated in real time based on the logic expressed by the fault logic interaction interface, and the correct parentheses can be matched according to the nesting level of the fault logic unit.

[0044] At the same time, whenever human-computer interaction causes a change in the structure of the fault logic unit, resulting in a change in the fault model, it triggers the generation of a structured fault logic expression to express the real-time logical operation results.

[0045] According to an exemplary embodiment, the fault modeling scheme based on interactive structured data design may further include the generation of fault combination logic onboard information. The generation of fault combination logic onboard information may include generating corresponding Extensible Markup Language (Extreme Markup Language) files and binary files based on logical expressions to complete fault modeling.

[0046] Once the final fault model and its logical expression are determined, since they are all structured data, they can be directly converted into Extensible Markup Language (EXPLAIN) files and / or binary files. Binary files can be directly used as input to the airborne maintenance system, eliminating the need for manual verification or error correction using auxiliary tools, thus improving data accuracy and reducing the workload and difficulty for operators.

[0047] Figure 3 A flowchart of a fault modeling method 300 based on interactive structured data design according to an exemplary aspect of this disclosure is shown. According to the fault modeling method 300 based on interactive structured data design, in block 302, data processing and extraction of interface control file data are performed to generate a signal information mapping table.

[0048] According to some exemplary embodiments, the signal information mapping table may be stored in a database. According to other exemplary embodiments, the signal information mapping table may also be obtained from other internal or external sources.

[0049] According to some other exemplary embodiments, data processing and extraction of interface control file data may further include establishing a signal information mapping table. According to some exemplary embodiments, establishing a signal information mapping table may include processing all airborne interface data to obtain a table structure mapping globally unique identifiers of signals to all required information for the signals, thereby enabling rapid retrieval and location of airborne data signals.

[0050] According to some exemplary embodiments, establishing a signal information mapping table may include converting the interface file into an object structure and storing it in memory, then recursively operating on the memory object to obtain all signal information. The signal information is then stored in the table, and a globally unique identifier for the signal information is used as the primary key for quick signal location.

[0051] According to some exemplary embodiments, for example, converting interface files into an object structure programmatically may include first parsing all interface control files, where the interface control files are all Extensible Markup Language (XML) files. According to some exemplary embodiments, converting interface files into an object structure programmatically may include then converting these files into data objects in memory and recursively obtaining information about all signals. According to some exemplary embodiments, the interface control files may include a tree structure. In such embodiments, recursion may include traversing the tree structure to recursively obtain information about all signals. In other exemplary embodiments, the interface control files may include other data structures, and recursion may include recursively traversing the data structure using other algorithms to obtain information about all signals.

[0052] According to some exemplary embodiments, establishing a signal information mapping table may further include storing signal information in a table structure, such as the signal information mapping table shown in Table 1 above. Data processing and extraction of interface control file data may include selecting fault-related signals from the signal information mapping table.

[0053] The fault logic unit is constructed in box 304 according to the fault modeling method 300 based on interactive structured data design.

[0054] According to some exemplary embodiments, data processing and extraction of interface control file data may include selecting fault-related signals from a signal information map table.

[0055] According to an exemplary embodiment, constructing fault logic units may include building one or more fault logic units based on selected signals, and building a basic fault model based on the one or more fault logic units. A fault logic unit may include at least one of signal information and / or logical operators, and the fault logic unit may also include a nested structure. In other words, the lowest-level fault logic unit may include a single signal information or a single logical operator. According to an exemplary embodiment, through nesting, a fault logic unit may include a combination of one or more signal information, one or more logical operators, and one or more fault logic units.

[0056] This fault modeling scheme based on interactive structured data design may further include selecting all fault-related signals from a signal information mapping table and constructing fault logic units based on these signals. According to some exemplary embodiments, the structure of the fault logic unit may be as shown in Table 2 above. Signal-type logic units are the innermost nested units, and operator-type logic units contain several logic units performing this operation, including signal-type logic units and nested fault logic units of operator type containing several other signal units.

[0057] The fault logic nesting structure is generated in box 306 according to the fault modeling method 300 based on interactive structured data design.

[0058] According to at least some exemplary embodiments, generating a nested fault logic structure in block 306 may include generating a fault logic interaction interface 106 based on fault logic units to visualize the fault model. The fault logic interaction interface includes a human-computer interface (HCI) for users to edit fault logic units to modify the fault model. For example, editing fault logic units may include, but is not limited to, adding, deleting, and modifying fault logic units and logical operators. Editing fault logic units may also include, but is not limited to, editing nesting relationships, such as deleting nested units, adding nested units, and modifying nested units.

[0059] At the same time, whenever human-computer interaction causes a change in the structure of the fault logic unit, resulting in a change in the fault model, it triggers the generation of a structured fault logic expression to express the real-time logical operation results.

[0060] According to some exemplary embodiments, the fault logic interaction interface is a human-machine interface generated based on fault logic units, which can be divided into a signal information operation area, a logic operation area, and a nested operation area. The signal operation area corresponds to fault logic units with operation type of signal information, and this logic unit can be deleted from the human-machine interface; the logic operation area corresponds to fault logic units with type of operator, and logical operators such as "AND" or "OR" can be selected; the nested operation area is the area for performing nested logical operations, and dragging one logic unit into another logic unit will trigger the operation.

[0061] According to an exemplary embodiment, a logical unit of type operator can be generated by dragging and dropping a logical unit into or out of the nested operation area, triggered by a human-machine interface event. The generated nested logical unit can then continue to perform operations with other signals.

[0062] According to an exemplary embodiment, the fault modeling scheme based on interactive structured data design may further include the generation of fault combination logic expressions. The fault combination logic expressions can be structured combination logic results generated in real time based on information from the fault logic interactive interface. For example, the fault logic interactive interface may or may not include a fault combination logic expression display area. The fault combination logic expression display area can display the fault combination logic expressions of the visualized fault model included in the signal information operation area, logic operation area, and nested operation area of ​​the fault logic interactive interface. The fault combination logic expression is a type of structured data. The fault combination logic expression can be generated in real time based on the logic expressed by the fault logic interactive interface, and the correct brackets can be matched according to the nesting level of the fault logic unit.

[0063] The generation of nested fault logic structures in box 306 may also include the generation of onboard information for fault combination logic. Generating onboard information for fault combination logic may include generating corresponding Extensible Markup Language (Extreme Markup Language) files and binary files based on logical expressions, thus completing fault modeling.

[0064] Once the final fault model and its logical expression are determined, since they are all structured data, they can be directly converted into Extensible Markup Language (EXPLAIN) files and / or binary files. Binary files can be directly used as input to the airborne maintenance system, eliminating the need for manual verification or error correction using auxiliary tools, thus improving data accuracy and reducing the workload and difficulty for operators.

[0065] Various aspects and embodiments of this disclosure propose a nested structure to define fault models, so that each fault logic unit has a similar composition structure and can be nested with each other. This not only allows for the flexible expression of various complex fault combination logics, but also allows for interactive operation of the model through a graphical interface. Furthermore, since all logic units can only perform predefined operations, such as adding, deleting, and nesting, the current structured fault logic model can be obtained in real time through the graphical interface, and logical expressions conforming to mathematical syntax can be formed based on the model, solving the problem of inaccurate manually entered expressions. Moreover, since the constructed model and logical expressions are structured data, there are no syntax errors, so they can be directly parsed to generate corresponding Extensible Markup Language (Extreme Markup Language) files and binary files, reducing the workload of data parsing and improving data accuracy.

[0066] Meanwhile, whenever the human-computer interaction interface changes, i.e., the structure of the logic unit changes, a method for generating structured fault logic expressions is triggered. This method recursively reads the nested structure of the logic units, combines them from the lowest level of operation, adds corresponding parentheses to each level of operation to form the current fault combination logic expression, avoiding syntax errors such as mismatched parentheses that may occur when manually defining them, and allows the operation results to be viewed in real time.

[0067] Finally, since the fault model and its logical expressions are structured data, they can be directly converted into Extensible Markup Language (EXPLAIN) files and binary files. The binary files can be directly used as input to the airborne maintenance system, eliminating the need for manual verification or error correction using auxiliary tools, thus improving data accuracy and reducing the workload and difficulty for operators.

[0068] The above descriptions are merely exemplary embodiments of the present invention. However, the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

[0069] The various illustrative logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0070] The steps of the methods or algorithms described in this disclosure can be implemented directly in hardware, in a software module executed by a processor, or in a combination of both. The software module can reside in any form of storage medium known in the art. Some examples of usable storage media include random access memory (RAM), read-only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, and so on. The software module can include a single instruction or many instructions, and can be distributed across several different code segments, across different programs, and across multiple storage media. The storage medium can be coupled to the processor so that the processor can read and write information from / to the storage medium. Alternatively, the storage medium can be integrated into the processor.

[0071] The methods disclosed herein include one or more steps or actions for achieving the described methods. These method steps and / or actions may be interchanged with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0072] A processor can execute software stored on a machine-readable medium. The processor may be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Software should be interpreted broadly as instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As examples, a machine-readable medium may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be implemented in a computer program product. This computer program product may include packaging materials.

[0073] In hardware implementations, machine-readable media can be a separate part of the processing system from the processor. However, as those skilled in the art will readily appreciate, machine-readable media or any portion thereof can be external to the processing system. As examples, machine-readable media may include transmission lines, data-modulated carrier waves, and / or computer products separate from wireless nodes, all accessible to the processor via a bus interface. Alternatively or additionally, machine-readable media or any portion thereof may be integrated into the processor, such as caches and / or general-purpose register files.

[0074] The processing system can be configured as a general-purpose processing system having one or more microprocessors providing processor functionality, and external memory providing at least a portion of machine-readable medium, all linked to other supporting circuitry via an external bus architecture. Alternatively, the processing system can be implemented using an ASIC (Application-Specific Integrated Circuit) with a processor, bus interface, user interface (in the case of an access terminal), supporting circuitry, and at least a portion of machine-readable medium integrated on a single chip, or using one or more FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gated logic, discrete hardware components, or any other suitable circuitry, or any combination of circuitry capable of performing the various functionalities described throughout this disclosure. Depending on the specific application and the overall design constraints imposed on the system, those skilled in the art will recognize how best to implement the functionality described regarding the processing system.

[0075] Machine-readable media may include several software modules. These software modules include instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. These software modules may include transfer modules and receive modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a trigger event occurs, a software module may be loaded from a hard drive into RAM. During the execution of a software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may subsequently be loaded into a general-purpose register file for processor execution. In the context of the functionality of the software module described below, it will be understood that such functionality is implemented by the processor when the processor executes the instructions from the software module.

[0076] If implemented in software, the functions can be stored or transmitted as one or more instructions or codes on or through a computer-readable medium. Computer-readable media includes both computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Any connection is also legitimately referred to as computer-readable media. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then that coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray® discs, where disks typically reproduce data magnetically, while discs optically reproduce data using lasers. Therefore, in some aspects, computer-readable media may include non-transient computer-readable media (e.g., tangible media). Additionally, in other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0077] Therefore, certain aspects may include computer program products for performing the operations set forth herein. For example, such computer program products may include computer-readable media on which instructions are stored (and / or encoded) that can be executed by one or more processors to perform the operations described herein. In some aspects, computer program products may include packaging materials.

[0078] It will be understood that the claims are not limited to the precise configurations and components described above. Various modifications, substitutions, and variations can be made to the layout, operation, and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A fault modeling method, comprising: Identify one or more signals corresponding to one or more airborne interface data related to the fault; One or more corresponding underlying fault logic units are constructed based on the one or more signals; Based on the underlying fault logic unit and one or more logic operators, construct fault combination logic including zero-level, one-level, or multi-level nested logic; Based on the constructed fault combination logic, generate fault combination logic expressions; as well as At least one of the corresponding Extensible Markup Language (Extreme Markup Language) file and binary file is generated based on the generated fault combinational logic expression.

2. The fault modeling method of claim 1, wherein, Identifying one or more signals corresponding to one or more airborne interface data related to a fault includes: Obtain a signal information mapping table, wherein the signal information mapping table includes the identifier of the signal and the signal information; and The identifier is used as the primary key to select one or more signals.

3. The fault modeling method as described in claim 2, further comprising establishing the signal information mapping table, wherein establishing the signal information mapping table includes: Convert the interface file into an object structure; as well as The object structure is recursively processed to store the obtained information in the signal information mapping table.

4. The fault modeling method of claim 2, wherein, The identifier is a globally unique identifier.

5. The fault modeling method of claim 1, wherein, Based on the underlying fault logic unit and one or more logical operators, fault combination logic including zero-level, one-level, or multi-level nested logic is constructed. The fault combination logic can also be modified based on the fault logic interactive interface.

6. The fault modeling method of claim 5, wherein the fault logic interaction interface comprises: The system includes a signal information operation area, a logic operation area, and a nested operation area. Modifying the fault combination logic based on the fault logic interaction interface includes one or more of the following, or any combination thereof: The fault logic unit is modified by performing operations in the signal information operation area; The logical operators are modified by performing operations in the logical operation area; as well as The nesting of the fault combination logic can be modified by performing operations in the nested operation area.

7. The fault modeling method as described in claim 6 further includes: Whenever the fault combination logic is modified based on the fault logic interaction interface, that is, a modified fault combination logic expression is generated based on the fault combination logic that needs to be modified.

8. A fault logic interactive interface for fault modeling, comprising: The signal information operation area, the logic operation area, and the nested operation area, among which, The operation performed in the signal information operation area corresponds to modifying the fault logic unit; Performing an operation in the logical operation area corresponds to modifying the logical operator; and Performing operations in the nested operation area corresponds to modifying the nested fault combination logic, wherein The fault combination logic is constructed based on underlying fault logic units and one or more logical operators, and includes zero-level, one-level, or multi-level nesting; and wherein The underlying fault logic unit determines one or more signals corresponding to one or more airborne interface data related to the fault to construct the logic.

9. An apparatus for fault modeling, comprising: A module used to determine one or more signals corresponding to one or more airborne interface data related to a fault; A module for constructing one or more corresponding underlying fault logic units based on the one or more signals; A module for constructing fault combination logic including zero-level, one-level, or multi-level nested logic based on the underlying fault logic unit and one or more logic operators; A module for generating fault combination logic expressions based on the constructed fault combination logic; as well as A module for generating at least one of the corresponding Extensible Markup Language (Extensible Markup Language) file and binary file based on the generated fault combinational logic expression.

10. A process-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions, when executed by one or more processors, control the one or more processors to perform the following operations: Identify one or more signals corresponding to one or more airborne interface data related to the fault; One or more corresponding underlying fault logic units are constructed based on the one or more signals; Based on the underlying fault logic unit and one or more logic operators, construct fault combination logic including zero-level, one-level, or multi-level nested logic; Based on the constructed fault combination logic, generate fault combination logic expressions; as well as At least one of the corresponding Extensible Markup Language (Extreme Markup Language) file and binary file is generated based on the generated fault combinational logic expression.

Images