ZTE UMTS RAN Sharing Feature Guide PDF

RAN Sharing
Feature Guide
RAN Sharing
RAN Sharing
Version Date Author Reviewer Notes
Pang
V1.0 2014/06/28 Wang Juntao First edition
Xiufeng
2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 1

RAN Sharing
TABLE OF CONTENTS
1 Feature Attribute ............................................................................................... 8
2 Overview ............................................................................................................ 8
2.1 Feature Introduction ............................................................................................. 8
2.1.1 ZWF21-30-100 Basic Network Sharing Support ................................................... 9
2.1.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier ......................................... 10
2.1.3 ZWF21-30-102 Shared Network Access Control ................................................ 11
2.1.4 ZWF21-30-121 Operator Specific CE Resource ................................................ 12
2.1.5 ZWF21-30-120 Operator Specific FM/PM/CM.................................................... 12
2.1.6 ZWF21-30-116 Operator Specific Function Control............................................ 13
2.1.7 ZWF21-30-117 Operator QoS Priority ................................................................ 14
2.1.8 ZWF21-30-118 Operator Specific Iub/Iur Transmission ..................................... 15
2.1.9 ZWF21-30-119 Operator Specific RNC Resource .............................................. 16
2.1.10 ZWF21-30-122 Extended GSM Neighboring Cells ............................................. 16
2.1.11 ZWF21-30-200 Multi PLMN Support .................................................................. 16
2.2 License Control .................................................................................................. 17
2.3 Correlation With Other Features ........................................................................ 17
3 Technical Description ..................................................................................... 18

3.1 ZWF21-30-100 Basic Network Sharing Support ................................................. 18
3.1.1 RAN Sharing with GWCN .................................................................................. 18
3.1.2 RAN Sharing with MOCN ................................................................................... 20
3.1.3 PLMN Configuration Rule for Non-Sharing RNCs .............................................. 21
3.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier ......................................... 21
3.3 ZWF21-30-102 Shared Network Access Control ................................................ 22
3.3.1 Based on SNAC ................................................................................................. 22
3.3.2 Based on the PLMN-Id Label of the Cell ............................................................ 24
3.3.3 Based on the PLMN-Id Label of the LTE Neighbor Cell ..................................... 26
3.4 ZWF21-30-121 Operator Specific CE Resource ................................................ 27
3.4.1 Description of Operator Specific CE Resources ................................................. 27
3.4.2 CE-based Admission Control in PLMN............................................................... 30
3.4.3 Congestion Control When Cells in Different PLMNs Share the CE Resource .... 38
3.5 ZWF21-30-116 Operator Specific Function Control............................................ 43
3.6 ZWF21-30-117 Operator QoS Priority ................................................................ 44
3.7 ZWF21-30-118 Operator Specific Iub/Iur Transmission ..................................... 45
3.8 ZWF21-30-119 Operator Specific RNC Resource .............................................. 46
3.9 ZWF21-30-122 Extended GSM Neighboring Cells ............................................. 47
3.10 ZWF21-30-200 Multi PLMN Support .................................................................. 48

RAN Sharing
4 Parameters....................................................................................................... 48
4.1 ZWF21-30-100 Basic Network Sharing Support Parameter List ......................... 48
4.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier Parameters List................ 50
4.3 ZWF21-30-102 Shared Network Access Control Parameters List ...................... 51
4.4 ZWF21-30-118 Operator Specific Iub/Iur Transmission Parameters List ............ 55
4.5 ZWF21-30-121 Operator Specific CE Resource Parameters List ....................... 56
4.6 ZWF21-30-119 Operator Specific RNC Resource Parameters List .................... 58
5 Related Counters and Alarms ........................................................................ 59

5.1 Related Counters ............................................................................................... 59
5.1.1 ZWF21-30-100 Basic Network Sharing Support Related Counters .................... 59
5.1.2 ZWF21-30-119 Operator Specific RNC Resource Related Counters ................. 61
5.2 Related Alarms .................................................................................................. 61
6 Engineering Guide .......................................................................................... 62

6.1 Application Scenario .......................................................................................... 62
6.2 Feature Activation Procedure ............................................................................. 62
6.2.1 ZWF21-30-100 Basic Network Sharing Support ................................................. 62
6.3 Feature Validation Procedure ............................................................................ 80
6.4 Feature Deactivation Procedure......................................................................... 92

RAN Sharing

6.5 Impact on the Network ....................................................................................... 94
7 Abbreviation .................................................................................................... 95
8 Reference Document....................................................................................... 96

RAN Sharing
FIGURES
Figure 2-1 Network Architecture of MOCN .......................................................................... 9

Figure 2-2 Network Architecture of Gateway Core Network Sharing ................................... 9
Figure 2-3 Independent Carrier Network Sharing ...............................................................11
Figure 2-4 Four-Operator-Shared Iub Interface ..................................................................15
Figure 3-1 Flow of Information Transfer .............................................................................23
Figure 3-2 Structure of the Shared Network Information IE..............................................23
Figure 3-3 Structure of the SNA Access Information IE......................................................24
Figure 3-4 Scenario of Sharing 3G network and 2G network .............................................25
Figure 3-5 Example of Baseband Resources Shared in the Method of Splitting During
Congestion ...........................................................................................................................29
Figure 6-1 Parameters on the UMTS Logical Function Configuration Tab..........................63
Figure 6-2 Parameters on the Local MangedElement Plmn Information Tab .....................63
Figure 6-3 Parameters on the UMTS Logical Function Configuration Tab..........................64
Figure 6-4 Parameters on the PLMN Group Tab................................................................64
Figure 6-5 Parameters on the Used LocalPlmnGroup Tab .................................................65
Figure 6-6 Parameters on the External RNC Function Tab ................................................65
Figure 6-7 Parameters on the External UTRAN Cell Tab ...................................................66
Figure 6-8 Parameters on the External GSM Cell Tab .......................................................67
Figure 6-9 Parameters on the UMTS logical Function Configuration Tab ...........................67
Figure 6-10 Parameters on the External UTRAN Cell Tab .................................................68
Figure 6-11 Parameters on the External GSM Cell Tab .....................................................68
Figure 6-12 The parameters in LTE Handover Support Sharing Switch ...........................69
Figure 6-13 Configuring the Minimal percent of CE can be used by the PLMN Parameter .70
Figure 6-14 Configuring the CE Share Switch for Carrier Sharing Parameter ....................71
Figure 6-15 Configuring the CE Share Switch for Carrier Sharing Parameter ....................71
Figure 6-16 Parameters on the PLMN Configuration of Path Group Tab............................72
Figure 6-17 Parameters on the Service IP Configuration Tab ............................................73
Figure 6-18 Parameters on the UDP Port Configuration Tab .............................................73

RAN Sharing
Figure 6-19 Parameters on the Iub Transmission Path Tab ...............................................74

Figure 6-20 Parameter on the MGW Transmission Path Tab .............................................75
Figure 6-21 Parameters on the Iur Transmission Path Tab ................................................75
Figure 6-22 Parameters on the Iups Transmission Path Tab .............................................76
Figure 6-23 Parameters on the Flow Control of Iu Interface Tab ........................................77
Figure 6-24 Parameters on the PLMN Group Tab ..............................................................78
Figure 6-25 Parameters on the Local PLMN Group Tab ....................................................78
Figure 6-26 Parameters on the Adjacent ManagedElement PLMN Information Tab ..........79
Figure 6-27 Parameters on the Local ManagedElement PLMN Information Tab ................79
TABLES
Table 2-1 License Control List ...........................................................................................17
Table 3-1 Example of the Main PLMN-id and Other PLMN-Id Mapping List .......................19
Table 3-2 Example of 3G Cell PLMN-Id Label ...................................................................25
Table 3-3 Example of GSM Neighbor Cell PLMN-Id Label .................................................25
Table 3-4 Example of LTE Neighbor Cell PLMN-Id Label ..................................................27
Table 3-5 Features Allowed for Per Operator Activation ....................................................43
Table 3-6 Basic Priority Mapping of Operator A .................................................................44
Table 3-7 Basic Priority Mapping of Operator B .................................................................45
Table 3-8 RNC Hardware Resource Allowed to be Purchased Per Operator .....................46
Table 4-1 ZWF21-30-100 Basic Network Sharing Support Parameter List .........................48
Table 4-2 ZWF21-30-101 RAN Sharing with Dedicated Carrier Parameter List .................50
Table 5-1 ZWF21-30-100 Basic Network Sharing Support measurement type...................59
Table 5-2 Alarm List for V3 ................................................................................................61
Table 5-3 Alarm List for V4 ................................................................................................61
Table 6-1 Feature Validation Procedure - Basic Network Sharing Support ........................80
Table 6-2 Feature Validation Procedure - RAN Sharing with Dedicated Carrier .................80
Table 6-3 Feature Validation Procedure.............................................................................82
Table 6-4 Feature Validation Procedure - Operator Specific CE Resource ........................83
Table 6-5 Feature Validation Procedure - Operator Specific FM/PM/CM ...........................84

RAN Sharing
Table 6-6 Feature Validation Procedure - Operator Specific Function Control ...................86
Table 6-7 Feature Validation Procedure - Operator QoS Priority .......................................86
Table 6-8 Feature Validation Procedure - Operator Specific Iub Transmission ..................87
Table 6-9 Feature Validation Procedure - Operator Specific Iur Transmission ...................88
Table 6-10 Feature Validation Procedure - Operator Specific RNC Resource ...................89
Table 6-11 Feature Validation Procedure - Extended GSM Neighboring Cells ...................90
Table 6-12 Feature Validation Procedure - Multi PLMN Support ........................................91
Table 6-13 Feature Deactivation Procedure - Basic Network Sharing Support ..................92
Table 6-14 Feature Deactivation Procedure - Operator Specific CE Resource ..................93
Table 6-15 Feature Deactivation Procedure - Operator Specific RNC Resource................94

RAN Sharing
1 Feature Attribute
RNC Version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
Node B Version: [ZXSDR V4.13.10.20]
Attribute: [Optional]
Involved NEs:
NE Name Related or Not Special Requirement
MS/UE
BTS/Node B
BSC/RNC
iTC -
MSC
MGW
SGSN
GGSN -
HLR -
: involved, -: not involved
2 Overview
2.1 Feature Introduction
Due to the long period and high cost for establishing a 3G network, it is hard for a single
operator to establish a 3G network with complete coverage during a short period, and the
business combination between operators requires network sharing. To satisfy the above
requirements, the 3GPP develops the network sharing technology. This technology can
be used for operators to share the access network section that is the largest part in the
network investment to reduce the investment of the 3G network, enhance the layout
speed, and integrate the access network resources of different operators. Network
sharing is particularly important for operators at the early stage.

RAN Sharing
2.1.1 ZWF21-30-100 Basic Network Sharing Support
ZTE RAN devices support two 3GPP-defined UTRAN network sharing methods.
Multi-operator core network (MOCN)
Figure 2-1 Network Architecture of MOCN
CN CN CN
Operator A Operator B Operator C
Iu
RNC
Node B Node B
Radio Access Network
Operator X
In this network architecture, operators have different core network devices, and all the
core network devices are connected to the same RNC, sharing the RAN radio resources.
Gateway core network (GWCN)
Figure 2-2 Network Architecture of Gateway Core Network Sharing
CN CN CN
Operator A Operator B Operator C
Shared Shared Shared

MSC/SGSN MSC/SGSN MSC/SGSN
Iu
RNC RNC RNC
Radio Access Network

Operator X

RAN Sharing
In this network architecture, operators use the same core network devices (MGW,
MSC-server, and SGSN) as the gateway to connect independent HLR, GGSN, GMSC,
GSGW, and systems (such as a billing system) of different operators.
In the MOCN scenario, PLMNs are handled as follows:
ZTE RAN devices configure different PLMN codes for multiple operators with shared
networks. In the MOCN network architecture, the RNC differentiates subscribers of
different operators, and routes the signaling connections and services of subscribers of
different operators to the core network devices of each operator. The RNC routes
messages in accordance with PLMN information indicated by the UE or UEs access
carrier. If that is not enough for routing, the RNC randomly selects a core network node
for the UE. If the core network node rejects the users request, the RNC retries other core
network nodes until it finds the core network node that the user is authorized to access.
When the UTRAN is shared, it can also be connected to one or more operators core
networks through the Iu Flex interface.
With this feature during UTRAN network sharing, all UEs transparently access the
shared network, and enjoy the services provided by their own operators. If a UE can only
obtain the common PLMN code through the system message, it is advised to use the
NITZ function (3GPP TS22.042) in the core network to identify the logo of its own
operator. The network informs the UE of the operator PLMN ID after a successful
location update, and the corresponding logo is displayed on the UE.
2.1.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier
When multiple operators work together to establish and share the UTRAN network, they
use their own frequencies to develop their services, preventing capacities from affecting
each other because users of different operators compete for air resources.
If different operators have occupied their own frequency resources, ZTE RAN devices
support independent carriers with multiple operators in the shared UTRAN network, in
other words, sharing the UTRAN devices and resources except carriers. Carriers of
different operators can be deployed in the same NodeB, sharing devices such as
cabinets, power supply, and baseband processing boards of the NodeB. RF devices
such as PAs, feeders, and antennas can be shared or be deployed separately as

RAN Sharing
required. Carriers of different operators can also be deployed in different Node Bs. They
can be connected to the same RNC through the lub interface, sharing the RNC devices
such as cabinets, power supply, and control plane and user plane processing boards.
Figure 2-3 Independent Carrier Network Sharing
Operator one Shared RNC Shared Node B
Frequency one Frequency one MNC

Operator two one
Frequency two Frequency two MNC

two
Carriers of different operators can be identified by different PLMN codes broadcasted in

the system messages. UEs identify networks of different operators by reading the system
message from different cells, select their own PLMNs or the authorized PLMNs, and
show the logo of the operator. This process is the same as the PLMN selection process
of a non-sharing network. UEs do not need to know whether cells of different PLMNs use
the shared resources. Therefore, all UEs can access the shared network, enjoying
services provided by their own operators. The RNC routes the signaling connection and
services of a UE to the core network node of the corresponding operator based on the
UE-accessed carrier.
2.1.3 ZWF21-30-102 Shared Network Access Control
This feature enables the access control over a UE in DCH status in the shared network
and the boundary between the shared network and non-shared network based on the
subscription relationships between this UE and different operators, ensuring that the UE
always enjoys the services of the authorized network in mobility.
ZTE RAN supports access control in the Shared Network Area (SNA). Each SNA is
identified by the Shared Network Area Code (SNAC). One PLMN has only one SNAC,
one SNA may contain one or multiple Location Areas (LAs), and one LA may belong to
multiple SNAs.

