Baas Provider Fast Path Service Decentralized Data Management

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 blockchain technology 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 data is stored in a centralized database, then data management and control are simplified, but the system has a single point of failure and limited data accessibility

Engineering Contradiction:
Improvedata managementVSAvoidfault tolerance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple decentralized nodes distributed across different locations. Each node maintains a copy of the data, eliminating the single point of failure while preserving management capabilities through coordinated consensus mechanisms among nodes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a mediator layer that coordinates data operations across decentralized nodes. This mediator enables simplified management and control while maintaining the distributed architecture, allowing nodes to collaborate without direct peer-to-peer complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is replicated across multiple nodes, then data accessibility and redundancy are improved, but network dependency and complexity increase

Engineering Contradiction:
Improvedata redundancyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates simplified copies of data across nodes rather than full replicas. Each node stores essential data copies with standardized formats, reducing the complexity of synchronization and management while maintaining redundancy and accessibility benefits.

Inventive Principle:
Principle #26Copying

3Reliability

If all data is stored in the blockchain, then data integrity is ensured, but storage efficiency decreases and access speed slows

Engineering Contradiction:
Improvedata integrityVSAvoiddata access speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts large data payloads from the blockchain structure and stores them in external decentralized storage systems. Only essential metadata, hashes, and critical information remain in the blockchain, preserving data integrity verification while dramatically improving access speed and storage efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent moves data storage from a single-dimensional blockchain structure to a multi-dimensional architecture where data resides in external storage layers while the blockchain maintains a verification layer. This dimensional separation enables both integrity assurance and fast access.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11418322B2Information management in a decentralized database including a fast path service
Publication Date: 2022.08.16 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11418322B2 patent drawing
  • US11418322B2 patent drawing
  • US11418322B2 patent drawing

AI summary

An example operation may include one or more receiving an entry at a blockchain-as-a-service (Baas) provider, determining whether the entry satisfies a first set of policies, and controlling placement of the entry into a first queue when the first set of policies is satisfied and into a second queue when the first set of policies is not satisfied, wherein the first queue is to store confirmed entries to be submitted for consensus without validation and the second queue is to store pending entries that require validation before consensus.