Documente Academic
Documente Profesional
Documente Cultură
eRAN Sharing
Li Yongqing (Employee ID: 141602)
www.huawei.com
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.
S1 interface
Itf-N
F1: operator A
Shared eNodeB F2: operator B
Shared EMS
f1 f2
f1 f1 f2
f2
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.
60% for
Operator A
40% for
Operator
B
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.
LTE UE Others
MOCN Architecture
Oper A EPC Oper B EPC
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.
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 !
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
Mobility Management
MME/SGW MME/SGW
Oper A Oper B
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.
MME SGW
S1 flex
S1 interface
Shared eNodeB
Shared frequency
f1
f1 f1
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.
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.
In eRAN sharing with dedicated carrier and MOCN, transmission resources are managed in the
same mode.
S1 interface
X2 interface
Complete sharing for all operators
S1-Flex
www.huawei.com
NNSF
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.
When multiple SCTP links are established, each link is identified by SCTP IP+ port ID.
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).
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.
In some scenarios, the MME can set relative capacity without reference to the actual
processing capabilities, for example, when adding MMEs or removing MMEs.
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;
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