Implementation method for constructing micro-service architecture air traffic control automatic display system

Abstract

The invention discloses an implementation method for constructing an air traffic control automatic display system of a micro-service architecture, an SDD system based on the micro-service architecture is constructed by introducing Golang, WebGL and React technologies, the system specifically comprises a software engine, a Golang programming language and the micro-service architecture, the software engine is responsible for acquiring, processing and displaying management data; through a plug-in mechanism, a user can quickly expand functions of a software engine according to requirements, and different data sources and function modules are supported; according to the method, high customization is supported, and a user can flexibly configure interface layout and display different data and graphs through modular design, so that the method adapts to the difference of air traffic control requirements of various regions; and by utilizing 2D / 3D hardware acceleration rendering supported by WebGL, visual and smooth data display is provided for an administrator, and the information acquisition efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of microservice architecture, and in particular to an implementation method for constructing an air traffic control automation display system with a microservice architecture. Background Art

[0002] In the field of air traffic control, the display terminal subsystem (Situational Data Display System, SDD system for short) of the automation system, as a human-machine interface, is the core tool for controllers to monitor data and perform command operations. With the rapid development of global air transportation and the continuous growth of civil aviation business volume, the requirements of air traffic control units in various regions for SDD systems are gradually increasing, showing obvious personalized needs.

[0003] The traditional SDD system interface is usually based on a fixed layout, with only a few movable windows to adjust the display area. Controllers need to obtain track, weather and other data in a fixed interface, and this design is unable to cope with diverse needs.

[0004] Secondly, since each client needs to be installed separately, the maintenance process is complicated, which increases the operation and maintenance burden. At the same time, as the system scale grows, the system's failure points also increase.

[0005] In addition, traditional systems are difficult to adapt to cloud-native environments, making it difficult to achieve rapid fault recovery, smooth system deployment and centralized management. They also do not have the statistical and big data storage capabilities that are advantages of cloud platforms, which greatly affects the scale expansion of the system.

[0006] Therefore, the main problems of existing SDD systems include:

[0007] ① Insufficient customization, unable to meet diverse needs;

[0008] ②Poor scalability, unable to flexibly add new functions;

[0009] ③ Incompatibility with cloud platforms limits the system’s deployment flexibility and resource utilization;

[0010] ④ The operation and maintenance costs are high, and terminal deployment and updates are time-consuming and labor-intensive.

[0011] To this end, the present invention proposes an implementation method for constructing an air traffic control automation display system with a microservice architecture. Summary of the invention

[0012] In view of the defects in the prior art, the present invention provides a method for implementing an air traffic control automation display system based on a microservice architecture. By introducing Golang, WebGL, and React technologies, an SDD system based on a microservice architecture is constructed, which specifically includes a software engine, a Golang programming language, and a microservice architecture, wherein:

[0013] Software Engine:

[0014] The software engine is responsible for managing the acquisition, processing and display of data; through the plug-in mechanism, users can quickly expand the functions of the software engine according to their needs, supporting different data sources and functional modules. The software engine includes a data source engine, a data display engine, an alarm engine, a user interaction engine and a log recording engine;

[0015] Microservices Architecture:

[0016] The microservice architecture splits the application into multiple small services, each of which is responsible for a specific functional module, including data acquisition, data processing, and data display;

[0017] Use a unified interface for communication to achieve interaction and data transfer between services;

[0018] Manage and deploy microservices based on orchestration tools; process high-concurrency requests through load balancers;

[0019] The SDD system implements data visualization based on the WebGL library; improves the performance and fluency of data rendering based on WebGL hardware acceleration; processes data based on the parallel computing capability of GPU; and uses React components to encapsulate WebGL rendering logic to achieve separation of front-end and back-end and modular development.

[0020] Preferably, the data source engine is an engine that reads required regulatory data from a specific database through user-defined data source parameters.

[0021] Preferably, the data source engine is specifically implemented in the following steps:

[0022] S1: Configuration management, users enter data source parameters through configuration files or interfaces, including database type, host address, port number, user name, password, and specific query statements;

