Flight data transmission system and transmission method

Abstract

The embodiment of the invention provides a flight data transmission system and transmission method, the system comprises an airborne data node, a ground link main node and a ground service node, when the airborne data node and the ground link main node cannot be connected, the airborne data node stores flight data into a local memory; when the airborne data node can be communicated with the ground link main node, VPN connection is established between the airborne data node and the ground link main node; the airborne data node notifies the ground link main node to download flight data; and the ground link main node downloads the flight data from the local memory in an SFTP mode, serves as an MQ proxy node of the airborne data node, and notifies ground service nodes in a first range to download the flight data in an MQ message. According to the embodiment of the invention, artificial participation is not needed, and the flight data is transmitted to the corresponding ground service node when the airborne data node is automatically communicated with the ground link main node.

Description

Technical Field

[0001] This application relates to the field of data transmission technology, and in particular to a flight data transmission system and transmission method. Background Technology

[0002] In existing technologies, flight data on aircraft is generally transmitted via WQAR. However, there are still instances where ground personnel cannot receive wireless data, and data transmission cannot automatically resume when the wireless connection is restored. When ground personnel cannot receive wireless data, they still need to board the aircraft to read and download flight data from a solid-state cache such as a PCMCIA card or CF card.

[0003] Furthermore, existing technical solutions do not support cross-platform implementation of aircraft data transmission links, data access is limited, and the links require human intervention, manual maintenance, and management. The freedom, timeliness, and reliability of the entire data transmission link from the aircraft to the ground and from the ground to remote terminals cannot be effectively guaranteed, and the workload for management is substantial.

[0004] In many cases, ground-based software requires the development, deployment, and installation of multiple different applications to meet the operational requirements of airlines. Inconsistent application technologies can lead to chaotic interoperability and hinder daily maintenance and management. To a significant extent, this impedes airlines' data service needs. Summary of the Invention

[0005] In view of this, the present application provides a flight data transmission system and method. The technical solution of the present application establishes a VPN connection when the airborne data node and the ground link master node are automatically connected, without manual intervention, and transmits the flight data to the corresponding ground service node for consumption in a timely manner. Moreover, each ground node is deployed with an SFTP+MQ scheme, which is suitable for ground nodes of various operating systems.

[0006] In a first aspect, embodiments of this application provide a flight data transmission method, operating on a flight data transmission system. The system includes an airborne data node located on an aircraft, a ground link master node located on the ground, and ground service nodes. The method includes: when the airborne data node and the ground link master node cannot communicate, the airborne data node stores the flight data in a local storage; when the airborne data node and the ground link master node can communicate, a VPN connection is established between the airborne data node and the ground link master node; when a VPN connection is established between the airborne data node and the ground link master node and there is flight data to be downloaded, the airborne data node notifies the ground link master node to download the flight data; the ground link master node downloads the flight data from the local storage using SFTP and, acting as an MQ proxy node for the airborne data node, notifies a first range of ground service nodes to download the flight data using SFTP via MQ messages.

[0007] A VPN connection is established automatically when the airborne data node and the ground link master node are connected. No manual intervention is required. Flight data is transmitted to the corresponding ground service nodes for consumption in a timely manner. Moreover, each ground node is equipped with an SFTP+MQ solution, which is suitable for ground nodes of various operating systems.

[0008] In one possible implementation of the first aspect, the method further includes: after receiving a notification from the airborne data node, the ground link master node sends a confirmation message to the airborne data node; before receiving the confirmation message, the airborne data node repeatedly notifies the ground link master node to download the flight data.

[0009] As described above, reliable transmission of flight data from the airborne data node to the ground link master node is achieved by repeatedly notifying the airborne data node to download flight data before receiving confirmation messages.

[0010] In one possible implementation of the first aspect, the method further includes: the ground service node in the first range downloads the flight data from the ground link master node via SFTP, and notifies the ground link master node via MQ message after the download is completed.

[0011] As described above, the download is managed via MQ, and after the first range of ground service nodes completes the download of flight data from the ground link master node, it notifies the ground link master node, thereby moving the confirmation of flight data download from the aircraft to the ground.

[0012] In one possible implementation of the first aspect, when any ground service node is configured as a distribution node, it is used to proxy the distribution of data from the previous node in the data transmission link to ground service nodes in the second range. The data includes the flight data or third-party data. The method further includes: the distribution node registering with the previous node and creating an MQ connection and an SFTP connection with the ground service nodes in the second range. The registration information includes: the address of the distribution node and the address of the ground service nodes in the second range. After receiving the registration of the distribution node, the previous node updates the MQ connection between the distribution nodes and routes MQ messages with the ground service nodes in the second range as consumers to the distribution node.

[0013] As shown above, when any ground service node is configured as a distribution node, the MQ connection is reconstructed by registering with the previous node.

[0014] In one possible implementation of the first aspect, when any ground service node is configured as a secondary synchronization node, the synchronization node is used to proxy the synchronization of data from each upstream node in its data transmission link to the ground service nodes in the third range. The data includes the flight data or third-party data. The method further includes: the synchronization node registering with each upstream node and creating an MQ connection and an SFTP connection with the ground service nodes in the third range. The registration information includes: the address of the synchronization node and the address of the ground service nodes in the third range. After receiving the registration of the synchronization node, the upstream node updates the MQ connection and SFTP connection between the synchronization nodes and routes MQ messages with the ground service nodes in the third range as consumers to the synchronization node.

[0015] As shown above, when any ground service node is configured as a management node, the MQ connection is reconstructed by registering with the previous node.

[0016] In one possible implementation of the first aspect, when any ground service node is configured as a third-party access node for obtaining third-party data from a third-party node, the method further includes: the third-party access node acting as an MQ proxy node for the third-party node, notifying the fourth range of ground service nodes to download the third-party data via an MQ message; the fourth range of ground service nodes downloading the third-party data from the third-party access node via SFTP, and notifying the third-party access node via an MQ message after the download is completed.

[0017] Therefore, when any ground service node is configured as a third-party access node, the third-party access node acts as the MQ proxy node for the third-party node and transmits third-party data in the MQ+SFTP manner.

[0018] In one possible implementation of the first aspect, it further includes: each SFTP server sending SFTP information to its client, wherein when the sent SFTP information is inconsistent with the client's SFTP information, the client configures its SFTP connection according to the SFTP information, wherein the SFTP information includes the address of the file consumed by the client.

[0019] Therefore, when the SFTP information received by the client is inconsistent with the client's own corresponding SFTP information, the client automatically configures its SFTP connection according to the SFTP information, realizing automatic SFTP configuration update without manual intervention.

