FDD Network Sharing ZTE eReader-Browse

16/4/2020 FDD Network Sharing (LR18+)
FDD Network Sharing (LR18+)

Feature Guide
FDD Network Sharing (LR18+)

Version Date Author Reviewer Notes
Zhang No technical change

V1.0 2018-11-30 Haixia Zhang Fan Change the structure
He Lifang
Add:
Zhang 1. RIM Routing in RAN Sharing in
V1.1 2019-02-28 Haixia Zhang Fan Chapter 3.4.6
He Lifang 2. SN Addition in RAN Sharing in
Chapter 3.5.4.
Add:
V1.2 2019-05-30 Mou Jun Zhang Fan PLMN Group Based RRC User Number
Resource Sharing in Chapter 3.3.2.4
TABLE OF CONTENTS
1 Introduction
1.1 Related Feature List and License Control
1.2 Correlation with Other Features
1.2.1 ZLF31-12-017 Further multi PLMN Shared Carrier
1.2.2 ZLF31-12-018 Operator Specific Customized Subscription Based Mobility Management
1.2.3 ZLF31-12-019 Intra-LTE ANR of Dedicated Carrier Sharing
2 Function Description
3 Technical Description
3.1 Basic Networking Modes
3.1.1 Network Sharing Mode
3.1.2 Radio Carrier Sharing Mode
3.2 Basic Functions
3.2.1 PLMN Negotiation between the Core Network and eNodeB
3.2.2 Broadcasting of the PLMN List
3.2.3 PLMN Routing of UEs
3.3 Resource Management
3.3.1 Transmission Resource Sharing Management
3.3.2 Radio Resource Management
3.4 Mobility in the Network Sharing
3.4.1 Handover
3.4.2 Redirection
3.4.3 Re-Establishment
3.4.4 CSFB
3.4.5 Operator Specific Customized Subscription Based Mobility Management
3.4.6 RIM Routing in RAN Sharing
3.5 Others
3.5.1 ANR of Dedicated Carrier Sharing
3.5.2 X2 Self-Setup in Dedicated Carrier Sharing
3.5.3 eNodeB Access Solution
3.5.4 SN Addition in RAN Sharing
3.6 Performance Management in Network Sharing
4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements
4.1.2 EPC Requirements
4.1.3 UE Requirement
4.1.4 Transmission Bandwidth Requirements
4.2 Function Activate
4.2.1 Basic Networking Modes Configuration
4.2.2 Resource Management Configuration
4.2.3 Mobility in the Network Sharing Configuration
4.2.4 Others
4.2.5 Data Synchronization
4.2.6 Deactivate feature
5 Related Counters, KPI and Alarms
127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 1/56
5.1 Related Counters
5.2 Related KPIs
5.3 Related Alarms
6 Impact on Network
7 Abbreviations
8 References
9 Appendix
FIGURES
Figure 3-1 MOCN Network Sharing

Figure 3-2 GWCN Network Sharing
Figure 3-3 Dedicated Carrier Network Sharing
Figure 3-4 Sharing Carrier Network Sharing
Figure 3-5 S1 Setup Process
Figure 3-6 Delivery of SIB1
Figure 3-7 Attach Process
Figure 3-8 TAU Process
Figure 3-9 Complete Sharing of Access Network (only the eNodeB is shared, the transmission network is independent)
Figure 3-10 Access Network Sharing (both the eNodeB and transmission network are shared)
Figure 3-11 Radio Resource Sharing Mode
Figure 3-12 Case5 admission Control processing flow
Figure 3-13 Case5 congestion status Jugement
Figure 3-14 PLMN Based RRC User Number Resource Sharing
Figure 3-15 PLMN Group Based RRC User Number Resource Sharing.
Figure 3-16 Intra-frequency interference in the boundary area of shared area and non-shared area
Figure 4-1 Configuring Ran Sharing Switch
Figure 4-3 Operator Configuration
Figure 4-4 PLMN Configuration
Figure 4-5 configuring multiple PLMN
Figure 4-6 Configure Ran Sharing Switch
Figure 4-7 Configure Switch for Replacing PLMN in RAN Share Area In Dedicated Carrier Mode
Figure 4-8 PLMN List for RAN Share Area In Dedicated Carrier Mode Configure
Figure 4-10 Configure bandwidth resource group
Figure 4-11 Configure bandwidth resource
Figure 4-12 Configure bandwidth resource to associate with different operator 1
Figure 4-16 Configure bandwidth resource to associate with multiple operator 1
Figure 4-18 Configure Case5 Related parameters
Figure 4-19 Configure Admission Control Algorithm
Figure 4-20 Open Congestion Control Switch
Figure 4-21 Configure RB Division Mode and Resource Ratio
Figure 4-22 Configure Admission control algorithm for RRC User Number of Operator in Network Sharing
Figure 4-23 Configure Allocation Mode of the Numbers of RRC Users in Network Sharing Scenarios and Ratio of the Numbers of RRC Users Allocated Based on PLMN
Groups (%) in Network Sharing
Figure 4-24 Configure QoS Basic Priority, MCC and MNC,
Figure 4-25 Configure Switch for QoS Configuration Based PLMN
Figure 4-26 Open Switch of Inter PLMN HO
Figure 4-27 Configure PLMN List of Serving Cell
Figure 4-28 Configure PLMN of Neighbor Cell
Figure 4-29 Configure PLMN of UTRAN FDD Neighbor Cell
Figure 4-30 Configure PLMN of GERAN Neighbor Cell
Figure 4-31 Configure Inter-Frequency, GERAN-Frequency, UTRAN-Frequency
Figure 4-32 Configure Handover Switch Based Frequency Priority with PLMN
Figure 4-33 Configure Frequency Priority Based PLMN
Figure 4-34 Configure E-UTRAN Neighbor Relation
Figure 4-35 Configure Operation Method of LTE to UTRAN\GERAN
Figure 4-36 ConfigureRAT priority
Figure 4-37 E-UTRAN Frequency Redirection Priority
Figure 4-38 UTRAN Frequency Redirection Priority
Figure 4-39 GERAN Frequency Redirection Priority,
Figure 4-40 Configure local strategy
Figure 4-41 Configure Multi-PLMN local strategy for PS
Figure 4-42 Configure Multi-PLMN local strategy for Redirection
Figure 4-43 Configure Multi-PLMN local strategy for RRC connection re-establishment
Figure 4-44 local strategy for CSFB,
Figure 4-45 Configuring LTE PLMN Level RIM Optimization
TABLES
Table 1‑1 Related Feature List and License Control
Table 1‑2 Correlation with Other Features
Table 3‑1 S1 Setup Request Message
Table 3‑2 S1 Setup Response Message
Table 3‑3 Initial UE Message
Table 3‑4 Related Parameters
Table 4‑1 Network Sharing Parameters Configuration Rule
Table 4‑2 Radio Resource Sharing Management related parameters
Table 4‑3 Proportional Division of the Number of RRC Users related parameters
Table 4‑4 Qos Management related parameters
Table 4‑5 Mobility in the Network Sharing configuration related parameters
Table 4‑6 Handover Switch Based Frequency Priority with PLMN
Table 4‑7 Local Strategy configuration related parameters
Table 4‑8 PLMN Replacement under Dedicated Carrier Sharing
Table 5‑1 Related Counters
Table 5‑2 Related KPIs
Table 9‑2Related KPIs
1 Introduction
This document provides the introduction, technical descriptions, parameter configuration, counters, alarms, and validation procedure of the LTE FDD network sharing
feature.
The parameters, alarms and counters in this document are the same as those of the latest software version when this document is released. To obtain the MO, parameters,
alarms, and KPIs of the existing software version, please refer to the product manuals of the existing software version.
This document is applicable to LTE FDD mode. "LTE" or "eNodeB" or “eNB” mentioned in this document respectively refer to "LTE FDD" and "LTE FDD-based eNodeB".
1.1 Related Feature List and License Control
Table 1‑1 Related Feature List and License Control
No Feature ID Feature Name License Control Technical Part

or not
1 ZLF31-12-001 Dedicated Carrier Sharing Yes 3.1.2.1
2 ZLF31-12-002 Shared Carrier Sharing Yes 3.1.2.2
3 ZLF31-12-003 Multi PLMN Support Yes 3.2
4 ZLF31-12-004 UE Route Selection Yes 3.2.3
5 ZLF31-12-005 Basic Mobility Control of Yes 3.4
RAN Sharing
6 ZLF31-12-006 Transport Traffic Separation Yes 3.4.5
of RAN Sharing
No Feature ID Feature Name License Control Technical Part
or not
7 ZLF31-12-007 Operator Specific Radio Yes 3.3.2
Resource Management
8 ZLF31-12-008 Inter PLMN Mobility Yes 3.4
9 ZLF31-12-009 Operator Specific Transport Yes 3.3.1
Resource Management
10 ZLF31-12-010 IRAT L>U Mobility of RAN Yes 3.4
Sharing
11 ZLF31-12-011 Operator Specific PM/FM Yes 4.3.3
12 ZLF31-12-012 Voice Management (CSFB Yes 3.4.4
to UTRAN) of RAN Sharing
13 ZLF31-12-013 IRAT L>G Mobility of RAN Yes 3.4
Sharing
14 ZLF31-12-014 Voice Management (CSFB Yes 3.4.4
to GERAN) of RAN Sharing
15 ZLF31-12-015 Operator specific Yes 3.3.2.5
User/Service priority
management of Shared
Carrier
16 ZLF31-12-016 Operator Specific RRC Yes 3.3.2.4
Resource Management of
Shared Carrier
17 ZLF31-12-017 Further multi PLMN Shared Yes 3.1.2.2
Carrier
18 ZLF31-12-018 Operator Specific Yes 3.4.5
Customized Subscription
Based Mobility
Management
19 ZLF31-12-019 Intra-LTE ANR of Dedicated Yes 3.5.1
Carrier Sharing
20 ZLF31-07-039 Multi PLMN Mobility Yes 3.4.5
Management Enhancement
21 ZLF31-12-020 Operator Group Level Yes 3.3.2.1
Radio Resource Sharing
1.2 Correlation with Other Features
Table 1‑2 Correlation with Other Features
Feature ID Feature Name Required Mutually Impacted

Feature Exclusive Feature
Feature
ZLF31-12- Dedicated Carrier None None None
001 Sharing
ZLF31-12- Shared Carrier None None None
002 Sharing
ZLF31-12- Multi PLMN None None None
003 Support
ZLF31-12- UE Route Selection None None None
004
ZLF31-12- Basic Mobility None None None
005 Control of RAN
Sharing
ZLF31-12- Transport Traffic None None None
006 Separation of RAN
Sharing
ZLF31-12- Operator Specific None None None
007 Radio Resource
Management
ZLF31-12- Inter PLMN Mobility None None None
008

009 Transport Resource
Management
ZLF31-12- IRAT L>U Mobility None None None
010 of RAN Sharing
011 PM/FM
ZLF31-12- Voice Management None None None
012 (CSFB to UTRAN)
of RAN Sharing
ZLF31-12- IRAT L>G Mobility None None None
013 of RAN Sharing
ZLF31-12- Voice Management None None None
014 (CSFB to GERAN)
of RAN Sharing
Feature ID Feature Name Required Mutually Impacted
Feature Exclusive Feature
Feature
ZLF31-12- Operator specific None None None
015 User/Service
priority
management of
Shared Carrier
016 RRC Resource
Management of
Shared Carrier
ZLF31-12- Further multi PLMN ZLF31-12-002 None None
017 Shared Carrier ZLF31-12-003
ZLF31-12-004
ZLF31-12- Operator Specific ZLF31-12-005 None None
018 Customized ZLF31-12-010
Subscription Based ZLF31-12-012
Mobility ZLF31-12-013
Management ZLF31-12-014
ZLF31-12- Intra-LTE ANR of ZLF31-12-001 None None
019 Dedicated Carrier
Sharing
ZLF31-07- Multi PLMN None None None
039 Mobility
Management
Enhancement
ZLF31-12- Operator Group
020 Level Radio
Resource Sharing
1.2.1 ZLF31-12-017 Further multi PLMN Shared Carrier
Required Feature:
ZLF31-12-002 Shared Carrier Sharing
ZLF31-12-003 Multi PLMN Support
ZLF31-12-004 UE Route Selection
Without these function, further multi PLMN Shared Carrier cannot work normally.
Exclusive Feature:
None
Impacted Feature:
None
1.2.2 ZLF31-12-018 Operator Specific Customized Subscription Based Mobility Management
l Required Feature:
ZLF31-12-005 Basic Mobility Control of RAN Sharing
ZLF31-12-010 IRAT L>U Mobility of RAN Sharing
ZLF31-12-012 Voice Management (CSFB to UTRAN) of RAN
Sharing
ZLF31-12-013 IRAT L>G Mobility of RAN Sharing
ZLF31-12-014 Voice Management (CSFB to GERAN) of RAN
Sharing
Without these functions, Operator Specific Customized Subscription Based Mobility Management cannot work normally.
Exclusive Feature:
None
Impacted Feature:
None
1.2.3 ZLF31-12-019 Intra-LTE ANR of Dedicated Carrier Sharing
Required Feature:
ZLF31-12-001 Dedicated Carrier Sharing
Only when Dedicated Carrier Sharing is enabled can Intra-LTE ANR of Dedicated Carrier Sharing work.
Exclusive Feature:
None
Impacted Feature:
None
2 Function Description
Network sharing is usually adopted by different operators to share high mobile network deployment cost, which greatly improves network utilization.
From the application point of view, network sharing can be classified into the following types:
- Virtual Network Operator (VNO): An operator completely shares another operator’s mobile network for virtual network operation.
- Site sharing: also known as passive sharing. Operators share site resources to resolve site acquisition problems and establish sites respectively.
- Roaming sharing: Operators establish networks in their respective geographical areas to achieve entire-network coverage by signing roaming protocols.
- Multi-Operator Core Network (MOCN) sharing: also known as active sharing. Operators share equipment on radio side and establish their respective core
networks.
- Gateway Core Network (GWCN) sharing: also known as active sharing. Operators share radio-side equipment and some core network equipment.
From the radio network point of view, network sharing can be classified into dedicated carrier and shared carrier:
- Dedicated carriers mean that operators share the eNodeB device, but do not share radio carriers.
- Shared carriers mean that operators share the same radio frequency band, or one of the operators or multiple operators share a radio frequency band of other
operators. The shared carrier mode is more advanced than the dedicated carrier mode. Multiple operators share not only the eNodeB device, but also radio
carriers. In shared carrier mode, multiple operators can share a carrier.
This document focuses on MOCN sharing and the key technical points are covered:
- Shared carrier and dedicated carrier
- Multi-PLMN broadcasting
- UE routing
- Mobility management in network sharing
- Radio resource sharing management
- Transmission resource sharing management
- Network sharing UEs/service priority management
- Network sharing RRC user proportioning
- Network sharing performance/alarm management
3 Technical Description
3.1 Basic Networking Modes
3.1.1 Network Sharing Mode

