WCDMA RAN

RAN20.1

RAN Sharing Feature Parameter

Description

Issue 01
Date 2018-04-20

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2024. 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: https://www.huawei.com
Email: [email protected]

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. i

Security Declaration
Vulnerability
Huawei's regulations on product vulnerability management are subject to the Vul. Response Process. For
details about this process, visit the following web page:
https://www.huawei.com/en/psirt/vul-response-process
For vulnerability information, enterprise customers can visit the following web page:
https://securitybulletin.huawei.com/enterprise/en/security-advisory

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. ii

WCDMA RAN
RAN Sharing Feature Parameter Description Contents

Contents

1 About This Document.............................................................................................................1

1.1 Scope........................................................................................................................................................................................... 1
1.2 General Statements................................................................................................................................................................ 1
1.3 Change History......................................................................................................................................................................... 2
1.4 Differences Between Base Station Types........................................................................................................................ 3

2 Overview....................................................................................................................................4
3 Technical Description..............................................................................................................5
3.1 UE's Network Selection......................................................................................................................................................... 5
3.1.1 Operator ID and Type......................................................................................................................................................... 5
3.1.2 System Information Broadcast........................................................................................................................................ 5
3.1.3 UE's Route Selection........................................................................................................................................................... 5
3.2 Flexible Network Architecture............................................................................................................................................ 6
3.2.1 Iu Interface............................................................................................................................................................................. 7
3.2.2 Iu-BC Interface...................................................................................................................................................................... 8
3.2.3 Iub Interface.......................................................................................................................................................................... 9
3.2.4 Iur interface......................................................................................................................................................................... 11
3.2.5 Single CN with Multi-PLMN IDs................................................................................................................................... 11
3.2.6 Base Station Supporting Multi-operator PKI........................................................................................................... 13
3.2.7 Typical Networking Modes of RAN Sharing.............................................................................................................13
3.2.7.1 Coexistence of RNCs Under Full Coverage............................................................................................................ 13
3.2.7.2 Coexistence of Shared RNC and 2G Network...................................................................................................... 14
3.2.7.3 Coexistence of Full and Partial Coverage for Different Operators............................................................... 15
3.2.7.4 Coexistence of Iu Flex and RAN Sharing............................................................................................................... 15
3.2.7.5 Coexistence of Multiple Operators.......................................................................................................................... 16
3.2.7.6 Platform Sharing by the DCU and BBU of LampSite Base Stations............................................................. 17
3.3 Mobility Control and Service Differentiation.............................................................................................................. 18
3.3.1 Mobility Control................................................................................................................................................................. 18
3.3.2 Service Differentiation..................................................................................................................................................... 18
3.4 License Management.......................................................................................................................................................... 19
3.5 Operation and Maintenance............................................................................................................................................. 20
3.6 Inter-PLMN Multi-Carrier HSPA....................................................................................................................................... 23

4 Engineering Guidelines........................................................................................................ 25

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. iii

WCDMA RAN
RAN Sharing Feature Parameter Description Contents

4.1 WRFD-021304 RAN Sharing Introduction Package.................................................................................................. 25

4.1.1 When to Use WRFD-021304 RAN Sharing Introduction Package.................................................................... 25
4.1.2 Deployment......................................................................................................................................................................... 25
4.1.2.1 Requirements................................................................................................................................................................... 25
4.1.2.2 Data Preparation............................................................................................................................................................ 27
4.1.2.3 Activation.......................................................................................................................................................................... 29
4.1.2.4 Activation Observation.................................................................................................................................................31
4.1.2.5 Deactivation..................................................................................................................................................................... 31
4.1.3 Performance Monitoring................................................................................................................................................. 31
4.1.4 Troubleshooting................................................................................................................................................................. 32
4.2 WRFD-02130401 Dedicated Carrier for Each Operator...........................................................................................32
4.3 WRFD-02130402 Flexible Network Architecture....................................................................................................... 32
4.3.1 When to Use WRFD-02130402 Flexible Network Architecture.........................................................................32
4.3.2 Deployment......................................................................................................................................................................... 32
4.3.2.1 Requirements................................................................................................................................................................... 32
4.3.2.2 Data Preparation............................................................................................................................................................ 33
4.3.2.3 Activation.......................................................................................................................................................................... 34
4.3.2.4 Activation Observation.................................................................................................................................................34
4.3.2.5 Deactivation..................................................................................................................................................................... 34
4.3.3 Performance Monitoring................................................................................................................................................. 35
4.3.4 Troubleshooting................................................................................................................................................................. 35
4.4 Single CN With Multi-PLMN IDs..................................................................................................................................... 35
4.4.1 When to Use Single CN With Multi-PLMN IDs....................................................................................................... 35
4.4.2 Required Information....................................................................................................................................................... 35
4.4.3 Deployment......................................................................................................................................................................... 35
4.4.4 Performance Monitoring................................................................................................................................................. 38
4.4.5 Troubleshooting................................................................................................................................................................. 38
4.5 WRFD-02130403 Mobility Control and Service Differentiation............................................................................38
4.5.1 When to Use WRFD-02130403 Mobility Control and Service Differentiation............................................. 38
4.5.2 Deployment......................................................................................................................................................................... 38
4.5.2.1 Requirements................................................................................................................................................................... 39
4.5.2.2 Data Preparation............................................................................................................................................................ 39
4.5.2.3 Activation.......................................................................................................................................................................... 39
4.5.2.4 Activation Observation.................................................................................................................................................40
4.5.2.5 Deactivation..................................................................................................................................................................... 40
4.5.3 Performance Monitoring................................................................................................................................................. 40
4.5.4 Troubleshooting................................................................................................................................................................. 40
4.6 WRFD-02130404 Independent License Control..........................................................................................................40
4.7 WRFD-02130406 Transmission Recourse Sharing on Iub/Iur Interface............................................................. 41
4.8 Inter-PLMN Multi-Carrier HSPA....................................................................................................................................... 41
4.8.1 When to Use Inter-PLMN Multi-Carrier HSPA........................................................................................................ 41
4.8.2 Required Information....................................................................................................................................................... 41

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. iv

