RAN Feature Documentation - MOCN - 20231121 091122 - 091357

WCDMA RAN
RAN23.1
RAN Feature Documentation
Issue Date 2023-05-12
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. 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]
Contents
Contents.........................................................................................................................................................................................1
1 MOCN...........................................................................................................................................................................................2
1 MOCN
WCDMA RAN
RAN20.1
MOCN Feature Parameter Description
Issue 02
Date 2018-10-30
2024-11-25 2
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2023. 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]
1 About This Document
1.1 Scope
1.2 General Statements
1.3 Change History
1.4 Differences Between NodeB Types
2 Overview
2.1 Background
2.2 Introduction
2.3 Benefits
2.4 Architecture
3 Carrier Sharing by Operators
3.1 System Information Broadcast
3.2 Network Selection
3.2.1 Network Selection for a Supporting UE
3.2.2 Network Selection for a Non-supporting UE
3.3 CS/PS Domain Registration Coordination
4 Dedicated NodeB and Cell for Operators
2024-11-25 3
5 MOCN Mobility Management

5.1 Inter-PLMN Handovers
5.2 Inter-RNC Relocation
5.3 Inter-PLMN Multi-Carrier HSPA
5.4 Handover Parameters Belonging to Each Operator
6 MOCN Load Balancing
7 Routing Roaming UEs in Proportion
8 MOCN Independent Performance Management
9 MOCN Cell Resource Demarcation
9.1 Overview
9.2 Predefined Percentages of Available Cell Resources
9.3 Admission and Preemption
9.3.1 Admission
9.3.2 Preemption
9.4 Congestion Control
9.5 Scheduling
9.6 Related Features
9.7 Network Impact
9.7.1 System Capacity
9.7.2 Network Performance
10 MOCN Independent CE Resource Allocation
10.1 Overview
10.1.1 Introduction
10.1.2 Benefits
10.2 Allocating CE Resources to Operators
10.3 NodeB Allocating CE Resources to UEs
10.4 RNC Relieving CE Congestion per Operator
10.6 Network Impact
11 MOCN Independent Iub Transmission Resource Allocation
11.1 Overview
11.1.1 Benefits
11.2 Configuring Operator-Specific Logical Ports
11.3 Identifying the UE's Serving Operator
11.5 Network Impact
12 Single CN With Multi-PLMN IDs
12.1 Overview
12.2 Broadcasting Multiple PLMN IDs by the RAN
2024-11-25 4
12.3 Configuring the CN Sharing Relationship Among Operators

12.4 Selecting a Route by the RNC
12.5 Providing Services for UEs of Multiple Operators by the Shared CN
12.7 Network Impact
13 Forbidding UEs of Specific Operators from Setting Up CS Services
13.1 Overview
13.2 Call Setup Procedure
13.2.1 Calls Initiated by UEs in Idle Mode
13.2.2 Calls Initiated by UEs in the CELL_FACH State
13.2.3 Calls Initiated by UEs in the CELL_DCH State
13.2.4 Relocation to the Current Cell
13.4 Network Impact
14 Engineering Guidelines
14.1 MOCN Introduction Package
14.1.1 When to Use MOCN Introduction Package
14.1.2 Required Information
14.1.3 Deployment
14.1.3.1 Requirements
14.1.3.2 Precautions
14.1.3.3 Activation (Using MML Commands)
14.1.3.4 Activation (Using the MAE-Deployment)
14.1.3.5 Activation Observation
14.1.3.6 Deactivation (Using MML Commands)
14.1.3.7 Deactivation (Using the MAE-Deployment)
14.1.3.8 MML Command Examples
14.1.4 Performance Monitoring
14.2 Routing Roaming UEs in Proportion
14.2.1 When to Use Routing Roaming UEs in Proportion
14.2.2 Requirements
14.2.3 Deployment
14.3 MOCN Cell Resource Demarcation
14.3.1 When to Use
14.3.3 Deployment
14.3.5 Parameter Optimization
2024-11-25 5
14.3.6 Troubleshooting
14.4 MOCN Independent CE Resource Allocation
14.4.1 When to Use MOCN Independent CE Resource Allocation
14.4.3 Deployment
14.5 MOCN Independent Iub Transmission Resource Allocation
14.5.1 When to Use MOCN Independent Iub Transmission Resource Allocation
14.5.3 Deployment
14.6 Single CN With Multi-PLMN IDs
14.6.1 When to Use Single CN With Multi-PLMN IDs
14.6.3 Deployment
14.7 Forbidding UEs of Specific Operators from Setting Up CS Services
14.7.1 When to Use Forbidding UEs of Specific Operators from Setting Up CS Services
14.7.3 Planning
14.7.3.1 RF Planning
14.7.3.2 Network Planning
14.7.3.3 Hardware Planning
14.7.4 Deployment
14.7.4.1 Deployment Process
14.7.4.4 Hardware Adjustment
14.7.4.5 Data Preparation and Feature Activation
14.7.4.5.1 Data Preparation
14.7.4.5.2 Using the MAE-Deployment
14.7.4.5.3 Using MML Commands
14.7.4.5.4 MML Command Examples
14.7.4.7 Deactivation
2024-11-25 6

14.7.4.8 Reconfiguration
15 Parameters
16 Counters
17 Glossary
18 Reference Documents
 1.1 Scope
 1.2 General Statements
 1.3 Change History
 1.4 Differences Between NodeB Types
1.1 Scope
This document describes MOCN, including its technical principles, related features, network
impact, and engineering guidelines.
This document covers the following features:
 WRFD-021311 MOCN Introduction Package
 WRFD-02131101 Carrier Sharing by Operators
 WRFD-02131102 Dedicated NodeB/Cell for Operators
 WRFD-02131103 MOCN Mobility Management
 WRFD-02131104 MOCN Load Balance
 WRFD-02131105 MOCN Independent Performance Management
 WRFD-02131106 Routing Roaming UEs in Proportion
 WRFD-140223 MOCN Cell Resource Demarcation
 WRFD-150213 MOCN Independent Iub Transmission Resource Allocation
 WRFD-150214 MOCN Independent CE Resource Allocation
1.2 General Statements
Purpose
Feature Parameter Description documents are intended to acquaint readers with:
 The technical principles of features and their related parameters
2024-11-25 7
 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
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 and any related parameters affected by
editorial changes
RAN20.1 02 (2018-10-30)
Compared with Issue 01 (2018-04-20) of RAN20.1, Issue 02 (2018-10-30) of RAN20.1 includes

the following changes.
Change Change Description Parameter
Type Change
Feature Added the following description: You do not need to configure the OSP for None
change each operator on the Iur interface. For details, see 14.1.3.3 Activation
(Using MML Commands).
Editorial None None

change
RAN20.1 01 (2018-04-20)
2024-11-25 8
This issue does not include any changes.
RAN20.1 Draft A (2018-02-05)
Compared with Issue 04 (2018-01-10) of RAN19.1, Draft A (2018-02-05) of RAN20.1 includes the
following changes.
Change Change Description Parameter Change
Type
Feature Added the counter VS.TCP.NonHS.Usage.Mean ( None

change BSC6910 , BSC6900 ) for calculating the cell non-
HSPA TCP power load. For details, see 14.3.4
Performance Monitoring.
Added the methods for the RNC to obtain the PLMN ID Added the
of the UE's operator when the IE "selected PLMN" is MulPLMNSingleCNOPByIMSIS
not contained in the COMMON ID or RELOCATION W ( BSC6910 , BSC6900 )
REQUEST message sent from the CN. For details, see parameter.
12.5 Providing Services for UEs of Multiple Operators
by the Shared CN.
Editorial None None

change
1.4 Differences Between NodeB Types
Feature Support by Macro, and LampSite NodeBs
Feature ID Feature Name Supported by Supported by Supported by

RNCs Macro NodeBs LampSite NodeBs
BSC690 BSC691
0 0
WRFD- MOCN Introduction Package Yes Yes Yes Yes

021311
WRFD- Carrier Sharing by Operators Yes Yes Yes Yes

02131101
WRFD- Dedicated NodeB/Cell for Yes Yes Yes Yes

02131102 Operators
WRFD- MOCN Mobility Management Yes Yes Yes Yes

02131103
WRFD- MOCN Load Balance Yes Yes Yes Yes

02131104
WRFD- MOCN Independent Yes Yes Yes Yes

02131105 Performance Management
WRFD- Routing Roaming UEs in Yes Yes Yes Yes

02131106 Proportion
WRFD- MOCN Cell Resource Yes Yes Yes Yes

140223 Demarcation
2024-11-25 9
Feature ID Feature Name Supported by Supported by Supported by

RNCs Macro NodeBs LampSite NodeBs
WRFD- MOCN Independent Iub Yes Yes Yes Yes

150213 Transmission Resource
Allocation
WRFD- MOCN Independent CE Yes Yes Yes Yes

150214 Resource Allocation
 2.1 Background
 2.2 Introduction
 2.3 Benefits
 2.4 Architecture
2.1 Background
Launching a 3G network requires considerable investment. If different operators jointly deploy
the network and share the network infrastructure, investment in the 3G network can be lowered.
In addition, this can also shorten the time to market for the network.
To enable operators to share some network elements (NEs) in the 3G network, the Iu Flex and
RAN Sharing features were introduced in 3GPP Release 5 (R5) and the MOCN feature in 3GPP
Release 6 (R6). For details about the Iu Flex and RAN Sharing features, see Iu Flex Feature
Parameter Description and RAN Sharing Feature Parameter Description , respectively.
2.2 Introduction
The MOCN feature can save investment in site leasing, site construction, transmission
equipment, and RAN equipment. It allows operators to have independent CNs, services, and
billing. Different from RAN sharing, MOCN enables multiple operators to share carrier resources
to improve network resource utilization.
With MOCN, RAN nodes (RNC and NodeB) and resources are shared by operators. Any UTRAN
feature cannot be independently controlled by different operators.
2.3 Benefits
 The MOCN feature can save investment in site leasing, site construction, transmission
equipment, and RAN equipment. It allows operators to have independent CNs, services, and
billing.
 Compared with RAN sharing, MOCN improves network resource utilization.
2.4 Architecture
In the MOCN solution, operators share all access network resources (including spectrum
resources). Figure 2-1 shows the MOCN solution.
2024-11-25 10
Figure 2-1 MOCN solution
UEs complying with 3GPP Release 6 (R6) and later versions support MOCN, whereas UEs
complying with versions earlier than R6 do not support this solution. However, on the RAN side,
UEs can access the MOCN and be routed to a correct CN even if they do not comply with R6 or
later.
 The MOCN solution has two types of UEs:
 Supporting UEs: UEs that support MOCN. On the MOCN-based network, the RNC
broadcasts the PLMN information about multiple operators in the Multiple-PLMN LIST IE
in the system information. The supporting UEs must support the 3GPP R6 protocol.
 Non-supporting UEs: UEs that do not support MOCN. The non-supporting UEs cannot
decode the PLMN information of multiple operators in the system information.
 The spectrum utilization policy for the MOCN solution is as follows:
 The spectrum resources are provided by one operator and are shared among all
operators.
 The spectrum resources are provided by multiple operators and are shared among all
operators.
 The MOCN solution has the following characteristics and benefits:
 The shared network is constructed by one operator and shared by several other
operators. Alternatively, the shared network is constructed by multiple operators and
shared by all of them.
 The shared RAN connects to the CNs of multiple operators.
 Each operator is allowed to deploy Iu Flex, and the CN nodes within an operator's
network form a CN pool.
 The shared RAN automatically routes UEs to the subscriber's CNs.
2024-11-25 11
 The MOCN solution has the following limitations:
 Operators need to cooperate more closely because of decreased independence.
 The current solution provided by Huawei does not support MOCN and RAN sharing
simultaneously.
The Carrier Sharing by Operators feature enables multiple operators to share the RAN equipment
and carriers. One cell can belong to and serve different operators.
The Carrier Sharing by Operators feature consists of the following:
 System information broadcast
 Network selection
 CS/PS domain registration coordination
 3.1 System Information Broadcast
 3.2 Network Selection
 3.3 CS/PS Domain Registration Coordination
3.1 System Information Broadcast

Each cell in a shared RAN includes information about available CN operators sharing the network
in the broadcast system information. The RAN broadcasts the PLMN IDs in the master information
block (MIB). A UE decodes this information and selects a proper PLMN. Broadcast system
information is specified in section 10.2.48.8.1 Master Information Block in 3GPP TS 25.331
V6.4.0.
An MIB includes two types of PLMN identities: PLMN identity and Multiple PLMN identity. PLMN
identity specifies whether the common PLMN ID is used as the candidate serving operator for
supporting UEs. Multiple PLMN identity indicates the PLMN ID list of each operator in a MOCN
network. A supporting UE selects a proper PLMN from the list as its serving operator.
 If the value of CnOpIndexComm ( BSC6910 , BSC6900 ) is 255, the RNC sets the MIB
PLMN Identity to True. Under this circumstance, the first PLMN ID in the Multiple PLMN List is
used as the common PLMN ID, which identifies the serving operator for the non-supporting
UEs and also identifies a candidate operator for the supporting UEs.
 If the value of CnOpIndexComm ( BSC6910 , BSC6900 ) is greater than or equal to 5 and

less than or equal to 31, the RNC sets the MIB PLMN Identity to False. Under this
circumstance, a new PLMN ID is used as the common PLMN ID, which identifies only the
serving operator for the non-supporting UEs. The supporting UE selects the PLMN only from
the Multiple PLMN List.
The principles for MIB cell system information broadcast are as follows:
2024-11-25 12
 If an operator does not have the MOCN license, the Multiple-PLMN LIST does not include
PLMN ID for this operator.
 If the Iu-CS and Iu-PS signaling links provided by an operator are faulty and the RNC-level
PROCESSSWITCH ( BSC6910 , BSC6900 ): SYS_INFO_UPDATE_FOR_IU_RST is turned
on, the PLMN ID of this operator is deleted from the Multiple PLMN List IE in the MIB
message.
If the Iu-CS signaling link is faulty and the Iu-PS signaling link is normal, and if the RNC-level
PROCESSSWITCH ( BSC6910 , BSC6900 ): SYS_INFO_UPDATE_FOR_IU_RST,
BARRED_CELL_FOR_CSDOMAIN_RST and the cell-level NBMCacAlgoSwitch ( BSC6910 ,
BSC6900 ): SYS_INFO_UPDATE_FOR_IU_RST are turned on, the PLMN ID of this operator
is deleted from the Multiple PLMN List IE in the MIB message.
 If the Iu-PS signaling link is faulty and the Iu-CS signaling link is normal, or if the user-plane
link is faulty, the MIB message is not affected.
3.2 Network Selection

A UE decodes the broadcast system information to determine available CN operators in the
shared network. According to the network selection procedure defined in section 4.2.3 "Network
selection in a shared network" in 3GPP TS 23.251 V6.0.0, supporting UEs and non-supporting UEs
use different methods to select appropriate operators.
3.2.1 Network Selection for a Supporting UE

A supporting UE selects a favorable PLMN ID from the PLMN ID list of multiple operators
broadcast in the MIB and reports the PLMN ID to the RNC through the initial direct transfer
message. For the principle of how a UE selects a PLMN, see chapter 3 "PLMN Selection" in UE
Behaviors in Idle Mode Feature Parameter Description . For details, see "5.1 PLMN selection" in
3GPP TS 25.304 V10.0.0 and "4.4 PLMN selection process" in 3GPP TS 23.122 V10.0.0. The RNC
selects an operator based on the PLMN ID selected by the UE. Then, the RNC selects a CN node
based on the operator as follows:
 If the operator is not using the Iu Flex feature, the RNC directly selects the CN node
corresponding to the operator.
 If the operator is using the Iu Flex feature, the RNC selects a CN node of the operator based
on the NAS node selection function (NNSF). For details about the Iu Flex feature, see Iu Flex
Feature Parameter Description .
Figure 3-1 shows the registration process of a supporting UE in a shared cell. For details, see
section 7.1.5 Supporting UEs in a MOCN configuration in 3GPP TS 23.251 V6.0.0.
2024-11-25 13
Figure 3-1 Registration process of a supporting UE in a MOCN cell
The registration process is described as follows:
1. A supporting UE reads the broadcast system information in the shared RAN.
2. The UE decodes the shared network information and supplies the available CN operator
PLMN IDs as candidates to the PLMN selection procedure. The common PLMN is not given
as a candidate for network selection.
3. The UE performs network selection among available PLMNs.
4. The UE sends an ATTACH REQUEST message to the network and indicates to the RNC the
chosen CN operator. The RNC routes the UE to the chosen CN operator.
5. The CN determines whether the UE is allowed to attach.
6. The shared CN node sends the appropriate ACCEPT/REJECT message back to the UE. In
case of an ATTACH ACCEPT message, the CN assigns the UE an appropriate TMSI/P-TMSI so
that this identity can be used for any further rerouting of messages by the RNC.
3.2.2 Network Selection for a Non-supporting UE
Registration Process of Non-Supporting UEs
Different from a supporting UE, a non-supporting UE does not report the PLMN ID to the RNC
through the INITIAL DIRECT TRANSFER message. Before determining the CN node that the UE
should register with, the RNC initiates a polling attempt on each operator's CN, according to the
network selection policy described below, until the registration is accepted or a round of polling
ends. If the RNC finds no more MSC/SGSN to redirect after receiving a Reroute Command
message, the RNC compares the cause code with cause codes from other Reroute Command
messages it has earlier received for this UE. A cause code ranking is done and the "softest"
2024-11-25 14
cause code is chosen and the corresponding saved NAS attach reject message is returned to the
UE.
According to the section "Annex N (normative): Ranking of reject causes for Location Registration
(MM and GMM) in a shared network" in 3GPP TS 24.008 V12.1.0, the reject causes are arranged
as follows:
#11 (PLMN not allowed) > #12 (Location Area not allowed) > #13 (Roaming not allowed in this
location area) > #14 (GPRS services not allowed in this PLMN) > #15 (No Suitable Cells In
Location Area) > #25 (Not authorized for this CSG) > #17 (Network failure). (Note: #17 is the
softest reject cause. For reject causes other than the preceding ones, the larger the value of the
reject cause, the softer the reject cause.)
Figure 3-2 shows the 3GPP TS 23.251-defined registration process of non-supporting UEs in a
MOCN cell. For details, see section 7.1.4 "Non-supporting UEs in a MOCN configuration" in 3GPP
TS 23.251 V6.0.0.
Figure 3-2 Registration process of a non-supporting UE in a MOCN cell
As shown in Figure 3-2, the RNC cannot determine the CN to which the UE accesses. Therefore,
the RNC originates an attempt to Operator A. After the attempt is rejected, the RNC originates
another attempt to Operator B. After the attempt is rejected, the RNC originates another attempt
to Operator C. The polling is completed until Operator C accepts the UE registration request.
In actual implementation, to improve network efficiency, the RNC does not perform polling to
each operator in a certain sequence as shown in the preceding figure. Based on the network
selection policy and obtained information, the RNC determines the priority sequence of operators
during the polling to improve the attempt success rate.
RNC Network Selection Policies
2024-11-25 15
The network selection policies of the RNC are as follows:
 The RNC preferentially chooses the UE homing operator if it receives a UE IMSI.
 The RNC preferentially chooses the CN node mapped with the network resource identifier
(NRI) if it receives a correct and valid NRI from the TMSI/P-TMSI.
In scenarios other than the preceding two, the RNC preferentially chooses the CN node specified
by DefaultCnOp ( BSC6910 , BSC6900 ).
The RNC does not originate attempts in the following scenarios:
 The cell does not support the MOCN function (for example, the license does not support
MOCN, or the cell is configured with only one operator).
 For a supporting UE, the RNC can select the operator based on the PLMN ID contained by the
UE.
 The two domains of the UE originate registration on the same RRC connection. One domain
is registered successfully, and the attempt for the request of the other domain is not
originated.
 When a supporting UE initiates an emergency CS call but the RNC determines that all CS CNs
of the operator selected by the UE are faulty, the RNC reroutes the UE as a non-supporting
UE to an available CN of another operator for successfully admitting the emergency call. It is
good practice to select EMER_CSFB_MOCN_AS_NON_MOCN_SWITCH under the
MocnControlSwitch2 ( BSC6910 , BSC6900 ) parameter in the SET
UOPERATORSHARINGMODE command to enable this function. By default, this function is
disabled. When the UE initiates a PS service during the emergency call, the RNC selects a PS
CN of the same operator as the CS CN. If a roaming agreement is not signed among
operators, the PS service fails.
 If END_REROUTE_CN_NORESPONSE_SWITCH is selected under the

UOPERATORSHARINGMODE command, the RNC does not initiate any redirection attempt
to the CN of other operators when the RNC carries the redirection attempt flag in the Initial
UE Message to the CN and the CN does not carry the IE "Redirection Completed" or
"Redirection Indication" in the Direct Transfer Message to the RNC.
3.3 CS/PS Domain Registration Coordination

After MOCN is introduced, the CS and PS domains for a non-supporting UE may be registered
with different operators. MOCN uses the following methods to ensure CS/PS domain registration
coordination. For details, see section 4.2.5 PS and CS domain registration coordination in 3GPP
TS 23.251 V6.0.0.
 If the Gs interface is available between the MSC and the SGSN, the SGSN is used to ensure
CS/PS domain registration coordination because the registration information in the CS
domain is forwarded by the PS domain.
2024-11-25 16
 If the Gs interface is unavailable between the MSC and the SGSN, the RNC is used to ensure
CS/PS domain registration coordination. During the initial registration of a UE, the CN sends
the UE a direct transfer message including Redirection Indication. The message also includes
a reject cause code ''CS/PS coordination required", instructing the RNC to ensure
coordination. Therefore, the RNC includes an IMSI in the subsequent Initial UE Message,
indicating that coordination is ensured.
The RNC implements CS/PS domain registration coordination as follows:
 After a UE is powered on, the RNC first registers the UE in the CS domain and then registers
it in the PS domain of the same operator.
 For a UE in connected mode, the RNC selects the operator in the domain with the existing
signaling connection on the Iu interface.
 If the RNC cannot identify the serving CN operator for a UE, run the SET
UOPERATORSHARINGMODE command and set the DefaultCnOp ( BSC6910 , BSC6900
) parameter as required so that the UE is preferentially registered in the CS and PS domains
of the default operator.
UEs in idle mode may not register the CS and PS domains simultaneously and the RNC does not record the
ID of the operator where the UEs have registered. Therefore, the RNC may not ensure CS/PS domain
registration coordination for UEs in idle mode.
To meet the special requirements of different operators, the RNC is connected to dedicated
NodeBs of these operators. Besides, the RNC can be connected to a shared NodeB of multiple
operators. The dedicated NodeB, called non-shared NodeB (WRFD-02131102 Dedicated
NodeB/Cell for Operators), serves only one operator. The shared NodeB of multiple operators is
also known as MOCN NodeB. Figure 4-1 shows two types of NodeB networking.
Figure 4-1 Two types of NodeB networking
A dedicated NodeB belongs only to its dedicated operator. All the UEs that access the network
from this NodeB will be connected to the CN node of its dedicated operator.
An MOCN NodeB belongs to multiple operators. It can be configured with both dedicated cells
and shared cells. UEs accessing a dedicated cell of the MOCN NodeB can only connect to the CN
2024-11-25 17
of the operator owning the cell, whereas UEs accessing a shared cell can automatically connect
to the CN belonging to the HPLMN operator of the UEs. This relationship is supported by the RNC
but has the following application requirement or impact:
 The MAE cannot distinguish operators when reporting traffic statistics and alarms to the
network management system (NMS).
 Features to be activated for the dedicated cells are under the license control of the primary
operator.
Each operator can have an independent base station transmission port, or multiple operators
share a base station transmission port.
If multiple operators share a transmission port, the attributes of the transmission port and the
values of each attribute should be appropriately configured based on the backhaul network
performance, for example the maximum transmission unit (MTU), of each operator.
If the MTU value of each operator's backhaul network is different, the MTU value on the
transmission port can be configured as MIN(MTU1,MTU2,MTU3...). As a result, all over-long
packets are fragmented on the base station. The MTU value can also be configured as
MAX(MTU1,MTU2,MTU3...). In this way, the fragmentation and reassembly for networks with a
large backhaul network MTU value can be reduced. For networks with a small backhaul network
MTU value, some packets are moved upward to routers for fragmentation purposes.
A UE performs location area (LA) or routing area (RA) update and attach, which may result in a
change of the serving CN node.
MOCN mobility management (WRFD-02131103 MOCN Mobility Management) determines whether
to hand over a UE to a target cell based on the PLMN ID of the target cell and the PLMN ID of the
CN operator to which the UE belongs.
The handover types in this chapter include all handover types described in the Handover Feature
Parameter Description .
 5.1 Inter-PLMN Handovers
 5.2 Inter-RNC Relocation
 5.3 Inter-PLMN Multi-Carrier HSPA
 5.4 Handover Parameters Belonging to Each Operator
5.1 Inter-PLMN Handovers

Generally, an inter-PLMN handover is not allowed among operators. To determine whether to
allow the inter-PLMN handover, perform the following operations on the RNC:
 In intra-RAT scenarios, if the InterPlmnHoAllowedIntraRat ( BSC6910 , BSC6900 )

parameter in the SET UOPERATORSHARINGMODE command is set to YES, the RNC
2024-11-25 18
supports inter-PLMN intra-RAT handovers and UEs can move between PLMNs. If this
parameter is set to NO, the RNC does not support inter-PLMN intra-RAT handovers.
 In inter-RAT scenarios, if the InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 )

parameter in the SET UOPERATORSHARINGMODE command is set to YES, the RNC
supports inter-PLMN inter-RAT handovers and UEs can move between PLMNs. If this
parameter is set to NO, the RNC does not support inter-PLMN inter-RAT handovers.
When InterPlmnHoAllowedIntraRat ( BSC6910 , BSC6900 ) or
InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 ) is set to YES:
If the TarCnOpIndex ( BSC6910 , BSC6900 ) parameter is configured for a UE's serving
operator by running the ADD UINTERPLMNHOLIST command, the RNC delivers only the
neighboring cells/frequencies that belong to the serving operator or the cells/frequencies
that belong to the target operator specified in the UINTERPLMNHOLIST MO, when
selecting target neighboring cells or frequencies during UMTS-to-LTE, UMTS-to-UMTS, and
UMTS-to-GSM handovers. In this way, UEs served by different operators can be handed over
to different target neighboring cells/frequencies in the inter-PLMN handover list.
If the UINTERPLMNHOLIST MO is not configured for the UE's serving operator, the RNC
delivers all configured neighboring cells/frequencies to the UE.
Inter-PLMN handovers affect the following operations: configuring neighboring cells, processing
measurement control messages, and deciding handovers and cell updates.
Configuring Neighboring Cells
The CnOpGrpIndex ( BSC6910 , BSC6900 ) parameter in the ADD UCNOPERGROUP

command specifies the operator group index for a neighboring RNC (NRNC) or an inter-RAT
neighboring cell. If operators configured for the NRNC or inter-RAT neighboring cell do not exist
in the SRNC, run the ADD UCNOPERATOR command to add outer operators and configure the
corresponding operator group based on the operator to which the NRNC or inter-RAT neighboring
cell belongs.
Processing Measurement Control Messages
Before delivering an intra-frequency, inter-frequency, or inter-RAT measurement control

message, the RNC checks whether the PLMN ID of the UE is on the PLMN ID list of the
neighboring cell if both the following conditions are met:
 InterPlmnHoAllowedIntraRat ( BSC6910 , BSC6900 ) or

InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 ) in the SET
UOPERATORSHARINGMODE command is set to NO.
 The PLMN ID of the UE is valid.
Then, the RNC filters out the information about the cells belonging to different operators and
delivers only the information about the neighboring cells belonging to the same operator. If the
2024-11-25 19
PLMN that the UE accesses is not determined, the RNC delivers the information about all the
neighboring cells. After the PLMN is determined, the RNC delivers the information about
neighboring cells again, including the information about the neighboring cells of the PLMN that
the UE does not access.
If InterPlmnHoAllowedIntraRat ( BSC6910 , BSC6900 ) or InterPlmnHoAllowedInterRat (
BSC6910 , BSC6900 ) in the SET UOPERATORSHARINGMODE command is set to YES, the
neighboring cell list is generated in compliance with the settings in the ADD
UINTERPLMNHOLIST command.
Deciding Handovers and Cell Updates
If InterPlmnHoAllowedIntraRat ( BSC6910 , BSC6900 ) or InterPlmnHoAllowedInterRat (

BSC6910 , BSC6900 ) in the SET UOPERATORSHARINGMODE command is set to NO,
handovers and cell updates are allowed only when the PLMN ID of the UE is in the target cell
operator list. If either InterPlmnHoAllowedIntraRat ( BSC6910 , BSC6900 ) or
InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 ) is set to YES, the neighboring cell list
is generated in compliance with the settings in the ADD UINTERPLMNHOLIST command.
The SRNC determines whether to allow cell update or UTRAN registration area (URA) update
after receiving the PLMN ID list of the target cell.
When a radio link is being set up or added over the Iur interface, the SRNC receives the PLMN ID
list of the configured neighboring UMTS cell of the target cell on the DRNC and makes the next
handover decision based on the PLMN ID list. The neighboring cell of the target cell may or may
not be configured on the SRNC. The RNSAP RL SETUP RSP/RNSAP RL ADD RSP IE in the message
carries the PLMN ID list of neighboring cells only when UNRNC.RncProtclVer ( BSC6910 ,
BSC6900 ) is set to R7 or later on the DRNC. Otherwise, after the SRNC receives the neighboring
cell information from the DRNC, the SRNC determines that the target cell does not belong to the
same PLMN because the DRNC does not carry the PLMN ID list. As a result, the handover is
prohibited.
 If the neighboring cell of the target cell has not been configured on the SRNC:
 If HO_MC_NCELL_COMBINE_SWITCH under the HoSwitch ( BSC6910 , BSC6900 )

