RAN Sharing 4g

3/14/24, 2:31 PM HedEx Startpage
eRAN19.1 FDD Feature Documentation

Product Version: eRAN19.1
Library Version: 08
Date: 2023-11-30
For any question, please contact us.

Security Declaration
Copyright © Huawei Technologies Co., Ltd. 2023. All rights reserved.
RAN Sharing
Contents
4.13.2 RAN Sharing
eRAN
RAN Sharing Feature Parameter Des
cription
Issue 04
Date 2023-08-23
127.0.0.1:7890/printtopics.html?time=Thu Mar 14 2024 14:31:28 GMT+0200 (Eastern European Standard Time) 1/195
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2023. 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 Hua
wei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property 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: [email protected]
4.13.2 Contents
1 Change History
1.1 eRAN19.1 04 (2023-08-23)
1.2 eRAN19.1 03 (2023-06-29)
1.3 eRAN19.1 02 (2023-04-28)
1.4 eRAN19.1 01 (2023-03-09)
1.5 eRAN19.1 Draft A (2022-12-30)
2 About This Document
2.1 General Statements
2.2 Applicable RAT
2.3 Features in This Document
3 General Principles
3.1 Overview
3.2 Network Architecture
4 RAN Sharing with Common Carrier
4.1 Principles
4.1.1 Overview
4.1.2 NE Functions
4.1.3 Idle Mode Management
4.1.3.1 System Information Broadcast
4.1.3.2 EPC Selection
4.1.3.3 Fairness Guarantee for Roaming
4.1.3.4 Paging
4.1.3.5 Redirection
4.1.3.6 Cell Selection and Reselection
4.1.4 Mobility Management in Connected Mode
4.1.4.1 Configuration of Shared Neighboring Cells
4.1.4.2 Outgoing Handover
4.1.4.3 Incoming Handover
4.1.4.4 Operator-specific Selection of Mobility Policies
4.1.5 Feature and Capacity Management
4.1.5.1 Feature License
4.1.5.2 Capacity License
4.1.6 Air Interface Resource Management
4.1.6.1 Dynamic RB Resource Sharing
4.1.6.2 Admission Control
4.1.6.3 Congestion Control
4.1.6.4 Scheduling Policies
4.1.6.5 Mobility Load Balancing
4.1.6.6 Carrier Aggregation
4.1.7 ANR Management
4.1.8 OSS Management
4.1.8.1 Configuration Management
4.1.8.2 Fault Management
4.1.8.3 Performance Management
4.1.9 Transmission Networking
4.1.9.1 Transmission Port Planning
4.1.9.2 Transmission Link Setup
4.1.9.3 Dynamic Sharing of Uplink Transmission Bandwidth
4.1.9.4 VLAN Planning
4.1.10 Multi-operator PKI
4.2 Network Analysis
4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Others
4.4 Operation and Maintenance (FDD)
4.4.1 Data Configuration
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the MAE-Deployment
4.4.2 Activation Verification
4.4.3 Network Monitoring
5 RAN Sharing with Dedicated Carrier

5.1 Principles
5.1.1 Overview
5.1.2 NE Functions
5.2.1 Benefits
5.2.2 Impacts
5.3 Requirements
5.3.1 Licenses
5.3.2 Software
5.3.3 Hardware
5.3.4 Others
5.4 Operation and Maintenance
5.4.1 Data Configuration (FDD)
6 RAN Sharing with Special Dedicated Carrier (FDD)

6.1 Principles
6.1.1 Overview
6.1.2 NE Functions
6.1.3.4 Paging
6.1.3.5 Redirection
6.1.6 Fair Sharing of Air Interface Resources
6.2.1 Benefits
6.2.2 Impacts
6.3 Requirements
6.3.1 Licenses
6.3.2 Software
6.3.3 Hardware
6.3.4 Others
7 Hybrid RAN Sharing

7.1 Principles
7.1.1 Overview
7.1.2 NE Functions
7.1.3.4 Paging
7.1.3.5 Redirection
7.1.5.2 Capacity Control
7.2.1 Benefits
7.2.2 Impacts
7.3 Requirements
7.3.1 Licenses
7.3.2 Software
7.3.3 Hardware
7.3.4 Others
8 RAN Sharing by More Operators
8.1 Principles
8.2.1 Benefits
8.2.2 Impacts
8.3 Requirements
8.3.1 Licenses
8.3.2 Software
8.3.3 Hardware
8.3.4 Others
9 Fair User Sharing (FDD)

9.1 Principles
9.2.1 Benefits
9.2.2 Impacts
9.3 Requirements
9.3.1 Licenses
9.3.2 Software
9.3.3 Hardware
9.3.4 Others
10 MOCN Cell Reselection Priority Configuration

10.1 Principles
10.2.1 Benefits
10.2.2 Impacts
10.3 Requirements
10.3.1 Licenses
10.3.2 Software
10.3.3 Hardware
10.3.4 Others
11 Multi-Operator SPID Policy

11.1 Principles
11.2.1 Benefits
11.2.2 Impacts
11.3 Requirements
11.3.1 Licenses
11.3.2 Software
11.3.3 Hardware
11.3.4 Others
12 Network Smart Sharing

12.1 Principles
12.1.1 PLMN-based Algorithm Optimization
12.1.2 Operator-specific Frequency Priorities for Coverage-based Handovers
12.1.3 Operator-specific UE-level Handover Thresholds
12.1.4 Service Steering for UEs of Secondary Operators
12.1.5 Operator-Specific Measurement for Frequency-priority-based and Service-based Inter-frequency
Handovers
12.1.6 Operator-specific Measurement Events for Coverage-based Inter-frequency Handovers
12.1.7 PLMN-based Mobility Measurement Event Configuration
12.2.1 Benefits
12.2.2 Impacts
12.3 Requirements
12.3.1 Licenses
12.3.2 Software
12.3.3 Hardware
12.3.4 Others
13 Parameters
14 Counters
15 Glossary
1
16 Reference Documents
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 eRAN19.1 04 (2023-08-23)
This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.2 eRAN19.1 03 (2023-06-29)
Technical Changes
None
Editorial Changes
1.3 eRAN19.1 02 (2023-04-28)
Technical Changes
Change Description Parameter Change RAT Base Station Model
Added the impact relati None FDD 3900 and 5900 seri
onship between Uplink es base stations (m
Single-Side In-Band Int acro base stations)
erference Management
(FDD) and RAN sharing.
For details, see:
4.2.2 Impacts
5.2.2 Impacts
6.2.2 Impacts
7.2.2 Impacts
Editorial Changes
1.4 eRAN19.1 01 (2023-03-09)
Technical Changes
None
Editorial Changes
None
1.5 eRAN19.1 Draft A (2022-12-30)
This issue introduces the following changes to eRAN18.1 01 (2022-03-08).
Technical Changes
None
Editorial Changes
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
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 optimal gains, contact Huawei professional service engineers.
Functions mentioned in this document work properly only when enabled in the specified
applicable scenarios (such as RAT and networking). If a function not mentioned in this
document is enabled or a function is enabled in a scenario not specified as applicable,
exceptions or other impacts may occur.
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.
2.2 Applicable RAT
This document applies to FDD.
2.3 Features in This Document
This document describes the following FDD features.
Feature ID Feature Name Chapter/Section
LOFD-001036 RAN Sharing with Com 4 RAN Sharing with Common Carrier
mon Carrier
LOFD-001037 RAN Sharing with Dedic 5 RAN Sharing with Dedicated Carrier
ated Carrier
LOFD-070206 Hybrid RAN Sharing 7 Hybrid RAN Sharing
LOFD-001086 RAN Sharing by More O 8 RAN Sharing by More Operators
perators
LOFD-070213 Fair User Sharing 9 Fair User Sharing (FDD)
LOFD-001112 MOCN Flexible Priority B 10 MOCN Cell Reselection Priority Configuration

ased Camping
LOFD-070210 Multi Operators SPID Po 11 Multi-Operator SPID Policy

licy
3
LNOFD-161331 Network Smart Sharing 12 Network Smart Sharing
General Principles
3.1 Overview
When operators deploy their own networks, they have to pay expensive spectrum license fees and high
network deployment costs. They need to deploy sites within a short period to provide proper network
coverage. Huawei proposes RAN sharing to help operators tackle with these challenges.
RAN sharing is the sharing of network infrastructure or network equipment among multiple operators
or with third parties.
The infrastructure that can be shared includes sites, equipment rooms, towers, and power supplies.
Network equipment that can be shared includes base stations, transmission equipment, and core
network (CN) equipment.
The following is a sample list of RAN sharing modes:
Operators share the infrastructure of a site.
Mobile network operators (MNOs) share their RANs and CNs with mobile virtual network operators
(MVNOs).
Operators share network resources by allowing national or international roaming.
Operators jointly invest in the construction of a single wireless network.
Huawei eNodeBs support the following modes:
Independent operator mode
RAN sharing with common carrier
RAN sharing with dedicated carrier
Hybrid RAN sharing
According to section 6.2.2 "Message definitions" in 3GPP TS 36.331 V8.5.0, a single cell can broadcast a
maximum of six PLMN IDs. Huawei eNodeBs support RAN sharing among more than four operators.
However, the license control item for RAN sharing with common carrier, RAN sharing with dedicated
carrier, or hybrid RAN sharing allows up to four operators to share RAN resources. If RAN resources
need to be shared by more operators, the corresponding license must be purchased. For details, see 8
RAN Sharing by More Operators.
Independent Operator Mode
In independent operator mode, each operator has their own RAN. In this mode, RAN sharing can be
enabled by allowing national roaming among geographically separated networks. This is a broader
type of RAN sharing. To enable independent operator mode, set the
ENodeBSharingMode.ENodeBSharingMode parameter to INDEPENDENT.
Figure 3-1 shows an example of the independent operator mode. In this example, operators A and B
provide network coverage independently. Each operator allows their subscribers to use the RAN of the
other operator during national roaming.
Figure 3-1 RAN sharing between geographically separated networks by allowing national roaming
Assume that a UE subscribes to services of operator A. Independent operator mode is described as

follows:
In areas covered by operator A's network, which is the home public land mobile network (HPLMN)
of the UE, operator A serves this UE.
After the UE moves out of areas covered by operator A's network into those covered by operator
B's network, operator B serves this UE through national roaming.
In areas where the two networks overlap, the UE can be preferentially handed over back to
operator A's network based on the subscriber profile ID (SPID) policy.
For details about preferential handovers back to HPLMNs based on SPID policies, see Flexible User
Steering.
3.2 Network Architecture
RAN Sharing Architectures
Section 4.1 "Overview" in 3GPP TS 23.251 V8.4.0 defines two RAN sharing architectures for the E-
UTRAN:
Multi-operator core network (MOCN): Multiple operators share the RAN, but not the evolved
packet core (EPC), as shown in Figure 3-2.
Gateway core network (GWCN): Multiple operators share both the RAN and the mobility
management entity (MME), as shown in Figure 3-3. In this architecture, the MME must support
sharing among operators and can deliver the Handover Restriction List to eNodeBs.
Figure 3-2 Architecture of MOCN
Figure 3-3 Architecture of GWCN
Table 3-1 Network elements (NEs)
NE Description
EPC An EPC includes MMEs and serving gateways (S-GWs). Different ope
rators either have their own EPCs (MOCN) or share the same EPC (G
WCN).
Shared eNodeB An FDD eNodeB can be shared by multiple operators if RAN sharing
with common carrier, RAN sharing with dedicated carrier, RAN sharin
g with special dedicated carrier, or hybrid RAN sharing is enabled.
Shared OSS The operations support system (OSS) is an NE management system.

The functions of the OSS include configuration management, fault
management, and performance management. A team is responsible
for operating and maintaining this system, which manages all the sh
ared and non-shared eNodeBs.
NMS The shared OSS connects to the network management systems (NM
Ss) of multiple operators over northbound interfaces.
Table 3-2 Interfaces
Interface Description
S1 Connects the eNodeB and EPC. S1 is divided into S1-C (control-plan

e interface between the eNodeB and MME) and S1-U (user-plane int
erface between the eNodeB and S-GW).
X2 Connects eNodeBs. X2 consists of the control plane and user plane.
OM Connects the eNodeB and OSS. All operators share the OM interface
between each eNodeB and the OSS.
Itf-N Connects the OSS and the NMS of an operator. Each operator has th
eir own Itf-N interface.
S11 Connects the MME and S-GW.
Comparison Between MOCN and GWCN
Huawei eNodeBs support both the MOCN and GWCN architectures. The similarities and differences
between the two architectures are as follows:
Similarities
For FDD, both architectures support RAN sharing with common carrier, RAN sharing with
dedicated carrier, RAN sharing with special dedicated carrier, and hybrid RAN sharing. For NB-
IoT, both architectures support RAN sharing with common carrier, RAN sharing with dedicated
carrier, and hybrid RAN sharing.
Both require support from the eNodeB and the OSS.
Differences
MOCN does not support EPC sharing. Each operator has their own EPC.
GWCN supports MME sharing in the EPC, and requires support from the MME.
Huawei devices support MME separation and sharing in the MOCN and GWCN architectures,
which are defined in section 4.1 "Overview" in 3GPP TS 23.251. Huawei devices also support S-
GW separation and sharing. These functions are inherently supported by 3GPP specifications,
although not being explicitly defined.
Huawei E-UTRAN, including the multi-cell/multicast coordination entity (MCE) and eNodeB,
supports LTE unicast services and evolved multimedia broadcast/multicast services (eMBMSs).
The MCE and eNodeB can be shared among operators as a whole to provide eMBMSs in both
the MOCN and GWCN architectures. Operators can deploy their own eMBMSs in both
architectures. This document describes only LTE unicast services. For details about RAN sharing
for eMBMSs, see eMBMS.
4 RAN Sharing with Common Carrier
4.1 Principles
4.1.1 Overview
In RAN sharing with common carrier, multiple operators share spectrum resources and eNodeB
hardware resources. These operators share a same cell. In a shared cell, multiple PLMN IDs are
broadcast, including the primary operator's PLMN ID and secondary operators' PLMN IDs. To enable
RAN sharing with common carrier, set the ENodeBSharingMode.ENodeBSharingMode parameter to
SHARED_FREQ.
RAN sharing with common carrier is used when:
One operator owns spectrum resources and shares them with others.
Multiple operators own spectrum resources and use their resources to form a resource pool. They
share the pooled resources among themselves or with others who do not own spectrum resources.
Figure 4-1 shows the network architecture for RAN sharing with common carrier.
Figure 4-1 Network architecture for RAN sharing with common carrier
RAN sharing with common carrier differs from the independent operator mode in the following
aspects:
NE functions
Idle mode management
Mobility management in connected mode
Feature and capacity management
Fair sharing of air interface resources
Automatic neighbor relation (ANR) management
OSS management
Transmission networking
Multi-operator PKI
4.1.2 NE Functions
This section describes the NE functions and configurations specific to RAN sharing with common
carrier.
UE
To support RAN sharing with common carrier, UEs must be able to decode system information
broadcast in a shared cell and obtain information about the EPC operators supported by the shared
RAN.
In RAN sharing with common carrier, a UE first selects one PLMN (from the PLMNs listed in SIB1) as the
serving PLMN, and reports the PLMN to the eNodeB. The eNodeB then selects an EPC operator based
on the reported information. For details, see 4.1.3.2 EPC Selection.
eNodeB
In RAN sharing with common carrier, Huawei eNodeBs must support the following functions:
Setup of an S1 interface with an MME shared by operators or exclusively used by a specific

operator
Sharing by a maximum of four operators and broadcast of a maximum of four PLMN IDs in a
shared cell under the control of the RAN Sharing with Common Carrier license
MME selection for a UE based on the PLMN ID selected by the UE
Configuration of all PLMNs of a shared intra- and inter-RAT neighboring cell
Mobility management on a per operator basis
Reporting of certain counters and alarms on a per operator basis
MME
In RAN sharing with common carrier, the core networks of multiple operators use the same global
eNodeB ID (primary PLMN ID + eNodeB ID) and ECGI for addressing of shared eNodeBs and cells. The
eNodeB uses the global eNodeB ID and ECGI to communicate with the core networks of multiple
operators over the S1 interface. For details about the global eNodeB IDs and ECGIs, see 4.1.3.1 System
Information Broadcast.
If the GWCN architecture is used, the MME must:
Support multiple operators and be configured with information about all the operators.
Support the delivery of the Handover Restriction List IE. This IE is used to inform the target eNodeB
of UE's serving PLMN during an S1- or X2-based handover. If the MME does not deliver this IE, the
S1- or X2-based handover will fail. For details, see 4.1.4.3 Incoming Handover.
Idle mode management for RAN sharing with common carrier is different from that for the
independent operator mode. This section only describes the differences. For details about idle mode
management, see Idle Mode Management.
Related Concepts
PLMN ID
A PLMN ID consists of a mobile network code (MNC) and a mobile country code (MCC). In RAN
sharing with common carrier, multiple PLMN IDs can be broadcast in a shared cell.
Primary and secondary operators

The type of an operator is specified by the CnOperator.CnOperatorType parameter. According to
section 6.2.2 "Message definitions" in 3GPP TS 36.331 V8.5.0, the PLMN at the top of the broadcast
PLMN ID list is the primary PLMN. The ID of this PLMN is contained in the global eNodeB ID and
ECGI. The primary and secondary operators can share eNodeB resources based on predefined
proportions. The primary operator does not have any privileges.
System Information
As defined in section 6.2.2 "Message definitions" in 3GPP TS 36.331 V8.5.0, the contents of system
information block 1 (SIB1) are as follows:
Cell Reservation and Barring Status
Cell status information is sent to UEs through SIB1 and includes the following:
Cell barring status CellBarred (When a cell belongs to multiple PLMNs, this status is applied to all
of them.)
Cell reservation status CellReservedForOp (This status is individually applied to each PLMN.)
The CellAccess.CellBarred parameter specifies whether a cell is barred. The CellOp.CellReservedForOp

parameter specifies whether a cell is reserved for an operator.
Upon S1 setup failures or S1 faults, the cell reservation and barring status are adaptively changed in
SIB1.
If an S1 link for the primary operator fails to be set up or becomes faulty, the cell is in the
reservation status for the primary operator.
If an S1 link for a secondary operator fails to be set up or becomes faulty, the PLMN ID of this
operator is not included in the broadcast PLMN ID list.
If all S1 links fail to be set up or become faulty, the cell is barred and the eNodeB broadcasts the
barring status in SIB1. If the cell is deactivated before the SIB1 broadcast, the eNodeB does not
broadcast the barring status.
Assume that operator A is the primary operator and operator B is a secondary operator. The following
describes SIB1 in different scenarios:
Figure 4-2 shows SIB1 when S1 links for operators A and B are normal.
Figure 4-2 SIB1 (1)
Figure 4-3 shows SIB1 when the S1 link for operator A is faulty.
Figure 4-3 SIB1 (2)
Figure 4-4 shows SIB1 when the S1 link for operator B is faulty.
Figure 4-4 SIB1 (3)
When the S1 links for both operators A and B are faulty, the cell is unavailable.
TAC
The CnOperatorTa.Tac parameter specifies the TAC of an EPC operator. The CellOp.TrackingAreaId
parameter specifies the TAI of the cell. Because a cell belongs to only one TA, all operators of a cell
must be configured with the same TAC. That is, the values of all CnOperatorTa.Tac parameters
corresponding to the CellOp.TrackingAreaId parameters must be identical in a cell.
To change the TAC for a cell in which RAN sharing with common carrier is enabled, perform the
following steps: Delete the setting for CellOp.TrackingAreaId, set a new TAC for the
CnOperatorTa.TrackingAreaId parameter, and set the CellOp.TrackingAreaId parameter for the cell.
After a UE is powered on in a cell enabled with RAN sharing with common carrier, it learns of multiple
PLMNs after listening to the PLMN list in SIB1 broadcast by this cell. Based on the configuration
information in the USIM and recorded historical information, the UE selects one of them as its serving
PLMN according to the selection rules specified in section 4.4 "PLMN selection process" in 3GPP TS
23.122 V8.5.0.
After the UE selects an PLMN, it notifies the eNodeB of the selected PLMN through the RRC
Connection Setup Complete message.
The eNodeB then selects the S1 interface based on the PLMN ID selected by the UE and connects the
EPC.
Initial network access is different for UEs that are in their own home PLMNs (HPLMNs) and those
roaming to other PLMNs. In all of these scenarios, one or more PLMN IDs are broadcast in the shared
cell.
Scenario 1: Not Roaming
The UE selects its HPLMN and notifies the eNodeB through the RRC Connection Setup Complete
message. The eNodeB then selects the EPC based on this notification.
Scenario 2: Roaming Agreement with Only One Operator
The UE selects an EPC according to the selection rules specified in section 4.4 "PLMN selection process"
in 3GPP TS 23.122 V8.5.0.
If... Then...
The UE selects the EPC of an operator with w The eNodeB selects the corresponding EPC, a
hich a roaming agreement is signed nd the EPC allows the UE to attach.
The UE selects the EPC of an operator with w The EPC rejects the UE. The UE tries other EP
hich a roaming agreement is not signed Cs until it attaches to the EPC of an operator
with which a roaming agreement is signed.
Scenario 3: Roaming Agreements with All RAN Sharing Operators
in 3GPP TS 23.122 V8.5.0. The eNodeB selects the corresponding EPC, and the EPC allows the UE to
attach.
Scenario 4: No Roaming Agreement with Operators
in 3GPP TS 23.122 V8.5.0. The eNodeB then selects the corresponding EPC, and the EPC rejects the UE.
The UE tries other EPCs until it is rejected by all EPCs in the PLMNs indicated in the PLMN ID list.
According to section 4.4 "PLMN selection process" in 3GPP TS 23.122 V8.5.0, a roaming UE randomly
selects a PLMN ID if there is not a prominent PLMN (for example, in terms of signal quality). Some UEs
of a third-party operator are more likely to select the PLMN ID at the top of the PLMN list when they
roam to a cell in which RAN sharing with common carrier is enabled.
It is recommended that operators consider fairness among different regions or time periods when they
plan the sequence of broadcast PLMN IDs. For example, operators A and B divide a shared area into
eastern and western regions based on user balancing. In the eastern region, the PLMN ID of operator A
is ranked first; in the western region, the PLMN ID of operator B is ranked first.
To achieve fairness among operators sharing a cell, you can set the CellAccess.BroadcastMode
parameter to specify a PLMN ID broadcast mode in the cell. Assume that operators A, B, and C share a
cell.
When this parameter is set to NORMAL_MODE, PLMN IDs are broadcast at a fixed sequence in the
cell.
The PLMN IDs in the list are always broadcast in the following sequence:
Operator A
Operator B
Operator C
When this parameter is set to RR_MODE, the PLMN ID at the top of the PLMN ID list is rotated in
RR mode at a cell-specific interval. This interval is specified by the CellAccess.RoundPeriod
parameter. The start time for broadcast sequence rotation is specified by the
CellAccess.RoundActionTime parameter.
For example, when the CellAccess.RoundPeriod parameter is set to 12, the PLMN IDs in the list are
broadcast in the sequence as shown in Figure 4-5.
Figure 4-5 PLMN ID rotation in RR mode at a cell-specific interval
When this parameter is set to FREE_Mode, the PLMN ID at the top of the PLMN ID list is rotated at
an operator-specific interval. This interval is specified by the CellOp.OperatorPlmnRoundPeriod
parameter and the start time is specified by the CellAccess.RoundActionTime parameter.

For example, when the CellOp.OperatorPlmnRoundPeriod parameters are set to 12, 11, and 1 for
operators A, B, and C, respectively, the PLMN IDs in the list are broadcast in the sequence as shown
in Figure 4-6.
Figure 4-6 PLMN ID rotation at an operator-specific interval
According to section 6.2.2 "Message definitions" in 3GPP TS 36.331 V8.5.0, the primary PLMN is
the one at the top of the broadcast PLMN ID list in SIB1 and also the PLMN in the ECGI. When
RAN sharing with common carrier is enabled and the CellAccess.BroadcastMode parameter is set
to RR_MODE or FREE_Mode, the PLMN at the top of the broadcast PLMN ID list in SIB1
regularly changes while the primary PLMN in the ECGI does not.
4.1.3.4 Paging
The EPC pages a UE in the following ways:
The EPC uses the international mobile subscriber identity (IMSI) of the UE for paging. Each UE has a
unique IMSI.
The EPC uses the SAE-temporary mobile subscriber identity (S-TMSI) of the UE. The S-TMSI is used
to reduce the transmissions of IMSI and improve the efficiency of paging, service requests, and
other radio signaling procedures. An S-TMSI consists of a mobility management entity code
(MMEC) and an MME temporary mobile subscriber identity (M-TMSI). An MMEC identifies an MME.
An M-TMSI is randomly allocated to a UE within an MME.
To ensure that S-TMSIs are unique in cells where RAN sharing with common carrier is enabled and
prevent paging conflicts, it is recommended that the MMEC of each MME (including MMEs of the
same and different operators) be unique in a TA. The MMECs of different operators must be
negotiated to ensure uniqueness.
If RAN sharing operators can tolerate paging errors caused by MMEC conflicts, you can set the
GlobalProcSwitch.DiffOpWithSameMmecSwitch parameter to ON so that the eNodeBs allow MMEs of
these operators to have the same MMEC.
4.1.3.5 Redirection
A redirection may be performed when the system is overloaded, an S1 interface is faulty, or a handover
fails. During the redirection, the RRC Connection Release message carries operator-specific frequencies
or frequency groups, which helps the UE promptly re-access the operator's network.
When a UE switches from the connected mode to the idle mode or after it selects a PLMN, the UE must
select an appropriate cell to camp on.
After camping on a cell, the UE listens to system information. It measures the serving and neighboring
cells according to the neighboring cell measurement and cell reselection rules to select a more
appropriate cell to camp on.
Before cell reselection, the UE is required to measure the signal quality of certain neighboring cells and
evaluate them by using the cell reselection criteria based on the cell priority. During measurement and
cell reselection, the UE needs to obtain the priorities of neighboring frequencies.
There are both intra- and inter-RAT frequency priorities for cell reselection, and there are two different
types of each:
Common priority: The common priority is delivered in a cell broadcast message to all UEs in the
cell. It is not operator-specific. For details, see Idle Mode Management.
Dedicated priority: The dedicated priority is generated by an internal algorithm during an RRC
connection release. It is delivered to a specific UE in the IdleModeMobilityControlInfo IE in the RRC
Connection Release message.
In RAN sharing with common carrier, a shared eNodeB assigns dedicated cell reselection priorities to
UEs of different operators so that operators can use different camping strategies for UEs in idle mode.
The dedicated cell-reselection priority can be configured based on the following:
SPID
Different operators can be configured with different dedicated cell reselection priorities based on
the SPID. The value range of the SPID is 1–256. Operators are allocated different SPIDs. The
RatFreqPriorityGroup.RatFreqPriorityGroupId parameter specifies the ID of a group of parameters
related to the dedicated cell reselection priorities for each operator. The SpidCfg.Spid and
SpidCfg.RatFreqPriorityGroupId parameters associate operators' SPIDs with their dedicated cell-
reselection priorities. For details, see Flexible User Steering.
To use SPID-specific dedicated cell-reselection priorities in FDD, you must purchase the
license for LOFD-00105401 Camp & Handover Based on SPID.
Dedicated cell-reselection priorities can now be configured based on negotiation-free

SPIDs. For details, see 11 Multi-Operator SPID Policy.
Serving cell's PLMN

The NrNFreqSCellOp, EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs specify the dedicated cell-reselection priority of an intra-RAT
neighboring frequency or an inter-RAT neighboring frequency or frequency band for the PLMN of
the serving cell.
Before sending information about the dedicated cell-reselection priority to a UE, the eNodeB filters
the frequencies/frequency bands for the dedicated cell-reselection priority configuration by
comparing them with the UE's serving PLMN. If the CnOperator.CnOperatorID parameter
corresponding to the serving PLMN of the UE is the same as the CnOperator.CnOperatorID
parameter corresponding to a neighboring frequency or frequency band, the information about
the neighboring frequency or frequency band must be included in the delivered dedicated cell
reselection priority. Otherwise, the information about the neighboring frequency or frequency
band is not delivered.
The EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and

Cdma2000BcSCellOp MOs are configured to specify the dedicated cell-reselection priority
of an intra-RAT neighboring frequency or an inter-RAT neighboring frequency or frequency
band for the PLMN of the serving cell. In addition, the following is required:
For FDD, the license for LOFD-001112 MOCN Flexible Priority Based Camping is required.
For details, see 10 MOCN Cell Reselection Priority Configuration.
Neighboring frequency's PLMN

A neighboring frequency's PLMN is broadcast in the broadcast messages of the cell working on the
neighboring frequency. Therefore, this method can be used to set dedicated cell reselection
priorities only for the PLMN broadcast by the cell working on the neighboring frequency.
The UtranRanShare, GeranRanShare, and EutranNFreqRanShare MOs specify the dedicated cell
reselection priorities specific to each PLMN that shares a neighboring UTRAN frequency, GERAN
frequency group, or neighboring E-UTRAN frequency, respectively.
If the CellOpHoCfg.ServingFreqReselPriority parameter is set to 255, the eNodeB delivers the cell
reselection priority specified by the CellResel.CellReselPriority parameter to the UE as its serving
frequency's cell reselection priority. If the CellOpHoCfg.ServingFreqReselPriority parameter is not set
to 255, the eNodeB delivers the cell reselection priority specified by this parameter to the UE as its
serving frequency's cell reselection priority.
This method is less flexible than dedicated priority of cell reselection based on the PLMN of the
serving cell. In this method, the eNodeB delivers the dedicated cell reselection priorities on all
frequencies broadcast in system information. This method requires that all non-serving frequencies
be configured in the EutranNFreqRanShare MO. If delivering the priority on a frequency is not

required, set EutranNFreqRanShare.CellReselPriorityCfgInd of this frequency to NOT_CFG.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is deselected,
the eNodeB filters neighboring frequencies for dedicated cell-reselection priority configuration by
comparing their PLMNs with the UE's serving PLMN. If a neighboring frequency's PLMN is the
same as the UE's serving PLMN, the eNodeB sends the priority of the neighboring frequency to the
UE as the dedicated cell-reselection priority. If no neighboring frequency's PLMN is the same as the
UE's serving PLMN, the eNodeB does not send a dedicated cell-reselection priority to the UE.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected,
the eNodeB filters neighboring frequencies for dedicated cell-reselection priority configuration by
comparing their PLMNs with the PLMNs that allow incoming handovers from UE's serving PLMN. If
a neighboring frequency's PLMN is the same as a PLMN that allows incoming handovers from UE's
serving PLMN, the eNodeB sends the priority of this neighboring frequency to the UE as the
dedicated cell-reselection priority. If no neighboring frequency's PLMN is the same as a PLMN that
allows incoming handovers from UE's serving PLMN, the eNodeB does not send a dedicated cell-
reselection priority to the UE.
In addition, the INTRA_RAT_INTER_PLMN_HO_SW, UTRAN_INTER_PLMN_HO_SW,
GERAN_INTER_PLMN_HO_SW, and NR_INTER_PLMN_HO_SW options of the
CnOperator.OperatorFunSwitch parameter can be used to specify whether the eNodeB filters RAT-
specific neighboring frequencies for dedicated cell-reselection priority configuration by comparing
their PLMNs with the PLMNs to which a handover is allowed.
If a RAT-specific option is selected, the source eNodeB filters neighboring frequencies of this
RAT for dedicated cell-reselection priority configuration by comparing their PLMNs with the
PLMNs to which a handover is allowed.
If a RAT-specific option is deselected, the source eNodeB filters neighboring frequencies of this
RAT for dedicated cell-reselection priority configuration by comparing their PLMNs with the
UE's serving PLMN.
The following lists the PLMNs that allow incoming handovers from UE's serving PLMN. The eNodeB
selects these types of PLMNs in descending order. If several PLMNs are of the same type, the PLMN
at the top is selected.
UE's serving PLMN
Equivalent PLMNs (EPLMNs) sent from the MME

During initial access, the eNodeB obtains the EPLMN from the INITIAL CONTEXT SETUP
REQUEST or DOWNLINK NAS TRANSPORT message delivered by the MME. During an S1-
based handover, the target eNodeB obtains the EPLMN information from the MME. During an
X2-based handover, the target eNodeB obtains the EPLMN information from the source
eNodeB.
Note that the EPlmnSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter must be
selected if UEs need to be handed over to neighboring cells under the EPLMNs sent by the
MME or source eNodeB.
PLMNs that allow incoming handovers from the UE's serving PLMN according to the
configuration on the eNodeB
The InterPlmnHoList.CnOperatorId parameter specifies the serving PLMN of the source
eNodeB. The InterPlmnHoList.TarMcc and InterPlmnHoList.TarMnc parameters specify a list of
PLMNs that allow incoming handovers from UE's serving PLMN.
Both the EPLMNs sent from the MME (if the EPlmnSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected) and the configured PLMNs that allow
incoming handovers from UE's serving PLMN can be candidates for inter-PLMN handovers.
The relationships between the three types of dedicated cell reselection priorities are as follows:
If a UE is configured with an SPID, the eNodeB sends the dedicated cell-reselection priority to the
UE based on the SPID.
If the UE is not configured with an SPID, the eNodeB sends the dedicated cell-reselection priority to
the UE based on the serving cell's PLMN or neighboring frequency's PLMN. These two types of
dedicated cell reselection priorities cannot be used simultaneously. That is, the MOs related to one
type cannot be configured if the MOs related to the other have been configured. Dedicated cell-
reselection based on serving cell's PLMN is recommended.
Frequencies configured with dedicated cell-reselection priorities must be configured in SIBs.

