Server Device Traceability Blockchain Stakeholder Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data management techniques using blockchain struggle to ensure both tamper resistance and data sovereignty, particularly when dealing with information from multiple stakeholders, as they require browsing all original data to verify non-tampering, which compromises data sovereignty.
Innovation Solution
A server device and method that stores data with identification information for stakeholders, generates hash values for management data, and issues transactions to a blockchain, ensuring that only specific stakeholder information remains unchanged, allowing for n types of management data to be created and verified, thereby maintaining tamper resistance and data sovereignty.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all original data is browsed to verify non-tampering, then tamper resistance is guaranteed, but data sovereignty is compromised
Solution Approach 1:
The patent segments the verification process by creating separate management data for each stakeholder. Instead of browsing all original data, each stakeholder receives customized management data containing only their own information plus hash values. This segmentation allows verification of tamper resistance while preserving data sovereignty, as each party only accesses their own segmented data portion.
Solution Approach 2:
The patent creates multiple copies of management data, each tailored to a specific stakeholder. These copies contain the same hash values for verification purposes but differ in the actual data content shown to each stakeholder. This copying approach enables tamper verification through hash comparison while maintaining data sovereignty by ensuring each stakeholder only sees their own information in the copied data.
2Quantity of substance
If multiple stakeholders' information is stored together, then data completeness is improved, but data sovereignty cannot be guaranteed
Solution Approach 1:
The patent applies local quality by customizing the data presentation for each stakeholder. The management data has different local qualities (content) for different stakeholders, even though the underlying hash verification structure remains the same. Each stakeholder's management data contains their specific information with appropriate quality tailored to their needs, while the hash values ensure overall data completeness and integrity.
3Measurement precision
If hash values for all stakeholders are recorded in blockchain, then verification capability is improved, but system complexity increases
Solution Approach 1:
The patent creates management data structures that serve multiple functions simultaneously. Each management data copy serves as both verification data (containing hash values) and personalized stakeholder data (containing specific stakeholder information). This multi-functionality reduces system complexity by eliminating the need for separate verification systems for each stakeholder, while maintaining precise verification capability through the universal hash comparison mechanism.
Data Source
AI summary
A server device stores data sent from a client device together with data identification information and stakeholder identification information that identifies a stakeholder operating the client device. A controller determines a number of stakeholders included in the data, and, in a case where the data stores information on stakeholders of a plurality of n organizations, leaves information on a specific stakeholder unrewritten and rewrites information of other stakeholders with optional information to generate n types of management data. The controller generates first hash value for each of the n types of management data, and controls n transactions including the first hash value to be issued to a blockchain, and transmits the transaction. The controller returns, in response to a browsing request specifying the data identification information and the stakeholder identification information from the client device, management data corresponding to the stakeholder identification information among the n types of management data.