5 ERAN Sharing and S1-Flex

03/16/17 Security Level:
eRAN Sharing
Li Yongqing (Employee ID: 141602)
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Agenda
Basic Concepts
eRAN Sharing with Dedicated Carrier
eRAN Sharing with Common Carrier (MOCN)
In this course, you will:
1. Learn the concepts and functions of eRAN sharing
2. Learn eRAN sharing with dedicated carriers.
3. Learn eRAN sharing with common carriers
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

What is eRAN Sharing?
Broadly speaking, network sharing includes multiple types of sharing types, and
any components of a network are shared by multiple operators is called network
sharing.
For example: Transport network sharing
Access network sharing (eRAN sharing),
EPC sharing (GWCN).
3GPP TS 23.251 defines and specifies the network sharing architecture and
functions.
Access network sharing consist : MOCN and eRAN Sharing with dedicated carrier.
1. eRAN Sharing with dedicated carrier: use different frequency carrier ;
2. eRAN Sharing with common carrier(MOCN): share the same frequency carrier ans
eNodeB harware.

Challenges for Operator to Deploy LTE Networks Independently
Expensive LTE spectrum license fees

Most of LTE frequency spectrum resources are consumed. When the frequency spectrum
resources are limited, operators share the resources.
High network deployment costs Cost Coverag Applications

& Services
High requirements for providing e
network coverage in a short

period
How to reduce the pressure of network deployment? How to create new services as soon as possible?

Main Functions and Values of eRAN Sharing
eRAN Sharing involves several telecom

operators, but there is only one team to
planning, build the network, maintenance.
Fast deployment It s not allowed to be operated and

Enhanced coverage maintenance by several operators at the
same time. Operators could determine a
CAPEX&OPEX primary operator, or several operators build
saving
a joint team.
eRAN
sharing For example, Sweden Net4Mobility consists
of operators Tele2 and Telnor and is
responsible for contacting Huawei.
Standard interference and solution

This simplifies operation mode is better for
Transparent to UE and EPC OM and management in the future.
Service convergence

Architecture of eRAN Sharing
Sharing status of NEs and interfaces
NE or Interface eNodeB EPC OSS NMS S1 Itf-N

Shared/Independ Shared Independent Shared Independent Independent Independent
ent

Related Concepts
Primary Operator
The primary operator is responsible for the eRAN network. The primary operator provides the following functions:
Controls the eRAN sharing function.
Manages and assigning licenses.
Configures eRAN system parameters.
Adds the information of secondary operators.
Configures parameters of secondary operators.
Secondary Operator
The secondary operator shares eRAN resources provided by the primary operator. The secondary operator has only read and write
permissions, related to some eRAN resources and configuration data.
Primary PLMN ID
The Public Land Mobile Network (PLMN) ID is composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). In
eRAN sharing with common carrier, each cell has multiple PLMN IDs. Among these, the PLMN ID of the primary operator is called the
primary PLMN ID. The PLMN IDs of other operators are called the secondary PLMN IDs.
License
A license is an authorization agreement between the vendor and the customer in terms of the application scope and service lifetime of
products. Licenses related to eRAN sharing are the feature license and capacity license.

Two Modes of eRAN Sharing
According to the sharing of frequency spectrum resources, eRAN sharing consists of
eRAN sharing with common carrier and eRAN sharing with dedicated carrier.
eRAN sharing with
dedicated carrier eRAN sharing with common
carrier (MOCN)
The eRAN resources, including carrier

Different operators have their own and eNodeB hardware resources, are
carrier resources. Only the eNodeB shared by multiple operators, and CNs are
hardware resources are shared by independent.
operators, and CNs are independent. Sharing fault management (FM) and CM,

Independent cell-level configuration and partially sharing performance
management (CM). management (PM).

Cell-level features of operators are Sharing RF units.
independent. High frequency spectrum usage.
eRAN2.2 supports the two modes, but They cannot be configured on the eNodeB at
the same time. Huawei supports a maximum of four operators for eRAN sharing.

Dedicated
Carrier Mode
eRAN Sharing with Dedicated Carrier

Dedicated
Carrier Mode
Architecture of eRAN Sharing with

Dedicated Carrier Oper A EPC Oper B EPC
Oper A NMS Oper B NMS
MME SGW MME SGW
S1 interface
Itf-N
F1: operator A
Shared eNodeB F2: operator B
Shared EMS
f1 f2
f1 f1 f2
f2
1. Shared eNodeB and independent CNs.