parameter is selected in the SET UCORRMALGOSWITCH command, the neighboring
cells are added to the neighboring cell list of the UE regardless of whether the cell is the
best cell.
 If the switch is turned off, the neighboring cells are added to the neighboring cell list of
the UE when the target cell is the best cell.
 If the DRNC does not send the SRNC the PLMN ID list, the SRNC may be unable to make
a handover decision. Only after receiving a RADIO LINK SETUP/ADDITION RESPONSE
message from the DRNC, the SRNC can make a handover decision according to the
PLMN ID in the Service Area Identity (SAI).
 If the neighboring cell of the target cell has been configured on the SRNC, the PLMN ID list
sent by the DRNC is used.
2024-11-25 20
When a radio link is being set up or added over the Iur interface, the SRNC receives the
PLMN ID list of the configured neighboring GSM cell of the target cell on the DRNC and
makes the next inter-RAT handover decision based on the PLMN ID list.
If HO_GSMNCELL_OPGRP_CARRY_OVER_IUR_SWITCH is selected under the HoSwitch1 (
BSC6910 , BSC6900 ) parameter in the RNC MML command SET UCORRMALGOSWITCH,
the DRNC adds the operator PLMN list proprietary IE shared by GSM cells to the Neighboring
GSM Cell Information IE in the Radio Link Setup Response or Radio Link Addition Response
message and sends the message to the SRNC. Then, according to the preceding information,
the SRNC selects appropriate neighboring GSM cells to initiate the inter-RAT handover or
measurement control.
3GPP TS 25.423 V11.6.0 introduces the standard IE "Multiple PLMN List" for neighboring GSM
cells. If HO_GSMNCELL_OPGRP_CARRY_OVER_IUR_SWITCH2 is selected under the
HoSwitch1 ( BSC6910 , BSC6900 ) parameter in the RNC MML command SET
UCORRMALGOSWITCH, the DRNC adds the operator PLMN list standard IE shared by GSM
cells to the Neighboring GSM Cell Information IE in the Radio Link Setup Response or Radio
Link Addition Response message and sends the message to the SRNC. Then, according to
the preceding information, the SRNC selects appropriate neighboring GSM cells to initiate
the inter-RAT handover or measurement control.
After receiving from the DRNC the operator PLMN list IE for neighboring GSM cells, the SRNC
filters these cells as follows:
 If the InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 ) parameter is set to YES,

a neighboring GSM cell is not filtered and the neighboring GSM cell information is added
to the measurement control message when the inter-RAT measurement control
message is being delivered.
 If the InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 ) parameter is set to NO,

a neighboring GSM cell is not filtered and the neighboring GSM cell information is added
to the measurement control message when the serving operator of the UE is included in
the cell's operator group and the inter-RAT measurement control message is being
delivered. Otherwise, this cell is filtered out.
If the DRNC does not support carrying the neighboring GSM cell PLMN list IE and
InterPlmnHoAllowedInterRat ( BSC6910 , BSC6900 ) is set to NO, neighboring GSM cells are
filtered depending on whether HO_INTER_RAT_DRNC_GSMNCELL_FILTER_SWITCH is selected
under the HoSwitch1 ( BSC6910 , BSC6900 ) parameter in the SET UCORRMALGOSWITCH
command. This parameter is valid only when the DRNC does not transfer the neighboring GSM cell
PLMN list IE.
 If HO_INTER_RAT_DRNC_GSMNCELL_FILTER_SWITCH under the HoSwitch1 parameter is

selected, neighboring GSM cells are filtered. The information about a neighboring GSM cell for a
DRNC cell is added to the measurement control message only when the neighboring GSM cell's
operator is consistent with the UE's operator.
 If HO_INTER_RAT_DRNC_GSMNCELL_FILTER_SWITCH under the HoSwitch1 parameter is
deselected, neighboring GSM cells are not filtered and the information about these cells is
allowed to be sent to the UE for the inter-RAT handover or measurement control.
2024-11-25 21
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 ( BSC6910 , BSC6900 ) is selected,

UEs of the operator are not allowed for service-based inter-RAT handovers.
 If HO_IRAT_SERV_FORBID_SWITCH under HoSwitch ( BSC6910 , BSC6900 ) is not

selected, UEs of the operator are allowed for service-based inter-RAT handovers.
For details about the conditions for service-based handovers, see Handover Feature Parameter
Description .
5.2 Inter-RNC Relocation

During inter-RNC relocation, if the SRNC can determine the CN operator of the target network
according to the available MOCN information, current PLMN ID, or similar information, the SRNC
specifies the selected CN operator to the target network.
 For inter-PLMN relocation from a dedicated cell or shared MOCN cell to a dedicated cell, the
RNC sets the PLMN in the target RNC ID in the RELOCATION REQUIRED message to the PLMN
configured for the cell. The source CN decodes the RELOCATION REQUIRED message and
forwards it to the target CN, if required.
 For relocation from one dedicated cell or shared MOCN cell to another shared MOCN cell, if
the RNC cannot determine the operator to which the UE is relocated, the RNC sets the PLMN
in the target RNC ID in the RELOCATION REQUIRED message to the common PLMN
configured for the cell. The source CN selects a CN to forward the message. The target CN
sends the target RNC (TRNC) the RELOCATION REQUEST message carrying the selected
PLMN. The TRNC notifies the UE of the new PLMN ID through the UE configuration message.
Non-supporting UE obtains the new PLMN ID from the PLMN identity in the message.
Supporting UE obtain the new PLMN ID from the Primary PLMN identity in the message.
5.3 Inter-PLMN Multi-Carrier HSPA

Different carriers may belong to different operators because a shared RNC can support common
carriers and dedicated carriers. The InterPlmnMultiCarrSwitch ( BSC6910 , BSC6900 )
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 ( BSC6910 , BSC6900 ) 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 ( BSC6910 , BSC6900 ) is set to YES,
 when TarRAT ( BSC6910 , BSC6900 ) and TarCnOpIndex ( BSC6910 , BSC6900 ) are

not set in the ADD UINTERPLMNHOLIST command, multi-carrier HSPA is allowed no
2024-11-25 22
matter whether the UE's serving operator is one of the operators that provide both primary
and secondary carriers or not.
 when TarRAT ( BSC6910 , BSC6900 ) and TarCnOpIndex ( BSC6910 , BSC6900 ) 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.
If the secondary carrier supports DC-HSUPA and UEs' services can be carried over DC-HSUPA,
inter-PLMN DC-HSUPA can be allowed.
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 .
5.4 Handover Parameters Belonging to Each Operator

Operator in an operator group can be configured with different inter-frequency measurement
triggering and stopping thresholds to meet handover requirements of different operators. For
example, when a UE is at the edge between a shared cell and a dedicated cell, the handover
success rate is increased if different operators are configured with different inter-frequency
measurement triggering and stopping thresholds. To obtain the engineering guidelines on this
function, see Configuring Inter-PLMN Mobility Management.
During interoperability between UMTS and LTE, the U2LAlgoSwitch ( BSC6910 , BSC6900 )
parameter can independently control whether each operator in the operator group uses the
Measurement-based Fast Return from UMTS to LTE and UMTS-to-LTE (U2L) PS
Redirection/Handover functions. The independent control mechanism allows operators to use
different U2L mobility policies. For related technical principles and engineering guidelines, see
Interoperability Between UMTS and LTE Feature Parameter Description.
The RNC selects a proper operator for UEs that do not support MOCN through the redirection
function. In some scenarios, more than one operator may serve a UE (for example, a roaming
2024-11-25 23
UE). In this case, the load balancing mechanism is required to ensure load balancing among
operators and fairness to each operator in using shared network resources.
If the previous conditions are met, the RAN node selects a CN node with light load from all the
CN nodes connected to the RNC. In the same pool area, the network loads can be evenly
distributed among the CN nodes without changing the functionality of the original serving CN
node. Therefore, the imbalance of resource usage among different CN nodes on the traditional
mobile network in different traffic peak hours can be effectively avoided and the load balancing
among CN nodes can be achieved.
Loading balancing may increase the possibility that a UE is registered in the CS and PS domains
of different CN nodes. Therefore, it is recommended that geographical area-based rather than
intra-RNC load balancing be deployed on commercial networks. Under the RNCs in some
geographical areas, a third-party UE that has roaming relationships with multiple operators
preferentially tries a shared operator CN. Under the RNCs in other geographical areas, this type
of UE preferentially tries another shared operator CN.
For details about load balancing among CN nodes of an operator, see Iu Flex Feature Parameter
Description .
This section describes the WRFD-02131106 Routing Roaming UEs in Proportion feature.
When a UE roams to an RNC shared among multiple operators and the home operator of the UE
has signed roaming agreement with these operators, the RNC needs to select a proper operator's
CN node for the UE.
 If the roaming UE is a supporting UE, the UE selects a PLMN from the Multiple PLMN List field
of the MIB and then sends the PLMN to the RNC. The RNC then routes the UE to the CN node
of the selected PLMN.
 If the UE is a non-supporting UE, the RNC selects a CN node for the UE by using the function
of routing roaming UEs in proportion.
After the function of routing roaming UEs in proportion is introduced, the ADD UROAMMAP
command can be used at a shared RNC to configure roaming relationships between operators
and the roaming capacity ratio. Based on the configurations, the RNC can distribute load among
CN nodes. Assume that operator A has roaming relationships with operators B, C, and D
(operators B, C, and D share one RNC), as described in Table 7-1.
Table 7-1 Roaming capacity ratio between operators
Operator Having Roaming Relationships with Operator Operator Operator
Operator A B C D
Roaming capacity 10 20 10
Then, the roaming capacity ratio between B, C, and D is 10:20:10, that is, 1:2:1. That is,
considering operator A's UEs roaming to the shared RNC, one fourth of the UEs will be routed to
operator B's CN nodes, two fourths to operator C's CN nodes, and one fourth to operator D's CN
nodes.
The roaming capacity ratio is specified by the AvailRoamCap ( BSC6910 , BSC6900 )
parameter in the ADD UROAMMAP command.
2024-11-25 24
For a non-supporting UE roaming to a shared RNC, the method of selecting a CN node is as

follows:
 If the UE sends its IMSI to the RNC, the RNC obtains the PLMN information according to the
UE's IMSI. Then, the RNC selects an operator and the corresponding CN node based on the
configured roaming relationships and the roaming capacity ratio.
 If the UE sends its TMSI/P-TMSI to the RNC, the RNC selects a CN node according to the NRI.
If the selected CN node rejects the access of the UE or requires the RNC to ensure CS/PS
domain registration coordination, the CN sends the UE's IMSI to the RNC. After receiving the
IMSI, the RNC selects an operator and the corresponding CN node based on the configured
roaming relationships and the roaming capacity ratio.
If the CN node does not support CS/PS consistency check, the RNC cannot obtain the UE's IMSI. In
this case, the RNC selects a CN node of the default operator. If a CN node fails to be selected, the
RNC attempts to select a CN node by using the method described in section 6 MOCN Load
Balancing. This does not ensure that roaming UEs are routed in proportion.
The RNC supports independent performance management for different operators (WRFD-
02131105 MOCN Independent Performance Management). This feature enables operators to
independently obtain the information about network operation such as traffic and network
quality. That is, operators can obtain traffic volumes and network quality information related to
their specific usage and UEs attached to them.
In addition, the performance counters related to MOCN (for example, the redirection with various
causes) are added to the RNC performance counters.
When the RNC receives the RANAP DIRECT TRANSFER message (carrying the redirection
indication) from the CN, as indicated by B in Figure 8-1, it measures the counters listed in Table
8-1.
Figure 8-1 Measurement of redirection due to different causes
Table 8-1 Redirection counters and related causes

Counter Cause of Redirection
VS.IU.MOCN.CsPsCoordination ( BSC6910 Number of Redirection Requests from CN (CS/PS

, BSC6900 ) Coordination Required)
VS.IU.MOCN.LocAreaNotAllowed ( Number of Redirection Requests from CN (Location

BSC6910 , BSC6900 ) Area Not Allowed)
VS.IU.MOCN.PlmnNotAllowed ( BSC6910 , Number of Redirection Requests from CN (PLMN
2024-11-25 25
Counter Cause of Redirection
BSC6900 ) Not Allowed)
VS.IU.MOCN.RoamNotAllowed ( BSC6910 Number of Redirection Requests from CN (Roaming

, BSC6900 ) Not Allowed in this Location Area)
VS.IU.MOCN.NoSuitableCell ( BSC6910 , Number of Redirection Requests from CN (No

BSC6900 ) Suitable Cell in Location Area)
VS.IU.MOCN.GprsServicesNotAllowed ( Number of Redirection Requests from CN (GPRS

BSC6910 , BSC6900 ) Services Not Allowed in this PLMN)
VS.IU.MOCN.NetworkFailure ( BSC6910 , Number of Redirection Requests from CN (Network

BSC6900 ) failure)
VS.IU.MOCN.NotAuthorizedforthisCSG ( Number of Redirection Requests from CN (Not

BSC6910 , BSC6900 ) authorized for this CSG)
 9.1 Overview
 9.2 Predefined Percentages of Available Cell Resources
 9.3 Admission and Preemption
 9.4 Congestion Control
 9.5 Scheduling
 9.6 Related Features
 9.7 Network Impact
9.1 Overview
In MOCN networking scenarios, the MOCN Cell Resource Demarcation feature (corresponding to
feature WRFD-140223 MOCN Cell Resource Demarcation) introduced in RAN14.0 prevents UEs of
an operator from occupying excessive cell resources. This ensures fairness to each operator in
using shared cell resources. With this feature, the percentage of cell resources available for each
operator in a shared MOCN cell is configurable. The available cell resources configurable for each
operator are DL R99 SCs, HSDPA power resources, and total downlink power resources. For
details, see 9.2 Predefined Percentages of Available Cell Resources.
As shown in Figure 9-1, after this feature is enabled, the RNC and NodeB manage DL R99 SCs
and HSDPA power resources in a shared MOCN cell as follows:
 The RNC performs admission, preemption, and congestion control.

When cell resources are sufficient, the RNC admits UEs without differentiating between
operators. UEs of any operator can use more resources than the predefined resource
percentage. For details, see 9.3.1 Admission. When a UE cannot be admitted due to
insufficient cell resources, the RNC determines whether to trigger preemption based on the
actual percentage of resources each operator is using. For details, see 9.3.2 Preemption.
2024-11-25 26
When congestion triggered by insufficient DL R99 SCs occurs in the cell, the RNC
preferentially performs flow control on R99 UEs whose operator exceeds the predefined
percentage of DL R99 SCs the most. For details, see 9.4 Congestion Control.
 The NodeB adjusts the scheduling priority and performs scheduling for HSDPA UEs.
This adjustment is based on the actual percentage of HSDPA power resources each operator
is using and the percentage of available HSDPA power resources predefined for each
operator. The real-time scheduling priority adjustment ensures that the NodeB schedules
resources as they are demarcated whenever possible. For details, see section 9.5
Scheduling.
Figure 9-1 Resource management
The RAN manages other resources in a shared MOCN cell in the same way it manages them in a
non-MOCN cell. For details, see Load Control Feature Parameter Description .
This feature requires that the RNC sends information about operators and their predefined resource
percentages to the NodeB. The information is carried in proprietary IEs in Iub interface messages. For
details, see 9.5 Scheduling.
If an inter-RNC handover is required and cells under the DRNC are enabled with this feature, the SRNC
needs to indicate information about the UE's serving operator to the DRNC. DRNC is short for drift radio
network controller and SRNC is short for serving radio network controller. The information is carried in the
proprietary IE ulPlmnId in Iur interface messages RADIO LINK SETUP REQUEST, RADIO LINK
RECONFIGURATION PREPARE, and RADIO LINK ADDTION REQUEST. This IE is carried only when
PLMNID_INCLUDED is selected under the IurPrivateInterfaceSwitch ( BSC6910 , BSC6900 )
parameter in the ADD UNRNC command.
This feature is under cell-level license control on the RNC. To activate this license, run the ADD
UCELLLICENSE command on the RNC and select CELL_MOCN_DEMARCATION_SWITCH under
the FuncSwitch1 ( BSC6910 , BSC6900 ) parameter.
9.2 Predefined Percentages of Available Cell Resources

The available cell resources configurable for each operator are DL R99 SCs and HSDPA power
resources. They are specified by parameters DLAvaiSFRatio ( BSC6910 , BSC6900 ) and
DPAAvaiPwrRatio ( BSC6910 , BSC6900 ), respectively. Other cell resources are not assigned
on a per operator basis.
In a shared MOCN cell, the predefined percentages must meet the following requirements:
 The sum of the DLAvaiSFRatio ( BSC6910 , BSC6900 ) values configured for all operators
must be less than or equal to 100.
2024-11-25 27
 The sum of the DPAAvaiPwrRatio ( BSC6910 , BSC6900 ) values configured for all
operators must be less than or equal to 100.
It is noteworthy that:
 If DLAvaiSFRatio ( BSC6910 , BSC6900 ) is set to 0 for an operator, no SCs will be

assigned for downlink R99 services. As a result, DL R99 services of this operator cannot be
accessed.
 If DPAAvaiPwrRatio ( BSC6910 , BSC6900 ) is set to 0 for an operator, no HSDPA power

resources will be assigned for downlink HSDPA services. As a result, HSDPA services of this
operator cannot be accessed.
Figure 9-2 illustrates example configurations for resource demarcation in a shared MOCN cell.
The MOCN cell shown in Figure 9-2 is shared by operators A, B, and C. Operator A is the primary
operator, and operators B and C are secondary operators. The percentages of available DL R99
SCs configured for operators A, B, and C are 30%, 40%, and 30%, respectively. The percentages
of HSDPA power resources configured for operators A, B, and C are 40%, 40%, and 20%,
respectively.
The total downlink power in a MOCN cell is allocated to operators in proportions specified using
DLPwrRatio ( BSC6910 , BSC6900 ). The sum of DLPwrRatio ( BSC6910 , BSC6900 )
specified for all operators is less than or equal to 100. Note that the configuration of percentages
of total downlink power resources for operators and allocation of HSDPA power resources for
operators cannot take effect simultaneously. If these two functions are both enabled, the former
one prevails.
Figure 9-2 Example configurations for MOCN Cell Resource Demarcation
9.3 Admission and Preemption
9.3.1 Admission
After this feature is enabled, the following admission policies apply:
 When cell resources are sufficient, the RNC admits UEs based on resource usage in the
entire cell without differentiating between operators. UEs of any operator can use more
2024-11-25 28
resources than the predefined resource percentage. This helps achieve dynamic sharing of
DL R99 SCs, HSDPA power resources, or total downlink power resources among operators.
 When a UE cannot be admitted due to insufficient cell resources, the RNC triggers
preemption based on resource usage of the UE's serving operator. For details, see section
9.3.2 Preemption.
If admission of an HSPA service fails, the service falls back to an R99 service and attempts to access the
cell again. If the admission succeeds, the service is carried on a DCH. If the admission fails gain,
preemption is triggered for HSPA services.
The RNC makes admission decision for HSDPA UEs based on GBP. GBP is the minimum power required for
the guaranteed bit rate (GBR). The NodeB notifies the RNC of HSDPA UEs' power usage. The NodeB
periodically notifies the RNC of total GBP required for each operator's HSDPA UEs using network resources
in the proprietary IE OperatorHsdpaGbpPwrListPrivate carried in the COMMON MEASUREMENT REPORT
message. This IE is carried under no switch control.
The NodeB periodically notifies the RNC of total power resources required by the downlink DCHs of each
operator using the proprietary IE OperatorDCHPwrListPrivate carried in the transmitted carrier power (TCP)
measurement message.
For details about admission, see Call Admission Control Feature Parameter Description .
9.3.2 Preemption
Overview
Preemption is triggered when a UE cannot be admitted due to insufficient DL R99 SCs or HSDPA
power resources or total power resources in a cell. A UE whose serving operator has not
exceeded its predefined resource percentage can preempt resources of a UE whose serving
operator has. However, if there are no redundant resources available for the serving operator
that has exceeded its predefined resource percentage, resources of this serving operator's UEs
cannot be preempted.
A UE whose serving operator has exceeded its predefined resource percentage can only preempt
resources of low-priority UEs of the same operator.
This document only describes preemption triggered due to insufficient DL R99 SCs or HSDPA
power resources or total power resources in a cell. For details about preemption triggered due to
other causes, see Load Control Feature Parameter Description .
Emergency calls are always processed with the highest priority. A new UE who initiates an emergency call
can preempt resources of another UE regardless of whether resource usage of the UE's operator has
exceeded its predefined percentage or not.
Preemption Based on DL R99 SCs
2024-11-25 29
After this function is enabled, the RNC selects a UE of an operator that exceeds the predefined
percentage of DL R99 SCs most and then triggers preemption for a new UE if its admission fails
due to insufficient DL R99 SCs in its camping cell.
A new UE that fails to be admitted due to insufficiency of DL R99 SCs can preempt resources of
another UE in the same cell if the following conditions are met:
 The new UE is capable of preempting resources of other UEs according to the configurations
of the CN.
In the RAB ASSIGNMENT REQUEST message sent by the CN, the Preemption Capability IE specifies whether
a service can trigger preemption and the Preemption Vulnerability IE specifies whether a service can be
preempted. Service priorities and the Preemption Capability and Preemption Vulnerability IEs determine
whether to perform preemption.
 The switch for preemption based on the DL R99 SCs is turned on:
MOCN_DEMARC_PREEMPT_SF under the DemarcPreemptSwitch ( BSC6910 ,
BSC6900 ) parameter is selected.
 The new UE's serving operator has not exceeded its predefined percentage of DL R99 SCs,
as measured by the following equation:
(SFused + DL R99 SCs required for the new service)/SF available ≤ DLAvaiSFRatio ( BSC6910 ,
BSC6900 ), where,
 SFused: DL R99 SCs occupied by the operator
 SFavailable: DL R99 SCs occupied by all operators in the cell
 DLAvaiSFRatio ( BSC6910 , BSC6900 ): predefined percentage of DL R99 SCs for the

operator
Preemption is less likely to be triggered and adjusted on a per operator basis in the following
scenarios:
 New service subscription requires a high data rate and occupies many codes, which makes it
difficult to trigger preemption.
 When the MultCodePreemptAlgoSwitch ( BSC6910 , BSC6900 ) parameter is set to ON,
preemption can be triggered only if the preempted codes are adjacent and the serving operators
all have their predefined percentages of code usage exceeded.
The preemption policy is as follows:
1. The RNC selects a preempted operator.

The RNC selects the operator that exceeds its predefined percentage of DL R99 SCs. The
criteria for the selection is as follows: Number of SFs occupied by this operator/Total
number of occupied SFs > DLAvaiSFRatio ( BSC6910 , BSC6900 ).
2. The RNC selects a preempted UE.
2024-11-25 30
The RNC selects a UE whose user priority is the lowest among the UEs of the selected
operator. If there is more than one UE that has the lowest priority, the RNC selects a UE
that can release the most resources. If several UEs release the same amount of resources,
the RNC randomly chooses one from such UEs.
Preemption Based on GBP
When this function is enabled, a new UE that fails to be admitted due to insufficiency of downlink
power resources can preempt resources of a UE of an operator that has exceeded the GBP by the
highest degree.
A new UE that fails to be admitted due to insufficiency of downlink power resources can preempt
resources of another UE in the same cell if the following conditions are met:
of the CN.
 MOCN_DEMARC_PREEMPT_GBP is selected under the DemarcPreemptSwitch (

BSC6910 , BSC6900 ) parameter.
 HSDPA_GBP_MEAS is selected under the NBMCacAlgoSwitch ( BSC6910 , BSC6900 )

parameter.
 Sum of DL power occupied by non-HSPA UEs ≤ NonHPwrForGBPPreemp ( BSC6910 ,

BSC6900 ).
If the sum of DL power for non-HSPA UEs is greater than NonHPwrForGBPPreemp ( BSC6910 ,
BSC6900 ), there are too many R99 UEs in the serving cell. Preemption based on DL R99 SCs will be
triggered instead.
 The new UE's serving operator does not exceed the defined GBP, as measured by the
following equation:
(GBPused + GBP resources required for the new service)/GBP available ≤ DPAAvaiPwrRatio (
BSC6910 , BSC6900 ), where,
 GBPused: GBP resources occupied by the UE's serving operator
 GBPavailable: GBP resources available for all operators in the cell
 DPAAvaiPwrRatio ( BSC6910 , BSC6900 ): predefined percentage of HSDPA power

resources for the operator

The RNC selects the operator that exceeds its predefined percentage of HSDPA power
resources. The criteria for the selection is as follows: GBP used/GBPavailable >
DPAAvaiPwrRatio ( BSC6910 , BSC6900 ).
2024-11-25 31
If multiple operators exceed their predefined percentages, the RNC selects the operator
that exceeds its predefined percentage of HSDPA power resources the most.

Preemption Based on Total Downlink Power Resources
RAN16.0 introduces the function of allocating total downlink power resources to each operator.
When this function is enabled, a new UE that fails to be admitted due to insufficiency of downlink
power resources can preempt resources of a UE of an operator that has exceeded predefined
percentage of total downlink power resources by the highest degree.
A new UE that fails to be admitted due to insufficiency of downlink power resources can preempt
resources of another UE in the same cell if the following conditions are met:
of the CN.
 MOCN_DEMARC_PREEMPT_GBP is selected under the DemarcPreemptSwitch (

BSC6910 , BSC6900 ) parameter.
 HSDPA_GBP_MEAS is selected under the NBMCacAlgoSwitch ( BSC6910 , BSC6900 )

parameter.
 The NodeB reports the percentage of power resources consumed by the DCH of each
operator using the TCP measurement message.

The RNC selects an operator that has exceeded its predefined percentage of total downlink
power resources.
An operator exceeds the predefined percentage of total downlink power resources when
the percentage of the downlink power resources consumed by the operator is greater than
the value of DLPwrRatio ( BSC6910 , BSC6900 ) specified for the operator.
Percentage of downlink power resources consumed by the operator of the new UE = (GBP
power consumed by the operator + DCH power consumed by the operator + Power
required by the new UE)/Sum of GBP power and DCH power consumed by all operators
sharing the cell
Percentage of downlink power resources consumed by another operator = (GBP power of
the operator + DCH power of the operator)/Sum of GBP power and DCH power consumed
by all operators sharing the cell
2024-11-25 32
 If the operator of the new UE does not exceed the predefined percentage of power
resources, the UE can preempt resources of another UE that is served by other
operators whose downlink power resources exceed the predefined percentage.
 If the operator of the new UE has exceeded the predefined percentage of power
resources, the UE can only preempt resources of another UE that is served by the
same operator.
 If more than one operator has exceeded the predefined percentage of downlink power
resources, the RNC selects the operator that has exceeded the predefined power
resources by the highest degree. If multiple operators have exceeded the predefined
downlink power resources by the same degree, the RNC randomly selects one of the
operators.

9.4 Congestion Control

