Cisco Headend System Release 2.5 Guia Do Desenho

4022455 Rev B 

 

3 

 

This section provides an overview of a direct ADSG environment. It includes various 
concepts and other information to help you understand how to provision direct 
ADSG and CMTS bridge definitions on the DNCS. 

 

In direct ADSG, the CableCARD module parses the DCD file which results in a DSG 
directory. This directory defines the broadcast tunnels (IP addresses and ports) for 
each broadcast tunnel type. The embedded cable modem (eCM) uses these broadcast 
tunnels to transmit broadcast DSG messages (SI, EAS, XAIT, and CDL CVT) directly 
to an ADSG-compliant host device. 

Note: For non-broadcast tunnel data (for example, passthru, BFS), the eCM uses the 
extended channel to pass the DSG flows to the CableCARD module, which then uses 
the command channel for delivery of the data to the host device. 

The logical flow of broadcast tunnel data in an ADSG environment is shown in the 
following diagram. 

 

Direct ADSG can be provisioned in the following environments: 

 

SARA: broadcast data is sent out-of-band from the Broadcast File System (BFS) 
object carousel directly over a CMTS or QPSK bridge directly to host devices 

 

tru2way and other Third-Party Navigators: broadcast data is sent out-of-band 
from a third-party application object carousel (for example, TSBroadcaster) over 
a CMTS or QPSK bridge directly to host devices. For details about third-party 
applications, please refer to the documentation that accompanied the application. 
Note: When provisioning direct ADSG with a third-party application, you must 
link the application to ADSG using the ADSG Application GUI on the DNCS. 
Refer to Defining a Third-Party Application for ADSG (Optional) (on page 12) 
for details.