ANSI SCTE 118-2:2019 pdf free download – Program-Specific Ad Insertion – Content Provider to Traffic Communication Applications Data Model
Current Traffic Systems allow Affiliates to schedule the insertion of commercial advertising in either a Time-Based or Event-Based “window” format. Both Time-Based and Event-Based reservations are setup well in advance based on communication from the content provider as described in SCTE 118-1. This document describes implementation requirements to achieve the functionality associated with Program-Specific Ad Insertion. Program-Specific Ad Insertion is the scheduling and insertion of a Spot into a digital broadcast Program based on the program identifier passed in the SCTE 35 Cue Message. This document does not specify the source of the data that is required by the Traffic System. This data may be provided by the content provider or by a 3rd party (such as a network schedule aggregator, etc.). The data may be provided in its entirety, or a subset of the data may be provided and then manually supplemented.
1.3. Benefits
When implemented as described in SCTE 118-1and with additional reference to SCTE 118-3[11], Program-Specific Ad Insertion will allow for an Avail to be associated with a specific Program, as communicated by the Network. By associating advertising to programming instead of simply to windows, the Affiliate should be able to earn more revenue by guaranteeing the context of the advertisement, and by adapting to occurrences surrounding live events, such as delayed starts, early ends, or overrun. These scenarios, especially when dealing with sports programming, can involve a great deal of high value advertising.
1.4. Intended Audience
The intended audience is content providers, multi-channel video program distributors, TV Everywhere providers/distributors and vendors/developers who build solutions.
2. Normative References
The following documents contain provisions, which, through reference in this text, constitute provisions of this document. At the time of Subcommittee approval, the editions indicated were valid. All documents are subject to revision; and while parties to any agreement based on this document are encouraged to investigate the possibility of applying the most recent editions of the documents listed below, they are reminded that newer editions of those documents might not be compatible with the referenced version.
This word or the adjective“required’ means that the item is an absolute requirement of this document. This phrase means that the item is an absolute prohibition of this document. This word means the value specified shall never be used. This word or the adjective“recommended” means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighted before choosing a different course. This phrase means that there may exist valid reasons in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. This word or the adjective“optional” means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item. Use is permissible for legacy purposes only. Deprecated features may be removed from future versions of this document. Implementations should avoid use of deprecated features.