An aircraft message generation method, apparatus, device, medium and program product

Abstract

This application discloses a method, apparatus, device, medium, and program product for generating aircraft messages, relating to the field of aviation technology. The method includes: collecting flight data for a target flight segment of the aircraft, the flight data being data from the aircraft's WQAR decoding system; determining a message triggering event corresponding to a preset triggering condition, the message triggering event including the type of the target message; determining target parameters corresponding to the target message based on a preset mapping table and the flight data, the mapping table representing the correspondence between the target message and the target parameters; and generating a target message according to a preset message format using the target parameters. This method enables the generation of standardized engine messages from unstructured WQAR data, effectively compensating for data gaps caused by potential interruptions in the ACARS link and ensuring the continuity and timeliness of engine monitoring.

Description

Technical Field

[0001] This application relates to the field of aviation technology, and in particular to a method, apparatus, device, medium, and program product for generating aircraft messages. Background Technology

[0002] In the civil aviation sector, real-time engine health monitoring is crucial for flight safety and maintenance. Currently, parameters for determining engine operating status primarily rely on the Aircraft Communications Addressing and Reporting System (ACARS) for transmission. While ACARS technology is widely used and offers a degree of real-time capability, it suffers from the following shortcomings in complex real-world operating environments.

[0003] First, its transmission stability is susceptible to disruptions caused by remote airspace, severe weather, or blind spots in ground base station coverage, leading to transmission interruptions and data loss. Second, ACARS channel capacity is limited; during critical phases such as takeoff and landing, when multiple aircraft systems transmit large amounts of data concurrently, channel congestion can easily occur, causing data delays or data loss. Third, the technology has a long transmission chain, relying on the coordination of multiple hardware components, including airborne terminals, communication modules, and ground base stations; a failure in any link can cause the entire transmission to be interrupted. These limitations make ACARS-based engine monitoring data streams susceptible to "breakpoints," affecting the integrity and timeliness of data analysis in the monitoring system.

[0004] Therefore, the existing technical solutions suffer from incomplete and discontinuous engine monitoring data due to the unreliability of ACARS transmission. The industry urgently needs a new method for generating aircraft messages to ensure that the monitoring system receives a complete and continuous stream of monitoring data. Summary of the Invention

[0005] This application provides a method, apparatus, device, medium, and program product for generating aircraft messages to solve the problem in related technologies that unreliable ACARS transmission may lead to incomplete and discontinuous engine monitoring data.

[0006] In a first aspect, this application provides a method for generating aircraft messages, the method comprising: The flight data for the target flight segment of the aircraft is collected. The flight data is from the aircraft's WQAR decoding system.

[0007] Based on the preset triggering conditions, determine the message triggering event corresponding to the triggering conditions. The message triggering event includes the type of the target message.

[0008] Based on a pre-defined mapping table and flight data, the target parameters corresponding to the target message are determined. The mapping table represents the correspondence between the target message and the target parameters.

[0009] Generate a target message according to the preset message format using the target parameters.

[0010] This method uses the aircraft's WQAR decoding system as the data source, whose data features high sampling rate and high fidelity, providing the original basis for message generation. The message type is determined based on preset trigger conditions to ensure that the logic of the generated message is consistent with the onboard native system, accurately reflecting the key operating stages or abnormal events of the engine. Target parameters are located from flight data through a preset mapping table, enabling the extraction of parameters required for specific messages from general monitoring data, which helps ensure the accuracy and standardization of data extraction. Generating target messages according to a preset message format ensures that the output message structure is consistent with the native ACARS message, allowing it to be received and parsed by the ground health monitoring system. This method realizes the generation of standardized engine messages from unstructured WQAR data, effectively compensating for data gaps caused by potential ACARS link interruptions, and ensuring the continuity and timeliness of engine monitoring.

[0011] In one possible design approach of the first aspect, the method further includes: Before determining the type of target message corresponding to the preset triggering conditions, a parameter union is generated based on flight data and multiple preset mapping tables. The parameter union includes multiple parameters, and each mapping table corresponds to a type of target message.

[0012] This method extracts the complete set of parameters required for all target message types at once based on multiple mapping tables, avoiding the need to scan and process massive amounts of raw flight data separately and repeatedly for each message type. This not only reduces overall data I / O overhead and computational load but also enables the system to comprehensively consider all possible message generation requirements when processing data for the same flight segment. This provides a foundation for efficient multi-message parallel processing, thereby improving the processing speed and resource utilization efficiency of the entire message reconstruction system.

[0013] In one possible design approach of the first aspect, the method further includes: After generating a parameter union based on flight data and multiple preset mapping tables, it is determined whether the parameter union contains the parameters required for all types of target messages. If yes, the data in the parameter union is preprocessed; otherwise, no target message is generated.

[0014] This method determines whether the union of parameters meets the requirements of all target messages before allocating computational resources for data preprocessing, serving as an early fault screening mechanism. If the data source (WQAR decoded file) itself has missing or incomplete parameters, the system can terminate the subsequent processing of that invalid data in advance. This avoids unnecessary preprocessing and scanning calculations, thus saving computational resources and providing timely and clear feedback on processing failures. It ensures that only data with complete data proceeds to subsequent processing stages, improving the reliability of the entire process and the rationality of resource utilization.

[0015] In one possible design approach of the first aspect, the preprocessing steps for the data in the parameter union include: Data cleaning, time alignment, unit conversion, and format standardization are performed at least once to save the preprocessed parameters as an intermediate data file.

[0016] This method specifies the content and output format of preprocessing, and transforms the raw data, which may have various quality problems, into a standardized intermediate data file through preprocessing.

