DASH Segment File Brand Configuration for Legacy Playback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Dynamic Adaptive Streaming over HTTP (DASH) systems face challenges in seamlessly playing multimedia content stored in segment files, as existing formats are not universally playable across devices, leading to issues with file management and compatibility.
Innovation Solution
The solution involves generating segment files with a configuration that maintains the 'dash' brand while allowing legacy media players to interpret the content by using the 'compatible_brand' field, ensuring seamless concatenation and playback by setting the 'major_brand' field to 'dash' and recording the raw media file's brand in the 'compatible_brand' field, and using the styp box to indicate the 'dash' brand, ensuring compatibility across different representation groups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If segment files are stored intact for DASH streaming service, then the streaming service can be delivered, but the content cannot be seamlessly played when stored and played in receiving devices
Solution Approach 1:
The media file is divided into multiple segments with initialization segments containing metadata and media segments containing actual content. Each segment is structured with boxes (ftyp, moov, moof, mdat) that can be independently processed and concatenated, enabling seamless playback while maintaining DASH streaming functionality.
Solution Approach 2:
The patent implements nested box structures where ftyp boxes are nested within initialization segments, moov boxes contain track boxes and sample description boxes, and moof boxes contain track fragment boxes. This nested structure allows legacy players to interpret the content through compatible_brand fields while DASH players utilize the dash-specific major_brand fields.
2Adaptability or versatility
If segment files are generated with DASH-specific format, then streaming service functionality is enabled, but legacy media players cannot play the stored content
Solution Approach 1:
The segment file structure serves dual purposes: it supports DASH streaming service with dash-specific branding while simultaneously being interpretable by legacy media players through compatible_brand fields. The same file structure enables both adaptive streaming and traditional playback without requiring separate formats.
Solution Approach 2:
The compatible_brand field acts as an intermediary that bridges DASH-specific segment files and legacy media players. By recording the raw media file's brand in this field, legacy players can identify and play the content while DASH players ignore this field and use the major_brand field for protocol-specific operations.
3Productivity
If multiple representations use the same track_ID for media type, then efficient resource management is achieved, but file structure complexity increases requiring multiple sample entries
Solution Approach 1:
The patent applies local quality by creating distinct sample description boxes within track boxes for each representation, while maintaining unique track_IDs at the track level. This allows efficient resource management through shared track identifiers while managing complexity through localized sample description structures that are confined to specific track contexts.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
To store and play contents streamed in a multimedia streaming system, an operating method of a server in the multimedia streaming system includes receiving a transmission request for a Media Presentation Description (MPD) file; and transmitting the MPD file including a flag indicating whether it is possible to generate a media file that is playable by a media file player by concatenating transmitted segments.