Edge Node Content Popularity Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks face inefficiencies due to limited storage in edge nodes, which are burdened with storing both popular and unpopular content, leading to reduced efficiency in content serving and caching.

Innovation Solution

Implementing a system where edge nodes dynamically identify content popularity using local and general popularity lists, allowing for caching and serving decisions based on local popularity, with options to cache, serve without caching, or redirect requests to optimize cache efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If edge nodes store both popular and unpopular content to serve all customer requests, then service coverage is improved, but cache efficiency deteriorates

Engineering Contradiction:
Improveservice coverageVSAvoidcache efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements local popularity lists at each edge node that reflect the specific popularity characteristics of that location, rather than using a uniform global approach. This allows each edge node to optimize its cache for local customer preferences, improving cache efficiency while maintaining service coverage for both popular and unpopular content through differentiated local strategies

Inventive Principle:
Principle #3Local quality

2Loss of time

If edge nodes cache all content for quick delivery, then response time is improved, but storage resource utilization deteriorates

Engineering Contradiction:
Improveresponse timeVSAvoidstorage resource utilization
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The patent employs dynamic popularity lists that are continuously updated based on real-time content request patterns at each edge node. This dynamic approach allows the system to adapt cache content automatically, ensuring that storage resources are allocated to currently popular content while maintaining quick response times for frequently requested items

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback from content request patterns to update local popularity lists, which then guide caching decisions. This closed-loop feedback mechanism ensures that edge nodes maintain optimal cache content based on actual customer behavior, improving response times for popular content while avoiding waste of storage resources on unpopular items

Inventive Principle:
Principle #23Feedback

3Reliability

If edge nodes store unpopular content requested by few subscribers, then service availability is improved, but cache efficiency deteriorates

Engineering Contradiction:
Improveservice availabilityVSAvoidcache efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent allows each edge node to maintain its own local popularity list that reflects local demand characteristics. This enables the system to provide service availability for unpopular content at specific locations where it is actually requested, while avoiding the inefficiency of caching unpopular content at all edge nodes, thus maintaining service availability without sacrificing overall cache efficiency

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11870871B2Methods and apparatus for serving content to customer devices based on dynamic content popularity
Publication Date: 2024.01.09 TIME WARNER CABLE ENTERPRISES LLC
  • US11870871B2 patent drawing
  • US11870871B2 patent drawing
  • US11870871B2 patent drawing

AI summary

Methods and apparatus for processing requests for content received from customer devices are described. A decision on how to respond to a request for content is made at an edge node based on a locally maintained popularity list. The local popularity list reflects the local popularity of individual pieces of content at the edge node. A white list of content to be cached and served irrespective of popularity is sometimes used in combination with the local popularity list to make decisions as to how to respond to individual requests for content. In some embodiments the edge node decides on one of the following responses to a content request: i) cache and serve the requested content; ii) serve but don't cache the requested content; or iii) redirect the content request to another node, e.g., an alternate serving node, which can respond to the content request.