Class-Based CDN Request Routing for Lower Network Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content providers and CDN service providers face challenges in efficiently managing and processing resource requests from client computing devices, which can strain their computing resources due to the high volume of requests and the inclusion of multiple components, while considering factors like latency and cost.

Innovation Solution

A content delivery network (CDN) service provider implements a request routing system that determines a class for client computing devices based on geographic region or ISP, using DNS servers to select appropriate resource cache components or alternative DNS servers through CNAME records, optimizing routing based on class information and network performance metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all content requests are routed to the origin server, then content accuracy is maintained, but network latency increases and origin server load increases

Engineering Contradiction:
Improvecontent accuracyVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces CDN edge servers as intermediary nodes between clients and origin servers. These edge servers cache content and serve requests locally, acting as mediators that reduce the distance data must travel while maintaining content accuracy through synchronization mechanisms with origin servers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the content delivery function by separating origin servers (which maintain authoritative content) from edge servers (which serve cached content). This segmentation allows requests to be handled locally at edge servers while origin servers remain available for content updates and verification.

Inventive Principle:
Principle #1Segmentation

2Loss of time

If content is cached at edge servers, then network latency is reduced, but content freshness may deteriorate

Engineering Contradiction:
Improvenetwork latencyVSAvoidcontent freshness
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where edge servers monitor content freshness and automatically synchronize with origin servers when content changes are detected. This feedback loop ensures cached content remains fresh without requiring constant client-server communication.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent uses preliminary actions by pre-caching content at edge servers before client requests arrive. This allows edge servers to serve content from local cache rather than fetching from origin servers, reducing latency while maintaining freshness through periodic updates.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If class-based routing is implemented, then resource distribution is optimized, but DNS system complexity increases

Engineering Contradiction:
Improveresource distribution efficiencyVSAvoidDNS system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent changes the routing parameter from traditional IP-based or domain-based routing to class-based routing, where clients are assigned to classes based on characteristics like geography, device type, or service level. This parameter change enables more efficient resource distribution while the DNS system handles the complexity transparently.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12452205B2Request routing based on class
Publication Date: 2025.10.21 AMAZON TECH INC
  • US12452205B2 patent drawing
  • US12452205B2 patent drawing
  • US12452205B2 patent drawing

AI summary

A system and method for management and processing of resource requests is provided. A content delivery network service provider receives a DNS query from a client computing device. The DNS query corresponds to a requested resource from the client computing device. The content delivery network service provider associates the client computing device with a cluster of other client computing devices. Based on routing information for the cluster, the content delivery network service provider routes the DNS query. The process can further include monitoring performance data associated with the delivery of the requested resource and updating the routing information for the cluster based on the performance data for use in processing subsequent requests from client computing devices in the cluster.