Phased Asset Replication Prioritizing Data Center Cost Parameters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Replicating large software assets across multiple data centers is costly due to bandwidth usage and resource processing requirements, with existing methods lacking efficient prioritization strategies to optimize the replication process.

Innovation Solution

Estimate cost parameters such as geographical distance, channel bandwidth, and utilization ratio to determine replication priority, allowing for phased replication that prioritizes remotely located target clusters initially, thereby optimizing resource utilization and reducing system overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software assets are replicated across multiple data centers, then accessibility and availability are improved, but bandwidth consumption and processing resources increase

Engineering Contradiction:
ImproveaccessibilityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the replication process into multiple phases (e.g., phase 1, phase 2, phase 3) where different subsets of target data centers receive replicated assets in each phase. This allows the system to distribute replication operations over time, reducing peak bandwidth consumption while ultimately achieving widespread availability across all data centers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by determining replication priorities and cost parameters before actual replication begins. It calculates geographic distances, estimates bandwidth costs, and establishes replication phases in advance, allowing for optimized resource allocation that reduces overall bandwidth consumption while maintaining accessibility.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If replication is performed to all target data centers simultaneously, then accessibility is improved, but system capacity is overwhelmed

Engineering Contradiction:
ImproveavailabilityVSAvoidsystem overload
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the target data centers into different groups or phases for sequential replication. Instead of replicating to all targets simultaneously, it processes them in manageable batches (e.g., Phase 1 targets, Phase 2 targets), which prevents system overload while progressively improving availability across the distributed system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts replication operations based on system capacity and priority levels. It monitors processing loads and adapts the replication schedule, allowing the system to handle replication tasks flexibly without being overwhelmed, while still achieving comprehensive availability over time.

Inventive Principle:
Principle #15Dynamics

3Loss of energy

If replication priority is determined by geographical distance, then bandwidth cost is reduced, but remotely located clusters may be delayed

Engineering Contradiction:
Improvebandwidth costVSAvoidreplication delay
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system performs preliminary actions by calculating geographic distances and determining replication priorities before execution. It identifies remotely located data centers in advance and schedules them for specific phases, ensuring that while they may be replicated later, the delay is planned and managed rather than arbitrary, balancing bandwidth cost optimization with acceptable service levels.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of replication timing based on geographic parameters. It adjusts the replication schedule according to distance-based cost parameters, replicating to closer data centers first and remotely located ones in later phases, thereby optimizing bandwidth cost while managing replication delay through parameter-driven scheduling.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9298790B2Replication of assets across data centers
Publication Date: 2016.03.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9298790B2 patent drawing
  • US9298790B2 patent drawing
  • US9298790B2 patent drawing

AI summary

The replication of an asset from a source cluster in a source data center to multiple target clusters in multiple destination data centers. The replication occurs by first estimating or determining a cost parameter associated with copying of the asset from the source cluster to each of at least some of the target clusters. As an example, the cost parameter might be a geographical parameter, but might also be any cost parameter such as a channel bandwidth, channel cost, utilization ratio or the like. Based on the cost parameters, an order of replication priority is determined. Then, the replication is initiated in accordance with the prioritization. The replication may occur in multiple phases, and replication prioritization may occur on a per phase basis.