Viewed from the core network, the 3GPP 23.251 protocol defines two basic sharing architectures for reference: Multi-Operator Core Network (MOCN) and Gateway Core
Network (GWCN).
3.1.1.1 MOCN
The figure below shows the MOCN architecture, in which one eNodeB is connected to multiple core network nodes. Multiple operators share this eNodeB, which provides
services for these operators.
Figure 3-1 MOCN Network Sharing
The MOCN architecture provides the following features:
- Each operator owns its independent core network.
- Multiple operators share the same access network, namely, the eNodeB.
- The eNodeB selects an appropriate core network NE for a UE according to UE messages.
3.1.1.2 GWCN
The figure below shows the GWCN architecture, in which operators share both the access network and some core network nodes. The operators share not only the
eNodeB but also some core network devices (such as MME).In GWCN mode, E-UTRAN is completely shared by operators, so more consideration will be given to carrier
frequency sharing.
Figure 3-2 GWCN Network Sharing
The GWCN architecture provides the following features:
- Operators share some core network NEs.
- Multiple operators share the same access network, namely, the eNodeB.
- The eNodeB transmits UE messages transparently. The shared core network NE selects an appropriate core network NE for a UE.
3.1.2 Radio Carrier Sharing Mode

Viewed from the radio side, radio carriers are divided into shared carriers and dedicated carriers based on whether carriers are shared or not.
Dedicated carriers mean that operators share the eNodeB device, but do not share radio carriers. Shared carriers mean that operators share the same radio frequency
band, or one of the operators or multiple operators share a radio frequency band of other operators. The shared carrier mode is more advanced than the dedicated carrier
mode. Multiple operators share not only the eNodeB device, but also radio carriers. In shared carrier mode, multiple operators can share a carrier.
3.1.2.1 Dedicated Carrier Network Sharing
In dedicated carrier network sharing mode (when GlobleSwitchInformation.ranSharSwch is set to “RAN Dedicated Carrier Mode”, which can be configured in EMS),
operators share the eNodeB device. However, they do not share radio carries. Inside the eNodeB, different cells that are logically independent are provided for multiple
operators.
Figure 3-3 Dedicated Carrier Network Sharing
Each cell broadcasts its unique PLMN ID. Because each cell only has one PLMN ID, a UE's operations are the same as those in the non-shared network.
The dedicated carrier provides the following features:
1. The dedicated carriers are based on the MOCN architecture or the GWCN architecture.
2. Each operator owns its independent carriers.
3. Each cell broadcasts its unique PLMN ID.
4. Each operator has its logically independent network, providing diversified services.
5. The dedicated carrier mode makes balance between saving cost and keeping the network independent.
There is one dedicated carrier network sharing modes:

1. Mode 1: When eNodeB interacts S1 signaling with MME or X2 with eNodeB, fill in the unique PLMN+eNodeB ID configured.
3.1.2.2 Shared Carrier Network Sharing
The shared carrier mode (when GlobleSwitchInformation.ranSharSwch is set “RAN Sharing Carrier Mode”, which can be configured in EMS) means that operators share a
radio frequency band, or one of the operators or multiple operators share a radio frequency band of other operators. The shared carrier mode is more advanced than the
dedicated carrier mode. Multiple operators share not only the eNodeB device, but also radio carries, and multiple operators can share a carrier.
Figure 3-4 Sharing Carrier Network Sharing
The sharing carrier provides the following features:
1. The shared carriers are based on the MOCN architecture or the GWCN architecture.
2. Operators share carriers.
3. Each cell broadcasts multiple PLMN IDs, but the first PLMN ID for each cell of the same eNodeB is the same as the PLMN ID of Global eNB ID for the eNodeB.
4. The discrete frequency spectrums of multiple operators are combined into a sequential frequency spectrum so that the performance (for example rate) of network can
be provided.
5. The traffic of operators is balanced dynamically, increasing the usage of the frequency spectrum.
3.2 Basic Functions
3.2.1 PLMN Negotiation between the Core Network and eNodeB

The PLMN negotiation between the core network and eNodeB is implemented through S1 Setup messages.
Figure 3-5 S1 Setup Process
In the S1 SETUP REQUEST message, the eNodeB carries the supported PLMN, including the PLMN in the Global eNB ID and the PLMN list broadcasted by the air
interface (which can be configured on EMS, EUtranCellFDD.refPlmn), and informs it to MME.
The contents of the S1 SETUP REQUEST message are displayed in the following table. In the table, the chapter numbers listed in the IE type and reference column
correspond to the chapters in the TS36.413 protocol.
Table 3‑1 S1 Setup Request Message
IE/Group Presence Range IE type and Semantics Criticality Assigned

Name reference description Criticality
Message M 9.2.1.1 YES reject
Type
Global eNB M 9.2.1.37 YES reject
ID
eNB Name O PrintableString(1..150, YES ignore
…)
Supported 1..<maxnoofTACs> Supported GLOBAL reject
Tas Tas in the
eNB
>TAC M 9.2.3.7 Broadcasted -
TAC
>Broadcast 1.. Broadcasted -
PLMNs <maxnoofBPLMNs> PLMNs
>>PLMN M 9.2.3.8
Identity
CSG Id List 0 to < GLOBAL reject
maxnoofCSGIds >
>CSG Id M 9.2.1.62
Default M 9.2.1.16 YES ignore
paging
DRX
The S1 SETUP RESPONSE message carries the PLMN list that the MME supports. The eNodeB saves the PLMN list that the MME supports.
The contents of the “S1 Setup Response” message are displayed in Table 3-2. The chapter numbers listed in the IE type and reference column correspond to the
chapters in the TS36.413 protocol.
Table 3‑2 S1 Setup Response Message

Message M 9.2.1.1 YES reject
Type
MME O PrintableString(1..150, YES ignore
Name …)
Served 1..<maxnoofRATs> The LTE GLOBAL reject
GUMMEIs related pool
configuration
is included
on the first
place in the
list.
>Served 1.. -
PLMNs <maxnoofPLMNsPer
MME>
>>PLMN M 9.2.3.8 -
Identity
>Served 1.. -
GroupIDs <maxnoofGroupIDs>
>>MME M OCTET STRING (2) -
Group ID
>Served 1.. -
MMECs <maxnoofMMECs>
>>MME M 9.2.3.12 -
Code
Relative M 9.2.3.17 YES ignore
MME
Capacity
Criticality O 9.2.1.21 YES ignore
Diagnostics
3.2.2 Broadcasting of the PLMN List
The PLMN list is broadcast through SIB1 messages.
Figure 3-6 Delivery of SIB1
The contents of the SIB1 message are as follows:

SystemInformationBlockType1 ::= SEQUENCE {
cellAccessRelatedInfo SEQUENCE {
plmn-IdentityList PLMN-IdentityList,
trackingAreaCode TrackingAreaCode,
cellIdentity CellIdentity,
cellBarred ENUMERATED {barred, notBarred},
intraFreqReselection ENUMERATED {allowed, notAllowed},
csg-Indication BOOLEAN,
csg-Identity BIT STRING (SIZE (27)) OPTIONAL
},
cellSelectionInfo SEQUENCE {
q-RxLevMin Q-RxLevMin,
q-RxLevMinOffset INTEGER (1..8) OPTIONAL -- Need OP
},
p-Max P-Max OPTIONAL,
freqBandIndicator INTEGER (1..64),
schedulingInfoList SchedulingInfoList,
tdd-Config TDD-Config OPTIONAL, -- Cond TDD
si-WindowLength ENUMERATED {
ms1, ms2, ms5, ms10, ms15, ms20,
ms40},
systemInfoValueTag INTEGER (0..31),
nonCriticalExtension SEQUENCE {} OPTIONAL -- Need OP
}
3.2.3 PLMN Routing of UEs

A UE needs to select a PLMN when it initiates cell selection or reselection. The UE selects the PLMN, generally from the serving PLMN and the EPLMN, according to the
SIB1 message and the saved PLMN_ID List message. The eNodeB only needs to send the PLMN_ID to the relevant NE correctly.
The UE notifies the selected PLMN to the eNodeB through selected PLMN-Identity in the RRC CONNECTION SETUP COMPLETE message. The selected PLMN-Identity
parameter indicates the sequence number of the PLMN in the PLMN-Identity List. The eNodeB selects an MME according to the value and creates a TAI accordingly. Then
the TAI is added to the INITIAL UE Message and sent to the MME. Finally, the MME carries GUTI (including MCC, MNC, MME Group, and MME Code) and the EPLMN list
in the ATTACH ACCEPT message. GUTI is used to confirm the selected PLMN. The EPLMN list is used for the UE to update the EPLMN list.
In MOCN mode, the eNodeB selects the MME of the corresponding operator for the UE according to selected PLMN-Identity. In GWCN mode, the shared MME obtains the
PLMN information from the NAS message after it receives the message. Then, the MME selects the core NE of the corresponding operator for the UE.
Figure 3-7 Attach Process
Cell reselection may involve the TAU flow. Figure 3-11 shows the TAU flow. Similar to the ATTACH process, the eNodeB obtains the selected PLMN from selected PLMN-
Identity in the RRC CONNECTION SETUP COMPLETE message. Then the eNodeB adds the PLMN to the INITIAL UE Message and sends it to MME. The MME carries
GUTI (including MCC, MNC, MME Group, and MME Code) and the EPLMN list in TAU ACCEPT message.
Figure 3-8 TAU Process
The contents of the RRC CONNECTION SETUP COMPLETE message are as follows:
RRCConnectionSetupComplete-r8-IEs ::= SEQUENCE {
selectedPLMN-Identity INTEGER (1..6),
registeredMME RegisteredMME OPTIONAL,
dedicatedInfoNAS DedicatedInfoNAS,
nonCriticalExtension RRCConnectionSetupComplete-v8a0-IEs OPTIONAL
}
The Selected PLMN-Identity is the PLMN selected by the UE. The Selected PLMN-Identity corresponds to the index number of the PLMN in the PLMN-Identity List. The
value 1 stands for the first PLMN in the SIB broadcast, the value 2 stands for the second PLMN in the SIB broadcast, and so on.
The Initial UE Message must carry TAI IE, which includes the selected PLMN. As shown in Table 3-3, the chapter numbers listed in the IE type and reference column
correspond to the chapters in the TS36.413 protocol.
Table 3‑3 Initial UE Message
IE/Group Presence Range IE type Semantics Criticality Assigned

Name and description Criticality
reference
Message M 9.2.1.1 YES ignore
Type
eNB UE M 9.2.3.4 YES Reject
S1AP ID
NAS-PDU M 9.2.3.5 YES Reject
TAI M 9.2.3.16 Indicating YES Reject
the
Tracking
Area from
which the
UE has sent
the NAS
message.
E-UTRAN M 9.2.1.38 Indicating YES Ignore
CGI the E-
UTRAN
CGI from
which the
UE has sent
the NAS
message.
RRC M 9.2.1.3a YES Ignore
Establishment
cause
S-TMSI O 9.2.3.6 YES Reject
CSG Id O 9.2.1.62 YES Reject
IE/Group Presence Range IE type Semantics Criticality Assigned
Name and description Criticality
reference
GUMMEI O 9.2.3.9 YES Reject
Cell Access O 9.2.1.74 YES Reject
Mode
3.3 Resource Management
3.3.1 Transmission Resource Sharing Management

