Associates or disassociates supportive services and policies, such as an Evolved GPRS Tunnelling Protocol (eGTP) service, an HSS peer service, or an MME policy subscriber map with an MME service.

no

Disassociates a previously associated service with this MME service.

access-policy policy_name

Specifies the access-policy to be associated with the MME Service. policy_name must be an alphanumeric string of 1 through 64 characters.

associate monitoring-event-profileprofile_monte

Specifies the monitoring event profile to be associated with the MME Service.

decor-profile profile_name

Specifies the DECOR profile to be associated with the MME Service.

access-type { eutran | nb-iot | all }

Configures the type of network access in a DCN — E-UTRAN, NB-IoT, or both.

egtp-mef-service egtp_mef_service_name

Associates the given egtp-service for MEF interface at the MME.

egtp_mef_service_name must be a string from 1 to 63.

context context_name : Specifies the context to which the service belongs.

egtp-s10-s3-service service_name

Associates EGTP service for S10/S3 interface to support Inter-Operator S10 Handover.

service_name must be an alphanumeric string of size 1 to 63 characters.

egtp-service egtp_svc_name

Associates an eGTP service with MME service.

egtp_svc_name specifies the name for a pre-configured eGTP service to associate with the MME service. The eGTP service provides eGTP-C protocol interface support between EPS nodes. For more information on the eGTP service, refer to the egtp-service command in the Context Configuration Mode Commands chapter and the eGTP Service Configuration Mode Commands chapter.

Only one eGTP service can be associated with a service. The eGTP service should be configured prior to issuing this command.

egtp-sv-service egtp_sv_svc_name

Associates an eGTP Sv service with this MME service.

egtp_sv_svc_name specifies the name for a pre-configured eGTP Sv service to associate with the MME service. For more information on the eGTP Sv service, refer to the egtp-service command in the Context Configuration Mode Commands chapter.

foreign-plmn-guti-mgmt-db db_name

Associates a Foreign PLMN GUTI management database with this MME service.

db_name specifies the name for a pre-configured foreign PLMN GUTI management database to associate with the MME service. For more information on the Foreign PLMN GUTI management database, refer to the foreign-plmn-guti-mgmt-db command in the LTE Policy Configuration Mode Commands chapter.

Only one Foreign PLMN GUTI management database can be associated to an MME service. The Foreign PLMN GUTI management database should be configured prior to issuing this command.

Multiple MME services can be associated to the same Foreign PLMN GUTI management database.

gtpc-load-control-profile profile_name

Associates a GTP-C Load Control Profile with this MME service

The profile_name specifies the name of a GTP-C load control profile to associate with the MME service.

For more information on the GTPC Load Control Profile, refer to the feature chapter "GTP-C Load and Overload Control on MME" in the MME Administration Guide.

gtpc-overload-control-profile profile_name

Associates a GTP-C Overload Control Profile with this MME service

The profile_name specifies the name of a GTP-C overload control profile to associate with the MME service.

For more information on the GTPC Overload Control Profile, refer to the feature chapter "GTP-C Load and Overload Control on MME" in the MME Administration Guide.

henbgw-mgmt-db db_name

Important

In Release 20, 21.0 and 21.1, HeNBGW is not supported. This keyword must not be used for HeNBGW in these releases. For more information, contact your Cisco account representative.

Associates the specified HeNB-GW management database with the MME service.

db_name specifies the name for an LTE MME HeNB-GW Management Database to associate with the MME service as an alphanumeric string of 1 through 64 characters. This is required to support S1 HANDOVERs to Home eNodeBs connected via a HeNB-GW.

hss-peer-service hss_svc_name

Associates an HSS peer service with this MME service.

hss_svc_name specifies the name for a pre-configured HSS peer service to associate with the MME service as an alphanumeric string of 1 through 64 characters. The HSS peer service provides S6a and S13 interface support via the Diameter protocol between the MME and an HSS (S6a) or EIR (S13). For more information about the HSS peer service, refer to the hss-peer-service command in the Context Configuration Mode Commands chapter and the HSS Peer Service Configuration Mode Commands chapter.

Only one HSS peer service can be associated to a service. The HSS peer service should be configured prior to issuing this command.

ipne-service ipne_svc_name

Associates an IPNE service with this MME service.

ipne_svc_name must be an alphanumeric string of 1 to 63 characters to identify a pre-configured, uniquely-named IPNE service. For more information about the IPNE service, refer to the sections for the IPNE Service Configuration Mode Commands and the IPNE Endpoint Configuration Mode Commands.

location-service location_svc_name

Associates a location service with this MME service. Only one location service should be associated with an MME Service.

location_svc_name specifies the name for a pre-configured location service to associate with the MME service as an alphanumeric string of 1 through 64 characters. For more information about Location Services (LCS), refer to the location-service command in the Context Configuration Mode Commands chapter and the Location Services Configuration Mode Commands chapter.

lte-emergency-profile profile_name

Associates an LTE emergency profile with this MME service.

profile_name specifies the name for a pre-configured LTE emergency profile to associate with the MME service as an alphanumeric string of 1 through 64 characters. For more information about the LTE emergency profile, refer to the lte-emergency-profile command in the LTE Policy Configuration Mode Commands chapter and the LTE Emergency Profile Configuration Mode Commands chapter.

network-global-mme-id-mgmt-db

Associates the configured global MME ID management database with this MME service. The global MME ID management database is configured through the LTE Policy Configuration Mode using the network-global-mme-id-mgmt-db command.

s102-service s102_svc_name [ context context_name ]

Associates the specified S102 service that manages the S102 interface with this MME service.

s102_svc_name specifies the name for a pre-configured S102 service to associate with this MME service. Enter a string of 1 through 63 alphanumeric characters.

context context_name identifes the context in which the S102 service has been created and configured.

Each MME service can be associated with one unique S102 service.

The S102 service is not a critical parameter for the MME service. Removing this configuration will not restart the MME service.

For more information about the S102 service, refer to the s102-service command in the Global Configuration Mode Commands chapter and the S102 Service Configuration Mode Commands chapter.

sbc-service sbc_svc_name

Important

Beginning with Release 18.4, this keyword is only accessible or configurable if a valid SBc license key is installed. For information about obtaining such a license, contact your Cisco Representative.

Associates the specified SBc service with this MME service.

sbc_svc_name specifies the name for a pre-configured SBc service to associate with this MME service as an alphanumeric string of 1 through 63 characters.

Each MME service can be associated with one unique SBc service.

The SBc service is not a critical parameter for the MME service. Removing this configuration will not restart the MME service.

For more information about the SBc service, refer to the sbc-service command in the Global Configuration Mode Commands chapter, the SBc Service Configuration Mode Commands chapter, and the Cell Broadcast Center - SBc Interface feature chapter in the MME Administration Guide.

sctp-param-template template_name

Associates a Stream Control Transmission Protocol (SCTP) parameter template with this MME service.

template_name specifies the name for a pre-configured SCTP parameter template to associate with this MME service as an alphanumeric string of 1 through 63 characters. For more information on the SCTP parameter template, refer to the sctp-param-template command in the Global Configuration Mode Commands chapter and the SCTP Parameter Template Configuration Mode Commands chapter.

sgs-service sgs_svc_name

Associates an SGs service with this MME service.

sgs_svc_name specifies the name for a pre-configured SGs service to associate with the MME service as an alphanumeric string of 1 through 64 characters. For more information on the SGs service, refer to the sgs-service command in the Context Configuration Mode Commands chapter and the MME SGs Service Configuration Mode Commands chapter.

sgtpc-service sgtpc_svc_name

Associates an SGTPC service with this MME service.

sgtpc_svc_name specifies the name for a pre-configured SGTPC service to associate with the MME service as an alphanumeric string of 1 through 64 characters.

Important

When co-locating an SGSN and MME, the MME Service cannot be associated with the same SGTP service that is used by the SGSN.

For more information on the SGTPC service, refer to the sgtp-service command in the Context Configuration Mode Commands chapter and the SGTP Service Configuration Mode Commands chapter.

smsc-service smsc_svc_name

Associates an SMSC service with this MME service.

