Blockchain Code Verification for Network Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network connected devices face challenges in verifying the trustworthiness of received code due to vulnerabilities in traditional security mechanisms, especially in intermittent or non-persistent network connections, where hashing and signing can be compromised by malicious entities.

Innovation Solution

A computer-implemented method using a blockchain data structure maintained by a base station to distribute code, where the target device verifies the code's validity by comparing hash values with a broadcasted current state of the blockchain, ensuring the code originates from a trusted source and is suitable for execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional hashing and signing mechanisms are used for code distribution, then code authenticity can be verified, but the security is compromised by malicious entities in non-persistent network connections

Engineering Contradiction:
Improvecode authenticity verificationVSAvoidspoofing and unauthorized modification
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a blockchain-based intermediary verification system that mediates between the code distribution server and target devices. The blockchain acts as a trusted third party that records and verifies code hashes, preventing malicious entities from spoofing code authenticity even in non-persistent network connections. The verification process uses blockchain-stored hash values as an intermediary reference to confirm code integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-storing code hash values in the blockchain before actual code distribution occurs. This advance preparation creates a trusted reference framework that enables rapid verification when code is distributed, ensuring security even when network connections are intermittent or non-persistent.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If blockchain verification is implemented for code distribution, then code reliability is improved, but system complexity increases

Engineering Contradiction:
Improvecode distribution trustworthinessVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex blockchain verification logic from the target devices and concentrates it in the base station and distribution servers. Target devices only need to perform simple hash comparison operations using pre-distributed verification information, while the heavy lifting of blockchain state management and verification is handled by dedicated infrastructure components.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates simplified copies of the verification process by distributing verification information (code hashes and blockchain state references) to target devices in advance. This allows devices to perform lightweight local verification without needing to implement full blockchain clients, reducing complexity while maintaining reliability.

Inventive Principle:
Principle #26Copying

3Object-affected harmful factors

If comprehensive security verification is performed on all received code, then unauthorized modifications are prevented, but processing time increases

Engineering Contradiction:
Improveunauthorized code modificationVSAvoidcode verification time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The patent implements partial verification by focusing security checks on critical elements (code hash values and blockchain state references) rather than performing exhaustive analysis of all code components. This selective verification approach provides sufficient security against unauthorized modifications while minimizing verification time.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Verification data including code hashes and blockchain references are prepared and distributed in advance before actual code execution is needed. This preliminary preparation eliminates the need for time-consuming verification during code execution, reducing loss of time while maintaining comprehensive security checks.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10534913B2Blockchain state reliability determination
Publication Date: 2020.01.14 BRITISH TELECOM PLC
  • US10534913B2 patent drawing
  • US10534913B2 patent drawing
  • US10534913B2 patent drawing

AI summary

Disclosed herein is a computer implemented method for receiving code distributed by a base station at a target device via a network, the distribution being made to one or more destination devices including the target device via one or more distribution servers arranged between the base station and the one or more devices on the network, wherein the base station maintains a first blockchain data structure storing one or more blocks and having a state determined by a most recently committed block in the first blockchain.