Otherwise, the dedicated priorities do not take effect.
For details about cell selection and reselection in non-RAN sharing scenarios, see Idle Mode
Management.
Mobility management in connected mode enables the eNodeB to select a target cell for a UE during an
intra-frequency, inter-frequency, or inter-RAT handover. For details about handover procedures, see
Mobility Management in Connected Mode.
When RAN sharing with common carrier is enabled:
If a cell served by the eNodeB has a neighboring cell in which RAN sharing with common carrier is
enabled, the list of all serving PLMN IDs of this neighboring cell must be configured for the source
eNodeB to determine the target cell for a handover. For details, see 4.1.4.1 Configuration of Shared
Neighboring Cells.
The source eNodeB selects the target cell for a handover based on the UE's serving PLMN.
When the inter-PLMN handover function is disabled, the source eNodeB can only select a
neighboring cell, whose PLMNs include the UE's serving PLMN, as the target cell.
When the inter-PLMN handover function is enabled, the source eNodeB can select a
neighboring cell, whose PLMNs include the UE's serving PLMN or a PLMN that allows
incoming handovers from UE's serving PLMN, as the target cell. For details, see 4.1.4.2 Outgoing
Handover.
During a UE is handed over, the target eNodeB must correctly identify the serving PLMN of the
target cell. Otherwise, an S1- or X2-based handover may fail. For details, see 4.1.4.3 Incoming
Handover.
4.1.4.1 Configuration of Shared Neighboring Cells
Intra-RAT Neighboring Cells
If a cell served by an eNodeB has an intra-RAT neighboring cell in which RAN sharing with common
carrier is enabled, the eNodeB must be configured with the PLMN ID list of this neighboring cell using
the EutranExternalCellPlmn.ShareMcc and EutranExternalCellPlmn.ShareMnc parameters. This list is
used by the eNodeB to determine the target cells for outgoing handovers.
Inter-RAT Neighboring Cells
Configuration of shared inter-RAT neighboring cells is similar to that of shared intra-RAT neighboring
cells.
If a cell served by an eNodeB has an inter-RAT neighboring cell in which RAN sharing with common
carrier is enabled, the eNodeB must be configured with any of the following:
A list of serving PLMNs of the neighboring NG-RAN cell, configured by using the
NrExternalCellPlmn.SharedMcc and NrExternalCellPlmn.SharedMnc parameters
A list of serving PLMNs of the neighboring UTRAN cell, configured by using the
UtranExternalCellPlmn.ShareMcc and UtranExternalCellPlmn.ShareMnc parameters
A list of serving PLMNs of the neighboring GERAN cell, configured by using the
GeranExternalCellPlmn.ShareMcc and GeranExternalCellPlmn.ShareMnc parameters
When both E-UTRAN and GERAN cells use RAN sharing with common carrier, perform operations
according to the protocol release that the GERAN cell complies with:
If a GERAN cell complies with 3GPP Release 10 or earlier (a non-standard scenario), select the
L2GPLMNChooseOptSwitch option of the GlobalProcSwitch.ProtocolMsgOptSwitch parameter.
For details about RAN sharing with common carrier in such a cell, see section 4.2.2 "Broadcast
system information for network sharing" in 3GPP TS 23.251 v10.1.0.
In this scenario, only the primary PLMN ID is broadcast in the GERAN cell. The target PLMN ID
carried in messages sent from an E-UTRAN cell to the GERAN cell, such as handover requests
or RIM requests, must be consistent with the primary PLMN ID configured for the GERAN cell.
If the PLMN IDs are inconsistent, the requests will fail.
If a GERAN cell complies with 3GPP Release 11 or later, deselect the

L2GPLMNChooseOptSwitch option of the GlobalProcSwitch.ProtocolMsgOptSwitch parameter.
For details about RAN sharing with common carrier in such a cell, see section 4.2.2 "Broadcast
system information for network sharing" in 3GPP TS 23.251 v11.1.0.
In this scenario, multiple PLMN IDs can be broadcast in the GERAN cell. The target PLMN ID
carried in messages sent from an E-UTRAN cell to the GERAN cell is the ID of the UE's serving
PLMN, which is not necessarily consistent with the primary PLMN ID configured for the GERAN
cell.
CDMA2000 does not support RAN sharing with common carrier. The PLMN information of
neighboring CDMA2000 1xRTT cells and neighboring CDMA2000 HRPD cells is indicated by the
MCC and MNC parameter combinations in the Cdma20001XrttExternalCell and
Cdma2000HrpdExternalCell MOs, respectively.
4.1.4.2 Outgoing Handover
If a handover is triggered on the eNodeB where RAN sharing with common carrier is enabled, the
source eNodeB selects a neighboring cell of a PLMN that allows incoming handovers from UE's serving
PLMN as the target cell. If the target cell is also enabled with RAN sharing with common carrier, the
source eNodeB also selects the serving PLMN for the UE after the UE is handed over to the target cell.
The selected serving PLMN may or may not be the same as the serving PLMN of the UE in the source
eNodeB. If the UE's serving PLMN in the source eNodeB is supported by the target cell, it is
preferentially selected over all other supported PLMNs.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is deselected,

the UE's serving PLMN must remain the same after an inter-eNodeB handover. Therefore, the
source eNodeB must select a neighboring cell that supports the UE's serving PLMN as the target
cell for a handover.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected,

the source eNodeB can select a neighboring cell of a PLMN that allows incoming handovers from
UE's serving PLMN as the target cell. The selected PLMN must be the serving PLMN in the target
cell. The PLMNs that allow incoming handovers from UE's serving PLMN are the same as those
described in the content related to dedicated cell-reselection priority based on neighboring
frequency's PLMN in 4.1.3.6 Cell Selection and Reselection.
In addition, the INTRA_RAT_INTER_PLMN_HO_SW, UTRAN_INTER_PLMN_HO_SW,
GERAN_INTER_PLMN_HO_SW, and NR_INTER_PLMN_HO_SW options of the
CnOperator.OperatorFunSwitch parameter specify whether RAT-specific inter-PLMN handovers are
allowed.
If a RAT-specific option is selected, the source eNodeB can select a neighboring cell of this RAT
that belongs to any PLMN to which the UE is allowed to be handed over as the target cell.
If a RAT-specific option is deselected, the source eNodeB can select only a neighboring cell of
this RAT that belongs to the UE's serving PLMN as the target cell.
To use the inter-PLMN handover function, you must purchase the licenses for the following
features:
For FDD:
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN
4.1.4.3 Incoming Handover
In RAN sharing with common carrier, the source eNodeB selects the target cell for a handover and the
serving PLMN of the UE in the target cell based on UE's serving PLMN. The target eNodeB must
correctly identify the serving PLMN to be used after an S1- or X2-based handover. Otherwise, the
handover may fail.
According to section 9.1.5.4 "HANDOVER REQUEST" in 3GPP TS 36.413 V8.0.0 and section 9.1.1.1
"HANDOVER REQUEST" in 3GPP TS 36.423 V8.0.0, the source eNodeB can indicate the UE's serving
PLMN to be used after a handover to the target eNodeB only through the serving PLMN in the
optional IE Handover Restriction List in the S1/X2 handover request message. This requires the MME to
indicate the IE Handover Restriction List to the eNodeB through the INITIAL CONTEXT SETUP REQUEST
or DOWNLINK NAS TRANSPORT message on the S1 interface. During an S1- or X2-based handover, the
MME or source eNodeB includes the IE Handover Restriction List in the handover request message sent
to the target eNodeB.
If the target eNodeB does not receive the IE Handover Restriction List, it can identify the UE's serving
PLMN to be used after a handover as follows in some cases:
During an S1- or X2-based handover, if the MME or source eNodeB includes the IE Handover
Restriction List in the handover request message to the target eNodeB, the target eNodeB selects
the serving PLMN indicated in the IE as the serving PLMN of the UE to be used after the handover.
During an S1- or X2-based handover, if the MME or source eNodeB does not include the IE
Handover Restriction List in the handover request message to the target eNodeB, the rules vary
depending on the network architecture:
MOCN (where MMEs are dedicated to individual operators): For an S1-based handover, the
target eNodeB can select the PLMN supported by the independent operator's MME that sends
the handover request message as the UE's serving PLMN to be used after the handover. For an
X2-based handover, the target eNodeB can select the PLMN identified by the PLMN ID in the
IE GUMMEI in the handover request message as UE's serving PLMN to be used after the
handover. (GUMMEI is short for globally unique MME identifier.)
GWCN (where MMEs are shared by operators): If RAN sharing with common carrier is not
enabled in the target cell, the only PLMN supported by the cell is used as the UE's serving
PLMN after the handover. If RAN sharing with common carrier is enabled in the target cell, the
MME must, in compliance with 3GPP specifications, deliver the IE Handover Restriction List to
the eNodeB. Otherwise, an S1- or X2-based handover may fail. If the MME does not send the
IE Handover Restriction List to the eNodeB:
If the GwcnIncomingHoWithoutHrlSwitch option of the

GlobalProcSwitch.HoProcCtrlSwitch parameter is deselected, the eNodeB rejects the
incoming handover.
If the GwcnIncomingHoWithoutHrlSwitch option of the

GlobalProcSwitch.HoProcCtrlSwitch parameter is selected, the eNodeB allows the incoming
handover. The target PLMN of the handover is the PLMN in the GUMMEI IE in the
handover request message. It is recommended that this option be selected when the MME
does not support the delivery of the IE Handover Restriction List.
4.1.4.4 Operator-specific Selection of Mobility Policies
The following functions are supported during intra-RAT mobility policy selection for the E-UTRAN:
Frequency priorities for connected mode can be configured based on PLMN IDs of different
operators so that the eNodeB can deliver frequency measurement configurations for operator-level
handovers. For details, see Mobility Management in Connected Mode.
Measurement and handover threshold offsets for services with different QCIs can be configured
based on the PLMN IDs of different operators. In this way, different A2 measurement thresholds
can be set for different operators. For details, see Mobility Management in Connected Mode.
Mobility measurement events can be configured based on the PLMN IDs of different operators. In
this way, different triggering quantities for events A1 and A2 (including thresholds 1 and 2 for
event A5) can be set for different operators. If the CnoperatorHoCfg.InterFreqHoA1A2TrigQuan
parameter is set to a value other than NONE, the value of this parameter is used as the triggering
quantity for events A1 and A2 (including thresholds 1 and 2 for event A5) of the operator. For
details, see Mobility Management in Connected Mode.
The following functions are supported during inter-RAT mobility policy selection for the UTRAN:
The eNodeB can be configured with peer UTRAN capabilities, including PS handover, RIM, VoLTE,
ultra-flash CSFB, and SRVCC capabilities, based on the peer PLMN ID and RNC ID, to implement
operator-specific policies. For details, see Mobility Management in Connected Mode.
Different measurement and handover threshold offsets for services with different QCIs can be
configured based on the PLMN IDs of different operators. In this way, different inter-RAT
measurement and handover thresholds can be set for different operators. For details, see Mobility
Management in Connected Mode.
The following function is supported during inter-RAT mobility policy selection for the GERAN:
The eNodeB can be configured with peer GERAN capabilities, including RIM, ultra-flash CSFB, and
SRVCC, based on the PLMN ID and LAC of the peer end, to implement operator-specific policies.
For details, see Mobility Management in Connected Mode.
The following function is supported during inter-RAT handovers to NG-RAN:
Measurement and handover threshold offsets for services with different QCIs can be configured
based on PLMN IDs of different operators. In this way, different A2 measurement thresholds can be
set for different operators. For details, see Interoperability between E-UTRAN and NG-RAN.
A license is an authorization agreement between a vendor and a customer in terms of the application
scope and service lifetime of products.
In RAN sharing with common carrier, a license purchase order is placed by only one party, who can be
the primary operator or a joint venture of multiple operators. Each eNodeB still has only one license
file, which specifies the total licensed limits for all RAN sharing operators, not for a specific operator.
All feature licenses are shared by operators and are not dedicated to individual operators.
4.1.5.2 Capacity License
Capacity licenses are shared among operators, and they are not operator-specific. Some of the capacity
resource items, including the number of RRC_CONNECTED UEs and traffic, can be proportionally
configured for individual operators.
Number of RRC_CONNECTED UEs
Sharing of licensed RRC_CONNECTED UE resources on a per operator basis

The licensed RRC_CONNECTED UE resources can be distributed among operators in proportions
specified by the LicenseSharingPolicy.MaxUserNumRate parameter. The eNodeB calculates the number
of RRC_CONNECTED UEs and performs access control for each operator based on the assigned
proportion.
All of the following conditions must be met:
It is recommended that the LicenseSharingPolicy.MaxUserNumRate parameter values be properly

configured for all operators so that the sum reaches the maximum value 100%. If the sum is less
than 100%, the licensed RRC_CONNECTED UE resources will be wasted.
The proportion of license resources that can be used by each operator must be within the
configured proportion.
All operators have been configured with LicenseSharingPolicy.MaxUserNumRate.
If licensed RRC_CONNECTED UE resources do not need to be proportionally allocated among

operators, that is, operators share all licensed RRC_CONNECTED UE resources and the eNodeB does
not perform differentiated control on the number of RRC_CONNECTED UEs for each operator, then the
following methods can be used:
The LicenseSharingPolicy MO is not configured for any operator;
LicenseSharingPolicy.MaxUserNumRate is configured only for some operators.
The number of RRC_CONNECTED UEs served by each operator can be obtained from the operator-
specific performance counters about user quantity.
Sharing of licensed RRC_CONNECTED UE resources on a per RRC_CONNECTED UE number sharing
group basis
This function is an enhancement of operator-specific licensed RRC_CONNECTED UE resource sharing. If
an operator has multiple PLMN IDs, RRC_CONNECTED UE number sharing groups can be used.
Operators with the same LicenseSharingPolicy.UserNumSharingGroupId value are of the same
RRC_CONNECTED UE number sharing group (255 is an invalid value, indicating that no
RRC_CONNECTED UE number sharing group is configured). In this way, the proportion of
RRC_CONNECTED UE resources that can be shared by operators in the same group is the sum of their
LicenseSharingPolicy.MaxUserNumRate values.
The principles for configuring the LicenseSharingPolicy.MaxUserNumRate parameter are the same as
those for configuring operator-specific licensed RRC_CONNECTED UE resource sharing.
In addition to static sharing, the licensed RRC_CONNECTED UE resources can be dynamically

shared in FDD. An operator (for example, operator A) can share its unused allotment of
RRC_CONNECTED UE resources with another operator (for example, operator B). When operator
A's UEs access the network, they can reclaim those previously shared resources by preemption if
needed. The total proportion of all RRC_CONNECTED UE resources used by operator A is still
limited by the amount specified in the purchased licenses. For details, see 9 Fair User Sharing
(FDD).
Traffic Volume
The LicRatio.TrafficSharingType parameter specifies whether the total traffic of the eNodeB is
proportionally allocated to operators.
If this parameter is set to SHARING, all operators share the total traffic of the eNodeB.
If this parameter is set to DEDICATE, the traffic volume of the eNodeB is allocated to operators in
proportions.
The proportion allocated to each operator is specified by the LicRatioSharePolicy.TrfRatio parameter. In

addition, the unused resources of an operator can be shared by other operators based on the
proportion specified by the LicRatioSharePolicy.TrfSharingRatio parameter. These resources can be
reclaimed if needed.
In this case, the following conditions must be met:
It is recommended that the LicRatioSharePolicy.TrfRatio parameter values be properly configured

for all operators so that the sum reaches the maximum value 100%. If the sum is less than 100%,
the licensed traffic resources will be wasted.
For each operator, the value of the LicRatioSharePolicy.TrfSharingRatio parameter cannot be

greater than that of the LicRatioSharePolicy.TrfRatio parameter.
If the LicRatioSharePolicy.TrfRatio parameter is configured only for some operators, traffic

resources are not allocated among operators based on the configured proportions. In this case, the
licensed traffic resources are all shared among operators.
When traffic volume is allocated among operators based on proportions, configuring different sharing
proportions can reach different sharing effects, including non-sharing, partial sharing, or full sharing. In
the following examples, the LicRatioSharePolicy.TrfRatio parameter is set to 50% for the two operators
(A and B), the traffic volume of operator A is greater than 50%, and that of operator B is less than 50%.
Non-sharing
When the LicRatioSharePolicy.TrfSharingRatio parameter is set to 0% for both operators, operator
A cannot occupy the traffic volume of operator B.
Partial sharing
A can occupy the traffic volume of operator B but at most 60% of the total traffic volume.
Full sharing
A can occupy the traffic volume of operator B and all the total traffic volume can be occupied by
operator A.
The traffic volume used by each operator can be obtained from the operator-specific performance
counters about traffic.
4.1.6 Air Interface Resource Management
Based on the objects, air interface resource management falls into the following two types:
Operator-specific air interface resource management: Multiple operators share RAN resources.
Therefore, air interface resources need to be managed on a per operator basis.
Operator-group-specific air interface resource management: This is an enhancement to operator-

specific air interface resource management. This function is controlled by the
OpPrbGroupshareSwitch option of the CellAlgoSwitch.OpResourceGroupShareSwitch parameter.
When three or more operators share a cell, some of the operators form an alliance. The operators
that have alliance relationships can be regarded as one operator group. The operator group to
which an operator belongs is specified by the CellOp.OpResourceGroupIndex parameter. Operators
with the same value of this parameter belong to the same operator group and can be considered
as one operator. Air interface resources are preferentially shared within an operator group. If there
are remaining air interface resources in the group, they can be shared to operators beyond the
group.
The monitoring results of quality of service (QoS) satisfaction rate and cell performance are
displayed on a per cell basis. The value of the operator field is that of
CnOperator.CnOperatorID of the corresponding operator.
There are three sharing modes of air interface resource management.
RAN Sharing Without Differentiating Operators
In RAN sharing with common carrier, if the CellAlgoSwitch.RanShareModeSwitch parameter is set to

OFF, admission control, congestion control, and scheduling policies are not performed on a per
operator basis.
For details about admission and congestion control, see Admission and Congestion Control.
Dynamic Sharing Mode
If the CellAlgoSwitch.RanShareModeSwitch parameter is set to ON in a cell where RAN sharing with

common carrier is enabled, the eNodeB performs admission control, congestion control, scheduling,
and mobility load balancing on a per operator basis. If an operator has unused RBs, these RBs can be
shared with other operators. If no operator has unused RBs, RBs are allocated proportionally.
The CellOp MO is used to configure the RB allocation proportion for each operator and control the
maximum RB allocation proportion for each operator. For details, see 4.1.6.1 Dynamic RB Resource
Sharing.
The eNodeB must calculate and record the following items for each operator to perform admission
control, congestion control, scheduling, and mobility load balancing on a per operator basis:
QoS satisfaction rate corresponding to QoS class identifier (QCI) x of all UEs (x ranges from 1 to
4 or equals 65.)
RB usage for all guaranteed bit rate (GBR) services. The eNodeB calculates the RB usage based
on the CellOp.OpUlRbUsedRatio and CellOp.OpDlRbUsedRatio parameter settings.
For example, if operators A and B share resources, the eNodeB performs admission control,
congestion control, and scheduling while observing the following two principles:
When operator B is serving a small number of UEs, the UEs served by operator A can access
the eNodeB and use available eNodeB resources.
When the number of UEs served by operator B increases, the eNodeB performs scheduling to
ensure that the correct proportion of resources is used by operator B. When this happens,
services provided by operator A are affected and the QoS satisfaction rate decreases. When the
eNodeB detects this overload for services provided by operator A, it performs congestion
control.
Static Sharing Mode
When the CellAlgoSwitch.RanShareModeSwitch parameter is set to STATIC_SHARING in a cell where

RAN sharing with common carrier is enabled, the eNodeB performs admission control, congestion
control, scheduling, and mobility load balancing on a per operator basis. RBs are allocated in
proportions for each operator in each transmission time interval (TTI). If an operator has unused RBs in
certain TTIs, these RBs cannot be shared by other operators.
The CellOp.OpDlRbUsedRatio and CellOp.OpUlRbUsedRatio parameters are configured for each

operator to specify the proportions of the RBs allocated in the downlink and uplink, respectively.
The sum of the uplink or downlink RB used ratios for all operators cannot be greater than 100%. It
is recommended that the sum be 100%.
Scheduling priority adjustment enables the proportion of RBs occupied by each operator to reach
or approach the configured RB allocation proportion. To maximize resource usage, in each TTI,
When the sum of the uplink or downlink RB used ratios for all operators is less than 100%, the
eNodeB cannot allocate any remaining available RBs to operators requiring additional
transmission resources.
When an operator has unused RBs, other operators cannot use these RBs.
When there are retransmission UEs, the scheduling of retransmission UEs is not
restricted by static RB configuration. When the number of RBs scheduled for
retransmission UEs exceeds the number of static RBs, the RBs of other operators are
used.
In RAN sharing, if user scheduling is performed on a per RBG basis, the number of
actually scheduled RBs may be 1 to 3 greater than that of statically configured RBs.
The eNodeB must calculate and record the following items for each operator to perform admission
control, congestion control, scheduling, and mobility load balancing on a per operator basis:
QoS satisfaction rate corresponding to QoS class identifier (QCI) x of all UEs (x ranges from 1 to
4 or equals 65.)
RB usage for all guaranteed bit rate (GBR) services. The eNodeB calculates the RB usage based
on the CellOp.OpUlRbUsedRatio and CellOp.OpDlRbUsedRatio parameter settings.
After this function is enabled, the values of counters in the following counter subsets will fluctuate:
Throughput and Data Volume Measurement per CNOperator
PRB Measurement per CNOperator
Throughput and Data Volume Measurement
PRB Measurement
eMTC throughput or data volume measurement
Operator groups do not support the static sharing mode.
4.1.6.1 Dynamic RB Resource Sharing
When the CellAlgoSwitch.RanShareModeSwitch parameter is set to ON, operators can dynamically share
RB resources.
To enable operator-specific RB resource sharing, set the percentage of downlink RBs occupied by each
operator (specified by the CellOp.OpDlRbUsedRatio parameter) and the percentage of uplink RBs
occupied by each operator (specified by the CellOp.OpUlRbUsedRatio parameter). Neither the sum of
the percentages of uplink RBs occupied by all operators nor the sum of the percentages of downlink
RBs occupied by all operators can be greater than 100%. It is recommended that these sums all be
100%. Scheduling priority adjustment enables the percentage of RBs actually occupied by each
operator to reach or approach the configured value.
When RB sharing based on operator groups is enabled, the preceding functions are performed
on a per operator resource group basis.
If RBs are proportionally allocated to operators, the RB sharing ratio with other operators (specified by
the CellOp.RbSharingRatioWithOtherOp parameter) and the operator maximum available RB ratio
(specified by the CellOp.OpMaxAvailableRbRatio parameter) can be configured to achieve no sharing,
partial sharing, and full sharing effects.
No Sharing
If the CellOp.RbSharingRatioWithOtherOp parameter is set to 0 for all operators, they cannot occupy each
other's RBs. In this case, the maximum available RB ratio of an operator is the configured percentage of
uplink/downlink RBs.
For example, if operators A and B share RB resources and their percentages of uplink/downlink RBs are
all set to 50%, operators A and B can occupy a maximum of 50% RB resources, respectively.
Partial Sharing
If the CellOp.RbSharingRatioWithOtherOp parameter is set to non-zero values for all operators and the
sum of the values is less than 100, an operator can occupy partial RBs of another operator.
If two operators share RB resources, the maximum number of available RBs for each operator can
be controlled only by setting the CellOp.RbSharingRatioWithOtherOp parameter. Retain the default
value 100 for the CellOp.OpMaxAvailableRbRatio parameter.

For example, operators A and B share RB resources and their percentages of RB occupation are set
as described in Table 4-1. In non-congestion scenarios, operator A can occupy a part of RB resources
of operator B and can use up to 70% of total RB resources in a cell. Operator B can occupy a part of
RB resources of operator A and can use up to 60% of total RB resources in a cell.
Table 4-1 Percentages of RB occupation for two operators
RB Occupation Percentage Operator A Operator B
Percentage of downlink RB occupation 50% 50%

(CellOp.OpDlRbUsedRatio) and percentag
e of uplink RB occupation (CellOp.OpUl
RbUsedRatio)
RB sharing ratio with other operators 10% 20%

(CellOp.RbSharingRatioWithOtherOp)
CellOp.OpMaxAvailableRbRatio 100% 100%
If three or more operators share RB resources, both CellOp.RbSharingRatioWithOtherOp and

CellOp.OpMaxAvailableRbRatio parameters must be set to limit the maximum number of RBs
available for each operator.
For example, operators A, B, and C share RB resources and their percentages of RB occupation
parameters are set as described in Table 4-2. In non-congestion scenarios, the actual maximum
available RB ratio for each operator is calculated as follows:
1. The maximum available RB ratios can be calculated based on the

CellOp.RbSharingRatioWithOtherOp parameter setting. Assuming that the values of this
parameter for the three operators are X1, Y1, and Z1, they are calculated as follows: X1 = 50%
+ 30% + 20% = 100%; Y1 = 30% + 20% + 20% = 70%; Z1 = 20% + 20% + 30% = 70%
2. The maximum available RB ratios can also be specified using the CellOp.OpMaxAvailableRbRatio
parameter. Assuming that the values of this parameter for the three operators are X2, Y2, and
Z2, respectively, they are specified as follows: X2 = 100%; Y2 = 50%; Z2 = 50%
3. Assuming that X, Y, and Z are respectively the actual maximum available RB ratios of the three
operators, they are calculated as follows: X = min(X1, X2) = 100%; Y = min(Y1, Y2) = 50%; Z =
min(Z1, Z2) = 50%
Table 4-2 Example of RB allocation for three operators
RB Occupation Percentage Operator A Operator B Operator C
Percentage of downlink RB occupation 50% 30% 20%

(CellOp.OpDlRbUsedRatio) and percentag
e of uplink RB occupation (CellOp.OpUl
RbUsedRatio)
RB Occupation Percentage Operator A Operator B Operator C
RB sharing ratio with other operator (C 20% 30% 20%

ellOp.RbSharingRatioWithOtherOp)
Operator maximum available RB ratio 100% 50% 50%

(CellOp.OpMaxAvailableRbRatio)
Full Sharing
If the value sum of the CellOp.RbSharingRatioWithOtherOp parameter for all operators is 100 and the
CellOp.OpMaxAvailableRbRatio parameter is set to 100 for all operators, each operator can occupy all
RBs of another operator.
For example, operators A and B share RB resources and their configured percentages of
uplink/downlink RB occupation are 60% and 40%. The CellOp.RbSharingRatioWithOtherOp parameter
is set to 60 for operator A and 40 for operator B. In non-congestion scenarios, operators A and B
can occupy a maximum of 100% RB resources.
If the CellOp.RbSharingRatioWithOtherOp parameter is set to 255 for all operators, any proportion or
even 100% of an operator's RBs can be shared with other operators.
If the sum of the percentages of uplink/downlink RB occupation of all operators is less

than 100%, it is recommended that the CellOp.RbSharingRatioWithOtherOp parameter be
set to 255 for all operator to maximize resource utilization. In this way, RBs that are not
configured can be allocated to operators that require data transmission, achieving full
resource sharing.
In no sharing or partial sharing scenarios, if the number of RBs occupied by an operator
reaches the upper limit, the remaining RBs can be scheduled for only signaling, voice,
and retransmission services of the operator.
In no sharing or partial sharing scenarios, the operator whose resources are preempted
can reclaim the resources if the signaling, voice services, or retransmission traffic
volume of the operator reach specified thresholds.
RB resources are more likely to be insufficient when RBs are not shared or partially
shared among operators. When eMTC UEs occupy a large number of resources, the
user-perceived rate of common UEs decreases.
When the operator resource group sharing switch is turned on, only full sharing is
supported.
Full Fair Sharing Among Operators
When three or more operators share a cell, the OP_FAIR_SHARING_SWITCH option of the
CellOp.OperatorFunSwitch parameter can be selected to enable full fair sharing among operators.
All operators with this option selected have the same scheduling priority and they are in a full fair
sharing relationship.
If this option is deselected, this function does not take effect.
4.1.6.2 Admission Control
The rules for GBR service admission control on a per operator basis are as follows:
In the uplink, the RB usage of the cell and the RB usage and QoS satisfaction rate corresponding to
QCI x (x ranges from 1 to 4 or equals 65.) are measured and detected for each operator to
determine whether to admit GBR services. The other processes in RAN sharing with common
carrier are the same as those in the independent operator mode.
In the downlink, the QoS satisfaction rate corresponding to QCI x (x ranges from 1 to 4 or equals
65.) is measured and detected for each operator to determine whether to admit GBR services. The
other processes in RAN sharing with common carrier are the same as those in the independent
operator mode.
GBR service preemption: If GBR services of an operator fail to be admitted, the eNodeB performs
GBR service preemption within the operator.
For details about admission control, see Admission and Congestion Control.
4.1.6.3 Congestion Control
The rules for congestion control on a per operator basis are as follows:
In the uplink, the RB usage of the cell and the RB usage and QoS satisfaction rate corresponding to
QCI x (x ranges from 1 to 4 or equals 65.) are measured and detected for each operator to
determine whether to perform congestion control. The other processes in RAN sharing with
common carrier are the same as those in the independent operator mode.
In the downlink, the QoS satisfaction rate corresponding to QCI x (x ranges from 1 to 4 or equals
65.) is measured and detected for each operator to determine whether to perform congestion
control. The other processes in RAN sharing with common carrier are the same as those in the
independent operator mode.
Service release: If an operator's cell is overloaded, the eNodeB releases some of the operator's
services. The service release rules are the same as those in the independent operator mode.
For details about congestion control, see Admission and Congestion Control.
4.1.6.4 Scheduling Policies
Dynamic scheduling is performed on a per operator basis. The dynamic scheduling process is as
follows:
1. The eNodeB groups UEs based on PLMN IDs (operators).
2. The eNodeB determines the priority of each UE group based on the RB usage of each operator. A
lower RB usage indicates a higher priority.
3. The eNodeB schedules UEs in descending order of priority. UEs in the same UE group are
scheduled in the same way as those in the independent operator mode.
Semi-persistent scheduling, control-plane message scheduling, and Hybrid Automatic Repeat Request
(HARQ) retransmission scheduling policies in the RAN sharing mode are the same as those in the
For details about scheduling, see Scheduling.
4.1.6.5 Mobility Load Balancing
When RAN sharing is enabled, the eNodeB supports operator-level inter-frequency mobility load
balancing (MLB) based on the PRB usage or number of UEs.
For details about MLB, see Intra-RAT Mobility Load Balancing.
4.1.6.6 Carrier Aggregation
In RAN sharing scenarios, the eNodeB supports operator-specific CA configuration.
For details about CA, see Carrier Aggregation.
Only operator-specific CA configuration is supported, and CA configuration based on operator

resource groups is not supported.
When RAN sharing is enabled in the serving cell and a neighboring cell, ANR allows the serving
eNodeB of a UE to obtain the PLMN list of the neighboring cell from the OSS that manages both cells.
This reduces unexpected handovers and improves network performance. In addition, manual
intervention is not required, decreasing the network planning and optimization costs. To enable the
serving eNodeB to obtain the correct PLMN list from the OSS, set the options of the
ENodeBAlgoSwitch.RanSharingAnrSwitch parameter accordingly. For example, when Cell 1 and Cell 2
may have neighbor relationships, the parameter needs to be configured as follows:
If the CellAccess.BroadcastMode parameter is set to RR_MODE or FREE_Mode in Cell 1, select the

NBSLTEPLMNRoundSwitch option of the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter for
the eNodeB that serves Cell 2. If this option is deselected, a UE may not obtain the correct serving
PLMN information for Cell 1 where the PLMN ID at the top of the broadcast PLMN list is rotated. As
a result, a handover to Cell 1 according to the neighbor relationships set up by ANR may fail.
If the CellAccess.BroadcastMode parameter is set to NORMAL_MODE in Cell 1, select the

