Connected Vehicle Anomaly Detection via Distributed Ledger Trust

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Connected vehicle networks face challenges in determining the trustworthiness of data from external nodes, leading to potential unnecessary vehicle movements due to incorrect or anomalous data from unverified sources, and the risk of central authority corruption.

Innovation Solution

A distributed ledger system is used to manage trust by identifying unique identifiers of nodes and executing a consensus algorithm to determine trustworthiness, with cameras and sensors identifying anomalies in received data to update the ledger, ensuring only trusted data is used for vehicle control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data from all external nodes is accepted without verification, then the quantity of available data increases, but the reliability of the connected vehicle system deteriorates due to anomalous data from untrusted sources

Engineering Contradiction:
Improvequantity of dataVSAvoiddata reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent introduces a distributed ledger as an intermediary mechanism that mediates between external data sources and the vehicle control system. The ledger stores and verifies unique identifiers of trusted nodes, acting as a gatekeeper that allows quantity of data to increase while maintaining reliability through cryptographic verification of data sources

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary verification by checking unique identifiers against the distributed ledger before accepting data from external nodes. This advance validation ensures that only data from pre-verified trusted sources is processed, preventing anomalous data from compromising system reliability

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If a central authority is used to verify node trustworthiness, then the ease of operation increases with centralized verification, but the reliability deteriorates due to potential corruption of the central authority

Engineering Contradiction:
Improveease of verificationVSAvoidtrust verification reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized verification function into a distributed ledger system where verification capabilities are distributed across multiple nodes. Each vehicle and infrastructure element maintains a copy of the ledger, eliminating the single point of failure and corruption risk associated with centralized authorities while maintaining ease of verification through consistent cryptographic protocols

Inventive Principle:
Principle #1Segmentation

3Productivity

If data from unverified sources is used for vehicle control, then the productivity of the connected vehicle system increases through more data-driven decisions, but the reliability deteriorates due to incorrect data causing unnecessary vehicle movements

Engineering Contradiction:
Improvesystem responsivenessVSAvoidcontrol accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary verification of unique identifiers against the distributed ledger before data is used for control decisions. This advance validation ensures that high-productivity data-driven operations only process information from verified trusted sources, preventing incorrect data from causing erroneous vehicle movements

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10599140B2System and method for mitigation of anomalous data in a connected vehicle system
Publication Date: 2020.03.24 GENERAL MOTORS LLC
  • US10599140B2 patent drawing
  • US10599140B2 patent drawing
  • US10599140B2 patent drawing

AI summary

At least one transceiver is configured to wirelessly receive data from a source node that is external to a vehicle, the data including a unique identifier (ID) of the source node and at least one of: a first location of the source node; a first heading of the source node; a first speed of the source node; and a first object type of the source node. At least one of a camera and a sensor is configured to identify objects located around the vehicle. An anomaly module is configured to selectively indicate that an anomaly is present in the data. A distributed ledger includes a list of unique IDs associated with not-trusted source nodes. A ledger management module is configured to, in response to an indication that an anomaly is present in the data received from the source node, add the unique ID of the source node to the list.