Table of Contents
Advertisement
▀ How HNB-GW Works
5. On reception of RANAP Iu Release Complete command in SCCP-DATA-FORM1 Response message from
HNB-GW, CN sends SCCP-RELEASED message to HNB-GW and triggers the associated SCCP connection.
On reception of SCCP-RELEASED message from CN, the HNB-GW sends RUA-DISCONNECT message to
HNB and disconnect the IuH connection with HNB.
6. After successful completion of RUA-DISCONNECT procedure and IuH connection release, HNB-GW sends
SCCP-RELEASE-COMPLETE message to CN and HNB-GW confirms the IuPS/IuCS connection released
between HNB-GW and CN.
Paging and Serving RNS Relocation Procedures
This section describes the call flow for network-initiated paging and SRNS relocation procedures on HNB-GW.
Following procedure call flows are described for Paging and SRNS relocation procedures between HNB, HNB-GW,
and SGSN/MSC in core network:
Paging Procedure
SRNS Relocation Procedure
Paging Procedure
This procedure is applicable for establishment of IuH and IuPS/IuCS connection between HNB to HNB-GW and HNB-
GW to SGSN/MSC in core network.
The following text describes the call flow for Paging procedure on HNB-GW:
1. HNB-GW receives Paging from SGSN/MSC. HNB-GW finds out if any UE is registered with that IMSI.
2. If a UE is registered then HNB-GW sends the Paging message to the HNB through which the UE is registered.
3. If no registered UE is found then HNB-GW finds out the list of HNBs which have IMSI received in the message
in their respective Whitelist.
4. If one or more HNBs were found, and Paging message contained LAI, then HNB-GW compares the HNB's
PLMN-ID and LAC values against LAI received in the Paging. The HNB which do not have matching values
is dropped from this list.
5. If one or more HNBs were found, and Paging message contained RAI, then HNB-GW compares the HNB's
PLMN-ID, LAC and RAC values against RAI received in the Paging. The HNB which do not have matching
values is dropped from this list.
6. If Paging message did not have Paging-area then list of HNBs is same as what was found in step 1 otherwise list
of HNBs is as found in step 2 or step 3.
If this list is empty then Paging message is dropped. Otherwise HNB-GW sends Paging message to these
HNBs.
SRNS Relocation Procedure
This procedure is applicable for intra-CN or inter-CN handover procedure between HNB to HNB-GW and HNB-GW to
SGSN/MSC in core network.
The following text describes the call flow for SRNS relocation procedure on HNB-GW:
1. HNB-GW receives Relocation-Request from SGSN/MSC in case subscriber moves from Macrocell to Femtocell
in a connected mode.
2. If the request does not contain IMSI (i.e. for an emergency call), HNB-GW sends Relocation-Request-Reject
with an appropriate cause.
3. . If the request contains IMSI, HNB-GW finds the list of registered HNBs which have this IMSI in their white-
list. If there is no such HNB found, HNB-GW sends Relocation-Request-Reject with appropriate cause.
▄ Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
48
HNB Gateway in Wireless Network
OL-25069-03
Advertisement
Table of Contents
