S1-Flex Feature Parameter Description: Issue Date

eRAN
S1-flex Feature Parameter

Description
Issue 04
Date 2020-07-27
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. i

eRAN
S1-flex Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN16.1 04 (2020-07-27)..................................................................................................................................................1
1.2 eRAN16.1 03 (2020-07-03)..................................................................................................................................................1
1.3 eRAN16.1 02 (2020-05-21)..................................................................................................................................................2
1.4 eRAN16.1 01 (2020-03-30)..................................................................................................................................................2
1.5 eRAN16.1 Draft A (2020-01-15)........................................................................................................................................ 2
2 About This Document.............................................................................................................4

2.1 General Statements................................................................................................................................................................ 4
2.2 Applicable RAT......................................................................................................................................................................... 5
2.3 Features in This Document.................................................................................................................................................. 5
2.4 Feature Differences Between NB-IoT and FDD............................................................................................................ 5
2.5 Feature Differences Between FDD and TDD................................................................................................................. 5
3 Related Concepts..................................................................................................................... 6
3.1 TA and TAL................................................................................................................................................................................. 6
3.2 MME Pool and MME Pool Area..........................................................................................................................................7
3.3 MME Identities......................................................................................................................................................................... 8
3.4 AS and NAS States.................................................................................................................................................................. 8
3.4.1 AS States................................................................................................................................................................................. 9
3.4.2 NAS States........................................................................................................................................................................... 10
4 S1-flex...................................................................................................................................... 13
4.1 Principles.................................................................................................................................................................................. 13
4.1.1 MME Selection Based on NNSF Policies.................................................................................................................... 13
4.1.2 MME Selection Based on the High Rank Policy......................................................................................................20
4.1.2.1 MME Pool Selection...................................................................................................................................................... 21
4.1.2.2 MME Selection from an MME Pool......................................................................................................................... 25
4.1.2.3 MME Selection Based on Cell Configurations...................................................................................................... 29
4.1.2.4 MME Selection Based on DCN Range.....................................................................................................................29
4.1.3 Load Rebalancing Among MMEs................................................................................................................................. 32
4.1.4 MME Overload Handling................................................................................................................................................ 33
4.1.5 S1 Interface Failure Handling........................................................................................................................................38
4.2 Network Analysis.................................................................................................................................................................. 38
4.2.1 Benefits................................................................................................................................................................................. 38
Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
S1-flex Feature Parameter Description Contents
4.2.2 Impacts.................................................................................................................................................................................. 39
4.3 Requirements......................................................................................................................................................................... 39
4.3.1 Licenses................................................................................................................................................................................. 39
4.3.2 Software................................................................................................................................................................................39
4.3.3 Hardware.............................................................................................................................................................................. 40
4.3.4 Networking.......................................................................................................................................................................... 40
4.3.5 Others.................................................................................................................................................................................... 41
4.4 Operation and Maintenance............................................................................................................................................. 42
4.4.1 Data Configuration........................................................................................................................................................... 42
4.4.1.1 Data Preparation............................................................................................................................................................ 42
4.4.1.2 Using MML Commands............................................................................................................................................... 47
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 48
4.4.2 Activation Verification..................................................................................................................................................... 48
4.4.3 Network Monitoring......................................................................................................................................................... 52
5 Parameters.............................................................................................................................. 53
6 Counters.................................................................................................................................. 54
7 Glossary................................................................................................................................... 55
8 Reference Documents...........................................................................................................56
Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
S1-flex Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN16.1 04 (2020-07-27)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised some descriptions in the following sections:
● 4.1.1 MME Selection Based on NNSF Policies

● 4.1.2 MME Selection Based on the High Rank Policy
1.2 eRAN16.1 03 (2020-07-03)

Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
1.3 eRAN16.1 02 (2020-05-21)

Technical Changes
None
Editorial Changes
1.4 eRAN16.1 01 (2020-03-30)

Technical Changes
None
Editorial Changes
1.5 eRAN16.1 Draft A (2020-01-15)

This issue introduces the following changes to eRAN15.1 02 (2019-09-05).
Technical Changes
Change Description Parameter RAT Base Station Model
Change
Added the MME selection Added the FDD ● 3900 and 5900 series
for UEs based on MME MME_CAPACI TDD base stations
capacities. For details, see TY_BASED_SE ● DBS3900 LampSite
4.1.2 MME Selection LECT_SW and DBS5900
Based on the High Rank option to the LampSite
Policy. GlobalProcSw
itch.MmeSele ● BTS3911E
ctProcSwitch
parameter.

eRAN
Change Description Parameter RAT Base Station Model

Change
Changed the name of CME None FDD ● 3900 and 5900 series
to MAE-Deployment. TDD base stations
● DBS3900 LampSite
and DBS5900
LampSite
● BTS3911E
Editorial Changes
None

eRAN
S1-flex Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a
description does not apply to all RATs, the specific RAT that it does apply to will
be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-
MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.

eRAN
S1-flex Feature Parameter Description 2 About This Document
2.2 Applicable RAT

This document applies to FDD/NB-IoT/TDD.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Chapter/Section
LBFD-001018 S1-flex 4 S1-flex
MLBFD-12000310 S1-flex 4 S1-flex
This document describes the following TDD features.
Feature ID Feature Name Chapter/Section
TDLBFD-001018 S1-flex 4 S1-flex
2.4 Feature Differences Between NB-IoT and FDD

NB-IoT Feature FDD Feature Difference Chapter/Section
MLBFD-12000310 LBFD-001018 S1- None 4 S1-flex

S1-flex flex
2.5 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Chapter/Section
LBFD-001018 S1- TDLBFD-001018 None 4 S1-flex

flex S1-flex

eRAN
S1-flex Feature Parameter Description 3 Related Concepts
3 Related Concepts
3.1 TA and TAL

Tracking Area
Tracking area (TA) is a concept introduced to the LTE/SAE system for UE location
management.
A network coverage area is divided into multiple TAs, which are identified by
tracking area codes (TACs). A TA consists of a series of cells with the same TAC
that provide continuous coverage. See Figure 3-1 for details.
Figure 3-1 TA
NOTE
● A cell can belong to only one TA.

● Cells served by an eNodeB can belong to different TAs. For example, as shown in Figure
3-1, cells served by eNB2 belong to either TA1 or TA2.
● Cells included in a TA can be served by different eNodeBs. For example, as shown in
Figure 3-1, TA1 consists of cells served by eNB2, eNB3, and eNB5.

eRAN
Tracking Area List

A tracking area list (TAL) consists of multiple TAs.
An MME allocates a TAL to a UE when the UE registers with the network or when
the UE updates its location. All TAs in the TAL are served by the same MME.
The UE initiates a location update when it moves out of the area covered by the
allocated TAL, not when it moves within the TAs in the TAL.
3.2 MME Pool and MME Pool Area

S1-flex introduces the concepts of the MME pool and MME pool area. An MME
pool consists of one or multiple MMEs. These MMEs serve the same area called
MME pool area.
To learn the concepts of MME pool and MME pool area, see:
● 3.1 "Definitions" and 4.3.7.2 "Load balancing between MMEs" in 3GPP TS

23.401 V10.7.0
● 19.2.1.9 "MME Load balancing Function" in 3GPP TS 36.300 V10.7.0
Figure 3-2 shows the relationships among MME pools, MME pool areas, and
eNodeBs.
Figure 3-2 Relationships between MME pools and MME pool areas
● Each MME in an MME pool connects to all eNodeBs in the MME pool area.
● Each eNodeB in the MME pool area connects to all MMEs in the MME pool.
● All eNodeBs in the same TA connect to MMEs in the same way.
● An MME pool area consists of one or multiple complete TAs.

eRAN
● A UE does not need to change its serving MME when moving within the MME
pool area.
● MME pool areas may overlap each other, and the overlapping area must be
one or more complete TAs.
● When MME pool areas are overlapped, the TAs in the overlapping areas are
served by multiple MME pools. Each eNodeB in these TAs is connected to all
the MMEs that serve the area.
NOTE
Overlapping areas reduce the number of tracking area updates (TAUs) when a UE
moves in and out of an MME pool area repeatedly. For example, a central business
district (CBD) can be planned as an overlapping area to reduce the number of TAUs
when UEs move between the CBD and other areas.
3.3 MME Identities

eNodeBs use different MME identities (described in this section) to identify MMEs.
MMEC
An MME code (MMEC) uniquely identifies an MME within an MME pool. Different
schemes for planning MMECs are available based on whether MME pool areas are
overlapped. For details, see MMEC Planning.
NOTE
The RRCConnectionRequest message that a UE sends to the eNodeB contains the S-

temporary mobile subscriber identity (S-TMSI), and the S-TMSI contains the MMEC.
MMEI
An MME identifier (MMEI) uniquely identifies an MME within a PLMN. It is
constructed from an MME group identifier (MMEGI, which uniquely identifies an
MME pool within a PLMN) and an MMEC; that is, MMEI = MMEGI + MMEC.
GUMMEI
A globally unique MME identifier (GUMMEI) identifies an MME globally. It is
constructed from a PLMN ID plus an MMEI; that is, GUMMEI = PLMN ID + MMEI.
NOTE
The information element (IE) RegisterMME in the RRCConnectionSetupComplete message

sent from a UE to the eNodeB indicates the GUMMEI.
3.4 AS and NAS States

Table 3-1 describes the storage of UE contexts in different access stratum (AS)/
non-access stratum (NAS) states.

eRAN
Table 3-1 Storage of UE contexts in different AS/NAS states
AS State NAS State Whether the Whether the

eNodeB Stores MME Stores the
the UE Context UE Context
RRC-IDLE ● EMM- No No
DEREGISTERED
● ECM-IDLE
RRC-IDLE ● EMM- No Yes

