Fault monitoring method, system and equipment based on aircraft engine message and medium

Abstract

The invention relates to a fault monitoring method and system equipment based on an aircraft engine message and a medium, and the method comprises the steps: obtaining the aircraft engine message, extracting a message header identifier from the aircraft engine message, and determining a message analysis template according to the message header identifier; analyzing the aircraft engine message according to the message analysis template to obtain aircraft engine parameters and operation data thereof; and in response to a fault monitoring instruction for the aircraft engine parameters, monitoring operation data of the aircraft engine parameters based on a preset early warning condition, and when the early warning condition is met, issuing early warning information. According to the method provided by the invention, various types of aircraft engine messages can be identified and analyzed to obtain the operation data of each parameter of the engine, so that fault monitoring and early warning prompting are carried out on the engine.

Description

Technical Field

[0001] This invention relates to the field of flight data processing technology, and in particular to a fault monitoring method, system, device and medium based on aircraft engine messages. Background Technology

[0002] In the civil aviation sector, monitoring and data analysis of aircraft engines are crucial. Engines generate a large amount of critical parameter data during operation, which is transmitted via specific message formats to provide a basis for flight safety and maintenance decisions.

[0003] However, existing solutions for parsing aircraft engine messages have significant compatibility limitations. They are prone to parsing errors or data loss when dealing with different aircraft models and data transmission standards. Some existing parsing systems only support specific ARINC protocol versions, making them unsuitable for the data transmission formats of newer aircraft. Furthermore, after obtaining the aircraft engine operating parameter data, they cannot perform in-depth analysis of parameter change trends, hindering timely and accurate fault monitoring of the aircraft engine. Summary of the Invention

[0004] Based on this, the purpose of the present invention is to provide a fault monitoring method, system, device and medium based on aircraft engine messages. By parsing the engine messages to obtain real-time operating data and monitoring the engine parameter data, the abnormal conditions of the aircraft engine can be detected in a timely and accurate manner, and fault warnings can be issued.

[0005] Firstly, this application provides a fault monitoring method based on aircraft engine messages, including:

[0006] Obtain aircraft engine messages;

[0007] Extract the message header identifier from the aircraft engine message, and determine the message parsing template based on the message header identifier;

[0008] The aircraft engine message is parsed according to the message parsing template to obtain the aircraft engine parameters and its operating data;

[0009] In response to a fault monitoring command for the aircraft engine parameters, the system monitors the operating data of the aircraft engine parameters based on preset warning conditions, and issues a warning message when the warning conditions are met.

[0010] Secondly, this application provides a fault monitoring system based on aircraft engine messages, including:

[0011] The message acquisition module is used to acquire aircraft engine messages;

[0012] The template matching module is used to extract the message header identifier from the aircraft engine message and determine the message parsing template based on the message header identifier.

[0013] The message parsing module is used to parse the aircraft engine message according to the message parsing template to obtain the aircraft engine parameters and its operating data;

[0014] The fault monitoring module is used to respond to fault monitoring commands for the aircraft engine parameters, monitor the operating data of the aircraft engine parameters based on preset warning conditions, and issue warning information when the warning conditions are met.

[0015] Thirdly, this application provides a computer device including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the fault monitoring method based on aircraft engine messages as described in any of the preceding claims.

[0016] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the fault monitoring method based on aircraft engine messages as described in any of the preceding claims.

[0017] This application provides a fault monitoring method, system, device, and storage medium based on aircraft engine messages. The method acquires aircraft engine messages, identifies the corresponding message parsing template based on the message header identifier, parses the aircraft engine messages according to the parsing template to obtain various parameters and corresponding operating data of the aircraft engine, monitors the aircraft engine operating data according to received fault monitoring instructions, and determines whether early warning conditions are met. When the operating data meets the early warning conditions, an early warning message is issued to relevant personnel, providing early warning and response to abnormal engine conditions. The method provided in this application, by matching the corresponding message parsing template to the engine model, is applicable to various aircraft models and engine types. It performs real-time monitoring and fault prediction of the engine based on preset early warning conditions, thereby meeting the requirements for real-time, accurate, and reliable monitoring of aircraft engines and ensuring stable aircraft operation. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art 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.

[0019] Figure 1 A flowchart illustrating the steps of a fault monitoring method based on aircraft engine messages provided in Embodiment 1 of this application;

