Decentralized Secure Data Sharing via Blockchain
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized databases are inefficient for secure and precise data sharing among multiple clients, as they lack decentralized and secure mechanisms for data access and management.
Innovation Solution
A decentralized system utilizing a blockchain-based approach with smart contracts and a distributed ledger for secure and precise sharing of persistent data, enabling multiple clients to access and share data through a common data store without a single owner, using request and receipt keys for authentication and access control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a centralized database is used for data storage and sharing, then data management and control are simplified, but security and efficiency for multi-client data sharing deteriorate
Solution Approach 1:
The patent divides the centralized database into multiple distributed nodes across a blockchain network. Each node maintains a copy of the ledger, eliminating the single point of control while distributing security responsibilities. This segmentation allows multiple clients to share data securely without relying on a single centralized authority.
Solution Approach 2:
The patent introduces smart contracts as intermediary automated agreements that mediate data access and sharing between clients. These self-executing contracts enforce access rules and permissions without requiring manual intervention or centralized control, thereby improving both security and operational efficiency for multi-client data sharing.
2Quantity of substance
If a centralized database is used for data storage, then data redundancy is minimized with a single storing place, but efficiency for decentralized data sharing among multiple clients deteriorates
Solution Approach 1:
The patent creates a universal blockchain ledger that serves multiple functions simultaneously: it stores data, manages access permissions, enables sharing among multiple clients, and maintains security protocols. This multi-functional system eliminates the need for separate centralized databases for each client while improving sharing efficiency through standardized access mechanisms.
Solution Approach 2:
The patent implements distributed copying of the database ledger across multiple nodes in the blockchain network. Each node maintains an identical copy of the data, eliminating data redundancy issues while enabling efficient decentralized access. Clients can query and share data from any node, improving productivity without creating unnecessary duplicates.
3Ease of operation
If multiple clients access data through a centralized database, then data accessibility is improved, but security control and precision in data sharing deteriorate
Solution Approach 1:
The patent implements local quality control through client-specific access permissions and encryption keys stored in individual wallets. Each client has customized access rights to specific data sets, allowing precise control over what each client can view or share. This localized permission system maintains high accessibility while enforcing precise security boundaries for each client.
Solution Approach 2:
The patent uses parameter changes in the form of cryptographic keys and access tokens that dynamically control data sharing permissions. Access permissions are not static but can be modified by changing cryptographic parameters, allowing precise control over data sharing while maintaining ease of access for authorized clients. The system can grant or revoke access by updating cryptographic parameters without restructuring the entire system.
Data Source
AI summary
An example operation may include one or more of registering a first service node and a second service node for accessing a common data store, providing to the second client node, by the first client node, a data access request token key and a data access receipt key corresponding to a data access request, responsive to a receipt of the access request token key and the data access receipt key by the second service, retrieving a result from the common data store; and providing the result to the second client node.


