DNS Query Routing via Application Broker for Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers face strain on resources due to high volumes of content requests from multiple client devices, especially when requested content includes numerous components like images or videos, which can be alleviated by optimizing the delivery process through network storage providers and CDN service providers, but existing methods do not effectively manage resource requests to reduce latency and costs.
Innovation Solution
Implementing an application broker that routes DNS queries from client computing devices to network computing components, using resource identifiers that include application information to select appropriate network computing components for processing resource requests, thereby optimizing resource allocation and reducing latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If content providers directly serve all content requests from client computing devices, then content delivery control and quality are maintained, but computing resources and network bandwidth are overwhelmed due to high request volumes
Solution Approach 1:
The patent segments the content delivery system into multiple specialized components: origin servers for content management, CDN edge servers for caching and delivery, and application brokers for intelligent request routing. This segmentation distributes the workload across the network, preventing any single server from being overwhelmed while maintaining delivery control.
Solution Approach 2:
The patent introduces application brokers as intermediary components that sit between clients and content providers. These brokers receive DNS queries, analyze application information, and intelligently route requests to appropriate servers. This intermediary layer optimizes resource allocation and reduces direct pressure on origin servers.
2Reliability
If all resource requests are routed to the original content provider, then content accuracy and authorization are ensured, but network latency increases and service quality deteriorates
Solution Approach 1:
The patent implements preliminary action through CDN caching mechanisms where frequently requested content is pre-fetched and stored at edge servers closer to clients. Application brokers also pre-analyze application information to determine optimal routing paths before requests are fulfilled, reducing actual request latency while maintaining content accuracy.
Solution Approach 2:
The patent adds a new dimension to content delivery by introducing geographic and network-topology-based routing. Application brokers use application information to select servers based on multiple dimensions including client location, server capacity, and network conditions, rather than simply routing to the original content provider.
3Use of energy by moving object
If network storage providers or CDN service providers are used to deliver content, then resource strain on content providers is reduced, but effective management and optimization of resource requests are insufficient
Solution Approach 1:
The patent implements feedback mechanisms where application brokers continuously monitor application information, server performance metrics, and request patterns. This feedback is used to dynamically adjust routing decisions and optimize resource allocation, enabling effective management of distributed content delivery while reducing origin server strain.
Data Source
AI summary
A system, method and computer-readable medium for request routing based on application information associated with the requested resource are provided. A DNS nameserver at an application broker 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 application information associated with the requested resource. Based on the application information parsed from the first resource identifier, the DNS nameserver at the application broker selects either a second resource identifier which resolves to a domain of a network computing provider or an IP address associated with a network computing component for processing the requested resource. The DNS nameserver then transmits either the second resource identifier or IP address to the client computing device.


