A method and system for airport terminal equipment telemetry and control

Abstract

The application belongs to the technical field of computers, and discloses an airport terminal equipment telemetry and control method and system. The method is realized by using a java language to realize a probe to complete terminal equipment information collection and report and terminal management background instruction processing; through terminal management background, the terminal equipment account management, terminal telemetry data aggregation management, terminal telemetry data alarm analysis, remote terminal instruction issuing, and remote terminal desktop control are realized. The method provides a centralized management airport terminal equipment system, all terminal equipment is included in a unified management platform for management and control, the terminal equipment state and running data are telemetered, abnormal equipment can be alarmed in time, the terminal equipment can be remotely controlled, and the problem of airport terminal equipment operation and maintenance is solved.

Description

Technical Field

[0001] This invention belongs to the field of computer technology, and in particular relates to a method and system for telemetry and control of airport terminal equipment. Background Technology

[0002] With the rapid development of the civil aviation industry and the continuous expansion of airport scale, the types and quantities of terminal equipment used in airports are also increasing dramatically. These terminal devices include various types and models such as turnstiles, displays, and self-service kiosks, playing a crucial role in the daily operation of airports. However, due to the dispersed distribution of terminal equipment and the lack of centralized management methods, the current maintenance methods for terminal equipment rely on manual inspections and on-site operations, which are inefficient, prone to oversights, and fail to meet the operational needs of modern airports, seriously affecting the service quality and operational efficiency of airports.

[0003] Therefore, developing a method for centralized management, telemetry, and control of various terminal devices at airports has become an urgent problem to be solved within airports.

[0004] Existing utility model patent one, a telemetry terminal device (publication number CN206132078U), discloses a telemetry terminal device, including a telemetry terminal, a sensor connected to the telemetry terminal, and a power supply module for powering the telemetry terminal. An electrostatic discharge (ESD) protection circuit is connected between the power supply module and the telemetry terminal. The ESD protection circuit includes an ESD discharge circuit and a switching circuit. The switching circuit includes a current-limiting resistor and a field-effect transistor (FET). The drain of the FET is connected to the power supply module through the current-limiting resistor, and the source is connected to the telemetry terminal. A first resistor and a second resistor, connected in series and with their other ends grounded, are connected to the connection point of the current-limiting resistor and the power supply module. The common terminal of the first resistor and the second resistor is connected to the non-inverting input of an amplifier. The inverting input of the amplifier is connected to a reference voltage through a fourth resistor and simultaneously connected to the cathode of a fourth diode. The anode of the fourth diode is grounded. The output of the amplifier is connected to the gate of the FET. This device has an ESD protection function, effectively preventing ESD damage to its internal components. The focus of this solution is to provide a telemetry terminal device that, through the telemetry terminal, sensor, and power supply, realizes a hardware device for telemetry data acquisition.

[0005] Existing utility model patent two, a remote control system (publication number CN212569465U), discloses that the remote control system includes a terminal module, a main gateway module, one or more sub-device modules, and a cloud service module. The main gateway module is communicatively connected to the cloud service module and receives control commands sent by the terminal module. Based on the control commands, it generates control signals and sends them to one or more sub-device modules. The sub-device modules control their devices according to the control signals, thereby expanding the range of remote control of home appliances. The focus of this solution is to provide a smart remote control system for home appliances, where the terminal module sends commands to the sub-device modules via a cloud service to control the sub-devices.

[0006] Based on the above analysis, the problems and defects of the existing technology are as follows: the existing technology does not address the telemetry and control of airport terminal equipment. Airport terminal equipment is characterized by its variety, large quantity, and scattered distribution. Traditional terminal maintenance and fault handling are carried out manually on-site, which is extremely inefficient and difficult to guarantee quality, making it difficult to meet the ever-increasing maintenance needs. Summary of the Invention

[0007] To overcome the problems existing in related technologies, this invention discloses a method and system for telemetry and control of airport terminal equipment. Specifically, it relates to a telemetry and control method for terminal equipment that is compatible with multiple operating systems. The purpose of this invention is to propose a telemetry and control method for airport terminal equipment, aiming to solve the management problems of airport terminal equipment and improve the operational efficiency and service quality of airports. This method achieves unified management, telemetry of operational status, and remote control of various types of terminal equipment by constructing a centralized terminal equipment management backend and a unified cross-platform probe.

