Ran Sharing

WCDMA RAN
RAN Sharing Feature Parameter Description

Issue 01
Date 2015-03-25
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between Base Station Types
2 Overview
3 Technical Description
3.1 UE's Network Selection
3.1.1 Operator ID and Type
3.1.2 System Information Broadcast
3.1.3 UE's Route Selection
3.2 Flexible Network Architecture
3.2.1 Iu Interface
3.2.2 Iu-BC Interface
3.2.3 Iub Interface
3.2.4 Iur interface
3.2.5 Single CN With Multi-PLMN IDs
3.2.6 Base Station Supporting Multi-operator PKI
3.2.7 Typical Networking Modes of RAN Sharing
3.2.7.1 Coexistence of RNCs Under Full Coverage
3.2.7.2 Coexistence of Shared RNC and 2G Network
3.2.7.3 Coexistence of Full and Partial Coverage for Different Operators
3.2.7.4 Coexistence of Iu Flex and RAN Sharing
3.2.7.5 Coexistence of Multiple Operators
3.3 Mobility Control and Service Differentiation
3.3.1 Mobile Control
3.3.2 Service Differentiation
3.4 License Management
3.5 Operation and Maintenance
4 Engineering Guidelines
4.1 WRFD-021304 RAN Sharing Introduction Package
4.1.1 When to Use WRFD-021304 RAN Sharing Introduction Package
4.1.2 Deployment
4.1.2.1 Requirements
4.1.2.2 Data Preparation
4.1.2.3 Activation
4.1.2.4 Activation Observation
4.1.2.5 Deactivation
4.1.3 Performance Monitoring
4.1.4 Troubleshooting
4.2 WRFD-02130401 Dedicated Carrier for Each Operator
4.3 WRFD-02130402 Flexible Network Architecture
4.3.1 When to Use WRFD-02130402 Flexible Network Architecture
4.3.2 Deployment
4.3.2.3 Activation
4.4 Single CN With Multi-PLMN IDs
4.4.1 When to Use Single CN With Multi-PLMN IDs
4.4.2 Required Information
4.4.3 Deployment
4.5 WRFD-02130403 Mobility Control and Service Differentiation
4.5.1 When to Use WRFD-02130403 Mobility Control and Service Differentiation
4.5.2 Deployment
4.5.2.3 Activation
4.6 WRFD-02130404 Independent License Control
4.7 WRFD-02130406 Transmission Recourse Sharing on Iub/Iur Interface
5 Parameters
6 Counters
7 Glossary
8 Reference Documents
1 About This Document
1.1 Scope
This document describes RAN Sharing, including its technical principles and engineering guidelines.
This document covers the following features:
WRFD-021304 RAN Sharing Introduction Package
WRFD-02130401 Dedicated Carrier for Each Operator
WRFD-02130402 Flexible Network Architecture
WRFD-02130403 Mobility Control and Service Differentiation
WRFD-02130404 Independent License Control
WRFD-02130405 Independent Cell-level FM/PM/CM
WRFD-02130406 Transmission Recourse Sharing on Iub/Iur Interface
This document applies to the following types of network elements (NEs).
NE Type Model
RNC BSC6900 and BSC6910
NodeB Macro 3900 series macro base stations: BTS3900, BTS3900A, BTS3
BTS3900C
Micro BTS3911E
LampSite DBS3900 LampSite
1.2 Intended Audience

This document is intended for personnel who:
Need to understand the features described herein
Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are two
types of changes:
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version
RAN17.1 01 (2015-03-25)
This issue does not include any changes.

RAN17.1 Draft A (2015-01-15)
Compared with Issue 02 (2014-07-30) of RAN16.0, Draft A (2015-01-15) of RAN17.1 includes the
following changes.
Change Type Change Description

Feature change Added the Base Station Supporting Multi-operator PKI feature. For details, see 3.2.6 B
Supporting Multi-operator PKI.
Added the Single CN With Multi-PLMN IDs function. For details, see 3.2.5 Single CN
Multi-PLMN IDs.
Editorial change None
1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Description Supported by Base Station Controller Supported by

Macro Base Stat
BSC6900 BSC6910
WRFD-021304 RAN SharingIntroduction Y Y Y
Package
WRFD-02130401 Dedicated Carrier for Y Y Y

Each Operator
WRFD-02130402 Flexible Network Y Y Y

Architecture
WRFD-02130403 Mobility Control and Y Y Y

Service Differentiation
WRFD-02130404 Independent License Y Y Y

Control
WRFD-02130405 Independent Cell-level Y Y Y

FM/PM/CM
WRFD-02130406 Transmission Y Y Y
Recourse Sharing on
Iub/Iur Interface
NOTE:
"Y" indicates that this feature is supported by the NE. "N" indicates that this feature is not supported
by the NE. N/A indicates that an NE is not involved, that is, a feature does not require the support of
the NE.
2 Overview
Introduction
The RAN Sharing feature enables operators to share RAN equipment RNCs and NodeBs while
keeping individual core networks (CNs) and frequencies.
After RAN Sharing is introduced, RAN equipment is shared, but the operators can use their dedicated
frequencies (WRFD-02130401 Dedicated Carrier for Each Operator) and their independent cells. The
same RAN equipment can provide customized solutions to different operators.
Benefits
The most important driving force for operators to implement RAN Sharing is that this feature can
reduce about 30%40% of the CAPEX and OPEX and improve network resource utilization.
However, RAN Sharing reduces network independence. The specific gains provided by this feature
are as follows:
Lower costs
The motivation for operators to share networks is to reduce investment and operation costs.
Higher deployment efficiency
RAN Sharing can overcome the problem of lack of sites or antennas and simplify network
deployment, so that each sharing operator can speed up deployment of the entire network and
expansion of the coverage area.
Architecture
Figure 2-1 shows the structure of RAN Sharing. The shared equipment is U2000 and RAN, and
the sharing interfaces are Iub, Iur, and Itf-S. The cell, CN, and northbound NMS are dedicated to each
operator.
RAN Sharing brings changes in interfaces, functions, license management, and operation and
maintenance (O&M), which are described in detail later in this document.
Figure 2-1 Shared NEs
3 Technical Description
3.1 UE's Network Selection
A UE obtains the PLMN ID and selects a cell to camp on according to system information, and the
RNC finishes the UE's network selection based on the cell that the UE accesses.
3.1.1 Operator ID and Type

Each operator corresponds to a globally unique PLMN ID, which consists of MCC and MNC.
In the RNC, the CnOpIndex(BSC6900,BSC6910) parameter identifies a specified operator and has a
mapping relationship with the PLMN ID. CnOpIndex(BSC6900,BSC6910) can be quickly indexed to
a specified operator.
In RAN Sharing, there are two types of operators: primary operator and secondary
operator. OperatorType(BSC6900,BSC6910) identifies the operator type. There must be a primary
operator in an RNC.
The primary operator must be one of the sharing operators and has a higher license management
priority than secondary operators.
3.1.2 System Information Broadcast

A UE obtains the PLMN ID and selects a cell to camp on according to system information broadcast.
Each cell has a unique PLMN ID in a RAN sharing network similar to a non-RAN sharing network.
The PLMN IDs are different for different operators' cells under the same RNC.
3.1.3 UE's Route Selection

On the RNC, the CnOpGrpIndex(BSC6900,BSC6910) parameter specifies an index for an operator
group. In the RAN Sharing feature, the operator group index includes
one CnOpIndex(BSC6900,BSC6910). The ADD UCNOPERATOR command can be used to define
the mapping between a PLMN ID and an operator index.
After a UE is switched on, it first selects a PLMN. Upon detecting different PLMNs broadcast by
different cells, the UE preferentially selects the cell of its home PLMN (HPLMN) to camp on. If the UE
is not the subscribed user of an operator, it cannot camp on the cells of the operator, as shown
in Figure 3-1.
Figure 3-1 UE's route selection
When the UE initiates a service request, the RNC routes the UE to the CN node of the operator based
on the cell on which the UE camps. If the operator has deployed the Iu Flex feature, you must run the
ADD UNRIGLBCNIDMAP command to add the mapping between NRIs and CN nodes. The RNC
then routes the UE to the corresponding CN node based on the UE's NRI, which is derived from the
TMSI and P-TMSI. For details about Iu Flex, see Iu Flex Feature Parameter Description.
NOTE:
A CN node (such as the MSC server and SGSN) belongs to only one operator regardless of
whether RAN Sharing is used.
3.2 Flexible Network Architecture

This section describes the following features:
WRFD-02130402 Flexible Network Architecture
WRFD-02130406 Transmission Recourse Sharing on Iub/Iur Interface
All the physical connections supported by a shared RNC are the same as those supported by a non-
shared RNC. That is, a shared RNC can connect to both shared and non-shared RNCs and to both
shared and non-shared NodeBs. Figure 3-2 shows the network architecture after RAN Sharing is
used, which mainly consists of a shared RAN and a shared OSS.
Figure 3-2 Network architecture after RAN Sharing is used
3.2.1 Iu Interface
In a shared RNC, different operators require different Iu interfaces, but these Iu interfaces can be
deployed on the same interface board.
Each CN connected to the shared RNC must have a globally unique CN ID configured on the RNC.
To configure the CN ID, use
the CnOpIndex(BSC6900,BSC6910) and CNId(BSC6900,BSC6910) parameters in the ADD
UCNNODE command.
Figure 3-3 shows an RNC shared by operators A and B. Operator A has deployed Iu Flex, and
operator B has not.
Figure 3-3 RNC shared by operators A and B
Operators can activate or deactivate the Iu Flex feature independently. Iu Flex is configured the same
way in a shared RNC as in a non-shared RNC. The SET UOPERATORCFGPARA command is used
to configure whether an operator supports Iu Flex and to configure the NRI length. The ADD
UNRIGLBCNIDMAP command is used to configure the mapping between NRIs and CN nodes. For
the method of deploying Iu Flex, see Iu Flex Feature Parameter Description.
3.2.2 Iu-BC Interface

Each non-shared RNC can be connected to only one cell broadcast center (CBC).
Each shared RNC can be connected to a maximum of four CBCs. Each operator has only one
dedicated CBC, and the Iu-BC interface is dedicated to each operator. Figure 3-4 shows operator-
dedicated Iu-BC interfaces between a shared RNC and dedicated CBCs. On an Iu-BC interface, the
Service Area Broadcast Protocol (SABP) peer entity uses TCP/IP. Each operator that uses the cell
broadcast service (CBS) should configure a dedicated connection to its own CBC. For details about
CBS, see CBS Feature Parameter Description.
Figure 3-4 Operator-dedicated Iu-BC interfaces between a shared RNC and dedicated CBCs
3.2.3 Iub Interface

The physical attributes of the Iub interface in a RAN sharing network are the same as those in a non-
RAN sharing network. A shared RNC can connect to both shared and non-shared NodeBs, as shown
in Figure 1. The maximum numbers of NodeBs and cells supported by a shared RNC are the same as
those supported by a non-shared RNC.
Figure 3-5 Shared RNC connecting to both shared and non-shared NodeBs
For a shared NodeB, each operator can have an independent base station transmission port, or
multiple operators share a base station transmission port.
If multiple operators share a transmission port, the attributes of the transmission port and the values
of each attribute should be appropriately configured based on the backhaul network performance, for
example the maximum transmission unit (MTU), of each operator.
If the MTU value of each operator's backhaul network is different, the MTU value on the transmission
port can be configured as MIN(MTU1,MTU2,MTU3...). As a result, all over-long packets are
fragmented on the base station. The MTU value can also be configured as
MAX(MTU1,MTU2,MTU3...). In this way, the fragmentation and reassembly for networks with a large
backhaul network MTU value can be reduced. For networks with a small backhaul network MTU
value, some packets are moved upward to routers for fragmentation purposes.
Transmission for the Iub Control Plane and Management Plane
In RAN sharing, the transmission for the Iub control plane and management plane is the same as that
in non-RAN sharing scenarios. As shown in Figure 3-6, the NCP, CCPs, ALCAP link, and OM path
are common to all operators that share the NodeB.
Each NodeB has only one NCP, one ALCAP link, and multiple CCPs. The mapping between cells and
CCPs is not fixed. A CCP is selected using the load balancing policy, rather than through operators or
cells in which the call is initiated.
Common NBAP (such as cell setup, cell reconfiguration, common transport channel setup, and radio
link setup) is implemented through the NCP. All operators must share the NCP.
Figure 3-6 Shared Iub connections
Transmission for the Iub User Plane
Iub user-plane transmission resources can be shared or dedicated by operators, as shown in Figure
3-7.
Figure 3-7 Allocation of transmission resources for the Iub user plane
NOTE:
When the BSC6910 is used, only Iub transmission resource sharing is supported.
An ALCAP link exists only when ATM transmission is used.
For details about Iub transmission resource sharing and exclusive use, see TRM in
the RAN Sharing Scenario Feature Parameter Description.
3.2.4 Iur interface

