Cisco Cisco Broadband Access Center for Cable 4.1 Data Sheet
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 2 of 4
●
Extendable technology support: Cisco BAC supports DOCSIS cable modems and set-top boxes for high-
speed data provisioning, PacketCable voice provisioning of media termination adapters (MTAs) and
DOCSIS cable modems. It also can be extended to support other Dynamic Host Configuration Protocol
(DHCP)-based devices, including non-DOCSIS cable modems.
Table 1 outlines the features and benefits of Cisco BAC.
Table 1.
Cisco Broadband Access Center Features and Benefits
Feature
Benefit
Full support for Linux and Cisco
Unified Computing System (UCS)
(New!)
Unified Computing System (UCS)
(New!)
Red Hat Enterprise Linux 5 and Cisco UCS support is now extended to all components of BAC product
including RDU and KDC. This feature completes Red Hat Enterprise Linux 5 and Cisco UCS support for
BAC.
including RDU and KDC. This feature completes Red Hat Enterprise Linux 5 and Cisco UCS support for
BAC.
Integrated Kerberos Protocol
server (KDC) for PacketCable voice
service provisioning
server (KDC) for PacketCable voice
service provisioning
Provides a single platform with all the necessary security components for PacketCable provisioning
Linux and Cisco Unified Computing
System (UCS) support for
provisioning group
System (UCS) support for
provisioning group
Red Hat Enterprise Linux 5 and Cisco UCS support for provisioning group components - DPE, Cisco
Network Registrar (CNR) DHCP, and Cisco CNR DNS.
Network Registrar (CNR) DHCP, and Cisco CNR DNS.
DOCSIS 3.0 and IPv6 support
DOCSIS 3.0 channel-bonding allows increased data speed for subscribers. Support for IPv4 and IPv6
cable modems and IPv4/IPv6 mixed device environment.
cable modems and IPv4/IPv6 mixed device environment.
Distributed architecture with high
availability and disaster recovery
availability and disaster recovery
Offers true scalability, failover, and high reliability to manage a growing subscriber base while helping to
ensure minimum subscriber service disruption. Allows a simple way to extend provisioning to additional
subscribers and new markets; dramatically simplifies capacity upgrade and maintenance costs and
complexity. Distributed provisioning engines allow you to put them in different datacenters for disaster
recovery.
ensure minimum subscriber service disruption. Allows a simple way to extend provisioning to additional
subscribers and new markets; dramatically simplifies capacity upgrade and maintenance costs and
complexity. Distributed provisioning engines allow you to put them in different datacenters for disaster
recovery.
Java-based provisioning API
Provides easy integration to customer OSS, billing, or workflow and mediation software
Scripting Interface with templates
Templates offer an easy way for reducing the number of configuration files and decreasing operational
costs. The BAC scripting interface provides more flexibility for managing templates parameters and an
automated way for deploying templates.
costs. The BAC scripting interface provides more flexibility for managing templates parameters and an
automated way for deploying templates.
Technology extensions
Provides an easy means to extend this single platform to provision new devices and technologies to meet
changing network and subscriber requirements
changing network and subscriber requirements
PacketCable compliant
Supports PacketCable 1.0, 1.1, and 1.5 for complete end-to-end IP voice service provisioning and meets
all PacketCable security specifications
all PacketCable security specifications
Dynamic DOCSIS file generation
Offers a means to build unique DOCSIS files for individual subscriber devices to meet needs of tiered
service provisioning and true IP voice requirements
service provisioning and true IP voice requirements
Safe failover
High uptime and service reliability through DPE and DHCP failover as well as TFTP redundancy
Product Specifications
Cisco Broadband Access Center uses a distributed architecture for provisioning services on broadband devices.
Figure 1 illustrates the components of the Cisco BAC solution, which include the following:
●
Provisioning API: A flow-through provisioning interface used to integrate the Cisco BAC system with service
prov
iders’ 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.
●
RDU: The primary server in the Cisco BAC system. It 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