Co-ownership Database System with Rule-Based Access Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud databases struggle to manage co-ownership among multiple members for data sharing, as traditional blockchain systems are inefficient in data migration and execution, failing to support multi-user shared database systems effectively.

Innovation Solution

A co-ownership database system is implemented, comprising an underlying database, a rule set defining member permissions, and a blockchain for storing operation history, where accessing requests are verified against the rule set to ensure secure and efficient data sharing among multiple members.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional blockchain systems are used for co-ownership database management, then data sharing among multiple members is enabled, but execution efficiency and data migration capability deteriorate

Engineering Contradiction:
Improveco-ownership data sharing capabilityVSAvoidexecution efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the database system into multiple independent nodes, each capable of autonomous operation and data storage. This segmentation allows the system to maintain blockchain's decentralized co-ownership capability while improving execution efficiency through parallel processing across nodes, directly resolving the contradiction between adaptability and productivity

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If traditional blockchain systems are used for co-ownership database management, then data sharing among multiple members is enabled, but data migration capability deteriorates

Engineering Contradiction:
Improveco-ownership data sharing capabilityVSAvoiddata migration capability
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements a universal node architecture where each database node can perform multiple functions including data storage, computation, and seamless migration. This multi-functionality enables easy data migration between nodes while maintaining co-ownership capabilities, resolving the contradiction between adaptability and ease of manufacture

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If existing cloud databases are used, then single-owner data management is achieved, but multi-member data sharing capability deteriorates

Engineering Contradiction:
Improvesingle-owner data managementVSAvoidmulti-member data sharing capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent transforms the static single-owner database model into a dynamic multi-owner system where ownership and permissions can be flexibly assigned and modified. The rule set dynamically adjusts access control based on member roles and operations, enabling both easy single-owner management and versatile multi-member sharing

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3607471B1Management of co-ownership database system
Publication Date: 2024.05.08 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3607471B1 patent drawingFigure 1
  • EP3607471B1 patent drawingFigure 2
  • EP3607471B1 patent drawingFigure 3

AI summary

In implementations of the present disclosure, a solution for managing a co-ownership database system is provided. In this solution, multiple members access the database system as the co-owner thereof. The database system comprises: an underlying database for storing data of multiple members of the database system, a rule set defining constraints on operations of the multiple members over the database system, and a blockchain storing a record of an operation history of the database system. The database system is co-owned by the multiple members. In response to receiving a data accessing request from one of members, the accessing request will be verified based on the rule set. Subsequently, the accessing request will be processed according to a result of the verification.