Method and system for air / ground data transmission

Abstract

Methods and systems for air / ground data transmission are provided. The system comprises an application layer, a session / transport layer, a QUIC / TLS layer, a User Datagram Protocol (UDP) layer, an Internet Protocol (IP) layer and a LINK / PHY (Physical) layer. If the data is small, the session / transport layer selects an MQTT transport protocol for control plane communication. If the data is large, the session / transport layer selects an rsync / SSH protocol for data plane communication.

Description

Technical Field

[0001] The present disclosure relates generally to data communications and, more particularly, to methods and systems for air / ground data transmission. Background Art

[0002] Existing networking infrastructure that facilitates connectivity between aircraft and ground systems includes Wi-Fi, cellular, and satellite communications. However, these networking infrastructures share common limitations, including packet loss during data transmission, significant latency, limited bandwidth, and challenging environmental conditions that require frequent network interruptions and switching.

[0003] Currently, communications between aircraft and ground systems typically rely on file transfers for all data types and sizes. This presents a challenge when using Wi-Fi, cellular, and satellite communications, as bandwidth constraints result in slow data transfer rates. Bandwidth asymmetry (ground systems typically have five times more available bandwidth than aircraft) exacerbates this problem. Furthermore, the inherent instability of network connections caused by the dynamic nature of aircraft motion (whether in active flight, on the tarmac, or encountering obstacles) contributes to slow packet transmission or packet drops.

[0004] File and data transfers that rely on TCP / IP protocols further suffer from slow network switching and inefficient use of an already limited environment. Taken together, these performance limitations significantly hinder file and data transfers between aircraft and ground systems. Summary of the Invention

[0005] An illustrative embodiment provides an air / ground data transmission (AGDT) system for data transmission. The system includes an application layer configured to receive data and present the data in a format suitable for further processing by subsequent layers. The system also includes a session / transport layer configured to receive data from the application layer, select a protocol for data transmission based on the data size, and append headers and control information specific to the selected protocol to the data. The selected protocol may include MQTT, in response to determining that the data is small, or rsync / SSH, in response to determining that the data is large. The system also includes a QUIC / TLS layer configured to receive processed data from the session / transport layer and manage the User Datagram Protocol (UDP) and Internet Protocol (IP) layers. The UDP layer is configured to append headers and control information specific to the source and destination port numbers, length information, and a checksum to the data. The IP layer is configured to append source and destination IP addresses to the data. The system includes a LINK / PHY (physical) layer configured to receive processed data from the QUIC / TLS layer and add a header and control information specific to a MAC address, frame type, and error checking information to the data. The LINK / PHY layer is configured to convert the data into an electrical signal.

[0006] In an illustrative embodiment, if the data does not require segmentation and reassembly, the data is smaller, and if the data requires segmentation and reassembly, the data is larger.

[0007] In an illustrative embodiment, the QUIC layer operates over UDP and adds headers and control information to reduce latency and improve congestion control. The TLS layer adds headers and control information to provide encryption, authentication, and integrity of the data.

[0008] In an illustrative embodiment, the LINK / PHY layer includes a transceiver configured to convert data into electrical signals. The LINK / PHY layer is coupled to an antenna configured to convert the electrical signals into radio signals for transmission via radio waves.

[0009] In an illustrative embodiment, an air / ground data transmission (AGDT) system for data reception includes a LINK / PHY (physical) layer configured to receive data and extract and decode header and control information specific to the MAC address, frame type, and error checking information from the data. The system also includes a QUIC / TLS layer configured to receive processed data from the LINK / PHY layer and manage the User Datagram Protocol (UDP) and Internet Protocol (IP) layers. The IP layer is configured to extract and decode header and control information specific to the source and destination IP addresses from the data. The UDP layer is configured to extract and decode header and control information specific to the source and destination port numbers, length information, and a checksum from the data. The system also includes a session / transport layer configured to receive processed data from the QUIC / TLS layer and, during the transmission phase, extract and decode header and control information specific to the selected protocol from the data. The system includes an application layer configured to receive processed data from the session / transport layer and present the data in a format suitable for an end-user application.