[0008] The technical solution is as follows: a telemetry and control method for airport terminal equipment, including:

[0009] S1 installs a cross-platform probe on the terminal device, collects terminal device information including terminal name, operating system type and name, terminal MAC address and IP, registers it in the terminal management backend, and reports heartbeat and device operation data every 10 seconds.

[0010] S2, the terminal management backend supplements and maintains terminal information through the terminal device management module, including terminal type, terminal location, and terminal remote login information. The telemetry data receiving module processes the received reported data, updates the terminal status, and aggregates and stores the terminal operation data. A visual interface is used to display the list of managed terminal devices, terminal status, and operation data. Commands are sent to the terminal devices through the remote command issuing module, including shutdown, restart, and process operation. The remote desktop control module connects to the terminal devices, obtains the screen display content of the terminal devices, and performs desktop operations.

[0011] S3 defines alarm rules for the terminal device's operating data through the alarm analysis module, analyzes and processes the device operating data received by the telemetry data receiving module, and promptly issues alarms for abnormal operating data of the terminal device that meets the alarm rules.

[0012] In step S1, heartbeat and equipment operating data are reported every 10 seconds, including:

[0013] S101, Terminal Registration and Heartbeat: The probe starts automatically when the terminal device starts. When the probe starts, it establishes a Netty channel with the terminal management backend and interacts with upstream and downstream data of the terminal management backend. The probe collects terminal device information and registers the terminal information into the terminal management backend using the MAC address as a unique identifier. The terminal management backend persists the terminal information and establishes a mapping between the terminal instance and the communication channel, obtaining key-value pairs {key=terminal mac, value=channel id}.

[0014] S102, Terminal Operation Data Collection and Reporting: The probe uses Java's system API to collect the terminal device's operation data, including CPU usage, memory usage, hard disk usage, and running processes. The operation data is then uploaded to the terminal management backend, which persists the operation data for real-time display and alarm analysis.

[0015] S103, Terminal Command Processing: The probe receives commands issued by the terminal management backend, parses the commands, and executes them.

[0016] In step S101, the probe sends heartbeat information to the terminal management backend every 10 seconds. The terminal management backend determines the terminal's survival status based on the heartbeat reception status. A terminal that does not receive a heartbeat for 30 seconds is considered offline.

[0017] In step S103, the instruction is parsed and executed, including: converting the instruction into an instruction that matches the current system based on the type of the current terminal device, and calling the operating system's instruction execution API to execute the instruction.

[0018] In step S2, the terminal management backend supplements and maintains terminal information through the terminal device management module, including:

[0019] The system listens for probe registration requests, automatically generates terminal device records, uses the MAC address in the registration information as the unique identifier of the terminal device, and updates the terminal device information. It also listens for probe heartbeats to identify the status of the terminal device and maintains terminal information through a visual page, including supplementing terminal type, model, manufacturer, and remote connection parameters.

[0020] In step S2, the telemetry data receiving module processes the received reported data, including: listening to the probe's operation data reporting request, persistently storing the operation data in the time series database, and using the visual page for terminal devices to query the operation status and historical data trend; and forwarding the operation data to the alarm analysis module for alarm analysis.

[0021] In step S3, alarm rules are defined for the operating data of the terminal device through the alarm analysis module. This includes: maintaining alarm rules and notification configurations through a visual page. The alarm rule information includes target selection, indicator selection, threshold setting, and associated notification configuration. After telemetry data is received, it is asynchronously sent to the alarm analysis message queue. The alarm analysis module listens to the message queue topic and performs alarm analysis on each received data.

[0022] Furthermore, the alarm analysis module monitors the message queue topic and performs alarm analysis on each received data item, including:

[0023] (I) Select matching alarm rules based on the target to which the received data belongs;

[0024] (II) Obtain the configured metrics and thresholds from the alarm rules;

[0025] (III) Obtain the value of the configured indicator from the received data and compare it with the threshold configured in the rule. The threshold setting includes a comparison operator and a comparison value. Take the real-time value and the comparison value and compare them according to the comparison operator. If the result is true, it is determined to be compliant.

