DASH-IF Logo

DASH-IF IOP v5 Part 5: Ad Insertion and Content Replacement

Living Document,

This version:
https://dashif.org/Guidelines/iop-v5/part05-ad-insertion.html
Issue Tracking:
GitHub
Inline In Spec
Currently open Part 5 issues
File a new Part 5 issue (then assign to Part 5 project)
Editor:
DASH-IF Technical Working Group
Document Status:
Working Draft 0.1.
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:
Ad Insertion, Content Replacement, SSAI, SGAI

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. Executive summary

Part 5 of DASH-IF IOP v5 provides guidelines for advertisement insertion in an MPEG CMAF based content-serving workflow using MPEG-DASH as the delivery protocol.

This part details the general architecture of an ad-enabled content-serving workflow together with the conditioning, packaging, and signalling requirements that enable Server-Side Ad Insertion (SSAI) and Server-Guided Ad Insertion (SGAI). It also defines guidelines for the creation, storage, and serving of ad content, and provides informative references and recommendations for auxiliary content and ad systems involved in the ad-insertion architecture.

This section is a structured skeleton migrated from the published DASH-IF IOP v5.0.0 Part 5 heading model. Clause text still needs clause-by-clause migration from the published source. See rag/reports/reconcile-part05-ad-insertion.md.

3. Introduction

This document is Part 5 of DASH-IF IOP v5 and covers ad insertion in DASH.

The published Part 5 document supersedes clause 5, "Ad Insertion in DASH", of DASH-IF IOP Guidelines version 4.3. The scope remains focused on recommendations and guidelines for implementing ad insertion in DASH, updated for greater industry utilization and alignment with MPEG CMAF content authoring.

4. Scope

This part specifies DASH-IF IOP v5 Part 5: Ad Insertion in DASH.

The scope includes guidelines for implementing ad insertion in DASH with CMAF content authoring, including:

Client-Side Ad Insertion is explicitly excluded from the scope of the published Part 5 architecture.

5. References

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

Informative references to migrate include CableLabs VoD, MPEG-2 Systems, RIST, W3C MSE, W3C EME, IAB VAST, Open Measurement SDK, and ITU-R BS.1770-4.

Published Part 5 references have been listed as migration placeholders. The corresponding Bikeshed bibliography aliases still need to be added to part05-ad-insertion.bs and normalized against shared bibliography policy.

6. Terms and Definitions

6.1. General

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

The following terms are migrated from the published DASH-IF IOP v5.0.0 Part 5 source.

ABR encoder

Live encoder that converts a broadcast stream or mezzanine into a ladder of different bit-rate tracks.

ad avail processor

Logical service that, given cue data, determines the placement of advertisement content within a stream and describes the necessary ad decision service communications.

ad content server

Server storing ad content and serving it on a per-request basis.

ad creative

Linear visual and auditory asset that represents the content of an advertisement.

ad decision service

Functional entity that decides which ad or ads will be shown to the user.

ad insertion MPD manipulator

Functional entity that proxies a DASH MPD and may change it to insert the ad creative in the streaming presentation. It may also embed other ad-related metadata, or remove ad-related metadata in the MPD.

ad pod

Location or point in time where one or more ad slots may be scheduled for delivery. This is the same as an ad break, avail, or placement opportunity. The prefixes pre-, mid-, and post- may be used to denote pod location relative to content as before, during, and after respectively.

ad reporting server

Functional entity for collecting viewer impressions of advertisement content.

ad slot

Single ad creative that is one of possibly many others that make up an ad pod.

CDN node

Functional entity returning a segment on request from a DASH client. There are no assumptions on the location of the node.

client-side ad insertion

Ad-serving architecture in which the client application loads advertisements in a secondary player at externally described ad opportunity points.

CMAF packager

Functional entity, often residing with the ABR encoder, which packages the adaptive bit-rate tracks into CMAF tracks.

DASH access client

Client consuming the DASH stream, possibly also containing functionality for client-side ad insertion and viewer impression reporting.

DASH ad resolver

Functional entity which returns one or more remote elements on request from a DASH client, or one or more ad creatives in a DASH-formatted construct on request from a DASH access client.

DASH packager

Functional entity that processes conditioned content and produces media segments suitable for consumption by a DASH client. This entity is also known as a fragmenter, encapsulater, or segmenter.

DASH-IF ad content

Content that follows specific restrictions and requirements according to this specification to be independently produced and inserted into well-formatted main content by simple MPD manipulation processes.

default content

Placeholder content within main content that is shown when a paid placement is not inserted.

MPD generator

Functional entity returning an MPD on request from a DASH client. It may be generating an MPD on the fly or returning a cached one.

origin

Functional entity that contains all media segments indicated in the MPD, and is the fallback if CDN nodes are unable to provide a cached version of the segment on client request.

placement opportunity

Marker within content that denotes where paid placements may be inserted.

reference playback platform

Reference platform for playback, for example HTML5 MSE/EME.

server-side ad insertion

Ad-serving architecture that interleaves content and ad assets prior to the stream reaching the client.

server-guided ad insertion

Ad-serving architecture that fully describes ad opportunities within content prior to the stream reaching the client, but has the client resolve opportunities as needed.

service provider

Entity that actively distributes a streaming service to an end consumer.

splice point

Point in media content where its stream may be switched to the stream of another content, for example to an ad.

tracking event

Data payload associated with an ad creative that is emitted by an application when a specific time point or criteria is met during creative playout.

6.2. Symbols and abbreviations

For the purposes of this part, the following published abbreviations are identified for migration:

Part 5 abbreviations identified from the published source.
Abbreviation Meaning
ABR Adaptive Bit Rate
ADS Ad Decision Service
CSAI Client Side Ad Insertion
CDN Content Delivery Network
CMAF Common Media Application Format
CTA Consumer Technology Association
DASH Dynamic Adaptive Streaming over HTTP
DASH-IF DASH Industry Forum
EIDR Entertainment ID Registry
HTTP HyperText Transport Protocol
IAB Interactive Advertising Bureau
IF Interface
IOP Interoperability Point
ISO International Organization for Standardization
MPD Media Presentation Description
MPEG Moving Picture Experts Group
RIST Reliable Internet Stream Transport
SCTE Society of Cable Telecommunications Engineers
SGAI Server-Guided Ad Insertion
SMPTE Society of Motion Picture and Television Engineers
SSAI Server-Side Ad Insertion
TS Transport Stream
VAST Video Ad Serving Template
VOD Video On-Demand
WAVE Web Application Video Ecosystem

7. Use Cases and Scenarios

7.1. Overview

This clause will migrate published Part 5 clause 4.1.

Ad insertion allows a service provider to replace or augment portions of a main DASH presentation with advertising or slate content. The published Part 5 use cases cover live, VoD, recorded live, pre-roll into live, ad obfuscation, and transition handling between main content and inserted ads.

In all cases, the key problem is to create a Media Presentation that remains playable by DASH clients while allowing ad opportunities to be resolved, conditioned, inserted, tracked, and measured by the entities described in the Part 5 architecture.

7.2. VoD

In a VoD workflow, the full content timeline is available before presentation. Ad opportunities may be known from content metadata, manual authoring, or a previously prepared set of placement opportunities.

VoD ad insertion can be performed before the MPD is served or dynamically when a client requests the MPD. Since the content timeline is known, opportunity duration, splice points, and placement boundaries can typically be determined before playback begins.

7.3. Live

In a live workflow, placement opportunities can be signalled as the live service progresses. The exact end time of an opportunity may not be known when the start of the opportunity is encountered.

Live ad insertion therefore depends on timely opportunity metadata, the ability to estimate or later correct opportunity duration, and MPD update behaviour that allows the DASH client to continue playback while ad Periods or remote resolution points are introduced.

7.4. Recorded Live

Recorded live content combines properties of live and VoD workflows. The content may originate from a live service and retain opportunity metadata and splice points from the live event, but it is consumed later as on-demand or time-shifted content.

Ad insertion for recorded live content may reuse the original live opportunity metadata, replace previously inserted ads, or re-decision placements for the later playback context.

7.5. Pre-Roll into Live

A pre-roll into live workflow inserts ad content before joining an ongoing live presentation. The inserted ad content must lead the client into the live presentation without disrupting playback timing or media compatibility.

This use case requires careful handling of join time, live edge, buffer requirements, and any transition from inserted ad Periods to the current live Period.

7.6. Obfuscation of Inserted Ads

Some deployments may need to obfuscate the identity, boundaries, or source of inserted ad content. Obfuscation can be relevant for business rules, measurement, or attempts to reduce ad blocking.