RAN Sharing
The area where users can obtain services is configured by the core network. The RNC
can learn the SNACs of each LA under the RNC through the core network, and the SNAs
that each user is authorized to access. In a cross-lur handover, the SRNC can learn the
SNAs of the cells under the DRNC through the lur interface. The RNC reserves the
SNAC that each user is allowed to access, and performs filtering in the construction of
the intra-frequency, inter-frequency, and inter-system neighboring cell list. Only the cell
with the authorized SNA can be configured as the new neighboring cell. Then the cell can
be added into the cell list in the measurement control message, ensuring that the UE
performs handovers only in the authorized cells.
2.1.4 ZWF21-30-121 Operator Specific CE Resource
There are two ways to realize CE resources sharing by multi-operators: one is that
multi-operators share CE resources in the same baseband pools, and the other one is
that multi-operators occupy different baseband pools in the same BBU. ZTE RAN
devices support both ways.
ZTE RAN devices support at most six cells in one baseband pool. One baseband pool
includes one to five baseband boards, and one baseband board only belongs to one
baseband pool. The CE proportion that belongs to each operator can be configured by
the OMC when cells of multi-operators are configured in the same baseband pool or in
different baseband pools. Then the division of CE resources between operators by
proportion can be realized.
Since the method of reserving CE resources for each operator leads to reduced CE
utilization efficiency, an alternative CE allocation method is introduced by ZTE RAN in
carrier sharing mode. The given CE resource percentage for each operator will not be
implemented until CE resources reached the maximum. Before that all CE resources
could be fully utilized by all operators. If CE congestion occurs, resources used by users
of an operator who exceeds its percentage could be preempted by users of other
operators who do not run out of its percentage.
2.1.5 ZWF21-30-120 Operator Specific FM/PM/CM
The feature supports operators to independently manage the cell-level CM, PM, and FM
of the network, that is:

RAN Sharing
Independent CM
Different operators can independently configure the parameters related to the cell
that belongs to only one operator. For example, different operators own dedicated
SW (software) functions, and features differentiation can be embodied in the
cell-level configuration.
Independent PM
For those counters related to cells, performance statistics can be done based on
operators. The operator-dedicated results of performance statistics can only be
accessed by the owner PM manager, for example, operators can differentiate the
counters related to the networks KPI from different operators, independently
manage their own measurement tasks and measurement objects.
Independent FM
The fault management function can differentiate the cell-level alarms for different
operators. The alarm that corresponds to only one operator can be only accessed
by its owner, so only the owner FM manager can process the alarm.
2.1.6 ZWF21-30-116 Operator Specific Function Control
The operators of the shared RAN can separately purchase optional features and can
separately configure the parameters of some key features .
Most optional features can be switched on or off based on the PLMN ID. Also dozens of
operating parameters related to HSPA, MBMS, handovers, and so on can be configured
based on the PLMN ID to realize the differentiated service strategies for operators using
the shared device. This feature is realized through license control.
ZTE RAN devices support many optional features that could be purchased and activated
based on the network deployment strategy. Those features could be categorized into
three groups, and each feature has a different management method in the network
sharing scenario.
RNC-level functions applied to a single subscriber

RAN Sharing
Most of those functions can be configured in an RNC level based on the PLMN and
can be applied to different subscribers belonging to different operators. Still few
RNC-level optional functions only support the same configuration to all operators
and cannot be purchased separately.
Cell-level functions applied to all subscribers in each cell
All of those functions are configured in a cell level and can be applied to different
subscribers belonging to different operators in a dedicated carrier network sharing
scenario, which means that if different operators have different frequencies, those
functions can be purchased and configured separately.
Other functions applied to a physical device
All of those functions are applied to physical devices but not to any single
subscriber, for example, the transmission function. Because physical devices are
shared when the network is shared, those functions are shared as well and cannot
be purchased and configured separately.
Operator-specific function control is implemented through the license control mechanism

of ZTE RAN. Different operators can purchase different licenses in a shared RAN,
activating and operating optional features separately.
2.1.7 ZWF21-30-117 Operator QoS Priority
QoS priorities can be configured based on PLMN so that each operator can have an
individual QoS strategy.
PLMN-based QoS priority configuration is introduced. The QoS priority will be

implemented in the RRM algorithm including access control, congestion control, and
overload control. The QoS priority also will be effective in HSPA packet scheduling and
transmission resource allocation. Therefore, more system resources can be allocated to
subscribers and services of operators with priorities. For each operator, QoS priorities of
subscribers and services still can be defined separately as the description in the feature
of Differentiated Service.

RAN Sharing
2.1.8 ZWF21-30-118 Operator Specific Iub/Iur Transmission
Operators of the shared RAN can flexibly deploy transmission networks. The feature
supports transmission reservation for different operators to ensure their usage.
For the Iu and Iur interface, transmission networks can be deployed separately for
different operators and signaling flow and media data flow can be handled separately. A
ZTE RNC supports multiple signaling points and IP addresses, which could be used to
connect different UMTS nodes, such as RNCs, MSCs and SGSNs, in different
transmission networks belonging to different operators.
For the Iur and Iub interface, transport links between shared RNCs or Node Bs also can
be divided into logical transport paths, which could be occupied by different operators for
the separation and reservation of transmission resources. Logical transport paths can be
mapped to both logical and physical transport links.
Figure 2-4 Four-Operator-Shared Iub Interface
ANI+Path+PLMN1
ANI+Path1+PLMN2
RNC Node B
ANI+Path1+PLMN3
ANI+Path1+PLMN4
ANI+Path+PLMN_MIX
Transmission resources of logical transport paths among different operators can be

completely reserved to ensure the usage of each operator or dynamically shared to
improve transmission efficiency, or combination of partitioning and sharing. For shared
transmission resources, QoS differentiation can be implemented as the description in the
feature of Operator QoS Priority.

RAN Sharing
2.1.9 ZWF21-30-119 Operator Specific RNC Resource
Capacities can be logically separated in shared RNC equipment and purchased by

operators who share the RAN.
Processing resources can be logically separated in ZTE RNC, which means that the
RNC capacity of CS traffic volume and PS throughputs can be separated and reserved
for different operators.
2.1.10 ZWF21-30-122 Extended GSM Neighboring Cells
More GSM neighboring cells are possible to be configured in a RAN sharing scenario for
better supporting of inter-RAT mobility.
Operators who share a 3G radio network usually have their own GSM network as well.
So compared with UMTS neighboring cells, including intra-frequency and inter-frequency
neighboring cells, more GSM neighboring cells of different operators could exist. A ZTE
RNC supports up to 96 GSM neighboring cells.
2.1.11 ZWF21-30-200 Multi PLMN Support
A Public Land Mobile Network (PLMN) is uniquely identified by its PLMN identifier. A
PLMN-Id consists of Mobile Country Code (MCC) and Mobile Network Code (MNC).
When a physical RAN is shared by multiple operators, multiple PLMN-Ids should be
labeled to it. It is possible for a RAN to allocate and calculate system resources in
accordance with the operator. Moreover, a RAN needs to broadcast PLMN-Ids in cell
system information to help users choose a suitable network.
Before RNC supports the ZWF21-30-101 RAN Sharing with Dedicated Carrier feature,
ZWF21-30-200 Multi PLMN Support provides a non-generics solution of network
sharing with dedicated carriers. So it is not recommended to activate this feature. If RAN
Sharing with Dedicated Carrier is required, it is recommended to use ZWF21-30-101
RAN Sharing with Dedicated Carrier instead of this feature.

RAN Sharing
2.2 License Control
Table 2-1 License Control List
License Configured
Feature ID Feature Name Unit
Control Item NE
ZWF21-30-100 Basic RAN Sharing WCDMA

Support Basic RAN
RNC RNC
Sharing
Support
ZWF21-30-101 RAN Sharing with WCDMA

Dedicated Carrier Basic RAN
RNC RNC
Sharing
Support
ZWF21-30-102 Shared Networks WCDMA

Access Control Basic RAN
RNC RNC
Sharing
Support
ZWF21-30-200 Multi PLMN Support WCDMA

Basic RAN
RNC RNC
Sharing
Support
2.3 Correlation With Other Features
1. Required Features
None
2. Mutually Exclusive Features
None
3. Affected Features
None

RAN Sharing
3 Technical Description
3.1 ZWF21-30-100 Basic Network Sharing Support
3.1.1 RAN Sharing with GWCN
In Gateway Core Network (GWCN) mode, not only RNCs and Node Bs are shared by
multiple operators, but also some network elements of the core network can be shared. A
RAN is directly connected to a core network element such as Media Gateway (MGW),
MSC-server, and Serving GPRS Support Node (SGSN), which is shared by multiple
operators. So there is no need to select routing messages between a User Equipment
(UE) and the core network. The URncFunction.sharedNetMode parameter should be
set to GWCN if GWCN mode is used.
In GWCN mode, if a paging message from the core network carries the Paging Area IE,
the RNC pages terminals that are in IDLE state in the specified LAI/RAI area. If the
paging message does not carry the Paging Area IE but carries the Global CN-ID IE
instead, RNC pages terminals in IDLE state in the cells that belong to the indicated core
network. If neither Paging Area nor Global CN-ID is carried, RNC pages terminals in
IDLE state in all cells under the RNC. Paging terminals in URA_PCH state is similar to
paging terminals in IDLE state. Except that, the SRNC pages terminals in cells in the
DRNC through the Iur interface. The URA of theses DRNC cells must be the URA that
the terminals reside in.
For other Radio Access Network Application Part (RANAP) processes initiated by the
core network, such as Reset, Reset Resource and so on, which are transmitted in
connectionless signaling bearer mode, the RNC identifies the operator through the
Global CN-ID indicated in the message. If the Global CN-ID is not carried, the message
is considered to be applicable to all operators. When the RNC needs to initiate an
RANAP process in connectionless signaling bearer mode, it sends messages to each
operator with a Global RNC-ID.

RAN Sharing
3.1.1.1 User Identification
If an operator has multiple PLMN-Ids, the multi-home PLMN-Id in the IMSI of his
subscriber may exist. In this case, the RAN should indentify a users home operator with
its IMSI. The URncFunction.defPlmnInGwcnInd parameter is set to enable or disable
such identification.
Each operator should select a PLMN-Id as the main PLMN-Id from his multi-PLMN-Id. A
list of mapping between the main PLMN-Id and the other PLMN-Id for each operator
should be pre-configured. Table 3-1 shows an example. When the RAN gets an IMSI
from the core network, it extracts the home PLMN-Id and checks the table to identify the
operator that the user belongs to.
Table 3-1 Example of the Main PLMN-id and Other PLMN-Id Mapping List
Main PLMN-Id Other PLMN-Id
PLMN A1
PLMN A2
PLMN A3
PLMN A
..
..
PLMN Ax
PLMN B1
PLMN B2
PLMN B
PLMN By
PLMN C1
PLMN C2
PLMN C
PLMN Cz
At most 200 PLMN-Ids are allowed to be configured and at most four main PLMN-Ids are
supported in the mapping list.

RAN Sharing
Each main PLMN-Id is configured with the UPlmnSpecFunction.refLocalPlmnGroup

parameter. The other PLMN-Ids are configured with the parameters
PlmnGroup.AliasMCC and PlmnGroup.AliasMNC. Each
UPlmnSpecFunction.refLocalPlmnGroup can associate one PlmnGroup. The
PlmnGroup.AliasMNCBcdCodeLen parameter indicates the coding size of
PlmnGroup.AliasMNC The number of the other PLMN-Ids is indicated by
PlmnGroup.AliasPlmnNum.
3.1.2 RAN Sharing with MOCN
When the URncFunction.sharedNetMode parameter is set to Multi-Operator Core

Network (MOCN), MOCN mode is used. In this mode, the RAN is shared by multiple
operators while the core network is owned by one operator.
3.1.2.1 Message Routing
In MOCN mode, the RNC is connected to multiple operators core networks. So, the RNC
has to determine which operator a UE should be connected to. This procedure is called
routing.
When a RAN is shared in dedicated carriers, one cell only belongs to one operator. A UE
will select its home PLMN after it starts up. After an RRC is established, the UE will send
an Initial Direct Transfer message. The RNC selects the operator of the cell in which the
UE resides. In other words, the Initial UE Message will be routed to the operator to
establish a signaling and data connection to the operator for the UE.
In shared carriers, for message routing, refer to Section 3.1.2 in the ZTE UMTS RAN
Sharing with Shared Carrier Feature Guide.
3.1.2.2 Paging
In MOCN mode, if a paging message from the core network carries the Paging Area IE,
the RNC pages terminals that are in IDLE state in the specified LAI/RAI area. If the
paging message does not carry the Paging Area IE but carries the Global CN-ID IE
instead, the RNC pages terminals in IDLE state in cells that belong to the indicated core
network.

RAN Sharing
If neither Paging Area nor Global CN-ID is carried, the RNC will get the Origination
Point Code (OPC) from the SCCP data packets that carry paging messages in the
transmission network layer. Every OPC corresponds to an NE (such as an RNC, MSC, or
SGSN) connected to the RNC. The RNC finds out the core network that has sent the
paging message through the OPC. Then the RNC pages terminals that are in IDLE state
in the cells belonging to the operator of the core network.
Paging terminals in URA_PCH state is similar to paging terminals in IDLE state. Except
that, the SRNC pages terminals in cells in the DRNC through the Iur interface. The URA
of these DRNC cells must be the URA that terminals reside in.
3.1.2.3 Processing of RANAP Non RRC Connection Signaling Messages
For the Radio Access Network Application Part (RANAP) processes initialed by the core
network, such as Reset, Reset Resource and so on, which are transmitted in
connectionless signaling bearer mode, the RNC identifies the Public Land Mobile
Network (PLMN) that sends the message to the core network indicated by the Global
CN-ID carried in the message. If the Global CN-ID is not carried, the RNC finds the
operator that sends the message through an OPC. If the OPC is unavailable, the
message is considered to be applicable to all operators sharing the RAN. When the RNC
sends these RANAP processes in connectionless signaling bearer mode, it sends a
message to each PLMN with a Global RNC-ID.
3.1.3 PLMN Configuration Rule for Non-Sharing RNCs
When the URncFunction.sharedNetMode parameter is set to No Shared Network, but

the RNC and cell configure multi-PLMN, the PlmnGroup.DefaultPlmnInd parameter
indicates which PLMN is used. When the URncFunction.sharedNetMode parameter is
not set to No Shared Network, the PlmnGroup.DefaultPlmnInd parameter is invalid.
3.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier
A Public Land Mobile Network (PLMN) is uniquely identified by its PLMN identifier. A
PLMN-Id consists of Mobile Country Code (MCC) and Mobile Network Code (MNC). In
the RAN sharing scenario, a physical RAN is shared by several operators. The PLMN-Id

RAN Sharing
of each operator sharing the RAN should be configured to the RAN. Then it is possible
for the RAN to allocate system resources based on the operator and calculate
performance for an individual operator. Also it is possible for individual operators users
to select the RAN with the broadcasted operators PLMN-Id.
The PLMN of ZTE RAN is configured with the UPlmnSpecFunction.refLocalPlmnGroup