[0017] In one possible design approach of the first aspect, the method further includes: A single time-series scan is performed on the parameter union. Then, based on preset trigger conditions, all message trigger events during the target flight segment are identified, and a trigger event list is generated. According to the trigger event list, the target parameters corresponding to each target message are extracted from the parameter union, and messages corresponding to the type of each target message are generated in batches.

[0018] This method identifies all message triggering events within a flight segment in a single time sequence by performing a single time-series scan of the parameter union and simultaneously evaluating all triggering conditions, generating a triggering event list. This avoids wasting resources by scanning data separately for each message type, improving the efficiency of event identification and ensuring global consistency in the event time sequence. By generating messages in batches based on the event list, the system can extract and encapsulate parameters from intermediate data files as needed. The generation tasks for each message are independent, enabling rapid reconstruction of large-scale, multi-message operations and improving system processing efficiency.

[0019] In one possible design approach of the first aspect, the method further includes: After generating the target message according to the preset message format using the target parameters; The generated target message is sent to a preset receiving end via at least one preset communication protocol.

[0020] This method achieves a fully automated closed-loop process from message generation to message application. No manual intervention is required, ensuring timely and reliable message transmission to downstream systems. This compensates for data flow gaps caused by ACARS interruptions, guaranteeing the continuity and effectiveness of monitoring.

[0021] In one possible design of the first aspect, the communication protocol includes at least one of a secure file transfer protocol and an email protocol.

[0022] Secondly, this application provides an apparatus for generating aircraft messages, the apparatus comprising: The data acquisition module is used to collect flight data of the aircraft's target flight segment. The flight data is data from the aircraft's WQAR decoding system.

[0023] The event triggering module is used to determine the message triggering event corresponding to the preset triggering conditions. The message triggering event includes the type of the target message.

[0024] The parameter determination module is used to determine the target parameters corresponding to the target message based on a preset mapping table and flight data. The mapping table represents the correspondence between the target message and the target parameters.

[0025] The message generation module is used to generate target messages from target parameters according to a preset message format.

[0026] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps: The flight data for the target flight segment of the aircraft is collected. The flight data is from the aircraft's WQAR decoding system.

[0027] Based on the preset triggering conditions, determine the message triggering event corresponding to the triggering conditions. The message triggering event includes the type of the target message.

[0028] Based on a pre-defined mapping table and flight data, the target parameters corresponding to the target message are determined. The mapping table represents the correspondence between the target message and the target parameters.

[0029] Generate a target message according to the preset message format using the target parameters.

[0030] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps: The flight data for the target flight segment of the aircraft is collected. The flight data is from the aircraft's WQAR decoding system.

[0031] Based on the preset triggering conditions, determine the message triggering event corresponding to the triggering conditions. The message triggering event includes the type of the target message.

[0032] Based on a pre-defined mapping table and flight data, the target parameters corresponding to the target message are determined. The mapping table represents the correspondence between the target message and the target parameters.

[0033] Generate a target message according to the preset message format using the target parameters.

[0034] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps: The flight data for the target flight segment of the aircraft is collected. The flight data is from the aircraft's WQAR decoding system.

[0035] Based on the preset triggering conditions, determine the message triggering event corresponding to the triggering conditions. The message triggering event includes the type of the target message.

[0036] Based on a pre-defined mapping table and flight data, the target parameters corresponding to the target message are determined. The mapping table represents the correspondence between the target message and the target parameters.

[0037] Generate a target message according to the preset message format using the target parameters.

[0038] It is understood that the beneficial effects achieved by the aircraft message generation apparatus provided in the second aspect, the computer equipment provided in the third aspect, the computer-readable storage medium provided in the fourth aspect, and the computer program product provided in the fifth aspect can be referred to as the beneficial effects in the first aspect and any possible implementation thereof, and will not be repeated here. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying 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.

[0040] Figure 1 A flowchart illustrating a method for generating aircraft messages provided in an embodiment of this application; Figure 2 A flowchart illustrating another method for generating aircraft messages provided in this application embodiment; Figure 3 A flowchart illustrating another method for generating aircraft messages provided in this application embodiment; Figure 4A schematic diagram of the structure of an aircraft message generation device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0041] To facilitate understanding of this application, a more complete description will be provided below with reference to the accompanying drawings, which illustrate embodiments of the present application. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided so that the disclosure of this application will be thorough and complete.

[0042] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0043] It should be understood that the terminology used in the description of the various examples herein is for the purpose of describing the particular examples only and is not intended to be limiting. As used in the description of the various examples, the singular forms “a” (“a”, “an”) and “the” are intended to include the plural forms as well, unless the context explicitly indicates otherwise.

[0044] It should also be understood that the term “comprising” (also referred to as “includes”, “including”, “comprises” and / or “comprising”) as used in this specification specifies the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0045] It should be understood that the terms "an embodiment," "another embodiment," and "a possible design" used throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment or implementation is included in at least one embodiment of this application. Therefore, phrases such as "in one embodiment of this application," "in another embodiment of this application," and "a possible design" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0046] In the civil aviation field, real-time and continuous monitoring of aircraft engine operating status is a crucial aspect of ensuring flight safety and implementing predictive maintenance and performance optimization. The relevant parameters for determining engine operating status are primarily transmitted via the Aircraft Communications Addressing and Reporting System (ACARS). Engine ACARS real-time messages, serving as the key data carrier for onboard systems, contain key parameters such as low-pressure rotor speed (N1), high-pressure rotor speed (N2), exhaust gas temperature (EGT), and fuel flow rate (FF). This data, in a standardized format, is transmitted to the ground health monitoring system via an air-to-ground data link, providing engineers with a basis for condition assessment, fault warning, and trend analysis.