[0010] In an illustrative embodiment, a method for air / ground data transmission includes receiving data at an application layer and presenting the received data in a format suitable for further processing. The method includes determining, by a session / transport layer, a protocol for data transmission and adding a header and control information specific to the protocol to the data. If the data is small, the MQTT protocol is selected, and if the data is large, the rsync / SSH protocol is selected. The method includes receiving, by a QUIC / TLS layer, processed data from the session / transport layer. The QUIC / TLS layer is configured to manage a UDP layer and an IP layer. The UDP layer is configured to add a header and control information specific to the source and destination port numbers, length information, and a checksum to the data. The IP layer is configured to add a header and control information specific to the source and destination IP addresses to the data. The method includes adding, by a LINK / PHY layer, a header and control information specific to the MAC address, frame type, and error checking information to the data.

[0011] In an illustrative embodiment, a method for air / ground data transmission includes receiving data from radio waves at a LINK / PHY layer and extracting and decoding, by the LINK / PHY layer, control information specific to a MAC address, frame type, and error checking information from the data. The method also includes receiving, by the QUIC / TLS layer, processed data from the LINK / PHY layer. The QUIC / TLS layer is configured to manage the User Datagram Protocol (UDP) layer and the Internet Protocol (IP) layer. The IP layer is configured to extract and decode, from the data, headers and control information specific to source and destination IP addresses, and the UDP layer is configured to extract and decode, from the data, headers and control information specific to source and destination port numbers, length information, and a checksum. The method also includes receiving, at a session / transport layer, processed data from the QUIC / TLS layer and selecting a protocol for processing the data by the session / transport layer. If the data is small, the MQTT protocol is selected, and if the data is large, the rsync / SSH protocol is selected. The method also includes receiving, at an application layer, processed data from the session / transport layer and presenting the data in a format suitable for an end-user application. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The novel features which are believed to be characteristic of the illustrative embodiments are set forth in the appended claims. However, the illustrative embodiments together with the preferred mode of use, further objects and features thereof will be best understood by reference to the following detailed description of illustrative embodiments of the disclosure when read in conjunction with the accompanying drawings, in which:

[0013] Figure 1 shows a network of data processing systems in which the illustrative embodiments may be implemented;

[0014] Figure 2 is a block diagram of a system for air / ground data transmission (AGDT) according to an illustrative embodiment;

[0015] Figure 3 shows a communication stack of an AGDT according to an illustrative embodiment;

[0016] Figure 4 and Figure 5 It is a state machine diagram showing the different states data can exist during the transmission and reception phases respectively.

[0017] Figure 6 shows the processing of a large data set with rsync by the various layers of AGDT during the transmit and receive phases; and

[0018] Figure 7 The processing of small data with MQTT by various layers of AGDT during the transmission and reception phases is shown. DETAILED DESCRIPTION

[0019] The illustrative embodiments provide a method and system for Air / Ground Data Transfer (AGDT). AGDT is designed to facilitate secure, robust, and efficient bidirectional data transmission between aircraft and ground-based systems. AGDT addresses and alleviates current data transmission limitations by optimizing the existing networking infrastructure connecting aircraft and ground systems.

[0020] refer to Figure 1 , depicts a pictorial representation of a network of data processing systems in which the illustrative embodiments may be implemented. Network data processing system 100 is a network of computers in which the illustrative embodiments may be implemented. System 100 may be used to facilitate air / ground data transfers.

[0021] System 100 contains network 102, which is the medium used to provide communications links between various devices and computers connected within network data processing system 100. Network 102 may include connections such as wire, wireless communication links, fiber optic cables, or coaxial cables.

[0022] In the depicted example, server computers 104 and 106 and storage unit 108 are connected to network 102 via communication link 112, which may include wired, fiber optic cables, coaxial cables, and wireless links. Server computers 104 and 106 and storage unit 108 may be based on land-based systems. Furthermore, aircraft computer system 110 is connected to network 102 via wireless link 114. Aircraft computer system 110 may also be connected to network 102 via satellite 130 and wireless link 114. Aircraft computer system 110 includes computers, tablet computers, and other computing devices.

[0023] exist Figure 1 In the illustrative embodiment, server computers 104 and 106 , storage unit 108 , and aircraft computer system 110 are network devices connected to network 102 , which is the communication medium for these network devices.

[0024] Program code located in network data processing system 100 may be stored on computer-recordable storage media and downloaded to a data processing system or other device for use. For example, program code may be stored on computer-recordable storage media on server computers 104 and 106 and storage unit 108. Furthermore, program code may be stored in aircraft computer system 110.