[0020] Figure 2 This is a flowchart illustrating the steps for acquiring aircraft engine operating data, provided in Embodiment 1 of this application.

[0021] Figure 3 This application provides a flowchart of steps for generating a visual chart in Embodiment 1.

[0022] Figure 4 This is a schematic diagram of the structure of a fault monitoring system based on aircraft engine messages, provided in Embodiment 2 of this application.

[0023] Figure 5 This is a schematic diagram of the structure of a computer device provided in Embodiment 3 of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the protection scope of this application.

[0025] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0026] In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims. In the description of this application, it should be understood that the terms "first," "second," "third," etc., are used only to distinguish similar objects and are not necessarily used to describe a specific order or sequence, nor should they be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0027] Furthermore, in the description of this application, unless otherwise stated, "multiple" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0028] Example 1

[0029] Please see Figure 1 , Figure 1 A flowchart illustrating the steps of the fault monitoring method based on aircraft engine messages provided in Embodiment 1 of this application. The fault monitoring method based on aircraft engine messages provided in this embodiment includes:

[0030] S101, Obtain aircraft engine message;

[0031] S102, extract the message header identifier from the aircraft engine message, and determine the message parsing template based on the message header identifier;

[0032] S103, parse the aircraft engine message according to the message parsing template to obtain the aircraft engine parameters and its operating data;

[0033] S104, in response to the fault monitoring command for the aircraft engine parameters, monitors the operating data of the aircraft engine parameters based on preset warning conditions, and issues a warning message when the warning conditions are met.

[0034] This application provides a fault monitoring method, system, device, and storage medium based on aircraft engine messages. The method acquires aircraft engine messages, identifies the corresponding message parsing template based on the message header identifier, parses the aircraft engine messages according to the parsing template to obtain various parameters and corresponding operating data of the aircraft engine, monitors the aircraft engine operating data according to received fault monitoring instructions, and determines whether early warning conditions are met. When the operating data meets the early warning conditions, an early warning message is issued to relevant personnel, providing early warning and response to abnormal engine conditions. The method provided in this application, by matching the corresponding message parsing template to the engine model, is applicable to various aircraft models and engine types. It performs real-time monitoring and fault prediction of the engine based on preset early warning conditions, thereby meeting the requirements for real-time, accurate, and reliable monitoring of aircraft engines and ensuring stable aircraft operation.

[0035] For step S101, obtain the aircraft engine message.

[0036] The Aircraft Communications Addressing and Reporting System (ACARS) is a digital data link system that transmits short messages (messages) between aircraft and ground stations via radio or satellite. The aircraft engine message is an ACARS message, and the system sends and receives aircraft engine messages in real time.

[0037] For civil airliners, each aircraft is equipped with multiple engines, the number of which varies depending on the size and purpose of the aircraft. Medium-sized airliners generally employ a twin-engine design, while large wide-body airliners typically have four engines. Aircraft engines are supplied by multiple manufacturers, corresponding to different engine models and, consequently, different engine message formats.

[0038] For step S102, extract the message header identifier from the aircraft engine message, and determine the message parsing template based on the message header identifier.

[0039] The message header identifier includes the aircraft model information and the aircraft engine message type.

[0040] Taking the A330 aircraft as an example, the aircraft engine messages include A330 ENGINE CRUISE REPORT, A330 ENGINE TAKE OFF REPORT, A330 ENGINE GAS PATH ADVISORY REPORT, A330 ENGINE MECHANICAL ADVISORY REPORT, A330 ENGINE TRIM BALANCE ADV REPORT, A330 ENGINE START REPORT, and A330 ENGINE START SUMMARY REPORT. By obtaining the message header of the aircraft engine messages, the aircraft model information and the aircraft engine message type are extracted to determine the message parsing template.

[0041] In one embodiment, the aircraft engine message type is determined based on the aircraft model and the message purpose. Taking A330ENGINE CRUISE REPORT as an example, A330 is the aircraft model and ENGINE CRUISE REPORT is the message purpose. The combination of the two names forms a type of aircraft engine message.

[0042] Technicians pre-establish a message parsing model, which uses various types of aircraft engine messages as a training set to train the model, resulting in message parsing templates for parsing different types of messages.