The transmission network supports the following two networking modes:
1. Independent transmission network
Some operators own several independent mobile and fixed transmission networks. These operators have established complete transmission networks. They want to
own the independent transmission networks and only share the eNodeB, relevant antenna stations, and other devices for LTE network construction.
Figure 3-9 Complete Sharing of Access Network (only the eNodeB is shared, the transmission network is independent)
2. Shared transmission network
For the operators who want to establish a transmission network together or share the transmission network of one operator, both the eNodeB and the transmission
network are shared.
Figure 3-10 Access Network Sharing (both the eNodeB and transmission network are shared)
3.3.1.1 Transmission Networking
Operators have their own network deployment plans if they have their independent transmission networks even if the transmission networks are shared. The eNodeB
provides the same or different VLANs and IP addresses for operators by configuring the association between the IP address (Used IP layer configuration) and operator in
the Service Map.
3.3.2 Radio Resource Management
3.3.2.1 Radio Resource Sharing Management
For dedicated carrier sharing mode, the cell resource is not shared by different operators because one carrier, namely, resource of one cell, is only used by an operator. So
the radio resource sharing management is a method for dividing radio resources that is only used for shared carrier sharing mode. Here, the radio resource refers to
Resource Block (RB).
The radio resource sharing mode can be divided into five cases according to the methods of dividing radio resources. In the following example, two operators share radio
resources.
Figure 3-11 Radio Resource Sharing Mode
l Case 1: Operator A and Operator B have their own fixed radio resources. x% of radio resources are assigned to Operator A and y% of radio resources are assigned to
Operator B. The remaining z% of radio resources are public resources and can be assigned flexibly to Operator A and Operator B according to their loads.
l Case 2: All radio resources are assigned to Operator A and Operator B, without public resources left. m% of radio resources is assigned to Operator A and n% of radio
resources is assigned to Operator B.
l Case 3: All the radio resources are public resources, and Operator A and Operator B share them.
l Case 4: Operator A and Operator B have their own fixed radio resources. m% of radio resources is assigned to Operator A and n% of radio resources is assigned to
Operator B. However, under some special conditions, for example, when Operator B has few users and little traffic in a period of time, Operator A can use some
resources of Operator B, and vice versa.
l Case5: Operators are grouped, and the groups can have multiple PLMNs. x% of radio resources are assigned to Operator group A and y% of radio resources are
assigned to Operator groupB. For the guaranteed GBR services, the resources are allocated first without consideration of resource proportion division. When the
network is congested, the resources are allocated according to the resource proportion of operator group; when the network is not congested, the users of all the
operators share all the radio resources.
On the EMS, users can configure the RB sharing mode by the parameter EUtranCellFDD.rbSharMode.
l When the RB sharing mode is configured to Case1/Case2/Case3/Case4, Resource Ratio of Operator n in Network Sharing (EUtranCellFDD.ratioOperatorn) and
Resource Ratio of Shared in Network Sharing (EUtranCellFDD.ratioShared) can be configured for each operator;
l When the RB sharing mode is configured to Case2 or Case4, the shared RB ratio must be 0%;
l When the RB sharing mode is configured to Case3, the shared RB ratio must be 100%;
l When the RB sharing mode is configured to Case5, operator PLMN group index (EUtranCellFDD.plmnGroupIndex), and the ratio of operator PLMN group
(EUtranCellFDD.ratioOperatorGroupn) should be configured, and the ratio should be larger than 4%. In Case 5, GBR service should be guaranteed, and the realted
parameter is (EUtranCellFDD.case5GuaranteedGBR).
Note:
1. In the current version, four operators can share radio resources.
2. In Case5 scenario, the parameters like (EUtranCellFDD.plmnGroupIndex, EUtranCellFDD.ratioOperatorGroupn, and EUtranCellFDD.case5GuaranteedGBR) do

not take effect in real time. They cannot take effect only when blocking /unblocking the cell manually after parameter modification.
According to the radio resource sharing mode configured by the operator, the eNodeB can implement the radio resource sharing management from both admission control
level and scheduling management level.
For the specific admission mechanism and RB resource allocation mechanism of GBR and NGBR services are the same as in non-network sharing scenario. For details,
refer to FDD Admission Control Feature Guide and FDD MAC Feature Guide. The difference in the network sharing scenario is that the total available cell bandwidth of
each operator's UE is controlled by the RB division method, and the RB assignment ratio of each operator and sharing ratio.
3.3.2.2 Admission Control
When a UE needs to create new services or modify services, the eNodeB performs the admission control on the UE according to the available cell bandwidth resources of
the UE’s operator.
l If the number of networks to which the cell belongs is 1 (namely, only one operator can use the cell resources) or the RB division mode is Case 3 (namely, all operators
can share the cell resources. For admission, it is unnecessary to differentiate between operators). The available bandwidth resources that can be used by the UE are
the total available bandwidth resources of the cell.
l If the RB division mode is Case 1, Case 2, or Case 4, the available bandwidth resources that can be used by the UE is the available cell bandwidth resources of the
UE's operator, which are calculated according to the total bandwidth of the cell, RB division mode, the operator's RB division ratio, and RB sharing ratio.
l If the RB sharing mode is Case5, the processing flow is as follows:
Figure 3-12 Case5 admission Control processing flow
If it is a guaranteed GBR service, perform admission according to the whole bandwidth.
l If the cell is not congested, perform admission according to the whole bandwidth. The cell congestion status are determined by the following parameters:
- EUtranCellFDD.case5CongJudPrd
- EUtranCellFDD.case5CongStarThrdUl
- EUtranCellFDD.case5RecoverThrdUl
- EUtranCellFDD.case5CongStarThrdDl
- EUtranCellFDD.case5RecoverThrdDl
Figure 3-13 Case5 congestion status Jugement
- In Case5, if EUtranCellFDD.case5RatioACSwch is configured to “Close”, perform admisison according to the whole bandwidth.
l If the actual scenario is beyond the descriptions above, perform admisison according to the available cell bandwidth resource of the operator which the UE belongs to, of
which the available cell bandwidth resource is determined by the total cell bandwidthm operator group RB ratio, and the occupied RBs of guaranteed GRB services,
etc.
Additionally, if the admission fails and the congestion control is enabled, only the services of the UEs that belong to the same operator can be released forcibly.
Note: When the RB sharing mode is Case5, the uplink services are admitted according to the whole bandwidth withour consideration of operator distinction.
3.3.2.3 Scheduling Management
The eNodeB allocates RB resources to a UE according to the UE's operator, number of operators that share the cell resources, RB division mode, operators’ RB division
ratios, and RB sharing ratios.
The solution is as follows:
l If the number of networks to which the cell belongs is 1 (namely, only one operator uses the cell resources) or the RB division mode is Case 3 (namely, the cell
resources are not divided and all operators can share the cell resources), the eNodeB does not need to allocate RB resources according to operators.
l If RB division mode is Case 1, Case 2, or Case 4, the eNodeB needs to allocate the RB resources according to the available resources of the operator.
When the RB sharing mode is Case5, calculate the operator’s available resources to allocate RB numbers for the UE according to the RB number for guarannteed GBR
service, the cell congestion status, and operator group ratio.
3.3.2.4 Proportional Division of the Number of RRC Users
In a carrier-shared network sharing scenario, an operator may occupy all user number resources in a cell, resulting in the users of other operators not being able to access
the cell. To avoid this problem, each operator is assigned with an RRC user number ratio to implement admission control over the users in a cell. In addition, the ratio of the
number of RRC users and the sliding window size of the number of RRC users can be used to maximize usage of RRC user-number resources.
The eNodeB can control the number of users that each operator can access according to the resource ratio configured when the following conditions are satisfied:
- The number of CELL PLMNs(EUtranCellFDD.refPlmn) is greater than 1 and
- The admission control algorithm switch for RRC user number of operator in network sharing (AC.rrcNum4NetSharSwch) is configured to “open”.
RRC user proportion division method of the network sharing can be divided into two types:
l One is to allocate the proportion of RRC user resources based on the PLMN;
l The other is to allocate the proportion of RRC user resource based on the PLMN group, and the operator group may include multiple PLMNs.
User can configure the allocation mode according to his own needs by configuring the parameter Allocation Mode of the Numbers of RRC Users in Network Sharing
Scenarios (AC.rRCResourceAllocationMode).
1. PLMN Based RRC User Number Resource Sharing,
Figure 3-14 PLMN Based RRC User Number Resource Sharing
- If the ratio of the remaining RRC users in the cell is larger than Window Length Of RRC User Number (AC.rrcNumWindowLength), it is considered that the
resource of the cell is sufficient and UEs of all operators can be accepted.
- If the ratio of the remaining RRC users in the cell is less than or equal to Window Length Of RRC User Number, and the current RRC user ratoi of the operator
has exceeded the ratio of the numbers of RRC users allocated based on PLMNs(AC.ratioOperatornOfRrcNum), the UEs of operator will be refused; otherwise,
normal access will be possible.
Note: RRC User Number Ratio = Online User Number/ Threshold of RRC Connection User Number (AC.ueNumThrd)
2. PLMN Group Based RRC User Number Resource Sharing
Figure 3-15 PLMN Group Based RRC User Number Resource Sharing.
The processing strategy is the same as 1, except that the RRC resource ratio of the operator is configured by Ratio of the Numbers of RRC Users Allocated Based on
PLMN Groups(AC.rRCRatio4PLMNGroup), and each operator group can configure multiple PLMNs.
Note: This version supports proportional division of the number of RRC users for two operators (or two operator groups).
3.3.2.5 Qos Management
In a network sharing scenario, to avoid or decrease the priority differences between the services of the same class, operators use different ARP mapping rules in the core
network. To ensure the fairness of occupying air-interface resources for the users who have the same-class service but belong to different operators, the eNodeB must
support the separate service priority configuration for each operator, which means that the service priorities are set for different PLMNs. This can correct the priority
differences between the services of the same class caused by the different ARP mapping rules of each operator in the core network.
Currently, this function can configure the basic priority, scheduling priority, and DSCP of services by PLMN. Specifically, by adding the key word “PLMN” in the basic priority
table (QoSPRIMapping), service priority table (ServicePrior), QoS parameter table (QoS), and DSCP and QCI mapping table (QoSDSCPMapping), the UE can configure
the basic priority, scheduling priority parameters (including uplink/downlink service factor priority, ARP scheduling weights, and uplink/downlink service priority scheduling
weights), and DSCP values by PLMN.
eNodeB can determine the basic priority value corresponding to specific PLMN by the parameter GlobleSwitchInformation.priBasedPLMNSwch.
1. When GlobleSwitchInformation.priBasedPLMNSwch is set to “Close”, the UE’s QoS parameters are not distinguished by PLMN. For the services of all UEs, the
global PLMN ID of the eNodeB (that is, PLMN ID in Global eNodeB ID) is used as the key word to read the basic priority of the UEs’ services
(QoSPRIMapping.qosBasicPrio) and determine scheduling priority parameters (including uplink/downlink service factor priority, ARP scheduling weights, and
uplink/downlink service priority scheduling weights) and DSCP values.
2. When GlobleSwitchInformation.priBasedPLMNSwch is set to “Open”, the UE’s QoS parameters are distinguished by PLMN. The current serving PLMN of the UE is
used as the key word to read the basic priority of the UE’s services (QoSPRIMapping.qosBasicPrio) and determine scheduling priority parameters (including
uplink/downlink service factor priority, ARP scheduling weights, and uplink/downlink service priority scheduling weights) and DSCP values.
3.4 Mobility in the Network Sharing

In the Network Sharing, mobility management need to consider the following various mobility scenarios:
l Mobility management within sharing LTE area;
l Mobility management between sharing LTE area and non-sharing LTE area;
l Mobility management between sharing LTE area and 3G/2G network;
l Mobility management between different operators(i.e. different PLMNs) within sharing LTE area;
l Mobility management between sharing LTE area and non-sharing LTE area for different operators(i.e. different PLMNs) ;
l Mobility management between sharing LTE area and 3G/2G network for different operators(i.e. different PLMNs).
Viewed from the eNodeB, mobility management in the Network Sharing for various mobility scenarios is mainly how to select appropriate mobility target cell (for handover)
or frequency (for redirection) according to PLMN information.
3.4.1 Handover
3.4.1.1 Coverage-Based Handover
The core network sends the handover restriction list to the eNodeB through the INITIAL CONTEXT SETUP REQUEST or DOWNLINK NAS TRANSPORT messages. when
eNodeB makes a handover decision, the eNodeB selects the target cell and target PLMN according to the handover restriction list, UE’s current serving PLMN , PLMNs
supported by neighbor cells and local PS PLMN policy (if the local PLMN policy based on Handover is enabled, i.e. EUtranCellMeasurement.multiPLMNLocSt4PSSwch
is set to “Open”), perform target cell and target PLMN selection. Besides, the inter-eNodeB inter-PLMN handover depends on the inter-PLMN handover switch
(GlobleSwitchInformation.interPlmnHOSwch).
1. The handover restriction list exists. The eNodeB filter the PLMNs of the candidate cells in the measurement report according to the handover restriction list, deletes the
unavailable PLMNs (the available PLMNs include UE’s service PLMN and EPLMN supported by the cell actually) and then makes a handover decision.
1) If the available PLMN list of a candidate cell includes the UE’s current serving PLMN, the eNodeB selects the candidate cell as the handover target cell, and the
UE’s current serving PLMN as the target PLMN. If there are several such candidate cells, the eNodeB selects the cell with the best signal quality as the handover
target cell.
2) If the available PLMN lists of the candidate cells do not include the UE’s current serving PLMN, and the local PLMN policy based on handover
(EUtranCellMeasurement.multiPLMNLocSt4PSSwch) is disabled, the eNodeB selects the cell with the best signal quality as the handover target cell, and a
random PLMN supported by the cell as the target PLMN.
(EUtranCellMeasurement.multiPLMNLocSt4PSSwch) is enabled, the eNodeB selects the cell with the highest PLMN priority from the available PLMNs, the
selection details as follows:
Sort the candidate cells based PLMN by local PS PLMN policy: the cell which supported the PLMN indicated by High priority MCC in local strategy and High
priority MNC in local strategy is in the first position, the cell which supported the PLMN indicated by Medium priority MCC in local strategy and Medium priority
MNC in local strategy is in the second position, the cell which supported the PLMN indicated by Low priority MCC in local strategy and Low priority MNC in local
strategy is in the third position, other cells(except the cells which only supported the PLMN indicated by Forbidden priority MCC in local strategy and Forbidden
priority MNC in local strategy)are ranked last in the random way.
The cell which is in the first position is the right cell with the highest PLMN priority. If there are several such cells, the eNodeB selects the cell with the best signal
quality as the handover target cell, and the PLMN as the target PLMN.
Table 3‑4 Related Parameters
Parameter Name Parameters

