FDD LTE S1-FLEX Feature

Guide
 FDD LTE S1-FLEX Feature Guide Internal Use Only

LEGAL INFORMATION

By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.

Copyright 2017 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.

and are registered trademarks of ZTE CORPORATION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyones access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.

The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).

This document is provided as is and as available. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATIONs
products and technologies.

ZTE CORPORATION

Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: 800@zte.com.cn

ZTE Confidential Proprietary 2017 ZTE CORPORATION. All rights reserved. I

 FDD LTE S1-FLEX Feature Guide Internal Use Only

Revision History

Product Version Document Version Serial Number Reason for Revision

V2.10.080bP02 R1.0 First published

Author

Date Document Version Prepared by Reviewed by Approved by

2012-10-28 R1.0 Shi Chao, Ma
Lu Wei
Jun

ZTE Confidential Proprietary 2017 ZTE CORPORATION. All rights reserved. II

 FDD LTE S1-FLEX Feature Guide Internal Use Only

TABLE OF CONTENTS

1 Overview ......................................................................................................... 1

2 Technical Description .................................................................................... 1

2.1 RAN Sharing Principle ...................................................................................... 1
2.2 Algorithm Flow .................................................................................................. 1

3 Scenario .......................................................................................................... 3
3.1 Application Condition ........................................................................................ 3
3.2 IOT Status ........................................................................................................ 3
3.3 EPC Status ....................................................................................................... 4

4 Key Parameters and Configuration ............................................................... 4

5 Function Test .................................................................................................. 4

ZTE Confidential Proprietary 2017 ZTE CORPORATION. All rights reserved. III
 FDD LTE S1-FLEX Feature Guide Internal Use Only

FIGURES

Figure 2-1 S1-Flex ............................................................................................................... 2

Figure 2-2 S1-Flex Example ................................................................................................. 3
Figure 4-1 Multi-SCTP Configuration.................................................................................... 4

TABLES

Table 3-1 IOT status ............................................................................................................ 4

Table 3-2 EPC status ........................................................................................................... 4

ZTE Confidential Proprietary 2017 ZTE CORPORATION. All rights reserved. IV

 FDD LTE S1-FLEX Feature Guide Internal Use Only

1 Overview
This document describes function S1-Flex within the eNodeB in LTE network. The main
contents comprise the following: technical description, scenario, key parameters and
configuration, KPI statistics, function test and FAQ.

2 Technical Description
S1-Flex means not only one MME/S-GW can be connected to multiple eNodeBs, but also
one eNodeB can be connected to multiple MME/S-GWs.

S1-Flex can supply the functions of MME/SGW redundancy and MME/S-GW load
balancing.

Some UEs connected to the certain eNodeB belong to one MME/S-GW, some UEs may
belong to other MME/S-GW. At the same time one UE can only be assigned to one
MME/S-GW.

2.1 RAN Sharing Principle

On S1, no specific procedure corresponds to the NAS Node Selection Function (NNSF).

To support the interconnection of eNodeB to multiple MME/S-GW, NAS node selection

function (NNSF) is located in the eNodeB to determine the UEs MME association. This
function is located in the eNodeB only and enables proper routing via the S1 interface.

According to this function, the eNodeB determines the UEs MME association based on
the UEs temporary identifier, which is assigned to the UE by the CN node (e.g. MME).

Depending on the actual scenario the NNSF determines the UEs MME association either
based its S-TMSI (e.g. at service request) or based on its GUMMEI and selected PLMN
(e.g. at attach or tracking area update in non-registered TA).

2.2 Algorithm Flow

If the eNodeB cannot get the UEs S-TMSI or GUMMEI from radio interface, the eNodeB
determines the UEs MME association based on the selected PLMN received from radio
interface, the eNodeB selecting the UEs MME associated from all MMEs connecting to
the eNodeB and MME load balancing between the MMEs should be involved in the
NNSF. The eNodeB assigned one UE to the certain MME according all connected MMEs
load weight factor and realizes load balancing of all connected MME. When a new UE is
attached, if the eNodeB can not select suitable MME for the UE, it will search that if there

2017 ZTE CORPORATION. All rights

ZTE Confidential Proprietary 1
reserved.
 FDD LTE S1-FLEX Feature Guide Internal Use Only

is Overload MME. If there is S1-Flex, no overload MME will be chosen in priority, if all the
MMEs are overload, the mechanism is the same as no S1-Flex scenario, the new sub will
be subject to the 3 types of rejection mechanism that embody in Overload Action IE in the
Overload Start message, there is no effect to the existing sub.

Figure 2-1 S1-Flex

MME S-GW MME S-GW

eNode-B eNode-B

UE1 UE2

S-TMSI is composed with MMEC (MME code) and M-TMSI. M-TMSI is assiged by
registered MME. If got S-TMSI information from UE, the eNodeB will search and map
with appropriate S1 association based on this information. GUMMEI is also composed
with MMEC (MME code) and MME Group ID. It is shown as RegisteredMME information
in RRC Connection Complete message. When received from UE, the eNodeB will search
and map with appropriated S1 association based on this information. The eNodeB gets
MME Group ID information from MME in S1 Setup Response and MME Configuration
Update messages. It is defined in the MME.