REGISTERED
● ECM-IDLE
RRC-CONNECTED ● EMM- Yes Yes

REGISTERED
● ECM-
CONNECTED
3.4.1 AS States
AS states are the connection states between a UE and an eNodeB. Based on
whether an RRC connection is set up, there are two AS states:
● RRC_IDLE
In this state, the eNodeB does not have the UE context. It can send system
information and paging messages to the UE.
● RRC_CONNECTED
In this state, the eNodeB has the UE context. It can order the UE to perform
data transmission and handovers, notify the UE of scheduling information,
receive information such as the channel quality from the UE, and send system
information to the UE. For LTE NB-IoT, it can order the UE to perform data
transmission and notify the UE of scheduling information.
After a UE sets up an RRC connection, it enters the RRC_CONNECTED state. In this

state, the UE can exchange data with the network. After the RRC connection is
released, the UE switches from the RRC_CONNECTED state to the RRC_IDLE state.
Figure 3-3 shows the transition between AS states.
Figure 3-3 Transition between AS states

eRAN
3.4.2 NAS States

NAS states have the following two management sub-classes:
● EPS mobility management (EMM)

EMM states are the mobility management states that result from the mobility
management procedures.
● EPS connection management (ECM)
ECM states describe the signaling connectivity between the UE and the
evolved packet core (EPC).
For details, see 4.6 "EPS Mobility Management and Connection Management
states" in 3GPP TS 23.401 V10.7.0.
EMM
Based on the UE mobility management states on the EPC, NAS states are
classified as follows:
● EMM-DEREGISTERED
In the EMM-DEREGISTERED state, the EMM context in an MME holds no valid
location or routing information for the UE. The UE is unreachable by the MME
because the UE location is unknown.
● EMM-REGISTERED
In the EMM-REGISTERED state, the MME sets up and stores the UE context
and provides services for the UE.
Figure 3-4 shows the transition between the EMM-DEREGISTERED and EMM-
REGISTERED states.
● The UE enters the EMM-REGISTERED state after a successful attach or TAU

procedure.
During the conversion process, the MME assigns a temporary ID called M-
TMSI to uniquely identify the UE within the MME. The M-TMSI and the MMEC
form an S-TMSI. The S-TMSI, which is unique within a TA, is used to identify
the UE during paging and UE access.
● After the detach procedure is performed, the state is changed to EMM-
DEREGISTERED in both the UE and MME.
Figure 3-4 Transition between EMM states

eRAN
ECM
Based on the UE signaling connectivity states managed by the EPC, NAS states are
classified as follows:
● ECM-IDLE
A UE is in the ECM-IDLE state when there is no NAS signaling connection
between the UE and the EPC. In this state,
– A UE performs cell selection or reselection.
– eNodeBs do not have contexts for the UE.
– There is no dedicated S1-MME connection for the UE between MMEs and
eNodeBs.
– The MME and UE maintain the TAL for the UE if the UE is still in the
EMM-REGISTERED state.
● ECM-CONNECTED
When a UE needs to transmit or receive data, it must access a cell and enter
the ECM-CONNECTED state. In this state:
– The eNodeB sets up and saves the UE context.
– There is a signaling connection between the UE and the MME.
– The UE is also in the EMM-REGISTERED state when the UE is in the ECM-
CONNECTED state.
Figure 3-5 and Figure 3-6 show transitions between the ECM-IDLE and ECM-
CONNECTED states.
● When switching from the ECM-IDLE state to the ECM-CONNECTED state, the
UE attempts to access the current cell. After receiving the access request from
the UE, the eNodeB sends the UE's NAS information to the MME and sets up
a dedicated S1-MME connection for the UE.
NOTE
A UE accesses the current cell by initiating a service request or by responding to a

paging request.
A UE responding to a paging request must be in the EMM-REGISTERED state.
● When the signaling connection between the UE and the MME is released or
interrupted, the UE switches from the ECM-CONNECTED state to the ECM-
IDLE state.

eRAN
Figure 3-5 ECM state transitions of EMM-REGISTERED UEs
Figure 3-6 ECM state transitions of EMM-DEREGISTERED UEs

eRAN
S1-flex Feature Parameter Description 4 S1-flex
4 S1-flex
4.1 Principles
With S1-flex, an eNodeB in the LTE/SAE network sets up an S1-MME connection
with each MME in an MME pool. When a UE accesses the network through the
eNodeB, the eNodeB selects an MME from the pool for the UE and sets up a
dedicated S1-MME connection with the MME. S1-flex involves the following
techniques:
● The eNodeB selects an MME based on the following policies:
– If a UE provides an MME identifier, the eNodeB selects the MME
identified by the MME identifier preferentially. This selection policy is NAS
node selection function (NNSF). For details, see 4.1.1 MME Selection
Based on NNSF Policies.
– If a UE does not provide an MME identifier or the MME identified by the
UE-provided MME identifier is unavailable, the eNodeB selects an MME
for the UE based on the priorities, capacities, and loads of MMEs. For
details, see 4.1.2 MME Selection Based on the High Rank Policy.
● MME load rebalancing balances the loads among all the MMEs in an MME
pool. For details, see 4.1.3 Load Rebalancing Among MMEs.
● eNodeBs handle MME overload according to the instructions in an Overload
Start message sent from the MME to the eNodeBs. For details, see 4.1.4 MME
Overload Handling.
● If the status of an S1 interface between an eNodeB and an MME is abnormal,
the eNodeB releases or redirects UEs in the RRC_CONNECTED state over this
S1 interface. For details, see 4.1.5 S1 Interface Failure Handling.
With S1-flex, the eNodeB selects MMEs for the following two types of UEs:
● LTE UEs
● UEs transferred back from a GERAN or UTRAN to E-UTRAN by cell reselection
4.1.1 MME Selection Based on NNSF Policies

During the process of UE switching from the ECM-IDLE state to the ECM-
CONNECTED state, the eNodeB must set up a dedicated S1-MME connection to

eRAN
the MME. If the eNodeB is connected to multiple MMEs, the eNodeB must select
one of these MMEs to set up a dedicated S1-MME connection. The function that
the eNodeB uses to select an MME based on the MME identifier reported by the
UE is called NNSF.
When a UE accesses the network through an eNodeB, the eNodeB must select one
MME from the connected MMEs and set up a dedicated S1-MME connection for
the UE. The dotted box in Figure 4-1 shows the NNSF procedure.
Figure 4-1 NNSF procedure
The detailed NNSF procedure is as follows:
1. The UE accesses the network through the eNodeB.

2. The eNodeB checks whether the UE provides an MME identifier.
If... Then...
The UE is in the EMM-REGISTERED The UE sends the identity of the

state registered MME to the eNodeB
when accessing the network.

eRAN
If... Then...
The UE is in the EMM- There is no registered MME for the

DEREGISTERED state UE and therefore the UE is unable to
provide an MME identifier to the
eNodeB.
3. The eNodeB decides whether it can find the MME that is identified by the
MME identifier provided by the UE.
If... Then...
The eNodeB finds the MME based The eNodeB goes to 4.

on NNSF policies
The eNodeB does not find the MME The eNodeB goes to 5.
based on NNSF policies
4. Based on the MME status and access reason of the UE, the eNodeB decides
whether the UE can continue to use the MME.
If... Then...
The UE can continue to use the The eNodeB goes to 6.

MME
The UE cannot continue to use the The eNodeB goes to 5.

MME
5. The eNodeB selects an MME based on the high rank policy. For details, see
4.1.2 MME Selection Based on the High Rank Policy.
6. The eNodeB sets up a dedicated S1-MME connection to the MME.
NNSF Policies
Figure 4-2 shows an example of the eNodeB searching for the required MME for
the UE.

eRAN
Figure 4-2 Example of the eNodeB searching for the required MME for the UE
If the eNodeB receives an RRCConnectionRequest message that contains an S-

TMSI from a UE, the eNodeB preferentially matches the MMEC IE contained in the
S-TMSI against the configuration information sent from the MME to find the
required MME. If the RRCConnectionRequest message does not contain an S-TMSI,
and the RRCConnectionSetupComplete message sent from the UE to the eNodeB
contains the RegisterMME IE, the eNodeB matches the RegisterMME IE against
the configuration information sent from the MME to find the required MME. The
RRCConnectionSetupComplete message also contains the GUMMEI TYPE IE for UE
type determination. For details, see UE Type Determination.
NOTE
Currently, the RRCConnectionSetupComplete message does not contain the GUMMEI TYPE
IE for NB-IoT.
NNSF policies are as follows:

● Strict match: The eNodeB selects the MME whose MMEGI and MMEC match
those sent by the UE. This policy is controlled by the
MME_STRICT_SELECTION_SWITCH option of the
CnOperator.OperatorFunSwitch parameter.
● Loose match: The eNodeB selects the MME whose MMEC matches that sent
by the UE.
If MME selection based on NNSF policies fails, the high rank policy is used. For
details, see 4.1.2 MME Selection Based on the High Rank Policy.
When the MMESELECTALGOSWITCHFORGUUE option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter is selected, the high rank
policy can be directly used for UEs transferred back from a GERAN or UTRAN to E-
UTRAN by cell reselection.
Under certain parameter settings, the eNodeB preferentially uses specific policies
to select MMEs for the two types of UEs. For details, see Table 4-1.

eRAN
Table 4-1 MME selection policies

MME_STRICT MMESELECTA NNSFENHAN UE Type MME
_SELECTION_ LGOSWITCHF CEMENTSWI Selection
SWITCH ORGUUE TCH Option Policy
Option of Option of of
CnOperator. GlobalProcS GlobalProcS
OperatorFun witch.MmeSe witch.MmeSe
Switch lectProcSwitc lectProcSwitc
h h
Selected Selected Selected A UE transferred High rank
back from a
GERAN or
UTRAN to E-
UTRAN by cell
reselection
An LTE UE Strict
match >
High rank
Selected Selected Deselected A UE transferred High rank

