An integrated software system based on civil aviation laser wind radar

By adopting front-end separation architecture and microservice architecture in the civil aviation laser wind measurement radar system, unified data management and real-time analysis are realized, the problems of high data isolation and false alarm rates in existing systems are solved, and the use of the system is improved Efficiency and friendliness, supporting multi-radar data fusion and cluster management.

CN118093640BActive Publication Date: 2024-11-08NANJING MOVELASER TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410475428.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-04-19
Publication Date
2024-11-08
Estimated Expiration
2044-04-19

AI Technical Summary

Technical Problem

The existing software systems of civil aviation laser wind measurement radar have problems such as data isolation, inconvenient storage, difficulty in single point control and multi-radar data fusion, resulting in inconvenient data transmission and high false alarm rate, and the inability to realize joint system analysis and radar cluster management.

Method used

An integrated software system designed with front-end separation architecture, including the display layer, gateway layer, service layer and data layer, uses the VUE2.0 framework, Nginx middleware, SpringCloud microservice architecture, MySQL, InfluxDB, Redis and MQTT to achieve data unification Management and messaging, supporting multi-radar data fusion and cluster management.

Benefits of technology

It realizes unified data management and real-time analysis, reduces false alarm rate, improves system usage efficiency and friendliness, supports multi-radar data fusion and cluster management, and simplifies operation and maintenance and remote analysis.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118093640B_ABST
    Figure CN118093640B_ABST
Patent Text Reader

Abstract

The present invention discloses an integrated software system based on civil aviation laser wind radar, including an operation and maintenance data center, wherein the operation and maintenance data center adopts a front-end and back-end separation architecture design, wherein the front-end includes a display layer, and the back-end includes a gateway layer, a service layer, a data layer and an operation layer; the display layer is a user interface, including system management, radar operation and maintenance and data products, and adopts a VUE2.0 framework. The integrated software system based on civil aviation laser wind radar manages user data, equipment data, external reference data, radar sampling data, wind speed inversion data, wind shear warning data, etc. in a unified manner through basic data services such as Mysql / InfluxDB / Redis / NAS, and stores them in association, which greatly facilitates joint analysis of early warnings and avoids the generation of false alarms.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention belongs to the technical field of civil aviation, and in particular relates to an integrated software system based on a civil aviation laser wind measuring radar. Background Art

[0002] In the field of civil aviation, the safety and efficiency of aircraft take-off and landing are two factors that major airports are concerned about. One of the main means and methods is to use meteorological observation to warn and dispatch aircraft take-off and landing. Laser wind radar can well replace the traditional wind measurement method. It has the advantages of large range, high precision, high real-time performance, and high reliability. It has begun to be used in some airports. For the radar software support system, considering the different application scenarios, the common implementation solution in the industry is to develop corresponding software for operation and maintenance, meteorological observation and air traffic control departments respectively.

[0003] According to the current technical solution, radar operation and maintenance, meteorological observation and air traffic control forecast belong to three independent software entities, which have the following shortcomings:

[0004] The data needs to be transmitted in triplicate and isolated from each other, which makes it difficult to conduct joint system analysis.

[0005] Data storage relies on software installation clients, which is not conducive to rapid migration and remote analysis;

[0006] It is a single-point control and cannot be used for radar cluster management, which is not convenient for operation and maintenance.

[0007] It is difficult to achieve multi-radar data fusion based on single radar wind speed inversion and warning, and the false alarm rate is high.

[0008] To this end, the present invention proposes a clustered software design solution that integrates operation and maintenance, meteorological observation and air traffic control forecast. Summary of the invention

[0009] The present invention aims to provide an integrated software system based on civil aviation laser wind measurement radar to solve the technical problems raised in the background technology.

[0010] To achieve the above purpose, the specific technical solution of the present invention is as follows: an integrated software system based on civil aviation laser wind radar, including an operation and maintenance data center, the operation and maintenance data center adopts a front-end and back-end separation architecture design, the front end includes a display layer, and the back end includes a gateway layer, a service layer, a data layer and an operation layer;

[0011] The display layer is the user interface, including system management, radar operation and maintenance, and data products, using the VUE2.0 framework;

[0012] The gateway layer is used to deploy Nginx middleware, configure upstream to achieve load balancing, configure server / stream to achieve HTTP / TCP request reverse proxy, and configure auth_request to achieve unified authentication;

