Central Node for Multi-Party Secure Data Query
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of multi-party secure databases, existing data query methods fail to adequately address data security requirements in sharing scenarios, making it difficult to ensure secure data sharing and protect private data.
Innovation Solution
A central node receives data query requests and processes target data only if they meet predefined security requirements set by data providers, using a logical plan to determine if the query operations are allowed or prohibited, thereby restricting access and ensuring secure data sharing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data providers provide data services independently, then data security is maintained, but data sharing capability is reduced
Solution Approach 1:
The patent introduces a central node as an intermediary between data providers and data requesters. The central node receives query requests, generates logical plans, and coordinates with multiple data providers to execute queries while enforcing security policies. This mediator enables secure multi-party data sharing without requiring independent data provider infrastructure, resolving the contradiction between maintaining security and enabling sharing.
Solution Approach 2:
The central node performs multiple functions: receiving queries, generating logical plans, validating security policies, coordinating data providers, and returning results. This multi-functional system replaces independent data provider services with a unified platform that maintains security while enabling broader data sharing capabilities across multiple parties.
2Productivity
If data query requests are allowed without restriction, then data sharing efficiency is improved, but data security is compromised
Solution Approach 1:
The system performs preliminary security validation by generating a logical plan for the query request and validating it against security policies before executing the query. This advance checking ensures that only security-compliant queries are processed, maintaining data security while allowing efficient execution of authorized requests without runtime restrictions.
Solution Approach 2:
The central node provides feedback by returning query results only after successful security validation. If the logical plan violates security policies, the system rejects the request with appropriate error messages. This feedback mechanism guides data requesters to formulate compliant queries while maintaining efficient processing of valid requests.
3Reliability
If security validation is performed on each data query request, then data security is improved, but query processing time is increased
Solution Approach 1:
The system changes the validation parameter from checking individual data access requests to validating the overall logical plan structure. By analyzing the logical plan's operations and data flow at a higher level, the system performs comprehensive security validation more efficiently than checking each data access point individually, reducing validation time while maintaining security.
Data Source
AI summary
This specification provides example data query methods, apparatuses, and systems for a multi-party secure database. In an example computer-implemented method, a central node receives a data query request from a data requester, where the data query request relates to one or more pieces of target data stored at one or more data providers. The central node determines whether the data query request satisfies respective security requirements of the one or more pieces of target data. In response to determining that the data query request satisfies respective security requirements of the one or more pieces of target data, the central node processes the one or more pieces of target data to obtain result data; and sends the result data to the data requester. The central node can restrict query of the target data by the data requester based on the security requirement of the target data stored at the data provider.