A Method and System for Monitoring and Intelligent Notification of Changes in Multi-Source Heterogeneous Data in Aviation Bulletins
By unifying the access and standardizing the processing of multi-source heterogeneous data, and combining dynamic situational awareness and intelligent notification strategies, the problems of scattered data sources and delayed change detection in the aviation bulletin system have been solved, enabling real-time monitoring and adaptive notification, and improving the reliability and efficiency of information transmission under extreme conditions.
Patent Information
- Application Number
- CN202611347453.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-02
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2046-09-02
AI Technical Summary
The existing aviation notification system suffers from problems such as scattered data sources, strong heterogeneity, delayed change detection, single notification strategy, lack of impact assessment, and inability to adapt to dynamic changes in meteorological environment and personnel status, resulting in information delays, overload, and insufficient response.
It enables unified access and standardized processing of multi-source heterogeneous data, combines dynamic situational awareness to dynamically adjust monitoring frequency, monitor changes in aviation bulletin data and assess the scope of impact, and generate intelligent notification strategies based on the recipient's environment and operating mode. This includes the integration of various parsing adapters, situational awareness modules, monitoring frequency adjustment, impact assessment, and notification generation modules.
It enables real-time monitoring, accurate assessment, and dynamic adaptive notification of aviation notices, improving the reliability and efficiency of information transmission under extreme conditions and reducing information overload and omissions.
Smart Images

