Filter
Top Products
4-18
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 4 CPE Management Overview
Initial Provisioning Flows
Note With no preregistered device data available, the chances of a Denial of Service attack increase, as
unknown devices are not authenticated.
Initial Provisioning Flows
This section describes the configuration workflow for a device, which differs based on whether a device
is preregistered or unregistered.
Figure 4-2 shows a common initial configuration flow.
Figure 4-2 Initial CPE Configuration Workflow
For Preregistered Devices
a. From the Cisco BAC API, the RDU is populated with specifically defined configurations and rules
for various types of devices. The device is preconfigured and associated with a Class of Service.
b. The preregistered device finds its provisioning group by contacting the Cisco BAC server at a
preconfigured URL, and initiates autoprovisioning with provisioning group servers (DPEs).
c. The RDU generates instructions appropriate for the device. The resulting device instructions direct
DPE responses to various CPE protocol events, such as a TR-069 Inform and an HTTP file request.
System Operator
Populate Provisioning
Rules
RDU Provisioning Group CPE
Add CPE (optional)
Deliver Instruction Set
CPE Makes Protocol X response
Yes, Send Protocol X response
Do I have Instructions?
158331
Generate Instruction
Set
Store Discovered
Data