[0020] In one possible implementation of the first aspect, it further includes: each SFTP server serializes the data file to be downloaded by the client on its server into several serialized files, and creates a serialization metafile describing the serialization information for each of the data files; when each SFTP client downloads any data file from the corresponding SFTP server, it first downloads the serialization metafile of the data file, and then downloads the corresponding serialized files according to the serialization metafile, and retains the serial number of the serialized file currently being downloaded when the download is interrupted, wherein the data file includes third-party data or the flight data.

[0021] The above demonstrates how SFTP serializes files to enable resumeable SFTP transfers.

[0022] In one possible implementation of the first aspect, the method further includes: defining each MQ connection in the system based on the names of each node in the system; when any node in the system detects a change in its own IP address, the node updates the MQ connection with its next node and registers with its previous node with the new IP address; after receiving the registration, the previous node updates the MQ connection with the node.

[0023] Based on the above, each MQ connection in the system is defined by the name of each node. When any node detects a change in its own IP address, it triggers the automatic update of the corresponding MQ connection.

[0024] In one possible implementation of the first aspect, it further includes: when the airborne data node notifies the ground link master node to download the flight data, it also informs the ground link master node of the first range; the ground link master node determines the MQ route and SFTP transmission path of the ground service nodes in the first range accordingly.

[0025] As described above, the airborne data node notifies the ground link master node which ground service nodes are downloading flight data, and the ground link master node automatically configures the MQ routing and SFTP transmission paths for the ground service nodes.

[0026] Secondly, embodiments of this application provide a flight data transmission system, including: an airborne data node located on an aircraft, a ground link master node located on the ground, and a ground service node; the system operates the method described in any embodiment of the first aspect.

[0027] As described above, a VPN connection is established automatically when the airborne data node and the ground link master node are connected. No manual intervention is required, and the flight data is transmitted to the corresponding ground service node for consumption in a timely manner. Moreover, each ground node is equipped with an SFTP+MQ solution, which is suitable for ground nodes of various operating systems. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of a flight data transmission system according to one embodiment of the present application;

[0029] Figure 2 This is a flowchart illustrating a flight data transmission method according to a first embodiment of this application;

[0030] Figure 3 This is a schematic diagram of a second embodiment of a flight data transmission system according to this application;

[0031] Figure 4 This is a flowchart illustrating a second embodiment of a flight data transmission method according to this application;

[0032] Figure 5 This is a detailed flowchart illustrating step S410 of a second embodiment of a flight data transmission method according to this application;

[0033] Figure 6 This is a detailed flowchart illustrating step S440 of a flight data transmission method according to a second embodiment of the present application, showing the transmission of data from any node in the ground data transmission link to its next node.

[0034] Figure 7 This is a detailed flowchart illustrating step S430 of a flight data transmission method according to a second embodiment of the present application, showing the receipt of third-party data.

[0035] Figure 8 This is a detailed flowchart illustrating the configuration of the distribution node 210 and the synchronization node 220 in step S440 of a second embodiment of a flight data transmission method according to this application.

[0036] Figure 9 This is a detailed flowchart illustrating step S450 of a second embodiment of a flight data transmission method according to this application. Detailed Implementation

[0037] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0038] In the following description, the terms “first, second, third, etc.” or module A, module B, module C, etc. are used not only to distinguish similar objects or different embodiments, but also do not represent a specific ordering of objects. It is understood that a specific order or sequence may be interchanged where permitted so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0039] In the following description, the labels of the steps, such as S110, S120, etc., do not necessarily mean that the steps will be executed in this way. The order of the steps can be interchanged or executed simultaneously if permitted.

[0040] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0041] This application provides a flight data transmission system and method. The system includes an airborne data node on an aircraft, a ground link master node, and ground service nodes. The method includes: when the airborne data node and the ground link master node cannot communicate, the airborne data node stores the flight data in its local storage; when the airborne data node and the ground link master node can communicate, a VPN connection is established between the airborne data node and the ground link master node; when a VPN connection is established between the airborne data node and the ground link master node and there is flight data to be downloaded, the airborne data node notifies the ground link master node to download the flight data; the ground link master node downloads the flight data from the local storage using SFTP and, acting as an MQ proxy node for the airborne data node, notifies a first range of ground service nodes to download the flight data using MQ messages.

[0042] The technical solution of this application embodiment does not require manual intervention. A VPN connection is established when the airborne data node and the ground link master node are automatically connected, and the flight data is transmitted to the corresponding ground service node for consumption in a timely manner. Moreover, each ground node is deployed with an SFTP+MQ solution, which is suitable for ground nodes of various operating systems.

[0043] The embodiments of this application are described below with reference to the accompanying drawings. First, the terminology involved in the embodiments of this application.

[0044] VPN: Virtual Private Network. Its main function is to establish a private network over a public network for encrypted communication. It is widely used in enterprise networks. VPNs achieve remote access by encrypting data packets and translating their destination addresses. VPNs include OpenVPN, WireGuard, and other virtual private network providers.

[0045] SFTP: SSH file transfer protocol (Secure FTP or SFTP) is a network transfer protocol that enables data streaming for file access, transfer, and management, used to securely transfer files between clients and servers. File downloads are always initiated by the client. Unlike traditional FTP, SFTP protects data transmission through encrypted communication, making it suitable for transmitting sensitive information. In this application, an SFTP connection refers to the transmission link between the SFP server and client.

[0046] MQ: Message Queues (MQ) are core components of distributed systems, undertaking key functions such as asynchronous communication, traffic shaping, and application decoupling. MQ includes RabbitMQ, Apache Kafka, RocketMQ, ActiveMQ, etc. In this application, an MQ connection refers to the message transmission link between the message producer and the message consumer.

[0047] MQ+SFTP: This application proposes a combination of the two, using MQ to exchange messages and SFTP to download files.

[0048] The following is combined with Figure 1 This application introduces one embodiment of a flight data transmission system.

[0049] Figure 1 The diagram illustrates the structure of a flight data transmission system according to one embodiment of this application, including: an airborne data node located on an aircraft, a ground link master node located on the ground, and several ground service nodes.

[0050] The airborne data node is equipped with local storage. When the airborne data node cannot communicate with the ground link master node, the airborne data node stores the aircraft's flight data in the local storage. When the airborne data node can communicate with the ground link master node, a VPN connection is established between the airborne data node and the ground link master node.

[0051] After the aircraft lands, the onboard data node connects wirelessly to the current operator network at the airport, thereby connecting with the ground link master node. The location of the ground link master node can be different from the airport where the aircraft is parked.

[0052] The onboard data node connects to the local operator's network at the airport via at least one SIM card or Wi-Fi, and automatically selects the best-performing connection from these connections to establish a VPN connection.