[0047] Currently, engine message transmission heavily relies on the traditional ACARS technology link. While this technology is widely used in global fleets and possesses a certain degree of real-time capability, it reveals significant shortcomings in complex operational environments: First, its transmission stability is susceptible to remote airspace, severe weather, or ground base station coverage blind spots, leading to critical data link interruptions and message loss. Second, ACARS channel capacity is limited; during critical phases such as takeoff and landing, when multiple aircraft systems transmit large amounts of data concurrently, channel congestion can easily occur, causing message delays or loss. Third, the technology chain is long, relying on the coordination of multiple hardware components, including airborne terminals, communication modules, and ground base stations; a failure in any link can cause the entire transmission to be interrupted. These limitations create a "breakpoint" risk in ACARS-based engine monitoring data streams, potentially affecting the integrity and timeliness of ground system data analysis.

[0048] In summary, existing technical solutions cannot effectively solve the problem of incomplete and discontinuous engine monitoring data caused by unreliable ACARS transmission. Providing a new method for generating aircraft messages to ensure that the ground health monitoring system obtains a complete and continuous monitoring data stream, thereby safeguarding aircraft flight safety, has become an urgent technical problem to be solved in this field.

[0049] To address the aforementioned issues, this application proposes a method for generating aircraft messages. This method generates engine messages based on WQAR data, using the same format and triggering logic as the original airborne messages. This compensates for data gaps caused by potential interruptions in the ACARS link, ensuring the timeliness and continuity of engine monitoring.

[0050] refer to Figure 1 , Figure 1 This is a flowchart illustrating a method for generating aircraft messages according to an embodiment of this application. Figure 1 As shown, the method includes the following steps: S101 collects flight data for the target flight segment of the aircraft. The flight data is from the aircraft's WQAR decoding system.

[0051] In this embodiment, the Wireless Quick Access Recorder (WQAR), as an airborne data recording device, can record a large number of flight parameters at a high frequency throughout almost the entire flight. After the flight, the data is rapidly transmitted to a ground health monitoring system via a wireless network. The data in the WQAR is typically used for post-flight engineering analysis and troubleshooting. Flight data refers to the decoded data files obtained from the aircraft's WQAR decoding system. To acquire flight data, a standardized data interface connected to the WQAR decoding system can be established to automatically acquire the decoded data files for the target flight segment. For example, changes in the decoded database file can be monitored to trigger an automatic data acquisition process, replacing the traditional manual reading method, thereby improving the efficiency and timeliness of data acquisition and facilitating subsequent real-time or near-real-time data processing.

[0052] S102, based on the preset triggering conditions, determine the message triggering event corresponding to the triggering conditions, the message triggering event including the type of the target message.

[0053] After acquiring flight data, the system determines the corresponding message trigger event based on preset trigger conditions. This event includes the type of target message to be generated. The preset trigger conditions can be set according to the logic of the airborne engine control system generating ACARS messages. For example, for an engine start message, the trigger condition can be set to the engine high-pressure rotor speed (N2) exceeding a certain threshold (e.g., 20%), or a specific engine start switch status position changing. The system continuously monitors key parameters in the flight data, and when a trigger condition is met, it determines that a corresponding message trigger event has occurred. Each message trigger event is associated with a specific target message type. The following is an illustration using a specific example: Taking an engine start message as an example, the preset triggering condition can be set as follows: when the high-pressure rotor speed (N2) of a certain engine continuously rises from below a low threshold (e.g., 5%) and exceeds a preset start-up judgment threshold (e.g., 20%) for the first time, the system continuously tracks the N2 speed parameters of the left and right engines while processing the WQAR decoded data stream in real time. When the N2 value sequence of the left engine meets the above condition (e.g., rising from 3% to 25%), the system determines that the "left engine start" message triggering event has occurred. The target message type associated with this event is "left engine start message". Similarly, if the right engine N2 meets the condition, the "right engine start" message triggering event is triggered, and the target message type associated with this event is "right engine start message".

[0054] Taking a takeoff message as an example, the triggering condition for a takeoff message might be based on a combination of multiple parameters. For instance, a preset condition could be defined as follows: when the aircraft's air-to-ground signal (or landing gear status) is "airborne," and the indicated airspeed (IAS) is consistently greater than 80 knots, while the engine thrust mode is in takeoff rated power mode (as indicated by EEC parameters). The system analyzes these conditions in parallel when analyzing flight segment data. When the data at a certain point in time simultaneously meets all three conditions, the system determines that a "takeoff" event has occurred. The target message type corresponding to this event is a "takeoff message." This composite triggering condition ensures that the message is only generated during the actual takeoff phase, avoiding accidental triggering during other phases such as high-speed taxiing.

[0055] Taking the target message type corresponding to the message triggering event as an engine over-limit alarm message as an example, for abnormal situations requiring immediate alarm, the triggering condition can be set to threshold monitoring of key safety parameters. For example, for engine exhaust temperature (EGT), the preset condition can be set as follows: when the EGT value exceeds the redline threshold specified for its model and remains there for a very short period of time (e.g., 2 seconds) to filter out transient spikes. When the system detects that the engine EGT parameter value continuously exceeds this redline threshold, it will trigger an "engine EGT over-limit" event. The target message type associated with this event is "engine over-limit alarm," which can contain key information such as the specific over-limit parameter (EGT), the over-limit value, and the time of occurrence, so that the ground health monitoring system can be aware of and handle it immediately.

