Cisco ASR 5x00 Home eNodeB Administration Manual page 34

▀ Information Required to Configure the System as an HeNB-GW
Table 3. Required Information for Destination Context Configuration
Required Description
Information
Destination context An identification string from 1 to 79 characters (alpha and/or numeric) by which the destination context will
name be recognized by the system.
Interface name An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is
recognized by the system.Multiple names are needed if multiple interfaces will be configured.
IP address and IPv4 addresses assigned to the interface.
subnet Multiple addresses and subnets are needed if multiple interfaces will be configured.
Physical port The physical port to which the interface will be bound. Ports are identified by the chassis slot number where
number the line card resides followed by the number of the physical connector on the card. For example, port 17/1
identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces.
Gateway IP address Used when configuring static IP routes from the management interface(s) to a specific network.
HeNB-GW Access Service Configuration
S1-MME interface IPv4 addresses assigned to the S1-MME interface as SCTP bond address.This address will be used for
IP address 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.
Public Land Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999.
Mobile Network
Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999.
(PLMN) Identifiers
S1-MME SCTP The physical port to which is used to communicate with the HeNBs over S1-MME interface. It is usually an
Port integer value ranging from 1 to 65535.
MME ID Group ID MME Group ID to be configured for the HeNB-GW Access Service. This is a required parameter since the
HeNB-GW acts as an MME to the HeNB(s) and this ID is filled in the S1-SETUP response sent to the
HeNB(s). It is an integer ranging from 32768..65535.
MME Code MME Code is also part of the MME ID configuration. MME Group ID and MME Code both are required
for MME Identifier configuration for the HeNB-GW Access service. It is an integer which ranges from
0..255.
S1-U Relay Enables the S1-U relay functionality for the HeNB-GW Access Service. Once S1-U Relay is enabled, the
association to Ingress and Egress GTP-U services is considered as critical configuration for the HeNB-GW
Access service.
Associate A preconfigured HeNB-GW Network Service is requird to be associated to the HeNB-GW Access Service.
HeNBGW Network User can enter a desired HeNB-GW Network service name even if it is not pre-configured, but it will be
Service required to be configured in later course for this HeNB-GW Access service to come up.
Optional Security Gateway Configuration
Security Gateway This is the IP Address where the SeGW service is bound and shall be provided to HeNB during SeGW-
IP address Discovery. This security gateway is associated with the HeNB-GW Access Service.
Only one SeGW IP address can be configured.
Diameter Endpoint An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint
configuration is recognized by the system. This Diameter Endpoint is required by the SeGW to
communicate with the AAA server.
▄ Cisco ASR 5x00 Home eNodeB Gateway Administration Guide
34
HeNB-GW Service Configuration Procedures