Federated Data Management via Blockchain Notarization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data management between enterprises during cross-company transactions is resource-intensive and insecure, particularly in cross-company supply chains, where data sharing and verification require manual management and are prone to errors.
Innovation Solution
Implementing a computer-implemented method for federated data management using a blockchain network to notarize root hash values of data objects, enabling secure and authentic data sharing and verification between partner systems through peer-to-peer communication and event management based on hash references.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual data management is used between enterprises, then data exchange can occur, but the process becomes resource-intensive and insecure
Solution Approach 1:
The patent introduces a blockchain network as an intermediary between partner systems. The blockchain stores notarized root hash values of data objects, serving as a trusted mediator that enables secure data verification without requiring manual intervention. This intermediary mechanism resolves the contradiction by providing automated security validation (improving reliability) while eliminating manual management overhead (improving productivity).
Solution Approach 2:
The patent replaces manual data management mechanisms with automated cryptographic verification. Instead of manual data exchange processes, the system uses hash-based verification where partner systems automatically verify data authenticity by comparing root hash values stored on the blockchain. This substitution of mechanical manual processes with automated cryptographic mechanisms simultaneously improves security and resource efficiency.
2Reliability
If complete data replication is performed between partner systems, then data sharing is comprehensive, but data privacy and security are compromised
Solution Approach 1:
The patent extracts only the essential verification element (root hash value) from the complete data object and stores it on the blockchain. Partner systems can verify data authenticity using this extracted hash without needing access to the complete data. This extraction approach maintains data authenticity verification capability while preserving data privacy, as the sensitive complete data remains localized and is not replicated across the network.
Solution Approach 2:
The patent uses cryptographic hashing to create a digital fingerprint (hash value) of the data object. This hash copy serves as a verification token that proves data authenticity without being the data itself. Partner systems receive and verify this hash copy rather than the complete data, enabling authentication while maintaining privacy. The hash acts as a lossless copy for verification purposes only.
3Measurement precision
If traditional data verification methods are used, then data exchange occurs, but the verification process is complex and resource-intensive
Solution Approach 1:
The patent changes the verification parameter from complex manual validation to simple hash comparison. Instead of verifying complete data sets through complex processes, the system transforms verification into a straightforward comparison of root hash values. This parameter change maintains verification accuracy (ensuring data integrity) while dramatically reducing system complexity and resource requirements.
Data Source
AI summary
Methods, systems, and computer-readable storage media for federated data management between partner systems is provided. A hash structure is generated for a first data object and includes a first root hash value. The hash structure maps properties of the first data object with corresponding visibility levels for the first data object. The first root hash value is notarized to store the first root hash value in a blockchain network. A request is received to share data for the first data object from a first partner system to a second partner system. The first partner system determines the data to be shared with the second partner system based on a visibility criteria defined in relation to the first data object and the second partner system. The data and a hash proof for the data for verification of authenticity of the data is shared with the second partner system.