Key Exchange Control for Private-Public Blockchain Lineage Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in maintaining data lineage on private blockchains, particularly when third-party vendors need access to update data lineage on a corporation's private blockchain, due to the lack of interoperability between private and public blockchains.
Innovation Solution
A key exchange controller (KEC) is introduced to facilitate communication and access permission between private and public blockchains, generating smart contracts and key exchange protocols to allow entities on public blockchains to access and maintain data lineage on private blockchains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a corporation stores sensitive data on a private blockchain to maintain security and control, then data security and privacy are improved, but interoperability with public blockchains and access by third-party vendors deteriorate
Solution Approach 1:
The patent introduces a key exchange controller as an intermediary component that enables secure communication between private and public blockchains. The key exchange controller generates and manages cryptographic key pairs, allowing third-party vendors on public blockchains to access and verify data lineage on private blockchains without compromising the underlying data security. This mediator resolves the contradiction by enabling controlled interoperability while maintaining security boundaries.
2Reliability
If third-party vendors are granted access to update data lineage on a private blockchain, then data lineage completeness and authenticity are improved, but system complexity and access control requirements worsen
Solution Approach 1:
The patent implements a self-service mechanism where the key exchange controller automatically generates cryptographic key pairs and manages access credentials for third-party vendors. The system autonomously handles key generation, distribution, and rotation without requiring manual intervention for each access request. This automation reduces the operational complexity of access control while maintaining robust security protocols for data lineage updates.
Solution Approach 2:
The key exchange controller serves as an intermediary that simplifies access control by centralizing key management functions. Instead of implementing complex access control logic across multiple nodes, the intermediary consolidates authentication and authorization mechanisms, making the system easier to manage while enabling third-party vendors to securely update data lineage.
3Reliability
If data is kept on a private blockchain for security reasons, then data privacy is improved, but the ability to maintain updated data lineage documentation deteriorates
Solution Approach 1:
The patent applies segmentation by separating data storage from data lineage documentation. Sensitive data remains on the private blockchain maintaining privacy, while data lineage information is documented on both private and public blockchains. The key exchange controller enables public blockchain nodes to verify and record lineage metadata without accessing the underlying sensitive data, thus preventing information loss while preserving privacy.
Solution Approach 2:
The key exchange controller acts as an intermediary that enables public blockchain participants to contribute to data lineage documentation without compromising data privacy. It allows vendors on public blockchains to retrieve and update lineage information about private blockchain data, ensuring comprehensive documentation is maintained while the sensitive data itself remains private and secure on the private blockchain.
Data Source
AI summary
Systems, apparatuses, methods, and computer program products are disclosed for providing interoperability between private and public blockchains. An example method for providing interoperability between private and public blockchains includes, by a key exchange controller (KEC): receiving access key generation instructions; generating, based on the key generation instructions, an access key comprising access credentials; transmitting the access key to an access key target on a public blockchain network; receiving, from the access key target, a access request including the access credentials and information indicating a private blockchain on a private blockchain network; and providing, in response to receiving the access request, access for the access key target to access the private blockchain of the private blockchain network.