[0056] Taking a steady-state cruise message as an example, the triggering condition can be set as follows: when the aircraft altitude is above the transition altitude layer (e.g., FL100), the absolute value of the vertical speed is less than a certain threshold (e.g., 500 feet / minute), the airspeed change is gradual, and this state has lasted for a predetermined period of time (e.g., 5 minutes). When the system determines that the flight data meets these characteristics of stable cruise, it triggers the "steady-state cruise" event and generates the corresponding "steady-state cruise message".

[0057] In this embodiment, by incorporating matching rules between the aforementioned triggering conditions and message types, the system can identify corresponding event points from continuous flight data streams, just like an airborne system, and drive the generation process of corresponding message types. This ensures that the generated messages are consistent with native ACARS messages not only in content format but also in generation logic and timing, thus making the data stream received by the ground system continuous in terms of business logic.

[0058] S103, based on a preset mapping table and flight data, determines the target parameters corresponding to the target message. The mapping table represents the correspondence between the target message and the target parameters.

[0059] In this embodiment, the target parameters corresponding to the target message are determined based on a preset mapping table and the aforementioned flight data. The mapping table is pre-constructed according to the aircraft engine ACARS message specification, and it represents the correspondence between different message types (such as left / right engine start message, takeoff message, cruise message, etc.) and the set of parameters they must contain. This mapping table covers the set of all parameters required for the target message type. After determining the target message type, the system uses the mapping table to filter out all the parameters necessary to reconstruct this type of message from a large amount of WQAR decoded flight data, such as low-pressure rotor speed N1, high-pressure rotor speed N2, exhaust temperature EGT, fuel flow rate FF, etc. The set of these filtered parameters is the target parameter.

[0060] During or after the screening process, the target parameters can be cleaned and preprocessed. This includes handling null values, standardizing timestamps, converting units, and standardizing numerical formats to eliminate noise and inconsistencies in the original data, generating a clean, well-organized subset containing only the required parameters. This step efficiently and accurately extracts relevant information from the massive WQAR data, filtering out irrelevant data. This not only improves subsequent processing efficiency but, more importantly, ensures that the data used for reconstruction meets the requirements for generating the corresponding target message in terms of content and quality.

[0061] S104, Generate a target message by setting the target parameters according to the preset message format.

[0062] The preset message format can follow the specifications of the airborne native ACARS engine message, including the order of parameters in the message, the character length of each parameter, and the representation format of values ​​(such as decimal places and padding methods). The system combines the preprocessed target parameter values ​​in the specified order and converts each parameter value (such as truncating and padding with zeros) into a string pattern that meets its length requirements, finally encapsulating it into a complete, formatted data block, i.e., the target message. The target message generated in this way is highly consistent with the native message directly generated by the airborne system and sent through the ACARS link in terms of data content composition and external presentation. Therefore, the generated reconstructed message can be directly received, parsed, and processed by the existing ground health monitoring system without the need to modify the ground system.

[0063] This application embodiment automatically acquires data from the WQAR system, simulates airborne logic to trigger message events, extracts parameters based on a mapping table, and strictly encapsulates messages according to standard formats, forming a complete target message generation process. This enables the use of WQAR data to supplement or back up ACARS messages. When the ACARS link is interrupted due to signal, congestion, or hardware problems, this method can quickly generate engine messages with equivalent format and logic based on WQAR data and automatically output them to the ground health monitoring system. This effectively fills the gap in the monitoring data stream, ensuring the data integrity of the ground health monitoring system for continuous and timely monitoring and analysis of engine status, and improving the safety and reliability of aircraft operation support.

[0064] In one embodiment of this application, reference is made to Figure 2 , Figure 2 This is a flowchart illustrating another method for generating aircraft messages provided in an embodiment of this application. Figure 2 As shown, before determining the type of the target message corresponding to the preset triggering condition, the method further includes: S201 generates a parameter union based on flight data and multiple pre-set mapping tables. This parameter union includes multiple parameters, with each mapping table corresponding to a specific type of target message.

[0065] In this embodiment, multiple mapping tables are pre-configured to correspond to various types of target messages. For example, the target message types related to the engine may include: left engine start message, right engine start message, takeoff message, climb message, steady-state cruise message, and engine over-limit warning message, etc. Each message is intended to reflect the state of the engine at different stages or under different events, therefore the focus of the parameters to be monitored is different.

[0066] Accordingly, the system will pre-build a corresponding mapping table for each target message type. For example, the mapping table for the left engine start message may mainly include parameters such as: left engine low-pressure rotor speed (N1), left engine high-pressure rotor speed (N2), left engine exhaust temperature (EGT), left engine fuel flow (FF), and engine start switch status. The mapping table for the takeoff message may include: N1, EGT, and FF for both the left and right engines, as well as parameters reflecting takeoff performance and environmental conditions such as indicated airspeed (IAS), pressure altitude, engine bleed air status, and total air temperature (TAT). The mapping table for the engine over-limit warning message may include: all parameters that need to be monitored for thresholds, such as EGT, N1, N2, lubricating oil temperature, lubricating oil pressure, and vibration value for both the left and right engines, as well as their respective over-limit flags or actual values.

[0067] After the system obtains the WQAR decoded data file for the target flight segment, it does not immediately proceed to the trigger condition judgment and message generation process. Instead, it first performs a parameter union generation operation. Specifically, the system reads all preset mapping tables (such as the mapping tables for the six message types mentioned above), merges and removes duplicates of all parameter identifiers listed in these tables, forming a parameter identifier set. This parameter identifier set includes all parameter identifiers required to generate any engine message that may be triggered. For example, it will simultaneously include parameter identifiers such as left engine N1, right engine N1, left engine N2, right engine N2, left engine EGT, right engine EGT, IAS, and altitude.