NBSLTERANSharingSwitch, NBSUTRANRANSharingSwitch, or NBSGERANRANSharingSwitch
option of the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter for the eNodeB that serves Cell 2.
If none of these options is selected, a UE may report an incomplete PLMN list. As a result, the
information about Cell 1 cannot be correctly added, and the UE of a secondary PLMN may not be
handed over to Cell 1 according to the neighbor relationships set up by ANR.
For details about ANR procedures, see ANR Management.
The OSS can manage both shared and non-shared eNodeBs. OSS management mainly includes
configuration management, fault management, and performance management.
All of the operators can share the OSS, which manages NEs on the eRAN and connects to operators'
upper-layer NMSs through their own Itf-N interfaces.
Configuration management in RAN sharing mode is the same as that in independent operator mode.
All RAN parameters are negotiated by operators and configured by an OM team.
The configuration data reported through an operator-specific Itf-N interface from the OSS includes the
eNodeB-level common information and the operator-specific cell-level information.
On the eNodeB, S1 and X2 interface alarms are reported on a per operator basis.
On the OSS, some important alarms, such as those related to S1 and X2 interfaces, are sent to the NMS
of each operator through the Itf-N interface. The alarm information sent to the NMS of an operator
includes information exclusive to the operator and common information.
On the eNodeB side, the values of some key counters are collected specifically for different operators.
On the OSS side, performance statistics are reported to each individual operator through the Itf-N
interface. Dedicated data is reported to the operator it concerns, and common data is reported to all
operators.
In RAN sharing with common carrier mode, the S1 and X2 interfaces may be shared by operators or
not, with the transmission networking being different in these scenarios.
When operators share one transmission port, the port attributes and related parameters must be
appropriately configured according to the backhaul transport network conditions of the operators in
the eNodeB.
A typical parameter is the maximum transmission unit (MTU) of this transmission port. For details
about the MTU, see IPv4 Transmission.
If the backhaul networks of operators who share an eNodeB have different MTUs, the MTU of a shared
transmission port can be configured in either of the following ways:
Set the MTU of the transmission port to the minimum value, that is, MIN(MTU1, MTU2, MTU3...).
Using this method enables the fragmentation of any excessively long packet on the eNodeB.
Set the MTU of the transmission port to the maximum value, that is, MAX(MTU1, MTU2, MTU3...).
Using this method reduces the pressure for fragmenting and reassembling packets on backhaul
networks with large MTUs. Some packets on backhaul networks with small MTUs will be
fragmented by routers.
The S1 interface connects the eNodeB and EPC. There are two types of S1 interfaces: S1-C and S1-U.
The S1-C interface transfers signaling messages over the control plane between the eNodeB and MME.
The S1-U interface transfers data over the user plane between the eNodeB and S-GW.
The X2 interface connects eNodeBs. It has a control plane and a user plane. The X2 control plane
transfers signaling messages between eNodeBs. The X2 user plane transfers user data between
eNodeBs.
It is recommended that operators sharing the RAN plan IP addresses in a unified manner to prevent
possible IP address conflicts between operators.
The eNodeB supports two configuration modes for both S1 and X2 interfaces: endpoint and link
modes. The configuration mode determines the MOs to be configured.
Endpoint mode
Figure 4-7 shows the required MOs and the relationships between them in endpoint mode. The
SCTPPEER and USERPLANEPEER MOs are optional for both the S1 and X2 interfaces. For details,
see S1 and X2 Self-Management.
Figure 4-7 MOs for configuring the S1 and X2 interfaces in endpoint mode
In endpoint mode, the CnOperatorId parameter of the S1 or X2 MO indicates the operator that
the S1 or X2 interface belongs to. The CpEpGroupId and UpEpGroupId parameters of the same
MO indicate the control-plane and user-plane endpoint resource groups, respectively. The
SCTPHOST and SCTPPEER MOs specify the local and peer control-plane IP addresses for S1 or X2,
respectively. The USERPLANEHOST and USERPLANEPEER MOs specify the local and peer user-
plane IP addresses for S1 or X2, respectively.
In S1 or X2 simple mode (specified by the GTRANSPARA.EPCFGMODE parameter), a maximum of
two operators can be configured for each eNodeB. RAN sharing with dedicated carrier, hybrid RAN
sharing, or RAN sharing with special dedicated carrier is not supported.
Link mode
In link mode, the IPPATH, SCTPLNK, S1Interface, CPBEARER, and eNodeBPath MOs need to be
configured for the S1 interface. The IPPATH, SCTPLNK, X2Interface, CPBEARER, and eNodeBPath
MOs need to be configured for the X2 interface. The CnOperatorIpPath MO is optional for the X2
interface. For details, see IP eRAN Engineering Guide.
During the initial configuration of RAN sharing with common carrier, note the following:
You can configure S1 transmission links only for operators who will provide services or undergo
testing during the initial stage of network deployment.
If multiple operators sharing the RAN concurrently provide services, configure the S1 transmission
links for all operators. You must check the configurations carefully and ensure that none of the S1
transmission links are missing.
Table 4-3 and Table 4-4 describe the S1 and X2 transmission link configurations (whether dedicated to
individual operators or shared by the operators) for RAN sharing with common carrier in different
topologies.
Table 4-3 Configuration of dedicated or shared control-plane transmission links for RAN
sharing with common carrier in different topologies
Transmission Link S1 with Dedicated MME S1 with Shared MMEs X2

s
Control-plane link Dedicated Shared Shared
In RAN sharing with common carrier, X2 control-plane links are shared among operators. An
eNodeB must use the same X2 control-plane configuration for its X2 control-plane links
connected to a gNodeB and another eNodeB.
Table 4-4 Configuration of dedicated or shared user-plane transmission links for RAN sharing
with common carrier in different topologies
Transmission Link S1 with Dedicated S-GW S1 with Shared S-GWs X2

s
User-plane link Dedicated Dedicated or shared Dedicated or shared
The transmission links can be created in endpoint or link mode.
Endpoint Mode
Table 4-5 Control-plane transmission link configuration in endpoint mode for RAN sharing
with common carrier
Configuration Item S1 with Dedicated MME S1 with Shared MMEs X2

s
S1 or X2 MO Configure a dedicate Configure the CpEpG Configure a dedicate

d S1 MO for each op roupId parameter for d X2 MO for each op
erator, and specify a the S1 MO of only on erator, specify a uniq
unique CpEpGroupId e operator. ue CpEpGroupId par
parameter value for e ameter value for each
ach MO. X2 MO, and specify t
he same SCTPHOST
MO for all operators t
o share.
Local control plane Configure a single loc Configure a single loc Configure a single loc
al S1 control-plane IP al S1 control-plane IP al X2 control-plane IP
address for the opera address for the opera address for the opera
tors to share, or confi tors to share. tors to share.

s
gure a dedicated one

for each operator.
Peer control plane Configure a dedicate Configure a single pe Configure a single pe

d peer S1 control-pla er S1 control-plane IP er X2 control-plane IP
ne IP address for eac address for the opera address for the opera
h operator. tors to share. tors to share.
Table 4-6 User-plane transmission link configuration in endpoint mode for RAN sharing with
common carrier
Configuration Item S1 with Dedicated S-GW S1 with Shared S-GWs X2

s
S1 or X2 MO Configure a dedicate If operators share If operators share

d S1 MO for each op an S1 user-plane an X2 user-plane
erator, and specify a link, configure a link, configure a
unique UpEpGroupId dedicated S1 MO dedicated X2 MO
parameter value for e for each operator for each operator
ach MO. and specify the s and specify the s
ame UpEpGroup ame UpEpGroup
Id parameter valu Id parameter valu
e for the MOs. e for the MOs.
If operators use d If operators use d
edicated S1 user- edicated X2 user-
plane links, confi plane links, confi
gure a dedicated gure a dedicated
S1 MO for each o X2 MO for each
perator and speci operator and spe
fy a unique UpEp cify a unique UpE
GroupId paramet pGroupId param
er value for each eter value for eac
MO. h MO.
Local user plane Configure a single loc Configure a single loc If multiple operat
al S1 user-plane IP ad al S1 user-plane IP ad ors share an X2 u
dress for the operator dress for the operator ser-plane link, th
s to share, or configur s to share, or configur ey can share the l
e a dedicated one for e a dedicated one for ocal X2 user-plan
each operator. each operator. e IP address.
If multiple operat
ors do not share
an X2 user-plane
link, plan a dedic
ated local X2 user

s
-plane IP address
for each operator.
Peer user plane Configure a dedicate Configure a single pe Configure a single pe

d peer S1 user-plane I er S1 user-plane IP ad er X2 user-plane IP ad
P address for each op dress for the operator dress for the operator
erator. s to share, or configur s to share, or configur
e a dedicated one for e a dedicated one for
each operator. each operator.
When all operators use the same local and peer user-plane IP address:
If an eNodeB works in RAN sharing with common carrier mode, configure the same EPGROUP MO
for all operators. Otherwise, only the first user-plane channel can be successfully set up.
If the newly configured EPGROUP MO for which the user-plane link is to be set up has the same
local and peer user-plane IP addresses as an existing EPGROUP MO, delete the newly configured
MO or refer it to the existing EPGROUP MO. Otherwise, user-plane link setup will fail.
When an eNodeB autonomously obtains the peer X2 control-plane IP addresses (that is, when the
SCTPPEER MO is not configured):
Only handovers for UEs of a specific operator configured with an X2 MO can trigger the setup of an X2
control-plane link. The UEs served by the other operators can be handed over through the X2 interface
only after the control-plane link is set up.
In RAN sharing with common carrier, operator-specific virtual routing and forwarding (VRF) must be
planned for isolated transmission among operators.
In RAN sharing with common carrier where operators do not share an X2 user-plane link,
the SHARE_FREQ_X2_UP_OPT_SW option of the
EnodebAlgoExtSwitch.NetworkPrfmOptSwitch parameter must be selected. (This does not
apply in other RAN sharing scenarios.)
If operators do not share an X2 user-plane link in RAN sharing scenarios, each of the
operators must be configured with an X2 object associated with a unique user-plane
EPGROUP MO. If certain operators are not configured with X2 objects, the eNodeB may
initiate self-setup of inter-operator X2 user-plane links. In addition, if an inter-operator
transmission link is faulty, a user-plane fault alarm is reported and packet loss may occur
during X2-based handovers.
When the base station is configured with two main control boards and the IPv4/IPv6 dual-
stack is used, both IPv4 and IPv6 addresses must be configured for the X2 and Xn interfaces
planned for dual-stack transmission on a single main control board. It is not allowed that
one main control board is configured only with IPv4 addresses and the other main control
board is configured only with IPv6 addresses.
Link Mode
Table 4-7 Control-plane transmission link configuration in link mode for RAN sharing with
common carrier

s
Control plane Configure dedicated Only configure S1Int Configure X2Interfac

S1Interface and SCT erface and SCTPLNK e and SCTPLNK MOs
PLNK MOs for each o MOs for the operator for the operators to s
perator. s to share. hare.
Table 4-8 User-plane transmission link configuration in link mode for RAN sharing with
common carrier

s
User plane Configure a dedicate Configure a single IP Configure a single IP

d IPPATH MO for eac PATH MO for the ope PATH MO for the ope
h operator. rators to share, or co rators to share, or co
nfigure a dedicated o nfigure a dedicated o
ne for each operator. ne for each operator.
If a dedicated IPPAT If a dedicated IPPAT
H MO is configured f H MO is configured f
or each operator, con or each operator, con
figure CnOperatorIp figure CnOperatorIp
Path MOs to define t Path MOs to define t
he mapping relations he mapping relations
hips between the ope hips between the ope
rators and the IP path rators and the IP path
s. s.
In RAN sharing with common carrier, it is recommended that transmission resource groups be
configured for individual operators. To dynamically share uplink transmission bandwidth between
transmission resource groups, enable the overbooking function for the physical port by setting the
total bandwidth of transmission resource groups to be greater than the physical port bandwidth. For
details, see Transmission Resource Management.
Each operator can use a unique virtual local area network (VLAN). For details about how to divide
VLANs, see IPv4 Transmission.
This function enables the eNodeB to support PKIs of multiple operators. Each operator deploys a PKI
and the IPsec tunnel uses the certificate issued by the PKI server of each operator for authentication,
independent of the primary operator's PKI. This function achieves service isolation among operators.
For details, see Base Station Supporting Multi-operator PKI.
4.2.1 Benefits
RAN sharing provides the following benefits for operators:
Reduced capital expenditure (CAPEX) and operating expense (OPEX)
Accelerated network deployments
Expanded network coverage
4.2.2 Impacts
Network Impacts
Compared with scenarios other than RAN sharing with common carrier:
If the UE distribution is inconsistent among operators sharing the network, the traffic volume may
change. As a result, the values of indicators such as MCS indexes, CCE usage, and UE measurement
results may change.
The traffic volume is not affected if the UE distribution is consistent among operators sharing the
network.
If the RB proportions vary greatly between the RAN sharing operators (for example, 9:1 for two
operators), UEs served by the operator with a smaller RB proportion experience a longer scheduling
delay after RAN sharing with common carrier is enabled. However, the scheduling delay can still meet
the QoS requirements specified in section 6.1.7.2 "Standardized QCI characteristics" in 3GPP TS 23.203
V8.5.0.
Function Impacts
RAT Function Name Function Switch Reference Description
FDD Out-of-band rela OutOfBandRela Relay When out-of-band relay a

y ySwitch option nd RAN sharing with com
of the CellAlgoS mon carrier are both enab
witch.RelaySwitch led, all resources of operat
parameter ors (including RB resource
s, licensed traffic, and lice
nsed number of RRC_CON

NECTED UEs) can only be
shared completely, not par
tly.
FDD In-band relay None Relay When in-band relay and R

AN sharing with common
carrier are both enabled, a
ll resources of operators (i
ncluding RB resources, lice
nsed traffic, and licensed
number of RRC_CONNECT
ED UEs) can only be share
d completely, not partly.
FDD VoIP semi-persis VoLTE Voice services have a high

SpsSchSwitc
tent scheduling h option of t scheduling priority and ar
he CellAlgo e sensitive to scheduling d
Switch.UlSch elays. Uplink and downlin
Switch param k semi-persistent scheduli
eter ng does not consider the
configured proportions of
SpsSchSwitc
RBs that can be allocated t
h option of t
o different operators.
he CellAlgo
Switch.DlSch
Switch param
eter
FDD PRB upper limit c CellWttxParaCf WBB In RAN sharing with com
ontrol mode g.PrbUpLimitCtrlMo mon carrier mode, if tight
de control over the maximum
PRB usage is implemente
d, the proportions of RBs
allocated to an operator c
annot exceed the preset t
hresholds.
FDD WTTx MU-MIMO Tm9FourLayerP WTTx MU-MIMO (FD Only UEs whose operators
D)
airSwitch option are in the same operator g
of the CellAlgoE roup can be paired for MU
xtSwitch.WttxMuM -MIMO.
imoSwitch parame
ter
FDD CSPC CspcAlgoPara.Cs CSPC If CSPC is enabled and do

pcAlgoSwitch wnlink PRB proportions ar
e specified for the operato
rs that share individual cel

ls, fairness among CSPC-e
nabled cells cannot be ens
ured and network perform
ance deteriorates. Therefo
re, it is not recommended
that CSPC be activated to
gether with RAN sharing
with common carrier.
FDD Intelligent power CellShutdown.C Energy Conservation In RAN sharing scenarios,

and Emission Reducti
-off of carriers in ellShutdownSwitch on the PLMN IDs of a capacit
the same covera set to ON y cell must be a subset of
ge the PLMN IDs of its co-co
verage neighboring basic
cell. Otherwise, the capaci
ty cell cannot be shut dow
n.
FDD Multi-carrier coo CellShutdown.C Energy Conservation In RAN sharing scenarios,

rdinated energy ellShutdownSwitch on the PLMN IDs of a capacit
saving set to ON_MULT y cell must be a subset of
I_CARRIER_HIER the PLMN IDs of its co-co
_SHUTDOWN or verage neighboring basic
ON_MUL_CARR_ cell. Otherwise, the capaci
HIER_MANUAL_ ty cell cannot be shut dow
SHUTDN n.
FDD Direct IPsec self- USERPLANEHO X2 and S1 Self-Manag Direct IPsec self-setup is in
ement in NSA Network
setup ST.IPSECSWITCH a ing compatible with RAN Shar
nd SCTPHOST.SI S1 and X2 Self-Manag ing.
GIP1SECSWITCH ement
FDD Uplink single-sid UlInterfSuppres Interference Detection It is recommended that int

and Suppression
e in-band interfe sCfg.UlSingleSideIn erference detection and s
rence managem trfImpMitSw uppression not be enable
ent d in RAN sharing scenario
s.
FDD LTE FDD and NR SpectrumCloud. LTE FDD and NR Spe When RAN sharing with c
Flash Dynamic S SpectrumCloudSwitc ctrum Sharing ommon carrier is enabled
h
pectrum Sharing together with LTE FDD an
d NR Flash Dynamic Spect
rum Sharing (that is, Spec
trumCloud.SpectrumCloudS
witch is set to LTE_NR_SPE
CTRUM_SHR), the numbe
r of available RBs for an o
perator is calculated as fol

lows: (Total number of RBs
– Number of RBs shared t
o the NR network) x RB all
ocation proportion config
ured for the operator
FDD Hybrid DSS Base SpectrumCloud. LTE FDD and NR Spe When RAN sharing with c
ctrum Sharing
d on Asymmetric SpectrumCloudSwitc ommon carrier is enabled
Bandwidth h set to LTE_NR_ together with Hybrid DSS
SPECTRUM_SH Based on Asymmetric Ban
R, and the LNR_ dwidth, the number of ava
SPECTRUM_SHR ilable RBs for an LTE opera
_ASYM_SW opti tor is calculated as follow
on of the Spectr s: (Total number of RBs –
umCloud.Spectru Number of RBs shared wit
mCloudEnhSwitch p
h NR) x RB allocation prop
arameter selecte ortion configured for the
d operator.
FDD Centralized pow LTE_CENTRAL_P Dynamic Power Shari In static RAN sharing mod
ng Between LTE Carri
er sharing OWER_SHARIN ers e, the power estimation fo
G_SW option of r centralized power sharin
the CellDynPow g does not consider the o
erSharing.Dynami perator-specific RB restrict
cPowerSharingSwitc ions. As a result, the estim
h parameter ated power is greater than
expected, and the power s
haring gain is smaller than
expected.
FDD Flexible TM4 MU FLEX_TM4_MU_ Low-Band Booster Only UEs whose operators
-MIMO MIMO_SW optio are in the same operator g
n of the CellMim roup can be paired for MU
oParaCfg.MimoSw -MIMO.
itch parameter
FDD Hybrid power sh LTE_HYBRID_PO Smart 8T8R (FDD) In static RAN sharing mod
aring WER_SHARING_ e, the power estimation fo
SW option of th r centralized power sharin
e CellDynPower g does not consider the o
Sharing.Dynami perator-specific RB restrict
cPowerSharingS ions. As a result, the estim
witch parameter ated power is greater than
expected.
FDD Dynamic carrier s CellPwrSavingAl Energy Conservation In RAN sharing scenarios,

hutdown phase go.CarrierDynShutd on the PLMN IDs of a capacit
2 ownPh2Sw set to y cell must be a subset of
CAPACITY_CELL the PLMN IDs of its co-co
n.
FDD 8T UE pairing en 8T_TM9_ENH_M Smart 8T8R (FDD) 8T UE pairing enhanceme

hancement U_SW option of nt allows only UEs in the s
the CellMimoPa ame operator group to be
raCfg.MimoSwitch paired for MU-MIMO.
parameter
4.3 Requirements
4.3.1 Licenses
If the licensed value of RAN Sharing with Common Carrier is 0, the RAN sharing with common
carrier function becomes invalid to secondary operators.
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-001036 RAN Sharing with C LT1S00RSCC00 per cell

ommon Carrier
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and mutually
exclusive functions have been deactivated. For detailed operations, see the relevant feature documents.
Prerequisite Functions
FDD S1-flex None S1-flex This function is required if

the MOCN architecture is
used.
Mutually Exclusive Functions
FDD RAN sharing wit ENodeBSharing RAN Sharing Each operator supports o
h dedicated carri Mode.ENodeBShar nly one RAN sharing mod
er ingMode e.
FDD Hybrid RAN shar ENodeBSharing RAN Sharing Each operator supports o
ing Mode.ENodeBShar nly one RAN sharing mod
ingMode e.
FDD Intra-RAT ANR ANR Management If the serving cell and neig
IntraRatEve
ntAnrSwitch hboring cells are managed
option of th by different OSSs, intra-R
e ENodeBAl AT ANR does not work wh
goSwitch.An en the PLMN ID at the top
rSwitch para of the PLMN list is rotated.
meter: contr
olling intra-
RAT event-tri
ggered ANR
IntraRatFast
AnrSwitch o
ption of the
ENodeBAlg
oSwitch.AnrS
witch parame
ter: controlli
ng intra-RAT
fast ANR
FDD LTE FDD and NR SpectrumCloud. LTE FDD and NR Upli None
nk Spectrum Sharing
Uplink Spectrum SpectrumCloudSwitc
h
Sharing
FDD Dynamic control WBBMBB_USER WBB If the CellOp.RbSharingRatio

over the maximu _PRB_UP_LMT_S WithOtherOp parameter is se
m downlink PRB WITCH and WB t to a value other than 25
usage of WBB U B_UE_DL_DYN_P 5 for any operator in a cel
Es RB_LMT_SWITC l, the WBBMBB_USER_PR
H options of the B_UP_LMT_SWITCH and
CellAlgoSwitch. WBB_UE_DL_DYN_PRB_L
SpecUserAlgoSwitch MT_SWITCH options mus
parameter t be deselected.
FDD Physical Resourc PHY_RES_SLICIN None When the Physical Resour

e Slicing G_SWITCH optio ce Slicing function is enabl
n of the CellAlgo ed:
ExtSwitch.Operat
orFunSwitch para The CellAlgoSwitch.R

meter anShareModeSwitch para
meter must be set to
OFF.
The OpPrbGroupshar
eSwitch option of the
CellAlgoSwitch.OpRes
ourceGroupShareSwitch p
arameter must be des
elected.
FDD TM4 and TM6 A CL_TM_ADAPTA Low-Band Booster If TM4 and TM6 Adaptatio
daptation TION_OPT_SW o n is enabled, the CellAlgo
ption of the Cell Switch.RanShareModeSwitch
MimoParaCfg.Mi parameter cannot be set t
moSwitch paramet o OFF.
er
4.3.3 Hardware
The hardware described in this section may require compatibility between each other. For details, see
the technical specifications and hardware description of the corresponding hardware in 3900 & 5900
Series Base Station Product Documentation.
Base Station Models
For FDD, the following base station models are compatible with this function:
3900 and 5900 series base stations (macro base stations)
DBS3900 LampSite and DBS5900 LampSite
For NB-IoT, the following base stations are compatible with this function:
Boards
No requirements
RF Modules
No requirements
4.3.4 Others
None
4.4 Operation and Maintenance (FDD)
Preparations for the transmission and interface data required in RAN sharing scenarios are similar to
those in the independent operator mode. The configurations vary depending on the network
architecture in use. For details, see 4.1.9 Transmission Networking and S1 and X2 Self-Management.
Scenario-specific data for RAN sharing with common carrier can be configured based on information
provided in this section, Cell Management, and Mobility Management in Connected Mode.
Parameters for Initial Configuration
The following table lists parameters related to X2 self-setup in endpoint configuration mode.
Table 4-9 Parameters that must be set for the GlobalProcSwitch MO
Parameter Name Parameter ID Setting Notes
The Switch of X2 GlobalProcSwitc Set this parameter based on the network plan. The swi
setup by SON h.X2SonSetupSwitch tch must be turned on if the X2 interface uses the sim
plified endpoint mode.
The method of X GlobalProcSwitc This parameter specifies the method of X2 self-setup.

2 setup by SON h.X2SonLinkSetupTy This parameter takes effect only when the GlobalProc
pe Switch.X2SonSetupSwitch parameter is set to ON.
Table 4-10 Parameters that must be set to configure the reference relationship between the
X2 and EPGROUP MOs
X2 ID X2.X2Id Set this parameter based on the network plan.
CN Operator ID X2.CnOperatorId Set this parameter based on the network plan.
End Point Group X2.EpGroupCfgFlag This parameter specifies whether to configure the cont
Config Flag rol-plane or user-plane endpoint group.
Set this parameter to CP_CFG when only control-p
lane endpoints in the EPGROUP MO are reference
d in the configuration of the X2 MO.
Set this parameter to UP_CFG when only user-plan
e endpoints in the EPGROUP MO are referenced i
n the configuration of the X2 MO.
Set this parameter to CP_UP_CFG when both contr
ol-plane and user-plane endpoints in the EPGROU
P MO are referenced in the configuration of the X

2 MO.
Control Plane En X2.CpEpGroupId Set this parameter based on the network plan.
d Point Group ID
User Plane End P X2.UpEpGroupId Set this parameter based on the network plan.
oint Group ID
Peer Base Statio X2.TargetENodeBR Set this parameter based on the network plan.
n Release elease
The following table describes the parameters used for function activation in FDD.
Table 4-11 Parameters used for activation in FDD
Local tracking ar CnOperatorTa.Tr None

ea ID ackingAreaId
CN Operator ID CnOperatorTa.C None

nOperatorId
Tracking area co CnOperatorTa.Ta In a cell where RAN sharing with common carrier is en
de c abled, configure the same TAC for all operators.
Local cell ID CellOp.LocalCellId None
Local tracking ar CellOp.TrackingAr In a cell where RAN sharing with common carrier is en
ea ID eaId abled, the CnOperatorTa.CnOperatorId parameter values
must be different. One of the parameter values must c
orrespond to the primary operator.
Operator uplink CellOp.OpUlRbUse None

RB used ratio dRatio
Operator downli CellOp.OpDlRbUse None

nk RB used ratio dRatio
Operator PLMN CellOp.OperatorPl None

Round Period mnRoundPeriod
Operator Resour CellOp.OpResourc None

ce Group Index eGroupIndex
eNodeB sharing ENodeBSharing Set this parameter to SHARED_FREQ.

mode Mode.ENodeBShar
ingMode
CN Operator ID CnOperator.CnO By default, one eNodeB can be configured with data f

peratorId or up to four operators, whose CnOperator.CnOperatorI
d values must be different.
The parameter value for each operator must be the sa
me on all eNodeBs managed by the same OSS. The PL
MN ID uniquely identifies an operator globally, which i
s composed of the MCC and MNC.
CN Operator na CnOperator.CnO None

me peratorName
CN Operator typ CnOperator.CnO Set this parameter to CNOPERATOR_PRIMARY or CN

e peratorType OPERATOR_SECONDARY based on the contracts sign
ed by the operators.
Mobile country c CnOperator.Mcc None

ode
Mobile network CnOperator.Mnc None

code
The following table describes the parameters used for function optimization in FDD.
Table 4-13 Parameters used for optimization in FDD
Local cell ID CellAccess.LocalC None

ellId
Plmn Broadcast CellAccess.Broad Set this parameter based on the network plan.
Mode castMode
Plmn Round Bro CellAccess.Round None

adcast Period Period
Plmn Round Acti CellAccess.Round None

on Time ActionTime
Different Operat GlobalProcSwitc None

or With Same M h.DiffOpWithSameM
MEC Switch mecSwitch
Parameter Name Parameter ID Option Setting Notes
CN Operator ID LicenseSharingP None None

olicy.CnOperatorId
The proportion o LicenseSharingP None None

f the maximum n olicy.MaxUserNum
umber of users Rate

f the sharing nu olicy.UserNumShari
mber of users ngRate
User Number Sh LicenseSharingP None None

aring Group ID olicy.UserNumShari
ngGroupId
Local cell ID CellAlgoSwitch. None None

LocalCellId
RAN Sharing Mo CellAlgoSwitch. None None

de Switch RanShareModeSwitc
h
Operator Resour CellAlgoSwitch. None None

ce Group Share S OpResourceGroupS
hareSwitch
witch
RB Sharing Ratio CellOp.RbSharing None None

with Other Oper RatioWithOtherOp
ator
Operator Max Av CellOp.OpMaxAvai None None

ailable RB Ratio lableRbRatio
Operator Functio CellOp.OperatorFu OP_FAIR_SHARIN Set this parameter based on the net
n Switch nSwitch G_SWITCH work plan.
Uplink Traffic Lic LicRatio.UpLicRati None None

ense Ratio o
Traffic Sharing Ty LicRatio.TrafficSh None None

pe aringType
CN Operator ID LicRatioSharePo None None

licy.CnOperatorId
TrfRatio LicRatioSharePo None None

licy.TrfRatio
TrfSharingRatio LicRatioSharePo None None
licy.TrfSharingRatio
ANR Under RAN ENodeBAlgoSwi None Select the NBSLTEPLMNRoundSwi

Sharing Algorith tch.RanSharingAnr tch option of the ENodeBAlgoSwit
m Switch Switch ch.RanSharingAnrSwitch parameter for
an eNodeB if a cell under the eNod
eB may have a neighboring cell that
meets the following conditions: The
neighboring cell is enabled with RA
N sharing with common carrier and
the CellAccess.BroadcastMode param
eter is set to RR_MODE or FREE_M
ode for the neighboring cell.
Select the NBSLTERANSharingSwit
ch, NBSUTRANRANSharingSwitch,
or NBSGERANRANSharingSwitch
option of the ENodeBAlgoSwitch.R
anSharingAnrSwitch parameter for an
eNodeB if a cell under the eNodeB
may have a neighboring cell that m
eets the following conditions: The n
eighboring cell supports RAN shari
ng with common carrier and the Ce
llAccess.BroadcastMode parameter is
set to NORMAL_MODE for the neig
hboring cell.
Handover Algo s ENodeBAlgoSwi InterPlmnHoSwit Select this option.

witch tch.HoAlgoSwitch ch
Operator Functio CnOperator.Oper INTRA_RAT_INTE Set this parameter based on the net
n Switch atorFunSwitch R_PLMN_HO_SW work plan.
UTRAN_INTER_P
LMN_HO_SW
GERAN_INTER_P
LMN_HO_SW
NR_INTER_PLMN
_HO_SW
CN Operator ID InterPlmnHoLis None None

t.CnOperatorId
Target Mobile co InterPlmnHoLis None None

untry code t.TarMcc
Target Mobile ne InterPlmnHoLis None None

twork code t.TarMnc
RAT frequency pr RatFreqPriority None None

iority group ID Group.RatFreqPrio
rityGroupId
RAT Type RatFreqPriority None None

Group.RatType
DL Earfcn or Ban RatFreqPriority None None

dclass Group.DlEarfcn
Priority RatFreqPriority None None

Group.Priority
GERAN Frequenc RatFreqPriority None None

y Indicator Group.BandIndicat
or
Spid SpidCfg.Spid None None
RAT frequency pr SpidCfg.RatFreqPr None None

iority indication iorityInd

iority group ID iorityGroupId
For FDD, set the following parameters to configure measurement frequency filtering.
Local cell ID CellHoParaCfg.Lo None None

calCellId
Handover Algo S CellHoParaCfg.C HoPlmnFilterOp In RAN sharing with common carri

witch ellHoAlgoSwitch tSw er mode, if ANR is enabled, select t
his option to ensure that the eNod
eB delivers only frequencies availa
ble to the operator when deliverin
g frequency measurement configur
ations to different operators.
Local cell ID CellOp.LocalCellId None None
Local tracking ar CellOp.TrackingAre None None

ea ID aId
RAT Frequency P CellOp.RatFreqPrio None Set different RAT/frequency priorit

riority Group ID rityGroupId y groups for LTE UEs of different o
perators.
NSA DC RAT Fre CellOp.NsaDcRatFr None Set different RAT/frequency priorit

quency Priority eqPriorityGrpId y groups for NSA DC UEs of differe
Group ID nt operators.
DL Earfcn or Ban RatFreqPriorityG None None

dclass roup.DlEarfcn
RAT frequency p RatFreqPriorityG None None

riority group ID roup.RatFreqPriorit
yGroupId
For FDD, to enable frequency-priority-based incoming handovers for UEs in an MOCN cell where MLB
is triggered, set the following parameters.
Local cell ID CellMlbHo.LocalC None None

ellId
MLB Match Othe CellMlbHo.MlbMat MocnSecOpUeF In RAN sharing with common carri
r Feature Mode chOtherFeatureMode reqPriInHoEhnS er mode, if ANR is enabled, select t
w his option to ensure that the eNod
eB delivers frequencies available to
the operator when delivering frequ
ency measurement configurations
to different operators.
The following table describes the FDD parameters that must be set to configure the dedicated cell-
reselection priority for a GERAN frequency based on the serving cell's PLMN.
Local cell ID GeranNFGroupS None

CellOp.LocalCellId
BCCH group ID GeranNFGroupS None

CellOp.BcchGroup
Id
Cn operator ID GeranNFGroupS None

CellOp.CnOperator
ID
Cell reselection d GeranNFGroupS None

edicated priority CellOp.CellReselD
configure indicat ediPriCfgInd
or
Cell reselection d GeranNFGroupS Set this parameter based on the network plan.
ediPri
reselection priority for a GERAN frequency based on the neighboring frequency's PLMN.
Local cell ID GeranRanShare. None

LocalCellId
BCCH group ID GeranRanShare. None

BcchGroupId
Mobile country c GeranRanShare. None

ode Mcc
Mobile network GeranRanShare. None

code Mnc
Cell reselection p GeranRanShare. None

riority configure i CellReselPriorityCfgI
nd
ndicator
Cell reselection p GeranRanShare. Set this parameter based on the network plan.
riority CellReselPriority
reselection priority for a UTRAN frequency based on the serving cell's PLMN.
Local cell ID UtranNFreqSCel None

lOp.LocalCellId
Downlink UARFC UtranNFreqSCel None

N lOp.UtranDlArfcn
Cn operator ID UtranNFreqSCel None

lOp.CnOperatorID
Cell reselection d UtranNFreqSCel None

edicated priority lOp.CellReselDediP
configure indicat riCfgInd
or
Cell reselection d UtranNFreqSCel Set this parameter based on the network plan.

ri
reselection priority for a UTRAN frequency based on the neighboring frequency's PLMN.
Local cell ID UtranRanShare. None