[0023] S2: Connection establishment: According to the parameters provided by the user, the data source engine establishes a connection with the target database based on the database driver;

[0024] S3: Data reading. Once the connection is established successfully, the data source engine executes the query statement provided by the user to obtain data.

[0025] S4: Data processing, including data cleaning, format conversion, and aggregate computing operations.

[0026] Preferably, the data display engine displays the processed data in a visual manner, supports customized overall layout, geographic data display, track symbol display and visualization of other data; the specific implementation steps are as follows:

[0027] Configuration management: The data display engine implements configuration management based on the display parameters entered by the user through the configuration file or interface, including layout settings, color schemes, and font sizes;

[0028] Geographic data display: The data display engine statically displays points, lines and surfaces on the base of the global map to display the aerial map; loads and renders map data based on geographic information system technology;

[0029] Dynamic display of track symbols: Use the WebGL library to dynamically display track symbols;

[0030] Other data visualization: Use ECharts for other data visualization displays.

[0031] Preferably: the alarm engine provides the function of customizing user alarm type, alarm duration and alarm display mode;

[0032] The implementation method of the alarm engine includes:

[0033] Alarm type definition: The alarm engine is based on user-defined alarm types, each type corresponds to a specific monitoring condition or event; the user enters the name and triggering condition of the alarm type through the configuration file or interface;

[0034] Alarm rule configuration: For each alarm type, users configure specific triggering rules; the rules include threshold judgment and the number of event occurrences within the time window;

[0035] Alarm triggering mechanism: The alarm engine monitors the data stream provided by the data source engine in real time, and analyzes whether the data meets the triggering conditions according to the preset alarm rules; once an event that meets the conditions is detected, an alarm message is immediately generated;

[0036] Alarm duration management: Users set different durations for each alarm type; the alarm duration determines how long an alarm will be displayed before being cleared; the alarm engine tracks the start time and duration of each alarm, and automatically clears expired alarms after a specified time;

[0037] Alarm display mode: including pop-up window prompt, sound alarm, LED indicator flashing;

[0038] Alarm priority management: Users can assign different priority levels to each alarm type based on the importance of the alarm, and high-priority alarms will be displayed first;

[0039] Alarm record and query: All generated alarm information is recorded in the log system; the alarm record includes the alarm type, trigger time, duration, and display mode; users retrieve historical alarm records through the query interface provided by the log recording engine.

[0040] Preferably: the data source engine: uses golang to implement expansion using plug-ins, and the architecture of the data source engine includes: JS / TS parsing engine, React component engine;

[0041] The implementation steps of the data source engine are:

[0042] S1: Use Golang to build the backend TypeScript / JavaScript engine, and preliminarily build the framework of the data source engine in the form of interfaces and classes;

[0043] S2: defines the common interface of data source objects;

[0044] S3: Use the React component engine to define the representation interface of the data source plug-in on the interface.

[0045] Preferably: the data display engine, its architecture includes a canvas drawing engine, a React component engine, a data conversion module and a visualization customization module;

[0046] The implementation steps are:

[0047] S1: First, the control data is input into the data conversion module for conversion, and the longitude and latitude coordinates in the geographic data and track data are converted into rectangular coordinates;

[0048] S2: Convert the speed and altitude information in the track data into a sign with a preset color, and then deliver it to the canvas drawing engine for drawing;

[0049] S3: The drawing engine draws visible layers with user-defined colors and icon elements according to a custom drawing profile written by the user.

[0050] Preferably: the alarm engine comprises: an alarm rule parsing module, an alarm judgment module, an alarm message generating module, and an alarm routing module;

[0051] Among them: the alarm rule parsing module parses the external alarm rule script into alarm rules and alarm routing tables; the scope of the alarm rules includes track position alarms, specific secondary code alarms, and the alarm routing table specifies which subsystems or modules the alarm messages are sent to.

[0052] Preferably: the user interaction engine comprises: a custom interface script parsing module, a custom event script parsing module, an event processing module, and a display engine interface;

[0053] The user interaction engine reads external scripts, decomposes custom events and custom interface scripts from them, parses them separately, sends the custom interface rules to the display engine through the display engine interface, generates custom controls through the React component engine, and binds custom control events; at the same time, the custom control event rules are sent to the event processing module for calling.