back from a
GERAN or
UTRAN to E-
UTRAN by cell
reselection
An LTE UE Strict
match >
High rank
Selected Deselected Selected A UE transferred Strict

back from a match >
GERAN or High rank
UTRAN to E-
UTRAN by cell
reselection
An LTE UE Strict
match >
High rank
Selected Deselected Deselected A UE transferred Strict

back from a match >
GERAN or High rank
UTRAN to E-
UTRAN by cell
reselection
An LTE UE Strict
match >
High rank

eRAN

h h
Deselected Selected Selected A UE transferred High rank
back from a
GERAN or
UTRAN to E-
UTRAN by cell
reselection
An LTE UE Strict
match >
Loose
match >
High rank
Deselected Selected Deselected A UE transferred High rank

back from a
GERAN or
UTRAN to E-
UTRAN by cell
reselection
An LTE UE Strict
match >
High rank
Deselected Deselected Selected A UE transferred Strict

back from a match >
GERAN or Loose
UTRAN to E- match >
UTRAN by cell High rank
reselection
An LTE UE Strict
match >
Loose
match >
High rank
Deselected Deselected Deselected A UE transferred Loose

back from a match >
GERAN or High rank
UTRAN to E-
UTRAN by cell
reselection

eRAN

h h
An LTE UE Strict
match >
High rank
NOTE
In the preceding table, ">" indicates that the policy on its left has a higher priority than that
on its right. For example, "Strict match > Loose match > High rank" indicates that the strict
match policy is preferentially used; if the strict match policy fails, the loose match policy is
used; if the loose match also fails, the high rank policy is used.
UE Type Determination
● If the RRCConnectionSetupComplete message reported by the UE contains the
GUMMEI TYPE IE, the eNodeB determines the UE type based on the value of
the IE, as described in Figure 4-2. For details, see 3GPP TS 36.300.
NOTE
This enhanced algorithm for deciding a UE type applies only to 3GPP Release 10 UEs.
In addition, the MME release as indicated by S1Interface.MmeRelease must be
Release_R10(Release 10) or later and the S1 interface must support the GUMMEI
TYPE IE.
If... Then...
The IE value is native The UE is an LTE UE.
The IE value is mapped The UE is a GSM or UMTS UE.
● If the RRCConnectionSetupComplete message reported by the UE does not

contain the GUMMEI TYPE IE, the eNodeB determines the UE type based on
the value of the most significant bit of MMEGI in GUMMEI. For details, see
section 2.8.2.2 "Mapping from RAI and P-TMSI to GUTI" in 3GPP TS 23.003
V10.10.0.
If... Then...
The value is 1 The UE is an LTE UE.
The value is 0 The UE is a GSM or UMTS UE.

eRAN
NOTE
When the eNodeB uses the most significant bit of the MMEGI to decide a UE type and
the operator has set the most significant bit of the LAC of the GSM or UMTS network
to 1, the eNodeB decides a UE as an LTE UE if the UE has fallen back from the LTE
network to the GSM or UMTS network and then reselected to the LTE network.
4.1.2 MME Selection Based on the High Rank Policy

If a UE does not provide an MME identifier or the MME identified by the UE-
provided MME identifier is unavailable, the eNodeB selects an appropriate MME in
the MME pool to provide services for the UE. Figure 4-3 shows how the eNodeB
selects such an MME.
Figure 4-3 High-rank-policy-based MME selection procedure
If the MME_CAPACITY_BASED_SELECT_SW option of the

GlobalProcSwitch.MmeSelectProcSwitch parameter is deselected:
● The eNodeB selects an MME pool based on the priorities, network topologies,
and average loads of MME pools. For details, see 4.1.2.1 MME Pool
Selection.

eRAN
● The eNodeB selects an MME based on the priorities, capacities, and average
loads of MMEs in the MME pool. For details, see 4.1.2.2 MME Selection from
an MME Pool.
If the MME_CAPACITY_BASED_SELECT_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter is selected:
● The eNodeB selects an MME pool based on the priorities, network topologies,
and capacity proportions of MME pools. For details, see 4.1.2.1 MME Pool
Selection.
● The eNodeB selects an MME based on the priorities and capacity proportions
of MMEs in the MME pool. For details, see 4.1.2.2 MME Selection from an
MME Pool.
NOTE
● When separate MMEs have been configured for the FDD, TDD, and NB-IoT cells served
by the same eNodeB, the eNodeB selects corresponding MMEs for UEs accessing from
the FDD, TDD, or NB-IoT cells. In this scenario, the eNodeB selects an MME for a UE
based only on MME capacities and loads but not the MME pool and MME priorities. For
details, see 4.1.2.3 MME Selection Based on Cell Configurations.
● When a UE for which control plane CIoT EPS optimization is applied accesses an NB-IoT
cell, the eNodeB can select an MME only from those supporting control plane CIoT EPS
optimization for NB-IoT. If the MmeCapInfo.NbCiotEpsOptCap parameter is set to CP,
the MME supports control plane CIoT EPS optimization. After the eNodeB determines a
list of MMEs supporting control plane CIoT EPS optimization for NB-IoT, the MME
selection steps are the same as those for FDD or TDD. When a UE for which user plane
CIoT EPS optimization is applied accesses an NB-IoT cell, the eNodeB preferentially
selects an MME from those supporting user plane CIoT EPS optimization for NB-IoT for
the UE. If such an MME is unavailable, the eNodeB selects an MME from those
supporting control plane CIoT EPS optimization for NB-IoT. If the
MmeCapInfo.NbCiotEpsOptCap parameter is set to CP_UP, the MME supports control
plane and user plane CIoT EPS optimization.
4.1.2.1 MME Pool Selection

The procedure for selecting an MME pool varies according to the settings of the
MME_CAPACITY_BASED_SELECT_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter.
● If this option is deselected, an eNodeB selects an MME pool based on
priorities followed by network topologies and average loads, as shown in
Figure 4-4.
● If this option is selected, the eNodeB selects an MME pool based on the
priorities followed by network topologies and capacity proportions, as shown
in Figure 4-5.

eRAN
Figure 4-4 MME pool selection procedure (with the

MME_CAPACITY_BASED_SELECT_SW option deselected)
Figure 4-5 MME pool selection procedure (with the

MME_CAPACITY_BASED_SELECT_SW option selected)
The following describes the priorities, network topologies, average loads, and
capacity proportions of MME pools.
MME Pool Priority

● Deciding whether MME pools have the same priorities
Each MME connected to an eNodeB is configured with the MME Selection
Priority (S1.Priority in endpoint configuration mode or S1Interface.Priority
in link configuration mode). The highest MME Selection Priority in an MME
pool is regarded as the priority of the MME pool.

eRAN
NOTE
● In endpoint configuration mode, the MME Selection Priority can be modified by

running the MOD S1 command. In link configuration mode, the MME Selection
Priority can be modified by running the MOD S1INTERFACE command.
● Regardless of whether the S1 interface is configured in endpoint mode or link
mode, after the corresponding MME selection priority configuration takes effect,
the eNodeB always uses the MME selection priority of an MME specified by the
S1Interface.Priority parameter.
● Selecting an MME pool based on priorities
If MME pools have different priorities, the eNodeB selects an MME pool with
the highest priority for a UE.
Network Topology
● Deciding whether network topologies are the same
Through signaling exchange over X2 interfaces, each eNodeB obtains the
information about the MME pools to which its neighboring eNodeBs are
connected. If an eNodeB is connected to the same MME pool as a
neighboring eNodeB, the two eNodeBs belong to the same MME pool area.
When a UE accesses eNodeB 5 in Figure 4-6, eNodeB 5 finds through the X2
interface:
– eNodeB 1, eNodeB 2, eNodeB 3, eNodeB 4, and eNodeB 6 are connected
to MME pool 1. Then, eNodeB 5 records the neighboring eNodeBs that
belong to MME pool area 1.
– eNodeB 3, eNodeB 4, and eNodeB 6 are connected to MME pool 2. Then,
eNodeB 5 records the neighboring eNodeBs that belong to MME pool
area 2.
NOTE
● Topologies between eNodeB5 and its neighboring eNodeBs are different in MME
pool areas 1 and 2, because the numbers of its neighboring eNodeBs in the two
MME pool areas are different.
● An X2 interface does not need to be configured between eNodeBs because the
control plane CIoT EPS optimization scheme of NB-IoT does not involve signaling
interaction over the X2 interface. In this case, an MME pool cannot be selected
based on topologies. If an X2 interface is configured, an MME pool can be selected
based on topologies.
Figure 4-6 Network topologies of the eNodeB where the UE accesses

eRAN
● Selecting an MME pool based on the network topologies

An eNodeB selects an MME pool serving the maximum number of its
neighboring eNodeBs to reduce the probability that the serving MME for the
UE will be changed. Use Figure 4-6 as an example.
If... Then...
If a UE The serving MME must be changed when the UE moves out

selects MME of MME pool area 1. For example: when the UE moves to
pool 1 the coverage of eNodeB 10 or eNodeB 11.
If a UE The serving MME must be changed when the UE moves out

