SCTE 104/35 Codex

How a splice_request becomes an SCTE 35 splice_insert

9.3.2

A splice_request_data operation is the most common way to open or close an ad break. The Injector turns it into an SCTE 35 splice_insert, copying splice_event_id, unique_program_id, avail_num, and avails_expected straight across, and inferring the flags from splice_insert_type. A spliceStart sets out_of_network_indicator to 1, a spliceEnd sets it to 0, an immediate type sets splice_immediate_flag, and splice_cancel sets splice_event_cancel_indicator. A non-zero break_duration sets the duration_flag, and auto_return_flag feeds the auto_return bit inside the resulting break_duration. In the 2004-2014 editions this mapping is clause 8.3.2 rather than 9.3.2.

Related fields