Configure input: events mapping to control

Connect to SCTE-224 events database

Input tab section allows Stream Conditioning service to connect to the list of events formatted using SCTE 224 standard (media points). In other words, Input section connects to a SCTE 224 database, and maps media points into video headend operations (such as switch to blackout using ESAM for instance). Mapping of media points over ESAM or SCTE-104 controls is stored in a separate database.

1. Click the Input tab.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Type	Select ESNI SCTE-224.
   ESNI Server	Prisma can connect to its own database of SCTE-224 events or connect to an external database. When connecting to SCTE-224 events database managed by Prisma (via viewing policy manager service, one database per service), a drop-down list will list all the different events database available (one per Viewing policy manager service). This generally corresponds to a programmer (ESPN, FOX etc.).
   ESNI Media ID	From the selected SCTE-224 events database, select the Media ID containing all the different media points, viewing policies, policies and audience. Selected Media ID generally corresponds to a linear channel for instance.
   Ignore metadata	Check this box if ESNI SCTE-224 metadata are not used in conditioning to improve performance.
   Enable audit	Return status of the events to the SCTE-224 database to enable SCTE-224 audit creation.

Once the connection to the SCTE-224 events database is configured, you need to configure the way media points will be converted into operations. Indeed, a Media (identified by its Media ID) contains a collection of Media Points.

These Media points provide information about:

• When the event shall be triggered (@matchTime attribute, @effective and @expire may also be used to provide validity window).
• SCTE-35 in-band trigger conditions (via <asset> section).
• The policy to apply or remove. A policy being a collection of viewing policies.

Translations: identify events using Media point filtering

Events (SCTE-224 media points) must be mapped to ESAM/SCTE-104 or SCTE-30 controls.

To configure media point filtering, proceed as follows:

1. From the Input tab, go to the Translations section then click Add rule.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Name	Name of the translation rule.
   SCTE-224 filters	Configure filtering rules to identify a n SCTE-224 event, using filters such as Viewing Policy ID, audience ID, action etc.

Translations: Operations

Prisma implements different types of operations that may be grouped in two categories:

Standard operations

Alternate content and SCTE-35. These operations are based on standard and supported by any device compatible ESAM/SCTE-104/SCTE-30.

Advanced operations

Image overlay, Animation, slate and video clip operations require specific functionalities only available within MediaKind portfolio (Live Encoder for instance).

Operation: General parameters

To configure one or more operation(s) associated with the filtering of events configured in the previous section, follow these steps:

1. From the Input tab, go to the Operations section then click Add.

2. Enter and/or select the appropriate value for each parameter:

The next sections provide information regarding the configuration of the different types of operations, as well as scheduling restrictions, ESAM properties and fallback operations.

Operation: Alternate Content

When selecting Live Alternate content type of operation, the following configuration is expected:

When the Input ID field is left blank, this implicitly means a return to “default” asset. In the case of a live to live stream switching for instance, configuring a blank value will lead to returning to main live stream.

Scheduling, ESAM properties and Fallback operation tabs are common to all operations. Please refer to:

• Operation (all): Scheduling configuration
• Operation: ESAM properties
• Operation: Fallback operation

Operation: SCTE-35

SCTE-35 operation can be used for two main purposes:

• SCTE-35 insertion: Prisma controls the encoder or TS processor to insert a given SCTE-35 in its output stream. In this case, Scheduling mode shall be set to Time-based. This mode is also referred to as “out-of-band”.
• SCTE-35 rewrite: This operation is aimed at modifying the incoming SCTE-35 to normalize the information for instance (rewriting descriptors, translating the SCTE-35 commands from splice insert to time signal). In this case, Scheduling mode shall be set to SCTE-35 Signal-based and Discard incoming signal must be checked (to avoid two signals in the output stream).

SCTE-35 Insertion

To configure out-of-band (time-based) SCTE-35 insertion, follow these steps:

1. Make sure Scheduling mode is set to Time-based.

2. Under the Operation tab, set Type to SCTE-35 from the list of available type of operations.