[0053] The local storage of the airborne data node can be a disk or RAM, and its capacity is at least greater than the size of the flight data on the aircraft when it is not connected to the ground link master node.

[0054] The flight data includes aircraft data such as QAR, ACMS, and DAR.

[0055] Both the ground link master node and the ground service node are ground nodes, and each ground node can run on any of the following operating systems: Windows, OpenCloud, Kylin, OpenEuler, Deepin, and UOS.

[0056] When a VPN connection is established between the airborne data node and the ground link master node and there is flight data to be downloaded, the airborne data node notifies the ground link master node to download the flight data. The ground link master node downloads the flight data from its local storage using SFTP and notifies the first range of ground service nodes to consume it via MQ messages. The ground link master node acts as the MQ proxy node for the airborne data node, acting as the proxy for the airborne data node to exchange MQ messages with the first range of ground service nodes. At this time, the ground link master node acts as the producer of MQ messages on behalf of the airborne data node, and the first range of ground service nodes acts as the consumers of MQ messages.

[0057] In this process, the ground link master node downloads flight data files from the airborne data node via SFTP. In this case, the airborne data node acts as the SFTP server, and the ground link master node acts as the SFTP client.

[0058] In this process, the ground service node downloads flight data files from the ground link master node via SFTP. In this case, the ground link master node acts as the SFTP server, and the ground service node acts as the SFTP client.

[0059] In some embodiments, when the airborne data node notifies the ground link master node to download flight data, it also informs the ground link master node which ground service nodes are included in the first range. This information is used by the ground link master node to determine the MQ route and SFTP transmission path to the ground service nodes in the first range. Specifically, the ground link master node determines the transmission link from the ground link master node to each ground service node in the first range based on the stored topology of the ground network. The transmission link is then segmented, with the starting point of each segment being the ground link master node, a distribution node, or a synchronization node. The ground link master node, distribution node, or synchronization node serves as the SFTP server and MQ producer for the corresponding segment, thereby constructing the MQ route and SFTP transmission path determined by the ground link master node to the ground service nodes in the first range.

[0060] In some embodiments, when any data node in the flight data transmission system is configured as a distribution node, it acts as an intermediary for a node on the data transmission link to distribute data to ground service nodes in a second range using SFTP+MQ. This data includes flight data or third-party data. For example, the distribution node is used to distribute data to various ground service nodes within a company's intranet.

[0061] In some embodiments, any data node in the flight data transmission system acts as a synchronization node, acting as an intermediary for each preceding node in the data transmission link to synchronize data with ground service nodes within a third range using SFTP+MQ. This data includes flight data or third-party data. For example, the synchronization node may be used to synchronize data with ground service nodes within a defined range outside the company.

[0062] In some embodiments, when any ground service node is configured as a third-party access node to obtain third-party data from a third-party node, the third-party access node acts as an MQ proxy node for the third-party node and notifies the fourth-range ground service nodes to download the third-party data via MQ messages; the fourth-range ground service nodes download the third-party data from the third-party access node via SFTP and notify the third-party access node via MQ messages after the download is completed.

[0063] In some embodiments, each MQ connection in the flight data transmission system is defined based on the name of each node in the system. When any node in the flight data transmission system detects a change in its IP address, it updates its MQ connection with its next node and registers with its previous node using the new IP address. Upon receiving the registration, the previous node updates its MQ connection with the new node. The MQ connection relationships defined by name remain unchanged throughout the system, thus essentially achieving dynamic MQ connections that are automatically updated without manual intervention.

[0064] In summary, the first embodiment of a flight data transmission system establishes a VPN connection when the airborne data node and the ground link master node are automatically connected, without manual intervention, and transmits flight data to the corresponding ground service nodes for consumption in a timely manner. Moreover, each ground node is equipped with an SFTP+MQ scheme, which is suitable for ground nodes of various operating systems.

[0065] The following is combined with Figure 2 This application introduces a flight data transmission method according to Embodiment 1. This flight data transmission method, implemented on top of a flight data transmission system according to Embodiment 1, possesses all its advantages.

[0066] Figure 2 The flowchart of a flight data transmission method according to this application is shown, including steps S10 to S50.

[0067] S10: When communication between the airborne data node and the ground link master node fails, the airborne data node will store the flight data in its local storage.

[0068] In some embodiments, when storing data, the airborne data node also generates metadata based on the flight data, including but not limited to the data size, name format, and download address of the flight data file, in order to check whether the flight data file meets the requirements for download in subsequent flight data transmission links.

[0069] S20: When communication is possible between the airborne data node and the ground link master node, a VPN connection is established between the airborne data node and the ground link master node.

[0070] The airborne data node constantly monitors whether a wireless connection can be established with the ground operator network of the current airport. Once the wireless connection is available, it can connect with the ground link master node and establish a VPN connection with the ground link master node.

[0071] S30: When the airborne data node has flight data to be downloaded, it notifies the ground link master node to download the flight data from the airborne data node's local storage.

[0072] In some embodiments, after the airborne data node sends a notification, it continues to send the notification message to the ground link master node even if it does not receive an acknowledgment message from the ground link master node, to ensure that the ground link master node receives the notification message. Upon receiving the notification from the airborne data node, the ground link master node sends an acknowledgment message to the airborne data node.

[0073] In some embodiments, the notification message sent by the airborne data node also includes download metadata generated based on flight data. This download metadata file includes data size, name format, and download address.

[0074] S40: The ground link master node downloads flight data from the local storage of the airborne data node via SFTP.

[0075] In some embodiments, the airborne data node acts as an SFTP server, sending SFTP information to the ground link master node. When the sent SFTP information is inconsistent with the corresponding SFTP information of the ground link master node, the ground link master node configures itself as an SFTP client relative to the airborne data node based on the SFTP information. The SFTP information includes the SFTP server address, the download file address, the client account, and the password, etc.

[0076] In some embodiments, the airborne data node also serializes the flight data file to be downloaded into several serialized files, each with a configurable size, and creates a serialization metafile to describe the serialization information. When the ground link master node downloads the data file from the corresponding SFTP server, it first downloads the serialization metafile, and then downloads the corresponding serialized files based on the metafile. If the download is interrupted, the sequence number of the currently downloading serialized file is retained, allowing the download to resume from the serialized file corresponding to that sequence number when the SFTP resumes, thus enabling breakpoint resumption. The data files include third-party data or flight data.

[0077] S50: The ground link master node acts as the MQ proxy node for the airborne data node, and notifies the ground service nodes in the first range to download flight data via SFTP using MQ messages.