[0013] The service layer is a microservice architecture based on SpringCloud, which is divided into a management platform, data services and message services. Each service allocates server resources according to the concurrency.

[0014] The data layer selects a storage method based on data characteristics. The database mainly includes the relational database MySQL and the time series database InfluxDB;

[0015] The operation layer is used to provide basic hardware resource services, physical servers or cloud servers, with a minimum configuration of 8 cores and 16G, and install and run the Linux (X86 or ARM) operating system and configure JRE8+ environment variables.

[0016] Preferably, the data service is mainly used to subscribe to the topic of laser radar publishing messages, push them to the front end in real time and persist them in the time series database. In order to make full use of the server multi-thread resources, thread pool technology is used here to improve the message processing throughput.

[0017] Preferably, the management platform is responsible for processing user requests from the front-end page, real-time monitoring of radar data products, batch updating of radar data, and batch remote upgrading of radars.

[0018] Preferably, the message service mainly accepts connections from MQTT clients, manages publishing / subscribing of messages, and completes message delivery.

[0019] Preferably, the MySQL is mainly used to store basic data such as users, permissions, configurations, etc. managed by the system, InfluxDB mainly stores data collected by the lidar in real time, the cache mainly uses Redis to store hot data and timeliness data, and the file server mainly stores the lidar's daily summary data files, upgrade packages, and extracted log files.

[0020] Preferably, the specific steps of the VUE2.0 framework receiving real-time data are as follows:

[0021] S1. The radar initiates a connection request to the message queue telemetry transmission protocol. The message queue telemetry transmission protocol verifies the request and successfully establishes a connection with the radar. At the same time, the radar subscribes to the instruction topic of the message queue telemetry transmission protocol.

[0022] S2. Radar publishes real-time data to the message queue telemetry transmission protocol, the message queue telemetry transmission protocol bridges the real-time data to the message queue service, the message queue service sends the consumption real-time data to the application service, and the application service pushes the data to the front-end page.

[0023] Preferably, the specific steps of VUE2.0 framework issuing instructions are as follows:

[0024] T1. The front-end page sends instructions to the application server, and the application server publishes instruction messages to the message queue telemetry transmission protocol. The message queue telemetry transmission protocol feeds back the consumption instruction messages to the radar;

[0025] T2, radar receives the consumption command message and publishes the command execution result to the message queue telemetry transmission protocol, and the message queue telemetry transmission protocol bridges the command execution result to the message queue service;

[0026] T3. The message queue service sends the execution result of the consumption instruction to the application server, and the application server pushes it to the front-end page.

[0027] Preferably, the specific steps of the VUE2.0 framework to query historical data are as follows:

[0028] Y1. The front-end page establishes a connection with the application server and sends the query conditions, and the application server sends the data that meets the conditions to the database;

[0029] Y2. The database sends the data that meets the conditions to the application server, and the server returns the total amount of data to the front-end page;

[0030] Y2. The front-end page subscribes to a unique topic from the application server, and the application server pushes historical data to the unique topic and feeds it back to the front-end page.

[0031] Preferably, the specific method for VUE2.0 framework to perform shear warning is as follows: the radar receives shear data and calculates the shear position in real time to determine whether it is within the glide path or runway range. If it is within the range, the shear warning data is saved and pushed to the front-end warning. If it is not within the range, the instruction ends.

[0032] The integrated software system based on civil aviation laser wind radar of the present invention has the following advantages:

[0033] The present invention uses basic data services such as Mysql / InfluxDB / Redis / NAS to uniformly manage user data, device data, external reference data, radar sampling data, wind speed inversion data, wind shear warning data, etc., and associates and stores them, which greatly facilitates joint analysis of early warnings and avoids the generation of false alarms.

[0034] The present invention adopts the mainstream front-end and back-end design scheme, and the end user can manage and query the radar through any terminal, which greatly improves the efficiency and friendliness of use. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1 is the overall system block diagram of the present invention;

[0037] Figure 2 A system block diagram of real-time data transmission of the present invention;

[0038] Figure 3 A system block diagram of sending a connection request of the present invention;

[0039] Figure 4 A system block diagram of issuing instructions of the present invention;

[0040] Figure 5 It is a system block diagram of the shear warning of the present invention. DETAILED DESCRIPTION

[0041] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the embodiments of the present invention. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0042] In the description of the embodiments of the present invention, it should be understood that the terms "length", "vertical", "horizontal", "top", "bottom", etc. indicating the orientation or positional relationship are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing the embodiments of the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present invention.