[0043] Please see Figure 2 , Figure 2 This is a flowchart illustrating the steps for obtaining aircraft engine operating data according to Embodiment 1 of this application. In step S103, the aircraft engine message is parsed according to the message parsing template to obtain the aircraft engine parameters and its operating data. In one embodiment, step S103 includes:

[0044] S301, Identify the identifiers and delimiters in the engine message according to the message parsing template;

[0045] S302, determine the position information of each identifier and its corresponding data based on the identifier and the separator;

[0046] S303, the engine message is parsed according to a preset message parsing algorithm to obtain the aircraft engine parameters and its operating data.

[0047] In one embodiment, the identifier may include a message header identifier, a key field identifier, a checksum identifier, etc. The message header identifier is used to identify the message type, the key field identifier is used to identify the start position of the aircraft engine parameters, and the checksum identifier is used to check the integrity of the data. The delimiter is used to identify field boundaries. In this embodiment, the identifier and delimiter are used to identify the location information of the engine parameters and corresponding data in the message. After parsing, each engine parameter can be matched with its data, thereby accurately obtaining the operating data of each parameter.

[0048] In other embodiments, an anomalous data identifier may also be included to identify anomalous data.

[0049] By matching aircraft engine messages with message parsing templates, the corresponding message parsing templates are obtained. A message parsing algorithm is then used to convert the parameters in the messages, thereby extracting the data for each aircraft engine parameter. In one embodiment, parsing the aircraft engine messages includes data type conversion, decomposition of complex fields, and character offset correction. After parsing, the message data is converted into parameter data in a unified format. In this embodiment, a preset message parsing algorithm is used, taking into account the structural characteristics and encoding rules of aircraft engine messages, to decode and decompose the original message data layer by layer. By converting different types and formats of message data into unified format engine parameter data, technicians can quickly understand the engine's operating status and provide a reliable data foundation for subsequent engine fault monitoring and early warning.

[0050] For step S104, in response to the fault monitoring command for the aircraft engine parameters, the operating data of the aircraft engine parameters are monitored based on preset warning conditions, and when the warning conditions are met, a warning message is issued.

[0051] After obtaining the operating data corresponding to the aircraft engine parameters through the methods provided in the above embodiments, the engine parameter data is monitored to provide early warning of abnormal engine operating conditions.

[0052] In one embodiment, the method further includes:

[0053] Receive a warning setting instruction for aircraft engine parameters and set a warning threshold for the aircraft engine parameters; wherein the warning setting instruction includes the type of aircraft engine parameter and the corresponding warning threshold.

[0054] Warning conditions are set based on the warning thresholds of the aircraft parameters.

[0055] The types of aircraft engine parameters may include the engine speed, temperature, pressure and vibration values. According to the warning setting instructions, a warning threshold is set for each engine parameter. The warning threshold is used to identify abnormal engine operation.

[0056] Based on the actual operating requirements of the aircraft engine or the specific analytical purpose of the flight test, technicians send warning setting instructions to the system to set the warning thresholds corresponding to each aircraft engine parameter.

[0057] In one embodiment, a warning setting interface is displayed in the system. This interface includes an engine parameter type selection area and a warning threshold setting area. Technicians can select or input engine parameter types by clicking controls in the engine parameter type selection area, and then set the corresponding warning threshold in the warning threshold setting area. For example, if the selected engine parameter type is engine speed, the upper limit threshold, lower limit threshold, and rate of change threshold for the engine speed can be set according to actual operating conditions. The rate of change threshold reflects changes in engine speed; when the speed changes abruptly and the rate of change exceeds the rate of change threshold, it indicates an abnormal engine operation. The warning threshold setting area supports mixed input of warning threshold data, percentages, and units. In this embodiment, users set parameters such as upper and lower limits and rate of change thresholds to meet the need for accurate warnings of parameter anomalies under different engine operating conditions.

[0058] The warning conditions are set according to the warning threshold of the aircraft parameters. The warning conditions may include exceeding the warning threshold range. For example, it may be exceeding the upper or lower limit threshold range, or the rate of change is higher than and / or lower than the rate of change threshold. In this embodiment, the conditions can be set according to actual needs.

[0059] According to the inventive concept of this application, the warning setting instruction further includes warning logic rules, and the method further includes:

[0060] Based on the types of aircraft engine parameters and their corresponding warning thresholds, and in conjunction with warning logic rules, warning conditions are set.