[0026] (IV) Data that meets the threshold conditions will trigger an alarm, and the alarm will be notified according to the notification configuration.

[0027] Furthermore, the maintenance of alarm rules and notification configurations is provided through a visual page, including:

[0028] (A) Obtain the notification configuration associated with the alarm rule;

[0029] (B) Obtain the convergence configuration from the notification configuration, including the sending interval and the maximum number of sending times. Obtain the notification history according to the target to which the received data belongs, including the last sending time and the number of sending times. Compare with the convergence configuration, and do not send notifications if the convergence conditions are met.

[0030] (C) Assemble the notification content that does not meet the convergence condition, obtain the notification template, replace the template variables according to the received data attributes, and obtain the final notification content;

[0031] (D) Obtain the notification target, push the notification, and update the notification history;

[0032] (E) Remote command issuance: The terminal management backend defines commands, including shutdown, restart, and process start / stop. Commands are issued to the terminal device using the visual page operation. The terminal management backend obtains the communication channel with the probe, packages the command into a message body and sends it. The probe listens for command messages on the channel, receives the command, converts it according to the current terminal operating system type, and calls the system API to execute it.

[0033] (F) Remote Desktop Control: Obtain remote connection information of the terminal from the terminal management module, including the terminal target, connection type and authentication information. The terminal management backend establishes a connection with the remote terminal according to the remote connection information, performs two-way information exchange, and realizes the monitoring and control of the remote terminal desktop.

[0034] Another object of the present invention is to provide a telemetry and control system for airport terminal equipment, the system implementing the aforementioned telemetry and control method for airport terminal equipment, the system comprising:

[0035] The probe, written in Java, is used to collect and report terminal device information and process commands from the terminal management backend.

[0036] The terminal management backend is responsible for the ledger management of terminal devices, the aggregation and management of terminal telemetry data, the alarm analysis of terminal telemetry data, the issuance of remote terminal commands, and the desktop control of remote terminals.

[0037] Combining all the above technical solutions, the beneficial effects of this invention are as follows: This method provides a system for centralized management of airport terminal equipment. The system incorporates all terminal equipment into a unified management platform for control, remotely measures the status and operation data of the terminal equipment, promptly alerts abnormal equipment, and enables remote control of the terminal equipment, thus solving the problem of difficult operation and maintenance of airport terminal equipment.

[0038] Compared to the existing technology patent, the focus of this invention is on collecting, reporting and presenting monitoring data of terminal devices at the software level.

[0039] Compared to the existing technology patent 2, the focus of this invention is to realize two-way information interaction between various types of airport terminal equipment and the terminal management backend through the airport's internal network. Attached Figure Description

[0040] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure;

[0041] Figure 1 This is a flowchart of the airport terminal equipment telemetry and control method provided in an embodiment of the present invention;

[0042] Figure 2This is a schematic diagram of the airport terminal equipment telemetry and control system provided in an embodiment of the present invention;

[0043] Figure 3 This is a timing flowchart of the interaction between the machine probe and the terminal management backend provided in an embodiment of the present invention;

[0044] In the diagram: 1. Probe; 2. Terminal management backend. Detailed Implementation

[0045] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Many specific details are set forth in the following description to provide a thorough understanding of the present invention. However, the present invention can be practiced in many other ways different from those described herein, and those skilled in the art can make similar modifications without departing from the spirit of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.

[0046] The innovation of this invention lies in the following: This invention develops a cross-platform probe and terminal management backend based on the Java language. It establishes communication between the cross-platform probe and the terminal management backend to achieve two-way information interaction, including the reporting of terminal operation data and the issuance of instructions and remote control by the terminal management backend. Furthermore, it enables in-depth application of terminal operation data in the terminal management backend, including monitoring, display, and alarm analysis of terminal operation data.

[0047] This invention, while ensuring the normal operation of the terminal device, enables communication with the terminal management backend by installing probes on the terminal device, thereby achieving centralized management of telemetry information of the terminal device and remote control of the terminal device.