LocalCellId
Downlink UARFC UtranRanShare. None

N UtranDlArfcn
Mobile country c UtranRanShare. None

ode Mcc
Mobile network UtranRanShare. None

code Mnc
Cell reselection p UtranRanShare. None

nd
ndicator
Cell reselection p UtranRanShare. Set this parameter based on the network plan.
reselection priority for an E-UTRAN frequency based on the serving cell's PLMN.
Local cell ID EutranNFreqSCe None

llOp.LocalCellId
Downlink EARFC EutranNFreqSCe None

N llOp.DlEarfcn
Cn operator ID EutranNFreqSCe None

llOp.CnOperatorID
Cell reselection d EutranNFreqSCe None

edicated priority llOp.CellReselDedi
configure indicat PriCfgInd
or
Cell reselection d EutranNFreqSCe Set this parameter based on the network plan.
Pri
reselection priority for an E-UTRAN frequency based on the neighboring frequency's PLMN.
Local cell ID EutranNFreqRa None

nShare.LocalCellId
Downlink EARFC EutranNFreqRa None

N nShare.DlEarfcn
Mobile country c EutranNFreqRa None

ode nShare.Mcc
Mobile network EutranNFreqRa None

code nShare.Mnc
Cell reselection p EutranNFreqRa None

riority configure i nShare.CellReselP
ndicator riorityCfgInd
Cell reselection p EutranNFreqRa Set this parameter based on the network plan.
riority nShare.CellReselP
riority
reselection priority for a CDMA frequency.
Local cell ID Cdma2000BcSC None

ellOp.LocalCellId
Band class Cdma2000BcSC None

ellOp.BandClass
Cn operator ID Cdma2000BcSC None

ellOp.CnOperatorI
D
CDMA2000 HRP Cdma2000BcSC Set this parameter based on the network plan.
D dedicated prio ellOp.HrpdCellRes
rity configure ind elDediPriCfgInd
icator
CDMA2000 HRP Cdma2000BcSC Set this parameter based on the network plan.
D Cell Reselectio ellOp.HrpdCellRes
n Dedicated Prio elDediPri
rity
reselection priority for an NR frequency.
Local Cell ID NrNFreqSCellO None

p.LocalCellId
Downlink ARFCN NrNFreqSCellO None

p.DlArfcn
Cn Operator ID NrNFreqSCellO None

p.CnOperatorId
Cell Reselection NrNFreqSCellO None

Priority Config In p.CellReselPriorityC
dicator onfigInd
Cell Reselection NrNFreqSCellO Set this parameter based on the network plan.
Priority p.CellReselPriority
The following table describes the FDD parameter that must be set when both the E-UTRAN and GERAN
cells use RAN sharing with common carrier.
Protocol Messag GlobalProcSwitc L2GPLMNChoos Select this option if the GERAN cell
e Optimization S h.ProtocolMsgOptS eOptSwitch where RAN sharing with common c
witch witch arrier is enabled complies with 3GP
P R10 or earlier.
In other scenarios, select or deselec
t this option based on the actual sit
uation. Select this option to ensure
that the target PLMN IDs carried in
the handover request messages or
RIM request messages are the GER
AN-configured primary PLMN ID.
Parameters for Reconfiguration
Reconfiguration can be performed in batches on the MAE-Deployment or for a single base station on
the GUI.
A reconfiguration is required in any of the following scenarios:
The sharing mode of an eNodeB is changed from the independent operator mode to the RAN
sharing with common carrier mode. For example, if two operators are going to share eNodeB
hardware and spectrum resources, the eNodeB sharing mode must be changed and the related
secondary-operator parameters must be set. For the setting to take effect, you need to manually
reset the application referenced by the eNodeB function.
A secondary operator is added. For example, if a third operator is added to share eNodeB hardware
and spectrum resources, the related secondary-operator parameters must be set for this operator.
A secondary operator is removed. For example, if a secondary operator is removed from the three
operators that share eNodeB hardware and spectrum resources, the related secondary-operator
configurations must be removed.
The sharing mode of an eNodeB is changed from the RAN sharing with common carrier mode to
the independent operator mode. For the setting to take effect, you need to manually reset the
application referenced by the eNodeB function.
Transmission on the S1 interface for any given operator can be configured in endpoint or link mode.
For configurations in endpoint mode, see S1 and X2 Self-Management. For configurations in link mode, see
Transmission Resource Management.
The following provides the eNodeB- and operator-related MOs to be reconfigured. For details about
the parameters in the MOs and the parameter settings, see Parameters for Initial Configuration.
Changing the sharing mode of an eNodeB from the independent operator mode to the RAN
sharing with common carrier mode
The following MOs need to be reconfigured:
1. ENodeBSharingMode: Used to set the eNodeB sharing mode. After the modification, you
need to run the RST APP command to reset the application referenced by the eNodeB
function for the application to take effect (the application ID can be queried by running the
LST APP command).
2. CnOperator: Used to add operator information.
3. (Optional) LicenseSharingPolicy: Used to set the licensed proportion of RRC_CONNECTED

UEs for each operator in FDD.
4. CnOperatorTa: Used to add tracking area information.
5. CellAlgoSwitch: Used to set the RAN sharing mode switch in FDD.
6. (Optional) CellAccess: Used to set the cell access information.
7. CellOp: Used to set the cell operator information.
8. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
9. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for each operator
and the percentage of available resources one operator can share with other operators in FDD.
10. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to set the external E-

UTRAN cells and PLMN lists for the local cell and cells that have neighbor relationships with
the local cell in FDD.
11. (Optional) ENodeBAlgoSwitch.RanSharingAnrSwitch: Used to turn on the ANR switch in the

adjacent cells that have neighbor relationships with the local cell in FDD.
12. (Optional) RatFreqPriorityGroup and SpidCfg: Used to set the SPID-based dedicated cell-
reselection priority in FDD.
13. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, or

Cdma2000BcSCellOp: Used to set a dedicated cell-reselection priority based on the serving
cell's PLMN in FDD.
14. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used to set a

dedicated cell-reselection priority based on the neighboring frequency's PLMN in FDD.
Adding a secondary operator


7. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to set the external E-


Cdma2000BcSCellOp: Used to set a dedicated cell-reselection priority based on the serving
cell's PLMN in FDD.
9. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used to set a

dedicated cell-reselection priority based on the neighboring frequency's PLMN in FDD.
Removing a secondary operator

1. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to remove the external E-

2. (Optional) LicRatioSharePolicy: Used to remove the configuration of the licensed traffic

proportion for each operator and the percentage of available resources one operator can
share with other operators in FDD.
3. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.
4. CellOp: Used to remove the cell operator information.
5. (Optional) LicenseSharingPolicy: Used to remove the configured licensed proportion of

RRC_CONNECTED UEs for each operator.

Cdma2000BcSCellOp: Used to remove the dedicated cell-reselection priority configured
based on the serving cell's PLMN in FDD.
7. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used to remove the

dedicated cell-reselection priority configured based on the neighboring frequency's PLMN in
FDD.
8. CnOperatorTa: Used to remove the tracking area information.
9. CnOperator: Used to remove the operator information.
Changing the sharing mode of an eNodeB from the RAN sharing with common carrier mode to the
independent operator mode
1. (Optional) EutranIntraFreqNCell: Used to remove the neighboring relationships with intra-

frequency E-UTRAN cells in FDD. EutranInterFreqNCell: Used to remove the neighboring
relationships with inter-frequency E-UTRAN cells in FDD.
2. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to remove the external E-

3. (Optional) X2Interface: Used to remove the X2 interface in FDD.
4. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.

7. S1Interface: Used to remove the S1 interface.

RRC_CONNECTED UEs for each operator in FDD.
10. CellAlgoSwitch: Used to turn off the cell-specific RAN sharing switch.

based on the serving cell's PLMN in FDD.
12. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used to remove the

dedicated cell-reselection priority configured based on the neighboring frequency's PLMN in
FDD.

14. ENodeBSharingMode: Used to set the eNodeB sharing mode to the independent operator
mode. After the modification, you need to run the RST APP command to reset the application
referenced by the eNodeB function for the application to take effect (the application ID can be
queried by running the LST APP command).
15. (Optional) ENodeBAlgoSwitch.RanSharingAnrSwitch: Used to turn off the ANR switch in the
adjacent cells that have neighbor relationships with the local cell in FDD.
Before using MML commands, confirm the related parameter modification precautions by referring to
the fields including "Service Interrupted After Modification" and "Caution" for the corresponding
parameters in the parameter reference.
The license for this feature takes effect only after the cell is reestablished. Therefore, ensure that
sufficient licenses have been activated before running the following commands.
Activation Command Examples
The following are command examples for function activation in FDD:
//Setting the eNodeB sharing mode

MOD ENODEBSHARINGMODE: ENodeBSharingMode=SHARED_FREQ;
//Performing this step for the cell of the primary operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="unicom",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="01";
//Performing this step for the cell of the secondary operator
ADD CNOPERATOR: CnOperatorId=1, CnOperatorName="telecom",
CnOperatorType=CNOPERATOR_SECONDARY, Mcc="460", Mnc="03";
//Configuring a transmission link (in endpoint mode). Note: If operators share an S1 user-plane
link, configure the UpEpGroupId parameter for the S1 MO of only one operator. If operators use
dedicated S1 user-plane links, configure a dedicated S1 MO for each operator and specify a
unique UpEpGroupId parameter value for each MO. (In the following example, two operators
use dedicated S1 user-plane links.)
ADD EPGROUP: EPGROUPID=0, IPPMSWITCH=DISABLE;
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.3.19",
SIGIP1SECSWITCH=DISABLE, PN=36422;
ADD SCTPPEER: SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4="192.168.1.19",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=36422;
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
ADD SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.3.36",
IPSECSWITCH=DISABLE;
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="192.168.1.36",
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0,
UpEpGroupId=0;
UpEpGroupId=1;
//Configuring a transmission link (in endpoint mode). Note: X2 self-setup with X2 user-plane
shared by two operators is used as an example.
MOD GLOBALPROCSWITCH: X2SONSETUPSWITCH=ON, X2SONLINKSETUPTYPE=X2_OVER_S1;
ADD X2: X2Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=2,
UpEpGroupId=2, TargetENodeBRelease=Release_R14;
ADD X2: X2Id=1, CnOperatorId=1, EpGroupCfgFlag= CP_UP_CFG, CpEpGroupId=3,
UpEpGroupId=2;
//Configuring tracking area information for operators
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33;
ADD CELLOP: LocalCellId=0, TrackingAreaId=0,
CellReservedForOp=CELL_NOT_RESERVED_FOR_OP, OpUlRbUsedRatio=25,
OpDlRbUsedRatio=25, OpResourceGroupIndex=255, OperatorPlmnRoundPeriod=1;

//Resetting the application referenced by the eNodeB function for the application to take effect
(the application ID can be queried by running the LST APP command)
RST APP: AID=1;
Optimization Command Examples
The following are command examples for function optimization in FDD:
//Configuring the licensed proportion of RRC_CONNECTED UE resources for each operator and
the percentage of available resources one operator can share with other operators
ADD LICENSESHARINGPOLICY: CnOperatorId=0, MaxUserNumRate=50,
UserNumSharingRate=0, UserNumSharingGroupId=1;
//Configuring the cell-specific RAN sharing mode switch
MOD CELLALGOSWITCH: LocalCellId=0, RanShareModeSwitch=ON,
OpResourceGroupShareSwitch=OpPrbGroupshareSwitch-0;
MOD CELLOP: LocalCellId=0, TrackingAreaId=0,
OperatorFunSwitch=OP_FAIR_SHARING_SWITCH-1;
//Configuring the PLMN broadcast mode in a cell
MOD CELLACCESS: LocalCellId=0, BroadcastMode=NORMAL_MODE;
//Configuring the traffic sharing mode
MOD LICRATIO: UpLicRatio=28, TrafficSharingType=DEDICATE;
//Configuring the licensed traffic proportion for each operator and the percentage of available
resources one operator can share with other operators
ADD LICRATIOSHAREPOLICY: CnOperatorId=0, TrfRatio=50, TrfSharingRatio=20;
//Configuring the proportion of RBs that each operator shares with other operators (using the
two operators sharing part of RBs as an example)
MOD CELLOP: LocalCellId=0, TrackingAreaId=0, RbSharingRatioWithOtherOp=10;
MOD CELLOP: LocalCellId=0, TrackingAreaId=1, RbSharingRatioWithOtherOp=10;
//Configuring whether to allow MMEs of different RAN sharing operators to have the same
MMEC
MOD GLOBALPROCSWITCH: DiffOpWithSameMmecSwitch=OFF;
//Configuring the eNodeB-specific ANR switch under RAN sharing
MOD ENODEBALGOSWITCH: RANSHARINGANRSWITCH=NBSLTERANSharingSwitch-1;
//Configuring the inter-PLMN handover switch
MOD ENODEBALGOSWITCH: HoAlgoSwitch=InterPlmnHoSwitch-1;
//Configuring the RAT-specific inter-PLMN handover switches
MOD CNOPERATOR: CnOperatorId=0, OperatorFunSwitch=INTRA_RAT_INTER_PLMN_HO_SW-

1&UTRAN_INTER_PLMN_HO_SW-1&GERAN_INTER_PLMN_HO_SW-
1&NR_INTER_PLMN_HO_SW-1;
//Configuring information for inter-PLMN handovers
ADD INTERPLMNHOLIST: CnOperatorId=0, TarMcc="460", TarMnc="30";
//Configuring a RAT/frequency priority group
ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=0, RatType=EUTRAN, DlEarfcn=3000;
//Configuring the RAT/frequency priority information (based on UE's SPID)
ADD SPIDCFG: Spid=1, RatFreqPriorityInd=CFG, RatFreqPriorityGroupId=0;
//Configuring the handover PLMN filtering optimization switch when the ANR function is
enabled in RAN sharing with common carrier mode
MOD CELLHOPARACFG:LocalCellId=0, CellHoAlgoSwitch=HoPlmnFilterOptSw-1;
ADD RatFreqPriorityGroup:RatFreqPriorityGroupId=0,RatType=EUTRAN, DlEarfcn=1234;
ADD CELLOP:LocalCellId=0, TrackingAreaId=1, RatFreqPriorityGroupId=0,
NsaDcRatFreqPriorityGrpId=1;
//When a UE of a secondary operator initiates a frequency-priority-based handover from an
MOCN cell to a cell of the secondary operator's PLMN, the handover is not controlled by the
MLB status of the target cell.
MOD CELLMLBHO:LocalCellId=0,
MlbMatchOtherFeatureMode=MocnSecOpUeFreqPriInHoEhnSw-1;
//Configuring a dedicated cell-reselection priority for a GERAN frequency (based on the serving
cell's PLMN)
ADD GERANNFGROUPSCELLOP: LocalCellId=0, BcchGroupId=0, CnOperatorID=0,
CellReselDediPriCfgInd=CFG, CellReselDediPri=1;
//Configuring a dedicated cell-reselection priority for a GERAN frequency (based on the
neighboring frequency's PLMN)
ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="02",
CellReselPriorityCfgInd=CFG, CellReselPriority=6;
//Configuring a dedicated cell-reselection priority for a UTRAN frequency (based on the serving
cell's PLMN)
ADD UTRANNFREQSCELLOP: LocalCellId=0, UtranDlArfcn=1234, CnOperatorID=0,
//Configuring a dedicated cell-reselection priority for a UTRAN frequency (based on the

ADD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=10800, Mcc="460", Mnc="02",
//Configuring a dedicated cell-reselection priority for an E-UTRAN frequency (based on the
serving cell's PLMN)
ADD EUTRANNFREQSCELLOP: LocalCellId=0, DlEarfcn=1234, CnOperatorID=0,
ADD EUTRANNFREQRANSHARE: LocalCellId=0, DlEarfcn=1234, Mcc="460", Mnc="01",
CellReselPriorityCfgInd=NOT_CFG;
//Configuring a dedicated cell-reselection priority for a CDMA frequency (based on the serving
cell's PLMN)
ADD CDMA2000BCSCELLOP: LocalCellId=0, BandClass=bc0, CnOperatorID=0,
HrpdCellReselDediPriCfgInd=NOT_CFG;
//Configuring a dedicated cell-reselection priority for an NR frequency (based on the serving
cell's PLMN)
ADD NRNFREQSCELLOP:LocalCellId=0, DlArfcn=620000, CnOperatorId=0,
CellReselPriorityConfigInd=CFG, CellReselPriority=3;
//Configuring the protocol message optimization switch when RAN sharing with common
carrier is enabled in both the E-UTRAN and GERAN cells
MOD GLOBALPROCSWITCH: ProtocolMsgOptSwitch=L2GPLMNChooseOptSwitch-1;
Fast batch activation

This function can be batch activated using the Feature Operation and Maintenance function of the
MAE-Deployment. For detailed operations, see the following section in the MAE-Deployment
product documentation or online help: MAE-Deployment Operation and Maintenance > MAE-
Deployment Guidelines > Enhanced Feature Management > Feature Operation and
Maintenance.
Single/Batch configuration
This function can be activated for a single base station or a batch of base stations on the MAE-
Deployment. For detailed operations, see Feature Configuration Using the MAE-Deployment.
Prerequisites
1. Based on the network plan, the eNodeB is shared between two operators that use common
carriers.
2. The transmission links between the eNodeB and EPCs are functioning normally.
3. Two UEs (UE 1 and UE 2) are ready. They respectively subscribe to services of the two operators.
Procedure
1. Check the cell status by running the following command:
DSP CELL:LOCALCELLID=0;
Expected result:
The value of Cell instance state is Normal, and the value of Cell PLMN Info contains multiple
PLMN IDs.
2. View the information contained in the SIB1 broadcast in the cell.

Expected result:
SIB1 contains the correct PLMN information about each operator.
In the GWCN architecture where the MME is shared, if information about a secondary
operator is not configured on the MME, the PLMN of this operator will not be carried in
the cell broadcast messages.
3. If "mcc" and "mnc" of the "plmn-Identity" fields in SIB1 are consistent with the operators' PLMNs,
PLMN information about the primary and secondary operators has been correctly sent in SIB1.
This indicates that the function has been activated successfully. In this example, the first PLMN
indicates the primary operator whose "plmn-Identity" field is "46001." The second PLMN indicates
the secondary operator whose "plmn-Identity" field is "46003."
systemInformationBlockType1
cellAccessRelatedInfo
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
MCC-MNC-Digit:0x4 (4)
mnc
cellReservedForOperatorUse:notReserved (1)
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
trackingAreaCode:0000000000100001(00 21)
cellIdentity:0000001100110001101000000000(03 31 A0 00)
4. Power on the two UEs to initiate attach procedures towards the shared cell.
Expected result:
In the "tAI" information element (IE) in the S1AP_INITIAL_UE_MSG message traced over each S1
interface, the values of "PLMNidentity" and "TAC" are consistent with the operator data. This
indicates that the UEs have successfully accessed the shared cell and selected the correct EPCs.
The path of the "tAI" IE is S1ap-
Msg\initiatingMessage\value\initialUEMessage\protocolIEs\SEQUENCE\value\tAI.
The values of "PLMNidentity" and "TAC" in the traced message are mapped to the eNodeB
configurations as follows. The PLMN ID 46001 is used as an example.
The MCC is 460 and MNC is F01 (F is added if there are fewer than three digits), which are
combined as 460F01. Then, each two adjacent digits exchange positions to get 64F010, which
is the value of "PLMNidentity" in the traced message.
The value of "TAC" is a hexadecimal number in the traced message.
In networks where RAN sharing with common carrier is enabled, some cell-level performance counters
can be monitored on a per operator basis. These counters are used to indicate whether the network key
performance indicators (KPIs) meet operators' requirements and whether proportion-based resource
sharing achieves the expected effect. Operators can use these counters for preliminary fault
demarcation and locating.
For details about operator-specific performance counters in FDD, see the Measurement of Operator-
specific Performance (Cell.Operator) and Measurement of Operator-specific Extended Performance
(Cell.Operator.Extension) function sets in 3900 & 5900 Series Base Station Performance Counter
5
Reference in 3900 & 5900 Series Base Station Product Documentation.
RAN Sharing with Dedicated Carrier
5.1 Principles
5.1.1 Overview
In RAN sharing with dedicated carrier, operators share eNodeBs but not cells. Only one PLMN ID is
broadcast in each cell. To enable RAN sharing with dedicated carrier, set the
ENodeBSharingMode.ENodeBSharingMode parameter to SEPARATED_FREQ.
RAN sharing with dedicated carrier is used when:
Each operator has their own spectrum resources but they jointly construct eNodeBs and share
eNodeB hardware.
One operator owns spectrum resources and provides certain frequencies to be used exclusively by
another operator.
Figure 5-1 illustrates the network architecture for RAN sharing with dedicated carrier where operators A
and B have their own spectrum and share only eNodeB hardware resources.
Figure 5-1 Network architecture for RAN sharing with dedicated carrier
Unlike RAN sharing with common carrier, RAN sharing with dedicated carrier allows operators to have
their exclusive cells. Therefore, the functions (idle mode management, mobility management in
connected mode, and air interface resource sharing between cells) dedicated to RAN sharing with
common carrier are not required in RAN sharing with dedicated carrier. RAN sharing with dedicated
carrier also differs from RAN sharing with common carrier in the following ways:
NE functions
OSS management
Multi-operator PKI
5.1.2 NE Functions
RAN sharing with dedicated carrier does not have special requirements for UEs because operators
have their exclusive cells and RAN sharing with dedicated carrier is transparent to UEs.
In MOCN mode, RAN sharing with dedicated carrier does not have special requirements for EPCs.
In GWCN mode, RAN sharing with dedicated carrier requires that the MME supports multiple
PLMNs and supports the sending of the IE Handover Restriction List to avoid X2- or S1-based
handover failures.
Cell-level features can be sold on a per cell basis. In RAN sharing with dedicated carrier, cells are
exclusively used by individual operators and therefore cell-level features can be sold on a per operator
basis.
eNodeB-level features are shared between operators and cannot be sold on a per operator basis.
Capacity management for RAN sharing with dedicated carrier is the same as that for RAN sharing with
common carrier. For details, see 4.1.5 Feature and Capacity Management.
This section describes the OSS management that only applies to RAN sharing with dedicated carrier
compared with RAN sharing with common carrier. For other aspects of OSS management that apply to
both RAN sharing modes, see OSS Management.
In RAN sharing with dedicated carrier, eRAN parameters are configured by an OM team. Cell-level
parameters are configured for each individual operator without the need of parameter negotiation
because each operator has a dedicated cell. However, eNodeB-level parameters must be configured
based on parameter negotiation result between operators.
Fault management in RAN sharing with dedicated carrier is the same as that in RAN sharing with
common carrier. For details, see Fault Management.
In RAN sharing with dedicated carrier, cell-level performance counters for individual operators can be
obtained because performance counters are measured on individual cells.
operators.
In RAN sharing with dedicated carrier, the S1 and X2 interfaces may be shared or not shared by
operators, with the transmission networking being different in these scenarios.
Transmission port planning in RAN sharing with dedicated carrier is the same as that in RAN sharing
with common carrier. For details, see 4.1.9.1 Transmission Port Planning.
For basic information about transmission link setup, see 4.1.9 Transmission Networking.
In RAN sharing with dedicated carrier, operators need to have their own transmission links (S1 and X2
links), as listed in Table 5-1 and Table 5-2.
Table 5-1 Dedicated or shared transmission link configuration in the control plane for RAN
sharing with dedicated carrier mode in different topologies

s
Control-plane link Dedicated Dedicated Dedicated
Table 5-2 Dedicated or shared transmission link configuration in the user plane for RAN
sharing with dedicated carrier mode in different topologies

s
User-plane link Dedicated Dedicated or shared Dedicated or shared
The transmission links can be created in endpoint or link mode.
Endpoint Mode
Table 5-3 Control-plane transmission link configuration in endpoint mode for RAN sharing
with dedicated carrier

s
S1 or X2 MO Configure a dedicated Configure a dedicated Configure a dedicated

S1 MO for each opera S1 MO for each opera X2 control plane MO
tor, and specify a uniq tor, and specify a uniq for each operator, spe
ue CpEpGroupId para ue CpEpGroupId par cify unique CpEpGro
meter for each MO. ameter for each MO. upId and SCTPHOST
MO for each X2 MO.
Local control plane Configure a single loc Configure a single loc Configure a dedicated
al S1 control-plane IP al S1 control-plane IP local X2 control-plane
address for the opera address for the opera

s
tors to share, or confi tors to share, or confi IP address for each o

gure a dedicated local gure a dedicated local perator.
S1 control-plane IP ad S1 control-plane IP a
dress for each operat ddress for each opera
or. tor.
Peer control plane Configure a dedicated Configure a single pe Configure a single pe

peer S1 control-plane er S1 control-plane IP er X2 control-plane IP
IP address for each o address for the opera address for the opera
perator. tors to share, or confi tors to share, or confi
gure a dedicated peer gure a dedicated peer
S1 control-plane IP a X2 control-plane IP a
ddress for each opera ddress for each opera
tor. tor.
In RAN sharing with dedicated carrier, if different operators share the same local X2 control-
plane IP address but are configured with different SCTP port numbers, there is a possibility that
only one SCTP link can be set up between the eNodeB in RAN sharing with dedicated carrier
and other eNodeBs. As a result, some UEs may fail to perform X2-based handovers. Therefore, it
is recommended that each operator be configured with a dedicated local X2 control-plane IP
address.
Table 5-4 User-plane transmission link configuration in endpoint mode for RAN sharing with
dedicated carrier

s

S1 MO for each opera S1 MO for each opera X2 MO for each oper
tor, and specify uniqu tor or configure a sin ator or configure a sin
e UpEpGroupId for e gle S1 MO for the op gle X2 MO for the op
ach MO. erators to share, and s erators to share, and s
pecify unique or the s pecify unique or the s
ame UpEpGroupId fo ame UpEpGroupId fo
r each MO. When diff r each MO.
erent UpEpGroupId
MOs are associated, t
he corresponding US
ERPLANEHOST MOs
must be different.

s
Local user plane Configure a single loc Configure a single loc Configure a single loc
al S1 user-plane IP ad al S1 user-plane IP ad al X2 user-plane IP ad
dress for the operator dress for the operator dress for the operator
s to share, or configur s to share, or configur s to share, or configur
e a dedicated local S1 e a dedicated local S1 e a dedicated local X2
user-plane IP address user-plane IP address user-plane IP address
for each operator. for each operator. for each operator.
When the local and p
eer user-plane IP addr
esses are shared, the
same user-plane EPG
ROUP must be config
ured.
Peer user plane Configure a dedicated Configure a single pe Configure a single pe

peer S1 user-plane IP er S1 user-plane IP ad er X2 user-plane IP ad
address for each oper dress for the operator dress for the operator
ator. s to share, or configur s to share, or configur
e a dedicated peer S1 e a dedicated peer X2
user-plane IP address user-plane IP address
for each operator. for each operator.
In RAN sharing with dedicated carrier, if the S1 objects of different operators are associated with
different UpEpGroupId but the same USERPLANEHOST MO, UEs may fail to access the
network.
Link Mode
Table 5-5 Control-plane transmission link configuration in link mode for RAN sharing with
dedicated carrier

s
Control plane Configure dedicated Configure dedicated Configure dedicated

S1Interface and SCT S1Interface and SCT X2Interface and SCT
PLNK MOs for each o PLNK MOs for each o PLNK MOs for each o
perator. perator. perator.
Table 5-6 User-plane transmission link configuration in link mode for RAN sharing with
dedicated carrier

s
User plane Configure a dedicated Configure a single IP Configure a single IP

IPPATH MO for each PATH MO for the ope PATH MO for the ope
operator. rators to share, or con rators to share, or con
figure a dedicated IP figure a dedicated IP
PATH MO for each op PATH MO for each op
erator. erator.
If a dedicated IPPATH If a dedicated IPPATH
MO is configured for MO is configured for
each operator, config each operator, config
ure CnOperatorIpPat ure CnOperatorIpPat
h MOs to define the h MOs to define the
mapping between the mapping between the
operators and the IP operators and the IP
paths. paths.
Dynamic sharing of uplink transmission bandwidth in RAN sharing with dedicated carrier is the same as
that in RAN sharing with common carrier. For details, see Dynamic Sharing of Uplink Transmission Bandwidth.
VLAN planning in RAN sharing with dedicated carrier is the same as that in RAN sharing with common
carrier. For details, see 4.1.9.4 VLAN Planning.
Multi-operator PKI in RAN sharing with dedicated carrier is the same as that in RAN sharing with
common carrier. For details, see 4.1.10 Multi-operator PKI.
5.2.1 Benefits
The benefits are the same as those provided by RAN sharing with common carrier. For details, see 4.2.1
Benefits.
5.2.2 Impacts
Network Impacts
None
Function Impacts
FDD Out-of-band re OutOfBandRelaySwi Relay When in-band relay and R

lay tch option of the Cell AN sharing with dedicated
AlgoSwitch.RelaySwitch carrier are both enabled, a
parameter ll resources of operators (i
ncluding the licensed traff
ic and RRC_CONNECTED
UE resources) can only be
completely shared, but no
t partly shared.
FDD In-band relay None Relay When in-band relay and R

AN sharing with dedicated
carrier are both enabled, a
ll resources of operators (i
ncluding the licensed traff
ic and RRC_CONNECTED
UE resources) can only be
completely shared, but no
t partly shared.
FDD Intelligent pow CellShutdown.CellShu Energy Conserv In RAN sharing scenarios,

ation and Emiss
er-off of carrier tdownSwitch set to ON ion Reduction the PLMN IDs of a capacit
s in the same c y cell must be a subset of
overage the PLMN IDs of its co-co
n.
FDD Multi-carrier c CellShutdown.CellShu Energy Conserv In RAN sharing scenarios,

ation and Emiss
oordinated ene tdownSwitch set to ON_ ion Reduction the PLMN IDs of a capacit
rgy saving MULTI_CARRIER_HIE y cell must be a subset of
R_SHUTDOWN or O the PLMN IDs of its co-co
N_MUL_CARR_HIER_ verage neighboring basic
MANUAL_SHUTDN cell. Otherwise, the capaci
n.
FDD Direct IPsec sel USERPLANEHOST.IPS X2 and S1 Self- Direct IPsec self-setup is in
Management in
f-setup ECSWITCH and SCTPH NSA Networking compatible with RAN Shar
OST.SIGIP1SECSWITCH S1 and X2 Self- ing.
Management
FDD Uplink single-si UlInterfSuppressCfg. Interference Det It is recommended that int

ection and Supp
de in-band int UlSingleSideIntrfImpMitSw ression erference detection and s
erference man uppression not be enable
agement d in RAN sharing scenario
s.
FDD Dynamic carrie CellPwrSavingAlgo.C Energy Conserv In RAN sharing scenarios,

ation and Emiss
r shutdown ph arrierDynShutdownPh2Sw ion Reduction the PLMN IDs of a capacit
ase 2 set to CAPACITY_CEL y cell must be a subset of
L the PLMN IDs of its co-co
n.
5.3 Requirements
5.3.1 Licenses
If the licensed value of RAN Sharing with Dedicated Carrier is 0, the RAN sharing with dedicated
FDD LOFD-001037 RAN Sharing with De LT1S00RSD per cell

dicated Carrier C00
5.3.2 Software

used.
h common carrie Mode.ENodeBShar nly one RAN sharing mod
r ingMode e.
FDD Hybrid RAN shar ENodeBSharing RAN Sharing Each operator supports o
ing Mode.ENodeBShar nly one RAN sharing mod
ingMode e.
nk Spectrum Sharing
Uplink Spectrum SpectrumCloudSwitc
h
Sharing
5.3.3 Hardware
Base Station Models
In FDD, the following base station models are compatible with this function:
For NB-IoT, the following base stations are compatible with this function:
Boards
No requirements
RF Modules
No requirements
5.3.4 Others
None
The transmission and interface data required in RAN sharing scenarios is similar to that in the
independent operator mode. The configurations vary depending on the network architecture in use.
For details, see 5.1.5 Transmission Networking and S1 and X2 Self-Management.
Scenario-specific data for RAN sharing with dedicated carrier can be configured based on information
provided in Cell Management and this section.
setup by SON h.X2SonSetupSwitch tch must be turned on in simplified endpoint mode.

Table 5-8 Parameters that must be set to configure the reference relationship between the X2
and EPGROUP MOs
Set this parameter to CP_UP_CFG when only both
control-plane and user-plane endpoints in the EP
GROUP MO are referenced in the configuration of
the X2 MO.
d Point Group ID
oint Group ID
n Release elease
Table 5-9 Parameters used for activation
Local tracking area ID CnOperatorTa.TrackingAreaId None
CN Operator ID CnOperatorTa.CnOperatorId None
Tracking area code CnOperatorTa.Tac None
Local tracking area ID CellOp.TrackingAreaId Only one parameter value ca

n be configured in each cell
where RAN sharing with dedi
cated carrier is enabled.
CN Operator ID CnOperator.CnOperatorId The CnOperator.CnOperatorId

parameter values must be dif
ferent between operators.
The parameter value for each
operator must be the same o
n all eNodeBs managed by th
e same OSS. The PLMN ID un
iquely identifies an operator
globally, which is composed
of the MCC and MNC.
CN Operator name CnOperator.CnOperatorName None
CN Operator type CnOperator.CnOperatorType Set this parameter to CNOPE