Obfuscation needs to be balanced with interoperability. DASH signalling, Period boundaries, metadata, and segment URLs still need to provide enough information for correct playback, tracking, and conformance validation.

7.7. Changes at transitions of main content and ads

Transitions between main content and inserted ads can introduce changes in media properties and presentation structure. Examples include changes in:

Part 5 therefore relies on conditioning, Period continuity/connectivity signalling, CMAF-compatible ad content, and client playback behaviour to support seamless transitions.

8. Architectures

8.1. General

The Part 5 architecture is organized around functional entities and interfaces rather than a single deployment topology. The same interfaces can be instantiated in different ways for SSAI and SGAI deployments.

In an SSAI architecture, the service-side entities resolve ad opportunities and produce a DASH MPD in which main content and ad content are already interleaved. The DASH client plays the resulting presentation using ordinary DASH playback procedures, while ad tracking and measurement are driven by metadata and application behaviour.

In an SGAI architecture, the service-side entities signal ad opportunities and provide enough information for the DASH client to resolve some ad placements during playback. This allows ad decisions to depend on client or session context available at the time the opportunity is reached.

The common functional entities are:

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
flowchart LR
    subgraph Source["Source (IF-0)"]
        ABR["ABR Encoder\n+ CMAF Packager"]
    end
    subgraph Packaging["Packaging (IF-1/IF-2/IF-3)"]
        PKG["DASH Packager\n/ MPD Generator"]
    end
    subgraph AdSystem["Ad System (IF-4)"]
        ADS["Ad Decision\nService"]
        ACS["Ad Content\nServer"]
    end
    subgraph Manipulation["Manipulation (IF-5)"]
        MPX["Ad Insertion\nMPD Manipulator"]
    end
    subgraph Client["Client (IF-6/IF-7/IF-8/IF-9)"]
        CDN["CDN / Origin"]
        DASH["DASH Access\nClient"]
        ARP["Ad Reporting\nServer"]
    end

    ABR -->|IF-1 CMAF ingest| PKG
    PKG -->|IF-2 DASH content| MPX
    PKG -->|IF-3 opportunity metadata| MPX
    MPX -->|IF-4a decision request| ADS
    ADS -->|IF-4e ad selection result| MPX
    MPX -->|IF-4b conditioning| ACS
    ACS -->|IF-4c/4d ad content| MPX
    MPX -->|IF-5 MPD + segments| CDN
    CDN -->|DASH stream| DASH
    DASH -->|IF-7 decisioning params| MPX
    DASH -->|IF-8 tracking| ARP
Figure 1: DASH-IF Ad Insertion Architecture (redrawn from published Part 5 Figure 1).

Note: This diagram is a Mermaid redraw of the published Part 5 Figure 1. The original figure is a richer block diagram; this version captures the interface flow between functional entities. A visual check against the published DOCX/PDF is recommended.

9. Overview on Interfaces and Functions

This clause will migrate published Part 5 clause 4.3 and Table 1.

The ad-insertion architectures start with ingest of an input stream over IF-0, which is processed by an ABR encoder and output as well-formed CMAF content over IF-1. A DASH packager / MPD generator uses the IF-1 input to generate a conformant DASH content presentation that is sent over IF-2, and additional opportunity metadata that is sent over IF-3.

An ad insertion MPD manipulator uses the inputs of IF-2 and IF-3 to generate a DASH presentation that mixes content and advertisements. In the SSAI architecture, the manipulator uses IF-4 to ask an ad decisioning / content server to provide advertisement placements for the content stream, possibly using client-sourced parameters from IF-7, before generating the final DASH MPD for IF-5. In the SGAI architecture, the manipulator embeds opportunity information from IF-3 into the DASH MPD IF-5 output so that the DASH client may later use IF-7 to retrieve the appropriate ad placements.

The DASH client uses the reference media pipeline provided by IF-9 to perform seamless playout of the mixed content and ad presentation obtained via IF-5. Ad measurement and tracking is enabled in the client by IF-8 using ad metadata embedded as part of IF-6.

Interfaces identified in the ad insertion architecture, example instantiations, and migration targets.
Interface Function Example instantiations / related references Migration target
IF-0 ABR Stream Source Mezzanine delivery, CableLabs VoD [CABLELABS-VOD], MPEG-2 TS [MPEG2-SYSTEMS], RIST [RIST], SCTE-35 [SCTE35], SCTE-104 [SCTE104] #ad-if0-abr-stream-source
IF-1 Packager Ingest CMAF tracks and switching sets [MPEGCMAF], DASH-IF Live Media Ingest [DASHIF-INGEST] #ad-if1-packager-ingest
IF-2 Content Preparation DASH presentation generation, CMAF-aligned content conditioning, device capability constraints [CTA5003] #ad-if2-content-preparation
IF-3 Ad Avail Signalling SCTE-35 opportunity signalling [SCTE35], SCTE 214 DASH event carriage [SCTE214-1] #ad-if3-ad-avail-signalling
IF-4 Ad Decisioning and Exchange Interfaces Ad decision requests, content conditioning requests, VAST [VAST], SCTE-130 [SCTE130-3], EIDR [EIDR-FORMAT], Ad-ID [SMPTE-RP2092-1] #ad-if4-decisioning-exchange
IF-5 MPD and Segments with Ad Placements DASH MPD/segments [MPEGDASH], CMAF [MPEGCMAF], MPD proxy operations, playback guidelines #ad-if5-mpd-segments
IF-6 Ad Metadata Signalling DASH callback events and metadata for tracking/measurement #ad-if6-ad-metadata
IF-7 Ad Decisioning Parameters and Remote Resolution URL parameters, content-conditioning parameters, Remote Period late binding #ad-if7-remote-resolution
IF-8 Ad Tracking and Measurement VAST view tracking [VAST], Open Measurement SDK [OPENMEASUREMENT], alternative tracking methods #ad-if8-tracking-measurement
IF-9 Reference Media Playback and Decryption HTML5 MSE [MSE], EME [EME], reference playback platform, content protection alignment #ad-if9-reference-playback-decryption

This table is a source-level reconstruction from the published Part 5 interface overview. It should be checked against the original DOCX/PDF table layout and any architecture figure labels before being marked fully reconciled.

10. Interfaces

10.1. General

This clause will migrate published Part 5 clause 5.

10.2. IF-0: ABR Stream Source

IF-0 describes the stream source input to the ad-insertion workflow. The source may be live, VoD, or recorded live content. It provides media and descriptive metadata that are later used for packaging, opportunity signalling, and ad decisioning.

For live workflows, IF-0 may carry descriptive metadata from the live production or automation environment, including cueing information that can be translated into ad opportunities. SCTE-104 [SCTE104] and SCTE-35 [SCTE35] are common sources of such cueing information.

For VoD workflows, descriptive metadata may be provided as side metadata associated with the content asset. It can identify candidate placement opportunities, content identifiers, genre, language, ratings, or other information useful for ad decisioning.

The abstracted IF-0 model provides:

The IF-0 abstracted model assumes that media is produced on a continuous media timeline. Splice points identify media times at which the main content may later transition to another content item, for example an ad or slate. A splice point is identified by media time tsplice.

For live workflows, splice-point information can be generated by production automation, SCTE-104 messages, SCTE-35 messages, or other cueing systems. For VoD workflows, splice-point information can be generated from asset metadata or authoring systems.

When source media is prepared for ad insertion, timed metadata associated with each splice point should preserve at least:

The published Part 5 model identifies three preparation options for CMAF-based live content:

  1. Splice-Conditioned Packaging. CMAF Fragment boundaries are generated at splice points. This allows the DASH packager / MPD generator to create Period boundaries aligned with fragment boundaries.

  2. Splice-Conditioned Encoding. The encoder conditions media so that splice points are suitable for later packaging. For video, the splice point should correspond to a suitable random access point, such as SAP type 1 or SAP type 2, so that packaging can later generate compatible fragments.

  3. Splice Point Signalling. The media is not necessarily fragmented at splice points, but metadata signals the splice points and their properties so that downstream components can generate or infer Period boundaries.

Option 1 is preferred when downstream MPD-level manipulation is expected, because the DASH packager can generate Period boundaries without media segment splitting. Options 2 and 3 require more downstream processing and may require the MPD manipulator or packaging function to access media segment details.

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
timeline
    title Abstracted Media Model with Splice Points
    section Main Content
        t0 : Media start
        tsplice,1 : Splice point 1 (ad opportunity start)
        tsplice,2 : Splice point 2 (ad opportunity end / return to main)
        tsplice,3 : Splice point 3 (next ad opportunity)
    section Ad Opportunity
        tsplice,1 : Ad avail begins
        tsplice,2 : Ad avail ends
