A multi-level cache hierarchical transmission system and method for UAVs across security boundaries based on MQTT.
By employing a multi-level caching architecture and hierarchical transmission mechanism for both internal and external networks, the problems of data congestion and low resource utilization in cross-network transmission of UAVs are solved, achieving efficient and secure cross-network data transmission and ensuring the real-time performance and security of UAV missions.
Patent Information
- Application Number
- CN202611344758.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-01
- Publication Date
- 2026-11-17
AI Technical Summary
The existing MQTT cross-network transmission technology for drones lacks a multi-level caching mechanism, which cannot simultaneously meet the needs of fast forwarding of high real-time data and persistent storage of large volumes of non-real-time data. Urgent commands are easily blocked by low-priority data, and the utilization rate of internal and external network cache resources is low, making it difficult to meet the requirements of real-time, reliability and security.
A two-level multi-level caching architecture with symmetrical deployment of internal and external networks is adopted. The memory cache is used for second-level real-time data, and the disk cache is used for minute-level and non-real-time data. Combined with a hierarchical rule engine, queuing and scheduling unit and cache collaborative management unit, hierarchical storage and priority transmission of data instructions are realized. Cross-network transmission is carried out through MQTT cross-network scheduling gateway, and differentiated security verification is performed under the control of security boundary isolation unit.
It enables rapid access and forwarding of high real-time data, ensures that the transmission latency of emergency commands is within 1 second, improves the real-time response capability and operational safety of UAVs in cross-network operations, optimizes network resource utilization, and ensures the security and compliance of data transmission.
Smart Images

