Geographic Data Routing with XOR Reconstruction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Geographically distributed data storage systems face performance issues and high failure rates due to slow communication between zones, leading to delayed data read operations and timeouts, especially when using XOR techniques for data replication.

Innovation Solution

The system evaluates and selects the most efficient route to obtain data by potentially reconstructing it from other zones using XOR-based data recovery, rather than directly accessing the owning zone, thereby avoiding slow data read operations and timeouts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is directly read from the owning zone, then data read speed is improved, but system reliability deteriorates due to network issues between zones

Engineering Contradiction:
Improvedata read speedVSAvoidread operation reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent introduces an intermediary routing mechanism that selects between direct reading from the owning zone and indirect reading through alternative zones. When direct communication between zones is detected as slow or unreliable, the system routes read requests through intermediate zones that have cached copies of the data, thereby maintaining high read speed while improving reliability by avoiding problematic direct zone communications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If XOR replication is used across multiple zones, then data protection is improved, but data read performance deteriorates due to slow inter-zone communication

Engineering Contradiction:
Improvedata protectionVSAvoiddata read performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-caching data blocks in multiple zones through asynchronous replication before read requests arrive. This allows the system to maintain XOR-based data protection across zones while improving read performance, as cached copies are already available locally or in nearby zones, eliminating the need for slow real-time inter-zone communications during read operations.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If data is replicated across geographically distributed zones, then data availability is improved, but read operation time increases due to network latency

Engineering Contradiction:
Improvedata availabilityVSAvoidread operation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies local quality by enabling zones to serve read requests from their own local caches when available, rather than always fetching data from remote owning zones. The routing system evaluates local cache availability and prioritizes local reads, significantly reducing read operation time while maintaining data availability through the distributed XOR-replicated architecture.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11112978B2Routing to obtain user data in a geographically distributed data storage environment
Publication Date: 2021.09.07 EMC IP HLDG CO LLC
  • US11112978B2 patent drawing
  • US11112978B2 patent drawing
  • US11112978B2 patent drawing

AI summary

The described technology is generally directed towards obtaining data, such as corresponding to a read request, from a geographic zone which may not be the zone that owns the data. When a request for data (e.g., a data segment) is received by a zone that does not own the requested data, the zone evaluates statistical data to determine whether it is more efficient to obtain the requested data directly from the zone that owns the data, or indirectly from one or more zones that contain related data from which the requested data can be reconstructed. If the indirect route is deemed sufficiently more efficient, the reconstruction data (e.g., counterpart segments) are obtained, and processed into the requested data, e.g., by XOR-ing the counterpart data segments into the requested data segment for returning to the client.