Figure 3: Abstracted Media Model with Splice Points (redrawn from published Part 5 Figure 3). The continuous media timeline carries splice-point metadata at each tsplice position. Splice points identify where the main content may transition to ad content and back.
%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
flowchart TD
    subgraph Option1["Option 1: Splice-Conditioned Packaging"]
        E1["ABR Encoder\n(continuous output)"] --> P1["CMAF Packager\n(fragment boundaries at tsplice)"] --> D1["DASH Packager\n(Period boundaries at tsplice)"]
    end
    subgraph Option2["Option 2: Splice-Conditioned Encoding"]
        E2["ABR Encoder\n(SAP at tsplice)"] --> P2["CMAF Packager\n(standard fragmentation)"] --> D2["DASH Packager\n(Period boundaries at tsplice)"]
    end
    subgraph Option3["Option 3: Splice Point Signalling"]
        E3["ABR Encoder\n(continuous output)"] --> P3["CMAF Packager\n(standard fragmentation)"] --> D3["DASH Packager\n(MPD Event at tsplice)"]
    end
Figure 4: CMAF Encoder and Packager Options (redrawn from published Part 5 Figure 4). Option 1 is preferred for MPD-level manipulation. Options 2 and 3 require more downstream processing.

10.3. IF-1: Packager Ingest

IF-1 describes ingest from the ABR stream source or CMAF packager into the DASH packager / MPD generator. The ingest interface provides well-conditioned CMAF tracks and associated metadata to the DASH packaging function.

The interface is expected to align with CMAF-based ingest and DASH-IF Live Media Ingest [DASHIF-INGEST] where applicable. The ingest output should preserve timing and opportunity metadata required to generate IF-2 DASH content and IF-3 ad avail signalling.

The packager ingest process should ensure that media is conditioned so that future ad insertion can be performed using Period boundaries, compatible CMAF headers, and appropriate timeline information.

The published architecture references IF-1 sub-interfaces in Figure 1:

These labels need visual confirmation against Figure 1 before becoming stable anchors in the source.

For splice-conditioned ingest, the DASH packager / MPD generator should receive or infer enough information to:

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
flowchart LR
    subgraph Broadcast["Live Broadcast"]
        BC["Broadcast\nEncoder"]
        SCTE["SCTE-35\nCue Messages"]
    end
    subgraph Segmentation["Segmentation"]
        SEG["Segmenter\n(SCTE-35 aware)"]
    end
    subgraph Output["Output"]
        SEG1["Segment 1\n(pre-break)"]
        SEG2["Segment 2\n(break start)"]
        SEG3["Segment 3\n(ad avail)"]
        SEG4["Segment 4\n(break end)"]
        SEG5["Segment 5\n(post-break)"]
    end
    BC --> SEG
    SCTE -->|splice_insert out| SEG
    SCTE -->|splice_insert in| SEG
    SEG --> SEG1 --> SEG2 --> SEG3 --> SEG4 --> SEG5
Figure 2: Segmented Live Broadcast with Broadcast Events from SCTE-35 (redrawn from published Part 5 Figure 2). Broadcast events from SCTE-35 are used to segment the live stream and signal ad opportunities. The segmenter creates segment boundaries aligned with splice points.

IF-1 has been hardened from the extracted Figure 1 / Figure 4 context, but the actual published figures still need extraction or redrawing before the IF-1a/IF-1b/IF-1c labels are finalized.

10.4. IF-9: Reference Media Playback and Decryption

IF-9 identifies the reference media playback and decryption environment used to evaluate whether the combined main-content and ad-content presentation can be played seamlessly.

The reference playback platform includes DASH playback with HTML5 Media Source Extensions [MSE] and, when encrypted content is used, Encrypted Media Extensions [EME]. Content protection aspects need to remain aligned with Part 6.

The purpose of IF-9 is to constrain the generated presentation to behaviour that a DASH access client and reference playback platform can perform, including:

10.5. IF-2: Content Preparation

IF-2 describes the DASH presentation output of the DASH packager / MPD generator before ad placements are inserted. The IF-2 output is the main content input to the ad insertion MPD manipulator.

The DASH-IF IOP guidelines provide the baseline DASH output requirements. This part adds ad-insertion-specific preparation guidance for content that will later be processed by an ad insertion MPD manipulator.

For each known ad splice point, the DASH packager / MPD generator should either:

Providing a Period boundary at splice points is recommended because the downstream ad insertion MPD manipulator can then perform replacement and insertion operations at MPD level without accessing the content segments.

If the DASH packager / MPD generator is not aware of appropriate ad-insertion splice points, Period boundaries may be omitted and created later by the ad insertion MPD manipulator. In that case, the manipulator may need to perform Period splitting operations as described by IF-5.

The following live-content assumptions are used by the published Part 5 model:

For the initial MPD, the DASH packager / MPD generator maps CMAF data to the MPD using the DASH Core Profile for CMAF content. For every CMAF Switching Set that is known to be offered in the MPD, an InitializationSet should be added to describe all known static parameters for the CMAF Switching Set, preferably based on information in the CMAF Master Header.

The following InitializationSet rules apply:

For live operation, MPD@availabilityStartTime is set to an arbitrary value, for example 1970-01-01T00:00:00Z. The MPD@minimumUpdatePeriod is set sufficiently small so that DASH clients and MPD proxies do not miss Periods created for announced splice points, taking into account minimum splice point advance notice time.

For each Period, a unique identifier for the main content should be carried in an AssetIdentifier descriptor. Example identification schemes include:

Note: Based on MPEG MPD restrictions, at most one AssetIdentifier may be added per Period.

For every splice point i at media time tsplice,i, if a Period is generated, the following Period start rules apply:

Period continuity should be signalled across Adaptation Sets that continue across the Period boundary. Preferably the same signalling and track structure is used.

Every available CMAF Switching Set in the CMAF Presentation is mapped to one Adaptation Set using the DASH Core Profile for CMAF content. The following additional restrictions apply for each Adaptation Set:

If the CMAF Switching Set is identical to one for which an InitializationSet was set, then all parameters from the InitializationSet are copied into the Adaptation Set and @initializationRefId is set to the referenced InitializationSet.

IF-2 content is used together with IF-3 opportunity metadata and IF-4 ad decision/content responses to produce the IF-5 MPD and segments with ad placements.

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
flowchart LR
    subgraph CMAF["CMAF Fragment (Option 1 / Option 3)"]
        direction TB
        F1["CMAF Fragment 1\n(pre-splice)"]
        F2["CMAF Fragment 2\n(at tsplice — SAP)"]
        F3["CMAF Fragment 3\n(post-splice)"]
        F1 --> F2 --> F3
    end
    subgraph DASH["DASH Mapping"]
        direction TB
        P1["Period 1\n(main content)"]
        P2["Period 2\n(ad opportunity)"]
        P3["Period 3\n(main content)"]
        P1 --> P2 --> P3
    end
    F1 -->|maps to| P1
    F2 -->|Period boundary at tsplice| P2
    F3 -->|maps to| P3
Figure 5: CMAF Fragment to DASH Mapping for Option 1 and 3 (redrawn from published Part 5 Figure 5). CMAF Fragment boundaries at splice points map directly to DASH Period boundaries, enabling MPD-level ad insertion without segment splitting.
DASH-IF Main live content MPD.
Context Element or attribute Use Requirement / description
— MPD — Provides the requirements for DASH-IF main content. Any value not specified here is identical to ISO/IEC 23009-1 [MPEGDASH] clause 5.3.1.
MPD ServiceDescription 0 … N —​
ServiceDescription Latency@target O A target latency may be provided.
MPD @profiles M Should include a profile indicator for the DASH CMAF profile urn:mpeg:dash:profile:cmaf:2019.
MPD InitializationSet 0 … N May be present; @inAllPeriods may be set to true to express continuity of content across Period boundaries.
MPD ProgramInformation 0 … N Should be used to describe information about the main content.
MPD Period 1 … N One or more Periods shall be present. Any value not specified here is identical to ISO/IEC 23009-1 clause 5.3.2.
Period @xlink:href R Shall be absent.
Period @xlink:actuate R Shall be absent.
Period @start M Shall be present.
Period AssetIdentifier 0 … 1 Should be used to provide an explicit main content identifier.
Period EventStream 0 … N Specifies an event stream. There are two types of Events: Event Streams terminating in the MPD proxy / ad processor, and Event Streams continuing even if an ad is inserted. The handling of these Events is decided by the proxy.
EventStream @presentationTimeOffset OD Needed for multi-period split Events across Period boundaries. For details, see ISO/IEC 23009-1.
Period AdaptationSet 1 … N At least one Adaptation Set shall be present.
AdaptationSet @xlink:href R Shall be absent.
AdaptationSet @xlink:actuate R Shall be absent.
AdaptationSet SegmentBase@presentationTimeOffset OD (default 0) Shall be set to the correct value of the presentation time of the Adaptation Set at the start of the Period, if the presentation time is not equal to 0.
AdaptationSet @contentType M Shall be present.
AdaptationSet SegmentList 0 Shall be absent.
AdaptationSet Representation 1 … N At least one Representation shall be present in each Adaptation Set. Any value not specified here is identical to ISO/IEC 23009-1 clause 5.3.3.
Period EmptyAdaptationSet 0 Shall be absent.
MPD UTCTiming 1 … N At least one shall be present.

