Enhanced URLTemplates for DASH Media Segment Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Dynamic Adaptive Streaming over HTTP (DASH) protocols face inefficiencies in representing non-consecutive segment numbers, segment timelines, and representation switching, leading to suboptimal messaging and data delivery in multimedia streaming.
Innovation Solution
The introduction of enhanced URLTemplates that allow for compact representation of media parameter values using lists, delimiters, and parameter types such as {Number}, {Time}, and {Timestamp}, enabling efficient signaling and data delivery by generating URLs for non-consecutive segments and segment timelines, and supporting representation switching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional DASH protocols are used to represent non-consecutive segment numbers and segment timelines, then the protocol structure is simple, but the messaging efficiency is poor and data delivery is suboptimal
Solution Approach 1:
The patent segments the media content into discrete segments with unique identifiers, allowing non-consecutive segments to be referenced efficiently. The segment timeline is divided into separate time-point references rather than continuous sequences, enabling selective pushing of specific segments without requiring representation of all intermediate segments.
Solution Approach 2:
The patent introduces a new dimension for segment identification by using timestamp-based segment timelines alongside traditional segment numbers. This allows segments to be referenced from multiple dimensions (segment number, timestamp, URL template parameters), enabling more efficient messaging patterns for non-consecutive segment delivery.
2Loss of information
If detailed segment information is sent to represent non-consecutive segments and segment timelines, then the representation is complete, but the message size increases and parsing complexity increases
Solution Approach 1:
The patent extracts only the essential identifying parameters (segment numbers, timestamps, URL template parameters) needed to locate and deliver specific segments, rather than transmitting complete segment metadata. This extraction approach maintains information completeness for segment identification while minimizing message size and parsing requirements.
Solution Approach 2:
The patent uses URL templates as compact representations that can be expanded into full segment URLs on the server side. Instead of transmitting complete segment paths and metadata, the system transmits simplified template parameters that replicate the full segment information when needed, reducing message size while maintaining completeness.
3Adaptability or versatility
If traditional push directives are used without enhanced URLTemplates, then the implementation is simple, but the ability to represent non-consecutive segments and segment timelines is limited
Solution Approach 1:
The patent creates a universal URLTemplate structure that can represent multiple types of segment references (consecutive segments, non-consecutive segments, segment timelines, representation switches) through a single standardized syntax. This multi-functional template system handles diverse segment delivery scenarios without requiring separate protocol mechanisms for each case.
Solution Approach 2:
The patent enhances push directives by introducing parameterized URL templates with variables that can be dynamically substituted. This allows the same template structure to adapt to different segment delivery scenarios by changing parameter values (segment numbers, timestamps, representation IDs), providing flexibility without increasing structural complexity.
Data Source
AI summary
A method and system of message exchange for controlling flow associated with multimedia streaming services from a server to a client using DASH are disclosed. In one method, one or more Push Directives are sent from a client to a server to indicate information related to media data requested. At least one selected Push Directive uses one URLTemplate that comprises a list of media parameter values, and where each media parameter value corresponds to one media parameter associated with one media segment requested. The server then pushes one or more groups of data for the media data requested to the client according to the list of media parameter values. In another method, at least one selected Push Directive uses one URLTemplate that includes a first number to represent a number of repeating difference of media parameter values associated with requested media segments.