Decentralized Database Fast Path Service for Data Redundancy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, limited data access, and lack of redundancy, leading to potential data loss and management challenges.

Innovation Solution

A blockchain-as-a-service (Baas) provider manages virtual nodes to store and manage data, using a blockchain to ensure data redundancy and accessibility through a decentralized system, where data is stored in a shared storage area and appended to a blockchain without the actual data, allowing for efficient data management and access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used, then data management is easy and security is improved, but the system has a single point of failure and is highly dependent on network connectivity

Engineering Contradiction:
Improvedata management easeVSAvoidsystem reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across different locations. Each node stores a copy of the data, eliminating the single point of failure while maintaining manageable through distributed consensus mechanisms. This segmentation resolves the contradiction by sacrificing centralized control simplicity for improved reliability through distribution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements multiple copies of data across different nodes and locations. Instead of a single centralized copy, data is replicated across the distributed network, ensuring that if one node fails, other nodes can still access the data. This copying approach directly addresses the reliability issue while maintaining ease of access through any node.

Inventive Principle:
Principle #26Copying

2Quantity of substance

If a centralized database is used, then data redundancy is minimized, but data loss occurs when hardware failure happens

Engineering Contradiction:
Improvedata redundancyVSAvoiddata safety
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent divides data storage into segmented copies distributed across multiple nodes. Each node maintains a portion of the data, and the system uses consensus protocols to ensure data integrity. This segmentation enables redundancy without creating a single point of failure, resolving the contradiction between minimal redundancy and data safety.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements beforehand cushioning by pre-distributing data copies across multiple nodes before any failure occurs. The system continuously maintains redundant copies and uses fault-tolerance mechanisms to ensure that if hardware failure happens, data can be retrieved from other nodes. This prior preparation cushions against data loss while maintaining appropriate redundancy levels.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Ease of operation

If a centralized database is used, then access control is simplified, but multiple devices cannot access the same data at the same time

Engineering Contradiction:
Improveaccess control simplicityVSAvoidconcurrent access capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments data access control into distributed authorization mechanisms at each node. Each node independently manages access control for its local copy while maintaining consistency through consensus protocols. This enables multiple devices to access data concurrently through different nodes without conflicts, resolving the contradiction between simple access control and concurrent access capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic access control where authorization can change based on real-time conditions across the distributed network. The system dynamically manages access rights through consensus mechanisms, allowing flexible concurrent access while maintaining security. This dynamic approach resolves the contradiction by adapting access control to multiple simultaneous requests without sacrificing security.

Inventive Principle:
Principle #15Dynamics

4Device complexity

If a centralized database is used, then data storage is consolidated, but network connectivity dependency increases

Engineering Contradiction:
Improvestorage system complexityVSAvoidnetwork dependency
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the centralized storage system into distributed storage nodes. Each node independently stores and manages data locally, reducing dependency on continuous network connectivity for basic data access. The system maintains consistency through periodic synchronization rather than continuous connectivity, resolving the contradiction between storage consolidation and network dependency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary mechanisms such as local caches and asynchronous replication to reduce direct network dependency. These intermediaries allow nodes to operate semi-independently and synchronize data at appropriate intervals, decoupling the storage system from continuous network connectivity while maintaining data consistency. This intermediary approach resolves the contradiction by providing buffer between storage operations and network communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11269858B2Information management in a decentralized database including a fast path service
Publication Date: 2022.03.08 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11269858B2 patent drawing
  • US11269858B2 patent drawing
  • US11269858B2 patent drawing

AI summary

An example operation may include one or more of determining data at a first node satisfies a condition, obtaining a pointer to a shared storage area for the data, controlling generation of a block including the pointer, and appending the block to a blockchain without the data, wherein the first node corresponds to first virtual node hosted by blockchain-as-a-service (Baas) provider and wherein the first virtual node receives the data from a network coupled to the Baas provider.