[0054] Preferably: the log recording engine comprises: a log rule parsing module, a log message generating module, a log database, and a log query module;

[0055] The logging engine works by:

[0056] S1: Read the log rule configuration file at startup, and generate log rules through the parsing module, waiting for the log message generation module to call;

[0057] S2: Other modules in the system generate logs that comply with log rules by calling the external interface of the log message generation module, and write logs through the log database operation module;

[0058] S3: Log generation module, which collects logs from other subsystems at regular intervals, parses them according to built-in rules, and writes them into the log database;

[0059] S4: The user enters conditions to query the log on the interface, and the data display engine calls the log query interface and displays the returned query results.

[0060] Preferably, the process of the SDD system is divided into the following stages:

[0061] S1: Set the data source. First, select the data source of the monitoring system;

[0062] S2: Set the display interface. Based on the default interface, the display interface is built by setting rules and configurations.

[0063] S3: Set alarm rules and customize the alarm engine by setting configuration files;

[0064] S4: Set interaction rules. Customize interaction rules by setting interaction scripts.

[0065] S5: Set log rules, set the format and content of output logs by setting log templates;

[0066] S6: Start the trial run. If there is any problem during the trial run, modify the specific module configuration through S1-S5 and continue to use it after the problem is solved.

[0067] The beneficial effects of the present invention are embodied in:

[0068] 1. The present invention supports high customization: through modular design, users can flexibly configure the interface layout and display different data and graphics to adapt to the differentiated air traffic control needs of various regions.

[0069] 2. The present invention realizes efficient data visualization: by utilizing 2D / 3D hardware accelerated rendering supported by WebGL, it provides controllers with intuitive and smooth data display, thereby improving the efficiency of information acquisition.

[0070] 3. The present invention improves system scalability and compatibility: adopts a microservice architecture to enable each module to be independently managed and deployed, simplifying the system update and expansion process; and realizes centralized management and flexible resource utilization through the compatibility of the cloud platform.

[0071] 4. The present invention reduces operation and maintenance costs: through the centralized management and automation tools of the cloud native system, the workload of terminal deployment and maintenance is reduced, allowing the system to adapt to rapidly changing business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following is a brief introduction to the drawings required for the specific embodiments or the description of the prior art. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn according to the actual scale.

[0073] Figure 1 The software engine architecture diagram of the present invention;

[0074] Figure 2 This is a diagram of the data source engine architecture of the present invention;

[0075] Figure 3 A diagram showing the implementation steps of the data source engine of the present invention;

[0076] Figure 4 This is a diagram of the data display engine architecture of the present invention;

[0077] Figure 5 A diagram showing the implementation steps of the data display engine of the present invention;

[0078] Figure 6 This is the architecture diagram of the alarm engine of the present invention;

[0079] Figure 7 It is a working principle diagram of the alarm engine of the present invention;

[0080] Figure 8 This is a diagram of the user interaction engine architecture of the present invention;

[0081] Fig. 9 This is a working principle diagram of the user interaction engine of the present invention;

[0082] Fig.10 This is a log recording engine architecture diagram of the present invention;

[0083] Fig.11 This is a working principle diagram of the log recording engine of the present invention;

[0084] Fig.12 It is a system framework diagram of the present invention. DETAILED DESCRIPTION

[0085] The following embodiments of the technical solution of the present invention are described in detail in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and are therefore only used as examples, and cannot be used to limit the protection scope of the present invention.

[0086] It should be noted that, unless otherwise specified, the technical terms or scientific terms used in this application should have the common meanings understood by those skilled in the art to which the invention belongs.

[0087] Embodiment 1:

[0088] A method for implementing an air traffic control automation display system with a microservice architecture, such as Figure 1-11 As shown in the figure, by introducing Golang, WebGL, React and other technologies, a modern SDD system based on microservice architecture is built to improve the system's customization, scalability and cross-platform compatibility.

[0089] Specifically include:

[0090] Software engine, Golang programming language and microservice architecture; to achieve an efficient and flexible air traffic control automated display terminal system.