1 Multi-PLMN local EUtranCellMeasurement.multiPLMNLocSt4RdSwch
strategy for PS
2 High priority MCC in MultiPLMNLocSt.highPrioMcc
local strategy
3 High priority MNC in MultiPLMNLocSt.highPrioMnc
local strategy
4 Medium priority MCC MultiPLMNLocSt.mediumPrioMcc
in local strategy
5 Medium priority MCC MultiPLMNLocSt.mediumPrioMnc
in local strategy
6 Low priority MCC in MultiPLMNLocSt.lowPrioMcc
local strategy
7 Low priority MNC in MultiPLMNLocSt.lowPrioMnc
local strategy
8 Forbidden priority MultiPLMNLocSt.forbiddenMcc
MCC in local strategy
9 Forbidden priority MultiPLMNLocSt.forbiddenMnc
MNC in local strategy
10 Serving MCC in MultiPLMNLocSt.servMcc
Local Strategy
11 Serving MNC in MultiPLMNLocSt.servMnc
Local Strategy
12 Function of Local MultiPLMNLocSt.funcOfLocSt
Strategy
4) If there is no available PLMN, the eNodeB does not perform handover because no cell can be selected as the handover target cell.
2. The handover restriction list does not exist. All cells in the measurement report are handover candidate cells.
1) If the PLMN list of a handover candidate cell includes the UE’s current serving PLMN, the eNodeB selects the candidate cell as the handover target cell, and the
UE’s current serving PLMN as the target PLMN. If there are several such candidate cells, the eNodeB selects the cell with the best signal quality as the handover
target cell.
(EUtranCellMeasurement.multiPLMNLocSt4PSSwch) is disabled, the eNodeB selects the cell with the best signal quality as the handover target cell, and a
random PLMN supported by the cell as the target PLMN.
3) If the available PLMN lists of the candidate cells do not include the UE’s current serving PLMN, and the local PLMN policy based on
handover(EUtranCellMeasurement.multiPLMNLocSt4PSSwch) is enabled, the eNodeB selects the cell with the highest PLMN priority from the available
PLMNs, the selection details as following:
Sort the candidate cells based PLMN by local PS PLMN policy: the cell which supported the PLMN indicated by High priority MCC in local strategy and High
priority MNC in local strategy is in the first position, the cell which supported the PLMN indicated by Medium priority MCC in local strategy and Medium priority
MNC in local strategy is in the second position, the cell which supported the PLMN indicated by Low priority MCC in local strategy and Low priority MNC in local
strategy is in the third position, other cells are ranked last in the random way (except the cells which only supported the PLMN indicated by Forbidden priority
MCC in local strategy and Forbidden priority MNC in local strategy).
The cell which is in the first position is the right cell with the highest PLMN priority. If there are several cells with the same highest PLMN priority, the eNodeB
selects the cell with the best signal quality as the handover target cell, and the PLMN as the target PLMN.
Note:
1. The intra-eNodeB inter-PLMN handover is prohibited;
2. The inter-eNodeB inter-PLMN handover depends on the inter-PLMN handover switch (GlobleSwitchInformation.interPlmnHOSwch.
3. UEs with emergency calls cannot perform inter-PLMN handover.
4. The target cell and target PLMN selection method described above is applied to SRVCC, too.
5. For inter-eNodeB inter-PLMN UE handover triggered by any reason and the source eNodeB has no handover restriction list, only using S1 handover, because if using
X2 handover, the source eNodeB cannot tell the target PLMN to the target eNodeB which may lead to handover failure.
3.4.1.2 PLMN-Based Frequency Priority Handover
After operators agree on network sharing, the existing non-shared networks are transformed to shared networks step by step. During the transforming stage, when the UEs
in a non-local network frequency band move from a shared area to a non-shared area, intra-frequency interference may occur. For example, a UE of operator A moves
from a 1.8 G high-frequency band cell in a shared area to a non-shared area, the UE needs to be handed over to a cell of the same operator on the basis of coverage when
the UE reaches the cell edge. However, because the cell of operator A is a 1.8 G low-frequency band cell, intra-frequency interference to the cell occurs if there is a 1.8 G
high-frequency band neighbor cell of operator B. The inter-frequency measurement of the 1.8 G low-frequency band may not be reported, while the intra-frequency
measurement of the 1.8 G high-frequency band can be reported but the UE cannot be handed over (because the target cell belongs to operator B) and a call drop occurs.
Figure 3-16 Intra-frequency interference in the boundary area of shared area and non-shared area
To deal with intra-interference, the UEs in the eNodeB area at the edge ring of the yellow MOCN can be handed over to the frequency of the local network, that is, the
frequency priority-based handover function in the PLMN is used to solve the problems in large-scale network transformation and deployment.
Specifically, when a UE accesses a network, re-establishes a connection, or is handed over to a network, if the frequency priority-based handover function
(GlobleSwitchInformation.hoBaseFreqPriSwch) in the PLMN is enabled, the eNodeB needs to determine whether to hand over the UE blindly according to the UE’s
current serving PLMN (PlmnFreqPri.mcc, PlmnFreqPri.mnc) and the corresponding handover frequency list (PlmnFreqPri.freqNum,
PlmnFreqPri.plmnFreqParasFDD.freqBandInd, PlmnFreqPri.plmnFreqParasFDD.centerFreqDl, that is, the list of frequencies that can be provided to the local
operator’s UEs by other operators) after the UE’s access, reestablishment, or handover succeeds.
l If the frequency of the cell where the UE is located is in the handover frequency list of the corresponding PLMN configured at EMS (which means that the UE is on the
frequency of the local operator), no handover is required.
l Otherwise, the UE is not on the frequency of the local operator. The list of intra-site handover candidate neighbor cells that have the same coverage as, or contain the
cell where the UE is located and support the UE’s current serving PLMN are selected. According to the priorities of the frequencies
(PlmnFreqPri.plmnFreqParasFDD.freqPriBasPLMN) in the list, a neighbor cell that has the highest priority and is supported by the UE is selected from the hadover
candidate neighbor cell list as the target cell to which the UE is forcibly handed over.
Note:
Currently, only intra-LTE, intra-site blind handovers that are based on the frequency priority in the PLMN is supported. In network planning stage, the sites whose frequency
priority-based handover function is enabled have co-site inter-frequency neighbor cells that have the same coverage as, or contain the local cell and have sufficient cell
resources. This ensures the success rate of such handovers and effectively resolves intra-frequency interference.
3.4.2 Redirection
Redirection consists of measurement based redirection and blind redirection.
In network sharing scenario, PLMN selection policy for measurement based redirection is the same as that of coverage based handover, see 3.2.6.1.1. The PLMN
selection policy for blind redirection is described as follows:
When making a blind redirection decision, the eNodeB selects the redirection frequency in accordance with the UE's current serving PLMN, handover restriction list,
PLMNs supported by neighbor cells, local redirection PLMN policy (if the local PLMN policy based on redirection is enabled,
i.e.EUtranCellMeasurement.multiPLMNLocSt4RdSwch is set “Open”), redirection RAT priority, and redirection frequency priority.
1. The handover restriction list exists.
1) The eNodeB selects redirection candidate frequencies with a non-zero priority that is supported by the UE capacity and is not forbidden according to the handover
restriction list, redirection RAT priority, redirection frequency priority, and UE capacity.
2) According to the UE's current serving PLMN, EPLMN (if there are EPLMN list in the handover restriction list), local redirection PLMN policy
(ifEUtranCellMeasurement.multiPLMNLocSt4RdSwch is set “Open”), and the eNodeB ranks the redirection candidate frequencies by PLMN, and determines the
redirection candidate frequency list. The selection details as following:
The frequency which the neighbor cells with this frequency supported the UE’s current PLMN service PLMN is in the first position;
If there are EPLMN list in the handover restriction list, select the frequency which the neighbor cells with this frequency supported the EPLMN and rank it
according to local redirection PLMN policy:
If EUtranCellMeasurement.multiPLMNLocSt4RdSwch is set “Open”, Sort the candidate cells based PLMN by local PS PLMN policy: the cell which supported
the PLMN indicated by High priority MCC in local strategy and High priority MNC in local strategy is in the second position, then the cell which supported the
PLMN indicated by Medium priority MCC in local strategy and Medium priority MNC in local strategy, the cell which supported the PLMN indicated by Low priority
MCC in local strategy and Low priority MNC in local strategy. Other cells are ranked last in the random way (except the cells which only supported the PLMN
indicated by Forbidden priority MCC in local strategy and Forbidden priority MNC in local strategy).
If there are several such frequencies and EUtranCellMeasurement.multiPLMNLocSt4RdSwch is set “Close”, sort the frequencies randomly. The frequency
which is in the first position is the right frequency with the highest PLMN priority.
3) If there are several frequencies with the same highest PLMN priority in the redirection candidate frequency list, the eNodeB selects the frequency with the highest
redirection RAT priority and highest redirection frequency priority as the redirection frequency.
2. The handover restriction list does not exist.
1) The eNodeB selects redirection candidate frequencies with a non-zero priority that is supported by the UE capacity according to the redirection RAT priority,
redirection frequency priority, and UE capacity.
2) According to the UE's current serving PLMN, and local redirection PLMN policy (if EUtranCellMeasurement.multiPLMNLocSt4RdSwch is set “Open”), the
eNodeB ranks the redirection candidate frequencies by PLMN, and determines the redirection candidate frequency list. The selection details as following:
The frequency which the neighbor cells with this frequency supported the UE’s current PLMN service PLMN is in the first position;
Then the frequencies of other PLMN neighbor cells are ranked according to redirection PLMN policy:
If EUtranCellMeasurement.multiPLMNLocSt4RdSwch is set “Open”, Sort the candidate cells based PLMN by local PS PLMN policy: the cell which supported
the PLMN indicated by High priority MCC in local strategy and High priority MNC in local strategy is in the second position, then the cell which supported the
PLMN indicated by Medium priority MCC in local strategy and Medium priority MNC in local strategy, the cell which supported the PLMN indicated by Low priority
MCC in local strategy and Low priority MNC in local strategy. Other cells are ranked last in the random way (except the cells which only supported the PLMN
indicated by Forbidden priority MCC in local strategy and Forbidden priority MNC in local strategy).
If there are frequencies which the neighbor cells with this frequency supported other PLMNs and EUtranCellMeasurement.multiPLMNLocSt4RdSwch is set
“Close”, sort the frequencies randomly. The frequency which is in the first position is the right frequency with the highest PLMN priority.
3) If there are several frequencies with the same highest PLMN priority in the redirection candidate frequency list, the eNodeB selects the frequency with the highest
redirection RAT priority and highest redirection frequency priority as the redirection frequency.
Note:
1. For a UE with an emergency call, only the frequency that supports the UE's current serving PLMN can be selected as the blind redirection frequency.
2. The redirection frequency selection method is applied in all blind redirection triggered by various reasons (except CSFB by redirection).
3.4.3 Re-Establishment
For RRC connection reestablishment in network sharing scenario, if Multi-PLMN local strategy for RRC connection re-establishment
EUtranCellMeasurement.multiPLMNLocSt4ReestabSwch is configured to “Open”, Multi-PLMN local strategy for RRC connection re-establishment will be effective. And
the operator can configure different local strategy of RRC connection re-establishment for different PLMNs.
3.4.4 CSFB
When the core network sends the CS Fallback Indicator to the eNodeB through the INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST,
eNodeB will trigger CSFB.
CSFB consists of handover and redirection. In network sharing scenario, in terms of handover based CSFB and redirection based CSFB, PLMN selection policy is different
from that of normal handover and redirection. For details, refer to FDD CSFB Feature Guide.
3.4.5 Operator Specific Customized Subscription Based Mobility Management
In network-sharing scenarios, to enable a subscriber to stay in its home network as long as possible or enable a roaming subscriber to return to its home network as early
as possible, the operator can enable the subscriber to perform handover to a cell of its home network as soon as possible according to the information about the Home
Public Land Mobile Network (HPLMN) corresponding to the customized Subscriber Profile ID for RAT/Frequency priority (SPID).
In the network management system, the operator can configure HPLMN information corresponding to customized SPIDs (namely, SPID values not definitely defined in the
protocol; the SIPD values definitely defined in the protocol include 254, 255, and 256.)
When the eNodeB receives a customized SPID from the MME, and if the HPLMN information corresponding to the SPID exists in EMS, the eNodeB searches for all inter-
frequency carriers that support the HPLMN and delivers A4 measurement of the carriers to the UE. Once the UE is located in a home cell where the signal quality satisfies
the A4 measurement condition, the UE can perform handover to the home cell first.
For details, refer to FDD Subscription Based Mobility Management Feature Guide.
3.4.6 RIM Routing in RAN Sharing