[0025] exist Figure 1In the illustrative embodiment, network 102 may be the Internet, which represents a worldwide collection of networks and gateways that use the Transmission Control Protocol / Internet Protocol (TCP / IP) suite of protocols to communicate with one another. Network data processing system 100 may also be implemented using different types of networks. For example, network 102 may include an intranet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or a switched telephone network. Figure 1 It is intended as an example, not as an architectural limitation for the different illustrative embodiments.

[0026] Figure 2 is a block diagram of a system 200 for air / ground data transmission between an aircraft 204 and a ground-based system 206, according to an illustrative embodiment. Aircraft 204 includes an air / ground data transmission (AGDT) 208, and ground-based system 206 includes AGDT 210. AGDT 208 and AGDT 210 are designed to facilitate bidirectional data transmission between aircraft 204 and ground-based system 206.

[0027] As described in detail below, end-user applications generate data that is processed by AGDT 208 and transmitted to ground-based system 206. AGDT 208 processes data received from ground-based system 206. Similarly, AGDT 210 transmits data to aircraft 204 and processes data received from aircraft 204.

[0028] System 200 includes a ground-based antenna 212 that communicates bidirectionally with aircraft 204 via a wireless link 214. In a transmit mode, antenna 212 converts electrical or optical signals received from network 216 into radio signals that propagate over radio waves and are received by aircraft 204. In a receive mode, antenna 212 converts radio signals transmitted by aircraft 204 into electrical or optical signals that are then transmitted to network 216 via a communication link 218.

[0029] Network 216 facilitates bidirectional communication between antenna 212 and land-based system 206. Network 216 transmits electrical or optical signals to antenna 212 via communication link 218 and receives electrical or optical signals from antenna 212 via communication link 218. Similarly, network 216 receives electrical or optical signals from land-based system 206 via communication link 220 and transmits electrical or optical signals to land-based system 206 via communication link 220.

[0030] Network 216 may be, for example, the Internet, a telephone switching network, an intranet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or any other telecommunications infrastructure that facilitates data communication between antenna 212 and network 216. Communication links 218 and 220 are physical links that allow antenna 212, network 216, and land-based system 206 to exchange data. Communication links 218 and 220 may take different forms, including wired connections such as wirelines, fiber optic cables, coaxial cables, and Ethernet cables.

[0031] Figure 3 The communication stack of AGDT 300 is shown in accordance with an illustrative embodiment. The communication stack comprises various layers. During the transmission and reception phases, data undergoes processing through various layers, with each layer serving a specific function to ensure secure, efficient, and reliable communication between aircraft 204 and ground-based systems 206. The choice of protocol and the use of specific layers help optimize data transmission in various situations within the aviation communication environment.

[0032] The AGDT 300 can be configured as the AGDT 208 installed in the aircraft 204 . Additionally, the AGDT 300 can be configured as the AGDT 210 installed in the ground-based system 206 .

[0033] The process begins during the transmission phase when an end-user application provides data to the application layer 302. The end-user application may include a word processor, a web browser, an email client, a database, or a storage device. The data may include text data, numeric data, image data, video data, audio data, binary data, telemetry data, and geospatial data.

[0034] The application layer 302 serves as an interface between the end-user application and the rest of the communication stack of the AGDT 300. The application layer 302 presents raw data in a format that the next layer in the stack can understand. At this stage, no special headers or trailers are added to the data packet. In some exemplary embodiments, the application layer 302 is implemented in software.

[0035] Data from the application layer 302 is handed over to the session / transport layer 304. Within the session / transport layer 304, the size of the data determines which protocol to use for data transmission. If the data is small and does not require segmentation, the Message Queuing Telemetry Transport (MQTT) protocol 306 is selected, serving as the control plane for communication. This data can include short messages containing an aircraft's designated gate number or a passenger's baggage claim area code. MQTT is a lightweight publish-subscribe messaging protocol designed for efficient communication between devices. MQTT is suitable for scenarios with low bandwidth, high latency, or unreliable networks. At this stage, headers and control information specific to the MQTT protocol are added to the data packet.

