Wake turbulence monitoring system and monitoring method based on civil aircraft landing separation specifications

Abstract

The present invention belongs to the field of civil aviation aircraft monitoring technology, and in particular, relates to a wake turbulence monitoring system and monitoring method based on the civil aircraft landing interval specification. It is mainly used to monitor the wake turbulence interval between landing flights, and to prevent the interval between landing flights from being too small during busy flight periods, which may lead to safety problems. The flight information data acquisition module and the basic monitoring parameter setting module are located in the data acquisition and storage server; the wake turbulence monitoring alarm calculation module and the monitoring alarm display presentation module are located in the alarm calculation and distribution server; the data acquisition and storage server and the alarm calculation and distribution server are connected to the control automation system, the monitoring alarm display terminal, and the basic monitoring parameter setting terminal through a signal access switch to transmit data to each other; provide a graphical display of the alarm aircraft, and provide a sound reminder method at the same time. The dual reminder method avoids the control from forgetting or missing the alarm information, and provides full protection for the safe operation of the control.

Description

Technical Field

[0001] The present invention belongs to the technical field of civil aircraft monitoring, and in particular relates to a wake turbulence monitoring system and a monitoring method based on civil aircraft landing interval specifications. Background Art

[0002] Civil aircraft are subject to wake turbulence risks during flight. The minimum wake turbulence separation between preceding and succeeding aircraft must be maintained, meaning the distance between aircraft must meet the wake turbulence separation standard to ensure the avoidance of wake turbulence conflicts during flight. With the rapid development of the civil aviation industry, the number of civil aviation flights has grown rapidly, and the number of flights in China's first-tier cities has reached saturation. The dense operation of flights has led to a gradual increase in the probability of wake turbulence conflicts during flight. This is especially true for landing flights in the approach area. During busy landing periods, the probability of wake turbulence conflict alerts between landing aircraft increases exponentially. Therefore, wake turbulence monitoring and alerts are of great safety significance to approach control.

[0003] The control production systems currently used for approach control include control automation systems, etc. However, in most control units, these systems do not have the function of wake turbulence monitoring and alarm. In this case, wake turbulence monitoring can only rely on manual monitoring, which is not only prone to errors and omissions, but also increases the workload of controllers, posing a major risk source for control safety.

[0004] The wake turbulence standard monitoring method based on the civil aviation aircraft landing interval specification starts from the characteristics of approach control. By distinguishing different aircraft models, the wake turbulence standards between models are set. The system predicts in advance whether the sorted aircraft meet the wake turbulence standards. For aircraft with wake turbulence conflicts, the system provides sound and light warnings to prevent controllers from forgetting or missing warning information, thereby improving the safe operation coefficient of control and reducing the workload of control. Summary of the Invention

[0005] In response to the shortcomings of the existing technology, the present invention establishes an external safety monitoring system based on the control automation system, which mainly monitors the wake turbulence interval between landing flights and prevents the interval between the landing flights from being too small during busy flight periods, which may lead to safety problems.

[0006] The wake turbulence monitoring system based on the civil aircraft landing interval specification includes a flight information data acquisition module, a basic monitoring parameter setting module, a wake turbulence monitoring alarm calculation module, and a monitoring alarm display and presentation module;

[0007] The flight information data acquisition module and the basic monitoring parameter setting module are located in the data acquisition and storage server;

[0008] The wake monitoring alarm calculation module and the monitoring alarm display presentation module are located in the alarm calculation and distribution server;

[0009] The data acquisition and storage server and the alarm calculation and distribution server transmit data to each other through the signal access switch and the control automation system, the monitoring alarm display terminal, and the monitoring basic parameter setting terminal;

[0010] The flight information data acquisition module collects flight dynamic data and comprehensive track data from the control automation system, integrates the two data, and performs storage and forwarding.

[0011] The basic monitoring parameter setting module calculates the basic parameters for monitoring and alarming, configures the wake turbulence separation distance and advance warning duration parameters for two types of flights, and stores the parameters in a database. The module is divided into a front-end and a back-end. The back-end is used for parameter configuration storage, and the front-end provides a configuration interaction page for controllers. The configured parameters take effect immediately.

[0012] The wake turbulence monitoring and alarm calculation module sets a monitoring area, performs wake turbulence monitoring and alarms between flights in the area, determines whether the conditions for landing wake turbulence monitoring are met, and then determines the models of the two flights and whether the trend relationship between the flights is less than the standard wake turbulence interval, thereby triggering a monitoring alarm;

[0013] The monitoring and alarm display presentation module presents the results of the wake turbulence monitoring and alarm calculation module in the form of a web page. Controllers can view flight information and monitoring and alarm information through a browser. It provides air route map display, real-time flight status display, monitoring and alarm information display, and interactive operations. It is divided into front-end and back-end. The back-end is for data interaction and push, and the front-end is for data reception, presentation, and operation interface.