[0048] Example 1, as Figure 1 As shown, the airport terminal equipment telemetry and control method provided in this embodiment of the invention includes:

[0049] S1, install the cross-platform probe 1 to the terminal device, collect terminal device information including terminal name, operating system type and name, terminal MAC address and IP, register it in the terminal management backend 2, and report heartbeat and device operation data every 10 seconds.

[0050] S2, the terminal management backend 2 supplements and maintains terminal information through the terminal device management module, including terminal type, terminal location, and terminal remote login information. The telemetry data receiving module processes the received reported data, updates the terminal status, and aggregates and stores the terminal operation data. A visual interface is used to display the list of managed terminal devices, terminal status, and operation data. Commands are sent to the terminal devices through the remote command issuing module, including shutdown, restart, and process operation. The remote desktop control module connects to the terminal devices, obtains the screen display content of the terminal devices, and performs desktop operations.

[0051] S3 defines alarm rules for the terminal device's operating data through the alarm analysis module, analyzes and processes the device operating data received by the telemetry data receiving module, and promptly issues alarms for abnormal operating data of the terminal device that meets the alarm rules.

[0052] Example 2, as Figure 2 As shown, the airport terminal equipment telemetry and control system provided in this embodiment of the invention solves the difficulties in operation and maintenance and control caused by the large variety, quantity and physical location of airport terminal equipment.

[0053] The system consists of Probe 1 (a cross-platform probe) and Terminal Management Backend 2. Probe 1 collects and reports terminal information and processes commands from the Terminal Management Backend. Developed in Java, it internally communicates with the unified terminal management backend to shield against differences in operating systems and communication protocols across various terminal devices. The unified terminal management backend is responsible for terminal device ledger management, aggregation and management of terminal telemetry data, alarm analysis of terminal telemetry data, remote terminal command issuance, and remote terminal desktop control.

[0054] like Figure 2 As shown, the probe is installed on the terminal device and starts automatically upon device startup. It is centrally deployed in the terminal management backend, providing a user-friendly terminal management interface. After startup, the probe collects terminal device information, registers it in the terminal management backend, and reports heartbeat and device operation data at regular intervals. The telemetry data receiving module in the terminal management backend processes the received reported data, updates the terminal status, and aggregates and stores the terminal operation data. Users can supplement and maintain terminal information, such as terminal type, location, and remote login information, through the terminal device management module. A visual interface displays the managed terminal device list, terminal status, and operation data. Commands, such as shutdown, restart, and process operations, are issued to the terminal device through the remote command issuing module. Users can connect to the terminal device through the remote desktop control module to access the screen content and perform desktop operations. Users can define alarm rules for the terminal device's operation data through the alarm analysis module and analyze and process the device operation data received by the telemetry data receiving module, promptly issuing alarms for abnormal terminal device operation data.

[0055] Since there are many types and models of airport terminal equipment, and the operating systems and communication protocols of different devices are different, in order to shield the differences in operating systems and communication protocols, a probe is implemented using the cross-platform Java language. A common communication protocol is established between probe 1 and terminal management backend 2 to achieve unified terminal registration and heartbeat, terminal operation data collection and reporting, and terminal command processing.

[0056] The technical implementation scheme of probe 1 is as follows:

[0057] S101, Terminal Registration and Heartbeat: Probe 1 starts automatically when the terminal device starts. When Probe 1 starts, it establishes a Netty channel with the terminal management backend 2 and interacts with upstream and downstream data of the terminal management backend 2. Probe 1 collects terminal device information and registers the terminal information into the terminal management backend 2 using the MAC address as a unique identifier. The terminal management backend 2 persists the terminal information and establishes a mapping between the terminal instance and the communication channel, obtaining key-value pairs {key=terminal mac, value=channel id}.

[0058] When the probe starts, it reads the Netty service address of the terminal management backend from the configuration file, creates a Netty client, and establishes a Netty channel with the terminal management backend. Subsequent upstream and downstream data interactions with the terminal management backend are conducted through this channel. The probe collects basic information about the terminal device, such as the terminal name, operating system type and name, terminal MAC address, and IP address. Using the MAC address as a unique identifier, the probe registers the terminal information with the terminal management backend. The terminal management backend persists the terminal information and establishes a mapping cache in memory, storing the mapping between the terminal instance's MAC address and the communication channel number. The probe sends a heartbeat to the terminal management backend every 10 seconds. The terminal management backend determines the terminal's liveness status based on the received heartbeats; a terminal that does not receive a heartbeat for 30 seconds is considered offline.