In a RAN sharing network, Iur transmission resources are totally shared by operators.
A shared RNC can connect to both shared and non-shared RNCs, as shown in Figure 3-8.
Figure 3-8 Shared RNC connecting to both shared and non-shared RNCs
3.2.5 Single CN With Multi-PLMN IDs

In the common RAN sharing scenario, operators also share CN devices to further reduce capital
expenditure (CAPEX) and operating expense (OPEX). The Single CN With Multi-PLMN IDs function
is introduced to support this scenario.
After the Single CN With Multi-PLMN IDs function is introduced into the
common RAN sharing scenario, cell system message broadcasting remains unchanged, but the
PLMN IDs broadcast in different operators' cells are different. However, this function causes the
following changes to the network:
The RNC routes UEs of all operators to the primary operator's CN node.
This function requires only the primary operator's CN node to be configured through
the OperatorType(BSC6900,BSC6910) parameter in the ADD UCNOPERATOR command.
The primary operator is unique on the RNC side. The RNC routes UEs of all operators to the
primary operator's CN node, regardless of which operators share the cells.
As the RNC is connected only to the CN node of one operator, the reset or overload procedure
triggered by the CN applies to all UEs served by the CN node. The RNC uses the PLMN ID of
the primary operator as the value of the "Global RNC ID" IE in the direct transfer message.
When the RST UCNNODE or RST UIU command is executed,
the CnOpIndex(BSC6900,BSC6910) and CNID(BSC6900,BSC6910) parameters must be set
to the index of the primary operator and the ID of the CN node of the primary operator,
respectively. Otherwise, execution of this command fails.
The primary operator's CN provides service to UEs of all operators.
All CN nodes must be deployed with the Multi-PLMN or GWCN feature on the CN side. If the
WRFD-021302 Iu-flex feature is enabled, the index of the operator that serves each CN node on
the RAN side must be that of the primary operator, and the multiple PLMN IDs must be the
same for all CN nodes.
In the WRFD-021302 Iu Flex feature, the mapping between the NRI and CN or the mapping
between the IMSI and CN cannot be configured for secondary operators. The UEs of the
secondary operator select the CN based on the primary operator's configuration.
The counters related to the Iu-interface change.
If the secondary operator's CN changes, the counters related to the Iu-interface also change.
For example, the counters in the following measurement objects measure the UEs of all
operators rather than of specific operators:
CS.SIG.IU
CS.TRF.IU
MBMS.IU
NAS.IU
PS.SIG.IU
PS.TRF.IU
SIG.SCCP.IU
3.2.6 Base Station Supporting Multi-operator PKI

The base station supports multi-operator PKI in the RAN sharing scenario. In addition to multiple
operators sharing PKI in RAN16.0, each operator can deploy a dedicated PKI server. The IPsec
tunnel uses the certificate issued by the dedicated PKI server to perform authentication. In this way,
the secondary operator does not rely on the primary operator's PKI server, which implements secure
isolation of services.
The networking of Base Station Supporting Multi-operator PKI is shown in Figure 3-9. For the working
principles and engineering guidelines for this feature, see Base Station Supporting Multi-operator PKI.
Figure 3-9 Base Station Supporting Multi-operator PKI deployed on the network
3.2.7 Typical Networking Modes of RAN Sharing
Typical networking modes of RAN Sharing include five typical application scenarios:
Coexistence of shared and non-shared RNCs under full coverage
Coexistence of shared RNC and 2G network
Coexistence of full and partial coverage for different operators
Coexistence of Iu Flex and RAN Sharing
Coexistence of multiple operators
3.2.7.1 Coexistence of RNCs Under Full Coverage

In the example shown in Figure 3-10, both operator A and operator B have deployed their own non-
shared 3G networks in one area and decide to deploy a shared 3G network together in another area.
Shared RNC1 is connected to shared RNC2, RNC A, and RNC B over the Iur interfaces. The
neighboring cell relations are also configured. Therefore, a UE of operator A is free to transfer from an
operator A cell to the neighboring operator A cell by soft handover. The same situation applies to
operator B. This scenario is applicable to an early stage of network rollout when there are a small
number of subscribers.
Figure 3-10 Coexistence of shared and non-shared RNCs under full coverage
3.2.7.2 Coexistence of Shared RNC and 2G Network

In the example shown in Figure 3-11, both operator A and operator B have deployed a GSM network
and decide to deploy a shared 3G network. To fully use the GSM resources, the new RAN network is
required to interwork with the existing GSM network. Therefore, the neighboring cells on shared
RNC1, Base Station System (BSS) A and BSS B are configured. Therefore, service continuity is
assured when a UE of operator A transfers between the operator A UMTS cell and the neighboring
operator A GSM cell. The same situation applies to operator B.
Figure 3-11 Coexistence of shared RNC and 2G network
3.2.7.3 Coexistence of Full and Partial Coverage for Different Operators

In the example shown in Figure 3-12, operator A has already deployed a RAN network and has a full
coverage, whereas operator B only has partial coverage. Operator B must share the RAN network
with operator A in uncovered areas of operator B to achieve full coverage.
When a UE of operator B transfers from the edge of a cell under operator B's coverage to an area
under operator A's coverage, the UE can access the cell of operator A through handover, cell
reselection, or cell update. When the UE transfers back to an area covered by both operators, the UE
can also re-access operator B's network through Shared Network Area (SNA) or International Mobile
Subscriber Identity (IMSI)-based handover.
In this scenario, the switch of InterPlmnHoAllowedIntraRat(BSC6900,BSC6910) must be enabled
and the neighboring cell relations must be configured.
Figure 3-12 Coexistence of full and partial coverage for different operators
3.2.7.4 Coexistence of Iu Flex and RAN Sharing
In the example shown in Figure 3-13, operator A and operator B share the RAN. To improve the
network reliability, operator A applies Iu Flex to both the Circuit Switched (CS) and the Packet
Switched (PS) domains, and operator B applies Iu Flex to the PS domain.
In this scenario, services of one operator can only be processed by the CN nodes of this operator.
Figure 3-13 Coexistence of Iu Flex and RAN Sharing
3.2.7.5 Coexistence of Multiple Operators

In the example shown in Figure 3-14, operator A and operator B share a RAN, and operator C has a
roaming agreement with operator B. This agreement allows all the subscribers of operator B and
operator C to share the network resources.
To achieve roaming (such as handover and cell reselection) between the cells of operator B and
operator C, the switch of InterPlmnHoAllowedIntraRat(BSC6900,BSC6910) must be enabled and
the neighboring cell relations must be configured.
Figure 3-14 Coexistence of multiple operators
3.3 Mobility Control and Service Differentiation

This section describes the principles of WRFD-02130403 Mobility Control and Service Differentiation.
3.3.1 Mobile Control

If an inter-PLMN handover is performed, the cell resources of one operator may be occupied by the
UEs of other operators and the charging is affected. To ensure the interests of operators, inter-PLMN
handover is generally prohibited.
If UEs are expected to be handed over between cells of different operators for load balancing
purposes, you can
set InterPlmnHoAllowedInterRat(BSC6900,BSC6910)and InterPlmnHoAllowedIntraRat(BSC6900
,BSC6910) to YES to allow the inter-PLMN inter-RAT and intra-RAT handovers.
3.3.2 Service Differentiation

In a RAN sharing network, you can set licenses and parameters to deploy features that are
independently used by different operators to achieve service differentiation.
A shared RNC has only one RNC license file. However, you can run the SET License command to
allocate different resource control items and function control items to different operators. In this way,
different operators are enabled with different capacities and features. For the license allocation mode,
see License Management Feature Parameter Description.
A RAN parameter can be of cell-, NodeB-, RNC-, or operator-level. However, only cell- and operator-
level parameters can enable different features for different operators. The following table lists the
mapping between some operator-dedicated features and parameters.
Table 3-1 Mapping between some operator-dedicated features and parameters
Parameter Description Parameter Example
Level
RNC RNC-level parameters are shared by all SET UCORRMALGOSWITCH:
operators and cannot be independently HoSwitch=HO_INTER_RAT_PS_OUT_
configured by operators.
Parameter Description Parameter Example
Level
Cell The cells of different operators are independent MOD UCELLALGOSWITCH: CellId=1
of each other. Cell-level parameters can enable NBMLdcAlgoSwitch=INTRA_FREQUE
different features for different cells. 1;
Operator Operator-level parameters can enable different SET UOPERATORCFGPARA: CnOpInd

features for different operators. CsNriCfgMode=SUPP_IUFLEX,
NodeB NodeB-level parameters are shared by all MOD UNODEB: IDTYPE=BYID, Node
operators and cannot be independently TRANSDELAY=600, SATELLITEIND=
configured by operators.
3.4 License Management

