Blockchain Truth Graph for Semantic Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Enterprise Application Integration techniques fail to achieve real-time data synchronization across disparate systems of record, leading to semantic interoperability challenges, especially across organizational boundaries, due to differences in data models and lack of operational infrastructure for real-time data synchronization.
Innovation Solution
A system and method for propagating identity state changes across multiple systems of record using a management server that detects CRUD operations, generates an identity state change set, and synchronizes it through a distributed immutable storage and domain cache, leveraging blockchain technology for secure and timely data replication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional Message-Oriented Middleware systems are used for data sharing, then network transparency is achieved for physical topology changes, but semantic interoperability cannot be achieved across organizational boundaries due to opaque IT topologies and unknown data models
Solution Approach 1:
The patent introduces a blockchain-based intermediary layer that mediates between disparate systems of record. This intermediary enables semantic interoperability by providing a common truth graph that translates and reconciles data from different organizational boundaries without requiring direct knowledge of each system's internal topology or data model.
Solution Approach 2:
The system achieves universality by creating a multi-functional platform that handles various data types and organizational boundaries through a single blockchain-based truth graph. This universal approach allows any system to participate in data sharing without requiring system-specific integration logic.
2Quantity of substance
If data is stored in multiple internal databases for different business functions, then comprehensive data coverage is achieved, but real-time synchronization becomes difficult due to lack of operational infrastructure
Solution Approach 1:
The patent implements continuous synchronization by maintaining a blockchain-based truth graph that continuously updates and propagates changes across all systems of record. This ensures that data remains consistent across multiple databases in real-time without requiring batch processing or manual intervention.
Solution Approach 2:
The system employs feedback mechanisms where changes in one system automatically trigger updates in other systems through the blockchain truth graph. This feedback loop ensures that data inconsistencies are automatically resolved and all systems remain synchronized with the current state of truth.
3Device complexity
If manual data entry or ad-hoc batch processing is used for data propagation, then system complexity is reduced, but data freshness and accuracy deteriorate due to non-real-time updates
Solution Approach 1:
The patent implements self-service data propagation where the blockchain system automatically detects, validates, and propagates changes across systems without requiring manual intervention. The system serves itself by maintaining the truth graph and automatically synchronizing data, eliminating the need for ad-hoc batch processing while ensuring data accuracy.
Data Source
AI summary
A system for propagating an identity state change set about shared identities may include a plurality of systems of record (SORs), and a management server cooperating with the plurality of SORs and configured to: detect discrete Create-Retrieve-Update-Delete (CRUD) operations on a given SOR related to at least one shared identity to generate an identity state change set corresponding to a current state of the at least one shared identity; transact the identity state change set, with associated metadata, to a distributed immutable long-term storage as a current transaction; propagate the identity state change set and associated metadata to replicate a current state of the at least one shared identity as of the current transaction to at least one domain cache instance, and; synchronize the current state of the at least one shared identity across the plurality of SORs from the at least one domain cache instance.