Cisco Cisco D9896 4 2 2 10-Bit AVC Decoder Data Sheet
Description
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.
DPI is used to signal local ad insertion or
local program insertion from broadcasters
and programmers to receive 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.
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.
In addition to logging received messages, the Event Logger also provides detailed decoding for DPI
messages according to the SCTE-35 standard. This feature allows uplink operators to view all contents of
SCTE-35 Start and Stop messages to assist receive sites in diagnosing headend configuration issues, without
having to refer to a protocol analyzer.
The Event Logger is system agnostic, allowing it to
monitor, correlate and log DPI messages in Cisco
PowerVu
(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 receive 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.
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.
In addition to logging received messages, the Event Logger also provides detailed decoding for DPI
messages according to the SCTE-35 standard. This feature allows uplink operators to view all contents of
SCTE-35 Start and Stop messages to assist receive sites in diagnosing headend configuration issues, without
having to refer to a protocol analyzer.
The Event Logger is system agnostic, allowing it to
monitor, correlate and log DPI messages in Cisco
PowerVu
®
and ROSA
®
systems, as well as
encoding and decoding solutions from third party
vendors.
vendors.
Features
•
108 GPI contact sensors
•
6 ASI inputs
•
SPTS and MPTS support
•
Detailed decoding of SCTE-35 messages
• Data
archiving
• Real-time and offline operation
Event
Logger