[0036] If the data is large and thus requires segmentation and reassembly, the rsync / SSH protocol 308 is selected, which serves as the data plane. Remote Sync (rsync) is a file synchronization and transfer protocol that efficiently transfers and updates files between devices. Rsync minimizes data transfer by sending only the difference (delta) between the source and destination files. Secure Shell (SSH) is an encrypted network protocol that provides a secure channel over an insecure network. When combined with rsync, SSH ensures secure communication during file synchronization and transfer. At this stage, headers and control information specific to the rsync and SSH protocols are added to the data packets. In some exemplary embodiments, the session / transport layer 304 is implemented in software, while in other embodiments, the session / transport layer 304 is implemented in hardware.

[0037] Once the session / transport layer 304 determines the protocol to use, the data is passed to the QUIC / TLS 1.3 layer 310, either locally or via MQTT and a proxy layer between QUIC and SSH. QUIC is responsible for providing a secure and optimized transport channel for data transmission. QUIC is a transport layer protocol designed to provide an optimized and secure alternative to traditional TCP. QUIC operates on top of the User Datagram Protocol, a combination that offers benefits such as reduced latency, improved congestion control, and seamless network switching. Transport Layer Security (TLS 1.3) is a cryptographic protocol that ensures secure communications over computer networks. TLS 1.3 provides encryption and authentication of data during transmission. QUIC adds headers and control information specific to reducing latency and improving congestion control. TLS 1.3 adds headers and control information specific to encryption, authentication, and integrity information to data packets. In some exemplary embodiments, the QUIC / TLS 1.3 layer 310 is implemented in software.

[0038] In some exemplary embodiments, QUIC / TLS 1.3 layer 310 is configured to receive processed data from the session / transport layer and manage the User Datagram Protocol (UDP) layer 312 and the Internet Protocol (IP) layer 314. UDP layer 312 is a connectionless transport layer protocol that provides faster, but less reliable, data transmission than TCP. UDP layer 312 was chosen for its efficiency and speed, making it suitable for scenarios where real-time communication is critical. UDP layer 312 adds header and control information specific to the source and destination port numbers, length information, and a checksum for error detection. IP layer 314 adds header and control information specific to the source and destination IP addresses, version, time to live (TTL), and protocol type to the data. IP layer 314 ensures that data packets are properly addressed and directed to their intended destination.

[0039] The processed data is handed to the LINK / PHY (physical) layer 316, which handles the physical transmission of the data. The LINK / PHY layer 316 adds a header and control information specific to the MAC address, frame type, and error checking to the data. The LINK / PHY layer 316 includes a transceiver ( Figure 3 Not shown in Figure 1). At this stage, modulation and coding techniques are applied to the digital signal. The transceiver can be coupled to an antenna ( Figure 3 ), which converts electrical signals into radio signals for transmission via radio waves.

[0040] During the receive phase, the process begins by receiving a radio signal containing data. The antenna converts the radio signal into an electrical signal, which is then converted into a digital signal by the transceiver. During this phase, the transceiver can perform demodulation and decoding to convert the electrical signal into digital data. The demodulation process involves extracting the original digital bits from the received radio signal.

[0041] The QUIC / TLS layer 310 receives processed data from the LINK / PHY layer 316. The QUIC / TLS layer 310 is configured to manage the User Datagram Protocol (UDP) layer 312 and the Internet Protocol (IP) layer 314. The IP layer 314 is configured to extract and decode the header and control information specific to the source and destination IP addresses from the data. The UDP layer 312 is configured to extract and decode the header and control information specific to the source and destination port numbers, length information, and a checksum from the data.

[0042] Next, the data moves up to the session / transport layer 304, either locally or via the proxy layer between QUIC and MQTT and between QUIC and SSH. At this stage, the protocol used for data transmission (MQTT or rsync / SSH) is determined based on protocol-specific information extracted from the received data, such as headers and control information.

[0043] Once the protocol is determined, the data is passed up to the application layer 302. If the rsync / SSH protocol 308 is selected, the rsync / SSH protocol securely handles the transfer and synchronization of files, extracting the original file from the received data. If the MQTT protocol is selected, the application layer 304 processes the data using a publish-subscribe model, extracting the message payload.

[0044] The application layer 302 presents the data in a format that the end-user application can understand. At this stage, the data is fully decoded and interpreted based on the requirements of the end-user application. This can involve converting binary data into a readable format such as text, images, or any other type of information.

[0045] Figure 4 4 is a state machine diagram 400 illustrating the various states that data can exist in and the transitions between these states during a transfer phase. In some implementations, the state machine is implemented using software, hardware, firmware, and other technologies such as field programmable gate arrays (FPGAs) and programmable logic controllers (PLCs).

