Cisco Headend System Release 2.5 User Guide

1-14 

Introducing Cisco’s OCAP Object Carousel Solution: 

4011043 Rev B 

 

The TSBroadcaster 

 

The TSBroadcaster System View, Continued 

The TSBroadcaster Server component maintains a model that contains all the 

information needed to perform its function: 
• 

Transport Stream definitions 

• 

Applications to be played out  

• 

Schedule for application playout 

• 

Players allocated for Transport Streams 

• 

Application update polling instructions 

• 

User account information 

The TSBroadcaster handles all transactions initiated by clients through the HTTP 

interface. The server may modify the model and its own configuration in response to 

the transactions. 
The component launches processes to poll HTTP and FTP data sources to check for 

application data updates.  The component includes a process that builds the 

Transport Stream and updates it in response to: 
• 

Application playouts starting and stopping 

• 

Updates to application data files 

• 

Changes in the model 

 

When a Transport Stream is built or updated, the new data is sent via TCP/IP to one 

or more TSPlayers that are nominated to play out the Transport Stream. 
TSBroadcaster Servers may be configured to operate in dual-redundant mode with a 

partner, in which case they cross-monitor each other. The component maintains an 

event log and an archive of all the Transport Streams it has built. 

The TSPlayer Server component plays out the Transport Stream built by the 

TSBroadcaster Server, incorporating updates as they become available. The 

component maintains an event log. 

The TSMux component receives a continuous stream of data from the TSPlayer 

server and sends it out through an ASI interface. If directed, the TSMux will 

multiplex in locally stored A/V content. The component maintains an event log.