selects MME of MME pool area 2. For example: when the UE moves to
pool 2 the coverage of eNodeB 1 or eNodeB 2.
If the UE accesses the network through eNodeB 5, the probability that the UE
will move to the coverage area of eNodeB 1, 2, 3, 4, or 6 is much higher than
the probability of moving to the coverage area of other eNodeBs. Therefore,
selecting MME pool 1 can reduce the probability that the serving MME for the
UE will be changed.
Average Load
● Deciding whether the average loads of MME pools are the same
Average load of an MME pool = Sum of loads of all MMEs in the MME pool/
Number of MMEs. To learn the method of calculating the load of an MME,
see 4.1.2.2 MME Selection from an MME Pool.
● Selecting an MME pool based on the average loads
The eNodeB selects an MME pool with a lighter load.
NOTE
● If all MMEs in an MME pool are overloaded and the overload indication matches the
RRC connection setup cause, the eNodeB excludes this MME pool from the MME pool
candidate list. For details about the mapping between overload indications and RRC
connection setup causes, see 4.1.4 MME Overload Handling.
● If S1 interfaces between the eNodeB and all MMEs in an MME pool are faulty, the
eNodeB excludes this MME pool from the MME pool candidate list. For details about S1
interface fault handling, see 4.1.5 S1 Interface Failure Handling.
Capacity Proportion
● Deciding whether the capacity proportions are the same
Capacity proportion of an MME pool = Capacity of the MME pool/Total
capacity of all MME pools
NOTE
The capacity of an MME pool is sent to the eNodeB by the EPC and is indicated by the
value of MME Relative Capacity in the command output of DSP S1INTERFACE.
● Selecting an MME pool based on the capacity proportions

eRAN
The eNodeB converts the capacity proportion of an MME pool to a probability

and uses this probability to select an MME pool for a UE. A higher capacity
proportion indicates a higher probability for an MME pool to be selected.
4.1.2.2 MME Selection from an MME Pool

The procedure for selecting an MME from an MME pool varies according to the
settings of the MME_CAPACITY_BASED_SELECT_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter.
● If this option is deselected, an eNodeB selects an MME based on priorities
followed by capacities and loads, as shown in Figure 4-7.
● If this option is selected, an eNodeB selects an MME based on priorities
followed by capacity proportions, as shown in Figure 4-8.
Figure 4-7 MME selection procedure (with the

MME_CAPACITY_BASED_SELECT_SW option deselected)

eRAN
Figure 4-8 MME selection procedure (with the

MME_CAPACITY_BASED_SELECT_SW option selected)
Selecting an MME Based on Priorities

If an eNodeB is connected to multiple MMEs with different MME Selection
Priority settings (S1.Priority in endpoint configuration mode or
S1Interface.Priority in link configuration mode), the eNodeB selects the MME
with the highest priority.
MME pool selection and MME selection based on priorities enable location-based
MME backup.
As shown in Figure 4-9, an eNodeB in area A is connected to MME Pool A with a
high priority and MME Pool B with a low priority. The eNodeB sets up dedicated
S1 connections to MMEs in area A for UEs that access the network in area A. The
eNodeB sets up dedicated S1 connections to MMEs in area B for these UEs only
when MMEs in area A are unreachable.

eRAN
Figure 4-9 Example of selecting an MME
Selecting an MME Based on MME Capacities and Loads

If an eNodeB is connected to multiple MMEs with the same priority in an MME
pool, the eNodeB selects an MME based on the capacities and loads of MMEs to
balance the loads among MMEs in the MME pool and make full use of the
processing capability of the EPC.
The eNodeB selects the MME with the minimum relative load in an MME pool.
● When the UE_TYPE_BASED_MME_LOAD_BAL_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter is deselected, the
eNodeB calculates the relative load of an MME based on the total number of
online UEs without distinguishing UE types. The formula for calculating the
relative load is as follows:
Relative load = Number of dedicated S1-MME connections x 255/Relative
capacity of the MME
● For FDD, when the UE_TYPE_BASED_MME_LOAD_BAL_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter is selected, the eNodeB
calculates the relative load of an MME for non-NB-IoT UEs and NB-IoT UEs
separately. The eNodeB selects the MME with the minimum relative load for
both NB-IoT UEs and non-NB-IoT UEs. The relative load is calculated as
follows:
Relative load of the MME for non-NB-IoT UEs = Number of dedicated S1-
MME connections for non-NB-IoT UEs x 255/Relative capacity of the MME
Relative load of the MME for NB-IoT UEs = Number of dedicated S1-MME
connections for NB-IoT UEs x 255/Relative capacity of the MME
NOTE
For FDD, the eNodeB calculates the relative load based on the number of NB-IoT UEs and
selects an MME with the minimum relative load for NB-IoT UEs when the
UE_TYPE_BASED_MME_LOAD_BAL_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter is selected. In this case, the relative
load of MMEs on the EPC may change.
The parameters in the formula are described as follows:

● The number of dedicated S1-MME connections that have been set up
between the MME and eNodeB is obtained by the eNodeB.

eRAN
The eNodeB measures the number of dedicated S1-MME connections every

second. The number is indicated by the value of S1 Interface User Number in
the command output of DSP S1INTERFACE.
● The relative capacity of an MME is obtained by both the MME and eNodeB.
MMEs in an MME pool are configured with different relative capacities based
on their processing capabilities.
NOTE
In some situations, the relative capacity for an MME can be set not based on the
actual processing capability. For example:
After an MME is added to an MME pool or the capacity of an existing MME is
expanded in the MME pool, the relative capacity of the MME can be set to a value
that is much greater than its actual processing capability. In this scenario, the load of
this MME increases quickly. When the load reaches a specified value, the operator can
update the MME's relative capacity based on its actual processing capability.
To remove an MME from an MME pool, the eNodeB is informed that the MME is
overloaded, preventing UEs from selecting this MME. After the UEs or MME releases
all calls, you can disable the MME and remove it from the MME pool.
For details, see 4.1.3 Load Rebalancing Among MMEs.
The eNodeB needs to set up an S1-MME connection to each MME in an MME
pool and maintains the relative capacity of each MME as follows:
If... Then...
The eNodeB The MME notifies the eNodeB of its processing capability
is setting up relative to the other MMEs in the same pool (relative
an S1-MME capacity) through the Relative MME Capacity IE.
connection
to an MME
The eNodeB The MME informs the eNodeB of its capability by using the
has set up an Relative MME Capacity IE in the Configuration Update
S1-MME message if the MME capability is updated.
connection
to an MME
NOTE
● If an MME is overloaded and the overload indication matches the RRC connection
setup cause, the eNodeB excludes the MME from the MME candidate list. For
details about the mapping between overload indications and RRC connection setup
causes, see 4.1.4 MME Overload Handling.
● If the S1 interface between the eNodeB and an MME is faulty, the eNodeB also
excludes the MME from the MME candidate list. For details about S1 interface
fault handling, see 4.1.5 S1 Interface Failure Handling.
Selecting an MME based on the capacity proportions

Capacity proportion of an MME = Capacity of the MME/Total capacity of all MMEs
in a pool. The eNodeB converts the capacity proportion of an MME to a
probability and uses this probability to select an MME for a UE. A higher capacity
proportion indicates a higher probability for an MME to be selected.

eRAN
4.1.2.3 MME Selection Based on Cell Configurations

In this scenario, an MME range is configured for a cell. The eNodeB selects an
MME from this range when a UE accesses this cell. The MME pool and MME
selection mechanisms in this scenario are similar to those described in 4.1.2 MME
Selection Based on the High Rank Policy and 4.1.2.2 MME Selection from an
MME Pool. The only difference is that an eNodeB does not consider MME pool
priorities, average loads, and MME priorities during MME pool and MME selection
in this scenario. The following parameters are involved:
● CellOp.MMECfgNum: indicates the number of MMEs configured for a cell.
This parameter also functions as a switch for configuring separate MMEs for
FDD, TDD, and NB-IoT cells served by the same eNodeB.
● CellOp.MMEGI1 to CellOp.MMEGI4: indicate the IDs of MME groups.
● CellOp.MMEC1 to CellOp.MMEC4: indicate the codes of MMEs.
The numbers of configured MMEGIs and MMECs must be equal to the number of
configured MMEs.
This function can work with the procedure described in 4.1.2.4 MME Selection
Based on DCN Range. For details, see descriptions of MME selection in 4.1.2.4
MME Selection Based on DCN Range for FDD, TDD, and NB-IoT cells that are
served by the same eNodeB but different MMEs.
4.1.2.4 MME Selection Based on DCN Range

Multiple dedicated core networks (DCNs) can be deployed within one public land
mobile network (PLMN). Each DCN can serve a particular category of subscribers,
such as M2M subscribers or subscribers belonging to a specific enterprise or a
specific administrative domain. A DCN comprises one or more MMEs/SGSNs and it
may comprise one or more S-GWs/P-GWs/PCRFs. During the access of a UE, the
serving MME designates a DCN for the UE based on the UE Usage Type in the UE
subscription information. The eNodeB selects an MME for the UE based on the
DCN information provided by the serving MME.
Huawei eNodeBs support the DCN function introduced in 3GPP Release 13. This
function has no requirements for UE releases.
The DCN function is controlled by the DCN_SUPPORT_SWITCH option of the
CnOperator.OperatorFunSwitch parameter, and it can be deployed by PLMN.
During an attach or TAU procedure, the eNodeB selects an MME for the UE based
on the access information provided by the UE. If the selected MME does not
support the service required by the UE, the MME triggers an NAS message
redirection procedure, as shown in Figure 4-10.

eRAN
Figure 4-10 NAS message redirection procedure
The NAS message redirection procedure is described as follows:

1. Upon the access of a UE, the eNodeB selects an MME for the UE based on the
access information and sends an Initial UE Message to the MME. See UE-
Access-triggered MME Selection to learn the MME selection algorithm.
2. If the MME does not support the service required by the UE, it triggers a NAS
message redirection procedure (see Redirection-triggered MME Selection)
by sending a Reroute NAS Request to the eNodeB. This message contains the
following IEs:
– original RAN message, which is a complete packet data unit (PDU)
received from the RAN. It contains the original NAS request message and
all RAN IEs.
– MME Group ID, which determines the next serving DCN.
– Additional GUTI, which is optional. It helps the eNodeB to select an MME.
– UE Usage Type, which is optional. Its value is specified upon UE
subscription and sent by the eNodeB to the next MME.
3. The eNodeB selects a new MME based on the IEs MME Group ID and
Additional GUTI carried in the Reroute NAS Request.
4. The eNodeB sends an Initial UE Message to the newly selected MME. This
message contains the IEs MME Group ID and UE Usage Type (which is
available only if it is present in the Reroute NAS Request). Based on the IE
MME Group ID, the new MME determines that this is an Initial UE Message
sent after a redirection is triggered. Therefore, the MME does not forward this
message but processes or rejects it.
During UE access and NAS message redirection, the eNodeB can select a default
DCN or an MME determined by NAS message redirection only within the same
PLMN.
UE-Access-triggered MME Selection

When the DCN function is enabled, the eNodeB selects an MME for a UE during
its access as follows:
1. The eNodeB selects an MME according to the procedure described in 4.1.1
MME Selection Based on NNSF Policies. For NB-IoT and eMTC UEs, if MMEs

eRAN
having eMTC/NB-IoT capabilities exist in the pool, the eNodeB can select
MMEs only from these MMEs. The eMTC/NB-IoT capabilities of an MME can
be set by running the ADD MMECAPINFO command. If no MME is selected,
the eNodeB goes to the next step.
2. The eNodeB selects an MME from the default DCN. If no MME in the default
DCN is available for use or the eNodeB is not configured with a default DCN,
the eNodeB selects an MME according to the methods described in 4.1.2.1
MME Pool Selection, 4.1.2.2 MME Selection from an MME Pool, and 4.1.2.3
MME Selection Based on Cell Configurations.
A default DCN can be configured using the ADD DEFAULTDCNCFG
command. To select an MME from the default DCN, the eNodeB first selects
an MME pool (see 4.1.2.1 MME Pool Selection) from the MME Group IDs
configured under the PLMN and then selects an MME from the pool (see
4.1.2.2 MME Selection from an MME Pool). For NB-IoT and eMTC UEs, if an
MME pool in the default DCN contains MMEs having eMTC/NB-IoT
capabilities, the eNodeB selects MMEs from those MMEs preferentially. If no
MME is selected, an MME that has eMTC/NB-IoT capabilities is selected from
all the other MMEs configured for the eNodeB.
The preceding MME selection steps apply to FDD, TDD, and NB-IoT cells served by
the same eNodeB but different MMEs. However, the MMEs must be selected from
those configured in the CellOp MO.
NOTICE
NB-IoT UEs can access only NB-IoT MMEs whose MmeCapInfo.NbCiotEpsOptCap

is set to a value other than NOT_SUPPORT. If the NB-IoT MMEs configured on
the EPC for serving an eNodeB outnumber those configured on the eNodeB, the
MME group identified by the MMEGI selected during NAS message redirection
may contain MMEs that the eNodeB does not support, causing UE access failures.
Therefore, the NB-IoT MMEs configured on the eNodeB must be consistent with
those on the EPC that serve the eNodeB.
eMTC UEs that the eNodeB has identified through PRACH time-frequency
resources can access only eMTC MMEs whose
MmeCapInfo.MmeSupportEmtcDedEpcCap is set to a value other than
NOT_SUPPORT. The EPC does not have the MME range that is configured on the
eNodeB. Therefore, UE access fails if the MME group identified by the MMEGI
selected during NAS message redirection does not contain these MMEs.
Considering this, the eMTC MMEs configured on the eNodeB must be consistent
with those on the EPC that serve the eNodeB. Operators can spare the task of
configuring eMTC MMEs on the eNodeB and let the EPC assign appropriate MMEs
for UEs.
If the range of MMEs that can be selected for UEs in a cell is configured through
the CellOp MO, UEs in this cell can access these MMEs only. If these MMEs do not
support all UE Usage Type values or the MME group identified by the MME Group
ID that the EPC selects during NAS message redirection does not contain these
MMEs, certain UEs in this cell will fail to access the MME. In this case, do not set
the range of MMEs on the eNodeB for such a cell and let the EPC assign
appropriate MMEs for UEs.

eRAN
Redirection-triggered MME Selection

If the Reroute NAS Request message carries the Additional GUTI IE and the MME
identified by the GUMMEI of the GUTI is valid, the eNodeB selects this MME for
UE access. If the Reroute NAS Request message does not carry the Additional
GUTI IE, the eNodeB selects a valid MME from the MME group identified by the
MME Group ID IE in this message. If there is no valid MME in the MME group, the
eNodeB selects an MME from the default DCN configured on the eNodeB. If there
is no valid MME in the default DCN, the eNodeB sends an Initial UE Message to
the MME that triggers the Reroute NAS Request. For NB-IoT and eMTC UEs, the
eNodeB can select MMEs only from those having eMTC/NB-IoT capabilities in the
preceding steps. The preceding MME selection steps apply to FDD, TDD, and NB-
IoT cells served by the same eNodeB but different MMEs. However, the MMEs
must be selected from those configured in the CellOp MO.
4.1.3 Load Rebalancing Among MMEs

With S1-flex, UE contexts registered with one MME can be transferred to other
MMEs.
When load rebalancing is initiated on an MME, the MME's relative capacity can be
changed and delivered to each connected eNodeB to prevent the eNodeBs from
selecting this MME.
If a UE is in the ECM-CONNECTED or ECM-IDLE state, the MME that it registers
with stores the UE context. MME load rebalancing for this UE is as follows:
● For an ECM-CONNECTED UE, MMEa transfers its context to MMEb, as shown
in Figure 4-11.
a. MMEa initiates a UE context release over the S1 interface with the
release cause "Load Balancing TAU Required".
b. The eNodeB initiates an RRC connection release with the release cause
"Load Balancing TAU Required".
c. After receiving the RRC connection release message, the UE releases the
RRC connection and reinitiates an RRC connection request to follow a
TAU procedure.
NOTE
During the RRC connection setup, the RRC connection request message does not
carry the S-TMSI, and the RRC connection setup completion message does not
carry the RegisterMME IE. The eNodeB then reselects an MME for the UE.
d. The eNodeB selects an MME for the UE and sets up a dedicated S1-MME
connection with MMEb. For details about how the eNodeB selects an
MME, see 4.1.2 MME Selection Based on the High Rank Policy.

eRAN
Figure 4-11 MME load rebalancing for an ECM-CONNECTED UE
● For an ECM-IDLE UE, the MME first initiates a paging procedure for the UE to
enter the ECM-CONNECTED state. The subsequent procedure is the same as
that for a UE in the ECM-CONNECTED state.
The MME load rebalancing function requires the collaboration of the MME,
eNodeB, and UE.
The eNodeB initiates an RRC connection release with the release cause "Load
Balancing TAU Required" if all the following conditions are met:
● The RRC Connection Request message of the UE contains an S-TMSI, and the
MME identified by the S-TMSI is overloaded.
● The overload indication matches the RRC connection setup cause.
● The UE is not redirected to another cell.
NOTE
When load rebalancing is initiated on a high-priority MME, the eNodeB still preferentially
selects this MME for UEs initiating TAU procedures. Therefore, you must lower the priority
of this MME.
If the MME informs the eNodeB that it is highly loaded and there are lightly loaded MMEs
under the same PLMN as the highly loaded MME, the eNodeB will determine whether the
UE should access the highly loaded MME when the
GlobalProcSwitch.EnbTrigMmeLoadRebalSwitch parameter is set to ON. If the eNodeB
determines that the UE should access the highly loaded MME, the eNodeB will initiate an
RRC connection release with the release cause "Load Balancing TAU Required".
4.1.4 MME Overload Handling

Figure 4-12 shows the signaling between an eNodeB and an MME when the MME
is overloaded.

eRAN
Figure 4-12 Signaling between an eNodeB and an overloaded MME
1. When an MME is overloaded, it sends an Overload Start message to some or

all connected eNodeBs.
2. After receiving the Overload Start message, each eNodeB marks the MME as
overloaded. If the MME_OVERLOAD_BASED_SELECT_SW option of the
GlobalProcSwitch.MmeSelectProcSwitch parameter is selected and the
Overload Start message contains the Traffic Load Reduction Indication IE, the
eNodeB determines whether to accept UE access requests to the MME based
on the rejection percentage indicated by this IE for UEs whose access reasons
match the overload handling policy.
NOTE
If all MMEs in an MME pool are overloaded and the overload indication matches the
RRC connection setup cause, the eNodeB does not select this MME pool for UE access.
3. The MME and eNodeB take measures to reduce the MME load.
4. When the MME is no longer overloaded, it sends an Overload Stop message
to the eNodeBs.
5. After receiving the Overload Stop message, each eNodeB deletes the MME
overload indication and updates the information about the related MME pool.
Normal processing resumes.
MME Load Reduction

As shown in Figure 4-12, when an MME is overloaded, both the MME and
eNodeB take measures to reduce the MME load.
● The MME takes the following measures:
– Sends an Overload Start message to some or all connected eNodeBs.
– Instructs these eNodeBs to accept only the specified types of service
requests through the Overload Start message.
● The eNodeB compares the RRC connection setup cause of a UE and the
overload indication sent from the MME to determine whether the UE can
access the overloaded MME.