WCDMA RAN
RAN Sharing Feature Parameter Description Contents

4.8.3 Planning................................................................................................................................................................................ 41
4.8.3.1 RF Planning...................................................................................................................................................................... 41
4.8.3.2 Network Planning.......................................................................................................................................................... 41
4.8.3.3 Hardware Planning........................................................................................................................................................ 41
4.8.4 Deployment......................................................................................................................................................................... 42
4.8.4.1 Requirements................................................................................................................................................................... 42
4.8.4.2 Precautions....................................................................................................................................................................... 42
4.8.4.3 Data Preparation and Feature Activation.............................................................................................................. 42
4.8.4.3.1 Data Preparation.........................................................................................................................................................43
4.8.4.3.2 Using MML Commands............................................................................................................................................ 43
4.8.4.3.3 MML Command Examples...................................................................................................................................... 43
4.8.4.3.4 Using the MAE-Deployment................................................................................................................................... 43
4.8.4.4 Activation Observation.................................................................................................................................................43
4.8.4.5 Deactivation..................................................................................................................................................................... 44
4.8.4.5.1 Using MML Commands............................................................................................................................................ 44
4.8.4.5.2 MML Command Examples...................................................................................................................................... 44
4.8.4.5.3 Using the MAE-Deployment................................................................................................................................... 44
4.8.4.6 Reconfiguration.............................................................................................................................................................. 44
4.8.5 Performance Monitoring................................................................................................................................................. 44
4.8.6 Parameter Optimization..................................................................................................................................................45
4.8.7 Troubleshooting................................................................................................................................................................. 45

5 Parameters.............................................................................................................................. 46
6 Counters.................................................................................................................................. 47
7 Glossary................................................................................................................................... 48
8 Reference Documents...........................................................................................................49

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. v

WCDMA RAN
RAN Sharing Feature Parameter Description 1 About This Document

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

1.2 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 1

WCDMA RAN
RAN Sharing Feature Parameter Description 1 About This Document

NOTE

This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Functions mentioned in this document work properly only when enabled in the
specified applicable scenarios (such as RAT and networking). If a function not
mentioned in this document is enabled or a function is enabled in a scenario not
specified as applicable, exceptions or other impacts may occur.

Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.

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 and parameters of a specified version
● Editorial change
Changes in wording or addition of information that was not described in the
earlier version

RAN20.1 01 (2018-04-20)
This issue does not include any changes.

RAN20.1 Draft A (2018-02-05)

Compared with Issue 02 (2017-04-30) of RAN19.1, Draft A (2018-02-05) of
RAN20.1 includes the following changes.

Change Change Description Paramete

Type r Change

Feature Allowed the DCU and BBU of LampSite base stations None
change to share the same hardware platform. For details, see
3.2.7.6 Platform Sharing by the DCU and BBU of
LampSite Base Stations.

Added description about inter-PLMN multi-carrier None

HSPA. For details, see the following sections:
● 3.6 Inter-PLMN Multi-Carrier HSPA
● 4.8 Inter-PLMN Multi-Carrier HSPA

Editorial None None

change

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 2

WCDMA RAN
RAN Sharing Feature Parameter Description 1 About This Document

1.4 Differences Between Base Station Types

Feature Support by Macro/LampSite Base Stations
Feature ID Feature BSC6900 BSC6910 Supported Supported
Name by Macro by
Base LampSite
Stations Base
Stations

WRFD-021 RAN Yes Yes Yes Yes

304 Sharing
Introductio
n Package

WRFD-021 Dedicated Yes Yes Yes Yes

30401 Carrier for
Each
Operator

WRFD-021 Flexible Yes Yes Yes Yes

30402 Network
Architectur
e

WRFD-021 Mobility Yes Yes Yes Yes

30403 Control
and Service
Differentiat
ion

WRFD-021 Independe Yes Yes Yes Yes

30404 nt License
Control

WRFD-021 Independe Yes Yes Yes Yes

30405 nt Cell-
level
FM/PM/CM

WRFD-021 Transmissio Yes Yes Yes Yes

30406 n Recourse
Sharing on
Iub/Iur
Interface

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 3

WCDMA RAN
RAN Sharing Feature Parameter Description 2 Overview

2 Overview

Introduction
The RAN Sharing feature enables operators to share 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 delivered by this feature are as follows:
● Lower cost
The motivation for operators to share networks is to reduce investment and
operation cost.
● 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
RAN sharing devices include MAE and RAN. The shared interfaces include Iub, Iur,
and Itf-S. The cell, CN, and northbound NMS are solely used by 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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 4

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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 has a globally unique PLMN ID, which consists of the 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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 5

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 6

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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, specify 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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 7

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

Figure 3-3 RNC shared by operators A and B

Operators can activate or deactivate the Iu Flex feature independently. Iu Flex is

configured in 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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 8

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical 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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 9

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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 oversized packets are fragmented on the base station. The MTU value
can also be configured as MAX(MTU1, MTU2, MTU3...). In this way, packet
fragmentation and reassembly for networks with a large MTU value can be
reduced. For networks with a small MTU value, some packets are moved 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 O&M path are shared among 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 solely used by operators,
as shown in Figure 3-7.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 10

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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.
● ALCAP links are configured 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 CAPEX and 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

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 11

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

the PLMN IDs broadcast in different operators' cells are different. However, this
function causes the following changes to the network:

● When only the primary operator's CN is available and all of them are shared
by multiple operators, the CN sharing relationship does not need to be
configured. The RNC routes all UEs to the primary operator's CN as long as
MultiPLMNforSingleCNSwitch (BSC6900, BSC6910) is set to ON.
NOTE