parameter. Each UPlmnSpecFunction.refLocalPlmnGroup can associate one
PlmnGroup. The PLMN-Id is configured with the PLMNGroup.MCC and
PLMNGroup.MNC parameters. The PLMNGroup.MNCBcdCodeLen parameter is used to
indicate the coding size of PLMNGroup.MNC. In the RAN sharing scenario, multiple
groups of UPlmnSpecFunction should be configured. Each UPlmnSpecFunction
represents an operators PLMN-Id. The PLMN-Id of the sharing neighbor RAN is
configured with one group of UExternalRncFunction.MCC and
UExternalRncFunction.MNC, and one or more groups of
UExternalRncFunction.SharingMCC and UExternalRncFunction.SharingMNC.
3.3 ZWF21-30-102 Shared Network Access Control
A mechanism should be applied to prohibit the subscribers that belong to other operators
from accessing the non-sharable areas in a shared network. The core network controls
the access of subscribers in IDLE state in accordance with PLMN selection and Location
Areas (LAs). For the subscribers in RRC connected mode, the RAN provides two
methods to prevent subscribers from accessing a cell. One is based on the allowed
Shared Network Area Code (SNAC), and the other is based on the PLMN-Id label of a
cell. The URncFunction.ShaNetTarCelStra parameter determines which method is used.
3.3.1 Based on SNAC
The SNAC, which is valid in one PLMN, is allocated by the operator. One SNAC includes
one or multiple LAs. The value of SNAC ranges from 0 to 65,535. An SNAC, together
with a PLMN-Id, constitutes a Shared Network Area Identifier (SNA-Id), which uniquely
identifies an area among all operators PLMNs.
The mapping between SNAC and LAC is delivered to the RNC in an RANAP procedure
by the core network. See Figure 3-1. The core network carries Shared Network

RAN Sharing
Information in the Provided Data IE of the Information Transfer message, which

indicates the mapping between SNAC and LAC in one PLMN, see Figure 3-2.
Each cell is allocated with a LAC. Thus the RNC gets the mapping between an SNAC
and a cell.
Figure 3-1 Flow of Information Transfer
CN RNC
Information Transfer
Information Transfer Confirmation
Figure 3-2 Structure of the Shared Network Information IE
Shared Network Information

IE
Operator 1
PLMN ID
LAC
SNAC

SNAC
Operator n
PLMN ID
LAC
SNAC

SNAC
When a ZTE RNC acts as the DRNC, it carries SNA Information in a Radio Link Setup
Response message (an RANAP message) to provide the SRNC with the mapping
between the DRNC neighboring cells and the SNAC. When a ZTE RNC acts as the
SRNC, if the DRNC does not support SNA Information on the Iur interface, the SNAC of
inter-RNC neighboring cells allows to be configured through the
UExternalUtranCellFDD.snacList parameter. Through the PLMN-Id and SNAC of an
inter-RNC neighboring cell, the SNA-Id is obtained. The

RAN Sharing
UExternalUtranCellFDD.snacNum parameter indicates the number of SNACs in

UExternalUtranCellFDD.snacList.
For a GSM neighbor cell, the SNAC is configured through the

UExternalGsmCell.SnacList parameter. The UExternalGsmCell.SnacNum parameter
indicates the number of SNACs in UExternalGsmCell.SnacList.
During new call establishment or SRNC relocation, the core network needs to provide the
SNA Access Information IE in the Common ID message or in the Relocation Request
message. The IE indicates the area where a subscriber is accessible. In other words,
only the area whose SNA-Id is included in the SNA Access Information IE is accessible
to IMSI, see Figure 3-3.
Figure 3-3 Structure of the SNA Access Information IE
IMSI
Allowed PLMN ID + SNAC

Allowed PLMN ID + SNAC
Because every cell is assigned with a LAC, when the RAN initiates intra-frequency,
inter-frequency, or inter-system measurements, it knows which neighbor cell is
accessible for the subscriber by checking whether the PLMN-Id + LAC are the allowed
SNA-Id. Only the neighboring cells that belong to the allowed SNA-Id are included in the
Measurement Control message. In this way, the access restriction for subscribers in
dedicated state is performed.
Access control over the SNAC-based shared network requires the cooperation of the
core network. If the core network does not support access control, IMSI-based handover
can be used. For details, refer to the ZTE RAN UMTS IMSI based Handover Feature
Guide.
3.3.2 Based on the PLMN-Id Label of the Cell
In a ZTE RAN, each 3G cell of the local RNC, each neighbor cell of other RNCs, and
each GSM neighbor cell is labeled with an operator list, which means that the users of

RAN Sharing
these operators are allowed to access the cell. Actually, the operator list is a PLMN-Id
label. Each PLMN-Id in the PLMN-Id label represents an operator. There are three
operators sharing a 3G network: Operator A and Operator C share the GSM network,
and Operator B has its own 2G network, see Figure 3-4.
Figure 3-4 Scenario of Sharing 3G network and 2G network
For 3G cell U1, the PLMN-Id label is shown in Table 3-4. It means that cell U1 is allowed
to be accessed by three operators users.
Table 3-2 Example of 3G Cell PLMN-Id Label
PLMN ID Label
PLMN A
Cell U1
PLMN B
PLMN C
Cell U1s GSM neighbors are cell G1, G2, G3, B1, B2, and B3. The PLMN-Ids of these
GSM cells are shown in Table 3-5. Cell G1, G2, and G3 are allowed to be accessed by
the users of Operator A and Operator C. And Cell B1, B2, and B3 are only allowed to be
accessed by the users of Operator B.
Table 3-3 Example of GSM Neighbor Cell PLMN-Id Label
GSM Neighbors PLMN ID Label
PLMN A
Cell G1
PLMN C
PLMN A
Cell G2
PLMN C
PLMN A
Cell G3
PLMN C
Cell B1 PLMN B

RAN Sharing
GSM Neighbors PLMN ID Label
Cell B2 PLMN B
Cell B3 PLMN B
When the RNC gets an IMSI from the core network for a user in RRC dedicated state, the
RAN identifies his home operator through the method described in 3.1.1.1 User
Identification if GWCN is used, or through the method described in 3.1.2.1 Message
Routing if MOCN is used. When it is time to trigger intra-frequency, inter-frequency, or
inter-system measurements, the RAN only provides neighbor cells labeled with the home
operators PLMN-Id in the Measurement Control message.
The PLMN-Id labels of 3G cells belonging to the neighbor RNC are configured through
the parameters UExternalUtranCellFDD.MCC, UExternalUtranCellFDD.MNC,
UExternalUtranCellFDD.SharingMCC, and UExternalUtranCellFDD.SharingMNC. The
UExternalUtranCellFDD.MncLength parameter is used to indicate the coding size of
UExternalUtranCellFDD.MNC. The UExternalUtranCellFDD.SharingMNCLength
parameter is used to indicate the coding size of UExternalUtranCellFDD.SharingMNC.
The PLMN-Id label of a GSM neighbor cell is configured through the parameters
UExternalGsmCell.MCC, UExternalGsmCell.MNC, UExternalGsmCell.SharingMCC, and
UExternalGsmCell.SharingMNC. The UExternalGsmCell.MncLength parameter is used
to indicate the coding size of UExternalGsmCell.MNC. The
UExternalGsmCell.SharingMNCLength parameter is used to indicate the coding size of
UExternalGsmCell.SharingMNC.
3.3.3 Based on the PLMN-Id Label of the LTE Neighbor Cell
In a ZTE RAN, each LTE neighbor cell is labeled with an operator list, which means that
the users of these operators are allowed to access the cell. Actually, the operator list is a
PLMN-Id label. Each PLMN-Id in the PLMN-Id label represents an operator. The
URncFunction.ShareExLteSwch parameter is provided to enable or disable this feature.
Cell U1s LTE neighbors are cells G1, G2, G3, B1, B2, and B3. The PLMN-Ids of these
LTE cells are shown in Table 3-5. Cells G1, G2 are G3 are allowed to be accessed by the
users of operators A and C. Cells B1, B2 are B3 are only allowed to be accessed by the
users of operator B.

RAN Sharing
Table 3-4 Example of LTE Neighbor Cell PLMN-Id Label
LTE Neighbors PLMN ID Label
PLMN A
Cell G1
PLMN C
PLMN A
Cell G2
PLMN C
PLMN A
Cell G3
PLMN C
Cell B1 PLMN B
Cell B2 PLMN B
Cell B3 PLMN B
When the RNC gets an IMSI from the core network for a user in RRC dedicated state, the
RAN identifies his home operator through the method described in 3.1.1.1 User
Identification if GWCN is used, or through the method described in 3.1.2.1 Message
Routing if MOCN is used. When it is time to trigger inter-system measurements, the RAN
only provides neighbor cells labeled with the home operators PLMN-Id in the
Measurement Control message.
The PLMN-Id labels of LTE neighbor cells are configured through the parameters
UExternalEUtranCellFDD.sharingMCC, UExternalEUtranCellFDD.sharingMNC,
UExternalEUtranCellFDD.sharingMNCLength, UExternalEUtranCellTDD.sharingMCC,
UExternalEUtranCellTDD.sharingMNC, and
UExternalEUtranCellTDD.sharingMNCLength. The
UExternalEUtranCellFDD.sharingMNCLength parameter is used to indicate the coding
size of UExternalEUtranCellFDD.sharingMNC. The
UExternalEUtranCellTDD.sharingMNCLength parameter is used to indicate the coding
size of UExternalEUtranCellTDD.sharingMNC.
3.4 ZWF21-30-121 Operator Specific CE Resource
3.4.1 Description of Operator Specific CE Resources
For RAN sharing, the baseband processing resources of a Node B, which is based on

RAN Sharing
the CE, are shared in the following three methods:
Pooling
The operators share all or some of the baseband processing resources. When the
RAN receives baseband processing resource requests during call admission, if
there are free baseband processing resources in the sharing part, the RAN
allocates baseband processing resources for the call. Call admission will be
rejected until all shared baseband processing resources are used up. For CE
Admission Control, refer to the ZTE UMTS Admission Control Feature Guide and
the ZTE UMTS HSUPA Introduction Guide.
Reservation
A certain percentage of baseband processing resources are reserved for an

operator. No matter how many resources other operators use, the RAN always
guarantees at least a certain percentage of the baseband processing resources for
the operator. The ratio is configured through the ULogicalIubLink.MinCEPercent
parameter for an operator of shared carrier and through the
ULogicalIubLink.CePercent parameter of dedicated carrier sharing. For CE
Admission Control, refer to 3.4.2 CE-based Admission Control in PLMN.
Splitting during congestion
The total baseband processing resources are split among operators sharing the
RAN. The percentage of each operator is configured through the
ULogicalIubLink.MinCEPercent parameter. For example, three operators share a
RAN. They are operator A, B and C. The baseband processing resources are split
as A:B:C=4:3:3, see Figure 3-6.
When baseband processing resources are not congested, all operators share these
resources, that is, the splitting ratio is ignored.
But when baseband processing resources are congested, that is, no more
baseband processing resources can be allocated for a new call, the RAN selects an
operator who currently uses a higher percentage of baseband processing
resources than his splitting percentage. The RAN only decreases the DCH bit rate

RAN Sharing
of users with the lowest QoS priority within the selected operator. The released
baseband processing resources are allocated to the new call.
Figure 3-5 Example of Baseband Resources Shared in the Method of Splitting During
Congestion
In the three methods to partition baseband processing resources, pooling and splitting
during congestion cannot be activated at the same time. The UIubLink.CEShareMode
parameter determines which one is used between the two methods. The
UIubLink.CeShareSwitch parameter enables baseband processing resources partitioned
in the two methods in sharing carriers. Pooling and reservation can be used in
combination, that is, reserving a certain percentage of resources for some operators and
sharing all left resources among all operators.

RAN Sharing
For admission control of baseband processing resources during RAN sharing, the
algorithm should be based on the number of CEs that can be used by an operator. For
details, refer to the ZTE UMTS Admission Control Feature Guide.
ZTE RAN does not support co-existence of dedicated carrier sharing and shared carrier
sharing in one Node B.
3.4.2 CE-based Admission Control in PLMN
This feature is only used when CEs are shared by multiple PLMNs in the RAN.
The RNC determines whether CE sharing is used in the Node B and which CE sharing
mode is used based on the extension IE in AUDIT RESPONSE > Local Cell Group
Information and based on the parameters configured in the OMC-R. The details are
described as follows:
If the number of the valid data groups in the extension IE in AUDIT RESPONSE > Local
Cell Group Information is 1 or 0:
If the UIubLink.CeShareSwitch parameter is set to 1: On and the

UIubLink.CEShareMode parameter is set to 0: Minimal CE Percentage should be
guaranteed for operators whether CE Resource is congested or not, CE share
mode 0 is used for Shared Carriers of the Cells in Different PLMNs.

guaranteed for operators only when CE Resource is congested, CE share mode 1
is used for Shared Carriers of the Cells in Different PLMNs.
If the UIubLink.CeShareSwitch parameter is set to 0: Off, the CE credit in the local

cell is less than the CE credit in the local cell group, and the
mode 0 is used for Independent Carriers of the Cells in Different PLMNs.
If the UIubLink.CeShareSwitch parameter is set to 0: Off, the CE credit in the local

cell is less than the CE credit in the local cell group, and the

RAN Sharing

is used for Independent Carriers of the Cells in Different PLMNs.
If the UIubLink.CeShareSwitch parameter is set to 0: Off, and the CE credit in the

local cell equals the CE credit in the local cell group, the CE is not shared.
If the number of the valid data groups in the extension IE in AUDIT RESPONSE> Local
Cell Group Information is greater than or equal to 2:

mode 0 is used for Shared Carriers of the Cells in Different PLMNs.

is used for Shared Carriers of the Cells in Different PLMNs.
If the UIubLink.CeShareSwitch parameter is set to 0: Off, the first bit of data[1] of

the extension IE in AUDIT RESPONSE > Local Cell Group Information is 1, and
the UIubLink.CEShareMode is set to 0: Minimal CE Percentage should be
mode 0 is used for Independent Carriers of the Cells in Different PLMNs.
If the UIubLink.CeShareSwitch parameter is set to 0: Off, the first bit of data[1] of

the extension IE in AUDIT RESPONSE > Local Cell Group Information is 1, and
the UIubLink.CEShareMode parameter is set to 1: Minimal CE Percentage should
be guaranteed for operators only when CE Resource is congested, CE share mode
1 is used for Independent Carriers of the Cells in Different PLMNs.
If the UIubLink.CeShareSwitch parameter is set to 0: Off, and the first bit of data[1]
of the extension IE in AUDIT RESPONSE > Local Cell Group Information is 0, the
CE is not shared.
CE share mode 1 means that the minimal CE percent should be guaranteed only
when the CE is in congestion state, and the minimal CE percent is only used when CE