[0059] S102, Terminal operation data collection and reporting: Probe 1 uses Java's system API to collect the terminal device's operation data, including CPU usage, memory usage, hard disk usage, and running processes, and uploads the operation data to the terminal management backend 2. The terminal management backend 2 persists the operation data and performs real-time display and alarm analysis.

[0060] The probe uses Java's system APIs (such as java.lang.Runtime, java.lang.management.PlatformManagedObject, etc.) to collect operational data from the terminal device;

[0061] S103, Terminal instruction processing: Probe 1 receives instructions from the terminal management backend 2, parses the instructions, and executes them;

[0062] The probe 1 has a built-in mapping table of general instruction codes and instructions of various types of operating systems. After receiving the general instruction code issued by the terminal management background, the probe retrieves the system instruction that matches the current operating system from the instruction mapping table and executes the instruction.

[0063] The timing diagram of the interaction between probe 1 and terminal management backend 2 is as follows: Figure 3 .

[0064] In this embodiment of the invention, the terminal management backend 2 is responsible for the centralized management of all terminal devices in the airport, including terminal device management, telemetry data reception, alarm analysis, remote command issuance, and remote desktop control. Specific functions include:

[0065] (a) Terminal Device Management: Monitor probe registration requests, extract terminal information from the registration requests, assemble them into terminal device records, and persistently store them in the terminal information table. Use the MAC address from the registration information as the unique identifier for each terminal device to prevent duplicate registrations and update terminal information promptly. Monitor probe heartbeat requests, determine the terminal device record in the terminal information table using the MAC address in the heartbeat request, update the most recent heartbeat time, and update the terminal device status every second via a scheduled task based on terminal status updates. Terminals whose current time is more than 30 seconds since the last heartbeat are marked as offline. Provide a visual page for users to maintain terminal information, such as adding terminal type, model, manufacturer, and remote connection parameters.

[0066] (b) Telemetry Data Reception: Listen for operational data reporting requests from probes, extract data from the requests, including the MAC address used as a terminal identifier, and operational data such as CPU usage, memory usage, hard disk usage, and running processes. Classify and persistently store the operational data in the corresponding time-series database tables, providing a visual page for terminal device operational status queries and historical data trend queries. Forward the operational data to the alarm analysis module for alarm analysis.

[0067] (c) Alarm Analysis: Provides a visual page for maintaining alarm rules and notification configurations. Alarm rule information includes target selection, metric selection, threshold settings, and associated notification configurations. The definitions of alarm rule information attributes are as follows:

[0068] (i) Target selection: The terminal devices applicable to this alarm rule are selected from the terminal information table. The relationship between alarm rule and target is one-to-many.

[0069] (ii) Indicator selection: The data types of the operation applicable to this rule, such as CPU utilization, memory usage, etc.

[0070] (iii) Threshold setting: The threshold formula for triggering alarms for this type of operating data of the terminal device, including the comparison operator and the comparison value. For example, if the target is selected as terminal device A, the indicator is selected as CPU utilization, the comparison operator is configured as >=, and the comparison value is configured as 90%, it means that an alarm will be triggered when the CPU utilization value of terminal device A is >= 90%.

[0071] (iiii) Associated notification configuration: The notification configuration after the alarm rule is triggered is selected from the notification configuration table. The relationship between alarm rules and notification configuration is many to one.

[0072] After telemetry data is received, it is asynchronously sent to the alarm analysis message queue. The alarm analysis module listens to the message queue topic and performs alarm analysis on each received data message. The process is as follows:

[0073] (i) Select matching alarm rules based on the target to which the received data belongs, extract the MAC address that identifies the unique terminal from the received data, and compare it with the terminal information in the selected target of the alarm rule. The alarm rule that contains this MAC address in the selected target is the matching rule.