[0046] Initially, the data is in state 402. In this state, the data can reside in the application layer. If the data is small and does not need to be segmented, the data is transitioned to state 404 for processing using the MQTT protocol. Such data may include a short message containing an airplane's designated gate number or a passenger's baggage claim area code. MQTT is a lightweight publish-subscribe messaging protocol designed for efficient communication between devices. MQTT is well suited for scenarios with low bandwidth, high latency, or unreliable networks. At this stage, headers and control information specific to the MQTT protocol are added to the data packet. After processing using the MQTT protocol, the data is transitioned to state 406 for processing using the QUIC / TLS1.3 protocol.

[0047] If the data is large and requires segmentation and reassembly, it transitions to state 408 for processing using the rsync protocol. Rsync is a file synchronization and transfer protocol that efficiently transfers and updates files between devices. Rsync minimizes data transfer by sending only the differences (deltas) between the source and destination files. At this stage, header and control information specific to the rsync protocol is added to the data packet.

[0048] After processing using the rsync protocol, the data transitions to state 410 for processing using the SSH protocol. SSH is an encrypted network protocol that provides a secure channel over an insecure network. At this stage, headers and control information specific to the SSH protocol are added to the data packet. When combined with rsync, SSH ensures secure communication during file synchronization and transfer. After processing using the SSH protocol, the data transitions to state 406 for processing using the QUIC / TLS1.3 protocol.

[0049] QUIC / TLS 1.3 provides a secure and optimized transport channel for data transmission. QUIC is a transport layer protocol designed to provide an optimized and secure alternative to traditional TCP. TLS 1.3 is a cryptographic protocol that ensures secure communication over computer networks. TLS 1.3 provides encryption and authentication of data during transmission. QUIC adds headers to data packets for reduced latency and improved congestion control. TLS 1.3 adds encryption, authentication, and integrity information to data packets.

[0050] After processing using the QUIC / TLS 1.3 protocol, the data is transitioned to state 412 for processing using the UDP protocol. UDP is a connectionless transport protocol that provides faster, but less reliable, data transmission than TCP. The UDP protocol was chosen for its efficiency and speed, making it suitable for scenarios where real-time communication is crucial. At this stage, a header and control information specific to the source and destination port numbers, length information, and a checksum are added to the data packet.

[0051] The processed data is transitioned to state 414 for processing using the Internet Protocol. The Internet Protocol ensures that the data packets are properly addressed and directed to their intended destination. At this stage, header and control information specific to the source and destination IP addresses, version, time to live (TTL), and protocol type are added to the data packet.

[0052] Data processed using the Internet Protocol is then transitioned to state 416 for LINK layer processing. The Link layer provides reliable and error-free communication between directly connected devices over the local network. At this stage, a header and control information specific to the MAC address, frame type, and error checking are added to the data packet.

[0053] The data processed by the LINK layer is transferred to state 418 for processing by the PHY layer. The PHY layer handles the physical transmission of the data. The PHY layer converts digital data into electrical signals, which are transmitted as radio signals over radio waves.

[0054] Figure 55 is a state machine diagram 500 illustrating the various states that data may exist in and the transitions between these states during the receive phase. In some implementations, the state machine is implemented using software, hardware, firmware, and other technologies such as field programmable gate arrays (FPGAs) and programmable logic controllers (PLCs).

[0055] In state 502, a radio signal containing data is received and converted to an electrical signal by physical hardware. The physical hardware may include an antenna coupled to a transceiver. The antenna receives the radio signal and converts it to an electrical signal, which is then converted to a digital signal (e.g., data) by the transceiver. The transceiver may perform demodulation and decoding to convert the electrical signal to digital data.

[0056] The data packet is then transitioned to state 504 for processing by the link layer, which extracts the header and control information specific to the source and destination MAC addresses, the frame type, and other control information from the data packet. The link layer retrieves the payload, or data portion, from the data packet. The link layer also performs error checking to ensure the integrity of the data packet by detecting any transmission errors.

[0057] Next, the data transitions to state 506 for processing by the IP layer. In this stage, header and control information specific to the source and destination IP addresses, version, time to live (TTL), and protocol type are extracted and decoded from the data packet.

[0058] Next, the data transitions to state 508 for UDP layer processing. In this stage, the header and control information specific to the source and destination port numbers are extracted and decoded from the data packet, and the UDP checksum is verified for data integrity to ensure that the data has not been damaged during transmission.

