HTTP Adaptive Streaming Manifest Management via Local Chunk Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The frequent retrieval of large manifest files containing data chunk identifiers for time-shifted playback in telecommunications networks leads to bandwidth congestion and server resource degradation due to the need to periodically update these files, especially when users access live content with time-shifted playback functions.

Innovation Solution

A method where clients generate and manage data chunk identifiers locally within a file, reducing the need to retrieve the file from the server by comparing time intervals and thresholds, and only updating the file periodically to maintain synchronization with the server's production.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the client periodically retrieves the manifest file to obtain identifiers of new data chunks for time-shifted playback, then the client can access past temporal segments, but the bandwidth consumption and server load increase significantly

Engineering Contradiction:
Improvetime-shifted playback capabilityVSAvoidbandwidth consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by having the client generate chunk identifiers locally in advance based on time segments, rather than retrieving them from the server. The client anticipates future playback needs by pre-generating identifiers for time segments that may be needed for time-shifted playback, thus avoiding frequent server requests

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements self-service by enabling the client to autonomously generate chunk identifiers using its own clock and the known chunk duration. The client serves itself by maintaining a local cache of identifiers and only requesting updates from the server when necessary, rather than relying on continuous server-provided identifier lists

Inventive Principle:
Principle #25Self-service

2Reliability

If the client retrieves the manifest file frequently to maintain synchronization with live content production, then the content remains up-to-date, but the server resources are degraded

Engineering Contradiction:
Improvecontent synchronizationVSAvoidserver performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by having the client retrieve only the essential manifest file information periodically rather than continuously. The client generates identifiers locally for normal playback and only performs partial updates by requesting the manifest file from the server when the local cache needs refreshment, thus reducing server load while maintaining adequate synchronization

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements periodic action by establishing a regular interval for manifest file retrieval based on the chunk duration and time-shifted playback requirements. Instead of continuous or frequent requests, the client periodically updates its local identifier cache at intervals that balance synchronization needs with server load reduction

Inventive Principle:
Principle #19Periodic action

3Adaptability or versatility

If the manifest file contains identifiers for a long time period to enable extensive time-shifted playback, then the user can go back further in time, but the file size becomes considerable

Engineering Contradiction:
Improvetime-shifted playback rangeVSAvoidmanifest file size
Core Design Contradiction:
Adaptability or versatilityVSWeight of moving object

Solution Approach 1:

The patent applies segmentation by dividing the manifest file into manageable chunks corresponding to specific time segments. Instead of providing a single large file containing all identifiers, the system segments identifiers by time periods, allowing the client to load only the necessary segments for the desired playback range, thus reducing the size of individual manifest files while maintaining extended time-shifted playback capability

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250247572A1Optimized management of manifest files for telecommunications clients receiving adaptive contents over http (HAS)
Publication Date: 2025.07.31 ORANGE SA
  • US20250247572A1 patent drawing
  • US20250247572A1 patent drawing

AI summary

A method for managing access by a client to content available on at least one server through a telecommunications network, the content being temporally segmented into a sequence of data chunks. The method includes a transmission by the server of a file associating time segments with data chunk identifiers, as well as an action selected from a generation by the client within the file of at least one chunk identifier associated with a time segment and a transmission of a request towards the server to receive the file again.