[0043] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present invention, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0044] In the embodiments of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection, an electrical connection, or a communication; it can be a direct connection, or an indirect connection through an intermediate medium, and it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the embodiments of the present invention can be understood according to specific circumstances.

[0045] The disclosure below provides many different embodiments or examples to implement different structures of the embodiments of the present invention. In order to simplify the disclosure of the embodiments of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the embodiments of the present invention. In addition, the embodiments of the present invention can repeat reference numbers and / or reference letters in different examples, and this repetition is for the purpose of simplification and clarity, which itself does not indicate the relationship between the various embodiments and / or settings discussed.

[0046] In order to better understand the purpose, structure and function of the present invention, the integrated software system based on the civil aviation laser wind measurement radar of the present invention is further described in detail below with reference to the accompanying drawings.

[0047] like Figure 1-5As shown, an integrated software system based on civil aviation laser wind radar of the present invention includes an operation and maintenance data center, and the operation and maintenance data center adopts a front-end and back-end separation architecture design, the front end includes a display layer, and the back end includes a gateway layer, a service layer, a data layer and an operation layer; the display layer is a user interface, including system management, radar operation and maintenance and data products, and adopts a VUE2.0 framework; the gateway layer is used to deploy Nginx middleware, configure upstream to achieve load balancing, configure server / stream to achieve HTTP / TCP request reverse proxy, and configure auth_request to achieve unified authentication; the service layer is a microservice architecture based on SpringCloud, which is divided into a management platform, a data service and a message service, and each service allocates server resources according to the concurrency. The data service is mainly used to subscribe to the topic of the laser radar publishing message, push it to the front end in real time and persist it in the time series database. In order to make full use of the server multi-threaded resources, the thread pool technology is used here to improve the message processing throughput. The operation layer provides basic hardware resource services, physical servers or cloud servers, with a minimum configuration of 8 cores and 16G, installs and runs the Linux (X86 or ARM) operating system, and configures JRE8+ environment variables. The management platform is responsible for processing user requests from the front-end page, real-time monitoring of radar data products, batch updating of radar data, and batch remote upgrade of radars. The message service mainly accepts the connection of the MQTT client, manages the publishing / subscription of messages, and completes message delivery. The data layer selects the storage method according to the characteristics of the data. The database mainly includes the relational database MySQL and the time series database InfluxDB. The MySQL is mainly used to store basic data such as users, permissions, and configurations managed by the system. InfluxDB mainly stores data collected by the laser radar in real time. The cache mainly uses Redis to store hot data and time-effectiveness data. The file server mainly stores the daily summary data files, upgrade packages, and extracted log files of the laser radar.

[0048] Preferably, the specific steps of the VUE2.0 framework receiving real-time data are as follows:

[0049] S1. The radar initiates a connection request to the message queue telemetry transmission protocol. The message queue telemetry transmission protocol verifies the request and successfully establishes a connection with the radar. At the same time, the radar subscribes to the instruction topic of the message queue telemetry transmission protocol.

[0050] S2. Radar publishes real-time data to the message queue telemetry transmission protocol, the message queue telemetry transmission protocol bridges the real-time data to the message queue service, the message queue service sends the consumption real-time data to the application service, and the application service pushes the data to the front-end page.

[0051] Preferably, the specific steps of VUE2.0 framework issuing instructions are as follows:

[0052] T1. The front-end page sends instructions to the application server, and the application server publishes instruction messages to the message queue telemetry transmission protocol. The message queue telemetry transmission protocol feeds back the consumption instruction messages to the radar;

[0053] T2, radar receives the consumption command message and publishes the command execution result to the message queue telemetry transmission protocol, and the message queue telemetry transmission protocol bridges the command execution result to the message queue service;

[0054] T3. The message queue service sends the execution result of the consumption instruction to the application server, and the application server pushes it to the front-end page.

[0055] Preferably, the specific steps of the VUE2.0 framework to query historical data are as follows:

[0056] Y1. The front-end page establishes a connection with the application server and sends the query conditions, and the application server sends the data that meets the conditions to the database;

[0057] Y2. The database sends the data that meets the conditions to the application server, and the server returns the total amount of data to the front-end page;

[0058] Y2. The front-end page subscribes to a unique topic from the application server, and the application server pushes historical data to the unique topic and feeds it back to the front-end page.

