Vehicle Data Record Access via Blockchain Hash Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for providing vehicle datasets to third parties lack sufficient security and transparency, particularly in ensuring confidentiality and integrity.
Innovation Solution
A method involving cryptographic key pairs, where a public key is used to encrypt vehicle data and store a hash value in a blockchain database, allowing secure and transparent access control by the vehicle owner, with optional decryption on a mobile terminal or controller.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If vehicle data is transmitted to third parties through a central back-end server, then data accessibility is improved, but data security and confidentiality deteriorate
Solution Approach 1:
The system segments data access control by separating the cryptographic key pair management from the central server. The private key remains on the user's mobile terminal while the public key is stored on the server, enabling distributed security control. This segmentation allows third parties to access data through the server while the user maintains security control locally, resolving the contradiction between accessibility and security.
Solution Approach 2:
The system performs preliminary encryption of vehicle data using the user's public key before transmission to the server. This preliminary cryptographic action ensures that data is secured in advance during the upload process, allowing the server to store and transmit encrypted data to third parties without compromising confidentiality, thus maintaining both accessibility and security.
2Reliability
If data is encrypted using cryptographic key pairs, then data confidentiality is improved, but system complexity deteriorates
Solution Approach 1:
The system introduces a cryptographic intermediary layer where the public key acts as a mediator between the user and the server. The public key enables encryption of data without requiring the server to have access to the private key, simplifying the security model. This intermediary approach maintains confidentiality while avoiding the complexity of key management on the server side.
Solution Approach 2:
The system uses cryptographic key pairs where the public key is a functional copy that can be freely distributed and stored on servers without compromising security. This copying mechanism allows the encrypted data to be stored and accessed by third parties through the server while the original private key remains secure on the user's device, reducing system complexity by eliminating the need for complex key distribution protocols.
3Reliability
If hash values are stored in a blockchain database, then data integrity and transparency are improved, but storage requirements and system complexity deteriorate
Solution Approach 1:
The system extracts only the essential integrity verification component (hash value) and stores it in the blockchain database, while keeping the full encrypted data on the server. This extraction approach provides transparency and integrity verification through the immutable blockchain ledger without requiring the blockchain to store large volumes of data, thus maintaining data integrity while limiting the storage burden and complexity to only the necessary cryptographic proofs.
Data Source
AI summary
A method for providing a data record of a vehicle to a third party includes: receiving a cryptographic key pair including a public, cryptographic key and a private, cryptographic key; receiving the data record of the vehicle; encrypting the received data record by the public, cryptographic key; transmitting the encrypted data record to a data memory for storing the encrypted data record; generating a cryptographic hash value for the encrypted data record; transmitting the hash value of the encrypted data record to a blockchain database for storing the hash value of the encrypted data record; receiving a request message from a third party for retrieving the data record; generating a first request message to the data memory and a second request message to the blockchain database on the basis of the received request message; transmitting the first request message to the data memory and the second request message to the blockchain database; receiving the encrypted data record from the data memory in response to the first request message and the hash value of the encrypted data record from the blockchain database in response to the second request message; validating the encrypted data record by the hash value; and, when validation of the encrypted data record is successful: decrypting the encrypted data record by the private, cryptographic key; and transmitting the data record in response to the request message from the third party to a server of the third party.