[0074] (ii) Obtain the metric and threshold configuration from the alarm rules matched in the previous step, such as configuring the metric as CPU utilization and the threshold as >=90%;

[0075] (iii) Obtain the value of the configured indicator from the received data, such as CPU utilization = 95%, compare it with the threshold configured in the rule, and if it meets the threshold condition of current CPU utilization >= 90%, trigger an alarm;

[0076] (iiii) Data that meets the threshold conditions in the previous step will trigger an alarm, and the alarm will be sent according to the notification configuration selected in the alarm matching rule in (i).

[0077] In this embodiment of the invention, the notification configuration information includes a notification template, a notification target, and a notification convergence configuration. The attributes of the notification configuration information are defined as follows:

[0078] (i) Notification Template: A template for the notification content, supporting dynamic replacement of variables. After an alarm triggers a notification, the actual variable values ​​will be substituted into the template variables and sent as the notification content. For example, the template configuration is as follows:

[0079] Alarm target: ${deviceName}

[0080] Alert metrics: ${metric}

[0081] Trigger threshold: ${threshold}

[0082] Current value: ${value}

[0083] Where ${deviceName}, ${metric}, ${threshold}, and ${value} are embedded variables, which are substituted from the received data and the actual values ​​in the alarm rules. The actual notification content after substitution is as follows:

[0084] Alarm target: Terminal device A

[0085] Alarm indicator: CPU utilization

[0086] Trigger threshold: >=90%

[0087] Current value: 95%

[0088] (ii) Notification target: The notification method configured to trigger this notification, such as WeChat, DingTalk, etc.

[0089] (iii) Notification convergence configuration: Convergence rules configured to avoid a large number of notifications, including the sending interval and the maximum number of sending times. For example, a sending interval of 60 seconds means that multiple alarms triggered within 60 seconds will only send one notification, and a maximum number of sending times of 10 means that no matter how many alarms are triggered, a maximum of 10 notifications will be sent.

[0090] The receiving data that meets the alarm conditions triggers the notification logic, as follows:

[0091] (A) Obtain the notification configuration associated with the alarm rule from the alarm rule configuration that was triggered;

[0092] (B) Extract the convergence configuration (sending interval, maximum number of sending times) from the notification configuration obtained in the previous step. Retrieve the notification history from the notification record table according to the target of the received data and the triggered alarm rules. The notification history is written to the notification record table after each successful notification transmission, including the target of the notification, the triggering rule, the last sending time, and the total number of sending times. Compare the convergence configuration with the data, calculating whether the number of sending times exceeds the maximum number of sending times configuration, and whether the current time is less than the last sending time is less than the sending interval configuration. If both convergence conditions are met, no notification is sent.

[0093] (C) If the convergence condition is not met, a notification is sent. The notification template is extracted from the notification configuration. The template variables are replaced according to the received data and the attribute values ​​of the triggered alarm rules. For example, the ${metric} variable in the template is replaced with the metric configuration value "CPU utilization" in the alarm rule to obtain the final notification content.

[0094] (D) Obtain the notification target, supporting WeChat, DingTalk, email and SMS. Push notifications by calling the open API of each platform and update the notification history, including recording the current notification time and incrementing the total number of sends by 1.

[0095] (E) Remote Command Issuance: The terminal management backend defines commands, such as shutdown, restart, process start / stop, etc., and provides a visual page for issuing commands to the terminal device. The terminal management backend 2 obtains the communication channel with probe 1, packages the command into a message body and sends it. The message body contains the operation type and operation parameters, such as {"OPERATE_CODE":"KILL_PROCESS","PARAMS":["1234"]}, which represents the command to close the process, and the process number to be closed is 1234. The probe listens for command messages on the channel, and after receiving the command, it queries the built-in command mapping table and performs command conversion according to the current terminal operating system type. For example, if the current operating system type is LINUX, the system command corresponding to the LINUX system "KILL_PROCESS" command code obtained from the table is "kill -9 ${param1}". The above process number "1234" is substituted into the variable ${param1} to assemble the system command "kill -9 1234", which is then executed by calling the system command.