[0014] Furthermore, the flight information data acquisition module includes a flight dynamics data acquisition submodule, a comprehensive track data acquisition submodule, a flight data fusion and forwarding submodule, and a data recording and storage submodule;

[0015] The flight dynamics data acquisition submodule collects flight dynamics data from the control automation system in a unicast manner through the network port, and parses and caches the data according to the flight dynamics data standard parsing protocol 4029.3 protocol format;

[0016] The comprehensive track data acquisition submodule collects the comprehensive track data of the control automation system in a unicast manner through the network port, and the system parses and caches the data according to the format of the standard protocol CAT062;

[0017] The flight data fusion and forwarding submodule retrieves all flight data from the integrated track data cache and the flight dynamic data cache, performs a traversal based on the integrated track data, and checks for each flight's plan information in the flight dynamic cache. If so, the plan data and the integrated track data are simultaneously stored in a new fusion data structure and forwarded. The forwarding uses the internal Redis middleware to provide data support for other modules.

[0018] The data recording and storage submodule records and stores the original flight dynamic data and integrated track data, and stores the calculated fusion data at the same time.

[0019] Furthermore, the basic monitoring parameter setting module includes a monitoring parameter display submodule, a monitoring parameter modification submodule, and a monitoring parameter publishing submodule;

[0020] The monitoring parameter display submodule provides the control personnel with a monitoring parameter display function, displaying the currently effective monitoring parameter values;

[0021] The monitoring parameter modification submodule provides an interactive operation interface for monitoring parameter modification for control personnel, which can modify and save parameter values;

[0022] The monitoring parameter publishing submodule: publishes the modified parameters in a unified manner and provides an operation interface for the publication.

[0023] Furthermore, the wake turbulence monitoring and alarm calculation module includes a parameter data loading submodule, a flight data filtering and loading submodule, a flight landing judgment submodule, a wake turbulence trend alarm calculation submodule, and a monitoring alarm sending submodule;

[0024] The parameter data loading submodule is used to load the interval parameters, pre-alarm time parameters, aircraft type parameters, and basic runway position condition parameters required for monitoring;

[0025] The flight data filtering and loading submodule: loads the current flights from Redis, filters them according to landing conditions, location conditions, and runway conditions, and puts the flights to be calculated into the calculation queue;

[0026] The flight landing judgment submodule calculates whether the flight meets the landing conditions of the open runway based on the flight's position and heading data, and sorts the landing of flights that meet the conditions;

[0027] The wake turbulence trend alarm calculation submodule calculates the trend relationship between flights based on the landing flight's speed, heading, and the distance between the preceding and following aircraft, and determines whether the interval will be less than the interval within the pre-alarm time. If so, an alarm is issued. Since the wake turbulence interval alarm requires high sensitivity, the alarm calculation period is calculated in seconds.

[0028] The monitoring alarm sending submodule performs alarm queue maintenance on the calculated results, including insertion, deletion and update. The first alarm is inserted into the alarm queue, the existing alarm is updated, and the ended alarm is deleted from the alarm queue.

[0029] Furthermore, the monitoring alarm display and presentation module includes a flight fusion data display submodule, a map route display and operation submodule, a monitoring alarm display and operation submodule, and a history record query submodule;

[0030] The flight fusion data display submodule receives flight data sent by the flight information data acquisition module and pushes it to the front-end display to display the air flight data for control;

[0031] The map route display and operation submodule: displays static air route data, map data information, and supports map zooming operations;

[0032] The monitoring alarm display and operation submodule displays the monitoring alarm information sent by the wake turbulence monitoring alarm calculation module, presenting it in the form of sound alarms and a highlighted color display of the flight in the air, allowing controllers to confirm the alarm;

[0033] The historical record query submodule can query and display historical alarm information and provide an alarm filtering query method.

[0034] The wake turbulence monitoring method based on the civil aircraft landing interval specification includes the following steps: S50: the flight information data collection module collects comprehensive track data and flight dynamics data by means of a flight dynamics data collection submodule and a comprehensive track data collection submodule, and the flight data fusion and forwarding submodule fuses the comprehensive track data and flight dynamics data into a message, updates the message in a 4-second cycle, and sends the updated message to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display and presentation module; first, the flight dynamics data is cached according to the flight number and secondary code as unique identifiers, and the latest flight dynamics information of the flight is cached in Redis; each time a message is received, the flight dynamics cache is searched for whether the flight dynamics information exists based on the flight number and secondary code information in the message; if the flight dynamics information does not exist, the corresponding flight dynamics field is left blank; if the information exists, the corresponding field is filled in and the message is sent to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display and presentation module; the original flight dynamics data, comprehensive track data, and fused data are stored in the data recording and storage submodule;

