Cisco Cisco Broadband Access Center for Cable 5.0
C H A P T E R
6-1
Cisco Broadband Access Center for Cable Administrator’s Guide
OL-2445-02
6
Configuring and Using the Sample User Interface
The Broadband Access Center for Cable (BAC) Sample User Interface (SUI) provides you with a sample
user interface for both self- and pre-provisioning. The SUI can demonstrate the basic functionality of
BAC in lab testing scenarios. In full BAC deployments, SUI functionality is expected to be provided by
billing, OSS, and/or workflow applications.
user interface for both self- and pre-provisioning. The SUI can demonstrate the basic functionality of
BAC in lab testing scenarios. In full BAC deployments, SUI functionality is expected to be provided by
billing, OSS, and/or workflow applications.
What is the Sample User Interface?
BAC provides a sample workflow application that manages the automated provisioning of devices on
the network, and an administrator interface that gives basic functions to those who manage the accounts
that are maintained in BAC.
the network, and an administrator interface that gives basic functions to those who manage the accounts
that are maintained in BAC.
In the SUI, data is managed in two distinct ways: registration of devices on the network and the
accounting of results from those registrations. For example, pages that permit the complete
self-provisioning of new cable modems, using credit card information, must be capable of handling the
automated billing for services along with device tracking. While the SUI does not track accounting
information, it allows each device to be associated with an owner identifier (Owner ID). For example,
the association with an Owner ID allows objects stored in BAC, to be related to external objects such as
billing account systems. In this sample workflow, the Owner ID is used as the account number, but is
not actually related to any external data. The Owner ID associated on device objects in BAC can be any
external string used to group devices.
accounting of results from those registrations. For example, pages that permit the complete
self-provisioning of new cable modems, using credit card information, must be capable of handling the
automated billing for services along with device tracking. While the SUI does not track accounting
information, it allows each device to be associated with an owner identifier (Owner ID). For example,
the association with an Owner ID allows objects stored in BAC, to be related to external objects such as
billing account systems. In this sample workflow, the Owner ID is used as the account number, but is
not actually related to any external data. The Owner ID associated on device objects in BAC can be any
external string used to group devices.
The SUI uses shortcuts to provide an interface that can support such functions as accounting, without
actually needing an external accounting entity. Accounting information is stored on the modem object
as custom properties. When viewing an account, the modem is found using the Owner ID and then the
account data is retrieved from the modem.
actually needing an external accounting entity. Accounting information is stored on the modem object
as custom properties. When viewing an account, the modem is found using the Owner ID and then the
account data is retrieved from the modem.
BAC supports two distinct methods of managing devices: the Standard mode and the Promiscuous mode.
•
In the Standard mode, modems and computers are tracked individually.
•
In the Promiscuous mode, only the modems are tracked regardless of how many computers may
exist on the other side of the modem. When Promiscuous mode is enabled, computers only receive
access if they are behind a provisioned modem.
exist on the other side of the modem. When Promiscuous mode is enabled, computers only receive
access if they are behind a provisioned modem.