If the CN sends the RNC the RIM carrying the PLMN information of the secondary
operator, set MultiPLMNforSingleCNSwitch (BSC6900, BSC6910) to OFF and
MultiPLMNforCNEnhanceSw (BSC6900, BSC6910) to ON, and run the MML
command ADD UCNNODESHAREDMAP to add the MOCN operator for the CN.
– The RNC routes UEs of all operators to the primary operator's CN node.
This function only requires the configuration of the primary operator's CN
node, by using 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 UIU command is to be run on the RNC, the CnOpIndex
(BSC6900, BSC6910) and CNID (BSC6900, BSC6910) parameters must
be set to the index and ID of the CN node of the primary operator,
respectively. Otherwise, execution of this command fails.
– The primary operator's CN provides services 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 or
IMSI and the 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 measurement
objects CS.SIG.IU, CS.TRF.IU, NAS.IU, PS.SIG.IU, PS.TRF.IU, and SIG.SCCP.IU
are measured for all operators.
● Otherwise, MultiPLMNforCNEnhanceSw must be set to ON so that some CN
nodes can be shared by multiple operators and all CN nodes do not need to
be provided by the primary operator.
If some CNs are shared and other CNs are dedicated, the RNC MML command
ADD UCNNODESHAREDMAP can be used to configure the CN sharing
relationship among operators. In this command, the CnOpIndex specifies the
index of the homing operator of this CN and SharedCnOpIndex specifies the
indexes of the operators sharing this CN.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 12

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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 and secure isolation of services is
achieved.
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

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 13

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

shared 3G network together in another area. Shared RNC 1 is connected to shared

RNC 2, 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 move from an
operator A cell to a neighboring operator A cell by soft handovers. The same case
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 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. In this way, service continuity is assured when
a UE of operator A moves between the operator A UMTS cell and the neighboring
operator A GSM cell. The same case applies to operator B.

Figure 3-11 Coexistence of Shared RNC and 2G Network

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 14

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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 that
provides full coverage, whereas operator B only has partial coverage in this RAN.
Operator B must share the RAN with operator A in uncovered areas of operator B
to achieve full coverage.
When a UE of operator B moves 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 a handover, cell reselection, or cell update. When the UE
moves 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 handovers.
In this scenario, the switch specified by the InterPlmnHoAllowedIntraRat
(BSC6900, BSC6910) parameter must be turned on 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 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 only.
In this scenario, services of one operator can only be processed by the CN node of
this operator.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 15

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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 network resources.
To achieve roaming (such as handovers and cell reselections) between the cells of
operator B and operator C, the switch specified by the
InterPlmnHoAllowedIntraRat (BSC6900, BSC6910) parameter must be turned
on and the neighboring cell relations must be configured.

Figure 3-14 Coexistence of multiple operators

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 16

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

3.2.7.6 Platform Sharing by the DCU and BBU of LampSite Base Stations
In the LampSite scenario, the DCU and BBU are two hardware units of a LampSite
base station. Now, they share one hardware platform on which the following two
boards are introduced:
● Multi Extended Radio Frequency Card (MERC): supports reception of RF
signals from operators.
● Multi Extended Digital Card (MEDC): supports reception of digital signals
from operators.
In the LampSite sharing scenario, the network can be constructed by the
proprietor and primary operator, and the signals of other operators can be
received by the MERC or MEDC. Figure 3-15 shows the network architecture, in
which the MEDC board connects optical fibers and implements inter-rack BBU
connections.

Figure 3-15 Network architecture in the LampSite sharing scenario

In Figure 3-15, only MERC or MEDC boards are configured in the BBU (RF only)
without baseband processing units. Figure 3-16 shows the detailed configuration.

Figure 3-16 Configuration in the BBU (RF only)

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 17

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

Only baseband processing units are configured in the BBU (baseband only)
without MERC or MEDC boards. Figure 3-17 shows the detailed configuration.

Figure 3-17 Configuration in the BBU (baseband only)

For details about the LampSite sharing of the LampSite DCU BBU, see DBS3900 &
DBS5900 LampSite Technical Description > Networking Scenario > LampSite
Solution for Outdoor Residential Areas in 3900 & 5900 Series Base Station Product
Documentation.

3.3 Mobility Control and Service Differentiation

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

3.3.1 Mobility Control

If an inter-PLMN handover is performed, cell resources of one operator may be
occupied by UEs of other operators and the charging is affected. To ensure the
interests of operators, inter-PLMN handovers are 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.

Service-based Inter-RAT Handover Control

For service-based RAT handovers across PLMNs, the handover conditions must be
satisfied and the following switch control applies:
● If HO_IRAT_SERV_FORBID_SWITCH under HoSwitch (BSC6900, BSC6910) is
selected, UEs of the operator are not allowed for service-based inter-RAT
handovers.
● If HO_IRAT_SERV_FORBID_SWITCH under HoSwitch (BSC6900, BSC6910) is
deselected, UEs of the operator are allowed for service-based inter-RAT
handovers.
For details about conditions for service-based handovers, see Handover Feature
Parameter Description.

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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 18

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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

Paramet Description Parameter Feature Example

er Level Example

RNC RNC-level parameters are SET WRFD-020309

shared by all operators UCORRMALGOSW Inter-RAT
and cannot be ITCH: Handover Based
independently configured HoSwitch=HO_IN on DL QoS
by operators. TER_RAT_PS_OUT
_SWITCH-1;

Cell The cells of different MOD WRFD-020104

operators are independent UCELLALGOSWIT Intra Frequency
of each other. Cell-level CH: CellId=111, Load Balance
parameters can enable NBMLdcAlgoSwitc
different features for h=INTRA_FREQUE
different cells. NCY_LDB-1;

Operator Operator-level parameters SET WRFD-021302 Iu

can enable different UOPERATORCFGP Flex
features for different ARA:
operators. CnOpIndex=1,
CsNriCfgMode=SU
PP_IUFLEX;

NodeB NodeB-level parameters MOD UNODEB: WRFD-050104

