Manual

The figure given describes a high level view of LTE network with Femtocell and HeNB-GW.
Figure 1: Home eNodeB Gateway Network Architecture
In the above figure, the S1 interface has been defined as an interface between
•
HeNB-GW and the Core Network (CN)/EPC
•
HeNB and the HeNB-GW
•
HeNB and the CN
An HeNB-GW provides standards-based S1-MME and S1-U network interfaces. As shown in the above high
level LTE Femto network architecture diagram, The HeNB-GW appears to the MME as an eNodeB. The
HeNB-GW appears to the HeNB as an MME. The S1 interface between HeNB and EPC whether the HeNB
is connected to the CN/EPC via an HeNB-GW or not. The HeNB-GW connects to the EPC in a way that
inbound and outbound mobility to cells served by the HeNB-GW does not necessarily require inter MME
handovers.
In accordance with 3GPP LTE standards, the HeNB-GW hosts the following functions and procedures in
LTE core network:
•
Relaying UE-associated S1 application part messages between the MME serving the UE and the HeNB
serving the UE.
•
Terminating non-UE associated S1 application part procedures towards the HeNB and towards the MME.
When an HeNB-GW is deployed, non-UE associated procedures shall be run between
HeNBs and the HeNB-GW and between the HeNB-GW and MME.
Important
•
Optionally terminating S1-U interface with the HeNB and with the S-GW.
•
Supporting tracking area code (TAC) and PLMN ID used by the HeNB.
•
Allowing no X2 interface establishment between the HeNB-GW and other nodes.
•
Optionally performing paging optimization in case the Allowed closed subscriber group (CSG) List of
the paged UE is included in the PAGING message.
At the same time, the MME hosts the following functions to support HeNB-GW:
•
CSG reporting to S-GW/P-GW
•
Access control for UEs that are members of CSG
HeNB-GW Administration Guide, StarOS Release 19
2
HeNB Gateway in Wireless LTE Network
Product Description