MME context
name
|
An
identification string from 1 to 79 characters (alpha and/or numeric) by which
the MME context is recognized by the system.
|
S1-MME Interface
Configuration (To/from eNodeB)
|
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 subnet
|
IPv4 or IPv6
address assigned to the S1-MME interface. This address will be used for binding
the SCTP (local bind address(es)) to communicate with the eNodeBs using S1-AP.
Multiple
addresses and subnets are needed if multiple interfaces will be configured.
|
Physical
port number
|
The physical
port to which the interface will be bound. Ports are identified by the chassis
slot number where 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.
|
S11 Interface Configuration
(To/from S-GW)
|
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 subnet
|
IPv4 address
assigned to the S11 interface.
Multiple
addresses and subnets are needed if multiple interfaces will be configured.
|
Physical
port number
|
The physical
port to which the interface will be bound. Ports are identified by the chassis
slot number where 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.
|
S6a Interface Configuration
(To/from HSS)
|
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 subnet
|
IPv4 or IPv6
addresses assigned to the S6a interface.
Multiple
addresses and subnets are needed if multiple interfaces will be configured.
|
Physical
port number
|
The physical
port to which the interface will be bound. Ports are identified by the chassis
slot number where 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.
|
S6a Diameter Endpoint
Configuration
|
End point
name
|
An
identification string from 1 to 63 characters (alpha and/or numeric) by which
the S6a Diameter endpoint configuration is recognized by the system.
|
Origin realm
name
|
An
identification string between 1 through 127 characters.
The realm is
the Diameter identity. The originator's realm is present in all Diameter
messages and is typically the company or service name.
|
Origin host
name
|
An
identification string from 1 to 255 characters (alpha and/or numeric) by which
the S6a origin host is recognized by the system.
|
Origin host
address
|
The IP
address of the S6a interface.
|
Peer name
|
The S6a
endpoint name described above.
|
Peer realm
name
|
The S6a
origin realm name described above.
|
Peer address
and port number
|
The IP
address and port number of the HSS.
|
Route-entry
peer
|
The S6a
endpoint name described above.
|
S13 Interface Configuration
(To/from EIR)
|
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 subnet
|
IPv4 or IPv6
addresses assigned to the S13 interface.
Multiple
addresses and subnets are needed if multiple interfaces will be configured.
|
Physical
port number
|
The physical
port to which the interface will be bound. Ports are identified by the chassis
slot number where 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.
|
S13 Diameter Endpoint
Configuration
|
End point
name
|
An
identification string from 1 to 63 characters (alpha and/or numeric) by which
the S13 Diameter endpoint configuration is recognized by the system.
|
Origin realm
name
|
An
identification string between 1 through 127 characters.
The realm is
the Diameter identity. The originator's realm is present in all Diameter
messages and is typically the company or service name.
|
Origin host
name
|
An
identification string from 1 to 255 characters (alpha and/or numeric) by which
the S13 origin host is recognized by the system.
|
Origin host
address
|
The IP
address of the S13 interface.
|
Peer name
|
The S13
endpoint name described above.
|
Peer realm
name
|
The S13
origin realm name described above.
|
Peer
address and port number
|
The IP
address and port number of the EIR.
|
Route-entry peer
|
The S13
endpoint name described above.
|
MME Service
Configuration
|
MME
service name
|
An
identification string from 1 to 63 characters (alpha and/or numeric) by which
the MME service can be identified on the system. It is configured in the
Context configuration mode.
Multiple
names are needed if multiple MME services will be configured.
|
PLMN
identifier
|
The
identifier of Public Land Mobile Network (PLMN) of which MME belongs to. PLMN
identifier is consisting of MCC and MNC.
|
MME
identifier
|
The
identifier of MME node. The MME Id is consisting of MME group and MME code.
|
TAI
management database name
|
An
identification string from 1 to 64 characters (alpha and/or numeric) by which
the TAI management database service can be associated with the MME service.
This is
required for static S-GW selection. Refer to the
Required MME Policy Configuration Information section
below.
|
P-GW IP
address
|
IPv4 or
IPv6 address of a PDN Gateway (P-GW). This is required for static S-GW/P-GW
selection.
|
eGTP Service
Configuration
|
eGTP
service name
|
An
identification string from 1 to 63 characters (alpha and/or numeric) by which
the eGTP service can be associated with MME system.
Multiple
names are needed if multiple eGTP services will be used.
|
Interface
type
|
Identifies
the type of interface to which the eGTP service is bound. This interface type
is "interface-mme".
|
GTP-C
binding IP address
|
The IPv4
address of the S11 interface.
|
HSS Peer Service
Configuration
|
HSS peer
service name
|
An
identification string from 1 to 63 characters (alpha and/or numeric) by which
the HSS peer service is recognized by the system.
Multiple
names are needed if multiple HSS peer services will be used.
|
Diameter
HSS peer
|
The name
for a pre-configured Diameter endpoint, configured on system to associate with
this MME service to access an HSS and an EIR. This is the S6a Diameter endpoint
name.
|