Full Description

This standard supports delivery of events, frame accurate or non-frame accurate, and associateddescriptive data in MPEG-2 transport streams, MPEG-DASH and HLS. This standard supports thesplicing of content (MPEG-2 transport streams, MPEG-DASH, etc.) for the purpose of Digital ProgramInsertion, which includes advertisement insertion and insertion of other content types. An in-streammessaging mechanism is defined to signal splicing and insertion opportunities and it is not intended toensure seamless insertion (splicing, playlist, etc.). As such, this standard does not specify the insertionmethod used or constraints applied to the content being inserted, nor does it address constraints placed oninsertion devices.

Fully compliant MPEG-2 transport stream (either Multi Program Transport Stream or Single ProgramTransport Stream), MPEG-DASH content, etc. is assumed. No further constraints beyond the inclusion ofthe defined cueing messages are placed upon the stream.

This standard specifies a technique for carrying notification of upcoming points and other timinginformation in the transport stream. A splice information table is defined for notifying downstreamdevices of splice events, such as a network break or return from a network break. For MPEG-2 transportstreams, the splice information table, which pertains to a given program, is carried in one or more MPEGSections carried in PID(s) referred to by that program?s Program Map Table (PMT). In this way, spliceevent notification can pass through most transport stream remultiplexers without need for specialprocessing. For MPEG-DASH, the splice information table is carried in the DASH MPD (See [SCTE214-1]) or in media segments (see [SCTE 214-2] and [SCTE 214-3]. Section 12.2 details how SCTE 35messages are carried in HLS manifests.

Product Details

Published: 2016 ANSI: ANSI Approved Number of Pages: 73 File Size: 1 file , 1.7 MB