Executive Summary
This standard provides an augmentation to the existing “Digital Program Insertion Cueing Message Part 1: Legacy Splice-Based and Time-Based Signaling” [SCTE 35-1] standard. Specifically, a streamlined EventDescriptor addition to the TimeSignal is described. The TimeSignal with EventDescriptor and recommended TimeDescriptor, takes the place of all other Signal and Descriptor combinations provided in [SCTE 35-1].
SCTE 35-2 is applicable as a replacement for all [SCTE 35-1] integrations. This standard is designed to be used in conjunction with [SCTE 30] for QAM MPEG-2 splicing, [SCTE 130-3] for alternate content and ad decisions, [SCTE 224] for policy matching, [SCTE 250] event management, and [SCTE 214-1] or [HLS] for carriage in IP ABR formats. The recommended carriage of SCTE 35-2 in ABR formats is detailed in [214-1] Appendix.
The layout of this document mirrors the sections in [SCTE 35-1], providing the relevant constraints and additions to the SCTE 35 standard as appropriate.
Scope
This standard supports delivery of events, frame accurate or non-frame accurate, and associated descriptive data in MPEG-2 transport streams, MPEG-DASH, and HLS. This standard supports the splicing of content (MPEG-2 transport streams, MPEG-DASH, etc.) for the purpose of digital program insertion, which includes advertisement insertion and insertion of other content types. This standard defines an in-stream messaging mechanism to signal splicing and insertion opportunities. As such, this standard does not specify the insertion method used or constraints applied to the content being inserted, nor does it address constraints placed on insertion devices.
Fully compliant MPEG-2 transport stream (either Multi Program Transport Stream or Single Program Transport Stream), MPEG-DASH content, etc. is assumed. No further constraints beyond the inclusion of the defined cueing messages are placed upon the stream.
This standard specifies a technique for carrying notifications of upcoming points and other timing information in the transport stream. A splice information table is defined for notifying downstream devices of splice events, such as a network Break or return from a network Break. For MPEG-2 transport streams, the splice information table, which pertains to a given program, is carried in one or more MPEG Sections carried in PID(s) referred to by that program’s Program Map Table (PMT). In this way, splice event notification can pass through most MPEG-2 transport stream re-multiplexers without need for special processing. For MPEG-DASH, the splice information table is carried in the DASH MPD (see [SCTE 214-1]) or in media segments (see [SCTE 214-2] and [SCTE 214-5]). The [SCTE 214-1] Appendix and [HLS] detail how [SCTE 35-1] and subsequently SCTE 35-2 messages are carried in HLS manifests
Benefits
This document provides a streamlined Event structure that aligns the SCTE 35-2 message for transport stream carriage of Events with the SCTE 214-1 Event Appendix.
Intended Audience
The intended audience is content providers, multi-channel video program distributors, TV everywhere providers/distributors, Free Ad-Supported Streaming Television (FAST) providers/distributors, and vendors/developers who build solutions.