[0096] (F) Remote Desktop Control: Obtain remote connection information from the terminal management module, including terminal target (terminal IP, port), connection type (rdp, ssh, vnc) and authentication information (username / password or vnc password). It supports two operation types: read-only and operable. The terminal management backend establishes a connection with the remote terminal according to the remote connection information and conducts two-way information interaction. The management end transmits keyboard, mouse and other inputs to the terminal, and the terminal transmits desktop display and other outputs to the management end, realizing the monitoring and control of the remote terminal desktop.

[0097] As can be seen from the above embodiments, the probe for cross-platform terminal devices provided by the present invention includes cross-platform support for terminal probes, establishment of probe communication protocols, probe data acquisition, and probe processing instructions.

[0098] A unified terminal device management backend includes terminal management, terminal telemetry monitoring, terminal command issuance, and remote desktop monitoring and control.

[0099] This invention provides a telemetry and control method for airport terminal equipment. This method can meet the centralized management needs of numerous airport terminal devices and realize telemetry monitoring and remote control of these devices. Implementation of this solution can significantly improve the operation and maintenance management efficiency of airport terminal equipment.

[0100] To further illustrate the effects of the embodiments of the present invention, the following experiments were conducted.

[0101] (1) Start the terminal management backend.

[0102] (2) Install a cross-platform probe on terminal device A and modify the configuration file to specify the IP and port of the terminal management backend. After the probe starts, it collects terminal information, registers with the terminal management backend, and reports heartbeat and running data on a regular basis.

[0103] (3) The registration information of terminal device A can be seen in the terminal management module in the terminal management backend. The real-time running data can be seen by opening the monitoring page of terminal device A.

[0104] (4) Configure alarm rules and notification settings. When the terminal device A's running data is abnormal, an alarm event is generated and a notification is received.

[0105] (5) In the terminal management backend, the terminal management module maintains the remote connection method and authentication information of terminal device A, connects to terminal device A through the remote desktop control module, obtains the screen display content of terminal device A and can perform desktop operations.

[0106] (6) In the terminal management background, the instruction issuing module sends a shutdown instruction to terminal device A, and terminal device A successfully shuts down.

[0107] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications, equivalent substitutions and improvements made by those skilled in the art within the scope of the technology disclosed in the present invention and within the spirit and principles of the present invention should be covered within the scope of protection of the present invention.

Claims

1. An airport terminal equipment telemetry and control method, characterized by, The method comprises: S1, installing a cross-platform probe (1) to a terminal device, collecting terminal device information including terminal name, operating system type and name, terminal mac address and ip, registering into a terminal management background (2), and reporting heartbeat and device running data at a time interval of every 10s; S2, the terminal management background (2) supplements and maintains terminal information including terminal type, terminal position and terminal remote login information through a terminal device management module, processes received reporting data through a telemetry data receiving module, updates terminal state and stores terminal running data, displays a terminal device list, terminal state and running data through a visual interface, and issues instructions including shutdown, restart and process operation to the terminal device through a remote instruction issuing module; and connects to the terminal device through a remote desktop control module, acquires terminal device screen display content and performs desktop operation; S3, defining alarm rules for terminal device running data through an alarm analysis module, analyzing and processing device running data received by the telemetry data receiving module, and timely alarming terminal device abnormal running data meeting the alarm rules; In step S1, heartbeat and device running data are reported at a time interval of every 10s, including: S101, terminal registration and heartbeat: the probe (1) is started with the terminal device, the probe (1) establishes a netty channel with the terminal management background (2) when starting, and interacts with upstream and downstream data of the terminal management background (2); the probe (1) collects terminal device information, registers the terminal information into the terminal management background (2) with a mac address as a unique identifier, the terminal management background (2) persists the terminal information, and establishes a mapping of a terminal instance and a communication channel to obtain a key-value pair of {key=terminal mac, value=channel id}; S102, terminal running data collection and reporting: the probe (1) collects terminal device running data including cpu usage, memory usage, hard disk usage and running processes by using a system API of java, uploads the running data to the terminal management background (2), and the terminal management background (2) persists the running data, performs real-time display and alarm analysis; S103, terminal instruction processing: the probe (1) receives instructions issued by the terminal management background (2), analyzes and executes the instructions; In step S2, the telemetry data receiving module processes received reporting data, including: listening to running data reporting requests of the probe (1), persisting the running data into a time sequence database, using a visual page for terminal device running state query and historical data trend query; and forwarding the running data to the alarm analysis module for alarm analysis.