Note: In the table above, M=mandatory, O=optional, R=removed for attributes; element occurrence is given as minOccurs…maxOccurs (N=unbounded). Elements are shown in bold; attributes are non-bold and preceded by @.

This Table 2 reconstruction was rebuilt from the published DOCX table structure (extracted via python-docx table parsing rather than plain-text extraction, which had lost the row layout). The row content and hierarchy have been verified against the DOCX table cells; a final visual check against the rendered PDF is still recommended before this table is treated as fully reconciled.

10.6. IF-3: Ad Avail Signalling

10.6.1. General

Opportunity metadata consists of the original descriptive metadata of the input media related to signalling ad opportunities, together with content segmentation information generated by the DASH packager. Carriage of opportunity metadata in the presentation output by the DASH packager / MPD generator is done through IF-3.

The following requirements apply to opportunity metadata carriage:

The metadata format is workflow-dependent. For the purposes of this part, opportunity metadata carriage using SCTE-35 signalling in DASH MPD Events is assumed. Other methods and formats may be used, but service providers should understand the downstream system effects if the packager does not follow this assumption.

Any opportunity metadata used in the context of this specification must provide:

10.6.2. Opportunity Signalling via SCTE-35

SCTE-35 describes command messages that can be used to describe ad opportunities within a presentation. Broadcast events for a live presentation are often already signalled as SCTE-35 commands and may be directly used. A VoD workflow may optionally synthesize a series of SCTE-35 commands to describe conditioning and opportunities in a VoD presentation.

SCTE 214-1 [SCTE214-1] and SCTE 214-3 [SCTE214-3] define event schemes for carrying SCTE-35. DASH MPD Events may use either urn:scte:scte35:2013:xml or urn:scte:scte35:2014:xml+bin.

When carrying SCTE-35 with MPD Events using the urn:scte:scte35:2014:xml+bin scheme:

For signalling opportunity metadata, it is common to use an SCTE-35 time_signal() splice command carrying a segmentation_descriptor() splice descriptor. Alternatively, the legacy splice_insert() command may be used. In that case, the Event duration equals the break duration in the splice, which is the expected duration of the ad break. The out_of_network indicator is set to true when the splice into an advertisement slot occurs. A break can be terminated early by an additional MPD Event carrying a splice_insert() command with out_of_network set to 0 and the splice-immediate flag set.

The presentation time of the splice point is provided by the splice_time() structure present within the command and is represented in the Event Stream as the value of the Event @presentationTime attribute.

Opportunity boundaries are signalled by pairs of segmentation_descriptor() segment_type_id values. The descriptor pair contains the same segmentation_event_id value so that start and end can be matched. If an expected opportunity duration is known, the segment-start descriptor may provide the expected duration in the segmentation_duration field, which may be represented as the Event @duration until the final duration is known.

With SCTE-35, the final accurate duration is only established when the matching segment-end descriptor is encountered. The segment-end descriptor may occur at, before, or after the duration specified by the segment-start descriptor. The final opportunity duration is calculated as the difference between the splice times of the segmentation pair and is represented as the Event @duration.

An example SCTE-35 message embedded as an MPD Event using SCTE 214 is:

<EventStream schemeIdUri="urn:scte:scte35:2014:xml+bin" timescale="1">
  <Event presentationTime="1540809120" duration="24" id="1999">
    <scte35:Signal>
      <scte35:Binary>
        /DAhAAAAAAAAAP/wEAUAAAfPf+9/fgAg9YDAAAAAAAA/APOv
      </scte35:Binary>
    </scte35:Signal>
  </Event>
</EventStream>

Note: While the example presentation time is large, the presentation time may and typically is adjusted by @presentationTimeOffset to align with the Period start time.

10.7. IF-4: Ad Decisioning and Exchange Interfaces

10.7.1. General

Information about ad content to insert into a presentation is retrieved from the ad decision and ad content servers through IF-4 interfaces. The request from the ad insertion MPD manipulator for ad content provides the information needed to perform ad decisioning, including content metadata and opportunity descriptions. The response is translated by the ad insertion MPD manipulator into the DASH structures described by IF-5.

This part identifies six IF-4 sub-interfaces:

These sub-interfaces are described independently to define the data and interactions that occur in an ad insertion architecture, without assuming a specific deployment form for the ad decision and ad content servers.

This part assumes:

10.7.2. IF-4a: Ad Decision request parameters

A decisioning parameter is a piece of information about the content stream, consumption medium, or end user that is used by the ad decisioning server as part of the advertisement qualification and selection process. The ad insertion MPD manipulator collects and sends this information to the ad decisioning server as part of IF-4a.

Transmission of decisioning parameters is integration-dependent. Examples of commonly used parameters include:

Methods for carrying decisioning parameters in the request from the ad insertion MPD manipulator to the ad content server may follow the same guidelines as requests between the DASH client and ad insertion MPD manipulator. See IF-7a for further details.

10.7.2.1. Decisioning modes

The decisioning mode of an ad decisioning server dictates how the server chooses to fulfill ad requests made by a caller. The ad insertion MPD manipulator must specify the decisioning mode for the ad decisioning server to use through IF-4a, based on the implemented ad insertion architecture.

Two general decisioning modes are used:

After a DASH client receives a stream produced from an SSAI architecture, the stream remains fixed for the playback session. After a DASH client receives a stream produced from an SGAI architecture, the stream can continue to change during the playback session, for example if advertisements are re-decisioned when the user rewinds.

10.7.3. IF-4b: Content Conditioning request parameters

A conditioning parameter is information about the encoding or packaging of the content stream, or about a client player capability, that is used by the ad content server to ensure that an ad creative is compatibly encoded for inclusion in the generated presentation. The ad insertion MPD manipulator collects and sends this information to the ad content server as part of IF-4b.

Transmission of conditioning parameters is integration-dependent. Examples of commonly used parameters include:

An ad content server is expected to use a best-effort approach to the provided conditioning parameters. This part does not require real-time transcoding of ad content to fit all parameters. Further recommendations for use of conditioning parameters by the ad content server are made by IF-4c.

Methods for carrying conditioning parameters from the ad insertion MPD manipulator to the ad content server may follow the same guidelines as requests between the DASH client and ad insertion MPD manipulator. See IF-7b for further details.

10.7.4. IF-4e: Ad Selection Result format

The response of the ad decision server identifies the advertisements selected by the server and provides information associated with them, such as general metadata, viewability requirements, media files, mezzanines, and tracking events. The actual ad content is provided by the ad content server, preferably following the DASH-IF ad content format described by IF-4c. Depending on the decisioning mode, the decision response may also contain the placement and ordering of advertisements.

The explicit response format is workflow-dependent. For an ad selection result format to be used in the context of this part, the result format must include a reference to one or more well-defined ad content items, each with a well-defined duration.

The result format may include:

10.7.4.1. IAB VAST

An IF-4e instantiation is standardized by IAB as the Video Ad Serving Template (VAST) [VAST]. VAST provides structure definitions for representing linear, non-linear, and companion advertisements. A single VAST response may contain a stand-alone ad slot or a pod of ad slots, and each ad structure can provide general metadata, viewability requirements, media files, mezzanines, and tracking events.

In VAST, a reference to DASH-IF ad content may be provided for each Ad element contained in the response. Specifically, each Ad element may contain a MediaFile element under Ad.InLine.Creatives.Linear.MediaFiles, where:

10.7.4.2. SCTE-130

Another IF-4e instantiation is standardized by SCTE as the response of the Ad Decision Service. The Ad Decision Service determines how advertising content is combined with non-advertising content. The exact format and schema of this response is defined by SCTE-130 Part 3 [SCTE130-3].

In SCTE-130, a reference to DASH-IF ad content may be derived for each Placement element contained in the PlacementResponse structure. Specifically, each Placement may contain a core:AssetRef element under Placement.coreContent or Placement.CoreRotationList.core:Content, where the supplied @assetID may be used to retrieve the content from the ad content server specified by @providerID.