are shared by all operators IDTYPE=BYID, Satellite
and cannot be NodeBId=1, Transmission on
independently configured TRANSDELAY=600 Iub Interface
by operators. ,
SATELLITEIND=TR
UE;

3.4 License Management

This section describes the WRFD-02130404 Independent License Control feature.
WRFD-02130404 Independent License Control allows operators in a RAN sharing
network to use licenses to control deployment of different features and
configuration of different capacities on RNCs and NodeBs based on actual needs.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 19

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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
MAE. In this way, different capacities and features are enabled for operators.

Figure 3-18 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-18 Principles of RAN Sharing license management

3.5 Operation and Maintenance

This section describes the WRFD-02130405 Independent Cell-level FM/PM/CM
feature.

O&M Architecture
The O&M architecture of a RAN sharing network mainly consists of the RAN, MAE,
and each operator's NMS. The RAN and MAE are shared by operators, and the
NMSs and northbound interfaces (NBIs) are solely used by operators. The MAE
provides a secure and efficient O&M solution to a RAN sharing network. The MAE,
through the NBI, provides required configuration data, alarm data, and
performance data to an operator's NMS based on the role of the operator. This
effectively manages the privacy, independence, and sharing of network resources
and data specific to operators' requirements.

As shown in Figure 3-19, BTS X, BTS Y, and BTS Z compose a sharing network. A
third party (called Jointer) is responsible for the O&M of the sharing network.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 20

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

Figure 3-19 O&M architecture

BTS Y is shared by operators A and B, BTS X is solely used by operator A, and BTS
Z is solely used by operator 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 are 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 or alarm management solution. The MAE 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 northbound interface
(Itf-N) is classified into two types:

● Operator-specific data
Operator-specific data refers to cell-level FM, PM, and CM data. It is only
related to a specific operator and is stored in the operator's NMS on Itf-N.
● Operator-shared data
Operator-shared data refers to other FM, PM, and CM data. It is related to all
operators.

Setting Principles of O&M Modes

A RAN sharing network generally has two OM modes: Joint and Rent.

In Joint mode, multiple operators provide respective devices and frequency

spectrum to form a shared network, and one of the operators or a third party
(called Jointer) is responsible for the O&M of the shared network. In Rent mode,
an operator provides devices and frequency spectrum and rents these resources to
other operators. The operator that provides devices and frequency spectrum

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 21

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

(called Renter) is responsible for the O&M of the shared network. In both modes,
NEs may be solely used by an operator.

In these modes, Jointer and Renter have the MAE operation rights and are
responsible for the O&M 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 MAE, 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 MAE 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 MAE 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 MAE 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 at the same time. You can use the OSS self-
maintenance unit (OSMU) of the MAE 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 MAE, 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 MAE Northbound Interface Developer Guide.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 22

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

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 MAE Northbound Interface Developer Guide.

3.6 Inter-PLMN Multi-Carrier HSPA

Background
In RAN sharing scenarios, if an operator has only one carrier, users of the operator
cannot adopt the multi-carrier technology and therefore cannot obtain high peak
rate, leading to poor user experience. This feature helps deploy multi-carrier
networks in RAN sharing scenarios to increase the peak rate, improving user
experience.

Benefits
The feature supports multi-carrier relationships across different PLMNs in RAN
Sharing scenarios to improve the peak rate.

Technical Description
Different carriers may belong to different operators because a shared RNC can
support common carriers and dedicated carriers. The InterPlmnMultiCarrSwitch
parameter in the SET UOPERATORSHARINGMODE command controls whether
inter-PLMN multi-carrier HSPA, such as DC-HSDPA, DB-HSDPA, 3C-HSDPA and 4C-
HSDPA, can be allowed.

If InterPlmnMultiCarrSwitch is set to NO, multi-carrier HSPA is allowed only

when the UE's serving operator is one of the operators that provide both primary
and secondary carriers.

If InterPlmnMultiCarrSwitch is set to YES,

● when TarRAT and TarCnOpIndex are not set in the ADD

UINTERPLMNHOLIST command, multi-carrier HSPA is allowed no matter
whether the UE's serving operator is one of the operators that provide both
primary and secondary carriers or not.
● when TarRAT and TarCnOpIndex are set in the ADD UINTERPLMNHOLIST
command, multi-carrier HSPA is allowed when the UE's serving operator
meets one of the following conditions:
– The UE's serving operator is the operator that provides secondary carriers,
and the operator has an inter-PLMN handover relationship with the
operator that provides the primary carrier.
– The UE's serving operator is included in the operator group to which
secondary carrier cells belong.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 23

WCDMA RAN
RAN Sharing Feature Parameter Description 3 Technical Description

If the secondary carrier supports DC-HSUPA and UEs' services can be carried over
DC-HSUPA, inter-PLMN DC-HSUPA can be allowed.

NOTE

After this function is enabled, license consumption by multi-carrier HSDPA users may
become different.
For example, if DC-HSDPA licenses are available for three cells under a NodeB:
● Before this function is enabled, DC-HSDPA users can be established in three cells with
the same PLMN ID and neighboring frequencies (for example, cell 1 operating on F1,
cell 2 operating on F2, and cell 3 operating on F3). The cells belong to the same carrier
group, and F1, F2, and F3 are neighboring frequencies.
● After this function is enabled, cell 4 (operating on F4) with another PLMN ID is added
to the carrier group. Among the four cells, only three can accommodate DC-HSDPA
users. For example, if DC-HSDPA users are established in cell 4 and cell 3, only cell 3
and cell 2 can accommodate DC-HSDPA users. This is because the available licenses
have been used up in cell 4, cell 3, and cell 2.
For details about license consumption, see Multi-Carrier HSDPA Feature Parameter
Description and DC-HSUPA Feature Parameter Description.

Related Features
● Prerequisite features
None
● Mutually exclusive features
None
● Impacted features
None

