DASH Media Streaming Without Manifest Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital video delivery systems face challenges in providing synchronized, randomly accessible, and low-latency media streams that can seamlessly switch between broadband and unicast connections, often resulting in re-buffering and start-up delays due to the need for manifest files and complex metadata handling.
Innovation Solution
The implementation of a system using File Delivery over Unidirectional Transport (FLUTE), Real-Time Object Delivery over Unidirectional Transport (ROUTE), or Object Delivery for Asynchronous Layered Coding and NACK-Oriented Reliable Multicast Protocols, along with Dynamic Adaptive Streaming over HTTP (DASH) segments based on the ISO base media file format, allowing media data reception without a manifest file, enabling synchronized playback, random access, and low start-up delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manifest files and complex metadata handling are used for synchronized media stream delivery, then reliability of media synchronization is improved, but start-up delay and latency increase
Solution Approach 1:
The patent embeds synchronization metadata and timing information directly within the media segment data structures before transmission. This preliminary embedding eliminates the need for separate manifest file processing at reception, allowing immediate parsing and synchronized playback while maintaining reliability. The media segments are pre-configured with all necessary timing and synchronization data required for reliable media stream coordination.
2Adaptability or versatility
If manifest files are required for media stream delivery, then adaptability to different representations is improved, but device complexity increases
Solution Approach 1:
The patent merges the functionality previously separated into manifest files and media segments by embedding representation switching information, timing data, and synchronization metadata directly within the media segment structures. This consolidation eliminates the need for separate manifest file handling while maintaining full adaptability for switching between different media representations. The combined structure reduces device complexity by removing redundant parsing and coordination operations.
3Measurement precision
If separate manifest file processing is used, then measurement precision of media timing is improved, but productivity of media playback decreases
Solution Approach 1:
The patent embeds precise timing information and synchronization data directly within each media segment before transmission. This preliminary inclusion of measurement data eliminates the need for separate manifest file processing during playback, allowing immediate extraction and application of timing information. The result is both maintained measurement precision for accurate media timing and improved productivity through faster playback initiation and reduced processing delays.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In one example, a device includes one or more media decoders configured to decode media data, a network interface configured to receive a layered coding transport (LCT) Session Instance Description (LSID), the LSID including information representing a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a DASH media presentation and data of one or more of the LCT sessions, and a processor configured to initiate consumption of one or more of the representations of the DASH media presentation using the LSID and without using a manifest file for the DASH media presentation, wherein to initiate consumption, the processor is configured to receive, via the network interface, packets of the LCT sessions including portions of data of the one or more of the representations; and provide data of the packets to the one or more media decoders.