[0035] The S51 wake turbulence monitoring and alarm calculation module loads the monitoring basic parameter setting module information from the parameter data loading submodule, and monitors the interval parameters, pre-warning time parameters, aircraft model parameters, and basic runway position condition parameters required for monitoring. At the same time, it loads the real-time fusion data of the flight. First, the flight data is filtered in the flight data filtering and loading submodule, mainly to select the landing flight from all flights. Then, the flight landing judgment submodule determines whether the flight meets the landing position, altitude, and direction requirements. Among the flights that meet the requirements, the wake turbulence trend alarm calculation submodule determines whether the trend has broken through the interval of the monitoring wake turbulence. When the interval size is broken, the monitoring alarm signal is sent out by the monitoring alarm sending submodule.

[0036] Furthermore, S50 includes the following steps: S10: monitoring the integrated track port, and when the integrated track data appears, parsing the received integrated track data, and searching the redis cache of Feixing Dynamics for the flight dynamic data according to the parsed flight number and secondary code, and if so, turning to S11, otherwise turning to S12;

[0037] S11: Combine the altitude, speed, heading and other data in the integrated track with the command altitude, take-off and landing airport and route information data in the flight dynamics to form new fused data, and send the fused data to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display module according to a predetermined data structure, and then go to S13;

[0038] S12: Only the altitude, speed, and heading field data in the integrated track are filled into the fused data structure, and the corresponding flying star dynamic field data is left empty. The fused data is sent to the wake monitoring and alarm calculation module and the monitoring and alarm display module, and then the process goes to S13;

[0039] S13: Continue to monitor the integrated track data port and wait for new data.

[0040] Furthermore, S51 includes the following steps:

[0041] Flight data filtering and loading submodule process:

[0042] S20: Load the current flights from Redis, filter out unscheduled flights and flights at non-landing airports, and if there are still flights, go to S21, otherwise exit the current calculation process;

[0043] S21: Calculate whether the flight's runway meets the current landing runway conditions. If there is still a flight, go to S22; otherwise, jump out of the current calculation process;

[0044] S22: Whether the location is within the calculation range is mainly determined by filtering based on latitude, longitude, and altitude. If there is still a flight, it is stored in the flight calculation queue; otherwise, the current calculation process is exited;

[0045] Flight landing judgment submodule process:

[0046] S30: Load flights from the flight queue to be calculated. If there is no flight information, the calculation is terminated, otherwise go to S31;

[0047] S31: Calculate whether the flight meets the runway alignment condition based on the heading. If so, go to S32; otherwise, delete the flight.

[0048] S32: Determine whether the flight is in a state of continuous decline in the historical process. If so, add the flight to the judgment queue;

[0049] Wake trend alarm calculation submodule process:

[0050] S40: Check and determine whether there are more than or equal to two flights in the queue. If so, go to S41; if not, terminate the calculation.

[0051] S41: Traverse flights in the order of landing. If a flight exists, continue the calculation; otherwise, go to S40. Determine whether the subsequent flight has a catching-up relationship with the previous flight. If so, go to S42; otherwise, exit and calculate the next flight.

[0052] S42: Determine whether the distance between the flight and the overtaking flight meets the safety interval within the preset warning time range. If not, proceed to S43; otherwise, proceed to the next flight in S41 and continue the calculation.

[0053] S43: When the alarm condition is met, the alarm data is sent from the monitoring alarm sending submodule to the monitoring alarm display and presentation module, and the calculation returns to S41.

[0054] The present invention is based on the wake vortex standard of the landing interval specification for civil aircraft. Based on this standard, a wake vortex monitoring system and monitoring method are developed. The aviation dynamic data of civil aircraft are introduced to monitor according to different aircraft types. When it is predicted that the aircraft wake vortex interval is less than the standard interval, a reminder alarm is provided to the controller in a timely manner that the landing aircraft wake vortex interval is less than the standard. The alarm is provided in the form of an audible and visual alarm, which not only provides a graphical display of the warning aircraft, but also provides an audible reminder. The dual reminder method avoids controller errors and omissions of warning information, thereby providing full protection for safe operation of the controller.

[0055] The present invention can identify whether the wake turbulence separation of landing aircraft meets the standards and prevent the occurrence of dangerous control events; the wake turbulence separation provides sufficient time and space margin for adjustment and can identify all conflict information in different situations; the false alarm rate is low, and through multiple parameter settings, the system and the site are highly matched, reducing interference with control personnel; it can adapt to a variety of different runway operation modes and has high scalability; it has efficient calculation, accurate data, low latency, and is applicable to control conditions in various situations, especially conditions that are unfavorable to control command, providing an important guarantee for control safety.

[0056] The present invention is based on data from control automation and is externally connected to the control automation system. The monitoring system receives the control flight data sent by the control automation system, and combines it with the standard wake vortex monitoring method to calculate the wake vortex relationship between flights in the air and predict whether an alarm will occur. For any alarm that occurs, the monitoring system provides alarms in the form of sound, light and images to the controller using the alarm display device and sound reminder device, and implements a confirmation mechanism.