Network Impact
● System capacity
In RAN sharing scenarios, when this function takes effect, the single-UE peak
rate increases and can reach the peak rate of multi-carrier HSPA.
● Network performance
When this function takes effect, resource consumption of other operators
increases.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 24

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

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

4.1.2.1 Requirements

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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 25

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

License
For details about how to activate the license, see License Management Feature
Parameter Description.

Feature Feature License License NE License Sal

ID Name Control Control Allocatio es
Item ID Item n for Uni
Name Multiple t
Operator
s

WRFD-02 RAN LQW1RA RAN BSC6900 Method 1 per

1304 Sharing NSH01RE Sharing BSC6910 Erl
Introducti SE Introducti
on on
Package Package
(per Erl)

WRFD-02 RAN LQW1RA RAN BSC6900 Method 2 per

1304 Sharing NSH01RE Sharing BSC6910 Mb
Introducti SM Introducti ps
on on
Package Package
(per
Mbps)

If RAN Sharing or MOCN is enabled, the licensed resource is allocated among the
primary and secondary operators according to the method listed in the License
Allocation for Multiple Operators column.
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
FeatureResAssignMode parameter set to ManualAssign and license-related
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, PSTHROUGHPUT, HSDPATHROUGHPUT, and
HSUPATHROUGHPUT). Example:
SET LICENSE: SETOBJECT=UMTS, OperatorType=PRIM, CNOPERATORINDEX=0,
FeatureResAssignMode=AutoAssign, CSERLANG=35000, PSTHROUGHPUT=10000000,
HSDPATHROUGHPUT=10000000, HSUPATHROUGHPUT=10000000;
SET LICENSE: SETOBJECT=UMTS, OperatorType=SEC, CNOPERATORINDEX=1,
FeatureResAssignMode=AutoAssign, CSERLANG=15000, PSTHROUGHPUT=8000000,
HSDPATHROUGHPUT=8000000, HSUPATHROUGHPUT=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

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 26

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

parameter set to AutoAssign for automatic allocation or with the

FeatureResAssignMode parameter set to ManualAssign and license-related
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 for the primary operator, that is, to deselect MOCN_PACKAGE under the
FUNCTIONSWITCH4 parameter.

Other Requirements
None

4.1.2.2 Data Preparation

Table 4-1 lists the data to prepare before activating WRFD-021304 RAN Sharing
Introduction Package.

Table 4-1 Data to prepare before activating WRFD-021304 RAN Sharing

Introduction Package

Parameter Parameter ID Setting Notes Data

Name Source

RAN Sharing RANSharingSupport Set this parameter to YES. Network

Support (BSC6900, BSC6910) plan
(negotiati
on not
required)

Operator OperatorType Set this parameter based Network

Type (BSC6900, BSC6910) on whether the sharing plan
operator is a primary or (negotiati
secondary operator. on
required)

Operator CnOperatorName The value of this Internal

Name (BSC6900, BSC6910) parameter must be unique. plan

Cn Operator CnOpGrpIndex The value of this Internal

Group Index (BSC6900, BSC6910) parameter must be unique. plan

Operator CnOpNum (BSC6900, The value of this Internal

Number BSC6910) parameter must be unique. plan

Operator 1 CnOpIndex1 The value of this Internal

Index (BSC6900, BSC6910) parameter must be unique. plan

Cn Operator CnOpGrpName The value of this Internal

Group (BSC6900, BSC6910) parameter must be unique. plan
Name

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 27

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

Parameter Parameter ID Setting Notes Data

Name Source

OSP name NAME (BSC6900, Set this parameter based Network

BSC6910) on the negotiated data plan
among operators. The (negotiati
value of this parameter on
must be unique. required)

OSP index SPX (BSC6900, Set this parameter based Network

BSC6910) on the negotiated data plan
among operators. The (negotiati
value of this parameter on
must be unique. required)

DSP name NAME (BSC6900, Set this parameter based Network

BSC6910) on the negotiated data plan
among operators. The (negotiati
value of this parameter on
must be unique. required)

DSP index DPX (BSC6900, Set this parameter based Network

BSC6910) on the negotiated data plan
among operators. The (negotiati
value of this parameter on
must be unique. required)

OSP index SPX (BSC6900, Set this parameter based Network

BSC6910) on the negotiated data plan
among operators. The (negotiati
value of this parameter on
must be unique. required)

Cn Operator CnOpIndex (BSC6900, The value of this Internal

Index BSC6910) parameter must be unique. plan

CN node ID CNId (BSC6900, Set this parameter based Network

BSC6910) on the negotiated data plan
among operators. The (negotiati
value of this parameter on
must be unique. required)

Sharing SharingType Set this parameter to Network

Type Of (BSC6900, BSC6910) DEDICATED(Dedicated) plan
NodeB or RANSHARING(RAN (negotiati
Sharing) depending on on
whether the NodeB is to required)
be shared.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 28

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

4.1.2.3 Activation

Using MML Commands

Step 1 Run the RNC MML command SET UOPERATORSHARINGMODE with
RANSharingSupport (BSC6900, BSC6910) set to YES.
Step 2 Run the RNC MML command ADD UCNOPERATOR to set OperatorType
(BSC6900, BSC6910) for each operator.
Step 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).
Step 4 Run the RNC MML command ADD OPC for multiple times to configure originating
signaling points (OSPs) for the primary and 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.

Step 5 Run the RNC MML command ADD N7DPC for multiple times to configure
destination signaling points (DSPs) for the primary and secondary operators.
Step 6 Configure Iu data for the primary operator and for each of the secondary
operators.
Step 7 Run the RNC MML command ADD UCNNODE to add CN nodes for the primary
operator and for each of the secondary operators.
Step 8 Run the RNC MML command ADD UNODEB with SharingType (BSC6900,
BSC6910) set to DEDICATED(Dedicated) or RANSHARING(RAN Sharing).
Step 9 Run the RNC MML command ADD ULAC, ADD URAC, ADD USAC, and ADD
UURA to set the LAC, RAC, SAC, and URA, respectively, for the primary operator
and for each of the secondary operators.
Step 10 Run the RNC MML command ADD ULOCELL to add a local cell.
Step 11 Run the RNC MML command ADD UCELLQUICKSETUP to add a dedicated cell.

