DASH-IF Logo

DASH-IF IOP v5 Part 10: Events

Living Document,

This version:
https://dashif.org/Guidelines/iop-v5/part10-events.html
Issue Tracking:
GitHub
Currently open Part 10 issues
File a new Part 10 issue (then assign to Part 10 project)
Editor:
DASH-IF Technical Working Group
Document Status:
Working Draft 0.4.
See Annex A: Document Status for versioning and workflow.
Contributors:
Contributors are maintained via GitHub pull requests to the IOPv5 repository.
Contributing:
See Part 1 §1.4 Contributing and Reviewing.
Key Words:
Events, Timed Metadata, InbandEventStream, EventStream

1. Intellectual Property Rights

1.1. Disclaimer

This is a document made available by DASH-IF. The technology embodied in this document may involve the use of intellectual property rights, including patents and patent applications owned or controlled by any of the authors or developers of this document. No patent license, either implied or express, is granted to you by this document. DASH-IF has made no search or investigation for such rights, and DASH-IF disclaims any duty to do so. The rights and obligations which apply to DASH-IF documents, as such rights and obligations are set forth and defined in the DASH-IF Bylaws and IPR Policy, including but not limited to patent and other intellectual property license rights and obligations. A copy of the DASH-IF Bylaws and IPR Policy can be obtained at https://dashif.org/.

The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this material is provided AS IS, and the authors and developers of this material and DASH-IF hereby disclaim all other warranties and conditions, either express, implied, or statutory, including but not limited to any (if any) implied warranties, duties, or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of workmanlike effort, and of lack of negligence.

In addition, this document may include references to documents and/or technologies controlled by third parties. Those third-party documents and technologies may be subject to third-party rules and licensing terms. No intellectual property license, either implied or express, to any third-party material is granted to you by this document or DASH-IF. DASH-IF makes no warranty whatsoever for such third-party material.

Note: IPR declarations relevant to DASH-IF specifications are published at https://dashif.org/ipr-declarations/.

1.2. Modal Verbs Terminology

In the present document, shall, shall not, should, should not, may, need not, will, will not, can, and cannot are to be interpreted as described in the ETSI Drafting Rules (Verbal forms for the expression of provisions). must and must not are NOT allowed in DASH-IF deliverables except when used in direct citation.

2. Scope

This document specifies DASH-IF IOP v5 Part 10: Events. Event signalling and processing, including MPD events, inband events, timed metadata tracks, and DASH Callback events.

This part defines the general event model and the requirements for event signalling that are common across service types. Service-type-specific event requirements are defined in:

Note: ETSI TS 103 285 [DVBDASH] (the "DVB-DASH" profile) defines its own constraints on event signalling, including mandatory support for the urn:mpeg:dash:event:2012 MPD validity expiry event and DVB-specific application-signalling event streams (e.g. programme metadata and SCTE-35 cue messages carried per DVB conventions). Alignment notes with DVB-DASH are provided in the relevant clauses below.

3. References

The following referenced documents are necessary for the application of this part:

4. Terms and Definitions

Terms and definitions are inherited from ISO/IEC 23009-1, ISO/IEC 23000-19, and Part 2 unless defined in this part.

MPD event

An event carried in the MPD as an Event element within an EventStream element at Period level.

inband event

An event carried in a Media Segment as an ISO BMFF emsg box.

timed metadata track

A CMAF track carrying timed metadata samples, delivered as a DASH Representation with @mimeType="application/mp4".

5. DASH Events Overview

DASH events are messages having type, timing and optional payload. They can appear either in the MPD (as a Period-level EventStream element) or inband, as ISO BMFF boxes of type emsg. The emsg boxes shall be placed at the very beginning of the Segment, i.e. prior to any media data, so that a DASH client needs a minimal amount of parsing to detect them.

DASH defines events that are processed directly by a DASH client:

User-defined events are also possible. The DASH client does not process these directly — they are passed to an application, or discarded if there is no application willing or registered to process these events. A possible client API would allow an application to register callbacks for specific event types, triggered when the DASH client parses the emsg box in a Segment or the Event element in the MPD. User-defined events can, for example, be used to signal cue messages such as SCTE-35 in an ad-insertion context (see Part 5, Section "IF-3 Opportunity Metadata and SCTE-35 MPD Events").

If several emsg boxes are present in a Segment and one of them is the MPD Validity Expiration event, the emsg carrying it shall always appear first.

6. Update Signaling via In-Band Events

Services may signal the MPD validity duration by embedding in-band messages into Representations instead of specifying a fixed validity duration in the MPD. This allows services to trigger MPD refreshes at exactly the desired time and to avoid needless MPD refreshes.

This clause only applies to services and clients that use in-band MPD validity signaling. For the complete requirements on MPD updates and snapshot validity in live services, see Part 4 (Section "Live Service Offering including MPD Updates").

Services shall define MPD@minimumUpdatePeriod=0 and add an in-band event stream to every audio Representation or, if no audio Representations are present, to every video Representation. The in-band event stream may also be added to other Representations. The in-band event stream shall be identical in every Representation where it is present.

The in-band event stream shall be signaled on the adaptation set level by an InbandEventStream element with @schemeIdUri="urn:mpeg:dash:event:2012" and a @value of 1 or 3, where:

Services shall update MPD@publishTime to a unique value after every MPD update.

Note: MPD@publishTime is merely a version label. The value is not used in timing calculations.

Using in-band signaling and MPD@minimumUpdatePeriod=0, each Media Segment increases the validity period of the MPD by the duration of the Media Segment by default. When a validity event arrives, it carries the validity end timestamp of the MPD, enabling the client to determine when a new MPD refresh is needed.

Services shall emit in-band events as emsg boxes to signal the MPD validity duration using the following logic:

The in-band events used for signaling MPD validity duration shall have schemeIdUri and value matching the InbandEventStream element. Clients shall not use in-band events for MPD validity update signaling if these fields on the events do not match the InbandEventStream element or if the InbandEventStream element is not present in the MPD.

In-band events with value=3 shall provide an updated MPD in the event’s mpd field as UTF-8 encoded text without a byte order mark.

Clients may perform MPD refreshes or process an event-embedded MPD immediately upon reading the event, without waiting for the moment signaled by the event timestamp. Services shall ensure that an updated MPD is available and valid starting from the moment a validity event is signaled.

Multiple Media Segments may signal the same validity update event (identified by a matching id field on the event), enabling the signal to be delivered several segments in advance of the MPD expiration.

In-band MPD validity events shall not be signaled in a static MPD but may be present in the Media Segments referenced by a static MPD, in which case they shall be ignored by clients.

Note: The above may happen when a live service is converted to an on-demand service for catchup/recording purposes.

Note: DVB-DASH [DVBDASH] mandates support for the urn:mpeg:dash:event:2012 in-band MPD validity expiry event, consistent with the signalling defined in this clause, and requires DVB-DASH Live players to react by fetching an updated MPD. Services should confirm they set MPD@minimumUpdatePeriod=0 and populate the InbandEventStream element exactly as required by this clause to remain compatible with DVB-DASH players.

7. MPD Events

In addition to tracking events (e.g. ad starts, quartile tracking), a server may also need to signal additional metadata to the application. There is no need for a generic DASH client to implement this functionality directly — it is enough to provide opaque information that the client passes to an external module. The Event@schemeIdUri provides the addressing mechanism, while MPD events allow opaque payloads to be embedded in the MPD.

MPD events shall be carried in EventStream elements at Period level. Each EventStream element shall carry a @schemeIdUri that identifies the event type. The @timescale attribute shall be present if Event@presentationTime or Event@duration are used.

For ad-insertion cue messages (e.g. SCTE-35), see Part 5 (Section "IF-3 Opportunity Metadata and SCTE-35 MPD Events") for the specific requirements on MPD event stream signalling.

