Blockchain Command Verification Across Multi-Operator Device Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Controlling and processing command sequences in heterogeneous networks of devices from different operators is challenging due to the complexity of synchronizing and executing commands across diverse systems.

Innovation Solution

A control system utilizing a distributed database system based on blockchain technology, which includes modules for determining execution requirements, mapping commands, storing transactions, checking device-specific requirements, and executing control commands, ensuring secure and decentralized execution of commands across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a distributed database system with blockchain technology is implemented to enable decentralized control command execution, then security and reliability are improved, but device complexity increases

Engineering Contradiction:

Improvesecurity of control command executionVSAvoidcomplexity of control system

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments control commands into individual control transactions, each with its own execution requirements. This segmentation allows the distributed database system to process and verify commands independently, improving security through granular verification while managing complexity by breaking down the overall control process into manageable units.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The distributed database system serves multiple functions: it stores control transactions, verifies execution requirements, tracks device states, and manages acknowledgment transactions. This multi-functionality consolidates what would otherwise require separate systems, improving security through a unified verification mechanism while actually reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If execution requirements are verified for each control command in a heterogeneous network, then reliability of command execution is improved, but processing time increases

Engineering Contradiction:

Improveaccuracy of device-specific requirement verificationVSAvoidtime for verifying execution requirements

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Execution requirements are determined and attached to control transactions before they are stored in the distributed database system. This preliminary action allows devices to quickly verify requirements without performing complex analysis in real-time, improving verification accuracy while reducing processing time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback through acknowledgment transactions that confirm whether control commands were executed successfully. This feedback mechanism allows the system to verify execution reliability efficiently by comparing expected outcomes with actual results, rather than requiring extensive pre-verification of all possible execution scenarios.

Inventive Principle:

Principle #23Feedback

3Reliability

If control transactions are stored in a distributed database system, then tamper-proof security is improved, but storage requirements and system complexity increase

Engineering Contradiction:

Improvetamper-proof security of transactionsVSAvoidcomplexity of distributed database system

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system merges control commands with their execution requirements into single control transactions, which are then stored together in the distributed database system. This combining approach ensures tamper-proof security by maintaining the integrity relationship between commands and requirements, while reducing complexity by eliminating the need for separate storage and synchronization mechanisms.

Inventive Principle:

Principle #5Merging (Combining)

4Reliability

If acknowledgment transactions are checked before executing control commands, then reliability of command execution is improved, but processing speed decreases

Engineering Contradiction:

Improveensuring prerequisite commands are executedVSAvoidspeed of control command execution

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs acknowledgment checks for prerequisite control commands as a preliminary step before executing the main control command. This preliminary verification ensures reliability by confirming that necessary prerequisites are met, while the structured approach to checking acknowledgments minimizes processing overhead and maintains execution speed.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentEP3669285B1Method and system for controlling and/or monitoring of devices

Publication Date: 2021.09.08 SIEMENS AG

Figure 1
Figure 2
Figure 3

AI summary

The invention allows complex control command chains to be processed in a simple manner in an (automation) network, in which nodes and/or device nodes and/or blockchain-external devices are networked with one another, even if different operators of the individual nodes and devices do not have trust relations between themselves.