DNS Request Routing Optimization via Performance Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content providers and CDN service providers face challenges in efficiently managing resource requests and optimizing content delivery due to high volumes of requests and additional resource components, which strain computing resources and increase latency, necessitating improved request routing strategies.

Innovation Solution

Implementing a system where a service provider, such as a CDN or DNS service provider, processes DNS requests, correlates performance information, and generates prioritized request routing information to optimize resource requests and reduce latency by identifying the best network addresses for resource delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If content providers serve high volumes of client requests directly, then content delivery capacity increases, but computing resource strain increases and latency increases

Engineering Contradiction:
Improvecontent delivery capacityVSAvoidlatency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the content delivery system into multiple distributed edge servers located geographically close to client devices. These edge servers cache and serve content locally, dividing the overall delivery load across multiple nodes rather than concentrating it at a single origin server. This segmentation reduces latency by serving content from nearby locations while maintaining high overall delivery capacity through the distributed architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces edge servers as intermediary components between the origin server and client devices. These intermediaries cache content and manage local request routing, acting as buffers that reduce the direct burden on origin servers while delivering content efficiently to clients. The intermediaries resolve the contradiction by providing local service capacity (reducing latency) while orchestrating with the origin server to maintain overall delivery capacity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If content providers include multiple embedded resources in content delivery, then content completeness improves, but computing resource strain increases

Engineering Contradiction:
Improvecontent completenessVSAvoidcomputing resource strain
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-caching embedded resources (images, videos, scripts) at edge servers before they are actually requested by clients. When content is delivered, associated embedded resources are already available at the edge location, eliminating the need for additional real-time retrieval operations. This ensures content completeness while reducing the computational burden on origin servers during active content delivery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges the delivery of main content and embedded resources into a single edge server operation. Instead of separately retrieving content and its embedded resources from the origin server, the edge server delivers both from its local cache in coordinated fashion. This combining approach ensures all content components are delivered together (maintaining completeness) while reducing the overall computing resource strain on the origin server.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If CDN service providers optimize for efficient content transmission, then delivery speed improves, but service complexity increases

Engineering Contradiction:
Improvedelivery speedVSAvoidservice complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent utilizes parameter changes by dynamically adjusting routing parameters based on real-time performance metrics. The system monitors delivery speed, latency, and resource utilization, then modifies routing decisions to optimize for efficient content transmission. This automated parameter adjustment achieves high delivery speed while managing service complexity through algorithmic optimization rather than manual configuration.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent implements feedback mechanisms where the CDN system continuously monitors delivery performance and uses this information to optimize routing and caching strategies. Performance metrics from content transmissions feed back into the system to adjust edge server configurations and routing paths, enabling the system to maintain high delivery speed while automatically managing the complexity of service optimization through data-driven decisions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9172674B1Managing request routing information utilizing performance information
Publication Date: 2015.10.27 AMAZON TECH INC
  • US9172674B1 patent drawing
  • US9172674B1 patent drawing
  • US9172674B1 patent drawing

AI summary

Systems and methods for managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider are provided. The request routing functionality can correspond to the processing of domain name service (“DNS”) requests for resources by computing devices and the resolution of the DNS requests by the identification of a network address of a computing device that will provide the requested resources. Based on the processing resource requests initiated by a client computing device, a CDN service provider can obtain performance information from client computing devices and correlate the performance information into a prioritized list for classes of client computing devices. The prioritized list can be utilized in resolving subsequent DNS queries.