Manual

DescriptionRequired Information
The Logical eNodeB configuration option enables the configuration of
one or more logical eNodeBs within the HeNB-GW. The Logical eNodeB
configuration is usually used to support load balancing within a pool of
TAIs. At least one logical eNodeB configuration is required to START
an HeNB-GW Network service. 8 Logical eNodeBs are supported per
HeNB-GW Network service.
Deleting or modifying any of the parameters for a fully
configured logical eNodeB results in the termination of SCTP
connections to MMEs from that logical eNodeb.
Caution
Logical eNodeB
Mobile Country Code (MCC): The MCC can be configured to any
integer value from 0 to 999.
Public Land Mobile Network
(PLMN) Identifiers
Mobile Network Code (MNC): The MNC can be configured to any
integer value from 0 to 999.
Macro eNodeB identifier, required as a parameter for the Logical eNodeB
configuration. It is an option to the Home eNodeB identifier.
Macro eNodeB ID
Home eNodeB identifier, required as a parameter for the Logical eNodeB
configuration. It is an option to the Macro eNodeB identifier.
Home eNodeB ID
IPv4 addresses assigned to the S1-MME interface as SCTP bond address.
This address will be used for binding the SCTP (local bind address(es))
to communicate with the MME using eGTP. The HeNB-GW passes this
IP address during setting up the association with the MME. Multiple
addresses and subnets are needed if multiple interfaces will be configured.
S1-MME interface IP address
The physical port to which is used to communicate with the HeNBs over
S1-MME interface. It is usually an integer value ranging from 1 to 65535.
S1-MME SCTP Port
Logical eNodeB Configuration
A pre-configured MME pool to be associated with the Logical eNodeB.
An MME pool is configured in the LTE Policy Configuration Mode.
Only one MME Pool instance can be associated with a Logical eNodeB
instance. All MMEs in the pool are assumed to support all TAIs in the
associated TAI List DB object. One Logical eNodeB can connect up to
8 MMEs and therefore a max of 64 associations can be established
between HeNB-GW and MME
MME Pool
A pre-configured list of tracking area identity (TAIs) pool to be associated
with the Logical eNodeB. A TAI List database is configured in the LTE
Policy Configuration Mode. Only one TAI list DB can be associated with
the Logical eNodeB instance. The tai-list-db contains a list of TAIs. These
are sent in the S1 Setup message to the MME to indicate the list of TAIs
supported by the eNodeB. The TAI database which can be associated to
each logical EnodeB can accommodate 256 configuration of TACs.
TAI List DB
TAI List DB Configuration
HeNB-GW Administration Guide, StarOS Release 19
45
HeNB-GW Service Configuration Procedures
Required Destination Context Configuration Information