Local Gateway Update Distribution for IoT Cloud Load Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional update methods for end nodes in the Internet of Things lead to excessive burden on cloud resources, causing network congestion and potential update failures due to the need for each node to establish and maintain a cloud channel for firmware and configuration updates.
Innovation Solution
Implementing a local network architecture where only one active update node acquires update information from a server, and passive update nodes receive this information from the active node through the local network, reducing the number of nodes directly accessing the server and alleviating cloud resource strain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each end node independently establishes and maintains a cloud channel with the server for update information acquisition, then each node can obtain updates independently, but the cloud burden increases significantly causing network congestion and update failures
Solution Approach 1:
The patent introduces a gateway device as an intermediary between end nodes and the server. The gateway collects update information from the server and distributes it to multiple end nodes locally, eliminating the need for each node to maintain independent cloud channels. This mediator approach reduces cloud burden while ensuring reliable update delivery to all nodes.
Solution Approach 2:
The system segments the update process into two distinct phases: (1) the gateway establishes a single cloud channel with the server to acquire update information, and (2) the gateway distributes this information locally to multiple end nodes through a local network. This segmentation separates the cloud interaction function from the local distribution function, reducing overall system complexity.
2Adaptability or versatility
If tens of billions of end nodes all acquire update information directly from the server, then each node gets the latest updates, but computing resources such as bandwidth and processors become insufficient
Solution Approach 1:
The gateway device creates local copies of update information obtained from the server and stores them in its local storage. These copies are then distributed to multiple end nodes without requiring each node to fetch the original data from the server. This copying mechanism ensures update information availability while dramatically reducing the computing power and bandwidth requirements at the server end.
Solution Approach 2:
The patent introduces a new dimensional layer (local network distribution layer) between the server and end nodes. Instead of a direct one-to-many connection, the system creates a two-stage distribution architecture where the gateway handles local network communications, freeing up server resources for core update management functions.
3Ease of operation
If each end node maintains its own cloud channel, then direct server access is ensured, but network congestion occurs due to the large number of simultaneous connections
Solution Approach 1:
The patent merges multiple individual cloud channels into a single shared cloud channel at the gateway level. Instead of each end node maintaining a separate connection to the server, all nodes share the gateway's single connection. This consolidation maintains ease of operation for update acquisition while eliminating network congestion caused by numerous simultaneous connections.
Data Source
AI summary
An updating method including: acquiring, by an active update node, update information from a server; and acquiring or receiving, by a passive update node, the update information from the active update node through a local network. By using the update method and system, end node and electronic device provided in the present disclosure, an active update node of a plurality of end nodes in the same local network acquires update information from a server, and a passive update node acquires the update information from the active update node, thereby reducing the number of end nodes acquiring the update information from the server, and reducing the burden of the cloud.