[0078] In this configuration, the first range is configured in the ground link master node. The MQ connection between the ground link master node and the ground service node of the first range is established in advance, or it can be established when downloading is required. By using the ground link master node as the MQ proxy node for the airborne data node, the confirmation of the flight data being downloaded from the aircraft to the data service node is changed from on-board to ground-based.

[0079] In some embodiments, ground service nodes in the first range download flight data from the ground link master node via SFTP and notify the ground link master node via MQ message after the download is complete. This SFTP+MQ method is independent of the node's operating system and can be implemented on any node.

[0080] In some embodiments, when any ground service node in the flight data transmission system is configured as a distribution node, the distribution node acts as an intermediary for the upstream node in its transmission link to distribute data to ground service nodes in a second range. This data includes flight data or third-party data. The distribution node registers itself with the upstream node in its data link and establishes a dynamic MQ connection with the ground service nodes in the second range. The ground service nodes in the second range need to delete the corresponding previous MQ connections. The registration information includes the IP address of the distribution node and the address of the ground service nodes in the second range. After receiving the registration from the distribution node, the upstream node establishes a dynamic MQ routing table and routes the MQ messages of the ground service nodes in the second range to the distribution node according to the dynamic MQ routing table. After receiving the MQ message, the distribution node sends the MQ message to the ground service nodes in the second range and downloads the data from the upstream node via SFTP. After receiving the MQ message, the ground service nodes in the second range download the data from the distribution node via SFTP for consumption.

[0081] In some embodiments, when any ground service node of the flight data transmission system is configured as a synchronization node, the synchronization node acts as an intermediary for each upstream node in its transmission link to synchronize data with ground service nodes in a third range. This data includes flight data or third-party data. The synchronization node registers itself with the upstream node in its data link and establishes a dynamic MQ connection with the ground service nodes in the third range. The registration information includes the IP address of the synchronization node and the IP address of the ground service nodes in the third range. After receiving the registration from the synchronization node, the upstream node establishes a dynamic MQ routing table and routes the MQ messages of the ground service nodes in the third range to the synchronization node according to the dynamic MQ routing table. After receiving the MQ message, the synchronization node sends the MQ message to the ground service nodes in the third range and downloads data from the upstream node using SFTP. After receiving the MQ message, the ground service nodes in the third range download data from the synchronization node using SFTP for consumption.

[0082] In some embodiments, when the flight data transmission system is configured with a third-party access node, the third-party access node acts as an MQ proxy node for the third-party node and notifies the ground service node in the fourth range to download the third-party data via an MQ message; the ground service node in the fourth range downloads the third-party data from the third-party access node via SFTP and notifies the third-party access node via an MQ message after the download is completed.

[0083] In some embodiments, the ground link master node, distribution node, synchronization node, and third-party access node serve as SFTP services, and the client configures the SFTP connection on them according to the SFTP information. The SFTP information includes the SFTP server address, the download file address, the client account, and the password, etc.

[0084] In some embodiments, the ground link master node, distribution node, synchronization node, and third-party access node act as SFTP servers, serializing the data files to be downloaded by clients into several serialized files and creating metafiles to describe the serialization information. When each SFTP client downloads a data file from the corresponding SFTP server, it first downloads the metafile, and then downloads the corresponding serialized file according to the metafile. When the download is interrupted, the serial number of the serialized file currently being downloaded is retained, so that when SFTP resumes, the download can start again from the serialized file corresponding to the serial number, thus realizing the interrupted resume.

[0085] In some embodiments, each node in the flight data transmission system maintains the data transmission connection in the following ways: when any node times out downloading data, it releases the occupied resources and reorders the timed-out download task with other tasks based on priority; in some embodiments, a notification is also triggered; when any node does not detect any files to be downloaded on the SFTP server within a set time, it triggers a notification; and any node informs its predecessor of its own maintenance status, specifically by informing the predecessor in the form of a heartbeat packet.

[0086] In some embodiments, each MQ connection in the flight data transmission system is defined based on the name of each node in the system. When any node in the flight data transmission system detects a change in its IP address, it updates its MQ connection with its next node and registers with its previous node using the new IP address. Upon receiving the registration, the previous node updates its MQ connection with the new node. The MQ connection relationships defined by name remain unchanged throughout the system, thus essentially achieving dynamic MQ connections that are automatically updated without manual intervention.

[0087] The following is combined with Figure 3 This application introduces a second embodiment of a flight data transmission system. This second embodiment is a more detailed representation of the first embodiment of the flight data transmission system and possesses all its advantages.

[0088] Figure 3 The structure of a flight data transmission system according to a second embodiment of this application is shown, including: an airborne data node 100, an airborne data node 110, a ground link master node 120, a distribution node 210, a synchronization node 220, a plurality of ground service nodes 230, a distribution node 310, a plurality of ground service nodes 330, and a third-party node 400.

[0089] Among them, distribution node 210, synchronization node 220 and distribution node 310 are also ground service nodes, which are configured as nodes with corresponding functions. Distribution node 210 is also configured as a third-party access node.

[0090] Airborne data node 100, airborne data node 110, and ground link master node 120 belong to airline A. Airborne data node 100 and airborne data node 110 are located on two separate aircraft. These two aircraft are an example; in a real scenario, multiple aircraft could be involved, with one airborne data node on each aircraft. Ground link master node 120 is located on airline A's internal network on the ground.

[0091] Airborne data nodes 100 and 110 are each equipped with a SIM card. The SIM card can roam and establish a wireless connection with the current operator network of the airport where it is parked, thereby connecting with the ground link master node 120 where the ground network of the flight data transmission system is located. Airborne data nodes 100 and 110 establish VPN connections with the ground link master node 120 respectively for exchanging data with the ground link master node 120.

[0092] Each airborne data node is equipped with local storage. When communication between the airborne data node and the ground link master node is lost, the airborne data node stores the aircraft's flight data in the local storage. The local storage is a disk, and its capacity is at least larger than the size of the flight data generated when the aircraft is unable to communicate with the ground link master node. Each aircraft's flight data includes aircraft data such as QAR, ACMS, and DAR.

[0093] Each airborne data node is equipped with a lightweight application that monitors whether a VPN connection has been established between the aircraft and the ground link master node 120, and whether new flight data files need to be downloaded. When a VPN connection is established between the aircraft and the ground link master node 120 and a flight data file needs to be downloaded, the aircraft immediately notifies the ground link master node 120 to download the corresponding flight data file and waits for an acknowledgment signal. The ground link master node 120 is the only ground node in the ground data link that can establish a VPN connection with each airborne data node.

[0094] When each airborne data node notifies the ground link master node 120 to download flight data, it also informs the ground link master node 120 which ground service nodes need to process the flight data, thereby configuring the routing of each MQ message and the SFTP transmission path on the flight data transmission link in combination with the topology of the ground network.