RAN Sharing
congestion occurred in a local cell or local cell group (for more information about it,
refer to Section 3.4.3). The following sections describe CE share mode 0.
3.4.2.1 CE-based Admission Control in PLMN When CE Is shared in the

Independent Carriers Scene
3.4.2.1.1 Principles for Reporting the CE Credit When the Cells in Different PLMNs Share
the CE Resources
For the software version that allows different PLMNs to share the CE resources, both
Audit Response and Resource Status Indication of the Node B contain two IEs: Local
Cell Information and Local Cell Group Information. The CE Credit in Audit Response
indicates the minimum number of CE resources that should be guaranteed for the
operator (PLMN) in the cell group, and the CE Credit in Resource Status Indication
indicates the maximum number of CE resources that can be used in the cell group
3.4.2.1.2 CE-based Admission Control in PLMN
CE-based Admission Control in PLMN is performed as follows:
1. Check whether Audit Response or Resource Status Indication contains Local Cell
Group Information. If not, the admission decision is not made (the CE resources in a
certain PLMN in the cell group are not restricted).
2. Check whether Local Cell Group Information in Audit Response or Resource Status
Indication contains the UL Capacity Credit IE. If yes, the uplink uses its independent
CE resources, and the total quantity is UL Capacity Credit. If not, the uplink and
downlink share the CE resources, and the total quantity is DL Or Global Capacity
Credit. If neither UL Capacity Credit nor DL Or Global Capacity Credit is available,
the admission decision is not made (the CE resources in a certain PLMN in the cell
group are not restricted).
3. CE-based admission decision in PLMN:
i. Uplink and downlink use separate CE resources:

RAN Sharing
Decision of UL CE restriction:
ULTotalCost N*ULcos t2 ULcos t1
{ UL Capacity Credit reported in the cell group
max (Number of CEs occupied by the uplink channels, UL Capacity Credit reported by the cell)
Cumulative sum
of other PLMNs
}
If the formula is true, the subsequent admission decision is made. Otherwise,

the admission request is directly rejected.
Decision of DL CE restriction:
DLTotalCost N*DLcos t2 DLcos t1
{DL or Global Capacity Credit reported in the cell group
Max (Number of CEs occupied by the downlink channels,

Cumulative sum of other DL
or Global Capacity Credit reported by the cell)
PLMNs
}

ii. Uplink and downlink share the CE resources:
ULTotalCost+DLTotalCost+N*ULCost2+ULCost1+N*DLCost2+DLCost1<=
{DL or Global Capacity Credit reported in the cell group
Max (Number of CEs occupied by the uplink and downlink

Cumulative sum of other channels, DL or Global Capacity Credit reported by the cell)
PLMNs
}
If the formula is true, the subsequent admission decision is made. Otherwise, the
admission request is directly rejected.
Where,

RAN Sharing
ULTotalCost refers to the accumulative CE resources consumed by the dedicated

uplink in a certain PLMN in the cell group.
DLTotalCost refers to the accumulative CE resources consumed by the dedicated

downlink in a certain PLMN in the cell group.
Cost1 refers to the CE resources consumed by the reported RLS in the cell. It uses
the maximum value of Cost1 from Local cell information in RLS.
Cost2 refers to the CE resources consumed by the reported RL in the cell. It uses
the Cost2 from the local cell information of the RL.
N refers to the number of channelized codes.
Notes:
If the RL in the admission request is not the first RL in the corresponding RLS
(handover user), the resource consumption cost2 of the RL is taken into account. If
the RL in the admission request is the first RL in the corresponding RLS (new user),
the resource consumption cost1 of the RLS is also taken into account. The resource
consumption is derived from Dedicated Channels Capacity Consumption Law or
E-DCH Capacity Consumption Law in Local Cell Information. Its value is
determined by the spreading factor.
When the PLMN of the UE is changed, the CE cost in the old PLMN will be released
and CE admission control will be decided in the new PLMN. If the new PLMN is
limited by CE, the UE will be denied to access the new PLMN.
For SRNC relocation, if the PLMN of the UE is changed and CE admission is

successful in the new PLMN, but reconfiguration is not successful for any other
reasons, the CE cost will be returned to the old PLMN.

RAN Sharing
3.4.2.2 CE-based Admission Control in PLMN When CE Is Shared in the Shared

Carriers Scene
3.4.2.2.1 Principles for Reporting the CE Credit and for Configuring the Operators Available
CE Proportion When CE Resources Are Shared
When the CE is shared in the Shared Carriers Scene, the Node B cannot obtain the
PLMN information. Therefore, the total CE Credit in the resource pool is reported in Local
Cell Group.
The minimum available CE proportion is configured in the RNC for each operator
(PLMN), indicating the minimum proportion of available CE resources that the operator
can use in each Local Cell Group. The RNC supports up to four PLMNs that share one
RAN.
3.4.2.2.2 How to Obtain the Available CE in a Certain PLMN in the Cell Group
The number of available CE resources in a certain PLMN in the cell group is obtained
in accordance with the following:
If Audit Response or Resource Status Indication does not contain Local Cell Group
Information, the admission decision is not made (the CE resources in a certain
PLMN in the cell group are not restricted).
If Audit Response or Resource Status Indication contains Local Cell Group

Information, check whether Local Cell Group Information contains the UL Capacity
Credit IE.
If yes, the uplink uses its independent CE resources and the total quantity is
UL Capacity Credit. The downlink uses its own independent CE resources,
and the total quantity is DL Or Global Capacity Credit.
Total number of available uplink CE resources in a certain PLMN in the cell

group = (Total number of uplink CE resources in the cell group)

RAN Sharing
Max (Number of Ces occupied by the dedicated uplink channels, Total

Cumulative sum of number of uplink Ces * MInCePercent)
related quantities of other
PLMNs in the cell
Total number of available downlink CE resources in a certain PLMN in the cell

group = (Total number of downlink CE resources in the cell group)
Max (Number of CEs occupied by the dedicated downlink channels,

Cumulative sum of Total
number of downlink CEs * MInCePercent)
related quantities of other
PLMNs in the cell
If not, the uplink and downlink share the CE resources, and the total quantity is
DL Or Global Capacity Credit.
Total number of available downlink and uplink CE resources in a certain PLMN

in the cell group = (Total number of downlink and uplink CE resources in the
cell group)
Max (Number of CEs occupied by the dedicated uplink and

downlink channels, Total number of uplink and downlink CEs *
Cumulative sum of
related quantities of other MInCePercent)
PLMNs in the cell
Where, MinCePercent is the minimum available CE proportion configured in the RNC

(ULogicalIubLink.MinCEPercent)
3.4.2.2.3 CE-Based Admission Control in PLMN
The method for CE-based Admission Control in PLMN is described as follows:
1. Uplink and downlink use separate CE resources:
i. Decision of the UL CE restriction:
ULTotalCost+ULCost2+ULCost1<= Total number of available uplink CE

resources in the PLMN in the cell group

RAN Sharing

ii. Decision of the DL CE restriction:
DLTotalCost+DLCost2+DLCost1<= Total number of available downlink CE

resources in the PLMN in the cell group

2. Uplink and downlink share CE resources:
ULTotalCost+DLTotalCost+NxULCost2+ULCost1+NxDLCost2+DLCost1<= Total
number of available uplink and downlink CE resources in the PLMN in the cell
group
If the formula is true, the subsequent admission decision is made. Otherwise, the
admission request is directly rejected.
Where,
ULTotalCost refers to the accumulative CE resources consumed by the uplink in a

certain PLMN in the cell group.
DLTotalCost refers to the accumulative CE resources consumed by the downlink in

a certain PLMN in the NodeB group.
Cost1 refers to the CE resources consumed by the reported RLS in the cell. It uses
the maximum value of Cost1 from Local cell information in RLS.
Cost2 refers to the CE resources consumed by the reported RL in the cell. It uses
the Cost2 from the local cell information of the RL.
N refers to the number of channelized codes.
Notes:
If the currently established RL is the first link in the corresponding radio link set, the
consumed CE resources include Cost1 and Cost2, and are calculated based on the

RAN Sharing
consumption rule reported by the Node B. If the currently established RL is not the
first link (handover user) in the corresponding RLS, the consumed CE resources
only include Cost2. The resource consumption is derived from Dedicated Channels
Capacity Consumption Rule or E-DCH Capacity Consumption Rule in Local Cell
Information. Its value is determined by the spreading factor.
When the PLMN of the UE is changed, the CE cost in the old PLMN will be released
and the CE admission control will be decided in the new PLMN. If the new PLMN is
limited by CE, the UE will be denied to access the new PLMN.
For SRNC relocation, if the PLMN of the UE is changed and CE admission is

successful in the new PLMN, but reconfiguration is not successful for any other
reasons, the CE cost will be returned to the old PLMN.
3.4.3 Congestion Control When Cells in Different PLMNs Share the CE

Resource
The CE resources can be shared among multiple PLMNs after the PLMN network
resources share function is introduced.
There are two kinds of modes used for sharing CE resources among multiple PLMNs.
Which mode is used is controlled by the UIubLink.CEShareMode parameter.
For both modes, the minimum percent of CE (MinCE) used for a PLMN is configured by
the ULogicalIubLink.MinCEPercent parameter. The parameter is an array and each
element indicates the minimum percent of CE used for a PLMN.
If UIubLink.CEShareMode is set to 0: Minimal CE Percentage should be guaranteed for

operators whether CE Resource is congested or not, the minimum percent must be
guaranteed in any condition (Mode 0).
If UIubLink.CEShareMode is set to 1: Minimal CE Percentage should be guaranteed for

operators only when CE Resource is congested, the minimum percent is considered
only when congestion occurs. In congestion, if the CE percent of a PLMN is less than the
minimum percent configured for the PLMN and the access of user A who belongs to the
PLMN is rejected, the CE resources used by the users from another PLMN whose CE

RAN Sharing
percent is larger than the minimum percent configured for the PLMN shall be released to
guarantee user A to access (Mode 1).
Because the modes used for sharing CE resources are different, the congestion control
strategies are different. The differences reside on determining the range of target users
for downgrading or service pre-emption. The specific target users within the range are
selected in an ascending order, from the lowest priority to the highest priority.
They are described respectively in the following sections.
3.4.3.1 Downgrading When Cells in Different PLMNs Share the CE Resource
The strategies to select subscribers to be downgraded are described as follows.
1. Method to select the target subscribers to be downgraded in Mode 0:
If only local cell CE resource congestion occurs, the subscribers in the local cell
whose priorities are lower than the priorities of originator subscribers should be
downgraded.
If local cell group CE congestion occurs (including both local cell group CE
congestion and PLMN CE congestion in a local cell group), or only PLMN CE
congestion in a local cell group occurs, the subscribers whose PLMNs are the same
as the subscribers triggering downgrading or the subscribers who belong to the
other PLMNs whose CE percent occupied are larger than the minimum percent of
CE configured (MinCE) should be downgraded, and the RNC selects the
subscribers whose priorities are lower than the priorities of originator subscribers
out of the above subscribers to be downgraded.
When local cell CE resource congestion occurs, and meanwhile, local cell group CE
congestion occurs (including both local cell group CE congestion and PLMN CE
congestion in a local cell group) or the PLMN CE congestion in a local cell group
occurs (the local cell group CE is not congested), the subscribers in the local cell
whose PLMNs are the same as the subscribers triggering downgrading or the
subscribers in the local cell who belong to the other PLMNs whose CE percent
occupied are larger than the minimum percent of CE configured (MinCE) should be
downgraded, and the RNC selects the subscribers whose priorities are lower than
the priorities of originator subscribers out of the above subscribers to be

RAN Sharing
downgraded.
When local cell group CE congestion or PLMN CE congestion in a local cell group
together with other resource congestion occur (for example, the cause of the
congestion is DL code resource, RTWP, TCP, number of HSDPA/HUSPA users, or
HS-DSCH data throughput), the subscribers in the local cell whose PLMNs are the
same as the subscribers triggering downgrading or the subscribers in the local cell
who belong to the other PLMNs whose CE percent occupied are larger than the
minimum percent of CE configured (MinCE) should be downgraded, and the RNC
selects the subscribers whose priorities are lower than the priorities of originator
subscribers out of the above subscribers to be downgraded.
2. Method to select the target subscribers to be downgraded in Mode 1:
In Mode 1, there are two kinds of congestion: local cell CE resource congestion and local
cell group CE congestion, and they are independent each other. If local cell CE resource
congestion occurs, the subscribers in the local cell should be downgraded. If local cell
group CE congestion occurs, the subscribers in the local cell group should be
downgraded. The same strategies on selecting subscribers are for the two kinds of
congestion.
Specific strategies are as follows:
If the CE occupancy of the PLMN is less than the minimum percent of CE

configured (MinCE) for the PLMN, the subscribers who belong to the other PLMNs
whose CE percent occupied are larger than the minimum percent of CE configured
(MinCE) should be downgraded, ignoring the priority difference between the target
subscriber and the originator subscriber. If no subscribers who belong to other
PLMNs are selected, the subscriber whose PLMNs are the same as the subscriber
triggering downgrading and whose priorities are lower than the originator subscriber
should be downgraded.
If the CE occupancy of the PLMN is larger than or equal to the minimum percent of
CE occupancy (MinCE) configured for the PLMN, the subscribers whose PLMNs
are the same as the subscriber triggering downgrading or the subscribers who
belong to the other PLMNs whose CE percent occupied are larger than the
minimum percent of CE configured (MinCE) should be downgraded, and the RNC
selects the subscribers whose priorities are lower than the priorities of originator

RAN Sharing
subscribers out of the above subscribers to be downgraded.
3.4.3.2 Service Pre-emption When Cells in Different PLMNs Sharing the CE

Resource
When Service Pre-emption is triggered, the CE resources needed for the service which
triggers congestion need to be considered, which is indicated by CEneed.
The strategies to select subscribers for service pre-emption are described as follows.
1. To select the target subscribers for service pre-emption in Mode 0:
If only local cell CE resource congestion occurs, the subscribers in the local cell
whose priorities are lower than the priorities of originator subscribers should be
selected for pre-emption.
If local cell group CE congestion occurs (both local cell group CE congestion and
PLMN CE congestion in a local cell group occur), or only PLMN CE congestion in a
local cell group occurs, the subscribers whose PLMNs are the same as the
subscriber triggering pre-emption or the subscribers who belong to the other
PLMNs whose CE percent occupied are larger than (MinCE+CEneed) should be
selected for pre-emption, and the RNC selects the subscribers whose priorities are
lower than the priorities of originator subscribers out of the above subscribers for
pre-emption. Where, MinCE is the minimum percent of CE configured.
If local cell CE resource congestion occurs, and meanwhile, local cell group CE
congestion occurs (including both local cell group CE congestion and PLMN CE
congestion in a local cell group) or PLMN CE congestion in a local cell group occurs
(the local cell group CE is not congested), the subscribers in the local cell whose
PLMNs are the same as the subscriber triggering pre-emption or the subscribers in
the local cell who belong to the other PLMNs whose CE percent occupied are larger
than (MinCE+CEneed) should be selected for pre-emption, and the RNC selects
the subscribers whose priorities are lower than the priorities of originator
subscribers out of the above subscribers for preemption. Where, MinCE is the
minimum percent of CE configured.
If local cell group CE congestion or local cell group self-PLMN CE congestion

