Blockchain Consensus Node Synchronization via Section Snapshots

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain consensus technologies face challenges in synchronizing information about nodes that are frequently connected to and disconnected from the network, leading to inconsistencies and potential consensus disruptions.

Innovation Solution

An apparatus and method for synchronizing consensus node information in a blockchain network, which involves receiving committed messages, verifying nodes, broadcasting consensus node information, and using snapshots with hash values to ensure node synchronization, while considering propagation delay and nonce chain generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If nodes are dynamically connected to and disconnected from the blockchain network, then network flexibility and node mobility are improved, but node information synchronization deteriorates leading to consensus inconsistencies

Engineering Contradiction:
Improvenode mobilityVSAvoidconsensus consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing section boundaries in advance and pre-defining synchronization checkpoints at section transitions. When a node joins or leaves the network, the system has already prepared the section structure and synchronization mechanisms, allowing the node to quickly synchronize by retrieving information from the appropriate section start block without disrupting ongoing consensus operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces section start blocks as intermediary elements that mediate between dynamic node changes and consensus consistency requirements. These special blocks contain synchronized node information snapshots that act as reference points, allowing dynamically joining or leaving nodes to obtain authoritative node lists without requiring continuous real-time synchronization with all other nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If real-time synchronization of consensus node information is implemented, then consensus consistency is improved, but network overhead and communication costs increase

Engineering Contradiction:
Improvenode information synchronizationVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The blockchain is divided into sections with designated section start blocks that serve as synchronization checkpoints. Instead of continuously synchronizing node information across all blocks, the system segments the synchronization task to occur only at section boundaries. This reduces network overhead by limiting full node information exchanges to periodic intervals rather than continuous real-time communication.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements periodic synchronization at section start blocks rather than continuous real-time synchronization. Nodes update their consensus node information periodically when encountering section start blocks, which reduces network traffic and computational overhead compared to maintaining constant synchronization. The periodic interval is determined by the section size, allowing optimization between synchronization freshness and network efficiency.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS12184801B2Apparatus and method for synchronizing consensus node information in blockchain network
Publication Date: 2024.12.31 ELECTRONICS & TELECOMM RES INST
  • US12184801B2 patent drawing
  • US12184801B2 patent drawing
  • US12184801B2 patent drawing

AI summary

Disclosed herein are an apparatus and method for apparatus for synchronizing consensus node information in a blockchain network. The apparatus for synchronizing consensus node information includes one or more processors, and execution memory for storing at least one program that is executed by the one or more processors, wherein the at least one program is configured to receive a committed message for block consensus from the blockchain network and verify nodes participating in the block consensus, set a block number required to participate in the block consensus to a block size of a start block of a section corresponding to the block consensus, and broadcast consensus node information including the block number to the blockchain network.