Decentralized Database System Using Blockchain Consensus

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases are vulnerable to single points of failure, network dependency, data redundancy issues, and limited access, making them susceptible to data loss and tampering.

Innovation Solution

A decentralized database system utilizing a blockchain network with multiple peer nodes that maintain a shared, immutable ledger, enabling secure data storage and consensus-based transactions to ensure data integrity and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used, then data management is easy and control is centralized, but the system has a single point of failure and is vulnerable to data loss

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

Solution Approach 1:

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

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a consensus mechanism as an intermediary that coordinates actions among decentralized nodes. This mediator ensures that all nodes agree on data integrity and transaction validity, maintaining reliability without centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a centralized database is used, then network connectivity is required for access, but this increases access time and creates bottlenecks

Engineering Contradiction:
Improvedata accessibilityVSAvoidaccess time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the database into multiple distributed nodes that can be accessed independently. Users can query local nodes without requiring centralized network access, reducing access time and eliminating bottlenecks while maintaining data accessibility.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If a centralized database is used, then data redundancy is minimized, but data loss is difficult to retrieve

Engineering Contradiction:
Improvedata redundancyVSAvoiddata recovery capability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent creates multiple copies of the data ledger across decentralized nodes. Each node maintains an identical copy through consensus mechanisms, providing data redundancy that enables automatic recovery without manual intervention if any single node fails.

Inventive Principle:
Principle #26Copying

4Ease of operation

If a centralized database is used, then security control is centralized, but the system is vulnerable to tampering

Engineering Contradiction:
Improvesecurity controlVSAvoidtampering vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments security control across multiple decentralized nodes, each with equal voting power. This distribution prevents any single point of tampering while maintaining security through consensus requirements, making the system resistant to attacks on individual nodes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a consensus mechanism that provides feedback loops among nodes. Any attempted tampering is detected by other nodes through cryptographic verification and consensus validation, preventing successful attacks while maintaining security control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11645376B2Device-based database system
Publication Date: 2023.05.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11645376B2 patent drawing
  • US11645376B2 patent drawing
  • US11645376B2 patent drawing

AI summary

An example operation may include one or more of submitting a part replacement request to replace a first part of a device, qualifying a second part and repair resources, issue a part replacement transaction to the blockchain network, endorse the part replacement transaction by the plurality of blockchain peers, and replace the first part with the second part. The first part includes a blockchain peer of a plurality of blockchain peers and the device includes a blockchain network including a plurality of parts each corresponding to one of the plurality of blockchain peers.