2. Shared eNodeBs can connect to non-shared eNodeBs.
3. Shared eNodeBs are managed by one set of EMS to provide different itf-N interfaces for NMSs of
different operators.
4. The EMS can be operated by the maintenance team of one operator or a joint team of several operators.

Dedicated
Carrier Mode
Independently Deploying S1-Flex

Oper A EPC Oper B EPC
SGW SGW SGW MME

MME
MME SGW
S1 flex
S1 interface
Shared eNodeB
f1 f2
f1 f1 f2
f2
Operators can deploy S1-flex independently, and the nodes are selected in an operator
based on allocation proportion.

Dedicated
Carrier Mode
Feature and Capacity Management

In dedicated carrier mode, one eNodeB has only one external license file.
Cell-level features are independently configured and activated by operators.
The number of licensed active users can be independently configured by operators.
Number of active users of operator A + Number of active users of operator B Total number of
licensed active users
60% for
Operator A
40% for
Operator
B
Shared operators can deploy scalable bandwidths.

The traffic control is not performed independently by operators. The eNodeB only calculates the total
traffic volume and ensures that the traffic volume does not exceed the licensed traffic volume.

Dedicated
Carrier Mode
OSS Management
Partially Independent CM/FM/PM
CM FM PM
Cell-level parameters can Cell-level alarms are
Cell-level counters are reported
be independently reported on an operator
individually to different operators
configured by operators. basis.
through the Itf-N interface.
Alarms are not reported
All the eRAN system on an operator basis;
parameters are configured instead, they are sent to
by one OM team. the NMSs of all
operators through the Itf-
N interface.

Dedicated
Carrier Mode
Impact of Dedicated Carrier Mode on NEs

EPC eNodeB
Require software upgrade to support the
No impact dedicated carrier mode.
Require multiple RF units.
LTE UE Others
No impact X2 transmission resources are shared.

MOCN
eRAN Sharing with Common Carrier (MOCN)

MOCN
MOCN Architecture
Oper A NMS Oper B NMS MME SGW SGW

MME
S1 interface
Itf-N
Shared eNodeB
Shared EMS
f1 Shared frequency
f1
f1
In MOCN, multiple operators share the eRAN resources, including carrier
resources and eNodeB hardware resources, and different operators share the
same cell.
Each shared cell broadcasts the PLMN IDs, related to each operator sharing
the cell/frequency. The Huawei solution enables a maximum of four operators
at the same time.
It is managed by one set of EMS, and connects to the NMS of each operator
using the independent Itf-N interface.

Key Techniques Used in MOCN
The feature of MOCN uses the following key techniques:

1. EPC routing
2. Mobility management
3. Feature and capacity management
4. OSS system management

MOCN
EPC Routing (1) Subscription UEs of operator A or B
Oper A Oper A Oper B

Each cell broadcasts the PLMN IDs of shared operators using
SIB1.
EPC The UE decoding the broadcast message chooses its HPLMN (A
EPC EPC
Node 1 or B). The UE sends the PLMN ID to the eNodeB through the
Node 1
Node N
RRC Connection Setup Complete message, and then the
eNodeB selects an S1 interface based on the PLMN ID.
S1-flex
The eNodeB selects an S1 interface based on the
RegisteredMme IE in the Initial UE Message or the topology rule.
Route to A Route to B The eNodeB checks whether the PLMN ID in the ServedPlmns
of the S1 interface is the same as the PLMN ID carried in the
RRC Connection Setup Complete message received by the
Shared
eNodeB eNodeB. If yes, go to step f. If no, go to step e.
Indicate selected
The selected PLMN ID traverses the ServedPlmns of all
Indicate selected
As PLMN-id interfaces to determine the S1 interface of the operator's EPC to
Bs PLMN-id
which the UE connects.
The eNodeB sends the Initial UE Message to the EPC using the
S1 interface.
Uu
EPC routing is performed.
interface - The EPC determines whether the UE has a subscription to
services.
As subscriber
- If it is a subscribed or roaming UE, the UE is admitted.
Bs subscriber
- If it is not a subscribed or roaming UE, the UE is rejected, and
the UE has to attempt to choose another PLMN ID.
Simple, fast, and standard routing !

MOCN
EPC Routing (2)