3. Configure Splice info: under the Splice info tab, select Splice info type from the list of SCTE-35 command types.

   

   The set of parameters to configure will depend on the selected command. Users shall be familiar with the SCTE-35 standard. The main commands used are generally the following one: Splice Insert and Time Signal.

   Some parameters can be automatically configured (retrieved from the media point/event schedule), for instance the Break duration or segmentation duration.

   The figure below shows a Splice insert command configuration example with Break duration set automatically to the duration of the media point policy.

   

   Any SCTE-35 message, whether it’s a splice null, splice insert etc. contains a splice info section, as well as (optionally) a set of one or more segmentation descriptors. These segmentation descriptors are used to convey additional information and characterize the placement opportunity.

4. Configure segmentation descriptors:

   1. Click the Splice descriptors tab.

   2. Click the Add descriptor button then select SegmentationDescriptor.

   The configuration of all the different fields is user-defined and aligned with the SCTE-35 standard. Some fields can be configured automatically based on the event it is attached to (such as Policy Duration for the segmentation duration).

   

SCTE-35 Rewriting

SCTE-35 signal submitted by an encoder or TS processor can be modified using Prisma.

To configure SCTE-35 rewriting, follow these steps:

1. Make sure that Scheduling mode is set to SCTE-35 Signal-based.

2. Under the Operation tab, set Type to SCTE-35 from the list of available type of operations.

3. Under the Splice info section, check the Use source as template option if you want to keep the SCTE-35 as is, and just modify attached segmentation descriptors for instance. You still have the possibility to override few parameters such as event ID or break duration for splice insert type of commands as show below.

   

4. Uncheck this option if you want to convert an SCTE-35 splice insert into time signal for instance (and vice versa).

   1. Configure splice info: see example below where we assuming that time signal SCTE-35 are received and translated into Splice insert type of command.

      

   2. Modify the incoming SCTE-35 descriptors: go to the Source splice descriptors section then click Add modifier then select whether you want to remove or rewrite segmentation descriptors from the SCTE-35 signal.

      • If you select Remove, configure the filter to identify the segmentation descriptor that needs to be deleted. The figure below shows an example of SCTE-35 rewrite where Prisma deletes the segmentation descriptor of type program start.

        

      • If you select Rewrite, configure the filter to identify the segmentation descriptor to rewrite/modify. Then, under override section, select the field to modify and configure its value.

        

   3. To add segmentation descriptors to the SCTE-35 submitted to Prisma: go to Additional splice descriptors section, click on Add descriptor then select SegmentationDescriptor and configure the segmentation descriptor, either manually, or leveraging pre-defined value (such as splice duration or segmentation duration for instance).

      

Advanced Operation: image overlay

Image overlay operation is used for use cases such as logo insertion. It allows controlling the insertion of an image on top of ongoing video. Parameters such as width, height, and X-Y coordinate must be configured to determine size and position of the image overlay.

To configure image overlay operation, follow these steps:

1. From the Operation tab set the Type to Image overlay.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Duration	Can be manually configured, or automatically configured with Policy duration when selecting trigger point with value At the beginning.
   Material ID	ID of the image on the target device (can be a name like logo.jpg for instance)
   Width	image width, in pixels
   Height	Image height, in pixels
   X	X-horizontal coordinate
   Y	Y-vertical coordinate
   Layer	Specify which layer the image will be positioned on. Up to 8 layers can be managed (7 images overlaying). Elements with higher layers will be displayed on top of others.

3. Click Ok to validate.

   The new operation is added to the list of operations.

Advanced Operation: Animation

When combining Prisma with MediaKind Encoding Live, linear transcoded channel can be combined with Flash animation. Encoding Live embeds a Flash decoding module, enabling composing of Flash animation with the video. Flash animation can be used for:

• Providing crawling functionality (for Emergency Alert System (EAS) application).
• Promoting a service, while keeping the live channel (stretch video, and use space for advertising or promo).

To configure animation type of operation, follow these steps:

1. From the Operation tab set the Type to Animation.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Duration	Can be manually configured, or automatically configured with Policy duration when selecting trigger point with value at the beginning
   Material ID	ID of the Flash SWF object on Encoding Live.
   Layer	Specify which layer the image will be positioned on. Up to 8 layers can be managed (7 images overlaying). Elements with higher layers will be displayed on top of others.
   Fields	Name/value that are MediaKind-specific. A description of the options is given in the table below.

   Parameter	Description
   SWF_TEXT_01	Crawling text that will be passed as a variable by Prisma when controlling Encoding Live to trigger crawling insertion. Example: This is my crawling text
   SWF_SPEED	Crawling speed. Configured value ranges from 1 to n (number of point per frame). Default value is 4.
   SWF_BACK_ALPHA	Background transparency. Value range: [0..1]. Default value is 0.6.
   SWF_COLOR_BACK	Background color of the crawler, using RGB color system. Example: 55A9B0. Default value is no background.
   SWF_COLOR	Text color using RBG system. Example: 55A9B0. Default value is FFFFFF.

   

3. Click Ok to validate.

   The new operation is added to the list of operations.

Advanced Operation: Slate

Prisma can control a target device to enable slate insertion. An obvious use case being global blackout at the encoder, or TS processing component level. Contrary to Image overlay, the underlying live channel is entirely replaced by the slate, either rat the baseband level, or TS level for instance.

To configure slate insertion, follow these steps:

1. From the Operation tab set the Type to Slate.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Duration	Can be manually configured, or automatically configured with Policy duration when selecting trigger point with value at the beginning
   Material ID	ID of the Flash SWF object on Encoding Live.

   

3. Click Ok to validate.

   The new operation is added to the list of operations.

Advanced Operation: Video clip

Prisma can control live to file and file to live video switching using operation type “Video clip”. This operation, like “Image overlay” or “Animation” requires support of such behavior at the target device level.

To configure video clip, follow these steps:

1. From the Operation tab set the Type to Video clip.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Clip	Set to Custom to manually configure the video clip or set to Auto (following SCTE-224) to use material from SCTE-224 viewing policy.
   Duration	Can be manually configured, or automatically configured with Policy duration when selecting trigger point with value at the beginning
   Material ID	ID of the Flash SWF object on Encoding Live.
   Start offset	Offset in seconds the video clip will start playing at. Default value is 0, meaning the video clip will start from the beginning.

   

3. Click Ok to validate.

   The new operation is added to the list of operations.

Scheduling, ESAM properties & Fallback

Scheduling, ESAM properties and Fallback operation tabs are common to all operations.

Please refer to:

• Operation (all): Scheduling configuration
• Operation: ESAM properties
• Operation: Fallback operation

Operation (all): Scheduling configuration

As explained in Translations: Operations, scheduling mode can be automatically set based on media point configuration (using either @matchTime and or @matchSignal attributes), or forced to be time-based or signal-based. In such a case, the Scheduling tab will not appear.

When forcing to Time-based or SCTE-35 signal-based, a Scheduling tab appears to adjust the timing or validity window and matching criteria respectively.

SCTE-35 time-based scheduling mode

To configure Scheduling tab when Scheduling mode is set to Time-based, follow these steps:

1. Configure Time: select among the list of available options:

   • Auto (follow SCTE-224): based on ingested schedule (@matchTime, @effective or @expire attribute of the media point)
   • Match time: force to @matchTime attribute of the media point
   • Effective: force to @effective attribute of the media point
   • Expires: force to @expires attribute of the media point Timing can be adjusted in seconds (positive or negative, for example-30) to launch the operation before or after the time configured in the media point.

SCTE-35 signal-based scheduling mode

When launching operations based on SCTE-35 (submitted by an encoder for instance), a validity window must be configured:

• if the SCTE-35 falls within the window, the operation will be launched,
• otherwise, the operation will be canceled.

To configure the Scheduling tab when Scheduling mode is set to SCTE-35 Signal-based, follow these steps:

1. Go to the Scheduling tab.

2. Activate and select the appropriate value for each parameter.

   Parameter	Description
   Create on alternate service	Prisma allows launching the operation on another service at the same time. Note: This configuration is optional, and reserved for advanced workflow.
   Define stop condition	Define the condition for canceling the ongoing operation (started by startcondition). Restriction: This parameter is only displayed is you selected an ESAM (advanced) operation (see advanced operations table).
   Enable priority	Define the priority at which the signal-based operations should be applied: - If matching criteria are met for one or more signal-based operations, only those with the highest priority will be triggered, 0 being the highest. - If no priority is set all matching signal-based operations will be triggered.