[0095] Ground link master node 120 acts as the MQ proxy node for airborne data nodes 100 and 110, and acts as the proxy for airborne data nodes 100 and 110 to interact with ground service node 230 via MQ messages. At this time, ground link master node 120 acts as the producer of MQ messages for airborne data nodes, and ground service node 230 acts as the consumer of MQ messages.

[0096] Ground link master node 120 downloads flight data files from airborne data node 100 and airborne data node 110 via SFTP. At this time, airborne data node 100 and airborne data node 110 are both SFTP servers, and ground link master node 120 is an SFTP client.

[0097] Distribution node 210, synchronization node 220, and ground service node 230 are also located on Airline A's internal network on the ground. Distribution node 310 and ground service node 330 are located on the internal network of Unit B. For example, only two unit internal networks are shown here; in a real scenario, multiple unit internal networks may be included. Unit B could be a regulatory or research unit involved in aircraft flight, or a subsidiary of Airline A used for data management and backup. Third-party node 400 is located in Unit C; here, the third-party data is the result of processing historical flight data of Airline A's aircraft by a third-party company.

[0098] Airline A's distribution node 210 downloads flight data from ground link master node 120, obtains third-party data from third-party node 400, and distributes it to Airline A's ground service node 230 and synchronization node 220. Synchronization node 220 synchronizes the flight data and third-party data to unit B's distribution node 310.

[0099] It should be noted that the ground link master node 120 can also obtain third-party data from the third-party node 400, and the distribution node 210 downloads third-party data from the ground link master node 120.

[0100] Distribution node 210 registers with ground link master node 120. The registration information includes the address of master node 120 and the address of ground service node 230. Ground link master node 120 forwards the first MQ message routed to ground service node 230 to distribution node 210. Distribution node 210 downloads the flight data file from ground link master node 120 via SFTP. At this time, between distribution node 210 and ground link master node 120, distribution node 210 is the consumer of MQ.

[0101] Distribution node 210 also forwards the first MQ message to ground service node 230. At this time, between distribution node 210 and ground service node 230, distribution node 210 is the producer of MQ and ground service node 230 is the consumer of MQ. Ground service node 230 downloads flight data files from distribution node 210 via SFTP and consumes them.

[0102] Distribution node 210, as a third-party access node, also receives third-party data from third-party node 400 and, as the MQ agent of third-party node 400, sends a second MQ message to ground service node 230. Ground service node 230 downloads the third-party data file from distribution node 210 via SFTP and consumes it.

[0103] Synchronization node 220 registers itself with distribution node 210. The registration information includes the address of synchronization node 220 and the address of distribution node 210. Distribution node 210 and synchronization node 220 also establish an MQ connection. Distribution node 210 is the producer of MQ, and synchronization node 220 is the consumer of MQ. Synchronization node 220 downloads flight data files and third-party data from distribution node 210 via SFTP.

[0104] Unit B's distribution node 310 receives flight data and third-party data from airline A's synchronization node 220 and distributes them to Unit B's ground service node 330.

[0105] Distribution node 310 registers itself with synchronization node 220 of B. The registration information includes the address of distribution node 310 and the address of ground service node 330. Synchronization node 220 establishes an MQ connection with distribution node 310. Synchronization node 220 sends a third MQ message to distribution node 310 through the MQ connection. Distribution node 310 downloads flight data files and third-party data files from synchronization node 220 via SFTP.

[0106] Distribution node 310 forwards the fourth MQ message to ground service node 330 via the MQ connection. At this time, between distribution node 310 and ground service node 330, distribution node 310 is the producer of MQ and ground service node 330 is the consumer of MQ. Ground service node 330 downloads flight data files and third-party data files from distribution node 310 via SFTP and consumes them.

[0107] Each MQ connection in the flight data transmission system is defined based on the node names. When any node in the system detects a change in its IP address, it updates its MQ connection with its next node and registers with its previous node using the new IP address. Upon receiving the registration, the previous node updates its MQ connection with the new node. The MQ connection relationships defined by name remain unchanged throughout the system, thus essentially achieving dynamic MQ connections that are automatically updated without manual intervention.

[0108] In the flight data transmission system, each SFTP server providing SFTP downloads sends SFTP information to its clients. When the sent SFTP information does not match the corresponding SFTP information on the client, the client configures its SFTP connection according to the SFTP information. The SFTP information includes the SFTP server address, the download file address, the client account, and the password.

[0109] In the flight data transmission system, the node acting as the SFTP server serializes the data file to be downloaded by the client into several serialized files and creates a serialization metafile to describe the serialization information. When each SFTP client downloads a data file from the corresponding SFTP server, it first downloads the serialization metafile, and then downloads the corresponding serialized file according to the serialization metafile. When the download is interrupted, the serial number of the serialized file currently being downloaded is retained, so that when SFTP resumes, the download can start from the serialized file corresponding to the serial number, thus realizing the interrupted resume.

[0110] In the flight data transmission system, if a node acting as an SFTP client times out while downloading data, it releases the occupied resources, reorders the timed-out download task with other tasks based on priority, and triggers a notification. If no files to be downloaded are detected on the SFTP server within a set time, a notification is also triggered. Each node in the flight data transmission system informs its predecessor of its own maintenance status, specifically by sending a heartbeat packet.

[0111] In summary, Embodiment 2 of the flight data transmission system has at least the following advantages:

[0112] (1) VPN not only solves the security problem of network connection between the aircraft and the ground, and between the ground and the ground in the flight data transmission link; but also allows for remote monitoring of the flight data transmission link without 24-hour monitoring; and it also solves the problem of restrictions on domestic ground nodes connecting to other countries or regions.

[0113] (2) The secure transmission of SFTP solves the risk of data loss, eavesdropping or tampering during the transmission of flight data. It also serializes the file to be downloaded to enable resume transmission.

[0114] (3) Asynchronous communication via MQ technology not only solves the problem of cascading failure caused by node failure in the flight data transmission link, but also distributes the task execution time of the nodes, allowing the system on each node to process stably and orderly according to its own processing capacity, thus avoiding system crash.

[0115] (4) By backing up data to the backup center or regulatory unit through the synchronization node, the problem of data inconsistency in flight data transmission link services in multiple regions can be solved.

[0116] (5) Cross-platform use of flight data transmission links through the combination of SFTP and MQ technologies. This includes support for mature operating systems such as Windows, OpenCloud, Kylin, OpenEuler, Deepin, and UOS.

[0117] (6) By combining VPN, SFTP and MQ technologies, no manual intervention is required, and there is no need to worry about untimely, insecure, incomplete, failed, or disconnected aircraft data transmission. The aircraft data is delivered to the terminal node in a complete, timely, cross-platform, secure, and stable manner.