The SCTE-130 mapping is based on the published Part 5 explanatory text and should be reviewed by an SCTE-130 expert before being treated as final.

10.7.5. IF-4d: DASH-IF Ad Content Storage format

This interface provides a recommended content format for ad content that is expected to be dynamically inserted into a DASH live or on-demand Media Presentation.

Ad content is recommended to follow the DASH-IF ad content format defined in this clause. This part does not exclude use of other content, but content authors should be aware of differences from the DASH-IF ad content format.

DASH-IF ad content follows the restrictions and requirements of this part and may be produced independently of the main content for insertion into well-formatted main content by simple MPD manipulation.

If content is offered conforming to the DASH-IF ad content format and follows the requirements and recommendations below, it may be annotated with the @profiles parameter value http://dashif.org/guidelines/dashif-ad-content.

The following requirements apply to DASH-IF ad content:

Note: An important assumption for this profile is the availability of content for CMAF tracks over the entire Period. Content may overlap at the end of the Period.

The following recommendations apply to DASH-IF ad content:

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
flowchart TB
    subgraph AdMPD["DASH-IF Ad Content MPD (IF-4d)"]
        direction TB
        MPD["MPD\n(type=static, 1 Period)"]
        Period["Period\n(@duration = ad duration)"]
        BaseURL["BaseURL\n(ad content origin)"]
        AS1["AdaptationSet\n(video)"]
        AS2["AdaptationSet\n(audio)"]
        R1a["Representation\n(codec A, 1080p)"]
        R1b["Representation\n(codec A, 720p)"]
        R2["Representation\n(audio)"]
        MPD --> Period
        Period --> BaseURL
        Period --> AS1
        Period --> AS2
        AS1 --> R1a
        AS1 --> R1b
        AS2 --> R2
    end
Figure 6: Recommended Ad Content Format (redrawn from published Part 5 Figure 6). DASH-IF ad content is a static single-Period MPD with multiple Representations for different codecs and resolutions, enabling dynamic conditioning by the MPD proxy.

Examples of asset identifier schemes include:

DASH-IF Ad content MPD.
Context Element or attribute Use Requirement / description
MPD MPD — Provides the requirements for ad insertion content. Values not specified here are identical to ISO/IEC 23009-1.
MPD @profiles M Should include http://dashif.org/guidelines/dashif-ad-content and shall include the DASH CMAF profile identifier urn:mpeg:dash:profile:cmaf:2019.
MPD @type M Shall be set to static.
MPD @mediaPresentationDuration R Shall not be present.
MPD @minimumUpdatePeriod R Shall not be present.
MPD @minBufferTime M Shall be present.
MPD @timeShiftBufferDepth R Shall not be present.
MPD @suggestedPresentationDelay R Shall not be present.
MPD @maxSegmentDuration R Shall not be present.
MPD @maxSubsegmentDuration R Shall not be present.
MPD ProgramInformation 0 … N Should be used to describe information about the ad.
MPD BaseURL 0 Shall not be present at MPD level; BaseURL belongs in the Period.
MPD Period 1 Exactly one Period shall be present. Values not specified here are identical to ISO/IEC 23009-1.
Period @xlink:href R Shall be absent.
Period @xlink:actuate R Shall be absent.
Period @start R Shall be absent; assumed to be 0.
Period @duration M Shall be present and provide the ad content duration.
Period BaseURL 1 … N At least one shall be present and refer to the BaseURL of the ad content.
Period AssetIdentifier 0 … 1 Should be used to provide an explicit identifier for the ad content.
Period EventStream 0 … N Event Streams are permitted, for example for beaconing.
Period AdaptationSet 1 … N At least one Adaptation Set shall be present.
AdaptationSet @xlink:href R Shall be absent.
AdaptationSet @xlink:actuate R Shall be absent.
AdaptationSet InbandEventStream 0 … N Inband Event Streams are permitted, for example for beaconing.
AdaptationSet CommonAttributesElements — Specifies the common attributes and elements from RepresentationBaseType; values not specified here follow ISO/IEC 23009-1.
AdaptationSet SegmentBase@presentationTimeOffset OD Shall be absent.
AdaptationSet SegmentBase@eptDelta O Shall be absent.
AdaptationSet SegmentBase@pdDelta O May be present for non-video tracks. If present, it shall be non-negative and should be as small as possible.
AdaptationSet @contentType M Shall be present.
AdaptationSet SegmentList 0 Shall be absent.
AdaptationSet Representation 1 … N At least one Representation shall be present in each Adaptation Set.
Period EmptyAdaptationSet 0 Shall be absent.
MPD UTCTiming 0 Shall not be present.
MPD LeapSecondInformation 0 Shall not be present.

This Table 4 reconstruction has been restructured against the DOCX table structure extracted from DASH-IF-IOP-Part5-v5.0.0.docx. The extraction confirmed 36 rows, the published caption "DASH-IF Ad content MPD", the top-level MPD description row, the AdaptationSet @xlink:href and @xlink:actuate rows, and the CommonAttributesElements row. A rendered visual DOCX/PDF review is still recommended to confirm typography and final row hierarchy.

10.7.6. IF-4f: DASH-IF Recommended Slate Content

This interface provides a recommended content format for slate content that is expected to be dynamically inserted into a DASH live or on-demand Media Presentation by an ad insertion proxy to fill timeline gaps introduced by ad durations that do not exactly match the placement opportunity duration.

Slate content is recommended to follow the requirements and recommendations of the DASH-IF ad content format defined by IF-4d. In addition, the following recommendations apply:

10.7.7. IF-4c: Recommended Dynamic Ad Content Response format

The response format should follow the DASH-IF ad content format defined by IF-4d.

The following recommendations apply:

10.8. IF-5: MPD and Segments with Ad Placements

10.8.1. General

IF-5 describes the DASH manifest and segment output produced by the ad insertion MPD manipulator.

The ad insertion MPD manipulator operates under the following assumptions:

Based on this input, the MPD manipulator produces a Media Presentation such that the IF-5 content can be played back by the DASH client. Additional ad metadata transported with linear ad creatives is described as part of IF-6.

When serving ad content, three timing cases exist:

  1. The selected ad content duration matches the ad opportunity duration in the main content. The return to the main Period is direct.

  2. The selected ad content duration exceeds the ad opportunity duration. The ad content needs to be cut short by returning to the main Period, which may require removing or truncating one or more ad-content Periods.

  3. The selected ad content duration is shorter than the ad opportunity duration. Additional content can be added, either as another ad if the remaining ad slot is long enough, or as slate content.

Each splice point is signalled with a Period boundary, or at least sufficient information is available for the MPD proxy to add a Period.

This is the first IF-5 migration pass from published Part 5 clause 5.7. The detailed Table 5 MPD element/attribute requirements still need to be reconstructed from the published source.

10.8.2. Media Presentation Requirements on IF-5

The content on IF-5 shall conform to the DASH Extended Profile for CMAF content, taking into account multi-period requirements.

When used in the context of ad insertion, this part provides additional requirements for multi-Period content created from inserted ads. In general, the client should not be able to differentiate between main-content Periods and ad-content Periods except through signalled metadata or client/application policy.

Ad content is spliced into the main content following the Period structure identified by the published Part 5 Table 5.

