Data Replication Path Latency Measurement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Synchronous data replication between data centers is vulnerable to transmission latency issues, leading to performance limitations and increased vulnerability to attacks, as it requires waiting for acknowledgement from the secondary data center, which can cause replication failures if backup pathways have excessive latency.

Innovation Solution

A method that determines the latency of data replication paths by transmitting test data and measuring latency parameters, allowing for the selection of suitable paths for synchronous replication or switching to pseudo-synchronous replication if latency thresholds are exceeded, ensuring continuous data integrity and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous replication is used to guarantee data integrity, then data reliability is improved, but transmission latency increases and system performance deteriorates

Engineering Contradiction:
Improvedata integrityVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically adjusts the replication mode between synchronous and asynchronous based on real-time latency measurements. When latency is below a threshold, synchronous replication is used for maximum reliability; when latency exceeds the threshold, the system switches to asynchronous replication or alternative paths, thereby adapting to changing network conditions and avoiding performance degradation.

Inventive Principle:
Principle #15Dynamics

2Stability of the object's composition

If synchronous replication is used between distant data centers, then data consistency is maintained, but the system becomes vulnerable to attacks and replication failures occur

Engineering Contradiction:
Improvedata consistencyVSAvoidvulnerability to attacks
Core Design Contradiction:
Stability of the object's compositionVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary latency measurements and path assessments before initiating data replication. By measuring latency in advance and selecting optimal paths, the system prevents replication failures caused by high-latency paths and reduces vulnerability to attacks on specific network routes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the replication parameter (synchronous vs. asynchronous mode) based on measured latency parameters. When the measured latency exceeds a predetermined threshold, the system switches from synchronous to asynchronous replication or selects alternative paths, thereby adapting to network conditions and reducing vulnerability to attacks while maintaining data consistency where possible.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the server waits for acknowledgement from the secondary data center, then data integrity is ensured, but application performance decreases

Engineering Contradiction:
Improvedata integrityVSAvoidapplication performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically determines whether to wait for acknowledgements based on real-time latency measurements. When latency is low, the system waits for acknowledgements to ensure integrity; when latency is high, the system may proceed without waiting or use alternative paths, thereby maintaining application performance while preserving data integrity when conditions allow.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11314772B2Robust data replication among data centers
Publication Date: 2022.04.26 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US11314772B2 patent drawing
  • US11314772B2 patent drawing
  • US11314772B2 patent drawing

AI summary

A method of data replication between a first data center and a second data center, wherein the first data center has a data set to be replicated, the method comprising: determining (501) whether a first path from the first data center to the second data center is suitable for the data set to be replicated, by: transmitting (502) test data along the first path, taking (503) latency measurements for the test data along the first path; and determining a latency parameter of the first path using the latency measurements; and determining (504) if the latency parameter of the test data is less than a maximum latency threshold. If the latency parameter is less than the maximum latency threshold, the method performs (505) replication of the data set using the first path.