together with other resource congestion occurs (for example, DL code resource
congestion, RTWP congestion, TCP congestion, HSDPA/HUSPA user congestion,

RAN Sharing
HS-DSCH data throughput congestion), the subscribers in the local cell whose
PLMN is the same as the subscribers triggering pre-emption or the subscribers in
the local cell who belong to the other PLMNs whose CE percent occupied are larger
than (MinCE+CEneed) should be selected for pre-emption, and the RNC selects
the subscribers whose priorities are lower than the priorities of originator
subscribers out of the above subscribers for pre-emption. Where, MinCE is the
minimum percent of CE configured.
2. To select the target subscribers for service pre-emption in Mode 1:
In Mode 1, there are two kinds of congestion: local cell CE resource congestion and
local cell group CE congestion, and they are independent each other. If local cell
CE resource congestion occurs, the subscribers in the local cell should be selected
for pre-emption. If local cell group CE congestion occurs, the subscribers in the
local cell group should be selected for pre-emption. The same strategies on
selecting subscribers are for the two kinds of congestion.
Specific strategies are as follows:
If the CE occupancy of the current PLMN is less than the minimum percent of
CE configured (MinCE), the subscribers who belong to the other PLMNs whose CE
percent occupied are larger than (MinCE+CEneed) should be selected for
pre-emption, ignoring the priority difference between the target subscribers and the
originator subscribers. If no subscribers who belong to other PLMNs are selected,
the subscribers whose PLMN is the same as the subscriber triggering pre-emption
and whose priorities are lower than the originator subscriber should be selected for
If the CE occupancy of the current PLMN is larger than or equal to the minimum
percent of CE configured (MinCE), the subscribers whose PLMNs are the same as
the subscriber triggering pre-emption or the subscribers who belong to the other
PLMNs whose CE percent occupied are larger than (MinCE+CEneed) should be
selected for pre-emption, and the RNC selects the subscribers whose priorities are
lower than the priorities of originator subscribers out of the above subscribers for

RAN Sharing
3.5 ZWF21-30-116 Operator Specific Function Control
During RAN sharing, some optional features are allowed to be purchased by operators.
The following table lists the available features. These features can be purchased
individually both in dedicated carrier sharing and in shared carrier sharing. Take
ZWF21-02-020 WB-AMR Speech Support for example, operator A and B share a ZTE
RAN physical device, and they can determine whether to purchase the feature
respectively. If operator A purchased the feature, while operator B did not, the RNC then
allows operator As subscribers to establish a WB-AMR voice call, but does not allow
operator Bs subscribers to setup a WB-AMR voice call.
Table 3-5 Features Allowed for Per Operator Activation
PLMN based
Feature ID Feature Name Active/Deactiv
e
ZWF21-02-020 WB-AMR Speech Support Yes
ZWF21-02-021 PS Conversational RAB for VoIP Yes
ZWF21-02-022 PS Signaling RAB for IMS Yes
ZWF21-03-022 IMSI based Handover Yes
ZWF21-04-005 AMR Rate Controlling Yes
ZWF21-05-020 RAB Negotiation/ Renegotiation Yes
ZWF21-05-022 Service-Based Handover Yes
ZWF21-05-024 Video Call Fallback to Speech Yes
ZWF21-10-001 Cell ID & RTT Positioning Yes
ZWF21-10-002 AGPS Yes
ZWF21-30-026 Neighboring Cell Monitoring Yes
HSDPA HS-DPCCH ACK/NACK

ZWF23-01-042 Yes
enhancement
ZWF23-05-003 HSDPA Nominal Bit Rate for I/B Service Yes
ZWF24-01-011 MBMS PTP over HSDPA Yes
ZWF25-02-011 SRB over HSUPA Yes
ZWF25-05-002 HSUPA Nominal Bit Rate for I/B Service Yes
ZWF21-03-023 PS handover with GSM Yes

RAN Sharing
PLMN based
Feature ID Feature Name Active/Deactiv
e
ZWF21-03-024 DTM Handover with GSM Yes
ZWF21-03-025 NACC Yes
ZWF21-03-026 Target cell Load based inter-RAT HO Yes
ZWF26-02-005 CS over HSPA Yes
ZWF21-01-025 Ciphering Algorithm UEA2 Yes
ZWF21-01-026 Integrity Protection Algorithm UIA2 Yes
ZWF21-03-110 Handover with LTE Yes
ZWF21-03-120 SR-VCC Yes
ZWF27-01-100 Application Awared Flow Control Yes
ZWF27-03-002 Application Awared DRBC Enhancement Yes
ZWF21-05-026 Voice service Optimization for Multi-RAB Yes
ZWF27-02-002 User Dedicated Frequency Priority Yes
ZWF25-01-033 Adaptive 2/10ms HSUPA TTI Yes
ZWF21-30-119 Operator Specific RNC Resource Yes
3.6 ZWF21-30-117 Operator QoS Priority
Normally, each operator has its own QoS policy. In RAN sharing, ZTE RAN allows
different QoS mapping priorities to operators, to differentiate operators QoS policies. For
details about the QoS mapping priority, refer to the ZTE UMTS QoS Feature Guide.
Namely, the basic priority, scheduling priority, and the application priority are configured
per operator. See an example in Table 3-6 and 3-7. Streaming service of ARPSeg=1 and
background service of ARPSeg=3 between operator A and operator B have different
basic priorities.
Table 3-6 Basic Priority Mapping of Operator A
PLMN ID (Operator A)
Traffic Class
I (THP)
ARPSeg SIP C_Voice C_Video S B
15 610 1115

RAN Sharing
1 15 14 14 11 9 8 7 7
2 15 13 13 10 6 5 4 4
3 15 12 12 10 3 2 1 0
Table 3-7 Basic Priority Mapping of Operator B
PLMN ID (Operator B)
Traffic Class
I (THP)
ARPSeg SIP C_Voice C_Video S B
15 610 1115
1 15 14 14 10 9 8 7 7
2 15 13 13 10 6 5 4 4
3 15 12 12 10 3 2 1 1
The ZTE RAN RRM policy is based on the mapped priority. Users having a higher priority
can preferentially use resources. Users having a lower priority might be forced to release
all or part of occupied resources during congestion. It means that the mapped priorities
of different operators are considered together. Take operator A and operator B mentioned
above for example, because the uplink interference and downlink admission threshold
differentiate basic priority configurations, the admission threshold of operator As
ARPSeg=1 streaming services is the one based on priority 11, while the admission
threshold of operator B is the one based on priority 10.
3.7 ZWF21-30-118 Operator Specific Iub/Iur

Transmission
The ZTE RAN supports two methods to differentiate transmission resources for network
sharing.
Dynamic sharing
Transmission bandwidths are shared among operators. Unused transmission

bandwidths are allocated to a new request of a call, until all transmission
bandwidths are occupied.
Static reservation

RAN Sharing
A certain amount of transmission bandwidth is reserved for an operator, which is

the minimum bandwidth that can be used by the operator.
The above two methods can be used independently, as well as in combination.
For the configuration and admission of each operators transmission bandwidth after
network sharing is introduced, refer to the ZTE UMTS RAN Transmission Overview.
In RAN sharing scenarios, service IP addresses can also be split for the traffic of different
operators (ServiceIp.refLocalPlmnGroup). The default configuration for a service IP is
served for all operators (ServiceIp.IsSupportAllPlmn).
3.8 ZWF21-30-119 Operator Specific RNC Resource
In RAN sharing, operators can purchase RNC hardware processing resources, including
CS traffic capacity and PS data throughput, in accordance with their individual
requirements. The purchase of CS traffic capacity and PS data throughput is based on
license. Operators can buy different quantity of capacity licenses. The following table
shows a list of RNC hardware recourses that can be individually purchased by operators.
Table 3-8 RNC Hardware Resource Allowed to be Purchased Per Operator
RNC Hardware Resource Step Length Unit

CS service capacity 1 Erlang
PS service capacity 1 Mbps
The CS traffic capacity or PS data throughput used by a user depends on the operator
who provides service for the user.
If the IU PS capacity and IU CS capacity are purchased independently

(UIuFlowCtrl.IuFlowCtrlType is set as 0) in a commercial contract, the operator should
configure the lower threshold of the CS flow (UIuFlowCtrl.IuCSLowThres) and that of PS
flow (UIuFlowCtrl.IuPSLowThres) in accordance with the contract. At the same time, the
operator should configure the upper threshold of the CS flow
(UIuFlowCtrl.IuCSHighThres) to IuCSLowThres*120% and configure the upper threshold
of the PS flow (UIuFlowCtrl.IuPSHighThres) to min(IuPSLowThres*120%,
IuPSLowThres+100Mbps). When the number of CS users on the IU Interface exceeds

RAN Sharing
the lower threshold of the CS flow (UIuFlowCtrl.IuCSLowThres), an alarm will be raised.

When the number exceeds the upper threshold of the CS flow
(UIuFlowCtrl.IuCSHighThres), the subsequent CS calls may be rejected on a certain
proportion until the number of CS users is lower than the lower threshold of the CS flow.
When the PS traffic on the IU interface exceeds the lower threshold of the PS flow
(UIuFlowCtrl.IuPSLowThres), an alarm will be raised. When the number exceeds the
upper threshold of the PS flow (UIuFlowCtrl.IuPSHighThres), the subsequent PS calls
may be rejected on a certain proportion until the PS traffic capacity is lower than the
lower threshold of the PS flow.
If the IU PS capacity and IU CS capacity are purchased with a mixed type

(UIuFlowCtrl.IuFlowCtrlType is set to 1) in a commercial contract, the operator should
configure the lower threshold of IU PS and CS traffic mix control
(UIuFlowCtrl.IuMixLowThres) in accordance with the contract and configure the upper
threshold of IU PS and CS traffic mix control (UIuFlowCtrl.IuMixHighThres) to
min(IuMixLowThres*120%, IuMixLowThres+100Mbps). When the IU CS and PS mix
traffic capacity exceeds the lower threshold (UIuFlowCtrl.IuMixLowThres), an alarm will
be raised. When the traffic capacity exceeds the upper threshold
(UIuFlowCtrl.IuMixHighThres), the subsequent CS and PS calls may be rejected on a
certain proportion until the mixed traffic capacity is lower than the lower threshold of PS
and CS traffic mix control.
3.9 ZWF21-30-122 Extended GSM Neighboring Cells
Normally, an operator sharing a 3G RAN owns a GSM network by itself. To keep service
continuity when a user moves from the 3G network to the operators GSM network, all
the operators GSM neighboring cells should be configured. ZTE RAN allows at most 96
GSM neighboring cells to be configured, and each neighboring cell has an index
(AdjPhyGsmCId). Limited by 3GPP specifications, a maximum of 32 GSM neighboring
cells can be contained in system information. If a cell is configured with more than 32
GSM neighboring cells in IDLE state and non-dedicated state, ZTE RAN selects 32 cells
having the highest priority and puts them in system information to broadcast. In
connection mode, ZTE RAN selects 32 GSM neighboring cells based on the description
in 3.3 ZWF21-30-102 Shared Network Access Control, and sends them to UE for

RAN Sharing
measurement.
3.10 ZWF21-30-200 Multi PLMN Support
If Multi-PLMN mode is used, the URncFunction.sharedNetMode parameter should be

set to Multi Plmn, and one 3G cell belongs to only one PLMN. For details, refer to 3.2
ZWF21-30-101 RAN Sharing with Dedicated Carrier.
4 Parameters
4.1 ZWF21-30-100 Basic Network Sharing Support

Parameter List
Table 4-1 ZWF21-30-100 Basic Network Sharing Support Parameter List
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
This parameter indicates

the network sharing mode.
There are three network
sharing modes: Gateway
Core Network (GWCN), 0:GWCN
Multi-Operator Core
1:MOCN 0xFF:
Network (MOCN), and
URncFunct 2: Multi No Networ
Shared Multi-PLMN. Both radio
ion.shared Plmn N/A Shared kplanni
Network Mode access networks and core
NetMode 0xFF: No Networ ng
networks are shared in
Shared k
GWCN mode. Only radio
Network
access networks are
shared in MOCN mode.
MOCN and GWCN belong
to shared carrier network
sharing, and Multi-PLMN

RAN Sharing
Recom
Name Range Value d
Value
belongs to dedicated
carrier network sharing.
UPlmnSpe
Networ
cFunction.r Used Local This parameter indicates
N/A N/A N/A kplanni
efLocalPlm PLMN Group the Used LocalPlmnGroup
ng
nGroup
User-Defined
The RNC may select a
PLMN
URncFunct PLMN for a UE based on
Selection In Networ
ion.defPlm its IMSI. This parameter 0: False
case of N/A N/A kplanni
nInGwcnIn indicates whether the RNC 1: True
GWCN ng
d supports user-defined
support
PLMN selection.
Indicator
PlmnGroup Networ
Number of This parameter indicates
.AliasPlmn 0-50 N/A 0 kplanni
Alias PLMN the number of Alias PLMN
Num ng
Networ
PlmnGroup Alias Mobile
Alias Mobile Country Code 0..999 N/A N/A kplanni
.AliasMCC Country Code
ng
PlmnGroup
Alias MNC Networ
.AliasMNC Alias MNC BCD Code
BCD Code 2,3 N/A 2 kplanni
BcdCodeL Length
Length ng
en
Networ
PlmnGroup Alias Mobile
Alias Mobile Network Code N/A N/A N/A kplanni
.AliasMNC Network Code
ng
PlmnGroup Networ
Default PLMN
.DefaultPl Default PLMN Indicator 0/1 N/A 0 kplanni
Indicator
mnInd ng

RAN Sharing
4.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier

Parameters List
Table 4-2 ZWF21-30-101 RAN Sharing with Dedicated Carrier Parameter List
Recom
Name Range Value d
Value
UPlmnSpe
Used This parameter indicates
cFunction.r
LocalPlmnGro the PLMN index of the 0..20 N/A N/A N/A
efLocalPlm
up Network Element (NE).
nGroup
MCC uniquely identifies

the country that the UE
UExternal
Mobile users (or system) belong
RncFunctio 0..999 N/A N/A N/A
Country Code to. MCC is allocated
n.mcc
uniformly and
internationally.
UExternal MNC identifies a specific