eRAN
NOTE
When an MME sends an Overload Start message to an eNodeB, the eNodeB will not
allocate the newly accessed UEs that match the overload cause to the MME. UEs that
are already served by the MME, however, may still access the MME but will increase
the MME load.
The following are examples of eNodeB actions in the case of MME overload.
Table 4-2 eNodeB actions in case of MME overload
Overload The eNodeB Rejects the A UE Can Still Be Served If It

Handling Request If a UE Initiates an Initiates an RRC Connection
Policy RRC Connection Setup Setup Request with the
Indicated in Request with the Following Following Cause
the Overload Cause
Start
Message
from the
MME
Reject RRC mo-data or delayTolerantAc- emergency, highPriorityAccess,

connection cess mo-ExceptionData (RRC
establishment connection setup with the
s for non- cause of "mo-ExceptionData"
emergency is not supported in TDD), mt-
MO DT Access, or mo-Signalling
Reject RRC mo-data, mo-signalling, or emergency, highPriorityAccess,

connection delayTolerantAccess or mo-ExceptionData (RRC
establishment connection setup with the
s for cause of "mo-ExceptionData"
Signalling is not supported in TDD)
Permit mo-data, mo-signalling, emergency or mt-Access

Emergency delayTolerantAccess,
Sessions and highPriorityAccess, or mo-
mobile ExceptionData
terminated
services only
Permit High mo-data, mo-signalling, highPriorityAccess, mo-

Priority delayTolerantAccess, or ExceptionData, or mt-Access
Sessions and emergency
mobile
terminated
services only
Reject delay ● delayTolerantAccess by a A cause other than

tolerant non-NB-IoT UE delayTolerantAccess by a non-
access ● mo-data by an NB-IoT UE NB-IoT UE and a cause other
than mo-data by an NB-IoT
UE

eRAN
NOTE
For indications in the Overload Start message from the MME, see the Overload Action IE in
section 9.2.3.20 in 3GPP TS 36.413 V10.5.0 (2012-03). For RRC connection setup causes
contained in the RRCConnectionRequest message, see the EstablishmentCause IE of the
RRCConnectionRequest message described in section 6.2.2 in 3GPP TS 36.331 V10.5.0
(2012-03).
MME Selection When an MME Is Overloaded

Figure 4-12 shows the MME selection procedure when an MME is overloaded.
Figure 4-13 MME selection procedure when an MME is overloaded
1. The UE initiates an RRC connection setup request.

eRAN
NOTE
In FDD:
● After receiving an RRCConnectionRequest message from the UE in non–RAN
sharing scenarios, if all MMEs connecting to the eNodeB are overloaded and the
serving cell of the UE has no inter-RAT neighboring cells, the eNodeB directly
rejects the UE's RRC connection setup request by sending an RRCConnectionReject
message to the UE and specifies the period after which the UE can attempt to
access the eNodeB again.
● In RAN sharing scenarios, the eNodeB sends an RRCConnectionReject message to
the UE only when all MMEs are overloaded and the serving cell of the UE has no
inter-RAT neighboring cells.
● NB-IoT does not support inter-RAT operations and there is no need to determine
whether inter-RAT neighboring cells are configured or not.
2. The eNodeB selects an MME for the UE.
The eNodeB selects an MME based on the MME identifier provided by the UE,
MME priorities, MME capacities, MME loads, and the S1 interface status.
3. The eNodeB checks whether the MME is overloaded.
The eNodeB compares the RRC connection setup cause and the overload
indication to determine whether the UE can access the overloaded MME.
If... Then...
The UE is allowed to access the The eNodeB performs operations

overloaded MME described in 5.
The UE is not allowed to access the The eNodeB performs operations

overloaded MME described in 4.
4. The eNodeB checks whether there are other available MMEs.
If... Then...
Other MMEs are available The eNodeB performs operations

described in 2.
There are no other available MMEs The eNodeB performs operations

described in 6.
5. The eNodeB sets up a dedicated S1-MME connection.

6. The eNodeB redirects or releases the UE.
– If the S1 interfaces between the eNodeB and all available MMEs are
normal, the eNodeB selects an inter-RAT frequency for redirection.
– NB-IoT does not support redirection currently and therefore the eNodeB
releases the UE.
NOTE
This is because eNodeBs may be connected to the same MME or the same MME
pool, and therefore the MME loads may not be reduced if the source eNodeB
selects an intra-RAT frequency for redirection.

eRAN
– If the S1 interfaces between the eNodeB and all available MMEs are
abnormal, the eNodeB selects a frequency for redirection by following the
principles described in 4.1.5 S1 Interface Failure Handling.
4.1.5 S1 Interface Failure Handling

The following table lists the alarms related to the S1 control plane.
Alarm ID Alarm Name Severity
ALM-29201 S1 Interface Fault Major
A fault in the S1 interface between an eNodeB and an MME affects MME pool
selection and MME selection in an MME pool. If a fault occurs on the S1 control
plane, the eNodeB cannot select the MME of the S1 interface for UEs that attempt
to access the network.
If the S1 interface status in the control plane is abnormal, the eNodeB handles the
UEs in the RRC_CONNECTED state over this interface as described in the following
table. The S1 interface status can be queried by running the DSP S1INTERFACE
command. For details, see 4.4.2 Activation Verification.
If... Then...
The eNodeB is connected The eNodeB releases all UEs that are carried on the
to other MMEs that faulty S1 interface. When UEs re-access the network,
belong to the same the eNodeB selects other available S1 interfaces for
serving operator the UEs.
The eNodeB is not The eNodeB initiates redirection for all UEs that are
connected to any other carried on this S1 interface.
MME that belongs to the
same serving operator
On reception of an S1 interface fault indication, the eNodeB immediately starts

RRC connection release procedures to release all UEs in all cells of the eNodeB.
The RRC connection release message contains redirection information. For details
about redirection triggered by S1 interface faults, see Idle Mode Management.
4.2 Network Analysis
4.2.1 Benefits
S1-flex provides the following benefits:
● Signaling overheads for location updates are reduced because the serving
MME does not need to change when the UE moves in an MME pool area (the
area covered by an MME pool).

eRAN
● Load balancing is implemented among MMEs in the same MME pool,

improving resource utilization.
● MME nodes are easy to add or remove with minimal impact on ongoing
services.
● MME selection is based on priorities, capacities and loads, which enhances
network reliability because each MME in an MME pool is a backup for the
other MMEs in the pool.
● MME selection based on priorities enables location-based MME backup,
improving network reliability.
4.2.2 Impacts
Network Impacts
When MME selection based on cell configurations is enabled by setting the
CellOp.MMECfgNum parameter to a non-zero value:
● There is a higher probability of triggering the S1-flex algorithm to select S1
interfaces for UEs, and the value of the L.S1.UE.FLEX.Selection counter may
increase.
● When an intra- or inter-eNodeB coverage-based inter-duplex-mode handover
between FDD and TDD is performed for a UE, the eNodeB triggers a
redirection to hand over the UE to another MME. This may increase the UE
handover delay and interrupt delay-sensitive VoLTE services.
When the DCN function is enabled:
● The UE access delay may increase if the MME triggers a NAS message
redirection when a UE initiates an attach procedure or moves from one MME
to another.
● During an inter-DCN handover, the serving MME may proactively release the
UE after the inter-DCN handover is completed. In this case, UE services will be
interrupted. The MME releases the UE for it to initiate a TAU procedure, and
then the MME can initiate a NAS message redirection towards the
corresponding MME.
Function Impacts
None
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Prerequisite Functions
None

eRAN
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.3.4 Networking
MMEC Planning
Before deploying S1-flex, make an MMEC plan based on the following rules:
● If MME pool areas do not overlap, MMECs can be reused among the MME
pools.
● If MME pool areas overlap:
– MMECs must be uniquely assigned to MMEs in the MME pools so that
each MMEC is unique within a TA of the overlapping area.
To ensure unique MMECs within TA2, MMECs in MME pool 1 and MME
pool 2 (which are MMEC1 to MMEC9) need to be allocated uniformly, as
shown in Figure 4-14.
Figure 4-14 No duplicate MMEC within TA2 of the overlapping area

eRAN
– In RAN sharing scenarios, MMECs should be uniformly allocated for MME

pools of different operators and cannot be duplicated by default for
macro and LampSite eNodeBs. But you can set identical MMECs for
MMEs of different operators by using the
GlobalProcSwitch.DiffOpWithSameMmecSwitch parameter.
NOTE
If the same MMEC is assigned to MMEs of different operators, an MME may

page a wrong UE. When an MME of operator A uses the S-TMSI (the
combination of the MMEC and M-TMSI) to page a UE, another UE subscribing to
operator B may receive and respond to the paging message. The probability that
a wrong UE is paged depends on the length of the M-TMSI. Since the M-TMSI is
32 bits in length, this probability is .
MME Backup Planning for Geographic Redundancy

If MME backup for geographic redundancy is required, make an MME priority and
MME pool plan based on the following rules:
● If multiple MMEs in area A belong to the same MME pool and these MMEs
need to be backup MMEs for eNodeBs in area B, each eNodeB in area B must
be connected to all the MMEs in area A and, on the eNodeBs in area B, MMEs
in area A must be assigned lower priorities than MMEs in area B. If MMEs in
area A are assigned higher priorities than or same priorities as MMEs in area
B on the eNodeBs in area B, then UEs in area B will also access the backup
MMEs in normal situations.
● If some MMEs in area A need to be backup MMEs for eNodeBs in both area A
and area B, the backup MMEs cannot belong to the same MME pool as other
MMEs in area A.
4.3.5 Others
The EPC must support the S1-flex feature. It is not a Huawei proprietary feature
and can be used with EPC equipment from Huawei or other vendors. If the EPC
equipment is provided by Huawei, the version must be PS9.1 or later. If the EPC
equipment is provided by another vendor, check whether the vendor's equipment
supports this feature.
MMEs must support the pooling function. During S1-MME connection setup, these
MMEs must send the IEs MME-group-id, MME-Code, and MME-capacity that are
required for supporting S1-flex to eNodeBs. S1-flex imposes restrictions on the
planning of MME pools and TAs. For details about the planning rules, see 3
Related Concepts.
Operators must determine a list of MMEs to which each eNodeB needs to connect
based on the networking requirements, and configure the corresponding SCTP
links, S1 interfaces, transport-layer managed objects (MOs), and routes to the
MMEs based on this list.
Operators must plan one or more IP addresses and SCTP port numbers for S1
interfaces based on the networking requirements, and ensure that the
transmission links between eNodeBs and MMEs in MME pools are working
properly.