Note: DVB-DASH [DVBDASH] defines its own application-signalling and programme-metadata event streams (using DVB-specific @schemeIdUri values distinct from the SCTE-35 signalling referenced above) for carrying DVB SI-like metadata within the MPD. Services offering DVB-DASH-compatible programme metadata or ad-cue signalling should consult ETSI TS 103 285 clause 9 for the complete set of required event stream descriptors, in addition to the SCTE-35 requirements in Part 5.

8. DASH Callback Events

DASH Callback events, defined in ISO/IEC 23009-1, are a simple native implementation of time-based impression reporting (e.g. quartiles). A callback event is a promise by the DASH client to issue an HTTP GET request to a provided URL at a given offset from PeriodStart. The body of the HTTP response is ignored. Callback events may be signaled as either MPD events or inband events.

For ad tracking and measurement using DASH Callback events in an ad-insertion context, see Part 5 (Section "IF-8 Ad Tracking and Measurement").

9. Timed Metadata Tracks

9.1. General

Timed metadata tracks carry time-aligned metadata samples as CMAF tracks delivered as DASH Representations. They are used for metadata that must be precisely synchronized with media playback, such as:

9.2. Signalling

A timed metadata Representation shall use @mimeType="application/mp4" and shall carry a @codecs string identifying the metadata format.

The AdaptationSet containing timed metadata Representations shall carry a @mimeType="application/mp4" and should carry a Role descriptor indicating the purpose of the metadata (e.g. urn:mpeg:dash:role:2011 with value supplementary, caption, subtitle, or description).

9.3. Timing

Timed metadata tracks shall follow the same timing model as media tracks in the same Period. The @presentationTimeOffset and @timescale attributes shall be consistent with the Period timing as defined in Part 2.

Timed metadata samples shall be aligned with the Period boundaries. Metadata that spans a Period boundary shall be split at the boundary, with each part carried in the respective Period.

Note: The ownership boundary between timed metadata tracks (Part 10) and text/subtitle tracks (Part 9) is defined by the @mimeType: text tracks use application/mp4 with IMSC1 or WebVTT codecs and are governed by Part 9; other timed metadata tracks are governed by this part.

10. Open Issues and Work Items

Part 10 open issues and topics to progress.
Topic Status Next action
Cross-part alignment Partial Cross-references to Part 4 (MPD update timing) and Part 5 (SCTE-35, ad tracking) added as plain-text section references. Verify section names once Part 4 and Part 5 are finalized.
Timed metadata track ownership Partial Ownership boundary with Part 9 (text tracks) defined by @mimeType. Ownership boundary with Part 11 (additional technologies) still needs to be defined.
Conformance mapping Open Add Part 12 conformance mapping for Part 10 (event stream signalling, inband events, timed metadata).
Validator-start tool Open Create tools/validation/validate_part10_events_mpd.py covering EventStream signalling, InbandEventStream presence, and timed metadata track constraints.
MPD Patch events Open Add normative requirements for MPD Patch events (ISO/IEC 23009-1 Amendment 3) once the amendment is finalized.

11. Change History

Part 10 change history.
Version Date Change
0.1 Initial Created initial Bikeshed/Markdown shell for Part 10.
0.2 Migration Migrated general DASH events model and in-band MPD validity/update signaling from DASH-IF-IOP v5-old-draft.
0.3 Reconciliation Added cross-references to Part 4 (MPD update timing) and Part 5 (SCTE-35, ad tracking). Added timed metadata tracks section. Added terms and definitions. Updated scope to reference Parts 4 and 5 for service-type-specific event requirements.
0.4 Fix Replaced cross-document [[#section-id]] anchors with plain-text section references to fix Bikeshed build errors.

Index

Terms defined by this specification

References

Normative References

[MPEGCMAF]
Information technology - Multimedia application format (MPEG-A) - Part 19: Common media application format (CMAF) for segmented media. 2024. URL: https://www.iso.org/standard/85623.html
[MPEGDASH]
Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats. 2022. URL: https://www.iso.org/standard/83314.html

Non-Normative References

[DVBDASH]
ETSI TS 103 285: MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks. 2024. URL: https://www.etsi.org/standards-search