Multi-version Database with Blockchain Containers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional database management systems lack immutability, security, and scalability, leading to inefficiencies and increased vulnerabilities, particularly in handling sensitive data, and often require ad-hoc solutions that increase complexity and costs.

Innovation Solution

A multi-version database management system utilizing blockchain principles for immutability, security, and authentication, with a relational structure and intuitive interface, providing append-only data storage and fine-grained permissions, and supporting various container types optimized for different data sources and usage patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional database management systems are used, then basic data storage and querying functions are provided, but data integrity and security are compromised

Engineering Contradiction:

Improvedata integrityVSAvoidsystem structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent embeds blockchain technology within the traditional database management system, creating a nested structure where the blockchain layer provides immutability and security while the relational database layer maintains compatibility with existing SQL operations. This allows the system to achieve enhanced data integrity without completely replacing the existing database structure.

Inventive Principle:

Principle #7Nested doll (Nesting)

Solution Approach 2:

The system combines traditional relational database components with blockchain technology to create a hybrid system that leverages the strengths of both approaches. The relational database provides efficient data storage and querying, while the blockchain layer provides immutability, security, and auditability, resulting in a composite system that achieves both performance and reliability.

Inventive Principle:

Principle #40Composite materials

2Adaptability or versatility

If ad-hoc solutions and middleware are built around traditional DBMS, then specific functionality is achieved, but system complexity and development costs increase

Engineering Contradiction:

Improvefunctional capabilityVSAvoidsoftware stack

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal database management system that natively supports multiple functionality including immutability, versioning, audit trails, and security features through its blockchain-integrated architecture. This eliminates the need for multiple separate middleware layers and ad-hoc solutions, as the system provides these capabilities out-of-the-box through a unified structure.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If non-native solutions are implemented, then specific requirements are met, but vulnerabilities and security risks increase

Engineering Contradiction:

Improvefunctional requirementVSAvoidsecurity vulnerabilities

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent employs disposable cryptographic hashes and digital signatures that are computed and verified efficiently, providing security without requiring complex long-term key management systems. The blockchain structure creates immutable records that can be verified without storing sensitive information, reducing the attack surface and security vulnerabilities associated with persistent data storage.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

4Productivity

If conventional database solutions are used, then basic operations are supported, but scalability and performance are limited

Engineering Contradiction:

Improvesystem performanceVSAvoidsystem architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the database system into distinct components: a relational database layer for efficient data storage and querying, and a blockchain layer for immutability and security. This segmentation allows each layer to be optimized independently, with the relational database handling high-performance operations and the blockchain providing scalability through its distributed ledger architecture.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS20220114165A1Multi-version database management system

Publication Date: 2022.04.14 BLOCKPOINT SYSTEMS INC

AI summary

A multi-version database includes user-defined blockchain containers, where each of the user-defined blockchain containers is configured based on a type of data to be stored in a corresponding user-defined blockchain container. Each of the user-defined blockchain containers includes a set of one or more fields defined by a user. A command to write data to the multi-version database is received, where the command includes an identification of a first blockchain container of the user-defined blockchain containers, an identification of at least one of the set of one or more fields of the first blockchain container, and a value to write for at least one field of the set of one or more fields. A record is generated for the first blockchain container, the record including the value to write for the at least one field. A current state of the first blockchain container is then updated to include the record.