[0057] The present invention performs monitoring and calculation based on data from automated control. The automated system data is an external data input source and is flight data generated by real-time control of aviation. The data mainly includes flight plan data (take-off time, route information, etc.), sectors, position coordinates, heading, flight speed and altitude, etc. The system uses all landed aircraft in the approach control airspace as calculation aircraft, identifies the occurrence of wake turbulence separation conflicts between aircraft, and plays a predictive role through conflict calculation, promptly reminding controllers of wake turbulence conflicts, thereby playing a supervisory role in air traffic safety. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1This is a structural block diagram of the wake turbulence monitoring system based on the civil aircraft landing separation specification of the present invention;

[0059] Figure 2 For the present invention Figure 1 The structural block diagram of the flight information data collection module in;

[0060] Figure 3 For the present invention Figure 1 The structural diagram of the basic monitoring parameter setting module in;

[0061] Figure 4 For the present invention Figure 1 The structural block diagram of the wake monitoring and alarm calculation module in the figure;

[0062] Figure 5 For the present invention Figure 1 The structural block diagram of the monitoring and alarm display module is shown in Figure 2. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of this application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0064] Civil aircraft: aircraft primarily used in the civil aviation transport industry, referring to aircraft legally registered with the civil aviation authorities.

[0065] Separation specification: The landing separation between the aircraft in front and behind when the aircraft lands. The separation is calculated based on the distance.

[0066] Wake turbulence separation: To ensure safety, the safe distance that aircraft must maintain between each other during flight.

[0067] like Figure 1 As shown:

[0068] The wake turbulence monitoring system, based on the civil aircraft landing separation specification, includes software modules for flight information data collection, basic monitoring parameter setting, wake turbulence monitoring alarm calculation, and monitoring alarm display. The hardware includes a data collection and storage server, an alarm calculation and distribution server, a signal access switch, a monitoring alarm display terminal, a basic monitoring parameter setting terminal, and common networking equipment.

[0069] The flight information data acquisition module and the basic monitoring parameter setting module are located in the data acquisition and storage server;

[0070] The wake monitoring alarm calculation module and the monitoring alarm display presentation module are located in the alarm calculation and distribution server;

[0071] The data acquisition and storage server and the alarm calculation and distribution server transmit data to each other through the signal access switch and the control automation system, the monitoring alarm display terminal, and the monitoring basic parameter setting terminal;

[0072] The flight information data acquisition module collects flight dynamics data and integrated track data from the control automation system, fuses the two data, and cooperates with storage and forwarding; the data sent by the control automation system includes two types of data, namely flight dynamics data and integrated track data, which respectively represent static plan data and dynamic air flight data of the flight. The above two types of data are required for the monitoring method calculation. After the flight information data acquisition module collects the two types of data, it fuses the two types of information into a type of data that can be used for internal alarm calculation based on common information such as flight number information. For example, for air flights, the flight plan information (route information, take-off and landing airports, etc.) is extracted from the flight dynamics data, and the real-time position, altitude, heading and other data of the flight are extracted from the integrated track data. After the two types of data are obtained, the data are fused according to the common field (flight number) of the two types of data to form the new data required for internal alarm calculation, namely the fused data.

[0073] The basic monitoring parameter setting module calculates the basic parameters for monitoring and alarming, configures the wake turbulence separation distance and advance warning duration parameters for two types of flights, and stores the parameters in a database. The module is divided into a front-end and a back-end. The back-end is used for parameter configuration storage, and the front-end provides a configuration interaction page for controllers. The configured parameters take effect immediately.

[0074] The wake turbulence monitoring and alarm calculation module sets a monitoring area, performs wake turbulence monitoring and alarms between flights in the area, determines whether the conditions for landing wake turbulence monitoring are met, and then determines the models of the two flights and whether the trend relationship between the flights is less than the standard wake turbulence interval, thereby triggering a monitoring alarm;

[0075] The monitoring and alarm display presentation module presents the results of the wake turbulence monitoring and alarm calculation module in the form of a web page. Controllers can view flight information and monitoring and alarm information through a browser. It provides air route map display, real-time flight status display, monitoring and alarm information display, and interactive operations. It is divided into front-end and back-end. The back-end is for data interaction and push, and the front-end is for data reception, presentation, and operation interface.

[0076] Further, if Figure 2 As shown:

[0077] The flight information data acquisition module includes a flight dynamics data acquisition submodule, a comprehensive track data acquisition submodule, a flight data fusion and forwarding submodule, and a data recording and storage submodule;

[0078] The flight dynamics data acquisition submodule collects flight dynamics data from the control automation system in a unicast manner through the network port, and parses and caches the data according to the flight dynamics data standard parsing protocol 4029.3 protocol format;

