Backup Node Takeover for Edge Device Management Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In current device-edge-cloud synergy architectures, when the network between the central device and the edge device is weak and disconnected, the edge device loses high-level autonomy, unable to deploy new services or maintain service continuity.
Innovation Solution
A data backup device is configured to back up the management device, and upon disconnection, it is upgraded to manage the edge device, ensuring high-level autonomy by electing a backup designated node to continue managing edge devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the network between the central device and the edge device is disconnected, then the edge device loses high-level autonomy and cannot deploy new services, but implementing a backup device mechanism increases system complexity
Solution Approach 1:
The patent implements preliminary action by pre-configuring a backup device (second device) that maintains data backups and management information before any disconnection occurs. When the network disconnects, this pre-prepared backup device can immediately take over management functions without requiring complex real-time decision-making or reconfiguration, thus maintaining autonomy while keeping the system relatively simple.
Solution Approach 2:
The patent applies the copying principle by creating a backup device that replicates the essential management capabilities and data of the central device. The second device stores copies of management information and can function as a substitute when the central device is inaccessible, providing autonomy without requiring the entire central device infrastructure at the edge.
2Duration of action of stationary object
If the backup device is upgraded to manage edge devices upon disconnection, then service continuity is maintained, but the upgrade process and node election increase system complexity
Solution Approach 1:
The system performs preliminary actions by pre-establishing the backup device with all necessary management data and capabilities before disconnection occurs. The second device is already configured with backup information, so when upgrading is needed, it can immediately assume the management role without complex real-time setup procedures, ensuring service continuity with minimal complexity.
Solution Approach 2:
The patent implements periodic action through the node election mechanism where devices periodically check the status of the central device and the backup device. When disconnection is detected, the periodic status checks trigger the upgrade process automatically, maintaining service continuity through rhythmically occurring status verification and seamless transition.
3Reliability
If the second device sends packets to indicate it manages third devices, then autonomy is maintained during disconnection, but communication overhead increases
Solution Approach 1:
The patent applies the extraction principle by isolating the communication function to only what is absolutely necessary for maintaining autonomy. The second device sends out indication packets only when needed to assert its management role during disconnection, rather than maintaining continuous communication. This extracts the essential management assertion from unnecessary continuous communication, reducing energy overhead while preserving autonomy.
Data Source
AI summary
A device management system includes a first device, a second device, and at least one third device. The first device is configured to manage the second device and the at least one third device. The second device includes data backup of the first device. The method is performed by the second device includes: determining that the first device is in an abnormal state; and sending a first packet to the at least one third device, where the first packet indicates that the second device manages the at least one third device.