smsc_svc_name specifies the name for a pre-configured SMSC service to associate with the MME service as an alphanumeric string of 1 through 64 characters. For more information on the SMSC service, refer to the smsc-service command in the Context Configuration Mode Commands chapter and the MME SMSC Service Configuration Mode Commands chapter.

context ctx_name

Identifies a specific context name where the named service is configured. If this keyword is omitted, the named service must exist in the same context as the MME service.

ctx_name is name of the configured context of the named service expressed as an alphanumeric string of 1 through 63 characters that is case sensitive.

subscriber-map map_name

Associates this MME service with a pre-configured subscriber map.

map_name specifies the name of a pre-configured subscriber map to associate with the MME service as an alphanumeric string of 1 through 64 characters. For more information on subscriber maps, refer to the subscriber-map command in the LTE Policy Configuration Mode Commands chapter and the LTE Subscriber Map Configuration Mode Commands chapter.

tai-mgmt-db database_name

Associates this MME service with a pre-configured TAI Management Database.

database_name specifies the name of a pre-configured TAI Management Database to associate with the MME service as alphanumeric string of 1 through 64 characters. For more information on subscriber maps, refer to the tai-mgmt-db command in the LTE Policy Configuration Mode Commands chapter and the LTE TAI Management Database Configuration Mode Commands chapter.

Binds the MME service to a logical IP interface serving as the S1-MME interface.

no

Removes a previously configured IP address used for binding the SCTP (local bind address) to communicate with the eNodeBs using an S1-MME interface.

{ ipv4-address address [ ipv4-address secondary_address ] | ipv6-address address [ ipv6-address secondary_address ] }

Specifies the IP address for the interface configured as an S1-MME interface in IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation. Optionally configure a secondary IP address for either address type.

crypto-template name

Specifies an existing crypto template name used when implementing IP Security (IPSec) on the S1-MME interface. name is an alphanumeric string of 1 through 104 characters.

max-subscribers number

Specifies the maximum number of subscribers that can access this service on this interface as an integer from 0 through 8000000.

For Release 15.0, the ASR 5500 platform supports up to 10,000,000 MME UE sessions.

This command configures the maximum number of retransmissions of CP data for MO or MT SMS scenario in MME.

default

Sets the default value to 2.

num_retrans

Specifies the number of times CP Data for SMS is retransmitted. num_retrans must be an integer from 1 to 10.

This command enables or disables the Closed Subscriber Group (CSG) Information reporting (notification) mechanism on the MME. When enabled, the MME includes the CSG Information Reporting Action IE with the appropriate Action field for subscribers.

default

By default, this feature is disabled. Using the default command prefix causes the MME to reset the configuration for this parameter to the default so that the feature is disabled.

no

Disables the feature.

Enables Dual Connectivity with New Radio (DCNR) to support 5G Non Standalone (NSA).

no

Disables the DCNR configuration.

Configures Delay Value IE Support in MME.

no

Removes the configured downlink-data-notification delay value

ddn-delay ddn_delay_value

Configures the downlink-data-notification delay value in multiples of 50 milliseconds. ddn_delay_value is an integer and it must be between 0 and 255

This command specifies the Dedicated Core Network (DCN) configuration and enables MME to advertise or request UE Usage Type over the S6a interface.

no

Disables the specified DECOR configuration.

default

Configures default air-flags in AIR

decor

Specifies a dedicated core network configuration.

custom-actions

Configures the specific decor actions.

air

Configures UUT actions in AIR message.

explicit-air-flags

Fills air-flags in AIR, irrespective of UUT stored in DB.

ula

Configures UUT actions in ULA message.

gw-selection

Enables GW selection based on UUT received in ULA.

nas-reroute

Enables NAS re-route based on Ue-Usage-Type received in ULA.

reject

Rejects the rerouted call based on Ue-Usage-Type received in ULA.

s6a

Configures the S6a interface.

ue-usage-type

Specifies the UE Usage Type that needs to be sent in the Authentication-Information-Request message over the S6a interface.

Specifes the context where the Domain Name System (DNS) client service is configured for DNS query to select an MSC, P-GW, S-GW, peer SGSN, peer MME or peer AMF for this MME service.

no

Removes a previously specified context having a DNS client service configured for DNS query to select a MSC, peer MME, peer SGSN, peer AMF, P-GW or S-GW with this MME service.

msc

Specifies the context where a DNS client service is configured for DNS queries for selecting a Mobile Switching Center (MSC) for SRVCC.

peer-mme

Specifies the context where a DNS client service is configured for DNS queries for selecting a peer MME.

peer-sgsn

Specifies the context where a DNS client service is configured for DNS queries for selecting a peer SGSN for inter-RAT handovers.

pgw

Specifies the context where a DNS client service is configured for DNS queries for selecting a P-GW.

sgw

Specifies the context where a DNS client service is configured for DNS queries for selecting an S-GW.

context ctx_name

Optionally associates the specific context name where the DNS client service is configured for this MME service. If this keyword is omitted, the DNS client service is configured to use the same context as this MME service.

ctx_name is name of the configured context of the DNS client service expressed as an alphanumeric string of 1 through 79 characters that is case sensitive.

This command configures the Hyper SFN synchronization reference time for eDRX.

Syntax

edrx hsfn-reference ref_time adjust leap_seconds 
no edrx hsfn-reference 

no

Disables the H-SFN synchronization reference time configuration.

hsfn-reference ref_time

Specifies the UTC Time at which H-SFN=0 starts. ref_time must be entered in the UTC Time format as follows: YYYY:MM:DD:hh:mm:ss. For example: 2016:03:01:12:34:56.

adjust leap_seconds

Specifies the number of leap seconds that need to be adjusted. leap_seconds must be an integer from 0 to 100.

A maximum of 2 H-SFN reference time configuration is allowed. The first configuration will be the latest leap-second adjustment UTC time and the second configuration will be the next or declared leap-second adjustment UTC time.

For example:

Consider the following H-SFN reference time configuration:

asr5000(config-mme-service)# edrx hsfn-reference 2017:01:01:00:00:00 adjust 5

When the next leap second adjustment is announced with new time 2018:01:01:00:00:00 , MME can be configured any time before 2018:01:01 with the following configuration.

asr5000(config-mme-service)# edrx hsfn-reference 2018:01:01:00:00:00 adjust 6

When another leap second adjustment is announced with another new time 2018:06:30:00:00:00, MME can be configured any time before 2018:06:30 with the following configuration, and deletes the oldest time reference (2017:01:01) configuration.

asr5000(config-mme-service)# no edrx hsfn-reference 2017:01:01:00:00:00

asr5000(config-mme-service)# edrx hsfn-reference 2018:06:30:00:00:00 adjust 7

For HSFN-Start in GPS format, the number of leap seconds must be provided from 1980:1:06. For example: at 2017:01:01:00:00:00, the number of leap seconds from 1980:1:06 are 18.

For HSFN-Start in UTC format, the number of leap seconds must be provided from the HSFN-Start time. For example: at 2000:03:01:12:34:5, the number of leap seconds from 2000:03:01:12 are 5.

Example

edrx hsfn-start 2016:03:01:12:34:56 

This command configures the Hyper SFN synchronization start time for eDRX.

Syntax

edrx hsfn-start start_time [ gps | utc ] 
no edrx hsfn-start 

no

Disables the H-SFN synchronization time configuration.

hsfn-start start_time

Specifies the time at which H-SFN=0 starts in GPS or UTC format. The UTC time format is YYYY:MM:DD:hh:mm:ss. For example: 2016:03:01:12:34:56.

gps | utc

The gps and utc keywords are optional. If not explicitly provided, then H-SFN=0 starts in UTC format.

• gps : Specifies the time at which H-SFN=0 starts in GPS format. GPS time starts from 1980:01:06:00:00:00.

  For example: edrx hsfn-start 2000:03:01:12:34:56 gps

• utc : Specifies the time at which H-SFN=0 starts in UTC format. UTC time starts from 1972:06:30:00:00:00.

  For example: edrx hsfn-start 2000:03:01:12:34:56 utc

• After the HSFN-start configuration, the HSFN-reference can be configured to adjust the leap seconds.

Example

edrx hsfn-start 2016:03:01:12:34:56 

