Blockchain Subsystem Update Distribution for Vehicle Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicles face challenges in efficiently updating their numerous sub-systems' software and firmware due to the need for direct internet connections and individual management, which can lead to inefficient and insecure update processes.

Innovation Solution

Implementing blockchain technology for peer-to-peer communication allows a first sub-system to monitor and download updates for other sub-systems, using separate blockchains for version numbers and update files, reducing processing power and ensuring immutability and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If direct internet connection is required to download updates from main server, then update availability is ensured, but system complexity and energy consumption increase

Engineering Contradiction:
Improveupdate availabilityVSAvoidcommunication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The update management system is segmented into multiple independent sub-systems, each capable of autonomously monitoring its own update requirements and downloading updates from the blockchain network without requiring centralized server coordination. This segmentation reduces communication complexity while maintaining update availability through distributed peer-to-peer interactions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each sub-system is equipped with autonomous capabilities to monitor blockchain for update notifications, identify required updates, and download them independently. This self-service mechanism eliminates the need for complex centralized server communication protocols, reducing system complexity while ensuring updates are obtained reliably from the immutable blockchain ledger.

Inventive Principle:
Principle #25Self-service

2Measurement precision

If each sub-system is individually managed and updated, then update precision is maintained, but time consumption and processing overhead increase

Engineering Contradiction:
Improveupdate management precisionVSAvoidupdate time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

Multiple sub-systems are merged into a unified blockchain-based update management framework where all sub-systems share common update information stored on the blockchain. This allows simultaneous monitoring and coordinated updates across multiple sub-systems, maintaining individual precision while reducing overall time consumption through parallel processing capabilities.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Update information is preliminarily stored and validated on the blockchain before distribution to sub-systems. The blockchain maintains a ready pool of verified update packages that sub-systems can quickly retrieve and install, eliminating the need for real-time validation and reducing update time while maintaining precision through pre-verified update integrity.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If large update files are stored in blockchain, then update completeness is ensured, but processing efficiency and energy consumption decrease

Engineering Contradiction:
Improveupdate data completenessVSAvoidprocessing energy
Core Design Contradiction:
Quantity of substanceVSUse of energy by moving object

Solution Approach 1:

Large update files are extracted from the blockchain structure and stored separately in distributed file storage systems. The blockchain retains only essential metadata including version numbers, update descriptors, and file location pointers. This extraction maintains update completeness by preserving all necessary information while dramatically reducing processing energy requirements for monitoring and validation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The update storage system transitions from a single-dimension blockchain structure to a multi-dimensional architecture where metadata resides on the blockchain and large files are stored in external distributed storage. This dimensional separation allows efficient blockchain monitoring for update detection while minimizing energy consumption during file transfer and installation operations.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Reliability

If blockchain monitoring is performed for all sub-systems, then update detection completeness is ensured, but processing overhead increases

Engineering Contradiction:
Improveupdate detection completenessVSAvoidprocessing power
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The blockchain monitoring function is segmented and assigned to specific sub-systems based on their update requirements. Each sub-system monitors only the blockchain segments relevant to its updates, ensuring complete detection of required updates while reducing overall processing power consumption through specialized division of monitoring responsibilities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10936302B2Updating sub-systems of a device using blockchain
Publication Date: 2021.03.02 POLESTAR PERFORMANCE
  • US10936302B2 patent drawing
  • US10936302B2 patent drawing
  • US10936302B2 patent drawing

AI summary

In general, techniques are described by which provide a technique for securely updating sub-systems of a device. A device includes multiple sub-systems including a first sub-system and a second sub-system. Each sub-system includes one or more processors. One or more processors of the first sub-system may be configured to perform the techniques herein. The one or more processors of the first sub-system are configured to download, from one or more nodes of a network, a sub-system update for the second sub-system in response to detecting an update to a ledger of a blockchain associated with the second sub-system. The one or more processors of the first sub-system are further configured to distribute the sub-system update for the second sub-system to the second sub-system.