DASH Event Message Track Scheme Signaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current Event Message Track specification in Dynamic Adaptive Streaming over HTTP (DASH) lacks the capability to signal schemes that may appear in the track, limiting its effectiveness in processing and managing event messages.
Innovation Solution
A method is introduced to signal possible event schemes in a track header using a scheme identifier box, which includes the number of schemes, their identifiers, and flags indicating whether each scheme occurs at least once or if other schemes are present, allowing for efficient processing and management of event messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the Event Message Track specification is kept simple without scheme signaling capability, then the specification remains easy to implement, but it cannot effectively process and manage diverse event messages
Solution Approach 1:
The event message track is segmented into distinct components: a scheme identifier box that lists possible schemes, and event messages that reference these schemes. This segmentation allows the specification to handle diverse event types through a structured framework without requiring complex handling logic for each individual event type.
Solution Approach 2:
The scheme identifier box is placed in the track header to preliminarily declare all possible event schemes before the actual event messages appear. This preliminary action enables clients to prepare appropriate processing logic in advance, improving runtime efficiency without adding complexity to the event message format itself.
2Reliability
If scheme identifiers and flags are added to the track header, then event message processing capability is improved, but the track header size and complexity increase
Solution Approach 1:
The scheme identifier box uses localized quality indicators through flags (atleast_once, other_schemes) that provide specific information about scheme occurrence patterns without requiring detailed declarations of every possible event instance. This approach improves processing reliability while minimizing the quantity of header data.
Solution Approach 2:
The specification changes the parameter representation by using compact flags (boolean values) instead of verbose declarations. The atleast_once and other_schemes flags efficiently encode scheme occurrence information in minimal space while maintaining high processing accuracy.
3Loss of information
If all scheme details are declared in the track header, then complete event information is available, but the initialization time and processing overhead increase
Solution Approach 1:
The scheme identifier box extracts only the essential scheme identification information (schemeIdUri and flags) from the complete event message structure, separating it from the detailed event data. This extraction provides sufficient information for client initialization without requiring transmission or processing of complete event instances, reducing initialization time while maintaining information completeness.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems, devices, and methods for obtaining an event message track configured to be processed by a Dynamic Adaptive Streaming over HyperText Transfer Protocol (DASH) client for displaying media content; obtaining a scheme identifier box identifying one or more event schemes that appear in the event message track, wherein each event scheme of the one or more event schemes specifies at least one parameter for processing an event included in the event message track; and providing the event message track to the DASH client or displaying media content based on the event message track according to the one or more event schemes.