Cisco Cisco Packet Data Gateway (PDG)
HNB Gateway in Wireless Network
Features and Functionality - Base Software ▀
HNB-GW Administration Guide, StarOS Release 18 ▄
47
3. Upon receiving (3) Radius Access Accept, the corresponding session manager at HNBGW reads all the white-
list and store the IMSI as part of the HNB record. It also sends the HNB details to HNB manager. There is no
change in the existing data structure or FSM of SESSMGR and HNBMGR to handle increased number of IMSI
per HNB.
change in the existing data structure or FSM of SESSMGR and HNBMGR to handle increased number of IMSI
per HNB.
4. The corresponding SESSMGR at HNBGW then sends HNB register accept to HNB.
5. Now to initiate a PS or CS call, UE first initiates LA update (IMSI attach) for CS network or Attach Request
5. Now to initiate a PS or CS call, UE first initiates LA update (IMSI attach) for CS network or Attach Request
(GPRS attach) for PS network. This triggers the HNB to initiate (6) UE register request towards HNBGW.
HNB passes UE IMSI in the (6) UE register request to HNBGW.
HNB passes UE IMSI in the (6) UE register request to HNBGW.
6. In case of Hybrid mode, the corresponding SESSMGR at HNBGW if finds the IMSI matching one of the IMSI
in the IMSI list of concerned HNB then (7) UE Register Accept with CSG membership status as “member”
otherwise “non-member” is sent to HNB. After successful UE registration NAS signaling and data exchange
will be carried out indicated in (8) in the above figure
otherwise “non-member” is sent to HNB. After successful UE registration NAS signaling and data exchange
will be carried out indicated in (8) in the above figure
7. If there is an update in the ACL(IMSI list) of an HNB at RMS then RADIUS sever at RMS sends the updated
ACL in the (9) “change of authorization” message of Radius protocol. HNBGW respond backs to RADIUS
server with (9a) COA ack.
server with (9a) COA ack.
8. In case of hybrid mode, for any (10)(11) new UE registration the updated IMSI list will be checked to see its
CSG membership status and accordingly (12) UE Register Accept will be sent to the HNB.
IURH HNB Configuration Transfer
HNBGW supports Femto-to-Femto handover using the SRNS-Relocation, which involves the Core-Node entities, and a
direct Iurh-based handover, which doesn't involve the Core-Node entities.
direct Iurh-based handover, which doesn't involve the Core-Node entities.
For direct IURH connectivity, HNB should know the details of other HNBs to communicate, like the IURH interface IP
address. To achieve the same, a new HNBAP procedure HNB Configuration Procedure is added in the specifications.
An addition of IURH TNL IP address of HNB in HNBAP HNB registration Procedure helps the HNBGW to build the
knowledge of IURH interface IP address of HNBs. And the HNB Configuration Transfer Procedure helps to convey this
information to HNBs who require it.
address. To achieve the same, a new HNBAP procedure HNB Configuration Procedure is added in the specifications.
An addition of IURH TNL IP address of HNB in HNBAP HNB registration Procedure helps the HNBGW to build the
knowledge of IURH interface IP address of HNBs. And the HNB Configuration Transfer Procedure helps to convey this
information to HNBs who require it.
Architecture
Below diagram describes the architecture of IURH HNBG Configuration Transfer.