[0091] in:

[0092] Software Engine:

[0093] The software engine is the core component of a software system that builds specific functions. In this invention, the software engine is responsible for managing the acquisition, processing and display of data. It implements specific functions through different modules and provides good scalability and reusability. The main advantages of using a software engine include:

[0094] Highly reusable: Different applications can be developed based on the same software engine without the need to rewrite code, which improves development efficiency.

[0095] Portability: The software engine can run on multiple operating systems, supports a wide range of hardware platforms, and reduces system dependencies.

[0096] Scalability: Through the plug-in mechanism, users can quickly expand the functionality of the software engine according to their needs to support different data sources and functional modules.

[0097] In the present invention, the software engine is designed as a modular system, and each module can be independently developed and updated to achieve rapid response to market changes.

[0098] Golang Language:

[0099] Golang (also known as Go language) is a programming language developed by Google, which has the characteristics of compilation, static typing and concurrent processing. The application of Golang in the present invention is mainly reflected in the following aspects:

[0100] High performance: Golang is compiled into machine code with high execution efficiency, which is suitable for scenarios requiring high-performance computing and fast response.

[0101] Simplicity: Golang has a concise syntax that is easy to read and maintain, which helps with team collaboration and later development.

[0102] Concurrent processing: Golang's built-in coroutine supports lightweight concurrent programming, making multi-tasking more efficient and suitable for processing complex air traffic control data streams.

[0103] Modern library support: Golang comes with a variety of modern libraries, including network communication, data parsing, etc., which can quickly build efficient network services.

[0104] By using Golang, the SDD system is able to implement efficient background services, support real-time data processing and response, and improve the overall performance of the system.

[0105] Microservices Architecture:

[0106] Microservice architecture is a modern application development method that splits an application into multiple small services, each of which performs a specific function and communicates through a unified interface. The application of this architecture in the present invention is mainly reflected in the following aspects:

[0107] Service independence: Each microservice can be deployed, upgraded, and expanded independently, which reduces the coupling of the system and ensures that when a problem occurs in a service, it will not affect the operation of the entire system.

[0108] Flexibility and scalability: Microservice architecture allows functional modules to be quickly added or replaced according to specific needs, adapting to changing market demands. Different services can use different technology stacks so that the best solution can be selected.

[0109] High availability: Through redundant deployment of services, the system can improve fault tolerance and ensure that when some services fail, other services can still operate normally.

[0110] Automated deployment and continuous integration: Microservice architecture is suitable for use in combination with containerization technology (such as Docker) to achieve automated deployment and continuous integration, thereby improving the efficiency of development and operation and maintenance.

[0111] In the present invention, the microservice architecture enables the SDD system to be flexibly deployed in a cloud environment, supporting high-concurrency request processing and large-scale data processing.

[0112] WebGL Technology:

[0113] WebGL is a browser-based graphics API that allows developers to render 2D and 3D graphics on web pages. The introduction of WebGL provides powerful data visualization capabilities for the technology of this invention, allowing controllers to display information such as flight dynamics and weather changes in an intuitive way. Its main features include:

[0114] High-performance rendering: WebGL uses graphics processing units (GPUs) for hardware acceleration, which can efficiently render complex graphics and improve the real-time and smoothness of data display.

[0115] Cross-platform compatibility: WebGL is widely supported in modern browsers, allowing developed applications to run seamlessly on different devices and operating systems, improving the accessibility of the system.

[0116] Rich visual effects: With WebGL, you can create a variety of visual effects to enhance the presentation of data and help controllers better understand and analyze information.

[0117] By combining WebGL technology, the SDD system can achieve efficient data visualization and provide a more intuitive and dynamic user experience.

[0118] The present invention uses Golang and WebGL to build a microservice architecture air traffic control automation display system, and its software engine is as follows: Figure 1 As shown, including:

[0119] 1) Data source engine: An engine that reads required regulatory data from a specific database by setting data source parameters through the user. It supports most mainstream products of time series databases and traditional relational databases.

[0120] 2) Data display engine, whose functions include:

[0121] a) The overall layout can be customized, including the main track display, control data display and other panels;

[0122] b) Geographic data is displayed on the basis of the global map, with points, lines and surfaces displayed statically to realize the display of the aviation map.

[0123] c) Dynamically display track symbols, sign content arrangement colors, etc.;

[0124] d) Other data visualization, custom SDD to display other regulatory data tables, charts, etc.

[0125] 3) Alarm engine, which can customize user alarm type, alarm duration, and alarm display method.

[0126] 4) User interaction engine, a software engine that customizes the operations that users can perform and the execution results.

[0127] 5) Log recording engine, an engine that provides log collection, recording, and query services.

[0128] Among them, for the data source engine: golang is used to implement a data source engine that is extended using plug-ins. The architecture of the data source engine is as follows: Figure 2 As shown, it includes: JS / TS parsing engine and React component engine.

[0129] The main implementation steps are as follows Figure 3 As shown in the figure: Use Golang to build the backend TypeScript / JavaScript engine, use interfaces and classes to preliminarily build the framework of the data source engine, and define the common interface of the data source object, such as the Query interface. Use the React component engine to define the interface of the data source plug-in on the interface, focusing on defining the data source name and data source source interface.

[0130] Among them, for the data display engine, its architecture is as follows Figure 4 As shown, it includes canvas drawing engine, React component engine, data conversion module and visualization customization module;

[0131] Implementation steps: Figure 5 As shown: First, the control data is input into the data conversion module for conversion, mainly converting the latitude and longitude coordinates in the geographic data and track data into rectangular coordinates, and converting the speed and altitude information in the track data into signs with pre-set colors, and then delivered to the canvas drawing engine for drawing. The drawing engine draws the visible layer using user-defined colors, icons and other elements based on the custom drawing configuration file written by the user.

[0132] Among them, for the alarm engine, its architecture is as follows Figure 6 As shown, it includes: an alarm rule parsing module, an alarm judgment module, an alarm message generating module, and an alarm routing module;

[0133] The alarm engine works like this: Figure 7 As shown: The alarm rule parsing module parses the external alarm rule script into alarm rules and alarm routing tables. The scope of alarm rules includes track position alarms (i.e., whether the approach distance between tracks exceeds the threshold, whether the track is within a specific restricted area, whether the aircraft on the scene intrudes the runway, etc.), specific secondary code alarms (such as 7700, 7600), and the alarm routing table specifies which subsystems or modules the alarm message will be sent to, such as sending it to the data display engine so that the alarm information can be displayed on the main interface with sound and light effects.

[0134] Among them, for the user interaction engine, its architecture is as follows Figure 8 As shown, it includes: a custom interface script parsing module, a custom event script parsing module, an event processing module, and a display engine interface;

[0135] The user interaction engine works like Fig. 9 As shown: By reading the external script, the custom event and custom interface script are decomposed from it, and the custom interface rules are sent to the display engine through the display engine interface, and the custom control is generated through the React component engine, and the custom control event is bound. At the same time, the custom control event rules are sent to the event processing module for calling.

[0136] Among them, for the logging engine, its architecture is as follows Fig.10 As shown, it includes: a log rule parsing module, a log message generating module, a log database, and a log query module;

[0137] The logging engine works like this Fig.11 As shown:

[0138] The log rule configuration file is read at startup, and the log rules are generated through the parsing module, waiting to be called by the log message generation module.

[0139] Other modules in this system generate logs that comply with log rules by calling the external interface of the log message generation module, and write logs through the log database operation module.

[0140] The log generation module can also collect logs from other subsystems at a regular interval and write them into the log database after parsing according to built-in rules.

[0141] On the other hand, users can enter conditions to query logs on the interface, and the data display engine will call the log query interface and display the returned query results.

[0142] The process of using the software engine to build the SDD subsystem can be divided into the following stages:

[0143] Set the data source, that is, first select the data source of the monitoring system.

[0144] Setting the display interface means building a display interface based on the default interface by setting rules and configurations.

[0145] Set alarm rules, that is, customize the alarm engine by setting configuration files (rule files in yaml file format).

