Blockchain Sensor Data Validation via Cryptographic Hashing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the IoT environment, there is a need to validate the integrity and origin of sensor data, particularly in ensuring that the data comes from a specific sensor, was recorded at a specific location, and at a specific time, as existing methods lack irrevocable proof and are not scalable for diverse sensors in remote locations.
Innovation Solution
The use of a blockchain to validate sensor data by obtaining sensor data, calculating a signature, and storing it encrypted with a private key, allowing decryption with a public key to verify the source, location, and timestamp, providing an immutable record of sensor data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sensor data is validated using traditional methods, then the validation process is simple, but the integrity and authenticity of sensor data cannot be ensured
Solution Approach 1:
The patent introduces a blockchain as an intermediary layer between sensors and data consumers. The blockchain stores cryptographic hashes of sensor data along with metadata (location, timestamp, sensor ID), acting as a trusted mediator that verifies data authenticity without requiring complex point-to-point validation between each sensor and every consumer. This resolves the contradiction by providing strong reliability through the blockchain intermediary while keeping individual sensor devices simple.
Solution Approach 2:
The patent creates cryptographic copies of sensor data in the form of hash values stored on the blockchain. Instead of storing or transmitting the actual sensor data multiple times, the system stores compact hash representations that serve as immutable copies for verification purposes. This ensures data integrity through copying while minimizing the complexity and storage requirements compared to duplicating full data sets.
2Reliability
If sensor data is stored with full validation metadata, then the authenticity and source verification are improved, but the data storage and transmission overhead increases
Solution Approach 1:
The patent extracts only the essential validation metadata needed for verification (sensor ID, location, timestamp) and stores it on the blockchain alongside cryptographic hashes. The actual full sensor data remains separate, and only the extracted critical elements are replicated and stored for verification purposes. This approach improves source verification capability while minimizing the quantity of stored data by taking out only what is necessary.
Solution Approach 2:
The patent applies different quality levels to different parts of the data system. Full sensor data is stored locally at the source or in distributed storage, while the blockchain contains a streamlined version with just the essential validation metadata and hashes. This local quality differentiation ensures source verification capability where needed (on the blockchain) without unnecessarily replicating all data everywhere, thus controlling data volume.
3Reliability
If blockchain validation is implemented for all sensor data, then the tamper-proof verification is achieved, but the processing time and computational overhead increases
Solution Approach 1:
The patent performs preliminary actions by computing cryptographic hashes of sensor data and storing them on the blockchain at the time of data generation. This preliminary hashing and storage of validation information eliminates the need for complex real-time verification computations when data is consumed. The tamper-proof verification is achieved through this preliminary action, and the actual verification at consumption time is simplified to comparing hashes, thus reducing processing time.
4Reliability
If cryptographic signatures are calculated for sensor data, then the data authenticity is ensured, but the computational energy consumption increases
Solution Approach 1:
The patent uses cryptographic hashing (a form of copying) instead of full digital signatures for the sensor data itself. The hash function creates a compact cryptographic representation of the data that is computationally efficient to generate. Full cryptographic signatures are applied only to the metadata and hash values stored on the blockchain, not to every sensor data point. This copying approach ensures data authenticity while minimizing energy consumption compared to signing every data point.
Data Source
AI summary
Techniques are provided for validating sensor data using a blockchain. An exemplary method comprises: obtaining sensor data from a sensor; retrieving a transaction identifier from a blockchain; saving one or more public properties of the sensor and the transaction identifier in an output metadata stream; calculating a signature of the obtained sensor data, the one or more public properties of the sensor and the transaction identifier; saving the signature in the output metadata stream; and storing the signature encrypted with a private key of the sensor as a transaction in the blockchain. An exemplary validation of sensor data comprises decrypting the encrypted signature from the blockchain using a public key of the sensor and comparing the decrypted signature with a signature of the sensor data obtained from the output metadata stream.