CDN Origin Server Relocation for Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks (CDNs) face high latency in serving content, particularly for first-time requests, as existing solutions primarily focus on caching for subsequent requests, neglecting the latency associated with initial content delivery.

Innovation Solution

A CDN service provider monitors historical request data to recommend and migrate the origin server from a first geographic region to a second region closer to the majority of request sources, using techniques like data clustering to determine optimal edge locations for reducing round-trip time (RTT) for requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If the origin server remains at the first geographic location, then existing content delivery mechanisms are maintained, but the round-trip time for content requests increases due to distance from request sources

Engineering Contradiction:
Improveround-trip timeVSAvoidsystem configuration complexity
Core Design Contradiction:
Loss of timeVSEase of manufacture

Solution Approach 1:

The patent implements dynamic origin server relocation by continuously monitoring the geographic distribution of content requests and automatically migrating the origin server to optimal locations. This dynamic adaptation allows the system to respond to changing request patterns, reducing round-trip time without requiring manual reconfiguration of the entire CDN infrastructure.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces a CDN service provider as an intermediary that manages the origin server migration on behalf of content providers. This intermediary handles the complexity of geographic distribution analysis, request pattern monitoring, and server relocation, simplifying the system configuration for content providers while achieving reduced latency through optimized server positioning.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If caching is used for subsequent requests, then delivery speed for repeated content is improved, but first-time request latency remains high due to origin server distance

Engineering Contradiction:
Improvecontent delivery speedVSAvoidfirst-time request latency
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent applies preliminary action by proactively migrating the origin server to locations closer to request sources before content delivery demands increase. By analyzing historical request data and predicting future request patterns, the system positions the origin server in advance, ensuring that both first-time and subsequent requests benefit from reduced latency without relying solely on caching mechanisms.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If the origin server is migrated to follow request distribution, then round-trip time is reduced, but system adaptability requirements increase

Engineering Contradiction:
Improverequest latencyVSAvoidsystem adaptability
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The patent implements feedback mechanisms by continuously monitoring the geographic distribution of content requests and using this information to guide origin server migration decisions. The system analyzes request patterns, determines optimal server locations, executes migrations, and then evaluates the impact on latency, creating a closed-loop control system that adapts to changing conditions while maintaining manageable system complexity through automated decision-making.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10735528B1Geographic relocation of content source in a content delivery network
Publication Date: 2020.08.04 AMAZON TECH INC
  • US10735528B1 patent drawing
  • US10735528B1 patent drawing
  • US10735528B1 patent drawing

AI summary

A Content Delivery Network (CDN) service provider is described that monitors historical data of a geographic distribution of requests and makes source relocation recommendations based on the historical data. Based on a selected recommendation, the CDN service provider can migrate the source of content from a first geographical region to a second geographical region closer to where the requests are generated. As a result, a round-trip time (RTT) for requests is reduced, even for first time requests.