Figure CN123123447A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of unmanned aerial vehicle (UAV) communication, network security isolation, and MQTT message transmission technology, specifically to an MQTT-based UAV multi-level cache hierarchical transmission system and method across security boundaries. Background Technology
[0002] In professional application scenarios such as industrial inspection, security monitoring and emergency rescue, drones need to connect to both the control platform deployed on the intranet and the cloud server on the extranet when performing tasks. However, there are usually security boundary devices such as network gateways and firewalls deployed between the intranet and the extranet. These devices strictly limit the bidirectional penetration of data, which makes the cross-network data transmission and control command issuance of drones face severe transmission challenges.
[0003] The MQTT protocol, with its advantages of being lightweight, low-power, and using a publish / subscribe model, has become the mainstream communication protocol in the field of drone data transmission; however, existing drone MQTT cross-network transmission technology solutions still have the following significant drawbacks:
[0004] First, there is a lack of multi-level caching mechanisms adapted to cross-security boundary scenarios. Existing solutions generally use a single-level cache to store all types of data, which cannot meet the needs of fast forwarding of high real-time data and persistent storage of large-volume non-real-time data, and is prone to data congestion or even loss.
[0005] Second, the data commands were not transmitted in a tiered queuing manner to address the differences in real-time performance. Emergency flight control commands, routine telemetry data, and log files were transmitted together, which made it easy for high-priority, second-level commands to be blocked by low-priority, high-volume data, thus failing to guarantee the transmission latency requirements of emergency commands.
[0006] Third, the lack of coordinated management of cache resources on both the internal and external networks leads to low data synchronization efficiency during cross-network transmission. Furthermore, the cache scheduling strategy is not linked with the hierarchical transmission rules, resulting in low network resource utilization and making it difficult to meet the complex requirements of UAVs in terms of real-time performance, reliability, and security when operating across safety boundaries. Summary of the Invention
[0007] This invention aims to at least partially solve one of the technical problems in related technologies. To this end, one object of this invention is to propose an MQTT-based multi-level cached hierarchical transmission system for unmanned aerial vehicles across security boundaries, comprising:
[0008] The intranet domain is equipped with an intranet MQTT proxy server, an intranet multi-level caching module, an intranet management and control platform, and an intranet access authentication unit.
[0009] The external network domain is equipped with an external MQTT proxy server, an external multi-level caching module, a cloud management platform, and external terminals. The external network domain is physically isolated from the internal network domain.
[0010] A security boundary isolation unit is deployed between the internal network domain and the external network domain and is configured to block direct communication between the internal network domain and the external network domain.
[0011] The MQTT cross-network scheduling gateway connects to both the intranet multi-level caching module and the extranet multi-level caching module, and has a built-in hierarchical rule engine, queuing scheduling unit, and cache collaborative management unit.
[0012] The hierarchical rule engine is configured to divide the transmitted data instructions into at least high real-time level, medium real-time level and non-real-time level according to real-time requirements;
[0013] The queuing scheduling unit is configured to establish a priority transmission queue based on the partitioning results of the hierarchical rule engine;
[0014] The cache collaborative management unit is configured to control the hierarchical storage and status synchronization of data between the intranet multi-level cache module and the extranet multi-level cache module.
[0015] Preferably, both the intranet multi-level cache module and the extranet multi-level cache module adopt a two-level cache architecture, including a first-level memory cache dedicated to storing high real-time data instructions and providing high-speed read and write, and a second-level disk cache that stores real-time and non-real-time data instructions in different regions and provides persistent storage.
[0016] Preferably, the hierarchical rule engine is specifically configured to divide data instructions into second-level real-time categories, minute-level real-time categories, and non-real-time categories;
[0017] Among them, the transmission latency requirement for second-level real-time classes is less than or equal to 1 second, corresponding to the first transmission priority;
[0018] For minute-level real-time transmission, the transmission latency requirement is greater than 1 second and less than or equal to 60 seconds, corresponding to the second transmission priority.
[0019] For non-real-time transmissions, the latency requirement is greater than 60 seconds, corresponding to the third transmission priority.
[0020] The first transmission priority is higher than the second transmission priority, and the second transmission priority is higher than the third transmission priority.
[0021] Preferably, the hierarchical rule engine is further configured to identify the real-time level of data instructions based on the topic prefix of the MQTT message;
[0022] Among them, second-level real-time data instructions correspond to the first exclusive topic prefix set, minute-level real-time data instructions correspond to the second exclusive topic prefix set, and non-real-time data instructions correspond to the third exclusive topic prefix set.
[0023] Preferably, the queuing scheduling unit is configured as follows:
[0024] When there is a high real-time level data instruction in the priority transmission queue, a dedicated transmission channel is preempted for the high real-time level data instruction and its transmission is scheduled with priority.
[0025] When there are no high real-time level data commands, the real-time level data commands in the transmission are scheduled in batches at preset time intervals.
[0026] When there are no data commands of high real-time or medium real-time level, non-real-time level data commands are scheduled for transmission during network idle periods.
[0027] Preferably, the cache collaborative management unit is further configured as follows:
[0028] High real-time data instructions are written directly to the first-level memory cache, and the corresponding cache entries are cleared immediately after cross-network transmission is completed.
[0029] It writes real-time and non-real-time data commands to the secondary disk cache and supports fragmented storage and breakpoint resume status marking for non-real-time data commands.
[0030] Preferably, the security boundary isolation unit is a combined isolation device consisting of a hardware gateway and a firewall.
[0031] Preferably, the MQTT cross-network scheduling gateway also has a built-in security verification unit, which is configured to perform hierarchical security verification on data instructions transmitted across networks. Specifically, for data instructions with high real-time level, the focus is on performing digital signature and anti-replay verification, while for data instructions with medium real-time level and non-real-time level, the focus is on performing content auditing and format verification.
[0032] A method for hierarchical transmission of UAVs across security boundaries using MQTT-based multi-level buffers, applied to the aforementioned MQTT-based UAV hierarchical transmission system using multi-level buffers, includes the following steps:
[0033] S1. Initialization steps: The intranet multi-level cache module and the extranet multi-level cache module complete the cache partitioning according to the pre-configured real-time level;
[0034] S2. Grading determination step: The MQTT cross-network scheduling gateway receives the data instruction to be transmitted, and the grading rule engine identifies and determines the real-time level of the data instruction;
[0035] S3. Layered storage step: Based on the result of the layered determination step, the cache collaborative management unit distributes and stores the data instructions to the intranet cache partition corresponding to the real-time level.
[0036] S4. Hierarchical queuing transmission step: According to the result of the hierarchical determination step, the queuing scheduling unit adds the data instruction to the corresponding priority transmission queue, and controls the data instruction to complete the cross-network transfer transmission through the security boundary isolation unit in order of priority from high to low.
[0037] S5. Cache status synchronization step: After the data instruction completes cross-network transmission, the cache collaborative management unit synchronously cleans up the transmitted data in the corresponding cache partitions of the internal and external networks.
[0038] Preferably, the hierarchical queuing transfer step further includes:
[0039] High real-time level data commands are added to the first priority queue to preempt the transmission channel for immediate transmission, with a transmission delay of less than or equal to 1 second.
[0040] Add real-time data commands to the second priority queue and transmit them in batches at the first preset time interval;
[0041] Non-real-time data commands are added to the third priority queue and transmitted during network idle periods. Large data volumes are transmitted in chunks.
[0042] When a transmission interruption is detected, data instructions at both the real-time and non-real-time levels retain cached fragments in the secondary disk cache and resume transmission from the point of interruption after the network is restored.
[0043] The above-described solution of the present invention has at least the following beneficial effects:
[0044] By employing a two-level multi-level caching architecture with symmetrical deployment of internal and external networks, this invention uses a first-level memory-level high-speed cache dedicated to storing second-level real-time data instructions, providing microsecond-level read and write speeds to ensure rapid access and forwarding of highly real-time data; simultaneously, a second-level disk-level persistent cache is used to store minute-level real-time and non-real-time data instructions in separate areas, balancing the persistent storage requirements of large-capacity data with the ability to resume interrupted transmissions; this multi-level caching architecture effectively solves the technical contradiction that traditional single-level caching cannot simultaneously meet the dual requirements of transmission speed and storage capacity, avoiding data loss and network congestion caused by cache overflow;
[0045] By establishing a three-tiered real-time classification standard of second-level real-time, minute-level real-time, and non-real-time, and configuring corresponding priority transmission queues, this invention achieves refined hierarchical queuing transmission of data commands. High-priority second-level real-time data commands can preempt dedicated transmission channels and skip queuing, ensuring that the transmission delay of emergency flight control commands and real-time alarm information is strictly controlled within 1 second. Medium-priority minute-level data is transmitted in batches at scheduled times. Low-priority non-real-time data is transmitted during network idle periods. This hierarchical queuing mechanism completely solves the pain point of emergency commands being blocked by low-priority data, significantly improving the real-time response capability and operational safety of UAVs in cross-network operations.
[0046] By using a cache collaborative management unit to uniformly schedule and synchronize the status of cache resources on both the internal and external networks, this invention achieves efficient collaborative management and control of cross-network caches. This mechanism can automatically synchronize the cache data status of corresponding partitions on the internal and external networks, automatically clean up data that has been transmitted or expired to release cache space, and support the retention of transmitted fragments in the secondary cache for interruptions in the transmission of non-real-time large file data, so that transmission can continue from the breakpoint after the network is restored. This design significantly reduces the cross-network data retransmission rate and optimizes the allocation and utilization of network bandwidth resources.
[0047] This invention, while ensuring the physical isolation and security compliance of internal and external networks, combines a security boundary isolation unit and a hierarchical security verification strategy to achieve compliant cross-network transmission of data commands. It implements differentiated security verification granularity for data commands with different real-time requirements: for high-real-time commands, it focuses on performing digital signature and rapid replay protection verification; for non-real-time data, it focuses on performing content auditing and format verification. This design balances data security and transmission efficiency during cross-network transmission without increasing the transmission latency of high-real-time commands, fully adapting to the high security and compliance requirements of UAVs in professional operation scenarios such as industrial inspection and security monitoring.
[0048] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description
[0049] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.
[0050] Figure 1This is a schematic diagram of the overall architecture of a UAV cross-security boundary multi-level cache hierarchical transmission system based on MQTT provided in an embodiment of the present invention;
[0051] Figure 2 This is a schematic diagram of the structure of the multi-level caching module provided in an embodiment of the present invention;
[0052] Figure 3 This is a schematic diagram of a hierarchical queuing transmission process provided in an embodiment of the present invention.
[0053] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0054] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.
[0055] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "circumferential," and "radial," etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the accompanying drawings and are only for the convenience of describing this invention and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this invention.
[0056] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.
[0057] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.
[0058] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can include direct contact between the first and second features, or contact between the first and second features through another feature between them. Furthermore, "above," "over," and "on top" of the second feature includes the first feature directly above or diagonally above the second feature, or simply indicates that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature includes the first feature directly below or diagonally below the second feature, or simply indicates that the first feature is at a lower horizontal level than the second feature.
[0059] The following describes in detail, with reference to the accompanying drawings, an embodiment of the present invention: a multi-level cache hierarchical transmission system and method for unmanned aerial vehicles (UAVs) across security boundaries based on MQTT.
[0060] Example 1: System Overall Architecture and Composition
[0061] like Figure 1 As shown, this embodiment provides a multi-level cached hierarchical transmission system for UAVs across security boundaries based on MQTT. This system is mainly deployed in cross-network operation scenarios for power inspection UAVs, used to achieve reliable bidirectional data and command transmission between the UAV's onboard terminal and the internal network management platform and the external cloud management platform. The system consists of four main parts: internal network domain 1, external network domain 2, security boundary isolation unit 3, and MQTT cross-network scheduling gateway 4. The internal network domain is deployed in the confidential network environment within the power company, while the external network domain is deployed in the public cloud server environment. The two domains are isolated through a combination of physical and logical network isolation to ensure the security and compliance of core data within the internal network.
[0062] I. Detailed Structure of an Intranet Domain
[0063] Intranet Domain 1 is a core component of the system on the classified intranet side, undertaking the key functions of receiving UAV data, issuing intranet commands, managing local cache, and controlling permissions. Intranet Domain 1 specifically includes an intranet MQTT proxy server 101, an intranet multi-level cache module 102, an intranet management and control platform 103, and an intranet permission authentication unit 104.
[0064] The intranet MQTT broker server 101 is implemented using the standard MQTT protocol stack, and performs message topic distribution and connection management based on the publish / subscribe model. In actual deployment, the broker server is configured with a dedicated network port and enables TLS encrypted transmission to ensure the confidentiality of intranet communication links.
[0065] Its main functions include two aspects: First, receiving various data instruction messages from the UAV airborne MQTT client uploaded through the intranet wireless link, and routing the data to the intranet management platform 103 or the intranet multi-level cache module 102 according to the message topic;
[0066] Secondly, it receives control commands issued by the intranet management platform 103, publishes them to the corresponding downlink topics via the MQTT protocol, and is then subscribed to and executed by the UAV's onboard client.
[0067] The intranet MQTT agent server 101 maintains the session state of all connected clients, supports reconnection after disconnection and offline message queue functions, and ensures the connection stability of drones in the edge area of intranet coverage.
[0068] The intranet multi-level caching module 102 is one of the core innovative components of this invention, and its detailed structure is as follows: Figure 2 As shown.
[0069] This module adopts a two-level cache architecture design, specifically consisting of a first-level memory cache 501 and a second-level disk cache 502.
[0070] The Level 1 memory cache 501 is implemented based on a high-performance in-memory database, such as Redis or Memcached, and is dedicated to storing real-time data commands at the second level. Due to the microsecond-level random read and write latency of the memory medium, the Level 1 memory cache 501 can meet the extreme requirements of emergency flight control commands and real-time sensor data for access speed.
[0071] The secondary disk cache 502 is built on solid-state drives or hard disk drives and uses an embedded database or custom file storage format to provide large-capacity, persistent data storage capabilities. The secondary disk cache 502 is further divided into three logical partitions: second-level cache partition 503, minute-level cache partition 504, and non-real-time cache partition 505, which correspond to the data instruction storage requirements of the three real-time levels, respectively. The storage quota, data expiration policy, and cleanup rules of each partition can be configured and managed through the intranet management platform 103.
[0072] The intranet management platform 103 is the business processing and monitoring center on the intranet side. It is usually deployed on workstations or servers and provides a graphical user interface.
[0073] Maintenance personnel can view real-time telemetry data such as the drone's flight attitude, 3D position, power and voltage, and equipment temperature and humidity through the intranet management platform 103, and can issue flight control commands such as emergency return to home, hovering, and waypoint switching with one click.
[0074] The intranet management platform 103 also integrates management functions for multi-level cache modules, allowing administrators to configure parameters such as the capacity limit of the first-level memory cache, the storage quota of each partition of the second-level disk cache, and the time threshold for data expiration cleanup.
[0075] In addition, the intranet management platform 103 has data parsing and archiving capabilities, which can store the received drone data in the intranet historical database according to the time series for subsequent offline analysis and accident tracing.
[0076] The intranet authentication unit 104 is the security entry point for the intranet domain, responsible for authenticating the identities and controlling the permissions of all devices and users connected to the intranet MQTT agent server 101.
[0077] This unit maintains a whitelist of authorized devices and a user credential database. When a drone-borne terminal first connects, it needs to provide a pre-set digital certificate or device fingerprint for two-way authentication. Only after successful authentication can an MQTT connection be established.
[0078] Meanwhile, the intranet permission authentication unit 104 provides fine-grained control over the publishing and subscription permissions of MQTT topics. For example, it allows only specific drone terminals to publish emergency commands to the uav / sec / ctrl topic, and only allows the intranet management platform 103 to subscribe to the uav / min / tele topic to receive telemetry data.
[0079] By using a topic-based access control list mechanism, unauthorized devices are effectively prevented from accessing the intranet or operating drones without authorization, thus ensuring access security on the intranet side.
[0080] II. Detailed Structure of External Domains
[0081] External domain 2 is deployed in a public cloud or enterprise external network environment and is physically isolated from internal domain 1 through security boundary isolation unit 3. External domain 2 is symmetrical to internal domain 1 in architecture to simplify the complexity of cross-network collaborative management and control.
[0082] External domain 2 specifically includes an external MQTT agent server 201, an external multi-level caching module 202, a cloud management platform 203, and an external terminal 204.
[0083] The functions of the external MQTT broker server 201 are basically the same as those of the internal MQTT broker server 101, and they use the same MQTT protocol standard and topic naming convention.
[0084] The key difference between the two is that the external MQTT broker server 201 does not directly establish any network connection with the internal MQTT broker server 101. All cross-network data exchanges are completed through the MQTT cross-network scheduling gateway 4 via the security boundary isolation unit 3.
[0085] External MQTT proxy server 201 provides services to the public network and requires stronger DDoS protection and access rate limiting policies to cope with potential attack risks in the public network environment.
[0086] It receives remote instructions from the cloud management platform 203 and the external network terminal 204, and distributes the drone data that has been transmitted across the network to the corresponding subscribers according to the topic.
[0087] The external network multi-level cache module 202 and the internal network multi-level cache module 102 adopt a completely symmetrical two-level cache architecture, which also includes a first-level memory cache and a second-level disk cache. The storage partitions in the second-level cache are divided into three levels: second-level, minute-level, and non-real-time.
[0088] The main function of the external network multi-level cache module 202 is to receive and temporarily store drone data transmitted across the network from the internal network domain, as well as to temporarily store control commands waiting to be sent from the external network side to the internal network domain.
[0089] Since the transmission channel between the external network and the internal network is limited by the switching rate of the network gateway, the external network multi-level caching module 202 can effectively smooth out sudden data traffic and avoid data loss caused by cross-network link congestion.
[0090] The cloud management platform 203 is the core business system on the external network side. It is deployed on a cloud server and provides web-based remote access capabilities.
[0091] Its main tasks include long-term storage, in-depth analysis, and visualization of non-real-time data.
[0092] For example, a large number of high-definition aerial images, infrared thermal imaging data, and complete flight log files captured by drones during power line inspection missions are archived and stored in the cloud management platform 203.
[0093] Maintenance personnel can log in to the cloud management platform through a browser to view historical inspection records, generate equipment defect reports, or conduct trend analysis on the long-term operating status of drones at any time.
[0094] The cloud management platform 203 also supports issuing non-emergency remote commands, such as updating inspection routes, pushing firmware upgrade packages, and modifying configuration parameters.
[0095] External network terminal 204 refers to various terminal devices used by maintenance personnel for remote operation, including but not limited to personal computers, tablets, or smartphones.
[0096] External terminal 204 establishes a secure connection with external MQTT agent server 201 via the public network by installing dedicated client software or using a web browser.
[0097] After identity authentication, maintenance personnel can view the drone's real-time status summary through external network terminal 204 and issue remote control commands within the authorized scope. It should be noted that, for security reasons, emergency control commands involving flight safety are, in principle, only allowed to be issued through the internal network management platform 103, and the issuing permissions of external network terminal 204 are strictly limited.
[0098] III. Detailed Composition of Security Boundary Isolation Units
[0099] The security boundary isolation unit 3 is deployed at the network boundary between the internal network domain 1 and the external network domain 2, and is the core physical device for realizing the security isolation between the internal and external networks.
[0100] In this embodiment, the security boundary isolation unit 3 adopts a combined deployment architecture of hardware gateway and hardware firewall.
[0101] Hardware firewalls serve as the first line of defense, filtering and performing state checks on network traffic entering and leaving the intranet according to preset access control rules, blocking unauthorized IP addresses, ports, and protocol communications.
[0102] As a second line of defense, the hardware gateway is deployed behind the firewall and adopts a "2+1" architecture, which includes an internal network processing unit, an external network processing unit, and a dedicated isolation switching unit.
[0103] There is no direct physical network connection between the internal network processing unit and the external network processing unit, nor do they share any TCP / IP protocol stack.
[0104] The data transfer process is completed by copying data blocks from the storage medium using a proprietary protocol through a dedicated isolated switching unit; this architecture fundamentally eliminates the possibility of network protocol-based attacks penetrating the system.
[0105] Security boundary isolation unit 3 prohibits the establishment of any direct end-to-end communication connection between the internal network and the external network; all UAV data and commands that need to cross the boundary must be converted and extracted through the MQTT cross-network scheduling gateway 4 and then passed through the hardware gateway in the form of dedicated transfer data blocks.
[0106] This mechanism ensures that even if the external network is attacked, attackers cannot directly access internal network resources or control drones, which is in line with the power industry's general principle of secondary security: "security zoning, dedicated network, horizontal isolation, and vertical authentication".
[0107] IV. Detailed Composition of MQTT Cross-Network Scheduling Gateway
[0108] The MQTT cross-network scheduling gateway 4 is the core control and scheduling hub of this invention. Logically, it is deployed on both sides of the security boundary isolation unit 3, and respectively connects to the internal network multi-level cache module 102 and the external network multi-level cache module 202.
[0109] In actual physical deployment, independent gateway servers can be set up on the intranet side and the extranet side respectively, and the two exchange data through the private interface of the hardware gateway. The MQTT cross-network scheduling gateway 4 has four core functional modules built in: hierarchical rule engine 401, queuing scheduling unit 402, cache collaborative management unit 403, and security verification unit 404.
[0110] The hierarchical rule engine 401 is the system's decision-making brain, pre-configured with a complete three-level real-time classification standard. This standard clearly defines data commands at three levels: second-level real-time, minute-level real-time, and non-real-time, and specifies the corresponding transmission latency requirements, MQTT topic prefix set, transmission priority value, and cache storage target partition for each level.
[0111] Specifically, second-level real-time data commands include UAV flight control emergency commands, real-time attitude data, 3D position information, obstacle avoidance sensor signals, and emergency alarm information. The transmission latency requirement is less than or equal to 1 second. The corresponding MQTT topic prefixes are uav / sec / ctrl and uav / sec / data. They have the highest transmission priority and are stored in a first-level memory cache.
[0112] Minute-level real-time data commands include routine telemetry data from drones, power and voltage parameters, equipment temperature and humidity, and non-emergency alarm information. The transmission latency requirement is between 1 and 60 seconds. The corresponding MQTT topic prefixes are uav / min / tele and uav / min / alarm. The transmission priority is medium, and the storage target is a minute-level partition of the secondary disk cache.
[0113] Non-real-time data commands include UAV flight logs, historical trajectory data, high-definition aerial images, equipment maintenance records, and configuration files. The transmission latency requirement is greater than 60 seconds. The corresponding MQTT topic prefixes are uav / non / data and uav / non / file. The transmission priority is the lowest, and the storage target is a non-real-time partition of the secondary disk cache.
[0114] When the hierarchical rule engine 401 is working, it can automatically determine the real-time level of each MQTT message by parsing the topic prefix and attach the level tag to the message metadata for use by subsequent storage and scheduling units.
[0115] The queuing and scheduling unit 402 is responsible for executing specific cross-network transmission queuing and scheduling strategies.
[0116] This unit maintains three independent priority transmission queues: a second-level real-time queue, a minute-level real-time queue, and a non-real-time queue. The priorities of the three queues decrease sequentially.
[0117] The scheduling algorithm of the queuing scheduling unit 402 follows a strict priority preemption principle: as long as the second-level real-time queue is not empty, the scheduler will prioritize scheduling the data instructions in the queue and allocate dedicated transmission channel resources to them. After the message enters the queue, it skips the regular waiting and directly enters the cross-network transfer process to ensure that the end-to-end transmission delay does not exceed 1 second. When the second-level real-time queue is empty, the scheduler will switch to processing the data in the minute-level real-time queue.
[0118] Minute-level data uses a batch aggregation transmission strategy. The scheduler periodically extracts a batch of messages from the queue at preset time intervals for unified cross-network transfer. The time interval is usually configurable between 10 and 30 seconds to achieve a balance between transmission efficiency and network overhead.
[0119] When both the second-level and minute-level queues are empty, the scheduler processes data in the non-real-time queues. The transmission of non-real-time data adopts a "best-effort" mode, which is carried out during network idle periods. For large files, a fragmentation transmission mechanism is used, transferring one data block at a time to avoid occupying the cross-network link for a long time.
[0120] The cache coordination management unit 403 is responsible for unified storage management, status synchronization and resource reclamation of multi-level cache modules on both the internal and external networks.
[0121] During the data storage phase, the cache collaborative management unit 403 distributes data instructions to the corresponding cache partitions based on the level labels determined by the hierarchical rule engine 401.
[0122] For data processed in seconds, write it directly to the first-level memory cache and set a short cache expiration period.
[0123] For minute-level and non-real-time data, write to the corresponding partition in the secondary disk cache and record the timestamp for subsequent sorting.
[0124] In terms of state synchronization, whenever a data unit successfully completes cross-network transmission, the cache collaborative management unit 403 will synchronously update the status of the corresponding cache entry on both the internal and external networks to "transmitted" and trigger an automatic cleanup process to release cache space in a timely manner.
[0125] For non-real-time data that fails to be transmitted due to network interruption or other reasons, the cache coordination management unit 403 retains the cached fragment data and transmission progress markers in the secondary disk cache.
[0126] Once the network is restored, unit 403 continues to read and transmit the fragmented data from the breakpoint position according to the progress marker, without having to re-cache the entire file from the beginning, thus greatly improving transmission efficiency and network bandwidth utilization.
[0127] In addition, the cache coordination management unit 403 is also responsible for periodically scanning the cache space and automatically cleaning up expired data that has exceeded the preset lifespan to prevent the cache space from growing indefinitely.
[0128] The security verification unit 404 embeds security detection points in the cross-network transmission process to perform hierarchical security verification on the data commands to be transferred. The granularity of the security verification is dynamically adjusted according to the real-time level of the data commands.
[0129] For real-time data commands at the second level, which are extremely sensitive to transmission latency, the security verification unit 404 focuses on performing lightweight and efficient verification items, mainly including HMAC-based digital signature verification and replay attack prevention checks based on timestamps or random numbers; the verification process is completed quickly in memory, and the additional latency introduced is controlled at the millisecond level.
[0130] For minute-level real-time and non-real-time data commands, due to the high tolerance for transmission delay, the security verification unit 404 can perform more in-depth content auditing, such as checking whether the data payload contains sensitive keywords, whether the file format conforms to the preset specifications, and whether the data length is within the allowed range.
[0131] Once the verification detects abnormal or illegal content, the security verification unit 404 immediately intercepts the data unit, prevents it from entering the cross-network transfer process, deletes the original data in the corresponding cache, and sends an alarm notification to the intranet management platform 103.
[0132] Example 2: Detailed Implementation Process of Cross-Network Transmission Method
[0133] This embodiment, based on the system described in Embodiment 1, elaborates in detail the specific execution steps of a multi-level cache hierarchical transmission method for UAVs across security boundaries based on MQTT. This method is applicable to typical application scenarios where power inspection UAVs, during the execution of their missions, transmit the collected inspection data back to the intranet management platform in real time and transmit the route update instructions issued by the cloud to the UAVs.
[0134] Step 1: Device Connection and Buffer Initialization
[0135] When the system starts up or the drone goes online, the device access and cache initialization process is executed first.
[0136] The drone-borne MQTT client accesses the intranet coverage area via the onboard 4G / 5G communication module or private WiFi and initiates a connection request to the intranet authentication unit 104.
[0137] The request message carries a pre-installed X.509 device certificate; the intranet authorization authentication unit 104 verifies the validity of the certificate and the issuance chain, and checks whether the device fingerprint is in the authorized whitelist.
[0138] After successful authentication, the internal MQTT broker server 101 establishes a TLS-encrypted MQTT long connection with the onboard client.
[0139] Meanwhile, the cloud management platform 203 deployed on the external network and the external network terminal 204 used by the operation and maintenance personnel also need to complete the authentication access with the external network MQTT agent server 201 through username and password or certificate.
[0140] At the same time as the device is connected, the MQTT cross-network scheduling gateway 4 triggers the initialization process of the multi-level caching module of the internal and external networks.
[0141] According to the preset configuration file, the cache coordination management unit 403 allocates a dedicated storage area for second-level real-time data in the first-level memory cache and sets the maximum memory capacity to 512MB.
[0142] In the secondary disk cache, storage directories and index files for minute-level partitions and non-real-time partitions are created respectively, and a total disk quota of 8GB is allocated, of which 2GB is allocated to minute-level partitions and 6GB is allocated to non-real-time partitions.
[0143] The data expiration and cleanup time thresholds for each partition are also loaded at this stage. For example, the lifespan of second-level cached data is set to 5 seconds, the lifespan of minute-level data is set to 30 minutes, and there is no time limit for non-real-time data.
[0144] Step Two: Data Command Issuance and Hierarchical Determination
[0145] When drones perform power pole inspection missions, their onboard flight control system and various sensors continuously generate data.
[0146] The onboard MQTT client publishes the data to the corresponding MQTT topic based on the data's real-time attributes.
[0147] For example, when the drone detects an obstacle ahead and triggers an autonomous obstacle avoidance maneuver, the flight control system immediately generates an emergency obstacle avoidance status command and publishes it to the topic uav / sec / data / obstacle.
[0148] Meanwhile, the drone's real-time attitude angle and three-dimensional coordinate position information are continuously published to the uav / sec / data / pose topic at a frequency of 50Hz.
[0149] Common telemetry parameters such as the battery's current voltage, remaining charge percentage, and motor temperature are published at a frequency of 1Hz to the uav / min / tele / battery and uav / min / tele / temperature topics.
[0150] The high-definition photos and infrared thermal images of the pole insulators taken by the airborne high-definition gimbal are published in file format in segments to the uav / non / file / inspection topic.
[0151] When the intranet MQTT agent server 101 receives these messages, it forwards them to the intranet-side interface of the MQTT cross-network scheduling gateway 4.
[0152] The gateway's internal hierarchical rule engine 401 captures each message, extracts its topic string, and matches it against a pre-configured topic prefix rule set.
[0153] Messages with a subject starting with uav / sec / are identified as second-level real-time data commands; those starting with uav / min / are identified as minute-level real-time data commands; and those starting with uav / non / are identified as non-real-time data commands.
[0154] After the hierarchical rule engine 401 attaches a level label field to each message, it submits it to the cache coordination management unit 403.
[0155] Step 3: Multi-level caching and tiered storage
[0156] After receiving a message carrying a level tag, the cache coordination management unit 403 performs a hierarchical storage operation. For emergency obstacle avoidance status commands and real-time pose data marked as second-level real-time, unit 403 calls the write interface of the first-level memory cache to directly write the message body and metadata to the memory storage area. The write operation adopts a non-blocking asynchronous mode to ensure that it does not block the processing of subsequent messages.
[0157] Meanwhile, unit 403 sets a 5-second time-to-live timer for the memory cache entry; if the data fails to complete cross-network transmission within 5 seconds, the timer will expire and trigger a retransmission reminder mechanism.
[0158] For the battery voltage and motor temperature telemetry data marked as minute-level real-time, unit 403 serializes them and appends them to the log file corresponding to the minute-level partition in the secondary disk cache.
[0159] Data is stored in the order of the timestamps carried in the messages, which facilitates subsequent batch reading. For high-definition photo files of towers that are marked as non-real-time, unit 403 identifies them as large file fragments and stores their fragment number, total number of fragments, and fragment data payload together in the non-real-time partition.
[0160] The data of each file's fragments is aggregated and stored using the filename as an index, and a separate metadata file is maintained to record the reception status of each fragment.
[0161] Step 4: Hierarchical queuing and transfer
[0162] The queuing and scheduling unit 402 continuously monitors the status of the three priority transmission queues and schedules data to complete cross-network transfer via the security boundary isolation unit 3 according to the queue status.
[0163] First, the queuing and scheduling unit 402 checks the second-level real-time queue; the queue currently contains emergency obstacle avoidance state instructions and continuous multi-frame pose data; since the second-level queue is not empty, the queuing and scheduling unit 402 immediately preempts the cross-network transmission channel resources.
[0164] Second-level data messages are read from the first-level memory cache and delivered to the security verification unit 404 in a first-in-first-out order for fast signing and anti-replay verification.
[0165] After successful verification, the message is encapsulated into a data block of the gateway's private protocol and copied from the internal network side to the external network side through the isolation switching unit of the hardware gateway.
[0166] After receiving the data block, the external network component of the MQTT cross-network scheduling gateway 4 restores it to an MQTT message and publishes it to the external network MQTT agent server 201.
[0167] The entire process, from the message entering the second-level queue to the completion of restoration on the external network, has an end-to-end latency measurement of 0.6 to 0.8 seconds, meeting the latency requirement of less than 1 second.
[0168] After the transmission is completed, the cache coordination management unit 403 immediately deletes the corresponding transmitted entry from the intranet level-one memory cache.
[0169] Once the second-level real-time queue is emptied, the queuing and scheduling unit 402 switches the scheduling target to the minute-level real-time queue. The scheduling unit 402 reads the accumulated telemetry data records from the minute-level partition of the secondary disk cache every 20 seconds, packages them into a batch message group, performs signature verification, and then forwards them to the external network through the network gateway. Upon receiving the message, the external network splits the batch message group into individual messages and publishes them sequentially to the external MQTT broker server 201.
[0170] After successful transmission, the cache collaborative management unit 403 marks the corresponding record as synchronized in the minute-level partition of the intranet secondary disk cache, but does not perform physical deletion for the time being, so as to provide short-term data backtracking query when necessary.
[0171] Records marked as synchronized will be physically deleted in subsequent periodic cleanup tasks.
[0172] When both the second-level and minute-level queues are empty, such as when a drone has returned and landed at night, the queuing scheduling unit 402 initiates the idle transmission task of the non-real-time queue.
[0173] Unit 402 scans the non-real-time partitions of the secondary disk cache, searching for file fragments with a status of "pending transfer". Taking a high-definition photo file as an example, suppose a 5MB photo file is divided into 10 fragments.
[0174] The scheduling unit 402 reads one fragment from the disk each time and transfers it to the external network through the network gateway.
[0175] After receiving the fragments, the external network component writes them to the corresponding file in the non-real-time partition of the external network secondary disk cache. The cache coordination management unit 403 synchronously updates the fragment reception status bitmap on both sides.
[0176] Once all 10 fragments have been transmitted, the cache collaborative management unit 403 on the external network side reassembles all fragments into a complete original file and notifies the cloud management platform 203 to perform archiving.
[0177] Finally, the cache coordination management unit 403 cleans up all cache fragments and metadata related to this file on both the internal and external networks.
[0178] During step four, if transmission is interrupted due to a network outage or a restart of the gateway device, the system has robust exception handling capabilities.
[0179] For data at the second level, since the caching time is extremely short and the transmission is not yet complete, the system directly discards the old data and triggers a retransmission reminder. The drone's onboard terminal then decides whether to re-report the latest status based on the business logic.
[0180] For minute-level and non-real-time data, the cache coordination management unit 403 preserves the stored data and fragment status markers intact in the secondary disk cache.
[0181] Once the network is restored, the queuing and scheduling unit 402 resumes the transmission from the unfinished portion before the interruption, without needing to re-collect or retransmit all the data from the drone. For example, if the transmission of a high-definition photo is interrupted when it reaches the 7th image, it will resume transmission from the 8th image after the network is restored.
[0182] Step 5: Cache Coordination and Exception Handling
[0183] Throughout the entire transmission lifecycle, the cache coordination management unit 403 continues to work, performing cache state synchronization and maintenance tasks.
[0184] This unit periodically exchanges status information between the internal and external network cache management units through heartbeat messages or status synchronization protocols to ensure that both parties have a consistent understanding of the transmission status of each piece of cached data.
[0185] Once a piece of data is confirmed to have completed cross-network transmission and been successfully delivered to the target MQTT broker server, the cache coordination management unit 403 will trigger a cleanup action on both sides simultaneously to release the occupied cache space.
[0186] To clean up expired data, the cache co-management unit 403 runs a background cleanup thread that scans cache partitions at all levels once per minute.
[0187] For the first-level memory cache, check the lifetime of each entry, delete second-level data entries that have not been transmitted for more than 5 seconds, and accumulate the deletion count for monitoring and alarm purposes.
[0188] For the secondary disk cache, examine the minute-level partitions and non-real-time partitions separately.
[0189] In minute-level partitions, synchronized data stored for more than 30 minutes will be physically deleted.
[0190] In non-real-time partitions, file fragments that have been stored for more than 72 hours and have not been fully transferred will be judged as transfer failures. The system will generate an alarm log and clean up the corresponding fragments to free up disk space.
[0191] When the security verification unit 404 detects illegal or abnormal data, it immediately performs an interception operation.
[0192] For example, when a terminal on the external network attempts to send a forged flight control command message to the internal network, the security verification unit 404 finds the signature invalid during signature verification, immediately discards the message, prevents it from entering the transfer queue, and sends an alarm message to the internal network management platform 103 containing the source IP, subject, and reason for verification failure.
[0193] For non-real-time files found to contain sensitive words during content auditing, verification unit 404 will also block transmission and issue an alarm.
[0194] Step Six: Data Command Reception and Parsing
[0195] The drone data commands, once transmitted across networks, eventually arrive at either the external MQTT proxy server 201 or the internal MQTT proxy server 101.
[0196] The MQTT broker server looks up the list of currently online subscribers based on the message topic and pushes the message to the corresponding client.
[0197] In the power inspection scenario, the cloud management platform 203 on the external network side pre-subscribed to the topics uav / min / tele / # and uav / non / file / #.
[0198] Once the telemetry data and inspection photo files have been transmitted, the external MQTT agent server 201 will push the data to the cloud management platform 203.
[0199] The parsing module of the cloud management platform 203 extracts voltage and temperature values from telemetry data and updates them to the real-time monitoring dashboard. For received photo files, the parsing module stores them in the object storage service and archives them in association with the inspection task work order and tower number.
[0200] The intranet management platform 103 on the intranet side pre-subscribed to the topic uav / sec / data / #.
[0201] Once the emergency obstacle avoidance command is transmitted across networks back to the intranet and published, the intranet management platform 103 receives the message in real time.
[0202] The analysis module identifies the type and location of the obstacle avoidance event, immediately pops up a prominent alarm prompt box on the monitoring interface, accompanied by an audible alarm, to remind the on-duty personnel on the intranet to pay attention to the safety of drone operations.
[0203] Through the close collaboration of the above six steps, this invention achieves efficient, reliable, and hierarchical transmission of UAV data commands between the intranet and the security boundary of the extranet.
[0204] Throughout the process, the transmission latency of second-level emergency commands remained stable within 1 second, minute-level telemetry data arrived in order without packet loss, non-real-time large files supported breakpoint resumption, and internal and external network caches worked together efficiently and orderly.
[0205] This system and method fully meet the stringent requirements for real-time performance, reliability, and safety of power line inspection drones operating across safety boundaries.
[0206] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0207] The above description is merely a preferred embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural transformations made using the contents of the present invention's specification and drawings under the inventive concept of the present invention, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.
Claims
1. A multi-level cached hierarchical transmission system for unmanned aerial vehicles (UAVs) across security boundaries based on MQTT, characterized in that, include: The intranet domain is equipped with an intranet MQTT proxy server, an intranet multi-level caching module, an intranet management and control platform, and an intranet access authentication unit. The external network domain is equipped with an external MQTT proxy server, an external multi-level caching module, a cloud management platform, and external terminals. The external network domain is physically isolated from the internal network domain. A security boundary isolation unit is deployed between the internal network domain and the external network domain and is configured to block direct communication between the internal network domain and the external network domain. The MQTT cross-network scheduling gateway connects to both the intranet multi-level caching module and the extranet multi-level caching module, and has a built-in hierarchical rule engine, queuing scheduling unit, and cache collaborative management unit. The hierarchical rule engine is configured to divide the transmitted data instructions into at least high real-time level, medium real-time level and non-real-time level according to real-time requirements; The queuing scheduling unit is configured to establish a priority transmission queue based on the partitioning results of the hierarchical rule engine; The cache collaborative management unit is configured to control the hierarchical storage and status synchronization of data between the intranet multi-level cache module and the extranet multi-level cache module.
2. The MQTT-based UAV cross-security boundary multi-level cache hierarchical transmission system according to claim 1, characterized in that, Both the intranet multi-level cache module and the extranet multi-level cache module adopt a two-level cache architecture, including a first-level memory cache dedicated to storing high real-time data instructions and providing high-speed read and write, and a second-level disk cache that stores real-time and non-real-time data instructions in different regions and provides persistent storage.
3. The MQTT-based UAV cross-security boundary multi-level cache hierarchical transmission system according to claim 2, characterized in that, The hierarchical rule engine is specifically configured to divide data instructions into second-level real-time categories, minute-level real-time categories, and non-real-time categories. Among them, the transmission latency requirement for second-level real-time classes is less than or equal to 1 second, corresponding to the first transmission priority; For minute-level real-time transmission, the transmission latency requirement is greater than 1 second and less than or equal to 60 seconds, corresponding to the second transmission priority. For non-real-time transmissions, the latency requirement is greater than 60 seconds, corresponding to the third transmission priority. The first transmission priority is higher than the second transmission priority, and the second transmission priority is higher than the third transmission priority.
4. The MQTT-based UAV cross-security boundary multi-level cache hierarchical transmission system according to claim 3, characterized in that, The hierarchical rule engine is further configured to identify the real-time level of data instructions based on the topic prefix of MQTT messages; Among them, second-level real-time data instructions correspond to the first exclusive topic prefix set, minute-level real-time data instructions correspond to the second exclusive topic prefix set, and non-real-time data instructions correspond to the third exclusive topic prefix set.
5. A UAV cross-security boundary multi-level cache hierarchical transmission system based on MQTT according to claim 3, characterized in that, The queuing scheduling unit is configured as follows: When there is a high real-time level data instruction in the priority transmission queue, a dedicated transmission channel is preempted for the high real-time level data instruction and its transmission is scheduled with priority. When there are no high real-time level data commands, the real-time level data commands in the transmission are scheduled in batches at preset time intervals. When there are no data commands of high real-time or medium real-time level, non-real-time level data commands are scheduled for transmission during network idle periods.
6. A multi-level cached hierarchical transmission system for UAVs based on MQTT across security boundaries, as described in claim 2, is characterized in that... The cache collaborative management unit is further configured as follows: High real-time level data instructions are directly written to the first-level memory cache, and the corresponding cache entries are cleared immediately after cross-network transmission is completed. It writes real-time and non-real-time data commands to the secondary disk cache and supports fragmented storage and breakpoint resume status marking for non-real-time data commands.
7. A UAV cross-security boundary multi-level cache hierarchical transmission system based on MQTT according to claim 1, characterized in that, The security boundary isolation unit is a combined isolation device consisting of a hardware gateway and a firewall.
8. The MQTT-based UAV cross-security boundary multi-level cache hierarchical transmission system according to claim 1, characterized in that, The MQTT cross-network scheduling gateway also has a built-in security verification unit. The security verification unit is configured to perform hierarchical security verification on data commands transmitted across networks. For data commands with high real-time level, the focus is on performing digital signature and anti-replay verification. For data commands with medium real-time level and non-real-time level, the focus is on performing content auditing and format verification.
9. A method for hierarchical transmission of UAVs across security boundaries using MQTT-based multi-level buffers, applied to the hierarchical transmission system for UAVs across security boundaries using MQTT-based multi-level buffers as described in any one of claims 1 to 8, characterized in that, Includes the following steps: S1. Initialization steps: The intranet multi-level cache module and the extranet multi-level cache module complete the cache partitioning according to the pre-configured real-time level; S2. Grading determination step: The MQTT cross-network scheduling gateway receives the data instruction to be transmitted, and the grading rule engine identifies and determines the real-time level of the data instruction; S3. Layered storage step: Based on the result of the layered determination step, the cache collaborative management unit distributes and stores the data instructions to the intranet cache partition corresponding to the real-time level. S4. Hierarchical queuing transmission step: According to the result of the hierarchical determination step, the queuing scheduling unit adds the data instruction to the corresponding priority transmission queue, and controls the data instruction to complete the cross-network transfer transmission through the security boundary isolation unit in order of priority from high to low. S5. Cache status synchronization step: After the data instruction completes cross-network transmission, the cache collaborative management unit synchronously cleans up the transmitted data in the corresponding cache partitions of the internal and external networks.
10. A method for hierarchical transmission of UAVs across security boundaries using MQTT-based multi-level buffering, as described in claim 9, characterized in that... The hierarchical queuing and transfer step further includes: High real-time level data commands are added to the first priority queue to preempt the transmission channel for immediate transmission, with a transmission delay of less than or equal to 1 second. Add real-time data commands to the second priority queue and transmit them in batches at the first preset time interval; Non-real-time data commands are added to the third priority queue and transmitted during network idle periods. Large data volumes are transmitted in chunks. When a transmission interruption is detected, data instructions at both the real-time and non-real-time levels retain cached fragments in the secondary disk cache and resume transmission from the point of interruption after the network is restored.
