Distributed Ledger Auto-Recovery for Heterogeneous Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computer networks with centralized communication models, such as the server/client model, are prone to failures and security vulnerabilities, and face challenges in updating heterogeneous devices, including 'orphaned' devices that lack support from original developers, leading to potential disruptions and interoperability issues.
Innovation Solution
Implementing a distributed ledger system that allows multiple devices in a computer network to validate and record updates decentralizedly, eliminating the need for a central server and enhancing security and interoperability across diverse devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a centralized server/client model is used for device updates, then update management is simplified, but security vulnerabilities and single points of failure increase
Solution Approach 1:
The patent segments the centralized update authority into multiple distributed update entities across the network. Each entity maintains a copy of the distributed ledger and can independently validate updates, eliminating the single point of failure while maintaining coordinated update management through the consensus mechanism.
Solution Approach 2:
The distributed ledger acts as an intermediary between update entities and devices. It provides a shared, immutable record of valid updates that all entities can reference, enabling coordinated update distribution without requiring direct communication between entities or a central server.
2Ease of operation
If a centralized server is used for update distribution, then update coordination is easier, but bottlenecks and failure points are created
Solution Approach 1:
The patent divides the centralized update coordination function into multiple distributed nodes that each maintain the distributed ledger. Update coordination is achieved through consensus mechanisms where multiple entities validate and record updates, eliminating bottlenecks while maintaining coordination through the shared ledger.
Solution Approach 2:
The patent combines the update validation and coordination functions across multiple distributed entities rather than concentrating them in a single server. Each entity contributes to the consensus process, merging their computational resources and validation capabilities to achieve more reliable coordinated updates.
3Reliability
If multiple update entities are introduced to eliminate central servers, then security and reliability improve, but update conflict resolution becomes more complex
Solution Approach 1:
The distributed ledger provides continuous feedback to all update entities about the current state of valid updates and device configurations. This feedback mechanism allows entities to detect conflicts, determine which updates have been applied, and coordinate their actions based on the shared ledger state, simplifying conflict resolution despite multiple entities.
Solution Approach 2:
The patent implements preliminary validation of updates against the distributed ledger before deployment. Entities check the ledger to ensure updates are consistent with the current network state, preventing conflicts before they occur and reducing the complexity of conflict resolution.
4Reliability
If distributed ledger is implemented across multiple devices, then central server dependency is eliminated, but system complexity increases
Solution Approach 1:
Each device in the network runs its own copy of the distributed ledger and can independently validate updates without requiring services from a central server. The system is self-organizing, with each node contributing to the overall security and validity verification, reducing dependency while managing complexity through decentralized autonomy.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Updating computer program(s) installed on a programmable device using a distributed ledger that is based on cryptography and blockchain technology is described. A distributed ledger logic/module can commit, to the distributed ledger, a first configuration of a computer program installed on a device. The logic/module can also receive requests to apply a first update and a second update to the first configuration. The logic/module can receive a second configuration of the computer program that is based on the first update and the first configuration, and also commit the second configuration to the distributed ledger. Furthermore, the logic/module can determine that the second update cannot be applied to the first configuration and receive a third configuration of the computer program that is based on the second update and the second configuration. The logic/module can also commit the third configuration to the distributed ledger. Other advantages and embodiments are described.