3. Locate the Condition section.

4. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Validity period begin	This setting determines the lower boundary of the validity window period. It can be automatically set based on the mediaPoint configuration (Auto (follow SCTE-224) i.e. equal to @effective if present else @matchTime) or forced to @matchTime, @effective or @expires. Timing can be adjusted in seconds (positive or negative value).
   Validity period end	This setting determines the upper boundary of the validity window. It can be automatically set based on the mediaPoint configuration (Auto (follow SCTE-224) i.e equal to @matchTime + @signalTolerance is present else @expires) or forced to @matchTime or @expires.
   Occurrence	This setting controls the occurrence of the submitted SCTE-35.Possible values: - Auto (follow SCTE-224): Occurrence based on the media point configuration. When @matchTime contains reusable attribute, this means that multiple occurrences are allowed. If not, this is equivalent to enabling occurrence to once. If @matchTime and @matchSignal are configured, this is equivalent to “once with time-based fallback”. - Multiple: allows multiple SCTE-35 occurrence. In other words, if more than one SCTE-35 with matching criteria is received within the validity window, the operation will be launched as many times as there are matching SCTE-35 signals. - Once: this mode allows launching the operation once, and de-activate it. Should other SCTE-35 signal be received within the validity window with matching criteria, the operation will not be triggered. - Once with time-based fallback: launch the operation upon SCTE-35 with matching criteria within the validity window. If no signal is received, the operation will be launched based on time (timing linked to validity period end configuration). - Time-based fallback only: this special mode enables to de-activate the operation when a SCTE-35 signal with matching criteria within the validity period is received. If no signal is received, the operation is forced time-based. Note: When configuring occurrence with Time-based fallback only or Once with time-based fallback, the fallback operation must be configured. This configuration is detailed in Operation: Fallback operation.
   SCTE-35 matching	When the media point configuration contains @matchSignal, SCTE-35 matching can be automatically managed using Auto (follow SCTE-224). This is the case for SCTE-224 ingest, or Disney PCC type of ingest. For other types of ingest like ESNI-I02, no matching criteria are conveyed as part of the schedule. They must then be configured by selecting Custom.

   An example of signal-based scheduling configuration is given in the figure below, where a validity period of 60 seconds surrounding @matchTime is configured, with an Occurrence set to Once, and Custom SCTE-35 matching criteria: only match if time signal and segmentation type ID is set to Program start.

Operation: ESAM properties

When selecting ESAM communication at the Connection tab level, ESAM properties can be configured when configuring the operation.

To configure ESAM properties, follow these steps:

1. Go to the ESAM properties tab.

2. Enter and/or select the appropriate value for each parameter:

   Parameter	Description
   Enable conditioning info	Prisma supports enabling/disabling conditioning info.
   Enable event schedule	Enable repetition of a signal using EventSchedule element in ESAM response.
   Type	EventSchedule supports a choice of two scheduling models: - Absolute start and end UTC times, - Relative (to signal time) start and end offsets
   Interval	Specifies a desired repetition interval for the scheduled signal.
   Start UTC	Note: Available when scheduling type is set to Absolute. Specifies the time to start broadcasting the data as a UTC date and time.
   End UTC	Note: Available when scheduling type is set to Absolute. Optional time to stop broadcasting the data as a UTC date and time.
   Start offset	Note: Available when scheduling type is set to Relative. Specify the time to start broadcasting the data as a duration from the associated/related signal.
   End offset	Note: Available when scheduling type is set to Relative. Optional time to stop broadcasting the data as a duration from the associated/related signal.

   

Operation: Fallback operation

For Signal-based operation, a fallback may need to be configured in case the SCTE-35 signal is not received during the window validity period.

This is crucial for use cases like blackout, where the switch-over is generally done based on SCTE-35. In case this signal does not show up, a fallback mechanism must be put in place to make sure the restriction is being handled properly.

To configure fallback operation, set the following parameters:

1. Define fallback operation: enable or disable operation fallback configuration:

   1. Click the Copy initial operation button to copy the settings from the Operation tab.

   2. If you want to configure a different operation from the one in Operation tab, configuration is fully customizable, providing the user with all the different operations to be triggered as fallback.