Subscribers that have roaming services with only operator A or B
The UE enters the MOCN cell and selects the PLMN and
shared cell. During registration, only the EPC of the operator
that has roaming services with the subscriber receives the
registration request.
Route to A
Or Route to B
Shared
eNodeB
Indicate selected A or Bs Subscribers that have roaming services with operator A and operator B
PLMN-id The EPC selects UE-dependent behaviors.
If the eSIM card does not contain the preferential PLMNs controlled by
Uu the UE and operator, the UE selects the PLMN ID of an operator at
interface
random, that is, the UE is routed to operator A or B at random.
Roaming subscriber

MOCN
Mobility Management
MME/SGW MME/SGW
Oper A Oper B
How to send the

PLMN message?
Bs UE
X2 X2
handover
Shared eNB X2 X2 Shared eNB
As UE
handover
Intra LTE
MOCN Shared Area MOCN Shared Area
Within the coverage area of an operator, UEs can be handed over from one shared
eNodeB to another shared or non-shared eNodeB.
During UE handovers, the EPC providing services are not changed.

MOCN
Independently Deploying S1-Flex by MOCN
SGW SGW SGW MME

MME
MME SGW
S1 flex
S1 interface
Shared eNodeB
Shared frequency
f1
f1 f1
In MOCN, operators can deploy S1-flex independently.

MOCN
Capacity and Feature Management

The licenses of system features and capacity are uniquely offered, configured, and managed by
the primary operator.
In MOCN, one eNodeB has only one external license file.
The licenses are categorized into the feature license and capacity license.
Feature license: Features are fully shared by all operators because the cells on the eNodeB side
are fully shared.
Capacity license: It includes the number of active users, traffic volume, power, and scalable
bandwidth.
60% for The operator type is configured using the

Operator A CnOperatorType parameter.
The active users of the eNodeB can be distributed
among operators in proportion. The proportion is
40% for
Operator B
specified by the CnOperatorId and
MaxUserNumRate parameters. The latitudes of other
licenses are the same for all operators.

MOCN
OSS System Management

Partially Independent CM/FM/PM
CM FM PM
Cell parameters are FM instances are not Some key counters are reported
shared by several operator specific. individually to different operators
operators, and all the Operators obtain the using the Itf-N interface; other
eRAN system parameters same FM data using the data is shared for all operators.
are configured by one OM Itf-N interface.
team.
Only one set of
parameters are set,
including cell parameters
and network optimization
parameters.
The OSS system supports configuration, fault, and performance management in case of OSS
shared by multiple operators.

MOCN
Impact of MOCN on NEs

EPC eNodeB
Requires software upgrade to support MOCN.

No impact
LTE UE Others
Each operator must have a unique Mobility
The UE complies with LTE protocols Management Entity Code (MMEC).
and supports MOCN messages by Only a TAC is broadcast in an MOCN cell.
default. Global eNB Identifier and E-UTRAN Cell
Global ID contain the MCC and MNC, which
must be unique.
eNodeB ID and E-UTRAN Cell must be unique.

Dedicated
MOCN
Transmission Resource
Carrier Mode
In eRAN sharing with dedicated carrier and MOCN, transmission resources are managed in the
same mode.
S1 interface
Logical port 1 Operator A

Physical Link
Logical port 2 Operator B
Operator-specific and independent: allocating dynamic bandwidth for

operators, and each operator cannot use the bandwidth beyond the
scope of the allocated bandwidth.
X2 interface
Complete sharing for all operators

03/16/17 Security Level:
S1-Flex
Li Yongqing (Employee ID: 141602)
www.huawei.com

Agenda
S1-Flex
NNSF

What is S1-Flex?
S1-flex on an LTE/SAE network is a feature that enables one eNodeB to set up S1-MME
connections to multiple MMEs, which form a resource pool known as an MME pool. When a
UE attaches to the network through an eNodeB, the eNodeB selects the serving MME of the
UE and sets up a dedicated S1 connection.

Benefits of S1-Flex
When moving within the area covered by an MME pool, which is known as an MME pool area,
a UE does not need to change its serving MME, reducing the signaling overheads in
transmission and processing.
Load rebalancing is implemented among the MMEs in the same MME pool, resulting in
overall capacity gain.
Network management is simplified. For example, topology adjustments are easy to perform
and do not have a great impact on the ongoing services, and adding or removing MME nodes
is convenient to perform.
Each MME in an MME pool is a cold standby of the other MMEs in the MME pool, improving
the network reliability.

