Cisco Cisco Packet Data Gateway (PDG)
HNB Gateway in Wireless Network
▀ How HNB-GW Works
▄ HNB-GW Administration Guide, StarOS Release 16
50
Figure 8.
UE Registration Call Flow for Non-CSG UEs or Non-CSG HNBs
1. Upon camping on the HNB, the UE initiates an initial NAS procedure (e.g. LU Procedure) by establishing an
RRC connection with the HNB. UE capabilities are reported to the HNB as part of the RRC Connection
establishment procedure.
establishment procedure.
2. The UE then transmits a RRC Initial Direct Transfer message carrying the initial NAS message (e.g. Location
Updating Request message) with identity (IMSI or TMSI).
3. The HNB checks UE capabilities provided in step 1, if these indicate that CSG is not supported and if the
identity of the UE (provided during RRC Connection Establishment) is unknown at the HNB being accessed,
i.e. no Context id exists for the UE, the HNB initiates UE registration towards HNB-GW (step 6-8).
i.e. no Context id exists for the UE, the HNB initiates UE registration towards HNB-GW (step 6-8).
4. Before starting the UE Registration procedure, HNB optionally triggers the Identification procedure asking for
the UE IMSI, if such identity is not provided during the RRC Connection Establishment. If the HNB has a
context id for the UE, the UE registration procedure is not performed nor the Identification procedure.
context id for the UE, the UE registration procedure is not performed nor the Identification procedure.
5. The HNB may optionally perform access control based on IMSI and provided access control list.