2. The airport ground terminal telemetry and control method according to claim 1, characterized in that, In step S101, the probe (1) sends heartbeat information to the terminal management background (2) every 10s, and the terminal management background (2) judges the survival state of the terminal according to the heartbeat receiving condition, and a terminal not receiving heartbeat for 30s is regarded as offline.

3. The airport ground terminal telemetry and control method according to claim 1, characterized by, In step S103, the instruction is parsed and executed, including: for the type of the current terminal device, converting the instruction into an instruction matching the current system, calling the instruction execution API of the operating system, and performing instruction execution.

4. The airport ground terminal telemetry and control method of claim 1, wherein, In step S2, the terminal management background (2) supplements and maintains terminal information through the terminal device management module, including: Listening to the registration request of the probe (1), automatically generating a terminal device record, taking the mac address in the registration information as the unique identifier of the terminal device, and updating the terminal device information; listening to the heartbeat of the probe (1), identifying the state of the terminal device, and maintaining the terminal information through a visual page, including supplementing the terminal type, model, manufacturer, and remote connection parameters.

5. The method of airport terminal equipment telemetry and control according to claim 1, characterized in that, In step S3, the alarm analysis module defines alarm rules for the running data of the terminal device, including: providing maintenance of alarm rules and notification configuration through a visual page, alarm rule information includes target selection, index selection, threshold setting, and associated notification configuration, after receiving telemetry data, it is sent to the alarm analysis message queue asynchronously, and the alarm analysis module listens to the message queue topic and performs alarm analysis on each received data.

6. The airport ground terminal telemetry and control method according to claim 5, wherein, The alarm analysis module listens to the message queue topic and performs alarm analysis on each received data, including: (I) According to the target to which the received data belongs, filter and select matching alarm rules; (II) Obtain the configured index and threshold from the alarm rule; (III) Obtain the value of the configured index from the received data, compare it with the threshold configured in the rule, the threshold setting includes a comparison symbol and a comparison value, compare the real-time value with the comparison value according to the comparison symbol, and the result true is determined as meeting the condition; (IV) Data meeting the threshold condition will trigger an alarm, and the alarm will be notified according to the notification configuration.

7. The airport ground terminal telemetry and control method according to claim 5, wherein, Provide maintenance of alarm rules and notification configuration through a visual page, including: (A) Obtain the notification configuration associated with the alarm rule; (B) Obtain the convergence configuration from the notification configuration, including the sending interval and the maximum number of sending times, obtain the notification history according to the target to which the received data belongs, including the last sending time and the sending times, compare the convergence configuration, and do not send notifications if the convergence condition is met; (C) Assemble the notification content, obtain the notification template, replace the template variables according to the received data attributes, and obtain the final notification content; (D) Obtain the notification target and push the notification, and update the notification history; (E) Remote instruction issuance: the terminal management background (2) defines instructions, including shutdown, restart, and process start / stop, and issues instructions to the terminal device through a visual page, the terminal management background (2) obtains the communication channel with the probe (1), packages the instructions into a message body and sends them, the probe (1) listens to the channel for instruction messages, performs instruction conversion according to the current terminal operating system type after receiving the instructions, calls the system API for execution; (F) Remote desktop control: obtain the terminal remote connection information from the terminal management module, including the terminal target, connection type, and authentication information, the terminal management background (2) establishes a connection with the remote terminal according to the remote connection information, performs bidirectional information exchange, and realizes monitoring and control of the remote terminal desktop.

8. An ATC system, characterized by The system implements the airport terminal equipment telemetry and control method as claimed in any one of claims 1-7, and comprises: a probe (1) using a Java language to complete terminal equipment information collection and reporting and terminal management background (2) instruction processing; a terminal management background (2) for being responsible for terminal equipment account management, terminal telemetry data aggregation management, terminal telemetry data alarm analysis, remote terminal instruction issuing, and remote terminal desktop control.

Images