Cisco Cisco Broadband Access Center for Cable 4.1 Hoja De Datos
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 3 of 4
Product Specifications
BAC-TW uses a distributed architecture for provisioning services on devices. Figure 1 illustrates the components of
the Cisco BAC-TW solution, which include the following:
●
Provisioning API: A flow-through provisioning interface used to integrate the Cisco BAC-TW system with
service providers
’ client programs, such as workflow applications and billing systems. Integration is
implemented through a Java client library that service providers
’ client programs use to drive tiered-service
selection and to trigger device activation on their networks. The client library reduces the need to develop
integration code and facilitates integration with web-based user interfaces.
Figure 1. Cisco BAC-TW Deployment Blueprint
●
RDU: The primary server in the Cisco BAC-TW system, the regional distribution unit performs the following
functions:
◦
Manages the generation of all configurations
◦
Maintains the authoritative database
◦
Represents the central point through which all API requests must pass
◦
Supports external clients, OSSs, and other provisioning functions through the provisioning API
●
DPE: The Cisco DPE server that manages devices directly. The DPEs are grouped in regional clusters for
redundancy. Multiple clusters facilitate BAC-TW scalability. The Cisco DPE manages the following:
◦
Device communication over CWMP
◦
Firmware download over HTTP/HTTPS
◦
Caching of device instructions, indicating how BAC-TW will interact with a device when the devices starts
a CWMP session with BAC-TW