[0068] After generating the parameter identifier set, the system uses it to preprocess and filter the raw WQAR decoded data. For example, by traversing the parameter identifier set list, the system locates and extracts the data sequences corresponding to these parameters from the raw data file, while ignoring other parameters unrelated to the engine standard message. This process may be accompanied by necessary data cleaning, such as handling missing data values ​​and unifying the time base. Finally, the system generates a data-optimized parameter union, which contains the data that may be used in the generation of all subsequent message types.

[0069] In this embodiment, the required data is pre-filtered and extracted by generating a parameter union. Since WQAR records a large amount of data containing many parameters, but the engine standard message only uses a portion of this data, data filtering early in the message generation process reduces the amount of data that subsequent processing modules need to load and process, improving overall processing efficiency and providing a foundation for real-time or near-real-time data processing.

[0070] Furthermore, by comparing the union of parameters with the contents of the current WQAR data file, data missing issues can be detected in advance (e.g., a necessary parameter is not recorded in this flight segment). If the basic data is incomplete, the system can issue an early warning or take appropriate measures to prevent the triggering logic from misjudging or failing due to missing critical data.

[0071] Furthermore, by generating a parameter union, a standardized and accurate input is provided for subsequent trigger judgment and message generation modules. When the trigger condition is met and a specific type of message (such as the left engine start message) needs to be generated, the system does not need to traverse the original data (WQAR data file) again. Instead, it can directly extract the required parameter values ​​from the prepared, structured parameter union according to the corresponding mapping table, simplifying the logic and time consumption of real-time message encapsulation.

[0072] Therefore, this embodiment of the application, by generating a parameter union based on a mapping table, achieves the acquisition of data required to generate multiple types of messages with a single data read, making the entire message generation process clear in structure and making reasonable use of resources. When faced with continuous WQAR data streams, it can robustly and agilely respond to various triggering events, thereby reliably generating the required engine messages.

[0073] In one embodiment of this application, reference is made to Figure 3 , Figure 3 This is a flowchart illustrating another method for generating aircraft messages provided in an embodiment of this application. Figure 3 As shown, after generating the union of parameters based on flight data and multiple preset mapping tables, the method further includes: S301, determine whether the parameter set contains the parameters required for all types of target messages.

[0074] S302, if so, preprocess the data in the parameter union.

[0075] S303, if not, do not generate a target message.

[0076] In this embodiment, the system compares the generated parameter union (i.e., the set of parameters extracted from all mapping tables) with the standard requirements defined by the preset mapping tables to determine whether the WQAR data for the current flight segment completely contains all the parameters required to reconstruct all possible types of target messages. For example, the system checks whether the parameter union simultaneously contains every parameter listed as a required item in the mapping table, such as the left engine high-pressure rotor speed (N2), the right engine high-pressure rotor speed (N2), exhaust gas temperature (EGT), fuel flow rate (FF), and indicated airspeed (IAS).

[0077] Based on the judgment result, the system will take different paths: If the determination is yes, meaning all necessary parameters are confirmed to be complete, the system will preprocess the data in the parameter union. Preprocessing is a series of operations designed to improve data quality, making it more suitable for precise triggering judgments and message encapsulation. Since WQAR data originates from airborne sensors and systems, various quality issues may be introduced during acquisition, recording, or transmission; preprocessing is precisely to correct these problems. Specific preprocessing content may include, but is not limited to, the following aspects: data cleaning, time alignment, unit conversion, and format standardization.

[0078] If the determination is negative, meaning one or more required parameters are missing from the parameter union, it indicates that the original WQAR data for the current flight segment has inherent deficiencies and cannot meet the basic requirements for generating any compliant engine message. In this case, the system will decide not to generate the target message and may log or alert regarding the missing data. This mechanism effectively avoids invalid or erroneous calculations and encapsulation in the event of missing data, preventing the injection of engine messages generated based on incomplete data that could mislead ground engineers into the ground health monitoring system, thereby ensuring the credibility and value of the generated messages.

[0079] By performing the aforementioned preprocessing on the parameter union data, the original WQAR data is transformed into a clean, continuous, time-synchronized, and uniformly formatted dataset. This processing improves the accuracy of trigger condition judgment because smooth, continuous data more realistically reflects engine status changes, avoiding false or missed triggers due to data noise. It also provides a reliable data source for message encapsulation, ensuring that the values ​​entered into the message are verified and corrected, thereby guaranteeing the accuracy and consistency of the generated message content. Furthermore, by combining parameter completeness judgment with data preprocessing, a quality gating mechanism is formed. This allows for the interception of substandard data early in the message generation process. This improves the overall reliability and availability of the message products output by the entire method, enabling the ground health monitoring system to make more reliable analyses and decisions based on these messages, preventing safety impacts caused by potential ACARS data interruptions.

[0080] In one embodiment of this application, the data in the parameter union is preprocessed, wherein the preprocessing steps include at least one of data cleaning, time alignment, unit conversion and format standardization, and the preprocessed parameters are saved as an intermediate data file.

[0081] In this embodiment, after determining that the parameter union data is complete and deciding to perform preprocessing, the system executes a series of standardized data processing operations. These operations are collectively referred to as preprocessing, and their purpose is to transform the WQAR decoding parameters, which may contain various quality issues in the original data, into a dataset suitable for subsequent message reconstruction. The preprocessing process typically includes, but is not limited to, data cleaning, time alignment, unit conversion, and format standardization.

[0082] Data cleaning involves correcting obvious errors, invalid values, or noise in the data. For example, the system identifies and removes null values ​​or "N / A" markings, which may be caused by temporary sensor malfunctions or transmission interruptions. Values ​​significantly exceeding reasonable physical ranges (e.g., negative engine speeds or speeds exceeding 150% of rated values) are marked as abnormal and discarded. Furthermore, for transient spikes or glitches caused by electromagnetic interference, the system can apply digital filtering algorithms (such as moving average filtering and median filtering) to smooth the data. Identified invalid jump points are removed and filled with interpolated reasonable values, resulting in a smoother parameter curve that more accurately reflects the engine's actual operating state.

