Cisco Cisco Broadband Access Center Telco Wireless 3.8 發佈版本通知

下载
页码 10
 
4
Cisco Broadband Access Center 3.8.1 Release Notes
OL-27175-02
  New Features in Cisco BAC 3.8.1
The below properties are used to add DNPrefix:
/IPDevice/cpeAlarm/prefixFaultMOI 
/IPDevice/cpeAlarm/prefixDeviceProp 
These properties should be configured on the device hierarchy level and are also available in 
/IPDevice/properties/available/pg property.
Construction of DNPrefix
BAC supports construction of DNPrefix (FC-DN-PREFIX) based on a new custom property, 
FC-DN-PREFIX-FORMAT.
FC-DN-PREFIX-FORMAT supports any property, including discovered data. You can configure value 
for this property for constructing DNPrefix. 
Modified UMTS Flow
BAC provides an option to configure list of RAT for which provisioning flow should wait for location 
check. This feature assumes that the device may support 2G, 3G or 4G REM scans, for location 
verification methods. The DPE script extension looks for 2G, 3G and 4G lastscantime parameters based 
on the configurations.
This affects the following LV (Location Verification) methods:
EDN
DNL
DNM
DNB
BAC provides the following configuration for each RAT, which you can set on the device record using 
the Admin UI.
FC-2G-REM-SCAN - Defualt value is true
FC-3G-REM-SCAN - Defualt value is true
FC-4G-REM-SCAN - Defualt value is false
The provisioning flow waits for REM scan only for those RAT for which you have configured the value 
as true. For location verification methods, the extension looks for 2G, 3G and 4G lastscantime 
parameters based on the configurations in the inform message.
PAR changes to Push Grid ID to HNB gateway
BAC provides USC Access Point grid ID to the HNB-Gateway in AAA RADIUS Access-Accept. 
BAC constructs grid ID by combining Enterprise ID, Site ID and Group ID. 
The BAC extension in Prime Access Registrar (PAR) performs an "authenticate" request against the 
DPE, passing along the RADIUS request data. The DPE provides an HTTPS based interface to support 
authentication and authorization. 
The DPE will pass the request to an internal authentication/authorization extension mechanism which 
will perform the checks such as running a lease query. This returns back any formatted data such as the 
white-list and Grid-ID, if the authenticate requests passes both authentication and authorization.