Privileged Node Blockchain for Vehicle Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle data storage systems using Proof of Work (PoW) blockchain technology face high computational burdens, leading to increased costs and energy consumption, and risk data loss due to fork occurrences, while privileged node systems are costly and prone to operational failures.

Innovation Solution

A vehicle data storage method using a blockchain with multiple nodes sharing a common key, where new blocks are generated and verified by other nodes, with a majority vote determining validity and re-transmission of verification requests to avoid forks, allowing for cost-effective and robust data storage without the need for high-performance computing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PoW-type blockchain system is used to store vehicle data, then data credibility is improved, but computational burden and energy consumption increase significantly

Engineering Contradiction:
Improvedata credibilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the nonce value search function from all participant miners and assigns it to a privileged node. This removes the computationally intensive PoW mechanism from the general node population, retaining only the essential blockchain verification and data storage functions that provide credibility without the energy-intensive mining process.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a privileged node as an intermediary that generates blocks on behalf of the network. This mediator performs the block generation and verification functions centrally, allowing ordinary nodes to participate in data storage and verification without bearing the computational burden of PoW, thus reducing overall energy consumption while maintaining system reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Stability of the object's composition

If difficulty of finding appropriate nonce value is set high to avoid fork, then chain stability is improved, but computational burden and energy consumption increase

Engineering Contradiction:
Improvechain stabilityVSAvoidenergy consumption
Core Design Contradiction:
Stability of the object's compositionVSUse of energy by moving object

Solution Approach 1:

The patent removes the nonce value search process from the system by having privileged nodes generate blocks directly without requiring PoW validation. This extracts the source of both chain stability (through controlled block generation) and energy consumption (through elimination of repeated hashing), resolving the contradiction between stability and energy use.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The privileged node performs block generation and verification functions that would otherwise require all nodes to participate in PoW. This self-service approach to block creation maintains chain stability through controlled generation while eliminating the need for energy-intensive nonce searching across the network.

Inventive Principle:
Principle #25Self-service

3Stability of the object's composition

If privileged nodes are introduced to generate blocks, then fork occurrence is avoided, but system cost and operational reliability risk increase

Engineering Contradiction:
Improvefork avoidanceVSAvoidsystem robustness
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

The patent designs the privileged node to perform multiple functions: block generation, verification, and network coordination. This multi-functional design consolidates critical operations in a single node type, reducing the complexity of managing multiple specialized nodes while maintaining fork avoidance through centralized control, thereby improving system robustness.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements verification mechanisms where ordinary nodes verify blocks generated by privileged nodes using public keys. This feedback loop ensures that even if a privileged node fails or behaves maliciously, the network can detect and reject invalid blocks, maintaining system reliability while preventing forks through proper verification protocols.

Inventive Principle:
Principle #23Feedback

4Quantity of substance

If multiple nodes generate blocks simultaneously, then data storage capacity is improved, but fork occurrence increases leading to data loss

Engineering Contradiction:
Improvedata storage capacityVSAvoiddata loss due to fork
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent establishes a predetermined hierarchy where privileged nodes have priority in block generation. This preliminary arrangement of generation rights prevents simultaneous block creation by multiple nodes, eliminating forks before they can occur. Data storage capacity is maintained through the privileged node's ability to process and include multiple transactions in each block it generates.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20230259293A1Vehicle data storage method and vehicle data storage system
Publication Date: 2023.08.17 DENSO CORP
  • US20230259293A1 patent drawing
  • US20230259293A1 patent drawing
  • US20230259293A1 patent drawing

AI summary

A vehicle data storage method implemented by each of a plurality of nodes includes: generating, as a new block, a block to be connected to the blockchain; verifying, using a common key, validity of a new block generated by, and distributed from, one of other nodes when requested by the one of the other nodes and transmitting a verification result to at least the one of the other nodes; connecting the new block to the blockchain when a majority of the plurality of nodes determines that the new block is valid; and if two new blocks are generated by two nodes and verification requests on the two new blocks are made at a substantially same time, retransmitting, by at least one of the two nodes, a verification request at random or when a predetermined time has elapsed.