Datacenter Data Synchronization Using Hierarchical Change Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Entity servers face challenges in synchronizing data across multiple data centers, with issues in adaptability, efficiency, and security in dynamic computing environments, and latency in dynamic computing environments, leading to inefficiencies and latency in data synchronization across the data centers.

Innovation Solution

The system uses artificial intelligence to identify and patterns in the hierarchical structures, and security in dynamic computing environments, and latency in data synchronization across multiple data centers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is replicated across multiple datacenters, then data availability is improved, but data consistency deteriorates due to synchronization latency

Engineering Contradiction:
Improvedata availabilityVSAvoiddata consistency
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The patent segments the data synchronization process into multiple independent components: change detection mechanisms that identify modified data blocks, selective replication that transmits only changed portions, and verification protocols that ensure consistency. This segmentation allows parallel processing across datacenters while maintaining data integrity, resolving the contradiction between availability and consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by establishing synchronization protocols and change detection mechanisms before data modifications occur. Version control systems and checksum verification are pre-configured to automatically detect and resolve inconsistencies, ensuring data consistency is maintained proactively rather than reactively, thus preventing synchronization issues before they affect availability.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If real-time data replication is implemented across multiple datacenters, then data accuracy is improved, but system latency increases

Engineering Contradiction:
Improvedata accuracyVSAvoidsynchronization latency
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies local quality by implementing region-specific caching mechanisms and edge replication strategies. Frequently accessed data is replicated to local caches at each datacenter, reducing the need for continuous real-time synchronization across all nodes. This localized approach maintains high data accuracy for critical operations while significantly reducing synchronization latency for non-critical updates.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements periodic action through scheduled synchronization intervals and batch processing mechanisms. Instead of continuous real-time replication, data changes are collected and synchronized in periodic batches at optimized intervals. This approach maintains sufficient data accuracy for most operations while dramatically reducing the overall synchronization latency and network overhead compared to continuous real-time replication.

Inventive Principle:
Principle #19Periodic action

3Stability of the object's composition

If comprehensive data synchronization protocols are implemented, then data consistency is improved, but system complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent uses copying mechanisms to simplify the synchronization protocol. Instead of implementing complex real-time comparison and conflict resolution algorithms, the system creates simplified copies of data change metadata (such as checksums, version identifiers, and timestamps) that can be easily exchanged and verified between datacenters. This copying approach maintains data consistency through simple verification protocols while avoiding the complexity of full data comparison and conflict resolution mechanisms.

Inventive Principle:
Principle #26Copying

4Measurement precision

If frequent data synchronization is performed, then data accuracy is improved, but computational efficiency deteriorates

Engineering Contradiction:
Improvedata accuracyVSAvoidcomputational efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent implements partial action by synchronizing only the necessary portion of data rather than performing comprehensive frequent synchronization of all data. Change detection algorithms identify and transmit only modified data blocks, and selective replication applies synchronization only to affected regions. This partial synchronization approach maintains sufficient data accuracy while dramatically reducing computational overhead and improving overall system efficiency compared to frequent full-data synchronization.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20250390504A1System and Method for Synchronizing Data Across a Plurality of Datacenters
Publication Date: 2025.12.25 BANK OF AMERICA CORP
  • US20250390504A1 patent drawing
  • US20250390504A1 patent drawing

AI summary

A method is provided that includes generating a first image of first memory blocks stored in a first database that includes a first hierarchical structure, and generating a second image of second memory blocks stored in a second database that includes a second hierarchical structure. The method includes processing the first and second images to identify a visual change between the first and second hierarchical structures. The method includes determining whether the first and second hierarchical structures are desynchronized based on the visual change. In response to determining that the first and second hierarchical structures are desynchronized, the method includes synchronizing a first set of user data in the first memory blocks with a second set of user data in the second memory blocks.