[0079] The integrated track data acquisition submodule collects integrated track data from the control automation system in a unicast manner through the network port. The amount of integrated track data is large, and the system adopts a dual-threaded receiving and processing method to prevent the problem of receiving blockage caused by untimely processing. The system parses and caches the data in the format of the standard protocol CAT062;

[0080] The flight data fusion and forwarding submodule retrieves all flight data from the integrated track data cache and the flight dynamic data cache, performs a traversal based on the integrated track data, and checks for each flight's plan information in the flight dynamic cache. If so, the plan data and the integrated track data are simultaneously stored in a new fusion data structure and forwarded. The forwarding uses the internal Redis middleware to provide data support for other modules.

[0081] The data recording and storage submodule records and stores the original flight dynamic data and integrated track data, and stores the calculated fusion data at the same time.

[0082] Furthermore, if Figure 3 As shown:

[0083] The basic monitoring parameter setting module includes a monitoring parameter display submodule, a monitoring parameter modification submodule, and a monitoring parameter publishing submodule;

[0084] The monitoring parameter display submodule provides the control personnel with a monitoring parameter display function, displaying the currently effective monitoring parameter values;

[0085] The monitoring parameter modification submodule provides an interactive operation interface for monitoring parameter modification for control personnel, which can modify and save parameter values;

[0086] The monitoring parameter publishing submodule: publishes the modified parameters in a unified manner and provides an operation interface for the publication.

[0087] Furthermore, if Figure 4 As shown:

[0088] The wake turbulence monitoring and alarm calculation module includes a parameter data loading submodule, a flight data filtering and loading submodule, a flight landing judgment submodule, a wake turbulence trend alarm calculation submodule, and a monitoring alarm sending submodule;

[0089] The parameter data loading submodule is used to load the interval parameters, pre-alarm time parameters, aircraft type parameters, and basic runway position condition parameters required for monitoring;

[0090] The flight data filtering and loading submodule: loads the current flights from Redis, filters them according to landing conditions, location conditions, and runway conditions, and puts the flights to be calculated into the calculation queue;

[0091] The flight landing judgment submodule calculates whether the flight meets the landing conditions of the open runway based on the flight's position and heading data, and sorts the landing of flights that meet the conditions;

[0092] The wake turbulence trend alarm calculation submodule calculates the trend relationship between flights based on the landing flight's speed, heading, and the distance between the preceding and following aircraft, and determines whether the interval will be less than the interval within the pre-alarm time. If so, an alarm is issued. Since the wake turbulence interval alarm requires high sensitivity, the alarm calculation period is calculated in seconds.

[0093] The monitoring alarm sending submodule performs alarm queue maintenance on the calculated results, including insertion, deletion and update. The first alarm is inserted into the alarm queue, the existing alarm is updated, and the ended alarm is deleted from the alarm queue.

[0094] Further, if Figure 5 As shown:

[0095] The monitoring alarm display and presentation module includes a flight fusion data display submodule, a map route display and operation submodule, a monitoring alarm display and operation submodule, and a history record query submodule;

[0096] The flight fusion data display submodule receives flight data sent by the flight information data acquisition module and pushes it to the front-end display to display the air flight data for control;

[0097] The map route display and operation submodule: displays static air route data, map data information, and supports map zooming operations;

[0098] The monitoring alarm display and operation submodule displays the monitoring alarm information sent by the wake turbulence monitoring alarm calculation module, presenting it in the form of sound alarms and a highlighted color display of the flight in the air, allowing controllers to confirm the alarm;

[0099] The historical record query submodule can query and display historical alarm information and provide an alarm filtering query method.

[0100] The flight information data collection module mainly processes two types of data collected from the control automation system. For each type of data, data verification is performed to ensure data integrity, data cleaning is performed to ensure data preparation, and data analysis is performed to ensure data preparation and analysis. The data content of each type of data is as follows:

[0101] Flight dynamics data: For each flight, each piece of flight dynamics information includes the flight number, secondary code, planned take-off time, take-off and landing airports, alternate airports, command altitude, route and reporting point information, etc. It is a kind of external information sent by the controller to command the flight.

[0102] Comprehensive track data: This part of the information is quantitative data on the flight's status in the air. For each flight in the air, this data is updated at a cycle of 4 seconds, that is, the data is updated once every 4 seconds for each flight. The format of each updated data is fixed. The fields that can be parsed according to the format include: flight number, secondary code, track number, altitude, speed, navigation direction, crew dial altitude and other flight dynamic information.

[0103] The wake turbulence monitoring method based on the civil aircraft landing separation specification includes the following steps:

