DASH Client Event Dispatch Model for Repeated Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The MPEG DASH standard lacks a defined processing model for repeated events, leading to ambiguity in client processing and potential issues with event handling.
Innovation Solution
A method and apparatus are introduced to handle repeated DASH events by identifying duplicate identifier values and dispatching both the initial and repeated events together, using specific syntax such as '@status=repeat' or 'emsg box with flag &2=1', to ensure proper event processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the DASH client processes repeated events without a defined model, then the client can handle event repeats, but the processing becomes ambiguous and unreliable
Solution Approach 1:
The patent applies preliminary action by pre-defining the processing model for repeated events in the DASH specification before actual event processing occurs. The specification establishes clear rules in advance about how to handle repeated events (including when to dispatch them and how to manage event state), so that when events are processed, the client follows predetermined guidelines rather than making ambiguous decisions during runtime.
2Loss of information
If the DASH client dispatches repeated events with the same identifier value, then event completeness is improved, but processing ambiguity increases
Solution Approach 1:
The patent implements feedback mechanisms where the DASH client tracks previously processed events using their identifier values and dispatches repeated events based on feedback from this tracking. The client maintains state information about events that have been dispatched and uses this feedback to determine whether to dispatch repeated events, ensuring complete event information is preserved while following clear processing rules.
Data Source
AI summary
There is included a method and apparatus comprising computer code configured to cause a processor or processors to obtain identifier values of a plurality of events of a media file in DASH, determine whether ones of the identifier values of the plurality of events having a same value, dispatch, from the DASH client and to a DASH application, a first DASH event of the plurality of events, wherein dispatching the first DASH event having also dispatching together the first DASH event and a second DASH event of the plurality of events based on determining that the second DASH event is scheduled to be dispatched and having the same value as the first DASH event, and control the DASH application based on dispatching at least the first DASH event and the second DASH event.