CDN Request Routing Loop Prevention via Provider ID Lists
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing content delivery networks (CDNs) connected in multiple levels and topologies face challenges in ensuring high availability and extendibility of content delivery quality, as well as loop detection and prevention in request routing, especially when multiple CDN providers are involved.
Innovation Solution
A method for request routing redirection that includes receiving a DNS request with a list of CDN-provider-IDs, determining processability, and redirecting requests while preventing loops by selecting candidate CDNs and using CDN-provider-IDs to manage redirection hops, ensuring loop detection and prevention across multiple CDNs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If CDNs are connected in multiple levels and topologies to improve content delivery coverage, then the extendibility and availability of content delivery quality improve, but the complexity of loop detection and prevention in request routing increases
Solution Approach 1:
The patent applies preliminary action by maintaining a list of higher CDN-provider-IDs at each CDN node before request routing occurs. This pre-established knowledge structure enables immediate loop detection when requests are redirected, avoiding the need for complex real-time analysis of multi-level CDN topologies. The list is prepared in advance during CDN interconnection setup, allowing the system to handle complex topologies without increasing operational complexity.
Solution Approach 2:
The patent uses the list of higher CDN-provider-IDs as an intermediary mechanism that simplifies loop detection. Instead of directly analyzing complex multi-level CDN relationships, each CDN node uses this intermediary list to quickly determine whether a redirect would create a loop. This intermediary structure mediates between the complex topology and the simple detection logic, resolving the contradiction between extendibility and detection complexity.
2Device complexity
If a single CDN provider candidate is replied to simplify the routing decision, then the device complexity is reduced, but the availability of content delivery quality is not guaranteed
Solution Approach 1:
The patent applies dynamics by enabling CDNs to dynamically select from multiple candidate providers in the list based on real-time conditions such as load, availability, and performance metrics. Rather than a static single-candidate approach, the system adaptively chooses the most appropriate CDN from the list, maintaining simple routing logic while improving availability through dynamic selection among multiple options.
Solution Approach 2:
The patent uses parameter changes by varying the selection criteria from the CDN provider list based on current system state. When one CDN is unavailable or overloaded, the system changes parameters such as selecting the next available candidate from the list, thus maintaining simple routing decisions while ensuring content delivery availability through parameter-based adaptation.
3Measurement precision
If CDN-provider-IDs are tracked for every request to detect loops, then loop prevention accuracy improves, but the loss of time for processing requests increases
Solution Approach 1:
The patent applies preliminary action by pre-populating each CDN node with a list of higher CDN-provider-IDs during system setup. This eliminates the need for time-consuming real-time tracking and analysis of CDN relationships during request processing. The pre-established list enables immediate loop detection by simple comparison, maintaining high accuracy while minimizing processing time loss.
Data Source
AI summary
A method of request routing redirection includes: receiving, by a first content delivery network (CDN) among a plurality of CDNs connected by CDN interconnection (CDNi), a domain name system (DNS) request including a list of CDN-provider-identifications (IDs) of higher CDNs, from a client; determining whether the client's request is processable; and when the client's request is not processable, redirecting the request, while preventing a loop of the request routing on the basis of the list of the CDN-provider-IDs.


