Table of Contents
Advertisement
▀ How HNB-GW Works
HNB Identity: the HNB has a globally unique and permanent identity.
HNB Operating Parameters: Such as the selected LAC, RAC, SAC, etc.
6. The HNB-GW uses the information from the HNB-REGISTER-REQUEST message to perform access control
of the HNB (e.g. whether a particular HNB is allowed to operate in a given location, etc). If the HNB-GW
accepts the registration attempt the PLMN-ID received in the request shall be used to lookup the PLMN to
RNC id mapping table and corresponding RNC-ID shall be returned in the HNB-REGISTER-ACCEPT
message else the HNB-GW may reject the registration request (e.g. due to network congestion, blacklisted
HNB, unauthorized HNB location, etc). In reject case, the HNB-GW shall respond with a HNB-REGISTER-
REJECT indicating the reject cause.
Important:
UE Registration Procedure
This section describes the UE registration procedures for HNB provides means for the HNB to convey UE identification
data to the HNB-GW in order to perform access control for the UE in the HNB GW. The UE Registration also informs
the HNB-GW of the specific HNB where the UE is located.
The UE registration procedure generally triggers when the UE attempts to access the HNB through an initial NAS
message and there is no context id in the HNB for specific UE.
UE Registration procedure is described for following scenarios:
UE Registration Procedure of Non-CSG UEs or Non-CSG HNBs
UE Registration Procedure of Non-CSG UEs or Non-CSG HNBs
This procedure is applicable for non-CSG UEs or HNBs.
The following figure and the text that follows describe the message flow for UE registration procedure of Non-CSG
UEs or Non-CSG HNBs:
▄ Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
42
Internet connectivity information (e.g. IP address).
The HNB shall start broadcasting only after successful registration with the HNB-GW.
HNB Gateway in Wireless Network
OL-25069-03
Advertisement
Table of Contents
