Native Application Database Roles for Secure Data Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data sharing methods are cumbersome, slow, and expensive, particularly for smaller entities, as they require data copying and transfer, which is time-consuming and insecure, and do not allow scalable sharing or real-time access to updated data.
Innovation Solution
A data exchange platform that enables secure, scalable sharing of data through cloud computing services, allowing data providers to create share objects that grant controlled access to specific database objects, enabling secure joins and analysis without data copying, and allowing native applications to be shared and installed by consumers for data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is copied and transferred using traditional methods, then data sharing is achieved, but the process becomes slow and expensive
Solution Approach 1:
The patent creates a shared database that is a copy of the original database, allowing multiple users to access and query data simultaneously without copying physical data files. This virtual copy approach enables fast data sharing while avoiding the time-consuming process of physically copying and transferring large datasets.
Solution Approach 2:
The patent introduces a shared database as an intermediary between the original data source and end users. This intermediary layer allows real-time data access and sharing without requiring direct data transfer between systems, significantly reducing transfer time and improving productivity.
2Reliability
If data is encrypted and stored securely, then security is improved, but data sharing capability deteriorates
Solution Approach 1:
The patent creates an encrypted copy of the database that maintains security while enabling sharing. The shared database contains encrypted data that can be accessed by multiple users with appropriate permissions, preserving security (reliability) while enabling broad access (adaptability).
Solution Approach 2:
The shared database is designed to serve multiple functions simultaneously: it maintains security through encryption, enables multi-user access, supports various query operations, and allows controlled data sharing. This multi-functional design resolves the contradiction between security and sharing capability.
3Adaptability or versatility
If data is shared with multiple parties, then data sharing scalability is improved, but access control complexity increases
Solution Approach 1:
The patent implements a universal access control system that handles multiple users and permissions through a single shared database structure. This universal approach allows scalable sharing with many parties while maintaining consistent, manageable access control rules, preventing complexity from increasing linearly with the number of users.
Solution Approach 2:
The patent segments access control into discrete permissions that can be independently granted and managed for different users. This segmentation allows fine-grained control over who can access what data, enabling scalable sharing while keeping access control complexity manageable through modular permission management.
4Productivity
If data is transferred to third parties for processing, then data processing capability is improved, but data security deteriorates
Solution Approach 1:
The patent uses the shared database as an intermediary that enables third parties to process data without directly receiving or transferring the actual data. Users can query and analyze data through the shared database while the original data remains secure in the encrypted copy, improving processing capability while maintaining security.
Solution Approach 2:
The patent creates an encrypted copy of the database that third parties can access for processing purposes. This copy contains the necessary data for analysis and processing while the original sensitive data remains protected, enabling data processing capability improvement without compromising security.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
Embodiments of the present disclosure enable users of a data sharing system to build native applications that can be shared with other users of the data sharing system. The native applications can be published and discovered in the data sharing system like any other data listing, and consumers can install them in their local data sharing system account to serve their data processing needs. A provider may define an installation script for installing an application and create a share object to which the installation script may be attached. In response to an imported database being created in a consumer account based on the share object, a native application framework may automatically execute the installation script in the consumer account and may create a set of database roles to manage execution of the application in the consumer account.