Main Techniques Used in S1-Flex
With the S1-flex feature, one eNodeB is connected to multiple MMEs. In such a
case, the eNodeB must be capable of routing signaling messages of UEs to
different MMEs. The basic mechanisms and functions related to the S1-flex feature
are as follows:
MME pool selection
MME selection within the MME pool
Load rebalancing among MMEs
MME overload processing

Impact of S1-Flex on Network Deployment -
Networking
In order for all the MMEs in the MME pool to serve the MME pool area, each MME
in the MME pool must be connected to all the eNodeBs in the MME pool area. In
this way, each eNodeB is connected to all the MMEs in the MME pool.
The physical link may require only one Ethernet cable, but the eNodeB must
connect to several MMEs in terms of logical links.

Impact of S1-Flex on Network Deployment -
Configuration
1. The eNodeB must negotiate with multiple MMEs over parameters. The negotiated
parameters include MNC, MCC, and TAC.
2. The eNodeB can correctly route the UE signaling messages to different MMEs
using the IPRT command.
3. The eNodeB must establish multiple SCTP links to multiple MMEs. When SCTP
links are set, the parameters of the peer end (MME) such as IP address and
SCTP port ID are required.
When multiple SCTP links are established, each link is identified by SCTP IP+ port ID.
1024-65535 SCTP for sctp link Configurable

Definition of NNSF (3GPP TS 23.236)
NAS Node Selection Function (NNSF): This function allocates a suitable EPC
node to provide services for a UE and routes the following data of the UE to the
node.
The eRAN selects a suitable EPC node for the initial NAS message using the
NNSF and routes the initial NAS message to the EPC node.
1. If the initial NAS message carries the NRI of the CN node, the message will be
routed to the CN node identified by the NRI.
2. If the initial NAS message does not carry the NRI, the NNSF selects a suitable CN
node based on the load of the CN node and routes the message to the node.
After a UE attaches to a CN node in a pool, the UE is always connected to the CN
before the UE leaves out of the MME pool (except overload scenarios).

NNSF
In S1-flex, the eNodeB must implement the NNSU function using the following techniques:
1. MME pool selection: eNodeBs in overlaps between MME pool areas select one MME
pool based on the topology.
2. MME selection within the MME pool is based on the load configurations of MMEs,
balancing the load among the MMEs and effectively using the processing capabilities.
3. Load rebalancing among MMEs: Load rebalancing is achieved among MMEs by
transferring the UE contexts registered with one MME to other MMEs in the same
MME pool.
4. MME overload processing: When an MME is overloaded, it sends the Overload Start
message to the eNodeB, instructing the eNodeB to take measures, for example,
rejecting non-emergency calls initiated by UEs or rejecting signaling initiated by UEs.

MME Pool Selection l
Through signaling over the X2
interface, each eNodeB obtains
the MME pool information about
its neighboring eNodeBs.
eNodeBs in overlaps between MME pool areas select one MME pool based on the
topology. The probability that the UE changes its serving MME is reduced, reducing
signaling overheads.
For example, there are two MME pool areas. MME pool area 1 is controlled by MME
pool 1, and MME pool area 2 is controlled by MME pool 2.

MME Selection Within an MME Pool
MME selection within an MME pool is based on the load condition, with the intention to
achieve load rebalancing among the MMEs in the MME pool, effectively using the
processing capability of the EPC. MMEs have difference processing capabilities, and
they inform eNodeBs of their respective processing capabilities during the process of
S1 interface setup. MME selection is based on the relative capacities of the MMEs and
the number of dedicated S1 connections that are already set up between MMEs and
eNodeBs. The probability of an MME being selected is directly proportional to the
relative capacity of the MME and inversely proportional to the number of dedicated S1
connections that are already set up between the MME and the eNodeBs.
In some scenarios, the MME can set relative capacity without reference to the actual
processing capabilities, for example, when adding MMEs or removing MMEs.

Load Rebalancing Among MMEs
Objective: With the S1-flex feature, UE contexts registered on one MME can be
transferred to other MMEs in the same MME pool. This function is known as load
rebalancing, and it can be used.
When an MME initiates load rebalancing, the relative capacity of the MME must be
reconfigured and notified to the eNodeB so that the eNodeB does not select the
MME when a UE attaches to the network.

