Cisco Headend System Release 2.5 用户指南
4011043 Rev B
Introducing Cisco’s OCAP Object Carousel Solution:
1-5
The TSBroadcaster
OCAP Object Carousel Acronyms and Terms, Continued
Term
Description
Model
A model is the saved TSBroadcaster configuration. The
model is a representation of the configuration choices you
made through the GUI. You can retrieve models containing
development configurations, demonstrations, and test cases
to be swapped in and out as often as necessary.
A model contains all the information needed to perform its
A model 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
Module
A module is a physical data block that is used to broadcast
file and directory data. The physical size limitations for a
module are 64KB for a module containing multiple files and
1MB for a module containing a single file.
Object Carousel
The Object Carousel works like the Broadcast File Server in
delivering data. In a TSBroadcaster system, you can have
both an Object Carousel and a Broadcast File Server or one or
the other. The descriptors for the transport streams are
different depending upon the device.
Player
A player takes a TSBroadcaster build and turns the data into
a stream. You can use a player for inband and system
information (SI) data. The player is used for locally managed
content.
The player is a process that runs on the server. The player
The player is a process that runs on the server. The player
sends the data over TXmux using an Ethernet connection.
Role
A TSBroadcaster server will only operate if it has been
assigned a role. A role is essentially the name of the job that
the server is performing. The actual value of the role does not
matter for a standalone server.