Secure Multi-Party Database Query Coordination via Central Node Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing secure multi-party databases face limitations in extensibility, requiring all service providers to contribute to the central node and using the same privacy algorithms, which restricts their ability to expand and adapt to diverse data management needs.
Innovation Solution
A secure multi-party database architecture with a central node and multiple databases, where each database has a second interface for interacting with the central node's first interface, allowing databases to join and communicate using specific privacy algorithms, and a metadata system for grouping databases by privacy algorithms, enabling flexible query execution across different databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all service providers contribute to the central node and use the same privacy algorithms, then security and consistency are improved, but extensibility and adaptability deteriorate
Solution Approach 1:
The system segments the database architecture into independent participant databases that each maintain their own privacy algorithms and data, interacting through a standardized interface at the central node. This allows each participant to operate independently with their chosen algorithms while maintaining system-wide security through the standardized interaction protocol.
Solution Approach 2:
The central node implements a universal standardized interface that can interact with multiple different privacy algorithms and database types. This universal interface allows the system to accommodate diverse participants with different technical requirements while maintaining consistent security standards across all interactions.
2Stability of the object's composition
If a single service provider provides the central node and all databases, then system control and consistency are improved, but adaptability to diverse data management needs deteriorates
Solution Approach 1:
Each participant database is allowed to have local quality in terms of choosing their own privacy algorithms and data management approaches suitable for their specific needs, while the central node provides the standardized interface that ensures overall system consistency. This local autonomy within a standardized framework enables both diversity and coherence.
Solution Approach 2:
The central node acts as an intermediary that mediates between participants with diverse requirements and the need for system-wide consistency. It receives queries from users, determines which participant databases are relevant, and coordinates the query execution across different algorithms and systems while maintaining a unified interface for users.
3Productivity
If databases are grouped by privacy algorithms with metadata management, then query efficiency is improved, but system complexity increases
Solution Approach 1:
The system performs preliminary action by pre-grouping participant databases according to their privacy algorithms and maintaining metadata that describes these groupings. This pre-organization allows the central node to efficiently route queries to appropriate database groups without requiring complex real-time analysis, thereby improving query efficiency while managing complexity through advance preparation.
Data Source
AI summary
This specification provides a multi-party database including a central node and a plurality of databases. The central node has a disclosed first interface. Each of a plurality of query engines corresponding to the plurality of databases includes a second interface configured to interact with the first interface. The central node can determine a plurality of target databases related to a query request from the plurality of databases based on the query request; and send a query indication to a plurality of target query engines corresponding to the plurality of target databases through the first interface. The plurality of target query engines can receive the query indication from second interfaces in the plurality of target query engines, and execute the query indication to obtain a query result; and send the query result to the first interface in the central node through the second interfaces.