Simulation Data Management With Hash-Verified Ledger Registration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems using distributed ledger technology, such as blockchain, fail to prevent falsification of data during registration and registration of erroneous data in the ledger.

Innovation Solution

Implement a data management device that generates and verifies hash values using the same hash algorithm for data received from an external device, ensuring that only matching hash values allow data registration in the distributed ledger, thereby preventing falsification and erroneous data entry.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If distributed ledger technology is used to store data, then data reliability is improved, but data falsification at registration time and erroneous data registration cannot be prevented

Engineering Contradiction:
Improvedata reliabilityVSAvoiddata falsification and erroneous data registration
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary hash value generation at the external device before data transmission. The external device generates a first hash value of the data and transmits it to the data management device, which then generates a second hash value and compares it with the first hash value. This preliminary action of generating and transmitting the hash value allows the system to detect data falsification and erroneous data registration before registration in the distributed ledger.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the data management device receives the first hash value from the external device, generates a second hash value locally, and compares the two hash values. Based on this comparison feedback, the system determines whether to register the data in the distributed ledger. This feedback loop ensures that only genuine data is registered, preventing both falsification and erroneous data registration.

Inventive Principle:
Principle #23Feedback

2Reliability

If hash value verification is implemented, then data integrity is improved, but system complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The external device performs self-service by generating its own first hash value before transmitting data to the data management device. This self-service approach allows the external device to prepare the data for verification independently, reducing the burden on the data management device and simplifying the overall system architecture while maintaining data integrity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses parameter changes by transforming the data into a hash value parameter. Instead of storing and verifying the original data directly, the system converts the data into a fixed-length hash value that can be efficiently compared. This parameter transformation simplifies the verification process and reduces computational complexity while ensuring data integrity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12425244B2Data management device and data management system
Publication Date: 2025.09.23 TOYOTA JIDOSHA KK
  • US12425244B2 patent drawing
  • US12425244B2 patent drawing
  • US12425244B2 patent drawing

AI summary

The client device executes a simulation, and generates a data set including result data and metadata based on the execution result. The client device generates a first hash value of the data set and transmits the data set and the first hash value to the data management device. When the data set and the first hash value are received from the client device, the data management device generates a second hash value of the data set from the data set. The data management device decides to register the data set in the distributed ledger when the first hash value and the second hash value match each other.