Mobile
RncFunctio PLMN inside one country 0..999 N/A N/A N/A
Network Code
n.mnc (decided by MCC).
UExternal
Sharing This parameter indicates
RncFunctio
Mobile the sharing MNC of the 0..999 N/A N/A N/A
n.sharingM
Network Code neighboring RNC.
NC
UExternal
RncFunctio
Mobile the sharing MCC of the 0..999 N/A N/A N/A
n.sharingM
Country Code neighboring RNC.
CC

RAN Sharing
4.3 ZWF21-30-102 Shared Network Access Control

Parameters List
Table 4-2 ZWF21-30-102 Shared Network Access Control Parameter List
Recom
Name Range Value d
Value

the Shared Network Area
UExternal Shared
Code (SNAC) that the
GsmCell.s Network Area 0..65535 N/A N/A N/A
neighboring cell belongs
nacList Code
to. One cell can belong to
up to four SNACs.
0..
UExternal Shared MAX_NU
the number of SNACs that
GsmCell.s Network Area M_SNAC N/A N/A N/A
the neighboring cell
nacNum Code Number _PER_G
belongs to.
SMCEL

UExternal the Shared Network Area
Shared
UtranCellF Code (SNAC) that the
Network Area 0..65535 N/A N/A N/A
DD.snacLi neighboring cell belongs
Code
st to. One cell can belong to
up to four SNACs.
0..
UExternal This parameter indicates
Shared MAX_NU
UtranCellF the number of SNACs that
Network Area M_SNAC N/A N/A N/A
DD. the neighboring cell
Code Number _PER_G
snacNum belongs to.
SMCEL
Target Cell 0:Judgme

Judgment This parameter indicates nt Based
URncFunct
Strategy for the determination policy for on
ion.
Access/Hand access/handover to the Authoriza N/A 0 N/A
ShaNetTar
over Algorithm target cell in a shared tion
CelStra
in Shared network. Informati
Network on

RAN Sharing
Recom
Name Range Value d
Value
1:Judgme
nt Based
on
Selected
PLMN

Mobile
GsmCell. PLMN inside one country 0..999 N/A N/A N/A
Network Code
mnc (decided by MCC).

UExternal
MNC BCD the code length of the
GsmCell.m 2..3 N/A 2 N/A
Code Length MNC BCD of the
ncLength
neighboring GSM cell.
MCC uniquely identifies

the country that the UE
UExternal
Mobile users (or system) belong
GsmCell.m 0..999 N/A N/A N/A
Country Code to. MCC is allocated
cc
uniformly and
internationally.
UExternal Sharing This parameter indicates

GsmCell.s Mobile the sharing MNC of the 0..999 N/A N/A N/A
haringMNC Network Code neighboring RNC.

the code length of the
UExternal MNC BCD of the
GsmCell.s sharing MNC neighboring GSM cell. The
2..3 N/A 2 N/A
haringMNC Length MNC contains two or three
Length digits (09), and this
parameter indicates the
number of digits.

GsmCell.s Mobile the sharing MCC of the 0..999 N/A N/A N/A
haringMCC Country Code neighboring RNC.

Mobile
UtranCellF PLMN inside one country 0..999 N/A N/A N/A
Network Code
DD.mnc (decided by MCC).

RAN Sharing
Recom
Name Range Value d
Value
UExternal This parameter indicates

UtranCellF MNC BCD the code length of the
2..3 N/A 2 N/A
DD.mncLe Code Length MNC BCD of the
ngth neighboring UMTS cell.

UtranCellF Mobile the sharing MCC of the 0..999 N/A N/A N/A
DD.mcc Country Code neighboring RNC.
UExternal
UtranCellF
Mobile the sharing MNC of the 0..999 N/A N/A N/A
DD.sharing
Network Code neighboring RNC.
MNC

UExternal
MNC BCD of the
UtranCellF
sharing MNC neighboring UMTS cell.
DD.sharing 2..3 N/A 2 N/A
Length The MNC contains two or
MNCLengt
three digits (09), and this
h
number of digits.
UExternal
UtranCellF
Mobile the sharing MCC of the 0..999 N/A N/A N/A
DD.sharing
Country Code neighboring RNC.
MCC

UExternalE the code of the country
Sharing
UtranCellF where a cell is located. It 0..999
Mobile N/A N/A N/A
DD.sharing uniquely identifies the
Country Code
MCC country that a mobile user
or a system belongs to.
UExternalE
Sharing This parameter identifies
UtranCellF 0..999
Mobile the MNC for the operator N/A N/A N/A
DD.sharing
Network Code of the shared cell.
MNC
UExternalE sharing MNC This parameter indicates?

2, 3 N/A 2 N/A
UtranCellF Length the code length of the

RAN Sharing
Recom
Name Range Value d
Value
DD.sharing MNC BCD of the
MNCLengt neighboring UTRAN cell.
h The MNC contains two or
number of digits.

UExternalE the code of the country
Sharing
UtranCellT where a cell is located. It 0..999
Mobile N/A N/A N/A
DD.sharing uniquely identifies the
Country Code
MCC country that a mobile user
or a system belongs to.
UExternalE
Sharing This parameter identifies
UtranCellT 0..999
Mobile the MNC for the operator N/A N/A N/A
DD.sharing
Network Code of the shared cell.
MNC
This parameter indicates?

UExternalE
MNC BCD of the
UtranCellT
sharing MNC neighboring UTRAN cell.
DD.sharing 2, 3 N/A 2 N/A
Length The MNC contains two or
MNCLengt
h
number of digits.
The parameter indicates

LTE Handover whether SRNC support the
URncFunct
Support determination policy based 0: Off 0: Off
ion.ShareE N/A N/A
Sharing on selected PLMN for 1: On
xLteSwch
Switch handover to LTE in a
shared network.

RAN Sharing
4.4 ZWF21-30-118 Operator Specific Iub/Iur

Transmission Parameters List
Table 4-2 ZWF21-30-118 Operator Specific Iub/Iur Transmission Parameter List
Recom
Name Range Value d
Value

the operator list supported
by this service IP address.
It applies to radio
resources shared by
ServiceIp.r multiple operators. This
Used Local
efLocalPlm service IP address can be N/A N/A N/A N/A
Plmn Group
nGroup used for service packets
addressing of the operator
in the list. If all the
operators are supported,
this parameter is not
configured.

whether the service IP
address supports all the
operators. It applies to
Whether IP
ServiceIp.I radio resources shared by
address 0: No
sSupportAl multiple operators. If this N/A 1: Yes N/A
support all 1: Yes
lPlmn parameter is set to support
PLMNs
all the operators, the
service IP address can be
used for packet addressing
of all the operators.

RAN Sharing
4.5 ZWF21-30-121 Operator Specific CE Resource

Parameters List
Table 4-2 ZWF21-30-121 Operator Specific CE Resource Parameter List
Recom
Name Range Value d
Value

the minimum percentage
of CE that can be used by
the PLMN for RAN Sharing
while carrier sharing.
When the CeShareSwitch
parameter is set to 1 and
CEShareMode to 0, the
minimum percentage of
CE can only be used by
the corresponding operator
(PLMN) and cannot be
occupied by other
Minimal
ULogicalIu operators at any time. (0100)
percent of CE
bLink.MinC When the CeShareSwitch %, step % N/A N/A
can be used
EPercent parameter is set to 1 and by 0.1%
by the PLMN
CEShareMode to 1, the
parameter is invalid if CE
resources are not
congested. In the case of
CE congestion, the
minimum percentage of
CE can only be used by
the operator (PLMN) and
cannot be occupied by
other operators. When the
UIubLink.CeShareSwitch
parameter is set to 0, the
parameter is invalid.
UIubLink.C CE Share This parameter indicates 0: Off N/A 0 0

RAN Sharing
Recom
Name Range Value d
Value
eShareSwi Switch for the CE shared switch for 1: On
tch Carrier carrier sharing. If this
Sharing parameter is set to 1: On,
every PLMN can reserve
minimal CE percentage in
the CE shared scenario for
carrier sharing. If this
parameter is set to 0: Off,
every PLMN cannot
reserve any CE in the CE
shared scenario for carrier
sharing, and the CE will be
used based on the
First-Arrive-First-Get rule.
This parameter indicates 0:

the shared mode of CE Minimal
resources for multiple CE
operators. If this parameter Percenta
is set to 0, a minimal CE ge should
percentage should be be
guaranteed for the guarante
operators no matter ed for
whether CE resources are operators
Share Mode congested or not, which whether
UIubLink.C of CE can ensure that a minimal CE
EShareMo Resource for CE percentage for an Resource N/A N/A N/A
de Multi-Operator operator cannot be used is
s by other operators at any congeste
time. If this parameter is d or not
set to 1, a minimal CE 1:
percentage should be Minimal
guaranteed for the CE
operator only when CE Percenta
resources are congested, ge should
which can ensure that a be
minimal CE percentage guarante
can be used by each ed for

RAN Sharing
Recom
Name Range Value d
Value
operator in the case of CE operators
congestion and the CE only
utilization rate can be when CE
improved when CE Resource
resources are not is
congested. congeste
d
4.6 ZWF21-30-119 Operator Specific RNC Resource

Parameters List
Table 4-2 ZWF21-30-119 Operator Specific RNC Resource Parameter List
Recom
Name Range Value d
Value
UIuFlowCtr
IU traffic flow
l.IuFlowCtrl IU traffic flow control type 0,1 N/A 0 N/A
control type
Type
UIuFlowCtr IU PS low 0..10000

l.IuPSLow control IU PS low control threshold 0000,429 Kbps 50000 N/A
Thres threshold 4967295
UIuFlowCtr IU PS high 0..20000

IU PS high control
l.IuPSHigh control 0000,429 Kbps 60000 N/A
threshold
UIuFlowCtr IU CS low 0..10000

IU CS low control
l.IuCSLow control 00,42949 Erl 500 N/A
threshold
UIuFlowCtr IU CS High IU CS High control 0..20000

Erl 600 N/A
l.IuCSHigh control threshold 00,42949

RAN Sharing
Recom
Name Range Value d
Value
IU PS and CS
UIuFlowCtr 0..10000
traffic mix IU PS and CS traffic mix
l.IuMixLow 0000,429 Kbps 50000 N/A
control low control low threshold
Thres 4967295
threshold
IU PS and CS
UIuFlowCtr 0..20000
traffic mix IU PS and CS traffic mix
l.IuMixHigh 0000,429 Kbps 60000 N/A
control High control High threshold
Thres 4967295
threshold
5 Related Counters and Alarms
5.1 Related Counters
5.1.1 ZWF21-30-100 Basic Network Sharing Support Related Counters
Because the RAN network sharing related counter is too many, the FG support list only
to distinguish the PLMN statistical measurement type. For details, please refer to the
ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Performance Counter Reference or
the ZXUR 9000 UMTS (V3.13.10.15) Radio Network Controller Performance Counter Reference.
Table 5-1 ZWF21-30-100 Basic Network Sharing Support measurement type
Measurement Type ID Measurement Type Name
31001 Statistics of cell traffic
31002 Statistics of cell RLC traffic
31003 Statistics of cell user number
31004 Statistics of cell RAB holding time
31192 Statistics of cell RAB transmission time
31377 Statistics of logic cell resource

RAN Sharing
31085 Statistics of NodeB logic cell group CE
31330 Statistics of logic RNC Iu traffic
31336 Statistics of logic cell RAB setup request
31337 Statistics of logic cell RAB setup success
31338 Statistics of logic cell RAB setup failure
31339 Statistics of logic cell HSPA service setup
31340 Statistics of logic cell RB setup attempt
31341 Statistics of logic cell RB setup failure
31342 Statistics of logic cell RB setup release
31343 Statistics of logic cell RAB setup queue time
31344 Statistics of logic cell RAB setup time
31345 Statistics of logic cell call drop by traffic for CS
31346 Statistics of logic cell call drop by traffic for PS
31347 Statistics of logic cell call drop by traffic for HS
31348 Statistics of logic cell call drop by fail code for CS
31349 Statistics of logic cell call drop by fail code for PS
31366 Statistics of logic cell call drop by RRC_STATE
31350 Statistics of logic cell soft handover
31351 Statistics of logic cell hard handover
31352 Statistics of logic cell relocation
31353 Statistics of logic cell inter-RAT handover
31354 Statistics of logic cell HSPA serving cell change
31355 Statistics of logic cell DRBC
31356 Statistics of logic cell channel switch
31357 Statistics of logic cell access control
31358 Statistics of logic cell load control
31359 Statistics of logic cell congest control
31360 Statistics of logic cell RAB pre-empty
31361 Statistics of logic cell transmission quality
31362 Statistics of logic cell DPI traffic
31380 Statistics of logic cell VIP user
31407 Statistics of cell append user number

RAN Sharing
5.1.2 ZWF21-30-119 Operator Specific RNC Resource Related Counters
Table 5-1 ZWF21-30-119 Operator Specific RNC Resource Related Counters
Counter ID Counter Name
Peak payload traffic rate of short period of logic IU

C313300001
interface in bidirectional link direction
Total seconds of logic IU payload traffic rate exceed the

C313300002
threshold of license control
Peak payload traffic rate of short period of logic IU PS in

C313300003
bidirectional link direction
Peak payload traffic rate of short period of logic IU CS in

C313300004
bidirectional link direction
C313300005 Peak instant number of logic IU CS in short period
Total seconds of logic IU PS payload traffic rate exceed

C313300006
the threshold of license control
Total seconds of logic IU CS traffic rate exceed the

C313300007
threshold of license control
5.2 Related Alarms
Table 5-2 Alarm List for V3
Alarm Code Alarm Name

198105022 IU PS traffic over load alarm
198105023 IU CS traffic over load alarm
198105024 IU traffic over load alarm
Table 5-3 Alarm List for V4
Alarm Code Alarm Name
199105022 IU PS traffic over load alarm
199105023 IU CS traffic over load alarm
199105024 IU traffic over load alarm

RAN Sharing
6 Engineering Guide
6.1 Application Scenario
The sharing network technology provides services to multiple operators at the same time
through a physical network. This technology can be used for operators to share the
access network, which is the largest part in network investment to reduce 3G network
investment, enhance the layout speed, and to integrate the access network resources of
different operators, which is particularly important for operators at the early stage. Typical
application scenarios are as follows:
In Gateway Core Network (GWCN) mode, not only RNCs and/or Node Bs are
shared by multiple operators, but also some network elements of the core network
are shared.
In MOCN mode, RNCs and/or Node Bs are shared by multiple operators, whereas
the core networks are not shared.
GWCN mode and MOCN mode determine the CN RANAP message routing mode.
But no matter which mode is used, RNC resources such as CE, transport resources,
carrier frequency, and QoS are shared in accordance with the requirements of
operators.
6.2 Feature Activation Procedure
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
In the configuration resource tree, select Modify Area > Managed Element, and
double-click UMTS logical Function Configuration. Set Shared Network Mode. See
Figure 6-1.