----End

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 29

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

NOTE

● There are two types of RAN sharing:

NodeBs are independently deployed by operators.
NodeBs are shared by operators but cells are not.
● After a cell is added or the UARFCN is changed, check whether the UARFCN used by the
cell is in the allowed range of the NodeB license. If not, you must issue a new NodeB
license on the MAE.
● If an operator's cells have all been removed from a NodeB, manually reclaim the NodeB
license on the MAE before performing license operations. If the entire NodeB has been
removed from the MAE, 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 a 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="SECCS", DPX=2, SPX=1, SPDF=WNF, DPC=555, DPCT=IUCS, BEARTYPE=M3UA;
ADD N7DPC: NAME="SECPS", 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, CNProtclVer=R99,
SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, AvailCap=60000;
//Adding CN nodes for a secondary operator
ADD UCNNODE: CnOpIndex=1, CNId=2, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R99,
SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, AvailCap=60000,
TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1, Switch3GPP25415CR0125=OFF;
ADD UCNNODE: CnOpIndex=1, CNId=3, CNDomainId=PS_DOMAIN, Dpx=3, CNProtclVer=R99,
SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, 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;
//Configuring cell 1
ADD ULOCELL: IDTYPE=BYNAME,NODEBNAME="NodeB1",LOCELL=1;
ADD UCELLQUICKSETUP: CELLID=1, CELLNAME="Cell1", BANDIND=BAND1,
CnOpGrpIndex=0,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, PSCRAMBCODE=0, TCELL=CHIP256,
LAC=H'2201, 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=1,

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 30

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

SUPBMC=FALSE, MAXTXPOWER=430, PCPICHPOWER=330;

//Configuring cell 2
ADD ULOCELL: IDTYPE=BYNAME,NODEBNAME="NodeB1",LOCELL=2;
ADD UCELLQUICKSETUP: CELLID=2, CELLNAME="Cell2", BANDIND=BAND1,
CnOpGrpIndex=1,UARFCNUPLINK=9637, UARFCNDOWNLINK=10587, PSCRAMBCODE=0, TCELL=CHIP256,
LAC=H'2201, 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=2,
SUPBMC=FALSE, MAXTXPOWER=430, PCPICHPOWER=330;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.1.2.4 Activation Observation

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.

4.1.2.5 Deactivation

Using MML Commands

Step 1 Run the RNC MML command SET UOPERATORSHARINGMODE with
RANSharingSupport (BSC6900, BSC6910) set to NO.
Step 2 Run the RNC MML command MOD UNODEB with Sharing Type Of NodeB set to
DEDICATED(Dedicated).

----End

MML Command Examples

//Deactivating RAN Sharing Introduction Package
//Changing the NodeB sharing type 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 MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.1.3 Performance Monitoring

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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 31

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

4.1.4 Troubleshooting
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

4.3.2.1 Requirements

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&5900 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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 32

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

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

4.3.2.2 Data Preparation

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-2 lists the data to prepare before activating WRFD-02130402 Flexible
Network Architecture.

Table 4-2 Data to prepare before activating WRFD-02130402 Flexible Network

Architecture

Parameter Parameter ID Setting Notes Data

Name Source

Sharing Type RANSharingSuppo Set this parameter to Network

Of NodeB rt (BSC6900, DEDICATED(Dedicated) or plan
BSC6910) RANSHARING(RAN (negotiati
Sharing) depending on on
whether the NodeB is to be required)
shared.

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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 33

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

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.

4.3.2.4 Activation Observation

To verify flexible deployment on the Iu interface, see the WRFD-021302 Iu Flex
feature in Iu Flex Feature Parameter Description.

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.

4.3.2.5 Deactivation
To deactivate flexible deployment on the Iu interface, see the WRFD-021302 Iu
Flex feature in Iu Flex Feature Parameter Description.

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.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 34

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

To deactivate flexible deployment on the Iub interface, run the RNC MML
command MOD UNODEB with Sharing Type Of NodeB set to
DEDICATED(Dedicated) or RANSHARING(RAN Sharing).

4.3.3 Performance Monitoring

None

4.3.4 Troubleshooting
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 deploying this function, you must enable the WRFD-021304 RAN
Sharing Introduction Package feature and turn off the inter-operator
handover switch specified by the InterPlmnHoAllowedIntraRat (BSC6900,
BSC6910) parameter.
The MSC must support WSFD-110103 Multiple HPLMNs, and the SGSN must
support WMFD-160100 Multi-PLMN Function.
● Hardware
None

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 35

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

● 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
Parame Parameter ID Setting Notes Data
ter Source
Name

Single MultiPLMNforSingleCNS- Turn on this switch when Network

CN With witch only the primary operator's plan
Multi- CNs are available and all
PLMN the CN nodes of the
IDs primary operator are
Switch shared by multiple
operators.

CN CnOpIndex Configure the operator Network

Operato sharing relationship by CN plan
r Index node.

CN node CNID Configure the operator Network

ID sharing relationship by CN plan
node.

Sharing SharedCnOpIndex Configure the operator Network

Operato sharing relationship by CN plan
r Index node.

Enhance MultiPLMNforCNEnhan- Turn on this switch if some Network

Multi- ceSw CN nodes are shared and plan
PLMN others are dedicated.
for CN

Activation (Using MML Commands)

CN side: For the configuration of the Multi-PLMN or GWCN feature, see related
CN documentation.
See 4.1.2 Deployment to activate RAN Sharing Introduction Package.
● If all CN nodes are shared, perform the following steps:

Step 1 (Optional) Delete the Iu interface and the mapping between the NRI and the CN
node for the secondary operator.
Step 2 Run the RNC MML command SET UOPERATORSHARINGMODE with Intra RAT
Inter Plmn Ho Allowed set to OFF.
Step 3 Run the RNC MML command SET UOPERATORSHARINGMODE with Single CN
With Multi-PLMN IDs Switch set to ON.

----End

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 36

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

● If some CN nodes are shared and others are dedicated, perform the following
steps:

Step 1 Run the RNC MML command ADD UCNNODESHAREDMAP with Sharing
Operator Index specified.
Step 2 Run the RNC MML command SET UOPERATORSHARINGMODE with Intra RAT
Inter Plmn Ho Allowed set to OFF.
Step 3 Run the RNC MML command SET UOPERATORSHARINGMODE with Enhance
Multi-PLMN for CN set to ON.

----End

Activation (Using the MAE-Deployment)

For detailed operations, see Feature Configuration Using the MAE-Deployment.

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)

If all CN nodes are shared, perform the following steps:

Step 1 (Optional) If the secondary operator's CN node is not configured, you need to
configure the CN node and NRI first.
Step 2 Run the RNC MML command SET UOPERATORSHARINGMODE with Single CN
With Multi-PLMN IDs Switch set to OFF.

----End
If some CN nodes are shared and others are dedicated, perform the following
steps:

Step 1 Run the RNC MML command ADD UCNNODESHAREDMAP with Sharing
Operator Index specified.
Step 2 Run the RNC MML command SET UOPERATORSHARINGMODE with Enhance
Multi-PLMN for CN set to OFF.

----End

Deactivation (Using the MAE-Deployment)

For detailed operations, see Feature Configuration Using the MAE-Deployment.

MML Command Examples

//Activating the Single CN with Multi-PLMN IDs function after RAN Sharing Introduction Package is
deployed
//(Optional) Deleting the Iu interface for a secondary operator
RMV UCNNODE: CnOpIndex=1, CNId=11;

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 37

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

//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;
//Deactivating (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
ADD UCNNODE: CnOpIndex=1, CNId=11, CNDomainId=CS_DOMAIN, Dpx=5, CNProtclVer=R5,
SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS,
RTCPSwitch=OFF, Switch3GPP25415CR0125=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;

//Activating the Enhanced Multi-PLMN for CN function after RAN Sharing Introduction Package is deployed
//Configuring the CN sharing relationship among operators
ADD UCNNODESHAREDMAP: CnOpIndex=0, CNId=1, SharedCnOpIndex=1;
//Turning on the switch for the Enhanced Multi-PLMN for CN function on the RNC
SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES,
MultiPLMNforCNEnhanceSw=ON, InterPlmnHoAllowedIntraRat=NO,InterPlmnHoAllowedInterRat=NO,
DefaultCnOp=0;
//Feature deactivation
//Removing the CN sharing relationship among operators
RMV UCNNODESHAREDMAP: CnOpIndex=0, CNId=1, SharedCnOpIndex=1;
//Turning off the switch for the Enhanced Multi-PLMN for CN function on the RNC
SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES,
MultiPLMNforCNEnhanceSw=OFF, InterPlmnHoAllowedIntraRat=NO,InterPlmnHoAllowedInterRat=NO,
DefaultCnOp=0;

4.4.4 Performance Monitoring

None

4.4.5 Troubleshooting
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

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 38

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

4.5.2.1 Requirements

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

4.5.2.2 Data Preparation

Table 4-3 lists the data to prepare before activating WRFD-02130403 Mobility
Control and Service Differentiation.

Table 4-3 Data to prepare before activating WRFD-02130403 Mobility Control and
Service Differentiation

Parameter Parameter ID Setting Notes Data

Name Source

Intra RAT Inter InterPlmnHoAllowe- Set this parameter to Network

Plmn Ho dIntraRat (BSC6900, YES. plan
Allowed BSC6910) (negotiati
on
required)

Inter RAT Inter InterPlmnHoAllowe- Set this parameter to Network

Plmn Ho dInterRat (BSC6900, YES. plan
Allowed BSC6910) (negotiati
on
required)

4.5.2.3 Activation

Using MML Commands

Run the RNC MML command SET UOPERATORSHARINGMODE with
InterPlmnHoAllowedInterRat (BSC6900, BSC6910) and
InterPlmnHoAllowedIntraRat (BSC6900, BSC6910) both set to YES.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 39

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

MML Command Examples

/Activating Mobility Control and Service Differentiation
SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=YES,
InterPlmnHoAllowedInterRat=YES;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.5.2.4 Activation Observation

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.

4.5.2.5 Deactivation

Using MML Commands

Run the RNC MML command SET UOPERATORSHARINGMODE with
InterPlmnHoAllowedInterRat (BSC6900, BSC6910) and
InterPlmnHoAllowedIntraRat (BSC6900, BSC6910) both set to NO.

MML Command Examples

//Deactivating Mobility Control and Service Differentiation
SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=NO,
InterPlmnHoAllowedInterRat=NO;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.5.3 Performance Monitoring

None.

4.5.4 Troubleshooting
None.

4.6 WRFD-02130404 Independent License Control

WRFD-02130404 Independent License Control allows operators in a RAN sharing
network to 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
MAE. For details about RAN Sharing license management, see the "License Control
for Multiple Operators" section in License Management Feature Parameter
Description.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 40

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

The license delivered by the MAE to the NodeB carries the operator's frequency
information. In the multi-operator sharing scenario, to ensure the frequencies in
the license information are consistent with the configured frequencies after cell
frequencies are modified on the RNC, the license must be re-delivered on the
MAE.

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.

4.8 Inter-PLMN Multi-Carrier HSPA

4.8.1 When to Use Inter-PLMN Multi-Carrier HSPA

This function has the following requirements:
● The network runs in RAN sharing mode.
● The operator has only one or multiple carriers and requires multi-carrier
relationships with cells of other operators.
● The network is enabled with a multi-carrier technology and serves UEs that
support multiple carriers.