[0146] Set interaction rules and customize interaction rules by setting interaction scripts.

[0147] Set log rules and set the format and content of output logs by setting log templates.

[0148] Start the trial run. If there is any problem during the trial run, modify the specific module configuration through one of the above steps and continue to use it after the problem is solved.

[0149] The present invention:

[0150] Supports high degree of customization: Through modular design, users can flexibly configure the interface layout and display different data and graphics to adapt to the differentiated air traffic control needs of various regions.

[0151] Achieve efficient data visualization: Use 2D / 3D hardware accelerated rendering supported by WebGL to provide controllers with intuitive and smooth data display, improving the efficiency of information acquisition.

[0152] Improve system scalability and compatibility: Adopt microservice architecture to enable independent management and deployment of each module, simplify the system update and expansion process; and achieve centralized management and flexible resource utilization through the compatibility of cloud platforms.

[0153] Reduce operation and maintenance costs: Through the centralized management and automation tools of cloud-native systems, the workload of terminal deployment and maintenance is reduced, allowing the system to adapt to rapidly changing business needs.

[0154] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be included in the scope of the claims and specification of the present invention.

Claims

1. A method for implementing an air traffic control automation display system based on a microservice architecture, characterized in that: Build an SDD system based on microservice architecture, including software engine, Golang programming language and microservice architecture, including: Software Engine: The software engine is responsible for managing the acquisition, processing and display of data; through the plug-in mechanism, users can quickly expand the functions of the software engine according to their needs, supporting different data sources and functional modules. The software engine includes a data source engine, a data display engine, an alarm engine, a user interaction engine and a log recording engine; Microservices Architecture: The microservice architecture splits the application into multiple small services, each of which is responsible for a specific functional module, including data acquisition, data processing, and data display; uses a unified interface for communication to achieve interaction and data transmission between services; manages and deploys microservices based on orchestration tools; and uses a load balancer to process high-concurrency requests; The SDD system implements data visualization based on the WebGL library; improves the performance and fluency of data rendering based on WebGL hardware acceleration; processes data based on the parallel computing capability of GPU; and uses React components to encapsulate WebGL rendering logic to achieve separation of front-end and back-end and modular development.

2. According to the method for implementing a microservice architecture air traffic control automation display system according to claim 1, it is characterized by: The data source engine is an engine that reads the required regulatory data from a specific database through user-defined data source parameters; The data source engine is specifically implemented in the following steps: S1: Configuration management, users enter data source parameters through configuration files or interfaces, including database type, host address, port number, user name, password, and specific query statements; S2: Connection establishment: According to the parameters provided by the user, the data source engine establishes a connection with the target database based on the database driver; S3: Data reading. Once the connection is established successfully, the data source engine executes the query statement provided by the user to obtain data. S4: Data processing, including data cleaning, format conversion, and aggregate computing operations.

3. According to the method for implementing a microservice architecture air traffic control automation display system of claim 1, it is characterized by: The data display engine displays the processed data in a visual manner, supporting the customization of overall layout, geographic data display, track symbol display and visualization of other data; the specific implementation steps are as follows: Configuration management: The data display engine implements configuration management based on the display parameters entered by the user through the configuration file or interface, including layout settings, color schemes, and font sizes; Geographic data display: The data display engine statically displays points, lines and surfaces on the base of the global map to display the aerial map; loads and renders map data based on geographic information system technology; Dynamic display of track symbols: Use the WebGL library to dynamically display track symbols; Other data visualization: Use ECharts for other data visualization displays.

