1-8
Cisco Building Broadband Service Manager 5.1 Software Configuration Guide
OL-1566-01
Chapter1 Introduction
Access and Accounting Components
7. Configure BBSM to allow control and management of access codes. Refer toChapter 8, “BBSM
Access Code Management.”
8. Configure BBSM for RADIUS accounting. Refer to Chapter 9, “RADIUS Authentication,
Authorization and Accounting.”
9. Configure BBSM for port hopping. Refer to Chapter 10, “BBSM Port Hopping.”
10. Install any Service Packs or Patches using WEBpatch. Refer to Chapter 11, “WEBpatch Utility.”
Caution In addition to the basic configurationdetailed in Chapters 2 and 3, your system can require additional
installationand configuration processes as explained in Chapters 4 through 11 of this manual. Be sure
to complete the necessary procedures in those chapters before attempting to offer Internet service to
end users.
Access and Accounting Components
There are two components you must consider when defining your configuration:
•Access policy
•Accounting method

Access Policy

An access policyis on a per-port basis, where a port allows an end user to connect to BBSM. It is through
the selection of an access policy that the characteristics of a port connection are specified. In doing so,
the end user’s Internet experience is defined when they use BBSM by selecting an access policy.
BBSM includes default, built-in access policies as shown in the list that follows. Your web developer
can add new access policies to the system using the BBSM Software Developer’s Toolkit (SDK).
Access policies include:
•Access Code
To gain Internet access, the end user enters an Access Code created by an administrator.
The access code is valid for a finite time period as specified by the administrator. After the access
code expires, the end user cannot activate a new session. Depending on the page set, the code can
beexclusive, allowing only one end user at a time to use it, or it can be non-exclusive, allowing many
users to use the code at the same time.
•Block
End User purchases Internet access in a block of time, specified in minutes.
If the end user terminates the session prior to the block expiration, unused minutes are forfeited.
Otherwise, BBSM deactivates the session automatically at the end of the block.
•Daily
End User purchases time on a 24-hour basis. The 24-hour period is based on either a site-wide start
time, or 24 hours from session start.