[0104] S50: The flight information data acquisition module collects comprehensive track data and flight dynamics data by the flight dynamics data acquisition submodule and the comprehensive track data acquisition submodule. The flight data fusion and forwarding submodule fuses the comprehensive track data and flight dynamics data into a message, which is updated every 4 seconds. The updated information is sent to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display and presentation module. First, the flight dynamics data is cached according to the flight number and secondary code as the unique identifier, and the latest flight dynamics information is cached in Redis. Each time a message is received, the flight dynamics cache is checked for flight dynamics information based on the flight number and secondary code in the message. If no flight dynamics information exists, the corresponding flight dynamics field is left empty. If so, the corresponding field is filled in and the message is sent to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display and presentation module. The original flight dynamics data, comprehensive track data, and fused data are stored in the data record storage submodule. The specific processing flow of S50 is as follows:

[0105] S10: Monitor the integrated track port. When the integrated track data appears, parse the received integrated track data. Based on the parsed flight number and secondary code, check whether there is flight dynamic data for the flight in the Redis cache of Feixing Dynamics. If there is, go to S11; if not, go to S12.

[0106] S11: Combine the altitude, speed, heading and other data in the integrated track with the command altitude, take-off and landing airport and route information data in the flight dynamics to form new fused data, and send the fused data to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display module according to a predetermined data structure, and then go to S13;

[0107] S12: Only the altitude, speed, and heading field data in the integrated track are filled into the fused data structure, and the corresponding flying star dynamic field data is left empty. The fused data is sent to the wake monitoring and alarm calculation module and the monitoring and alarm display module, and then the process goes to S13;

[0108] S13: Continue to monitor the integrated track data port and wait for new data;

[0109] The fused data is a collection of aircraft in the current airspace. The data includes the aircraft's position, speed, altitude, heading, take-off and landing airports, route, altitude instructions and other data. The fused data is multicasted throughout the system in the form of a network signal. The multicast address is configured by the system, and the devices within the multicast can receive and process the relevant data.

[0110] S51: The wake turbulence monitoring alarm calculation module loads the monitoring basic parameter setting module information from the parameter data loading submodule, and the interval parameters, pre-alarm time parameters, aircraft model parameters, and runway position condition basic parameters required for monitoring are loaded at the same time. At the same time, the real-time fusion data of the flight is loaded. First, the flight data is filtered in the flight data filtering loading submodule, mainly to select the landing flight from all flights. Then, the flight landing judgment submodule determines whether the flight meets the landing position, altitude, and direction requirements. Among the flights that meet the requirements, the wake turbulence trend alarm calculation submodule determines whether the trend has broken through the interval of the monitoring wake turbulence. When the interval size is broken, the monitoring alarm signal is sent out by the monitoring alarm sending submodule. The specific processing flow of S51 is as follows:

[0111] Flight data filtering and loading submodule process:

[0112] S20: Load the current flights from Redis, filter out unscheduled flights and flights at non-landing airports, and if there are still flights, go to S21, otherwise exit the current calculation process;

[0113] S21: Calculate whether the flight's runway meets the current landing runway conditions. If there is still a flight, go to S22; otherwise, jump out of the current calculation process;

[0114] S22: Whether the location is within the calculation range is mainly determined by filtering based on latitude, longitude, and altitude. If there is still a flight, it is stored in the flight calculation queue; otherwise, the current calculation process is exited;

[0115] Flight landing judgment submodule process:

[0116] S30: Load flights from the flight queue to be calculated. If there is no flight information, the calculation is terminated, otherwise go to S31;

[0117] S31: Calculate whether the flight meets the runway alignment condition based on the heading. If so, go to S32; otherwise, delete the flight.

[0118] S32: Determine whether the flight is in a continuous decline state in the historical process. If so, add the flight to the judgment queue;

[0119] Wake trend alarm calculation submodule process:

[0120] S40: Check and determine whether there are more than or equal to two flights in the queue. If so, go to S41; if not, terminate the calculation.

[0121] S41: Traverse flights in the order of landing. If a flight exists, continue the calculation; otherwise, go to S40. Determine whether the subsequent flight has a catching-up relationship with the previous flight. If so, go to S42; otherwise, exit and calculate the next flight.

[0122] S42: Determine whether the distance between the flight and the overtaking flight meets the safety interval within the preset warning time range. If not, proceed to S43; otherwise, proceed to the next flight in S41 and continue the calculation.

[0123] S43: When the alarm condition is met, the alarm data is sent from the monitoring alarm sending submodule to the monitoring alarm display and presentation module, and the calculation returns to S41.

[0124] The present invention has been described above by way of example with reference to the accompanying drawings. It is apparent that the specific implementation of the present invention is not limited to the above-described embodiments. Those skilled in the art may make various modifications or variations to the present invention without departing from the technical concept of the present invention, and such modifications or variations shall naturally fall within the scope of protection of the present invention.

Claims

