Recursive Ledger Chaining for Edge Device Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional load balancing schemes in IoT edge devices do not account for dynamic changes in resource availability, leading to unbalanced and unpredictable workload architectures, especially in mobile environments where edge devices are frequently moved or relocated.
Innovation Solution
The implementation of recursive ledger chaining in a decentralized resource ledger structure that dynamically updates information about edge device resources, allowing nodes to traverse paths and update ledgers to reflect changes in resource availability and paths, ensuring accurate tracking and management of resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional load balancing schemes are used in IoT edge devices, then device simplicity and ease of operation are maintained, but resource availability becomes unbalanced and unpredictable due to dynamic changes in mobile environments
Solution Approach 1:
The decentralized resource ledger structure is segmented into multiple constituent ledgers distributed across different nodes in the network. Each node maintains its own ledger entries locally, dividing the overall resource tracking system into manageable segments that can operate independently yet remain synchronized through the chaining mechanism.
Solution Approach 2:
The patent implements nested ledgers where constituent ledgers are embedded within a hierarchical structure. Each node's ledger contains entries that reference and chain to ledgers at other nodes, creating a nested arrangement where local resource information is embedded within the broader network context, allowing efficient local access while maintaining global consistency.
2Loss of information
If decentralized resource ledger structure with recursive chaining is implemented, then up-to-date resource information is maintained, but information processing time and computational overhead increase
Solution Approach 1:
Nodes perform preliminary actions by maintaining local copies of constituent ledgers and proactively updating their entries when resource availability changes. This preliminary local updating eliminates the need for real-time synchronization queries, as each node already possesses current information about resources within its local network segment.
Solution Approach 2:
The recursive ledger chaining mechanism implements feedback loops where nodes verify and update their ledger entries based on information from chained ledgers at other nodes. When a node detects changes in resource availability, it propagates updates through the chain, and receiving nodes feedback their status, ensuring all participants maintain accurate information without continuous polling.
3Adaptability or versatility
If edge devices are moved or relocated in mobile environments, then system adaptability and flexibility improve, but workload architecture becomes unbalanced and unpredictable
Solution Approach 1:
The ledger structure is designed to be dynamic, automatically adapting to device relocation. When edge devices move between network segments, their resource entries are dynamically re-chained to new parent ledgers, and the decentralized structure automatically recalculates resource availability paths, maintaining workload balance without requiring centralized reconfiguration.
Solution Approach 2:
The system changes key parameters such as ledger parent-child relationships and resource path routing when devices are relocated. By modifying these structural parameters dynamically, the system maintains stable workload architecture despite physical device movement, as the logical resource topology adapts to reflect current network conditions.
Data Source
AI summary
Edge device resourcing in a networked environment may employ a decentralized resource ledger structure to track information about edge device resources and their locations relative to other devices. Each entry of the decentralized resource ledger may include, for a respective edge device resource, a unique identifier, a time stamp indicating when it was created, resource type information, relative location information, or path information. Each of multiple nodes in the environment may include a constituent portion of the decentralized resource ledger structure. During periodic discovery operations or in response to a configuration change, one or more paths from a static non-edge device toward edge devices may be traversed, and any fresh resource information may be returned (recursively) back along the path to the static non-edge device. These operations may discover new paths between nodes (e.g., for self-healing). The decentralized resource ledger may be analyzed to predict resource availability.