The original RIM routing has no distinction for PLMM, that is, in MOCN scenario, eNodeB communicates with the core networks of all operators and obtains the neighbor
RIM information of 3G/2G of each operator. This method is not efficient. To improve the efficiency, the parameter LTE PLMN Level RIM Optimization
(GlobleSwitchInformation.plmnRouteSwch) is introduced. It can separately control operator’s PLMNs. When the parameter is configured to “Open”, the eNodeB
communicates with the core network of the specified PLMN. Otherwise, it communicates with all the connected core networks.
3.5 Others
3.5.1 ANR of Dedicated Carrier Sharing
If the ANR function is required to be enabled in dedicated carrier-sharing scenarios to guarantee the correctness and uniqueness of ECGI information of unknown neighbor
cells. ANR operations are different according to the dedicated carrier methods.
The operator must configure the same and unique primary PLMN for each eNodeB in the dedicated carrier-sharing area. In addition, the primary PLMN and all the shared
PLMNs in this area should be configured for each eNodeB. Upon receiving the ECGI measurement result of the unknown neighboring cells reported by a UE, the eNodeB
does the following:
l If the PLMN in the ECGI is in the shared PLMN list but is different from the primary PLMN in the sharing area, the eNodeB replaces the PLMN with the primary PLMN if
GlobleSwitchInformation.rplcPLMNInRanSharSwch is configured to “Open”, and adds neighbor cells by using the new ECGI.
Note: The eNodeB does not replace the PLMN list supported by neighbor cells, but uses the PLMN in the ECGI reported by the UE and PLMN-IdentityList2 to make a
PLMN list for broadcasting.
l If the PLMN in the ECGI is not in the shared PLMN list, the eNodeB does not replace the EGCI in the measurement result, but adds neighbor cells by using the ECGI in
the measurement result.
For detailed information, refer to FDD ANR Feature Guide.
3.5.2 X2 Self-Setup in Dedicated Carrier Sharing
In dedicated carrier sharing scenario, X2 function should be enabled. To ensure X2 correctness, X2 operation varies with dedicated carrier sharing modes.
Mode 1:
The same with non RAN sharing methods, and there are no special requirements.
Mode 2:
Omitted
3.5.3 eNodeB Access Solution
Shared eNodeBs are connected to a mobile backhaul network through different physical interfaces or the same physical interface. An IP RAN bearer network or a UTN
network uses VLAN sub-interfaces to distinguish its own services and shared services and respectively connect them to their VPN networks.
An eNodeB can be respectively connected to a mobile backhaul network of operator 1 and a mobile backhaul network of operator 2 through VLAN logical sub-interfaces.
The eNodeB can be configured in the following modes according to the number and types of CC boards.
1. Single-CC co-physical-interface transmission
In this mode, a CC16 board or CCE board is configured, and a single transmission physical interface is used. To avoid the influence between the two mutually
independent networks of operator 1 and operator 2, different VLANs and IP addresses are configured for operator 1 and operator 2 in the eNodeB configuration, to
implement network isolation and separated service transmissions. The configuration is as follows:
Operator 1: one VLAN and the corresponding IP address, used for S1 signaling and services.
Operator 2: one VLAN and the corresponding IP address, used for S1 signaling and services. The X2 interface and network management system use the VLAN and
IP address of the primary operator.
2. Single-CC separate-physical-interface transmission
In this mode, a CCE board is configured, and two transmission physical interfaces are respectively used for operator 1 and operator 2. In this case, the traffic of the
two operators can be physically separated but needs to be distinguished through VLAN sub-interfaces. The configuration is as follows:
Operator 1: one independent physical interface, configured with a VLAN and corresponding IP address, used for S1 signaling and services.
Operator 2: one independent physical interface, configured with a VLAN and corresponding IP address, used for S1 signaling and services. The X2 interface and
network management system use the VLAN and IP address of the primary operator.
3. Dual-CC transmission
The configuration is similar to that of the single-CC cases. The above configuration modes are used according to the maintenance habits of the two operators. The IP
address configuration of an eNodeB must comply with the IP address section planned by the group. The IP address section of shared eNodeBs should be allocated
by the other party. Meanwhile, it must be guaranteed that the IP addresses configured for the eNodeBs are not in the same network segment and the eNodeBs have
different VLANs.
3.5.3.1 Bandwidth and QoS Requirements
The QoS requirement of shared eNodeBs on bearers must satisfy the basic QoS requirement by LTE eNodeBs on the bearer network. Compared with the single-operator
cases, both the number of cells and the bandwidth requirement are doubled.
3.5.3.2 Synchronization
Because the problem that clocks are not synchronized may be encountered in X2 interface handover among shared eNodeBs, it is recommended that all eNodeBs in the
shared network use the same clock source.
3.5.4 SN Addition in RAN Sharing
In the network sharing scenario, if you need to enable EN-DC (E-UTRA-NR Dual Connectivity) at the same time, refer to FDD EN-DC Feature Guide for SN addition policy
for flexible control of SNs (Secondary Node) under different PLMNs.
3.6 Performance Management in Network Sharing

In network sharing mode, the performance statistics provides counters and indicators for different PLMNs. The performance statistics contain different operators’ RRC
connections, activated users, cell throughput, packet loss rate, air interface delay, IP delay, and PRB usage, etc.
4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements
BPL0 does not support RB sharing. BPL1 and BPN series support RB division.
4.1.2 EPC Requirements
EPC needs to support delivering handover limitation list to eNodeB (this list carries target handover PLMN during the handover).
If EPC does not support delivering handover limitation list to eNodeB, handover failure may occur due to the fact that eNodeB on the target handover cannot decide the
PLMN to be served in multi-PLMN, which leads to low handover success rate.
EPC should support multi-PLMNs.
4.1.3 UE Requirement
No special requirements
4.1.4 Transmission Bandwidth Requirements
No special requirements
4.2 Function Activate
4.2.1 Basic Networking Modes Configuration
4.2.1.1 Related parameters
Table 4‑1 Network Sharing Parameters Configuration Rule
Parameter Parameter Range Default

SN Parameter
name explanation Value Value
RAN
sharing
switch. If
this switch
is set to “0”,
RAN
sharing is
not allowed,
else if this
switch is set
to “1”,RAN 0:{Close},
sharing is 1:{ RAN
allowed and Sharing
Ran the carrier Carrier
1 GlobleSwitchInformation.ranSharSwch Sharing sharing Mode}, Close
Switch mode is 2:{ RAN
sharing Dedicated
mode, else Carrier
if this switch Mode}
is set to
“2”,RAN
sharing is
allowed and
the carrier
sharing
mode is
dedicated
sharing
mode.
SN Parameter
Switch of
Inter-PLMN
HO. If this
switch is set
Switch of to “Open”, 0:{Close},
2 GlobleSwitchInformation.interPlmnHOSwch Inter Inter-PLMN Close
1:{Open}
PLMN HO HO is
allowed,
else Inter-
PLMN HO is
not allowed.
4.2.1.2 Ran Sharing Switch configuration
To test network sharing, open the “Ran Sharing Switch”;
1. If you want to test network sharing function, enter the EMS configuration management, click the button to set Ran Sharing switch to Shared [1], and then click on
the button and click save configuration.
2. Click Modify Area>Managed Element>Radio Parameter>LTE FDD>E-UTRAN Service Configuration>Global Switch, and set Ran Sharing switch to RAN
Sharing Carrier Mode[1] or RAN Dedicated Carrier Mode[2].
4.2.1.3 Dedicated Carrier Network Share Configuration
1. Select Modify Area - >Managed Element - >Operator, and Click button.
Figure 4-3 Operator Configuration
Then click the button to save the configuration, and then add the PLMN information, click Modify Area - > Managed Element - > Operator->PLMN, click the button to
configure PLMN.
Figure 4-4 PLMN Configuration
Then click the button to save the configuration, Similarly,configuretwo different operators and PLMN.
Figure 4-5 configuring multiple PLMN
After the PLMN configuration completed, then configure the business and DSCP mapping, see the 4.2.2.2.1 section of the multi carrier bandwidth independent
configuration program step.
2. Dedicated Carrier Switch Configuration
EMS Configuration Management, click Modify Area - >Managed Element ->Radio Parameter -> LTE FDD->E-UTRAN Service Configuration - > Global Switch, click
the button to Configure the Ran sharing switch for Ran Dedicated Carrier Mode [2].
Figure 4-6 Configure Ran Sharing Switch
Then click the button to save the configuration.
3. Switch for Replacing PLMN in RAN Share Area In Dedicated Carrier Mode Configure
EMS Configuration Management, click Modify Area - >Managed Element ->Radio Parameter -> LTE FDD->E-UTRAN Service Configuration - > Global Switch, click
the button to Configure Switch for Replacing PLMN in RAN Share Area In Dedicated Carrier Mode for Open [1].
Figure 4-7 Configure Switch for Replacing PLMN in RAN Share Area In Dedicated Carrier Mode
4. PLMN List for RAN Share Area In Dedicated Carrier Mode Configure
EMS Configuration Management, click Modify Area - >Managed Element ->Radio Parameter -> LTE FDD, click the button to Configure PLMN List for RAN
Share Area In Dedicated Carrier Mode.
Figure 4-8 PLMN List for RAN Share Area In Dedicated Carrier Mode Configure
4.2.1.4 Sharing Carrier Network Sharing Configuration

1. Refer to the 4.2.1.3 section of the PLMN configuration method, configure the 2 different PLMNs, and then configure the business and DSCP mapping, see section
4.2.2.2.2 multi carrier bandwidth sharing configuration steps.
2. Click Modify Area>Managed Element>Radio Parameter>LTE FDD>E-UTRAN Service Configuration>Global Switch, and set Ran Sharing switch to RAN
Sharing Carrier Mode[1]as shown below.
Then click the button to save the configuration.
4.2.2 Resource Management Configuration
Table 4‑2 Radio Resource Sharing Management related parameters
Parameter Parameter Default

SN Parameter Range Value
name explanation Value
The RB sharing
mode when
multiple operators
sharing the cell
radio resource.
The parameter is
valid when the
PLMN number of
this cell is more
than one.
Case1: each
operator occupies
a certain ratio of
the cell radio
resource, and
there are sharing
radio resource
which all of the
operators can
use, and
resource snatch
is not permitted
between
operators.
Case2: each 0:{Certain and
operator occupies shared ratio,
a certain ratio of Non-
the cell radio Preemptive},
resource, and 1:{Certain and
RB there are no no shared Fully
1 EUtranCellFDD.rbSharMode Sharing sharing radio ratio,Non- shared
Mode resources which Preemptive},
all of the
operators can 2:{Fully shared},
use, and 3: {Certain and
resource snatch no shared
is not permitted ratio,Preemptive}
between
operators.
Case3: all
operators share
the all radio
resource of the
cell, i.e. close the
RB sharing
function.
Case4: each
operator occupies
a certain ratio of
the cell radio
resource, and
there are no
sharing radio
resources which
all of the
operators can
use, and
resource snatch
is permitted
between
operators.
Resource Ratio
of Operator in
Network Sharing,
each value from
Resource
RatioOperatorn[0]
Ratio of
is respectively
2 EUtranCellFDD.ratioOperatorn Operator n [0,100] unit pct 0
corresponding to
in Network
the each PLMN
Sharing
ID in R_SRVCEL
which is
constituted with
MCC and MNC.
Resource
Ratio of Resource Ratio
3 EUtranCellFDD.ratioShared Shared in of Shared in [0,100] unit pct 100
Network Network Sharing.
Sharing
Admission Switch of PRB
control based GBR
algorithm service admission
switch for control, which 0: Close,
4 AC.switchForGbr hardware can determine Close
1: Open.
resource whether the GBR
based admission control
GBR algorithm is valid
service or not.
Switch of PRB
based GBR
Admission
service admission
control
control algorithm
algorithm
in downlink,
switch for 0:Close;
which can
5 AC.switchForGbrDl downlink Close
determine 1: Open.
PRB
whether downlink
based
PRB based GBR
GBR
service admission
service
control algorithm
is valid or not.
Switch of PRB
Admission based GBR
control service admission
algorithm control algorithm
switch for in uplink, which 0:Close,
6 AC.switchForGbrUl uplink can determine Close
1: Open.
PRB whether uplink
based PRB based GBR
GBR service admission
service control algorithm
is valid or not.
Admission Switch of PRB
control based NGBR
algorithm service admission
switch for control, which 0:{Close},
7 AC.switchForNGBR hardware can determine Close
1:{Open}.
resource whether the
based NGBR admission
NGBR control algorithm
service is valid or not.
Switch of PRB
based NGBR
Admission service admission
control control algorithm
algorithm in downlink,
switch for which can 0:{Close},
8 AC.switchForNGBRDl downlink determine Close
1:{Open}.
PRB whether downlink
based PRB based
NGBR NGBR service
service admission control
algorithm is valid
or not.
Switch of PRB
based NGBR
Admission
service admission
control
control algorithm
algorithm
in uplink, which
switch for 0:{Close},
can determine
9 AC.switchForNGBRUl uplink Close
whether uplink 1:{Open}.
PRB
PRB based
based
NGBR service
NGBR
admission control
service
algorithm is valid
or not.
This parameter
determines
whether the 0:{close},
algorithm is valid 1:{Congestion
or not. Admission process of Pre-
denied does not empting Own
Switch for trigger congestion Service Prior},
10 AC.switchForConCtl congestion process when 2: {Congestion close
control this switch is process of not
close; Admission Pre-empting
denied trigger Own Service},
congestion 3: { GBR
process when Compression }
this switch is
open.
Table 4‑3 Proportional Division of the Number of RRC Users related parameters

SN Parameter
SN Parameter
Admission control
algorithm switch
for RRC User
Number of
Operator in
Network Sharing,
When the switch
Admission
is opened, in
control
accordance with
algorithm
the current ratio 0:
switch for
of the RRC user {Close},
1 AC.rrcNum4NetSharSwch RRC User Close
number of
Number of 1:{Open}
operators to
Operator
determine
in Network
whether to accept
Sharing
the user; When
the switch is
close, the RRC
user number
does not
distinguish by the
operator.
RRC user
number Resource
Ratio of Operator
RRC User in Network
Number Sharing, each
Resource value from
[0,100]
2 AC.ratioOperatornOfRrcNum Ratio of RatioOperatorn[0] N/A
unit pct
Operator n is respectively
in Network corresponding to
Sharing the each PLMN
ID in R_SRVCEL
which consists of
MCC and MNC.
This parameter is
used to prevent
an operator to
Window accept too many
Length Of RRC user [0,100]
3 AC.rrcNumWindowLength N/A
RRC User number to protect unit pct
Number at least
available.RRC
user number for
other operators.
This parameter
determines how
to allocate the
numbers of RRC
users in network
sharing 0: PLMN
scenarios. If it is Based
set to PLMN RRC
Allocation Based RRC User User
Mode of Number Number 0: PLMN
the Resource Resource Based
Numbers Sharing, the Sharing, RRC
4 AC.rRCResourceAllocationMode of RRC numbers of RRC 1: PLMN User
Users in users are Group Number
Network allocated by Based Resource
Sharing PLMN. If it is set RRC Sharing
Scenarios to PLMN Group User
Based RRC User Number
Number Resource
Resource Sharing.
Sharing, the
numbers of RRC
users are
allocated by
PLMN group.
This parameter
sets the ratio of
RRC resources
allocated to
Ratio of PLMN groups in
the network sharing
Numbers scenarios. From
of RRC left to right, the
[0,100]
5 AC.rRCRatio4PLMNGroup Users array elements N/A
unit pct
Allocated correspond to
Based on PLMN group 1,
PLMN PLMN group 2,
Groups PLMN group 3,
PLMN group 4,
PLMN group 5,
and PLMN group
6 separately.
SN Parameter
The parameter is
the threshold of
RRC Connection
user number. It
can be configured
Threshold
according to the
of RRC
numbers of client
6 AC.ueNumThrd Connection 0-65535 800
purchase. But the
User
max value
Number
configured will
not larger than
memory capacity
of one cell on
BPL board.
Table 4‑4 Qos Management related parameters
Parameter Parameter Parameter Range Default

