V2V Sensor Data Sharing Using Blockchain for Collision Evidence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current vehicle data sharing systems, particularly those using centralized databases, are prone to single points of failure, lack data redundancy, and struggle with fraudulent claims, making them inefficient for storing and utilizing vehicle sensor data effectively, especially for safety and collision-related information.

Innovation Solution

A decentralized system utilizing a blockchain-based database for vehicle-to-vehicle (V2V) sensor data sharing, where sensors on vehicles detect potential events, transmit data to nearby vehicles, and store it on a server, enabling secure, immutable, and permissioned data management through smart contracts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used to store vehicle sensor data, then data storage and management is simplified, but the system has a single point of failure and lacks data redundancy

Engineering Contradiction:
Improvedata storage and managementVSAvoidsystem reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across the blockchain network. Each node maintains a copy of the data, eliminating the single point of failure while preserving data storage functionality. The blockchain partitions data into blocks that are distributed across multiple participants in the network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates multiple copies of the vehicle sensor data across different nodes in the blockchain network. Each participant maintains a replicated copy of the data, ensuring that if one node fails, the data remains accessible from other nodes. This copying mechanism provides the required redundancy while maintaining ease of data retrieval.

Inventive Principle:
Principle #26Copying

2Productivity

If a centralized database is used, then data storage is efficient, but data that is unexpectedly lost is very difficult to retrieve

Engineering Contradiction:
Improvedata storage efficiencyVSAvoiddata retrieval capability
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements beforehand cushioning by creating redundant copies of data across multiple blockchain nodes before any loss can occur. This preventive measure ensures that if data is lost from one node, identical copies are already available at other nodes, making retrieval possible without loss.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The system creates multiple copies of vehicle sensor data across the distributed blockchain network. Each node stores replicated data, ensuring that even if one copy is lost or corrupted, the data can be retrieved from any of the other replicated copies, thus preventing information loss.

Inventive Principle:
Principle #26Copying

3Device complexity

If a centralized database is used, then data management is straightforward, but the system cannot effectively prevent fraudulent claims

Engineering Contradiction:
Improvedata management complexityVSAvoidfraud prevention capability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where multiple nodes in the blockchain network verify and validate sensor data before accepting it into the ledger. This cross-validation feedback loop prevents fraudulent claims by requiring consensus among distributed participants, thereby enhancing reliability without significantly increasing management complexity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent merges the functions of data storage, verification, and validation into a single distributed blockchain system. Multiple nodes collectively perform these functions through consensus mechanisms, combining their computational resources to prevent fraud while maintaining a unified data management approach that doesn't overly complicate operations.

Inventive Principle:
Principle #5Merging (Combining)

4Reliability

If sensor data is shared among multiple vehicles, then data redundancy and security are improved, but system complexity increases

Engineering Contradiction:
Improvedata security and redundancyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes each blockchain node multi-functional, capable of storing data, verifying incoming data, validating sensor readings, and participating in consensus all in one system. This universality allows data to be shared across multiple vehicles for enhanced security and redundancy without requiring separate specialized systems for each function, thereby limiting the increase in complexity.

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

Data Source

PatentUS11961401B2Vehicle-to-vehicle sensor data sharing
Publication Date: 2024.04.16 TOYOTA MOTOR NORTH AMERICA INC
  • US11961401B2 patent drawing
  • US11961401B2 patent drawing
  • US11961401B2 patent drawing

AI summary

An example operation may include one or more of detecting a potential event via sensors on a transport, sending data related to the potential event to other transports within a predefined distance, storing the data at the transports and a server, and performing a transport operation response on the transports.