[0059] Next, the data transitions to state 510 for processing by QUIC / TLS 1.3 layer 310 for decryption. At this stage, the header and control information are decrypted along with the original data. TLS 1.3 handles the decryption and verifies the integrity of the data. The result is the original data in unencrypted form.

[0060] If the data is processed using the MQTT protocol during the transfer phase, the data transitions to state 512 for MQTT processing. In this phase, the data is processed using a publish-subscribe model, the payload is extracted, and the data is reconstructed into its original form. The reconstructed data transitions to state 518.

[0061] If the data is processed using the rsync / SSH protocol during the transfer phase, the data transitions from state 510 to state 514. In this phase, the data is processed using the SSH protocol, which provides a secure channel over an insecure network.

[0062] Next, the data is transitioned to state 516 for synchronization using the rsync protocol. Rsync minimizes data transfer by extracting only the differences between the source and destination files, and the files are synchronized. The data is reconstructed into its original form and the reconstructed data is transitioned to state 518.

[0063] The AGDT 300 addresses and overcomes the shortcomings associated with existing communication systems between aircraft and ground systems. Unlike existing systems that rely on traditional file transfers using the TCP / IP protocol, the AGDT 300 introduces a dynamic approach that determines which protocol to use based on the size of the data being transferred. For small data sizes, the AGDT 300 employs the MQTT protocol, which is designed for efficient communication in scenarios with low bandwidth, high latency, or unreliable networks. By using MQTT for short messages, such as an aircraft's gate number or a passenger's baggage claim area code, the AGDT 300 ensures fast and reliable communication without the need for heavy file transfer protocols.

[0064] In some exemplary embodiments, control plane messages are typically small, requiring minimal segmentation and reassembly, and such messages are transmitted via MQTT. For example, for small data (e.g., less than 20MB), MQTT is selected because the data can be transmitted with minimal segmentation and reassembly.

[0065] In situations where large data sets require segmentation and reassembly, the AGDT 300 utilizes an rsync / SSH protocol combination. Rsync is a well-known file synchronization and transfer protocol, known for its efficiency in transferring only the differences between the source and destination files, reducing data transfer requirements. The integration of SSH ensures secure communication during the file synchronization and transfer process, thus addressing issues related to the security of transferred data.

[0066] The AGDT 300 addresses bandwidth asymmetry between aircraft and ground systems by intelligently selecting protocols. This prevents network overload with unnecessary data and optimizes the use of available bandwidth, thereby enhancing overall data transmission efficiency. The AGDT 300 addresses the inherent instability of network connections caused by the dynamic nature of aircraft motion. Designed for scenarios with unreliable networks, the use of MQTT and rsync / SSH ensures adaptability to varying network conditions, reducing the likelihood of slow or dropped packet transmissions.

[0067] Figure 6The processing of a large data set with rsync by the various layers of AGDT 300 during the transmission and reception phases is shown. During the transmission phase, data 602 is processed and encapsulated by the rsync layer into rsync packets 604. The SSH layer processes rsync packets 604 and encapsulates them into SSH packets 606. The QUIC layer processes and encapsulates SSH packets 606 into QUIC packets 608. The UDP layer processes QUIC packets 608 and encapsulates them into UDP packets 610. Finally, the IP layer processes UDP packets 610 and encapsulates them into IP packets 612.

[0068] During the receive phase, the IP layer extracts the IP header from the IP packet 612 and provides the UDP packet 610 to the UDP layer. Next, the UDP layer decodes the UDP header from the UDP packet 610 and provides the QUIC packet 608 to the SSH layer.

[0069] Next, the SSH layer processes the QUIC packet 608 to provide a secure channel and provides the rsync packet 606 to the rsync layer. The rsync layer synchronizes and reassembles the rsync packet 604 into the original data 602.

[0070] Figure 7 The processing of small data with MQTT by the various layers of AGDT 300 during the transmission and reception phases is shown. During the transmission phase, data 702 is processed and encapsulated into MQTT packets 704 by the MQTT layer. Next, the QUIC layer processes the MQTT packets 704 and encapsulates them into QUIC packets 706. Next, the UDP layer processes the QUIC packets 706 and encapsulates them into UDP packets 708. Finally, the IP layer processes the UDP packets 708 and encapsulates them into IP packets 710.