RATOR_PRIMARY or CNOPE
RATOR_SECONDARY based
on the contracts signed by th
e operators.
Mobile country code CnOperator.Mcc None
Mobile network code CnOperator.Mnc None
eNodeB sharing mode ENodeBSharingMode.ENodeB Set this parameter to SEPAR

SharingMode ATED_FREQ.
Different Operator With Sam GlobalProcSwitch.DiffOpWithS Set this parameter based on

e MMEC Switch ameMmecSwitch the network plan.
CN Operator ID LicenseSharingPolicy.CnOpera None

torId
The proportion of the maxim LicenseSharingPolicy.MaxUser Set this parameter based on

um number of users NumRate the network plan.
The proportion of the sharing LicenseSharingPolicy.UserNu Set this parameter based on

number of users mSharingRate the network plan.
User Number Sharing Group I LicenseSharingPolicy.UserNu None

D mSharingGroupId
Uplink Traffic License Ratio LicRatio.UpLicRatio Set this parameter based on

the network plan.
Traffic Sharing Type LicRatio.TrafficSharingType Set this parameter based on

the network plan.
CN Operator ID LicRatioSharePolicy.CnOperato None

rId
TrfRatio LicRatioSharePolicy.TrfRatio Set this parameter based on

the network plan.
TrfSharingRatio LicRatioSharePolicy.TrfSharing Set this parameter based on

Ratio the network plan.
eNodeBs can be reconfigured in batches on the MAE-Deployment or one by one on the GUI.
sharing with dedicated carrier mode. For example, if two operators are going to share eNodeB
hardware resources, the eNodeB sharing mode must be changed, a cell must be added, and the
related secondary-operator parameters must be set.
A secondary operator is added. For example, if a third operator is added to share eNodeB hardware
resources, a cell must be added and the related secondary-operator parameters must be set for
this operator.
operators that share eNodeB hardware resources, a cell and the related secondary-operator
configurations must be removed.
The sharing mode of an eNodeB is changed from the RAN sharing with dedicated carrier mode to
the independent operator mode.
sharing with dedicated carrier mode
LST APP command).





2. (Optional) LicRatio: Used to remove the configured traffic sharing mode in FDD.

Changing the sharing mode of an eNodeB from the RAN sharing with dedicated carrier mode to
the independent operator mode
1. (Optional) X2Interface: Used to remove the X2 interface. In FDD, if the X2 interface has been
configured and the base station mode is to be changed, the X2 interface configuration needs
to be deleted.


The following are command examples for function activation in FDD:

MOD ENODEBSHARINGMODE: ENodeBSharingMode=SEPARATED_FREQ;
//Configuring a transmission link in endpoint mode (X2 self-setup is used as an example)
UpEpGroupId=2;
//Configuring information related to RAN sharing with dedicated carrier

CellReservedForOp=CELL_NOT_RESERVED_FOR_OP;
RST APP: AID=1;
The following are command examples for function optimization in FDD:

Maintenance.
Prerequisites
Based on the network plan, the eNodeB is shared between two operators that use dedicated
carriers.
The transmission links between the eNodeB and EPCs are functioning normally.
Two UEs (UE 1 and UE 2) are ready. They respectively subscribe to services of the two operators.
Procedure
1. Check the cell status by running the following commands:
Expected result:
PLMN IDs.
2. View the information contained in SIB1 broadcasts in the cells.

Expected result:
For cell 0, if "mcc" and "mnc" of the "plmn-Identity" field in SIB1 are consistent with one
operator's PLMN, PLMN information about the primary operator has been correctly sent in SIB1.
This indicates that the function has been activated successfully. In this example, the "plmn-
Identity" field for cell 0 is "46001."
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellIdentity:0000001100110001101000000000(03 31 A0 00)
For cell 1, the "plmn-Identity" field in SIB1 is "46003."
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellIdentity:0000001100110001101000000001(03 31 A0 01)
3. Power on the two UEs to initiate attach procedures towards the respective cells.
Expected result:
In the "tAI" IE in the S1AP_INITIAL_UE_MSG message traced on each S1 interface, the values of
"PLMNidentity" and "TAC" are consistent with the operator data. This indicates that the UEs have
successfully accessed the respective cells and selected the correct EPCs. In this situation, the
function has been activated successfully. The path of the "tAI" IE is S1ap-
In networks where RAN sharing with dedicated carrier is enabled, cells are exclusively used by
individual operators. Therefore, all cell-level performance counters can be monitored on a per operator
basis. Operators can use these counters for preliminary fault demarcation and locating in the same way
6
as that in independent operator mode.
RAN Sharing with Special Dedicated Carrier (FDD)
6.1 Principles
6.1.1 Overview
In RAN sharing with special dedicated carrier, operators share eNodeB hardware resources, but not
spectrum resources. Only one PLMN ID is broadcast in cells of the primary operator. In cells of a
secondary operator, the PLMN IDs of both the primary operator in a reserved state and the secondary
operator are broadcast. To enable RAN sharing with special dedicated carrier, set the
ENodeBSharingMode.ENodeBSharingMode parameter to SEPARATED_FREQ_SPEC. RAN sharing with
special dedicated carrier is used during swapping of another vendor's devices on a network with
dedicated carriers.
A secondary operator can choose to allow or not allow spectrum resources in their cells to be used by
UEs subscribing to services of the primary operator. For ease of description, the two cases are defined
as case 1 and case 2 in subsequent descriptions as follows:
Case 1: The CellOp MO of the primary operator is not configured for cells of a secondary operator.
In this case, UEs subscribing to services of the primary operator are not allowed to use the
spectrum resources of the secondary operator.
Case 2: The CellOp MO of the primary operator must be configured for cells of a secondary
operator. The CellOp.CellReservedForOp parameter is set to CELL_RESERVED_FOR_OP and the
CnOperatorTa MO associated with the CellOp.TrackingAreaId parameter must be configured. In this
case, UEs subscribing to services of the primary operator are allowed to use the spectrum
resources of the secondary operator.
In RAN sharing with special dedicated carrier, the GWCN architecture only supports case 2.
When the MOCN and GWCN coexist, only case 2 is supported.
RAN sharing with special dedicated carrier is different from RAN sharing with common carrier or RAN
sharing with dedicated carrier in the following ways. The subsequent sections describe only the
differences.
Mobility management in connected mode
ANR management
OSS management
6.1.2 NE Functions
The NE functions required by RAN sharing with special dedicated carrier are the same as those required
by RAN sharing with common carrier. For details, see 4.1.2 NE Functions.
Idle mode management for RAN sharing with special dedicated carrier is different from that for RAN
sharing with common carrier or RAN sharing with dedicated carrier. This section describes only the
differences. For details about idle mode management, see Idle Mode Management.
Only one PLMN ID is broadcast in cells of the primary operator.

Two PLMN IDs are broadcast in cells of a secondary operator. For details, see 4.1.1 Overview.
EPC selection for RAN sharing with special dedicated carrier is the same as that for RAN sharing with
common carrier. For details, see 4.1.3.2 EPC Selection.
In RAN sharing with special dedicated carrier, cells are owned by specific operators and therefore, no
roaming fairness issue exists.
6.1.3.4 Paging
Paging for special dedicated carrier is the same as that for RAN sharing with common carrier. For
details, see 4.1.3.4 Paging.
6.1.3.5 Redirection
Redirection for special dedicated carrier is the same as that for RAN sharing with common carrier. For
details, see 4.1.3.5 Redirection.
When case 1 of RAN sharing with special dedicated carrier is used, you need to use the
EutranInterNFreq and EutranNFreqSCellOp MOs to configure the frequency of cells served by the
primary operator that meets the conditions below as a neighboring frequency for each cell of a
secondary operator. In addition, the frequency priority of cells served by the primary operator must be
higher than that of cells served by the secondary operator.
No CellOp MO is configured.
The broadcast PLMN ID is in the "reserved" state.
Other aspects of cell selection and reselection for RAN sharing with special dedicated carrier are the
same as those for RAN sharing with common carrier. For details, see 4.1.3.6 Cell Selection and Reselection.
When case 1 is selected, the primary operator's UE that is assigned AC11 or AC15 and is running
on HPLMN or EHPLMN will select a cell of a secondary operator as the candidate cell during cell
reselection. Therefore, if such a UE needs to be first migrated to a frequency of the primary

operator, EutranInterNFreq and EutranNFreqSCellOp of the primary operator must be
configured on cells of the secondary operators.
When RAN sharing with special dedicated carrier is enabled and the ADD_FREQ_CFG_SW option of
the GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is deselected, the InterPlmnHoSwitch
option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter must be deselected.
In case 1, UEs subscribing to services of the primary operator are prohibited from using the
spectrum resources of a secondary operator. Therefore, inter-PLMN intra-eNodeB handovers to
cells of the secondary operator are not possible for such UEs. When cells of a secondary operator
and those of the primary operator are not served by the same eNodeB, there will be no handovers
between them. This is because the frequencies of the former are not configured as neighboring
frequencies for the latter to establish any neighbor relationships.
In RAN sharing with special dedicated carrier, the PLMN used to configure external cells and add
inter-frequency neighbor relationships must be the one queried by running LST CNOPERATOR
with the CnOperator.CnOperatorType parameter set to CNOPERATOR_PRIMARY. In addition, the
MASTER_PLMN_RESERVED_FLAG option of the EutranExternalCell.AggregationAttribute parameter
must be selected for the primary PLMN of the secondary operator's cell in case 1.
When the HoPlmnFilterOptSw option of the CellHoParaCfg.CellHoAlgoSwitch parameter is

selected, intra-eNodeB inter-PLMN handovers are not allowed between cells of the primary
and secondary operators in case 1. If the neighboring cell is an inter-site cell and the
serving PLMN of the UE is the same as the primary PLMN of the target cell, the cell of the
secondary operator in RAN sharing with special dedicated carrier cannot be selected as the
target cell. If the MASTER_PLMN_RESERVED_FLAG option of the
EutranExternalCell.AggregationAttribute parameter is selected, the cell is a secondary-
operator cell.
Other aspects of mobility management in connected mode for RAN sharing with special dedicated
carrier are the same as those for RAN sharing with common carrier. For details, see 4.1.4 Mobility
Management in Connected Mode.
Cell-level features can be sold on a per cell basis. In RAN sharing with special dedicated carrier, cells are
exclusively used by individual operators and therefore cell-level features can be sold on a per operator
basis.
eNodeB-level features are shared between operators and cannot be sold on a per operator basis.
Capacity management for RAN sharing with special dedicated carrier is the same as that for RAN
sharing with common carrier. For details, see 4.1.5 Feature and Capacity Management.
RAN sharing with special dedicated carrier does not involve fair sharing of air interface resources or
operator-specific MLB within a cell.
ANR management for RAN sharing with special dedicated carrier is the same as that for RAN sharing
with common carrier. For details, see 4.1.7 ANR Management.
When swapping out another vendor's eNodeBs, perform the following operations on Huawei eNodeB if
the PLMN IDs broadcast in cells of another vendor do not comply with 3GPP specifications:
Disable ANR on any Huawei eNodeB adjacent to the other vendor's eNodeB.
Manually configure neighbor relationships for Huawei eNodeB.
Set the ECGI of the neighboring cell to a value that contains the PLMN of the primary operator.
In RAN sharing with special dedicated carrier, all of the operators can share the OSS, which manages
NEs on the eRAN and connects to operators' upper-layer NMSs through their own Itf-N interfaces.
Configuration, fault, and performance management data can be reported over the Itf-N interface of the
OSS on a per cell and operator basis.
Configuration management for RAN sharing with special dedicated carrier is the same as that for RAN
sharing with dedicated carrier. For details, see 5.1.4.1 Configuration Management.
Fault management for RAN sharing with special dedicated carrier is the same as that for RAN sharing
with common carrier. For details, see 4.1.8.2 Fault Management.
In RAN sharing with special dedicated carrier, cell-level performance counters for cells of the primary
operator or the secondary operator in case 1 can be obtained on a per operator basis because cells are
owned by specific operators.
Some key performance counters can be collected on a per operator basis for cells of the secondary
operator in case 2.
operators.
In RAN sharing with special dedicated carrier, the GWCN architecture requires that the S1 links of the
primary operator be used on any shared MME. The same requirement applies when the MOCN and
GWCN architectures coexist.
In RAN sharing with special dedicated carrier, operator-specific virtual routing and forwarding (VRF)
must be planned if operators need to isolate transmission.
Other networking scenarios for RAN sharing with special dedicated carrier are the same as those for
RAN sharing with common carrier. For details, see 4.1.9 Transmission Networking.
Multi-operator PKI for RAN sharing with special dedicated carrier is the same as that for RAN sharing
with common carrier. For details, see 4.1.10 Multi-operator PKI.
6.2.1 Benefits
RAN sharing with special dedicated carrier increases the handover success rate during inter-vendor
device swapping. This is because there will be no handover failures between adjacent inter-vendor
eNodeBs caused by incorrect neighbor relationships.
Other benefits are the same as those provided by RAN sharing with common carrier. For details, see
4.2.1 Benefits.
6.2.2 Impacts
Network Impacts
RAN sharing with special dedicated carrier increases the handover success rate during inter-vendor
device swapping. This is because there will be no handover failures between adjacent inter-vendor
eNodeBs caused by incorrect neighbor relationships.
Function Impacts

ation and Emiss
n.
Management in
Management
FDD Uplink Single-S UlInterfSuppressCfg. Interference Det It is recommended that int

ection and Supp
ide In-Band Int UlSingleSideIntrfImpMitSw ression erference detection and s
erference Man uppression not be enable
s.
6.3 Requirements
6.3.1 Licenses
If the licensed value of RAN Sharing with Dedicated Carrier is 0, the RAN sharing with dedicated
FDD LOFD-001037 RAN Sharing wit LT1S00RSDC00 per Cell

h Dedicated Carr
ier
6.3.2 Software
Function Name Function Switch Reference Description
S1-flex None S1-flex This function is requir

ed if the MOCN archi
tecture is used.
RAN sharing with co ENodeBSharingMod RAN Sharing Each operator suppor

mmon carrier e.ENodeBSharingMode ts only one RAN shari
ng mode.
Hybrid RAN sharing ENodeBSharingMod RAN Sharing Each operator suppor

e.ENodeBSharingMode ts only one RAN shari
ng mode.
Out-of-band relay OutOfBandRelaySwi Relay Out-of-band relay do

tch option of the Cell es not apply to multi-
AlgoSwitch.RelaySwitc operator scenarios.
h parameter
In-band relay None Relay In-band relay does no

t apply to multi-oper
ator scenarios.
6.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
6.3.4 Others
None
setup by SON h.X2SonSetupSwitch tch must be turned on in simplified endpoint mode.

pe
Switch.X2SonSetupSwitch parameter is set to ON.
Table 6-2 Parameters that must be set to configure the reference relationship between the X2
and EPGROUP MOs
Set this parameter to CP_UP_CFG when both contr
ol-plane and user-plane endpoints in the EPGROU
P MO are referenced in the configuration of the X
2 MO.
d Point Group ID
oint Group ID
n Release elease
Table 6-3 and Table 6-4 describe the parameters used for function activation and optimization,
respectively.

ea ID ackingAreaId

nOperatorId
Tracking area co CnOperatorTa.Ta In a cell where RAN sharing with special dedicated carr
de c ier is enabled, configure the same TAC for all operator
s.
Local tracking ar CellOp.TrackingAr In a cell where case 1 of RAN sharing with special dedi
ea ID eaId cated carrier is used, only one TrackingAreaId can be
configured.
When case 2 of RAN sharing with special dedicated ca
rrier is used, only one TrackingAreaId instance can be
configured in a cell of the primary operator. In a cell of
a secondary operator, two TrackingAreaId instances
must be configured and the corresponding CnOperat
orTa.CnOperatorId parameters must be set to different v
alues with one being set to the ID of the primary oper
ator. In addition, the CellOp.CellReservedForOp paramete
r of the primary operator must be set to CELL_RESERV
ED_FOR_OP.
When the GWCN architecture is used, only case 2 of R
AN sharing with special dedicated carrier is supported.
That is, the CellOp MO of the primary operator must b
e configured for cells of a secondary operator and the
CnOperatorTa MO associated with the CellOp.Tracking
AreaId parameter must be configured.
Cell reserved for CellOp.CellReserv When case 2 of RAN sharing with special dedicated ca
operator edForOp rrier is used, the CellOp.CellReservedForOp parameter of
the primary operator configured for a cell of a second
ary operator must be set to CELL_RESERVED_FOR_OP.
CN Operator ID CnOperator.CnO By default, one eNodeB can be configured with data f

peratorId or up to four operators, whose CnOperator.CnOperatorI
d values must be different.

me peratorName
CN Operator typ CnOperator.CnO Set this parameter to CNOPERATOR_PRIMARY or CN

e peratorType OPERATOR_SECONDARY based on the contracts sign
ed by the operators.

ode

code
eNodeB sharing ENodeBSharing Set this parameter to SEPARATED_FREQ_SPEC.

ingMode
Table 6-4 Parameters used for optimization
CN Operator I LicenseSharin None None

D gPolicy.CnOpera
torId
The proportion LicenseSharin None Set this parameter based on the network pl
of the maximu gPolicy.MaxUser an.
m number of u NumRate
sers
The proportion LicenseSharin None Set this parameter based on the network pl
of the sharing gPolicy.UserNu an.
number of user mSharingRate
s
Uplink Traffic Li LicRatio.UpLicR None Set this parameter based on the network pl
cense Ratio atio an.
Traffic Sharing LicRatio.TrafficS None Set this parameter based on the network pl
Type haringType an.
CN Operator I LicRatioShare None None

D Policy.CnOperat
orId
TrfRatio LicRatioShare None Set this parameter based on the network pl

Policy.TrfRatio an.
TrfSharingRati LicRatioShare None Set this parameter based on the network pl

o Policy.TrfSharing an.
Ratio
Different Oper GlobalProcSwi None Set this parameter based on the network pl
ator With Sam tch.DiffOpWithSa an.
e MMEC Switc meMmecSwitch
Handover Algo ENodeBAlgoS InterPlmnHo Deselect this option.

switch witch.HoAlgoSwi Switch
tch
X2-based Neig GlobalProcSwi ADD_FREQ_C Deselect this option.

hboring Cell C tch.X2BasedUptN FG_SW
onfiguration U cellCfgSwitch
pdate Switch
Local cell ID EutranNFreqS None None

CellOp.LocalCell
Id
Downlink EARF EutranNFreqS None None

CN CellOp.DlEarfcn
Cn operator ID EutranNFreqS None Set this parameter to the same value as the
CellOp.CnOperat CN Operator ID parameter in the CnOpera
orID tor MO.
Cell reselection EutranNFreqS None When case 1 of RAN sharing with special d
dedicated prior CellOp.CellResel edicated carrier is used, the frequency of th
ity configure in DediPriCfgInd e primary operator for which no CellOp M
dicator O is configured and the "reserved" status is
broadcast must be configured as a neighbo
ring frequency in each cell of a secondary o
perator.
Cell reselection EutranNFreqS None None

dedicated prior CellOp.CellResel
ity DediPri
Local cell ID EutranInterNF None None

req.LocalCellId
Downlink EARF EutranInterNF None When RAN sharing with special dedicated c
CN req.DlEarfcn arrier is used, the neighboring frequencies
of a cell of the primary operator cannot be
set to the frequencies of cells of a secondar
y operator.
When case 1 of RAN sharing with special d
edicated carrier is used, the frequency of th
e primary operator for which no CellOp M
O is configured and the "reserved" status is
broadcast must be configured as a neighbo
ring frequency in each cell of a secondary o
perator.
Inter frequency EutranInterNF None Set this parameter to CFG.

cell resel priori req.CellReselPrio
ty configure in rityCfgInd
dicator
Inter frequency EutranInterNF None None

cell resel priori req.CellReselPrio
ty rity
Handover Algo CellHoParaCf HoPlmnFilte Set this parameter based on the network pl
Switch g.CellHoAlgoSwit rOptSw an.
ch
Aggregation A EutranExterna MASTER_PL Set this parameter based on the network pl

ttribute lCell.Aggregation MN_RESERV an.
Attribute ED_FLAG
the GUI.
sharing with special dedicated carrier mode. For example, if two operators are going to share RAN
resources in RAN sharing with special dedicated carrier mode, the eNodeB sharing mode must be
changed, a cell must be added, and the related secondary-operator parameters must be set.
A secondary operator is added. For example, if a third operator is added to share RAN resources in
RAN sharing with special dedicated carrier mode, a cell must be added and the related secondary-
operator parameters must be set for this operator.
operators that share RAN resources in RAN sharing with special dedicated carrier mode, a cell and
the related secondary-operator configurations must be removed.
The sharing mode of an eNodeB is changed from the RAN sharing with special dedicated carrier
mode to the independent operator mode.
sharing with special dedicated carrier mode
LST APP command).



3. (Optional) CnOperatorTa: Used to add tracking area information.


3. (Optional) CellOp: Used to remove the cell operator information.

Changing the sharing mode of an eNodeB from the RAN sharing with special dedicated carrier
mode to the independent operator mode
1. (Optional) X2Interface: Used to remove the X2 interface. In FDD, if the X2 interface has been
configured and the base station mode is to be changed, the X2 interface configuration needs
to be deleted.



MOD ENODEBSHARINGMODE: ENodeBSharingMode=SEPARATED_FREQ_SPEC;

//Configuring transmission links in endpoint mode. Note that the GWCN architecture requires
that the S1 links of the primary operator be used on all MMEs. When the MOCN and GWCN
architectures coexist, any shared MME must use the S1 links of the primary operator. To fulfill
the requirements, set the CpEpGroupId parameter only for the S1 MO of the primary operator
when the GWCN architecture is used.
UpEpGroupId=0;
//Configuring a transmission link in end point configuration mode (X2 self-setup is used as an
example)
UpEpGroupId=2;
//Configuring transmission links in link mode. Note that the GWCN architecture requires that
the S1 links of the primary operator be used on all MMEs. When the MOCN and GWCN
architectures coexist, any shared MME must use the S1 links of the primary operator. To fulfill
the requirements, set the CnOperatorId parameter only for the S1INTERFACE MO of the primary
operator when the GWCN architecture is used.
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0;
ADD X2INTERFACE: X2InterfaceId=0, X2CpBearerId=0, CnOperatorId=0;
//Performing the following configuration when case 1 of RAN sharing with special dedicated
carrier is used
//Performing the following configuration when case 2 of RAN sharing with special dedicated
carrier is used
ADD CELLOP: LocalCellId=1, TrackingAreaId=0, CellReservedForOp=CELL_RESERVED_FOR_OP;
RST APP: AID=1;
UserNumSharingRate=0;
UserNumSharingRate=0;
MMEC
//Configuring inter-PLMN handovers
//Configuring whether to add frequencies based on received X2 messages
MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=ADD_FREQ_CFG_SW-0;
//Performing this step for the cell of a secondary operator when case 2 of RAN sharing with
special dedicated carrier is used
ADD CELLOP: LocalCellId=1, TrackingAreaId=1, CellReservedForOp=CELL_RESERVED_FOR_OP;
ADD EUTRANINTERNFREQ: LocalCellId=1, DlEarfcn=1234, CellReselPriorityCfgInd=CFG,
CellReselPriority=3, MeasBandwidth=MBW75;
//Performing this step to filter out cells of secondary operators in RAN sharing with special
dedicated carrier
MOD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=255, CellId=1, DlEarfcn=3000,
AggregationAttribute=MASTER_PLMN_RESERVED_FLAG-1;

Maintenance.
Prerequisites
1. Based on the network plan, the eNodeB is shared between two operators that use case 1 of RAN
sharing with special dedicated carrier.
3. Two UEs (UE 1 and UE 2) are ready. They respectively subscribe to services of the two operators.
Procedure
Expected result:
PLMN IDs.

Expected result:
For cell 0, if "mcc" and "mnc" of the "plmn-Identity" field in SIB1 are consistent with one
operator's PLMN, PLMN information about the primary operator has been correctly sent in SIB1.
This indicates that the function has been activated successfully. In this example, the "plmn-
Identity" field for cell 0 is "46001."
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellIdentity:0000001100110001101000000000(03 31 A0 00)
In SIB1 of cell 1, the "plmn-Identity" field is "46001" and the status is "Reserved" for the primary
operator and the "plmn-Identity" field is "46003" for the secondary operator.
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellReservedForOperatorUse:Reserved (0)
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellIdentity:0000001100110001101000000001(03 31 A0 01)
3. Power on UE 1 and UE 2 to initiate attach procedures towards the shared cell.

Expected result:
successfully accessed the respective cells and selected the correct EPCs. In this situation, the
function has been activated successfully. The path of the "tAI" IE is S1ap-
In networks where RAN sharing with special dedicated carrier is enabled, cells of the primary operator
and a secondary operator in case 1 are exclusively used by individual operators. Therefore, all cell-level
performance counters can be monitored on a per operator basis. Operators can use these counters for
preliminary fault demarcation and locating in the same way as that in independent operator mode.
For cells of a secondary operator in case 2, some cell-level performance counters can be monitored on
a per operator basis. These counters are used to indicate whether the network KPIs meet operators'
requirements and whether proportion-based resource sharing achieves the expected effect. Operators
can use these counters for preliminary fault demarcation and locating. RAN sharing with special
dedicated carrier and RAN sharing with common carrier use the same operator-specific counters. For
7
details about these counters, see 5.4.3 Network Monitoring.
Hybrid RAN Sharing
7.1 Principles
7.1.1 Overview
In hybrid RAN sharing, operators share eNodeB hardware resources. They can choose to share
spectrum resources or keep spectrum resources for their own use. In a shared cell, multiple PLMN IDs
are broadcast, including the primary operator's and secondary operators' PLMN IDs. The primary
operator's PLMN ID can be different between cells. To enable hybrid RAN sharing, set the
ENodeBSharingMode.ENodeBSharingMode parameter to HYBRID_SHARED.
Hybrid RAN sharing is typically used in the following scenarios:
Scenario 1: One operator shares some of its spectrum resources with other operators. Other
spectrum resources are still exclusively used by this operator. The primary PLMNs of the shared and
the non-shared spectrum resources are different.
Figure 7-1 shows the network architecture for hybrid RAN sharing where operators A and B have
their own spectrum resources and share eNodeB hardware resources and some of the spectrum
resources. Frequency 1 (f1) is shared by operators A and B, with A being the primary operator and
B being the secondary one. Frequency 2 (f2) is exclusively used by operator B.
In this scenario, there are two RAN sharing groups: operators (A and B) and operator B. Each RAN
sharing group must have a unique primary operator. The secondary operators can be the same.
Figure 7-1 Network architecture for hybrid RAN sharing (1)
Scenario 2: Operators co-construct and share a RAN. Different operators share different spectrum
resources.
Figure 7-2 shows the network architecture for hybrid RAN sharing where operators A, B, C, and D
share eNodeB hardware resources and different spectrums. f1 is shared by operators A and B, while
f2 is shared by operators C and D. Operators (A and B) and operators (C and D) are members of
different RAN sharing groups.
Figure 7-2 Network architecture for hybrid RAN sharing (2)
To conclude, all the following conditions must be met before hybrid RAN sharing is enabled:
An eNodeB has two or more frequencies.
At least one frequency is shared by operators.

Two or more frequencies have different primary PLMNs.
The eNodeB working in the hybrid RAN sharing mode provides the following functions based on the
instruction from RAN sharing operator groups:
Broadcasting information about primary and secondary operators.
Setting up proper transmission links.
Hybrid RAN sharing enables flexible resource sharing for operators.
Compared with RAN sharing with common carrier, hybrid RAN sharing allows the primary PLMN ID
to be different between cells.
Compared with RAN sharing with dedicated carrier, hybrid RAN sharing allows operators to share
the same cell.
Hybrid RAN sharing is different from RAN sharing with common carrier or RAN sharing with dedicated
carrier in the following ways. The subsequent sections describe only the differences.
NE functions
ANR management
OSS management
7.1.2 NE Functions
Some NEs in hybrid RAN sharing have specific functions and configurations, besides all functions in
RAN sharing with common carrier and RAN sharing with dedicated carrier. This section describes the
NE functions and configurations specific to hybrid RAN sharing.
UE
Functions of a UE are the same as those in RAN sharing with common carrier. For details, see 4.1.2 NE
Functions.
eNodeB
To support hybrid RAN sharing, an eNodeB must support all functions in RAN sharing with common
carrier and RAN sharing with dedicated carrier, and also must be able to:
Support the hybrid RAN sharing configurations.
Support a maximum of four operators in a shared eNodeB and broadcast of a maximum of four
PLMN IDs in a shared cell under the control of the Hybrid RAN Sharing license.
Broadcast the PLMN ID information for a shared cell based on the carrier-sharing operator group
to which the cell belongs.
Set up transmission links on a per carrier-sharing operator group basis.
MME
Functions of an MME are the same as those in RAN sharing with common carrier. For details, see 4.1.2
NE Functions.
Idle mode management for hybrid RAN sharing is different from that for RAN sharing with common
carrier and RAN sharing with dedicated carrier. This section only describes the differences. For details
about idle mode management, see Idle Mode Management.
Multiple PLMN IDs are broadcast in a shared cell where hybrid RAN sharing is enabled.
The primary PLMN IDs of the cells may be different. The primary and secondary PLMN IDs are specified
by the parameters CnOpSharingGroup.PrimaryOperatorId and
CnOpSharingGroup.SecondaryOperatorList, respectively. In addition, the Cell.CnOpSharingGroupId
parameter associates a cell with a RAN sharing operator group. A cell broadcasts information about the
primary and secondary operators as instructed by the RAN sharing operator group. According to
section 6.2.2 "Message definitions" in 3GPP TS 36.331 V8.5.0, the primary PLMN ID is the one at the top
of the broadcast PLMN ID list and also the PLMN ID in the global eNodeB ID and ECGI. The primary
operator does not have any privileges of using eNodeB resources.
After a UE is powered on in a cell enabled with hybrid RAN sharing, it learns of multiple PLMNs after
listening to the PLMN list in SIB1 broadcast by this cell. Based on the configuration information in the
USIM and recorded historical information, the UE selects one of them as its serving PLMN according to
the selection rules specified in section 4.4 "PLMN selection process" in 3GPP TS 23.122 V8.5.0.
After the UE selects an PLMN, it notifies the eNodeB of the selected PLMN through the RRC
Connection Setup Complete message.
The eNodeB then selects the corresponding S1 interface and connects to the EPC based on the PLMN
ID selected by the UE and the carrier-sharing operator group to which the serving cell belongs.
In a non-shared cell, only one PLMN ID is contained in cell broadcast information. The UE selects the S1
interface and the EPC based on the broadcast PLMN ID and the carrier-sharing operator group to
which the serving cell belongs.
Fairness guarantee for roaming for shared cells in hybrid RAN sharing is the same as that in RAN
sharing with common carrier. For details, see 4.1.3.3 Fairness Guarantee for Roaming.
Non-shared cells are not involved in fairness guarantee for roaming because a non-shared cell is
exclusively owned by a specific operator.
7.1.3.4 Paging
When hybrid RAN sharing is used, TACs are planned at the cell level.
Shared cells
You are advised to plan MMECs based on each operator's EPC. The MME's MMEC must be unique
in a TAC. The MMECs of different operators must be negotiated to ensure this requirement is met.
Otherwise, MMEC conflicts may occur.
Non-shared cells
Plan an MMEC for the operator if the operator does not own any shared cell.
In hybrid RAN sharing, operators in a shared cell can be configured with the same MMEC if paging
errors due to MMEC conflicts are acceptable. For details, see 4.1.3.4 Paging.
7.1.3.5 Redirection
Redirection in hybrid RAN sharing is the same as that in RAN sharing with common carrier. For details,
see 4.1.3.5 Redirection.
Cell selection and reselection in hybrid RAN sharing is the same as that in RAN sharing with common
carrier. For details, see 4.1.3.6 Cell Selection and Reselection.
Mobility management in connected mode in hybrid RAN sharing is the same as that in RAN sharing
with common carrier. For details, see 4.1.4 Mobility Management in Connected Mode.
In hybrid RAN sharing, UEs are handed over between different RAN sharing operator
groups over the S1 interface.
In hybrid RAN sharing, if a Huawei eNodeB is connected to a non-Huawei core network and
the INTER_RAN_SHR_GRP_REEST_SWITCH option of the
GlobalProcSwitch.RrcReestOptSwitch parameter is selected, it is recommended that the
INTER_RAN_SHR_GRP_REEST_OPT_SW option of the GlobalProcSwitch.RrcReestOptSwitch
parameter be selected. The latter option is used to control whether the eNodeB sends a
Path Switch Request message to the core network after an RRC connection is reestablished
upon an intra-eNodeB inter-RAN-sharing-group handover. After this option is selected, if
the UE experiences an intra-eNodeB inter-RAN-sharing-group handover again, the
handover success rate increases.
In hybrid RAN sharing, a license purchase order is placed by only one party, who can be the primary
operator or a joint venture of multiple operators. Each eNodeB still has only one license file, which
specifies the total licensed limits for all RAN sharing operators, not for a specific operator.
Cell-level features can be sold on a per cell basis. In a non-shared cell, cell-level features can be sold on
a per operator basis.
In a shared cell, the licenses for cell-level features are shared by operators and therefore cannot be sold
on a per operator basis.
eNodeB-level features are shared by operators and therefore cannot be sold on a per operator basis.
7.1.5.2 Capacity Control
Capacity management in hybrid RAN sharing is the same as that in RAN sharing with common carrier.
For details, see 4.1.5.2 Capacity License.
Fair sharing of air interface resources and operator-specific MLB for shared cells in hybrid RAN sharing
are the same as those in RAN sharing with common carrier. For details, see 4.1.6 Air Interface Resource
Management.
Non-shared cells are not involved in fair sharing of air interface resources or intra-cell operator-specific
MLB because air interface resources are exclusively used by such cells.
ANR management in hybrid RAN sharing is the same as that in RAN sharing with common carrier. For
details, see 4.1.7 ANR Management.
All of the operators can share the OSS, which manages NEs on the eRAN and connects to operators'
upper-layer NMSs through their own Itf-N interfaces.
Configuration, fault, and performance management data can be reported over the Itf-N interface of the
OSS on a per cell and operator basis.
In hybrid RAN sharing, eRAN parameters are configured by an OM team. Configuration management
for a shared cell in hybrid RAN sharing requires parameter negotiation result between operators that
share the cell. Configuration management for a non-shared cell in hybrid RAN sharing is implemented
by the operator that owns the non-shared cell.
Configuration management for eNodeB-level common information must be negotiated by all
operators.
Fault management in hybrid RAN sharing is the same as that in RAN sharing with common carrier. For
details, see 4.1.8.2 Fault Management.
In shared cells, the values of some key counters can be collected specifically for different operators.
In non-shared cells, the values of cell-level counters are collected specifically and operators can be
distinguished based on specific cells.
operators.
The MME or eNodeB identifies a peer eNodeB using the global eNodeB ID corresponding to the
control-plane transmission link. Therefore, a global eNodeB ID is required to set up a control-plane
transmission link. Under an eNodeB, there is a one-to-one mapping between the carrier-sharing
operator groups and the global eNodeB IDs. In hybrid RAN sharing, the control-plane transmission
links are set up based on the carrier-sharing operator groups and transmission networking requires
special treatment.
Transmission port planning in hybrid RAN sharing is the same as that in RAN sharing with common
carrier. For details, see 4.1.9.1 Transmission Port Planning.
For basic information about transmission link setup, see 4.1.9 Transmission Networking.
In hybrid RAN sharing, operator-specific virtual routing and forwarding (VRF) must be planned if
operators need to isolate transmission.
In hybrid RAN sharing, operators need to select a proper mode for setting up the transmission links (S1
and X2 links) based on network architectures. The transmission links can be created in endpoint or link
mode.
Endpoint Mode
Table 7-1 Dedicated or shared transmission link configuration in endpoint mode for hybrid
RAN sharing