Ad Content spliced into main content.
Context Element or attribute Use Requirement / description
MPD MPD — Provides the requirements for content that is combined between main content and ad content. Values not specified here are identical to ISO/IEC 23009-1.
MPD ServiceDescription — Service description information may be present.
ServiceDescription Latency@target 0 Target latency is provided when applicable.
MPD @profiles M Set to urn:mpeg:dash:profile:cmaf-extended:2019 or urn:mpeg:dash:profile:cmaf:2019. The proxy can change to urn:mpeg:dash:profile:cmaf-extended:2019 if it cannot exactly condition the ads to the Period durations.
MPD @minimumUpdatePeriod — Adjusted according to the ad-insertion operation.
MPD InitializationSet 0 … N If InitializationSet@inAllPeriods is true, the MPD proxy checks whether it can provide ad content conditioned to the InitializationSet parameters. If it can, it should leave the InitializationSet included. If it cannot, it must set @inAllPeriods to false or remove the InitializationSet from the MPD.
Period (Main content) Period — Specifies a main-content Period. Information from the main-content Period is reused except where specified differently.
Period (Main content) @duration R Shall not be present; the duration is determined by the @start of the Ad Period.
Period (Main content) EventStream 0 … N Reused from the main content.
Period (Main content) AdaptationSet 1 … N Reused from the main content.
Period (Main content) AssetIdentifier 0 … 1 Reused from the main content.
Period (Ad Content) Period 0 … N Specifies an Ad Content Period. Information from the Ad Content Period is reused except where specified differently.
Period (Ad Content) @id M A unique identifier, preferably reused from one already present in the main content where applicable.
Period (Ad Content) @start M Set to tsplice-out from the main content.
Period (Ad Content) @duration O / remove Typically removed. Detailed operations are described by the MPD proxy operation guidelines.
Period (Ad Content) BaseURL 1 … N Reused from the remote Ad Content Period unless the ad content is moved elsewhere.
Period (Ad Content) @availabilityTimeOffset M Set such that the client can download content according to the schedule of the live service.
Period (Ad Content) EventStream 0 … N Reused from the remote ad or slate content Period unless the proxy removes events based on business rules.
Period (Ad Content) AdaptationSet 1 … N Reused from the remote ad or slate content Period. A subset may be selected based on main content or client information. If compatible with an InitializationSet, it should include @initializationSetRef referencing the compatible InitializationSet.
Period (Ad Content) AssetIdentifier 0 … 1 Reused from the remote Ad Content Period.
Period (Slate Content) Period 0 … N Specifies a Slate Content Period. Information from the slate content Period is reused except where specified differently.
Period (Slate Content) @id M A unique identifier, preferably using a unique slate content identifier.
Period (Slate Content) @start M Typically set to the sum of tsplice-out and the duration of the previous ad.
Period (Slate Content) @duration O / remove Typically removed. Detailed operations are described by the MPD proxy operation guidelines.
Period (Slate Content) BaseURL 1 … N Reused from the remote slate content Period unless the slate content is moved elsewhere.
Period (Slate Content) @availabilityTimeOffset M Set such that the client can download content according to the schedule of the live service.
Period (Slate Content) EventStream 0 … N Reused from the remote slate content Period unless the proxy removes events based on business rules. Slate content is not expected to carry Events.
Period (Slate Content) AdaptationSet 1 … N Reused from the remote slate content Period. A subset may be selected based on main content or client information. If compatible with an InitializationSet, it should include @initializationSetRef referencing the compatible InitializationSet.
Period (Slate Content) AssetIdentifier 0 … 1 Reused from the slate content Period.
Period (Main Content) Period — Specifies the return-to-main-content Period. Information from the main content Period is reused except where specified differently.
Period (Main Content) @start M Set to tsplice-in from the main content.
Period (Main Content) @duration R Shall not be present.
Period (Main Content) EventStream 0 … N Reused from main content.
Period (Main Content) AdaptationSet 1 … N Reused from main content.
Period (Main Content) AssetIdentifier 0 … 1 Reused from the main content.

Key: for attributes, M means mandatory and O means optional. For elements, values use minOccurs … maxOccurs, where N means unbounded. The conditions only hold without using xlink:href. If linking is used, then all attributes are optional and minOccurs is 0.

This Table 5 reconstruction has been restructured against the DOCX table structure extracted from DASH-IF-IOP-Part5-v5.0.0.docx. The extraction confirmed 37 rows and the published row groups for MPD, Period (Main content), Period (Ad Content), Period (Slate Content), and return Period (Main Content). A rendered visual DOCX/PDF review is still recommended to confirm typography and final row hierarchy.

10.8.3. MPD Proxy Operation Guidelines

In an SSAI architecture, the ad insertion MPD manipulator may use IF-4 to request an advertisement decision for part or all of the content stream. The returned ad placements can be represented as ad pods positioned within the content stream, with each pod containing one or more ad slots.

The manipulator inserts the Period element or elements representing the pod at the content stream position specified by the ad decisioning response. If the content MPD already has Period boundaries at the desired ad insertion points, the manipulator may directly insert the Periods representing the ad placements.

Note: The case where the manipulator receives a content MPD without Period boundaries at desired insertion points is not covered by this migration pass. Such a manipulator would need to split content Periods, which may require access to media segments as well as to the MPD.

If the ad insertion MPD manipulator does not perform an insertion at a conditioned Period boundary, and if all Adaptation Sets in the new Period reference exactly one Adaptation Set in a supplemental descriptor for Period continuity, it should remove this Period element and recombine the Periods.

For scenarios where original in-stream ads are replaced rather than inserted into a clean stream, the manipulator creates Periods for ad creatives and replaces sections of the content stream. If the ads are already delineated in the content MPD, the in-stream Periods are replaced by the generated ones. If not, the manipulator must perform splitting operations before replacement.

A typical MPD proxy operation flow is:

  1. Pass through DASH content from IF-2 for Periods that are not ad Periods.

  2. Preserve MPD@minimumUpdatePeriod as received from the main server unless an ad-operation constraint requires otherwise.

  3. Prepare for content replacement when opportunity metadata is provided through IF-3.

  4. Determine or estimate the opportunity duration and request suitable ad content through IF-4a and IF-4b.

  5. Insert one or more selected ad-content Periods into the MPD at tsplice-out.

  6. Remove all main-content Periods that span the opportunity.

  7. Continue updating from the main content server while clients continue following the MPD update behaviour.

For inserted ad Periods:

When the ad opportunity is terminated through opportunity metadata, the MPD proxy updates the MPD according to the relationship between the actual opportunity duration and the inserted ad content duration:

In an SGAI architecture, the ad insertion MPD manipulator uses opportunity metadata from IF-3 to embed signals into the MPD response that allow the DASH client to defer ad opportunity resolution until actively needed.

Published Part 5 states that DASH mechanisms for SGAI signalling were under active study. Keep this section aligned with current Part 10/Part 11 event and remote-resolution work before turning it into final normative text.

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'14px','fontFamily':'system-ui, Arial, sans-serif'}}}%%
flowchart LR
    subgraph Input["Input"]
        MC["Main Content MPD\n(IF-2)"]
        OM["Opportunity Metadata\n(IF-3)"]
        AC["Ad Content MPDs\n(IF-4)"]
    end
    subgraph Proxy["Ad Insertion MPD Manipulator"]
        direction TB
        P1["Identify splice points\nfrom IF-3"]
        P2["Request ad content\nvia IF-4"]
        P3["Insert ad Periods\nat tsplice-out"]
        P4["Remove main-content\nPeriods in opportunity"]
        P5["Copy EventStreams\nand continuity signals"]
        P1 --> P2 --> P3 --> P4 --> P5
    end
    subgraph Output["IF-5 Output MPD"]
        direction TB
        O1["Period: Main content\n(before tsplice-out)"]
        O2["Period: Ad content 1"]
        O3["Period: Ad content 2 / Slate"]
        O4["Period: Main content\n(after tsplice-in)"]
        O1 --> O2 --> O3 --> O4
    end
    Input --> Proxy --> Output
Figure 7: MPD Manipulator Operation — Conforming IF-5 output (redrawn from published Part 5 Figure 7). The ad insertion MPD manipulator takes main content (IF-2), opportunity metadata (IF-3), and ad content (IF-4) as inputs and produces a multi-Period MPD (IF-5) with ad Periods inserted at splice points.

10.8.4. DASH Client Operation Requirements and Guidelines for Playback

A DASH client is expected to consume content offered with the DASH Extended Profile for CMAF content and DASH-IF multi-period ad content.

For playback within a single Period, the DASH client shall support playback of a single Period of content according to the DASH profile for CMAF content.

At Period transitions, the DASH client should handle the following cases:

Playback of overlapping content at Period boundaries can be optimized by using append-window start and append-window end signalling to define the portion of the segment to play. Detailed requirements for this optimization remain for further study.

10.9. IF-6: Ad Metadata Signalling

10.9.1. General

IF-6 carries ad metadata associated with ad creatives and ad placements in the DASH presentation generated by the ad insertion MPD manipulator.

The metadata may be used by the DASH client or an application associated with the DASH client for functions such as:

The exact metadata format is workflow-dependent. In the published Part 5 model, the DASH Callback Event is identified as the primary metadata signalling mechanism to migrate for this interface.

10.9.2. DASH Callback Event

A DASH Callback Event is a DASH event mechanism defined in ISO/IEC 23009-1 [MPEGDASH] that instructs a DASH client to issue an HTTP GET request to a given URL and ignore the HTTP response. It is used in ad-insertion contexts to trigger impression reporting, quartile tracking, and other measurement callbacks at defined media timeline positions.

DASH Callback Events are identified by the scheme URI urn:mpeg:dash:event:callback:2015. The event @value attribute carries the callback URL. The DASH client shall issue an HTTP GET request to the URL specified in @value when the event presentation time is reached, and shall ignore the HTTP response body.