[0083] Time alignment is used to address data asynchrony issues caused by inconsistent sampling frequencies of different parameters. In a WQAR system, different parameters may have different recording periods; some parameters are recorded once per second (e.g., airspeed, altitude), while others may be recorded every four seconds or longer (e.g., certain temperature parameters). To use a complete snapshot of parameters at the same moment in subsequent triggering decisions and message encapsulation, the system needs to establish a unified high-resolution time base (e.g., one point per second). For parameter values ​​missing at the base time point, the system can use interpolation algorithms, such as linear interpolation or spline interpolation, to calculate an estimated value for that moment based on known values ​​at time points before and after the missing parameter. In this way, each unified timestamp corresponds to a complete and logically synchronized set of parameter values.

[0084] Unit conversion unifies parameter values ​​to the units of measurement required by the target message specification. Raw data may contain multiple unit systems; for example, temperature may be expressed in both Celsius and Fahrenheit, and pressure may be expressed in pounds, square inches (PSI), and hectopascals (hPa). The system converts all parameter values ​​to the standard units specified in the message specification (e.g., temperature to Celsius, pressure to hectopascals) according to predefined conversion rules, ensuring that the data in the final message has consistent dimensions, facilitating direct parsing and comparison by the ground system.

[0085] Format standardization involves regulating the numerical representation of parameter values. This includes standardizing numerical precision (decimal places), string length, and padding methods. For example, a message specification might require exhaust gas temperature (EGT) to be expressed in degrees Celsius, with a fixed format of 3 integers and 1 decimal place. The system rounds and formats the raw data to ensure that each parameter value conforms to its predefined field length and format requirements when entered into the message, avoiding message parsing errors due to inconsistent formats.

[0086] After completing one or more of the above preprocessing operations, the system saves the preprocessed and standardized data as a structured intermediate data file. This intermediate file can be stored in an efficient and easily readable format for subsequent programs (such as binary format, a text file with a specific structure, or database records). The file not only contains the numerical sequence of all necessary parameters on a unified timeline, but may also include information such as data quality indicators and processing logs.

[0087] This application embodiment preprocesses the data in the parameter union and saves the preprocessed data as an intermediate data file. The intermediate data file prevents the original data from being contaminated by accidental changes in memory or errors in subsequent steps. Furthermore, for data from the same flight segment, the intermediate data file can be directly read during the generation of different types of messages without repeating the preprocessing step. This avoids the time-consuming and resource-wasting process caused by repeated preprocessing, thereby improving the processing speed and responsiveness of the entire message generation system.

[0088] In one embodiment of this application, the method further includes: performing a single temporal scan on the parameter union, then identifying all message triggering events during the flight of the target segment based on preset triggering conditions, and generating a triggering event list. Based on the triggering event list, target parameters corresponding to each target message are extracted from the parameter union, and messages corresponding to the type of each target message are generated in batches.

[0089] In this embodiment, the system performs a single time-series scan of the parameter union (or preprocessed intermediate data file). Starting from the beginning time of the flight segment data, the system reads and analyzes the complete parameter dataset point-by-point (e.g., one data frame per second) in chronological order. During this process, the system simultaneously loads and runs all preset message trigger condition judgment logic. For example, the start-up trigger logic monitors engine speed (N2), the takeoff trigger logic comprehensively judges air-to-ground signals, airspeed, and thrust status, and the over-limit trigger logic continuously compares multiple parameters with their warning thresholds. The goal of this scan is to identify all message trigger events occurring during the target flight segment. Whenever any trigger condition is met—for example, detecting that the left engine N2 exceeds the start-up threshold at time T1, or detecting that the takeoff condition is met at time T2—the system records an event, including the event type, the precise timestamp of occurrence, and other relevant contextual information. After the scan, all these identified events are arranged chronologically to form a structured list of trigger events. This list fully describes the times and types of all engine messages that need to be generated during the flight.

[0090] When the system enters the batch message generation stage, it no longer needs to reread or scan the original data, but instead uses the already generated list of trigger events. For each event entry in the list, the system extracts all the target parameters required by the message specification for that type from the union of parameters (or intermediate data file) according to the target message type corresponding to that event.

[0091] Specifically, the system queries a preset mapping table corresponding to the message type to obtain the required parameter identifier list. Then, based on the timestamp of the event, it locates and reads the specific values ​​of these parameters at that specific moment from the parameter union or intermediate data file. For example, for a left engine start-up message event, the system extracts the values ​​of all parameters defined in the left engine start-up message mapping table at the event trigger time, such as left engine N1, N2, EGT, etc. Next, the system encapsulates the extracted parameter values ​​into a complete, standard-format message data block according to the format specifications of the airborne native message, including the parameter order, the bit length of each parameter, the data format (such as integer, floating-point, character), and necessary padding characters. The system iterates through the entire list of triggering events, performing parameter extraction and format encapsulation independently and in parallel for each event in the list, thereby generating all messages corresponding to the type of each target message in batches.

[0092] In this embodiment, a single-scan identification and batch on-demand generation mode is adopted, which greatly improves the processing efficiency for generating multiple types of engine messages. Scanning the target segment data independently for each message type would significantly increase computational costs. However, this method, through a single time-series scan, simultaneously evaluates all triggering conditions and detects all events at once, avoiding redundant I / O reads and parsing. The efficiency improvement is even more pronounced for long-segment or high-sampling-rate data.