s
Control-plane link be Dedicated Dedicated Dedicated

tween carrier-sharing
operator groups
Control-plane link wi Dedicated Shared Shared

thin one carrier-shari

s
ng operator group

s
User-plane link betw Dedicated Dedicated or shared Dedicated or shared

een carrier-sharing o
perator groups
User-plane link withi Dedicated Dedicated or shared Dedicated or shared

n one carrier-sharing
operator group
Configurations for carrier-sharing operator groups

Table 7-2 Control-plane transmission link configuration in endpoint mode for hybrid RAN
sharing between carrier-sharing operator groups

s
Control-plane S1 or Configure a dedicated Configure a dedicated Configure a dedicated

X2 MO S1 MO for each carrie S1 MO for each carrie X2 MO for each carrie
r-sharing operator gr r-sharing operator gr r-sharing operator gr
oup, and specify a uni oup, and specify a uni oup, and specify a uni
que CpEpGroupId pa que CpEpGroupId pa que CpEpGroupId pa
rameter for each MO. rameter for each MO. rameter for each MO.
Specify a same SCTP
HOST MO for differe
nt CpEpGroupId para
meters within a carrie
r-sharing operator gr
oup. Specify a unique
SCTPHOST MO for ea
ch carrier-sharing ope
rator group.
Local control plane Configure a dedicated Configure a dedicated Configure a dedicated

local S1 control-plane local S1 control-plane local X2 control-plane
IP address for each ca IP address for each ca IP address for each ca
rrier-sharing operator rrier-sharing operator rrier-sharing operator
group, or configure a group, or configure a group.
single local S1 control single local S1 control
-plane IP address for t -plane IP address for t
he carrier-sharing ope he carrier-sharing ope
rator groups to share. rator groups to share.

s
Peer control plane Configure a dedicated Configure a dedicated Configure a dedicated

peer S1 control-plane peer S1 control-plane peer X2 control-plane
IP address for each ca IP address for each ca IP address for each ca
rrier-sharing operator rrier-sharing operator rrier-sharing operator
group. group, or configure a group, or configure a
single peer S1 control single peer X2 control
-plane IP address for t -plane IP address for t
he carrier-sharing ope he carrier-sharing ope
rator groups to share. rator groups to share.
In hybrid RAN sharing, if different carrier-sharing operator groups share the same local X2
control-plane IP address but are configured with different SCTP port numbers, there is a
possibility that the SCTP link setup fails during X2-C self-setup between the eNodeB in hybrid
RAN sharing and other eNodeBs. Therefore, it is recommended that each carrier-sharing
operator group be configured with a dedicated local X2 control-plane IP address.
Table 7-3 User-plane transmission link configuration in endpoint mode for hybrid RAN
sharing between carrier-sharing operator groups

s
User-plane S1 or X2 Configure a dedicated Configure a dedicated Configure a dedicated

MO S1 MO for each carrie S1 MO for each carrie X2 MO for each carrie
r-sharing operator gr r-sharing operator gr r-sharing operator gr
oup, and specify a uni oup, or configure a si oup, or configure a si
que UpEpGroupId pa ngle S1 MO for the ca ngle X2 MO for the c
rameter for each MO. rrier-sharing operator arrier-sharing operato
groups to share. Speci r groups to share. Spe
fy a unique or use the cify a unique or use t
same UpEpGroupId p he same UpEpGroupI
arameter for each M d parameter for each
O. When different Up MO.
EpGroupId MOs are a
ssociated, the corresp
onding USERPLANEH
OST MOs must be dif
ferent.
Local user plane Configure a dedicated Configure a dedicated Configure a dedicated

local S1 user-plane IP local S1 user-plane IP local X2 user-plane IP
address for each carri address for each carri address for each carri

s
er-sharing operator g er-sharing operator g er-sharing operator g

roup, or configure a si roup, or configure a si roup, or configure a si
ngle local S1 user-pla ngle local S1 user-pla ngle local X2 user-pla
ne IP address for the ne IP address for the ne IP address for the
carrier-sharing operat carrier-sharing operat carrier-sharing operat
or groups to share. or groups to share. or groups to share.
When the local and p
eer user-plane IP addr
esses are shared, the
same user-plane EPG
ROUP must be config
ured.
Peer user plane Configure a dedicated Configure a dedicated Configure a dedicated

peer S1 user-plane IP peer S1 user-plane IP peer X2 user-plane IP
address for each carri address for each carri address for each carri
er-sharing operator g er-sharing operator g er-sharing operator g
roup. roup, or configure a si roup, or configure a si
ngle peer S1 user-pla ngle peer X2 user-pla
ne IP address for the ne IP address for the
carrier-sharing operat carrier-sharing operat
or groups to share. or groups to share.
In hybrid RAN sharing, if the S1 objects of different carrier-sharing operator groups are
associated with different UpEpGroupId but the same USERPLANEHOST MO, UEs may fail to
access the network.
Configurations for each carrier-sharing operator group

Table 7-4 Control-plane transmission link configuration in endpoint mode for hybrid RAN
sharing within a carrier-sharing operator group

s
S1 or X2 MO Configure a dedicated Configure an S1 MO f If the peer operat

S1 MO for each opera or the operators to sh ors are within the
tor within a carrier-sh are within a carrier-sh same carrier-shari
aring operator group, aring operator group. ng operator grou
and specify a unique p, configure the s
CpEpGroupId param ame X2 control-pl
eter for each MO. ane link for them
to share.

s
If the peer operat

ors are not in the
same carrier-shari
ng operator grou
p, they use differe
nt X2 control-pla
ne links. Configur
e a unique CpEp
GroupId paramet
er for each MO.
Local control plane Configure a single loc Configure a local S1 c Configure a local X2 c
al S1 control-plane IP ontrol-plane IP addre ontrol-plane IP addre
address for the opera ss for the operators t ss for the operators t
tors to share within a o share within a carrie o share within a carrie
group. r-sharing operator gr r-sharing operator gr
oup. oup.
Peer control plane Configure a dedicated Configure a peer S1 c If the peer operat
peer S1 control-plane ontrol-plane IP addre ors are within the
IP address for each o ss for the operators t same carrier-shari
perator within a grou o share within a carrie ng operator grou
p. r-sharing operator gr p, configure the s
oup. ame peer X2 cont
rol-plane IP addre
ss for them to sha
re.
If the peer operat
ors are not in the
same carrier-shari
ng operator grou
p, configure a de
dicated peer X2 c
ontrol-plane IP a
ddress for each o
perator within a g
roup.
Table 7-5 User-plane transmission link configuration in endpoint mode for hybrid RAN
sharing within a carrier-sharing operator group

s

user-plane S1 MO for user-plane S1 MO for user-plane X2 MO for

s
each operator within each operator within each operator within

a carrier-sharing oper a carrier-sharing oper a carrier-sharing oper
ator group. ator group, or configu ator group, or configu
re a single user-plane re a single user-plane
S1 MO for the operat X2 MO for the operat
ors to share within a ors to share within a
group. group.
Local user plane Configure a single loc Configure a single loc Configure a dedicated
al S1 user-plane IP ad al S1 user-plane IP ad local X2 user-plane IP
dress for the operator dress for the operator address for each oper
s to share within a gr s to share within a gr ator within the group,
oup. oup. or configure a single l
ocal X2 user-plane IP
address for the opera
tors to share within a
group.
Peer user plane Configure a dedicated Configure a dedicated Configure a dedicated

peer S1 user-plane IP peer S1 user-plane IP peer X2 user-plane IP
address for each oper address for each oper address for each oper
ator within a group. ator within the group, ator within the group,
or configure a single or configure a single
peer S1 user-plane IP peer X2 user-plane IP
address for the opera address for the opera
tors to share within a tors to share within a
group. group.
Link Mode
Table 7-6 Control-plane transmission link configuration in link mode for hybrid RAN sharing
between carrier-sharing operator groups
Transmission Link S1 with Shared MMEs S1 with Dedicated MME X2

s
Control plane Configure dedicated Configure dedicated Configure dedicated

S1Interface and SCT S1Interface and SCT X2Interface and SCT
PLNK MOs for each c PLNK MOs for each c PLNK MOs for each c
arrier-sharing operato arrier-sharing operato arrier-sharing operato
r group. r group. r group.
Table 7-7 User-plane transmission link configuration in link mode for hybrid RAN sharing
between carrier-sharing operator groups
Transmission Link S1 with Shared S-GWs S1 with Dedicated S-GW X2

s
User plane Configure a dedicated Configure a dedicated Configure a dedicated

IPPATH MO for each IPPATH MO for each IPPATH MO for each
operator, or configure operator. operator, or configure
a single IPPATH MO f a single IPPATH MO f
or the operators to sh or the operators to sh
are. are.
Table 7-8 Control-plane transmission link configuration in link mode for hybrid RAN sharing
within a carrier-sharing operator group
Transmission Link S1 with Shared MMEs S1 with Dedicated MME X2

s
Control plane Configure the S1Inter Configure dedicated If the peer operat
face and SCTPLNK M S1Interface and SCT ors are within the
Os for the operators t PLNK MOs for each o same carrier-shari
o share within a grou perator. ng operator grou
p. p, configure the X
2Interface and S
CTPLNK MOs for
them to share.
If the peer operat
ors are not in the
same carrier-shari
ng operator grou
p, configure dedi
cated X2Interfac
e and SCTPLNK
MOs.
Table 7-9 User-plane transmission link configuration in link mode for hybrid RAN sharing
within a carrier-sharing operator group
Transmission Link S1 with Shared S-GWs S1 with Dedicated S-GW X2

s
User plane Configure a dedicated Configure a dedicated Configure a dedicated

IPPATH MO for each IPPATH MO for each IPPATH MO for each
operator, or configure operator. operator, or configure
a single IPPATH MO f a single IPPATH MO f
or the operators to sh or the operators to sh
are within the group. are within the group.
Dynamic sharing of uplink transmission bandwidth in hybrid RAN sharing is the same as that in RAN
sharing with common carrier. For details, see 4.1.9.3 Dynamic Sharing of Uplink Transmission Bandwidth.
VLAN planning in hybrid RAN sharing is the same as that in RAN sharing with common carrier. For
details, see 4.1.9.4 VLAN Planning.
Multi-operator PKI in hybrid RAN sharing is the same as that in RAN sharing with common carrier. For
details, see 4.1.10 Multi-operator PKI.
7.2.1 Benefits
Benefits.
7.2.2 Impacts
Network Impacts
If the UE distribution is different among RAN sharing operators, the throughput may change after
hybrid RAN sharing is enabled. The throughput is not affected if the UE distribution is consistent
among RAN sharing operators.
If the RB proportions vary greatly between the RAN sharing operators (for example, 9:1 for two
operators), UEs served by the operator with a smaller RB proportion experience a longer scheduling
delay after hybrid RAN sharing is enabled. However, the scheduling delay can still meet the QoS
requirements specified in section 6.1.7.2 "Standardized QCI characteristics" in 3GPP TS 23.203 V8.5.0.
After this function is enabled, handovers between RAN sharing operator groups under the same
eNodeB are treated as S1-based handovers. Therefore, this function increases the number of inter-
eNodeB handovers when operators (A and B) and operator B are in different RAN sharing operator
groups.
Function Impacts
FDD None None None None

ation and Emiss

n.
FDD Multi-carrier c CellShutdown.CellShu Energy Conserv In RAN sharing scenarios,

ation and Emiss
oordinated ene tdownSwitch set to ON_ ion Reduction the PLMN IDs of a capacit
rgy saving MULTI_CARRIER_HIE y cell must be a subset of
R_SHUTDOWN or O the PLMN IDs of its co-co
N_MUL_CARR_HIER_ verage neighboring basic
MANUAL_SHUTDN cell. Otherwise, the capaci
n.
Management in
Management
FDD Uplink single-si UlInterfSuppressCfg. Interference Det It is recommended that int

ection and Supp
de in-band int UlSingleSideIntrfImpMitSw ression erference detection and s
erference man uppression not be enable
s.
FDD LTE FDD and N SpectrumCloud.Spect LTE FDD and N When hybrid RAN sharing
R Spectrum Sh
R Flash Dynami rumCloudSwitch aring is enabled together with L
c Spectrum Sh TE FDD and NR Flash Dyn
aring amic Spectrum Sharing (th
at is, SpectrumCloud.Spect
rumCloudSwitch is set to LTE
_NR_SPECTRUM_SHR), th
e number of available RBs
for an operator is calculat
ed as follows: (Total numb
er of RBs – Number of RBs
shared to the NR network)
x RB allocation proportion
configured for the operat
or
FDD Centralized po LTE_CENTRAL_POWE Dynamic Power In static RAN sharing mod

Sharing Betwee
wer sharing R_SHARING_SW opti n LTE Carriers e, the power estimation fo
on of the CellDynPo r centralized power sharin
werSharing.DynamicPo g does not consider the o
werSharingSwitch param perator-specific RB restrict
eter ions. As a result, the estim
ated power is greater than

expected.
FDD Hybrid power s LTE_HYBRID_POWER Smart 8T8R (FD In static RAN sharing mod
D)
haring _SHARING_SW optio e, the power estimation fo
n of the CellDynPow r centralized power sharin
erSharing.DynamicP g does not consider the o
owerSharingSwitch p perator-specific RB restrict
arameter ions. As a result, the estim
ated power is greater than
expected.
FDD Dynamic carrie CellPwrSavingAlgo.C Energy Conserv In RAN sharing scenarios,

ation and Emiss
r shutdown ph arrierDynShutdownPh2Sw ion Reduction the PLMN IDs of a capacit
ase 2 set to CAPACITY_CEL y cell must be a subset of
L the PLMN IDs of its co-co
n.
7.3 Requirements
7.3.1 Licenses
If the licensed value of Hybrid RAN Sharing is 0, the hybrid RAN sharing function becomes
invalid to secondary operators.
FDD LOFD-070206 Hybrid RAN Sharin LT1S0HRANS00 per cell

g
7.3.2 Software

used.
h common carrie Mode.ENodeBShar nly one RAN sharing mod
r ingMode e.
h dedicated carri Mode.ENodeBShar nly one RAN sharing mod
er ingMode e.
FDD Out-of-band rela OutOfBandRela Relay None

y ySwitch option
of the CellAlgoS
witch.RelaySwitch
parameter
FDD In-band relay InBandRelayDe Relay None

NbSwitch or InB
andRelayReNbS
witch option of t
he CellAlgoSwit
ch.RelaySwitch par
ameter
FDD Intra-RAT ANR ANR Management If the serving cell and neig
IntraRatEve
ntAnrSwitch hboring cells are managed
option of th by different OSSs, intra-R
e ENodeBAl AT ANR does not work wh
goSwitch.An en the PLMN ID at the top
rSwitch para of the PLMN list is rotated.
meter: contr
olling intra-
RAT event-tri
ggered ANR
IntraRatFast
AnrSwitch o
ption of the
ENodeBAlg
oSwitch.AnrS
witch parame
ter: controlli
ng intra-RAT
fast ANR
Uplink Spectrum SpectrumCloudSwitc nk Spectrum Sharing
h
Sharing
FDD Uplink single-sid UlInterfSuppres None None

e in-band interfe sCfg.UlSingleSideIn
rence impact mit trfImpMitSw
igation
FDD Physical Resourc PHY_RES_SLICIN None When the Physical Resour

e Slicing G_SWITCH optio ce Slicing function is enabl
n of the CellAlgo ed:
ExtSwitch.Operat
The CellAlgoSwitch.R
orFunSwitch para
anShareModeSwitch para
meter
meter must be set to
OFF.
The OpPrbGroupshar
eSwitch option of the
CellAlgoSwitch.OpRes
ourceGroupShareSwitch p
arameter must be des
elected.
FDD TM4 and TM6 A CL_TM_ADAPTA Low-Band Booster If TM4 and TM6 Adaptatio
daptation TION_OPT_SW o n is enabled, the CellAlgo
ption of the Cell Switch.RanShareModeSwitch
MimoParaCfg.Mi parameter cannot be set t
moSwitch paramet o OFF.
er
7.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
7.3.4 Others
None
Preparation for the transmission and interface data required in RAN sharing scenarios is similar to that
in the independent operator mode. The configurations vary depending on the network architecture in
use. For details, see 7.1.9 Transmission Networking and S1 and X2 Self-Management.
Scenario-specific data for hybrid RAN sharing can be configured based on information provided in this
section, Cell Management, and Mobility Management in Connected Mode.
setup by SON h.X2SonSetupSwitch tch must be turned on if the X2 interface uses the sim
plified endpoint mode.

Table 7-11 Parameters that must be set to configure the reference relationship between the
X2 and EPGROUP MOs

Set this parameter to CP_UP_CFG when only both
control-plane and user-plane endpoints in the EP
GROUP MO are referenced in the configuration of
the X2 MO.
d Point Group ID
oint Group ID
n Release elease
CN Operator Sha X2.CnOpSharingGr Set this parameter based on the network plan.
ring Group ID oupId
CN Operator ID CnOperator.CnO The CnOperator.CnOperatorId parameter values must be

peratorId different between operators.

me peratorName
CN Operator typ CnOperator.CnO The configuration of the primary and secondary opera
e peratorType tors does not take effect for hybrid RAN sharing. Whe
n the license for hybrid RAN sharing is invalid, the pri
mary operator configured by this parameter takes effe
ct for the eNodeB and the primary operator's links are
retained. The primary operator must be the primary o
perator of a RAN sharing operator group. Every eNode
B must be configured with one primary operator.
ode

code
CN Operator Sha CnOpSharingGr None

ring Group ID oup.CnOpSharingG
roupId
Primary Operato CnOpSharingGr None

r ID oup.PrimaryOperat
orId
Secondary Oper CnOpSharingGr None

ator List oup.SecondaryOpe
ratorList
Local Cell ID Cell.LocalCellId None
CN Operator Sha Cell.CnOpSharingG None

ring Group ID roupId

ea ID ackingAreaId

nOperatorId
Tracking area co CnOperatorTa.Ta In a cell where hybrid RAN sharing is enabled, configur
de c e the same TAC for all operators.
Local tracking ar CellOp.TrackingAr For example, when the eNodeB is shared by two opera
ea ID eaId tors in hybrid RAN sharing mode, a cell must be config
ured with the tracking area IDs of both operators, and
the two tracking area IDs must correspond to the sam
e TAC.
In a cell where hybrid RAN sharing is enabled, the CnO
peratorTa.CnOperatorId parameter values must be differ
ent. One of the parameter values must correspond to t
he primary operator.
Operator uplink CellOp.OpUlRbUse The sum of the operator uplink RB used ratio paramet
RB used ratio dRatio er values configured for all operators involved in hybri
d RAN sharing must not exceed 100%.
Operator downli CellOp.OpDlRbUse The sum of the operator downlink RB used ratio para
nk RB used ratio dRatio meter values configured for all operators involved in h
ybrid RAN sharing must not exceed 100%.
Operator PLMN CellOp.OperatorPl None

Round Period mnRoundPeriod
Operator Resour CellOp.OpResourc None

ce Group Index eGroupIndex
eNodeB sharing ENodeBSharing Set this parameter to HYBRID_SHARED.

ingMode
S1 ID S1.S1Id None
CN Operator Sha S1.CnOpSharingGro None

ring Group ID upId
S1 Interface ID S1Interface.S1Int None

erfaceId
CN Operator Sha S1Interface.CnOp None

ring Group ID SharingGroupId
X2 ID X2.X2Id None
CN Operator Sha X2.CnOpSharingGr None

ring Group ID oupId
X2Interface ID X2Interface.X2Int None

erfaceId
CN Operator Sha X2Interface.CnO None

ring Group ID pSharingGroupId
Local cell ID CellAlgoSwitch. None

LocalCellId
Plmn Broadcast CellAccess.Broad None

Mode castMode
Plmn Round Bro CellAccess.Round None

adcast Period Period
Plmn Round Acti CellAccess.Round None

on Time ActionTime
CN Operator ID LicenseSharingP None None

olicy.CnOperatorId
The proportion o LicenseSharingP None If the licensed RRC_CONNECTED UE

f the maximum n olicy.MaxUserNum resources of the eNodeB are distrib
umber of users Rate uted among operators in proportio
ns, the maximum number of RRC_C
ONNECTED UEs served by each ope
rator cannot exceed the predefined
proportion. If the proportions are n
ot specified, all the operators share
the total licensed number of RRC_C
ONNECTED UEs of the eNodeB.

f the sharing nu olicy.UserNumShari
mber of users ngRate
User Number Sh LicenseSharingP None None

aring Group ID olicy.UserNumShari
ngGroupId
RAN Sharing Mo CellAlgoSwitch. None None

de Switch RanShareModeSwitc
h
Operator Resour CellAlgoSwitch. None None

ce Group Share S OpResourceGroupS
hareSwitch
witch
Local cell ID CellAccess.LocalC None None

ellId
Uplink Traffic Lic LicRatio.UpLicRati None None

ense Ratio o
Traffic Sharing Ty LicRatio.TrafficSh None None

pe aringType
CN Operator ID LicRatioSharePo None None

licy.CnOperatorId
TrfRatio LicRatioSharePo None None

licy.TrfRatio
TrfSharingRatio LicRatioSharePo None None

licy.TrfSharingRatio
Different Operat GlobalProcSwitc None None

or With Same M h.DiffOpWithSameM
MEC Switch mecSwitch
ANR Under RAN ENodeBAlgoSwi None Select the NBSLTEPLMNRoundSwi

Sharing Algorith tch.RanSharingAnr tch option of the ENodeBAlgoSwit
m Switch Switch ch.RanSharingAnrSwitch parameter for
neighboring cell supports hybrid R
AN sharing and the CellAccess.Broa
dcastMode parameter is set to RR_M
ODE or FREE_Mode for the neighb
oring cell.
Select the NBSLTERANSharingSwit
ch option of the ENodeBAlgoSwitc
h.RanSharingAnrSwitch parameter for
neighboring cell supports hybrid R
AN sharing and the CellAccess.Broa
dcastMode parameter is set to NORM
AL_MODE for the neighboring cell.
Handover Algo s ENodeBAlgoSwi InterPlmnHoSwit Select this option.

witch tch.HoAlgoSwitch ch
Operator Functio CnOperator.Oper INTRA_RAT_INTE Set this parameter based on the net
n Switch atorFunSwitch R_PLMN_HO_SW work plan.
UTRAN_INTER_P
LMN_HO_SW
GERAN_INTER_P
LMN_HO_SW
NR_INTER_PLMN
_HO_SW
CN Operator ID InterPlmnHoLis None None

t.CnOperatorId
Target Mobile co InterPlmnHoLis None None

untry code t.TarMcc
Target Mobile ne InterPlmnHoLis None None

twork code t.TarMnc
RAT frequency pr RatFreqPriority None None

iority group ID Group.RatFreqPrio
rityGroupId
RAT Type RatFreqPriority None None

Group.RatType
DL Earfcn or Ban RatFreqPriority None None

dclass Group.DlEarfcn
Priority RatFreqPriority None None

Group.Priority
GERAN Frequenc RatFreqPriority None None

y Indicator Group.BandIndicat
or
Spid SpidCfg.Spid None None

iority indication iorityInd

iority group ID iorityGroupId
RRC Reestablish GlobalProcSwitc INTER_RAN_SHR It is recommended that this option

ment Optimize S h.RrcReestOptSwitc _GRP_REEST_OP be selected when a Huawei eNodeB
witch h T_SW is connected to a non-Huawei core
network.
The following table describes the parameters that must be set to configure the dedicated cell-

CellOp.LocalCellId

CellOp.BcchGroup

Id
Cn operator ID GeranNFGroupS None

CellOp.CnOperator
ID

or
Cell reselection d GeranNFGroupS The dedicated cell-reselection priorities of different RA

edicated priority CellOp.CellReselD Ts must be different.
ediPri
reselection priority for a GERAN frequency based on the neighboring frequency's PLMN.
Local cell ID GeranRanShare. None

LocalCellId
BCCH group ID GeranRanShare. None

BcchGroupId
Mobile country c GeranRanShare. None

ode Mcc
Mobile network GeranRanShare. None

code Mnc
Cell reselection p GeranRanShare. None

nd
ndicator
Cell reselection p GeranRanShare. Set this parameter based on the network plan.

lOp.LocalCellId

N lOp.UtranDlArfcn
Cn operator ID UtranNFreqSCel None

lOp.CnOperatorID

or
Cell reselection d UtranNFreqSCel The dedicated cell-reselection priorities of different RA

edicated priority lOp.CellReselDediP Ts must be different.
ri
reselection priority for a UTRAN frequency based on the neighboring frequency's PLMN.
Local cell ID UtranRanShare. None

LocalCellId
Downlink UARFC UtranRanShare. None

N UtranDlArfcn
Mobile country c UtranRanShare. None

ode Mcc
Mobile network UtranRanShare. None

code Mnc
Cell reselection p UtranRanShare. None

nd
ndicator
Cell reselection p UtranRanShare. Set this parameter based on the network plan.

llOp.LocalCellId

N llOp.DlEarfcn
Cn operator ID EutranNFreqSCe None
llOp.CnOperatorID

or
Cell reselection d EutranNFreqSCe The dedicated cell-reselection priorities of different RA

edicated priority llOp.CellReselDedi Ts must be different.
Pri
reselection priority for an E-UTRAN frequency based on the neighboring frequency's PLMN.
Local cell ID EutranNFreqRa None

nShare.LocalCellId
Downlink EARFC EutranNFreqRa None

N nShare.DlEarfcn
Mobile country c EutranNFreqRa None

ode nShare.Mcc
Mobile network EutranNFreqRa None

code nShare.Mnc
Cell reselection p EutranNFreqRa None

riority configure i nShare.CellReselP
ndicator riorityCfgInd
Cell reselection p EutranNFreqRa Set this parameter based on the network plan.
riority nShare.CellReselP
riority
reselection priority for a CDMA frequency based on the serving cell's PLMN.

ellOp.LocalCellId

ellOp.BandClass
Cn operator ID Cdma2000BcSC None

ellOp.CnOperatorI

D
CDMA2000 HRP Cdma2000BcSC None

icator
CDMA2000 HRP Cdma2000BcSC The dedicated cell-reselection priorities of different RA

D Cell Reselectio ellOp.HrpdCellRes Ts must be different.
rity
reselection priority for an NR frequency.

p.LocalCellId

p.DlArfcn

p.CnOperatorId

dicator onfigInd
the GUI.
A RAN sharing operator group is added for hybrid RAN sharing.
A RAN sharing operator group for hybrid RAN sharing is removed.
The operator information within a hybrid RAN sharing operator group is modified.
The sharing mode of an eNodeB is changed from the hybrid RAN sharing mode to the
Adding a RAN sharing operator group for hybrid RAN sharing

1. Configure the information about the operator and the RAN sharing operator group.
a. (Optional) CnOperator: Used to add operator information.
b. CnOpSharingGroup: Used to add RAN sharing operator group information.
2. Configure transmission links in FDD.

For detailed operations, see transmission link configurations in S1 and X2 Self-Management. The
mapping relationships between the RAN sharing operator group and the X2, S1, X2Interface,
and S1Interface MOs need to be configured.
3. Configure a cell.
a. Cell configurations in the hybrid RAN sharing mode are the same as those in the
independent operator mode. For details, see Cell Management. The mapping relationships
between the RAN sharing operator group and the Cell MOs need to be configured.
b. CellOp: Used to set the cell operator information.
c. Resource sharing policies between hybrid RAN sharing operators need to be configured.
i. (Optional) LicenseSharingPolicy: Used to set the licensed proportion of

ii. CnOperatorTa: Used to add tracking area information.
iii. CellAlgoSwitch: Used to set the RAN sharing mode switch in FDD.
iv. (Optional) CellAccess: Used to set the cell access information.
v. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
vi. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for each
operator and the percentage of available resources one operator can share with
other operators in FDD.
4. Configure neighboring cells in FDD.
a. (Optional) EutranExternalCell: Used to configure external E-UTRAN cells.
b. (Optional) EutranExternalCellPlmn: Used to configure the PLMNs of the external E-

UTRAN cells.
5. Use the ENodeBAlgoSwitch MO to set the ANR switch and inter-PLMN handover information
in FDD.
6. Configure the cell-reselection priority in FDD.
a. (Optional) RatFreqPriorityGroup and SpidCfg: Used to set the SPID-based dedicated

cell-reselection priority.
b. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, or

Cdma2000BcSCellOp: Used to set a dedicated cell-reselection priority based on the
serving cell's PLMN.
c. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used to set a

dedicated cell-reselection priority based on the neighboring frequency's PLMN.
Removing a RAN sharing operator group from hybrid RAN sharing operator groups
1. Remove the configured cell-reselection priority in FDD.
a. (Optional) RatFreqPriorityGroup and SpidCfg: Used to remove the SPID-based

dedicated cell-reselection priority.
b. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, or

based on the serving cell's PLMN.
c. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used to remove

the dedicated cell-reselection priority configured based on the neighboring frequency's
PLMN.
2. Use the ENodeBAlgoSwitch MO to remove the ANR switch and inter-PLMN handover
information in FDD.
3. Remove neighboring cells in FDD.
a. (Optional) EutranExternalCell: Used to remove external E-UTRAN cells.
b. (Optional) EutranExternalCellPlmn: Used to remove the PLMNs of the external E-UTRAN

cells.
c. EutranIntraFreqNCell, EutranInterFreqNCell, UtranNCell, and GeranNcell: Used to

remove neighboring cells of the E-UTRAN cell.
4. Remove the resource sharing policies between hybrid RAN sharing operators.
a. (Optional) LicenseSharingPolicy: Used to remove the configured licensed proportion of

b. CnOperatorTa: Used to remove the tracking area information.
c. CellAlgoSwitch: Used to remove the RAN sharing mode switch configuration in FDD.
d. (Optional) CellAccess: Used to remove the cell access information.
e. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.
f. (Optional) LicRatioSharePolicy: Used to remove the configuration of the licensed traffic

5. Remove cells.
a. Cell removal in the hybrid RAN sharing mode is the same as that in the independent
operator mode. For details, see Cell Management. The mapping relationships between the
RAN sharing operator group and the Cell MOs need to be removed.
b. CellOp: Used to remove the cell operator information.
6. Remove transmission links in FDD.

