Manual

Flows
A high level message sequence diagram below explains the overview of the new feature and exchanges of
messages between different involved network entities:
Figure 8: Hybrid and ACL Call Flow with Involved Networks
1
To register an HNB with HNBGW, (1) HNB register request is sent by HNB to HNBGW. HNB sends
HNB-ID to identify itself with the HNBGW. Upon receiving the register request HNBGW authenticates
the validity of HNB with RADIUS server by sending (2) Radius Access Request.
2
If HNB is found valid then RADIUS will server send the IMSI white-list for the requested HNB. One
HNB can have max of 150 IMSI in its white-list, to send 150 IMSI, 6 white-list will be send in (3) Radius
Access Accept.
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.
4
The corresponding SESSMGR at HNBGW then sends HNB register accept to HNB.
HNB-GW Administration Guide, StarOS Release 19
37
HNB Gateway in Wireless Network
Hybrid and ACL Phase I support