eRAN
The functions "MME pool selection based on the network topology and average
loads" and "MME selection based on MME capacities and loads" depend on
whether the given MMEs support the MME pooling function.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation

S1-flex requires the configuration of multiple S1 interfaces. For details about data
preparation for S1 interface configuration, see S1 and X2 Self-Management. Other
required data is as follows:
Configure the MME priority (link model). The mapping MO is S1Interface. The
following table describes the key parameters.
Parameter Parameter ID Setting Notes

Name
MME S1Interface.P After this parameter is set for MMEs, the

Selection riority eNodeB can select a high-priority MME for UEs
Priority that attempt to access the network.
Configure the MME priority (EP model). The mapping MO is S1. The following
table describes the key parameters.

Name
MME S1.Priority After this parameter is set for MMEs, the

Selection eNodeB can select a high-priority MME for UEs
Priority that attempt to access the network.
Load Rebalancing
The following table describes the parameters that must be set in the
GlobalProcSwitch MO to configure the switch of eNodeB-triggered MME load
rebalancing.

eRAN

Name
eNB Triggered GlobalProcS This parameter indicates whether to enable

MME load re- witch.EnbTri eNodeB-triggered MME load rebalancing.
balance gMmeLoadR When this parameter is set to ON, the eNodeB
switch ebalSwitch releases a UE with the cause value
"loadBalancingTAUrequired" if the UE accesses
the network using an S-TMSI that is associated
with an overloaded MME. Then, if the UE
initiates another access request, it will be
routed to a lightly loaded MME. When this
parameter is set to OFF, the eNodeB sends an
RRCConnectionRelease message with the cause
value "other" to the UE to release its RRC
connection.
MME Selection Based on Cell Configurations

The following table describes the parameters that must be set in a CellOp MO to
configure cell-configuration–based MME selection for an operator.

Name
MME CellOp.MME Set this parameter to a non-zero value when

configure CfgNum separate MMEs have been configured for TDD,
number FDD, and NB-IoT cells.
First MME CellOp.MME This parameter can be configured only when

group identity GI1 the MMECfgNum parameter value is greater
than or equal to 1.
The MME Group ID plus MMEC for an MME
must be unique under a CellOp MO.
First MME CellOp.MME Same as above

code C1
Second MME CellOp.MME This parameter can be configured only when
than or equal to 2.
Second MME CellOp.MME Same as above

code C2

eRAN

Name
Third MME CellOp.MME This parameter can be configured only when

than or equal to 3.
Third MME CellOp.MME Same as above

code C3
Fourth MME CellOp.MME This parameter can be configured only when
than or equal to 4.
Fourth MME CellOp.MME Same as above

code C4
MME Selection Policy Configurations for GSM/UMTS UEs

GlobalProcSwitch MO to configure the MME selection policies.

Name
MME Select GlobalProcS This parameter has the following two options:
Procedure witch.MmeSe MMESELECTALGOSWITCHFORGUUE and
Switch lectProcSwitc NNSFENHANCEMENTSWITCH
h
Set the two options to ON and OFF when the
following conditions are met:
Operators require that an eNodeB select an
MME with a light load for UEs accessing an
LTE network from a GSM or UMTS network,
and the EPC is required to support normal
access of UEs when the eNodeB selects an
MME that does not store the UEs' contexts.
Otherwise, it is not recommended that the
MMESELECTALGOSWITCHFORGUUE option
be selected.

eRAN

Name
Set the two options to OFF and ON when the

● There are LACs whose most significant bit is
1 in a GSM or UMTS network.
● MMEs in a network do not send a complete
set of MME Group IDs to the connected
eNodeBs.
● Operators require that an eNodeB select
MMEs having UE contexts when UEs
reselect to an LTE network from a GSM or
UMTS network.
Set the two options to OFF and OFF when the

● The most significant bit of all LACs in a
GSM or UMTS network is planned as 0.
● Operators require that an eNodeB select
MMEs having UE contexts when UEs
reselect to an LTE network from a GSM or
UMTS network.
(Optional) The following table describes the parameters that must be set in the
S1Interface MO to configure the release of the MME.

Name
MME Release S1Interface. The MME Release must be

MmeRelease Release_R10(Release 10) or later.
(Optional) The following table describes the parameters that must be set in the
MmeCapInfo MO to control whether the MME supports NB-IoT and LTE.

eRAN

Name
NB-IoT CIoT MmeCapInfo. If this parameter is set to NOT_SUPPORT, the

EPS NbCiotEpsOp MME does not support CIoT EPS optimization
Optimization tCap for NB-IoT. The eNodeB will not transfer NB-
Capability IoT services to the MME.
If this parameter is to CP, the MME supports
control plane CIoT EPS optimization for NB-IoT.
Before setting this parameter to CP, ensure
that at least one TAI for NB-IoT has been
configured for the S1 link of the MME.
MME Support MmeCapInfo. If this parameter is set to SUPPORT, the NB-

LTE Capability NbLteSuppor IoT MME supports LTE. In this case, the
tCap MmeCapInfo.NbCiotEpsOptCap parameter
must not be set to NOT_SUPPORT.
MME Selection Based on DCN Range

The following table describes the parameters that must be set in a CnOperator
MO to configure DCN-range-based MME selection.

Name
Operator CnOperator. Select the DCN_SUPPORT_SWITCH option of

Function OperatorFun this parameter when the DCN function on the
Switch Switch EPC is enabled.
The following table describes the parameters that must be set in a DefaultDcnCfg
MO to configure a default DCN.

Name
CN Operator DefaultDcnCf Set this parameter if a default DCN is

ID g.CnOperator configured on the EPC.
Id
Default DCN DefaultDcnCf Set this parameter if a default DCN is
MME Group g.DefaultDcn configured on the EPC.
ID MmeGroupId
MME Selection Policy Configurations for Non-NB-IoT/NB-IoT UEs (FDD)


eRAN

Name
MME Select GlobalProcS You are advised to select the

Procedure witch.MmeSe UE_TYPE_BASED_MME_LOAD_BAL_SW option
Switch lectProcSwitc in NB-IoT and LTE hybrid networking scenarios.
h
Name
MME Select GlobalProcS If there are a large number of UEs on the live
Procedure witch.MmeSe network, you are advised to select the
Switch lectProcSwitc MME_OVERLOAD_BASED_SELECT_SW option.
h
4.4.1.2 Using MML Commands
Activation Command Examples

● Creating an S1 interface in link configuration mode (old model) when the
GTRANSPARA.TRANSCFGMODE parameter is set to OLD
//If multiple MMEs are involved, control-plane objects should be added for several times while user-
plane objects should be added only once.
//Configuring the control plane (transmission backup is needed for the No.0 SCTP link)
ADD SCTPLNK: SCTPNO=0, SN=7, LOCIP="70.170.107.17", SECLOCIP="70.170.107.18",
LOCPORT=2911, PEERIP="30.0.0.20", SECPEERIP="30.0.0.21", PEERPORT=1032,
AUTOSWITCH=ENABLE, DESCRI="MME1";
ADD SCTPLNK: SCTPNO=1, SN=7, LOCIP="70.170.107.17", LOCPORT=2940, PEERIP="30.0.0.38",
PEERPORT=1030, AUTOSWITCH=ENABLE, DESCRI="MME2";
ADD CPBEARER: CPBEARID=0, BEARTYPE=SCTP, FLAG=MASTER;
ADD CPBEARER: CPBEARID=1, BEARTYPE=SCTP, LINKNO=1, FLAG=MASTER;
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0, Priority=0;
//Configuring the user plane
ADD IPPATH: PATHID=0, SN=7, SBT=BASE_BOARD, PT=ETH, LOCALIP="70.170.107.19",
PEERIP="10.10.8.88", PATHTYPE=ANY;
● Creating an S1 interface in link configuration mode (new model) when the
GTRANSPARA.TRANSCFGMODE parameter is set to NEW
//If multiple MMEs are involved, control-plane objects should be added for several times while user-
plane objects should be added only once.
//Configuring the control plane
ADD SCTPLNK: SCTPNO=0, LOCIP="70.170.107.17", SECLOCIP="70.170.107.18", LOCPORT=2911,
PEERIP="30.0.0.20", SECPEERIP="30.0.0.21", PEERPORT=1032, AUTOSWITCH=ENABLE,
DESCRI="MME1";
ADD SCTPLNK: SCTPNO=1, LOCIP="70.170.107.17", LOCPORT=2940, PEERIP="30.0.0.38",
PEERPORT=1030, AUTOSWITCH=ENABLE, DESCRI="MME2";
ADD CPBEARER: CPBEARID=0, BEARTYPE=SCTP, FLAG=MASTER;
ADD CPBEARER: CPBEARID=1, BEARTYPE=SCTP, LINKNO=1, FLAG=MASTER;
ADD IPPATH: PATHID=0, TRANSCFGMODE=NEW, JNIPRSCGRP=DISABLE, BPT=ETH, PORTID=0,
LOCALIP="70.170.107.19", PEERIP="10.10.8.88", PATHTYPE=ANY;

