Blockchain Data Synchronization via Selective Block Height Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In blockchain networks, when a service node pulls block data from other nodes, if some data is missing, it needs to resynchronize all block data, leading to low efficiency due to the large volume of data involved.
Innovation Solution
A method where a service node acquires target block data with a minimum block height greater than its local block height, determines the block height of missing data, and requests the target service node to synchronize only the missing data based on this height, rather than resynchronizing all data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a service node resynchronizes all block data when some data is missing, then data completeness is ensured, but synchronization efficiency deteriorates due to large data volume
Solution Approach 1:
The patent segments the block data synchronization process into two distinct phases: (1) continuous pulling of new block data by comparing local maximum block height with target service node's block height to acquire target block data, and (2) selective synchronization of missing block data by determining the specific block height range that is missing. This segmentation allows the system to maintain data completeness while avoiding unnecessary resynchronization of already拥有的 data, thereby resolving the contradiction between reliability and synchronization efficiency.
Solution Approach 2:
Instead of performing a complete resynchronization of all block data when missing data is detected, the patent applies partial action by identifying and synchronizing only the specific missing block data within the determined block height range. This partial synchronization approach ensures data completeness is restored while minimizing the data volume that needs to be transferred, thus improving synchronization efficiency without compromising reliability.
2Reliability
If a service node pulls all block data from target service node, then data completeness is maintained, but time consumption increases due to continuous full data transfer
Solution Approach 1:
The patent implements preliminary action by continuously monitoring and comparing the local maximum block height with the target service node's block height before initiating data synchronization. This preliminary comparison allows the system to identify the exact block height range of missing data in advance, so that when synchronization is needed, only the necessary data is transferred. This prevents unnecessary time consumption while ensuring data completeness is maintained.
Solution Approach 2:
The patent changes the synchronization parameter from a fixed full-data-transfer mode to a dynamic range-based mode. By determining the missing block height range through parameter comparison (local maximum block height vs. target node's block height), the system adapts the synchronization scope to match the actual data needs, reducing time consumption while maintaining data completeness.
3Measurement precision
If a service node continuously monitors block height for synchronization, then synchronization accuracy is improved, but system complexity increases
Solution Approach 1:
The patent makes the block height comparison mechanism universal by using the same comparison logic for both continuous pulling of new block data and identification of missing data. The maximum block height parameter serves multiple functions: it tracks the latest synchronized block, enables detection of missing data ranges, and guides both continuous pulling and selective synchronization operations. This multi-functionality improves synchronization accuracy without proportionally increasing system complexity.
Data Source
AI summary
A blockchain-based data synchronization method, executed by a first service node, includes: acquiring target block data having a minimum block height that is greater than a first local block height, the first local block height being a maximum block height of local block data of the first service node before the first service node acquires the target block data; determining a block height of missing block data according to a block height of the target block data and the first local block height, the block height of the missing block data being less than the minimum block height of the target block data and greater than the first local block height; and requesting a target service node to synchronize the missing block data according to the block height of the missing block data.