Streaming Manifest Dependency Description for Tiled Video
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DASH standard limitations prevent efficient streaming of tiled video content, as they do not allow for precise description of dependencies between media components, leading to delays and additional HTTP roundtrips for clients to determine tile associations and dependencies.
Innovation Solution
A method is introduced to enhance streaming manifest files by providing a richer dependency description mechanism, allowing clients to identify mandatory and optional components and their dependencies, enabling dynamic selection and adaptation of media content for user-defined regions of interest.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the DASH standard is used for streaming media content, then adaptive streaming capability is provided, but precise description of dependencies between media components is not possible
Solution Approach 1:
The manifest structure is segmented into distinct dependency description elements that separately identify mandatory and optional media components. Each component can be independently described with its dependency relationships, allowing precise tracking of component associations without requiring complex cross-referencing throughout the entire manifest structure.
Solution Approach 2:
A dependency description mechanism acts as an intermediary between the media components and the client device. This mechanism translates complex dependency relationships into a standardized format that clients can easily interpret, eliminating the need for clients to perform complex analysis of manifest structures to determine component dependencies.
2Adaptability or versatility
If media components are segmented into separate files for independent streaming, then streaming flexibility is improved, but additional HTTP roundtrips are required to determine tile associations
Solution Approach 1:
Dependency relationships between media components are described in advance within the manifest structure. Clients receive all necessary information about component associations and dependencies in a single manifest download, eliminating the need for additional HTTP roundtrips to determine tile associations and dependencies during playback.
Solution Approach 2:
The manifest structure merges component description and dependency information into a single integrated data structure. This combination allows clients to obtain both the list of media components and their dependency relationships in one operation, reducing the number of HTTP roundtrips required.
3Reliability
If all media components are downloaded to ensure complete reconstruction, then reconstruction reliability is improved, but data transmission volume increases
Solution Approach 1:
The client device dynamically selects which media components to download based on real-time conditions such as available bandwidth, processing capabilities, and user preferences. The dependency description mechanism enables clients to make informed decisions about which mandatory and optional components to retrieve, optimizing the balance between reconstruction reliability and data transmission volume.
Solution Approach 2:
Different regions or areas of interest in the media content can be reconstructed with different quality levels by selectively downloading mandatory components for critical areas and optional components for less critical areas. The dependency description allows clients to prioritize components based on their importance to overall reconstruction quality.
Data Source
AI summary
Receiving, transmitting, and generating streamed timed media data organized into temporal media segments, the timed media data belonging to partitioned timed media data comprising timed samples, each timed sample comprising a plurality of subsamples, the timed media data being transmitted as at least two media segment files, each comprising at least one independently encapsulated component. A manifest comprises a dependency item of information indicating a dependency relation between components and a dependency characterization item of information for interpreting the dependency item of information. Alternatively, the manifest comprises at least two different descriptions of at least one component, a first description comprising at least a first dependency item of information indicating a dependency relation from the at least one component to another component and a second description comprising at least a second dependency item of information indicating a dependency relation from another component to the at least one component.