[0118] The following is combined with Figures 4 to 9 This application introduces a second embodiment of a flight data transmission method. This second embodiment of the flight data transmission method operates on a second embodiment of a flight data transmission system and possesses all its advantages.

[0119] Figure 4 The overall flow of a flight data transmission method according to a second embodiment of this application is shown, including steps S410 to S450.

[0120] For ease of description, the following process is used as an example in this embodiment: the ground link master node 120 downloads flight data from the airborne data node 100 and distributes it to various ground service nodes 230 and synchronization nodes 220 of airline A through the distribution node 210. The distribution node 210 also receives third-party data from the third-party node 400 and distributes it to various ground service nodes 230 and synchronization nodes 220. The synchronization node 220 synchronizes the flight data and third-party data with the distribution node 310, and the distribution node 310 distributes the flight data and third-party data to various ground service nodes 330 of unit B. The ground service nodes 230 and 330 download and use the flight data and third-party data.

[0121] S410: When the airborne data node 100 detects that the aircraft has established a VPN connection with the ground link master node 120 and that there are flight data files that need to be downloaded, it immediately notifies the ground link master node 120 to download the corresponding flight data files via SFTP and waits to receive a confirmation signal.

[0122] S420: When the ground link master node 120 downloads the corresponding flight data file via SFTP, it monitors the aircraft data file transmission status in real time, sends a confirmation message after the download is completed, and stores the flight data file in the corresponding location.

[0123] If a download fails or times out due to network instability or other reasons during this process, the ground link master node 120 will automatically relinquish resources and reorder the download task priorities until all the aircraft data files it was notified of have been downloaded. If no notification is received from the airborne data node 100 for an extended period, an alarm will be triggered, and relevant personnel will be notified.

[0124] S430: Distribution node 210 acts as a third-party access node to access the third data file and store it in the corresponding location.

[0125] Among them, the distribution node 210 will automatically listen for and filter out valid third-party data files according to the rules. The rules here can be configured, including but not limited to aircraft identification number matching, data file format matching, data time range matching, etc., and will promptly visualize and present all current and previous accessed third-party data file records.

[0126] S440: Distribution node 210, synchronization node 220 and distribution node 310 transmit data as needed using SFTP+MQ to gradually transmit to various ground service nodes.

[0127] Specifically, the ground link master node 120 transmits flight data to the distribution node 210 via SFTP+MQ, the distribution node 210 transmits flight data and third-party data to various ground service nodes 230 and synchronization nodes 220 via SFTP+MQ, the synchronization node 220 transmits synchronized flight data and third-party data to the distribution node 310 via SFTP+MQ, and the distribution node 310 transmits flight data and third-party data to various ground service nodes 330 via SFTP+MQ.

[0128] S450: Ground service node 230 and ground service node 330 process and use flight data and third-party data.

[0129] Ground service node 230 and ground service node 330 convert flight data files and third-party data files as needed, including but not limited to decompression, decryption, decompression and decryption, renaming and other conversion operations, and store the converted data files in a specified directory for use.

[0130] Figure 5 The detailed flowchart of step S410 of a second embodiment of the flight data transmission method of this application is shown, including steps S4110 to S4170.

[0131] For ease of description, let's take an airborne data node 100 on an aircraft of airline A as an example.

[0132] S4110: When the airborne data node 100 is not connected to the ground link master node 120, the airborne data node 100 stores the generated flight data file and its meta file.

[0133] The metadata for each flight data file includes, but is not limited to, the file size, name format, and download address.

[0134] S4120: After the aircraft lands, the SIM card module of the airborne data node 100 automatically connects to the local cellular network and automatically establishes a VPN connection with the ground link master node 120.

[0135] The SIM card of the airborne data node 100 supports international roaming and accesses the local operator network of the ground cellular network at the airport where it is parked.

[0136] Among them, the VPN between the airborne data node 100 and the ground link master node 120 is an end-to-end dedicated network channel between the airborne data node 100 and the ground link master node 120, which ensures the security of data transmission.

[0137] S4130: Airborne data node 100 monitors whether a VPN connection has been established with ground link master node 120.

[0138] The airborne data node 100 is equipped with a lightweight airborne data service application that monitors whether a VPN connection has been established between the airborne node and the ground link master node 120. If a VPN connection is established, step S4140 is executed; otherwise, step S4120 is returned.

[0139] S4140: Airborne data node 100 notifies ground link master node 120 to download flight data and informs the ground service nodes within the first range that use the flight data, the metafile of the flight data file, and the aircraft's SIM card information.

[0140] Specifically, when the airborne data node 100 has a VPN connection with the ground link master node 120 and there is flight data to be downloaded, it notifies the ground link master node 120 to download the flight data and informs the ground link master node which ground service nodes will process the flight data. Thus, the ground link master node 120, which acts as the MQ agent of the airborne data node 100, establishes the routing of MQ messages and the transmission link of SFTP accordingly.

[0141] The ground link master node 120 stores the topology of the ground network and configures routes to the ground service nodes using flight data based on this topology and the ground service nodes within a first range. In this embodiment, the ground service nodes within the first range are the various ground service nodes 230 within the airline A's intranet. When there is no distribution node 210 within the airline A's intranet, the ground link master node 120 establishes MQ routes with the various ground service nodes 230, confirming that the SFTP path is from the ground link master node 120 to the various ground service nodes 230; when there is a distribution node 210 within the airline A's intranet, the ground link master node 120 establishes MQ routes with the distribution node 210, and the distribution node 210 then goes to the various ground service nodes 230, confirming that the SFTP path is from the ground link master node 120 to the distribution node 210, and the distribution node 210 then goes to the various ground service nodes 230.

[0142] Among them, the metafile of the flight data file is used to check the flight data file to be downloaded, and the aircraft's SIM card information is used to determine that the flight data comes from the airborne data node 100.

[0143] S4150: The ground link master node 120 stores the notification message from the airborne data node 100 and confirms to the airborne data node 100 that it has received the notification.

[0144] Among them, the ground link master node 120, which acts as the MQ agent of the airborne data node 100, sends MQ messages to the ground service nodes 230 within the first range and waits for the ground service nodes 230 within the first range to consume them.

[0145] S4160: Airborne data node 100 confirms whether it is a confirmation message from ground link master node 120.

[0146] In this process, the airborne data node 100 will continue to execute step S4140 and send notification messages until the ground link master node 120 receives the notification, before confirming that the message notification has been received.

[0147] S4170: Ground link master node 120 notifies ground service nodes 230 within the first range to download flight data via SFTP until all messages are consumed.

