SPD ERAN7.0 RAN Sharing Feature Introduction

Security Level: INTERNAL
Huawei eRAN7.0
RAN Sharing Feature
Introduction
www.huawei.com
Huawei NodeBs
April in 2006
HUAWEI TECHNOLOGIES CO., LTD.
Contents
LTE RAN Sharing Solution
Architecture and Scenario
RAN Sharing with Common Carriers
RAN Sharing with Dedicated Carriers
Hybrid RAN Sharing
Resource Management
Transmission Configurations
Planning
Installation and Commissioning
Acceptance and Maintenance
FAQs
Reference Documents
Acronyms and Abbreviations
Huawei Confidential
Page 2
RAN Sharing Solution (Dedicated/Common Carrier Policy)

LOFD-001037 RAN Sharing with Dedicated Carrier
Operator A's EPC
Operator A's
NMS
Operator B's EPC
Operator B's
NMS
RAN sharing with dedicated carriers:

Only one PLMN ID is supported in each cell.
LOFD-001036 RAN Sharing with Common Carrier

Operator A's EPC
Operator A's
NMS
Operator B's EPC
Operator B's
NMS
RAN sharing with common carriers:

The primary PLMN IDs of cells must be consistent.
Huawei Confidential
Page 3
RAN Sharing Solution (Hybrid Carrier Policy)

LOFD-070206 Hybrid RAN Sharing
Operator A's EPC
Operator A's EPC
Operator B's EPC
Operator D's EPC
Operator A's Operator D's

NMS
NMS
Operator A's Operator B's

NMS
NMS
Hybrid RAN sharing

Each eNodeB operates on two or more frequencies.
At least one frequency is shared by operators.
Two or more cells have different primary PLMN IDs.
A maximum of six operators can share one eNodeB and LOFD-001086 RAN Sharing by More Operators needs to be purchased.
Shared and non-shared cells can be covered by the same eNodeB and primary operators of cells can be different.
In a non-shared cell, cell-level features and resources can be configured and used by an operator. In a shared cell, cell-level
features and resources are shared by operators. eNodeB-level features and resources are shared by operators.
The EMS in Hybrid RAN sharing is the same as that in RAN Sharing with common/dedicated carriers. For details, see the preceding
slide.
Both the MME and SGW can be shared or independent.
eRAN7.0
Huawei Confidential
Page 4
Comparison of LTE RAN Sharing Modes

Item
RAN Sharing with

Common Carriers
RAN Sharing with Dedicated

Carriers
Hybrid RAN Sharing
Carrier
Shared
Independent
Shared or independent
Network OAM
CMs are shared.

Some PMs/FMs are
shared.
Cell-level CMs are independent and

eNodeB-level CMs are shared.
Some PMs/FMs are shared.
When cells are shared, CMs are shared.

When cells are independent, cell-level CMs are
independent and eNodeB-level CMs are
shared.
Some PMs/FMs are shared.
Shared
Cell-level resources are expanded

independently.
eNodeB-level resources are shared.
When cells are shared, resource are shared.

When cells are independent, cell-level
resources are expanded independently.
eNodeB-level resources are shared.
Feature
deployment
Shared (Some feature

parameters are adjusted
independently.)
Cell-level features are deployed

independently and parameters of the
features are adjusted independently.
eNodeB-level features are shared.
Some feature parameters can be
adjusted independently.
Cell sharing: Shared (Some feature

parameters are adjusted independently.)
Cell non-sharing: Cell-level features are
deployed independently and parameters of the
features are adjusted independently.
eNodeB-level features are shared and some
feature parameters are adjusted independently.
Impact on the
EPC
If the MME is shared, the

MME needs to support
multiple PLMN IDs.
If the MME is shared, the MME needs to

support multiple PLMN IDs.
If the MME is shared, the MME needs to

support multiple PLMN IDs.
Requirements
on UEs
None
None
None
Network
adjustment
In RAN sharing with common carriers, more RAN resources can be shared, resulting in improved user experience and high
resource usage.
In RAN sharing with dedicated carriers, cells are independent.
In hybrid RAN sharing, networks can be deployed flexibly and only some cells are shared. In addition, primary and secondary
operators can also be flexibly configured.
Huawei Confidential
Page 5
eRAN7.0
Definition of the Network Sharing Architecture in 3GPP
MOCN
GWCN
3GPP TS 23.251 defines the network sharing architecture. The preceding figure shows the UMTS RAN sharing
architecture. This architecture is also applicable to LTE RAN sharing, in which the SGSN, RNC, and Iu interface
are replaced with the MME, eNodeB, and S1 interface, respectively.
The GGSN or SGW sharing architecture is supported by default and therefore it is not listed in 3GPP protocols.
3GPP LTE protocols support LTE RAN sharing. Therefore, all LTE UEs support RAN sharing by default.
LOFD-001037 RAN Sharing with Dedicated Carrier, LOFD-001036 RAN Sharing with Common Carrier, and
LOFD-070206 Hybrid RAN Sharing support multi-operator core network (MOCN) and gateway core network (GWCN).
Huawei Confidential
Page 6
Network Sharing Architecture with Common Carriers

