Introduction

Events may be provided in the MPD or within a Representation in order to signal aperiodic information to the DASH client or to an application. Events are timed, i.e. each event starts at a specific media presentation time and typically has a duration. To classify events a proper scheme identifier identifies the application such that the DASH client can forward the event to the proper application.

Two ways of signalling events are provided, namely

Appropriate schemes and identifiers are defined below.

MPEG DASH Event Schemes

The following event schemes are defined by ISO/IEC 23009-1:

Identifier Reference Section Comment
urn:mpeg:dash:event:2012 ISO/IEC 23009-1 5.10.4 <ul><li>MPD validity expiration event(expiration only, with MPD patch, with complete updated MPD)</li><li>on-receive</li></ul>
urn:mpeg:dash:event:callback:2015 ISO/IEC 23009-1 5.10.4.5.2 <ul><li>DASH callback event</li><li>on-start</li></ul>
urn:mpeg:dash:event:ttfn:2016 ISO/IEC 23009-1 5.10.4.6 <ul><li>Presentation termination event</li><li>on-start</li></ul>

Consortia Event Schemes

The following event schemes are defined by consortia:

Identifier Reference Section Comment
urn:aomedia:cmaf:id3 AOMedia Carriage of ID3 Timed Metadata ID3V2 metadata. Value is a URI defining the sematic. Inband event. Message_data contains ID3 version 2.4 data. Presentation time can not go beyond the CMAF fragment boundary. No explicit dispatch mode fis defined.
tag:atsc.org,2016:event DASH-IF Interoperability Point for ATSC 3.0 5.6.3 ATSC Stream table update. @value shall be set to “stu”. Inband event. Not clear what is carried in message_data. No explicit dispatch mode is defined. An ATSC 3.0 application may use its application events and subscribe to a specific event by (SchemeIdURI, value) pair. However, the dispatch model of events is not specified in the ATSC 3.0 DASH client processing model.
urn:dvb:iptv:cpm:2014 ETSI TS 103 285 V1.3.1 9.1.2.1 TV-Anytime Content Programm Metadata. It provides content identifiers and basic metadata relating to the current programme. MPD or inband event. 1. The event duration indicates the minimum validity duration of the metadata. The event with the latest presentation time takes precedence among events with overlapping durations. The event payload carries the TV-Anytime element. No explicit dispatch mode for the above event is defined.
urn:dvb:iptv:rating:2014 ETSI TS 103 285 V1.3.1 9.1.2.3 Parental rating. Id carries the minimum age. MPD or inband event. No explicit dispatch mode is defined.
urn:dvb:iptv:guidance:2014 ETSI TS 103 285 V1.3.1 9.1.2.3 Parental rating. Id carries the rating. Id carries the rating. MPD or inband event. No explicit dispatch mode is defined.
urn:dvb:dash:radiovis:2016 ETSI TS 103 285 V1.3.1 9.1.2.3 Hybrid radio slide show of text or iamges. @value shall be set to 1, 2, or 3. Inband event. No explicit dispatch mode is defined.
urn:scte:scte35:2013:xml SCTE 214-1 6.7.2 XML representation of SCTE 35 message. MPD event. The event duration is bounded by the period that contains it. Use of essential property if the client is required to process events. Event@messageData is not used. on-receive mode. The use of this scheme is discouraged.
urn:scte:scte35:2013:xml+bin SCTE 214-1 6.7.2 XML representation of SCTE 35 message in binary form. MPD event. The event duration is bounded by the period that contains it. Use of essential property if the client is required to process events. Event@messageData is not used. on-receive mode. The most used event scheme.
urn:scte:scte35:2013:bin SCTE 214-1 6.7.3 binary representation of SCTE 35 message in emsg box. It is defined in 214-3, but being moved in 214-1. Inband event. The event duration is bounded by the period that contains it. Use of essential property if the client is required to process events. Event@messageData is not used. on-receive mode.

Other Inband Event Schemes

The following event schemes are defined by the industry:

Identifier Reference Abstract