If the eNodeB can not get the UEs S-TMSI or GUMMEI from UE, MME selection is
performed according to Weight factor for each MME. Weight factor is shown as Relative
MME Capacity in S1 SETUP RESPONSE message. It is a value range from 0 to 255.
Much bigger the value is, more opporunity and UE number this MME can get and access.
If the factor changed, core network will inform to the eNodeB through MME Configuration
Update message.

The relativeMMECapacity is typically set according to the capacity of an MME node

relative to other MME nodes. This parameter is pre-configued according to MME capacity
and operator's requirement. It can not be updated automatically according to the
real-time loading of the MME. It is sent from the MME to the eNodeB in case of the
establishment of S1-MME connectivity. After that, the factor could be changed by
operator in some scenarios, such as a newly MME is installed in the network, or an
already installed and pooled MME maintainance. It is updated to the eNodeB by MME
Configuration Update message. For a newly installed MME, it can be configured with very
much higher value for an initial period of time making it faster to increase its load. For an
already installed and pooled MME for maintainance purpose, it can be configured with
zero if all subscribers are to be removed from the MME, which will route new users to
other MMEs in pool area.

2017 ZTE CORPORATION. All rights

ZTE Confidential Proprietary 2
reserved.
 FDD LTE S1-FLEX Feature Guide Internal Use Only

RelativeMMECapacity is not used in inter-MME handover. Inter-MME handover can be

trigged in UE mobility or eNodeB load balancing scenarios. RelativeMMECapacity is
used in load balancing between MMEs. Load balancing between MMEs permits UEs that
are entering into an MME Pool Area to be directed to an appropriate MME in a manner
that achieves load balancing between MMEs. it is performed by MME selection during
new users accessing.

Following figure shows an example of S1-Flex. In the figure, MME1 and MME2 belong to
MME group 1, and MME3 belongs to MME group 2. In MME Group 1, MME selection or
load balancing between MMEs is used. When users perform handover from eNodeB1 to
eNodeB2 or eNodeBn, inter-MME is not triggered. When users perform handover from
eNodeBn to eNodeBn+1, inter-MME handover is triggered.

Figure 2-2 S1-Flex Example

S1 Interface
eNB1

MME1

eNB2 MME Group 1

...
MME2

eNBn

eNBn+1 MME3
MME Group 2

If the SCTP to one MME is broken, users which already access to this MME will be
performed with release procedure. And this MME will be deleted from MME selection list.
New request users will connect to another MME according to updated MME selection.

3 Scenario

3.1 Application Condition

one eNodeB is connect to multiple MME/S-GWs and eNodeB in the MME POOL area.

3.2 IOT Status

For this function, MF820 and MF820D have been tested. More details please check the
following tables:

2017 ZTE CORPORATION. All rights

ZTE Confidential Proprietary 3
reserved.
 FDD LTE S1-FLEX Feature Guide Internal Use Only

Table 3-1 IOT status

Commercial
Name Type Vendor Version
Use
MF820 Dongle ZTE 3.3 Yes
MF820D Dongle ZTE 3.3 Yes

3.3 EPC Status

The EPC versions now used are shown in the following table:

Table 3-2 EPC status

NE Version
MME ZXUN-uMAC V4.10.10.P7.B2b
XGW ZXUN-xGW V4.11.20P2.B6
SGSN ZXUN-uMAC V4.10.10.P7.B2b
MSC ZXWN-MGW V4.10.20.P4.B3
HSS ZXUN USPPV4.09.20.B5

4 Key Parameters and Configuration

Figure 4-1 Multi-SCTP Configuration

S1 SCTP configuration configure in Upper Protocol->SCTP. We need to be configure

Multiple S1 SCTP in OMC when we test S1-Flex.And We do not need other special
configuration in OMC for S1-Flex.

5 Function Test
The pre-condition for S1-Flex function test is as follows:

MME1 and MME2 which are configured as the same PLMN work normally.

2017 ZTE CORPORATION. All rights

ZTE Confidential Proprietary 4
reserved.
 FDD LTE S1-FLEX Feature Guide Internal Use Only

The S1 sctp connection between eNodeB and two MMEs is normal.

The two MMEs in system have same Group-ID but with different MMEC.

The test steps test are as follows:

1. Power on one UE and make sure that the UE camps on the LTE service cell.
2. Initial and finish an IMSI Attach and Ping operation to the application server.
3. Repeat step1 to step2 10 times, to confirm the MME which UE attach to by
using Wireshark to record the destination IP of the Initial UE Message
message.
4. Block the sctp connection between eNdodeB and MME1 through EMS
client.
Power on one UE and make sure that the UE camps on the LTE service cell.UE
Initial and finish an Attach.
5. Do the ftp service to application server for some minutes, and then detach
UE
6. Unblock the sctp connection between eNodeB and MME1,and block the
sctp connection between eNdodeB and MME2 through EMS client.
7. Initial and finish an attach operation.
8. Do the ftp service to application server for some minutes.

In this way, by step1-3 we can judge whether UE sometimes access to MME1,

and sometimes access to MME2 according mme loadbalance. By step 4-5 we
can judge whether UE access to MME1. In step 6-8,UE access to MME2, The
FTP service is normal.

2017 ZTE CORPORATION. All rights

ZTE Confidential Proprietary 5
reserved.