Figure CN122867448B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of aviation operation information management technology, specifically to a method and system for monitoring and intelligently notifying changes in multi-source heterogeneous data of aviation announcements. Background Technology
[0002] Aeronautical bulletins are key information carriers for ensuring flight safety and operational efficiency. They cover a variety of types, including NOTAMs, aeronautical meteorological bulletins, airport operations bulletins, aeronautical information compilation revision bulletins, airspace management bulletins, and flight schedule change bulletins. Timely access to and accurate understanding of aeronautical bulletins directly affects the decision-making quality and response timeliness of flight crews, dispatchers, air traffic controllers, and airport operations personnel. Currently, the issuance and management of aviation bulletins suffer from the following prominent problems and shortcomings: data sources are highly dispersed and heterogeneous; aviation bulletins are issued by different entities, such as the Civil Aviation Administration of China's Air Traffic Management Bureau Information Center, regional air traffic management bureaus, airport management agencies, airline operation control centers, and meteorological service agencies, through their respective systems or channels. Data types include structured database records, XML / JSON format messages, PDF documents, HTML web pages, and plain text files, with significant differences in data format, field definitions, encoding rules, update frequency, and interface protocols among the data sources; existing technologies typically process aviation bulletins of a single type or from a single source, lacking a unified monitoring capability for all categories of aviation bulletins; and change detection methods are outdated and lack timeliness. In current industry practice, monitoring changes to aviation bulletins mainly relies on manual, periodic logins to various bulletin publishing platforms or passive reception of update notifications via email subscriptions, RSS subscriptions, etc. The detection cycle is usually measured in hours or days, making it impossible to achieve real-time or near-real-time change detection. There is a significant time lag in obtaining important bulletins. The notification methods are also limited and lack environmental awareness. Existing aviation bulletin notification systems generally adopt a uniform push strategy, sending information through the same channels and in the same form regardless of the recipient's operating environment. This fails to consider the differences in network connectivity, device capabilities, attention status, and workload of recipients under different operating environments, resulting in low notification delivery rates, insufficient attention, or information overload. There is a lack of methods for assessing the impact of changes to announcements; existing technologies typically only forward and push the announcement content itself, lacking automatic correlation analysis and impact assessment of operational elements such as flights, routes, airports, and airspace that may be affected by the changes. Recipients need to read and analyze each announcement individually to determine its relevance to their work, which is inefficient and prone to omissions. The coupled impact of meteorological environment and personnel status on the operation of the announcement system is ignored; the aviation announcement system itself operates in a dynamically changing meteorological environment and personnel working status; severe weather not only generates a large number of meteorological announcements, but also leads to a decrease in the accuracy of data source sensors, a surge in data change frequency, and a reduction in the reliability of communication links; at the same time, under high-load operating conditions, the cognitive burden on dispatchers and crew members increases, and their information processing capabilities decrease. Existing technologies lack the ability to dynamically link external meteorological conditions, personnel work status, system operating load, and announcement monitoring and notification mechanisms. They cannot adaptively adjust monitoring frequency, notification granularity, and push strategies under extreme conditions, which may lead to message backlog, notification delays, or information overload during critical periods. They also lack the ability to respond to micro-meteorological differences and sudden weather changes. Wind speed and visibility may vary significantly at different runway heads of the same airport, and existing systems cannot perform fine-grained announcement correlation analysis based on dynamic thresholds at the runway level. At the same time, for sudden and severe weather events such as summer heat thunderstorms, the forecast time window is extremely short, and traditional polling monitoring mechanisms are unable to achieve early warning and timely notification. Summary of the Invention
[0003] The purpose of this invention is to provide a method and system for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data, in order to solve the problems in the existing technology such as dispersed data sources, strong heterogeneity, delayed change detection, single notification strategy, lack of impact assessment, and inability to adapt to dynamic changes in meteorological environment and personnel status. This invention enables real-time monitoring, intelligent analysis, accurate assessment, and dynamic adaptive notification of changes in aviation bulletin data.
[0004] To achieve the above objectives, the present invention provides the following technical solution: This invention provides a method for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data, comprising the following steps: S1. Multi-source heterogeneous aviation bulletin data access and standardization processing. Configure data source adaptation parameters and establish data connection channels with various aviation bulletin publishing sources; obtain raw aviation bulletin data from each data source according to the preset basic polling time interval. Select the corresponding parsing adapter according to the data source type to parse the format and extract fields from the raw data; map the extracted fields to a unified bulletin data model to generate standardized bulletin data records and store them in the bulletin database; S2. Dynamic monitoring frequency adjustment; acquire current operational situation awareness information, which includes at least one of meteorological situation information, system load status information, and personnel work status information; assess the current operational risk level based on the operational situation awareness information; when the operational risk level increases, shorten the polling interval to increase the monitoring frequency; when the operational risk level decreases, restore or extend the polling interval to reduce system resource consumption. S3. Monitoring and identifying changes in aviation bulletin data; read historical bulletin data records from the bulletin database and compare them with the newly generated standardized bulletin data records in step one; the comparison dimensions include bulletin identifier, bulletin content, bulletin status, effective time, expiration time, scope of impact, and priority level; when any of the following situations are found: new bulletin, modified bulletin content, changed bulletin status, or bulletin revocation, it is determined that a bulletin data change event has occurred, and a change event record is generated; S4. Impact Assessment of Announcement Changes: Extract the impact scope field from the change event record to identify affected operational elements, including airports, airways, airspace, navigation facilities, runways, and procedure types. Match these operational elements with flight schedules to obtain a list of affected flights. Calculate the impact severity score for each affected flight. The impact severity score is determined based on the degree of overlap between the flight's effective time and the announcement's effective time, the spatial correlation between the flight and the announcement's impact scope, and the additional impact coefficient of the current weather conditions on the flight's operation. S5. Dynamic notification strategy generation; Obtain the current operating environment information of the recipient, which includes at least one of the following: the recipient's geographical location, network connection status, device type, and current work task status; Determine the environmental scenario of the recipient based on the operating environment information, including high-altitude flight scenario, ground operation control scenario, and airport on-site operation scenario; Obtain current operating situation awareness information, and determine the current operating mode based on the operating situation awareness information, including normal operating mode and abnormal operating mode; For different combinations of environmental scenarios and operating modes, select the corresponding notification strategy from the preset notification strategy library, which includes notification channel combination, notification priority filtering rules, message simplification rules, repeated notification interval rules, and notification rate limiting rules; S6. Intelligent notification generation and sending: Based on the impact score determined in step four and the notification strategy selected in step five, generate a notification message; the notification message includes an announcement summary, change description, impact range description, impact level, additional tips related to the current weather situation, and a link to obtain the original announcement; send the notification message to the receiving terminal according to the notification channel combination and notification flow restriction rules specified by the notification strategy.
[0005] When parsing the format of the raw data in S1, for announcement sources of HTML web page type, the announcement field is extracted by the extraction path positioning method. The extraction path is composed of the tag name, attribute name and attribute value of the HTML element. For announcement sources of PDF document type, the announcement field is extracted by the region positioning method. The region positioning is determined by the page number range and the coordinate range.
[0006] The meteorological situation information mentioned in S2 includes at least one of the following: weather phenomenon type, thunderstorm coverage area, icing intensity level, visibility value, crosswind component value, and runway visual range value for the current and forecast periods; the system load status information includes at least one of the following: current pending announcement data queue length, processor usage ratio, memory usage ratio, and network communication latency value; the personnel work status information includes at least one of the following: number of dispatchers on duty, current average number of flights monitored per person, and current shift period characteristics; the operational risk level is assessed by: quantifying the meteorological situation information, the system load status information, and the personnel work status information respectively... The system is matched against its respective preset threshold ranges to determine a risk level of low, medium, or high. When the risk level is low, the basic polling interval remains at the preset first duration. When the risk level is medium, the polling interval is shortened to the preset second duration, which is shorter than the first duration. When the risk level is high, the polling interval is further shortened to the preset third duration, which is shorter than the second duration, and a continuous monitoring mode for key announcement sources is simultaneously initiated. The continuous monitoring mode refers to maintaining a long connection to the key announcement sources and actively pushing updates to the system as soon as the data source is updated, achieving a response time of seconds or even sub-seconds.
[0007] In S3, the announcement data change monitoring adds an event triggering mechanism on top of the polling interval for announcement sources with a posting frequency higher than a preset threshold. That is, when the data source actively pushes a change message, a change monitoring is triggered immediately, regardless of the polling interval. This dual monitoring mechanism ensures both the coverage of regular monitoring and the ability to respond instantly to high-frequency change sources.
[0008] The impact score in S4 is calculated as follows: First, the planned flight duration within the effective period of the announcement is obtained, and the planned flight duration is compared with the total effective period of the announcement to obtain the time overlap ratio; then, the spatial correlation between the flight and the scope of the announcement's impact is obtained; next, the additional impact coefficient of the current weather situation on flight operations is obtained, and the additional impact coefficient is determined based on the weather phenomenon type and intensity level of the area through which the flight is planned to pass; the time overlap ratio, spatial correlation, and additional impact coefficient are multiplied together to obtain the impact score.
[0009] The time overlap ratio is obtained as follows: if the planned flight operation period overlaps with the effective period of the announcement, the overlap duration divided by the total effective period of the announcement is the time overlap ratio; if there is no overlap, the time overlap ratio is zero. The spatial correlation degree is obtained as follows: if the operational elements passed by the flight completely overlap with the scope of the announcement's influence, the spatial correlation degree is one; if there is partial overlap, the percentage of the overlapping portion is the spatial correlation degree; if there is no overlap, the spatial correlation degree is zero. The additional impact coefficient is obtained by querying the network corresponding to the flight's planned waypoints. The system uses gridded weather forecast data to identify whether the waypoint is located in a thunderstorm-covered area, icing area, low-visibility area, or strong crosswind area. If it is located in any of the hazardous weather areas, an additional coefficient greater than one is determined based on the weather intensity level. If the weather conditions are good, the additional impact coefficient is set to one. For example, a slight hazardous weather corresponds to 1.2 times, a moderate hazardous weather corresponds to 1.5 times, and a severe hazardous weather corresponds to 2.0 times. If multiple hazardous weather conditions exist simultaneously, the largest coefficient value is used. The impact score usually ranges from zero to one, with the value closer to one indicating a greater impact of the announcement on the flight.
[0010] When identifying affected operational elements in S4, it also includes identifying runway-level micro-meteorological differences; when the announcement's impact area involves an airport, it further obtains real-time meteorological observation data for different runways of that airport; if the crosswind or tailwind component of a runway exceeds the published limit value for that runway, the runway is identified as an affected operational element, and flights scheduled to use that runway are included in the list of affected flights; the impact level of such flights is scored by multiplying the original calculation by a micro-meteorological adjustment factor, such as 1.2 times, to reflect the additional risks brought about by runway-level differences.
[0011] The environmental scenario determination method in S5 is as follows: if the geographical location change rate of the receiving terminal is greater than the preset speed threshold and the device type is airborne equipment, it is determined to be a high-altitude flight scenario; the geographical location change rate is obtained by collecting location information twice consecutively and calculating the distance difference between the locations divided by the time interval; if the geographical location change rate of the receiving terminal is less than or equal to the preset speed threshold and the device type is a workstation, it is determined to be a ground operation control scenario; if the geographical location of the receiving terminal is within the geographical fence of the airport area and the device type is a mobile terminal, it is determined to be an airport on-site operation scenario.
[0012] The operation mode is determined as follows: when any one of the dangerous weather conditions such as thunderstorms, low visibility, strong crosswinds, or icing is present in the meteorological situation information, or when the length of the pending announcement queue in the system load status information exceeds the preset queue threshold, or when the number of flights monitored per person in the personnel work status information exceeds the preset number threshold, the system is determined to enter the abnormal operation mode; otherwise, it is determined to enter the normal operation mode.
[0013] The notification policy library in S5 stores differentiated notification policies for different environmental scenarios and operating modes; specifically including: In high-altitude flight scenarios and normal operation modes, the notification strategy is as follows: only high-priority notifications with an impact score higher than the first preset threshold are sent, the notification content adopts a concise summary format, the notification channel prioritizes air-to-ground data link communication, and the backup satellite communication short message is used. In high-altitude flight scenarios and abnormal operating modes, the notification strategy is adjusted as follows: the notification priority filtering threshold is increased to the second preset threshold, which is higher than the first preset threshold; at the same time, the notification content is further compressed into a key warning format, containing only the announcement type and core operation suggestions; and notification rate limiting rules are activated to limit the maximum number of notifications sent to the same recipient per unit time. In ground operation control scenarios and normal operation mode, the notification strategy is as follows: send notifications at all levels, use the full format for the notification content, use a combination of system interface pop-ups and instant messaging tools for the notification channels, and repeat notifications every five minutes until confirmed. In ground operation control scenarios and abnormal operation modes, the notification strategy is adjusted as follows: low and medium priority notifications are sent in batches, and multiple low and medium priority notifications are merged into a single summary notification at intervals of one aggregation time window before being sent; high priority notifications are sent immediately as single messages; additional meteorological situation information and personnel status reminders are added to the notification messages. In airport on-site operation scenarios and under normal operating conditions, the notification strategy is as follows: voice broadcasting is used as the main notification channel, and the notification content adopts a task-oriented format. In airport on-site operation scenarios and non-normal operation modes, the notification strategy is adjusted to: activate a combination of voice broadcast and strong vibration prompts; for announcement types that directly affect on-site operation safety, such as runway changes and ground operation restrictions, a location-triggered repeat notification function based on geofence is added, that is, when the recipient enters the runway or aircraft stand area affected by the announcement, a repeat notification is automatically triggered.
[0014] The selection of notification strategy in S5 is also affected by the weight of the recipient role; the system pre-configures priority weight coefficients for different recipient roles, and when the same announcement involves multiple recipients and system resources are limited, priority is given to ensuring the notification is sent to recipients with high weight coefficients.
[0015] The notification message in S6 also includes response action options, which include at least one of the following: confirm read, mark as important, forward to other recipients, and add a handling note. After the recipient provides feedback through the response action options, the system records the response behavior data.
[0016] The method also includes S7, feedback-driven continuous strategy optimization; collecting response behavior data from each receiver, including response latency, confirmation of read, and marked as key attention; periodically analyzing response performance indicators under different notification strategy combinations; and adjusting preset parameters in the notification strategy library based on the analysis results, including priority filtering threshold, aggregation time window length, and rate limiting threshold, to achieve closed-loop optimization of the strategy.
[0017] On the other hand, the present invention provides a system for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data, comprising: The data access module is used to configure data source adaptation parameters, establish data connection channels with various aviation bulletin publishing sources, and obtain raw aviation bulletin data from each data source according to a preset polling time interval.
[0018] The data parsing module, connected to the data access module, receives raw aviation announcement data, selects the corresponding parsing adapter based on the data source type for format parsing and field extraction, and maps the extracted fields to a unified announcement data model to generate standardized announcement data records. The data parsing module includes at least three of the following: HTML parsing adapter, PDF parsing adapter, XML parsing adapter, JSON parsing adapter, and structured database adapter.
[0019] The announcement database, connected to the data parsing module, is used to store standardized announcement data records, historical announcement data records, and change event records.
[0020] The situational awareness module is used to acquire current operational situational awareness information, which includes at least one of meteorological situation information, system load status information, and personnel work status information. The situational awareness module includes: a meteorological situation acquisition submodule, used to acquire real-time and forecast weather data from the meteorological data service interface; a system load monitoring submodule, used to monitor the system's own processing queue length, processor utilization, memory usage, network latency, and other indicators; and a personnel status acquisition submodule, used to acquire information such as the number of on-duty personnel, average monitoring load per person, and duty periods from the duty management system.
[0021] The monitoring frequency adjustment module, connected to the situation awareness module and the data access module, is used to assess the current operational risk level based on the operational situation awareness information and dynamically adjust the polling time interval of the data access module according to the operational risk level.
[0022] The change monitoring module is connected to the announcement database and is used to read historical announcement data records from the announcement database, compare them with newly generated standardized announcement data records, and generate change event records and store them in the announcement database when changes to announcement data are detected.
[0023] The impact assessment module, connected to the change monitoring module and the situation awareness module, is used to extract the impact range field from the change event record, identify the affected operational elements, parse out the list of affected flights, and calculate the impact degree score for each affected flight in combination with meteorological situation information.
[0024] The runway-level micro-meteorological correlation module, connected to the impact assessment module, is used to obtain real-time meteorological observation data for each runway of the airport. When the announcement of the impact range involves a certain airport, the meteorological conditions are compared with the runway operation restriction standards for each runway. Runways that exceed the restriction standards are marked as runways affected by micro-meteorology, and this information is provided to the impact assessment module to adjust the impact degree score of the affected flights.
[0025] The environment perception module is used to acquire the current operating environment information of the receiver and determine the environmental scene in which the receiver is located based on the operating environment information. The environment perception module includes: a location acquisition submodule, used to acquire the geographical location information of the receiver terminal and calculate the rate of change; a network detection submodule, used to acquire the network connection status of the receiver terminal; a device identification submodule, used to acquire the device type of the receiver terminal; and a status perception submodule, used to acquire the current working task status of the receiver.
[0026] The notification strategy module, connected to the environment perception module and the situation perception module respectively, is used to select the corresponding notification strategy from the preset notification strategy library based on the operating mode determined by the environmental scenario and operational situation perception information. The notification strategy module includes a notification strategy library, which stores notification strategies for six combinations of modes: normal mode for high-altitude flight scenario, abnormal mode for high-altitude flight scenario, normal mode for ground operation control scenario, abnormal mode for ground operation control scenario, normal mode for airport field operation scenario, and abnormal mode for airport field operation scenario. Each notification strategy includes notification channel combination, notification priority filtering rules, message simplification rules, repeated notification interval rules, and notification flow restriction rules.
[0027] The notification generation and sending module is connected to the impact assessment module and the notification strategy module, respectively. It is used to generate a notification message based on the impact score and the notification strategy, and send the notification message to the receiving terminal according to the notification channel combination specified by the notification strategy.
[0028] The feedback collection module, connected to the notification generation and sending module, is used to obtain feedback behavior data submitted by the recipient through response operation options and store the feedback behavior data in the announcement database.
[0029] The strategy optimization module, connected to the feedback collection module and the notification strategy module, is used to periodically analyze feedback behavior data and adjust the strategy parameters in the notification strategy library based on the analysis results.
[0030] The beneficial effects of this invention are as follows: 1. This invention achieves unified access and standardized processing of multi-source heterogeneous aviation bulletin data. Through the collaborative work of multiple parsing adapters, it can simultaneously monitor aviation bulletins from different issuing entities and with different data formats, providing wide coverage and strong compatibility. It also realizes adaptive adjustment of monitoring frequency based on dynamic situational awareness, which can adjust the polling monitoring interval in real time according to the severity of weather, system load pressure, and personnel workload. This saves system resources during normal operation and ensures high timeliness during abnormal operation, achieving dynamic matching between monitoring resources and operational risks.
[0031] 2. This invention achieves accurate assessment of the impact range of announcement changes by integrating meteorological conditions. It not only considers the temporal and spatial correlation between flights and announcements but also introduces an additional meteorological impact coefficient, making the impact score more reflective of actual operational risks. Simultaneously, it achieves fine identification of runway-level micro-meteorological differences, overcoming the shortcomings of traditional systems that cannot distinguish between different runway operating conditions within the same airport. Furthermore, it implements an adaptive notification strategy based on both environmental scenarios and operational modes. This strategy can dynamically switch notification strategy combinations according to normal and abnormal operational modes in three environmental scenarios: high-altitude flight, ground operation control, and airport on-site operations. Under extreme conditions, it automatically activates complementary mechanisms such as flow control, aggregation, and strong alerts, ensuring that critical information is not missed while preventing information overload.
[0032] 3. This invention establishes a feedback-driven strategy continuous optimization closed loop. By collecting data on the response behavior of the receiver, the notification strategy parameters are iteratively adjusted, enabling the system to continuously adapt to actual operational needs. For sudden severe weather processes and space weather events, the system significantly improves the reliability of information transmission under extreme conditions through rapid switching between high-frequency polling and continuous monitoring modes, as well as redundancy protection of the ground-to-air data link. Attached Figure Description
[0033] Figure 1 This is a schematic diagram of the overall architecture of the system of the present invention; Figure 2 This is a schematic diagram of the main flow of the method of the present invention; Figure 3 This is a schematic diagram of the dynamic monitoring frequency adjustment and situational awareness module structure. Figure 4 This diagram illustrates the matching of notification strategies under different environmental scenarios and operating modes. Detailed Implementation
[0034] To make the technical means, creative features, objectives and effects of this invention easier to understand, the invention will be further described below in conjunction with specific embodiments.
[0035] like Figures 1-4As shown, the present invention provides a method and system for monitoring and intelligently notifying changes to multi-source heterogeneous aviation bulletin data; Figure 1 The overall architecture of the system of the present invention is shown. The system includes a data access module, a data parsing module, an announcement database, a situational awareness module, a monitoring frequency adjustment module, a change monitoring module, an impact assessment module, a runway-level micro-meteorological correlation module, an environmental awareness module, a notification strategy module, a notification generation and sending module, a feedback collection module, and a strategy optimization module; the modules interact with each other through a standard data interface and work together to complete the entire process from data acquisition to intelligent notification. The data access module is responsible for establishing data connection channels with various aviation bulletin publishing sources. These sources include: the Civil Aviation Administration of China Air Traffic Management Bureau Information Center's bulletin publishing system, regional air traffic management bureau bulletin systems, airport operation bulletin platforms, airline operation control bulletin systems, and aviation meteorological service agency bulletin platforms. For different data sources, the data access module configures corresponding connection parameters, including data source address, interface type, authentication credentials, connection timeout, etc., and periodically retrieves raw aviation bulletin data from each data source according to the current polling interval specified by the module based on the monitoring frequency. For data sources that support proactive push, the data access module also maintains a message receiving endpoint to receive real-time pushed change data. The data parsing module connects to the data access module to receive raw aviation notice data; the data parsing module integrates various parsing adapters, such as... Figure 3 As shown. HTML parsing adapter 121 is used to parse announcement pages in web page format, locating and extracting announcement fields through a preset extraction path. The extraction path consists of a combination of the HTML element's tag name, attribute name, and attribute value; for example, specifying the div element's class attribute as "notice-title" to locate the announcement title. PDF parsing adapter 122 is used to parse announcement documents in PDF format, extracting announcement fields through preset area positioning. Area positioning is determined by a range of page numbers and coordinates, for example, page number 1, top-left corner coordinates 120 and 340, bottom-right corner coordinates 480 and 520. XML parsing adapter 123 is used to parse XML format message data. JSON parsing adapter 124 is used to parse JSON format API response data. Structured database adapter 125 is used to directly connect to a relational database to read announcement records.
[0036] All adapters map the extracted fields to a unified announcement data model, generating standardized announcement data records. The unified announcement data model includes the following fields: unique announcement identifier, announcement type (Notice to Airmen, Notice to Meteorologists, Notices to Airports, Notices of Information Revision, Notices to Airspace, Notices of Flight Changes, etc.), issuing agency, announcement date and time, effective date and time, expiration date and time, announcement title, announcement text, description of impact scope, priority level, status (in effect, pending effect, expired, withdrawn), data source identifier, and standardized processing time. This unified model provides a standardized data foundation for subsequent change monitoring and impact assessment.
[0037] The announcement database is implemented using a relational database and includes an announcement master table, a historical version table, and a change event table. The announcement master table stores the latest standardized announcement data records. The historical version table saves snapshots of each announcement's previous versions for change comparison. The change event table records details of each detected change event.
[0038] The structure of the situation awareness module is as follows: Figure 3 As shown, it includes three sub-modules: The meteorological situation acquisition sub-module acquires real-time and forecast weather data through a standard meteorological data interface, specifically including: thunderstorm coverage area (stored in latitude and longitude grid format), icing intensity level (light, moderate, severe), visibility value (in meters), cloud base height, crosswind component (in knots), tailwind component, runway visual range (RVR) value, temperature, air pressure, etc.; the meteorological data update frequency is 1 minute to 5 minutes, which can be dynamically adjusted according to the severity of the weather; The system load monitoring sub-module monitors the system's own operating status indicators in real time, including: the length of the pending announcement data queue (the number of currently accumulated unparsed raw data entries), processor usage ratio (percentage), memory usage ratio (percentage), network communication latency value (round-trip latency between various data sources, in milliseconds), announcement database write latency, etc.; The personnel status acquisition sub-module obtains information such as the number of dispatchers currently on duty, the number of air traffic controllers on duty, the number of flights monitored per person per seat, and the current duty period (daytime, nighttime, holidays) from the duty management module of the airline's operation control system.
[0039] The monitoring frequency adjustment module receives situational information from the situational awareness module and performs an operational risk level assessment. The assessment method is as follows: First, various situational indicators are compared with preset thresholds to obtain the meteorological situation risk level, system load risk level, and personnel status risk level. The meteorological situation risk judgment rules are as follows: If there is thunderstorm covering the operating area, or the icing intensity is moderate or above, or the visibility is lower than the Class I instrument landing system standard, or the crosswind component exceeds 15 knots, it is marked as high risk; if there is light icing, or the visibility is lower than the Class II instrument landing system standard but higher than the Class I standard, or the crosswind component is between 10 and 15 knots, it is marked as medium risk; the rest are low risk. The system load risk judgment rules are as follows: If the queue length of pending announcements exceeds 500, or the processor utilization rate continuously exceeds 85%, or the network latency exceeds 2000 milliseconds, it is marked as high risk; if the queue length is between 100 and 500, or the processor utilization rate is between 60% and 85%, it is marked as medium risk; the rest are low risk. The rules for judging the risk of personnel status are as follows: if the number of flights monitored per person exceeds the preset upper limit (30 flights per person during the day shift and 20 flights per person during the night shift), or the number of personnel currently on duty is lower than the minimum configuration requirement, it is marked as high risk; if the number of flights monitored per person is close to the upper limit, or it is in the second half of the night shift, it is marked as medium risk; the rest are low risk.
[0040] The overall risk level is determined by taking the highest of the three risk levels as the current operational risk level. Based on the overall operational risk level, the monitoring frequency adjustment module determines the current polling interval: at a low risk level, the basic polling interval remains at the first duration of 60 seconds; at a medium risk level, the polling interval is shortened to the second duration of 30 seconds; at a high risk level, the polling interval is further shortened to the third duration of 10 seconds, and a continuous monitoring mode for key announcement sources (such as navigation notices and weather warnings) is simultaneously initiated. The continuous monitoring mode is achieved by maintaining a long connection with the data source. Once the data source generates new data, it actively pushes it to the system, achieving a millisecond-level response.
[0041] The change monitoring module reads the latest historical version record of the current announcement from the announcement database and compares it field by field with the newly generated standardized announcement data record. The comparison dimensions include: announcement identifier (to determine whether it is new or already exists), announcement content (to determine whether there has been a substantial modification through text similarity comparison), announcement status, effective time, expiration time, description of the scope of impact, and priority level. When a new announcement, a substantial modification to the announcement content, or a change in the announcement status (such as changing from effective to expired or revoked) is detected, it is determined that an announcement data change event has occurred, and a change event record is generated. The fields of the change event record include: event unique identifier, announcement identifier, change type (new, modified, revoked, status change), changed field name, field value before change, field value after change, change occurrence time, and data source identifier.
[0042] For announcement sources with high update frequency (such as more than ten updates per hour), the change monitoring module also supports an event-triggered monitoring mechanism. When the data source actively pushes change messages through message queues or Webhook callbacks, the change monitoring module immediately responds and triggers a change monitoring process, without being limited by the polling time interval. This dual monitoring mechanism, which combines polling and event triggering, ensures both comprehensive coverage of regular monitoring and immediate response to high-frequency change sources.
[0043] The impact assessment module extracts the impact scope description field from the change event records and identifies the operational elements involved using natural language processing and rule matching techniques. The categories of operational elements include: airports (identified by four-letter ICAO codes), routes (identified by route codes), airspace (identified by airspace numbers), navigation facilities (identified by navigation beacon identifiers), runways (identified by runway numbers), and procedure types (such as standard instrument departure procedures, standard arrival procedures, and approach procedures). The impact assessment module further matches the identified operational elements with flight plans in the flight plan database: for airport elements, it matches the departure airport, arrival airport, and alternate airport in the flight plan; for route elements, it matches the waypoint sequence in the flight plan; for airspace elements, it matches the airspaces marked in the flight plan; and for runway elements, it matches the runways allocated for use in the flight plan. A list of affected flights is obtained upon successful matching.
[0044] For each affected flight, the impact assessment module calculates an impact severity score. The calculation process consists of three steps: The first step is to calculate the time overlap ratio. Read the scheduled departure and arrival times of the flight from the flight schedule to determine the flight's operating time period. Compare the flight's operating time period with the effective time period of the announcement. If the two time periods overlap, calculate the overlap duration (in minutes) and divide the overlap duration by the total effective time of the announcement (in minutes) to obtain the time overlap ratio. If there is no overlap, the time overlap ratio is zero. For example, if a flight's scheduled operating time is from 2 PM to 4 PM, and the announcement's effective time period is from 1 PM to 5 PM, the overlap duration is two hours (120 minutes), and the total effective time of the announcement is four hours (240 minutes). The time overlap ratio is 120 divided by 240, which equals 0.5. The second step is to calculate the degree of spatial correlation. This involves matching the operational elements the flight passes through with the operational elements within the scope of the announcement's influence. If all operational elements the flight passes through fall within the scope of the announcement's influence, the degree of spatial correlation is set to one. If there is partial overlap, the proportion of overlapping operational elements to the total number of operational elements within the scope of the announcement's influence is calculated; this proportion represents the degree of spatial correlation. If there is no overlap, the degree of spatial correlation is set to zero. For example, if the announcement's influence involves three airports and two air routes, and a flight plans to pass through two of these airports and one air route, the number of overlapping operational elements is three, and the total number of operational elements within the scope of the announcement's influence is five. The degree of spatial correlation is three divided by five, which equals 0.6. The third step is to obtain the meteorological additional impact coefficient. This involves acquiring gridded meteorological data for the current and forecast periods from the meteorological situation acquisition submodule, matching the latitude and longitude of the flight's planned waypoint with the meteorological grid, and identifying whether the waypoint is located in a thunderstorm coverage area, icing area, low visibility area, or strong crosswind area. If it is located in any of these hazardous weather areas, the additional impact coefficient is determined based on the weather intensity level: 1.2 times for mild hazardous weather, 1.5 times for moderate hazardous weather, and 2 times for severe hazardous weather. If multiple hazardous weather conditions exist simultaneously, the highest coefficient value is used. If the weather conditions are good, the additional impact coefficient is set to one. For example, if a flight waypoint is located in a moderate thunderstorm coverage area, the additional impact coefficient is 1.5. The fourth step is to multiply the time overlap ratio, spatial correlation degree, and additional impact coefficient to obtain the impact score. Using the example above, the time overlap ratio is 0.5, the spatial correlation degree is 0.6, and the additional impact coefficient is 1.5. Multiplying these three together gives 0.45. Theoretically, the score can exceed 1, but the system truncates it to the maximum value of 1. The closer the value is to 1, the greater the impact of the announcement on the flight.
[0045] The runway-level micro-meteorological correlation module works in conjunction with the impact assessment module. When the announcement of the impact area involves an airport, this module obtains real-time meteorological observation data for each runway of the airport through the airport's automatic weather observation system interface. For each runway, it compares its crosswind component, tailwind component, visibility, runway visual range, and other parameters with the published restriction standards for that runway. For example, if the crosswind restriction for a certain aircraft type is 15 knots, and the measured crosswind component of a certain runway reaches 18 knots, then that runway is marked as a runway affected by micro-meteorological conditions. When matching affected flights, the impact assessment module additionally filters out flights that plan to use the runway and applies a micro-meteorological adjustment coefficient to the impact score of these flights. Specifically, the original score is multiplied by 1.2 times the micro-meteorological adjustment coefficient. This runway-level fine-grained processing enables the system to discover differences in operating conditions between different runways at the same airport, providing dispatchers and flight crews with more accurate decision support.
[0046] The environmental perception module is responsible for obtaining the current operating environment information of the receiver; the location acquisition submodule 171 obtains the geographical latitude and longitude coordinates through the positioning system of the receiver terminal, and calculates the distance difference between two consecutive locations divided by the time interval to obtain the rate of change of geographical location; the network detection submodule 172 detects the network connection status and network quality of the receiver terminal by sending detection packets; the device identification submodule 173 determines the device type (airborne electronic flight bag, dispatch workstation, mobile handheld terminal, tablet computer, etc.) by reading the device identification information; the status perception submodule 174 obtains the current work task status (on duty, processing flights, idle, etc.) by interfacing with the business system of the receiver.
[0047] The environmental perception module determines the receiving environment based on the operating environment information, using the following rules: If the speed of change of geographical location is greater than a preset speed threshold (set to 300 kilometers per hour in this embodiment) and the device type is airborne equipment, it is determined to be a high-altitude flight scenario. If the speed of change of geographical location is less than or equal to the preset speed threshold and the device type is a workstation, it is determined to be a ground operation control scenario. If the location information is within the airport area's geofence and the device type is a mobile terminal, it is determined to be an airport on-site operation scenario.
[0048] The notification strategy module is connected to both the environmental perception module and the situational awareness module. The notification strategy module first obtains the environmental scenario from the environmental perception module, then obtains the current operational risk level from the situational awareness module, and determines the operational mode based on the operational risk level. The operational mode is determined as follows: if any of the hazardous weather conditions (thunderstorms, low visibility, strong crosswinds, or icing) are present in the meteorological situation information, or if the length of the pending announcement queue exceeds 500 items, or if the average number of flights monitored per person exceeds a preset upper limit, it is determined to be an abnormal operational mode; otherwise, it is determined to be a normal operational mode.
[0049] The notification strategy module contains a notification strategy library, which stores notification strategy configurations for six combined scenarios; Figure 4 It demonstrates the matching relationship of notification strategies under different environmental scenarios and operating modes, as well as the core elements of each strategy.
[0050] Combination 1: High-altitude flight scenario and normal operation mode; Notification strategy: Only send high-priority notifications with an impact score higher than the first preset threshold of 0.6; Notification content uses a concise summary format, with no more than 120 characters, including only the announcement type, affected airport or route, effective time, and core operational suggestions; The notification channel prioritizes air-to-ground data link communication, with satellite communication short messages as a backup. Repeated notifications are sent only once, without repeated pushes. Notification rate limiting is not enabled. Combination 2: High-altitude flight scenario and abnormal operation mode; the notification strategy is adjusted as follows: the notification priority filtering threshold is increased to the second preset threshold of 0.8, and only extremely high priority notifications are sent; the notification content is further compressed into a key warning format, with no more than 60 characters, containing only announcement type abbreviations and operation suggestion codes; the notification channel uses air-to-ground data link communication, while also sending backups through the airborne satellite communication backup link; the repetition interval is a single send, but if no confirmation receipt is received from the airborne equipment, it will be resent once after five minutes through the backup link; a notification flow limit rule is enabled, limiting the number of notifications received by a single aircraft to no more than five within ten minutes, and any excess notifications are put into a waiting queue and sent in order of priority; Combination 3: Ground operation control scenario and normal operation mode. The notification strategy is as follows: send notifications at all levels (high, medium, and low); the notification content uses a complete format, including a full summary of the announcement, detailed change instructions, a complete impact analysis, a list of affected flights, a link to the original announcement, and response options; the notification channels utilize both system interface pop-ups and enterprise instant messaging tools for simultaneous push notifications; the repeat notification interval is once every five minutes until the recipient confirms reading or manually closes the notification. Notification rate limiting is not enabled. Combination 4: Ground operation control scenario and non-normal operation mode; the notification strategy is adjusted as follows: high-priority notifications are sent immediately as a single message; medium-priority and low-priority notifications are sent in batches; the specific rules for batch aggregation are as follows: with a one-minute aggregation time window, all medium- and low-priority notifications arriving within the window are merged into a comprehensive announcement change summary notification. The summary notification lists the titles and brief descriptions of each announcement in descending order of impact, and provides links to the original text of each announcement; the notification channels remain the system interface pop-up and instant messaging tools; each notification message adds additional prompts on the current weather situation and personnel status reminders; regarding the interval of repeated notifications, high-priority notifications are repeated every three minutes until confirmed, while summary notifications are sent once every one aggregation time window without repeated reminders; this aggregation mechanism effectively reduces the number of notifications that the receiver needs to process per unit time, avoiding information overload; Combination 5: Airport on-site operation scenario and normal operating mode; Notification strategy: Only send high-priority and medium-priority notifications; Notification content adopts a task-oriented format, with the execution action as the core of the content, making it easy for frontline personnel to quickly understand and execute; Notification channels are primarily voice broadcasts, with mobile terminal notification bar push as a secondary channel; Repeat notifications are sent every two minutes until read confirmation is received. Notification rate limiting is not enabled; Combination Six: Airport on-site operation scenario and non-normal operating mode; The notification strategy is adjusted to: send high-priority notifications, and force the sending of key announcement types that directly affect on-site operation safety, such as those involving runway closure, ground equipment shutdown, and emergency rescue; The notification content adopts a task-oriented format and adds a warning prefix; The notification channel adopts a combination of voice broadcast and strong vibration prompts to ensure attention is drawn in noisy apron environments; At the same time, the location-triggered repeat notification function based on geofences is enabled, that is, when the system detects that a personnel terminal enters the preset electronic fence range around the runway or stand area affected by the announcement, the voice broadcast reminder is automatically triggered again; In the location-triggered mode, a reminder is triggered every time the fenced area is entered, with an interval of no less than 30 seconds; Regular repeat notifications are sent once every two minutes; In terms of notification flow control, the location-triggered repeat notification for the same type of announcement is limited to a maximum of five times per hour to prevent excessive disturbance.
[0051] The notification strategy module also considers the weight of the recipient role when selecting a notification strategy; the system pre-configures priority weight coefficients for different recipient roles, for example, the weight coefficient for the chief dispatcher is 1.5, the weight coefficient for the ordinary dispatcher is 1.0, and the weight coefficient for the assistant dispatcher is 0.8; when system resources are limited (such as message queue backlog in abnormal operation mode), notifications are sent in descending order of weight coefficients to ensure that key personnel receive information first.
[0052] The notification generation and sending module generates a notification message based on the impact score calculated by the impact assessment module and the notification strategy selected by the notification strategy module. The notification message includes an announcement summary, change description, impact range description, impact level (divided into high, medium, and low levels according to the score), additional tips related to the current weather situation (if applicable), a link to obtain the original announcement, and response operation options. The response operation options include confirming reading, marking as important, forwarding to other recipients, and adding handling remarks. The notification generation and sending module sends the notification message to the recipient terminal according to the channel combination and flow restriction rules specified by the notification strategy.
[0053] The feedback collection module is connected to the notification generation and sending module to obtain feedback behavior data submitted by the recipient through response operation options, including confirmation of read time, whether it is marked as important, forwarding target, and handling remarks, and stores the feedback behavior data in the feedback record table of the announcement database.
[0054] The strategy optimization module periodically (e.g., weekly) extracts and analyzes data from the feedback record table to calculate key performance indicators under different notification strategy combinations, including average response latency, confirmed read rate, and marked as key attention rate. Based on the analysis results, the strategy optimization module automatically or manually adjusts the preset parameters in the notification strategy library, such as appropriately lowering the priority filtering threshold in slow response scenarios or shortening the aggregation time window in high-frequency notification scenarios, to achieve continuous iterative optimization of notification strategies.
[0055] Figure 2 The main flow of the method of the present invention is shown; step S210 performs multi-source heterogeneous aviation notice data access and standardization processing; step S220 performs dynamic monitoring frequency adjustment; step S230 performs aviation notice data change monitoring and difference identification; step S240 performs notice change impact scope assessment; step S250 performs dynamic notification strategy generation; step S260 performs intelligent notification generation and sending; step S270 performs feedback collection and strategy optimization; the specific implementation details of each step have been described in detail in the above module descriptions.
[0056] Example 1: Scenario of concurrent processing of multiple announcements during thunderstorms At 2:00 PM on a certain day in July of a certain year, a sudden severe thunderstorm occurred at an airport and its surrounding area. At 2:05 PM, the meteorological department issued an airport warning, forecasting thunderstorms, strong wind shear, and low visibility at the airport. At 2:08 PM, the air traffic control bureau issued a NOTAM, initiating flow management procedures due to the thunderstorms, and adjusting the reception frequency for inbound flights to 20 flights per hour. At 2:12 PM, the airport operations department issued a gate adjustment notice, suspending the use of multiple remote gates due to strong winds. This scenario is a typical case of multiple concurrent announcements and high timeliness requirements. The dynamic collaborative working process of the various modules in this scenario is as follows: During the dynamic adjustment phase of the monitoring frequency; at 2 PM, the meteorological situation acquisition submodule detected thunderstorm echoes within a 50-kilometer radius of an airport from meteorological radar data, with an intensity level of strong; simultaneously, the system load monitoring submodule detected that the length of the pending announcement queue began to increase, rapidly climbing from the usual dozens of items to over 200; the personnel status acquisition submodule showed that there were currently 6 dispatchers on duty, and the number of flights monitored per person was approaching the upper limit; the monitoring frequency adjustment module comprehensively assessed the meteorological risk as high risk, the system load risk as medium risk, and the personnel status risk as medium risk, and determined the overall risk level to be high risk; the monitoring frequency adjustment module immediately adjusted the polling interval from 60 seconds to 10 seconds and started a continuous monitoring mode for the NOTAM and weather NOTAM sources; this adjustment ensured that the system could capture upcoming announcement changes as quickly as possible.
[0057] During the announcement data access and change identification phase, with the dual protection of high-frequency polling and continuous monitoring, the weather warning issued at 14:05, the traffic management announcement issued at 14:08, and the aircraft position adjustment announcement issued at 14:12 were all acquired by the data access module within 30 seconds of their release. The data parsing module selected the corresponding adapter according to each data source type to complete the parsing and standardization processing, generating 3 standardized announcement data records and sending them to the announcement database. The change monitoring module completed the comparison with the new records and historical versions within seconds, determined that all 3 records were new announcements, and generated 3 change event records, all of which were new.
[0058] The impact assessment module extracts the impact range of three announcements. For the traffic management announcement, the operational element is identified as the airport: ZBAA. After matching the flight schedule database, 78 inbound flights scheduled to use a certain airport between 14:00 and 18:00 are selected. The impact assessment module further obtains the additional meteorological impact coefficient from the meteorological situation acquisition sub-module: since the airport is located in a thunderstorm coverage area, the additional impact coefficient is set to 1.5.
[0059] Taking one flight, Flight No. 1, as an example, the calculation of the impact score is as follows: The flight's scheduled landing time is 14:30, and its flight period is from 13:50 to 14:30, overlapping with the announcement's effective period of 14:00 to 18:00; the overlap is 30 minutes, and the total effective period of the announcement is 240 minutes, so the time overlap ratio is 30 divided by 240, which equals 0.125; the flight uses a certain airport as its landing airport, so the spatial correlation value is 1; the additional impact coefficient is 1.5; multiplying these three factors, the impact score is 0.125 multiplied by 1 multiplied by 1.5, which equals 0.1875. Because the score is below 0.6, the flight is marked as having a medium impact level.
[0060] For another flight, Flight No. 2, the scheduled landing time is 15:00, and the flight period is from 14:20 to 15:00, which completely overlaps with the effective period of the announcement, with a time overlap ratio of 1. The spatial correlation is 1; the additional impact coefficient is 1.5. Multiplying the three factors together, the impact score is 1.5, and the cutoff is 1 (the highest impact level).
[0061] The runway-level micrometeorological correlation module obtains meteorological data for three runways at an airport from the automatic weather observation system: runway 36L has a crosswind component of 18 knots (exceeding the crosswind limit for this aircraft type by 15 knots), runway 36R has a crosswind component of 12 knots (within the limit), and runways 01 / 19 have a crosswind component of 9 knots. This module marks runway 36L as a runway affected by micrometeorological conditions. Based on this, the impact assessment module selects 12 flights scheduled to land on runway 36L and multiplies their impact score by a micrometeorological adjustment factor of 1.2. One flight, with an original score of 0.8, becomes 0.96 after multiplying by 1.2, thus being upgraded to a high-impact level.
[0062] During the dynamic notification strategy matching phase, the environmental perception module identifies the environmental scenarios of each recipient. Dispatcher A uses a dispatch workstation with a fixed geographical location, thus identifying it as a ground operations control scenario. Crew member C is operating flight number one, using an onboard electronic flight bag with a ground speed of approximately 850 km / h, thus identifying it as a high-altitude flight scenario. Maintenance guide D is holding a mobile terminal and is located in an airport apron area, thus identifying it as an airport on-site operations scenario.
[0063] The situational awareness module determines the current operational risk level to be high and the operational mode to be abnormal. The notification strategy module matches the strategy accordingly. Dispatcher A matches combination 4 (ground operations control plus abnormal), sending high-priority flow management announcements and weather alerts in full format immediately as a single message, while medium-priority gate adjustment announcements are aggregated into the window. Crew C matches combination 2 (high-altitude flight plus abnormal). The system detects that the impact score of a certain flight on flight number one is 0.1875, below the filtering threshold of 0.8, so no notification is sent. For a certain flight on flight number two (score 1), a critical warning message is generated and sent via ACARS. Maintenance guide D matches combination 6 (airport site plus abnormal), generating a voice broadcast notification and amplifying vibration alerts for gate adjustment announcements. When the guide approaches the affected gate area, a location trigger mechanism provides another reminder.
[0064] Feedback collection and strategy optimization phase; After the event, the feedback collection module statistics show that the average response delay of dispatcher A in the abnormal mode is 1.8 minutes, which is significantly better than the historical average of 4.5 minutes in the normal mode for this scenario; the arrival time of the ACARS message confirmation receipt of crew C is 35 seconds after sending; the strategy optimization module records the strategy performance parameters of this event to provide data support for parameter fine-tuning in similar scenarios in the future.
[0065] Example 2: Application Scenario of Runway-Level Micrometeorological Differences under Low Visibility Conditions This embodiment illustrates the specific role and value of the runway-level micrometeorological correlation module under low visibility conditions; Early one winter morning, radiation fog appeared at an international airport, causing a continuous decrease in visibility. The meteorological department issued a notice at 3:00 AM initiating low visibility operation procedures. The international airport has four runways. Runway 17L / 35R is equipped with a Category II Instrument Landing System, with a minimum runway visual range (MVL) requirement of 300 meters. Runway 17R / 35L is equipped with a Category I Instrument Landing System, with a minimum runway MVL requirement of 550 meters. Real-time data from the automatic weather observation system showed that the MVL of runway 17L was 400 meters, meeting the Category II operation standard; the MVL of runway 17R was 550 meters, which was at the critical value of the Category I operation standard.
[0066] After the system detects a low visibility notice, the change monitoring module generates a change event record; the impact assessment module extracts the impact range field and identifies the operational element as the airport: ZSPD; the runway-level micro-meteorological correlation module then obtains real-time meteorological data for each runway from the automatic weather observation system and compares the meteorological conditions with the operational restriction standards for each runway; the comparison results show that the visual range of runway 17L is 400 meters, which is greater than the 300-meter limit, and the operation is normal; the visual range of runway 17R is 550 meters, which is equal to the minimum limit, but considering that the visibility is still decreasing, the system marks it as a critical impact runway; the impact assessment module selects 8 inbound flights that plan to land on runway 17R and applies a micro-meteorological adjustment factor of 1.2 times to their impact score.
[0067] The notification messages for these flights included a clear additional message: Runway 17R's RVR is at the critical value of 550 meters and is showing a downward trend. Please confirm runway availability with air traffic control. After receiving the notification, the dispatchers coordinated with air traffic control in advance to divert six of the flights to land on Runway 17L to avoid go-arounds or diversions due to temporary runway closures or downgrades.
[0068] Experimental data shows that during the three-hour period of the low visibility event, a total of 86 flights were involved in the 17R runway. Among them, after the activation of the runway-level micro-meteorological correlation and advance notification mechanism, the actual number of diversions or go-arounds was only 2, a rate of only 2.3%. In contrast, according to statistics of similar low visibility events in the same period in history (without the activation of runway-level monitoring), the diversion and go-around rate of flights involving critical runways under similar conditions was approximately 15.1%. This comparison fully demonstrates the significant value of runway-level micro-meteorological difference identification and advance notification in improving operational safety and efficiency.
[0069] Example 3: System Response Scenario under Space Weather Events This embodiment illustrates the system's ability to respond to the impact of space weather, an area that is generally neglected by existing aviation notice systems; A solar flare event triggered a geomagnetic storm, prompting the Space Weather Warning Center to issue an aviation space weather notice, warning that flights passing through the Arctic route may experience GPS signal degradation and satellite communication interruptions. The notice was effective from 10:00 to 16:00 on the same day, and the affected area was the polar route region north of 60 degrees north latitude.
[0070] After the situational awareness module obtains the early warning information from the space weather data interface, the meteorological situation acquisition submodule marks the space weather type as severe and the impact level as high risk; the monitoring frequency adjustment module immediately raises the comprehensive risk level to high risk, shortens the polling interval to ten seconds, and starts continuous monitoring of the space weather notification source.
[0071] The impact assessment module extracts the impact range field from the announcement and identifies the operational element as airspace: the Arctic route from 60 degrees north latitude. After matching with the flight schedule database, it selects a total of twelve flights scheduled to fly over this area between 10:00 and 16:00. When the impact assessment module calculates the impact score for these flights, it sets the additional impact coefficient to 2.0 (severe risk level), so that the impact score of all involved flights reaches or exceeds 0.9, and all are marked as high impact level.
[0072] In high-altitude flight scenarios, due to the activation of abnormal operating modes, the notification strategy module matches and combines two strategies; the system generates key warning format notification messages for these twelve flights, the content of which is a space weather warning and the possibility of GPS degradation in polar routes, which is sent through the ACARS ground-to-air data link; at the same time, the system sends backup notifications through satellite communication backup links to ensure that at least one link can be successfully delivered.
[0073] In ground operation control scenarios, after receiving a high-priority notification, dispatchers immediately assess the backup plan for voice communication in the event of satellite communication interruption, including high-frequency voice communication frequencies and backup satellite phone numbers. The system adds suggested operation options to the notification message, and dispatchers can confirm the backup plan with one click.
[0074] Thanks to early warnings and thorough preparations, all affected flights completed navigation equipment checks and communication plan confirmations before entering the affected area. No route deviations or communication interruptions due to loss of GPS signals occurred during the entire event. This embodiment demonstrates the effective coverage capability of the present invention for low-frequency but high-risk events.
[0075] To verify the actual effect of the technical solution of the present invention, a systematic comparative experiment was designed and implemented, focusing on verifying the comprehensive performance of dynamic monitoring frequency adjustment, meteorological situation fusion assessment, adaptive notification strategy, and runway-level micrometeorological correlation under different operating conditions. Experimental Environment: The system of this invention was set up in the test environment of an airline's operation control center. The hardware configuration consisted of an 8-core CPU, 64 gigabytes of memory, and 2 terabytes of storage. The data source was configured to access six real aviation announcement sources: the Civil Aviation Administration of China Air Traffic Management Bureau Information Center Announcement System (HTML format), two regional air traffic management bureau announcement systems (XML format), a large airport operation announcement platform (JSON format), an aviation meteorological service agency (PDF format), and a space weather forecasting center data interface (XML format). The experimental period was 60 consecutive days, covering one complete peak period of the thunderstorm season. Comparison of solutions: Solution A adopts the complete system of this invention, including all features such as dynamic monitoring frequency adjustment, meteorological additional impact coefficient, runway-level micro-meteorological correlation, and operation mode switching; Solution B adopts the basic version of this invention, but disables situational awareness-driven monitoring frequency adjustment (fixed 60-second polling), disables meteorological additional impact coefficient (only calculates the degree of impact based on time and space), and disables operation mode switching (only retains three basic environmental scenario notification strategies); Solution C adopts the traditional email subscription plus RSS subscription method.
[0076] Evaluation indicators include: (1) Delay time for discovering announcement changes during peak hours; peak hours are defined as periods when the number of announcement changes exceeds fifty per hour. Record the time difference from the actual publication of the announcement to its discovery by the system or personnel, in minutes; (2) Accuracy of impact rating under different weather conditions; Based on the evaluation results of an expert group consisting of three senior dispatchers and two meteorological experts after the fact, the matching rate between the high-impact flight list given by the system and the actual high-risk flight list identified by the experts was calculated; The matching rate was calculated by dividing the number of high-risk flights correctly identified by the system by the total number of high-risk flights identified by the experts. (3) Notification delivery success rate under abnormal operating mode; Abnormal operating mode includes conditions such as thunderstorms, low visibility, strong crosswinds, and high load; The delivery success rate is calculated by dividing the number of notifications successfully delivered to the receiving terminal by the total number of notifications sent. (4) Receiver response delay time in abnormal operation mode; the time starts from when the notification is successfully delivered to the receiver terminal and ends when the receiver clicks to confirm that it has been read, in minutes; (5) Information overload suppression effect; measured by the number of notifications actually received by the receiver per unit time, the aggregation ratio of low and medium priority notifications, the confirmation read ratio of notifications of each priority, and the dispatcher's subjective information overload score (1 to 5 points, 5 points indicates severe overload).
[0077] (6) Effectiveness of runway-level micrometeorological correlation. The diversion and go-around rate of flights involving runways affected by micrometeorology is used as the metric; the diversion and go-around rate is calculated by dividing the actual number of diverted or go-around flights by the total number of flights involving runways affected by micrometeorology.
[0078] During the experiment, a total of 3,826 aviation notices were issued from the six data sources; among them, 1,652 were NOTAMs, 1,038 were meteorological notices, 744 were airport notices, 258 were airspace notices, and 134 were other types. The total duration of thunderstorms was 120 hours, the duration of low visibility was 58 hours, and there were 2 space weather warnings.
[0079] Table 1 Comparison of delays in the discovery of announcement changes during peak hours.
[0080] Data explanation in the table: Peak hours refer to periods when the number of change announcements exceeds 50 per hour. During the experimental period, there were 42 peak hours, with a total of 1856 change announcements. The average detection latency for Scheme A is calculated by summing the detection latency times of all successfully detected changes and dividing by the total number of detected changes. The average latency for Scheme A is 0.9 minutes, for Scheme B it is 6.4 minutes, and for Scheme C it is 15.8 minutes. Scheme A achieves sub-minute detection during peak hours, mainly due to the dynamic adjustment mechanism of the monitoring frequency, which shortens the polling interval to 10 seconds and initiates continuous listening at high-risk levels. Scheme B, due to its fixed 60-second polling, is prone to queue backlog during periods of dense announcement release, leading to a significant increase in latency. Scheme C, limited by the email server push cycle and RSS refresh interval, has the highest latency.
[0081] Table 2 Comparison of accuracy rates for impact severity scoring under different meteorological conditions
[0082] The data in the table explains: the actual number of high-risk flights was determined by a post-event assessment by an expert group; the accuracy of Scheme A was calculated as the number of high-risk flights identified by Scheme A divided by the actual number of high-risk flights; Scheme A, by introducing a meteorological additional impact coefficient, can more accurately identify flights affected by the combined effects of severe weather and announcements; for example, in space weather events, Scheme B can only identify flights whose routes overlap with the announcement area, and cannot determine the actual impact of space weather on navigation and communication, with an accuracy of only 50%; Scheme A accurately marked the vast majority of high-risk flights through the additional impact coefficient; overall, Scheme A achieved an accuracy of 94.5%, significantly better than Scheme B's 75.4%.
[0083] Table 3 Comparison of notification delivery success rates in different environmental scenarios under abnormal operating conditions
[0084] The data in the table illustrates the following: During the abnormal operation mode, a total of 2,626 notifications were sent; Solution A, in high-altitude flight scenarios, activated backup satellite communication links and notification flow control mechanisms, achieving a delivery success rate of 94.4%, a significant improvement compared to Solution B's 79.5%; Solution B, in high-altitude scenarios, still used a single internet push channel, resulting in a lower delivery rate when the network was unstable during flight; In airport on-site operation scenarios, Solution A adopted a combination of voice broadcasts with enhanced vibration and location-triggered repetitive reminders, increasing the success rate from Solution B's 88.8% to 97.2%; In ground scenarios, the difference between the two was small, but Solution A, by aggregating notifications to reduce network load, still maintained a slightly higher success rate.
[0085] Table 4 Comparison of receiver response delay time under abnormal operating conditions (unit: minutes)
[0086] The data in the table explains: the response latency starts when the notification is successfully delivered to the recipient's terminal and ends when the recipient clicks to confirm that it has been read; the average response latency is calculated by summing the response latency times of all confirmed notifications and dividing by the number of confirmed notifications; in abnormal operating mode, Scheme A uses a targeted combination of notification strategies, with an average response latency of 2.2 minutes, which is nearly half of the 4.3 minutes of Scheme B; the non-response rate also decreased from 4.5% to 1.1%; in high-altitude flight scenarios, Scheme A's simplified message format and flow control mechanism effectively reduce the cognitive burden on the crew to read and process notifications, reducing the response latency from 5.8 minutes to 2.1 minutes.
[0087] Table 5. Information overload suppression effect under abnormal operating mode
[0088] The data in the table illustrates that: Solution A, through an aggregation notification mechanism, aggregates 62.3% of the low-to-medium priority notifications in the ground operation control scenario into a summary notification, reducing the average number of notifications received per dispatcher per hour from 67.2 to 28.4. After aggregation, the confirmation read rate of high-priority notifications remains high at 96.8%, while the confirmation read rate of low-to-medium priority notifications also increases from 52.1% to 78.5%. The dispatcher's subjective information overload score was obtained through a questionnaire survey after the experiment, with 1 point indicating no overload and 5 points indicating severe overload. Solution A scored 2.1 points, indicating slight overload, while Solution B scored 4.3 points, indicating significant overload. This demonstrates that the aggregation and rate limiting mechanisms effectively alleviate the information overload problem under abnormal operation modes.
[0089] Table 6. Validation of runway-level micrometeorological correlations
[0090] The data in the table are explained as follows: 86 flights involving runways affected by micrometeorological conditions under low visibility and strong crosswind conditions were selected for comparative analysis; data without runway-level correlation were derived from historical operational statistics under similar meteorological conditions during the same period; with runway-level correlation enabled, the system identified critical runways in advance and notified dispatchers and crews to coordinate runway changes, resulting in only 2 diversions or go-arounds, a diversion / go-around rate of 2.3%; without runway-level correlation, due to the lack of early warning of runway-level differences, flights typically only discovered runway conditions were unacceptable during the approach phase, leading to go-arounds or diversions, a rate of 15.1%; the runway-level micrometeorological correlation function reduced the diversion / go-around rate by approximately 85 percentage points, demonstrating the significant safety benefits and operational efficiency improvements brought about by refined monitoring.
[0091] Comprehensive experimental results show that, based on the unified monitoring of multi-source heterogeneous aviation notices, the technical solution of this invention, by incorporating a dynamic adjustment mechanism driven by operational situational awareness, meteorological fusion impact assessment, runway-level micro-meteorological identification, and an adaptive notification strategy encompassing both environmental and operational modes, demonstrates significantly superior performance compared to existing technologies under various operational conditions. Its advantages are particularly pronounced under extreme weather and high-load, abnormal conditions. Furthermore, the collaborative work among the system's modules forms a complete closed loop from data acquisition and risk identification to impact assessment and intelligent notification, demonstrating excellent technical effectiveness and practical application value.
[0092] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of the present invention is defined by the appended claims and their equivalents.
Claims
1. A method for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data, characterized in that, Includes the following steps: S1. Configure data source adaptation parameters and establish data connection channels with various aviation announcement publication sources; According to the preset basic polling time interval, the system obtains raw aviation bulletin data from various data sources, selects the corresponding parsing adapter according to the data source type, performs format parsing and field extraction on the raw data, maps the extracted fields to a unified bulletin data model, generates standardized bulletin data records, and stores them in the bulletin database. S2. Obtain current operational situation awareness information, which includes at least one of meteorological situation information, system load status information, and personnel work status information; assess the current operational risk level based on the operational situation awareness information. When the operational risk level increases, shorten the polling interval to increase the monitoring frequency; when the operational risk level decreases, restore or extend the polling interval to reduce system resource consumption. S3. Read historical announcement data records from the announcement database and compare them with the newly generated standardized announcement data records in S1. The comparison dimensions include announcement identifier, announcement content, announcement status, effective time, expiration time, scope of impact, and priority level. When any of the following situations are detected: new announcement, modified announcement content, changed announcement status, or revoked announcement, it is determined that an announcement data change event has occurred, and a change event record is generated. S4. Extract the impact range field from the change event record to identify the affected operational elements, including airports, air routes, airspace, navigation facilities, runways, and procedure types; match the operational elements with flight plans to obtain a list of affected flights; calculate the impact score for each affected flight; the impact score is determined based on the degree of overlap between the flight and the effective time of the announcement, the spatial correlation between the flight and the impact range of the announcement, and the additional impact coefficient of the current weather situation on the flight operation. S5. Obtain the receiver's current operating environment information, which includes at least one of the receiver's geographical location, network connection status, device type, and current work task status; determine the receiver's environmental scenario based on the operating environment information, including high-altitude flight scenario, ground operation control scenario, and airport on-site operation scenario; obtain current operating situation awareness information, and determine the current operating mode based on the operating situation awareness information, including normal operating mode and abnormal operating mode; for different combinations of environmental scenarios and operating modes, select the corresponding notification strategy from the preset notification strategy library, which includes notification channel combination, notification priority filtering rules, message simplification rules, repeated notification interval rules, and notification rate limiting rules; S6. Generate a notification message based on the impact score determined in S4 and the notification strategy selected in S5; The notification message includes an announcement summary, a description of the changes, a description of the scope of impact, a level of impact, additional tips related to the current weather situation, and a link to access the original announcement. The notification message is sent to the receiving terminal according to the notification channel combination and notification flow restriction rules specified in the notification strategy.
2. The method for monitoring and intelligently notifying changes to multi-source heterogeneous aviation bulletin data according to claim 1, characterized in that, In S1, for HTML webpage-type announcement sources, an extraction path consisting of HTML element tag names, attribute names, and attribute values is used to locate and extract announcement fields; for PDF document-type announcement sources, a region-based location determined by page number range and coordinate range is used to extract announcement fields.
3. The method for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data according to claim 1, characterized in that, The meteorological situation information mentioned in S2 includes at least one of the following: weather phenomenon type, thunderstorm coverage area, icing intensity level, visibility value, crosswind component value, and runway visual range value; the system load status information includes at least one of the following: length of pending announcement queue, processor occupancy ratio, and network communication latency value; the personnel work status information includes at least one of the following: number of on-duty personnel and number of flights monitored per person; the assessment method for the operational risk level is as follows: the meteorological situation information, system load status information, and personnel work status information are matched with preset threshold intervals respectively, and comprehensively determined into three risk levels: low, medium, and high; the polling interval remains at the first duration for low risk, shortens to the second duration for medium risk, and further shortens to the third duration for high risk, and initiates a continuous monitoring mode for key announcement sources.
4. The method for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data according to claim 1, characterized in that, The impact score in S4 is calculated by obtaining the planned flight time of the flight during the effective period of the announcement and comparing it with the total effective period of the announcement to obtain the time overlap ratio. To determine the spatial correlation between flights and the scope of impact of announcements; Obtain the additional impact coefficient of the current weather situation on flight operations. The additional impact coefficient is determined based on the type and intensity level of weather phenomena in the area through which the flight is scheduled to pass. The degree of influence is scored by multiplying the proportion of time overlap, the degree of spatial correlation, and the coefficient of additional influence.
5. The method for monitoring and intelligently notifying changes in multi-source heterogeneous aviation bulletin data according to claim 4, characterized in that, S4 also includes runway-level micro-meteorological difference identification: when the scope of the announcement involves an airport, it obtains real-time meteorological observation data of each runway of that airport; If the crosswind or tailwind component of a runway exceeds the published limit for that runway, the runway will be marked as an affected operational element, and flights scheduled to use that runway will be included in the list of affected flights. At the same time, a micro-weather adjustment factor will be applied to the impact score of the corresponding flights.
6. The method for monitoring and intelligently notifying changes to multi-source heterogeneous aviation bulletin data according to claim 1, characterized in that, The environmental scenario determination method in S5 is as follows: if the geographical location of the receiving terminal changes faster than a preset speed threshold and the device type is airborne equipment, it is determined to be a high-altitude flight scenario. If the rate of change is less than or equal to a preset threshold and the device type is a workstation, it is determined to be a ground operation control scenario. If the location is within the airport area and the device type is a mobile terminal, it is determined to be an airport on-site operation scenario. The operating mode is determined as follows: when any of the following weather conditions are present in the meteorological situation information: thunderstorms, low visibility, strong crosswinds, or icing; or when the length of the pending announcement queue of the system load exceeds a preset threshold; or when the average number of flights monitored per person exceeds a preset threshold, it is determined to be an abnormal operating mode; otherwise, it is a normal operating mode.
7. The method for monitoring and intelligently notifying changes to multi-source heterogeneous aviation bulletin data according to claim 6, characterized in that, The notification strategy library in S5 has different notification strategies for different storage combinations: in the normal mode of high-altitude flight scenarios, only high-priority notifications are sent, a simplified digest format is used, and ground-to-air data link communication is prioritized. In abnormal high-altitude flight scenarios, priority filtering thresholds are adjusted, key warning formats are adopted, and notification rate limiting is enabled. In the normal mode of ground operation control scenarios, all levels of notifications are sent, using the complete format, a combination of system pop-ups and instant messaging; In the abnormal mode of ground operation control scenario, low- and medium-priority notifications are sent in batches and high-priority notifications are sent immediately and individually, with additional prompts for weather and personnel status. In normal airport on-site operation scenarios, voice broadcasting and task-oriented formats are used. In abnormal operation scenarios at airport sites, a combination of voice broadcasting and strong vibration is enabled, and geofence-based location-triggered repeat notifications are initiated for key announcement types.
8. A system for monitoring and intelligently notifying changes to multi-source heterogeneous data in aviation bulletins, applicable to the method for monitoring and intelligently notifying changes to multi-source heterogeneous data in aviation bulletins as described in any one of claims 1-7, characterized in that, include: The data access module is used to establish data connection channels with various aviation bulletin publication sources and obtain raw aviation bulletin data at polling intervals. The data parsing module is used to select a parsing adapter based on the data source type to perform format parsing and field extraction, and generate standardized announcement data records; The announcement database is used to store standardized announcement data records, historical announcement data records, and change event records; The situation awareness module is used to acquire operational situation awareness information, including meteorological situation information, system load status information, and personnel work status information. The monitoring frequency adjustment module is connected to the situational awareness module and the data access module. It is used to assess the operational risk level based on the operational situational awareness information and dynamically adjust the polling time interval. The change monitoring module is used to compare historical announcement data records with newly generated standardized announcement data records and generate change event records. The impact assessment module, connected to the change monitoring module and the situation awareness module, is used to extract the impact range field, identify affected operational elements, match the list of affected flights, and calculate the impact degree score in combination with meteorological situation information. The environmental perception module is used to acquire information about the receiver's operating environment and determine the environmental scene in which it is located. The notification strategy module, connected to the environment perception module and the situation perception module, is used to determine the operating mode based on the environmental scenario and the operational situation perception information, and to select a notification strategy from the preset notification strategy library based on the environmental scenario and the operating mode. The notification generation and sending module, connected to the impact assessment module and the notification strategy module, is used to generate notification messages based on the impact score and notification strategy, and send them to the receiving terminal according to the strategy.
9. The aviation bulletin board multi-source heterogeneous data change monitoring and intelligent notification system according to claim 8, characterized in that, The data parsing module includes at least three of the following: HTML parsing adapter, PDF parsing adapter, XML parsing adapter, JSON parsing adapter, and structured database adapter; The environment perception module includes a location acquisition submodule, a network detection submodule, a device identification submodule, and a status perception submodule; The situation awareness module includes a meteorological situation acquisition submodule, a system load monitoring submodule, and a personnel status acquisition submodule.
10. The aviation bulletin multi-source heterogeneous data change monitoring and intelligent notification system according to claim 8, characterized in that, It also includes a runway-level micro-meteorological correlation module, which is connected to the impact assessment module to obtain real-time meteorological observation data of each runway of the airport. When the announcement of the impact range involves a certain airport, the meteorological conditions are compared with the runway operation restriction standards for each runway. Runways that exceed the restriction standards are marked as runways affected by micro-meteorology and fed back to the impact assessment module. It also includes a feedback collection module and a strategy optimization module. The feedback collection module is used to obtain the response behavior data of the recipient, and the strategy optimization module is used to adjust the strategy parameters in the notification strategy library based on the analysis results of the response behavior data.
Citation Information
Patent Citations
Navigation announcement intelligent analysis method based on large language model
CN122046060A
Response method and system for aviation ticket meteorological risk
CN122133850A