[0148] Among them, the ground link master node 120 notifies the ground service nodes 230 within the first range to download flight data via MQ messages. One MQ message is sent for each flight data file, and the ground service nodes 230 within the first range consume one MQ message for each flight data file downloaded.

[0149] Figure 6The following is a detailed flowchart illustrating the transmission of data from any node in the ground data transmission link to its next node in step S440 of a second embodiment of the flight data transmission method of this application, including steps S4410 to S4480.

[0150] This process can also be used in step S420 of a second embodiment of a flight data transmission method, in which the ground link master node 120 downloads flight data from the airborne data node 100, but does not include step S4410.

[0151] For ease of explanation, any node in the ground data transmission link here is called a server node, and the next node is called a client node.

[0152] The MQ messages originate from the server, which is the SFTP server and also the MQ message producer or producer agent. The client is the SFTP client and also the MQ message consumer or consumer agent.

[0153] S4410: When a client node receives an MQ message notification, it begins to process and consume messages one by one according to its own capacity until all messages have been consumed.

[0154] S4420: Determine whether the SFTP information received by the client node is consistent with its own SFTP information.

[0155] When a client node receives SFTP information, it automatically compares it with its own SFTP configuration information. If they match, step S4440 is executed; otherwise, step S4430 is executed.

[0156] S4430: Client nodes automatically update their own SFTP configuration based on the received SFTP information.

[0157] S4440: When a client node receives a message that there is a download task, it downloads the data using SFTP according to the number of simultaneous download tasks set by the current node, and monitors the data download status in real time and checks the data transmission link status.

[0158] The data here can be flight data or third-party data.

[0159] Here, SFTP download refers to downloading serialized files to support resuming interrupted downloads.

[0160] S4450: The client node checks if the task currently being downloaded via SFTP has timed out. If a timeout is found, step S4455 is executed, immediately and automatically relinquishing the resource and reordering the task to the end of the download schedule, and so on, until all data is downloaded. If no timeout is found, step S4460 is executed.

[0161] The timeout duration has a default setting and can also be manually modified.

[0162] S4460: During the data download process, the client node determines in real time whether the data file download is complete.

[0163] If the download is not complete, the process will return to step S4440 to continue downloading until the data file is successfully downloaded; otherwise, step S4470 will be executed.

[0164] S4470: When the data download is complete, the client node reports to the server that the download task is complete and stores the downloaded data file in the storage location specified by the client node.

[0165] If there is an MQ connection between the client node and the server node, the client node will use MQ messages to report to the server that the MQ messages for the current download task have been consumed.

[0166] S4480: When the client node determines that it has not received a message about downloading data files for an extended period of time, it triggers an alarm and notifies relevant personnel.

[0167] Figure 7 The following is a detailed flowchart of receiving third-party data in step S430 of a second embodiment of the flight data transmission method of this application, including steps S4310 to S4340.

[0168] For ease of description, we will take the distribution node 210 of airline A as an example of a third-party access node.

[0169] S4310: Distribution node 210 enables third-party data file access services as needed.

[0170] S4320: Distribution node 210 monitors the directory where third-party data files are stored on third-party node 400 in real time.

[0171] This directory is configured when the third-party data file access service is enabled in step S4310.

[0172] S4330: When a new third-party data file is detected entering the directory, it automatically determines whether the data file name, format, time, and aircraft range match.

[0173] First, it checks if the data file name and format match. If they don't match, it continues listening. If the data file name and format match, it automatically checks if the time range of the third-party data file matches. If they don't match, it continues listening. If the time range also matches, it automatically checks if its data file package matches the specified aircraft range. If they don't match, it continues listening. If they match, it proceeds to step S4340 for further processing.

[0174] S4340: Store the retrieved valid third-party data files in the specified location under distribution node 210.

[0175] The specified location can be configured by default or modified manually.

[0176] Figure 8 The detailed process of configuring the distribution node 210 and synchronization node 220 in step S440 of a second embodiment of the flight data transmission method of this application is shown, including steps S510 to S560.

[0177] If the distribution node 210 and synchronization node 220 have been configured in advance, this process is not required. If the distribution node 210 and synchronization node 220 have not been configured in advance, but will be configured during the subsequent elastic expansion of the ground network, this step will be performed.

[0178] S510: Select two ground service nodes in the intranet of airline A and configure them as distribution node 210 and synchronization node 220 respectively.

[0179] Distribution node 210 receives flight data from ground link master node 120 and third-party data from third-party node 400, and distributes the flight data and third-party data to various ground service nodes 230 within airline A's intranet. Synchronization node 220 receives flight data and third-party data from distribution node 210, synchronizes with distribution node 310 of unit B, and distributes the flight data and third-party data to various ground service nodes 330 within unit B.

[0180] S520: Distribution node 210 registers itself with ground link master node 120; synchronization node 220 registers itself with distribution node 210.

[0181] In this process, distribution node 210 records the MQ information (mainly the address of ground link master node 120) of the ground link master node 120, and then registers itself with the ground link master node 120. Synchronization node 220 records the MQ information (mainly the address of distribution node 210) of the distribution node 210, and then registers itself with the distribution node 210. Afterwards, distribution node 210 and synchronization node 220 each monitor and maintain the transmission status with their respective upstream and downstream nodes.

[0182] Distribution node 210 also establishes MQ and SFTP connections with ground service node 230; and / or synchronization node 220 also establishes MQ and SFTP connections with distribution node 310.

[0183] S530: Check whether the distribution node 210 or the synchronization node 220 has successfully connected to its respective parent node.

[0184] If the status lights of distribution node 210 and synchronization node 220 are lit in their respective parent nodes, the connection is considered successful; otherwise, the MQ information configuration needs to be checked for correctness.

[0185] S540: Set the flight data to be distributed on the distribution node 210 and update the MQ connection between the ground link master node 120 and the distribution node 210; set the flight data to be synchronized on the synchronization node 220 and create the MQ connection between the distribution node 210 and the synchronization node 220.

[0186] The flight data must specify whether it comes from the aircraft corresponding to airborne data node 100 or the aircraft corresponding to airborne data node 110.

[0187] S550: When any node detects a change in its own IP address, it updates the MQ connection between that node and its upstream and downstream nodes according to the MQ connection relationship defined by name.

[0188] As the terrestrial network expands elastically, the IP addresses of some nodes may change. The MQ connection between the node and its upstream and downstream nodes is updated according to the MQ connection relationship defined by name, and the fixed MQ connection is transformed into a dynamic MQ connection.

[0189] This step includes:

[0190] (1) Nodes whose IP addresses change clean up their old MQ connections with the next node to release memory resources;