The mechanism for triggering cell basic congestion caused by insufficient DL R99 SCs is the
same as the original algorithm. For details, see Load Control Feature Parameter Description .
After cell basic congestion is triggered, this feature performs load reshuffling (LDR) in a range of
objects that differ from those in the original algorithm.
The objects of LDR are specified by the NbmSFLdcUeSelSwitch ( BSC6910 , BSC6900 )
parameter. Following are details:
 If NBM_SF_LDC_DEMARC is selected under the NbmSFLdcUeSelSwitch ( BSC6910 ,

BSC6900 ) parameter, the RNC selects UEs whose operator exceeds its predefined
percentage of DL R99 SCs the most.
If PERFENH_DEMARC_SF_LDC_OPT_SWITCH is selected under the PerfEnhanceSwitch2
( BSC6910 , BSC6900 ) parameter in the MML command SET UNBMPARA, the RNC uses
the percentage of SF code resources occupied by an operator to total occupied SF code
resources to determine whether the predefined percentage has been exceeded. In other
circumstances, the RNC uses the percentage of SF code resources occupied by an operator
to available SF code resources to determine whether the predefined percentage has been
exceeded.
 If NBM_SF_LDC_ALL_UE is selected under the NbmSFLdcUeSelSwitch ( BSC6910 ,

BSC6900 ) parameter, the RNC does the same way it does in the original algorithm. That is,
the RNC selects UEs with the lowest service priority for LDR without differentiating between
operators.
This feature uses the same algorithm for triggering basic congestion of a cell as the Load Control
feature, which is described in Load Control Feature Parameter Description . The only difference is
2024-11-25 33
as follows: The scope of load reshuffling implemented by this feature after the basic congestion
is triggered for a cell is different from that of load reshuffling implemented by the Load Control
feature.
For this feature, the scope of LDR is specified by the DlPWRLdcUeSelSwitch ( BSC6910 ,
BSC6900 ) parameter as follows:
 If DL_PWR_LDC_DEMARC is selected under the DlPWRLdcUeSelSwitch ( BSC6910 ,

BSC6900 ) parameter, the RNC performs LDR on UEs whose operator exceeds its predefined
percentage of DL power resources by the highest degree.
 If DL_PWR_LDC_ALL_UE is selected under the DlPWRLdcUeSelSwitch ( BSC6910 ,

BSC6900 ) parameter, the RNC performs LDR on the UEs with the lowest priority without
demarcating the operators.
The setting of the preceding parameter takes effect only when the function of allocating
power resources to each operator is enabled.
If basic congestion is caused by insufficiency of other resources, the RNC selects UEs with the
lowest service priority for LDR without differentiating between operators as the RNC does in a
non-MOCN cell. For details about LDR and cell congestion control, see Load Control Feature
Parameter Description .
9.5 Scheduling
Scheduling for HSDPA UEs means allocating resources to HSDPA UEs in a cell. The NodeB
schedules HSDPA UEs based on their scheduling priorities. This feature maintains differentiated
scheduling for UEs served by an operator. The NodeB performs scheduling based on operator
information and DPAAvaiPwrRatio ( BSC6910 , BSC6900 ) values configured for the UEs'
serving operators that are indicated by the RNC. This aims to ensure the scheduling fairness.
Before scheduling, the NodeB calculates the value of the following formula for each operator:
HSDPA power consumed by the operator in last sampling period (set to 200 ms)/(Total HSDPA
power available to the cell x DPAAvaiPwrRatio ( BSC6910 , BSC6900 ) specified for the
operator). According to the calculated result, the NodeB prioritizes the operators. The smaller the
calculated result of this formula, the higher the scheduling priority of the operator in the current
period, and the more scheduling opportunities the UEs of this operator will have.
When the function of allocating power resources to each operator is enabled, the NodeB
implements the following mechanism to ensure that the percentage of power resources
consumed by each operator is close to the predefined one: Before scheduling, the NodeB
calculates the following formula for each operator: Sum of HSDPA power and downlink DCH
power consumed by the operator in last sampling period (set to 200 ms)/[(Total HSDPA power
available to the cell + Total downlink DCH power available to the cell) x DLPwrRatio ( BSC6910
, BSC6900 ) specified for the operator]. According to the calculated result of the formula, the
NodeB prioritizes the operators. The smaller the calculated result of this formula, the more
scheduling opportunities the HSDPA UEs of this operator will have.
2024-11-25 34
The scheduling priority for UEs of the same operator is determined based on the existing mechanism. For
details, see HSDPA Feature Parameter Description .
Scheduling for HSDPA UEs aims to ensure the usage of resources is close to the predefined
percentage. However, an operator may use less power resources than its predefined percentage
on the live network if services of this operator require only a small amount of HSDPA power
resources (for example, web page browsing) or the UEs have limited capabilities.
The RNC indicates the following DPAAvaiPwrRatio ( BSC6910 , BSC6900 ) information to the
NodeB:
 The RNC indicates the indexes of MOCN operators, operators' predefined values for
DPAAvaiPwrRatio ( BSC6910 , BSC6900 ), and index of the primary operator in
proprietary IEs ucMocnoperatorIndex, ucMocnoperatordemarcationHpowerratio, and
ucPrimOperIndex, respectively. These IEs are carried in the Physical Shared Channel
Reconfiguration Request message.
 When the function of allocating power resources to each operator, which is introduced in
RAN16.0, is enabled, the DLPwrRatio ( BSC6910 , BSC6900 ) parameter and another
proprietary IE "enMultiOpPwrDemarcType" are also carried in the Physical Shared Channel
Reconfiguration Request message besides the preceding proprietary IEs. The proprietary IE
enMultiOpPwrDemarcType indicates whether the percentage of power in the Physical Shared
Channel Reconfiguration Request message to the NodeB is the percentage of HSDPA power
or percentage of total downlink power.
 The proprietary IEs ucMocnoperatorIndex and ucMocnoperatordemarcationHpowerratio

can be delivered in the message only when CELL_MOCN_DEMARCATION_SWITCH is
selected under the FuncSwitch1 ( BSC6910 , BSC6900 ) parameter.
 The proprietary IE ucPrimOperIndex can be delivered in the message only when

PSCRR_OpIndex_INCLUDED is selected under the IubPrivateInterfaceSwitch (
BSC6910 , BSC6900 ) parameter by running the SET URRCTRLSWITCH command.
The NodeB must learn information about the primary operator from the RNC because the RAN cannot
differentiate the operator that uses power resources on common channels, such as EFACH and EPCH, from
other operators, and HSDPA power resources consumed by the common channels are counted as resources
consumed by the primary operator.
 The RNC indicates information about each HSDPA UE's serving operator in the proprietary IE
ucSharedOperIndex carried in the following messages:
 Radio Link setup Request
 Radio Link Reconfiguration Prepare
 Radio Link Addition Request

The proprietary IE ucSharedOperIndex is carried in the messages only when
RL_OpIndex_INCLUDED is selected under the IubPrivateInterfaceSwitch (
BSC6910 , BSC6900 ) parameter in the SET URRCTRLSWITCH command.
2024-11-25 35
To ensure the maximum cell throughput, set RSCALLOCM to POWERCODE_BAL by running the
SET ULOCELLMACHSPARA command on the NodeB side. This setting ensures that the NodeB
performs scheduling based on a balance between code resources and power resources.
For details about scheduling for HSDPA UEs, see HSDPA Feature Parameter Description .
Prerequisite Features
Feature ID Feature Name Description
WRFD- MOCN Introduction This feature requires the WRFD-021311 MOCN Introduction
021311 Package Package feature.
Mutually Exclusive Features
Featur Function Name Description

e ID
None HSDPA power In the same cell, the function of allocating HSDPA power resources to
resource allocation each operator cannot take effect together with the function of
allocating total downlink power resources to each operator.
None Allocation of total In the same cell, the function of allocating HSDPA power resources to
downlink power each operator cannot take effect together with the function of
resources allocating total downlink power resources to each operator.
Impacted Features
Featur Feature/ Description

e ID Function Name
None Inter-PLMN The MOCN Cell Resource Demarcation feature cannot be used with the
Handovers inter-PLMN handover function. This is because inter-PLMN handovers
cause UEs belonging to an operator to occupy the dedicated cell
resources of another operator, which affects cell resource allocation
and increases difficulty in charging.
None Inter-PLMN multi- The MOCN Cell Resource Demarcation feature cannot be used with the
carrier HSPA inter-PLMN multi-carrier HSPA function. This is because the inter-PLMN
multi-carrier HSPA function causes UEs belonging to an operator to
occupy the dedicated cell resources of another operator, which affects
cell resource allocation and increases difficulty in charging.
WRFD- Load Reshuffling The function of allocating total downlink power resources to each
020106 operator must be deployed in a cell supporting HSDPA. It is
recommended that this function be enabled together with the WRFD-
020106 Load Reshuffling feature and the LDR based on power
resources function.
9.7 Network Impact
2024-11-25 36
No impact.
 With the MOCN Cell Resource Demarcation feature, the RNC is more likely to trigger
preemption and the call drop rate increases in a cell with heavy load if any operator uses
more DL R99 SCs, HSDPA power resources, or total power resources than its predefined
resource percentage. In a cell with light load, however, this feature has no impact on
network performance because preemption is not triggered.
 Before the function of using cell resources based on the HSDPA power percentages for
MOCN-enabled operators in a cell is enabled, the downlink power uses the non-HSPA power.
After this function is enabled, the downlink power uses the non-HSPA power and GBP power.
This may cause downlink power congestion and increase access failures.
 Before enabling this feature, check whether the MOCN CE resource independent allocate(per
Cell) (LQW9MOCN01) is installed on the NodeB. If the license has been installed, turning on
RL_OPINDEX_INCLUDED on the base station controller will also enable the MOCN
Independent CE Resource Allocation function on the NodeB. If the number of CE resources in
the operator's private group is "Not set" on the MAE, UEs of the operator cannot access the
network.
 10.1 Overview
 10.2 Allocating CE Resources to Operators
 10.3 NodeB Allocating CE Resources to UEs
 10.4 RNC Relieving CE Congestion per Operator
10.1 Overview
The MOCN Independent CE Resource Allocation feature is introduced to ensure that each
operator retains independent CE resources in MOCN scenarios.
This function involves the following sub-functions:
 The NodeB-level uplink and downlink CE resources are allocated by operator.
 The NodeB allocates the CE resources to UEs by operator.
 The RNC relieves CE congestion for each operator separately.
10.1.1 Introduction
CE resources can be allocated to operators by configuring private and common groups.
 Private group: CE resources in a private group belong to only one operator.
2024-11-25 37
 Common group: CE resources in the common group can be shared by all operators.
10.1.2 Benefits
This feature prevents a single operator from occupying excessive CE resources in MOCN
scenarios and ensures that each operator retains independent CE resources.
This feature slightly decreases CE resource utilization. If CE resources are not properly allocated
(for example, the CE resources allocated to an operator are insufficient), this feature brings some
negative effects. For example, the access performance as measured by the RRC connection
setup success rate and RAB setup success rate deteriorates and the HSUPA throughput
decreases.
10.2 Allocating CE Resources to Operators

The CE resources are allocated to operators when the following conditions are met:
 LampSite, or macro base stations are used, and they are running RAN15.0 or later.
 The license for the MOCN Independent CE Resource Allocation feature has been activated.
 MOCN configuration is used.
When these conditions are met, CE resources are allocated to NodeBs based on the settings
made in the License Distributed to Operator window on the MAE.
 When this feature is enabled, the operator's private group CE must be assigned with an actual value. If
it is set to Not set, the users served by this operator cannot access the network.
 The total number of CE resources assigned to the common group and private groups cannot exceed
the licensed CE capacity.
10.3 NodeB Allocating CE Resources to UEs

After dividing CE resources into groups and identifying a UE's serving operator, the NodeB
allocates the CE resources in this operator's private groups to the UE. If the CE resources in the
operator's private groups are used up, the CE resources in the common group can be used. The
CE resources in the common group are used on a first come, first served basis.
To enable the NodeB to identify a UE's serving operator, run the SET URRCTRLSWITCH
command with IubPrivateInterfaceSwitch ( BSC6910 , BSC6900 ) set to
RL_OpIndex_INCLUDED. The RNC will indicate information about a UE's serving operator in the
proprietary IE ucSharedOperIndex in the messages Radio Link Setup Request, Radio Link
Reconfiguration Prepare, and Radio Link Addition Request.
In the following two scenarios, however, the NodeB cannot identify a UE's serving operator:
 During the radio resource control (RRC) connection setup, signaling radio bearers (SRBs) are
carried over ERACHs. In this scenario, the RNC has not yet sent the Radio Link Setup Request
message, and therefore the NodeB cannot identify a UE's serving operator.
2024-11-25 38
 Uplink user-plane data is carried over ERACHs. In this scenario, the UE resides on the
common channels, and the RNC has deleted the radio link assigned to the UE. Therefore, the
NodeB cannot identify the UE's serving operator.
To sum up, if uplink CE resources are consumed by ERACHs, the NodeB considers such CE
resources as consumed by the primary operator. To enable the NodeB to identify the primary
operator, run the SET URRCTRLSWITCH command with PSCRR_OpIndex_INCLUDED under
IubPrivateInterfaceSwitch ( BSC6910 , BSC6900 ) selected. The RNC will indicate
information about the primary operator in the proprietary IE ucPrimOperIndex in the Physical
Shared Channel Reconfiguration Request message.
If a UE moves between RNCs over the Iur interface, and NodeBs managed by the neighboring
RNC support this feature, run the ADD UNRNC command with PLMNID_INCLUDED under the
IurPrivateInterfaceSwitch ( BSC6910 , BSC6900 ) parameter selected so that the serving
RNC sends operator information to the drift RNC (DRNC) over the Iur interface. Upon receipt of
the information, the DRNC sends the operator information to the serving NodeB.
10.4 RNC Relieving CE Congestion per Operator

After the MOCN Independent CE Resource Allocation feature is activated, preset trigger
mechanisms and load reshuffling (LDR) operations for cell- or NodeB-level basic congestion
remain unchanged. For details about these mechanisms and operations, see Load Control
Feature Parameter Description . The trigger mechanism for operator-level congestion release is
added in this feature.
The congestion release operations for operator-level uplink CE congestion include the following:
 BE service rate reduction
If the remaining uplink CE resources of an operator fall below the UlLdrCreditSfResThd (

BSC6910 , BSC6900 ) value, basic congestion occurs, triggering best effort (BE) service rate
reduction for certain UEs served by the operator. For details about how to specify UEs for rate
deduction and the rate reduction process, see Load Control Feature Parameter Description .
If more than one operator experiences basic congestion at the same time, BE service rate
reduction is triggered for the operator who experiences the most severe congestion. During BE
service rate reduction, the number of UEs involved and the rate reduction period for each UE
depend on the values of the UlLdrBERateReductionRabNum ( BSC6910 , BSC6900 ) and
LdrPeriodTimerLen ( BSC6910 , BSC6900 ) parameters, respectively.
 Switching from 2 ms TTI to 10 ms TTI
If the remaining uplink credit resources of an operator fall below the value of
UlTtiCreditSfResThd ( BSC6910 , BSC6900 ), and
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH is enabled, the transmission time interval (TTI)
of connected UEs served by the operator is switched from 2 ms to 10 ms, and the 10 ms TTI is
used for idle-to-connected UEs.
If an operator has less than eight CE licenses, the TTI of connected UEs served by the operator is
switched from 2 ms to 10 ms, and the 10 ms TTI is used for idle-to-connected UEs.
2024-11-25 39
HSUPA TTI switching remains the same. For details, see HSUPA TTI Selection Feature Parameter
Description .
Feature Feature Name Description

ID
WRFD- RAN Sharing This feature cannot be used together with the WRFD-021304
021304 Introduction Package RAN Sharing Introduction Package feature.
Impacted Features
None
10.6 Network Impact

This feature has no impact on system capacity when the CE resources allocated to each operator
are sufficient.
If the resources are not properly allocated among operators, system capacity decreases. For
example, if a total of 100 CEs are equally allocated to operators A and B who require 60 and 40
CEs, respectively, only 90 CEs are utilized, with a 10% decrease in system capacity.

It is recommended that the CE resources be allocated to each operator according to their traffic
volumes. If different operators have similar traffic models, it is recommended that the CE
resources be allocated equally among operators.
 If the CE resource allocated to each operator matches the traffic volume of each operator,
this feature does not affect related KPIs.
 If the allocated CE resource does not meet operators' traffic requirements, network
performance deteriorates. For example, before feature deployment, the total number of CEs
is 100 and the demand of operators A and B is 60 and 40 respectively. If the CEs allocated to
each operator are 50, the CE resource utilization, cell HSUPA throughput, R99 PS throughput,
and access success rate decrease by 10%.
2024-11-25 40
 Before enabling this feature, ensure that the number of CE resources in the operator's
private group is a valid value. If the number of CE resources in the operator's private group
is "Not set" on the MAE and the RL_OPINDEX_INCLUDED switch is turned on on the base
station controller, UEs of the operator cannot access the network.
 11.1 Overview
 11.2 Configuring Operator-Specific Logical Ports
 11.3 Identifying the UE's Serving Operator
11.1 Overview
The MOCN Independent Iub Transmission Resource Allocation feature allocates Iub transmission
resources to operators in MOCN scenarios, which prevents one operator from occupying
excessive Iub transmission resources and ensures that each operator retains independent Iub
transmission resources.
Iub transmission resources are logically divided into user- and control-plane transmission
resources. In MOCN scenarios, this feature allocates user-plane bandwidth to each operator
independently and enables operators to share control-plane bandwidth and the common channel
bandwidth in a shared cell. Figure 11-1 illustrates the bandwidth allocation.
Figure 11-1 Allocating Iub bandwidth
To allocate user-plane bandwidth independently in static independent Iub transmission mode:
 The RNC is configured with multiple logical ports, and each logical port corresponds to one
operator.
 The RNC identifies the UE's serving operator and sends the UE's user-plane data to the
corresponding logical port.
 ALCAP is required only in the ATM transmission mode.
2024-11-25 41
This feature supports Iub interface sharing on the RNC in the following scenarios:
 Operators share one physical link over the Iub interface, as shown in Figure 11-2.
Figure 11-2 Sharing one physical link over the Iub interface
 Each operator uses a dedicated physical link over the Iub interface, as shown in Figure 11-3.
Figure 11-3 Using dedicated physical links over the Iub interface
This feature applies only to RNC downlink transmission resources. The NodeB uplink transmission
resource allocation is not supported.
From RAN16.0 onwards, the dynamic independent Iub transmission mode is supported. In this
mode, the NodeB is configured with a Hub logical port for convergence. In the Hub logical port, a
dedicated leaf logical port is configured for each operator, as shown in Figure 11-4.
If the Hub logical port is not congested but the dedicated logical port of an operator is congested,
the NodeB limits the user-plane transmit rate of this operator only. When the Hub logical port for
a NodeB experiences transmission congestion, the NodeB limits the user-plane transmit rate of
all operators that share this NodeB to ensure that the percentage of bandwidth used by each
operator in the Hub logical port is close to the percentage of bandwidth configured for each leaf
logical port.
For example, the bandwidth configured for the Hub logical port is 10 Mbit/s. The bandwidth
configured for the leaf logical port dedicated to operator A is 8 Mbit/s, and the bandwidth
configured for the leaf logical port dedicated to operator B is 6 Mbit/s. If the Hub logical port is
congested, this feature ensures that the ratio of the bandwidth allocated to operator A to the
bandwidth allocated to operator B can reach 4:3.
2024-11-25 42
Figure 11-4 Configuration of logical ports in dynamic independent Iub transmission mode
11.1.1 Benefits
This feature allocates Iub transmission resources to operators in MOCN scenarios, which prevents
one operator from occupying excessive Iub transmission resources and ensures that each
operator retains independent Iub transmission resources.
The dynamic independent Iub transmission mode introduced in RAN16.0 enables each operator
to utilize the Iub bandwidth according to the percentage of bandwidth configured for the leaf
logical port of the operator.
This feature slightly decreases Iub resource utilization. If Iub resources are not properly allocated
(for example, the Iub resources allocated to an operator are insufficient), this feature brings
some negative effects. For example, the access performance as measured by the RRC
connection setup success rate and RAB setup success rate deteriorates and the HSPA throughput
decreases.
11.2 Configuring Operator-Specific Logical Ports

When the RNC is configured with the ATMLOGICPORT or IPLOGICPORT MO, if RSCMNGMODE
( BSC6910 , BSC6900 ) is set to EXCLUSIVE on the RNC, the logical port can be used by only
one operator specified by the CNOPINDEX ( BSC6910 , BSC6900 ) parameter.
If RSCMNGMODE ( BSC6910 , BSC6900 ) is set to EXCLUSIVE, MOCNSupport ( BSC6910 ,
BSC6900 ) must be set to YES and the licenses for both the MOCN Introduction Package feature
and the MOCN Independent Iub Transmission Resource Allocation feature must be activated.
Otherwise, the transport resource admission will fail and services cannot be set up.
11.3 Identifying the UE's Serving Operator

After identifying the UE's serving operator, the RNC sends the UE's user-plane data to the
corresponding logical port.
For RRC signaling:
 If the operator group configured for the cell has only one operator, the RNC selects that
operator.
 If the operator group has multiple operators, the RNC selects an operator as follows:
2024-11-25 43
If the initial UE ID in the RRC connection request message is the TMSI, PTMSI, or IMSI, the
RNC checks whether the PLMN carried in the initial UE ID corresponds to a non-common
operator in the operator group. If yes, the RNC selects that operator.
 If the initial UE ID in the RRC connection request message is not the TMSI, PTMSI, or IMSI, or
the RNC cannot identify the UE's serving operator, the RNC randomly selects an operator
from the operator group.
 For common channels of a shared cell:

Common channels (including EFACH, EPCH, and ERACH) are shared by operators. You can
run the RNC MML command ADD UCELLSETUP and set the CchCnOpIndex ( BSC6910 ,
BSC6900 ) parameter to specify the operator that provides bandwidth for common channels
of a shared cell. The default value 255 indicates that the primary operator provides
bandwidth. If there is no primary operator, the first operator listed in the operator group
provides bandwidth.
 For user-plane dedicated channels:

The RNC checks the CN node connected to a UE to identify the operator that provides
bandwidth for user-plane dedicated channels, and then routes data to that operator.
If the primary operator is chosen to carry signaling messages during RRC connection establishment but the
CN of another operator serves the UE during RAB establishment, retain the settings of carrying RRC
signaling messages over the logical port of the primary operator to prevent the effects brought by RRC
connection reestablishment.
DCH synchronization frames and node synchronization frames, which are periodically sent, are carried over
the logical port of the primary operator by default.
 When the Iub interface uses static independent transmission, this feature cannot be used
together with the following features.
ID
WRFD- Iub Transmission This feature cannot be used together with the WRFD-140208
140208 Resource Pool in RNC Iub Transmission Resource Pool in RNC feature.
WRFD- Dedicated Iub This feature cannot be used together with the WRFD-02130501
2024-11-25 44

ID
02130501 Transmission Control Dedicated Iub Transmission Control feature.
WRFD- Iub IP Transmission This feature cannot be used together with the WRFD-150243
150243 Based on Dynamic Iub IP Transmission Based on Dynamic Load Balancing feature.
Load Balancing
WRFD- RAN Sharing This feature cannot be used together with the WRFD-021304
021304 Introduction Package RAN Sharing Introduction Package feature.
WRFD- RAN Sharing Phase 2 This feature cannot be used together with the WRFD-021305
021305 RAN Sharing Phase 2 feature.
GBFD- Abis Independent On a GU multimode base station controller where the Iub and
118704 Transmission Abis interfaces share a physical port, this feature cannot be
used together with the GBFD-118704 Abis Independent
Transmission feature.
 When the Iub interface uses dynamic independent transmission, this feature cannot be used
together with the following features.
ID
WRFD- Iub Transmission This feature cannot be used together with the WRFD-140208 Iub
140208 Resource Pool in Transmission Resource Pool in RNC feature.
RNC
WRFD- Dedicated Iub This feature cannot be used together with the WRFD-02130501
02130501 Transmission Dedicated Iub Transmission Control feature.
Control
WRFD- RAN Sharing This feature cannot be used together with the WRFD-021304 RAN
021304 Introduction Sharing Introduction Package feature.
Package
WRFD- RAN Sharing Phase This feature cannot be used together with the WRFD-021305 RAN
021305 2 Sharing Phase 2 feature.
GBFD- Abis Independent On a GU multimode base station controller where the Iub and Abis
118704 Transmission interfaces share a physical port, this feature cannot be used
together with the GBFD-118704 Abis Independent Transmission
feature.
Impacted Features
None
11.5 Network Impact

This feature has no impact on system capacity when the Iub transmission resources allocated to
each operator are sufficient.
If the resources are not properly allocated among operators, system capacity decreases. For
example, if a total of 10 MHz bandwidth is equally allocated to operators A and B who require 6
2024-11-25 45
MHz and 4 MHz, respectively, only 9 MHz bandwidth is utilized, with a 10% decrease in system
capacity.

It is recommended that the Iub bandwidth be allocated to each operator according to their traffic
volumes. If different operators have similar traffic models, it is recommended that the Iub
bandwidth be allocated equally among operators.
 If the Iub transmission resource allocated to each operator matches the traffic volume of
each operator, this feature does not affect related KPIs.
 The downlink bandwidth usage, the access success rate, and the single-user HSDPA
throughput decrease if the allocated Iub transmission resource does not meet operators'
traffic requirements. For example, before feature deployment, the total bandwidth is 10
MHz, and the traffic requirement of operators A and B is 6 MHz and 4 MHz separately. If the
Iub bandwidth allocated to each operator is 5 MHz, the total downlink Iub bandwidth usage
and the access success rate decrease by 10%. The decreases of single-user HSDPA
throughput can be calculated using the following formula: Single-user HSDPA throughput
decrease = 1 – Minimum bandwidth allocated to the operator/Min(Original bandwidth,
Bandwidth required for maximum UE capability)
 12.1 Overview
 12.2 Broadcasting Multiple PLMN IDs by the RAN
 12.3 Configuring the CN Sharing Relationship Among Operators
 12.4 Selecting a Route by the RNC
 12.5 Providing Services for UEs of Multiple Operators by the Shared CN
12.1 Overview
In the conventional MOCN scenario, operators also share CN devices to further reduce capital
expenditure (CAPEX) and operating expense (OPEX). The Single CN With Multi-PLMN IDs function
is introduced to support this scenario.
This function involves the following sub-functions:
 Broadcasting multiple PLMN IDs by the RAN
 Configuring the CN sharing relationship among operators
 Selecting a route by the RNC
 Providing service to UEs of multiple operators by the shared CN
2024-11-25 46
12.2 Broadcasting Multiple PLMN IDs by the RAN

The system information broadcast for this sub-function is the same as that for the MOCN
Introduction Package feature. To be specific, the RNC uses the IE "Multiple PLMN List" in the
master information block (MIB) to broadcast the PLMN IDs configured for the MOCN-capable cell.
For details, see 3.1 System Information Broadcast.
The CN of an operator is considered unavailable if all CN nodes, including the operator-dedicated
CN node and the shared CN node, are faulty.
12.3 Configuring the CN Sharing Relationship Among Operators
 When only the primary operator's CNs are 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 CNs as long as MultiPLMNforSingleCNSwitch ( BSC6910 ,
BSC6900 ) is set to ON.
If the CN sends the RNC the RIM carrying the PLMN of the secondary operator, set
MultiPLMNforSingleCNSwitch ( BSC6910 , BSC6900 ) to OFF and MultiPLMNforCNEnhanceSw
( BSC6910 , BSC6900 ) to ON, and run the MML command ADD UCNNODESHAREDMAP to add the
MOCN operator for the CN.
 Otherwise, MultiPLMNforCNEnhanceSw ( BSC6910 , BSC6900 ) 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 ( BSC6910 , BSC6900 ) specifies the index of
the homing operator of this CN and SharedCnOpIndex ( BSC6910 , BSC6900 ) specifies
the indexes of the operators sharing this CN.
 The PLMN ID in the connectionless messages such as CN reset, resource reset, and flow control is the
ID of the home PLMN for the CN. The reset of the CN takes effect for all operators' UEs under this CN.
 One CN can be shared by a maximum of four PLMNs.
 When this function takes effect, ensure that an operator has at least one CN node available in a
domain. Otherwise, the registration or location update of the UEs of this operator will be affected.
12.4 Selecting a Route by the RNC

If some CNs are shared and others are dedicated, the RNC determines which CNs are available
according to the parameter configurations in the ADD UCNNODESHAREDMAP command.
 A supporting UE selects an appropriate PLMN ID among all the PLMN IDs broadcast in the
MIB message upon registration or location update and reports the PLMN ID to the RNC
through the INITIAL DIRECT TRANSFER message. The RNC determines the serving operator
of the UE according to the reported PLMN ID and informs the CN of the PLMN ID through the
2024-11-25 47
IE "Selected PLMN Identity" in the Initial UE Message. If the operator has multiple CN nodes,
the RNC uses Iu Flex to select an appropriate CN node route based on the mapping between
the NRI and CN or based on the CN capacity. For details about Iu Flex, see Iu Flex Feature
Parameter Description.
 A non-supporting UE does not report the PLMN ID to the RNC through the Initial Direct
Transfer Message upon registration or location update. The RNC does not carry the IE
"Selected PLMN Identity" in the Initial UE Message. Instead, it carries the IE "Redirect
Attempt Flag" and attempts to select the network among operators. Only one attempt will be
performed on the CN node shared by operators.
When only the primary operator's CNs are available and all of them are shared, the RNC
routes all UEs to the primary operator's CN node regardless of which operators share the
cells if MultiPLMNforSingleCNSwitch ( BSC6910 , BSC6900 ) is set to ON.
 For supporting UEs, when routing the Initial UE Message to the CN node of the primary
