Transaction Manager for Blockchain Two-Phase Commit Recovery

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 access, and inefficiencies in transaction management, particularly with the lack of support for two-phase commit protocols in blockchain systems.

Innovation Solution

A system and method for managing a blockchain resource in a fully recoverable two-phase commit transaction, where a transaction manager connects to a blockchain, performs transactions on two-phase commit capable resources, writes data to a recovery log, and commits transactions while enabling automatic recovery from unknown outcomes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized database is used to store and maintain data at one location, then data redundancy is minimized and security control is simplified, but the system has a single point of failure and limited access capability

Engineering Contradiction:
Improvedata security controlVSAvoidaccess capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across a network. Each node maintains copies of the data, transforming a single-location storage system into a multi-location distributed system. This segmentation enables multiple users to access data simultaneously from different locations while maintaining security through distributed consensus mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates multiple copies of the data and distributes them across different nodes in the network. Instead of maintaining a single primary record, the system replicates data across multiple locations, allowing simultaneous access while preserving data integrity through consensus validation at each node.

Inventive Principle:
Principle #26Copying

2Ease of operation

If a centralized database stores all data at one location, then management and control are simplified, but the system becomes highly dependent on network connectivity and experiences bottlenecks during high traffic

Engineering Contradiction:
Improvedatabase managementVSAvoidtransaction speed
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent divides the centralized database management function into multiple autonomous nodes that operate independently. Each node can process transactions locally without requiring constant communication with a central authority, reducing network dependency and eliminating bottlenecks during high traffic periods.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a dynamic distributed architecture where nodes can join and leave the network flexibly. The system adapts to varying traffic loads by distributing transaction processing across available nodes, maintaining ease of operation through automated consensus while improving transaction speed through parallel processing.

Inventive Principle:
Principle #15Dynamics

3Reliability

If a centralized database maintains a single copy of data, then data redundancy is minimized, but data loss is difficult to retrieve and requires manual intervention from back-up storage

Engineering Contradiction:
Improvedata integrityVSAvoiddata recovery
Core Design Contradiction:
ReliabilityVSEase of repair

Solution Approach 1:

The patent creates multiple redundant copies of data distributed across different nodes in the network. If data is lost or corrupted at one node, identical copies exist at other nodes, enabling automatic recovery without manual intervention. The distributed consensus mechanism ensures data integrity is maintained across all copies.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent implements automatic data recovery mechanisms where lost or corrupted data can be retrieved from other nodes in the distributed network. The system automatically detects data loss, retrieves copies from alternative nodes, and restores integrity without requiring manual backup operations.

Inventive Principle:
Principle #34Discarding and recovering

4Reliability

If blockchain does not support two-phase commit protocol, then transaction coordination with external resources cannot be guaranteed, but implementing it manually is highly disruptive and error-prone

Engineering Contradiction:
Improvetransaction coordinationVSAvoidrecovery mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a transaction manager as an intermediary layer between the blockchain and external two-phase commit capable resources. This mediator coordinates transactions by maintaining a recovery log that records the state of all resources, enabling automatic two-phase commit semantics without modifying the blockchain protocol itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary actions by writing transaction state information to a recovery log before committing transactions to the blockchain. This preliminary recording enables automatic recovery and coordination with external resources, ensuring transaction reliability while keeping the blockchain protocol simple and unchanged.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10936445B2Resource management
Publication Date: 2021.03.02 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10936445B2 patent drawing
  • US10936445B2 patent drawing
  • US10936445B2 patent drawing

AI summary

An example operation may include one or more of connecting, by a transaction manager node, to a blockchain configured to store transaction data, receiving, by the transaction manager node, a transaction from a user node, the transaction includes a transactional operation, performing, by the transaction manager node, the transactional operation on an at least one two-phase commit capable resource, writing, by the transaction manager node, the transaction data into a recovery log, committing, by the transaction manager node, the transaction to the blockchain, and in response to an unknown outcome of the commit of the transaction, executing a recovery operation.