Distributed Audit Trail for Vehicle Software Integrity Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack an efficient and scalable method to ensure software and data integrity in connected vehicles, particularly in the face of software updates and potential attacks, which can compromise safety-critical functions.
Innovation Solution
A distributed audit trail system utilizing a master unit with a blockchain light client and DHT, along with nodes and remote servers, to create a combined audit trail for vehicles, ensuring software and data integrity by verifying meta-hashes against a library of acceptable versions, and implementing a parity system for resilience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a distributed audit trail system with blockchain and DHT is implemented, then software and data integrity assurance is improved, but device complexity increases
Solution Approach 1:
The system segments the audit trail functionality into multiple independent components: master units at the vehicle level, remote servers at the cloud level, and blockchain technology for decentralized verification. Each segment handles specific tasks (local audit logging, remote storage, cryptographic verification) rather than requiring a single complex system, thereby improving reliability through distribution while managing complexity through modular design
Solution Approach 2:
The patent introduces intermediary components including the distributed hash table (DHT) as a mediator between master units and remote servers, and blockchain as a mediator for verifying software integrity. These intermediaries facilitate secure communication and verification without requiring direct complex interactions between all system components, thus enhancing integrity assurance while abstracting complexity
2Reliability
If full blockchain nodes are deployed in vehicles, then audit trail security is improved, but resource consumption increases
Solution Approach 1:
The system segments blockchain functionality between vehicle-based master units and remote servers. Master units perform lightweight operations (creating audit trails, generating hashes) while remote servers handle resource-intensive tasks (full blockchain node operations, comprehensive verification). This segmentation allows secure audit trails without requiring full blockchain nodes in resource-constrained vehicles
Solution Approach 2:
Instead of deploying full blockchain nodes in vehicles (excessive action), the system implements partial blockchain functionality at the vehicle level through master units that create and sign audit trails, while relying on remote servers for complete blockchain verification. This partial approach provides sufficient security for vehicle resources while maintaining audit trail integrity
3Adaptability or versatility
If software updates are allowed to enhance vehicle features, then adaptability is improved, but software integrity risks increase
Solution Approach 1:
The system implements feedback mechanisms where master units continuously monitor software changes, generate audit trails of software updates, and verify integrity through cryptographic hashes stored in the distributed ledger. This feedback loop enables the system to adapt to software updates while maintaining integrity verification, allowing feature enhancement without compromising security
Solution Approach 2:
The system performs preliminary actions by creating audit trails and cryptographic hashes of software before updates occur, and by pre-storing verified software hashes in the distributed ledger. When updates occur, the system can quickly verify integrity by comparing new software against the pre-stored hashes, enabling adaptability while maintaining integrity through advance preparation
Data Source
AI summary
Various disclosed embodiments pertain to a distributed audit trail system for use in a connected system including: a master unit to control a first aspect of the connected system and to create a blockchain light client and a distributed hash table (DHT); a first node to control a second aspect of the connected system; a second node to control a third aspect of the connected system; and one or more remote servers to form a blockchain full node, where the master unit, the first node, and the second node electronically communicate with each other through the DHT in order to form a combined audit trail, where the master unit creates a meta-hash of the software version of the software in the master unit, the first node, and the second node, system identification data, system sensor data, and system hardware configuration.