[0061] Referring to the above embodiments, monitoring can be performed on a single type of engine parameter. Furthermore, early warning monitoring can also be performed by combining multiple types of engine parameters according to preset early warning logic rules.

[0062] The aforementioned early warning logic rules are pre-set by technicians based on the actual operating conditions of the aircraft engine. They can analyze the changing trends of engine parameters based on multiple types of engine parameters, perform combined analysis, meet the early warning needs for abnormal parameters under different operating conditions, and improve the accuracy of data monitoring and early warning prompts.

[0063] The warning logic rules support the combined use of various logical operators and functions. These logical operators may include "AND," "OR," etc., which, in conjunction with the warning logic rules, set warning conditions. For example, when the rate of change of engine temperature increases (i.e., a sudden temperature rise) and the pressure value exceeds a set upper limit threshold, the warning condition is determined to be met.

[0064] In one embodiment, flight segments can also be set, and warning thresholds and warning logic rules for each parameter in different flight segments can be set. The warning condition is met only when the warning logic rules are met in the preset flight segment, so as to avoid the situation where the parameters for normal aircraft operation are different in different flight segments, which may lead to false fault responses.

[0065] In this embodiment, warning thresholds for various engine parameters are set based on flight requirements, and warning conditions for triggering warning notifications are set by receiving pre-defined warning logic rules from technicians, thereby enhancing the practicality and flexibility of fault monitoring.

[0066] In one embodiment, the fault monitoring command includes target aircraft engine parameters, and step S104 includes:

[0067] In response to a fault monitoring command, the system acquires the operating data corresponding to the engine parameters of the target aircraft.

[0068] Obtain the warning threshold corresponding to the target aircraft engine parameters, compare the operating data of the target aircraft engine parameters with the warning threshold, and obtain the comparison result of the target aircraft engine parameters.

[0069] Warning information is generated based on the comparison results of the target engine parameter operating data and its corresponding warning threshold.

[0070] The target aircraft engine parameters are the types of aircraft engine parameters that technicians want to monitor.

[0071] Based on the target aircraft engine parameters, obtain its corresponding operating data and warning threshold, compare the operating data with the warning threshold, and generate warning information based on the comparison result.

[0072] In one embodiment, the warning information includes the type of aircraft engine parameters, operating data, warning thresholds, and the values ​​and / or percentages exceeding the thresholds. In other embodiments, several warning levels can be set based on the magnitude and / or percentage of the exceeded values; the greater the exceedance, the higher the warning level, thus providing a more intuitive warning.

[0073] In one embodiment, issuing a warning message when the warning condition is met includes:

[0074] The warning information is sent to the corresponding information receiving terminal according to at least one preset warning information release channel.

[0075] The warning information dissemination channels may include SMS, email, and system pop-ups. These channels are pre-set by technical personnel, with contact information pre-configured based on relevant personnel or on-duty staff to ensure timely delivery of warning information. For example, a warning notification interface may be displayed on the system, including areas for different dissemination channels. For email contact methods, this might include an email sending enable control, a contact person field, and an email template selection control. By enabling email notifications and selecting the appropriate email template based on the warning event, the warning information can be sent to the contact person.

[0076] In this embodiment, warning information is sent to relevant personnel through a preset warning information release channel in one or more ways, so that relevant personnel can respond to engine abnormalities in a timely manner and ensure flight safety.

[0077] Please see Figure 3 , Figure 3 A flowchart illustrating the steps for generating a visual chart is provided in Embodiment 1 of this application. According to the inventive concept of this application, the method further includes:

[0078] S1051, Using visualization tools, generate at least one visualization chart from the analyzed aircraft engine parameters and their operating data;

[0079] S1052, in response to a data analysis command for aircraft engine parameters, displays a visual graphical interface, on which the visual charts are displayed.

[0080] The visualization charts may include scatter plots, line graphs, bar charts, etc. The operation data corresponding to each type of aircraft engine is obtained by parsing the aircraft engine messages, and after data processing, the operation data is presented in the form of visualization charts using visualization tools.

[0081] In one embodiment, based on actual analysis needs, the operating data of the target engine parameter type is selected to generate a visualization chart.

[0082] In this embodiment, the changing trends of engine parameters, historical data comparisons, and correlations between parameters can be presented intuitively through visual charts. This not only helps technicians to quickly and accurately understand the engine's operating status, but also assists in engine fault diagnosis and performance evaluation. In addition, the types of parameters to be displayed, chart styles, interface layouts, and data update frequencies can be selected according to analysis needs, improving the system's interactive experience and usability.