operator, the RNC includes the selected PLMN ID in the IE "Selected PLMN Identity".
 For non-supporting UEs, when this switch is turned on, the CNs of other operators will not be
tried. Therefore, the RNC does not carry the IE "Redirect Attempt Flag" in the Initial UE
Message.
12.5 Providing Services for UEs of Multiple Operators by the Shared CN

A CN node shared by multiple operators must be deployed with the multi-PLMN or GWCN
function. The CN node will receive access requests of UEs belonging to multiple operators.
 A supporting UE will carry its own PLMN ID selected upon attach, location update, and
routing area update.
 For a non-supporting UE, the CN determines which operator's PLMN will provide services for
the UE based on the subscription information. For details, see section 9.1.24 in 3GPP TS
25.413 and section 7.1.3 in 3GPP TS 23.251.
The RNC obtains the PLMN ID of the UE's operator by using the following methods:
 If the CN includes the IE "selected PLMN" in the COMMON ID or RELOCATION REQUEST

message, the RNC obtains the PLMN ID of the UE's operator from the IE "selected PLMN".
 If the CN does not include the IE "selected PLMN" in the COMMON ID or RELOCATION
REQUEST message, the RNC obtains the PLMN ID of the UE's operator from the UE's
IMSI. This function is controlled by MulPLMNSingleCNOPByIMSISW ( BSC6910 ,
BSC6900 ).
1. If the CN does not include the IE "selected PLMN" in the COMMON ID or RELOCATION
REQUEST message and the RNC-level switch specified by
MulPLMNSingleCNOPByIMSISW ( BSC6910 , BSC6900 ) is not turned on, the following
risks arise:
 The RNC regards non-supporting UEs as the UEs of the first operator in the operator
group, which affects the accuracy of traffic statistics on a per operator basis.
2024-11-25 48
 For an inter-RNC handover from a MOCN-capable network to a dedicated network, the

UEs served by the secondary operator will be regarded as the UEs served by the
primary operator, leading to handover failures.
2. Enabling the GWCN feature requires that the CN have the GWCN switch turned on and be
provided by the same vendor.
3. Enabling the GWCN feature requires that the CN support including the "selected PLMN" IE
in a COMMON ID or RELOCATION REQUEST message. In addition, it is recommended that a
network entry test be performed first.
 RAN side
WRFD-021311 MOCN Introduction Package N/A
 PS side
WSFD-110113 Network Share (GWCN) N/A
WSFD-110103 Multiple HPLMNs N/A
 CS side
WMFD-160100 Multi-PLMN Function N/A
None
Impacted Features
Featur Feature Description

e ID Name
WRFD- Iu Flex If an operator has multiple CN nodes available, it is recommended that WRFD-
021302 021302 Iu Flex be deployed.
When MultiPLMNforSingleCNSwitch ( BSC6910 , BSC6900 ) is set to ON,
the WRFD-021302 Iu Flex feature cannot be used to configure the mapping
between the NRI and CN or the mapping between the IMSI and CN for
secondary operators. UEs of secondary operators select the CN based on the
mapping configured for the primary operator.
When MultiPLMNforCNEnhanceSw ( BSC6910 , BSC6900 ) is set to ON,
you are advised to deploy WRFD-021302 Iu Flex so that disaster recovery can
be performed among multiple nodes if an operator has multiple CN nodes
available in the same domain. If WRFD-021302 Iu Flex is not deployed, the
RNC may route the UE to an incapable CN node.
2024-11-25 49
Featur Feature Description

e ID Name
In addition, this feature does not support the Selecting CN Node Based on IMSI
function in the WRFD-021302 Iu Flex feature.
None Single CN MultiPLMNforCNEnhanceSw ( BSC6910 , BSC6900 ) and

with Multi- MultiPLMNforSingleCNSwitch ( BSC6910 , BSC6900 ) are mutually
PLMN IDs exclusive.
12.7 Network Impact

Compared with the MOCN Introduction Package feature, this function does not affect network
capacity. However, the CN shared by multiple operators serves UEs of multiple operators,
causing both the transmission bandwidth and CN load on the Iu interface to increase.
 The Iu interface is shared by multiple operators. Therefore, after this function is enabled, UEs
of all operators are measured by the counters related to the following measurement objects:
CS.SIG.IU, CS.TRF.IU, NAS.IU, PS.SIG.IU, PS.TRF.IU, and SIG.SCCP.IU. With the Single CN With
Multi-PLMN IDs function, non-supporting UEs no longer perform redirection attempts.
Therefore, redirection-related counters are no longer measured in the MOCN scenario.
 If the Single CN With Multi-PLMN IDs function is used in the conventional MOCN scenario, the
CN that serves the UEs of secondary operators changes. Due to different CN configurations,
Iu interface-related counters change.
 13.1 Overview
 13.2 Call Setup Procedure
13.1 Overview
In MOCN scenarios, the following switch controls whether UEs of a specific operator are forbidden
from setting up CS RABs:
The CSLimitInUMTSSwitch ( BSC6910 , BSC6900 ) parameter.
 When this parameter is set to ON, UEs served by the operator whose index is set to
CnOpIndex ( BSC6910 , BSC6900 ) cannot set up CS RABs in the serving UMTS cell.
 When this parameter is set to OFF, UEs served by the operator whose index is set to
CnOpIndex ( BSC6910 , BSC6900 ) can set up CS RABs in the serving UMTS cell.
13.2 Call Setup Procedure
2024-11-25 50
The call setup procedure is as follows when the best cell is served by the DRNC or SRNC:
 If the best cell is served by the DRNC, the function of forbidding UEs of specific operators
from setting up CS services cannot take effect. Upon receiving a CS RAB assignment
message from the CN, the SRNC performs the following operations based on the setting of
the CSLimitInUMTSStrategySW ( BSC6910 , BSC6900 ) parameter:
 If this parameter is set to OFF (default value), UEs cannot be handed over to the current
cell and the RNC returns a failure cause of "Radio Network Layer Cause" to the CN.
 If this parameter is set to ON, CS RABs can be set up in the serving UMTS cell.
 If the best cell is served by the SRNC, see the following sections for the call setup procedure:
 13.2.1 Calls Initiated by UEs in Idle Mode
 13.2.2 Calls Initiated by UEs in the CELL_FACH State
 13.2.3 Calls Initiated by UEs in the CELL_DCH State
 13.2.4 Relocation to the Current Cell
13.2.1 Calls Initiated by UEs in Idle Mode

For UEs in idle mode that are enabled with the function of forbidding UEs of specific operators
from setting up CS services, the call setup procedure is as follows:
1. Establish the RRC connection and go to 2.
2. After the RRC connection setup is complete, the RNC receives a RAB assignment message
from the CN.
 If the assigned type is PS services, PS services can be established.
 If the assigned type is CS services, the RNC buffers CS RABs and goes to 3.
3. Based on whether the UE supports GSM frequency measurement capability, the RNC
performs the following operations:
 If the UE supports the capability, the RNC delivers an inter-RAT measurement control
message to the UE with parameters in Table 13-1 carried, and then goes to 4.
Table 13-1 Inter-RAT measurement control parameters
Parameter Parameter Value
Name
GSM cell ID If the operator group configured with CnOpGrpIndex ( BSC6910 , BSC6900 )
for GSM neighboring cells includes the serving operator, these GSM neighboring
cells are contained in the measurement control message. If the operator group
does not include the serving operator, the RNC considers it as measurement
timeout.
Inter-RAT Filter D3
Coefficient
Inter-RAT Report EVENT_TRIGGER

Mode
2024-11-25 51
Parameter Parameter Value

Name
BSIC Verify REQUIRED(Verify mode)

Switch
Time to Trigger 0
Handover to
Verified GSM
Cell
3C Hysteresis 0
Inter-RAT DRD 3
Max Attempt
Times
Inter-RAT 3
Handover Max
Attempt Times
Inter-RAT 5
Measure Timer
Length
Event 3C Retry 1
Max Times
Time to Trigger The value of TrigTime3CForCSLimit ( BSC6910 , BSC6900 ) (D640 by default)

Event 3C for
Limit CS RAB
Inter RAT Target The value of InterRATTarThldForCSLimit ( BSC6910 , BSC6900 ) (21 by

Threshold for default)
Limit CS RAB
 If the UE does not support the capability, the RNC considers it as measurement timeout
and goes to 5.
The following scenarios are also considered as measurement timeout:
 Measurement is interrupted by other procedures.
 The RRC connection is set up and the UE enters the common state.
The RRC connection is not set up in the common state, so that this function can take effect.
For details, see section "RRC Connection Setup" in Radio Bearers Feature Parameter
Description .
4. Based on whether the RNC receives a measurement report from a UE before the timer
expires, perform the following operations:
 If the RNC receives a measurement report before the timer expires, it triggers the
inter-RAT DRD to the target GSM cell.
Inter-RAT DRD Max Attempt Times and Inter-RAT Handover Max Attempt
Times are both set to 3 and Event 3C Retry Max Times is set to 1.
 Otherwise, go to 5.
2024-11-25 52
5. Process measurement timeout.
The RNC performs the following operations based on the setting of the
CSLimitInUMTSStrategySW ( BSC6910 , BSC6900 ) parameter:
 If this parameter is set to ON, the RNC rejects the CS RAB setup and returns a failure
reason to the CN, and the value returned by the VS.RAB.FailEstabCS.RNL (
BSC6910 , BSC6900 ) counter increases by 1.
 If this parameter is set to OFF, the RNC allows the CS RAB to be set up in the serving
cell.
The measurement control priority for forbidding UEs of specific operators from setting up CS services
is higher than the priority for other types of handovers (such as the coverage-based inter-RAT
handover). Therefore, other types of handovers may be affected.
After the measurement timer expires, other inter-RAT measurements can be triggered if other inter-
RAT measurement triggering conditions are met.
13.2.2 Calls Initiated by UEs in the CELL_FACH State

For UEs in the CELL_FACH state that are enabled with the function of forbidding UEs of specific
operators from setting up CS services, the call setup procedure is as follows:
1. The RNC receives a RAB assignment message from the CN.
2. The RNC triggers the state transition from CELL_FACH to CELL_DCH.
and goes to 6.
Description .
2024-11-25 53
 Upon receiving a measurement report from a UE before the timer expires, the RNC
performs the following operations based on whether
DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH under DrSwitch ( BSC6910 ,
BSC6900 ) is selected:
 If this option is selected, the RNC triggers the inter-RAT DRD for CS+PS combined
services.
 If this option is deselected, go to 5.
5. Check the setting of the following policy switch:
CSLimitInUMTSStrategySW ( BSC6910 , BSC6900 )
 If this parameter is set to OFF, the RNC rejects the RAB setup.
In this case, PS services are retained and the RNC does not trigger D2C state transition
for the UE. If the conditions for activating the DCCC algorithm are met, the RNC can
trigger D2C state transition for PS services.
 If this parameter is set to ON, the RNC allows the RAB setup.
In this case, if the UE performs CS+PS combined services, the RNC does not trigger
D2C state transition. If the conditions for activating the DCCC algorithm are met, the
RNC can trigger D2C state transition for PS services.
When the inter-RAT DRD is triggered for CS+PS combined services, Iu-PS and Iu-CS UEs are
controlled by DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH.
cell.
In MOCN scenarios, if UEs (having an Iu-CS connection) of a specific operator are forbidden from
setting up CS services, state transition from CELL_FACH to CELL_PCH (F2P) is forbidden as well.
To enable this function, you are advised to select DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH
under the DraSwitch2 ( BSC6910 , BSC6900 ) parameter. After this option is selected, D2F
state transition is not triggered if UEs have an Iu-CS connection. In this way, the RNC can deliver
the inter-RAT measurement control message as soon as possible to reduce the F2D state
transition delay and the DRD can be triggered directly.
2024-11-25 54
13.2.3 Calls Initiated by UEs in the CELL_DCH State

For a UE enabled with the function of forbidding UEs of specific operators from setting up CS
services, if the UE has set up PS services, the call setup procedure is as follows:
1. The RNC receives a RAB assignment message from the CN.
and goes to 5.
Description .
 Upon receiving a measurement report from a UE before the timer expires, the RNC
performs the following operations based on whether
DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH under DrSwitch ( BSC6910 ,
BSC6900 ) is selected:
 If this option is selected, the RNC triggers the inter-RAT DRD for CS+PS combined
services.
 If this option is deselected, go to 4.
 If this parameter is set to OFF, the RNC rejects the RAB setup.
In this case, PS services are retained and the RNC does not trigger D2C state transition
for the UE. If the conditions for activating the DCCC algorithm are met, D2C can be
triggered.
2024-11-25 55
 If this parameter is set to ON, the RNC allows the RAB setup.
In this case, if the UE performs CS+PS combined services, the RNC does not trigger
D2C state transition. If the conditions for activating the DCCC algorithm are met, the
RNC can trigger D2C state transition for PS services.
When the inter-RAT DRD is triggered for CS+PS combined services, Iu-PS and Iu-CS UEs are
controlled by DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH.
cell.
13.2.4 Relocation to the Current Cell

For a UE enabled with the function of forbidding UEs of specific operators from setting up CS
services, if the UE is relocated to the current cell, the call setup procedure is as follows:
1. The RNC receives a relocation request from the CN in the CS domain, and then goes to 2.
This relocation may be requested by another RNC, a BSC or an eNodeB.
 If this parameter is set to OFF (default value), UEs cannot be relocated to the current
cell and the RNC returns a failure cause of "Radio Network Layer Cause" to the CN.
 If this parameter is set to ON, the UE can be relocated to the current cell.
It is recommended that this function be enabled on all the RNCs.

If this function is enabled on the SRNC, but disabled on the DRNC, the DRNC cannot decide whether CS
RABs are available on the RL upon receiving an RL request from the SRNC, causing this function not to take
effect.
2024-11-25 56
WRFD-020400 DRD Introduction Package N/A
None Measurement-based non-periodic inter-frequency DRD N/A
None Measurement-based non-periodic inter-RAT DRD N/A
Impacted Features

ID
WRFD- Ultrafast CS Call Setup Parallel processing of the alerting procedure

171202 on the called party side cannot take effect.
WRFD- UE State in Connected Mode (CELL-DCH, D2C or F2P state transition is forbidden during
010202 CELL-PCH, URA-PCH, CELL-FACH) measurement.
WRFD- Intra RNC Cell Update The UE-triggered cell update procedure does
010801 not take effect.
WRFD- DRD Introduction Package The satisfaction-based DRD function does not
020400 take effect.
WRFD- Enhanced Fast Dormancy This feature cannot take effect.

020500
WRFD- SRNS Relocation Introduction Package The RNC forbids UEs enabled with this function
020605 from relocating to another cell.
None Inter-PLMN Handovers This function does not take effect.
13.4 Network Impact

Enabling this function reduces CS services.
If DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH is selected, measurement is started for
state transition from the common state to CELL_DCH. Therefore, UEs in the common state
decrease and UEs in the CELL_DCH state increase.

This function has the following impacts:
 The inter-RAT measurement process occurs before CS RAB setups or inter-RAT DRDs, and
therefore the CS RAB setup delay increases.
2024-11-25 57
 In the case of measurement timeout, the UE is forbidden from setting up CS RABs when the
policy switch is turned off. Therefore, the CS RAB setup success rate decreases.
 After the CN delivers a RAB assignment message, the number of successful RAB
assignments and the RAB assignment success rate both decrease. When the policy switch is
turned on, the RAB assignment success rate is slightly higher than that when the policy
switch is turned off.
 UEs of a specific operator are forbidden from setting up CS RABs, and therefore the
relocation success rate decreases.
 14.1 MOCN Introduction Package
 14.2 Routing Roaming UEs in Proportion
 14.3 MOCN Cell Resource Demarcation
 14.4 MOCN Independent CE Resource Allocation
 14.5 MOCN Independent Iub Transmission Resource Allocation
 14.6 Single CN With Multi-PLMN IDs
 14.7 Forbidding UEs of Specific Operators from Setting Up CS Services
14.1 MOCN Introduction Package
14.1.1 When to Use MOCN Introduction Package

This feature is recommended if multiple operators want to share RAN equipment and frequency
resources using MOCN mode.

The information to be collected before enabling this feature is as follows:
 Whether the physical connection over the interface between the shared RNC and the CN of
each operator has been established
 Percentage of the licensed RNC-level capacity allocated to each operator
 The NRI length of the CS domain must be the same among operators. The NRI value must be
unique for each operator.
 The NRI length of the PS domain must be the same among operators. The NRI value must be
unique for each operator.
 PLMN whose ID serves as the common PLMN ID
 Whether the CN of each operator supports the MOCN feature
2024-11-25 58
 The common PLMN ID can be a new PLMN ID or the PLMN ID of one of the sharing operators. In the
latter case, ensure that the forbidden PLMN list in the SIM card of another operator's UE does not
include this PLMN ID. Otherwise, the UE cannot access the network.
 If MOCN is deployed on both GSM and UMTS networks, ensure that the forbidden PLMN list in the SIM
card of the sharing operators' UEs does not include the common PLMN ID broadcast by GSM.
Otherwise, the UMTS-to-GSM inter-RAT PS handover success rate is affected.
14.1.3 Deployment
 Other NEs
This feature requires support from the MSC, SGSN, and UE.
 Hardware
None
 Other Features
This feature cannot be used together with the WRFD-021304 RAN Sharing Introduction
Package feature.
 License
For details about how to activate the license, see License Management Feature Parameter
Description .
Feature Feature Name License Control License Control Item Name NE Sales
ID Item ID Unit
WRFD- MOCN LQW1MOCN01RES MOCN Introduction Package (Per BSC690 per

021311 Introduction Cell) 0 cell
Package BSC691
0
WRFD- MOCN LQW1MOCN01 MOCN Introduction Package (per BSC690 per

021311 Introduction Erl),MOCN Introduction Package 0 Erl
Package (per Mbps) BSC691 per
0 Mbps
In the RAN Sharing/MOCN scenario, the primary and secondary operators do not support
license allocation by operator.
1. The common PLMN ID can be a new PLMN ID or the PLMN ID of one of the sharing
operators. In the latter case, ensure that the forbidden PLMN list in the SIM card of another
operator's UE does not include this PLMN ID. Otherwise, the UE cannot access the network.
2. If MOCN is deployed on both GSM and UMTS networks, ensure that the forbidden PLMN list
in the SIM card of the sharing operators' UEs does not include the common PLMN ID
broadcast by GSM. Otherwise, the UMTS-to-GSM inter-RAT PS handover success rate is
affected.
2024-11-25 59
3. The operator's PLMN ID on the RNC side (Global RNC ID) must be consistent with that on
the CN side (Global CN ID). If inconsistent, the messages delivered by the CN will be
discarded.
4. The MOCN Introduction Package feature has two license control items: MOCN Introduction
Package (per Cell) and MOCN Introduction Package (per Erl),MOCN Introduction Package
(per Mbps). To deploy this feature, enable any of the two licenses, to which different control
modes apply on the RNC:
 MOCN Introduction Package (per Cell): The license control items must be added (by
running the ADD UCELLLICENSE command) to the cells serving the secondary
operators. Such cells include those dedicated to the secondary operators and those
shared by the primary and secondary operators.
 MOCN Introduction Package (per Erl),MOCN Introduction Package (per Mbps): The
license control items must be purchased and activated for the cells serving the
secondary operators.
 If a commissioning license control item 'MOCN Introduction Package (per Erl),MOCN

Introduction Package (per Mbps)' is converted into a commercial license control item
'MOCN Introduction Package (per Cell)', the license must be added (by running the
ADD UCELLLICENSE command) to all cells serving the secondary operators.
Otherwise, cell setup will fail.
5. The UE's serving operator cannot be accurately identified during RRC connection setup.
Therefore, you are advised to disable the single signaling handover function or the RRC
DRD function to prevent the UE from being handed over or DRD-switched to a cell of
another operator during RRC connection setup.
 Run the SET UCORRMALGOSWITCH command with HO_MC_SIGNAL_SWITCH under

the HoSwitch ( BSC6910 , BSC6900 ) parameter deselected to disable the single
signaling handover function.
 Run the SET UCORRMALGOSWITCH command with DR_RRC_DRD_SWITCH under

the DrSwitch ( BSC6910 , BSC6900 ) parameter deselected to disable the RRC DRD
function.
14.1.3.3 Activation (Using MML Commands)
Adding Operators and Operator Groups
Determine an operator type before using the MOCN feature. You can set the operator type to the
primary, secondary, outer, or common operator by setting the Operator Type parameter to
PRIM(Primary Operator), SEC(Secondary Operator), OUTER(Outer Operator), or
COMM(Common Operator), respectively. The four operator types are described in Table 14-1.
Table 14-1 Operator types
2024-11-25 60
Operator Parameter Description

Type Value
Primary PRIM(Primary This type determines the functions to be supported by the entire
operator Operator) RAN system and allocates licenses to secondary operators.
Primary operators permit registration and access of UEs.
Secondary SEC(Secondary This type determines the functions to be supported by the entire
operator Operator) RAN system and the licenses of secondary operators are
controlled by the primary operator. Secondary operators permit
access of UEs.
Outer OUTER(Outer In mobility management, UEs need to be handed over from the
operator Operator) operator of the SRNC to the operator of the TRNC.
If an operator is not a primary operator or a secondary operator of
the SRNC, the operator can be defined as an outer operator to
support mobility management.
Common COMM(Common The PLMN ID is indicated in the system broadcast information. UEs
operator Operator) that do not support HSDPA consider the corresponding operator as
the serving operator, as in conventional networks.
Common operators support non-supporting UEs.
1. Run the RNC MML command ADD UCNOPERATOR to add an operator to the RNC.
To facilitate maintenance and management, the concept of operator group is introduced.
Each operator group must be configured with one to four operators. Each cell corresponds
to an operator group. You can use the RNC MML command ADD UCNOPERGROUP to add
an operator group.
2. Select MOCN_CNOPGRP_CONFIG_CMP_SWITCH under the MocnControlSwitch2 (

BSC6910 , BSC6900 ) parameter in the SET UOPERATORSHARINGMODE command.
An operator group can be configured as different operator groups, in which the operators are
arranged in different orders. Non-supporting UEs select the network to access according to the order
of operators in each group. For example, operators A, B, and C can be configured as two operator
groups with the IDs of 0 and 1. The sequence of the operator group with the ID of 0 is A, B, and C.
The sequence of the other operator group with the ID of 1 is B, A, and C. To implement this
configuration, you can turn on the RNC-level function switch specified by selecting the
MOCN_CNOPGRP_CONFIG_CMP_SWITCH option or select the
MOCN_REDIR_BY_CONFIG_OP_SEQ option under the CellConnAlgoSwitch2 parameter in the
ADD UCELLCONNALGOPARA command.
Setting the Operator Sharing Mode
1. Run the RNC MML command SET UOPERATORSHARINGMODE with the MOCN Support
parameter set to YES and RAN Sharing Support set to NO.
For special requirements on MOCN control, configure the switches under the
UOPERATORSHARINGMODE command. The following table describes the switches under
the MocnControlSwitch2 parameter and their recommended settings.
2024-11-25 61
Switch Setting Notes
PLMN_SEL_ALGO_SWITCH Whether the RNC sends a redirect flag to the CN when a

UE is initiating services. You are advised to turn on this
switch. When this switch is turned off, the RNC sends an
Initial UE Message with the redirect flag to the CN. If the
CN does not respond to this message, the RNC forwards
the message to other CN nodes.
PLMN_ACCEPT_BY_DL_DT_SWITCH Whether the RNC makes a redirection attempt based on

the DIRECT TRANSFER message if the CN does not
support the redirect flag. When this switch is turned on,
the RNC performs the processing according to Huawei
proprietary protocols (not standard protocols), and UE
compatibility issues may occur as a result. You are
advised to turn off this switch.
PLMN_PRIORITY_SEL_SWITCH Whether the RNC preferentially selects the default

operator for a UE using its TMSI for registration when the
NRI of the UE is mapped to a CN node. When this switch
is turned on, unnecessary redirection attempts may be
made. You are advised to turn off this switch.
PLMN_SEL_BY_INT_DT_SWITCH Whether the RNC sends the redirect flag when the cause
value carried in the IE "NAS-PDU" in the DIRECT
TRANSFER message is "LOCATION UPDATING REQUEST",
"ROUTING AREA UPDATE REQUEST", "ATTACH
REQUEST", or REGISTRATION." You are advised to turn
on this switch.
MOCN_SUPP_UE_ACT_AS_NOSUPP_SWITC Whether the RNC regards MOCN supporting UEs as

H MOCN non-supporting UEs when MOCN is applied. When
this switch is turned on, the RNC performs the
processing according to Huawei proprietary protocols
(not standard protocols), and UE compatibility issues
may occur as a result. You are advised to turn off this
switch.
MOCN_CNOPGRP_CONFIG_CMP_SWITCH Whether two operator groups can have the same

operators but in different orders.
EMER_CSFB_MOCN_AS_NON_MOCN_SWIT Whether the RNC reroutes a supporting UE as a non-

CH supporting UE to an available CN of another operator for
successfully admitting the emergency call initiated by
the supporting UE when the RNC detects that all CS CNs
of the operator selected by the supporting UE are faulty.
You are advised to turn on this switch.
2. Run the RNC MML command SET UOPERATORCFGPARA with Feature Supporting
Mode of CS Domain set to SUPP_MOCN and Feature Supporting Mode of PS
Domain set to SUPP_MOCN for the primary and secondary operators and with other
parameters specified.
3. Run the RNC MML command SET URRCTRLSWITCH to set compatibility switches for
MOCN.
a. Select UL_DT_SAI_PLMN_CMP_SWITCH under the PROCESSSWITCH5 ( BSC6910

, BSC6900 ) parameter and fill the PLMN of the best cell in the SAI IE.
b. Select MOCN_SAME_DOMAIN_DISC_INIT_DT_SWITCH under the

OptimizationSwitch8 ( BSC6910 , BSC6900 ) parameter.
2024-11-25 62
c. (Optional) If the SPID-related feature is also activated, select

MOCN_REDIR_GET_SPID_OPT_SWITCH under the OptimizationSwitch8 (
BSC6910 , BSC6900 ) parameter. Non-supporting UEs select the SPID of the most
recent serving operator.
d. (Optional) If the IMSI-based handover feature is also activated, select

RNC_IMSI_HO_OPT_SWITCH under the OptimizationSwitch4 ( BSC6910 ,
BSC6900 ) parameter.
If a certain operator has Iu Flex enabled, when you run the SET UOPERATORCFGPARA command,
set Feature Supporting Mode of CS Domain and Feature Supporting Mode of PS Domain to
SUPP_IUFLEX_MOCN for this operator. In addition, set the CS NRI length and PS NRI length.
Configuring the Iu interface for Each Operator
1. Run the RNC MML command ADD OPC for multiple times to configure originating signaling
points (OSPs) for the primary and secondary operators.
The primary and secondary operators can be configured with the same or different OSPs.
The Network ID parameter in the ADD OPC command can be set to the same or different values for
the primary and secondary operators.
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.
2. Run the RNC MML command ADD N7DPC for multiple times to configure destination
signaling points (DSPs) for the primary and secondary operators.
3. Configure Iu data for the primary and secondary operators.
4. Run the RNC MML command ADD UCNNODE for multiple times to add CN nodes for the
primary and secondary operators.
In MOCN scenarios, you do not need to run the ADD OPC command to configure an OSP for each operator.
You only need to configure an OSP for the primary operator or a secondary operator. It is good practice to
configure the OSP based on the OSP code of the primary operator.
Configuring MOCN Load Balance
1. Load balancing is classified into geographic-area load balancing and intra-RNC load
balancing. You are advised to configure geographic-area load balancing. Run the SET
UOPERATORSHARINGMODE command to set the Default CnOperator parameter in
order to specify the preferred CN operator.
2024-11-25 63
To configure intra-RNC load balancing, run the SET UOPERATORSHARINGMODE command with
the Default CnOperator parameter set to 255.
2. (Optional) Run the ADD UCELLCONNALGOPARA command with

MOCN_REDIR_BY_CONFIG_OP_SEQ under the CellConnAlgoSwitch2 parameter
selected. If the cell-level switch is turned on, a non-supporting UE can select the CN
according to the sequence of operators in the configured operator group when the NRI in
the IMSI or TMSI of cannot be used to identify the CN.
Configuring the Multiple PLMN List
1. Run the SET UOPERATORSHARINGMODE command with

COMM_MIB_MULTI_PLMN_LIST_ALLOWED_SWITCH under the Mocn Control Switch
parameter selected to enable the MIB in the cell system information to carry the Multiple
PLMN List.
Turning on this switch causes the Multi PLMN list IE to be included in an MIB message, increasing the
message size. This may cause procedure overlapping on certain UEs when reading the message.
2. Run the SET URRCTRLSWITCH command with SYS_INFO_UPDATE_FOR_IU_RST under