[0093] Furthermore, since all judgments are based on the same time-aligned data and completed in a single traversal, the system can accurately maintain the global temporal order of events, avoiding timestamp discrepancies or event omissions that may result from multiple independent scans, thus ensuring the completeness and timing accuracy of event identification. After obtaining the complete event list, message encapsulation can be viewed as a series of independent tasks, providing the possibility for parallel computing and fully utilizing multi-core processor resources to accelerate message production. This mechanism for batch generating target messages optimizes the use of computing resources.

[0094] In this embodiment of the application, by separating the two processes of event identification and message generation and using an event list as a link for batch processing, this method optimizes the processing flow while ensuring the logical correctness and format accuracy of the generated messages. It can generate engine messages in batches based on WQAR data.

[0095] In one embodiment of this application, after generating a target message from the target parameters according to a preset message format, the method further includes: sending the generated target message to a preset receiving end through at least one preset communication protocol.

[0096] In this embodiment, the preset receiving end refers to a pre-configured data destination that needs to receive and use these engine messages. This typically refers to a ground-based Engine Health Management System (EHM), a fleet monitoring center's data server, or an engineering maintenance platform. To adapt to the technical environments and access requirements of different receiving ends, this method supports message transmission through at least one communication protocol. These protocols are standardized data transmission rules pre-configured in the system.

[0097] For example, a commonly used protocol is the SSH File Transfer Protocol (SFTP), a file transfer protocol based on the Secure Shell (SSH) protocol. The system can automatically upload one or more generated message files (which can be packaged by flight or time) to the SFTP server directory specified on the receiving end via an SFTP client. Another possible protocol supports automatic email forwarding; the system can attach message content as an attachment or embed message data in the email body and send it to a designated monitoring email address via the SMTP protocol, facilitating timely receipt and manual processing by engineers. Furthermore, depending on actual integration needs, other protocols such as HTTP / SAPI calls, message queues (such as MQTT, AMQP), or direct database writes can also be used.

[0098] When performing a send operation, the system can automatically invoke the corresponding protocol client or interface according to the preset configuration. For example, if configured for SFTP output, the system will initiate the transmission task immediately after the message is generated or as scheduled, establish a secure connection, and push the message file from the local storage path to the remote server. At the same time, the system usually records a transmission log, including the sending time, message identifier, destination address, and transmission status (success or failure), for tracking and auditing purposes.

[0099] In this embodiment, data is sent to a pre-defined receiving end via at least one pre-defined communication protocol, achieving automated data delivery and a closed-loop process. This fully automates the entire processing chain from WQAR data to usable messages, eliminating the need for manual intervention in file copying or transmission, thus improving operational efficiency and reducing the possibility of human error. Furthermore, this method supports multiple protocols, enhancing the system's adaptability and flexibility, enabling it to interface with different customers or systems, and reducing integration complexity. In addition, by sending messages with identical format and logic to the same receiving end as native ACARS messages, the ground health monitoring system can parse, store, analyze, and issue alarms for these reconstructed messages as if they were normal messages, thereby filling the data gap caused by ACARS link interruptions and ensuring the continuity and integrity of engine operating status monitoring.

[0100] In one embodiment of this application, the communication protocol includes at least one of a secure file transfer protocol and an email protocol.

[0101] In this embodiment, a secure file transfer protocol, such as SFTP (SSH File Transfer Protocol) based on SSH (Secure Shell), is a widely used protocol for enterprise-level data exchange. When SFTP is configured, the system acts as a client, establishing an encrypted connection with a pre-defined receiving SFTP server. This protocol encrypts data and authentication information during transmission, effectively preventing data from being eavesdropped on or tampered with, thus meeting the security requirements of aviation data. The transmitted content is typically a complete message file, which can be organized by flight number and date, facilitating batch and automated acquisition and processing by the receiving system.

[0102] Email protocols, typically referring to the Simple Mail Transfer Protocol (SMTP), combined with the Multipurpose Internet Mail Extensions (MIME) protocol, support the sending of attachments. When configured to use email protocols, the system can automatically send one or more generated target messages as email attachments, or fill the email body with a summary of key message content, to a preset monitoring email address. This approach provides greater flexibility and instant notification capabilities. Engineers or monitoring personnel can receive timely alerts when new messages are generated and can easily view or download attachments through email clients for preliminary analysis. It is suitable for scenarios requiring manual verification, alarm notifications, or data transmission in environments lacking complex system interfaces.

[0103] This method supports at least one of a secure file transfer protocol and an email protocol. On one hand, the secure file transfer protocol ensures the security, reliability, and automated integration capabilities of the data transmission process, enabling the efficient and secure injection of large numbers of messages into the backend analysis system. On the other hand, the email protocol provides a lightweight, easily deployable, and manually reachable backup or supplementary channel. These two protocols can be used individually or in combination depending on the importance of the messages or the recipient. For example, regular messages can be sent to the server via SFTP, while important alert messages can be sent to engineers separately via email. This flexible protocol support mechanism ensures that reconstructed messages can be reliably and promptly delivered to end users or downstream systems through the most suitable paths, thereby maximizing their value in filling data gaps and supporting decision-making.

[0104] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0105] Based on the same inventive concept, this application also provides an aircraft message generation apparatus for implementing the above-described aircraft message generation method. The solution provided by this apparatus is similar to the implementation described in the above-described method. Therefore, the specific limitations of one or more embodiments of an aircraft message generation apparatus provided below can be found in the limitations of the aircraft message generation method described above, and will not be repeated here.