For detailed operations, see transmission link removal in S1 and X2 Self-Management. The
mapping relationships between the RAN sharing operator group and the X2, S1, X2Interface,
and S1Interface MOs need to be removed.
7. Remove the information about the operator and the RAN sharing operator group.
a. CnOpSharingGroup: Used to remove the RAN sharing operator group information.
b. (Optional) CnOperator: Used to remove the operator information.
Modifying the operator information within a hybrid RAN sharing operator group
Changing the primary operator
1. Remove the RAN sharing operator group and related configurations. For detailed
operations, see steps 1 through 6 in "Removing a RAN sharing operator group from
hybrid RAN sharing operator groups."
2. Add a RAN sharing operator group and related configurations. For detailed operations,
see steps 1 through 6 in "Adding a RAN sharing operator group for hybrid RAN sharing."
1. (Optional) Use the CnOperator MO to add operator information.
2. Use the CnOpSharingGroup MO to add the mapping relationship between the secondary
operator and the RAN sharing operator group.
3. For other steps, see steps 2 through 9 in "Adding a secondary operator" in Parameters for
Reconfiguration of 4.4.1.1 Data Preparation.
1. Perform steps 1 through 8 in "Removing a secondary operator" in Parameters for

Reconfiguration of 4.4.1.1 Data Preparation.
2. Use the CnOpSharingGroup MO to remove the mapping relationship between the

secondary operator and the RAN sharing operator group.
3. (Optional) Use the CnOperator MO to remove the operator information.
Changing the sharing mode of an eNodeB from the hybrid RAN sharing mode to the independent
operator mode
1. Perform steps 1 through 7 in "Removing a RAN sharing operator group from hybrid RAN
sharing operator groups." Additionally, remove all information about the RAN sharing
operator groups, retain information about the independent operator, and remove information
about other operators.
2. Use the ENodeBSharingMode MO to set the eNodeB sharing mode to the independent
operator mode. After the modification, you need to run the RST APP command to reset the
application referenced by the eNodeB function for the application to take effect (the
application ID can be queried by running the LST APP command).
3. (Optional) Use the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter to turn off the ANR

switch in the adjacent cells that have neighbor relationships with the local cell in FDD.

MOD ENODEBSHARINGMODE: ENodeBSharingMode=HYBRID_SHARED;
//Adding operators and operator groups for hybrid RAN sharing
ADD CNOPERATOR: CnOperatorId=1,
CnOperatorName="telecom",CnOperatorType=CNOPERATOR_SECONDARY, Mcc="460",
Mnc="03";
ADD CNOPERATOR: CnOperatorId=2,
CnOperatorName="yunyingshangX",CnOperatorType=CNOPERATOR_SECONDARY, Mcc="460",
Mnc="06";
ADD CnOpSharingGroup: CnOpSharingGroupId=0, PrimaryOperatorId=0;
ADD CnOpSharingGroup: CnOpSharingGroupId=1, PrimaryOperatorId=2;
ADD SECONDARYOP2GROUP: CnOpSharingGroupId=0, SecondaryOperatorId=1;
//Configuring transmission links (in endpoint mode)
//In endpoint mode, the S1 switch needs to be turned on if different SCTPHOST MOs are
configured for operators in the same RAN sharing group.
MOD GLOBALPROCSWITCH: SinglePlmnHostSplitSwitch=S1_SWITCH-1;

UpEpGroupId=0, CnOpSharingGroupId=0;
//Configuring a transmission link in end point configuration mode (X2 self-setup is used as an
example)
UpEpGroupId=3, TargetENodeBRelease=Release_R14, CnOpSharingGroupId=0;
//Configuring transmission links (in link mode)
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0,
CnOpSharingGroupId=0;
ADD X2INTERFACE: X2InterfaceId=0, X2CpBearerId=0, CnOperatorId=0,
//Adding cells
ADD CELL: LocalCellId=0, CellName="LTE", CellId=0, PhyCellId=0, FddTddInd=CELL_FDD,
TxRxMode=2T2R, CnOpSharingGroupId=0;
//Configuring the mapping relationships between the cells and operator tracking areas
ADD CELL: LocalCellId=1, CellName="LTE-1", CellId=0, PhyCellId=0, FddTddInd=CELL_FDD,
TxRxMode=2T2R, CnOpSharingGroupId=1;
RST APP: AID=1;
//Configuring the cell-specific RAN sharing mode switch
MOD CELLALGOSWITCH: LocalCellId=0, RanShareModeSwitch=ON,
OpResourceGroupShareSwitch=OpPrbGroupshareSwitch-0;
//Configuring the PLMN broadcast mode in a cell
MOD CELLACCESS: LocalCellId=0, BroadcastMode=NORMAL_MODE;
MMEC
//Configuring the eNodeB-specific ANR switch under RAN sharing
MOD ENODEBALGOSWITCH: RANSHARINGANRSWITCH=NBSLTERANSharingSwitch-1;
//Configuring the inter-PLMN handover information
//Configuring the RAT-specific inter-PLMN handover switches

//Configuring a RAT/frequency priority group
ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=0, RatType=EUTRAN, DlEarfcn=3000;
//Configuring the RAT/frequency priority information (based on UE's SPID)
ADD SPIDCFG: Spid=1, RatFreqPriorityInd=CFG, RatFreqPriorityGroupId=0;
//Configuring a dedicated cell-reselection priority for a GERAN frequency (based on the serving
cell's PLMN)
//Configuring a dedicated cell-reselection priority for a GERAN frequency (based on the
ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="02",
//Configuring a dedicated cell-reselection priority for a UTRAN frequency (based on the serving
cell's PLMN)
//Configuring a dedicated cell-reselection priority for a UTRAN frequency (based on the
ADD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=10800, Mcc="460", Mnc="02",
serving cell's PLMN)
ADD EUTRANNFREQRANSHARE: LocalCellId=0, DlEarfcn=1234, Mcc="460", Mnc="01",
CellReselPriorityCfgInd=NOT_CFG;
//Configuring a dedicated cell-reselection priority for a CDMA frequency (based on the serving
cell's PLMN)
//Configuring a dedicated cell-reselection priority for an NR frequency (based on the serving

cell's PLMN)
//(Optional) Configuring the intra-eNodeB inter-RAN-sharing-group RRC reestablishment
optimization switch
MOD GLOBALPROCSWITCH:RrcReestOptSwitch=INTER_RAN_SHR_GRP_REEST_OPT_SW-1;

Maintenance.
Prerequisites
1. Based on the network plan, the eNodeB is shared between three operators that use hybrid RAN
sharing. Operators A and B are in one RAN sharing operator group, while operator C is in another
RAN sharing operator group.
3. Three UEs (UE 1, UE 2, and UE 3) are ready. They respectively subscribe to services of the three
operators (A, B, and C).
Procedure
Expected result:
PLMN IDs.

Expected result:
For cell 0, if "mcc" and "mnc" of the "plmn-Identity" fields in SIB1 are consistent with the
operators' PLMNs, PLMN information about the primary and secondary operators has been
correctly sent in SIB1. This indicates that the function has been activated successfully. In this
example, the first PLMN indicates the primary operator whose "plmn-Identity" field is "46001."
The second PLMN indicates the secondary operator whose "plmn-Identity" field is "46003."
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellIdentity:0000001100110001101000000000(03 31 A0 00)
For cell 1, the "plmn-Identity" field in SIB1 is "46006."
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
mnc
cellIdentity:0000001100110001101000000001(03 31 A0 01)
3. Power on UE 1 and UE 2 to initiate attach procedures towards the shared cell.

Expected result:
successfully accessed the shared cell and selected the correct EPCs. In this situation, the function
has been activated successfully. The path of the "tAI" IE is S1ap-
The values of "PLMNidentity" and "TAC" in the traced message are mapped to the eNodeB
configurations as follows. The PLMN ID 46001 is used as an example.
The MCC is 460 and MNC is F01 (F is added if there are fewer than three digits), which are
combined as 460F01. Then, each two adjacent digits exchange positions to get 64F010, which
is the value of "PLMNidentity" in the traced message.
The value of "TAC" is a hexadecimal number in the traced message.
In networks where hybrid RAN sharing is enabled, some cell-level performance counters can be
monitored on a per operator basis. These counters are used to indicate whether the network key
performance indicators (KPIs) meet operators' requirements and whether proportion-based resource
sharing achieves the expected effect. Operators can use these counters for preliminary fault
demarcation and locating.
Hybrid RAN sharing and RAN sharing with common carrier use the same operator-specific counters.
For details about these counters, see 4 RAN Sharing with Common Carrier.
8
RAN Sharing by More Operators
8.1 Principles
This function allows an eNodeB to be shared by up to six operators.

If this function is not enabled together with RAN sharing with common carrier, RAN sharing with
dedicated carrier, or hybrid RAN sharing is enabled, a maximum of four operators can share the RAN.
8.2.1 Benefits
Benefits.
8.2.2 Impacts
Network Impacts
None
Function Impacts
None
8.3 Requirements
8.3.1 Licenses
In addition to the license required in a specific scenario, the operator has purchased and activated the
license for the feature listed in the following table.
FDD LOFD-001086 RAN Sharing by LT1S00RSMO00 per cell

More Operators
8.3.2 Software
FDD RAN sharing wit ENodeBSharing RAN Sharing RAN sharing by

h common carrie Mode.ENodeBShar more operators r
r ingMode equires that one
of these function
FDD RAN sharing wit ENodeBSharing RAN Sharing
s be enabled.
h dedicated carri Mode.ENodeBShar
er ingMode
FDD Hybrid RAN shar ENodeBSharing RAN Sharing

ing Mode.ENodeBShar
ingMode
None
8.3.3 Hardware
Base Station Models
For FDD, the following base stations are compatible with this function:
Boards
No requirements
RF Modules
No requirements
8.3.4 Others
None
For details, see section "Data Preparation" of a specific function deployment scenario.
RAN sharing with common carrier (FDD): See 4.4.1.1 Data Preparation.
RAN sharing with dedicated carrier (FDD): See 5.4.1.1 Data Preparation.
Hybrid RAN sharing (FDD): See 7.4.1.1 Data Preparation.
For details, see "Using MML Commands" of a specific function deployment scenario.
RAN sharing with common carrier (FDD): See 4.4.1.2 Using MML Commands.
RAN sharing with dedicated carrier (FDD): See 5.4.1.2 Using MML Commands.
Hybrid RAN sharing (FDD): See 7.4.1.2 Using MML Commands.
For detailed operations, see Feature Configuration Using the MAE-Deployment.
For details, see section "Activation Verification" of a specific function deployment scenario. The only
difference is that you need to enable five or six UEs to initiate attach procedures towards the cells.
RAN sharing with common carrier (FDD): See 4.4.2 Activation Verification.
RAN sharing with dedicated carrier: See 5.4.2 Activation Verification.
RAN sharing with special dedicated carrier (FDD): See 6.4.2 Activation Verification.
Hybrid RAN sharing: See 7.4.2 Activation Verification.
For details, see section "Network Monitoring" of a specific function deployment scenario.
RAN sharing with common carrier in FDD: See 4.4.3 Network Monitoring.
RAN sharing with dedicated carrier: See 5.4.3 Network Monitoring.
RAN sharing with special dedicated carrier in FDD: See 6.4.3 Network Monitoring.
9
Hybrid RAN sharing: See 7.4.3 Network Monitoring.
Fair User Sharing (FDD)
9.1 Principles
In RAN sharing scenarios, the licensed RRC_CONNECTED UE resources are allocated to operators in
proportions specified by the LicenseSharingPolicy.MaxUserNumRate parameter. In addition, the fair user
sharing function is introduced. In this function, the LicenseSharingPolicy.UserNumSharingRate
parameter controls what percentage of an operator's resources can be shared with other operators
when there are unused resources. Such percentage of resources can also be shared between operators
within the same RRC_CONNECTED UE number sharing group. The sum of the values of the
LicenseSharingPolicy.MaxUserNumRate parameters for all operators cannot be greater than 100%. The
value of the LicenseSharingPolicy.UserNumSharingRate parameter for any operator cannot be greater

than the value of the LicenseSharingPolicy.MaxUserNumRate parameter for that operator.
For details about the RRC_CONNECTED UE number sharing group, see 4.1.5.2 Capacity License.
When the licensed RRC_CONNECTED UE resources are allocated among operators in proportions,
resources can be configured to be not shared, partly shared, or completely shared among operators by
using the LicenseSharingPolicy.UserNumSharingRate parameter. The following examples assume that
operator A and operator B share the RRC_CONNECTED UE number license.
Not shared
For both operators, the LicenseSharingPolicy.MaxUserNumRate parameter is set to 50% and the
LicenseSharingPolicy.UserNumSharingRate parameter to 0%. In this case, operator A cannot use
operator B's resources when the number of RRC_CONNECTED UEs of operator A has exceeded 50%
of the licensed user number and the number of RRC_CONNECTED UEs of operator B has not
reached 50% of the licensed user number.
Partly shared
LicenseSharingPolicy.UserNumSharingRate parameter to 10%. In this case, operator A can use
reached 50% of the licensed user number. Operator A can have a maximum of 60% of the licensed
user number.
Completely shared
LicenseSharingPolicy.UserNumSharingRate parameter to 50%. In this case, operator A can use
reached 50% of the licensed user number. Operator A can use all licensed system user number
when necessary.
When unused resources of an operator are shared with other operators, if UEs served by the operator
require access but experience insufficient resources, they can preempt those previously shared
resources as needed, up to the limit specified by the purchased license. The
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter controls whether the preemption is allowed.
Preemption will lead to service drops. The details vary depending on the settings of different options of
this parameter.
If the InterOpUeNumPreemptSwitch option is deselected, a UE attempting to access the network

of the operator cannot preempt resources of any other operator. In this case, the UE performs the
following operation:
If the IntraOpUeNumPreemptSwitch option is selected, the UE preempts the

RRC_CONNECTED UE resource from a UE with a lower priority served by the same operator.
The UE can also preempt the RRC_CONNECTED UE resource from a UE with a lower priority
served by another operator in the same RRC_CONNECTED UE number sharing group as its
own operator.
If the IntraOpUeNumPreemptSwitch option of the ENodeBAlgoSwitch.UeNumPreemptSwitch

parameter is deselected, the RRC_CONNECTED UE resources cannot be preempted in the
RRC_CONNECTED UE number sharing group.
If the InterOpUeNumPreemptSwitch option is selected, the UE attempting to access the network

of the operator preferentially preempts the resource from a UE served by another operator whose
number of RRC_CONNECTED UEs has exceeded the licensed number based on the following
principle: The eNodeB calculates, for each operator, the ratio of the actual number of
RRC_CONNECTED UEs to licensed number. Resources are preempted preferentially from whichever
operator has the highest ratio of actual number of UEs to licensed UE resources.
If the inter-operator resource preemption fails but the IntraOpUeNumPreemptSwitch option is

selected, the UE attempts to preempt the resource from another UE served by the same operator
or from a UE served by another operator in the same RRC_CONNECTED UE number sharing group
as its own operator. The procedure is the same as that for non-RAN-sharing scenarios. The
following principles apply to inter-PLMN resource preemption:
Resource preemption: All UEs that attempt to access the network of the operator whose
resources are being shared with can initiate inter-PLMN resource preemption.
Resources being preempted: Resources can be preempted from all UEs served by an operator
whose resources can be preempted, except for emergency call UEs and UEs that do not allow
preemption (as indicated in their ARP attributes). Resources are preempted from UEs served by
operators with the highest ratio of actual number of UEs to licensed UE resources.
UEs with lower priorities can preempt resources of UEs with higher priorities.
Note that a UE can still preempt the resource from a UE served by another operator when the
following conditions are met: The UeNumPreemptCapbEnhSwitch option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected; The CellRacThd.AcUserNumber
parameter is set to a value less than the number of RRC_CONNECTED UEs supported by the
eNodeB; The number of RRC_CONNECTED UEs in the cell has already reached or exceeded the
CellRacThd.AcUserNumber parameter value.
9.2.1 Benefits
With this function, an operator in RAN sharing mode can share its unused allotment of
RRC_CONNECTED UE resources with another operator. RAN sharing modes include RAN sharing with
common carrier, RAN sharing with dedicated carrier, hybrid RAN sharing, and RAN sharing with special
dedicated carrier.
4.2.1 Benefits.
9.2.2 Impacts
Network Impacts
When RRC_CONNECTED UE resources are partially or not shared among RAN sharing operators, the
maximum allowed number of RRC_CONNECTED UEs in shared cells cannot be reached. This is because
other operators cannot use or fully use the unused RRC_CONNECTED UE resources of a certain
operator.
Fair user sharing allows dynamic sharing and preemption of RRC_CONNECTED UE resources. This
increases the network resource usage but may increase the service drop rate because the resources of
low-priority UEs may be preempted when the network is congested.
Function Impacts
None
9.3 Requirements
9.3.1 Licenses
Feature ID Feature Name Model Sales Unit
LOFD-070213 Fair User Sharing LT1S00FUSH00 per Cell
9.3.2 Software
RAN sharing wit ENodeBSharing RAN Sharing Fair user sharing requires t
h common carrie Mode.ENodeBShar hat one of these features
r ingMode be enabled.
RAN sharing wit ENodeBSharing RAN Sharing

er ingMode
Hybrid RAN shar ENodeBSharing RAN Sharing

ing Mode.ENodeBShar
ingMode
RAT Function Name Function Switch Reference
FDD Out-of-band rela OutOfBandRelaySwitch o Relay

y ption of the CellAlgoSwit
ch.RelaySwitch parameter
FDD In-band relay InBandRelayDeNbSwitch Relay

or InBandRelayReNbSwit
ch option of the CellAlgo
Switch.RelaySwitch paramet
er
9.3.3 Hardware
Base Station Models
The compatible base stations are as follows:
Boards
No requirements
RF Modules
No requirements
9.3.4 Others
None
Fair user sharing is dependent on RAN sharing with common carrier, RAN sharing with dedicated
carrier, RAN sharing with special dedicated carrier, or hybrid RAN sharing. This section only describes
the data specific to fair user sharing. For data required by a prerequisite function, see section "Data
Preparation" of a specific function deployment scenario.
RAN sharing with common carrier: See 4.4.1.1 Data Preparation.
RAN sharing with dedicated carrier: See 5.4.1.1 Data Preparation.
RAN sharing with special dedicated carrier: See 6.4.1.1 Data Preparation.
Hybrid RAN sharing: See 7.4.1.1 Data Preparation.
Table 9-1 describes the parameters used for function activation specific to fair user sharing.
CN Operator ID LicenseSharingPolicy. None Set this parameter to the

CnOperatorId same value as the CN Op
erator ID parameter in th
e CnOperator MO.
The proportion o LicenseSharingPolicy. None None

f the maximum n MaxUserNumRate
umber of users
The proportion o LicenseSharingPolicy. None None

f the sharing nu UserNumSharingRate
mber of users
User Number Sh LicenseSharingPolicy. None None

aring Group ID UserNumSharingGroupId
UE number pree ENodeBAlgoSwitch.U InterOpUeNumPree Select this option.

mption switch eNumPreemptSwitch mptSwitch
This function is dependent on RAN sharing with common carrier, RAN sharing with dedicated carrier,
RAN sharing with special dedicated carrier, or hybrid RAN sharing. This section only describes the MML
configurations specific to this function. For MML commands required by a prerequisite function, see
section "Using MML Commands" of a specific function deployment scenario.
RAN sharing with common carrier: See 4.4.1.2 Using MML Commands.
RAN sharing with dedicated carrier: See 5.4.1.2 Using MML Commands.
RAN sharing with special dedicated carrier: See 6.4.1.2 Using MML Commands.
Hybrid RAN sharing: See 7.4.1.2 Using MML Commands.
The following are MML commands specific to this function.
//Configuring whether to allow inter-operator RRC_CONNECTED UE resource preemption
MOD ENODEBALGOSWITCH: UeNumPreemptSwitch=InterOpUeNumPreemptSwitch-1;

Maintenance.
The prerequisites for activation verification are as follows:
One of the prerequisite functions for fair user sharing has been activated.
The total licensed number of RRC_CONNECTED UEs is 100, and RAN sharing is used for operators
A and B with the LicenseSharingPolicy.MaxUserNumRate parameter set to 50 and the
LicenseSharingPolicy.UserNumSharingRate parameter set to 20 for both operators.
35 UEs of operators A and 60 UEs of operator B need to establish RRC connections.
Expected result:
RRC connections are established for all UEs of operator A and B. The excessive resources used by UEs of
operator B are offered by operator A.
To verify the activation of a prerequisite function, see section "Activation Verification" of a specific
function deployment scenario.
RAN sharing with common carrier: See 4.4.2 Activation Verification.
RAN sharing with special dedicated carrier: See 6.4.2 Activation Verification.
10
None
MOCN Cell Reselection Priority Configuration
10.1 Principles
In cells where RAN sharing with common carrier or hybrid RAN sharing is enabled, and in cells of a
secondary operator (involved in RAN sharing with special dedicated carrier), common priorities for cell
reselection are delivered through broadcast information and are not operator-specific. With this
function, the cell-reselection priority can be configured on a per operator basis. That is, different
operators can be configured with different camping policies for UEs in idle mode. For details, see 4.1.3.6
Cell Selection and Reselection.
The NrNFreqSCellOp, EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and
Cdma2000BcSCellOp MOs specify the dedicated cell-reselection priority of an intra-RAT neighboring
frequency or an inter-RAT neighboring frequency or frequency band for the PLMN of the serving cell.
The idleModeMobilityControlInfo (IMMCI) IE contains only the frequencies configured in the
configuration model and the serving frequency.
Before sending information about the dedicated cell-reselection priority to a UE, the eNodeB compares
the CnOperatorID of the UE's serving PLMN with the CnOperatorID of a neighboring frequency or
frequency band configured for dedicated cell-reselection priorities based on the serving cell's PLMN. If
the CnOperator.CnOperatorID parameter corresponding to the serving PLMN of the UE is the same as
the CnOperator.CnOperatorID parameter corresponding to a neighboring frequency or frequency band,
the information about the neighboring frequency or frequency band must be included in the delivered
dedicated cell reselection priority. Otherwise, the information about the neighboring frequency or
frequency band is not delivered.
Currently, the cell reselection priority of the serving frequency can be configured using either of the
following methods:
Method 1:
When the eNodeB delivers the dedicated cell-reselection priority based on the serving cell's PLMNs to
the UE, the priority specified by the CellResel.CellReselPriority parameter is used as the cell-reselection
priority of the serving frequency.
To assign different serving-frequency priorities for different operators, it is recommended that the
CellResel.CellReselPriority parameter be set to a value in the middle of the range from 0 to 7 (for
example, 2 to 5) so that the priorities for neighboring frequencies or frequency band relative to the
serving-frequency priority can be adjusted accordingly.
Take two operators (A and B) as an example, where the dedicated cell-reselection priorities of operator
B are in an order opposite to those of operator A. The CellResel.CellReselPriority parameter is 4, and the
priorities required for operator A are, from highest to lowest:
Serving frequency
Neighboring E-UTRA frequency
Neighboring UTRA frequency
The priorities required for operator B, in this example, are the reverse:
Neighboring UTRA frequency
Neighboring E-UTRA frequency
Serving frequency
In this scenario, the priorities can be configured as follows:

Operator A:
CellResel.CellReselPriority = 4
EutranNFreqSCellOp.CellReselDediPri = 3
UtranNFreqSCellOp.CellReselDediPri = 2
Operator B:
CellResel.CellReselPriority = 4
EutranNFreqSCellOp.CellReselDediPri = 5
UtranNFreqSCellOp.CellReselDediPri = 6
Method 2:
When CellOpHoCfg.ServingFreqReselPriority is set to a value other than 255 and the eNodeB delivers
the dedicated cell-reselection priority based on the serving cell's PLMNs to the UE, the priority
specified by the CellOpHoCfg.ServingFreqReselPriority parameter is used as the cell-reselection priority
of the serving frequency.
10.2.1 Benefits
When this function is used together with RAN sharing with common carrier, RAN sharing with
dedicated carrier, RAN sharing with special dedicated carrier, or hybrid RAN sharing, operators can
configure dedicated cell reselection priorities based on the serving cell's PLMN to provide operator-
specific camping policies for UEs in idle mode.
4.2.1 Benefits.
10.2.2 Impacts
Network Impacts
None
Function Impacts
FDD Coverage-based EmcInterFreqBli Mobility Management i MOCN cell reselection pri

n Connected Mode
inter-frequency e ndHoSwitch opt ority configuration is inco
mergency blind ion of the CellHo mpatible with RAN sharin
handover ParaCfg.CellHoAlg g information in coverage
oSwitch paramete -based inter-frequency em
r ergency blind handovers.
These two functions cann
ot be both enabled.
FDD Coverage-based UtranRedirectS Mobility Management i The cell reselection prioriti

n Connected Mode
inter-RAT hando witch or UtranP es based on operators of t
ver to UTRAN sHoSwitch optio he serving cell and blind r
n of the CellHoP edirection to a UTRAN cell
araCfg.HoModeSwi (controlled by UtranRedir
tch parameter ectSwitch) cannot be use
d at the same time. This is
because the UtranRanSha
re MO configuration is req
uired in the case of a blind
redirection to a UTRAN cel
l; however, the cell reselect
ion priorities based on op
erators of the serving cell
and the cell reselection pri
orities based on operators
of neighboring frequencie
s cannot exist at the same
time.
FDD Coverage-based GeranPsHoSwit Mobility Management i MOCN cell reselection pri

n Connected Mode
inter-RAT hando ch option of the ority configuration is inco
ver to GERAN ENodeBAlgoSwi mpatible with RAN sharin
tch.HoModeSwitch g information in coverage
parameter or Ge -based inter-RAT handove
ranRedirectSwit rs to GERAN. These two fu
ch option of the nctions cannot be both en
CellHoParaCfg.H abled.
oModeSwitch para
meter
10.3 Requirements
10.3.1 Licenses
FDD LOFD-001112 MOCN Flexible P LT1S0MFPBC00 per cell

riority Based Ca
mping
If the NrNFreqSCellOp MO is used to configure the dedicated cell-reselection priority of an

inter-RAT neighboring frequency or frequency band for the PLMN of the serving cell, this
function is not controlled by the preceding licenses.
10.3.2 Software
FDD RAN sharing wit ENodeBSharing RAN Sharing MOCN cell reselectio
h common carrie Mode.ENodeBShar n priority configurati
r ingMode on requires that one
of these functions be
FDD RAN sharing wit ENodeBSharing RAN Sharing enabled.
er ingMode

ing Mode.ENodeBShar
ingMode
None
10.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
10.3.4 Others
None
MOCN cell reselection priority configuration is dependent on RAN sharing with common carrier, RAN
sharing with dedicated carrier, or hybrid RAN sharing. This section only describes the data specific to
MOCN cell reselection priority configuration. For data required by a prerequisite function, see section
"Data Preparation" of a specific function deployment scenario.
Before configuring data for MOCN cell reselection priority configuration, check whether dedicated cell-
reselection priorities based on the neighboring frequency's PLMN have been configured. If so, delete
these settings.
The following tables describe the parameters specific to MOCN cell reselection priority configuration.

CellOp.LocalCellId

CellOp.BcchGroup
Id
Cn operator ID GeranNFGroupS Set this parameter to the same value as the CN Opera
CellOp.CnOperator tor ID parameter in the CnOperator MO.
ID

or

ediPri

lOp.LocalCellId

N lOp.UtranDlArfcn
Cn operator ID UtranNFreqSCel Set this parameter to the same value as the CN Opera
lOp.CnOperatorID tor ID parameter in the CnOperator MO.

or

ri

llOp.LocalCellId

N llOp.DlEarfcn
Cn operator ID EutranNFreqSCe Set this parameter to the same value as the CN Opera
llOp.CnOperatorID tor ID parameter in the CnOperator MO.

or

Pri
Local cell ID CellResel.LocalCel Set this parameter to the same value as the Local Cell
lId ID parameter in the Cell MO.
Cell reselection ti CellResel.TReselE None

mer value for EU utran
TRAN
Serving Frequen CellOpHoCfg.Ser None

cy Reselection Pr vingFreqReselPriorit
y
iority
reselection priority for a CDMA frequency based on the serving cell's PLMN.

ellOp.LocalCellId

ellOp.BandClass
Cn operator ID Cdma2000BcSC Set this parameter to the same value as the CN Opera
ellOp.CnOperatorI tor ID parameter in the CnOperator MO.
D

icator

D Cell Reselectio ellOp.HrpdCellRes
rity
Local cell ID CellReselCdma2 Set this parameter to the same value as the Local Cell
000.LocalCellId ID parameter in the Cell MO.
Cell reselection ti CellReselCdma2 None

mer for HRPD 000.TreselectionHr
pd
Configure dedicated cell reselection priorities for cells of the NR frequency.

p.LocalCellId

p.DlArfcn

p.CnOperatorId

dicator onfigInd
This function is dependent on RAN sharing with common carrier, RAN sharing with dedicated carrier, or
hybrid RAN sharing. This section only describes the MML configurations specific to this function. For
MML commands required by a prerequisite function, see section "Using MML Commands" of a specific

Configuring GERAN cell information
//Configuring a dedicated cell-reselection priority for a GERAN frequency

Configuring UTRAN cell information
//Configuring a dedicated cell-reselection priority for a UTRAN frequency

Configuring E-UTRAN cell information
//Configuring a dedicated cell-reselection priority for an E-UTRAN frequency

//(Optional) Setting parameters for cell reselection to E-UTRAN
MOD CELLRESEL: LocalCellId=0, TReselEutran=1;
//(Optional) Adding the dedicated priority of the serving frequency
ADD CELLOPHOCFG: LocalCellId=0, CnOperatorId=1, ServingFreqReselPriority=3;
Configuring CDMA2000 cell information
//Configuring a dedicated cell-reselection priority for a CDMA frequency

//(Optional) Setting parameters for cell reselection to CDMA2000
ADD CELLRESELCDMA2000: LocalCellId=0, HrpdParaCfgInd=CFG,
HrpdCellReselectParamCfgInd=CFG,TreselectionHrpd=2;
Configuring NR cell information
//Configuring a dedicated cell-reselection priority for an NR frequency


Maintenance.
The prerequisites for activation verification are as follows:

One of the prerequisite functions for MOCN cell reselection priority configuration has been activated.
An EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, or Cdma2000BcSCellOp MO
has been configured while an SpidCfg MO has not.
Expected result:
The eNodeB includes the cell reselection priorities for all the UE-supported PLMNs in the IE
"IdleModeMobilityControlInfo" in an RRC Connection Release message sent to the UE.
To verify the activation of a prerequisite function, see section "Activation Verification" of a specific
RAN sharing with common carrier (FDD): See 4.4.2 Activation Verification.
11
None
Multi-Operator SPID Policy
11.1 Principles
In RAN sharing mode, the operators that share an eNodeB must jointly plan the SPIDs to prevent SPID
range overlaps among operators. With the multi-operator SPID policy function, these operators can
specify their own SPID ranges without the need to negotiate the SPID ranges with one another.
Operator-specific SPID lists can be configured using the CnOperatorSpidCfg MO. Based on these SPID
lists, operators can configure their own SPID-based policies, for example, their own dedicated cell
reselection priorities. When releasing an RRC connection for a UE configured with an SPID, the eNodeB
checks whether a dedicated SPID list has been configured for the operator. If so, the eNodeB queries
the dedicated cell-reselection priority corresponding to the UE's SPID and then delivers the queried
information to the UE in an RRC connection release message.
Since the operators sharing an eNodeB have their respective SPID lists, each operator can allocate
SPIDs without negotiating with one another. The SPID ranges from 1 to 256.
This function allows different operators to have a same SPID but different dedicated cell reselection
priorities on a shared eNodeB.
11.2.1 Benefits
In RAN sharing mode, operators can configure dedicated cell reselection priorities based on respective
dedicated SPID lists to provide operator-specific camping policies for UEs in idle mode.
4.2.1 Benefits.
11.2.2 Impacts
Network Impacts
None
Function Impacts
FDD SPID-based cam None Flexible User Steering If both the multi-oper
ping and handov ator SPID policy and
er SPID-based camping
& handover are enabl
ed, the former takes
precedence.
11.3 Requirements
11.3.1 Licenses
licenses for the features listed in the following table.
FDD LOFD-001054 Flexible User Ste LT1S00FXUS00 per RRC Connected U

ering ser
FDD LOFD-070210 Multi Operators LT1SMOSPID00 per cell

SPID Policy
11.3.2 Software
FDD RAN sharing wit ENodeBSharing RAN Sharing Multi-operator SPID

h common carrie Mode.ENodeBShar policy requires that o
r ingMode ne of these functions
be enabled.
FDD RAN sharing wit ENodeBSharing RAN Sharing
er ingMode

ing Mode.ENodeBShar
ingMode
FDD Flexible user stee None Flexible User Steering None

ring
FDD WBB UE identific None WBB Multi-operator SPID

ation and differe policy allows different
ntiated QoS guar operators to use the s
antee ame SPIDs. WBB UE i
dentification and diff
erentiated QoS guara
ntee identifies WBB U
Es by using SPIDs. If b
oth functions are ena
bled, the eNodeB can
not identify WBB UEs
based on SPIDs.
11.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
11.3.4 Others
None
Multi-operator SPID policy is dependent on RAN sharing with common carrier, RAN sharing with
dedicated carrier, RAN sharing with special dedicated carrier in FDD, or hybrid RAN sharing. This
section only describes the data specific to multi-operator SPID policy. For data required by a
prerequisite function, see section "Data Preparation" of a specific function deployment scenario.
RAN sharing with special dedicated carrier (FDD): See 6.4.1.1 Data Preparation.
Table 11-1 describes the parameters used for function activation specific to multi-operator SPID policy.
CN Operator ID CnOperatorSpidCfg.CnOperato Set this parameter to the same va