MME Overload Processing
When an MME is overloaded, it sends the Overload Start message to the eNodeB, instructing the
eNodeB to take actions, such as rejecting non-emergency calls initiated by UEs and rejecting signaling
procedures initiated by UEs.
1. When the MME sends the Overload Start message to inform the eNodeB that the MME is overloaded,
the eNodeB does not allocate new UEs to the MME.
2. However, the UEs that are already served by the MME may still access the MME and increase its load
The eNodeB rejects non-emergency data requests. In this case, if a UE initiates an ordinary service
connection request, the eNodeB rejects the request. However, if the UE initiates a signaling connection
or emergency call request, the eNodeB serves the UE.
3. The messages are sent only to some eNodeBs.
4. Using the information element in the Overload Start message, the MME can instruct the eNodeB to
process specific types of calls initiated by UEs.
After MME overload is cleared, the MME sends an Overload Stop message, asking the eNodeB to
restore services.

Enabling S1-Flex
From eRAN2.1, eNodeB cancel the S1FlexSwitch Whether
the eNodeB has the S1-flex feature deponds on the license.
Configuration Steps
1.Need to get the following information about each MME firstly
MCC,MNC,TAC SCTP ,IP ,MME (R8/R9)
2.Add SCTP link to each MME
3.Add S1 interface with MML command:ADD S1INTERFACE
ADD S1INTERFACE: S1InterfaceId=0, S1SctpLinkId=0, CnOperatorId=0;
ADD S1INTERFACE: S1InterfaceId=1, S1SctpLinkId=1, CnOperatorId=0;

Disabling S1-Flex
Before disabling the S1-flex feature for an eNodeB, you must decide which MME will serve the TA to which the eNodeB
belongs. The eNodeB remains connected only to this MMEs after S1-MME connections to other MMEs are all removed.
Removing an S1 interface interrupting all services over this interface. To prevent this from occurring, you must block
this interface before disabling the S1-flex feature. After you do so, the eNodeB, in the NNSF, does not select the MME
connected to this interface for UEs that attach later. However, the eNodeB continues providing context services for
UEs that are already carried on this interface.
The eNodeB delivers each paging message sent to it from the MME connected to the blocked S1 interface. However,
the eNodeB does not select this MME to set up a connection for the paged UE. Instead, the eNodeB selects an MME
connected to an S1 interface that is not blocked.
Coverage of the MME pool areas before the S1- Coverage of the MME pool areas after the S1-
flex feature is disabled flex feature is disabled

Thank you
www.huawei.com

5 ERAN Sharing and S1-Flex

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

5 ERAN Sharing and S1-Flex

Hochgeladen von

Copyright:

Verfügbare Formate

03/16/17 Security Level:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

Expensive LTE spectrum license fees

High network deployment costs Cost Coverag Applications

network coverage in a short

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

eRAN Sharing involves several telecom

Fast deployment It s not allowed to be operated and

Standard interference and solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

Sharing status of NEs and interfaces

NE or Interface eNodeB EPC OSS NMS S1 Itf-N

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

The eRAN resources, including carrier

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

eRAN Sharing with Dedicated Carrier

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

Architecture of eRAN Sharing with

Oper A NMS Oper B NMS

MME SGW MME SGW

1. Shared eNodeB and independent CNs.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

Independently Deploying S1-Flex

SGW SGW SGW MME

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

Feature and Capacity Management

Shared operators can deploy scalable bandwidths.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

Impact of Dedicated Carrier Mode on NEs

No impact X2 transmission resources are shared.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

eRAN Sharing with Common Carrier (MOCN)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

Oper A NMS Oper B NMS MME SGW SGW

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

The feature of MOCN uses the following key techniques:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

EPC Routing (1) Subscription UEs of operator A or B

Oper A Oper A Oper B

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

EPC Routing (2)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

How to send the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

Independently Deploying S1-Flex by MOCN

Oper A EPC Oper B EPC

SGW SGW SGW MME

In MOCN, operators can deploy S1-flex independently.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

Capacity and Feature Management

60% for The operator type is configured using the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

OSS System Management

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

Impact of MOCN on NEs

Requires software upgrade to support MOCN.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

Logical port 1 Operator A

Logical port 2 Operator B

Operator-specific and independent: allocating dynamic bandwidth for