1. A wake turbulence monitoring system based on civil aircraft landing separation specifications, characterized by: It includes flight information data collection module, basic monitoring parameter setting module, wake turbulence monitoring alarm calculation module, and monitoring alarm display and presentation module; The flight information data acquisition module and the basic monitoring parameter setting module are located in the data acquisition and storage server; The wake monitoring alarm calculation module and the monitoring alarm display presentation module are located in the alarm calculation and distribution server; The data acquisition and storage server and the alarm calculation and distribution server are connected to the control automation system, the monitoring alarm display terminal, and the monitoring basic parameter setting terminal through the signal access switch to transmit data to each other; The flight information data acquisition module collects flight dynamic data and comprehensive track data from the control automation system, integrates the two data, and performs storage and forwarding. The basic monitoring parameter setting module calculates the basic parameters for monitoring and alarming, configures the wake turbulence separation distance and advance warning duration parameters for two types of flights, and stores the parameters in a database. The module is divided into a front-end and a back-end. The back-end is used for parameter configuration storage, and the front-end provides a configuration interaction page for controllers. The configured parameters take effect immediately. The basic monitoring parameter setting module includes a monitoring parameter display submodule, a monitoring parameter modification submodule, and a monitoring parameter publishing submodule; The monitoring parameter display submodule provides the control personnel with a monitoring parameter display function, displaying the currently effective monitoring parameter values; The monitoring parameter modification submodule provides an interactive operation interface for monitoring parameter modification for control personnel, which can modify and save parameter values; The monitoring parameter publishing submodule: publishes the modified parameters in a unified manner and provides an operation interface for publishing; The wake turbulence monitoring and alarm calculation module sets a monitoring area, performs wake turbulence monitoring and alarms between flights in the area, determines whether the conditions for landing wake turbulence monitoring are met, and then determines the models of the two flights and whether the trend relationship between the flights is less than the standard wake turbulence interval, thereby triggering a monitoring alarm; The wake turbulence monitoring and alarm calculation module includes a parameter data loading submodule, a flight data filtering and loading submodule, a flight landing judgment submodule, a wake turbulence trend alarm calculation submodule, and a monitoring alarm sending submodule; The parameter data loading submodule is used to load the interval parameters, pre-alarm time parameters, aircraft type parameters, and basic runway position condition parameters required for monitoring; The flight data filtering and loading submodule: loads the current flights from Redis, filters them according to landing conditions, location conditions, and runway conditions, and puts the flights to be calculated into the calculation queue; The flight landing judgment submodule calculates whether the flight meets the landing conditions of the open runway based on the flight's position and heading data, and sorts the landing of flights that meet the conditions; The wake turbulence trend alarm calculation submodule calculates the trend relationship between flights based on the landing flight's speed, heading, and the distance between the preceding and following aircraft, and determines whether the interval will be less than the interval within the pre-alarm time. If so, an alarm is issued. Since the wake turbulence interval alarm requires high sensitivity, the alarm calculation period is calculated in seconds. The monitoring alarm sending submodule: performs alarm queue maintenance for the calculated results, including insertion, deletion and update. For the first alarm, it is inserted into the alarm queue, for the existing alarm, it is updated, and for the ended alarm, it is deleted from the alarm queue; The monitoring and alarm display presentation module presents the results of the wake turbulence monitoring and alarm calculation module in the form of a web page. Controllers can view flight information and monitoring and alarm information through a browser. It provides air route map display, real-time flight status display, monitoring and alarm information display, and interactive operations. It is divided into front-end and back-end. The back-end is for data interaction and push, and the front-end is for data reception, presentation, and operation interface.

2. The wake turbulence monitoring system based on the civil aircraft landing separation specification according to claim 1, characterized in that: The flight information data acquisition module includes a flight dynamics data acquisition submodule, a comprehensive track data acquisition submodule, a flight data fusion and forwarding submodule, and a data recording and storage submodule; The flight dynamics data acquisition submodule collects flight dynamics data from the control automation system in a unicast manner through the network port, and parses and caches the data according to the flight dynamics data standard parsing protocol 4029.3 protocol format; The comprehensive track data acquisition submodule collects the comprehensive track data of the control automation system in a unicast manner through the network port, and the system parses and caches the data according to the format of the standard protocol CAT062; The flight data fusion and forwarding submodule retrieves all flight data from the integrated track data cache and the flight dynamic data cache, performs a traversal based on the integrated track data, and checks for each flight's plan information in the flight dynamic cache. If so, the plan data and the integrated track data are simultaneously stored in a new fusion data structure and forwarded. The forwarding uses the internal Redis middleware to provide data support for other modules. The data recording and storage submodule records and stores the original flight dynamic data and integrated track data, and stores the calculated fusion data at the same time.