4.8.2 Required Information

None

4.8.3 Planning

4.8.3.1 RF Planning
None

4.8.3.2 Network Planning

None

4.8.3.3 Hardware Planning

To apply a multi-carrier technology, refer to "Hardware Planning" in Multi-Carrier
HSDPA Feature Parameter Description.
To apply the DC-HSUPA technology, refer to "Hardware Planning" in DC-HSUPA
Feature Parameter Description.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 41

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

4.8.4 Deployment

4.8.4.1 Requirements

Other Features
● Prerequisite Features
None
● Mutually Exclusive Features
None
● Impacted Features
None

Hardware
● RNC
None
● NodeB
None
● Others
To apply a multi-carrier technology, refer to "Hardware Planning" in Multi-
Carrier HSDPA Feature Parameter Description.
To apply the DC-HSUPA technology, refer to "Hardware Planning" in DC-
HSUPA Feature Parameter Description.

License
This function is not under license control.

Other Requirements
None

4.8.4.2 Precautions
Before the upgrade, clear the following alarm:
ALM-28206 Local Cell Capability Decline

4.8.4.3 Data Preparation and Feature Activation

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 42

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

4.8.4.3.1 Data Preparation

Parameter Parameter ID Setting Notes Data Remarks

Name Source

Inter-PLMN InterPlmnMulti No Default/ NE: RNC

Multicarrier CarrSwitch Recomme MO:
HSDPA (BSC6900, nded UOPERATOR
Switch BSC6910) value SHARINGM
ODE
Batch
modification
on the MAE-
Deployment
is not
supported.

4.8.4.3.2 Using MML Commands

Step 1 Run the RNC MML command SET UOPERATORSHARINGMODE with
InterPlmnMultiCarrSwitch set to YES.
Step 2 Run the NodeB MML command ADD NODEBMULTICELLGRPITEM multiple times
to add the inter-PLMN cells to a specified downlink multi-carrier cell group.

----End

4.8.4.3.3 MML Command Examples

//On the RNC
//Turning on the function switch
SET UOPERATORSHARINGMODE:RANSharingSupport=YES,InterPlmnMultiCarrSwitch=YES;
//On the NodeB
ADD NODEBMULTICELLGRPITEM:MULTICELLGRPID=1, ULOCELLID=2;

4.8.4.3.4 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.8.4.4 Activation Observation

1. The current carrier group contains cells of only operator A and operator B. On
the Trace tab page of the WebLMT, initiate Uu interface tracing, as shown in
Figure 4-1.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 43

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

Figure 4-1 Uu interface tracing task

2. Enable the UE to set up PS services carried on the DC-HSDPA. The RB setup

message shows that DC-HSDPA is established and the primary and secondary
carriers belong to different operators, indicating that this function takes
effect.

4.8.4.5 Deactivation

4.8.4.5.1 Using MML Commands

Run the RNC MML command SET UOPERATORSHARINGMODE with
InterPlmnMultiCarrSwitch set to NO.

4.8.4.5.2 MML Command Examples

//On the RNC
//Turning off the function switch
SET UOPERATORSHARINGMODE:RANSharingSupport=YES,InterPlmnMultiCarrSwitch=NO;

4.8.4.5.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.8.4.6 Reconfiguration
None

4.8.5 Performance Monitoring

Before this function is enabled, only SC-HSDPA/SC-HSUPA is allowed. After this
function is enabled, inter-PLMN multi-carrier HSPA is allowed under the same
network conditions and it brings the following impacts:

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 44

WCDMA RAN
RAN Sharing Feature Parameter Description 4 Engineering Guidelines

● Values returned by counters related to multi-carrier setup and release, and to

the number of multi-carrier users increase.
● The HSDPA/HSUPA throughput of users increases.
For details about specific counters, see Multi-Carrier HSDPA Feature Parameter
Description and DC-HSUPA Feature Parameter Description.

4.8.6 Parameter Optimization

None

4.8.7 Troubleshooting
None

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 45

WCDMA RAN
RAN Sharing Feature Parameter Description 5 Parameters

5 Parameters

The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
Base station controller parameter reference
● BSC6900 UMTS Parameter Reference: contains the parameters related to the
BSC6900 equipment, transport, and radio access functions.
● BSC6910 UMTS Parameter Reference: contains the parameters related to the
BSC6910 equipment, transport, and radio access functions.
NodeB parameter reference
● Node Parameter Reference: contains base station equipment and transport
parameters.
● NodeBFunction Parameter Reference: contains all parameters related to radio
access functions, including air interface management, access control, mobility
control, and radio resource management.
NOTE

You can find the EXCEL files of parameter reference for the software version on the live
network from the product documentation delivered with that version.

FAQ: How do I find the parameters related to a certain feature from

parameter reference?

Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, WRFD-170201.
Step 3 Click OK. All parameters related to the feature are displayed.

----End

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 46

WCDMA RAN
RAN Sharing Feature Parameter Description 6 Counters

6 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
Base station controller performance counter reference
● BSC6900 UMTS Performance Counter Reference: contains the counters related
to the BSC6900 equipment, transport, and radio access functions.
● BSC6910 UMTS Performance Counter Reference: contains the counters related
to the BSC6910 equipment, transport, and radio access functions.
NodeB performance counter reference
● Node Performance Counter Reference: contains base station equipment and
transport counters.
● NodeBFunction Performance Counter Reference: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE

You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from

performance counter reference?

Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, WRFD-170201.
Step 3 Click OK. All counters related to the feature are displayed.

----End

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 47

WCDMA RAN
RAN Sharing Feature Parameter Description 7 Glossary

7 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 48

WCDMA RAN
RAN Sharing Feature Parameter Description 8 Reference Documents

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

Issue 01 (2018-04-20) Copyright © Huawei Technologies Co., Ltd. 49