DASH Initialization Segment Transport via FLUTE Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for delivering Dynamic Adaptive Streaming over HTTP (DASH) in wireless communication systems face challenges such as initial acquisition latency and service switching time, leading to reduced user satisfaction due to the need for separate file delivery sessions for initialization and media segments.
Innovation Solution
The method involves transporting initialization segments as part of the User Service Description (USD) FLUTE session, allowing caching and reducing latency, while also enabling backward compatibility by sending initialization segments in both USD and media sessions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If initialization segments are delivered in a separate file delivery session from media segments, then the system maintains clear separation of control and data streams, but the user experiences increased startup latency and service switching time
Solution Approach 1:
The patent combines the delivery of initialization segments and media segments into a single file delivery session. The initialization segment is transported as a metadata fragment within the same FLUTE session that carries media segments, eliminating the need for separate sessions and reducing startup latency while maintaining organizational clarity through structured metadata formatting.
Solution Approach 2:
The initialization segment is delivered in advance as a metadata fragment before media segment playback begins. By including the initialization segment in the metadata portion of the file delivery session, the system prepares all necessary initialization data beforehand, allowing the media player to start playback without additional delays for separate initialization segment retrieval.
2Loss of time
If initialization segments are transported as metadata fragments in the USD session, then startup latency is reduced through caching during service discovery, but the system complexity increases due to integrated session management
Solution Approach 1:
The file delivery session is designed to serve multiple functions simultaneously: it delivers both initialization segments and media segments, and it provides both metadata information and actual content data. This multi-functional approach consolidates what would otherwise require separate sessions, reducing overall system complexity while enabling efficient caching of initialization data during service discovery.
Solution Approach 2:
The file delivery session is segmented into distinct metadata and data portions, with the initialization segment clearly identified as a metadata fragment. This segmentation allows the receiving device to efficiently parse and cache only the necessary initialization information during service discovery, reducing startup latency without requiring complex full-session reprocessing.
3Adaptability or versatility
If initialization segments are sent in both USD and media sessions, then backward compatibility is maintained, but network bandwidth is consumed redundantly
Solution Approach 1:
The system creates a lightweight reference copy of the initialization segment information within the metadata structure, rather than duplicating the full initialization segment data across multiple sessions. The metadata fragment contains sufficient information to identify and retrieve the initialization segment, maintaining backward compatibility with devices that expect separate delivery while avoiding redundant transmission of the actual segment data.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method, an apparatus, and a computer program product for wireless communication are provided. The apparatus establishes a file delivery session (910) with a server in a broadcast network for system information. The apparatus also receives a plurality of metadata fragments (912a-912d, 914a-914d) in the file delivery session. The plurality of metadata fragments including at least one initialization segment description fragment (912d, 914d), wherein the at least one initialization segment description fragment is associated with at least one media segment (942a-942g, 962a-962g) transmitted in another file delivery session (940, 960).