DASH Callback Events may be carried as MPD events (in an EventStream element at Period level) or as inband events (in emsg boxes in Media Segments). For ad-insertion tracking, MPD events are preferred because they allow the ad insertion MPD manipulator to embed tracking callbacks directly in the IF-5 MPD without requiring access to media segments.

When DASH Callback Events are used with inserted ad content:

An example DASH Callback Event in an MPD EventStream for ad impression tracking:

<EventStream schemeIdUri="urn:mpeg:dash:event:callback:2015" timescale="1">
  <Event presentationTime="0" duration="0" id="1">
    https://tracking.example.com/impression?adId=ad123
  </Event>
  <Event presentationTime="15" duration="0" id="2">
    https://tracking.example.com/firstquartile?adId=ad123
  </Event>
  <Event presentationTime="30" duration="0" id="3">
    https://tracking.example.com/midpoint?adId=ad123
  </Event>
</EventStream>

Note: The general DASH event model, including MPD events, inband events, and the urn:mpeg:dash:event:callback:2015 scheme, is specified in Part 10 (Events) of this document set. Part 5 uses DASH Callback Events specifically for ad tracking and measurement in the context of IF-6. For the general event processing requirements applicable to all DASH clients, see Part 10.

10.10. IF-7: Ad Decisioning Parameters and Remote Resolution

10.10.1. General

IF-7 provides mechanisms for communication between the DASH client and the ad insertion MPD manipulator when ad decisioning or content conditioning is deferred until playback time.

IF-7 supports the SGAI architecture by enabling a DASH client to provide decisioning or conditioning parameters when it reaches an ad opportunity, rather than requiring all ad choices to be finalized before the MPD is delivered.

Three IF-7 sub-interfaces are identified:

10.10.2. IF-7a: Decisioning Parameters via URL Parameters

Decisioning parameters may be passed from the DASH client to the ad insertion MPD manipulator using URL parameters. The ad insertion MPD manipulator can then use these values when forming IF-4a requests to the ad decisioning server.

Examples of URL-carried decisioning parameters include:

The use of URL parameters is deployment-specific. Services should take care that client-provided parameters are authenticated, authorized, privacy-preserving, and not trusted beyond their appropriate security context.

10.10.3. IF-7b: Content Conditioning via URL Parameters

Content conditioning parameters may be passed from the DASH client to the ad insertion MPD manipulator using URL parameters. The ad insertion MPD manipulator can then use these values when forming IF-4b requests to the ad content server.

Examples of URL-carried conditioning parameters include:

The ad content server is expected to use the supplied conditioning information on a best-effort basis to return ad content suitable for the current playback context.

10.10.4. IF-7c: Late Binding via Remote Periods

ISO/IEC 23009-1 [MPEGDASH] defines the XLink mechanism for enabling remote elements within an MPD. The Remote Period variant of remote elements can be used in an SGAI architecture to defer ad opportunity resolution until the DASH client reaches the relevant location in the MPD.

In this model, the ad insertion MPD manipulator creates an IF-5 MPD in which ad opportunity locations are represented by Period elements with @xlink:href set to a URL that the DASH client resolves when needed. The @xlink:actuate attribute controls when resolution occurs:

The late-binding SGAI workflow using Remote Periods is:

  1. The ad insertion MPD manipulator receives opportunity metadata through IF-3.

  2. The manipulator creates an IF-5 MPD containing a Period element with @xlink:href pointing to the ad resolver URL and @xlink:actuate="onRequest" at the opportunity location.

  3. Decisioning and/or conditioning parameters from IF-7a and IF-7b are embedded in the URL as query parameters.

  4. When playback approaches the opportunity, the DASH client issues an HTTP GET request to the URL in @xlink:href.

  5. The DASH ad resolver uses IF-4 to retrieve or condition the selected ad content and returns an MPD fragment containing one or more concrete Period elements suitable for insertion.

  6. The DASH client replaces the remote Period element with the resolved Period elements and continues playback.

The URL in @xlink:href should include sufficient context for the ad resolver to perform decisioning and conditioning, including the parameters described by IF-7a and IF-7b. The URL shall be HTTPS when the content is served over HTTPS.

The resolved MPD fragment shall conform to the DASH-IF ad content format described by IF-4d, with the following additional constraints for Remote Period resolution:

Late binding is especially useful when ad decisions depend on the playback context at the time the opportunity is reached, such as current device capabilities, client state, or session attributes.

Note: The XLink remote entity mechanism is defined in ISO/IEC 23009-1 [MPEGDASH] clause 5.6. The DASH client processing model for remote elements, including the onRequest resolution trigger and the HTTP GET request behaviour, is specified there. Part 5 uses this mechanism specifically for SGAI ad opportunity resolution; the general remote entity model applies.

10.11. IF-8: Ad Tracking and Measurement

10.11.1. General

IF-8 covers ad tracking and measurement operations associated with inserted ad content. These operations allow an application, DASH client, or associated measurement component to report ad playback progress, impressions, completion, viewability, and other measurement events.

The tracking and measurement interface is driven by metadata supplied by IF-4, metadata inserted into the MPD or media via IF-6, and playback events observed by the DASH client or application.

10.11.2. VAST View Tracking

VAST [VAST] defines tracking events associated with an ad creative. Examples include impression, start, first quartile, midpoint, third quartile, complete, pause, resume, mute, unmute, skip, and other events.

When VAST tracking metadata is present, the client application or associated ad measurement component should emit the corresponding tracking requests when the specified playback condition is reached.

For dynamic ad insertion, the timing of VAST tracking events should be evaluated against the inserted ad media timeline after any Period insertion, Period splitting, truncation, or slate insertion performed by the MPD proxy.

10.11.3. Open Measurement SDK

The Open Measurement SDK [OPENMEASUREMENT] provides a common framework for ad viewability and verification measurement. When used with DASH ad insertion, Open Measurement integration is expected to operate at the application or player integration layer while using metadata from IF-4 and IF-6 to associate measurement sessions with the inserted ad creative.

10.11.4. Alternative Tracking Methods

Other tracking and measurement mechanisms may be used by deployments. Alternative methods should preserve the same basic mapping between ad decision metadata, inserted media Periods, playback timeline, and emitted measurement events.

This IF-8 migration is an initial source-level baseline from the published heading structure and extracted tracking references. Exact event lists, callback rules, and any examples should be visually checked against the published DOCX/PDF and aligned with current DASH-IF tracking/test-asset plans.

11. Requirements and Recommendations

The following is a summary of the key normative requirements in this part, organized by interface. For the complete requirements, see the interface clauses above. For conformance mapping to validators and test assets, see Part 12.

IF-2 (Content Preparation):

IF-5 (MPD and Segments with Ad Placements):

IF-6 (DASH Callback Event):

IF-7c (Remote Period late binding):

[GROUNDED_BY=rag/corpus/published/DASH-IF-IOP-Part5-v5.0.0.docx.extracted.txt]

12. Open Issues and Work Items

Part 5 open issues and topics to progress.
Topic Status Next action
Published v5.0.0 migration Structured skeleton added Migrate clause text section-by-section from the published Part 5 source.
References and bibliography Open Add/normalize published Part 5 references in part05-ad-insertion.bs.
Terms and abbreviations Terms migrated; abbreviations identified Published term definitions migrated; review exact wording and shared terminology, then normalize abbreviations against shared glossary policy.
Use cases and architecture Initial migration Use cases and architecture prose migrated; extract/redraw published figures and verify wording against DOCX/PDF.
Architecture figures and tables Tables 1, 2, 4, 5 reconstructed Review reconstructed tables against published DOCX/PDF layout; extract or redraw Figures 1–7.
IF-0/IF-1/IF-9/IF-2 early interfaces IF-0/IF-1/IF-2 hardened; Table 2 reconstructed IF-0/IF-1 source hardened with splice-point media time, CMAF preparation options, SAP assumptions, timed metadata, and IF-1 sub-interface tracking; IF-2 source hardened with Period-boundary, EventStream, InitializationSet, AssetIdentifier, Period start, continuity, presentationTimeOffset, and eptDelta rules; Table 2 (DASH-IF Main live content MPD) reconstructed directly from the DOCX table structure via python-docx; extract/redraw Figures 1, 3, 4, and 5 next.
IF-3 Ad Avail Signalling Initial migration Published clause 5.5 opportunity metadata carriage, SCTE-35 MPD Event signalling, and example migrated; review Table 3 formatting against DOCX/PDF.
IF-4 Ad Decisioning and Exchange Initial migration complete Published clause 5.6 initial migration now covers IF-4 introduction, IF-4a, IF-4b, IF-4e, IF-4d, Table 4, IF-4f, and IF-4c; review exact table layout and modal wording against DOCX/PDF.
IF-5 MPD and segment requirements Table 5 reconstructed Initial published clause 5.7 overview, MPD proxy operation, playback guidance, and Table 5 MPD element/attribute requirements migrated; visually review against published DOCX/PDF.
IF-6 Ad Metadata Signalling Initial migration DASH Callback Event baseline migrated; verify exact scheme/payload/examples against published DOCX/PDF and Part 10 event guidance.
IF-7 Decisioning Parameters and Remote Resolution Initial migration URL-parameter decisioning, conditioning, and Remote Period late-binding baseline migrated; align with current remote entity model.
IF-8 Ad Tracking and Measurement Initial migration VAST tracking, Open Measurement SDK, and alternative tracking baseline migrated; verify detailed event/callback rules.
Cross-part alignment Open Align terminology and references with Parts 1, 2, 6, and 12.
Conformance mapping Open Identify validator/test-asset/reference-player expectations and link them to Part 12 after requirements stabilize.