[0106] In one embodiment of this application, reference is made to Figure 4 , Figure 4 This is a schematic diagram of an aircraft message generation apparatus provided in an embodiment of this application. Figure 4 As shown, this application provides an apparatus for generating aircraft messages, including: a data acquisition module 401, an event triggering module 402, a parameter determination module 403, and a message generation module 404, wherein: The data acquisition module 401 is used to acquire flight data of the aircraft's target flight segment. The flight data is the data from the aircraft's WQAR decoding system. The event triggering module 402 is used to determine the message triggering event corresponding to the preset triggering conditions, and the message triggering event includes the type of the target message; The parameter determination module 403 is used to determine the target parameters corresponding to the target message based on a preset mapping table and flight data. The mapping table represents the correspondence between the target message and the target parameters. The message generation module 404 is used to generate a target message from the target parameters according to a preset message format.

[0107] In one embodiment of this application, an aircraft message generation apparatus provided in this application further includes: The parameter union generation module is used to generate a parameter union based on flight data and multiple preset mapping tables. The parameter union includes multiple parameters, and each mapping table corresponds to a type of target message.

[0108] In one embodiment of this application, an aircraft message generation apparatus provided in this application further includes: The parameter determination module is used to determine whether the parameter union contains all the parameters required for all types of target messages. If yes, the data in the parameter union is preprocessed; otherwise, no target message is generated.

[0109] In one embodiment of this application, the parameter determination module in the aircraft message generation apparatus provided in this application includes: The data preprocessing module is used to preprocess the data in the parameter union by employing at least one of the following: data cleaning, time alignment, unit conversion, and format standardization, and save the preprocessed parameters as an intermediate data file.

[0110] In one embodiment of this application, an aircraft message generation apparatus provides a message generation module further configured to perform a single temporal scan of the parameter union, identify all message triggering events during the flight of the target segment based on preset triggering conditions, and generate a triggering event list. Based on the triggering event list, target parameters corresponding to each target message are extracted from the parameter union, and messages corresponding to the type of each target message are generated in batches.

[0111] In one embodiment of this application, an aircraft message generation apparatus provided in this application further includes: The message sending module is used to send the generated target message to the preset receiving end through at least one preset communication protocol.

[0112] The modules in the aforementioned aircraft message generation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0113] In one embodiment of this application, reference is made to Figure 5 , Figure 5 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application. Figure 5As shown, this application provides a computer device, which can be a server. The computer device includes a processor, memory, input / output interface (I / O), and communication interface. The processor, memory, and I / O interface are connected via a system bus, and the communication interface is connected to the system bus via the I / O interface. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores message data. The I / O interface of the computer device is used for exchanging information between the processor and external devices. The communication interface of the computer device is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a method for generating aircraft messages.

[0114] Those skilled in the art will understand that Figure 5 The structure shown is a block diagram of a partial structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0115] In one embodiment of this application, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0116] In one embodiment of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps in the above-described method embodiments.

[0117] In one embodiment of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0118] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program mentioned can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0119] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

[0120] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0121] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the scope of protection of this application includes the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of this application.

[0122] This document uses specific examples to illustrate the working principle and implementation of a method, apparatus, device, medium, and program product for generating aircraft messages according to this application. The description of the above embodiments is only for the purpose of helping to understand the specific settings and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0123] 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 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 method for generating aircraft messages, characterized in that, The method includes: Collect flight data of the aircraft's target flight segment, wherein the flight data is data from the aircraft's WQAR decoding system; Based on preset triggering conditions, determine the message triggering event corresponding to the triggering conditions, wherein the message triggering event includes the type of the target message; Based on a preset mapping table and the flight data, the target parameters corresponding to the target message are determined, and the mapping table represents the correspondence between the target message and the target parameters. The target parameters are used to generate the target message according to a preset message format.

2. The method according to claim 1, characterized in that, The method further includes: Before determining the type of target message corresponding to the preset triggering condition, a parameter union is generated based on the flight data and multiple preset mapping tables, wherein the parameter union includes multiple parameters, and each mapping table corresponds to a type of target message.

3. The method according to claim 2, characterized in that, The method further includes: After generating a parameter union based on the flight data and multiple preset mapping tables, it is determined whether the parameter union contains the parameters required for all types of target messages; if so, the data in the parameter union is preprocessed; if not, the target message is not generated.

4. The method according to claim 3, characterized in that, The step of preprocessing the data in the parameter union includes: At least one of the following: data cleaning, time alignment, unit conversion, and format standardization; Save the preprocessed parameters as an intermediate data file.

5. The method according to any one of claims 2 to 4, characterized in that, The method further includes: A single time-series scan is performed on the union of the parameters, and then, based on the preset triggering conditions, all the message triggering events during the flight of the target segment are identified, and a list of triggering events is generated. Based on the trigger event list, the target parameters corresponding to each target message are extracted from the parameters and set, and messages corresponding to the type of each target message are generated in batches.

6. The method according to claim 1, characterized in that, The method further includes: After generating the target message according to the target parameters in a preset message format, the generated target message is sent to a preset receiving end through at least one preset communication protocol.

7. The method according to claim 6, characterized in that, The communication protocol includes at least one of a secure file transfer protocol and an email protocol.

8. An apparatus for generating aircraft messages, characterized in that, The device includes: The data acquisition module is used to collect flight data of the aircraft's target flight segment, and the flight data is the data from the aircraft's WQAR decoding system; The event triggering module is used to determine the message triggering event corresponding to the preset triggering conditions, wherein the message triggering event includes the type of the target message; The parameter determination module is used to determine the target parameters corresponding to the target message based on a preset mapping table and the flight data, wherein the mapping table represents the correspondence between the target message and the target parameters; The message generation module is used to generate the target message from the target parameters according to a preset message format.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images