SN
QoSPRIMapping.qosBasicPrio Basic prior based
QoS Basic
1 ARP and service 0-15 15
Priority
class
4.2.2.2 Transmission Resource Sharing Management
4.2.2.2.1 Multiple operators with independent bandwidth configuration
For multiple operators with independent bandwidth configuration, you need to configure Ran Sharing switch to RAN Sharing Carrier Mode[1] as shown in Figure 4-2.
And each operator is independently configured with bandwidth resources.The procedure is listed below:
i. Click Modify Area>Transmission Network>LTE FDD>Bandwidth Assignment>Bandwidth Resource Group
ii. Configure two bandwidth resource groups,as shown in Figure 4-10.
iii. Each bandwidth resource group configures a bandwidth resource, as shown in Figure 4-11.
iv. Each bandwidth resource is associated with different operator, as shown in Figure 4-12 and Figure 4-13.
4.2.2.2.2 Multiple operators with shared bandwidth configuration
Multiple operators with independent bandwidth configuration, you need to configure Ran Sharing switch toRAN Sharing Carrier Mode [1] as shown in Figure 4-2. And all
of operators configure one bandwidth resource.The procedure is list below:
1. Click Modify Area>Transmission Network>LTE FDD>Bandwidth Assignment>Bandwidth Resource Group
2. Configure one bandwidth resource group,as shown in Figure 4-14.
3. The bandwidth resource group configures two bandwidth resources, as shown in Figure 4-15.
4. Each bandwidth resource is associated with multiple operators, as shown in Figure 4-16 and Figure 4-17.
4.2.2.3 Radio Resource Management
4.2.2.3.1 Radio Resource Sharing Management
For testing network sharing function is based on RB division, In the Configuration Management window on the EMS, select [Modify Area> Radio Parameter > LTE FDD >
E-UTRAN FDD Cell]. Click button, Configure Case5 Related parameters. Click to save the configuration.
Figure 4-18 Configure Case5 Related parameters
4.2.2.3.2 Admission Control
Configure admission control algorithm
For testing admission control function is based on RB division, you should open admission control algorithm switch. The procedure is listed below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control, and Click
button.
2. Configure Admission Control Algorithm Switch for Hardware Resource Based GBR Service, Admission Control Algorithm Switch for Downlink PRB Based
GBR Service and Admission Control Algorithm Switch for Uplink PRB Based GBR Service to open[1] as shown below.
3. Click to save the configuration.
Figure 4-19 Configure Admission Control Algorithm
Configure Switch for Congestion Control
For testing congestion control function is based on RB division, you should open congestion control switch. The procedure is listed below:
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control, and Click
button.
2. Configure Switch for Congestion Control to Congestion Process of not Pre-Empting Own Service[2], as shown below.
Figure 4-20 Open Congestion Control Switch
4.2.2.3.3 Scheduling Management
Configure RB division mode and Resource Ratio.
For testing different RB division mode, you can configure the RB Sharing Mode. The procedure is listed below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell, and Click button.
2. Configure RB Sharing Mode, Resource Ratio of Operator in Network Sharing and Resource Ratio of Shared in Network Sharing according to Operator as
shown below.
Figure 4-21 Configure RB Division Mode and Resource Ratio
4.2.2.3.4 Proportional Division of the Number of RRC Users
For testing proportional division of the number of RRC users in Network Sharing, you should open Admission control algorithm switch for RRC User Number of Operator in
Network Sharing. The procedure is listed below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell >Admission Control, and Click
button.
2. Configure Admission control algorithm switch for RRC User Number of Operator in Network Sharing, Ratio of the Numbers of RRC Users Allocated Based
on PLMNs (%), Window Length Of RRC User Number, Allocation Mode of the Numbers of RRC Users in Network Sharing Scenarios and Ratio of the
Numbers of RRC Users Allocated Based on PLMN Groups (%) as shown below.
Figure 4-22 Configure Admission control algorithm for RRC User Number of Operator in Network Sharing
Figure 4-23 Configure Allocation Mode of the Numbers of RRC Users in Network Sharing Scenarios and Ratio of the Numbers of RRC Users Allocated Based on PLMN
Groups (%) in Network Sharing
4.2.2.3.5 Qos Management
For testing Qos management, you should configuration service basic priority. The procedure is listed below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD >Qos Configuration>QosBasic Priority, and Click
button.
2. Configure QoS Basic Priority, MCC and MNC, as shown below.
Figure 4-24 Configure QoS Basic Priority, MCC and MNC,
For testing Qos management, you should configuration Switch for QoS Configuration Based PLMN. The procedure is listed below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD >->E-UTRAN Service Configuration - > Global Switch,
and Click button.
2. Configure Switch for QoS Configuration Based PLMN to Open[1] as shown below.
Figure 4-25 Configure Switch for QoS Configuration Based PLMN
4.2.3 Mobility in the Network Sharing Configuration
Table 4‑5 Mobility in the Network Sharing configuration related parameters

SN Parameter
1 EUtranCellFDD.refPlmn PLMN List PLMN List N/A N/A
SN Parameter
Number of
Number of
PLMN List
PLMN List of
2 ExternalEUtranCellFDD.plmnIdList of 1-6 N/A
Neighboring
Neighboring
Cell
Cell
Mobile
MCC of Country Code
0-
3 ExternalEUtranCellFDD.mcc Neighboring of EUTRAN N/A
9,0xFF
Cell Neighboring
Cell
Mobile
MNC of Network Code
0-
4 ExternalEUtranCellFDD.mnc Neighboring of EUTRAN N/A
9,0xFF
Cell Neighboring
Cell
Number of Number of
PLMN List PLMN List of
5 ExternalUtranCellFDD.plmnIdList of UTRAN UTRAN 1-6 N/A
Neighboring Neighboring
Cell Cell
Mobile
MCC of Country Code
0-
6 ExternalUtranCellFDD.mcc Neighboring of UTRAN N/A
9,0xFF
Cell Neighboring
Cell
Mobile
MNC of Network Code
0-
7 ExternalUtranCellFDD.mnc Neighboring of UTRAN N/A
9,0xFF
Cell Neighboring
Cell
Number of Number of
PLMN List PLMN List of
8 ExternalGsmCell.plmnIdList of GERAN GERAN 1-6 N/A
Neighboring Neighboring
Cell Cell
Mobile
MCC of Country Code
0-
9 ExternalGsmCell.mcc Neighboring of GERAN N/A
9,0xFF
Cell Neighboring
Cell
Mobile
MNC of Network Code
0-
10 ExternalGsmCell.mnc Neighboring of GERAN N/A
9,0xFF
Cell Neighboring
Cell
Table 4‑6 Handover Switch Based Frequency Priority with PLMN

Handover switch based
Frequency Priority with
PLMN.When the switch
is opened,if the
access/handover-in
frequency is not the
Handover same with all
switch configured frequency in
based R_PLMNFREQPRI 0:Close,
1 GlobleSwitchInformation.hoBaseFreqPriSwch 0:close
Frequency (awInterCarriFreq in 1:Open
Priority R_PLMNFREQPRI),the
with PLMN new access/handover-
in user will be handover
to the high priority
frequency according to
the configuration based
PLMN(awInterCarriFreq
in R_PLMNFREQPRI).
Serving
Mobile The MCC of serving
2 PlmnFreqPri.mcc 0-9,0xFF N/A
country PLMN
code
Serving
mobile The MNC of serving
3 PlmnFreqPri.mnc 0-9,0xFF N/A
network PLMN
code
Candidate Frequency
frequency number for handover
4 PlmnFreqPri.freqNum 0-16 N/A
number based Frequency
Priority.
Band The parameter is band
indicator indicator of each
for DL 1-5,7-14,17-28,30-
5 PlmnFreqPri.plmnFreqParasFDD.freqBandInd candidate DL frequency N/A
frequency 32,33-64,101
for handover based
Frequency Priority.
(1:2110-2170,
2:1930-1990,
3:1805-1880,
4:2110-2155, 5:869-
894, 7:2620-2690,
8:925-960,
9:1844.9-1879.9,
10:2110-2170,
11:1475.9-1500.9,
12:728-746, 13:746-
756, 14:758-768,
17:734-746, 18:860-
875,19:875-
890,20:791
-821,21:1495.9-
1510.9, 22:3510-
List of candidate
3590,23:2180-
frequencies for
Downlink 2200,24:1525-
handover based
center 1559,25:1930-
6 PlmnFreqPri.plmnFreqParasFDD.centerFreqDl Frequency Priority.The N/A
carrier 1995,26:859-
actual size of the list is
frequency 894,27:852-
consistent with
869,28:758-803, 30:
PlmnFreqPri.freqNum.
380-
430,31:460,32;1785-
1805,33:1900-1920,
34:2010-2025,
35:1850-1910,
36:1930-1990,
37:1910-1930,
38:2570-2620,
39:1880-1920,
40:2300-2400,
41:2496-2690,
42:3400-3600,
43:3600-3800, 44-
64:0-5000,
101:1037-1057) unit
MHZ step 0.1
This array indicates
Frequency priority of every
Priority frequency, the higher
7 PlmnFreqPri.plmnFreqParasFDD.freqPriBasPLMN [0,255] N/A
based the value, indicating
PLMN that the frequency of
the higher priority.
Table 4‑7 Local Strategy configuration related parameters