[0071] During the receive phase, the IP layer extracts the IP header from the IP packet 710 and provides the UDP packet 708 to the UDP layer. Next, the UDP layer decodes the UDP header from the UDP packet 708 and provides the QUIC packet 706 to the QUIC layer. Next, the QUIC layer processes the QUIC packet 706 and provides the MQTT packet 704 to the MQTT layer, which then reassembles the data packets into the original data 702.

[0072] As used herein, the phrase "number" means one or more. When used with a list of items, the phrase "at least one" means that different combinations of one or more of the listed items can be used, and only one of each item in the list may be required. In other words, "at least one" means that any combination of the items in the list and the number of items can be used, but not all items in the list are required. An item can be a specific object, thing, or category.

[0073] For example, but not limited to, "at least one of item A, item B, or item C" may include item A, item A and item B, or item C. This example may also include item A, item B, and item C, or item B and item C. Of course, any combination of these items may exist. In some illustrative examples, "at least one" may be, for example, but not limited to, two items A, one item B, and ten items C, four items B, and seven items C, or other suitable combinations.

[0074] The flowcharts and block diagrams in the various described embodiments illustrate the architecture, functionality, and operation of some possible implementations of the devices and methods in the illustrative embodiments. In this regard, each block in the flowchart or block diagram may represent at least one of a module, a segment, a function, and a portion of an operation or step. For example, one or more blocks may be implemented as program code.

[0075] In some alternative implementations of the illustrative embodiments, one or more functions indicated in the blocks may occur out of the order indicated in the figures. For example, in some cases, two blocks shown in succession may be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functions involved. Furthermore, other blocks may be added in addition to the blocks shown in the flowchart or block diagram.

[0076] The descriptions of the different illustrative embodiments have been presented for the purposes of illustration and description, and the descriptions are not intended to be exhaustive or limited to the embodiments in the disclosed form. The different illustrative examples describe components that perform actions or operations. In the illustrative embodiments, the components can be configured to perform the described actions or operations. For example, the components can have a configuration or design of a structure that provides the component with the ability to perform the actions or operations described as being performed by the component in the illustrative examples. Many modifications and variations will be apparent to those of ordinary skill in the art. In addition, different illustrative embodiments may provide different features compared to other desired embodiments. The selected one or more embodiments are selected and described in order to best explain the principles of the embodiments, practical applications, and to enable others of ordinary skill in the art to understand the disclosure of various embodiments with various modifications suitable for the specific purposes envisioned.

Claims

1. An air / ground data transmission (AGDT) system (300) for data transmission, comprising: an application layer (302) configured to receive data and present said data in a format suitable for further processing by subsequent layers; A session / transport layer (304) configured to receive the data from the application layer and select a protocol for data transmission based on the size of the data and add a header and control information specific to the selected protocol to the data, wherein the selected protocol includes: MQTT (306), in response to determining that the data is small; or rsync / SSH (308), in response to determining that the data is large; a QUIC / TLS layer (310) configured to receive processed data from the session / transport layer (304) and manage a User Datagram Protocol (UDP) layer (312) and an Internet Protocol (IP) layer (314), wherein the UDP layer (312) is configured to add a header and control information specific to a source port number and a destination port number, length information, and a checksum to the data, and wherein the IP layer (314) is configured to add a source IP address and a destination IP address to the data; and A LINK / PHY layer (316) is configured to receive processed data from the QUIC / TLS layer (310) and add a header and control information specific to a MAC address, a frame type, and error checking information to the data, wherein the LINK / PHY layer (316) is configured to convert the data into an electrical signal.

2. The system according to claim 1, wherein: If the data does not need to be segmented and reassembled, the data is smaller.

3. The system according to claim 1, wherein: If the data needs to be segmented and reassembled, the data is larger.

4. The system according to claim 1, wherein: The QUIC layer operates over UDP and adds the header and control information to reduce latency and improve congestion control, and wherein the TLS layer adds the header and control information to provide encryption, authentication, and integrity of the data.

5. The system according to claim 1, wherein The LINK / PHY layer includes a transceiver configured to convert the data into the electrical signal.

6. The system according to claim 5, wherein: The LINK / PHY layer is coupled to an antenna, which is configured to convert the electrical signal into a radio signal for transmission over radio waves.

