Client Cache Preload via CDN Resource Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers and CDN service providers face strain on resources due to high-volume content requests from client devices, which can be exacerbated by the need to transmit multiple components of requested content, such as Web pages, efficiently while managing costs and latency.
Innovation Solution
Client computing devices preprocess resource identifiers provided by CDN service providers to preload resources in memory before they are needed, using resource request executable code to generate requests for preload information from CDN service providers, optimizing resource delivery through caching and class information management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If content providers transmit all content components (Web pages and embedded resources) to client devices, then complete content delivery is achieved, but network bandwidth consumption and transmission costs increase
Solution Approach 1:
The system performs preliminary actions by having the client device generate resource requests for embedded resources before the actual content delivery occurs. The resource identifier translation service pre-processes these requests to determine if resources are available in CDN cache, allowing the system to avoid transmitting resources that are already cached, thus reducing network bandwidth consumption while ensuring complete content delivery.
2Speed
If CDN service providers maintain resources in cache to improve delivery speed, then latency is reduced and delivery efficiency improves, but CDN cache memory resources are consumed
Solution Approach 1:
The system applies partial action by having the client device request only specific embedded resources that are identified as being available in the CDN cache, rather than requesting all possible resources. The resource identifier translation service selectively translates only those resource identifiers that correspond to cached resources, reducing the overall memory burden on CDN caches while maintaining fast delivery for the subset of resources that are cached.
3Reliability
If client devices request all embedded resources from content providers, then complete resource availability is ensured, but the number of requests increases and strains provider resources
Solution Approach 1:
The resource identifier translation service acts as an intermediary between the client device and the content provider/CDN. It receives resource requests from the client, translates resource identifiers to determine if resources are available in CDN cache, and only forwards requests for resources that are not cached. This intermediary function reduces the number of requests reaching content providers while ensuring complete resource availability for the user.
4Productivity
If resource identifiers are translated to check CDN cache availability, then resource delivery efficiency improves, but additional processing time and complexity are introduced
Solution Approach 1:
The client device performs self-service by autonomously generating resource requests for embedded resources and processing the resource identifier translations itself, rather than relying on the content provider or CDN to manage all resource delivery logic. This self-service approach allows the translation and cache checking to occur locally at the client, reducing the processing burden on servers while improving overall resource delivery efficiency through intelligent caching utilization.
Data Source
AI summary
A system, method and computer-readable medium for client-side cache management are provided. A client request for content is returned that includes executable code for generating a request for preload information. Based on processing the executable code, a client computing device requests preload information from a content delivery service provider. The content delivery service provider provides an identification of content based on resource requests previously served by the content delivery service provider. The client computing device processes the preload information and generates and obtains identified resources for maintenance in a client computing device memory, such as cache.