Embedded Resource Link Resolution for Dynamic CDN Node Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing content delivery networks (CDNs) rely heavily on conventional DNS servers for edge server selection, which can be inefficient and do not account for client location, content popularity, or network conditions, leading to suboptimal content delivery.
Innovation Solution
An API is introduced to embed link resolution information within HTML documents, allowing for dynamic selection of CDN nodes based on client IP address, content popularity, and network conditions, bypassing traditional DNS servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional DNS servers are used for edge server selection, then the system maintains simplicity in architecture, but content delivery performance deteriorates due to inability to account for client location, content popularity, and network conditions
Solution Approach 1:
The patent introduces an API as an intermediary component between the content delivery system and clients. This API receives client requests, determines optimal CDN nodes based on multiple parameters (client location, content popularity, network conditions), and returns optimized resource links. This intermediary layer enables sophisticated decision-making without requiring complex changes to the core DNS infrastructure, thus improving content delivery performance while maintaining architectural simplicity.
Solution Approach 2:
The patent segments the content delivery function into distinct components: the conventional DNS system remains unchanged for basic domain resolution, while a new API layer handles optimized CDN node selection. This segmentation allows the system to adopt advanced content delivery mechanisms without overhauling the entire architecture, resolving the contradiction between performance improvement and complexity increase.
2Adaptability or versatility
If API-based dynamic CDN node selection is implemented, then content delivery optimization improves by considering client location and network conditions, but the system complexity increases due to additional API infrastructure
Solution Approach 1:
The API designed in the patent serves multiple functions: it receives client requests, determines client location, assesses network conditions, queries content popularity data, and selects optimal CDN nodes. By consolidating these diverse functions into a single multi-functional API, the system achieves high adaptability without proportionally increasing complexity, as the API handles multiple tasks through a unified interface and processing logic.
3Productivity
If traditional DNS resolution is used, then the resolution process remains simple and fast, but it cannot provide optimized content delivery based on real-time network conditions and content popularity
Solution Approach 1:
The system performs preliminary actions by pre-establishing the API infrastructure that can quickly evaluate multiple parameters (client location, network conditions, content popularity) and pre-determine optimal CDN nodes. When a content request arrives, the API has already processed and stored optimization data, enabling rapid resolution without extensive real-time computation, thus maintaining fast response times while achieving optimized content delivery.
Data Source
AI summary
A content delivery method, and related apparatus, that involves the operations of receiving a request for a content resource including at least one embedded resource with a tag. Upon identification of the tag, using at least one delivery parameter to generate a modified embedded resource. Embedding the modified embedded resource in a content resource, such as an HTML document. Delivering, such as in response to request from a browser, the content resource with the modified embedded resource.