This section describes the WRFD-02130404 Independent License Control feature. Independent
License Control means that, in a RAN sharing network, operators can use licenses to control
deployment of different features and configuration of different capacities on RNCs and NodeBs based
on actual needs.
An RNC can be shared by a maximum of four operators. There is still one RNC license and one
NodeB license for a shared RAN. Licenses are classified into function control items and resource
control items. The RNC license control items can be allocated to different operators using the SET
LICENSE command. The NodeB license control items can be allocated to different operators through
the U2000. In this way, different capacities and features are enabled for operators.
Figure 3-15 shows the principles of RAN Sharing license management. For details
about RAN Sharing license management, see the "License Control for Multiple Operators" section
in License Management Feature Parameter Description.
Figure 3-15 Principles of RAN Sharing license management
3.5 Operation and Maintenance
This section describes the WRFD-02130405 Independent Cell-level FM/PM/CM feature.
OM Architecture
The OM architecture of a RAN sharing network mainly consists of the RAN, U2000, and each
operator's NMS. The RAN and U2000 are shared by operators, and the NMSs and northbound
interfaces (NBIs) are dedicated to each operator. The U2000 provides a secure and efficient OM
solution for a RAN sharing network. The U2000, through the northbound interface, provides required
configuration data, alarm data, and performance data to an operator's NMS based on the role of the
operator. This is to effectively manage the privacy, independence, and sharing of network resources
and data specific to operators' different requirements.
As shown in Figure 3-16, BTS X, BTS Y, and BTS Z, shared by operators A and B, consist of
a sharing network. A third party (called Jointer) is responsible for the OM of the sharing network.
Figure 3-16 OM architecture
BTS Y is shared by operators A and B, BTS X is dedicated to A, and BTS Z is dedicated to B. The
data sheet obtained from the upper-layer NMSs of operators A and B shows that each operator,
except Jointer, can only obtain its own cell-level data.
Alarm data and performance data is the basis of network maintenance, and configuration data is
fundamental to a network. Therefore, for a RAN sharing network, the configuration management
solution is different from the performance/alarm management solution. The U2000 provides functions
of importing and exporting radio configuration parameters on a per operator basis, so that each
operator can view and modify its own radio configuration parameters. Even if each operator modifies
its private parameters, the integrity and validity of these parameters can be ensured globally.
Data Type for FM, PM, and CM
When RAN Sharing is applied, the FM, PM, and CM data on Itf-N is classified into two types:
Operator dedicated data
Operator dedicated data refers to cell-level FM, PM, and CM data. It is only related to a specific
operator and is distributed to the operator's NMS on Itf-N.
Operator shared data
Operator shared data refers to the other FM, PM, and CM data. It is related to all operators.
Setting Principles of OM Modes
A RAN sharing network generally has two OM modes: Joint and Rent.
In Joint mode, multiple operators provide devices and spectra to form a shared network, and one of
the operators or a third party (called Jointer) is responsible for the OM of the shared network. In Rent
mode, an operator provides devices and spectra and rents these resources to other operators. The
operator that provides devices and spectra (called Renter) is responsible for the OM of the shared
network. In both modes, NEs may be dedicated to an operator.
In these modes, Jointer and Renter have the U2000 operation rights and are responsible for the OM
of the shared network. Different operation rights should be granted to each operator based on its roles
and responsibilities of operators involved in network sharing. The U2000, based on the role of an
operator, provides the required configuration data, alarm data, and performance data to the operator's
OSS through the NBI.
Setting Principles of Operator Roles
The U2000 distinguishes data based on the operator to which the NE management object belongs,
regardless of whether carriers are dedicated or common. The difference is that cells belong to only
one operator in the dedicated carrier solution, but belong to multiple operators in the common carrier
solution. Based on an in-depth analysis of application scenarios, the U2000 allocates operation rights
to three roles: Jointer, Renter, and Other operator.
For a dedicated NE, its home operator can obtain all the performance and alarm data of this NE
regardless of which role this operator is set to. For non-home operators of a dedicated NE or for a
shared NE, the U2000 allocates different operation rights to the three roles:
Jointer
Can obtain all the alarm data and performance data of all shared and dedicated NEs,
including both cell-level and non-cell-level.
Renter
Can obtain the cell-level alarm data and performance data of the operator and the non-cell-
level alarm data and performance data of all shared and dedicated NEs.
Other operator, including Common-Included and Common-Excluded
Other operator (Common-Included) can obtain the cell-level alarm data and performance
data of the operator and the non-cell-level alarm data and performance data of the shared
and dedicated NEs of the operator.
Other operator (Common-Excluded) can obtain the cell-level alarm data and performance
data of the operator and the non-cell-level alarm data and performance data of the
dedicated NEs of the operator.
Northbound User Management
Northbound user management is applied when the NMSs of different operators use the northbound
interface (NBI) at the same time. You can use the OSS self-maintenance unit (OSMU) of
the U2000 to add, modify, and delete northbound user and operator information and to manage
northbound user and operator rights.
Log in to the OSMU of the U2000, access the northbound user management page, and set the
information about operators and NMS users. In the Set Operator Information area, you can add,
modify, and delete operators. In the Set NMS User Information area, you can add, modify, and
delete NMS users.
For detailed operations, see U2000 Northbound Interface Developer Guide.
Northbound Interface Management
After setting the operator and northbound user information, the NMS of each operator can only view
and modify the configuration, performance, and alarm data of its own resources over the NBI.
Operators' resources are managed by operator indexes, northbound operator codes, and distribution
policies that are configured by NEs.
For detailed operations, see U2000 Northbound Interface Developer Guide.
4 Engineering Guidelines
The following describes RAN Sharing function switch, mobile control switch, typical networking
modes, and hardware configurations.
4.1 WRFD-021304 RAN Sharing Introduction Package
4.1.1 When to Use WRFD-021304 RAN Sharing Introduction Package

This feature is recommended if multiple operators want to share RAN equipment to reduce network
construction costs and want to keep dedicated core networks and spectrum resources.
4.1.2 Deployment
Other Features
This feature cannot be used together with the WRFD-021311 MOCN Introduction Package feature.
Hardware
RNC interface boards, NodeB baseband processing units, and RRUs are shared by operators to
improve resource utilization and reduce CAPEX. The configuration for RAN Sharing is the same
as that for scenarios in which an operator has multiple carriers. For details, see the
corresponding technical description documents.
Whether RRUs can be shared by operators depends on whether the RRU model meets multiple
operators' frequency bandwidth and power.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
Feature ID Feature Name License Control Item License Control Item

ID Name
WRFD-021304 RAN SharingIntroduction LQW1RANSH01RESE RAN SharingIntroduction BSC6

Package Package (per Erl)
WRFD-021304 RAN SharingIntroduction LQW1RANSH01RESM RAN SharingIntroduction BSC6

Package Package (per Mbps)
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the "License Allocation for Multiple Operators"
parameter.
Method 1#: It is recommended that the license allocation proportion of a feature be consistent with
that of the capacity license item "Voice Erlang-Erlang." You can run the RNC MML command SET
LICENSE with the FeatureResAssignMode parameter set to AutoAssign for automatic allocation or
with the FeatureResAssignModeparameter set to ManualAssign and license-rated parameters
specified for manual allocation.
NOTE:
If FeatureResAssignMode is set to AutoAssign, the licensed values of the control items will be
allocated for the primary and secondary operators in the same proportion of the associated license
control items (CSERLANG, PSTHROUGHPU, HSDPATHROUGHPUT, HSUPATHROUGHPUT, and
MBMSTHROUGHPUT). Example:
SET LICENSE: SETOBJECT=UMTS, OperatorType=PRIM, CNOPERATORINDEX=0,
FeatureResAssignMode=AutoAssign, CSERLANG=35000, PSTHROUGHPUT=10000000,
HSDPATHROUGHPUT=10000000, HSUPATHROUGHPUT=10000000,
MBMSTHROUGHPUT=10000000;
SET LICENSE: SETOBJECT=UMTS, OperatorType=SEC, CNOPERATORINDEX=1,
FeatureResAssignMode=AutoAssign, CSERLANG=15000, PSTHROUGHPUT=8000000,
HSDPATHROUGHPUT=8000000, HSUPATHROUGHPUT=8000000,
MBMSTHROUGHPUT=8000000;
Method 2#: It is recommended that the license allocation proportion of a feature be consistent with
that of the capacity license item "PS throughput only-kbps." You can run the RNC MML
command SET LICENSE with the FeatureResAssignMode parameter set to AutoAssign for
automatic allocation or with the FeatureResAssignMode parameter set to ManualAssign and
license-rated parameters specified for manual allocation.
The license of RAN Sharing Introduction Package is mutually exclusive with that of MOCN
Introduction Package. That is, these licenses cannot be activated at the same time. If the license
of RAN Sharing Introduction Package is activated, run the RNC MML command SET LICENSE to
deactivate the license of MOCN Introduction Package, that is, to deselect
the MOCN_PACKAGE check box under the FUNCTIONSWITCH4 parameter.
Other Requirements
None

Table 4-1 lists the data to prepare before activating WRFD-021304 RAN Sharing Introduction
Package.
Table 4-1 Data Preparation
Parameter Name Parameter ID Setting No
RAN Sharing Support RANSharingSupport(BSC6900,BSC6910) Set this parameter to YES.
Operator Type OperatorType(BSC6900,BSC6910) Set this parameter based on wh

the sharing operator is a primar
operator.
Cn Operator Name CnOperatorName(BSC6900,BSC6910) The value of this parameter mu
Cn Operator Group Index CnOpGrpIndex(BSC6900,BSC6910) The value of this parameter mu
Operator Number CnOpNum(BSC6900,BSC6910) The value of this parameter mu

Parameter Name Parameter ID Setting No
Operator 1 Index CnOpIndex1(BSC6900,BSC6910) The value of this parameter mu
Operator Name CnOpGrpName(BSC6900,BSC6910) The value of this parameter mu
OSP name NAME(BSC6900,BSC6910) Set this parameter based on the

among operators. The value of
unique.
OSP index SPX(BSC6900,BSC6910) Set this parameter based on the

unique.
DSP name NAME(BSC6900,BSC6910) Set this parameter based on the

unique.
DSP index DPX(BSC6900,BSC6910) Set this parameter based on the

unique.
OSP index SPX(BSC6900,BSC6910) Set this parameter based on the

unique.
Cn Operator Index CnOpIndex(BSC6900,BSC6910) The value of this parameter mu
CN node ID CNId(BSC6900,BSC6910) Set this parameter based on the

unique.
Sharing Type Of NodeB SharingType(BSC6900,BSC6910) Set this parameter to DEDICA

