SCTE 35 2022 PDF

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 notification 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 transport stream remultiplexers 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-3]). Section 12.2 details how SCTE 35 messages are carried in HLS manifests.

File Size :	1 file , 1.6 MB
Number of Pages :	101
Published :	2022