3. The wake turbulence monitoring system based on the civil aircraft landing separation specification according to claim 2, characterized in that: The monitoring alarm display and presentation module includes a flight fusion data display submodule, a map route display and operation submodule, a monitoring alarm display and operation submodule, and a history record query submodule; The flight fusion data display submodule receives flight data sent by the flight information data acquisition module and pushes it to the front-end display to display the air flight data for control; The map route display and operation submodule: displays static air route data, map data information, and supports map zooming operations; The monitoring alarm display and operation submodule displays the monitoring alarm information sent by the wake turbulence monitoring alarm calculation module, presenting it in the form of sound alarms and a highlighted color display of the flight in the air, allowing controllers to confirm the alarm; The historical record query submodule can query and display historical alarm information and provide an alarm filtering query method.

4. A wake turbulence monitoring method based on civil aircraft landing separation specifications, characterized by: The following steps are involved: S50: The flight information data acquisition module collects comprehensive track data and flight dynamics data by the flight dynamics data acquisition submodule and the comprehensive track data acquisition submodule. The flight data fusion and forwarding submodule fuses the comprehensive track data and flight dynamics data into a message, which is updated every 4 seconds. The updated information is sent to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display and presentation module. First, the flight dynamics data is cached according to the flight number and secondary code as the unique identifier, and the latest flight dynamics information is cached in Redis. Each time a message is received, the flight dynamics cache area is checked for flight dynamics information based on the flight number and secondary code information in the message. If no flight dynamics information exists, the corresponding flight dynamics field is left empty. If so, the corresponding field is filled in and the message is sent to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display and presentation module. The original flight dynamics data, comprehensive track data, and fused data are stored in the data record storage submodule. S51: The wake turbulence monitoring and alarm calculation module loads the monitoring basic parameter setting module information from the parameter data loading submodule, including the required monitoring interval parameters, pre-alarm time parameters, aircraft model parameters, and basic runway position condition parameters. It also loads the real-time fusion data of the flight. First, the flight data is filtered in the flight data filtering and loading submodule, primarily selecting the landing flight from all flights. The flight landing judgment submodule then determines whether the flight meets the landing position, altitude, and direction requirements. For flights that meet the requirements, the wake turbulence trend alarm calculation submodule determines whether the trend has exceeded the interval for monitoring wake turbulence. If the interval is exceeded, a monitoring alarm signal is sent out by the monitoring alarm sending submodule. S50 includes the following steps: S10: Monitor the integrated track port. When the integrated track data appears, parse the received integrated track data. Based on the parsed flight number and secondary code, check whether there is flight dynamic data for the flight in the Redis cache of Feixing Dynamics. If there is, go to S11; if not, go to S12. S11: Combine the altitude, speed, and heading data in the integrated track with the command altitude, take-off and landing airport, and route information data in the flight dynamics to form new fused data, and send the fused data to the wake turbulence monitoring and alarm calculation module and the monitoring and alarm display module according to a predetermined data structure, and then proceed to S13; S12: Only the altitude, speed, and heading field data in the integrated track are filled into the fused data structure, and the corresponding flying star dynamic field data is left empty. The fused data is sent to the wake monitoring and alarm calculation module and the monitoring and alarm display module, and then the process goes to S13; S13: Continue to monitor the integrated track data port and wait for new data; S51 includes the following steps: Flight data filtering and loading submodule process: S20: Load the current flights from Redis, filter out unscheduled flights and flights at non-landing airports, and if there are still flights, go to S21, otherwise exit the current calculation process; S21: Calculate whether the flight's runway meets the current landing runway conditions. If there is still a flight, go to S22; otherwise, jump out of the current calculation process; S22: Whether the location is within the calculation range is mainly determined by filtering based on latitude, longitude, and altitude. If there is still a flight, it is stored in the flight calculation queue; otherwise, the current calculation process is exited; Flight landing judgment submodule process: S30: Load flights from the flight queue to be calculated. If there is no flight information, the calculation is terminated, otherwise go to S31; S31: Calculate whether the flight meets the runway alignment condition based on the heading. If so, go to S32; otherwise, delete the flight. S32: Determine whether the flight is in a continuous decline state in the historical process. If so, add the flight to the judgment queue; Wake trend alarm calculation submodule process: S40: Check and determine whether there are more than or equal to two flights in the queue. If so, go to S41; if not, terminate the calculation. S41: Traverse flights in the order of landing. If a flight exists, continue the calculation; otherwise, go to S40. Determine whether the subsequent flight has a catching-up relationship with the previous flight. If so, go to S42; otherwise, exit and calculate the next flight. S42: Determine whether the distance between the flight and the overtaking flight meets the safety interval within the preset warning time range. If not, proceed to S43; otherwise, proceed to the next flight in S41 and continue the calculation. S43: When the alarm condition is met, the alarm data is sent from the monitoring alarm sending submodule to the monitoring alarm display and presentation module, and the calculation returns to S41.

Images