rId lue as the CN Operator ID param
eter in the CnOperator MO.
Spid CnOperatorSpidCfg.Spid Set this parameter to the register

ed SPID of a UE.
RAT frequency priority in CnOperatorSpidCfg.RatFreqPri Set this parameter to CFG.

dication orityInd
RAT frequency priority g CnOperatorSpidCfg.RatFreqPri This parameter specifies the ID of

roup ID orityGroupId a RAT/frequency priority group. S
et this parameter to the same val
ue as the RAT frequency priority
group ID parameter in the RatFr
eqPriorityGroup MO.
RAT frequency priority g RatFreqPriorityGroup.RatFreq This parameter specifies the ID of

roup ID PriorityGroupId a RAT/frequency priority group.
RAT Type RatFreqPriorityGroup.RatType Set this parameter to the RAT to

which the frequency belongs.
DL Earfcn or Bandclass RatFreqPriorityGroup.DlEarfcn None
Priority RatFreqPriorityGroup.Priority None
GERAN Frequency Indica RatFreqPriorityGroup.BandInd None

tor icator
1. CnOperatorSpidCfg: Used to add, modify, or remove operator-specific SPID configurations.
2. RatFreqPriorityGroup: Used to add, modify, or remove configurations of a RAT/frequency priority

group.
This function is dependent on RAN sharing with common carrier, RAN sharing with dedicated carrier,
RAN sharing with special dedicated carrier in FDD, or hybrid RAN sharing. This section only describes
the MML configurations specific to this function. For MML commands required by a prerequisite
function, see section "Using MML Commands" of a specific function deployment scenario.
RAN sharing with special dedicated carrier (FDD): See 6.4.1.2 Using MML Commands.
//Adding a RAT/frequency priority group

ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=1, RatType=EUTRAN, DlEarfcn=2795,
Priority=1;
//Adding the operator-specific SPID configuration
ADD CNOPERATORSPIDCFG: CnOperatorId=0, Spid=1, RatFreqPriorityInd=CFG,
RatFreqPriorityGroupId=1;

Maintenance.
Prerequisites
RAN sharing with common carrier, RAN sharing with dedicated carrier, or hybrid RAN sharing is
enabled on the eNodeB.
The SPID is configured based on the UE's serving PLMN, and a RAT/frequency priority group is
configured.
Neighboring frequencies and external cells are configured. If RAN sharing with common carrier is
enabled in the external cells, the PLMNs of external cells must be configured.
Procedure
1. Power on a UE for it to access an E-UTRAN cell and obtain the SPID.

Then, check the UE's SPID in the S1AP_INITIAL_CONTEXT_SETUP_REQ message, as shown in Figure
11-1.
Figure 11-1 SPID contained in the S1AP_INITIAL_CONTEXT_SETUP_REQ message
2. Stop all services running on the UE.

After services on the UE are stopped for a while (20s by default), the eNodeB releases the UE and
instructs it to enter the idle mode by sending an RRC Connection Release message. The dedicated
cell-reselection priority information contained in the RRC Connection Release message is
consistent with the RAT/frequency priority group information corresponding to the SPID
configured on the eNodeB based on the UE's serving PLMN, as shown in Figure 11-2.
Figure 11-2 SPID contained in the RRC Connection Release message
3. Move the UE to the coverage area of neighboring cells. The UE reselects a neighboring cell with
the highest cell-reselection priority in the same way as it does normally.
12
None
Network Smart Sharing
12.1 Principles
NSA network sharing involves both 4G and 5G networks. Different service policies, such as camping
frequencies and voice policies, are required for LTE UEs and NSA DC UEs. Network Smart Sharing allows
different policies to be configured for LTE UEs and NSA DC UEs among different operators.
Network Smart Sharing is controlled by the FLEXIBLE_SHARING_SWITCH option of the
CellAlgoExtSwitch.OperatorFunSwitch parameter. In this release, Network Smart Sharing has the
following sub-functions:
Algorithms are optimized to allow PLMN-based cell policies. For details, see 12.1.1 PLMN-based
Algorithm Optimization.
Frequency selection for handover measurements of LTE UEs or NSA DC UEs
Selecting UEs whose PLMN is the same as that of the target cell for intra-LTE MLB
Frequency priorities for LTE or NSA DC UEs in connected mode can be configured based on PLMN
IDs. For details, see 12.1.2 Operator-specific Frequency Priorities for Coverage-based Handovers.
Operator-specific measurement and handover threshold offsets for services with different QCIs can
be configured. In this way, intra-RAT measurement and handover thresholds are differentiated
among operators. For details, see 12.1.3 Operator-specific UE-level Handover Thresholds.
When a UE of a secondary operator initiates a frequency-priority-based handover from an MOCN

cell to a cell of the secondary operator's PLMN, the handover is not subject to the MLB status of
the target cell. For details, see 12.1.4 Service Steering for UEs of Secondary Operators.
Operator-specific frequency-priority-based and service-based inter-frequency handovers can be

configured. For details, see 12.1.5 Operator-Specific Measurement for Frequency-priority-based and Service-
based Inter-frequency Handovers.
Operator-specific coverage-based inter-frequency handover measurement events can be

configured. For details, see 12.1.6 Operator-specific Measurement Events for Coverage-based Inter-frequency
Handovers.
12.1.1 PLMN-based Algorithm Optimization
PLMN-based algorithm optimization is controlled by the HoPlmnFilterOptSw option of the

CellHoParaCfg.CellHoAlgoSwitch parameter. This algorithm optimization includes:
In intra-LTE MLB, the eNodeB selects UEs with a PLMN the same as that of the target cell.
During frequency filtering and target cell selection, the eNodeB delivers frequencies of each
operator only based on intra-RAT or inter-RAT configurations. This function is applicable to
mobility algorithms, MLB, handovers or redirections for PCC anchoring, and cell reselection based
on SPID or operator dedicated priorities. Before this function takes effect, perform intra-RAT or
inter-RAT configurations.
Intra-RAT
Intra-RAT measurement frequency filtering targets at LTE or NSA DC UEs of different operators. Before
this function takes effect, the RatFreqPriorityGroup MO must be configured to specify a frequency
priority group, and the CellOp.RatFreqPriorityGroupId or CellOp.NsaDcRatFreqPriorityGrpId parameter

must be set to bind the frequency priority group to corresponding operators.
If the CellOp.RatFreqPriorityGroupId or CellOp.NsaDcRatFreqPriorityGrpId parameter corresponds to more
than one RatFreqPriorityGroup MO, the number of measurement frequencies for an LTE or NSA DC UE
to choose is the same as the number of MOs.
Inter-RAT
In inter-RAT measurement frequency selection, only the measurement frequencies of CDMA2000 can
be configured for LTE UEs and NSA DC UEs. Before this function takes effect, use the
RatFreqPriorityGroup MO to specify the CDMA2000 frequencies, and then use the
CellOp.RatFreqPriorityGroupId or CellOp.NsaDcRatFreqPriorityGrpId parameter to bind the CDMA2000
frequency to an operator.
Because there are a large number of CDMA2000 frequencies and CDMA2000 networks are rarely
involved in RAN sharing, configuring only one RatFreqPriorityGroup MO corresponding to the
CellOp.RatFreqPriorityGroupId or CellOp.NsaDcRatFreqPriorityGrpId parameter allows LTE UEs and NSA DC
UEs to filter all CDMA2000 frequencies.
12.1.2 Operator-specific Frequency Priorities for Coverage-based Handovers
Frequency priorities for LTE or NSA DC UEs in connected mode can be configured based on PLMN IDs
to implement UE-level frequency measurements for handovers. For details, see Mobility Management in
Connected Mode.
12.1.3 Operator-specific UE-level Handover Thresholds
Measurement and handover-related threshold offsets for services with different QCIs performed by LTE
UEs and NSA DC UEs can be configured based on operators' PLMNs. In this way, thresholds for intra-
RAT inter-frequency measurement and handovers as well as UTRAN frequency measurement and
handovers can be operator-specific and UE-type-specific. For details, see Mobility Management in Connected
Mode.
The CnOpQciEventParam.UserType parameter specifies the type of UEs for which the handover
threshold offset takes effect. The following table lists the events for which the operator-specific
threshold offsets can be configured and the final effective thresholds.
Table 12-1 Events for which the operator-specific threshold offsets can be configured and
final effective thresholds
Threshold Name Final Thresholdc Description
Thresholds related to e InterFreqHoGroup.A3InterFreqHoA RSRP threshold for event A1 rel

vent A1 for coverage-b 1ThdRsrp + CnOpQciEventParam. ated to A3-based inter-frequen
ased inter-frequency ha HandoverThldOffseta cy handovers
ndover
InterFreqHoGroup.A3InterFreqHoA RSRQ threshold for event A1 rel
1ThdRsrq+ CnOpQciEventParam. ated to A3-based inter-frequen
HandoverRsrqThldOffseta cy handovers
InterFreqHoGroup.InterFreqHoA1T RSRP threshold for event A1 rel

hdRsrp + CnOpQciEventParam.Ha ated to A4- or A5-based inter-fr
ndoverThldOffseta equency handovers
InterFreqHoGroup.InterFreqHoA1T RSRQ threshold for event A1 rel

hdRsrq + CnOpQciEventParam.Ha ated to A4- or A5-based inter-fr
ndoverRsrqThldOffseta equency handovers
Thresholds related to e InterFreqHoGroup.A3InterFreqHoA RSRP threshold for event A2 rel

vent A2 for coverage-b 2ThdRsrp + CnOperatorQciPara.In ated to A3-based inter-frequen
ased inter-frequency ha terFreqA2RsrpThldOffsetb + CnOpQc cy handovers
ndover iEventParam.HandoverThldOffseta
InterFreqHoGroup.A3InterFreqHoA RSRQ threshold for event A2 rel

2ThdRsrq + CnOpQciEventParam. ated to A3-based inter-frequen
HandoverRsrqThldOffseta cy handovers
InterFreqHoGroup.InterFreqHoA2T RSRP threshold for event A2 rel

hdRsrp + CnOperatorQciPara.Inter ated to A4- or A5-based inter-fr
FreqA2RsrpThldOffsetb+ CnOpQciEv equency handovers
entParam.HandoverThldOffseta
InterFreqHoGroup.InterFreqHoA2T RSRQ threshold for event A2 rel

hdRsrq + CnOpQciEventParam.Ha ated to A4- or A5-based inter-fr
ndoverRsrqThldOffseta equency handovers
Thresholds related to e InterFreqHoGroup.InterFreqHoA3O None

vent A3 for coverage-b ffset + CnOpQciEventParam.Hand
ased inter-frequency ha overThldOffseta
ndover
InterFreqHoGroup.InterFreqHoA3O None
ffset + CnOpQciEventParam.Hand
overRsrqThldOffseta
Thresholds related to e InterFreqHoGroup.InterFreqHoA4T None

vent A4 for coverage-b hdRsrp + EutranInterNFreq.IfHoTh
ased inter-frequency ha dRsrpOffset + CnOpQciEventPara
ndover m.HandoverThldOffseta
InterFreqHoGroup.InterFreqHoA4T None
hdRsrq + CnOpQciEventParam.Ha
ndoverRsrqThldOffseta
Threshold 1 for event A InterFreqHoGroup.InterFreqHoA5T None

5 for coverage-based in hd1Rsrp + EutranInterNFreq.InterF
ter-frequency handover reqHoA5Thd1RsrpOfs + EutranInter
NFreq.CovIfHoA5VolteThld1RsrpOfs +
CnOpQciEventParam.HandoverThl
dOffseta
hd1Rsrq + EutranInterNFreq.InterF
reqHoA5Thd1RsrqOfs + CnOpQciEv
entParam.HandoverRsrqThldOffseta
Threshold 2 for event A InterFreqHoGroup.InterFreqHoA4T None

5 for coverage-based in hdRsrp + EutranInterNFreq.IfHoTh
ter-frequency handover dRsrpOffset + EutranInterNFreq.C
ovIfHoA5VolteThld2RsrpOfs+ CnOpQ
ciEventParam.HandoverThldOffseta
hdRsrq + CnOpQciEventParam.Ha
ndoverRsrqThldOffseta
Event B1 for UTRAN InterRatHoUtranGroup.InterRatHo None

UtranB1ThdRscp + CnOpQciEventP
aram.HandoverThldOffseta
Thresholds related to e InterFreqHoGroup.FreqPriInterFreq None

vent A1 for frequency- HoA1ThdRsrp + CnOpQciEventPar
priority-based inter-fre am.HandoverThldOffseta
quency handover
Thresholds related to e InterFreqHoGroup.FreqPriInterFreq None

vent A2 for frequency- HoA2ThdRsrp + CnOpQciEventPar
priority-based inter-fre am.HandoverThldOffseta
quency handover
Thresholds related to e InterFreqHoGroup.InterFreqLoadBa None

vent A4 for frequency- sedHoA4ThdRsrp + CnOpQciEvent
priority-based measure Param.HandoverThldOffseta+Eutran
ment-based handover InterNFreq.FreqPriHoA4ThldRsrpOffs
et
a: When CnOpQciEventParam.HandoverThldOffset or CnOpQciEventParam.HandoverRsrqThldOffs

et is configured, corresponding CnOpQciEventParam.EventType and CnOpQciEventParam.Us
erType need to be selected.
b: When both CnOperatorQciPara.InterFreqA2RsrpThldOffset and CnOpQciEventParam.Handover
ThldOffset are set, thresholds related to event A2 for coverage-based handovers all take effec
t.
c: If the calculated RSRP threshold is lower than the protocol-specified minimum value (-140
dBm), the protocol-specified minimum value is used as the RSRP threshold. If the calculated
RSRP threshold exceeds the protocol-specified maximum value (-43 dBm), the protocol-spe
cified maximum value is used as the RSRP threshold. If the calculated RSRQ threshold is low
er than the protocol-specified minimum value (-20 dB), the protocol-specified minimum val
ue is used as the RSRQ threshold. If the calculated RSRQ threshold exceeds the protocol-spe
cified maximum value (-3 dB), the protocol-specified maximum value is used as the RSRQ th
reshold.
12.1.4 Service Steering for UEs of Secondary Operators
If the HoAdmitSwitch option of the CellMlbHo.MlbMatchOtherFeatureMode parameter is selected, some

unnecessary handover admission requests will be rejected when the cell is in the MLB state. As a result,
the handover preparation success rate is low. In the preceding scenario, the
MocnSecOpUeFreqPriInHoEhnSw option of the CellMlbHo.MlbMatchOtherFeatureMode parameter can
be selected so that frequency-priority-based handovers of secondary-operator UEs from an MOCN cell
to a cell of their own PLMN are not subject to the MLB status.
When an MOCN cell (functioning as the NSA anchor) hands over LTE UEs of a secondary
operator using this function and the peer end sets the local NSA anchor to the highest
priority, the switch for making frequency-priority-based handovers invalid for NSA DC UEs
must be configured. Otherwise, ping-pong handovers will occur for NSA DC UEs.
The frequency priorities of the source and target cells cannot be the highest for each other.
Otherwise, ping-pong handovers may occur for LTE UEs.
12.1.5 Operator-Specific Measurement for Frequency-priority-based and Service-based Inter-frequency Handovers
In RAN sharing with common carrier, the CellOpHoCfg MO can be used to configure operator-specific
frequency-priority-based handovers and service-based inter-frequency handovers. If no operator-
specific policy is configured, the handovers are performed in compliance with the cell configuration.
To enable operator-specific frequency-priority-based inter-frequency handovers, select the

FreqPriorIFHOSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter and the
FREQ_PRI_BASED_HO_SW option of the CellOpHoCfg.HoModeSwitch parameter.
To enable operator-specific service-based inter-frequency handovers, select the

ServiceBasedInterFreqHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter, the
SrvBasedInterFreqHoSw option of the CellAlgoSwitch.HoAllowedSwitch parameter, and the
SERV_BASED_INTER_FREQ_HO_SW option of the CellOpHoCfg.HoModeSwitch parameter.
12.1.6 Operator-specific Measurement Events for Coverage-based Inter-frequency Handovers
In RAN sharing with common carrier, operator-specific coverage-based inter-frequency handover

measurement events (including events A3, A4, and A5) can be configured. If no operator-specific policy
is configured, the handovers are performed in compliance with the cell configuration.
Coverage-based handover measurement events are specified by the
RatFreqPriorityGroup.CovBasedHoEventType parameter. If the inter-frequency measurement event
(specified by RatFreqPriorityGroup.CovBasedHoEventType) associated with the
CellOp.RatFreqPriorityGroupId or CellOp.NsaDcRatFreqPriorityGrpId parameter of a cell operator is not set
to SAME_AS_CELL_CONFIG, the cell operator-specific policy has taken effect.
12.1.7 PLMN-based Mobility Measurement Event Configuration
Mobility measurement events can be configured based on the PLMN IDs of different operators. In this
way, different triggering quantities for events A1 and A2 (including thresholds 1 and 2 for event A5)
can be set for different operators. If the CnoperatorHoCfg.InterFreqHoA1A2TrigQuan parameter is set to
a value other than NONE, the value of this parameter is used as the triggering quantity for events A1
and A2 (including thresholds 1 and 2 for event A5) of the operator. For details, see Mobility Management in
Connected Mode.
12.2.1 Benefits
In RAN sharing with common carrier, different operators can use different steering policies for UEs in
connected mode. Other benefits are the same as those provided by RAN sharing with common carrier.
For details, see 4.2.1 Benefits.
12.2.2 Impacts
Network Impacts
PLMN-based algorithm optimization: In RAN sharing scenarios, the service drop rate may decrease
and the throughput may increase.
Service steering for UEs of secondary operators: If the HoAdmitSwitch option of the
CellMlbHo.MlbMatchOtherFeatureMode parameter is selected for a heavily-loaded cell, the cell admits
frequency-priority-based incoming handovers of secondary operator's UEs. As a result, the gains of
MLB to neighboring cells decrease, and the handover preparation success rate increases. In this
way, user steering can be achieved in hybrid networking of MOCN and non-MOCN cells. A
neighboring cell admits incoming handover UEs of secondary operators, and therefore the cell
accommodates more UEs, increasing the handovers.
Other sub-functions have no impact on the network.
Function Impacts
None
12.3 Requirements
12.3.1 Licenses
licenses for the features listed in the following table.
RAT Feature ID Feature Nam Model Sales Unit NE

e
FDD LNOFD-16 Network S LT1S000NFS00 per cell Macro eNodeB

1331 mart Shari
ng
FDD LNOFD-16 Network S LT1STDNSSS99 per Carrier per p LampSite eNodeB

1331 mart Shari RRU
ng
12.3.2 Software
RAT Function Nam Function Switch Reference Description

e
FDD RAN sharing ENodeBSharingMode. RAN Sharing This function depends on

with commo ENodeBSharingMode RAN sharing with commo
n carrier n carrier.
FDD Network sma FLEXIBLE_SHARING_S RAN Sharing The sub-functions of net

rt sharing WITCH option of the C work smart sharing can ta
ellAlgoExtSwitch.Opera ke effect only when this o
torFunSwitch parameter ption is selected.
None
12.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
12.3.4 Others
None
Table 12-2 describes the parameters used for function activation specific to multi-operator SPID policy.
Paramete Parameter ID Option Setting Notes

r Name
Local Ce CellAlgoExtSwitch.LocalCel None None

ll ID lId
Operato CellAlgoExtSwitch.Operato FLEXIBLE_SHARING_ In RAN sharing with common c

r Functi rFunSwitch SWITCH arrier mode, it is recommende
on Switc d that this function be enabled
h if operators require flexible ste
ering and ANR is enabled.
Configure the operator-specific PLMN algorithm optimization function. Table 12-3 describes the
parameters related to this function.
Table 12-3 Parameters related to measurement frequency filtering
Local cell ID CellHoParaCfg.LocalC None None

ellId
Handover Algo Switc CellHoParaCfg.CellHo HoPlmnFilterOptSw In RAN sharing with c

h AlgoSwitch ommon carrier, if AN
R is enabled, select th
is option to ensure th
at during the delivery

of operator-specific fr
equencies, only frequ
encies available to th
e operator are deliver
ed.
Local tracking area ID CellOp.TrackingAreaId None None
RAT Frequency Priorit CellOp.RatFreqPriorityGr None Set different RAT/freq

y Group ID oupId uency priority groups
for LTE UEs of differe
nt operators.
NSA DC RAT Frequen CellOp.NsaDcRatFreqPri None Set different RAT/freq

cy Priority Group ID orityGrpId uency priority groups
for NSA DC UEs of dif
ferent operators.
DL Earfcn or Bandclas RatFreqPriorityGrou None None

s p.DlEarfcn
RAT frequency priorit RatFreqPriorityGrou None None

y group ID p.RatFreqPriorityGroupId
Table 12-4 describes the parameters that must be set to configure the connected-mode frequency
priority settings for coverage-based inter-frequency handovers.
Table 12-4 Parameters that must be set to configure the frequency priorities of connected-
mode UEs for coverage-based inter-frequency handovers
Multi Op Freq Priority CellAlgoSwitch.MultiC None It is recommended th

For Connected Mode nConnFreqPriSw at the switch be turne
Sw d on and operator- a
nd UE-specific freque
ncy priorities be set w
hen inter-operator ha
ndovers need to be r
educed in RAN sharin
g with common carrie
r.
Local tracking area ID CellOp.TrackingAreaId None None
RAT Frequency Priorit CellOp.RatFreqPriorityGr None Set different RAT/freq

y Group ID oupId uency priority groups
for LTE UEs of differe
nt operators.
NSA DC RAT Frequen CellOp.NsaDcRatFreqPri None Set different RAT/freq

cy Priority Group ID orityGrpId uency priority groups
for NSA DC UEs of dif
ferent operators.
DL Earfcn or Bandclas RatFreqPriorityGrou None None

s p.DlEarfcn
RAT frequency priorit RatFreqPriorityGrou None None

y group ID p.RatFreqPriorityGroupId
Frequency Priority for RatFreqPriorityGrou None None

Connected Mode p.ConnFreqPriority
Table 12-5 describes the related parameters for configuring UE-level handover thresholds.
Table 12-5 Parameters for configuring UE-level handover thresholds
CN Operator ID CnOpQciEventPara None None

m.CnOperatorId
QoS Class Indication CnOpQciEventPara None None

m.Qci
User Type CnOpQciEventPara None In RAN sharing scena

m.UserType rios, set this paramet
er when setting opera
tor-specific and UE-s
pecific handover thre
shold offsets is requir
ed.
Event Type CnOpQciEventPara None In RAN sharing, set th

m.EventType is parameter when th
e RSRP thresholds for
events A1, A3, A4, an
d A5 related to cover
age-based inter-frequ
ency handovers, the
RSCP threshold for ev
ent B1 related to cove
rage-based handover
s from E-UTRAN to U
Handover Threshold CnOpQciEventPara None
TRAN, and the RSRP t
Offset m.HandoverThldOffset
hresholds for events
A1, A2, and A4 relate
d to frequency-priorit
y-based inter-frequen
cy handovers need to
be flexibly configured
for different operator
s.
Table 12-6 describes the related parameters for configuring the UE service steering policy of the
secondary operator.
Table 12-6 Parameters for configuring the UE service steering policy of secondary operators
Local cell ID CellMlbHo.LocalCellId None None
MLB Match Other Fea CellMlbHo.MlbMatchOt MocnSecOpUeFreqP If the HoAdmitSwitc

ture Mode herFeatureMode riInHoEhnSw h option of the CellM
lbHo.MlbMatchOtherFeat
ureMode parameter is s
elected,
handover admission r
equests will be reject
ed when the cell is in
the MLB state. As a re
sult, the handover pre
paration success rate
is low. In this case, th
e MocnSecOpUeFreq
PriInHoEhnSw optio
n of the CellMlbHo.Ml
bMatchOtherFeatureMode
parameter can be sel
ected so that a UE of
a secondary operator
is not affected by the
MLB status of the tar
get cell when initiatin
g a frequency-priority
-based handover fro
m an MOCN cell to a
cell of its own PLMN.
Table 12-7 describes the parameters for configuring the UE service steering policy of secondary
operators.
Table 12-7 Operator-specific policies for frequency-priority-based and service-based inter-
frequency handovers
Handover Mode Swit CellOpHoCfg.HoMode FREQ_PRI_BASED_H None

ch Switch O_SW or SERV_BASE
D_INTER_FREQ_HO_
SW
Table 12-8 describes the parameters related to coverage-based inter-frequency handover measurement
events.
Table 12-8 Events related to coverage-based inter-frequency handovers
Coverage-based Han RatFreqPriorityGrou None None

dover Event Type p.CovBasedHoEventType
The activation command example is as follows:
//Turning on the network smart sharing switch

MOD CELLALGOEXTSWITCH: LocalCellId=0,OperatorFunSwitch=FLEXIBLE_SHARING_SWITCH-1;
The optimization command example is as follows:
//Enabling operator-specific PLMN algorithm optimization in RAN sharing with common carrier
//Configuring frequency priorities of connected-mode UEs for coverage-based handovers in
RAN sharing with common carrier
MOD CELLALGOSWITCH: LocalCellId=0, MultiCnConnFreqPriSw=ON;
ADD RatFreqPriorityGroup:RatFreqPriorityGroupId=0,RatType=EUTRAN, DlEarfcn=1234,
ConnFreqPriority=7;
ConnFreqPriority=4;
ConnFreqPriority=2;
//Configuring operator-specific handover thresholds in RAN sharing with common carrier
ADD CnOpQciEventParam: CnOperatorId=0, Qci=1, EventType=INTER_FREQ_HO_A1,
HandoverThldOffset=-20, UserType=NSA_DC_UE-1;
//Configuring service steering for UEs of a secondary operator in RAN sharing with common
carrier mode (If the local cell is an MOCN cell, UEs of the secondary operator are not controlled
by the MLB status of the target cell when initiating a frequency-priority-based handover from
the MOCN cell to its PLMN.)
MOD CELLMLBHO:LocalCellId=0,
MlbMatchOtherFeatureMode=MocnSecOpUeFreqPriInHoEhnSw-1;
//Configuring the frequency-priority-based and service-based inter-frequency handover
policies in RAN sharing with common carrier
ADD CELLOPHOCFG: LocalCellId=0, CnOperatorId=0,
HoModeSwitch=FREQ_PRI_BASED_HO_SW-1;
ADD CELLOPHOCFG: LocalCellId=0, CnOperatorId=0, HoModeSwitch=
SERV_BASED_INTER_FREQ_HO_SW-1;
//Configuring event A3/A4 for coverage-based inter-frequency handovers in RAN sharing with
common carrier
CovBasedHoEventType=EVENT_A3;
CovBasedHoEventType=EVENT_A4;
CovBasedHoEventType=SAME_AS_CELL_CONFIG;

Maintenance.
Prerequisites
The prerequisite functions have been activated.
The subfunctions have been activated.
Verification Method
Operator-specific PLMN algorithm optimization

Using signaling tracing: If the eNodeB receives measurement reports from a UE and the
frequencies (MeasObjectToAddModList) carried in the MeasConfig IE in the RRC Connection
Reconfiguration message sent from the eNodeB to the UE are all included in the PLMN's
frequencies supported by the UE, this function has been activated.
Operator-specific frequency priorities for coverage-based handovers

Using signaling tracing: After the eNodeB receives measurement reports from two co-located UEs
of different operators, the measObjectId carried by the MeasConfig IE in the RRC Connection
Reconfiguration messages sent from the eNodeB to the two UEs are different.
Operator-specific handover threshold setting

Using signaling tracing: If the eNodeB receives measurement reports from a UE and the
measurement report threshold (ReportConfigToAddModList) carried by the MeasConfig IE in the
RRC Connection Reconfiguration message sent from the eNodeB to the UE is the result of the
corresponding handover threshold plus an offset, this function has been activated.
UE service steering policy of the secondary operator

Using the performance counter: If the values of the counters listed in Table 12-9 are greater than or
equal to the values before the function is enabled, this function has taken effect.
Table 12-9 Counters related to the UE service steering policy of the secondary operator
function
Counter ID Counter Name
1526729484 L.HHO.InterFreq.FreqPri.ExecSuccOut
Operator-specific measurements for frequency-priority-based and service-based inter-frequency

handovers
Compare the messages received by two collocated UEs of the same model served by different
operators. If the MeasConfig IE in the RRC Connection Reconfiguration message received by one
UE contains the measurement for frequency-priority-based and service-based handovers while that
received by the other UE does not contain such measurement, this function has taken effect.
Operator-specific measurement events for coverage-based inter-frequency handovers
Compare the messages received by two collocated UEs of the same model served by different
operators. If the reportConfigId contained in the MeasConfig IE of the RRC Connection
Reconfiguration messages received by the two UEs differs, this function has taken effect.
The following KPIs can be used for network monitoring:
Inter-Frequency Handover Out Success Rate
Call Drop Rate (VoIP)
13
Service Drop Rate
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.
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?
1. Open the EXCEL file of parameter reference.
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.
3. Click OK. All parameters related to the feature are displayed.
FAQ 2: How do I find the information about a certain reserved parameter from the used reserved
parameter list?
1. Open the EXCEL file of the used reserved parameter list.
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,
14
including the meaning, values, impacts, and product version in which it is activated for use.
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.
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?
1. Open the EXCEL file of performance counter reference.
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.
15
3. Click OK. All counters related to the feature are displayed.
Glossary
16
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Reference Documents
1. 3GPP TS 23.122, "PLMN selection process"
2. 3GPP TS 23.203, "Standardized QCI characteristics"
3. 3GPP TS 23.251, "Overview"
4. 3GPP TS 36.413, "HANDOVER REQUEST"
5. 3GPP TS 36.423, "HANDOVER REQUEST"
6. 3GPP TS 36.331, "Message definitions"
7. Flexible User Steering
8. eMBMS
9. Idle Mode Management
10. Mobility Management in Connected Mode
11. Admission and Congestion Control
12. Scheduling
13. S1 and X2 Self-Management
14. IPv4 Transmission
15. IP eRAN Engineering Guide
16. Transmission Resource Management
17. Base Station Supporting Multi-operator PKI
18. Cell Management
19. Intra-RAT Mobility Load Balancing
20. ANR Management
21. CSPC
22. Relay
23. S1-flex
24. VoLTE
25. WBB
26. Uplink Coordinated Scheduling
27. LTE FDD and NR Uplink Spectrum Sharing
28. Interference Detection and Suppression

RAN Sharing 4g

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

RAN Sharing 4g

Uploaded by

Copyright:

Available Formats

3/14/24, 2:31 PM HedEx Startpage

eRAN19.1 FDD Feature Documentation

For any question, please contact us.

4.13.2 RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. All rights reserved.

Huawei Technologies Co., Ltd.

5 RAN Sharing with Dedicated Carrier

6 RAN Sharing with Special Dedicated Carrier (FDD)

7 Hybrid RAN Sharing

9 Fair User Sharing (FDD)

10 MOCN Cell Reselection Priority Configuration

11 Multi-Operator SPID Policy

12 Network Smart Sharing

1.1 eRAN19.1 04 (2023-08-23)

This issue includes the following changes.

Revised descriptions in this document.

1.2 eRAN19.1 03 (2023-06-29)

This issue includes the following changes.

Revised descriptions in this document.

1.3 eRAN19.1 02 (2023-04-28)

This issue includes the following changes.

Change Description Parameter Change RAT Base Station Model

Revised descriptions in this document.

1.4 eRAN19.1 01 (2023-03-09)

This issue includes the following changes.

1.5 eRAN19.1 Draft A (2022-12-30)

This issue introduces the following changes to eRAN18.1 01 (2022-03-08).

About This Document

2.1 General Statements

This document is intended to acquaint readers with:

The technical principles of features and their related parameters

2.2 Applicable RAT

This document applies to FDD.

2.3 Features in This Document

This document describes the following FDD features.

Feature ID Feature Name Chapter/Section

LOFD-070206 Hybrid RAN Sharing 7 Hybrid RAN Sharing

LOFD-001086 RAN Sharing by More O 8 RAN Sharing by More Operators

LOFD-070213 Fair User Sharing 9 Fair User Sharing (FDD)

LOFD-001112 MOCN Flexible Priority B 10 MOCN Cell Reselection Priority Configuration

LOFD-070210 Multi Operators SPID Po 11 Multi-Operator SPID Policy

Operators share the infrastructure of a site.

Operators share network resources by allowing national or international roaming.

Operators jointly invest in the construction of a single wireless network.

Huawei eNodeBs support the following modes:

Independent operator mode

RAN sharing with common carrier

RAN sharing with dedicated carrier

Hybrid RAN sharing

Independent Operator Mode

Assume that a UE subscribes to services of operator A. Independent operator mode is described as

3.2 Network Architecture

RAN Sharing Architectures

Figure 3-2 Architecture of MOCN

Figure 3-3 Architecture of GWCN

Table 3-1 Network elements (NEs)

Shared OSS The operations support system (OSS) is an NE management system.

Table 3-2 Interfaces

S1 Connects the eNodeB and EPC. S1 is divided into S1-C (control-plan

X2 Connects eNodeBs. X2 consists of the control plane and user plane.

S11 Connects the MME and S-GW.

Comparison Between MOCN and GWCN