Decentralized Hardware Configuration Control via Blockchain Quorum

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for changing system configurations in hardware systems lack a robust mechanism to ensure compatibility and consensus among multiple hardware components, leading to potential functional disruptions and lack of secure logging of changes.

Innovation Solution

A method utilizing a block chain to manage system configuration changes, where each hardware component checks and approves changes before they are implemented, ensuring compatibility and consensus through a quorum-based mechanism, and securely logging these changes for forgery-proof records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a central control unit manages system configuration changes, then coordination and consensus among hardware components can be achieved, but the system complexity and single point of failure increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidcontrol structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the central control unit from the system architecture and replaces it with a decentralized consensus mechanism using blockchain technology. Each hardware component independently validates configuration changes through smart contracts, eliminating the single point of failure while maintaining coordination through distributed agreement protocols.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system divides the centralized control function into multiple independent validation nodes distributed across hardware components. Each component maintains its own copy of the configuration state and independently executes validation logic, segmenting the control authority to improve reliability while reducing dependency on a central entity.

Inventive Principle:
Principle #1Segmentation

2Productivity

If configuration changes are implemented without comprehensive compatibility checking, then implementation speed increases, but functional disruptions and system errors occur

Engineering Contradiction:
Improveconfiguration change speedVSAvoidsystem functionality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary compatibility checking through smart contracts that automatically validate configuration changes against predefined rules and component capabilities before implementation. This preliminary validation ensures functional integrity while maintaining rapid deployment through automated verification processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system incorporates real-time feedback mechanisms where each hardware component reports its compatibility status with proposed configuration changes. This feedback loop enables dynamic adjustment of change proposals to ensure system-wide compatibility while maintaining implementation efficiency through automated negotiation and validation.

Inventive Principle:
Principle #23Feedback

3Reliability

If configuration changes are manually verified and approved, then compatibility and consensus are ensured, but the time required for implementation increases

Engineering Contradiction:
Improveconfiguration compatibilityVSAvoidconfiguration change time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual verification processes with automated smart contract execution on the blockchain. Configuration changes are validated through programmed logic that automatically checks compatibility rules, eliminating the need for manual review while ensuring the same level of compatibility assurance through cryptographic verification.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service configuration management where hardware components autonomously validate and approve configuration changes according to predefined policies. Each component independently executes validation logic and reaches consensus through automated protocols, eliminating manual intervention while maintaining reliability through decentralized agreement.

Inventive Principle:
Principle #25Self-service

4Ease of manufacture

If configuration changes are logged in a centralized database, then recording and tracking are simplified, but security and tamper-proof capabilities are reduced

Engineering Contradiction:
Improvelogging implementation easeVSAvoidchange record security
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent introduces a blockchain ledger as an intermediary layer between configuration changes and their records. This decentralized ledger provides tamper-proof logging through cryptographic hashing and distributed storage, ensuring security and integrity while maintaining ease of implementation through standardized blockchain protocols and smart contract integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

5Reliability

If all hardware components must approve configuration changes, then system-wide compatibility is ensured, but the consensus process becomes slower

Engineering Contradiction:
Improvesystem compatibilityVSAvoidconsensus achievement time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a quorum-based consensus mechanism where a predefined threshold of hardware component approvals is sufficient to implement configuration changes, rather than requiring unanimous consent. This partial action approach ensures adequate system-wide compatibility while reducing consensus time by eliminating the need for all components to agree.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11513816B2System configuration control of a hardware system
Publication Date: 2022.11.29 BUNDESDRUCKEREI GMBH
  • US11513816B2 patent drawing
  • US11513816B2 patent drawing
  • US11513816B2 patent drawing

AI summary

The method includes creating and sending a change request for a change to the system configuration of the hardware system by means of a first hardware component of the plurality of hardware components, receiving the change request by means of the further hardware components of the plurality of hardware components, checking the change request by means of the further hardware components for compatibility of the change request with the configuration of the particular receiving hardware component by using configuration data of the receiving hardware component, in the case that the requested change to the system configuration is compatible with the configuration of the receiving hardware component, generating and sending an approval of the change to the system configuration by means of the receiving hardware component, and in the case that an approval quorum of the hardware components that is necessary for consent is achieved, entering the requested change to the system configuration of the hardware system into the block chain, implementing the requested change to the system configuration in the hardware system.