Cisco Cisco Live Event Controller Data Sheet
Data Sheet
Page 1 of 3
Cisco Event Logger
Product Overview
The Event logger is used by Programmers and Broadcasters to monitor and log digital
program insertion (DPI) messages, allowing them to verify correct and timely
transmission of the signals via a satellite distribution system.
program insertion (DPI) messages, allowing them to verify correct and timely
transmission of the signals via a satellite distribution system.
DPI is used to signal local ad insertion or local program insertion from broadcasters and
programmers to receiving sites such as cable MSOs and IPTV headends. DPI is
generally signalled from the satellite uplink, and normally terminates in splicers at the
headend, where ads from ad servers or programs from alternate sources are spliced into
the stream. Headends may be financially impacted if a DPI avail is not fulfilled and a
local ad or program is missed. As a result, if programmers and broadcasters do not see
a DPI event take place, they often ask the uplink owner to verify that DPI signals were
actually sent.
programmers to receiving sites such as cable MSOs and IPTV headends. DPI is
generally signalled from the satellite uplink, and normally terminates in splicers at the
headend, where ads from ad servers or programs from alternate sources are spliced into
the stream. Headends may be financially impacted if a DPI avail is not fulfilled and a
local ad or program is missed. As a result, if programmers and broadcasters do not see
a DPI event take place, they often ask the uplink owner to verify that DPI signals were
actually sent.
Figure 1.
Event Logger view
The Event Logger provides a means of monitoring, correlating, and logging DPI triggers
and the resulting DPI messages. General purpose inputs (GPIs) on video encoders,
used to trigger SCTE-35 message generation, are monitored by the Event Logger.
Configured GPI state changes indicate to the Event Logger that a specific DPI message
is now expected. The Event Logger then watches the ASI output of a monitoring receiver
to look for the expected SCTE-35 message. If the message is not received within a given
time period, the Event Logger flags it as a missed event. If the message does arrive
within the given time period, it is correlated to the configured GPI and logged as a
matched event. Results are logged in real time and archived for record-keeping
purposes.
and the resulting DPI messages. General purpose inputs (GPIs) on video encoders,
used to trigger SCTE-35 message generation, are monitored by the Event Logger.
Configured GPI state changes indicate to the Event Logger that a specific DPI message
is now expected. The Event Logger then watches the ASI output of a monitoring receiver
to look for the expected SCTE-35 message. If the message is not received within a given
time period, the Event Logger flags it as a missed event. If the message does arrive
within the given time period, it is correlated to the configured GPI and logged as a
matched event. Results are logged in real time and archived for record-keeping
purposes.