RAN Sharing
Figure 6-1 Parameters on the UMTS Logical Function Configuration Tab
In the configuration resource tree, select Modify Area > Managed Element > UMTS
logical Function Configuration > Link Configuration, and double-click Local
ManagedElement Plmn Information. Set Used LocalPlmnGroup. See Figure 6-2.
Figure 6-2 Parameters on the Local MangedElement Plmn Information Tab
double-click UMTS logical Function Configuration. Set User-Defined PLMN
Selection In case of GWCN support Indicator. See Figure 6-3.

RAN Sharing
Figure 6-3 Parameters on the UMTS Logical Function Configuration Tab
In the configuration resource tree, select Modify Area > Managed Element > Plmn
Group Configuration, and double-click PLMN Group. Set Number of Alias PLMN,
Alias Mobile Country Code, Alias MNC BCD Code Length, Alias Mobile Network
Code, and Default PLMN Indicator. See Figure 6-4.
Figure 6-4 Parameters on the PLMN Group Tab
Logical Function Configuration > Link Configuration, and double-click Local

RAN Sharing
Figure 6-5 Parameters on the Used LocalPlmnGroup Tab
Logical Function Configuration > External Resource Configuration, and
double-click External RNC Function. Set the related parameters. See Figure 6-6.
Figure 6-6 Parameters on the External RNC Function Tab
Logical Function Configuration > External Resource Configuration > External RNC

RAN Sharing
Function, and double-click External UTRAN Cell. Set the related parameters. See
Figure 6-7.
Figure 6-7 Parameters on the External UTRAN Cell Tab
double-click External GSM Cell. Set the related parameters. See Figure 6-8.

RAN Sharing
Figure 6-8 Parameters on the External GSM Cell Tab
double-click UMTS logical Function Configuration. Set Target Cell Judgment
Strategy for Access/Handover Algorithm in Shared Network. See Figure 6-9.
Figure 6-9 Parameters on the UMTS logical Function Configuration Tab
Logical Function Configuration > External Resource Configuration > External RNC
Function, and double-click External UTRAN Cell. Set the related parameters. See
Figure 6-10.

RAN Sharing
Figure 6-10 Parameters on the External UTRAN Cell Tab
double-click External GSM Cell. Set the related parameters. See Figure 6-11.
Figure 6-11 Parameters on the External GSM Cell Tab
In the configuration resource tree window, open the [Modify Area->Managed

Element->UMTS Logical Function Configuration] interface and set the parameters, as
shown in Figure 6-12

RAN Sharing
Figure 6-12 The parameters in LTE Handover Support Sharing Switch
Logical Function Configuration > Link Configuration > Local Managed Element
Plmn Information, and double-click Logic Iub Link Configuration. Set Minimal
percent of CE can be used by the PLMN. See Figure 6-13.

RAN Sharing
Figure 6-13 Configuring the Minimal percent of CE can be used by the PLMN
Parameter
Logical Function Configuration > Link Configuration, and double-click Iub Link. Set
CE Share Switch for Carrier Sharing and Share Mode of CE Resource for
Multi-Operators. See Figure 6-14 and Figure 6-15.

RAN Sharing
Figure 6-14 Configuring the CE Share Switch for Carrier Sharing Parameter
Figure 6-15 Configuring the CE Share Switch for Carrier Sharing Parameter
None
None
None

RAN Sharing
In the configuration resource tree, select Modify Area > Managed Element > Transport
Network > Transmission Path Group, and double-click PLMN Configuration of Path
Group. Set Used PLMN Group and Ratio of occupied private bandwidth of Path
Group by operator. See Figure 6-16.
Figure 6-16 Parameters on the PLMN Configuration of Path Group Tab
In the configuration resource tree, select Modify Area > Managed Element > Transport
Network > User Plane Service Configuration, and double-click Service IP
Configuration. Set Whether IP address support all PLMNs and Used Local Plmn
Group. See Figure 6-17.

RAN Sharing
Figure 6-17 Parameters on the Service IP Configuration Tab
In the configuration resource tree, select Modify Area > Managed Element > System
Global Configuration > System Function, and double-click UDP Port Configuration.
Set System Mode, Plmn Index, Application Type of IP address, and Multiple of UDP
port. See Figure 6-18.
Figure 6-18 Parameters on the UDP Port Configuration Tab

RAN Sharing
PLMN Information > Logical Iub Link, and double-click Iub Transmission Path. Set
Used PLMN Configuration of Path Group. See Figure 6-19.
Figure 6-19 Parameters on the Iub Transmission Path Tab
PLMN Information > Logical MGW Link, and double-click MGW Transmission Path.
Set Used PLMN Configuration of Path Group. See Figure 6-20.

RAN Sharing
Figure 6-20 Parameter on the MGW Transmission Path Tab
Logical Function Configuration > Link Configuration > Adjacent ManagedElement
PLMN Information > Logical Iur Link, and double-click Iur Transmission Path. Set
Used PLMN Configuration of Path Group. See Figure 6-21.
Figure 6-21 Parameters on the Iur Transmission Path Tab

RAN Sharing
PLMN Information > Logical Iups Link Group > Logical Iups Link, and double-click
Iups Transmission Path. Set Used PLMN Configuration of Path Group. See Figure
6-22.
Figure 6-22 Parameters on the Iups Transmission Path Tab
Plmn Information, and double-click Flow control of Iu Interface. Set the related
parameters. See Figure 6-23.

RAN Sharing
Figure 6-23 Parameters on the Flow Control of Iu Interface Tab
None
In the configuration resource tree, select Modify Area > Managed Element > Plmn
Group Configuration, and double-click PLMN Group. Set Mobile Country Code, MNC
BCD Code Length, Mobile Network Code, and Default PLMN Indicator. See Figure
6-24. The PLMN Index parameter is automatically generated by the OMC, so it is not
displayed in this capture.

RAN Sharing
Figure 6-24 Parameters on the PLMN Group Tab
In the configuration resource tree, select Modify Area > Managed Element > PLMN
Group, and double-click Local PLMN Group. Set Used PLMN Group. See Figure 6-25.
Figure 6-25 Parameters on the Local PLMN Group Tab
Logical Function Configuration > Link Configuration > UMTS Logical Function
Configuration > Link Configuration, and double-click Adjacent ManagedElement
PLMN Information. Set Used PLMN Group. See Figure 6-26.

RAN Sharing
Figure 6-26 Parameters on the Adjacent ManagedElement PLMN Information Tab
Logical Function Configuration > Link Configuration, and double-click Local
Figure 6-27 Parameters on the Local ManagedElement PLMN Information Tab

RAN Sharing
6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure - Basic Network Sharing Support
Test Item Basic RAN Sharing Support
1. The WCDMA system is ready.

2. RNC1 is connected to CN1 and CN2 synchronously.
3. SNAC is configured on both CN1 and CN2.
4. Both CN1 and CN2 support network sharing (MOCN or GWCN).
Prerequisit
5. Cell1 and cell2 belong to RNC1 with the same or different
e
frequencies. Cell1 is configured with PLMN1 and LAC1, and cell2 is
configured with PLMN2and LAC1.
6. UE1 is authorized to access SNAC1 (PLMN1, LAC1) and SNAC2
(PLMN2, LAC1), and resides in cell1 in idle mode.
1. Use UE1 to make a voice call to PSTN and/or UE2.

2. Release the CS call.
Steps 3. Use UE1 to reside in cell2 in idle mode.
4. Use UE1 to make a voice call to PSTN and/or UE2.
1. The voice call in cell1 of PLMN1 is established successfully.
Expected 2. The voice call in cell2 of PLMN2 is established successfully.

Result 3. The correct PLMN ID is displayed in the InitialUE_MessageMsg
message.
Table 6-2 Feature Validation Procedure - RAN Sharing with Dedicated Carrier
Test Item RAN Sharing with Dedicated Carrier

RAN Sharing
Test Item RAN Sharing with Dedicated Carrier

2. RNC1 is connected to CN1 and CN2 synchronously.
3. CN1 is configured with PLMN A, and CN2 is configured with PLMN
B. Both CN1 and CN2 support network sharing (MOCN).
Prerequisit
4. Cell1 and cell2 belong to RNC1. Cell1 is configured with PLMN A,
e
and cell2 is configured with PLMN B. Cell1 and cell 2 have different
frequencies.
5. UE1 is a subscriber of PLMN A, and UE2 is a subscriber of PLMN
B.
1. Use UE1 to reside in cell1 in idle mode.

2. Use UE1 to make a voice call to PSTN.
Steps
4. Use UE2 to reside in cell2 in idle mode.
5. Use UE2 to make a voice call to PSTN.
1. The voice call in cell1 of PLMN A is established successfully.
Expected 2. The voice call in cell2 of PLMN B is established successfully.

Result 3. The correct PLMN ID is displayed in the InitialUE_MessageMsg
message.
6.3.3.1 Based on SNAC
Table 6-1 Feature Validation Procedure - Shared Network Access Control
Test Item Shared Networks Access Control

RAN Sharing
1. WCDMA system is ready.

2. RNC1 is connected with CN1 and CN2 synchronously.
3. CN1 and CN2 both configure PLMN/SNAC/LAC, CN1 with
PLMN1, SNAC1 and LAC1, CN2 with PLMN2, SNAC2 and LAC2.
Preconditio 4. Both CNs support shared network (e.g. MOCN).

ns 5. Cell1, cell2 and cell3 belongs to RNC1 with the different/same
frequency, cell1 is configured with PLMN1, LAC1, cell 2 is
configured with PLMN2, LAC2, and cell3 is configured with PLMN1
LAC1.
6. UE1 is authorized to SNAC1 and camps in cell1 in idle mode.
1. UE1 makes a voice call to PSTN/UE2 and move the UE1 from
cell1 to cell2 to trigger handover to cell2.
Test Steps
2. UE1 makes a voice call to PSTN/UE2 and move the UE1 from
cell1 to cell3 to trigger handover to cell3.
1. In step1, the handover is not successful because cell2 is not

Anticipative
authorized to UE1;
Result
2. In step2, the handover is successful;
6.3.3.2 Based on PLMN-Id Label of the LTE Neighbor Cell
Table 6-3 Feature Validation Procedure
1. WCDMA system is ready.

2. RNC1 is connected with CN1 and CN2 synchronously.
Preconditio 3. Both CN support shared network (MOCN or GWCN).

ns 4. Cell1 belongs to RNC1 configured with PLMN1, Cell 2 belongs to
eNODEB1 configured with PLMN2, Cell 3 belongs to eNODEB2
configured with PLMN1.
1. UE makes a PS call in cell1, move the UE from cell1 to cell2.

Test Steps
2. Move the UE to cell3

RAN Sharing
1. In step1,the handover to Cell2 is not successful because the

Anticipative
PLMN of cell2 is different from cell1, cell2 is not authorized;
Result
2. In step2,the handover to Cell3 is successful;
Table 6-4 Feature Validation Procedure - Operator Specific CE Resource
Test Item Operator Specific CE Resources
2. RNC1 is connected to CN1 and CN2.

3. CN1 is configured with PLMN A, and CN2 is configured with PLMN
B.
Prerequisit
e 4. Cell1 belongs to RNC1, and is configured with PLMN A. Cell2
belongs to RNC1, and is configured with PLMN B.
5. CE Share switch for carrier sharing is set to ON.

6. The minimum CE percent of PLMN A is set to 0.5%, and the
minimum CE percent of PLMN B is set to 99.5%.

RAN Sharing
Test Item Operator Specific CE Resources
1. Check the initial CE resource from the NBAP Audit response to

make sure how many CE resources that 0.5% indicates.
2. Use UE1 and UE2 to reside in cell1.

3. Use UE1 to make a CS 12.2k voice call to PSTN.
Steps
5. Release all the CS calls.
6. Use UE1 and UE2 to reside in cell2.
9. Release all the CS calls.
1. UE1 sets up CS services successfully in cell1, but UE2 fails to set
Expected up CS services because the CAC refuses it due to lack of CE
Result resources.
2. UE1 and UE2 set up CS services successfully in cell2.
Table 6-5 Feature Validation Procedure - Operator Specific FM/PM/CM
Test Item Operator Specific FM/PM/CM

RAN Sharing
Test Item Operator Specific FM/PM/CM
1. The RAN and core network are operating properly.

2. The link between the OMC and NE is normal.
3. The OMC is operating properly.
Prerequisit 4. The RNC is connected to CN1 and CN2 synchronously.
e 5. CN1 is configured with PLMN A, and CN2 is configured with PLMN
B. Both CN1 and CN2 support network sharing (MOCN or GWCN).
6. Cell1 and Cell2 belong to RNC1/NODEB1. Cell1 is configured with
PLMN A+PLMN B, and Cell2 is configured with PLMN B.
1. Select View > Configuration Management, and click the sub

menu.
2. Check the parameters of Cell1 and Cell2, and modify them if
required.
3. Select View > Performance Management, and click the sub
menu.
4. Select Performance Management > performance data query.
5. Select the KPIs in Query Index by different PLMN.
6. Configure the query granularity and the check the time in the
Query Time page.
Steps 7. Select the NE in the Query Object page.
8. Click OK. The query result is displayed.
9. Select View > Fault Management, and click the sub menu.
10. Select Query > View History Alarms. The History Alarm Query
Conditions window is displayed.
11. Click the Quick Search button at the top left corner of the window.
The View History Alarms dialog box is displayed.
12. Set the query conditions (by different PLMN) in the Query History
Alarm window.
13. After the query condition is set, click OK. The query results are
returned in View History Alarms.
Expected
In step 8 and 13, the query results are correct.
Result

RAN Sharing
Table 6-6 Feature Validation Procedure - Operator Specific Function Control
Test Item Operator Specific Function Control

2. RAN sharing with dedicated carriers or RAN sharing with shared
carriers is configured.
3. If RAN sharing with dedicated carriers is used, cell1 is configured
with PLMN A, and cell2 is configured with PLMN B. Cell1 and cell2
Prerequisit
e have different frequencies.
4. UE1 in PLMN A and UE2 in PLMN B have the same subscription.
5. PLMN A supports encryption algorithm UEA0, but does not support

UEA1 and UEA2. PLMN B supports encryption algorithm UEA0
and UEA1, but does not support UEA2.
1. Use UE1 to make a voice call to PSTN and/or UE3 in cell1.

Steps
2. Use UE2 to make a voice call to PSTN and/or UE4 in cell2.
1. In step1, no encryption is used for UE1.
Expected
Result
2. In step2, encryption algorithm UEA1 and UEA0 are used for UE2.
Table 6-7 Feature Validation Procedure - Operator QoS Priority
Test Item Operator QoS Priority

RAN Sharing
Test Item Operator QoS Priority

2. RAN sharing with dedicated carriers or RAN sharing with shared
carriers is configured. RAN sharing with dedicated carrier is shown
as example.
Prerequisit
3. Cell1 is configured with PLMN A, and cell2 is configured with
e
PLMN B.
4. UE1 in PLMN A and UE2 in PLMN B have the same subscription.
5. The DL TCP admission parameters of PLMN A and PLMN B are
configured to admit UE1 but not UE2.
1. Use UE1 to make a voice call to PSTN in cell1.

