Resource Cache Inode Tracking for CDN Update Efficiency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The management of resources in content delivery networks (CDNs) is inefficient due to the burden of frequent update requests caused by short time-to-refresh parameters and the risk of distributing invalid or expired resources when using longer parameters, leading to increased strain on CDN service providers.

Innovation Solution

Implementing a resource management system that utilizes an inode data structure for tracking resource validity, with cache management components requesting updates from the origin source when expiration criteria are met, and distributing invalidation notifications across peer-to-peer networks to ensure timely updates and resource synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If shorter time to refresh parameters are associated with resources, then resource validity is improved, but the frequency of update requests increases causing increased strain on CDN service providers

Engineering Contradiction:

Improveresource validityVSAvoidfrequency of update requests

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent implements a feedback mechanism where resource cache components monitor the validity of cached resources and automatically initiate update requests when resources approach expiration. The system receives notifications from origin sources about resource updates and adjusts caching behavior accordingly, creating a closed-loop feedback system that balances resource freshness with request frequency.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent applies preliminary action by proactively refreshing resources before their expiration time is reached. Resource cache components predict when resources will expire and initiate update requests in advance, ensuring resource validity without waiting for complete expiration. This prevents the distribution of invalid resources while avoiding excessive update frequency.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If longer time to refresh parameters are associated with resources, then the frequency of update requests decreases, but the likelihood of distributing invalid or expired resources increases

Engineering Contradiction:

Improvefrequency of update requestsVSAvoidresource validity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements dynamic time-to-refresh parameters that adapt based on resource characteristics, access patterns, and origin source responses. Instead of using fixed refresh intervals, the system dynamically adjusts the time-to-refresh parameter for different resources and even for the same resource over time, optimizing the balance between update frequency and resource validity.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of time-to-refresh from a static value to a dynamic value that is adjusted based on multiple factors including resource type, access frequency, origin source performance, and validation results. This parameter change allows the system to optimize resource caching behavior for different scenarios while maintaining overall system efficiency.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If resource cache components frequently request updates from origin sources, then resource freshness is improved, but the strain on content provider computing resources increases

Engineering Contradiction:

Improveresource freshnessVSAvoidstrain on computing resources

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by selectively updating only those resources that are likely to be accessed and have changed at the origin source. Instead of blanketly refreshing all cached resources, the system uses validation mechanisms to determine which resources need updates, performing partial refresh operations that reduce the strain on origin sources while maintaining resource freshness for critical content.

Inventive Principle:

Principle #16Partial or excessive action

4Adaptability or versatility

If resource cache components use distributed architecture, then system scalability is improved, but the complexity of managing resource invalidation across multiple components increases

Engineering Contradiction:

Improvesystem scalabilityVSAvoidcomplexity of managing resource invalidation

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces intermediary components that mediate between origin sources and distributed resource cache components. These intermediaries centralize certain management functions such as tracking resource validity, coordinating update requests, and distributing invalidation notifications across the distributed cache network, thereby reducing the complexity each individual cache component must handle while maintaining scalability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10491534B2Managing resources and entries in tracking information in resource cache components

Publication Date: 2019.11.26 AMAZON TECH INC

AI summary

A system, method, and computer readable medium for managing resources maintained in resource cache components are provided. A network storage provider storing one or more resources on behalf of a content provider obtains client computing device requests for content. The network storage provider provides resources that are received and maintained on resource cache components. The network storage provider either processes requests or provides notifications to the resource cache components to facilitate the management of resources that need to be updated or are otherwise treated as invalid.