Manual

Each TAIDB list associated for a logical EnodeB shall be configured with only one PLMN. If operator
has multiple PLMNs then, configure different PLMNs in multiple TAIDB list and associate each to a
different logical ENB.
HeNBGW now support up to 256 TAIs per TAIDB. Given max of 8 logical EnodeBs, it can support up
to (8*256) 2048 unique TAIs. Considering at max 6 PLMS each sharing the same TAC, the geographical
area covered can be shrunk. HeNBGW cannot increase the number of TAIs per TAIDB, as s1-setup
request message sent to MME can hold max of 256 TAIs.
There will be only one IPSEC tunnel for each HENB SCTP association.
S1AP Handover Request & DL NAS Transport Message with network sharing (MOCN or GWCN) the
MME will generally populate the optional Handover Restriction List IE in the S1AP Initial Context
Setup Request which is S1AP Handover Request & S1AP DL NAS Transport Message. These messages
are transparent to the HeNBGW and no specific processing required from HeNBGW.
HENB requirements for MOCN
With multiple TAIs (one TAC and multiple PLMNs) per HeNB, all the TAIs information has to be
informed to the HeNBGW in the S1AP Setup Request and S1AP ENB Configuration Update.
When UE's connect to the HENB they indicate the PLMN they wish to use. Based on the UE's choice,
the HENB needs to populate the TAI corresponding to the selected PLMN in the S1AP Initial UE
Message.
Configuring HeNBGW MOCN support
This section Introduces configuration support details for the HeNBGW MOCN support.
ENB configuration update from HENB
When HeNBGW validates new PLMN list and TAC, it should match all the PLMNs list & TAC received
with the ENB Configuration Update message from HENB with the TAIDB list of logical EnodeBs.
Otherwise HENBGW will send ENB configuration update failure message.
If there is any change of logical EnodeB list for the new PLMN list and TAC, HeNBGW aggregates
GUMMEI list for newly selected logical EnodeB from all MMEs in a MME-pool in the S1 MME
Configuration Update message to HENB.
If any of the PLMN is deleted or TAC changed with the ENB configuration update message then
HENBGW will send ENB configuration update failure message.
MME configuration update from MME
GUMMEI list status changes for any MME (i.e. lost SCTP connection to MME, new MME connections
is up, or receive MME configuration Update message which changes GUMMEI list for a MME) is
broadcasted to all the HeNBs attached to the logical EnodeB using MME configuration Update Message.
If one of the MME connection goes down HeNBGW will send partial RESET message towards HENB.
If all the MME connections for all the PLMNS goes down HeNBGW will terminate SCTP/S1AP
connection for HeNB.
HeNB-GW Administration Guide, StarOS Release 19
25
HeNB Gateway in Wireless LTE Network
HeNBGW Multi Operator Core Network (MOCN)