Steps
2. Use UE2 to make a voice call to PSTN in cell2.
Expected 1. In step1, UE1 sets up the voice call successfully.

Result 2. In step2, UE2 fails to set up the voice call due to DL TCP limit.
Table 6-8 Feature Validation Procedure - Operator Specific Iub Transmission
Test Item Operator Specific Transmission-Iub

2. Cell1 supports HSUPA, HSDPA and DCH. Cell1 is configured with
PLMN 1 and PLMN 2. Transmission paths are configured with
different PLMNs. PATH1 is configured with PLMN1, and PATH2 is
Prerequisit
configured with PLMN2.
e
3. UE1 in PLMN1 resides in Cell1 in idle mode. Background
MBR2048kbps/2048bps (DL/UL) is subscribed in HLR.
4. UE2 in PLMN2 resides in Cell1 in idle mode. Background MBR
2048kbps/2048bps (DL/UL) is subscribed in HLR.
1. Use UE1 in PLMN1 to activate a PS call in Cell1.

2. End the PS call after 30 seconds.
Steps
3. Use UE2 in PLMN2 to activate a PS call in Cell1.

RAN Sharing
Test Item Operator Specific Transmission-Iub
1. In step1, UE1 sets up the PS call successfully and occupies the
Expected transmission bandwidth of PATH1.

Result 2. In step2, UE2 sets up the PS call successfully and occupies the
transmission bandwidth of PATH2.
Table 6-9 Feature Validation Procedure - Operator Specific Iur Transmission
Test Item Operator Specific Transmission-Iur

2. RNC1 and RNC2 are connected with IP transmission.
3. The Iur connection is available between RNC1 and RNC2. R6, R5,
and R99 are supported over the Iur interface.
4. Cell1 and Cell2 belong to RNC1 (RAN Sharing). Cell1 is configured
with PLMN 1, and Cell2 is configured with PLMN 2. Cell3 belongs to
RNC2. The three cells have different frequencies. Cell3 and Cell1,
Prerequisit and Cell 3 and Cell 2 are adjacent cells over the Iur interface with
e different coverage.
5. RNC2 acts as an SRNC, which has two Iur transmission paths:
PATH 3 for PLMN1 and PATH4 for PLMN2. The bandwidth of the
two paths are different.
6. The timer of Relocation Delay for PS Service is large enough to
hold the UE on the Iur interface.
7. The UE resides in cell3 in idle mode, and background
MBR2048kbps/2048kbps (DL/UL) is subscribed in HLR at first.

RAN Sharing
Test Item Operator Specific Transmission-Iur
1. Use the UE to activate a PS call in Cell 3.

2. Move the UE from Cell3 to Cell1 to trigger event 2D and activate
compressed mode.
3. Move the UE further to Cell1 to trigger event 2A.
Steps
5. Use the UE to activate a PS call in Cell 3.
6. Move the UE from Cell3 to Cell2 to trigger event 2D and activate
compressed mode.
7. Move the UE further to Cell2 to trigger event 2A.
1. In step1-3, the UE sets up the PS call successfully and occupies the
Expected transmission bandwidth of PATH3.

Result 2. In step5-7, the UE sets up the PS call successfully and occupies the
transmission bandwidth of PATH4.
Table 6-10 Feature Validation Procedure - Operator Specific RNC Resource
Test Item Operator Specific RNC Resource
1. The WCDMA system is ready, and the OMC is operating properly.

2. RAN sharing with dedicated carriers is configured. Cell1 and Cell2
belong to RNC1/NODEB1. Cell1 is configured with PLMN A, and
Cell2 is configured with PLMN B. The two cells have different
frequencies.
Prerequisit 3. UE7 supports R6 and subscribes interactive/background class with

e MBR=DL8Mbps/UL2Mbps.
4. Only three pairs of CS12.2k services are allowed for PLMN A, and
other resources are reserved for PLMN B.
5. Only 1000 kbps throughput is allowed for PLMN A, and other
resources are remained for PLMN B.
6. UE1UE8 reside in Cell1 in idle mode.

RAN Sharing
Test Item Operator Specific RNC Resource
1. Use UE1 to make a CS12.2k call to UE2 in cell1.

2. Use UE3 to make a CS12.2k call to UE4 in cell1
Steps 3. Use UE5 to make a CS12.2k call to UE6 in cell1.
4. Use UE7 to make a PS call in cell1 and start FTP download.
5. Use UE8 to make a PS call in cell2 and start FTP download.
1. In step1, the CS12.2k call is set up successfully.

2. In step2, the CS12.2k call is set up successfully.
3. In step3, the CS12.2k call is set up successfully
4. Alarms about IU CS traffic overload are raised in the History
Alarm window.
Expected 5. In step4, the PS call is set up on HS/EDCH and the DL rate is no

Result more than 1000 kbps because RNC resources for PLMN A are
limited.
6. Alarms about IU PS traffic overload are raised in the History Alarm
window.
7. In step5, the PS call is set up on HS/EDCH and the DL rate is not
limited because RNC resources for PLMN B are not limited.
Table 6-11 Feature Validation Procedure - Extended GSM Neighboring Cells
Test Item Extended GSM Neighboring Cells
1. The WCDMA system and GSM system are ready.

2. UMTS 2100M Cell1 supports HSUPA, HSDPA and DCH. Cell1
belongs to PLMN A and PLMN B. GSM Cell2 belongs to
BSC1/BTS1.
Prerequisit 3. Cell1 and Cell2 are adjacent cells with different coverage.
e 4. Cell1 has 96 GSM neighbor cells in total (including Cell2), and
Cell2 has a higher priority. There are 10 GSM cells belong to PLMN
A and 10 GSM cells that belong to PLMN B.
5. UE1 and UE2 reside in the cell1 in idle mode. UE1 supports UMTS
and GSM.

RAN Sharing
Test Item Extended GSM Neighboring Cells
1. Use UE1 to reside in cell1 that belongs to PLMN A.

2. Set Target Cell Judgment Strategy for Access/Handover
Algorithm in Shared Network to Judgment Based on Selected
PLMN.
3. Use UE1 to make an AMR voice call to UE2 in Cell1.
4. Move UE1to Cell2 to trigger event 2D and activate compressed
mode.
5. Release the AMR call.
6. Use UE1 to reside in cell1 that belongs to PLMN B.
Steps 7. Use UE1 to make an AMR voice call to UE2 in Cell1.
8. Move UE1 to Cell2 to trigger event 2D and activate compressed
mode.
10. Set Target Cell Judgment Strategy for Access/Handover
Algorithm in Shared Network to Judgment Based on
Authorization Information.
11. Use UE1 to make an AMR voice call to UE2 in Cell1. Move UE1 to
Cell2 to trigger event 3A/3C and perform inter-RAT HO.
1. In step 4, 10 GSM neighbor cells that belong to PLMN A can be
found in the measurement control message.
Expected 2. In step 8, 10 GSM neighbor cells that belong to PLMN B can be
Result found in the measurement control message.
3. In step 11, 32 GSM neighbor cells can be found in the measurement
control message, including Cell2.
Table 6-12 Feature Validation Procedure - Multi PLMN Support
Test Item Multi PLMN Support

RAN Sharing
Test Item Multi PLMN Support

2. The CN supports multi-PLMN. PLMN1, PLMN2, and PLMN3 are
configured for this RNC as equivalent PLMN.
3. Cell1, Cell2, and Cell3 belong to RNC1/NodeB1, and they all
support HSUPA, HSDPA, and DCH.
Prerequisit 4. Cell1 is configured with PLMN1, Cell2 is configured with PLMN2,
e and Cell3 is configured with PLMN3.
5. Cell1, Cell2, and Cell3 have different frequencies. Cell2 is
configured as an adjacent cell of Cell1 with different coverage, and
Cell3 is configured as an adjacent cell of Cell2 with different
coverage.
6. UE1 (R6 or later) resides in Cell1 in Idle mode.
1. Move UE1 from Cell1 to Cell2 to trigger a cell reselection

procedure.
Steps
2. Move UE1 from Cell2 to Cell3 to trigger a cell reselection
procedure.
1. UE1 performs the cell reselection procedure successfully.

2. UE1 performs the location update procedure and routing area
Expected
update procedure successfully after cell reselection.
Result
3. The correct PLMN ID is displayed in the Location Updating Accept
message and Routing Area Update accept message.
6.4 Feature Deactivation Procedure
Table 6-13 Feature Deactivation Procedure - Basic Network Sharing Support
Managed Object. logic Default

GUI Name Deactivation Value
name Value
0xFF: No
URncFunction. Shared Network
Shared 0xFF
sharedNetMode Mode
Network

RAN Sharing
None
None
Table 6-14 Feature Deactivation Procedure - Operator Specific CE Resource
Managed Object. logic name Default Deactivat

GUI Name
Value ion Value
Minimal percent of CE
MinCEPercent[DBS_RR_MAX_NU
can be used by the 0 0
M_SHARED_PLMN_PER_CELL
PLMN
CE Share Switch for

CeShareSwitch 0 0
Carrier Sharing
LTE Handover Support

URncFunction. ShareExLteSwch 0:Off 0:Off
Sharing Switch
None
None
None
None

RAN Sharing
Table 6-15 Feature Deactivation Procedure - Operator Specific RNC Resource
Managed Object. logic name Default Deactivation

GUI Name
Value Value
IU traffic flow
UIuFlowCtrl. IuFlowCtrlType 0 0
control type
IU PS low control ALL PLMNs:

UIuFlowCtrl. IuPSLowThres 50000
threshold 50000
IU PS high control ALL PLMNs:

UIuFlowCtrl. IuPSHighThres 60000
threshold 60000
IU CS low control ALL PLMNs:

UIuFlowCtrl. IuCSLowThres 500
threshold 500
IU CS High control ALL PLMNs:

UIuFlowCtrl. IuCSHighThres 600
threshold 600
None
None
For the description and configuration of these parameters, refer to Chapter 6.2.
6.5 Impact on the Network
Advantages of this feature:
RNC resources, such as CE, transport, carrier frequency, and QoS, are shared in
accordance with the different sharing requirements of the operators.
Disadvantages of this feature:
None

RAN Sharing
7 Abbreviation
Abbreviation Full Name
rd
3GPP 3 Generation Partnership Project
BSC Base Station Controller
CE Channel Element
CN Core Network
CS Circuit Switch
DL Down Link
MS/UE Mobile Station/User Equipment
PS Packet Switch
RNC Radio Network Controller
UL Up Link
UTRAN UMTS Terrestrial Radio Access Network
WCDMA Wideband Code Division Multiple Access
BPA Base Pool Area
IDNNS Intra Domain NAS Node Selector
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
LA Location Area
MCC Mobile Country Code
MNC Mobile Network Code
MOCN Multi-Operator Core Network
MS Mobile Station
MSC Mobile Switching Centre
NNSF NAS Node Selection Function
NRI Network Resource Identifier
PLMN Public Land Mobile Network
PPA Preferred Pool Area
RA Routing Area
RAN Radio Access Network
SGSN Serving GPRS Support Node
TMSI Temporary Mobile Subscriber Identity

RAN Sharing
DRNC Drift Radio Network Controller
GWCN Gateway Core Network
MOCN Multi-Operator Core Network
OPC Origination Point Code
SCCP Signaling Connection Control Part
SNA Shared Network Area
SNAC Shared Network Area Code
SRNC Serving Radio Network Controller
8 Reference Document
[1]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Parameter
Reference
[2]ZXWR RNC (V3.13.10.15) Radio Network Controller Radio Parameter Reference
[3]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Counter Reference
[4]ZXWR RNC (V3.13.10.15) Radio Network Controller Radio Counter Reference

ZTE UMTS RAN Sharing Feature Guide PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZTE UMTS RAN Sharing Feature Guide PDF

Încărcat de

Drepturi de autor:

Formate disponibile

RAN Sharing

2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attribute ............................................................................................... 8

3 Technical Description ..................................................................................... 18

ZTE Confidential Proprietary 2

5 Related Counters and Alarms ........................................................................ 59

6 Engineering Guide .......................................................................................... 62

ZTE Confidential Proprietary 3

6.4.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier ......................................... 93

ZTE Confidential Proprietary 4

Figure 2-1 Network Architecture of MOCN .......................................................................... 9

ZTE Confidential Proprietary 5

Figure 6-19 Parameters on the Iub Transmission Path Tab ...............................................74

ZTE Confidential Proprietary 6

ZTE Confidential Proprietary 7

Node B Version: [ZXSDR V4.13.10.20]

2.1 Feature Introduction

ZTE Confidential Proprietary 8

2.1.1 ZWF21-30-100 Basic Network Sharing Support

Multi-operator core network (MOCN)

Figure 2-1 Network Architecture of MOCN

Gateway core network (GWCN)

Figure 2-2 Network Architecture of Gateway Core Network Sharing

Shared Shared Shared

RNC RNC RNC

Radio Access Network

ZTE Confidential Proprietary 9

In the MOCN scenario, PLMNs are handled as follows:

2.1.2 ZWF21-30-101 RAN Sharing with Dedicated Carrier

ZTE Confidential Proprietary 10

Figure 2-3 Independent Carrier Network Sharing

Operator one Shared RNC Shared Node B

Frequency one Frequency one MNC

Frequency two Frequency two MNC

Carriers of different operators can be identified by different PLMN codes broadcasted in

2.1.3 ZWF21-30-102 Shared Network Access Control

ZTE Confidential Proprietary 11

2.1.4 ZWF21-30-121 Operator Specific CE Resource

2.1.5 ZWF21-30-120 Operator Specific FM/PM/CM

ZTE Confidential Proprietary 12

2.1.6 ZWF21-30-116 Operator Specific Function Control

RNC-level functions applied to a single subscriber

ZTE Confidential Proprietary 13

Cell-level functions applied to all subscribers in each cell

Other functions applied to a physical device

Operator-specific function control is implemented through the license control mechanism

2.1.7 ZWF21-30-117 Operator QoS Priority

PLMN-based QoS priority configuration is introduced. The QoS priority will be

ZTE Confidential Proprietary 14

2.1.8 ZWF21-30-118 Operator Specific Iub/Iur Transmission

Figure 2-4 Four-Operator-Shared Iub Interface

Transmission resources of logical transport paths among different operators can be

ZTE Confidential Proprietary 15

2.1.9 ZWF21-30-119 Operator Specific RNC Resource

Capacities can be logically separated in shared RNC equipment and purchased by

2.1.10 ZWF21-30-122 Extended GSM Neighboring Cells

2.1.11 ZWF21-30-200 Multi PLMN Support

ZTE Confidential Proprietary 16

2.2 License Control

Table 2-1 License Control List

ZWF21-30-100 Basic RAN Sharing WCDMA

ZWF21-30-101 RAN Sharing with WCDMA