Functionality; Use Case Configuration Examples - Imagine communications Selenio BNP 2xr User Manual

ETV Binary Interchange Format

Functionality

ETV is interpreted by a User Agent: a software application that runs on the set-top box that is installed
remotely by the MSO.
When ETV is downloaded to the STB, it uses a pairing of data elementary streams, which consist of the
following:
ETV Binary Interchange Format (EBIF) data ES — carries the application data.
•
ETV Integrated Signaling Stream (EISS) data ES — carries timing signals that trigger events
•
associated with the application.
ETV applications are typically "bound" (or Pre-bound) to particular pieces of content, and packaged in
a program together with video and audio while being broadcast to the STB. This content can be a 30-
second ad or a network stream (a dedicated channel or program with EBIF content coded into it).
Another possible source of ETV data is a local EBIF streamer: a server that provides pre-packaged EBIF
content, allowing the BNP to enhance a video or audio program (network stream or ad) with additional
ETV data. The process of adding EBIF enhancement to an existing network stream or ad is referred to as
Late-binding.
Figure 169 shows the basic ETV data source flow.
Figure 169. ETV EBIF Data Source flow
Sat. Receiver
Sat. Receiver

Use Case Configuration Examples

The BNP can groom, splice or filter ETV data streams, including, but not limited to, the Use Case
examples listed below:
Pre-Bound Ad
1.
Pre-Bound EBIF Passthrough (no
2.
Pre-Bound EBIF
3.
Pre-Bound EBIF Passthrough and Keep During Ad
4.
Pre-Bound Network EBIF; Late-Bind EBIF During
5.
Selenio TM BNP User Guide, Release 3.7.1
- Functionality
DPI Pump
DPI Pump
Ad Insertion
Broadcast
BNP
BNP
Local EBIF
Local EBIF
Streamer
Streamer
Splice.
DPI).
Drop.
Output Mux
QAM
QAM
Splice.
Ad.
STB
STB
237