or RANSHARING(RAN Shari
whether the NodeB is to be sha
4.1.2.3 Activation
Using MML Commands
1. Run the RNC MML command SET UOPERATORSHARINGMODE to

set RANSharingSupport(BSC6900,BSC6910) to YES to enable the RAN sharingswitch.
2. Run the RNC MML command ADD UCNOPERATOR to
set OperatorType(BSC6900,BSC6910) for each operator.
3. Run the RNC MML command ADD UCNOPERGROUP to configure an operator group for each
operator and set the following parameters for each operator
group: CnOpGrpIndex(BSC6900,BSC6910), CnOpNum(BSC6900,BSC6910), CnOpIndex1(
BSC6900,BSC6910), and CnOpGrpName(BSC6900,BSC6910).
4. Run the RNC MML command ADD OPC to configure the originating signaling point (OSP) for
the primary operator and for each of the secondary operators.
NOTE:
The OSPs and network IDs of the primary and secondary operators can be the same or
different.
If the network IDs of the primary and secondary operators are the same, "OSP code bits"
must be the same and "OSP code" must be different.
If the network IDs of the primary and secondary operators are different, "OSP code bits"
can be different.
5. Run the RNC MML command ADD N7DPC to configure the destination signaling point (DSP)
for the primary operator and for each of the secondary operators.
6. Configure Iu data for the primary operator and for each of the secondary operators.
7. Run the RNC MML command ADD UCNNODE to add CN nodes for the primary operator and
for each of the secondary operators.
8. Run the RNC MML command ADD UNODEB to
set SharingType(BSC6900,BSC6910) to DEDICATED(Dedicated) or RANSHARING(RAN Sh
aring) to add a dedicated or shared NodeB.
9. Run the RNC MML command ADD ULAC, ADD URAC, ADD USAC, and ADD UURA to set
the LAC, RAC, SAC, and URA for the primary operator and for each of the secondary
operators.
10. Run the RNC MML command ADD UCELLQUICKSETUP to add a dedicated cell.
NOTE:
There are two types of RAN sharing:
NodeBs are independently deployed by operators.
NodeBs are shared by operators and cells are not shared by operators.
After a cell is added or the UARFCN is changed, you need to verify that the UARFCN used by
the cell is in the allowed range of the NodeB license. Otherwise, you must issue a new NodeB
license on the U2000.
If an operator's cells have all been removed from a NodeB, manually reclaim the NodeB license
on the U2000 before performing license operations. If the entire NodeB has been removed from
the U2000, there is no need to reclaim the NodeB license.
MML Command Examples
//Activating RAN Sharing Introduction Package

//Setting the operator sharing mode
SET UOPERATORSHARINGMODE: RANSharingSupport=YES,
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
//Adding a primary operator
ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502",
MNC="10", CnOpIndex=0;
//Adding a secondary operator
ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310",
MNC="30", CnOpIndex=1;
//Adding an operator group for the primary operator
ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE,
CnOpIndex1=0;
//Adding an operator group for the secondary operator
ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE,
CnOpIndex1=1;
//Configuring the OSP for the primary operator
ADD OPC: NAME="PRIM", SPX=0, NI=INT, SPCBITS=BIT14, SPDF=WNF, SPC=111;
//Configuring the OSP for a secondary operator
ADD OPC: NAME="SEC", SPX=1, NI=NAT, SPCBITS=BIT24, SPDF=WNF, SPC=222;
//Configuring the DSP for the primary operator
ADD N7DPC: NAME="PRIMCS", DPX=0, SPX=0, SPDF=WNF, DPC=333, DPCT=IUCS,
BEARTYPE=M3UA;
ADD N7DPC: NAME="PRIMPS", DPX=1, SPX=0, SPDF=WNF, DPC=444, DPCT=IUPS,
BEARTYPE=M3UA;
//Configuring the DSP for a secondary operator
ADD N7DPC: NAME="PRIMCS", DPX=2, SPX=1, SPDF=WNF, DPC=555, DPCT=IUCS,
BEARTYPE=M3UA;
ADD N7DPC: NAME="PRIMPS", DPX=3, SPX=1, SPDF=WNF, DPC=666, DPCT=IUPS,
BEARTYPE=M3UA;
//Adding CN nodes for the primary operator
ADD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0,
CNProtclVer=R99, SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL,
AvailCap=60000, TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1,
Switch3GPP25415CR0125=OFF;
ADD UCNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=1,
AvailCap=60000;
//Adding CN nodes for a secondary operator
AvailCap=60000, TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1,
ADD UCNNODE: CnOpIndex=1, CNId=3, CNDomainId=PS_DOMAIN, Dpx=3,
AvailCap=60000;
//Adding a NodeB
ADD UNODEB: NodeBName="NodeB1", NodeBId=1, SRN=0, SN=0,
TnlBearerType=IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST,
SharingType=RANSharing;
//Adding the LAC, RAC, SAC, and URA for multiple operators
ADD ULAC:CNOPINDEX=0, LAC=H'2201, PLMNVALTAGMIN=1, PLMNVALTAGMAX=64;
ADD ULAC:CNOPINDEX=1, LAC=H'0001, PLMNVALTAGMIN=1, PLMNVALTAGMAX=2;
ADD URAC:LAC=H'0001, RAC=H'01, CNOPINDEX=1, PLMNVALTAGMIN=1,
PLMNVALTAGMAX=2;
ADD URAC:LAC=H'2201, RAC=H'00, CNOPINDEX=0, PLMNVALTAGMIN=1,
PLMNVALTAGMAX=64;
ADD USAC:LAC=H'0001, SAC=H'0001, CNOPINDEX=1;
ADD USAC:LAC=H'2201, SAC=H'0000, CNOPINDEX=0;
ADD UURA:URAID=0, CNOPINDEX=0;
//Adding a cell
ADD UCELLQUICKSETUP: CELLID=1, CELLNAME="Cell1",
BANDIND=BAND1,PeerIsValid=VALID, PeerCellId=100,
CnOpGrpIndex=0,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, PSCRAMBCODE=0,
TCELL=CHIP256, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId =
6,URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7,
URA8=8, NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430,
PCPICHPOWER=330;
Using the CME
NOTE:
When configuring the feature on the CME, perform a single configuration first, and then perform a
batch modification if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
1. Configure a single object (such as a cell) on the CME.
Set parameters on the CME according to the operation sequence in Table 4-2. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
2. (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 while running the wizard to obtain online help.
Table 4-2 Configuring parameters on the CME
SN MO NE Parameter Name P
1 UOPERATORSHARINGMODE RNC RAN Sharing Support RANSharingSup

Set this parameter to YES.
2 UCNOPERATOR RNC Operator Type OperatorType(B

Operator Name CnOperatorNam
Cn Operator Index CnOpIndex(BSC
3 UCNOPERGROUP RNC Cn Operator Group Index CnOpGrpIndex(
Operator Number CnOpNum(BSC
Operator 1 Index CnOpIndex1(BS
Cn Operator Group Name CnOpGrpName
4 OPC RNC OSP name NAME(BSC6900
OSP index SPX(BSC6900,B
5 N7DPC RNC DSP name NAME(BSC6900
DSP index DPX(BSC6900,B
OSP index SPX(BSC6900,B
6 UCNNODE RNC Cn Operator Index CnOpIndex(BSC
CN node ID CNId(BSC6900,
7 UNODEB RNC Sharing Type Of NodeB SharingType(BS
8 Right-click RNC and choose ADD RNC None None
UMTS Cell

This feature is successfully activated if the following conditions are met:
The CNs of primary and secondary operators are working properly.
Cells can be normally set up for primary and secondary operators.
The identifier of the primary or secondary operator can be displayed on the UE.
CS/PS services can be normally set up.
Using MML Commands

set RANSharingSupport(BSC6900,BSC6910) to NO to disable the RAN sharingswitch.
2. Run the RNC MML command MOD UNODEB to set Sharing Type Of
NodeB to DEDICATED(Dedicated).
//Deactivating RAN Sharing Introduction Package

//Changing the NodeB sharing mode to dedicated
MOD UNODEB: NodeBName="NodeB1", NodeBId=1, SRN=0, SN=0,
TnlBearerType=IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST,
SharingType=Dedicated, CnOpIndex=0;
//Setting the operator sharing mode
SET UOPERATORSHARINGMODE: RANSharingSupport=NO;
Using the CME
NOTE:
Guide.
SN MO NE Parameter Name Param
1 UOPERATORSHARINGMODE RNC RAN Sharing Support RANSharingSuppo

Set this parameter to NO.
2 UNODEB RNC Sharing Type Of NodeB SharingType(BSC6

Set this parameter to
DEDICATED(Dedicated).
Use the VS.CSLoad.Erlang.Equiv.PLMN.RNC(BSC6900,BSC6910) counter to measure the
equivalent Erlang values of all services in the CS domain of the RNC for each operator.
Use the VS.R99PSLoad.DLThruput.PLMN.RNC(BSC6900,BSC6910) counter to measure the
downlink traffic of all R99 services in the PS domain of the RNC for each operator.
None
4.2 WRFD-02130401 Dedicated Carrier for Each Operator

WRFD-021304 RAN Sharing Introduction Package is a dedicated carrier solution. When the WRFD-
021304 RAN Sharing Introduction Package feature is activated, the optional feature WRFD-02130401
Dedicated Carrier for Each Operator is activated at the same time.
For details about how to activate, verify, and deactivate WRFD-02130401 Dedicated Carrier for Each
Operator, see 4.1 WRFD-021304 RAN Sharing Introduction Package.
4.3 WRFD-02130402 Flexible Network Architecture

This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402
Flexible Network Architecture.
4.3.1 When to Use WRFD-02130402 Flexible Network Architecture

Enable this feature when an operator needs to deploy a dedicated NodeB or a sharing operator
requires the coexistence of a shared network and an existing dedicated network.
4.3.2 Deployment
Other Features
The WRFD-021304 RAN Sharing Introduction Package feature has been activated.
Hardware
RNC interface boards, NodeB baseband processing units, and RRUs are shared by operators to
improve resource utilization and reduce CAPEX. The configuration for RAN Sharing is the same
as that for scenarios in which an operator has multiple carriers. For details, see 3900 Series
Base Station Technical Description.
Whether RRUs can be shared by operators depends on whether the RRU model meets multiple
operators' frequency bandwidth and power.
License
This feature is controlled by the license for the WRFD-021304 RAN Sharing Introduction Package
feature. For details about this license, see 4.1.2.1 Requirements.
Other Requirements
None

Flexible Deployment on Iu Interface
On a RAN sharing network, different operators can deploy the Iu Flex feature independently. For data
preparation, see the WRFD-021302 Iu Flex feature in Iu Flex Feature Parameter Description.
Flexible Deployment on Iu-BC Interface
On a RAN sharing network, each operator has only one dedicated CBC. The Iu-BC interface is
dedicated to each operator. Different operators can deploy the Cell Broadcast Service feature
independently. For data preparation, see the WRFD-011000 Cell Broadcast Service feature in CBS
Feature Parameter Description.
Flexible Deployment on Iub Interface
Table 4-4 lists the data to prepare before activating WRFD-02130402 Flexible Network Architecture.
Parameter Name Parameter ID Setting
Sharing Type Of NodeB RANSharingSupport(BSC6900,BSC6910) Set this parameter to DEDI
or RANSHARING(RAN S
whether the NodeB is to be
Flexible Deployment on Iur Interface
A shared RNC can be connected to both dedicated and shared RNCs. The Iur interface configuration
operations are the same for dedicated and shared RNCs. For data preparation, see BSC6900 UMTS
Initial Configuration Guide and BSC6910 UMTS Initial Configuration Guide.
4.3.2.3 Activation
Flexible Deployment on Iu Interface
On a RAN sharing network, different operators can deploy the Iu Flex feature independently. For the
activation procedure, see the WRFD-021302 Iu Flex feature in Iu Flex Feature Parameter Description.
Flexible Deployment on Iu-BC Interface
On a RAN sharing network, each operator has only one dedicated CBC. The Iu-BC interface is
dedicated to each operator. Different operators can deploy the Cell Broadcast Service feature
independently. For the activation procedure, see the WRFD-011000 Cell Broadcast Service feature
in CBS Feature Parameter Description.
Flexible Deployment on Iub Interface
A shared RNC can be connected to both dedicated and shared NodeBs. Run the RNC MML
command ADD UNODEB to set Sharing Type Of
NodeB to DEDICATED(Dedicated) or RANSHARING(RAN Sharing), to add a dedicated or shared
NodeB.
Flexible Deployment on Iur Interface
A shared RNC can be connected to both dedicated and shared RNCs. The Iur interface configuration
operations are the same for dedicated and shared RNCs.

To verify flexible deployment on the Iu interface, see the WRFD-021302 Iu Flex feature in Iu Flex
To verify flexible deployment on the Iu-BC interface, see the WRFD-011000 Cell Broadcast Service
feature in CBS Feature Parameter Description.
To verify flexible deployment on the Iur interface, see BSC6900 UMTS Initial Configuration
Guide and BSC6910 UMTS Initial Configuration Guide.
To verify flexible deployment on the Iub interface, run the Lst UNodeB command to query the
NodeB sharing type.
To deactivate flexible deployment on the Iu interface, see the WRFD-021302 Iu Flex feature in Iu Flex
To deactivate flexible deployment on the Iu-BC interface, see the WRFD-011000 Cell Broadcast
Service feature in CBS Feature Parameter Description.
To deactivate flexible deployment on the Iur interface, see BSC6900 UMTS Initial Configuration
Guide and BSC6910 UMTS Initial Configuration Guide.
To deactivate flexible deployment on the Iub interface, run the RNC MML command MOD
UNODEB to set Sharing Type Of
NodeB to DEDICATED(Dedicated) or RANSHARING(RAN Sharing).

None
None
4.4 Single CN With Multi-PLMN IDs
4.4.1 When to Use Single CN With Multi-PLMN IDs

In the RAN sharing scenario, activate this function if the customer requires multiple operators to share
the same CN node and requires the RAN to continue broadcasting multiple PLMN IDs in different
cells.
If the Single CN With Multi-PLMN IDs function is used in the common RAN sharing scenario, you are
advised to delete the configurations of secondary operators' CN nodes, in order to avoid data
redundancy.
4.4.2 Required Information

Before you deploy the Single CN With Multi-PLMN IDs function, obtain the following information:
Whether the MSC and SGSN are deployed with the Multi-PLMN feature
The PLMN ID of the primary operator and the DPC of the CN node
NOTE:
The primary operator's PLMN ID on the RNC side (Global RNC ID) must be consistent with that on
the CN side (Global CN ID). If not consistent, the messages delivered by the CN are lost.
4.4.3 Deployment
Requirements
Other Features
Before you activate this function, the WRFD-021304 RAN Sharing Introduction Package feature
must be configured and the inter-operator handover
switch InterPlmnHoAllowedIntraRat(UMTS BSC6900,UMTS BSC6910) must be turned off.
The MSC must support WSFD-110103 Multiple HPLMNs, and the SGSN must support WMFD-
160100 Multi-PLMN Function.
Hardware
None
License
This feature is controlled by the license for the WRFD-021304 RAN Sharing Introduction
Package feature. For details about this license, see 4.1.2.1 Requirements.
Data Preparation
Parameter Name Parameter ID

Single CN With Multi-PLMN MultiPLMNforSingleCNSwitch(BSC6900,BSC6910) Set this
IDs
Activation (Using MML Commands)
CN side: For the configuration of the Multi-PLMN or GWCN feature, see related CN documentation.
RAN side: See section 4.2.
1. (Optional) Delete the Iu interface and the mapping between the NRI and the CN node for the
secondary operator.
2. Run the RNC MML command SET UOPERATORSHARINGMODE to set the Single CN With
Multi-PLMN IDs Switch to ON.
Activation (Using the CME)
Turning on the Single CN With Multi-PLMN IDs Switch

Set the parameter described in the following table on the CME. For instructions on how to
perform the CME single configuration, see CME Single Configuration Operation Guide.
Configuring parameters on the CME
SN MO NE Parameter Param
Name
1 UOPERATORSHARINGMODE RNC Single CN MultiPLMNforSingleCNS

With Multi-
PLMN IDs
Switch (set to
YES)
Activation Observation
If the UEs of the primary and secondary operators can access their own cells and register with the
network successfully, and if the UEs can normally initiate CS and PS services, the Single CN With
Multi-PLMN IDs function has been successfully activated.
Deactivation (Using MML Commands)
To deactivate this function, perform the following steps:

1. (Optional) If the secondary operator's CN node is not configured, you need to configure the CN
node and NRI first.
2. Run the RNC MML command SET UOPERATORSHARINGMODE to set the Single CN With
Multi-PLMN IDs Switch to OFF.
Deactivation (Using the CME)
SN MO NE Parameter Param
Name
1 UOPERATORSHARINGMODE RNC Single CN MultiPLMNforSingleCNS

With Multi-
PLMN IDs
Switch (set to
No)
//Activating the Single CN With Multi-PLMN IDs function after RAN Sharing
Introduction Package is deployed
//(Optional) Deleting the Iu interface for the secondary operator
RMV UCNNODE: CnOpIndex=1, CNId=11;
//Turning on the Single CN With Multi-PLMN IDs Switch on the RNC
SET UOPERATORSHARINGMODE: RANSharingSupport=YES, MOCNSupport=NO,
MultiPLMNforSingleCNSwitch=ON, InterPlmnHoAllowedIntraRat=NO,
InterPlmnHoAllowedInterRat=NO;
//Deactivation procedure (If a secondary operator's CN node is not

configured, you need to configure the CN node and NRI first.)
//Configuring the Iu interface for a secondary operator
//Adding CN node 11 for a secondary operator
CNProtclVer=R5, SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL,
AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF,
//Setting parameters for a secondary operator
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_MOCN,
PsNriCfgMode=SUPP_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=1;
//Adding the mapping between CN node 11 and an NRI for a secondary operator
ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=11, NRI=600;
//Turning off the Single CN With Multi-PLMN IDs Switch on the RNC
SET UOPERATORSHARINGMODE: RANSharingSupport=YES, MOCNSupport=NO,
MultiPLMNforSingleCNSwitch=OFF, InterPlmnHoAllowedIntraRat=NO,
InterPlmnHoAllowedInterRat=NO;

None
None
4.5 WRFD-02130403 Mobility Control and Service Differentiation
This section describes how to activate, verify, and deactivate the optional feature WRFD-02130403
Mobility Control and Service Differentiation.
4.5.1 When to Use WRFD-02130403 Mobility Control and Service Differentiation

If UEs are expected to be handed over between cells of different operators for load balancing
purposes, you can enable the inter-PLMN handover switch. However, if this switch is turned on, the
cell resources of one operator may be occupied by the UEs of other operators and the charging is
affected. Generally, you are not advised to enable the inter-PLMN handover switch.
4.5.2 Deployment
Other Features
The WRFD-021304 RAN Sharing Introduction Package feature has been activated.
Hardware
None
License
This feature is controlled by the license for the WRFD-021304 RAN Sharing Introduction Package
feature. For details about this license, see 4.1.2.1 Requirements.
Other Requirements
None

Table 4-6 lists the data to prepare before activating WRFD-02130403 Mobility Control and Service
Differentiation.
Parameter Name Parameter ID Set
Intra RAT Inter Plmn Ho InterPlmnHoAllowedIntraRat(BSC6900,BSC6910) Set this parame
Allowed
Inter RAT Inter Plmn Ho InterPlmnHoAllowedInterRat(BSC6900,BSC6910) Set this parame

Allowed
4.5.2.3 Activation
Using MML Commands

set InterPlmnHoAllowedInterRat(BSC6900,BSC6910) and InterPlmnHoAllowedIntraRat(B
SC6900,BSC6910) to YES.
//Activating Mobility Control and Service Differentiation

InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES;
Using the CME

NOTE:
Set the parameter described in Table 4-7 on the CME. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.
press F1 on the wizard interface to obtain online help.
Table 4-7 Configuring the parameter on the CME
SN MO NE Parameter Name Para
1 UOPERATORSHARINGMODE RNC RAN Sharing Support RANSharingSupport(B

Intra RAT Inter Plmn Ho InterPlmnHoAllowedIn

Allowed
Inter RAT Inter Plmn Ho InterPlmnHoAllowedIn

Allowed

Configure the cells that belong to different operators as intra-frequency/inter-frequency/inter-RAT
neighboring cells. If inter-PLMN intra-RAT handover and inter-PLMN inter-RAT handovers can be
implemented, this feature is successfully activated.
Using MML Commands
Run the RNC MML command SET

UOPERATORSHARINGMODE with InterPlmnHoAllowedInterRat(BSC6900,BSC6910) and InterPl
mnHoAllowedIntraRat(BSC6900,BSC6910) to NO.
//Deactivating Mobility Control and Service Differentiation

InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
Using the CME

NOTE:
Guide.
SN MO NE Parameter Name Param
1 UOPERATORSHARINGMODE RNC RAN Sharing Support RANSharingSupport(BS

Intra RAT Inter Plmn Ho InterPlmnHoAllowedIntr

Allowed
Inter RAT Inter Plmn Ho InterPlmnHoAllowedInte

Allowed

None.
None.
4.6 WRFD-02130404 Independent License Control

Independent License Control means that, in a RAN sharing network, operators can use licenses to
control deployment of different features and configuration of different capacities on RNCs and
NodeBs based on actual needs.
The RNC license can be allocated to different operators using the SET LICENSE command. The
NodeB license can be allocated to different operators through the U2000. For details
about RAN Sharing license management, see the "License Control for Multiple Operators" section
in License Management Feature Parameter Description.
The license delivered by the U2000 to the NodeB carries the operator's frequency information.
Therefore, in the multi-operator sharing scenario, the license should be re-delivered on the U2000 if
cell frequencies are modified on the RNC, which ensures the frequencies in the license are consistent
with the configured frequencies.
4.7 WRFD-02130406 Transmission Recourse Sharing on Iub/Iur Interface
Transmission Recourse Sharing on Iub/Iur Interface means that transmission resources are shared
among operators over the Iub and Iur interfaces. For details about how to activate, verify, and
deactivate this feature, see 4.3 WRFD-02130402 Flexible Network Architecture.
5 Parameters
Table 5-1 Parameters
Parameter ID NE MML Feat Feature Description
Command ure Name
ID
CnOpIndex BSC ADD WR Dedicated Meaning:
690 UCNOPERATO FD- Carrier for Represent an index for a CN
0 R 0213 Each operator.
MOD 0401 Operator If "OperatorType" is set to
UCNOPERATO WR MOCN PRIM, the value range of
R FD- Introduction "Operator Index" is 0~3.
RMV 0213 Package If "OperatorType" is set to
UCNOPERATO 11 Routing SEC, the value range of
R WR Roaming "Operator Index" is 0~3.
FD- UEs in If "OperatorType" is set to
0213 Proportion OUTER, the value range of
1106 RAN Sharin "Operator Index" is 5~31.
WR gIntroductio If "OperatorType" is set to
FD- n Package COMM, the value range of
0213 "Operator Index" is 5~31.
04
If "OperatorType" is set to
ICR, the value range of
"Operator Index" is 5~31.
GUI Value Range: 0~3;5~31
Unit: None
Actual Value Range: 0~3,
5~31
Default Value: None
CnOpIndex BSC ADD WR Dedicated Meaning:

691 UCNOPERATO FD- Carrier for Represent an index for a CN
0 R 0213 Each operator.
MOD 0401 Operator If "OperatorType" is set to
UCNOPERATO WR MOCN PRIM, the value range of
R FD- Introduction "Operator Index" is 0~3.
RMV 0213 Package If "OperatorType" is set to
UCNOPERATO 11 Routing SEC, the value range of
R WR Roaming "Operator Index" is 0~3.
FD- UEs in If "OperatorType" is set to
0213 Proportion OUTER, the value range of
1106 "Operator Index" is 5~31.
Command ure Name
ID
WR RAN Sharin If "OperatorType" is set to
FD- gIntroductio COMM, the value range of
0213 n Package "Operator Index" is 5~31.
04 If "OperatorType" is set to
ICR, the value range of
"Operator Index" is 5~31.
GUI Value Range: 0~3;5~31
Unit: None
Actual Value Range: 0~3,
5~31
Default Value: None
OperatorType BSC ADD WR 3GPP R9 Meaning:

690 UCNOPERATO FD- Specification Identify operator type,as
0 R 0101 s follows:
MOD 01 Dedicated Primary operator:
UCNOPERATO WR Carrier for Each RAN system has only
R FD- Each one primary operator. The
0213 Operator primary operator owns all or
0401 MOCN part of the resources of
WR Introduction the RAN system. The license
FD- Package of the primary operator
0213 controls the features and
11 functions supported by
the RAN system.
Secondary operator:
Each RAN system can have a
maximum of three secondary
operators. A secondary
operator owns part of the
resources of the RAN system.
The license of the secondary
operator controls the
functions and features
supported by the secondary
operator.
Outer Operator: In order to
support mobility between two
RNCs, we define the operator
switched over to the target
RNC as an outer operator.
The outer operator is not a
primary or secondary operator
of the source RNC.
Command ure Name
ID
Common operator: PLMN-id
indicated in the system
broadcast information as
defined for conventional
networks, which non-
supporting UEs understand as
the serving operator. If there
are multiple operators in the
operator group to which the
cell belongs, you are advised
to configure the operators as
common operators.
ICR operator: In a partnership
between a 2G network
operator and a 3G network
operator, the latter provides
3G services to the 2G
network operator. In this case,
the 2G network operator is an
ICR(Intra Circle Roaming)
operator.
GUI Value Range:
PRIM(Primary Operator),
SEC(Secondary Operator),
OUTER(Outer Operator),
COMM(Common Operator),
ICR(ICR Operator)
Unit: None
Actual Value Range: PRIM,
SEC, OUTER, COMM, ICR
Default Value: None
OperatorType BSC ADD WR 3GPP R9 Meaning:

691 UCNOPERATO FD- Specification Identify operator type,as
0 R 0101 s follows:
MOD 01 Dedicated Primary operator:
UCNOPERATO WR Carrier for Each RAN system has only
R FD- Each one primary operator. The
0213 Operator primary operator owns all or
0401 MOCN part of the resources of
WR Introduction the RAN system. The license
FD- Package of the primary operator
0213 controls the features and
11 functions supported by
the RAN system.
Command ure Name
ID
Secondary operator:
Each RAN system can have a
maximum of three secondary
operators. A secondary
operator owns part of the
resources of the RAN system.
The license of the secondary
operator controls the
functions and features
supported by the secondary
operator.
Outer Operator: In order to
support mobility between two
RNCs, we define the operator
switched over to the target
RNC as an outer operator.
The outer operator is not a
of the source RNC.
Common operator: PLMN-id
indicated in the system
broadcast information as
defined for conventional
networks, which non-
supporting UEs understand as
the serving operator. If there
are multiple operators in the
operator group to which the
cell belongs, you are advised
to configure the operators as
common operators.
ICR operator: In a partnership
between a 2G network
operator and a 3G network
operator, the latter provides
3G services to the 2G
network operator. In this case,
the 2G network operator is an
ICR(Intra Circle Roaming)
operator.
GUI Value Range:
PRIM(Primary Operator),
SEC(Secondary Operator),
OUTER(Outer Operator),
Command ure Name
ID
COMM(Common Operator),
ICR(ICR Operator)
Unit: None
Actual Value Range: PRIM,
SEC, OUTER, COMM, ICR
Default Value: None
CnOpGrpIndex BSC ADD WR Dedicated Meaning: Represent an index

690 UCNOPERGRO FD- Carrier for for a Operator Group.
0 UP 0213 Each GUI Value Range: 0~31
MOD 0401 Operator Unit: None
UCNOPERGRO WR MOCN Actual Value Range: 0~31
UP FD- Introduction
Default Value: None
RMV 0213 Package
UCNOPERGRO 11 Routing
UP WR Roaming
FD- UEs in
0213 Proportion
1106
CnOpGrpIndex BSC ADD WR Dedicated Meaning: Represent an index

691 UCNOPERGRO FD- Carrier for for a Operator Group.
UCNOPERGRO WR MOCN Actual Value Range: 0~31
UP FD- Introduction
Default Value: None
RMV 0213 Package
UCNOPERGRO 11 Routing
UP WR Roaming
FD- UEs in
0213 Proportion
1106
CnOpIndex BSC ADD WR Dedicated Meaning: Represent an index
690 UCNNODE FD- Carrier for for a CN operator.
0 MOD 0213 Each GUI Value Range: 0~3
UCNNODE 0401 Operator Unit: None
RMV WR MOCN Actual Value Range: 0~3
UCNNODE FD- Introduction
Default Value: None
0213 Package
11 Warning of
WR Disaster
FD- Iu Flex
0201
27
Command ure Name
ID
WR RAN Sharin
FD- gIntroductio
0213 n Package
02
WR
FD-
0213
04
CnOpIndex BSC ADD WR Dedicated Meaning: Represent an index

691 UCNNODE FD- Carrier for for a CN operator.
0 MOD 0213 Each GUI Value Range: 0~3
UCNNODE 0401 Operator Unit: None
RMV WR MOCN Actual Value Range: 0~3
UCNNODE FD- Introduction
Default Value: None
0213 Package
11 Warning of
WR Disaster
FD- Iu Flex
0201 RAN Sharin
27 gIntroductio
WR n Package
FD-
0213
02
WR
FD-
0213
04
CNId BSC ADD WR 3GPP R9 Meaning:

690 UCNNODE FD- Specification Identifying a CN Node. When
0 MOD 0101 s the Iu-Flex feature is enabled,
UCNNODE 01 MOCN a maximum of 32 CN nodes
RMV WR Introduction can be configured in each CN
UCNNODE FD- Package domain, either the CS domain
0213 Iu Flex or the PS domain. CN nodes
11 are uniquely but not
WR necessarily consecutively
FD- numbered within a RNC. For
0213 example, set the number of a
02 CN node to 0 and that of
another CN node to 2.
Note:
Command ure Name
ID
Although the number of a CN
node ranges from 0 to 4095, a
maximum of 64 CN nodes
can be configured.
GUI Value Range: 0~4095
Unit: None
Actual Value Range: 0~4095
Default Value: None
CNId BSC ADD WR 3GPP R9 Meaning:

691 UCNNODE FD- Specification Identifying a CN Node. When
0 MOD 0101 s the Iu-Flex feature is enabled,
UCNNODE 01 MOCN a maximum of 64 CN nodes
RMV WR Introduction can be configured in each CN
UCNNODE FD- Package domain, either the CS domain
0213 Iu Flex or the PS domain. CN nodes
11 are uniquely but not
WR necessarily consecutively
FD- numbered within a RNC. For
0213 example, set the number of a
02 CN node to 0 and that of
another CN node to 2.
Note:
Although the number of a CN
node ranges from 0 to 4095, a
maximum of 128 CN nodes
can be configured.
Unit: None
Default Value: None
InterPlmnHoAll BSC SET WR Dedicated Meaning: Whether intra-RAT

owedIntraRat 690 UOPERATORS FD- Carrier for inter-PLMN handovers are
0 HARINGMOD 0213 Each allowed.
E 0401 Operator GUI Value Range: NO, YES
WR MOCN Unit: None
FD- Introduction Actual Value Range: NO,
0213 Package YES
11 Mobility Default Value: NO
WR Control and
FD- Service
0213 Differentiati
0403 on
Command ure Name
ID
WR MOCN
FD- Mobility
0213 Management
1103 RAN Sharin
WR gIntroductio
FD- n Package
0213
04
InterPlmnHoAll BSC SET WR Dedicated Meaning: Whether intra-RAT

owedIntraRat 691 UOPERATORS FD- Carrier for inter-PLMN handovers are
WR MOCN Unit: None
0213 Package YES
WR Control and
FD- Service
0213 Differentiati
0403 on
WR MOCN
FD- Mobility
0213 Management
1103 RAN Sharin
WR gIntroductio
FD- n Package
0213
04
InterPlmnHoAll BSC SET WR Dedicated Meaning: Whether inter-RAT

owedInterRat 690 UOPERATORS FD- Carrier for inter-PLMN handovers are
WR MOCN Unit: None
0213 Package YES
WR Control and
FD- Service
0213 Differentiati
0403 on
WR MOCN
FD- Mobility
Management
Command ure Name
ID
0213 RAN Sharin
1103 gIntroductio
WR n Package
FD-
0213
04
InterPlmnHoAll BSC SET WR Dedicated Meaning: Whether inter-RAT

owedInterRat 691 UOPERATORS FD- Carrier for inter-PLMN handovers are
WR MOCN Unit: None
0213 Package YES
WR Control and
FD- Service
0213 Differentiati
0403 on
WR MOCN
FD- Mobility
0213 Management
1103 RAN Sharin
WR gIntroductio
FD- n Package
0213
04
RANSharingSu BSC SET WR Dedicated Meaning: Whether the RNC

pport 690 UOPERATORS FD- Carrier for supports the independent
0 HARINGMOD 0213 Each carrier RAN sharing function.
WR MOCN Unit: None
0213 Package YES
WR Control and
FD- Service
0213 Differentiati
0403 on
WR Carrier Shari
FD- ng by
0213 Operators
1101
Command ure Name
ID
WR RAN Sharin
FD- gIntroductio
0213 n Package
04
RANSharingSu BSC SET WR Dedicated Meaning: Whether the RNC

pport 691 UOPERATORS FD- Carrier for supports the independent
0 HARINGMOD 0213 Each carrier RAN sharing function.
WR MOCN Unit: None
0213 Package YES
WR Control and
FD- Service
0213 Differentiati
0403 on
WR Carrier Shari
FD- ng by
0213 Operators
1101 RAN Sharin
WR gIntroductio
FD- n Package
0213
04
CnOperatorNa BSC ADD WR Dedicated Meaning: Operator name.

me 690 UCNOPERATO FD- Carrier for This parameter uniquely
0 R 0213 Each identifies an operator in the
MOD 0401 Operator entire radio network
UCNOPERATO WR MOCN subsystem (RNS).
R FD- Introduction GUI Value Range: 1~31
0213 Package characters
11 RAN Sharin Unit: None
WR gIntroductio Actual Value Range: 1~31
FD- n Package characters
0213 Default Value: None
04
CnOperatorNa BSC ADD WR Dedicated Meaning: Operator name.

me 691 UCNOPERATO FD- Carrier for This parameter uniquely
0 R 0213 Each identifies an operator in the
MOD 0401 Operator entire radio network
UCNOPERATO WR subsystem (RNS).
R FD-
Command ure Name
ID
0213 MOCN GUI Value Range: 1~31
11 Introduction characters
WR Package Unit: None
FD- RAN Sharin Actual Value Range: 1~31
0213 gIntroductio characters
04 n Package Default Value: None
CnOpNum BSC ADD WR Dedicated Meaning: Identify Operator

690 UCNOPERGRO FD- Carrier for Number in Operator Group.
0 UP 0213 Each GUI Value Range:
MOD 0401 Operator ONE(One), TWO(Two),
UCNOPERGRO WR MOCN THREE(Three), FOUR(Four)
UP FD- Introduction Unit: None
0213 Package Actual Value Range: 1, 2, 3, 4
11 RAN Sharin Default Value: None
WR gIntroductio
FD- n Package
0213
04
CnOpNum BSC ADD WR Dedicated Meaning: Identify Operator

691 UCNOPERGRO FD- Carrier for Number in Operator Group.
0 UP 0213 Each GUI Value Range:
MOD 0401 Operator ONE(One), TWO(Two),
UCNOPERGRO WR MOCN THREE(Three), FOUR(Four)
UP FD- Introduction Unit: None
0213 Package Actual Value Range: 1, 2, 3, 4
11 RAN Sharin Default Value: None
WR gIntroductio
FD- n Package
0213
04
CnOpIndex1 BSC ADD WR Dedicated Meaning: Represent an index
690 UCNOPERGRO FD- Carrier for for a CN operator 1.
0 UP 0213 Each GUI Value Range: 0~3;5~31
UCNOPERGRO WR MOCN Actual Value Range: 0~3,
UP FD- Introduction 5~31
0213 Package
Default Value: None
11 RAN Sharin
WR gIntroductio
FD- n Package
0213
04
Command ure Name
ID
CnOpIndex1 BSC ADD WR Dedicated Meaning: Represent an index
691 UCNOPERGRO FD- Carrier for for a CN operator 1.
0 UP 0213 Each GUI Value Range: 0~3;5~31
UCNOPERGRO WR MOCN Actual Value Range: 0~3,
UP FD- Introduction 5~31
0213 Package
Default Value: None
11 RAN Sharin
WR gIntroductio
FD- n Package
0213
04
CnOpGrpName BSC ADD WR Dedicated Meaning: Cn Operator Group

690 UCNOPERGRO FD- Carrier for Name.
MOD 0401 Operator characters
UCNOPERGRO WR MOCN Unit: None
UP FD- Introduction Actual Value Range: 1~31
11
Default Value: None
CnOpGrpName BSC ADD WR Dedicated Meaning: Cn Operator Group

691 UCNOPERGRO FD- Carrier for Name.
MOD 0401 Operator characters
UCNOPERGRO WR MOCN Unit: None
UP FD- Introduction Actual Value Range: 1~31
11
Default Value: None
NAME BSC ADD OPC WR ATM Meaning: Name of the OSP.

690 MOD OPC FD- Transmissio GUI Value Range: 1~49
0 0503 n characters
01 Introduction Unit: None
Package
characters
Default Value: None
NAME BSC ADD OPC WR ATM Meaning: Name of the OSP.

691 MOD OPC FD- Transmissio GUI Value Range: 1~49
0 0503 n characters
01 Introduction Unit: None
Package
Command ure Name
ID
characters
Default Value: None
SPX BSC ADD OPC WR 3GPP R9 Meaning: Uniquely identifies

690 MOD OPC FD- Specification an OSP.
0 RMV OPC 0101 s GUI Value Range: 0~4
01 IP Unit: None
WR Transmissio Actual Value Range: 0~4
FD- n
Default Value: None
0504 Introduction
09 on Iu
WR Interface
FD- IP
0504 Transmissio
10 n
WR Introduction
FD- on Iur
0503 Interface
01 ATM
Transmissio
n
Introduction
Package
SPX BSC ADD OPC WR 3GPP R9 Meaning: Uniquely identifies

691 MOD OPC FD- Specification an OSP.
0 RMV OPC 0101 s GUI Value Range: 0~10
01 Iu/Iur IP Unit: None
FD- n Based on
Default Value: None
1502 Dynamic
44 Load
WR Balance
FD- ATM
0503 Transmissio
01 n
Introduction
Package
NAME BSC ADD N7DPC WR 3GPP R9 Meaning: The DSP must have
690 MOD N7DPC FD- Specification been configured. The DSP
0 0101 s name must be unique.
01 IP GUI Value Range: 1~49
Transmissio characters
Command ure Name
ID
WR n Unit: None
FD- Introduction Actual Value Range: 1~49
0504 on Iu characters
09 Interface Default Value: None
WR IP
FD- Transmissio
0504 n
10 Introduction
WR on Iur
FD- Interface
0503 ATM
01 Transmissio
n
Introduction
Package
NAME BSC ADD N7DPC WR 3GPP R9 Meaning: The DSP must have
691 MOD N7DPC FD- Specification been configured. The DSP
0 0101 s name must be unique.
01 Iu/Iur IP GUI Value Range: 1~49
WR Transmissio characters
FD- n Based on Unit: None
1502 Dynamic Actual Value Range: 1~49
44 Load characters
WR Balance
Default Value: None
FD- ATM
0503 Transmissio
01 n
Introduction
Package
DPX BSC ADD N7DPC WR 3GPP R9 Meaning: The DSP index

690 INH N7DPC FD- Specification uniquely identifies a DSP. A
0 MOD N7DPC 0101 s RNC supports a maximum of
01 187 DSPs, including the
RMV N7DPC
DSPs that are either directly
UIN N7DPC or indirectly connected to the
Originating Signaling Points
(OSPs). The number of the
DSP ranges from 0 to 186.
DSPs are uniquely but not
necessarily consecutively
numbered within a RNC by
using the DSP index. For
example, you can set the
number of an MSC signaling
Command ure Name
ID
point to 10 and that of another
MSC signaling point to 12.
Unit: None
Default Value: None
DPX BSC ADD N7DPC WR 3GPP R9 Meaning: The DSP index

691 INH N7DPC FD- Specification uniquely identifies a DSP. A
0 MOD N7DPC 0101 s RNC supports a maximum of
01 428 DSPs, including the
RMV N7DPC
DSPs that are either directly
UIN N7DPC or indirectly connected to the
Originating Signaling Points
(OSPs). The number of the
DSP ranges from 0 to 427.
DSPs are uniquely but not
necessarily consecutively
numbered within a RNC by
using the DSP index. For
example, you can set the
number of an MSC signaling
point to 10 and that of another
MSC signaling point to 12.
Unit: None
Default Value: None
SPX BSC ADD N7DPC WR 3GPP R9 Meaning: Uniquely identifies

690 FD- Specification an OSP.
0 0101 s GUI Value Range: 0~4
01 IP Unit: None
FD- n
Default Value: None
0504 Introduction
09 on Iu
WR Interface
FD- IP
0504 Transmissio
10 n
WR Introduction
FD- on Iur
Interface
Command ure Name
ID
0503 ATM
01 Transmissio
n
Introduction
Package
SPX BSC ADD N7DPC WR 3GPP R9 Meaning: Uniquely identifies

691 FD- Specification an OSP.
0 0101 s GUI Value Range: 0~10
01 Iu/Iur IP Unit: None
FD- n Based on
Default Value: None
1502 Dynamic
44 Load
WR Balance
FD- ATM
0503 Transmissio
01 n
Introduction
Package
SharingType BSC ADD UNODEB WR Dedicated Meaning:

690 MOD UNODEB FD- Carrier for NodeB sharing type. The
0 0213 Each Dedicated type indicates that
0401 Operator all cells under this NodeB
WR MOCN belong only to one non-ICR
FD- Introduction operator.
0213 Package The RAN Sharing type
11 Transmissio indicates that cells under this
WR n NodeB can belong to
FD- Recourse Sh different non-ICR operators
0213 aring on but each cell belongs to only
0406 Iub/Iur one non-ICR operator. The
Interface MOCN type indicates that
each cell under this NodeB
can belong to multiple non-
ICR operators.
Note that similar to MOCN-
enabled cells, cells under a
NodeB of the Dedicated
or RAN Sharing type can be
configured with multiple
operators. The operators,
however, must consist of the
Command ure Name
ID
and several ICR operators.
GUI Value Range:
DEDICATED(Dedicated), R
ANSHARING(RAN Sharing)
, MOCN(MOCN)
Unit: None
Actual Value Range:
Dedicated, RANSharing,
MOCN
Default Value: None
SharingType BSC ADD UNODEB WR Dedicated Meaning:

691 MOD UNODEB FD- Carrier for NodeB sharing type. The
0 0213 Each Dedicated type indicates that
0401 Operator all cells under this NodeB
WR MOCN belong only to one non-ICR
FD- Introduction operator.
0213 Package The RAN Sharing type
11 Transmissio indicates that cells under this
WR n NodeB can belong to
FD- Recourse Sh different non-ICR operators
0213 aring on but each cell belongs to only
0406 Iub/Iur one non-ICR operator. The
Interface MOCN type indicates that
each cell under this NodeB
can belong to multiple non-
ICR operators.
Note that similar to MOCN-
enabled cells, cells under a
NodeB of the Dedicated
or RAN Sharing type can be
configured with multiple
operators. The operators,
however, must consist of the
and several ICR operators.
GUI Value Range:
DEDICATED(Dedicated), R
ANSHARING(RAN Sharing)
, MOCN(MOCN)
Unit: None
Command ure Name
ID
Actual Value Range:
Dedicated, RANSharing,
MOCN
Default Value: None
MultiPLMNfor BSC SET WR MOCN Meaning:

SingleCNSwitc 690 UOPERATORS FD- Introduction Whether the RNC connecting
h 0 HARINGMOD 0213 Package only to the CN nodes of one
E 11 RAN Sharin operator supports the
WR gIntroductio broadcast of multiple public
FD- n Package land mobile network (PLMN)
0213 IDs.
04 When this parameter is set to
ON, the RNC routes the
service requests from UEs of
different operators to the CN
for processing.
When this parameter is set to
OFF, the RNC connecting
only to the CN nodes of one
operator does not support the
broadcast of multiple
PLMNs.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF,
ON
Default Value: OFF
MultiPLMNfor BSC SET WR MOCN Meaning:

SingleCNSwitc 691 UOPERATORS FD- Introduction Whether the RNC connecting
h 0 HARINGMOD 0213 Package only to the CN nodes of one
E 11 RAN Sharin operator supports the
WR gIntroductio broadcast of multiple public
FD- n Package land mobile network (PLMN)
0213 IDs.
04 When this parameter is set to
ON, the RNC routes the
service requests from UEs of
different operators to the CN
for processing.
When this parameter is set to
OFF, the RNC connecting
only to the CN nodes of one
Command ure Name
ID
operator does not support the
broadcast of multiple
PLMNs.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF,
ON
Default Value: OFF
6 Counters
Table 6-1 Counters
Count Counter Name Counter NE Featur Feature Name
er ID Descript e ID
ion
50332 VS.ULCE.Mean.Dedicated Average NodeB Multi- RAN SharingIntro
548 Dedicate mode: duction Package
d Uplink None Coverage
CE GSM: Expansion Under
None Interference
UMTS
:
WRFD
-
02130
4
WRFD
-
17121
2
LTE:
None
50332 VS.DLCE.Mean.Dedicated Average NodeB Multi- RAN SharingIntro

549 Dedicate mode: duction Package
d None
Downlin GSM:
k CE None
UMTS
:
WRFD
-
02130
4
er ID Descript e ID
ion
LTE:
None
50332 VS.ULCE.Mean.Shared Average NodeB Multi- RAN SharingIntro

550 Shared mode: duction Package
Uplink None Coverage
CE GSM: Expansion Under
None Interference
UMTS
:
WRFD
-
02130
4
WRFD
-
17121
2
LTE:
None
50332 VS.DLCE.Mean.Shared Average NodeB Multi- RAN SharingIntro

554 Shared mode: duction Package
Downlin None
k CE GSM:
None
UMTS
:
WRFD
-
02130
4
LTE:
None
50342 VS.ULCE.Max.Dedicated Maximu NodeB Multi- RAN SharingIntro

548 m mode: duction Package
Dedicate None Coverage
d Uplink GSM: Expansion Under
CE None Interference
UMTS
:
WRFD
-
er ID Descript e ID
ion
02130
4
WRFD
-
17121
2
LTE:
None
50342 VS.DLCE.Max.Dedicated Maximu NodeB Multi- RAN SharingIntro

Dedicate None
d GSM:
Downlin None
k CE UMTS
:
WRFD
-
02130
4
LTE:
None
50342 VS.ULCE.Max.Shared Maximu NodeB Multi- RAN SharingIntro

Shared None Coverage
Uplink GSM: Expansion Under
CE None Interference
UMTS
:
WRFD
-
02130
4
WRFD
-
17121
2
LTE:
None
50342 VS.DLCE.Max.Shared Maximu NodeB Multi- RAN SharingIntro

Shared None
er ID Descript e ID
ion
Downlin GSM:
k CE None
UMTS
:
WRFD
-
02130
4
LTE:
None
67192 VS.CSLoad.MaxErlang.Equiv.PLM Maximu BSC6 WRFD RAN SharingIntro

511 N.RNC m 900 - duction Package
equivale 02130 MOCN
nt CS 4 Introduction
Erlang WRFD Package
for RNC - Independent
per 02131 License Control
Operator 1
WRFD
-
02130
404
67192 VS.CSLoad.MaxErlang.Equiv.PLM Maximu BSC6 WRFD RAN SharingIntro

511 N.RNC m 910 - duction Package
equivale 02130 MOCN
nt CS 4 Introduction
Erlang WRFD Package
Operator 1
WRFD
-
02130
404
67193 VS.R99PSLoad.MaxULThruput.PL Maximu BSC6 WRFD RAN SharingIntro

010 MN.RNC m 900 - duction Package
Uplink 02130 MOCN
PS R99 4 Introduction
Traffic WRFD Package
Operator 1
er ID Descript e ID
ion
WRFD
-
02130
404
67193 VS.R99PSLoad.MaxULThruput.PL Maximu BSC6 WRFD RAN SharingIntro

Uplink 02130 MOCN
PS R99 4 Introduction
Traffic WRFD Package
Operator 1
WRFD
-
02130
404
67193 VS.R99PSLoad.MaxDLThruput.PL Maximu BSC6 WRFD RAN SharingIntro

Downlin 02130 MOCN
k PS 4 Introduction
R99 WRFD Package
Traffic - Independent
for RNC 02131 License Control
per 1
Operator WRFD
-
02130
404
67193 VS.R99PSLoad.MaxDLThruput.PL Maximu BSC6 WRFD RAN SharingIntro

Downlin 02130 MOCN
k PS 4 Introduction
R99 WRFD Package
per 1
Operator WRFD
-
02130
404
67193 VS.HSDPAPSLoad.MaxDLThruput Maximu BSC6 WRFD RAN SharingIntro

016 .PLMN.RNC m 900 - duction Package
er ID Descript e ID
ion
Downlin 02130 MOCN
k PS 4 Introduction
HSDPA WRFD Package
per 1
Operator WRFD
-
02130
404
67193 VS.HSDPAPSLoad.MaxDLThruput Maximu BSC6 WRFD RAN SharingIntro

Downlin 02130 MOCN
k PS 4 Introduction
HSDPA WRFD Package
per 1
Operator WRFD
-
02130
404
67193 VS.HSUPAPSLoad.MaxULThruput Maximu BSC6 WRFD RAN SharingIntro

Uplink 02130 MOCN
PS 4 Introduction
HSUPA WRFD Package
per 1
Operator WRFD
-
02130
404
67193 VS.HSUPAPSLoad.MaxULThruput Maximu BSC6 WRFD RAN SharingIntro

Uplink 02130 MOCN
PS 4 Introduction
HSUPA WRFD Package
1
er ID Descript e ID
ion
per WRFD
Operator -
02130
404
67193 VS.MBMSPSLoad.MaxDLThruput. Maximu BSC6 WRFD RAN SharingIntro

022 PLMN.RNC m 900 - duction Package
Downlin 02130 MOCN
k PS 4 Introduction
MBMS WRFD Package
per 1 MBMS
Operator WRFD Introduction
- Package
02130
404
WRFD
-
01061
6
67193 VS.MBMSPSLoad.MaxDLThruput. Maximu BSC6 WRFD RAN SharingIntro

022 PLMN.RNC m 910 - duction Package
Downlin 02130 MOCN
k PS 4 Introduction
MBMS WRFD Package
per 1 MBMS
Operator WRFD Introduction
- Package
02130
404
WRFD
-
01061
6
67203 VS.CSLoad.Erlang.Equiv.PLMN.R Equivale BSC6 WRFD RAN SharingIntro

962 NC nt CS 900 - duction Package
Erlang 02130 MOCN
for RNC 4 Introduction
per WRFD Package
Operator -
er ID Descript e ID
ion
02131 Independent
1 License Control
WRFD
-
02130
404
67203 VS.CSLoad.Erlang.Equiv.PLMN.R Equivale BSC6 WRFD RAN SharingIntro

962 NC nt CS 910 - duction Package
Erlang 02130 MOCN
per WRFD Package
Operator - Independent
02131 License Control
1
WRFD
-
02130
404
67204 VS.R99PSLoad.ULThruput.PLMN. Uplink BSC6 WRFD RAN SharingIntro

145 RNC PS R99 900 - duction Package
Traffic 02130 MOCN
per WRFD Package
1
WRFD
-
02130
404
67204 VS.R99PSLoad.ULThruput.PLMN. Uplink BSC6 WRFD RAN SharingIntro

145 RNC PS R99 910 - duction Package
Traffic 02130 MOCN
per WRFD Package
1
WRFD
-
02130
404
er ID Descript e ID
ion
67204 VS.R99PSLoad.DLThruput.PLMN. Downlin BSC6 WRFD RAN SharingIntro
146 RNC k PS 900 - duction Package
R99 02130 MOCN
Traffic 4 Introduction
for RNC WRFD Package
per - Independent
Operator 02131 License Control
1
WRFD
-
02130
404
67204 VS.R99PSLoad.DLThruput.PLMN. Downlin BSC6 WRFD RAN SharingIntro

146 RNC k PS 910 - duction Package
R99 02130 MOCN
per - Independent
1
WRFD
-
02130
404
67204 VS.HSDPAPSLoad.DLThruput.PL Downlin BSC6 WRFD RAN SharingIntro

147 MN.RNC k PS 900 - duction Package
HSDPA 02130 MOCN
per - Independent
1
WRFD
-
02130
404
67204 VS.HSDPAPSLoad.DLThruput.PL Downlin BSC6 WRFD RAN SharingIntro

HSDPA 02130 MOCN
-
er ID Descript e ID
ion
per 02131 Independent
WRFD
-
02130
404
67204 VS.HSUPAPSLoad.ULThruput.PL Uplink BSC6 WRFD RAN SharingIntro

148 MN.RNC PS 900 - duction Package
HSUPA 02130 MOCN
per - Independent
1
WRFD
-
02130
404
67204 VS.HSUPAPSLoad.ULThruput.PL Uplink BSC6 WRFD RAN SharingIntro

148 MN.RNC PS 910 - duction Package
HSUPA 02130 MOCN
per - Independent
1
WRFD
-
02130
404
67204 VS.MBMSPSLoad.DLThruput.PL Downlin BSC6 WRFD RAN SharingIntro

MBMS 02130 MOCN
per - Independent
1
WRFD
-
02130
404
er ID Descript e ID
ion
67204 VS.MBMSPSLoad.DLThruput.PL Downlin BSC6 WRFD RAN SharingIntro
MBMS 02130 MOCN
per - Independent
1
WRFD
-
02130
404
67204 VS.AMR.Erlang.Equiv.PLMN.RNC Equivale BSC6 WRFD RAN SharingIntro

835 nt 900 - duction Package
Erlang 02130 MOCN
of CS 4 Introduction
AMR WRFD Package
Service - Independent
per 1
Operator WRFD
-
02130
404
67204 VS.AMR.Erlang.Equiv.PLMN.RNC Equivale BSC6 WRFD RAN SharingIntro

Erlang 02130 MOCN
of CS 4 Introduction
AMR WRFD Package
Service - Independent
per 1
Operator WRFD
-
02130
404
67204 VS.VP.Erlang.Equiv.PLMN.RNC Equivale BSC6 WRFD RAN SharingIntro

Erlang 02130 MOCN
of 4 Introduction
64kbit/s WRFD Package
CS -
er ID Descript e ID
ion
Service 02131 Independent
per WRFD
Operator -
02130
404
67204 VS.VP.Erlang.Equiv.PLMN.RNC Equivale BSC6 WRFD RAN SharingIntro

Erlang 02130 MOCN
of 4 Introduction
64kbit/s WRFD Package
CS - Independent
Service 02131 License Control
for RNC 1
per WRFD
Operator -
02130
404
67204 VS.PS.CellDchUEs.PLMN Number BSC6 WRFD RAN SharingIntro

840 of 900 - duction Package
Cell_DC 02130 MOCN
H UEs 4 Introduction
in PS WRFD Package
Domain - Independent
per 1
Operator WRFD
-
02130
404
67204 VS.PS.CellDchUEs.PLMN Number BSC6 WRFD RAN SharingIntro

Cell_DC 02130 MOCN
H UEs 4 Introduction
in PS WRFD Package
per 1
Operator WRFD
-
02130
404
er ID Descript e ID
ion
73394 VS.PSLoad.MaxThruput.PLMN.RN Maximu BSC6 WRFD RAN SharingIntro
023 C m Total 900 - duction Package
Through 02130 MOCN
out of 4 Introduction
UL and WRFD Package
DL PS - Independent
Services 02131 License Control
per 1
Operator WRFD
for RNC -
02130
404
73394 VS.PSLoad.MaxThruput.PLMN.RN Maximu BSC6 WRFD RAN SharingIntro

023 C m Total 910 - duction Package
Through 02130 MOCN
out of 4 Introduction
UL and WRFD Package
DL PS - Independent
per 1
Operator WRFD
for RNC -
02130
404
73410 VS.PSLoad.Thruput.PLMN.RNC Average BSC6 WRFD RAN SharingIntro

502 Total 900 - duction Package
Through 02130 MOCN
put of 4 Introduction
UL and WRFD Package
DL PS - Independent
per 1
Operator WRFD
for RNC -
02130
404
73410 VS.PSLoad.Thruput.PLMN.RNC Average BSC6 WRFD RAN SharingIntro

502 Total 910 - duction Package
Through 02130 MOCN
put of 4 Introduction
UL and WRFD Package
DL PS -
er ID Descript e ID
ion
Services 02131 Independent
Operator WRFD
for RNC -
02130
404
73440 VS.PS.CellFachUEs.PLMN Number BSC6 WRFD RAN SharingIntro

Cell_FA 02130 MOCN
CH UEs 4 Introduction
in PS WRFD Package
per 1
Operator WRFD
-
02130
404
73440 VS.PS.CellFachUEs.PLMN Number BSC6 WRFD RAN SharingIntro

Cell_FA 02130 MOCN
CH UEs 4 Introduction
in PS WRFD Package
per 1
Operator WRFD
-
02130
404
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
8 Reference Documents
1. 3GPP TS 23.251, "Network Sharing Architecture and Functional Description"
2. 3GPP TR 23.851, "Network Sharing Architecture and Functional Description"
3. 3GPP TS 23.236, "Intra-domain Connection of RAN Nodes to Multiple CN Nodes"
4. 3GPP TR 22.951, "Service Aspects and Requirements for Network Sharing"
5. License Management Feature Parameter Description
6. Iu Flex feature parameter description
7. CBS feature parameter description
8. TRM in the RAN Sharing Scenario Feature Parameter Description

Ran Sharing

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ran Sharing

Hochgeladen von

Copyright:

Verfügbare Formate

WCDMA RAN

RAN Sharing Feature Parameter Description

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Huawei Technologies Co., Ltd.

LampSite DBS3900 LampSite

1.2 Intended Audience

1.3 Change History

This issue does not include any changes.

Change Type Change Description

Editorial change None

1.4 Differences Between Base Station Types

Feature ID Description Supported by Base Station Controller Supported by

WRFD-02130401 Dedicated Carrier for Y Y Y

WRFD-02130402 Flexible Network Y Y Y

WRFD-02130403 Mobility Control and Y Y Y

WRFD-02130404 Independent License Y Y Y

WRFD-02130405 Independent Cell-level Y Y Y

3.1.1 Operator ID and Type

3.1.2 System Information Broadcast

3.1.3 UE's Route Selection

3.2 Flexible Network Architecture

3.2.2 Iu-BC Interface

3.2.3 Iub Interface

Transmission for the Iub User Plane

3.2.4 Iur interface

3.2.5 Single CN With Multi-PLMN IDs

3.2.6 Base Station Supporting Multi-operator PKI

3.2.7.1 Coexistence of RNCs Under Full Coverage

3.2.7.2 Coexistence of Shared RNC and 2G Network

3.2.7.3 Coexistence of Full and Partial Coverage for Different Operators

3.2.7.5 Coexistence of Multiple Operators

3.3 Mobility Control and Service Differentiation

3.3.1 Mobile Control

3.3.2 Service Differentiation

Operator Operator-level parameters can enable different SET UOPERATORCFGPARA: CnOpInd

3.4 License Management

4.1 WRFD-021304 RAN Sharing Introduction Package

4.1.1 When to Use WRFD-021304 RAN Sharing Introduction Package

Feature ID Feature Name License Control Item License Control Item

WRFD-021304 RAN SharingIntroduction LQW1RANSH01RESE RAN SharingIntroduction BSC6

WRFD-021304 RAN SharingIntroduction LQW1RANSH01RESM RAN SharingIntroduction BSC6

4.1.2.2 Data Preparation

Operator Type OperatorType(BSC6900,BSC6910) Set this parameter based on wh

Cn Operator Name CnOperatorName(BSC6900,BSC6910) The value of this parameter mu

Cn Operator Group Index CnOpGrpIndex(BSC6900,BSC6910) The value of this parameter mu

Operator Number CnOpNum(BSC6900,BSC6910) The value of this parameter mu

Operator Name CnOpGrpName(BSC6900,BSC6910) The value of this parameter mu

OSP name NAME(BSC6900,BSC6910) Set this parameter based on the

OSP index SPX(BSC6900,BSC6910) Set this parameter based on the

DSP name NAME(BSC6900,BSC6910) Set this parameter based on the

DSP index DPX(BSC6900,BSC6910) Set this parameter based on the

OSP index SPX(BSC6900,BSC6910) Set this parameter based on the

Cn Operator Index CnOpIndex(BSC6900,BSC6910) The value of this parameter mu

CN node ID CNId(BSC6900,BSC6910) Set this parameter based on the

Sharing Type Of NodeB SharingType(BSC6900,BSC6910) Set this parameter to DEDICA

1. Run the RNC MML command SET UOPERATORSHARINGMODE to

//Activating RAN Sharing Introduction Package

Using the CME

1 UOPERATORSHARINGMODE RNC RAN Sharing Support RANSharingSup

2 UCNOPERATOR RNC Operator Type OperatorType(B

4.1.2.4 Activation Observation

1. Run the RNC MML command SET UOPERATORSHARINGMODE to

MML Command Examples

//Deactivating RAN Sharing Introduction Package