Cache Server Hierarchy Resource Expiration Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks (CDNs) face inefficiencies in managing resource requests due to the need for offline modifications of resource identifiers to leverage CDN services, which can strain content providers' resources and impact delivery latency and cost considerations.

Innovation Solution

Implementing a cache server component hierarchy that assigns resource expiration data based on request frequency, allowing popular resources to be maintained at edge servers with shorter expiration times and less popular resources to migrate through the hierarchy, optimizing resource delivery and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If resource identifiers are modified offline to leverage CDN services, then content delivery efficiency is improved, but content provider resource strain increases and delivery latency worsens

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoiddelivery latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-fetching and caching content at CDN edge servers before actual user requests arrive. The origin server proactively pushes content to the CDN hierarchy based on predicted demand patterns, so when users request content, it is already available at edge servers, eliminating the need for real-time identifier modification and reducing delivery latency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism between the origin server and CDN edge servers that uses predictive analytics and demand forecasting to pre-position content. This intermediary layer analyzes user behavior patterns and content popularity trends to determine which content should be cached at edge servers, thereby improving delivery efficiency without straining origin server resources during peak traffic periods.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If resource identifiers are modified offline to leverage CDN services, then content delivery efficiency is improved, but content provider computing resources are strained

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoidcomputing resources
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The system extracts the resource identifier modification function from the origin server and relocates it to the CDN edge servers. Edge servers independently manage their own resource identifier mappings and caching strategies, so the origin server only needs to push content once to the CDN hierarchy. This extraction eliminates the need for continuous origin server involvement in identifier management, reducing its computing resource strain while maintaining delivery efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

CDN edge servers are empowered to self-manage their caching strategies and resource identifier mappings autonomously. Each edge server monitors local cache performance, predicts demand patterns, and independently decides which content to cache or evict without requiring real-time coordination with the origin server. This self-service capability distributes the computational burden across the CDN infrastructure rather than concentrating it at the origin server.

Inventive Principle:
Principle #25Self-service

3Reliability

If popular resources are maintained at edge servers with shorter expiration times, then resource availability is improved, but resource distribution complexity increases

Engineering Contradiction:
Improveresource availabilityVSAvoidresource distribution complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements dynamic expiration times for cached resources based on real-time demand patterns and content popularity metrics. Instead of using fixed expiration times, the CDN edge servers continuously adjust cache validity periods dynamically - popular content receives longer expiration times to maintain availability, while less popular content uses shorter expiration times to free up cache space. This dynamic adaptation simplifies resource distribution by using a unified, flexible caching policy rather than complex manual configuration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The CDN system incorporates feedback loops where edge servers continuously monitor cache hit rates, request patterns, and resource popularity metrics. This feedback information is used to automatically adjust expiration times and caching strategies for different resources. The system learns from actual usage patterns and optimizes resource distribution accordingly, reducing the need for complex pre-planning while improving resource availability based on real-world performance data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10783077B2Managing resources using resource expiration data
Publication Date: 2020.09.22 AMAZON TECH INC
  • US10783077B2 patent drawing
  • US10783077B2 patent drawing
  • US10783077B2 patent drawing

AI summary

Resource management techniques, such as cache optimization, are employed to organize resources within caches such that the most requested content (e.g., the most popular content) is more readily available. A service provider utilizes content expiration data as indicative of resource popularity. As resources are requested, the resources propagate through a cache server hierarchy associated with the service provider. More frequently requested resources are maintained at edge cache servers based on shorter expiration data that is reset with each repeated request. Less frequently requested resources are maintained at higher levels of a cache server hierarchy based on longer expiration data associated with cache servers higher on the hierarchy.