eRAN
● Creating an S1 interface in endpoint configuration mode

//Configuring the control plane
ADD EPGROUP: EPGROUPID=0, USERLABEL="for cp1";
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="70.190.103.8",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=2911, SCTPTEMPLATEID=0,
USERLABEL="for MME1";
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
ADD SCTPPEER: SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4="30.0.0.20", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=1032, USERLABEL="for MME1";
ADD SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
ADD SCTPPEER: SCTPPEERID=1, IPVERSION=IPv4, SIGIP1V4="30.0.0.38", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=1030,USERLABEL="for MME2";
ADD SCTPPEER2EPGRP: EPGROUPID0, SCTPPEERID=1;
ADD EPGROUP: EPGROUPID=2, USERLABEL="for up";
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="70.190.103.1",
IPSECSWITCH=DISABLE, USERLABEL="for UGW";
ADD UPHOST2EPGRP: EPGROUPID=2, UPHOSTID=0;
//Adding an S1 object
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0, UpEpGroupId=2,
Priority=10;
● Other optional functions

//Enabling load rebalancing among MMEs
MOD GLOBALPROCSWITCH:EnbTrigMmeLoadRebalSwitch=1;
//Setting MME selection policies for GSM/UMTS UEs
MOD GLOBALPROCSWITCH:
MmeSelectProcSwitch=MMESELECTALGOSWITCHFORGUUE-0&NNSFENHANCEMENTSWITCH-1;
//Enabling cell-configurations-based MME selection
ADD CNOPERATORTA:TrackingAreaId=0,CnOperatorId=0,Tac=1;
ADD CNOPERATORTA:TrackingAreaId=1,CnOperatorId=0,Tac=2;
MOD CELLOP:LocalCellId=0,TrackingAreaId=0,MMECfgNum=
CELL_MME_CFG_NUM_1,MMEGI1=1,MMEC1=1;
MOD CELLOP:LocalCellId=1,TrackingAreaId=1,MMECfgNum=
CELL_MME_CFG_NUM_1,MMEGI1=2,MMEC1=2;
//Setting the NB-IoT MME to support control plane CIoT EPS optimization and LTE services
ADD MMECAPINFO:MmeCapCfgId=1,S1CfgType=S1_CFG,S1Id=1,NbCiotEpsOptCap=CP_UP,
NbLteSupportCap=SUPPORT;
ADD
MMECAPINFO:MmeCapCfgId=1,S1CfgType=S1INTERFACE_CFG,S1InterfaceId=1,NbCiotEpsOptCap=CP_
UP,NbLteSupportCap=SUPPORT;
//Setting the DCN function switch
MOD CNOPERATOR: CnOperatorId=0, OperatorFunSwitch=DCN_SUPPORT_SWITCH-1;
ADD DEFAULTDCNCFG: CnOperatorId=0, DefaultDcnMmeGroupId=32769;
Deactivation Command Examples

//Removing the backup MME pool
RMV S1INTERFACE:S1INTERFACEID=0;
4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.
4.4.2 Activation Verification
S1 Interface Status
Step 1 Run the DSP S1INTERFACE command to query the status of all configured S1
interfaces.
In the command output shown in Figure 4-15:

eRAN
● If the value of S1 Interface State is Normal, the S1 interface is normal.

● If the value of S1 CP Bearer State is Normal, the SCTP link is normal.
● If all the S1 interfaces and SCTP links are normal, S1-flex has been activated.
Figure 4-15 S1 interface status
Step 2 Use multiple UEs that have not been registered with the MMEs to access the
network and initiate services separately.
Then, check whether the UEs can perform services properly; for example, whether
the UEs can perform uplink and downlink File Transfer Protocol (FTP) services.
Step 3 Run the DSP S1INTERFACE command to query the value of S1 Interface User
Number for each S1 interface.
If the UE access statistics comply with the principles described in Principles, the
eNodeB performs load balancing among multiple MMEs when the UEs access the
network. The NNSF procedures are correct.
----End
MME Priority
Step 1 Run the DSP S1INTERFACE command to query the MME priority configuration, as
shown in Figure 4-16.

eRAN
Figure 4-16 MME priority information
Step 2 Enable UEs to access the network and check whether the UE access statistics
comply with the principles described in 4.1.2.2 MME Selection from an MME
Pool.
If the UE access statistics comply with the principles, the priority-based MME
selection procedure is correct.
----End
NNSF
Step 1 Enable a UE to access the network. Then check the mmec IE in the
RRC_CONN_SETUP_CMP message. As shown in Figure 4-17, the value of the
mmec IE is 0F.

eRAN
Figure 4-17 mmec IE
Step 2 Run the DSP SERVEDGUMMEIS command to query the GUMMEI of the serving
MME.
If the UE always accesses the MME matching the mmec IE in the

RRC_CONN_SETUP_CMP message, the function has taken effect.
Figure 4-18 Querying the GUMMEI of the serving MME
----End

The observation methods vary with scenarios:

eRAN
● For UE-access-triggered MME selection, run the DSP SERVEDGUMMEIS

command to query the MMEs associated with the MME Group ID, which is
configured for the default DCN. Use multiple UEs that have not registered
with the network to initiate services separately. Ensure that the UEs can
access the network normally. Check the value of L.S1.UE.FLEX.Selection for
the identified MME. If the counter value is not zero, the eNodeB has selected
the default DCN during UE access.
● For redirection-triggered MME selection, if the
L.Sig.S1.RerouteNasReq.Rcved counter value is not zero, the MME has
triggered the NAS message redirection procedure and the eNodeB has
received a Reroute NAS Request from the MME.
4.4.3 Network Monitoring

The following table lists the alarms related to S1-flex.
Alarm ID Alarm Name Severity
ALM-29201 S1 Interface Fault Major
ALM-25886 IP Path Fault Major
ALM-26819 Data Configuration Warning

Exceeding Licensed Limit
If any of these alarms is generated, clear it by referring to 3900 & 5900 Series
Base Station Alarm Reference in 3900 & 5900 Series Base Station Product
Documentation.

Monitor the value of L.Sig.S1.RerouteNasReq.Fail.InvalidMmegi. If the counter
value is not 0, MMEs associated with the MME Group ID in the Reroute NAS
Request message are unusable for the eNodeB and a configuration error may be
present.
● No MME associated with the MME Group ID is configured on the eNodeB.
● All MMEs associated with the MME Group ID are overloaded.
● The capabilities of all MMEs associated with the MME Group ID are
inconsistent with UE capabilities. For example, the MME that the EPC
designates to NB-IoT UEs is not configured as an NB-IoT MME on the
eNodeB.
● In 4.1.2.3 MME Selection Based on Cell Configurations, none of the MMEs
associated with the MME Group ID is in the MME range configured for the
desired cell.

eRAN
S1-flex Feature Parameter Description 5 Parameters
5 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
S1-flex Feature Parameter Description 6 Counters
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
S1-flex Feature Parameter Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
S1-flex Feature Parameter Description 8 Reference Documents
8 Reference Documents
● 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for

Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
● 3GPP TS 36.300, "Overall description"
● 3GPP TS 36.331, "Radio Resource Control (RRC)"
● 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
● S1 and X2 Self-Management
● Idle Mode Management
● 3900 & 5900 Series Base Station Alarm Reference in 3900 & 5900 Series Base
Station Product Documentation

S1-Flex Feature Parameter Description: Issue Date

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S1-Flex Feature Parameter Description: Issue Date

Uploaded by

Copyright:

Available Formats

eRAN

S1-flex Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................4

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. ii

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. iii

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN16.1 04 (2020-07-27)

● 4.1.1 MME Selection Based on NNSF Policies

1.2 eRAN16.1 03 (2020-07-03)

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 1

1.3 eRAN16.1 02 (2020-05-21)

1.4 eRAN16.1 01 (2020-03-30)

1.5 eRAN16.1 Draft A (2020-01-15)

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter RAT Base Station Model

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 3

2 About This Document

2.1 General Statements

Feature Differences Between RATs

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 4

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Chapter/Section

LBFD-001018 S1-flex 4 S1-flex

MLBFD-12000310 S1-flex 4 S1-flex

This document describes the following TDD features.

Feature ID Feature Name Chapter/Section

TDLBFD-001018 S1-flex 4 S1-flex

2.4 Feature Differences Between NB-IoT and FDD

MLBFD-12000310 LBFD-001018 S1- None 4 S1-flex

2.5 Feature Differences Between FDD and TDD

LBFD-001018 S1- TDLBFD-001018 None 4 S1-flex

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 5

3.1 TA and TAL

● A cell can belong to only one TA.

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 6

Tracking Area List

3.2 MME Pool and MME Pool Area

● 3.1 "Definitions" and 4.3.7.2 "Load balancing between MMEs" in 3GPP TS

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 7

3.3 MME Identities

The RRCConnectionRequest message that a UE sends to the eNodeB contains the S-

The information element (IE) RegisterMME in the RRCConnectionSetupComplete message

3.4 AS and NAS States

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 8

Table 3-1 Storage of UE contexts in different AS/NAS states

AS State NAS State Whether the Whether the

RRC-IDLE ● EMM- No Yes

RRC-CONNECTED ● EMM- Yes Yes

After a UE sets up an RRC connection, it enters the RRC_CONNECTED state. In this

Figure 3-3 Transition between AS states

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 9

3.4.2 NAS States

● EPS mobility management (EMM)

● The UE enters the EMM-REGISTERED state after a successful attach or TAU

Figure 3-4 Transition between EMM states

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 10

A UE accesses the current cell by initiating a service request or by responding to a

Issue 04 (2020-07-27) Copyright © Huawei Technologies Co., Ltd. 11