Manual

HeNB-GW Access Service: This service is configured under the Context Configuration Mode in
order to initialize the HeNB-GW functionality. The configuration of this service controls the
functionality of S1-MME interface between HeNB-GW and the HeNBs.
This service is bound to a local SCTP end-point address (IP address) to listen the incoming SCTP
associations from HeNBs.
◦
◦
HeNB-GW Network Service: This service is also configured in the Context configuration mode
to support the HeNB-GW functionalities. The configuration of this service controls the functionality
of S1-MME interface between HeNB-GW and MME. One-to-one mapping is maintained between
the HeNB-GW Access service and HeNB-GW Network service.
It is the HeNB-GW Network service where enabling of logical eNodeBs is configured within the
HeNB-GW. The Logical eNodeB configuration can be used to support load balancing among
different TAI Lists. Each Logical eNodeB can connect up to 8 MMEs from the MME pool and
therefore 64 connections are possible to be established between HeNB-GW and MME.
At least one logical eNodeB configuration is required to start the HeNB-GW Network
service. Up to 8 logical eNodeBs can be configured per HeNB-GW Network service.
Important
•
Radio Network PLMN: The Radio Network PLMN is configured in HeNB-GW Access service to
associate PLMNs with HeNB-GW.
PLMN configuration is also required at the time of configuring Logical eNodeBs for the HeNB-GW
Network service.
•
GTP-U services: GTP-U services are configured in Context configuration mode in pair of two services;
one for GTP-U tunnel support towards HeNB on S1 interface and another for GTP-U tunnel support
towards the core network on S1-U interface to communicate with the S-GW respectively. These two
GTP-U services are called Access GTP-U service and Network GTP-U service.
GTP-U service comes in picture specially when the S1-U Relay option is enabled. S1-U relay activation
actually allows the data to flow through the GTP-U tunnel via HeNB-GW, otherwise it directly travels
from HeNBs to S-GW.
When S1-U relay is enabled, the HeNB-GW Access service has to be associated with the Network
GTP-U service and Access GTP-U service. Also the HeNB-GW Access service has to be associated
with the HeNB-GW Network service.
S1-U Relay is disabled by default. Also when S1-U relay is enabled, both Access and
Network GTP-U services need to be in STARTED state for the HeNB-GW access
service to be STARTED.
Important
HeNB-GW Administration Guide, StarOS Release 19
38
Understanding the Service Operation
Services and Networks