Edge Node Autonomy via Federation Controller and MQTT Queuing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In edge computing, edge nodes often disconnect from central nodes in weak network environments, disrupting the normal operation of local containers and lacking autonomy, which existing technologies do not adequately address through federation autonomy.
Innovation Solution
A computer-implemented method and apparatus for edge node autonomy that determines the availability of a controller within a federation to process requests, utilizes an MQTT module for request queuing during disconnection, and synchronizes data to ensure continuous operation and reconnection to the central node, enabling edge node autonomy even in disconnected states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If edge nodes are connected to central node through network connection, then edge nodes can access data and manage local containers, but edge nodes cannot operate autonomously when disconnected in weak network environments
Solution Approach 1:
The patent applies preliminary action by pre-synchronizing data between edge nodes and central node before disconnection occurs. The system performs data synchronization in advance during connected states, storing necessary data locally at edge nodes. When disconnected, these pre-synchronized data enable edge nodes to continue operating autonomously without immediate central node access, thus resolving the contradiction between reliability during disconnection and autonomy capability.
Solution Approach 2:
The patent introduces an intermediary mechanism through the federation of edge nodes. When one edge node disconnects from the central node, other connected edge nodes in the federation act as intermediaries to provide data and services. This intermediary approach allows disconnected edge nodes to maintain operations through peer edge nodes, enhancing both reliability during disconnection and autonomy capability without requiring direct central node connection.
2Adaptability or versatility
If edge nodes operate independently during disconnection, then autonomy is improved, but request processing capability is lost without central node connection
Solution Approach 1:
The patent applies merging by combining the capabilities of multiple edge nodes into a federation. When edge nodes form a federation, they pool their resources, data, and processing capabilities. During disconnection, this merged capability allows the federation to process requests autonomously that would otherwise require central node access, thus maintaining productivity while operating independently. The federation acts as a unified autonomous unit, preserving request processing capability without central node connection.
3Loss of information
If edge nodes synchronize data frequently with central node, then data consistency is improved, but network dependency increases and autonomy decreases
Solution Approach 1:
The patent applies partial action by implementing selective data synchronization rather than frequent comprehensive synchronization. The system identifies and synchronizes only critical data changes between edge nodes and central node, rather than synchronizing all data frequently. This partial synchronization approach maintains data consistency for essential operations while reducing network dependency, thereby preserving edge node autonomy. The selective synchronization occurs only when necessary, balancing data consistency requirements with autonomy preservation.
Data Source
AI summary
A computer-implemented method, an apparatus, and a computer program product for edge node autonomy. For a first edge node of a plurality of edge nodes in a federation in a distributed computing framework, one or more processors receive a request to be sent to a central node in the distributed computing framework. The one or more processors determine whether the federation is connected to the central node. In response to determining that the federation is not connected to the central node, the one or more processors determine whether a controller capable of processing the request is available in the federation. In response to determining that the controller capable of processing the request is available in the federation, the one or more processors notify the controller to process the request.