Operator As NMS
Operator
As EPC
Operator Bs NMS
Operator
Bs EPC
S1 interface
X2 interface
Broadcasting in SIB1
iManagerTM M2000
eNodeB
Shared RAN
Shared EMS
X2
interface
F1
F1
F1
F1
F1
F1
F1
Non-shared eRAN
Shared carrier, and shared MME in GWCN or
independent MME in MOCN
The EMS is shared and the NMS can be independent.
The multi-operator PLMN IDs are broadcast in SIB1.
Huawei Confidential
SystemInformationBlockType1
{
PLMN-IdentityList
{
OperA PLMN-id
OperB PLMN-id
}
Page 7
Network Selection Process

Operator As EPC
Shared eNodeB
MME
S-GW
Operator As
PLMN
Shared
cell
Operator Bs
PLMN
MME
Shared
cell
Operator As UE
Operator As
roaming UE
Shared
cell
S-GW
Operator Bs UE
Operator Bs
roaming UE
Operator Bs EPC
The SIB 1 message broadcasts PLMN IDs of all operators in each cell.
The UE selects the PLMN ID and sends the selected PLMN ID to the eNodeB over RRCConnectionSetupComplete.
Subscribed UEs of the operators
The shared eNodeB routes the UE to the corresponding EPC based on the selected PLMN ID.
Roaming UEs
The roaming UE selects a PLMN ID and a shared cell based on related principles. The UE is served by the operator
to which the UE belongs and with which the UE signs a roaming protocol.
If a UE signs a roaming protocol with both operator A and operator B, the PLMN ID selected by the UE determines
which operator serves the UE.
Huawei Confidential
Page 8
Camping Policy
Operator A's
Operator B's
Operator A's
Operator B's
MME/SGW
MME/SGW
MME/SGW
MME/SGW
Operator A's
frequency
information
Operator A's
or B's UE
Common broadcasting information
Operator A's UE
Operator B's
frequency
information
Operator B's UE
UE dedicated information
Cell reselection and reselection are controlled by the system priority and frequency priority.
Two types of priorities are available:
Common priority: The priority is broadcast in the SIB message and all UEs in the cell share the
information.
Dedicated priority: The priority is sent to the UE over the RRCConnectionRelease message and is used
only by the UE. Only shared cells use the dedicated priority.
Huawei Confidential
Page 9
Mobility Management
Operator
Operator
As EPC
Bs EPC
Handover
GSM/UM
TS cell
GSM/UM
TS cell
Handover
Operator A's UE
MOCN
cell
Non-shared
Operator A's UE LTE cell
Handover
Handover
Operator Bs UE
Operator Bs UE
Non-shared
LTE cell
Configured data and specifications of neighboring cells are shared between operators.
UEs can be handed over between shared cells and between non-shared neighboring LTE cells of the same operator.
UEs can be handed over between shared cells and between neighboring GSM/UMTS cells of the same operator.
Inter-PLMN handovers are supported, which are used on a per operator basis.
Huawei RAN sharing with common carriers, like traditional networks, supports
handovers in various scenarios.
Huawei Confidential
Page 11
Outgoing Handover
The source cell selects a neighboring cell that is included in a PLMN allowing handovers
as the target cell and then selects the serving PLMN in the target cell after the handover.
If the target cell supports the serving PLMN in the source cell, the serving PLMN in the
source cell is selected as the serving PLMN in the target cell after the handover.
PLMNs allowing handovers include the following:
Serving PLMNs
EPLMNs in the handover restriction list (HRL)
Inter-PLMN handover lists configured on the eNodeB based on the serving PLMN
Huawei Confidential
Page 12
X2-based Incoming Handover

Operator
A's MME
Operator
B's MME
X2-based handover in MOCN
The HRL is
optional for
MOCN.
Operator
A's MME
Operator
B's MME
The HRL is
mandatory for GWCN
in RAN sharing with
common carriers.
X2-based handover in GWCN
The target eNodeB needs to determine the UEs serving PLMN in X2-based handovers. Otherwise,
X2-based handovers will fail.
The HRL IE contains the UEs serving PLMN, but this IE is optional for the MME.
How to identify the UEs serving PLMN in the X2-based handover procedure:
If the HRL is available, the target eNodeB sets the serving PLMN in the HRL as the UEs serving PLMN.
If the HRL is not available, the target eNodeB finds the MME serving the UE based on GUMMEI IE in HANDOVER
REQUEST.
If the MME supports only one PLMN, the target eNodeB sets this PLMN as the UEs serving PLMN in MOCN.
If the MME supports more than one PLMN IDs in GWCN:
If the target cell broadcasts only one PLMN, the target eNodeB sets this PLMN as the UEs serving PLMN.
Otherwise, the target eNodeB sends HANDOVER PREPARATION FAILURE to the source eNodeB.
Huawei Confidential
Page 13
S1-based Incoming Handover

Operator
As MME
Operator
Bs MME
The HRL is
optional for
MOCN.
Operator A's
and B's MME
Operator A's
and B's MME
The HRL is
mandatory for
GWCN in RAN
sharing with
common carriers.
Operator
A's UE
Operator
A's UE
S1-based handover in GWCN
S1-based handover in MOCN
The target eNodeB needs to determine the UEs serving PLMN in S1-based handovers. Otherwise, S1based handovers will fail.
The HRL IE contains the UEs serving PLMN, but this IE is optional for the MME.
How to identify the UEs serving PLMN in the S1-based handover procedure:
If the HRL is available, the target eNodeB sets the serving PLMN in the HRL as the UEs serving PLMN.
If the HRL is not available, the target eNodeB finds the MME sending the HANDOVER REQUEST message:
If the MME supports only one PLMN, the target eNodeB sets this PLMN as the UEs serving PLMN in MOCN.
If the MME supports more than one PLMN IDs in GWCN:
If the target cell broadcasts only one PLMN, the target eNodeB sets this PLMN as the UEs serving PLMN.
Otherwise, the target eNodeB sends HANDOVER PREPARATION FAILURE to the source eNodeB.
Huawei Confidential
Page 14
Multi-operator Independent LTE-to-UMTS Mobility Policy

PSHO and RIM need to be supported by the UMTS. Operators have their own UMTS
networks but have different PSHO/RIM capabilities.
In versions earlier than eRAN6.1, the PSHO/RIM switch is at the eNodeB level. Therefore,
it is good practice to enable the PSHO/RIM function when end-to-end supports are
available for all operators. Otherwise, call drops or signaling shocks occur.
In eRAN6.1, the multi-operator independent LTE-to-UMTS mobility policy is supported.
With this feature, the peer-end PSHO/RIM capabilities including the PLMN ID, RNC ID,
PsHoCapCfg-OFF/ON, and SiByRimCapCfg-OFF/ON can be configured independently. In
this case, the PSHO/RIM function can be used flexibly and accurately.
This feature applies to RAN sharing as well as the roaming scenario and the scenario
where EPC vendors are different.
Huawei Confidential
Page 15
Common-Carrier CM/FM/PM
CM/FM/PM
CM
Configurations in RAN sharing with
common carriers are the same as
those in RAN non-sharing. All
eRAN parameters are configured
by an OM team and some
parameter configurations require
negotiation between operators.
The configuration information
reported over the northbound
interface (Itf-N) on the OSS side is
the cell-level information about the
cells belonging to operators and
eNodeB-level public information
about operators.
PM
FM
The S1 and X2 interfaces on the
eNodeB side can report alarms on
a per operator basis.
Count key counters on the

eNodeB side on a per operator
basis.
Itf-N on the OSS side reports

some key alarms such as S1 and
X2 interface alarms on a per
operator basis. For example,
operator A obtains dedicated
alarm information of operator A
and public alarm information.
Itf-N reports key counters on the

OSS side on a per operator
basis. For example, operator A
obtains dedicated PM data of
operator A and public PM data.
LTE RAN is managed only by one OM team and the shared EMS manages the public OM function
including the software upgrade, and system configurations and reconfigurations.
Huawei Confidential
Page 16

Operator As EPC
Operator As carrier
Shared eNodeB
MME
Cell A
S-GW
PLMN A
PLMN A
Operator As UE
Cell A
Cell A
Cell B
PLMN B
Cell B
Operator As
roaming UE
PLMN B
Cell B
MME
S-GW
Operator Bs EPC
Operator Bs UE
Operator Bs carrier
Operator Bs
roaming UE
Operators broadcast their HPLMN IDs in their own cells.

Subscribed users of operator A or B are routed to the cells belonging to the operator by identifying the
HPLMN ID.
The eNodeB routes users to their EPCs based on their HPLMN IDs.
Roaming UEs select PLMN IDs and shared cells based on related principles. The UE is served by the
operator to which the UE belongs and with which the UE signs a roaming protocol.
Huawei Confidential
Page 17
Mobility Management
Operator As
network
Operator
As UE
Shared eNodeB
Carrier 1
Operator Bs
network
Carrier 2
Operator
Bs UE
LTE network sharing with dedicated carriers
LTE/GSM/UMTS network
Independent neighboring cell configurations

Operators' frequencies and cells are independent, and therefore UE handover principles on shared LTE
networks are the same as those on an independent LTE network.
Inter-PLMN handovers are supported, which are used on a per operator basis. The inter-PLMN
handover is configured by running eNodeBAlgoSwitch ::HoAlgoSwitch.
Huawei Confidential
Page 18
Dedicated-Carrier CM/FM/PM
CM/FM/PM
CM
In RAN sharing with dedicated
carriers, all eRAN parameters are
configured by an OM team. Cells are
independent. Therefore, the eNodeB
supports operator-based
configurations of cell-level parameters
and no negotiation is required.
eNodeB-level parameter
configurations require negotiations
between operators.
FM
eNodeB side can report alarms on a
per operator basis.
Itf-N on the OSS side reports some
key alarms such as S1 and X2
interface alarms on a per operator
obtains dedicated alarm information
of operator A and public alarm
information.
The configuration information reported

over Itf-N on the OSS side is the celllevel information and eNodeB-level
public information about the cells
belonging to operators.
PM
In RAN sharing with dedicated
carriers, cells are independent.
Therefore, when cell-level
performance counters are counted,
operators can be distinguished based
on specific cells.
Ift-N reports performance counters on
the OSS side on a per operator basis.
That is, each operator reports its
unique performance examples and
public performance examples.
Independent cell-level PM/FM/CM helps operators monitor and maintain their own cells.
Huawei Confidential
Page 19
Hybrid RAN Sharing

Operator As EPC
Operator As carrier
MME
S-GW
PLMN A
Cell A
Shared eNodeB
Operator As UE
Cell A
Operator Bs EPC
PLMN B
S-GW
Shared
cell
Operator Cs EPC
PLMN C
MME
Operator As
roaming UE
Cell A
PLMN B
MME
PLMN A
Shared
cell
Operator Bs UE
Shared
cell
Operator Bs
roaming UE
PLMN C
Operator Bs and Cs carrier
S-GW
Operator Cs UE
Operator Cs
roaming UE
The eNodeB configures primary and secondary information based on cells to broadcast information about primary and secondary
PLMN IDs.
Subscribed users of operator A, B, or C are routed to the cells belonging to the operator by identifying the HPLMN ID.
The eNodeB routes users to their EPCs based on their HPLMN IDs.
Roaming UEs select PLMN IDs and shared cells based on related principles. The UE is served by the operator to which the UE
belongs and with which the UE signs a roaming protocol.
eRAN7.0
Huawei Confidential
Page 20
Hybrid RAN Sharing
Mobility Management
Operator As
network
Shared eNodeB
Carrier 1
Operator Bs
network
Operator
As UE
Operator
Carrier 2 Bs and Cs
UE
Operator Cs
network
LTE network sharing with hybrid carriers
LTE/GSM/UMTS network
If a cell is shared between operators, configurations and specifications of neighboring cells are shared between operators.
If a cell is independent, neighboring cells are configured independently.
If a cell is shared between operators, the cell-based mobility policy is shared between operators. If a cell is independent,
the cell-based mobility policy is used by an operator. The eNodeB-based mobility policy is shared between operators.
Inter-PLMN handovers are supported, which are used on a per operator basis. The inter-PLMN handover is configured by
running eNodeBAlgoSwitch ::HoAlgoSwitch.
eRAN7.0
Huawei Confidential
Page 21
Hybrid RAN Sharing
Hybrid Carrier and CA (eRAN 7.0)
In eRAN6.0, CA is performed only when operators
Operator A's EPC
Operator B's EPC
sharing the two carriers have the same requirements.
f1: shared by operator A and operator B; f2:

shared by operator A and operator B
In eRAN7.0, CA can still be performed even if

operators sharing the two carriers have different
requirements.
f1: shared by operator A and operator B; f2: used

only by operator A; f3: used only by operator B
Operator A can use CA in f1+f2.
Operator B can use CA in f1+f3.
Operator
A's CA
Operator
B's CA
eRAN7.0
Huawei Confidential
Page 22
Hybrid RAN Sharing
Hybrid-Carrier CM/FM/PM
CM/FM/PM
CM
In hybrid RAN sharing, all eRAN
parameters are configured by an OM
team. Cell-level parameters
configured in shared cells require
negotiation between operators. Nonshared cells are independent and
parameters are set by an operator.
eNodeB-level public information is
configured and managed based on
negotiation between all operators.
FM
PM

eNodeB side can report alarms on a
per operator basis.
Some key performance counters can

be counted in shared cells on a per
operator basis.
Itf-N on the OSS side reports some

key alarms such as S1 and X2
interface alarms on a per operator
obtains dedicated alarm information
of operator A and public alarm
information.
Non-shared cells are independent.

Therefore, when cell-level
performance counters are counted,
operators can be distinguished based
on specific cells.
The configuration information

reported over Itf-N on the OSS side
is the cell-level information and
eNodeB-level public information
about the cells belonging to
operators.
Ift-N reports performance counters on

the OSS side on a per operator basis.
That is, each operator reports its
unique performance examples and
public performance examples.
eRAN7.0
Huawei Confidential
Page 23
Resource Management
Resource Management
In RAN sharing, resource management maximizes the throughput

and balances shared resources between operators.
Resource management in RAN sharing includes:
Fair sharing of cell resources (PRBs)
Sharing of specifications of RRC connected users
Fair sharing of traffic licenses
MLB
Huawei Confidential
Page 24
Resource Management
Fair Sharing of Cell Resources (PRBs)

The cell-level resource sharing policy is configured and used in shared cells with common and
hybrid carriers. If CellAlgoSwitch.RanShareModeSwitch is set to ON, admission control,
congestion control, and scheduling policies can be implemented on a per operator basis.
The scheduling algorithm ensures that remaining PRB resources of one operator are used by
another operator and that the eNodeB converges PRBs to their RB ratios in the case of overloads.
HARQ retransmission scheduling, control-plane message scheduling, and semi-dynamic scheduling are preferentially
implemented.
Operators' priorities depend on the proportion of RBs occupied by the operator.
Users are scheduled based on priorities in the descending order.
The admission/congestion control algorithm implements admission and congestion control

based on the GBR satisfaction rate of each operator.
In the uplink: Admission control and congestion control are implemented based on the proportion of occupied cell
RBs, the proportion of RBs occupied by GBR services of each operator, and the QoS satisfaction rate of GBR
services of each operator.
In the downlink, admission control and congestion control are implemented based on the QoS satisfaction rate of
GBR services of each operator.
GBR services can be preempted in the scope of each operator in the event of admission failures.
GBR services can be released in the scope of each operator in the event of overloads.
Huawei Confidential
Page 25
Resource Management
Sharing of the Number of Active Users

On the U2000, the proportion of resources used by each operator can be configured.
The specifications of RRC connected users in RAN sharing can be shared in the following
modes:
Mode 1: complete sharing Resources are shared between all operators.
Mode 2: proportional static sharing Configure the proportion of each operator's resources to be
shared. The operator can only use the configured proportion of resources.
Mode 3: dynamic sharing Configure the resource proportion and penetrable resource proportion
for each operator. When an operator has idle resources, these idle resources can be used by
other operators based on the configured penetrable proportion. When UE congestion occurs for
an operator, the operator can preempt its own resources by setting
ENODEBALGOSWITCH.InterOpUeNumPreemptSwitch to ON.
Proportional static sharing
Complete sharing
A ->
B
<-
Operator As
proportion
Operator Bs
proportion
Huawei Confidential
Dynamic sharing
Operator As proportion Operator Bs proportion

Operator As sharing Operator Bs sharing
Page 26
Resource Management
Fair Sharing of Traffic Licenses
Control the user-plane PDCP load based on the

configured traffic proportion.
On the U2000, the proportion of resources used by each operator can be configured.
In MOCN, traffic resources can be controlled in the following modes:

Mode 1: complete sharing Resources are shared between all operators.
Mode 2: proportional static sharing Configure the proportion of each operator's resources to be
shared. The operator can only use the configured proportion of resources.
Mode 3: dynamic sharing Configure the resource proportion and penetrable resource proportion
for each operator. When traffic congestion of an operator occurs, the operator can preempt its
own resources.
Proportional static sharing
Complete sharing
A ->
B
<-
Operator As
proportion
Operator Bs
proportion
Huawei Confidential
Dynamic sharing
Operator As proportion Operator Bs proportion
Page 27
Resource Management
MLB
Operator As
network
Operator As
load balancing
Sharing between
operator A and
operator B
Operator Bs
network
Operator A Operator B
Number of UEs with

RRC
connections/Number of
UEs consuming PRB
resources
The eNodeB evaluates PRB resource usage and the number of RRC connected UEs. When the PRB
usage of an operator in the source cell is high or the number of UEs in the cell is large, the eNodeB
selects a neighboring cell with light loads of the operator over load interaction and selects UEs with a
low service priority and high resource usage for handovers, which helps the operator to achieve
balance between reserved PRB resources and UE quantity.
eRAN7.0
Huawei Confidential
Page 28
Transmission Network
Operator A's S1
Independent bearer network
Operator B's S1
X2
Shared eNodeB
Ethernet
network
Operator A (MME A
and SGW A)
IP network
Router
Ethernet
network
IP network
Operator B (MME B
and SGW B)
Router
Shared eNodeB
Shared bearer network
Operator A (MME A
and SGW A)
Shared eNodeB
Ethernet
network
IP network
Operator B (MME B
and SGW B)
Router
Shared eNodeB
The independent or shared bearer network is selected based on actual conditions of bearer networks for each operator.
The independent bearer network is independently operated and maintained and the shared bearer network requires low
costs.
Huawei Confidential
Page 29
Example of Flexible VLAN Configurations

Different operators can be configured with different VLANs, preventing the broadcasting
storm, enabling isolation (security), and providing various VLAN priorities.
The eNodeB marks VLANs according to next-hop IP addresses, as shown in the following
figure. Operators can plan VLANs based on their live-network conditions.
Huawei Confidential
Page 30
Operator-based Configurations of Transmission

Resource Groups
Physical ports of the eNodeB are shared between operators. Operators can be mapped to different
transmission resource groups by configuring various IP addresses. In this way, operators can be
distinguished for flow control. If transmission resource groups are not distinguished on a per operator
basis, transmission resources are shared between operators.
The following figure shows port configurations. Operators can plan configurations of transmission
resource groups based on their live-network conditions.
Uplink transmission resource group 1 is
configured with a 50 Mbit/s bandwidth and a
40% weight factor.
Resource
group 1
Operator A's path 1
Operator B's path 1
Resource
group 2
The uplink physical port is configured

with a 100 Mbit/s bandwidth.
Logical
port
Operator A's path n
Physical port
Logical
port
Operator B's path n
Uplink transmission resource group 2 is

configured with a 70 Mbit/s bandwidth and a
60% weight factor.
Huawei Confidential
Page 31
Dynamic Sharing During Uplink Transmission
If the sum of configured bandwidth for transmission resource groups is greater than the bandwidth
configured for the physical port, uplink transmission resources are dynamically shared.
According to preceding examples,

The bandwidth configured for physical ports is 100 Mbit/s and the proportion of weight in transmission
resource group 1 to weight in transmission resource group 2 is 4:6.
The configured bandwidth in transmission resource group 1 is 50 Mbit/s.
The configured bandwidth in transmission resource group 2 is 70 Mbit/s.
When traffic is less than 50 Mbit/s in transmission resource group 2, traffic in transmission resource
group 1 can reach up to 50 Mbit/s, which exceeds the bandwidth calculated based on the weight
proportion between transmission resource groups.
If all transmission resource groups have sufficient data to transmit, transmission resources are
distributed based on the preset weight proportion.
Huawei Confidential
Page 32
Transmission IP Planning (S1)

Common/Dedicated Carriers
Common/dedicated carrier
Operator As
MME
Operator Bs
MME
IP2
Common/dedicated carrier
Operator As
MME
IP2
IP3
Operator As
path
Operator Bs
path
Operator Bs
MME
IP4
Operator As
path
IP1
Shard eNodeB
Common carrier
Dedicated carrier
Operator As and Bs
MME
Operator As and Bs
MME
IP2
Operator Bs
path
IP1
IP3
Shared eNodeB
IP2
Operator A,s
and Bs path
IP1
Shared eNodeB
Operator As
path
IP1
IP4
Operator Bs
path
IP3
Shared eNodeB
The eNodeB can use one or more IP addresses to communicate with the EPC through the S1 interface.
When the MME is shared, the S1-C link of operators with common carriers is shared and that of operators with dedicated carriers is independent.
When the MME is not shared, the S1-C link of operators with common or dedicated carriers is independent.
If the SGW is independently deployed by an operator, the S1-U link is independent. If the SGW is deployed by operators, the S1-U link is
independent or shared, which however cannot be seen from the preceding figure.
Huawei Confidential
Page 33
Transmission IP Planning (X2)

Sharing with Common/Dedicated Carriers
Dedicated carrier
Common carrier
Shared eNodeB
Shared eNodeB
IP2
IP4
IP2
Operator As
path
Operator As and Bs
path
Operator Bs
path
IP1
IP3
IP1
Shared eNodeB
Shared eNodeB
The X2-C link of operators with common carriers is shared and that of operators with dedicated carriers
is independent.
The X2 link can be manually or automatically established.
The X2-U link is independent or shared, which however cannot be seen from the preceding figure.
Huawei Confidential
Page 34
Transmission IP Planning (S1)

Sharing with Hybrid Carriers
Sharing mode: A+B and B
Operator As
MME
Operator Bs
MME
Operator As and Bs
MME
IP2
IP4
IP2
Operator As Operator Bs
path
path
IP1
A+B
Operator Bs
path
Sharing mode: A+B and C+D
Operator As Operator Bs Operator Cs Operator Ds

MME
MME
MME
MME
IP4
IP2
Operator As Operator Bs Operator Bs

and Bs
path
path
path
IP1
IP3
Shared eNodeB
A+B
IP3
Operator As
path
IP5
Operator Bs Operator Cs
path
path
IP3
Shared eNodeB
IP1
IP4
A+B
C+D
IP6
Operator Ds
path
Shared eNodeB
Operators need to establish different S1-C links in different sharing groups (with different primary operators).
If operators are in the same sharing group, S1-C link status depends on MME status. That is, if the MME is independent,
the S1-C link is independent; if the MME is shared, the S1-C link is shared.
If the SGW is independently deployed by an operator, the S1-U link is independent. If the SGW is deployed by operators,
the S1-U link is independent or shared, which however cannot be seen from the preceding figure.
Huawei Confidential
Page 35
eRAN7.0
Transmission IP Planning (X2)

Sharing with Hybrid Carriers
Sharing mode: A+B and C+D

Shared eNodeB
Shared eNodeB
A+B
A+B
IP2
IP4
Operator A and Bs
path
IP2
Operator Bs
path
IP1
IP3
A+B
Operator As and Bs
path
C+D
IP4
Operator Cs and Ds
path
IP1
IP3
A+B
C+D
Shared eNodeB
Shared eNodeB
Operators need to establish different X2-C links in different sharing groups (with different primary operators).
Operators in the same sharing group can share the X2-C link.
The X2 link can be manually or automatically established.
The X2-U link is independent or shared between sharing groups, which however cannot be seen from the preceding
figure.
eRAN7.0
Huawei Confidential
Page 36
Contents
Hybrid RAN Sharing
Resource Management
Planning
FAQs
Reference Documents
Huawei Confidential
Page 37
Planning
According to 3GPP protocols, scenarios contain MOCN and GWCN.
Operator A's NMS
Operator B's NMS
Operator A's
EPC
Operator B's
EPC
MOCN
Independent MME
Shared eNodeB
Shared OSS
Independent NMS
Shared or independent carrier
Operator A's NMS
Operator A's
EPC
Operator B's
EPC
GWCN
Shared MME
Shared eNodeB
Shared OSS
Shared NMS
Shared or independent carrier
Note: In Huawei eRAN7.0 RAN Sharing, the SGW can be shared or independent.
Operator B's NMS
Huawei Confidential
Page 38
Version/License Planning
Versions
Feature LOFD-001036
RAN Sharing with Common
Involved NE
Carrier
eNodeB
U2000
CME
eRAN2.0 or later
iManager U2000
V200R011C00SPC200 or later
iManager U2000-CME
LOFD-001037 RAN Sharing

with Dedicated Carrier
LOFD-070206 Hybrid RAN

Sharing
eRAN2.0 or later
iManager U2000
iManager U2000-CME
eRAN7.0 or later
iManager U2000-CME
V200R014C00
iManager U2000
V200R014C00
License Control
Feature ID
LOFD-001036
Feature Name
RAN Sharing with Common Carrier
License Description
NE
Sale Unit
Controlled by using a switch
eNodeB
Per cell
LOFD-001037
RAN Sharing with Dedicated Carrier
eNodeB
Per cell
LOFD-070206
Hybrid RAN Sharing
eNodeB
Per cell
Feature Conflict: None

Feature Dependency (for All Network Sharing Features)
If sharing of six operators is required, the license for the LOFD-001086 RAN Sharing by More
Operators feature needs to be purchased.
If the MME is independently deployed by each operator, the license for the LOFD-001018 S1-Flex
feature needs to be purchased.
eRAN7.0
Huawei Confidential
Page 39
Acceptance Planning/Tool Planning/Hardware

Planning/Data Planning
Acceptance Planning/Tool Planning
The U2000 and CME are involved.
Hardware Planning
N/A
Data Planning
For details, see descriptions about Transmission Configurations.
Huawei Confidential
Page 40
Contents
Hybrid RAN Sharing
Resource Management
OM Management
Planning
FAQs
Reference Documents
Huawei Confidential
Page 41
Installation and Commissioning - Data Configuration

Process (with Common/Dedicated/Hybrid Carriers)
MOs are configured in different sequences in sharing mode. For details, see
eRAN6.0 Reconfiguration Guide and eRAN7.0 Reconfiguration Guide.
eRAN7.0
Huawei Confidential
Page 42
eNodeB Sharing Mode
The ENodeBSharingMode MO consists of the parameter that indicates the sharing

mode of the eNodeB. The eNodeB supports the following modes:
Non-shared
Shared by common carriers
Shared by dedicated carriers
Shared by hybrid carriers
The eNodeB cannot support two or more modes at the same time.
eRAN7.0
Huawei Confidential
Page 43
Sharing Operators
The CnOperator MO consists of the ID, name, type, mobile country code (MCC), and
mobile network code (MNC) of an operator. The MCC and MNC constitute a PLMN ID,
which uniquely identifies the operator.
A maximum of six operators can share the RAN.
Huawei Confidential
Page 44
Operator Sharing Group
This MO is available only in the LOFD-070206 Hybrid RAN Sharing feature.
The CnOperator MO includes the ID of the operator sharing group, the ID of the primary
operator, the operator index table, MCC, and MNC. The MCC and MNC constitute a PLMN
ID, which uniquely identifies the operator.
A maximum of six operators can share the RAN.
The CnOpSharingGroup MO needs to be associated with the MOs including the S1, X2,
S1 interface, and X2 interface.
eRAN7.0
Huawei Confidential
Page 45
Tracking Area
CnOperatorTa includes the following parameters:
TrackingAreaId
CnOperatorId
Tac
The CnOperatorTa MO consists of parameters related to a tracking area

identified by a TAC for an operator. The TAC is used by the EPC to determine
the area within which paging messages can be sent. One tracking can
include one or more cells. An eNodeB can be configured with a maximum of
108 CnOperatorTa MOs.
Huawei Confidential
Page 46
Active User Ratio
LicenseSharingPolicy includes the following parameters:
CnOperatorId
MaxUserNumRate
UserNumSharingRate
The LicenseSharingPolicy MO consists of the parameters related to a

license sharing policy among operators. The parameters in this MO are set to
determine the proportion of the license performance items and the right to
access the license function items allocated to each operator.
If operators do not need to control the proportion, this MO is not required.
Huawei Confidential
Page 47
Traffic Ratio
LicRatio:
UpLicRatio
TrafficSharingType
LicRatioSharePolicy:
CnOperatorId
TrfRatio
TrfSharingRatio
The LicRatioSharePolicy MO consists of the parameters related to a license sharing policy

among operators. The parameters in this MO are set to determine the proportion of the license
performance items.
The TrafficSharingType parameter in the LicRatio MO indicates the mode of traffic sharing
between operators in eRAN sharing scenarios and can be set to SHARING or DEDICATE.
Huawei Confidential
Page 48
RB Ratio
CellAlgoSwitch includes the following
parameters:
LocalCellId
LocalCellId
TrackingAreaId
RanShareModeSwitch
CellReservedForOp
OpUlRbUsedRatio
OpDlRbUsedRatio
BroadcastCnOperatorId
CellOP includes the following parameters:
The CellAlgoSwitch MO is used to
The CellOp MO is used to identify an

operator of a cell.
configure admission control, congestion

control, and scheduling policies based on
the operator.
Huawei Confidential
Page 49
Dedicated Priority Camping Strategies
Based on SPID
Based on the PLMN of neighboring frequencies

UTRANRANSHARE.CellReselPriority
GERANRANSHARE.CellReselPriority
EUTRANNFREQRANSHARE.CellReselPriority
Based on the PLMN of serving cells

GeranNFGroupSCellOp.CellReselDediPri
UtranNFreqSCellOp.CellReselDediPri
EutranNFreqSCellOp.CellReselDediPri
Cdma2000BcSCellOp.CellReselDediPri
Huawei Confidential
Page 50
Main Configurations in the Common Carrier Scenario

1.
Configure eNodeB sharing mode: MO ENodeBSharingMode
2.
Configure PLMN IDs supported in eNodeB: MO CNOPERATOR
3.
Configure TAI: MO CNOPERATORTA
4.
Configure PLMN IDs supported in cell: MO CellOP
5.
If support RB allocation operator aware: MO CELLALGOSWITCH.RanShareModeSwitch, CellOP
6.
If support PDCP throughput operator aware: MO LICRATIO.TrafficSharingType, LICRATIOSHAREPOLICY
7.
If support RRC connected user number operator aware: MO LICENSESHARINGPOLICY
8.
If support PLMN round: MO CELLACCESS
9.
If support ANR: MO ENODEBALGOSWITCH.RanSharingAnrSwitch
10. If support dedicated camping strategy, select one from the following three strategies:
RATFREQPRIORITYGROUP, SPIDCFG
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, Cdma2000BcSCellOp
UTRANRANSHARE, GERANRANSHARE, EUTRANINTERNFREQRANSHARE
Huawei Confidential
Page 51
Main Configurations in the Dedicated Carrier Scenario

1.
2.
3.
4.
5.
If support PDCP throughput operator aware: MO LICRATIO.TrafficSharingType,

LICRATIOSHAREPOLICY
6.
If support RRC connected user number operator aware: MO LICENSESHARINGPOLICY
Huawei Confidential
Page 52
Main Configurations in the Hybrid Carrier Scenario

1.
2.
Configure information about the operator sharing group: MO CnOpSharingGroup
3.
Configure link information: MO S1,S1Interface,MO X2,MO X2Interface
4.
Configure cell information: MO Cell
5.
6.
7.
8.
If support RB allocation operator aware: MO CELLALGOSWITCH.RanShareModeSwitch
9.
If support PDCP throughput operator aware: MO LICRATIO.TrafficSharingType,

LICRATIOSHAREPOLICY
10. If support RRC connected user number operator aware: MO LICENSESHARINGPOLICY

11. If support PLMN round: MO CELLACCESS
12. If support ANR: MO ENODEBALGOSWITCH.RanSharingAnrSwitch
13. If support dedicated camping strategy, select one from the following three strategies:
RATFREQPRIORITYGROUP, SPIDCFG
EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, Cdma2000BcSCellOp
UTRANRANSHARE, GERANRANSHARE, EUTRANINTERNFREQRANSHARE
eRAN7.0
Huawei Confidential
Page 53
Contents
Hybrid RAN Sharing
Resource Management
Planning
FAQs
Reference Documents

Huawei Confidential
Page 54
Ensure that meanings in the following table are clear.

You are advised to place interpretations in remarks.
Status detection: For details, see section "Activation Observation" in RAN Sharing
FPD (eRAN7.0).
In the common/hybrid carrier scenario, observe whether the PLMN ID is delivered in SIB1. If multi-operator
information is contained in SIB1 and is consistent with configured information, the feature is activated.
In independent cells of an operator with dedicated carriers, if the PLMN ID in SIB1 for each cell is consistent
with configured information, the feature is activated.
Alarms (Alarms in the following table can be used to distinguish operators.)
Signaling tracing: Signaling tracing in sharing mode is the same as that in independent mode.
Focus the tAI IE in the S1AP_INITIAL_UE_MSG message to observe whether the PLMN ID
carried by the UE is correct.
Huawei Confidential
Page 55
Counters: (Counters enclosed in the red box are added in eRAN7.0. For details, see eNodeB Performance Counter Reference.)
Inter-operation
indications between
TDD and FDD are
added.
Huawei Confidential
Page 56
Contents
Hybrid RAN Sharing
Resource Management
Planning
FAQs
Reference Documents

Huawei Confidential
Page 57
FAQs
None
Huawei Confidential
Page 58
Contents
Hybrid RAN Sharing
Resource Management
Planning
FAQs
Reference Documents

Huawei Confidential
Page 59
Reference Documents
1. RAN Sharing Feature Parameter Description

2. LTE RAN Sharing Solution Whitepaper
3. 3GPP TS 36.331 Radio Resource Control (RRC)
4. 3GPP TS 36.413 S1AP
5. 3GPP TS 36.423 X2AP
6. eNodeB Performance Counter Reference
7. eNodeB MO Reference
8. eRAN6.0/7.0 Reconfiguration Guide
Huawei Confidential
Page 60
Contents
Hybrid RAN Sharing
Resource Management
Planning
FAQs
Reference Documents

Huawei Confidential
Page 61

Acronym or Abbreviation
MOCN
GWCN
Full Expansion
multi-operator core
network
gateway core network
Huawei Confidential
Page 62
Thank You
Huawei Confidential
Page 63

SPD ERAN7.0 RAN Sharing Feature Introduction

Uploaded by

Document Information

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

SPD ERAN7.0 RAN Sharing Feature Introduction

Uploaded by

Copyright:

Available Formats

Security Level: INTERNAL

LTE RAN Sharing Solution

Architecture and Scenario

RAN Sharing with Common Carriers

RAN Sharing with Dedicated Carriers

Hybrid RAN Sharing

Installation and Commissioning

Acceptance and Maintenance

Acronyms and Abbreviations

HUAWEI TECHNOLOGIES CO., LTD.

Architecture and Scenario

RAN Sharing Solution (Dedicated/Common Carrier Policy)

Operator B's EPC

RAN sharing with dedicated carriers:

HUAWEI TECHNOLOGIES CO., LTD.

LOFD-001036 RAN Sharing with Common Carrier

Operator B's EPC

RAN sharing with common carriers:

Architecture and Scenario

RAN Sharing Solution (Hybrid Carrier Policy)

Operator A's EPC

Operator B's EPC

Operator D's EPC

Operator A's Operator D's

Operator A's Operator B's

Hybrid RAN sharing

HUAWEI TECHNOLOGIES CO., LTD.

Architecture and Scenario

Comparison of LTE RAN Sharing Modes

RAN Sharing with

RAN Sharing with Dedicated

Hybrid RAN Sharing

CMs are shared.

Cell-level CMs are independent and

When cells are shared, CMs are shared.

Cell-level resources are expanded

When cells are shared, resource are shared.

Shared (Some feature

Cell-level features are deployed

Cell sharing: Shared (Some feature

If the MME is shared, the

If the MME is shared, the MME needs to

If the MME is shared, the MME needs to

HUAWEI TECHNOLOGIES CO., LTD.

Architecture and Scenario

Definition of the Network Sharing Architecture in 3GPP

RAN Sharing with Common Carriers

Network Sharing Architecture with Common Carriers

HUAWEI TECHNOLOGIES CO., LTD.

RAN Sharing with Common Carriers

Network Selection Process

RAN Sharing with Common Carriers

RAN Sharing with Common Carriers

RAN Sharing with Common Carriers

EPLMNs in the handover restriction list (HRL)

HUAWEI TECHNOLOGIES CO., LTD.

RAN Sharing with Common Carriers

X2-based Incoming Handover

X2-based handover in MOCN

X2-based handover in GWCN

HUAWEI TECHNOLOGIES CO., LTD.

RAN Sharing with Common Carriers

S1-based Incoming Handover

S1-based handover in GWCN