Manual

9
HNB sends UE Registration request with UE Identity as IMSI to HNBGW. HNBGW is considering that
it always receives UE Registration Request with IMSI. MOCN will work even if IMSI is not received;
only that re-routing load will increase.
10
HNBGW performs access control on the UE Registration request and sends UE Registration Accept if
successful.
11
HNB prepares Initial UE Message with LAI as Common PLMN C + CN LAC "Y", It also populated
Selected PLMN Identity received from the UE. The message is forwarded to HNBGW.
12
HNBGW reads the selected PLMN Identity from the Initial UE message. This is supported UE. Based on
the received PLMN Identity request is forwarded to CN1.
13
MSC/CN1 sends the Location Update Accept with LAI as "PLMN A + LAC Y". As UE is supporting
MSC assigns its own PLMN and not common PLMN.
14
HNBGW forwards the message to HNB.
15
If CN and OTA LAC are different HNB changes the LAC in Location Update Accept.i.e. PLMN A +
LAC "Z".
Network Sharing - HNB with MOCN, CN with MOCN, non-supporting UE Re-Routing
Figure 6: Network Sharing - HNB with MOCN, CN with MOCN, non-supporting UE Re-Routing
In this scenario HNB supports MOCN. CN also supports MOCN. HNB broadcasts common PLMN and PLMN
List as well. Non-Supported UEs are able to read only Common PLMN.
HNB-GW Administration Guide, StarOS Release 19
32
HNB Gateway in Wireless Network
Multi-Operator Core Network (MOCN)