DNS Query Routing via Embedded Resource Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers and CDN service providers face inefficiencies in managing DNS queries and resource requests due to the need for offline modifications of resource identifiers, which can strain computing resources and impact delivery latency and cost.
Innovation Solution
A method for routing DNS queries from client computing devices to a CDN service provider, utilizing resource identifiers that include an application identifier in the DNS portion, allowing for dynamic selection of cache servers or network computing components based on factors like geographic proximity, service level agreements, and quality of service criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If resource identifiers are modified offline to provide alternative resources identifiers for CDN service providers, then content delivery can be facilitated through CDN, but the process becomes inefficient and requires additional offline processing steps
Solution Approach 1:
The patent applies preliminary action by pre-configuring multiple alternative resource identifiers (CNAME records) in the DNS system before content delivery requests occur. When a content request arrives, the CDN service provider can immediately select from pre-available alternative identifiers without requiring offline modification processes, thus resolving the technical contradiction between facilitating CDN delivery and avoiding offline processing delays.
2Adaptability or versatility
If multiple alternative resources identifiers are maintained for the same CDN service provider, then flexibility in routing and meeting service level agreements is improved, but device complexity and management overhead increase
Solution Approach 1:
The patent applies universality by designing a standardized DNS record structure where multiple CNAME records follow a consistent naming convention and format. This universal structure allows the system to maintain multiple alternative resource identifiers with different functions (geographic routing, load balancing, service level agreement compliance) while managing them through a single, unified DNS management interface, thus resolving the contradiction between routing flexibility and management complexity.
3Reliability
If resource identifiers include additional information for CDN service providers in the DNS portion, then the ability to route requests based on geographic proximity and service level agreements is improved, but the structure of resource identifiers becomes more complex
Solution Approach 1:
The patent applies local quality by embedding specific routing information (such as geographic region codes, service level agreement identifiers) directly into specific portions of the CNAME record names. This allows different parts of the resource identifier to serve different functions: the base domain identifies the CDN provider, while appended suffixes provide localized routing information. This resolves the contradiction between improving service level agreement compliance and increasing identifier structure complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system, method and computer-readable medium for request routing. A DNS server at a content delivery network service provider obtains a DNS query corresponding to a resource requested from a client computing device and associated with a first resource identifier. The first resource identifier includes a first portion with DNS information and a second portion with path information. The DNS server selects a network computing component for processing the requested resource based on the DNS portion of the resource identifier and transmits information identifying the selected network computing component to the client computing device.