Application Proxy for Dynamic Resource Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service providers face challenges in efficiently routing client requests due to increasing network complexity and load variability, with existing solutions like DNS-based, BGP-based, and application-level solutions failing to optimize routing within a single request and scaling effectively, especially during peak content demands and service federation.
Innovation Solution
Implementing an application-level intelligence in an edge network device with an application proxy that terminates connections, determines target servers, and proxies requests and resources between client devices and target servers, allowing for fine-grain and dynamic routing without explicit manual provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DNS-based solution is used for routing, then domain name resolution is provided, but only coarse-grain routing at domain level is achieved
Solution Approach 1:
The patent segments the routing control into multiple components: DNS server for domain resolution, authoritative name servers for zone management, and resolvers for query processing. This segmentation enables fine-grain routing decisions at different levels of the DNS hierarchy, moving beyond coarse-grain domain-level routing to more precise subdomain and record-level routing control.
Solution Approach 2:
The patent introduces resolver servers as intermediaries between client devices and authoritative name servers. These resolvers perform recursive queries, cache results, and make intelligent routing decisions based on multiple factors including geo-location, load conditions, and content type. This intermediary layer enables sophisticated fine-grain routing while shielding clients from the complexity of direct authoritative server management.
2Adaptability or versatility
If BGP-based solution is used for routing, then server IP address support in multiple locations is provided, but only coarse-grain routing at server level is achieved
Solution Approach 1:
The patent replaces the BGP protocol mechanism with DNS-based routing. Instead of using BGP's path vector protocol and AS-path attributes for routing decisions, the system uses DNS queries and responses to encode and convey routing information. This substitution enables fine-grain routing control through DNS record types (CNAME, MX, NS) and query patterns while eliminating BGP's complex protocol overhead and manual configuration requirements.
3Loss of time
If application level-based solution is used for routing, then content server redirection is provided, but latency increases due to extra routing and connection setup
Solution Approach 1:
The patent performs routing decisions at the DNS query stage, before any content transfer or application-level communication occurs. The resolver server determines the optimal target server through DNS resolution and returns the appropriate IP address to the client in advance. This preliminary routing action eliminates the need for application-level redirection and connection setup overhead, reducing latency while maintaining content delivery efficiency.
Solution Approach 2:
The patent enables clients to skip intermediate application-level redirection steps by providing direct IP address resolution through DNS. Instead of going through portal servers or application-level gateways that embed URLs and require additional connection setup, clients receive direct routing information from DNS resolvers and can establish immediate connections to the target content servers, rushing through the routing process efficiently.
4Adaptability or versatility
If application level-based solution is used for routing, then content server redirection is provided, but scaling becomes difficult and content server becomes a bottleneck
Solution Approach 1:
The patent makes DNS resolver servers universal routing points that handle all types of content delivery routing decisions. Instead of deploying specialized application-level routing infrastructure for different content types, the same DNS resolver infrastructure handles routing for video, audio, images, software downloads, and other content. This multi-functionality enables easy scaling by simply adding more resolver servers to the DNS infrastructure without requiring content-specific routing components.
Data Source
AI summary
A device receives, from a client device, a request for a resource, where the request provides an identifier of the client device. The device selects a target device for the resource, connects with the selected target device, and provides a proxy of the request to the selected target device, where the proxy of the request hides the identifier of the client device. The device receives the resource from the selected target device, where the resource provides an identifier of the target device. The device provides a proxy of the resource to the client device, where the proxy of the resource hides the identifier of the target device.