13. Change History

Part 5 change history.
Version Date Change
0.1 Initial Created initial Bikeshed/Markdown shell for Part 5.
0.2 Reconciliation Replaced shell with a structured skeleton matching the published DASH-IF IOP v5.0.0 Part 5 heading model and migration map.
0.3 Reconciliation Migrated published Part 5 term definitions into Bikeshed definition-list form.
0.4 Reconciliation Added published Part 5 bibliography aliases and reconstructed the interface overview table.
0.5 Reconciliation Migrated initial IF-5 MPD and Segments with Ad Placements overview, MPD proxy operation guidelines, and DASH client playback guidance.
0.6 Reconciliation Reconstructed published Part 5 Table 5 MPD element/attribute requirements for main content and ad insertion content.
0.7 Reconciliation Migrated IF-3 Ad Avail Signalling and initial IF-4 Ad Decisioning and Exchange Interfaces material.
0.8 Reconciliation Completed initial IF-4 migration with DASH-IF ad content storage, Table 4, slate content, and dynamic ad content response guidance.
0.9 Reconciliation Migrated initial IF-6 ad metadata, IF-7 remote resolution, and IF-8 tracking/measurement sections.
0.10 Reconciliation Migrated initial use cases, architecture overview, and IF-0/IF-1/IF-9/IF-2 baseline sections.
0.11 Reconciliation Hardened IF-2 content preparation using published Period-boundary, EventStream, InitializationSet, AssetIdentifier, Period start, continuity, presentationTimeOffset, and eptDelta rules.
0.12 Reconciliation Hardened IF-0 and IF-1 with splice-point media time, CMAF preparation options, SAP assumptions, timed metadata, and IF-1 sub-interface figure tracking.
0.13 Reconciliation Normalized bibliography (added missing href fields to 9 entries); aligned IF-6 DASH Callback Event with ISO/IEC 23009-1 scheme URI and Part 10 event guidance; aligned IF-7c Remote Period late binding with ISO/IEC 23009-1 XLink mechanism; replaced #requirements placeholder with normative summary; added Mermaid diagrams for Figures 1, 3, 4, 7.
5.0.0 2021-11 Version published as Part 5 v5.0.0.

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

[CABLELABS-VOD]
CableLabs Video-On-Demand Content Specification. URL: https://specification-search.cablelabs.com/cablelabs-video-on-demand-content-specification-version-1-1
[CTA5003]
Web Application Video Ecosystem - Device Playback Capabilities. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5003-c-final.pdf
[DASHIF-INGEST]
DASH-IF Live Media Ingest Protocol. URL: https://dashif-documents.azurewebsites.net/Ingest/master/DASH-IF-Ingest.html
[EIDR-FORMAT]
EIDR ID Format. 2014. URL: http://eidr.org/documents/EIDR_ID_Format_v1.2.pdf
[EME]
Encrypted Media Extensions. URL: https://www.w3.org/TR/encrypted-media/
[MPEG2-SYSTEMS]
MPEG-2 Part 1: Systems. URL: https://www.iso.org/standard/74427.html
[MSE]
Media Source Extensions. URL: https://www.w3.org/TR/media-source/
[OPENMEASUREMENT]
Open Measurement SDK. URL: https://iabtechlab.com/standards/open-measurement-sdk/
[RIST]
Reliable Internet Stream Transport (RIST), TR-06-1. 2018. URL: https://www.videoservicesforum.org/download/technical_recommendations/VSF_TR-06-1_2018_10_17.pdf
[SCTE104]
Automation System to Compression System Communications Applications Programming Interface. 2019A. URL: https://www.scte.org/standards/library/catalog/scte-104-automation-system-to-compression-system-communications-applications-programming-interface/
[SCTE130-3]
Digital Program Insertion - Advertising Systems Interface Part 3. 2013. URL: https://www.scte.org/standards/library/catalog/scte-130-3-digital-program-insertion-advertising-systems-interfaces-part-3/
[SCTE214-1]
MPEG DASH for IP-Based Cable Services, Part 1: MPD Constraints and Extensions. URL: https://www.scte.org/standards/library/catalog/scte-214-1-mpeg-dash-for-ip-based-cable-services-part-1-mpd-constraints-and-extensions/
[SCTE214-3]
MPEG DASH for IP-Based Cable Services, Part 3: DASH/FF Profile. URL: https://www.scte.org/standards/library/catalog/scte-214-3-mpeg-dash-for-ip-based-cable-services-part-3-dash-ff-profile/
[SCTE35]
Digital Program Insertion Cueing Message for Cable. 2015. URL: https://www.scte.org/standards/library/catalog/scte-35-digital-program-insertion-cueing-message/
[SMPTE-RP2079]
Digital Object Identifier (DOI) Name and Entertainment ID Registry (EIDR) Identifier Representations. 2013.
[SMPTE-RP2092-1]
Advertising Digital Identifier (Ad-ID) Representations. 2015. URL: https://ieeexplore.ieee.org/document/7291893
[VAST]
Video Ad Serving Template. URL: https://www.iab.com/guidelines/digital-video-ad-serving-template-vast/

Issues Index

This section is a structured skeleton migrated from the published DASH-IF IOP v5.0.0 Part 5 heading model. Clause text still needs clause-by-clause migration from the published source. See rag/reports/reconcile-part05-ad-insertion.md. ↵
Published Part 5 references have been listed as migration placeholders. The corresponding Bikeshed bibliography aliases still need to be added to part05-ad-insertion.bs and normalized against shared bibliography policy. ↵
This table is a source-level reconstruction from the published Part 5 interface overview. It should be checked against the original DOCX/PDF table layout and any architecture figure labels before being marked fully reconciled. ↵
IF-1 has been hardened from the extracted Figure 1 / Figure 4 context, but the actual published figures still need extraction or redrawing before the IF-1a/IF-1b/IF-1c labels are finalized. ↵
This Table 2 reconstruction was rebuilt from the published DOCX table structure (extracted via python-docx table parsing rather than plain-text extraction, which had lost the row layout). The row content and hierarchy have been verified against the DOCX table cells; a final visual check against the rendered PDF is still recommended before this table is treated as fully reconciled. ↵
The SCTE-130 mapping is based on the published Part 5 explanatory text and should be reviewed by an SCTE-130 expert before being treated as final. ↵
This Table 4 reconstruction has been restructured against the DOCX table structure extracted from DASH-IF-IOP-Part5-v5.0.0.docx. The extraction confirmed 36 rows, the published caption "DASH-IF Ad content MPD", the top-level MPD description row, the AdaptationSet @xlink:href and @xlink:actuate rows, and the CommonAttributesElements row. A rendered visual DOCX/PDF review is still recommended to confirm typography and final row hierarchy. ↵
This is the first IF-5 migration pass from published Part 5 clause 5.7. The detailed Table 5 MPD element/attribute requirements still need to be reconstructed from the published source. ↵
This Table 5 reconstruction has been restructured against the DOCX table structure extracted from DASH-IF-IOP-Part5-v5.0.0.docx. The extraction confirmed 37 rows and the published row groups for MPD, Period (Main content), Period (Ad Content), Period (Slate Content), and return Period (Main Content). A rendered visual DOCX/PDF review is still recommended to confirm typography and final row hierarchy. ↵
Published Part 5 states that DASH mechanisms for SGAI signalling were under active study. Keep this section aligned with current Part 10/Part 11 event and remote-resolution work before turning it into final normative text. ↵
This IF-8 migration is an initial source-level baseline from the published heading structure and extracted tracking references. Exact event lists, callback rules, and any examples should be visually checked against the published DOCX/PDF and aligned with current DASH-IF tracking/test-asset plans. ↵