edrx hsfn-start 2016:03:01:12:34:56 gps 

Defines the Evolved Mobility Management timer parameters, such as timeout durations for timers and retransmission counts, for Non-Access Stratum (NAS) message retransmission in MME service.

default

Resets the specified timer timeout to the system default value.

implicit-detach-timeout detach_dur

Sets the timer timeout duration (in seconds) after which subscriber will implicitly detached from the network if there is no activity. Generally this timer value is 240 seconds (4 minutes) more than the timeout value of the T3423 timer.

This timer starts when mobile reachable timer expires while the network is in EMM-IDLE mode and ISR is activated and stops when a NAS signalling connection established.

detach_dur is an integer from 1 through 12000. Default: 3480

mobile-reachable-timeout mob_reach_dur

Sets the timeout timer duration (in seconds) after which reachability procedure will be discarded and reattempt starts.

mob_reach_dur is an integer from 1 through 12000. Default: 3480

mt-queue-timeout mtq_timer

Configures the timer to hold MT SMS in MT queue. MT SMS will be present in the queue while the previous SMS is being processed. The timer expiry will return error to SMSC for an absent subscriber.

mtq_timer specifies the timeout in seconds, as an integer from 1 to 300. Default: 30 seconds

t3346-timeout t3346_dur

Sets the EMM backoff timer duration (in seconds). If an EMM request is rejected by MME because of congestion, it shall have EMM cause as congestion (#22) and shall include back-off timer (T3346) IE. The back-off timer shall be chosen randomly and shall be 10% below or above the configured T3346 timer value.

t3346_dur is an integer from 0 through 11160 (0-186 minutes). Default: 1500 seconds (25 minutes).

While storing this back-off timer expiry time, the MME shall adjust the mobile reachability timer and/or implicit detach timer. This is to make sure that the sum of the mobile reachability timer + implicit detach timer is greater than the back-off timer duration.

The MME will store the DB for at least the EMM back-off timer duration even if the attach is rejected because of congestion. The MME will not start any timer for EMM back-off. Instead, back-off timer expiry time will be stored in the DB as the DB is stored for at least back-off timer duration.

If an EMM call is rejected due to congestion control for EMM, the DB created during ULA will not be cleared and the purge timer will be started for a time period 10% greater than the back-off timer duration. This is done to make sure that DB is available during back-off timer duration to reject any requests during this period and also to avoid the HSS signaling again if the UE comes back immediately after the back-off timer duration.

The MME will not reject any requests related to handovers as part of this feature even if EMM back-off timer is running.

The MME will drop attach requests received during congestion while EMM back-off timer is running based on configuration in congestion-action-profile. For example, if configuration is enabled to reject new call only when low priority indication is set and the UE comes without low priority indication while back off timer is running, the MME will accept the new call attempt from the UE.

The MME will not reject/drop attach requests received even if EMM back-off timer is running if the congestion gets cleared.

The MME will forward SGS paging requests received from MSC for a UE attached in MME even if back-off timer is running.

t3412-extended-timeout t3412_ext_dur

Sets the extended periodic TAU timer duration (in seconds), enabling the Operator to configure longer values for the periodic TAU timer and Mobile Reachable timer. This helps the MME to reduce network load from periodic TAU signaling and to increase the time until the UE detects a potential need for changing the RAT or PLMN.

t3412_ext_dur is an integer from 0 through 1116000 (0-186 minutes). Default: 3600 seconds (60 minutes).

The UE must include the "MS network feature support" IE in the Attach Request/TAU Request. This IE indicates to the MME that the UE supports the extended periodic timer T3412, in which case the MME sends the extended-3412 IE in the Attach/TAU response. The MME will not forward the extended-T3412 timer value to any UE which has not indicated that it supports this extended-t3412 timer.

The MME supports storing the Subscribed-Periodic-RAU-TAU-Timer value if received as part of subscription data, and deleting this stored value if the corresponding withdrawal flag is received in the DSR command.

For homers, the MME will send the extended-3412 IE value as received in Subscribed-Periodic-RAU-TAU-Timer IE in subscription data.

For roamers, the MME takes the presence of Subscribed-Periodic-RAU-TAU-Timer IE in subscription data as an indication and shall send the extended-3412 IE with the value from the local configuration.

The MME adjusts the configured mobile reachability timer value if the subscribed extended-3412 timer value received from HSS is greater than the sum of the mobile reachability timer + implicit detach timer such that the extended-3412 timer value becomes 10% less than the mobile reachability timer + implicit detach timer.

Refer to 3GPP TS 23.401 Section 4.3.17.3 (Version 10.4.0) and 29.272 for more details.

t3412-timeout t3412_dur

Sets the timeout duration (in seconds) for the T3412 timer. This timer is used for periodic tracking area update (P-TAU). When this timer expires, the periodic tracking area updating procedure starts and the timer is set to its initial value for the next start.

This timer starts when the UE goes from EMM-CONNECTED to EMM-IDLE mode and stops when the UE enters EMM-CONNECTED mode.

t3412_dur is an integer from 1 through 11160. Default: 3240

t3413-timeout t3413_dur

Sets the timeout duration (in seconds) for the T3413 timer. The timer starts when MME initiates the EPS paging procedure to the EMM entity in the network and requests the lower layer to start paging. This timer stops for the paging procedure when a response received from the UE.

t3413_dur is an integer from 1 through 20. Default: 6

t3415-timeout t3415_dur

The keyword t3415-timeout t3415_dur is used to configure the T3415 paging timeout value. The t3415_dur is an integer value in the range 1 up to 20 seconds. The default value is 6 seconds.

t3422-timeout t3422_dur

Sets the timeout duration (in seconds) for the T3422 timer. This timer starts when MME initiates the detach procedure by sending a DETACH REQUEST message to the UE and stops upon receipt of the DETACH ACCEPT message.

t3422_dur is tan integer from 1 through 20. Default: 6

t3423-timeout t3423_dur

Sets the timeout duration (in seconds) for the T3423 timer. This timer starts when UE enters the EMM-DEREGISTERED state or when entering EMM-CONNECTED mode. It stops while the UE is in EMM-REGISTERED.NO-CELL-AVAILABLE state and Idle mode Signalling Reduction (ISR) is activated.

t3423_dur is an integer from 1 through 11160. Default: 3240

t3450-timeout t3450_dur

Sets the timeout duration (in seconds) for the T3450 timer. This timer starts when MME initiates the Globally Unique Temporary Identifier (GUTI) reallocation procedure by sending a GUTI REALLOCATION COMMAND message to the UE and stops upon receipt of the GUTI REALLOCATION COMPLETE message.

This timer is also used for the Tracking Area update procedure.

t3450_dur is an integer from 1 through 20. Default: 6

t3460-timeout t3460_dur

Sets the timeout duration (in seconds) for the T3460 timer. This timer starts when the network initiates the authentication procedure by sending an AUTHENTICATION REQUEST message to the UE and stops upon receipt of the AUTHENTICATION RESPONSE message.

t3460_dur is an integer from 1 through 20. Default: 6

t3470-timeout t3470_dur

Sets the timeout duration (in seconds) for the T3470 timer. The MME starts this timer when the network initiates the identification procedure by sending an IDENTITY REQUEST message to the UE and stops upon receipt of the IDENTITY RESPONSE message.

t3470_dur is an integer from 1 through 20. Default: 6

tc1n-timeout tc1n_timer

Configures the retransmission timer to send CP SMS data to UE for MO/MT scenario.

tc1n_timer specifies the timeout in seconds, as an integer from 1 to 20. Default: 30 seconds

tr1n-timeout tr1n_timer

Configures the wait time to receive RP-Ack from UE for MT SMS, before sending error to SMSC.

tr1n_timer specifies the timeout in seconds, as an integer from 1 to 300. Default: 30 seconds

tr2n-timeout tr2n_timer

Configures the wait time to send RP-Ack to UE for MO SMS, before sending protocol error to UE.

tr2n_timer specifies the timeout in seconds, as an integer from 1 to 300. Default: 30 seconds

Configures the amount of time that eNodeB information is stored in cache after the eNodeB terminates the connection.

default

Returns the command to its default value of 10.

min

Specifies the amount of time (in minutes) that the MME stores eNodeB information after the eNodeB terminates the connection. min is an integer value from 1 through 1440. Default: 10

Configures the precedence for LTE encryption algorithms to use for security procedures through this MME service.

default

Removes the preconfigured encryption algorithm and sets the default LTE encryption algorithm for security procedures with configured priority. The lowest value has the highest preference.

The default configuration of LTE encryption algorithm is:

• priority1 with 128-eea0 encryption algorithm

• priority2 with 128-eea1 encryption algorithm

• priority3 with 128-eea2 encryption algorithm

priority1

Specifies the preference of encryption algorithm for security procedures on this MME service as priority 1.

priority2

Specifies the preference of encryption algorithm for security procedures on this MME service as priority 2.

priority3

Specifies the preference of encryption algorithm for security procedures on this MME service as priority 3.

priority4

Specifies the preference of encryption algorithm for security procedures on this MME service as priority 4.

128-eea0

Sets the Null ciphering algorithm (128-EEA0) for LTE encryption as the encryption algorithm for security procedures.

Default: priority1

128-eea1

Sets the SNOW 3G synchronous stream ciphering algorithm (128-EEA1) for LTE encryption as the encryption algorithm for security procedures. SNOW 3G is a stream cipher that forms the base of the 3GPP confidentiality algorithm UEA2 and the 3GPP integrity algorithm UIA2.

Default: priority2

128-eea2

Sets the Advance Encryption Standard (AES) ciphering algorithm (128-EEA2) for LTE encryption as the encryption algorithm for security procedures.

Default: priority3

128-eea3

Sets the ZUC algorithm (128-EEA3) for LTE encryption as the encryption algorithm for security procedures.

Default: priority4

Defines the Evolved Session Management timer parameters like timeout durations for timers and retransmission counts for the retransmission of Non-Access Stratum (NAS) messages in MME service.

default

Resets the specified Evolved Session Management timer timeout to the system default value.

t3396-timeout t3396_dur

Sets the ESM backoff timer duration (in seconds). If an ESM request is rejected because of congestion, the reject will have ESM cause "Insufficient resources" and will include a back-off timer IE (T3396). This back-off timer is chosen randomly and will be 10% below or above the configured T3396 timer value.

t3396_dur is an integer from 0 through 11160 (0-186 minutes). Default: 1500 seconds (25 minutes).

The MME will not start any timer for SM back-off, nor store the SM back-off timer expiry time. If an SM request is received and if congestion exists, the request would be rejected based and a new random value will be sent as the ESM back-off timer value.

The MME will reject any subsequent requests from the UE targeting to the same APN based on the presence of congestion at that time and not based on the SM back-off time previously sent to the UE.

If the ESM cause value is #26 "insufficient resources" or #27 "missing or unknown APN", the MME will include a value for timer T3396 in the reject message. If the ESM cause value is #26 "insufficient resources" and the request message was sent by a UE accessing the network with access class 11 - 15 or if the request type in the PDN CONNECTIVITY REQUEST message was set to "emergency", the MME will not include a value for timer T3396.

t3485-timeout t3485_dur

Sets the timeout duration (in seconds) for the T3485 timer. This timer is used by the default EPS bearer context activation procedure.

This timer starts when the MME sends an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to UE and stops when receives ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message from UE.

t3485_dur is an integer from 1 through 60. Default: 8

t3486-timeout t3486_dur

Sets the timeout duration (in seconds) for theT3486 timer. This timer is used by the default EPS bearer context modification procedure.

This timer starts when the MME sends a MODIFY EPS BEARER CONTEXT REQUEST message to the UE and stops when it receives a MODIFY EPS BEARER CONTEXT ACCEPT received or a MODIFY EPS BEARER CONTEXT REJECT message from UE.

t3485_dur is an integer from 1 through 60. Default: 8

t3489-timeout t3489_dur

Sets the timeout duration (in seconds) for the T3489 timer. This timer is used for the default EPS bearer context deactivation procedure.

This timer starts when the MME sends an ESM INFORMATION REQUEST message to the UE and stops when receives a ESM INFORMATION RESPONSE message from the UE.

t3495_dur is an integer from 1 through 60. Default: 4

t3495-timeout t3495_dur

Sets the timeout duration (in seconds) for the T3495 timer. This timer is used for default EPS bearer context deactivation procedure.

This timer starts when the MME sends a DEACTIVATE EPS BEARER CONTEXT REQUEST message to UE and stops when receives DEACTIVATE EPS BEARER CONTEXT ACCEPT or DEACTIVATE EPS BEARER CONTEXT REJECT message from UE.

t3495_dur is tan integer from 1 through 60. Default: 8

Configures GTPv2 piggybacking support from the MME to the P-GW. A piggybacking flag is sent by the MME to a P-GW in the S11 "Create Session Request" message and determines whether dedicated bearer creation (Create Bearer Request) is piggybacked onto the "Create Session Response" message or not.

default

Returns the command to its default setting of enabled.

no

Disables the feature.

piggybacking

Specifies that piggybacking is to be performed by the P-GW.

Configures the target HeNB type (home or macro or both) behind HeNBGW. Based on this configuration, MME allows TAI-based lookup of target eNB, if target eNB ID is not found by MME during handover.

no

Removes the existing configuration, if previously configured. By default, when the henbgw henb-type command is not executed explicitly, target eNB type is set as home-enb.

henb-type { all | home-enb | macro-enb }

Configures HeNB type. TAI-based lookup depends on HeNB type.

• all : Configures HeNB type both macro-enb (20-bits) and home-enb (28-bits).

• home-enb : Configures HeNB type home-enb (28-bits). This is the default keyword.

• macro-enb : Configures HeNB type macro-enb (20-bits).

Configures HeNBGW selection using HeNB MSB 10 bits for the same TAI.

no

Removes the configured HeNBGW selection for same TAI.

henbgw selection msb-10-bits

Configures HeNBGW selection using HeNB MSB 10 bits for the same TAI.

• henbgw : Configures HeNBGW options.

• selection : Configures HeNBGW selection for same TAI.

• msb-10-bits Configures HeNBGW selection using HeNB MSB 10 bits for same TAI. By default this is disabled.

Important

HeNBGW selection using HeNB MSB 10 bits is performed only when TAIs are shared across multiple HeNBGWs.

Enables or disables the heuristic or optimized paging feature for the service.

default

Returns the command to its default setting of disabled.

no

Disables the feature.

paging-map paging_map_name

Specifies the paging-map to be associated with this MME service. This keyword is only supported in Release 14.0 and higher.

Configures the timer that is started when the source MME initiates a handover.

default

Returns the command to the default setting of 5000 milliseconds.

timeout

Specifies the time in milliseconds that the MME will hold on to bearers and E-RABs after an S1-based handover has been initiated.

timeout must be an integer from 500 through 15000.

Default: 5000.

Configures the precedence of LTE integrity algorithms to use for security procedures through this MME service. By default the integrity algorithm is enabled on MME service and cannot be disabled.

default

Removes the preconfigured integrity algorithm and sets the default LTE integrity algorithm for security procedures.

The default configuration of LTE integrity algorithm is:

• priority1 with 128-eia0 integrity algorithm

• priority2 with 128-eia1 integrity algorithm

• priority3 with 128-eia2 integrity algorithm

priority1

Specifies the preference of integrity algorithm for security procedures on this MME service as priority 1.

This is the mandatory and default priority keyword.

priority2

Specifies the preference of integrity algorithm for security procedures on this MME service as priority 2.

priority3

Specifies the preference of integrity algorithm for security procedures on this MME service as priority 3.

priority4

Specifies the preference of integrity algorithm for security procedures on this MME service as priority 4.

128-eia0

Sets the Null ciphering algorithm (128-EIA0) for LTE integrity as the integrity algorithm for security procedures.

Default: priority1

128-eia1

Sets the SNOW 3G synchronous stream ciphering algorithm (128-EIA1) for LTE integrity as the integrity algorithm for security procedures. SNOW 3G is a stream cipher that forms the base of the 3GPP confidentiality algorithm UEA2 and the 3GPP integrity algorithm UIA2.

Default: priority2

128-eia2

Sets the Advance Encryption Standard (AES) ciphering algorithm (128-EIA2) for LTE integrity as the integrity algorithm for security procedures.

Default: priority3

128-eia3

Sets the ZUC algorithm (128-EIA3) for LTE integrity as the integrity algorithm for security procedures.

Default: priority4

Configures an NNSF (NAS Node Selection Functionality) entry to define a list of Served MMECs (MME codes) that is indicated to the eNodeB in the S1 Setup Response. This optional configuration is used to aid the eNodeB when selecting the MME for inter-rat handovers when the MME is co-located with an SGSN.

no

Removes the specified NNSF entry.

collocated-mme

Specifies that the MME is co-located with an SGSN.

plmn-id mcc mcc_value mnc mnc_value

Specifies the PLMN-ID for this MME service.

mcc mcc_value : Specifies the mobile country code (MCC) portion of the PLMN identifier as an integer from 100 through 999.

mnc mnc_value : Specifies the mobile network code (MNC) portion of the PLMN identifier as a 2- or 3-digit integer from 00 through 999.

group-id mme_group_id

Configures the group id for this MME service.

mme_group_id must be an integer value from 0 through 65536.

mme-codes mmec

Configures a list of MMEC (MME codes) to be used.

mmec : must be entered as a series of codes, each separated by a space, such as: 10 25 102 103 105. Each code must be an integer from 0 through 255.

A maximum of 16 MME Codes are allowed to be configured per inter-rat-nnsf entry.

mme-code-range first_mme_code to last_mme_code

Configures a range of MMEC (MME codes) to be used. Identify an unlimited number of MME codes, for a particular PLMN-ID and Group-ID combination, as part of a range of MME codes.

first_mme_code : must be the first MME code in the range and it must be an integer from 0 through 255.

last_mme_code : must be the last MME code in the range and it must be an integer from 0 through 255 and it must be an integer greater than the value entered for the first_mme_code .

This command specifies/selects the Insert Subscriber Data Answer sent to the HSS.

Syntax

isda loc-validity-timeout timer_value   
[ no ] isda loc-validity  

no

Disables the ISDA location validity configuration.

loc-validity-timeout timer_value

Specifies the expiry time for the age of the UE's location information. During this time, if the EPS Location Information with current location is requested in the ISDR, the MME does not process a location procedure with the eNodeB, but sends the location information from the cache.

The timer_value specifies the amount of time in seconds. The timer is an integer value that ranges from 1 to 1000 seconds.

Example

Sets the number of seconds for the Insert Subscription Data Answer (ISDA) guard timer. The time the MME waits for current location information for the UE. If the current location is not learned before expiry, because there is no paging response or location reporting control from the eNB, then the MME sends the ISDA with the last-known location upon expiry of this timer.

no

Disables any configuration for this timer and resets the wait time to the default of 25 seconds.

seconds

Enter an integer from 1 to 100.

Enables or disables the Idle-mode Signaling Reduction (ISR) feature on the MME service.

default

Sets the ISR feature to the default setting (disabled) on MME service.

no

Disables the ISR feature on MME service.

Using this command instructs the MME to override the default behavior (described in Usage section below) and enables the MME to use "010" encoding value for the Tracking Area Identity (TAI) list IE for TAIs belonging to different PLMNs.

no

Disables the use of "010" encoding value for the TAI list IE for TAIs belonging to different PLMNs and returns the MME to using the TAI list value encoding based on PLMN and TAC values of TAI entries, the default behavior.

Configures the reject cause code to send to a UE when an APN mismatch occurs.

default local-cause-code-mapping apn-mismatch

Returns the cause code mapping to its default value: esm-failure esm-cause-code unknown-apn .

apn-mismatch emm-cause-code { eps-service-not-allowed-in-this-plmn | esm-failure esm-cause-code unknown-apn | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when an APN mismatch occurs.

Gives the operator the option to specify the local cause-code mapping when the UE-requested APN is not subscribed.

default

Returns the local cause code mapping to the default of #27 (Unknown or Missing APN).

This command maps the operator-preferred ESM/EMM cause code to be sent in Activation Reject messages in place of the standard 3GPP Release 11 rejection cause #66 when activation of the requested APN is not supported in current RAT and PLMN combination.

default

Returns the cause code mapping to its default values. The default cause code values for Attach procedures are emm-cause-code 19 and esm-cause-code 66. The default cause code values for TAU procedures are emm-cause-code 15 and esm-cause-code 66 respectively. The default cause code for ESM procedure is 66.

apn-not-supported-in-plmn-rat

The keyword apn-not-supported-in-plmn-rat specifies that the cause codes to be used for a rejection due to the requested APN not being supported in the current RAT and PLMN combination are those that are mapped in the configuration.

emm-cause-code emm_cause_number esm-cause-code esm_cause_number [ attach ] [ tau ]

MME only.

The keyword emm-cause-code configures the operator-preferred EMM cause code to be used if a NAS Request is rejected due to this configuration.

esm-cause-code esm_cause_number esm-proc

MME only.

Configures the reject cause code to send to a UE when an authentication failure occurs.

default local-cause-code-mapping auth-failure

Returns the cause code mapping to its default value: illegal-ms .

auth-failure emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when an authentication failure occurs.

Configures the reject cause code to send to a UE when a procedure fails due to a congestion condition.

default local-cause-code-mapping congestion

Returns the cause code mapping to its default value: emm-cause congestion esm-cause congestion .

congestion emm-cause { congestion [ esm-cause-code { congestion | insufficient-resources | service-option-temporarily-out-of-order } ] | eps-service-not-allowed-in-this-plmn | network failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when a UE requests access when the system is exceeding any of its congestion control thresholds.

esm-cause-code { congestion | insufficient-resources | service-option-temporarily-out-of-order }

Specifies the EPS Session Management (ESM) cause code to return when a UE requests access when the system is exceeding any of its congestion control thresholds.

Configures the reject cause code to send to a UE when a UE context transfer failure from a peer MME occurs.

default local-cause-code-mapping ctxt-xfer-fail-mme

Returns the cause code mapping to its default value:unknown-ue-context .

ctxt-xfer-fail-mme emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed | unknown-ue-context }

Specifies the EPS Mobility Management (EMM) cause code to return when a UE context transfer failure from an old MME occurs.

Configures the reject cause code to send to a UE when a UE context transfer failure from a peer SGSN occurs.

default local-cause-code-mapping ctxt-xfer-fail-sgsn

Returns the cause code mapping to its default value:unknown-ue-context .

ctxt-xfer-fail-sgsn emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed | unknown-ue-context }

Specifies the EPS Mobility Management (EMM) cause code to return when a UE context transfer failure from an old SGSN occurs.

Configures the reject cause code to send to a UE when a gateway (S-GW or P-GW) does not respond during an EMM procedure.

default local-cause-code-mapping gw-unreachable [ attach | tau ]

Returns the cause code mapping to its default value: #19 - ESM Failure cause code for Attach procedures, and no-bearers-active - #40 - NO-EPS-BEARER-CONTEXT-ACTIVATED for TAU procedures.

gw-unreachable emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when a gateway does not respond.

[ attach [ tau ] | tau [ attach ] ] | { no-bearers-active tau }

Optionally, the MME can return separate cause codes for Attach procedures and TAU procedures. This capability is available for any of the above EMM cause codes except no-bearers-active , which can only be defined for TAU procedures.

Configures the reject cause code to send to a UE when the HSS does not respond.

default local-cause-code-mapping hss-unavailable

Returns the cause code mapping to its default value:

hss-unavailable emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when the HSS does not respond.

Configures the EPS Mobility Management (EMM) reject cause code to send to a UE when a UE requests access but the call control profile has set the call disposition to reject.

default local-cause-code-mapping newcall-policy-restrict

Returns the cause code mapping to its default value: congestion .

newcall-policy-restrict emm-cause-code emm_cause_code

Specifies the EPS Mobility Management (EMM) cause code to return when a UE requests access but the call control profile has set the call disposition to reject.

emm_cause_code must be one of the following options:

Configures the reject cause code to send to a UE when the context received from a peer SGSN (during a TAU procedure) does not contain any active PDP contexts.

default local-cause-code-mapping no-active-bearers

Returns the cause code mapping to its default value: no-bearers-active .

no-active-bearers emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-bearers-active | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when no active PDP context exists.

Configures the ESM and EMM cause codes to send to a UE depending on the Operator Determined Barring (ODB) condition.

default local-cause-code-mapping odb packet-services

Returns the EMM cause code mapping to its default value: #15 - NO_SUITABLE_CELL_IN_TRACKING_AREA.

packet-services emm-cause-code cc_value [ esm-cause-code cc_value ]

Specifies the EPS Mobility Management (EMM) cause code to return when ODB condition is hit.

emm-cause-code cc_value : Specifies the EMM cause code for ODB all packet services. The EMM cause code value is an integer from 0 to 255.

esm-cause-code cc_value : This is an optional keyword used to specify the ESM cause code as an integer from 0 to 255.

Configures the ESM and EMM cause codes to send to a UE depending on the Operator Determined Barring (ODB) condition.

default local-cause-code-mapping odb roamer-to-vplmn emm-cause-code

Returns the EMM cause code mapping to its default value: #15 - NO_SUITABLE_CELL_IN_TRACKING_AREA.

roamer-to-vplmn emm-cause-code cc_value [ esm-cause-code cc_value ]

Specifies the EPS Mobility Management (EMM) cause code to return when ODB condition is hit.

emm-cause-code cc_value : Specifies the EMM cause code for ODB roamer to visited PLMN. The EMM cause code value is an integer from 0 to 255.

esm-cause-code cc_value : This is an optional keyword used to specify the ESM cause code as an integer from 0 to 255.

Configures the reject cause code to send to a UE when peer node resolution is not successful.

default local-cause-code-mapping peer-node-unknown

Returns the cause code mapping to its default value: unknown-ue-context

peer-node-unknown emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when the peer node is not known.

Configures the reject cause code to send to a UE when a failure occurs during P-GW selection.

default local-cause-code-mapping pgw-selection-failure

Returns the cause code mapping to its default value: network-failure .

pgw-selection-failure emm-cause-code { { esm-failure esm-cause-code unknown-apn } | eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when a failure occurs during P-GW selection.

Configures the reject cause code to send to a UE when a procedure fails.

default local-cause-code-mapping restricted-zone-code

Returns the cause code mapping to its default value: no-suitable-cell-in-tracking-area .

restricted-zone-code emm-cause-code emm_cause_code

Specifies the EPS Mobility Management (EMM) cause code to return when a UE requests access to a restricted zone.

emm_cause_code must be one of the following options:

Configures the reject cause code to send to a UE when a failure occurs during S-GW selection.

default local-cause-code-mapping sgw-selection-failure

Returns the cause code mapping to its default value: network-failure .

sgw-selection-failure emm-cause-code { eps-service-not-allowed-in-this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed }

Specifies the EPS Mobility Management (EMM) cause code to return when a failure occurs during S-GW selection.

Configures the cause code to send in a ATTACH ACCEPT or TAU ACCEPT to a UE that attachment to the VLR has failed because a VLR down condition is present.

default local-cause-code-mapping vlr-down

Returns the cause code mapping to its default value: msc-temp-unreachable .

vlr-down emm-cause-code emm_cause_code

Specifies the EPS Mobility Management (EMM) cause code to return when a VLR down condition is present.

emm_cause_code must be one of the following options:

Configures the cause code to send in a ATTACH ACCEPT or TAU ACCEPT to a UE that attachment to the VLR has failed because a VLR unreachable condition is present.

default local-cause-code-mapping vlr-unreachable

Returns the cause code mapping to its default value: msc-temp-unreachable .

vlr-down emm-cause-code emm_cause_code

Specifies the EPS Mobility Management (EMM) cause code to return when a VLR unreachable condition is present.

emm_cause_code must be one of the following options:

Enables or disables the UE location reporting function on the MME service.

default

Disables the location reporting feature on MME service.

no

Disables the location reporting feature on MME service.

Configures how the MME maps the Target RNC-ID fields to the Target eNodeB-ID and TAC fields for Inter-RAT Gn/Gp handovers.

no

Sets the command to use the default value of maptype-default-includes-only-enb .

maptype-default-includes-only-enb

Default mapping logic

Maps the Target RNC-ID fields to Target eNodeB-ID fields as follows:

maptype1-includes-enb-tai

Maps the Target RNC-ID fields to Target eNodeB-ID fields as follows:

Specifies the maximum number of EPS bearers that a subscriber may simultaneously use to access this MME service.

default

Configures the maximum EPS bearers for a subscriber to use simultaneously to the default value of 11.

max_bearer

Specifies the maximum number of EPS bearers for a subscriber may simultaneously use to access this MME service.

max_bearer is an integer from 1 through 11. Default: 11

This command configures the maximum number of paging attempts allowed for network requested service creation to a subscriber.

default

Configures the maximum number of paging attempts to the default value of 3.

max_paging_attempts

Specifies the maximum number of paging attempts allowed for network requested service creation to a subscriber.

max_paging_attempts is an integer from 1 through 10. Default: 3

Specifies the maximum number of Packet Data Networks (PDNs) that a subscriber may simultaneously access through this MME service.

default

Configures the maximum PDNs that a subscriber can simultaneously access through this MME service to the default value of 3.

max_pdn

Specifies the maximum number of PDNs that a subscriber may simultaneously access through this MME service.

max_pdn is an integer from 1 through 11. Default: 3

Enables Minimization Drive Test(MDT) handling on MME.

no

Disables the Minimization Drive Test(MDT) handling on MME.

minimization-drive-test

This command enables Minimization Drive Test(MDT) handling on MME.

Configures the MME identifier within an MME service. The MME identifier is constructed form the MME group ID and MME Code.

no

Removes the configured MME identifier for this MME service.

Caution

Removing the MME identifier is a disruptive operation; the MME service is removed from the system.

group-id grp_id

Specifies the group identifier for the group of which this MME belongs as an integer from 0 through 65535.

mme-code mme_code

Specifies the unique code for this MME service as an integer from 0 through 255.

Configures the recovery action for the MME manager.

default

Resets the function configuration to the MME's default value of reset S1 peers.

no-reset

Specifies that the recovery action is not to reset S1 peers.

reset-s1-peers

Specifies that the recovery action is to reset S1 peers. This is the default action.

Enables Monitoring Events for UE on MME.

default

Disables monitoring-events at the time of MME service configuration.

Creates and manages an Mobile Switching Center (MSC) server configuration, for the MME service, for an MSC enhanced with Single Radio Voice Call Continuity (SRVCC). The MSC server acts as an endpoint for the Sv interface.

no msc_name

Removes the MSC configuration from the MME service.

msc_name

Specifies a name for this peer MSC server.

msc_name must be an alphanumeric string from 1 to 63 characters.

ip-address ipv4_address | ipv6_address

Specifies the IP address of the peer MSC server in either IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.

In Release 16.0 and higher, the MME supports DNS-based MSC selection. If DNS-based selection is configured, the DNS lookup is done first, then it will fall back to local ip address.

offline

Mark this MSC server offline for maintenance. Once this command is issued, the MME will no longer send future handover requests to this MSC server. No GTPv2 messages are generated when offline/online mode is changed.

Once the MSC server is set for offline, the online keyword must be used to return the server to online mode.

online

Mark this MSC server for online mode. Once this command is issued, the MSC server is added back into the MSC selection algorithm and normal operation is returned. By default, an MSC server is online unless the offline keyword is specified.

This command creates a mapping between the MSC ISDN number and the MSC's IP-address (either IPv4 or IPv6) to ensure location continuity for SRVCC handover. This mapping is required to include the MSV ID in the target service node IE for the Emergency_Call_Handover event.

no

Removes a specific MSC IP address mapping definition from the MME Service configuration.

ip-address

ipv4_address | ipv6_address Specifies the IP address for the MSC as an IPv4 dotted-decimal or as an IPv6 colon-separated-hexadecimal notation.

isdn

isdn_number : Enter a numeric string upto 15 digits long.

Configures which QOS the MME uses in NAS GMM QoS IE and GTPv1 Context response message when the subscriber comes to MME via a handover from a GN/GP SGSN.

gngp-imported-qos

Configures the MME to send the QoS received from GN/GP SGSN (whenever applicable).

native-eps-qos

Configures the MME to send the EPS (4G) QoS received from HSS.

This is the default setting.

Sets the retransmission counter for all type of Non-Access Stratum (NAS) messages in an MME service.

default

Resets the retransmission counter to the default value of 4.

nas_retrans_count

Sets the maximum number of retransmission of NAS messages permitted during any procedure after which the activation procedure will be discarded.

nas_retrans_count is an integer from 1 through 10. Default: 4

Configures additional PLMN IDs for this MME service. Refer to the plmn-id command to create the base PLMN identifier for an MME service. Each PLMN ID consists of the Mobile Country Code (MCC) and Mobile Network Code (MNC). A maximum of four network sharing entries can be configured per MME service. These PLMN IDs will be communicated to the eNodeBs in the S1 SETUP response and MME CFG Update messages.

no

Disables the network sharing mode on this MME service.

Caution

Removing the PLMN identifier is a disruptive operation; the MME service will be restarted.

plmnid mcc number mnc number

Sets the mobile country code (MCC) and mobile network code (MNC) of the PLMN ID for this service.

mcc number : Specifies the MCC portion of the PLMN identifier as an integer from 100 through 999.

mnc number : Specifies the MNC portion of the PLMN identifier as a 2- or 3-digit integer from 00 through 999.

mme-id group-id id

Specifies the group identifier for the group to which this MME belongs as an integer from 0 through 65535.

mme-code code

Specifies the unique code for an MME service as an integer from 0 through 255.

Configures the network resource identifier (NRI) length used for source SGSN discovery via NRI-FQDN (Fully Qualified Domain Name) based DNS resolution.

no

Removes a configured NRI length.

length length

Specifies the number of bits to be used in the P-TMSI (bits 23 to 18) to define the NRI as an integer from 1 through 8.

plmn-id mcc mcc_value mnc mnc_value

Specifies the PLMN-ID of the SGSN pool.

mcc mcc_value : Specifies the mobile country code (MCC) portion of the PLMN identifier as an integer from 100 through 999.

mnc mnc_value : Specifies the mobile network code (MNC) portion of the PLMN identifier as a 2- or 3-digit integer from 00 through 999.

Enables or Disables NR UE Security Capability IE in messages over S1AP and S10 Interfaces to the peer.

no

Disables a configuration

MME ignores "UE Additional Security Capability" received over Attach/TAU request. It does not replay (Replayed UE Additional Security Capability") in the Security Mode Command,

MME does not include NR UE Security Capability IE and UE Additional Security Capability over S1AP and S10 respectively.

Configures parameters that, when matched by another MME, specifies that MME as a peer for inter-MME relocations.

no

Removes the configured path management for Peer MME or peer Globally Unique MME Identifier (GUMMEI) or TAI match priority from this service.

echo-params interval interval retransmission-timeout retransmission-timeout max-retransmissions max-retransmissions reconnect-interval reconnect-interval

Configures the path management for Peer MME.

interval interval : Configures echo interval in seconds. interval must be an ineteger between 60 and 300.

retransmission-timeout retransmission_timeout : Configures echo retransmission timeout in seconds. retransmission_timeout must be an ineteger between 1 and 20.

max-retransmissions max-retransmissions : Configures maximum retries for echo request. max-retransmissions must be an ineteger between 0 and 15.

reconnect-interval reconnect_interval : Configures echo interval to be used once a peer node is detected to be unreachable. Retransmission is not applicable in this time. reconnect_interval must be an ineteger between 60 and 86400.

gummei mcc number mnc number group-id id mme-code code address ipv4_address

Specifies that an MME with values matching those configured in this GUMMEI is to be considered a peer MME. This variable supports the lookup of an IP address for a peer MME based on the exact match of the supporting keyword below (which make up the GUMMEI).

mcc number : Sets the mobile country code (MCC) for peer match as an integer from 100 through 999.

mnc number : Sets the mobile network code (MNC) for this peer match as a 2- or 3-digit integer from 00 through 999.

group-id id : Specifies the group identifier for the group to which this MME belongs as an integer from 0 through 65535.

mme-code code : Specifies the unique code for an MME service as an integer from 0 through 255.

address ipv4_address : Specifies the IP address of the peer MME in IPv4 dotted-decimal notation.

tai-match priority value mcc number mnc number tac { area_code | any | start_area_code to end_area_code } address ipv4_address

Specifies that an MME with values matching those configured in this Tracking Area Identifier (TAI) match, is to be considered a peer MME. This keyword provides a priority-ordered list of TAI descriptions where the Tracking Area Code (TAC) field may be either an exact value, a range of values, or a "wildcard" value. It also provides an IP address of the peer MME corresponding to the TAI description.

priority value :

mcc number : Sets the mobile country code (MCC) for peer match as an integer from 100 through 999.

mnc number : Sets the mobile network code (MNC) for this peer match as an integer from 00 through 999.

tac area_code : Sets a specific Tracking Area Code (TAC) for the peer MME match as an integer from 1 through 65535.

tac any : Specifies that any TAC value can be considered for a peer MME.

tac start_area_code to end_area_code : Specifies a range of TACs. MMEs within this range and matching the rest of the criteria in this command are to be considered peer MMEs. start_area_code and end_area_code are integers from 1 through 268435455.

address ipv4_address : Sets a specific IP address for this TAI peer MME match in IPv4 dotted-decimal notation.

Statically configures Routing Area Identity (RAI) parameters of the peer SGSN environment to facilitate MME-SGSN relocations over S3 or Gn/Gp interfaces.

no

Deletes the specified peer-SGSN RAI parameter configuration from the MME Service configuration.

mcc mcc_value

Specifies the mobile country code (MCC) portion of the PLMN identifier as an integer from 100 through 999.

mnc mnc_value

Specifies the mobile network code (MNC) portion of the PLMN identifier as a 2- or 3-digit integer from 00 through 999.

nri value

Specifies the Network Resource Identifier (NRI) value, used as an additional identity, as an integer from 0 through 65535.

rac value

Specifies the Routing Area Code (RAC) used to facilitate a lookup for a specific peer SGSN as an integer from 0 through 255.

lac value

Specifies the Location Area Code (LAC) value, used to facilitate a lookup for a specific peer SGSN, as an integer from 0 through 65535.

address ip_address

Specifies an existing IP address of the peer SGSN in IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.

capability [ gn ] [ gp ] [ s16 ] [ s3 ]

Configures the GTP interface capability of the peer SGSN.

gn : Specifies that the peer SGSN is capable of communication over the Gn interface.

gp : Specifies that the peer SGSN is capable of communication over the Gp interface.

s16 : Specifies that the peer SGSN is capable of communication over the S16 interface.

s3 : Specifies that the peer SGSN is capable of communication over the S3 interface.

Configures echo parameters for peer SGSN with GN/GP Capability.

no

Removes the path management configuration for peer SGSN with Gn/Gp capability.

interval interval : Configures echo interval in seconds. interval must be an ineteger between 60 and 300.

retransmission-timeout retransmission_timeout : Configures echo retransmission timeout in seconds. retransmission_timeout must be an ineteger between 1 and 20.

max-retransmissions max-retransmissions : Configures maximum retries for echo request. max-retransmissions must be an ineteger between 0 and 15.

reconnect-interval reconnect_interval : Configures echo interval to be used once a peer node is detected to be unreachable. Retransmission is not applicable in this time. reconnect_interval must be an ineteger between 60 and 86400.

Statically configures Radio Network Controller Identification (RNC-ID) parameters of the peer SGSN environment to facilitate MME-SGSN relocations over S3 or Gn/Gp interfaces.

no

Deletes the specified peer-SGSN RAI parameter configuration from the MME Service configuration.

mcc mcc_value

Specifies the mobile country code (MCC) portion of the PLMN identifier as an integer from 100 through 999.

mnc mnc_value

Specifies the mobile network code (MNC) portion of the PLMN identifier as a 2- or 3-digit integer from 00 through 999.

rnc value

Specifies the Radio Network Controller (RNC) identification number used to facilitate a lookup for a specific peer SGSN as an integer from 0 through 65535.

address ip_address

Specifies an existing IP address of the peer SGSN in IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.

capability [ gn ] [ gp ] [ s16 ] [ s3 ]

Configures the GTP interface capability of the peer SGSN.

gn : Specifies that the peer SGSN is capable of communication over the Gn interface.

gp : Specifies that the peer SGSN is capable of communication over the Gp interface.

s16 : Specifies that the peer SGSN is capable of communication over the S16 interface.

s3 : Specifies that the peer SGSN is capable of communication over the S3 interface.

Configures the IPv4 or IPv6 address of the PDN Gateway (P-GW), specifies the protocol for S5 and S8 interfaces, and sets other parameters within the MME service. By default S5 and S8 use GTP protocol for this.

no

Removes a previously configured IP address for a P-GW along with the S5 and S8 interface of P-MIP protocol type, and other parameters from this MME service.

ipv4_address | ipv6_address

Specifies the IP address of the P-GW in IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.

collocated-node

Configures the collocation name to select the collocated S/PGW node IP addresses for MME.

collocated_node_name must be a string of size 1 to 255.

s5-s8-protocol pmip

Specifies that Proxy-MIP is to be used for S5 and S8 interfaces with the P-GW. By default S5 and S8 interface uses GTP protocol.

pmip Sets the protocol to Proxy-MIP for S5 and S8 interface.

ue-usage-type

Configures the ue-usage-type for the gateway. ue_usage_type_value must be an integer between 1 through 255.

weight weight

Specifies the weight (preference) assigned to the address P-GW for load balancing. weight is an integer from 1 through 100 where 1 is the least preferred and 100 is the most preferred. If no weight is specified, the P-GW address is assigned a default weight of 1.

If a weight is assigned to an address, the weights of the P-GW(s) (that are operational) are totaled, and then a weighted round-robin selection is used to distribute new primary PDP contexts among the P-GW(s) according to their weights. As with all weighted round-robin algorithms, the distribution does not look at the current distribution, but simply uses the weights to distribute new requests. For example, two P-GWs assigned weights of 70 and 30 would distribute 70% of calls to one, and 30% to the other. The sum of all weights do not need to total 100.

Configures the Public Land Mobile Network (PLMN) identifier for this MME service. The PLMN identifier consists of the Mobile Country Code (MCC) and Mobile Network Code (MNC). A single PLMN ID can be configured per MME service.

no

Removes the configured PLMN identifier for this MME service.

Caution

Removing the PLMN identifier is a disruptive operation; the MME service will be restarted.

mcc mcc_value

Specifies the mobile country code (MCC) portion of the PLMN identifier as an integer from 100 through 999.

mnc mnc_value

Specifies the mobile network code (MNC) portion of the PLMN identifier as a 2- or 3-digit integer from 00 through 999.

Configures parameters for the UE Attach procedure.

default

Returns the command to its default setting. Default values are:

imei-query-type : none

reject-non3gpp-char-apn : Reject Attach request with non-3GPP character APN

set-ue-time : disabled

imei-query-type { imei | imei-sv | none }

Configures the IMEI query type for UE attach.

• imei : Specifies that the MME is required to query the UE for its International Mobile Equipment Identity (IMEI).

• imei-sv : Specifies that the MME is required to query the UE for its International Mobile Equipment Identity - Software Version (IMEI-SV).

• none : Specifies that the MME does not need to query for IMEI or IMEI-SV.

verify-equipment-identity [ allow-on-eca-timeout | deny-greylisted | deny-unknown | verify-emergency ]

Specifies that the identification (IMEI or IMEI-SV) of the UE is to be performed by the Equipment Identity Register (EIR) over the S13 interface.

• allow-on-eca-timeout : Configures the MME to allow equipment that has timed-out on ECA during the attach procedure.

• deny-greylisted : Configures the MME to deny grey-listed equipment during the attach procedure.

• deny-unknown : Configures the MME to deny unknown equipment during the attach procedure.

• verify-emergency : Configures the MME to ignore the IMEI validation of the equipment during the attach procedure in emergency cases. This keyword is only supported in release 12.2 and higher.

reject-non3gpp-char-apn

Enables MME to immediately reject the attach procedure without any APN remapping, if the UE requested APN contains non 3GPP characters. The attach procedure is rejected with ESM cause-code #27 "missing or unknown APN" and T3396 value IE is included in the Attach reject message.

set-ue-time { disable | enable [ prefer-mme | prefer-msc ] }

Configures the MME to set the time in the UE during the Attach procedure. Default: disabled .

[ prefer-mme | prefer-msc ] : Specifies which UE-time to use when delivering EMM messages to the UE for cases when a UE performs combined registration.

prefer-mme : The MME shall always send its UE-time information (based on the MME's own settings), and ignore any EMM Information messages sent by the MSC.

prefer-msc : In cases where a successful Location Update is performed to a MSC, the MME shall NOT send MME configured information to the UE, and shall transmit only MSC-sent information. In cases where a Location Update procedure is not required (for example, for UEs that are performing EPS only ATTACH), or in cases where the Location Update Procedure is unsuccessful, the MME shall send the MME configured information.

Sets the handling for ERAB-SETUP-RESPONSE failure message.

policy erab-setup-rsp-fail retry-timer retry_timer max-retries max_retries { default | no } policy erab-setup-rsp-fail retry-timer

Configures the IMEI query type for UE attach.

• no Disables the retry timer mechanism.

• default Restores the default value to existing behavior by disabling the retry timer mechanism.

• policy Specifies the user-defined policies like idle mode detach behavior etc.

• erab-setup-rsp-fail Sets the handling for ERAB-SETUP-RESPONSE failure message.

• retry-timer retry_timer Configures the retry timer for ERAB Setup Procedure. retry_timer must be an integer between 1 and 15.

• max-retries max_retries Configures the maximum retry limit for ERAB Setup Procedure. max_retries must be an integer between 1 and 10.

Configures the user-defined behavioral policies of session management for an LTE subscriber in an MME service.

default

Sets the policy configuration to the default behavior for subscriber IDLE mode Detach. The default behavior is Detach implicit.

idle-mode detach

Configures the IDLE mode Detach behavior of a UE.

detach

Defines the Detach procedure while the UE is in IDLE mode.

explicit

Enables the Explicit Detach while a UE is in IDLE mode. The system will page the UE before Detach procedure is started, and then perform the Explicit Detach procedure.

implicit

Enables the Implicit Detach while a UE is in IDLE mode. The system never sends any message to the UE before Detach, and executes the Implicit Detach procedure immediately. This is the default behavior.

Configures inter-RAT policy settings.

no

Disables the function.

ignore-sgsn-context-id

Configures the MME to ignore any Context-ID mismatch between HSS and HLR and to use the Context-ID from the HSS to override the Context-ID from the source SGSN. If this option is disabled (default), the MME will drop the PDN when there is a Context-ID mismatch.

indirect-forwarding-tunnels always

Enables establishment of Indirect Data Forwarding Tunnels (IDFT) for Gn/Gp-based Serving Radio Network Subsystem (SRNS) relocations. By default, the MME is configured to never establish IDFT.

select-topologic-sgw interface gn

Configures the MME to select the S-GW based on topological closeness to the P-GW for Gn/Gp handoff scenarios. Weighted distribution will occur across node pairs in the same degree and same order. By default this functionality is disabled.

During inter-RAT Gn/Gp based handoffs, the MME does not learn the P-GW host name from the old Gn/Gp SGSN as part of UE context. Without the P-GW host name, selection of the topologically closest S-GW is not possible per 3GPP standards. This functionality enables the MME to use a proprietary mechanism for learning the P-GW host name. For S3 & S10 cases, there is no need to enable this command, as GTPv2 allows the P-GW host name to be communicated to/from S4-SGSN/MME.

This functionality requires the gw-selection co-location or gw-selection topology commands to be enabled in the call-control-profile mode.

Note: The P-GW is anchored in the inter-RAT handoff scenarios, so regardless of the preferred weight specified in gw-selection , the MME always considers the S-GW's weight for weighted distribution purposes.