4. According to claim 1, a method for implementing an air traffic control automation display system with a microservice architecture is characterized in that: The alarm engine provides the function of customizing user alarm type, alarm duration and alarm display mode; The implementation method of the alarm engine includes: Alarm type definition: The alarm engine is based on user-defined alarm types, each type corresponds to a specific monitoring condition or event; the user enters the name and triggering condition of the alarm type through the configuration file or interface; Alarm rule configuration: For each alarm type, users configure specific triggering rules; the rules include threshold judgment and the number of event occurrences within the time window; Alarm triggering mechanism: The alarm engine monitors the data stream provided by the data source engine in real time, and analyzes whether the data meets the triggering conditions according to the preset alarm rules; once an event that meets the conditions is detected, an alarm message is immediately generated; Alarm duration management: Users set different durations for each alarm type; the alarm duration determines how long an alarm will be displayed before being cleared; the alarm engine tracks the start time and duration of each alarm, and automatically clears expired alarms after a specified time; Alarm display mode: including pop-up window prompt, sound alarm, LED indicator flashing; Alarm priority management: Users can assign different priority levels to each alarm type based on the importance of the alarm, and high-priority alarms will be displayed first; Alarm record and query: All generated alarm information is recorded in the log system; the alarm record includes the alarm type, trigger time, duration, and display mode; users retrieve historical alarm records through the query interface provided by the log recording engine.

5. According to the method for implementing a microservice architecture air traffic control automation display system of claim 1, it is characterized by: The data source engine: uses golang to implement extension using plug-ins, and the architecture of the data source engine includes: JS / TS parsing engine, React component engine; The implementation steps of the data source engine are: S1: Use Golang to build the backend TypeScript / JavaScript engine, and preliminarily build the framework of the data source engine in the form of interfaces and classes; S2: defines the common interface of data source objects; S3: Use the React component engine to define the representation interface of the data source plug-in on the interface.

6. According to claim 1, a method for implementing an air traffic control automation display system with a microservice architecture is characterized in that: The data display engine, whose architecture includes a canvas drawing engine, a React component engine, a data conversion module and a visualization customization module; The implementation steps are: S1: First, the control data is input into the data conversion module for conversion, and the longitude and latitude coordinates in the geographic data and track data are converted into rectangular coordinates; S2: Convert the speed and altitude information in the track data into a sign with a preset color, and then deliver it to the canvas drawing engine for drawing; S3: The drawing engine draws visible layers with user-defined colors and icon elements according to a custom drawing profile written by the user.

7. The method for implementing an air traffic control automation display system with a microservice architecture according to claim 1, characterized in that: The alarm engine includes: an alarm rule parsing module, an alarm judgment module, an alarm message generation module, and an alarm routing module; Among them: the alarm rule parsing module parses the external alarm rule script into alarm rules and alarm routing tables; the scope of the alarm rules includes track position alarms, specific secondary code alarms, and the alarm routing table specifies which subsystems or modules the alarm messages are sent to.

8. The method for implementing an air traffic control automation display system with a microservice architecture according to claim 1, characterized in that: The user interaction engine includes: a custom interface script parsing module, a custom event script parsing module, an event processing module, and a display engine interface; The user interaction engine reads external scripts, decomposes custom events and custom interface scripts from them, parses them separately, sends the custom interface rules to the display engine through the display engine interface, generates custom controls through the React component engine, and binds custom control events; at the same time, the custom control event rules are sent to the event processing module for calling.

9. The method for implementing an air traffic control automation display system with a microservice architecture according to claim 1, characterized in that: The log recording engine includes: a log rule parsing module, a log message generating module, a log database, and a log query module; The logging engine works by: S1: Read the log rule configuration file at startup, and generate log rules through the parsing module, waiting for the log message generation module to call; S2: Other modules in the system generate logs that comply with log rules by calling the external interface of the log message generation module, and write logs through the log database operation module; S3: Log generation module, which collects logs from other subsystems at regular intervals, parses them according to built-in rules, and writes them into the log database; S4: The user enters conditions to query the log on the interface, and the data display engine calls the log query interface and displays the returned query results.

10. The method for implementing a microservice architecture air traffic control automation display system according to claim 1, characterized in that: The process of the SDD system is divided into the following stages: S1: Set the data source. First, select the data source of the monitoring system; S2: Set the display interface. Based on the default interface, the display interface is built by setting rules and configurations. S3: Set alarm rules and customize the alarm engine by setting configuration files; S4: Set interaction rules. Customize interaction rules by setting interaction scripts. S5: Set log rules, set the format and content of output logs by setting log templates; S6: Start the trial run. If there is any problem during the trial run, modify the specific module configuration through S1-S5 and continue to use it after the problem is solved.

Images