Blockchain Peer Clustering for Seamless Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed ledger peer-to-peer networks, such as blockchain systems, face challenges in maintaining transaction integrity and availability due to node unavailability, leading to stalled transactions when peers fail to approve updates.

Innovation Solution

Implementing a peer-to-peer fabric with clustering configurations that allow peers to execute workload packages, enabling different roles based on blockchain fabric types, such as Hyperledger or Corda, and utilizing package configurations like one-peer, multi-peer, and multi-role setups to ensure continuous operation and failover mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a decentralized peer-to-peer blockchain network is implemented, then transaction integrity and security are improved, but system availability and performance deteriorate when nodes become unavailable

Engineering Contradiction:
Improvetransaction integrityVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments peer availability into multiple independent levels: individual peer availability, cluster availability, and fabric availability. By dividing the peer-to-peer network into autonomous clusters with internal failover mechanisms, the system maintains transaction integrity at the fabric level while ensuring availability at the cluster level, resolving the contradiction between reliability and productivity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the parameter of peer availability from binary (available/unavailable) to a spectrum of availability states through clustering. Peers within a cluster can dynamically assume different roles (primary, backup, standby) based on availability parameters, allowing the system to maintain high availability while preserving transaction integrity through configurable failover thresholds and mechanisms

Inventive Principle:
Principle #35Parameter changes

2Reliability

If strict consensus requirements are enforced for transaction approval, then transaction security is improved, but transaction throughput and speed deteriorate due to node unavailability

Engineering Contradiction:
Improvetransaction securityVSAvoidtransaction throughput
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system performs preliminary actions by pre-configuring backup and standby peers within clusters before failures occur. When a primary peer becomes unavailable, the pre-positioned backup peers can immediately assume their roles without waiting for network-wide consensus, maintaining transaction security through pre-established trust relationships while preserving transaction throughput through rapid failover

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces dynamics to the consensus process by allowing peer roles and availability requirements to change based on current system state. Transaction security is maintained through adaptive consensus thresholds that adjust based on cluster composition and peer availability, enabling the system to maintain security while optimizing throughput under different operational conditions

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If individual peer failures are allowed, then system robustness is improved, but transaction completion deteriorates when peers are unavailable

Engineering Contradiction:
Improvesystem robustnessVSAvoidtransaction completion
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system introduces cluster-level intermediaries that mediate between individual peer failures and fabric-level transaction completion. When individual peers fail, the cluster intermediary (primary peer or backup) maintains the transaction state and coordinates with other clusters to ensure completion, allowing the system to be robust to individual failures while maintaining reliable transaction completion through intermediary coordination

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11496558B2Peer-to-peer blockchain fabric management mechanism
Publication Date: 2022.11.08 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11496558B2 patent drawing
  • US11496558B2 patent drawing
  • US11496558B2 patent drawing

AI summary

A system is described. The system includes a distributed ledger peer-to-peer blockchain fabric comprising a plurality of peer nodes, including a first peer node to receive a workload package, examine the workload package to determine a role of the first peer node within a cluster configuration of a first set of the plurality of peer nodes and execute the workload package at resources included in the first peer node.