DASH Cache Response Substitution for Legacy Caching Accuracy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

HTTP adaptive streaming technologies face challenges with cache friendliness, particularly when intermediate legacy caches misinterpret responses from DASH-aware caches, leading to incorrect caching and network congestion, as they are not aware of substitution made by smart caches.

Innovation Solution

A method where a first type cache sends a response to a client terminal with an alternative representation of a multimedia content segment, including additional information to prevent further caches from storing the alternative representation as the first representation requested, ensuring correct caching and preventing network congestion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a DASH-aware cache substitutes the first representation with an alternative representation, then the client terminal can still obtain the requested content, but intermediate legacy caches misinterpret the response and incorrectly cache the alternative representation as the first representation

Engineering Contradiction:
Improvecaching accuracyVSAvoidrepresentation identification information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary mechanism (additional information field in the response) that mediates between the DASH-aware cache and intermediate legacy caches. This intermediary element carries substitution information that prevents legacy caches from misinterpreting the alternative representation as the requested first representation, thus resolving the information loss problem while maintaining caching accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a feedback mechanism where the DASH-aware cache provides feedback information (through additional response fields) to intermediate legacy caches about the substitution that occurred. This feedback loop ensures that legacy caches understand the alternative representation was not the originally requested first representation, preventing incorrect caching behavior while maintaining system reliability.

Inventive Principle:
Principle #23Feedback

2Productivity

If a cache stores every requested representation, then the cache hit rate increases, but network resources are consumed and congestion may occur

Engineering Contradiction:
Improvecache hit rateVSAvoidnetwork resources
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent applies local quality by making different parts of the caching system have different behaviors: DASH-aware caches perform substitution and selective caching based on local conditions (client capabilities, representation availability), while legacy caches receive simplified responses without substitution information. This localized differentiation allows optimized caching decisions without requiring all caches to process complex substitution logic, balancing cache hit rates with network resource consumption.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10728295B2Method for operating a cache arranged along a transmission path between client terminals and at least one server, and corresponding cache
Publication Date: 2020.07.28 INTERDIGITAL VC HOLDINGS INC
  • US10728295B2 patent drawing
  • US10728295B2 patent drawing
  • US10728295B2 patent drawing

AI summary

First type cache adapted to be arranged between a client terminal and at least one server, which:is configured to receive, from the client terminal, a request for a first representation of a segment of a multimedia content, said multimedia content being available in a plurality of representations,and comprises a module configured to send a response to the client terminal which comprises:one alternative representation of said segment, which is cached by said first type cache;first additional information preventing a second type cache—arranged between the first type cache and the client terminal—from caching the alternative representation of said response; andsecond additional information identifying the alternative representation of said response, allowing a further first type cache to cache said alternative representation.