RAN Sharing (eRAN13.1 - 05)

eRAN
RAN Sharing Feature Parameter

Description
Issue 05
Date 2018-11-07
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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 Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks 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: http://www.huawei.com
Email: support@huawei.com
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. i

eRAN
RAN Sharing Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN13.1 05 (2018-11-07)............................................................................................................................................1
1.2 eRAN13.1 04 (2018-08-27)............................................................................................................................................2
1.3 eRAN13.1 03 (2018-06-30)............................................................................................................................................2
1.4 eRAN13.1 02 (2018-05-25)............................................................................................................................................3
1.5 eRAN13.1 01 (2018-04-10)............................................................................................................................................3
1.6 eRAN13.1 Draft A (2018-01-15) (FDD)........................................................................................................................4
2 About This Document.................................................................................................................. 6

2.1 Applicable RAT ............................................................................................................................................................. 6
2.2 Features in This Document.............................................................................................................................................6
2.3 Feature Differences Between NB-IoT and FDD............................................................................................................ 7
3 General Principles......................................................................................................................... 8
3.1 Overview........................................................................................................................................................................ 8
3.2 Network Architecture..................................................................................................................................................... 9
4 RAN Sharing with Common Carrier....................................................................................... 13

4.1 Principles...................................................................................................................................................................... 13
4.1.1 Overview................................................................................................................................................................... 13
4.1.2 NE Functions............................................................................................................................................................. 14
4.1.3 Idle Mode Management.............................................................................................................................................15
4.1.3.1 System Information Broadcast............................................................................................................................... 15
4.1.3.2 EPC Selection......................................................................................................................................................... 18
4.1.3.3 Fairness Guarantee for Roaming............................................................................................................................ 19
4.1.3.4 Paging..................................................................................................................................................................... 21
4.1.3.5 Redirection..............................................................................................................................................................21
4.1.3.6 Cell Selection and Reselection............................................................................................................................... 21
4.1.4 Mobility Management in Connected Mode...............................................................................................................24
4.1.4.1 Configuration of Shared Neighboring Cells........................................................................................................... 24
4.1.4.2 Outgoing Handover................................................................................................................................................ 25
4.1.4.3 Incoming Handover................................................................................................................................................ 26
4.1.4.4 Operator-specific Selection of Mobility Policies................................................................................................... 26
4.1.5 Feature and Capacity Management........................................................................................................................... 27
4.1.5.1 Feature License.......................................................................................................................................................27
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
4.1.5.2 Capacity License.....................................................................................................................................................27

4.1.6 Fair Sharing of Air Interface Resources.................................................................................................................... 29
4.1.6.1 Admission Control..................................................................................................................................................31
4.1.6.2 Congestion Control.................................................................................................................................................31
4.1.6.3 Scheduling Policies.................................................................................................................................................32
4.1.6.4 MLB........................................................................................................................................................................32
4.1.7 NB-IoT User-Plane UE Context Storage Management.............................................................................................32
4.1.8 ANR Management..................................................................................................................................................... 32
4.1.9 OSS Management...................................................................................................................................................... 33
4.1.9.1 Configuration Management.................................................................................................................................... 33
4.1.9.2 Fault Management.................................................................................................................................................. 33
4.1.9.3 Performance Management...................................................................................................................................... 33
4.1.10 Transmission Networking........................................................................................................................................34
4.1.10.1 Transmission Port Planning.................................................................................................................................. 34
4.1.10.2 Transmission Link Setup...................................................................................................................................... 34
4.1.10.3 Dynamic Sharing of Uplink Transmission Bandwidth.........................................................................................39
4.1.10.4 VLAN Planning.................................................................................................................................................... 39
4.1.11 Multi-operator PKI.................................................................................................................................................. 39
4.2 Network Analysis......................................................................................................................................................... 39
4.2.1 Benefits...................................................................................................................................................................... 39
4.2.2 Impacts.......................................................................................................................................................................40
4.3 Requirements................................................................................................................................................................ 41
4.3.1 Licenses..................................................................................................................................................................... 41
4.3.2 Software.....................................................................................................................................................................42
4.3.3 Hardware................................................................................................................................................................... 43
4.3.4 Others.........................................................................................................................................................................44
4.4 Operation and Maintenance (FDD).............................................................................................................................. 44
4.4.1 Data Configuration.................................................................................................................................................... 44
4.4.1.1 Data Preparation..................................................................................................................................................... 44
4.4.1.2 Using MML Commands......................................................................................................................................... 57
4.4.1.3 Using the CME....................................................................................................................................................... 60
4.4.2 Activation Verification.............................................................................................................................................. 60
4.4.3 Network Monitoring.................................................................................................................................................. 61
5 RAN Sharing with Dedicated Carrier..................................................................................... 67

5.1 Principles...................................................................................................................................................................... 67
5.1.1 Overview................................................................................................................................................................... 67
5.1.2 NE Functions............................................................................................................................................................. 68
5.1.4 NB-IoT User-Plane UE Context Storage Management (FDD)................................................................................. 69
5.1.5 OSS Management...................................................................................................................................................... 69
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. iii

eRAN

5.1.6 Transmission Networking..........................................................................................................................................69
5.1.6.1 Transmission Port Planning.................................................................................................................................... 69
5.1.6.2 Transmission Link Setup........................................................................................................................................ 69
5.1.6.3 Dynamic Sharing of Uplink Transmission Bandwidth...........................................................................................73
5.1.6.4 VLAN Planning...................................................................................................................................................... 73
5.1.7 Multi-operator PKI.................................................................................................................................................... 73
5.2.1 Benefits...................................................................................................................................................................... 73
5.2.2 Impacts.......................................................................................................................................................................74
5.3 Requirements................................................................................................................................................................ 74
5.3.1 Licenses..................................................................................................................................................................... 74
5.3.2 Software.....................................................................................................................................................................75
5.3.3 Hardware................................................................................................................................................................... 76
5.3.4 Others.........................................................................................................................................................................76
5.4 Operation and Maintenance..........................................................................................................................................76
5.4.1 Data Configuration (FDD).........................................................................................................................................76
5.4.1.3 Using the CME....................................................................................................................................................... 82
5.4.3 Network Monitoring.................................................................................................................................................. 84
6 RAN Sharing with Special Dedicated Carrier (FDD).......................................................... 85

6.1 Principles...................................................................................................................................................................... 85
6.1.1 Overview................................................................................................................................................................... 85
6.1.2 NE Functions............................................................................................................................................................. 86
6.1.3 Idle Mode Management.............................................................................................................................................86
6.1.3.1 System Information Broadcast............................................................................................................................... 86
6.1.3.2 EPC Selection......................................................................................................................................................... 86
6.1.3.3 Fairness Guarantee for Roaming............................................................................................................................ 86
6.1.3.4 Paging..................................................................................................................................................................... 86
6.1.3.5 Redirection..............................................................................................................................................................86
6.1.3.6 Cell Selection and Reselection............................................................................................................................... 87
6.1.4 Mobility Management in Connected Mode...............................................................................................................87
6.1.6 Fair Sharing of Air Interface Resources.................................................................................................................... 87
6.1.7 ANR Management..................................................................................................................................................... 88
6.1.8 OSS Management...................................................................................................................................................... 88
6.1.9 Transmission Networking..........................................................................................................................................88
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
6.1.10 Multi-operator PKI.................................................................................................................................................. 89

6.2.1 Benefits...................................................................................................................................................................... 89
6.2.2 Impacts.......................................................................................................................................................................89
6.3 Requirements................................................................................................................................................................ 89
6.3.1 Licenses..................................................................................................................................................................... 89
6.3.2 Software.....................................................................................................................................................................89
6.3.3 Hardware................................................................................................................................................................... 90
6.3.4 Others.........................................................................................................................................................................90
6.4 Operation and Maintenance..........................................................................................................................................90
6.4.1 Data Configuration.................................................................................................................................................... 90
6.4.1.3 Using the CME....................................................................................................................................................... 98
6.4.3 Network Monitoring................................................................................................................................................ 100
7 Hybrid RAN Sharing................................................................................................................ 101

7.1 Principles.................................................................................................................................................................... 101
7.1.1 Overview................................................................................................................................................................. 101
7.1.2 NE Functions........................................................................................................................................................... 103
7.1.3 Idle Mode Management...........................................................................................................................................104
7.1.3.1 System Information Broadcast............................................................................................................................. 104
7.1.3.2 EPC Selection....................................................................................................................................................... 104
7.1.3.3 Fairness Guarantee for Roaming.......................................................................................................................... 104
7.1.3.4 Paging................................................................................................................................................................... 104
7.1.3.5 Redirection............................................................................................................................................................105
7.1.3.6 Cell Selection and Reselection............................................................................................................................. 105
7.1.4 Mobility Management in Connected Mode.............................................................................................................105
7.1.5 Feature and Capacity Management......................................................................................................................... 105
7.1.5.1 Feature Control..................................................................................................................................................... 105
7.1.5.2 Capacity Control...................................................................................................................................................105
7.1.6 Fair Sharing of Air Interface Resources.................................................................................................................. 105
7.1.7 ANR Management................................................................................................................................................... 106
7.1.8 OSS Management.................................................................................................................................................... 106
7.1.8.1 Configuration Management.................................................................................................................................. 106
7.1.8.2 Fault Management................................................................................................................................................ 106
7.1.8.3 Performance Management.................................................................................................................................... 106
7.1.9 Transmission Networking........................................................................................................................................106
7.1.9.1 Transmission Port Planning.................................................................................................................................. 107
7.1.9.2 Transmission Link Setup...................................................................................................................................... 107
7.1.9.3 Dynamic Sharing of Uplink Transmission Bandwidth.........................................................................................114
7.1.9.4 VLAN Planning.................................................................................................................................................... 114
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. v

eRAN
7.1.10 Multi-operator PKI................................................................................................................................................ 114

7.2 Network Analysis....................................................................................................................................................... 114
7.2.1 Benefits.................................................................................................................................................................... 114
7.2.2 Impacts.....................................................................................................................................................................114
7.3 Requirements.............................................................................................................................................................. 115
7.3.1 Licenses................................................................................................................................................................... 115
7.3.2 Software................................................................................................................................................................... 115
7.3.3 Hardware..................................................................................................................................................................117
7.3.4 Others.......................................................................................................................................................................117
7.4 Operation and Maintenance........................................................................................................................................ 117
7.4.1 Data Configuration (FDD).......................................................................................................................................117
7.4.1.1 Data Preparation................................................................................................................................................... 117
7.4.1.2 Using MML Commands....................................................................................................................................... 130
7.4.1.3 Using the CME..................................................................................................................................................... 132
7.4.2 Activation Verification............................................................................................................................................ 132
8 RAN Sharing by More Operators...........................................................................................135

8.1 Principles.................................................................................................................................................................... 135
8.2.1 Benefits.................................................................................................................................................................... 135
8.2.2 Impacts.....................................................................................................................................................................135
8.3 Requirements.............................................................................................................................................................. 135
8.3.1 Licenses................................................................................................................................................................... 135
8.3.2 Software...................................................................................................................................................................136
8.3.3 Hardware................................................................................................................................................................. 136
8.3.4 Others.......................................................................................................................................................................137
8.4 Operation and Maintenance........................................................................................................................................137
8.4.1 Data Configuration.................................................................................................................................................. 137
8.4.1.3 Using the CME..................................................................................................................................................... 137
9 Fair User Sharing (FDD)...........................................................................................................139

9.1 Principles.................................................................................................................................................................... 139
9.2.1 Benefits.................................................................................................................................................................... 141
9.2.2 Impacts.....................................................................................................................................................................141
9.3 Requirements.............................................................................................................................................................. 141
9.3.1 Licenses................................................................................................................................................................... 141
9.3.2 Software...................................................................................................................................................................142
9.3.3 Hardware................................................................................................................................................................. 142
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
9.3.4 Others.......................................................................................................................................................................143
9.4 Operation and Maintenance........................................................................................................................................143
9.4.1 Data Configuration.................................................................................................................................................. 143
9.4.1.3 Using the CME..................................................................................................................................................... 144
10 MOCN Cell Reselection Priority Configuration............................................................... 146

10.1 Principles.................................................................................................................................................................. 146
10.2 Network Analysis..................................................................................................................................................... 147
10.2.1 Benefits.................................................................................................................................................................. 147
10.2.2 Impacts...................................................................................................................................................................147
10.3 Requirements............................................................................................................................................................ 148
10.3.1 Licenses................................................................................................................................................................. 148
10.3.2 Software.................................................................................................................................................................149
10.3.3 Hardware............................................................................................................................................................... 149
10.3.4 Others.....................................................................................................................................................................149
10.4 Operation and Maintenance......................................................................................................................................150
10.4.1 Data Configuration................................................................................................................................................ 150
10.4.1.1 Data Preparation................................................................................................................................................. 150
10.4.1.2 Using MML Commands..................................................................................................................................... 153
10.4.1.3 Using the CME................................................................................................................................................... 154
10.4.2 Activation Verification.......................................................................................................................................... 154
10.4.3 Network Monitoring.............................................................................................................................................. 155
11 Multi-Operator SPID Policy..................................................................................................156

11.1 Principles.................................................................................................................................................................. 156
11.2 Network Analysis..................................................................................................................................................... 156
11.2.1 Benefits.................................................................................................................................................................. 156
11.2.2 Impacts...................................................................................................................................................................157
11.3 Requirements............................................................................................................................................................ 157
11.3.1 Licenses................................................................................................................................................................. 157
11.3.2 Software................................................................................................................................................................. 157
11.3.3 Hardware................................................................................................................................................................158
11.3.4 Others.....................................................................................................................................................................159
11.4 Operation and Maintenance...................................................................................................................................... 159
11.4.1 Data Configuration................................................................................................................................................ 159
11.4.1.1 Data Preparation................................................................................................................................................. 159
11.4.1.2 Using MML Commands..................................................................................................................................... 160
11.4.1.3 Using the CME................................................................................................................................................... 161
11.4.2 Activation Verification...........................................................................................................................................161
11.4.3 Network Monitoring.............................................................................................................................................. 162
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. vii

eRAN
12 Parameters................................................................................................................................. 163
13 Counters.................................................................................................................................... 287
14 Glossary..................................................................................................................................... 558
15 Reference Documents............................................................................................................. 559
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
RAN Sharing Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN13.1 05 (2018-11-07)

This issue includes the following changes.
Technical Changes
Change Description Parameter RAT Base Station
Change Model
Added static allocation of RB Modified FDD l 3900 and 5900

resources in proportions in RAN parameters: series base
sharing with common carrier. CellAlgoSwitc stations
For details, see 4.1.6 Fair h.RanShareMo l DBS3900
Sharing of Air Interface deSwitch LampSite and
Resources. DBS5900
LampSite
l BTS3912E
l BTS3911E
Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 1

eRAN

Change Model
Added the mutual impact None FDD l 3900 and 5900

between RAN sharing with series base
common carrier and out-of- stations
band/in-band relay. For details, l DBS3900
see 4.2.2 Impacts. LampSite and
DBS5900
LampSite
l BTS3912E
l BTS3911E
Added the mutual impact None FDD l 3900 and 5900

between RAN sharing with series base
dedicated carrier and out-of- stations
band/in-band relay. For details, l DBS3900
see 5.2.2 Impacts. LampSite and
DBS5900
LampSite
l BTS3912E
l BTS3911E
Editorial Changes
None
1.2 eRAN13.1 04 (2018-08-27)

Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.3 eRAN13.1 03 (2018-06-30)

Technical Changes
None

eRAN
Editorial Changes
For FDD, there is no change.
1.4 eRAN13.1 02 (2018-05-25)

Technical Changes
None
Editorial Changes
Revised descriptions in 4.1.3.3 Fairness Guarantee for Roaming.
1.5 eRAN13.1 01 (2018-04-10)

Technical Changes
Change Model
Added the mutually exclusive None FDD l 3900 and 5900

relationship between RAN series base
sharing with common carrier stations
and in-band relay. For details, l DBS3900
see 4.3.2 Software. LampSite and
DBS5900
LampSite
l BTS3912E
l BTS3911E
l BTS3203E
l BTS3202E

relationship between RAN series base
sharing with dedicated carrier stations
and in-band relay. For details, l DBS3900
see 5.3.2 Software. LampSite and
DBS5900
LampSite

eRAN

Change Model

relationship between hybrid series base
RAN sharing and in-band relay. stations
For details, see 7.3.2 Software. l DBS3900
LampSite and
DBS5900
LampSite
Editorial Changes
None
1.6 eRAN13.1 Draft A (2018-01-15) (FDD)

This issue introduces the following changes to eRAN12.1 03 (2017-06-29).
Technical Changes
Change Description Parameter Change Base Station Model
Added support for sharing of Added the LicenseSharingPo- l 3900 and 5900
RRC_CONNECTED UE licy.UserNumSharingGrou- series base stations
resources within an pId parameter. l DBS3900
RRC_CONNECTED UE LampSite and
number sharing group. For DBS5900
details, see 4 RAN Sharing LampSite
with Common Carrier and 9
Fair User Sharing (FDD). l BTS3912E
l BTS3911E
l BTS3203E
l BTS3202E
Added the DBS3900 LampSite None DBS3900 LampSite

and DBS5900 LampSite to the and DBS5900
base station models that support LampSite
NB-IoT RAN sharing with
common carrier and NB-IoT
RAN sharing with dedicated
carrier. For details, see 4.3.3
Hardware and 5.3.3
Hardware.

eRAN
Editorial Changes
Reorganized this document using a new template.

eRAN
RAN Sharing Feature Parameter Description 2 About This Document
2 About This Document
2.1 Applicable RAT

This document applies to FDD/NB-IoT.
2.2 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LOFD-001036 RAN Sharing with 4 RAN Sharing with Common Carrier

Common Carrier
LOFD-001037 RAN Sharing with 5 RAN Sharing with Dedicated Carrier

Dedicated Carrier
LOFD-070206 Hybrid RAN Sharing 7 Hybrid RAN Sharing
LOFD-001086 RAN Sharing by More 8 RAN Sharing by More Operators

Operators
LOFD-070213 Fair User Sharing 9 Fair User Sharing (FDD)
LOFD-001112 MOCN Flexible 10 MOCN Cell Reselection Priority

Priority Based Configuration
Camping
LOFD-070210 Multi Operators SPID 11 Multi-Operator SPID Policy

Policy
This document describes the following NB-IoT features.

eRAN
RAN Sharing Feature Parameter Description 2 About This Document
Feature ID Feature Name Section
MLOFD-121251 NB-IoT RAN Sharing 4 RAN Sharing with Common Carrier

with Common Carrier
MLOFD-121252 NB-IoT RAN Sharing 5 RAN Sharing with Dedicated Carrier

with Dedicated Carrier
2.3 Feature Differences Between NB-IoT and FDD

NB-IoT Feature FDD Feature Difference Section
MLOFD-121251 LOFD-001036 RAN NB-IoT does not 4 RAN Sharing

NB-IoT RAN Sharing with support RAN with Common
Sharing with Common Carrier sharing by more Carrier
Common Carrier operators, fair user
sharing, MOCN cell
reselection priority
configuration, multi-
operator SPID
policy, or fair
sharing of air
interface resources.
FDD does not
support user-plane
UE context storage
management.
MLOFD-121252 LOFD-001037 RAN NB-IoT does not 5 RAN Sharing

NB-IoT RAN Sharing with support RAN with Dedicated
Sharing with Dedicated Carrier sharing by more Carrier
Dedicated Carrier operators, fair user
sharing, multi-
operator SPID
policy, or RAN
sharing with special
dedicated carrier.
FDD does not
support user-plane
UE context storage
management.

eRAN
RAN Sharing Feature Parameter Description 3 General Principles
3 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:
l Operators share the infrastructure of a site.
l Mobile network operators (MNOs) share their RANs and CNs with mobile virtual
network operators (MVNOs).
l Operators share network resources by allowing national or international roaming.
l Operators jointly invest in the construction of a single wireless network.
Huawei eNodeBs support the following modes:
l Independent operator mode
l RAN sharing with common carrier
l RAN sharing with dedicated carrier
l 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.

eRAN
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:
l 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.
l 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.
l 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.
NOTE
NB-IoT does not support handovers.
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:
l Multi-operator core network (MOCN): Multiple operators share the RAN, but not the
evolved packet core (EPC), as shown in Figure 3-2.
l 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

eRAN
MME must support sharing among operators and can deliver the IE Handover
Restriction List to eNodeBs.
Figure 3-2 Architecture of MOCN

eRAN
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

operators either have their own EPCs (MOCN) or share the same
EPC (GWCN).
Shared eNodeB An FDD eNodeB can be shared by multiple operators if RAN

sharing with common carrier, RAN sharing with dedicated carrier,
RAN sharing 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 shared and non-shared eNodeBs.
NMS The shared OSS connects to the network management systems

(NMSs) of multiple operators over northbound interfaces.

eRAN
Table 3-2 Interfaces

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

plane interface between the eNodeB and MME) and S1-U (user-
plane interface 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
their 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:
l 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 and RAN sharing with dedicated carrier.
– Both require support from the eNodeB and the OSS.
l 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.
NOTE
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.

eRAN
RAN Sharing Feature Parameter Description 4 RAN Sharing with Common Carrier
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:
l One operator owns spectrum resources and shares them with others.
l 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.

eRAN
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:
l NE functions
l Idle mode management
l Mobility management in connected mode
l Feature and capacity management
l Fair sharing of air interface resources
l Automatic neighbor relation (ANR) management
l OSS management
l Transmission networking
l 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:
l Decode system information broadcast in a shared cell

l 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.

eRAN
eNodeB
To support RAN sharing with common carrier, each eNodeB must support the following
functions:
l Setup of an S1 interface with an MME shared by operators or exclusively used by a
specific operator
l 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
l MME selection for a UE based on the PLMN ID selected by the UE
l Configuration of all PLMNs of a shared intra- and inter-RAT neighboring cell
l Mobility management on a per operator basis
l Reporting of certain counters and alarms on a per operator basis
NOTE
NB-IoT does not support mobility management on a per operator basis.
MME
In RAN sharing with common carrier, the MMEs of RAN sharing operators use unique global
eNodeB IDs and E-UTRAN cell global identifiers (ECGIs) to address shared eNodeBs and
cells. An eNodeB uses the global eNodeB ID and ECGI when communicating with MMEs of
the operators over the S1 interfaces. The global eNodeB ID consists of the primary PLMN ID
and eNodeB ID. 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:
l Allow multiple operators to share eNodeBs and the MME itself.
l Support the delivery of the IE Handover Restriction List. 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.
4.1.3 Idle Mode Management

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.
4.1.3.1 System Information Broadcast
Related Concepts
l 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.
l 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

eRAN
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:
l Cell barring status CellBarred (When a cell belongs to multiple PLMNs, this status is
applied to all of them.)
l 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.
l If an S1 link for the primary operator fails to be set up or becomes faulty, the cell is
reserved for this operator.
l 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.
l 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:

eRAN
l Figure 4-2 shows SIB1 when S1 links for operators A and B are normal.
Figure 4-2 SIB1 (1)
l Figure 4-3 shows SIB1 when the S1 link for operator A is faulty.
Figure 4-3 SIB1 (2)
l Figure 4-4 shows SIB1 when the S1 link for operator B is faulty.

eRAN
Figure 4-4 SIB1 (3)
l 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 tracking area (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:
1. Delete the CellOp.TrackingAreaId parameter setting.

2. Set a new TAC for the CnOperatorTa.TrackingAreaId parameter.
3. Set the CellOp.TrackingAreaId parameter for the cell.
4.1.3.2 EPC Selection

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 EPC, it notifies the eNodeB of the selected EPC 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.

eRAN
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 The eNodeB selects the corresponding EPC,
which a roaming agreement is signed and the EPC allows the UE to attach.
The UE selects the EPC of an operator with The EPC rejects the UE. The UE tries other
which a roaming agreement is not signed EPCs 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

selection process" 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

selection process" 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.
4.1.3.3 Fairness Guarantee for Roaming

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.

eRAN
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.
l 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
l 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
l 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.
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

eRAN
NOTE
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:
l The EPC uses the international mobile subscriber identity (IMSI) of the UE for paging.
Each UE has a unique IMSI.
l 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 frequency or frequency group, which helps the UE promptly re-access the operator's
network.
NOTE
NB-IoT does not support redirections.
4.1.3.6 Cell Selection and Reselection

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 having camped 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 each of 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:

eRAN
l Common priorities
Common priorities are delivered in cell broadcasts to all the UEs in the cell. They are not
operator-specific. For details, see Idle Mode Management.
l Dedicated priorities
A dedicated priority is generated by an internal algorithm during an RRC connection
release. The dedicated priority is delivered to a specific, single UE in the
IdleModeMobilityControlInfo IE in the RRC Connection Release message.
NOTE
NB-IoT does not support dedicated priorities.
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:
l SPID
Operators can configure 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.
NOTE
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.
l Serving cell's PLMN
The 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 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 they are the same, the
eNodeB includes the frequency or frequency band in the information. Otherwise, the
eNodeB does not do so.
NOTE
To use dedicated cell-reselection priorities based on the serving cell's PLMN in FDD, you must
purchase the license for LOFD-001112 MOCN Flexible Priority Based Camping. For details, see
10 MOCN Cell Reselection Priority Configuration.
l Neighboring frequency's HPLMN
Neighboring frequency's HPLMN is the PLMN that is indicated in the system
information broadcast in the cells on the neighboring frequency. Therefore, dedicated
cell reselection priorities based on the neighboring frequency's HPLMN only apply to
PLMNs broadcast for the neighboring frequency. Dedicated cell reselection priorities
based on the neighboring frequency's HPLMN are less flexible than dedicated cell
reselection priorities based on the serving cell's PLMN.

eRAN
The UtranRanShare, GeranRanShare, and EutranNFreqRanShare MOs specify the

dedicated cell-reselection priority specific to each PLMN that shares a neighboring
UTRA frequency, GERAN frequency group, or neighboring E-UTRA frequency,
respectively.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
is deselected, the eNodeB compares the UE's serving PLMN with the neighboring
frequencies' HPLMNs configured for dedicated cell-reselection priorities based on
neighboring frequency's HPLMN. If a neighboring frequency's HPLMN 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 HPLMN
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 compares the PLMNs that allow incoming handovers from UE's
serving PLMN with the neighboring frequencies' HPLMNs configured for dedicated
cell-reselection priorities based on neighboring frequency's HPLMN. If a neighboring
frequency's HPLMN 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 HPLMN 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.
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 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:
l If a UE is configured with an SPID, the eNodeB sends the dedicated cell-reselection

priority to the UE based on the SPID.

eRAN
l 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 HPLMN. 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.
NOTE
For details about cell selection and reselection in the independent operator mode, see Idle Mode
Management.
4.1.4 Mobility Management in Connected Mode

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:
l 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.
l 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.
l After 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 source eNodeB to
determine the target cell for a handover.
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 either of the following:

eRAN
l A list of serving PLMNs of the neighboring UTRAN cell, configured by using the
UtranExternalCellPlmn.ShareMcc and UtranExternalCellPlmn.ShareMnc
parameters
l 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, set the
L2GPLMNChooseOptSwitch option of the GlobalProcSwitch.ProtocolMsgOptSwitch
parameter according to the protocol release the GERAN cell complies with.
– If a GERAN cell complies with 3GPP Release 10 or earlier (a non-standard
scenario), select the L2GPLMNChooseOptSwitch option. 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. 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. 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 serving PLMN of the UE, which is not necessarily consistent with the
primary PLMN ID configured for the GERAN.
NOTE
CDMA2000 does not support RAN sharing with common carrier. The PLMN information of
CDMA2000 1x neighboring cells and CDMA2000 HPRD neighboring cells is indicated by the MCC
and MNC 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 enabled with RAN sharing
with common carrier, the source eNodeB also selects the serving PLMN for the UE to use
after it 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.
l 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.
l 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

eRAN
dedicated cell-reselection priority based on neighboring frequency's HPLMN in 4.1.3.6

Cell Selection and Reselection.
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 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 after a handover to the target eNodeB only through the
serving PLMN in the 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 as follows in some cases:
l 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 after the handover.
l 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: 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. 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. (GUMMEI is short for globally
unique MME identifier.)
– GWCN: 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. If RAN
sharing with common carrier is enabled in the target cell, the MME must support
delivering the IE Handover Restriction List to the eNodeB; otherwise, an S1- or
X2-based handover may fail because the target eNodeB cannot identify the UE's
serving PLMN.
4.1.4.4 Operator-specific Selection of Mobility Policies

Selecting an intra-E-UTRAN mobility policy can be operator-specific because frequency
priorities for UEs in connected mode can be configured in cells based on the PLMN ID.

eRAN
Operators can implement their own frequency delivery policies for handover measurements.
For details, see Mobility Management in Connected Mode.
Selecting an E-UTRAN-to-GERAN mobility policy can be operator-specific because peer

GERAN capabilities can be configured on eNodeBs based on the PLMN ID and the LAC.
Peer GERAN capabilities include RAN information management (RIM), ultra-flash circuit
switched fallback (CSFB), and single radio voice call continuity (SRVCC). For details, see
Mobility Management in Connected Mode.
Selecting an E-UTRAN-to-UTRAN mobility policy can be operator-specific because peer

UTRAN capabilities can be configured on eNodeBs based on the PLMN ID and RNC ID.
Peer UTRAN capabilities include PS handovers, RIM, VoLTE, ultra-flash CSFB, and
SRVCC. For details, see Mobility Management in Connected Mode.
4.1.5 Feature and Capacity Management

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.
4.1.5.1 Feature License

All feature licenses are shared by operators and are not dedicated to individual operators.
4.1.5.2 Capacity License

The capacity license is shared by operators and does not differentiate between individual
operators. 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.
The following principles must apply:
l 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.
l Each operator can only use its own allotment.
l If the LicenseSharingPolicy.MaxUserNumRate parameter is configured only for some
operators, operators not configured with this parameter are not allocated any resource by
default and their UEs will not be admitted except those performing emergency call
services.

eRAN
If the licensed RRC_CONNECTED UE resources do not need to be distributed among

operators in proportions, do not configure the LicenseSharingPolicy MO. If this is the case,
all operators share the total RRC_CONNECTED UE resources, and the eNodeB does not
limit the proportion for any individual operator.
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. When an operator has multiple PLMN IDs, these PLMNs can form an
RRC_CONNECTED UE number sharing group and share the sum of proportions specified by
the LicenseSharingPolicy.MaxUserNumRate parameter for each PLMN. PLMNs are in the
same group if they have the same LicenseSharingPolicy.UserNumSharingGroupId
parameter value. If the LicenseSharingPolicy.UserNumSharingGroupId parameter is set to
the invalid value 255 for a PLMN, this PLMN is not in any RRC_CONNECTED UE number
sharing group.
The principles for configuring the LicenseSharingPolicy.MaxUserNumRate parameter are

the same as those for operator-specific licensed RRC_CONNECTED UE resource sharing.
NOTE
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
The LicRatio.TrafficSharingType parameter specifies whether the total traffic of the eNodeB
is allocated to operators in proportions.
l If this parameter is set to SHARING, all operators share the total traffic of the eNodeB.
l If this parameter is set to DEDICATE, the traffic 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.
The following principles must apply:
l 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.
l For each operator, the value of the LicRatioSharePolicy.TrfSharingRatio parameter
cannot be greater than that of the LicRatioSharePolicy.TrfRatio parameter.
l If the LicRatioSharePolicy.TrfRatio parameter is configured only for some operators,
operators not configured with this parameter are not allocated any resource by default
and their UEs will not be admitted except those performing emergency call services.

eRAN
When traffic is allocated among operators in proportions, resources can be configured to be

not shared, partly shared, or completely shared among operators by using the
LicRatioSharePolicy.TrfSharingRatio parameter. In the following examples, the
LicRatioSharePolicy.TrfRatio parameter is set to 50% for the two operators (A and B), the
traffic required by operator A is greater than 50%, and the traffic required by operator B is
less than 50%.
l Not shared
When the LicRatioSharePolicy.TrfSharingRatio parameter is set to 0% for both
operators, operator A cannot occupy the unused capacity of operator B.
l Partly shared
operators, operator A can occupy 60% of the total traffic of the eNodeB at most.
l Completely shared
operators, operator A can occupy the total traffic of the eNodeB at most.
The traffic used by each operator can be obtained from the operator-specific performance
counters about traffic.
4.1.6 Fair Sharing of Air Interface Resources

RBs can be shared on a per operator or operator group basis.
Operator-specific RB Sharing
When 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, and scheduling on a per operator basis. If an operator has unused RBs,
they can be shared by other operators. If no operator has unused RBs, RBs are allocated in
proportions. For details about admission and congestion control, see Admission and
Congestion Control.
l 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 CellOp.OpDlRbUsedRatio or
CellOp.OpUlRbUsedRatio parameter values 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:
– When the sum of the CellOp.OpDlRbUsedRatio or CellOp.OpUlRbUsedRatio
parameter values for all operators is less than 100%, the eNodeB allocates any
remaining available RBs to operators requiring additional transmission resources.
– When an operator has unused RBs, other operators can use these RBs.
l The eNodeB must calculate and record the following items for each operator to perform
admission control, congestion control, and scheduling on a per operator basis:
– Quality of service (QoS) satisfaction rate corresponding to QoS class identifier
(QCI) x of all UEs (x ranges from 1 to 4)
– 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.

eRAN
For example, if two operators A and B share resources, the eNodeB performs admission
control, congestion control, and scheduling while observing the following two principles:
l 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.
l When the number of UEs served by operator B increases, eNodeB scheduling ensures
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.
For FDD, 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, and scheduling 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. For details about admission and congestion control, see Admission and Congestion
Control.
l 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 CellOp.OpDlRbUsedRatio or
CellOp.OpUlRbUsedRatio parameter values 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 CellOp.OpDlRbUsedRatio or CellOp.OpUlRbUsedRatio
parameter values for all operators is less than 100%, the eNodeB does not allocate
any remaining available RBs to operators requiring additional transmission
resources.
– When an operator has unused RBs, other operators cannot use these RBs.
l The eNodeB must calculate and record the following items for each operator to perform
admission control, congestion control, and scheduling on a per operator basis:
– Quality of service (QoS) satisfaction rate corresponding to QoS class identifier
(QCI) x of all UEs (x ranges from 1 to 4)
– 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:
l Throughput and Data Volume Measurement per CNOperator
(Traffic.Thruput.Cell.Operator)
l PRB Measurement per CNOperator (Traffic.RB.Cell.Operator)
l Throughput and Data Volume Measurement (Traffic.Thruput.Cell)
l PRB Measurement (ChMeas.PRB.Cell)
l eMTC Throughput and Data Volume Measurement (Traffic.Thruput.Cell.eMTC)
RB Sharing Based on Operator Groups
RBs can be shared on a per operator group basis. This function is an enhancement of operator-
specific RB sharing. Some operators may have a partnership with each other. When three or

eRAN
more operators share a cell, those in a partnership can form a resource group that can be
represented by a member operator, and RBs are preferentially shared within the resource
group. If there are still unused RBs, they can be shared by other operators. This function
ensures that resources are equally allocated to operators in the same resource group.
The eNodeB can perform admission control, congestion control, and scheduling based on
operator resource groups if the OpPrbGroupshareSwitch option of the
CellAlgoSwitch.OpResourceGroupShareSwitch parameter is selected. Operators in the same
resource group must be configured with the same CellOp.OpResourceGroupIndex value.
The proportion of RBs allocated to an operator resource group in the uplink or downlink is the
sum of the CellOp.OpUlRbUsedRatio or CellOp.OpDlRbUsedRatio parameter values for
each operator in the resource group, respectively.
4.1.6.1 Admission Control

The rules for GBR service admission control on a per operator basis are as follows:
l 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.) 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.
l In the downlink, the QoS satisfaction rate corresponding to QCI x (x ranges from 1 to 4.)
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.
l 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.
NOTE
When RB sharing based on operator groups is enabled, the preceding functions are performed on a per
operator resource group basis.
4.1.6.2 Congestion Control

The rules for congestion control on a per operator basis are as follows:
l 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.) 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.
l In the downlink, the QoS satisfaction rate corresponding to QCI x (x ranges from 1 to 4.)
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.
l 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.

eRAN
NOTE
4.1.6.3 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 independent operator mode.
For details about scheduling, see Scheduling.
NOTE
4.1.6.4 MLB
When RAN sharing is enabled, the eNodeB supports operator-level or operator-group-level
inter-frequency MLB based on the PRB usage or number of UEs.
For details about MLB, see Intra-RAT Mobility Load Balancing.
4.1.7 NB-IoT User-Plane UE Context Storage Management

When the data over user plane function is enabled, Huawei eNodeBs support storage of UE
contexts, which reduces signaling overheads, delays, and UE power consumption. The license
item for "NB-IoT User" is required.
When NB-IoT RAN sharing with common carrier is enabled, the proportion of UE contexts
that are stored on an eNodeB in user plane mode can be specified on a per operator basis
using the NbSharingPolicy.UeContextProportion parameter. The eNodeB stores UE contexts
for each operator based on the parameter value. When the proportion specified for an operator
by this parameter exhausts, earlier UE contexts of this operator will be deleted.
For details about the data over user plane function, see NB-IoT Radio and Performance
Basics (FDD).
4.1.8 ANR Management

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

eRAN
accordingly. For example, when Cell 1 and Cell 2 may have neighbor relationships, the
parameter needs to be configured as follows:
l 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.
l 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.
4.1.9 OSS 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.
4.1.9.1 Configuration Management

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.
4.1.9.2 Fault Management

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.
4.1.9.3 Performance Management

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.

eRAN
4.1.10 Transmission Networking

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.
4.1.10.1 Transmission Port Planning

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 IP 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:
l 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.
l 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.
4.1.10.2 Transmission Link Setup

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.
l 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.

eRAN
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.
l 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:
l You can configure S1 transmission links only for operators who will provide services or
undergo testing during the initial stage of network deployment.
l If all operators sharing the RAN will 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 is missing.
Table 4-1 and Table 4-2 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.

eRAN
Table 4-1 Configuration of dedicated or shared control-plane transmission links for RAN
sharing with common carrier in different topologies
Transmission S1 with Dedicated S1 with Shared X2
Link MMEs MMEs
Control-plane link Dedicated Shared Shared
Table 4-2 Configuration of dedicated or shared user-plane transmission links for RAN sharing
with common carrier in different topologies
Transmission S1 with Dedicated S1 with Shared S- X2
Link S-GWs GWs
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-3 Control-plane transmission link configuration in endpoint mode for RAN sharing
with common carrier
Configuration S1 with Dedicated S1 with Shared X2
Item MMEs MMEs
S1 or X2 MO Configure a Configure the Configure a

dedicated S1 MO for CpEpGroupId dedicated X2 MO
each operator, and parameter for the S1 for each operator,
specify a unique MO of only one specify a unique
CpEpGroupId operator. CpEpGroupId
parameter value for parameter value for
each MO. each X2 MO, and
specify the same
SCTPHOST MO
for all operators to
share.
Local control plane Configure a single Configure a single Configure a single

local S1 control- local S1 control- local X2 control-
plane IP address for plane IP address for plane IP address for
the operators to the operators to the operators to
share, or configure a share. share.
dedicated one for
each operator.

eRAN

Item MMEs MMEs
Peer control plane Configure a Configure a single Configure a single

dedicated peer S1 peer S1 control- peer X2 control-
control-plane IP plane IP address for plane IP address for
address for each the operators to the operators to
operator. share. share.
Table 4-4 User-plane transmission link configuration in endpoint mode for RAN sharing with
common carrier
Configuration S1 with Dedicated S1 with Shared S- X2
Item S-GWs GWs
S1 or X2 MO Configure a l If operators share l If operators share

dedicated S1 MO for an S1 user-plane an X2 user-plane
each operator, and link, configure link, configure a
specify a unique the dedicated X2
UpEpGroupId UpEpGroupId MO for each
parameter value for parameter for the operator and
each MO. S1 MO of only specify the same
one operator. UpEpGroupId
l If operators use parameter value
dedicated S1 for the MOs.
user-plane links, l If operators use
configure a dedicated X2
dedicated S1 MO user-plane links,
for each operator configure a
and specify a dedicated X2
unique MO for each
UpEpGroupId operator and
parameter value specify a unique
for each MO. UpEpGroupId
parameter value
for each MO.
Local user plane Configure a single Configure a single Configure a single

local S1 user-plane local S1 user-plane local X2 user-plane
IP address for the IP address for the IP address for the
operators to share, operators to share, operators to share,
or configure a or configure a or configure a
dedicated one for dedicated one for dedicated one for
each operator. each operator. each operator.

eRAN

Item S-GWs GWs
Peer user plane Configure a Configure a single Configure a single

dedicated peer S1 peer S1 user-plane peer X2 user-plane
user-plane IP IP address for the IP address for the
address for each operators to share, operators to share,
operator. or configure a or configure a
dedicated one for dedicated one for
each operator. each operator.
When all operators use the same local and peer user-plane IP address:
l 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.
l 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.
Link Mode
Table 4-5 Control-plane transmission link configuration in link mode for RAN sharing with
common carrier
Link MMEs MMEs
Control plane Configure dedicated Only configure Configure

S1Interface and S1Interface and X2Interface and
SCTPLNK MOs for SCTPLNK MOs for SCTPLNK MOs for
each operator. the operators to the operators to
share. share.

eRAN
Table 4-6 User-plane transmission link configuration in link mode for RAN sharing with
common carrier
Link S-GWs GWs
User plane Configure a Configure a single Configure a single

dedicated IPPATH IPPATH MO for the IPPATH MO for the
MO for each operators to share, operators to share,
operator. or configure a or configure a
dedicated one for dedicated one for
each operator. each operator.
If a dedicated If a dedicated
IPPATH MO is IPPATH MO is
configured for each configured for each
operator, configure operator, configure
CnOperatorIpPath CnOperatorIpPath
MOs to define the MOs to define the
mapping mapping
relationships relationships
between the between the
operators and the IP operators and the IP
paths. paths.
4.1.10.3 Dynamic Sharing of Uplink Transmission Bandwidth

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.
4.1.10.4 VLAN Planning

Each operator can use a unique virtual local area network (VLAN). For details about how to
divide VLANs, see IP Transmission.
4.1.11 Multi-operator PKI

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 Network Analysis
4.2.1 Benefits
RAN sharing provides the following benefits for operators:

eRAN
l Reduced capital expenditure (CAPEX) and operating expense (OPEX)

l Accelerated network deployments
l Expanded network coverage
4.2.2 Impacts
Network Impacts
If the UE distribution is different among RAN sharing operators, the throughput may change
after RAN sharing with common carrier 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 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.
This function has no impact on NB-IoT.
Function Impacts
RAT Function Function Switch Reference Description
Name
FDD Out-of-band OutOfBandRelayS Relay When out-of-band relay

relay witch option of the and RAN sharing with
CellAlgoSwitch.Rel common carrier are both
aySwitch parameter enabled, all the resources
(including RB resources
and the licensed traffic
and RRC_CONNECTED
UE resources) of an
eNodeB can only be
completely shared among
operators (not in
proportions).
FDD In-band relay None Relay When in-band relay and

RAN sharing with
common carrier are both
enabled, all the resources
(including RB resources
and the licensed traffic
and RRC_CONNECTED
UE resources) of an
eNodeB can only be
completely shared among
operators (not in
proportions).

eRAN

Name
FDD VoIP semi- l SpsSchSwitch VoLTE Voice services have a

persistent option of the high scheduling priority
scheduling CellAlgoSwitch. and are sensitive to
UlSchSwitch scheduling delays.
parameter Uplink and downlink
l SpsSchSwitch semi-persistent
option of the scheduling does not
CellAlgoSwitch. consider the configured
DlSchSwitch proportions of RBs that
parameter can be allocated to
different operators.
FDD PRB upper CellWttxParaCfg.P WBB In RAN sharing with

limit control rbUpLimitCtrlMode common carrier
mode scenarios, if tight control
over the maximum PRB
usage is implemented,
the proportions of RBs
allocated to an operator
cannot exceed the preset
thresholds.
4.3 Requirements
4.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-001036 RAN Sharing with LT1S00RSCC00 per cell

Common Carrier
NB-IoT MLOFD-121251 NB-IoT RAN ML1S00RSCC00 per cell

Sharing with
Common Carrier

eRAN
4.3.2 Software
Prerequisite Functions
Name
FDD S1-flex None S1-flex This function is required

if the MOCN
architecture is used.
Mutually Exclusive Functions

Name
FDD RAN sharing ENodeBSharing RAN Each operator supports

with dedicated Mode.ENodeBSha Sharing only one RAN sharing
carrier ringMode mode.
NB-IoT NB-IoT RAN ENodeBSharing RAN Each operator supports

sharing with Mode.ENodeBSha Sharing only one RAN sharing
dedicated ringMode mode.
carrier
FDD Hybrid RAN ENodeBSharing RAN Each operator supports

sharing Mode.ENodeBSha Sharing only one RAN sharing
ringMode mode.
FDD Out-of-band OutOfBandRelay Relay This function does not

relay Switch option of support multiple
the operators. Therefore, it
CELLALGOSWI does not work with
TCH.RelaySwitch RAN sharing with
parameter common carrier.
FDD In-band relay None Relay This function does not

support multiple
operators. Therefore, it
does not work with
RAN sharing with
common carrier.

eRAN

Name
FDD Intra-RAT l IntraRatEvent ANR If the serving cell and

ANR AnrSwitch Manageme neighboring cells are
option of the nt managed by different
ENodeBAlgoS OSSs, intra-RAT ANR
witch.AnrSwitc does not work when the
h parameter: PLMN ID at the top of
controlling the PLMN list is rotated.
intra-RAT
event-triggered
ANR
l IntraRatFastA
nrSwitch
option of the
ENodeBAlgoS
witch.AnrSwitc
h parameter:
controlling
intra-RAT fast
ANR
4.3.3 Hardware
Base Station Models

For FDD, the following base stations are compatible with this function:
l 3900 and 5900 series base stations

l DBS3900 LampSite and DBS5900 LampSite
l BTS3912E
l BTS3911E
l BTS3203E
l BTS3202E
For NB-IoT, the following base stations are compatible with this function:

l BTS3912E
l BTS3911E
Boards
No requirements

eRAN
RF Modules
No requirements
4.3.4 Others
None
4.4 Operation and Maintenance (FDD)
4.4.1 Data Configuration
4.4.1.1 Data Preparation

The transmission and interface data required in RAN sharing with common carrier is similar
to that in the independent operator mode. The configurations vary depending on the network
architecture in use. For details, see 4.1.10 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 Cell Management, Mobility Management in Connected Mode, and
this section.
Parameters for Initial Configuration

The following table describes the parameters used for function activation in both FDD and
NB-IoT.
Table 4-7 Parameters used for activation in both FDD and NB-IoT
Parameter Parameter ID Setting Notes
Name
Local tracking CnOperatorTa None

area ID .TrackingAreaI
d
CN Operator ID CnOperatorTa None

.CnOperatorId
Tracking area CnOperatorTa In a cell where RAN sharing with common carrier is
code .Tac enabled, configure the same TAC for all operators.
Local cell ID CellOp.LocalC None

ellId
Local tracking CellOp.Tracki In a cell where RAN sharing with common carrier is
area ID ngAreaId enabled, the CnOperatorTa.CnOperatorId
parameter values must be different. One of the
parameter values must correspond to the primary
operator.

eRAN

Name
Operator uplink CellOp.OpUlR None

RB used ratio bUsedRatio
Operator CellOp.OpDlR None

downlink RB bUsedRatio
used ratio
Operator CellOp.Operat None

PLMN Round orPlmnRoundP
Period eriod
Operator CellOp.OpReso None

Resource Group urceGroupInde
Index x
eNodeB sharing ENodeBSharin Set this parameter to SHARED_FREQ.

mode gMode.ENode
BSharingMode
The following table describes the parameters used for function activation specific to FDD.
Table 4-8 Parameters used for activation specific to FDD

Name
CN Operator ID CnOperator.C By default, one eNodeB can be configured with data

nOperatorId for up to four operators, whose
CnOperator.CnOperatorId values must be different.
The parameter value for each operator must be the
same on all eNodeBs managed by the same OSS. The
PLMN ID uniquely identifies an operator globally,
which is composed of the MCC and MNC.
CN Operator CnOperator.C None

name nOperatorNam
e
CN Operator CnOperator.C Set this parameter to CNOPERATOR_PRIMARY

type nOperatorType or CNOPERATOR_SECONDARY based on the
contracts signed by the operators.
Mobile country CnOperator.M None

code cc
Mobile network CnOperator.M None

code nc
The following table describes the parameters used for function activation specific to NB-IoT.

eRAN
Table 4-9 Parameters used for activation specific to NB-IoT

Name
S1 MmeCapInfo. Set this parameter to S1INTERFACE_CFG.

Configuration S1CfgType
Type
The following table describes the parameters used for function optimization in both FDD and
NB-IoT.
Table 4-10 Parameters used for optimization in both FDD and NB-IoT

Name
Local cell ID CellAccess.Loc None

alCellId
Plmn Broadcast CellAccess.Bro Set this parameter based on the network plan.
Mode adcastMode
Plmn Round CellAccess.Rou None

Broadcast ndPeriod
Period
Plmn Round CellAccess.Rou None

Action Time ndActionTime
Different GlobalProcSwi None

Operator With tch.DiffOpWith
Same MMEC SameMmecSwi
Switch tch
The following table describes the parameters used for function optimization specific to FDD.
Table 4-11 Parameters used for optimization specific to FDD
Parameter Parameter ID Option Setting Notes

Name
CN Operator ID LicenseSharin N/A None

gPolicy.CnOpe
ratorId
The proportion LicenseSharin N/A None

of the gPolicy.MaxUs
maximum erNumRate
number of users

eRAN

Name

of the sharing gPolicy.UserNu
number of users mSharingRate
User Number LicenseSharin N/A None

Sharing Group gPolicy.UserNu
ID mSharingGrou
pId
Local cell ID CellAlgoSwitc N/A None

h.LocalCellId
RAN Sharing CellAlgoSwitc N/A None

Mode Switch h.RanShareMo
deSwitch
Operator CellAlgoSwitc N/A None

Resource Group h.OpResource
Share Switch GroupShareSw
itch
Uplink Traffic LicRatio.UpLic N/A None

License Ratio Ratio
Traffic Sharing LicRatio.Traffi N/A None

Type cSharingType
CN Operator ID LicRatioShare N/A None

Policy.CnOper
atorId
TrfRatio LicRatioShare N/A None

Policy.TrfRatio
TrfSharingRatio LicRatioShare N/A None

Policy.TrfShari
ngRatio

eRAN

Name
ANR Under ENodeBAlgoS N/A Select the

RAN Sharing witch.RanShar NBSLTEPLMNRoundSwitch
Algorithm ingAnrSwitch option of this parameter for an
Switch eNodeB if a cell (Cell 1) under the
eNodeB may have a neighboring
cell (Cell 2) that meets the
following conditions:
l Cell 2 supports RAN sharing
with common carrier.
l The
CellAccess.BroadcastMode
parameter is set to RR_MODE
or FREE_Mode for Cell 2.
Select the
NBSLTERANSharingSwitch,
NBSUTRANRANSharingS-
witch, or NBSGERANRANShar-
ingSwitch option for an eNodeB if
a cell (Cell 1) under the eNodeB
may have a neighboring cell (Cell
2) that meets the following
conditions:
l Cell 2 supports RAN sharing
with common carrier.
l The
parameter is set to
NORMAL_MODE for Cell 2.
Handover Algo ENodeBAlgoS InterPlmnHoSw Select this option.

switch witch.HoAlgoS itch
witch
CN Operator ID InterPlmnHoL N/A None

ist.CnOperator
Id
Target Mobile InterPlmnHoL N/A None

country code ist.TarMcc

network code ist.TarMnc
RAT frequency RatFreqPriorit N/A None

priority group yGroup.RatFre
ID qPriorityGroup
Id

eRAN

Name
RAT Type RatFreqPriorit N/A None

yGroup.RatTyp
e
DL Earfcn or RatFreqPriorit N/A None

Bandclass yGroup.DlEarf
cn
Priority RatFreqPriorit N/A None

yGroup.Priorit
y
GERAN RatFreqPriorit N/A None

Frequency yGroup.BandI
Indicator ndicator
Spid SpidCfg.Spid N/A None
RAT frequency SpidCfg.RatFr N/A None

priority eqPriorityInd
indication

priority group eqPriorityGrou
ID pId
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.

Name
Local cell ID GeranNFGrou None

pSCellOp.Loca
lCellId
BCCH group GeranNFGrou None

ID pSCellOp.Bcch
GroupId
Cn operator ID GeranNFGrou None

pSCellOp.CnO
peratorID
Cell reselection GeranNFGrou None

dedicated pSCellOp.Cell
priority ReselDediPriCf
configure gInd
indicator

eRAN

Name
Cell reselection GeranNFGrou Set this parameter based on the network plan.
priority ReselDediPri
cell-reselection priority for a GERAN frequency based on the neighboring frequency's
HPLMN.

Name
Local cell ID GeranRanSha None

re.LocalCellId
BCCH group GeranRanSha None

ID re.BcchGroupI
d
Mobile country GeranRanSha None

code re.Mcc
Mobile network GeranRanSha None

code re.Mnc
Cell reselection GeranRanSha None

priority re.CellReselPri
configure orityCfgInd
indicator
Cell reselection GeranRanSha Set this parameter based on the network plan.
priority re.CellReselPri
ority
cell-reselection priority for a UTRAN frequency based on the serving cell's PLMN.

Name
Local cell ID UtranNFreqS None

CellOp.LocalC
ellId
Downlink UtranNFreqS None

UARFCN CellOp.UtranD
lArfcn

eRAN

Name
Cn operator ID UtranNFreqS None

CellOp.CnOpe
ratorID
Cell reselection UtranNFreqS None

dedicated CellOp.CellRes
priority elDediPriCfgIn
configure d
indicator
Cell reselection UtranNFreqS Set this parameter based on the network plan.
priority elDediPri
cell-reselection priority for a UTRAN frequency based on the neighboring frequency's
HPLMN.

Name
Local cell ID UtranRanShar None

e.LocalCellId
Downlink UtranRanShar None

UARFCN e.UtranDlArfcn
Mobile country UtranRanShar None

code e.Mcc
Mobile network UtranRanShar None

code e.Mnc
Cell reselection UtranRanShar None

priority e.CellReselPrio
configure rityCfgInd
indicator
Cell reselection UtranRanShar Set this parameter based on the network plan.
rity
cell-reselection priority for an E-UTRAN frequency based on the serving cell's PLMN.

eRAN

Name
Local cell ID EutranNFreqS None

CellOp.LocalC
ellId
Downlink EutranNFreqS None

EARFCN CellOp.DlEarf
cn
Cn operator ID EutranNFreqS None

CellOp.CnOpe
ratorID
Cell reselection EutranNFreqS None

configure d
indicator
Cell reselection EutranNFreqS Set this parameter based on the network plan.
priority elDediPri
cell-reselection priority for an E-UTRAN frequency based on the neighboring frequency's
HPLMN.

Name
Local cell ID EutranNFreq None

RanShare.Loc
alCellId
Downlink EutranNFreq None

EARFCN RanShare.DlE
arfcn
Mobile country EutranNFreq None

code RanShare.Mcc
Mobile network EutranNFreq None

code RanShare.Mnc
Cell reselection EutranNFreq None

priority RanShare.Cell
configure ReselPriorityCf
indicator gInd

eRAN

Name
Cell reselection EutranNFreq Set this parameter based on the network plan.
priority RanShare.Cell
ReselPriority
cell-reselection priority for a CDMA frequency.

Name
Local cell ID Cdma2000BcS None

CellOp.LocalC
ellId
Band class Cdma2000BcS None

CellOp.BandCl
ass
Cn operator ID Cdma2000BcS None

CellOp.CnOpe
ratorID
CDMA2000 Cdma2000BcS None

1xRTT CellOp.Cdma1
dedicated XrttCellReselPr
priority iInd
configure
indicator
CDMA2000 Cdma2000BcS Set this parameter based on the network plan.

1xRTT Cell CellOp.Cdma1
Reselection XrttCellReselD
Dedicated ediPri
Priority

HRPD CellOp.HrpdC
dedicated ellReselDediPri
priority CfgInd
configure
indicator

HRPD Cell CellOp.HrpdC
Reselection ellReselDediPri
Dedicated
Priority

eRAN
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.

Name
Protocol GlobalProcSwi L2GPLMNCho Select this option if the GERAN

Message tch.ProtocolMs oseOptSwitch cell where RAN sharing with
Optimization gOptSwitch common carrier is enabled
Switch complies with 3GPP R10 or
earlier.
In other scenarios, select or
deselect this option based on site
conditions to ensure that the target
PLMN ID carried in a handover
request message or RIM request
message is the GERAN-
configured primary PLMN ID.
The following table describes the parameters used for function optimization specific to NB-
IoT.
Table 4-12 Parameters used for optimization specific to NB-IoT

Name
CN Operator ID NbSharingPoli None

cy.CnOperatorI
d
UE Context NbSharingPoli Set this parameter based on the network plan.

Proportion cy.UeContextPr
oportion
Parameters for Reconfiguration

eNodeBs can be reconfigured in batches on the CME or one by one on the GUI.
A reconfiguration is required in any of the following scenarios:
l 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.
l 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.

eRAN
l 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.
l 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 the configurations in endpoint mode, see S1 and X2 Self-Management. For the
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.
l 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:
a. 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 ENODEBFUNCTION command).
b. CnOperator: Used to add operator information.
c. (Optional) LicenseSharingPolicy: Used to set the licensed proportion of
RRC_CONNECTED UEs for each operator in FDD.
d. CnOperatorTa: Used to add tracking area information.
e. CellAlgoSwitch: Used to set the RAN sharing mode switch in FDD.
f. (Optional) CellAccess: Used to set the cell access information.
g. CellOp: Used to set the cell operator information.
h. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
i. (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.
j. (Optional) NbSharingPolicy: Used to set the proportion of UE contexts that can be
stored in NB-IoT user-plane mode on a per operator basis.
k. (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.
l. (Optional) ENodeBAlgoSwitch.RanSharingAnrSwitch: Used to turn on the ANR
switch in the adjacent cells that have neighbor relationships with the local cell in
FDD.
m. (Optional) RatFreqPriorityGroup and SpidCfg: Used to set the SPID-based
dedicated cell-reselection priority in FDD.
n. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, or Cdma2000BcSCellOp: Used to set a dedicated cell-
reselection priority based on the serving cell's PLMN in FDD.
o. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used
to set a dedicated cell-reselection priority based on the neighboring frequency's
HPLMN in FDD.

eRAN
l Adding a secondary operator

a. CnOperator: Used to add operator information.
b. (Optional) LicenseSharingPolicy: Used to set the licensed proportion of
c. CnOperatorTa: Used to add tracking area information.
d. CellOp: Used to set the cell operator information.
e. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
f. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for
g. (Optional) NbSharingPolicy: Used to set the proportion of UE contexts that can be
h. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to set the
external E-UTRAN cells and PLMN lists for the local cell and cells that have
i. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, or Cdma2000BcSCellOp: Used to set a dedicated cell-
reselection priority based on the serving cell's PLMN in FDD.
j. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used
to set a dedicated cell-reselection priority based on the neighboring frequency's
HPLMN in FDD.
l Removing a secondary operator
a. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to remove
the external E-UTRAN cells and PLMN lists for the local cell and cells that have
b. (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.
c. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.
d. CellOp: Used to remove the cell operator information.
e. (Optional) LicenseSharingPolicy: Used to remove the configured licensed
proportion of RRC_CONNECTED UEs for each operator.
f. (Optional) NbSharingPolicy: Used to remove the configured proportion of UE
contexts that can be stored in NB-IoT user-plane mode on a per operator basis.
g. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, or Cdma2000BcSCellOp: Used to remove the
dedicated cell-reselection priority configured based on the serving cell's PLMN in
FDD.
h. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used
to remove the dedicated cell-reselection priority configured based on the
neighboring frequency's HPLMN in FDD.
i. CnOperatorTa: Used to remove the tracking area information.
j. CnOperator: Used to remove the operator information.

eRAN
l Changing the sharing mode of an eNodeB from the RAN sharing with common carrier
mode to the independent operator mode
a. (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.
b. (Optional) EutranExternalCell and EutranExternalCellPlmn: Used to remove
the external E-UTRAN cells and PLMN lists for the local cell and cells that have
c. (Optional) X2Interface: Used to remove the X2 interface in FDD.
d. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.
e. (Optional) LicRatioSharePolicy: Used to remove the configuration of the licensed
f. (Optional) NbSharingPolicy: Used to remove the configured proportion of UE
g. CellOp: Used to remove the cell operator information.
h. S1Interface: Used to remove the S1 interface.
i. CnOperatorTa: Used to remove the tracking area information.
j. (Optional) LicenseSharingPolicy: Used to remove the configured licensed
proportion of RRC_CONNECTED UEs for each operator in FDD.
k. CellAlgoSwitch: Used to turn off the cell-specific RAN sharing switch.
l. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp,
dedicated cell-reselection priority configured based on the serving cell's PLMN in
FDD.
m. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare: Used
to remove the dedicated cell-reselection priority configured based on the
neighboring frequency's HPLMN in FDD.
n. CnOperator: Used to remove the operator information.
o. 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
ENODEBFUNCTION command).
p. (Optional) ENodeBAlgoSwitch.RanSharingAnrSwitch: Used to turn off the ANR
switch in the adjacent cells that have neighbor relationships with the local cell in
FDD.
4.4.1.2 Using MML 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

eRAN
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 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
ENODEBFUNCTION command)
RST APP: AID=1;
The following are command examples for function activation in NB-IoT:

MOD ENODEBSHARINGMODE: ENodeBSharingMode=SHARED_FREQ;
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=78,
NbIotTaFlag=BOOLEAN_TRUE;
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, OperatorPlmnRoundPeriod=1;
ADD CELLOP: LocalCellId=0, TrackingAreaId=1, OperatorPlmnRoundPeriod=1;
//Enabling the MME to support NB-IoT
ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType= S1INTERFACE_CFG, S1Id=0,
S1InterfaceId=0, NbCiotEpsOptCap=CP_UP, NbLteSupportCap=SUPPORT;
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;
//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 whether to allow MMEs of different RAN sharing operators to have

eRAN
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 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 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;

neighboring frequency's HPLMN)
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

ADD UTRANNFREQSCELLOP: LocalCellId=0, UtranDlArfcn=1234, CnOperatorID=0,

ADD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=10800, Mcc="460", Mnc="02",
Configuring a dedicated cell-reselection priority for an E-UTRAN frequency (based on the

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,
Cdma1XrttCellReselPriInd=NOT_CFG, HrpdCellReselDediPriCfgInd=NOT_CFG;
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;

eRAN
The following are command examples for function optimization in NB-IoT:

ADD CNOPERATORTA: TrackingAreaId=1, CnOperatorId=1, Tac=78, NbIotTaFlag=
BOOLEAN_TRUE;
//Configuring the proportion of UE contexts that are stored on an eNodeB in NB-
IoT user plane mode for each operator
ADD NBSHARINGPOLICY: CnOperatorId=0, UeContextProportion=50;
the same MMEC
4.4.1.3 Using the CME

l Fast batch activation
This feature can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration
This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
4.4.2 Activation Verification

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
Step 1 Check the cell status by running the following command:
DSP CELL:LOCALCELLID=0;
Expected result:
The cell status is normal.
The following is an example of the command output for normal cell status:
--------------------------start--------------------------
%%/*34421*/DSP CELL:;%%
RETCODE = 0 Operation succeeded.
...
Local cell ID = 0
Cell instance state = Normal
...
--------------------------end---------------------------
Step 2 View the information contained in the SIB1 broadcast in the cell.
Expected result:

eRAN
SIB1 contains the correct PLMN information about each operator.
Step 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)
Step 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.
l 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.
l The value of "TAC" is a hexadecimal number in the traced message.
----End
4.4.3 Network Monitoring

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.

eRAN
Table 4-13 lists the operator-specific FDD counters. For details, see Performance Counter
Reference of eNodeBs.
Table 4-13 Operator-specific FDD counters

Function Subset Counter
E-RAB Setup l L.E-RAB.AttEst.PLMN.QCI.1~9

Measurement per l L.E-RAB.SuccEst.PLMN.QCI.1~9
CNOperator (E-
RAB.Est.Cell.Opera l L.E-RAB.AttEst.PLMN
tor) l L.E-RAB.SuccEst.PLMN
l L.E-RAB.AttEst.HOIn.PLMN
l L.E-RAB.SuccEst.HOIn.PLMN
E-RAB Release l L.E-RAB.AbnormRel.PLMN.QCI.1~9

Measurement per l L.E-RAB.AbnormRel.PLMN
CNOperator (E-
RAB.Rel.Cell.Opera l L.E-RAB.NormRel.PLMN.QCI.1
tor) l L.E-RAB.NormRel.PLMN
l L.E-RAB.NormRel.HOOut.PLMN.QCI.1~9
l L.E-RAB.NormRel.HOOut.PLMN
l L.E-RAB.AbnormRel.HOOut.PLMN.QCI.1~9
l L.E-RAB.AbnormRel.HOOut.PLMN
l L.E-RAB.AbnormRel.MME.PLMN
l L.E-RAB.AbnormRel.MMETot.PLMN
l L.E-RAB.AbnormRel.Radio.PLMN
l L.E-RAB.AbnormRel.TNL.PLMN
l L.E-RAB.AbnormRel.Cong.PLMN
l L.E-RAB.AbnormRel.HOFailure.PLMN
l L.E-RAB.AbnormRel.Radio.SRBReset.PLMN
l L.E-RAB.AbnormRel.Radio.DRBReset.PLMN
l L.E-RAB.AbnormRel.Radio.ULSyncFail.PLMN
l L.E-RAB.AbnormRel.Radio.UuNoReply.PLMN
l L.E-RAB.Rel.S1Reset.eNodeB.PLMN.QCI.1~9
l L.E-RAB.Rel.S1Reset.eNodeB.PLMN
l L.E-RAB.AbnormRel.Radio.UuNoReply.PLMN

eRAN
Throughput and l L.Thrp.bits.UL.PLMN.QCI.1~9

Data Volume l L.Thrp.Time.UL.PLMN.QCI.1~9
Measurement per
CNOperator l L.Thrp.bits.DL.PLMN.QCI.1~9
(Traffic.Thruput.Cel l L.Thrp.Time.DL.PLMN.QCI.1~9
l.Operator) l L.Thrp.bits.UL.PLMN
l L.Thrp.Time.UL.PLMN
l L.Thrp.bits.DL.PLMN
l L.Thrp.Time.DL.PLMN
l L.Thrp.bits.DL.LastTTI.PLMN
l L.Thrp.Time.DL.RmvLastTTI.PLMN
l L.Thrp.bits.UE.UL.LastTTI.PLMN
l L.Thrp.Time.UE.UL.RmvLastTTI.PLMN
l L.Thrp.bits.UE.UL.SmallPkt.PLMN
l L.Thrp.Time.UE.UL.RmvSmallPkt.PLMN
Cell User Quantity l L.Traffic.User.Avg.PLMN

Measurement per l L.Traffic.User.Max.PLMN
CNOperator
(Traffic.User.Cell.O
perator)
PRB Measurement l L.RBUsedOwn.DL.PLMN

per CNOperator l L.RBUsedOwn.UL.PLMN
(Traffic.RB.Cell.Op
erator) l L.RBUsedOther.DL.PLMN
l L.RBUsedOther.UL.PLMN

eRAN
Outgoing Intra-RAT l L.HHO.IntraeNB.IntraFreq.PrepAttOut.PLMN

Handover l L.HHO.IntraeNB.IntraFreq.ExecAttOut.PLMN
Measurement per
CNOperator l L.HHO.IntraeNB.IntraFreq.ExecSuccOut.PLMN
(HO.eRAN.Out.Cell l L.HHO.IntraeNB.InterFreq.PrepAttOut.PLMN
.Operator) l L.HHO.IntraeNB.InterFreq.ExecAttOut.PLMN
l L.HHO.IntraeNB.InterFreq.ExecSuccOut.PLMN
l L.HHO.IntereNB.IntraFreq.PrepAttOut.PLMN
l L.HHO.IntereNB.IntraFreq.ExecAttOut.PLMN
l L.HHO.IntereNB.IntraFreq.ExecSuccOut.PLMN
l L.HHO.IntereNB.InterFreq.PrepAttOut.PLMN
l L.HHO.IntereNB.InterFreq.ExecAttOut.PLMN
l L.HHO.IntereNB.InterFreq.ExecSuccOut.PLMN
l L.HHO.X2.IntraFreq.PrepAttOut.PLMN
l L.HHO.X2.IntraFreq.ExecAttOut.PLMN
l L.HHO.X2.IntraFreq.ExecSuccOut.PLMN
l L.HHO.X2.InterFreq.PrepAttOut.PLMN
l L.HHO.X2.InterFreq.ExecAttOut.PLMN
l L.HHO.X2.InterFreq.ExecSuccOut.PLMN
l L.HHO.BlindHO.PrepAttOut.PLMN
l L.HHO.BlindHO.ExecAttOut.PLMN
l L.HHO.BlindHO.ExecSuccOut.PLMN
l L.HHO.IntraeNB.InterFddTdd.PrepAttOut.PLMN
l L.HHO.IntraeNB.InterFddTdd.ExecAttOut.PLMN
l L.HHO.IntraeNB.InterFddTdd.ExecSuccOut.PLMN
l L.HHO.IntereNB.InterFddTdd.PrepAttOut.PLMN
l L.HHO.IntereNB.InterFddTdd.ExecAttOut.PLMN
l L.HHO.IntereNB.InterFddTdd.ExecSuccOut.PLMN
l L.HHO.X2.InterFddTdd.PrepAttOut.PLMN
l L.HHO.X2.InterFddTdd.ExecAttOut.PLMN
l L.HHO.X2.InterFddTdd.ExecSuccOut.PLMN
l L.HHO.InterFddTdd.BlindHO.PrepAttOut.PLMN
l L.HHO.InterFddTdd.BlindHO.ExecAttOut.PLMN
l L.HHO.InterFddTdd.BlindHO.ExecSuccOut.PLMN
l L.HHO.S1.IntraFreq.MMEAbnormRsp.PLMN
l L.HHO.S1.InterFreq.MMEAbnormRsp.PLMN
l L.HHO.S1.InterFddTdd.MMEAbnormRsp.PLMN

eRAN
Outgoing Inter-RAT All counters of this function subset. For example:

Handover l L.CSFB.PrepAtt.PLMN
Measurement per
CNOperator l L.CSFB.PrepSucc.PLMN
(HO.IRAT.Out.Cell. l L.IRATHO.SRVCC.E2G.MMEAbnormRsp.PLMN
Operator) l L.IRATHO.SRVCC.E2W.MMEAbnormRsp.PLMN
E-RAB Establish All counters of this function subset. For example:

Failure l L.E-RAB.FailEst.NoReply.PLMN
Measurement per
CNOperator (E- l L.E-RAB.FailEst.MME.PLMN
RAB.EstFail.Cell.O
perator)
Throughput All counters of this function subset. For example:

Distribution l L.Thrp.DL.BitRate.Samp.Index0.PLMN
Measurement per
CNOperator l L.Thrp.UL.BitRate.Samp.Index0.PLMN
(Traffic.Thruput.PD
F.Cell.Operator)
Paging l L.Paging.S1.Rx.PLMN
Measurement per
CNOperator
(Paging.Cell.Operat
or)
Voice Quality All counters of this function subset. For example:

Measurement per l L.Voice.VQI.UL.Excellent.Times.PLMN
CNOperator
(VoiceQuality.Cell.O l L.Voice.VQI.UL.Good.Times.PLMN
perator)
Packet Measurement All counters of this function subset. For example:

per CNOperator l L.Traffic.DL.PktDelay.Time.PLMN.QCI.1
(Traffic.Packet.Cell.
Operator) l L.Traffic.DL.PktDelay.Time.PLMN.QCI.5
PDCP Measurement All counters of this function subset. For example:

per CNOperator l L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.1
(Traffic.PDCP.Cell.
Operator) l L.PDCP.Tx.Disc.Trf.SDU.PLMN.QCI.5
Table 4-14 lists the operator-specific NB-IoT counters. For details, see Performance Counter
Reference of eNodeBs.

eRAN
Table 4-14 Operator-specific NB-IoT counters

NB-IoT Cell RRC L.NB.RRC.ConnReq.Succ.PLMN

Setup Measurement
per CNOperator
(RRC.Setup.NB.Cell
.Operator)
NB-IoT Cell UE l L.NB.UECNTX.NormRel.PLMN

Context Release l L.NB.UECNTX.AbnormRel.PLMN
Measurement per
CNOperator
(UeCntx.Rel.NB.Cel
l.Operator)

eRAN
RAN Sharing Feature Parameter Description 5 RAN Sharing with Dedicated Carrier
5 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:
l Each operator has their own spectrum resources but they jointly construct eNodeBs and
share eNodeB hardware.
l 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.

eRAN
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:
l NE functions
l OSS management
l Multi-operator PKI
5.1.2 NE Functions
l 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.
l In MOCN mode, RAN sharing with dedicated carrier does not have special requirements
for EPCs.
l 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.

eRAN
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.
5.1.4 NB-IoT User-Plane UE Context Storage Management (FDD)

The mechanism is the same as that in NB-IoT RAN sharing with common carrier. For details,
see 4.1.7 NB-IoT User-Plane UE Context Storage 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.
information.

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.

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.10.1 Transmission Port Planning.

For basic information about transmission link setup, see 4.1.10 Transmission Networking.

eRAN
In RAN sharing with dedicated carrier, operators need to have their own transmission links
(S1 and X2 interfaces), 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
Link MMEs MMEs
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
Link S-GWs GWs
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
Item MMEs MMEs
S1 or X2 MO Configure a Configure a Configure a

dedicated S1 MO for dedicated S1 MO for dedicated X2 control
each operator, and each operator, and plane MO for each
specify a unique specify a unique operator, specify
CpEpGroupId CpEpGroupId unique
parameter for each parameter for each CpEpGroupId and
MO. MO. SCTPHOST MO
for each X2 MO.

eRAN

Item MMEs MMEs
Local control plane Configure a single Configure a single Configure a

local S1 control- local S1 control- dedicated local X2
plane IP address for plane IP address for control-plane IP
the operators to the operators to address for each
share, or configure a share, or configure a operator.
dedicated local S1 dedicated local S1 Alternatively,
control-plane IP control-plane IP configure a single
address for each address for each local X2 control-
operator. operator. plane IP address for
the operators to
share and a
dedicated SCTP port
number for each
operator.
Peer control plane Configure a Configure a single Configure a single

dedicated peer S1 peer S1 control- peer X2 control-
control-plane IP plane IP address for plane IP address for
address for each the operators to the operators to
operator. share, or configure a share, or configure a
dedicated peer S1 dedicated peer X2
control-plane IP control-plane IP
address for each address for each
operator. operator.
Table 5-4 User-plane transmission link configuration in endpoint mode for RAN sharing with
dedicated carrier
Item S-GWs GWs

dedicated S1 MO for dedicated S1 MO for dedicated X2 MO
each operator, and each operator or for each operator or
specify unique configure a single S1 configure a single
UpEpGroupId for MO for the operators X2 MO for the
each MO. to share, and specify operators to share,
unique or the same and specify unique
UpEpGroupId for or the same
each MO. UpEpGroupId for
each MO.

eRAN

Item S-GWs GWs
Local user plane Configure a single Configure a single Configure a single

operators to share, or operators to share, or operators to share, or
configure a configure a configure a
dedicated local S1 dedicated local S1 dedicated local X2
user-plane IP user-plane IP user-plane IP
address for each address for each address for each
operator. operator. operator.
Peer user plane Configure a Configure a single Configure a single

dedicated peer S1 peer S1 user-plane peer X2 user-plane
user-plane IP IP address for the IP address for the
address for each operators to share, or operators to share, or
operator. configure a configure a
dedicated peer S1 dedicated peer X2
user-plane IP user-plane IP
address for each address for each
operator. operator.
Link Mode
Table 5-5 Control-plane transmission link configuration in link mode for RAN sharing with
dedicated carrier
Link MMEs MMEs
Control plane Configure dedicated Configure dedicated Configure dedicated

each operator. each operator. each operator.

eRAN
Table 5-6 User-plane transmission link configuration in link mode for RAN sharing with
dedicated carrier
Link S-GWs GWs
User plane Configure a Configure a single Configure a single

dedicated IPPATH IPPATH MO for the IPPATH MO for the
MO for each operators to share, or operators to share, or
operator. configure a configure a
dedicated IPPATH dedicated IPPATH
MO for each MO for each
operator. operator.
If a dedicated If a dedicated
IPPATH MO is IPPATH MO is
configured for each configured for each
operator, configure operator, configure
CnOperatorIpPath CnOperatorIpPath
MOs to define the MOs to define the
mapping between mapping between
the operators and the the operators and the
IP paths. IP 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.10.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.11 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.

eRAN
5.2.2 Impacts
Network Impacts
None
Function Impacts
Name
FDD Out-of-band OutOfBandRelayS Relay When out-of-band relay

relay witch option of the and RAN sharing with
CellAlgoSwitch.Rel dedicated carrier are both
aySwitch parameter enabled, all the resources
(including the licensed
traffic and
RRC_CONNECTED UE
resources) of an eNodeB
can only be completely
shared among operators
(not in proportions).
FDD In-band relay None Relay When in-band relay and

RAN sharing with
dedicated carrier are both
enabled, all the resources
(including the licensed
traffic and
RRC_CONNECTED UE
resources) of an eNodeB
can only be completely
shared among operators
(not in proportions).
5.3 Requirements
5.3.1 Licenses
FDD LOFD-00103 RAN Sharing with LT1S00RS per cell

7 Dedicated Carrier DC00
NB-IoT MLOFD-121 NB-IoT RAN ML1S00R per cell

252 Sharing with SDC00
Dedicated Carrier

eRAN
5.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.
RAT Function Function Reference Description
Name Switch
FDD S1-flex None S1-flex This function is

required if the
MOCN
architecture is
used.

Name Switch
FDD RAN sharing ENodeBSharin RAN Sharing Each operator

with common gMode.ENode supports only
carrier BSharingMode one RAN
sharing mode.
NB-IoT NB-IoT RAN ENodeBSharin RAN Sharing Each operator

sharing with gMode.ENode supports only
common carrier BSharingMode one RAN
sharing mode.
FDD Hybrid RAN ENodeBSharin RAN Sharing Each operator

sharing gMode.ENode supports only
BSharingMode one RAN
sharing mode.
FDD Out-of-band OutOfBandRel Relay This function

relay aySwitch does not
option of the support
CELLALGOS multiple
WITCH.Relay operators.
Switch Therefore, it
parameter does not work
with RAN
sharing with
dedicated
carrier.

eRAN

Name Switch
FDD In-band relay None Relay This function

does not
support
multiple
operators.
Therefore, it
does not work
with RAN
sharing with
dedicated
carrier.
5.3.3 Hardware
Base Station Models
For NB-IoT, the following base stations are compatible with this function:
Boards
No requirements
RF Modules
No requirements
5.3.4 Others
None
5.4 Operation and Maintenance
5.4.1 Data Configuration (FDD)

The transmission and interface data required in RAN sharing with dedicated carrier is similar
to that in the independent operator mode. The configurations vary depending on the network

eRAN
architecture in use. For details, see 5.1.6 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.

The following table describes the parameters used for function activation in both FDD and
NB-IoT.
Table 5-7 Parameters used for activation
Parameter Name Parameter ID Setting Notes
Local tracking area ID CnOperatorTa.TrackingAr None

eaId
CN Operator ID CnOperatorTa.CnOperator None

Id
Tracking area code CnOperatorTa.Tac None
Local cell ID CellOp.LocalCellId None
Local tracking area ID CellOp.TrackingAreaId Only one parameter value

can be configured in each
cell where RAN sharing
with dedicated carrier is
enabled.
CN Operator ID CnOperator.CnOperatorId The

CnOperator.CnOperatorId
parameter values must be
different between operators.
The parameter value for
each operator must be the
same on all eNodeBs
managed by the same OSS.
The PLMN ID uniquely
identifies an operator
globally, which is composed
of the MCC and MNC.
CN Operator name CnOperator.CnOperatorN None

ame
CN Operator type CnOperator.CnOperatorTy Set this parameter to

pe CNOPERATOR_PRIMA
RY or
CNOPERATOR_SECON
DARY based on the
contracts signed by the
operators.

eRAN
Mobile country code CnOperator.Mcc None
Mobile network code CnOperator.Mnc None
eNodeB sharing mode ENodeBSharingMode.ENo Set this parameter to

deBSharingMode SEPARATED_FREQ.
The following table describes the parameters used for function activation specific to NB-IoT.
Table 5-8 Parameters used for activation specific to NB-IoT

S1 Configuration Type MmeCapInfo.S1CfgType Set this parameter to

S1INTERFACE_CFG.
The following table describes the parameters used for function optimization in both FDD and
NB-IoT.
Table 5-9 Parameters used for optimization in both FDD and NB-IoT
Different Operator With GlobalProcSwitch.DiffOp Set this parameter based on

Same MMEC Switch WithSameMmecSwitch the network plan.
The following table describes the parameters used for function optimization specific to FDD.
Table 5-10 Parameters used for optimization specific to FDD

CN Operator ID LicenseSharingPoli- None

cy.CnOperatorId
The proportion of the LicenseSharingPoli- Set this parameter based on

maximum number of users cy.MaxUserNumRate the network plan.
The proportion of the LicenseSharingPoli- Set this parameter based on

sharing number of users cy.UserNumSharingRate the network plan.
User Number Sharing Group LicenseSharingPoli- None

ID cy.UserNumSharingGrou-
pId
Uplink Traffic License Ratio LicRatio.UpLicRatio Set this parameter based on

the network plan.

eRAN
Traffic Sharing Type LicRatio.TrafficSharingTy Set this parameter based on

pe the network plan.
CN Operator ID LicRatioSharePoli- None

cy.CnOperatorId
TrfRatio LicRatioSharePoli- Set this parameter based on

cy.TrfRatio the network plan.
TrfSharingRatio LicRatioSharePoli- Set this parameter based on

cy.TrfSharingRatio the network plan.
The following table describes the parameters used for function optimization specific to NB-
IoT.
Table 5-11 Parameters used for optimization specific to NB-IoT
CN Operator ID NbSharingPolicy.CnOperat None

orId
UE Context Proportion NbSharingPolicy.UeContex Set this parameter based on

tProportion the network plan.

RAN 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.
l 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.
the three operators that share eNodeB hardware resources, a cell and the related
secondary-operator configurations must be removed.
l The sharing mode of an eNodeB is changed from the RAN sharing with dedicated carrier
mode to the independent operator mode.

eRAN
Configuration.
RAN sharing with dedicated carrier mode
d. (Optional) NbSharingPolicy: Used to set the proportion of UE contexts that can be
e. CnOperatorTa: Used to add tracking area information.
f. CellOp: Used to set the cell operator information.
g. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
h. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for
c. (Optional) NbSharingPolicy: Used to set the proportion of UE contexts that can be
e. CellOp: Used to set the cell operator information.
f. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
g. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for
a. (Optional) LicenseSharingPolicy: Used to remove the configured licensed
b. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.
c. (Optional) NbSharingPolicy: Used to remove the configured proportion of UE
e. CnOperatorTa: Used to remove the tracking area information.

eRAN
f. (Optional) LicRatioSharePolicy: Used to remove the configuration of the licensed

g. CnOperator: Used to remove the operator information.
l Changing the sharing mode of an eNodeB from the RAN sharing with dedicated carrier
mode to the independent operator mode
a. (Optional) X2Interface: Used to remove the X2 interface in FDD if it has been
configured.
f. CellOp: Used to remove the cell operator information.
g. S1Interface: Used to remove the S1 interface.
h. CnOperatorTa: Used to remove the tracking area information.
i. CnOperator: Used to remove the operator information.
j. ENodeBSharingMode: Used to set the eNodeB sharing mode to the independent

The following are command examples for function activation in FDD:
MOD ENODEBSHARINGMODE: ENodeBSharingMode=SEPARATED_FREQ;
//Configuring information related to RAN sharing with dedicated carrier
CellReservedForOp=CELL_NOT_RESERVED_FOR_OP;
RST APP: AID=1;

eRAN
The following are command examples for function activation in NB-IoT:

MOD ENODEBSHARINGMODE: ENodeBSharingMode=SEPARATED_FREQ;
//Configuring information related to RAN sharing with dedicated carrier
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
ADD CELLOP: LocalCellId=1, TrackingAreaId=1;
//Enabling the MME to support NB-IoT
RST APP: AID=1;

The following are command examples for function optimization in FDD:
other operators
The following are command examples for function optimization in NB-IoT:

//Configuring the proportion of UE contexts that are stored on an eNodeB in NB-
IoT user plane mode for each operator
the same MMEC


eRAN

Prerequisites
l Based on the network plan, the eNodeB is shared between two operators that use
dedicated carriers.
l The transmission links between the eNodeB and EPCs are functioning normally.
l Two UEs (UE 1 and UE 2) are ready. They respectively subscribe to services of the two
operators.
Procedure
Step 1 Check the cell status by running the following commands:
Expected result:
--------------------------start--------------------------
%%/*44421*/DSP CELL: LOCALCELLID=0;%%
...
Local cell ID = 0
...
...
Local cell ID = 1
...
--------------------------end---------------------------
Step 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)

eRAN
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)
Step 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-Msg
\initiatingMessage\value\initialUEMessage\protocolIEs\SEQUENCE\value\tAI.
----End

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 as that in independent operator mode.

eRAN
RAN Sharing Feature Parameter Description 6 RAN Sharing with Special Dedicated Carrier (FDD)
6 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:
l 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.
l 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.
NOTE
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 works only in FDD cells where NB-IoT is not
used. When RAN sharing with special dedicated carrier is enabled, NB-IoT cells cannot
provide services.

eRAN
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.

l Mobility management in connected mode
l ANR management
l 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 6.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.

eRAN

When method 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.
l No CellOp MO is configured.
l 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 RAN sharing with special dedicated carrier is enabled, the ADD_FREQ_CFG_SW
option of the GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter and 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.
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. Note that if a cell where RAN sharing
with special dedicated carrier is enabled needs to be manually configured as a neighboring
cell, 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 is set to CNOPERATOR_PRIMARY.

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.

eRAN

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.8 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:
l Disable ANR on any Huawei eNodeB adjacent to the other vendor's eNodeB.
l Manually configure neighbor relationships for Huawei eNodeB.
l 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.5.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.9.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 method 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 method 2.

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.
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.10 Transmission
Networking.

eRAN

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.11 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
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
None
6.3 Requirements
6.3.1 Licenses
FDD LOFD-001037 RAN Sharing LT1S00RSDC0 per cell

with Dedicated 0
Carrier
6.3.2 Software
feature documents.

eRAN
Function Function Switch Reference Description
Name
S1-flex None S1-flex This function is required if

the MOCN architecture is
used.

Functions that do not work with RAN sharing with special dedicated carrier are the same as
those with RAN sharing with dedicated carrier. For details, see 5.3.2 Software.
6.3.3 Hardware
Base Station Models

The following base stations are compatible with this function:

Boards
No requirements
RF Modules
No requirements
6.3.4 Others
None

Table 6-1 and Table 6-2 describe the parameters used for function activation and
optimization, respectively.

eRAN

Local tracking area ID CnOperatorTa.TrackingAr None

eaId
CN Operator ID CnOperatorTa.CnOperator None

Id
Tracking area code CnOperatorTa.Tac In a cell where RAN sharing

with special dedicated carrier is
enabled, configure the same
TAC for all operators.
Local cell ID CellOp.LocalCellId None

eRAN
Local tracking area ID CellOp.TrackingAreaId In a cell where case 1 of RAN

sharing with special dedicated
carrier is used, only one
CellOp.TrackingAreaId
parameter value can be
configured.
When case 2 of RAN sharing
with special dedicated carrier is
used, only one
parameter value can be
configured in a cell of the
primary operator. In a cell of a
secondary operator, two
parameter values must be
configured and the
corresponding
CnOperatorTa.CnOperatorId
parameters must be set to
different values with one being
set to the ID of the primary
operator. In addition, the
CellOp.CellReservedForOp
parameter of the primary
operator must be set to
CELL_RESERVED_FOR_OP
.
When the GWCN architecture is
used, only case 2 of RAN
sharing with special dedicated
carrier is supported. That is, the
CellOp MO of the primary
operator must be configured for
cells of a secondary operator and
the CnOperatorTa MO
associated with the
CellOp.TrackingAreaID
parameter must be configured.
Cell reserved for CellOp.CellReservedForOp When case 2 of RAN sharing

operator with special dedicated carrier is
used, the
CellOp.CellReservedForOp
parameter of the primary
operator configured for a cell of
a secondary operator must be set
to
CELL_RESERVED_FOR_OP
.

eRAN
CN Operator ID CnOperator.CnOperatorId By default, one eNodeB can be

configured with data for up to
four operators, whose
CnOperator.CnOperatorId
values must be different.
The parameter value for each
operator must be the same on all
eNodeBs managed by the same
OSS. The PLMN ID uniquely
identifies an operator globally,
which is composed of the MCC
and MNC.
CN Operator name CnOperator.CnOperatorNa None

me
CN Operator type CnOperator.CnOperatorTy Set this parameter to

pe CNOPERATOR_PRIMARY
or
CNOPERATOR_SECONDAR
Y based on the contracts signed
by the operators.
Mobile country code CnOperator.Mcc None
Mobile network code CnOperator.Mnc None
eNodeB sharing mode ENodeBSharingMode.ENo Set this parameter to

deBSharingMode SEPARATED_FREQ_SPEC.
Table 6-2 Parameters used for optimization

Parameter Name Parameter ID Optio Setting Notes
n
CN Operator ID LicenseSharingPoli- N/A None

cy.CnOperatorId
The proportion of LicenseSharingPoli- N/A Set this parameter based on

the maximum cy.MaxUserNumRate the network plan.
number of users
The proportion of LicenseSharingPoli- N/A Set this parameter based on

the sharing number cy.UserNumSharingRate the network plan.
of users
Uplink Traffic LicRatio.UpLicRatio N/A Set this parameter based on

License Ratio the network plan.
Traffic Sharing LicRatio.TrafficSharingT N/A Set this parameter based on

Type ype the network plan.

eRAN

n
CN Operator ID LicRatioSharePoli- N/A None

cy.CnOperatorId
TrfRatio LicRatioSharePoli- N/A Set this parameter based on

cy.TrfRatio the network plan.
TrfSharingRatio LicRatioSharePoli- N/A Set this parameter based on

cy.TrfSharingRatio the network plan.
Different Operator GlobalProcSwitch. N/A Set this parameter based on

With Same MMEC DiffOpWithSameMmecS- the network plan.
Switch witch
Handover Algo ENodeBAlgoSwitch.HoA InterPl Deselect this option.

switch lgoSwitch mnHo
Switch
X2-based GlobalProcSwitch.X2Bas ADD_ Deselect this option.

Neighboring Cell edUptNcellCfgSwitch FREQ
Configuration _CFG
Update Switch _SW
Local cell ID EutranNFreqSCel- N/A None

lOp.LocalCellId
Downlink EutranNFreqSCel- N/A None

EARFCN lOp.DlEarfcn
Cn operator ID EutranNFreqSCel- N/A Set this parameter to the same

lOp.CnOperatorID value as the CN Operator ID
parameter in the CnOperator
MO.
Cell reselection EutranNFreqSCel- N/A When case 1 of RAN sharing

dedicated priority lOp.CellReselDediPriCf- with special dedicated carrier
configure indicator gInd is used, the frequency of the
primary operator for which no
CellOp MO is configured and
the "reserved" status is
broadcast must be configured
as a neighboring frequency in
each cell of a secondary
operator.
Cell reselection EutranNFreqSCel- N/A None

dedicated priority lOp.CellReselDediPri
Local cell ID EutranInterNFreq.Local N/A None

CellId

eRAN

n
Downlink EutranInterNFreq.DlEar N/A When RAN sharing with

EARFCN fcn special dedicated carrier is
used, the neighboring
frequencies of a cell of the
primary operator cannot be set
to the frequencies of cells of a
secondary operator.
When case 1 of RAN sharing
with special dedicated carrier
is used, the frequency of the
primary operator for which no
CellOp MO is configured and
the "reserved" status is
broadcast must be configured
as a neighboring frequency in
each cell of a secondary
operator.
Inter frequency EutranInterNFreq.CellR N/A Set this parameter to CFG.

cell resel priority eselPriorityCfgInd
configure indicator
Inter frequency EutranInterNFreq.CellR N/A None

cell resel priority eselPriority

RAN 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.
l 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.
the three operators that share RAN resources in RAN sharing with special dedicated
carrier mode, a cell and the related secondary-operator configurations must be removed.
l The sharing mode of an eNodeB is changed from the RAN sharing with special
dedicated carrier mode to the independent operator mode.

eRAN
Configuration.
RAN sharing with special dedicated carrier mode
d. (Optional) NbSharingPolicy: Used to set the proportion of UE contexts that can be
e. CnOperatorTa: Used to add tracking area information.
f. CellOp: Used to set the cell operator information.
g. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
h. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for
c. (Optional) NbSharingPolicy: Used to set the proportion of UE contexts that can be
e. CellOp: Used to set the cell operator information.
f. (Optional) LicRatio: Used to set the traffic sharing mode in FDD.
g. (Optional) LicRatioSharePolicy: Used to set the licensed traffic proportion for
a. (Optional) LicenseSharingPolicy: Used to remove the configured licensed
b. (Optional) LicRatio: Used to change the traffic sharing mode in FDD.
e. CnOperatorTa: Used to remove the tracking area information.

eRAN
f. (Optional) LicRatioSharePolicy: Used to remove the configuration of the licensed

g. CnOperator: Used to remove the operator information.
l Changing the sharing mode of an eNodeB from the RAN sharing with special dedicated
carrier mode to the independent operator mode
a. (Optional) X2Interface: Used to remove the X2 interface in FDD if it has been
configured.
f. CellOp: Used to remove the cell operator information.
g. S1Interface: Used to remove the S1 interface.
h. CnOperatorTa: Used to remove the tracking area information.
i. CnOperator: Used to remove the operator information.
j. ENodeBSharingMode: Used to set the eNodeB sharing mode to the independent

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.
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0,
UpEpGroupId=0;
ADD X2: X2Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=2,
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

eRAN
used.
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0;
ADD X2INTERFACE: X2InterfaceId=0, X2CpBearerId=0, CnOperatorId=0;
//Configuring a TAC for the primary operator in a reserved state when case 2 of
RAN sharing with special dedicated carrier is used
RST APP: AID=1;

other operators
UserNumSharingRate=0;
UserNumSharingRate=0;
the same 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
CellReservedForOp=CELL_RESERVED_FOR_OP;
ADD EUTRANINTERNFREQ: LocalCellId=1, DlEarfcn=1234, CellReselPriorityCfgInd=CFG,
CellReselPriority=3, MeasBandwidth=MBW75;


eRAN
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:
--------------------------start--------------------------
RETCODE = 0
Operation succeeded.
...
Local cell ID = 0
...
%%/44423*/DSP CELL: LOCALCELLID=1;%%
RETCODE = 0
...
Local cell ID = 1
...
--------------------------end---------------------------

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

eRAN
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)
Step 3 Power on the two UEs to initiate attach procedures towards the respective cells.
Expected result:

the UEs have successfully accessed the respective cells and selected the correct EPCs. In this
----End

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 details about these counters, see 4.4.3 Network
Monitoring.

eRAN
RAN Sharing Feature Parameter Description 7 Hybrid RAN Sharing
7 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:
l 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.

eRAN
Figure 7-1 Network architecture for hybrid RAN sharing (1)
l 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:

eRAN
l An eNodeB has two or more frequencies.

l At least one frequency is shared by operators.
l 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:
l Broadcasting information about primary and secondary operators.

l Setting up proper transmission links.
Hybrid RAN sharing enables flexible resource sharing for operators.
l Compared with RAN sharing with common carrier, hybrid RAN sharing allows the
primary PLMN ID to be different between cells.
l 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.
l NE functions
l ANR management
l 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:
l Support the hybrid RAN sharing configurations.

l 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
l Broadcast the PLMN ID information for a shared cell based on the carrier-sharing
operator group to which the cell belongs
l Set up transmission links on a per carrier-sharing operator group basis

eRAN
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 EPC, it notifies the eNodeB of the selected EPC 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.

eRAN
l 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.
l 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, 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.
7.1.5.1 Feature Control

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 Fair Sharing of Air Interface Resources.

eRAN
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.8 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.
information.

Fault management in hybrid RAN sharing is the same as that in RAN sharing with common
carrier. For details, see 4.1.9.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.

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.

eRAN

Transmission port planning in hybrid RAN sharing is the same as that in RAN sharing with
common carrier. For details, see 4.1.10.1 Transmission Port Planning.

For basic information about transmission link setup, see 4.1.10 Transmission Networking.
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
Link MMEs MMEs
Control-plane link Dedicated Dedicated Dedicated

between carrier-
sharing operator
groups
Control-plane link Dedicated Shared Shared

within one carrier-
sharing operator
group

Link S-GWs GWs

between carrier-
sharing operator
groups

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

eRAN
Table 7-2 Control-plane transmission link configuration in endpoint mode for hybrid RAN
sharing between carrier-sharing operator groups
Item MMEs MMEs
Control-plane S1 or Configure a Configure a Configure a

X2 MO dedicated S1 MO for dedicated S1 MO for dedicated X2 MO
each carrier-sharing each carrier-sharing for each carrier-
operator group, and operator group, and sharing operator
specify a unique specify a unique group, and specify a
CpEpGroupId CpEpGroupId unique
parameter for each parameter for each CpEpGroupId
MO. MO. parameter for each
MO.
Specify a same
SCTPHOST MO
for different
CpEpGroupId
parameters within a
carrier-sharing
operator group.
Specify a unique
SCTPHOST MO
for each carrier-
sharing operator
group.
Local control plane Configure a Configure a Configure a

control-plane IP control-plane IP control-plane IP
carrier-sharing carrier-sharing carrier-sharing
operator group, or operator group, or operator group.
configure a single configure a single Alternatively,
local S1 control- local S1 control- configure a single
plane IP address for plane IP address for local X2 control-
the carrier-sharing the carrier-sharing plane IP address for
operator groups to operator groups to the carrier-sharing
share. share. operator groups to
share and a
dedicated SCTP port
number for each
carrier-sharing
operator group.

eRAN

Item MMEs MMEs
Peer control plane Configure a Configure a Configure a

dedicated peer S1 dedicated peer S1 dedicated peer X2
control-plane IP control-plane IP control-plane IP
operator group. operator group, or operator group, or
configure a single configure a single
peer S1 control- peer X2 control-
plane IP address for plane IP address for
the carrier-sharing the carrier-sharing
operator groups to operator groups to
share. share.
Table 7-3 User-plane transmission link configuration in endpoint mode for hybrid RAN
sharing between carrier-sharing operator groups
Item S-GWs GWs
User-plane S1 or Configure a Configure a Configure a

X2 MO dedicated S1 MO for dedicated S1 MO for dedicated X2 MO
each carrier-sharing each carrier-sharing for each carrier-
operator group, and operator group, or sharing operator
specify a unique configure a single S1 group, or configure a
UpEpGroupId MO for the carrier- single X2 MO for
parameter for each sharing operator the carrier-sharing
MO. groups to share. operator groups to
Specify a unique or share. Specify a
use the same unique or use the
UpEpGroupId same UpEpGroupId
parameter for each parameter for each
MO. MO.
Local user plane Configure a Configure a Configure a

operator group, or operator group, or operator group, or
configure a single configure a single configure a single
operator groups to operator groups to operator groups to
share. share. share.

eRAN

Item S-GWs GWs
Peer user plane Configure a Configure a Configure a

peer S1 user-plane peer X2 user-plane
IP address for the IP address for the
carrier-sharing carrier-sharing
operator groups to operator groups to
share. share.
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
Item MMEs MMEs
S1 or X2 MO Configure a Configure an S1 MO l If the peer

dedicated S1 MO for for the operators to operators are
each operator within share within a within the same
a carrier-sharing carrier-sharing carrier-sharing
operator group, and operator group. operator group,
specify a unique configure the
CpEpGroupId same X2 control-
parameter for each plane link for
MO. them to share.
l If the peer
operators are not
in the same
carrier-sharing
operator group,
they use different
X2 control-plane
links. Configure
a unique
CpEpGroupId
parameter for
each MO.

eRAN

Item MMEs MMEs
Local control plane Configure a single Configure a local S1 Configure a local X2

local S1 control- control-plane IP control-plane IP
plane IP address for address for the address for the
the operators to operators to share operators to share
share within a group. within a carrier- within a carrier-
sharing operator sharing operator
group. group.
Peer control plane Configure a Configure a peer S1 l If the peer

dedicated peer S1 control-plane IP operators are
control-plane IP address for the within the same
address for each operators to share carrier-sharing
operator within a within a carrier- operator group,
group. sharing operator configure the
group. same peer X2
control-plane IP
address for them
to share.
l If the peer
operators are not
in the same
carrier-sharing
operator group,
configure a
dedicated peer
X2 control-plane
IP address for
each operator
within a group.
Table 7-5 User-plane transmission link configuration in endpoint mode for hybrid RAN
sharing within a carrier-sharing operator group
Item S-GWs GWs

dedicated user-plane dedicated user-plane dedicated user-plane
S1 MO for each S1 MO for each X2 MO for each
operator within a operator within a operator within a
user-plane S1 MO user-plane X2 MO
for the operators to for the operators to
share within a group. share within a group.

eRAN

Item S-GWs GWs
Local user plane Configure a single Configure a single Configure a

local S1 user-plane local S1 user-plane dedicated local X2
IP address for the IP address for the user-plane IP
operators to share operators to share address for each
within a group. within a group. operator within the
group, or configure a
single local X2 user-
plane IP address for
the operators to
share within a group.
Peer user plane Configure a Configure a Configure a

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

each carrier-sharing each carrier-sharing each carrier-sharing
operator group. operator group. operator group.

eRAN
Table 7-7 User-plane transmission link configuration in link mode for hybrid RAN sharing
between carrier-sharing operator groups
Transmission S1 with Shared S- S1 with Dedicated X2
Link GWs S-GWs
User plane Configure a Configure a Configure a

dedicated IPPATH dedicated IPPATH dedicated IPPATH
MO for each MO for each MO for each
operator, or operator. operator, or
IPPATH MO for the IPPATH MO for the
operators to share. operators to share.
Table 7-8 Control-plane transmission link configuration in link mode for hybrid RAN sharing
within a carrier-sharing operator group
Transmission S1 with Shared S1 with Dedicated X2
Link MMEs MMEs
Control plane Configure the Configure dedicated l If the peer

S1Interface and S1Interface and operators are
SCTPLNK MOs for SCTPLNK MOs for within the same
the operators to each operator. carrier-sharing
share within a group. operator group,
configure the
X2Interface and
SCTPLNK MOs
for them to share.
l If the peer
operators are not
in the same
carrier-sharing
operator group,
configure
dedicated
X2Interface and
SCTPLNK
MOs.

eRAN
Table 7-9 User-plane transmission link configuration in link mode for hybrid RAN sharing
within a carrier-sharing operator group
Transmission S1 with Shared S- S1 with Dedicated X2
Link GWs S-GWs
User plane Configure a Configure a Configure a

dedicated IPPATH dedicated IPPATH dedicated IPPATH
MO for each MO for each MO for each
operator, or operator. operator, or
IPPATH MO for the IPPATH MO for the
operators to share operators to share
within the group. 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.10.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.10.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.11 Multi-operator PKI.
7.2.1 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

eRAN
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
Name
FDD None N/A N/A N/A
7.3 Requirements
7.3.1 Licenses
FDD LOFD-070206 Hybrid RAN LT1S0HRANS00 per cell

Sharing
7.3.2 Software
feature documents.
RAT Function Name Function Switch Reference Description
FDD S1-flex None S1-flex This function is

required if the
MOCN
architecture is
used.

eRAN

RAT Function Name Function Switch Reference Description
FDD RAN sharing ENodeBSharingM RAN Sharing Each operator

with common ode.ENodeBShari supports only one
carrier ngMode RAN sharing
mode.
FDD RAN sharing ENodeBSharingM RAN Sharing Each operator

with dedicated ode.ENodeBShari supports only one
carrier ngMode RAN sharing
mode.
FDD Out-of-band relay OutOfBandRelay Relay This function

Switch option of does not support
the multiple
CELLALGOSWI operators.
TCH.RelaySwitch Therefore, it does
parameter not work with
hybrid RAN
sharing.
FDD In-band relay None Relay This function

does not support
multiple
operators.
Therefore, it does
not work with
hybrid RAN
sharing.
FDD Intra-RAT ANR l IntraRatEvent ANR If the serving cell

AnrSwitch Management and neighboring
option of the cells are managed
ENodeBAlgoS by different
witch.AnrSwitc OSSs, intra-RAT
h parameter: ANR does not
controlling work when the
intra-RAT PLMN ID at the
event-triggered top of the PLMN
ANR list is rotated.
l IntraRatFastA
nrSwitch option
of the
ENodeBAlgoS
witch.AnrSwitc
h parameter:
controlling
intra-RAT fast
ANR

eRAN
7.3.3 Hardware
Base Station Models


Boards
No requirements
RF Modules
No requirements
7.3.4 Others
None
7.4.1 Data Configuration (FDD)

The transmission and interface data required in hybrid RAN sharing 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 Cell Management, Mobility Management in Connected Mode, and this section.

The following table describes the parameters used for function activation.

Name
CN Operator ID CnOperator.C The CnOperator.CnOperatorId parameter values

nOperatorId must be different between operators.
The parameter value for each operator must be the
same on all eNodeBs managed by the same OSS. The
PLMN ID uniquely identifies an operator globally,
which is composed of the MCC and MNC.

eRAN

Name
CN Operator CnOperator.C None

name nOperatorNam
e
CN Operator CnOperator.C The configuration of the primary and secondary

type nOperatorType operators does not take effect for hybrid RAN
sharing. When the license for hybrid RAN sharing is
invalid, the primary operator configured by this
parameter takes effect for the eNodeB and the
primary operator's links are retained. The primary
operator must be the primary operator of a RAN
sharing operator group. Every eNodeB must be
configured with one primary operator.
Mobile country CnOperator.M None

code cc
Mobile network CnOperator.M None

code nc
CN Operator CnOpSharing None

Sharing Group Group.CnOpS
ID haringGroupId
Primary CnOpSharing None

Operator ID Group.Primary
OperatorId
Secondary CnOpSharing None

Operator List Group.Second
aryOperatorlist
Local Cell ID Cell.LocalCellI None

d
CN Operator Cell.CnOpShar None

Sharing Group ingGroupId
ID
S1 ID S1.S1Id None
CN Operator S1.CnOpShari None

Sharing Group ngGroupId
ID
S1 Interface ID S1Interface.S1 None

InterfaceId
CN Operator S1Interface.Cn None

Sharing Group OpSharingGro
ID upId
X2 ID X2.X2Id None

eRAN

Name
CN Operator X2.CnOpShari None

Sharing Group ngGroupId
ID
X2Interface ID X2Interface.X2 None

InterfaceId
CN Operator X2Interface.C None

Sharing Group nOpSharingGr
ID oupId
Local tracking CnOperatorTa None

area ID .TrackingAreaI
d
CN Operator ID CnOperatorTa None

.CnOperatorId
Tracking area CnOperatorTa In a cell where hybrid RAN sharing is enabled,

code .Tac configure the same TAC for all operators.
Local cell ID CellOp.LocalC None

ellId
Local tracking CellOp.Tracki For example, when the eNodeB is shared by two
area ID ngAreaId operators in hybrid RAN sharing mode, a cell must
be configured with the tracking area IDs of both
operators, and the two tracking area IDs must
correspond to the same TAC.
In a cell where hybrid RAN sharing is enabled, the
CnOperatorTa.CnOperatorId values must be
different. One of the parameter values must
correspond to the primary operator of the RAN
sharing group.
Operator uplink CellOp.OpUlR The sum of the CellOp.OpUlRbUsedRatio values

RB used ratio bUsedRatio configured for all operators involved in hybrid RAN
sharing must not exceed 100%.
Operator CellOp.OpDlR The sum of the CellOp.OpDlRbUsedRatio values

downlink RB bUsedRatio configured for all operators involved in hybrid RAN
used ratio sharing must not exceed 100%.
Operator CellOp.Operat None

PLMN Round orPlmnRoundP
Period eriod
Operator CellOp.OpReso None

Resource Group urceGroupInde
Index x

eRAN

Name
eNodeB sharing ENodeBSharin Set this parameter to HYBRID_SHARED.

mode gMode.ENode
BSharingMode
Table 7-11 Parameters used for optimization

Name
CN Operator ID LicenseSharin N/A None

gPolicy.CnOpe
ratorId
The proportion LicenseSharin N/A If the licensed

of the gPolicy.MaxUs RRC_CONNECTED UE
maximum erNumRate resources of the eNodeB are
number of users distributed among operators in
proportions, the maximum number
of RRC_CONNECTED UEs
served by each operator cannot
exceed the predefined proportion.
If the proportions are not
specified, all the operators share
the total licensed number of
RRC_CONNECTED UEs of the
eNodeB.

of the sharing gPolicy.UserNu
number of users mSharingRate
User Number LicenseSharin N/A None

Sharing Group gPolicy.UserNu
ID mSharingGrou
pId
Local cell ID CellAlgoSwitc N/A None

h.LocalCellId
RAN Sharing CellAlgoSwitc N/A None

Mode Switch h.RanShareMo
deSwitch
Operator CellAlgoSwitc N/A None

Resource Group h.OpResource
Share Switch GroupShareSw
itch
Local cell ID CellAccess.Loc N/A None

alCellId

eRAN

Name
Plmn Broadcast CellAccess.Bro N/A None

Mode adcastMode
Plmn Round CellAccess.Rou N/A None

Broadcast ndPeriod
Period
Plmn Round CellAccess.Rou N/A None

Action Time ndActionTime
Uplink Traffic LicRatio.UpLic N/A None

License Ratio Ratio
Traffic Sharing LicRatio.Traffi N/A None

Type cSharingType
CN Operator ID LicRatioShare N/A None

Policy.CnOper
atorId
TrfRatio LicRatioShare N/A None

Policy.TrfRatio
TrfSharingRatio LicRatioShare N/A None

Policy.TrfShari
ngRatio
Different GlobalProcSwi N/A None

Operator With tch.DiffOpWith
Same MMEC SameMmecSwi
Switch tch

eRAN

Name
ANR Under ENodeBAlgoS N/A Select the

RAN Sharing witch.RanShar NBSLTEPLMNRoundSwitch
Algorithm ingAnrSwitch option of this parameter for an
Switch eNodeB if a cell (Cell 1) under the
l Cell 2 supports hybrid RAN
sharing.
l The
parameter is set to RR_MODE
or FREE_Mode for Cell 2.
Select the
NBSLTERANSharingSwitch
option of this parameter for an
eNodeB if a cell (Cell 1) under the
l Cell 2 supports hybrid RAN
sharing.
l The
parameter is set to
NORMAL_MODE for Cell 2.
Handover Algo ENodeBAlgoS InterPlmnHoSw Select this option.

switch witch.HoAlgoS itch
witch
CN Operator ID InterPlmnHoL N/A None

ist.CnOperator
Id

country code ist.TarMcc

network code ist.TarMnc
RAT frequency RatFreqPriorit N/A None

priority group yGroup.RatFre
ID qPriorityGroup
Id
RAT Type RatFreqPriorit N/A None

yGroup.RatTyp
e

eRAN

Name
DL Earfcn or RatFreqPriorit N/A None

Bandclass yGroup.DlEarf
cn
Priority RatFreqPriorit N/A None

yGroup.Priorit
y
GERAN RatFreqPriorit N/A None

Frequency yGroup.BandI
Indicator ndicator
Spid SpidCfg.Spid N/A None

priority eqPriorityInd
indication

priority group eqPriorityGrou
ID pId
The following table describes the parameters that must be set to configure the dedicated cell-
reselection priority for a GERAN frequency based on the serving cell's PLMN.

Name

pSCellOp.Loca
lCellId

ID pSCellOp.Bcch
GroupId
Cn operator ID GeranNFGrou None

pSCellOp.CnO
peratorID

configure gInd
indicator
Cell reselection GeranNFGrou The dedicated cell-reselection priorities of different

dedicated pSCellOp.Cell RATs must be different.

eRAN
reselection priority for a GERAN frequency based on the neighboring frequency's HPLMN.

Name
Local cell ID GeranRanShar None

e.LocalCellId
BCCH group GeranRanShar None

ID e.BcchGroupId
Mobile country GeranRanShar None

code e.Mcc
Mobile network GeranRanShar None

code e.Mnc
Cell reselection GeranRanShar None

configure rityCfgInd
indicator
Cell reselection GeranRanShar Set this parameter based on the network plan.
rity
reselection priority for a UTRAN frequency based on the serving cell's PLMN.

Name
Local cell ID UtranNFreqSC None

ellOp.LocalCellI
d
Downlink UtranNFreqSC None

UARFCN ellOp.UtranDlA
rfcn
Cn operator ID UtranNFreqSC None

ellOp.CnOperat
orID
Cell reselection UtranNFreqSC None

dedicated ellOp.CellResel
priority DediPriCfgInd
configure
indicator
Cell reselection UtranNFreqSC The dedicated cell-reselection priorities of different

dedicated ellOp.CellResel RATs must be different.
priority DediPri

eRAN
reselection priority for a UTRAN frequency based on the neighboring frequency's HPLMN.

Name
Local cell ID UtranRanShare. None

LocalCellId
Downlink UtranRanShare. None

UARFCN UtranDlArfcn
Mobile country UtranRanShare. None

code Mcc
Mobile network UtranRanShare. None

code Mnc
Cell reselection UtranRanShare. None

priority CellReselPriori-
configure tyCfgInd
indicator
Cell reselection UtranRanShare. Set this parameter based on the network plan.
priority CellReselPriority
reselection priority for an E-UTRAN frequency based on the serving cell's PLMN.

Name
Local cell ID EutranNFreqSC None

ellOp.LocalCellI
d
Downlink EutranNFreqSC None

EARFCN ellOp.DlEarfcn
Cn operator ID EutranNFreqSC None

ellOp.CnOperato
rID
Cell reselection EutranNFreqSC None

dedicated ellOp.CellReselD
priority ediPriCfgInd
configure
indicator

eRAN

Name
Cell reselection EutranNFreqSC The dedicated cell-reselection priorities of different

dedicated ellOp.CellReselD RATs must be different.
priority ediPri
reselection priority for an E-UTRAN frequency based on the neighboring frequency's
HPLMN.

Name
Local cell ID EutranNFreqRan None

Share.LocalCellId
Downlink EutranNFreqRan None

EARFCN Share.DlEarfcn
Mobile country EutranNFreqRan None

code Share.Mcc
Mobile network EutranNFreqRan None

code Share.Mnc
Cell reselection EutranNFreqRan None

priority Share.CellReselPr
configure iorityCfgInd
indicator
Cell reselection EutranNFreqRan Set this parameter based on the network plan.
priority Share.CellReselPr
iority
reselection priority for a CDMA frequency based on the serving cell's PLMN.

Name
Local cell ID Cdma2000BcSC None

ellOp.LocalCellI
d
Band class Cdma2000BcSC None

ellOp.BandClass
Cn operator ID Cdma2000BcSC None

ellOp.CnOperato
rID

eRAN

Name
CDMA2000 Cdma2000BcSC None

1xRTT ellOp.Cdma1Xrtt
dedicated CellReselPriInd
priority
configure
indicator
CDMA2000 Cdma2000BcSC The dedicated cell-reselection priorities of different

1xRTT Cell ellOp.Cdma1Xrtt RATs must be different.
Reselection CellReselDediPri
Dedicated
Priority
CDMA2000 Cdma2000BcSC None

HRPD dedicated ellOp.HrpdCellR
priority eselDediPriCfgI
configure nd
indicator
CDMA2000 Cdma2000BcSC The dedicated cell-reselection priorities of different

HRPD Cell ellOp.HrpdCellR RATs must be different.
Reselection eselDediPri
Dedicated
Priority

l A RAN sharing operator group is added for hybrid RAN sharing.

l A RAN sharing operator group for hybrid RAN sharing is removed.
l The operator information within a RAN sharing operator group is modified.
l The sharing mode of an eNodeB is changed from the hybrid RAN sharing mode to the
independent operator mode.
Configuration.
l Adding a RAN sharing operator group for hybrid RAN sharing

a. Configure the information about the operator and the RAN sharing operator group.
i. (Optional) CnOperator: Used to add operator information.
ii. CnOpSharingGroup: Used to add RAN sharing operator group information.
b. Configure transmission links.

eRAN
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.
c. Configure a cell.
i. 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.
ii. CellOp: Used to set the cell operator information.
iii. Resource sharing policies between hybrid RAN sharing operators need to be
configured.
1) (Optional) LicenseSharingPolicy: Used to set the licensed proportion of
RRC_CONNECTED UEs for each operator.
2) CnOperatorTa: Used to add tracking area information.
3) CellAlgoSwitch: Used to set the RAN sharing mode switch.
4) (Optional) CellAccess: Used to set the cell access information.
5) (Optional) LicRatio: Used to set the traffic sharing mode.
6) (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.
d. Configure neighboring cells.
i. (Optional) EutranExternalCell: Used to configure external E-UTRAN cells.
ii. (Optional) EutranExternalCellPlmn: Used to configure the PLMNs of the
external E-UTRAN cells.
e. Use the ENodeBAlgoSwitch MO to set the ANR switch and inter-PLMN handover
information.
f. Configure the cell-reselection priority.
i. (Optional) RatFreqPriorityGroup and SpidCfg: Used to set the SPID-based
dedicated cell-reselection priority.
ii. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, or Cdma2000BcSCellOp: Used to set a dedicated
cell-reselection priority based on the serving cell's PLMN.
iii. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare:
Used to set a dedicated cell-reselection priority based on the neighboring
frequency's HPLMN.
l Removing a RAN sharing operator group from hybrid RAN sharing operator groups
a. Remove the configured cell-reselection priority.
i. (Optional) RatFreqPriorityGroup and SpidCfg: Used to remove the SPID-
based dedicated cell-reselection priority.
ii. (Optional) EutranNFreqSCellOp, UtranNFreqSCellOp,
dedicated cell-reselection priority configured based on the serving cell's
PLMN.
iii. (Optional) UtranRanShare, GeranRanShare, or EutranNFreqRanShare:
Used to remove the dedicated cell-reselection priority configured based on the
neighboring frequency's HPLMN.

eRAN
b. Use the ENodeBAlgoSwitch MO to remove the ANR switch and inter-PLMN

handover information.
c. Remove neighboring cells.
i. (Optional) EutranExternalCell: Used to remove external E-UTRAN cells.
ii. (Optional) EutranExternalCellPlmn: Used to remove the PLMNs of the
external E-UTRAN cells.
iii. EutranIntraFreqNCell, EutranInterFreqNCell, UtranNCell, and
GeranNcell: Used to remove neighboring cells of the E-UTRAN cell.
d. Remove the resource sharing policies between hybrid RAN sharing operators.
i. (Optional) LicenseSharingPolicy: Used to remove the configured licensed
proportion of RRC_CONNECTED UEs for each operator.
ii. CnOperatorTa: Used to remove the tracking area information.
iii. CellAlgoSwitch: Used to remove the RAN sharing mode switch configuration.
iv. (Optional) CellAccess: Used to remove the cell access information.
v. (Optional) LicRatio: Used to change the traffic sharing mode.
vi. (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.
e. Remove cells.
i. 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.
ii. CellOp: Used to remove the cell operator information.
f. Remove transmission links.
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.
g. Remove the information about the operator and the RAN sharing operator group.
i. CnOpSharingGroup: Used to remove the RAN sharing operator group
information.
ii. (Optional) CnOperator: Used to remove the operator information.
l Modifying the operator information within a RAN sharing operator group
– Change the primary operator.
i. 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."
ii. 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."
– Add a secondary operator.
i. (Optional) Use the CnOperator MO to add operator information.
ii. Use the CnOpSharingGroup MO to add the mapping relationship between
the secondary operator and the RAN sharing operator group.

eRAN
iii. For other steps, see steps 2 through 9 in "Adding a secondary operator" in
Parameters for Reconfiguration of 4.4.1.1 Data Preparation.
– Remove a secondary operator.
i. Perform steps 1 through 8 in "Removing a secondary operator" in Parameters
for Reconfiguration of 4.4.1.1 Data Preparation.
ii. Use the CnOpSharingGroup MO to remove the mapping relationship
between the secondary operator and the RAN sharing operator group.
iii. (Optional) Use the CnOperator MO to remove the operator information.
l Changing the sharing mode of an eNodeB from the hybrid RAN sharing mode to the
independent operator mode
a. Remove all information related to RAN sharing operator groups. Retain all the
configurations about independent operators and remove the configurations of other
operators. For detailed operations, see steps 1 through 7 in "Removing a RAN
sharing operator group from hybrid RAN sharing operator groups."
b. 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
c. (Optional) Use the ENodeBAlgoSwitch.RanSharingAnrSwitch parameter to turn
off the ANR switch in the adjacent cells that have neighbor relationships with the
local cell.

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;
ADD X2: X2Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=3,
//Configuring transmission links (in link mode)
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0,
CnOpSharingGroupId=0;

eRAN
ADD X2INTERFACE: X2InterfaceId=0, X2CpBearerId=0, CnOperatorId=0,
//Adding cells
ADD CELL: LocalCellId=0, CellName="LTE", CellId=0, PhyCellId=0,
FddTddInd=CELL_FDD, 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, CnOpSharingGroupId=1;
RST APP: AID=1;

other operators
//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;
the same MMEC
//Configuring the eNodeB-specific ANR switch under RAN sharing
MOD ENODEBALGOSWITCH: RANSHARINGANRSWITCH=NBSLTERANSharingSwitch-1;
//Configuring the inter-PLMN handover information
//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;



eRAN
ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="02",



ADD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=10800, Mcc="460", Mnc="02",


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)


Prerequisites
1. Based on the network plan, the eNodeB is shared between three operators that use hybrid
RAN sharing. Operators (A and B) and operator C are in different RAN sharing operator
groups.
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).

eRAN
Procedure
Expected result:
--------------------------start--------------------------
RETCODE = 0
...
Local cell ID = 0
...
RETCODE = 0
...
Local cell ID = 1
...
--------------------------end---------------------------

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)

eRAN
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)
Step 3 Power on UE 1 and UE 2 to initiate attach procedures towards the shared cell.
Expected result:
the UEs have successfully accessed the shared cell and selected the correct EPCs. In this
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.
l 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.
l The value of "TAC" is a hexadecimal number in the traced message.
----End

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.

eRAN
RAN Sharing Feature Parameter Description 8 RAN Sharing by More Operators
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
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.

eRAN
FDD LOFD-001086 RAN Sharing LT1S00RSMO0 per cell

by More 0
Operators
8.3.2 Software
feature documents.
Name Switch
FDD RAN sharing ENodeBSharin RAN Sharing RAN sharing

with common gMode.ENode by more
carrier BSharingMode operators
requires that
FDD RAN sharing ENodeBSharin RAN Sharing one of these
with dedicated gMode.ENode functions be
carrier BSharingMode enabled.
FDD Hybrid RAN ENodeBSharin RAN Sharing
sharing gMode.ENode
BSharingMode

None
8.3.3 Hardware
Base Station Models


l BTS3912E
l BTS3911E
l BTS3203E
l BTS3202E

eRAN
Boards
No requirements
RF Modules
No requirements
8.3.4 Others
None

For details, see section "Data Preparation" of a specific function deployment scenario.
l RAN sharing with common carrier (FDD): See 4.4.1.1 Data Preparation.
l RAN sharing with dedicated carrier (FDD): See 5.4.1.1 Data Preparation.
l Hybrid RAN sharing (FDD): See 7.4.1.1 Data Preparation.

For details, see "Using MML Commands" of a specific function deployment scenario.
l RAN sharing with common carrier (FDD): See 4.4.1.2 Using MML Commands.
l RAN sharing with dedicated carrier (FDD): See 5.4.1.2 Using MML Commands.
l Hybrid RAN sharing (FDD): See 7.4.1.2 Using MML Commands.


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.
l RAN sharing with common carrier (FDD): See 4.4.2 Activation Verification.
l RAN sharing with dedicated carrier: See 5.4.2 Activation Verification.
l RAN sharing with special dedicated carrier (FDD): See 6.4.2 Activation Verification.
l Hybrid RAN sharing: See 7.4.2 Activation Verification.

For details, see section "Network Monitoring" of a specific function deployment scenario.

eRAN
l RAN sharing with common carrier in FDD: See 4.4.3 Network Monitoring.
l RAN sharing with dedicated carrier: See 5.4.3 Network Monitoring.
l RAN sharing with special dedicated carrier in FDD: See 6.4.3 Network Monitoring.
l Hybrid RAN sharing: See 7.4.3 Network Monitoring.

eRAN
RAN Sharing Feature Parameter Description 9 Fair User Sharing (FDD)
9 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.
NOTE
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. In the
following examples, the LicenseSharingPolicy.MaxUserNumRate parameter for both
operators is set to 50%, the number of RRC_CONNECTED UEs of operator A has exceeded
50% of the licensed number but that of operator B has not.
l Not shared
When the LicenseSharingPolicy.UserNumSharingRate parameter for both operators is
set to 0%, operator A cannot occupy the remaining capacity of operator B.
l Partly shared
set to 10%, operator A can occupy the remaining capacity of operator B. However,
operator A can occupy only 60% of the total licensed number of RRC_CONNECTED
UEs of the eNodeB at most.
l Completely shared

eRAN

set to 50%, operator A can occupy the remaining capacity of operator B. Operator A can
occupy the total licensed number of RRC_CONNECTED UEs of the eNodeB at most.
When unused resources of an operator are shared with other operators, if UEs served by the
former lack sufficient 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.
l 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.
l 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.
– UE priority for resource preemption: A UE can preempt resources of another UE
who has a higher priority.
l 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 is selected.
– The CellRacThd.AcUserNumber parameter is set to a value less than the number
of RRC_CONNECTED UEs supported by the eNodeB.

eRAN
– The number of RRC_CONNECTED UEs in the cell has already reached or

exceeded the CellRacThd.AcUserNumber parameter value.
l When the NbUeNumPreemptSwitch option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, an NB-IoT UE can
preempt the resource from another NB-IoT UE based on the number of
RRC_CONNECTED UEs.
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.
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 LT1S00FUSH00 Per Cell

Sharing

eRAN
9.3.2 Software
feature documents.
Function Name Function Reference Description
Switch
RAN sharing with ENodeBSharin RAN Sharing Fair user sharing requires
common carrier gMode.ENode that one of these features be
BSharingMode enabled.
RAN sharing with ENodeBSharin RAN Sharing

dedicated carrier gMode.ENode
BSharingMode
Hybrid RAN sharing ENodeBSharin RAN Sharing

gMode.ENode
BSharingMode

RAT Function Name Function Switch Reference
FDD Out-of-band relay OutOfBandRelaySwitch Relay

option of the
CellAlgoSwitch.RelaySw
itch parameter
FDD In-band relay InBandRelayDeNbS- Relay

witch or
InBandRelayReNbS-
witch option of the
CellAlgoSwitch.RelaySw
itch parameter
9.3.3 Hardware
Base Station Models

The following base stations are compatible with this function:

l BTS3912E

eRAN
l BTS3911E
l BTS3203E
l BTS3202E
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.
l RAN sharing with common carrier: See 4.4.1.1 Data Preparation.

l RAN sharing with dedicated carrier: See 5.4.1.1 Data Preparation.
l RAN sharing with special dedicated carrier: See 6.4.1.1 Data Preparation.
l 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.

Name
CN Operator ID LicenseSharingPoli- N/A Set this parameter to the

cy.CnOperatorId same value as the CN
Operator ID parameter
in the CnOperator MO.
The proportion LicenseSharingPoli- N/A None

of the maximum cy.MaxUserNumRat
number of users e

eRAN

Name
The proportion LicenseSharingPoli- N/A None

of the sharing cy.UserNumSharing
number of users Rate
User Number LicenseSharingPoli- N/A None

Sharing Group cy.UserNumSharing
ID GroupId
UE number ENodeBAlgoSwitch. InterOpUeNumPree Select this option.

preemption UeNumPreemptSwit mptSwitch
switch ch

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 MML configurations specific to fair user sharing. For MML commands
required by a prerequisite function, see section "Using MML Commands" of a specific
function deployment scenario.
l RAN sharing with common carrier: See 4.4.1.2 Using MML Commands.
l RAN sharing with dedicated carrier: See 5.4.1.2 Using MML Commands.
l RAN sharing with special dedicated carrier: See 6.4.1.2 Using MML Commands.
l Hybrid RAN sharing: See 7.4.1.2 Using MML Commands.
The following are MML commands specific to fair user sharing.

other operators
//Configuring whether to allow inter-operator RRC_CONNECTED UE resource preemption
MOD ENODEBALGOSWITCH: UeNumPreemptSwitch=InterOpUeNumPreemptSwitch-1;


The prerequisites for activation verification are as follows:

eRAN
l One of the prerequisite functions for fair user sharing has been activated.
l 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.
l 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.
l RAN sharing with common carrier: See 4.4.2 Activation Verification.
l RAN sharing with special dedicated carrier: See 6.4.2 Activation Verification.

None

eRAN
RAN Sharing Feature Parameter Description 10 MOCN Cell Reselection Priority Configuration
10 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 system 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 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
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 they are the same, the eNodeB includes the frequency or
frequency band in the information. Otherwise, the eNodeB does not do so.
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:
l Serving frequency
l Neighboring E-UTRA frequency

eRAN
l Neighboring UTRA frequency

The priorities required for operator B, in this example, are the reverse:
l Neighboring UTRA frequency
l Neighboring E-UTRA frequency
l Serving frequency
In this scenario, the priorities can be configured as follows:
Operator A:
l CELLRESEL.CellReselPriority = 4
l EutranNFreqSCellOp.CellReselDediPri = 3
l UtranNFreqSCellOp.CellReselDediPri = 2
Operator B:
l CELLRESEL.CellReselPriority = 4
l EutranNFreqSCellOp.CellReselDediPri = 5
l UtranNFreqSCellOp.CellReselDediPri = 6
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.
10.2.2 Impacts
Network Impacts
None

eRAN
Function Impacts
Name Switch
FDD Coverage-based EmcInterFreq Mobility MOCN cell reselection

inter-frequency BlindHoSwitch Management in priority configuration is
emergency or Connected incompatible with RAN
blind handover UtranPsHoSwi Mode sharing information in
tch option of coverage-based inter-
the frequency emergency
CellHoParaCf blind handovers. These
g.CellHoAlgoS two functions cannot be
witch parameter both enabled.
FDD Coverage-based UtranRedirect Mobility MOCN cell reselection

inter-RAT Switch option Management in priority configuration is
handover to of the Connected incompatible with RAN
UTRAN CellHoParaCf Mode sharing information in
g.HoModeSwit coverage-based inter-
ch parameter RAT handovers to
UTRAN. These two
functions cannot be both
enabled.
FDD Coverage-based GeranPsHoSw Mobility MOCN cell reselection

inter-RAT itch option of Management in priority configuration is
handover to the Connected incompatible with RAN
GERAN ENodeBAlgoS Mode sharing information in
witch.HoMode coverage-based inter-
Switch RAT handovers to
parameter or GERAN. These two
GeranRedirect functions cannot be both
Switch of the enabled.
CellHoParaCf
g.HoModeSwit
ch parameter
10.3 Requirements
10.3.1 Licenses
FDD LOFD-001112 MOCN Flexible LT1S0MFPBC0 per cell

Priority Based 0
Camping

eRAN
10.3.2 Software
feature documents.
Name Switch
FDD RAN sharing ENodeBSharin RAN Sharing MOCN cell

with common gMode.ENode reselection priority
carrier BSharingMode configuration
requires that one of
FDD RAN sharing ENodeBSharin RAN Sharing these functions be
with dedicated gMode.ENode enabled.
carrier BSharingMode

sharing gMode.ENode
BSharingMode

None
10.3.3 Hardware
Base Station Models
l BTS3912E
l BTS3911E
l BTS3203E
l BTS3202E
Boards
No requirements
RF Modules
No requirements
10.3.4 Others
None

eRAN

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 HPLMN have been
configured. If so, delete these settings.
The following tables describe the parameters specific to MOCN cell reselection priority
configuration.
reselection priority for a GERAN frequency based on the serving cell's PLMN.

Name

pSCellOp.Loca
lCellId

ID pSCellOp.Bcch
GroupId
Cn operator ID GeranNFGrou Set this parameter to the same value as the CN

pSCellOp.CnO Operator ID parameter in the CnOperator MO.
peratorID

configure gInd
indicator


eRAN

Name
Local cell ID CellReselGera Set this parameter to the same value as the Local Cell
n.LocalCellId ID parameter in the Cell MO.
Cell reselection CellReselGera None

timer value for n.TReselGeran
GERAN
reselection priority for a UTRAN frequency based on the serving cell's PLMN.

Name
Local cell ID UtranNFreqS None

CellOp.LocalC
ellId
Downlink UtranNFreqS None

UARFCN CellOp.UtranD
lArfcn
Cn operator ID UtranNFreqS Set this parameter to the same value as the CN

CellOp.CnOpe Operator ID parameter in the CnOperator MO.
ratorID

configure d
indicator

priority elDediPri
Local cell ID CellReselUtra Set this parameter to the same value as the Local Cell
n.LocalCellId ID parameter in the Cell MO.
Cell reselection CellReselUtra None

timer value for n.TReselUtran
UTRAN
reselection priority for an E-UTRAN frequency based on the serving cell's PLMN.

eRAN

Name
Local cell ID EutranNFreqS None

CellOp.LocalC
ellId
Downlink EutranNFreqS None

EARFCN CellOp.DlEarf
cn
Cn operator ID EutranNFreqS Set this parameter to the same value as the CN

ratorID

configure d
indicator

priority elDediPri
Local cell ID CellResel.Loca Set this parameter to the same value as the Local Cell
lCellId ID parameter in the Cell MO.
Cell reselection CellResel.TRes None

timer value for elEutran
EUTRAN
reselection priority for a CDMA frequency based on the serving cell's PLMN.

Name
Local cell ID Cdma2000BcS None

CellOp.LocalC
ellId
Band class Cdma2000BcS None

CellOp.BandCl
ass
Cn operator ID Cdma2000BcS Set this parameter to the same value as the CN

ratorID

eRAN

Name

1xRTT CellOp.Cdma1
dedicated XrttCellReselPr
priority iInd
configure
indicator

1xRTT Cell CellOp.Cdma1
Reselection XrttCellReselD
Dedicated ediPri
Priority

HRPD CellOp.HrpdC
dedicated ellReselDediPri
priority CfgInd
configure
indicator

HRPD Cell CellOp.HrpdC
Reselection ellReselDediPri
Dedicated
Priority
Local cell ID CellReselCdm Set this parameter to the same value as the Local Cell
a2000.LocalCel ID parameter in the Cell MO.
lId
Cell reselection CellReselCdm None

timer for HRPD a2000.Treselect
ionHrpd
Cell reselection CellReselCdm None

timer for a2000.Cdma1X
1XRTT rttTreselection

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 MML configurations specific to MOCN cell reselection priority configuration.
For MML commands required by a prerequisite function, see section "Using MML
Commands" of a specific function deployment scenario.
The following are MML commands specific to MOCN cell reselection priority configuration.

eRAN
Configuring GERAN cell information

//Configuring a dedicated cell-reselection priority for a GERAN frequency
//(Optional) Setting parameters for cell reselection to GERAN
ADD CELLRESELGERAN: LocalCellId=0, TReselGeran=1;
Configuring UTRAN cell information

//Configuring a dedicated cell-reselection priority for a UTRAN frequency
//(Optional) Setting parameters for cell reselection to UTRAN
ADD CELLRESELUTRAN: LocalCellId=0, TReselUtran=1;
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;
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, Cdma1XrttParaCfgInd=CFG,
Cdma1XrttCellReselCfgInd=CFG, Cdma1XrttTreselection=2;


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 function deployment scenario.
l RAN sharing with common carrier (FDD): See 4.4.2 Activation Verification.

eRAN


None

eRAN
RAN Sharing Feature Parameter Description 11 Multi-Operator SPID Policy
11 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.

eRAN
11.2.2 Impacts
Network Impacts
None
Function Impacts
Name Switch
FDD SPID-based None Flexible User If both the multi-

camping and Steering operator SPID
handover policy and SPID-
based camping &
handover are
enabled, the former
takes precedence.
11.3 Requirements
11.3.1 Licenses
activated the licenses for the features listed in the following table.
FDD LOFD-001054 Flexible User LT1S00FXUS0 per RRC Connected

Steering 0 User
FDD LOFD-070210 Multi Operators LT1SMOSPID0 per cell

SPID Policy 0
11.3.2 Software
feature documents.

eRAN
Name Switch
FDD RAN sharing ENodeBSharin RAN Sharing Multi-operator SPID

with common gMode.ENode policy requires that
carrier BSharingMode one of these
functions be
FDD RAN sharing ENodeBSharin RAN Sharing enabled.
with dedicated gMode.ENode
carrier BSharingMode

sharing gMode.ENode
BSharingMode
FDD Flexible user None Flexible User None

steering Steering

Name Switch
FDD WBB UE None WBB Multi-operator SPID

identification policy allows
and different operators to
differentiated use the same SPIDs.
QoS guarantee WBB UE
identification and
differentiated QoS
guarantee identifies
WBB UEs by using
SPIDs. If both
functions are
enabled, the eNodeB
cannot identify
WBB UEs based on
SPIDs.
11.3.3 Hardware
Base Station Models



eRAN
l BTS3912E
l BTS3911E
l BTS3203E
l BTS3202E
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.
l 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.CnOp Set this parameter to the same

eratorId value as the CN Operator ID
parameter in the CnOperator
MO.

eRAN
Spid CnOperatorSpidCfg.Spid Set this parameter to the

registered SPID of a UE.
RAT frequency priority CnOperatorSpidCfg.RatFr Set this parameter to CFG.

indication eqPriorityInd
RAT frequency priority CnOperatorSpidCfg.RatFr This parameter specifies the ID

group ID eqPriorityGroupId of a RAT/frequency priority
group. Set this parameter to the
same value as the RAT
frequency priority group ID
parameter in the
RatFreqPriorityGroup MO.
RAT frequency priority RatFreqPriorityGroup.Rat This parameter specifies the ID

group ID FreqPriorityGroupId of a RAT/frequency priority
group.
RAT Type RatFreqPriorityGroup.Rat Set this parameter to the RAT to

Type which the frequency belongs.
DL Earfcn or Bandclass RatFreqPriorityGroup.DlE None

arfcn
Priority RatFreqPriorityGroup.Prio None

rity
GERAN Frequency RatFreqPriorityGroup.Ban None

Indicator dIndicator

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.

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 MML configurations specific to multi-operator SPID
policy. For MML commands required by a prerequisite function, see section "Using MML
Commands" of a specific function deployment scenario.
l RAN sharing with special dedicated carrier (FDD): See 6.4.1.2 Using MML
Commands.

eRAN
The following are MML commands specific to multi-operator SPID policy.

//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;

Prerequisites
l RAN sharing with common carrier, RAN sharing with dedicated carrier, or hybrid RAN
sharing is enabled on the eNodeB.
l The SPID is configured based on the UE's serving PLMN, and a RAT/frequency priority
group is configured.
l 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
Step 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
Step 2 Stop all services running on the UE.

eRAN
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
Step 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.
----End

None

eRAN
RAN Sharing Feature Parameter Description 12 Parameters
12 Parameters
Table 12-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
License UserNu ADD TDLBF License Meaning: Indicates the ID of the sharing group of UEs
Sharing mSharin LICENS D-00401 Manage in RRC_CONNECTED mode. Operators with the
Policy gGroupI ESHAR 4 ment same UserNumSharingGroupId parameter value share
d INGPO LOFD-0 RAN the sum of the proportions of UEs in
LICY 01036/ Sharing RRC_CONNECTED mode of each operator and the
MOD TDLOF with sum of the penetration rates of UEs in
LICENS D-00103 Commo RRC_CONNECTED mode of each operator. The
ESHAR 6 n value 255 is an invalid ID, indicating that the operator
INGPO Carrier is not configured with a sharing group of UEs in
LOFD-0 RRC_CONNETED mode. This parameter applies
LICY 01037/ RAN only to LTE FDD and LTE TDD.
LST TDLOF Sharing
LICENS D-00103 with GUI Value Range: 1~6,255
ESHAR 7 Dedicate Unit: None
INGPO LOFD-0 d Actual Value Range: 1~6,255
LICY 70206 Carrier
Default Value: 255
Hybrid
RAN
Sharing

eRAN

nd
CellAlg OpReso MOD LOFD-0 RAN Meaning: Indicates whether to enable RAN sharing so
oSwitch urceGro CELLA 01036/ Sharing that admission and scheduling take effect in RAN
upShare LGOSW TDLOF with sharing mode. When the switch is on, operators share
Switch ITCH D-00103 Commo the resources specified by the RAN-sharing operator
LST 6 n group. When the OpPrbGroupshareSwitch option is
CELLA LOFD-0 Carrier selected, PRB resources can be shared by operator
LGOSW 70206/ Hybrid groups. This parameter applies only to LTE FDD and
ITCH TDLOF RAN LTE TDD.
D-08122 Sharing GUI Value Range: OpPrbGroupshareS-
4 witch(OpPrbGroupshareSwitch)
Unit: None
Actual Value Range: OpPrbGroupshareSwitch
Default Value: OpPrbGroupshareSwitch:Off
CellOp OpReso ADD LOFD-0 RAN Meaning: Indicates the index of the resource group to
urceGro CELLO 01036 Sharing which the operator belongs. The default value is 255,
upIndex P LOFD-0 with which indicates an invalid value. The
MOD 70206 Commo OpPrbGroupshareSwitch option takes effect only
CELLO n when operator sharing is set to a valid value.
P Carrier GUI Value Range: 0~5,255
LST Hybrid Unit: None
CELLO RAN
Sharing Actual Value Range: 0~5,255
P
Default Value: 255

eRAN

nd
CellAcc Broadca MOD LOFD-0 RAN Meaning: Indicates the public land mobile network
ess stMode CELLA 01036/ Sharing (PLMN) broadcast mode of the cell. If RAN sharing
CCESS TDLOF with with common carrier or hybrid RAN sharing is
LST D-00103 Commo enabled in certain cells on the live network and the
CELLA 6 n PLMN IDs are broadcast in rotation mode in least one
CCESS MLOFD Carrier of these cells, NBSLTEPLMNRoundSwitch under the
-121251 NB-IoT RanSharingAnrSwitch parameter must be selected for
RAN eNodeBs whose cells may be configured as
MLOFD neighboring cells for the local cell. Otherwise, the
-131253 Sharing
with local eNodeB may experience failures in handing over
MLBFD Commo UEs from the local cell to an ANR-established
-120002 n neighboring cell in which the PLMN IDs are
29 Carrier broadcast in rotation mode. If this parameter is set to
LOFD-0 NORMAL_MODE(Normal Mode), PLMN IDs are
NB-IoT broadcast in a fixed sequence in the cell. If this
70206/ Hybrid
TDLOF parameter is set to RR_MODE(Round Robin Mode),
RAN the PLMN ID at the top of the PLMN ID list is rotated
D-08122 Sharing
4 in RR mode at a cell-specific interval. If this
Broadca parameter is set to FREE_MODE(Free Mode), the
st of PLMN ID at the top of the PLMN ID list is rotated at
system an operator-specific interval. This parameter applies
informat only to LTE FDD and LTE TDD.
ion GUI Value Range: NORMAL_MODE(Normal
Hybrid Mode), RR_MODE(Round Robin Mode),
RAN FREE_MODE(Free Mode)
Sharing Unit: None
Actual Value Range: NORMAL_MODE, RR_MODE,
FREE_MODE
Default Value: NORMAL_MODE(Normal Mode)

eRAN

nd
ENodeB ENodeB MOD LOFD-0 RAN Meaning: Indicates the eNodeB sharing mode, which
Sharing Sharing ENODE 01036/ Sharing can be independent operator mode, RAN sharing with
Mode Mode BSHAR TDLOF with common carrier, RAN sharing with dedicated carrier,
INGMO D-00103 Commo hybrid RAN sharing, or RAN sharing with special
DE 6 n dedicated carrier.
LST MLOFD Carrier GUI Value Range: INDEPENDENT(Independent
ENODE -121251 NB-IoT Operator Mode), SHARED_FREQ(Shared Frequency
BSHAR LOFD-0 RAN Sharing Mode), SEPARATED_FREQ(Separate
INGMO 01037/ Sharing Frequency Sharing Mode),
DE TDLOF with HYBRID_SHARED(Hybrid RAN Sharing),
D-00103 Commo SEPARATED_FREQ_SPEC(Special Separate
7 n Frequency Sharing Mode)
Carrier Unit: None
MLOFD
-121252 RAN Actual Value Range: INDEPENDENT,
Sharing SHARED_FREQ, SEPARATED_FREQ,
MLOFD with
-131253 HYBRID_SHARED, SEPARATED_FREQ_SPEC
Dedicate
LOFD-0 d Default Value: INDEPENDENT(Independent
70206/ Carrier Operator Mode)
TDLOF NB-IoT
D-08122 RAN
4 Sharing
with
Dedicate
d
Carrier
NB-IoT
Hybrid
RAN
Sharing
Hybrid
RAN
Sharing

eRAN

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the type of the operator. The
ator atorType CNOPE 01036/ Sharing operator can be the primary operator or a secondary
RATOR TDLOF with operator. For each eNodeB, only one primary operator
MOD D-00103 Commo but more than one secondary operator can be
CNOPE 6 n configured.
RATOR MLOFD Carrier GUI Value Range:
LST -121251 NB-IoT CNOPERATOR_PRIMARY(Primary Operator),
CNOPE LOFD-0 RAN CNOPERATOR_SECONDARY(Secondary Operator)
RATOR 01037/ Sharing Unit: None
TDLOF with
Commo Actual Value Range: CNOPERATOR_PRIMARY,
D-00103 CNOPERATOR_SECONDARY
7 n
Carrier Default Value: None
MLOFD
-121252 RAN
Sharing
MLOFD with
-131253 Dedicate
LOFD-0 d
01086/ Carrier
TDLOF NB-IoT
D-00108 RAN
6 Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4 NB-IoT
Hybrid
RAN
Sharing
RAN
Sharing
by More
Operator
s
Hybrid
RAN
Sharing

eRAN

nd
CellAcc CellBarr MOD LBFD-0 Cell Meaning: Indicates whether the cell is barred. If the
ess ed CELLA 02013/ Outage cell is barred, the UE cannot camp on the serving cell.
CCESS TDLBF Detectio During cell reselection, the serving cell is not selected
LST D-00203 n and as a candidate cell.
CELLA 7 Compen GUI Value Range: CELL_BARRED(Barred),
CCESS LBFD-0 sation CELL_NOT_BARRED(Not Barred)
02009/ Broadca Unit: None
TDLBF st of
D-00200 system Actual Value Range: CELL_BARRED,
9/ informat CELL_NOT_BARRED
MLBFD ion Default Value: CELL_NOT_BARRED(Not Barred)
-120002 RAN
29 Sharing
LOFD-0 with
01036/ Commo
TDLOF n
D-00103 Carrier
6
CellOp CellRes ADD LBFD-0 Broadca Meaning:

ervedFo CELLO 02009/ st of Indicates whether the cell is reserved for operator use.
rOp P TDLBF system
MOD D-00200 informat If this parameter is set to
CELLO 9/ ion CELL_RESERVED_FOR_OP, the cell is reserved for
P MLBFD RAN operator use. UEs of AC11 or AC15 in their HPLMN
-120002 Sharing or EHPLMN can consider this cell as a candidate cell
LST 29 for cell selection or reselection. UEs of AC11 or
CELLO with
LOFD-0 Commo AC15 outside their HPLMN/EHPLMN and UEs of
P AC0-9/AC12-14 consider this cell as a barred cell
01036/ n
TDLOF Carrier during cell selection or reselection.
D-00103 If this parameter is set to
6 CELL_NOT_RESERVED_FOR_OP, the cell is not
reserved for operator use. All UEs can consider this
cell as a candidate cell for cell selection or reselection.
This parameter applies to LTE FDD, LTE TDD, and
NB-IoT.
GUI Value Range:
CELL_RESERVED_FOR_OP(Reserved),
CELL_NOT_RESERVED_FOR_OP(Not Reserved)
Unit: None
Actual Value Range: CELL_RESERVED_FOR_OP,
CELL_NOT_RESERVED_FOR_OP
Default Value:
CELL_NOT_RESERVED_FOR_OP(Not Reserved)

eRAN

nd
CnOper Tac ADD LOFD-0 RAN Meaning: Indicates the tracking area code (TAC),
atorTa CNOPE 01036/ Sharing which is used by the EPC to determine the area within
RATOR TDLOF with which paging messages are sent. One tracking area is
TA D-00103 Commo comprised of one or more cells.
MOD 6 n GUI Value Range: 1~65533,65535
CNOPE MLOFD Carrier
Unit: None
RATOR -121251 NB-IoT
TA RAN Actual Value Range: 1~65533,65535
LOFD-0
LST 01037/ Sharing Default Value: None
CNOPE TDLOF with
RATOR D-00103 Commo
TA 7 n
Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4
NB-IoT
MLOFD RAN
-131253 Sharing
with
Dedicate
d
Carrier
Hybrid
RAN
Sharing
NB-IoT
Hybrid
RAN
Sharing

eRAN

nd
CnOper Trackin ADD LOFD-0 RAN Meaning: Indicates the tracking area ID, which
atorTa gAreaId CNOPE 01036/ Sharing uniquely identifies an entry of tracking area
RATOR TDLOF with information. This parameter is used only within the
TA D-00103 Commo eNodeB and is not used during the information
LST 6 n exchange with the EPC. This is different from the TAI
CNOPE MLOFD Carrier configured in the EPC TAL.
RATOR -121251 NB-IoT GUI Value Range: 0~65535
TA LOFD-0 RAN Unit: None
MOD 01037/ Sharing
with Actual Value Range: 0~65535
CNOPE TDLOF
RATOR D-00103 Commo Default Value: None
TA 7 n
Carrier
RMV MLOFD
CNOPE -121252 RAN
RATOR Sharing
LOFD-0 with
TA 70206/ Dedicate
TDLOF d
D-08122 Carrier
4
NB-IoT
MLBFD RAN
-120002 Sharing
29 with
MLBFD Dedicate
-120002 d
37 Carrier
MLOFD Hybrid
-131253 RAN
Sharing
Broadca
st of
system
informat
ion
Cell
Selectio
n and
Re-
selection
NB-IoT
Hybrid
RAN
Sharing

eRAN

nd
CellOp Trackin ADD LBFD-0 Broadca Meaning:

gAreaId CELLO 02009/ st of Indicates the local tracking area identity of the cell,
P TDLBF system which uniquely identifies an operator's record of
LST D-00200 informat tracking area information within a cell. This parameter
CELLO 9 ion is used only in the eNodeB and is different from the
P LBFD-0 Cell tracking area identity configured in the tracking area
MOD 0201803 Selectio list on the MME.
CELLO / n and
TDLBF Re- This parameter applies to LTE FDD, LTE TDD, and
P NB-IoT. According to NB-IoT specifications, the
D-00201 selection
RMV 803 TAIs planned for NB-IoT must be different from the
CELLO TAIs planned for LTE.
P GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: None
CellAcc RoundP MOD LOFD-0 RAN Meaning: Indicates the changing period of cell
ess eriod CELLA 01036/ Sharing PLMN.
CCESS TDLOF with GUI Value Range: 1~720
LST D-00103 Commo
6 n Unit: h
CELLA
CCESS MLOFD Carrier Actual Value Range: 1~720
-121251 NB-IoT Default Value: 1
MLOFD RAN
-131253 Sharing
with
MLBFD Commo
-120002 n
29 Carrier
LOFD-0 NB-IoT
70206/ Hybrid
TDLOF RAN
D-08122 Sharing
4
Broadca
st of
system
informat
ion
Hybrid
RAN
Sharing

eRAN

nd
CellAcc RoundA MOD LOFD-0 RAN Meaning: Indicates the start time for broadcasting
ess ctionTi CELLA 01036/ Sharing PLMN-specific information in round robin mode.
me CCESS TDLOF with GUI Value Range:
LST D-00103 Commo 2000-01-01T00:00:00+00:00~2099-12-31T23:59:59+
CELLA 6 n 00:00
CCESS MLOFD Carrier
Unit: None
-121251 NB-IoT
RAN Actual Value Range:
MLOFD 2000-01-01T00:00:00+00:00~2099-12-31T23:59:59+
-131253 Sharing
with 00:00
LOFD-0 Commo Default Value: 2000-01-01T00:00:00+00:00
70206/ n
TDLOF Carrier
D-08122
4 NB-IoT
Hybrid
RAN
Sharing
Hybrid
RAN
Sharing
CellOp Operator ADD LOFD-0 RAN Meaning: Indicates the operator-level PLMN
PlmnRo CELLO 01036/ Sharing broadcast round-robin period.
undPeri P TDLOF with GUI Value Range: 1~720
od MOD D-00103 Commo
6 n Unit: h
CELLO
P MLOFD Carrier Actual Value Range: 1~720
LST -121251 NB-IoT Default Value: 1

CELLO MLBFD RAN
P -120002 Sharing
29 with
Commo
LOFD-0 n
70206/ Carrier
TDLOF
D-08122 Broadca
4 st of
system
MLOFD informat
-131253 ion
Hybrid
RAN
Sharing
NB-IoT
Hybrid
RAN
Sharing

eRAN

nd
GlobalP DiffOp MOD LBFD-0 S1-flex Meaning: Indicates whether MMEs of operators that
rocSwitc WithSa GLOBA 01018/ RAN share the eNodeB can be configured with the same
h meMme LPROC TDLBF Sharing mobility management entity code (MMEC). If this
cSwitch SWITC D-00101 with parameter is set to OFF(Off), MMEs of operators that
H 8 Commo share the eNodeB cannot be configured with the same
LST LOFD-0 n MMEC. If this parameter is set to ON(On), MMEs of
GLOBA 01036/ Carrier operators that share the eNodeB can be configured
LPROC TDLOF with the same MMEC.
Hybrid
SWITC D-00103 RAN GUI Value Range: OFF(Off), ON(On)
H 6 Sharing Unit: None
LOFD-0 Actual Value Range: OFF, ON
70206/
TDLOF Default Value: OFF(Off)
D-08122
4
RatFreq RatFreq ADD LOFD-0 Camp & Meaning: Indicates the ID of the RAT/frequency
Priority Priority RATFR 0105401 Handov priority group. This parameter applies only to LTE
Group GroupId EQPRI / er Based FDD and LTE TDD.
ORITY TDLOF on SPID GUI Value Range: 0~255
GROUP D-00105
401 Unit: None
LST
RATFR Actual Value Range: 0~255
EQPRI Default Value: None
ORITY
GROUP
MOD
RATFR
EQPRI
ORITY
GROUP
RMV
RATFR
EQPRI
ORITY
GROUP

eRAN

nd
SpidCfg Spid ADD LOFD-0 Camp & Meaning: Indicates the subscriber profile ID (SPID).
SPIDCF 0105401 Handov According to 3GPP specifications, the SPID can be
G / er Based from 1 to 256. When this parameter is set to 0, the
LST TDLOF on SPID eNodeB does not obtain the SPID from the MME or
SPIDCF D-00105 UL Pre- the eNodeB is not configured with an SPID for UEs.
G 401 allocatio This parameter applies only to LTE FDD and LTE
LOFD-0 n Based TDD.
MOD
SPIDCF 01059/ on SPID GUI Value Range: 0~256
G TDLOF Unit: None
D-00105
RMV 9 Actual Value Range: 0~256
SPIDCF Default Value: None
G
SpidCfg RatFreq ADD LOFD-0 Camp & Meaning: Indicates the ID of the intra-RAT frequency
Priority SPIDCF 0105401 Handov priority group. This parameter applies only to LTE
GroupId G / er Based FDD and LTE TDD.
MOD TDLOF on SPID GUI Value Range: 0~255
SPIDCF D-00105 RAN
401 Unit: None
G Sharing
LOFD-0 with Actual Value Range: 0~255
LST
SPIDCF 01036/ Commo Default Value: 0
G TDLOF n
D-00103 Carrier
6

eRAN

nd
ENodeB HoAlgo MOD LBFD-0 Coverag Meaning:

AlgoSwi Switch ENODE 0201801 e Based Indicates whether to enable handover algorithms. This
tch BALGO / Intra- parameter includes the following options:
SWITC TDLBF frequenc
H D-00201 y IntraFreqCoverHoSwitch: If this option is selected,
801 Handov the coverage-based intra-frequency handover
LST
er algorithm is enabled to ensure service continuity. If
ENODE LBFD-0
Coverag this option is deselected, the coverage-based intra-
BALGO 0201802
e Based frequency handover algorithm is disabled.
SWITC /
H TDLBF Inter- InterFreqCoverHoSwitch: If this option is selected,
D-00201 frequenc the coverage-based inter-frequency handover
802 y algorithm is enabled to ensure service continuity. If
Handov this option is deselected, the coverage-based inter-
LBFD-0
er frequency handover algorithm is disabled.
0201804
/ Distance
Cdma1xRttCsfbSwitch: If this option is selected,
TDLBF Based
CSFB to CDMA2000 1xRTT is enabled, and UEs can
D-00201 Inter-
fall back to CDMA2000 1xRTT. If this option is
804 frequenc
deselected, CSFB to CDMA2000 1xRTT is disabled.
y
LBFD-0
Handov UtranServiceHoSwitch: If this option is selected, the
0201805
er service-based UTRAN handover algorithm is enabled,
/
Service and UEs running a specific type of services can be
TDLBF
Based handed over to UTRAN. If this option is deselected,
D-00201
Inter- the service-based UTRAN handover algorithm is
805
frequenc disabled.
LOFD-0 y
01033/ GeranServiceHoSwitch: If this option is selected, the
Handov service-based GERAN handover algorithm is enabled,
TDLOF er
D-00103 and UEs running a specific type of services can be
3 CS handed over to GERAN. If this option is deselected,
Fallback the service-based GERAN handover algorithm is
LOFD-0 to disabled.
01034/ UTRAN
TDLOF UlQualityInterRATHoSwitch: If this option is
CS selected, the UL-quality-based inter-RAT handover
D-00103
Fallback algorithm is enabled, and UEs can be handed over to
4
to inter-RAT cells to ensure service continuity when UL
LOFD-0 GERAN signal quality is poor. If this option is deselected, the
01035/
CS UL-quality-based inter-RAT handover algorithm is
TDLOF
Fallback disabled.
D-00103
to
5 InterPlmnHoSwitch: If this option is selected, the
CDMA2
LOFD-0 000 inter-PLMN handover algorithm is enabled, and UEs
01052/ 1xRTT can be handed over to cells in other PLMNs. If this
TDLOF option is deselected, the inter-PLMN handover
Flash
D-00105 algorithm is disabled.
CS
2 Fallback ServiceBasedInterFreqHoSwitch: If this option is
LOFD-0 to selected, the service-based inter-frequency handover
01053/ UTRAN algorithm is enabled, and UEs running a specific type

eRAN

nd
TDLOF Flash of services can be handed over to inter-frequency E-

D-00105 CS UTRAN cells. If this option is deselected, the service-
3 Fallback based inter-frequency handover algorithm is disabled.
LOFD-0 to
GERAN UlQualityInterFreqHoSwitch: If this option is
01088/ selected, the UL-quality-based inter-frequency
TDLOF CS handover algorithm is enabled, and UEs can be
D-00108 Fallback handed over to inter-frequency E-UTRAN cells to
8 Steering ensure service continuity when UL signal quality is
LOFD-0 to poor. If this option is deselected, the UL-quality-based
01089/ UTRAN inter-frequency handover algorithm is disabled.
TDLOF CS
D-00108 Fallback CSFBLoadInfoSwitch: If this option is selected, the
9 Steering load-based CSFB algorithm is enabled, and a target
to cell for CSFB is selected based on loads of candidate
LOFD-0 target cells. If this option is deselected, the load-based
GERAN
01090/ CSFB algorithm is disabled. This option applies only
TDLOF Enhance
to LTE FDD and LTE TDD.
D-00109 d CS
0 Fallback Cdma1XrttEcsfbSwitch: If this option is selected,
to eCSFB to CDMA2000 1xRTT is enabled and UEs can
LOFD-0
CDMA2 fall back to CDMA2000 1xRTT through handovers. If
01019/
000 this option is deselected, eCSFB to CDMA2000
TDLOF
1xRTT 1xRTT is disabled. This option applies only to LTE
D-00101
9 PS Inter- FDD and LTE TDD.
RAT
LOFD-0 EmcBlindHoA1Switch: If this option is selected, blind
Mobility
01020/ handover event A1 measurements are enabled. In this
between
TDLOF case, if a blind handover event measurement conflicts
E-
D-00102 with a handover procedure, an emergency blind
UTRAN
0 handover can be triggered after the handover
and
LOFD-0 procedure is complete. If this option is deselected,
UTRAN
01043/ blind handover event A1 measurements are disabled.
PS Inter- In this case, if a blind handover event measurement
TDLOF
RAT conflicts with a handover procedure, an emergency
D-00104
Mobility blind handover cannot be triggered. This option
3
between applies only to LTE FDD and LTE TDD.
LOFD-0 E-
01046/ UTRAN EmcInterFreqBlindHoSwitch: If this option is
TDLOF and selected, the eNodeB preferentially performs an inter-
D-00104 GERAN frequency blind handover when an emergency blind
6 Service handover is triggered. If this option is deselected, the
LOFD-0 based eNodeB only performs an inter-RAT blind handover
01072/ Inter- when an emergency blind handover is triggered. This
TDLOF RAT option applies only to LTE FDD and LTE TDD.
D-00107 handove EPlmnSwitch: Indicates whether handovers to
2 r to neighboring cells under the equivalent PLMNs
LOFD-0 UTRAN (EPLMNs) are allowed. When inter-PLMN handovers
01073/ Service are allowed, handovers to neighboring cells under the
TDLOF based EPLMNs are allowed if this option is selected, and not

eRAN

nd
D-00107 Inter- allowed if this option is deselected. The EPLMNs are

3 RAT delivered by the MME to the UE. This option applies
TDLBF handove only to LTE FDD and LTE TDD.
D-00201 r to
ServiceReqInterFreqHoSwitch: If this option is
8 GERAN
selected, the service-request-based inter-frequency
TDLOF Distance handover algorithm is enabled and UEs running a
D-00102 based specific type of services can be handed over to inter-
2 Inter- frequency E-UTRAN cells. If this option is
RAT deselected, the service-request-based inter-frequency
TDLOF handove
D-07022 handover algorithm is disabled. This option applies
r to only to LTE TDD.
8 UTRAN
LOFD-0 VoipHoControlSwitch: If this option is selected, the
Distance eNodeB filters out target cells that do not support
81283/
based VoLTE services when processing intra-RAT handovers
TDLOF
Inter- for VoLTE services. If this option is deselected, the
D-08120
RAT eNodeB does not filter out target cells that do not
3
handove support VoLTE services when processing intra-RAT
LOFD-0 r to handovers for VoLTE services. This option applies
70202/ GERAN only to LTE FDD and LTE TDD.
TDLOF
Mobility
D-08122 UtranUltraFlashCsfbSwitch: If this option is selected,
Manage
3 ultra-flash CSFB to UTRAN is enabled. If this option
ment
LOFD-0 is deselected, ultra-flash CSFB to UTRAN is disabled.
SRVCC This option applies only to LTE FDD and LTE TDD.
01021/
to
TDLOF GeranUltraFlashCsfbSwitch: If this option is selected,
UTRAN
D-00102 ultra-flash CSFB to GERAN is enabled. If this option
1 Service- is deselected, ultra-flash CSFB to GERAN is disabled.
LOFD-0 Request This option applies only to LTE FDD and LTE TDD.
01036/ Based
TDLOF Inter- RatLayerSwitch: If this option is selected, the eNodeB
D-00103 frequenc selects different target RATs for voice and data
6 y services during coverage-based inter-RAT handovers.
Handov If this option is deselected, the service-based RAT
LOFD-0 er steering function is controlled by the
01111 SrvccRatSteeringSwitch and PsRatSteeringSwitch
Ultra-
Flash options. This option applies only to LTE FDD and
CSFB to LTE TDD.
GERAN ServiceBasedMultiFreqHoSwitch: If this option is
Ultra- selected, the eNodeB selects the optimum frequency
Flash from multiple neighboring frequencies as the target
CSFB to frequency for handovers of UEs running a certain type
UTRAN of services during service-based inter-frequency
handovers. If this option is deselected, the eNodeB
PS Inter-
does not perform the selection. This option applies
RAT
only to LTE FDD and LTE TDD.
Mobility
between SrvccRatSteeringSwitch: If this option is selected, the
E- eNodeB selects only the RAT with the highest voice

eRAN

nd
UTRAN service priority for measurements during coverage-

and based SRVCC. If this option is deselected, the
CDMA2 eNodeB selects different target RATs for
000 measurements. This option takes effect only when the
RAN RatLayerSwitch option is deselected. This option
Sharing applies only to LTE FDD and LTE TDD.
with
PsRatSteeringSwitch: If this option is selected, the
Commo
eNodeB selects only the RAT with the highest data
n
service priority for measurements during coverage-
Carrier
based inter-RAT handovers for data services. If this
PS option is deselected, the eNodeB selects different
Mobility target RATs for measurements. This option takes
from E- effect only when the RatLayerSwitch option is
UTRAN deselected. This option applies only to LTE FDD and
to LTE TDD.
CDMA2
GUI Value Range: IntraFreqCoverHoS-
000
witch(IntraFreqCoverHoSwitch), InterFreqCoverHoS-
HRPD
witch(InterFreqCoverHoSwitch),
Based
Cdma1xRttCsfbSwitch(Cdma20001xRttCsfbSwitch),
on
UtranServiceHoSwitch(UtranServiceHoSwitch),
Frequen
GeranServiceHoSwitch(GeranServiceHoSwitch),
cy-
UlQualityInterRATHoSwitch(UlQualityInterRA-
specific
THoSwitch),
Factors
InterPlmnHoSwitch(InterPlmnHoSwitch),
ServiceBasedInterFreqHoSwitch(ServiceBasedInter-
FreqHoSwitch), UlQualityInterFreqHoS-
witch(UlQualityInterFreqHoSwitch),
CSFBLoadInfoSwitch(CSFBLoadInfoSwitch),
Cdma1XrttEcsfbSwitch(Cdma1XrttEcsfbSwitch),
EmcBlindHoA1Switch(EmcBlindHoA1Switch),
EmcInterFreqBlindHoSwitch(EmcInterFreqBlind-
HoSwitch), EPlmnSwitch(EPlmnSwitch),
ServiceReqInterFreqHoSwitch(ServiceReqInterFreq-
HoSwitch),
VoipHoControlSwitch(VoipHoControlSwitch),
UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbS-
witch), GeranUltraFlashCsfbS-
witch(GeranUltraFlashCsfbSwitch),
RatLayerSwitch(RatLayerSwitch), ServiceBasedMul-
tiFreqHoSwitch(ServiceBasedMultiFreqHoSwitch),
SrvccRatSteeringSwitch(SrvccRatSteeringSwitch),
PsRatSteeringSwitch(PsRatSteeringSwitch)
Unit: None
Actual Value Range: IntraFreqCoverHoSwitch,
InterFreqCoverHoSwitch, Cdma1xRttCsfbSwitch,
UtranServiceHoSwitch, GeranServiceHoSwitch,
UlQualityInterRATHoSwitch, InterPlmnHoSwitch,

eRAN

nd
ServiceBasedInterFreqHoSwitch, UlQualityInterFreq-
HoSwitch, CSFBLoadInfoSwitch,
Cdma1XrttEcsfbSwitch, EmcBlindHoA1Switch,
EmcInterFreqBlindHoSwitch, EPlmnSwitch,
ServiceReqInterFreqHoSwitch,
VoipHoControlSwitch, UtranUltraFlashCsfbSwitch,
GeranUltraFlashCsfbSwitch, RatLayerSwitch,
ServiceBasedMultiFreqHoSwitch, SrvccRatSteeringS-
witch, PsRatSteeringSwitch
Default Value: IntraFreqCoverHoSwitch:On,
InterFreqCoverHoSwitch:On,
Cdma1xRttCsfbSwitch:Off, UtranServiceHoS-
witch:Off, GeranServiceHoSwitch:Off,
UlQualityInterRATHoSwitch:Off,
InterPlmnHoSwitch:Off, ServiceBasedInterFreqHoS-
witch:Off, UlQualityInterFreqHoSwitch:Off,
CSFBLoadInfoSwitch:Off,
Cdma1XrttEcsfbSwitch:Off,
EmcBlindHoA1Switch:Off, EmcInterFreqBlindHoS-
witch:Off, EPlmnSwitch:Off, ServiceReqInterFreq-
HoSwitch:Off, VoipHoControlSwitch:Off,
UtranUltraFlashCsfbSwitch:Off,
GeranUltraFlashCsfbSwitch:Off, RatLayerSwitch:Off,
ServiceBasedMultiFreqHoSwitch:Off,
SrvccRatSteeringSwitch:Off,
PsRatSteeringSwitch:Off
InterPlm CnOper ADD None None Meaning: Indicates the index of the operator. This
nHoList atorId INTERP parameter applies only to LTE FDD and LTE TDD.
LMNH GUI Value Range: 0~5
OLIST
Unit: None
LST
INTERP Actual Value Range: 0~5
LMNH Default Value: None
OLIST
RMV
INTERP
LMNH
OLIST

eRAN

nd
InterPlm TarMcc ADD LBFD-0 Coverag Meaning: Indicates the mobile country code of the
nHoList INTERP 0201801 e Based target PLMN. This parameter applies only to LTE
LMNH / Intra- FDD and LTE TDD.
OLIST TDLBF frequenc GUI Value Range: 3 characters
LST D-00201 y
801 Handov Unit: None
INTERP
LMNH LBFD-0 er Actual Value Range: 000~999
OLIST 0201802 Coverag Default Value: None
RMV / e Based
INTERP TDLBF Inter-
LMNH D-00201 frequenc
OLIST 802 y
LBFD-0 Handov
0201804 er
/ Distance
TDLBF Based
D-00201 Inter-
804 frequenc
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
01019/ y
TDLOF Handov
D-00101 er
9 PS Inter-
LOFD-0 RAT
01020/ Mobility
TDLOF between
D-00102 E-
0 UTRAN
and
LOFD-0 UTRAN
01033/
TDLOF PS Inter-
D-00103 RAT
3 Mobility
between
E-
UTRAN
and
GERAN
CS
Fallback

eRAN

nd
to
UTRAN

eRAN

nd
InterPlm TarMnc ADD LBFD-0 Coverag Meaning: Indicates the mobile network code of the
nHoList INTERP 0201801 e Based target PLMN. This parameter applies only to LTE
LMNH / Intra- FDD and LTE TDD.
OLIST TDLBF frequenc GUI Value Range: 2~3 characters
LST D-00201 y
801 Handov Unit: None
INTERP
LMNH LBFD-0 er Actual Value Range: 00~99,000~999
OLIST 0201802 Coverag Default Value: None
RMV / e Based
INTERP TDLBF Inter-
LMNH D-00201 frequenc
OLIST 802 y
LBFD-0 Handov
0201804 er
/ Distance
TDLBF Based
D-00201 Inter-
804 frequenc
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
01019/ y
TDLOF Handov
D-00101 er
9 PS Inter-
LOFD-0 RAT
01020/ Mobility
TDLOF between
D-00102 E-
0 UTRAN
and
LOFD-0 UTRAN
01033/
TDLOF PS Inter-
D-00103 RAT
3 Mobility
between
E-
UTRAN
and
GERAN
CS
Fallback

eRAN

nd
to
UTRAN
EutranE ShareM ADD LOFD-0 RAN Meaning:

xternalC cc EUTRA 01036/ Sharing Indicates the mobile country code of the external E-
ellPlmn NEXTE TDLOF with UTRAN cell that is shared among multiple operators.
RNALC D-00103 Commo
ELLPL 6 n A PLMN ID is comprised of an MCC and an MNC.
MN LOFD-0 Carrier
LST 01037/ RAN The MCC consists of three digits.
EUTRA TDLOF Sharing
The MNC consists of two to three digits.
NEXTE D-00103 with
RNALC 7 Dedicate For example, if the MCC is 123 and the MNC is 45,
ELLPL LOFD-0 d then the PLMN ID is 12345. This parameter applies
MN 70206/ Carrier only to LTE FDD and LTE TDD.
RMV TDLOF Hybrid GUI Value Range: 3 characters
EUTRA D-08122 RAN
NEXTE 4 Sharing Unit: None
RNALC Actual Value Range: 000~999
ELLPL
Default Value: None
MN
EutranE ShareM ADD LOFD-0 RAN Meaning:

xternalC nc EUTRA 01036/ Sharing Indicates the mobile network code of the external E-
ellPlmn NEXTE TDLOF with UTRAN cell that is shared among multiple operators.
RNALC D-00103 Commo
ELLPL 6 n A PLMN ID is comprised of an MCC and an MNC.
MN LOFD-0 Carrier
EUTRA TDLOF Sharing
NEXTE D-00103 with
RNALC 7 Dedicate For example, if the MCC is 123 and the MNC is 45,
ELLPL LOFD-0 d then the PLMN ID is 12345. This parameter applies
MN 70206/ Carrier only to LTE FDD and LTE TDD.
RMV TDLOF Hybrid GUI Value Range: 2~3 characters
EUTRA D-08122 RAN
NEXTE 4 Sharing Unit: None
RNALC Actual Value Range: 00~99,000~999
ELLPL
Default Value: None
MN

eRAN

nd
UtranEx ShareM ADD LOFD-0 RAN Meaning:

ternalCe cc UTRAN 01036/ Sharing Indicates the mobile country code of the external
llPlmn EXTER TDLOF with UTRAN cell that is shared among multiple operators.
NALCE D-00103 Commo
LLPLM 6 n A PLMN ID is comprised of an MCC and an MNC.
N LOFD-0 Carrier
UTRAN TDLOF Sharing
EXTER D-00103 with
NALCE 7 Dedicate For example, if the MCC is 123 and the MNC is 45,
LLPLM d then the PLMN ID is 12345. This parameter applies
N Carrier only to LTE FDD and LTE TDD.
RMV GUI Value Range: 3 characters
UTRAN
EXTER Unit: None
NALCE Actual Value Range: 000~999
LLPLM
Default Value: None
N
UtranEx ShareM ADD LOFD-0 RAN Meaning:

ternalCe nc UTRAN 01036/ Sharing Indicates the mobile network code of the external
llPlmn EXTER TDLOF with UTRAN cell that is shared among multiple operators.
NALCE D-00103 Commo
N LOFD-0 Carrier
UTRAN TDLOF Sharing
EXTER D-00103 with
RMV GUI Value Range: 2~3 characters
UTRAN
EXTER Unit: None
NALCE Actual Value Range: 00~99,000~999
LLPLM
Default Value: None
N

eRAN

nd
GeranEx ShareM ADD LOFD-0 RAN Meaning:

ternalCe cc GERAN 01036/ Sharing Indicates the mobile country code of the external
llPlmn EXTER TDLOF with GERAN cell that is shared among multiple operators.
NALCE D-00103 Commo
N LOFD-0 Carrier
GERAN TDLOF Sharing
EXTER D-00103 with
GERAN
EXTER Unit: None
NALCE Actual Value Range: 000~999
LLPLM
Default Value: None
N
GeranEx ShareM ADD LOFD-0 RAN Meaning:

ternalCe nc GERAN 01036/ Sharing Indicates the mobile network code of the external
llPlmn EXTER TDLOF with GERAN cell that is shared among multiple operators.
NALCE D-00103 Commo
N LOFD-0 Carrier
GERAN TDLOF Sharing
EXTER D-00103 with
GERAN
EXTER Unit: None
NALCE Actual Value Range: 00~99,000~999
LLPLM
Default Value: None
N

eRAN

nd
GlobalP Protocol MOD LOFD-0 SRVCC Meaning:

rocSwitc MsgOpt GLOBA 01022/ to Indicates whether to optimize protocol messages sent
h Switch LPROC TDLOF UTRAN by the eNodeB. This parameter provides the following
SWITC D-00102 SRVCC options:
H 2 to
LST LOFD-0 RrcSetupOptSwitch: If this option is selected,
GERAN
GLOBA 01023/ optimization of RRCConnectionSetup messages is
Ultra- enabled. In this case, IEs with protocol-defined default
LPROC TDLOF
Flash values are no longer included in the
SWITC D-00102
CSFB to RRCConnectionSetup messages. For details about the
H 3
GERAN protocol-defined default setting, see 3GPP TS 36.331.
LOFD-0 This option applies only to LTE FDD and LTE TDD.
Flash
81283/
CS IucsRrcRecfgMcCombSwitch: If this option is
TDLOF
Fallback selected, the eNodeB includes the radio resource
D-08120
to configuration and measurement configuration for a
3
GERAN UE in one RRCConnectionReconfiguration message
LOFD-0
PS Inter- during initial access. This option applies only to LTE
01053/
RAT FDD and LTE TDD.
TDLOF
D-00105 Mobility
RcrpRrcRecfgMcCombSwitch: If this option is
3 between
selected, the eNodeB includes the radio resource
E-
LOFD-0 configuration and measurement configuration for a
UTRAN
01020/ UE in one RRCConnectionReconfiguration message
and
TDLOF during RRC connection reestablishment. The option
GERAN
D-00102 will not take effect on the interaction of RRC
0 PS Inter- connection reestablishment and other signaling
RAT procedures. This option applies only to LTE FDD and
TDLOF Mobility LTE TDD.
D-00101 between
9/ E- RrcRecfgMcOptSwitch: If this option is selected, the
LOFD-0 UTRAN cell measurement configurations with the CIO of 0
01019 and (indicated by cellIndividualOffset) are no longer
LBFD-0 UTRAN included in the measurement configurations delivered
02007/ to UEs. This option applies only to LTE FDD and LTE
RRC TDD.
TDLBF
Connect
D-00200
ion IdleCsfbRedirectOptSwitch: If this option is selected
7
Manage and the preferred CSFB policy is redirection, during
LBFD-0 ment CSFB of UEs in idle mode, the eNodeB no longer
02018/ activates the security mode or performs RRC
Mobility
TDLBF connection reconfiguration, but sends a redirection
Manage
D-00201 message. According to the security requirements of
ment
8 3GPP CR (R2-1714284), this option takes effect only
LOFD-0 CS for redirections to UTRAN cells. This option applies
01033/ Fallback only to LTE FDD and LTE TDD.
TDLOF to
UTRAN UlNasBufferSwitch: If this option is selected, the
D-00103 eNodeB buffers uplink NAS messages sent by the UE
3 CS before the UE-associated logical S1 connection is
Fallback available and sends these messages after the UE-

eRAN

nd
LOFD-0 to associated logical S1 connection is available. If this

01034/ GERAN option is deselected, the eNodeB releases this UE after
TDLOF RAN the procedures end. This option applies only to LTE
D-00103 Sharing FDD and LTE TDD.
4 with IratMeasCfgTransSwitch: If this option is selected, the
LOFD-0 Commo Handover Required message that the eNodeB sends to
01036/ n a BSC contains the IE IRAT Measurement
TDLOF Carrier Configuration. This option applies only to LTE FDD
D-00103 and LTE TDD.
6
GeranAnrMcOptSwitch: This option controls whether
measurement configuration optimization takes effect
when ANR with GERAN is enabled. If this option is
deselected, the optimization does not take effect. That
is, when an eNodeB delivers measurement
configuration to UEs to perform CGI reading for ANR
with GERAN, the carrierFreqs IE can contain multiple
GERAN frequencies. If this option is selected, the
optimization takes effect, and the carrierFreqs IE
contains only one GERAN frequency. This option
applies only to LTE FDD and LTE TDD.
InactDiscardSwitch: This option specifies whether to
terminate the ongoing signaling flow when the UE
inactivity timer expires. If this option is deselected,
the ongoing flow is terminated and the eNodeB
directly releases the UE. If this option is selected, the
ongoing flow is not terminated and the timer is
restarted. This option involves procedures of an
eNodeB waiting for Uu interface response messages,
such as RRCConnectionReconfigurationComplete,
SecurityModeComplete, RRCConnectionReestablish-
mentComplete, UECapabilityInformation, and
CounterCheckResponse messages, from UEs. This
option applies only to LTE FDD and LTE TDD.
SRVCCHoBasedUeCapSwitch: If this option is
selected, the eNodeB determines whether to trigger an
SRVCC based only on UE's SRVCC capabilities, not
the SRVCCOperationPossible IE that the MME sends
to the eNodeB. If this option is deselected, the
eNodeB determines whether to trigger an SRVCC
based on the SRVCCOperationPossible IE that the
MME sends to the eNodeB. This option applies only
L2GPLMNChooseOptSwitch: This option specifies
whether to enable target PLMN ID optimization for
handovers to GERAN. If this option is selected, the
eNodeB takes the NCL-defined PLMN IDs and

eRAN

nd
includes them in the handover request messages or

RIM request messages. If this option is deselected, the
optimization is not activated. This option applies only
HoInRrcRecfgMcCombSwitch: If this option is

selected, after a UE is handed over to a cell, the cell
delivers the radio resource configuration and
measurement configuration in a single RRC
Connection Reconfiguration message to the UE
during the resource reconfiguration procedure. This
UeCapEnquiryCombSwitch: If this option is selected

and a UE sends an Attach Request message to an
eNodeB during initial access, the eNodeB directly
queries capabilities of the UE after the RRC
connection for the UE is established. This option does
not apply to subsequent UE capability query induced
by the CA extended frequency band combination
query. If this option is deselected and a UE sends an
Attach Request message to an eNodeB during initial
access, the eNodeB does not query capabilities of the
UE until the MME sends a UE context setup request
to the eNodeB. This option applies only to LTE FDD
and LTE TDD.
UeTraceOptSwitch: If this option is selected, the

eNodeB does not handle the DEACTIVATE TRACE
message sent by the MME or stop the UE tracing task
in the eNodeB until the UE is released or handed over
to a cell served by another eNodeB. This option
PaDistributeMechOptSwitch: If this option is selected,

the PaPcOff parameter value is taken as the PA value
in the RRCConnectionSetup or RRC Connection
Reestablishment message. If this option is deselected,
the PA value is set to -3 dB by default. This option
InactReSyncCompatSwitch: If this option is selected

and the eNodeB determines that the UE inactivity
timer expires and the resynchronization procedure is
being performed, the eNodeB preferentially processes
the resynchronization procedure and the timer restarts.
If this option is deselected, the optimization does not
take effect. That is, the UE is directly released when
the UE inactivity timer expires. This option applies

eRAN

nd
VolteX2HoDelayOptSwitch: If this option is selected,

when receiving a VoLTE UE handover complete
message, the target eNodeB for an X2-based handover
starts to send uplink data with QCI of 1. If this option
is deselected, the target eNodeB for an X2-based
handover starts to send uplink data with QCI of 1 after
receiving an MME PATH SWITCH REQUEST
ACKNOWLEDGE message. This option applies only
UeUtranCapEnquiryOptSwitch: When a serving cell
is not configured with neighboring UTRAN cells, the
eNodeB does not query UE's UTRAN capability if
this option is selected. If this option is deselected, this
optimization does not take effect. This option applies
only to LTE TDD.
FreqRandomOptSwitch: If this option is selected, the
eNodeB randomly selects a target frequency when
there are multiple candidate frequencies with the same
priority. If this option is deselected, this optimization
function does not take effect. This option applies only
MrMdtMeasOptSwitch: If this option is selected,
measurement configurations related to MR and MDT
are delivered separately. If this option is deselected,
this optimization does not take effect. This option
CellReselectionOptSwitch: If this option is selected,
when the cell reselection configuration needs to be
contained in an RRC release message, the eNodeB
performs as follows:
- If inter-RAT cell reselection is not configured in the
eNodeB, the eNodeB does not determine inter-RAT
operator-dedicated cell reselection frequency
priorities.
-If inter-RAT cell reselection is configured in the
eNodeB, the eNodeB determines inter-RAT operator-
dedicated cell reselection frequency priorities.
If this option is deselected, the eNodeB always
determines inter-RAT operator-dedicated cell
reselection frequency priorities regardless of whether
inter-RAT cell reselection is configured in the
eNodeB. This option applies only to LTE FDD and
LTE TDD.
X2GuGroupIdInfoOptSwitch: If this option is
selected, the eNodeB does not include any GU Group

eRAN

nd
Id dedicated to NB-IoT in the IE GU Group Id List in

X2 setup request, X2 setup response, and eNodeB
configuration update messages when the eNodeB has
multiple GU Group Ids. (For details about the IE, see
3GPP TS 36.423.) If all GU Group Ids are dedicated
to NB-IoT, the eNodeB can include the GU Group Ids
dedicated to NB-IoT. If this option is deselected, the
eNodeB can include the GU group Ids dedicated to
NB-IoT in the IE Group Id List in X2 setup request,
X2 setup response, and eNodeB configuration update
messages. This option applies only to LTE FDD and
LTE TDD.
GUI Value Range: RrcSetupOptSwitch,
IucsRrcRecfgMcCombSwitch,
RcrpRrcRecfgMcCombSwitch,
RrcRecfgMcOptSwitch, IdleCsfbRedirectOptSwitch,
UlNasBufferSwitch, IratMeasCfgTransSwitch,
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch,
PaDistributeMechOptSwitch, InactReSyncCompatS-
witch, VolteX2HoDelayOptSwitch,
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch,
CellReselectionOptSwitch, X2GuGroupIdInfoOptS-
witch
Unit: None
Actual Value Range: RrcSetupOptSwitch,
IucsRrcRecfgMcCombSwitch,
RcrpRrcRecfgMcCombSwitch,
RrcRecfgMcOptSwitch, IdleCsfbRedirectOptSwitch,
UlNasBufferSwitch, IratMeasCfgTransSwitch,
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch,
PaDistributeMechOptSwitch, InactReSyncCompatS-
witch, VolteX2HoDelayOptSwitch,
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch,
CellReselectionOptSwitch, X2GuGroupIdInfoOptS-
witch
Default Value: RrcSetupOptSwitch:Off,
IucsRrcRecfgMcCombSwitch:Off,

eRAN

nd
RcrpRrcRecfgMcCombSwitch:Off,
RrcRecfgMcOptSwitch:Off, IdleCsfbRedirectOptS-
witch:Off, UlNasBufferSwitch:On,
IratMeasCfgTransSwitch:Off,
GeranAnrMcOptSwitch:Off, InactDiscardSwitch:Off,
SRVCCHoBasedUeCapSwitch:Off,
L2GPLMNChooseOptSwitch:Off,
HoInRrcRecfgMcCombSwitch:Off,
UeCapEnquiryCombSwitch:Off,
UeTraceOptSwitch:Off, PaDistributeMechOptS-
witch:On, InactReSyncCompatSwitch:Off,
VolteX2HoDelayOptSwitch:Off, UeUtranCapEnquir-
yOptSwitch:Off, FreqRandomOptSwitch:Off,
MrMdtMeasOptSwitch:Off, CellReselectionOptS-
witch:Off, X2GuGroupIdInfoOptSwitch:Off
License MaxUse ADD LOFD-0 RAN Meaning: Indicates the proportion of the number of
Sharing rNumRa LICENS 01036/ Sharing UEs in RRC_CONNECTED mode of the operator
Policy te ESHAR TDLOF with when the eNodeB is shared among operators. This
INGPO D-00103 Commo parameter must be set based on the contract signed
LICY 6 n with operators. This parameter applies only to LTE
MOD LOFD-0 Carrier FDD and LTE TDD.
LICENS 01037/ RAN GUI Value Range: 1~100
ESHAR TDLOF Sharing Unit: %
INGPO D-00103 with
LICY 7 Dedicate Actual Value Range: 1~100
LST LOFD-0 d Default Value: None

LICENS 70206/ Carrier
ESHAR TDLOF Hybrid
INGPO D-08122 RAN
LICY 4 Sharing
LOFD-0 Fair
70213 User
Sharing

eRAN

nd
LicRatio TrafficS MOD LOFD-0 RAN Meaning: Indicates the mode of traffic sharing
haringT LICRAT 01036/ Sharing between the operators in RAN sharing scenarios. If
ype IO TDLOF with this parameter is set to SHARING, all the operators
LST D-00103 Commo share the total traffic of the eNodeB without
LICRAT 6 n proportional limits. If this parameter is set to
IO LOFD-0 Carrier DEDICATE and the ENodeBSharingMode parameter
01037/ RAN is not set to INDEPENDENT, all the operators share
TDLOF Sharing the total traffic of the eNodeB based on specific
D-00103 with proportions. However, the vacant traffic of an operator
7 Dedicate can be used by other operators. This parameter applies
d only to LTE FDD and LTE TDD.
LOFD-0
70206/ Carrier GUI Value Range: SHARING(Sharing),
TDLOF Hybrid DEDICATE(Dedicate)
D-08122 RAN Unit: None
4 Sharing Actual Value Range: SHARING, DEDICATE
Default Value: SHARING(Sharing)
LicRatio TrfRatio ADD LOFD-0 RAN Meaning: Indicates the proportion of traffic used by
SharePo LICRAT 01036/ Sharing the operator when the eNodeB is shared among
licy IOSHA TDLOF with operators. This parameter must be set based on the
REPOLI D-00103 Commo contract signed by operators. If this parameter is set to
CY 6 n 0, services except emergency calls of this operator are
MOD LOFD-0 Carrier not admitted.
LICRAT 01037/ RAN GUI Value Range: 0~100
IOSHA TDLOF Sharing Unit: %
REPOLI D-00103 with
CY 7 Dedicate Actual Value Range: 0~100
LST LOFD-0 d Default Value: 0

LICRAT 70206/ Carrier
IOSHA TDLOF Hybrid
REPOLI D-08122 RAN
CY 4 Sharing

eRAN

nd
LicRatio TrfShari ADD LOFD-0 RAN Meaning: Indicates the proportion of traffic that the
SharePo ngRatio LICRAT 01036/ Sharing operator can share with other operators when the
licy IOSHA TDLOF with eNodeB is shared among operators.
REPOLI D-00103 Commo GUI Value Range: 0~100
CY 6 n
Carrier Unit: %
MOD LOFD-0
LICRAT 70206/ Hybrid Actual Value Range: 0~100
IOSHA TDLOF RAN Default Value: 0
REPOLI D-08122 Sharing
CY 4 RAN
LST LOFD-0 Sharing
LICRAT 01037/ with
IOSHA TDLOF Dedicate
REPOLI D-00103 d
CY 7 Carrier
CellAlg RanShar MOD LOFD-0 RAN Meaning: Indicates whether admission control,
oSwitch eModeS CELLA 01036/ Sharing congestion control, and scheduling policies are
witch LGOSW TDLOF with operator-specific. If this switch is turned on,
ITCH D-00103 Commo admission control, congestion control, and scheduling
LST 6 n policies are operator-specific. On FDD and TDD
CELLA LOFD-0 Carrier networks, operators share data channel resources
LGOSW 01112/ MOCN according to the specified RB percentages. On NB-
ITCH TDLOF Flexible IoT networks, operators share UE context storage
D-00111 Priority resources according to the specified percentages. If
2 Based this switch is turned off, admission control, congestion
Campin control, and scheduling policies are not operator-
LOFD-0 specific.
70206/ g
TDLOF Hybrid GUI Value Range: OFF(Off), ON(On),
D-08122 RAN STATIC_SHARING(STATIC_SHARING)
4 Sharing Unit: None
Actual Value Range: OFF, ON, STATIC_SHARING
Default Value: OFF(Off)

eRAN

nd
CellOp OpDlRb ADD LOFD-0 RAN Meaning: Indicates the percentage of resource blocks
UsedRat CELLO 01036/ Sharing (RBs) occupied by the operator on the physical
io P TDLOF with downlink shared channel (PDSCH) when RAN
MOD D-00103 Commo sharing is enabled on the eNodeB and the
CELLO 6 n RanShareModeSwitch parameter of the
P LBFD-0 Carrier CellAlgoSwitch MO is set to ON(On). If the data
02009/ Broadca volume is sufficient, the percentage of RBs occupied
LST by each operator will reach the preset value.
CELLO TDLBF st of
D-00200 system Modifications on this parameter affect the percentage
P of RBs occupied by operators on the PDSCH. When
9 informat
ion the OpPrbGroupshareSwitch option is selected in
LOFD-0 RAN sharing mode, this parameter is used to calculate
70206/ Hybrid the percentage of RBs occupied by the operator
TDLOF RAN resource group on the PDSCH. The percentage of RBs
D-08122 Sharing occupied by an operator resource group is the sum of
4 percentages of RBs occupied by operators in the
group. This parameter takes effect only in RAN
sharing with common carrier mode or in hybrid RAN
sharing mode with more than one CellOp MO being
configured. This parameter applies only to LTE FDD
and LTE TDD.
GUI Value Range: 1~100
Unit: %
Default Value: 16

eRAN

nd
CellOp OpUlRb ADD LOFD-0 RAN Meaning: Indicates the percentage of resource blocks
UsedRat CELLO 01036/ Sharing (RBs) occupied by the operator on the physical uplink
io P TDLOF with shared channel (PUSCH) when RAN sharing is
MOD D-00103 Commo enabled on the eNodeB and the RanShareModeSwitch
CELLO 6 n parameter of the CellAlgoSwitch MO is set to
P LBFD-0 Carrier ON(On). If the data volume is sufficient, the
02009/ Broadca percentage of RBs occupied by each operator will
LST reach the preset value. Modifications on this
CELLO TDLBF st of
D-00200 system parameter affect the percentages of RBs occupied by
P operators on the PUSCH. When the
9 informat
ion OpPrbGroupshareSwitch option is selected in RAN
LOFD-0 sharing mode, this parameter is used to calculate the
70206/ Hybrid percentage of RBs occupied by the operator resource
TDLOF RAN group on the PUSCH. The percentage of RBs
D-08122 Sharing occupied by an operator resource group is the sum of
4 percentages of RBs occupied by operators in the
group. This parameter takes effect only in RAN
sharing with common carrier mode or in hybrid RAN
sharing mode with more than one CellOp MO being
configured. This parameter applies only to LTE FDD
and LTE TDD.
Unit: %
Default Value: 16

eRAN

nd
ENodeB RanShar MOD LOFD-0 Automat Meaning:

AlgoSwi ingAnrS ENODE 02001/ ic Indicates whether to enable the ANR algorithm in
tch witch BALGO TDLOF Neighbo RAN sharing mode. This parameter provides the
SWITC D-00200 ur following options:
H 1 Relation
LST LOFD-0 (ANR) NBSLTEPLMNRoundSwitch: If this option is
ENODE 02002/ Inter- selected, some neighboring eNodeBs provide cells
BALGO TDLOF RAT that work in E-UTRAN sharing mode and broadcast
SWITC D-00200 ANR their PLMN lists in a round robin (RR) manner. In this
H 2 case, if the IntraRatEventAnrSwitch or
RAN IntraRatFastAnrSwitch option of the AnrSwitch
LOFD-0 Sharing parameter is selected for the local eNodeB, the local
01036/ with eNodeB obtains the actual cell global identifier (CGI)
TDLOF Commo and serving PLMN list for a neighboring cell
D-00103 n broadcasting PLMNs from the U2000 in an RR
6 Carrier manner after the UE reports the CGI of the cell during
LOFD-0 RAN ANR measurements. If both the
01037/ Sharing NBSLTEPLMNRoundSwitch and
TDLOF with NBSLTERANSharingSwitch options are selected, the
D-00103 Dedicate NBSLTEPLMNRoundSwitch option takes precedence
7 d over the NBSLTERANSharingSwitch option. This
LOFD-0 Carrier option applies only to LTE FDD and LTE TDD.
70206/ Hybrid NBSLTERANSharingSwitch: If this option is
TDLOF RAN selected, some neighboring eNodeBs provide cells
D-08122 Sharing that work in E-UTRAN sharing mode. In this case, if
4 the IntraRatEventAnrSwitch or IntraRatFastAnrS-
witch option of the AnrSwitch parameter is selected
for the local eNodeB, the local eNodeB obtains the
serving PLMN list for a neighboring cell from the
U2000 after the UE reports the CGI of the cell during
ANR measurements. If the UE has reported the
PLMN list, the local eNodeB does not need to obtain
the serving PLMN list for a neighboring cell from the
U2000. This option applies only to LTE FDD and LTE
TDD.
NBSUTRANRANSharingSwitch: If this option is
selected, some neighboring NodeBs provide cells that
work in UTRAN sharing mode. In this case, if the
UtranEventAnrSwitch or UtranFastAnrSwitch option
of the AnrSwitch parameter is selected for the local
eNodeB, the local eNodeB obtains the serving PLMN
list for a neighboring cell from the U2000 after the UE
reports the CGI of the cell during ANR measurements.
If the UE has reported the PLMN list, the local
eNodeB does not need to obtain the serving PLMN
list for a neighboring cell from the U2000. This option

eRAN

nd
NBSGERANRANSharingSwitch: If this option is

selected, some neighboring BTSs provide cells that
work in GERAN sharing mode. In this case, if the
GeranEventAnrSwitch or GeranFastAnrSwitch option
of the AnrSwitch parameter is selected for the local
eNodeB, the local eNodeB obtains the serving PLMN
list for a neighboring cell from the U2000 after the UE
reports the CGI of the cell during ANR measurements.
This option applies only to LTE FDD and LTE TDD.
GUI Value Range: NBSLTEPLMNRound-
Switch(NBSLTEPLMNRoundSwitch),
NBSLTERANSharingSwitch(NBSLTERANSharingS-
witch), NBSUTRANRANSharingS-
witch(NBSUTRANRANSharingSwitch),
NBSGERANRANSharingS-
witch(NBSGERANRANSharingSwitch)
Unit: None
Actual Value Range: NBSLTEPLMNRoundSwitch,
NBSLTERANSharingSwitch, NBSUTRANRANShar-
ingSwitch, NBSGERANRANSharingSwitch
Default Value: NBSLTEPLMNRoundSwitch:Off,
NBSLTERANSharingSwitch:Off,
NBSUTRANRANSharingSwitch:Off,
NBSGERANRANSharingSwitch:Off
GTRAN EPCFG SET LBFD-0 Self- Meaning: Indicates the configuration mode of an end
SPARA MODE GTRAN 02035 configur point object, including S1SIMPLE_MODE(S1 Simple
SPARA ation Mode), X2SIMPLE_MODE(X2 Simple Mode) and
FBFD-0 EX2SIMPLE_MODE(eX2 Simple Mode). This
LST 10016 Transmi
GTRAN parameter can be set to one or multiple values. The
ssion parameter takes effect only in LTE.
SPARA Network
ing GUI Value Range: S1SIMPLE_MODE(S1 Simple
Mode), X2SIMPLE_MODE(X2 Simple Mode),
EX2SIMPLE_MODE(eX2 Simple Mode)
Unit: None
Actual Value Range: S1SIMPLE_MODE,
X2SIMPLE_MODE, EX2SIMPLE_MODE
Default Value: S1SIMPLE_MODE:0,
X2SIMPLE_MODE:0, EX2SIMPLE_MODE:0

eRAN

nd
CellAlg RelayS MOD LAOFD Out of Meaning:

oSwitch witch CELLA -111202/ Band Indicates whether to enable relay-related functions.
LGOSW TDLAO Relay
ITCH FD-080 In-Band OutOfBandRelaySwitch: Indicates whether to enable
LST 405 Relay out-of-band relay. If this option is selected, out-of-
CELLA LAOFD band relay is enabled. If this option is deselected, out-
LGOSW -131208 of-band relay is disabled. This option applies only to
ITCH / LTE FDD and LTE TDD.
TDLAO InBandRelayDeNbSwitch: Indicates whether to
FD-131 enable in-band relay for the DeNB. If this option is
406 selected, in-band relay is enabled for the DeNB. If this
option is deselected, in-band relay is disabled for the
DeNB. This option applies only to LTE FDD and LTE
TDD.
InBandRelayReNbSwitch: Indicates whether to enable
in-band relay for the ReNB. If this option is selected,
in-band relay is enabled for the ReNB. If this option is
deselected, in-band relay is disabled for the ReNB.
InBandRelayDistantDeploySw: Indicates whether to
allow the first-hop ReNB to be deployed less than 20
km from the DeNB in in-band relay scenarios. If this
option is selected, the first-hop ReNB can be deployed
less than 20 km from the DeNB in in-band relay
scenarios. If this option is deselected, the first-hop
ReNB cannot be deployed less than 20 km from the
DeNB in in-band relay scenarios. This option applies
GUI Value Range:
OutOfBandRelaySwitch(OutOfBandRelaySwitch),
InBandRelayDeNbSwitch(InBandRelayDeNbSwitch),
InBandRelayReNbSwitch(InBandRelayReNbSwitch),
InBandRelayDistantDeploySw(InBandRelayDistant-
DeploySw)
Unit: None
Actual Value Range: OutOfBandRelaySwitch,
InBandRelayDeNbSwitch, InBandRelayReNbSwitch,
InBandRelayDistantDeploySw
Default Value: OutOfBandRelaySwitch:Off,
InBandRelayDeNbSwitch:Off, InBandRelayReNbS-
witch:Off, InBandRelayDistantDeploySw:Off

eRAN

nd
CellAlg UlSchS MOD LOFD-0 VoIP Meaning:

oSwitch witch CELLA 01016/ Semi- Indicates whether to enable uplink scheduling
LGOSW TDLOF persisten functions for the cell.
ITCH D-00101 t
LST 6 Scheduli SpsSchSwitch: Indicates whether to enable semi-
CELLA LOFD-0 ng persistent scheduling during talk spurts of VoLTE
LGOSW 01048/ TTI services. If this option is selected, semi-persistent
ITCH TDLOF Bundlin scheduling is applied during talk spurts of VoLTE
D-00104 g services. If this option is deselected, dynamic
8 scheduling is applied during talk spurts of VoLTE
Dynami services. This option applies only to LTE FDD and
LBFD-0 c LTE TDD.
0101502 Scheduli
/ ng SinrAdjustSwitch: Indicates whether to adjust the
TDLBF Basic measured SINR based on ACK/NACK messages in
D-00101 Scheduli the UL hybrid automatic repeat request (HARQ)
502 ng processes. This option applies only to LTE FDD and
LBFD-0 LTE TDD.
MBR>G
02025/ BR PreAllocationSwitch: Indicates whether to enable
TDLBF Configu preallocation in the uplink. If this option is selected:
D-00202 ration (1) If the SmartPreAllocationSwitch option is
5
UL 2x2 deselected and a UE is in the discontinuous reception
LBFD-0 MU- (DRX) state, preallocation is disabled for the UE in
70102/ MIMO the uplink; (2) If the SmartPreAllocationSwitch option
TDLBF is deselected and the UE is not in the DRX state,
D-07010 UL 2x4 preallocation is enabled for the UE in the uplink; (3) If
2 MU- the SmartPreAllocationSwitch option is selected and
MIMO the SmartPreAllocationDuration parameter value is
LOFD-0
01002 AMC greater than 0, smart preallocation is enabled for the
Uplink UE in the uplink; (4) If the SmartPreAllocationSwitch
LOFD-0 option is selected and the SmartPreAllocationDuration
01058/ Coverag
e parameter value is 0, preallocation is disabled for the
TDLOF UE in the uplink. If this option is deselected,
D-00105 Improve
ment for preallocation is disabled for the UE in the uplink. If
8 bearer-level preallocation or bearer-level smart
Video
LBFD-0 preallocation is enabled for a QCI, cell-level
01006/ Enhance preallocation and cell-level smart preallocation do not
TDLBF d UL apply to UEs with the QCI. This option applies only to
D-00100 Frequen LTE FDD and LTE TDD.
6 cy
Selectiv UlVmimoSwitch: Indicates whether to enable multi-
LOFD-1 e user MIMO (MU-MIMO) in the uplink. If this option
20205 Scheduli is selected, the eNodeB performs MU-MIMO pairing
LBFD-0 ng among UEs based on related principles. UEs forming
60102 UL a pair transmit data using the same time-frequency
TDLEO 2x64 resources, which improves the system throughput and
FD-121 MU- spectral efficiency. This option applies only to LTE
60302 MIMO FDD and LTE TDD.

eRAN

nd
TDLEO UL 4- TtiBundlingSwitch: Indicates whether to enable

FD-121 Layer transmission time interval (TTI) bundling. If TTI
609 MU- bundling is enabled, more transmission opportunities
TDLEO MIMO are available to UEs within the delay budget for
FD-121 UL 8- VoLTE services on the Uu interface, thereby
610 Layer improving uplink coverage. This option applies only
MU- to LTE FDD and LTE TDD.
TDLOF
D-07022 MIMO SmartPreAllocationSwitch: Indicates whether to
2/ Scheduli enable uplink smart preallocation when the
LOFD-1 ng PreAllocationSwitch option is selected. If both the
31213 Based PreAllocationSwitch option and this option are
on Max selected and the SmartPreAllocationDuration
Bit Rate parameter in the CellPreallocGroup MO is set to a
value greater than 0, uplink smart preallocation is
enabled. Otherwise, uplink smart preallocation is
disabled. This option applies only to LTE FDD and
LTE TDD.
PuschDtxSwitch: Indicates whether the eNodeB uses
the PUSCH discontinuous transmission (DTX)
detection result during uplink scheduling. If this
option is selected for an LTE FDD cell, the eNodeB
determines whether to perform adaptive
retransmission, and also adjusts the CCE aggregation
level of the PDCCH carrying downlink control
information (DCI) format 0 based on the PUSCH
DTX detection result during uplink scheduling. If an
LTE FDD cell is established on an LBBPc, this option
takes effect only if the cell uses less than four RX
antennas and normal cyclic prefix (CP) in the uplink
and the SrsCfgInd parameter in the SRSCfg MO is set
to BOOLEAN_TRUE(True). Note that the LBBPc
does not support PUSCH DTX detection for VMIMO
UEs. For an LTE TDD cell, this option takes effect
only when the uplink-downlink subframe
configuration is set to SA2 or SA5. If this option takes
effect, the eNodeB adjusts the CCE aggregation level
based on the PUSCH DTX detection results. Note that
LTE TDD cells established on LBBPc boards do not
support PUSCH DTX detection. This option applies
UlIblerAdjustSwitch: Indicates whether to enable the
uplink IBLER adjustment algorithm. If this option is
selected, the target IBLER is adjusted for UEs based
on the channel quality and fluctuation to increase the
cell throughput. This option applies only to LTE FDD
and LTE TDD. If this option is selected independently

eRAN

nd
for FDD cells with the UlTargetIBlerAdaptType

option deselected, the algorithm does not take effect.
UlEnhancedFssSwitch: Indicates whether to enable
uplink load-based enhanced frequency selective
scheduling. This option applies only to LTE FDD.
UlIicsAlgoSwitch: Indicates whether to enable the
uplink interference-intensity-based coordinated
scheduling (UL IICS) algorithm. If this option is
selected, interference can be reduced based on
accurate detection of user attributes and scheduling
resource coordination, increasing the cell edge
throughput. This option applies only to LTE TDD.
UlEnhancedSrSchSwitch: Indicates whether uplink re-
scheduling is performed only when the On Duration
timer for the DRX long cycle starts. Uplink re-
scheduling is required if the number of HARQ
retransmissions for a scheduling request (SR) reaches
the maximum value but the scheduling still fails. If
this option is selected, uplink re-scheduling is
performed only when the On Duration timer for the
DRX long cycle starts. If this option is deselected,
uplink re-scheduling is performed immediately when
the number of HARQ retransmissions for SR reaches
the maximum value but the scheduling still fails. It is
recommended that this option be selected for live
networks. This option applies only to LTE FDD and
LTE TDD.
SchedulerCtrlPowerSwitch: Indicates whether the
uplink scheduler performs scheduling without
considering power control restrictions. If this option is
selected, the uplink scheduler performs scheduling
without considering power control restrictions,
ensuring full utilization of the transmit power for all
UEs. If this option is deselected, the uplink scheduler
considers power control restrictions while performing
scheduling. In this case, the transmit power cannot be
fully used for UEs at the cell edge or between the cell
edge and cell center. This option applies only to LTE
FDD and LTE TDD.
UlMinGbrSwitch: Indicates whether to ensure uplink
minimum guaranteed bit rate (GBR). If this option is
selected, the minimum GBR of non-GBR services is
ensured by increasing the scheduling priority of UEs
whose non-GBR service rates are lower than the
minimum GBR of GBR services. This option applies

eRAN

nd
UlMbrCtrlSwitch: Indicates whether to enable uplink

scheduling based on the maximum bit rate (MBR) and
guaranteed bit rate (GBR) on the GBR bearer. If this
option is selected, the eNodeB performs uplink
scheduling on GBR bearers based on the MBR and
GBR. If this option is deselected, the eNodeB
performs uplink scheduling on GBR bearers based
only on the GBR. This option applies only to LTE
FDD and LTE TDD.
MbrUlSchSwitch: Indicates whether the eNodeB
performs uplink scheduling based on the MBR. If this
option is selected, the eNodeB prioritizes UEs based
on the MBRs during uplink scheduling. This option
UeAmbrUlSchSwitch: Indicates whether the eNodeB
performs uplink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this option is
selected, the eNodeB prioritizes UEs based on the
AMBRs of UEs during uplink scheduling. This option
UlEnhancedDopplerSwitch: Indicates whether to
enable enhanced uplink scheduling based on mobility
speed estimation. If this option is selected, enhanced
uplink scheduling based on mobility speed estimation
is enabled. In enhanced uplink scheduling based on
mobility speed estimation, the eNodeB uses Doppler
measurement results to identify low-speed UEs to
further improve uplink performance of low-speed
UEs. If this option is deselected, enhanced uplink
scheduling based on mobility speed is disabled.
Enhanced uplink scheduling based on mobility speed
takes effect only when the DopMeasLevel parameter
is set to CLASS_1(CLASS_1) and the
UlEnhancedDopplerSwitch option is selected. This
option does not apply to cells established on LBBPc
boards. This option applies only to LTE FDD.
UlRaUserSchOptSw: Indicates whether the eNodeB
raises the scheduling priority of UEs sending uplink
access signaling, including MSG5 and the RRC
Connection Reconfiguration Complete message. If
this option is selected, the eNodeB raises the
scheduling priority of UEs sending uplink access
signaling. If this option is deselected, the eNodeB
does not raise the scheduling priority of UEs sending
uplink access signaling. In NB-IoT scenarios with air
interface resource congestion, this option restricts the

eRAN

nd
number of preambles to perform flow control on UEs

accessing the cell.
UlLast2RetransSchOptSwitch: Indicates whether to

optimize the scheduling policy for the last two
retransmissions. If this option is selected, the
scheduling policy is optimized for the last two
retransmissions. If the UE transmit power is not
limited, adaptive retransmission is used, and the
number of RBs increases in the last two
retransmissions to increase the receive success rate of
the last two retransmissions and decrease uplink
RBLER. If this option is deselected, the scheduling
policy is not optimized for the last two
retransmissions. This option applies only to LTE FDD
and LTE TDD.
UlInterfFssSwitch: Indicates whether to enable

interference-based uplink frequency-selective
scheduling. This option applies only to LTE FDD.
UlSmallRBSpectralEffOptSw: Indicates whether to

improve the spectral efficiency of small RBs in the
uplink. If this option is selected, the spectral efficiency
of small RBs in the uplink is optimized, ensuring that
the transmission block size calculated based on
optimized spectral efficiency is not less than the traffic
volume to be scheduled. If this option is deselected,
the spectral efficiency of small RBs in the uplink is
not optimized. This option applies only to LTE FDD
and LTE TDD.
PuschUsePucchRbSwitch: Indicates whether PUCCH

RBs can be occupied by the PUSCH. In scenarios
with a single user: If this option is selected, PUCCH
RBs can be occupied by the PUSCH; if this option is
deselected, PUCCH RBs cannot be occupied by the
PUSCH. In scenarios with multiple users, PUCCH
RBs cannot be occupied by the PUSCH regardless of
the setting of this option. This option applies only to
LTE FDD and LTE TDD.
PuschDtxSchOptSwitch: If this option is selected, the

eNodeB determines whether to perform adaptive
retransmission based on the PUSCH DTX detection
result during uplink scheduling. This option takes
effect only when the uplink-downlink subframe
configuration SA2 or SA5 is used. If an LTE TDD cell
is established on an LBBPc, PUSCH DTX detection is
not supported. This option applies only to LTE TDD.

eRAN

nd
PrachRbReuseSwitch: If this option is selected, the

PUSCH and PRACH transmissions can use the same
resource. If this option is deselected, the PUSCH and
PRACH transmissions cannot use the same resource.
ULFSSAlgoswitch: If this option is deselected, uplink
frequency-selective scheduling is disabled. If this
option is selected, uplink frequency-selective
scheduling is enabled. This option applies only to LTE
TDD.
SrSchDataAdptSw: Indicates whether to enable data
amount adaptation in SR-based scheduling. Data
amount adaptation in SR-based scheduling is enabled
only when this option is selected. This option applies
only to LTE FDD.
UlFssUserThdStSwitch: If this option is selected, the
UE number threshold is optimized for uplink
frequency selective scheduling. If this option is
deselected, the UE number threshold is not optimized
for uplink frequency selective scheduling. This option
HighOrderVMIMOSwitch: Indicates whether to
enable high order VMIMO. If this option is selected,
high order VMIMO is enabled. If this option is
deselected, high order VMIMO is disabled. This
option applies only to LTE TDD.
VMIMOReduceMCSRiseRBSwitch: Indicates
whether to perform uplink MU MIMO for UEs whose
MCS index is reduced in the downlink to increase the
number of available RBs in non-massive MIMO
scenarios, or whether the beam determination criteria
are loosened up for uplink MU MIMO pairing in
massive MIMO scenarios. In non-massive MIMO
scenarios: (1) If this option is selected, uplink MU
MIMO can be performed for UEs whose MCS index
is reduced to increase the number of available RBs.
(2) If this option is deselected, uplink MU MIMO
cannot be performed for UEs whose MCS index is
reduced to increase the number of available RBs. In
massive MIMO scenarios: (1) If the option is selected,
the eNodeB loosens up the beam determination
criteria for uplink MU MIMO pairing. (2) If this
option is deselected, the eNodeB does not loosen up
such criteria. This option applies only to LTE TDD.
VoLTEUeVmimoSwitch: Indicates whether VMIMO
pairing is performed for VoLTE UEs. If this option is

eRAN

nd
selected, VMIMO pairing is performed for VoLTE

UEs. If this option is deselected, VMIMO pairing is
not performed for VoLTE UEs. This option applies
only to LTE TDD.
TtiBundlingForVideoSwitch: Indicates whether to
enable TTI bundling for UEs running video services
in weak coverage areas. If this option is selected, TTI
bundling is enabled for UEs running video services in
weak coverage areas, improving video service
coverage at the cell edge. If this option is deselected,
TTI bundling is disabled for UEs running video
services in weak coverage areas. This option applies
only to LTE FDD.
GUI Value Range: SpsSchSwitch(SpsSchSwitch),
SinrAdjustSwitch(SinrAdjustSwitch),
PreAllocationSwitch(PreAllocationSwitch),
UlVmimoSwitch(UlVmimoSwitch),
TtiBundlingSwitch(TtiBundlingSwitch),
SmartPreAllocationSwitch(SmartPreAllocationS-
witch), PuschDtxSwitch(PuschDtxSwitch),
UlIblerAdjustSwitch(UlIblerAdjustSwitch),
UlEnhancedFssSwitch(UlEnhancedFssSwitch),
UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch),
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerS-
witch), UlIicsAlgoSwitch(UlIicsAlgoSwitch),
UlMinGbrSwitch(UlMinGbrSwitch),
UlMbrCtrlSwitch(UlMbrCtrlSwitch),
MbrUlSchSwitch(MbrUlSchSwitch),
UeAmbrUlSchSwitch(UeAmbrUlSchSwitch),
UlEnhancedDopplerSwitch(UlEnhancedDopplerS-
witch), UlRaUserSchOptSw(UlRaUserSchOptSw),
UlLast2RetransSchOptSwitch(UlLast2RetransSchOpt
Switch), UlInterfFssSwitch(UlInterfFssSwitch),
UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEf-
ficiencyOptSw), PuschUsePucchRbS-
witch(PuschUsePucchRbSwitch), PuschDtxSchOptS-
witch(PuschDtxSchOptSwitch),
ULFSSAlgoSwitch(ULFSSAlgoSwitch),
PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw),
UlFssUserThdStSwitch(UlFssUserThdStSwitch),
HighOrderVMIMOSwitch(HighOrderVMIMOS-
witch), VMIMOReduceMCSRiseRBS-
witch(VMIMOReduceMCSRiseRBSwitch),
VoLTEUeVmimoSwitch(VoLTEUeVmimoSwitch),
TtiBundlingForVideoSwitch(TtiBundlingForVideoS-
witch)

eRAN

nd
Unit: None
Actual Value Range: SpsSchSwitch,
SinrAdjustSwitch, PreAllocationSwitch,
UlVmimoSwitch, TtiBundlingSwitch,
SmartPreAllocationSwitch, PuschDtxSwitch,
UlIblerAdjustSwitch, UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,
UlIicsAlgoSwitch, UlMinGbrSwitch,
UlMbrCtrlSwitch, MbrUlSchSwitch,
UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch,
UlRaUserSchOptSw, UlLast2RetransSchOptSwitch,
UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch, PuschDtxSchOptSwitch,
ULFSSAlgoSwitch, PrachRbReuseSwitch,
SrSchDataAdptSw, UlFssUserThdStSwitch,
HighOrderVMIMOSwitch, VMIMOReduceMCSRi-
seRBSwitch, VoLTEUeVmimoSwitch,
TtiBundlingForVideoSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
SmartPreAllocationSwitch:On, PuschDtxSwitch:On,
UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:On, SchedulerCtrlPowerS-
witch:Off, UlIicsAlgoSwitch:Off,
UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off,
MbrUlSchSwitch:Off, UeAmbrUlSchSwitch:Off,
UlEnhancedDopplerSwitch:On,
UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:On,
UlInterfFssSwitch:Off, UlSmallRBSpectralEf-
fOptSw:Off, PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off, HighOrderVMIMOS-
witch:Off, VMIMOReduceMCSRiseRBSwitch:Off,
VoLTEUeVmimoSwitch:Off, TtiBundlingForVideoS-
witch:Off

eRAN

nd
CellAlg DlSchS MOD LOFD-1 Traffic Meaning:

oSwitch witch CELLA 10205/ Model Indicates whether to enable downlink scheduling
LGOSW TDLOF Based algorithms in a cell. This parameter includes the
ITCH D-11022 Perform following options:
LST 7 ance
CELLA LOFD-0 Optimiz FreqSelSwitch: Indicates whether to enable
LGOSW 01016/ ation frequency-selective scheduling. If this option is
ITCH TDLOF VoIP selected, data is transmitted on the frequency band of
D-00101 Semi- high channel quality. This option applies only to LTE
6 persisten FDD and LTE TDD.
LBFD-0 t
SpsSchSwitch: Indicates whether to enable semi-
0101502 Scheduli
persistent scheduling during talk spurts of VoLTE
/ ng
services. If this option is selected, semi-persistent
TDLBF Dynami scheduling is applied during talk spurts of VoLTE
D-00101 c services. If this option is deselected, dynamic
502 Scheduli scheduling is applied during talk spurts of VoLTE
ng services. This option applies only to LTE FDD and
LOFD-0
01109/ DL LTE TDD.
TDLOF Non-
MBSFNShutDownSwitch: Indicates whether to
D-00110 GBR
enable Multimedia Broadcast multicast service Single
9 Packet
Frequency Network (MBSFN) subframe shutdown. If
Bundlin
LOFD-0 this option is selected, MBSFN subframe shutdown is
g
01070/ applied. If this option is deselected, MBSFN subframe
TDLOF Symbol shutdown is not applied. This option takes effect only
D-00107 Power if the SymbolShutdownSwitch option of the
0 Saving PowerSaveSwitch parameter is selected. If the
TDLOF Scheduli MBSFNShutDownSwitch option is selected, the
D-07022 ng setting of the switch for mapping SIBs to SI messages
2/ Based becomes invalid. If the MBSFNShutDownSwitch
LOFD-1 on Max option is deselected, the setting of the switch for
31213 Bit Rate mapping SIBs to SI messages becomes valid. The
MBSFNShutDownSwitch option applies only to LTE-
LBFD-0 Basic
only base stations. This option applies only to LTE
02025/ Scheduli
FDD and LTE TDD.
TDLBF ng
D-00202 Aperiodi NonGbrBundlingSwitch: Indicates whether to enable
5 c CQI downlink non-GBR packet bundling. If this option is
LBFD-0 Reportin selected, delay of non-GBR services can be controlled
02031/ g in non-congestion scenarios. If this option is
TDLBF MBR>G deselected, delay of non-GBR services cannot be
D-00203 BR controlled. This option applies only to LTE FDD and
1 Configu LTE TDD.
LBFD-0 ration EnAperiodicCqiRptSwitch: Indicates whether to

70102/ Enhance enable enhanced aperiodic channel quality indicator
TDLBF d DL (CQI) reporting. If this option is selected, the eNodeB
D-07010 Frequen triggers aperiodic CQI reporting for a UE based on
2 cy downlink services of the UE and the interval at which

eRAN

nd
LBFD-0 Selectiv the UE sends periodic CQI reports. If this option is

60103 e deselected, UEs under non-frequency-selective
LOFD-0 Scheduli scheduling do not trigger aperiodic CQI reporting
81218 ng based on downlink services and trigger an aperiodic
Enhance CQI reporting if no valid periodic CQI reports are sent
LTROF in eight consecutive periodic CQI reporting periods.
D-11120 d
Extende This option applies only to LTE FDD and LTE TDD.
4/
TDLOF d QCI DlMbrCtrlSwitch: Indicates whether to enable
D-12110 MCPTT downlink scheduling based on the maximum bit rate
6 Voice (MBR) and guaranteed bit rate (GBR) on GBR
TDLBF Manage bearers. If this option is selected, the eNodeB
D-00200 ment performs downlink scheduling on GBR bearers based
5 DL on the MBR and GBR. If this option is deselected, the
Asynchr eNodeB performs downlink scheduling on GBR
LBFD-0 bearers based on the GBR only. This option applies
60101 onous
HARQ only to LTE FDD and LTE TDD.
LBFD-0
60103/ Optimiz MbrDlSchSwitch: Indicates whether the eNodeB
TDLBF ation of performs downlink scheduling based on MBR. If this
D-08010 CQI option is selected, the eNodeB prioritizes UEs based
2 Reportin on the MBRs during downlink scheduling. This
g parameter applies only to LTE FDD and LTE TDD.
LEOFD-
111305 Enhance UeAmbrDlSchSwitch: Indicates whether the eNodeB
d DL performs downlink scheduling based on per UE
LEOFD- Frequen aggregate maximum bit rates (UE-AMBRs). If this
111307 cy option is selected, the eNodeB prioritizes UEs based
TDLOF Selectiv on the UE-AMBRs during downlink scheduling. This
D-12110 e option applies only to LTE FDD and LTE TDD.
5 Scheduli
ng EpfEnhancedSwitch: Indicates whether to enable
enhanced proportional fair (EPF) enhancement for
Virtual
scheduling. EPF enhancement for scheduling is
4T4R
enabled only if this option is selected. This option
eMIMO applies only to LTE FDD and LTE TDD.
RRC AperiodicCqiTrigOptSwitch: Indicates whether to
and optimize triggering of aperiodic CQI reporting. If this
DRX option is selected, a UE performing initial access
Policy triggers aperiodic CQI reporting based on related
for trigger conditions after the DLMAC instance has been
Public established for 200 ms and the eNodeB receives
Safety MSG5. Consider that aperiodic CQI reporting is
triggered by invalid CQI reports in eight consecutive
CQI reporting periods. If cyclic redundancy check
(CRC) on aperiodic CQI reports fails, aperiodic CQI
reporting is not repeatedly triggered when DRX is
enabled; or aperiodic CQI reporting is triggered after
eight TTIs when DRX is disabled. If this option is
deselected, a UE performing initial access triggers

eRAN

nd
aperiodic CQI reporting based on related trigger

conditions after the DLMAC instance has been
established for 200 ms. Consider that aperiodic CQI
reporting is triggered by invalid CQI reports in eight
consecutive CQI reporting periods. If CRC on
aperiodic CQI reports fails, aperiodic CQI reporting is
triggered after eight TTIs, regardless of the DRX
status. This option applies only to LTE FDD and LTE
TDD.
VoipTbsBasedMcsSelSwitch: Indicates whether the
modulation and coding scheme (MCS) index is
selected based on the transport block size (TBS) in
downlink scheduling for VoLTE services. The MCS
index is selected based on the TBS in downlink
dynamic scheduling for VoLTE services only if this
option is selected. This option applies only to LTE
FDD and LTE TDD.
PagingInterfRandSwitch: Indicates whether to enable
interference randomization for paging messages. If
this option is selected, interference randomization is
enabled for paging messages. This option applies only
DlSingleUsrMcsOptSwitch: Indicates conditions for
lowering the MCS index for a single UE. If this option
is selected, the MCS index can be lowered for a UE if
the UE is the only UE to be scheduled in a
transmission time interval (TTI). If this option is
deselected, the MCS index can be lowered for a UE if
the threshold for the function of lowering the MCS
index to increase the number of RBs is reached and
the UE is the only UE to be scheduled in a TTI. This
UeSigMcsEnhanceSwitch: Indicates whether to
enable MCS optimization for UE signaling. If this
option is selected, MCS optimization for UE signaling
is enabled. For LTE FDD, the MCS index for UE
signaling is the same as the MCS index for data. For
LTE TDD, the MCS index for UE signaling is lowered
based on the MCS index for data. If this option is
deselected, a fixed low MCS index is used for UE
signaling. This option applies only to LTE FDD and
LTE TDD.
SubframeSchDiffSwitch: For TDD cells, this option
indicates whether to perform scheduling in subframes
3 and 8 based on the policy of increasing the number
of UEs scheduled in the uplink when uplink-downlink

eRAN

nd
configuration 2 is used. If this option is selected,

scheduling in subframes 3 and 8 is performed based
on the policy of increasing the number of UEs
scheduled in the uplink when uplink-downlink
configuration 2 is used. If this option is deselected, the
scheduling policy used in subframes 3 and 8 is the
same as that used in other downlink subframes when
uplink-downlink configuration 2 is used. For NB-IoT
cells, this option indicates whether to enable
scheduling priority optimization. If this option is
deselected, the scheduling priority of downlink
services is higher than that of uplink services for UEs
for which control plane CIoT EPS optimization is
used. If this option is selected, the scheduling priority
of downlink services is the same as that of uplink
services for UEs for which control plane CIoT EPS
optimization is used. This option applies only to LTE
TDD and NB-IoT.
TailPackagePriSchSwitch: Indicates whether to enable
scheduling of downlink connected tail packages in the
bearer. If this option is selected, the connected tail
package is scheduled preferentially in the next TTI,
which reduces the delay and increases the
transmission rate. If this option is deselected, the
scheduling policy of the connected tail package is the
same as other downlink subframes. This option
applies only to LTE TDD.
SIB1InterfRandSwitch: Indicates whether to enable
SIB1 interference randomization. If this option is
selected, interference randomization is enabled for
SIB1. This option applies only to LTE TDD.
FreqSelJudgeIgnorDopplerSwitch: Indicates whether
to ignore Doppler conditions. If this option is selected,
Doppler conditions are ignored during frequency
selective channel determination. If this option is
deselected, Doppler conditions are considered during
frequency selective channel determination. This
parameter applies only to LTE FDD and LTE TDD.
EnhExtQCISpsSchSwitch: Indicates whether to
enable semi-persistent scheduling during talk spurts of
PTT services with standardized QCI 65, standardized
QCI 66, or an enhanced extended QCI. If this option
is selected, semi-persistent scheduling is applied. If
this option is deselected, dynamic scheduling is
applied. This option applies only to LTE FDD and
LTE TDD.

eRAN

nd
DlVoipBundlingSwitch: Indicates whether to enable

active packet bundling for downlink VoLTE services.
Active packet bundling is enabled for downlink
VoLTE services only if this option is selected. If this
option is selected, PDCCH resources can be saved for
downlink data services or uplink services, thereby
increasing the VoLTE capacity for VoLTE services or
increasing the throughput of data services in mixed
service scenarios. However, the delay in VoLTE voice
packet scheduling will increase in the downlink and
MOSs may decrease. You are advised to deselect this
option if you prefer VoLTE performance and do not
expect MOS reduction. This option applies only to
DlPacketLenAwareSchSw: Indicates whether to
enable packet length awareness performance
optimization in the downlink. Packet length awareness
performance optimization is enabled in the downlink
only if this option is selected. This option applies only
RLCArqFeedbackEnhancedSwitch: Indicates whether
to modify HARQ feedback results based on RLC
status reports when uplink-downlink configuration 2
is used. If this option is selected, the eNodeB modifies
HARQ feedback results based on RLC status reports
after receiving the reports. This prevents unnecessary
HARQ retransmissions. This option applies only to
LTE TDD.
PaReconfigOptSwitch: Indicates whether to enable PA
reconfiguration optimization. The optimization is
enabled when this option is selected. This option
RankRapidRptSwitch: Indicates whether to enable fast
rank reporting. If this option is selected, an aperiodic
CQI reporting is immediately triggered after
successful network access. If this option is deselected,
an aperiodic CQI reporting is not immediately
triggered after successful network access. This option
DlRLCStateReportSchDelaySw: Indicates whether to
enable optimization on the delay-based scheduling of
downlink RLC status reports. The optimization is
enabled when this option is selected. This option
SmallPktMcsSelectAlgoSw: Indicates whether to
enable MCS selection for small packets. If this option

eRAN

nd
is selected, the scheduler selects an MCS with a lower

index based on the amount of data to be initially
transmitted and the allocated TBS in each TTI on
condition that the allocated TB can carry the data. The
function is enabled only if this option is selected. This
SRB0SplitSchSw: Indicates whether to enable

separate scheduling of SRB0 and contention
resolution MCE. If this option is selected, SRB0 and
contention resolution MCE are separately scheduled.
BfUserPairPriorSwitch: Indicates whether to

preferentially allocate resources to paired
beamforming UEs for UE pairing features such as MU
beamforming and D-MIMO. If this option is selected,
the eNodeB preferentially allocates resources to
paired beamforming UEs for UE pairing features such
as MU beamforming and D-MIMO. This option
HarqAllocOptSwitch: Indicates whether to optimize

the allocation of HARQ processes. If this option is
selected, the downlink UE rate increases. This option
takes effect only when D-MIMO or massive MIMO is
enabled. This option applies only to LTE TDD.
Pusch32Switch: Indicates whether to enable the

PUSCH 3-2 feedback mode. If this option is selected,
UEs that support the PUSCH 3-2 feedback mode use
this mode to aperiodically report CQIs. If this option
is deselected, the mode cannot be used. This option
applies only to LTE FDD.
DlPreciseAmbrCtrlSwitch: Indicates whether to

enable precise downlink AMBR control. If this option
is selected, a more accurate optimization algorithm
applies to the AMBR control, which achieves more
accurate AMBR control. If this option is deselected,
the original AMBR control algorithm is used. This
GUI Value Range: FreqSelSwitch(FreqSelSwitch),
SpsSchSwitch(SpsSchSwitch),
MBSFNShutDownSwitch(MBSFNShutDownSwitch),
NonGbrBundlingSwitch(NonGbrBundlingSwitch),
EnAperiodicCqiRptSwitch(EnAperiodicCqiRptS-
witch), DlMbrCtrlSwitch(DlMbrCtrlSwitch),
MbrDlSchSwitch(MbrDlSchSwitch),
UeAmbrDlSchSwitch(UeAmbrDlSchSwitch),

eRAN

nd
EpfEnhancedSwitch(EpfEnhancedSwitch),
AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptS-
witch), VoipTbsBasedMcsSelS-
witch(VoipTbsBasedMcsSelSwitch),
PagingInterfRandSwitch(PagingInterfRandSwitch),
DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptS-
witch), SubframeSchDiffSwitch(SubframeSchDiffS-
witch), TailPackagePriSchS-
witch(TailPackagePriSchSwitch),
UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch),
FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnor-
DopplerSwitch),
SIB1InterfRandSwitch(SIB1InterfRandSwitch),
EnhExtQCISpsSchSwitch(EnhExtQCISpsSchSwitch),
DlVoipBundlingSwitch(DlVoipBundlingSwitch),
DlPacketLenAwareSchSw(DlPacketLenAwar-
eSchSw), RLCArqFeedbackEnhanced-
Switch(RLCArqFeedbackEnhancedSwitch),
PaReconfigOptSwitch(PaReconfigOptSwitch),
RankRapidRptSwitch(RankRapidRptSwitch),
DlRLCStateReportSchDe-
laySw(DlRLCStateReportSchDelaySw),
SmallPktMcsSelectAlgoSw(SmallPktMcsSelectAl-
goSw), SRB0SplitSchSw(SRB0SplitSchSw),
BfUserPairPriorSwitch(BfUserPairPriorSwitch),
HarqAllocOptSwitch(HarqAllocOptSwitch),
Pusch32Switch(Pusch32Switch),
DlPreciseAmbrCtrlSwitch(DlPreciseAmbrCtrlSwitch)
Unit: None
Actual Value Range: FreqSelSwitch, SpsSchSwitch,
MBSFNShutDownSwitch, NonGbrBundlingSwitch,
EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch,
MbrDlSchSwitch, UeAmbrDlSchSwitch,
EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch,
VoipTbsBasedMcsSelSwitch, PagingInterfRand-
Switch, DlSingleUsrMcsOptSwitch,
SubframeSchDiffSwitch, TailPackagePriSchSwitch,
UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop-
plerSwitch, SIB1InterfRandSwitch,
EnhExtQCISpsSchSwitch, DlVoipBundlingSwitch,
DlPacketLenAwareSchSw, RLCArqFeedbackEnhan-
cedSwitch, PaReconfigOptSwitch,
RankRapidRptSwitch, DlRLCStateReportSchDe-
laySw, SmallPktMcsSelectAlgoSw, SRB0SplitSchSw,
BfUserPairPriorSwitch, HarqAllocOptSwitch,
Pusch32Switch, DlPreciseAmbrCtrlSwitch
Default Value: FreqSelSwitch:Off, SpsSchSwitch:Off,
MBSFNShutDownSwitch:Off, NonGbrBundlingS-

eRAN

nd
witch:Off, EnAperiodicCqiRptSwitch:Off,
DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off,
UeAmbrDlSchSwitch:Off, EpfEnhancedSwitch:Off,
AperiodicCqiTrigOptSwitch:On, VoipTbsBasedMcs-
SelSwitch:On, PagingInterfRandSwitch:Off,
DlSingleUsrMcsOptSwitch:Off, SubframeSchDiffS-
witch:Off, TailPackagePriSchSwitch:Off,
UeSigMcsEnhanceSwitch:Off, FreqSelJudgeIgnor-
DopplerSwitch:Off, SIB1InterfRandSwitch:On,
EnhExtQCISpsSchSwitch:Off, DlVoipBundlingS-
witch:Off, DlPacketLenAwareSchSw:Off,
RLCArqFeedbackEnhancedSwitch:Off,
PaReconfigOptSwitch:Off, RankRapidRptSwitch:Off,
DlRLCStateReportSchDelaySw:Off,
SmallPktMcsSelectAlgoSw:Off,
SRB0SplitSchSw:Off, BfUserPairPriorSwitch:Off,
HarqAllocOptSwitch:Off, Pusch32Switch:Off,
DlPreciseAmbrCtrlSwitch:Off
CellWtt PrbUpLi MOD LOFD-1 WBB Meaning: Indicates the PRB threshold control mode.
xParaCf mitCtrl CELLW 10223/ User This parameter provides the TIGHT_CONTROL and
g Mode TTXPA TDLOF Steering MBB_LOOSE_CONTROL modes. When this
RACFG D-11022 Manage parameter is set to TIGHT_CONTROL, the upper
LST 3 ment limit of PRB resources for WBB and MBB UEs are
CELLW subject to the uplink and downlink PRB threshold
TTXPA policies. That is, the PRB resources for WBB and
RACFG MBB UEs must not exceed the upper limit even if
there are spare PRB resources. When this parameter is
set to MBB_LOOSE_CONTROL, the PRB resources
for MBB UEs can exceed the preset upper limit if
PRB resources are not exhausted after meeting the
requirements for scheduling WBB UEs. In this
situation, MBB UEs are allowed to use spare PRB
resources in the cell. The TIGHT_CONTROL policy
still applies to WBB UEs. This parameter applies only
GUI Value Range: TIGHT_CONTROL,
MBB_LOOSE_CONTROL
Unit: None
Actual Value Range: TIGHT_CONTROL,
MBB_LOOSE_CONTROL
Default Value: MBB_LOOSE_CONTROL

eRAN

nd
CellAlg CamcS MOD TDLOF Intra- Meaning:

oSwitch witch CELLA D-11020 eNodeB Indicates whether to enable coordinated AMC for a
LGOSW 5 Uplink cell.
ITCH TDLOF Coordin
LST D-11020 ated UlCamcSw: Indicates whether to enable uplink
CELLA 6 Scheduli coordinated AMC for a cell. This option applies only
LGOSW ng to LTE TDD.
ITCH Inter- UlInterEnbCamcSw: Indicates whether to enable
eNodeB uplink inter-eNodeB coordinated AMC for a cell. This
Uplink option applies only to LTE TDD.
Coordin
ated GUI Value Range: UlCamcSw(UlCamcSw),
Scheduli UlInterEnbCamcSw(UlInterEnbCamcSw)
ng Unit: None
Actual Value Range: UlCamcSw, UlInterEnbCamcSw
Default Value: UlCamcSw:Off,
UlInterEnbCamcSw:Off

eRAN

nd
CellAlg DlComp MOD TDLAO Inter- Meaning:

oSwitch Switch CELLA FD-081 eNodeB Indicates whether to enable the DL CoMP algorithm.
LGOSW 411 DL
ITCH LAOFD CoMP If the IntraDlCompSwitch option is selected and the
LST -120201 Based InterDlCompDcsSwitch and InterDlCompCbfSwitch
CELLA on options are deselected, intra-BBP adaptive DL CoMP
LGOSW Relaxed is enabled, and the eNodeB adaptively selects DCS,
ITCH Backhau CBF, or JT as the transmission mode.
l
If the IntraDlCompSwitch and InterDlCompDcsS-
DL witch options are selected and the InterDlCompCbfS-
CoMP witch option is deselected, intra-BBP adaptive DL
CoMP, inter-BBP DCS, and inter-eNodeB DCS are
enabled.
If the IntraDlCompSwitch, InterDlCompDcsSwitch,
and InterDlCompCbfSwitch options are selected,
intra-BBP adaptive DL CoMP, inter-BBP adaptive DL
CoMP, and inter-eNodeB adaptive DL CoMP are
enabled.
In inter-BBP and inter-eNodeB adaptive DL CoMP,
the eNodeB adaptively selects DCS or CBF as the
transmission mode. The IntraDlCompSwitch,
InterDlCompDcsSwitch, and InterDlCompCbfSwitch
options apply only to LTE TDD.
FDDHomNetDlCompSwitch: Indicates whether to
enable DL CoMP in a homogeneous network
(consisting of only macro or micro cells) under a
Cloud BB architecture. DL CoMP is enabled in such a
network only if this option is selected. This option
FDDHetNetDlCompSwitch: Indicates whether to
enable DL CoMP in a heterogeneous network
(consisting of macro and micro cells) under a Cloud
BB architecture. DL CoMP is enabled in such a
network only if this option is selected. This option
IntraDlCompJtSwitch: Indicates whether to enable the
intra-eNodeB SU-JT algorithm. If this option is
selected, intra-BBP SU-JT is enabled. If this option is
deselected, intra-BBP SU-JT is disabled. This option
GUI Value Range:
IntraDlCompSwitch(IntraDlCompSwitch),
InterDlCompDcsSwitch(InterDlCompDcsSwitch),
InterDlCompCbfSwitch(InterDlCompCbfSwitch),
FDDHomNetDlCompSwitch(FDDHomNetDlCompS-

eRAN

nd
witch), FDDHetNetDlCompS-
witch(FDDHetNetDlCompSwitch),
IntraDlCompJtSwitch(IntraDlCompJtSwitch)
Unit: None
Actual Value Range: IntraDlCompSwitch,
InterDlCompDcsSwitch, InterDlCompCbfSwitch,
FDDHomNetDlCompSwitch, FDDHetNetDlCompS-
witch, IntraDlCompJtSwitch
Default Value: IntraDlCompSwitch:Off,
InterDlCompDcsSwitch:Off, InterDlCompCbfS-
witch:Off, FDDHomNetDlCompSwitch:Off,
FDDHetNetDlCompSwitch:Off,
IntraDlCompJtSwitch:Off
CspcAlg CspcAlg MOD LOFD-0 Coordin Meaning: Indicates whether to enable CSPC in cells
oPara oSwitch CSPCA 70208 ated under the centralized control node in Cloud BB
LGOPA TDLOF Scheduli scenarios. This parameter applies only to LTE FDD.
RA D-08020 ng based GUI Value Range: OFF(Off), ON(On)
LST 3 Power
Control Unit: None
CSPCA
LGOPA Coordin Actual Value Range: OFF, ON
RA ated Default Value: OFF(Off)
Scheduli
ng based
Power
Control

eRAN

nd
CellAlg MuBfAl MOD TDLOF MU- Meaning:

oSwitch goSwitc CELLA D-00107 Beamfor Indicates whether to enable multi-user beamforming
h LGOSW 7 ming (MU beamforming). This parameter is valid only if
ITCH TDLOF DL 4- the BfSwitch option of the BfAlgoSwitch parameter is
LST D-11022 Layer selected.
CELLA 1 MU-
LGOSW Beamfor MuBfSwitch: Indicates whether to enable MU
TDLEO beamforming in the downlink for a cell. If this option
ITCH FD-121 ming
is selected, MU beamforming in the downlink is
604 DL 8- enabled for a cell (or an SFN physical cell). If this
TDLEO Layer option is deselected, MU beamforming in the
FD-121 MU- downlink is disabled for a cell (or an SFN physical
605 Beamfor cell). This option applies only to LTE TDD.
ming
TDLOF TM9MuBfSwitch: Indicates whether to enable MU
D-13020 DL 16-
Layer beamforming in the downlink for closed-loop TM9
2 UEs in a cell. The setting of this option takes effect
MU-
TDLEO Beamfor only when the MuBfSwitch option of this parameter
FD-131 ming or the SfnCbfSwitch option of the SfnAlgoSwitch
612 parameter is selected. If this option is selected, the
WTTx MuBfSwitch option of this parameter or the
Turbo SfnCbfSwitch option of the SfnAlgoSwitch parameter
Beamfor is selected, and the TM9Switch option of the
ming EnhMIMOSwitch parameter is selected, MU
Multi- beamforming in the downlink is enabled for closed-
User loop TM9 UEs in a cell. If this option is deselected in
Split non-multi-user split SDMA scenarios, MU
SDMA beamforming in the downlink is disabled for closed-
in loop TM9 UEs in a cell. This option applies only to
Massive LTE TDD.
MIMO
HighOrderMubfSwitch: Indicates whether to enable
high-order MU beamforming for a cell. The setting of
this option takes effect only when the MuBfSwitch
option of this parameter or the SfnCbfSwitch option
of the SfnAlgoSwitch parameter is selected. If this
option is selected and the MuBfSwitch option of this
parameter or the SfnCbfSwitch option of the
SfnAlgoSwitch parameter is selected, high-order MU
beamforming in the downlink is enabled for a cell. If
this option is deselected, high-order MU beamforming
is disabled for a cell.
MubfResAdjSwitch: Indicates whether to enable MU
beamforming resource adjustment. The setting of this
option takes effect only when the MuBfSwitch option
of this parameter or the SfnCbfSwitch option of the
SfnAlgoSwitch parameter is selected. If this option is
selected and the MuBfSwitch option of this parameter
or the SfnCbfSwitch option of the SfnAlgoSwitch

eRAN

nd
parameter is selected, downlink resource adjustment

for MU beamforming is enabled for the cell. If this
option is deselected, downlink resource adjustment for
MU beamforming is disabled for the cell. This option
HarqRetranPairSwitch: Indicates whether to enable
MU beamforming for UEs subjected to HARQ
retransmissions. This option is valid only if the
MuBfSwitch option of this parameter is selected. If
both the MuBfSwitch option and this option are
selected, MU beamforming is enabled for UEs
subjected to HARQ retransmissions in the cell. If this
option is deselected, MU beamforming is disabled for
UEs subjected to HARQ retransmissions in the cell.
This option applies only to LTE TDD.
SplitSdmaSwitch: Indicates whether to enable split
SDMA for massive MIMO cells. If this option is
selected, adaptation between MU beamforming and
split SDMA for the PDSCH is supported. If this
option is deselected, split SDMA for the PDSCH is
not supported. This option applies only to LTE TDD.
TurboBfSwitch: Indicates whether to enable turbo
beamforming in WTTx scenarios. If both this option
and the MuBfSwitch option of this parameter are
selected, turbo beamforming takes effect in 8T8R
normal cells.
GUI Value Range: MuBfSwitch(MuBfSwitch),
TM9MuBfSwitch(TM9MuBfSwitch),
HighOrderMubfSwitch(HighOrderMubfSwitch),
MubfResAdjSwitch(MubfResAdjSwitch),
HarqRetranPairSwitch(HarqRetranPairSwitch),
SplitSdmaSwitch(SplitSdmaSwitch),
TurboBfSwitch(TurboBfSwitch)
Unit: None
Actual Value Range: MuBfSwitch, TM9MuBfSwitch,
HighOrderMubfSwitch, MubfResAdjSwitch,
HarqRetranPairSwitch, SplitSdmaSwitch,
TurboBfSwitch
Default Value: MuBfSwitch:Off,
TM9MuBfSwitch:Off, HighOrderMubfSwitch:Off,
MubfResAdjSwitch:Off, HarqRetranPairSwitch:Off,
SplitSdmaSwitch:Off, TurboBfSwitch:Off

eRAN

nd
ENodeB AnrSwit MOD LOFD-0 Automat Meaning:

AlgoSwi ch ENODE 02001/ ic Indicates whether to enable automatic neighbor
tch BALGO TDLOF Neighbo relation (ANR). This parameter provides the following
SWITC D-00200 ur options:
H 1 Relation
LST LOFD-0 (ANR) IntraRatEventAnrSwitch: If this option is selected,
ENODE 02002/ Inter- intra-RAT event-triggered ANR is enabled. This type
BALGO TDLOF RAT of ANR sets up and optimizes intra-RAT neighbor
SWITC D-00200 ANR relationships based on coverage-based intra-RAT
H 2 handover events. This option applies only to LTE
FDD and LTE TDD.
IntraRatFastAnrSwitch: If this option is selected,
intra-RAT fast ANR is enabled. This type of ANR sets
up and optimizes intra-RAT neighbor relationships
based on periodic intra-RAT measurement. This
IntraRatAnrAutoDelSwitch: If both this option and
the IntraRatEventAnrSwitch option are selected, and
the NoRmvFlag parameter is set to
PERMIT_RMV_ENUM for an intra-RAT neighboring
cell, the eNodeB can automatically remove intra-RAT
neighbor relationships. If the IntraRatAnrAutoDelS-
witch option is deselected, the eNodeB cannot
automatically remove intra-RAT neighbor
relationships. This option applies only to LTE FDD
and LTE TDD.
UtranEventAnrSwitch: If this option is selected,
event-triggered ANR with UTRAN is enabled. This
type of ANR sets up and optimizes inter-RAT
neighbor relationships with UTRAN cells based on
events for coverage-based handovers to UTRAN. This
GeranEventAnrSwitch: If this option is selected,
event-triggered ANR with GERAN is enabled. This
neighbor relationships with GERAN cells based on
events for coverage-based handovers to GERAN. This
UtranFastAnrSwitch: If this option is selected, fast
ANR with UTRAN is enabled. This type of ANR sets
up and optimizes inter-RAT neighbor relationships
with UTRAN cells based on periodic UTRAN
measurement. UEs measure only neighboring cells
contained in measurement configurations, in which
the eNodeB does not include external UTRAN cells.
To enable external neighboring UTRAN cells added

eRAN

nd
by fast ANR to be selected for handovers, you are

advised to select the UtranEventAnrSwitch option at
the same time. This option applies only to LTE FDD
and LTE TDD.
GeranFastAnrSwitch: If this option is selected, fast
ANR with GERAN is enabled. This type of ANR sets
with GERAN cells based on periodic GERAN
measurement. This option applies only to LTE FDD
and LTE TDD.
CdmaFastAnrSwitch: If this option is selected, fast
ANR with CDMA is enabled. This type of ANR sets
with CDMA cells based on periodic CDMA
measurement. This option applies only to LTE FDD
and LTE TDD.
UtranAutoNrtDeleteSwitch: If both this option and the
UtranEventAnrSwitch option are selected, the
eNodeB can automatically remove inter-RAT
neighbor relationships with UTRAN cells for which
PERMIT_RMV_ENUM. If this option is deselected,
the eNodeB cannot automatically remove neighbor
relationships with UTRAN cells. This option applies
GeranAutoNrtDeleteSwitch: If both this option and
the GeranEventAnrSwitch option are selected, the
neighbor relationships with GERAN cells for which
relationships with GERAN cells. This option applies
CdmaAutoNrtDeleteSwitch: If both this option and
the CdmaEventAnrSwitch option are selected, the
neighbor relationships with CDMA cells for which the
NoRmvFlag parameter is set to
relationships with CDMA cells. This option applies
CdmaEventAnrSwitch: If this option is selected,
event-triggered ANR with CDMA is enabled. This

eRAN

nd

neighbor relationships with CDMA cells based on
events for handovers to CDMA. This option applies
MlbBasedEventAnrSwitch: Indicates whether to
enable MLB-based event-triggered ANR. If both this
option and the IntraRatEventAnrSwitch option are
selected, the eNodeB can automatically set up and
optimize inter-frequency neighbor relationships based
on inter-frequency MLB measurement. If both this
option and the option for event-triggered inter-RAT
ANR (UtranEventAnrSwitch or
GeranEventAnrSwitch) are selected, the eNodeB can
automatically set up and optimize neighbor
relationships with cells of that RAT based on
measurement for MLB to that RAT. If this option is
deselected, the eNodeB does not set up or optimize
neighbor relationships based on MLB measurement.
IntraRatNoHoSetAnrSwitch: If both this option and
the IntraRatEventAnrSwitch option are selected, the
eNodeB automatically sets the NoHoFlag parameter
for intra-RAT neighbor relationships. If this option is
deselected, the eNodeB does not modify the
NoHoFlag parameter. When this option is selected,
pay attention to the neighboring cells for which the
NoHoFlag parameter is set to
FORBID_HO_ENUM(Forbid Ho) by ANR so as to
prevent any impact on handover performance. This
option takes effect only when the OptMode parameter
is set to FREE(FREE). This option applies only to
IntraRatDoubleThdAnrSwitch: If both this option and
eNodeB can automatically set up and optimize intra-
RAT neighbor relationships based on events for intra-
RAT ANR measurement. Configurations can ensure
that the probability of triggering intra-RAT ANR
measurement is higher than or equal to that of
triggering measurement for coverage-based
handovers. If this option is deselected, the eNodeB
cannot set up or optimize intra-RAT neighbor
relationships based on events for intra-RAT ANR
measurement. This option applies only to LTE TDD.
ServiceBasedEventAnrSwitch: If both this option and

eRAN

nd
eNodeB can set up and optimize intra-RAT inter-

frequency neighbor relationships based on service-
based inter-frequency handovers. If both this option
and the UtranEventAnrSwitch option are selected, the
eNodeB can set up and optimize neighbor
relationships with UTRAN cells based on service-
based handovers. This option applies only to LTE
FDD and LTE TDD.
ServiceReqEventAnrSwitch: If both this option and
eNodeB can set up and optimize intra-RAT inter-
frequency neighbor relationships based on service-
based inter-frequency handovers. This option applies
IntraRatEnhancedEventAnrSwitch: If this option is
selected, intra-RAT enhanced event-triggered ANR is
enabled. This type of ANR is triggered by events
other than coverage-based handovers, handovers for
MLB, service-based handovers, and service-request-
based handovers. When both this option and the
IntraRatEventAnrSwitch option are selected and the
frequency-specific ANR indicator is set to allow
ANR, the eNodeB can set up and optimize intra- and
inter-frequency neighbor relationships based on
corresponding handover events. If this option is
deselected, the eNodeB does not set up or optimize
neighbor relationships based on corresponding
handover events. This option applies only to LTE
FDD and LTE TDD.
InterFreqAngcAnrSwitch: Indicates whether to enable
ANGC-based event-triggered inter-frequency ANR. If
both this option and the IntraRatEventAnrSwitch
option are selected, the eNodeB automatically adds a
neighbor relationship with a neighboring cell detected
based on ANGC. This option applies only to LTE
FDD and LTE TDD.
CaBasedEventAnrSwitch: Indicates whether to enable
event-triggered ANR based on CA measurement. If
both this option and the IntraRatEventAnrSwitch
option are selected, the eNodeB can set up neighbor
relationships with cells detected during CA
measurement. In addition, when PCI confusions
occur, the eNodeB acquires ECGIs to identify target
cells. This option applies only to LTE FDD and LTE
TDD.

eRAN

nd
UtranUpdateRacSwitch: If this option is selected and

RAC is not configured for external UTRAN cells,
UEs retrigger CGI reading to obtain RAC upon
detecting that the cell provides strongest signals
during ANR. If this option is deselected, UEs do not
retrigger CGI reading to obtain RAC upon detecting
that the cell provides strongest signals during ANR.
GeranUpdateRacSwitch: If this option is selected and
RAC is not configured for external GERAN cells,
UEs retrigger CGI reading to obtain RAC upon
detecting that the cell provides strongest signals
during ANR. If this option is deselected, UEs do not
retrigger CGI reading to obtain RAC upon detecting
that the cell provides strongest signals during fast
ANR. This option applies only to LTE FDD and LTE
TDD.
GUI Value Range: IntraRatEventAnrS-
witch(IntraRatEventAnrSwitch), IntraRatFastAnrS-
witch(IntraRatFastAnrSwitch), IntraRatAnrAutoDelS-
witch(IntraRatAnrAutoDelSwitch),
UtranEventAnrSwitch(UtranEventAnrSwitch),
GeranEventAnrSwitch(GeranEventAnrSwitch),
UtranFastAnrSwitch(UtranFastAnrSwitch),
GeranFastAnrSwitch(GeranFastAnrSwitch),
CdmaFastAnrSwitch(CdmaFastAnrSwitch),
UtranAutoNrtDeleteSwitch(UtranAutoNrtDeleteS-
witch), GeranAutoNrtDeleteS-
witch(GeranAutoNrtDeleteSwitch),
CdmaAutoNrtDeleteSwitch(CdmaAutoNrtDeleteS-
witch),
CdmaEventAnrSwitch(CdmaEventAnrSwitch),
MlbBasedEventAnrSwitch(MlbBasedEventAnrS-
witch), IntraRatNoHoSetAnrS-
witch(IntraRatNoHoSetAnrSwitch),
IntraRatDoubleThdAnrSwitch(IntraRatDoubleTh-
dAnrSwitch), ServiceBasedEventAnrS-
witch(ServiceBasedEventAnrSwitch),
ServiceReqEventAnrSwitch(ServiceReqEventAnrS-
witch), IntraRatEnhancedEventAnrS-
witch(IntraRatEnhancedEventAnrSwitch),
InterFreqAngcAnrSwitch(InterFreqAngcAnrSwitch),
CaBasedEventAnrSwitch(CaBasedEventAnrSwitch),
UtranUpdateRacSwitch(UtranUpdateRacSwitch),
GeranUpdateRacSwitch(GeranUpdateRacSwitch)
Unit: None

eRAN

nd
Actual Value Range: IntraRatEventAnrSwitch,

IntraRatFastAnrSwitch, IntraRatAnrAutoDelSwitch,
UtranEventAnrSwitch, GeranEventAnrSwitch,
UtranFastAnrSwitch, GeranFastAnrSwitch,
CdmaFastAnrSwitch, UtranAutoNrtDeleteSwitch,
GeranAutoNrtDeleteSwitch, CdmaAutoNrtDeleteS-
witch, CdmaEventAnrSwitch, MlbBasedEventAnrS-
witch, IntraRatNoHoSetAnrSwitch,
IntraRatDoubleThdAnrSwitch, ServiceBasedEven-
tAnrSwitch, ServiceReqEventAnrSwitch,
IntraRatEnhancedEventAnrSwitch,
InterFreqAngcAnrSwitch, CaBasedEventAnrSwitch,
UtranUpdateRacSwitch, GeranUpdateRacSwitch
Default Value: IntraRatEventAnrSwitch:Off,
IntraRatFastAnrSwitch:Off, IntraRatAnrAutoDelS-
witch:On, UtranEventAnrSwitch:Off,
GeranEventAnrSwitch:Off, UtranFastAnrSwitch:Off,
GeranFastAnrSwitch:Off, CdmaFastAnrSwitch:Off,
UtranAutoNrtDeleteSwitch:On, GeranAutoNrtDele-
teSwitch:On, CdmaAutoNrtDeleteSwitch:On,
CdmaEventAnrSwitch:Off, MlbBasedEventAnrS-
witch:Off, IntraRatNoHoSetAnrSwitch:On,
IntraRatDoubleThdAnrSwitch:Off,
ServiceBasedEventAnrSwitch:Off,
ServiceReqEventAnrSwitch:Off, IntraRatEnhancedE-
ventAnrSwitch:Off, InterFreqAngcAnrSwitch:Off,
CaBasedEventAnrSwitch:On, UtranUpdateRacS-
witch:Off, GeranUpdateRacSwitch:Off

eRAN

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the ID of the operator.
atorTa atorId CNOPE 01036/ Sharing GUI Value Range: 0~5
RATOR TDLOF with
TA D-00103 Commo Unit: None
MOD 6 n Actual Value Range: 0~5

CNOPE MLOFD Carrier Default Value: None
RATOR -121251 NB-IoT
TA LOFD-0 RAN
LST 01037/ Sharing
CNOPE TDLOF with
RATOR D-00103 Commo
TA 7 n
Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4
NB-IoT
MLOFD RAN
-131253 Sharing
with
Dedicate
d
Carrier
Hybrid
RAN
Sharing
NB-IoT
Hybrid
RAN
Sharing

eRAN

nd
CellOp LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELLO identifies a cell within an eNodeB.
P GUI Value Range: 0~255
DSP Unit: None
CELLB
ROADC Actual Value Range: 0~255
ASTCN Default Value: None
OPERA
TOR
LST
CELLO
P
MOD
CELLO
P
RMV
CELLO
P

eRAN

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the ID of the operator.
ator atorId CNOPE 01036/ Sharing GUI Value Range: 0~5
RATOR TDLOF with
D-00103 Commo Unit: None
LST
CNOPE 6 n Actual Value Range: 0~5
RATOR MLOFD Carrier Default Value: None
MOD -121251 NB-IoT
CNOPE LOFD-0 RAN
RATOR 01037/ Sharing
TDLOF with
RMV Commo
CNOPE D-00103
7 n
RATOR Carrier
MLOFD
-121252 RAN
Sharing
MLOFD with
-131253 Dedicate
LOFD-0 d
01086/ Carrier
TDLOF NB-IoT
D-00108 RAN
6 Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4 NB-IoT
Hybrid
RAN
Sharing
RAN
Sharing
by More
Operator
s
Hybrid
RAN
Sharing

eRAN

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the name of the operator.
ator atorNam CNOPE 01036/ Sharing GUI Value Range: 1~32 characters
e RATOR TDLOF with
D-00103 Commo Unit: None
MOD
CNOPE 6 n Actual Value Range: 1~32 characters
RATOR MLOFD Carrier Default Value: None
LST -121251 NB-IoT
CNOPE LOFD-0 RAN
TDLOF with
D-00103 Commo
7 n
Carrier
MLOFD
-121252 RAN
Sharing
MLOFD with
-131253 Dedicate
LOFD-0 d
01086/ Carrier
TDLOF NB-IoT
D-00108 RAN
6 Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4 NB-IoT
Hybrid
RAN
Sharing
RAN
Sharing
by More
Operator
s
Hybrid
RAN
Sharing

eRAN

nd
CnOper Mcc ADD LOFD-0 RAN Meaning: Indicates the mobile country code (MCC) of
ator CNOPE 01036/ Sharing the operator.
RATOR TDLOF with GUI Value Range: 3 characters
MOD D-00103 Commo
6 n Unit: None
CNOPE
RATOR MLOFD Carrier Actual Value Range: 000~999
LST -121251 NB-IoT Default Value: None

CNOPE LOFD-0 RAN
TDLOF with
D-00103 Commo
7 n
Carrier
MLOFD
-121252 RAN
Sharing
MLOFD with
-131253 Dedicate
LOFD-0 d
01086/ Carrier
TDLOF NB-IoT
D-00108 RAN
6 Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4 NB-IoT
Hybrid
RAN
Sharing
RAN
Sharing
by More
Operator
s
Hybrid
RAN
Sharing

eRAN

nd
CnOper Mnc ADD LOFD-0 RAN Meaning: Indicates the mobile network code (MNC)
ator CNOPE 01036/ Sharing of the operator. The value of this parameter is a string
RATOR TDLOF with of two or three decimal digits.
MOD D-00103 Commo GUI Value Range: 2~3 characters
CNOPE 6 n
Carrier Unit: None
RATOR MLOFD
-121251 NB-IoT Actual Value Range: 00~99,000~999
LST
CNOPE LOFD-0 RAN Default Value: None
TDLOF with
D-00103 Commo
7 n
Carrier
MLOFD
-121252 RAN
Sharing
MLOFD with
-131253 Dedicate
LOFD-0 d
01086/ Carrier
TDLOF NB-IoT
D-00108 RAN
6 Sharing
LOFD-0 with
70206/ Dedicate
TDLOF d
D-08122 Carrier
4 NB-IoT
Hybrid
RAN
Sharing
RAN
Sharing
by More
Operator
s
Hybrid
RAN
Sharing
CellAcc LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
ess llId CELLA identifies a cell within a BS.
CCESS GUI Value Range: 0~255
MOD Unit: None
CELLA
CCESS Actual Value Range: 0~255
Default Value: None

eRAN

nd
License CnOper ADD LOFD-0 RAN Meaning: Indicates the index of the operator. This
Sharing atorId LICENS 01036/ Sharing parameter applies only to LTE FDD and LTE TDD.
Policy ESHAR TDLOF with GUI Value Range: 0~5
INGPO D-00103 Commo
LICY 6 n Unit: None
LST LOFD-0 Carrier Actual Value Range: 0~5

LICENS 01037/ RAN Default Value: None
ESHAR TDLOF Sharing
INGPO D-00103 with
LICY 7 Dedicate
MOD LOFD-0 d
LICENS 70206/ Carrier
ESHAR TDLOF Hybrid
INGPO D-08122 RAN
LICY 4 Sharing
RMV
LICENS
ESHAR
INGPO
LICY
CellAlg LocalCe DSP None None Meaning: Indicates the local ID of the cell. It uniquely
oSwitch llId CELLU identifies a cell within an eNodeB.
LCAMC GUI Value Range: 0~255
CLUST
ER Unit: None
DSP Actual Value Range: 0~255

CELLU Default Value: None
LICSST
ATUS
LST
CELLA
LGOSW
ITCH
MOD
CELLA
LGOSW
ITCH

eRAN

nd
LicRatio UpLicR MOD LOFD-0 RAN Meaning: Indicates the proportion of the UL licensed
atio LICRAT 01036/ Sharing traffic to the total licensed traffic of the eNodeB. The
IO TDLOF with total licensed traffic is the sum of UL and DL licensed
LST D-00103 Commo traffic. If this parameter is set to 100%, there is no DL
LICRAT 6 n licensed traffic, affecting service admission. This
IO LOFD-0 Carrier parameter applies only to LTE FDD and LTE TDD.
01037/ RAN GUI Value Range: 1~100
TDLOF Sharing Unit: %
D-00103 with
7 Dedicate Actual Value Range: 1~100
LOFD-0 d Default Value: 25

70206/ Carrier
TDLOF Hybrid
D-08122 RAN
4 Sharing
LicRatio CnOper ADD LOFD-0 RAN Meaning: Indicates the ID of the operator.
SharePo atorId LICRAT 01036/ Sharing GUI Value Range: 0~5
licy IOSHA TDLOF with
REPOLI D-00103 Commo Unit: None
CY 6 n Actual Value Range: 0~5
LST LOFD-0 Carrier Default Value: None
LICRAT 01037/ RAN
IOSHA TDLOF Sharing
REPOLI D-00103 with
CY 7 Dedicate
MOD LOFD-0 d
LICRAT 70206/ Carrier
IOSHA TDLOF Hybrid
REPOLI D-08122 RAN
CY 4 Sharing
RMV
LICRAT
IOSHA
REPOLI
CY

eRAN

nd
RatFreq RatType ADD LOFD-0 Camp & Meaning: Indicates the Radio Access Technology
Priority RATFR 0105401 Handov (RAT). This parameter applies only to LTE FDD and
Group EQPRI / er Based LTE TDD.
ORITY TDLOF on SPID GUI Value Range: EUTRAN, UTRAN, GERAN,
GROUP D-00105 Enhance CDMA20001XRTT, CDMA2000HRPD
LST 401 d CS Unit: None
RATFR LOFD-0 Fallback
EQPRI 01090/ Actual Value Range: EUTRAN, UTRAN, GERAN,
to
ORITY TDLOF CDMA20001XRTT, CDMA2000HRPD
CDMA2
GROUP D-00109 000 Default Value: None
MOD 0 1xRTT
RATFR LOFD-0 PS Inter-
EQPRI 01021/ RAT
ORITY TDLOF Mobility
GROUP D-00102 between
RMV 1 E-
RATFR UTRAN
EQPRI and
ORITY CDMA2
GROUP 000
RatFreq DlEarfc ADD LOFD-0 Camp & Meaning: Indicates the downlink frequency. In
Priority n RATFR 0105401 Handov CDMA2000, this parameter indicates the bandclass.
Group EQPRI / er Based Before configuring a priority for a frequency specified
ORITY TDLOF on SPID by this parameter, ensure that an external or local cell
GROUP D-00105 operating on this frequency has been configured. This
LST 401 parameter applies only to LTE FDD and LTE TDD.
RATFR GUI Value Range: 0~68585,229376~229575
EQPRI Unit: None
ORITY
GROUP Actual Value Range: 0~68585,229376~229575
MOD Default Value: None

RATFR
EQPRI
ORITY
GROUP
RMV
RATFR
EQPRI
ORITY
GROUP

eRAN

nd
RatFreq Priority ADD LOFD-0 Camp & Meaning: Indicates the priority of the intra-RAT
Priority RATFR 0105401 Handov frequency band or frequency. The value 0 indicates
Group EQPRI / er Based the lowest priority. The value of this parameter must
ORITY TDLOF on SPID be determined together with the priorities of other
GROUP D-00105 RAN frequencies during the network planning. Cell
MOD 401 Sharing reselection priorities in different RATs cannot be the
RATFR LOFD-0 with same. This parameter applies only to LTE FDD and
EQPRI 01036/ Commo LTE TDD.
ORITY TDLOF n GUI Value Range: 0~7
GROUP D-00103 Carrier Unit: None
LST 6 Multi Actual Value Range: 0~7
RATFR LOFD-0 Operator
EQPRI 70210/ s SPID Default Value: 0
ORITY TDLOF Policy
GROUP D-00113
3
RatFreq BandInd ADD LOFD-0 Camp & Meaning: Indicates the GERAN frequency band. This
Priority icator RATFR 0105401 Handov parameter applies only to LTE FDD and LTE TDD.
Group EQPRI / er Based GUI Value Range: GSM_dcs1800, GSM_pcs1900
ORITY TDLOF on SPID
GROUP D-00105 Unit: None
RAN
MOD 401 Sharing Actual Value Range: GSM_dcs1800, GSM_pcs1900
RATFR LOFD-0 with Default Value: GSM_dcs1800
EQPRI 01036/ Commo
ORITY TDLOF n
GROUP D-00103 Carrier
LST 6 Multi
RATFR LOFD-0 Operator
EQPRI 70210/ s SPID
ORITY TDLOF Policy
GROUP D-00113
3
SpidCfg RatFreq ADD LOFD-0 Camp & Meaning: Indicates whether to set the priority for the
PriorityI SPIDCF 0105401 Handov intra-RAT frequency. If this parameter is set to
nd G / er Based CFG(CFG), UEs select the target frequency based on
MOD TDLOF on SPID the priority setting. If this parameter is set to
SPIDCF D-00105 RAN NOT_CFG(NOT_CFG), UEs do not select the target
G 401 Sharing frequency based on the priority setting. This
LOFD-0 with parameter applies only to LTE FDD and LTE TDD.
LST
SPIDCF 01036/ Commo GUI Value Range: NOT_CFG(NOT_CFG),
G TDLOF n CFG(CFG)
D-00103 Carrier Unit: None
6
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(NOT_CFG)

eRAN

nd
GeranN LocalCe ADD None None Meaning: Indicates the local cell ID. It uniquely
FGroup llId GERAN identifies a cell within an eNodeB. This parameter
SCellOp NFGRO applies only to LTE FDD and LTE TDD.
UPSCE GUI Value Range: 0~255
LLOP
Unit: None
LST
GERAN Actual Value Range: 0~255
NFGRO Default Value: None
UPSCE
LLOP
MOD
GERAN
NFGRO
UPSCE
LLOP
RMV
GERAN
NFGRO
UPSCE
LLOP
GeranN BcchGr ADD LOFD-0 MOCN Meaning: Indicates the index of the GERAN carrier
FGroup oupId GERAN 01112/ Flexible frequency group. It uniquely identifies a GERAN
SCellOp NFGRO TDLOF Priority carrier frequency group. This parameter applies only
UPSCE D-00111 Based to LTE FDD and LTE TDD.
LLOP 2 Campin GUI Value Range: 0~31
LST g
Unit: None
GERAN
NFGRO Actual Value Range: 0~31
UPSCE Default Value: None
LLOP
MOD
GERAN
NFGRO
UPSCE
LLOP
RMV
GERAN
NFGRO
UPSCE
LLOP

eRAN

nd
GeranN CnOper ADD LOFD-0 MOCN Meaning: Indicates the ID of the operator. This
FGroup atorID GERAN 01112/ Flexible parameter applies only to LTE FDD and LTE TDD.
SCellOp NFGRO TDLOF Priority GUI Value Range: 0~5
UPSCE D-00111 Based
LLOP 2 Campin Unit: None
LST g Actual Value Range: 0~5

GERAN Default Value: None
NFGRO
UPSCE
LLOP
MOD
GERAN
NFGRO
UPSCE
LLOP
RMV
GERAN
NFGRO
UPSCE
LLOP
GeranN CellRes ADD LOFD-0 MOCN Meaning: Indicates whether to configure a dedicated
FGroup elDediPr GERAN 01112/ Flexible cell-reselection priority based on the PLMN ID of the
SCellOp iCfgInd NFGRO TDLOF Priority local cell for the GERAN carrier frequency group.
UPSCE D-00111 Based This parameter applies only to LTE FDD and LTE
LLOP 2 Campin TDD.
MOD LBFD-0 g GUI Value Range: NOT_CFG(Not configure),
GERAN 0201803 Cell CFG(Configure)
NFGRO / Selectio Unit: None
UPSCE TDLBF n and
LLOP D-00201 Re- Actual Value Range: NOT_CFG, CFG
LST 803 selection Default Value: NOT_CFG(Not configure)

GERAN LOFD-0 RAN
NFGRO 01036/ Sharing
UPSCE TDLOF with
LLOP D-00103 Commo
6 n
Carrier

eRAN

nd
GeranN CellRes ADD LOFD-0 MOCN Meaning: Indicates the cell reselection dedicated
FGroup elDediPr GERAN 01112/ Flexible priority for a GERAN frequency carrier group based
SCellOp i NFGRO TDLOF Priority on the PLMN ID of the serving cell. The value 0
UPSCE D-00111 Based indicates the lowest priority. If the related SPID
LLOP 2 Campin configuration is specified, set this priority to the one
MOD LBFD-0 g specified in the SPID configuration. If no related
GERAN 0201803 Cell SPID configuration is specified but this parameter is
NFGRO / Selectio set, the eNodeB delivers the cell reselection priorities
UPSCE TDLBF n and of all PLMNs supported by a UE by using the IE
LLOP D-00201 Re- idleModeMobilityControlInfo in an RRC Connection
803 selection Release message to the UE. If no related SPID
LST configuration is specified and this parameter is not set,
GERAN LOFD-0 RAN a UE uses the cell reselection priority of the
NFGRO 01036/ Sharing neighboring GERAN carrier frequency group, which
UPSCE TDLOF with is broadcast in the system information. This parameter
LLOP D-00103 Commo applies only to LTE FDD and LTE TDD.
6 n
Carrier GUI Value Range: 0~7
Unit: None
Default Value: 0
GeranRa LocalCe ADD None None Meaning: Indicates the cell identity of the local cell. It
nShare llId GERAN uniquely identifies a cell within an eNodeB. This
RANSH parameter applies only to LTE FDD and LTE TDD.
ARE GUI Value Range: 0~255
LST Unit: None
GERAN
RANSH Actual Value Range: 0~255
ARE Default Value: None
MOD
GERAN
RANSH
ARE
RMV
GERAN
RANSH
ARE

eRAN

nd
GeranRa BcchGr ADD LOFD-0 RAN Meaning: Indicates the index of the GERAN carrier
nShare oupId GERAN 01036/ Sharing frequency group. It uniquely identifies a GERAN
RANSH TDLOF with carrier frequency group. This parameter applies only
ARE D-00103 Commo to LTE FDD and LTE TDD.
LST 6 n GUI Value Range: 0~31
GERAN LOFD-0 Carrier
Unit: None
RANSH 01112/ MOCN
ARE TDLOF Flexible Actual Value Range: 0~31
MOD D-00111 Priority Default Value: None

GERAN 2 Based
RANSH LOFD-0 Campin
ARE 70206/ g
RMV TDLOF Hybrid
GERAN D-08122 RAN
RANSH 4 Sharing
ARE
GeranRa Mcc ADD LOFD-0 RAN Meaning:

nShare GERAN 01036/ Sharing Indicates the mobile country code (MCC) of the
RANSH TDLOF with operator that shares the neighboring GERAN carrier
ARE D-00103 Commo frequency group.
LST 6 n
GERAN LOFD-0 Carrier A public land mobile network (PLMN) ID is
RANSH 01112/ MOCN comprised of an MCC and a mobile network code
ARE TDLOF Flexible (MNC).
MOD D-00111 Priority The MCC consists of three digits.

GERAN 2 Based
RANSH LOFD-0 Campin The MNC consists of two to three digits.
ARE 70206/ g
For example, if the MCC is 123 and the MNC is 45,
RMV TDLOF Hybrid then the PLMN ID is 12345. This parameter applies
GERAN D-08122 RAN only to LTE FDD and LTE TDD.
RANSH 4 Sharing
GUI Value Range: 3 characters
ARE
Unit: None
Default Value: None

eRAN

nd
GeranRa Mnc ADD LOFD-0 RAN Meaning:

nShare GERAN 01036/ Sharing Indicates the mobile network code (MNC) of the
RANSH TDLOF with operator that shares the neighboring GERAN carrier
ARE D-00103 Commo frequency group.
LST 6 n
GERAN LOFD-0 Carrier A public land mobile network (PLMN) ID is
RANSH 01112/ MOCN comprised of a mobile country code (MCC) and an
ARE TDLOF Flexible MNC.
MOD D-00111 Priority The MCC consists of three digits.

GERAN 2 Based
RANSH LOFD-0 Campin The MNC consists of two to three digits.
ARE 70206/ g
RMV TDLOF Hybrid then the PLMN ID is 12345. This parameter applies
GERAN D-08122 RAN only to LTE FDD and LTE TDD.
RANSH 4 Sharing
GUI Value Range: 2~3 characters
ARE
Unit: None
Actual Value Range: 00~99,000~999
Default Value: None
GeranRa CellRes ADD LOFD-0 RAN Meaning: Indicates whether to configure the cell
nShare elPriorit GERAN 01036/ Sharing reselection priority of the operator that shares the
yCfgInd RANSH TDLOF with neighboring GERAN carrier frequency group. This
ARE D-00103 Commo parameter applies only to LTE FDD and LTE TDD.
MOD 6 n GUI Value Range: NOT_CFG(Not configure),
GERAN LBFD-0 Carrier CFG(Configure)
RANSH 0201803 Cell Unit: None
ARE / Selectio
TDLBF n and Actual Value Range: NOT_CFG, CFG
LST
GERAN D-00201 Re- Default Value: NOT_CFG(Not configure)
RANSH 803 selection
ARE LOFD-0 MOCN
01112/ Flexible
TDLOF Priority
D-00111 Based
2 Campin
LOFD-0 g
70206/ Hybrid
TDLOF RAN
D-08122 Sharing
4

eRAN

nd
GeranRa CellRes ADD LOFD-0 RAN Meaning: Indicates the cell reselection priority of the
nShare elPriorit GERAN 01036/ Sharing operator that shares the neighboring GERAN carrier
y RANSH TDLOF with frequency group. The value 0 indicates the lowest
ARE D-00103 Commo priority. If the related SPID configuration is specified,
MOD 6 n set this priority to the one specified in the SPID
GERAN LBFD-0 Carrier configuration. If no related SPID configuration is
RANSH 0201803 Cell specified but this parameter is set, the eNodeB
ARE / Selectio delivers the cell reselection priorities of all PLMNs
TDLBF n and supported by a UE by using the IE idleModeMobility-
LST ControlInfo in an RRC Connection Release message
GERAN D-00201 Re-
803 selection to the UE. If no related SPID configuration is
RANSH specified and this parameter is not set, a UE uses the
ARE LOFD-0 MOCN cell reselection priority of the neighboring GERAN
01112/ Flexible carrier frequency group, which is broadcast in the
TDLOF Priority system information. This parameter applies only to
D-00111 Based LTE FDD and LTE TDD.
2 Campin
g GUI Value Range: 0~7
LOFD-0
70206/ Hybrid Unit: None
TDLOF RAN Actual Value Range: 0~7
D-08122 Sharing Default Value: 0
4
UtranNF LocalCe ADD None None Meaning: Indicates the cell ID of the local cell. It
reqSCell llId UTRAN uniquely identifies a cell within an eNodeB. This
Op NFREQ parameter applies only to LTE FDD and LTE TDD.
SCELL GUI Value Range: 0~255
OP
Unit: None
LST
UTRAN Actual Value Range: 0~255
NFREQ Default Value: None
SCELL
OP
MOD
UTRAN
NFREQ
SCELL
OP
RMV
UTRAN
NFREQ
SCELL
OP

eRAN

nd
UtranNF UtranDl ADD LOFD-0 MOCN Meaning: Indicates the downlink UARFCN of the
reqSCell Arfcn UTRAN 01112/ Flexible neighboring UTRAN frequency. This parameter
Op NFREQ TDLOF Priority applies only to LTE FDD and LTE TDD.
SCELL D-00111 Based GUI Value Range: 0~16383
OP 2 Campin
g Unit: None
LST
NFREQ Default Value: None
SCELL
OP
MOD
UTRAN
NFREQ
SCELL
OP
RMV
UTRAN
NFREQ
SCELL
OP
UtranNF CnOper ADD LOFD-0 MOCN Meaning: Indicates the ID of the operator. This
reqSCell atorID UTRAN 01112/ Flexible parameter applies only to LTE FDD and LTE TDD.
Op NFREQ TDLOF Priority GUI Value Range: 0~5
SCELL D-00111 Based
OP 2 Campin Unit: None

UTRAN Default Value: None
NFREQ
SCELL
OP
MOD
UTRAN
NFREQ
SCELL
OP
RMV
UTRAN
NFREQ
SCELL
OP

eRAN

nd
UtranNF CellRes ADD LOFD-0 MOCN Meaning: Indicates whether to configure a dedicated
reqSCell elDediPr UTRAN 01112/ Flexible cell-reselection priority based on the PLMN ID of the
Op iCfgInd NFREQ TDLOF Priority local cell for the UTRAN frequency. This parameter
SCELL D-00111 Based applies only to LTE FDD and LTE TDD.
OP 2 Campin GUI Value Range: NOT_CFG(Not configure),
MOD LBFD-0 g CFG(Configure)
UTRAN 0201803 Cell Unit: None
NFREQ / Selectio
SCELL TDLBF n and Actual Value Range: NOT_CFG, CFG
OP D-00201 Re- Default Value: NOT_CFG(Not configure)
LST 803 selection
UTRAN LOFD-0 RAN
NFREQ 01036/ Sharing
SCELL TDLOF with
OP D-00103 Commo
6 n
LOFD-0 Carrier
70206/ Hybrid
TDLOF RAN
D-08122 Sharing
4
UtranNF CellRes ADD LOFD-0 MOCN Meaning: Indicates the dedicated cell reselection
reqSCell elDediPr UTRAN 01112/ Flexible priority for a UTRAN frequency based on the PLMN
Op i NFREQ TDLOF Priority ID of the local cell. The value 0 indicates the lowest
SCELL D-00111 Based priority. If the related SPID configuration is specified,
OP 2 Campin set this priority to the one specified in the SPID
MOD LBFD-0 g configuration. If no related SPID configuration is
UTRAN 0201803 Cell specified but this parameter is set, the eNodeB
NFREQ / Selectio delivers the cell reselection priorities of all PLMNs
SCELL TDLBF n and supported by a UE by using the IE idleModeMobility-
OP D-00201 Re- ControlInfo in an RRC Connection Release message
LST specified and this parameter is not set, a UE uses the
UTRAN LOFD-0 RAN cell reselection priority of the neighboring UTRAN
NFREQ 01036/ Sharing frequency, which is broadcast in the system
SCELL TDLOF with information. This parameter applies only to LTE FDD
OP D-00103 Commo and LTE TDD.
6 n
LOFD-0
4

eRAN

nd
UtranRa LocalCe ADD None None Meaning: Indicates the cell identity of the local cell. It
nShare llId UTRAN uniquely identifies a cell within an eNodeB. This
RANSH parameter applies only to LTE FDD and LTE TDD.
ARE GUI Value Range: 0~255
LST Unit: None
UTRAN
RANSH Actual Value Range: 0~255
ARE Default Value: None
MOD
UTRAN
RANSH
ARE
RMV
UTRAN
RANSH
ARE

eRAN

nd
UtranRa UtranDl ADD LOFD-0 RAN Meaning:

nShare Arfcn UTRAN 01036/ Sharing Indicates the DL UARFCN of the neighboring cell
RANSH TDLOF with operating on the UTRAN frequency. The UARFCN
ARE D-00103 Commo range in each FDD frequency band is shown as
LST 6 n follows:
UTRAN LOFD-0 Carrier
RANSH 01112/ MOCN Band 1:
ARE TDLOF Flexible Normal UARFCNs: [10562-10838]
MOD D-00111 Priority
UTRAN 2 Based Special UARFCNs: none
RANSH LOFD-0 Campin
Band 2:
ARE 70206/ g
TDLOF Hybrid Normal UARFCNs: [9662-9938]
RMV
UTRAN D-08122 RAN
Special UARFCNs: (412, 437, 462, 487, 512, 537,
RANSH 4 Sharing
562, 587, 612, 637, 662, 687)
ARE
Band 3:
Normal UARFCNs: [1162-1513]
Special UARFCNs: none
Band 4:
Special UARFCNs: (1887, 1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087)
Band 5:
Special UARFCNs: (1007, 1012, 1032, 1037, 1062,
1087)
Band 6:
Special UARFCNs: (1037, 1062)
Band 7:
Special UARFCNs: (2587, 2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887,
2912)
Band 8:

eRAN

nd

Band 9:
The UARFCN range in each TDD frequency band is
shown as follows:
Band 1:
Normal UARFCNs: [9500-9600] and [10050-10125]
Band 2:
Normal UARFCNs: [9250-9550] and [9650-9950]
Band 3:
Band 4:
Special UARFCNs: (2112, 2137, 2162, 2187, 2212,
2237, 2262, 2287, 2312, 2337)
Band 5:
Band 6:
For details, see 3GPP TS 25.104 and 3GPP TS
25.105. This parameter applies only to LTE FDD and
LTE TDD.
Unit: None
Default Value: None

eRAN

nd
UtranRa Mcc ADD LOFD-0 RAN Meaning:

nShare UTRAN 01036/ Sharing Indicates the mobile country code (MCC) of the
RANSH TDLOF with neighboring UTRAN cell.
ARE D-00103 Commo
LST 6 n A public land mobile network (PLMN) ID is
UTRAN LOFD-0 Carrier comprised of an MCC and a mobile network code
RANSH 01112/ MOCN (MNC).
ARE TDLOF Flexible The MCC consists of three digits.
UTRAN 2 Based The MNC consists of two to three digits.
RANSH LOFD-0 Campin
ARE 70206/ g
then the PLMN ID is 12345. This parameter applies
RMV TDLOF Hybrid only to LTE FDD and LTE TDD.
UTRAN D-08122 RAN
GUI Value Range: 3 characters
RANSH 4 Sharing
Unit: None
ARE
Default Value: None
UtranRa Mnc ADD LOFD-0 RAN Meaning:

nShare UTRAN 01036/ Sharing Indicates the mobile network code (MNC) of the
RANSH TDLOF with neighboring UTRAN cell.
ARE D-00103 Commo
LST 6 n A public land mobile network (PLMN) ID is
UTRAN LOFD-0 Carrier comprised of a mobile country code (MCC) and an
RANSH 01112/ MOCN MNC.
ARE TDLOF Flexible The MCC consists of three digits.
UTRAN 2 Based The MNC consists of two to three digits.
RANSH LOFD-0 Campin
ARE 70206/ g
then the PLMN ID is 12345. This parameter applies
RMV TDLOF Hybrid only to LTE FDD and LTE TDD.
UTRAN D-08122 RAN
GUI Value Range: 2~3 characters
RANSH 4 Sharing
Unit: None
ARE
Actual Value Range: 00~99,000~999
Default Value: None

eRAN

nd
UtranRa CellRes ADD LOFD-0 RAN Meaning: Indicates whether to configure the cell
nShare elPriorit UTRAN 01036/ Sharing reselection priority of the operator that shares the
yCfgInd RANSH TDLOF with neighboring UTRAN frequency. This parameter
ARE D-00103 Commo applies only to LTE FDD and LTE TDD.
MOD 6 n GUI Value Range: NOT_CFG(Not configure),
UTRAN LBFD-0 Carrier CFG(Configure)
RANSH 0201803 Cell Unit: None
ARE / Selectio
TDLBF n and Actual Value Range: NOT_CFG, CFG
LST
UTRAN D-00201 Re- Default Value: NOT_CFG(Not configure)
RANSH 803 selection
ARE LOFD-0 MOCN
01112/ Flexible
TDLOF Priority
D-00111 Based
2 Campin
LOFD-0 g
70206/ Hybrid
TDLOF RAN
D-08122 Sharing
4
UtranRa CellRes ADD LOFD-0 RAN Meaning: Indicates the cell reselection priority of the
nShare elPriorit UTRAN 01036/ Sharing operator that shares the neighboring UTRAN
y RANSH TDLOF with frequency. The value 0 indicates the lowest priority. If
ARE D-00103 Commo the related SPID configuration is specified, set this
MOD 6 n priority to the one specified in the SPID configuration.
UTRAN LBFD-0 Carrier If no related SPID configuration is specified but this
RANSH 0201803 Cell parameter is set, the eNodeB delivers the cell
ARE / Selectio reselection priorities of all PLMNs supported by a UE
TDLBF n and by using the IE idleModeMobilityControlInfo in an
LST RRC Connection Release message to the UE. If no
UTRAN D-00201 Re-
803 selection related SPID configuration is specified and this
RANSH parameter is not set, a UE uses the cell reselection
ARE LOFD-0 MOCN priority of the neighboring UTRAN frequency, which
01112/ Flexible is broadcast in the system information. This parameter
TDLOF Priority applies only to LTE FDD and LTE TDD.
D-00111 Based
2 Campin GUI Value Range: 0~7
LOFD-0 g Unit: None
70206/ Hybrid Actual Value Range: 0~7
TDLOF RAN Default Value: 0
D-08122 Sharing
4

eRAN

nd
EutranN LocalCe ADD None None Meaning: Indicates the ID of the local cell. It uniquely
FreqSCe llId EUTRA identifies a cell within an eNodeB. This parameter
llOp NNFRE applies only to LTE FDD and LTE TDD.
QSCEL GUI Value Range: 0~255
LOP
Unit: None
LST
EUTRA Actual Value Range: 0~255
NNFRE Default Value: None
QSCEL
LOP
MOD
EUTRA
NNFRE
QSCEL
LOP
RMV
EUTRA
NNFRE
QSCEL
LOP
EutranN DlEarfc ADD LOFD-0 MOCN Meaning: Indicates the DL EARFCN of the Operator
FreqSCe n EUTRA 01112/ Flexible Configuration for Serving Cell in EUTRAN
llOp NNFRE TDLOF Priority Frequency. For details, see the 3GPP TS 36.104. This
QSCEL D-00111 Based parameter applies only to LTE FDD and LTE TDD.
LOP 2 Campin GUI Value Range: 0~68585,229376~229575
LST g
Unit: None
EUTRA
NNFRE Actual Value Range: 0~68585,229376~229575
QSCEL Default Value: None
LOP
MOD
EUTRA
NNFRE
QSCEL
LOP
RMV
EUTRA
NNFRE
QSCEL
LOP

eRAN

nd
EutranN CnOper ADD LOFD-0 MOCN Meaning: Indicates the ID of the operator. This
FreqSCe atorID EUTRA 01112/ Flexible parameter applies only to LTE FDD and LTE TDD.
llOp NNFRE TDLOF Priority GUI Value Range: 0~5
QSCEL D-00111 Based
LOP 2 Campin Unit: None

EUTRA Default Value: None
NNFRE
QSCEL
LOP
MOD
EUTRA
NNFRE
QSCEL
LOP
RMV
EUTRA
NNFRE
QSCEL
LOP
EutranN CellRes ADD LOFD-0 MOCN Meaning: Indicates whether to configure a dedicated
FreqSCe elDediPr EUTRA 01112/ Flexible cell-reselection priority based on the PLMN ID of the
llOp iCfgInd NNFRE TDLOF Priority local cell for the neighboring E-UTRAN frequency.
QSCEL D-00111 Based This parameter applies only to LTE FDD and LTE
LOP 2 Campin TDD.
MOD LBFD-0 g GUI Value Range: NOT_CFG(Not configure),
EUTRA 0201803 Cell CFG(Configure)
NNFRE / Selectio Unit: None
QSCEL TDLBF n and
LOP D-00201 Re- Actual Value Range: NOT_CFG, CFG
LST 803 selection Default Value: NOT_CFG(Not configure)

EUTRA LOFD-0 RAN
NNFRE 01036/ Sharing
QSCEL TDLOF with
LOP D-00103 Commo
6 n
Carrier

eRAN

nd
EutranN CellRes ADD LOFD-0 MOCN Meaning: Indicates the cell reselection dedicated
FreqSCe elDediPr EUTRA 01112/ Flexible priority for an E-UTRAN frequency based on the
llOp i NNFRE TDLOF Priority PLMN ID of the local cell. The value 0 indicates the
QSCEL D-00111 Based lowest priority. If the related SPID configuration is
LOP 2 Campin specified, the cell reselection priority specified in the
MOD LBFD-0 g SPID configuration is used. If no related SPID
EUTRA 0201803 Cell configuration is specified but this parameter is set, the
NNFRE / Selectio eNodeB delivers the cell reselection priorities of all
QSCEL TDLBF n and PLMNs supported by a UE by using the IE
LOP D-00201 Re- idleModeMobilityControlInfo in an RRC Connection
803 selection Release message to the UE. If no related SPID
LST configuration is specified and this parameter is not set,
EUTRA LOFD-0 RAN a UE uses the cell reselection priority of the
NNFRE 01036/ Sharing neighboring E-UTRAN frequency, which is broadcast
QSCEL TDLOF with in the system information. This parameter applies only
LOP D-00103 Commo to LTE FDD and LTE TDD.
6 n
Unit: None
Default Value: 0
EutranN LocalCe ADD None None Meaning: Indicates the ID of the local cell. It uniquely
FreqRan llId EUTRA identifies a cell within an eNodeB. This parameter
Share NNFRE applies only to LTE FDD and LTE TDD.
QRANS GUI Value Range: 0~255
HARE
Unit: None
LST
EUTRA Actual Value Range: 0~255
NNFRE Default Value: None
QRANS
HARE
MOD
EUTRA
NNFRE
QRANS
HARE
RMV
EUTRA
NNFRE
QRANS
HARE

eRAN

nd
EutranN DlEarfc ADD LOFD-0 RAN Meaning: Indicates the DL EARFCN of the operator
FreqRan n EUTRA 01036/ Sharing that shares the neighboring E-UTRAN frequency. For
Share NNFRE TDLOF with details, see the 3GPP TS 36.104. This parameter
QRANS D-00103 Commo applies only to LTE FDD and LTE TDD.
HARE 6 n GUI Value Range: 0~68585,229376~229575
LST LOFD-0 Carrier
Unit: None
EUTRA 01112/ MOCN
NNFRE TDLOF Flexible Actual Value Range: 0~68585,229376~229575
QRANS D-00111 Priority Default Value: None
HARE 2 Based
MOD LOFD-0 Campin
EUTRA 70206/ g
NNFRE TDLOF Hybrid
QRANS D-08122 RAN
HARE 4 Sharing
RMV
EUTRA
NNFRE
QRANS
HARE
EutranN Mcc ADD LOFD-0 RAN Meaning:

FreqRan EUTRA 01036/ Sharing Indicates the mobile country code (MCC) of the
Share NNFRE TDLOF with operator that shares the neighboring E-UTRAN
QRANS D-00103 Commo frequency.
HARE 6 n
LST LOFD-0 Carrier A public land mobile network (PLMN) ID is
EUTRA 01112/ MOCN comprised of an MCC and a mobile network code
NNFRE TDLOF Flexible (MNC).
QRANS D-00111 Priority
HARE 2 Based The MCC consists of three digits.
MOD LOFD-0 Campin The MNC consists of two to three digits.

EUTRA 70206/ g
NNFRE TDLOF Hybrid For example, if the MCC is 123 and the MNC is 45,
QRANS D-08122 RAN the PLMN ID is 12345. This parameter applies only to
HARE 4 Sharing LTE FDD and LTE TDD.
EUTRA Unit: None
NNFRE
QRANS Actual Value Range: 000~999
HARE Default Value: None

eRAN

nd
EutranN Mnc ADD LOFD-0 RAN Meaning:

FreqRan EUTRA 01036/ Sharing Indicates the mobile network code (MNC) of the
Share NNFRE TDLOF with operator that shares the neighboring E-UTRAN
QRANS D-00103 Commo frequency.
HARE 6 n
LST LOFD-0 Carrier A public land mobile network (PLMN) ID is
EUTRA 01112/ MOCN comprised of a mobile network code (MCC) and an
NNFRE TDLOF Flexible MNC.
QRANS D-00111 Priority
HARE 2 Based The MCC consists of three digits.
MOD LOFD-0 Campin The MNC consists of two to three digits.

EUTRA 70206/ g
NNFRE TDLOF Hybrid For example, if the MCC is 123 and the MNC is 45,
QRANS D-08122 RAN the PLMN ID is 12345. This parameter applies only to
HARE 4 Sharing LTE FDD and LTE TDD.
EUTRA Unit: None
NNFRE
QRANS Actual Value Range: 00~99,000~999
HARE Default Value: None
EutranN CellRes ADD LOFD-0 RAN Meaning: Indicates whether to configure the cell
FreqRan elPriorit EUTRA 01036/ Sharing reselection priority. This parameter applies only to
Share yCfgInd NNFRE TDLOF with LTE FDD and LTE TDD.
QRANS D-00103 Commo GUI Value Range: NOT_CFG(Not configure),
HARE 6 n CFG(Configure)
MOD TDLBF Carrier
Unit: None
EUTRA D-00201 Cell
NNFRE 803 Selectio Actual Value Range: NOT_CFG, CFG
QRANS LOFD-0 n and Default Value: NOT_CFG(Not configure)
HARE 01112/ Re-
LST TDLOF selection
EUTRA D-00111 MOCN
NNFRE 2 Flexible
QRANS LOFD-0 Priority
HARE 70206/ Based
TDLOF Campin
D-08122 g
4 Hybrid
RAN
Sharing

eRAN

nd
EutranN CellRes ADD LOFD-0 RAN Meaning: Indicates the cell reselection priority of the
FreqRan elPriorit EUTRA 01036/ Sharing operator that shares the neighboring E-UTRAN
Share y NNFRE TDLOF with frequency. The value 0 indicates the lowest priority. If
QRANS D-00103 Commo the related SPID configuration is specified, the cell
HARE 6 n reselection priority specified in the SPID
MOD LBFD-0 Carrier configuration is used. If no related SPID configuration
EUTRA 0201803 Cell is specified but this parameter is set, the eNodeB
NNFRE / Selectio delivers the cell reselection priorities of all PLMNs
QRANS TDLBF n and supported by a UE by using the IE idleModeMobility-
HARE D-00201 Re- ControlInfo in an RRC Connection Release message
LST specified and this parameter is not set, a UE uses the
EUTRA LOFD-0 MOCN cell reselection priority of the neighboring E-UTRAN
NNFRE 01112/ Flexible frequency, which is broadcast in the system
QRANS TDLOF Priority information. This parameter applies only to LTE FDD
HARE D-00111 Based and LTE TDD.
2 Campin
g GUI Value Range: 0~7
LOFD-0
4
Cdma20 LocalCe ADD None None Meaning: Indicates the ID of the local cell. It uniquely
00BcSC llId CDMA2 identifies a cell within an eNodeB. This parameter
ellOp 000BCS applies only to LTE FDD and LTE TDD.
CELLO GUI Value Range: 0~255
P
Unit: None
LST
CDMA2 Actual Value Range: 0~255
000BCS Default Value: None
CELLO
P
MOD
CDMA2
000BCS
CELLO
P
RMV
CDMA2
000BCS
CELLO
P

eRAN

nd
Cdma20 BandCla ADD LOFD-0 CS Meaning: Indicates the neighboring CDMA2000 band
00BcSC ss CDMA2 01035/ Fallback class. For details, see 3GPP 36.331. This parameter
ellOp 000BCS TDLOF to applies only to LTE FDD and LTE TDD.
CELLO D-00103 CDMA2 GUI Value Range: bc0, bc1, bc2, bc3, bc4, bc5, bc6,
P 5 000 bc7, bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15,
LST LOFD-0 1xRTT bc16, bc17, bc18, bc19, bc20, bc21
CDMA2 01021/ PS Inter- Unit: None
000BCS TDLOF RAT
CELLO D-00102 Mobility Actual Value Range: bc0, bc1, bc2, bc3, bc4, bc5, bc6,
P 1 between bc7, bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15,
E- bc16, bc17, bc18, bc19, bc20, bc21
MOD LOFD-0
CDMA2 01112/ UTRAN Default Value: None
000BCS TDLOF and
CELLO D-00111 CDMA2
P 2 000
RMV MOCN
CDMA2 Flexible
000BCS Priority
CELLO Based
P Campin
g
Cdma20 CnOper ADD LOFD-0 CS Meaning: Indicates the ID of the operator. This
00BcSC atorID CDMA2 01035/ Fallback parameter applies only to LTE FDD and LTE TDD.
ellOp 000BCS TDLOF to GUI Value Range: 0~5
CELLO D-00103 CDMA2
P 5 000 Unit: None
LST LOFD-0 1xRTT Actual Value Range: 0~5

CDMA2 01021/ PS Inter- Default Value: None
000BCS TDLOF RAT
CELLO D-00102 Mobility
P 1 between
MOD LOFD-0 E-
CDMA2 01112/ UTRAN
000BCS TDLOF and
CELLO D-00111 CDMA2
P 2 000
RMV MOCN
CDMA2 Flexible
000BCS Priority
CELLO Based
P Campin
g

eRAN

nd
Cdma20 Cdma1 ADD LOFD-0 CS Meaning: Indicates whether to configure a dedicated

00BcSC XrttCell CDMA2 01035/ Fallback cell-reselection priority based on the PLMN ID of the
ellOp ReselPri 000BCS TDLOF to local cell for the CDMA2000 1xRTT band class. This
Ind CELLO D-00103 CDMA2 parameter applies only to LTE FDD and LTE TDD.
P 5 000 GUI Value Range: NOT_CFG(Not configure),
MOD TDLBF 1xRTT CFG(Configure)
CDMA2 D-00101 S1-flex Unit: None
000BCS 8 MOCN
CELLO Actual Value Range: NOT_CFG, CFG
LOFD-0 Flexible
P 01112/ Priority Default Value: NOT_CFG(Not configure)
LST TDLOF Based
CDMA2 D-00111 Campin
000BCS 2 g
CELLO LOFD-0 RAN
P 01036/ Sharing
TDLOF with
D-00103 Commo
6 n
Carrier

eRAN

nd
Cdma20 Cdma1 ADD LOFD-0 CS Meaning: Indicates the dedicated cell reselection
00BcSC XrttCell CDMA2 01035/ Fallback priority for a CDMA2000 1xRTT band class based on
ellOp ReselDe 000BCS TDLOF to the PLMN ID of the local cell. The value 0 indicates
diPri CELLO D-00103 CDMA2 the lowest priority. If the related SPID configuration is
P 5 000 specified, set this priority to the one specified in the
MOD TDLBF 1xRTT SPID configuration. If no related SPID configuration
CDMA2 D-00101 S1-flex is specified but this parameter is set, the eNodeB
000BCS 8 delivers the cell reselection priorities of all PLMNs
MOCN supported by a UE by using the IE idleModeMobility-
CELLO TDLOF Flexible
P ControlInfo in an RRC Connection Release message
D-00111 Priority to the UE. If no related SPID configuration is
LST 2 Based specified and this parameter is not set, a UE uses the
CDMA2 LBFD-0 Campin cell reselection priority of the CDMA2000 band class,
000BCS 0201803 g which is broadcast in the system information. This
CELLO / Cell parameter applies only to LTE FDD and LTE TDD.
P TDLBF Selectio GUI Value Range: 0~7
D-00201 n and
803 Re- Unit: None
LOFD-0 selection Actual Value Range: 0~7
01036/ RAN Default Value: 0
TDLOF Sharing
D-00103 with
6 Commo
LOFD-0 n
01112 Carrier
MOCN
Flexible
Priority
Based
Campin
g

eRAN

nd
Cdma20 HrpdCel ADD LOFD-0 PS Inter- Meaning: Indicates whether to configure a dedicated
00BcSC lReselD CDMA2 01021/ RAT cell-reselection priority for a CDMA2000 HRPD band
ellOp ediPriCf 000BCS TDLOF Mobility class based on the PLMN ID of the local cell. This
gInd CELLO D-00102 between parameter applies only to LTE FDD and LTE TDD.
P 1 E- GUI Value Range: NOT_CFG(Not configure),
MOD LOFD-0 UTRAN CFG(Configure)
CDMA2 01112/ and
CDMA2 Unit: None
000BCS TDLOF
CELLO D-00111 000 Actual Value Range: NOT_CFG, CFG
P 2 MOCN Default Value: NOT_CFG(Not configure)
LST LOFD-0 Flexible
CDMA2 01036/ Priority
000BCS TDLOF Based
CELLO D-00103 Campin
P 6 g
RAN
Sharing
with
Commo
n
Carrier

eRAN

nd
Cdma20 HrpdCel ADD LOFD-0 PS Inter- Meaning: Indicates the dedicated cell reselection
00BcSC lReselD CDMA2 01021/ RAT priority for a CDMA2000 HRPD band class based on
ellOp ediPri 000BCS TDLOF Mobility the PLMN ID of the local cell. The value 0 indicates
CELLO D-00102 between the lowest priority. If the related SPID configuration is
P 1 E- specified, set this priority to the one specified in the
MOD LOFD-0 UTRAN SPID configuration. If no related SPID configuration
CDMA2 01112/ and is specified but this parameter is set, the eNodeB
000BCS TDLOF CDMA2 delivers the cell reselection priorities of all PLMNs
CELLO D-00111 000 supported by a UE by using the IE idleModeMobility-
P 2 MOCN ControlInfo in an RRC Connection Release message
Flexible to the UE. If no related SPID configuration is
LST LBFD-0 specified and this parameter is not set, a UE uses the
CDMA2 0201803 Priority
Based cell reselection priority of the CDMA2000 band class,
000BCS / which is broadcast in the system information. This
CELLO TDLBF Campin
g parameter applies only to LTE FDD and LTE TDD.
P D-00201
803 Cell GUI Value Range: 0~7
LOFD-0 Selectio Unit: None
01036/ n and Actual Value Range: 0~7
TDLOF Re-
selection Default Value: 0
D-00103
6 RAN
Sharing
with
Commo
n
Carrier

eRAN

nd
License UserNu ADD TDLBF License Meaning: Indicates the proportion of users that the
Sharing mSharin LICENS D-00401 Manage operator can share with other operators when the
Policy gRate ESHAR 4 ment eNodeB is shared among operators. This parameter
INGPO LOFD-0 RAN must be set based on the contract signed with
LICY 01036/ Sharing operators. This parameter applies only to LTE FDD.
MOD TDLOF with GUI Value Range: 0~100
LICENS D-00103 Commo Unit: %
ESHAR 6 n
INGPO Carrier Actual Value Range: 0~100
LOFD-0
LICY 01037/ RAN Default Value: 0
LST TDLOF Sharing
LICENS D-00103 with
ESHAR 7 Dedicate
INGPO LOFD-0 d
LICY 70206 Carrier
LOFD-0 Hybrid
70213 RAN
Sharing
Fair
User
Sharing
CnOpSh Primary ADD LOFD-0 Hybrid Meaning: Indicates the ID of the primary operator in a
aringGr Operator CNOPS 70206/ RAN carrier-sharing operator group.
oup Id HARIN TDLOF Sharing GUI Value Range: 0~5
GGROU D-08122
P 4 Unit: None
MOD Actual Value Range: 0~5

CNOPS Default Value: None
HARIN
GGROU
P
LST
CNOPS
HARIN
GGROU
P

eRAN

nd
CnOpSh Seconda LST LOFD-0 Hybrid Meaning: Indicates the list of secondary operators in a
aringGr ryOperat CNOPS 70206/ RAN carrier-sharing operator group.
oup orList HARIN TDLOF Sharing GUI Value Range: 0~5
GGROU D-08122
P 4 Unit: None
ADD Actual Value Range: 0~5

SECON Default Value: None
DARYO
P2GRO
UP
LST
SECON
DARYO
P2GRO
UP
RMV
SECON
DARYO
P2GRO
UP
Cell CnOpSh ADD LOFD-0 Hybrid Meaning: Indicates the ID of the eNodeB operator
aringGr CELL 70206/ RAN group that shares the cell. This parameter must be set
oupId MOD TDLOF Sharing to a value within the range of 0 to 5 if the eNodeB
CELL D-08122 works in hybrid RAN sharing mode. This parameter
4 must be set to 255 (an invalid value) in independent
LST RAN sharing, RAN sharing with dedicated carrier, or
CELL RAN sharing with common carrier mode.
GUI Value Range: 0~5,255
Unit: None
Actual Value Range: 0~5,255
Default Value: 255

eRAN

nd
CnOpSh CnOpSh ADD LOFD-0 Hybrid Meaning: Indicates the ID of a carrier-sharing

aringGr aringGr CNOPS 70206/ RAN operator group. This parameter uniquely specifies a
oup oupId HARIN TDLOF Sharing carrier-sharing operator group.
GGROU D-08122 GUI Value Range: 0~5
P 4
Unit: None
ADD
SECON Actual Value Range: 0~5
DARYO Default Value: None
P2GRO
UP
LST
CNOPS
HARIN
GGROU
P
LST
SECON
DARYO
P2GRO
UP
MOD
CNOPS
HARIN
GGROU
P
RMV
CNOPS
HARIN
GGROU
P
RMV
SECON
DARYO
P2GRO
UP

eRAN

nd
Cell LocalCe ACT None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELL identifies a cell within a BS.
ADD GUI Value Range: 0~255
CELL Unit: None
ADD Actual Value Range: 0~255
CELLB
Default Value: None
AND
BLK
CELL
DEA
CELL
DSP
CELL
DSP
CELLC
ALIBR
ATION
DSP
CELLC
AMCST
ATUS
DSP
CELLH
LHCHK
DSP
CELLL
AA
DSP
CELLP
HYTOP
O
DSP
CELLU
LCOMP
CLUST
ER
DSP
CELLU
LICCL
USTER
DSP
DDCEL
LGROU
P

eRAN

nd
DSP
LIOPTR
ULE
DSP
PRIBBP
ADJUS
T
LST
CELL
LST
CELLB
AND
MOD
CELL
RMV
CELL
RMV
CELLB
AND
RMV
CELLN
RT
RST
EUCEL
LRES
STR
CELLH
LHCHK
STR
CELLR
FLOOP
BACK
STR
CELLS
ELFTES
T
STR
LRTWP
RTTST
STR
PRIBBP
ADJUS
T

eRAN

nd
UBL
CELL
DSP
CELLB
YLOCA
TION
DSP
LRTWP
RTTST
DSP
PRIBBP
RESINF
O
S1 S1Id ADD S1 LBFD-0 Star Meaning: Indicates the S1 object ID.

DSP S1 0300101 Topolog GUI Value Range: 0~31
/ y
LST S1 TDLBF Unit: None
Chain
MOD D-00300 Topolog Actual Value Range: 0~31
S1 101 y Default Value: None
RMV LBFD-0 Tree
S1 0300102 Topolog
/ y
TDLBF
D-00300 S1-flex
102
LBFD-0
0300103
/
TDLBF
D-00300
103
LBFD-0
01018/
TDLBF
D-00101
8

eRAN

nd
S1 CnOpSh ADD S1 LOFD-0 Hybrid Meaning: Indicates the ID of a carrier-sharing

aringGr MOD 70206/ RAN operator group that shares the S1 MO. If the eNodeB
oupId S1 TDLOF Sharing works in hybrid RAN sharing mode, set this parameter
D-08122 to a value within the range from 0 to 5. If the eNodeB
LST S1 4 works in independent operator mode, RAN sharing
with common carriers mode, or RAN sharing with
dedicated carriers mode, retain the default value 255,
which is an invalid value.
Unit: None
Default Value: 255
S1Interf S1Interf ADD LBFD-0 Star Meaning: Indicates the S1 interface ID. If the S1
ace aceId S1INTE 0300101 Topolog interface is set up based on the endpoint configuration
RFACE / y mode, the value range is 40000 to 65534. If the S1
BLK TDLBF Chain interface is set up based on the link configuration
S1INTE D-00300 Topolog mode using the CME or MML commands, the
RFACE 101 y recommended value range is 0 to 39999.
DSP LBFD-0 Tree GUI Value Range: 0~65534
S1INTE 0300102 Topolog Unit: None
RFACE / y
TDLBF Actual Value Range: 0~65534
MOD D-00300 S1-flex Default Value: None
S1INTE 102
RFACE
LBFD-0
RMV 0300103
S1INTE /
RFACE TDLBF
RST D-00300
S1INTE 103
RFACE LBFD-0
UBL 01018/
S1INTE TDLBF
RFACE D-00101
8

eRAN

nd
S1Interf CnOpSh ADD LOFD-0 Hybrid Meaning: Indicates the ID of a carrier-sharing

ace aringGr S1INTE 70206/ RAN operator group that shares the S1Interface MO. If the
oupId RFACE TDLOF Sharing eNodeB works in hybrid RAN sharing mode, set this
MOD D-08122 parameter to a value within the range from 0 to 5. If
S1INTE 4 the eNodeB works in independent operator mode,
RFACE RAN sharing with common carriers mode, or RAN
sharing with dedicated carriers mode, retain the
DSP default value 255, which is an invalid value.
S1INTE
RFACE GUI Value Range: 0~5,255
Unit: None
Default Value: 255
X2 X2Id ADD LBFD-0 Star Meaning: Indicates the X2 MO ID.

X2 0300101 Topolog GUI Value Range: 0~11
DSP X2 / y
TDLBF Unit: None
LST X2 Chain
D-00300 Topolog Actual Value Range: 0~11
MOD 101 y Default Value: None
X2 LBFD-0 Tree
RMV 0300102 Topolog
X2 / y
TDLBF
D-00300
102
LBFD-0
0300103
/
TDLBF
D-00300
103
X2 CnOpSh ADD LOFD-0 Hybrid Meaning: Indicates the ID of a carrier-sharing

aringGr X2 70206/ RAN operator group that shares the X2 MO. If the eNodeB
oupId MOD TDLOF Sharing works in hybrid RAN sharing mode, set this parameter
X2 D-08122 to a value within the range from 0 to 5. If the eNodeB
4 works in independent mode, RAN sharing with
LST X2 common carriers mode, or RAN sharing with
which is an invalid value.
Unit: None
Default Value: 255

eRAN

nd
X2Interf X2Interf ADD LBFD-0 Star Meaning: Indicates the X2 interface ID. If the X2
ace aceId X2INTE 0300101 Topolog interface is set up based on the end point configuration
RFACE / y mode, the value range is 40000 to 65535. If the X2
DSP TDLBF Chain interface is set up based on the link configuration
X2INTE D-00300 Topolog mode using the CME or MML commands, the
RFACE 101 y recommended value range is 0 to 39999.
DSP LBFD-0 Tree GUI Value Range: 0~65535
X2UPIN 0300102 Topolog Unit: None
FO / y
TDLBF Actual Value Range: 0~65535
MOD D-00300 Default Value: None
X2INTE 102
RFACE
LBFD-0
RMV 0300103
X2INTE /
RFACE TDLBF
RST D-00300
X2INTE 103
RFACE
X2Interf CnOpSh ADD LOFD-0 Hybrid Meaning: Indicates the ID of a carrier-sharing

ace aringGr X2INTE 70206/ RAN operator group that shares the X2 Interface MO. If the
oupId RFACE TDLOF Sharing eNodeB works in hybrid RAN sharing mode, set this
MOD D-08122 parameter to a value within the range from 0 to 5. If
X2INTE 4 the eNodeB works in independent mode, RAN sharing
RFACE with common carriers mode, or RAN sharing with
DSP which is an invalid value.
X2INTE
RFACE GUI Value Range: 0~5,255
Unit: None
Default Value: 255

eRAN

nd
CellRes CellRes MOD LBFD-0 Cell Meaning: Indicates the cell reselection priority of the
el elPriorit CELLR 0201803 Selectio serving frequency. The value 0 indicates the lowest
y ESEL / n and priority. The value of this parameter must be
LST TDLBF Re- determined together with the priorities of other
CELLR D-00201 selection frequencies during the network planning. Frequencies
ESEL 803 Broadca used for different RATs must be assigned different cell
LBFD-0 st of reselection priorities. This parameter applies only to
02009/ system LTE FDD and LTE TDD.
TDLBF informat GUI Value Range: 0~7
D-00200 ion Unit: None
9 PS Inter- Actual Value Range: 0~7
LOFD-0 RAT
01021/ Mobility Default Value: 7
TDLOF between
D-00102 E-
1 UTRAN
LOFD-0 and
01111 CDMA2
000
LOFD-0
01112/ PS
TDLOF Mobility
D-00111 from E-
2 UTRAN
to
CDMA2
000
HRPD
Based
on
Frequen
cy-
specific
Factors
MOCN
Flexible
Priority
Based
Campin
g

eRAN

nd
CellHoP CellHo MOD LBFD-0 Coverag Meaning:

araCfg AlgoSwi CELLH 0201802 e Based Indicates whether to enable handover algorithms. This
tch OPARA / Inter- parameter provides the following options:
CFG TDLBF frequenc
LST D-00201 y InterFreqCoverHoSwitch: If this option is selected,
CELLH 802 Handov coverage-based inter-frequency handovers are enabled
OPARA LOFD-0 er to ensure service continuity. If this option is
CFG 01047 LoCatio deselected, coverage-based inter-frequency handovers
n are disabled. This option applies only to LTE FDD
LBFD-0 and LTE TDD.
02028 Services
(LCS) EmcInterFreqBlindHoSwitch: If this option is
TDLOF
D-07022 Emerge selected, the eNodeB preferentially performs an inter-
8 ncy Call frequency blind redirection when an emergency blind
Service- handover is triggered. If this option is deselected, the
Request eNodeB only performs an inter-RAT blind handover
Based when an emergency blind handover is triggered. This
Inter- option applies only to LTE FDD and LTE TDD.
frequenc InterFreqSpeedHoSwitch: If this option is selected,
y speed-based inter-frequency handovers are enabled.
Handov This algorithm allows UEs that are running GBR
er services and move at a high speed to be handed over
to operator-specific neighboring frequencies with
better coverage. In addition, the eNodeB does not
perform load-based and other unnecessary handovers
for these UEs. If this option is deselected, speed-based
inter-frequency handovers are disabled. This option
IfCoverPreBlindHoSwitch: If this option is selected,
the eNodeB preferentially performs coverage-based
inter-frequency handovers in a blind manner. That is,
the eNodeB does not have to deliver measurement
configuration to UEs in the handovers. If this option is
deselected, the eNodeB performs the handovers in a
measurement-based manner. That is, the eNodeB
delivers measurement configuration to UEs in the
handovers. This option applies only to LTE FDD and
LTE TDD.
InterFreqLcsHoSwitch: If this option is selected and
the OTDOA function is enabled, OTDOA-capable
emergency UEs in the cell are allowed to be handed
over to cells on a frequency with the
LcsMobilityTargetInd option of the MobilityTargetInd
parameter selected and such UEs are not allowed to be
handed over to cells on other frequencies through
unnecessary low-priority handovers. If this option is
deselected, the serving eNodeB does not perform

eRAN

nd
positioning-based inter-frequency handovers and can

perform other types of unnecessary inter-frequency
handovers for OTDOA-capable emergency UEs. This
SevReqHoFailNotifyMmeSw: If the eNodeB re-
receives a QCI 1 bearer setup request that is re-sent
from the MME after a service-request-based inter-
frequency handover is triggered, the eNodeB and the
MME perform as follows: If this option is selected
and the eNodeB does not receive any measurement
report for a service-request-based handover, the
eNodeB responds with a special cause value "Failure
in the Radio Interface Procedure" to the MME. The
MME immediately transfers the voice call procedure
from the VoIP procedure to a CSFB procedure when
receiving the cause value. If this option is deselected,
the eNodeB directly responds with a cause value "S1
intra system Handover triggered" to the MME. The
MME does not transfer the voice call procedure from
the VoIP procedure to a CSFB procedure when
receiving the cause value. This option applies only to
GUI Value Range: InterFreqCoverHoSwitch,
EmcInterFreqBlindHoSwitch, InterFreqSpeedHoS-
witch, IfCoverPreBlindHoSwitch, InterFreqLcsHoS-
witch, SevReqHoFailNotifyMmeSw
Unit: None
Actual Value Range: InterFreqCoverHoSwitch,
EmcInterFreqBlindHoSwitch, InterFreqSpeedHoS-
witch, IfCoverPreBlindHoSwitch, InterFreqLcsHoS-
witch, SevReqHoFailNotifyMmeSw
Default Value: InterFreqCoverHoSwitch:On,
EmcInterFreqBlindHoSwitch:Off,
InterFreqSpeedHoSwitch:Off, IfCoverPreBlindHoS-
witch:Off, InterFreqLcsHoSwitch:Off,
SevReqHoFailNotifyMmeSw:Off

eRAN

nd
CellHoP HoMode MOD LOFD-0 SRVCC Meaning:

araCfg Switch CELLH 01022/ to Indicates the handover method switches based on
OPARA TDLOF UTRAN which the eNodeB determines handover policies.
CFG D-00102 SRVCC
2 BlindHoSwitch: This option specifies whether to
LST to
enable blind handover for CSFB. Bind handover for
CELLH LOFD-0 GERAN
CSFB is enabled only if this option is selected. A
OPARA 01023/ CS blind handover for CSFB can be triggered only if both
CFG TDLOF Fallback this option and the BlindHoSwitch option of the
D-00102 to HoModeSwitch parameter in the ENodeBAlgoSwitch
3 UTRAN MO are selected. This option applies only to LTE
LOFD-0 CS FDD and LTE TDD.
01033/ Fallback
TDLOF UtranPsHoSwitch: PS handover to UTRAN is
to
D-00103 supported only if this option is selected. This option
GERAN
3 applies only to LTE FDD and LTE TDD.
PS Inter-
LOFD-0 RAT UtranSrvccSwitch: SRVCC to UTRAN is supported
01034/ Mobility only if this option is selected. This option applies only
TDLOF between to LTE FDD and LTE TDD.
D-00103 E-
4 GeranSrvccSwitch: SRVCC to GERAN is supported
UTRAN only if this option is selected. This option applies only
LOFD-0 and to LTE FDD and LTE TDD.
01019/ UTRAN
TDLOF PS Inter- UtranRedirectSwitch: Redirection to UTRAN is
D-00101 RAT supported only if this option is selected. This option
9 Mobility applies only to LTE FDD and LTE TDD.
LOFD-0 between GeranRedirectSwitch: Redirection to GERAN is
01020/ E- supported only if this option is selected. This option
TDLOF UTRAN applies only to LTE FDD and LTE TDD.
D-00102 and
0 GERAN UFCsfbBlindHoDisSwitch: If both the
BlindHoSwitch and UFCsfbBlindHoDisSwitch
LOFD-0 Ultra-
options are selected, the eNodeB performs a
70202/ Flash
measurement-based handover for a UE during an
TDLOF CSFB to
ultra-flash CSFB to UTRAN or GERAN. If the
D-08122 UTRAN
BlindHoSwitch option is selected and the
3 Ultra- UFCsfbBlindHoDisSwitch option is deselected, the
LOFD-0 Flash eNodeB performs a blind handover for the UE during
81283/ CSFB to the ultra-flash CSFB to UTRAN or GERAN. This
TDLOF GERAN option applies only to LTE FDD and LTE TDD.
D-08120 Handov
3 HighSpeedCsfbBlindSwitch: If this option is selected,
er the eNodeB can perform blind handovers for high-
LOFD-0 Enhance speed UEs in CSFB. If this option is deselected,
81228/ ment at whether the eNodeB can perform blind handovers is
TDLOF Speed controlled by the BlindHoSwitch option of the
D-08020 Mobility HoModeSwitch parameter in the ENodeBAlgoSwitch
5 MO and the BlindHoSwitch option of the
HoModeSwitch parameter in the CellHoParaCfg MO,

eRAN

nd
LBFD-0 Mobility and blind handovers can be triggered only if these two
02018/ Manage options are selected. This option applies only to LTE
TDLBF ment FDD and LTE TDD.
D-00201 NSA GUI Value Range: BlindHoSwitch(BlindHoSwitch),
8 Network UtranPsHoSwitch(UtranPsHoSwitch),
MRFD- ing UtranSrvccSwitch(UtranSrvccSwitch),
131122 based on GeranSrvccSwitch(GeranSrvccSwitch),
MRFD- EPC(LT UtranRedirectSwitch(UtranRedirectSwitch),
131132 E FDD) GeranRedirectSwitch(GeranRedirectSwitch),
NSA UFCsfbBlindHoDisSwitch(UFCsfbBlindHoDisS-
Network witch), HighSpeedCsfbBlind-
ing Switch(HighSpeedCsfbBlindSwitch)
based on Unit: None
EPC(LT Actual Value Range: BlindHoSwitch,
E TDD) UtranPsHoSwitch, UtranSrvccSwitch,
GeranSrvccSwitch, UtranRedirectSwitch,
GeranRedirectSwitch, UFCsfbBlindHoDisSwitch,
HighSpeedCsfbBlindSwitch
Default Value: BlindHoSwitch:Off,
UtranPsHoSwitch:Off, UtranSrvccSwitch:Off,
GeranSrvccSwitch:Off, UtranRedirectSwitch:Off,
GeranRedirectSwitch:Off, UFCsfbBlindHoDisS-
witch:Off, HighSpeedCsfbBlindSwitch:Off

eRAN

nd
ENodeB HoMode MOD LOFD-0 SRVCC Meaning:

AlgoSwi Switch ENODE 01022/ to Indicates whether to enable different types of
tch BALGO TDLOF UTRAN handovers, based on which the eNodeB determines
SWITC D-00102 SRVCC handover policies.
H 2 to
UtranVoipCapSwitch: If this option is selected,
LST LOFD-0 GERAN
UTRAN supports VoIP. If this option is deselected,
ENODE 01023/ CS UTRAN does not support VoIP. This option applies
BALGO TDLOF Fallback only to LTE FDD and LTE TDD.
SWITC D-00102 to
H 3 UTRAN GeranPsHoSwitch: If this option is selected, GERAN
LOFD-0 supports PS handovers. If this option is deselected,
CS GERAN does not support PS handovers. This option
01033/
Fallback applies only to LTE FDD and LTE TDD.
TDLOF
to
D-00103 CdmaHrpdNonOptimisedHoSwitch: If this option is
GERAN
3 selected, non-optimized handovers to CDMA2000
PS Inter-
LOFD-0 HRPD are enabled. If this option is deselected, non-
RAT
01034/ optimized handovers to CDMA2000 HRPD are
Mobility
TDLOF disabled. This option applies only to LTE FDD and
between
D-00103 LTE TDD.
E-
4
UTRAN CdmaHrpdOptimisedHoSwitch: If this option is
LOFD-0 and selected, optimized handovers to CDMA2000 HRPD
01019/ UTRAN are enabled. If this option is deselected, optimized
TDLOF handovers to CDMA2000 HRPD are disabled. This
PS Inter-
D-00101 option applies only to LTE FDD and LTE TDD.
RAT
9
Mobility GeranNaccSwitch: This option does not take effect if
LOFD-0 between
01020/ GeranCcooption is deselected. If this option is
E- selected, the GERAN supports network assisted cell
TDLOF UTRAN
D-00102 change (NACC). If this option is deselected, the
and GERAN does not support NACC. This option applies
0 GERAN only to LTE FDD and LTE TDD.
LOFD-0 PS Inter-
01021/ GeranCcoSwitch: If this option is selected, the
RAT
TDLOF GERAN supports cell change order (CCO). If this
Mobility
D-00102 option is deselected, the GERAN does not support
between
1 CCO. This option applies only to LTE FDD and LTE
E-
TDD.
LOFD-0 UTRAN
01052/ and Cdma1xRttSrvccSwitch: If this option is selected, the
TDLOF CDMA2 CDMA2000 1xRTT supports SRVCC. If this option is
D-00105 000 deselected, the CDMA2000 1xRTT does not support
2 Flash SRVCC. This option applies only to LTE FDD and
LOFD-0 CS LTE TDD.
01088/ Fallback CdmaHrpdRedirectSwitch: If this option is selected,
TDLOF to redirection to CDMA2000 HRPD is enabled. If this
D-00108 UTRAN option is deselected, redirection to CDMA2000 HRPD
8 CS is disabled. This option applies only to LTE FDD and
Fallback LTE TDD.

eRAN

nd
LOFD-0 Steering Cdma1xRttRedirectSwitch: If this option is selected,

01043/ to redirection to CDMA2000 1xRTT is enabled. If this
TDLOF UTRAN option is deselected, redirection to CDMA2000
D-00104 Service 1xRTT is disabled. This option applies only to LTE
3 based FDD and LTE TDD.
LOFD-0 Inter-
01072/ RAT BlindHoSwitch: If this option is selected, blind
TDLOF handove handovers for CSFB are enabled. If this option is
D-00107 r to deselected, blind handovers for CSFB are disabled. If
2 UTRAN both this option and the BlindHoSwitch option of the
Handover Mode switch parameter of the
LOFD-0 Distance CellHoParaCfg MO are selected, blind CSFB
01046/ based handovers for CSFB are enabled. This option applies
TDLOF Inter- only to LTE FDD and LTE TDD.
D-00104 RAT
6 handove LcsSrvccSwitch: If this option is selected, an SRVCC
LOFD-0 r to procedure is triggered when a UE receives a CSFB
01073/ UTRAN instruction during a VoIP service. If this option is
TDLOF Service deselected, an SRVCC procedure is not triggered
D-00107 based when a UE receives a CSFB instruction during a VoIP
3 Inter- service. This option applies only to LTE FDD and
LBFD-0 RAT LTE TDD.
02018/ handove
r to AutoGapSwitch: If this option is selected and UEs
TDLBF
GERAN support automatic measurement gap configurations on
D-00201
the target frequency, the eNodeB does not deliver gap
8 Distance configurations to UEs. If this option is deselected, the
LOFD-0 based eNodeB delivers gap configurations to UEs during all
01111/ Inter- inter-frequency and inter-RAT measurements. When
TDLOF RAT the eNodeB determines to deliver measurement
D-00111 handove configuration of NR frequencies, if this option is
1 r to selected and UEs support autonomous measurement
MRFD- GERAN gap configurations on the target frequency, the
131122 Mobility eNodeB does not deliver gap configurations to UEs. If
Manage this option is deselected, the eNodeB delivers gap
MRFD-
ment configurations to UEs during all inter-frequency and
131132
inter-RAT measurements. This option applies only to
PS LTE FDD and LTE TDD.
Mobility
from E- UeVoipOnHspaCapSwitch: If this option is selected
UTRAN and the eNodeB attempts to hand over UEs using
to voice services to UTRAN, the eNodeB checks UE
CDMA2 capabilities when determining whether PS handover is
000 applied. The UE capability information must include
HRPD voiceOverPS-HS-UTRA-FDD-r9 if the target
Based UTRAN cell works in FDD mode or voiceOverPS-
on HS-UTRA-TDD128-r9 if the target UTRAN cell
Frequen works in TDD mode. If this option is deselected, the
cy- eNodeB does not check UE capabilities when handing

eRAN

nd
specific over UEs to UTRAN based on PS handovers. This

Factors option applies only to LTE FDD and LTE TDD.
NSA UtranFddB1CapSwitch: If this option is selected, the
Network setting of bit 41 of FGI specifying the UE capability
ing of event B1 measurement on FDD UTRAN cells must
based on be considered. If this option is deselected, the setting
EPC(LT of bit 41 of FGI does not need to be considered. This
E FDD) option applies only to LTE FDD and LTE TDD.
NSA CdmaHrpdNonOptMeaHoSwitch: If this option is
Network selected, measurement-based non-optimized
ing handovers to CDMA2000 HRPD are enabled. If this
based on option is deselected, measurement-based non-
EPC(LT optimized handovers to CDMA2000 HRPD are
E TDD) disabled. This option applies only to LTE FDD and
LTE TDD.
GUI Value Range:
UtranVoipCapSwitch(UtranVoipCapSwitch),
GeranPsHoSwitch(GeranPsHoSwitch),
CdmaHrpdNonOptimisedHoS-
witch(CdmaHrpdNonOptimisedHoSwitch),
CdmaHrpdOptimisedHoSwitch(CdmaHrpdOptimised-
HoSwitch), GeranNaccSwitch(GeranNaccSwitch),
GeranCcoSwitch(GeranCcoSwitch),
Cdma1xRttSrvccSwitch(Cdma1xRttSrvccSwitch),
CdmaHrpdRedirectSwitch(CdmaHrpdRedirectS-
witch),
Cdma1xRttRedirectSwitch(Cdma1xRttRedirectSwitch
), BlindHoSwitch(BlindHoSwitch),
LcsSrvccSwitch(LcsSrvccSwitch),
AutoGapSwitch(AutoGapSwitch),
UeVoipOnHspaCapSwitch(UeVoipOnHspaCapS-
witch),
UtranFddB1CapSwitch(UtranFddB1CapSwitch),
CdmaHrpdNonOptMeaHoS-
witch(CdmaHrpdNonOptMeaHoSwitch)
Unit: None
Actual Value Range: UtranVoipCapSwitch,
GeranPsHoSwitch, CdmaHrpdNonOptimisedHoS-
witch, CdmaHrpdOptimisedHoSwitch,
GeranNaccSwitch, GeranCcoSwitch,
Cdma1xRttSrvccSwitch, CdmaHrpdRedirectSwitch,
Cdma1xRttRedirectSwitch, BlindHoSwitch,
LcsSrvccSwitch, AutoGapSwitch,
UeVoipOnHspaCapSwitch, UtranFddB1CapSwitch,
CdmaHrpdNonOptMeaHoSwitch
Default Value: UtranVoipCapSwitch:Off,
GeranPsHoSwitch:Off, CdmaHrpdNonOptimised-

eRAN

nd
HoSwitch:Off, CdmaHrpdOptimisedHoSwitch:Off,
GeranNaccSwitch:Off, GeranCcoSwitch:Off,
Cdma1xRttSrvccSwitch:Off, CdmaHrpdRedirectS-
witch:Off, Cdma1xRttRedirectSwitch:Off,
BlindHoSwitch:Off, LcsSrvccSwitch:Off,
AutoGapSwitch:Off, UeVoipOnHspaCapSwitch:Off,
UtranFddB1CapSwitch:Off, CdmaHrpdNonOptMea-
HoSwitch:Off
CellDlsc MultiCa MOD TDLOF Inter- Meaning:

hAlgo rrierCoS CELLD D-12120 eNodeB Indicates whether to enable the multi-carrier
chAlgoS LSCHA 3 Multi- coordinated scheduling algorithm.
w LGO Carrier
LST Coordin MULTI_CARRIER_COSCH_SW: Indicates whether
CELLD ated to enable the multi-carrier coordinated scheduling
LSCHA Scheduli algorithm. If this option is selected, multi-carrier
LGO ng coordinated scheduling is enabled. If this option is
deselected, multi-carrier coordinated scheduling is
disabled.
ADAPTIVE_FREQ_PRIORITY_SW: Indicates
whether to adaptively adjust the frequency priority. If
both this option and the
MULTI_CARRIER_COSCH_SW option are selected,
the eNodeB adaptively adjusts the frequency priority.
If this option is deselected, the eNodeB does not
adaptively adjust the frequency priority. This
parameter applies only to LTE TDD.
GUI Value Range:
MULTI_CARRIER_COSCH_SW(MULTI_CARRIE
R_COSCH_SW),
ADAPTIVE_FREQ_PRIORITY_SW(ADAPTIVE_F
REQ_PRIORITY_SW)
Unit: None
Actual Value Range:
MULTI_CARRIER_COSCH_SW,
ADAPTIVE_FREQ_PRIORITY_SW
Default Value: MULTI_CARRIER_COSCH_SW:Off,
ADAPTIVE_FREQ_PRIORITY_SW:Off

eRAN

nd
CellRes LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
elGeran llId CELLR identifies a cell within an eNodeB. This parameter
ESELG applies only to LTE FDD and LTE TDD.
ERAN GUI Value Range: 0~255
LST Unit: None
CELLR
ESELG Actual Value Range: 0~255
ERAN Default Value: None
MOD
CELLR
ESELG
ERAN
RMV
CELLR
ESELG
ERAN
CellRes TReselG ADD LBFD-0 Cell Meaning: Indicates the evaluation period for a UE to
elGeran eran CELLR 0201803 Selectio determine whether to reselect a neighboring GERAN
ESELG / n and cell to camp on. During the evaluation period, if the
ERAN TDLBF Re- signal quality in a neighboring GERAN cell is better
MOD D-00201 selection than that in the serving cell and a UE camps on the
CELLR 803 Broadca serving cell for more than 1s, the UE attempts to
ESELG LBFD-0 st of reselect the neighboring GERAN cell to camp on.
ERAN 02009/ system This parameter applies only to LTE FDD and LTE
TDLBF informat TDD.
LST
CELLR D-00200 ion GUI Value Range: 0~7
ESELG 9 MOCN Unit: s
ERAN LOFD-0 Flexible Actual Value Range: 0~7
01112/ Priority
TDLOF Based Default Value: 1
D-00111 Campin
2 g

eRAN

nd
elUtran llId CELLR identifies a cell within an eNodeB. This parameter
ESELU applies only to LTE FDD and LTE TDD.
TRAN GUI Value Range: 0~255
LST Unit: None
CELLR
ESELU Actual Value Range: 0~255
TRAN Default Value: None
MOD
CELLR
ESELU
TRAN
RMV
CELLR
ESELU
TRAN
CellRes TReselU ADD LBFD-0 Broadca Meaning: Indicates the evaluation period for a UE to
elUtran tran CELLR 02009/ st of determine whether to reselect a neighboring UTRAN
ESELU TDLBF system cell to camp on. During the evaluation period, if the
TRAN D-00200 informat signal quality in a neighboring UTRAN cell is better
MOD 9 ion than that in the serving cell and a UE camps on the
CELLR LBFD-0 Cell serving cell for more than 1s, the UE attempts to
ESELU 0201803 Selectio reselect the neighboring UTRAN cell to camp on.
TRAN / n and This parameter applies only to LTE FDD and LTE
TDLBF Re- TDD.
LST
CELLR D-00201 selection GUI Value Range: 0~7
ESELU 803 MOCN Unit: s
TRAN LOFD-0 Flexible Actual Value Range: 0~7
01112/ Priority
D-00111 Campin
2 g
CellRes LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
el llId CELLR identifies a cell within a BS.
ESEL GUI Value Range: 0~255
MOD Unit: None
CELLR
ESEL Actual Value Range: 0~255
Default Value: None

eRAN

nd
CellRes TReselE MOD LBFD-0 Cell Meaning: Indicates the evaluation period for a UE to
el utran CELLR 0201803 Selectio determine whether to perform cell reselections to a
ESEL / n and new E-UTRAN cell. If the signal quality of a new E-
LST TDLBF Re- UTRAN cell is better than that of the serving cell
CELLR D-00201 selection within the period specified by this parameter and a UE
ESEL 803 Broadca camps on the serving cell for more than 1s, the UE
LBFD-0 st of initiates cell reselections to the new E-UTRAN cell.
02009/ system This parameter applies only to LTE FDD and LTE
TDLBF informat TDD.
D-00200 ion GUI Value Range: 0~7
9 MOCN Unit: s
LOFD-0 Flexible Actual Value Range: 0~7
01112/ Priority
D-00111 Campin
2 g
elCdma llId CELLR identifies a cell within an eNodeB. This parameter
2000 ESELC applies only to LTE FDD and LTE TDD.
DMA20 GUI Value Range: 0~255
00
Unit: None
LST
CELLR Actual Value Range: 0~255
ESELC Default Value: None
DMA20
00
MOD
CELLR
ESELC
DMA20
00
RMV
CELLR
ESELC
DMA20
00

eRAN

nd
CellRes Treselec ADD LBFD-0 Cell Meaning: Indicates the evaluation period for a UE to
elCdma tionHrp CELLR 0201803 Selectio determine whether to reselect a neighboring
2000 d ESELC / n and CDMA2000 HRPD cell to camp on. During the
DMA20 TDLBF Re- evaluation period, if the signal quality in a
00 D-00201 selection neighboring CDMA2000 HRPD cell is better than that
MOD 803 PS Inter- in the serving cell and a UE camps on the serving cell
CELLR LOFD-0 RAT for more than 1s, the UE attempts to reselect the
ESELC 01021/ Mobility neighboring CDMA2000 HRPD cell to camp on. For
DMA20 TDLOF between details about this parameter, see 3GPP TS 36.331.
00 D-00102 E- This parameter applies only to LTE FDD and LTE
1 UTRAN TDD.
LST
CELLR LBFD-0 and GUI Value Range: 0~7
ESELC 02009/ CDMA2 Unit: s
DMA20 TDLBF 000
00 D-00200 Broadca
9 st of Default Value: 1
LOFD-0 system
01112/ informat
TDLOF ion
D-00111 MOCN
2 Flexible
Priority
Based
Campin
g

eRAN

nd
CellRes Cdma1 ADD LBFD-0 Cell Meaning: Indicates the evaluation period for a UE to
elCdma XrttTres CELLR 0201803 Selectio determine whether to reselect a neighboring
2000 election ESELC / n and CDMA2000 1xRTT cell to camp on. During the
DMA20 TDLBF Re- evaluation period, if the signal quality in a
00 D-00201 selection neighboring CDMA2000 1xRTT cell is better than
MOD 803 CS that in the serving cell and a UE camps on the serving
CELLR LOFD-0 Fallback cell for more than 1s, the UE attempts to reselect the
ESELC 01035/ to neighboring CDMA2000 1xRTT cell to camp on. For
DMA20 TDLOF CDMA2 details about this parameter, see 3GPP TS 36.331.
00 D-00103 000 This parameter applies only to LTE FDD and LTE
5 1xRTT TDD.
LST
CELLR LBFD-0 Broadca GUI Value Range: 0~7
ESELC 02009/ st of Unit: s
DMA20 TDLBF system Actual Value Range: 0~7
00 D-00200 informat
9 ion Default Value: 1
TDLOF Enhance
D-00109 d CS
0/ Fallback
LOFD-0 to
01090 CDMA2
LOFD-0 000
01112/ 1xRTT
TDLOF MOCN
D-00111 Flexible
2 Priority
Based
Campin
g

eRAN

nd
CnOper CnOper ADD LOFD-0 Multi Meaning: This parameter indicates the ID of the
atorSpid atorId CNOPE 70210/ Operator operator. This parameter applies only to LTE FDD and
Cfg RATOR TDLOF s SPID LTE TDD.
SPIDCF D-00113 Policy GUI Value Range: 0~5
G 3
Unit: None
LST
CNOPE Actual Value Range: 0~5
RATOR Default Value: None
SPIDCF
G
MOD
CNOPE
RATOR
SPIDCF
G
RMV
CNOPE
RATOR
SPIDCF
G

eRAN

nd
CnOper Spid ADD LOFD-0 Intra- Meaning: Indicates the dedicated SPID for an
atorSpid CNOPE 01032/ LTE operator. According to 3GPP specifications, the SPID
Cfg RATOR TDLOF Load can be from 1 to 256. When this parameter is set to 0,
SPIDCF D-00103 Balancin the eNodeB does not obtain the SPID from the MME
G 2 g or the eNodeB is not configured with an SPID for
LST LOFD-0 Inter- UEs. This parameter applies only to LTE FDD and
CNOPE 01044/ RAT LTE TDD.
RATOR TDLOF Load GUI Value Range: 0~256
SPIDCF D-00104 Sharing Unit: None
G 4 to
MOD LOFD-0
CNOPE 01045/ Inter- Default Value: None
RATOR TDLOF RAT
SPIDCF D-00104 Load
G 5 Sharing
RMV LOFD-0 to
CNOPE 01054/ GERAN
RATOR TDLOF Flexible
SPIDCF D-00105 User
G 4 Steering
LOFD-0 Camp &
0105401 Handov
/ er Based
TDLOF on SPID
D-00105 UL Pre-
401 allocatio
LOFD-0 n Based
01059/ on SPID
TDLOF Multi
D-00105 Operator
9 s SPID
LOFD-0 Policy
70210/
TDLOF
D-00113
3

eRAN

nd
CnOper RatFreq ADD LOFD-0 Intra- Meaning: Indicates whether to set a RAT/frequency
atorSpid PriorityI CNOPE 01032/ LTE priority. If this parameter is set to CFG, UEs
Cfg nd RATOR TDLOF Load preferentially camp on the RAT or frequency. If this
SPIDCF D-00103 Balancin parameter is set to NOT_CFG, UEs do not
G 2 g preferentially camp on the RAT or frequency. This
MOD LOFD-0 Inter- parameter applies only to LTE FDD and LTE TDD.
CNOPE 01044/ RAT GUI Value Range: NOT_CFG(NOT_CFG),
RATOR TDLOF Load CFG(CFG)
SPIDCF D-00104 Sharing Unit: None
G 4 to
UTRAN Actual Value Range: NOT_CFG, CFG
LST LOFD-0
CNOPE 01045/ Inter- Default Value: NOT_CFG(NOT_CFG)
RATOR TDLOF RAT
SPIDCF D-00104 Load
G 5 Sharing
LOFD-0 to
70210/ GERAN
TDLOF Multi
D-00113 Operator
3 s SPID
Policy

eRAN

nd
CnOper RatFreq ADD LOFD-0 Intra- Meaning: Indicates the ID of a RAT/frequency priority
atorSpid Priority CNOPE 01032/ LTE group. This parameter applies only to LTE FDD and
Cfg GroupId RATOR TDLOF Load LTE TDD.
SPIDCF D-00103 Balancin GUI Value Range: 0~255
G 2 g
Unit: None
MOD LOFD-0 Inter-
CNOPE 01044/ RAT Actual Value Range: 0~255
RATOR TDLOF Load Default Value: 0
SPIDCF D-00104 Sharing
G 4 to
LST LOFD-0 UTRAN
CNOPE 01045/ Inter-
RATOR TDLOF RAT
SPIDCF D-00104 Load
G 5 Sharing
LOFD-0 to
01054/ GERAN
TDLOF Flexible
D-00105 User
4 Steering
LOFD-0 Camp &
0105401 Handov
/ er Based
TDLOF on SPID
D-00105 UL Pre-
401 allocatio
LOFD-0 n Based
01059/ on SPID
TDLOF Multi
D-00105 Operator
9 s SPID
LOFD-0 Policy
70210/
TDLOF
D-00113
3

eRAN
RAN Sharing Feature Parameter Description 13 Counters
13 Counters
Table 13-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526727849 L.Thrp.bits.UL.PL Total uplink traffic Multi-mode: None Radio Bearer

MN.QCI.1 volume for PDCP GSM: None Management
SDUs for a specific RAN Sharing with
operator for UMTS: None
Common Carrier
services with the LTE:
QCI of 1 in a cell RAN Sharing with
LBFD-002008
Dedicated Carrier
LOFD-001036 Basic Scheduling
LOFD-001037 Radio Bearer
LBFD-002025 Management
TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037 Dedicated Carrier
TDLBFD-002025 Basic Scheduling
LOFD-070206 Hybrid RAN
TDLOFD-081224 Sharing
NR: None Hybrid RAN
Sharing

eRAN

Description
1526727850 L.Thrp.Time.UL.PL Receive duration of Multi-mode: None Radio Bearer

MN.QCI.1 uplink PDCP SDUs GSM: None Management
for a specific RAN Sharing with
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526727853 L.E- Number of E-RAB Multi-mode: None Radio Bearer

RAB.AttEst.PLMN. setup attempts GSM: None Management
QCI.1 initiated by UEs for Radio Bearer
services with the UMTS: None
Management
QCI of 1for a LTE:
specific operator in RAN Sharing with
LBFD-002008
a cell Common Carrier
LOFD-001036 Dedicated Carrier
LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526727854 L.E- Number of Multi-mode: None Radio Bearer

RAB.SuccEst.PLM successful E-RAB GSM: None Management
N.QCI.1 setups initiated by Radio Bearer
UEs for services UMTS: None
Management
with the QCI of 1 LTE:
LBFD-002008
operator in a cell Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 2 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 3 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 4 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 5 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 6 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 7 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 8 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 9 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

UEs for services for UMTS: None
Management
a specific operator LTE:
with the QCI of 9 in RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.AbnormRel.P abnormal releases GSM: None Management
LMN.QCI.1 of activated E- Radio Bearer
RABs for services UMTS: None
Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526727872 L.E- Number of normal Multi-mode: None Radio Bearer

RAB.NormRel.PL E-RAB releases for GSM: None Management
MN.QCI.1 services with the Radio Bearer
QCI of 1 for a UMTS: None
Management
specific operator in LTE:
a cell RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.NormRel.HO E-RAB releases for GSM: None Management
Out.PLMN.QCI.1 outgoing handovers Radio Bearer
of services with the UMTS: None
Management
QCI of 1 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
QCI of 2 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 3 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
QCI of 4 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 5 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
QCI of 6 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 7 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
QCI of 8 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
QCI of 9 for a LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.AbnormRel.H abnormal E-RAB GSM: None Management
OOut.PLMN.QCI.1 releases for Radio Bearer
outgoing handovers UMTS: None
Management
of services with the LTE:
QCI of 1 for a RAN Sharing with
LBFD-002008
specific operator in Common Carrier
a cell TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526728050 L.Thrp.bits.DL.PL Total downlink Multi-mode: None Radio Bearer

MN.QCI.1 traffic volume for GSM: None Management
PDCP SDUs for a RAN Sharing with
specific operator for UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526728051 L.Thrp.Time.DL.PL Transmit duration Multi-mode: None Radio Bearer

MN.QCI.1 of downlink PDCP GSM: None Management
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

SDUs in a cell for a RAN Sharing with
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526728077 L.Traffic.User.Avg. Average number of Multi-mode: None RRC Connection

PLMN users served by a GSM: None Management
specific operator in RRC Connection
a cell UMTS: None
Management
LTE:
RAN Sharing with
LBFD-002007
Common Carrier
LOFD-001036 Common Carrier
TDLOFD-001036 RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526728250 L.E- Total number of E- Multi-mode: None Radio Bearer

RAB.AttEst.PLMN RAB setup attempts GSM: None Management
initiated by UEs for Radio Bearer
a specific operator UMTS: None
Management
in a cell LTE:
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526728251 L.E- Total number of Multi-mode: None Radio Bearer

N setups initiated by Radio Bearer
UEs for a specific UMTS: None
Management
operator in a cell LTE:
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526728252 L.E- Total number of E- Multi-mode: None Coverage Based

RAB.AttEst.HOIn. RAB setup attempts GSM: None Intra-frequency
PLMN for incoming Handover
handovers for a UMTS: None
Coverage Based
specific operator in LTE: Intra-frequency
a cell LBFD-00201801 Handover
TDLBFD-0020180 Coverage Based
1 Inter-frequency
LBFD-00201802 Handover
2 Inter-frequency
TDLBFD-0020180 Distance Based
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
TDLBFD-0020180 Inter-frequency
5 Handover
LOFD-001036 Service Based Inter-
LOFD-001037 frequency
TDLOFD-001036 Handover
TDLOFD-001037 Service Based Inter-
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
NR: None Common Carrier
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728253 L.E- Total number of Multi-mode: None Coverage Based

RAB.SuccEst.HOIn successful E-RAB GSM: None Intra-frequency
.PLMN setups for incoming Handover
handovers for a UMTS: None
Coverage Based
specific operator in LTE: Intra-frequency
a cell LBFD-00201801 Handover
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

RAB.AbnormRel.P abnormal releases GSM: None Intra-frequency
LMN of activated E- Handover
RABs for a specific UMTS: None
Coverage Based
operator in a cell LTE: Intra-frequency
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

RAB.NormRel.PL normal E-RAB GSM: None Intra-frequency
MN releases for a Handover
specific operator in UMTS: None
Coverage Based
a cell LTE: Intra-frequency
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

RAB.NormRel.HO normal E-RAB GSM: None Intra-frequency
Out.PLMN releases for Handover
Coverage Based
for a specific LTE: Intra-frequency
operator in a cell LBFD-00201801 Handover
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

RAB.AbnormRel.H abnormal E-RAB GSM: None Intra-frequency
OOut.PLMN releases for Handover
Coverage Based
operator in a cell LBFD-00201801 Handover
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

MN volume for PDCP GSM: None Management
operator in a cell UMTS: None
Common Carrier
LTE:
RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526728264 L.Thrp.Time.UL.PL Total receive Multi-mode: None Radio Bearer

MN duration of uplink GSM: None Management
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

MN traffic volume for GSM: None Management
Common Carrier
a cell LTE:
RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526728266 L.Thrp.Time.DL.PL Total transmit Multi-mode: None Radio Bearer

MN duration of GSM: None Management
downlink PDCP RAN Sharing with
SDUs for a specific UMTS: None
Common Carrier
operator in a cell LTE:
RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526728293 L.RBUsedOwn.DL. Average number of Multi-mode: None Basic Scheduling

PLMN own PDSCH PRBs GSM: None Basic Scheduling
used by a specific
operator UMTS: None RAN Sharing with
Common Carrier
LTE:
LBFD-002025 RAN Sharing with
Dedicated Carrier
TDLBFD-002025
Adaptive SFN/
LOFD-001036 SDMA
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
TDLOFD-081224
Hybrid RAN
LEOFD-111305 Sharing
NR: None Virtual 4T4R
1526728294 L.RBUsedOwn.UL. Average number of Multi-mode: None Basic Scheduling

PLMN own PUSCH PRBs GSM: None Basic Scheduling
used by a specific
operator UMTS: None RAN Sharing with
Common Carrier
LTE:
Dedicated Carrier
TDLBFD-002025
Adaptive SFN/
LOFD-001036 SDMA
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
TDLOFD-081224 Hybrid RAN
NR: None Sharing

eRAN

Description
1526728295 L.RBUsedOther.DL Average number of Multi-mode: None Basic Scheduling

.PLMN other operators' GSM: None Basic Scheduling
PDSCH PRBs used
by a specific UMTS: None RAN Sharing with
operator Common Carrier
LTE:
Dedicated Carrier
TDLBFD-002025
Adaptive SFN/
LOFD-001036 SDMA
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
TDLOFD-081224
Hybrid RAN
LEOFD-111305 Sharing
NR: None Virtual 4T4R
1526728296 L.RBUsedOther.UL Average number of Multi-mode: None Basic Scheduling

.PLMN other operators' GSM: None Basic Scheduling
PUSCH PRBs used
by a specific UMTS: None RAN Sharing with
LTE:
Dedicated Carrier
TDLBFD-002025
Adaptive SFN/
LOFD-001036 SDMA
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description
1526728359 L.HHO.IntraeNB.In Number of intra- Multi-mode: None Coverage Based

traFreq.PrepAttOut. eNodeB intra- GSM: None Intra-frequency
PLMN frequency outgoing Handover
handover attempts UMTS: None
Coverage Based
operator LBFD-00201801 Handover
1 Common Carrier
TDLOFD-001037 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

traFreq.ExecAttOut eNodeB intra- GSM: None Intra-frequency
.PLMN frequency outgoing Handover
handover UMTS: None
Coverage Based
executions for a LTE: Intra-frequency
specific operator LBFD-00201801 Handover
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728361 L.HHO.IntraeNB.In Number of Multi-mode: None Coverage Based

traFreq.ExecSuccO successful intra- GSM: None Intra-frequency
ut.PLMN eNodeB intra- Handover
frequency outgoing UMTS: None
Coverage Based
handovers for a LTE: Intra-frequency
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

terFreq.PrepAttOut. eNodeB inter- GSM: None Inter-frequency
Coverage Based
for a specific LTE: Inter-frequency
2 Inter-frequency
4 Inter-frequency
TDLBFD-0020180 Service Based Inter-
5 frequency
Handover
LOFD-001036
Service Based Inter-
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFreq.ExecAttOut eNodeB inter- GSM: None Inter-frequency
handover UMTS: None
Coverage Based
executions for a LTE: Inter-frequency
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFreq.ExecSuccO successful intra- GSM: None Inter-frequency
ut.PLMN eNodeB inter- Handover
Coverage Based
handovers for a LTE: Inter-frequency
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728365 L.HHO.IntereNB.In Number of inter- Multi-mode: None Coverage Based

Coverage Based
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

handover UMTS: None
Coverage Based
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728367 L.HHO.IntereNB.In Number of Multi-mode: None Coverage Based

traFreq.ExecSuccO successful inter- GSM: None Intra-frequency
ut.PLMN eNodeB intra- Handover
Coverage Based
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

handover UMTS: None
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFreq.ExecSuccO successful inter- GSM: None Inter-frequency
ut.PLMN eNodeB inter- Handover
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728371 L.HHO.X2.IntraFre Number of X2- Multi-mode: None Coverage Based

q.PrepAttOut.PLM based intra- GSM: None Intra-frequency
N frequency outgoing Handover
Coverage Based
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing
1526728372 L.HHO.X2.IntraFre Number of X2- Multi-mode: None Coverage Based

q.ExecAttOut.PLM based intra- GSM: None Intra-frequency
handover UMTS: None
Coverage Based
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728373 L.HHO.X2.IntraFre Number of Multi-mode: None Coverage Based

q.ExecSuccOut.PL successful X2- GSM: None Intra-frequency
MN based intra- Handover
Coverage Based
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728374 L.HHO.X2.InterFre Number of X2- Multi-mode: None Coverage Based

q.PrepAttOut.PLM based inter- GSM: None Inter-frequency
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728375 L.HHO.X2.InterFre Number of X2- Multi-mode: None Coverage Based

q.ExecAttOut.PLM based inter- GSM: None Inter-frequency
handover UMTS: None
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728376 L.HHO.X2.InterFre Number of Multi-mode: None Coverage Based

q.ExecSuccOut.PL successful X2- GSM: None Inter-frequency
MN based inter- Handover
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728377 L.IRATHO.E2W.Pr Number of inter- Multi-mode: UL Unified Video

epAttOut.PLMN RAT handover MRFD-101401 Steering
attempts from E- GSM: None
UTRAN to PS Inter-RAT
WCDMA network UMTS: None Mobility between
for a specific LTE: E-UTRAN and
operator LOFD-001019 UTRAN
LOFD-001022 SRVCC to UTRAN
LOFD-001033 CS Fallback to
TDLOFD-001019 UTRAN
TDLOFD-001022 PS Inter-RAT
Mobility between
TDLOFD-001033 E-UTRAN and
LOFD-001036 UTRAN
TDLOFD-001036 CS Fallback to
TDLOFD-001037 UTRAN
Common Carrier
TDLOFD-081224
RAN Sharing with
NR: None Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728378 L.IRATHO.E2W.Ex Number of inter- Multi-mode: UL Unified Video

ecAttOut.PLMN RAT handover MRFD-101401 Steering
executions from E- GSM: None
UTRAN to PS Inter-RAT
TDLOFD-001019 UTRAN
Mobility between
LOFD-001036 UTRAN
TDLOFD-001037 UTRAN
Common Carrier
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728379 L.IRATHO.E2W.Ex Number of Multi-mode: UL Unified Video

ecSuccOut.PLMN successful inter- MRFD-101401 Steering
RAT handovers GSM: None
from E-UTRAN to PS Inter-RAT
TDLOFD-001019 UTRAN
Mobility between
LOFD-001036 UTRAN
TDLOFD-001037 UTRAN
Common Carrier
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728380 L.IRATHO.E2G.Pr Number of inter- Multi-mode: None PS Inter-RAT

epAttOut.PLMN RAT handover GSM: None Mobility between
attempts from E- E-UTRAN and
UTRAN to UMTS: None GERAN
GERAN for a LTE: SRVCC to GERAN
specific operator LOFD-001020
CS Fallback to
LOFD-001023 GERAN
LOFD-001034 PS Inter-RAT
TDLOFD-001020 Mobility between
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
NR: None RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728381 L.IRATHO.E2G.Ex Number of inter- Multi-mode: None PS Inter-RAT

ecAttOut.PLMN RAT handover GSM: None Mobility between
executions from E- E-UTRAN and
UTRAN to UMTS: None GERAN
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728382 L.IRATHO.E2G.Ex Number of Multi-mode: None PS Inter-RAT

ecSuccOut.PLMN successful inter- GSM: None Mobility between
RAT handovers E-UTRAN and
from E-UTRAN to UMTS: None GERAN
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing
1526728383 L.E- Number of MME- Multi-mode: None Radio Bearer

RAB.AbnormRel. triggered abnormal GSM: None Management
MME.PLMN releases of activated Radio Bearer
E-RABs for a UMTS: None
Management
specific operator LTE:
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526728389 L.IRATHO.BlindH Number of inter- Multi-mode: None PS Inter-RAT

O.E2W.PrepAttOut. RAT blind GSM: None Mobility between
PLMN handover attempts E-UTRAN and
from E-UTRAN to UMTS: None UTRAN
WCDMA network LTE: SRVCC to UTRAN
for a specific LOFD-001019
operator CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

O.E2G.PrepAttOut. RAT blind GSM: None Mobility between
PLMN handover attempts E-UTRAN and
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

O.E2W.ExecAttOut RAT blind GSM: None Mobility between
.PLMN handover E-UTRAN and
executions from E- UMTS: None UTRAN
UTRAN to LTE: SRVCC to UTRAN
WCDMA network LOFD-001019
for a specific CS Fallback to
LOFD-001022 UTRAN
operator
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728392 L.IRATHO.BlindH Number of Multi-mode: None PS Inter-RAT

O.E2W.ExecSuccO successful inter- GSM: None Mobility between
ut.PLMN RAT blind E-UTRAN and
handover UMTS: None UTRAN
executions from E- LTE: SRVCC to UTRAN
UTRAN to LOFD-001019
WCDMA network CS Fallback to
LOFD-001022 UTRAN
for a specific
operator LOFD-001033 PS Inter-RAT
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

O.E2G.ExecAttOut. RAT blind GSM: None Mobility between
PLMN handover E-UTRAN and
executions from E- UMTS: None GERAN
UTRAN to LTE: SRVCC to GERAN
GERAN for a LOFD-001020
specific operator CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728394 L.IRATHO.BlindH Number of Multi-mode: None PS Inter-RAT

O.E2G.ExecSuccO successful inter- GSM: None Mobility between
ut.PLMN RAT blind E-UTRAN and
handover UMTS: None GERAN
executions from E- LTE: SRVCC to GERAN
UTRAN to LOFD-001020
GERAN for a CS Fallback to
LOFD-001023 GERAN
specific operator
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728395 L.HHO.BlindHO.Pr Number of intra- Multi-mode: None Coverage Based

epAttOut.PLMN duplex-mode GSM: None Intra-frequency
outgoing blind Handover
Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728396 L.HHO.BlindHO.E Number of intra- Multi-mode: None Coverage Based

xecAttOut.PLMN duplex-mode GSM: None Intra-frequency
outgoing blind Handover
handover UMTS: None
Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728397 L.HHO.BlindHO.E Number of Multi-mode: None Coverage Based

xecSuccOut.PLMN successful intra- GSM: None Intra-frequency
duplex-mode Handover
outgoing blind UMTS: None
Coverage Based
handover LTE: Intra-frequency
executions for a LBFD-00201801 Handover
specific operator TDLBFD-0020180 Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526728443 L.RRCRel.Dedicate Number of times Multi-mode: None Camp & Handover

dPri.WCDMA.High that the WCDMA GSM: None Based on SPID
network is Camp & Handover
configured as the UMTS: None
Based on SPID
highest frequency LTE:
priority in an Inter-RAT Load
LOFD-00105401
IMMCI IE Sharing to UTRAN
TDLOFD-0010540 Inter-RAT Load
1 Sharing to UTRAN
LOFD-001044 MOCN Flexible
TDLOFD-001044 Priority Based
Camping
LOFD-001112
MOCN Flexible
TDLOFD-001112 Priority Based
NR: None Camping
1526728467 L.Traffic.User.Max. Maximum number Multi-mode: None RRC Connection

PLMN of users for a GSM: None Management
a cell UMTS: None
Management
LTE:
RAN Sharing with
LBFD-002007
Common Carrier
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

dPri.GERAN.High that GERAN is GSM: None Based on SPID
configured as the Camp & Handover
highest frequency UMTS: None
Based on SPID
priority in an LTE:
IMMCI IE LOFD-00105401 MOCN Flexible
Priority Based
TDLOFD-0010540 Camping
1
MOCN Flexible
LOFD-001112 Priority Based
NR: None

eRAN

Description

dPri.LTE.High that E-UTRAN is GSM: None Based on SPID
configured as the Camp & Handover
highest frequency UMTS: None
Based on SPID
priority in an LTE:
IMMCI IE LOFD-00105401 MOCN Flexible
Priority Based
1
MOCN Flexible
LOFD-001112 Priority Based
NR: None

RAB.Rel.S1Reset.e abnormal E-RAB GSM: None Management
NodeB.PLMN.QCI. releases initiated by Radio Bearer
1 the eNodeB for UMTS: None
Management
QCI of 1 because of RAN Sharing with
LBFD-002008
the S1 RESET for a Common Carrier
specific operator in TDLBFD-002008 RAN Sharing with
a cell LOFD-001036 Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

NodeB.PLMN releases initiated by Radio Bearer
the eNodeB UMTS: None
Management
because of the S1 LTE:
RESET for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.AbnormRel. MME-triggered GSM: None Management
MMETot.PLMN abnormal E-RAB Radio Bearer
releases for a UMTS: None
Management
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729025 L.Thrp.bits.DL.Last Downlink traffic Multi-mode: None Radio Bearer

TTI.PLMN volume sent in the GSM: None Management
last TTI before the RAN Sharing with
buffer is empty for UMTS: None
Common Carrier
RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

TTI.PLMN.QCI.1 volume sent in the GSM: None Management
Common Carrier
QCI 1 for a specific RAN Sharing with
LBFD-002008
operator Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729035 L.Thrp.Time.DL.R Data transmit Multi-mode: None Radio Bearer

mvLastTTI.PLMN duration except the GSM: None Management
downlink buffer is UMTS: None
Common Carrier
empty for a specific LTE:
operator RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

mvLastTTI.PLMN. duration except the GSM: None Management
QCI.1 last TTI before the RAN Sharing with
Common Carrier
empty for services LTE:
with the QCI 1 for a RAN Sharing with
LBFD-002008
specific operator Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729051 L.Thrp.bits.UE.UL. Traffic volume of Multi-mode: None Radio Bearer

LastTTI.PLMN uplink PDCP PDUs GSM: None Management
received in the last Radio Bearer
TTI before the UE UMTS: None
Management
buffer is empty for LTE:
a specific operator Basic Scheduling
LBFD-002008
Basic Scheduling
TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
TDLBFD-002025 Hybrid RAN
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier
1526729052 L.Thrp.Time.UE.U Uplink data Multi-mode: None Radio Bearer

L.RmvLastTTI.PL transmit duration GSM: None Management
MN except the last TTI Radio Bearer
before the UE UMTS: None
Management
buffer is empty for LTE:
a specific operator Basic Scheduling
LBFD-002008
Basic Scheduling
TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description
1526729156 L.Thrp.DL.BitRate. Number of Multi-mode: None Radio Bearer

Samp.Index0.PLM operator-specific GSM: None Management
N samples with the RAN Sharing with
downlink UMTS: None
Common Carrier
throughput ranging LTE:
within index 0 RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

downlink UMTS: None
Common Carrier
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

QCI1.Samp.Index0. operator-specific GSM: None Management
PLMN samples with the RAN Sharing with
downlink QCI-1 UMTS: None
Common Carrier
service throughput LTE:
ranging within RAN Sharing with
LBFD-002008
index 0 Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.NoRe setup failures due to GSM: None Management
ply.PLMN no responses from Radio Bearer
the UE in a cell for UMTS: None
Management
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.MME. triggered E-RAB GSM: None Management
PLMN setup failures for a Radio Bearer
specific operator UMTS: None
Management
LTE:
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.TNL.P setup failures due to GSM: None Management
LMN faults at the Radio Bearer
transport network UMTS: None
Management
layer for a specific LTE:
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.RNL. setup failures due to GSM: None Management
PLMN faults at the radio Radio Bearer
network layer for a UMTS: None
Management
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.NoRa setup failures due to GSM: None Management
dioRes.PLMN insufficient radio Radio Bearer
resources for a UMTS: None
Management
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.Secur setup failures due to GSM: None Management
ModeFail.PLMN security mode Radio Bearer
configuration UMTS: None
Management
failures for a LTE:
specific operator RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729417 L.Thrp.bits.UE.UL. Uplink traffic Multi-mode: None Radio Bearer

SmallPkt.PLMN volume of PDCP GSM: None Management
PDUs scheduled for RAN Sharing with
small packets for a UMTS: None
Common Carrier
RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526729418 L.Thrp.Time.UE.U Uplink data Multi-mode: None Radio Bearer

L.RmvSmallPkt.PL transmission GSM: None Management
MN duration except that RAN Sharing with
for small packets UMTS: None
Common Carrier
for a specific LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729445 L.Thrp.UL.BitRate. Number of Multi-mode: None Radio Bearer

uplink throughput UMTS: None
Common Carrier
ranging within LTE:
index 0 RAN Sharing with
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Common Carrier
ranging within LTE:
LBFD-002008
Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.AbnormRel.R abnormal releases GSM: None Management
adio.PLMN of activated E- Radio Bearer
RABs because of UMTS: None
Management
faults at the radio LTE:
network layer for a RAN Sharing with
LBFD-002008
specific operator Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.AbnormRel.T abnormal releases GSM: None Management
NL.PLMN of activated E- Radio Bearer
Management
faults at the LTE:
transport network RAN Sharing with
LBFD-002008
layer for a specific Common Carrier
operator TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.AbnormRel.C abnormal releases GSM: None Management
ong.PLMN of activated E- Radio Bearer
Management
network congestion LTE:
for a specific LBFD-002008 Congestion Control
operator TDLBFD-002008 Congestion Control
LBFD-002024 Radio and
Transmission
TDLBFD-002024 Resource Pre-
LOFD-00102901 Emption
TDLOFD-0010290 Radio and
1 Transmission
LOFD-001036 Resource Pre-
Emption
LOFD-001037
RAN Sharing with
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

RAB.AbnormRel.H abnormal releases GSM: None Management
OFailure.PLMN of activated E- Radio Bearer
Management
handover failures LTE:
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729503 L.RRCRedirection. Number of Multi-mode: None PS Inter-RAT

E2W.PLMN redirections from E- GSM: None Mobility between
UTRAN to E-UTRAN and
WCDMA network UMTS: None UTRAN
for a specific LTE: CS Fallback to
UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729504 L.RRCRedirection. Number of Multi-mode: None PS Inter-RAT

E2G.PLMN redirections from E- GSM: None Mobility between
UTRAN to E-UTRAN and
GERAN for a UMTS: None GERAN
specific operator LTE: CS Fallback to
LOFD-001020 GERAN
GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

dioRes.SRS.PLMN insufficient SRS Radio Bearer
resources for a UMTS: None
Management
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

dioRes.PUCCH.PL insufficient PUCCH Radio Bearer
MN resources for a UMTS: None
Management
RAN Sharing with
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

adio.SRBReset.PL of activated E- Radio Bearer
MN RABs because the UMTS: None
Management
RLC PDU for an LTE:
SRB has been RAN Sharing with
LBFD-002008
retransmitted for Common Carrier
the maximum TDLBFD-002008 RAN Sharing with
number of times for LOFD-001036 Dedicated Carrier
a specific operator LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

adio.DRBReset.PL of activated E- Radio Bearer
MN RABs because the UMTS: None
Management
RLC PDU for a LTE:
DRB has been RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

adio.ULSyncFail.P of activated E- Radio Bearer
LMN RABs due to uplink UMTS: None
Management
resynchronization LTE:
failures for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

adio.UuNoReply.P of activated E- Radio Bearer
LMN RABs because of UMTS: None
Management
no responses from LTE:
the UE for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

terFddTdd.PrepAtt eNodeB inter- GSM: None Inter-frequency
Out.PLMN duplex-mode Handover
outgoing handover UMTS: None
Coverage Based
attempts for a LTE: Inter-frequency
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFddTdd.ExecAtt eNodeB inter- GSM: None Inter-frequency
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFddTdd.ExecSuc successful intra- GSM: None Inter-frequency
cOut.PLMN eNodeB inter- Handover
duplex-mode UMTS: None
Coverage Based
outgoing handovers LTE: Inter-frequency
for a specific LBFD-00201802 Handover
operator TDLBFD-0020180 Distance Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
attempts for a LTE: Inter-frequency
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFddTdd.ExecSuc successful inter- GSM: None Inter-frequency
cOut.PLMN eNodeB inter- Handover
Coverage Based
for a specific LBFD-00201802 Handover
operator TDLBFD-0020180 Distance Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729581 L.HHO.X2.InterFd Number of X2- Multi-mode: None Coverage Based

dTdd.PrepAttOut.P based inter-duplex- GSM: None Inter-frequency
LMN mode outgoing Handover
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729582 L.HHO.X2.InterFd Number of X2- Multi-mode: None Coverage Based

dTdd.ExecAttOut.P based inter-duplex- GSM: None Inter-frequency
LMN mode outgoing Handover
handover UMTS: None
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729583 L.HHO.X2.InterFd Number of Multi-mode: None Coverage Based

dTdd.ExecSuccOut. successful X2- GSM: None Inter-frequency
PLMN based inter-duplex- Handover
mode outgoing UMTS: None
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729596 L.HHO.InterFddTd Number of inter- Multi-mode: None Coverage Based

d.BlindHO.PrepAtt duplex-mode GSM: None Inter-frequency
Out.PLMN outgoing blind Handover
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729597 L.HHO.InterFddTd Number of inter- Multi-mode: None Coverage Based

d.BlindHO.ExecAtt duplex-mode GSM: None Inter-frequency
Out.PLMN outgoing blind Handover
handover UMTS: None
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729598 L.HHO.InterFddTd Number of Multi-mode: None Coverage Based

d.BlindHO.ExecSu successful inter- GSM: None Inter-frequency
ccOut.PLMN duplex-mode Handover
outgoing blind UMTS: None
Coverage Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526729665 L.Paging.S1.Rx.PL Number of received Multi-mode: None Paging

MN paging messages GSM: None Paging
over the S1
interface for a UMTS: None RAN Sharing with
LTE: LBFD-002011
TDLBFD-002011
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526729666 L.Thrp.Time.Cell.D Total duration of Multi-mode: None Radio Bearer

L.HighPrecision.PL downlink data GSM: None Management
MN transmission for a RAN Sharing with
Common Carrier
a cell (with the LTE:
sampling period of RAN Sharing with
LBFD-002008
1 millisecond) Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729667 L.Thrp.Time.Cell.U Total duration of Multi-mode: None Radio Bearer

L.HighPrecision.PL uplink data GSM: None Management
MN transmission for a RAN Sharing with
Common Carrier
sampling period of RAN Sharing with
LBFD-002008
1 millisecond) Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.AbnormRel. abnormal releases GSM: None Management
MME.EUtranGen.P of activated E- Radio Bearer
LMN RABs triggered by UMTS: None
Management
the MME with the LTE:
release cause of RAN Sharing with
LBFD-002008
Release due to E- Common Carrier
UTRAN Generated TDLBFD-002008 RAN Sharing with
Reason for a LOFD-001036 Dedicated Carrier
specific operator LOFD-001037 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

ong.PreEmp.PLMN of activated E- Radio Bearer
Management
radio resource LTE:
preemption for a LBFD-002008 RAN Sharing with
TDLBFD-002008
RAN Sharing with
Sharing
LBFD-002024
Hybrid RAN
TDLBFD-002024 Sharing
LOFD-00102901 Congestion Control
TDLOFD-0010290 Congestion Control
1
Radio and
NR: None Transmission
Resource Pre-
Emption
Radio and
Transmission
Resource Pre-
Emption

eRAN

Description

ong.Load.PLMN of activated E- Radio Bearer
Management
radio resource LTE:
overload for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
LBFD-002024 Hybrid RAN
Sharing
TDLBFD-002024
Congestion Control
NR: None
Congestion Control

NL.PreEmp.PLMN of activated E- Radio Bearer
Management
transport resource LTE:
preemption for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

NL.Load.PLMN of activated E- Radio Bearer
Management
transport resource LTE:
overload for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

MMETot.VoIP.PLM releases of E-RABs Radio Bearer
N for voice services UMTS: None
Management
for a specific LTE:
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

adio.SRBReset.VoI of activated E- Radio Bearer
P.PLMN RABs for voice UMTS: None
Management
services because the LTE:
RLC PDU for an RAN Sharing with
LBFD-002008
SRB has been Common Carrier
retransmitted for TDLBFD-002008 RAN Sharing with
the maximum LOFD-001036 Dedicated Carrier
number of times for LOFD-001037 RAN Sharing with
a specific operator Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

adio.NoReply.VoIP. of activated E- Radio Bearer
PLMN RABs for voice UMTS: None
Management
services because of LTE:
no responses from RAN Sharing with
LBFD-002008
the UE for a Common Carrier
specific operator TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

adio.ULSyncFail.V of activated E- Radio Bearer
oIP.PLMN RABs for voice UMTS: None
Management
uplink RAN Sharing with
LBFD-002008
resynchronization Common Carrier
failures for a TDLBFD-002008 RAN Sharing with
specific operator LOFD-001036 Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.AbnormRel. abnormal releases GSM: None Management
MME.EUtranGen. of activated E- Radio Bearer
VoIP.PLMN RABs for voice UMTS: None
Management
services triggered LTE:
by the MME with RAN Sharing with
LBFD-002008
the release cause of Common Carrier
Release due to E- TDLBFD-002008 RAN Sharing with
UTRAN Generated LOFD-001036 Dedicated Carrier
Reason for a LOFD-001037 RAN Sharing with
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

adio.VoIP.PLMN of activated E- Radio Bearer
RABs for voice UMTS: None
Management
faults at the radio RAN Sharing with
LBFD-002008
network layer for a Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.AbnormRel.H abnormal releases GSM: None Management
OFailure.VoIP.PLM of activated E- Radio Bearer
N RABs for voice UMTS: None
Management
handover failures RAN Sharing with
LBFD-002008
for a specific Common Carrier
operator TDLBFD-002008 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

ong.VoIP.PLMN of activated E- Radio Bearer
Management
radio network LBFD-002008 RAN Sharing with
congestion for a Common Carrier
TDLBFD-002008
Sharing
LBFD-002024
Hybrid RAN
1
Radio and
Resource Pre-
Emption
Radio and
Transmission
Resource Pre-
Emption

MME.VoIP.PLMN releases of activated Radio Bearer
E-RABs for voice UMTS: None
Management
services for a LTE:
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

NL.VoIP.PLMN of activated E- Radio Bearer
Management
faults at the RAN Sharing with
LBFD-002008
transport network Common Carrier
layer for a specific TDLBFD-002008 RAN Sharing with
operator LOFD-001036 Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

NL.PreEmp.VoIP.P of activated E- Radio Bearer
LMN RABs for voice UMTS: None
Management
transport resource RAN Sharing with
LBFD-002008
preemption for a Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

NL.Load.VoIP.PLM of activated E- Radio Bearer
N RABs for voice UMTS: None
Management
transport resource RAN Sharing with
LBFD-002008
overload for a Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

ong.PreEmp.VoIP.P of activated E- Radio Bearer
LMN RABs for voice UMTS: None
Management
radio resource LBFD-002008 RAN Sharing with
preemption for a Common Carrier
TDLBFD-002008
Sharing
LBFD-002024
Hybrid RAN
1
Radio and
Resource Pre-
Emption
Radio and
Transmission
Resource Pre-
Emption

eRAN

Description

ong.Load.VoIP.PL of activated E- Radio Bearer
MN RABs for voice UMTS: None
Management
radio resource RAN Sharing with
LBFD-002008
overload for a Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
LBFD-002024 Hybrid RAN
Sharing
TDLBFD-002024
Congestion Control
NR: None
Congestion Control

RAB.FailEst.SRBR setup failures GSM: None Management
eset.PLMN because the RLC Radio Bearer
PDU for an SRB UMTS: None
Management
has been LTE:
retransmitted for RAN Sharing with
LBFD-002008
the maximum Common Carrier
number of times for TDLBFD-002008 RAN Sharing with
a specific operator LOFD-001036 Dedicated Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.TNL. setup failures GSM: None Management
DLRes.PLMN because of Radio Bearer
insufficient UMTS: None
Management
downlink transport LTE:
resources for a Admission Control
LBFD-002008
specific operator Admission Control
TDLBFD-002008
RAN Sharing with
LBFD-002023 Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.TNL. setup failures GSM: None Management
ULRes.PLMN because of Radio Bearer
insufficient uplink UMTS: None
Management
transport resources LTE:
for a specific Admission Control
LBFD-002008
operator Admission Control
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.NoRa setup failures GSM: None Management
dioRes.DLThrpLic. because of Radio Bearer
PLMN insufficient UMTS: None
Management
downlink licensed LTE:
traffic volume for a Admission Control
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

dioRes.ULThrpLic. because of Radio Bearer
PLMN insufficient uplink UMTS: None
Management
licensed traffic LTE:
volume for a Admission Control
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

dioRes.DLSatis.PL because of a low Radio Bearer
MN downlink UMTS: None
Management
satisfaction rate for LTE:
a specific operator Admission Control
LBFD-002008
Admission Control
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

dioRes.ULSatis.PL because of a low Radio Bearer
MN uplink satisfaction UMTS: None
Management
rate for a specific LTE:
LBFD-002008
Admission Control
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526729979 L.E- Number of setup Multi-mode: None Radio Bearer

RAB.FailEst.NoRe failures of E-RABs GSM: None Management
ply.VoIP.PLMN for voice services Radio Bearer
because of no UMTS: None
Management
responses from the LTE:
UE in a cell for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.MME. triggered setup GSM: None Management
VoIP.PLMN failures of E-RABs Radio Bearer
for voice services UMTS: None
Management
for a specific LTE:
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.TNL. failures of E-RABs GSM: None Management
VoIP.PLMN for voice services Radio Bearer
because of faults at UMTS: None
Management
the transport LTE:
network layer for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.RNL. failures of E-RABs GSM: None Management
VoIP.PLMN for voice services Radio Bearer
because of faults at UMTS: None
Management
the radio network LTE:
layer for a specific RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.NoRa failures of E-RABs GSM: None Management
dioRes.VoIP.PLMN for voice services Radio Bearer
because of UMTS: None
Management
insufficient radio LTE:
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

RAB.FailEst.Secur failures of E-RABs GSM: None Management
ModeFail.VoIP.PL for voice services Radio Bearer
MN because of security UMTS: None
Management
mode configuration LTE:
failures for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

RAB.FailEst.SRBR failures of E-RABs GSM: None Management
eset.VoIP.PLMN for voice services Radio Bearer
because the RLC UMTS: None
Management
PDU for an SRB LTE:
has been RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

dioRes.SRS.VoIP.P for voice services Radio Bearer
LMN because of UMTS: None
Management
insufficient SRS LTE:
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

dioRes.PUCCH.VoI for voice services Radio Bearer
P.PLMN because of UMTS: None
Management
insufficient PUCCH LTE:
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

dioRes.DLThrpLic. for voice services Radio Bearer
VoIP.PLMN because of UMTS: None
Management
insufficient licensed LTE:
downlink traffic Admission Control
LBFD-002008
specific operator TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

dioRes.ULThrpLic. for voice services Radio Bearer
VoIP.PLMN because of UMTS: None
Management
insufficient licensed LTE:
uplink traffic Admission Control
LBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

dioRes.DLSatis.VoI for voice services Radio Bearer
P.PLMN because of a low UMTS: None
Management
downlink LTE:
satisfaction rate for Admission Control
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

dioRes.ULSatis.VoI for voice services Radio Bearer
P.PLMN because of a low UMTS: None
Management
uplink satisfaction LTE:
rate for a specific Admission Control
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

DLRes.VoIP.PLMN for voice services Radio Bearer
Management
insufficient LTE:
downlink transport Admission Control
LBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

ULRes.VoIP.PLMN for voice services Radio Bearer
Management
insufficient uplink LTE:
transport resources Admission Control
LBFD-002008
for a specific Admission Control
operator TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526730042 L.IRATHO.E2W.N Number of inter- Multi-mode: None PS Inter-RAT

oNRT.PLMN RAT handover GSM: None Mobility between
initiation failures E-UTRAN and
from E-UTRAN to UMTS: None UTRAN
WCDMA network LTE: Inter-RAT ANR
because the LOFD-001019
adjacent cell is not PS Inter-RAT
LOFD-002002 Mobility between
on the NRT of the
source cell for a TDLOFD-001019 E-UTRAN and
specific operator TDLBFD-002002 UTRAN
LOFD-001036 Transport Channel
Management
LOFD-001037
RAN Sharing with
Dedicated Carrier
NR: None
Hybrid RAN
Sharing
Hybrid RAN
Sharing
SRVCC to UTRAN
SRVCC to UTRAN

eRAN

Description
1526730043 L.IRATHO.E2G.No Number of inter- Multi-mode: None PS Inter-RAT

NRT.PLMN RAT handover GSM: None Mobility between
initiation failures E-UTRAN and
GERAN because LTE: Inter-RAT ANR
the adjacent cell is LOFD-001020
not on the NRT of PS Inter-RAT
LOFD-002002 Mobility between
the source cell for a
specific operator TDLOFD-001020 E-UTRAN and
TDLBFD-002002 GERAN
LOFD-001036 Transport Channel
Management
LOFD-001037
RAN Sharing with
Dedicated Carrier
NR: None
Hybrid RAN
Sharing
Hybrid RAN
Sharing
SRVCC to GERAN
SRVCC to GERAN

eRAN

Description
1526730044 L.CSFB.PrepAtt.PL Number of CSFB Multi-mode: None CS Fallback to

MN indicators received GSM: None UTRAN
by the eNodeB for a CS Fallback to
specific operator UMTS: None
UTRAN
LTE:
GERAN
TDLOFD-001033
CS Fallback to
LOFD-001034 GERAN
LOFD-001035 CDMA2000 1xRTT
Dedicated Carrier
TDLOFD-001036
CS Fallback to
TDLOFD-001037 CDMA2000 1xRTT
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526730045 L.CSFB.PrepSucc.P Number of Multi-mode: None CS Fallback to

LMN successful CSFB GSM: None UTRAN
responses sent from CS Fallback to
the eNodeB for a UMTS: None
UTRAN
GERAN
TDLOFD-001033
CS Fallback to
LOFD-001034 GERAN
LOFD-001035 CDMA2000 1xRTT
Dedicated Carrier
TDLOFD-001036
CS Fallback to
TDLOFD-001037 CDMA2000 1xRTT
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing
1526730046 L.RRCRedirection. Number of CSFB- Multi-mode: None CS Fallback to

E2W.CSFB.PLMN based redirections GSM: None UTRAN
from E-UTRAN to CS Fallback to
WCDMA network UMTS: None
UTRAN
for a specific LTE:
LOFD-001033
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526730047 L.IRATHO.E2W.C Number of CSFB- Multi-mode: None CS Fallback to

SFB.PrepAttOut.PL based handover GSM: None UTRAN
MN preparation CS Fallback to
attempts from E- UMTS: None
UTRAN
UTRAN to LTE:
WCDMA network RAN Sharing with
LOFD-001033
operator TDLOFD-001033 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526730048 L.IRATHO.E2W.C Number of CSFB- Multi-mode: None CS Fallback to

SFB.ExecAttOut.P based handover GSM: None UTRAN
LMN execution attempts CS Fallback to
from E-UTRAN to UMTS: None
UTRAN
WCDMA network LTE:
LOFD-001033
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526730049 L.IRATHO.E2W.C Number of Multi-mode: None CS Fallback to

SFB.ExecSuccOut. successful CSFB- GSM: None UTRAN
PLMN based handover CS Fallback to
executions from E- UMTS: None
UTRAN
UTRAN to LTE:
WCDMA network RAN Sharing with
LOFD-001033
operator TDLOFD-001033 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526730050 L.RRCRedirection. Number of CSFB- Multi-mode: None CS Fallback to

E2G.CSFB.PLMN based redirections GSM: None GERAN
from E-UTRAN to CS Fallback to
GERAN for a UMTS: None
GERAN
RAN Sharing with
LOFD-001034
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526730051 L.IRATHO.E2G.CS Number of CSFB- Multi-mode: None CS Fallback to

FB.PrepAttOut.PL based handover GSM: None GERAN
MN preparation CS Fallback to
attempts from E- UMTS: None
GERAN
UTRAN to LTE:
GERAN for a RAN Sharing with
LOFD-001034
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526730052 L.IRATHO.E2G.CS Number of CSFB- Multi-mode: None CS Fallback to

FB.ExecAttOut.PL based handover GSM: None GERAN
MN execution attempts CS Fallback to
from E-UTRAN to UMTS: None
GERAN
GERAN for a LTE:
LOFD-001034
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526730053 L.IRATHO.E2G.CS Number of Multi-mode: None CS Fallback to

FB.ExecSuccOut.P successful CSFB- GSM: None GERAN
LMN based handover CS Fallback to
executions from E- UMTS: None
GERAN
UTRAN to LTE:
GERAN for a RAN Sharing with
LOFD-001034
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526730054 L.IRATHO.SRVCC Number of SRVCC- Multi-mode: None SRVCC to UTRAN

.E2W.PrepAttOut.P based outgoing GSM: None SRVCC to UTRAN
LMN handover attempts
from E-UTRAN to UMTS: None RAN Sharing with
WCDMA network LTE: Common Carrier
for a specific LOFD-001022 RAN Sharing with
operator TDLOFD-001022 Dedicated Carrier
Common Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001036
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
NR: None Sharing

eRAN

Description
1526730055 L.IRATHO.SRVCC Number of SRVCC- Multi-mode: None SRVCC to UTRAN

.E2W.ExecAttOut.P based outgoing GSM: None SRVCC to UTRAN
LMN handover
executions from E- UMTS: None RAN Sharing with
UTRAN to LTE: Common Carrier
WCDMA network LOFD-001022 RAN Sharing with
for a specific TDLOFD-001022 Dedicated Carrier
operator
Common Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001036
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
NR: None Sharing
1526730056 L.IRATHO.SRVCC Number of Multi-mode: None SRVCC to UTRAN

.E2W.ExecSuccOut. successful SRVCC- GSM: None SRVCC to UTRAN
PLMN based outgoing
handovers from E- UMTS: None RAN Sharing with
WCDMA network LOFD-001022 RAN Sharing with
for a specific TDLOFD-001022 Dedicated Carrier
operator
Common Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001036
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
NR: None Sharing

eRAN

Description
1526730057 L.IRATHO.SRVCC Number of SRVCC- Multi-mode: None SRVCC to GERAN

.E2G.PrepAttOut.P based outgoing GSM: None SRVCC to GERAN
LMN handover attempts
from E-UTRAN to UMTS: None RAN Sharing with
GERAN for a LTE: Common Carrier
specific operator LOFD-001023 RAN Sharing with
Common Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001036
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
NR: None Sharing
1526730058 L.IRATHO.SRVCC Number of SRVCC- Multi-mode: None SRVCC to GERAN

.E2G.ExecAttOut.P based outgoing GSM: None SRVCC to GERAN
LMN handover
executions from E- UMTS: None RAN Sharing with
GERAN for a LOFD-001023 RAN Sharing with
specific operator TDLOFD-001023 Dedicated Carrier
Common Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001036
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
NR: None Sharing

eRAN

Description
1526730059 L.IRATHO.SRVCC Number of Multi-mode: None SRVCC to GERAN

.E2G.ExecSuccOut. successful SRVCC- GSM: None SRVCC to GERAN
PLMN based outgoing
handovers from E- UMTS: None RAN Sharing with
GERAN for a LOFD-001023 RAN Sharing with
specific operator TDLOFD-001023 Dedicated Carrier
Common Carrier
LOFD-001037
RAN Sharing with
TDLOFD-001036
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206 Sharing
NR: None Sharing
1526730113 L.E- Total duration of Multi-mode: None Radio Bearer

RAB.SessionTime. UE data GSM: None Management
UE.HighPrecision.P transmission for a Radio Bearer
LMN specific operator in UMTS: None
Management
precision of 100 Basic Scheduling
LBFD-002008
ms) Basic Scheduling
TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description

RAB.SessionTime. data transmission GSM: None Management
HighPrecision.PLM for a specific Radio Bearer
N operator in a cell UMTS: None
Management
(with the precision LTE:
of 100 ms) Basic Scheduling
LBFD-002008
Basic Scheduling
TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

HighPrecision.PLM for services with the Radio Bearer
N.QCI1 QCI of 1 for a UMTS: None
Management
a cell (with the Basic Scheduling
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

Management
LBFD-002008
ms) TDLBFD-002008
Hybrid RAN
LBFD-002025 Sharing
LOFD-070206 Sharing
Common Carrier
LOFD-001036
RAN Sharing with
Dedicated Carrier

eRAN

Description
1526730589 L.Traffic.User.Ulsy Average number of Multi-mode: None RRC Connection

nc.Avg.PLMN UL synchronized GSM: None Management
users for a specific RRC Connection
operator in a cell UMTS: None
Management
LTE:
Common Carrier
TDLBFD-002007
RAN Sharing with
Sharing
LOFD-070204
Hybrid RAN
NR: None Sharing
Operator Load
Based Intra-LTE
MLB
1526736660 L.Voice.VQI.UL.Ex Number of times Multi-mode: None Support of VoLTE

cellent.Times.PLM uplink voice quality GSM: None Support of VoLTE
N is Excellent for a
specific operator in UMTS: None RAN Sharing with
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description
1526736661 L.Voice.VQI.UL.G Number of times Multi-mode: None Support of VoLTE

ood.Times.PLMN uplink voice quality GSM: None Support of VoLTE
is Good for a
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526736662 L.Voice.VQI.UL.Ac Number of times Multi-mode: None Support of VoLTE

cept.Times.PLMN uplink voice quality GSM: None Support of VoLTE
is Accept for a
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description
1526736663 L.Voice.VQI.UL.Po Number of times Multi-mode: None Support of VoLTE

or.Times.PLMN uplink voice quality GSM: None Support of VoLTE
is Poor for a
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526736664 L.Voice.VQI.UL.Ba Number of times Multi-mode: None Support of VoLTE

d.Times.PLMN uplink voice quality GSM: None Support of VoLTE
is Bad for a specific
operator in a cell UMTS: None RAN Sharing with
Common Carrier
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description
1526736665 L.Voice.VQI.DL.Ex Number of times Multi-mode: None Support of VoLTE

cellent.Times.PLM downlink voice GSM: None Support of VoLTE
N quality is Excellent
for a specific UMTS: None RAN Sharing with
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526736666 L.Voice.VQI.DL.G Number of times Multi-mode: None Support of VoLTE

ood.Times.PLMN downlink voice GSM: None Support of VoLTE
quality is Good for
a specific operator UMTS: None RAN Sharing with
in a cell Common Carrier
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description
1526736667 L.Voice.VQI.DL.Ac Number of times Multi-mode: None Support of VoLTE

cept.Times.PLMN downlink voice GSM: None Support of VoLTE
quality is Accept
for a specific UMTS: None RAN Sharing with
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526736668 L.Voice.VQI.DL.Po Number of times Multi-mode: None Support of VoLTE

or.Times.PLMN downlink voice GSM: None Support of VoLTE
quality is Poor for a
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description
1526736669 L.Voice.VQI.DL.Ba Number of times Multi-mode: None Support of VoLTE

d.Times.PLMN downlink voice GSM: None Support of VoLTE
quality is Bad for a
LTE: LBFD-131107
RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526736670 L.Voice.VQI.AMR Number of times Multi-mode: None Support of VoLTE

WB.UL.Excellent.T uplink voice quality GSM: None Support of VoLTE
imes.PLMN of AMR-WB
services is UMTS: None RAN Sharing with
Excellent for a Common Carrier
LTE: LBFD-131107
TDLBFD-081101
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description

WB.UL.Good.Time uplink voice quality GSM: None Support of VoLTE
s.PLMN of AMR-WB
services is Good for UMTS: None RAN Sharing with
LTE: LBFD-131107
in a cell RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

WB.UL.Accept.Ti uplink voice quality GSM: None Support of VoLTE
mes.PLMN of AMR-WB
services is Accept UMTS: None RAN Sharing with
LTE: LBFD-131107
operator in a cell RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description

WB.UL.Poor.Times uplink voice quality GSM: None Support of VoLTE
.PLMN of AMR-WB
services is Poor for UMTS: None RAN Sharing with
LTE: LBFD-131107
in a cell RAN Sharing with
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

WB.UL.Bad.Times. uplink voice quality GSM: None Support of VoLTE
PLMN of AMR-WB
services is Bad for a UMTS: None RAN Sharing with
LTE: LBFD-131107
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description

WB.DL.Excellent.T downlink voice GSM: None Support of VoLTE
imes.PLMN quality of AMR-
WB services is UMTS: None RAN Sharing with
Excellent for a Common Carrier
LTE: LBFD-131107
TDLBFD-081101
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

WB.DL.Good.Time downlink voice GSM: None Support of VoLTE
s.PLMN quality of AMR-
Good for a specific Common Carrier
LTE: LBFD-131107
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description

WB.DL.Accept.Ti downlink voice GSM: None Support of VoLTE
mes.PLMN quality of AMR-
Accept for a Common Carrier
LTE: LBFD-131107
TDLBFD-081101
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

WB.DL.Poor.Times downlink voice GSM: None Support of VoLTE
.PLMN quality of AMR-
WB services is Poor UMTS: None RAN Sharing with
LTE: LBFD-131107
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing

eRAN

Description

WB.DL.Bad.Times. downlink voice GSM: None Support of VoLTE
PLMN quality of AMR-
WB services is Bad UMTS: None RAN Sharing with
LTE: LBFD-131107
TDLBFD-081101
Common Carrier
Dedicated Carrier
TDLOFD-001037
Hybrid RAN
LOFD-070206
Sharing
NR: None Sharing
1526736680 L.PDCP.Tx.Disc.Tr Number of Multi-mode: None Radio Bearer

f.SDU.PLMN.QCI. downlink traffic GSM: None Management
1 SDUs discarded by Radio Bearer
the PDCP layer for UMTS: None
Management
services with a QCI LTE:
of 1 for a specific Basic Scheduling
LBFD-002008
operator in a cell Basic Scheduling
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526736681 L.PDCP.Tx.Disc.Tr Number of Multi-mode: None Radio Bearer

f.SDU.PLMN.QCI. downlink traffic GSM: None Management
5 SDUs discarded by Radio Bearer
the PDCP layer for UMTS: None
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526736682 L.PDCP.Tx.TotRev. Number of Multi-mode: None Radio Bearer

Trf.SDU.PLMN.Q transmitted GSM: None Management
CI.1 downlink traffic Radio Bearer
PDCP SDUs for UMTS: None
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526736683 L.PDCP.Tx.TotRev. Number of Multi-mode: None Radio Bearer

Trf.SDU.PLMN.Q transmitted GSM: None Management
CI.5 downlink traffic Radio Bearer
PDCP SDUs for UMTS: None
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526736684 L.Traffic.UL.PktLo Total number of Multi-mode: None Radio Bearer

ss.Loss.PLMN.QCI discarded uplink GSM: None Management
.1 PDCP SDUs for Radio Bearer
traffic services with UMTS: None
Management
a QCI of 1 for a LTE:
specific operator in Basic Scheduling
LBFD-002008
a cell Basic Scheduling
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

ss.Loss.PLMN.QCI discarded uplink GSM: None Management
.5 PDCP SDUs for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

ss.Tot.PLMN.QCI.1 expected uplink GSM: None Management
data packets for Radio Bearer
DRB services with UMTS: None
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

ss.Tot.PLMN.QCI.5 expected uplink GSM: None Management
data packets for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526736688 L.Traffic.DL.PktDe Number of Multi-mode: None Radio Bearer

lay.Num.PLMN.QC successfully GSM: None Management
I.1 transmitted Radio Bearer
downlink PDCP UMTS: None
Management
SDUs for DRB LTE:
services with a QCI Basic Scheduling
LBFD-002008
operator in a cell TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526736689 L.Traffic.DL.PktDe Number of Multi-mode: None Radio Bearer

lay.Num.PLMN.QC successfully GSM: None Management
I.5 transmitted Radio Bearer
downlink PDCP UMTS: None
Management
SDUs for DRB LTE:
services with a QCI Basic Scheduling
LBFD-002008
operator in a cell TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526736690 L.Traffic.DL.PktDe Total processing Multi-mode: None Radio Bearer

lay.Time.PLMN.QC delay of downlink GSM: None Management
I.5 PDCP SDUs for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526736691 L.Traffic.DL.PktDe Total processing Multi-mode: None Radio Bearer

lay.Time.PLMN.QC delay of downlink GSM: None Management
I.1 PDCP SDUs for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing
1526736692 L.Traffic.User.VoIP. Average number of Multi-mode: None RRC Connection

Avg.PLMN VoIP UEs of a GSM: None Management
a cell UMTS: None
Management
LTE:
RAN Sharing with
LBFD-002007
Common Carrier
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526736693 L.Traffic.User.VoIP. Maximum number Multi-mode: None RRC Connection

Max.PLMN of VoIP UEs of a GSM: None Management
a cell UMTS: None
Management
LTE:
RAN Sharing with
LBFD-002007
Common Carrier
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

dioRes.DLSatis.QC with a QCI of 2 Radio Bearer
I2.PLMN because of a low UMTS: None
Management
downlink LTE:
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
downlink LTE:
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
downlink LTE:
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

dioRes.ULSatis.QC with a QCI of 2 Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

VoIP.PLMN frequency outgoing Handover
Coverage Based
for UEs performing LTE: Intra-frequency
voice services for a LBFD-00201801 Handover
specific operator in TDLBFD-0020180
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
for UEs performing LTE: Inter-frequency
a cell Distance Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

Out.VoIP.PLMN duplex-mode Handover
Coverage Based
attempts for UEs LTE: Inter-frequency
performing voice LBFD-00201802 Handover
services for a TDLBFD-0020180
specific operator in Distance Based
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

.VoIP.PLMN frequency outgoing Handover
handover UMTS: None
Coverage Based
executions for UEs LTE: Intra-frequency
1 Common Carrier
a cell
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

handover UMTS: None
Coverage Based
executions for UEs LTE: Inter-frequency
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

traFreq.ExecSuccO successful inter- GSM: None Intra-frequency
ut.VoIP.PLMN eNodeB intra- Handover
Coverage Based
handovers for UEs LTE: Intra-frequency
1 Common Carrier
a cell
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

terFreq.ExecSuccO successful inter- GSM: None Inter-frequency
ut.VoIP.PLMN eNodeB inter- Handover
Coverage Based
handovers for UEs LTE: Inter-frequency
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFddTdd.ExecSuc successful inter- GSM: None Inter-frequency
cOut.VoIP.PLMN eNodeB inter- Handover
Coverage Based
for UEs performing LBFD-00201802 Handover
voice services for a TDLBFD-0020180
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
for UEs performing LTE: Intra-frequency
1 Common Carrier
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
for UEs performing LTE: Inter-frequency
a cell Distance Based
2 Inter-frequency
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
attempts for UEs LTE: Inter-frequency
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

handover UMTS: None
Coverage Based
executions for UEs LTE: Intra-frequency
1 Common Carrier
a cell
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

Coverage Based
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

handover UMTS: None
Coverage Based
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFreq.ExecSuccO successful intra- GSM: None Intra-frequency
ut.VoIP.PLMN eNodeB inter- Handover
Coverage Based
handovers for UEs LTE: Intra-frequency
1 Common Carrier
a cell
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description

traFreq.ExecSuccO successful intra- GSM: None Inter-frequency
ut.VoIP.PLMN eNodeB intra- Handover
Coverage Based
handovers for UEs LTE: Inter-frequency
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description

terFddTdd.ExecSuc successful intra- GSM: None Inter-frequency
cOut.VoIP.PLMN eNodeB inter- Handover
Coverage Based
for UEs performing LBFD-00201802 Handover
voice services for a TDLBFD-0020180
2 Inter-frequency
a cell
4 Inter-frequency
5 frequency
Handover
LOFD-001036
Dedicated Carrier
NR: None
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526736724 L.E- Number of E-RAB Multi-mode: None Coverage Based

RAB.AttEst.HOIn. setup attempts for GSM: None Intra-frequency
PLMN.QCI.1 incoming handovers Handover
of services with a UMTS: None
Coverage Based
QCI of 1 for a LTE: Intra-frequency
specific operator in LBFD-00201801 Handover
a cell TDLBFD-0020180 Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526736725 L.E- Number of E-RAB Multi-mode: None Coverage Based

RAB.AttEst.HOIn. setup attempts for GSM: None Intra-frequency
PLMN.QCI.5 incoming handovers Handover
of services with a UMTS: None
Coverage Based
QCI of 5 for a LTE: Intra-frequency
specific operator in LBFD-00201801 Handover
a cell TDLBFD-0020180 Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526736726 L.E- Number of Multi-mode: None Coverage Based

.PLMN.QCI.1 setups for incoming Handover
handovers of UMTS: None
Coverage Based
services with a QCI LTE: Intra-frequency
of 1 for a specific LBFD-00201801 Handover
operator in a cell TDLBFD-0020180 Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526736727 L.E- Number of Multi-mode: None Coverage Based

.PLMN.QCI.5 setups for incoming Handover
handovers of UMTS: None
Coverage Based
services with a QCI LTE: Intra-frequency
of 5 for a specific LBFD-00201801 Handover
operator in a cell TDLBFD-0020180 Coverage Based
1 Inter-frequency
2 Inter-frequency
4 Inter-frequency
Handover
LBFD-00201805
Distance Based
5 Handover
frequency
LOFD-070206
Handover
TDLOFD-081224
RAN Sharing with
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
Hybrid RAN
Sharing

eRAN

Description
1526736737 L.Traffic.DL.PktUu Total number of Multi-mode: None Radio Bearer

Loss.Loss.PLMN.Q discarded downlink GSM: None Management
CI.1 PDCP SDUs for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

Loss.Loss.PLMN.Q discarded downlink GSM: None Management
CI.5 PDCP SDUs for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description

Loss.Tot.PLMN.QC expected downlink GSM: None Management
I.1 data packets for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

Loss.Tot.PLMN.QC expected downlink GSM: None Management
I.5 data packets for Radio Bearer
Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Dedicated Carrier
LOFD-001037
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526736867 L.Cell.UserLic.Lim Number of times Multi-mode: None Admission Control

it.Num.PLMN the licensed number GSM: None Admission Control
of UEs is limited
for a specific UMTS: None Radio and
operator LTE: Transmission
LBFD-002023 Resource Pre-
Emption
TDLBFD-002023
Radio and
LOFD-00102901 Transmission
TDLOFD-0010290 Resource Pre-
1 Emption
Sharing
TDLOFD-001036
Hybrid RAN
NR: None Sharing
RAN Sharing with
Common Carrier
1526736868 L.Cell.UserLic.Prep Number of Multi-mode: None Admission Control

Emp.Succ.Num.PL successful GSM: None Admission Control
MN preemptions
triggered by the UMTS: None Radio and
limitation of the LTE: Transmission
licensed number of LBFD-002023 Resource Pre-
UEs for a specific Emption
TDLBFD-002023
operator Radio and
LOFD-00102901 Transmission
TDLOFD-0010290 Resource Pre-
1 Emption
Sharing
TDLOFD-001036
Hybrid RAN
NR: None Sharing
RAN Sharing with
Common Carrier

eRAN

Description
1526739678 L.HHO.S1.IntraFre Number of Multi-mode: None Coverage Based

q.MMEAbnormRsp responses for GSM: None Intra-frequency
.PLMN abnormal causes Handover
received by the UMTS: None
Coverage Based
eNodeB from the LTE: Intra-frequency
MME during S1- LBFD-00201801 Handover
based outgoing TDLBFD-0020180
intra-frequency RAN Sharing with
1 Common Carrier
handover
executions for a LOFD-001036 RAN Sharing with
specific operator in LOFD-001037 Dedicated Carrier
a cell TDLOFD-001036 RAN Sharing with
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing
1526739679 L.HHO.S1.InterFre Number of Multi-mode: None Coverage Based

q.MMEAbnormRsp responses for GSM: None Intra-frequency
.PLMN abnormal causes Handover
Coverage Based
inter-frequency RAN Sharing with
1 Common Carrier
handover
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing

eRAN

Description
1526739680 L.HHO.S1.InterFdd Number of Multi-mode: None Coverage Based

Tdd.MMEAbnorm responses for GSM: None Intra-frequency
Rsp.PLMN abnormal causes Handover
Coverage Based
inter-duplex-mode RAN Sharing with
1 Common Carrier
handover
Dedicated Carrier
TDLOFD-081224
Hybrid RAN
NR: None Sharing
Hybrid RAN
Sharing
1526741667 L.RBUsedOtherGro Average number of Multi-mode: None Basic Scheduling

up.UL.PLMN other operator GSM: None RAN Sharing with
resource groups' Common Carrier
uplink PRBs used UMTS: None
by a specific LTE: RAN Sharing with
operator in an LBFD-002025 Dedicated Carrier
operator resource LOFD-001036 Adaptive SFN/
group in a cell SDMA
LOFD-001037
Hybrid RAN
LOFD-070205 Sharing
NR: None
1526741668 L.RBUsedOtherGro Average number of Multi-mode: None Basic Scheduling

up.DL.PLMN other operator GSM: None RAN Sharing with
resource groups' Common Carrier
downlink PRBs UMTS: None
used by a specific LTE: RAN Sharing with
operator in an LBFD-002025 Dedicated Carrier
operator resource LOFD-001036 Adaptive SFN/
group in a cell SDMA
LOFD-001037
Hybrid RAN
LOFD-070205 Sharing
NR: None

eRAN

Description
1526745753 L.NB.RRC.ConnRe Number of Multi-mode: None 3GPP R13 NB-IoT

q.Succ.PLMN successful RRC GSM: None Specifications
connection setups Hybrid RAN
for a specific UMTS: None
Sharing
operator in an NB- LTE:
IoT cell MLBFD-12000201
TDLOFD-081224
NR: None
1526745754 L.NB.UECNTX.No Number of normal Multi-mode: None 3GPP R13 NB-IoT

rmRel.PLMN UE context releases GSM: None Specifications
for a specific Hybrid RAN
operator in an NB- UMTS: None
Sharing
IoT cell LTE:
MLBFD-12000201
TDLOFD-081224
NR: None
1526745755 L.NB.UECNTX.Ab Number of Multi-mode: None 3GPP R13 NB-IoT

normRel.PLMN abnormal UE GSM: None Specifications
context releases for Hybrid RAN
a specific operator UMTS: None
Sharing
in an NB-IoT cell LTE:
MLBFD-12000201
TDLOFD-081224
NR: None

RAB.FailEst.X2AP. setup failures GSM: None Management
PLMN because of conflicts Radio Bearer
with X2AP-related UMTS: None
Management
procedures for a LTE:
LBFD-002008
Common Carrier
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN

Description
1526747657 L.E- Number of voice- Multi-mode: None Radio Bearer

RAB.FailEst.X2AP. service E-RAB GSM: None Management
VoIP.PLMN setup failures Radio Bearer
because of conflicts UMTS: None
Management
with X2AP-related LTE:
procedures for a RAN Sharing with
LBFD-002008
Common Carrier
TDLOFD-001036
RAN Sharing with
NR: None Hybrid RAN
Sharing

eRAN
RAN Sharing Feature Parameter Description 14 Glossary
14 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
RAN Sharing Feature Parameter Description 15 Reference Documents
15 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. IP 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. NB-IoT Radio and Performance Basics (FDD)
22. CSPC
23. Relay
24. S1-flex
25. VoLTE
26. WBB
27. Uplink Coordinated Scheduling

RAN Sharing (eRAN13.1 - 05)

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 (eRAN13.1 - 05)

Uploaded by

Copyright:

Available Formats

eRAN

RAN Sharing Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 6

4 RAN Sharing with Common Carrier....................................................................................... 13

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. ii

4.1.5.2 Capacity License.....................................................................................................................................................27

5 RAN Sharing with Dedicated Carrier..................................................................................... 67

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. iii

5.1.5.3 Performance Management...................................................................................................................................... 69

6 RAN Sharing with Special Dedicated Carrier (FDD).......................................................... 85

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. iv

6.1.10 Multi-operator PKI.................................................................................................................................................. 89

7 Hybrid RAN Sharing................................................................................................................ 101

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. v

7.1.10 Multi-operator PKI................................................................................................................................................ 114

8 RAN Sharing by More Operators...........................................................................................135

9 Fair User Sharing (FDD)...........................................................................................................139

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. vi

10 MOCN Cell Reselection Priority Configuration............................................................... 146

11 Multi-Operator SPID Policy..................................................................................................156

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. vii

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. viii

1.1 eRAN13.1 05 (2018-11-07)

Added static allocation of RB Modified FDD l 3900 and 5900

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 1

Change Description Parameter RAT Base Station

Added the mutual impact None FDD l 3900 and 5900

Added the mutual impact None FDD l 3900 and 5900

1.2 eRAN13.1 04 (2018-08-27)

1.3 eRAN13.1 03 (2018-06-30)

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 2

1.4 eRAN13.1 02 (2018-05-25)

1.5 eRAN13.1 01 (2018-04-10)

Added the mutually exclusive None FDD l 3900 and 5900

Added the mutually exclusive None FDD l 3900 and 5900

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter RAT Base Station

Added the mutually exclusive None FDD l 3900 and 5900

1.6 eRAN13.1 Draft A (2018-01-15) (FDD)

Added the DBS3900 LampSite None DBS3900 LampSite

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 4

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 5

2 About This Document

2.1 Applicable RAT

2.2 Features in This Document

Feature ID Feature Name Section

LOFD-001036 RAN Sharing with 4 RAN Sharing with Common Carrier

LOFD-001037 RAN Sharing with 5 RAN Sharing with Dedicated Carrier

LOFD-070206 Hybrid RAN Sharing 7 Hybrid RAN Sharing

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

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

LOFD-001112 MOCN Flexible 10 MOCN Cell Reselection Priority

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

This document describes the following NB-IoT features.

Issue 05 (2018-11-07) Copyright © Huawei Technologies Co., Ltd. 6

Feature ID Feature Name Section

MLOFD-121251 NB-IoT RAN Sharing 4 RAN Sharing with Common Carrier

MLOFD-121252 NB-IoT RAN Sharing 5 RAN Sharing with Dedicated Carrier

2.3 Feature Differences Between NB-IoT and FDD