DNS Request Routing in Content Delivery Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers face strain on computing resources due to high volumes of content requests from client devices, especially when requested content includes multiple components, and struggle to manage efficient delivery while considering cost and latency.
Innovation Solution
A content delivery network (CDN) service provider processes DNS requests separately from content storage and delivery, utilizing a service provider to route requests and resolve them based on cost, geographic, and performance criteria, allowing for efficient distribution of resources and improved service level agreements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If content providers directly handle all content requests from client devices, then content delivery can be controlled and managed, but computing resources become strained due to high request volumes
Solution Approach 1:
The patent segments the content delivery system into multiple distributed nodes (edge servers, cache servers, origin servers) geographically distributed across the network. Each node handles specific content requests locally, dividing the overall workload from a single content provider into many smaller handling units, thus reducing strain on any single computing resource while maintaining delivery control through coordinated architecture
2Loss of information
If all content requests are routed to the original content provider, then content accuracy is ensured, but delivery latency increases and service level agreements may be violated
Solution Approach 1:
The patent implements preliminary action by pre-caching content at edge servers and cache servers located closer to end users before actual requests arrive. When content is requested, it can be delivered immediately from the cached location rather than fetching from the origin server, thus reducing delivery latency while maintaining content accuracy through validated caching mechanisms
Solution Approach 2:
The patent introduces intermediary components (DNS service provider, edge servers, cache servers) between the client device and the origin content provider. These intermediaries handle request routing, caching, and delivery optimization, reducing the direct burden on the origin server and minimizing delivery latency while ensuring content accuracy through controlled caching and validation protocols
3Speed
If content is cached at multiple distributed nodes, then delivery speed improves, but system complexity increases
Solution Approach 1:
The patent implements universality by designing cache servers and edge servers with multi-functional capabilities that handle multiple tasks: content caching, request routing, local content delivery, and coordination with the DNS service provider. This consolidates diverse functions into unified server components, reducing overall system complexity while maintaining fast distributed content delivery through the multi-functional nodes
Data Source
AI summary
A system, methods, and interfaces for managing request routing functionality associated with resource requests for one or more resources associated with a content provider. 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. Unlike traditional CDN service provider implementation, the processing of resource requests by the service provider is separate from the delivery of the content by the content provider (or on behalf of the content provider).