[0059] Preferably, the specific method for VUE2.0 framework to perform shear warning is as follows: the radar receives shear data and calculates the shear position in real time to determine whether it is within the glide path or runway range. If it is within the range, the shear warning data is saved and pushed to the front-end warning. If it is not within the range, the instruction ends.

[0060] It is to be understood that the present invention is described by some embodiments, and it is known to those skilled in the art that various changes or equivalent substitutions may be made to these features and embodiments without departing from the spirit and scope of the present invention. In addition, under the teachings of the present invention, these features and embodiments may be modified to adapt to specific circumstances and materials without departing from the spirit and scope of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed herein, and all embodiments falling within the scope of the claims of this application are within the scope of protection of the present invention.

Claims

1. An integrated software system based on civil aviation laser wind radar, characterized in that: Including an operation and maintenance data center, the operation and maintenance data center adopts a front-end and back-end separation architecture design, the front-end includes a display layer, and the back-end includes a gateway layer, a service layer, a data layer and an operation layer; The display layer is the user interface, including system management, radar operation and maintenance, and data products, using the VUE2.0 framework; The gateway layer is used to deploy Nginx middleware, configure upstream to achieve load balancing, configure server / stream to achieve HTTP / TCP request reverse proxy, and configure auth_request to achieve unified authentication; The service layer is a microservice architecture based on SpringCloud, which is divided into management platform, data service and message service. Each service allocates server resources according to the concurrency. The data service is mainly used to subscribe to the topic of laser radar release messages, push them to the front end in real time and persist them in the time series database. In order to make full use of the server multi-thread resources, the thread pool technology is used here to improve the message processing throughput; The data layer selects a storage method based on data characteristics. The database mainly includes the relational database MySQL and the time series database InfluxDB; The MySQL is mainly used to store users, permissions, and basic configuration data of system management. InfluxDB is mainly used to store data collected by the laser radar in real time. The cache mainly uses Redis to store hot data and timeliness data. The file server mainly stores the daily summary data files, upgrade packages, and extracted log files of the laser radar. The operation layer is used to provide basic hardware resource services, physical servers or cloud servers, with a minimum configuration of 8 cores and 16G, installed and running Linux operating system, and configured with JRE8+ environment variables; The specific steps of the VUE2.0 framework to receive real-time data are as follows: S1. The radar initiates a connection request to the message queue telemetry transmission protocol. The message queue telemetry transmission protocol verifies the request and successfully establishes a connection with the radar. At the same time, the radar subscribes to the instruction topic of the message queue telemetry transmission protocol. S2. Radar publishes real-time data to the message queue telemetry transmission protocol, the message queue telemetry transmission protocol bridges the real-time data to the message queue service, the message queue service sends the consumption real-time data to the application service, and the application service pushes the data to the front-end page; The specific steps for VUE2.0 framework to issue instructions are as follows: T1. The front-end page sends instructions to the application server, and the application server publishes instruction messages to the message queue telemetry transmission protocol. The message queue telemetry transmission protocol feeds back the consumption instruction messages to the radar; T2, radar receives the consumption command message and publishes the command execution result to the message queue telemetry transmission protocol, and the message queue telemetry transmission protocol bridges the command execution result to the message queue service; T3. The message queue service sends the execution result of the consumption instruction to the application server, and the application server pushes it to the front-end page; The specific steps for querying historical data in the VUE2.0 framework are as follows: Y1. The front-end page establishes a connection with the application server and sends the query conditions, and the application server sends the data that meets the conditions to the database; Y2. The database sends the data that meets the conditions to the application server, and the server returns the total amount of data to the front-end page; Y2. The front-end page subscribes to a unique topic from the application server, and the application server pushes historical data to the unique topic and feeds it back to the front-end page; The specific method of shear warning in the VUE2.0 framework is as follows: the radar receives shear data and calculates the shear position in real time to determine whether it is within the glide path or runway range. If it is within the range, the shear warning data is saved and pushed to the front-end warning. If it is not within the range, the command ends.

2. The integrated software system based on civil aviation laser wind radar according to claim 1, characterized in that: The management platform is responsible for processing user requests from the front-end page, real-time monitoring of radar data products, batch updating of radar data, and batch remote upgrading of radars.

3. The integrated software system based on civil aviation laser wind radar according to claim 1, characterized in that: The message service mainly accepts connections from MQTT clients, manages message publishing / subscription, and completes message delivery.