In RAN Sharing
network PLMN
selection, the function
of local strategy.
If the parameter is
“CSFB”, the CSFB
function has the local
strategy; If the 0:{CSFB},
parameter is PS, the 1:{PS},
Function of PS function has the
1 MultiPLMNLocSt.funcOfLocSt 2: {Redirection}, N/A
local strategy local strategy; If the
parameter is 3:
Redirection, the {Reestablishment}
Redirection function
has the local strategy;
If the parameter is
“Reestablishment”, the
RRC connection re-
establishment function
has the local strategy.
In RAN Sharing
Serving MCC network PLMN
2 MultiPLMNLocSt.servMcc in local selection, the MCC of 0-9,0xFF N/A
strategy serving PLMN in local
strategy
In RAN Sharing
Serving MNC network PLMN
3 MultiPLMNLocSt.servMnc in Local selection, the MNC of 0-9,0xFF N/A
Strategy serving PLMN in local
strategy
In RAN Sharing
High priority network PLMN
4 MultiPLMNLocSt.highPrioMcc MCC in local selection, the MCC of 0-9,0xFF N/A
strategy high priority PLMN in
local strategy
In RAN Sharing
High priority network PLMN
5 MultiPLMNLocSt.highPrioMnc MNC in local selection, the MNC of 0-9,0xFF N/A
strategy high priority PLMN in
local strategy
In RAN Sharing
Medium
network PLMN
priority MCC
6 MultiPLMNLocSt.mediumPrioMcc selection, the MCC of 0-9,0xFF N/A
in local
medium priority PLMN
strategy
in local strategy
In RAN Sharing
Medium
network PLMN
priority MNC
7 MultiPLMNLocSt.mediumPrioMnc selection, the MNC of 0-9,0xFF N/A
in local
medium priority PLMN
strategy
in local strategy
In RAN Sharing
Low priority network PLMN
8 MultiPLMNLocSt.lowPrioMcc MCC in local selection, the MCC of 0-9,0xFF N/A
strategy low priority PLMN in
local strategy
In RAN Sharing
Low priority network PLMN
9 MultiPLMNLocSt.lowPrioMnc MNC in local selection, the MNC of 0-9,0xFF N/A
strategy low priority PLMN in
local strategy
In RAN Sharing
Forbidden network PLMN
10 MultiPLMNLocSt.forbiddenMcc MCC in local selection, the MCC of 0-9,0xFF N/A
strategy forbidden PLMN in
local strategy
In RAN Sharing
Forbidden network PLMN
11 MultiPLMNLocSt.forbiddenMnc MNC in local selection, the MNC of 0-9,0xFF N/A
strategy forbidden PLMN in
local strategy
If
ucMultiPLMNLocSt4PS
equal to 0,then Multi-
PLMN local strategy for
PS will not be effective;
If
Multi-PLMN 0:{Close},
ucMultiPLMNLocSt4PS
12 EUtranCellMeasurement.multiPLMNLocSt4PSSwch local strategy Close
equal to 1, Multi-PLMN 1:{Open}
for PS
local strategy for PS
will be effective; And
the operator can
configure different local
strategy of PS for
different PLMN.
If
ucMultiPLMNLocSt4Rd
equal to 0,then Multi-
PLMN local strategy for
Redirection will not be
effective;
Multi-PLMN If
local strategy ucMultiPLMNLocSt4Rd 0:{Close},
13 EUtranCellMeasurement.multiPLMNLocSt4RdSwch Close
for equal to 1, Multi-PLMN 1:{Open}
Redirection local strategy for
Redirection will be
effective; And the
operator can configure
different local strategy
of Redirection for
different PLMN.
If MultiPLMNLocSt4Rd
equal to 0, Multi-PLMN
local strategy for RRC
connection re-
establishment will not
be effective;
Multi-PLMN
If MultiPLMNLocSt4Rd
local strategy
equal to 1, Multi-PLMN 0:{Close},
for RRC
14 EUtranCellMeasurement.multiPLMNLocSt4ReestabSwch local strategy for RRC Close
connection 1:{Open}
connection re-
re-
establishment will be
establishment
effective. And the
operator can configure
different local strategy
of RRC connection re-
establishment for
different PLMN.
This parameter
controls RIM routing. If
it is set to 1, the
eNodeB communicates
LTE PLMN 0:{Close},
with the core network
15 GlobleSwitchInformation.plmnRouteSwch Level RIM Close
of the specified PLMN. 1:{Open}
Optimization
Otherwise, it
communicates with all
the connected core
networks.
4.2.3.2 Configuration
4.2.3.2.1 Coverage Based Handover
1. Open Switch of Inter PLMN HO.
For testing inter-PLMN handover, you should configure Switch of Inter PLMN HO to open [1]. The procedure is list below.
a) In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN Service Configuration > Global
Switch, and Click button.
b) Configure Switch of Inter PLMN HO to open [1].
c) Click to save the configuration.
Figure 4-26 Open Switch of Inter PLMN HO
1. Configure PLMN list of serving cell.
For testing PLMN which supported by serving cell, you should configure PLMN list of serving cell. The procedure is list below.
a) In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell > PLMN List, and Click
button.
b) Configure MCC and MNC according to Operator.
Figure 4-27 Configure PLMN List of Serving Cell
Note:
If Ran Sharing Switch is set to RAN Sharing Carrier Mode[1], PLMN the service cell supported configure one or more, and the first PLMN must be set to the
primary PLMN. If Ran Sharing Switch is set to RAN Dedicated Carrier Mode[2], PLMN the service cell supported configure only one, and PLMN the service cell
supported must be different with PLMN of the other service cell supported.
2. Configure PLMN of E-UTRAN FDD neighbor cell.
For testing PLMN which supported by E-UTRAN FDD neighbor cell, you should configure PLMN of E-UTRAN FDD neighbor cell. The procedure is list below.
a) In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > Neighbor Cell Configuration > E-UTRAN FDD
Neighbor Cell, and Click button.
b) Configure MCC of Neighboring Cell, MNC of Neighboring Celland PLMN List according to Operator.
Figure 4-28 Configure PLMN of Neighbor Cell
3. Configure PLMN of UTRAN FDD neighbor cell
For testing PLMN which supported by UTRAN FDD neighbor cell, you should configure PLMN of UTRAN FDD neighbor cell. The procedure is list below.
a) In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > Neighbor Cell Configuration > UTRAN FDD
Neighbor Cell, and Click button.
b) Configure MCC of Neighboring Cell, MNC of Neighboring Celland PLMN List according to Operator.
Figure 4-29 Configure PLMN of UTRAN FDD Neighbor Cell
4. Configure PLMN of GERAN neighbor cell
For testing PLMN which supported by GERAN neighbor cell, you should configure PLMN of GERAN neighbor cell. The procedure is list below.
a) In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > Neighbor Cell Configuration >GERAN Neighbor
Cell, and Click button.
b) Configure MCC of Neighbor Cell, MNC of Neighbor Celland PLMN List according to Operator.
Figure 4-30 Configure PLMN of GERAN Neighbor Cell
5. Configure Inter-Frequency, GERAN-Frequency, and UTRAN-Frequency.
a) Click Modify Area> Radio Parameter > LTE FDD >E-UTRAN FDD Cell>Measurement Parameter, and Click button.
b) Configure Inter-Frequency, GERAN-Frequency, and UTRAN-Frequency related parameters, as shown below.
Figure 4-31 Configure Inter-Frequency, GERAN-Frequency, UTRAN-Frequency
4.2.3.2.2 Handover Switch Based Frequency Priority with PLMN
For testing Frequency Priority with PLMN, open handover switch based frequency priority with PLMN. The procedure is list below:
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD >E-UTRAN Service Configuration>Global Swith, and Click
button.
2. Set Handover Switch Based Frequency Priority with PLMN to open, as shown below.
Figure 4-32 Configure Handover Switch Based Frequency Priority with PLMN
Configure the frequency priority with PLMN
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD >E-UTRAN FDD Cell>Frequency Priority Based PLMN,
2. Configure Serving PLMN, Frequency Number, Downlink Center Carrier Frequency Parametersas shown below.
Note: neighbor relation needs to be configured for the frequency configuration.
Figure 4-33 Configure Frequency Priority Based PLMN
4.2.3.2.3 Measurement Based Redirection
For Intra-RAT redirection based on measurement, need to add the following configurations on the basis of handover described.
1. Click Modify Area> Radio Parameter > LTE FDD >Neighbor Relation Configuration>E-UTRAN Neighbor Relation, and configure Switch for HO to No[0] as
shown below.
Figure 4-34 Configure E-UTRAN Neighbor Relation
For Inter-RAT redirection based on measurement, configure the neighbor relation to unsupported HO, also can set The Operation Method of LTE to UTRAN or The
Operation Method of LTE to GERAN to Redirection based on measurement as shown below.
1. Click Modify Area> Radio Parameter > LTE FDD >E-UTRAN FDD Cell>Measurement Parameter.
2. Set The Operation Method of LTE to UTRAN or The Operation Method of LTE to GERAN to Redirection based on measurement.
Figure 4-35 Configure Operation Method of LTE to UTRAN\GERAN
4.2.3.2.4 Blind Redirection
Blind redirection needs to configure RAT priority and redirection priority. The procedure is listed below:
1. Click Modify Area> Radio Parameter > LTE FDD >E-UTRAN FDD Cell>Measurement Parameter.
2. Configure RAT priority to non-zero.
3. Configure E-UTRAN Frequency Redirection Priority,UTRAN Frequency Redirection Priority,GERAN Frequency Redirection Priority, as shown below.
Figure 4-36 ConfigureRAT priority
Figure 4-37 E-UTRAN Frequency Redirection Priority
Figure 4-38 UTRAN Frequency Redirection Priority
Figure 4-39 GERAN Frequency Redirection Priority,
Note:
Blind redirection is only configured with frequency (without neighbor cell), but for multi-PLMN scene, and Ran-Share Policy of CSFB and blind redirection set to
Adaptive, when choosing the target cell, the frequency without neighbor cell has the lowest priority.
4.2.3.2.5 CSFB
See LTE FDD CSFB Feature Guide
4.2.3.2.6 Operator Specific Customized Subscription Based Mobility Management
See LTE FDD Subscription Based Mobility Management Feature Guide
4.2.3.2.7 Multi-PLMN Local Strategy
For testing local strategy function of networking sharing, you should open local strategy. The procedure is list below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Local Strategy for Multi-
PLMN, and Click button.
2. Configure Function of Local Strategy to PS\Redirection\ re-establishment, and configure Serving MCC in Local Strategy, Serving MNC in Local Strategy, High Priority
MCC in Local Strategy, High Priority MNC in Local Strategy, Medium Priority MCC in Local Strategy, Medium Priority MNC in Local Strategy, Low Priority MCC in
Local Strategy, Low Priority MNC in Local Strategy, Forbidden MCC in Local Strategy and Forbidden MNC in Local Strategy according to Operator as shown below.
Figure 4-40 Configure local strategy
l Configure Multi-PLMN local strategy for PS
For testing Multi-PLMN local strategy for PS, you should open the switch of Multi-PLMN local strategy for PS. The procedure is list below.
1. In the Configuration Management window on the EMS, select Modify Area> Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Measurement Parameter, and Click
button.
2. Configure Multi-PLMN local strategy for PS to Open [1] as shown below.
Figure 4-41 Configure Multi-PLMN local strategy for PS
l Configure Multi-PLMN local strategy for Redirection
For testing Multi-PLMN local strategy for Redirection, you should open the switch of Multi-PLMN local strategy for Redirection. The procedure is list below.
button.
2. Configure Multi-PLMN local strategy for Redirection to Open[1] as shown below.
Figure 4-42 Configure Multi-PLMN local strategy for Redirection
l Configure Multi-PLMN local strategy for RRC connection re-establishment
For testing Multi-PLMN local strategy for RRC connection re-establishment, you should open the switch of Multi-PLMN local strategy for RRC connection re-
establishment. The procedure is list below.
button.
2. Configure Multi-PLMN local strategy for RRC connection re-establishment to Open[1] as shown below.
Figure 4-43 Configure Multi-PLMN local strategy for RRC connection re-establishment
l Configure local strategy for CSFB
For testing local strategy for CSFB, you should open local strategy for CSFB. The procedure is list below.
button.
2. Configure Multi-PLMN local strategy for CSFB to Open, Switch for CS Fallback base LAI to Open as shown below.
Figure 4-44 local strategy for CSFB,
4.2.3.2.8 RIM Routing in RAN Sharing
In MOCN scenario, to obtain the neighbor RIM information of 3G/2G, the eNodeB can communicates with the core network of the specified PLMN.
When RIM routing according to PLMN is required, need to configure LTE PLMN Level RIM Optimization to “Open” as shown below.
Figure 4-45 Configuring LTE PLMN Level RIM Optimization
4.2.4 Others
Table 4‑8 PLMN Replacement under Dedicated Carrier Sharing

SN Parameter Range Value Unit
SN Parameter Range Value Unit
This parameter
indicates the switch
for Replacing PLMN
in RAN Share In
Dedicated Carrier
Mode. When the
switch is open, if the
Switch for PLMN of ECGI that
Replacing reported by UE is
PLMN in included in 0:Close,
1 GlobleSwitchInformation.rplcPLMNInRanSharSwch RAN Share RanSharMCC and N/A 0:close
1:Open
Area In RanSharMNC, eNB
Dedicated will replace the
Carrier Mode PLMN of ECGI with
the primary PLMN of
eNB. The new ECGI
is used to identify
neighbor cell. When
the switch is close,
eNB won't replace
the PLMN.
PLMN List
PLMN List for RAN
for RAN
Share Area In
2 ENBFunctionFDD.carrierShareAreaPlmnList Share Area 0-6 0 0
Dedicated Carrier
In Dedicated
Mode
Carrier Mode
MCC for
Broadcast
MCC for Broadcast
PLMN of
PLMN of RAN Share
3 ENBFunctionFDD.carrierShareAreaPlmnList.broadcastMCC RAN Share 0-9,0xFF N/A N/A
Area In Dedicated
Area In
Carrier Mode
Dedicated
Carrier Mode
MNC for
Broadcast
MNC for Broadcast
PLMN of
PLMN of RAN Share
4 ENBFunctionFDD.carrierShareAreaPlmnList.broadcastMNC RAN Share 0-9,0xFF N/A N/A
Area In Dedicated
Area In
Carrier Mode
Dedicated
Carrier Mode
MCC for
Primary
MCC for Primary
PLMN of
PLMN of RAN Share
5 ENBFunctionFDD.carrierShareAreaPlmnList.primaryMCC RAN Share 0-9,0xFF N/A N/A
Area In Dedicated
Area In
Carrier Mode
Dedicated
Carrier Mode
MNC for
Primary
MNC for Primary
PLMN of
PLMN of RAN Share
6 ENBFunctionFDD.carrierShareAreaPlmnList.primaryMNC RAN Share 0-9,0xFF N/A N/A
Area In Dedicated
Area In
Carrier Mode
Dedicated
Carrier Mode
Switch for QoS
Configuration Based
PLMN.When
PriBasedPLMNSwch
is Open, QoS Basic
Priority, ARP factor,
UL/DL service priory
level and UL/DL
service factor can
Distinguish
according to different
PLMNs; when
Switch for PriBasedPLMNSwch
QoS is Close, the QoS
7 GlobleSwitchInformation.priBasedPLMNSwch Close[0],Open[1] N/A 0
Configuration Basic Priority, ARP
Based PLMN factor, UL/DL service
priory level and
UL/DL service factor
for all UE not
according to PLMN
differentiated, are
taken as QoS Basic
Priority, ARP factor,
UL/DL service priory
level and UL/DL
service factor
corresponding to the
global PLMN.
4.2.4.2 Configuration
4.2.4.2.1 Dedicated Carrier Network Sharing ANR Configuration
Dedicated Carrier Network Sharing ANR Configuration is unchanged, see FDD ANR Feature Guide.
4.2.4.2.2 Dedicated Carrier Network Sharing X2 Configuration
Dedicated Carrier Network Sharing X2 Configuration is unchanged, see FDD X2 Self-Configuration Feature Guide.
4.2.4.2.3 SN Addition in RAN Sharing
Refer to FDD EN-DC Feature Guide.
4.2.5 Data Synchronization

Check the configuration and click Data Synchronization button.
4.2.6 Deactivate feature

To deactivate Network Sharing, set Ran Sharing switch to close.
5 Related Counters, KPI and Alarms
5.1 Related Counters
SN Counter Number Counter Name

Maximum Number of RRC Connection
1 C373200029
User
2 C373200030 Mean Number of RRC Connection User
3 C373384300 Average UL Active User Number(QCI=1)
12 C373384309 Average DL Active User Number(QCI=1)
Maximum UL Active User
21 C373384318
Number(QCI=1)
22 C373384319
Number(QCI=2)
23 C373384320
Number(QCI=3)
24 C373384321
Number(QCI=4)
25 C373384322
Number(QCI=5)
26 C373384323
Number(QCI=6)
27 C373384324
Number(QCI=7)
28 C373384325
Number(QCI=8)
29 C373384326
Number(QCI=9)
Maximum DL Active User
30 C373384327
Number(QCI=1)
31 C373384328
Number(QCI=2)
32 C373384329
Number(QCI=3)
33 C373384330
Number(QCI=4)
34 C373384331
Number(QCI=5)
35 C373384332
Number(QCI=6)
SN Counter Number Counter Name
36 C373384333
Number(QCI=7)
37 C373384334
Number(QCI=8)
38 C373384335
Number(QCI=9)
Maximum Number of UE that can be
39 C373384336
simultaneously
Minimum Number of UE that can be
40 C373384337
simultaneously
Average Number of UE that can be
41 C373384338
simultaneously
Maximum Active User Number on User
42 C373384348
Plane
Average Active User Number on User
43 C373384349
Plane
44 C373424608 PRB Number Used on Uplink Channel
PRB Number Available on Uplink
45 C373424609
Channel
46 C373424610 PRB Number Used on Downlink Channel
PRB Number Available on Downlink
47 C373424611
Channel
Number of RRC Connection Release by
ENB due to admission failure for RRC
48 C373200141
User Number of Operator in Network
Sharing
For the counters not so related to network sharing, please refer to the last chapter: Appendix
5.2 Related KPIs
Table 5‑2 Related KPIs
SN Counter Index Counter Name