7. An air / ground data transmission (AGDT) system (300) for data reception, comprising: a LINK / PHY layer (316) configured to receive data and extract and decode header and control information specific to a MAC address, frame type, and error checking information from the data; a QUIC / TLS layer (310) configured to receive processed data from the LINK / PHY layer and manage a User Datagram Protocol (UDP) layer (312) and an Internet Protocol (IP) layer (314), wherein the IP layer (314) is configured to extract and decode header and control information specific to a source IP address and a destination IP address from the data, and wherein the UDP layer (312) is configured to extract and decode header and control information specific to a source port number and a destination port number, length information, and a checksum from the data; a session / transport layer (304) configured to receive processed data from the QUIC / TLS layer (310) and to extract and decode headers and control information specific to the selected protocol from the data during a transport phase; and The application layer (302) is configured to receive the processed data from the session / transport layer and present the data in a format suitable for an end-user application.

8. The system according to claim 7, wherein: If the data is small, the session / transport layer selects the MQTT protocol for extraction and decoding, and if the data is large, the session / transport layer selects the rsync / SSH protocol for extraction and decoding.

9. The system according to claim 7, wherein: The TLS layer is configured to decrypt and authenticate the data during the transmission phase to check the integrity of the data.

10. The system according to claim 7, wherein: The LINK / PHY layer is coupled to an antenna configured to receive radio signals on radio waves and convert the radio signals into electrical signals.

11. The system according to claim 10, wherein: The LINK / PHY layer includes a transceiver configured to receive the electrical signal from the antenna and convert the electrical signal into data processed by the LINK / PHY layer.

12. A method for air / ground data transmission, comprising the following steps: receiving data at the application layer (302) and presenting the received data in a format suitable for further processing; determining, by the session / transport layer (304), a protocol for data transmission and adding a header and control information specific to the protocol to the data, wherein if the data is small, the MQTT protocol (306) is selected, and if the data is large, the rsync / SSH protocol (308) is selected; receiving, by a QUIC / TLS layer (310), processed data from the session / transport layer, wherein the QUIC / TLS layer (310) is configured to manage a User Datagram Protocol (UDP) layer (312) and an Internet Protocol (IP) layer (314), wherein the UDP layer is configured to add a header and control information specific to a source port number and a destination port number, length information, and a checksum to the data, and wherein the IP layer is configured to add a header and control information specific to a source IP address and a destination IP address to the data; and A header and control information specific to the MAC address, frame type, and error checking information is added to the data by the LINK / PHY layer (316).

13. The method according to claim 12, further comprising: The data is converted into electrical signals by the transceiver in the LINK / PHY layer.

14. The method according to claim 13, wherein The application layer receives the data from an end-user application.

15. The method according to claim 12, wherein: The MQTT protocol acts as a control plane for small data, and wherein the rsync / SSH protocol acts as a data plane for large data that requires segmentation and reassembly.

16. The method according to claim 12, wherein: If the data does not require segmentation and reassembly, the data is smaller, and wherein if the data requires segmentation and reassembly, the data is larger.

17. A method for air / ground data reception, comprising the following steps: receiving data from radio waves at a LINK / PHY layer (316) and extracting and decoding a header and control information specific to a MAC address, a frame type, and error checking information from the data by the LINK / PHY layer (316); receiving, by a QUIC / TLS layer (310), processed data from the LINK / PHY layer (316), wherein the QUIC / TLS layer (310) is configured to manage a User Datagram Protocol (UDP) layer (312) and an Internet Protocol (IP) layer (314), wherein the IP layer is configured to extract and decode header and control information specific to a source IP address and a destination IP address from the data, and wherein the UDP layer is configured to extract and decode header and control information specific to a source port number and a destination port number, length information, and a checksum from the data; receiving processed data from the QUIC / TLS layer (310) at a session / transport layer (304) and selecting a protocol for processing the data by the session / transport layer, wherein if the data is small, the MQTT protocol (306) is selected, and if the data is large, the rsync / SSH protocol (308) is selected; and The application layer (302) receives processed data from the session / transport layer and presents the data in a format suitable for an end-user application.

18. The method according to claim 17, wherein If the data does not require segmentation and reassembly, the data is smaller, and wherein if the data requires segmentation and reassembly, the data is larger.

19. The method of claim 17, further comprising: receiving a radio signal on the radio wave by an antenna coupled to the LINK / PHY layer; as well as The radio signal is converted into an electrical signal by the antenna.

Images