[0083] The fault monitoring method based on aircraft engine messages provided in this application acquires aircraft engine messages, determines the corresponding message parsing template according to the message type, and applies a message parsing algorithm to extract the corresponding operating data of each parameter type of the aircraft engine, converts it into a unified parameter format, sets warning conditions through pre-set warning threshold data and warning logic rules for each parameter, monitors the engine's operating data, and identifies abnormal engine operating status when the engine operating data meets the warning conditions, notifying relevant personnel by issuing warning information. In addition, the data status of corresponding parameters can be queried through custom visualization charts to further monitor engine faults.

[0084] The method described in this application enables efficient parsing, accurate early warning, and intuitive visualization of engine messages, effectively improving the safety and maintenance efficiency of aero-engine operation and meeting the requirements of modern aviation industry for engine monitoring and data analysis.

[0085] Example 2

[0086] Secondly, please refer to 4. Figure 4 This is a schematic diagram of a fault monitoring system based on aircraft engine messages, provided in Embodiment 2 of this application.

[0087] The fault monitoring system based on aircraft engine messages provided in this application includes:

[0088] Message acquisition module 11 is used to acquire aircraft engine messages;

[0089] Template matching module 12 is used to extract the message header identifier from the aircraft engine message and determine the message parsing template based on the message header identifier;

[0090] Message parsing module 13 is used to parse the aircraft engine message according to the message parsing template to obtain aircraft engine parameters and its operating data;

[0091] The fault monitoring module 14 is used to respond to the fault monitoring command for the aircraft engine parameters, monitor the operating data of the aircraft engine parameters based on preset warning conditions, and issue a warning message when the warning conditions are met.

[0092] In one embodiment, the system further includes a warning threshold setting module, used to receive a warning setting instruction for aircraft engine parameters and set a warning threshold for the aircraft engine parameters; wherein the warning setting instruction includes the type of aircraft engine parameter and the corresponding warning threshold.

[0093] In one embodiment, the system further includes an early warning logic rule setting module, which is used to set the corresponding early warning logic rules according to the early warning setting instructions.

[0094] In one embodiment, the system further includes a warning information dissemination module, which is used to send warning information to the corresponding information receiving end according to at least one preset warning information dissemination channel.

[0095] In one embodiment, a visualization chart module is further included, which is used to generate at least one visualization chart based on the parsed aircraft engine parameters and their operating data according to a visualization tool, and to display a visualization graphical interface in response to a data analysis command for the aircraft engine parameters, and to display the visualization chart on the visualization graphical interface.

[0096] It should be noted that the fault monitoring system based on aircraft engine messages provided in the above embodiments is only illustrated by the division of the above functional modules when executing the fault monitoring method based on aircraft engine messages. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the equipment can be divided into different functional modules to complete all or part of the functions described above. The fault monitoring system based on aircraft engine messages provided in the above embodiments is used to execute the fault monitoring method based on aircraft engine messages described in the above embodiments. Its operation method and principle are the same as the fault monitoring method based on aircraft engine messages described above. That is, the fault monitoring system based on aircraft engine messages provided in the above embodiments and the fault monitoring method based on aircraft engine messages belong to the same concept. The implementation process is detailed in the above method embodiments and will not be repeated here.

[0097] Example 3

[0098] Thirdly, this embodiment provides a computer device. Please refer to [link / reference needed]. Figure 5 , Figure 5 This is a schematic diagram of the structure of a computer device provided in Embodiment 3 of this application. Figure 5 As shown, the computer device 21 includes: a processor 210, a memory 211, and a computer program 212 stored in the memory 211 and executable on the processor 210, such as a fault monitoring program based on aircraft engine messages; the processor 210 executes the computer program 212 to implement the methods described in the above embodiments.

[0099] The processor 210 may include one or more processing cores. The processor 210 connects to various parts within the computer device 21 using various interfaces and lines. It executes various functions of the computer device 21 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 211, and by accessing data in the memory 211. Optionally, the processor 210 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 210 may integrate one or more of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required to be displayed on the touch screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 210 and may be implemented as a separate chip.