[0191] (2) Update the MQ connection based on the new IP address, port number, account, password, and other information;

[0192] (3) Create corresponding routing rules according to the data transmission requirements and declare the queue exchange for MQ connection;

[0193] (4) Create the next node as an MQ consumer.

[0194] (5) When a node whose IP address changes registers itself with the previous node with the new IP address, the previous node deletes the consumer corresponding to the original IP address and creates a consumer with the new IP address, and adds it to the corresponding routing rule.

[0195] After the above modifications, when the IP address of any node in the system changes, including changes in the IP address of airborne data nodes, company network environment switching, server relocation, or changes in MQ configuration affecting data service nodes on the transmission link, no manual intervention is required. The entire system can still receive MQ messages normally, so it can automatically determine whether the relevant configurations on the flight data transmission link are correct, complete self-checks and updates, and ensure the normal operation of the data transmission link.

[0196] S560: The newly configured distribution node and / or synchronization node receive the download task notification message from MQ and download it via SFTP.

[0197] Among them, see Figure 6 The following is a detailed process of step S440 of a second embodiment of the flight data transmission method of this application, in which any node in the ground data transmission link transmits data to its next node, starting by receiving messages from the previous node, consuming messages, downloading the corresponding aircraft data file, and recording logs.

[0198] Figure 9 The detailed flowchart of step S450 of a second embodiment of the flight data transmission method of this application is shown, including steps S4510 to S4560.

[0199] S4510: Each ground service node in the system downloads and receives data files from the previous node and records them in the log.

[0200] S4520: Automatically converts each received data file according to the conversion method set for the current node and records the conversion in the log.

[0201] The conversion method has a default configuration and can also be manually modified.

[0202] S4530: Whether decryption is required when performing conversion operations on data file packages.

[0203] If decryption is required, proceed to step S4540 and provide a decryption certificate; otherwise, proceed directly to step S4560.

[0204] S4540: Configure aircraft data decryption certificates on ground service nodes that require decryption processing.

[0205] The ground service nodes include ground link master nodes, distribution nodes, or synchronization nodes.

[0206] S4550: Uses the configured decryption certificate to decrypt the received data files one by one and records the relevant logs.

[0207] S4560: Stores the converted data file package in the specified directory configured on the ground service node for use.

[0208] The specified directory can be the default configuration or it can be modified manually.

[0209] Note that the above are merely preferred embodiments and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application, all of which fall within the scope of protection of this application.

Claims

1. A method for transmitting flight data, characterized in that, The method operates on a flight data transmission system, which includes an airborne data node on the aircraft, a ground link master node on the ground, and a ground service node. When communication between the airborne data node and the ground link master node fails, the airborne data node stores the flight data in its local memory. When the airborne data node is connected to the ground link master node, a VPN connection is established between the airborne data node and the ground link master node; When a VPN connection is established between the airborne data node and the ground link master node and there is flight data to be downloaded, the airborne data node notifies the ground link master node to download the flight data. The ground link master node downloads the flight data from the local storage via SFTP and, as the MQ agent node of the airborne data node, notifies the ground service nodes in the first range to download the flight data via SFTP using MQ messages.

2. The method according to claim 1, characterized in that, Also includes: After receiving the notification from the airborne data node, the ground link master node sends an acknowledgment message to the airborne data node. Before receiving the confirmation message, the airborne data node repeatedly notifies the ground link master node to download the flight data.

3. The method according to claim 1, characterized in that, When any ground service node is configured as a distribution node, it is used to proxy the distribution of data from the previous node in the data transmission link to ground service nodes in the second range. The data includes the flight data or third-party data. The method further includes: The distribution node registers with the previous node and establishes MQ and SFTP connections with the ground service nodes in the second range; After receiving the registration from the distribution node, the previous node updates the MQ connection between the distribution nodes and routes the MQ messages with the ground service nodes in the second range as consumers to the distribution node.

4. The method according to claim 1, characterized in that, When any ground service node is configured as a synchronization node, the synchronization node is used to proxy the synchronization of data from each preceding node in its data transmission link to ground service nodes in a third range. The data includes the flight data or third-party data. The method further includes: The synchronization node registers with each of the previous nodes and establishes MQ and SFTP connections with the ground service nodes in the third range. After receiving the registration from the synchronization node, the previous node updates the MQ connection and SFTP connection between the synchronization nodes, and routes the MQ messages with the third-range ground service node as the consumer to the synchronization node.

5. The method according to claim 1, characterized in that, When any ground service node is configured as a third-party access node to obtain third-party data from a third-party node, the method further includes: The third-party access node acts as the MQ proxy node for the third-party node, and uses MQ messages to notify the ground service nodes in the fourth range to download the third-party data. The fourth-range ground service node downloads the third-party data from the third-party access node via SFTP, and notifies the third-party access node via MQ message after the download is complete.

6. The method according to any one of claims 1 to 5, characterized in that, Also includes: Each SFTP server sends SFTP information to its clients; When the sent SFTP information is inconsistent with the client's SFTP information, the client configures its SFTP connection according to the SFTP information, which includes the address of the file consumed by the client.

7. The method according to any one of claims 1 to 5, characterized in that, Also includes: Each SFTP server serializes the data files to be downloaded by the client into several serialized files, and creates serialization metafiles for each data file to describe the serialization information; When each SFTP client downloads any data file from the corresponding SFTP server, it first downloads the serialization metafile of the data file, then downloads the corresponding serialized files according to the serialization metafile, and retains the serial number of the serialized file currently being downloaded when the download is interrupted.

8. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Each MQ connection in the system is defined based on the name of each node in the system. When any node in the system detects a change in its own IP address, the node updates the MQ connection with its next node and registers with its previous node with the new IP address. After receiving the registration, the previous node updates its MQ connection with this node.

9. The method according to claim 1, characterized in that, Also includes: When the airborne data node notifies the ground link master node to download the flight data, it also informs the ground link master node of the first range; Based on this, the ground link master node determines the MQ route and SFTP transmission path for the ground service nodes in the first range.

10. A flight data transmission system, characterized in that, include: Airborne data nodes located on the aircraft, ground link master nodes located on the ground, and ground service nodes; When communication between the airborne data node and the ground link master node fails, the airborne data node stores the flight data in its local memory. When communication is possible between the airborne data node and the ground link master node, a VPN connection is established between the airborne data node and the ground link master node; When a VPN connection is established between the airborne data node and the ground link master node and there is flight data to be downloaded, the airborne data node notifies the ground link master node to download the flight data. The ground link master node downloads the flight data from the local storage via SFTP and, as the MQ agent node of the airborne data node, notifies the ground service nodes in the first range to download the flight data via SFTP using MQ messages.

Images