Vehicle Data Storage Segmentation and Hash Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems for vehicles face challenges in ensuring data integrity and privacy, particularly with the increasing use of ADAS and autonomous driving systems, where sensitive data is collected and stored, and there is a need for efficient management within legal boundaries.
Innovation Solution
A centralized data storage system that separates vehicle identification information from event and interaction data, using a salt and one-way hash functions to generate link data, allowing for secure storage and retrieval of vehicle-generated data while ensuring privacy protection and compliance with regulations like GDPR.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If vehicle identification information is stored together with event data and interaction data in the same database, then data retrieval and management is simplified, but data privacy and security are compromised
Solution Approach 1:
The patent divides the database into separate tables: a first database storing vehicle identification information and a salt value, and a second database storing event data and interaction data with a hash value. This segmentation isolates sensitive personal information from operational data, preventing unauthorized access to vehicle owner identities while maintaining efficient data management through structured separation.
Solution Approach 2:
The patent introduces a hash value as an intermediary element that links vehicle identification information to event and interaction data without exposing the actual identification information. The hash value acts as a mediator that enables data retrieval and association while protecting the underlying personal information, allowing the system to maintain both security and operational efficiency.
2Productivity
If all vehicle data is stored in a centralized cloud database, then data accessibility and analysis capability are improved, but data integrity and susceptibility to manipulation increase
Solution Approach 1:
The patent applies a one-way hash function to vehicle identification information before storage, creating a hash value that serves as a digital fingerprint. This preliminary transformation ensures that even if the centralized database is compromised, the original identification information cannot be recovered from the hash values, thereby preserving data integrity while maintaining centralized storage benefits.
Solution Approach 2:
The patent replaces direct storage of sensitive vehicle identification information with cryptographic hash values in the centralized database. This substitution eliminates the risk of direct manipulation or recovery of personal information while maintaining the ability to link and retrieve associated event and interaction data through the hash value references.
3Measurement precision
If vehicle data is collected and stored for forensic investigation purposes, then accident analysis capability is improved, but risk to individual privacy increases
Solution Approach 1:
The patent extracts and separates vehicle identification information from event and interaction data, storing them in different database tables. This extraction removes personally identifiable information from the forensic analysis dataset, allowing detailed accident reconstruction and analysis while protecting individual privacy by preventing direct linkage between事故 data and vehicle owner identities.
Solution Approach 2:
The patent transforms vehicle identification information into hash values, changing the parameter form from readable personal identifiers to cryptographic representations. This parameter transformation enables precise forensic analysis of vehicle behavior and accident dynamics while eliminating the privacy risk associated with storing and processing actual vehicle identification numbers and owner information.
Data Source
AI summary
An embodiment method, performed by at least one server on a network for collecting and managing vehicle-generated data from a vehicle, includes receiving an event report message and an interaction report message from the vehicle, the event report message including vehicle identification information and event data stored by an event data recorder of the vehicle, and the interaction report message including the vehicle identification information and interaction data indicative of an interaction between an autonomous driving system of the vehicle and a driver, generating link data from the vehicle identification information and a salt, storing the vehicle identification information and the salt in a first database, storing the event data and the link data in a second database, and storing the interaction data and the link data in a third database.