the Process switch parameter selected.
 The PLMN ID of the operator is deleted from the MIB if the CS/PS Iu interface is faulty.
 The PLMN ID of the operator is included in the Multiple PLMN List if the CS/PS Iu
interface is recovered.
Configuring Inter-PLMN Mobility Management
To minimize the impact on dedicated cell resource usage, the MOCN Cell Resource Demarcation
feature, and subscriber charging, inter-PLMN handovers and multi-carrier setup are generally
prohibited in MOCN scenarios. To prohibit them, run the SET UOPERATORSHARINGMODE
command with Intra RAT Inter Plmn Ho Allowed, Inter RAT Inter Plmn Ho Allowed, and
Inter-PLMN Multicarrier HSDPA Switch set to NO.
To allow them, run the SET UOPERATORSHARINGMODE command with Intra RAT Inter
Plmn Ho Allowed, Inter RAT Inter Plmn Ho Allowed, and Inter-PLMN Multicarrier HSDPA
Switch set to YES.
To configure different inter-frequency handover parameters for different operators, run the ADD
UHOCOVTEMPLATE command with Template Index specified and the following parameters
set to appropriate values: EcN0 Thld for Starting Inter-Freq Measurement, RSCP Thld for
Starting Inter-Freq Measurement, EcN0 Thld for Stopping Inter-Freq Measurement,
and RSCP Thld for Stopping Inter-Freq Measurement. Then run the ADD
UCELLOperHOCOV command with Template Index specified for an operator. Special users
2024-11-25 64
still use the inter-frequency measurement start and termination thresholds. For details, see Voice
Service Experience Improvement for Weak Reception UEs Feature Parameter Description.
To configure different UMTS-to-LTE/UMTS-to-UMTS/UMTS-to-GSM inter-PLMN handover targets for
different operators, specify different values for the TarCnOpIndex parameter in the RNC MML
command ADD UINTERPLMNHOLIST.
Configuring NRI and CN Node Mapping
Before configuring the NRI and CN node mapping, run the RNC MML command ADD UCNNODE
to add CN nodes for the primary and secondary operators.
Generally, the RNC selects the route from a UE to a CN node based on the NRI. The mapping
between an NRI and a CN node must be configured on both the CN and RNC sides. The mapping
on the RNC side is configured by running the ADD UNRIGLBCNIDMAP command.
The NRI configured on the RNC side must be negotiated with the CN so that it is the same as the
NRI configured on the CN side.
The mapping between NRIs and CN nodes needs to be configured based on network plan.
Adding NodeBs and Cells
1. Adding NodeBs
Run the RNC MML command ADD UNODEB with the following parameter settings:
 Set Sharing Type Of NodeB to MOCN(MOCN) to add a MOCN NodeB. Set Resource
Management Mode to SHARE(Share) to enable Iub transmission resource sharing.
 Set Sharing Type Of NodeB to DEDICATED(Dedicated) to add a dedicated NodeB.
2. Adding cells
To configure an operator group for a cell, run the ADD UCELLSETUP or ADD
UCELLQUICKSETUP command. If the operator group contains multiple operators
(including the primary operator and secondary operator), the cell is shared by multiple
operators. If the operator group contains only one operator, the cell is dedicated to the
operator. You must configure the Location Area Code (LAC) and Routing Area Code (RAC)
for all the operators in the operator group. If a cell is shared by multiple operators, you only
need to configure the Service Area Code (SAC) for one of them by running the ADD USAC
command. A UE under an RNC can be configured with a maximum of 32 operator groups.
If there is an operator-dedicated cell under the RNC, run the RNC MML command SET UNBMPARA
with PERFENH_ONE_CNOP_NO_PLMN_LIST_SWITCH under the PerfEnhanceSwitch2 (
BSC6910 , BSC6900 ) parameter selected.
Activating MOCN Introduction Package
2024-11-25 65
1. Run the MML command ADD UCELLLICENSE with

MOCN_INTRODUCE_PACK_SWITCH(MOCN Introduce Pack Switch) under the
Function Switch1 parameter selected to enable the cell-level MOCN function.
If the license for MOCN Introduction Package is not activated but MOCN is enabled in a cell, the
INITIAL DIRECT TRANSFER message for the primary operator's users may be lost, and the INITIAL
DIRECT TRANSFER message for the secondary operator's users will be sent to the primary operator's
CN.
After the MOCN_CELL_NO_LICENSE_CMP_SWITCH option under the MocnControlSwitch2 (
BSC6910 , BSC6900 ) parameter in the SET UOPERATORSHARINGMODE command is selected,
the INITIAL DIRECT TRANSFER message for the primary operator's users will be sent to the primary
operator's CN, and the INITIAL DIRECT TRANSFER message for the secondary operator's users will be
discarded.
2. Run the RNC MML command SET LICENSE to set the following RNC-level traffic license
items and feature-related license resource items for primary and secondary operators:
Voice Erlang-Erlang, PS throughput only-kbps, HSDPA Throughput-kbps, and
HSUPA Throughput-kbps. The license function items are controlled using parameters
Function Switch1 through Function Switch6. For the license allocation method of a
specific feature among operators in MOCN scenarios, see section "License Control for
Multiple Operators" in License Management Feature Parameter Description .
In MOCN-enabled networks, the licensed value can be automatically or manually allocated
for the primary and secondary operators:
 Automatic allocation: Run the SET LICENSE command with FeatureResAssignMode

set to AutoAssign. In this mode, the licensed values need to be specified only for the
basic reference items. The licensed values for other resource items will be
automatically allocated to the primary and secondary operators in the same proportion
as the basic reference items. The four basic reference items include: Voice Erlang-
Erlang, PS throughput only-kbps, HSDPA Throughput-kbps, and HSUPA Throughput-
kbps.
 Manual allocation: Run the SET LICENSE command with FeatureResAssignMode set
to ManualAssign. In this mode, the licensed values for each resource item must be
manually specified for the primary and secondary operators.
The RNC-level traffic licenses cannot be shared among operators and therefore must be
separately allocated.
The RNC cannot identify the operator of a UE during the RRC connection setup. Therefore, a UE
can be admitted to the network by any operator during the RRC connection setup procedure.
Modifying Dedicated NodeBs and Cells in MOCN Networks
1. Run the RNC MML command MOD UNODEB to change a dedicated NodeB into a shared
NodeB.
2024-11-25 66
2. Run the RNC MML command DEA UCELL to deactivate a cell. In this step, set Cell ID to an
appropriate value.
3. Run the RNC MML command MOD UCELLSETUP to change CnOpGrpIndex so that cells
are shared by multiple operators.
4. Run the RNC MML command ACT UCELL to activate a cell. In this step, set Cell ID to an
appropriate value.
14.1.3.4 Activation (Using the MAE-Deployment)
Using the MAE-Deployment
For detailed operations, see Feature Configuration Using the MAE-Deployment .
1. Check whether the Multiple PLMN List has taken effect in an MOCN cell by checking
messages traced over the Uu interface. As shown in Figure 14-1 and Figure 14-2, the ID of
the common PLMN is 302580, and the PLMN IDs 302221 and 302640 are contained in the
Multiple PLMN List. In dedicated cells or cells under dedicated NodeBs, system information
is broadcast in the same way as in a non-MOCN network.
Figure 14-1 plmn-Identity IE in the MIB message
2024-11-25 67
Figure 14-2 multiplePLMN-List IE in the MIB message
2. Check whether the MOCN introduction package has been activated by registering
supporting and non-supporting UEs in MOCN cells of the primary and secondary operators.
If the UEs are registered successfully and properly initiate CS and PS services, the MOCN
introduction package has been activated.
3. (Optional) Check whether the MOCN load balancing function has been activated by
checking the value of the VS.IU.MOCN.CsPsCoordination ( BSC6910 , BSC6900 )
counter. If the counter values for all operators are similar, the MOCN load balancing
function has been activated.
4. (Optional) Check whether the inter-PLMN handover switch has been turned on by checking
whether UEs can perform inter-PLMN handovers, relocations, and cell updates. If UEs can
perform inter-PLMN handovers, relocations, and cell updates, inter-PLMN handover has
been activated.
5. (Optional) Check whether the inter-PLMN multi-carrier HSPA switch has been turned on by
checking whether UEs can set up inter-PLMN multi-carriers. If UEs can set up inter-PLMN
multi-carriers, inter-PLMN multi-carrier HSPA has been activated.
14.1.3.6 Deactivation (Using MML Commands)
1. Deactivate shared NodeBs and cells.
a. Run the RNC MML command DEA UCELL to deactivate the cell. In this step, set Cell
ID to an appropriate value.
b. Run the RNC MML command MOD UCELLSETUP to change the CnOpGrpIndex so
that cells are dedicated to a certain operator.
2024-11-25 68
c. Run the RNC MML command MOD UNODEB to change a shared NodeB into a
dedicated NodeB.
d. Run the RNC MML command ACT UCELL to activate non-shared cells again.
2. Deactivate operator sharing.
a. Run the RNC MML command SET UOPERATORSHARINGMODE with MOCN

Support set to NO.
b. Run the RNC MML command SET UOPERATORCFGPARA to set Feature

Supporting Mode of CS Domain and Feature Supporting Mode of PS Domain
to SUPP_NONE.
If a certain operator has Iu Flex enabled, when you run the SET UOPERATORCFGPARA
command, set Feature Supporting Mode of CS Domain and Feature Supporting Mode
of PS Domain to SUPP_IUFLEX for this operator.
14.1.3.7 Deactivation (Using the MAE-Deployment)
14.1.3.8 MML Command Examples

//Configuring MOCN Introduction Package
//Setting the primary operator

ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PrimOp", MCC="302", MNC="221",
CnOpIndex=0;
//Setting a secondary operator

ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SecOp", MCC="302", MNC="640", CnOpIndex=1;
//Setting the common operator

ADD UCNOPERATOR: OperatorType=COMM, CnOperatorName="Common", MCC="302", MNC="580",
CnOpIndex=5;
//Setting the Iu interface for different operators

//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
2024-11-25 69
ADD N7DPC: NAME="PRIMCS", DPX=0, SPX=0, SPDF=WNF, DPC=3, DPCT=IUCS, BEARTYPE=M3UA;

ADD N7DPC: NAME="PRIMPS", DPX=1, SPX=0, SPDF=WNF, DPC=4, DPCT=IUPS, BEARTYPE=M3UA;
//Configuring the DSP for a secondary operator

ADD N7DPC: NAME="SECCS", DPX=2, SPX=1, SPDF=WNF, DPC=5, DPCT=IUCS, BEARTYPE=M3UA;
ADD N7DPC: NAME="SECPS", DPX=3, SPX=1, SPDF=WNF, DPC=6, DPCT=IUPS, BEARTYPE=M3UA;
//Configuring manual allocation of licensed resource capacity for primary and secondary operators
SET LICENSE: SETOBJECT=UMTS, OperatorType=PRIM, CNOPERATORINDEX=0, CsErlang=5000,
Psthroughput=5000, HSDPAthroughput=5000, HSUPAthroughput=5000;
SET LICENSE: SETOBJECT=UMTS, OperatorType=SEC, CNOPERATORINDEX=1, CsErlang=4000,
Psthroughput=4000, HSDPAthroughput=4000, HSUPAthroughput=4000;
//(Optional) Configuring automatic allocation of licensed resource capacity for primary and secondary operators
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;
//Setting the operator group
ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="ShareCnOpGrp", CnOpNum=TWO, CnOpIndex1=0,
CnOpIndex2=1, CnOpIndexComm=5;
ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="DedicatedOp", CnOpNum=ONE, CnOpIndex1=0;
//Setting the operator sharing mode

SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES,
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO, InterPlmnMultiCarrSwitch=NO,
DefaultCnOp=255, MocnControlSwitch=COMM_MOCN_NRI_GLOBAL_CONFIG_MODE_SWITCH-
1&COMM_MIB_MULTI_PLMN_LIST_ALLOWED_SWITCH-1, MocnControlSwitch2=PLMN_SEL_ALGO_SWITCH-
1&PLMN_SEL_BY_INT_DT_SWITCH-1&EMER_CSFB_MOCN_AS_NON_MOCN_SWITCH-1;
//Setting parameters for the primary operator

SET UOPERATORCFGPARA: CnOpIndex=0, CsNriCfgMode=SUPP_MOCN, PsNriCfgMode=SUPP_MOCN,
CSNRILength=7, PSNRILength=10, NullNRI=0;
//Setting parameters for a secondary operator

//Adding CN node 10 for the primary operator
2024-11-25 70
ADD UCNNODE: CnOpIndex=0, CNId=10, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R5,

SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS,
RTCPSwitch=OFF, Switch3GPP25415CR0125=OFF;
//Adding CN node 20 for the primary operator

ADD UCNNODE: CnOpIndex=0, CNId=20, CNDomainId=PS_DOMAIN, Dpx=1, CNProtclVer=R5,
SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, Switch3GPP25415CR0125=OFF;
//Adding CN node 11 for a secondary operator


ADD UCNNODE: CnOpIndex=1, CNId=21, CNDomainId=PS_DOMAIN, Dpx=3, CNProtclVer=R5,
SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, Switch3GPP25415CR0125=OFF;
//Adding mapping between CN node 10 and an NRI for the primary operator
ADD UNRIGLBCNIDMAP: CnOpIndex=0, CNId=10, NRI=10;
//Adding mapping between CN node 20 and an NRI for the primary operator
//Adding mapping between CN node 11 and an NRI for the secondary operator
//Adding mapping between CN node 21 and an NRI for the secondary operator
//Adding an MOCN NodeB

ADD UNODEB: NodeBName="NodeB1", NodeBId=1, SRN=0, SN=0, TnlBearerType=IP_TRANS,
IPTRANSAPARTIND=NOT_SUPPORT, HostType=SINGLEHOST, SharingType=MOCN;
//Adding a dedicated NodeB

ADD UNODEB: NodeBName="NodeB2", NodeBId=2, SRN=0, SN=0, TnlBearerType=IP_TRANS,
IPTRANSAPARTIND=NOT_SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0;
//Setting the location area for the primary operator

ADD ULAC:CNOPINDEX=0, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256;
//Setting the location area for a secondary operator

ADD ULAC:CNOPINDEX=1, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256;
2024-11-25 71
//Setting the routing area for the primary operator

ADD URAC: CnOpIndex=0, LAC=H'7208, RAC=H'00, PLMNVALTAGMIN=6, PLMNVALTAGMAX=120;
//Setting the routing area for a secondary operator

ADD URAC: CnOpIndex=1, LAC=H'7208, RAC=H'00, PLMNVALTAGMIN=6, PLMNVALTAGMAX=120;
//Adding an MOCN cell

ADD UCELLQUICKSETUP: CellId=1, CellName="Cell1", CnOpGrpIndex=0, BandInd=Band1,
UARFCNDownlink=10562, PScrambCode=0, TCell=CHIP256, LAC=H'7208, SAC=H'0000, CfgRacInd=REQUIRE,
RAC=H'00, SpgId=6, URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7,
URA8=8, NodeBName="NodeB1", LoCell=0, SupBmc=FALSE;
//Adding a dedicated cell

ADD UCELLQUICKSETUP: CELLID=2, CELLNAME="Cell2", CnOpGrpIndex=1,
BANDIND=BAND1,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, PSCRAMBCODE=0, TCELL=CHIP256,
LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId = 6,URANUM=D8, URA1=1, URA2=2,
URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8, NODEBNAME="NodeB2", LOCELL=2, SUPBMC=FALSE;
SET UNBMPARA: LogicRncId=1, PerfEnhanceSwitch2=PERFENH_ONE_CNOP_NO_PLMN_LIST_SWITCH-1;
//(Optional) Setting the protocol version of the local RNC to R7 or later on the peer neighboring RNC before
enabling MOCN on the local RNC
MOD UNRNC: NRncId=1, RncProtclVer=R7;
//Adding a cell controlled by a neighboring RNC
ADD UEXT3GCELL: NRncId=1, CellId=1, CellHostType=SINGLE_HOST, CellName="Cell1", CnOpGrpIndex=0,
PScrambCode=0, BandInd=Band1, UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700,
TxDiversityInd=FALSE, LAC=h'2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE, QrxlevminInd=FALSE,
MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED, CellCapContainerFdd=EDCH_SUPPORT-1,
EFachSupInd=FALSE;
//Activating the cell-level license switch for the MOCN feature

ADD UCELLLICENSE: CellId=1, FuncSwitch1=MOCN_INTRODUCE_PACK_SWITCH-1;
//Configuring different inter-frequency handover measurement parameters for different operators in an

operator group
//Adding No.0 inter-frequency measurement triggering template
ADD UHOCOVTEMPLATE: TemplateIndex=0, InterFreqThd2DEcN0=-12, InterFreqThd2DRSCP=-90,
InterFreqThd2FEcN0=-10, InterFreqThd2FRSCP=-83;
//Applying template 0 to operator 2 of a cell
ADD UCELLOPERHOCOV: CellId=11011, CnOpIndex=2, TemplateIndex=0;
//Allowing the configuration of different operator groups for the same operators but in different orders
2024-11-25 72
SET UOPERATORSHARINGMODE: MOCNSupport=YES,

MocnControlSwitch2=MOCN_CNOPGRP_CONFIG_CMP_SWITCH-1;
//Enabling non-supporting UEs in a cell to access CNs according to the configured sequence
ADD UCELLCONNALGOPARA: CellId=11011, CellConnAlgoSwitch2=MOCN_REDIR_BY_CONFIG_OP_SEQ-1;
//Configuring inter-PLMN handover targets by operator

InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES, InterPlmnMultiCarrSwitch=NO,
DefaultCnOp=255, MocnControlSwitch=COMM_MOCN_NRI_GLOBAL_CONFIG_MODE_SWITCH-
1&COMM_MIB_MULTI_PLMN_LIST_ALLOWED_SWITCH-1, MocnControlSwitch2=PLMN_SEL_ALGO_SWITCH-
1&PLMN_SEL_BY_INT_DT_SWITCH-1&EMER_CSFB_MOCN_AS_NON_MOCN_SWITCH-1;
ADD UINTERPLMNHOLIST:LogicRncId=1,CnOpIndex=0,TarRAT=U2L,TarCnOpIndex=1;
ADD UINTERPLMNHOLIST:LogicRncId=1,CnOpIndex=0,TarRAT=U2U,TarCnOpIndex=1;
ADD UINTERPLMNHOLIST:LogicRncId=1,CnOpIndex=0,TarRAT=U2G,TarCnOpIndex=1;
//Deactivating the MOCN Introduction Package
//Deactivating shared NodeBs and cells
DEA UCELL: CellId=1;
MOD UCELLSETUP: CellId=1, CnOpGrpIndex=1;
MOD UNODEB: IDTYPE=BYID, CnOpIndex=0,NodeBId=1, SharingType= DEDICATED;
ACT UCELL: CellId=1;
//Deactivating operator sharing mode
SET UOPERATORSHARINGMODE: MOCNSupport=NO;
SET UOPERATORCFGPARA: CnOpIndex=0, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode= SUPP_IUFLEX,
CSNRILength=5, NullNRI=10, PSNRILength=5;