1
310531 Maximum Cell DL PDCP Throughput
2
310532 Minimum Cell DL PDCP Throughput
3
310533 Average Cell DL PDCP Throughput
4
310534 Maximum Cell UL PDCP Throughput
5
310535 Minimum Cell UL PDCP Throughput
6
310536 Average Cell UL PDCP Throughput
7
310537 Maximum Cell DL RLC Throughput
8
310538 Minimum Cell DL RLC Throughput
9
310539 Average Cell DL RLC Throughput
10
310540 Maximum Cell UL RLC Throughput
11 310541 Minimum Cell UL RLC Throughput
12 310542 Average Cell UL RLC Throughput
13 310640 DL PDCP SDU Discard Rate(QCI=1)

DL PDCP SDU Air Interface Loss
22 310649
Rate(QCI=1)
23 310650
Rate(QCI=2)
24 310651
Rate(QCI=3)
SN Counter Index Counter Name
25 310652
Rate(QCI=4)
26 310653
Rate(QCI=5)
27 310654
Rate(QCI=6)
28 310655
Rate(QCI=7)
29 310656
Rate(QCI=8)
30 310657
Rate(QCI=9)
31 310658 UL PDCP SDU Loss rate(QCI=1)
40 310667 Average DL PDCP SDU Delay(QCI=1)
5.3 Related Alarms

None
6 Impact on Network
Impact on Equipment Performance:
None
Impact on Network KPIs:
Advantages of this feature:
1. Different operators can share network resources (including network equipment, wireless resources, transmission resources), which can save investment and also can
maximally utilize the network resource;
2. The shared carrier mode provides flexible resource management policies and mechanisms, and operators can choose different policies according to their different
requirements;
3. The shared transmission mode provides flexible resource management policies and mechanisms, and operators can choose flexible configuration according to
necessaries;
4. Provide rich mobility management policies and guarantee users’ service continuity;
5. Supports differentiated services for shared operators at the most extent by providing operator-level QoS mapping configuration and wireless scheduling policy;
6. Implement co-management and maintenance of shared network elements and dedicated network elements and provide operator-level performance management and
alarm management.
Disadvantages of this feature:
Resources allocations and managements, billing and network O&M among multiple operators will be more complicated
7 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.
8 References
1. 3GPP TS 36.331 V9.5.0 (2010-12) Radio Resource Control (RRC);
2. 3GPP TS 36.413 V9.5.2 (2010-12) S1 Application Protocol (S1AP);
3. 3GPP TS 23.401 V9.7.0 (2010-12) General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access;
4. 3GPP TS 23.251 V9.3.0 (2010-12) Network Sharing;
5. 3GPP TS 36.300 V9.6.0 (2010-12) Network Sharing Overall description.
6. FDD ANR Feature Guide
7. FDD X2 Self-Configuration Feature Guide.
8. FDD CSFB Feature Guide.

9. FDD Admission Control Feature Guide
10. FDD MAC Scheduling Feature Guide
11. FDD Subscription Based Mobility Management Feature Guide
12. FDD EN-DC Feature Guide
9 Appendix
SN Counter No. Description
1 C495000029 Maximum Number of RRC Connection User
2 C495000030 Mean Number of RRC Connection User
3 C374543600 Maximum Cell DL PDCP Throughput
4 C374543601 Minimum Cell DL PDCP Throughput
5 C374543602 Average Cell DL PDCP Throughput
6 C374543603 Maximum Cell UL PDCP Throughput
7 C374543604 Minimum Cell UL PDCP Throughput
8 C374543605 Average Cell UL PDCP Throughput
9 C374543606 Maximum Cell DL PDCP Throughput(QCI=1)
10 C374543607 Minimum Cell DL PDCP Throughput(QCI=1)
11 C374543608 Average Cell DL PDCP Throughput(QCI=1)
12 C374543609 Maximum Cell UL PDCP Throughput(QCI=1)
13 C374543610 Minimum Cell UL PDCP Throughput(QCI=1)
14 C374543611 Average Cell UL PDCP Throughput(QCI=1)
63 C374543660 Maximum Cell DL RLC Throughput
64 C374543661 Minimum Cell DL RLC Throughput
65 C374543662 Average Cell DL RLC Throughput
66 C374543663 Maximum Cell UL RLC Throughput
67 C374543664 Minimum Cell UL RLC Throughput
68 C374543665 Average Cell UL RLC Throughput
69 C374543666 Maximum Cell DL RLC Throughput(QCI=1)
70 C374543667 Minimum Cell DL RLC Throughput(QCI=1)
71 C374543668 Average Cell DL RLC Throughput(QCI=1)
72 C374543669 Maximum Cell UL RLC Throughput(QCI=1)
73 C374543670 Minimum Cell UL RLC Throughput(QCI=1)
74 C374543671 Average Cell UL RLC Throughput(QCI=1)
123 C374553900 UL PDCP SDU Loss Number,QCI=1
124 C374553901 UL PDCP SDU Loss Number,QCI=2
125 C374553902 UL PDCP SDU Loss Number ,QCI=3
132 C374553909 DL PDCP SDU Loss Number ,QCI=1
141 C374553918 DL PDCP SDU Discard Number ,QCI=1
150 C374553927 UL PDCP SDU Number ,QCI=1
159 C374553936 DL PDCP SDU Number ,QCI=1
DL PDCP SDU Number Which HARQ

168 C374553947
Successfully Responds ,QCI=1
169 C374553948
170 C374553949
171 C374553950
172 C374553951
173 C374553952
174 C374553953
175 C374553954
176 C374553955
177 C374553956 UL PDCP SDU Loss Number
178 C374553957 DL PDCP SDU Loss Number
179 C374553958 DL PDCP SDU Discard Number
180 C374553959 UL PDCP SDU Number
181 C374553960 DL PDCP SDU Number

182 C374553961
Successfully Responds
183 C374564100 DL QCI1 PDCP SDU Delay
192 C374564109 DL QCI1 IP Packet Delay
201 C374564118 DL PDCP SDU Delay
202 C374564119 DL IP Packet Delay
Average Bitrate of PDCP SDU in The UL in

203 C374574200
Control Plane
Maximum Bitrate of PDCP SDU in The UL in
204 C374574201
Control Plane
Average Bitrate of PDCP SDU in The DL in
205 C374574202
Control Plane
Maximum Bitrate of PDCP SDU in The DL in
206 C374574203
Control Plane
Average Bitrate of PDCP SDU in The UL
207 C374574204
(QCI=1)
208 C374574205
(QCI=2)
209 C374574206
(QCI=3)
210 C374574207
(QCI=4)
211 C374574208
(QCI=5)
212 C374574209
(QCI=6)
213 C374574210
(QCI=7)
214 C374574211
(QCI=8)
215 C374574212
(QCI=9)
Average Bitrate of PDCP SDU in The DL
216 C374574213
(QCI=1)
217 C374574214
(QCI=2)
218 C374574215
(QCI=3)
219 C374574216
(QCI=4)
220 C374574217
(QCI=5)
221 C374574218
(QCI=6)
222 C374574219
(QCI=7)
223 C374574220
(QCI=8)
224 C374574221
(QCI=9)
Maximum Bitrate of PDCP SDU in The UL
225 C374574222
(QCI=1)
226 C374574223
(QCI=2)
227 C374574224
(QCI=3)
228 C374574225
(QCI=4)

229 C374574226
(QCI=5)
230 C374574227
(QCI=6)
231 C374574228
(QCI=7)
232 C374574229
(QCI=8)
233 C374574230
(QCI=9)
Maximum Bitrate of PDCP SDU in The DL
234 C374574231
(QCI=1)
235 C374574232
(QCI=2)
236 C374574233
(QCI=3)
237 C374574234
(QCI=4)
238 C374574235
(QCI=5)
239 C374574236
(QCI=6)
240 C374574237
(QCI=7)
241 C374574238
(QCI=8)
242 C374574239
(QCI=9)
Maximum Bitrate of PDCP SDU in The UL in
243 C374574240
Traffic Plane
Maximum Bitrate of PDCP SDU in The DL in
244 C374574241
Traffic Plane
Average Bitrate of PDCP SDU in The UL in
245 C374574242
Traffic Plane
Average Bitrate of PDCP SDU in The DL in
246 C374574243
Traffic Plane
265 C374584318 Maximum UL Active User Number(QCI=1)
274 C374584327 Maximum DL Active User Number(QCI=1)
Maximum Number of UE that can be

283 C374584336
simultaneously
Minimum Number of UE that can be
284 C374584337
simultaneously
Average Number of UE that can be
285 C374584338
simultaneously
Maximum Active User Number on User
286 C374584348
Plane
287 C374584349 Average Active User Number on User Plane
288 C495224608 PRB Number Used on Uplink Channel
289 C495224609 PRB Number Available on Uplink Channel
290 C495224610 PRB Number Used on Downlink Channel
291 C495224611 PRB Number Available on Downlink Channel
Number of RRC Connection Release by ENB

292 C373200141 due to admission failure for RRC User
Number of Operator in Network Sharing
293 C495295200 Number of Send Init UE Message by ENB
Number of Received First Message by ENB

294 C495295201
after Init UE Mess
Number of Abnormal Release Active E-RAB
295 C495305499
Triggered
Number of Abnormal Release Active E-RAB
296 C495867454
Triggered by MME
297 C374543804 UL Aggregated Volume High
298 C374543805 UL Aggregated Volume Low
299 C374543806 DL Aggregated Volume High through Uu
300 C374543807 DL Aggregated Volume Low through Uu
Table 9‑2Related KPIs
SN
KPI No. Description
1 343031 Maximum Cell DL PDCP Throughput
2 343032 Minimum Cell DL PDCP Throughput
3 343033 Average Cell DL PDCP Throughput
4 343034 Maximum Cell UL PDCP Throughput
5 343035 Minimum Cell UL PDCP Throughput
SN
KPI No. Description
6 343036 Average Cell UL PDCP Throughput
7 343037 Maximum Cell DL RLC Throughput
8 343038 Minimum Cell DL RLC Throughput
9 343039 Average Cell DL RLC Throughput
10 343040 Maximum Cell UL RLC Throughput
11 343041 Minimum Cell UL RLC Throughput
12 343042 Average Cell UL RLC Throughput
13 343140 DL PDCP SDU Drop Rate(QCI=1)
22 343149 DL PDCP SDU Air Interface Loss Rate(QCI=1)
SN
KPI No. Description

FDD Network Sharing ZTE eReader-Browse

Uploaded by

Copyright:

Available Formats

You might also like

FDD Network Sharing ZTE eReader-Browse

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FDD Network Sharing ZTE eReader-Browse

Uploaded by

Copyright:

Available Formats

16/4/2020 FDD Network Sharing (LR18+)

FDD Network Sharing (LR18+)

FDD Network Sharing (LR18+)

Zhang No technical change

5 Related Counters, KPI and Alarms

Figure 3-1 MOCN Network Sharing

1.1 Related Feature List and License Control

Table 1‑1 Related Feature List and License Control

No Feature ID Feature Name License Control Technical Part

1.2 Correlation with Other Features

Table 1‑2 Correlation with Other Features

Feature ID Feature Name Required Mutually Impacted

ZLF31-12- Operator Specific None None None

1.2.1 ZLF31-12-017 Further multi PLMN Shared Carrier

1.2.2 ZLF31-12-018 Operator Specific Customized Subscription Based Mobility Management

1.2.3 ZLF31-12-019 Intra-LTE ANR of Dedicated Carrier Sharing

ZLF31-12-001 Dedicated Carrier Sharing

- Shared carrier and dedicated carrier

- Mobility management in network sharing

- Radio resource sharing management

- Transmission resource sharing management

- Network sharing UEs/service priority management

- Network sharing RRC user proportioning

- Network sharing performance/alarm management

3.1 Basic Networking Modes

3.1.1 Network Sharing Mode

Figure 3-1 MOCN Network Sharing

The MOCN architecture provides the following features:

- Each operator owns its independent core network.

- The eNodeB selects an appropriate core network NE for a UE according to UE messages.

Figure 3-2 GWCN Network Sharing

The GWCN architecture provides the following features:

- Operators share some core network NEs.

3.1.2 Radio Carrier Sharing Mode

3.1.2.1 Dedicated Carrier Network Sharing

Figure 3-3 Dedicated Carrier Network Sharing

The dedicated carrier provides the following features:

2. Each operator owns its independent carriers.

3. Each cell broadcasts its unique PLMN ID.

There is one dedicated carrier network sharing modes:

3.1.2.2 Shared Carrier Network Sharing

Figure 3-4 Sharing Carrier Network Sharing

The sharing carrier provides the following features:

2. Operators share carriers.

3.2 Basic Functions

3.2.1 PLMN Negotiation between the Core Network and eNodeB

Figure 3-5 S1 Setup Process

Table 3‑1 S1 Setup Request Message

IE/Group Presence Range IE type and Semantics Criticality Assigned

Table 3‑2 S1 Setup Response Message

IE/Group Presence Range IE type and Semantics Criticality Assigned

3.2.2 Broadcasting of the PLMN List

The PLMN list is broadcast through SIB1 messages.

Figure 3-6 Delivery of SIB1

The contents of the SIB1 message are as follows:

3.2.3 PLMN Routing of UEs

Figure 3-7 Attach Process

Figure 3-8 TAU Process

Table 3‑3 Initial UE Message