Cisco Cisco Packet Data Gateway (PDG)
HNB Gateway in Wireless Network
Features and Functionality - Base Software ▀
HNB-GW Administration Guide, StarOS Release 18 ▄
45
10k UEs per HNB support
To support Spider Cloud SNs which aggregate many HNBs to what appears to the HNBGW as a single HNB, 10K UEs
support per HNB is required. This will require scaling up and optimization of some data structures.
support per HNB is required. This will require scaling up and optimization of some data structures.
Functional description
HNBGW supports registration of a maximum of 10K UEs per HNB in case of an HNB aggregator.
Even though fewer number of HNBs need to be supported on the HNBGW, the number of UEs supported should
remain the same.
HNBGW supports simultaneous registrations from normal HNBs as well as HNB aggregators, even though
different hnbgw-services are configured for each type of HNB.
HNBGW assigns system resources appropriately for HNBs and HNB aggregators to avoid unusual behavior on
HNBGW.
No separate license is required for HNB aggregators. HNBs and HNB aggregators will be assigned the same unit
of license.
Assumptions & Limitations
Below are the assumptions for the 10K UE support feature.
HNBGW assumes that an HNB aggregator can have a maximum of 10k UEs behind it. The maximum value supported for
max-registered-ues-per-hnb when HNB-Aggregation is enabled is 10k.
max-registered-ues-per-hnb when HNB-Aggregation is enabled is 10k.
One hnbgw-service can support only one kind of HNB. Therefore, if we want to support both normal HNBs and HNB
aggregators, we need to use a different hnbgw-service for each.
aggregators, we need to use a different hnbgw-service for each.
If state of HNB-Aggregation is changed from enabled to disabled or vice-versa, or value of max-registered-ues-per-hnb is
changed. Then all the HNBs and UEs registered to that service will be deregistered after confirmation.
changed. Then all the HNBs and UEs registered to that service will be deregistered after confirmation.
On IPNE interface HNBGW will continue to report only 32 UEs per HNB in the query response.
The response of “show hnbgw sessions full all” will display a maximum of 12k UEs per HNB only even If the HNB has
more UEs than that due to emergency calls.
more UEs than that due to emergency calls.
Hybrid and ACL Phase I support
HNBGW Hybrid support feature returns membership status of the UE in the UE Register accept message with respect to
the HNB.
the HNB.
With HNBGW Hybrid and ACL Phase I support HNBGW returns the membership status of the UE with respect to the
HNB in the UE Register accept message. Also max length of the list of IMSI (white-list) representing the UEs that can
register with an HNB is increased to 150 from 27.
HNB in the UE Register accept message. Also max length of the list of IMSI (white-list) representing the UEs that can
register with an HNB is increased to 150 from 27.
Overview
This feature provides the UE a means to know its CSG membership status in case of hybrid mode HNB. It also provides
means for HNBs to have higher number of registered members and provides mechanism to RMS to dynamically change
the white-list of a particular HNB. Maximum number of 150 UE/members which are part of the whitelist can register
with an HNB now based on the ‘max-registered-ue’ and ‘configured value’ because at a time the max number of UE
that can be registered at HNBGW is a configurable parameter and it can vary based on the configured value. So it is
independent of the whitelist length. All the IMSIs part of ACL of an HNB can be sent in multiple whitelist in the same
Access accept by the Radius server. So HNBGW shall be able to handle multiple IMSI whitelist received in Access
accept or “change of authorization” message.
means for HNBs to have higher number of registered members and provides mechanism to RMS to dynamically change
the white-list of a particular HNB. Maximum number of 150 UE/members which are part of the whitelist can register
with an HNB now based on the ‘max-registered-ue’ and ‘configured value’ because at a time the max number of UE
that can be registered at HNBGW is a configurable parameter and it can vary based on the configured value. So it is
independent of the whitelist length. All the IMSIs part of ACL of an HNB can be sent in multiple whitelist in the same
Access accept by the Radius server. So HNBGW shall be able to handle multiple IMSI whitelist received in Access
accept or “change of authorization” message.