DASH Manifest Delta Time Chunk Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing dynamic adaptive streaming over HTTP (DASH) technologies face challenges in efficiently managing and accessing non-existing data chunks, leading to potential errors and inconsistencies during media streaming.

Innovation Solution

The proposed solution involves including information in the media presentation that indicates the availability of start of segments and chunks over time, and configuring client and server devices to avoid accessing non-existing data by determining the validity of the service and using delta time values to identify available chunks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If clients wait for the entire segment to be formed before requesting data, then data availability is ensured, but streaming latency increases

Engineering Contradiction:
Improvedata availabilityVSAvoidstreaming latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The segment is divided into multiple chunks that can be independently requested and downloaded. Clients can request available chunks without waiting for the entire segment to be formed, while the manifest file tracks which chunks are currently available. This resolves the contradiction by allowing partial data retrieval (improving latency) while maintaining data availability for requested chunks (preserving reliability).

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server prepares and makes individual chunks available before the complete segment is finalized. The manifest file is updated to indicate which chunks are currently available for retrieval. Clients can perform preliminary downloads of available chunks, reducing latency while ensuring data availability through the manifest's availability indicators.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If clients request chunks that are not yet available, then streaming continuity is improved, but errors and inconsistencies occur

Engineering Contradiction:
Improvestreaming continuityVSAvoiddata access accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The manifest file provides feedback information about which chunks are currently available for retrieval. Clients query the manifest to determine availability before requesting chunks, and the server provides appropriate response codes for partially complete resources. This feedback mechanism ensures clients request only available chunks (maintaining reliability) while enabling continuous streaming through proactive availability checking (maintaining productivity).

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically updates the manifest file to reflect current chunk availability status. Clients dynamically query the manifest before each chunk request to adapt to changing availability conditions. This dynamic approach allows clients to request chunks as soon as they become available (improving continuity) while avoiding requests for non-existent data (maintaining accuracy).

Inventive Principle:
Principle #15Dynamics

3Productivity

If the manifest file includes detailed availability information, then chunk retrieval efficiency is improved, but file size and processing complexity increase

Engineering Contradiction:
Improvechunk retrieval efficiencyVSAvoidmanifest file complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The availability information is extracted as a separate, dedicated component within the manifest file structure. This dedicated section provides efficient chunk availability queries without burdening the entire manifest with unnecessary complexity. Clients can quickly access availability information without processing the entire manifest, improving retrieval efficiency while managing complexity through targeted information extraction.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12238370B2Determination of availability of chunks of data for network streaming media data
Publication Date: 2025.02.25 QUALCOMM INC
  • US12238370B2 patent drawing
  • US12238370B2 patent drawing
  • US12238370B2 patent drawing

AI summary

An example device for transporting media data includes: a memory configured to store media data; and one or more processors implemented in circuitry and configured to: determine that a manifest file for a media presentation includes data representing a delta time value for a resynchronization element of a segment of the media presentation; determine a multiple of the delta time value; determine a number of chunks of the segment that are currently available for retrieval using the multiple of the delta time value; send a request to a server device for the chunks of the segment that are currently available, wherein the request omits chunks of the segment that are not currently available; and store data of chunks received in response to the request in the memory.