[0100] The memory 211 may include random access memory (RAM) or read-only memory. Optionally, the memory 211 may include a non-transitory computer-readable storage medium. The memory 211 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 211 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch instructions), instructions for implementing the various method embodiments described above, etc.; the data storage area may store data involved in the various method embodiments described above, etc. Optionally, the memory 211 may also be at least one storage device located remotely from the aforementioned processor 210.

[0101] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0102] Example 4

[0103] Fourthly, embodiments of this application also provide a computer-readable storage medium that can store multiple instructions. These instructions are applicable to being loaded by a processor and executing the method steps of the above embodiments. For details of the execution process, please refer to the specific description of the above embodiments, which will not be repeated here.

[0104] The embodiments described above are merely examples of several implementations of the present invention, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention.

Claims

1. A fault monitoring method based on aircraft engine messages, characterized in that, include: Obtain aircraft engine messages; Extract the message header identifier from the aircraft engine message, and determine the message parsing template based on the message header identifier; The aircraft engine message is parsed according to the message parsing template to obtain the aircraft engine parameters and its operating data; In response to a fault monitoring command for the aircraft engine parameters, the system monitors the operating data of the aircraft engine parameters based on preset warning conditions, and issues a warning message when the warning conditions are met.

2. The fault monitoring method based on aircraft engine messages according to claim 1, characterized in that, The step of parsing the aircraft engine message according to the message parsing template to obtain the aircraft engine parameters and its operating data includes: Based on the message parsing template, identify the identifiers and delimiters in the engine message; Based on the identifier and the separator, determine the location information of each identifier and its corresponding data; The engine message is parsed according to a preset message parsing algorithm to obtain the aircraft engine parameters and its operating data.

3. The fault monitoring method based on aircraft engine messages according to claim 1, characterized in that, Also includes: Receive a warning setting instruction for aircraft engine parameters and set a warning threshold for the aircraft engine parameters; wherein the warning setting instruction includes the type of aircraft engine parameter and the corresponding warning threshold. Warning conditions are set based on the warning thresholds of the aircraft engine parameters.

4. The fault monitoring method based on aircraft engine messages according to claim 3, characterized in that, The warning setting instruction also includes warning logic rules. The step of receiving the warning setting instruction for aircraft engine parameters and setting the warning threshold for the aircraft engine parameters further includes: Based on the types of aircraft engine parameters and their corresponding warning thresholds, and in conjunction with warning logic rules, warning conditions are set.

5. The fault monitoring method based on aircraft engine messages according to claim 1, characterized in that, The fault monitoring command includes the target aircraft engine parameters; The step of monitoring the operating data of the aircraft engine parameters in response to a fault monitoring command for the aircraft engine parameters, based on preset early warning conditions, includes: In response to a fault monitoring command, the system acquires the operating data corresponding to the engine parameters of the target aircraft. Obtain the warning threshold corresponding to the target aircraft engine parameters, compare the operating data of the target aircraft engine parameters with the warning threshold, and obtain the comparison result of the target aircraft engine parameters. Warning information is generated based on the comparison results of the target engine parameter operating data and its corresponding warning threshold.

6. The fault monitoring method based on aircraft engine messages according to claim 1, characterized in that, When the warning conditions are met, issuing a warning message includes: The warning information is sent to the corresponding information receiving terminal according to at least one preset warning information release channel; wherein, the warning information release channel includes SMS, email and system pop-up window.

7. The fault monitoring method based on aircraft engine messages according to claim 1, characterized in that, Also includes: Using visualization tools, generate at least one visualization chart from the analyzed aircraft engine parameters and their operating data; In response to a data analysis command for aircraft engine parameters, a visual graphical interface is displayed, on which the visual charts are shown.

8. An aircraft engine message parsing system, characterized in that, include: The message acquisition module is used to acquire aircraft engine messages; The template matching module is used to extract the message header identifier from the aircraft engine message and determine the message parsing template based on the message header identifier. The message parsing module is used to parse the aircraft engine message according to the message parsing template to obtain the aircraft engine parameters and its operating data; The fault monitoring module is used to respond to fault monitoring commands for the aircraft engine parameters, monitor the operating data of the aircraft engine parameters based on preset warning conditions, and issue warning information when the warning conditions are met.

9. A computer device comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the fault monitoring method based on aircraft engine messages as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the fault monitoring method based on aircraft engine messages as described in any one of claims 1 to 7.

Images