In MOCN scenarios, the RNC can measure some key cell-level counters by operator. When the
STAT_KEY_CELLCOUNTER_WITH_CNOPER_SW option of the OptimizationSwitch13 (
BSC6910 , BSC6900 ) parameter in the SET URRCTRLSWITCH command is selected, the RNC
measures the following cell-level KPIs by operator. You can observe the number of UEs, traffic
volume, and RAB setup and release of different operators in a cell.
Counter Name Counter Description
VS.AMR.Erlang.BestCell.MOCN.PLMN0 ( BSC6910 , Equivalent Erlang for AMR Services for

BSC6900 )~VS.AMR.Erlang.BestCell.MOCN.PLMN3 ( Best Cell for Operators 0 to 3 in MOCN
BSC6910 , BSC6900 ) Cell
VS.SRNCIubBytesPSR99.Tx.MOCN.PLMN0 ( BSC6910 Number of DL Bytes of PS Services

, BSC6900 over Iub DCH for Operators 0 to 3 in
)~VS.SRNCIubBytesPSR99.Tx.MOCN.PLMN3 ( MOCN Cell
BSC6910 , BSC6900 )
VS.SRNCIubBytesHSDPA.Tx.MOCN.PLMN0 ( BSC6910 Number of DL Bytes over Iub HSDSCH

, BSC6900 for Operators 0 to 3 in a MOCN Cell
)~VS.SRNCIubBytesHSDPA.Tx.MOCN.PLMN3 (
BSC6910 , BSC6900 )
VS.SRNCIubBytesPSR99.Rx.MOCN.PLMN0 ( BSC6910 Number of UL Bytes of PS Services

, BSC6900 over Iub DCH for Operators 0 to 3 in
2024-11-25 73
)~VS.SRNCIubBytesPSR99.Rx.MOCN.PLMN3 ( MOCN Cell

BSC6910 , BSC6900 )
VS.SRNCIubBytesHSUPA.Rx.MOCN.PLMN0 ( BSC6910 Number of UL Bytes over Iub EDCH for

, BSC6900 Operators 0 to 3 in a MOCN Cell
)~VS.SRNCIubBytesHSUPA.Rx.MOCN.PLMN3 (
BSC6910 , BSC6900 )
VS.RAB.AbnormRel.AMR.MOCN.PLMN0 ( BSC6910 , Number of CS AMR RABs Abnormally

BSC6900 )~VS.RAB.AbnormRel.AMR.MOCN.PLMN3 ( Released for Operators 0 to 3 in a
BSC6910 , BSC6900 ) MOCN Cell
VS.RAB.AbnormRel.AMRWB.MOCN.PLMN0 ( BSC6910 Number of CS AMRWB RABs

, BSC6900 Abnormally Released for Operators 0
)~VS.RAB.AbnormRel.AMRWB.MOCN.PLMN3 ( to 3 in a MOCN Cell
BSC6910 , BSC6900 )
VS.RAB.AbnormRel.PS.MOCN.PLMN0 ( BSC6910 , Number of PS RABs Abnormally

BSC6900 )~VS.RAB.AbnormRel.PS.MOCN.PLMN3 ( Released for Operators 0 to 3 in a
VS.RAB.AbnormRel.CS.CN.MOCN.PLMN0 ( BSC6910 , Number of Abnormally Released CS

BSC6900 )~VS.RAB.AbnormRel.CS.CN.MOCN.PLMN3 RABs Triggered by CN for Operators 0
( BSC6910 , BSC6900 ) to 3 in a MOCN Cell
VS.RAB.AbnormRel.PS.CN.MOCN.PLMN0 ( BSC6910 , Number of Abnormally Released PS

BSC6900 )~VS.RAB.AbnormRel.PS.CN.MOCN.PLMN3 RABs Triggered by CN for Operators 0
( BSC6910 , BSC6900 ) to 3 in a MOCN Cell
VS.RAB.NormRel.AMR.MOCN.PLMN0 ( BSC6910 , Number of CS AMR RABs Normally

BSC6900 )~VS.RAB.NormRel.AMR.MOCN.PLMN3 ( Released for Operators 0 to 3 in a
VS.RAB.NormRel.AMRWB.MOCN.PLMN0 ( BSC6910 , Number of CS AMRWB RABs Normally

BSC6900 )~VS.RAB.NormRel.AMRWB.MOCN.PLMN3 ( Released for Operators 0 to 3 in a
VS.RAB.NormRel.PS.MOCN.PLMN0 ( BSC6910 , Number of PS RABs Normally Released

BSC6900 )~VS.RAB.NormRel.PS.MOCN.PLMN3 ( for Operators 0 to 3 in a MOCN Cell
BSC6910 , BSC6900 )
VS.RAB.AbnormRel.PS.DF2P.MOCN.PLMN0 ( Number of RABs Abnormally Released

BSC6910 , BSC6900 for PS Services during the State
)~VS.RAB.AbnormRel.PS.DF2P.MOCN.PLMN3 ( Transition to CELL_PCH or URA_PCH for
BSC6910 , BSC6900 ) Operators 0 to 3 in a MOCN Cell
VS.RAB.AbnormRel.PS.PCH.MOCN.PLMN0 ( BSC6910 Number of Abnormally Released PS

, BSC6900 RABs that Are in CELL_PCH or URA_PCH
)~VS.RAB.AbnormRel.PS.PCH.MOCN.PLMN3 ( State for Operators 0 to 3 in a MOCN
VS.RAB.NormRel.PS.PCH.MOCN.PLMN0 ( BSC6910 , Number of Normally Released PS RABs

BSC6900 )~VS.RAB.NormRel.PS.PCH.MOCN.PLMN3 ( that Are in CELL_PCH or URA_PCH
BSC6910 , BSC6900 ) State for Operators 0 to 3 in a MOCN
Cell
VS.DCCC.DF2P.Succ.MOCN.PLMN0 ( BSC6910 , Number of Successful State Transfers

BSC6900 )~VS.DCCC.DF2P.Succ.MOCN.PLMN3 ( to CELL_PCH or URA_PCH for Operators
BSC6910 , BSC6900 ) 0 to 3 in a MOCN Cell
VS.RRC.SuccConnEstab.Sum.MOCN.PLMN0 ( Number of Processed RRC Connection
2024-11-25 74
BSC6910 , BSC6900 Setup Successes of Operators 0 to 3

)~VS.RRC.SuccConnEstab.Sum.MOCN.PLMN3 ( for MOCN Cell
BSC6910 , BSC6900 )
VS.RRC.SuccConnEstab.CS.MOCN.PLMN0 ( BSC6910 , Number of RRC CSCall Connection

BSC6900 )~VS.RRC.SuccConnEstab.CS.MOCN.PLMN3 Successes for Operators 0 to 3 in a
( BSC6910 , BSC6900 ) MOCN Cell
VS.RRC.SuccConnEstab.PS.MOCN.PLMN0 ( BSC6910 , Number of RRC PSCall Connection

BSC6900 )~VS.RRC.SuccConnEstab.PS.MOCN.PLMN3 Successes for Operators 0 to 3 in a
VS.RAB.SuccEstabCS.AMR.MOCN.PLMN0 ( BSC6910 , Number of Successful CS AMR RAB

BSC6900 )~VS.RAB.SuccEstabCS.AMR.MOCN.PLMN3 Establishments for Operators 0 to 3 in
( BSC6910 , BSC6900 ) a MOCN Cell
VS.RAB.SuccEstabCS.AMRWB.MOCN.PLMN0 ( Number of Successful CS Wideband

BSC6910 , BSC6900 AMR RAB Establishments for Operators
)~VS.RAB.SuccEstabCS.AMRWB.MOCN.PLMN3 ( 0 to 3 in a MOCN Cell
BSC6910 , BSC6900 )
VS.RAB.AttEstab.AMR.MOCN.PLMN0 ( BSC6910 , Number of CS AMR Service RAB

BSC6900 )~VS.RAB.AttEstab.AMR.MOCN.PLMN3 ( Establishment Attempts for Operators
BSC6910 , BSC6900 ) 0 to 3 in a MOCN Cell
VS.RAB.AttEstabCS.AMRWB.MOCN.PLMN0 ( BSC6910 Number of CS Wideband AMR Service

, BSC6900 RAB Establishment Attempts for
)~VS.RAB.AttEstabCS.AMRWB.MOCN.PLMN3 ( Operators 0 to 3 in a MOCN Cell
BSC6910 , BSC6900 )
VS.RAB.AttEstabPS.MOCN.PLMN0 ( BSC6910 , Number of PS RAB Establishment

BSC6900 )~VS.RAB.AttEstabPS.MOCN.PLMN3 ( Attempts for Operators 0 to 3 in a
VS.RAB.AttEstab.PSR99.MOCN.PLMN0 ( BSC6910 , Number of PS R99 RAB establishment

BSC6900 )~VS.RAB.AttEstab.PSR99.MOCN.PLMN3 ( Attempts for Operators 0 to 3 in a
VS.HSDPA.RAB.SuccEstab.MOCN.PLMN0 ( BSC6910 , Number of Successful HSDPA RAB

BSC6900 )~VS.HSDPA.RAB.SuccEstab.MOCN.PLMN3 Establishments of Operators 0 to 3 for
VS.HSUPA.RAB.SuccEstab.MOCN.PLMN0 ( BSC6910 , Number of Successful HSUPA RAB

BSC6900 )~VS.HSUPA.RAB.SuccEstab.MOCN.PLMN3 Establishments of Operators 0 to 3 for
VS.HSDPA.RAB.AttEstab.MOCN.PLMN0 ( BSC6910 , Number of HSDPA RAB Establishment

BSC6900 )~VS.HSDPA.RAB.AttEstab.MOCN.PLMN3 ( Attempts of Operators 0 to 3 for MOCN
VS.HSUPA.RAB.AttEstab.MOCN.PLMN0 ( BSC6910 , Number of HSUPA RAB Establishment

BSC6900 )~VS.HSUPA.RAB.AttEstab.MOCN.PLMN3 ( Attempts of Operators 0 to 3 for MOCN
VS.RAB.SuccEstabPS.MOCN.PLMN0 ( BSC6910 , Number of Successful PS RAB

BSC6900 )~VS.RAB.SuccEstabPS.MOCN.PLMN3 ( Establishments for Operators 0 to 3 in
BSC6910 , BSC6900 ) a MOCN Cell
VS.RAB.SuccEstab.PSR99.MOCN.PLMN0 ( BSC6910 , Number of PS R99 RAB successfully

BSC6900 )~VS.RAB.SuccEstab.PSR99.MOCN.PLMN3 ( established for Operators 0 to 3 in a
2024-11-25 75
VS.RRC.AttConnEstab.Sum.MOCN.PLMN0 ( BSC6910 Number of Processed RRC Connection

, BSC6900 Requests of Operators 0 to 3 for MOCN
)~VS.RRC.AttConnEstab.Sum.MOCN.PLMN3 ( Cell
BSC6910 , BSC6900 )
VS.RRC.AttConnEstab.CS.MOCN.PLMN0 ( BSC6910 , Number of Processed RRC CSCall

BSC6900 )~VS.RRC.AttConnEstab.CS.MOCN.PLMN3 ( Connection Requests for Operators 0
BSC6910 , BSC6900 ) to 3 in a MOCN Cell
VS.RRC.AttConnEstab.PS.MOCN.PLMN0 ( BSC6910 , Number of Processed RRC PSCall

BSC6900 )~VS.RRC.AttConnEstab.PS.MOCN.PLMN3 ( Connection Requests for Operators 0
BSC6910 , BSC6900 ) to 3 in a MOCN Cell
SET UOPERATORSHARINGMODE: MOCNSupport=YES,

MocnControlSwitch2=USERPLN_PLMN_UPDATE_SWITCH-1; must be executed. Otherwise, traffic-
related counters are incorrectly measured.
14.2 Routing Roaming UEs in Proportion
14.2.1 When to Use Routing Roaming UEs in Proportion

In a MOCN-capable network, you are advised to perform load balancing on a per geographical
area basis. If roaming UEs' load balancing needs to be performed within all RNCs in the shared
network, this feature can be activated.
The restrictions for activating this feature are as follows:
 The network must be a MOCN-capable network, and the shared operators must be the same
for all cells.
 When a roaming UE registers with the MOCN for the first time, the CN needs to send a CS/PS
consistency check request and the UE's IMSI.
 This feature mainly applies to non-supporting UEs.
For roaming UEs that have registered with the shared network before feature activation, if a valid
NRI has been obtained, the RNC directly selects the corresponding operator of the NRI.
Therefore, if a registered roaming UE leaves the MOCN-capable network, the feature takes effect
only when the UE registers with the shared network again. To enable registered UEs to rapidly
select shared operators proportionally, manually delete the registration information of all
roaming UEs on the CN side. This operation, however, will increase the registration time of
roaming UEs.
14.2.2 Requirements
This feature requires that roaming relationships between the operators and the roaming capacity
ratio be configured at the shared RNC.
The roaming capacity ratio indicates the proportion of roaming UEs to be routed to different
operators' CN nodes.
14.2.3 Deployment
2024-11-25 76
Activation (Using MML Commands)
Assume that operator 1 and operator 2 share the same RNC by using the MOCN and operator A
signs a roaming agreement with the two operators.
1. To add operator A to the roaming relationship list of operator 1, run the RNC MML
command ADD UROAMMAP. In this step, set MCC for operator A to 460, MNC to 09, Cn
Operator Index for operator 1 to 1, Cn Operator Group Index for operator 1 to 1, and
Capability of Roaming Operator to an appropriate value according to the network plan,
such as 30.
2. To add operator A to the roaming relationship list of operator 2, run the RNC MML
command ADD UROAMMAP. In this step, set Cn Operator Index for operator 2 to 2, Cn
Operator Group Index to 1, and Capability of Roaming Operator to an appropriate
value according to the network plan, such as 70.
 After the parameter settings are complete, the UEs that belong to operator A are distributed to
operator 1 and operator 2 according to the preset ratio (30:70).
 If operator B also signs a roaming agreement with operator 1 and operator 2, the roaming UE
distribution ratio for operator B must be set to the same as that for operator A when operator B
is added to the roaming relationship lists of the two operators.
MML Command Examples
/*Activating the Routing Roaming UEs in Proportion feature*/

//Adding operator A serving roaming UEs to the roaming relationship list of operator 1
ADD UROAMMAP: MCC="460", MNC="09", CnOpIndex=1, CnOpGrpIndex = 1,AvailRoamCap =30;
//Adding operator A serving roaming UEs to the roaming relationship list of operator 2
ADD UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex = 1,AvailRoamCap =70;
/*Deactivating the Routing Roaming UEs in Proportion feature*/
//Removing operator A serving roaming UEs from the roaming relationship list of operator 1
RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=1, CnOpGrpIndex = 1;
//Removing operator A serving roaming UEs from the roaming relationship list of operator 2
RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex = 1;
Activation (Using the MAE-Deployment)
Activation Observation
1. Run the RNC MML command LST UROAMMAP to query the roaming capacity of operator
A. Expected result: Capability of Roaming Operator for operator 1 is set to 30, and
Capability of Roaming Operator for operator 2 is set to 70.
2024-11-25 77
2. When UEs belonging to operator A roam to the RNC shared through MOCN by operator 1
and operator 2 for a long measurement period, view the performance counter
VS.Roam.Cnoperator.MOCN.Num ( BSC6910 , BSC6900 ).
Expected result: The roaming UEs of operator A that are routed to CN nodes of operator 1
and those that are routed to CN nodes of operator 2 are in a preset ratio of 30:70.
 UEs of the non-supporting UE type do not support network sharing, as defined in the feature
WRFD-02131101 Carrier Sharing by Operators.
 This feature is not applicable to UEs of the supporting UE type (supporting network sharing).
Deactivation (Using MML Commands)
1. Run the RNC MML command RMV UROAMMAP to remove operator A from the roaming
relationship list of operator 1.
2. Run the RNC MML command RMV UROAMMAP to remove operator A from the roaming
relationship list of operator 2.
Deactivation (Using the MAE-Deployment)

The performance counter VS.Roam.Cnoperator.MOCN.Num ( BSC6910 , BSC6900 )
indicates the number of times that roaming UEs successfully register with local operators' MOCN
for the first time. Use the value of the VS.Roam.Cnoperator.MOCN.Num ( BSC6910 ,
BSC6900 ) counter to calculate the ratio of the number of roaming UEs among operators. The
calculated ratio must be the same as the configured one.
After this function is enabled for a short period, this counter cannot indicate the proportion of roaming UEs
among operators because UEs are not evenly distributed in the network. This counter indicates the
proportion of roaming UEs among operators when the feature is enabled for a long period and a large
number of roaming UEs move to the MOCN.
The local operators have signed roaming agreements with the home operators of these UEs. Under either of
the following conditions, the UE registration with the MOCN is regarded as a first-time registration:
 The UE ID in an RRC connection setup request is an IMSI and the IMSI prefix is not the PLMN of any
local operator.
 The UE ID used in an RRC connection setup request is an IMSI or PTMSI. The CN rejects the RRC
connection setup request and requires the UE to perform a CS/PS consistency check and the UE IMSI is
contained in the message sent by the CN.
14.3 MOCN Cell Resource Demarcation
14.3.1 When to Use
2024-11-25 78
 It is recommended that this feature be used if operators in a shared MOCN cell request
proportional demarcation of the shared cell resources. If a cell is independently owned by
one operator, it is recommended that this feature not be used in this cell. Otherwise, UEs of
this operator cannot preempt resources from each other in this cell.
 It is recommended that this feature not be enabled in scenarios where downlink power
congestion occurs. Otherwise, downlink power congestion will increase.

The information to be collected before enabling this feature is as follows:
 The cell that has been configured as a shared MOCN cell
 The percentage of available resources for each operator. The available resources include DL
R99 SCs, HSDPA power resources, and total DL power resources.
The percentages are determined based on each operator's investment ratio and traffic model.
14.3.3 Deployment
This section describes how to activate, verify, and deactivate the optional feature WRFD-140223
MOCN Cell Resource Demarcation.
Requirements
 Hardware
Only the macro base stations configured with the WBBPb, WBBPd, WBBPf, or UBBP board
support the function of allocating HSDPA power resources to each operator. Only the UBBP
board supports the function of allocating total downlink power resources to each operator.
This feature depends on the UBBP board. Therefore, before deploying this feature in a cell,
configure this cell with a downlink resource group that is formed only by UBBP boards.
Otherwise, this feature cannot take effect if the cell is reestablished on other baseband
processing units. For the method of adding cells and baseband processing units into a
downlink resource group, see CE Resource Management Feature Parameter Description .
 Other features
 The WRFD-021311 MOCN Introduction Package feature must be configured before this
feature is activated.
 The WRFD-010610 HSDPA Introduction Package feature must be configured if the

function of allocating HSDPA power and total downlink power resources for MOCN-
enabled operators in a cell is to be activated.
 When deploying the function of allocating total downlink power resources or the function
of allocating R99 code resources, you are advised to also deploy the WRFD-020106 Load
2024-11-25 79
Reshuffling feature to enable power- or code-based LDR and configure related

congestion relief actions.
 License
Description .
Table 14-2 BSC6900 and BSC6910
Feature ID Feature Name License Control NE Sales
Item ID Unit
WRFD- MOCN Cell Resource LQW1MOCNCDEM01 BSC6900/ per Cell

140223 Demarcation BSC6910
The license control item in the DSP LICUSAGE command output is MOCN Cell Resource
Demarcation (per cell).
In the RAN Sharing/MOCN scenario, the primary and secondary operators do not support
license allocation by operator.
 Using cell resources based on the HSDPA power percentages for MOCN-enabled operators in
a cell
Configuration on the RNC side:
1. Run the RNC MML command SET URRCTRLSWITCH. In this step, select
PSCRR_OpIndex_INCLUDED under Iub Private Interface Switch to include
operator indexes in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST
message.
RL_OpIndex_INCLUDED under Iub Private Interface Switch to include operator
indexes in the RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and
RADIO LINK RECONFIGURATION PREPARE messages.
3. Run the RNC MML command MOD UCELLALGOSWITCH. In this step, select
HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm) under Cell CAC algorithm
switch to enable the HSDPA GBP test.
4. (Optional) If there is an Iur interface between the serving RNC and its neighboring RNC,
run the RNC MML command MOD UNRNC. In this step, select PLMNID_INCLUDED
under Iur Private Interface Switch to include the PLMN ID in the proprietary IE of Iur
messages.
5. Run the RNC MML command MOD UCELLCAC. In this step, set Non-HSPA Power
Threshold for GBP-based Preemption according to the network plan.
6. Run the RNC MML command ADD UCELLMOCNDPAPOWERDEMAR. In this step, set
Cell ID, Cn Operator Index, and HSDPA Power Availability Percentage to
configure the HSDPA power percentage for an operator of an operator group in a cell.
2024-11-25 80
MOCN_DEMARC_PREEMPT_GBP under Demarcation Preemption Switch to
enable preemption based on HSDPA power percentages of operators in a cell.
CELL_MOCN_DL_HSDPAPWR_DEMARC_SWITCH under MOCN Cell Resource
Demarcation Switch to enable the function of allocating HSDPA power resources to
operators sharing an MOCN cell.
9. Run the RNC MML command ADD UCELLLICENSE or MOD UCELLLICENSE. In this
step, select CELL_MOCN_DEMARCATION_SWITCH(Cell MOCN Demarcation
Switch) under Function Switch1 to activate the license for MOCN Cell Resource
Demarcation for operators in a cell.
Configuration on the NodeB side:
1. Run the NodeB MML command SET ULOCELLMACHSPARA. In this step, set
Resource Allocate Method to POWERCODE_BAL(Balance between Code and
Power).
 Using cell resources based on the R99 SF percentages for MOCN-enabled operators in a cell
1. Run the RNC MML command ADD UCELLMOCNSFDEMAR. In this step, set Cell ID,
Cn Operator Index, and DL R99 SC Availability Percentage.
messages.
MOCN_DEMARC_PREEMPT_SF under Demarcation Preemption Switch to enable
preemption based on R99 SF percentages of operators in a cell.
NBM_SF_LDC_DEMARC(Select UEs of Operator R99 SC Exceeding Largest
Amount) under R99 SC LDR User Selection to enable the cell-level congestion
control function based on R99 SF percentages. By doing so, the UEs of the operator
whose actual R99 SF percentage has exceeded the predefined value can be
preempted.
5. Run the RNC MML command SET UOPERATORSHARINGMODE. In this step, set Intra
RAT Inter Plmn Ho Allowed to NO, set Inter RAT Inter Plmn Ho Allowed to NO
and Inter-PLMN Multicarrier HSDPA Switch to NO(NO).
CELL_MOCN_DL_SF_DEMARC_SWITCH under MOCN Cell Resource Demarcation
Switch to enable the function of allocating SF code resources to operators sharing an
MOCN cell.
2024-11-25 81
7. Run the RNC MML command ADD UCELLLICENSE to activate the license for MOCN
Cell Resource Demarcation for operators in a cell. In this step, select
CELL_MOCN_DEMARCATION_SWITCH(Cell MOCN Demarcation Switch) under
FuncSwitch1 ( BSC6910 , BSC6900 ).
 Enabling allocation of downlink power resources for MOCN-enabled operators in a cell

Configuration on the RNC side:
PSCRR_OpIndex_INCLUDED under Iub Private Interface Switch to include
operator indexes in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST
message.
RL_OpIndex_INCLUDED under Iub Private Interface Switch to include operator
indexes in the RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and
RADIO LINK RECONFIGURATION PREPARE messages.
HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm) under Cell CAC algorithm
switch to enable the HSDPA GBP test.
messages.
5. Run the RNC MML command ADD UCELLMOCNPWRDEMAR. In this step, specify the
Cell ID, CN Operator index, and DownLink Power Percentage parameters to
configure the percentage of R99+HSDPA power resources available to each operator.
MOCN_DEMARC_PREEMPT_GBP under Demarcation Preemption Switch to
enable preemption based on power percentages of operators in a cell.
7. (Optional) Run the RNC MML command MOD UCELLALGOSWITCH. In this step, select
DL_PWR_LDC_DEMARC under DL Power-based LDR UE Selection Switch to enable the
function of performing LDR preferentially on users of the operator whose power usage
exceeds its specified percentage.
CELL_MOCN_DL_TOTALPWR_DEMARC_SWITCH under MOCN Cell Resource
Demarcation Switch to activate the MOCN Cell Resource Demarcation feature.
9. Run the RNC MML command ADD UCELLLICENSE. In this step, select
CELL_MOCN_DEMARCATION_SWITCH under Function Switch1 to activate the
license for the MOCN Cell Resource Demarcation feature.
Configuration on the NodeB side:
2024-11-25 82
1. Run the NodeB MML command SET ULOCELLMACHSPARA. In this step, set
Resource Allocate Method to POWERCODE_BAL(Balance between Code and
Power).
When the cell's operator group changes, perform 5 to reconfigure the resource allocation percentage
of each operator. Otherwise, this feature becomes ineffective.
 Using cell resources based on the HSDPA power percentages for MOCN-enabled operators in
a cell
1. Start the Iub-interface message tracing task. Check whether the

NBAP_PHY_SHARED_CH_RECFG_REQ message carries the MOCN-Operator-Hsdpa-Operator-
Index-private IE and the MOCN-Operator-Hsdpa-Pwr-Ratio-private IE. If yes, the feature
based on the HSDPA power percentage has been activated.
2. Observe the following counters of operators: If any value of these counters is not 0, the
feature based on the HSDPA power percentage has been activated.
 VS.HSDPAPwrRatio.SharedOperator0
 Using cell resources based on the R99 SF percentages for MOCN-enabled operators in a cell
 Enabling allocation of downlink power resources for MOCN-enabled operators in a cell

Run the RNC MML command DSP UCELLCHK. In the output information, check the fields
Total power demarcation function of local cell and Whether total power
demarcation function of cell is configured and active.
 Deactivating the MOCN Cell Resource Demarcation feature
Run the RNC MML command ADD UCELLLICENSE. In this step, deselect
CELL_MOCN_DEMARCATION_SWITCH(Cell MOCN Demarcation Switch) under
FuncSwitch1 ( BSC6910 , BSC6900 ) to deactivate the license for MOCN Cell Resource
Demarcation for operators in a cell.
2024-11-25 83
 Run the RNC MML command MOD UCELLALGOSWITCH.

In this step, deselect the following switches under the MOCN Cell Resource Demarcation
Switch in the RNC MML MOD UCELLALGOSWITCH:
 Deselect the CELL_MOCN_DL_TOTALPWR_DEMARC_SWITCH check box to deactivate

the MOCN Cell Resource Demarcation feature.
 Deselect the CELL_MOCN_DL_SF_DEMARC_SWITCH check box to deactivate the

function of allocating SF code resources to MOCN-enabled operators in a cell.
 Deselect the CELL_MOCN_DL_HSDPAPWR_DEMARC_SWITCH check box to

deactivate the function of allocating HSDPA power resources to MOCN-enabled operators
in a cell.
//Activating MOCN Cell Resource Demarcation

//Using cell resources based on the HSDPA power resource percentages for MOCN-enabled operators in a cell
//Configuration on the RNC side
SET URRCTRLSWITCH: IubPrivateInterfaceSwitch=PSCRR_OpIndex_INCLUDED-1;
SET URRCTRLSWITCH: IubPrivateInterfaceSwitch=RL_OpIndex_INCLUDED-1;
MOD UCELLALGOSWITCH: CellId=0, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1;
MOD UNRNC: NRncId=1, IurPrivateInterfaceSwitch=PLMNID_INCLUDED-1;
MOD UCELLCAC: CellId=0, NonHPwrForGBPPreemp=40;
ADD UCELLMOCNDPAPOWERDEMAR: CellId=0, CnOpIndex=0, DPAAvaiPwrRatio=50;
ADD UCELLMOCNDPAPOWERDEMAR: CellId=0, CnOpIndex=1, DPAAvaiPwrRatio=50;
MOD UCELLALGOSWITCH: CellId=0, DemarcPreemptSwitch=MOCN_DEMARC_PREEMPT_GBP-1;
MOD UCELLALGOSWITCH:CellId=0,CellMocnDemarcSwitch= CELL_MOCN_DL_HSDPAPWR_DEMARC_SWITCH-1;
ADD UCELLLICENSE: CellId=0, FuncSwitch1=CELL_MOCN_DEMARCATION_SWITCH-1;
//Configuration on the NodeB side
SET ULOCELLMACHSPARA: ULOCELLID=0, RSCALLOCM=POWERCODE_BAL;
//Using cell resources based on the R99 SF percentages for MOCN-enabled operators in a cell
ADD UCELLMOCNSFDEMAR: CellId=1, CnOpIndex=0, DLAvaiSFRatio=10;
MOD UCELLALGOSWITCH: CellId=1, DemarcPreemptSwitch=MOCN_DEMARC_PREEMPT_SF-1;
MOD UCELLALGOSWITCH: CellId=1, NbmSFLdcUeSelSwitch=NBM_SF_LDC_DEMARC;

SET UOPERATORSHARINGMODE: InterPlmnHoAllowedIntraRat=NO, InterPlmnMultiCarrSwitch=NO;
MOD UCELLALGOSWITCH:CellId=1,CellMocnDemarcSwitch= CELL_MOCN_DL_SF_DEMARC_SWITCH-1;
//Using cell resources based on the downlink power resource percentages for MOCN-enabled operators in a cell
2024-11-25 84
//Setting parameters on the RNC side

MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1;
ADD UCELLMOCNPWRDEMAR: CellId=1, CnOpIndex=0, DLPwrRatio=50;
ADD UCELLMOCNPWRDEMAR: CellId=1, CnOpIndex=1, DLPwrRatio=50;
MOD UCELLALGOSWITCH: CellId=1, DemarcPreemptSwitch=MOCN_DEMARC_PREEMPT_GBP-1;
MOD UCELLALGOSWITCH: CellId=1, DlPWRLdcUeSelSwitch= DL_PWR_LDC_DEMARC;

MOD UCELLALGOSWITCH: CellId=1,CellMocnDemarcSwitch= CELL_MOCN_DL_TOTALPWR_DEMARC_SWITCH-1;
//Configuration on the NodeB side
SET ULOCELLMACHSPARA: ULOCELLID=0, RSCALLOCM=POWERCODE_BAL;
//Deactivating MOCN Cell Resource Demarcation
MOD UCELLLICENSE: CellId=1,FuncSwitch1=CELL_MOCN_DEMARCATION_SWITCH-0;
MOD UCELLALGOSWITCH:CellId=1,CellMocnDemarcSwitch= CELL_MOCN_DL_TOTALPWR_DEMARC_SWITCH-0;
MOD UCELLALGOSWITCH:CellId=1,CellMocnDemarcSwitch= CELL_MOCN_DL_SF_DEMARC_SWITCH-0;
MOD UCELLALGOSWITCH:CellId=1,CellMocnDemarcSwitch= CELL_MOCN_DL_HSDPAPWR_DEMARC_SWITCH-0;

Use the following counters to monitor the R99 SCs and HSDPA power resources occupied by each
operator:
 VS.RAB.SFOccupy.MAX.SharedOperator0 ( BSC6910 , BSC6900 )
 VS.RAB.SFOccupy.SharedOperator0 ( BSC6910 , BSC6900 )
 VS.DLDCHPwrRatio.SharedOperator0
2024-11-25 85
Observe whether the calculation result of ( VS.DLDCHPwrRatio.SharedOperator0 +

VS.HSDPAPwrRatio.SharedOperator0 )/( VS.DLDCHPwrRatio.SharedOperator1 +
VS.HSDPAPwrRatio.SharedOperator1 ) approximates to operator 0's DLPwrRatio (
BSC6910 , BSC6900 ) divided by operator 1's DLPwrRatio ( BSC6910 , BSC6900 ).
The sum of the percentage of downlink power resources for each operator cannot reach 100% because the
common channel power cannot be differentiated on a per operator basis and the NodeB allocates a power
margin for R99 channels. The power margin is specified by the PWRMGN parameter in the NodeB MML
command SET ULOCELLMACHSPARA.
When the total power resources are congested, that is, the sum of the percentage of HSPA power resources
for each operator is close to the value of (1 – Non-HSPA TCP power load of the cell – R99 power margin),
this feature ensures that the relative rate of downlink power resources occupied by each operator is close
to the value of DLPwrRatio ( BSC6910 , BSC6900 ).
where,
Non-HSPA TCP power load of the cell = 10^[(VS.MeanTCP.NonHS ( BSC6910 , BSC6900 ) -
MaxTxPower ( BSC6910 , BSC6900 )/10)/10] x 100%
Or,
Non-HSPA TCP power load of the cell = VS.TCP.NonHS.Usage.Mean ( BSC6910 , BSC6900 )
Use the following counters to measure the proportions of TTIs in which UEs in the scheduling
candidate set are not scheduled for each operator in an MOCN network to thereby evaluate the
impact of the feature on resource scheduling of each operator:
 VS.HSDPA.ScheduleLimit.TTINum.SharedOperator0 /
VS.HSDPA.Data.TTINum.SharedOperator0
Use the following counters to measure the number of successful fallbacks from HS-DSCH to DCH
for operators in a MOCN cell after HS-DSCH admission fails due to resource insufficiency to
thereby evaluate the impact of MOCN cell resource demarcation on UE admission in a MOCN cell.
 VS.RAC.H2D.Succ.SharedOperator0 ( BSC6910 , BSC6900 )
2024-11-25 86
Observe how the following key performance indicators (KPIs) fluctuate before and after this
feature is deployed:
 RRC setup success rate
 CS RAB setup success rate
 PS RAB setup success rate
The number of RRC connection releases caused by preemption in the RNC and the number of
abnormal RAB releases for an operator in the RNC measured before and after the feature
activation show how the previous KPIs fluctuate and what actions are required.
 If either of the numbers increases significantly, an operator serves a large number of UEs
whereas a predefined percentage for this operator is less than required. The predefined
percentages for operators in the same cell need to be adjusted.
 To adjust the percentage of DL R99 SCs available for an operator, set DLAvaiSFRatio (
BSC6910 , BSC6900 ) by running the MOD UCELLMOCNSFDEMAR command.
 To adjust the percentage of HSDPA power resources available for an operator, set
DPAAvaiPwrRatio ( BSC6910 , BSC6900 ) by running the MOD
UCELLMOCNDPAPOWERDEMAR command.
 To adjust the percentage of total downlink power resources available for an operator, set
DLPwrRatio ( BSC6910 , BSC6900 ) by running the MOD UCELLMOCNPWRDEMAR
command.
 If the numbers indicate that each operator in a shared MOCN cell serves a large number of
UEs, cell resources are insufficient and capacity expansion is required.
Because the predefined percentages of DL R99 SCs and HSDPA power resources are determined based on
each operator's investment ratio and traffic model, operators need to negotiate with each other when
adjusting the percentages.
N/A
14.4 MOCN Independent CE Resource Allocation
14.4.1 When to Use MOCN Independent CE Resource Allocation

Use this feature when the customer requires independent CE resource allocation on MOCN-
enabled networks.
Before you deploy the feature, collect traffic statistics about CN operators to ensure that the CE
resources are properly allocated. In addition, note the following points for feature deployment:
 If operators prioritize CE resource independence, CE resources can be allocated to private

groups only. In this scenario, CE resource utilization decreases.
2024-11-25 87
 If both resource independence and resource utilization need to be balanced, allocate more
CE resources to the common group. The more CE resources the common group has, the
higher the resource utilization, but the lower the resource independence.

Before you deploy MOCN Independent CE Resource Allocation, collect the following information:
 Traffic statistics about all CN operators in the MOCN configuration
 CE allocation information
When the MOCN Independent CE Resource Allocation feature is used along with the WRFD-151210 Inter-
Dependence of BBU Uplink Resource feature, the configured uplink CE capacity must be less than or equal
to the total uplink CE capacity of baseband processing units where cells are set up to maximize the use of
licensed uplink CEs. You can run the DSP ULOCELLRES command to query cell deployment on a baseband
processing unit. Based on the number of uplink CEs supported by each baseband processing unit, you can
find out the total uplink CE capacity of baseband processing units where cells are set up.
14.4.3 Deployment
Requirements
 Other features
Before you activate this feature, the WRFD-021311 MOCN Introduction Package feature must
be configured and the inter-operator handover switch InterPlmnHoAllowedIntraRat (
BSC6910 , BSC6900 ) must be turned off.
 Hardware
The 3900 series macro base stations need to be configured with the UBBP, WBBPb, WBBPd,
or WBBPf board.
5900 series macro base stations must be configured with the UBBP board.
 Customer resources
Allocated CE resources must satisfy operators' traffic requirements.
 License
Description .
Feature Feature Name License Control License Control Item NE Sales
ID Item ID Name Unit
WRFD- MOCN Independent CE LQW9MOCN01 MOCN CE resource Node per

150214 Resource Allocation independent allocate(per B Cell
Cell)
The license control item on the OSS GUI is MOCN CE resource independent allocate
(per Cell).
2024-11-25 88
If RAN Sharing or MOCN is enabled, the licensed resource is allocated among the primary
and secondary operators according to the following method:
Method 1: Some license control items, for example, Dynamic CE Function (per NodeB), can
be allocated only through the common group. For NodeB license allocation in multi-operator
scenarios, see License Management Feature Parameter Description .
Data Preparation
Parameter Parameter ID Setting Notes Data Source

Name
Iub Private IubPrivateInterfaceSw Select RL_OpIndex_INCLUDED and Network plan

Interface Switch itch ( BSC6910 , PSCRR_OpIndex_INCLUDED under
BSC6900 ) the Iub Private Interface Switch
parameter.
Iur Private IurPrivateInterfaceSwi Select the PLMNID_INCLUDED under Network plan

Interface Switch tch ( BSC6910 , the Iur Private Interface Switch
BSC6900 ) parameter if NodeBs managed by the
neighboring RNC support this feature.
Amount of Not applicable on the Configured according to the Network plan

allocated CE MAE customer's plan (negotiation
resource among required)
operators
(private and
common groups)
 Turning on the switch for carrying the operator's index (on the RNC side):
1. Run the RNC MML command SET URRCTRLSWITCH, and select RL_OpIndex_INCLUDED
and PSCRR_OpIndex_INCLUDED under the Iub Private Interface Switch parameter, to
enable operator information transmission over the Iub interface.
2. (Optional) If NodeBs managed by the neighboring RNC support this feature, run the RNC
MML command ADD UNRNC and select PLMNID_INCLUDED under the Iur Private
Interface Switch parameter, to enable the serving RNC to send operator information to
the DRNC over the Iur interface.
 Allocating CE licenses (on the MAE side):
1. Choose License > NE License Management > NodeB License Management. The
NodeB License Management window is displayed.
2. From the navigation tree in the left pane, select an RNC node whose NodeB license file has
been uploaded to the NMS server.
3. Right-click a license and choose License Distributed to Operator from the shortcut
menu.
2024-11-25 89
4. The License Distributed to Operator window is displayed. Set available functions and
resources for each operator, and then click OK.
5. In the lower part of the license information area, click the tab of an operator. The license
allocation information about all the NodeBs related to the operator is listed.
6. Double-click a NodeB to which you want to allocate the license, or right-click the NodeB
and choose Modify from the shortcut menu. Then, set MOCN CE resource independent
allocate to the number of cells enabled with this feature under the NodeB to enable CE
resource allocation.
The following procedure applies only to MOCN scenarios. If you need to deploy this feature in RAN
sharing scenarios, change the network structure to MOCN in advance.
When this feature is enabled, the operator's private group CE must be assigned with an actual value.
If it is set to Not set, the users served by this operator cannot access the network.
To verify whether the feature is activated, perform the following operations:
1. Run the NodeB MML command DSP License to query information about CEs allocated to
operators and the common group. If the queried information is the same as configuration,
the feature has been activated.
2. After the network has been running for a period of time, compare the values of the
following counters on the RNC and NodeB with the allocated CE License. If neither the
actually consumed CEs nor the admitted CEs do not exceed the allocated CEs (private and
common groups), this feature works properly.
Counters that reflect CEs consumed by each operator on the NodeB side
VS.LC.ULCreditUsed.Mean.Shared Average number of uplink CEs consumed by each operator

Operator in an MOCN network NodeB
VS.LC.DLCreditUsed.Mean.Shared Average number of downlink CEs consumed by each

Operator operator in an MOCN network NodeB
 After activating the license of this feature, run the RNC MML command SET URRCTRLSWITCH to
select the RL_OpIndex_INCLUDED check box under the Iub Private Interface Switch parameter
and allocate private group CEs to operators. These counters can be measured on a per operator basis
only in the preceding scenario.
2024-11-25 90
 If the license of this feature is not activated, RL_OpIndex_INCLUDED also needs to be selected to
observe these counters. Otherwise, the counter values are 0.
 If the license of this feature is activated and RL_OpIndex_INCLUDED is not selected, the NodeB
cannot allocate CE resources on a per operator basis and the feature does not take effect.
 If the license of this feature is activated, if RL_OpIndex_INCLUDED is selected, and if the operator's
private group CE is set to Not set, the services of this operator fail.
The table lists counters that reflect CE admission on the RNC side.
VS.NodeB.ULCreditUsed.Mean.PLMN ( Average NodeB Credit Consumption of an Operator in

BSC6910 , BSC6900 ) the Uplink
VS.NodeB.ULCreditUsed.Max.PLMN ( Maximum NodeB Credit Consumption of an Operator

BSC6910 , BSC6900 ) in the Uplink
VS.NodeB.DLCreditUsed.Mean.PLMN ( Average NodeB Credit Consumption of an Operator in

BSC6910 , BSC6900 ) the Downlink
VS.NodeB.DLCreditUsed.Max.PLMN ( Maximum NodeB Credit Consumption of an Operator

BSC6910 , BSC6900 ) in the Downlink
VS.NodeB.LDR.UL.BERateDown.PLMN ( Number of UEs With Decreased BE Service Rate in the

BSC6910 , BSC6900 ) Case of UL Credit Resource Congestion for Operator
1. Deactivate the license on the MAE.

Double-click the target NodeB (or right-click it and choose Modify from the shortcut
menu), and set MOCN CE resource independent allocate to 0 in the displayed Modify
dialog box.
You cannot use the SET ULOCELLMACHSPARA command on the MAE-Deployment to

deactivate the MOCN Independent CE Resource Allocation feature.
//Activation procedure
//Turning on the switch for carrying the operator's index on the RNC side
ADD UNRNC: NRncId=1, SHOTRIG=NON_HSPA_SHO_SWITCH-1, IurPrivateInterfaceSwitch=PLMNID_INCLUDED-
1,HHOTRIG=ON;
//Allocating CE licenses to operators and allocating CEs to private groups and the common group on the MAE
//Deactivating MOCN Independent CE Resource Allocation
//Setting the value of the NodeB's MOCN CE resource independent allocate to 0 on the MAE
2024-11-25 91
Use the following counters to monitor the usage of CE resources occupied by each operator:
 VS.NodeB.ULCreditUsed.Mean.PLMN ( BSC6910 , BSC6900 )
 VS.NodeB.ULCreditUsed.Max.PLMN ( BSC6910 , BSC6900 )
 VS.NodeB.DLCreditUsed.Mean.PLMN ( BSC6910 , BSC6900 )
 VS.NodeB.DLCreditUsed.Max.PLMN ( BSC6910 , BSC6900 )
 VS.NodeB.LDR.UL.BERateDown.PLMN ( BSC6910 , BSC6900 )

Detailed CE resource allocations are customer-specific. Adjust them only when customer
requirements change.
The license delivered to the NodeB carries the operator's frequency information. Therefore, after
the MOCN Independent CE Resource Allocation function is enabled, the license must be re-
delivered if cell frequencies are modified on the RNC to ensure that the frequencies in the license
are consistent with the configured frequencies.
If the CE resources used by an operator exceed the alarm generation threshold OTHD , ALM-
26812 System Dynamic Traffic Exceeding Licensed Limit will be reported.
Alarm Alarm Name NE Feature Feature Name
ID ID
ALM- ALM-26812 System Dynamic Traffic Node WRFD- MOCN Independent CE

26812 Exceeding Licensed Limit B 150214 Resource Allocation
When MOCN is enabled, the NodeB supports allocating CE licenses based on operators. The operator index
is valid only in the following CE license-related alarms:
 ALM-26811 Configured Capacity Limit Exceeding Licensed Limit

 ALM-26812 System Dynamic Traffic Exceeding Licensed Limit
14.5 MOCN Independent Iub Transmission Resource Allocation
14.5.1 When to Use MOCN Independent Iub Transmission Resource

Allocation
Use this feature when the customer requires independent Iub bandwidth allocation on MOCN-
enabled networks.
Before you deploy the feature, collect traffic statistics about CN operators to ensure that the Iub
interface is allocated sufficient bandwidth.
If operators prioritize Iub resource independence, the feature applies. To achieve bandwidth
independence between operators, the total bandwidth allocated to logical ports cannot exceed
the total bandwidth of physical ports.
To ensure that the bandwidth is allocated to operators according to the predefined percentages
at busy hours and that the bandwidth is allocated based on the operators' needs, it is
2024-11-25 92
recommended that dynamic independent Iub transmission mode introduced in RAN16.0 be

deployed.
If RSCMNGMODE ( BSC6910 , BSC6900 ) is set to EXCLUSIVE, MOCNSupport ( BSC6910 , BSC6900

) must be set to YES and the licenses for both the MOCN Introduction Package feature and the MOCN
Independent Iub Transmission Resource Allocation feature must be activated. Otherwise, the transport
resource admission will fail and services cannot be set up.

Before you deploy MOCN Independent Iub Transmission Resource Allocation, collect the following
information:
 Bandwidth allocated to the logical port of each operator
 Operator that provides the bandwidth for common channels of a shared cell
14.5.3 Deployment
Requirements
 Other features
Before you activate this feature, the WRFD-021311 MOCN Introduction Package feature must
If this feature needs to be deployed on a GU multimode base station controller where the Iub
and Abis interfaces share a physical port, ensure that the GBFD-118704 Abis Independent
Transmission feature has been disabled.
Before you activate static independent Iub transmission mode, deactivate the following
features:
 WRFD-140208 Iub Transmission Resource Pool in RNC
 WRFD-150243 Iub IP Transmission Based on Dynamic Load Balancing
 WRFD-021304 RAN Sharing Introduction Package
 WRFD-021305 RAN Sharing Phase 2
Before you activate dynamic independent Iub transmission mode, deactivate the following
features and feature:
 WRFD-021304 RAN Sharing Introduction Package
 WRFD-021305 RAN Sharing Phase 2
 User-plane load sharing function in the WRFD-150211 RNC in Pool Load Sharing feature
 Transmission
Static independent Iub transmission mode does not apply to transmission resource pool or
BSC6910 IP transmission scenarios.
2024-11-25 93
Dynamic independent Iub transmission mode does not apply to ATM transmission or
BSC6900 IP address pool scenarios. This mode does not apply to single-core interface
processing boards, including the FG2a, GOUa, PEUa, and POUa boards.
A Hub logical port cannot be configured with a redundant leaf logical port (which does not
belong to any operator). Otherwise, the percentages of bandwidth allocated to the logical
ports of other operators are affected.
The remaining bandwidth of the Hub logical port cannot be configured to 0. Otherwise, the
Hub logical port cannot trigger congestion control and the percentages of bandwidth
allocated to operators cannot be ensured during busy hours.
During data transmission over the Iub interface, operator information is transparent to the NodeB.
Specifically, the NodeB sends data packets by preconfigured IP addresses, not by operators. Therefore,
the NodeB can send all packets to one specific IP address or send them to different IP addresses.
This feature is mainly configured on the RNC, and it has no requirements on the NodeB.
 Customer resources
Allocated Iub bandwidth must satisfy operators' traffic requirements.
 License
Description .
Feature Feature Name License License Control Item NE Sales
ID Control Item ID Name Unit
WRFD- MOCN Independent Iub LQW1MIITRARES MOCN Independent Iub BSC690 per
150213 Transmission Resource Transmission Resource 0 NodeB
Allocation Allocation (per NodeB) BSC691
0
In the RAN Sharing/MOCN scenario, the primary and secondary operators do not support license
allocation by operator.
The WRFD-021305 RAN Sharing Phase 2 feature includes the WRFD-02130501 Dedicated Iub Transmission
Control feature. To avoid mutual impact between features, verify that the RAN Sharing Function and RAN
Sharing Enhanced Package licenses are deactivated before you activate the MOCN feature.
Data Preparation
Parameter Name Parameter ID Setting Notes Data

Source
Resource RscMngMode ( Set this parameter to EXCLUSIVE. Network

Management Mode BSC6910 , plan
BSC6900 )
Common Channel CchCnOpIndex ( The default value 255 indicates that the Network
Bandwidth Operator BSC6910 , primary operator provides bandwidth. plan
2024-11-25 94
Parameter Name Parameter ID Setting Notes Data

Source
Index BSC6900 )
Function Switch1 FuncSwitch1 ( Select MOCN_INDEPENDENT_IUB_TRANS. Network

BSC6910 , plan
BSC6900 )
Bandwidth [64kbps] CIR ( BSC6910 , Set this parameter as required in IP Network

BSC6900 ) transmission mode. plan
Forward bandwidth TXBW ( BSC6910 Set this parameter as required in ATM Network
[kbps] , BSC6900 ) transmission mode. plan
Peer IP address PEERIPADDR Set this parameter to the value specific to Network
the operator. plan
Bearing VPI VPI ( BSC6910 , Set this parameter to the value specific to Network
BSC6900 ) the operator. plan
Activating Static Independent Iub Transmission Mode on a

Newly Deployed BSC6900 (Using MML Commands)
1. Run the RNC MML command ADD UNODEBLICENSE with

MOCN_INDEPENDENT_IUB_TRANS(MOCN Independent Iub Resource Allocation
License) selected under the Function Switch1 parameter to turn on the feature switch
on the RNC.
2. Configure dedicated logical port bandwidth, path bandwidth, and IP address for each
operator to enable operators to manage their own transmission resources independently.
a. Run the RNC MML command ADD UNODEB with Resource Management Mode set
to EXCLUSIVE.
b. Configure dedicated logical port bandwidth for each operator.
 (In IP transmission mode) Run the RNC MML command ADD IPLOGICPORT to
configure the logical port bandwidth for each operator. In this step, set the
Resource management mode parameter to EXCLUSIVE, and set CN
operator index and Bandwidth [64kbps]. In addition, set the Dynamic
Bandwidth Sharing Switch parameter to OFF(OFF).
 (In ATM transmission mode) Run the RNC MML command ADD ATMLOGICPORT
to configure a dedicated logical ATM port for each operator. In this step, set the
Resource management mode parameter to EXCLUSIVE, and set CN
operator index and Forward bandwidth [kbps].
c. Add a path over the dedicated logical port of each operator.
 (In IP transmission mode) Run the RNC MML command ADD IPPATH. In this step,
set Peer IP address and set Carry Flag to IPLGCPORT(IP Logic Port).
2024-11-25 95
 (In ATM transmission mode) Run the RNC MML command ADD AAL2PATH. In
this step, set Bearing VPI and set Bearing type to ATMLOGICPORT(ATM
Logical Port).
d. (Optional) Run the RNC MML command ADD UCELLSETUP with Common Channel
Bandwidth Operator Index set to the index of an operator. The default value 255
indicates that the primary operator provides bandwidth for common channels of a
shared cell. If there is no primary operator, the first operator listed in the operator
group provides bandwidth.
3. (Optional) Configure a dedicated VLAN for each operator.
 On the RNC side:

Run the RNC MML command ADD DEVIP with IP address set to add an RNC IP
address.
Run the RNC MML command ADD VLANID to add a VLAN. In this step, set Next Hop
IP address and VLAN ID.
 On the NodeB side:

Run the NodeB MML command ADD DEVIP with IP address set to add a NodeB IP
address.
Run the NodeB MML command ADD VLANMAP to add an entry for VLAN mapping. In
this step, set Next Hop IP and VLAN ID.
4. (Optional) Configure a dedicated transmission resource mapping table and a dedicated

activation factor table for each operator.
a. Run the RNC MML command ADD TRMMAP to configure a dedicated transmission
resource mapping table for each operator.
b. Run the RNC MML command ADD TRMFACTOR to configure a dedicated activation
factor table for each operator.
c. Run the RNC MML command ADD ADJMAP. In this step, set Resource
Management Mode to EXCLUSIVE(EXCLUSIVE) and specify a dedicated TRMMAP
index and a dedicated activation factor table index for each operator.
To configure a transmission resource mapping table and an activation factor table shared by
operators, run the RNC MML commands ADD TRMMAP and ADD TRMFACTOR to configure a
TRMMAP and a TRMFACTOR and then run the RNC MML command ADD ADJMAP with
Resource Management Mode set to SHARE(SHARE) and a shared TRMMAP index as well
as a shared TRMFACTOR index specified.
Activating Static Independent Iub Transmission Mode on an

Existing BSC6900 (Using MML Commands)
2024-11-25 96
The following procedure describes how to activate the feature in MOCN scenarios where
independent Iub transmission resources were shared previously.

on the RNC.
2. Configure dedicated logical port bandwidth, path bandwidth, and IP address for each
operator to enable operators to manage their own transmission resources independently.
a. Add a dedicated logical port for each operator, and retain the original path address.
i. Run the RNC MML command ADD IPLOGICPORT (IP LP) or ADD
ATMLOGICPORT (ATM LP) to add a logical port. In this step, set Resource
Management Mode to EXCLUSIVE and set CN operator index. In addition,
set the Dynamic Bandwidth Sharing Switch parameter to OFF(OFF).
ii. Add a path over the new logical port.
(In IP transmission mode) Run the RNC MML command MOD IPPATH with Carry
Flag set to IPLGCPORT(IP Logic Port) and IP Logic Port No. set to the number of
the new logical port.
(In ATM transmission mode) Run the RNC MML command MOD AAL2PATH with
Bearing type set to ATMLOGICPORT(ATM Logical Port) and Bearing ATM logic
port No. set to the number of the new logical port.
Executing the MOD IPPATH or MOD AAL2PATH command causes service interruption.
iii. Run the RNC MML command RMV ATMLOGICPORT or RMV IPLOGICPORT to
remove the original logical port.
b. Add a logical port and IP path for another operator by referring to substeps 2 to 4 in
Step 2 in Activating Static Independent Iub Transmission Mode on a Newly Deployed
BSC6900 (Using MML Commands).
c. Run the RNC MML command MOD UNODEB. In this step, set Resource
Management Mode to EXCLUSIVE.
To change the operator that provides bandwidth for common channels of a shared cell, run
the RNC MML command MOD UCELLSETUP, and change the value of the Common
Channel Bandwidth Operator Index parameter. The default value 255 indicates that
the primary operator provides bandwidth for common channels of a shared cell. If there is
no primary operator, the first operator listed in the operator group provides bandwidth.
2024-11-25 97
3. (Optional) Configure a dedicated VLAN and a dedicated ADJMAP for each operator by
referring to Step 3 and Step 4 in Activating Static Independent Iub Transmission Mode on a
Newly Deployed BSC6900 (Using MML Commands).
Activating Dynamic Independent Iub Transmission Mode on

a Newly Deployed BSC6900 (Using MML Commands)
1. Configure dedicated logical port IP addresses and related transmission parameters for each
operator. For the configuration method, see section "Deployment of IP Transmission
Introduction on Iub Interface" in IP RAN Engineering Guide Feature Parameter Description .

on the RNC.
3. Configure a Hub logical port for the NodeB and a leaf logical port for each operator, and
configure the binding relationship between the IP paths and logical port numbers.
a. Run the RNC MML command ADD IPLOGICPORT to configure a Hub logical port for
the NodeB (Resource management mode set to SHARE and Type of the logic
port set to Hub) and configure a leaf logical port for each operator (Resource
management mode set to EXCLUSIVE and Type of the logic port set to Leaf). In
addition, set the Dynamic Bandwidth Sharing Switch parameter to OFF(OFF).
b. Run the RNC MML command ADD IPPATH to set up different IP paths, with Carry
Flag set to IPLGCPORT(IP Logic Port) and IP Logic Port No. set to the number of
the new leaf logical port of each operator.
c. (Optional) Configure a dedicated VLAN and a dedicated ADJMAP for each operator. For
detailed operations, see steps 3 and 4 in section Activating Static Independent Iub
Transmission Mode on a Newly Deployed BSC6900 (Using MML Commands).
4. Run the RNC MML command ADD UNODEB or MOD UNODEB with Resource
Management Mode set to EXCLUSIVE.

an Existing BSC6900 in IP Path Scenarios (Using MML
Commands)
In this scenario, the BSC6900 that uses IP paths needs to be restructured from Iub shared
transmission mode to dynamic independent Iub transmission mode.
1. Configure dedicated logical port IP addresses and related transmission parameters for each
operator. For the configuration method, see section "Deployment of IP Transmission
Introduction on Iub Interface" in IP RAN Engineering Guide Feature Parameter Description .
2024-11-25 98
2. Run the RNC MML command ADD UNODEBLICENSE or MOD UNODEBLICENSE. In this
step, select MOCN_INDEPENDENT_IUB_TRANS under the Function Switch1 parameter
to activate the license for this feature.
3. If no logical port has been configured before, configure logical ports according to step 4 in
section Activating Dynamic Independent Iub Transmission Mode on a Newly Deployed
BSC6900 (Using MML Commands). If a leaf logical port and an IP path have been configured
for an operator before, the IP path can be bound to the dedicated logical port of the
operator. The detailed operations are as follows:
a. Add a dedicated logical port for the operator, and retain the original path address.
i. Add a Hub logical port shared by operators: Run the RNC MML command ADD
IPLOGICPORT. In this step, set Type of the logic port to Hub and Resource
management mode to SHARE(SHARE).
ii. Add a dedicated logical port for the operator: Run the RNC MML command ADD
IPLOGICPORT. In this step, set Resource management mode to
EXCLUSIVE(EXCLUSIVE) and CN operator index to the index of the
operator.
iii. Bind the original path to the newly added logical port of the operator: Run the
RNC MML command MOD IPPATH. In this step, set Carry Flag to
IPLGCPORT(IP Logic Port) and IP Logic Port No. to the newly added logical
port of the operator.
Executing the MOD IPPATH or MOD AAL2PATH command causes service

interruption.
iv. Run the RNC MML command RMV IPLOGICPORT to remove the logical port
that is shared by operators.
b. Add a logical port and an IP path for another operator by following Step 3 in section
Activating Dynamic Independent Iub Transmission Mode on a Newly Deployed
4. Run the RNC MML command MOD UNODEB. In this step, set Resource Management
Mode to EXCLUSIVE.
5. (Optional) Run the RNC MML command ADD UCELLSETUP with Common Channel
indicates that the primary operator provides bandwidth for common channels of a shared
cell. If there is no primary operator, the first operator listed in the operator group provides
bandwidth.
6. (Optional) Configure a dedicated VLAN and a dedicated ADJMAP for each operator. For
detailed operations, see steps 3 and 4 in section Activating Static Independent Iub
Transmission Mode on a Newly Deployed BSC6900 (Using MML Commands).
2024-11-25 99

a Newly Deployed BSC6910 in IP Pool Scenarios (Using MML
Commands)
1. Configure the transmission resource pool, dedicated IP address, and other transmission
parameters for each operator. For the configuration method, see section "Configuring a
Transmission Resource Pool for the Iub Interface" in Transmission Resource Pool in RNC

on the RNC.
3. Configure a Hub logical port for the NodeB and a leaf logical port for each operator, and
configure the binding relationship between the adjacent nodes and logical port numbers.
a. Run the RNC MML command ADD IPLOGICPORT to configure a Hub logical port for
the NodeB (Resource management mode set to SHARE and Type of the logic
port set to Hub) and configure a leaf logical port for each operator (Resource
management mode set to EXCLUSIVE and Type of the logic port set to Leaf). In
addition, set the Dynamic Bandwidth Sharing Switch parameter to OFF(OFF).
b. Run the RNC MML command ADD ADJNODE with Resource Management Mode
set to EXCLUSIVE on the RNC to configure the shared NodeB as the adjacent node
for each operator.
c. Run the RNC MML command ADD ADJMAP to configure a dedicated ADJMAP for each
adjacent node, with Resource Management Mode set to
EXCLUSIVE(EXCLUSIVE).
d. Run the RNC MML command ADD ADJLOGICPORTBIND to bind a logical port
number with the adjacent node.
4. Run the RNC MML command ADD UNODEB. In this step, set Resource Management
Mode to EXCLUSIVE.
5. (Optional) Run the RNC MML command ADD UCELLSETUP. In this step, set Common
Channel Bandwidth Operator Index to the index of an operator. This parameter is set
to 255 by default, indicating that the common channel is owned by the primary operator or
the first operator in the operator group when no primary operator is specified.
6. (Optional) Configure a dedicated VLAN for each operator. For detailed operations, see Step
3 in section Activating Static Independent Iub Transmission Mode on a Newly Deployed

an Existing BSC6910 in IP Pool Scenarios (Using MML
Commands)
2024-11-25 100
In this scenario, the BSC6910 that uses an IP address pool needs to be restructured from Iub
shared transmission mode to dynamic independent Iub transmission mode.
1. Configure the transmission resource pool, dedicated IP address, and other transmission
parameters for each operator. For the configuration method, see section "Configuring a
Transmission Resource Pool for the Iub Interface" in Transmission Resource Pool in RNC
2. Run the RNC MML command ADD UNODEBLICENSE or MOD UNODEBLICENSE with
MOCN_INDEPENDENT_IUB_TRANS selected under the Function Switch1 parameter to
enable this feature.
Mode to EXCLUSIVE.
4. If no logical port has been configured before, configure logical ports according to Step 4 in
section Activating Dynamic Independent Iub Transmission Mode on a Newly Deployed
BSC6910 in IP Pool Scenarios (Using MML Commands). Then remove the original logical
port using the RMV IPLOGICPORT command.
5. Run the RNC MML command RMV ADJNODE to remove the shared adjacent node and run
the RNC MML command ADD ADJNODE to add a dedicated adjacent node for each
operator.
Removing the shared adjacent node causes service interruption.
6. Run the RNC MML command ADD ADJMAP to configure a dedicated ADJMAP for each
adjacent node, with Resource Management Mode set to EXCLUSIVE(EXCLUSIVE).
7. (Optional) Run the RNC MML command ADD UCELLSETUP with Common Channel
indicates that the primary operator provides bandwidth for common channels of a shared
cell. If there is no primary operator, the first operator listed in the operator group provides
bandwidth.
8. (Optional) Configure a dedicated VLAN for each operator. For detailed operations, see Step
3 in section Activating Static Independent Iub Transmission Mode on a Newly Deployed
 IP transmission mode
1. Run the RNC MML command LST IPLOGICPORT to query the logical port and port
bandwidth configured for each operator. If the queried information is the same as the
preset settings, the feature has been activated.
2024-11-25 101
2. After this feature has been functioning for a certain period, check the
VS.LGCPRT.PEAK.TXRATE counter for each logical port. If the value of this counter only
involves user-plane data and is not 0, the feature is functioning properly.
VS.LGCPRT.PEAK.TXRATE ( BSC6910 , T7506: Maximum Transmit Rate of Logical Port

BSC6900 )
VS.LGCPRT.MEAN.TXRATE ( BSC6910 , T7507: Average Transmit Rate of Logical Port

BSC6900 )
 ATM transmission mode
1. Check the counters listed in the following table to query the bandwidth allocated to each
operator's logical port. If the allocated bandwidth is consistent with the configured
bandwidth, this feature has taken effect.
VS.ATMLGCPRT.Alloced.Ave.Fwd ( Mean Forward Bandwidth Assigned to the ATM

BSC6910 , BSC6900 ) Logical Port
VS.ATMLGCPRT.Alloced.Ave.Bwd ( Mean Backward Bandwidth Assigned to the ATM

VS.ATMLGCPRT.Alloced.Max.Fwd ( Maximum Forward Bandwidth Assigned to the ATM

VS.ATMLGCPRT.Alloced.Max.Bwd ( Maximum Backward Bandwidth Assigned to the

BSC6910 , BSC6900 ) ATM Logical Port
2. Run the DSP ATMLOGICPORT command to query the operator's Iub resource usage
corresponding to the logical port.
Deactivating Static Independent Iub Transmission Mode on

a BSC6900 (Using MML Commands)
To deactivate the feature, run the following MML commands:
1. Create a shared logical port: Run the RNC MML command ADD IPLOGICPORT or ADD
ATMLOGICPORT to add a logical port. In this step, set Resource Management Mode to
SHARE.
2. Add a path over the new logical port:
 (In IP transmission mode) Run the RNC MML command MOD IPPATH with Carry Flag
set to IPLGCPORT(IP Logic Port) and IP Logic Port No. set to the number of the
new logical port.
 (In ATM transmission mode) Run the RNC MML command MOD AAL2PATH with
Bearing type set to ATMLOGICPORT(ATM Logical Port) and Bearing ATM logic
port No. set to the number of the new logical port.
2024-11-25 102
3. (Optional) Run the RNC MML command RMV IPLOGICPORT (IP LP) or RMV
ATMLOGICPORT (ATM LP) to remove the original logical port.
Mode to SHARE.
5. Run the RNC MML command MOD UNODEBLICENSE to turn off the license switch. In this
step, deselect MOCN_INDEPENDENT_IUB_TRANS(MOCN Independent Iub Resource
Allocation License) under the Function Switch1 parameter.
Deactivating Dynamic Independent Iub Transmission Mode

on a BSC6900 in Path Scenarios (Using MML Commands)
To deactivate the feature, run the following MML commands:
1. Create a logical port: Run the RNC MML command ADD IPLOGICPORT. In this step, set
Resource Management Mode to SHARE.
2. Bind the original IP path to the new logical port: Run the RNC MML command MOD
IPPATH. In this step, set Carry Flag to IPLGCPORT(IP Logic Port) and IP Logic Port
No. to the newly added logical port of the operator.
3. (Optional) Run the RNC MML command RMV IPLOGICPORT to remove the dedicated
logical port of the operator.
Mode to SHARE.
Deactivating Dynamic Independent Iub Transmission Mode

on a BSC6910 (Using MML Commands)
1. Run the RNC MML command RMV ADJNODE to remove dedicated adjacent nodes of the
operators.
Removing a dedicated adjacent node causes service interruption.
2024-11-25 103
2. Run the RNC MML command ADD ADJNODE to add a shared adjacent node. In this step,
set Resource Management Mode to SHARE.
3. Run the RNC MML command RMV IPLOGICPORT to remove the dedicated leaf logical
ports of operators and the Hub logical port of the NodeB.
If flow shaping over logical ports is required, the Hub logical port does not need to be removed.
4. (Optional) Run the RNC MML commands RMV DEVIP and RMV IPPOOL for multiple times
to remove multiple IP addresses and transmission resource pools and retain only one
interface-board IP address and transmission resource pool.
Mode to SHARE.
//Activating static independent Iub transmission mode on the BSC6900

//Activating the NodeB-level license for this feature on the RNC
ADD UNODEBLICENSE: IDTYPE=BYID,NodeBId=12,FuncSwitch1=MOCN_INDEPENDENT_IUB_TRANS-1;
//Setting the resource sharing mode to EXCLUSIVE on the NodeB

ADD UNODEB: NodeBName="12", NodeBId=12, SRN=1, SN=1, TnlBearerType=IP_TRANS,
RscMngMode=EXCLUSIVE, SharingType=MOCN;
//(In IP transmission mode) Configuring an independent logical port and port bandwidth for each operator, and
adding a path to each logical port
SET ETHPORT: SRN=0, SN=26, BRDTYPE=GOUc, PN=3;
ADD ETHIP: SRN=0, SN=26, PN=6, IPINDEX=0, IPADDR="10.11.11.12", MASK="255.255.255.0";
ADD IPLOGICPORT: SRN=0, SN=26, BT=FG2c, LPNTYPE=Leaf, LPN=0, CARRYT=ETHER, PN=6,
RSCMNGMODE=EXCLUSIVE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON;
RSCMNGMODE=EXCLUSIVE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON;
ADD ADJNODE: ANI=1, NAME="NodeB1", NODEBID=12, TRANST=IP, NODET=IUB, IPPOOLINDEX=1;
2024-11-25 104
ADD IPPATH: ANI=1, PATHID=1, TRANST=IP, PATHT=QoS, IPADDR="10.11.11.12",

PEERIPADDR="10.102.102.103", TXBW=10000, RXBW=10000, CARRYFLAG=IPLGCPORT, LPNSN=26, LPN=1,
VLANFlAG=DISABLE, PATHCHK=DISABLED;
PEERIPADDR="10.102.102.103",TXBW=10000, RXBW=10000, CARRYFLAG=IPLGCPORT, LPNSN=26, LPN=2,
VLANFlAG=DISABLE, PATHCHK=DISABLED;
//(In ATM transmission mode) Configuring an independent logical port and port bandwidth for each operator,
and adding a path to each logical port
ADD IMAGRP: SRN=0, SN=26, BT=AOUc, IMAGRPN=0, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
ADD ADJNODE: ANI=1, NAME="NodeB1", NODEBID=1, TRANST=ATM, NODET=IUB, IsROOTNODE=YES,
SAALLNKN=20;
ADD ATMLOGICPORT: SRN=0, SN=26, LPNTYPE=Leaf, BT=AOUc, LPN=10, CARRYT=IMA, CARRYSN=26,

CARRYIMAGRPN=0, TXBW=10000, RXBW=10000, RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0,
FLOWCTRLSWITCH=ON;
ADD AAL2PATH: ANI=1, PATHID=10, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=26, CARRYVPN=10,
VPI=2, VCI=50, TXTRFX=111, RXTRFX=111, AAL2PATHT=SHARE;

CARRYIMAGRPN=0, TXBW=20000, RXBW=20000, RSCMNGMODE=EXCLUSIVE, CNOPINDEX=3,
FLOWCTRLSWITCH=ON;
ADD AAL2PATH: ANI=1, PATHID=20, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=26, CARRYVPN=20,
VPI=3, VCI=60, TXTRFX=111, RXTRFX=111, AAL2PATHT=SHARE;
//(In IP path mode) Deactivating static or dynamic dependent Iub transmission mode on the BSC6900
MOD UNODEB: IDTYPE=BYID, NodeBId=12, RscMngMode=SHARE;
RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
MOD IPPATH: ANI=1, PATHID=1, CARRYFLAG=IPLGCPORT, LPNSN=26, LPN=2;
MOD IPPATH: ANI=1, PATHID=2, CARRYFLAG=IPLGCPORT, LPNSN=26, LPN=2;
//(In ATM transmission mode) Deactivating static independent Iub transmission mode on the BSC6900
MOD UNODEB: IDTYPE=BYID, NodeBId=12, RscMngMode=SHARE;
CARRYIMAGRPN=0, TXBW=10000, RXBW=10000, RSCMNGMODE=SHARE, FLOWCTRLSWITCH=ON;
MOD AAL2PATH: ANI=1, PATHID=10, CARRYT=IMA, CARRYF=0, CARRYSN=26, CARRYIMAGRPN=30,
RSCGRPFLAG=NO;
MOD AAL2PATH: ANI=1, PATHID=20, CARRYT=IMA, CARRYF=0, CARRYSN=26, CARRYIMAGRPN=30,
RSCGRPFLAG=NO;
2024-11-25 105
//(In IP pool mode) Activating dynamic independent Iub transmission mode on the BSC6910

//Configuring the dedicated device IP address and transmission resource pool for each operator
ADD DEVIP:IPADDR="10.160.100.103", SRN=0, SN=23, DEVTYPE=LOGIC_IP, REMARK="<NULL>";
ADD DEVIP:IPADDR="10.160.100.104", SRN=0, SN=23, DEVTYPE=LOGIC_IP, REMARK="<NULL>";
ADD SRCIPRT:SRN=0, SN=23, SRCIPADDR="10.160.100.103", IPTYPE=DEVIP, NEXTHOP="10.0.23.1",

STANDBYNEXTHOPSWITCH=NO, REMARK="for-IUB-0";
ADD SRCIPRT:SRN=0, SN=23, SRCIPADDR="10.160.100.104", IPTYPE=DEVIP, NEXTHOP="10.0.23.1",
STANDBYNEXTHOPSWITCH=NO, REMARK="for-IUB-1";
ADD SCTPLNK: SCTPLNKID=18, APP=NBAP, MODE=SERVER, LOCIP1="10.22.1.86", PEERIP1="10.22.1.89",
PEERPN=1024, LOGPORTFLAG=NO, SWITCHBACKFLAG=YES, REMARK="Iub19";
ADD SCTPLNK: SCTPLNKID=19, APP=NBAP, MODE=SERVER, LOCIP1="10.22.1.86", PEERIP1="10.22.1.89",
PEERPN=1025, LOGPORTFLAG=NO, SWITCHBACKFLAG=YES, REMARK="Iub19";
ADD IPPOOL:IPPOOLINDEX=0, IPPOOLNAME="IUB-2OP", MODE=ETHL3;
ADD IPPOOL:IPPOOLINDEX=10, IPPOOLNAME="IUB-1OP", MODE=ETHL3;
ADD IPPOOLIP:IPPOOLINDEX=0, IPADDR="10.160.100.104", SRN=0, SN=23;

ADD IPPOOLIP:IPPOOLINDEX=10, IPADDR="10.160.100.103", SRN=0, SN=23;
//Configuring a Hub logical port for the NodeB

ADD IPLOGICPORT:SRN=0, SN=23, BT=GOUc, LPNTYPE=Hub, LPN=512, CARRYT=IPPOOL,
RSCMNGMODE=SHARE, CIR=5, TRMLOADTHINDEX=4, IPADDR="255.255.255.255", REMARK="-",
DYNAMICSHARESW=ON;
//Configuring a leaf logical port for operator 0

ADD IPLOGICPORT:SRN=0, SN=23, BT=GOUc, LPNTYPE=Leaf, LPN=0, CARRYT=IPLOGICPORT, UPPERLP=512,
RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, CIR=4, CBS=4500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON,
FCINDEX=0, TRMLOADTHINDEX=4, IPADDR="10.160.100.103", REMARK="-", OPTYPE=UMTS;
//Configuring a leaf logical port for operator 1

ADD IPLOGICPORT:SRN=0, SN=23, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=IPLOGICPORT, UPPERLP=512,
RSCMNGMODE=EXCLUSIVE, CNOPINDEX=1, CIR=4, CBS=4500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON,
FCINDEX=0, TRMLOADTHINDEX=4, IPADDR="10.160.100.104", REMARK="-", OPTYPE=UMTS;
//Configuring an adjacent node for each operator on the RNC
2024-11-25 106
ADD ADJNODE:ANI=65533, NAME="1Op", LOGICRNCID=33, NODEBID=103, TRANST=IP, NODET=IUB,

IPPOOLINDEX=10, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TXBW=1000, RXBW=1000,
TRMLOADTHINDEX=3, PINGSWITCH=ENABLE, PERIOD=5, CHECKCOUNT=5, DSCP=46, PINGPKGLEN=256,
LEARNDIPAUTO=YES;
IPPOOLINDEX=0, CNMNGMODE=EXCLUSIVE, CNOPINDEX=1, TXBW=1000, RXBW=1000, TRMLOADTHINDEX=3,
PINGSWITCH=ENABLE, PERIOD=5, CHECKCOUNT=5, DSCP=46, PINGPKGLEN=256, LEARNDIPAUTO=YES;
//Configuring the binding relationship between the adjacent node and the logical port
ADD ADJLOGICPORTBIND:ANI=65533, SRN=0, SN=23, LPN=0;
ADD ADJLOGICPORTBIND:ANI=65534, SRN=0, SN=23, LPN=1;
//Adding different device IP address on the NodeB side
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, VRFIDX=0, IP="10.22.1.89", MASK="255.255.255.0";
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, VRFIDX=0, IP="10.22.2.89", MASK="255.255.255.0";
//(In IP pool mode) Deactivating dynamic independent Iub transmission mode on the BSC6910
RMV ADJNODE:ANI=65533;
RMV ADJNODE:ANI=65534;
IPPOOLINDEX=10, CNMNGMODE=SHARE, TXBW=1000, RXBW=1000, TRMLOADTHINDEX=3,
PINGSWITCH=ENABLE, PERIOD=5, CHECKCOUNT=5, DSCP=46, PINGPKGLEN=256, LEARNDIPAUTO=YES;
//(In IP path mode) Activating dynamic independent Iub transmission mode on the BSC6900

//Configuring the transport layer data

2024-11-25 107
//Adding different device IP addresses for an interface board

ADD DEVIP: SRN=11, SN=22, DEVTYPE=LOGIC_IP, IPADDR="10.51.101.22";
//Adding routes to the destination IP addresses for an interface board

ADD IPRT: SRN=11, SN=22, DSTIP="10.3.20.000", DSTMASK="255.255.255.248", NEXTHOPTYPE=Gateway,
NEXTHOP="10.21.22.006", PRIORITY=HIGH, REMARK="To_NodeB_RanSharing_High_OP0";
NEXTHOP="10.21.23.006", PRIORITY=LOW, REMARK="To_NodeB_RanSharing_Low_OP0";
//Configuring a Hub logical port of the NodeB and a leaf logical port for each operator and binding each IP path
to its dedicated leaf logical port
ADD IPLOGICPORT: SRN=11, SN=22, BT=FG2c, LPNTYPE=Hub, LPN=532, CARRYT=ETHER, PN=11,
RSCMNGMODE=SHARE, CIR=30, OPSEPFLAG=OFF;
ADD IPLOGICPORT: SRN=11, SN=22, BT=FG2c, LPNTYPE=Leaf, LPN=70, CARRYT=IPLOGICPORT,
UPPERLP=532, RSCMNGMODE=EXCLUSIVE, OPTYPE=UMTS, CNOPINDEX=0, BWADJ=OFF, CIR=30,
FLOWCTRLSWITCH=ON;
ADD IPLOGICPORT: SRN=11, SN=22, BT=FG2c, LPNTYPE=Leaf, LPN=71, CARRYT=IPLOGICPORT,
UPPERLP=532, RSCMNGMODE=EXCLUSIVE, OPTYPE=UMTS, CNOPINDEX=3, BWADJ=OFF, CIR=30,
FLOWCTRLSWITCH=ON;
VLANFLAG=DISABLE, PATHCHK=DISABLED;
VLANFLAG=DISABLE, PATHCHK=DISABLED;
2024-11-25 108
Use the following counters or commands to monitor the usage of Iub transmission resources:
In IP transmission mode:
 VS.LGCPRT.PEAK.TXRATE ( BSC6910 , BSC6900 )
 VS.LGCPRT.MEAN.TXRATE ( BSC6910 , BSC6900 )
In ATM transmission mode, run the DSP ATMLOGICPORT command to view the usage of Iub
transmission resources on a logical port of the corresponding operator.

Detailed Iub transmission resource allocations are customer-specific. Adjust them only when
customer requirements change.
None.
14.6 Single CN With Multi-PLMN IDs
14.6.1 When to Use Single CN With Multi-PLMN IDs

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 the MOCN scenario.

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 and GWCN functions
 Whether all or some CNs are shared
14.6.3 Deployment
Requirements
 Other Features
Before you deploy this function, the WRFD-021311 MOCN Introduction Package feature must
If an operator has multiple CN nodes available in a domain, deploy WRFD-021302 Iu Flex.
 Hardware
None
 License
No license control items are added because it is an enhancement of the MOCN Introduction
Package feature.
Description.
2024-11-25 109
 Other Requirements
Before you activate this function, both the MSC and SGSN must be deployed with the multi-
PLMN or GWCN function.
Data Preparation
Parameter Parameter ID Setting Notes Data

Name Source
Single CN With MultiPLMNforSingleCNSwitc Turn on this switch when only the Network
Multi-PLMN IDs h ( BSC6910 , BSC6900 ) primary operator's CNs are available plan
Switch and all the CN nodes of the primary
operator are shared by multiple
operators.
CN Operator CnOpIndex ( BSC6910 , Configure the operator sharing Network

Index BSC6900 ) relationship by CN node. plan
CN node ID CNID ( BSC6910 , BSC6900 ) Configure the operator sharing Network

relationship by CN node. plan
Sharing SharedCnOpIndex ( Configure the operator sharing Network

Operator Index BSC6910 , BSC6900 ) relationship by CN node. plan
Enhance Multi- MultiPLMNforCNEnhanceSw Turn on this switch if some CN nodes Network

PLMN for CN ( BSC6910 , BSC6900 ) are shared and others are dedicated. plan
 If all CN nodes are shared, perform the following steps:
1. (Optional) Delete the Iu interface and the mapping between the NRI and the CN node for
the secondary operator.
2. Run the RNC MML command SET UOPERATORSHARINGMODE with Intra RAT Inter
Plmn Ho Allowed set to OFF.
3. Run the RNC MML command SET UOPERATORSHARINGMODE with Single CN With
Multi-PLMN IDs Switch set to ON.
 If some CN nodes are shared and others are dedicated, perform the following steps:
1. Run the RNC MML command ADD UCNNODESHAREDMAP with Sharing Operator Index
configured based on network plans.
2. Run the RNC MML command SET UOPERATORSHARINGMODE with Intra RAT Inter
Plmn Ho Allowed set to OFF.
3. Run the RNC MML command SET UOPERATORSHARINGMODE with Enhance Multi-
PLMN for CN set to ON.
2024-11-25 110
If the primary and secondary operators' UEs (including Non-Supporting and Supporting UEs) in
the MOCN cell can successfully register with the shared CNs and properly initiate CS and PS
services, this function is successfully activated.
The shared CNs must offload UEs onto dedicated UEs before this function is deactivated on the
RNC. Otherwise, UEs cannot be routed to the shared CNs after the function is deactivated but
can register with the shared CNs and carry the NRIs allocated by the shared CNs. As a result, UEs
fail to perform mobile originated or terminated services on dedicated CNs.
 When only the primary operator's CNs are available and all of them are shared, perform the
following steps:
1. (Optional) If the operator's CN node is not configured, you need to configure the CN
node and NRI first.
2. Run the RNC MML command SET UOPERATORSHARINGMODE with Single CN With
Multi-PLMN IDs Switch set to OFF.
 When some CNs are shared and others are dedicated, perform the following steps:
1. (Optional) Run the RNC MML command RMV UCNNODESHAREDMAP to remove the
CN sharing relationship among operators.
2. Run the RNC MML command SET UOPERATORSHARINGMODE with Enhance Multi-
PLMN for CN set to OFF.
//Activating the Single CN with Multi-PLMN IDs function after MOCN Introduction Package is deployed
//(Optional) Deleting the Iu interface for the secondary operator
RMV UCNNODE: CnOpIndex=1, CNId=11;
//Turning on the Single CN With Multi-PLMN IDs Switch on the RNC
MultiPLMNforSingleCNSwitch=ON, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO,
DefaultCnOp=0;
2024-11-25 111
//Deactivation procedure (If the 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
//Setting parameters for a secondary operator
//Adding mapping information between CN node 11 and an NRI for a secondary operator
//Turning off the Single CN With Multi-PLMN IDs Switch on the RNC
MultiPLMNforSingleCNSwitch=OFF, InterPlmnHoAllowedIntraRat=NO,
InterPlmnHoAllowedInterRat=NO,DefaultCnOp=0;
//Activating the Enhanced Multi-PLMN for CN function after MOCN Introduction Package is deployed
//Configuring the CN sharing relationship among operators
ADD UCNNODESHAREDMAP: CnOpIndex=0, CNId=1, SharedCnOpIndex=1;
//Turning on the Enhance Multi-PLMN Switch for CN on the RNC
MultiPLMNforCNEnhanceSw=ON, InterPlmnHoAllowedIntraRat=NO,InterPlmnHoAllowedInterRat=NO,
DefaultCnOp=0;
//Deactivating the Enhanced Multi-PLMN for CN function after MOCN Introduction Package is deployed
//Removing the CN sharing relationship among operators
RMV UCNNODESHAREDMAP: CnOpIndex=0, CNId=1, SharedCnOpIndex=1;
//Turning off the Enhance Multi-PLMN Switch for CN on the RNC
MultiPLMNforCNEnhanceSw=OFF, InterPlmnHoAllowedIntraRat=NO,InterPlmnHoAllowedInterRat=NO,
DefaultCnOp=0;

None

None
None
14.7 Forbidding UEs of Specific Operators from Setting Up CS Services
2024-11-25 112
14.7.1 When to Use Forbidding UEs of Specific Operators from Setting

Up CS Services
This function is enabled when the customer wants to forbid specific operators from CS services.
 You are advised to enable this function on all the RNCs.

This prevents the RNC from using different policies to process inter-RNC handover UEs due
to different parameter settings on the SRNC and DRNC.
For example, if this function is enabled on the SRNC, but disabled on the DRNC, the DRNC
cannot set up CS RABs for UEs with only signaling connections during soft handovers
because the SRNC disallows CS RAB setups, which conflicts with parameter setting on the
DRNC.
 If both shared cells (for example, shared by operator A and B) and dedicated cells (for
example, owned by operator A) are allowed in a MOCN-enabled network, see Table 14-3 for
detailed deployment.
Table 14-3 Deployment suggestions in MOCN scenarios
Operat Whether to Suggestion
or Enable This
Function
Operato Not After this function is enabled, UEs cannot set up CS RABs in dedicated
rA recommended cells, affecting user experience.
Operato As required After this function is enabled, it is recommended that the inter-PLMN
rB handover function be disabled.
If the inter-PLMN handover function is enabled, a UE of operator B may
set up CS services when the policy switch is turned on. In this case, if
the UE initiates a handover request to a cell of operator A served by
another RNC and this function is enabled on the TRNC, the handover
fails as the SRNC cannot determine whether the function is enabled on
the TRNC or not.

Before you deploy this function, collect the following counters:
 VS.RAB.AttEstab.AMR.PLMN.RNC ( BSC6910 , BSC6900 )
 VS.RAB.SuccEstab.AMR.PLMN.RNC ( BSC6910 , BSC6900 )
14.7.3 Planning
14.7.3.1 RF Planning
N/A
14.7.3.2 Network Planning

N/A
14.7.3.3 Hardware Planning

N/A
14.7.4 Deployment
2024-11-25 113
14.7.4.1 Deployment Process

N/A
Other Features
Before you activate this function, the WRFD-020400 DRD Introduction Package feature must be
enabled.
Hardware
N/A
License
This function does not introduce any new license.
Others
None
Pay attention to the following items:
 Customers must clarify their requirements and accept impacts brought by this function.
 The impact of the inter-RAT DRD function for CS+PS combined services
 If DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH under the DrSwitch ( BSC6910 ,

BSC6900 ) parameter is selected, this function can take effect for combined services
and the inter-RAT DRD can be triggered, but UE compatibility issues may occur.
 If DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH under the DrSwitch ( BSC6910 ,

BSC6900 ) parameter is deselected, this function does not take effect for combined
services. Therefore, the number of times that this function takes effect decreases. Then,
the RNC allows or rejects CS RABs for UEs based on the policy switch setting.
 The measurement control priority for forbidding UEs of specific operators from setting up CS
services is higher than the priority for other types of handovers (such as the coverage-based
inter-RAT handover). Therefore, other types of handovers may be affected.
14.7.4.4 Hardware Adjustment

N/A
14.7.4.5 Data Preparation and Feature Activation

14.7.4.5.1 Data Preparation
Table 14-4 provides the data to prepare before deploying this function.
2024-11-25 114
Table 14-4 Data preparation

Parameter Parameter ID Settin Data Source Remarks
Name g
Notes
Limit CS RAB CSLimitInUMTSSwitch ( OFF Default/ NE: RNC

in UMTS BSC6910 , BSC6900 ) Recommended value MO:
Switch UOPERALGOSWITCH
MAE-Deployment batch
modification is not
supported.
Limit CS RAB CSLimitInUMTSStrategy OFF Default/ NE: RNC

in UMTS SW ( BSC6910 , Recommended value MO:
Strategy BSC6900 ) UOPERALGOSWITCH
Switch MAE-Deployment batch
modification is not
supported.
Time to TrigTime3CForCSLimit ( D640 Default/ NE: RNC

Trigger Event BSC6910 , BSC6900 ) Recommended value MO:
3C for Limit UINTERRATHONCOV
CS RAB MAE-Deployment batch
modification is not
supported.
Inter RAT InterRATTarThldForCSLi 21 Default/ NE: RNC

Target mit ( BSC6910 , Recommended value MO:
Threshold for BSC6900 ) UINTERRATHONCOV
Limit CS RAB MAE-Deployment batch
modification is not
supported.

1. Run the RNC MML command SET UCORRMALGOSWITCH with

DR_RAB_SING_DRD_SWITCH under the Direct Retry Switch parameter selected.
2. (Optional) Run the RNC MML command SET UCORRMALGOSWITCH with

DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH under the Direct Retry Switch
parameter selected.
3. Run the RNC MML command MOD UCELLMBDRINTERFREQ to deactivate the inter-
frequency MBDR algorithm.
4. Run the RNC MML command MOD UCELLMBDRINTERRAT to deactivate the inter-RAT
MBDR algorithm.
5. Run the RNC MML command SET UOPERALGOSWITCH with CSLimitInUMTSSwitch (

BSC6910 , BSC6900 ) set to ON.
6. (Optional) Run the RNC MML command SET UOPERALGOSWITCH with

CSLimitInUMTSStrategySW ( BSC6910 , BSC6900 ) set to ON.
2024-11-25 115
7. (Optional) Run the RNC MML command SET UINTERRATHONCOV with

TrigTime3CForCSLimit ( BSC6910 , BSC6900 ) and InterRATTarThldForCSLimit (
BSC6910 , BSC6900 ) specified.

//Turning on the DRD switch
SET UCORRMALGOSWITCH:DrSwitch=DR_RAB_SING_DRD_SWITCH-1;
//(Optional) Enabling the inter-RAT DRD function for CS+PS combined services
SET UCORRMALGOSWITCH:DrSwitch=DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWITCH-1;
//Deactivating the inter-frequency MBDR algorithm
MOD UCELLMBDRINTERFREQ:CellId=11,InterFreqActiveType=CSAMR_INTERFREQ-0;
MOD UCELLMBDRINTERFREQ:CellId=11,InterFreqActiveType=CSNONAMR_INTERFREQ-0;
MOD UCELLMBDRINTERFREQ:CellId=11,InterFreqActiveType=PSR99_INTERFREQ-0;
//Deactivating the inter-RAT MBDR algorithm
MOD UCELLMBDRINTERRAT:CellID=11,InterRatActiveType=CSAMR_INTERRAT-0;
//Turning on the function switch
ADD UOPERALGOSWITCH: CnOpIndex=0, CSLimitInUMTSSwitch=on;

//(Optional) Turning on the policy switch
ADD UOPERALGOSWITCH: CnOpIndex=0, CSLimitInUMTSStrategySW=on;

//Setting the delayed time to trigger event 3C and inter-RAT cell quality threshold for forbidding CS services
SET UINTERRATHONCOV:TrigTime3CForCSLimit=D640,InterRATTarThldForCSLimit=21;

After this function is enabled, the RAB assignment success rate decreases:
The RAB assignment success rate = VS.RAB.SuccEstab.AMR.PLMN.RNC ( BSC6910 ,
BSC6900 )/VS.RAB.AttEstab.AMR.PLMN.RNC ( BSC6910 , BSC6900 )
14.7.4.7 Deactivation
1. Run the RNC MML command SET UOPERALGOSWITCH with CSLimitInUMTSSwitch (

BSC6910 , BSC6900 ) set to OFF.

//Turning off the function switch
ADD UOPERALGOSWITCH: CnOpIndex=0, CSLimitInUMTSSwitch=off;
14.7.4.8 Reconfiguration
2024-11-25 116
N/A

N/A

N/A
None
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.
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?
1. Open the EXCEL file of parameter reference.
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.
3. Click OK. All parameters related to the feature are displayed.
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.
2024-11-25 117
 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 Summary : contains base station equipment and transport
counters.
 NodeBFunction Performance Counter Summary : contains all counters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
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?
1. Open the EXCEL file of performance counter reference.
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.
3. Click OK. All counters related to the feature are displayed.
For the acronyms, abbreviations, terms, and definitions, see Glossary .
1. 3GPP TS 23.236, "Intra-domain connection of Radio Access Network (RAN) nodes to

multiple Core Network (CN) nodes"
2. 3GPP TS 25.331, "Radio Resource Control (RRC)"
3. 3GPP TS 23.122, "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle
mode"
4. 3GPP TS 23.251, "Network Sharing Architecture and functional description"
5. Iu Flex Feature Parameter Description
6. RAN Sharing Feature Parameter Description
7. Load Control Feature Parameter Description
8. Call Admission Control Feature Parameter Description
9. HSDPA Feature Parameter Description
2024-11-25 118

RAN Feature Documentation - MOCN - 20231121 091122 - 091357

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

RAN Feature Documentation - MOCN - 20231121 091122 - 091357

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RAN Feature Documentation - MOCN - 20231121 091122 - 091357

Uploaded by

Copyright:

Available Formats

WCDMA RAN

Issue Date 2023-05-12

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. All rights reserved.

Huawei Technologies Co., Ltd.

5 MOCN Mobility Management

12.3 Configuring the CN Sharing Relationship Among Operators

14.7.4.7.3 MML Command Examples

 1.2 General Statements

 1.3 Change History

 1.4 Differences Between NodeB Types

 WRFD-021311 MOCN Introduction Package

 WRFD-02131101 Carrier Sharing by Operators

 WRFD-02131102 Dedicated NodeB/Cell for Operators

 WRFD-02131103 MOCN Mobility Management

 WRFD-02131104 MOCN Load Balance

 WRFD-02131105 MOCN Independent Performance Management

 WRFD-02131106 Routing Roaming UEs in Proportion

 WRFD-140223 MOCN Cell Resource Demarcation

 WRFD-150213 MOCN Independent Iub Transmission Resource Allocation

 WRFD-150214 MOCN Independent CE Resource Allocation

1.2 General Statements

Feature Parameter Description documents are intended to acquaint readers with:

 The technical principles of features and their related parameters

1.3 Change History

Compared with Issue 01 (2018-04-20) of RAN20.1, Issue 02 (2018-10-30) of RAN20.1 includes

Editorial None None

This issue does not include any changes.

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

Feature Added the counter VS.TCP.NonHS.Usage.Mean ( None

Editorial None None

1.4 Differences Between NodeB Types

Feature Support by Macro, and LampSite NodeBs

Feature ID Feature Name Supported by Supported by Supported by

WRFD- MOCN Introduction Package Yes Yes Yes Yes

WRFD- Carrier Sharing by Operators Yes Yes Yes Yes

WRFD- Dedicated NodeB/Cell for Yes Yes Yes Yes

WRFD- MOCN Mobility Management Yes Yes Yes Yes

WRFD- MOCN Load Balance Yes Yes Yes Yes

WRFD- MOCN Independent Yes Yes Yes Yes

WRFD- Routing Roaming UEs in Yes Yes Yes Yes

WRFD- MOCN Cell Resource Yes Yes Yes Yes

Feature ID Feature Name Supported by Supported by Supported by

WRFD- MOCN Independent Iub Yes Yes Yes Yes

WRFD- MOCN Independent CE Yes Yes Yes Yes

 Compared with RAN sharing, MOCN improves network resource utilization.

Figure 2-1 MOCN solution

 The MOCN solution has two types of UEs:

 The spectrum utilization policy for the MOCN solution is as follows:

 The MOCN solution has the following characteristics and benefits:

 The shared RAN connects to the CNs of multiple operators.

 The shared RAN automatically routes UEs to the subscriber's CNs.

 The MOCN solution has the following limitations:

 Operators need to cooperate more closely because of decreased independence.