RAN14.0 Feature Activation Guide

RAN14.
Feature Activation Guide

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

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 06 (2013-03-25)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
RAN14.0
About This Document
About This Document

Purpose
This document provides guidelines for enabling or disabling a feature after initial configuration.
Based on the activation, verification, and deactivation of a feature in the feature list, the
guidelines aim to ensure that the feature is available on the network.
This document describes how to activate a license and configure a feature in RAN.
NOTE
The BSC6900 is used as an example to describe the network controller in this document.
Product Version
The solution version is RAN14.0 related to this document, for more details you can refer to the
following table.
Product Name
Product Version
BSC6900
V900R014C00
NodeB
V100R014
NodeB
V200R014
Intended Audience
This document is intended for:
l
Technical support engineers
Maintenance engineers
Field engineers
Network optimization engineers
Organization
1 Changes in the RAN Feature Activation Guide
Issue 06 (2013-03-25)

ii
RAN14.0
About This Document
This chapter describes the changes in the RAN Feature Activation Guide.
2 Feature Activation and License Item Descriptions
RANFeatures are classified into basic and optional features. Basic features are not licensecontrolled and therefore do not require license activation before use. Some optional features are
license-controlled and therefore require license activation before use. If the Configuration
Method column for a basic feature in the RAN basic feature list is None, enabling this feature
does not involve any configurations. If the Configuration Method column for an optional feature
in the RAN optional feature list is None, this feature is enabled once it is activated.
3 Overview of Configurations on the CME
This section provides an overview of the configuration on the CME. The CME is a configuration
tool on GUIs assisting you to effectively configure the data about wireless NE features. You can
reconfigure configuration parameters by using the configuration expresses provided by the CME
to activate or deactivate specified features.
4 Activating the UMTS License
In the case of certain UMTS features, a license control item is defined for each feature. The
license control item of a feature must be activated before the configuration and use of the feature.
The license control items related to the RNC can be activated on the M2000 or RNC LMT,
whereas those related to the NodeB can be activated only on the M2000.
5 Configuring 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer
Establishment and Release
This section describes how to activate, verify, and deactivate the basic feature WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release.
6 Configuring Conversational QoS Class
Conversational QoS Class.
7 Configuring Streaming QoS Class
Streaming QoS Class.
8 Configuring Interactive QoS Class
Interactive QoS Class.
9 Configuring Background QoS Class
Background QoS Class.
10 Configuring Emergency Call
Emergency Call.
11 Configuring RAB Quality of Service Renegotiation over Iu Interface
RAB Quality of Service Renegotiation over Iu Interface.
Issue 06 (2013-03-25)

iii
RAN14.0
About This Document
12 Configuring 2-Way Antenna Receive Diversity

This section describes how to activate, verify, and deactivate the basic feature MRFD-210604
2-Way Antenna Receive Diversity.
13 Configuring Cell Digital Combination and Split
Cell Digital Combination and Split.
14 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH,
CELL_FACH)
UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).
15 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1).
16 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2)
Paging UE in CELL_FACH, CELL_DCH State (Type 2).
17 Configuring Dynamic Channel Configuration Control
Dynamic Channel Configuration Control (DCCC). (This feature cannot be configured using the
CME. )
18 Configuring Integrity Protection
Integrity Protection.
19 Configuring Encryption
Encryption.
20 Configuring Open Loop Power Control
Open Loop Power Control.
21 Configuring Downlink Power Balance
Downlink Power Balance.
22 Configuring Outer Loop Power Control
Outer Loop Power Control.
23 Configuring Inner Loop Power Control
Inner Loop Power Control.
Issue 06 (2013-03-25)

iv
RAN14.0
About This Document
24 Configuring Admission Control

Admission Control.
25 Configuring Load Measurement
Load Measurement.
26 Configuring Load Reshuffling
Load Reshuffling.
27 Configuring Overload Control
Overload Control.
28 Configuring Code Resource Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-020108
Code Resource Management.
29 Configuring Potential User Control
Potential User Control.
30 Configuring Cell Barring
Cell Barring.
31 Configuring Shared Network Support in Connected Mode
Shared Network Support in Connected Mode. (This feature cannot be configured using the
CME. )
32 Configuring Intra NodeB Softer Handover
Intra NodeB Softer Handover.
33 Configuring Intra RNC Soft Handover
Intra RNC Soft Handover.
34 Configuring Inter RNC Soft Handover
Inter RNC Soft Handover.
35 Configuring Intra Frequency Hard Handover
Intra Frequency Hard Handover.
36 Configuring Intra RNC Cell Update
Issue 06 (2013-03-25)

RAN14.0
About This Document
Intra RNC Cell Update.
37 Configuring Inter RNC Cell Update
Inter RNC Cell Update.
38 Configuring Intra RNC URA Update
Intra RNC URA Update.
39 Configuring Inter RNC URA Update
Inter RNC URA Update.
40 Configuring Direct Signaling Connection Re-establishment (DSCR)
Direct Signaling Connection Re-establishment (DSCR).
41 Configuring CS Fallback Guarantee for LTE Emergency Calls
CS Fallback Guarantee for LTE Emergency Calls. For details about how to configure this feature
on the LTE side, see the related documents provided by the LTE equipment vendor.
42 Configuring NodeB Clock
NodeB Clock.
43 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.
44 Configuring Permanent AAL5 Connections for Control Plane Traffic
Permanent AAL5 Connections for Control Plane Traffic.
45 Configuring Call Admission Based on Used AAL2 Path Bandwidth
Call Admission Based on Used AAL2 Path Bandwidth.
46 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
This section describes how to activate, verify, and deactivate the basic feature
"WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes".
47 Configuring F5
F5. (This feature cannot be configured using the CME. )
48 Configuring UBR+ ATM QoS Class
This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305
UBR+ ATM QoS Class".
Issue 06 (2013-03-25)

vi
RAN14.0
About This Document
49 Configuring Link Aggregation

Link Aggregation.
50 Configuring Flow Control
Flow Control.
51 Configuring BOOTP
BOOTP. In ATM transport mode, the NodeB can automatically set up the OM channel with the
BSC6900 by using the BOOTSTRAP Protocol (BOOTP) function.
52 Configuring NodeB Self-Discovery Based on IP Mode
NodeB Self-Discovery Based on IP Mode.
53 Configuring License Control for Urgency
License Control for Urgency. (This feature cannot be configured using the CME. )
54 Configuring Intelligently Out of Service
Intelligently Out of Service.
55 Configuring OCNS
OCNS (Orthogonal Channel Noise Simulator). (This feature cannot be configured using the
CME. )
56 Configuring Power Off the Equipment Level by Level
Power Off the Equipment Level by Level.
57 Configuring Solar Power Device Management
Solar Power Device Management.
58 Configuring Connection with TMA (Tower Mounted Amplifier)
Connection with TMA (Tower Mounted Amplifier). (This feature cannot be configured using
the CME. )
59 Configuring Remote Electrical Tilt
Remote Electrical Tilt. (This feature cannot be configured using the CME. )
60 Configuring Same Band Antenna Sharing Unit (900 MHz)
Issue 06 (2013-03-25)

vii
RAN14.0
About This Document
Configuring Same Band Antenna Sharing Unit (900 MHz). (This feature cannot be configured
using the CME. )
61 Configuring VoIP over HSPA/HSPA+
VoIP over HSPA/HSPA+.
62 Configuring Optimized Scheduling for VoIP over HSPA
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061703 Optimized Scheduling for VoIP over HSPA.
63 Configuring IMS Signaling over HSPA
IMS Signaling over HSPA.
64 Configuring PDCP Header Compression (RoHC)
PDCP Header Compression (RoHC).
65 Configuring CS Voice over HSPA/HSPA+
CS Voice over HSPA/HSPA+.
66 Configuring AMR-WB (Adaptive Multi Rate Wide Band)
AMR-WB (Adaptive Multi Rate Wide Band). (This feature cannot be configured using the
CME. )
67 Configuring AMR/WB-AMR Speech Rates Control
AMR/WB-AMR Speech Rates Control.
68 Configuring TFO/TrFO
TFO/TrFO.
69 Configuring AMR Voice Quality Improvement Based on PLVA
AMR Voice Quality Improvement Based on PLVA.
70 Configuring Cell Broadcast Service
Cell Broadcast Service.
71 Configuring Simplified Cell Broadcast
Simplified Cell Broadcast.
72 Configuring Warning of Disaster
Issue 06 (2013-03-25)

viii
RAN14.0
About This Document
Warning of Disaster.
73 Configuring MBMS Introduction Package
MBMS Introduction Package.
74 Configuring MBMS Admission Control
WRFD-01061602 MBMS Admission Control.
75 Configuring MBMS Load Control
WRFD-01061603 MBMS Load Control.
76 Configuring MBMS Transport Resource Management
WRFD-01061605 MBMS Transport Resource Management.
77 Configuring Streaming Service on MBMS
WRFD-01061606 Streaming Service on MBMS.
78 Configuring 16/32/64/128Kbps Channel Rate on MBMS
WRFD-01061608 16/32/64/128Kbps Channel Rate on MBMS.
79 Configuring MBMS Phase 2
MBMS Phase 2.
80 Configuring MBMS Enhanced Broadcast Mode
WRFD-01066001 MBMS Enhanced Broadcast Mode.
81 Configuring MBMS P2P over HSDPA
WRFD-01066002 MBMS P2P over HSDPA.
82 Configuring MBMS Admission Enhancement
WRFD-01066003 MBMS Admission Enhancement.
83 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users
WRFD-01066004 Inter-Frequency Neighboring Cell Selection for MBMS PTP Users.
84 Configuring FACH Transmission Sharing for MBMS
FACH Transmission Sharing for MBMS.
Issue 06 (2013-03-25)

ix
RAN14.0
About This Document
85 Configuring MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer

Dispersion)
MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion).
86 Configuring MBMS over Iur
MBMS over Iur.
87 Configuring Dynamic Power Estimation for MTCH
Dynamic Power Estimation for MTCH.
88 Configuring MSCH Scheduling
MSCH Scheduling.
89 Configuring MBMS Channel Audience Rating Statistics
MBMS Channel Audience Rating Statistics.
90 Configuring Cell ID + RTT Function Based LCS
Cell ID + RTT Function Based LCS.
91 Configuring OTDOA Based LCS
OTDOA Based LCS.
92 Configuring A-GPS Based LCS
A-GPS Based LCS. (This feature cannot be configured using the CME. )
93 Configuring LCS Classified Zones
LCS Classified Zones.
94 Configuring LCS over Iur
LCS over Iur.
95 Configuring Iupc Interface for LCS Service
Iupc Interface for LCS service.
96 Configuring Push to Talk
Push to Talk. (This feature cannot be configured using the CME. )
97 Configuring HSUPA Introduction Package
Issue 06 (2013-03-25)

RAN14.0
About This Document
HSUPA Introduction Package.
98 Configuring HSUPA Admission Control
WRFD-01061202 HSUPA Admission Control.
99 Configuring HSUPA Power Control
WRFD-01061203 HSUPA Power Control.
100 Configuring HSUPA Mobility Management
WRFD-01061204 HSUPA Mobility Management.
101 Configuring HSUPA DCCC
WRFD-01061208 HSUPA DCCC.
102 Configuring 20 HSUPA Users per Cell
WRFD-01061211 20 HSUPA Users per Cell.
103 Configuring HSUPA Iub Flow Control in Case of Iub Congestion
WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion.
104 Configuring HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH)
WRFD-01061401 HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH).
105 Configuring HSUPA 2ms TTI
WRFD-01061403 HSUPA 2ms TTI.
106 Configuring HSUPA 2 ms/10 ms TTI Handover
WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover.
107 Configuring HSUPA 5.74Mbps per User
WRFD-01061405 HSUPA 5.74Mbps per User.
108 Configuring Streaming Traffic Class on HSUPA
Streaming Traffic Class on HSUPA.
109 Configuring HSUPA over Iur
HSUPA over Iur.
Issue 06 (2013-03-25)

xi
RAN14.0
About This Document
110 Configuring TTI Switch for BE Services Based on Coverage

TTI Switch for BE Services Based on Coverage.
111 Configuring HSUPA Adaptive Transmission
HSUPA Adaptive Transmission.
112 Configuring Dynamic CE Resource Management
Dynamic CE Resource Management.
113 Configuring HSUPA FDE
HSUPA FDE.
114 Configuring Adaptive Configuration of Traffic Channel Power offset for HSUPA
Adaptive Configuration of Traffic Channel Power offset for HSUPA.
115 Configuring Anti-Interference Scheduling for HSUPA
Anti-Interference Scheduling for HSUPA.
116 Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation
Dual-Threshold Scheduling with HSUPA Interference Cancellation.
60 HSUPA Users per Cell.
118 Configuring HSUPA UL Interference Cancellation
HSUPA UL Interference Cancellation.
119 Configuring SRB over HSUPA
SRB over HSUPA.
120 Configuring Control Channel Parallel Interference Cancellation (Phase 2)
Control Channel Parallel Interference Cancellation (Phase 2). Control Channel Parallel
Interference Cancellation is short for CCPIC.
121 Configuring HSDPA Introduction Package
HSDPA Introduction Package. (This feature cannot be configured using the CME. )
122 Configuring 15 Codes per Cell
Issue 06 (2013-03-25)

xii
RAN14.0
About This Document
WRFD-01061001 15 Codes per Cell.
123 Configuring Time and HS-PDSCH Codes Multiplex
WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
124 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).
125 Configuring HSDPA Static Code Allocation and RNC-Controlled Dynamic Code
Allocation
WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code
Allocation.
126 Configuring HSDPA Power Control
WRFD-01061004 HSDPA Power Control.
127 Configuring HSDPA Admission Control
WRFD-01061003 HSDPA Admission Control.
128 Configuring Improvement of User Experience in Low Traffic Service
WRFD-01061020 Improvement of User Experience in Low Traffic Service.
129 Configuring HSDPA Flow Control
WRFD-01061010 HSDPA Flow Control.
130 Configuring HSDPA Mobility Management
WRFD-01061006 HSDPA Mobility Management.
131 Configuring HSDPA UE Category 1 to 28
WRFD-01061002 HSDPA UE Category 1 to 28.
132 Configuring DL 16QAM Modulation
DL 16QAM Modulation.
133 Configuring Dynamic Code Allocation Based on NodeB
Dynamic Code Allocation Based on NodeB.
134 Configuring HSDPA Enhanced Package
Issue 06 (2013-03-25)

xiii
RAN14.0
About This Document
HSDPA Enhanced Package.
135 Configuring Scheduling based on EPF and GBR
WRFD-01061103 Scheduling based on EPF and GBR.
136 Configuring HSDPA State Transition
WRFD-01061111 HSDPA State Transition.
137 Configuring HSDPA DRD
WRFD-01061112 HSDPA DRD.
138 Configuring HS-DPCCH Preamble Support
WRFD-01061113 HS-DPCCH Preamble Support.
139 Configuring Streaming Traffic Class on HSDPA
Streaming Traffic Class on HSDPA.
140 Configuring HSDPA over Iur
HSDPA over Iur.
141 Configuring SRB over HSDPA
SRB over HSDPA.
142 Configuring CQI Adjustment Based on Dynamic BLER Target
CQI Adjustment Based on Dynamic BLER Target.
143 Configuring MIMO Prime
This chapter describes how to activate, verify, and deactivate the basic feature WRFD-030011
MIMO Prime.
144 Configuring Adaptive Configuration of Typical HSPA Rate
Adaptive Configuration of Typical HSPA Rate.
145 Configuring HSDPA Scheduling Based on UE Location
HSDPA Scheduling Based on UE Location.
146 Configuring Adaptive Adjustment of HSUPA Small Target Retransmissions
This section describes how to activate, verify, and deactivate the try feature WRFD-140222
Adaptive Adjustment of HSUPA Small Target Retransmissions.
Issue 06 (2013-03-25)

xiv
RAN14.0
About This Document
147 Configuring HSPA+ Downlink 28Mbps per User

HSPA+ Downlink 28Mbps per User.
149 Configuring Downlink Enhanced L2
Downlink Enhanced L2.
151 Configuring Downlink 64QAM
Downlink 64QAM.
152 Configuring 2x2 MIMO
2x2 MIMO. Multiple Input Multiple Output (MIMO) is a multi-antenna technology, which
enables multiple antennas to receive and transmit data. This increases the data transmission rate.
153 Configuring Downlink 64QAM+MIMO
DL 64QAM+MIMO.
154 Configuring HSPA+ Uplink 11.5Mbit/s per User
HSPA+ Uplink 11.5Mbit/s per User.
155 Configuring HSPA+ Downlink 84 Mbit/s per User
HSPA+ Downlink 84 Mbit/s per User.
156 Configuring DC-HSDPA+MIMO
DC-HSDPA+MIMO.
157 Configuring UL 16QAM
UL 16QAM.
158 Configuring UL Layer 2 Improvement
UL Layer 2 Improvement.
159 Configuring DC-HSDPA
Issue 06 (2013-03-25)

xv
RAN14.0
About This Document
DC-HSDPA.
160 Configuring HSPA+ Uplink 23 Mbit/s per User
HSPA+ Uplink 23 Mbit/s per User.
161 Configuring DC-HSUPA
DC-HSUPA.
162 Configuring Downlink Enhanced CELL_FACH
Downlink Enhanced CELL_FACH.
163 Configuring Performance Improvement of MIMO and HSDPA Co-carrier
Performance Improvement of MIMO and HSDPA Co-carrier.
164 Configuring CPC - DTX /DRX
CPC - DTX /DRX.
165 Configuring CPC - HS-SCCH less operation
CPC - HS-SCCH less operation.
166 Configuring E-DPCCH Boosting
E-DPCCH Boosting.
167 Configuring Uplink Enhanced CELL_FACH
Uplink Enhanced CELL_FACH.
168 Configuring 96 HSDPA Users per Cell
96 HSDPA Users per Cell.
Issue 06 (2013-03-25)

xvi
RAN14.0
About This Document
172 Configuring Flexible HSPA+ Technology Selection

Flexible HSPA+ Technology Selection.
173 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier
In Multi-carrier
Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier.
174 Configuring Enhanced DRX
Enhanced DRX. (This feature cannot be configured using the CME. )
175 Configuring Enhanced Fast Dormancy
Enhanced Fast Dormancy. (This feature cannot be configured using the CME. )
176 Configuring Voice Service Experience Improvement for Weak Reception UEs
Voice Service Experience Improvement for Weak Reception UEs.
177 Configuring Layered Paging in URA_PCH
Layered Paging in URA_PCH.
178 Configuring Web browsing acceleration
Web browsing acceleration. (This feature cannot be configured using the CME. )
179 Configuring P2P Downloading Rate Control during Busy Hour
P2P Downloading Rate Control during Busy Hour. (This feature cannot be configured using the
CME. )
180 Configuring Dynamic Power Sharing of Multi-Carriers
Dynamic Power Sharing of Multi-Carriers.
181 Configuring Multi-Carrier Switch off Based on Traffic Load
Multi-Carrier Switch off Based on Traffic Load.
182 Configuring Energy Efficiency Improved
Energy Efficiency Improved.
183 Configuring Multi-Carrier Switch off Based on Power Backup
Multi-Carrier Switch off Based on Power Backup.
Issue 06 (2013-03-25)

xvii
RAN14.0
About This Document
184 Configuring Multi-Carrier Switch off Based on QoS

Multi-Carrier Switch off Based on QoS.
185 Configuring Intelligent Power Management
Intelligent Power Management.
186 Configuring RAN Sharing Introduction Package
This section describes how to activate, verify and deactivate the optional feature WRFD-021304
RAN Sharing Introduction Package.
187 Configuring Dedicated Carrier for Each Operator
WRFD-02130401 Dedicated Carrier for Each Operator.
188 Configuring Flexible Network Architecture
WRFD-02130402 Flexible Network Architecture.
189 Configuring Mobility Control and Service Differentiation
WRFD02130403 Mobility Control and Service Differentiation.
190 Configuring Independent License Control
WRFD-02130404 Independent License Control. (This feature cannot be configured using the
CME. )
191 Configuring RAN Sharing Phase 2
RAN Sharing Phase 2.
192 Configuring Dedicated Iub Transmission Control
WRFD-02130501 Dedicated Iub Transmission Control.
193 Configuring IMSI Based Handover
IMSI Based Handover.
194 Configuring MOCN Introduction Package
MOCN Introduction Package. (This feature cannot be configured using the CME. )
195 Configuring Carrier Sharing by Operators
WRFD-02131101 Carrier Sharing by Operators.
196 Configuring Dedicated NodeB/Cell for Operators
Issue 06 (2013-03-25)

xviii
RAN14.0
About This Document
WRFD-02131102 Dedicated NodeB/Cell for Operators.
197 Configuring MOCN Mobility Management
WRFD-02131103 MOCN Mobility Management.
198 Configuring MOCN Load Balance
WRFD-02131104 MOCN Load Balance.
199 Configuring Routing Roaming UEs in Proportion
WRFD-02131106 Routing Roaming UEs in Proportion.
200 Configuring MOCN Cell Resource Demarcation
MOCN Cell Resource Demarcation.
201 Configuring HCS (Hierarchical Cell Structure)
HCS (Hierarchical Cell Structure).
202 Configuring One Tunnel
One Tunnel.
203 Configuring Overbooking on ATM Transmission
Overbooking on ATM Transmission.
204 Configuring ATM Switching-Based Hub NodeB
ATM Switching-Based Hub NodeB.
205 Configuring AAL2 Switching-Based Hub NodeB
AAL2 Switching-Based Hub NodeB.
206 Configuring IP Transmission Introduction on Iub Interface
IP Transmission Introduction on Iub Interface. (This feature cannot be configured using the
CME. )
207 Configuring Hybrid Iub IP Transmission
Hybrid Iub IP Transmission.
208 Configuring ATM/IP Dual Stack NodeB
ATM/IP Dual Stack NodeB.
Issue 06 (2013-03-25)

xix
RAN14.0
About This Document
209 Configuring IP Transmission Introduction on Iu Interface

IP Transmission Introduction on Iu Interface.
210 Configuring IP Transmission Introduction on Iur Interface
IP Transmission Introduction on Iur Interface.
211 Configuring FP MUX for IP Transmission
Configuring FP MUX for IP Transmission.
212 Configuring Dynamic Bandwidth Control of Iub IP
Dynamic Bandwidth Control of Iub IP.
213 Configuring Overbooking on IP Transmission
Overbooking on IP Transmission.
214 Configuring IP Routing-Based Hub NodeB
IP Routing-Based Hub NodeB.
215 Configuring PDCP Header Compression (RFC2507)
PDCP Header Compression (RFC2507).
216 Configuring RNC Offload
RNC Offload. With this feature, the RNC can send some PS service data directly to Internet
over the offload Gi interface.
217 Configuring UDP MUX for Iu-CS Transmission
This section describes how to activate, verify, and deactivate the feature WRFD-050412 UDP
MUX for Iu-CS Transmission.
218 Configuring Iu/Iur Transmission Resource Pool in RNC
Iu/Iur Transmission Resource Pool in RNC.
219 Configuring Iub Transmission Resource Pool in RNC
Iub Transmission Resource Pool in RNC.
220 Configuring Satellite Transmission on Iub Interface
Satellite Transmission on Iub Interface.
221 Configuring Satellite Transmission on Iu Interface
Issue 06 (2013-03-25)

xx
RAN14.0
About This Document
Satellite Transmission on Iu Interface.
222 Configuring Clock Synchronization on Ethernet in NodeB
Clock Synchronization on Ethernet in NodeB.
223 Configuring Synchronous Ethernet
Synchronous Ethernet.
224 Configuring Ethernet OAM
Ethernet OAM. (This feature cannot be configured using the CME. )
225 Configuring RNC Node Redundancy
RNC Node Redundancy.
226 Configuring RRU Redundancy
RRU Redundancy.
227 Configuring Iu Flex
Iu Flex.
228 Configuring Iu Flex Load Distribution Management
Iu Flex Load Distribution Management.
229 Configuring Transmit Diversity
Transmit Diversity. Transmit diversity enables the NodeB to provide twice the number of RF
DL channels compared with no transmit diversity.
230 Configuring 4-Antenna Receive Diversity
4-Antenna Receive Diversity.
231 Configuring Extended Cell Coverage up to 200km
Extended Cell Coverage up to 200km.
232 Configuring HSUPA Coverage Enhancement at UE Power Limitation
HSUPA Coverage Enhancement at UE Power Limitation.
233 Configuring Flexible frequency bandwidth of UMTS carrier
Flexible frequency bandwidth of UMTS carrier.
Issue 06 (2013-03-25)

xxi
RAN14.0
About This Document
234 Configuring High Speed Access

High Speed Access.
235 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell
Independent Demodulation of Signals from Multiple RRUs in One Cell.
236 Configuring Inter Frequency Hard Handover Based on Coverage
Inter Frequency Hard Handover Based on Coverage.
237 Configuring Inter Frequency Hard Handover Based on DL QoS
Inter Frequency Hard Handover Based on DL QoS.
238 Configuring SRNS Relocation (UE Not Involved)
WRFD-02060501 SRNS Relocation (UE Not Involved). (This feature cannot be configured
using the CME. )
239 Configuring SRNS Relocation with Hard Handover
WRFD-02060502 SRNS Relocation with Hard Handover.
240 Configuring SRNS Relocation with Cell/URA Update
WRFD-02060503 SRNS Relocation with Cell/URA Update.
241 Configuring Multiple RAB Package (PS RAB 2)
Multiple RAB Package (PS RAB 2).
242 Configuring Combination of Two PS Services
WRFD-01061501 Combination of Two PS Services.
243 Configuring Combination of One CS Service and Two PS Services
WRFD-01061502 Combination of One CS Service and Two PS Services.
244 Configuring Combination of Three PS Services
WRFD-01061503 Combination of Three PS Services.
245 Configuring Combination of One CS Service and Three PS Services
WRFD-01061504 Combination of One CS Service and Three PS Services.
246 Configuring Combination of Four PS Services
Issue 06 (2013-03-25)

xxii
RAN14.0
About This Document
WRFD-01061505 Combination of Four PS Services.
247 Configuring Inter Frequency Load Balance
Inter Frequency Load Balance.
248 Configuring Domain Specific Access Control (DSAC)
Domain Specific Access Control (DSAC).
249 Configuring Multi Frequency Band Networking Management
Multi Frequency Band Networking Management.
250 Configuring Enhanced Multiband Management
Enhanced Multiband Management.
251 Configuring DRD Introduction Package
DRD Introduction Package.
252 Configuring Intra System Direct Retry
WRFD-02040001 Intra System Direct Retry.
253 Configuring Inter System Direct Retry
WRFD-02040002 Inter System Direct Retry.
254 Configuring Inter-System Redirect
WRFD-02040003 Inter System Redirect.
255 Configuring Traffic Steering and Load Sharing During RAB Setup
WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup.
256 Configuring Measurement Based Direct Retry
Measurement Based Direct Retry.
257 Configuring Service Steering and Load Sharing in RRC Connection Setup
Service Steering and Load Sharing in RRC Connection Setup.
258 Configuring Uplink Flow Control of User Plane
Uplink Flow Control of User Plane.
Issue 06 (2013-03-25)

xxiii
RAN14.0
About This Document
259 Configuring Intra Frequency Load Balance

Intra Frequency Load Balance.
260 Configuring Dynamic Target ROT Adjustment
Dynamic Target RoT Adjustment.
261 Configuring CE Overbooking
CE Overbooking.
262 Configuring Intelligent Access Class Control
Intelligent Access Class Control.
263 Configuring Dynamic Configuration of HSDPA CQI Feedback Period
Dynamic Configuration of HSDPA CQI Feedback Period.
264 Configuring Load-based Uplink Target BLER Configuration
Load-based Uplink Target BLER Configuration.
265 Configuring Inter-Frequency Load Balancing Based on Configurable Load Threshold
Inter-Frequency Load Balancing Based on Configurable Load Threshold.
266 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g
Load Based GSM and UMTS Handover Enhancement Based on Iur-g.
267 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based
on Iur-g
NACC Procedure Optimization Based on Iur-g.
268 Configuring GSM and UMTS Load Balancing Based on Iur-g
GSM and UMTS Load Balancing Based on Iur-g.
269 Configuring GSM and UMTS Traffic Steering Based on Iur-g
GSM and UMTS Traffic Steering Based on Iur-g.
270 Configuring Inter-RAT Handover Based on Coverage
Inter-RAT Handover Based on Coverage.
271 Configuring Inter-RAT Handover Based on DL QoS
Issue 06 (2013-03-25)

xxiv
RAN14.0
About This Document
Inter-RAT Handover Based on DL QoS.
272 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
273 Configuring Inter-RAT Handover Phase 2
Inter-RAT Handover Phase 2.
274 Configuring NACC(Network Assisted Cell Change)
WRFD-02030801 NACC(Network Assisted Cell Change).
275 Configuring PS Handover between UMTS and GPRS
WRFD-02030802 PS Handover between UMTS and GPRS.
276 Configuring Inter-RAT Handover Based on Service
Inter-RAT Handover Based on Service.
277 Configuring Inter-RAT Handover Based on Load
Inter-RAT Handover Based on Load.
278 Configuring Inter-RAT Redirection Based on Distance
This section describes how to activate and verify the optional feature WRFD-020401 Inter-RAT
Redirection Based on Distance.
279 Configuring 3G/2G Common Load Management
3G/2G Common Load Management.
280 Configuring Mobility Between UMTS and LTE Phase 1
Mobility Between UMTS and LTE Phase 1. For details about how to configure this feature on
the LTE side, see the related documents provided by the LTE equipment vendor. (This feature
cannot be configured using the CME. )
281 Configuring Service-Based PS Service Redirection from UMTS to LTE
Service-Based PS Service Redirection from UMTS to LTE.
282 Configuring Service-Based PS Handover from UMTS to LTE
Service-Based PS Handover from UMTS to LTE.
283 Configuring Fast CS Fallback Based on RIM
Issue 06 (2013-03-25)

xxv
RAN14.0
About This Document
fast CS fallback based on RIM. For details about how to configure this feature on the LTE side,
see the related documents provided by the LTE equipment vendor.
284 Configuring Queuing and Preemption
Queuing and Preemption.
285 Configuring Access Class Restriction
Access Class Restriction.
286 Configuring Traffic Priority Mapping onto Transmission Resources
Traffic Priority Mapping onto Transmission Resources.
287 Configuring Differentiated Service Based on SPI Weight
Differentiated Service Based on SPI Weight.
288 Configuring Optimization of R99 and HSUPA Users Fairness
Optimization of R99 and HSUPA Users Fairness.
289 Configuring Active Queue Management (AQM)
Active Queue Management (AQM).
290 Configuring Quality Improvement for Subscribed Service
Quality Improvement for Subscribed Service.
291 Configuring TCP Accelerator
TCP Accelerator.
292 Configuring Rate Negotiation at Admission Control
Rate Negotiation at Admission Control.
293 Configuring Videophone Service Restriction
Videophone Service Restriction.
294 Configuring Intelligent Inter-Carrier UE Layered Management
Intelligent Inter-Carrier UE Layered Management.
295 Configuring Micro NodeB Self-Planning
Micro NodeB Self-Planning.
Issue 06 (2013-03-25)

xxvi
RAN14.0
About This Document
296 Configuring NodeB Integrated IPSec

NodeB Integrated IPSec.
297 Configuring NodeB PKI Support
NodeB PKI Support. (This feature cannot be configured using the CME. )
298 Configuring Intelligent Battery Management
Intelligent Battery Management. (This feature cannot be configured using the CME. )
299 Configuring Multi-mode Dynamic Power Sharing (UMTS)
This section describes how to activate, verify, and deactivate the optional feature MRFD-221801
Multi-mode Dynamic Power Sharing (UMTS).
300 Configuring GSM and UMTS Dynamic Spectrum Sharing (UMTS)
GSM and UMTS Dynamic Spectrum Sharing (UMTS). This feature enables the spectrum
resources to be dynamically shared between the GSM and UMTS networks based on their traffic
load, improving frequency utilization.
301 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB)
IP-Based Multi-Mode Co-Transmission on Base Station Side. For details about data
configurations, see section Configuration Reference > MBTS Configuration Reference
(V100R007C00) > Common Transmission in the 3900 Series Base Station Initial
Configuration Guide, or see section Common Transmission in the WCDMA RAN Feature
Documentation. The latest 3900 Series Base Station Initial Configuration Guide can be obtained
from the following path: HUAWEI Technical Support (support.huawei.com), Support >
Documentation > SingleRAN > MBTS > SingleRAN7.0.
302 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side
(NodeB)
TDM-Based Multi-mode Co-Transmission via Backplane on BS side (NodeB). (This feature
303 Configuring Multi-Mode BS Common Reference Clock (NodeB)
Multi-Mode BS Common Reference Clock (NodeB). For details about data configurations, see
section Configuration Reference > MBTS Configuration Reference (V100R007C00) >
Common Clock in the 3900 Series Base Station Initial Configuration Guide, or see section
Common Clock in the WCDMA RAN Feature Documentation. The latest 3900 Series Base
Station Initial Configuration Guide can be obtained from the following path: HUAWEI
Technical Support (support.huawei.com), Support > Documentation > SingleRAN > MBTS
> SingleRAN7.0.
304 Multi-mode BS Common IPSec(UMTS)
This section describes how to activate, verify, and deactivate the multi-mode feature
MRFD-221602 Multi-mode BS Common IPSec(UMTS).
Issue 06 (2013-03-25)

xxvii
RAN14.0
About This Document
305 Configuring 2.0MHz Central Frequency point separation between GSM and UMTS
mode(UMTS)
2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS).
306 Configuring Dynamic MA for GU Dynamic Spectrum Sharing (UMTS)
MRFD-221803 Dynamic MA for GU Dynamic Spectrum Sharing(UMTS).
307 Configuring GSM Power Control on Interface Frequency for GU Small Frequency
Gap (UMTS)
MRFD-221804 GSM Power Control on Interference Frequency for GU Small Frequency gap
(UMTS).
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Issue 06 (2013-03-25)
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.

xxviii
RAN14.0
About This Document
Convention
Description
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Issue 06 (2013-03-25)
Format
Description
Key
Press the key. For example, press Enter and press Tab.
xxix
RAN14.0
About This Document
Format
Description
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 06 (2013-03-25)
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

xxx
RAN14.0
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in the RAN Feature Activation Guide......................................................................1
2 Feature Activation and License Item Descriptions...............................................................10
3 Overview of Configurations on the CME...............................................................................54
3.1 Introduction to Configuration Methods............................................................................................................56
3.2 Configuring Device Data..................................................................................................................................57
3.3 Introduction to the Configuration Express for UMTS Global Parameters.......................................................58
3.4 Introduction to the Configuration Express for Iub Interfaces...........................................................................59
3.5 Introduction to the Configuration Express for Iu-CS Interfaces......................................................................60
3.6 Introduction to the Configuration Express for Iu-PS Interfaces.......................................................................61
3.7 Introduction to the Configuration Express for Iur Interfaces...........................................................................62
3.8 Introduction to the Configuration Express for Iu-BC Interfaces......................................................................63
3.9 Introduction to the Configuration Express for Iu-PC Interfaces......................................................................64
3.10 Introduction to the Configuration Express for the (U)Iur-g Interface............................................................65
3.11 Introduction to the Configuration Express for Gi Interfaces..........................................................................66
3.12 Introduction to the Configuration Express for UMTS Global Radio Parameters..........................................67
3.13 Introduction to the Configuration Express for UMTS Cells..........................................................................68
3.14 Introduction to the Configuration Express for Neighboring UMTS Cells.....................................................69
3.15 Modifying RNC Parameters in Batches.........................................................................................................70
3.16 Modifying Logical NodeB Parameters in Batches.........................................................................................70
3.17 Modifying Physical NodeB Parameters in Batches........................................................................................71
3.18 Modifying UMTS Cell Parameters in Batches...............................................................................................71
3.19 Modifying RNC External Cell Parameters in Batches...................................................................................72
3.20 Modifying UMTS Channel Parameters in Batches........................................................................................73
3.21 Introduction to the Object Group Configuration............................................................................................74
4 Activating the UMTS License...................................................................................................76

4.1 Activating the BSC6900 License.....................................................................................................................77
4.2 Allocating a license to Telecom Operators.......................................................................................................78
4.3 Allocating a License to NodeBs.......................................................................................................................78
5 Configuring 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer

Establishment and Release...........................................................................................................80
Issue 06 (2013-03-25)

xxxi
RAN14.0
Contents
6 Configuring Conversational QoS Class .................................................................................83

7 Configuring Streaming QoS Class...........................................................................................86
8 Configuring Interactive QoS Class..........................................................................................89
9 Configuring Background QoS Class.......................................................................................91
10 Configuring Emergency Call...................................................................................................93
11 Configuring RAB Quality of Service Renegotiation over Iu Interface...........................94
12 Configuring 2-Way Antenna Receive Diversity..................................................................97
13 Configuring Cell Digital Combination and Split...............................................................99
14 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH,
CELL_FACH).................................................................................................................................102
15 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)......................105
16 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2)...........................109
17 Configuring Dynamic Channel Configuration Control..................................................111
18 Configuring Integrity Protection..........................................................................................120
19 Configuring Encryption.........................................................................................................122
20 Configuring Open Loop Power Control.............................................................................124
21 Configuring Downlink Power Balance...............................................................................127
22 Configuring Outer Loop Power Control.............................................................................129
23 Configuring Inner Loop Power Control .............................................................................132
24 Configuring Admission Control..........................................................................................134
25 Configuring Load Measurement..........................................................................................138
26 Configuring Load Reshuffling.............................................................................................140
27 Configuring Overload Control.............................................................................................144
28 Configuring Code Resource Management.........................................................................147
29 Configuring Potential User Control.....................................................................................149
30 Configuring Cell Barring.......................................................................................................151
31 Configuring Shared Network Support in Connected Mode..........................................156
32 Configuring Intra NodeB Softer Handover........................................................................159
33 Configuring Intra RNC Soft Handover...............................................................................161
34 Configuring Inter RNC Soft Handover...............................................................................163
35 Configuring Intra Frequency Hard Handover...................................................................165
Issue 06 (2013-03-25)

xxxii
RAN14.0
Contents
36 Configuring Intra RNC Cell Update....................................................................................168

37 Configuring Inter RNC Cell Update....................................................................................171
38 Configuring Intra RNC URA Update..................................................................................173
39 Configuring Inter RNC URA Update..................................................................................176
40 Configuring Direct Signaling Connection Re-establishment (DSCR) ........................179
41 Configuring CS Fallback Guarantee for LTE Emergency Calls.....................................182
42 Configuring NodeB Clock.....................................................................................................184
43 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface...........................188
44 Configuring Permanent AAL5 Connections for Control Plane Traffic........................190
45 Configuring Call Admission Based on Used AAL2 Path Bandwidth...........................192
46 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes........................................194
47 Configuring F5.........................................................................................................................196
48 Configuring UBR+ ATM QoS Class....................................................................................198
49 Configuring Link Aggregation.............................................................................................200
50 Configuring Flow Control.....................................................................................................204
51 Configuring BOOTP...............................................................................................................209
52 Configuring NodeB Self-Discovery Based on IP Mode..................................................211
53 Configuring License Control for Urgency..........................................................................215
54 Configuring Intelligently Out of Service...........................................................................217
55 Configuring OCNS.................................................................................................................219
56 Configuring Power Off the Equipment Level by Level...................................................221
57 Configuring Solar Power Device Management.................................................................224
58 Configuring Connection with TMA (Tower Mounted Amplifier)................................226
59 Configuring Remote Electrical Tilt......................................................................................229
60 Configuring Same Band Antenna Sharing Unit (900 MHz)...........................................232
61 Configuring VoIP over HSPA/HSPA+................................................................................235
62 Configuring Optimized Scheduling for VoIP over HSPA..............................................241
63 Configuring IMS Signaling over HSPA.............................................................................243
64 Configuring PDCP Header Compression (RoHC)............................................................246
65 Configuring CS Voice over HSPA/HSPA+........................................................................249
Issue 06 (2013-03-25)

xxxiii
RAN14.0
Contents
66 Configuring AMR-WB (Adaptive Multi Rate Wide Band).............................................254

67 Configuring AMR/WB-AMR Speech Rates Control........................................................257
68 Configuring TFO/TrFO..........................................................................................................262
69 Configuring AMR Voice Quality Improvement Based on PLVA.................................264
70 Configuring Cell Broadcast Service.....................................................................................266
71 Configuring Simplified Cell Broadcast..............................................................................276
72 Configuring Warning of Disaster.........................................................................................279
73 Configuring MBMS Introduction Package........................................................................281
74 Configuring MBMS Admission Control............................................................................285
75 Configuring MBMS Load Control.......................................................................................287
76 Configuring MBMS Transport Resource Management...................................................289
77 Configuring Streaming Service on MBMS........................................................................291
78 Configuring 16/32/64/128Kbps Channel Rate on MBMS.................................................293
79 Configuring MBMS Phase 2..................................................................................................295
80 Configuring MBMS Enhanced Broadcast Mode...............................................................297
81 Configuring MBMS P2P over HSDPA................................................................................299
82 Configuring MBMS Admission Enhancement.................................................................301
..........................................................................................................................................................303
84 Configuring FACH Transmission Sharing for MBMS....................................................304
85 Configuring MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer
Dispersion) ....................................................................................................................................306
86 Configuring MBMS over Iur.................................................................................................309
87 Configuring Dynamic Power Estimation for MTCH.......................................................311
88 Configuring MSCH Scheduling...........................................................................................313
89 Configuring MBMS Channel Audience Rating Statistics...............................................315
90 Configuring Cell ID + RTT Function Based LCS.............................................................317
91 Configuring OTDOA Based LCS.........................................................................................325
92 Configuring A-GPS Based LCS............................................................................................328
93 Configuring LCS Classified Zones......................................................................................336
94 Configuring LCS over Iur......................................................................................................339
Issue 06 (2013-03-25)

xxxiv
RAN14.0
Contents
95 Configuring Iupc Interface for LCS Service.......................................................................346

96 Configuring Push to Talk......................................................................................................349
97 Configuring HSUPA Introduction Package.......................................................................351
98 Configuring HSUPA Admission Control...........................................................................354
99 Configuring HSUPA Power Control ..................................................................................358
100 Configuring HSUPA Mobility Management...................................................................361
101 Configuring HSUPA DCCC................................................................................................363
102 Configuring 20 HSUPA Users per Cell.............................................................................366
103 Configuring HSUPA Iub Flow Control in Case of Iub Congestion............................368
104 Configuring HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH)...........370
105 Configuring HSUPA 2ms TTI.............................................................................................372
106 Configuring HSUPA 2 ms/10 ms TTI Handover.............................................................375
107 Configuring HSUPA 5.74Mbps per User..........................................................................377
108 Configuring Streaming Traffic Class on HSUPA...........................................................380
109 Configuring HSUPA over Iur.............................................................................................382
110 Configuring TTI Switch for BE Services Based on Coverage.......................................384
111 Configuring HSUPA Adaptive Transmission.................................................................388
112 Configuring Dynamic CE Resource Management..........................................................391
113 Configuring HSUPA FDE....................................................................................................393
114 Configuring Adaptive Configuration of Traffic Channel Power offset for HSUPA
..........................................................................................................................................................395
115 Configuring Anti-Interference Scheduling for HSUPA................................................403
116 Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation
..........................................................................................................................................................407
118 Configuring HSUPA UL Interference Cancellation.......................................................413
119 Configuring SRB over HSUPA...........................................................................................416
120 Configuring Control Channel Parallel Interference Cancellation (Phase 2).............418
121 Configuring HSDPA Introduction Package.....................................................................423
122 Configuring 15 Codes per Cell............................................................................................426
123 Configuring Time and HS-PDSCH Codes Multiplex....................................................429
Issue 06 (2013-03-25)

xxxv
RAN14.0
Contents
124 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).........................430
125 Configuring HSDPA Static Code Allocation and RNC-Controlled Dynamic Code
Allocation.......................................................................................................................................432
126 Configuring HSDPA Power Control ................................................................................434
127 Configuring HSDPA Admission Control.........................................................................437
128 Configuring Improvement of User Experience in Low Traffic Service......................440
129 Configuring HSDPA Flow Control....................................................................................442
130 Configuring HSDPA Mobility Management...................................................................445
131 Configuring HSDPA UE Category 1 to 28........................................................................447
132 Configuring DL 16QAM Modulation...............................................................................448
133 Configuring Dynamic Code Allocation Based on NodeB.............................................450
134 Configuring HSDPA Enhanced Package..........................................................................454
135 Configuring Scheduling based on EPF and GBR...........................................................456
136 Configuring HSDPA State Transition...............................................................................458
137 Configuring HSDPA DRD..................................................................................................460
138 Configuring HS-DPCCH Preamble Support...................................................................462
139 Configuring Streaming Traffic Class on HSDPA...........................................................465
140 Configuring HSDPA over Iur.............................................................................................467
141 Configuring SRB over HSDPA...........................................................................................469
142 Configuring CQI Adjustment Based on Dynamic BLER Target.................................473
143 Configuring MIMO Prime...................................................................................................475
144 Configuring Adaptive Configuration of Typical HSPA Rate......................................478
145 Configuring HSDPA Scheduling Based on UE Location..............................................480
..........................................................................................................................................................482
147 Configuring HSPA+ Downlink 28Mbps per User..........................................................485
149 Configuring Downlink Enhanced L2................................................................................489
151 Configuring Downlink 64QAM.........................................................................................495
152 Configuring 2x2 MIMO........................................................................................................499
Issue 06 (2013-03-25)

xxxvi
RAN14.0
Contents
153 Configuring Downlink 64QAM+MIMO..........................................................................509

154 Configuring HSPA+ Uplink 11.5Mbit/s per User...........................................................513
155 Configuring HSPA+ Downlink 84 Mbit/s per User.......................................................517
156 Configuring DC-HSDPA+MIMO......................................................................................519
157 Configuring UL 16QAM......................................................................................................524
158 Configuring UL Layer 2 Improvement..............................................................................527
159 Configuring DC-HSDPA.....................................................................................................531
160 Configuring HSPA+ Uplink 23 Mbit/s per User.............................................................537
161 Configuring DC-HSUPA.....................................................................................................540
162 Configuring Downlink Enhanced CELL_FACH.............................................................545
163 Configuring Performance Improvement of MIMO and HSDPA Co-carrier.............547
164 Configuring CPC - DTX /DRX............................................................................................552
165 Configuring CPC - HS-SCCH less operation...................................................................555
166 Configuring E-DPCCH Boosting........................................................................................558
167 Configuring Uplink Enhanced CELL_FACH...................................................................565
168 Configuring 96 HSDPA Users per Cell.............................................................................567
170 Configuring 128 HSDPA Users per Cell...........................................................................571
171 Configuring 128 HSUPA Users per Cell...........................................................................573
172 Configuring Flexible HSPA+ Technology Selection......................................................575
173 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier
In Multi-carrier..............................................................................................................................579
174 Configuring Enhanced DRX................................................................................................581
175 Configuring Enhanced Fast Dormancy.............................................................................584
..........................................................................................................................................................593
177 Configuring Layered Paging in URA_PCH......................................................................601
178 Configuring Web browsing acceleration..........................................................................604
179 Configuring P2P Downloading Rate Control during Busy Hour................................607
180 Configuring Dynamic Power Sharing of Multi-Carriers...............................................610
181 Configuring Multi-Carrier Switch off Based on Traffic Load......................................612
Issue 06 (2013-03-25)

xxxvii
RAN14.0
Contents
182 Configuring Energy Efficiency Improved........................................................................616

183 Configuring Multi-Carrier Switch off Based on Power Backup..................................618
184 Configuring Multi-Carrier Switch off Based on QoS....................................................622
185 Configuring Intelligent Power Management...................................................................626
186 Configuring RAN Sharing Introduction Package...........................................................628
187 Configuring Dedicated Carrier for Each Operator.........................................................632
188 Configuring Flexible Network Architecture....................................................................635
189 Configuring Mobility Control and Service Differentiation.........................................637
190 Configuring Independent License Control......................................................................639
191 Configuring RAN Sharing Phase 2....................................................................................641
192 Configuring Dedicated Iub Transmission Control........................................................642
193 Configuring IMSI Based Handover...................................................................................647
194 Configuring MOCN Introduction Package......................................................................649
195 Configuring Carrier Sharing by Operators......................................................................654
196 Configuring Dedicated NodeB/Cell for Operators.........................................................657
197 Configuring MOCN Mobility Management....................................................................660
198 Configuring MOCN Load Balance.....................................................................................662
199 Configuring Routing Roaming UEs in Proportion.........................................................664
200 Configuring MOCN Cell Resource Demarcation...........................................................667
201 Configuring HCS (Hierarchical Cell Structure)..............................................................673
202 Configuring One Tunnel.....................................................................................................676
203 Configuring Overbooking on ATM Transmission.........................................................681
204 Configuring ATM Switching-Based Hub NodeB...........................................................685
205 Configuring AAL2 Switching-Based Hub NodeB..........................................................687
206 Configuring IP Transmission Introduction on Iub Interface.......................................689
207 Configuring Hybrid Iub IP Transmission........................................................................696
208 Configuring ATM/IP Dual Stack NodeB..........................................................................699
209 Configuring IP Transmission Introduction on Iu Interface..........................................703
210 Configuring IP Transmission Introduction on Iur Interface........................................705
211 Configuring FP MUX for IP Transmission.......................................................................707
Issue 06 (2013-03-25)

xxxviii
RAN14.0
Contents
212 Configuring Dynamic Bandwidth Control of Iub IP.....................................................709

213 Configuring Overbooking on IP Transmission..............................................................711
214 Configuring IP Routing-Based Hub NodeB....................................................................716
215 Configuring PDCP Header Compression (RFC2507).....................................................718
216 Configuring RNC Offload...................................................................................................720
217 Configuring UDP MUX for Iu-CS Transmission............................................................724
218 Configuring Iu/Iur Transmission Resource Pool in RNC.............................................726
219 Configuring Iub Transmission Resource Pool in RNC.................................................729
220 Configuring Satellite Transmission on Iub Interface....................................................733
221 Configuring Satellite Transmission on Iu Interface.......................................................735
222 Configuring Clock Synchronization on Ethernet in NodeB.........................................737
223 Configuring Synchronous Ethernet...................................................................................740
224 Configuring Ethernet OAM................................................................................................742
225 Configuring RNC Node Redundancy...............................................................................745
226 Configuring RRU Redundancy..........................................................................................753
227 Configuring Iu Flex...............................................................................................................755
228 Configuring Iu Flex Load Distribution Management....................................................758
229 Configuring Transmit Diversity.........................................................................................763
230 Configuring 4-Antenna Receive Diversity.......................................................................765
231 Configuring Extended Cell Coverage up to 200km........................................................767
232 Configuring HSUPA Coverage Enhancement at UE Power Limitation.....................770
233 Configuring Flexible frequency bandwidth of UMTS carrier.....................................773
234 Configuring High Speed Access.........................................................................................775
235 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell
..........................................................................................................................................................778
236 Configuring Inter Frequency Hard Handover Based on Coverage.............................788
237 Configuring Inter Frequency Hard Handover Based on DL QoS................................792
238 Configuring SRNS Relocation (UE Not Involved).........................................................795
239 Configuring SRNS Relocation with Hard Handover.....................................................800
240 Configuring SRNS Relocation with Cell/URA Update.................................................804
241 Configuring Multiple RAB Package (PS RAB 2)........................................................807
Issue 06 (2013-03-25)

xxxix
RAN14.0
Contents
242 Configuring Combination of Two PS Services...............................................................809

243 Configuring Combination of One CS Service and Two PS Services..........................811
244 Configuring Combination of Three PS Services.............................................................813
245 Configuring Combination of One CS Service and Three PS Services....................... 815
246 Configuring Combination of Four PS Services...............................................................817
247 Configuring Inter Frequency Load Balance.....................................................................819
248 Configuring Domain Specific Access Control (DSAC).................................................826
249 Configuring Multi Frequency Band Networking Management..................................829
250 Configuring Enhanced Multiband Management............................................................831
251 Configuring DRD Introduction Package..........................................................................836
252 Configuring Intra System Direct Retry.............................................................................840
253 Configuring Inter System Direct Retry.............................................................................843
254 Configuring Inter-System Redirect....................................................................................846
255 Configuring Traffic Steering and Load Sharing During RAB Setup..........................848
256 Configuring Measurement Based Direct Retry...............................................................851
257 Configuring Service Steering and Load Sharing in RRC Connection Setup............854
258 Configuring Uplink Flow Control of User Plane............................................................857
259 Configuring Intra Frequency Load Balance.....................................................................860
260 Configuring Dynamic Target ROT Adjustment............................................................. 863
261 Configuring CE Overbooking.............................................................................................866
262 Configuring Intelligent Access Class Control.................................................................868
263 Configuring Dynamic Configuration of HSDPA CQI Feedback Period...................873
264 Configuring Load-based Uplink Target BLER Configuration.....................................878
265 Configuring Inter-Frequency Load Balancing Based on Configurable Load Threshold
..........................................................................................................................................................881
266 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g
..........................................................................................................................................................887
267 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based
on Iur-g........................................................................................................................................... 891
268 Configuring GSM and UMTS Load Balancing Based on Iur-g....................................894
269 Configuring GSM and UMTS Traffic Steering Based on Iur-g...................................899
270 Configuring Inter-RAT Handover Based on Coverage..................................................902
Issue 06 (2013-03-25)

xl
RAN14.0
Contents
271 Configuring Inter-RAT Handover Based on DL QoS....................................................906

272 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.........909
273 Configuring Inter-RAT Handover Phase 2.......................................................................911
274 Configuring NACC(Network Assisted Cell Change)....................................................913
275 Configuring PS Handover between UMTS and GPRS..................................................915
276 Configuring Inter-RAT Handover Based on Service.....................................................918
277 Configuring Inter-RAT Handover Based on Load..........................................................921
278 Configuring Inter-RAT Redirection Based on Distance................................................924
279 Configuring 3G/2G Common Load Management...........................................................927
280 Configuring Mobility Between UMTS and LTE Phase 1..............................................929
281 Configuring Service-Based PS Service Redirection from UMTS to LTE...................933
282 Configuring Service-Based PS Handover from UMTS to LTE.....................................937
283 Configuring Fast CS Fallback Based on RIM..................................................................941
284 Configuring Queuing and Preemption.............................................................................944
285 Configuring Access Class Restriction ..............................................................................946
286 Configuring Traffic Priority Mapping onto Transmission Resources........................950
287 Configuring Differentiated Service Based on SPI Weight............................................952
288 Configuring Optimization of R99 and HSUPA Users Fairness...................................958
289 Configuring Active Queue Management (AQM)...........................................................962
290 Configuring Quality Improvement for Subscribed Service.........................................964
291 Configuring TCP Accelerator..............................................................................................967
292 Configuring Rate Negotiation at Admission Control....................................................969
293 Configuring Videophone Service Restriction.................................................................973
294 Configuring Intelligent Inter-Carrier UE Layered Management.................................975
295 Configuring Micro NodeB Self-Planning.........................................................................980
296 Configuring NodeB Integrated IPSec................................................................................986
297 Configuring NodeB PKI Support.....................................................................................1007
298 Configuring Intelligent Battery Management...............................................................1018
299 Configuring Multi-mode Dynamic Power Sharing (UMTS)......................................1021
300 Configuring GSM and UMTS Dynamic Spectrum Sharing (UMTS).......................1024
Issue 06 (2013-03-25)

xli
RAN14.0
Contents
301 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB)

........................................................................................................................................................1029
302 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side
(NodeB).........................................................................................................................................1030
303 Configuring Multi-Mode BS Common Reference Clock (NodeB)............................1036
304 Multi-mode BS Common IPSec(UMTS).........................................................................1037
305 Configuring 2.0MHz Central Frequency point separation between GSM and UMTS
mode(UMTS)...............................................................................................................................1057
306 Configuring Dynamic MA for GU Dynamic Spectrum Sharing (UMTS)...............1061
307 Configuring GSM Power Control on Interface Frequency for GU Small Frequency
Gap (UMTS)................................................................................................................................1064
Issue 06 (2013-03-25)

xlii
RAN14.0
Changes in the RAN Feature Activation

Guide
This chapter describes the changes in the RAN Feature Activation Guide.
06 (2013-03-25)
This is the sixth commercial release of RAN14.0.
Compared with issue 05 (2012-12-31), this issue includes the following topics:
l
249 Configuring Multi Frequency Band Networking Management
Compared with issue 05 (2012-12-31), this issue incorporates the following changes:
Content
Description
The activation procedure is changed.
35 Configuring Intra Frequency Hard

Handover
The task example is changed.
114 Configuring Adaptive Configuration

of Traffic Channel Power offset for
HSUPA
The verification procedure is changed.
110 Configuring TTI Switch for BE

Services Based on Coverage
106 Configuring HSUPA 2 ms/10 ms TTI

Handover
The context is changed.
Compared with issue 05 (2012-12-31), this issue does not exclude any topics.
Issue 06 (2013-03-25)

RAN14.0
05 (2012-12-31)
This is the fifth commercial release of RAN14.0.
Compared with issue 04 (2012-11-07), this issue does not include any topics.
Content
Description
248 Configuring Domain Specific Access

Control (DSAC)
107 Configuring HSUPA 5.74Mbps per

User

+MIMO
The prerequisite is changed.
217 Configuring UDP MUX for Iu-CS

Transmission
04 (2012-11-07)
This is the fourth commercial release of RAN14.0.
Issue 06 (2013-03-25)
Content
Description
250 Configuring Enhanced Multiband

Management
263 Configuring Dynamic Configuration

of HSDPA CQI Feedback Period
186 Configuring RAN Sharing

Introduction Package
167 Configuring Uplink Enhanced

CELL_FACH
270 Configuring Inter-RAT Handover

Based on Coverage

RAN14.0
03 (2012-08-30)
This is the third commercial release of RAN14.0.
Compared with issue 02 (2012-06-30), this issue includes the following topics:
l
Issue 06 (2013-03-25)
Content
Description
43 Configuring Dynamic AAL2

Connections in Iub/IuCS/Iur Interface
155 Configuring HSPA+ Downlink 84

Mbit/s per User
148 Configuring HSPA+ Downlink

21Mbps per User

28Mbps per User

Handover
110 Configuring TTI Switch for BE

The procedure is changed.
220 Configuring Satellite Transmission on

Iub Interface

CELL_FACH
237 Configuring Inter Frequency Hard

Handover Based on DL QoS

Based on DL QoS
236 Configuring Inter Frequency Hard

Handover Based on Coverage
269 Configuring GSM and UMTS Traffic

Steering Based on Iur-g
The task example and the procedure are

changed.
67 Configuring AMR/WB-AMR Speech

Rates Control

RAN14.0
Content
Description
112 Configuring Dynamic CE Resource

Management
175 Configuring Enhanced Fast

Dormancy
58 Configuring Connection with TMA

(Tower Mounted Amplifier)

of Typical HSPA Rate
The data preparation is added.
146 Configuring Adaptive Adjustment of

HSUPA Small Target Retransmissions
176 Configuring Voice Service Experience

Improvement for Weak Reception UEs
The procedure is changed, and the data

preparation is added.
200 Configuring MOCN Cell Resource

Demarcation
247 Configuring Inter Frequency Load

Balance

Management

264 Configuring Load-based Uplink

Target BLER Configuration
265 Configuring Inter-Frequency Load

Balancing Based on Configurable Load
Threshold
282 Configuring Service-Based PS

Handover from UMTS to LTE
283 Configuring Fast CS Fallback Based

on RIM
Issue 06 (2013-03-25)

RAN14.0
02 (2012-06-30)
This is the second commercial release of RAN14.0.
Content
Description

CELL_FACH

Dormancy
The activation procedure is optimized.
282 Configuring Service-Based PS

287 Configuring Differentiated Service

Based on SPI Weight
265 Configuring Inter-Frequency Load

Threshold
200 Configuring MOCN Cell Resource

Demarcation
115 Configuring Anti-Interference

Scheduling for HSUPA
01 (2012-04-26)
This is the first commercial release of RAN14.0.
Compared with issue Draft B (2012-03-26), this issue includes the following new topics:
l
69 Configuring AMR Voice Quality Improvement Based on PLVA
Issue 06 (2013-03-25)

RAN14.0
Compared with issue Draft B (2012-03-26), this issue incorporates the following changes:
content
Description
215 Configuring PDCP Header

Compression (RFC2507)
The step of activating the license is deleted.

The dependencies on other features is

changed.
176 Configuring Voice Service Experience

Improvement for Weak Reception UEs
The verification procedure is optimized.

Based on Coverage
The verification procedure is optimized.
251 Configuring DRD Introduction

Package
The configuration procedure of activating the

RRC Inter-frequency Redirection Based on
Distance is added.
192 Configuring Dedicated Iub

Transmission Control
The configuration procedure of activating

Dedicated Iub Transmission Control in IP
mode is added.
The step of enabling the single-user peak-rate

improvement algorithm of HSUPA 2 ms TTI
is added.

Dormancy
The configuration procedure is optimized.
52 Configuring NodeB Self-Discovery

Based on IP Mode
The configuration of NodeB deployment on

the M2000 is modified.
120 Configuring Control Channel Parallel

Interference Cancellation (Phase 2)
The verification steps are modified.
The description of the HSPA+ Uplink 23

Mbit/s per User feature is incorporated into
160 Configuring HSPA+ Uplink 23 Mbit/s
per User.
The task example is optimized.
The task example is optimized.
The cell configuration is added.
Compared with issue Draft B (2012-03-26), this issue does not exclude any topics.
Draft B (2012-03-26)
This is the Draft B release of RAN14.0.
Issue 06 (2013-03-25)

RAN14.0
Compared with issue Draft A (2012-02-15), this issue does not include any new topics.
Compared with issue Draft A (2012-02-15), this issue incorporates the following changes:
content
Description

42Mbps per User
The dependecy of BBU3806C is deleted from

prerequisites.
288 Configuring Optimization of R99 and

HSUPA Users Fairness
172 Configuring Flexible HSPA+
Technology Selection
162 Configuring Downlink Enhanced
CELL_FACH
21Mbps per User
28Mbps per User
142 Configuring CQI Adjustment Based
on Dynamic BLER Target
115 Configuring Anti-Interference
107 Configuring HSUPA 5.74Mbps per
User
Handover
260 Configuring Dynamic Target ROT
Adjustment
Issue 06 (2013-03-25)
The dependencies on hardware are added to

prerequisites.

RAN14.0
content
Description
172 Configuring Flexible HSPA+

The limit that WRFD-010704 Flexible HSPA

+ Technology Selection cannot be used
together with WRFD-010699 DC-HSDPA
+MIMO is deleted from prerequisites, and the
configuration of DC-HSDPA and MIMO is
added.
Compared with issue Draft A (2012-02-15), this issue does not exclude any topics.
Draft A (2012-02-15)
This is the Draft A release of RAN14.0.
Compared with issue 05 (2012-01-05) of RAN13.0, this issue includes the following new topics:
l
41 Configuring CS Fallback Guarantee for LTE Emergency Calls
144 Configuring Adaptive Configuration of Typical HSPA Rate
263 Configuring Dynamic Configuration of HSDPA CQI Feedback Period
264 Configuring Load-based Uplink Target BLER Configuration
265 Configuring Inter-Frequency Load Balancing Based on Configurable Load

Threshold
282 Configuring Service-Based PS Handover from UMTS to LTE
306 Configuring Dynamic MA for GU Dynamic Spectrum Sharing (UMTS)
307 Configuring GSM Power Control on Interface Frequency for GU Small

Frequency Gap (UMTS)
Compared with issue 05 (2012-01-05) of RAN13.0, this issue incorporates the following
changes:
Issue 06 (2013-03-25)

RAN14.0
content
Description
The configuration of S12 interface is added.
235 Configuring Independent

Demodulation of Signals from Multiple
RRUs in One Cell
The configuration of new function is added.
247 Configuring Inter Frequency Load

Balance

Management
Compared with issue 05 (2012-01-05) of RAN13.0, this issue does not exclude any topics.
Issue 06 (2013-03-25)

RAN14.0
Feature Activation and License Item

Descriptions
RANFeatures are classified into basic and optional features. Basic features are not licensecontrolled and therefore do not require license activation before use. Some optional features are
license-controlled and therefore require license activation before use. If the Configuration
Method column for a basic feature in the RAN basic feature list is None, enabling this feature
does not involve any configurations. If the Configuration Method column for an optional feature
in the RAN optional feature list is None, this feature is enabled once it is activated.
Table 2-1 lists the RAN basic features. Table 2-2 lists the RAN optional features.
Table 2-1 RAN Basic Feature List
Issue 06 (2013-03-25)
Feature ID
Feature Name
Configuration Method
WRFD-000001
System Improvement for

RAN5.1
None
WRFD-000002

RAN6.0
None
WRFD-000003

RAN6.1
None
WRFD-000004

RAN10.0
None
WRFD-000005

RAN11.0
None
WRFD-000006

RAN11.1
None
WRFD-000007

RAN12.0
None
WRFD-000008

RAN13.0
None
WRFD-010101
3GPP R9 Specifications
None

10
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
WRFD-010102
Operating Multi-band
None
WRFD-010201
FDD Mode
None
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
Connection and Radio
Access Bearer Establishment
and Release
5 Configuring
3.4/6.8/13.6/27.2Kbps RRC
Connection and Radio
Access Bearer
WRFD-010501
Conversational QoS Class
6 Configuring
Conversational QoS Class
WRFD-010502
Streaming QoS Class
7 Configuring Streaming
QoS Class
WRFD-010503
Interactive QoS Class
8 Configuring Interactive
QoS Class
WRFD-010504
Background QoS Class
9 Configuring Background
QoS Class
WRFD-010609
Multiple RAB Introduction

Package (PS RAB < 2)
None
WRFD-01060901
Combination of Two CS
Services (Except for Two
AMR Speech Services)
None
WRFD-01060902
Combination of One CS
Service and One PS Service
None
WRFD-01060903
Combination of Two CS
Services and One PS Service
(Except for Two AMR
Speech Services)
None
WRFD-021104
Emergency Call
10 Configuring Emergency
Call
WRFD-010506
RAB Quality of Service

Renegotiation over Iu
Interface
11 Configuring RAB
Quality of Service
Renegotiation over Iu
Interface
MRFD-210604
2-Way Antenna Receive

Diversity
12 Configuring 2-Way
Antenna Receive Diversity
WRFD-010205
Cell Digital Combination and

Split
13 Configuring Cell Digital

Combination and Split
WRFD-010208
Fast Power Congestion

Control (FCC)
None

11
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
WRFD-010211
Active TX Chain Gain

Calibration
None
WRFD-010202
UE State in Connected Mode

(CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
14 Configuring UE State in
Connected Mode
(CELL_DCH,
CELL_PCH, URA_PCH,
CELL_FACH)
WRFD-010401
System Information
Broadcasting
None
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
15 Configuring Paging UE
in Idle, CELL_PCH,
URA_PCH State (Type 1)
WRFD-010302
Paging UE in CELL_FACH,
CELL_DCH State (Type 2)
16 Configuring Paging UE
in CELL_FACH,
WRFD-020900
Logical Channel
Management
None
WRFD-021000
Transport Channel
Management
None
WRFD-022000
Physical Channel
Management
None
WRFD-021101
Dynamic Channel
Configuration Control
(DCCC)
17 Configuring Dynamic
Channel Configuration
Control
WRFD-011401
Integrity Protection
18 Configuring Integrity
Protection
WRFD-011402
Encryption
WRFD-020501
Open Loop Power Control
20 Configuring Open Loop

Power Control
WRFD-020502
Downlink Power Balance
21 Configuring Downlink
Power Balance
WRFD-020503
Outer Loop Power Control
22 Configuring Outer Loop

Power Control
WRFD-020504
Inner Loop Power Control
23 Configuring Inner Loop

Power Control
WRFD-020101
Admission Control
24 Configuring Admission
Control
WRFD-020102
Load Measurement
25 Configuring Load
Measurement

12
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
WRFD-020106
Load Reshuffling
26 Configuring Load
Reshuffling
WRFD-020107
Overload Control
27 Configuring Overload
Control
WRFD-020108
Code Resource Management
28 Configuring Code
Resource Management
WRFD-020105
Potential User Control
29 Configuring Potential
User Control
WRFD-021102
Cell Barring
30 Configuring Cell
Barring
WRFD-021301
Shared Network Support in

Connected Mode
31 Configuring Shared
Network Support in
Connected Mode
MRFD-210104
BSC/RNC Resource Sharing
None
WRFD-020201
Intra NodeB Softer Handover
32 Configuring Intra
NodeB Softer Handover
WRFD-020202
Intra RNC Soft Handover
33 Configuring Intra RNC

Soft Handover
WRFD-020203
Inter RNC Soft Handover
34 Configuring Inter RNC

Soft Handover
WRFD-020301
Intra Frequency Hard

Handover
35 Configuring Intra
Frequency Hard Handover
WRFD-010801
Intra RNC Cell Update

Cell Update
WRFD-010802
Inter RNC Cell Update

Cell Update
WRFD-010901
Intra RNC URA Update

URA Update
WRFD-010902
Inter RNC URA Update

URA Update
WRFD-021400
Direct Signaling Connection

Re-establishment (DSCR)
40 Configuring Direct
Signaling Connection Reestablishment (DSCR)
WRFD-140102
CS Fallback Guarantee for

LTE Emergency Calls
41 Configuring CS
Fallback Guarantee for
LTE Emergency Calls
MRFD-210204
Star Topology
None
MRFD-210205
Chain Topology
None

13
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
MRFD-210206
Tree Topology
None
MRFD-210501
NodeB Clock
42 Configuring NodeB
Clock
MRFD-210502
RNC Clock
None
WRFD-050301
ATM Transmission
None
WRFD-05030101
ATM over E1T1 on Iub

Interface
None
WRFD-05030102
ATM over Channelized

STM-1/OC-3 on Iub
Interface
None
WRFD-05030103
ATM over Non-channelized

STM-1/OC-3c on Iub/Iu/Iur
Interface
None
WRFD-05030104
Dynamic AAL2 Connections

in Iub/IuCS/Iur Interface
43 Configuring Dynamic
AAL2 Connections in Iub/
IuCS/Iur Interface
WRFD-05030105
Permanent AAL5
Connections for Control
Plane Traffic
44 Configuring Permanent
AAL5 Connections for
Control Plane Traffic
WRFD-05030106
Call Admission Based on

Used AAL2 Path Bandwidth
45 Configuring Call
Admission Based on Used
AAL2 Path Bandwidth
WRFD-05030107
CBR, rt-VBR, nrt-VBR,

UBR ATM QoS Classes
46 Configuring CBR, rtVBR, nrt-VBR, UBR ATM

QoS Classes
WRFD-05030110
F5
47 Configuring F5
WRFD-050304
IMA for E1T1 or

Channelized STM-1/OC-3
on Iub Interface
None
WRFD-050305
UBR+ ATM QoS Class
48 Configuring UBR+
ATM QoS Class
MRFD-210103
Link aggregation
49 Configuring Link
Aggregation
WRFD-040100
Flow Control
50 Configuring Flow
Control
WRFD-040101
DPU Board Replaced

without Service Interrupt in
RNC
None

14
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
MRFD-210101
System Redundancy
None
MRFD-210102
Operate System Security

Management
None
MRFD-210302
Performance Management
None
MRFD-210304
Fault Management
None
MRFD-210303
Inventory Management
None
MRFD-210301
Configuration Management
None
MRFD-210305
Security Management
None
MRFD-210801
Interface Tracing
None
MRFD-210802
Call Tracing
None
MRFD-210401
RNC Software Management
None
MRFD-210402
NodeB Software
Management
None
MRFD-210310
NodeB Software USB

Download
None
WRFD-031100
BOOTP
WRFD-031101
NodeB Self-discovery Based

on IP Mode
52 Configuring NodeB SelfDiscovery Based on IP

Mode
WRFD-031102
NodeB Remote Selfconfiguration
None
WRFD-031103
NodeB Self-test
None
MRFD-210403
License Management
None
WRFD-040300
License Control for Urgency
53 Configuring License
Control for Urgency
MRFD-210309
DBS Topology Maintenance
None
WRFD-031000
Intelligently Out of Service
54 Configuring
Intelligently Out of Service
WRFD-031200
OCNS
55 Configuring OCNS
WRFD-031400
Power off the equipment

level by level
56 Configuring Power Off

the Equipment Level by
Level
WRFD-031500
Solar Power Device

Management
57 Configuring Solar
Power Device Management

15
RAN14.0
Feature ID
Feature Name
WRFD-021404
Single IP Address for NodeB
None
WRFD-020406
Intelligent Power
Measurement
None
WRFD-010212
Improved CE Mapping for EDCH
None
MRFD-210701
Documentation
None
MRFD-210601
Connection with TMA

58 Configuring Connection
with TMA (Tower
Mounted Amplifier)
MRFD-210602
Remote Electrical Tilt
59 Configuring Remote
Electrical Tilt
WRFD-060003
Same Band Antenna Sharing

Unit (900Mhz)
60 Configuring Same Band

Antenna Sharing Unit (900
MHz)
MRFD-220001
Multi-mode BS Common
CPRI Interface(NodeB)
None
MRFD-220002
Multi-mode BS RRU/RFU
star-connection with separate
CPRI interface(NodeB)
None
Table 2-2 RAN Optional Feature List
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010617
VoIP over
HSPA/HSPA+
VoIP over
HSPA
Introduction
Pakage
BSC6900
61 Configuring
VoIP over
HSPA/HSPA+
WRFD-010617
01
RAB Mapping
VoIP over
HSPA
Introduction
Pakage
BSC6900
None
WRFD-010617
03
Optimized
Scheduling for
VoIP over
HSPA
VoIP over
HSPA
Introduction
Pakage
BSC6900
62 Configuring
Optimized
Scheduling for
VoIP over
HSPA

16
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010618
IMS Signaling
over HSPA
IMS Signaling
over HSPA
BSC6900
63 Configuring
IMS Signaling
over HSPA
WRFD-011501
PDCP Header
Compression
(RoHC)
PDCP ROHC
Function
BSC6900
64 Configuring
PDCP Header
Compression
(RoHC)
WRFD-010619
CS voice over
HSPA/HSPA+
CS voice over
HSPA
BSC6900
65 Configuring
CS Voice over
HSPA/HSPA+
WRFD-010613
AMR-WB
(Adaptive Multi
Rate Wide
Band)
Wide Band
AMR
BSC6900
66 Configuring
AMR-WB
(Adaptive
Multi Rate
Wide Band)
WRFD-020701
AMR/WBAMR Speech
Rates Control
AMR voice
coding rate
control
BSC6900
67 Configuring
AMR/WBAMR Speech
Rates Control
WRFD-011600
TFO/TrFO
TFO/TrFO
BSC6900
68 Configuring
TFO/TrFO
WRFD-140201
AMR Voice
Quality
Improvement
Based on PLVA
AMR Voice
Quality
Improvement
Based on PLVA
NodeB
69 Configuring
AMR Voice
Quality
Improvement
Based on
PLVA
WRFD-011000
Cell Broadcast
Service
Cell broadcast
service
BSC6900
70 Configuring
Cell Broadcast
Service
WRFD-011001
Simplified Cell
Broadcast
Simplified Cell
Broadcast
BSC6900
71 Configuring
Simplified Cell
Broadcast
WRFD-020127
Warning of
Disaster
Warning of
Disaster
BSC6900
72 Configuring
Warning of
Disaster
WRFD-010616
MBMS
Introduction
Package
MBMS
Function
BSC6900&Nod
eB
73 Configuring
MBMS
Introduction
Package

17
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010616
01
MBMS
Broadcast Mode
MBMS
Function
BSC6900&Nod
eB
None
WRFD-010616
02
MBMS
Admission
Control
MBMS
Function
BSC6900&Nod
eB
74 Configuring
MBMS
Admission
Control
WRFD-010616
03
MBMS Load
Control
MBMS
Function
BSC6900&Nod
eB
75 Configuring
MBMS Load
Control
WRFD-010616
04
MBMS Soft/
Selective
Combining
MBMS
Function
BSC6900&Nod
eB
None
WRFD-010616
05
MBMS
Transport
Resource
Management
MBMS
Function
BSC6900&Nod
eB
76 Configuring
MBMS
Transport
Resource
Management
WRFD-010616
06
Streaming
Service on
MBMS
MBMS
Function
BSC6900&Nod
eB
77 Configuring
Streaming
Service on
MBMS
WRFD-010616
07
MBMS 2
Channels per
Cell
MBMS
Function
BSC6900&Nod
eB
None
WRFD-010616
08
16/32/64/128K
bps Channel
Rate on MBMS
MBMS
Function
BSC6900&Nod
eB
78 Configuring
16/32/64/128K
bps Channel
Rate on MBMS
WRFD-010660
MBMS Phase 2
None
BSC6900
79 Configuring
MBMS Phase 2
WRFD-010660
01
MBMS
Enhanced
Broadcast Mode
MBMS
Enhanced
Broadcast Mode
BSC6900
80 Configuring
MBMS
Enhanced
Broadcast
Mode
WRFD-010660
02
MBMS P2P
over HSDPA
MBMS P2P
over HSDPA
BSC6900
81 Configuring
MBMS P2P
over HSDPA

18
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010660
03
MBMS
Admission
Enhancement
MBMS
Admission
Enhancement
BSC6900
82 Configuring
MBMS
Admission
Enhancement
WRFD-010660
04
Inter-Frequency
Neighboring
Cell Selection
for MBMS PTP
Users
None
None
83 Configuring
InterFrequency
Neighboring
Cell Selection
for MBMS
PTP Users
WRFD-010627
FACH
Transmission
Sharing for
MBMS
None
None
84 Configuring
FACH
Transmission
Sharing for
MBMS
WRFD-010626
MBMS FLC
(Frequency
Layer
Convergence)/
FLD(Frequency
Layer
Dispersion)
MBMS FLC
(Frequency
Layer
Convergence)/
FLD(Frequency
Layer
Dispersion)
BSC6900
85 Configuring
MBMS FLC
(Frequency
Layer
Convergence)/
FLD
(Frequency
Layer
Dispersion)
WRFD-010624
MBMS 8
Channels per
Cell
MBMS 8
Channels per
Cell
BSC6900
None
WRFD-010625
256Kbps
Channel Rate on
MBMS
256Kbps
Channel Rate on
MBMS
BSC6900
None
WRFD-010628
MBMS 16
Channels per
Cell
MBMS 16
Channels per
Cell
BSC6900
None
WRFD-010661
MBMS over Iur
MBMS over Iur
BSC6900
86 Configuring
MBMS over
Iur
WRFD-010662
Dynamic Power
Estimation for
MTCH
Dynamic Power
Estimation for
MTCH
BSC6900
87 Configuring
Dynamic
Power
Estimation for
MTCH

19
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010663
MSCH
Scheduling
MSCH
Scheduling
BSC6900
88 Configuring
MSCH
Scheduling
WRFD-010665
MBMS Channel
Audience
Rating Statistics
MBMS Channel
Audience
Rating Statistics
BSC6900
89 Configuring
MBMS
Channel
Audience
Rating
Statistics
WRFD-020801
Cell ID + RTT
Function Based
LCS
Cell ID LCS
BSC6900
90 Configuring
Cell ID + RTT
Function
Based LCS
WRFD-020802
OTDOA Based
LCS
OTDOA LCS
BSC6900
91 Configuring
OTDOA Based
LCS
WRFD-020803
A-GPS Based
LCS
AGPS LCS
BSC6900
92 Configuring
A-GPS Based
LCS
WRFD-020804
LCS Classified
Zones
LCS Classified
Zones
BSC6900
93 Configuring
LCS Classified
Zones
WRFD-020805
LCS over Iur
LCS over Iur
BSC6900
94 Configuring
LCS over Iur
WRFD-020807
Iupc Interface
for LCS service
Iu-PC Interface
for LCS service
BSC6900
95 Configuring
Iupc Interface
for LCS
Service
WRFD-020134
Push to Talk
Push To Talk
(per PTT Active
User)
BSC6900
96 Configuring
Push to Talk
WRFD-010612
HSUPA
Introduction
Package
RNC:High
Speed Uplink
Packet Access
BSC6900&Nod
eB
97 Configuring
HSUPA
Introduction
Package
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
Issue 06 (2013-03-25)

20
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010612
01
HSUPA UE
Category
Support
RNC:High
Speed Uplink
Packet Access
BSC6900&Nod
eB
None
BSC6900&Nod
eB
None
BSC6900&Nod
eB
98 Configuring
HSUPA
Admission
Control
BSC6900&Nod
eB
99 Configuring
HSUPA Power
Control
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
WRFD-010612
09
WRFD-010612
02
HSUPA HARQ
and Fast UL
Scheduling in
Node B
RNC:High
Speed Uplink
Packet Access
HSUPA
Admission
Control
RNC:High
Speed Uplink
Packet Access
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
WRFD-010612
03
HSUPA Power
Control
RNC:High
Speed Uplink
Packet Access
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
Issue 06 (2013-03-25)

21
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010612
04
HSUPA
Mobility
Management
RNC:High
Speed Uplink
Packet Access
BSC6900&Nod
eB
100
Configuring
HSUPA
Mobility
Management
BSC6900&Nod
eB
101
Configuring
HSUPA DCCC
BSC6900&Nod
eB
None
BSC6900&Nod
eB
None
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
WRFD-010612
08
HSUPA DCCC
RNC:High
Speed Uplink
Packet Access
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
WRFD-010612
07
WRFD-010612
06
Issue 06 (2013-03-25)
HSUPA
Transport
Resource
Management
RNC:High
Speed Uplink
Packet Access
Interactive and
Background
Traffic Class on
HSUPA
RNC:High
Speed Uplink
Packet Access
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
NodeB:the
number of
NodeBs with
HSUPA
function
enabled

22
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010612
10
HSUPA
1.44Mbps per
User
RNC:High
Speed Uplink
Packet Access
BSC6900&Nod
eB
None
BSC6900&Nod
eB
102
Configuring 20
HSUPA Users
per Cell
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
WRFD-010612
11
20 HSUPA
Users per Cell
RNC:High
Speed Uplink
Packet Access
NodeB:the
number of
NodeBs with
HSUPA
function
enabled
WRFD-010612
12
HSUPA Iub
Flow Control in
Case of Iub
Congestion
None
None
103
Configuring
HSUPA Iub
Flow Control
in Case of Iub
Congestion
WRFD-010614
HSUPA Phase 2
HSUPA 2ms/
10ms TTI
handover
BSC6900
None
the number of
NodeBs with
HSUPA 2ms
TTI function
enabled
Issue 06 (2013-03-25)
WRFD-010614
01
HSUPA EAGCH Power

Control (Based
on CQI or HSSCCH)
HSUPA 2ms/
10ms TTI
handover
BSC6900
104
Configuring
HSUPA EAGCH Power
Control (Based
on CQI or HSSCCH)
WRFD-010614
02
Enhanced Fast
UL Scheduling
HSUPA 2ms/
10ms TTI
handover
BSC6900
None

23
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010614
03
HSUPA 2ms
TTI
the number of
NodeBs with
HSUPA 2ms
TTI function
enabled
NodeB
105
Configuring
HSUPA 2ms
TTI
WRFD-010614
04
HSUPA 2ms/
10ms TTI
Handover
HSUPA 2ms/
10ms TTI
handover
BSC6900
106
Configuring
HSUPA 2 ms/
10 ms TTI
Handover
WRFD-010614
05
HSUPA
5.74Mbps per
User
HSUPA
5.74Mbps per
User
BSC6900
107
Configuring
HSUPA
5.74Mbps per
User
WRFD-010632
Streaming
Traffic Class on
HSUPA
Streaming
Traffic Class on
HSUPA
BSC6900
108
Configuring
Streaming
Traffic Class
on HSUPA
WRFD-010635
HSUPA over Iur
HSUPA over Iur
BSC6900
109
Configuring
HSUPA over
Iur
WRFD-010640
Uplink Macro
Diversity
Intelligent
Receiving
Uplink Macro
Diversity
Intelligent
Receiving
BSC6900
None
WRFD-010690
TTI Switch for

BE Services
Based on
Coverage
TTI Switch for

BE Services
Based on
Coverage
BSC6900
110
Configuring
TTI Switch for
BE Services
Based on
Coverage
WRFD-010641
HSUPA
Adaptive
Transmission
HSUPA
Adaptive
Retransmission
BSC6900
111
Configuring
HSUPA
Adaptive
Transmission

24
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010638
Dynamic CE
Resource
Management
the number of
NodeBs with
dynamic CE
function
enabled
NodeB
112
Configuring
Dynamic CE
Resource
Management
WRFD-010692
HSUPA FDE
The number of
Cells with FDE
function
enabled
NodeB
113
Configuring
HSUPA FDE
WRFD-010712
Adaptive
Configuration
of Traffic
Channel Power
offset for
HSUPA
Adaptive
Configuration
of Traffic
Channel Power
offset for
HSUPA
BSC6900
114
Configuring
Adaptive
Configuration
of Traffic
Channel Power
offset for
HSUPA
WRFD-020136
AntiInterference
Scheduling for
HSUPA
the number of
cells with antiinterference
scheduling for
HSUPA
function
enabled
NodeB
115
Configuring
AntiInterference
Scheduling for
HSUPA
WRFD-020137
Dual-Threshold
Scheduling with
HSUPA
Interference
Cancellation
the number of
NodeBs with
dual-threshold
scheduling with
HSUPA
interference
cancellation
function
enabled
NodeB
116
Configuring
DualThreshold
Scheduling
with HSUPA
Interference
Cancellation
WRFD-010634
60 HSUPA
Users per Cell
60 HSUPA
Users per Cell
BSC6900
117
Configuring 60
HSUPA Users
per Cell
WRFD-010210
Control
Channel
Parallel
Interference
Cancellation
(CCPIC)
the number of
NodeBs with
CCPIC function
enabled
NodeB
None

25
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010691
HSUPA UL
Interference
Cancellation
The number of
Cells with UL
IC function
enabled
NodeB
118
Configuring
HSUPA UL
Interference
Cancellation
WRFD-010636
SRB over
HSUPA
SRB over
HSUPA
BSC6900
119
Configuring
SRB over
HSUPA
WRFD-140202
Control
Channel
Parallel
Interference
Cancellation
(Phase 2)
The number of
NodeBs with
flexible
frequency
separation
function
enabled
NodeB
120
Configuring
Control
Channel
Parallel
Interference
Cancellation
(Phase 2)
WRFD-010610
HSDPA
Introduction
Package
High Speed
Downlink
Packet Access
BSC6900
121
Configuring
HSDPA
Introduction
Package
WRFD-010610
17
QPSK
Modulation
NodeB:HSDPA
RRM package 1
NodeB
None
NodeB
122
Configuring 15
Codes per Cell
NodeB
123
Configuring
Time and HSPDSCH Codes
Multiplex
NodeB
124
Configuring
HSDPA HARQ &
Scheduling
(MAX C/I, RR,
and PF)
NodeB:HSDPA
function
WRFD-010610
01
15 Codes per
Cell
NodeB:HSDPA
RRM package 1
NodeB:HSDPA
function
WRFD-010610
18
WRFD-010610
09
Issue 06 (2013-03-25)
Time and HSPDSCH Codes

Multiplex
NodeB:HSDPA
RRM package 1
HSDPA HARQ &

Scheduling
(MAX C/I, RR
and PF)
NodeB:HSDPA
RRM package 1
NodeB:HSDPA
function
NodeB:HSDPA
function

26
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010610
05
HSDPA Static
Code Allocation
and RNCControlled
Dynamic Code
Allocation
NodeB:HSDPA
RRM package 1
NodeB
125
Configuring
HSDPA Static
Code
Allocation and
RNCControlled
Dynamic Code
Allocation
HSDPA Power
Control
NodeB:HSDPA
RRM package 1
NodeB
126
Configuring
HSDPA Power
Control
NodeB
127
Configuring
HSDPA
Admission
Control
NodeB
None
NodeB
128
Configuring
Improvement
of User
Experience in
Low Traffic
Service
NodeB
129
Configuring
HSDPA Flow
Control
NodeB
130
Configuring
HSDPA
Mobility
Management
NodeB
None
WRFD-010610
04
NodeB:HSDPA
function
NodeB:HSDPA
function
WRFD-010610
03
WRFD-010610
19
WRFD-010610
20
WRFD-010610
10
HSDPA
Admission
Control
NodeB:HSDPA
RRM package 1
HSDPA
Dynamic Power
Allocation
NodeB:HSDPA
RRM package 1
Improvement of
User Experience
in Low Traffic
Service
NodeB:HSDPA
RRM package 1
HSDPA Flow
Control
NodeB:HSDPA
RRM package 1
NodeB:HSDPA
function
NodeB:HSDPA
function
NodeB:HSDPA
function
NodeB:HSDPA
function
WRFD-010610
06
WRFD-010610
14
Issue 06 (2013-03-25)
HSDPA
Mobility
Management
NodeB:HSDPA
RRM package 1
HSDPA
Transport
Resource
Management
NodeB:HSDPA
RRM package 1
NodeB:HSDPA
function
NodeB:HSDPA
function

27
RAN14.0
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
NodeB:HSDPA
RRM package 1
NodeB
None
HSDPA UE
Category 1 to 28
NodeB:HSDPA
RRM package 1
NodeB
131
Configuring
HSDPA UE
Category 1 to
28
NodeB
None
NodeB
None
WRFD-010610
02
NodeB:HSDPA
function
NodeB:HSDPA
function
WRFD-010610
15
WRFD-010610
16
HSDPA
1.8Mbps per
User
NodeB:HSDPA
RRM package 1
16 HSDPA
Users per Cell
NodeB:HSDPA
RRM package 1
NodeB:HSDPA
function
NodeB:HSDPA
function
WRFD-010620
HSDPA
3.6Mbps per
User
High Speed
Downlink
Packet Access
Function 3.6M
BSC6900
None
WRFD-010629
DL 16QAM
Modulation
NodeB:HSDPA
RRM package 1
NodeB
132
Configuring
DL 16QAM
Modulation
NodeB:HSDPA
function
Issue 06 (2013-03-25)
WRFD-010631
Dynamic Code
Allocation
Based on Node
B
HSDPA RRM
package 1
NodeB
133
Configuring
Dynamic Code
Allocation
Based on
NodeB
WRFD-010621
HSDPA
7.2Mbps per
User
High Speed
Downlink
Packet Access
Function 7.2M
BSC6900
None
WRFD-010622
32 HSDPA
Users per Cell
32 HSDPA
Users per Cell
BSC6900
None

28
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010611
HSDPA
Enhanced
Package
None
BSC6900
134
Configuring
HSDPA
Enhanced
Package
WRFD-010611
03
Scheduling
based on EPF
and GBR
None
None
135
Configuring
Scheduling
based on EPF
and GBR
WRFD-010611
11
HSDPA State
Transition
HSDPA State
Transition
BSC6900
136
Configuring
HSDPA State
Transition
WRFD-010611
12
HSDPA DRD
HSDPA DRD
BSC6900
137
Configuring
HSDPA DRD
WRFD-010611
13
HS-DPCCH
Preamble
Support
HS-DPCCH
Preamble
support
BSC6900
138
Configuring
HS-DPCCH
Preamble
Support
WRFD-010630
Streaming
Traffic Class on
HSDPA
Streaming
Traffic Class on
HSDPA
BSC6900
139
Configuring
Streaming
Traffic Class
on HSDPA
WRFD-010650
HSDPA
13.976Mbps per
User
HSDPA
13.976Mbps per
User
BSC6900
None
WRFD-010651
HSDPA over Iur
HSDPA over Iur
BSC6900
140
Configuring
HSDPA over
Iur
WRFD-010652
SRB over
HSDPA
SRB over
HSDPA
BSC6900
141
Configuring
SRB over
HSDPA
WRFD-010623
64 HSDPA
Users per Cell
64 HSDPA
Users per Cell
BSC6900
None

29
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-030010
CQI
Adjustment
Based on
Dynamic BLER
Target
CQI
Adjustment
Based on
Dynamic BLER
Target(per Cell)
NodeB
142
Configuring
CQI
Adjustment
Based on
Dynamic
BLER Target
WRFD-030011
MIMO Prime
MIMO Prime
(per Cell)
NodeB
143
Configuring
MIMO Prime
WRFD-030004
Adaptive
Configuration
of Typical
HSPA Rate
Self-adaption of
HSPA Typical
Throughput
BSC6900
144
Configuring
Adaptive
Configuration
of Typical
HSPA Rate
WRFD-140221
HSDPA
Scheduling
Based on UE
Location
HSDPA
Scheduling
Based on UE
Location(Per
Cell)
NodeB
145
Configuring
HSDPA
Scheduling
Based on UE
Location
WRFD-140222
Adaptive
Adjustment of
HSUPA Small
Target
Retransmission
s
None
None
146
Configuring
Adaptive
Adjustment of
HSUPA Small
Target
Retransmissio
ns
WRFD-010680
HSPA+
Downlink
28Mbps per
User
HSPA +
Downlink 28
Mbit/s Per User
BSC6900
147
Configuring
HSPA+
Downlink
28Mbps per
User
WRFD-010681
HSPA+
Downlink
21Mbps per
User
HSPA +
Downlink 21
Mbit/s Per User
BSC6900
148
Configuring
HSPA+
Downlink
21Mbps per
User

30
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010685
Downlink
Enhanced L2
Downlink
Enhanced L2
BSC6900
149
Configuring
Downlink
Enhanced L2
WRFD-010689
HSPA+
Downlink
42Mbps per
User
HSPA+
Downlink 42
Mbit/s per User
BSC6900
150
Configuring
HSPA+
Downlink
42Mbps per
User
WRFD-010683
Downlink
64QAM
the number of
cells with
64QAM
function
enabled
NodeB
151
Configuring
Downlink
64QAM
WRFD-010684
2x2 MIMO
the number of
cells with
MIMO function
enabled
NodeB
152
Configuring
2x2 MIMO
WRFD-010693
DL 64QAM
+MIMO
the number of
Cells with DL
64QAM
+MIMO
function
enabled
NodeB
153
Configuring
Downlink
64QAM
+MIMO
WRFD-010698
HSPA+ Uplink
11.5Mbit/s per
User
HSPA+ Uplink
11.5Mbit/s per
User
BSC6900
154
Configuring
HSPA+ Uplink
11.5Mbit/s per
User
WRFD-010703
HSPA+
Downlink
84Mbit/s per
User
HSPA+
Downlink
84Mbit/s per
User
BSC6900
155
Configuring
HSPA+
Downlink 84
Mbit/s per User
WRFD-010699
DC-HSDPA
+MIMO
the number of
cells with DCHSDPA
+MIMO
function
enabled
NodeB
156
Configuring
DC-HSDPA
+MIMO

31
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010694
UL 16QAM
The number of
Cells with UL
16QAM
function
enabled
NodeB
157
Configuring
UL 16QAM
WRFD-010695
UL Layer 2
Improvement
The number of
Cells with UL
L2
Improvement
function
enabled
NodeB
158
Configuring
UL Layer 2
Improvement
WRFD-010696
DC-HSDPA
The number of
Cells with DL
DC function
enabled
NodeB
159
Configuring
DC-HSDPA
WRFD-140203
HSPA+ Uplink
23 Mbit/s per
User
HSPA+ Uplink
23 Mbit/s per
User
BSC6900
160
Configuring
HSPA+ Uplink
23 Mbit/s per
User
WRFD-140204
DC-HSUPA
DC-HSUPA
(Per Cell)
NodeB
161
Configuring
DC-HSUPA
WRFD-010688
Downlink
Enhanced
CELL_FACH
Enhanced
CELL_FACH
BSC6900
162
Configuring
Downlink
Enhanced
CELL_FACH
WRFD-010700
Performance
Improvement of
MIMO and
HSDPA Cocarrier
the number of
cells with
performace
improvement of
MIMO and
HSDPA cocarrier function
enabled
NodeB
163
Configuring
Performance
Improvement
of MIMO and
HSDPA Cocarrier
WRFD-010686
CPC - DTX /
DRX
CPC-DTX /
DRX
BSC6900
164
Configuring
CPC - DTX /
DRX

32
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010687
CPC - HSSCCH less

operation
CPC-HS-SCCH
Less Operation
BSC6900
165
Configuring
CPC - HSSCCH less
operation
WRFD-010697
E-DPCCH
Boosting
the number of
cells with EDPCCH
boosting
function
enabled
NodeB
166
Configuring EDPCCH
Boosting
WRFD-010701
Uplink
Enhanced
CELL_FACH
Enhanced
Uplink for
CELL_FACH
BSC6900
167
Configuring
Uplink
Enhanced
CELL_FACH
WRFD-010653
96 HSDPA
Users per Cell
96 HSDPA
Users per Cell
BSC6900
168
Configuring 96
HSDPA Users
per Cell
WRFD-010639
96 HSUPA
Users per Cell
96 HSUPA
Users per Cell
BSC6900
169
Configuring 96
HSUPA Users
per Cell
WRFD-010654
128 HSDPA
Users per Cell
128 HSDPA
Users per Cell
BSC6900
170
Configuring
128 HSDPA
Users per Cell
WRFD-010670
128 HSUPA
Users per Cell
128 HSUPA
Users per Cell
BSC6900
171
Configuring
128 HSUPA
Users per Cell
WRFD-010704
Flexible HSPA
+ Technology
Selection
Flexible HSPA
+ Technology
Selection
BSC6900
172
Configuring
Flexible HSPA
+ Technology
Selection

33
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010713
Traffic-Based
Activation and
Deactivation of
the
Supplementary
Carrier In Multicarrier
the number of
cells with
traffic-based
activation and
deactivation of
the slave carrier
function
enabled
NodeB
173
Configuring
Traffic-Based
Activation and
Deactivation of
the
Supplementar
y Carrier In
Multi-carrier
WRFD-010702
Enhanced DRX
Enhanced DRX
BSC6900
174
Configuring
Enhanced
DRX
WRFD-020500
Enhanced Fast
Dormancy
Fast Dormancy
Enhancement
(per PS Active
User)
BSC6900
175
Configuring
Enhanced Fast
Dormancy
WRFD-140205
Voice Service
Experience
Improvement
for Weak
Reception Ues
Voice Service
Experience
Improvement
for Weak
Reception Ues
BSC6900
176
Configuring
Voice Service
Experience
Improvement
for Weak
Reception UEs
WRFD-140206
Layered Paging
in URA_PCH
Layered Paging
in URA_PCH
BSC6900
177
Configuring
Layered
Paging in
URA_PCH
WRFD-020132
Web browsing
acceleration
Web Browsing
Acceleration
BSC6900
178
Configuring
Web browsing
acceleration
WRFD-020133
P2P
Downloading
Rate Control
during Busy
Hour
P2P Rate
Control
BSC6900
179
Configuring
P2P
Downloading
Rate Control
during Busy
Hour

34
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020116
Dynamic Power
Sharing in
Multi-Carriers
the number of
NodeBs with
PA-SHARING
function
enabled
NodeB
180
Configuring
Dynamic
Power Sharing
of MultiCarriers
WRFD-020117
Multi-Carrier
Switch off
Based on Traffic
Load
Multi-carrier
switch off based
on traffic load
BSC6900
181
Configuring
Multi-Carrier
Switch off
Based on
Traffic Load
WRFD-020118
Energy
Efficiency
Improved
the number of
NodeBs with
energy
efficiency
improved
function
enabled
NodeB
182
Configuring
Energy
Efficiency
Improved
WRFD-020119
Multi-Carrier
Switch off
Based on Power
Backup
the number of
NodeBs with
multi-carrier
switch off based
on power
backup function
enabled
NodeB
183
Configuring
Multi-Carrier
Switch off
Based on
Power Backup
WRFD-020122
Multi-Carrier
Switch off
Based on QoS
the number of
cells with multicarrier switch
off based on
QoS function
enabled
NodeB
184
Configuring
Multi-Carrier
Switch off
Based on QoS
WRFD-020121
Intelligent
Power
Management
the number of
NodeBs with
PSU Intelligent
Shutdown
function
enabled
NodeB
185
Configuring
Intelligent
Power
Management
WRFD-021304
RAN Sharing
Introduction
Package
RAN Sharing
Function
BSC6900
186
Configuring
RAN Sharing
Introduction
Package

35
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-021304
01
Dedicated
Carrier for Each
Operator
RAN Sharing
Function
BSC6900
187
Configuring
Dedicated
Carrier for
Each Operator
WRFD-021304
02
Flexible
Network
Architecture
RAN Sharing
Function
BSC6900
188
Configuring
Flexible
Network
Architecture
WRFD-021304
03
Mobility
Control and
Service
Differentiation
RAN Sharing
Function
BSC6900
189
Configuring
Mobility
Control and
Service
Differentiation
WRFD-021304
04
Independent
License Control
RAN Sharing
Function
BSC6900
190
Configuring
Independent
License
Control
WRFD-021304
05
Independent
Cell-level FM/
PM/CM
RAN Sharing
Function
BSC6900
None
WRFD-021304
06
Transmission
Recourse
Sharing on Iub/
Iur Interface
RAN Sharing
Function
BSC6900
None
WRFD-021305
RAN Sharing
Phase 2
RAN Sharing
Enhanced
Package
BSC6900
191
Configuring
RAN Sharing
Phase 2
WRFD-021305
01
Dedicated Iub
Transmission
Control
RAN Sharing
Enhanced
Package
BSC6900
192
Configuring
Dedicated Iub
Transmission
Control
WRFD-021303
IMSI Based
Handover
IMSI Based
Handover
BSC6900
193
Configuring
IMSI Based
Handover

36
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-021311
MOCN
Introduction
Package
MOCN
Introduction
Package
BSC6900
194
Configuring
MOCN
Introduction
Package
WRFD-021311
01
Carrier Sharing
by Operators
MOCN
Introduction
Package
BSC6900
195
Configuring
Carrier
Sharing by
Operators
WRFD-021311
02
Dedicated Node
B/Cell for
Operators
MOCN
Introduction
Package
BSC6900
196
Configuring
Dedicated
NodeB/Cell for
Operators
WRFD-021311
03
MOCN
Mobility
Management
MOCN
Introduction
Package
BSC6900
197
Configuring
MOCN
Mobility
Management
WRFD-021311
04
MOCN Load
Balance
MOCN
Introduction
Package
BSC6900
198
Configuring
MOCN Load
Balance
WRFD-021311
05
MOCN
Independent
Performance
Management
MOCN
Introduction
Package
BSC6900
None
WRFD-021311
06
Routing
Roaming UEs in
Proportion
MOCN
Introduction
Package
BSC6900
199
Configuring
Routing
Roaming UEs
in Proportion
WRFD-140223
MOCN Cell
Resource
Demarcatio
MOCN Cell
Resource
Demarcation
(per Cell)
BSC6900
200
Configuring
MOCN Cell
Resource
Demarcation
WRFD-021200
HCS
(Hierarchical
Cell Structure)
Hierarchical
Cell Structure
BSC6900
201
Configuring
HCS
(Hierarchical
Cell Structure)

37
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020111
One Tunnel
One Tunnel
BSC6900
202
Configuring
One Tunnel
WRFD-050405
Overbooking on
ATM
Transmission
ATM IUB
overbooking
Function
BSC6900
203
Configuring
Overbooking
on ATM
Transmission
WRFD-050105
ATM Switching
Based Hub
Node B
ATM Switching
Based Hub
NodeB (per
NodeB)
NodeB
204
Configuring
ATM
SwitchingBased Hub
NodeB
WRFD-050106
AAL2
Switching
Based Hub
Node B
ATM Switching
Based Hub
NodeB (per
NodeB)
NodeB
205
Configuring
AAL2
SwitchingBased Hub
NodeB
WRFD-050406
ATM QoS
Introduction on
Hub Node B
(Overbooking
on Hub Node B
Transmission)
HUB IUB
overbooking
Function
BSC6900
None
WRFD-050302
Fractional ATM
Function on Iub
Interface
Fractional ATM
BSC6900
None
WRFD-050402
IP Transmission
Introduction on
Iub Interface
IP
Transportation
in Iub Interface
BSC6900
206
Configuring IP
Transmission
Introduction
on Iub
Interface
WRFD-050411
Fractional IP
Function on Iub
Interface
Fractional IP
BSC6900
None
WRFD-050403
Hybrid Iub IP
Transmission
IUB Hybrid IP
Transportation
Function
BSC6900
207
Configuring
Hybrid Iub IP
Transmission

38
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-050404
ATM/IP Dual
Stack Node B
IUB ATM/IP
Dual Stack
Transportation
Function
BSC6900
208
Configuring
ATM/IP Dual
Stack NodeB
WRFD-050409
IP Transmission
Introduction on
Iu Interface
IP
Transportation
in Iu Interface
BSC6900
209
Configuring IP
Transmission
Introduction
on Iu Interface
WRFD-050410
IP Transmission
Introduction on
Iur Interface
IP
Transportation
in Iur Interface
BSC6900
210
Configuring IP
Transmission
Introduction
on Iur
Interface
WRFD-050420
FP MUX for IP
Transmission
FP MUX
BSC6900
211
Configuring
FP MUX for IP
Transmission
WRFD-050422
Dynamic
Bandwidth
Control of Iub
IP
Dynamic
Bandwidth
Control of Iub
IP
BSC6900
212
Configuring
Dynamic
Bandwidth
Control of Iub
IP
WRFD-050408
Overbooking on
IP Transmission
IP IUB
overbooking
Function
BSC6900
213
Configuring
Overbooking
on IP
Transmission
WRFD-050107
IP routing Based
Hub Node B
IP Routing
Based Hub
NodeB (per
NodeB)
NodeB
214
Configuring IP
Routing-Based
Hub NodeB
WRFD-011500
PDCP Header
Compression
(RFC2507)
PDCP Header
compression
BSC6900
215
Configuring
PDCP Header
Compression
(RFC2507)
WRFD-012001
RNC offload
(trial)
None
None
216
Configuring
RNC Offload

39
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-050412
UDP MUX for

Iu-CS
Transmission
UDP MUX for

Iu-CS
Transmission
BSC6900
217
Configuring
UDP MUX for
Iu-CS
Transmission
WRFD-140207
Iu/Iur
Transmission
Resource Pool
in RNC
Iu/Iur
Transmission
Resource Pool
in RNC
BSC6900
218
Configuring
Iu/Iur
Transmission
Resource Pool
in RNC
WRFD-140208
Iub
Transmission
Resource Pool
in RNC
Iub
Transmission
Resource Pool
in RNC
BSC6900
219
Configuring
Iub
Transmission
Resource Pool
in RNC
WRFD-050104
Satellite
Transmission
on Iub Interface
Satellite
Communication
in Iub Interface
BSC6900
220
Configuring
Satellite
Transmission
on Iub
Interface
WRFD-050108
Satellite
Transmission
on Iu Interface
Satellite
Transmission
on Iu Interface
BSC6900
221
Configuring
Satellite
Transmission
on Iu Interface
WRFD-050501
Clock Sync on
Ethernet in
Node B
the number of
NodeBs with IP
Clock function
enabled
NodeB
222
Configuring
Clock
Synchronizatio
n on Ethernet
in NodeB
WRFD-050502
Synchronous
Ethernet
The Number of
NodeBs with
Ethernet
Synchronizatio
n Function
Enabled
NodeB
223
Configuring
Synchronous
Ethernet

40
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-050425
Ethernet OAM
Ethernet
Operation and
Maintenance
Function (per
NodeB)
NodeB
224
Configuring
Ethernet OAM
WRFD-040202
RNC Node
Redundancy
RNC Node
Redundancy
BSC6900
225
Configuring
RNC Node
Redundancy
WRFD-040203
RRU
Redundancy
RRU Backup
(per Sector)
NodeB
226
Configuring
RRU
Redundancy
WRFD-021302
Iu Flex
IU FLEX
BSC6900
227
Configuring Iu
Flex
WRFD-021306
Iu Flex Load
Distribution
Management
Enhanced Iu
Flex
BSC6900
228
Configuring Iu
Flex Load
Distribution
Management
WRFD-010203
Transmit
Diversity
Transmit
Diversity (per
NodeB)
NodeB
229
Configuring
Transmit
Diversity
WRFD-010209
4-Antenna
Receive
Diversity
4-Antenna
Receive (per
NodeB)
NodeB
230
Configuring 4Antenna
Receive
Diversity
WRFD-021308
Extended Cell
Coverage up to
200km
None
None
231
Configuring
Extended Cell
Coverage up to
200km
WRFD-021309
Improved
Downlink
Coverage
Improved
Downlink
Coverage
BSC6900
None

41
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020138
HSUPA
Coverage
Enhancement at
UE power
limitation
HSUPA
Coverage
Enhancement at
UE power
limitation
BSC6900
232
Configuring
HSUPA
Coverage
Enhancement
at UE Power
Limitation
WRFD-021001
Flexible
frequency
bandwidth of
UMTS carrier
The number of
NodeBs with
flexible
frequency
separation
function
enabled
NodeB
233
Configuring
Flexible
frequency
bandwidth of
UMTS carrier
WRFD-010206
High Speed
Access
None
None
234
Configuring
High Speed
Access
WRFD-021350
Independent
Demodulation
of Signals from
Multiple RRUs
in One Cell
the number of
RRUs with in
independent
demodulation of
signals in one
cell
NodeB
235
Configuring
Independent
Demodulation
of Signals from
Multiple RRUs
in One Cell
WRFD-020302
Inter Frequency
Hard Handover
Based on
Coverage
Inter frequency
hard handover
BSC6900
236
Configuring
Inter
Frequency
Hard
Handover
Based on
Coverage
WRFD-020304
Inter Frequency
Hard Handover
Based on DL
QoS
Inter Frequency
Hard Handover
Based on DL
QoS
BSC6900
237
Configuring
Inter
Frequency
Hard
Handover
Based on DL
QoS

42
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020605
SRNS
Relocation
Introduction
Package
SRNS
Relocation (UE
Not Involved)
BSC6900
None
WRFD-020605
01
SRNS
Relocation (UE
Not Involved)
SRNS
Relocation (UE
Not Involved)
BSC6900
238
Configuring
SRNS
Relocation (UE
Not Involved)
WRFD-020605
02
SRNS
Relocation with
Hard Handover
SRNS
Relocation with
Hard Handover
BSC6900
239
Configuring
SRNS
Relocation
with Hard
Handover
WRFD-020605
03
SRNS
Relocation with
Cell/URA
Update
SRNS
Relocation with
Cell/URA
Update
BSC6900
240
Configuring
SRNS
Relocation
with Cell/URA
Update
WRFD-020605
04
Lossless SRNS
Relocation
Lossless SRNS
Relocation
BSC6900
None
WRFD-010615
Multiple RAB
Package
Multiple RAB
BSC6900
241
Configuring
Multiple RAB
Package (PS
RAB 2)
WRFD-010615
01
Combination of
Two PS
Services
Multiple RAB
BSC6900
242
Configuring
Combination
of Two PS
Services
WRFD-010615
02
Combination of
One CS Service
and Two PS
Services
Multiple RAB
BSC6900
243
Configuring
Combination
of One CS
Service and
Two PS
Services

43
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-010615
03
Combination of
Three PS
Services
Multiple RAB
BSC6900
244
Configuring
Combination
of Three PS
Services
WRFD-010615
04
Combination of
One CS Service
and Three PS
Services
Multiple RAB
BSC6900
245
Configuring
Combination
of One CS
Service and
Three PS
Services
WRFD-010615
05
Combination of
Four PS
Services
Multiple RAB
BSC6900
246
Configuring
Combination
of Four PS
Services
WRFD-020103
Inter Frequency
Load Balance
Inter frequency
load handover
BSC6900
247
Configuring
Inter
Frequency
Load Balance
WRFD-020114
Domain
Specific Access
Control
(DSAC)
Domain
Specific Access
Control
(DSAC)
BSC6900
248
Configuring
Domain
Specific Access
Control
(DSAC)
WRFD-020110
Multi
Frequency Band
Networking
Management
Multi
Frequency Band
Networking
Management
BSC6900
249
Configuring
Multi
Frequency
Band
Networking
Management
WRFD-020160
Enhanced
Multiband
Management
Enhancement
for Multi
frequency band
Networking
management
BSC6900
250
Configuring
Enhanced
Multiband
Management

44
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020400
DRD
Introduction
Package
None
None
251
Configuring
DRD
Introduction
Package
WRFD-020400
01
Intra System
Direct Retry
Intra System
Direct Retry
BSC6900
252
Configuring
Intra System
Direct Retry
WRFD-020400
02
Inter System
Direct Retry
Inter System
Direct Retry
BSC6900
253
Configuring
Inter System
Direct Retry
WRFD-020400
03
Inter System
Redirect
Inter System
Redirect
BSC6900
254
Configuring
Inter-System
Redirect
WRFD-020400
04
Traffic Steering
and Load
Sharing During
RAB Setup
None
None
255
Configuring
Traffic
Steering and
Load Sharing
During RAB
Setup
WRFD-020402
Measurement
Based Direct
Retry
Measurement
Based Direct
Retry Function
BSC6900
256
Configuring
Measurement
Based Direct
Retry
WRFD-020120
Service Steering
and Load
Sharing in RRC
Connection
Setup
Service Steering
in RRC
Connection
Setup
BSC6900
257
Configuring
Service
Steering and
Load Sharing
in RRC
Connection
Setup
WRFD-020124
Uplink Flow
Control of User
Plane
Uplink Flow
Control of User
Plane
BSC6900
258
Configuring
Uplink Flow
Control of User
Plane

45
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020104
Intra Frequency
Load Balance
Intra frequency
load balancing
BSC6900
259
Configuring
Intra
Frequency
Load Balance
WRFD-140211
Dynamic Target
RoT
Adjustment
Dynamic Target
ROT
Adjustment(per
Cell)
BSC6900
260
Configuring
Dynamic
Target ROT
Adjustment
WRFD-140212
CE
Overbooking
CE overbooking
(Per NodeB)
NodeB
261
Configuring
CE
Overbooking
WRFD-140213
Intelligent
Access Class
Control
Intelligent
Access Class
Control
BSC6900
262
Configuring
Intelligent
Access Class
Control
WRFD-140215
Dynamic
Configuration
of HSDPA CQI
Feedback
Period
Dynamic
Configuration
of HSDPA CQI
Feedback
Period (per Cell)
BSC6900
263
Configuring
Dynamic
Configuration
of HSDPA CQI
Feedback
Period
WRFD-140216
Load-based
Uplink Target
BLER
Configuration
Load-based
Uplink Target
BLER
Configuration
(per Cell)
BSC6900
264
Configuring
Load-based
Uplink Target
BLER
Configuration
WRFD-140217
Inter-Frequency
Load Balancing
Based on
Configurable
Load Threshold
Inter-Frequency
Load Balancing
Based on
Configurable
Load Threshold
(per Cell)
BSC6900
265
Configuring
InterFrequency
Load
Balancing
Based on
Configurable
Load
Threshold

46
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-070004
Load Based
GSM and
UMTS
Handover
Enhancement
Based on Iur-g
Handover
Based on Load
on Iur-g
BSC6900
266
Configuring
Load Based
GSM and
UMTS
Handover
Enhancement
Based on Iur-g
WRFD-070005
NACC
Procedure
Optimization
Based on Iur-g
NACC
Procedure
Optimization
Based on Iur-g
BSC6900
267
Configuring
NACC
(Network
Assisted Cell
Change)
Procedure
Optimization
Based on Iur-g
WRFD-070006
GSM and
UMTS Load
Balancing
Based on Iur-g
BSC Load
Balancing
Based on Iur-g
BSC6900
268
Configuring
GSM and
UMTS Load
Balancing
Based on Iur-g
WRFD-070007
GSM and
UMTS Traffic
Steering Based
on Iur-g
BSC Service
Distribution
Based on Iur-g
BSC6900
269
Configuring
GSM and
UMTS Traffic
Steering Based
on Iur-g
WRFD-020303
Inter-RAT
Handover
Based on
Coverage
Coverage Based
Inter-RAT
Handover
Between UMTS
and GSM/
GPRS
BSC6900
270
Configuring
Inter-RAT
Handover
Based on
Coverage
WRFD-020309
Inter-RAT
Handover
Based on DL
QoS
Inter-RAT
Handover
Based on DL
QoS
BSC6900
271
Configuring
Inter-RAT
Handover
Based on DL
QoS

47
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020307
Video
Telephony
Fallback to
Speech (AMR)
for Inter-RAT
HO
Video
Telephony
Fallback to
Speech (AMR)
for Inter-RAT
HO
BSC6900
272
Configuring
Video
Telephony
Fallback to
Speech (AMR)
for Inter-RAT
HO
WRFD-020308
Inter-RAT
Handover Phase
2
None
BSC6900
273
Configuring
Inter-RAT
Handover
Phase 2
WRFD-020308
01
NACC
(Network
Assisted Cell
Change)
NACC
(Network
Assisted Cell
Change)
BSC6900
274
Configuring
NACC
(Network
Assisted Cell
Change)
WRFD-020308
02
PS Handover
Between UMTS
and GPRS
PS Handover
Between UMTS
and GPRS
BSC6900
275
Configuring
PS Handover
between
UMTS and
GPRS
WRFD-020305
Inter-RAT
Handover
Based on
Service
Inter system
Service
Handover
BSC6900
276
Configuring
Inter-RAT
Handover
Based on
Service
WRFD-020306
Inter-RAT
Handover
Based on Load
Inter system
Load Handover
BSC6900
277
Configuring
Inter-RAT
Handover
Based on Load
WRFD-020401
Inter-RAT
Redirection
Based on
Distance
Inter System
Redirect Based
on Distance
BSC6900
278
Configuring
Inter-RAT
Redirection
Based on
Distance

48
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020310
3G/2G
Common Load
Management
3G/2G
Common Load
Management
BSC6900
279
Configuring
3G/2G
Common Load
Management
WRFD-020126
Mobility
Between UMTS
and LTE Phase
1
Mobility
Between UMTS
and LTE Phase
1
BSC6900
280
Configuring
Mobility
Between
UMTS and
LTE Phase 1
WRFD-020129
Service-Based
PS Service
Redirection
from UMTS to
LTE
Service-Based
PS Service
Redirection
from UMTS to
LTE
BSC6900
281
Configuring
Service-Based
PS Service
Redirection
from UMTS to
LTE
WRFD-140218
Service-Based
PS Handover
from UMTS to
LTE
PS Service
Redirection
from UMTS to
LTE
BSC6900
282
Configuring
Service-Based
PS Handover
from UMTS to
LTE
WRFD-140224
Fast CS
Fallback Based
on RIM
Fast CS
Fallback Based
on RIM
BSC6900
283
Configuring
Fast CS
Fallback Based
on RIM
WRFD-010505
Queuing and
Pre-Emption
Queuing and
Pre-emption
BSC6900
284
Configuring
Queuing and
Preemption
WRFD-021103
Access Class
Restriction
Access Class
Restriction
when SPU
overload
BSC6900
285
Configuring
Access Class
Restriction
WRFD-050424
Traffic Priority
Mapping onto
Transmission
Resources
Traffic Priority
Mapping on
Transport
BSC6900
286
Configuring
Traffic
Priority
Mapping onto
Transmission
Resources

49
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-020806
Differentiated
Service Based
on SPI Weight
Differentiated
Service Based
on SPI Weight
BSC6900
287
Configuring
Differentiated
Service Based
on SPI Weight
WRFD-020131
Optimization of
R99 and
HSUPA Users
Fairness
Optimization of
R99 and
HSUPA Users
Fairness
BSC6900
288
Configuring
Optimization
of R99 and
HSUPA Users
Fairness
WRFD-011502
Active Queue
Management
(AQM)
Active Queue
Management
(AQM)
BSC6900
289
Configuring
Active Queue
Management
(AQM)
WRFD-020128
Quality
Improvement
for Subscribed
Service
Quality
Improvement
for Subscribed
Service
BSC6900
290
Configuring
Quality
Improvement
for Subscribed
Service
WRFD-020123
TCP
Accelerator
TCP
Accelerator
BSC6900
291
Configuring
TCP
Accelerator
WRFD-010507
Rate
Negotiation at
Admission
Control
RAB
Downsizing at
Admission
Control
BSC6900
292
Configuring
Rate
Negotiation at
Admission
Control
WRFD-020130
Videophone
Service
Restriction
Videophone
Service
Restriction
BSC6900
293
Configuring
Videophone
Service
Restriction
WRFD-020135
Intelligent InterCarrier UE
Layered
Management
Intelligent InterCarrier UE
Layered
Management
(per Cell)
BSC6900
294
Configuring
Intelligent
Inter-Carrier
UE Layered
Management

50
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
WRFD-140219
Micro NodeB
Self-Planning
Micro NodeB
Self-Planning
(Per Cell)
NodeB
295
Configuring
Micro NodeB
Self-Planning
WRFD-140209
NodeB
Integrated
IPSec
NodeB
integrated IPSec
(Per NodeB)
NodeB
296
Configuring
NodeB
Integrated
IPSec
WRFD-140210
NodeB PKI
Support
NodeB PKI
support(Per
NodeB)
NodeB
297
Configuring
NodeB PKI
Support
WRFD-140220
Intelligent
Battery
Management
Intelligent
Battery
Management
(Per NodeB)
NodeB
298
Configuring
Intelligent
Battery
Management
MRFD-221801
Multi-mode
Dynamic Power
Sharing
(UMTS)
GSM and
UMTS
Dynamic Power
Sharing
NodeB
299
Configuring
Multi-mode
Dynamic
Power Sharing
(UMTS)
MRFD-221802
GSM and
UMTS
Dynamic
Spectrum
Sharing
(UMTS)
GSM and
UMTS
Dynamic
Spectrum
Sharing
(UMTS)(Per
NodeB)
NodeB
300
Configuring
GSM and
UMTS
Dynamic
Spectrum
Sharing
(UMTS)
MRFD-221501
IP-Based Multimode CoTransmission

on BS side
(NodeB)
None
None
301
Configuring
IP-Based
Multi-Mode
CoTransmission
on Base Station
Side (NodeB)

51
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
MRFD-221504
TDM-Based
Multi-mode CoTransmission
via Backplane
on BS side
(NodeB)
Multi Mode
BTS
Transmission
Sharing
NodeB
302
Configuring
TDM-Based
Multi-mode
CoTransmission
via Backplane
on BS side
(NodeB)
MRFD-221505
Bandwidth
sharing of
MBTS Multimode CoTransmission
(NodeB)
the number of
NodeBs with
Bandwidth
sharing of
MBTS Multimode CoTransmission
function
enabled
NodeB
None
MRFD-221601
Multi-mode BS
Common
Reference
Clock(NodeB)
None
None
303
Configuring
Multi-Mode
BS Common
Reference
Clock (NodeB)
MRFD-221602
Multi-mode BS
Common IPSec
(UMTS)
Co-IPSec
Between
GSM,UMTS
and LTE
(UMTS)
NodeB
304 Multimode BS
Common
IPSec(UMTS)
MRFD-221703
2.0MHz Central
Frequency point
separation
between GSM
and UMTS
mode(UMTS)
2.0MHz Central
Frequency point
separation
between GSM
and UMTS
mode(UMTS)
(Per NodeB)
NodeB
305
Configuring
2.0MHz
Central
Frequency
point
separation
between GSM
and UMTS
mode(UMTS)

52
RAN14.0
Issue 06 (2013-03-25)
Feature ID
Feature Name
License
Control Item
License
Configured
on...
Configuration
Method
MRFD-221803
Dynamic MA
for GU
Dynamic
Spectrum
Sharing
(UMTS)
Dynamic MA
for GU
Dynamic
Spectrum
Sharing
(UMTS)
NodeB
306
Configuring
Dynamic MA
for GU
Dynamic
Spectrum
Sharing
(UMTS)
MRFD-221804
GSM Power
Control on
Interference
Frequency for
GU Small
Frequency gap
(UMTS)
GSM Power
Control on
Interference
Frequency for
GU Small
Frequency gap
(UMTS)
NodeB
307
Configuring
GSM Power
Control on
Interface
Frequency for
GU Small
Frequency
Gap (UMTS)

53
RAN14.0
Overview of Configurations on the CME
About This Chapter

This section provides an overview of the configuration on the CME. The CME is a configuration
tool on GUIs assisting you to effectively configure the data about wireless NE features. You can
reconfigure configuration parameters by using the configuration expresses provided by the CME
to activate or deactivate specified features.
Feature activation and deactivation are mainly performed on the configuration expresses on the
CME. This part introduces the operations on the configuration expresses and you need to
understand the operations before activating or deactivating features.
3.1 Introduction to Configuration Methods
This section describes how to configure the features of one or multiple NEs at a time by using
the CME.
3.2 Configuring Device Data
This section describes how to configure device data on the device panel.
3.3 Introduction to the Configuration Express for UMTS Global Parameters
This section describes the structure and provides the configuration guidance to the configuration
express for UMTS global parameters.
3.4 Introduction to the Configuration Express for Iub Interfaces
express for Iub interfaces.
3.5 Introduction to the Configuration Express for Iu-CS Interfaces
express for Iu-CS interfaces.
3.6 Introduction to the Configuration Express for Iu-PS Interfaces
express for Iu-PS interfaces.
3.7 Introduction to the Configuration Express for Iur Interfaces
express for Iur interfaces.
3.8 Introduction to the Configuration Express for Iu-BC Interfaces
Issue 06 (2013-03-25)

54
RAN14.0
express for Iu-BC interfaces.
3.9 Introduction to the Configuration Express for Iu-PC Interfaces
express for Iu-PC interfaces.
3.10 Introduction to the Configuration Express for the (U)Iur-g Interface
express for the (U)Iur-g interface.
3.11 Introduction to the Configuration Express for Gi Interfaces
express for Gi interfaces.
3.12 Introduction to the Configuration Express for UMTS Global Radio Parameters
express for UMTS global radio parameters.
3.13 Introduction to the Configuration Express for UMTS Cells
express for UMTS cells.
3.14 Introduction to the Configuration Express for Neighboring UMTS Cells
express for neighboring UMTS cells.
3.15 Modifying RNC Parameters in Batches
This section describes how to change values of specified parameters for specified RNCs in
batches.
3.16 Modifying Logical NodeB Parameters in Batches
This section describes how to change values of specified parameters for specified logical NodeBs
in batches.
3.17 Modifying Physical NodeB Parameters in Batches
This section describes how to modify the data about multiple physical NodeBs in batches.
3.18 Modifying UMTS Cell Parameters in Batches
This section describes how to change values of specified parameters for specified UMTS cells
in batches.
3.19 Modifying RNC External Cell Parameters in Batches
This section describes how to change values of specified parameters for specified RNC external
cells in batches.
3.20 Modifying UMTS Channel Parameters in Batches
This section describes how to change values of specified parameters for specified UMTS
channels in batches.
3.21 Introduction to the Object Group Configuration
This section describes how to search for external cells in an object group and configure them.
Issue 06 (2013-03-25)

55
RAN14.0
3.1 Introduction to Configuration Methods

This section describes how to configure the features of one or multiple NEs at a time by using
the CME.
Introduction to Configuration Methods

The CME enables you to configure NE features in both single and batch modes. For details, see
Table 3-1.
Table 3-1 Introduction to configuration methods
Config
uratio
n
Metho
d
Characteristics
Single
configu
ration
Configures parameters for only one object (for example, a base station or a cell)
each time.
The CME provides configuration expresses and device panels for various types of
data to configure one object.
l The CME displays a navigation tree in the left pane and a table in the right pane.
The navigation tree shows managed objects (MOs) while the table shows the
parameters of the MOs and parameter values. After selecting an MO in the
navigation tree, you can configure its values in the table.
l The device panel is displayed on a GUI, allowing you to directly configure data
for devices such as cabinet, subrack, and board.
Batch
modific
ation
center
Applies the configuration data about an object (for example, a base station or a
cell) to other objects.
NOTE
This method is applicable to scenarios where the parameters for multiple objects need to be
configured the same.
For example, after setting the VAMOSSWITCH parameter for cell 1 to ON, you
can use the batch modification function to set the VAMOSSWITCH parameters
for other specified cells to ON at a time. By doing this, you do not need to configure
the parameters for these cells one by one.
Introduction to Data Configuration Procedures

Before using the CME to configure features, you need to be familiar with basic operations on
the CME. For details, see CME Guidelines in the M2000 Help.
The procedures for using the CME to activate or deactivate features are as follows:
1.
Synchronize the data in the current data area with the data on the live network.
2.
Create a planned data area and copy the data in the current data area to the planned data
area for configuration.
Issue 06 (2013-03-25)

56
RAN14.0
3.
Modify the parameters according to the planned data.
4.
After configuring data, export the data as scripts.
5.
Deliver the exported scripts to the live network for the configuration data to take effect on
NEs.
3.2 Configuring Device Data

This section describes how to configure device data on the device panel.
Right-click a BSC to be configured in the Main View navigation tree in the left pane, and choose
Device Panel from the shortcut menu. The NE device panel is displayed, as shown in Figure
3-1.
Figure 3-1 Device panel
Issue 06 (2013-03-25)

57
RAN14.0
Operatio
n
Operation description
Add
l In the upper-right part of the device panel window, click Add Cabinet.
l Right-click an empty subrack on the device panel window, and choose Add
Subrack from the shortcut menu.
l Right-click the empty slots on the panels of each subrack, and choose the
required board types from the shortcut menu.
Delete
l Right-click a cabinet to be deleted, and choose Delete Cabinet from the

shortcut menu.
l Right-click a subrack to be deleted, and choose Delete Subrack from the
shortcut menu.
l Right-click a board to be deleted, and choose Delete Board from the shortcut
menu.
View or
modify
Right-click a device to be viewed or modified, and choose Property to view or

modify the device.
3.3 Introduction to the Configuration Express for UMTS

Global Parameters
express for UMTS global parameters.
The configuration express provides a window for configuring RNC-level objects, as shown in
Figure 3-2.
Figure 3-2 Configuration express for UMTS global parameters
Issue 06 (2013-03-25)

58
RAN14.0
Configuration Guidance
1.
In area 1, choose The NE to be configured > UMTS > RNC in the Transport navigation
tree. The express window for configuring UMTS global parameters is displayed.
2.
In area 2, select an object to be configured in the Properties navigation tree. The

configuration parameters of the object are displayed in area 3.
TIP
In area 2, you can also type the parameters to be configured on the tab pages Parameter List and
Search. This helps to quickly locate parameters.
3.
In area 3, configure the data.
3.4 Introduction to the Configuration Express for Iub

Interfaces
express for Iub interfaces.
The configuration express provides a window for configuring interface-level objects, as shown
in Figure 3-3.
Figure 3-3 Configuration express for Iub interfaces
Issue 06 (2013-03-25)

59
RAN14.0
1.
In area 1, choose The NE to be configured > UMTS > Iub in the Transport navigation
tree. The express window for configuring Iub interfaces is displayed.
2.
In area 2, select a NodeB to be configured.
3.
In area 3, select an object to be configured in the navigation tree Properties. The

TIP
4.
In area 4, configure the parameters.
3.5 Introduction to the Configuration Express for Iu-CS

Interfaces
express for Iu-CS interfaces.
in Figure 3-4.
Figure 3-4 Configuration express for Iu-CS interfaces
1.
Issue 06 (2013-03-25)
In area 1, choose The NE to be configured > UMTS > Iu-CS in the Transport navigation
tree. The express window for configuring Iu-CS interfaces is displayed.
60
RAN14.0
2.

TIP
3.
3.6 Introduction to the Configuration Express for Iu-PS

Interfaces
express for Iu-PS interfaces.
in Figure 3-5.
Figure 3-5 Configuration express for Iu-PS interfaces
1.
In area 1, choose The NE to be configured > UMTS > Iu-PS in the Transport navigation
tree. The express window for configuring Iu-PS interfaces is displayed.
2.

TIP
Issue 06 (2013-03-25)

61
RAN14.0
3.
3.7 Introduction to the Configuration Express for Iur

Interfaces
express for Iur interfaces.
in Figure 3-6.
Figure 3-6 Configuration express for Iur interfaces
1.
In area 1, choose The NE to be configured > UMTS > Iur in the Transport navigation
tree. The express window for configuring Iur interfaces is displayed.
2.

TIP
3.
Issue 06 (2013-03-25)

62
RAN14.0
3.8 Introduction to the Configuration Express for Iu-BC

Interfaces
express for Iu-BC interfaces.
in Figure 3-7.
Figure 3-7 Configuration express for Iu-BC interfaces
1.
In area 1, choose The NE to be configured > UMTS > Iu-BC in the Transport navigation
tree. The express window for configuring Iu-BC interfaces is displayed.
2.

TIP
3.
Issue 06 (2013-03-25)

63
RAN14.0
3.9 Introduction to the Configuration Express for Iu-PC

Interfaces
express for Iu-PC interfaces.
in Figure 3-8.
Figure 3-8 Configuration express for Iu-PC interfaces
1.
In area 1, choose The NE to be configured > UMTS > Iu-PC in the Transport navigation
tree. The express window for configuring Iu-PC interfaces is displayed.
2.

TIP
3.
Issue 06 (2013-03-25)

64
RAN14.0
3.10 Introduction to the Configuration Express for the (U)

Iur-g Interface
express for the (U)Iur-g interface.
in Figure 3-9.
Figure 3-9 Configuration express for the (U)Iur-g interface
1.
In area 1, choose The NE to be configured > UMTS > Iur-g in the Transport navigation
tree. The configuration express window for configuring (U)Iur-g interfaces is displayed.
2.

TIP
3.
Issue 06 (2013-03-25)

65
RAN14.0
3.11 Introduction to the Configuration Express for Gi

Interfaces
express for Gi interfaces.
in Figure 3-10.
Figure 3-10 Configuration express for Gi interfaces
1.
In area 1, choose The NE to be configured > UMTS > Gi in the Transport navigation
tree. The express window for configuring Gi interfaces is displayed.
2.

TIP
3.
Issue 06 (2013-03-25)

66
RAN14.0

Global Radio Parameters
express for UMTS global radio parameters.
The configuration express provides a window for configuring BSC-level objects, as shown in
Figure 3-11.
Figure 3-11 Configuration express for UMTS global radio parameters
1.
In area 1, right-click a UMTS NE to be configured in the Main View navigation tree, and
choose UMTS Radio Global Configuration Express from the shortcut menu. The express
window for configuring UMTS global radio parameters is displayed.
2.

TIP
3.
Issue 06 (2013-03-25)

67
RAN14.0

Cells
express for UMTS cells.
The configuration express provides a window for configuring cell-level objects, as shown in
Figure 3-12.
Figure 3-12 Configuration express for UMTS cells
1.
In area 1, right-click a UMTS cell in the Main View navigation tree, and choose UMTS
Cell Configuration Express from the shortcut menu. The express window for configuring
UMTS cells is displayed.
2.
(Optional)In area 2, select a cell to be configured.
3.
In area 3, select an object to be configured in the navigation tree Properties. The

TIP
4.
Issue 06 (2013-03-25)

68
RAN14.0
3.14 Introduction to the Configuration Express for

Neighboring UMTS Cells
express for neighboring UMTS cells.
The configuration express provides a window for cell-level objects, as shown in Figure 3-13.
Figure 3-13 Configuration express for neighboring UMTS cells
1.
In area 1, right-click a UMTS cell in the Main View navigation tree, and then choose
UMTS Neighboring Cell Configuration Express. The express window for configuring
neighboring UMTS cells is displayed.
2.
(Optional)Select a source cell in area 2.
3.
Select the object to be configured in the Properties navigation tree in area 3.
4.
Select the corresponding Template and NE in area 4. Select one or multiple required
neighboring cells, and click Add. The information about the neighboring cell is displayed
in area 5.
5.
(Optional) Right-click the neighboring cell selected in area 5, and choose Modify NCell
Relationship from the shortcut menu to modify the information about the neighboring cell.
Issue 06 (2013-03-25)

69
RAN14.0
3.15 Modifying RNC Parameters in Batches

This section describes how to change values of specified parameters for specified RNCs in
batches.
Procedure
Step 1 In the configuration window, select a data record and click
objects is displayed.
. The dialog box for selecting
Step 2 Select RNCs to be modified in batches.

Step 3 Click Next. The dialog box for selecting parameters is displayed.
Step 4 Select parameters to be modified in batches.
NOTE
The dialog box displays only names and values of the parameters that can be changed in batches. You can
change parameter values as required.
The CME uses values of selected parameters as references to change parameter values of other specified
RNCs in batches.
Step 5 Click Next. The CME starts batch modification. After modification, the CME displays the
results.
Step 6 Click Finish.
----End
3.16 Modifying Logical NodeB Parameters in Batches

This section describes how to change values of specified parameters for specified logical NodeBs
in batches.
Procedure
Step 2 Click Add. Select the mode for adding NodeBs. For details, see Introduction to the Object
Selection Modes.
NOTE
NodeBs in batches.
Issue 06 (2013-03-25)

70
RAN14.0
results.
----End
3.17 Modifying Physical NodeB Parameters in Batches

This section describes how to modify the data about multiple physical NodeBs in batches.
Procedure
Step 1 In the Main View navigation tree in the left pane of the planned data area, right-click a UMTS
NE, and choose CM Express > UMTS Application > Physical NodeB Management > Modify
Physical NodeB Parameters in Bulk (M2000 Client Mode) or UMTS Application > Physical
NodeB Management > Modify Physical NodeB Parameters in Bulk (CME Client Mode)
from the menu bar. The Modify Physical NodeB Parameters in Bulk dialog box is displayed.
Step 2 Select an object to be modified and click Next. The data about the object for all physical NodeBs
in the planned data area is displayed in the lower part of the window. Select one or multiple
records, and click
Step 3 Click Next, and modify the parameters value of the selected object.
Step 4 Click Finish. The CME starts to modify the parameter value of the selected object.
Step 5 After the modification is complete, click Finish to exit the wizard.
After the automatic modification is complete, the CME displays a message, indicating whether
the modification is successful. If the modification fails, you need to locate and solve the problem
based on the displayed information.
----End
3.18 Modifying UMTS Cell Parameters in Batches

This section describes how to change values of specified parameters for specified UMTS cells
in batches.
Procedure
Step 2 Select cells to be modified in batches.

If you need to...
Then...
Modify all cells under an NE in batches
Select BY NE from the Select mode drop-down

list and select NEs in the NE list.
Issue 06 (2013-03-25)

71
RAN14.0
If you need to...
Then...
Modify specified cells under an NE in

batches
Select BY Cell from the Select mode drop-down

list, click Add, and select the mode for adding
cells based on site requirements. For details, see
Introduction to the Object Selection Modes.
NOTE
cells in batches.
results.
----End
3.19 Modifying RNC External Cell Parameters in Batches

This section describes how to change values of specified parameters for specified RNC external
cells in batches.
Procedure
Step 2 Select RNC external cells to be modified in batches.

If you need to...
Then...
Modify all RNC external cells under an Select BY NE from the Select mode drop-down
NE in batches
Issue 06 (2013-03-25)

72
RAN14.0
If you need to...
Then...
Modify specified RNC external cells

under an NE in batches
The following uses RNC 2G external cell as an

example.
Select BY GSMCELL from the Select mode
drop-down list, click Add, and select the mode for
adding RNC external cells based on site
requirements. For details, see Introduction to the
Object Selection Modes.
NOTE
l If you want to modify RNC 3G external cells, the
Select mode drop-down list displays BY
NRNCCELL.
l If you want to modify RNC LTE external cells, the
Select mode drop-down list displays By
LTECELL.
NOTE
RNC external cells in batches.
results.
----End
3.20 Modifying UMTS Channel Parameters in Batches

This section describes how to change values of specified parameters for specified UMTS
channels in batches.
Procedure
Step 2 Select cells to be modified in batches.

If you need to...
Then...
Modify all cells under an NE in batches
Select BY NE from the Select mode drop-down

Issue 06 (2013-03-25)

73
RAN14.0
If you need to...
Then...
Modify specified cells under an NE in

batches
Select BY Cell from the Select mode drop-down

list, click Add, and select the mode for adding
cells based on site requirements. For details, see
Introduction to the Object Selection Modes.
NOTE
cells in batches.
results.
----End
3.21 Introduction to the Object Group Configuration

This section describes how to search for external cells in an object group and configure them.
Figure 3-14 shows the window for configuring external cells.
Figure 3-14 Window for configuring external cells
Issue 06 (2013-03-25)

74
RAN14.0
1.
In area 1, select the BSC to be configured in the Main View navigation tree.
2.
In area 2, select the external cell to be configured in the Object Group navigation tree.
TIP
In area 2, you can also type the parameters to be set on the Search tab page. This helps quickly locate
parameters.
3.
Issue 06 (2013-03-25)

75
RAN14.0
Activating the UMTS License
About This Chapter

In the case of certain UMTS features, a license control item is defined for each feature. The
license control item of a feature must be activated before the configuration and use of the feature.
The license control items related to the RNC can be activated on the M2000 or RNC LMT,
whereas those related to the NodeB can be activated only on the M2000.
4.1 Activating the BSC6900 License
This section describes how to activate the BSC6900 license.
4.2 Allocating a license to Telecom Operators
When multiple telecom operators share one RAN, they can also share the resources defined in
a NodeB license after you allocate the license to the telecom operators.
4.3 Allocating a License to NodeBs
After uploading a NodeB license file of a RAN to the M2000 server, you need to allocate the
license to the NodeBs in the RAN. Then you can activate the license for it to take effect.
Issue 06 (2013-03-25)

76
RAN14.0
4.1 Activating the BSC6900 License

This section describes how to activate the BSC6900 license.
Prerequisites
l
The LMT is started and you have logged in to the BSC6900.
The BSC6900 is in service.
Procedure
Step 1 Run the BSC6900 MML command LST ESN and record the Equipment Serial Number (ESN)
of the BSC.
Step 2 Run the BSC6900 MML command DLD LICENSE to download the license file from the FTP
server to the \ftp\license directory of the main area directory of the OMU.
Step 3 Run the LST LICENSE command and enter the filename of the license to be activated to query
the file information.
If...
Then...
The file information complies with the information of Go to Step 4.

the file that you apply for,
The file information does not comply with the
information of the file that you apply for,
Exit the task and contact Huawei.
Step 4 Run the LST CFGMODE command to query the BSC6900 configuration status. If the
BSC6900 is ineffective, run the SET CFGDATAEFFECTIVE command to switch it to the
effective state.
Step 5 Run the ACT LICENSE command to activate the license.
Step 6 If the primary operator and secondary operators exist, run the SET LICENSE command to
active the license for the primary operator first and then for secondary operators. If multiple
secondary operators exist, run the SET LICENSE command repeatedly.
Step 7 Run the BSC6900 MML command CMP LICENSE to check whether the running license on
the host is consistent with that on the OMU.
If...
Then...
If the running license on the host is consistent with that End the task or go to Step 8.
on the OMU
If the running license on the host is inconsistent with
that on the OMU
Issue 06 (2013-03-25)

End the task and contact Huawei.
77
RAN14.0
Step 8 In the case of high traffic, run the SET LICENSECTRL command to enable the license control
function of the BSC6900 to enter the grace protection period.
----End
4.2 Allocating a license to Telecom Operators

When multiple telecom operators share one RAN, they can also share the resources defined in
a NodeB license after you allocate the license to the telecom operators.
Prerequisites
You have uploaded a valid NodeB license file to the M2000 server.
Procedure
Step 1 Choose License > NE License Management > NodeB License Management. The NodeB
License Management window is displayed.
Step 2 From the navigation tree in the left pane of the NodeB License Management window, select
an RNC node whose NodeB license file is already uploaded to the M2000 server.
Step 3 Right-click a license, and then choose License Distributed to Operator from the shortcut menu.
Step 4 In the License Distributed to Operator window, set available functions and resources for each
telecom operator, and then click OK.
----End
4.3 Allocating a License to NodeBs

After uploading a NodeB license file of a RAN to the M2000 server, you need to allocate the
license to the NodeBs in the RAN. Then you can activate the license for it to take effect.
Prerequisites
You have uploaded a valid NodeB license file to the M2000 server.
Procedure
Step 1 Choose License > NE License Management > NodeB License Management. The NodeB
License Management window is displayed.
Step 2 From the navigation tree in the left pane of the NodeB License Management window, select
an RNC node whose NodeB license file is already uploaded to the M2000 server.
Step 3 Optional: In the lower part of the license information area, click the tab of a telecom operator.
If a RAN is shared by multiple telecom operators, you can allocate a NodeB license to them by
referring to 4.2 Allocating a license to Telecom Operators.
The license allocation information about all the NodeBs related to the telecom operator is
displayed in a list.
Issue 06 (2013-03-25)

78
RAN14.0
Step 4 Double-click a NodeB to which you need to allocate the license, or right-click the NodeB and
choose Modify from the shortcut menu. Then, set available resources and functions for the
NodeB.
NOTE
l You can set a function control item to either 0 or 1. 0 indicates that the function is not enabled while
1 indicates that the function is enabled.
l You can hold down Ctrl or Shift to select multiple NodeBs at a time. Right-click the selected NodeBs,
and then choose Modify from the shortcut menu to set a control item value to all the selected NodeBs.
l If a control item is unavailable in the Modify dialog box, it indicates that the control item is not
supported by NodeBs. To view the values indicating that the control item is not supported by NodeBs,
click the status description on the right in the Modify dialog box. For descriptions of the values, see
Parameter Description in the dialog box.
l When setting a certain control item, you can click Clear to clear the preset values in the column of the
control item.
l You can click Settings in the Modify dialog box to add or delete one or multiple control items to be
set.
Step 5 Perform operations according to license allocation policies.

After a NodeB license file is uploaded to the M2000, you can allocate the license to NodeBs
immediately. You can also create a scheduled task for delivering preset license allocation
information to NodeBs at a certain non-busy hour. You can allocate an inactive license to
NodeBs. After an inactive license is allocated to NodeBs, it is activated automatically.
If you want to ...
Then ...
Allocate a license to NodeBs immediately 1. In the license information area, right-click a

license record, and then choose Distribute
from the shortcut menu.
2. In the displayed Message dialog box, click
Yes.
You can click Details to view the license
allocate information.
Deliver license allocation information to
NodeBs on a scheduled basis
1. In the license information area, right-click a

license record, and then chooseLicense
Distribute Task from the shortcut menu.
Alternatively, select the license record, and
then click
. The Task Management
window is displayed.
2. Set the parameters of the scheduled task for
delivering license allocation information.
----End
Issue 06 (2013-03-25)

79
RAN14.0
5 Configuring 3.4/6.8/13.6/27.2Kbps RRC Connection and

Radio Access Bearer Establishment and Release
Configuring 3.4/6.8/13.6/27.2Kbps RRC

Connection and Radio Access Bearer
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release.
Prerequisites
l
Dependencies on Hardware
This feature does not have any special requirements for hardware.
Dependencies on Other Features

This feature does not depend on other features.
License
This feature is not under license control.
Context
This feature enables RRC connection establishment and release and RAB assignment for
services of different rates, so as to meet different QoS requirements. This feature is fundamental
to service provision.
Procedure
l
Activation Procedure
1.
Run the BSC6900 MML command SET URRCESTCAUSE (CME single

configuration: UMTS Radio Global Configuration Express > Channel Type and
Rate of RRC Setup Cause Configuration > RRC Connection Establish Channel
Type And Bit Rate; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to set the channel type and bit rate corresponding to a specific
RRC connection establishment cause.
NOTE
Do not set Channel type for RRC establishment to FACH. Set Switch for RRC established
on E_FACH to OFF.
l
Issue 06 (2013-03-25)
Verification Procedure
80
RAN14.0

1.
Start Iub interface tracing on the BSC6900 LMT, as shown in Figure 5-1
Figure 5-1 Iub Interface Trace dialog box
2.
Establish a service on the UE. Among the traced Iub data, view the dCH-ID in the
DCH-Specific-FDD-Item IE in the NBAP_RL_SETUP_REQ message. The result
shows that the ID of the transport channel that carries signaling is 32.
3.
View the transmissionTimeInterval and nrOfTransportBlocks IEs in the ulTransportFormatSet IE associated with the DCH whose dCH-ID value is 32.
If the value of transmissionTimeInterval is 40, you can infer that an RRC
connection is established for a 3.4 kbit/s service.
If the value of transmissionTimeInterval is 20, you can infer that an RRC
connection is established for a 6.8 kbit/s service.
If the value of transmissionTimeInterval is 10 and the maximum value of
nrOfTransportBlocks is 1, you can infer that an RRC connection is established
for a 13.6 kbit/s service.
If the value of transmissionTimeInterval is 10 and the maximum value of
nrOfTransportBlocks is 2, you can infer that an RRC connection is established
for a 27.2 kbit/s service.
4.
Release the service on the UE, and perform Uu interface tracing. If you find an
RRC_RRC_CONN_REL_CMP message in the traced data, you can infer that the
RRC connection is released.
Deactivation Procedure
1.
This feature does not need to be deactivated.
----End
Example
//Activating 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer
Establishment and Release.
Issue 06 (2013-03-25)

81
RAN14.0

//set the channel type and bit rate corresponding to a specific RRC
connection establishment cause
SET URRCESTCAUSE: RrcCause=ORIGCONVCALLEST,
SigChType=DCH_3.4K_SIGNALLING, EFachSwitch=OFF;
Issue 06 (2013-03-25)

82
RAN14.0
Configuring Conversational QoS Class

Conversational QoS Class.
Prerequisites
l

License
Others
The UE and the CN support the conversational class.
Context
Based on QoS requirements, 3GPP defines four traffic classes: conversational, streaming,
interactive, and background.
They differ in their sensitivity to delay. The conversational class is highly sensitive to the delay
and therefore has a high requirement on real-time transmission. The conversational class has the
following fundamental characteristics:
l
Preservation of the time relationships between information entities in a stream and

limitation of the transmission delay and delay jitter within an acceptable range.
Conversational pattern (stringent requirement on the delay).
Conversational services are applicable in both the CS and PS domains. Most typical applications
of the conversational class are voice services and videophone services in the CS domain and
VoIP services in the PS domain.
Huawei RAN supports the following basic types of conversational services:
l
CS AMR speech services at the rates of 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7
kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s
CS transparent data services (conversational class) at the rates of 64 kbit/s, 56 kbit/s, 32

kbit/s, and 28.8 kbit/s
Issue 06 (2013-03-25)

83
RAN14.0
PS bidirectional symmetric voice services at the rates of 64 kbit/s, 42.8 kbit/s, 32 kbit/s, 16
kbit/s, and 8 kbit/s
Procedure
1.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA (CME single

configuration: UMTS Radio Global Configuration Express > Basic Resource
Control Parameter Configuration > Channel Type Parameters; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches). In this step, set
CS voice channel type and VOIP channel type to DCH(UL_DCH,DL_DCH).
1.
Initiate Iub interface tracing on the BSC6900 LMT, as shown in Figure 6-1.
Figure 6-1 Iub interface trace dialog box
2.
Establish a conversational service on the UE. Check the DPC (that is, the source) of
the RANAP_RAB_ASSIGNMENT_REQ message among the traced Iu data to
determine whether the service is a CS service or PS service.
3.
View the trafficClass IE in the rRB-Parameters IE of the

RANAP_RAB_ASSIGNMENT_REQ message to verify that the traffic class is
conversational.
4.
View the maxBitrate and rAB-AsymmetryIndicator IEs in the

RANAP_RAB_ASSIGNMENT_REQ message.
If the value of the rAB-AsymmetryIndicator IE is Asymmetric bidirectional,
then the maxBitrate IE contains two values. The first value indicates the downlink
rate of the conversational service, and the second indicates the uplink rate of the
service. That is, the uplink and downlink transmission uses asymmetric rates.
If the value of the rAB-AsymmetryIndicator IE is Symmetric bidirectional,
then the maxBitrate IE contains one value, which indicates the rate applicable in
both the uplink and the downlink. That is, the uplink and downlink transmission
uses symmetric rates.
If the value of the rAB-AsymmetryIndicator IE is Asymmetric Uni directional
downlink, then the maxBitrate IE contains one value, which indicates the
downlink rate of the conversational service. In this case, the uplink rate of the
service is 0.
Uplink, then the maxBitrate IE contains one value, which indicates the uplink
Issue 06 (2013-03-25)

84
RAN14.0
rate of the conversational service. In this case, the downlink rate of the service is
0.
5.
View the guaranteedBitRate (the guaranteed bit rate of the conversational service)
and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ
message by following the same rules as those for viewing maxBitrate.
1.
----End
Example
//Activating conversational QoS class
SET UFRCCHLTYPEPARA: CSVoiceChlType=DCH, VoipChlType=DCH;
Issue 06 (2013-03-25)

85
RAN14.0
Configuring Streaming QoS Class
Streaming QoS Class.
Prerequisites
l

License
Others
The UE and CN support streaming services.
Context
Based on QoS requirements, there are four traffic classes: conversational, streaming, interactive,
and background.
QoS indicates the sensitivity of services to the delay. The streaming class is a relatively recent
development in data communications, which raises a number of new requirements in both
telecommunication and data communication systems. The transmission of streaming services
must follow the time sequence of information entities . The streaming class has the following
features:
l
The time sequence of information entities in a stream is not changed.
Streaming services are applicable in both the CS and PS domains. The most typical
applications of the streaming class are fax services in the CS domain and streaming video
services in the PS domain.
Streaming services are real-time services, such as audio and video programs. They are
transmitted in only one direction and serve individual users.
Procedure
l
Issue 06 (2013-03-25)
86
RAN14.0
1.

modification center: 3.15 Modifying RNC Parameters in Batches) to set the
HSDPA/HSUPA rate threshold for streaming services. If the assigned rate of a
streaming service is lower than this threshold, the streaming service is set up on R99
channels.
NOTE
In the tests on 384 kbit/s streaming services, the settings of the thresholds cannot ensure that
the services are set up on R99 services. In this case, you can disable the HSDPA and HSUPA
capabilities of the cell to enable the streaming services to be set up on R99 channels.
2.
Optional: Run the BSC6900 MML command DEA UCELLHSDPA (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell
HSDPA Parameters. Set ACTSTATUS to Deactivated; CME batch modification
center: No supported) to disable the HSDPA capability of the cell.
3.
Optional: Run the BSC6900 MML command DEA UCELLHSUPA (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters >
Configuration of HSUPA in Cell. Set Cell HSUPA state to Deactivated; CME batch
modification center: No supported) to disable the HSUPA capability of the cell.
1.
Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 7-1
Figure 7-1 Iu Interface Trace dialog box
2.
Use a UE to set up a streaming service. Check the DPC (that is, the source) of the
RANAP_RAB_ASSIGNMENT_REQ message among the traced Iu data to
determine whether the service is a CS service or PS service.
3.
Check the RANAP_RAB_ASSIGNMENT_REQ message and check that the value

of the trafficClass information element (IE) in rRB-Parameters is streaming.
4.

Expected result:
the maxBitrate IE contains two values. The first value indicates the downlink rate
of the streaming service, and the second indicates the uplink rate of the service.
Issue 06 (2013-03-25)

87
RAN14.0
If the value of the rAB-AsymmetryIndicator IE is Symmetric bidirectional, the

maxBitrate IE contains one value, which indicates the rate in both the uplink and
the downlink. That is, the uplink and downlink transmission use the same rate.
downlink, the maxBitrate IE contains one value, which indicates the downlink
rate of the streaming service. In this case, the uplink rate of the service is 0.
Uplink, the maxBitrate IE contains one value, which indicates the uplink rate of
the streaming service. In this case, the downlink rate of the service is 0.
5.
View the guaranteedBitRate (the guaranteed bit rate of the streaming service) and
rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ
message by following the same rules as those for the maxBitrate IE.
1.
----End
Example
//Activating Streaming Class QoS
SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D384, UlStrThsOnHsupa=D384;
DEA UCELLHSDPA: CellId=1;
DEA UCELLHSUPA: CellId=1;
Issue 06 (2013-03-25)

88
RAN14.0
Configuring Interactive QoS Class
Interactive QoS Class.
Prerequisites
l

License
Others
The UE and CN support interactive services.
Context
and background. QoS indicates the sensitivity of services to the delay.
The interactive class is a typical data communication solution. It is characterized by the request/
response pattern of end users. For example, a person or an entity at the destination sends a data
request to a remote server and expects a response message within a specific time. In this situation,
the Round Trip Time (RTT) is one of the key attributes of the interactive class. Another
characteristic is that the packets should be transparently transferred at a low Bit Error Rate
(BER). In summary, the interactive class has the following fundamental characteristics: request/
response pattern and preservation of the payload.
Interactive services are applicable in the PS domain and not applicable in the CS domain. The
most typical application of the interactive class is web browsing.
Huawei RAN supports the following types of interactive services: PS bidirectional symmetric
or asymmetric interactive services at the rates of 384 kbit/s, 285 kbit/s, 144 kbit/s, 128 kbit/s,
64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.
Issue 06 (2013-03-25)

89
RAN14.0
Procedure
l
1.

HSDPA/HSUPA rate threshold for interactive services. If the assigned rate of an
interactive service is lower than this threshold, the interactive service is set up on R99
channels.
1.
2.
Use a UE to set up an interactive service. Check the

RANAP_RAB_ASSIGNMENT_REQ message and check that the value of the
trafficClass information element (IE) in rRB-Parameters is interactive.
3.

Expected result:
of the interactive service, and the second indicates the uplink rate of the service.
1.
----End
Example
//Activating Interactive QoS Class
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900,
UlBeTraffThsOnHsupa=D5440;
Issue 06 (2013-03-25)

90
RAN14.0
Configuring Background QoS Class
Background QoS Class.
Prerequisites
l

License
Others
The UE and CN support this feature.
Context
and background.
QoS indicates the sensitivity of services to the delay. A typical type of background service is
data services. One of the characteristics of the background class is that the destination does not
expect data within a specific time, and therefore the background class is delay-insensitive.
Another characteristic is that the packets should be transparently transferred at a low Bit Error
Rate (BER).
In summary, the background class has the following fundamental characteristics: destination not
expecting data within a specific time and preservation of the payload.
Background services are applicable in the PS domain and not applicable in the CS domain. The
most typical applications of the background class are download and emails.
Huawei RAN supports the following types of background services: PS bidirectional symmetric
or asymmetric background services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s,
64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.
Issue 06 (2013-03-25)

91
RAN14.0
Procedure
l
1.

HSDPA/HSUPA rate threshold for background services. If the assigned rate of a
background service is lower than this threshold, the background service is set up on
R99 channels.
1.
2.
Use a UE to set up a background service. Check the

RANAP_RAB_ASSIGNMENT_REQ message and check that the value of the
trafficClass information element (IE) in rRB-Parameters is background.
3.

Expected result:
of the background service, and the second indicates the uplink rate of the service.
1.
----End
Example
//Activating Background QoS Class
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900,
UlBeTraffThsOnHsupa=D5440;
Issue 06 (2013-03-25)

92
RAN14.0
10 Configuring Emergency Call
10
Configuring Emergency Call
Emergency Call.
Prerequisites
l

License
Context
This feature grants higher priority to emergency calls so that they are preferentially processed,
compared to normal calls.
CAUTION
If the license of the AMR-WB service is not activated on a RNC, ensure that AMR-WB is not
enabled for this RNC on the CS core network side. Otherwise, both the AMR-NB services and
emergency calls cannot be set up for the UE supporting AMR-WB.
Procedure
l
This feature need not be activated.
1.
Use a UE to initiate an emergency call.. The emergency call is successfully established.
This feature need not be deactivated.
----End
Issue 06 (2013-03-25)

93
RAN14.0
11 Configuring RAB Quality of Service Renegotiation over

Iu Interface
11
Configuring RAB Quality of Service

Renegotiation over Iu Interface
RAB Quality of Service Renegotiation over Iu Interface.
Prerequisites
l
The NEs in the core network must support selective configuration of the maximum bit
rate (MBR) and guaranteed bit rate (GBR).

License
Context
This feature enables the BSC6900 to initiate Iu renegotiation on the MBR and GBR of PS realtime services to reduce the rate of real-time services.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH (CME single

Algorithm Switches; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to enable the cell-level LDR algorithm. In this step, set Cell
LDC algorithm switch to UL_UU_LDR(Uplink UU LDR Algorithm),
DL_UU_LDR(Downlink UU LDR Algorithm), and CELL_CREDIT_LDR
(Credit LDR Algorithm).
2.
Run the BSC6900 MML command MOD UNODEBALGOPARA (CME single

configuration: NodeB Configuration Express > IUB_RNC > NodeB Basic
Information > NodeB Algorithm Parameters; CME batch modification center: 3.16
Modifying Logical NodeB Parameters in Batches) to enable the NodeB-level LDR
algorithm. In this step, set NodeB LDC algorithm switch to IUB_LDR(IUB LDR
94
RAN14.0

Iu Interface
Algorithm), LCG_CREDIT_LDR(LCG Credit LDR Algorithm), and

NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm).
Issue 06 (2013-03-25)
3.
Run the BSC6900 MML command MOD UCELLLDM (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Oriented LDM
Algorithm Parameters; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches) to set the cell-level LDR trigger threshold. In this step,
set UL/DL LDR Trigger threshold and DL State Trans Hysteresis threshold
according to the network plan.
4.
Run the BSC6900 MML command MOD UNODEBLDR (CME single

Information > NodeB LDR Algorithm Parameters; CME batch modification
center: 3.16 Modifying Logical NodeB Parameters in Batches) to set the NodeBlevel LDR credit spreading factor (SF) reserved threshold. In this step, set Ul LDR
Credit SF reserved threshold and Dl LDR Credit SF reserved threshold according
to the network plan.
5.
Run the BSC6900 MML command MOD UCELLLDR (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell LDR Algorithm
Parameters; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to set the NodeB credit LDR threshold for the local cell. In
this step, set Ul LDR Credit SF reserved threshold and DL LDR Credit SF
reserved threshold according to the network plan.
6.
Run the BSC6900 MML command SET ULDCPERIOD (CME single configuration:
UMTS Radio Global Configuration Express > Load Control Parameter
Configuration > RNC Oriented LDC Algorithm Cycle Length; CME batch
LDR period timer length according to the network plan.
7.
Parameters in Batches) to enable QoS renegotiation on real-time services. In this
step, set DL LDR first action to QOSRENEGO.
1.
Establish a PS streaming service.
2.
Trigger LDR in the cell according to the cell LDR threshold specified in the activation
procedure.
3.
If RAB MODIFY REQUEST is traced on the Iu interface, this feature has been
activated.
1.

Parameters in Batches) to disable the cell-level LDR algorithm. In this step, deselect
UL_UU_LDR(Uplink UU LDR Algorithm), DL_UU_LDR(Downlink UU LDR
Algorithm), and CELL_CREDIT_LDR(Credit LDR Algorithm) from the Cell
LDC algorithm switch drop-down list box.
2.

Modifying Logical NodeB Parameters in Batches) to disable the NodeB-level LDR
algorithm. In this step, deselect IUB_LDR(IUB LDR Algorithm),
95
RAN14.0

Iu Interface
LCG_CREDIT_LDR(LCG Credit LDR Algorithm), and

NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm) from the NodeB LDC
algorithm switch drop-down list box.
----End
Example
/*Activating RAB Quality of Service Renegotiation over Iu Interface*/
//Enabling the cell-level LDR algorithm
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=
UL_UU_LDR-1&DL_UU_LDR-1&CELL_CREDIT_LDR-1;
//Enabling the NodeB-level LDR algorithm
MOD UNODEBALGOPARA: NodeBName="NODEB1",
NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
//Enable QoS renegotiation on real-time services
MOD UCELLLDR: CellId=111, DlLdrFirstAction=QoSRenego;
/*Deactivating RAB Quality of Service Renegotiation over Iu Interface*/
//Disabling the cell-level LDR algorithm
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=
UL_UU_LDR-0&DL_UU_LDR-0&CELL_CREDIT_LDR-0;
//Disabling the NodeB-level LDR algorithm
MOD UNODEBALGOPARA: NodeBName="NODEB1",
Issue 06 (2013-03-25)

96
RAN14.0
12
Configuring 2-Way Antenna Receive

Diversity
2-Way Antenna Receive Diversity.
Prerequisites
l
In receive diversity mode, the NodeB should provide sufficient RF channels and
demodulation resources to meet the requirements for the number of antenna diversities.

License
Context
The 2-Antenna Receive Diversity is an effective approach of reducing signal attenuation by
using two antennas to receive a signal at the reception end, where two received signals are
combined after certain processing.
Procedure
l
1.
1.
Run the NodeB MML command ADD SEC (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Sector; CME batch
modification center: not supported). In this step, set Antenna Magnitude to 2.
Run the NodeB MML command LST SEC to query the value of Antenna
Magnitude.
Expected result: Antenna Magnitude is 2.
----End
Issue 06 (2013-03-25)

97
RAN14.0
Example
//Activation procedure
ADD SEC: STN=1, SECN=0, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE,
ANT1SRN=60, ANT1N=R0A, ANT2SRN=60, ANT2N=R0B;
//Verification procedure
LST SEC: STN=1, SECN=0;
Issue 06 (2013-03-25)

98
RAN14.0
13
Configuring Cell Digital Combination

and Split
Cell Digital Combination and Split.
Prerequisites
l
Only DBS3800/DBS3900 supports this feature, RRU3801c cannot support this feature.
Each RRU is configured with only one RX antenna.
It is not recommended that distributed sectors and non-distributed sectors are configured
on an RRU chain.
If distributed sectors are configured, one CPRI port supports a maximum of four
cascaded RRUs, a maximum of four RRUs share one cell, and a maximum of three
distributed cells are supported.
One BBU supports combination of uplink digital signals on only one CPRI port. A
maximum of four RRUs share one cell.
In consideration of delay requirements, the remote distance of fiber optic cables for the
RRUs in a cell and with the same coverage should be smaller than four kilometers.
RF modules, RRU3828 and RRU3829 can only support a maximum of four carriers
when they are implemented for Cell Digital Combination and Split.

License
Context
The feature enables multiple sectors to use the resources in the same cell, which improves system
spectrum efficiency and resource utilization. Compared with the analog combination and split,
the digital combination and split can provide higher capacity and wider coverage without
bringing additional noises or signal losses. Cell coverage can be adjusted simply through
software to adapt to actual traffic distribution and changes, which improves CE resource
utilization and operation benefits.
Issue 06 (2013-03-25)

99
RAN14.0
Procedure
l
1.
Run the NodeB MML command ADD RRUCHAIN (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Device Panel > Right click
TOPO > Add RXU Chain; CME batch modification center: not supported) to add
an RRU chain. In this step, set Topo Type to CHAIN.
2.
Run the NodeB MML command ADD RRU (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > TOPO > Right click RXU
CHAIN > Add RXU Board; CME batch modification center: not supported) to add
an RRU. In this step, set a group of RRUs in consecutive numbering to the RRUs to
be used by the distributed sector.
3.
modification center: not supported) to add a sector. In this step, set Sector Type to
DIST_SECTOR(DIST_SECTOR).
4.
Run the NodeB MML command ADD LOCELL (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > xx Sector > Locell; CME
batch modification center: 3.17 Modifying Physical NodeB Parameters in
Batches) to add a local cell. In this step, set Sector Type to DIST_SECTOR
(DIST_SECTOR).
1.
Run the NodeB MML command LST SEC. In this step, check that Sector Type is
set to DIST_SECTOR(DIST_SECTOR).
2.
Run the NodeB MML command LST LOCELL. In this step, check that Sector
Type is set to DIST_SECTOR(DIST_SECTOR).
----End
Example
1.
NodeB V200R014
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=2, HPN=0;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO;
ADD RRU: CN=0, SRN=61, SN=1, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=UO;
ADD SEC: STN=0, SECN=1, SECT=DIST_SECTOR, SRNB=60, SRNE=61;
ADD LOCELL: LOCELL=100, STN=0, SECN=1, SECT=DIST_SECTOR,
RRUMODE=SYNC, ULFREQ=9610, DLFREQ=10560, HISPM=FALSE;
LST LOCELL: MODE=LOCALCELL, LOCELL=100;
2.
NodeB V100R014
ADD RRUCHAIN: RCN=0, TT=CHAIN, HSN=0, HPN=0;
ADD RRU: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, RT=MRRU;
ADD RRU: CN=0, SRN=61, TP=TRUNK, RCN=0, PS=0, RT=MRRU;
ADD SEC: STN=0, SECN=1, SECT=DIST_SECTOR, SRNB=60, SRNE=61;
ADD LOCELL: LOCELL=100, STN=0, SECN=1, SECT=DIST_SECTOR,
BBPOOLTYPE=GEN_POOL, RRUMODE=SYNC, ULFREQ=9610, DLFREQ=10560,
HISPM=FALSE;
Issue 06 (2013-03-25)

100
RAN14.0

Issue 06 (2013-03-25)

101
RAN14.0
14 Configuring UE State in Connected Mode (CELL_DCH,

CELL_PCH, URA_PCH, CELL_FACH)
14
Configuring UE State in Connected
Mode (CELL_DCH, CELL_PCH, URA_PCH,

CELL_FACH)
UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).
Prerequisites
l

License
Other Prerequisites
The Iu-PS activity factor is already modified.
The Iu-PS activity factor can be modified by running the ADD TRMFACTOR (CME
single configuration: UMTS Global Configuration Express > Transmission
Resources Configuration > Factor Table; CME batch modification center: not
supported) and MOD ADJMAP (CME single configuration: IUPS Configuration
Express > IP Transport > Adjacent Node Mapping; CME batch modification center:
not supported) commands. The recommended value of the Iu-PS activity factor is 10%.
NOTE
If there are excessive users in the CELL_PCH or URA_PCH state, a large amount of bandwidth
on the Iu-PS interface is consumed though such users do not have data to transmit.
Adjusting the Iu-PS activity factor can prevent PS service admission failures due to the increase
in the number of UEs in the CELL_PCH or URA_PCH state.
The Fast Dormancy procedure of the UE must comply with 3GPP TS 25.331 CR3483.
UEs must support associated states.
Issue 06 (2013-03-25)

102
RAN14.0

Context
Huawei RAN supports four states of UEs in connected mode: CELL_DCH, CELL_PCH,
URA_PCH, and CELL_FACH. This feature helps save radio resources efficiently.
Procedure
l
A UE can directly enter the CELL_FACH or CELL_DCH state. It can enter the CELL_PCH
or URA_PCH state only through state transition from CELL_FACH or CELL_DCH. The
settings of state transition are as follows:
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single

configuration: UMTS Radio Global Configuration Express >
Connection_Oriented RRM Switch Configuration > Connection Oriented
Algorithm Switches; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches). In this step, select the
DRA_PS_BE_STATE_TRANS_SWITCH check box under the parameter
Dynamic Resource Allocation Switch.
2.
Optional: Run the BSC6900 MML command SET UCORRMALGOSWITCH

(CME single configuration: UMTS Radio Global Configuration Express >
Parameters in Batches). In this step, select the DRA_F2U_SWITCH check box
under the parameter Dynamic Resource Allocation Switch to enable state transition
from CELL_FACH to URA_PCH directly.
3.
Run the BSC6900 MML command SET UUESTATETRANSTIMER (CME single

configuration: UMTS Radio Global Configuration Express > UE State Transition
Parameter Configuration > RNC StateTrans Timer Parameters; CME batch
BE FACH or E_FACH to PCH Transition Timer and Cell Reselection Timer to
appropriate values.
4.
Run the BSC6900 MML command SET UUESTATETRANS (CME single

Parameter Configuration > UE State Translating Parameters; CME batch
Cell Reselection Counter Threshold to an appropriate value.
NOTE
l This feature involves the parameter settings of state transition from CELL_FACH or CELL_DCH to
CELL_PCH or URA_PCH. For the parameter settings of other types of state transition, see 17
Configuring Dynamic Channel Configuration Control.
l For the parameter settings related to fast dormancy, see 175 Configuring Enhanced Fast
Dormancy.
This feature cannot be verified separately. The state of a UE changes when it requests
different services. This is referred to as state transition. For details, see 17 Configuring
Dynamic Channel Configuration Control.
----End
Issue 06 (2013-03-25)

103
RAN14.0

Example
//Activating UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH,
CELL_FACH)
//Enabling status transition (CELL_FACH/CELL_PCH/URA_PCH)
SET UCORRMALGOSWITCH:
DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1&DRA_F2U_SWITCH-1;
//(Optional) Enabling state transition from CELL_FACH to URA_PCH directly
SET UUESTATETRANSTIMER: BeF2PStateTransTimer=65535,
CellReSelectTimer=180;
//Setting the parameters related to this feature
SET UUESTATETRANS: CellReSelectCounter=9;
Issue 06 (2013-03-25)

104
RAN14.0
15 Configuring Paging UE in Idle, CELL_PCH, URA_PCH

State (Type 1)
15
Configuring Paging UE in Idle,
CELL_PCH, URA_PCH State (Type 1)
Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1).
Prerequisites
l

License
Context
In paging type 1, the UTRAN sends a paging message to the UE in idle mode, CELL_PCH state,
or URA_PCH state through the paging control channel (PCCH).
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) with Dynamic Resource Allocation Switch set to
DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH and
DRA_PS_BE_STATE_TRANS_SWITCH.
2.
Run the BSC6900 MML command SET URRCTRLSWITCH (CME single

configuration: UMTS Radio Global Configuration Express > Process Switch
Configuration > Process Switch; CME batch modification center: 3.15 Modifying
RNC Parameters in Batches) to set the parameter Reserved parameter 1 to
RSVDBIT1_BIT21 (Reserved Parameter 1 Bit 21).
105
RAN14.0

State (Type 1)
3.

parameter BE FACH or E_FACH to PCH Transition Timer to 10
4.
Run the BSC6900 MML command SET UPSINACTTIMER (CME single

configuration: UMTS Radio Global Configuration Express > PS Permanent
Online Detection Timer Configuration > PS User Inactive Detecting Timer; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) to set
Interactive service T1 and Background service T1 to 1800.
5.
Run the BSC6900 MML command ADD TRMFACTOR (CME single configuration:
UMTS Global Configuration Express > Transmission Resources Configuration
> Factor Table; CME batch modification center: not supported) and MOD
ADJMAP (CME single configuration: NodeB Configuration Express >
IUB_RNC > ATM Transport > Adjacent Node Mapping; CME batch modification
center: not supported) to modify the Iu-PS activation factor. The recommended value
is 10%.
NOTE
l After this feature is activated, number of UEs in CELL_PCH or URA_PCH state will increase
sharply. These UEs consume a large number of Iu-PS resources although there is no service data
transmission.
l You can adjust the Iu-PS activation factor to avoid the PS admission failure due to increasing
number of UEs in CELL_PCH or URA_PCH state.
Verification Procedure (Paging a UE in Idle Mode)

1.
On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2.
Set parameters in the areas Cell Config, Uu Message Type, Trace Mode and Save
File. Then, click Submit.
3.
Power on UE1 and UE2, and camp on CELL1. Use UE2 to call UE1. The
RRC_PAGING_TYPE1 message should be displayed on the Trace Data tab page.
Commissioning Procedure (Paging a UE in CELL_PCH State)

1.
2.
On the HLR, set the PS service type to background or interactive.
3.
Establish an R99 PS service on UE1. The RRC_RB_SETUP message should be

displayed in trace data, and the value of the rrc-stateindicator IE should be
CELL_DCH.
4.
Do not send any data from UE1 for 30 seconds. Then, the network side should perform
UE1 transition to CELL_FACH state through the RRC_RB_RECFG message, and
the value of rrc-stateindicator IE should be CELL_FACH.
5.
Do not send any data from UE1 for another while. Then, the network side should
perform UE1 transition to CELL_PCH state through the RRC_RB_RECFG message,
and the value of rrc-stateindicator IE should be CELL_PCH.
6.
Use UE2 to call UE1. The RRC_PAGING_TYPE1 message should be displayed.
Verification Procedure (Paging a UE in URA_PCH)

1.
Issue 06 (2013-03-25)
106
RAN14.0

State (Type 1)
2.
Repeat step 3 through step 5 described in section "Paging a UE in URA_PCH" to

perform UE1 transition to CELL_PCH. Cause UE1 to perform a cell reselection
between CELL1 and CELL2. Cause UE1 to perform another cell reselection after the
Cell Reselection Timer[s] expires. Search for the last
RRC_CELL_UPDATE_CONFIRM message in trace data. The value of rrcstateindicator IE should be URA_PCH.
3.

NOTE
For details about how to enable UE transition to CELL_PCH or URA_PCH state, see 14
Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH,
CELL_FACH).
1.

RNC Parameters in Batches). In this step, deselect RSVDBIT1_BIT21 (Reserved
Parameter 1 Bit 21) from the Reserved parameter 1 drop-down list box.
2.

modification center: 3.15 Modifying RNC Parameters in Batches) to set BE FACH
or E_FACH to PCH Transition Timer to 65535. When this parameter is set to
65535, the FACH-to-PCH state transition is disabled.
3.

Interactive service T1and set Background service T1 to 20.
----End
Example
// Activation Procedure
//Setting the FACH/E_FACH-tO-PCH state transition timer for BE services
SET UUESTATETRANSTIMER: BeF2PStateTransTimer=10;
//Setting the PS inactive period detection timer for RNC
SET UPSINACTTIMER: PsInactTmrForInt=1800, PsInactTmrForBac=1800;
//Adding an activation factor
ADD TRMFACTOR: FTI=1, REMARK="Iu-PS", PSCONVDL=10, PSCONVUL=10,
PSSTRMDL=10, PSSTRMUL=10, PSINTERDL=10, PSINTERUL=10, PSBKGDL=10,
PSBKGUL=10;
//Modifying the mapping between activation factor and adjacent node
MOD ADJMAP: ANI=1, ITFT=IUPS, FTI=1;
//Enabling the cell update during CS service setup
SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT21-0;
// Deactivation Procedure
Issue 06 (2013-03-25)

107
RAN14.0

State (Type 1)
//Setting the FACH/E_FACH-tO-PCH state transition timer for BE services

//Setting the PS inactive period detection timer for RNC
//Disabling the cell update during CS service setup
Issue 06 (2013-03-25)

108
RAN14.0
16
16 Configuring Paging UE in CELL_FACH, CELL_DCH

State (Type 2)
Configuring Paging UE in CELL_FACH,

Paging UE in CELL_FACH, CELL_DCH State (Type 2).
Prerequisites
l

License
Context
In paging type 2, the UTRAN sends a paging message to the UE in CELL_FACH or CELL_DCH
state through the DCH or FACH.
Procedure
l
Issue 06 (2013-03-25)
1.
(Optional) Run the BSC6900 MML command SET UCORRMALGOSWITCH

Parameters in Batches) to turn on the RNC-oriented PS BE service state transition
switch.
2.

parameter BE DCH to FACH Transition Timer[s] to 30s.
3.

109
RAN14.0
16 Configuring Paging UE in CELL_FACH, CELL_DCH

State (Type 2)
inactivity detection timers for PS services.
l
Verification Procedure (Paging a UE in CELL_DCH State)

1.
2.
Set parameters in the areas Cell Config, Uu Message Type, Trace Mode and Save
File. Then, click Submit.
3.

CELL_DCH.
4.
Verification Procedure (Paging a UE in CELL_FACH State)

1.
2.
Set parameters in the areas Cell Config, Uu Message Type, and Save File, and then
click Submit. The Trace Data tab page is displayed.
3.
4.

CELL_DCH.
5.
Do not send any data from UE1 for 30 seconds. Then, you can view that the network
side performs UE transition to CELL_FACH state through the RRC_RB_RECFG
message. The value of rrc-stateindicator IE should be CELL_FACH.
6.
1.
----End
Example
//Activating paging type 2
SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1;
SET UUESTATETRANSTIMER: BeD2FStateTransTimer=30;
SET UPSINACTTIMER: PsInactTmrForInt=1440, ProtectTmrForInt=20,
PsInactTmrForBac=1440, ProtectTmrForBac=20;
Issue 06 (2013-03-25)

110
RAN14.0
17
Configuring Dynamic Channel

Configuration Control
Dynamic Channel Configuration Control (DCCC). (This feature cannot be configured using the
CME. )
Prerequisites
l
This feature does not depend on the hardware.

License
Context
This feature allows dynamic rate adjustment and UE state transition triggered by various reasons.
This improves the quality of services and increases resource utilization.
Procedure
l
Activating DCCC
1.
To activate the DCCC algorithm, perform the following steps:

Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH.
2.
To activate traffic-based BE service rate adjustment, perform the following steps:

a.
Run the BSC6900 MML command MOD UTYPRABDCCCMC to set the

following event 4A and 4B parameters:
Direction
Event4AThd
Event4BThd
TimetoTrigger4A
Issue 06 (2013-03-25)

111
RAN14.0
TimetoTrigger4B
PendingTime4A
PendingTime4B
b.
Run the BSC6900 MML command SET UDCCC to set the following RNClevel DCCC algorithm parameters:
DcccStg
UlRateUpAdjLevel
UlRateDnAdjLevel
DlRateUpAdjLevel
DlRateDnAdjLevel
UlDcccRateThd
DlDcccRateThd
UlMidRateCalc
DlMidRateCalc
UlMidRateThd
DlMidRateThd
3.
To activate throughput-based BE service rate adjustment, perform the following steps:

a.
Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this

step, set Dynamic Resource Allocation Switch to
DRA_THROUGHPUT_DCCC_SWITCH.
b.
Run the BSC6900 MML command SET UDCCC. In this step, set DCH Throu
Meas Period and HSUPA DCCC strategy.
c.
Run the BSC6900 MML command MOD UTYPRABDCCCMC to set the

following event 4B parameters for the DCH:
Period Amount to trigger 4B on DCH
Period Amount after trigger 4B on DCH
4.
To activate link-stability-based BE service rate adjustment, perform the following

steps:
a.
Run the BSC6900 MML command SET UQOSACT to set the RNC-level QoS
enhancement algorithm parameters. The parameters for ensuring link stability
are:
QOS Switch for BE Traffic
First Action for BE Uplink QOS
Second Action for BE Uplink QOS
Third Action for BE Uplink QOS
Wait Timer for BE Uplink Rate
First Action for BE Downlink QOS
Second Action for BE Downlink QOS
Third Action for BE Downlink QOS
Indicator for BE Uplink QOS Event
Srnc Parameter for BE Downlink RLC QOS
DRNC Parameter for BE Downlink RLC QOS
Issue 06 (2013-03-25)

112
RAN14.0
Measurement of 6A1 Switch

Measurement of 5A Switch
Measurement of 6D Switch
b.
Run the BSC6900 MML command SET UQUALITYMEAS to set the RNClevel QoS measurement parameters. The parameters for ensuring link stability
are:
BE Trigger Time 6A1
BE Trigger Time 6B1
BE Trigger Time 6A2
BE Trigger Time 6B2
BE Trigger Time 6D
UL Measurement Filter Coefficient
DL TCP Measurement Filter Coefficient
BE Trigger Time of Event E
BE Reporting Period Unit for Event E
BE Event E Reporting Period or BE Event E Reporting Period minute
BE Trigger Time of Event F
BE Reporting Period Unit for Event F
BE Event F Reporting Period or BE Event F Reporting Period minute
c.
Run the BSC6900 MML command MOD UCELLCAC to set the cell-level Call
Admission Control (CAC) algorithm parameters. The parameters for ensuring
link stability are:
Max UL TX power of interactive service
Max UL TX power of background service
NOTE
The BSC6900 defines default values for Max UL TX power of interactive service and
Max UL TX power of background service. Retain the default values in normal
situations.
d.
Run the BSC6900 MML command MOD UCELLRLPWR to set the cell-level
downlink transmit power parameters.
e.
Run the BSC6900 MML command MOD UCELLQUALITYMEAS to set the

cell-level QoS measurement parameters. The parameters for ensuring link
stability are:
BE Trigger Time 6A1
BE Trigger Time 6B1
BE Trigger Time 6A2
BE Trigger Time 6B2
BE Trigger Time 6D
BE Trigger Time of Event E
BE Reporting Period Unit for Event E
BE Event E Reporting Period
BE Trigger Time of Event F
Issue 06 (2013-03-25)

113
RAN14.0
BE Reporting Period Unit for Event F

BE Event E Reporting Period
NOTE
The BSC6900 defines default values for the preceding parameters. Retain the default
values in normal situations.
f.
Run the BSC6900 MML command MOD UTYPRABQUALITYMEAS to set

the following typical parameters for QoS measurement:
Uplink Event 6A1 Relative Threshold
Uplink Event 6A2 Relative Threshold
Uplink Event 6B1 Relative Threshold
Uplink Event 6B2 Relative Threshold
Statistic Block Number for 5A Event
Event 5A Threshold
Event 5A Interval Block Number
Event Ea Relative Threshold
Event Eb Relative Threshold
g.
Run the BSC6900 MML command MOD UTYPRABRLC to set Radio Link
Control (RLC) parameters for a typical Radio Access Bearer (RAB). The
parameters for ensuring link stability are:
Re-TX monitor period
Event A threshold
Hysteresis of Event A
Event A pending time after trigger
Filter Coefficient of RLC Retransmission Ratio
NOTE
The BSC6900 defines default values for the preceding parameters. Retain the default
values in normal situations.
h.
i.
j.
Issue 06 (2013-03-25)
Link stability control for BE services is implemented through Inter-frequency

handover.
a.
Run the BSC6900 MML command MOD UCELLHOCOMM. In this step,

set Inter-Frequency and Inter-RAT Coexist Switch to INTERFREQ.
b.
Run the BSC6900 MML command SET UCORRMALGOSWITCH. In

this step, set HandOver Switch to
HO_INTER_FREQ_HARD_HO_SWITCH.
To configure inter-RAT handover for the link stability of BE services, perform

the following steps:
a.

set Inter-Frequency and Inter-RAT Coexist Switch to INTERRAT and
Inter-RAT PS Handover Switch to ON.
b.

HO_INTER_RAT_PS_OUT_SWITCH.
To configure inter-frequency handover and inter-RAT handover for the link

stability of BE services, perform the following steps:
114
RAN14.0
k.
a.

set Inter-Frequency and Inter-RAT Coexist Switch to
SIMINTERFREQRAT and Inter-RAT PS Handover Switch to ON.
b.

HO_INTER_FREQ_HARD_HO_SWITCH and
Uplink Full Coverage Bit Rate
Downlink Full Coverage Bit Rate
l.
Run the BSC6900 MML command MOD UCELLDCCC to set the following
cell-level DCCC algorithm parameters:
Uplink Full Coverage Bit Rate
Downlink Full Coverage Bit Rate
NOTE
For details about the settings of measurement control parameters, see 110 Configuring TTI Switch
for BE Services Based on Coverage.
5.
Activating basic-congestion-based BE service rate adjustment

a.
Run the BSC6900 MML command SET UUSERGBR to set the guaranteed bit
rates (GBRs) for gold, silver, and copper users requesting interactive and
background services.
b.
Run the BSC6900 MML command SET UEDCHRATEADJUSTSET to set

HSUPA Uplink Rate Adjust Set.
c.
DCCC Rate Up Fail Time Threshold
DCCC Rate Up Fail Monitor Time length
DCCC Rate Up Fail Penalty Time Length
Activating the UE state transition algorithm

1.

turn on the following switches of Dynamic Resource Allocation Switch:
DRA_PS_BE_STATE_TRANS_SWITCH
DRA_PS_NON_BE_STATE_TRANS_SWITCH
DRA_F2U_SWITCH
DRA_HSDPA_STATE_TRANS_SWITCH
DRA_HSUPA_STATE_TRANS_SWITCH
NOTE
The HSDPA state transition license must be activated before the HSDPA state transition switch is
turned on.
Issue 06 (2013-03-25)
2.
Run the BSC6900 MML command SET UUESTATETRANS to set the measurement
control parameters of the UE state transition algorithm.
3.
Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the

timer parameters of the UE state transition algorithm.
115
RAN14.0
4.
l
Run the BSC6900 MML command SET UDCCC to set Low Activity Bit Rate
Threshold.
Activating always online

1.
Run the BSC6900 MML command SET UPSINACTTIMER to set the following
timer parameters for checking the low activity of PS users:
Conversational service T1
Streaming service T1
Interactive service T1
Background service T1
IMS signal T1
Conversational service T2
Streaming service T2
Interactive service T2
Background service T2
IMS signal T2
Verifying DCCC
1.
Traffic-based BE service rate adjustment

Set up an R99 BE service. Check whether the information element (IE)
trafficVolumeMeasurement exists in the RRC_MEAS_CTRL message traced on
the Uu interface, as shown in Figure 17-1. In addition, check whether the value of the
IE periodicalOrEventTrigger is eventTrigger (1), as shown in Figure 17-2.
Figure 17-1 IE trafficVolumeMeasurement
Figure 17-2 IE periodicalOrEventTrigger
2.
Throughput-based BE service rate adjustment

a.
Issue 06 (2013-03-25)
On the BSC6900 LMT, open the Monitor window. In the Monitor tab page,
double-click UMTS Monitoring > Connection Performance Monitoring.
Create UL Throughput Bandwidth and DL Throughput Bandwidth
monitoring tasks.
116
RAN14.0
b.
3.
Set up an R99 BE service and maintain the service without data operations. In
the Connection Performance Monitoring tab page, you can view the bandwidth
reduction in UL Throughput Bandwidth.
Link-stability-based BE service rate adjustment

Set up an R99 BE service. Check whether the value of measurementQuantity in the
RRC_MEAS_CTRL message traced on the Uu interface is ue-TransmittedPower
(0), as shown in Figure 17-3. In addition, check whether the value of the IE
periodicalOrEventTrigger is eventTrigger (1), as shown in Figure 17-4.
Figure 17-3 IE measurementQuantity
Figure 17-4 IE periodicalOrEventTrigger
4.
Basic-congestion-based BE service rate adjustment

a.
On the BSC6900 LMT, open the Monitor window. In the Monitor tab page,
double-click UMTS Monitoring > Connection Performance Monitoring.
Create UL Throughput Bandwidth and DL Throughput Bandwidth
monitoring tasks.
b.
Set up an R99 BE service. Run the BSC6900 MML command DSP

UCELLCHK to check the cell congestion status on the Uu interface (the cell is
in the basic congestion state). You can view the bandwidth decrease in UL
Throughput Bandwidth in the Connection Performance Monitoring tab
page.
Verifying the UE state transition algorithm

Set up an R99 BE service and maintain the service without data operations. Check whether
the value of rrc-StateIndicator in the traced RRC_RB_RECFG message is cell-FACH
(1), as shown in Figure 17-5.
Figure 17-5 IE rrc-StateIndicator
Verifying always online

Set up an R99 BE service and maintain the service without data operations. The message
RRC_RB_REL is not traced on the Uu interface.
l
Issue 06 (2013-03-25)
117
RAN14.0
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the
related switches.
2.

set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH.
----End
Example
//Activating DCCC
//Activating the DCCC algorithm
SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1;
//Activating traffic-based BE service rate adjustment
MOD UTYPRABDCCCMC: RabIndex=1, Direction=DOWNLINK, Event4aThd=D1024,
Event4bThd=D16, TimetoTrigger4A=D240, PendingTime4A=D4000,
TimetoTrigger4B=D2560, PendingTime4B=D4000;
SET UDCCC: UlDcccRateThd=D64, DlDcccRateThd=D64,
DcccStg=RATE_UP_AND_DOWN_ON_DCH, UlRateUpAdjLevel=3_Rates,
UlRateDnAdjLevel=3_Rates, UlMidRateCalc=HAND_APPOINT, UlMidRateThd=D128,
DlRateUpAdjLevel=3_Rates, DlRateDnAdjLevel=3_Rates,
DlMidRateCalc=HAND_APPOINT, DlMidRateThd=D128;
//Activating throughput-based BE service rate adjustment
SET UCORRMALGOSWITCH: DraSwitch=DRA_THROUGHPUT_DCCC_SWITCH-1;
SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH, DchThrouMeasPeriod=100;
MOD UTYPRABDCCCMC: RabIndex=1, Direction=UPLINK, Event4bThd=D64,
DchThrouTimetoTrigger4B=2, DchThrouPendingTime4B=16;
SET UUESTATETRANS: E2FThrouMeasPeriod=30;
//Activating link-stability-based BE service rate adjustment
//Setting the QoS-related parameters
SET UQOSACT: BEQosPerform=YES, BeUlAct1=RateDegrade,
BeUlAct2=InterFreqHO, BeUlAct3=InterRatHO, BeDlAct1=RateDegrade,
BeDlAct2=InterFreqHO, BeDlAct3=InterRatHO, BeUlEvTrigInd=SINGLE,
SrncBeDlRlcQosSwitch=YES, DrncBeDlRlcQosSwitch=YES,
BeUlQos6A1McSwitch=YES, BeUlQos5AMcSwitch=YES, BeUlQos6DMcSwitch=YES;
SET UQUALITYMEAS: UlBeTrigTime6A1=D640, UlBeTrigTime6B1=D2560,
UlBeTrigTime6A2=D1280, UlBeTrigTime6B2=D1280, UlBeTrigTime6D=D240,
UlMeasFilterCoef=D19, DlMeasFilterCoef=D1, DlBeTrigTimeE=64,
ChoiceRptUnitForBeE=TEN_MSEC, TenMsecForBeE=480, DlBeTrigTimeF=64,
ChoiceRptUnitForBeF=TEN_MSEC, TenMsecForBeF=480;
MOD UCELLRLPWR: CellId=1, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200,
RLMAXDLPWR=-30, RLMINDLPWR=-180, DLSF=D128;
MOD UTYPRABQUALITYMEAS: RabIndex=1, UlThd6a1=1, UlThd6a2=5, UlThd6b1=1,
UlThd6b2=5, StaBlkNum5A=500, Thd5a=280, HangBlockNum5a=512, ThdEa=2,
ThdEb=2;
MOD UTYPRABRLC: RabIndex=1, SubflowIndex=0, TrchType=TRCH_DCH,
OppositeTrchType=TRCH_DCH, DelayClass=1, RlcMode=AM,
AmRlcCfgPara=FLOWCONTROL_PARA, TimeToMoniter=6000, MoniterPrd=1000,
ReTransRatioFilterCoef=1, EventAThred=160, TimeToTriggerA=2,
PendingTimeA=1;
//Configuring inter-frequency handover for the link stability of BE
services
MOD UCELLHOCOMM: CellId=1, InterFreqRATSwitch=INTERFREQ,
CoexistMeasThdChoice=COEXIST_MEAS_THD_CHOICE_INTERFREQ,
CSServiceHOSwitch=OFF, PSServiceHOSwitch=OFF;
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1;
//Configuring inter-RAT handover for the link stability of BE services
MOD UCELLHOCOMM: CellId=1, InterFreqRATSwitch=INTERRAT,
CoexistMeasThdChoice=COEXIST_MEAS_THD_CHOICE_INTERFREQ,
CSServiceHOSwitch=OFF, PSServiceHOSwitch=ON;
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_OUT_SWITCH-1;
//Setting the DCCC algorithm parameters
Issue 06 (2013-03-25)

118
RAN14.0
SET UDCCC: UlFullCvrRate=D64, DlFullCvrRate=D64;

MOD UCELLDCCC: CellId=1, UlFullCvrRate=D64, DlFullCvrRate=D64;
//Activating basic-congestion-based BE service rate adjustment
SET UUSERGBR: TrafficClass=INTERACTIVE, THPClass=High, BearType=R99,
UserPriority=GOLD, UlGBR=D16, DlGBR=D16;
SET UEDCHRATEADJUSTSET:
EdchRateAdjustSet=RATE_144KBPS-1&RATE_384KBPS-1&RATE_1280KBPS-1;
SET UDCCC: FailTimeTh=4, MoniTimeLen=60, DcccUpPenaltyLen=30;
//Activating the UE state transition algorithm
DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-1&DRA_HSUPA_DCCC_SWITCH-1&DRA_PS_B
E_STATE_TRANS_SWITCH-1&DRA_PS_NON_BE_STATE_TRANS_SWITCH-1&DRA_F2U_SWITCH1;
SET UUESTATETRANS: CellReSelectCounter=9, D2F2PTvmThd=D64,
D2FTvmTimeToTrig=D5000, D2FTvmPTAT=D1000, F2PTvmTimeToTrig=D5000,
F2PTvmPTAT=D16000, BeF2DTvmThd=D1024, BeF2DTvmTimeToTrig=D0,
BeH2FTvmThd=D64, BeH2FTvmTimeToTrig=D5000, BeH2FTvmPTAT=D1000,
BeF2HTvmThd=D1024, BeF2HTvmTimeToTrig=D0, E2FThrouMeasPeriod=30,
E2FThrouThd=8, E2FThrouTimeToTrig=2, E2FThrouPTAT=4, BeF2ETvmThd=D1024,
BeF2ETvmTimeToTrig=D0, BeF2CpcHTvmThd=D1024, BeF2CpcHTvmTimeToTrig=D0,
BeF2CpcETvmThd=D1024, BeF2CpcETvmTimeToTrig=D0, BeEFach2DTvmThd=D1024,
BeEFach2DTvmTimeToTrig=D0, BeEFach2HTvmThd=D1024,
BeEFach2HTvmTimeToTrig=D0, BeEFach2CpcTvmThd=D1024,
BeEFach2CpcTvmTimeToTrig=D0, FastDormancyF2DHTvmThd=D3k;
SET UUESTATETRANSTIMER: CellReSelectTimer=180, BeD2FStateTransTimer=5,
BeF2PStateTransTimer=5, BeH2FStateTransTimer=5, BeE2FStateTransTimer=5,
BeCpc2FStateTransTimer=5, BeD2EFachStateTransTimer=5,
BeH2EFachStateTransTimer=5, BeCpc2EFachStateTransTimer=5;
SET UDCCC: LittleRateThd=D64;
//Activating always online
SET UPSINACTTIMER:PsInactTmrForInt=240, ProtectTmrForInt=10,
PsInactTmrForBac=240, ProtectTmrForBac=10, PsInactTmrForCon=240,
ProtectTmrForCon=10,PsInactTmrForStr=240, ProtectTmrForStr=10,
PSInactTmrForImsSig=3600, ProtectTmrForImsSig=10;
//Deactivating DCCC
Issue 06 (2013-03-25)

119
RAN14.0
18
Configuring Integrity Protection
Integrity Protection.
Prerequisites
l

License
Context
This feature protects the network and user data from being listened and modified illegally.
Procedure
l
1.
l
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UUIA (CME single configuration: UMTS
Radio Global Configuration Express > Security Mode Configuration > Integrity
Protection Algorithm; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to enable the RNC to support the integrity protection
algorithm.
1.
On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu
Interface Trace. The Iu Interface Trace dialog box is displayed.
2.
Keep UE1 and UE2 in idle mode in CELL1.
3.
Use UE2 to call UE1.
4.
The messages RANAP_SECURITY_ MODE_COMMAND and

RANAP_SECURITY_MODE_COMPLETE should be displayed. The
chosenIntegrityProtectionAlgorithm IE of the latter message indicates the integrity
protection algorithm.
120
RAN14.0
1.
----End
Example
//Activating integrity protection
SET UUIA: IntegrityProtectAlgo=UIA1-1;
Issue 06 (2013-03-25)

121
RAN14.0
19
Configuring Encryption
Encryption.
Prerequisites
l

License
Context
The encryption algorithms supported by Huawei RAN include UEA0 and UEA1.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UUEA (CME single configuration: UMTS
Radio Global Configuration Express > Security Mode Configuration >
Encryption Algorithm; CME batch modification center: not supported) to enable the
RNC to support the encryption algorithm.
1.
2.
3.
Use UE2 to call UE1.
4.
The messages RANAP_SECURITY_ MODE_COMMAND and

chosenEncryptionAlgorithm IE of the latter message indicates the encryption
algorithm.
5.
End the calling. UE1 and UE2 return to the idle mode.
122
RAN14.0
6.
The messages RANAP_SECURITY_MODE_COMMAND and

chosenEncryptionAlgorithm IE of the latter message indicates the encryption
algorithm.
1.
----End
Example
//Activating encryption
SET UUEA: EncryptionAlgo=UEA0-1&UEA1-1;
Issue 06 (2013-03-25)

123
RAN14.0
20
Configuring Open Loop Power Control

Open Loop Power Control.
Prerequisites
l

License
Context
This feature enables BSC6900 to roughly estimate path loss based on power measurement
results, network parameter settings, and QoS requirements. Based on the estimation results,
BSC6900 sets the initial transmit power for a UE and a NodeB before connection is established
between them.
Procedure
l
Activate open loop power control on the downlink DPCH.
1.
This feature does not need to be activated on the downlink DPCH.
Activate open loop power control on the uplink DPCH.

1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UFRC (CME single configuration: UMTS
Radio Global Configuration Express > Basic Resource Control Parameter
Configuration > RNC Oriented FRC Algorithm Parameters; CME batch
the parameters related to uplink DPCH power control.

124
RAN14.0

NOTE
l The BSC6900 uses the Default Constant Value parameter to calculate the power offset
on the uplink DPCCH (DPCCH_Power_offset). Based on the calculation result, the UE
calculates the initial transmit power on the uplink DPCCH (DPCCH_Initial_Power).
l The formula for calculating DPCCH_Power_offset is: DPCCH_Power_offset = Primary
CPICH DL TX power + UL interference + Default Constant Value. Where,
DPCCH_Power_offset indicates the initial transmit power offset on the DPCCH, Primary
CPICH DL TX power indicates the downlink transmit power on the P-CPICH, UL
interference indicates the uplink interference, and Default Constant Value is the value of
Default Constant Value.
l The formula for calculating DPCCH_Initial_Power is: DPCCH_Initial_Power =
DPCCH_Power_offset - CPICH_RSCP. Where, CPICH_RSCP indicates the received
signal code power (RSCP) that the UE measures on the P-CPICH. An excessively small
value of DPCCH_Power_offset may lead to uplink synchronization failures at the cell edge
during initial link establishment, which affects uplink coverage. An excessively great value
of DPCCH_Power_offset may lead to instantaneous interference on uplink signal
reception, which affects the uplink receiving performance. For details, see 3GPP TS 25.331.
Activate open loop power control on the uplink PRACH.

1.
Run the BSC6900 MML command MOD UPRACHUUPARAS (CME single

configuration: UMTS Cell Configuration Express > Channel Configuration >
PRACH Basic Information; CME batch modification center: not supported). In this
step, set the parameters related to the PARCH to appropriate values.
Verify open loop power control on the downlink DPCH
1.
Use UE 2 to establish a conversation with UE 1.
2.
The message NBAP_RL_SETUP_REQ on the Iub interface shows the value of the
IE initialDL-transmissionPower. This value is used for the downlink DPCH open
loop power control.
Verify open loop power control on the uplink DPCH

1.
Check the IE dpcch-PowerOffset, whose value is the same as that of DPCCH Power
Offset, under the IE ul-DPCH-PowerControlIonfo contained in the RRC message
RRC Connection Setup, as shown in Figure 20-1. Based on the dpcch-PowerOffset
value, the UE can further calculate the initial transmit power on the uplink DPCCH
(DPCCH_Initial_Power) and perform uplink open loop power control.
Figure 20-1 ul-DPCH-PowerControlIonfo IE
Verify open loop power control on the uplink PRACH

1.
Issue 06 (2013-03-25)
Check whether the IE constantValue whose value is -20 is contained in the

RRC_SYS_INFO_TYPE5 message by referring to Tracing Messages on the Uu
Interface. If the message contains this IE, parameters configured for the UE take effect.
After obtaining values of these parameters, the UE calculates the initial transmit power
and performs open look power control on the uplink PARCH.
125
RAN14.0
1.
----End
Example
//Activating open loop power control on the uplink DPCH
SET UFRC: DefaultConstantValue=-22;
//Activating open loop power control on the uplink PRACH
MOD UPRACHUUPARAS: CellId=111, PhyChId=1, Constantvalue=-20,
PowerRampStep=2, PreambleRetransMax=20;
Issue 06 (2013-03-25)

126
RAN14.0
21
Configuring Downlink Power Balance
Downlink Power Balance.
Prerequisites
l

License
Context
In soft handover, error codes in a TPC command may lead to downlink transmit power drift.
The downlink power balance feature solves the problem of power imbalance between links,
thereby achieving best gain in soft handover. The greater the downlink transmit power drift, the
smaller the macro diversity gain. Downlink power balance adjusts power drift and improves
performance of soft handover.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches). In this step, set Power Control Switch to
PC_DOWNLINK_POWER_BALANCE_SWITCH.
1.
On the BSC6900 LMT, choose Trace > UMTS Services and double-click Uu
2.
Set Cell Config, Uu Message Type, and Save File. Then click Submit.
3.
Move a UE from cell 1 to cell 2 to ensure that the UE performs a soft handover.
127
RAN14.0
4.
Check whether the active cell set update is complete in the traced Uu-interface
messages. Figure 21-1 shows the expected result.
Figure 21-1 RRC_ACTIVE_SET_UPDATE_CMP message traced in Uu interface message

tracing
5.
Start Iub interface message tracing on the BSC6900 LMT. Check the value of the
information element dedicatedMeasurementType in the
NBAP_DEDIC_MEAS_INIT_REQ message.
Expected result: the value of dedicatedMeasurementType is transmitted-codepower(2) shown in Figure 21-2.
Figure 21-2 Information element dedicatedMeasurementType
1.

Parameters in Batches). In this step, set
PC_DOWNLINK_POWER_BALANCE_SWITCH to 0.
----End
Example
//Activating downlink power balance SET UCORRMALGOSWITCH:
PcSwitch=PC_DOWNLINK_POWER_BALANCE_SWITCH-1;
//Deactivating downlink power balance SET UCORRMALGOSWITCH:
PcSwitch=PC_DOWNLINK_POWER_BALANCE_SWITCH-0;
Issue 06 (2013-03-25)

128
RAN14.0
22
Configuring Outer Loop Power Control

Outer Loop Power Control.
Prerequisites
l

License
Context
Outer loop power control guarantees the service quality by adjusting the target SIR of inner loop
power control. Outer loop power control is performed on the DCHs carrying the same RRC
connection. When the moving speed of a UE or the multi-path environment changes, the target
SIR needs to be adjusted to ensure a desirable service quality. Otherwise, the service quality
may be bad or will accordingly lead to severe interference and power waste.
The legacy OLPC algorithm enables the target SIR to quickly increase but slowly decrease,
therefore leading to a waste of uplink power. The optimized OLPC algorithm rapidly adjusts the
target SIR in any of the following scenarios: service setup, service reconfiguration, burst
interference, and status switching between insufficient UE transmit power and sufficient UE
transmit power. By doing so, the average uplink target SIR is reduced and the uplink power
consumption is decreased.
Procedure
l
Activating outer loop power control
1.
Issue 06 (2013-03-25)
Run the Run the BSC6900 MML command SET UCORRMALGOSWITCH

129
RAN14.0
Parameters in Batches) to activate outer loop power control. In this step, select
the PC_OLPC_SWITCH check box under the PcSwitch parameter.
2.
Optional: Run the Run the BSC6900 MML command MOD

UTYPRABOLPC (CME single configuration: UMTS Radio Global
Configuration Express > Typical Service Configuration > Typical RAB
OLPC Parameters; CME batch modification center: not supported). In this step,
set the parameters related to outer loop power control based on the network plan.
Activating optimized outer loop power control

NOTE
You need to activate outer loop power control before activating optimized outer loop power control.
1.

Parameters in Batches) to activate optimized outer loop power control. In this
step, select the PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH check box
under the PcSwitch parameter.
2.
Optional: Run the Run the BSC6900 MML command SET UOLPC (CME single
configuration: UMTS radio global Configuration Express > RNC-Oriented
OLPC Algorithm Parameters Configuration > RNC-Oriented OLPC
Algorithm Parameters; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches). In this step, set SIRtargetDownSpeed to an appropriate
value.
3.
Optional: Run the Run the BSC6900 MML command MOD

UTYPRABOLPC (CME single configuration: UMTS Radio Global
Configuration Express > Typical Service Configuration > Typical RAB
OLPC Parameters; CME batch modification center: not supported). In this step,
set RefSIRtarget for a DCH to an appropriate value.
Verifying outer loop power control
1.
On the BSC6900 LMT main page, click Monitor. In the Monitor Navigation
Tree pane, choose Monitor > UMTS Monitoring > Connection Performance
Monitoring. The Connection Performance Monitoring dialog box is displayed.
In this dialog box, set Monitor Item to OLPC, Monitor Period to OLPC,
IMSI to an appropriate value, and Carrier Info to Main Carrier. Then, click
Submit to start tracing.
2.
Use a UE to initiate an AMR or R99 service.
3.
Check whether the target SIR in OLPC has changed. If the target SIR has changed,
this feature has been activated.
Verifying optimized outer loop power control
Issue 06 (2013-03-25)
1.
On the BSC6900 LMT main page, click Monitor. In the Monitor Navigation
In this dialog box, set Monitor Item to OLPC, Monitor Period to OLPC,
IMSI to an appropriate value, and Carrier Info to Main Carrier. Then, click
Submit to start tracing.
2.
Use a UE to initiate an AMR or R99 service.

130
RAN14.0
3.
When the service is successfully set up, check whether the adjustment value of the
target SIR is the same as the specified value in each OLPC period. If they are the
same, this feature has been activated.
Deactivating outer loop power control
1.

Parameters in Batches) to deactivate outer loop power control. In this step, clear
the PC_OLPC_SWITCH check box under the PcSwitch parameter.
Deactivating optimized outer loop power control

1.

Parameters in Batches) to deactivate optimized outer loop power control. In this
step, clear the PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH check box
under the PcSwitch parameter.
----End
Example
//Activating Outer Loop Power Control
SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_SWITCH-1;
//Setting the parameters related to outer loop power control
MOD UTYPRABOLPC: RabIndex=11, SubflowIndex=0, TrchType=TRCH_DCH,
DelayClass=1, BLERQuality=-20;
//Deactivating Outer Loop Power Control
//Activating optimized outer loop power control
SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH-1;
//Setting the step of uplink target SIR adjustment
SET UOLPC: SIRtargetDownSpeed=10;
//Setting the reference target SIR for a DCH
MOD UTYPRABOLPC: RabIndex=5, SubflowIndex=0, TrchType=TRCH_DCH,
DelayClass=1, RefSIRtarget=107;
//Deactivating optimized outer loop power control
SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH-0;
Issue 06 (2013-03-25)

131
RAN14.0
23
Configuring Inner Loop Power Control

Inner Loop Power Control.
Prerequisites
l

License
Context
Inner loop power control is also known as fast close loop power control. It is applied for dedicated
channels only. It is used to adjust the transmit power based on the feedback from the physical
layer of the peer end. The UE and Node B can adjust transmit power according to the SIR sent
by each other. In this way, radio link fading can be reduced.
Procedure
l
1.
Issue 06 (2013-03-25)
The feature does not need to be activated.
1.
Click the Monitor on the BSC6900 LMT main page. On the Monitor Navigation
Monitoring. The Connection Performance Monitoring dialog box is displayed. In
the displayed dialog box, set Monitor Item to UL SIR and UE Tx Power, and enter
the corresponding IMSI. And then click Submit to initiate the trace.
2.
UE 1 calls UE 2. UE 2 rings, answers and starts the conversation.
3.
Observe the variation of UL SIR and UE Tx Power in the UL SIR and UE Tx

Power Connection Performance Monitoring window.
4.
UE 1 moves in the cell to change radio link quality.
5.
When you move UE 1 away from the cell center, UE_1 transmit power increases.
132
RAN14.0
6.
When you move UE_1 towards cell center, UE_1 transmit power decreases.
Figure 23-1 UL SIR Tracing
Figure 23-2 UE Tx Power Tracing
1.
----End
Issue 06 (2013-03-25)

133
RAN14.0
24
Configuring Admission Control
Admission Control.
Prerequisites
l
Uplink power admission algorithm 4 introduced in RAN14.0 is based on the actual
service load, which is reported by the NodeB. However, some boards cannot support
the measurement of the service load.
The BTS3812E, BTS3812A and BTS3812AE do not support uplink power
admission algorithm 4.
The DBS3800 does not support uplink power admission algorithm 4.
If the 3900 series base station is configured with the WBBPa board or the RRU3801C
20W, uplink power admission algorithm 4 is not supported. In other configurations,
the algorithm is supported.

License
Context
This feature enables the BSC6900 to perform admission control on UEs requesting R99 services
by considering the status of various resources. It helps ensure the QoS and optimize the allocation
of system resources.
Procedure
l
1.
Activating code resource admission

Run the BSC6900 MML command MOD UCELLCAC (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Oriented CAC
Issue 06 (2013-03-25)

134
RAN14.0
Cell Parameters in Batches) with Dl handover credit and code reserved SF set to
an appropriate value.
2.
3.
4.
l
Issue 06 (2013-03-25)
Activating power resource admission

a.
Run the BSC6900 MML command MOD UCELLALGOSWITCH (CME

single configuration: UMTS Cell Configuration Express > Cell Parameters
> Cell Algorithm Switches; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches). In this step, select associated cell-oriented
power admission control algorithms from the Cell CAC algorithm switch dropdown list, and select an appropriate algorithm from both the Uplink CAC
algorithm switch and Downlink CAC algorithm switch drop-down lists
b.
Run the BSC6900 MML command MOD UCELLCAC (CME single

Oriented CAC Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to set power resource
admission parameters to appropriate values.
Activating NodeB credit resource admission

a.
Run the BSC6900 MML command SET UCACALGOSWITCH (CME single

configuration: UMTS Radio Global Configuration Express > CAC
Algorithm Switch Configuration > CAC Algorithm Switch; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches). In this step,
select NODEB_CREDIT_CAC_SWITCH from the CAC algorithm switch
drop-down list to turn on the NodeB-level CE admission switch.
b.

UMTS Cell Parameters in Batches). In this step, select CRD_ADCTRL
(Credit Admission Control Algorithm) from the Cell CAC algorithm
switch drop-down list to turn on the NodeB-level credit admission switch.
c.

Modifying UMTS Cell Parameters in Batches). In this step, set UL handover
credit reserved SF to an appropriate value.
Activating Iub resource admission

This feature does not need to be activated.
The procedure for verifying downlink admission control on R99 non-real-time PS services
based on the number of equivalent subscribers is as follows:
1.
Enable a UE in the idle state to camp on CELL_A11.
2.
Set the PS service type to interactive on the HLR.
3.
Run the BSC6900 MML command MOD UCELLCAC. In this step, set DL total
equivalent user number of CELL_A11 to 1.
4.
Connect the UE to a laptop through the USB port and initiate a PS service.
Expected result: The UE fails to initiate the PS service. In the Iu Interface Trace
window, an RANAP_RAB_ASSIGNBMENT_RESP message sent from the RNC to
the CN is displayed, containing the cause value no-radio-resources-available-intarget-cell.
135
RAN14.0
5.
Run the BSC6900 MML command MOD UCELLCAC. In this step, set DL total
equivalent user number of CELL_A11 to 80.
6.
Connect the UE to a laptop through the USB port and initiate a PS service.
Expected result: The data service is set up successfully.
1.
Deactivating code resource admission

2.
Deactivating power resource admission

Parameters in Batches). In this step, set Uplink CAC algorithm switch and
Downlink CAC algorithm switch to ALGORITHM_OFF.
3.
4.
Deactivating NodeB credit resource admission

a.

deselect NODEB_CREDIT_CAC_SWITCH from the CAC algorithm
switch drop-down list.
b.

UMTS Cell Parameters in Batches). In this step, deselect CRD_ADCTRL
(Credit Admission Control Algorithm) from the Cell CAC algorithm
switch drop-down list.
Deactivating Iub resource admission

----End
Example
//Activating code resource admission
MOD UCELLCAC: CellId=11, UlNonCtrlThdForAMR=75, UlNonCtrlThdForNonAMR=75,
UlNonCtrlThdForOther=60, DlConvAMRThd=80, DlConvNonAMRThd=80,
DlOtherThd=75, UlNonCtrlThdForHo=80, DlHOThd=85, UlCellTotalThd=83,
DlCellTotalThd=90, DlHoCeCodeResvSf=SF32;
//Activating power resource admission
MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST,
NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND;
MOD UCELLALGOSWITCH: CellId=11,
NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1&HSDPA_GBP_MEAS-1&HSDPA_PBR_MEAS-1;
MOD UCELLCAC: CellId=11, MaxHsdpaUserNum=64, MaxUlTxPowerforConv=24,
MaxUlTxPowerforInt=24;
//Activating NodeB credit resource admission
SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=CRD_ADCTRL-1;
MOD UCELLCAC: CellId=11, UlHoCeResvSf=SF16;
//Deactivating power resource admission
MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_OFF,
NBMDlCacAlgoSelSwitch=ALGORITHM_OFF;
Issue 06 (2013-03-25)

136
RAN14.0
//Deactivating NodeB credit resource admission

Issue 06 (2013-03-25)

137
RAN14.0
25
Configuring Load Measurement
Load Measurement.
Prerequisites
l
In RAN14.0, the load measurement of total uplink services is introduced, and the
dependencies on NodeB are as follows:
The BTS3812, BTS3812E and BTS3812AE do not report the actual service load.
The DBS3800 does not report the actual service load.
20W, the actual service load is not reported. In other configurations, the actual
service load is reported.

License
Context
This feature is used to measure the load for the load control feature.
Procedure
l
Issue 06 (2013-03-25)
1.
The function of measurement on RTWP, TCP, and non-HSPA power is always

activated. Therefore, this feature does not need to be activated.
2.

Parameters in Batches). In this step, select HSDPA_PBR_MEAS(HSDPA PBR
Meas Algorithm) and HSUPA_PBR_MEAS(HSUPA PBR Meas Algorithm) from
the Cell CAC algorithm switch drop-down list to activate the cell-level load
measurement for HSDPA and HSUPA.
138
RAN14.0
3.
Cell Parameters in Batches). In this step, set load monitoring parameters, including
the uplink/downlink load reshuffling (LDR) algorithm trigger/release thresholds and
uplink/downlink overload congestion (OLC) algorithm trigger/release thresholds to
appropriate values.
4.
Run the BSC6900 MML command SET ULDM (CME single configuration: UMTS
Radio Global Configuration Express > Load Monitoring Parameter
Configuration > LDM Algorithm Parameters of RNC; CME batch modification
center: 3.15 Modifying RNC Parameters in Batches). In this step, set parameters
associated with load measurement, report period, and smoothing filter length
1.
On the BSC6900 LMT, open the Monitor page. In the Monitor navigation tree,
double-click UMTS Monitoring > Cell Performance Monitoring, and create tasks
of monitoring Cell DL Carrier TX Power and RTWP.
2.
Check whether the uplink full-bandwidth RX power of the cell is displayed in the
RTWP monitoring window.
3.
Check whether the downlink carrier TX power is displayed in the Cell DL Carrier
TX Power monitoring window.
1.
The measurement on RTWP, TCP, and non-HSPA power has been activated and
cannot be deactivated.
2.

Parameters in Batches). In this step, deselect HSDPA_PBR_MEAS(HSDPA PBR
Meas Algorithm) and HSUPA_PBR_MEAS(HSUPA PBR Meas Algorithm) from
the Cell CAC algorithm switch drop-down list to deactivate the cell-level load
measurement for HSDPA and HSUPA.
----End
Example
//Activating load measurement
NBMCacAlgoSwitch=HSDPA_PBR_MEAS-1&HSUPA_PBR_MEAS-1;
MOD UCELLLDM: CellId=1, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70,
DlLdrRelThd=60, UlOlcTrigThd=95, UlOlcRelThd=85, DlOlcTrigThd=95,
DlOlcRelThd=85, HsupAuRetrnsLdTrigThd=70, HsupAuRetrnsLdRelThd=50;
SET ULDM: UlBasicCommMeasFilterCoeff=D6,
ChoiceRprtUnitForUlBasicMeas=TEN_MSEC, TenMsecForUlBasicMeas=100,
DlBasicCommMeasFilterCoeff=D6;
//Deactivating load measurement
NBMCacAlgoSwitch=HSDPA_PBR_MEAS-0&HSUPA_PBR_MEAS-0;
Issue 06 (2013-03-25)

139
RAN14.0
26
Configuring Load Reshuffling
Load Reshuffling.
Prerequisites
l

License
Context
This feature provides multiple load reshuffling policies for a cell in the basic congestion state
to decrease the cell load and increase the access success rate. The load reshuffling policies are
inter-frequency load handover, code reshuffling, BE service rate reduction, CS domain interRAT load handover, PS domain inter-RAT load handover, and downsizing the bit rate of AMR
voice.
Procedure
l
NOTE
The following section provides the related parameters and commands. The parameter settings depend
on the network plan.
1.
Enable the related load reshuffling algorithms.

a.

UMTS Cell Parameters in Batches). In this step, turn on the following switches
of Cell LDC algorithm switch:
UL_UU_LDR(Uplink UU LDR Algorithm): UL UU load reshuffling
algorithm
Issue 06 (2013-03-25)

140
RAN14.0
DL_UU_LDR(Downlink UU LDR Algorithm): DL UU load reshuffling

algorithm
CELL_CODE_LDR(Code LDR Algorithm): Code reshuffling algorithm
CELL_CREDIT_LDR(Credit LDR Algorithm):Credit reshuffling algorithm
b.

Information > NodeB Algorithm Parameters; CME batch modification center:
3.16 Modifying Logical NodeB Parameters in Batches). In this step, turn on
the following switches of NodeB LDC algorithm switch:
IUB_LDR(IUB LDR Algorithm): NodeB Iub reshuffling algorithm
NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm): NodeB-level
credit reshuffling algorithm
LCG_CREDIT_LDR(LCG Credit LDR Algorithm): cell-group-level credit
reshuffling algorithm
2.
Set the related thresholds.

Run the BSC6900 MML command MOD UCELLLDM (CME single
Oriented LDM Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to set LDR thresholds (UL/DL
LDR Trigger/release threshold and DL State Trans Hysteresis threshold).
Run the BSC6900 MML command MOD UCELLLDR (CME single
LDR Algorithm Parameters; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches) to set code LDR threshold (Cell LDR SF
reserved threshold) and LDR actions.
Run the BSC6900 MML command MOD UNODEBLDR (CME single
center: 3.16 Modifying Logical NodeB Parameters in Batches) to set the cellgroup-level or NodeB-level LDR thresholds (Ul/DL LDR Credit SF reserved
threshold).
UMTS Cell Parameters in Batches) to set the cell-level credit LDR thresholds
(Ul/DL LDR Credit SF reserved threshold).
3.
modification center: 3.15 Modifying RNC Parameters in Batches) to set the LDR
period (LDR period timer length).
4.

Parameters in Batches) to enable the functions used in the LDR actions.
Inter-frequency load handover
Issue 06 (2013-03-25)

141
RAN14.0
Set HandOver Switch to HO_INTER_FREQ_HARD_HO_SWITCH and

HO_ALGO_LDR_ALLOW_SHO_SWITCH.
BE service rate reduction
Set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH.
CS domain inter-RAT load handover
Set HandOver Switch to HO_INTER_RAT_CS_OUT_SWITCH.
PS domain inter-RAT load handover
Set HandOver Switch to HO_INTER_RAT_PS_OUT_SWITCH.
Downsizing the bit rate of AMR voice
Set CS Algorithm Switch to CS_AMRC_SWITCH.
l
The following section takes R99 non-real-time data services as examples to verify BE
service rate reduction in the basic congestion state.
1.
Enable a UE in idle mode to camp on CELL_A11.
2.
On the BSC6900 LMT, open the Monitor tab page. In the Monitor Navigation
Tree tab page, double-click UMTS Monitoring > Cell Performance Monitoring.
In the displayed dialog box, create a Cell DL Throughput monitoring task.
3.
Connect the UE to a laptop through the USB port and initiate a data service. Check
the rb-mappinginfo information element (IE) contained in the RRC_RB_SETUP
message traced over the Uu interface. The value of rrc-Stateinditator is
CELL_DCH.
4.
Use the UE to log in to the FTP server and then start FTP downloading. Data
downloading is normal.
5.
To simulate the scenario where power load reaches 75%, run the NodeB MML
command STR DLSIM. The RRC_RB_RECFG message is displayed in the Uu
Interface Trace dialog box. In the Cell DL Throughput of the Connection
Performance Monitoring dialog box, you can view the downlink RB rate decrease
configured on the RNC.
6.
To stop simulating power load, run the NodeB MML command STP DLSIM. In the
Uu Interface Trace dialog box, the RRC_RB_RECFG message is displayed. In the
Cell DL Throughput of the Connection Performance Monitoring dialog box, you can
view the downlink RB rate increase configured on the RNC.
1.

Parameters in Batches). In this step, deselect the following switches from Cell LDC
algorithm switch:
UL_UU_LDR(Uplink UU LDR Algorithm): UL UU load reshuffling algorithm
DL_UU_LDR(Downlink UU LDR Algorithm): DL UU load reshuffling algorithm
CELL_CODE_LDR(Code LDR Algorithm): Code reshuffling algorithm
CELL_CREDIT_LDR(Credit LDR Algorithm):Credit reshuffling algorithm
2.
Issue 06 (2013-03-25)

142
RAN14.0
Modifying Logical NodeB Parameters in Batches). In this step, deselect the

following switches from NodeB LDC algorithm switch:
IUB_LDR(IUB LDR Algorithm): NodeB Iub reshuffling algorithm
NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm): NodeB-level credit
LCG_CREDIT_LDR(LCG Credit LDR Algorithm): cell-group-level credit
----End
Example
//Activating Load Reshuffling
//Enabling load reshuffling algorithms
NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR1;
MOD UNODEBALGOPARA: NodeBName="nodeb1",
//Setting load reshuffling thresholds
MOD UCELLLDM: CellId=100, UlLdrTrigThd=55, UlLdrRelThd=45,
DlLdrTrigThd=70, DlLdrRelThd=60, UlOlcTrigThd=95, UlOlcRelThd=85,
DlOlcTrigThd=95, DlOlcRelThd=85, DlLdTrnsHysTime=1000;
//Setting code reshuffling thresholds
MOD UCELLLDR: CellId=100, DlLdrFirstAction=CodeAdj,
DlLdrSecondAction=InterFreqLDHO, CellLdrSfResThd=SF8;
//Setting NodeB-level credit reshuffling thresholds
MOD UNODEBLDR: NodeBName="nodeb1", UlLdrCreditSfResThd=SF8,
DlLdrCreditSfResThd=SF8;
//Setting cell-level credit reshuffling thresholds
MOD UCELLLDR: CellId=100, UlLdrCreditSfResThd=SF8,
DlLdrCreditSfResThd=SF8;
//Setting load reshuffling period
SET ULDCPERIOD: LDRPERIODTIMERLEN=10;
//Turning on load reshuffling function switches
SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1,
CsSwitch=CS_AMRC_SWITCH-1,
HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-1&HO_INTER_FREQ_HARD_HO_SWITCH-1&HO
_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1;
//Deactivating Load Reshuffling
MOD UNODEBALGOPARA: NodeBName="nodeb1",
Issue 06 (2013-03-25)

143
RAN14.0
27
Configuring Overload Control
Overload Control.
Prerequisites
l

License
Context
This feature provides load adjustment means to quickly lower the load in overloaded cells.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to enable the air interface OLC algorithm. Select the
UL_UU_OLC(Uplink UU OLC Algorithm) and DL_UU_OLC(Downlink UU
OLC Algorithm) check boxes under the parameter Switch for Cell Load Control.
2.

Modifying Logical NodeB Parameters in Batches) to enable the OLC algorithm.
Select the IUB_OLC(IUB OLC Algorithm) check box under the parameter NodeB
LDC algorithm.
3.
144
RAN14.0
Cell Parameters in Batches) to set UL OLC trigger threshold, DL OLC trigger

threshold, UL OLC release threshold, and DL OLC release threshold.
4.
modification center: 3.15 Modifying RNC Parameters in Batches) to set the OLC
period (OLC period timer value).
5.
Run the BSC6900 MML command ADD UCELLOLC (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Overload
Congestion Control Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to set the parameter related to OLCrelated actions.
1.
Run the following BSC6900 MML commands to verify whether the activation is
successful.
LST UCELLALGOSWTICH
LST UCELLLDM
LST UNODEBALGOPARA
LST ULDCPERIOD
LST UCELLOLC
NOTE
Consult Huawei engineers about the verification solution to obtain professional technical support.
NOTE
1.

Parameters in Batches) to dienable the air interface OLC algorithm. Clear the
UL_UU_OLC(Uplink UU OLC Algorithm) and DL_UU_OLC(Downlink UU
OLC Algorithm) check boxes under the parameter Switch for Cell Load Control.
2.

Modifying Logical NodeB Parameters in Batches) to disenable the OLC algorithm,
Clear the IUB_OLC(IUB OLC Algorithm) check box under the parameter NodeB
LDC algorithm.
----End
Example
//Activating Overload Control
NBMLdcAlgoSwitch=UL_UU_OLC-1&DL_UU_OLC-1;
MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-1;
SET ULDCPERIOD: OlcPeriodTimerLen=3000;
ADD UCELLOLC: CellId=111;
//Deactivating Overload Control
Issue 06 (2013-03-25)

145
RAN14.0
NBMLdcAlgoSwitch=UL_UU_OLC-0&DL_UU_OLC-0;
MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-0;
Issue 06 (2013-03-25)

146
RAN14.0
28
Configuring Code Resource

Management
Code Resource Management.
Prerequisites
l

License
Context
This feature provides downlink code tree allocation and reshuffling. Through this, the code
resources can be rationally allocated, therefore increasing the utilization efficiency of the
resources.
Procedure
l
NOTE
The code allocation function is always activated. The activation procedure applies to only the code
reshuffling function.
Issue 06 (2013-03-25)
1.

Parameters in Batches), and then enable the required LDR algorithm switches for
resources (CELL_CODE_LDR(Code LDR Algorithm)) through setting the Cell
LDC algorithm switch parameter.
2.
147
RAN14.0
Parameters in Batches) to set code LDR threshold (Cell LDR SF reserved

threshold) and set CodeAdj(Code adjust) as one of the DL LDR actions.
3.
modification center: 3.15 Modifying RNC Parameters in Batches) to set the length
of LDR period (LDR period timer length).
1.
Enable the UE in the idle state to camp on CELL_A11.
2.
Set the PS service type to interactive on the HLR.
3.
Run the BSC6900 MML command MOD UCELLLDR with Cell LDR SF reserved
threshold set to SF8 and Max user number for code adjust to 1.
4.
Connect the UE to a laptop on the USB port and enable the UE to initiate a data service.
Expected result: Services are set up on the DCH successfully. You can view the rbmappinginfo information element (IE) in the RRC_RB_SETUP message traced over
the Uu interface. In the Cell Code Tree Monitor window, you can view that the
service occupies code SF32(4).
5.
Enable the UE to log in to the FTP Internet server and then enable FTP download.
6.
Run the BSC6900 MML command DSP UCELLCHK to check the cell health status.
The status of cell code congestion is displayed as basic congestion.
7.
Run the BSC6900 MML command RMV URESERVEOVSF to release the service
that occupies code SF32(1).
8.
Run the BSC6900 MML command DSP UCELLCHK to check the cell health status.
The status of cell code congestion is displayed as not congested.
1.

Parameters in Batches), and then deactivate the required LDR algorithm switches
for resources (CELL_CODE_LDR(Code LDR Algorithm)) through setting the Cell
LDC algorithm switch parameter.
----End
Example
//Activating Code Resource Management
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=CELL_CODE_LDR-1;
MOD UCELLLDR: CellId=111, DlLdrFirstAction=CodeAdj, CellLdrSfResThd=SF8;
SET ULDCPERIOD: LdrPeriodTimerLen=10;
//Verifying Code Resource Management
MOD UCELLLDR: CellId=111, CellLdrSfResThd=SF8, MaxUserNumCodeAdj=1;
DSP UCELLCHK: CHECKSCOPE=CELLID, CELLID=111;
RMV URESERVEOVSF: CellId=111, DLOVSFSF=SF32, DLCODENO=1;
//Deactivating Code Resource Management
Issue 06 (2013-03-25)

148
RAN14.0
29
Configuring Potential User Control
Potential User Control.
Prerequisites
l

License
The license controlling this feature has been activated. For details on how to activate
the license, see 4 Activating the UMTS License. For details about license items, see
2 Feature Activation and License Item Descriptions.
Context
This feature reduces system load by modifying cell selection and reselection parameters. In this
way, the cell where the UE camps can be controlled based on cell load.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to select PUC(Potential User Control Algorithm) from
the Switch for Cell Load Control drop list to enable the cell-oriented PUC algorithm.
2.
modification center: 3.15 Modifying RNC Parameters in Batches) to specify the
period of potential user control. In this step, set PUC period timer length to an
appropriate value.
3.
Run the BSC6900 MML command ADD UCELLPUC (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Oriented PUC
149
RAN14.0

Cell Parameters in Batches) to set the cell-oriented PUC algorithm parameters.
l
1.
Configure two cells CELL_A11 and CELL_A12 as inter-frequency neighboring cells

on the NodeB.
2.
Run the BSC6900 MML command MOD UCELLPUC to change the potential user
control threshold for CELL_A11.
3.
Run the NodeB MML command STR DLSIM to simulate a situation where the cell
has a high load.
The following messages can be traced on the Iub interface: the
NBAP_SYS_INFO_UPDATE_REQ from the RNC to the NodeB, and the
NBAP_SYS_INFO_UPDATE_RSP message responded by the NodeB.
The updated system information can be traced on the Uu interface. The value of the
Sintersearch signaling element (IE) of the SIB3 of CELL_A11 decreases, and the
values of the Qoffset1s,n and Qoffset2s,n IEs of the SIB11 of CELL_A11 increase.
4.
Run the BSC6900 MML command MOD UCELLPUC to change the potential user
control threshold for CELL_A12.
5.
Run the NodeB MML command STR DLSIM to simulate a situation where
CELL_A12 has a high downlink load.
The following messages can be traced on the Iub interface: the
NBAP_SYS_INFO_UPDATE_REQ message from the RNC to the NodeB, and the
NBAP_SYS_INFO_UPDATE_RSP response message from the NodeB.
The updated system information can be traced on the Uu interface. The value of the
Sintersearch IE of the SIB3 of CELL_A11 decreases, and the values of the Qoffset1s,n
and Qoffset2s,n IEs of the SIB11 of CELL_A11 increase.
1.

Parameters in Batches). In this step, deselect the PUC(Potential User Control
Algorithm) check box under the parameter Cell LDC algorithm switch.
----End
Example
//Activating Potential User Control
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-1;
SET ULDCPERIOD: PucPeriodTimerLen=1800;
ADD UCELLPUC: CELLID=1, SPUCLIGHT=45, SPUCHEAVY=70, SPUCHYST=5,
OFFSINTERLIGHT=-2, OFFSINTERHEAVY=2, OFFQOFFSET1LIGHT=-4,
OFFQOFFSET2LIGHT=-4, OFFQOFFSET1HEAVY=4, OFFQOFFSET2HEAVY=4;
//Deactivating Potential User Control
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-0;
Issue 06 (2013-03-25)

150
RAN14.0
30
Configuring Cell Barring
Cell Barring.
Prerequisites
l

License
Context
If the cell barring feature is enabled, cells can be barred either automatically or manually to
facilitate operators' maintenance when the cells are running improperly.
Procedure
l
Setting automatic cell barring
Issue 06 (2013-03-25)
1.

Configuration > Process Switch; CME batch modification center: 3.15
Modifying RNC Parameters in Batches). In this step, select
SYS_INFO_UPDATE_FOR_IU_RST and
BARRED_CELL_FOR_CSDOMAIN_RST from the Process switch dropdown list.
2.
Run the BSC6900 MML command SET UIUTIMERANDNUM (CME single

configuration: IUPS Configuration Express > CN > IU Timers And Counter
for CN Node; CME batch modification center: not supported) to enable
interruption protection by specifying CN protection timer.
151
RAN14.0
Setting manual cell barring
1.
Run the BSC6900 MML command ADD URNCALLCELLBLK (CME single

configuration: UMTS Radio Global Configuration Express > Access
Restriction Algorithm Parameters Configuration > The Parameters for
Quickly Blocking all the Cells in the RNC; CME batch modification center: not
supported) to configure parameters related to barring of all cells served by an RNC
in a network.
2.
Run the BSC6900 MML command ADD UCNOPALLCELLBLK (CME single

Quickly Blocking all the Cells of the Designated Operator in the RNC; CME
batch modification center: not supported) to configure parameters related to
operator-specific barring of all cells in a network.
Block the PS domain or the PS domain is disconnected, which prevents UEs from being
admitted to PS services. Perform the following steps to verify whether this feature is
activated:
NOTE
Perform the same verification procedure when blocking the CS domain or the CS domain is
disconnected.
1.
Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message

Type, select RRC_SYS_INFO_TYPE1.
2.
View whether information element (IE) information of the PS domain is contained

in the traced messages. Expected result: PS domain IE information is not contained,
as shown in Figure 30-1.
Figure 30-1 Uu Interface Trace dialog box
Issue 06 (2013-03-25)

152
RAN14.0
Block CS and PS domains, CS and PS domains are disconnected, or block the CS domain
and turn on BARRED_CELL_FOR_CSDOMAIN_RST. Perform the following steps
to verify whether this feature is activated:
1.

2.
View whether IE information related to CS and PS domains is contained in the

traced messages. Expected result: The IE information is not contained, as shown
in Figure 30-2.
Bar PS services of UEs served by an operator. Perform the following steps to verify
whether this feature is activated:
NOTE
Perform the same verification procedure when barring CS services of UEs served by an operator.
Issue 06 (2013-03-25)
1.

2.
View whether IE information related to CS and PS domains is contained in the

traced messages. Expected result: The IE information is not contained, as shown
in Figure 30-3.
153
RAN14.0
Deactivating automatic cell barring
1.

Modifying RNC Parameters in Batches). In this step, deselect
SYS_INFO_UPDATE_FOR_IU_RST and
BARRED_CELL_FOR_CSDOMAIN_RST from the Process switch dropdown list.
Deactivating manual cell barring
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command RMV URNCALLCELLBLK (CME single

Quickly Blocking all the Cells in the RNC; CME batch modification center: not
supported) to remove parameters related to barring of all cells served by an RNC
in a network.
2.
Run the BSC6900 MML command RMV UCNOPALLCELLBLK (CME single

Quickly Blocking all the Cells of the Designated Operator in the RNC; CME

154
RAN14.0
batch modification center: not supported) to remove parameters related to operatorspecific barring of all cells in a network.
----End
Example
//Activating Cell Barring
SET URRCTRLSWITCH: PROCESSSWITCH
SET UIUTIMERANDNUM: CnOpIndex=0,
//Deactivating Cell Barring
Issue 06 (2013-03-25)
= SYS_INFO_UPDATE_FOR_IU_RST-1;
= BARRED_CELL_FOR_CSDOMAIN_RST-1;
CNId=0, StateIndTmr=20000;
= SYS_INFO_UPDATE_FOR_IU_RST-0;
= BARRED_CELL_FOR_CSDOMAIN_RST-0;

155
RAN14.0
31
Configuring Shared Network Support in

Connected Mode
Shared Network Support in Connected Mode. (This feature cannot be configured using the
CME. )
Prerequisites
l

License
Other Prerequisites
CN must support this feature. When the Iur interface is used, the RNC connected over
the interface must also support this feature.
Context
This feature enables the RAN and CN together to perform UE access restriction in specified
location areas.
Procedure
l
Issue 06 (2013-03-25)
1.
For the CS service, configure two SNAs (for example, SNA1 and SNA2) on the MSC.
2.
For the PS service, run the MML command ADD SNA on the SGSN to add SNA,
SNA1, and SNA2.
3.
Run the BSC6900 MML command MOD UCELLACINFO to modify the RACs of
CELL1 and CELL2.
4.
Set up a cell. For details, see the BSC6900 UMTS Initial Configuration Guide.
5.
Run the BSC6900 MML command to turn on the soft handover switch.
156
RAN14.0
6.
l
Run the BSC6900 MML command to enable the SNA function.
Verifying the SNA Function of the CS Service

1.
2.
3.
Run the BSC6900 MML command to disable the SNA function.
4.
Use UE1 to call UE2. The RANAP_COMMON_ID message from UE1 should be
displayed in Iu trace data, and it should include the SNA ACCESS information IE.
5.
Move UE1 to CELL2 to trigger soft handover. The RRC_ACTIVE_SET_UPDATE

message from the RNC to UE1 and the RRC_ACTIVE_SET_UPDATE_CMP
message from UE1 to the RNC should be displayed in Uu trace data.
6.
End the calling. UE1 and UE2 return to the idle mode in CELL1.
7.
8.
Add a mapping relation between IMSI of UE1 and SNA1 on the MSC.
9.
Use UE1 to call UE2. The RANAP_COMMON_ID message from UE1 should be
displayed in Iu trace data, and it should include the SNA ACCESS information IE.
NOTE
CELL2 belongs to SNA2 but not SNA1. Therefore, the RRC_MEAS_CTRL message sent from
the RNC to UE1 on the Uu interface should indicate that CELL2 is not in the monitoring cell.
10. Move UE1 to CELL2, which will not trigger soft handover because UE1 does not
belong to SNA_2.
11. End the calling. UE1 and UE2 return to the idle mode in CELL1.
l
Verifying the SNA Function of the PS Service

1.
Run the MML command ADD SNA on the SGSN to add SNA information.
2.
Run the BSC6900 MML command to disable the SNA function.
3.
Keep the UE in idle mode in CELL1.
4.
Establish a PS service on UE1. The RANAP_COMMON_ID message from UE1

should be displayed in Iu trace data, and it should include the SNA ACCESS
information IE.
5.
Move UE1 to CELL2 to trigger soft handover. The RRC_ACTIVE_SET_UPDATE

message from the RNC to UE1 and the RRC_ACTIVE_SET_UPDATE_CMP
message from UE1 to the RNC should be displayed in Uu trace data.
6.
End the PS service of UE1. UE1 returns to the idle mode in CELL1.
7.
8.
Establish a PS service on UE1. The RANAP_COMMON_ID message from UE1

should be displayed in Iu trace data, and it should include the SNA ACCESS
information IE.
9.
CELL2 belongs to SNA2 but not SNA1. Therefore, the RRC_MEAS_CTRL message
sent from the RNC to UE1 on the Uu interface should indicate that CELL2 is not in
the monitoring set.
10. Move UE1 to CELL2, which will not trigger soft handover because UE1 does not
belong to SNA_2.
11. End the PS service of UE1. UE1 returns to the idle mode in CELL1.
l
Issue 06 (2013-03-25)
157
RAN14.0
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the

SNA function.
----End
Example
//Adding two SNAs (for example, SNA1 and SNA2) on the MSC
ADD LOCNOLAI: LOCNONAME="SNA_1", LAI="460020001";
ADD LOCSNA: LOCNONAME=" SNA_1", SNAC=1;
ADD SNAGRPCODE: SNAGRPN="1", SNAC=1;
ADD LOCNOLAI: LOCNONAME="SNA_2", LAI="460020002";
ADD LOCSNA: LOCNONAME=" SNA_2", SNAC=2;
ADD SNAGRPCODE: SNAGRPN="2", SNAC=2;
//Activating the SNA function of the CS Service
MOD UCELLACINFO: CellId=1, LAC=1, SAC=0, CfgRacInd=REQUIRE, RAC=1;
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1;
SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1;
//Verifying the SNA function of the CS Service
///Add a mapping relation between IMSI and SNA1 on the MSC
ADD IMSIGRP: IMSIPRE=K'460071104008338, MCCMNC1=K'46002, SNAGRPN1="1";
MOD RNC: RNCID=1, CAPABILITY=SNA-1;
//Deactivating the SNA function
//Adding two SNAs (for example, SNA1 and SNA2) on the SGSN
ADD SNA: PLMN="46002", LAC="1", SNAC=1;
ADD SNA: PLMN="46002", LAC="2", SNAC=2;
//Activating the SNA function of the PS Service
//Adding SNA information on the SGSN
ADD SNAA: BEGIMSI="460071104008338", ENDIMSI="460071104008338",
PLMN="46002", SNAC=1;
//Verifying the SNA function of the PS Service
//Deactivating the SNA function
Issue 06 (2013-03-25)

158
RAN14.0
32
Configuring Intra NodeB Softer

Handover
Intra NodeB Softer Handover.
Prerequisites
l

License
Context
This feature enables softer handover within a NodeB. Intra-NodeB softer handover is one type
of soft handover. To perform softer handover, multiple RLs need to be established. In this way,
the uplink resources of a cell in the same uplink resource group can be fully shared. In contrast
to soft handover, softer handover does not consume additional transmission resources on the Iub
interface. Therefore, softer handover can provide higher combination gain and require less
transmission resources on the Iub interface.
Softer handover may occur within the same uplink resource group.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, select
HO_INTRA_FREQ_SOFT_HO_SWITCH under HandOver Switch to enable
soft handover.
2.
Run the BSC6900 MML command SET UHOCOMM (CME single configuration:
UMTS Radio Global Configuration Express > HandOver Parameter
159
RAN14.0
Configuration > RNC Oriented Handover Algorithm Common Parameters;

CME batch modification center: 3.15 Modifying RNC Parameters in Batches) to
set Softer handover combination indicator switch to MAY or MUST.
3.
Run the BSC6900 MML command ADD UINTRAFREQNCELL (CME single

configuration: UMTS Cell Configuration Express > Neighboring Cell > Intrafrequency Neighboring Cell; CME batch modification center: not supported) to add
an intra-frequency neighboring cell.
4.
Run the BSC6900 MML command SET UINTRAFREQHO (CME single

configuration: UMTS Radio Global Configuration Express > HandOver
Parameter Configuration > RNC Oriented Intra-frequency Handover
Measurement Algorithm Parameters; CME batch modification center: 3.15
Modifying RNC Parameters in Batches) to set the parameter related to handover.
1.
2.
Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3.
UE is in idle mode and camps on the CELL1.
4.
UE initiates PS Dial-up, and service is set up successfully.
5.
UE moves from CELL1 to CELL2, through the Trace Data, it can be observed RNC
sends the RRC_ACTIVE_SET_UPDATE message to UE and UE sends the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC.
6.
The data transmission remains normal while UE is moving to CELL2.
1.
Run the BSC6900 MML command SET UHOCOMM (CME single configuration:
Configuration > RNC Oriented Handover Algorithm Common Parameters;
CME batch modification center: 3.15 Modifying RNC Parameters in Batches) to
set Softer handover combination indicator switch to MUST_NOT.
----End
Example
//Activating Intra NodeB Softer Handover
SET UHOCOMM: DivCtrlField=MAY;
ADD UINTRAFREQNCELL: RNCId=202, CellId=2381, NCellRncId=203,
NCellId=3291, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0,
NPrioFlag=FALSE;
SET UINTRAFREQHO: FilterCoef=D3, IntraFreqMeasQuantity=CPICH_EC/NO,
PeriodMRReportNumfor1C=D16, ReportIntervalfor1C=D4000;
//Deactivating Intra NodeB Softer Handover
Issue 06 (2013-03-25)

160
RAN14.0
33
Configuring Intra RNC Soft Handover
Intra RNC Soft Handover.
Prerequisites
l

License
Context
Intra-RNC soft handover is one type of soft handover. To implement intra-RNC soft handover,
multiple RLs need to be established between NodeBs or within a NodeB. Intra-NodeB softer
handover and intra-RNC soft handover differ in the place where macro diversity combining is
performed. For intra-RNC soft handover, macro diversity combining, which is in selective mode,
is performed within the RNC. In such a case, each RL on the Iub interface carries transmission
data independently. Compared with intra-NodeB softer handover, the intra-RNC soft handover
can be applied to more scenarios.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to enable soft handover.
2.

3.

161
RAN14.0

l
1.
2.
click Submit.
3.
Both UE1 and UE2 are in idle mode and camp on the CELL1.
4.
UE1 calls UE2, and the conversation clear.
5.
UE1 moves from CELL1 to CELL2, through the Trace Data, it can be observed that
RNC1 sends the RRC_ACTIVE_SET_UPDATE message to UE1, and UE1 sends the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC1.
1.

Parameters in Batches) to set Softer handover combination indicator to disable
the soft handover.
----End
Example
//Activating Intra RNC Soft Handover
ADD UINTRAFREQNCELL: RNCId=202, CellId=2381, NCellRncId=203,
NPrioFlag=FALSE;
SET UINTRAFREQHO: FilterCoef=D3, IntraFreqMeasQuantity=CPICH_EC/NO,
PeriodMRReportNumfor1C=D16, ReportIntervalfor1C=D4000;
//Deactivating Intra RNC Soft Handover
Issue 06 (2013-03-25)

162
RAN14.0
34
Configuring Inter RNC Soft Handover
Inter RNC Soft Handover.
Prerequisites
l

License
Other Prerequisites
The Iur interface is configured between adjacent RNCs.
Context
Inter-RNC soft handover is one type of soft handover. To implement inter-RNC soft handover,
multiple RLs need to be established between different RNCs. In such a case, macro diversity
combining is performed by the SRNC connected through the Iur interface. The SRNC sends the
DRNC the radio link establishment signaling over the Iur interface. Based on the signaling, the
DRNC establishes a radio link in the new NodeB. Other procedures are similar to those of intraRNC soft handover. This feature enables telecom operators to provide seamless connection
services to subscribers. Inter-RNC soft handover has wider application scenario than soft
handover in other forms, as it can be applied to the RNCs connected through the Iur interface.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to enable soft handover.
2.
Run the BSC6900 MML command ADD UNRNC (CME single configuration: IUR
Configuration Express > Neighbouring RNC > Neighboring RNC; CME batch
163
RAN14.0
modification center: not supported) or MOD UNRNC (CME single configuration:

IUR Configuration Express > Neighbouring RNC > Neighboring RNC; CME
batch modification center: not supported) to enable cross-Iur soft handover.
3.
Run the BSC6900 MML command ADD UEXT3GCELL (CME single

configuration: Object Group > UMTS Service Configuration and Maintenance
Management > External Cell Configuration > RNC 3G External Cell; CME batch
modification center: 3.19 Modifying RNC External Cell Parameters in Batches)
to add a neighboring RNC cell.
4.

5.

1.
2.
click Submit.
3.
Both UE1 and UE2 are in idle mode and camp on the CELL1.
4.
UE1 calls UE2, and the conversation clear.
5.
UE1 moves from CELL1 to CELL2, through the Trace Data, it can be observed that
RNC1 sends the RRC_ACTIVE_SET_UPDATE message to UE1, and UE1 sends the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC1.
1.
Run the BSC6900 MML command MOD UNRNC (CME single configuration: IUR
modification center: not supported) to disable the cross-Iur soft handover.
----End
Example
//Activating Inter RNC Soft Handover
MOD UNRNC: NRncId=1,
SHOTRIG=CS_SHO_SWITCH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1;
ADD UEXT3GCELL: NRncId=1, CellId=2381, CellHostType=SINGLE_HOST,
CellName="2222", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1,
UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700,
TxDiversityInd=FALSE, LAC=2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE,
QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED,
CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE;
ADD UINTRAFREQNCELL: RNCId=1, CellId=221, NCellRncId=2, NCellId=222,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE;
//Deactivating Inter RNC Soft Handover
SHOTRIG=CS_SHO_SWITCH-0&HSPA_SHO_SWITCH-0&NON_HSPA_SHO_SWITCH-0;
Issue 06 (2013-03-25)

164
RAN14.0
35
Configuring Intra Frequency Hard

Handover
Intra Frequency Hard Handover.
Prerequisites
l

License
Context
When hard handover is performed, the existing connection is interrupted before new connection
is set up. Intra-frequency hard handover is performed between cells on the same frequency.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to select HO_INTRA_FREQ_HARD_HO_SWITCH from
the HandOver switch list.
2.

an intra-frequency or inter-RNC neighboring cell.
3.
If cross-Iur hard handover is required, add the neighboring RNC and neighboring RNC
cell. Run the BSC6900 MML command ADD UNRNC (CME single configuration:
IUR Configuration Express > Neighbouring RNC > Neighboring RNC; CME
165
RAN14.0
batch modification center: not supported) to add a neighboring RNC. Run the
BSC6900 MML command ADD UEXT3GCELL (CME single configuration:
Object Group > UMTS Service Configuration and Maintenance Management >
External Cell Configuration > RNC 3G External Cell; CME batch modification
center: 3.19 Modifying RNC External Cell Parameters in Batches) to add a
neighboring RNC cell. Run the BSC6900 MML command ADD
UINTRAFREQNCELL (CME single configuration: UMTS Cell Configuration
Express > Neighboring Cell > Intra-frequency Neighboring Cell; CME batch
modification center: not supported) to set the neighboring cell relations.
4.

1.
2.
click Submit.
3.
Both UE1 and UE2 are subscribed in HLR to support speech service.
4.
4. Both UE1 and UE2 are in idle mode and camp on the CELL1.
5.
UE1 calls UE2, and the conversation is clear.
6.
UE1 moved from CELL1 to CELL2, through the Trace Date, it can be observed
RRC_MEAS_RPRT message with 1D event that UE1 sends to RNC1.
1.

Parameters in Batches) to deselect HO_INTRA_FREQ_HARD_HO_SWITCH
from the Handover switch list.
----End
Example
//Activating Intra Frequency Hard Handover
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_HARD_HO_SWITCH-1;
ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=1, NCellId=211,
ADD UNRNC: NRncId =2,
SHOTRIG=CS_SHO_SWITCH-0&HSPA_SHO_SWITCH-0&NON_HSPA_SHO_SWITCH-0,
HHOTRIG=ON, SERVICEIND=SUPPORT_CS_AND_PS, IurExistInd=TRUE, DPX=1,
RNCPROTCLVER=R5, STATEINDTMR=20, TnlBearerType=ATM_TRANS;
TxDiversityInd=FALSE, LAC=H'2506, CfgRacInd=NOT_REQUIRE,
QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE,
CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE;
Issue 06 (2013-03-25)

166
RAN14.0
//Deactivating Intra Frequency Hard Handover

SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_HARD_HO_SWITCH-0;
Issue 06 (2013-03-25)

167
RAN14.0
36
Configuring Intra RNC Cell Update
Intra RNC Cell Update.
Prerequisites
l

License
Context
Cell update is mainly used to update the UE information on the network side when the UE
location or behavior is changed. Intra-RNC cell update means cell update within the RNC.
Procedure
l
Issue 06 (2013-03-25)
1.

switch.
2.

parameters BE DCH to FACH Transition Timer[s] and BE FACH or E_FACH to
PCH Transition Timer[s] to 30s and 60s respectively.
3.

168
RAN14.0

4.
Run the BSC6900 MML command SET UCONNMODETIMER (CME single

configuration: UMTS Radio Global Configuration Express > UE Timers and
Constants Configuration > UE Timers And Constants in Connected Mode; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) to set the
periodic cell update timer to 5 minutes.
5.
Set CELL1 and CELL2 of the RNC as intra-frequency neighboring cells. For details,
see the BSC6900 UMTS Initial Configuration Guide.
Verifying Cell Update Triggered by Cell Reselection

1.
Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click
Uu Interface Trace. The Uu Interface Trace dialog box is displayed.
2.
click Submit.
3.
4.
5.
Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be

CELL_DCH.
6.
Do not send any data from UE for 30 seconds. Then, the network side should perform
UE transition to CELL_FACH state through the RRC_RB_RECFG message, and the
value of the rrc-stateindicator IE should be CELL_FACH.
7.
Cause the UE to reselect a new cell so as to trigger cell update. The UE should send
the RRC_CELL_UPDATE message to the RNC, with the cell update cause of cell
reselection, and the RNC should send the RRC_CELL_UPDATE_CONFIRM
message to the UE.
Verifying Cell Update Triggered by Uplink Data Transmission

1.
2.
3.
4.

CELL_DCH.
5.
6.
Do not send any data from UE1 for another while. Then, the network side should
perform UE transition to CELL_PCH state through the RRC_RB_RECFG message,
and the value of the rrc-stateindicator IE should be CELL_PCH.
7.
Use the UE to transmit data so as to trigger cell update. The UE should send the
RRC_CELL_UPDATE message to the RNC, with the cell update cause of
uplinkdatatransmission, and the RNC should send the
RRC_CELL_UPDATE_CONFIRM message to the UE.
Verifying Periodic Cell Update

1.
Issue 06 (2013-03-25)

169
RAN14.0

parameter BE FACH or E_FACH to PCH Transition Timer[s] to 65535.
For example,
2.
3.
4.
5.

CELL_DCH.
6.
7.
Do not send any data from the UE for five minutes so as to trigger periodic cell update.
The UE should send the RRC_CELL_UPDATE message to the RNC, with the cell
update cause of periodiccellupdate, and the RNC should send the
RRC_CELL_UPDATE_CONFIRM message to the UE.
1.
None
----End
Example
//Activating intra-RNC cell update
SET UUESTATETRANSTIMER: BeD2FStateTransTimer=30, BeF2PStateTransTimer=60;
SET UCONNMODETIMER: T305=D5;
Issue 06 (2013-03-25)

170
RAN14.0
37
Configuring Inter RNC Cell Update
Inter RNC Cell Update.
Prerequisites
l

License
Other Prerequisites
Context
Cell update is mainly used to update the UE information on the network side when the UE
location or behavior is changed. Inter-RNC cell update means cell update between RNCs.
Procedure
l
Issue 06 (2013-03-25)
1.

switch.
2.

parameter BE DCH to FACH Transition Timer to 30s.
3.

171
RAN14.0
4.
Configure intra-frequency neighboring cells controlled by different BSC6900s. For

details, see the Configuring an Intra-Frequency Neighboring Cell.
5.
modification center: not supported) to set the parameter IUR CCH support flag to
ON.
NOTE
IUR CCH support flag is also turned on neighboring BSC6900.
Verifying Cell Update Triggered by Cell Reselection

1.
2.
click Submit.
3.
Keep the UE in idle mode in CELL.
4.
5.

CELL_DCH.
6.
7.
Cause the UE to perform cell reselection from local cell to intra-frequency neighboring
cell so as to trigger cell update. The UE should send the RRC_CELL_UPDATE
message to neighboring BSC6900, with the cell update cause of cell reselection, and
local BSC6900 should send the RRC_CELL_UPDATE_CONFIRM message to the
UE.
1.
----End
Example
//Activating inter-RNC cell update
MOD UNRNC: NRncId=2, SuppIurCch=YES;
Issue 06 (2013-03-25)

172
RAN14.0
38
Configuring Intra RNC URA Update
Intra RNC URA Update.
Prerequisites
l

License
Context
The UTRAN registration area (URA) update procedure updates the URA of a UE when an RRC
connection exists and the location of the UE is known on the URA level in the UTRAN. IntraRNC URA update means URA update within the RNC.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD UCELLACINFO (CME single

configuration: UMTS Cell Configuration Express > Cell Basic Information > Cell
Basic Information; CME batch modification center: not supported) to set CELL1 and
CELL2 as the intra-frequency neighboring cells that belong to the same location area,
route area, and service area.
2.
Run the BSC6900 MML command ADD UCELLURA (CME single configuration:
UMTS Cell Configuration Express > Cell Basic Information > Cell URA; CME
batch modification center: not supported) to configure CELL1 and CELL2 to make
them belong to different URAs.
3.

Parameters in Batches) to select DRA_PS_BE_STATE_TRANS_SWITCH from
173
RAN14.0
the Dynamic Resource Allocation Switch drop-down list to turn on the RNCoriented PS BE service state transition switch.
4.

under the parameter Dynamic Resource Allocation Switch to to enable state
transition from CELL_FACH to URA_PCH directly.
5.

modification center: 3.15 Modifying RNC Parameters in Batches) to set the Cell
Reselection Timer, BE DCH to FACH Transition Timer, and BE FACH or
E_FACH to PCH Transition Timer parameters to 60s, 10s, and 10s respectively.
6.

7.
Run the BSC6900 MML command SET UCONNMODETIMER (CME single

configuration: UMTS Radio Global Configuration Express > UE Timers and
Constants Configuration > UE Timers And Constants in Connected Mode; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) to set the
periodic cell update timer to 5 minutes.
8.
Configure intra-frequency neighboring cells. For details, see the BSC6900 UMTS
Initial Configuration Guide.
Verifying URA Update Triggered by URA Reselection

1.
2.
click Submit.
3.
4.
5.

CELL_DCH.
6.
7.
When the DRA_F2U_SWITCH switch is on or off, the state transition of UE is

different.
If the switch is off: Do not send any data from the UE for another while. Then, the
network side should perform UE transition to CELL_PCH state through the
RRC_RB_RECFG message, and the value of the rrc-stateindicator IE should be
CELL_PCH. Make the UE perform a cell reselection between CELL1 and
CELL2. Make UE1 perform another cell reselection after the Cell Reselection
Issue 06 (2013-03-25)

174
RAN14.0
Timer[s] expires. Search for the last RRC_CELL_UPDATE_CONFIRM message

in trace data. The value of the rrc-stateindicator IE should be URA_PCH.
If the switch is on: Do not send any data from the UE for another while. Then, the
network side should perform UE transition to URA_PCH state through the
URA_PCH.
8.
Verifying Periodic URA Update

1.
Keep the UE in URA_PCH state. Perform another cell reselection between CELL1
and CELL2 so as to trigger URA update. The UE should send the
RRC_URA_UPDATE message to the RNC, with the cell update cause of
changeofURA, and the RNC should send the RRC_URA_UPDATE_CONFIRM
message to the UE.
Do not send any data from the UE for five minutes, to trigger periodic URA update.
The UE should send the RRC_URA_UPDATE message to the RNC, with the cell
update cause of URA reselection, and the RNC should send the
RRC_URA_UPDATE_CONFIRM message to the UE.
1.
----End
Example
//Activating intra-RNC URA update
//Configring the cell information
ADD UCELLURA: CellId=111, URAId=0;
SET UCORRMALGOSWITCH: DraSwitch=DRA_F2U_SWITCH-1;
SET UUESTATETRANSTIMER: BeD2FStateTransTimer=65535,
CellReSelectTimer=180;
BeF2PStateTransTimer=10;
Issue 06 (2013-03-25)

175
RAN14.0
39
Configuring Inter RNC URA Update
Inter RNC URA Update.
Prerequisites
l

License
Others
Context
Inter-RNC URA update means URA update between RNCs.
Procedure
l
1.
Configure the Iur interface. For details, see the BSC6900 UMTS Initial Configuration
Guide.
2.
Run the BSC6900 MML command ADD UCELLURA (CME single configuration:
UMTS Cell Configuration Express > Cell Basic Information > Cell URA; CME
batch modification center: not supported) to configure CELL1 and CELL2 to make
them belong to different URAs.
NOTE
Cell1 belongs to RNC_1, Cell2 belongs to RNC_2.
3.
Issue 06 (2013-03-25)
On the RNC1 side, run the BSC6900 MML command SET

UCORRMALGOSWITCH (CME single configuration: UMTS Radio Global
Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: 3.15
176
RAN14.0
Modifying RNC Parameters in Batches) to turn on the RNC-oriented PS BE service

state transition switch.
4.

under the parameter Dynamic Resource Allocation Switch to to enable state
transition from CELL_FACH to URA_PCH directly.
5.

modification center: 3.15 Modifying RNC Parameters in Batches) to set the Cell
Reselection Timer, BE DCH to FACH Transition Timer, and BE FACH or
E_FACH to PCH Transition Timer parameters to 60s, 10s, and 10s respectively.
6.
Run the BSC6900 MML command SET UUESTATETRANS (CME single

Parameter Configuration > UE State Translating Parameters; CME batch
parameter Cell Reselection Counter Threshold to 1.
7.

8.
Configure intra-frequency neighboring cells. For details, see the BSC6900 UMTS
Initial Configuration Guide.
9.
modification center: not supported) to enable the setup of command channels on the
Iur interface.
1.
2.
click Submit.
3.
4.
5.

CELL_DCH.
6.
7.
When the DRA_F2U_SWITCH switch is on or off, the state transition of UE is

different.
If the switch is off: Do not send any data from the UE for another while. Then, the
network side should perform UE transition to CELL_PCH state through the
Issue 06 (2013-03-25)

177
RAN14.0
CELL_PCH. Make the UE perform a cell reselection between CELL1 and

CELL2. Make UE1 perform another cell reselection after the Cell Reselection
Timer[s] expires. Search for the last RRC_CELL_UPDATE_CONFIRM message
in trace data. The value of the rrc-stateindicator IE should be URA_PCH.
If the switch is on: Do not send any data from the UE for another while. Then, the
network side should perform UE transition to URA_PCH state through the
URA_PCH.
8.
Keep the UE in URA_PCH state. Perform another cell reselection between CELL1
and CELL2 so as to trigger URA update. The UE should send the
RRC_URA_UPDATE message to the RNC, with the cell update cause of CHANGE
OF URA, and the RNC should send the RRC_URA_UPDATE_CONFIRM message
to the UE.
1.
----End
Example
//Activating inter-RNC URA update
//Configring the cell information
SET UCORRMALGOSWITCH: DraSwitch=DRA_F2U_SWITCH-1;
BeF2PStateTransTimer=10;
Issue 06 (2013-03-25)

178
RAN14.0
40 Configuring Direct Signaling Connection Reestablishment (DSCR)
40
Configuring Direct Signaling
Connection Re-establishment (DSCR)

Direct Signaling Connection Re-establishment (DSCR).
Prerequisites
l

License
Context
During a DSCR procedure, the RNC autonomously releases the RRC connection carrying nonreal-time RABs and then immediately requests the UE to re-establish an RRC connection for
service setup. The RRC connection re-establishment procedure is triggered by an RRC
CONNECTION RELEASE message with the cause value of Directed Signaling Connection
re-establishment sent from the RNC to the UE. A routing area update follows the RRC
connection re-establishment immediately.
The DSCR feature is supplementary to the feature WRFD-020605 SRNS Relocation
Introduction Package. When the Iur resources are insufficient or SRNS relocation fails, the
DSCR feature ensures uninterrupted PS services.
Only background and interactive services support this feature. The DSCR re-establishes a service
through the routing area update procedure. Therefore, this feature is applicable only to PS
services.
Procedure
l
1.
Issue 06 (2013-03-25)
179
RAN14.0
modification center: not supported). In this step, set Handover Type for PS BE
Traffic to CORRM_SRNSR_PSBE_DSCR.
NOTE
The default value of Handover Type for PS BE Traffic is

CORRM_SRNSR_PSBE_RELOC. You can modify the value according to the actual
requirements.
2.
If the Iur interface exists, run the BSC6900 MML command SET
Modifying RNC Parameters in Batches) to turn on the switches related to SRNS
relocation.
3.
If the UE is not in the CELL_DCH state, run the BSC6900 MML command SET
URRCTRLSWITCH (CME single configuration: UMTS Radio Global
Configuration Express > Process Switch Configuration > Process Switch; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) to turn on
the DSCR switch for the DRNC.
1.
Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 40-1 and Figure
40-2.
Figure 40-1 Uu interface tracing dialog box
Issue 06 (2013-03-25)

180
RAN14.0
Figure 40-2 RRC CONNECTION RELEASE
2.
Use the UE to establish a PS BE service. Perform a handover by adding a cell under

the DRNC and then removing the source cell.
3.
View the RRC_RRC_CONN_REL message traced on the Uu interface. Check the

value of the IE releaseCause in the rrcConnectionRelease of the message. If the
value is Directed Signaling Connection re-establishment, this feature has been
activated.
1.
modification center: not supported). In this step, set Handover Type for PS BE
Traffic to CORRM_SRNSR_PSBE_RELOC.
----End
Example
//Activating Direct Signaling Connection Re-establishment (DSCR)
MOD UNRNC: NRncId=20, PsBeProcType=CORRM_SRNSR_PSBE_DSCR;
SrnsrSwitch=SRNSR_DSCR_IUR_RESRCE_SWITCH-1&SRNSR_DSCR_LOC_SEPRAT_SWITCH-1
&SRNSR_DSCR_PROPG_DELAY_SWITCH-1&SRNSR_DSCR_SEPRAT_DUR_SWITCH-1;
SET URRCTRLSWITCH: PROCESSSWITCH=DRNC_DIRECT_DSCR-1;
//Deactivating Direct Signaling Connection Re-establishment (DSCR)
MOD UNRNC: NRncId=20, PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
Issue 06 (2013-03-25)

181
RAN14.0
41
41 Configuring CS Fallback Guarantee for LTE Emergency

Calls
Configuring CS Fallback Guarantee for

LTE Emergency Calls
CS Fallback Guarantee for LTE Emergency Calls. For details about how to configure this feature
on the LTE side, see the related documents provided by the LTE equipment vendor.
Prerequisites
l

License
Other Prerequisites
UEs of Release 8 or later support PS handovers from LTE to UMTS and CSFB from
LTE to UMTS. In addition, the message sent to the MME carries an emergency call
indicator.
The eNodeB supports PS handovers from LTE to UMTS and CSFB from LTE to UMTS.
In addition, the handover request sent to the RNC carries CSFB High Priority.
The CN supports PS handovers from LTE to UMTS and CSFB from LTE to UMTS. In
addition, the INITIAL CONTEXT SETUP REQUEST message sent from the MME to
the eNodeB carries CS Fallback High Priority.
Context
In the CS Fall Back (CSFB) process for an LTE emergency call, a UE can initiate an emergency
call on the UMTS network only after the PS service has been admitted to the UMTS network.
This feature ensures the success of PS admission by decreasing the PS service rate or performing
resource preemption.
Procedure
l
Issue 06 (2013-03-25)
182
RAN14.0
41 Configuring CS Fallback Guarantee for LTE Emergency

Calls
1.
Configure the data on the LTE side, including setting the neighbor relationships
between cells.
For details about how to configure this feature on the LTE side, see the related
documents provided by the LTE equipment vendor. If the LTE equipment is provided
by Huawei, see the LTE document CS Fallback Parameter Description.
2.

Parameters in Batches). In this step, select HO_L2U_EMGCALL_SWITCH
under HandOver Switch to enable this feature.
After this feature is activated, the incoming LTE-to-UMTS PS handover success rate caused
by LTE emergency calls increases.
1.

Parameters in Batches). In this step, clear HO_L2U_EMGCALL_SWITCH under
HandOver Switch to disable this feature.
----End
Example
//Activating CS Fallback Guarantee for LTE Emergency Calls
SET UCORRMALGOSWITCH: HoSwitch= HO_L2U_EMGCALL_SWITCH-1;
//Deactivating CS Fallback Guarantee for LTE Emergency Calls
SET UCORRMALGOSWITCH: HoSwitch= HO_L2U_EMGCALL_SWITCH-0;
Issue 06 (2013-03-25)

183
RAN14.0
42
Configuring NodeB Clock
NodeB Clock.
Prerequisites
l
Ensure that a clock link is available before configuring the LINE clock source.
Ensure that the GPS card is configured before configuring the GPS card clock source.
Ensure that the USCU is configured before configuring the BITS clock source.
The BTS3006C and BTS3002E do not support the GPS clock input.
The BTS3902E cannot support GPS and BITS clock.

License
Context
In normal operation, the base station needs to track an external clock to calibrate its main clock
frequency. The synchronization of the base station clock provides the basis for the frame
synchronization.
The base station can work in multiple clock synchronization modes:
l
Synchronization with the Iub clock (default mode)
Synchronization with GPS
Synchronization with the BITS clock
Synchronization with the IP clock
Synchronization with the synchronous Ethernet clock (NodeB V200R014)
Synchronization with the multi-mode sharing clock (NodeB V200R014)
Synchronization with the PTP clock (NodeB V100R014)
In addition to the preceding synchronization modes, the MBTS internal clock can work in freerun mode to keep the MBTS running.
Issue 06 (2013-03-25)

184
RAN14.0
Procedure
l
NodeB V200R014
1.
Run the NodeB MML command SET CLKMODE (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Basic Information > Clock
Source > System Clock Link Management; CME batch modification center: not
supported) to set the working mode of the reference clock source.
Table 42-1 Parameters
Clock
Synchronization
Modes
Parameter Name
Parameter Value
Synchronization with the

Iub clock (default mode)
Selected Clock Source
LINECLK(Line Clock)
Synchronization with
GPS
GPS(GPS Clock)

BITS clock
BITS(BITS Clock)

IP clock
IPCLK(IP Clock)

synchronous Ethernet
clock
SYNCETH(SyncEth
Clock)

multi-mode sharing clock
PEERCLK(Peer Clock)
1.
Run the NodeB MML command DSP CLKSTAT to query the status of the current
clock source.
Expected result: The value of Current Clock Source State is Normal.
l
NodeB V100R014
1.
Issue 06 (2013-03-25)

185
RAN14.0
Table 42-2 Parameters

Clock
Synchronization
Modes
Parameter Name
Parameter Value

Iub clock (default mode)
Clock Source Type
LINE(LINE clock
source)
Synchronization with
GPS
GPSCARD(GPS card
clock source)

BITS clock
BITS(BITS clock source)

IP clock
IPCLK(IP clock source)

PTP clock
PTP(PTP clock source)
1.
clock source.
----End
Example
l
NodeB V200R014
//Synchronization with the Iub clock
SET CLKMODE: MODE=MANUAL, CLKSRC=LINECLK;
//Synchronization with the GPS clock
SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0;
//Synchronization with the BITS clock
SET CLKMODE: MODE=MANUAL, CLKSRC=BITS;
//Synchronization with the IP clock
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK;
//Synchronization with the synchronous Ethernet clock
SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH;
//Synchronization with the multi-mode sharing clock
SET CLKMODE: MODE=MANUAL, CLKSRC=PEERCLK;
DSP CLKSTAT: SN=7;
NodeB V100R014
//Synchronization with the Iub clock
SET CLKMODE: MODE=MANUAL, CLKSRC=LINE;
//Synchronization with the GPS clock
SET CLKMODE: MODE=MANUAL, CLKSRC=GPSCARD;
//Synchronization with the BITS clock
Issue 06 (2013-03-25)

186
RAN14.0

SET CLKMODE: MODE=MANUAL, CLKSRC=BITS;
//Synchronization with the IP clock
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK;
//Synchronization with the PTP clock
SET CLKMODE: MODE=MANUAL, CLKSRC=PTP;
DSP CLKSTAT:;
Issue 06 (2013-03-25)

187
RAN14.0
43 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur

Interface
43
Configuring Dynamic AAL2
Connections in Iub/IuCS/Iur Interface

Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.
Prerequisites
l
BTS3902E does not support this feature.

License
Others
The RAN is based on ATM transmission.
Context
In ATM transmission mode, the ATM Adaptation Layer type 2 (AAL2) path is used to carry the
user plane data on the Iub/Iur/Iu-CS interface. The AAL2 path is provided according to service
type (conversational, streaming, interactive, and background) and bearer type (R99, HSDPA,
and HSUPA). Physical bandwidth resources are dynamically allocated to delay-sensitive
services and delay-insensitive services, which improves the utilization of transmission links on
the Iub interface.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD ADJNODE (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > Adjacent
Node, IUR Configuration Express > ATM Transport > Adjacent Node, IUCS
Configuration Express > ATM Transport > Adjacent Node; CME batch
modification center: not supported) to add an adjacent node. Set the parameter
Adjacent Node Type to IUB, IUR, or IUCS, and the parameter Transport Type to
ATM. If the node is the lowest leaf node of the switching network, set the parameter
Is Root Node to YES; otherwise, set the parameter Is Root Node to NO.
188
RAN14.0
43 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur

Interface
NOTE
For an adjacent node on the Iur or Iu-CS interface, the parameter Adjacent Node Type of its upperlevel hub node must be NNI_AAL2SWITCH; for an adjacent node on the Iub interface, the
parameter Adjacent Node Type of its upper-level hub node must be UNI_AAL2SWITCH.
2.
Run the BSC6900 MML command ADD AAL2PATH (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > AAL2 Path,
IUCS Configuration Express > ATM Transport > AAL2 Path, IUR
Configuration Express > ATM Transport > AAL2 Path; CME batch modification
center: not supported) to add an AAL2 path. The parameters CARRYVPI and
CARRYVCI must be consistent with those of the AAL2 path configured on the peer
end.
1.
Run the BSC6900 MML command DSP AAL2PATH to query the status of the AAL2
path on the Iub interface.
Expected result: The value of Operation state is Available.
2.
In the Iub/Iu-CS ATM transmission scenario, a UE in idle state camps on CELL1 and
the control plane is correctly configured. Originate the speech and data services. If the
service access is normal, the AAL2 path on the Iub/Iu-CS interface is set up
successfully.
3.
Optional: In the ATM transmission scenario on the Iur interface, a UE in idle state
camps on CELL1 and the control plane is correctly configured. Originate a cross-Iur
handover. If the handover is successful, the AAL2 path on the Iur interface is set up
successfully.
----End
Example
//Activating Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
//Adding an adjacent node
ADD ADJNODE: ANI=2, NAME="MSC1", NODET=IUCS, TRANST=ATM, IsROOTNODE=YES,
DPX=1;
//Adding an AAL2 path
ADD AAL2PATH: ANI=2, PATHID=1, CARRYT=UNI, CARRYF=1, CARRYSN=14,
CARRYUNILNKN=0, RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=111, RXTRFX=111,
AAL2PATHT=R99;
//Verifying Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
DSP AAL2PATH: ANI=2, PATHID=1;
Issue 06 (2013-03-25)

189
RAN14.0
44 Configuring Permanent AAL5 Connections for Control

Plane Traffic
44
Configuring Permanent AAL5
Connections for Control Plane Traffic
Permanent AAL5 Connections for Control Plane Traffic.
Prerequisites
l

License
Others
The equipment data has been configured for the ATM transmission on the Iub/Iu/Iur
interface.
NOTE
For details about how to configure the equipment data, see section Configuring the Equipment
Data of the BSC6900UMTS Initial Configuration Guide.
Context
In the RAN in ATM transmission mode, AAL5 connections are used to bear the Iub/Iur/Iu
signaling and the Iub OAM traffic. As specified by 3GPP, User-Network Interface SAAL (UNISAAL) is used for control-plane connections on the Iub interface and Network-Network
Interface SAAL (NNI-SAAL) is used for control-plane connections on the Iur/Iu interface.
AAL5 connections on the Iub/Iur/Iu interface are all set up by configuring Signaling ATM
adaptation layer (SAAL) links.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD SAALLNK (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > SAAL Signaling
Link, IUCS Configuration Express > ATM Transport > SAAL Signaling Link,
190
RAN14.0
44 Configuring Permanent AAL5 Connections for Control

Plane Traffic
IUR Configuration Express > ATM Transport > SAAL Signaling Link; CME
batch modification center: not supported) to add an SAAL link. If the interface is Iub,
set the parameter Interface type to UNI. If the interface is Iu or Iur, set Interface
type to NNI.
2.
Optional: Run the BSC6900 MML command ADD UNCP (CME single
configuration: NodeB Configuration Express > IUB_RNC > ATM Transport >
NCP Link; CME batch modification center: not supported) to add a NodeB Control
Port (NCP) link.
3.
Optional: Run the BSC6900 MML command ADD UCCP (CME single
CCP Link; CME batch modification center: not supported) to add a Communication
Control Port (CCP) link.
NOTE
An SAAL link can carry only one NCP or CCP link. Therefore, choose to perform step 2 or
step 3 based on the actual situation.
1.
Run the BSC6900 MML command DSP SAALLNK to query the status of the SAAL
link.
Expected result: The value of SAAL link state is AVAILABLE.
NOTE
An SAAL link can carry only one NCP or CCP link. Therefore, choose to remove the NCP or CCP
link carried by the SAAL link, based on the actual situation.
1.
Optional: Run the BSC6900 MML command RMV UNCP (CME single
NCP Link; CME batch modification center: not supported) to remove the NCP link
carried by the SAAL link.
2.
Optional: Run the BSC6900 MML command RMV UCCP (CME single
CCP Link; CME batch modification center: not supported) to remove the CCP link
carried by the SAAL link.
3.
Run the BSC6900 MML command RMV SAALLNK (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > SAAL Signaling
Link, IUCS Configuration Express > ATM Transport > SAAL Signaling Link,
IUR Configuration Express > ATM Transport > SAAL Signaling Link; CME
batch modification center: not supported) to remove the SAAL link.
----End
Example
//Activating Permanent AAL5 Connections for Control Plane Traffic
ADD SAALLNK: SRN=1, SN=2, SAALLNKN=10, CARRYT=UNI, CARRYSRN=0,
CARRYSN=14, CARRYUNILNKN=2, CARRYVPI=10, CARRYVCI=55, TXTRFX=100,
RXTRFX=100, SAALLNKT=UNI;
ADD UCCP: NODEBNAME="NodeB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=10;
//Verifying Permanent AAL5 Connections for Control Plane Traffic
DSP SAALLNK: SRN=1, SN=2, SAALLNKN=10;
//Deactivating Permanent AAL5 Connections for Control Plane Traffic
RMV UCCP: NODEBNAME="NodeB1", PN=0;
RMV SAALLNK: SRN=1, SN=2, SAALLNKN=10;
Issue 06 (2013-03-25)

191
RAN14.0
45
45 Configuring Call Admission Based on Used AAL2 Path

Bandwidth
Configuring Call Admission Based on

Used AAL2 Path Bandwidth
Call Admission Based on Used AAL2 Path Bandwidth.
Prerequisites
l

License
Context
With the Call Admission Based on Used AAL2 Path Bandwidth (AAL2 CAC) feature, admission
requests are accepted or rejected selectively. This feature maximizes the usage of transmission
resources in addition to ensuring the QoS.
Procedure
l
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD ATMTRF (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > ATM Traffic
Record; CME batch modification center: not supported) to set parameters to
appropriate values. For example, set Service type to NRTVBR, Peak cell rate to
100, and Sustainable cell rate to 80.
2.
NodeB Configuration Express > IUB_RNC > ATM Transport > AAL2 Path;
CME batch modification center: not supported) to add an ATM Adaptation Layer type
2 (AAL2) path. In this step, set TXTRFX and RXTRFX in accordance with the
settings in step 1.
192
RAN14.0
45 Configuring Call Admission Based on Used AAL2 Path

Bandwidth
1.
Assume that the verification is based on the preceding parameter settings and the peer
end is configured with the corresponding AAL2 path link. Originate a PS interactive
service. If the data rate is 64 kbit/s, the UE successfully accesses the network.
2.
Run the BSC6900 MML command DSP AAL2PATH to view that the used bandwidth
of the path is about 37 kbit/s, which is the admission bandwidth of the control plane.
3.
Originate a PS interactive service. If the data rate is 128 kbit/s, the UE fails to access
the network.
----End
Example
ADD ATMTRF: TRFX=100, ST=NRTVBR, UT=CELL/S, PCR=100, SCR=80;
AAL2PATHT=R99;
Issue 06 (2013-03-25)

193
RAN14.0
46
46 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS

Classes
Configuring CBR, rt-VBR, nrt-VBR, UBR

ATM QoS Classes
This section describes how to activate, verify, and deactivate the basic feature
"WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes".
Prerequisites
l

License
Context
Huawei RAN supports service type of ATM :
l
Constant Bit Rate (CBR)
Real time Variable Bit Rate (rt-VBR)
Non-real time Variable Bit Rate (nrt-VBR)
Unspecified Bit Rate (UBR)
Enhanced unspecified Bit Rate (UBR+)
Configuring UBR+ QoS Class feature, please refer to Configuring UBR+ ATM QoS Class.
The traffic volume on the VCC depends on the parameters (SCR, PCR, and CDVT) associated
with each type of ATM service. Generally, rt-VBR is applicable to delay-sensitive services and
nrt-VBR is applicable to delay-insensitive services. In addition, UBR and nrt-VBR are applicable
to None Delay Sensitive service mapping on the HSDPA/HSUPA.
It is recommended for configuring service type of ATM shown as Figure 46-1.
Issue 06 (2013-03-25)

194
RAN14.0
46 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS

Classes
Figure 46-1 Service type of ATM
Procedure
l
1.
1.
Run the BSC6900 MML command ADD ATMTRF (CME single configuration:
Record; CME batch modification center: not supported) to add an ATM traffic record.
To add more ATM traffic records, run this command repeatedly.
Run the BSC6900 MML command LST ATMTRF to query the ATM traffic
configuration. The expected result is that the query result is consistent with the
configuration information.
1.
Run the BSC6900 MML command RMV ATMTRF (CME single configuration:
Record; CME batch modification center: not supported) to delete an ATM traffic
record. To delete more ATM traffic records, run this command repeatedly.
----End
Example
//Activating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
ADD ATMTRF: TRFX=105, ST=CBR, UT=CELL/S, PCR=1000;
//Verifying CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
LST ATMTRF: TRFX=105;
Deactivating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
RMV ATMTRF: TRFX=105;
Issue 06 (2013-03-25)

195
RAN14.0
47 Configuring F5
47
Configuring F5
F5. (This feature cannot be configured using the CME. )
Prerequisites
l
VCL CC is applicable to the AEUa, AOUa, AOUc, UOIa(ATM), and UOIc boards of
the BSC6900.
VCL PM is applicable to the AOUc and UOIc boards of the BSC6900.
Only BSC6900 does not support the latency detection based on IE LB.
Only 3900 series Base Station supports the passive detection based on IE LB.

License
Context
This feature supports:
l
ATM CC provides E2E continuity detection on the VCL.
PM function provides performance monitoring on the VCL.
It is recommended to activate VCL CC before activating VCL PM.
Procedure
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ACT VCLCC to activate the VCL CC or loopback
function for a link. To activate the function for multiple links, run this command
repeatedly. There are three types of links, that is, SAALLNK, AAL2PATH, and
IPOAPVC.

196
RAN14.0
47 Configuring F5
2.
Run the BSC6900 MML command ACT VCLPM to activate the VCL PM function
for a link. To activate the function for multiple links, run this command repeatedly.
There are three types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.
1.
Run the BSC6900 MML command DSP VCLCC to query the CC result of a VCL.
If the VCL CC is activated and the PVC is functional, the SINK activated state
and SOURCE activated state are UP, and LOC, AIS, and RDI alarm state is
normal.
If the loopback is activated and the PVC is functional, the loopback query result
is UP, and LOC, AIS, and RDI alarm state is normal.
2.
Run the BSC6900 MML command DSP VCLPM to query the PM result of a VCL.
If the VCL PM is activated, the SINK activated state and SOURCE activated
state are PM_UP, and PM Active Fail Alarm is Normal.
1.
Run the BSC6900 MML command DEA VCLCC to deactivate the VCL CC or
loopback function for a link. To deactivate the function for multiple links, run this
command repeatedly. There are three types of links, that is, SAALLNK, AAL2PATH,
and IPOAPVC.
2.
Run the BSC6900 MML command DEA VCLPM to deactivate the VCL PM for a
link. To deactivate the function for multiple links, run this command repeatedly. There
are three types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.
----End
Example
//Activating F5
ACT VCLCC: LNKT=SAALLNK,
ACT VCLPM: LNKT=SAALLNK,
//Verifying F5
DSP VCLCC: LNKT=SAALLNK,
DSP VCLPM: LNKT=SAALLNK,
//Deactivating F5
DEA VCLCC: LNKT=SAALLNK,
DEA VCLPM: LNKT=SAALLNK,
Issue 06 (2013-03-25)
SRN=3, SN=2, SAALLNKN=0, VCLTYPE=CC;

SRN=3, SN=2, SAALLNKN=0;

197
RAN14.0
48
Configuring UBR+ ATM QoS Class
This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305
UBR+ ATM QoS Class".
Prerequisites
l

License
Other Prerequisites
The basic information about the BSC6900 is configured. For details, see the Configuring
the Basic Data.
Context
Huawei RAN supports the UBR+ ATM service class. UBR+ is the enhanced UBR feature. It
adds the Minimum Desired Cell Rate (MDCR) indication. UBR+ is particularly applicable to
the OAM channels over the Iub interface. The MDCR of UBR+ ensures the reliability of the
OAM connection in case of transmission channel congestion, and the BE service of the UBR+
fully utilizes transmission bandwidth.
Procedure
l
1.
1.
l
Issue 06 (2013-03-25)
Run the MML command ADD ATMTRF (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > ATM Traffic Record;
CME batch modification center: not supported) to add an ATM traffic record of the
UBR+ class. To add more ATM traffic records, run this command repeatedly.
Run the MML command LST ATMTRF to query the ATM traffic configuration.
Expected result: The query result is consistent with the configuration information.
198
RAN14.0
1.
Run the MML command RMV ATMTRF (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > ATM Traffic Record;
CME batch modification center: not supported) to delete an ATM traffic record of the
UBR+ class. To delete more ATM traffic records, run this command repeatedly.
----End
Example
//Adding UBR+ ATM QoS Class
ADD ATMTRF: TRFX=105, ST=UBR_PLUS, UT=CELL/S, MCR=100;
//Verifying UBR+ ATM QoS Class
LST ATMTRF: TRFX=105;
//Deactivating UBR+ ATM QoS Class
RMV ATMTRF: TRFX=105;
Issue 06 (2013-03-25)

199
RAN14.0
49
Configuring Link Aggregation
Link Aggregation.
Prerequisites
l
This feature applies only to 3900 series base stations excluding the BTS3902E.
This feature is only supported on BSC6900.

In the earlier versions than RAN13.0, trunk group configuration cannot support IP PM.
License
Others
This feature requires the support from peer transmission devices, such as switches and
base stations.
This feature supports IP networking, layer 2 (L2) networking, and layer 3 (L3)
networking.
Context
This feature enables multiple FE or GE ports to be bound to form a logical port. This provides
high bandwidth for end-to-end transmission, achieves load sharing across these FE or GE ports,
and improves the transmission reliability.
Procedure
l
Activate Link Aggregation on the BSC6900.
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD DEVIP (CME single configuration:
Abis Configuration Express > IP Transport > Device IP Address; CME batch
modification center: not supported) to add a device IP address to a board.
2.
Run the BSC6900 MML command ADD ETHTRK (CME single configuration:
Abis Configuration Express > IP Transport > Link Aggregation; CME batch
modification center: not supported) to add an Ethernet link aggregation group. In
200
RAN14.0
this step, set the Trunk group work mode to LOAD_SHARING(Load

sharing), set the Aggregation Mode to STATIC_LACP when the peer end
supports the LACP protocol or set the Aggregation Mode to
MANUAL_AGGREGATION when the peer end does not support the LACP
protocol, and set the Flow control switch to ON(ON).
3.
Run the BSC6900 MML command ADD ETHTRKLNK (CME single

configuration: Abis Configuration Express > IP Transport > Link
Aggregation; CME batch modification center: not supported) to add a specified
physical port to an Ethernet link aggregation group.
NOTE
If the Ethernet link aggregation group is configured with multiple physical ports, repeat this step
until all the required physical ports are configured.
4.
Run the BSC6900 MML command ADD ETHTRKIP (CME single

configuration: Abis Configuration Express > IP Transport > Trunk IP
Address; CME batch modification center: not supported) to add an IP address to
an Ethernet link aggregation group. When multiple virtual local area network
(VLAN) gateways are planned, run this command for each IP address you want to
add.
Activate Link Aggregation on the NodeB.
1.
Run the NodeB MML command ADD DEVIP (CME single configuration: NodeB
Configuration Express > IUB_NodeB > IP Transport Layer > IPPort > Device
IP Address; CME batch modification center: 3.17 Modifying Physical NodeB
Parameters in Batches) to add a device IP address to an Ethernet port. In this
step, set Port Type to ETHTRK(Ethernet Trunk).
2.
Run the NodeB MML command ADD ETHTRK (CME single configuration:
NodeB Configuration Express > IUB_NodeB > IP Transport Layer >
IPPort > Ethernet Trunk; CME batch modification center: not supported) to add
an Ethernet link aggregation group.
3.
Run the NodeB MML command ADD ETHTRKLNK (CME single

configuration: NodeB Configuration Express > IUB_NodeB > IP Transport
Layer > IPPort > Ethernet Trunk > Ethernet Trunk Member; CME batch
modification center: not supported) to add a member port to an Ethernet link
aggregation group. When multiple member ports need to be added, run this
command for each port you want to add.
Verify the effect of Link Aggregation on the BSC6900.
1.
Run the BSC6900 MML command DSP ETHTRK to query whether an Ethernet
link aggregation group is available.
NOTE
Expected result: If the value of Status of ETHTRK is UP in the command output, the Ethernet
link aggregation group is available.
Issue 06 (2013-03-25)
2.
Set the IP address of the peer NE to be on the same network segment as the IP
address for the Ethernet link aggregation group. For example, set the IP address
of the peer NE to 16.16.16.2.
3.
Run the BSC6900 MML command PING IP to check the IP communication

between the local and peer ends.

201
RAN14.0

NOTE
Expected result: If this command is executed and the command output indicates that no packet
loss occurs, the Ethernet link aggregation group has been successfully configured.
Verify the effect of Link Aggregation on the NodeB.
1.
Run the NodeB MML commandDSP ETHTRK to query whether an Ethernet link
aggregation group is available.
2.
Run the NodeB MML commandDSP ETHTRKLNK to query whether a member

port of an Ethernet link aggregation group is available.
Deactivate Link Aggregation on the BSC6900.
1.
Run the BSC6900 MML commandRMV ETHTRKIP (CME single

configuration: Abis Configuration Express > IP Transport > Trunk IP
Address; CME batch modification center: not supported) to remove an IP address
from an Ethernet link aggregation group. If the removal fails, perform operations
as prompted.
2.
Run the BSC6900 MML commandRMV ETHTRK (CME single configuration:

Abis Configuration Express > IP Transport > Link Aggregation; CME batch
modification center: not supported) to remove an Ethernet link aggregation group.
Deactivate Link Aggregation on the NodeB.

1.
Run the NodeB MML commandRMV DEVIP (CME single configuration: NodeB
Configuration Express > IUB_NodeB > IP Transport Layer > IPPort > Device
IP Address; CME batch modification center: not supported) to remove a device
IP address.
2.
Run the NodeB MML commandRMV ETHTRK (CME single configuration:

IPPort > Ethernet Trunk; CME batch modification center: not supported) to
remove an Ethernet link aggregation group.
----End
Example
//Activating Link Aggregation on the BSC6900
ADD DEVIP: SRN=2, SN=26, DEVTYPE=LOGIC_IP, IPADDR="10.171.35.123";
ADD ETHTRK: SRN=2, SN=26, TRKN=2, WORKMODE=ACTIVE_STANDBY,
LACPMODE=MANUAL_AGGREGATION, FLOWCTRLSWITCH=ON;
ADD ETHTRKLNK: SRN=2, SN=26, TRKN=2, TRKLNKSN=26, TRKLNKPN=2,
WORKMODE=ACTIVE_STANDBY, PORTPRI=101;
ADD ETHTRKLNK: SRN=2, SN=26, TRKN=2, TRKLNKSN=27, TRKLNKPN=2,
WORKMODE=ACTIVE_STANDBY, PORTPRI=102;
ADD ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0, IPADDR="126.126.126.1",
MASK="255.255.255.0";
/Activating Link Aggregation on the NodeB
//Adding a device IP address to an Ethernet port
ADD DEVIP: CN=0, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETHTRK, PN=0,
IP="192.168.2.24", MASK="255.255.255.0";
//Adding an Ethernet link aggregation group and adding a member port to
an Ethernet link aggregation group
ADD ETHTRK: CN=0, SRN=0, SN=0, SBT=ETH_COVERBOARD, TN=0;
ADD ETHTRKLNK: CN=0, SRN=0, SN=0, SBT=ETH_COVERBOARD, TN=0, PN=0,
PRI=255, FLAG=YES;
Issue 06 (2013-03-25)

202
RAN14.0
//Deactivating Link Aggregation on the BSC6900

//Removing active/standby Ethernet link aggregation groups
RMV ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0;
RMV ETHTRK: SRN=2, SN=26, TRKN=2;
//Deactivating Link Aggregation on the NodeB
//Removing a device IP address from an Ethernet port
RMV DEVIP: CN=0, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETHTRK, PN=0,
IP="192.168.2.24";
//Removing an Ethernet link aggregation group
RMV ETHTRK: CN=0, SRN=0, SN=0, SBT=ETH_COVERBOARD, TN=0;
Issue 06 (2013-03-25)

203
RAN14.0
50
Configuring Flow Control
Flow Control.
Prerequisites
l
NodeB RRC link priority based flow control is depended on WMPT and WBBP boards.

License
Context
Flow control is implemented by regulating the input transmission rate. This mechanism is called
feedback flow control mechanism.
The flow control measures are as follows:
l
Board flow control
Control-plane load sharing
User-plane load sharing
Flow control based on RRC request queuing
Flow control based on MPU load
Flow control based on traffic growth
Procedure
Activating board flow control
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET FCSW (CME single configuration:
UMTS Radio Global Configuration Express > Flow Control Management >
Flow Control Switch; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to switch on the flow control and related flow control
items.
204
RAN14.0
2.
Run the BSC6900 MML command SET FCCPUTHD (CME single

configuration: UMTS Radio Global Configuration Express > Flow Control
Management > Flow Control Threshold of CPU Usage; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches) to configure
the CPU usage threshold for each flow control item according to the network plan.
NOTE
l Flow control is triggered when the CPU usage exceeds the related threshold.
l The CPU usage thresholds must meet the following condition: 100 Critical threshold
Threshold for a flow control item Restore threshold for a flow control item
l The critical threshold is of the highest priority. That is, other thresholds take effect only
when the CPU usage is lower than the critical threshold.
l The flow control based on the packet usage and that based on the CPU usage are independent.
The system limits the flow to the lower one allowed by these two flow control algorithms.
3.
Run the BSC6900 MML command SET FCMSGQTHD (CME single

configuration: UMTS Radio Global Configuration Express > Flow Control
Management > Flow Control Threshold of Message Queue Usage; CME batch
the packet usage threshold for each flow control item according to the network
plan.
NOTE
l Flow control is triggered when the packet usage exceeds the related threshold.
l The packet usage thresholds must meet the following condition: 100 Critical threshold
Threshold for a flow control item Restore threshold for a flow control item
l The critical threshold is of the highest priority. That is, other thresholds take effect only
when the packet usage is lower than the critical threshold.
l The flow control based on the packet usage and that based on the CPU usage are independent.
The system limits the flow to the lower one allowed by these two flow control algorithms.
Activating control-plane load sharing

1.

Modifying RNC Parameters in Batches). In this step, set Process switch to
RNC_SHARE_SWITCH to switch on load sharing.
2.
(Optional) Run the BSC6900 MML command SET

UCTRLPLNSHAREPARA (CME single configuration: UMTS Radio Global
Configuration Express > Flow Control Management > Control Plane RRC
Sharing Parameter; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches). In this step, set Control Plane Sharing Out
Threshold to 40 so that the control-plane load sharing function can be triggered
easily. The default value of Control Plane Sharing Out Threshold is 50.
NOTE
l If the CPU usage is higher than this threshold and lower than the overload threshold, new
calls will be assigned to other SPUs. Overload threshold is set by the MML command SET
SHARETHD (CME single configuration: UMTS Radio Global Configuration Express
> Flow Control Management > Load Sharing Threshold of SPU Board; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches).
l Max capability middle load> Max capability normal load> Sharing out capability
middle load.
Activating user-plane load sharing

Issue 06 (2013-03-25)

205
RAN14.0
1.
Run the BSC6900 MML command SET UUSERPLNSHAREPARA (CME

single configuration: UMTS Radio Global Configuration Express > Typical
Signaling Configuration > Typical SRB HSUPA Power Control Parameters;
CME batch modification center: 3.15 Modifying RNC Parameters in Batches).
In this step, set Percentage of User Plane Sharing Out threshold according to
the network plan. Inter-subrack user-plane load sharing is triggered when the user
plane load on one subrack exceeds this threshold.
Activating flow control based on RRC request queuing

1.

configuration: UMTS Radio Global Configuration Express > CAC Algorithm
Switch Configuration > CAC Algorithm Switch; CME batch modification
center: 3.15 Modifying RNC Parameters in Batches). In this step, select
RSVDBIT14 in Reserved parameter 1.
Activating flow control based on MPU load

1.

RSVDBIT1_BIT19 in Reserved parameter 1.
Activating flow control based on traffic growth

1.
Run the BSC6900 MML command SET UCALLSHOCKCTRL (CME single

configuration: UMTS Radio Global Configuration Express > Traffic Volume
Control Parameter Configuration > Call Shock Control Parameters; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches). In this
step, select CELL_LEVEL in Call Shock Control Switch to switch on the celllevel flow control based on traffic growth.
Verifying board flow control
1.
Run the BSC6900 MML command LST FCSW to query the state of the flow
control switch.
2.
Run the BSC6900 MML command LST FCCPUTHD to query the CPU usage
threshold for flow control.
3.
Run the BSC6900 MML command LST FCMSGQTHD to query the packet usage
threshold for flow control.
Verifying control-plane and user-plane load sharing

1.
On the LMT, choose Monitor > Common Monitoring > CPU/DSP Usage
Monitoring to observe the CPU usage of each subsystem. If the CPU usage of
each subsystem is almost the same, load sharing takes effect.
Verifying flow control based on RRC request queuing

1.
Run the BSC6900 MML command LST UCACALGOSWITCH to query the

state of the switch for flow control based on RRC request queuing.
Verifying flow control based on MPU load

1.
Run the BSC6900 MML command LST URRCTRLSWITCH to query the state
of the switch for flow control based on MPU load.
Verifying flow control based on traffic growth

Issue 06 (2013-03-25)

206
RAN14.0
1.
l
Run the BSC6900 MML command LST UCALLSHOCKCTRL to query the

state of the switch for flow control based on traffic growth.
Deactivating board flow control
1.
Run the BSC6900 MML command SET FCSW (CME single configuration:
UMTS Radio Global Configuration Express > Flow Control Management >
Flow Control Switch; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to switch off flow control.
Deactivating control-plane load sharing

1.

Modifying RNC Parameters in Batches) to deselect
RNC_SHARE_SWITCH in Process switch.
Deactivating user-plane load sharing

1.
User-plane load sharing does not need to be deactivated.
Deactivating flow control based on RRC request queuing

1.

center: 3.15 Modifying RNC Parameters in Batches). In this step, deselect
RSVDBIT14 in Reserved parameter 1.
Deactivating flow control based on MPU load

1.

Modifying RNC Parameters in Batches). In this step, deselect
RSVDBIT1_BIT19 in Reserved parameter 1.
Deactivating flow control based on traffic growth

1.
Run the BSC6900 MML command SET UCALLSHOCKCTRL (CME single

configuration: UMTS Radio Global Configuration Express > Traffic Volume
Control Parameter Configuration > Call Shock Control Parameters; CME
step, deselect CELL_LEVEL in Call Shock Control Switch.
----End
Example
//Activating board flow control
//Switching on XPU load control
SET FCSW: BRDCLASS=XPU, FCSW=ON, PRINTSW=ON, TRACESW=ON, PMSW=ON,
LOGSW=ON;
//Setting CPU usage threshold for DPU flow control
SET FCCPUTHD:BRDCLASS=DPU, SMWINDOW=6, FDWINDOW=2, CTHD=95, PRINTCTHD=60,
PRINTRTHD=50, TRACECTHD=60, TRACERTHD=50, LOGCTHD=60, LOGRTHD=50;
//Setting packet usage threshold for DPU flow control
SET FCMSGQTHD: BRDCLASS=DPU, SMWINDOW=9, CTHD=95, PRINTCTHD=60,
PRINTRTHD=50, TRACECTHD=60, TRACERTHD=50, LOGCTHD=60, LOGRTHD=50;
Issue 06 (2013-03-25)

207
RAN14.0
//Activating control-plane load sharing

SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-1;
SET UCTRLPLNSHAREPARA: CtrlPlnSharingOutThd=40;
SET SHARETHD: BT=XPU, SMRRCCONNCCPUTHD=80, SMRRCCONNRCPUTHD=70,
CRRCCONNCCPUTHD=80, CRRCCONNRCPUTHD=70, LRRCCONNCCPUTHD=80,
LRRCCONNRCPUTHD=70, SMRRCCONNCMSGTHD=80, SMRRCCONNRMSGTHD=70,
CRRCCONNCMSGTHD=80, CRRCCONNRMSGTHD=70, LRRCCONNCMSGTHD=80,
LRRCCONNRMSGTHD=70;
//Activating user-plane load sharing
SET UUSERPLNSHAREPARA: UserPlnSharingOutThd=90;
//Activating RRC Shaping and Queuing
SET UCACALGOSWITCH:RsvdPara1=RSVDBIT14-1;
//Activating flow control based on MPU load
//Activating flow control based on traffic growth
SET UCALLSHOCKCTRL: CallShockCtrlSwitch=CELL_LEVEL-1;
//Verifying board flow control
LST FCSW: LstFormat=VERTICAL;
LST FCCPUTHD: LstFormat=VERTICAL;
LST FCMSGQTHD: LstFormat=VERTICAL;
//Verifying flow control based on RRC request queuing
LST UCACALGOSWITCH: LstFormat=VERTICAL;
//Verifying flow control based on MPU load
LST URRCTRLSWITCH: LstFormat=VERTICAL;
//Verifying flow control based on traffic growth
LST UCALLSHOCKCTRL: LSTFORMAT=VERTICAL;
//Deactivating board flow control
SET FCSW: BRDCLASS=XPU, FCSW=OFF;
//Deactivating control-plane load sharing
SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-0;
//Deactivating flow control based on RRC request queuing
SET UCACALGOSWITCH: RsvdPara1=RSVDBIT14-0;
//Deactivating flow control based on MPU load
//Deactivating flow control based on traffic growth
SET UCALLSHOCKCTRL: CallShockCtrlSwitch=CELL_LEVEL-0;
Issue 06 (2013-03-25)

208
RAN14.0
51
Configuring BOOTP
BOOTP. In ATM transport mode, the NodeB can automatically set up the OM channel with the
BSC6900 by using the BOOTSTRAP Protocol (BOOTP) function.
Prerequisites
l
The transmission equipment is in the connected state.
BOOTP applies only to ATM networking scenarios.

License
Context
This feature enables NodeB to set up the OM channel to the RNC automatically without
configuration data. The maintenance staff can download the data and software to the NodeB
through the OM channel at the far end. The feature decreases the operation and maintenance
costs and enhances the network maintainability and maintenance quality. NodeB will
automatically set up the OM channel using the BOOTP protocol. In addition, NodeB monitors
the OM channel. When the OM channel is broken, NodeB can rebuild it.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD DEVIP (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > Device IP Address;
CME batch modification center: not supported) to add the logical IP address for the
interface board of the BSC6900. This IP address serves as the local address of the
IPoA at the BSC6900.
2.
Run the BSC6900 MML command ADD IPOAPVC (CME single configuration:
IUPS Configuration Express > ATM Transport > IPoA PVC; CME batch
modification center: not supported) to add the IPoA PVC for bearing the OM channel.
3.
Run the BSC6900 MML command ADD UNODEBIP (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > NodeB IP
209
RAN14.0
Address; CME batch modification center: not supported) to add the IP address for the
OM channel of the NodeB.
l
If the BOOTP configurations at the BSC6900 are completed but no configuration at the
NodeB and the NodeB can be maintained on the M2000, it indicates that the NodeB has
successfully set up the OM channel by using the BOOTP feature.
----End
Example
ADD DEVIP: SRN=0, SN=14, DEVTYPE=IPOA_CLIENT_IP,
IPADDR="131.131.131.132", MASK="255.255.255.0";
ADD IPOAPVC: IPADDR="131.131.131.132", PEERIPADDR="131.131.131.131",
CARRYT=IMA,
CARRYIMAGRPN=0, CARRYVPI=83, CARRYVCI=80, TXTRFX=100;
ADD UNODEBIP: NODEBID=0, NBTRANTP=ATMTRANS_IP,
NBATMOAMIP="131.131.131.131",
NBATMOAMMASK="255.255.255.0", ATMSRN=0, ATMSN=14;
Issue 06 (2013-03-25)

210
RAN14.0
52
Configuring NodeB Self-Discovery

Based on IP Mode
NodeB Self-Discovery Based on IP Mode.
Prerequisites
l
The transmission equipment is in the connected state.
DHCP applies only to IP networks.
Only 3900 series base stations support DHCP+AACP.

License
Others
If NodeB self-discovery uses the DHCP+AACP scheme
VLANs are used to separate NodeBs to be deployed from other network devices not
required.
VLAN detection and IP path detection must be disabled on the M2000 to prevent
interference during AACP detection.
the deployment list of NodeBs to be commissioned must be ready. For details, see
the NodeB Commissioning Guide.
A bidirectional forwarding detection (BFD) session failure results in a NodeB
automatic deployment failure. Therefore, the BFD function must be disabled on the
gateway side if it is enabled on the NodeB side.
The IP path ping function must be disabled on the RNC side during NodeB automatic
deployment. Otherwise, when the ping message sent by the RNC reaches the
gateway, the gateway sends an ARP request to the NodeB, disturbing the AACP
detection process and resulting in a NodeB automatic deployment failure.
AACP and DHCP messages can be processed through port 67 or 68. Ports 67 and 68
must be enabled for the firewall in the radio network.
Issue 06 (2013-03-25)

211
RAN14.0
M2000 should support NodeB Auto Deployment function.
Context
l
If the configuration file is incorrect, DHCP enables NodeBs to establish OM channels for
NodeB remote maintenance.
The configuration is not required on the NodeB. If the hub NodeB is used, the configuration
on the hub NodeB is required. The configuration is required on the DHCP server, for
example, BSC6900 and M2000. Following takes BSC6900 for example.
Data Preparation
PPP/MLPPP networking
Parameter Name
Recommended
Parameter Settings
Source
NodeB ID
Network plan
NodeB DHCP Server IP

Address
It is set to the IP address of

the M2000 server by
default. If there are several
DHCP servers, the IP
addresses need to be added
manually.
NodeB AACP Server IP

Address

the M2000 server.
Ethernet networking
Issue 06 (2013-03-25)
Parameter Name
Recommended
Parameter Settings
Source
NodeB ID
Network plan
NodeB DHCP Server IP

Address

the M2000 server by
default. If there are several
DHCP servers, the IP
addresses need to be added
manually.
NodeB Next Hop IP

Address to DHCP Server
It is set to the gateway IP

address of the M2000
server by default. If there
are several DHCP servers,
the IP addresses need to be
added manually.
NodeB AACP Server IP

Address

the M2000 server.
NodeB Next Hop IP

Address to AACP Server
It is set to the gateway IP

address of the M2000
server.

212
RAN14.0
Parameter Name
Recommended
Parameter Settings
Interface subnet mask of

the NodeB
Interface subnet mask of

the NodeB
Source
Procedure
l
Activation Procedure (NodeB Self-Discovery Based on DHCP)

1.
Run the BSC6900 MML command ADD UNODEBESN (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > NodeB Electronic
Serial Number; CME batch modification center: not supported) to add the NodeB
ESN in response to the DHCP request reported by the NodeB.
2.
Run the BSC6900 MML command ADD UNODEBIP (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > NodeB IP
Address; CME batch modification center: not supported) to add the IP address for the
OM channel of the NodeB. When the BSC6900 makes a response to the DHCP
request, it sends the IP address to the NodeB.
3.
Optional: If the Hub NodeB is used and the DHCP function is used for NodeB selfdiscovery, the following configurations are required.
a.
Run the NodeB MML command SET DHCPRELAYSWITCH (CME single

configuration: NodeB Configuration Express > IUB_NodeB > Basic
Information > Transport Management > DHCP Relay Switch; CME batch
modification center: not supported) to enable DHCP relaying of the NodeB.
b.
Run the NodeB MML command ADD DHCPSVRIP (CME single

Information > Transport Management > DHCP Server IP Address; CME
batch modification center: not supported) to add the IP address of the DHCP
server so that lower-level NodeBs can automatically obtain the IP address of the
DHCP server through DHCP.
Activation Procedure (NodeB Self-Discovery Based on DHCP+AACP)

1.
Optional: Run the NodeB MML command SET NODEBRSVP (CME single
Information > Radio Management > NodeB Reserved Para; CME batch
modification center: not supported). In this step, select RSVDBIT29(Reserved
Switch 29) under Reserved Parameter 1.
2.
On the M2000 client, Choose Configuration > Auto Deployment > NodeB Auto
Deployment. Right-click the import the deployment list, and choose Task Setting
from the shortcut menu. The Task Settings dialog box is displayed.
3.
Select Use AACP during Auto Discovery to use AACP for NodeB automatic
deployment, Click OK to start NodeB automatic deployment.
Check the status of NodeB automatic deployment in either of the following ways:
On the deployment list of the M2000
Issue 06 (2013-03-25)
1.
Click Show Executing Information on the Deployment List tab page.
2.
View the information displayed in the Description column. If Execution

Succeed is displayed, AACP-based NodeB automatic deployment is successful.
213
RAN14.0
If AACP detection timed out is displayed, AACP-based NodeB automatic

deployment fails.
On the topology view of the M2000
Choose Topology > Main Topology to view the Main Topology tab page. If
is
displayed beside a NodeB on the Main Topology tab page, the NodeB failed to be
deployed.
l
1.
If the DHCP+AACP function is used for NodeB self-discovery, Run the NodeB MML
command SET NODEBRSVP (CME single configuration: NodeB Configuration
Express > IUB_NodeB > Basic Information > Radio Management > NodeB
Reserved Para; CME batch modification center: not supported). In this step, clear
RSVDBIT29(Reserved Switch 29) under Reserved Parameter 1.
----End
Example
//NodeB Self-Discovery Based on DHCP
//Operations on the BSC6900 side
ADD UNODEBESN: NODEBID=0, NBLB1="020GKV1082000126", USENBLB2=Disable,
NODEBPT=ETH/TRUNK, PTIP="131.131.131.132", PTIPMASK="255.255.255.0";
ADD UNODEBIP: NODEBID=0, NBTRANTP=IPTRANS_IP,
NBIPOAMIP="131.131.131.131", NBIPOAMMASK="255.255.255.0", IPSRN=0,
IPSN=18, IPLOGPORTFLAG=NO;
//(Optional) Operations on the NodeB side
//Enabling DHCP relaying of the NodeB
SET DHCPRELAYSWITCH: ES=ENABLE;
//Adding the IP address of the DHCP server
ADD DHCPSVRIP: DHCPSVRIP="13.13.13.13";
//NodeB Self-Discovery Based on DHCP+AACP
SET NODEBRSVP: REVDPARA1=RSVDBIT29-1;
//Deactivation procedure
SET NODEBRSVP: REVDPARA1=RSVDBIT29-0;
Issue 06 (2013-03-25)

214
RAN14.0
53
Configuring License Control for Urgency

License Control for Urgency. (This feature cannot be configured using the CME. )
Prerequisites
l
Only BSC6900 supports this feature.

License
Context
CAUTION
This feature is enabled only in scenarios where the traffic volume increases abruptly, for
example, in a disaster.
It can be enabled only three times for each R version by BSC6900 MML command SET
LICENSECTRL and it can be enabled only fifteen times by WRFD-040202 RNC Node
Redundancy and it is valid only for seven days each time.
After this function is enabled, a network can reach its maximum capacity that is supported by
the hardware. This documentation describes the procedure of enabling the feature by
BSC6900 MML command .
Procedure
l
Issue 06 (2013-03-25)
1.
On the BSC6900 side: Run the BSC6900 MML command SET LICENSECTRL. In
this step, set Grace Protection Period Switch to ON(ON).
2.
On the NodeB V200R014 side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch State to ON.
215
RAN14.0
3.
l
On the NodeB V100R014 side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch to ON(ON).
1.
On the BSC6900 Side

a.
Run the BSC6900 MML command DSP LICUSAGE to view resource items of
the license.
Expected result: All the resource items reach their maximum values.
b.
Run the BSC6900 MML command LST LICENSECTRL to query the setting
of Grace Protection Period Switch State.
Expected result: Values of Remaining Grace Protection Times and Remaining
Grace Protection Days are displayed and the value of Grace Protection Period
Switch State is ON.
2.
On the NodeB V200R014 side or NodeB V100R014 side

a.
Run the NodeB MML command DSP LICENSE to view resource items of the
license.
Expected result: All the resource items reach their maximum values.
b.
Run the NodeB MML command LST LICENSECTRL to query the setting of
Grace Protection Period Switch State.
Expected result: Values of Remaining Grace Protection Times and Remaining
Grace Protection Days are displayed and the value of Grace Protection Period
Switch State is ON.
1.
On the BSC6900 Side: Run the BSC6900 MML command SET LICENSECTRL.
In this step, set Grace Protection Period Switch to OFF(OFF).
2.
On the NodeB V200R014 Side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch State to OFF.
3.
On the NodeB V100R014 Side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch to OFF(OFF).
----End
Issue 06 (2013-03-25)

216
RAN14.0
54
Configuring Intelligently Out of Service

Intelligently Out of Service.
Prerequisites
l

License
Context
NodeB reset will interrupt ongoing services. After intelligently Out of Service has been
introduced, the NodeB automatically reduces the pilot transmit power if the NodeB resets. As
a result, UEs can be handed over to other neighboring cells to prevent service interruption.
Procedure
l
1.
Run the NodeB MML command SET SMTHPWRSWTCH (CME single

Information > Basic Information > Smooth Power Change Function Switch;
CME batch modification center: not supported). In this step, set Smooth Power
Change Function Switch to OPEN(Open).
2.
Run the NodeB MML command SET SMTHPWRPARA (CME single

Information > Basic Information > Smooth Power Change Function Switch;
CME batch modification center: not supported). In this step, set Smart default step
(0.5dB) and Smart default time ratio(100ms).
1.
Issue 06 (2013-03-25)
Run the NodeB MML command LST SMTHPWRSWTCH. In this step, check
whether Smooth Power Change Function Switch is set to OPEN.
217
RAN14.0
2.
l
Run the NodeB MML command LST SMTHPWRPARA. In this step, check whether
Smart default step(0.5dB) and Smart default time ratio(100ms) are set correctly.
----End
Example
SET SMTHPWRSWTCH: SWITCH=OPEN;
SET SMTHPWRPARA: STEP=10, PERIOD=1;
LST SMTHPWRSWTCH:;
LST SMTHPWRPARA:;
Issue 06 (2013-03-25)

218
RAN14.0
55 Configuring OCNS
55
Configuring OCNS
OCNS (Orthogonal Channel Noise Simulator). (This feature cannot be configured using the
CME. )
Prerequisites
l

License
Context
With the OCNS feature, multiple downlink analog channels are set up on the Uu interface to
simulate the interference of multiple codes. In this way, the simulated downlink load test of a
cell can be performed.
Procedure
l
1.
Run the NodeB MML command STR DLSIM to start downlink load simulation. In
this step, set Local Cell ID and Load Ratio (%).
NOTE
l This command can be successfully executed only when the corresponding logical cell exists.
l The downlink network load simulation uses the channelization codes from 112 to 127 whose
SF = 128.
l If you start the downlink network load simulation, it is advised to reserve the channelization
codes in the RNC.
l After starting the DL load simulation, new service can not be built in the channel resource
occupied by the simulation.
l
Issue 06 (2013-03-25)
219
RAN14.0
55 Configuring OCNS
1.
Run the NodeB MML command DSP DLSIM to query the downlink load simulation
result. In this step, specify Local Cell ID. The execution result displayed on the LMT
shows the simulated load rate.
1.
Run the NodeB MML command STP DLSIM to stop the downlink load simulation.
In this step, specify Local Cell ID.
----End
Example
STR DLSIM: LOCELL=1, LR=80;
DSP DLSIM: LOCELL=1;
STP DLSIM: LOCELL=1;
Issue 06 (2013-03-25)

220
RAN14.0
56
Configuring Power Off the Equipment

Level by Level
Power Off the Equipment Level by Level.
Prerequisites
l
Cabinets providing AC input power such as APM30, APM100, and APM200. These
cabinets can be used for outdoor NodeBs.

License
Context
After the mains supply is cut off, the NodeB powers off devices by level when certain DC voltage
thresholds are reached. Intelligent shutdown of RF units and NodeBs can prolong the working
time of the system by making efficient use of the available storage batteries.
Procedure
l
NodeB V200R014
Issue 06 (2013-03-25)
1.
Run the NodeB MML command MOD PMU (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > Right click PMU board
> PMU Porperty > Power Monitoring Unit; CME batch modification center: not
supported). In this step, set Load Shutdown Flag to ENABLE(Enable) and set Load
Shutdown Voltage(0.1V) if needed.
2.
Run the NodeB MML command MOD BATTERY (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Device Panel > Right click PMU
board > Battery Property > Battery; CME batch modification center: not
221
RAN14.0
supported). In this step, set Low Voltage Shutdown Flag to ENABLE and set
Shutdown Voltage(0.1V) if needed.
1.
Run the NodeB MML command LST PMU and query the values of Load Shutdown
Flag and Load Shutdown Voltage(0.1V).
2.
Run the NodeB MML command LST BATTERY and query the values of Low
Voltage Shutdown Flag and Shutdown Voltage(0.1V).
1.
Run the NodeB MML command MOD BATTERY (CME single configuration:
board > Battery Property > Battery; CME batch modification center: not supported)
and set Low Voltage Shutdown Flag to DISABLE(Disable).
2.
Run the NodeB MML command MOD PMU (CME single configuration: NodeB
> PMU Porperty > Power Monitoring Unit; CME batch modification center: not
supported) and set Load Shutdown Flag to DISABLE(Disable).
NodeB V100R014
1.
Run the NodeB MML command SET SDPA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > PMU Board > PMU
Property > PMU Shutdown Parameter; CME batch modification center: not
supported). In this step, set Load Shutdown Flag to ENABLE(Enable), set Load
Shutdown Voltage(0.1V) if needed, set Low Voltage Shutdown Flag to ENABLE
(Enable), set Shutdown Voltage(0.1V) if needed.
1.
Run the NodeB MML command LST SDPA, query the values of Load Shutdown
Flag and Load Shutdown Voltage(0.1V),, query the values of Low Voltage
Shutdown Flag and Shutdown Voltage(0.1V),.
1.
Run the NodeB MML command SET SDPA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > PMU Board > PMU
Property > PMU Shutdown Parameter; CME batch modification center: not
supported). In this step, set Load Shutdown Flag to DISABLE(Disable), and set
Low Voltage Shutdown Flag to DISABLE(Disable).
----End
Example
l
NodeB V200R014
MOD PMU: CN=1, PTYPE=APM30, LSDF=ENABLE, LSDV=430;
MOD BATTERY: CN=1, LVSDF=ENABLE, SDV=360;
LST PMU: CN=1;
LST BATTERY: CN=1;
Issue 06 (2013-03-25)

222
RAN14.0

MOD BATTERY: CN=1, LVSDF=DISABLE;
MOD PMU: CN=1, PTYPE=APM30, LSDF=DISABLE;
NodeB V100R014
SET SDPA: CN=1, LSDF=ENABLE, LSDV=440, LVSDF=ENABLE, SDV=360,
CSLSDF=DISABLE;
LST SDPA: CN=1;
SET SDPA: CN=1, LSDF=DISABLE, LVSDF=DISABLE, CSLSDF=DISABLE;
Issue 06 (2013-03-25)

223
RAN14.0
57
Configuring Solar Power Device

Management
Solar Power Device Management.
Prerequisites
l
Only 3900 series base stations support the feature.

License
Context
As green energy, solar power is being gradually introduced for supplying power for the NodeB.
This feature enables the NodeB to communicate with a solar controller through the 485 serial
port, therefore managing a solar power device, which makes the NodeB an eco-friendly base
station.
Procedure
l
1.
Run the NodeB MML command ADD PMU (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > Add PMU; CME batch
modification center: not supported) to add a PMU. In this step, set Power System
Type to SC48200.
2.
Optional: If a diesel generator is required, run the NodeB MML command ADD
DIESELGEN (CME single configuration: NodeB Configuration Express >
IUB_NodeB > Device Panel > Right click PMU board > PMU Property > Diesel
Generator; CME batch modification center: not supported).
Set Intelligent Control Flag to ENABLE(Enable).
Issue 06 (2013-03-25)

224
RAN14.0
Set Rated Power(0.1kVA) based on the rated power specified on the nameplate
of the diesel generator.
l
1.
Run the NodeB MML command DSP PMU to query the configuration information
about the PMU.
Expected result: The value of Power System Type is SC48200.
2.
Optional: Run the NodeB MML command LST DIESELGEN to query the
configuration information about the diesel generator.
Expected result: The value of Intelligent Control Flag is ENABLE.
1.
Run the NodeB MML command RMV DIESELGEN (CME single configuration:
board > PMU Property > Diesel Generator; CME batch modification center: not
supported) to remove a dieselgen.
2.
Run the NodeB MML command RMV PMU (CME single configuration: NodeB
> Dlete PMU; CME batch modification center: not supported) to remove a PMU.
----End
Example
ADD PMU: CN=0, PTYPE=SC48200, MPN=0, LSDF=ENABLE;
ADD DIESELGEN: CN=0, ICF=ENABLE, POWER=500;
DSP PMU: CN=0;
LST DIESELGEN: CN=0;
RMV DIESELGEN: CN=0;
RMV PMU: CN=0;
Issue 06 (2013-03-25)

225
RAN14.0
58 Configuring Connection with TMA (Tower Mounted

Amplifier)
58
Configuring Connection with TMA

Connection with TMA (Tower Mounted Amplifier). (This feature cannot be configured using
the CME. )
Prerequisites
l
The base station is connected to the Antenna Line Device (ALD) normally.
The BTS3902E cannot support this feature.

License
Others
The TMA is loaded with basic software for its normal operation.
Context
The gain range supported by the Smart Tower-Mounted Amplifier (STMA) varies with models
and vendors.
Procedure
l
NodeB V200R014
Issue 06 (2013-03-25)
1.
Run the NodeB MML command MOD ANTENNAPORT to set ALD Power
Switch to ON.
2.
Run the NodeB MML command SCN ALD to scan the Device Name, Vendor
Code and Serial No..
3.
Run the NodeB MML command ADD TMA to add a TMA.
4.
Optional: If the device supports TMA gain, run the NodeB MML command MOD
TMASUBUNIT to set the TMA gain.
226
RAN14.0

Amplifier)
NOTE
It is recommended that you query the gain range supported by the STMA using the NodeB MML
command DSP TMADEVICEDATA before adjusting the gain.
5.
Run the NodeB MML command MOD RXBRANCH to modify the RX channel of
an RRU.
1.
Run the NodeB MML command DSP TMA to query the dynamic information about
a TMA.
l
NodeB V100R014
1.
Run the NodeB MML command SET ALDPWRSW to set Power Supply Switch to
ON(On).
2.
Run the NodeB MML command SCN ALD to scan Device Name, Vendor Code and
Serial No..
3.
Run the NodeB MML command ADD ALD to add a TMA.
4.
Optional: If the device supports TMA gain, run the NodeB MML command SET
TMAGAIN to set the TMA gain.
NOTE
It is recommended that you query the gain range supported by the STMA using the NodeB MML
command DSP TMAFUN before adjusting the gain.
5.
Run the NodeB MML command SET RXATTEN to set the attenuation of the RX
channel.
1.
Run the NodeB MML command LST TMAGAIN to query the TMA gain.
2.
Run the NodeB MML command LST RXATTEN to query the RX attenuation value.
----End
Example
l
NodeB V200R014
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
SCN ALD: CTRLCN=0, CTRLSRN=60, CTRLSN=0;
ADD TMA: DEVICENO=0, DEVICENAME="TMA1", CTRLCN=0, CTRLSRN=60,
CTRLSN=0, SUBUNITNUM=1;
MOD TMASUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNPN=R0A, MODE=NORMAL,
GAIN=48;
MOD RXBRANCH: CN=0, SRN=60, SN=0, RXNO=0, ATTEN=0;
DSP TMA: DEVICENO=0;
l
Issue 06 (2013-03-25)
NodeB V100R014
227
RAN14.0

Amplifier)
SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=TMA12DB_ONLY_NON_AISG,
PSP=R0A, PWRSW=ON;
SCN ALD: CN=0, SRN=60, ACN=R0A;
ADD ALD: NAME="test", CASE=REGULAR, DEVTP=STMA, CN=0, SRN=60,
ACN=R0A, SUBUNIT=1;
SET TMAGAIN: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A, GAIN=48;
SET RXATTEN: CN=0, SRN=60, SN=0, RXNO=0, ATTEN=0;
LST TMAGAIN: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A;
Issue 06 (2013-03-25)

228
RAN14.0
59
Configuring Remote Electrical Tilt
Remote Electrical Tilt. (This feature cannot be configured using the CME. )
Prerequisites
l
The base station is connected to a remote electrical tilt (RET) antenna properly.
The remote control unit (RCU) is compatible with the RET antenna. The RCU is loaded
with a configuration file designated for the RET antenna.
The RCU is loaded with the basic software.
This feature is supported by the all types of BTSs except for the BTS3600C and
BTS3002E.

License
Context
With this feature activated, users can remotely adjust the tilt of an RET antenna to optimize
network performance.
l
Calibrating the RET antenna may affect its coverage for a short period of time.
Calibrating an RET antenna takes up to 4 minutes.
NodeB V200R014
Procedure
1.
Issue 06 (2013-03-25)
Optional: If the antenna port is used, run the NodeB MML command MOD
ANTENNAPORT. In this step, set ALD Power Switch to ON.
229
RAN14.0
2.
Optional: If the RET antenna port is used, run the NodeB MML command MOD
RETPORT. In this step, set ALD Power Switch to ON.
3.
Run the NodeB MML command SCN ALD to obtain the ESN of an ALD.
4.
Run the NodeB MML command ADD RET to add an RET antenna.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
5.
Run the NodeB MML command CLB RET to calibrate the RET antenna.
6.
Optional: Run the NodeB MML command MOD RETSUBUNIT to modify

parameters concerning an RET antenna subunit.
7.
Optional: Run the NodeB MML command MOD RETDEVICEDATA to modify

parameters concerning the attributes of an RET device.
8.
Run the NodeB MML command MOD RETTILT to modify the tilt of the RET
antenna.
1.
Optional: If the antenna port is used, run the NodeB MML command DSP
ANTENNAPORT to query the power switch status for the port.
Expected result: ALD Actual Power Switch is ON.
2.
Optional: If the RET antenna port is used, run the NodeB MML command DSP
RETPORT to query the power switch status for the port.
Expected result:ALD Actual Power Switch is ON.
3.
Run the NodeB MML command DSP RET to query information about the RET
antenna.
4.
Run the NodeB MML command DSP RETSUBUNIT to query the dynamic
information on an RET antenna subunit and an RET antenna's tilt.
l
NodeB V100R014
1.
Run the NodeB MML command SET ALDPWRSW. In this step, set Power Supply
Switch to ON.
2.
Run the NodeB MML command SCN ALD to obtain the ESN of an ALD.
3.
Run the NodeB MML command ADD ALD to add an antenna device.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
4.
Run the NodeB MML command CLB ANT to calibrate the antenna device.
5.
Run the NodeB MML command SET ANTTILT to set the tilt of antenna device.
1.
Run the NodeB MML command DSP ANTCON to query the power switch status for
the antenna port.
Expected result: Power Supply Switch Run Status is ON.
2.
Issue 06 (2013-03-25)
Run the NodeB MML command DSP ANTTILT to query the tilt of the RET antenna.
230
RAN14.0
Expected result: Current Tilt (0.1 degree) is set to the specified value.
----End
Example
l
NodeB V200R014
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
SCN ALD:;
ADD RET: DEVICENO=0, DEVICENAME="RET1", CTRLCN=0, CTRLSRN=60,
CTRLSN=0, RETTYPE=SINGLE_RET, POLARTYPE=SINGLE, SCENARIO=REGULAR;
CLB RET: OPMODE=SUBUNIT, DEVICENO=0, SUBUNITNO=1;
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1;
MOD RETDEVICEDATA: DEVICENO=0, SUBUNITNO=1;
MOD RETTILT: RETCLASS=RET, OPMODE=DEVICENO, DEVICENO=0, TILT=45;
DSP ANTENNAPORT:;
DSP RET: DEVICENO=0;
DSP RETSUBUNIT: DEVICENO=0, SUBUNITNO=1;
NodeB V100R014
SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=RET_ONLY_COAXIAL,
PSP=R0A, PWRSW=ON;
SCN ALD:;
ADD ALD: NAME="test", CASE=REGULAR, DEVTP=SINGLE_RET, CN=0, SRN=60,
ACN=R0A;
CLB ANT: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A, DEVTP=SINGLE_RET;
SET ANTTILT: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A, DEVTP=SINGLE_RET,
TILT=20;
DSP ANTCON:;
DSP ANTTILT: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A;
Issue 06 (2013-03-25)

231
RAN14.0
60
Configuring Same Band Antenna

Sharing Unit (900 MHz)
Configuring Same Band Antenna Sharing Unit (900 MHz). (This feature cannot be configured
using the CME. )
Prerequisites
l

License
Context
l
The introduction of the feature enables UMTS900 and GSM900 to share the same antenna.
This feature helps to share an antenna in the same band and decreases the uplink division
loss. After SASU900 is applied, there is no uplink division loss, and the gain is expected
to be between 0 dB and 12 dB.
NodeB V200R014
Procedure
Issue 06 (2013-03-25)
1.
Run the NodeB MML command MOD ANTENNAPORT to set ALD Power
Switch to ON.
2.
Run the NodeB MML command SCN ALD to scan antenna devices and obtain the
serial number of the SASU.
3.
Run the NodeB MML command ADD SASU to configure the SASU and set the
antenna DC power switch state of the SASU.
4.
Run the NodeB MML command MOD SASUSUBUNIT to set the SASU working
mode and the gain of the SASU.
232
RAN14.0
1.
Run the NodeB MML command DSP SASU to query the antenna DC power switch
state of the SASU.
2.
Run the NodeB MML command DSP SASUSUBUNIT to query the SASU working
mode and the gain of the SASU.
NodeB V100R014
1.
Run the NodeB MML command SET ALDPWRSW to turn on the power supply
switch of the SASU (Same band Antenna Sharing Unit) port.
2.
Run the NodeB MML command SCN ALD to scan antenna devices and obtain the
serial number of the SASU.
3.
Run the NodeB MML command ADD ALD to configure the SASU.
4.
Run the NodeB MML command SET SASUMODE to set the SASU working mode.
5.
Run the NodeB MML command SET SASUGAIN to set the gain of the SASU.
6.
Run the NodeB MML command SET SASUDCSW to set the antenna DC power
switch state of the SASU.
7.
Run the NodeB MML command SET SASUDCLD to set the DC load of the SASU.
1.
Run the NodeB MML command LST ALD to query the configuration information
about the SASU.
2.
Run the NodeB MML command LST SASUMODE to query the SASU working
mode.
3.
Run the NodeB MML command LST SASUGAIN to query the gain of the SASU.
4.
Run the NodeB MML command LST SASUDCSW to query the antenna DC power
switch state of the SASU.
5.
Run the NodeB MML command LST SASUDCLD to query the DC load of the SASU.
----End
Example
l
NodeB V200R014
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON,
THRESHOLDTYPE=UER_SELF_DEFINE, UOTHD=1000, UCTHD=1050, OOTHD=1200,
OCTHD=1150;
SCN ALD: CTRLCN=0, CTRLSRN=60, CTRLSN=0;
ADD SASU: DEVICENO=0, DEVICENAME="0_0N0A0SASU_3G", CTRLCN=0,
CTRLSRN=60, CTRLSN=0, DCSWITCH=UMTS;
MOD SASUSUBUNIT: DEVICENO=0, SUBUNITNO=1, MODE=NORMAL, BSGAIN=12,
UMTSGAIN=12, DCLOAD=20;
DSP SASU: DEVICENO=0;
DSP SASUSUBUNIT: DEVICENO=0;
l
Issue 06 (2013-03-25)
NodeB V100R014
233
RAN14.0

SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=CUSTOM, PSP=R0A,
PWRSW=ON, UOTHD=1000, UCTHD=1050, OOTHD=1200, OCTHD=1150;
SCN ALD: CN=0, SRN=60, ACN=R0A;
ADD ALD: NAME="0_0N0A0SASU_3G", CASE=REGULAR, DEVTP=SASU, CN=0,
SRN=60, ACN=R0A;
SET SASUMODE: OPMODE=NAME, NAME="0_0N0A0SASU_3G", MODE=BYPASS;
SET SASUGAIN: OPMODE=NAME, NAME="0_0N0A0SASU_3G", CHTP=UMTS, GAIN=12;
SET SASUDCSW: OPMODE=NAME, NAME="0_0N0A0SASU_3G", DCSWITCH=UMTS;
SET SASUDCLD: OPMODE=NAME, NAME="0_0N0A0SASU_3G", DCLOAD=20;
LST ALD:;
LST SASUMODE: OPMODE=NAME, NAME="0_0N0A0SASU_3G";
LST SASUGAIN: OPMODE=NAME, NAME="0_0N0A0SASU_3G";
LST SASUDCSW: OPMODE=NAME, NAME="0_0N0A0SASU_3G";
LST SASUDCLD: OPMODE=NAME, NAME="0_0N0A0SASU_3G";
Issue 06 (2013-03-25)

234
RAN14.0
61
Configuring VoIP over HSPA/HSPA+
VoIP over HSPA/HSPA+.
Prerequisites
l
This feature depends on the UE capability and the IP multimedia subsystem (IMS).

In the case of VoIP over HSPA, the following features have been configured before this
feature is activated: WRFD-010610 HSDPA Introduction Package, WRFD-010612
HSUPA Introduction Package, WRFD-010636 SRB over HSUPA and WRFD-010652
SRB over HSDPA.
In the case of VoIP over HSPA+, the WRFD-010686 CPC-DTX/DRX feature has been
configured before this feature is activated.
License
Other Prerequisites
The UE should support VoIP.
CN should support IP multimedia subsystem (IMS).
Context
VoIP services can be carried on the DCH or HSPA. When VoIP services are carried on the DCH,
a large quantity of resources are consumed. When VoIP services are carried on the HSPA, the
system capacity significantly increases. When the Robust Header Compression (RoHC)
technique is used, the data transmission efficiency of VoIP services is greatly improved.
Issue 06 (2013-03-25)

235
RAN14.0
NOTE
l Data configurations on the BSC6900 and NodeB are required to activate the VoIP over HSPA/HSPA
+ feature.
l To increase the transmission efficiency of VoIP services, it is recommended that the WRFD-011501
PDCP Header Compression (RoHC) feature be activated.
l In the case of HSUPA, it is recommended that the non-scheduling transmission mode be used. In the
case of HSDPA, it is recommended that the Enhanced Proportional Fair (EPF) algorithm be activated.
The purpose is to reduce the delay of VoIP services.
Procedure
l
1.

VOIP channel type to HSPA(UL_EDCH,DL_HSDSCH) and IMS channel type
to HSPA(UL_EDCH,DL_HSDSCH).
2.

Parameters in Batches) to enable the RoHC algorithm. In this step, select the
CFG_PDCP_RFC3095_HC_SWITCH check box under the parameter Channel
Configuration Strategy Switch.
3.
Optional: If VoIP services need to use the WRFD-01061403 HSUPA 2ms TTI
feature, run the BSC6900 MML command SET UCORRMALGOSWITCH (CME
single configuration: UMTS Radio Global Configuration Express >
MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter Service
Mapping Strategy Switch. Go to Step 4.
4.
Optional:
a.
If the NodeB is configured with the WCDMA Baseband Process Unit REV:b
(WBBPb) and Enhanced Base Band Card (EBBC) boards, it is recommended
that 10 ms HSUPA TTI be set for VoIP services. Run the BSC6900 MML
command SET UFRC (CME single configuration: UMTS Radio Global
Configuration Express > Basic Resource Control Parameter
select the EDCH_TTI_10ms check box under the parameter HSUPA TTI type
of VOIP service.
b.
If the NodeB is configured with the WCDMA Baseband Process Unit REV:d
(WBBPd) and Enhanced Base Band Card REV:d (EBBCd) boards, either 10 ms
or 2 ms HSUPA TTI can be set for VoIP services.
a.
Issue 06 (2013-03-25)
To set 10 ms HSUPA TTI for HSUPA services, run the BSC6900 MML
Configuration > RNC Oriented FRC Algorithm Parameters; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches)

236
RAN14.0
to select the EDCH_TTI_10ms check box under the parameter HSUPA

TTI type of VOIP service.
b.
1)
Run the BSC6900 MML command SET UFRC (CME single

configuration: UMTS Radio Global Configuration Express > Basic
Resource Control Parameter Configuration > RNC Oriented FRC
Algorithm Parameters; CME batch modification center: 3.15
Modifying RNC Parameters in Batches). In this step, select the
EDCH_TTI_2ms check box under the parameter HSUPA TTI type
of VOIP service.
2)
Run the BSC6900 MML command SET

UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented
RRM Switch Configuration > Connection Oriented Algorithm
Switches; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to select the
DRA_VOICE_SAVE_CE_SWITCH check box under the
parameter Dynamic Resource Allocation Switch.
5.
Optional: To use the WRFD-01061404 HSUPA 2ms/10ms TTI HO feature, run the
BSC6900 MML command SET UCORRMALGOSWITCH (CME single
DRA_VOICE_TTI_RECFG_SWITCH check box under the parameter Dynamic
Resource Allocation Switch.
6.
To configure the EPF scheduling strategy, run the NodeB MML command SET
MACHSPARA (CME single configuration: NodeB Configuration Express >
IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: 3.17 Modifying
Physical NodeB Parameters in Batches) to set Scheduling Method to EPF
(Enhanced PF).
1.
Issue 06 (2013-03-25)
To set 2 ms HSUPA TTI for HSUPA services, do as follows:
In the Navigation Tree pane on the BSC6900 LMT, click the Trace tab. In the
displayed Trace Navigation Tree pane, double-click UMTS Services. On the
unfolded list, double-click Uu Interface Trace. In the displayed Uu Interface
Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG as shown in
Figure 61-1 to trace Uu interface signaling messages.

237
RAN14.0
2.
Analyze the traced messages.

If data shown in Figure 61-2 is traced on the Uu interface, the UE is in the
CELL_DCH state.
If data shown in Figure 61-3 is traced on the Uu interface, VoIP services are carried
on HSPA/HSPA+.
Figure 61-2 UE in CELL_DCH state
Issue 06 (2013-03-25)

238
RAN14.0
Figure 61-3 VoIP services carried on HSPA/HSPA+
3.
If VoIP services are carried on HSPA or HSPA+, trace the RRC_RB_SETUP or

RRC_RB_RECFG message on the Uu interface to check the type of carried TTI, as
shown in Figure 61-4.
Figure 61-4 Type of TTI carried in the message
NOTE
The services admitted before deactivation of this feature are not affected.
The services admitted after the deactivation will not use this feature.
1.

select the DCH(UL_DCH,DL_DCH) check box under the parameter VOIP channel
type, and select the DCH(UL_DCH,DL_DCH) check box under the parameter IMS
channel type.
----End
Example
//Activating VoIP over HSPA/HSPA+
//Configuring VoIP/IMS to be carried on the E-DCH in the uplink and HSDSCH in the downlink
SET UFRCCHLTYPEPARA: VoipChlType=HSPA, ImsChlType=HSPA;
Issue 06 (2013-03-25)

239
RAN14.0
//Enabling the RoHC algorithm

SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-1;
//Enabling the HSUPA 2 ms scheduling algorithm
SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1;
//Setting the HSUPA TTI type of the VoIP service to 10 ms TTI
SET UFRC: VoipHsupaTti=EDCH_TTI_10ms;
//Turning off the switch of saving CE resources
SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_SAVE_CE_SWITCH-1;
//Enabling dynamic adjustment of TTI reconfiguration for CS voice
services
SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_TTI_RECFG_SWITCH-1;
//Setting the EPF scheduling strategy on the NodeB side
SET MACHSPARA: SM=EPF;
/*Deactivating VoIP over HSPA/HSPA+*/
SET UFRCCHLTYPEPARA: VoipChlType=DCH, ImsChlType=DCH;
Issue 06 (2013-03-25)

240
RAN14.0
62
Configuring Optimized Scheduling for

VoIP over HSPA
WRFD-01061703 Optimized Scheduling for VoIP over HSPA.
Prerequisites
l

The following features have been configured before this feature is activated:
WRFD-010611 HSDPA Enhanced Package and WRFD-010612 HSUPA
Introduction Package have been configured before this feature is activated for VoIP
over HSPA.
WRFD-010611 HSDPA Enhanced Package and WRFD-010686 CPC- DTX/DRX
have been configured before this feature is activated for VoIP over HSPA+.
Other Prerequisites
The UE should support VoIP.
CN should support IP multimedia subsystem (IMS).
License
Context
RAN10.0 supports VoIP over HSPA. To ensure the QoS of VoIP carried over HSPA, the nonscheduling method is used for the HSUPA scheduling, and the delay-sensitive (DS) scheduling
algorithm is used for optimized HSDPA scheduling.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the NodeB MML command SET MACHSPARA (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm
241
RAN14.0
Parameters > MAC Parameters > MACHSPARA; CME batch modification center:
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set
Scheduling Method to EPF(Enhanced PF).
l
1.
Run the NodeB MML command LST MACHSPARA to query the configuration
result.
1.
Scheduling Method to MAXCI(Max C/I), RR(Round Robin), or PF(PF).
----End
Example
SET MACHSPARA: LOCELL=0, SM=EPF;
LST MACHSPARA: LOCELL=0;
SET MACHSPARA: LOCELL=0, SM=PF;
Issue 06 (2013-03-25)

242
RAN14.0
63
Configuring IMS Signaling over HSPA

IMS Signaling over HSPA.
Prerequisites
l

The configurations of the features on which this feature depends are complete. This
feature depends on the feature WRFD-010610 HSDPA Introduction Package and
WRFD-010612 HSUPA Introduction Package.
License
Other Prerequisites
CN should support the signaling indication at Iu interface.
Context
IP Multimedia Subsystem (IMS) signaling over HSPA can shorten the setup delay of IMS
services like VoIP to save network resources for the operator.
Procedure
l
1.
1.
Issue 06 (2013-03-25)

modification center: 3.15 Modifying RNC Parameters in Batches) to set IMS
channel type to HSPA(UL_EDCH,DL_HSDSCH).
243
RAN14.0

2.

If data shown in Figure 63-2 is traced on the Uu interface, the UE is in the
CELL_DCH state.
If data shown in Figure 63-3 is traced on the Uu interface, VoIP services are carried
on HSPA/HSPA+.
Issue 06 (2013-03-25)

244
RAN14.0
Figure 63-3 VoIP services carried on HSPA/HSPA+
3.
If VoIP services are carried on HSPA or HSPA+, trace the RRC_RB_SETUP or

1.

modification center: 3.15 Modifying RNC Parameters in Batches) to set IMS
channel type to DCH(UL_DCH,DL_DCH).
----End
Example
//Activating IMS Signaling over HSPA.
SET UFRCCHLTYPEPARA: ImsChlType=HSPA;
//Deactivating IMS Signaling over HSPA.
SET UFRCCHLTYPEPARA: ImsChlType=DCH;
Issue 06 (2013-03-25)

245
RAN14.0
64
Configuring PDCP Header Compression

(RoHC)
PDCP Header Compression (RoHC).
Prerequisites
l
The UE supports this feature.

WRFD-010619 CS Voice over HSPA/HSPA+
License
Other Prerequisites
The UE should support the ROHC compression function.
Context
PDCP header compression (RoHC) mainly applies to VoIP services to reduce IP overhead. This
feature provides an IP header compression mechanism, which aims to save the bandwidth over
the Uu interface, thereby reducing occupancy of radio resources.
Procedure
l
1.
Issue 06 (2013-03-25)

configuration strategy switch. Select the following parameters in the Compatibility
Switch list box:
246
RAN14.0
CMP_RAB_5_CFG_ROHC_SWITCH
l
1.
On the BSC6900 LMT, click Trace > UMTS Service, and double-click Uu Interface
Trace to display the Uu Interface Trace window.
2.
Set Cell config, Uu Message Type, and Save File, and then click Submit.
3.
Enable the UE to establish VoIP services.
4.
Check the rb-InformationSetupList message in the traced data:

If this message contains the IE headerCompressionInfoList, as shown in Figure
64-1, this feature has been activated.
If this message does not contain the IE headerCompressionInfoList, this feature
has not been activated.
Figure 64-1
1.

Parameters in Batches). In this step, deselect the
configuration strategy switch. Disable the following switches in the Compatibility
Switch list box:
Issue 06 (2013-03-25)

247
RAN14.0
----End
Example
//Activating PDCP Header Compression (RoHC)
SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-1,
CmpSwitch=CMP_RAB_5_CFG_ROHC_SWITCH-1&CMP_RAB_6_CFG_ROHC_SWITCH-1&CMP_RAB
_7_CFG_ROHC_SWITCH-1&CMP_RAB_8_CFG_ROHC_SWITCH-1&CMP_RAB_9_CFG_ROHC_SWITC
H-1;
//Deactivating PDCP Header Compression (RoHC)
SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-0,
CmpSwitch=CMP_RAB_5_CFG_ROHC_SWITCH-0&CMP_RAB_6_CFG_ROHC_SWITCH-0&CMP_RAB
_7_CFG_ROHC_SWITCH-0&CMP_RAB_8_CFG_ROHC_SWITCH-0&CMP_RAB_9_CFG_ROHC_SWITC
H-0;
Issue 06 (2013-03-25)

248
RAN14.0
65
Configuring CS Voice over HSPA/HSPA

+
CS Voice over HSPA/HSPA+.
Prerequisites
l

WRFD-010610 HSDPA Introduction Package, WRFD-010612 HSUPA
Introduction Package, WRFD-010652 SRB over HSDPA, and WRFD-010636 SRB
over HSUPA, in the case of CS voice over HSPA.
WRFD-010686 CPC-DTX/DRX, in the case of CS voice over HSPA+.
License
Other Prerequisites
The UE is of 3GPP Release 8 or higher and CS voice services are capable of being
carried on HSPA/HSPA+.
Context
The implementation of CS voice services over HSPA is introduced in 3GPP Release 8. In the
case of CS voice services over HSPA, uplink CS voice packets are carried on the E-DCH and
downlink CS voice packets are carried on the HS-DSCH.
CS Voice over HSPA is intended for CS conversational AMR and AMR WB. CS streaming
services are still carried on the DCH. The IMS for VoIP services is not required because the CS
voice services over HSPA are carried on the CS domain of the CN.
Issue 06 (2013-03-25)

249
RAN14.0
NOTE
l Data configurations on the BSC6900 and NodeB are required to activate the CS Voice over HSPA/
HSPA+.
l In the case of HSUPA, it is recommended that the non-scheduling transmission mode be used, which
does not need to be configured. In the case of HSDPA, it is recommended that the Enhanced
Proportional Fair (EPF) algorithm be activated. The purpose is to reduce the delay of CS voice services.
Procedure
l
1.

modification center: 3.15 Modifying RNC Parameters in Batches) to configure the
uplink EDCH and downlink HSDSCH as the channels carrying HSPA CS services.
In this step, select the HSPA(UL EDCH,DL HSDSCH) check box under the
parameter CS voice channel type.
2.
Optional: If CS voice services need to be carried on the 2 ms Transmission Time

Interval (TTI), run the BSC6900 MML command SET
Mapping Strategy Switch. Go to Step 3.
3.
Optional: Configure the HSUPA TTI type of the VoIP service.

a.
If the NodeB is configured with the WCDMA Baseband Process Unit REV:b
(WBBPb) and Enhanced Base Band Card (EBBC) boards, it is recommended
that 10 ms HSUPA TTI be set for VoIP services. Run the BSC6900 MML
select the EDCH_TTI_10ms check box under the parameter HSUPA TTI type
of VOIP service.
b.
If the NodeB is configured with the WCDMA Baseband Process Unit REV:d
(WBBPd) and Enhanced Base Band Card REV:d (EBBCd) boards, either 10 ms
or 2 ms HSUPA TTI can be set for VoIP services.
a.
To set 10 ms HSUPA TTI for HSUPA services, run the BSC6900 MML
Configuration > RNC Oriented FRC Algorithm Parameters; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches)
to select the EDCH_TTI_10ms check box under the parameter HSUPA
TTI type of VOIP service.
b.
To set 2 ms HSUPA TTI for HSUPA services, do as follows:

1)
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UFRC (CME single

configuration: UMTS Radio Global Configuration Express > Basic
Resource Control Parameter Configuration > RNC Oriented FRC
Algorithm Parameters; CME batch modification center: 3.15

250
RAN14.0

EDCH_TTI_2ms check box under the parameter HSUPA TTI type
of VOIP service.
2)
4.
Optional: If the dynamic adjustment of CS voice services over HSUPA from 2 ms

TTI to 10 ms TTI is required, run the BSC6900 MML command SET
DRA_VOICE_TTI_RECFG_SWITCH check box under the parameter Dynamic
5.
To configure the EPF scheduling strategy, run the NodeB MML command SET
MACHSPARA (CME single configuration: NodeB Configuration Express >
IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: 3.17 Modifying
Physical NodeB Parameters in Batches) to set Scheduling Method to EPF
(Enhanced PF).
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET

UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented
RRM Switch Configuration > Connection Oriented Algorithm
Switches; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to select the
DRA_VOICE_SAVE_CE_SWITCH check box under the

251
RAN14.0
2.

If data shown in Figure 65-2 is traced on the Uu interface, the UE is in CELL_DCH
state.
If the data traced on the Uu interface is displayed, as shown in Figure 65-3, CS
voice services are carried on HSPA/HSPA+.
Figure 65-3 CS voice services carried on HSPA/HSPA+
3.
Issue 06 (2013-03-25)
If CS voice services are carried on HSPA or HSPA+, trace the RRC_RB_SETUP or


252
RAN14.0
NOTE
The services admitted before deactivation of this feature are not affected.
The services admitted after the deactivation will not use this feature.
1.

select the DCH(UL_DCH,DL_DCH) check box under the parameter CS voice
channel type.
----End
Example
/*Activation procedure*/
//Configuring CS voice services to be carried on the EDCH in the uplink
and HS-DSCH in the downlink
SET UFRCCHLTYPEPARA: CSVoiceChlType =HSPA;
//Enabling the HSUPA 2 ms scheduling algorithm
SET UFRC: CSVoiceHsupaTti=EDCH_TTI_2ms;
//Turning off the switch of saving CE resources
SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_SAVE_CE_SWITCH-1;
//Enabling dynamic adjustment of TTI reconfiguration for CS voice
services
SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_TTI_RECFG_SWITCH-1;
//Setting the EPF scheduling strategy on the NodeB side
/*Deactivating CS Voice over HSPA/HSPA+*/
SET UFRCCHLTYPEPARA: CSVoiceChlType=DCH;
Issue 06 (2013-03-25)

253
RAN14.0
66
Configuring AMR-WB (Adaptive Multi

Rate Wide Band)
AMR-WB (Adaptive Multi Rate Wide Band). (This feature cannot be configured using the
CME. )
Prerequisites
l
The CN supports associated specifications.

License
Other Prerequisites
The UE supports associated specifications.
The AMR-WB function is enabled on the MSC and UMG.
The UE must have the corresponding support capability.
The CN must have the corresponding support capability.
Context
This feature provides AMR-WB services, which help improve the QoS of voice services when
resources are sufficient.
Issue 06 (2013-03-25)

254
RAN14.0
CAUTION
l If the license of the AMR-WB service is not activated on a RNC, ensure that AMR-WB is
not enabled for this RNC on the CS core network side. Otherwise, both the AMR-NB services
and emergency calls cannot be set up for the UE supporting AMR-WB.
l If the license of the AMR-WB service is enabled on a RNC, ensure that AMR-WB is enabled
for this RNC on the CS core network side. Otherwise, the AMR-WB service cannot be set
up.
l This feature is an integrated solution. To enable this feature, specific parameters must be
configured based on the actual network conditions. Contact Huawei for technical support.
l Do not configure relevant parameters without the assistance of Huawei technical personnel;
otherwise, the network capacity and KPI values may be affected.
Procedure
l
1.
Optional: Run the BSC6900 MML command SET UAMRCWB to set the RNClevel speech rates for the gold, silver, and bronze users.
2.
Optional: Run the BSC6900 MML command ADD UCELLAMRCWB to set celllevel speech rates for the gold, silver, and bronze users.
1.
Optional: Run the BSC6900 MML command LST UAMRCWB to query the AMRWB speech rates of the gold, silver, and bronze users.
2.
Optional: Run the BSC6900 MML command LST UCELLAMRCWB to query the
AMR-WB speech rates for the gold, silver, and bronze users.
3.
On the BSC6900 LMT, open the Monitor tab page, choose Monitor > Monitor >
UMTS Monitoring > Cell Performance Monitoring, and create a task of AMR
Mode.
4.
Enable the AMR-WB function on UE1 and UE2, and enable the UEs to camp on the
cell CELL_A11.
5.
Use UE1 to initiate a voice call to UE2. The call is successfully established and the
voice is clear.
6.
Check the AMR mode on the LMT and verify that the downlink rate of UE1 reaches
the specified value.
Run the BSC6900 MML command SET LICENSE to deactivate the license controlling
this feature.
NOTE
After deactivating the license controlling this feature, a WB-AMR cannot establish WB and NB
services. If the WB rate for the RNC is disabled, a WB-AMR UE still can establish NB services.
----End
Example
//Activating AMR-WB
//Setting RNC-level parameters for the WB-AMR speech rate control (WBAMRC) algorithm
Issue 06 (2013-03-25)

255
RAN14.0
SET UAMRCWB: GoldMaxMode=WBAMR_BITRATE_12.65K,

SilverMaxMode=WBAMR_BITRATE_12.65K, CopperMaxMode=WBAMR_BITRATE_12.65K;
//Setting cell-level parameters for the WB-AMRC algorithm
ADD UCELLAMRCWB: CellId=111, GoldMaxMode=WBAMR_BITRATE_12.65K,
//Deactivating AMR-WB
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH2=WBAMR-0;
Issue 06 (2013-03-25)

256
RAN14.0
67
Configuring AMR/WB-AMR Speech

Rates Control
AMR/WB-AMR Speech Rates Control.
Prerequisites
l

If this feature is to be applied to Adaptive Multi Rate Wide Band (AMR WB), this
feature depends on WRFD-010613 AMR-WB.
License
Other Prerequisites
The UE supports TFC control processing.
Context
This feature enables the adjustment of AMR/AMR-WB speech rates triggered by multiple
factors. This ensures uninterrupted services, expands the service coverage area, and reduces the
cell load.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, set CS Algorithm Switch to
CS_AMRC_SWITCH.
2.
Run the BSC6900 MML command SET UQOSACT (CME single configuration:
UMTS Radio Global Configuration Express > QOS Parameter Configuration >
257
RAN14.0
RNC-Oriented QoS Enhancement Algorithm Parameters; CME batch

modification center: 3.15 Modifying RNC Parameters in Batches) to turn on the
QoS switches for AMR services.
3.
Optional: Run the BSC6900 MML command SET UQUALITYMEAS (CME single
configuration: UMTS Radio Global Configuration Express > QOS Parameter
Configuration > RNC-Oriented QoS quality measurement parameters; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) or MOD
UTYPRABQUALITYMEAS (CME single configuration: UMTS Radio Global
Configuration Express > Typical Service Configuration > QoS link Stability
Control Parameters; CME batch modification center: not supported) to set the
parameters for RNC-level AMR and AMR-WB speech rate control based on link
stability.
4.
Optional: Set the parameters for AMR and AMR-WB speech rate control.
Set the AMR speech rate control parameters.
a.
Run the BSC6900 MML command SET UCORRMPARA (CME single

Connection_Oriented RRM Switch Configuration > the connectionoriented algorithm parameters of an RNC; CME batch modification
the RESERVED_SWITCH_0_BIT4 check box under parameter CORRM
Algorithm Reserved Switch 0 to enable NB-AMRC.
NOTE
Select the RESERVED_SWITCH_0_BIT4 check box to disable NB-AMRC when

there are some NB-AMRC compatibility problems.
b.
Run the BSC6900 MML command SET UAMRC (CME single

configuration: UMTS Radio Global Configuration Express > AMRC
Parameter Configuration > RNC Oriented AMRC Algorithm
Parameters; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) to set the RNC-level AMR speech rate control
parameters.
Set the AMR-WB speech rate control parameters.

a.
Run the BSC6900 MML command SET UCORRMPARA (CME single

Connection_Oriented RRM Switch Configuration > the connectionoriented algorithm parameters of an RNC; CME batch modification
the RESERVED_SWITCH_0_BIT3 check box under parameter CORRM
Algorithm Reserved Switch 0 to enable WB-AMRC.
NOTE
Select the RESERVED_SWITCH_0_BIT3 check box to disable WB-AMRC when

there are some WB-AMRC compatibility problems.
b.
l
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UAMRCWB (CME single

configuration: UMTS Radio Global Configuration Express > AMRC
Parameter Configuration > RNC-Oriented Wideband AMRC
Algorithm Parameters; CME batch modification center: 3.15 Modifying
RNC Parameters in Batches) to set the RNC-level AMR-WB speech rate
control parameters.
258
RAN14.0
1.
On the BSC6900 LMT, open the Monitor tab page. In the Monitor tab page, doubleclick UMTS Monitoring > Connection Performance Monitoring. In the displayed
dialog box, set Monitor Item to AMR Mode and specify IMSI.
2.
On the BSC6900 LMT, open the Trace tab page. In the Trace tab page, double-click
UMTS Services > Uu Interface Trace. In the displayed dialog box, specify the RNC
ID and the Cell ID, as shown in Figure 67-1.
Figure 67-1 Uu interface tracing
3.
Two test UEs supporting AMR WB are available and camp on the cell named
CELL_A11. Use UE A to call UE B. The call is established.
4.
Check whether the following information elements (IEs) are contained in the traced
RRC_MEAS_CTR message, as shown in Figure 67-2.
event6a
event6b
Issue 06 (2013-03-25)

259
RAN14.0
Figure 67-2 IEs contained in RRC_MEAS_CTRL
5.
Place UE B in the center of the cell, and move UE A towards or away from UE B.
Check whether the AMR mode changes during performance monitoring, as shown in
Figure 67-3.
Figure 67-3 AMR mode
1.
Issue 06 (2013-03-25)


260
RAN14.0
Parameters in Batches). In this step, set CS Algorithm Switch to

CS_AMRC_SWITCH.
----End
Example
//Activating AMR/WB-AMR Speech Rates Control
SET UCORRMALGOSWITCH: CsSwitch=CS_AMRC_SWITCH-1;
SET UQOSACT: AMRQosPerform=YES, UlQosAmrAdjSwitch=YES,
UlQosWAmrAdjSwitch=YES, DlQosAmrAdjSwitch=YES, DlQosWAmrAdjSwitch=YES;
MOD UTYPRABQUALITYMEAS: RabIndex=1, UlThd6a1=1, UlThd6a2=5, UlThd6b1=1,
UlThd6b2=5, StaBlkNum5A=500, Thd5a=280, HangBlockNum5a=512, ThdEa=2,
ThdEb=2;
//Setting the AMR speech rate control parameters
SET UCORRMPARA: ReservedSwitch0=RESERVED_SWITCH_0_BIT4-0;
SET UAMRC: GoldMaxMode=NBAMR_BITRATE_6.70K,
SilverMaxMode=NBAMR_BITRATE_6.70K, CopperMaxMode=NBAMR_BITRATE_6.70K;
//Setting the AMR-WB speech rate control parameters
SET UCORRMPARA: ReservedSwitch0=RESERVED_SWITCH_0_BIT3-0;
SET UAMRCWB: GoldMaxMode=WBAMR_BITRATE_12.65K,
//Deactivating AMR/WB-AMR Speech Rates Control
SET UCORRMALGOSWITCH: CsSwitch=CS_AMRC_SWITCH-0;
Issue 06 (2013-03-25)

261
RAN14.0
68
Configuring TFO/TrFO
TFO/TrFO.
Prerequisites
l

License
Other Prerequisites
The CN node supports this feature.
Context
This feature helps implement the functions of TFO/TrFO by identifying the Iu user plane (IuUP)
V2 core network (CN) and processing related services.
This feature can prevent speech quality deterioration caused by the interpretation between
different coder and decoders (CODECs). The TrFO can also save the transmission resources.
If the TFO function is enabled on the GSM side, the AMRC rate adjustment function must
enabled together with this feature on the UMTS side to enable communications between GSM
and UMTS users to support the TFO function. To fully utilize this function, it is good practice
to enable the AMRC rate adjustment function on both UMTS users in a conversation.
Procedure
l
1.
Issue 06 (2013-03-25)

262
RAN14.0

Parameters in Batches) to turn on the IuUP V2 switch to support TFO/TrFO. Select
CS_IUUP_V2_SUPPORT_SWITCH from the CS Algorithm Switch drop-down
list.
l
1.
Start Uu interface tracing on the BSC6900 LMT.
2.
Enable UE1 to call UE2. UE2 answers and starts a conversation with UE1. When UE1
moves to the cell edge, you can view the RRC TFC CTRL message indicating rate
reduction sent from RNC to UE1 over the Uu interface. This indicates that this feature
is activated.
1.

Parameters in Batches) to turn off the IuUP switch. Deselect
CS_IUUP_V2_SUPPORT_SWITCH from the CS Algorithm Switch drop-down
list.
----End
Example
SET UCORRMALGOSWITCH: CsSwitch=CS_IUUP_V2_SUPPORT_SWITCH-1;
SET UCORRMALGOSWITCH: CsSwitch=CS_IUUP_V2_SUPPORT_SWITCH-0;
Issue 06 (2013-03-25)

263
RAN14.0
69 Configuring AMR Voice Quality Improvement Based on

PLVA
69
Configuring AMR Voice Quality

Improvement Based on PLVA
AMR Voice Quality Improvement Based on PLVA.
Prerequisites
l
This feature has the following impact on the NodeB hardware:
The BTS3812E, BTS3812A and BTS3812AE must be configured with the EULPd
board.
The DBS3800 must be configured with the EBBCd board.
The 3900 series base station must be configured with the WBBPd or WBBPf board.
Currently, for baseband boards, only the EULPd, EBBCd, WBBPd and WBBPf
boards support the PLVA feature. When the EULPd, EBBCd, WBBPd or WBBPf
board is inserted together with the other types of baseband boards, AMR services
cannot obtain the PLVA gain if the AMR services are set up on the other types of
baseband boards.

None
License
Procedure
l
After the license is activated, this feature has been activated.
The VS.PLVA.User counter informs operators of the number of UEs using this feature.
Verify that the value of the counter VS.PLVA.User is not 0. A non-zero value indicates
that this feature takes effect.
Issue 06 (2013-03-25)

264
RAN14.0
69 Configuring AMR Voice Quality Improvement Based on

PLVA
None
----End
Example
None
Issue 06 (2013-03-25)

265
RAN14.0
70
Configuring Cell Broadcast Service
Prerequisites
l

License
Others
The UE is capable of receiving cell broadcast messages.
Context
This feature supports the standard cell broadcast procedure specified in the related protocol and
therefore helps the cell broadcast center (CBC) implement cell broadcast services.
Procedure
l
External CBCs are deployed in an ATM or IP network. The ATM network is used as an
example in this document.
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command RMV URNCCBCPUID (CME single

configuration: IUBC Configuration Express > ATM Transport > RNC Broadcast
Message Main CPUID; CME batch modification center: not supported) to disable
the configuration of the built-in CBC.
2.
Run the BSC6900 MML command SET URNCCBPARA (CME single

configuration: UMTS Radio Global Configuration Express > Iu-BC Interface
Configuration > RNC Cell Broadcast Message Para; CME batch modification
center: 3.15 Modifying RNC Parameters in Batches) to turn off CB Switch.
266
RAN14.0
3.
Run the BSC6900 MML command ADD DEVIP (CME single configuration: IUBC
Configuration Express > ATM Transport > Device IP Address; CME batch
modification center: not supported) to add the device IP address of the interface board.
4.
Run the BSC6900 MML command ADD IPOAPVC (CME single configuration:
IUBC Configuration Express > ATM Transport > IPoA PVC; CME batch
modification center: not supported) to add an Internet Protocol over ATM (IPoA)
permanent virtual circuit (PVC).
NOTE
The IP address is the device IP address (DEVIP) of the interface board.

The peer IP address is the IP address for interconnection between serving GPRS support node
(SGSN) and RNC.
The VPI and VCI must be the same as those configured on the SGSN. To query the specific
settings, run the LST IPOA command on the SGSN maintenance terminal.
5.
Run the BSC6900 MML command ADD IPRT (CME single configuration: IUBC
Configuration Express > ATM Transport > IP Route; CME batch modification
center: not supported) to add a route from the interface board to the CBC. The route
passes the IP address of the SGSN.
6.
Run the BSC6900 MML command ADD UCBSADDR (CME single configuration:
IUBC Configuration Express > ATM Transport > CBS Address; CME batch
modification center: not supported) to add the CBS socket IP address.
7.
Run the BSC6900 MML command ADD UCTCH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > CTCH; CME
batch modification center: not supported) to add the common traffic channel (CTCH)
to a cell.
NOTE
To set up a CTCH on FACH5, run the following commands:

DEA
ADD
ADD
ACT
USCCPCH: CellId=0, PhyChId=8;

UFACHLOCH: CellId=0, TrChId=5;
USCCPCHTFC: CellId=0, PhyChId=8, CTFC=7;
USCCPCH: CellId=0, PhyChId=8;
8.
Run the BSC6900 MML command ADD UCELLCBSDRX (CME single

configuration: UMTS Cell Configuration Express > Cell Broadcast Service > Cell
CBS DRX Parameters; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches) to add the CBS discontinuous reception (DRX)
scheduling parameter.
9.
Run the BSC6900 MML command ADD UCELLCBSSAC (CME single

CBS SAC; CME batch modification center: 3.18 Modifying UMTS Cell Parameters
in Batches) to add a CBS area.
10. Run the BSC6900 MML command ACT UCELLCBS (CME single configuration:
UMTS Cell Configuration Express > Cell Broadcast Service > Cell CBS. Set Cell
CBS state to Activated; CME batch modification center: not supported) to enable the
CBS function of the cell.
l
1.
Issue 06 (2013-03-25)
Check whether the CBS function works properly.

a.
Ping the CBS IP address of the RNC on the CBC. If the ping operation is
successful, it indicates that the data transmission from CBC to RNC is normal.
b.
Ping the CBC IP address on the RNC. The source IP address is the device IP
address, that is, the IP address of the CBS. PING IP: SRN=0, SN=16,
267
RAN14.0
SIPADDR="12.12.12.12", DESTIP="11.11.11.11"; If the ping operation is

successful, it indicates that the data transmission from RNC to CBC is normal.
If the ping operation fails, check the configuration.
c.
Check whether the CBS socket is connected properly. To do this, trace messages
over the Iu interface and view whether the SABP_LOAD_QUERY is sent to
the RNC, as shown in Figure 70-1.
Figure 70-1 Viewing the SABP_LOAD_QUERY message
d.
Issue 06 (2013-03-25)
As shown in Figure 70-2, the 0SABP_LOAD_QUERY_CMP message

returned from the RNC contains the information element (IE) availablebandwidth.

268
RAN14.0
Figure 70-2 Viewing the SABP_LOAD_QUERY_CMP message
e.
Run the BSC6900 MML command DSP UCELL to check whether the CBS
function works, as shown in Figure 70-3.
Figure 70-3 Viewing the CBS function
2.
Issue 06 (2013-03-25)
Check the broadcast messages sent.

a.
Use the MTC tool to send messages on the CBC. It is recommended that the time
interval for sending messages be within 10s and the number of messages sent be
more than two (0 indicates infinity).
b.
Trace messages on the Iu interface to check whether the

SABP_WRITE_REPLACE message is sent to the RNC, as shown in Figure
70-4.

269
RAN14.0
Figure 70-4 Viewing the SABP_WRITE_REPLACE message
c.
Issue 06 (2013-03-25)
As shown in Figure 70-5, the SABP_WRITE_REPLACE_CMP message

returned from the RNC contains a broadcast message with the IE number-ofbroadcasts-completed.

270
RAN14.0
Figure 70-5 Viewing the SABP_WRITE_REPLACE_CMP message
d.
Issue 06 (2013-03-25)
Trace messages on the Uu interface to check whether the

UU_BMC_MSG_TYPE message beginning with 01 is sent from the RNC, as

271
RAN14.0
Figure 70-6 Viewing the UU_BMC_MSG_TYPE message
3.
Issue 06 (2013-03-25)
Stop the RNC from sending broadcast messages.

a.
On the CBC, select the message being sent and click delete.
b.
Trace messages on the Iu interface to check whether the SABP_KILL message

is sent to the RNC, as shown in Figure 70-7.

272
RAN14.0
Figure 70-7 Viewing the SAB_KILL message
c.
Issue 06 (2013-03-25)
Trace messages on the Iu interface, as shown in Figure 70-8. The

SABP_KILL_CMP message returned from the RNC contains the IE numberof-broadcast-completed.

273
RAN14.0
Figure 70-8 Viewing the SABP_KILL_CMP message
d.
l
It can be viewed from the Uu interface trace data that the RNC stops sending the
UU_BMC_MSG_TYPE message beginning with 01.
1.
Run the BSC6900 MML command RMV UCBSADDR (CME single configuration:
IUBC Configuration Express > ATM Transport > CBS Address; CME batch
modification center: not supported) to disable Cell Broadcast Service.
----End
Example
//Activating Cell Broadcast Service
//Configuring the license controlling Cell Broadcast Service
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=1,
FUNCTIONSWITCH1=CBS-1;
Issue 06 (2013-03-25)

274
RAN14.0
//Removing the configuration of the built-in CBC

RMV URNCCBCPUID: CnOpIndex=1;
//Disabling the inner CBS function for the RNC
SET URNCCBPARA: CBSwitch=OFF;
//Configuring the device IP address of the interface board
ADD DEVIP: SRN=5, SN=18, DEVTYPE=IPOA_CLIENT_IP, IPADDR="12.12.12.12",
MASK="255.255.255.0";
//Configuring the IPoA PVC
ADD IPOAPVC: IPADDR="12.12.12.12", PEERIPADDR="12.12.12.120",
CARRYT=NCOPT, CARRYNCOPTN=0, CARRYVPI=255, CARRYVCI=32, TXTRFX=103,
RXTRFX=103, PEERT=OTHER;
//Configuring a route from the interface board to CBC
ADD IPRT: SRN=5, SN=18, DSTIP="11.11.11.12", DSTMASK="255.255.255.255",
NEXTHOP="12.12.12.120", PRIORITY=HIGH, REMARK="SGSN_CBS";
//Configuring the CBS socket IP address
ADD UCBSADDR: SRN=5, SN=2, CnOpIndex=1, RNCIPADDR="12.12.12.12",
CBCIPADDR="11.11.11.11", CBCMASK="255.255.255.0";
//Configuring the CTCH for a cell
ADD UCTCH: CellId=0, FachId=4;
//Configuring the CBS DRX scheduling parameter
ADD UCELLCBSDRX: CellId=0;
//Configuring a CBS area
ADD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=OFF;
//Enabling the cell-level CBS
ACT UCELLCBS: CellId=0;
//Deactivating Cell Broadcast Service

//Removing the CBS socket IP address
RMV UCBSADDR: CnOpIndex=1;
Issue 06 (2013-03-25)

275
RAN14.0
71
Configuring Simplified Cell Broadcast
Simplified Cell Broadcast.
Prerequisites
l
OnlyBSC6900 supports this feature.

This feature and the feature WRFD-011000 Cell Broadcast Service cannot be used
together.
License
Others
The UE is capable of receiving cell broadcast messages.
Context
This feature is used to send simple cell broadcast messages by running a BSC6900 MML
command on the M2000 or BSC6900 LMT when the cell broadcast center (CBC) is not
configured.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command RMV UCBSADDR (CME single configuration:
IUBC Configuration Express > IP Transport > CBS Address; CME batch
modification center: not supported) to remove the IP address of the external CBC.
2.
Run the BSC6900 MML command ADD URNCCBCPUID (CME single

configuration: IUBC Configuration Express > IP Transport > RNC Broadcast
Message Main CPUID; CME batch modification center: not supported) to configure
the SPU subsystem of the built-in CBC.
3.

276
RAN14.0
center: 3.15 Modifying RNC Parameters in Batches). In this step, set CB Switch
to ON(ON) to enable the built-in CBC for the RNC.
4.
Run the BSC6900 MML command ADD UCTCH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > CTCH; CME
batch modification center: not supported) to add the common traffic channel (CTCH)
to a cell.
5.
Run the BSC6900 MML command ADD UCELLCBSDRX (CME single

CBS DRX Parameters; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches) to add the CBS discontinuous reception (DRX)
scheduling parameter.
6.
Run the BSC6900 MML command ADD UCELLCBSSAC (CME single

CBS SAC; CME batch modification center: 3.18 Modifying UMTS Cell Parameters
in Batches) to add a CBS area and a broadcast message.
7.
Run the BSC6900 MML command ACT UCELLCBS (CME single configuration:
CBS state to Activated; CME batch modification center: not supported) to enable the
CBS function for a cell.
1.
Check whether the CBS function works properly.

After activating the CBS function on the RNC, if the UU_BMC_MSG_TYPE
message beginning with 01 is traced on the Uu interface, as shown in Figure 71-1,
the CBS function works properly.
Figure 71-1 UU_BMC_MSG_TYPE message
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command DEA UCELLCBS (CME single configuration:
CBS state to Deactivated; CME batch modification center: not supported) to disable
the CBS function for a cell.
2.

277
RAN14.0
center: 3.15 Modifying RNC Parameters in Batches). In this step, set CB Switch
to OFF(OFF) to turn off the CBS switch for the BSC6900.
----End
Example
//Activating Simplified Cell Broadcast
//Enabling the license controlling Simplified Cell Broadcast
FUNCTIONSWITCH4=SIMPLE_CELL_BORADCAST-1;
//Removing the IP address of an external CBS
//Configuring the SPU subsystem of the built-in CBC
ADD URNCCBCPUID: CnOpIndex=1, SRN=0, SN=2, SSN=1;
//Enabling the built-in CBC for the RNC
SET URNCCBPARA: CBSwitch=ON, RepeatPeriod=10, RepeatNum=0;
//Configuring the CTCH for a cell
ADD UCTCH: CellId=0, FachId=4;
//Configuring the CBS DRX scheduling parameter
ADD UCELLCBSDRX: CellId=0;
//Configuring a CBS area and a broadcast message
ADD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=ON,
MsgContent="welcome! it is cell 0";
//Enabling the CBS function for a cell
//Verifying Simplified Cell Broadcast

//Modifying the CBS configuration for a cell
MOD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=ON,
MsgContent="HELLO,SIMPLE CBS";
//Activating the CBS function for a cell
//Deactivating Simplified Cell Broadcast

//Disabling the CBS function for a cell
DEA UCELLCBS: CellId=0;
//Disabling the CBS function for the BSC6900
SET URNCCBPARA: CBSwitch=OFF;
Issue 06 (2013-03-25)

278
RAN14.0
72
Configuring Warning of Disaster
Warning of Disaster.
Prerequisites
l

feature depends on the feature WRFD-011001 Simplified Cell Broadcast.
License
Context
With this feature, the Cell Broadcast Center (CBC) incorporated into the RNC informs all users
in specified cells of the disaster information through message broadcasting in the shortest time,
therefore minimizing the impact of the disaster.
NOTE
Activating this feature requires operations on only the RNC.
Procedure
l
Issue 06 (2013-03-25)
1.
For detailed operations for activating license, see Activating the BSC6900 License.
2.
(Optional) Run the BSC6900 MML command RMV UCBSADDR (CME single
configuration: IUBC Configuration Express > IP Transport > CBS Address; CME
batch modification center: not supported) to remove the CBS configuration, if the
operator configured the CBS function using external CBC.
3.

center: 3.15 Modifying RNC Parameters in Batches) to set CB switch and CTCH
279
RAN14.0
switch of cell broadcast to ON. By doing this, the system can configure the disaster
warning message and send the message to UEs.
4.
Run the BSC6900 MML command ADD URNCCBCPUID (CME single

configuration: IUBC Configuration Express > IP Transport > RNC Broadcast
Message Main CPUID; CME batch modification center: not supported) to configure
the SPU subsystem for the built-in CBC.
5.
Run the BSC6900 MML command ADD UCBSAREA (CME single configuration:
UMTS Global Configuration Express > Radio Basic Data Configuration >
Simple Cell Broadcast Area; CME batch modification center: not supported) to
configure the broadcast area. The broadcast area can be a LAC, a cell, or all cells under
the RNC.
6.
Run the BSC6900 MML command ADD UCBSMSG (CME single configuration:
Simplified CBS Message; CME batch modification center: not supported) or MOD
UCBSMSG (CME single configuration: UMTS Global Configuration Express >
Radio Basic Data Configuration > Simplified CBS Message; CME batch
modification center: not supported) to configure the broadcast message.
NOTE
l When disasters (such as earthquakes, tsunamis, and hurricanes) occur, Set Geography
Scope to CellImmediate, and set CBS Message Priority to High so that users can receive
the message in time.
l It is recommended to set Number of CBS Messages to a value greater than 3 to ensure
that all UEs can receive the message.
1.
Use a test UE to camp on the cell, and then activate the feature. Check whether the
test UE can receive the disaster warning message.
NOTE
A UE can receive this message only after it is enabled with the 3G broadcast message receiving
function.
1.

center: 3.15 Modifying RNC Parameters in Batches) to set CTCH switch of cell
broadcast to OFF.
----End
Example
//Activating warning of disaster (The following procedure uses a cell as
an example.)
SET URNCCBPARA: CBSwitch=ON, CTCHSwitch =ON;
ADD URNCCBCPUID: CnOpIndex=1, SRN=0, SN=2, SSN=1;
ADD UCBSAREA: AreaId=1, CnOpIndex=1, AreaType=CELL, CellId=22;
ADD UCBSMSG: MsgIndex=0, MsgTypeId=1, GeographicalScope=CellImmediate,
Priority=High, RepetPeriod=10, NumOfBrdcstReq=5, CodeType=English,
AreaID=1, EmergencyType=Other, CBSMsg="Hurricane";
//Deactivating warning of disaster
SET URNCCBPARA: CTCHSwitch=OFF;
Issue 06 (2013-03-25)

280
RAN14.0
73
Configuring MBMS Introduction

Package
MBMS Introduction Package.
Prerequisites
l

License
Others
The existing PS domain functional entities (GGSN, SGSN, UTRAN, and UE) support
the Multimedia Broadcast Multicast Service (MBMS) bearer service.
A new functional entity, that is, the broadcast multicast service centre (BM-SC) is added
to provide a set of functions for the MBMS services.
The UE supports MBMS functions.
Context
The MBMS feature is an important feature specified by 3GPP Release 6. When MBMS is
enabled, point-to-multipoint multimedia services can be forwarded from one entity to multiple
entities over a common channel. In this way, the resources can be shared.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UMBMSSWITCH (CME single

configuration: UMTS Radio Global Configuration Express > MBMS
281
RAN14.0
Configuration > MBMS Switch; CME batch modification center: 3.15 Modifying
RNC Parameters in Batches) to set MBMS Control Switch to ON(ON).
2.
Run the BSC6900 MML command ADD UMBMSSA (CME single configuration:
UMTS Radio Global Configuration Express > MBMS Configuration > MBMS
SA; CME batch modification center: not supported) to add the MBMS service area
3.
Run the BSC6900 MML command ADD UCELLMBMSSA (CME single

configuration: UMTS Cell Configuration Express > MBMS Configuration >
Relation Between Cell and SA; CME batch modification center: not supported) to
add the mapping between the cell and the MBMS service area (SA) according to the
network plan.
4.
Run the BSC6900 MML command ADD USCCPCHBASIC (CME single

SCCPCH Basic Information; CME batch modification center: not supported) to add
the SCCPCH according to the network plan.
5.
Run the BSC6900 MML command ADD UFACH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > FACH; CME
batch modification center: not supported) to add the FACH according to the network
plan.
6.
Run the BSC6900 MML command ADD UFACHDYNTFS (CME single

Dynamic TFS of FACH; CME batch modification center: not supported) to add the
transport format set (TFS) of an FACH according to the network plan.
7.
batch modification center: not supported) to add a logical channel mapped to an FACH
8.
Run the BSC6900 MML command ADD USCCPCHTFC (CME single

TFC of SCCPCH; CME batch modification center: not supported) to add the
Calculated Transport Format Combination (CTFC) of an SCCPCH according to the
network plan.
9.
Run the BSC6900 MML command ADD UCELLMCCH (CME single

Configuration of the MCCH And MICH; CME batch modification center: not
supported) to add the MCCH and the MICH for the cell according to the network plan.
10. Configure the cell-level MBMS parameters according to the network plan.
a.
Run the BSC6900 MML command ACT USCCPCH (CME single

configuration: UMTS Cell Configuration Express > Channel Configuration
> SCCPCH Basic Information. Set Validation indication to Activated; CME
batch modification center: not supported) to activate the configuration
information of an SCCPCH.
b.
Run the BSC6900 MML command ACT UCELLMBMS (CME single

configuration: UMTS Cell Configuration Express > MBMS Configuration >
Cell MBMS Status. Set Cell MBMS state to Activated; CME batch
modification center: not supported) to activate the MBMS configuration data for
the cell.
11. Run the BSC6900 MML command SET UMTCH (CME single configuration:
UMTS Radio Global Configuration Express > MBMS Configuration > SemiIssue 06 (2013-03-25)

282
RAN14.0
Static Parameter of TF for FACH Carrying MTCH; CME batch modification

center: not supported) to set the MBMS service type and rate according to the network
plan.
12. Run the BSC6900 MML command SET URNCMBMSPARA (CME single
Configuration > MBMS Parameter in RNC Level; CME batch modification center:
3.15 Modifying RNC Parameters in Batches) to set the RNC-level parameters for
the MBMS algorithm according to the network plan.
l
1.
Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the

MBMS status in the cell.
2.
Conduct a test to check whether the MBMS UE can receive the corresponding MBMS
data successfully.
1.

RNC Parameters in Batches) to set MBMS Control Switch to OFF(OFF).
----End
Example
//Activation MBMS Introduction Package
//Enabling the MBMS control switch
SET UMBMSSWITCH: MbmsSwitch=ON;
//Adding the MBMS service area
ADD UMBMSSA: CnOpIndex=0, MbmsSaId=1;
//Adding the mapping between the cell and the MBMS service area (SA)
ADD UCELLMBMSSA: CellId=2, CnOpIndex=0, MbmsSaId=1;
//Adding the SCCPCH
ADD USCCPCHBASIC: CellId=2, PhyChId=11, ScrambCode=0, SlotFormat=D8,
TFCIpresence=NOT_EXISTS, MbmsChInd=MCCH;
//Adding the FACH
ADD UFACH: CellId=2, PhyChId=11, TrChId=10, RateMatchingAttr=220,
ToAWS=20, ToAWE=10, MaxFachPower=-10, MAXCMCHPI=D15, MINCMCHPI=D14,
SIGRBIND=TRUE, ChCodingType=CONVOLUTIONAL;
//Adding the transport format set (TFS) of an FACH
ADD UFACHDYNTFS: CellId=2, TrChId=10, RLCSize=168, TFsNumber=D3,
TbNumber1=0, TbNumber2=1, TbNumber3=2;
//Adding a logical channel mapped to an FACH
ADD UFACHLOCH: CellId=2, TrChId=10;
//Adding the Calculated Transport Format Combination (CTFC) of an SCCPCH
ADD USCCPCHTFC: CellId=2, PhyChId=11, CTFC=0;ADD USCCPCHTFC: CellId=2,
PhyChId=11, CTFC=1;
//Adding the MCCH and the MICH for the cell
ADD UCELLMCCH: CellId=2, MichId=19, PhyChIdforMcch=11, FachIdforMcch=10;
//Activating the configuration information of an SCCPCH
ACT USCCPCH: CellId=2, PhyChId=11;
//Activating the MBMS configuration data for the cell
ACT UCELLMBMS: CellId=100;
//Setting the MBMS service type and rate
SET UMTCH: ServiceType=STREAMING, ServiceBitRate=D128;
//Setting the RNC-level parameters for the MBMS algorithm
SET URNCMBMSPARA: MbmsTransMode=DYNAMIC;
Issue 06 (2013-03-25)

283
RAN14.0
//Deactivation MBMS Introduction Package

SET UMBMSSWITCH: MbmsSwitch=OFF;
Issue 06 (2013-03-25)

284
RAN14.0
74
Configuring MBMS Admission Control

WRFD-01061602 MBMS Admission Control.
Prerequisites
l

The feature WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
License
Context
The admission criteria of Iub resources and credit resources for the Multimedia Broadcast and
Multicast Service point-to-point/point-to-multipoint resource block (MBMS PtP/PtM RB)
requests is the same as that for other services. The cell power resources are preferentially
allocated to high-priority MBMS broadcasting services. Only the activation procedure of the
resource admission on the Uu interface is provided in this section.
Procedure
l
1.
l
Issue 06 (2013-03-25)

Parameters in Batches). In this step, select MBMS_UU_ADCTRL(MBMS UU
Load Admission Control Algorithm) from the Cell CAC algorithm switch dropdown list to enable the MBMS admission control on the Uu interface and select a
proper admission algorithm according to the network plan.
285
RAN14.0
1.
2.
l
Enable the MBMS admission algorithm, and then limit cell resources to ensure that
the admission resources are insufficient. In this manner, the admission fails. An
example is given as follows:
a.
Run the BSC6900 MML command ADD URESERVEOVSF to reserve the

downlink Orthogonal Variable Spreading Factor (OVSF) for the cell so that only
64 kbit/s services are supported in the cell.
b.
Originate a 256 kbit/s service. Check the messages traced on the Iu interface on
the RNC side, which are the MBMS SESSION START message from the core
network (CN) to the RNC and the MBMS SESSION START RSPPONSE
message from the RNC to the CN.
c.
Run the BSC6900 MML command DSP UCELLMBMSSERVICE. If the

parameter Reason of service setup failure is Access Failure, the MBMS
admission algorithm takes effect.
Disable the MBMS admission algorithm, and the services are successfully admitted.
1.

Parameters in Batches). In this step, deselect MBMS_UU_ADCTRL(MBMS UU
Load Admission Control Algorithm) from the Cell CAC algorithm switch dropdown list to disable the MBMS admission algorithm.
----End
Example
//Activating MBMS Admission Control
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-1,
NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST;
//Verifying MBMS Admission Control
ADD URESERVEOVSF: CellId=1, DLOVSFSF=SF32, DLCODENO=20;
DSP UCELLMBMSSERVICE: CellId=1;
//Deactivating MBMS Admission Control
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-0;
Issue 06 (2013-03-25)

286
RAN14.0
75
Configuring MBMS Load Control
WRFD-01061603 MBMS Load Control.
Prerequisites
l

License
Context
The feature helps to lighten the cell load when the cell enters the congestion state and ensures
the system stability. When the cell is in the basic congestion state and downlink congestion is
detected, the power consumed by MBMS services is reduced.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, select DL_UU_LDR(Downlink UU LDR
Algorithm) and DL_UU_OLC(Downlink UU OLC Algorithm) from the Cell LDC
algorithm switch drop-down list to enable downlink load reshuffling and downlink
overload congestion control on the Uu interface.
2.
287
RAN14.0
Parameters in Batches) to set the congestion-relief action triggered by Load

Reshuffling (LDR).
3.
Run the BSC6900 MML command ADD UCELLOLC (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Overload
Congestion Control Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to set the sequence and number of
MBMS services to be released for Overload Control (OLC).
1.
Originate an MBMS service on the BSC6900, and ensure that service data is sent.
2.
Run the BSC6900 MML command MOD UCELLLDM. Based on the current load
of the cell, set the triggering thresholds for LDR and OLC. Ensure that the
corresponding load control actions can be triggered.
3.
When the cell load exceeds the LDR threshold, the power of MBMS services is
reduced in the cell. Check the maxFACH Power information element in the
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST
message on the Iub interface.
4.
When the cell load exceeds the OLC threshold, MBMS services are released.
1.

Parameters in Batches). In this step, deselect DL_UU_LDR(Downlink UU LDR
Algorithm) and DL_UU_OLC(Downlink UU OLC Algorithm) from the Cell LDC
algorithm switch drop-down list to disable downlink load reshuffling and downlink
overload congestion control on the Uu interface.
2.
Optional: Run the BSC6900 MML command MOD UCELLLDR (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell LDR
Cell Parameters in Batches) to remove the MBMS service power reduction from the
LDR-triggered actions.
----End
Example
//Activating MBMS Load Control
//Enabling downlink load reshuffling and downlink overload congestion
control on the Uu interface
MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR-1&DL_UU_OLC-1;
//Setting the first LDR-triggered action to power reduction of MBMS
services
MOD UCELLLDR: CellId=1, DlLdrFirstAction=MBMSDECPOWER;
//Enabling the triggered OLC to release MBMS services on a one-by-one
basis
ADD UCELLOLC: CellId=1, SeqOfUserRel=MBMS_REL, MbmsOlcRelNum=1;
//Verifying MBMS Load Control
MOD UCELLLDM: CellId=1, DlLdrTrigThd=2, DlLdrRelThd=1, DlOlcTrigThd=2,
DlOlcRelThd=1;
//Deactivating MBMS Load Control
MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR-0&DL_UU_OLC-0;
MOD UCELLLDR: CellId=1, DlLdrFirstAction=NoAct;
Issue 06 (2013-03-25)

288
RAN14.0
76
Configuring MBMS Transport Resource

Management
WRFD-01061605 MBMS Transport Resource Management.
Prerequisites
l

The features WRFD-010616 MBMS Introduction Package must be configured before
License
Context
For the same MBMS session in the same Node B, a separate Iub transport bearer is established
for each cell. An example is shown in the following figure assuming 3 cells in one Node B.
Three copies of exact same MBMS session data are sent through the Iub from the CRNC to the
Node B.
For details, see the Optional Feature Description of Huawei UMTS.
Issue 06 (2013-03-25)

289
RAN14.0
Procedure
l
1.
Use UEs to require an MBMS service in the two cells under the same NodeB.
2.
Check the signaling traced on the Iub interface.

You may find two pairs of COMMON TRANSPORT CHANNEL SETUP
REQUEST/COMMON TRANSPORT CHANNEL SETUP RESPONSE
messages.
The BROADCAST REFERENCE IEs in the two COMMON TRANSPORT
CHANNEL SETUP REQUEST messages are different. This indicates that the
messages are from different Iub interfaces.
Both the COMMON TRANSPORT CHANNEL SETUP RESPONSE
messages contain the TLA and Binding ID.
----End
Issue 06 (2013-03-25)

290
RAN14.0
77
Configuring Streaming Service on

MBMS
WRFD-01061606 Streaming Service on MBMS.
Prerequisites
l

feature depends on the feature WRFD-010616 MBMS Introduction Package.
License
Context
This feature enables the MBMS service to be carried on the PS streaming class, therefore
ensuring QoS.
Procedure
l
This feature depends on MBMS basic functions.
This feature can be activated only after MBMS basic functions are enabled. For details, see
the section "Configuring MBMS Introduction Package".
The parameters of streaming services have been configured by the RNC by default. This
feature is used as long as the CN sends MBMS services in the form of PS streaming. No
activation operation is needed.
l
Issue 06 (2013-03-25)
291
RAN14.0
1.
Use an MBMS-supportive UE to request an MBMS mobile television service and

receive the corresponding data.
2.
The UE receives the data of the MBMS mobile television service successfully.
This feature is used as long as MBMS is configured. There is no need to deactivate this
feature.
----End
Issue 06 (2013-03-25)

292
RAN14.0
78
Configuring 16/32/64/128Kbps Channel

Rate on MBMS
WRFD-01061608 16/32/64/128Kbps Channel Rate on MBMS.
Prerequisites
l

License
Context
This feature is related to four MBMS channel rates: 16 kbit/s, 32 kbit/s, 64 kbit/s, and 128 kbit/
s.
Procedure
l
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the

MBMS status in the cell and the bandwidth of the MBMS service.
2.
Use an MBMS-supportive UE to request an MBMS service, the UE can receive the

corresponding data successfully.
293
RAN14.0

----End
Issue 06 (2013-03-25)

294
RAN14.0
79
Configuring MBMS Phase 2
MBMS Phase 2.
Prerequisites
l

License
Other Prerequisites
UE should support the corresponding enhanced MBMS functions.
Context
This feature supports the enhanced MBMS (PTP/PTM) to save cell resources. The MBMS phase
2 includes following features:
l
WRFD-01066001 MBMS Enhanced Broadcast Mode
WRFD-01066002 MBMS P2P over HSDPA
WRFD-01066003 MBMS Admission Enhancement
WRFD-01066004 Inter-Frequency Neighboring Cell Selection for MBMS PTP Users
Procedure
For details about activation procedures, see the following sections:
Issue 06 (2013-03-25)

295
RAN14.0

----End
Issue 06 (2013-03-25)

296
RAN14.0
80
Configuring MBMS Enhanced Broadcast

Mode
WRFD-01066001 MBMS Enhanced Broadcast Mode.
Prerequisites
l

License
Context
Compared with broadcast mode, it is a more efficient way to deploy the point-to-multipoint
services, such as mobile TV.
This feature can be activated only after MBMS basic functions are enabled. For details, see the
section "Configuring MBMS Introduction Package".
The CN specifies whether broadcast mode or enhanced broadcast mode is used for MBMS
services. If the CN specifies the enhanced broadcast mode and the license for this mode is
activated, then, enhanced broadcast mode is used. The MBMS transmission mode should be
configured on the RNC.
The MBMS transmission mode can be configured at the SA level, RNC level, or cell level. The
cell level has the highest priority, while the RNC level has the lowest priority. That is, if the
MBMS transmission mode is configured at both the RNC level and the cell level, the cell level
configuration takes effect in the corresponding cell. The detailed process is as follows:
Issue 06 (2013-03-25)

297
RAN14.0
Procedure
l
1.
Run the BSC6900 MML command SET URNCMBMSPARA (CME single

3.15 Modifying RNC Parameters in Batches) to set the transmission mode at the
RNC level through the Mbms Transfer Mode parameter.
2.
Optional: Run the BSC6900 MML command ADD USAMBMSPARA (CME single
Configuration > MBMS Parameter in SA Level; CME batch modification center:
not supported) to set the transmission mode at the SA level through the Mbms
Transfer Mode parameter.
3.
Optional: Run the BSC6900 MML command ADD UCELLMBMSPARA (CME

single configuration: UMTS Cell Configuration Express > MBMS
Configuration > MBMS Parameter in Cell Level; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches) to set the transmission mode
at the cell level through the Mbms Transfer Mode parameter.
4.

3.15 Modifying RNC Parameters in Batches) to set the transfer threshold between
PtP and PtM mode through the Counting Threshold and the Ptp To Ptm Offset
parameters.
1.
Use an MBMS-supportive UE to request an MBMS service and receive the

corresponding data.
2.
Check MBMS SESSION START message traced on the Iu interface at the RNC. If
the value of the MBMS Bearer Service Type IE is broadcast and the value of MBMS
Counting Information IE is counting, the enhanced broadcast mode is configured.
3.
Use one or two MBMS-supportive UEs to receive the MBMS service, you can find
that the DCH or HS-DSCH is used. Use three MBMS-supportive UEs to receive the
MBMS service, you can find that the FACH is used.
To deactivate this feature, switch off the license item of the feature.
----End
Example
//Activating MBMS Enhanced Broadcast Mode
SET URNCMBMSPARA: MbmsTransMode= DYNAMIC;
ADD USAMBMSPARA: CnOpIndex=0, MbmsSaId=0, MbmsTransMode= DYNAMIC;
ADD UCELLMBMSPARA: CellId=100, MbmsTransMode= DYNAMIC;
SET URNCMBMSPARA: NCountingThd=2, NPtpToPtmOffset=1;
Issue 06 (2013-03-25)

298
RAN14.0
81
Configuring MBMS P2P over HSDPA
WRFD-01066002 MBMS P2P over HSDPA.
Prerequisites
l

The features WRFD-010616 MBMS Introduction Package and WRFD-010610 HSDPA
Introduction Package must be configured before this feature is activated.
License
Context
This feature enables Multimedia Broadcast and Multicast Service point-to-point (MBMS P2P)
services to be carried on the HS-DSCH, saving cell resources.
Procedure
l
l
Issue 06 (2013-03-25)
1.

3.15 Modifying RNC Parameters in Batches). In this step, set Mbms Transfer
Mode to DYNAMIC.
2.

Parameters in Batches). In this step, set Service Mapping Strategy Switch to
MAP_PS_STREAM_ON_HSDPA_SWITCH.
299
RAN14.0
1.
Set up a 256 kbit/s MBMS streaming service.
2.
Use an MBMS-capable UE to request the MBMS service and receive the

corresponding data.
To deactivate this feature, switch off the license item of the feature.
----End
Example
//Activating MBMS P2P over HSDPA
SET URNCMBMSPARA: MbmsTransMode= DYNAMIC;
SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1;
Issue 06 (2013-03-25)

300
RAN14.0
82
Configuring MBMS Admission

Enhancement
WRFD-01066003 MBMS Admission Enhancement.
Prerequisites
l

License
Context
This feature provides different admission policies for Multimedia Broadcast and Multicast
Service point-to-multipoint (MBMS PTM) services and MBMS point-to-point (MBMS PTP)
services. MBMS PTP services use the same admission, preemption, and congestion criteria with
normal services except MBMS HSDPA services. MBMS PTM services should be treated
differently so that they do not occupy excessive resources to block non-MBMS connection
admission. In addition, some resources should be reserved for MBMS PTM services.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET UQUEUEPREEMPT (CME single

configuration: UMTS Radio Global Configuration Express > Queue Preempt
Parameters Configuration > RNC Oriented Queue Preempt Algorithm
Parameters; CME batch modification center: 3.15 Modifying RNC Parameters in
Batches) to set Mbms PreemptAlgoSwitch and Preempt algorithm switch to
ON.
301
RAN14.0
2.
1.
Run the BSC6900 MML command LST URNCMBMSPARA to check the

configuration.
2.
Enable a low-priority user to access the cell.
3.
Enable the admission algorithm, and then limit cell resources so that the admission
resources in the cell are insufficient. In this case, the MBMS services successfully
preempt common services. An example is given as follows:
4.

3.15 Modifying RNC Parameters in Batches) to set the preemption parameters for
PTM services. The actual preemption capabilities are determined by both the settings
of these parameters and the parameter settings sent by the CN. The parameter settings
of PTP services are sent by the CN and do not need to be set manually.
a.
Run the BSC6900 MML command ADD URESERVEOVSF to reserve the

downlink OVSF for the cell so that only 64 kbit/s services are supported in the
cell.
b.
Originate a 256 kbit/s service. Check the messages traced on the Iu interface on
the RNC side, which are the MBMS SESSION START message from the CN
to the RNC and the MBMS SESSION START RSPPONSE message from the
RNC to the CN.
Run the BSC6900 MML command DSP UCELLMBMSSERVICE. If the parameter

Current State of Service Session is Setuping, the user connection is released due to
preemption.
1.

Batches) to set Mbms PreemptAlgoSwitch to OFF.
----End
Example
//Activating MBMS Admission Enhancement
SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, MbmsPreemptAlgoSwitch=ON;
SET URNCMBMSPARA: MbmsTransMode=PTM, PtmPreemptSwitch=ON,
PtmStrmPasiSwitch=ON, PtmNullStrmPasiSwitch=ON;
//Verifying MBMS Admission Enhancement
ADD URESERVEOVSF: CellId=1, DLOVSFSF=SF32, DLCODENO=20;
DSP UCELLMBMSSERVICE: CellId=1;
//Deactivating MBMS Admission Enhancement
SET UQUEUEPREEMPT: MbmsPreemptAlgoSwitch=OFF;
Issue 06 (2013-03-25)

302
RAN14.0
83 Configuring Inter-Frequency Neighboring Cell Selection

for MBMS PTP Users
83
Configuring Inter-Frequency
Neighboring Cell Selection for MBMS PTP

Users
WRFD-01066004 Inter-Frequency Neighboring Cell Selection for MBMS PTP Users.
Prerequisites
l

feature depends on the feature WRFD-010616 MBMS Introduction Package,
WRFD-010660 MBMS Phase 2.
License
Context
This feature enables the filtering and handover of a target cell based on the MBMS channel
resources in the inter-frequency neighboring cells, therefore ensuring the continuity of the
MBMS service.
Procedure
l
This feature does not need to be verified.
----End
Issue 06 (2013-03-25)

303
RAN14.0
84
Configuring FACH Transmission

Sharing for MBMS
FACH Transmission Sharing for MBMS.
Prerequisites
l

The feature WRFD-010616 MBMS Introduction Package has been configured before
License
Context
This feature enables the FACHs that carry MBMS services to share transport resources over the
Iub interface, thereby saving the Iub bandwidth.
Procedure
l
1.

RNC Parameters in Batches). In this step, set MBMS Iub Sharing Switch to ON
(ON).
1.
Before turning on the transmission sharing switch, activate the MBMS services in two
cells served by the same NodeB. View the tracing messages over the Iub interface.
REQUEST/COMMON TRANSPORT CHANNEL SETUP RESPONSE messages,
where the BROADCAST REFERENCE IEs in the two COMMON TRANSPORT
Issue 06 (2013-03-25)

304
RAN14.0
CHANNEL SETUP REQUEST messages are different. This indicates that the
messages are transmitted over different Iub interfaces.
2.
Turn on the transmission sharing switch, activate the MBMS services in two cells
served by the same NodeB, and view the tracing messages over the Iub interface.
REQUEST/COMMON TRANSPORT CHANNEL SETUP RESPONSE messages,
where the BROADCAST REFERENCE IEs in the two COMMON TRANSPORT
CHANNEL SETUP REQUEST messages are the same. This indicates that the
messages are transmitted over the same Iub interface. This feature has been activated.
1.

RNC Parameters in Batches). In this step, set MBMS Iub Sharing Switch to OFF
(OFF).
----End
Example
//Activating FACH Transmission Sharing for MBMS
SET UMBMSSWITCH: MbmsSwitch=ON, MbmsIubSharingSwitch=ON;
//Deactivating FACH Transmission Sharing for MBMS
SET UMBMSSWITCH: MbmsSwitch=ON, MbmsIubSharingSwitch=OFF;
Issue 06 (2013-03-25)

305
RAN14.0
85 Configuring MBMS FLC(Frequency Layer

Convergence)/FLD(Frequency Layer Dispersion)
85
Configuring MBMS FLC(Frequency
Layer Convergence)/FLD(Frequency Layer

Dispersion)
MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion).
Prerequisites
l

License
Others Prerequisites
UEs support this feature.
Context
Frequency Layer Convergence (FLC) denotes the process where the UTRAN requests UEs to
preferentially reselect to the frequency layer on which the MBMS service is intended to be
transmitted.
Frequency Layer Dispersion (FLD) denotes the process where the UTRAN redistributes UEs
across frequencies.
FLC helps users obtain the information about an MBMS service in real time. FLD reduces cell
load after the MBMS service is finished.
FLD is activated automatically after FLC takes effect, and is deactivated automatically after
FLC is disabled.
Issue 06 (2013-03-25)

306
RAN14.0

Procedure
l
NOTE
Two overlapping cells covered by multiple carriers must be enabled with MBMS.
The cell using frequency F1 is in the SA of MBMS, and other cells using other frequencies are not
in the SA of MBMS.
1.
Run the BSC6900 MML command MOD UCELLMCCH (CME single

supported). In this step, set Flc Algo Switch to ON(ON).
2.

HO_ALGO_MBMS_FLC_SWITCH check box under the parameter HandOver
Switch.
1.
Configure an MCCH in an R99 cell and set an MBMS cell to the neighboring cell of
the R99 cell.
2.
Make UEs camp on the R99 cell, activate the MBMS service, and accept the MBMS
service.
If UEs are reselected to the MBMS cell successfully and transmit and receive data
normally, FLC is activated.
3.
Move UEs to the MBMS cell edge and terminate the MBMS service.
If some UEs are reselected to the R99 cell, FLD is activated.
1.
Run the BSC6900 MML command MOD UCELLMCCH (CME single

supported). In this step, set Flc Algo Switch to OFF(OFF).
2.

HO_ALGO_MBMS_FLC_SWITCH check box under the parameter HandOver
Switch.
----End
Example
//Activating MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer
Dispersion)
MOD UCELLMCCH: CellId=1, FlcAlgoSwitch=ON;
SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-1;
//Deactivating MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer
Dispersion)
Issue 06 (2013-03-25)

307
RAN14.0

MOD UCELLMCCH: CellId=1, FlcAlgoSwitch=OFF;

SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-0;
Issue 06 (2013-03-25)

308
RAN14.0
86
Configuring MBMS over Iur
MBMS over Iur.
Prerequisites
l

The feature WRFD-010660 MBMS Phase 2 has been configured before this feature is
activated.
License
Other Prerequisites
The neighboring RNC supports the MBMS feature.
The Point to Point (PTP) services are supported.
Context
This feature extends the application scope of the MBMS service.
Procedure
l
This feature does not need to be activated. It takes effect after the feature WRFD-010616
MBMS Introduction Package is activated.
Initiate a softt handover by moving a UE that is in CELL_DCH state and receiving the
MBMS data in PTP mode from the Serving RNC (SRNC) to the Drift RNC (DRNC). In
this way, a Radio Link (RL) is established on the Iur interface. The cell to which the RL
belongs performs the MBMS service in Point to Multipoint (PTM) mode. If at the time
being the UE under the DRNC is receiving only MBMS data in PTM mode, this feature
has been activated.
Issue 06 (2013-03-25)

309
RAN14.0
----End
Issue 06 (2013-03-25)

310
RAN14.0
87
Configuring Dynamic Power Estimation

for MTCH
Dynamic Power Estimation for MTCH.
Prerequisites
l

The feature WRFD-010660 MBMS Phase 2 has been configured before this feature is
activated.
License
Context
This feature enables dynamic adjustment of the transmit power of the MTCH based on the
number of neighboring cells that are in PTM mode.
It does not conflict with the maximum power and minimum power defined in the MBMS service.
In addition, this feature depends on the MBMS service, because it introduces only power
deviation.
Procedure
l
This feature does not need to be activated. Telecom operators only need to set the power
adjustment threshold to an appropriate value.
1.
Issue 06 (2013-03-25)

3.15 Modifying RNC Parameters in Batches). In this step, set Combine Neighbour
Cell Percent to an appropriate value based on the network plan. When the rate of
311
RAN14.0
PTM applications in a cell in PTM mode reach the value of this parameter, this feature
brings a combining gain. If Combine Neighbour Cell Percent is set to a small value,
the transmit power of the MBMS SCCPCH in the cell decreases.
l
1.
Select two MBMS cells (cell A and cell B) that work in the same frequency. In cell
A, configure only cell B as its intra-frequency neighboring cell. Apply the PTM mode
in cell A and PTP mode in cell B.
2.
Use an MBMS-capable UE to initiate an MBMS service in cell A. View the

NBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub interface to
check the power of the FACH that carries the service.
3.
Set cell B to send MBMS data in the same channel in PTM mode. In this manner, the
rate of the intra-frequency neighboring cells that apply the PTM mode exceeds the
value of the preset Combine Neighbour Cell Percent.
4.
View the NBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub

interface to check the power of the FACH that carries the service.
Expected result: The power of the FACH that carries data of the MBMS channel
decreases by 5 dB.
----End
Example
//Setting the Power Adjusting Threshold
SET URNCMBMSPARA: CombNCellPercent=50;
Issue 06 (2013-03-25)

312
RAN14.0
88
Configuring MSCH Scheduling
MSCH Scheduling.
Prerequisites
l

License
Context
This feature enables a UE to receive packets on the MTCH in Discontinuous Reception (DRX)
mode, thereby reducing UE power consumption.
Procedure
l
1.
Issue 06 (2013-03-25)

RNC Parameters in Batches). In this step, set both Msch Switch For
NonMtchMulti Sccpch and Msch Switch For MtchMulti Sccpch to ON(ON).
1.
Use an MBMS-capable UE to initiate an MBMS service and ensure that the UE can
receive the MBMS data.
2.
Check messages traced on the Uu interface. If MSCH configuration information is

found in the MBMS CURRENT CELL P-T-M RB INFORMATION, MBMS
GENERAL INFORMATION, and MBMS NEIGHBOURING CELL P-T-M RB
INFORMATION messages, this feature has been activated.
313
RAN14.0
1.

RNC Parameters in Batches). In this step, set both Msch Switch For
NonMtchMulti Sccpch and Msch Switch For MtchMulti Sccpch to OFF(OFF).
----End
Example
//Activating MSCH scheduling
SET UMBMSSWITCH: MbmsSwitch=ON, MschSwitchForNonMtchMulti=ON,
MschSwitchForMtchMulti=ON;
//Deactivating MSCH scheduling
SET UMBMSSWITCH: MschSwitchForNonMtchMulti=OFF,
MschSwitchForMtchMulti=OFF;
Issue 06 (2013-03-25)

314
RAN14.0
89
Configuring MBMS Channel Audience

Rating Statistics
MBMS Channel Audience Rating Statistics.
Prerequisites
l

License
Other Prerequisites
The BMSC on the CN side identifies the channel with a fixed Temporary Mobile Group
Identity (TMGI) when delivering a program source.
Context
This feature enables statistics on MBMS channels to help the operator obtain the audience rating
of the MBMS channels.
Procedure
l
Set the MBMS channels (a maximum of five MBMS channels can be set) on which statistics
is to be performed. Then, send the TMGIs of these channels from the M2000 to the RNC.
The RNC then measures the following channel-related counters:
Issue 06 (2013-03-25)

315
RAN14.0
Average number of users in PTP mode

Average number of users in PTM mode
Time for channels remaining in PTM mode
TTime for channels remaining in PTP mode
Based on the preceding counters, the average duration for which each UE is connected to
a channel can be calculated.
l
----End
Issue 06 (2013-03-25)

316
RAN14.0
90
Configuring Cell ID + RTT Function

Based LCS
Cell ID + RTT Function Based LCS.
Prerequisites
l
If SAS-CENTRIC locating is required, SAS equipment has been configured.

License
UE is needed to report the relevant measurement results.
CN is needed to trigger the location request.
The UE supports at least one of the following locating methods:
UE-assisted CELLID+RTT locating or UE-based CELLID+RTT locating in RNCCENTRIC mode
UE-assisted CELLID+RTT locating in the SAS-CENTRIC mode
Context
The simplest CELLID + Round Trip Time (RTT) locating method is to directly use the
geographical center of the coverage area of the reference cell as the locating result.
To achieve high locating accuracy, the BSC6900 demands RTT measurement in all cells in the
active set and requests the UE to perform locating measurement on the corresponding cells. By
means of the two types of measurement, the BSC6900 calculates the time of arrival (TOA) of
signal from the cell antenna to the UE. By multiplying the TOA by the velocity of light, the
BSC6900 obtains the distance between a certain cell and the UE. If three TOA circles intersect,
the BSC6900 can obtain the accurate location of the UE.
Issue 06 (2013-03-25)

317
RAN14.0
Procedure
l
1.
Optional: If inter-RNC locating is required, the Iur interface needs to be configured.

For details, see 94 Configuring LCS over Iur.
2.
Optional: If SAS-CENTRIC mode needs to be supported, the Iupc interface is

required. For details, see 95 Configuring Iupc Interface for LCS Service.
3.
Run the BSC6900 MML command SET USMLC (CME single configuration: UMTS
Radio Global Configuration Express > Location Service Parameter
Configuration > SMLC Algorithm Parameters; CME batch modification center:
3.15 Modifying RNC Parameters in Batches) to set the parameters of the SMLC
algorithm. In this step, set UE Positioning Method, CELLID+RTT Method Type,
and Location Working Mode to appropriate values.
4.
Run the BSC6900 MML command ADD USMLCCELL (CME single configuration:
UMTS Cell Configuration Express > SMLC and IPDL > Cell SMLC
Information; CME batch modification center: not supported) to set the following
location information parameters of the cell:
Cell location configuration type
Geographical location information about the antenna:
Cell Antenna Latitude
Cell Antenna Altitude
Cell Antenna Longitude
Cell coverage information:
Cell Antenna Max Coverage
Cell Antenna Orientation
Cell Antenna Opening
1.
Issue 06 (2013-03-25)
Initiate Iu, Iub, and Uu interface message tracing, as shown in Figure 90-1, Figure
90-2, and Figure 90-3 respectively.

318
RAN14.0
Issue 06 (2013-03-25)

319
RAN14.0
2.
Use a UE to access the cell and enable the CN to send a locating request message.
3.
The message LOCATION REPORTING CONTROL and LOCATION

REPORT are traced on the Iu interface, as shown in Figure 90-4 and Figure 90-5.
Figure 90-4 LOCATION REPORTING CONTROL
Issue 06 (2013-03-25)

320
RAN14.0
Figure 90-5 LOCATION REPORT
4.
Issue 06 (2013-03-25)
The messages traced on the Iub interface show that the procedure Dedicated
Measurement Initiation is performed on all links in the active set and that the value
of Dedicated Measurement Type is Round Trip Time, as shown in Figure 90-6
and Figure 90-7.

321
RAN14.0
Figure 90-6 Dedicated Measurement Type
Figure 90-7 Round Trip Time
5.
Issue 06 (2013-03-25)
From the traced Uu interface messages, you can see the information about the UE RxTx time difference measurement, which is a type of internal measurement (if the UE
supports UE Rx-Tx time difference type 2 measurement, the locating method for RxTx time difference type 2 measurement is adopted), as shown in Figure 90-8 and
Figure 90-9.

322
RAN14.0
Figure 90-8 UE Rx-Tx time difference
Figure 90-9 UE Rx-Tx time difference type 1
1.
3.15 Modifying RNC Parameters in Batches) to deactivate the CELLID+RTT
locating method. In this step, deselect the CELLID_RTT check box under parameter
UE Positioning Method.
----End
Example
//Activating Cell ID + RTT Function Based LCS
//Setting the parameters of the SMLC algorithm
SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-1&OTDOA-0&AGPS-0,
CELLIDRTTMethodType=UE_ASSISTED, ForcedSHOSwitch=OFF,
IntraRelThdFor1A=2, IntraRelThdFor1B=2, TrigTime1A=D10, TrigTime1B=D10,
SHOQualmin=-20, LcsWorkMode=RNC_CENTRIC;
//Setting the location information parameters of the cell
Issue 06 (2013-03-25)

323
RAN14.0
ADD USMLCCELL: RNCId=2121, CellId=80, CellLocCfgType=CELL_ANTENNA,

GCDF=DEG, MTRLGY=MET, AntennaLatitudeDegree=78900,
AntennaLongitudeDegree=6789, AntennaAltitudeMeter=4567,
MaxAntennaRange=5678, AntennaOrientation=567, AntennaOpening=456,
CellAverageHeight=6789;
//Deactivating Cell ID + RTT Function Based LCS
SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-0&OTDOA-0&AGPS-0;
Issue 06 (2013-03-25)

324
RAN14.0
91
Configuring OTDOA Based LCS
OTDOA Based LCS.
Prerequisites
l
The corresponding NodeBs should be equipped USCU card with GPS function.

License
The UE supports at least one of the following positioning methods:
UE-based OTDOA positioning method
UE-assisted OTDOA positioning method
Context
Huawei UTRAN supports IPDL-OTDOA location services. In this feature, the NodeB is
configured with a GPS card and supports cell frame timing measurement. In addition,
BSC6900 initiates and traces the SFN-SFN observed time difference measurement. BSC6900
calculates the relative time difference (RTD) of the cell related to positioning based on the latest
measurement reports (MRs).
After BSC6900 receives a LOCATON REPORT CONTROL message, it requests the UE to
perform SFN-SFN observed time difference measurement if the IPDL-OTDOA positioning
method is used. After receiving the corresponding MRs, BSC6900 calculates the location of the
UE. For accurate location calculation, BSC6900 may request the NodeB to perform RTT
measurement and request the UE to perform Rx-Tx time difference measurement.
Issue 06 (2013-03-25)

325
RAN14.0
Procedure
l
1.
Optional: Configure the Iur interface if inter-RNC locating is required. For details,
see 94 Configuring LCS over Iur.
2.
3.15 Modifying RNC Parameters in Batches) to set the SMLC algorithm
parameters. In this step, set UE Positioning Method and Location Working Mode
to appropriate values.
NOTE
Location Working Mode must be set to RNC_CENTRIC(RNC CENTRIC Mode).
3.
Run the BSC6900 MML command ADD USMLCCELL (CME single configuration:
UMTS Cell Configuration Express > SMLC and IPDL > Cell SMLC
Information; CME batch modification center: not supported) to add the location
information about a cell. In this step, set the following parameters to appropriate
values:
Cell Location Setting Type
Parameters associated with the geographical location information about the
antenna system
Parameters associated with the cell coverage information
4.
Run the BSC6900 MML command ADD UCELLGPSFRMTIMING (CME single

configuration: UMTS Cell Configuration Express > SMLC and IPDL > Cell GPS
Frame Timing; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to set the parameters related to UTRAN GPS cell frame
timing measurement. In this step, set Cell ID and GPS Frame Timing Active Flag
1.
Check whether the parameters required for positioning are correctly set.
Run the BSC6900 MML command LST USMLC to query SMLC algorithm
parameter settings.
Run the BSC6900 MML command LST USMLCCELL to query the settings of
the location parameters of a cell.
Run the BSC6900 MML command LST UCELLGPSFRMTIMING to query the
parameter settings related to UTRAN GPS cell frame timing measurement.
1.
Issue 06 (2013-03-25)
326
RAN14.0
3.15 Modifying RNC Parameters in Batches) to deactivate the OTDOA-based

location service.
----End
Example
//Activating OTDOA Based LCS
//Setting the parameters for the SMLC algorithm
SET USMLC: SmlcMethod=OTDOA-1, OTDOAMethodType=UE_BASED,
LcsWorkMode=RNC_CENTRIC;
//Setting parameters related to UTRAN GPS cell frame timing measurement
ADD UCELLGPSFRMTIMING: CellId=80, StartFlag=ACTIVE;
//Deactivating OTDOA Based LCS
SET USMLC: SmlcMethod=OTDOA-0;
Issue 06 (2013-03-25)

327
RAN14.0
92
Configuring A-GPS Based LCS
A-GPS Based LCS. (This feature cannot be configured using the CME. )
Prerequisites
l
If GPS receiver is located at RNC,BSC6900 needs clock board such as GCGa to support
this feature.
If GPS receiver is located at NodeB, NodeB should be equipped with USCU card with
GPS function.
When the RNC-CENTRIC locating service is required:
If a Global Positioning System (GPS) receiver is configured on the BSC6900 side,
the BSC6900 must be configured with the General Clock Unit with GPS REV:a
(GCGa) board.
If a GPS receiver is configured on the NodeB side, the NodeB must be configured
with the Universal Satellite card and Clock Unit (USCU) and WCDMA GPS
Receiving Unit (WGRU), and all the equipment (including the GPS antenna system)
must be properly installed and connected.
When the SAS-CENTRIC locating service is required, the BSC6900 must be configured
with a Stand-Alone SMLC (SAS) device. SMLC refers to Serving Mobile Location
Center.
NOTE
If A-GPS positioning is required, the GPS receiver does not need to be installed in BSC6900 side
or NodeB side.

License
Other Prerequisites
NodeB V200R014 supports this feature while NodeB V100R014 does not support this
feature.
Issue 06 (2013-03-25)

328
RAN14.0
The UE supports UE-based A-GPS positioning or UE-assisted A-GPS positioning or

both.
The CN can send positioning requests.
Context
A-GPS positioning is an application of GPS positioning in the WCDMA network. In open areas,
A-GPS positioning can provide high positioning sensitivity, shorten positioning time, and save
power.
The location information about the GPS receiver can be automatically searched by the GPS
receiver itself or be configured by a user.
l
If the accurate location information (to be provided by the surveying and mapping
authorities) about the antenna of the GPS receiver can be obtained, it is recommended that
the information be specified when the GPS receiver is being configured. In this way, the
GPS receiver can quickly search for the satellite group in the area where it is located, and
accurately calculate the differential GPS information.
If the accurate location information about the antenna of the GPS receiver cannot be
obtained, the auto search mode can be selected.
Procedure
NOTE
The BSC6900 and NodeB must be configured with the related data to activate this feature.
Activation Procedure on the BSC6900 Side

1.
Optional: If inter-RNC locating is required, configure the Iur interface by referring

to 94 Configuring LCS over Iur.
2.
Optional: If the GPS positioning method in SAS-CENTRIC mode is required,

configure the Iu-PC interface by referring to 95 Configuring Iupc Interface for LCS
Service.
3.
In RNC-CENTRIC mode, if a GPS receiver is configured on the BSC6900 side, run

the BSC6900 MML command SET CLKTYPE to set the type of clock board to
GCGa.
4.
Run the BSC6900 MML command SET USMLC to set the SMLC algorithm
parameters. In this step, set UE Positioning Method and Location Working Mode
5.
Run the BSC6900 MML command ADD USMLCCELL to set the parameters related
to cell location information to appropriate values.
Cell Location Setting Type
Parameters associated with the geographical location information about the
antenna system
Issue 06 (2013-03-25)

329
RAN14.0

Parameters associated with the cell coverage information
6.
In RNC-CENTRIC mode, run the BSC6900 MML command ADD GPS to set the
parameters related to the GPS receiver. In this step, set GPS ID, GPS type, GPS
antenna latitude, GPS antenna longitude, and GPS antenna altitude to appropriate
values.
7.
In RNC-CENTRIC mode, run the BSC6900 MML command ACT GPS to activate
the specified GPS receiver. In this step, set AGPS ID and Type to appropriate values.
8.
Optional: Run the BSC6900 MML command STR POSAVE with Maximum time
for posave set to 12. Then, check the single point positioning results of the GPS
receiver in the \bam\common\fam\smlc directory.
Activation Procedure for NodeB V200R014

NOTE
In RNC-CENTRIC mode, a GPS receiver can be configured on the NodeB side as required. If a GPS
receiver is configured on the NodeB side, the NodeB must be configured with the USCU and WGRU,
and all the equipment (including the GPS antenna system) must be properly installed and connected.
1.
Run the NodeB MML command ADD BRD to add a USCU board.
Set Cabinet No., Subrack No., and Slot No. to appropriate values based on the
actual location of the USCU board.
Set Board Type to USCU.
2.
Run the NodeB MML command SET CLKMODE to set the working mode of the
reference clock source.
3.
Run the NodeB MML command ADD GPS to add a GPS clock link.
4.
Run the NodeB MML command MOD GPSPOS to add a GPS receiver.
If Way to Get Position is set to USER_CONFIG(User Config), set Antenna
Longitude, Antenna Latitude, and Antenna Altitude to appropriate values.
If Way to Get Position is set to SEARCH_WITH_DURATION(Search with
duration), set Duration to an appropriate value.
If Way to Get Position is set to SEARCH_WITH_PRECISION(Search with
precision), set Precision to an appropriate value.
Verification Procedure on the BSC6900 Side
1.
Issue 06 (2013-03-25)
Initiate Iu and Uu interface tracing, as shown in Figure 92-1 and Figure 92-2
respectively.

330
RAN14.0
Figure 92-1 Iub interface tracing
Issue 06 (2013-03-25)
2.
Make a UE access the network and enable the CN to send a positioning request.
3.
Over the Iu interface, you can view the Location Reporting Control and Location
Report messages, as shown in Figure 92-3 and Figure 92-4.

331
RAN14.0
Figure 92-3 LOCATION REPORTING CONTROL
Issue 06 (2013-03-25)

332
RAN14.0
Figure 92-4 LOCATION REPORT
4.
The Uu interface tracing messages contain the information about A-GPS positioning
measurement, as shown in Figure 92-5 and Figure 92-6.
Figure 92-5 ue-positioning-GPS-AssistanceData
Issue 06 (2013-03-25)

333
RAN14.0
Figure 92-6 GPS-MeasurementParam
Verification Procedure for NodeB V200R014
1.
Run the NodeB MML command DSP BRD to query the status of the USCU board
and status of the GPS receiver. In the command output displayed on the LMT, check
whether the USCU board and the GPS receiver are normal.
2.
Run the NodeB MML command DSP GPS to display the information of a GPS
receiver, including receiver position, receiver version, receiver status, and receiver
hardware information. In the command output displayed on the LMT, check whether
the location of the GPS receiver is locked up and whether the operating state of the
GPS receiver is normal.
1.
Run the BSC6900 MML command SET USMLC to deactivate the A-GPS location
service. In this step, deselect the AGPS check box under parameter UE Positioning
Method.
----End
Example
/*Activating A-GPS Based LCS*/
/*Operations on the BSC6900 side*
//Setting the type of clock board to GCGa
SET CLKTYPE:CLKTYPE=GCGa;
//Setting the parameters for the SMLC algorithm
SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-0&OTDOA-0&AGPS-1,
AGPSMethodType=UE_ASSISTED,
UeAssAgpsAssDataSwitch=REFERENCE_TIME_FOR_GPS-1&REFERENCE_LOCATION_FOR_GP
S-1&DGPS_CORRECT-0&GPS_NAVGMODEL-1&GPS_IONOSPHERIC_MODEL-1&GPS_UTC_MODEL1&GPS_ALMANAC-1&GPS_ACQ_ASSIST-1&GPS_REALTIME_INTEGRITY-1,LcsWorkMode=RNC
_CENTRIC;
//Setting the parameters of the GPS receiver
ADD GPS: AGPSRECEIVERID=0, AGPSRECEIVERTYPE=RNC, GCDF=DEG, MTRLGY=MET,
Issue 06 (2013-03-25)

334
RAN14.0
LATITUDE=31243596, LONGITUDE=121590603, ALTITUDE=20;

ADD GPS: AGPSRECEIVERID=1, AGPSRECEIVERTYPE=NODEB, CellId=82, GCDF=DEG,
MTRLGY=MET, LATITUDE=31243596, LONGITUDE=121590603, ALTITUDE=20;
//Activating the specified GPS receiver
ACT GPS: AGPSRECEIVERID=0, ACTTYPE=BOTH;
/*Operations on the NodeB V200R014 side*
SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0;
ADD GPS: SN=0;
MOD GPSPOS: WPOS=USER_CONFIG, LONG=160000000, LAT=80000000, ALT=900;
//Deactivating A-GPS Based LCS
SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-0&OTDOA-0&AGPS-0;
Issue 06 (2013-03-25)

335
RAN14.0
93
Configuring LCS Classified Zones
LCS Classified Zones.
Prerequisites
l

License
Other Prerequisites
The core network (CN) supports this feature.
Context
This feature defines a classified zone. Once the UE enters or exits the zone, the RNC
automatically reports the service area identity (SAI) of the UE.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD UCZ (CME single configuration: UMTS
Global Configuration Express > Area Information Configuration > Classified
Zone Information; CME batch modification center: not supported) to add a classified
zone.

336
RAN14.0

NOTE
l In this step, you need to set the parameters Cn Operator Index, Location Area Code,
Service Area Code, and Classified Zone ID. More than one classified zone can be set for
each operator.
l Before running the ADD UCZ (CME single configuration: UMTS Global Configuration
Express > Area Information Configuration > Classified Zone Information; CME batch
modification center: not supported) command, ensure that Location Area Code and
Service Area Code are configured at the local RNC. Otherwise, the classified zone cannot
be configured.
1.
Initiate Iub interface message tracing on the BSC6900 LMT, as shown in Figure
93-1.
2.
Enable the UE to establish a service of any type. Move the UE from cell A (whose
LAC and SAC are 9513 and 272 respectively) to cell B (whose LAC and SAC are
9514 and 273 respectively), to add cell B to the active set.
If a LOCATION REPORT message is displayed, this feature has been activated.
If the value of the information element (IE) "Cause" in the LOCATION REPORT
message is "User Restriction Start Indication", the UE enters the classified zone.
The SAI of the UE is also contained in the message, as shown in Figure 93-2.
Issue 06 (2013-03-25)

337
RAN14.0
Figure 93-2 LOCATION REPORT message
3.
Remove cell B from the active set by performing a handover or Serving Radio Network
Subsystem (SRNS) relocation.
If a LOCATION REPORT message is displayed, this feature has been activated.
If the cause value of the LOCATION REPORT message is displayed as "User
Restriction End Indication", the UE exits the classified zone. The SAI of the UE
is also contained in the LOCATION REPORT message.
1.
Run the BSC6900 MML command RMV UCZ (CME single configuration: UMTS
Global Configuration Express > Area Information Configuration > Classified
Zone Information; CME batch modification center: not supported) to remove the
classified zone from all operators at the RNC.
----End
Example
//Activating LCS Classified Zone
ADD UCZ: CnOpIndex=0, LAC=9513, SAC=272, CZ=0;
ADD UCZ: CnOpIndex=0, LAC=9514, SAC=273, CZ=1;
//Deactivating LCS Classified Zone
RMV UCZ: CnOpIndex=0, CZ=0;
RMV UCZ: CnOpIndex=0, CZ=1;
Issue 06 (2013-03-25)

338
RAN14.0
94
Configuring LCS over Iur
LCS over Iur.
Prerequisites
l

The following feature has been configured before this feature is activated:
WRFD-020801 Cell ID + RTT Function Based LCS or WRFD-020803 A-GPS Based
LCS.
License
The UE and the neighboring RNC (NRNC) support this feature.
This feature is used only in RNC-CENTRIC mode.
Context
This feature enables Huawei RAN to provide location services (LCS) over the Iur interface,
extending the LCS area. It enables exchange of cell information and GPS assistance information
over the Iur interface.
Procedure
l
NOTE
In this procedure, you need to set the positioning method and add the geographical information about
the cell at the RNC. For cell information exchange over the Iur interface, geographical information
about a neighboring cell must be configured at the NRNC.
1.
Issue 06 (2013-03-25)
339
RAN14.0
3.15 Modifying RNC Parameters in Batches) to set the SMLC algorithm

parameters, In this step, set UE Positioning Method and Location Working
Mode.
2.
Configure cell information exchange over the Iur interface.

a.
Run the BSC6900 MML command ADD UIURCOMMSCCP (CME single

configuration: UMTS Global Configuration Express > RNC Basic
Configuration > Information of IUR Common SCCP Connection; CME
batch modification center: not supported). In this step, set the subrack number
and slot number of the SPU subsystem that processes information exchange on
the BSC6900.
b.
Run the BSC6900 MML command ADD USMLCCELL (CME single

configuration: UMTS Cell Configuration Express > SMLC and IPDL > Cell
SMLC Information; CME batch modification center: not supported) to set the
parameters related to cell location information. The parameters include:
Cell location configuration type
Geographical location information about the antenna:
Cell coverage information:
Cell Antenna Opening and so on
3.
Configure GPS assistance information exchange.

a.
Run the BSC6900 MML command ADD UIURCOMMSCCP (CME single

Configuration > Information of IUR Common SCCP Connection; CME
batch modification center: not supported). In this step, set the subrack number
and slot number of the SPU subsystem that processes information exchange on
the BSC6900.
b.
For GPS information exchange over the Iur interface, run the BSC6900 MML
command ADD GPS (CME single configuration: UMTS Global Configuration
Express > Device Configuration > GPS Reference Receiver; CME batch
modification center: not supported) to add a GPS receiver to the NRNC. In this
step, set GPS type to NRNC_RNC(Nearby RNC), indicating that the GPS
receiver is installed at the NRNC.
NOTE
l If a GPS receiver on the NRNC side is installed on the NodeB, set GPS type to
NRNC_NODEB(NodeB in RNC).
l Before adding a GPS receiver to the NRNC, ensure that the GPS receiver is installed
at the NRNC. Run the BSC6900 MML command ADD GPS (CME single
configuration: UMTS Global Configuration Express > Device Configuration >
GPS Reference Receiver; CME batch modification center: not supported) to add
the GPS receiver. In this step, set GPS type to RNC(Local RNC) (when the GPS
receiver is installed at the RNC) or to NODEB(Local NodeB) (when the GPS
receiver is installed at the NodeB).
c.
Issue 06 (2013-03-25)
If a GPS receiver needs to be configured on the BSC6900 side, run the BSC6900
MML command SET CLKTYPE (CME single configuration: UMTS Global
340
RAN14.0
Configuration Express > Device Configuration > Clock Board Type; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) with
the type of clock board in the BSC6900 set to GCGa.
d.
Run the BSC6900 MML command ACT GPS (CME single configuration:
UMTS GLOBAL Configuration Express > Device Configuration > GPS
Reference Receiver. Set GPS Active Flag to Activated; CME batch
modification center: not supported) to activate the GPS reference receiver.
e.
Optional: Run the BSC6900 MML command ADD

UCELLGPSFRMTIMING (CME single configuration: UMTS Cell
Configuration Express > SMLC and IPDL > Cell GPS Frame Timing; CME
batch modification center: 3.18 Modifying UMTS Cell Parameters in
Batches) to set parameters related to UTRAN GPS cell frame timing
measurement to appropriate values. In this step, set Cell ID and GPS Frame
Timing Active Flag.
1.
Start Iur interface tracing on the BSC6900 LMT, as shown in Figure 94-1.
Figure 94-1 Iur Interface Trace dialog box
2.
Issue 06 (2013-03-25)
Check the information traced over the Iur interface. You can find an information
exchange initiation procedure. In this procedure, the local RNC sends the NRNC an
INFORMATION EXCHANGE INITIATION REQUEST message, in which the
value of Information Type is GPS Information or DGPS. The NRNC sends the
local RNC INFORMATION EXCHANGE INITIATION RESPONSE and
INFORMATION REPORT messages, which contain GPS assistance data, as shown
in Figure 94-2.

341
RAN14.0
Figure 94-2 GPS assistance data carried in the INFORMATION REPORT message
NOTE
You can see INFORMATION EXCHANGE INITIATION REQUEST and

INFORMATION EXCHANGE INITIATION RESPONSE messages only after the
BSC6900 MML command ACT GPS is executed.
Issue 06 (2013-03-25)
3.
Establish a service, and then perform a soft handover over the Iur interface.
4.
Enable the CN to send a LOCATION REPORTING CONTROL message with the

cause "DIRECT".
5.
Check messages traced over the Iur interface. You can find an Information Exchange
Initiation procedure. In this procedure, the local RNC sends the NRNC an
INFORMATION EXCHANGE INITIATION REQUEST message, in which the
value of Information Type is UTRAN Access Point Position with Altitude, as
shown in Figure 94-3. The NRNC sends the local RNC an INFORMATION
EXCHANGE INITIATION RESPONSE message, which contains geographical
information about the neighboring cell over the Iur interface, as shown in Figure
94-4.

342
RAN14.0
Figure 94-3 INFORMATION EXCHANGE INITIATION REQUEST
Figure 94-4 INFORMATION EXCHANGE INITIATION RESPONSE
6.
Issue 06 (2013-03-25)
Check messages traced over the Iur interface. You can find DEDICATED
MEASUREMENT INITIATION REQUEST and DEDICATED
MEASUREMENT INITIATION RESPONSE messages, as shown in Figure
94-5 and Figure 94-6 respectively. In the former message, the value of Dedicated
Measurement Type is Round Trip Time.

343
RAN14.0
Figure 94-5 DEDICATED MEASUREMENT INITIATION REQUEST
Figure 94-6 DEDICATED MEASUREMENT INITIATION RESPONSE
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command DEA GPS (CME single configuration: UMTS
GLOBAL Configuration Express > Device Configuration > GPS Reference
Receiver. Set GPS Active Flag to Deactivated; CME batch modification center: not
supported) to deactivate the GPS receiver. Alternatively, run the BSC6900 MML
command RMV GPS (CME single configuration: UMTS Global Configuration
Express > Device Configuration > GPS Reference Receiver; CME batch
344
RAN14.0
modification center: not supported) to remove the GPS receiver from the NRNC. GPS
information exchange over the Iur interface is thereby disabled.
2.
Run the BSC6900 MML command RMV UIURCOMMSCCP (CME single

Configuration > Information of IUR Common SCCP Connection; CME batch
modification center: not supported) to deactivate LCS over Iur.
----End
Example
/*Activating LCS over Iur*/
//Setting the positioning method
SET USMLC: SmlcMethod=CELLID_RTT-1&OTDOA-0&AGPS-0;
/*Configuring cell information exchange over the Iur interface*/
ADD UIURCOMMSCCP: SRN=0, SN=1;
ADD USMLCCELL: RNCId=29, CellId=1, CellLocCfgType=CELL_ANTENNA, GCDF=DEG,
MTRLGY=MET, AntennaLatitudeDegree=31245560,
MaxAntennaRange=2000, AntennaOrientation=0, AntennaOpening=1200;
/*Configuring GPS assistance information exchange.*/
ADD UIURCOMMSCCP: SRN=0, SN=1;
ADD GPS: AGPSRECEIVERID=0, AGPSRECEIVERTYPE=NRNC_RNC, RNCID=1, GCDF=DEG,
MTRLGY=MET, LATITUDE=31245560, LONGITUDE=121588230, ALTITUDE=21;
SET CLKTYPE: CLKTYPE=GCGa;
ACT GPS: AGPSRECEIVERID=0, ACTTYPE=BOTH;
ADD UCELLGPSFRMTIMING: CellId=1, StartFlag=ACTIVE;
//Deactivating LCS over Iur
RMV GPS: AGPSRECEIVERID=0;
Issue 06 (2013-03-25)

345
RAN14.0
95
Configuring Iupc Interface for LCS

Service
Iupc Interface for LCS service.
Prerequisites
l
IP interface boards of the BSC6900 support this feature.
A Stand-Alone SMLC (SAS) is configured.

WRFD-020801 Cell ID + RTT Function Based LCS has been configured if the
operator employs the Cell ID+RTT algorithm.
WRFD-020803 A-GPS Based LCS has been configured if the operator employs the
A-GPS algorithm.
License
Other Prerequisites
The UE supports at least one of the following positioning methods:
UE-assisted CELLID+RTT
UE-based A-GPS
UE-assisted A-GPS
The global data is configured by performing the following procedure:
1.
Configuring the Basic Data
2.
Configuring the OSP and DSP
3.
Configuring the Area Information
4.
Configuring the M3UA Local and Destination Entities
Physical layer data and data link layer data are configured by performing the following
procedure:
Issue 06 (2013-03-25)

346
RAN14.0
1.
Configuring the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/
GOUc Board
2.
Configuring the Physical Layer and Data Link Layer for the PEUa Board
3.
Configuring the Physical Layer and Data Link Layer for the POUa/POUc Board
4.
Configuring the User Plane of the Iub Interface (over ATM)
Context
Only IP transmission can be applied between the BSC6900 and the SAS. The transport network
layer data on the Iupc interface needs to be configured at the BSC6900. When the BSC6900 is
connected to multiple SASs through IP transmission, you need to configure this feature on each
Iupc interface. One BSC6900 can be connected to a maximum of four SASs simultaneously.
NOTE
Before configuring the Iupc interface data, familiarize yourself with Protocol Structure and Links on the
Iupc Interface.
Procedure
l
1.
Run the BSC6900 MML command ADD N7DPC (CME single configuration: UMTS
Global Configuration Express > Signaling Configuration > DSP Of DPU; CME
batch modification center: not supported) to add the destination signaling point (DSP)
data that corresponds to the SAS.
2.
Run the BSC6900 MML commands ADD M3LE (CME single configuration: UMTS
Global Configuration Express > Signaling Configuration > M3UA Local
Entity; CME batch modification center: not supported) and ADD M3DE (CME single
configuration: UMTS Global Configuration Express > Signaling Configuration >
M3UA Destination Entity; CME batch modification center: not supported) to add
the M3UA local entity (M3LE) and the M3UA destination entity (M3DE) that
correspond to the SAS respectively.
3.
Run the BSC6900 MML command ADD SCTPLNK (CME single configuration:
IUPC Configuration Express > IP Transport > SCTP Link; CME batch
modification center: not supported) to add an SCTP link. To add multiple SCTP links,
run this command for each SCTP link to be added.
If Signalling link mode is set to Server at the SAS, set Signalling link mode to
CLIENT at the BSC6900. If Signalling link mode is set to CLIENT at the SAS,
set Signalling link mode to Server at the BSC6900.
Set Application type to M3UA.
4.
Run the BSC6900 MML command ADD M3LKS (CME single configuration: IUPC
Configuration Express > IP Transport > M3UA Link Set; CME batch modification
center: not supported) to add an M3UA link set.
If Local entity type is set to M3UA_IPSP, set Work mode of the M3UA link set
to M3UA_IPSP.
If Local entity type is set to M3UA_ASP and Destination entity type is set to
M3UA_SP, set Work mode to M3UA_IPSP. If Local entity type is set to
M3UA_ASP and Destination entity type is not set to M3UA_SP, set Work
mode to M3UA_ASP.
Issue 06 (2013-03-25)

347
RAN14.0
5.
Run the BSC6900 MML command ADD M3RT (CME single configuration: IUPS
Configuration Express > IP Transport > M3UA Route; CME batch modification
center: not supported) to add an M3UA route.
6.
Run the BSC6900 MML command ADD M3LNK (CME single configuration: IUPC
Configuration Express > IP Transport > M3UA Link Set; CME batch modification
center: not supported) to add an M3UA link. To add more M3UA links, run this
command repeatedly.
7.
Run the BSC6900 MML command ADD USAS (CME single configuration: UMTS
Global Configuration Express > Radio Basic Data Configuration > Stand-alone
SMLC; CME batch modification center: not supported) to add the SAS.
8.
3.15 Modifying RNC Parameters in Batches) to enable SAS-CENTRIC positioning
based on CELLID + RTT or AGPS. For details, see 90 Configuring Cell ID + RTT
Function Based LCS or 92 Configuring A-GPS Based LCS.
1.
Perform the verification procedures by referring to 90 Configuring Cell ID + RTT

1.
Perform the deactivation procedures by referring to 90 Configuring Cell ID + RTT

----End
Example
//Activating Iupc Interface for LCS Service
//Adding the DSP data that corresponds to the SAS
ADD N7DPC:DPX=4, SPDF=WNF, DPC=8345, STP=OFF, SLSMASK=B0000,
NEIGHBOR=YES, NAME="SAS", DPCT=IUPC, PROT=ITUT, BEARTYPE=M3UA, SPX=4;
//Adding the M3LE that corresponds to the SAS
ADD M3LE:LENO=0, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME="IUPC",
SPX=4;
//Adding the M3DE that correspond to the SAS
ADD M3DE:DENO=0, LENO=0, DPX=4, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295,
NAME="IUPC";
//Adding an SCTP link
ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=0, MODE=SERVER, APP=M3UA,
LOCIP1="10.10.10.10", PEERIP1="10.10.11.11", PEERPN=3000, LOGPORTFLAG=NO,
VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//Adding an M3UA link set
ADD M3LKS: SIGLKSX=0, DENO=0, NAME="IUPC";
//Adding an M3UA route
ADD M3RT: DENO=0, SIGLKSX=0, NAME="IUPC";
//Adding an M3UA link
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=0, SCTPLNKN=0, NAME="IUPC";
//Adding the SAS
ADD USAS: CnOpIndex=0, SasId=0, Dpx=4;
//Setting SMLC-related parameters
SET USMLC: SmlcMethod=CELLID_RTT-1, AGPSMethodType=UE_ASSISTED,
LcsWorkMode=SAS_CENTRIC;
Issue 06 (2013-03-25)

348
RAN14.0
96
Configuring Push to Talk
Push to Talk. (This feature cannot be configured using the CME. )
Prerequisites
l

WRFD-010610 HSDPA Introduction Package, WRFD-010612 HSUPA Introduction
Package, WRFD-010688 Enhanced CELL_FACH, and WRFD-010636 SRB over
HSUPA.
License
NOTE
The license must be activated by performing the following operation first:

Run the BSC6900 MML command SET LICENSE to set Push To Talk (per PTT Active User) to
Other Prerequisites
This feature requires support from the UE and CN.
Context
This feature is a part of the end-to-end push to talk (PTT) solution. Implementation of the PTT
solution requires support from the UE, RAN, CN, and PTT server. Huawei RAN can identify
PTT services and implement techniques to reduce the delay in setting up calls of PTT services.
Procedure
l
Issue 06 (2013-03-25)

349
RAN14.0
1.

select the CFG_PTT_SWITCH check box under the parameter Channel
2.
Run the BSC6900 MML command SET UFRC. In this step, set PTT ARP
Priority, PTT ARP Preemption Capability, PTT ARP Preemption
Vulnerability, and PTT ARP Queuing Allowed to the same values as those of ARP
(allocation/retention priority) properties Priority Level, Preemption Capability,
Preemption Vulnerability, and Queuing Allowed. The ARP properties are carried in
the RNCAP_RAB_ASSIGNMENT_REQ message sent by the CN for PTT services
during the second RAB assignment procedure. In addition, set PTT HSUPA TTI
type to EDCH_TTI_10ms.
3.
Run the BSC6900 MML command SET URRCTRLSWITCH to turn on the

switches PTT_EARLY_TRANS_SWITCH and PTT_SPEC_LI_SWITCH. In this
step, clear the PTT_EARLY_TRANS_SWITCH_OFF and
PTT_SPEC_LI_SWITCH_OFF check boxes under the parameter Process switch.
4.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable PTT

UEs to switch to the DCH for access reattempts when HSPA resources are insufficient.
In this step, select the RESERVED_SWITCH_0_BIT19 check box under the
parameter CORRM Algorithm Reserved Switch 0.
5.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, select
HSUPA(UL_EDCH,DL_DCH) from the Type of Channel Preferably Carrying
Signaling RB drop-down list.
1.
Initiate Iu-interface message tracing on the BSC6900 LMT and check whether the CN
has sent an RNCAP_RAB_ASSIGNMENT_REQ message.
NOTE
The RNC identifies PTT services based on six information elements (IEs) in the
RNCAP_RAB_ASSIGNMENT_REQ message. The six IEs are Traffic Class, Signaling Indication,
Priority Level, Preemption Capability, Preemption Vulnerability, and Queuing Allowed. Services
identified as PTT services are allocated a rate of 8 kbit/s.
1.

clear the CFG_PTT_SWITCH check box under the parameter Channel
----End
Example
//Activating Push to Talk
SET UCORRMALGOSWITCH:CfgSwitch=CFG_PTT_SWITCH-1;
SET UFRC:PTTArpPriorityLevel=1, PTTArpPreEmptCap=TRIGGER,
PTTArpPreEmptVuln=NOT_PRE_EMPTABLE, PTTArpQueuingAllowed=ALLOWED,
PTTHsupaTti=EDCH_TTI_10ms;
SET
URRCTRLSWITCH:PROCESSSWITCH=PTT_EARLY_TRANS_SWITCH_OFF-0&PTT_SPEC_LI_SWIT
CH_OFF-0;
SET UCORRMALGOSWITCH:ReservedSwitch0=RESERVED_SWITCH_0_BIT19-1;
SET UFRCCHLTYPEPARA:SrbChlType=HSUPA;
//Deactivating Push to Talk
SET UCORRMALGOSWITCH:CfgSwitch=CFG_PTT_SWITCH-0;
Issue 06 (2013-03-25)

350
RAN14.0
97
Configuring HSUPA Introduction

Package
HSUPA Introduction Package.
Prerequisites
l
The NBBI and the NULP do not support this feature.

License
Other Prerequisites
The UE should have HSUPA capability.
Context
This feature enables the system to process HSUPA services, therefore increasing the uplink rate
and system throughput. It provides basic functions of HSUPA.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD UCELLHSUPA (CME single

Configuration of HSUPA in Cell; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches) to add HSUPA functions of a cell.
2.
Run the BSC6900 MML command ACT UCELLHSUPA (CME single

Configuration of HSUPA in Cell. Set Cell HSUPA state to Activated; CME batch
modification center: No supported) to activate the HSUPA function of the cell.
351
RAN14.0
3.
Configure Iub transport for HSUPA.

In an ATM network:
a.
Run the BSC6900 MML command ADD ATMTRF (CME single

configuration: NodeB Configuration Express > IUB_RNC > ATM
Transport > ATM Traffic Record; CME batch modification center: not
supported) to configure new records of ATM traffic based on network
planning requirements.
b.
Run the BSC6900 MML command LST TRMMAP (CME single

configuration: UMTS Global Configuration Express > Transmission
Resources Configuration > Transport Resource Mapping) to query the
transmission resource mapping.
c.
Run the BSC6900 MML command ADD AAL2PATH (CME single

Transport > AAL2 Path; CME batch modification center: not supported) to
set associated parameters according to the network plan. TX traffic record
index and RX traffic record index of the AAL2 path to be added must be
the same as those set in the ADD ATMTRF (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > ATM
Traffic Record; CME batch modification center: not supported) command.
In addition, AAL2 Path Type should be set according to the mapping
between service types and AAL paths.
d.
Run the NodeB MML command ADD AAL2PATH (CME single

configuration: NodeB Configuration Express > IUB_NodeB > ATM
Transport Layer > AAL2Path > AAL2 Path; CME batch modification
center: not supported) to configure an AAL2 path for HSDPA based on
network planning requirements.
In an IP network:
a.
Run the BSC6900 MML command LST ADJMAP (CME single

Transport > Adjacent Node Mapping) to query whether resource
management mapping is configured for the adjacent node.
If configured, check the TRMMAP index of the adjacent node.
If not configured, run the BSC6900 MML command LST TRMMAP
(CME single configuration: UMTS Global Configuration Express >
Transmission Resources Configuration > Transport Resource
Mapping) to query the default TRMMAP ID used by the adjacent node
based on the settings of Interface Type and Transport Type. For
example, if Interface Type is set to Iub Interface, then TRMMAP ID
is 1.
b.
Run the BSC6900 MML command LST TRMMAP (CME single

Resources Configuration > Transport Resource Mapping) to check
whether the IP path mapping to the HSDPA service is configured according
to the TRMMAP ID used by the adjacent node.
If configured, no further action is required.
If not configured, run the BSC6900 MML command ADD IPPATH
(CME single configuration: NodeB Configuration Express >
IUB_RNC > IP Transport > IP Path; CME batch modification center:
not supported) to configure the IP path mapping to the HSUPA service.
Issue 06 (2013-03-25)

352
RAN14.0

NOTE
To ensure that HSUPA services can be set up successfully, HSUPA services must be mapped to the
corresponding AAL2 paths or IP paths. To avoid the affect on ongoing services, you can add new
AAL2 paths or IP paths.
1.
Ensure that the HSUPA function of the cell is activated.

Run the BSC6900 MML command DSP UCELL to verify that the HSUPA function
of the cell is activated.
2.
Establish a PS service.
The IE E-DCH FDD information in the RL SETUP message on the Iub interface and
the IE rb-mappinginfo in the RRC_RB_SETUP message on the Uu interface should
indicate that the service has been set up and carried on the E-DCH.
1.
Run the BSC6900 MML command DEA UCELLHSUPA (CME single

Configuration of HSUPA in Cell. Set Cell HSUPA state to Deactivated; CME batch
modification center: No supported) to deactivate the HSUPA function of the cell.
2.
Run the BSC6900 MML command RMV UCELLHSUPA (CME single

Configuration of HSUPA in Cell; CME batch modification center: not supported)
to remove the HSUPA functions of a cell.
----End
Example
//Activating HSUPA Introduction Package
ADD UCELLHSUPA: CellId=111;
ACT UCELLHSUPA: CellId=111;
//Verifying HSUPA Introduction Package
DSP UCELL: DSPT=BYCELL, CellId=111;
//Deactivating HSUPA Introduction Package
DEA UCELLHSUPA: CellId=111;
RMV UCELLHSUPA: CellId=111;
Issue 06 (2013-03-25)

353
RAN14.0
98
Configuring HSUPA Admission Control

WRFD-01061202 HSUPA Admission Control.
Prerequisites
l

The feature WRFD-010612 HSUPA Introduction Package must be configured before
License
Context
This feature enables HSUPA and R99 services to simultaneously access the network by using
the remaining uplink cell load and other resources, improving the utilization of system resources
and ensuring QoS of admitted users.
Procedure
l
1.
Issue 06 (2013-03-25)
Activating Power Resource Admission

a.

UMTS Cell Parameters in Batches). In this step, select an uplink Call
Admission Control (CAC) algorithm through the parameter Uplink CAC
algorithm switch and a downlink CAC algorithm through the parameter
Downlink CAC algorithm switch.
b.
For HSUPA services, run the BSC6900 MML command MOD

UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME
354
RAN14.0

Batches). In this step, select the corresponding admission algorithm switches
from the Cell CAC algorithm switch drop-down list, such as
HSUPA_PBR_MEAS(HSUPA PBR Meas Algorithm),
HSUPA_EDCH_RSEPS_MEAS(HSUPA EDCH RSEPS Meas Algorithm),
and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control
Algorithm).
c.
2.
3.

Modifying UMTS Cell Parameters in Batches) to set power resource
admission parameters.
Activating NodeB Credit Resource Admission

a.

set CAC algorithm switch to NODEB_CREDIT_CAC_SWITCH(NodeB
Credit CAC Switch).
b.

UMTS Cell Parameters in Batches). In this step, set Cell CAC algorithm
switch to CRD_ADCTRL(Credit Admission Control Algorithm) to turn on
the cell-oriented credit resource admission switch.
c.

Modifying UMTS Cell Parameters in Batches). In this step, set the NodeB
credit resource admission parameters Ul handover credit reserved SF and Dl
handover credit and code reserved SF to appropriate values.
Activating Iub Resource Admission

Iub resource admission is unconditionally performed and does not need to be activated.
NOTE
Run the BSC6900 MML command MOD IPPATH (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > IP Path; CME batch modification
center: not supported) or MOD AAL2PATH (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > AAL2 Path; CME batch
modification center: not supported) to modify the Iub bandwidth.
Issue 06 (2013-03-25)
1.
UE1 and UE2 are in idle state and camp on CELL_A11. CELL_A11 supports HSUPA.
2.
3.
Run the BSC6900 MML command MOD UCELLCAC to set the maximum number
of HSUPA users supported by CELL_A11 to 1.
4.
Establish an HSUPA PS service on UE1, and then check the rb-mappinginfo

information element in the RRC_RB_SETUP message traced over the Uu interface.
The value of ul-TrCH-Type is e-dch.
355
RAN14.0
5.
Establish an HSUPA PS service on UE2, and then check the rb-mappinginfo

information element in the RRC_RB_SETUP message traced over the Uu interface.
The value of rrc-Stateinditator is CELL_DCH.
6.
Release all PS services.
7.
Run the BSC6900 MML command MOD UCELLCAC to set Maximum HSUPA
user number of CELL_A11 to 20.
8.
Establish an HSUPA PS service on UE1 and UE2 respectively.

Expected result: An HSUPA PS service is successfully established on UE1 and UE2
respectively.
9.
Run the following command to check whether Iub resource admission is activated.
Run the BSC6900 MML command DSP IPPATH or DSP AAL2PATH to check
whether any bandwidth is occupied.
1.
To disable Power Resource Admission, do as follows:

Algorithm Switches; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches) to set the cell-oriented power resource admission
switches (Uplink CAC algorithm switch and Downlink CAC algorithm
switch) to ALGORITHM_OFF.
2.
3.
To disable NodeB Credit Resource Admission, do as follows:

a.

deselect the NodeB credit resource admission switch
NODEB_CREDIT_CAC_SWITCH(NodeB Credit CAC Switch) from the
CAC algorithm switch drop-down list.
b.

UMTS Cell Parameters in Batches). In this step, deselect the cell-oriented
credit resource admission switch CRD_ADCTRL(Credit Admission Control
Algorithm) from the Cell CAC algorithm switch drop-down list.
Deactivating Iub Resource Admission

Iub resource admission is unconditionally performed and does not need to be
deactivated.
----End
Example
NBMCacAlgoSwitch=HSUPA_UU_ADCTRL-1&HSUPA_PBR_MEAS-1&HSUPA_EDCH_RSEPS_MEAS
-1;
MOD UCELLCAC: CellId=11, MaxUlTxPowerforConv=24, MaxUlTxPowerforInt=24,
MaxHsupaUserNum=20;
Issue 06 (2013-03-25)

356
RAN14.0

MOD UCELLCAC: CellId=11, UlHoCeResvSf=SF16, DlHoCeCodeResvSf=SF32;
Issue 06 (2013-03-25)

357
RAN14.0
99
Configuring HSUPA Power Control
WRFD-01061203 HSUPA Power Control.
Prerequisites
l

The features WRFD-010612 HSUPA Introduction Package must be configured before
License
Context
This feature increases the system power efficiency, reduces the uplink and downlink
interference, and improves the system capacity by controlling the power on HSUPA physical
channels.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the NodeB MML command SET MACEPARA (CME single configuration:
Parameters > MAC Parameters > MACEPARA; CME batch modification center:
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set E-AGCH
HPC Parameters, E-RGCH HPC Parameters for Service Radio Links Set, and
E-HICH HPC Parameters for Service Radio Links Set to YES.
2.
358
RAN14.0
HPC Mode, E-RGCH HPC Mode for Service Radio Links Set, and E-HICH HPC
Mode for Service Radio Links Set to FOLLOW_TPC.
3.
Power Offset(0.25dB), E-RGCH Power Offset for Service Radio Links Set
(0.25dB), E-HICH Power Offset for Service Radio Links Set(0.25dB), and EHICH Power Offset for Single Radio Link(0.25dB) to appropriate values according
to the network plan.
4.
Run the BSC6900 MML command MOD UTYPRABHSUPAPC (CME single

configuration: UMTS Radio Global Configuration Express > Typical Service
Configuration > Typical RAB HSUPA Power Control Parameters; CME batch
modification center: not supported) to modify power control parameters related to
HSUPA services. In this step, set E-RGCH 2-Index-Step Threshold to 9 and ERGCH 3-Index-Step Threshold to 12.
5.
Run the BSC6900 MML command MOD UTYPRABOLPC (CME single

Configuration > Typical RAB OLPC Parameters; CME batch modification center:
not supported). In this step, change the number of target retransmissions for large and
small retransmissions related to HSUPA services according to the network plan.
1.
On the BSC6900 LMT, open the Monitor page. Then, double-click Connection
Performance Monitoring under UMTS Monitoring. In the displayed dialog box,
select OLPC and specify the IMSI.
2.
Use an HSUPA-capable UE to set up a PS service over the enhanced DCH (E-DCH).
3.
Move the UE between the cell center and the cell edge.
4.
View the monitor items related to the number of E-DCH retransmissions in the
OLPC area. The values of the monitor items change with UE movement.
5.
View the power change on each HSUPA channel.

If static power control is used, the channel power remains unchanged.
If dynamic power control is used:
When the UE is moving away from the antenna, the transmit power of the EAGCH increases.
When the UE is moving towards the antenna, the transmit power of the EAGCH decreases.
1.
----End
Example
//Activating HSUPA Power Control
//Setting the power control mode
SET MACEPARA: LOCELL=111, EAGCHPCPARA=YES, SERGCHPCPARA=YES,
SEHICHPCPARA=YES;
SET MACEPARA: LOCELL=111, EAGCHPCMOD=FOLLOW_TPC, SERGCHPCMOD=FOLLOW_TPC,
SEHICHPCMOD=FOLLOW_TPC;
SET MACEPARA: LOCELL=111, EAGCHPWROFFSET=142, SERGCHPWROFFSET=100,
Issue 06 (2013-03-25)

359
RAN14.0
SEHICHPWROFFSET=96, SRLEHICHPWROFFSET=88;
//Modifying power control parameters related to HSUPA services
MOD UTYPRABHSUPAPC: RabIndex=48, SubflowIndex=0, TrchType=TRCH_EDCH_2MS,
Ul16QamInd=FALSE, UlL2EnhanceInd=FALSE, EdPwrInterpolationInd=FALSE,
ERgch2IndStpThs=9, ERgch3IndStpThs=12, UlEcBoostingInd=FALSE;
//Changing the number of target retransmissions for large and small
retransmissions related to HSUPA services
MOD UTYPRABOLPC: RabIndex=48, SubflowIndex=0, TrchType=TRCH_EDCH_2MS,
DelayClass=1, EdchTargetLittleRetransNum=12,
EdchTargetLargeRetransNum=20;
Issue 06 (2013-03-25)

360
RAN14.0
100
Configuring HSUPA Mobility

Management
WRFD-01061204 HSUPA Mobility Management.
Prerequisites
l

License
Context
This feature enables an HSUPA-capable UE to be handed over to an R99 cell or another HSUPA
cell.
This feature also enables an HSUPA-capable UE to change cells with a small probability of
service interruption.
Procedure
l
1.
The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers

are the same for HSUPA users and R99 users. For the activation procedures for
configuring HSUPA Mobility Management, see the following sections:
Issue 06 (2013-03-25)

361
RAN14.0

2.
None.
3.
----End
Issue 06 (2013-03-25)

362
RAN14.0
101
Configuring HSUPA DCCC
WRFD-01061208 HSUPA DCCC.
Prerequisites
l

The features WRFD-010612 HSUPA Introduction Package must be configured before
License
Context
HSUPA DCCC can dynamically adjust the minimum spreading factor (SF) code of HSUPA
based on the user throughput and flexibly switch the UE state based on the user traffic, which
improves the Channel Element (CE) resource utilization and system efficiency.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, select DRA_HSUPA_DCCC_SWITCH from
the Dynamic Resource Allocation Switch drop-down list.
2.
Optional: If the NodeB does not enable dynamic CE, run the BSC6900 MML
command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB
Algorithm Parameters; CME batch modification center: 3.16 Modifying Logical
363
RAN14.0
3.
NodeB Parameters in Batches). In this step, set HSUPA Credit Consume Type to
MBR.
Optional: Run the BSC6900 MML command SET UDCCC (CME single
configuration: UMTS Radio Global Configuration Express > Dynamic Channel
Control Parameter Configuration > RNC Oriented DCCC Algorithm
Batches). In this step, select RATE_UP_AND_DOWN_ON_EDCH from the
HSUPA DCCC Strategy drop-down list so that the data rate of HSUPA services on
the EDCH can increase or decrease.
NOTE
After the preceding optional step is performed, the data rate of HSUPA services on the EDCH can
increase or decrease as required. If the data rate of HSUPA services on the EDCH is expected to
increase only, select RATE_UP_ONLY_ON_EDCH from the HSUPA DCCC Strategy dropdown list.
4.
Optional: Run the BSC6900 MML command SET UEDCHRATEADJUSTSET

Dynamic Channel Control Parameter Configuration > HSUPA Rate Adjust
Set; CME batch modification center: 3.15 Modifying RNC Parameters in
Batches). In this step, set HSUPA Uplink Rate Adjust Set to a data rate set for rate
adjustment by the HSUPA DCCC algorithm.
NOTE
The preceding optional step sets the available data rate set of the HSUPA DCCC algorithm. After
the step is performed, HSUPA services can be of any data rate in the data rate set by using the HSUPA
DCCC algorithm.
1. On the BSC6900 LMT, display the Monitor page. In the Monitor Navigation
Tree, double-click UMTS Monitoring > Connection Performance Monitoring.
Select UL Throughput Bandwidth and DL Throughput Bandwidth respectively
from the Monitor Item drop-down list to create two monitoring tasks.
2. Make the UE establish an HSUPA Best Effort (BE) service. After the service is
established, layer 3 of the RNC sends an uplink throughput measurement control
message to layer 2.
3. Upload a large file for a period of time. Then, view the RRC_RB_RECFG message
on the Uu interface and check that the data rate increases. In UL Throughput
Bandwidth of Connection Performance Monitoring, the bandwidth increases.
4. Stop the data upload and wait for a period of time. Then, view the RRC_RB_RECFG
message on the Uu interface and check that the data rate decreases. In UL Throughput
Bandwidth of Connection Performance Monitoring, the bandwidth decreases.
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single
Parameters in Batches). In this step, deselect DRA_HSUPA_DCCC_SWITCH
from the Dynamic Resource Allocation Switch drop-down list.
----End
Example
//Activating HSUPA DCCC
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1;
Issue 06 (2013-03-25)

364
RAN14.0
MOD UNODEBALGOPARA: NodeBName="NodeB1", HsupaCeConsumeSelection=MBR;

SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH;
EdchRateAdjustSet=RATE_8KBPS-0&RATE_16KBPS-0&RATE_32KBPS-0&RATE_64KBPS-0&
RATE_128KBPS-1&RATE_144KBPS-0&RATE_256KBPS-1&RATE_384KBPS-0&RATE_608KBPS1&RATE_1280KBPS-0&RATE_2048KBPS-0&RATE_2720KBPS-0&RATE_5440KBPS-0&RATE_11
480KBPS-0;
//Deactivating HSUPA DCCC
SET UCORRMALGOSWITCH: DraSwitch= DRA_HSUPA_DCCC_SWITCH-0;
Issue 06 (2013-03-25)

365
RAN14.0
102
Configuring 20 HSUPA Users per

Cell
WRFD-01061211 20 HSUPA Users per Cell.
Prerequisites
l

License
Context
This feature enables a single HSUPA cell to serve a maximum of 20 HSUPA users
simultaneously. After the maximum is reached, the cell attempts to establish services on DCHs
to accommodate additional users.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, deselect HSDPA_UU_ADCTRL(HSDPA UU
Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU
Load Admission Control Algorithm) from the drop-down list of Cell CAC
algorithm switch.
2.
366
RAN14.0

Cell Parameters in Batches) to set Maximum HSUPA user number to 20.
l
1.
On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance

Monitoring in the Monitor Navigation Tree pane. In the displayed Cell
Performance Monitoring dialog box, set Monitor Item to Cell User Number.
2.
Use UEs to access the cell one by one. Then, make UEs establish PS services, for
example, upload files through FTP.
Expected result: Each UE establishes PS services successfully.
If the number of UEs is less than or equal to 20, uplink services are carried on
HSUPA channels and downlink services are carried on HSDPA channels.
If the number of UEs is greater than 20, HSPA services of the excessive UEs are
carried on R99 channels.
3.
View the maximum number of users indicated by the counter

VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
The 20 HSUPA users referred to in this feature are of the SRB Over HSPA type.
1.
----End
Example
//Disabling the admission control function in an HSPA cell on the Uu
interface
NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0;
//Setting the maximum number of HSUPA users supported by the cell to 20
MOD UCELLCAC: CellId=111, MaxHsupaUserNum=20;
Issue 06 (2013-03-25)

367
RAN14.0
103 Configuring HSUPA Iub Flow Control in Case of Iub

Congestion
103
Configuring HSUPA Iub Flow
Control in Case of Iub Congestion
WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion.
Prerequisites
l

The feature WRFD-010612 HSUPA Introduction Package has been configured before
License
Context
By monitoring Iub transmission resources, this feature dynamically adjusts the uplink Uu
throughput and thereby greatly improves resource utilization.
Procedure
l
l
Issue 06 (2013-03-25)
1.

RNC Parameters in Batches). In this step, select the
NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter
PROCESSSWITCH.
2.
Run the BSC6900 MML command SET UDPUCFGDATA (CME single

configuration: UMTS Radio Global Configuration Express > DPU Data
Configuration > DPU Configuration Parameters; CME batch modification center:
3.15 Modifying RNC Parameters in Batches). In this step, set HsupaTnlSwitch to
ON(ON).
368
RAN14.0
103 Configuring HSUPA Iub Flow Control in Case of Iub

Congestion
NOTE
l UE is in idle mode and supports the HSUPA and HSDPA functions.

l The bandwidth between the BSC6900 and the NodeB is 1 MHz.
1.
UE is of HSUPA category 5 and is correctly registered at the HLR. That is, traffic
class is set to background, the maximum bit rates are set to UL 2048 kbit/s and DL
7200 kbit/s.
2.
On the BSC6900 LMT, start Monitoring UL Throughput and Bandwidth.
3.
The uplink throughput of UE is stable and is about 1M.
1.

3.15 Modifying RNC Parameters in Batches). In this step, set HsupaTnlSwitch to
OFF(OFF).
----End
Example
SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
SET UDPUCFGDATA: HsupaTnlSwitch=ON;
SET UDPUCFGDATA: HsupaTnlSwitch=OFF;
Issue 06 (2013-03-25)

369
RAN14.0
104 Configuring HSUPA E-AGCH Power Control (Based on

CQI or HS-SCCH)
104
Configuring HSUPA E-AGCH Power

Control (Based on CQI or HS-SCCH)
WRFD-01061401 HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH).
Prerequisites
l
This feature does not depend on hardware.

WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA
Introduction Package.
License
Context
This feature enables the RAN to use the channel quality indicator (CQI) and HS-SCCH
information reported by UEs as a reference, therefore effectively reducing the power
consumption of the E-AGCH.
Procedure
l
1.
3.17 Modifying Physical NodeB Parameters in Batches) to set Mac-e parameters
with the following parameter settings:
E-AGCH HPC Parameters is set to YES(YES).
E-AGCH HPC Mode is set to CQI_BASED(Tx Pwr Ctr based on CQI) or
HSSCCH_BASED(Tx Pwr Ctr based on HS-SCCH).
Issue 06 (2013-03-25)

370
RAN14.0
104 Configuring HSUPA E-AGCH Power Control (Based on

CQI or HS-SCCH)
E-AGCH Power Offset(0.25dB), E-AGCH Max Power(0.1dB), and E-AGCH

Min Power(0.1dB) are set to values that comply with the data plan.
l
1.
Use an HSUPA-capable UE to perform PS services over the E-DCH.
2.
Move the UE and observe power changes on each channel carrying HSUPA services.
Expected result:
When the UE moves away from the antenna, the transmit power of the E-AGCH
increases.
When the UE moves towards the antenna, the transmit power of the E-AGCH
decreases.
1.
HPC Parameters to NO(NO).
----End
Example
SET MACEPARA: SCHEDULEPARA=NO, EAGCHPCPARA=YES, EAGCHPCMOD=CQI_BASED,
EAGCHPWROFFSET=100, MAXAGCHPOWER=100,
MINAGCHPOWER=-200, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO,
NSEHICHPCPARA=NO;
SET MACEPARA: SCHEDULEPARA=NO, EAGCHPCPARA=NO, SERGCHPCPARA=NO,
NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
Issue 06 (2013-03-25)

371
RAN14.0
105
Configuring HSUPA 2ms TTI
WRFD-01061403 HSUPA 2ms TTI.
Prerequisites
l
Dependencies on BSC6900 Hardware
This feature does not depend on the BSC6900 hardware.
Dependencies on NodeB Hardware
The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board, EBOI
board, EDLP or EDLPd board.
The BBU3806 is configured with the EBBC or EBBCd board.
The BBU3900 is configured with the WBBPb,WBBPd or WBBPf board.

License
Other Prerequisites
The UE should have the capability of HSUPA Category 2, 4, 6, 7, 8, 9.
Context
This feature enables a single user to obtain a higher uplink throughput and a shorter delay.
Procedure
l
1.
Issue 06 (2013-03-25)

372
RAN14.0

Mapping Strategy Switch.
2.
Rate Threshold of Streaming Services on 2ms TTI of HSUPA and Ratethreshold
of BE on 2ms TTI of HSUPA to appropriate values based on the network plan.
3.
Configure SRB over HSPA by referring to 119 Configuring SRB over HSUPA.
4.
Optional: If the single-user peak-rate improvement algorithm of HSUPA 2 ms TTI

is to be enabled, Run the BSC6900 MML command SET UCORRMPARA (CME
Connection_Oriented RRM Switch Configuration > the connection-oriented
algorithm parameters of an RNC; CME batch modification center: 3.15 Modifying
PERFENH_HSUPA_TTI2_ENHANCE_SWITCH check box under the parameter
Performance Enhancement Switch.
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify that

the MAP_HSUPA_TTI_2MS_SWITCH check box is selected.
2.
Use an HSPA-capable UE to establish an HSUPA service. If the

RRC_RB_SETUP message shown in Figure 105-1 is traced on the Uu interface, an
HSUPA service with 2 ms TTI has been set up on the E-DCH.
Figure 105-1 HSUPA service with 2 ms TTI carried on the E-DCH
Issue 06 (2013-03-25)
1.

Mapping Strategy Switch.
2.
Optional: If the single-user peak-rate improvement algorithm of HSUPA 2 ms TTI

is to be deactivated, Run the BSC6900 MML command SET UCORRMPARA (CME
RNC Parameters in Batches). In this step, deselect the
373
RAN14.0
PERFENH_HSUPA_TTI2_ENHANCE_SWITCH check box under the parameter

Performance Enhancement Switch.
----End
Example
//Activating HSUPA 2ms TTI
SET UFRC: StreamHsupa2msTtiRateThs=D64, BeHsupa2msTtiRateThs=D64;
//Configuring SRB over HSPA
SET UFRCCHLTYPEPARA: SrbChlType=HSPA;
//Configuring single-user peak-rate improvement algorithm of HSUPA 2 ms
TTI
SET UCORRMPARA: PerfEnhanceSwitch=PERFENH_HSUPA_TTI2_ENHANCE_SWITCH-1;
//Deactivating HSUPA 2ms TTISET UCORRMALGOSWITCH:
MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0;
//Deactivating single-user peak-rate improvement algorithm of HSUPA 2 ms
TTI
SET UCORRMPARA: PerfEnhanceSwitch=PERFENH_HSUPA_TTI2_ENHANCE_SWITCH-0;
Issue 06 (2013-03-25)

374
RAN14.0
106
Configuring HSUPA 2 ms/10 ms TTI

Handover
WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover.
Prerequisites
l
The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI,
EULP, or EULPd board.
The BBU3900 is configured with the WBBPb ,WBBPd or WBBPf board.

The feature WRFD-010614 HSUPA Phase 2 has been configured before this feature is
activated.
License
Context
This feature enables smooth handovers for HSUPA users between 2 ms TTI capable cells and
10 ms TTI capable cells, aiming to maximize HSUPA resource utilization. When this feature is
used, the factors such as the radio environment, CE resource usage, and user throughput rate are
considered.
Procedure
l
This feature is license controlled. It takes effect after its license is activated.
Issue 06 (2013-03-25)

375
RAN14.0
----End
Example
None
Issue 06 (2013-03-25)

376
RAN14.0
107
Configuring HSUPA 5.74Mbps per

User
WRFD-01061405 HSUPA 5.74Mbps per User.
Prerequisites
l
The BTS3812E , BTS3812A, and BTS3812AE should be configured with the EBBI,
EBOI, EULP or EULPd board, the downlink services can only be set up on EBBI,
EBOI, EDLP.
For BBU3806, the downlink services can only be set up on EBBC or EBBCd board.
The BBU3900 should be configured with the WBBPb ,WBBPd or WBBPf board.

The feature WRFD-010636 SRB over HSUPA has been configured before this feature
is activated.
License
Other Prerequisites
CN support the uplink speed of 5.74 Mbit/s (or more) .
The UE is of HSUPA category 6, 7, 8, or 9.
Context
This feature enables the HSUPA rate at the MAC layer to reach a maximum of 5.74 Mbit/s.
Issue 06 (2013-03-25)

377
RAN14.0
Procedure
l
1.
Optional: Run the BSC6900 MML command MOD TRMMAP (CME single
configuration: UMTS Global Configuration Express > Transmission Resources
Configuration > Transport Resource Mapping; CME batch modification center:
not supported) to configure the TRM mapping table based on the network plan. The
TRM mapping table contains the mapping relationship between the transmission mode
and the service type.
NOTE
The BSC6900 provides a default TRM mapping table. Use an appropriate mapping policy when
configuring the TRM mapping table. For example, if Transport Type is set to ATM, all HSUPA
services, including signaling services, must be carried by AAL2PATH that supports HSUPA
services.
2.

Parameters in Batches) to enable HSUPA services to use the 2 ms TTI. In this step,
set Service Mapping Strategy Switch to MAP_HSUPA_TTI_2MS_SWITCH.
3.

modification center: 3.15 Modifying RNC Parameters in Batches) to enable SRBs
to be carried on HSUPA channels. In this step, set Type of Channel Preferably
Carrying Signaling RB to HSUPA(UL_EDCH,DL_DCH).
1.
Use an HSPA-capable UE to establish a PS service on the E-DCH and HS-DSCH.
2.
Start Uu interface tracing on the BSC6900 LMT. The RRC_RB_SETUP message

shows that the 2 ms TTI is used in the uplink and the maximum channelization code
IE is 2SF2+2SF4.
3.
The real-time monitoring result of UL Throughput & Bandwidth on the BSC6900

side shows that the bandwidth is 5440 kbit/s and that upload through FTP is normal.
1.

Parameters in Batches) to prohibit the 2 ms TTI from being used on HSUPA
channels. In this step, deselect the MAP_HSUPA_TTI_2MS_SWITCH check box
under the Service Mapping Strategy Switch parameter.
2.

modification center: 3.15 Modifying RNC Parameters in Batches) to prohibit SRBs
from being carried on HSPA channels. In this step, set Type of Channel Preferably
Carrying Signaling RB to DCH(UL_DCH,DL_DCH).
----End
Issue 06 (2013-03-25)

378
RAN14.0
Example
//Activating HSUPA 5.74Mbps per User
SET UFRCCHLTYPEPARA: SrbChlType=HSUPA;
//Deactivating HSUPA 5.74Mbps per User
SET UFRCCHLTYPEPARA: SrbChlType=DCH;
Issue 06 (2013-03-25)

379
RAN14.0
108
Configuring Streaming Traffic Class

on HSUPA
Streaming Traffic Class on HSUPA.
Prerequisites
l

License
Context
This feature allows PS streaming services to be carried on E-DCHs, thereby increasing the
utilization of cell resources.
Procedure
l
Issue 06 (2013-03-25)
1.

MAP_PS_STREAM_ON_HSUPA_SWITCH check box under the parameter
Service Mapping Strategy Switch.
2.

380
RAN14.0
UL streaming traffic threshold on HSUPA to an appropriate value. The default

value is 256 kbit/s.
l
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH. Ensure that

the MAP_PS_STREAM_ON_HSUPA_SWITCH check box under the parameter
Service Mapping Strategy Switch is selected.
2.
Use the UE to establish a PS service.
3.
Expected result: The traffic type in the RAB assignment message is streaming, and
the RB setup message traced on the Uu interface indicates that the PS service is
established on an E-DCH.
1.

MAP_PS_STREAM_ON_HSUPA_SWITCH check box under the parameter
Service Mapping Strategy Switch.
----End
Example
//Activating Streaming Traffic Class on HSUPA
SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSUPA_SWITCH-1;
SET UFRCCHLTYPEPARA: UlStrThsOnHsupa=D256;
//Deactivating Streaming Traffic Class on HSUPA
Issue 06 (2013-03-25)

381
RAN14.0
109
Configuring HSUPA over Iur
HSUPA over Iur.
Prerequisites
l
The neighboring RNC supports this feature.

License
Other Prerequisites
The neighboring RNC must support HSUPA over Iur too.
Context
This feature enables HSUPA services to be carried on the Iur interface so that continuous HSUPA
services can be provided for UEs moving between BSC6900s.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD UEXT3GCELL (CME single

to configure a neighboring RNC's cell with the E-DCH function. In this step, set Cell
Capability Container to an appropriate value.
2.
modification center: not supported) to configure data about the neighboring RNC. In
382
RAN14.0
this step, set Hsupa cap ind over IUR for NRNC to ON to enable HSUPA services
to be carried on the Iur interface.
l
1.
Verify that the feature HSUPA over Iur has been activated by performing the following
operations:
Run the BSC6900 MML command LST UNRNC to query the configuration of
the neighboring RNC.
Run the BSC6900 MML command LST UEXT3GCELL to query the
configuration of the neighboring RNC's cell.
2.
Verify that an HSUPA service has been established on the Iur interface by performing
the following operations:
Configure the neighboring RNC and its cell with the HSUPA function.
Establish an HSUPA service under the serving RNC.
Add a cross-Iur soft handover link.
If the RNSAP_RL_SETUP_REQ message traced on the Iur interface contains
HSUPA-related information elements, an HSUPA service has been set up
successfully.
1.
modification center: not supported). In this step, set Hsupa cap ind over IUR for
NRNC to OFF.
----End
Example
MOD UEXT3GCELL: NRncId=2, CellId=2,
CellCapContainerFdd=EDCH_SUPPORT-1&EDCH_2SF4_SUPPORT-1&EDCH_HARQ_IR_COMBI
N_SUPPORT-1;
ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, TnlBearerType=IP_TRANS,
Dpx=2, IurHsupaSuppInd=ON;
MOD UNRNC: NRncId=1, IurHsupaSuppInd=OFF;
Issue 06 (2013-03-25)

383
RAN14.0
110 Configuring TTI Switch for BE Services Based on

Coverage
110
Configuring TTI Switch for BE

TTI Switch for BE Services Based on Coverage.
Prerequisites
l

The feature WRFD-010614 HSUPA Phase 2 has been configured before this feature is
activated.
License
Context
This feature dynamically adjusts transmission time intervals (TTIs) based on UE transmit power
and uplink service throughput. The TTI of UEs in the cell center is switched to 2 ms to increase
the service rate, whereas the TTI of UEs at the cell edge is switched to 10 ms to expand the
coverage.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches) to turn on the switch for this feature. In this step, select the
DRA_DCCC_SWITCH and the
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH check box under the
384
RAN14.0

Coverage
2.
Optional: If the Uplink Enhanced L2 feature is used, run the BSC6900 MML
command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch
Configuration > Connection Oriented Algorithm Switches; CME batch
select the DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH check box under
the parameter Dynamic Resource Allocation Switch.
NOTE
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH can be selected only when

DRA_BASE_COVER_BE_TTI_RECFG_SWITCH has been selected.
1.
Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG to trace Uu
interface signaling messages, as shown in Figure 110-1.
Issue 06 (2013-03-25)
2.
Adjust the distance between the UE and the NodeB to trigger a switching of the TTI
from 2 ms to 10 ms.
3.
Analyze the traced messages shown in Figure 110-2 and Figure 110-3. The TTI has
switched from 2 ms to 10 ms.

385
RAN14.0

Coverage
Figure 110-2 2 ms TTI
Figure 110-3 10 ms TTI
1.

Parameters in Batches) to turn off the switch for this feature. In this step, deselect
the DRA_BASE_COVER_BE_TTI_RECFG_SWITCH check box under the
----End
Issue 06 (2013-03-25)

386
RAN14.0

Coverage
Example
//Activating TTI Switch for BE Services Based on Coverage
//Turning on the switch for the feature TTI Switch for BE Services Based
on Coverage
DraSwitch=DRA_DCCC_SWITCH-1&DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITCH-1;
//Turning on the switch for TTI L2+ for BE services based on coverage
SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH-1;
//Deactivating TTI Switch for BE Services Based on Coverage
//Turning off the switch for the feature TTI Switch for BE Services Based
on Coverage
SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-0;
Issue 06 (2013-03-25)

387
RAN14.0
111
Configuring HSUPA Adaptive

Transmission
HSUPA Adaptive Transmission.
Prerequisites
l
The BTS3812E and BTS3812AE should be configured with the EBBI, EBOI, EULP
or EULPd board.
The BBU3900 is configured with the WBBPb, WBBPd or WBBPf board.

License
Context
Considering cell uplink power load, CE resources, and limited uplink coverage, this feature
enables the BTS to adjust the target number of uplink retransmissions to increase the throughput
per user and cell uplink capacity.
Procedure
l
1.
Issue 06 (2013-03-25)
To enable the message containing NodeB private interface data to be transmitted to

the NodeB over the Iub interface, run the BSC6900 MML command SET
388
RAN14.0
URRCTRLSWITCH (CME single configuration: UMTS Radio Global

Configuration Express > Process Switch Configuration > Process Switch; CME
step, set Process switch to NODEB_PRIVATE_INTERFACE_SWITCH.
2.

PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH from the Power Control
Switch drop-down list to activate HSUPA Adaptive Transmission.
3.
Run the NodeB MML command SET ADPRETRANSSWTCH (CME single

Information > Radio Management > ADPRETRANSSWTCH; CME batch
modification center: not supported) to activate HSUPA Adaptive Transmission on the
NodeB side.
1.
Enable the UE to establish an HSUPA BE service. Then, check whether the

NBAP_RL_RECFG_PREP message over the Iub interface carries the target number
of HSUPA adaptive retransmissions, as shown in Figure 111-1.
Figure 111-1 IE information
1.

Parameters in Batches). In this step, deselect
PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH from the Power Control
Switch drop-down list to deactivate HSUPA Adaptive Transmission.
2.
Run the NodeB MML command SET ADPRETRANSSWTCH (CME single

Information > Radio Management > ADPRETRANSSWTCH; CME batch
modification center: not supported) to deactivate HSUPA Adaptive Transmission on
the NodeB side.
----End
Example
//Activating HSUPA Adaptive Transmission (BSC6900 MML command)
Issue 06 (2013-03-25)

389
RAN14.0
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-1;

//Activating HSUPA Adaptive Retransmission (NodeB MML command)
SET ADPRETRANSSWTCH: SWITCH =OPEN;
//Deactivating HSUPA Adaptive Transmission (BSC6900 MML command)
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-0;
//Deactivating HSUPA Adaptive Retransmission (NodeB MML command)
SET ADPRETRANSSWTCH: SWITCH=CLOSE;
Issue 06 (2013-03-25)

390
RAN14.0
112
Configuring Dynamic CE Resource

Management
Dynamic CE Resource Management.
Prerequisites
l

WRFD-010612 HSUPA Introduction Package
License
Context
To improve utilization efficiency of channel element (CE) resources, Huawei RAN introduces
the Dynamic CE Resource Management feature. This feature helps to quickly adjust CE
allocation by considering the Guaranteed Bit Rate (GBR) and the actual rate of a UE. During
preemption of CE resources, this feature is used to allocate CE resources in a reasonable way,
therefore ensuring preemption fairness.
Procedure
l
1.
1.
Start Tracing Messages on the Iub Interface on BSC6900 LMT and check whether the
value of dynamic-CE-Switch-Private in NBAP_AUDIT_RSP is 1.
If the value is 1, it indicates the feature is activated. Else, it indicates the feature is not
activated. When the value of dynamic-CE-Switch-Private is 1, see Figure 112-1.
Issue 06 (2013-03-25)

391
RAN14.0
Figure 112-1 dynamic-CE-Switch-Private
1.
Set NodeB license control item the number of NodeBs with dynamic CE function
enabled to 0 on M2000 client . Details see Allocating a License to NodeBs.
----End
Example
None
Issue 06 (2013-03-25)

392
RAN14.0
113
Configuring HSUPA FDE
HSUPA FDE.
Prerequisites
l
The BTS3812E/BTS3812AE must be configured with the EULPd board.
The 3900 series base stations must be configured with the WBBPd or WBBPf board.

License
Context
HSUPA FDE equalizes the spectrum in the frequency domain on the HSUPA E-DPDCH through
the UL receiver of the NodeB, therefore suppressing the inter-path interference on the EDPDCH. In this manner, the SNR on the EDPDCH is increased and the UL system capacity of
the HSUPA network is expanded. The rate of HSUPA services is also increased in multipath
environment.
NOTE
For UEs of category 6 and category 7 at a transmission rate higher than 2 Mbit/s, the feature brings notable
gains if multipath channels are used in the uplink.
Procedure
l
Issue 06 (2013-03-25)
393
RAN14.0
1.
1.
Run the NodeB MML command MOD LOCELL (CME single configuration: NodeB
Batches) to modify the local cell. In this step, set FDE to TRUE.
Run the NodeB MML command DSP LOCELL to query the configuration
information about the local cell.
Expected result: The value of FDE MODE is ENABLED.
1.
Batches) to modify the local cell. In this step, set FDE to FALSE.
----End
Example
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, FDE_MODE=TRUE;
DSP LOCELL: LOCELL=1;
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, FDE_MODE=FALSE;
Issue 06 (2013-03-25)

394
RAN14.0
114 Configuring Adaptive Configuration of Traffic Channel

Power offset for HSUPA
114
Configuring Adaptive Configuration
of Traffic Channel Power offset for HSUPA

Adaptive Configuration of Traffic Channel Power offset for HSUPA.
Prerequisites
l

License
Context
As the HSPA/HSPA+ becomes an increasingly popular mainstream technology, uplink system
performance needs to be enhanced to adapt to the ever-refreshed HSUPA peak rate. Based on
the changes in subscriber behaviors and network status, this feature adaptively configures the
parameters related to power control on the optimum uplink data channel, increasing the HSUPA
system capacity.
NOTE
l This feature applies only to HSUPA Best Effort (BE) services whose Transmission Timing Interval (TTI)
is 10 ms.
l This feature is applicable to the scenarios where HSUPA dynamic channel configuration control (DCCC)
takes effect and the scenarios where dynamic channel element (CE) takes effect (HSUPA DCCC does not
take effect).
l This feature is highly dependent on parameter settings. The relevant parameters must retain the default
values. This feature may fail to take effect if these parameter settings are changed.
Issue 06 (2013-03-25)

395
RAN14.0

Procedure
l
CAUTION
Before activating this feature, check the settings of the following two parameters: if
Reference E-TFCI Index1 is set to 4 and Reference E-TFCI Power Offset1 is set to
12, you are advised to set Reference E-TFCI Power Offset1 to 8.
1.
2.
Issue 06 (2013-03-25)
Activation Procedure in the Scenario Where HSUPA DCCC Takes Effect

a.
Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME

PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH check box
under the parameter Power Control Switch.
b.

Parameters in Batches) to enable HSUPA DCCC. In this step, select the
DRA_DCCC_SWITCH and DRA_HSUPA_DCCC_SWITCH check boxes
under the parameter Dynamic Resource Allocation Switch.
c.
(Optional) Run the BSC6900 MML command SET

UEDCHRATEADJUSTSET (CME single configuration: UMTS Radio
Global Configuration Express > Dynamic Channel Control Parameter
Configuration > HSUPA Rate Adjust Set; CME batch modification center:
3.15 Modifying RNC Parameters in Batches) to select adjustable rates for
EDCH. In this step, select RATE_128KBPS, RATE_256KBPS,
RATE_608KBPS, and RATE_2048KBPS check boxes under the parameter
HSUPA UpLink Rate Adjust Set.
d.
Run the BSC6900 MML command SET UFRC (CME single configuration:
UMTS Radio Global Configuration Express > Basic Resource Control
Parameter Configuration > RNC Oriented FRC Algorithm Parameters;
CME batch modification center: 3.15 Modifying RNC Parameters in
Batches) to set the value of Initial rate of HSUPA BE traffic. You are advised
to set Initial rate of HSUPA BE traffic to the recommended value D256.
e.
Disable dynamic CE on the NodeB side.
Activation Procedure in the Scenario Where Dynamic CE Takes Effect

a.

PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH check box
under the parameter Power Control Switch.
b.
Enable dynamic CE on the NodeB side.

396
RAN14.0

NOTE
l In dynamic CE scenarios, the BSC6900 configures the Hybrid Automatic Repeat Request (HARQ)
power offset (PO) based on the realtime service rate. In the scenarios where HSUPA DCCC takes
effect, the actual service rate is variable, and the BSC6900 configures the HARQ PO based on the
realtime service rate.
l The HARQ PO is one of the variable that determines the power offset on the E-DPDCH compared
with the DPCCH.
1.
Run the BSC6900 MML command LST UTYPRABHSUPAPC to check the

parameters related to power offset for typical services. Figure 114-1 shows an
interactive BE service with the CN-assigned rate of 2048 kbit/s, whose Service
parameter index is set to 55, Traffic Subflow Index to 0, Transport channel
type to TRCH_EDCH_10MS, and the Ul 16QAM Used Indication, Ul enhanced
L2 Used Indication, EdPower Interpolation Priority Used Indication, and UL EDPCCH Boosting Indication parameters all set to FALSE. As shown in Figure
114-1, HARQ PO for Large Retransmission is set to 0, HARQ PO for small
Retrans at Low Speed is set to 4, and HARQ PO for small Retrans at High
Speed is set to 0.
Figure 114-1 PO parameters of typical services
Issue 06 (2013-03-25)

397
RAN14.0

2.
Establish a PS interactive BE service over HSUPA, for example, upload files to the
FTP server.
NOTE
l In multi-user scenarios where the target load is limited and the realtime service rate of a single
user is lower than a low-rate threshold (such as 150 kbit/s), the user is in the small retransmission
state at a low speed. The HARQ PO is the value of HARQ PO for small Retrans at Low
Speed.
l If the realtime service rate of a single user is higher than a high-rate threshold (such as 300 kbit/
s), the user is in the small retransmission state at a high speed. The HARQ PO is the value of
HARQ PO for small Retrans at High Speed.
3.
Check the realtime rate of the new BE service and the CN-assigned rate by referring
to Monitoring UL Throughput and Bandwidth, as shown in Figure 114-2.
Figure 114-2 Rate of the new BE service
4.
Verification Procedure in the Scenario Where HSUPA DCCC Takes Effect

a.
Issue 06 (2013-03-25)
Check the uplink throughput and bandwidth by referring to Monitoring UL

Throughput and Bandwidth. The data rate of the HSUPA service when
accessing the network is 256 kbit/s. Trace messages over the Uu interface by
referring to Tracing Messages on the Uu Interface. The value of the HARQ
PO in the RRC_RB_SETUP message shows that the user is in the small
retransmission state at a high speed. The HARQ PO is equal to the value of
HARQ PO for small Retrans at High Speed, as shown in Figure 114-3.

398
RAN14.0

Figure 114-3 HARQ PO (4) of a UE for small retransmission at a low speed (256
kbit/s)
b.
After the file upload on the FTP is complete, check the uplink data rate of the
UE by referring to Monitoring UL Throughput and Bandwidth. When the
data rate is 608 kbit/s, check the value of HARQ PO in the
RRC_RB_RECFG message by referring to Tracing Messages on the Uu
Interface. The HARQ PO changes from HARQ PO for small Retrans at High
Speed for 256 kbit/s to that for 608 kbit/s, as shown in Figure 114-4.
Figure 114-4 HARQ PO (0) of a UE for small retransmission at a high speed
5.
Verification Procedure in the Scenario Where Dynamic CE Takes Effect

a.
Issue 06 (2013-03-25)
Trace messages over the Uu interface by referring to Tracing Messages on the

Uu Interface. The value of the HARQ PO in the RRC_RB_SETUP message
399
RAN14.0

shows that the user is in the small retransmission state at a high speed when
accessing the network. The HARQ PO is equal to the value of HARQ PO for
small Retrans at High Speed, as shown in Figure 114-5.
Figure 114-5 HARQ PO (0) of a UE for small retransmission at a high speed
b.
Simulate a situation that the uplink load is limited by changing the target uplink
load to 10%. Run the BSC6900 MML command MOD UCELLHSUPA. In this
step, set Maximum Target Uplink Load Factor to 10. After the uplink load is
limited, check the uplink throughput and bandwidth by referring to Monitoring
UL Throughput and Bandwidth. HARQ PO reconfiguration is triggered when
the uplink throughput of the UE is lower than the low-rate threshold. Check the
value of HARQ PO in the RRC_RB_RECFG message by referring to Tracing
Messages on the Uu Interface. The HARQ PO changes from HARQ PO for
small Retrans at High Speed to HARQ PO for small Retrans at Low
Speed, as shown in Figure 114-6.
Figure 114-6 HARQ PO (4) of a UE for small retransmission at a low speed
Issue 06 (2013-03-25)

400
RAN14.0

c.
If the feature WRFD-010641 HSUPA Adaptive Transmission takes effect, use

another UE to perform a PS interactive service with an uplink rate of 2048 kbit/
s and downlink rate of 7200 kbit/s in the cell. There is a possibility that the UE
switches from small retransmission state to large retransmission state if the cell
load increases to a certain value. Check the HARQ PO in the
RRC_RB_RECFG message by referring to Tracing Messages on the Uu
Interface. The HARQ PO changes from HARQ PO for Small Retrans at Low
Speed to HARQ PO for Large Retransmission, as shown in Figure 114-7.
Figure 114-7 HARQ PO (0) of a UE for large retransmission at a low speed
1.

Parameters in Batches) to turn off the switch for this feature. In this step, clear the
PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH check box under the
parameter Power Control Switch.
----End
Example
//Activation procedure in the scenario where HSUPA DCCC takes effect
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-1;
DraSwitch=DRA_DCCC_SWITCH-1&DRA_HSUPA_DCCC_SWITCH-1;
EdchRateAdjustSet=RATE_128KBPS-1&RATE_256KBPS-1&RATE_608KBPS-1&RATE_2048K
BPS-1;
SET UFRC: HsupaInitialRate=D256;
//Activation procedure in the scenario where dynamic CE takes effect
Issue 06 (2013-03-25)

401
RAN14.0

LST UTYPRABHSUPAPC: QueryType=QUERY_BY_PROPERTY, CNDomainId=PS_DOMAIN,
TrafficClass=INTERACTIVE, MaxBitRate=256000, TrchType=TRCH_EDCH_10MS,
Ul16QamInd=FALSE, UlL2EnhanceInd=FALSE, EdPwrInterpolationInd=FALSE,
UlEcBoostingInd=FALSE;
//Verification procedure in the scenario where dynamic CE takes effect
MOD UCELLHSUPA: CellId=x, MaxTargetUlLoadFactor=10
Issue 06 (2013-03-25)

402
RAN14.0
115
Configuring Anti-Interference
Anti-Interference Scheduling for HSUPA.
Prerequisites
l
The BTS3812E and BTS3812AE should be configured with the HBBI, EBBI,
HULP, EBOI, EULP, or EULPd board. The downlink services can only be set up
on the EBBI, EBOI, or EDLP board.

License
Context
In commercial networks, the uplink data transmission of HSUPA at some sites is affected
randomly by strong external interference. When a site is strongly interfered, the HSUPA
throughput of the site is significantly reduced and user experience is affected.
This feature can eliminate the strong external interference and maintain high HSUPA
throughput, improving user experience.
NOTE
This feature is not proposed for multi-RRU cells.
Issue 06 (2013-03-25)

403
RAN14.0
Procedure
l
1.
3.17 Modifying Physical NodeB Parameters in Batches) to set Mac-e parameters.
a.
Set the MAC-e Schedule Para to YES(YES).
b.
Set the Anti-Interference Scheduling Switch to ON(ON).
c.
Own Cell UL Load Ratio.

In indoor coverage scenarios, the recommended value is 90.
In non-indoor coverage scenarios, the recommended value is 60.
d.
It is recommended that Min UL Cover Load Threshold(dB) be set to 13.

NOTE
If Local Cell ID is not specified, the Mac-e scheduling parameters of all local cells under the
NodeB will be set.
CAUTION
If the following conditions are met, step 2 is not required, and the configuration ends.
l On the RNC side, UL_UU_OLC(Uplink UU OLC Algorithm) is not selected
for Switch for Cell Load Control.
l On the RNC side, ALGORITHM_OFF or ALGORITHM_SECOND is selected
for Uplink CAC algorithm switch.
2.
Optional: Run the BSC6900 MML commandMOD UCELLALGOSWITCH (CME

single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell
Parameters in Batches). In this step, set Cell CAC algorithm switch to
RTWP_RESIST_DISTURB(RTWP Resist Disturb Switch).
1.
Run the NodeB MML command DSP LICENSE to display license information.
Exception result: the value of Anti-Interference Scheduling for HSUPA Function
(per Cell) is bigger than 0.
2.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters.
Set the Anti-Interference Scheduling Switch to OFF(OFF).
3.
Make interference.
For example: Run the NodeB MML command SET DESENS, set Desensitization
Intensity to 6.
Issue 06 (2013-03-25)
4.
Use a UE to carry out HSUPA upload task.
5.
Select Service > Realtime Specific Monitoring > Cell RTWP from the navigation
tree in Maintenance tab on NodeB LMT, as shown in Figure 115-1. The column
1-3 indicates the state of this feature disabled.
404
RAN14.0
Figure 115-1 Cell RTWP (feature disabled)
6.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters.
a.
Set the Anti-Interference Scheduling Switch to ON(ON).
b.
Own Cell UL Load Ratio

In indoor coverage scenarios, the recommended value is 90.
In non-indoor coverage scenarios, the recommended value is 60.
c.
It is recommended that Min UL Cover Load Threshold(dB) be set to 13.

NOTE
If Local Cell ID is not specified, the Mac-e scheduling parameters of all local cells under the
NodeB will be set.
7.
Issue 06 (2013-03-25)
1-3 indicates the state of this feature enabled. If the values of column 1-3 in Figure
115-1 are bigger than the values of 1-3 in Figure 115-2, it indicates the feature has
been enabled.

405
RAN14.0
Figure 115-2 Cell RTWP (feature enabled)
1.
Set the Anti-Interference Scheduling Switch to OFF(OFF).
----End
Example
SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=ON,
OWNCELLULLOADRATIO=60, LOADTHRESH4MINULCOV=13, EAGCHPCPARA=NO,
SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
(Optional)MOD UCELLALGOSWITCH: CELLID=0,
NBMCacAlgoSwitch=RTWP_RESIST_DISTURB-1;
DSP LICENSE:;
SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=OFF,
EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO,
NSEHICHPCPARA=NO;
SET DESENS: LOCELL=0, DI=6;
SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=ON,
OWNCELLULLOADRATIO=60, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO,
SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=OFF,
EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO,
NSEHICHPCPARA=NO;
Issue 06 (2013-03-25)

406
RAN14.0
116 Configuring Dual-Threshold Scheduling with HSUPA

Interference Cancellation
116
Configuring Dual-Threshold
Scheduling with HSUPA Interference

Cancellation
Dual-Threshold Scheduling with HSUPA Interference Cancellation.
Prerequisites
l


The BTS3812E/AE must be configured with EULPd baord, and all users of the cell
should be estabilished in one EULPd board.
The 3900 series base stations must be configured with the WBBPd board in the UL
resource pool which support IC feature, and slot 2 or 3 needs to be configured with at
least one WBBPd board.
The RRU3801C 20W and the MTFU for the BTS3812E and BTS3812AE do not support
this feature.

WRFD-010691 HSUPA UL Interference Cancellation
License
Context
This feature is applicable in cells enabled with the WRFD-010691 HSUPA UL Interference
Cancellation feature.
Issue 06 (2013-03-25)

407
RAN14.0

Procedure
l
1.
Set the MAC-e Schedule Para to YES.
Set the Max Target RoT Difference Before and After IC to 2.
2.
Run the BSC6900 MML commandMOD UCELLCAC (CME single configuration:

Cell Parameters in Batches), set UL IC LDC Optimized Switch in the specified
cell to ON(ON).
1.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set
Max Target RoT Difference Before and After IC to 0.
2.
Use multi users to carry out upload service.
3.
1-3 indicates the state of this feature disabled, the column 1-4 indicates the state of
this feature enabled. If the value of column 1-4 is less than the value of column 1-3,
it indicates HSUPA UL Interference Cancellation feature has been enabled.
Figure 116-1 Cell RTWP 1
4.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set
Max Target RoT Difference Before and After IC to 2.
5.
Check the Cell RTWP window. If the value of column 1-4 is less than the value of
column 1-3, and the values of column 1-4 and column 1-3 increase by 10, it indicates
dual-threshold scheduling with HSUPA interference cancellation feature has been
enabled.
NOTE
The prerequisite of the foregoing result is the cell power limit does not over.
Issue 06 (2013-03-25)

408
RAN14.0

6.
l
Run the BSC6900 MML commandLST UCELLCAC, check that UL IC LDC

Optimized Switch is set to ON(ON).
1.
Set Max Target RoT Difference Before and After IC to 0.
2.
Reallocate the license of this feature on M2000 LMT, and set Allocated to 0.
3.
Run the BSC6900 MML commandMOD UCELLCAC (CME single configuration:

Cell Parameters in Batches), set UL IC LDC Optimized Switch in the specified
cell to OFF(OFF).
----End
Example
//Operations at the NodeB
SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, MAXDELTAOFTARGETROT=2,
EAGCHPCPARA=NO, SERGCHPCPARA=NO,
//Operations at the RNC
MOD UCELLCAC: CellId=1, UlIcLdcOptSwitch=ON;
LST UCELLCAC: CellId=1;
Issue 06 (2013-03-25)

409
RAN14.0


MOD UCELLCAC: CellId=1, UlIcLdcOptSwitch=OFF;
Issue 06 (2013-03-25)

410
RAN14.0
117

Cell
Prerequisites
l

The following features must be configured before this feature is activated:
License
Context
This feature enables a single HSUPA cell to serve a maximum of 60 HSUPA users
simultaneously. After the maximum number of users is reached, the cell attempts to establish
services on DCHs to accommodate additional users.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD UCELLHSUPA (CME single

UMTS Cell Parameters in Batches) to set Code Number for E-RGCH/E-HICH
to appropriate value.
2.
Cell Parameters in Batches) to set Maximum HSUPA user number to 60.
411
RAN14.0
1.
On the BSC6900 LMT, click Monitor. Then, double-click UMTS Monitoring > Cell
Performance Monitoring in the Monitor Navigation Tree pane. In the displayed
Cell Performance Monitoring dialog box, set Monitor Item to Cell User
Number.
2.
Use UEs to access the cell one by one. Then, make UEs establish PS services, for
example, upload files through FTP.
3.
View the maximum number of HSUPA users indicated by the counter

NOTE
1.
----End
Example
//Allocating code resources to E-RGCHs
MOD UCELLHSUPA: CellId=111, ErgchEhichCodeNum=3;
//Setting the maximum number of HSUPA users to 60
MOD UCELLCAC: CellId=111, MaxHsupaUserNum=60;
Issue 06 (2013-03-25)

412
RAN14.0
118
Configuring HSUPA UL Interference

Cancellation
HSUPA UL Interference Cancellation.
Prerequisites
l
The BTS3812E or BTS3812AE must be configured with the EULPd board, the
downlink service cannot be estabilished on HBBI/HDLP/NDLP, and the IC effect
cannot be shared between BB boards.
The DBS3800 must be configured with the EBBCd board and the IC effect can be
shared between the BB boards.
The 3900 series base stations must be configured with the WBBPd or WBBPf board,
and only if slot 2 or 3 is configured with at least one WBBPd or WBBPf board, IC
effect can be shared between the WBBPd or WBBPf boards.
WBBPd/WBBPf is needed for 3900 series NodeB to support HSUPA UL
Interference Cancellation. If the inter-board sharing IC need to be supported, the
WBBPd/WBBPf should be configured in the UL resource pool which used for interboard sharing IC, and at least 1 WBBPd/WBBPf should be configured in slot 2 or
3.

License
Issue 06 (2013-03-25)

413
RAN14.0
Context
CAUTION
Activate this feature when the traffic volume in a cell is low. The reason is that the cell must be
deactivated before this feature is activated; after the cell is deactivated, the services in this cell
are disrupted.
Interference Cancellation (IC) is performed to cancel the interference caused by the uplink high
rate E-DPDCH data of other users, improving the demodulation signal-to-noise ratio (SNR) and
increasing the uplink capacity of the UMTS network.
NOTE
l For 3900 series base stations, the WBBPd/WBBPf must be configured on slot 2 or slot 3 on the
BBU3900 to support the uplink data IC integrated interference cancellation function. The uplink
resource group must contain the WBBPd/WBBPf. Therefore, cell of the group can support the IC
feature. For details, see Adding a Baseband Board to a 3900 Series Base Station.
l If the DBS3800 is configured with two EBBCd boards, it is recommended that two uplink resource
groups be allocated to the two boards separately. In this way, both the boards support HSUPA uplink
interference cancellation. For details about how to configure the active and standby BTSs, see Adding
an EBBC or EBBCd.
l If the BTS3812E or BTS3812AE is configured with two EULPd boards, it is recommended that two
uplink resource groups be allocated to the two boards separately. In this way, both the boards support
HSUPA uplink interference cancellation. For details about how to configure the active and standby
BTSs, see Adding a Baseband Board to the BTS3812E or BTS3812AE.
Procedure
l
l
Issue 06 (2013-03-25)
1.
If the UMTS cell has been activated, run the BSC6900 MML command DEA
UCELL (CME single configuration: UMTS Cell Configuration Express > Cell
Basic Information > Cell Basic Information. Set Validation indication to
Deactivated; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to deactivate the cell.
2.
Batches) to modify the local cell. In this step, set IC to TRUE.
3.
Run the BSC6900 MML command ACT UCELL (CME single configuration: UMTS
Cell Configuration Express > Cell Basic Information > Cell Basic Information.
Set Validation indication to Activated; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to activate the cell.
4.
Run the NodeB MML command SET RESALLOCRULE (CME single

Information > Radio Management > RESALLOCRULE; CME batch modification
center: not supported). In this step, set Auto Rebuild Cell Switch to ON(ON) and set
Cs User Number Threshold and Ps User Number Threshold. If the number of CS
users or the number of PS CELL_DCH users in the downlink resource group is equal
or smaller than the corresponding threshold, the local cells are reestablished
automatically.
414
RAN14.0
1.
Run the NodeB MML command DSP LOCELL to query the status of a specified
local cell.
Expected result: The value of IC MODE is ENABLED.
2.
Run the NodeB MML command LST RESALLOCRULE.

Expected result: The value of Auto Rebuild Cell Switch is ON.
3.
1-3 indicates the state of this feature disabled, the column 1-4 indicates the state of
this feature enabled. If the value of column 1-4 is less than the value of column 1-3,
it indicates the feature has been enabled.
1.
Batches) to modify the local cell. In this step, set IC to FALSE.
----End
Example
DEA UCELL: CellId=1;
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, IC_MODE=TRUE;
ACT UCELL: CellId=1;
SET RESALLOCRULE: SW=ON, CSUSERNUM=0, PSUSERNUM=0;
LST RESALLOCRULE:;
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, IC_MODE=FALSE;
Issue 06 (2013-03-25)

415
RAN14.0
119
Configuring SRB over HSUPA
SRB over HSUPA.
Prerequisites
l
BSC6900
Requirements for the NodeB
The 38XX series NodeB supports this feature, and the EBBI, EBOI, EULP or
EULPd, EBBC or EBBCd is required.
The 3900 series NodeB supports this feature, and the WBBPb, WBBPd or WBBPf
is required.

The WRFD-010612 HSUPA Introduction Package feature must be configured before
this feature is configured.
License
Other Prerequisites
The transmission mapping to support SRB over HSUPA has been configured.
Context
This feature provides high signaling rate and shortens call setup delay. Compared with the
function of carrying SRBs on DCHs, this feature saves code resources and reduces cell load.
Procedure
l
1.
Issue 06 (2013-03-25)

416
RAN14.0
modification center: 3.15 Modifying RNC Parameters in Batches) to set Type of

Channel Preferably Carrying Signaling RB to HSUPA(UL_EDCH,DL_DCH) or
HSPA(UL_EDCH,DL_HSDSCH).
NOTE
If the feature is effective in the case of RRC connection establishment, set Effective Flag of
Signaling RB Channel Type to TRUE.
1.
Run the BSC6900 MML command LST UFRCCHLTYPEPARA to query whether

the SRBs are carried over HSUPA.
2.
Use a UE with the HSPA function to set up an RRC connection on the enhanced DCH
(E-DCH).
View the RRC_RRC_CONN_SETUP message from the Uu interface trace data. If
the EDCH information is contained in the message, this feature is activated.
1.

Channel Preferably Carrying Signaling RB to DCH(UL_DCH,DL_DCH) and
Effective Flag of Signaling RB Channel Type to FALSE.
----End
Example
//Activating SRB over HSUPA
SET UFRCCHLTYPEPARA: SrbChlType=HSUPA, SrbChlTypeRrcEffectFlag=TRUE;
//Verifying SRB over HSUPA
LST UFRCCHLTYPEPARA:;
//Deactivating SRB over HSUPA
SET UFRCCHLTYPEPARA: SrbChlType=DCH, SrbChlTypeRrcEffectFlag=FALSE;
Issue 06 (2013-03-25)

417
RAN14.0
120 Configuring Control Channel Parallel Interference

Cancellation (Phase 2)
120
Configuring Control Channel
Parallel Interference Cancellation (Phase 2)

Control Channel Parallel Interference Cancellation (Phase 2). Control Channel Parallel
Interference Cancellation is short for CCPIC.
Prerequisites
l
The 3900 series base station (except for BTS3902E) must be configured with the
WBBPd or WBBPf board.
To support inter-board IC, the WBBPd or WBBPf board must be configured for the
uplink resource group that supports inter-board IC. In addition, at least one WBBPd or
WBBPf board must be configured in slot 2 or 3.
It is recommended that the WBBPa or WBBPb board be replaced with a WBBPd or
WBBPf board to fully utilize CCPIC (Phase 2). Assume that a WBBPa or WBBPb board
and a WBBPd or WBBPf board are inserted into one BBU to form a UL resource group.
To share the CCPIC gains of the WBBPd or WBBPf board when NodeB IC Mode is
set to FULL_IC(All board can share IC gain), UEs with their data channel carried
on the WBBPa or WBBPb board must set up another DPCCH on the WBBPd or WBBPf
board for power control. Of the UEs, those with their downlink services carried on an
HSDPA channel must set up another HS-DPCCH on the WBBPd or WBBPf board. The
extra channels consume extra processing resources, reducing the total number of users
supported by the system.

The feature WRFD-010210 Control Channel Parallel Interference Cancellation
(CCPIC) has been configured before this feature is activated.
License
None
Issue 06 (2013-03-25)

418
RAN14.0

Context
l
Precautions
Gains from CCPIC (Phase 2) and Adaptive Configuration of Traffic Channel Power
offset for HSUPA may decrease.
If CCPIC (Phase 2) is enabled, gains from Adaptive Configuration of Traffic
Channel Power offset for HSUPA decrease.
If Adaptive Configuration of Traffic Channel Power offset for HSUPA is enabled,
gains from CCPIC (Phase 2) decrease.
System throughput is always greater when CCPIC (Phase 2) is enabled together with
Adaptive Configuration of Traffic Channel Power offset for HSUPA, as compared
with when CCPIC (Phase 2) is not enabled together with Adaptive Configuration of
Traffic Channel Power offset for HSUPA or none of the features is enabled.
Gains from CCPIC (Phase 2) and HSUPA Adaptive Transmission may decrease.
If CCPIC (Phase 2) is enabled, gains from HSUPA Adaptive Transmission decrease.
If HSUPA Adaptive Transmission is enabled, gains from CCPIC (Phase 2) decrease.
System throughput is always greater when CCPIC (Phase 2) is enabled together with
HSUPA Adaptive Transmission, as compared with when CCPIC (Phase 2) is not
enabled together with HSUPA Adaptive Transmission or none of the features is
enabled.
The cell throughput decreases for 5 to 10 seconds and all UEs carried on a WBBPa or
WBBPb board experience call drops when the following conditions are true:
A WBBPd or WBBPf board and the WBBPa or WBBPb board are inserted into one
BBU to form a UL resource group.
The setting for ICMODE changes when the CCPIC (Phase 2) feature is enabled.
Data Preparation
Scenario 1: No WBBPa or WBBPb board is configured for a base station.
The configuration is not required.
Scenario 2: A WBBPa or WBBPb board is configured for a base station. The WBBPa
or WBBPb board cannot benefit from CCPIC (Phase 2) gains by default.
Parameter Name
Parameter ID
Recommended
Parameter
Settings
Source
IC_MODE
ICMODE
PART_IC(Old
board can not share
IC gain)
Network plan
Scenario 2: A WBBPa or WBBPb board is configured for a base station. The WBBPa
or WBBPb board cannot benefit from CCPIC (Phase 2) gains.
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Recommended
Parameter
Settings
Source
IC_MODE
ICMODE
FULL_IC(All
board can share IC
gain)
Network plan

419
RAN14.0

Procedure
l
NOTE
Even if all prerequisites are ready, CCPIC (Phase 2) may not be available temporarily to the cell to
avoid interruption of ongoing services. To ensure that the cell can be adjusted to support CCPIC
(Phase 2), the Auto Rebuild Cell Switch must be set to ON(ON).
1.
Run the NodeB MML command SET RESALLOCRULE (CME single

Information > Radio Management > RESALLOCRULE; CME batch modification
center: not supported). In this step, set Auto Rebuild Cell Switch to ON(ON) and set
Cs User Number Threshold and Ps User Number Threshold. If the number of CS
users or the number of PS CELL_DCH users in the downlink resource group is equal
or smaller than the corresponding threshold, the local cells are reestablished
automatically.
2.
Select operations as configured.

Scenario 1: The configuration ends.
Scenario 2: Run the NodeB MML command SET ICMODE (CME single
Information > Basic Information > Radio Management > ICMODE; CME
batch modification center: not supported). In this step, set NodeB IC Mode to
PART_IC(Old board can not share IC gain).
Scenario 3: Run the NodeB MML command SET ICMODE (CME single
Information > Basic Information > Radio Management > ICMODE; CME
batch modification center: not supported). In this step, set NodeB IC Mode to
FULL_IC(All board can share IC gain).
Check whether the CCPIC (Phase 2) feature has been activated by using the RNC or NodeB
LMT. If the base station is configured with the RRU3801C, the following verification mode
does not apply.
NOTE
Observe the activation when there are a large number of UEs because CCPIC (Phase 2) gain is obvious
only when there are a large number of UEs.
On the RNC LMT:

1.
On the RNC LMT, click Monitor, choose Cell Performance Monitoring >
RTWP, enter the cell ID, and click Submit.
2.
Check whether a valid value is displayed for Cell measured RTWP After First
Stage Interference Cancellation.
Expected result:
A valid value is displayed, indicating that the CCPIC (Phase 2) feature is
functioning properly. When there are a large number of UEs, Cell measured
RTWP After First Stage Interference Cancellation is smaller than Cell
Measured RTWP. The RTWP decrease further indicates that this feature has been
activated. Figure 120-1 shows the RTWP monitoring result displayed on the RNC
LMT.
Issue 06 (2013-03-25)

420
RAN14.0

Figure 120-1 Cell-level RTWP monitoring on the RNC LMT
On the NodeB LMT:

1.
On the NodeB LMT, click Maintenance, choose Service > Realtime Specific
Monitoring > Cell RTWP.
2.
Check whether a valid value is displayed for Cell measured RTWP After First
Stage interference cancellation.
Expected result:
A valid value is displayed, indicating that the CCPIC (Phase 2) feature is
functioning properly. When there are a large number of UEs, Cell measured
RTWP After First Stage interference cancellation is smaller than Cell
measured RTWP. The RTWP decrease further indicates that this feature has been
activated. Figure 120-2 shows the RTWP monitoring result displayed on the
NodeB LMT.
Issue 06 (2013-03-25)

421
RAN14.0

Figure 120-2 Figure 7-3 Cell-level RTWP monitoring on the NodeB LMT
None
----End
Example
SET RESALLOCRULE: SW=ON, CSUSERNUM=0, PSUSERNUM=0;
//Scenario 2
SET ICMODE: ICMODE=PART_IC;
//Scenario 3
SET ICMODE: ICMODE=FULL_IC;
Issue 06 (2013-03-25)

422
RAN14.0
121
Configuring HSDPA Introduction

Package
HSDPA Introduction Package. (This feature cannot be configured using the CME. )
Prerequisites
l
NDLP and NBBI in the NodeB do not support this feature.

License
Other Prerequisites
The UE is HSDPA-capable.
Context
High Speed Downlink Packet Access (HSDPA) is one of the important features defined in 3GPP
specifications. HSDPA can significantly increase the downlink peak rate per user, shorten the
round trip delay, and expand the system capacity. This feature package provides the basic
functions of HSDPA to meet the requirements for test or trial operation of HSDPA services.
Procedure
l
1.
Run the BSC6900 MML command ADD UCELLHSDPA to set HSDPA-related

parameters based on the network plan.
2.
Run the BSC6900 MML command ACT UCELLHSDPA to activate this feature.
3.
Configure Iub transport for HSDPA.

In an ATM network:
Issue 06 (2013-03-25)

423
RAN14.0
a.
Run the BSC6900 MML command ADD ATMTRF to configure new records
of ATM traffic based on network planning requirements.
b.
Run the BSC6900 MML command LST TRMMAP to query the

transmission resource mapping.
c.
Run the BSC6900 MML command ADD AAL2PATH to set associated

parameters according to the network plan. TX traffic record index and RX
traffic record index of the AAL2 path to be added must be the same as those
set in the ADD ATMTRF command. In addition, AAL2 Path Type should
be set according to the mapping between service types and AAL paths.
d.
Run the NodeB MML command ADD AAL2PATH to configure an AAL2

path for HSDPA based on network planning requirements.
In an IP network:
a.
Run the BSC6900 MML command LST ADJMAP to query whether

resource management mapping is configured for the adjacent node.
If configured, check the TRMMAP index of the adjacent node.
If not configured, run the BSC6900 MML command LST TRMMAP to
query the default TRMMAP ID used by the adjacent node based on the
settings of Interface Type and Transport Type. For example, if
Interface Type is set to Iub Interface, then TRMMAP ID is 1.
b.
Run the BSC6900 MML command LST TRMMAP to check whether the IP
path mapping to the HSDPA service is configured according to the TRMMAP
ID used by the adjacent node.
If configured, no further action is required.
If not configured, run the BSC6900 MML command ADD IPPATH to
configure the IP path mapping to the HSDPA service.
NOTE
To ensure that HSDPA services can be set up successfully, HSDPA services must be mapped to the
corresponding AAL2 paths or IP paths. To avoid the affect on ongoing services, you can add new
AAL2 paths or IP paths.
1.
Run the BSC6900 MML command DSP UCELL to check whether this feature is
activated. If HSDPA Operational State is set to Enabled, this feature has been
activated.
1.
Run the BSC6900 MML command DEA UCELLHSDPA to deactivate this feature.
2.
Run the BSC6900 MML command DSP UCELL to check whether the HSDPA
feature is deactivated. If HSDPA Operational State is set to Disabled, this feature
has been deactivated.
----End
Example
// Setting HSDPA-related parameters
ADD UCELLHSDPA: CellId=3000, AllocCodeMode=Automatic,
HsPdschMaxCodeNum=4, HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON;
//Activating HSDPA Introduction Package
ACT UCELLHSDPA: CellId=3000;
//Configuring Iub transport for HSDPA
//ATM network
Issue 06 (2013-03-25)

424
RAN14.0
ADD ATMTRF: TRFX=118, ST=RTVBR, UT=KBIT/S, PCR=5150, SCR=5149, REMARK="5Mfor-HSDPA";

ADD AAL2PATH: ANI=10, PATHID=2, CARRYT=IMA, CARRYF=1, CARRYSN=0,
CARRYIMAGRPN=1, RSCGRPFLAG=NO, VPI=13, VCI=71, TXTRFX=118, RXTRFX=118,
AAL2PATHT=HSPA;
ADD AAL2PATH: PATHID=2, SN=12, SBT=BASE_BOARD, PT=IMA, VPI=13, VCI=71,
ST=RTVBR, PCR=5150, SCR=5149, RCR=5150, NT=LOCAL, PAT=H_NRT;
//IP network
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP,PATHT=BE,
IPADDR="80.1.1.1", PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0",
TXBW=1000, RXBW=1000;
//Verifying HSDPA Introduction Package
DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;
//Deactivating HSDPA Introduction Package
DEA UCELLHSDPA: CellId=3000;
DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;
Issue 06 (2013-03-25)

425
RAN14.0
122
Configuring 15 Codes per Cell
WRFD-01061001 15 Codes per Cell.
Prerequisites
l

feature depends on the feature WRFD-010610 HSDPA Introduction Package.
License
Context
This feature provides code resources occupied by Huawei HSDPA services. An HS-PDSCH can
use up to 15 SF16 codes in a cell.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD UCELLHSDPA (CME single

HSDPA Parameters; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to set Code Number for HS-SCCH to 1.

426
RAN14.0

NOTE
l The BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) fails to be executed
when HSDPA is activated. Therefore, run the BSC6900 MML command DEA
UCELLHSDPA (CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell HSDPA Parameters. Set ACTSTATUS to Deactivated; CME batch
modification center: No supported) to deactivate HSDPA before configuring this feature and
run the BSC6900 MML command ACT UCELLHSDPA (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell HSDPA Parameters. Set
ACTSTATUS to Activated; CME batch modification center: No supported) to reactivate
HSDPA after configuring this feature.
l The BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) fails to be executed
when CELL-FACH enhancement is activated. Therefore, run the BSC6900 MML command
DEA UCELLEFACH (CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell Enhanced FACH parameters. Set Validation indication to
Deactivated; CME batch modification center: No supported) to deactivate enhanced CELLFACH before configuring this feature and Run the BSC6900 MML command ACT
UCELLEFACH (CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell Enhanced FACH parameters. Set Validation indication to Activated;
CME batch modification center: No supported) to reactivate enhanced CELL-FACH after
configuring this feature.
l By default, the number of HS-SCCH codes for each cell is 4. If the default number is used, the
HS-PDSCH can use only 14 SF16 codes. To enable the HS-PDSCH to use all 15 SF16 codes,
run the BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) to set the value of
Code Number for HS-SCCH to 1.
2.

Parameters in Batches) to set Allocate Code Mode to Manual(Manual) and Code
Number for HS-PDSCH to 15.
1.
Initialize UMTS monitoring on the BSC6900 LMT, as shown in Figure 122-1. Click
Submit. A real-time monitoring window is displayed.
Figure 122-1 Cell Performance Monitoring
2.
Check whether 15 SF16 codes are occupied by the HS-PDSCH in the Cell
Performance Monitoring window.
Expected result: The HS-PDSCH occupies 15 SF16 codes.
Issue 06 (2013-03-25)

427
RAN14.0
1.
----End
Example
//Verifying 15 Codes per Cell
MOD UCELLHSDPA: CellId=1, HsScchCodeNum=1;
MOD UCELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=15;
Issue 06 (2013-03-25)

428
RAN14.0
123 Configuring Time and HS-PDSCH Codes Multiplex
123
Configuring Time and HS-PDSCH

Codes Multiplex
WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
Prerequisites
l

License
Context
This feature enables the allocation of different codes in the same TTI to different users or the
multiplexing of the same code in different TTIs for different users to increase the code resource
utilization and system throughput.
Procedure
l
----End
Issue 06 (2013-03-25)

429
RAN14.0
124 Configuring HSDPA H-ARQ & Scheduling (MAX C/I,

RR, and PF)
124
Configuring HSDPA H-ARQ &
Scheduling (MAX C/I, RR, and PF)
WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).
Prerequisites
l

License
Context
Huawei provides multiple HSDPA scheduling algorithms such as maximum C/I (MAXCI),
round-robin (RR), proportional fair (PF), and Enhanced Proportional Fair (EPF).Before the
HSDPA feature is enabled, HARQ must be enabled and HSDPA scheduling algorithms must be
set.
Procedure
l
NOTE
l HSDPA H-ARQ is activated automatically without any configuration.

l This section describes how to set Max C/I, RR, and PF scheduling algorithms. For details on how to
set the EPF scheduling algorithm, see the description of the feature WRFD-01061103 Scheduling
based on EPF and GBR.
1.
Issue 06 (2013-03-25)
430
RAN14.0
124 Configuring HSDPA H-ARQ & Scheduling (MAX C/I,

RR, and PF)
3.17 Modifying Physical NodeB Parameters in Batches) to set the parameter

Scheduling Method to MAXCI(Max C/I Algorithm), RR(Round Robin
Algorithm) or PF(PF Algorithm).
l
1.
Run the NodeB MML command LST MACHSPARA to query the settings of the
parameter Scheduling Method.
----End
Example
SET MACHSPARA: LOCELL=0, SM=MAXCI;
Issue 06 (2013-03-25)

431
RAN14.0
125 Configuring HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation
125
Configuring HSDPA Static Code
Allocation and RNC-Controlled Dynamic Code

Allocation
WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code
Allocation.
Prerequisites
l

The feature WRFD-010610 HSDPA Introduction Package must be configured before
License
Context
This feature provides two code allocation strategies: HSDPA static code allocation and RNCcontrolled dynamic code allocation. When R99 and HSDPA services co-exist, this feature
enables full use of channelization code resources to expand system capacity.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches). In this step, set Allocate Code Mode to Manual or
Automatic.
432
RAN14.0
125 Configuring HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation
If Allocate Code Mode is set to Manual, set Code Number for HS-PDSCH to
specify the number of HS-PDSCH codes.
If Allocate Code Mode is set to Automatic, set Code Max Number for HSPDSCH to specify the maximum number of HS-PDSCH codes and set Code Min
Number for HS-PDSCH to specify the minimum number of HS-PDSCH codes.
l
1.
Run the BSC6900 MML command LST UCELLHSDPA to query code allocation
mode.
2.
On the BSC6900 LMT, click to display Cell Performance Monitoring. Set Monitor
Item to Cell Code Tree Monitor and click Submit. The Cell Performance Monitoring
tab page is displayed.
3.
View the number of codes allocated to the HS-PDSCH in the cell. If Allocate Code
Mode is set to Manual, the monitoring window of cell code tree usage shows that the
number of codes allocated to the HS-PDSCH remains unchanged. If Allocate Code
Mode is set to Automatic, the monitoring window of cell code tree usage shows that
the number of codes allocated to the HS-PDSCH varies with service access requests
in the cell. For example, the number of codes allocated to the HS-PDSCH increases
with the increase of HSDPA access requests and decreases with the decrease of
HSDPA access requests.
----End
Example
//Activating HSDPA Static Code Allocation and RNC-Controlled Dynamic Code
Allocation
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Manual, HsPdschCodeNum=5,
HsScchCodeNum=4;
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Automatic, HsPdschMaxCodeNum=5,
HsPdschMinCodeNum=1;
Issue 06 (2013-03-25)

433
RAN14.0
126
Configuring HSDPA Power Control
WRFD-01061004 HSDPA Power Control.
Prerequisites
l

License
Context
After an HSDPA service is introduced, the total downlink transmit power of each cell is classified
into common channel power, dedicated physical channel (DPCH) power, and power of HSDPA
physical channels (HS-PDSCH and HS-SCCH). To achieve high HSDPA performance, power
resources except those reserved for common channels are dynamically allocated to DPCHs and
HSDPA physical channels. For R99 services, the DPCH power can be adjusted by means of
inner-loop and outer-loop power control. HSDPA channel power resources can be dynamically
allocated and adjusted among users by using the NodeB scheduling algorithm.
HS-PDSCH power is controlled by the transport format and resource combination (TFRC)
algorithm and therefore does not require power control.
This feature enables operators to configure the appropriate power control mode of the HS-SCCH,
increasing the power efficiency and system capacity and improving the user experience.
Procedure
l
1.
Issue 06 (2013-03-25)
Activating the adaptive HS-SCCH power control based on the channel quality
indicator (CQI)
434
RAN14.0
2.

HSDPA Parameters; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches). In this step, set Allocate Code Mode to
Manual, Code Number for HS-PDSCH to 5, and Code Number for HSSCCH to 1.
b.
Run the NodeB MML command SET MACHSPARA (CME single

configuration: NodeB Configuration Express > IUB_NodeB > Radio Layer
> Locell Algorithm Parameters > MAC Parameters > MACHSPARA; CME
Batches). In this step, set HS-SCCH Power Control Method in CELL DCH
state to CQI.
Activating the fixed HS-SCCH power control

a.

HSDPA Parameters; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches). In this step, set Allocate Code Mode to
Manual, Code Number for HS-PDSCH to 5, and Code Number for HSSCCH to 1.
b.
Run the NodeB MML command SET MACHSPARA (CME single

> Locell Algorithm Parameters > MAC Parameters > MACHSPARA; CME
Batches). In this step, set HS-SCCH Power Control Method in CELL DCH
state to FIXED.
1.
2.
a.
Verifying the adaptive HS-SCCH power control based on the CQI

a.
Use an HSUPA-capable UE to set up a PS service over the HS-SCCH.
b.
Move the UE between the cell center and the cell edge to view the power change
on HS-SCCHs. Expected result: The HS-SCCH power changes with the CQI.
Verifying the fixed HS-SCCH power control

a.
Use an HSUPA-capable UE to set up a PS service over the HS-SCCH.
b.
Move the UE between the cell center and the cell edge to view the power change
on the HS-SCCH. Expected result: The HS-SCCH power remains unchanged.
----End
Example
//Activating HSUPA Power Control
//Setting the adaptive HS-SCCH power control based on the CQI
HsScchCodeNum=1;
SET MACHSPARA: LOCELL=111, HSSCCHPWRCMINDCH=CQI, HSSCCHFERTRGTINDCH=10;
//Setting the fixed HS-SCCH power control
Issue 06 (2013-03-25)

435
RAN14.0
HsScchCodeNum=1;
SET MACHSPARA: LOCELL=111, HSSCCHPWRCMINDCH=FIXED, SCCHPWR=0;
Issue 06 (2013-03-25)

436
RAN14.0
127
Configuring HSDPA Admission

Control
WRFD-01061003 HSDPA Admission Control.
Prerequisites
l

License
Context
This feature implements admission control over HSDPA users in the aspects such as the number
of HSDPA users, remaining power resources, Iub interface resources, and service rate thresholds.
This feature can ensure the QoS of existing HSDPA users while fully utilizing the resources.
Procedure
l
1.
Activate power resource admission.

Cell Parameters in Batches). In this step, set Uplink CAC algorithm switch and
Downlink CAC algorithm switch according to the network planning.
For HSDPA services, run the BSC6900 MML command MOD
Issue 06 (2013-03-25)

437
RAN14.0

Batches). In this step, select related admission algorithms in the Cell CAC
algorithm switch parameter. The available admission algorithms are
HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm), HSDPA_PBR_MEAS
(HSDPA PBR Meas Algorithm), and HSDPA_UU_ADCTRL(HSDPA UU
Load Admission Control Algorithm).
Modifying UMTS Cell Parameters in Batches) to set power resource admission
related parameters and the maximum number of HSDPA users.
NOTE
If HSDPA_PBR_MEAS(HSDPA PBR Meas Algorithm) is selected in Cell CAC algorithm

switch, set Hsdpa streaming PBR threshold and HSDPA best effort PBR threshold in this
step.
2.
Activate NodeB credit resource admission.

center: 3.15 Modifying RNC Parameters in Batches). In this step, select
NODEB_CREDIT_CAC_SWITCH in CAC algorithm switch.
Cell Parameters in Batches). In this step, select CRD_ADCTRL(Credit
Admission Control Algorithm) in Cell CAC algorithm switch.
3.
Activate Iub interface resource admission.

The Iub interface resource admission is mandatory and is activated automatically.
NOTE
Run the BSC6900 MML command MOD IPPATH (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > IP Path; CME batch modification
center: not supported) or MOD AAL2PATH (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > AAL2 Path; CME batch
modification center: not supported) to change the Iub interface bandwidth.
Issue 06 (2013-03-25)
1.
Enable two UEs UE1 and UE2 in idle mode to camp on the test cell, and the test cell
must support HSDPA.
2.
On the HLR, set PS service type to background or interactive.
3.
Run the BSC6900 MML command MOD UCELLCAC to set the maximum number
of HSDPA users to 1.
4.
Use UE1 to initiate an HSDPA PS service. After the service is set up successfully,
check the RRC_RB_SETUP message over the Uu interface. You can view that the
new-H-RNTI IE is under the rb-mappinginfo IE, and the value of the dlTransportChannel-Type IE is hsdsch.
5.
Use UE2 to initiate an HSDPA PS service. The service should fail to set up. Check
the RRC_RB_SETUP message over the Uu interface. You can view that the new-HRNTI IE is not under the rb-mappinginfo IE, and the value of the dlTransportChannel-Type IE is dch.
438
RAN14.0
6.
Release all the PS services.
7.
Run the BSC6900 MML command MOD UCELLCAC. In this step, set Maximum
HSDPA user number of the test cell to 64.
8.
Use UE1 and UE2 to initiate an HSDPA PS service.

Expected result: Services are set up successfully on UE1 and UE2.
1.
Deactivate power resource admission.

Parameters in Batches). In this step, set Uplink CAC algorithm switch and
Downlink CAC algorithm switch to ALGORITHM_OFF.
2.
Deactivate NodeB credit resource admission.

NODEB_CREDIT_CAC_SWITCH in Cell CAC algorithm switch.
Cell Parameters in Batches). In this step, select CRD_ADCTRL(Credit
Admission Control Algorithm) in Cell CAC algorithm switch.
3.
Deactivate Iub interface resource admission.

The Iub interface resource admission is mandatory and does not need to be deactivated.
----End
Example
NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1&HSDPA_GBP_MEAS-1&HSDPA_PBR_MEAS-1;
MOD UCELLCAC: CellId=11, HsdpaStrmPBRThd=70, HsdpaBePBRThd=30,
MaxHsdpaUserNum=64, MaxUlTxPowerforConv=24, MaxUlTxPowerforInt=24;
MOD UCELLCAC: CellId=11, UlHoCeResvSf=SF16, DlHoCeCodeResvSf=SF32;
Issue 06 (2013-03-25)

439
RAN14.0
128 Configuring Improvement of User Experience in Low

Traffic Service
128
Configuring Improvement of User

Experience in Low Traffic Service
WRFD-01061020 Improvement of User Experience in Low Traffic Service.
Prerequisites
l
Only BSC6900 support this feature.
The BTS3812E, BTS3812A, and BTS3812AE should be configured with the EULP,
EBBI, EBOI or EULPd board.

WRFD-010610 HSDPA Introduction Package
License
Context
l
The NodeB detects HSPA services with low traffic, such as gaming services and instant
messaging services (such as MSN).
The NodeB enables low traffic services to obtain more resources based on the scheduling
and flow control principles of HSPA, which reduces delay in low traffic services.
Procedure
Issue 06 (2013-03-25)

440
RAN14.0
128 Configuring Improvement of User Experience in Low

Traffic Service
1.
1.
Run the NodeB MML command SET UEQOSENHANCEPARA (CME single

Information > Radio Management > UEQOSENHANCEPARA; CME batch
modification center: not supported) to set the burst packet sizes of the gold, silver, and
copper users according to the actual conditions.
Run the NodeB MML command LST UEQOSENHANCEPARA to query the burst
packet sizes of the gold, silver, and copper users.
1.
Run the NodeB MML command SET UEQOSENHANCEPARA (CME single

Information > Radio Management > UEQOSENHANCEPARA; CME batch
modification center: not supported). In this step, set the burst packet sizes of the gold,
silver, and copper users to 0.
NOTE
When the burst packet size of a user is set to 0, it indicates that the NodeB stops identifying
the low traffic services of the user.
----End
Example
SET UEQOSENHANCEPARA: ULGOLDUEBPS=10, ULSILVERUEBPS=11, ULCOPPERUEBPS=12,
DLGOLDUEBPS=13, DLSILVERUEBPS=14, DLCOPPERUEBPS=15;
LST UEQOSENHANCEPARA:;
SET UEQOSENHANCEPARA: ULGOLDUEBPS=0, ULSILVERUEBPS=0, ULCOPPERUEBPS=0,
DLGOLDUEBPS=0, DLSILVERUEBPS=0, DLCOPPERUEBPS=0;
Issue 06 (2013-03-25)

441
RAN14.0
129
Configuring HSDPA Flow Control
WRFD-01061010 HSDPA Flow Control.
Prerequisites
l

License
Context
For each MAC-hs queue, HSDPA Flow Control calculates the pre-allocated Iub bandwidth based
on the Uu transmission rate and the amount of data buffered in the NodeB. The Uu transmission
rate of the MAC-hs queue is determined by the scheduling algorithm. For each MAC-hs queue,
if the Iub transmission rate is higher than the Uu transmission rate, the data packets are buffered.
Too much data buffered in the NodeB leads to transmission delay and even packet loss.
Therefore, each MAC-hs queue should not have too much data buffered in the NodeB. However,
it should retain a certain amount of data to prevent wasting the Uu resources due to not having
data to transmit.
The procedure for HSDPA Flow Control is briefly described as follows:
1.
The NodeB measures the buffered data amount of each MAC-hs queue and the average Uu
transmission rate.
2.
The NodeB estimates the buffering time based on the measurements.
3.
The NodeB adjusts the Iub bandwidth pre-allocated to the MAC-hs queue.
Procedure
Issue 06 (2013-03-25)

442
RAN14.0
1.
Run the NodeB MML command SET HSDPAFLOWCTRLPARA (CME single

configuration: NodeB Configuration Express > IUB_NodeB > ATM Transport
Layer > ATMPort > HSDPA Flow Control > HSDPA Flow Control
Parameters; CME batch modification center: not supported) to set the parameter
Flow Control Switch to enable the NodeB HSDPA flow control function. The
adaptive flow control algorithm is recommended.
There are four types of HSDPA flow control algorithm as follows:
When Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does
not adjust the available bandwidth for HSDPA users based on delay and packet
loss on the Iub interface. Then, subtracting Iub bandwidth used by R99 from Iub
bandwidth configured, the NodeB performs Iub shaping and distributes flow to
HSDPA users.
When Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB
adjusts the available bandwidth for HSDPA users based on delay and packet loss
on the Iub interface. Then, considering the data rate on the air interface, the NodeB
performs Iub shaping and distributes flow to HSDPA users.
When Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not
adjust the bandwidth based on delay and packet loss on the Iub interface. The
NodeB reports the conditions about the air interface to the RNC, and then the RNC
allocates the bandwidth.
When Flow Control Switch is set to BW_SHAPING_ONOFF_TOGGLE, the
flow control policy for the ports of the NodeB is either
DYNAMIC_BW_SHAPING or NO_BW_SHAPING in accordance with the
congestion detection mechanism of the NodeB. This flow control algorithm is
recommended.
1.
Choose Monitor > UMTS Monitoring > Connection Performance Monitoring on

the BSC6900 LMT. Create UL Throughput Bandwidth and DL Throughput
Bandwidth tasks.
2.
Assume that the current Iub bandwidth is 4 MHz and the bandwidth usage is 80%.
Enable an HSDPA-capable UE1 to access the network and originate a PS service.
Record the throughput of UE1.
Expected result:
The throughput of UE1 is 3.2 Mbps.
3.
Enable an HSDPA-capable UE2 to access the network (with the same configuration
as UE1) and originate a download service. Record the throughput of the two UEs.
Expected result:
The throughput of UE1 decreases after UE2 accesses the network. When the
throughput of the two UEs is stable, the total bandwidth of the two UEs is 4 MHz. If
user priority, service type and Security Parameter Index (SPI) of the two UEs are the
same, the final ratio of the two UEs' throughput is 1:1.
You can deactivate the current algorithm by selecting one of the other flow control
algorithms.
----End
Issue 06 (2013-03-25)

443
RAN14.0
Example
//Activating HSDPA Flow Control and setting the flow control mode to
adaptive flow control
SET HSDPAFLOWCTRLPARA: SRN=0, SN=6, BEAR=ATM, SBT=BASE_BOARD, PT=IMA,
PN=0, SWITCH= BW_SHAPING_ONOFF_TOGGLE, TD=2, DR=1, ITM=TERRESTRIAL;
Issue 06 (2013-03-25)

444
RAN14.0
130
Configuring HSDPA Mobility

Management
WRFD-01061006 HSDPA Mobility Management.
Prerequisites
l

License
Context
This feature enables an HSDPA-capable UE to be handed over to an R99 cell or another HSDPA
cell.
This feature also enables an HSDPA-capable UE to change cells with a small probability of
service interruption.
Procedure
l
1.
The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers

are the same for HSDPA users and R99 users. For details, see the following sections:
Issue 06 (2013-03-25)

445
RAN14.0

l
None
----End
Issue 06 (2013-03-25)

446
RAN14.0
131 Configuring HSDPA UE Category 1 to 28
131
Configuring HSDPA UE Category 1

to 28
WRFD-01061002 HSDPA UE Category 1 to 28.
Prerequisites
l

License
Context
This feature can provide proper HSDPA services for the UEs of category 1 to category 28.
Procedure
l
----End
Issue 06 (2013-03-25)

447
RAN14.0
132
Configuring DL 16QAM Modulation
DL 16QAM Modulation.
Prerequisites
l

License
Other Prerequisites
The UE should have the capability of HSDPA besides Category 11 and Category
12:category 1,2,3,4,5,6,7,8,9,10,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28.
Context
Compared with QPSK, 16QAM is a higher-order downlink data modulation scheme. This feature
enables the peak rate on the Uu interface to reach 14.4 Mbit/s.
l
The HS-PDSCH is used to carry the HS-DSCH data. The HS-PDSCH may use QPSK or
16QAM modulation symbols.
When the UE is in poor radio environment, the transmission can adopt the low-order QPSK
modulation mode and small transport blocks to ensure communication quality.
When the UE is in good radio environment, the transmission can adopt the high-order
16QAM modulation mode and large transport blocks to achieve high peak rate.
The UE of category 10 can support a maximum of 15 HS-PDSCH codes and 16QAM

modulation mode. The supported peak rate on the air interface can reach 14.4 Mbit/s.
Procedure
Issue 06 (2013-03-25)

448
RAN14.0

NOTE
HSDPA Introduction Package must be activated before activating this feature. For the method of
activating HSDPA Introduction Package, see the section "Configuring HSDPA Introduction
Package."
1.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set 16QAM
Switch to OPEN(open).
NOTE
l For the 16QAM modulation of the HSDPA UE, the NodeB license control item must be enabled.
l As defined in 3GPP 25.306, the UE in category 8 can support both QPSK and 16QAM modulation
schemes. Only 16QAM modulation, however, enables the throughput of category 8 UE to reach
5 Mbit/s.
NOTE
Only in case of good environment quality of the channel, the throughput of category 8 UE can
reach 5 Mbit/s.
Perform the following steps to check whether the download rate can reach 5 Mbit/s.
1.
Use the UE to start a PS interactive service of DL 7200 kbit/s. The PS service is carried
on the HS-DSCH. The UE keeps in Cell-DCH state.
2.
Start FTP (10 threads) to download given files, which are larger than 1 GB. By
monitoring the DL throughput and bandwidth, you find that the PS downloading
service is normal and the bit rate is higher than 5 Mbit/s.
1.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set 16QAM
Switch to CLOSE(close).
----End
Example
//Activating procedure
SET MACHSPARA: CME16QAMSW=OPEN;
//Deactivating procedure
SET MACHSPARA: CME16QAMSW=CLOSE;
Issue 06 (2013-03-25)

449
RAN14.0
133
Configuring Dynamic Code

Allocation Based on NodeB
Dynamic Code Allocation Based on NodeB.
Prerequisites
l

License
Context
This feature implements dynamic code allocation on the NodeB side. The NodeB adjusts the
allocation of code resources in each TTI according to available code resources and scheduling
algorithms. This feature can further improve the utilization of code resources.
Procedure
l
NOTE
HSDPA Introduction Package must be activated before activating this feature. For the method of
activating HSDPA Introduction Package, see the section "Configuring HSDPA Introduction
Package."
1.
l
Issue 06 (2013-03-25)
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set Dynamic
Code Switch to OPEN(open).
450
RAN14.0
1.
Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic
Code Switch to CLOSE(close).
2.
Run the BSC6900 MML command MOD UCELLHSDPA.

set Allocate Code Mode to Manual.
set Code Number for HS-PDSCH to 5.
3.
Use a UE that belongs to category 8 or is capable of higher HSDPA performance to

download 200 MB files from the FTP server in the serving cell.
4.
Select Service > Trace Management > Interface Trace Task > User from the
navigation tree in Maintenance tab on NodeB LMT, select (DL)Hsdpa User
Enhanced Schedule Data message, as shown in Figure 133-1.
Figure 133-1 User Tracing
5.
Issue 06 (2013-03-25)
To query the ucMaxPdschCodeNum is 5, as shown in Figure 133-2.

451
RAN14.0
Figure 133-2 Message Browser
Issue 06 (2013-03-25)
6.
Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic
Code Switch to OPEN(open).
7.
Trace (DL)Hsdpa User Enhanced Schedule Data message,

ucMaxPdschCodeNum is less than the value of 5, it indicates the feature has been
enabled. as shown in Figure 133-3.

452
RAN14.0
Figure 133-3 Message Browser
1.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set Dynamic
Code Switch to CLOSE(close).
----End
Example
//Operations on the NodeB side
SET MACHSPARA: DYNCODESW=OPEN;
SET MACHSPARA: DYNCODESW=CLOSE;
MOD UCELLHSDPA: CellId=0, AllocCodeMode=Manual, HsPdschCodeNum=5;
SET MACHSPARA: DYNCODESW=OPEN;
SET MACHSPARA: DYNCODESW=CLOSE;
Issue 06 (2013-03-25)

453
RAN14.0
134
Configuring HSDPA Enhanced

Package
HSDPA Enhanced Package.
Prerequisites
l

License
Other Prerequisites
UE should support the functions connected with HSDPA Enhanced package.
Context
HSDPA enhanced package is introduced on the basis of WRFD-010610 HSDPA Introduction
Package, and provides enhancement features to meet the QoS and HSDPA network
requirements. Related features include:
l
WRFD-01061103 Scheduling based on EPF and GBR
WRFD-01061111 HSDPA State Transition
WRFD-01061112 HSDPA DRD
WRFD-01061113 HS-DPCCH Preamble Support
For details about activate, verify, and deactivate procedures, see the following sections:
Procedure
Issue 06 (2013-03-25)

454
RAN14.0

NOTE
HS-DPCCH Preamble Support does not need to be activated, verified, or deactivated.
----End
Issue 06 (2013-03-25)

455
RAN14.0
135
Configuring Scheduling based on

EPF and GBR
WRFD-01061103 Scheduling based on EPF and GBR.
Prerequisites
l

License
Context
The operator can set different QoS parameters such as priority, weight, and Guaranteed Bit Rate
(GBR) for different users. Based on the QoS parameters, the Enhanced Proportional Fair (EPF)
algorithm can accurately allocate resources by proportion. This feature allows different users to
obtain accurate differentiated experiences.
Procedure
l
1.
1.
Run the NodeB MML command LST MACHSPARA to check that Scheduling
Method is set to EPF.
1.
Issue 06 (2013-03-25)
Scheduling Method to EPF(Enhanced PF).
456
RAN14.0
Scheduling Method to an option other than EPF(Enhanced PF).
----End
Example
LST MACHSPARA;
SET MACHSPARA: SM=PF;
Issue 06 (2013-03-25)

457
RAN14.0
136
Configuring HSDPA State Transition
WRFD-01061111 HSDPA State Transition.
Prerequisites
l

The feature WRFD-010610 HSDPA Introduction Package has been configured before
License
Context
l
This feature enables the switching between the DCH and HS-DSCH and makes it possible
for UEs to enjoy high-speed services.
This feature also enables a UE with an ongoing BE service or streaming service to move
to the CELL_FACH state to save system resources when the UE does not have data
transmission for a long period.
Procedure
1.
l
Issue 06 (2013-03-25)

DRA_HSDPA_STATE_TRANS_SWITCH and
DRA_PS_BE_STATE_TRANS_SWITCH check boxes under the parameter
458
RAN14.0
1.
Log in to the BSC6900 LMT and initiate Uu interface message tracing.
2.
Set up an HSDPA BE service, and do not perform any data operation for a period of
time. Then, search for the RRC_RB_RECFG in the traced Uu interface message.
Check the traced data to ensure that the value of the IE rrc-StateIndicator is cell-FACH
(1), as shown in Figure 136-1.
Figure 136-1 RRC_RB_RECFG message
1.

DRA_HSDPA_STATE_TRANS_SWITCH and
DRA_PS_BE_STATE_TRANS_SWITCH check boxes under the parameter
----End
Example
//Activating HSDPA State Transition
DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-1&DRA_PS_BE_STATE_TRANS_SWITCH-1;
//Deactivating HSDPA State Transition
DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_PS_BE_STATE_TRANS_SWITCH-0;
Issue 06 (2013-03-25)

459
RAN14.0
137
Configuring HSDPA DRD
WRFD-01061112 HSDPA DRD.
Prerequisites
l

WRFD-010610 HSDPA Introduction Package and WRFD-020400 DRD Introduction
Package.
License
Context
This feature enables HSDPA-suitable services to be established on the HS-DSCH cell as much
as possible if a UE is HS-DSCH capable, achieving better service performance.
Procedure
l
1.

Parameters in Batches). In this step, set Direct retry switch to
DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH
NOTE
The DR_RAB_SING_DRD_SWITCH and the DR_RAB_COMB_DRD_SWITCH can be

turned on at the same time according to the network plan.
l
Issue 06 (2013-03-25)
460
RAN14.0
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to check

whether DR_RAB_SING_DRD_SWITCH or
DR_RAB_COMB_DRD_SWITCH is set to ON.
Expected result: The value of DR_RAB_SING_DRD_SWITCH or
DR_RAB_COMB_DRD_SWITCH is ON.
2.
Run the BSC6900 MML command LST UINTERFREQNCELL to query the interfrequency neighboring cells of cell 1 and whether Blind handover flag is set to
TRUE. If Blind handover flag is set to FALSE, run the BSC6900 MML
command MOD UINTERFREQNCELL. In this step, set Blind Handover Flag of
cell 2 (inter-frequency neighboring cell of cell 1) to TRUE. If Blind handover flag
is set to TRUE, go to Step 3.
3.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set
DL BE traffic threshold on HSDPA to an appropriate value.
4.
Run the BSC6900 MML command MOD UCELLCAC. In this step, set Maximum
HSDPA user number of cell 1 to 0.
5.
Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set
HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) to Cell
CAC algorithm switch.
6.
Enable the UE in cell 1 to originate a PS FTP download service. The value of

Maximum HSDPA user number in cell 1 is 0; therefore, the UE is handed over to
cell 2 by using directed retry. The Uu message tracing or the UE CDT tracing shows
that the RRC_RB_RECFG/RRC_RB_SETUP message is sent to the UE in cell 1 and
the RRC_RB_RECFG_CMP/RRC_RB_SETUP_CMP message is sent to the RNC in
cell 2.
NOTE
This feature also supports the following scenario: If a UE in an R99 cell (cell 1) originates HSDPA
streaming services or BE services, the UE can camp on an HSDPA cell (cell 2) through directed
retry. In this scenario, cell 2 is the inter-frequency neighboring cell for blind handover of cell 1 and
admission to cell 2 is allowed.
1.
The feature does not need to be deactivated.
----End
Example
//Activating HSDPA DRD
SET UCORRMALGOSWITCH: DrSwitch= DR_RAB_SING_DRD_SWITCH-1;
SET UCORRMALGOSWITCH: DrSwitch= DR_RAB_COMB_DRD_SWITCH-1;
//Verifying HSDPA DRD
MOD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=1, NCellId=2,
BlindHoFlag=TRUE;
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D384;
MOD UCELLCAC: CellId=1, MaxHsdpaUserNum=0;
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1;
Issue 06 (2013-03-25)

461
RAN14.0
138
Configuring HS-DPCCH Preamble

Support
WRFD-01061113 HS-DPCCH Preamble Support.
Prerequisites
l
Dependency on RNC
This feature does not depend on the RCN hardware.
Dependency on NodeB
The BTS3812E, BTS3812A and BTS3812AE must be configured with EBBI board,
EBOI board, EULP or EULPd board.
The BBU3806 needs to configure EBBC or EBBCd board.
The BBU3900 needs to configure WBBPb ,WBBPd or WBBPf board.

WRFD-010610 HSDPA Introduction Package.
License
Others
The UE should have the capability of HSDPA Category 6 (or later) and support this
feature.
Context
This feature enables the transmission of dedicated preamble subframes before ACK/NACK
subframes are transmitted on the HS-DPCCH, improving transmission reliability.
Issue 06 (2013-03-25)

462
RAN14.0
Procedure
l
1.
Run the BSC6900 MML command ADD UCELLHSDPA (CME single

Parameters in Batches) or Run the BSC6900 MML command MOD
UCELLHSDPA (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell HSDPA Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches). In this step, set HARQ Preamble
Capability Indication to Mode1.
1.
Start UE message tracing on the BSC6900 LMT, and verify the value of the
information element (IE) harq-Preamble-Mode contained in the message
RRC_RRC_CONN_SETUP.
The expect result: The value of the information element (IE) harq-Preamble-Mode
is 1. As shown in Figure 138-1.
Figure 138-1 harq-Preamble-Mode
1.
Issue 06 (2013-03-25)

463
RAN14.0
Parameters in Batches) or Run the BSC6900 MML command MOD
Modifying UMTS Cell Parameters in Batches). In this step, set HARQ Preamble
Capability Indication to Mode0.
----End
Example
//Activation Procedure
ADD UCELLHSDPA: CellId=0,
MOD UCELLHSDPA: CellId=0,
//Deactivation Procedure
ADD UCELLHSDPA: CellId=0,
MOD UCELLHSDPA: CellId=0,
Issue 06 (2013-03-25)
HsdpcchPreambleSwitch=Mode1;

464
RAN14.0
139
Configuring Streaming Traffic Class

on HSDPA
Streaming Traffic Class on HSDPA.
Prerequisites
l

feature depends on the feature WRFD-010611 HSDPA Enhanced Package.
License
Context
This feature enables the streaming services to be mapped onto the HS-DSCH, which improves
the utilization of cell resources.
Procedure
l
1.
1.
Issue 06 (2013-03-25)

Parameters in Batches) to select MAP_PS_STREAM_ON_HSDPA_SWITCH from
the drop-down list Service mapping strategy switch.
Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 139-1.

465
RAN14.0
2.
Establish an HSDPA streaming service on the UE. To check whether the establishment
is successful, view the RRC_RB_SETUP message and check whether the dlTransportChannelType in the rb-MappingInfo information element (IE) is set to
hsdsch in the Uu interface trace data.
3.
Check whether the service can receive the data successfully.
1.

Parameters in Batches) to clear MAP_PS_STREAM_ON_HSDPA_SWITCH from
the drop-down list Service mapping strategy switch.
----End
Example
//Activating Streaming Traffic Class on HSDPA
//Deactivating Streaming Traffic Class on HSDPA
Issue 06 (2013-03-25)

466
RAN14.0
140
Configuring HSDPA over Iur
HSDPA over Iur.
Prerequisites
l

License
Other Prerequisites
The neighboring RNC supports this feature.
Context
This feature enables HSDPA services to be carried on the Iur interface and provides continuous
HSDPA services for UEs moving between BSC6900s.
Procedure
l
Issue 06 (2013-03-25)
1.

to configure the neighboring RNC's cell with HSDSCH and Fractional-Dedicated
Physical Control Channel (F-DPCH). In this step, select the HSDSCH support
indicator and F-DPCH support indicator check boxes under the parameter Cell
Capability Container.
2.
467
RAN14.0
modification center: not supported). In this step, set Hsdpa cap ind over IUR for
NRNC to ON.
l
1.
Verify that the feature HSDPA over Iur has been activated by performing the following
operations:
Run the BSC6900 MML command LST UNRNC to query the configuration of
the neighboring RNC.
Run the BSC6900 MML command LST UEXT3GCELL to query the
configuration of the neighboring RNC's cell.
2.
Verify that an HSDPA service has been set up by performing the following operations:
Configure the neighboring RNC and its cell with the HSDPA function.
Establish an HSDPA service under the serving RNC.
The serving cell changes to a cell under the neighboring RNC.
If the RNSAP_RL_SETUP_REQ message traced on the Iur interface contains
HSDPA-related information elements, an HSDPA service has been set up
successfully.
1.
modification center: not supported). In this step, set Hsdpa cap ind over IUR for
NRNC to OFF.
2.

modification center: 3.19 Modifying RNC External Cell Parameters in Batches).
In this step, deselect the HSDSCH support indicator and F-DPCH support
indicator check boxes under the parameter Cell Capability Container.
----End
Example
//Activating HSDPA over Iur
CellCapContainerFdd=HSDSCH_SUPPORT-1&FDPCH_SUPPORT-1;
MOD UNRNC: NRncId=1, IurHsdpaSuppInd=ON;
//Deactivating HSDPA over Iur
MOD UNRNC: NRncId=1, IurHsdpaSuppInd=OFF;
CellCapContainerFdd=HSDSCH_SUPPORT-0&FDPCH_SUPPORT-0;
Issue 06 (2013-03-25)

468
RAN14.0
141
Configuring SRB over HSDPA
SRB over HSDPA.
Prerequisites
l
Requirement for the BSC6900
Requirements for the NodeB
or EDLP board.
The BBU3900 is configured with the WBBPb, WBBPd or wBBPf board.

The WRFD-010610 HSDPA Introduction Package feature must be configured before
License
Others
The UE complies with the specifications of 3GPP Release 6 or higher versions and
supports fractional DPCH (F-DPCH) or E-FDPCH.
Context
Using F-DPCH multiplexing, this feature enables downlink signaling radio bearers (SRBs) of
multiple users to be carried over HSDPA. This helps reduce downlink code resource
consumption and call setup delay.
During radio access bearer (RAB) setup, SRBs can be carried over HSDPA only when all the
downlink services of the UE are carried on the HSDPA channels. During radio resource control
(RRC) connection setup, this feature can be activated by performing the following operations:
Issue 06 (2013-03-25)

469
RAN14.0
Procedure
l
1.

Channel Preferably Carrying Signaling RB to HSDPA
(UL_DCH,DL_HSDSCH) or HSPA(UL_EDCH,DL_HSDSCH).
2.

modification center: 3.15 Modifying RNC Parameters in Batches) to set the phase
at which this feature is activated by means of the Effective Flag of Signaling RB
Channel Type parameter.
NOTE
l If Effective Flag of Signaling RB Channel Type is set to False, this feature is activated during
RAB setup. Recommended Value is False.
l If Effective Flag of Signaling RB Channel Type is set to TRUE, this feature is activated during
RRC connection setup.
3.

Parameters in Batches) to set the E_F_DPCH is activated by means of the Cell Hspa
Enhanced function switch parameter.
NOTE
l If Cell Hspa Enhanced function switch is set to E_F_DPCH_ON, E_F_DPCH is enabled.

l If Cell Hspa Enhanced function switch is set to E_F_DPCH_OFF, E_F_DPCH is disabled.
1.
Issue 06 (2013-03-25)
Log in to the BSC6900 LMT to enable Uu interface tracing. In the displayed dialog
box, select RRC_RB_SETUP, as shown in Figure 141-1.

470
RAN14.0
2.
To verify whether this feature is activated , view the information element (IE) dlTransportChannelType and rb-Identity in the RRC_RB SETUP message from the
Uu interface trace data.
If the value of dl-TransportChannelType is hsdsch, as shown in Figure 141-2,
and the value of rb-Identity is less than or equal to 4, as shown in Figure 141-3,
Figure 141-2 Value of the dl-TransportChannelType IE
Issue 06 (2013-03-25)

471
RAN14.0
Figure 141-3 Value of the rb-Identity IE
1.

Channel Preferably Carrying Signaling RB to HSUPA or DCH.
----End
Example
//Activating SRB over HSDPA
//Setting the type of channel on which SRBs are preferably carried with
SrbChlType set to HSDPA
SET UFRCCHLTYPEPARA: SrbChlType=HSDPA;
SrbChlTypeRrcEffectFlag set to False
SET UFRCCHLTYPEPARA: SrbChlTypeRrcEffectFlag=False;
//setting the E_F_DPCH function
MOD UCELLALGOSWITCH: CellId=1, HspaEnhSwitch=E_F_DPCH_ON;
//Deactivating SRB over HSDPA
SrbChlType set to DCH
SET UFRCCHLTYPEPARA: SrbChlType=DCH;
Issue 06 (2013-03-25)

472
RAN14.0
142 Configuring CQI Adjustment Based on Dynamic BLER

Target
142
Configuring CQI Adjustment Based

on Dynamic BLER Target
CQI Adjustment Based on Dynamic BLER Target.
Prerequisites
l
The BTS3812E and BTS3812AE are configured with the EBBI, EBOI, or EDLP board.

License
Context
With this feature, the NodeB can dynamically select the optimum BLER target value based on
the channel quality fluctuation of HSDPA users. The NodeB then adjusts the Channel Quality
Indicator (CQI) accordingly, improving user throughput and cell throughput.
Procedure
l
1.
l
Issue 06 (2013-03-25)
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set CQI
Adjust Algorithm Switch of non-Conversational Service to
CQI_ADJ_BY_DYN_BLER(CQI Adjusted by Dynamic BLER).
473
RAN14.0
142 Configuring CQI Adjustment Based on Dynamic BLER

Target
1.
Run the NodeB MML command LST MACHSPARA. In this step, check that CQI
Adjust Algorithm Switch of non-Conversational Service is set to
CQI_ADJ_BY_DYN_BLER.
1.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set CQI
Adjust Algorithm Switch of non-Conversational Service to NO_CQI_ADJ(Not
CQI Adjust Algorithm).
----End
Example
//Activating CQI Adjustment Based on Dynamic BLER Target
SET MACHSPARA: LOCELL=0, CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER;
//Verifying CQI Adjustment Based on Dynamic BLER Target
//Deactivating CQI Adjustment Based on Dynamic BLER Target
SET MACHSPARA: CQIADJALGOFNONCON=NO_CQI_ADJ;
Issue 06 (2013-03-25)

474
RAN14.0
143
Configuring MIMO Prime
This chapter describes how to activate, verify, and deactivate the basic feature WRFD-030011
MIMO Prime.
Prerequisites
l
This feature is supported only by the 40W RRU3801C, RRU3804, RRU3806,
RRU3808, WRFU, RRU3805, WRFUd, RRU3828, RRU3829, RRU3928, RRU3929,
MRFUd, MRFUe, as well as the RRU3908 V1 operating in 850 MHz, 900 MHz, and
1900 MHz.
For RF modules providing only one transmit channel, two such RF modules need to be
interconnected to support this feature.
Two RF units, each with a TX channel, are configured.
The BTS3812E/AE does not support this feature.
The DBS3800 does not support this feature.
RRU3908 V2 and MRFU V2 modules support this feature from RAN14.0.0

License
Context
l
Issue 06 (2013-03-25)
MIMO Prime can increase the capacity of the cell in which MIMO has not been
implemented by 5% to 10%. The increase in the overall cell throughput helps to greatly
improve the experience of users in medium and bad radio conditions. MIMO Prime is
applicable to various services such as HSDPA and 64QAM, whereas it does not have any
special requirement for the capabilities of UEs and will not affect the performance of UEs
that do not support MIMO.

475
RAN14.0
Procedure
l
1.
Run the BSC6900 MML command DEA UCELL (CME single configuration: UMTS
Set Validation indication to Deactivated; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to deactivate cells.
2.
On the NodeB, remove the old local cell and establish a new local cell.
Run the NodeB MML command RMV LOCELL (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Radio Layer > xx Sector >
Locell; CME batch modification center: not supported) to remove the local cell
b.
Run the NodeB MML command ADD LOCELL (CME single configuration:
Locell; CME batch modification center: 3.17 Modifying Physical NodeB
Parameters in Batches) to add a local cell. In this step, set Support VAM to
TRUE(TRUE), Two Tx Way to FALSE.
3.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set MIMO
Prime Switch to OPEN(open).
4.
1.
Run the NodeB MML command LST LOCELL. In this step, check that Support
VAM is TRUE(TRUE), Two Tx Way is FALSE.
2.
Run the NodeB MML command LST MACHSPARA. In this step, check that MIMO
Prime Switch is set to Open.
3.
Observe the counters VS.APCPhase0CQI.MEAN and VS.APCCQI.MEAN.

Before this feature is activated, the values of both counters are 0. After this feature is
activated, the values of both counters differ from 0.
1.
Modifying UMTS Cell Parameters in Batches) to deactivate cells.
2.
3.
Issue 06 (2013-03-25)
a.
a.
Locell; CME batch modification center: not supported) to remove the local cell
b.
Parameters in Batches) to add a local cell. In this step, set Support VAM to
FALSE(FALSE).
476
RAN14.0
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set MIMO
Prime Switch to CLOSE(close).
4.
----End
Example
//Activating MIMO Prime
//Operations at the BSC6900
//Deactivating a cell
//Removing a local cell
RMV LOCELL: LOCELL=1;
//Adding a local cell and setting Two Tx Way and VAM
ADD LOCELL: LOCELL=1, STN=0, SECN=2, SECT=REMOTE_SECTOR, TTW=FALSE,
SRN1=60, SRN2=61, SN2=0, ULFREQ=9845, DLFREQ=10795, MXPWR=460,
HISPM=FALSE, RMTCM=FALSE, VAM=TRUE;
//Activating MIMO Prime
SET MACHSPARA: LOCELL=1, MIMOPRIMESW=OPEN;
//Verifying MIMO Prime
//Deactivating MIMO Prime
//Deactivating a cell
HISPM=FALSE, RMTCM=FALSE, VAM=FALSE;
SET MACHSPARA: LOCELL=1, MIMOPRIMESW=CLOSE;
Issue 06 (2013-03-25)

477
RAN14.0
144 Configuring Adaptive Configuration of Typical HSPA

Rate
144
Configuring Adaptive Configuration

Adaptive Configuration of Typical HSPA Rate.
Prerequisites
l
The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EBBI,
EBOI, EULP+EDLP, or EULPd+EDLP boards. Downlink services must be established
on the EBBI, EBOI, or EDLP board.
The DBS3800 must be configured with the EBBC or EBBCd board. Downlink services
must be established on the EBBC or EBBCd board.
The 3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf
board. Downlink services must be established on the WBBPb, WBBPd, or WBBPf
board.

The features WRFD-010610 HSDPA Introduction Package and WRFD-010612
HSUPA Introduction Package have been configured before this feature is activated.
License
Context
PS BE services carried on an HSPA channel use typical rate rather than the CN-assigned rate as
the maximum rate, leading to inconsistent between the CN-assigned rate and the actual rate.
This feature enables the users to apply the CN-assigned rate rather than the typical rate when
they are different.
l
Precautions
None
l
Issue 06 (2013-03-25)
Data Preparation
478
RAN14.0
144 Configuring Adaptive Configuration of Typical HSPA

Rate
Parameter Name
Parameter ID
Setting
Description
Source
PS Rate
Negotiation Switch
PsSwitch
The
HSPA_ADPTIVE
_RATE_ALGO_S
WITCH should be
selected.
Network plan
Procedure
l
1.

Parameters in Batches) to enable this feature. In this step, select the
HSPA_ADPTIVE_RATE_ALGO_SWITCH check box under the parameter PS
Rate Negotiation Switch.
1.
Before the feature is activated, the CN assigns a non-typical rate for a PS BE service
to be carried on an HSPA channel. Check the real rate.
The PS BE service is set up successfully on an HSPA channel with a typical rate.
2.
After the feature is activated, the CN assigns a non-typical rate for a PS BE service to
be carried on an HSPA channel. Check the real rate.
The PS BE service is set up successfully on an HSPA channel with the assigned rate.
1.

Parameters in Batches) to disable this feature. In this step, clear the
HSPA_ADPTIVE_RATE_ALGO_SWITCH check box under the parameter PS
Rate Negotiation Switch.
----End
Example
//Activating Adaptive Configuration of Typical HSPA Rate
//Enabling Adaptive Configuration of Typical HSPA Rate
SET UCORRMALGOSWITCH: PsSwitch=HSPA_ADPTIVE_RATE_ALGO_SWITCH-1;
//Deactivating Adaptive Configuration of Typical HSPA Rate
//Disabling Adaptive Configuration of Typical HSPA Rate
SET UCORRMALGOSWITCH: PsSwitch=HSPA_ADPTIVE_RATE_ALGO_SWITCH-0;
Issue 06 (2013-03-25)

479
RAN14.0
145
Configuring HSDPA Scheduling

Based on UE Location
HSDPA Scheduling Based on UE Location.
Prerequisites
l


All 3900 series base stations support this feature. To support this feature, the 3900 series
base stations must be configured with the WBBPb, WBBPd or WBBPf board.
All DBS3800 series base stations support this feature. To support this feature, the
DBS3800 series base stations must be configured with the EBBC or EBBCd board.
The BTS3812E/BTS3812A/BTS3812AE supports this feature. To support this feature,
the BTS3812E/BTS3812A/BTS3812AE must be configured with the EBBI, EDLP or
EBOI board.

This feature depends on the following features:
WRFD-010611 HSDPA Enhanced Package
License
As recommended, GBRs have been configured on the RNC for all BE services.
Context
l
Issue 06 (2013-03-25)
Developed on the basis of the EPF algorithm, this feature considers UE locations as the
criterion for adjusting HSDPA scheduling weights. This feature gives more scheduling
opportunities to UEs close to the NodeB and increases the cell throughput on the downlink.
480
RAN14.0
Precautions
With this feature, HSDPA UEs at cell edges have fewer scheduling opportunities and
the cell throughput at cell edges drops. If GBRs are not configured for BE services,
HSDPA UEs at cell edges may have to wait a long time before they can get scheduling
opportunities. As a result, traffic radio bearers (TRBs) are more likely to reset and the
call drop rate increases. The magnitude of this impact depends on factors such as UE
distribution and service distribution in the cell. It is recommended that GBRs be
configured for BE services to ensure network performance.
Procedure
l
1.
1.
Run the NodeB MML commandSET MACHSPARA (CME single configuration:

Scheduling Method to EPF_LOC(Location based EPF) and set Location
Weight.
Run the NodeB MML commandLST MACHSPARA. If the command output shows
that the value of Scheduling Method is EPF_LOC(Location based EPF), this
feature has been activated for the cell.
1.
Run the NodeB MML commandSET MACHSPARA (CME single configuration:

Scheduling Method to a value except EPF_LOC(Location based EPF).
----End
Example
SET MACHSPARA: LOCELL=1, SM=EPF_LOC, LOCWEIGHT=1;
SET MACHSPARA: LOCELL=1, SM=EPF;
Issue 06 (2013-03-25)

481
RAN14.0
146 Configuring Adaptive Adjustment of HSUPA Small

Target Retransmissions
146
Configuring Adaptive Adjustment of
HSUPA Small Target Retransmissions
Adaptive Adjustment of HSUPA Small Target Retransmissions.
Prerequisites
l
None

This feature depends on WRFD-010612 HSUPA Introduction Package.
License
None
Context
l
With this feature, the target number of retransmissions can shift between two preset values.
In scenarios where a small target number of retransmissions are desired on the E-DCH, the
larger one between the two preset values is used as the target number of retransmissions.
When the uplink load on the cell is not restricted and the UE rate is above a specific
threshold, the smaller one between the two preset values is used as the target number of
retransmissions. This improves the UE throughput. When the uplink load on the cell is
restricted again and the UE rate falls below another threshold, the larger one between the
two preset values is again used as the target number of retransmissions to raise the uplink
throughput of the cell.
This feature is only intended for non-DC-HSUPA UEs.
This feature provides two algorithms for configuring the small target number of
retransmissions: algorithm for selecting an initial small target number of retransmissions
for HSUPA UEs and algorithm for adaptively adjusting the small target number of
retransmissions for HSUPA UEs.
Precautions
None
l
Issue 06 (2013-03-25)
Data Preparation
482
RAN14.0

Parameter Name
Parameter ID
Setting
Description
Source
Power Control
Switch
PcSwitch
The
PC_OLPC_SWIT
CH,
PC_HSUPA_LIT
RETNUM_INIT_
SEL_SWITCH
and
PC_HSUPA_LIT
RETNUM_AUTO
_ADJUST_SWIT
CH should be
selected.
Network plan
Procedure
l
1.

Parameters in Batches) with PC_OLPC_SWITCH under Power Control Switch
selected to enable outer-loop power control.
NOTE
You need to activate outer loop power control before activating the adaptive adjustment of
HSUPA small target retransmissions.
2.

Parameters in Batches) with
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH and
PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWITCH under Power Control
Switch selected to activate the algorithm for selecting an initial small target number
of retransmissions for HSUPA UEs.
NOTE
When configuring the parameter Alter Edch Little Target Number of E-DCH PDU
retransfer, the default value for this parameter is recommended. An inappropriate value for
this parameter may lead to decreased cell throughput. For services with a 5.44 Mbit/s MBR
and a 2 ms transmission time interval (TTI), the default value of this parameter is 0.02. For
other services with a 2 ms TTI, the default value of this parameter is 0.01. For services with a
10 ms TTI, the default value of this parameter is 0.1.
Issue 06 (2013-03-25)
1.
On the BSC6900 LMT main page, click Monitor. In the Monitor Navigation Tree
pane, choose Monitor > UMTS Monitoring > Connection Performance
2.
In this dialog box, set Monitor Item to OLPC,and then click Submit. Check the
average number of transmissions on the E-DCH. If the following conditions are met,
483
RAN14.0

If there are multiple HSUPA UEs, the uplink load of the cell is limited and the
average number of transmissions on the E-DCH is close to the larger value between
EdchTargetLittleRetransNum and EdchAltTarLittleRetransNum.
If there are multiple HSUPA UEs, the uplink load of the cell is unlimited and the
average number of transmissions on the E-DCH is close to the smaller value
between EdchTargetLittleRetransNum and EdchAltTarLittleRetransNum.
l
1.

Parameters in Batches) with
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH and
PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWITCH under Power Control
Switch cleared to deactivate the algorithm for selecting an initial small target number
of retransmissions for HSUPA UEs.
----End
Example
//Activating Adaptive Adjustment of HSUPA Small Target Retransmissions
SET UCORRMALGOSWITCH: PcSwitch=
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH-1&PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWITC
H-1;
//Deactivating Adaptive Adjustment of HSUPA Small Target Retransmissions
SET UCORRMALGOSWITCH: PcSwitch=
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH-0&PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWITC
H-0;
Issue 06 (2013-03-25)

484
RAN14.0
147
Configuring HSPA+ Downlink

28Mbps per User
Prerequisites
l
BSC6900
NodeB
The BTS3812E, BTS3812A, and BTS3812AE should be configured with the EBBI,
EBOI or EDLP board.
The BBU3806 should be configured with the EBBC or EBBCd board.
The BBU3900 should be configured with the WBBPb, WBBPd or WBBPf board.
For the RF part, the RF module of Node B supports one TX channel each, and two
interconnected RF modules can provide two TX channels to support 2 x 2 MIMO.

feature depends on the feature:
WRFD-010684 2 x 2 MIMO or WRFD-010696 DC-HSDPA
WRFD-010650 HSDPA 13.976 Mbps per User
License
Other Prerequisites
CN support user rate of 28Mbit/s or above.
The UE category must support cat16, cat18(or later).
Issue 06 (2013-03-25)

485
RAN14.0
Context
This feature enables the theoretical HSPA+ MIMO rate per user to reach a maximum of 28
Mbps. This feature enhances the user experience for high-speed data services.
Procedure
l
1.
Enable a UE in a 2 x 2 MIMO cell to download a 500 MB file from the FTP server.
Then, detect the download transmission rate. At this time, the UE initiates BE services
in the 2 x 2 MIMO cell and the RNC establishes services on the 2 x 2 MIMO.
----End
Example
None
Issue 06 (2013-03-25)

486
RAN14.0
148

21Mbps per User
Prerequisites
l
The BTS3812E, BTS3812A, and BTS3812AE are configured with the EBBI, EBOI,
or EDLP board.

WRFD-010683 Downlink 64QAM, WRFD-010685 Downlink Enhanced L2.
License
Other Prerequisites
The UE category must support cat 14,18,20,24 or 28.
Context
This feature enables the theoretical HSPA+ 64QAM rate per user to reach a maximum of 21
Mbps. It provides users with high-speed data services.
Issue 06 (2013-03-25)

487
RAN14.0
Procedure
l
1.
Use the UE in a 64QAM cell to download a 500 MB file from the FTP server. Then,
check the downloading rate.
----End
Example
None
Issue 06 (2013-03-25)

488
RAN14.0
149
Configuring Downlink Enhanced L2
Downlink Enhanced L2.
Prerequisites
l

License
Others
The UE is of 3GPP R7 or later and supports this feature.
Context
The Downlink Enhanced L2 feature eliminates contradictions between high-rate transmission
that requires a large PDU size and cell-edge coverage that requires a small PDU size by using
flexible Protocol Data Unit (PDU) sizes. This feature enables dynamic adjustment of the PDU
size. This improves transmission efficiency on the Iub and Uu interfaces and increases the celledge throughput and coverage radius.
This feature is a prerequisite for the features DL 64QAM, 2x2 MIMO, and Enhanced
CELL_FACH.
Procedure
l
1.
Issue 06 (2013-03-25)
modification center: 3.15 Modifying RNC Parameters in Batches) to set the RNCHuawei Proprietary and Confidential
489
RAN14.0
level downlink layer 2 enhancement parameters. In this step, set Cell_DCH DL L2

enhance max PDU size and Cell_FACH L2 enhance max PDU size.
2.

Parameters in Batches). In this step, set Cell Hspa Plus function switch to
DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch) to turn on the
cell-level layer 2 enhancement switch.
1.
Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 149-1.

2.
Use the UE to establish an HSDPA service. Check whether the value of the IE dlTransportChannelType in the rb-MappingInfo of the RRC_RB_SETUP message
is hsdsch.
3.
View the value of the IE dL RLC PDU size in the RRC_RB_SETUP message.
If the value of the IE dL RLC PDU size is flexibleSize, as shown in Figure
If the value of the IE dL RLC PDU size is fixedSize, this feature is not activated.
Issue 06 (2013-03-25)

490
RAN14.0
Figure 149-2 Value of the IE dL RLC PDU size
1.

Parameters in Batches). In this step, deselect DL_L2ENHANCED(Cell DL
L2ENHANCED Function Switch) from the Cell Hspa Plus function switch dropdown list box.
----End
Example
//Activating Downlink Enhanced L2
//Enabling the cell-level downlink L2 enhancement
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-1;
//Deactivating Downlink Enhanced L2
//Disabling the cell-level downlink L2 enhancement
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-0;
Issue 06 (2013-03-25)

491
RAN14.0
150

42Mbps per User
Prerequisites
l
It is recommended that the BSC6900 be configured with the Data Processing Unit
REV:e (DPUe) board to support more peak-rate users.
On the NodeB side:
The BTS3812E, BTS3812A, or BTS3812AE must be configured with the EBBI,
EBOI or EDLP board.
The BBU3806 must be configured with the EBBC or EBBCd board.
BBU3806 is configured with the Enhanced Base Band Card (EBBC) or Enhanced
Base Band Card REV:d (EBBCd) board.
In the case of BTS3812E, BTS3812A, or BTS3812AE, the NodeB Enhanced
HSDPA Supported Baseband Processing and Interface Unit (EBBI) , NodeB
Enhanced HSDPA Supported Baseband Processing and Optical Interface Unit
(EBOI), or NodeB Enhanced Downlink Processing Unit (EDLP) board is
configured. In addition, the uplink service cannot be established on the NodeB
HSDPA supported Baseband processing and Interface Unit (HBBI) or NodeB
HSUPA supported Uplink Processing Unit (HULP) board.
BBU3900 is configured with the WBBPb, WBBPd or WBBPf board.
For the RF part which supports only one TX channel, two interconnected RF
modules can provide two TX channels to support 2 x 2 MIMO. In terms of RF
modules including 2 Tx channels, no additional RF modules is required for
2*2MIMO.

WRFD-010689 HSPA+ Downlink 21Mbit/s per User plus WRFD-010696 DCHSPA plus WRFD-010612 HSUPA Introduction Package, or WRFD-010689 HSPA
+ Downlink 21Mbit/s per User plus WRFD-010680 HSPA+ Downlink 28Mbit/s per
Issue 06 (2013-03-25)

492
RAN14.0
User plus WRFD-010693 DL 64QAM+MIMO plus WRFD-010612 HSUPA

l
License
Other Prerequisites
CN needs to support sending RAB assignment with relate data rate.
The UE should support category of 21(or later), that is, category: 21, 22, 23, 24, 25, 26,
27, or 28..
Context
As indicated in 3GPP Release 8, the downlink peak rate per user reaches up to 42 Mbit/s by
using the 2x2 MIMO+64QAM or 64QAM+DC-HSDPA technologies and by using enhanced
functions of the related NEs.
Procedure
l
1.
1.
Set the BE service rate of the UE at the Home Location Register (HLR) to 42 Mbit/
s.
2.
Enable a UE in an HSDPA cell to download a 500 MB file from the FTP server. Then,
check whether the download transmission rate is 42 Mbit/s. If yes, this feature has
been activated. At this time, the UE initiates BE services in the HSDPA cell and the
BSC6900 establishes services on the HS-DSCH.
3.
Start Monitoring DL Throughput and Bandwidth on the BSC6900 LMT, as shown in

Figure 150-1.
Figure 150-1 Connection Performance Monitoring dialog box
The connection performance monitoring result indicates that the BSC6900 assigns a
42.1 Mbit/s bandwidth to the UE, that is, this feature has been activated.
l
1.
----End
Issue 06 (2013-03-25)

493
RAN14.0
Example
None
Issue 06 (2013-03-25)

494
RAN14.0
151
Configuring Downlink 64QAM
Downlink 64QAM.
Prerequisites
l
The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board, EBOI
board or EDLP board.
The BBU3806 needs to be configured with the EBBC or EBBCd board.
The BBU3900 needs to be configured with the WBBPb, WBBPd or WBBPf board.

WRFD-010685 Downlink Enhanced L2
License
Other Prerequisites
The UE category must support 64QAM. That is, the UE must belong to category
13,14,17,18,19,20,23, 24, 27, 28, as specified by the 3GPP protocols.
Context
The 16QAM modulation scheme, which was introduced in 3GPP R5 specifications, provides a
higher peak rate per user and system capacity than Quadrature Phase Shift Keying (QPSK). The
64QAM modulation scheme, which was introduced in 3GPP R7 specifications, provides a higher
peak rate per user and system capacity than the 16QAM modulation scheme.
Procedure
l
1.
Issue 06 (2013-03-25)

495
RAN14.0

Parameters in Batches). In this step, select CFG_HSDPA_64QAM_SWITCH
from the Channel Configuration Strategy Switch list.
2.
preferential use of 64QAM.
Set Preferred MIMO or 64QAM character to 64QAM.
Set HSPA Technologies Retried by UEs to 64QAM.
NOTE
l If the switch parameter is set to 64QAM, the network preferentially configures 64QAM
for the UE. Otherwise, the network preferentially configures MIMO for the UE.
l Before commissioning the feature, you need to set the switch parameter to 64QAM. After
the commissioning, you can set the parameter according to the actual network planning.
l For UEs to 3GPP R7 specifications, MIMO and 64QAM cannot be used together.
3.

Parameters in Batches) to turn on the cell-level 64QAM switch and enhanced
downlink layer 2 function switch. In this step, select 64QAM(Cell 64QAM Function
Switch) and DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch)
from the Cell Hspa Plus function switch list.
4.
Optional: Run the BSC6900 MML command MOD UEXT3GCELL (CME single
to set neighboring BSC6900 cell support 64QAM. Set parameter Cell Capability
Container and select HSPAPLUS_DL_64QAM_SUPPORT (downlink 64QAM
support indicator).
NOTE
In a hard handover or soft handover over Iur, when the serving cell is relocated under the DRNC,
this function is enabled so that the serving cell continues to support 64QAM. Otherwise, the
serving cell does not support 64QAM. In this case, the actual physical capabilities of the cell
under DRNC support 64QAM.
1.
Issue 06 (2013-03-25)
As Figure 151-1 shows, start Uu interface tracing on the BSC6900 LMT.

496
RAN14.0
Figure 151-1 Uu interface tracing
2.
Establish an HSDPA service on the UE. Check the RRC_RB_SETUP message and
check that the value of the dl-TransportChannelType information element in rbMappingInfo is hsdsch.
3.
In the Uu interface tracing data, check the value of the dl-64QAM-Configured

information element under dl-HSPDSCH-Information in the RRC_RB_SETUP
message.
If the value of dl-64QAM-Configured is true as Figure 151-2 shows, you can
infer that this feature has been activated.
Otherwise, you can infer that this feature has not been activated.
Figure 151-2 Checking the dl-64QAM-Configured information element
1.
Issue 06 (2013-03-25)


497
RAN14.0
Parameters in Batches). In this step, deselect 64QAM(Cell 64QAM Function

Switch) from the Cell Hspa Plus function switch list.
2.
Optional: Run the BSC6900 MML command MOD UEXT3GCELL (CME single
to cancel neighboring BSC6900 cell support 64QAM. Set parameter Cell Capability
Container and deselect HSPAPLUS_DL_64QAM_SUPPORT (downlink
64QAM support indicator).
----End
Example
//Activation procedure SET UCORRMALGOSWITCH:
CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1;
SET UFRC: MIMOor64QAMSwitch=64QAM, RetryCapability=64QAM-1;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-1&DL_L2ENHANCED-1;
(Optional)MOD UEXT3GCELL: NRncId=0, CellId=0,
CellCapContainerFdd=HSPAPLUS_DL_64QAM_SUPPORT-1;
//Deactivation procedure MOD UCELLALGOSWITCH: CellId=1,
HspaPlusSwitch=64QAM-0;
(Optional)MOD UEXT3GCELL: NRncId=0, CellId=0,
CellCapContainerFdd=HSPAPLUS_DL_64QAM_SUPPORT-0;
Issue 06 (2013-03-25)

498
RAN14.0
152
Configuring 2x2 MIMO
2x2 MIMO. Multiple Input Multiple Output (MIMO) is a multi-antenna technology, which
enables multiple antennas to receive and transmit data. This increases the data transmission rate.
Prerequisites
l
EBOI, or EDLP board.
The BBU3806 must be configured with the EBBC or EBBCd board.
The BBU3900 must be configured with the WBBPb, WBBPd or WBBPf board.
For the RF part, the RF module of NodeB supports one TX channel each and two
interconnected RF modules can provide two TX channels to support 2 x 2 MIMO.
20W RRU3801c can only support MIMO by using together with the same module (20W
RRU3801c).

WRFD-010629 DL 16QAM Modulation
License
Other Prerequisites
The UE is of HSDPA category 15 or higher, that is, category 15, 16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 26, 27, or 28.
Issue 06 (2013-03-25)

499
RAN14.0
Context
CAUTION
Before enabling this feature in an activated cell, you need to:
l Deactivate the cell. This will interrupt services in the cell. Therefore, enable the feature when
the traffic of the cell is light.
l Ensure that there are sufficient baseband resources on the baseband processing board.
Otherwise, this feature cannot be activated.
2x2 MIMO is introduced to HSDPA in 3GPP R7. To support this feature, the NodeB use two
antennas to transmit signals, and UEs use two antennas to receive signals. When 2x2 MIMO is
enabled, the theoretical peak rate of HSDPA users increases from 14 Mbit/s to 28 Mbit/s.
Procedure
l
1.

Parameters in Batches) to turn on the BSC6900-level MIMO algorithm switch. In
this step, set Channel Configuration Strategy Switch to
CFG_HSDPA_MIMO_SWITCH.
2.
modification center: 3.15 Modifying RNC Parameters in Batches) to set common
parameters among the fundamental resource configuration (FRC) parameters. In this
step, set Preferred MIMO or 64QAM character to MIMO.
NOTE
l MIMO and 64QAM cannot be enabled together for UEs of 3GPP R7.
l If Preferred MIMO or 64QAM character is set to MIMO, MIMO is preferentially
configured for the UE.
l Before verifying the feature, set Preferred MIMO or 64QAM character to MIMO. After
the verification, set this parameter to a proper value according to the network plan.
Issue 06 (2013-03-25)
3.

Parameters in Batches) turn on the cell-level MIMO switch and enhanced L2
function switch. In this step, set Cell Hspa Plus function switch to MIMO,
DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch), and
UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch).
4.
Modifying UMTS Cell Parameters in Batches) to deactivate the cell.
5.
Configure the related data on the NodeB according to the MIMO hardware
configuration scheme. The following procedure takes the RRU3804 as an example to
500
RAN14.0
describe how to configure data for the change from one RRU3804 to two cascading
RRU3804s.
6.
7.
Issue 06 (2013-03-25)
a.
Optional: Run the NodeB MML command ADD RRUCHAIN (CME single
configuration: NodeB Configuration Express > IUB_NodeB > Device Panel
> Right click TOPO > Add RXU Chain; CME batch modification center: not
supported) to create an RRU chain.
b.
Configuration Express > IUB_NodeB > Device Panel > TOPO > Right click
RXU CHAIN > Add RXU Board; CME batch modification center: not
supported) to add an RRU to the chain.
On the NodeB, modify Diversity Mode of the sector and Two Tx Way of the cell.
a.
Locell; CME batch modification center: not supported) to remove the local cell.
b.
Run the NodeB MML command RMV SEC (CME single configuration: NodeB
modification center: not supported) to remove the sector.
c.
modification center: not supported) to add a sector. In this step, set Diversity
Mode to COMMON_MODE and configure the antenna data based on the
MIMO hardware deployment scheme.
d.
Parameters in Batches) to add a local cell. In this step, set Two Tx Way to
TRUE and configure the antenna data based on the MIMO hardware deployment
scheme.
Modify the transmit diversity mode of a cell on the BSC6900.

a.
Optional: If UPRACH exists, run the BSC6900 MML command RMV

UPRACH (CME single configuration: UMTS Cell Configuration Express >
Channel Configuration > PRACH Basic Information; CME batch
modification center: not supported) to remove the PRACH.
b.
Run the BSC6900 MML command ADD UPRACHBASIC (CME single

> PRACH Basic Information; CME batch modification center: not supported)
to add PRACH basic information.
c.
Run the BSC6900 MML command ADD UPRACHTFC (CME single

> TFC of PRACH; CME batch modification center: not supported) to add TFC
of PRACH.
d.
Run the BSC6900 MML command ADD UPRACHASC (CME single

> PRACH ASC Information; CME batch modification center: not supported)
to add ASC Of PRACH.
e.
Run the BSC6900 MML command ADD UPRACHACTOASCMAP (CME

single configuration: UMTS Cell Configuration Express > Channel
Configuration > AC-ASC Mapping Information of PRACH; CME batch
501
RAN14.0
modification center: not supported) to Add AC-ASC mapping information of

PRACH.
f.
Run the BSC6900 MML command ADD UPRACHSLOTFORMAT (CME

single configuration: UMTS Cell Configuration Express > Channel
Configuration > Slot Format of PRACH; CME batch modification center: not
supported) to add slot format of PRACH.
g.
Run the BSC6900 MML command ADD URACH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > RACH; CME
batch modification center: not supported) to add RACH.
h.
Run the BSC6900 MML command ADD URACHDYNTFS (CME single

> Dynamic TFS of RACH; CME batch modification center: not supported) to
add dynamic TFS of RACH.
i.
Optional: If AICH exists, run the BSC6900 MML command RMV UAICH
(CME single configuration: UMTS Cell Configuration Express > Channel
Configuration > AICH; CME batch modification center: not supported) to
remove AICH.
j.
Run the BSC6900 MML command ADD UAICH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > AICH; CME
batch modification center: not supported) to add AICH. Set STTD Indicator to
TRUE.
k.
Run the BSC6900 MML command ACT UPRACH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > PRACH
Basic Information. Set Validation indication to Activated; CME batch
modification center: not supported) to activate PRACH.
l.
Optional: If an SCCPCH exists, run the BSC6900 MML command RMV

USCCPCH (CME single configuration: UMTS Cell Configuration Express >
Channel Configuration > SCCPCH Basic Information; CME batch
modification center: not supported) to remove the SCCPCH.
m. Run the BSC6900 MML command ADD USCCPCHBASIC (CME single

> SCCPCH Basic Information; CME batch modification center: not supported)
to add an SCCPCH. In this step, set STTD Indicator to TRUE.
Issue 06 (2013-03-25)
n.
Run the BSC6900 MML command ADD USCCPCHTFC (CME single

> TFC of SCCPCH; CME batch modification center: not supported) to add the
Calculated Transport Format Combination (CTFC) of an SCCPCH.
o.
Optional: If a PICH exists, run the BSC6900 MML command RMV UPICH
(CME single configuration: UMTS Cell Configuration Express > Channel
Configuration > PICH; CME batch modification center: not supported) to
remove the PICH.
p.
Run the BSC6900 MML command ADD UPICH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > PICH; CME
batch modification center: not supported) to add a PICH. In this step, set STTD
Indicator to TRUE.
q.
batch modification center: not supported) to add a FACH.
r.
Run the BSC6900 MML command ADD UFACHDYNTFS (CME single

502
RAN14.0
> Dynamic TFS of FACH; CME batch modification center: not supported) to
add the transport format set (TFS) of the FACH.
s.
Run the BSC6900 MML command ADD UFACHLOCH (CME single

> Logical Channel Mapped to FACH; CME batch modification center: not
supported) to add a logical channel mapped to the FACH.
t.
Run the BSC6900 MML command ADD UPCH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > PCH; CME
batch modification center: 3.20 Modifying UMTS Channel Parameters in
Batches) to add a PCH.
u.
Run the BSC6900 MML command ADD UPCHDYNTFS (CME single

> Dynamic TFS of PCH; CME batch modification center: not supported) to add
the transport format set (TFS) of the PCH.
v.
Run the BSC6900 MML command ACT USCCPCH (CME single

> SCCPCH Basic Information. Set Validation indication to Activated; CME
batch modification center: not supported) to activate the SCCPCH.
w.
Run the BSC6900 MML command MOD UCELLSETUP (CME single

configuration: UMTS Cell Configuration Express > Cell Basic Information
> Cell Basic Information; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches) to set the transmit diversity mode of an
MIMO-enabled cell to STTD.
Set TX Diversity Indication to TRUE.
Set STTD Support Indicator to STTD_Supported.
Set CP1 Support Indicator to CP1_not_Supported.
Set DPCH Tx Diversity Mode for Other User to STTD.
Set DPCH Tx Diversity Mode for MIMO User to STTD.
Set FDPCH Tx Diversity Mode for Other User to STTD.
Set FDPCH Tx Diversity Mode for MIMO User to STTD.
8.
9.
Run the BSC6900 MML command ACT UCELLMIMO (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell MIMO status. Set
Cell MIMO state to Activated; CME batch modification center: not supported) to
activate the MIMO-related parameter settings.
1.
Issue 06 (2013-03-25)

503
RAN14.0
2.
Use the UE to establish an HSDPA service. Check whether the value of the information
element (IE) dl-TransportChannelType in the rb-MappingInfo of the
RRC_RB_SETUP message is hsdsch.
3.
In the traced Uu interface data, check whether the RRC_RB_SETUP message

contains the IE mimoParameters.
If the RRC_RB_SETUP message contains the IE mimoParameters, as shown in
Figure 152-2, this feature has been activated.
If the RRC_RB_SETUP message does not contain the IE mimoParameters, as
shown in Figure 152-2, this feature is not activated.
Figure 152-2 IE mimoParameters
1.
Issue 06 (2013-03-25)
504
RAN14.0

2.
Run the BSC6900 MML command DEA UCELLMIMO (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell MIMO status. Set
Cell MIMO state to Deactivated; CME batch modification center: not supported) to
deactivate the MIMO-related parameter settings.
3.
Run the BSC6900 MML command RMV USCCPCH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > SCCPCH Basic
Information; CME batch modification center: not supported) to remove the
SCCPCH.
4.

Basic Information; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches). In this step, set TX Diversity Indication to FALSE.
5.

Parameters in Batches). In this step, clear MIMO(Cell MIMO Function Switch)
from the HspaPlusSwitch drop-down list.
6.
----End
Example
l
NodeB V200R014
//Turning on the BSC6900-level MIMO algorithm switch
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-1;
//Setting MIMO as the preferred function
SET UFRC: MIMOor64QAMSwitch=MIMO;
//Enabling the cell-level MIMO and L2 enhancement
MOD UCELLALGOSWITCH: HspaPlusSwitch=MIMO-1&DL_L2ENHANCED-1;
//Deactivating the HSDPA cell
//Activation operation
RMV UPRACH: CellId=1, PhyChId=4;
ADD UPRACHBASIC: CellId=1,
PreambleSignatures=SIGNATURE0-1&SIGNATURE1-1&SIGNATURE2-1&SIGNATURE31&SIGNATURE4-1&SIGNATURE5-1&SIGNATURE6-1&SIGNATURE7-1,
RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1&SUBCHANEL3-1&SUBCH
ANEL4-1&SUBCHANEL5-1&SUBCHANEL6-1&SUBCHANEL7-1&SUBCHANEL8-1&SUBCHANEL
9-1&SUBCHANEL10-1&SUBCHANEL11-1, Constantvalue=-20, PowerRampStep=3;
ADD UPRACHTFC: CellId=1, PhyChId=4, CTFC=0, PowerOffsetPpm=-3,
GainFactorBetaC=13, GainFactorBetaD=15;
ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC0;
ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC2,
PersistScalingFactor=D0.9;
Issue 06 (2013-03-25)

505
RAN14.0

ADD UPRACHACTOASCMAP: CellId=1, PhyChId=4;
ADD UPRACHSLOTFORMAT: CellId=1, SlotFormatNum=D4;
ADD URACH: CellId=1, PhyChId=4, TrChId=1;
ADD URACHDYNTFS: CellId=1, RLCSize=168, TFsNumber=D1, TbNumber1=1;
ADD UAICH: CellId=1, PRACHPhyChId=4, PhyChId=6, STTDInd=TRUE;
ACT UPRACH: CellId=1, PhyChId=4;
RMV USCCPCH: CellId=1, PhyChId=8;
ADD USCCPCHBASIC: CellId=1, PhyChId=8, ScrambCode=0, STTDInd=TRUE,
SlotFormat=D8, TFCIpresence=EXISTS;
ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=0;
ADD UPICH: CellId=1, PhyChId=8, STTDInd=TRUE;
ADD UFACH: CellId=1, PhyChId=8, TrChId=4, ToAWS=20, ToAWE=10,
SigRbInd=FALSE, ChCodingType=CONVOLUTIONAL;
ToAWS=30, ToAWE=10, MaxCmchPi=D13, MinCmchPi=D0, ChCodingType=TURBO;
ADD UFACHDYNTFS: CellId=1, TrChId=4, RLCSize=168, TFsNumber=D3;
ADD UPCH: CellId=1, PhyChId=8;
ADD UPCHDYNTFS: CellId=1, RLCSize=240, TFsNumber=D2;
ACT USCCPCH:CELLID=1, PHYCHID=8;
MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE,
STTDSupInd=STTD_Supported, CP1SupInd=CP1_not_Supported,
DpchDivModforOther=STTD,
FdpchDivModforOther=STTD, DpchDivModforMIMO=STTD,
FdpchDivModforMIMO=STTD;
//Activating a cell
//Activating the MIMO-related parameter settings
ACT UCELLMIMO: CellId=1;
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=2, HPN=0;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO,
ALMPROCSW=OFF;
ALMPROCSW=OFF;
//Removing a local cell and a sector
RMV SEC: STN=0, SECN=2;
//Adding a sector and setting the transmit diversity mode
ANT1SRN=60, ANT1N=R0A, ANT2SRN=61, ANT2N=R0A;
//Adding a local cell and setting 2-way transmit diversity
ADD LOCELL: LOCELL=1, STN=0, SECN=2, SECT=REMOTE_SECTOR, TTW=TRUE,
Issue 06 (2013-03-25)

506
RAN14.0

SRN1=60, SRN2=61, SN2=0, ANT2N=ANTA, ULFREQ=9845,
DLFREQ=10795, MXPWR=460, HISPM=FALSE, RMTCM=FALSE, VAM=FALSE;
DEA UCELLMIMO: CellId=1;
MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=MIMO-0;
NodeB V100R014
//Turning on the BSC6900-level MIMO algorithm switch
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-1;
//Setting MIMO as the preferred function
SET UFRC: MIMOor64QAMSwitch=MIMO;
//Enabling the cell-level MIMO and L2 enhancement
MOD UCELLALGOSWITCH: HspaPlusSwitch=MIMO-1&DL_L2ENHANCED-1;
//Deactivating the HSDPA cell
//Activation operation
ADD UPRACHBASIC: CellId=1,
PreambleSignatures=SIGNATURE0-1&SIGNATURE1-1&SIGNATURE2-1&SIGNATURE31&SIGNATURE4-1&SIGNATURE5-1&SIGNATURE6-1&SIGNATURE7-1,
RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1&SUBCHANEL3-1&SUBCH
ANEL4-1&SUBCHANEL5-1&SUBCHANEL6-1&SUBCHANEL7-1&SUBCHANEL8-1&SUBCHANEL
9-1&SUBCHANEL10-1&SUBCHANEL11-1, Constantvalue=-20, PowerRampStep=3;
ADD UPRACHACTOASCMAP: CellId=1, PhyChId=4;
ADD UPRACHSLOTFORMAT: CellId=1, SlotFormatNum=D4;
ADD URACH: CellId=1, PhyChId=4, TrChId=1;
ADD UAICH: CellId=1, PRACHPhyChId=4, PhyChId=6, STTDInd=TRUE;
ACT UPRACH: CellId=1, PhyChId=4;
ADD USCCPCHBASIC: CellId=1, PhyChId=8, ScrambCode=0, STTDInd=TRUE,
SlotFormat=D8, TFCIpresence=EXISTS;
Issue 06 (2013-03-25)

507
RAN14.0

ADD UPICH: CellId=1, PhyChId=8, STTDInd=TRUE;
ADD UFACH: CellId=1, PhyChId=8, TrChId=4, ToAWS=20, ToAWE=10,
SigRbInd=FALSE, ChCodingType=CONVOLUTIONAL;
ToAWS=30, ToAWE=10, MaxCmchPi=D13, MinCmchPi=D0, ChCodingType=TURBO;
ADD UPCH: CellId=1, PhyChId=8;
ADD UPCHDYNTFS: CellId=1, RLCSize=240, TFsNumber=D2;
ACT USCCPCH:CELLID=1, PHYCHID=8;
MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE,
STTDSupInd=STTD_Supported, CP1SupInd=CP1_not_Supported,
DpchDivModforOther=STTD,
FdpchDivModforOther=STTD, DpchDivModforMIMO=STTD,
FdpchDivModforMIMO=STTD;
//Activating a cell
//Activating the MIMO-related parameter settings
ACT UCELLMIMO: CellId=1;
ADD RRUCHAIN: RCN=0, TT=CHAIN, HSN=0, HPN=0;
ADD RRU: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO,
ALMPROCSW=OFF;
ADD RRU: CN=0, SRN=61, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=UO,
ALMPROCSW=OFF;
//Removing a local cell and a sector
//Adding a sector and setting the transmit diversity mode
//Adding a sector and setting the transmit diversity mode (assuming
that DBS3800 is used)
SRN1=60, SRN2=61, SN2=0, ANT2N=ANTB, ULFREQ=9630, DLFREQ=10580,
MXPWR=430, HISPM=FALSE, RMTCM=FALSE, VAM=FALSE;
DEA UCELLMIMO: CellId=1;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=MIMO-0;
Issue 06 (2013-03-25)

508
RAN14.0
153
Configuring Downlink 64QAM

+MIMO
DL 64QAM+MIMO.
Prerequisites
l
The 3900 series base station supports 64QAM+MIMO when the WBBPb, WBBPd or
WBBPf board is configured.
In the case of the BTS3900, BTS3900A, and DBS3900, the WBBPb1, WBBPb2,
WBBPb3, WBBPb4, or WBBPd1 board needs to be configured.
In the case of the BTS3812E and BTS3812AE, the EBBI or EDLP board needs to be
configured.
Two RRUs (for example RRU3804) with single TX channels, or one RRU (for example
the RRU3805 or RRU3808) with a dual TX channel needs to be configured.
The HBBI and HDLP of the BTS3812E AND BTS3812AE do not support 64QAM
+MIMO. To support 64QAM+MIMO, the EBBI or EDLP must be configured.
The BBU3806 of the DBS3800 does not support 64QAM+MIMO. To support 64QAM
+MIMO, the EBBC or EBBCd board must be configured.

WRFD-010684 22 MIMO
WRFD-010683 Downlink 64 QAM
License
Other Prerequisites
The UE is of category 19, 20 as specified by the 3GPP specifications.
Context
In 3GPP Release 8, MIMO and 64QAM can be used in combination to increase the peak
throughput of a single user.
Issue 06 (2013-03-25)

509
RAN14.0
With 64QAM+MIMO, the peak throughput of a single user can reach 42Mbit/s, compared to
28Mbit/s with MIMO or 21Mbit/s with 64QAM only.
NOTE
l The SRB, CS service, IMS signaling, and PS conversational services are not carried on MIMO,
64QAM, or MIMO+64QAM because the data flow is small and the gain is insignificant.
l The PS streaming service, PS interactive service, PS background service, and the combined services
with previous services can be carried on MIMO+64QAM.
Data Planning
Parameter
Example
Source
Local Cell ID
Network planning
Cell ID
Network planning
DL streaming traffic
threshold on HSDPA
D64
Network planning
DL BE traffic threshold on
HSDPA
D64
Network planning
Procedure
l
Issue 06 (2013-03-25)
1.
Batches) to modify a local cell. In this step, set DL 64QAM MIMO to TRUE.
2.

Parameters in Batches) to turn on the following three BSC6900-level switches: In
this step, select CFG_HSDPA_64QAM_SWITCH,
CFG_HSDPA_MIMO_SWITCH, and
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH from the Channel
Configuration Strategy Switch list.
3.
preferential use of 64QAM+MIMO. In this step, select MIMO_64QAM from the
Prefered MIMO_64QAM or DC_HSDPA character list.
4.
Optional: If the streaming service needs to use HSDPA, run the BSC6900 MML

510
RAN14.0
select MAP_PS_STREAM_ON_HSDPA_SWITCH from the Service Mapping

Strategy Switch list.
5.
Optional: Run the BSC6900 MML command SET UFRCCHLTYPEPARA (CME

single configuration: UMTS Radio Global Configuration Express > Basic
Resource Control Parameter Configuration > Channel Type Parameters; CME
step, set DL streaming traffic threshold on HSDPA and DL BE traffic threshold
on HSDPA according to the actual network planning.
6.

Parameters in Batches) to turn on the following four cell-level switches: In this step,
select 64QAM(Cell 64QAM Function Switch), MIMO(Cell MIMO Function
Switch), DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch), and
64QAM_MIMO(Cell 64QAM+MIMO Function Switch) from the Cell Hspa Plus
function switch list.
1.
Run the NodeB MML command LST LOCELL to query the configuration
information of the local cell. In this step, set Query Mode to LOCALCELL(Query
Localcell by ID) and then specify Local Cell ID. The execution result displayed on
the LMT shows the DL 64QAM+MIMO capability.
2.
Run the BSC6900 MML command LST UCELLALGOSWITCH to verify the

configuration result of the cell algorithm switch.
3.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify the

configuration result of the connection-oriented algorithm switch.
4.
Run the BSC6900 MML command DSP UCELLCHK to check that the cell supports
64QAM+MIMO.
1.

Parameters in Batches) to turn off the cell-level 64QAM+MIMO switch. In this step,
deselect 64QAM_MIMO(Cell 64QAM+MIMO Function Switch) from the Cell
Hspa Plus function switch list.
2.

Parameters in Batches) to turn off the BSC6900-level 64QAM+MIMO switch. In
this step, deselect CFG_HSDPA_MIMO_WITH_64QAM_SWITCH from the
Channel Configuration Strategy Switch list.
----End
Example
MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, DL64QAM_MIMO=TRUE;
CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1&CFG_HSDPA_MIMO
Issue 06 (2013-03-25)

511
RAN14.0
_WITH_64QAM_SWITCH-1;
SET UFRC: MIMO64QAMorDCHSDPASwitch=MIMO_64QAM;
SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64;
HspaPlusSwitch=64QAM-1&MIMO-1&DL_L2ENHANCED-1&64QAM_MIMO-1;
LST UCELLALGOSWITCH:CellId=1;
LST UCORRMALGOSWITCH: LstFormat=VERTICAL;
DSP UCELLCHK:CellId=1;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM_MIMO-0;
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_WITH_64QAM_SWITCH-0;
Issue 06 (2013-03-25)

512
RAN14.0
154
Configuring HSPA+ Uplink

11.5Mbit/s per User
HSPA+ Uplink 11.5Mbit/s per User.
Prerequisites
l
Dependencies on NodeB for uplink 16QAM+E-DPCCH boosting:
The BTS3812E, BTS3812A and BTS3812AE must be configured with the EULPd
board.
The 3900 series base station must be configured with the WBBPd or WBBPf board.
Dependencies on NodeB for DC-HSUPA:
The BTS3812E, BTS3812A and BTS3812AE must be configured with the EULP
or EULPd board.
The DBS3800 must be configured with the EBBC or EBBCd board.
The 3900 series base station must be configured with the WBBPb, WBBPd or
WBBPf board.

For uplink 16QAM+E-DPCCH boosting,
WRFD-010694 UL 16QAM
WRFD-010614 HSUPA Phase 2
WRFD-010697 E-DPCCH Boosting
For DC-HSUPA,
WRFD-140204 DC-HSUPA
License
Issue 06 (2013-03-25)

513
RAN14.0
Others
The UE must support E-DPCCH boosting. The UE must be of HSUPA category 7, 8,
or 9.
The CN must support an uplink data rate of 11.5Mbit/s or above.
Context
With the original HSUPA peak rate of 5.74 Mbps, the UE increases its uplink peak rate to 11.5
Mbps by using the technologies introduced in 3GPP Release 7, including 16QAM and E-DPCCH
Boosting.
Procedure
l
Issue 06 (2013-03-25)
1.
To enable the SRB to carry over HSUPA, run the BSC6900 MML command SET
UFRCCHLTYPEPARA (CME single configuration: UMTS Radio Global
Configuration Express > Basic Resource Control Parameter Configuration >
Channel Type Parameters; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) with Type of Channel Preferably Carrying Signaling
RB set to HSUPA(UL_EDCH,DL_DCH).
2.
To enable the 2 ms TTI switch, run the BSC6900 MML command SET
Modifying RNC Parameters in Batches) with Service Mapping Strategy Switch
set to MAP_HSUPA_TTI_2MS_SWITCH.
3.
To enable the switch for RNC-level UL 16QAM, run the BSC6900 MML command
SET UCORRMALGOSWITCH (CME single configuration: UMTS Radio Global
Modifying RNC Parameters in Batches) with Channel Configuration Strategy
Switch set to CFG_HSUPA_16QAM_SWITCH.
4.
To enable the algorithm switch for RNC-level E-DPCCH Boosting, run the BSC6900
MML command SET UCORRMALGOSWITCH (CME single configuration:
UMTS Radio Global Configuration Express > Connection_Oriented RRM
Switch Configuration > Connection Oriented Algorithm Switches; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches) with Channel
Configuration Strategy Switch set to CFG_EDPCCH_BOOSTING_SWITCH.
5.
To enable the switch for cell-level UL 16QAM, run the BSC6900 MML command
MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) with Cell
Hspa Plus function switch set to UL_16QAM(Cell UL 16QAM Function
Switch) .
6.
To enable the switch for cell-level UL Layer 2 Improvement, run the BSC6900 MML
command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Hspa Plus function switch set to UL_L2ENHANCED(Cell UL L2ENHANCED
Function Switch).
514
RAN14.0
7.
To enable cell-level Boosting, run the BSC6900 MML command MOD

UCELLALGOSWITCH (CME single configuration: UMTS Cell Configuration
Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches) with Cell Hspa Plus
function switch set to EDPCCH_BOOSTING(Cell E-DPCCH Boosting Function
Switch).
8.
Batches) with UL_16QAM set to TRUE, UL_L2ENHANCED to TRUE, and
EDPCCH_BOOSTING to TRUE.
1.
Enable a UE of 3GPP Release 7 or later versions and supporting UL 16QAM to access

the network and to establish PS services on the E-DCH and HS-DSCH.
2.
Create a task under UL Throughput and Bandwidth on the BSC6900 LMT.

Upload by FTP is normal. Ideally, the uplink throughput of the UE in MAC layer can
reach 11.5 Mbps.
1.
To disable the switch for RNC-level UL 16QAM, run the BSC6900 MML
Configuration Strategy Switch deselect to CFG_HSUPA_16QAM_SWITCH .
2.
To disable the switch for cell-level UL 16QAM, run the BSC6900 MML command
Hspa Plus function switch deselect to UL_16QAM(Cell UL 16QAM Function
Switch) .
----End
Example
/* Activating the HSPA+ Uplink 11.5Mbps per User feature*/
//Enabling the SRB to carry over HSUPA
SET UFRCCHLTYPEPARA: SrbChlType=HSUPA;
//Enabling the 2ms TTI switch
//Enabling the switch for RNC-level UL 16QAM
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSUPA_16QAM_SWITCH-1;
//Enabling the algorithm switch for RNC-level Boosting
SET UCORRMALGOSWITCH: CfgSwitch= CFG_EDPCCH_BOOSTING_SWITCH-1;
//Enabling the switch for cell-level UL 16QAM
MOD UCELLALGOSWITCH: CellId=1,HspaPlusSwitch=UL_16QAM-1;
//Enabling the switch for cell-level UL Layer 2 Improvement
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_L2ENHANCED-1;
Issue 06 (2013-03-25)

515
RAN14.0
//Enabling the algorithm switch for cell-level Boosting

MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch= EDPCCH_BOOSTING-1;
//Setting the UL Layer 2 Improvement, UL 16QAM, and Boosting functions
MOD LOCELL: CellId=1, SECT=LOCAL_SECTOR, UL_L2+=TRUE, UL_16QAM=TRUE,
Boosting=TRUE;
/* Deactivating the HSPA+ Uplink 11.5Mbps per User feature*/
//Disabling the switch for RNC-level UL 16QAM
//Disabling the switch for cell-level UL 16QAM
MOD UCELLALGOSWITCH: CellId=1,HspaPlusSwitch=UL_16QAM-0;
Issue 06 (2013-03-25)

516
RAN14.0
155
Configuring HSPA+ Downlink 84

Mbit/s per User
HSPA+ Downlink 84 Mbit/s per User.
Prerequisites
l
Requirements on BSC6900 Hardware
The DPUe is required to support this feature.
The FG2a (for the GE interface), FG2c (for the GE interface), GOUa, or GOUc serve
as the interface boards.
Requirements on NodeB Hardware
The BTS3812AE/BTS3812E and DBS3800 cannot provide the downlink peak rate
of 84 Mbit/s per user.
To support this feature, 3900 series base stations must be configured with the
WBBPd, WBBPb3, WBBPb4 or WBBPf board.

WRFD-010689 HSPA+ Downlink 42Mbit/s per User
WRFD-010693 DL 64QAM+MIMO
WRFD-010699 DC-HSDPA+MIMO
License
Others
The UE must be of category 28 to support 84 Mbit/s in the downlink, according to 3GPP
Release 9.
The Iub interface uses IP transmission mode rather than ATM or STM-1 transmission
mode.
Downlink 64QAM
Issue 06 (2013-03-25)

517
RAN14.0
Context
This feature improves the maximum downlink rate of a single user to 84 Mbit/s using 64QAM,
MIMO, and DC-HSDPA, and users can experience high-speed data services.
Procedure
l
1.
Set the BE service rate of a UE at the Home Location Register (HLR) to 84 Mbit/s.
2.
Enable the UE in an HSDPA cell to download a 1024 MB file from the FTP server.
Check whether the download transmission rate is close to 84 Mbit/s. If yes, this feature
has been activated. In this case, the UE will originate BE services in the HSDPA cell,
and the BSC6900 will establish services on the HS-DSCH.
3.
On the BSC6900 LMT, start Monitoring DL Throughput and Bandwidth, as shown

in Figure 155-1.
Figure 155-1 Connection performance monitoring result
The connection performance monitoring result indicates that the bandwidth the
BSC6900 assigns to the UE is close to 84 Mbit/s bandwidth to the UE. That is, this
feature has been activated.
l
----End
Example
None
Issue 06 (2013-03-25)

518
RAN14.0
156
Configuring DC-HSDPA+MIMO
DC-HSDPA+MIMO.
Prerequisites
l
The HBBI and HDLP boards in the BTS3812E/BTS3812AE do not support the DCHSDPA+MIMO feature. To support this feature, the BTS3812E/BTS3812AE must be
configured with the EBBI and EDLP boards.
To support DC-HSDPA+MIMO, the DBS3800 must be configured with the EBBC or
EBBCd boards. In addition, the maximum capability of the DBS3800 is DC+MIMOx1.
That is, only one frequency in a dual cell (DC) group can be configured with MIMO.
3900 series base stations must be configured with the WBBPb, WBBPd or WBBPf
boards.

WRFD-010696 DC-HSDPA and WRFD-010684 22 MIMO.
License
Others
This feature is dependent on the UE capability (class 25, 26, 27, and 28 on the HSDSCH).
Differentiated Service Management.
Context
Introduced in the R9 protocol, the DC-HSDPA+MIMO feature combines the DS-HSDPA
feature in the R8 protocol and the MIMO feature in the R7 protocol. This feature allows two
inter-frequency co-coverage neighboring carriers under a NodeB that use the same frequency
band to simultaneously transmit HSDPA data to a UE.
Issue 06 (2013-03-25)

519
RAN14.0
Procedure
l
1.
To enable the algorithm switch for RNC-level DC-HSDPA+MIMO, run the BSC6900
MML command SET UCORRMALGOSWITCH (CME single configuration:
Switch Configuration > Connection Oriented Algorithm Switches; CME batch
Configuration Strategy Switch set to CFG_HSDPA_DCMIMO_SWITCH and
CFG_HSDPA_MIMO_SWITCH.
2.
Optional: if HSDPA is required for streaming services, you need to enable the
algorithm switch for streaming services carried over HSDPA: run the BSC6900 MML
modification center: 3.15 Modifying RNC Parameters in Batches) with Service
Mapping Strategy Switch set to MAP_PS_STREAM_ON_HSDPA_SWITCH.
3.
modification center: 3.15 Modifying RNC Parameters in Batches) with HSPA
Technologies Retried by UEs set to DCMIMO_HSDPA.
4.
To set the HSDPA threshold for downlink streaming services and for downlink BE
services, run the BSC6900 MML command SET UFRCCHLTYPEPARA (CME
single configuration: UMTS Radio Global Configuration Express > Basic
Resource Control Parameter Configuration > Channel Type Parameters; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) with DL
streaming traffic threshold on HSDPA and DL BE traffic threshold on HSDPA
set to appropriate values according to the network plan.
5.
To enable the switch for cell-level DC-HSDPA+MIMO and the algorithm switch for
DL Layer2 Improvement, run the BSC6900 MML command MOD
center: 3.18 Modifying UMTS Cell Parameters in Batches) with Cell Hspa Plus
function switch set to DL_L2ENHANCED and DCMIMO_HSDPA.
NOTE
You are advised to enable the switch for cell-level DC-HSDPA+MIMO and the algorithm
switch for DL Layer2 Improvement on two cells of the DC-HSDPA cell group.
Issue 06 (2013-03-25)
6.
To add the HSDPA parameters for a cell, run the BSC6900 MML command ADD
Modifying UMTS Cell Parameters in Batches) with related parameters set to
appropriate values according to the network plan.
7.
To enable the switch for cell-level DC-HSDPA+MIMO, run the NodeB MML
command ADD LOCELL (CME single configuration: NodeB Configuration
Express > IUB_NodeB > Radio Layer > xx Sector > Locell; CME batch
modification center: 3.17 Modifying Physical NodeB Parameters in Batches) or
MOD LOCELL (CME single configuration: NodeB Configuration Express >
IUB_NodeB > Radio Layer > xx Sector > Locell; CME batch modification center:
3.17 Modifying Physical NodeB Parameters in Batches) with DC+MIMO set to
TRUE on the NodeB.
520
RAN14.0
8.
Optional: Run the BSC6900 MML commandACT UCELLHSDPA (CME single

HSDPA Parameters. Set ACTSTATUS to Activated; CME batch modification
center: No supported) to activate the HSDPA function for a cell.
9.
Optional: When the DC-HSDPA+MIMO feature is used, you need to activate the
Configure HSPA+ Downlink 84 Mbit/s per User feature by referring to Configuring
HSPA+ Downlink 84 Mbit/s per User if the downlink throughput of a single user is
expected to reach 84 Mbit/s.
1.
To check the number of online DC-HSDPA+MIMO users, query the counter

VS.HSDPA.UE.Mean.CAT25.28 to obtain the average number of HSDPA users of
CAT25 to CAT28 in a cell, and query the counter VS.HSDPA.UE.Max.CAT25.28
to obtain the maximum number of HSDPA users of CAT25 to CAT28 in a cell.
2.
To check DC-HSDPA+MIMO service setup, query the counter

VS.HSDPA.RAB.DCMIMO.AttEstab to obtain the number of DC-HSDPA-MIMO
RAB setup attempts on the primary carrier in a DC group, and query the counter
VS.HSDPA.RAB.DCMIMO.SuccEstab to obtain the number of successful DCHSDPA-MIMO RAB setups on the primary carrier in a DC group.
3.
To check DC-HSDPA+MIMO call drops, query the counter

VS.HSDPA.RAB.DCMIMO.NormRel to obtain the number of DC-HSDPA-MIMO
RABs normally released on the primary carrier in a DC group, and query the counter
VS.HSDPA.RAB.DCMIMO.AbnormRel to obtain the number of DC-HSDPAMIMO RABs abnormally released on the primary carrier in a DC group (including
RF Failure).
4.
Enable UE tracing, and establish HSPA BE services to check whether the RADIO
BEARER SETUP message over the Uu interface carries dlSecondaryCellInfoFDD and secondaryCellMIMOparameters.
If the RADIO BEARER SETUP message over the Uu interface carries dlSecondaryCellInfoFDD and secondaryCellMIMOparameters, as shown in
Figure 156-1, the feature has been activated.
If the RADIO BEARER SETUP message over the Uu interface does not carry dlSecondaryCellInfoFDD or secondaryCellMIMOparameters, the feature has
not been activated.
Figure 156-1 RADIO BEARER SETUP message
Issue 06 (2013-03-25)

521
RAN14.0
1.

CFG_HSDPA_DCMIMO_SWITCH and CFG_HSDPA_MIMO_SWITCH from
the Channel Configuration Strategy Switch drop-down list to disable the algorithm
switch for RNC-level DC-HSDPA+MIMO on the RNC.
2.

Parameters in Batches). In this step, deselect DCMIMO_HSDPA(Cell DCHSDPA Combined with MIMO Function Switch) from the Cell Hspa Plus
function switch drop-down list to disable the algorithm switch for cell-level DCHSDPA+MIMO on the RNC.
3.
Batches). In this step, set DC+MIMO to FALSE to disable the algorithm switch for
DC-HSDPA+MIMO on the NodeB.
----End
Example
/*Activating DC-HSDPA+MIMO*/
//Enabling the algorithm switch for RNC-level DC-HSDPA+MIMO
CfgSwitch=CFG_HSDPA_DCMIMO_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1;
//(Optional) Enabling the algorithm switch for streaming services over
HSDPA If HSDPA is required for streaming services
//Enabling the retried switch for DC-HSDPA+MIMO
SET UFRC: RetryCapability=DCMIMO_HSDPA-1;
//Setting HSDPA thresholds for downlink streaming services and for
downlink BE services
//Enabling the switch for cell-level DC-HSDPA+MIMO and the algorithm
switch for DL Layer2 Improvement
HspaPlusSwitch=64QAM-1&MIMO-1&DL_L2ENHANCED-1&64QAM_MIMO-1&DC_HSDPA-1&DCM
IMO_HADPA-1
//Adding the HSDPA parameters for a cell
CodeAdjForHsdpaSwitch=ON;
//Activating the DC-HSDPA+MIMO function on the NodeB
MOD LOCELL: LOCELL=1, DC_MIMO=TRUE;
//Activating the HSDPA function for a cell
/*Deactivating DC-HSDPA+MIMO*/
//Disabling the algorithm switch for RNC-level DC-HSDPA+MIMO
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DCMIMO_SWITCH-0;
//Disable the switch for cell-level DC-HSDPA+MIMO
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DCMIMO_HSDPA-0;
Issue 06 (2013-03-25)

522
RAN14.0
//Disable the switch for DC-HSDPA+MIMO on the NodeB

MOD LOCELL: LOCELL=1, DC_MIMO=FALSE;
Issue 06 (2013-03-25)

523
RAN14.0
157
Configuring UL 16QAM
UL 16QAM.
Prerequisites
l
In the case of the 3900 series base station, the WBBPd or WBBPf board needs to be
configured.
In the case of the DBS3800, the EBBCd board needs to be configured.
In the case of the BTS3812E/BTS3812AE, the EULPd board needs to be configured.
For the BTS3812E/BTS3812AE, the uplink resource groups are set up on the EULPd
board, and the downlink cells are set up on the EBBI or EDLP board.

License
Other Prerequisites
The CN supports the "peak rate per user" introduced by UL 16QAM.
The UE must be of category 7, category 9.
Context
l
This feature can help increase the system capacity in the uplink so that HSUPA users can
obtain a higher peak rate.
It is recommended that the feature WRFD-010692 HSUPA FDE be activated to help

increase the data throughput on the Uu interface.
Procedure
1.
Issue 06 (2013-03-25)
524
RAN14.0

Batches) to modify a local cell. In this step, set UL 16QAM to TRUE.
2.
Run the BSC6900 MML command ADD UCELLALGOSWITCH (CME single

Parameters in Batches), Select the UL_16QAM(Cell UL 16QAM Function
Switch) check box under the parameter Cell Hspa Plus function switch.
3.

Parameters in Batches), Select the CFG_HSUPA_16QAM_SWITCH check box
under the parameter Channel Configuration Strategy Switch.
1.
Run the NodeB MML command DSP LOCELL to query the configuration
information of the local cell.
2.
As Figure 157-1 shows, start Uu interface tracing on the BSC6900 LMT.

Figure 157-1 Uu Interface tracing
3.
Use the UE to perform a dialing test of the PS service. Ensure that an HSUPA service
is established.
4.
Analyze the trace messages. In the Uu interface trace data, view the EDCH
information information element (IE) in the RRC_RB_SETUP message.
As shown in Figure 157-2, if the EDCH information IE contains the indicator of
uplink 16QAM, you can infer that this feature has been activated.
If the EDCH information IE does not contain the indicator of uplink 16QAM,
you can infer that this feature has not been activated.
Issue 06 (2013-03-25)

525
RAN14.0
Figure 157-2 Indication of uplink 16QAM
1.
Batches) to modify the local cell. In this step, set UL_16QAM to FALSE.
2.

Parameters in Batches), Clear the UL_16QAM(Cell UL 16QAM Function
3.

Parameters in Batches), Clear the CFG_HSUPA_16QAM_SWITCH check box
under the parameter Channel Configuration Strategy Switch.
----End
Example
MOD LOCELL: LOCELL=1, UL_16QAM=TRUE;
ADD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_16QAM-1;
MOD LOCELL: LOCELL=1, UL_16QAM=FALSE;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_16QAM-0;
Issue 06 (2013-03-25)

526
RAN14.0
158
Configuring UL Layer 2
Improvement
UL Layer 2 Improvement.
Prerequisites
l
In the case of the BTS3900, BTS3900A, or DBS3900, the WCDMA Baseband Process
Unit REV:b (WBBPb) board (including WBBPb1, WBBPb2, WBBPb3, and WBBPb4)
or the WCDMA Baseband Process Unit REV:d (WBBPd) board (including WBBPd1
or WBBPd2) is configured.
For BBU3806,EBBC or EBBCd is needed.
For BBU3900, WBBPb ,WBBPd or WBBPf is needed.
For BTS3812E and BTS3812AE, EBBI/EBOI/EULP/EULPd is needed.

The WRFD-010612 HSUPA Introduction Package feature has been configured before
License
Other Prerequisites
The UE needs to be compliant with 3GPP Release 8 (or later) to support the feature.
Context
This feature enables the radio link layer to use a flexible Protocol Data Unit (PDU) size for data
transmission based on the radio transmission environment on the Uu interface.
l
Issue 06 (2013-03-25)
When the UE is located at the cell edge, data is transmitted in a small PDU size, reducing
the bit error rate (BER) caused by power limitation and improving the data transmission
efficiency.
527
RAN14.0
When the UE is located in the cell center, data is transmitted in a large PDU size, meeting
the high-speed data transmission requirement and increasing the data transmission
efficiency. As a result, the effective throughput of the entire system is increased.
Procedure
1.
Optional: Run the BSC6900 MML command SET UFRC (CME single
Control Parameter Configuration > RNC Oriented FRC Algorithm
Batches) to set parameters related to UL Layer 2 Improvement at the BSC6900 level.
In this step, set Cell_DCH UL L2 enhance max RLC PDU size and Cell_DCH UL
L2 enhance min RLC PDU size to appropriate values.
NOTE
Generally, use the default values of Cell_DCH UL L2 enhance max RLC PDU size and
Cell_DCH UL L2 enhance min RLC PDU size of the BSC6900.
2.

Parameters in Batches) to enable UL Layer 2 Improvement at the cell level. In this
step, select the DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch)
check box under the parameter Cell Hspa Plus function switch.
3.
NodeB V100R014: Run the NodeB MML command MOD LOCELL (CME single
configuration: NodeB Configuration Express > IUB_NodeB > Radio Layer > xx
Sector > Locell; CME batch modification center: 3.17 Modifying Physical NodeB
step, set UL_L2+ to TRUE.
4.
step, set UL L2 Enhanced to TRUE.
1.
Issue 06 (2013-03-25)

528
RAN14.0
2.
Use an UE to establish an HSUPA service.

NOTE
The type of services that use this feature is limited by the HSUPA rate threshold.
3.
In the Uu interface tracing data, check the value of the information element (IE) rlcPDU-Size in the RRC_RB_SETUP message.
If the value of the IE rlc-PDU-Size is flexibleSize, as shown in Figure 158-2, this
If the value of the IE rlc-PDU-Size is fixedSize, this feature is not activated.
Figure 158-2 Value of the IE rlc-PDU-Size
l
Issue 06 (2013-03-25)
529
RAN14.0
1.

Parameters in Batches) to disable UL Layer 2 Improvement at the cell level. In this
step, deselect the DL_L2ENHANCED(Cell DL L2ENHANCED Function
2.
step, set UL_L2+ to FALSE.
3.
step, set UL L2 Enhanced to FALSE.
----End
Example
//Turning on the cell-level switch for UL Layer 2 Improvement on the
BSC6900 side
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_L2ENHANCED-1;
//Enabling UL Layer 2 Improvement at the cell level on the NodeB side
//NodeB V100R014
MOD LOCELL: CellId=1, UL_L2+=TRUE;
//NodeB V200R014
MOD LOCELL: CellId=1, UL_L2PLUS=TRUE;
//Turning off the cell-level switch for UL Layer 2 Improvement on the
BSC6900 side
MOD UCELLALGOSWITCH: HspaPlusSwitch=UL_L2ENHANCED-0;
//Disabling UL Layer 2 Improvement at the cell level on the NodeB side//
NodeB V100R014
MOD LOCELL: CellId=1, UL_L2+=FALSE;
//NodeB V200R014
MOD LOCELL: CellId=1, UL_L2PLUS=FALSE;
Issue 06 (2013-03-25)

530
RAN14.0
159
Configuring DC-HSDPA
DC-HSDPA.
Prerequisites
l
For 3900 series base station, BBU3900 needs to be configured with the WBBPb,
WBBPd or WBBPf.
The BTS3902E supports DC-HSDPA.
For DBS3800 base station, the BBU3806 needs to be configured with the EBBC or
EBBCd.
The BTS3812E or BTS3812AE needs to be configured with the EBBI or EDLP board,
and the UL baseband resources of DC-HSDPA cells cannot be carried on the HBBI or
HULP board. They can be carried on the EBBI or EDLP board.
For the BSC6900, DPUe boards are recommended because the downlink 42 Mbit/s
throughput of DC-HSDPA users may be affected if the BSC6900 is configured with
DPUb boards.

WRFD-010629 DL 16QAM Modulation
License
The license controlling this feature has been activated.
Other Prerequisites
One local cell can belong to only one DC-HSDPA group.
The two DC-HSDPA cells must belong to the same baseband board. Therefore, it is
recommended that all cells be configured in a downlink resource group. In this way, the
system automatically allocates resources so that cells in a DC-HSDPA group are created
on one baseband board.
The two DC-HSDPA cells must belong to the same sector.
Issue 06 (2013-03-25)

531
RAN14.0
For distributed cells, two local cells in a DC-HSDPA cell group must belong to one
RRU. For non-distributed cells, if two local cells in a DC-HSDPA cell group belong to
two RRUs, the RRUs adopt a star or chain topology.
In digital combining and dividing scenarios, two local cells in the DC group must belong
to one RRU.
The UEs must belong in categories 21 or later, as specified by the 3GPP specifications.
To enable the downlink 42 Mbit/s throughput of DC-HSDPA, the 64QAM must be
activated. For more details of the configuration of the 64QAM, see Configuring
Downlink 64QAM.
The UEs must belong in categories 21 or later(category 21, 22, 23, 24, 25, 26, 27, 28),
as specified by the 3GPP specifications.
Context
CAUTION
Activate this feature when the traffic volume in a cell is low. The reason is that the cell must be
deactivated before this feature is activated; after the cell is deactivated, the services in this cell
are disrupted.
Dual Cell-HSDPA (DC-HSDPA) allows an UE to establish downlink connections
simultaneously to two inter-frequency co-coverage cells that are configured with consecutive
frequencies and controlled by one NodeB. The two cells can schedule the UE simultaneously,
therefore increasing the downlink peak throughput of the UE.
The gain of downlink throughput is higher when the UE is located at the cell edge.
NOTE
l The CS service, IMS signaling, SRB signaling, or PS conversational service is carried on a single carrier
instead of DC-HSDPA because the amount of data is small and the gain is insignificant when DCHSDPA is used.
l The BE or streaming service can be carried over the DC-HSDPA. The BE/streaming combined service
is carried over the DC-HSDPA preferentially.
Data Configuration Plan

Parameters
Example
Source
ID of local cell 1
Network planning
ID of local cell 2
Network planning
Cell ID
1 and 2
Network planning
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD UNODEB (CME single configuration:
NodeB Configuration Express > IUB_RNC > NodeB Basic Information >
532
RAN14.0
NodeB; CME batch modification center: not supported). In this step, set NodeB
Protocol Version to R9.
2.
Run the BSC6900 MML command MOD UCNNODE (CME single configuration:
UMTS Global Configuration Express > Core Network > UMTS CN Node; CME
batch modification center: not supported). In this step, set CN protocol version to
R8.
3.
Modifying UMTS Cell Parameters in Batches) to deactivate the logical cell of local
cell 1.
4.
cell 2.
5.

Parameters in Batches). In this step, select CFG_HSDPA_DC_SWITCH from the
Channel Configuration Strategy Switch list.
6.
Preferred MIMO_64QAM or DC_HSDPA character to DC_HSDPA.
NOTE
If the switch parameter is set to DC_HSDPA, the network preferentially configures

DC_HSDPA for the UE.
Set this parameter to DC_HSDPA before the verification. After the verification is complete,
set this parameter according to actual network planning.
7.

Parameters in Batches). In this step, select DC_HSDPA from the Cell Hspa Plus
function switch list.
8.
Run the BSC6900 MML command LST UCELL (CME single configuration: UMTS
Cell Configuration Express > Cell Basic Information > Cell Basic Information)
to query the parameter Time Offset (TCELL) of the two cells. Ensure that the
parameter is set to the same value.
9.
Optional: Run the BSC6900 MML command MOD UCELLSETUP (CME single
Parameters in Batches) to change the time offset of a cell.
10. Run the NodeB MML command ADD DLDUALCELLGRP (CME single
configuration: NodeB Configuration Express > IUB_NodeB > Radio Layer >
Other Information > DLDUALCELLGRP; CME batch modification center: not
supported) to add a DC group of local cell 1 and local cell 2. In this step, set First
Issue 06 (2013-03-25)

533
RAN14.0
Local Cell ID and Second Local Cell ID respectively to the ID of local cell 1 and
local cell 2.
11. Run the BSC6900 MML command ACT UCELL (CME single configuration: UMTS
Modifying UMTS Cell Parameters in Batches) to activate the logical cell of local
cell 1.
12. Run the BSC6900 MML command ACT UCELL (CME single configuration: UMTS
cell 2.
l
1.
Click Uu Interface Trace on the LMT, as shown in Figure 159-1.
Figure 159-1 Uu Interface Trace dialogue box
2.
For cells with Cell DC-HSDPA Function Switch turned on, trace
RRC_RB_SETUP messages on the Uu interface.
3.
Perform dialing tests on FTP services for a UE to ensure that data is transmitted on
HSDPA channels.
4.
On the Trace tab page of the LMT, check whether RRC_RB_SETUP messages
contain the dl-SecondaryCellInfoFDD information element.
If the dl-SecondaryCellInfoFDD information element is contained, as shown in
Figure 159-2, it indicates that the feature is activated.
Issue 06 (2013-03-25)

534
RAN14.0
If the dl-SecondaryCellInfoFDD information element is not contained, it

indicates that the feature is not activated.
Figure 159-2 RRC_RB_SETUP message
1.

Parameters in Batches). In this step, deselect CFG_HSDPA_DC_SWITCH from
the Channel Configuration Strategy Switch list.
2.
cell 1.
3.
Run the NodeB MML command RMV DLDUALCELLGRP (CME single

Other Information > DLDUALCELLGRP; CME batch modification center: not
supported) to remove the DC-HSDPA cell group.
NOTE
To remove a DC-HSDPA cell group, you only need to remove one local cell in the group.
4.
cell 1.
----End
Example
//Modify the protocol version of the NodeB and CN
MOD UNODEB: IDTYPE=BYID, NodeBId=0, NodeBProtclVer=R9;
MOD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=PS_DOMAIN, CNProtclVer=R8;
//To deactivate cells, run the following command repeatedly:
//Setting channel configuration strategy switch
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DC_SWITCH-1;
//Setting preferred MIMO_64QAM or DC_HSDPA character
SET UFRC: MIMO64QAMorDcHSDPASwitch= DC_HSDPA;
//Setting Cell Hspa Plus function switch
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DC_HSDPA-1;
Issue 06 (2013-03-25)

535
RAN14.0

//Querying the parameter Time Offset (TCELL) of the cell
LST UCELL: LstType=ByCellId, CellId=1;
LST UCELL: LstType=ByCellId, CellId=2;
//Modifying the time offset of the cell
MOD UCELLSETUP: CellId=2, TCell=CHIP512;
//Configuring local cell 1 and local cell 2 as a DC-HSDPA cell group
ADD DLDUALCELLGRP: FIRSTLOCELL=1, SECONDLOCELL=2;
//Activating the cells
//To set Channel Configuration Strategy Switch, run the following
command:
//To deactivate cell, run the following command:
//To remove the DC-HSDPA cell group, run the following command:
RMV DLDUALCELLGRP: FIRSTLOCELL=1, SECONDLOCELL=2;
//To activate cell, run the following command:
Issue 06 (2013-03-25)

536
RAN14.0
160
Configuring HSPA+ Uplink 23 Mbit/

s per User
HSPA+ Uplink 23 Mbit/s per User.
Prerequisites
l
This feature has the following impact on the RNC hardware:
The DPUb or DPUe board must be configured.
In IP transmission mode, the GOUa, FG2A, POUc, FG2c or GOUc board must be
configured. The following table briefly describes the boards:
Board Name Description
FG2a
8-port FE or 2-port electronic GE interface unit REV:a
GOUa
2-port packet over GE Optical interface Unit REV:a
FG2c
12-port FE or 4-port electronic GE interface unit REV:c
GOUc
4-port packet over GE Optical interface Unit REV:c
POUc
4-port IP over channelized Optical STM-1/OC-3 interface Unit REV:c

Supporting IP over E1/T1 over SDH/SONET

In addition to the DPUb or DPUe board, the GOUa, FG2a, POUc, FG2c, or GOUc
board must be configured on the RNC.
All 3900 series base stations support this feature. The WBBPd or WBBPf board
must be configured on these base stations.
All DBS3800 series base stations support this feature. The EBBCd board must be
configured on these base stations.
Issue 06 (2013-03-25)

537
RAN14.0
The BTS3812E, BTS3812A and BTS3812AE support this feature. The EULPd
board must be configured on these base stations. Downlink services must be
established on the EBBI, EBOI or EDLP board.
When 4-way receive diversity is used, only 3900 series base stations (except the
BTS3902E) support this feature.
The uplink peak rate of 23 Mbit/s is applicable only to IP transmission scenarios.
The NodeB connects to the transmission equipment through the Ethernet port on the
transmission board.
The UE must support E-DPCCH Boosting and DC-HUSPA. The UE must be of
HSUPA UE category.
The CN is of 3GPP Release 7 or later to support a maximum uplink rate of 23 Mbit/
s or higher, which is promised at service subscription time.
l

WRFD-010694 UL 16QAM
WRFD-010697 E-DPCCH Boosting
WRFD-140204 DC-HSUPA
WRFD-010698 HSPA+ Uplink 11.5Mbit/s per User
License
Other Prerequisites
To support a peak rate of 23 Mbit/s of a single UE, the IP over Iub transmission is used
and the uplink bandwidth is greater than 25 Mbit/s.
On the NodeB side, run the SET ETHPORT or ADD ETHPORT command to set
Maximum Transmission Unit to 1500 or above. The default value of this parameter
is 1500.
The transmission network carried on the Iub interface supports the maximum
transmission unit (MTU) of greater than 1500 bytes. On the NodeB, the ping operation
is performed, with PING Packet Size set to 2990. If the ping operation succeeds, the
transmission network meets the requirements.
The UE must support E-DPCCH Boosting and DC-HUSPA.The UE must be of HSUPA
UE category 9.
The CN is of 3GPP Release 7 or later to support a maximum uplink rate of 23 Mbit/s
or higher, which is promised at service subscription time.
Procedure
l
Issue 06 (2013-03-25)
1.
Enable a DC-HSUPA UE supporting 16QAM to access the network and to establish

PS services on the E-DCH and HS-DSCH.
2.
On the BSC6900 LMT, start Monitoring UL Throughput and Bandwidth, as shown

in Figure 160-1.
538
RAN14.0
Figure 160-1 Performance monitoring result
Expected result: The bandwidth is 23 Mbit/s, and FTP uploading is normal. The feature
has been activated.
l
None
----End
Issue 06 (2013-03-25)

539
RAN14.0
161
Configuring DC-HSUPA
DC-HSUPA.
Prerequisites
l
All 3900 series base stations support this feature. The WBBPd or WBBPf board
must be configured on these base stations.
All DBS3800 series base stations support this feature. The EBBCd board must be
configured on these base stations.
The BTS3812E, BTS3812A and BTS3812AE configured with the EBBI, EBOI,
EULP, or EULPd board support this feature. Downlink services must be established
on the EBBI, EBOI or EDLP board.
When 4-way receive diversity is used, only 3900 series base stations (except the
BTS3902E) support this feature.
The uplink peak rate of 23 Mbit/s is applicable only to IP transmission scenarios.
The NodeB connects to the transmission equipment through the Ethernet port on the
transmission board. In addition to the DPUb or DPUe board, the GOUa, FG2a,
POUc, FG2c, or GOUc board must be configured on the RNC.

WRFD-010695 UL Layer 2 Improvement
WRFD-010652 SRB over HSDPA
WRFD-010636 SRB over HSUPA
WRFD-010696 DC-HSDPA
WRFD-010638 Dynamic CE Resource Management
License
Issue 06 (2013-03-25)

540
RAN14.0
To support a peak rate of 11.5 Mbit/s of a single UE, the license for the feature
WRFD-010698 HSPA+ Uplink 11.5 Mbit/s per User must be activated.
To support a peak rate of 23 Mbit/s of a single UE, the license for the feature
WRFD-140203 HSPA+ Uplink 23 Mbit/s per User must be activated.
l
Other Prerequisites
Two DC-HSUPA cells must be on intra-band adjacent carriers that provide the same
coverage.
Two adjacent carriers are available and DC-HSDPA has been configured in the
downlink.
To support a peak rate of 23 Mbit/s of a single UE, the IP over Iub transmission is used
and the uplink bandwidth is greater than 25 Mbit/s.
On the NodeB side, run the SET ETHPORT or ADD ETHPORT command to set
Maximum Transmission Unit to 1500. The default value of this parameter is 1500.
The UE must comply with 3GPP Release 9 or later.
The UE must be of HSUPA UE category 8 or 9.
Category-8 UEs support only DC-HSUPA+QPSK. Their peak rate is 11.5 Mbit/s.
Category-9 UEs support DC-HSUPA+16QAM. Their peak rate is 23 Mbit/s.
Context
Before DC-HSUPA is configured, DC-HSDPA must be configured in cells. For details, see 159
Configuring DC-HSDPA.
Procedure
l
1.
Run the NodeB MML command ADD ULDUALCELLGRP (CME single

Information > Radio Management > Other Information >
ULDUALCELLGRP; CME batch modification center: not supported) to configure
cells in a DC-HSUPA carrier group.
2.
To enable the DC-HSUPA algorithm on the RNC, Run the BSC6900 MML
select CFG_HSUPA_DC_SWITCH under Channel Configuration Strategy
Switch.
3.
To configure the cell capability on the RNC, Run the BSC6900 MML command MOD
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, select
DC_HSUPA(Cell DC-HSUPA Function Switch) under Cell Hspa Plus function
switch.
NOTE
DC-HSUPA must be enabled for the two cells. Logical cells corresponding to the local cells
on the NodeB must be configured.
4.
Issue 06 (2013-03-25)
To configure DC-HSUPA periodic retry capability, Run the BSC6900 MML

541
RAN14.0

RNC Oriented FRC Algorithm Parameters; CME batch modification center: 3.15
Modifying RNC Parameters in Batches). In this step, select DC_HSUPA under
HSPA Technologies Retried by UEs.
5.

Type of Channel Preferably Carrying Signaling RB to HSPA
(UL_EDCH,DL_HSDSCH).
6.
Enable the HSUPA TTI Selection feature or algorithm of coverage-based BE service

fallback from E-DCH to DCH.
If the HSUPA TTI Selection feature has been activated on the RNC, Run the
BSC6900 MML command SET UCORRMALGOSWITCH (CME single
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH, and
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH under Dynamic Resource
Allocation Switch.
If the HSUPA TTI Selection feature has not been activated on the RNC. In this
step, Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME
Parameters in Batches) to enable the algorithm of coverage-based BE service
fallback from E-DCH to DCH. In this step, select
RESERVED_SWITCH_0_BIT7 under CORRM Algorithm Reserved Switch
0.
1.
Issue 06 (2013-03-25)
In the Navigation Tree pane on the RNC LMT, click the Trace tab. In the displayed
Trace Navigation Tree pane, double-click UMTS Services. On the unfolded list,
double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box,
select RRC_RB_SETUP to trace Uu interface signaling messages of DC-HSUPA
cells, as shown in Figure 161-1.

542
RAN14.0
2.
Perform dialing tests on FTP services for a DC-HSUPA UE and ensure that HSUPA
services have been set up.
3.
On the Trace tab page of the BSC6900 LMT, check whether the
RRC_RB_SETUP messages contain the ul-SecondaryCellInfoFDD information
element (IE). If the IE is contained, the DC-HSUPA feature has been activated, as
Figure 161-2 Message Explanation
NOTE
Deactivating the DC-HSUPA feature decreases cell uplink throughput.
1.
Disable the DC-HSUPA algorithm on the RNC.

To disable the DC-HSUPA feature of the entire RNC, Run the BSC6900 MML
clear CFG_HSUPA_DC_SWITCH under Channel Configuration Strategy
Switch.
To disable the DC-HSUPA feature of a specified cell, Run the BSC6900 MML
command MOD UCELLALGOSWITCH (CME single configuration: UMTS
Issue 06 (2013-03-25)

543
RAN14.0
Cell Configuration Express > Cell Parameters > Cell Algorithm Switches;
CME batch modification center: 3.18 Modifying UMTS Cell Parameters in
Batches). In this step, clear DC_HSUPA(Cell DC-HSUPA Function Switch)
under Cell Hspa Plus function switch.
2.
Optional: Run the NodeB MML command RMV ULDUALCELLGRP (CME

single configuration: NodeB Configuration Express > IUB_NodeB > Basic
Information > Radio Management > Other Information >
ULDUALCELLGRP; CME batch modification center: not supported) to remove a
carrier group.
----End
Example
ADD ULDUALCELLGRP: FIRSTLOCELL=0, SECONDLOCELL=2;
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSUPA_DC_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DC_HSUPA-1;
SET UFRC: RetryCapability=DC_HSUPA-1;
DraSwitch=DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH-1&DRA_BASE_COVER_BE_TTI_L2
_OPT_SWITCH-1&DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH-1;
SET UCORRMALGOSWITCH: ReservedSwitch0=RESERVED_SWITCH_0_BIT7-1;
//Deactivating the DC-HSUPA feature of the entire RNC
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSUPA_DC_SWITCH-0;
//Deactivating the DC-HSUPA feature of a specified cell
//(Optional) Removing a NodeB carrier group
RMV ULDUALCELLGRP: FIRSTLOCELL=0, SECONDLOCELL=2;
Issue 06 (2013-03-25)

544
RAN14.0
162
Configuring Downlink Enhanced

CELL_FACH
Downlink Enhanced CELL_FACH.
Prerequisites
l
HBBI and HDLP on BTS3812E/BTS3812AE do not support this feature, EBBI, EDLP
is needed.
BBU3806 does not support this feature, EBBC or EBBCd is needed.
3900 series NodeB: WBBPa does not support this feature, and WBBPb, WBBPd or
WBBPf board are needed.

feature depends on the feature WRFD-010685 Downlink Enhanced L2.
License
Other Prerequisites
The UE must be Release 7 (or later) UE and support this feature.
Context
This feature enables the FACH to be carried on the HS-DSCH. Based on this feature, the UE
can receive data at a higher rate in CELL_FACH state.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches) to select E_FACH(Cell E_FACH Function Switch) and
545
RAN14.0
DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch) from the dropdown list Cell Hspa Plus function switch.
2.

Parameters in Batches) to add HUDPA parameters of a cell.
3.
Run the BSC6900 MML command ADD UCELLEFACH (CME single

Enhanced FACH parameters; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches) to add enhanced CELL_FACH state parameters
of a cell.
4.
Run the BSC6900 MML command ACT UCELLHSDPA (CME single

HSDPA Parameters. Set ACTSTATUS to Activated; CME batch modification
center: No supported) to activate HSDPA feature.
5.
Run the BSC6900 MML command ACT UCELLEFACH (CME single

Enhanced FACH parameters. Set Validation indication to Activated; CME batch
modification center: No supported) to activate this feature.
1.
Run the BSC6900 MML command DSP UCELL to check whether EFACH is
available.
The value of Status of EFACH is EFACH available.
1.

Parameters in Batches) to clear E_FACH(Cell E_FACH Function Switch) and
DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch) from the dropdown list Cell Hspa Plus function switch.
2.
Run the BSC6900 MML command DEA UCELLEFACH (CME single

Enhanced FACH parameters. Set Validation indication to Deactivated; CME
batch modification center: No supported) to deactivate this feature.
----End
Example
//Activating Downlink Enhanced CELL_FACH
MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_FACH-1&DL_L2ENHANCED-1;
CodeAdjForHsdpaSwitch=ON;
ADD UCELLEFACH: CellId=11;
ACT UCELLEFACH: CellId=11;
//Deactivating Downlink Enhanced CELL_FACH
MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_FACH-0&DL_L2ENHANCED-0;
DEA UCELLEFACH: CellId=11;
Issue 06 (2013-03-25)

546
RAN14.0
163 Configuring Performance Improvement of MIMO and

HSDPA Co-carrier
163
Configuring Performance
Improvement of MIMO and HSDPA Co-carrier

Performance Improvement of MIMO and HSDPA Co-carrier.
Prerequisites
l
This feature is only supported by 40W RRU3801C, RRU3804, RRU3806, RRU3808,
WRFU, RRU3805, WRFUd, RRU3828, RRU3829, RRU3928, RRU3929, MRFUd,
MRFUe and 850M/900M/1900M RRU3908V1.
The BTS3812E/AE cannot support this feature.
The RRU3908 V2 and MRFU V2 modules support this feature from RAN14.0.

WRFD-010685 Enhanced L2
WRFD-010684 2x2 MIMO
License
Other Prerequisites
The UE must be support 2x2 MIMO.
The UE is of category 15, 16, 17, 18, as specified by the 3GPP protocols.
Context
CAUTION
Before enabling the feature in an existing cell, you need to deactivate the cell. This, however,
will interrupt services in the cell. Therefore, you should enable the feature when the traffic of
the cell is low.
Issue 06 (2013-03-25)

547
RAN14.0

HSDPA Co-carrier
The feature adopts MIMO in Primary/Secondary common Pilot (PSP) mode, Virtual Antenna
Mapping (VAM), and Intelligent Interference Control (ICC), improving performance of MIMO
and HSDPA co-carrier.
Data Planning
Parameters
Example
Source
Site Number
Network plan
Sector number
Network plan
Local cell ID
Network plan
Cell ID
Network plan
SCPICH ID
Network plan
Transmit power of SCPICH

[0.1 dB]
Network plan
Procedure
l
1.
Modifying UMTS Cell Parameters in Batches) to deactivate MIMO cells.
2.
a.
b.
Parameters in Batches) to add a local cell. In this step, set VAM to TRUE
(TRUE), TTW to TRUE and Precoding Weight Set Restriction Switch to
TRUE.
3.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set IIC
Switch to OPEN(open).
4.
Configure the PSP function on the BSC6900 side.

configuration: UMTS Cell Configuration Express > Cell Basic Information >
Cell Basic Information; CME batch modification center: 3.18 Modifying UMTS
Cell Parameters in Batches) to modify the cell basic information. In this step, set
TX Diversity Indication to FALSE.
Run the BSC6900 MML command ADD USCPICH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > SCPICH;
Issue 06 (2013-03-25)

548
RAN14.0

HSDPA Co-carrier
CME batch modification center: 3.20 Modifying UMTS Channel Parameters in

Batches) to add a secondary common pilot channel (SCPICH).
5.
1.
Run the NodeB MML command LST LOCELL. In this step, check that VAM is
TRUE.
2.
Run the NodeB MML command LST MACHSPARA. In this step, check that IIC
Switch is OPEN.
3.
Run the BSC6900 MML command LST USCPICH. In this step, check that an
SCPICH is already configured.
1.
Modifying UMTS Cell Parameters in Batches) to deactivate MIMO cells.
2.
a.
b.
Parameters in Batches) to add a local cell. In this step, set VAM to FALSE
(FALSE) and TTW to FALSE.
3.
3.17 Modifying Physical NodeB Parameters in Batches). In this step, set IIC
Switch to CLOSE(close).
4.
Disable the PSP function on the BSC6900 side.

Run the BSC6900 MML command RMV USCPICH (CME single configuration:
UMTS Cell Configuration Express > Channel Configuration > SCPICH;
CME batch modification center: not supported) to remove a secondary common
pilot channel (SCPICH).
5.
----End
Example
l
NodeB V200R014
//Activation procedure (using an RRU with only one transmit channel as
an example)
Issue 06 (2013-03-25)

549
RAN14.0

HSDPA Co-carrier
//Deactivating an MIMO cell
HISPM=FALSE, RMTCM=FALSE, VAM=TRUE, PRECDWSRSW=TRUE;
//Turing on the IIC switch
SET MACHSPARA: LOCELL=1, IICSW=OPEN;
//Configuring the PSP function
ADD USCPICH: CellId=1, ScpichPhyId=5, ScpichPower=0;
//Activating a cell
//Checking parameter settings of VAM of the local cell
//Checking whether IIC switch is turned on
//Checking configuration information about an SCPICH
LST USCPICH: CellId=1;
//Adding a local cell and setting VAM
HISPM=FALSE, RMTCM=FALSE, VAM=FALSE;
//Turing off the IIC switch
SET MACHSPARA: LOCELL=1, IICSW=CLOSE;
//Removing an SCPICH
RMV USCPICH: CellId=1;
//Activating a cell
NodeB V100R014
//Activation procedure (using an RRU with only one transmit channel as
an example)
//Adding a local cell and setting Two Tx Way and VAM (assuming that
DBS3800 is used)
Issue 06 (2013-03-25)

550
RAN14.0

HSDPA Co-carrier
SRN1=60, SRN2=61, SN2=0, ULFREQ=9845, DLFREQ=10795, HISPM=FALSE,
MXPWR=460, RMTCM=FALSE, VAM=TRUE, PRECDWSRSW=TRUE;
//Turing on the IIC switch
SET MACHSPARA: LOCELL=1, IICSW=OPEN;
//Configuring the PSP function
ADD USCPICH: CellId=1, ScpichPhyId=5, ScpichPower=0;
//Activating a cell
//Checking parameter settings of VAM of the local cell
//Checking whether IIC switch is turned on
//Checking configuration information about an SCPICH
LST USCPICH: CellId=1;
//Adding a local cell and setting VAM (assuming that DBS3800 is used)
SRN1=60, SRN2=61, SN2=0, ULFREQ=9845, DLFREQ=10795, HISPM=FALSE,
MXPWR=460, RMTCM=FALSE, VAM=FALSE;
//Turing off the IIC switch
SET MACHSPARA: LOCELL=1, IICSW=CLOSE;
//Removing an SCPICH
RMV USCPICH: CellId=1;
//Activating a cell
Issue 06 (2013-03-25)

551
RAN14.0
164
Configuring CPC - DTX /DRX
CPC - DTX /DRX.
Prerequisites
l
EULP/EULPd (supporting DTX), and EDLP (supporting DRX) boards.

WRFD-010636 SRB over HSUPA and WRFD-010652 SRB over HSDPA.
License
Other Prerequisites
The UE is of 3GPP Release 7 or later and supports this feature.
Context
This feature is related to DTX and DRX. It can reduce the interference between UEs, improve
the HSPA+ user capacity per cell and save the battery consumption of the UE.
Procedure
l
1.
Issue 06 (2013-03-25)

552
RAN14.0
Parameters in Batches). In this step, select DTX_DRX(Cell DTX_DRX Function

Switch) from the Cell Hspa Plus function switch drop-down list.
2.

Parameters in Batches). In this step, select CFG_HSPA_DTX_DRX_SWITCH
from the Channel Configuration Strategy Switch drop-down list.
3.

select HSPA(UL_EDCH,DL_HSDSCH) from the Type of Channel Preferably
Carrying Signaling RB drop-down list.
1.
Create a Uu tracing task on the BSC6900 LMT, as shown in Figure 164-1.
Figure 164-1 Uu interface tracing task
Issue 06 (2013-03-25)
2.
Use an HSPA-capable UE to establish a new service.
3.
Check whether the following IEs are included in the RRC_RB_SETUP message, as

553
RAN14.0
Figure 164-2 IE information
dtx-drx-TimingInfo
dtx-drx-Info
l
1.

Parameters in Batches). In this step, deselect DTX_DRX(Cell DTX_DRX
Function Switch) from the Cell Hspa Plus function switch drop-down list.
----End
Example
//Activating CPC - DTX /DRX
MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=DTX_DRX-1;
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_DTX_DRX_SWITCH-1;
//Deactivating CPC - DTX /DRX
MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=DTX_DRX-0;
Issue 06 (2013-03-25)

554
RAN14.0
165
Configuring CPC - HS-SCCH less

operation
CPC - HS-SCCH less operation.
Prerequisites
l

feature depends on the feature WRFD-010652 SRB over HSDPA, WRFD-010636 SRB
over HSUPA.
License
Other Prerequisites
The UE must be Release-7 (or later) to support this feature.
Context
This feature supports the HS-SCCH less operation function. With this feature, UE can receive
data from HS-PDSCH without sending data on HS-SCCH. This increases the capacity of
downlink data services.
Procedure
l
1.
Issue 06 (2013-03-25)

555
RAN14.0
CFG_HSPA_HSSCCH_LESS_OP_SWITCH in the Channel configuration

strategy switch parameter to switch on the HS-SCCH less operation function.
2.

Parameters in Batches). In this step, select HS_SCCH_LESS_OPERATION(Cell
HS_SCCH LESS OPERATION Function Switch) in the Cell Hspa Plus function
switch parameter to activate the HS-SCCH less operation function at the cell level.
1.
Use an HSPA-supportive UE to initiate a PS service. The service is carried on E-DCH

and HS-DSCH.
NOTE
How to make the service on E-DCH, see section 97 Configuring HSUPA Introduction Package.
2.
Check the RRC_RB_SETUP message traced over the Uu interface. You can find the
hs-scch-LessInfo IE which contains the parameters related to CPC-HSSCCH less
operation, as shown in Figure 165-1.
Figure 165-1 RRC_RB_SETUP Information
l
Issue 06 (2013-03-25)
556
RAN14.0
1.

CFG_HSPA_HSSCCH_LESS_OP_SWITCH in the Channel configuration
strategy switch parameter to switch off the HS-SCCH less operation function.
2.

Parameters in Batches). In this step, deselect HS_SCCH_LESS_OPERATION
(Cell HS_SCCH LESS OPERATION Function Switch) in the Cell Hspa Plus
function switch parameter to deactivate the HS-SCCH less operation function at the
cell level.
----End
Example
//Activating CPC-HS-SCCH Less operation
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_HSSCCH_LESS_OP_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=HS_SCCH_LESS_OPERATION-1;
//Deactivating CPC-HS-SCCH Less operation
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_HSSCCH_LESS_OP_SWITCH-0;
MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=HS_SCCH_LESS_OPERATION-0;
Issue 06 (2013-03-25)

557
RAN14.0
166
Configuring E-DPCCH Boosting
E-DPCCH Boosting.
Prerequisites
l
The BTS3812E/BTS3812AE is configured with the Enhanced NodeB HSPA supported
Uplink Processing unit REV:d (EULPd) board, and the downlink services cannot be set
up on HBBI/HDLP/NDLP board.
The DBS3800 is configured with the Enhanced Base Band Card REV:d (EBBCd) board.
3900 series base stations are configured with WBBPd or WBBPf boards.

License
Others
The UE is of 3GPP Release-7 or later and supports this feature.
CN supports data bit rate of 11.5Mbit/s or above.
Context
An E-DCH Dedicated Physical Control Channel (E-DPCCH) is used for channel estimation to
improve the estimation accuracy when the HSUPA service data is demodulated. In this way, the
requirement for Dedicated Physical Control Channel (DPCCH) power is lowered, increasing
the HSUPA service rate.
Procedure
l
Issue 06 (2013-03-25)

558
RAN14.0

NOTE
When this feature is enabled together with the feature WRFD-010694 Uplink 16QAM, you are
advised to configure the network bandwidth over the Iub interface to 16 Mbit/s or higher if ATM
transmission is applied and to 15 Mbit/s or higher if IP transmission is applied.
1.
2.
Issue 06 (2013-03-25)
Configure the bandwidth over the Iub interface in ATM transmission mode.
a.
Configure the type of primary and secondary paths required by various services:
Run the BSC6900 MML command ADD TRMMAP (CME single
Resources Configuration > Transport Resource Mapping; CME batch
modification center: not supported). In this step, specify TRMMAP ID, set
Interface Type to IUB (Iub Interface) and Transport Type to ATM(ATM),
and specify SRB primary path and SRB secondary path.
b.
Add an activation factor table: Run the BSC6900 MML command ADD
TRMFACTOR (CME single configuration: UMTS Global Configuration
Express > Transmission Resources Configuration > Factor Table; CME
batch modification center: not supported). In this step, specify Factor table
index and Remark, and change the activation factor.
c.
Add the TRM mapping to an adjacent node: Run the BSC6900 MML
command ADD ADJMAP (CME single configuration: NodeB Configuration
Express > IUB_RNC > ATM Transport > Adjacent Node Mapping; CME
batch modification center: not supported). In this step, set Interface Type to
IUB (Iub Interface) and Transport Type of the adjacent node and interface
type to ATM(ATM), and specify Gold user TRMMAP index, Silver user
TRMMAP index, Bronze user TRMMAP index, and Factor table index.
d.
Add ATM traffic records corresponding to the type of the primary and secondary
paths set in 1.1 (you are advised to configure the network bandwidth over the
Iub interface to 16 Mbit/s or higher): Run the BSC6900 MML command ADD
ATMTRF (CME single configuration: NodeB Configuration Express >
IUB_RNC > ATM Transport > ATM Traffic Record; CME batch
modification center: not supported). In this step, specify Traffic index, Service
type, Rate unit, and Peak cell rate.
e.
Add an AAL2 path: Run the BSC6900 MML command ADD AAL2PATH
(CME single configuration: NodeB Configuration Express > IUB_RNC >
ATM Transport > AAL2 Path; CME batch modification center: not supported).
In this step, specify TX traffic record index and RX traffic record index.
Configure the bandwidth over the Iub interface in IP transmission mode.

a.
Configure the type of primary and secondary paths required by various services:
Run the BSC6900 MML command ADD TRMMAP (CME single
Resources Configuration > Transport Resource Mapping; CME batch
modification center: not supported). In this step, specify TRMMAP ID, set
Interface Type to IUB (Iub Interface) and Transport Type to IP(IP), and
specify SRB primary path and SRB secondary path.
b.
Add an activation factor table: Run the BSC6900 MML command ADD
TRMFACTOR (CME single configuration: UMTS Global Configuration
Express > Transmission Resources Configuration > Factor Table; CME
batch modification center: not supported). In this step, specify Factor table
index and Remark, and change the activation factor.
c.
Add the TRM mapping to an adjacent node: Run the BSC6900 MML
command ADD ADJMAP (CME single configuration: NodeB Configuration
559
RAN14.0
Express > IUB_RNC > IP Transport > Adjacent Node Mapping; CME batch
modification center: not supported). In this step, set Interface Type to IUB (Iub
Interface) and Transport Type of the adjacent node and interface type to IP
(IP), and specify Gold user TRMMAP index, Silver user TRMMAP index,
Bronze user TRMMAP index, and Factor table index.
3.
d.
Add an IP path (you are advised to configure the network bandwidth over the
Iub interface to 15 Mbit/s or higher): Run the BSC6900 MML command ADD
IPPATH (CME single configuration: NodeB Configuration Express >
IUB_RNC > IP Transport > IP Path; CME batch modification center: not
supported). In this step, specify Interface Type, Transport Type, IP path
type, Forward Bandwidth, and Backward Bandwidth.
e.
Optional: Set the mapping from the PHB to the DSCP based on the service type:
Run the BSC6900 MML command SET PHBMAP (CME single configuration:
Device Panel > Board > Mapping Table Between PHB And DSCP; CME
batch modification center: not supported).
Configure the E-DPCCH Boosting function.

a.
Turn on the E-DPCCH Boosting algorithm switch: Run the BSC6900 MML
command SET UCORRMALGOSWITCH (CME single configuration:
Switch Configuration > Connection Oriented Algorithm Switches; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches). In
this step, set Channel Configuration Strategy Switch to
CFG_EDPCCH_BOOSTING_SWITCH.
b.
Optional: If streaming services are to be enabled with E-DPCCH Boosting, run

the BSC6900 MML command SET UCORRMALGOSWITCH (CME single
Parameters in Batches). In this step, set Service Mapping Strategy Switch to
MAP_PS_STREAM_ON_HSUPA_SWITCH to ensure that streaming
services are carried over HSUPA.
c.
Set the rate threshold for BE services and streaming services carried over
HSUPA: Run the BSC6900 MML command SET UFRCCHLTYPEPARA
Basic Resource Control Parameter Configuration > Channel Type
Parameters in Batches). In this step, specify UL streaming traffic threshold
on HSUPA and UL BE traffic threshold on HSUPA.
d.
Optional: Configure HSUPA-related parameters for a cell: Run the BSC6900

MML command ADD UCELLHSUPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Configuration of HSUPA in
Cell; CME batch modification center: 3.18 Modifying UMTS Cell Parameters
in Batches).
NOTE
Retain the default values of Code Number for E-AGCH, Code Number for E-RGCH/
E-HICH, Maximum Target Uplink Load Factor, and Target Non-serving E-DCH
to Total E-DCH Power Ratio.
e.
Issue 06 (2013-03-25)
Activate the HSUPA function for a cell: Run the BSC6900 MML command ACT
UCELLHSUPA (CME single configuration: UMTS Cell Configuration
560
RAN14.0
Express > Cell Parameters > Configuration of HSUPA in Cell. Set Cell
HSUPA state to Activated; CME batch modification center: No supported).
f.
Enable the E-DPCCH Boosting function for a cell: Run the BSC6900 MML
command MOD UCELLALGOSWITCH (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell Algorithm Switches;
Batches). In this step, set Cell Hspa Plus function switch to
EDPCCH_BOOSTING(Cell E-DPCCH Boosting Function Switch).
g.
Turn on the E-DPCCH Boosting retry algorithm switch: Run the BSC6900 MML
set HSPA Technologies Retried by UEs to EDPCCH_BOOSTING.
h.
Enable the E-DPCCH Boosting function for a cell on the NodeB side: Run the
NodeB MML command MOD LOCELL (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > xx Sector > Locell;
CME batch modification center: 3.17 Modifying Physical NodeB Parameters
in Batches).
1.
Establish PS BE HSUPA services with the uplink rate higher than 1 Mbit/s.
2.
Trace messages over the Uu interface by referring to Tracing Messages on the Uu

Interface to check whether the RRC_RB_SETUP message carries the e-TFC-BoostInfo information element (IE) that includes the e-TFCI-Boost and delta-T2TP fields,
as shown in Figure 166-1.
Figure 166-1 Tracing messages over the Uu interface
3.
Issue 06 (2013-03-25)
Trace messages over the Iub interface by referring to Tracing Messages on the Iub
Interface to check whether the NBAP_RL_RECFG_PREP message carries the eTFCI-Boost-Information IE that includes the e-TFCI-BetaEC-Boost and uLDelta-T2TP fields, as shown in Figure 166-2.

561
RAN14.0
Figure 166-2 Tracing messages over the Iub interface
If the messages described in the preceding two steps carry the corresponding IEs,
the E-DPCCH Boosting function has taken effect.
If either of the messages described in the preceding two steps does not carry the
corresponding IEs, the E-DPCCH Boosting function has not taken effect.
l
1.
To disable the E-DPCCH Boosting function of all cells under the BSC6900, do as
follows: Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME
CFG_EDPCCH_BOOSTING_SWITCH check box under the parameter Channel
2.
To disable the E-DPCCH Boosting function in a single cell, do as follows:

a.
Method 1: Run the BSC6900 MML command MOD

Batches). In this step, deselect the EDPCCH_BOOSTING(Cell E-DPCCH
Boosting Function Switch) check box under the parameter Cell Hspa Plus
function switch to disable the E-DPCCH Boosting function in a cell on the
BSC6900 side.
b.
Method 2: Run the NodeB MML command MOD LOCELL (CME single
> xx Sector > Locell; CME batch modification center: 3.17 Modifying Physical
NodeB Parameters in Batches) to disable the E-DPCCH Boosting function in
a cell on the NodeB side.
----End
Example
/*Activating E-DPCCH Boosting */
/*Configuring the network bandwidth over the Iub interface in ATM
Issue 06 (2013-03-25)

562
RAN14.0
transmission mode*/
//Configuring the type of the primary and secondary paths required by
various services
ADD TRMMAP: TMI=15, ITFT=IUB, TRANST=ATM, SRBPRIPATH=RT_VBR,
SRBSECPATH=UBR;
//Adding an activation factor table
ADD TRMFACTOR: FTI=20, REMARK="Iub";
//Adding the TRM mapping to an adjacent node
ADD ADJMAP: ANI=4, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE, TMIGLD=15,
TMISLV=15, TMIBRZ=15, FTI=20;
//Adding ATM traffic records corresponding to the type of the primary and
secondary paths required by various services
ADD ATMTRF: TRFX=150, ST=RTVBR, UT=KBIT/S, PCR=16000, SCR=15000;
ADD ATMTRF: TRFX=151, ST=UBR, UT=KBIT/S, PCR=16000;
//Adding AAL2 paths
ADD AAL2PATH:ANI=4, PATHID=1, CARRYT=IMA, CARRYF=2, CARRYSN=14,
OWNERSHIP=LOCAL, TIMERCU=10, TRMLOADTHINDEX=0, AAL2PATHT=SHARE;
ADD AAL2PATH:ANI=4, PATHID=2, CARRYT=IMA, CARRYF=2, CARRYSN=14,
OWNERSHIP=LOCAL, TIMERCU=10, TRMLOADTHINDEX=0, AAL2PATHT=SHARE;
/*Configuring the network bandwidth over the Iub interface in IP
transmission mode*/
//Configuring the type of the primary and secondary paths required by
various services
ADD TRMMAP: TMI=16, ITFT=IUB, TRANST=IP, SRBPRIPATH=AF11,
SRBSECPATH=AF12;
//Adding an activation factor table
ADD TRMFACTOR: FTI=21, REMARK="Iub";
//Adding the TRM mapping to an adjacent node
ADD ADJMAP: ANI=0, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=16,
//Adding IP paths
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF11,
TXBW=45000, RXBW=30000, CARRYFLAG=NULL, VLANFlAG=DISABLE,
PATHCHK=DISABLED;
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF12,
TXBW=45001, RXBW=30001, CARRYFLAG=NULL, VLANFlAG=DISABLE,
PATHCHK=DISABLED;
//(Optional) Setting the mapping from the PHB to the DSCP
SET PHBMAP: SRN=0, SN=14, PHB=AF11, DSCP=40;
SET PHBMAP: SRN=0, SN=14, PHB=AF12, DSCP=41;
/*Configuring the E-DPCCH Boosting function*/
//Turning on the E-DPCCH Boosting algorithm switch
Issue 06 (2013-03-25)

563
RAN14.0
//(Optional) Setting streaming services to ensure that they are carried

over HSUPA
//Setting the rate threshold for BE services and streaming services
carried over HSUPA
SET UFRCCHLTYPEPARA: UlStrThsOnHsupa=D64, UlBeTraffThsOnHsupa=D64;
//Configuring the HSUPA function for a cell
ADD UCELLHSUPA: CellId=1, EagchCodeNum=1, ErgchEhichCodeNum=1,
MaxTargetUlLoadFactor=75, NonServToTotalEdchPwrRatio=0;
//Activating the HSUPA function for a cell
ACT UCELLHSUPA: CellId=1;
//Enabling the E-DPCCH Boosting function for a cell
//Turning on the E-DPCCH Boosting retry algorithm switch
SET UFRC: RetryCapability=EDPCCH_BOOSTING-1;
//Enabling the E-DPCCH Boosting function in a cell on the NodeB side
MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, BOOST=TRUE;
/*Deactivating E-DPCCH Boosting */
//Disabling the E-DPCCH Boosting function in all cells on the RNC side
//Disabling the E-DPCCH Boosting function in a cell on the BSC6900 side
//Disabling the E-DPCCH Boosting function in a cell on the NodeB side
MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, BOOST=FALSE;
Issue 06 (2013-03-25)

564
RAN14.0
167
Configuring Uplink Enhanced

CELL_FACH
Uplink Enhanced CELL_FACH.
Prerequisites
l
Dependencies on the NodeB:
The BTS3812E, BTS3812A and BTS3812AE must be configured with the EULPd,
EBBI, EBOI or EULP board. The downlink services must be set up on the EBBI,
EBOI, or EULP board. The E-AI is not supported.
The DBS3800 must be configured with the EBBC or EBBCd board. The downlink
services must be set up on the EBBC or EBBCd board. To support the E-AI, the
DBS3800 must be configured with the EBBCd board.
The 3900 series base station must be configured with the WBBPb, WBBPd, or
WBBPf board. The downlink services must be set up on the WBBPb, WBBPd, or
WBBPf board. To support the E-AI, the 3900 series base station must be configured
with the WBBPd or WBBPf board.

WRFD-010688 Downlink Enhanced CELL_FACH
WRFD-010695 UL Layer 2 Improvement
License
Other Prerequisites
The UE must be Release-8 (or later) UE and support uplink for CELL_FACH
enhancement state.
Issue 06 (2013-03-25)

565
RAN14.0
Context
This feature enables the random access channel (RACH) to be mapped onto the E-DCH
Dedicated Physical Data Control Channel (E-DPDCH). With this feature, UEs in the
CELL_FACH state can transmit uplink data at higher rates.
Procedure
l
1.
Run the BSC6900 MML command ADD UERACHBASIC (CME single

ERACH Basic Information; CME batch modification center: not supported) to add
basic information about the Enhanced RACH (ERACH) function, namely Uplink
Enhanced CELL_FACH in a cell. In this step, set TTI for Common E-DCH.
2.
Run the BSC6900 MML command ACT UCELLERACH (CME single

configuration: UMTS Cell Configuration Express > Cell Parameters > ERACH
Function. Set Cell ERACH state to Activated; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to activate this feature.
3.
Run the NodeB MML commandMOD LOCELL (CME single configuration: NodeB
Batches) to enable the UL L2 Enhanced and the ERACH function. In this step, set
the UL L2 Enhanced to TRUE, and set the ERACH to TRUE.
1.
Run the BSC6900 MML command DSP UCELL to check whether the ERACH is
available.
1.
Run the BSC6900 MML command DEA UCELLERACH (CME single

configuration: UMTS Cell Configuration Express > Cell Parameters > ERACH
Function. Set Cell ERACH state to Deactivated; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches) to deactivate this feature.
----End
Example
//Activating Uplink Enhanced CELL_FACH
ADD UERACHBASIC: CellId=11, CommonEdchTTISelect=TTI_10MS;
ACT UCELLERACH: CellId=11;
MOD LOCELL: LOCELL=11, SECT=REMOTE_SECTOR, UL_L2PLUS=TRUE, ERACH=TRUE;
//Verifying Uplink Enhanced CELL_FACH
//Deactivating Uplink Enhanced CELL_FACH
DEA UCELLERACH: CellId=11;
Issue 06 (2013-03-25)

566
RAN14.0
168
Configuring 96 HSDPA Users per

Cell
Prerequisites
l
In order to support this feature, EBBI, EBOI, EULP, EULPd is needed for BTS3812E
and BTS3812AE.
EBBC, EBBCd is needed for BBU3806.
WBBPb, WBBPd or WBBPf is needed for BBU3900.

WRFD-010639 96 HSUPA Users per Cell, WRFD-010623 64 HSDPA Users per Cell
and WRFD-010686 CPC-DTX/DRX.
License
Context
This feature enables an HSDPA cell to serve a maximum of 96 users performing VoIP or other
low-rate services, increasing capacity of voice services or other low-rate services.
Procedure
l
1.
l
Issue 06 (2013-03-25)
Cell Parameters in Batches) to set the Maximum HSDPA user number to 96.
567
RAN14.0
1.

2.
Use UEs to access the cell successively and then establish PS services, for example,
download files through FTP.
3.
Check the maximum number of users through the counter

VS.HSDPA.UE.Max.Cell on the M2000.
NOTE
The 96 HSDPA users referred to in this feature are of the SRB Over HSPA type.
1.
----End
Example
/*Activating 96 HSDPA Users per Cell*/
//Setting the maximum number of HSDPA users to 96
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=96;
Issue 06 (2013-03-25)

568
RAN14.0
169

Cell
Prerequisites
l
In order to support this feature, EBBI, EBOI, EULP, EULPd is needed for BTS3812E
and BTS3812AE.
EBBC, EBBCd is needed for BBU3806.
WBBPb, WBBPd or WBBPf is needed for BBU3900.

WRFD-010634 60 HSUPA Users per Cell, WRFD-010653 96 HSDPA Users per Cell
and WRFD-010686 CPC-DTX/DRX.
License
Context
This feature enables an HSUPA cell to serve a maximum of 96 users performing VoIP or other
low-rate services, increasing the capacity of voice services or other low-rate services per cell.
Procedure
l
1.
Issue 06 (2013-03-25)

UMTS Cell Parameters in Batches) to set Code Number for E-AGCH and Code
Number for E-RGCH/E-HICH to appropriate values.
569
RAN14.0
2.
Cell Parameters in Batches) to stop reserving uplink and downlink credit resources
by setting UL handover credit reserved SF and DL handover credit and code
reserved SF to SFOFF(SFOFF), and setting Maximum HSUPA user number to
96.
1.

2.
upload files through FTP.
3.
Check the maximum number of users indicated by the counter

NOTE
1.
----End
Example
//Allocating code resources to E-AGCHs and E-RGCHs
MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=5;
//Stopping reserving uplink and downlink credit resources and setting the
maximum number of HSUPA users to 96
MOD UCELLCAC: CellId=111, MaxHsupaUserNum=96, UlHoCeResvSf=SFOFF,
DlHoCeCodeResvSf=SFOFF;
Issue 06 (2013-03-25)

570
RAN14.0
170
Configuring 128 HSDPA Users per

Cell
Prerequisites
l
The feature is only available for 3900 series NodeB, 3900 series NodeB (except
BTS3902E) requires WBBPd2/WBBPd3 board which is one type of WBBPd or
WBBPf.

WRFD-010653 96 HSDPA Users per Cell and WRFD-010670 128 HSUPA Users per
Cell.
License
Context
This feature can increase the capacity of voice services in a cell, especially in cells with VoIP
users or a large number of low-rate users.
This feature enables an HSDPA cell to serve a maximum of 128 users performing VoIP or other
low-rate services. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
l
1.
Issue 06 (2013-03-25)
and set the maximum number of HSDPA users per cell to 128.
571
RAN14.0
1.

2.
download files through FTP.
3.
Check the maximum number of users through the counter

VS.HSDPA.UE.Max.Cell on the M2000.
NOTE
The 128 HSDPA users referred to in this feature are of the SRB Over HSPA type.
1.
----End
Example
/*Activating 128 HSDPA Users per Cell*/
//Stop reserving uplink and downlink credit resources and setting the
maximum number of HSDPA users to 128
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=128, UlHoCeResvSf=SFOFF,
Issue 06 (2013-03-25)

572
RAN14.0
171

Cell
Prerequisites
l
The feature is only available for 3900 series NodeB, 3900 series NodeB (except
BTS3902E) requires WBBPd2/WBBPd3 board which is one type of WBBPd or
WBBPf.

WRFD-010639 96 HSUPA Users per Cell and WRFD-010654 128 HSDPA Users per
Cell.
License
Context
This feature can increase the capacity of voice services in a cell with a large number of low-rate
users, such as VoIP users.
This feature enables an HSUPA cell to serve a maximum of 128 users performing VoIP or other
low-rate services. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
l
1.
Issue 06 (2013-03-25)

UMTS Cell Parameters in Batches) to allocate code resources to E-AGCHs and ERGCHs.
573
RAN14.0
2.
and set the maximum number of HSUPA users to 128.
1.

2.
upload files through FTP.
3.
Check the maximum number of users indicated by the counter

NOTE
1.
----End
Example
/*Activating 128 HSUPA Users per Cell*/
//Allocate code resources to E-AGCHs and E-RGCHs
MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=7;
//Stop reserving uplink and downlink credit resources and setting the
maximum number of HSUPA users to 128
MOD UCELLCAC: CellId=111, MaxHsupaUserNum=128, UlHoCeResvSf=SFOFF,
Issue 06 (2013-03-25)

574
RAN14.0
172
Configuring Flexible HSPA+

Flexible HSPA+ Technology Selection.
Prerequisites
l
EBOI, and EDLP boards. In addition, the uplink service cannot be established on the
HBBI or HULP board.
In DBS3800, the BBU3806 must be configured with the EBBC or EBBCd board.
The 3900 series base stations must be configured with the WBBPb, WBBPd or WBBPf
board.
BTS RF modules support only one transmission channel. MIMO requires
interconnection of two RF modules.

WRFD-010696 DC-HSDPA and RFD-010684 22 MIMO.
License
Other Prerequisites
In 22 MIMO mode, two RF units must be interconnected.
The UE has the HSDPA Category21 or higher capability, including HSDPA category
21, 22, 23, 24, 25, 26, 27, and 28.
Context
DC-HSDPA and MIMO can achieve gains under different conditions. DC-HSDPA ensures a
comparatively high throughput for the UEs when few HSDPA-capable UEs camp on a cell that
has a light load. MIMO ensures a comparatively high throughput for the UEs when a large
number of HSDPA-capable UEs camp on an overloaded cell.
Issue 06 (2013-03-25)

575
RAN14.0
When one or two carriers in DC-HSDPA networking support MIMO, Flexible HSPA+
Technology Selection dynamically selects DC-HSDPA or MIMO for newly accessing UEs,
based on the current number of HSDPA-capable UEs and downlink load of the carriers that
support MIMO. This ensures an optimum service bearing mode.
Procedure
l
Issue 06 (2013-03-25)
1.
Turn on the DC/MIMO dynamic selection algorithm switch. Run the BSC6900 MML
modification center: 3.15 Modifying RNC Parameters in Batches) with
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH selected in the Channel
Configuration Strategy Switch drop-down list.
2.
Turn off the RNC-oriented DC+MIMO algorithm switch. Run the BSC6900 MML
CFG_HSDPA_DCMIMO_SWITCH deselected in the Channel Configuration
Strategy Switch drop-down list.
3.
Optional: Turn on the HSDPA algorithm switch for streaming services if HSDPA is
required for streaming services. Run the BSC6900 MML command SET
Modifying RNC Parameters in Batches) with
MAP_PS_STREAM_ON_HSDPA_SWITCH selected in the Service Mapping
Strategy Switch drop-down list.
4.
Set HSDPA thresholds for downlink streaming services and HSDPA thresholds for
downlink BE services. Run the BSC6900 MML command SET
UFRCCHLTYPEPARA (CME single configuration: UMTS Radio Global
Channel Type Parameters; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) with DL streaming traffic threshold on HSDPA and DL
BE traffic threshold on HSDPA set to appropriate values based on network planning.
1.
Set the TX power threshold and HSDPA user number threshold of the secondary cell
for the DC/MIMO dynamic selection algorithm. Run the BSC6900 MML command
SET UFRC with DL TX Power Threshold of Secondary Cell and Threshold of
HSDPA Users in Secondary Cell set to appropriate values.
2.
Have a UE access the secondary cell and initiate an HSDPA service.
3.
Query the DL power load of the secondary cell covered by the DC carrier group. On
the BSC6900 LMT, choose Monitor > Monitor > UMTS Monitoring > Cell
Performance Monitoring and select Cell DL Carrier TX Power in the Monitor
Item: drop-down list.
4.
Check whether the value of the IE dl-TransportChannelType in the rb-MappingInfo

of the RRC_RB_SETUP message is hsdsch.
Expected result: As shown in Figure 172-2, the RRC_RB_SETUP message in the
Uu tracing result contains the mimoParameters IE when the downlink power of the
576
RAN14.0
secondary cell covered by the DC carrier group is greater than or equal to DL TX

Power Threshold of Secondary Cell set in Step 1 and the number of HSDPA users
is greater than or equal to Threshold of HSDPA Users in Secondary Cell set in Step
1. The RRC_RB_SETUP message in the Uu tracing result contains the dlSecondaryCellInfoFDD IE when the downlink power of the secondary cell covered
by the DC carrier group is smaller than DL TX Power Threshold of Secondary
Cell set in Step 1 and the number of HSDPA users is smaller than Threshold of
HSDPA Users in Secondary Cell set in Step 1.
Figure 172-1 mimoParameters message
Figure 172-2 dl-SecondaryCellInfoFDD IE
1.
Turn off the DC/MIMO dynamic selection algorithm switch. Run the BSC6900 MML
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH deselected in the Channel
Configuration Strategy Switch drop-down list.
----End
Example
//Turning on the DC/MIMO dynamic selection algorithm switch
SET UCORRMALGOSWITCH: CfgSwitch=CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH-1;
//Turning off the RNC-oriented DC+MIMO algorithm switch
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DCMIMO_SWITCH-0;
//(Optional) Enabling the HSDPA algorithm switch for streaming services
if HSDPA is required for streaming services
Issue 06 (2013-03-25)

577
RAN14.0
//Setting the HSDPA threshold for downlink streaming services and HSDPA
threshold for downlink BE services
SET UFRC: SecCellTcpThd=10, SecCellHUserNumThd=1;
SET UCORRMALGOSWITCH: CfgSwitch=CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH-0;
Issue 06 (2013-03-25)

578
RAN14.0
173 Configuring Traffic-Based Activation and Deactivation

of the Supplementary Carrier In Multi-carrier
173
Configuring Traffic-Based
Activation and Deactivation of the

Supplementary Carrier In Multi-carrier
Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier.
Prerequisites
l

WRFD-010696 DC-HSDPA
License
Other Prerequisites
The UE must be of HS-DSCH category 21, 22, 23, 24 to support DC-HSDPA or HSDSCH category 25, 26, 27, 28 to support DC-HSDPA+MIMO.
Context
For a user that uses DC-HSDPA/DC-HSDPA+MIMO in the downlink and DCH/SC-HSUPA
in the uplink, the feature has the following functions:
l
Disables the downlink secondary carrier function when the downlink traffic is light but the
buffer has been occupied by a large amount of data. In this case, the user becomes a singlecarrier user.
Re-activate the downlink secondary carrier function when the buffer can accommodate a
large amount of data and throughput is high. In this case, the user becomes a dual-carrier
user.
Issue 06 (2013-03-25)

579
RAN14.0
173 Configuring Traffic-Based Activation and Deactivation

of the Supplementary Carrier In Multi-carrier
Procedure
l
1.
3.17 Modifying Physical NodeB Parameters in Batches) to set the Mac-hs
scheduling parameters with the DC HSDPA Cell Act Deact Switch set to ON
(ON).
NOTE
If the Mac-hs scheduling parameters of two DC-HSDPA cells must be set, set DC HSDPA
Cell Act Deact Switch to ON(ON) for each cell.
1.
Run the NodeB MML command LST MACHSPARA to query the Mac-hs scheduling
parameters. Check whether the Secondary DC HSDPA Cell Act Deact Switch is
turned on.
2.

clear DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH, and
DRA_PS_BE_STATE_TRANS_SWITCH from the Dynamic Resource
Allocation Switch list.
3.
Use a DC-HSDPA UE to perform PS services in a DC-HSDPA cell. Do not upload

or download data after required connections are established. Five seconds later, the
UE becomes an SC UE, which indicates that the feature has been activated.
1.
3.17 Modifying Physical NodeB Parameters in Batches) to set the Mac-hs
scheduling parameters with the Secondary DC HSDPA Cell Act Deact Switch set
to OFF(OFF).
----End
Example
SET MACHSPARA: LOCELL=1, SECCELLACTDEASW=ON;
SET MACHSPARA: LOCELL=2, SECCELLACTDEASW=ON;
DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0&D
RA_PS_BE_STATE_TRANS_SWITCH-0;
SET MACHSPARA: LOCELL=1, SECCELLACTDEASW=OFF;
SET MACHSPARA: LOCELL=2, SECCELLACTDEASW=OFF;
Issue 06 (2013-03-25)

580
RAN14.0
174
Configuring Enhanced DRX
Enhanced DRX. (This feature cannot be configured using the CME. )
Prerequisites
l
NodeB:
The BTS3812E, BTS3812A, or BTS3812AE is configured with the EULPd, EBBI,
EBOI, or EULP board.

Configurations of other features, on which this feature depends, are complete. This
feature depends on the feature WRFD-010688 Enhanced CELL_FACH.
License
Other Prerequisites
The UE must be of 3GPP Release-8 or later and support Enhanced DRX.
HSPA+ Downlink 42Mbit/s per User
Context
The enhanced discontinuous reception (DRX) feature enables UEs in the enhanced downlink
for CELL_FACH state to receive the HS-SCCH discontinuously. After this feature is enabled,
the RAN and UEs in the enhanced downlink for CELL_FACH state transmit and receive data
at a specified time. The UE detects the HS-SCCH at regular intervals instead of detecting the
HS-SCCH continuously. When there is no data to transmit, the UE shuts down the receiver. As
a result, the power consumption of the UE decreases.
Procedure
l
Issue 06 (2013-03-25)
581
RAN14.0
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to select

E_DRX(Enhanced Discontinous Reception Function Switch) for Cell Hspa Plus
function switch.
2.
Run the BSC6900 MML command DSP UCELL to check whether enhanced
downlink for CELL_FACH is activated. If the enhanced downlink for CELL_FACH
is already activated, run the BSC6900 MML command DEA UCELLEFACH to
deactivate enhanced downlink for CELL_FACH. If enhanced downlink for
CELL_FACH is not activated, go to Step 3.
NOTE
The BSC6900 MML command ADD UCELLEDRX fails to be executed in an active cell enabled
with enhanced downlink for CELL_FACH. Therefore, you need to deactivate enhanced downlink
for CELL_FACH before configuring the related parameters.
3.
Run the BSC6900 MML command ADD UCELLEDRX to set parameters related to
enhanced DRX based on network planning requirements.
4.
Run the BSC6900 MML command ACT UCELLEFACH to activate this feature.
1.
Start Uu Interface Trace on the LMT to trace messages on the Uu interface.
2.
If the UE is not enabled with enhanced uplink for CELL_FACH, the information
element DRX Interruption by HS-DSCH data in the system information message
SIB5/5bis should be set to TRUE, as shown in Figure 174-1. If the UE is enabled
with enhanced uplink for CELL_FACH, the information element Common E-DCH
system info is carried in the system information message SIB5/5bis.
Figure 174-1 Information element in the system information message of enhanced
DRX
Issue 06 (2013-03-25)
3.
Start Cell Trace on the LMT to trace messages of a cell.
4.
When the UE is in the enhanced downlink for CELL_FACH state, the RNC carries
the E-DRX indication in the HS-DSCH DATA FRAME type2 to the NodeB on the
DCCH or DTCH. If enhanced DRX is enabled, you can view that the E-DRX bit is
1 in Cell Trace, as shown in Figure 174-2. If enhanced DRX is not enabled, the EDRX bit is 0.

582
RAN14.0
Figure 174-2 Indication sent from the RNC to the NodeB on the DCCH or DTCH
5.
If the UE is enabled with enhanced uplink for CELL_FACH, the HS-DSCH DATA
FRAME type2 carries New IE Flag, H-RNTI, and E-RNTI, which can be viewed in
Cell Trace, as shown in Figure 174-3.
Figure 174-3 HS-DSCH DATA FRAME type2
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to deselect

E_DRX(Enhanced Discontinous Reception Function Switch) for Cell Hspa Plus
function switch.
----End
Example
//Activating enhanced DRX
MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_DRX-1;
DEA UCELLEFACH: CellId=11;
ADD UCELLEDRX: CellId=11, EDRXT321=EDRXT321_100, EDRXCycle=EDRXCYCLE_8,
EDRXBurst=EDRXBURST_1, EDRXInterruptbyHSDSCHData=INTERRUPTION_CFG;
ACT UCELLEFACH: CellId=11;
//Deactivating enhanced DRX
MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_DRX-0;
Issue 06 (2013-03-25)

583
RAN14.0
175
Configuring Enhanced Fast

Dormancy
Enhanced Fast Dormancy. (This feature cannot be configured using the CME. )
Prerequisites
l

License
NOTE

Run the BSC6900 MML command SET LICENSE to set Fast Dormancy Enhancement-per PS
Active User to an appropriate value.
Other Prerequisites
It is good practice to maintain load balancing among all frequencies in the network when
using this feature, if the network is a service-layered network as follows and
RSVDBIT1_BIT29 of the Reserved parameter 1 in the SET URRCTRLSWITCH
command is set to 0, in order to reduce the call drops for UEs in the CELL_FACH state
that support fast dormancy, Wait RB reconfiguration response timer and RL restoration
timer in the SET USTATETIMER command need to be set to 11000 and 15000
respectively.
Frequency F1 carries R99 services.
Frequency F2 carries HSPA services.
F2 does not allow UEs in the idle, CELL_FACH, or CELL_PCH state to camp on.
Context
As the number of smartphones keeps increasing in mobile networks, the networks face signaling
storms produced by these UEs. With rich experience in network optimization, Huawei provides
Issue 06 (2013-03-25)

584
RAN14.0
a comprehensive end-to-end solution to respond to network challenges based on network

characteristics.
This feature is a component of the comprehensive solution. Deploying this feature only cannot
solve the signaling storm problem produced by smartphones. Operators should use this feature
together with professional services to optimize the quality of service of the entire network.
CAUTION
l Consult Huawei engineers about the comprehensive solution to obtain professional technical
support.
l Huawei engineers will recommend appropriate parameter settings for this feature based on
the network conditions.
l Do not configure the parameters related to this feature without Huawei professional technical
support. Inappropriate parameter settings may lead to network failures.
Always on line can be provided for PS services of intelligent UEs to improve user experience.
Always on line, however, will increase the power consumption of intelligent UEs. To prolong
UE battery life, the Fast Dormancy feature is introduced. When there is no PS data transfer, the
UE will send a signaling connection release indication (SCRI) message to request the
BSC6900 to release the RRC connection and move the UE state to IDLE mode, CELL_PCH,
or URA_PCH.
If this feature is not enabled, the BSC6900 will move the UE state to IDLE mode after the
BSC6900 receives an SCRI message from the UE or the UE inactivity timer expires. If UEs are
frequently switched between RRC connected states and IDLE mode, signaling storms occur.
If this feature is enabled, the BSC6900 will move the UE to the CELL_PCH or URA_PCH state
instead of the IDLE mode under either of the following conditions, reducing signaling processing
costs:
l
The BSC6900 receives an SCRI message from the UE.
The CELL_FACH/CELL_DCH inactivity timer on the BSC6900 expires.
Activation Procedure (The UE supporting fast dormancy is a Pre-Release 8 UE)
Procedure
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the feature
Enhanced Fast Dormancy at the BSC6900-level. In this step, select the
FAST_DORMANCY_SWITCH under PROCESSSWITCH.
2.
Run the BSC6900 MML commandSET URRCTRLSWITCH to select the

RNC_PS_QUERY_UE_IMEI_SWITCH under PROCESSSWITCH2.
3.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable cell update
during CS service setup. In this step, clear the RSVDBIT1_BIT21 check box under
Reserved Parameter 1.

585
RAN14.0

NOTE
After this feature is enabled, the number of CELL_DCH-to-CELL_FACH (D2F) procedures

performed increases.Set this parameter when a UE in the CELL_FACH state sets up a CS
service associated with cell reselection. The switch RSVDBIT1_BIT21 specifies whether to
allow cell update during CS service setup. When the switch is turned on, for UEs that are
establishing AMR services and shifting from the CELL_FACH state to the CELL_DCH state,
the RNC stops establishing AMR services to handle cell update if the RNC receives from the
UEs a cell update message containing the cause value "cell reselection."
4.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the state
transition from CELL_PCH or URA_PCH to CELL_DCH triggered by FACH
congestion. In this step, clear the RSVDBIT1_BIT20 check box under Reserved
Parameter 1.
NOTE
After this feature is enabled, the FACH will carry a large amount of data, which may lead to
FACH congestion. Therefore, it is recommended that a new SCCPCH be added.
For details about how to handle FACH congestion in other methods, see section "FACH
Congestion Control" in the Flow Control in the RAN Feature Documentation.
5.
Run the BSC6900 MML command SET UPSINACTTIMER to set the value of the
CELL_DCH, CELL_FACH, and CELL_PCH inactivity timer respectively.
The recommended value of the FAST DORMANCY USER T1 in
CELL_DCH is 5 seconds.
CELL_FACH is 5 seconds.
CELL_PCH is 1800 seconds.
NOTE
This document provide the recommended value of the FAST DORMANCY USER T1 in
CELL_DCH, the FAST DORMANCY USER T1 in CELL_FACH, and the FAST
DORMANCY USER T1 in CELL_PCH.
6.
Run the BSC6900 MML command SET UUESTATETRANS. In this step, set Fast
Dormancy User FACH/E_FACH2DCH/HSPA 4A Threshold to D1024.
7.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the Type
Allocation Code (TAC) match function. In this step, select the
FD_TAC_MATCH_SWITCH under PROCESSSWITCH.
8.
Run the BSC6900 MML commandADD UIMEITAC to set the value of the TAC to
add the IMEI TACs of smartphones to the whitelist, set the The function of the
TAC to Fast_Dormancy, and set the Fast Dormancy Switch to ON.
9.
Run the BSC6900 MML command ADD TRMFACTOR and MOD ADJMAP to
change the Iu-PS activity factor. The recommended value of the Iu-PS activity factor
is 10%. If the configured Iu-PS activity factor is smaller than 10%, retain the
configured value.
NOTE
After this feature is enabled, the number of UEs in the CELL_PCH or URA_PCH state increases
sharply. UEs in the CELL_PCH or URA_PCH state consume a large number of Iu-PS
bandwidth resources although they do not transmit any data.
Issue 06 (2013-03-25)

586
RAN14.0
CAUTION
The Iu-PS activity factor of all services must be set to an appropriate value. Otherwise,
a large number of PS service setups fail, and the CPU usage of the SPU boards
increases sharply.
l
Activation Procedure (The UE supporting fast dormancy is a Release 8 or later Release

UE)
1.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the feature
Enhanced Fast Dormancy at the BSC6900-level. In this step, select the
FAST_DORMANCY_SWITCH under PROCESSSWITCH.
2.
Run the BSC6900 MML command SET UCONNMODETIMER to set the value of
the Timer 323.
NOTE
If the UE supporting fast dormancy is a Release 8 or later Release UE, you need to set timer
323 after enabling fast dormancy. When the network supports the CELL_PCH or
URA_PCH, it is good practice to set timer 323 to 120s. When the network does not support
CELL_PCH or URA_PCH, it is good practice to set timer 323 to 10s.
3.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable cell update
during CS service setup. In this step, clear the RSVDBIT1_BIT21 check box under
Reserved Parameter 1.
NOTE
After this feature is enabled, the number of CELL_DCH-to-CELL_FACH (D2F) procedures

performed increases. Set this parameter when a UE in the CELL_FACH state sets up a CS
service associated with cell reselection. The switch RSVDBIT1_BIT21 specifies whether to
allow cell update during CS service setup. When the switch is turned on, for UEs that are
establishing AMR services and shifting from the CELL_FACH state to the CELL_DCH state,
the RNC stops establishing AMR services to handle cell update if the RNC receives from the
UEs a cell update message containing the cause value "cell reselection."
4.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the state
transition from CELL_PCH or URA_PCH to CELL_DCH triggered by FACH
congestion. In this step, clear the RSVDBIT1_BIT20 check box under Reserved
Parameter 1.
NOTE
After this feature is enabled, the FACH will carry a large amount of data, which may lead to
FACH congestion. Therefore, it is recommended that a new SCCPCH be added.
For details about how to handle FACH congestion in other methods, see section "FACH
Congestion Control" in the Flow Control in the RAN Feature Documentation.
5.
Run the BSC6900 MML command SET UPSINACTTIMER to set the value of the
CELL_DCH, CELL_FACH, and CELL_PCH inactivity timer respectively.
CELL_DCH is 5 seconds.
CELL_FACH is 5 seconds.
CELL_PCH is 1800 seconds.
Issue 06 (2013-03-25)

587
RAN14.0

NOTE
This document provide the recommended value of the FAST DORMANCY USER T1 in
CELL_DCH, the FAST DORMANCY USER T1 in CELL_FACH, and the FAST
DORMANCY USER T1 in CELL_PCH.
6.
Run the BSC6900 MML command SET UUESTATETRANS. In this step, set Fast
Dormancy User FACH/E_FACH2DCH/HSPA 4A Threshold to D1024.
7.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the Type
Allocation Code (TAC) match function. In this step, select the
FD_TAC_MATCH_SWITCH under PROCESSSWITCH.
8.
Optional: To enable this feature only for UEs of Release 8 or later versions on the
live network, Run the BSC6900 MML commandRMV UIMEITAC to remove the
TAC values for these UEs.
9.
Run the BSC6900 MML command ADD TRMFACTOR and MOD ADJMAP to
change the Iu-PS activity factor. The recommended value of the Iu-PS activity factor
is 10%. If the configured Iu-PS activity factor is smaller than 10%, retain the
configured value.
NOTE
After this feature is enabled, the number of UEs in the CELL_PCH or URA_PCH state increases
sharply. UEs in the CELL_PCH or URA_PCH state consume a large number of Iu-PS
bandwidth resources although they do not transmit any data.
CAUTION
The Iu-PS activity factor of all services must be set to an appropriate value. Otherwise,
a large number of PS service setups fail, and the CPU usage of the SPU boards
increases sharply.
l
1.
Run the BSC6900 MML command DSP LICUSAGE to query the state of the license
for this feature. If the result shown in Figure 175-1 is returned, the license for this
feature has been configured.
Figure 175-1 Status of the Enhanced Fast Dormancy license
2.
Initiate Uu interface message tracing on the BSC6900 LMT.
3.
Use a smartphone whose IMEI TAC has been added into whitelist to set up a PS service
in the CELL_DCH state. For example, use the smartphone to browse a Web page.
If the RRC_RB_SETUP message shown in Figure 175-2 is traced, the UE is in the
CELL_DCH state.
Issue 06 (2013-03-25)

588
RAN14.0
Figure 175-2 UE in the CELL_DCH state
4.
Keep the UE in IDLE mode for 10 seconds and perform no operation after a Web page
is opened.
If the RRC_RB_RECFG message shown in Figure 175-3 is traced, the UE will move
from the CELL_DCH state to the CELL_FACH state and then to the CELL_PCH
state.
Figure 175-3 State transition to the CELL_PCH state
5.
Use the UE to continue PS services such as web page browsing. Cell update or channel
reconfiguration occurs.
Check the RRC_CELL_UPDATE message as shown in Figure 175-4 and Figure
175-5.
Figure 175-4 Cell update
Figure 175-5 Channel reconfiguration
l
Issue 06 (2013-03-25)
589
RAN14.0
To deactivate this feature for all UEs on the live network, Run the BSC6900 MML
commandSET URRCTRLSWITCH. In this step, clear
FAST_DORMANCY_SWITCH under Process switch parameter to turn off the
BSC6900-level switch for enhanced fast dormancy.
To deactivate this feature only for UEs of versions earlier than Release 8 on the live
network, Run the BSC6900 MML commandRMV UIMEITAC to remove the TAC
values for these UEs.
To deactivate this feature only for UEs of Release 8 or later versions on the live network,
Run the BSC6900 MML commandSET UCONNMODETIMER. In this step, set
Timer 323 to INVALID.
NOTE
If this feature must be deactivated when the SPUa or SPUb board is being reset, do as follows:
1. Run the BSC6900 MML command SET CFGDATAINEFFECTIVE to set the subrack to ineffective
mode.
2. Run the MML commands to deactivate this feature. For details, see the script in the example.
3. Run the BSC6900 MML command SET CFGDATAEFFECTIVE to set the subrack to effective
mode.
----End
Example
//Activating Fast Dormancy Enhancement (The UE supporting fast dormancy
is a Pre-Release 8 UE)
//Enabling the Enhanced Fast Dormancy feature at the BSC6900 level
SET URRCTRLSWITCH: PROCESSSWITCH=FAST_DORMANCY_SWITCH-1;
//Set the PS IMEI Request Switch
SET URRCTRLSWITCH: PROCESSSWITCH2=RNC_PS_QUERY_UE_IMEI_SWITCH-1;
//Enabling cell update during CS service setup
//Enabling the state transition from CELL_PCH or URA_PCH to CELL_DCH
triggered by FACH congestion
//Setting the value of the CELL_DCH inactivity timer to 5 seconds
SET UPSINACTTIMER: PsInactTmrForFstDrmDch=5;
//Setting the value of the CELL_FACH inactivity timer to 5 seconds
SET UPSINACTTIMER: PsInactTmrForFstDrmFach=5;
//Setting the value of the CELL_PCH inactivity timer to 1800 seconds
SET UPSINACTTIMER: PsInactTmrForPreFstDrm=1800;
//Setting the traffic threshold of event 4A during the state transition
from CELL_FACH to CELL_DCH to D1024
SET UUESTATETRANS: FastDormancyF2DHTvmThd=D1024;
//Enabling the IMEI Type Allocation Code (TAC) match function
SET URRCTRLSWITCH: PROCESSSWITCH=FD_TAC_MATCH_SWITCH-1;
//Adding the IMEI TACs of smartphones to the whitelist
ADD UIMEITAC: TAC_FUNC=Fast_Dormancy, TAC=01177600, Description="Smart
Issue 06 (2013-03-25)

590
RAN14.0
Phone", FastDormancy=ON;
//Changing the Iu-PS activity factor
ADD TRMFACTOR: REMARK="Smart Phone", CSCONVDL=10, CSCONVUL=10,
CSSTRMDL=10, CSSTRMUL=10, PSCONVDL=10, PSCONVUL=10, PSSTRMDL=10,
PSSTRMUL=10, PSINTERDL=10, PSINTERUL=10, PSBKGDL=10, PSBKGUL=10,
HDVOICEDL=10, HDCONVDL=10, HDSTRMDL=10, HDINTERDL=10, HDBKGDL=10,
HUVOICEUL=10, HUCONVUL=10, HUSTRMUL=10, HUINTERUL=10, HUBKGUL=10;
//Activating Enhanced Fast Dormancy (The UE supporting fast dormancy is a

Release 8 or later Release UE)
//Enabling the Enhanced Fast Dormancy feature at the BSC6900 level
//Set the Timer 323
//Enabling cell update during CS service setup
//Enabling the state transition from CELL_PCH or URA_PCH to CELL_DCH
triggered by FACH congestion
//Setting the value of the CELL_DCH inactivity timer to 5 seconds
SET UPSINACTTIMER: PsInactTmrForFstDrmDch=5;
//Setting the value of the CELL_FACH inactivity timer to 5 seconds
SET UPSINACTTIMER: PsInactTmrForFstDrmFach=5;
//Setting the value of the CELL_PCH inactivity timer to 1800 seconds
SET UPSINACTTIMER: PsInactTmrForPreFstDrm=1800;
//Setting the traffic threshold of event 4A during the state transition
from CELL_FACH to CELL_DCH to D1024
SET UUESTATETRANS: FastDormancyF2DHTvmThd=D1024;
//Enabling the IMEI Type Allocation Code (TAC) match function
SET URRCTRLSWITCH: PROCESSSWITCH=FD_TAC_MATCH_SWITCH-1;
//Deleting the IMEI TACs of smartphones from the whitelist
RMV UIMEITAC: TAC_FUNC=Fast_Dormancy, TAC=01177600;
//Changing the Iu-PS activity factor
ADD TRMFACTOR: REMARK="Smart Phone", CSCONVDL=10, CSCONVUL=10,
CSSTRMDL=10, CSSTRMUL=10, PSCONVDL=10, PSCONVUL=10, PSSTRMDL=10,
PSSTRMUL=10, PSINTERDL=10, PSINTERUL=10, PSBKGDL=10, PSBKGUL=10,
HDVOICEDL=10, HDCONVDL=10, HDSTRMDL=10, HDINTERDL=10, HDBKGDL=10,
HUVOICEUL=10, HUCONVUL=10, HUSTRMUL=10, HUINTERUL=10, HUBKGUL=10;
//Deactivating Fast Dormancy Enhancement
//Deactivating Enhanced Fast Dormancy for all UEs on the
live network
//Deactivating Enhanced Fast Dormancy only for UEs of versions earlier
than Release 8
Issue 06 (2013-03-25)

591
RAN14.0
RMV UIMEITAC: TAC_FUNC=Fast_Dormancy, TAC=01177600;

//Deactivating Enhanced Fast Dormancy only for UEs of Release 8 or later
versions
SET UCONNMODETIMER: T323=INVALID;
Issue 06 (2013-03-25)

592
RAN14.0
176 Configuring Voice Service Experience Improvement for

Weak Reception UEs
176
Configuring Voice Service
Experience Improvement for Weak Reception

UEs
Voice Service Experience Improvement for Weak Reception UEs.
Prerequisites
l

License
Context
This feature enables the radio network controller (RNC) to identify weak reception UEs based
on the International Mobile Station Equipment Identity (IMEI) and to configure dedicated power
control and handover parameters for them. Based on the parameter settings, weak reception UEs
obtain a high downlink power control threshold in weak coverage areas and perform handovers
at the designated threshold. This prevents frequent compressed mode measurement and call
drops caused by signal quality fluctuations and improves user experience of CS voice services.
l
Precautions
None
Issue 06 (2013-03-25)
Data Preparation

593
RAN14.0

Weak Reception UEs
Parameter Name
Parameter ID
Setting
Description
Source
Process Control
Switch 2
PROCESSSWITC
H2
l If the core
network (CN)
has not enabled
the ID
REQUEST
function, select
the
RNC_CS_QU
ERY_UE_IME
I_SWITCH
check box on the
RNC side.
Network plan
l If the CN has
enabled the ID
REQUEST
function and the
query type is
IMEI, clear the
RNC_CS_QU
ERY_UE_IME
I_SWITCH
check box on the
RNC side.
l If the
RNC_CS_QU
ERY_UE_IME
I_SWITCH
check box is
selected on the
RNC side, be
sure to select the
SEND_MSG_
NULL_SWIT
CH check box
under Process
Control Switch
4 when the CN
verifies the
serial numbers
of direct transfer
messages.
The function of the
TAC
Issue 06 (2013-03-25)
TAC_FUNC
Set this parameter

to
Special_User_Enhance.

Network plan
594
RAN14.0
Issue 06 (2013-03-25)

Weak Reception UEs
Parameter Name
Parameter ID
Setting
Description
Source
Special User
Function Switch
SpecUserFunctionSwitch
SPECUSER_AM
R_HOENHANCE
_SWITCH and
SPECUSER_AM
R_PWRENHANC
E_SWITCH
should be selected.
Network plan
DL Pwr Cong Thres

for Spec User
Enhance
SpecUserPwrEnDlPwrTrigTh
d
Use the
recommended
value.
Network plan
CN domain ID
CNDomainId
Set this parameter

to CS_DOMAIN.
Network plan
Max bit rate of

service
MaxBitRate
Use the
recommended
value.
Network plan
RL Max DL TX
power
RlMaxDlPwr
Use the
recommended
value.
Network plan
Max DL RL Power
For Spec User
SpecUserRlMaxDlPwr
Use the
recommended
value.
Network plan
Delay in Reporting
2D for Special UEs
SpecUserHystFor2
D
The parameter is
RNC level, use the
recommended
value.
Network plan
Ec/N0 Threshold
for Reporting 2D
SpecUserCSThd2D
EcN0
The parameter is
RNC level, use the
recommended
value.
Network plan
Ec/N0 Threshold
for Reporting 2F
SpecUserCSThd2F
EcN0
The parameter is
RNC level, use the
recommended
value.
Network plan
RSCP Threshold
for Reporting 2D
SpecUserCSThd2D
RSCP
The parameter is
RNC level, use the
recommended
value.
Network plan
Delay in Reporting
2D for Special UEs
SpecUserHystFor2
D
The parameter is
cell level, use the
recommended
value.
Network plan

595
RAN14.0

Weak Reception UEs
Parameter Name
Parameter ID
Setting
Description
Source
Ec/N0 Threshold
for Reporting 2D
SpecUserCSThd2D
EcN0
The parameter is
cell level, use the
recommended
value.
Network plan
Ec/N0 Threshold
for Reporting 2F
SpecUserCSThd2F
EcN0
The parameter is
cell level, use the
recommended
value.
Network plan
RSCP Threshold
for Reporting 2D
SpecUserCSThd2D
RSCP
The parameter is
cell level, use the
recommended
value.
Network plan
RSCP Threshold
for Reporting 2F
SpecUserCSThd2F
RSCP
The parameter is
cell level, use the
recommended
value.
Network plan
Procedure
l
1.
Optional: Enable the CS international mobile equipment identity (IMEI) acquisition

function on the BSC6900.
a.

RNC_CS_QUERY_UE_IMEI_SWITCH check box under Process Control
Switch 2.
NOTE
l If CS IMEI acquisition has been enabled on the CN, skip this step.
l Before enabling CS IMEI acquisition, ensure that the CN checks the serial number of direct
transfer messages. Run the BSC6900 MML command SET URRCTRLSWITCH (CME single
Configuration > Process Switch; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches). In this step, turn on the SEND_MSG_NULL_SWITCH switch.
l After enabling CS IMEI acquisition, check for the compatibility issue between the BSC6900
and the CN. When there is a compatibility issue, enabling CS IMEI acquisition results in CS
service setup failures.
2.
Enable differentiated power control and differentiated handover for smartphones, and
configure the Type Allocation Code (TAC) of the smartphone.
a.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD UIMEITAC (CME single

Configuration > IMEI TAC; CME batch modification center: not supported).
In this step, set The function of the TAC to Special_User_Enhance, and select
the SPECUSER_AMR_HOENHANCE_SWITCH and
596
RAN14.0

Weak Reception UEs
SPECUSER_AMR_PWRENHANCE_SWITCH check boxes under Special

User Function Switch.
3.
Set the parameters related to differentiated power control and handover for
smartphones based on the network plan.
a.
Run the BSC6900 MML command ADD UCELLLDM (CME single

Modifying UMTS Cell Parameters in Batches) to set the parameters related
to cell load monitoring. In this step, set DL Pwr Cong Thres for Spec User
Enhance to an appropriate value based on the network plan.
b.
Run the BSC6900 MML command MOD UCELLRLPWR (CME single

Radio Link Power Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to set the parameters related
to the radio link (RL) transmit power in the cell. In this step, set CN domain
ID to CS_DOMAIN, and set Max bit rate of service, RL Max DL TX
power, and Max DL RL Power For Spec User to appropriate values based on
the network plan.
c.
Run the BSC6900 MML command SET UHOCOMM (CME single

Parameter Configuration > RNC Oriented Handover Algorithm Common
Parameters in Batches) to set the RNC-level parameters related to differentiated
handover for smartphones. In this step, set Delay in Reporting 2D for Special
UEs, Ec/N0 Threshold for Reporting 2D, Ec/N0 Threshold for Reporting
2F, RSCP Threshold for Reporting 2D, and RSCP Threshold for Reporting
2F to appropriate values based on the network plan.
d.
Optional: Run the BSC6900 MML command ADD UCELLHOCOMM (CME

> Cell Oriented Handover Common Algorithm Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) to
set the cell-level parameters related to differentiated handover for smartphones.
In this step, set Delay in Reporting 2D for Special UEs, Ec/N0 Threshold for
Reporting 2D, Ec/N0 Threshold for Reporting 2F, RSCP Threshold for
Reporting 2D, and RSCP Threshold for Reporting 2F to appropriate values
based on the network plan.
NOTE
To enable this feature in a specified cell, run the ADD UCELLHOCOMM (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented
Handover Common Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) command to set the differentiated handover
parameters for the cell.
Verifying inter-RAT handovers of a special UE based on parameters
Issue 06 (2013-03-25)
1.
Choose a special UE whose IMEI TAC is configured on the BSC6900 to start UE

tracing on the BSC6900 LMT. Obtain the IMEI of the UE.
2.
Use the UE to set up a CS call in a cell enabled with this feature.
3.
Check the traced UE signaling messages:

597
RAN14.0

Weak Reception UEs
Check the value of usedFreqThreshold under the IE event2d contained in the

RRC_MEAS_CTRLd message. If the value of usedFreqThreshold is the same as the
value of RSCP Threshold for Reporting 2D in the MML command SET
UHOCOMM, this feature has been activated.
Check the value of usedFreqThreshold under the IE event2f contained in the
RRC_MEAS_CTRL message. If the value of usedFreqThreshold is the same as the
value of RSCP Threshold for Reporting 2F in the MML command SET
UHOCOMM, this feature has been activated.
Figure 176-1 usedFreqThreshold IE diagram
Verifying power enhancement for the special UE

1.
Choose a special UE whose IMEI TAC is configured on the BSC6900 to start Iub
tracing on the BSC6900 LMT. Obtain the IMEI of the UE.
2.
Use the UE to set up a CS call in a cell enabled with this feature.
3.
Check the traced messages:
Check the value of maxDl-Power under the IE Nbap-Msg contained in the

NBAP_RL_RECFG_PREP message. If the value of the IE maxDl-Power is the same
as the value of Max DL RL Power For Spec User in the MML command MOD
UCELLRLPWR, this feature has been activated.
Issue 06 (2013-03-25)

598
RAN14.0

Weak Reception UEs
Figure 176-2 maxDl-Power IE diagram
1.
Disable differentiated power control and differentiated handover for smartphones.

a.
Run the BSC6900 MML command MOD UIMEITAC (CME single

Configuration > IMEI TAC; CME batch modification center: not supported).
In this step, set The function of the TAC to Special_User_Enhance, and clear
the SPECUSER_AMR_HOENHANCE_SWITCH and
SPECUSER_AMR_PWRENHANCE_SWITCH check boxes under
SpecUserFunctionSwitch.
b.
Optional: Run the BSC6900 MML command SET URRCTRLSWITCH

Process Switch Configuration > Process Switch; CME batch modification
center: 3.15 Modifying RNC Parameters in Batches). In this step, clear the
RNC_CS_QUERY_UE_IMEI_SWITCH check box under Process Control
Switch 2.
----End
Example
//Activating Voice Experience Improvement for Smartphones
//Enabling CS IMEI acquisition
SET URRCTRLSWITCH: PROCESSSWITCH2=RNC_CS_QUERY_UE_IMEI_SWITCH-1;
//Enabling differentiated power control and differentiated handover for
smartphones and setting the TAC of the smartphone
ADD UIMEITAC: TAC_FUNC=Special_User_Enhance, TAC=12345,
Description="Smart Phone",
SpecUserFunctionSwitch=SPECUSER_AMR_HOENHANCE_SWITCH-1&SPECUSER_AMR_PWREN
HANCE_SWITCH-1;
//Setting the parameters related to cell load monitoring
Issue 06 (2013-03-25)

599
RAN14.0

Weak Reception UEs
ADD UCELLLDM: CellId=1, SpecUserPwrEnDlPwrTrigThd =80;

//Setting the parameters related to RL transmit power in the cell
MOD UCELLRLPWR: CellId=1, CNDomainId=CS_DOMAIN, MaxBitRate=12200,
RlMaxDlPwr=0, SpecUserRlMaxDlPwr =30;
//Setting the RNC-level parameters related to differentiated handover for
smartphones
SET UHOCOMM: SpecUserHystFor2D=6, SpecUserCSThd2DEcN0=-13,
SpecUserCSThd2FEcN0=-10, SpecUserCSThd2DRSCP=-93,
SpecUserCSThd2FRSCP=-90;
//Setting the cell-level parameters related to differentiated handover
for smartphones
ADD UCELLHOCOMM: CellId=1, SpecUserHystFor2D =6, SpecUserCSThd2DEcN0=-13,
SpecUserCSThd2FEcN0=-10, SpecUserCSThd2DRSCP =-93,
SpecUserCSThd2FRSCP=-90;
//Deactivating Voice Experience Improvement for Smartphones
//Disabling CS IMEI acquisition
SET URRCTRLSWITCH: PROCESSSWITCH2=RNC_CS_QUERY_UE_IMEI_SWITCH-0,
PROCESSSWITCH4=SEND_MSG_NULL_SWITCH-0;
//Disabling differentiated power control and differentiated handover for
smartphones
MOD UIMEITAC: TAC_FUNC=Special_User_Enhance, TAC=12345,
Description="Smart Phone",
SpecUserFunctionSwitch=SPECUSER_AMR_HOENHANCE_SWITCH-0&SPECUSER_AMR_PWREN
HANCE_SWITCH-0;
Issue 06 (2013-03-25)

600
RAN14.0
177
Configuring Layered Paging in

URA_PCH
Layered Paging in URA_PCH.
Prerequisites
l
Dependency on Other Features

License
Other Prerequisites
The URA_PCH state has been enabled and CellReSelectCounter in the SET
UUESTATETRANS (CME single configuration: UMTS Radio Global
Configuration Express > UE State Transition Parameter Configuration > UE State
Translating Parameters; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches) command has been specified to enable UEs to easily enter the
URA_PCH state.
Before the feature activation, it is recommended that Enhanced Fast Dormancy be
activated and parameters related to the D2F state transition be configured to enable
smartphones to enter the URA_PCH state if possible.
Context
Due to the rapid rise of smart phone use in recent years, paging messages have been increasing.
Conventionally, paging messages are sent to the entire UTRAN registration area (URA). Once
Layered Paging in URA_PCH is activated, paging messages are first sent to the last camped-on
cell of the UEs in the URA_PCH state and the neighboring cells of the last camped-on cell.
When necessary, these messages will be sent to the URA. This reduces the number of paging
messages and the possibility of PCH congestion, eliminates the need for manually dividing
URAs, and reduces the number of URA updates.
l
Issue 06 (2013-03-25)
Precautions
601
RAN14.0
None.
l
Data Preparation
Paramet
er Name
Parame
ter ID
Parameter Setting
Data Source
Process
Control
Switch
PROCE
SSSWIT
CH:
URAPC
H_LAY
ERED_
PAGIN
G_NRT
_SWITC
H
This switch must be turned on.
Network plan
URAPC
H_LAYE
RED_PA
GING_R
T_SWIT
CH
PROCE
SSSWIT
CH:
URAPC
H_LAY
ERED_
PAGIN
G_RT_S
WITCH
It is recommended that this switch not Network plan

be turned on if users are highly
sensitive to the delay in real-time
services.
Procedure
l
1.

RNC Parameters in Batches). In this step,
Select the URAPCH_LAYERED_PAGING_RT_SWITCH check box under
the PROCESSSWITCH parameter to enable Layered Paging in URA_PCH for
real-time services.
Select the URAPCH_LAYERED_PAGING_NRT_SWITCH check box under
the PROCESSSWITCH parameter to enable Layered Paging in URA_PCH for
non-real-time services.
Check the value of the counter VS.Paging1.Att1.URA.RealTime.Cell or
VS.Paging1.Att1.URA.NonRealTime.Cell on the M2000. If either counter is set to a value
other than 0, this feature has been activated.
1.
Issue 06 (2013-03-25)

RNC Parameters in Batches). In this step,
602
RAN14.0
Clear the URAPCH_LAYERED_PAGING_RT_SWITCH check box under the

PROCESSSWITCH parameter to disable Layered Paging in URA_PCH for realtime services.
Clear the URAPCH_LAYERED_PAGING_NRT_SWITCH check box under
the PROCESSSWITCH parameter to disable Layered Paging in URA_PCH for
non-real-time services.
----End
Example
//Enabling Layered Paging in URA_PCH for real-time services
SET URRCTRLSWITCH: PROCESSSWITCH=URAPCH_LAYERED_PAGING_RT_SWITCH-1;
//Enabling Layered Paging in URA_PCH for non-real-time services
SET URRCTRLSWITCH: PROCESSSWITCH=URAPCH_LAYERED_PAGING_NRT_SWITCH-1;
//Disabling Layered Paging in URA_PCH for real-time services
SET URRCTRLSWITCH: PROCESSSWITCH=URAPCH_LAYERED_PAGING_RT_SWITCH-0;
//Disabling Layered Paging in URA_PCH for non-real-time services
SET URRCTRLSWITCH: PROCESSSWITCH=URAPCH_LAYERED_PAGING_NRT_SWITCH-0;
Issue 06 (2013-03-25)

603
RAN14.0
178
Configuring Web browsing

acceleration
Web browsing acceleration. (This feature cannot be configured using the CME. )
Prerequisites
l
Dependencies on RNC hardware

NIUa board is required.

BTS3812E and BTS3812AE series base stations are configured with EBBI or EDLP
boards. HBBI and HDLP boards do not support this feature.
DBS3800 series base stations are configured with EBBC or EBBCd boards. The HBBU
board does not support this feature.
3900 series base stations are configured with WBBPb, WBBPd or WBBPf boards. The
WBBPa board does not support this feature.
The Network Intelligence Unit REV:a (NIUa) board is ready. The NIUa board can be
housed in the same slot as the DPUb or DPUe board. For details of inserting a NIUa
board, see Inserting a Board.

License
NOTE

Run the BSC6900 MML command SET LICENSE to set PPS Active Users to an appropriate value.
Context
This feature enables the RNC to identify web browsing services by parsing packets and thereby
to preferentially allocate higher bandwidth to these services. As a result, web browsing services
take shorter time and the user experience is improved.
Issue 06 (2013-03-25)

604
RAN14.0
Procedure
l
1.
Run the BSC6900 MML command ADD BRD to add a NIUa board. In this step, set
the Board Class to NIU, and set the Board Type to NIUa.
2.
Set the initial Scheduling Priority Indicator (SPI) weight on the BSC6900 LMT.
If the switch for the license control item of the feature WRFD-020806
Differentiated Service Based on SPI Weight is turned on, run the BSC6900
MML command SET USPIWEIGHT to configure weight of each SPI. In this
step, set Scheduling Priority Indicator and SPI Weight to appropriate values
Differentiated Service Based on SPI Weight is not turned on, run the BSC6900
MML command SET UFRC to set Default SPI Weight to an appropriate value
3.
Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select
the NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter
Process switch.
4.
Run the BSC6900 MML command ADD UIPSERVICEQOS. In this step, set the
Traffic Type to HTTP, and set the Traffic Priority to HIGH.
5.
Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set
Scheduling Priority Weight for High PRI Service, Scheduling Priority Weight
for Middle PRI Service, and Scheduling Priority Weight for Low PRI Service to
appropriate values based on the network plan.
1.
Verify that the value of the counter VS.IuPS.BytesPayldHTTP.Rx is not 0. If it is not

0, this feature has been activated.
1.
----End
Example
//Activating Web Browsing Acceleration
//ADD a NIUa Board
ADD BRD: SRN=0, BRDCLASS=NIU, BRDTYPE=NIUa, SN=8, MPUSUBRACK=0,
MPUSLOT=0;
//Setting the initial SPI weight value if the switch for the license
control item of the feature WRFD-020806 Differentiated Service Based on
SPI Weight is turned on
SET USPIWEIGHT: SPI=4, SPIWEIGHT=10;
SPI Weight is not turned on
SET UFRC: DefaultSPIWeight=10;
//Turning on the switch for a NodeB private interface
//Adding the priority mapping of HTTP services
Issue 06 (2013-03-25)

605
RAN14.0
ADD UIPSERVICEQOS: CnOpIndex=0, TrafficType=HTTP, TrafficPriority=HIGH;

//Setting scheduling priority weight that corresponds to services of each
priority
SET UDPUCFGDATA: ServPriAdjCoefHigh=100, ServPriAdjCoefMiddle=10,
ServPriAdjCoefLow=1;
Issue 06 (2013-03-25)

606
RAN14.0
179 Configuring P2P Downloading Rate Control during Busy

Hour
179
Configuring P2P Downloading Rate

Control during Busy Hour
P2P Downloading Rate Control during Busy Hour. (This feature cannot be configured using the
CME. )
Prerequisites
l
Dependencies on RNC Hardware
NIUa board is required.
BTS3812E and BTS3812AE series base stations are configured with EBBI or EDLP
boards. HBBI and HDLP boards do not support this feature.
DBS3800 series base stations are configured with EBBC or EBBCd boards. The
HBBU board does not support this feature.
3900 series base stations are configured with WBBPb or WBBPd boards. The
WBBPa board does not support this feature.
The Network Intelligence Unit REV:a (NIUa) board is ready. The NIUa board can
be housed in the same slot as the DPUb or DPUe board. For details of inserting a
NIUa board, see Inserting a Board.

NOTE

Run the BSC6900 MML command SET LICENSE to set PPS Active Users to an appropriate value.
License
Issue 06 (2013-03-25)

607
RAN14.0

Hour
Context
This feature restricts point to point service (P2P) traffic during busy hours, thereby improving
the user experience of other delay-sensitive services and reducing operating costs. During nonbusy hours, P2P downloads are not restricted, thereby improving the user experience of P2P
users and full utilizing network resources.
Procedure
l
1.
Run the BSC6900 MML command ADD BRD to add a NIUa board. In this step, set
the Board Class to NIU, and set the Board Type to NIUa.
2.
Set the initial Scheduling Priority Indicator (SPI) weight on the BSC6900 LMT.
Differentiated Service Based on SPI Weight is turned on, run the BSC6900
MML command SET USPIWEIGHT to configure weight of each SPI. In this
step, set Scheduling Priority Indicator and SPI Weight to appropriate values
Differentiated Service Based on SPI Weight is not turned on, run the BSC6900
MML command SET UFRC to set Default SPI Weight to an appropriate value
3.
Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select
the NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter
Process switch.
4.
Run the BSC6900 MML command ADD UIPSERVICEQOS to add the priority
mapping of P2P services.
5.
Run the BSC6900 MML command SET UDPUCFGDATA to set scheduling priority
weight that corresponds to services of each priority to appropriate values.
1.
Verify that the value of the counter VS.IuPS.BytesPayldP2P.Rx is not 0. If it is not 0,

1.
----End
Example
//Activating P2P Downloading Rate Control during Busy Hour
//ADD a NIUa Board
ADD BRD: SRN=0, BRDCLASS=NIU, BRDTYPE=NIUa, SN=8, MPUSUBRACK=0,
MPUSLOT=0;
SPI Weight is turned on
SPI Weight is not turned on
Issue 06 (2013-03-25)

608
RAN14.0

Hour

//Adding the priority mapping of P2P services
ADD UIPSERVICEQOS: CnOpIndex=0, TrafficType=P2P, TrafficPriority=LOW;
//Setting scheduling priority weight that corresponds to services of each
priority
SET UDPUCFGDATA: ServPriAdjCoefHigh=100, ServPriAdjCoefMiddle=10,
ServPriAdjCoefLow=1;
Issue 06 (2013-03-25)

609
RAN14.0
180
Configuring Dynamic Power Sharing

of Multi-Carriers
Dynamic Power Sharing of Multi-Carriers.
Prerequisites
l

License
Context
Dynamic Power Sharing of Multi-Carriers means that among multiple carriers, the carrier
bearing HSPA service can dynamically share the unused power resource of another carrier. This
function increases the utilization of the power amplifier as well as the HSPA service rate of the
cell. For asymmetrical power configuration, the carrier with higher emitting power cannot share
the unused power resource of the carrier with lower emitting power.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the NodeB MML command ADD PAGRP (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Other Information >
PAGRP; CME batch modification center: not supported) to add a power sharing
group.

610
RAN14.0

NOTE
l Dynamic spectrum sharing cannot be configured with dynamic power sharing.

l A power sharing group consists of a source local cell and a destination local cell.
l The source local cell must support only R99 services, and the destination local cell must
support HSDPA services.
l The source local cell and the destination local cell must use the same RF module and be
configured with the same maximum power.
l The maximum rate of idle power that the source local cell is allowed to share with the
destination local cell is recommended to set to default value. This rate is based on the
configured maximum transmit power of the source local cell.
l The rate of idle power that must be reserved for the source local cell. This rate is based on
the configured maximum transmit power of the source local cell. Reserving the idle power
for the source local cell helps avoid power fluctuation in the source local cell caused by
power sharing that is not timely.
1.
Before configuring the power sharing group, increase the load in the destination local
cell to 90% by means of load simulation.
2.
Use multiple HSDPA UEs to perform high-speed downloading in the destination local
cell. Check the throughput of the destination local cell.
3.
Run the NodeB MML command ADD PAGRP to add a power sharing group.
4.
Check the throughput of the destination local cell after the power sharing group is
configured. If the throughput is greatly increased after the power sharing group is
configured, you can infer that the feature is enabled.
1.
Run the NodeB MML command RMV PAGRP (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Other Information >
PAGRP; CME batch modification center: not supported) to remove the power sharing
group.
----End
Example
ADD PAGRP: SLOCELL=1, DLOCELL=2, MAXSHRTO=50, SHMGN=10;
RMV PAGRP: DLOCELL=2;
Issue 06 (2013-03-25)

611
RAN14.0
181 Configuring Multi-Carrier Switch off Based on Traffic

Load
181
Configuring Multi-Carrier Switch off

Based on Traffic Load
Multi-Carrier Switch off Based on Traffic Load.
Prerequisites
l

License
Context
l
The power consumption evaluation of the products in mobile networks shows that the
devices, particularly the base stations, in the radio access network are the principal
contributor of power consumption and CO2 emissions when they are functioning.
If multiple carriers are used in the same coverage area, Huawei provides operators with
adaptive carrier power management to reduce power consumption. The traffic volume
varies with time. For example, a base station in the Central Business District (CBD) has a
higher traffic volume in the daytime, which requires more than one carrier to serve all the
subscribers; the traffic volume becomes low from midnight to early morning of the next
day. From RAN10.0 on, during an idle period that is configurable by operators, the RNC
dynamically shuts down the carriers on which there is no service and uses the other carriers
in the same area. The carriers will be turned on again when the traffic on the other carriers
becomes congested or when the idle period ends. This reduces power consumption.
Procedure
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA (CME

single configuration: UMTS Radio Global Configuration Express > RNC_Lever
612
RAN14.0

Load
Cell Dynamic ShutDown Parameter Configuration > Cell Dynamic Shutdown

Parameters in RNC; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches). In this step, set Cell Dynamic ShutDown Switch For
RNC, Period Judge Timer Length for Cell Dynamic Open, and Protect Timer
Length for Cell Dynamic ShutDown to appropriate values.
2.
Assume that the cell ID is 1. Run the BSC6900 MML command LST
UCELLDYNSHUTDOWN (CME single configuration: UMTS Cell Configuration
Express > Cell Parameters > Cell Dynamic Shutdown Parameters) to check
whether Cell Dynamic ShutDown Switch is turned on.
If Cell Dynamic ShutDown Switch is turned off, run the BSC6900 MML
command ADD UCELLDYNSHUTDOWN (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell Dynamic Shutdown
Parameters in Batches) to turn on Cell Dynamic ShutDown Switch, specify the
shutdown period, and set the following parameters to appropriate values.
Cell Dynamic ShutDown Type
Cell Dynamic ShutDown Total User number Threshold
Cell Dynamic ShutDown Hsdpa User number Threshold
Cell Dynamic ShutDown Hsupa User number Threshold
Cell Dynamic ShutDown Neighbour Cell Load Remain threshold
NOTE
Default values of the above parameters are recommended.
If Cell Dynamic ShutDown Switch is turned on, run the BSC6900 MML
command MOD UCELLDYNSHUTDOWN (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell Dynamic Shutdown
Parameters in Batches) to modify the related parameters.
3.
Run the BSC6900 MML command LST UINTERFREQNCELL (CME single

configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell) to check whether an inter-frequency co-coverage
neighboring cell is configured for cell 1. Assume that the ID of the inter-frequency
co-coverage neighboring cell is 2.
This feature takes effect only when cell 2 is served by the same NodeB as cell 1.
If the neighboring cell is not configured, run the BSC6900 MML command ADD
UINTERFREQNCELL (CME single configuration: UMTS Cell Configuration
Express > Neighboring Cell > Inter-frequency Neighboring Cell; CME batch
modification center: not supported) to add an inter-frequency co-coverage
neighboring cell. In this step, set Blind Handover Flag to TRUE.
If the neighboring cell is configured, run the BSC6900 MML command MOD
modification center: not supported). In this step, set Blind Handover Flag to
TRUE.
4.
Issue 06 (2013-03-25)

HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm).
613
RAN14.0

Load
NOTE
This feature takes effect only when the GBP measurement switch for the inter-frequency cocoverage neighboring cell is turned on.
1.
Start alarm browsing on the BSC6900 LMT.
2.
Ensure that the total number of users in cell 1 and cell 2 is 0. Alternatively, set up two
inter-frequency co-coverage neighboring cells where no user is admitted.
3.
At a time during the period specified by running the BSC6900 MML command ADD
UCELLDYNSHUTDOWN (for example, 09:10):
If an ALM-22202 UMTS Cell Unavailable is reported at cell 1 with the cause value
of cell dynamic shutdown, this feature has been activated.
If this alarm is not reported or is reported but the cause value is not cell dynamic
shutdown, this feature is not activated.
4.
Check whether this feature is activated by viewing the counter

VS.DynOpen.CellSetup and check whether this feature is deactivated by viewing the
counter VS.DynClose.CellDel on the M2000.
1.

Parameters in Batches) to deactivate this feature at the RNC. In this step, set Cell
Dynamic ShutDown Switch For RNC to OFF(switch off).
2.
Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN

(CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell Dynamic Shutdown Parameters; CME batch modification
center: not supported) to deactivate this feature for cell 1.
----End
Example
//Turning on the RNC-level switch for dynamic shutdown
SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=ON;
//Turning on the cell-level switch for dynamic shutdown
ADD UCELLDYNSHUTDOWN: CellId=1, DynShutdownSwitch=ON_1, StartTime1=08&59,
EndTime1=10&59, DynShutDownType=CONDITIONALSHUTDOWN;
//Adding inter-frequency co-coverage neighboring cells for the cell where
this feature is activated (cell 1 and cell 2 in the following command are
served by the same NodeB)
ADD UINTERFREQNCELL: RNCId=110, CellId=1, NCellRncId=110, NCellId=2,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE,
NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;
//Turning on the GBP measurement switch for an inter-frequency co-coverage
neighboring cell
MOD UCELLALGOSWITCH: CellId=2, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1,
NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST,
/*Deactivation procedure*/
//Deactivating Multi-Carrier Switch off Based on Traffic Load at the RNC
SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=OFF;
Issue 06 (2013-03-25)

614
RAN14.0

Load
//Deactivating Multi-Carrier Switch off Based on Traffic Load for cell 1

RMV UCELLDYNSHUTDOWN: CellId=1;
Issue 06 (2013-03-25)

615
RAN14.0
182
Configuring Energy Efficiency

Improved
Energy Efficiency Improved.
Prerequisites
l
MTRU of the BTS3812E/BTS3812AE does not support this feature.
The RRU3801C of the NodeB does not support this feature.
Other RF modules support this feature.

License
Context
l
Based on the high efficient power amplification techniques, power amplification

parameters can be dynamically adjusted to further improve the power amplification
efficiency under low load. The NodeB adjusts the Power Amplifier (PA) bias voltage based
on the output power that varies with the traffic load, improving the PA efficiency and
reducing the static PA power consumption.
When there is no HSDPA service, the NodeB supports this function as long as the license
is activated.
When there are HSDPA services, the NodeB does not support this function by default. If
this function is required, perform the following activation operations.
Procedure
1.
Issue 06 (2013-03-25)
Run the NodeB MML command SET OPTDYNADJPARA (CME single

616
RAN14.0
Information > Radio Management > OPTDYNADJPARA; CME batch

modification center: not supported) to set dynamic voltage adjustment parameters.
Set Dynamic Voltage Adjustment Switch to ON.
Set Start Time and End Time as required.
l
1.
Run the NodeB MML command LST OPTDYNADJPARA to query the dynamic
voltage adjustment parameters. In the command output, check that Dynamic Voltage
Adjustment Switch is set to ON, which indicates that the function is activated. Check
that Start Time and End Time are set to the required values.
1.
Run the NodeB MML command SET OPTDYNADJPARA (CME single

Information > Radio Management > OPTDYNADJPARA; CME batch
modification center: not supported) to set dynamic voltage adjustment parameters. In
this step, set Dynamic Voltage Adjustment Switch to OFF.
----End
Example
//Activation procedure SET OPTDYNADJPARA: DYNADJSWITCH=ON,
DYNADJSTARTTIME=0, DYNADJENDTIME=6;
//Verification procedure LST OPTDYNADJPARA:;
//Deactivation procedure SET OPTDYNADJPARA: DYNADJSWITCH=OFF;
Issue 06 (2013-03-25)

617
RAN14.0
183 Configuring Multi-Carrier Switch off Based on Power

Backup
183

Based on Power Backup
Multi-Carrier Switch off Based on Power Backup.
Prerequisites
l
The BTS3902E doesn't support this feature.

License
Context
In case of mains failure, the backup power system starts to operate. In this case, this feature can
implement hierarchical carrier shutdown based on the shutdown duration and cell priority.
Procedure
l
NodeB V200R014
1.
Batches) with Local Cell ID and Sector Type specified in order to set reserved cells.
For the cells that need to provide services continuously during the level-1 shutdown
period, set Reserved Cell to TRUE.
NOTE
It is recommended that at least one cell be reserved for a sector. In case of mains failure, the
reserved cell continues to provide services for the users in this sector.
Issue 06 (2013-03-25)

618
RAN14.0

Backup
2.
Run the NodeB MML command MOD LOWPOWERPARA (CME single

Information > Equipment Management > NODEB; CME batch modification
center: not supported) to set the intelligent power shutdown switch with the NodeB
ISD Switch set to ENABLE. Set Level 1 power off Delay (s) and Level 2 power off
Delay (s) based on the backup capability of the batteries.
3.
Optional: If you need to use the smooth power change function, run the NodeB MML
command SET SMTHPWRSWTCH (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Basic Information > Basic Information
> Smooth Power Change Function Switch; CME batch modification center: not
supported) to set the intelligent power shutdown switch with the Smooth Power
Change Function Switch set to OPEN.
NOTE
Before a cell is shut down, the smooth power change function reduces the TX power of the PCPICH so that the services in the cell are handed over to neighboring cells. This prevents service
disruption due to abrupt cell shutdown.
1.
Run the NodeB MML command LST LOWPOWERPARA to query the

configuration information about the intelligent power shutdown switch. On the LMT,
check whether the NodeB ISD Switch is set to ENABLE, and whether the Level 1
power off Delay (s) and Level 2 power off Delay (s) are set correctly.
2.
information about local cells. Check whether the value of Reserve Cell of each local
cell is correct.
3.
Optional: If the smooth power change function is already used, run the NodeB MML
command LST SMTHPWRSWTCH to check whether the intelligent power
shutdown switch is turned on. If the Smooth Power Change Function Switch is set
to OPEN, it indicates that this function is enabled.
1.
Run the NodeB MML command MOD LOWPOWERPARA (CME single

Information > Equipment Management > NODEB; CME batch modification
center: not supported) to turn off the intelligent power shutdown switch with the
NodeB ISD Switch set to DISABLE.
NodeB V100R014
1.
Batches) with Local Cell ID and Sector Type specified in order to set reserved cells.
For the cells that need to provide services continuously during the level-1 shutdown
period, set Reserved Cell to TRUE.
NOTE
It is recommended that at least one cell be reserved for a sector. In case of mains failure, the
reserved cell continues to provide services for the users in this sector.
2.
Issue 06 (2013-03-25)
Run the NodeB MML command SET ITELSHUTDOWN (CME single

619
RAN14.0

Backup
Information > More Information > NODEB; CME batch modification center: not
supported) to set the intelligent power shutdown switch with the ISD SWITCH set
to ENABLE. Set LEVEL1 DELAY and LEVEL2 DELAY based on the backup
capability of the batteries.
3.
Optional: If you need to use the smooth power change function, run the NodeB MML
command SET SMTHPWRSWTCH (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Basic Information > Basic Information
> Smooth Power Change Function Switch; CME batch modification center: not
supported) to set the intelligent power shutdown switch with the Smooth Power
Change Function Switch set to OPEN.
NOTE
Before a cell is shut down, the smooth power change function reduces the TX power of the PCPICH so that the services in the cell are handed over to neighboring cells. This prevents service
disruption due to abrupt cell shutdown.
1.
Run the NodeB MML command LST ITELSHUTDOWN to query the configuration
information about the intelligent power shutdown switch. On the LMT, check whether
the NodeB ISD Switch is set to ENABLE, and whether the Level 1 power off and
Level w power off are set correctly.
2.
information about local cells. Check whether the value of Reserve Cell of each local
cell is correct.
3.
Optional: If the smooth power change function is already used, run the NodeB MML
command LST SMTHPWRSWTCH to check whether the intelligent power
shutdown switch is turned on. If the Smooth Power Change Function Switch is set
to OPEN, it indicates that this function is enabled.
1.
Run the NodeB MML command SET ITELSHUTDOWN (CME single

Information > More Information > NODEB; CME batch modification center: not
supported) to turn off the intelligent power shutdown switch with the ISD Switch set
to DISABLE.
----End
Example
l
NodeB V200R014
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, RSV=TRUE;
MOD LOWPOWERPARA: ISD=ENABLE, LEVEL1=60, LEVEL2=120;
LST LOWPOWERPARA:;
LST SMTHPWRSWTCH:;
MOD LOWPOWERPARA: ISD=DISABLE;
NodeB V100R014
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, RSV=TRUE;
Issue 06 (2013-03-25)

620
RAN14.0

Backup
SET ITELSHUTDOWN: ISD=ENABLE, LEVEL1=60, LEVEL2=120;
LST ITELSHUTDOWN:;
LST SMTHPWRSWTCH:;
SET ITELSHUTDOWN: ISD=DISABLE;
Issue 06 (2013-03-25)

621
RAN14.0
184

Based on QoS
Multi-Carrier Switch off Based on QoS.
Prerequisites
l

License
Context
This feature guarantees the data rate for only DCH and high-priority HSDPA users. For lowpriority HSDPA users, only Guaranteed Bit Rate (GBR) is guaranteed.
If the remaining bandwidth of neighboring cells can meet the preceding requirements for rate,
this feature can be enabled to reduce the power consumption, and therefore increase profits of
operators.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, set Cell Dynamic ShutDown Switch for
RNC to ON(switch on).
2.
Assume that the cell ID is 2003. Run the BSC6900 MML command LST
UCELLDYNSHUTDOWN (CME single configuration: UMTS Cell Configuration
622
RAN14.0
Express > Cell Parameters > Cell Dynamic Shutdown Parameters) to check
whether Cell Dynamic ShutDown Switch is set to ON for this cell.
3.
4.
a.
If Cell Dynamic ShutDown Switch is set to OFF, run the BSC6900 MML
command ADD UCELLDYNSHUTDOWN (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Dynamic
Shutdown Parameters; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches). In this step, set Cell Dynamic ShutDown
Switch to ON_1(switch on1), specify First Cell Dynamic ShutDown Interval
Start Time, First Cell Dynamic ShutDown Interval End Time, set Cell
Dynamic ShutDown Type to QOSSHUTDOWN(QosShutDown), and specify
High-Priority Scheduling Indicator.
b.
If Cell Dynamic ShutDown Switch is turned on, run the BSC6900 MML
command MOD UCELLDYNSHUTDOWN (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Dynamic
Shutdown Parameters; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches) to modify the settings of the preceding
parameters to the specified settings.
Run the BSC6900 MML command LST UINTERFREQNCELL (CME single

configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell) to check whether cell 2003 is configured with an interfrequency co-coverage neighboring cell. Assume that the ID of the inter-frequency
co-coverage neighboring cell is 2004.
a.
This feature takes effect only when cell 2004 is under the same NodeB as cell
2003.
b.
If the neighboring cell is not configured, run the BSC6900 MML command ADD
UINTERFREQNCELL (CME single configuration: UMTS Cell
Configuration Express > Neighboring Cell > Inter-frequency Neighboring
Cell; CME batch modification center: not supported) to add an inter-frequency
co-coverage neighboring cell. In this step, set Blind Handover Flag to TRUE.
c.
If the neighboring cell is configured, run the BSC6900 MML command MOD
UINTERFREQNCELL (CME single configuration: UMTS Cell
Configuration Express > Neighboring Cell > Inter-frequency Neighboring
Cell; CME batch modification center: not supported). In this step, set Blind
Handover Flag set to TRUE.
Run the BSC6900 MML command ADD UCELLALGOSWITCH (CME single

HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm).
NOTE
This feature takes effect only when the GBP measurement switches of both cell 2003 and cell
2004 are turned on.
Issue 06 (2013-03-25)
1.
Start alarm browsing on the BSC6900 LMT.
2.
Ensure that the total number of users in cell 2003 and cell 2004 is 0. Alternatively,
add two inter-frequency co-coverage cells that have bidirectional neighboring cell
relationships, and these cells do not carry any services.
3.
At a time during the period specified in the BSC6900 MML command ADD
UCELLDYNSHUTDOWN (for example, 09:10):
623
RAN14.0
If the alarm ALM-22202 UMTS Cell Unavailable is reported at cell 2003 with a
cause of cell dynamic shutdown, this feature has been activated.
If the alarm is not reported or is reported at cell 2003 but the cause is not cell
dynamic shutdown, this feature has not been activated.
4.
You can also view whether the feature is activated by checking certain counters on
the M2000: If the value of the counter VS.DynOpen.CellSetup is not 0, the feature
is activated; If the value of the counter VS.DynClose.CellDel is not 0, the feature is
not activated.
1.

Parameters in Batches) to deactivate this feature for the RNC. In this step, set Cell
Dynamic ShutDown Switch for RNC to OFF(switch off).
2.
Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN

Parameters > Cell Dynamic Shutdown Parameters; CME batch modification
center: not supported). In this step, set Cell ID to 2003 to deactivate this feature for
cell 2003.
----End
Example
//Turning on the cell dynamic shutdown switch for the RNC
SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=ON;
//Turning on the cell dynamic shutdown switch
ADD UCELLDYNSHUTDOWN: CellId=2003, DynShutdownSwitch=ON_1,
StartTime1=11&50, EndTime1=11&55, DynShutDownType=QOSSHUTDOWN,
HighPriSPI=SPI11-1&SPI12-1&SPI13-1;
//Adding an inter-frequency co-coverage neighboring cell (cell 2004) to a
cell (cell 2003) whose TRXs are shut down (cells 2003 and 2004 are under
the same NodeB)
ADD UINTERFREQNCELL: RNCId=110, CellId=2003, NCellRncId=110,
BlindHoFlag=TRUE, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;
//Turning on the GBP measurement switches for a cell (cell 2003)and its
inter-frequency co-coverage neighboring cell (cell 2004)
ADD UCELLALGOSWITCH: CellId=2003, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1,
ADD UCELLALGOSWITCH: CellId=2004, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1,
//Deactivating Multi-Carrier Switch off Based on QoS for the RNC
SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=OFF;
//(Optional) Deactivating Multi-Carrier Switch off Based on QoS for cell
Issue 06 (2013-03-25)

624
RAN14.0
2003
RMV UCELLDYNSHUTDOWN: CellId=2003;
Issue 06 (2013-03-25)

625
RAN14.0
185
Configuring Intelligent Power

Management
Intelligent Power Management.
Prerequisites
l
Only when DBS3900, BTS3900AL or BTS3900A is used with APM30 and battery.

License
Context
With this feature, certain Power Supply Units (PSUs) can be powered on or off according to the
power consumption of the NodeB, reducing the power consumption.
Procedure
l
1.
1.
Run the NodeB MML command LST PSUISS to check whether the PSU Intelligent
Shutdown Switch is set to ENABLE(ENABLE).
1.
Issue 06 (2013-03-25)
Run the NodeB MML command SET PSUISS (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Basic Information > Equipment
Management > PSU Intelligent Shutdown Switch; CME batch modification center:
not supported) with the PSU Intelligent Shutdown Switch set to ENABLE
(ENABLE).
Run the NodeB MML command SET PSUISS (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Basic Information > Equipment
626
RAN14.0
Management > PSU Intelligent Shutdown Switch; CME batch modification center:
not supported) with the PSU Intelligent Shutdown Switch set to DISABLE
(DISABLE).
----End
Example
SET PSUISS: PSUISS=ENABLE;
LST PSUISS:;
SET PSUISS: PSUISS=DISABLE;
Issue 06 (2013-03-25)

627
RAN14.0
186
Configuring RAN Sharing

RAN Sharing Introduction Package.
Prerequisites
l

This feature cannot be used together with the feature WRFD-021311 MOCN
License
Context
This feature enables multiple operators to share the same set of RAN equipment but have their
own independent cells. The same set of RAN equipment can provide different operators with
rich and differentiated services.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command SET UOPERATORSHARINGMODE (CME

single configuration: UMTS Global Configuration Express > Operator
Configuration > RNC Operators Sharing Mode; CME batch modification center:
not supported). In this step, set RAN Sharing Support to YES to turn on the RAN
sharing switch.
2.
Run the BSC6900 MML command ADD UCNOPERATOR (CME single

configuration: UMTS Global Configuration Express > Operator Configuration >
CN Operator; CME batch modification center: not supported) twice to add the
primary and secondary operators respectively.
628
RAN14.0
3.
Run the BSC6900 MML command ADD UCNOPERGROUP (CME single

CN Operator Group; CME batch modification center: not supported) twice to add
an operator group respectively for the primary and secondary operators.
4.
Run the BSC6900 MML command ADD OPC (CME single configuration: UMTS
Global Configuration Express > Signaling Configuration > OSP; CME batch
modification center: not supported) for multiple times to add OSPs for primary and
secondary operators.
NOTE
Primary and secondary operators can have their own OSPs for the same BSC6900.
l Primary and secondary operators can share the same Network ID when required.
l When primary and secondary operators share the same Network ID, they must use the
same OSP code bits but different OSP code[Whole Number].
l When primary and secondary operators do not share Network ID, they can have different
values for OSP code bits.
5.
Run the BSC6900 MML command ADD N7DPC (CME single configuration: UMTS
Global Configuration Express > Signaling Configuration > DSP Of DPU; CME
batch modification center: not supported) for multiple times to add DSPs for primary
and secondary operators.
6.
Configure Iu data for the primary and secondary operators.
7.
Run the BSC6900 MML command ADD UCNNODE (CME single configuration:
batch modification center: not supported) for multiple times to add CN nodes for the
primary operator.
8.
Configure Iub data and add a dedicated cell.

NOTE
l There are two types of RAN sharing:

l NodeBs are independently deployed by operators.
l NodeBs are shared by operators and cells are not shared by operators.
l After adding a cell or changing the UARFCN, you need to verify that the UARFCN used
by the cell is in the allowed range of the NodeB license. If the UARFCN is not in the
allowed range of the NodeB license, you must issue a new NodeB license on the M2000.
If the CNs of the primary and secondary operators are working properly, dedicated cells
can be set up for these operators, and the IDs of these operators can be displayed on the
UE, this feature has been activated.
1.

not supported). In this step, set RAN Sharing Support to NO to turn off the RAN
sharing switch.
----End
Example
//Activating RAN Sharing Introduction Package
Issue 06 (2013-03-25)

629
RAN14.0
//Setting the sharing mode for the operators

SET UOPERATORSHARINGMODE: RANSharingSupport=YES,
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES;
//Adding a primary operator
ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502",
MNC="10", CnOpIndex=0;
//Adding a secondary operator
ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310",
//Adding an operator group for the primary operator
ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE,
CnOpIndex1=0;
//Adding an operator group for the secondary operator
ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE,
CnOpIndex1=1;
//Adding the OSP for the primary operator
ADD OPC: NAME="PRIM", SPX=0, NI=INT, SPCBITS=BIT14, SPDF=WNF, SPC=111;
//Adding the OSP for a secondary operator
ADD OPC: NAME="SEC", SPX=1, NI=NAT, SPCBITS=BIT24, SPDF=WNF, SPC=222;
//Adding DSPs for the primary operator
ADD N7DPC: NAME="PRIMCS", DPX=0, SPX=0,
BEARTYPE=M3UA;
ADD N7DPC: NAME="PRIMPS", DPX=1, SPX=0,
BEARTYPE=M3UA;
//Adding DSPs for a secondary operator
ADD N7DPC: NAME="PRIMCS", DPX=2, SPX=1,
BEARTYPE=M3UA;
ADD N7DPC: NAME="PRIMPS", DPX=3, SPX=1,
BEARTYPE=M3UA;
SPDF=WNF, DPC=333, DPCT=IUCS,

SPDF=WNF, DPC=444, DPCT=IUPS,
SPDF=WNF, DPC=555, DPCT=IUCS,
SPDF=WNF, DPC=666, DPCT=IUPS,
//Adding CN nodes for the primary operator

ADD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0,
CNProtclVer=R99, SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL,
AvailCap=60000, TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1,
Switch3GPP25415CR0125=OFF;
ADD UCNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=1,
AvailCap=60000;
//Adding CN nodes for a secondary operator
AvailCap=60000, TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1,
AvailCap=60000;
//Adding a cell
ADD UCELLQUICKSETUP: CELLID=1, CELLNAME="Cell1", BANDIND=BAND1,
PeerIsValid=VALID, PeerCellId=100, CnOpGrpIndex=0, UARFCNUPLINK=9612,
UARFCNDOWNLINK=10562, PSCRAMBCODE=0, TCELL=CHIP256, LAC=H'2501,
SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId = 6, URANUM=D8, URA1=1,
URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8,
Issue 06 (2013-03-25)

630
RAN14.0
NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430,

PCPICHPOWER=330;
//Deactivating RAN Sharing Introduction Package

SET UOPERATORSHARINGMODE: RANSharingSupport=NO;
Issue 06 (2013-03-25)

631
RAN14.0
187
Configuring Dedicated Carrier for

Each Operator
WRFD-02130401 Dedicated Carrier for Each Operator.
Prerequisites
l

The feature WRFD-021304 RAN Sharing Introduction Package has been configured
before this feature is activated.
License
Procedure
l
Issue 06 (2013-03-25)
1.

not supported). In this step, set RAN Sharing Support to YES to turn on the RAN
sharing switch.
2.

CN Operator; CME batch modification center: not supported) to add the primary and
secondary operators.
3.

CN Operator Group; CME batch modification center: not supported) twice to add
an operator group respectively for the primary and secondary operators.
4.
Configure Iu data for the primary and secondary operators.

632
RAN14.0
5.
Configure Iub data and add a dedicated cell.

NOTE
There are two types of RAN sharing:

l NodeBs are independently deployed by operators.
l NodeBs are shared by operators and cells are not shared by operators.
Use a UE to access cells 1000 and 1001. If the network access is successful, carriers are
exclusively used by the operators.
1.

not supported). In this step, set RAN Sharing Support to NO to turn off the RAN
sharing switch.
2.
Run the BSC6900 MML command RMV UCELL (CME single configuration: Main
View > Right click UMTS cell > Delete Cell; CME batch modification center: not
supported) to remove all cells configured for the operator.
----End
Example
//Activating Dedicated Carrier for Each Operator
//Configuring basic information about the BSC6900
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES;
ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502",
ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310",
//Adding an operator group for the primary operator
ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE,
CnOpIndex1=0;
//Adding an operator group for the secondary operator
ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE,
CnOpIndex1=1;
//Adding dedicated cell 1
ADD UCELLQUICKSETUP: CELLID=1, CELLNAME="Cell1",
BANDIND=BAND1,PeerIsValid=VALID, PeerCellId=100,
CnOpGrpIndex=0,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, PSCRAMBCODE=0,
TCELL=CHIP256, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId
= 6,URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7,
URA8=8, NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430,
PCPICHPOWER=330;
//Adding dedicated cell 2
ADD UCELLQUICKSETUP: CELLID=2, CELLNAME="Cell2",
BANDIND=BAND1,PeerIsValid=VALID, PeerCellId=100,
CnOpGrpIndex=1,UARFCNUPLINK=9622, UARFCNDOWNLINK=10572, PSCRAMBCODE=0,
Issue 06 (2013-03-25)

633
RAN14.0
TCELL=CHIP256, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId

= 6,URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7,
URA8=8, NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430,
PCPICHPOWER=330;
//Deactivating Dedicated Carrier for Each Operator

//Turning off the RAN sharing switch
SET UOPERATORSHARINGMODE: RANSharingSupport=NO;
//Removing a dedicated cell
RMV UCELL: CellId=1;
Issue 06 (2013-03-25)

634
RAN14.0
188
Configuring Flexible Network

Architecture
WRFD-02130402 Flexible Network Architecture.
Prerequisites
l

feature depends on the feature WRFD-021304 RAN Sharing Introduction Package.
License
Context
This feature can meet the networking requirements of different operators.
Procedure
l
For information on activating the Iu Flex feature, see 227 Configuring Iu Flex.
For information on activating the Cell Broadcast Service feature, see 70 Configuring Cell
Broadcast Service.
For information on activating the RAN Sharing feature, see 186 Configuring RAN
Sharing Introduction Package.
For information on verifying the Iu Flex feature, see 227 Configuring Iu Flex.
For information on verifying the Cell Broadcast Service feature, see 70 Configuring Cell
Broadcast Service.
Issue 06 (2013-03-25)

635
RAN14.0
For information on verifying the RAN Sharing feature, see 186 Configuring RAN Sharing
l
For information on deactivating the Iu Flex feature, see 227 Configuring Iu Flex.
For information on deactivating the Cell Broadcast Service feature, see 70 Configuring
For information on deactivating the RAN Sharing feature, see 186 Configuring RAN
Sharing Introduction Package.
----End
Issue 06 (2013-03-25)

636
RAN14.0
189 Configuring Mobility Control and Service

Differentiation
189
Configuring Mobility Control and

Service Differentiation
WRFD02130403 Mobility Control and Service Differentiation.
Prerequisites
l

feature depends on the feature WRFD-021304 RAN Sharing Introduction Package.
License
Context
This feature supports the configuration of different service support for multiple operators to meet
their individual requirements.
Procedure
l
1.

not supported) to set the parameter RAN Sharing Support to YES. Then, set the
parameters Intra RAT Inter Plmn Ho Allowed and Inter RAT Inter Plmn Ho
Allowed to YES.
The cells that belong to different operators can be configured as intra-frequency, interfrequency, or inter-RAT neighboring cells.
Issue 06 (2013-03-25)

637
RAN14.0
189 Configuring Mobility Control and Service

Differentiation
1.

not supported) to set the parameter RAN Sharing Support to YES. Then, set the
parameters Intra RAT Inter Plmn Ho Allowed and Inter RAT Inter Plmn Ho
Allowed to NO.
----End
Example
//Activating Mobility Control and Service Differentiation
InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES;
//Deactivating Mobility Control and Service Differentiation
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
Issue 06 (2013-03-25)

638
RAN14.0
190
Configuring Independent License

Control
WRFD-02130404 Independent License Control. (This feature cannot be configured using the
CME. )
Prerequisites
l

The feature WRFD-021304 RAN Sharing Introduction Package has been configured
License
Context
This feature enables operators to have their own network capacity and optional features, thereby
meeting different service and operation requirements.
Procedure
l
1.
Run the BSC6900 MML command SET LICENSE to configure a license for the
primary operator.
2.
Run the BSC6900 MML command SET LICENSE to configure a license for the
secondary operator.
l
Issue 06 (2013-03-25)
639
RAN14.0

----End
Example
//Activating Independent License Control
CsErlang=30000, FUNCTIONSWITCH1=PDCP-1;
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=NO, CNOPERATORINDEX=1,
CsErlang=20000;
Issue 06 (2013-03-25)

640
RAN14.0
191 Configuring RAN Sharing Phase 2
191
Configuring RAN Sharing Phase 2
RAN Sharing Phase 2.
Prerequisites
l

The features WRFD-021304 RAN Sharing Introduction Package must be configured
License
Context
This feature provides independent Iub transmission resource management for multiple telecom
operators to ensure the QoS of their respective users.
Procedure
l
For information on activating this feature, see 192 Configuring Dedicated Iub
Transmission Control.
----End
Issue 06 (2013-03-25)

641
RAN14.0
192
Configuring Dedicated Iub

Transmission Control
WRFD-02130501 Dedicated Iub Transmission Control.
Prerequisites
l

The configurations of the other features, on which this feature depends, are complete.
The feature WRFD-021304 RAN Sharing Introduction Package has been activated.
License
Context
This feature provides separate admission control policies for operators that share the same port,
thereby ensuring the basic bandwidth available for each operator and improving bandwidth
efficiency when the Iub resources are idle.
Procedure
l
Activating Dedicated Iub Transmission Control in ATM mode
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD OPSEPINFO (CME single

Resources Configuration > Separate Information for Operators; CME batch
modification center: not supported) to add the separate information for operators,
including the bandwidth admission ratio and load thresholds for each operator, and
set Transport Type to ATM.

642
RAN14.0

NOTE
This feature can be enabled for one to four operators as required. The bandwidth ratios and load
thresholds for these operators need to be separately configured. Note that the sum of the
bandwidth ratios for all valid operators must be 100%.
2.
Run the BSC6900 MML command ADD FRALNK (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > Fractional
ATM Link; CME batch modification center: not supported), ADD UNILNK
(CME single configuration: NodeB Configuration Express > IUB_RNC > ATM
Transport > UNI Link; CME batch modification center: not supported), or ADD
IMAGRP (CME single configuration: NodeB Configuration Express >
IUB_RNC > ATM Transport > IMA Group; CME batch modification center:
not supported) to add a physical port. Set Operator Separated Flag to ON
(ON). In addition, on the links carried on the physical port, set Index of Separate
Information for Operators.
3.
Run the BSC6900 MML command ADD UNODEB (CME single configuration:
Main View > Right Click RNC > Create Logical NodeB; CME batch
modification center: not supported) to add a NodeB. In this step, set Sharing Type
Of NodeB to RANSHARING(RAN Sharing).
4.
Node; CME batch modification center: not supported) to add an adjacent node.
5.

configuration: NodeB Configuration Express > IUB_RNC > ATM Transport
> AAL2 Path; CME batch modification center: not supported) to add an AAL2
path.
6.
Run the BSC6900 MML command ADD TRMMAP (CME single configuration:
UMTS Global Configuration Express > Transmission Resources
Configuration > Transport Resource Mapping; CME batch modification
center: not supported) to add a TRM mapping table.
NOTE
The BSC6900 provides a default TRM mapping table. This step is executed only when different
TRM mapping policies are required.
Activating Dedicated Iub Transmission Control in IP mode

1.
Run the BSC6900 MML command ADD OPSEPINFO (CME single

Resources Configuration > Separate Information for Operators; CME batch
modification center: not supported) to add the separate information for operators,
including the bandwidth admission ratio and load thresholds for each operator, and
set Transport Type to IP(IP).
NOTE
This feature can be enabled for one to four operators as required. The bandwidth ratios and load
thresholds for these operators need to be separately configured. Note that the sum of the
bandwidth ratios for all valid operators must be 100%.
2.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD PPPLNK (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > PPP Link; CME
batch modification center: not supported) or ADD MPGRP (CME single
configuration: NodeB Configuration Express > IUB_RNC > IP Transport >
MP Group; CME batch modification center: not supported) to add a physical port,
or run the BSC6900 MML command ADD IPLOGICPORT (CME single
643
RAN14.0
IP Logical Port; CME batch modification center: not supported) to add a logical
port. Set Operator Separated Flag to ON(ON), and set Index of Separate
Information for Operators on the links carried on the physical port.
NOTE
If this feature is activated on the physical port, this feature is only enabled on the physical port.
If this feature is activated on the logical port, this feature is only enabled on the logical port. You
can enable this feature on both the physical port and logical port based on the network plan.
3.
modification center: not supported) to add a NodeB. In this step, set Sharing Type
Of NodeB to RANSHARING(RAN Sharing).
4.
Node; CME batch modification center: not supported) to add an adjacent node.
5.
Run the BSC6900 MML command ADD IPPATH (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > IP Path; CME
batch modification center: not supported) to add an IP path.
6.
UMTS Global Configuration Express > Transmission Resources
Configuration > Transport Resource Mapping; CME batch modification
center: not supported) to add a TRM mapping table.
NOTE
The BSC6900 provides a default TRM mapping table. This step is executed only when different
TRM mapping policies are required.
7.
Run the BSC6900 MML command ADD ADJMAP (CME single configuration:
Node Mapping; CME batch modification center: not supported) to add the TRM
mapping to the adjacent node. In this step, set Resource Management Mode to
SHARE(Sharing) or EXCLUSIVE(EXCLUSIVE). If you set Resource
Management Mode to EXCLUSIVE(EXCLUSIVE), you are advised to add a
TRM mapping to the adjacent node for each operator. Otherwise, the operator
cannot admit services.
Assume that networks of operators A and B are enabled with the RAN sharing feature.
1.
Choose Monitor > Transport Resource RealTime Monitoring on the LMT. Specify
the parameters related to the physical port that is shared by operators A and B and
specify operator indexes. Then, check whether the bandwidth occupied by each
operator meets the conditions specified by the predefined bandwidth ratio parameters.
NOTE
The verification procedures for this feature are the same for the ATM mode and IP mode.
Deactivating Dedicated Iub Transmission Control in ATM mode
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD FRALNK (CME single configuration:
ATM Link; CME batch modification center: not supported), MOD UNILNK
(CME single configuration: NodeB Configuration Express > IUB_RNC > ATM
Transport > UNI Link; CME batch modification center: not supported), or MOD
IMAGRP (CME single configuration: NodeB Configuration Express >
644
RAN14.0
IUB_RNC > ATM Transport > IMA Group; CME batch modification center:
not supported) as required. In this step, set Operator Separated Flag to OFF
(OFF).
Deactivating Dedicated Iub Transmission Control in IP mode
1.
If a physical port is added, run the BSC6900 MML command MOD PPPLNK
(CME single configuration: NodeB Configuration Express > IUB_RNC > IP
Transport > PPP Link; CME batch modification center: not supported) or MOD
MPGRP (CME single configuration: NodeB Configuration Express >
IUB_RNC > IP Transport > MP Group; CME batch modification center: not
supported) to set Operator Separated Flag to OFF(OFF); if a logical port is
added, run the BSC6900 MML command MOD IPLOGICPORT (CME single
IP Logical Port; CME batch modification center: not supported) to set Operator
Separated Flag to OFF(OFF).
----End
Example
Activate Dedicated Iub Transmission Control in ATM mode
ADD OPSEPINFO: OPSEPINDEX=0, OPCOUNT=TWO, TYPE=ATM, OPINDEX1=0,
BWRATIO1=40, OPINDEX2=3, BWRATIO2=60;
ADD IMAGRP: SRN=0, SN=26, BT=AEUa, IMAGRPN=0, FLOWCTRLSWITCH=ON,
OPSEPFLAG=ON, OPSEPINDEX=0;
ADD UNODEB: NodeBName="NodeB1", NodeBId=1, SRN=0, SN=0, SSN=1,
TnlBearerType=ATM_TRANS, HostType=SINGLEHOST, SharingType=RANSHARING;
ADD ADJNODE: ANI=1, NAME="NodeB1", NODET=IUB, NODEBID=1, TRANST=ATM,
IsROOTNODE=YES, SAALLNKN=20;
ADD AAL2PATH: ANI=1, PATHID=10, CARRYT=ATMLOGICPORT, CARRYF=0,
CARRYSN=26, CARRYVPN=10, VPI=2, VCI=50, TXTRFX=111, RXTRFX=111,
AAL2PATHT=SHARE;
ADD TRMMAP: TMI=14, ITFT=IUB, TRANST=ATM; ADD ADJMAP: ANI=1, ITFT=IUB,
TRANST=ATM, CNMNGMODE=SHARE, TMIGLD=14, TMISLV=14, TMIBRZ=14, FTI=0;
Activate Dedicated Iub Transmission Control in IP mode
ADD OPSEPINFO: OPSEPINDEX=0, OPCOUNT=TWO, TYPE=IP, OPINDEX1=0,
BWRATIO1=40, OPINDEX2=3, BWRATIO2=60; ADD MPGRP: SRN=0, SN=26,
BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=0, MPTYPE=MCPPP, BORROWDEVIP=NO,
LOCALIP="11.11.11.12", MASK="255.255.255.0", PEERIP="11.11.11.13",
MHF=LONG, PPPMUX=Disable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V,
ERRDETECTSW=OFF, ANTIERRFLAG=OFF, OPSEPFLAG=ON, OPSEPINDEX=0;
ADD UNODEB: NodeBName="NodeB1", NodeBId=1, SRN=0, SN=0, SSN=1,
TnlBearerType=IP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT,
HostType=SINGLEHOST, SharingType=RANSHARING;
ADD ADJNODE: ANI=1, NAME="NodeB1", NODET=IUB, NODEBID=1, TRANST=IP;
ADD IPPATH: ANI=1, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="11.11.11.12", PEERIPADDR="11.11.11.13", TXBW=10000, RXBW=10000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
ADD TRMMAP: TMI=14, ITFT=IUB, TRANST=IP;
Deactivate Dedicated Iub Transmission Control in ATM mode
MOD IMAGRP: SRN=0, SN=26, BT=AEUa, IMAGRPN=0, OPSEPFLAG=OFF;
Deactivate Dedicated Iub Transmission Control in IP mode
Issue 06 (2013-03-25)

645
RAN14.0
MOD MPGRP: SRN=0, SN=26, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=0,

OPSEPFLAG=OFF;
Issue 06 (2013-03-25)

646
RAN14.0
193
Configuring IMSI Based Handover
IMSI Based Handover.
Prerequisites
l

The feature WRFD-021304 RAN Sharing Introduction Package must be configured
License
Context
With this feature, configuring SNA-related information on the RNC is supported. This enables
the UTRAN to limit UE mobility when the CN does not support the shared network area (SNA)
function.
Procedure
l
Issue 06 (2013-03-25)
1.

RNCAP_IMSI_HO_SWITCH check box under the parameter
PROCESSSWITCH.
2.
Run the BSC6900 MML command ADD ULASNAMAP (CME single configuration:
Mapping of LAC to SNA; CME batch modification center: not supported). In this
step, set PLMN to 46000, LAC to 1234, and SNAC to 1.
3.
Run the BSC6900 MML command ADD UIMSISNAMAP (CME single

configuration: UMTS Global Configuration Express > Radio Basic Data
647
RAN14.0
Configuration > Mapping of IMSI to SNA; CME batch modification center: not
supported) to add an IMSI-to-SNA mapping relationship. In this step, set The start of
IMSI to 460071234000000, The end of IMSI to 460071234500000, PLMN to 46000,
and SNAC to 1.
l
1.
Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of
H'1234. The UE is admitted to the cell.
2.
Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of
H'1235. The UE is rejected by the cell. In this case, you can view the RRC
CONNECTION REJECT message on the Uu interface.
NOTE
The restrictions on cell update, UTRAN registration area (URA) update, handovers,
relocations, and handling COMMON ID messages are the same as that on RRC connection
request.
1.
Run the BSC6900 MML command RMV ULASNAMAP (CME single

Configuration > Mapping of LAC to SNA; CME batch modification center: not
supported) to remove a mapping relationship between LAC and SNA.
2.
Run the BSC6900 MML command RMV UIMSISNAMAP (CME single

Configuration > Mapping of IMSI to SNA; CME batch modification center: not
supported) to remove a mapping relationship between IMSI and SNA.
----End
Example
//Activating IMSI-Based Handover
//Enabling IMSI Handover
SET URRCTRLSWITCH: PROCESSSWITCH=RNCAP_IMSI_HO_SWITCH-1;
//Adding PLMN, LAN, and SNAC
ADD ULASNAMAP: MCC="460", MNC="00", LAC=H'1234, SNAC=1;
//Adding the PLMN and SNAC of the SNA
ADD UIMSISNAMAP: ImsiMin = "460071234000000", ImsiMax =
"460071234500000", MCC="460", MNC="07", SnaExistInd=TRUE,SNAC=1;
//Deactivating IMSI-Based Handover

//Removing a mapping relationship between IMSI and SNA
RMV ULASNAMAP: MCC="460", MNC="00", LAC=1234, SNAC=1;
//Removing a mapping relationship between IMSI and SNA
RMV UIMSISNAMAP: ImsiMin="460071234000000", ImsiMax="460071234500000",
MCC="460", MNC="07", SnaExistInd=TRUE, SNAC=1;
Issue 06 (2013-03-25)

648
RAN14.0
194
Configuring MOCN Introduction

Package
MOCN Introduction Package. (This feature cannot be configured using the CME. )
Prerequisites
l

This feature cannot be used together with the feature WRFD-021304 RAN Sharing
License
Context
Multi-Operator Core Network (MOCN) was introduced in 3GPP Release 6. It enables multiple
operators to share the network and therefore reduces the CAPEX and OPEX.
The MOCN feature has no requirement for the RNC, NodeB, and UE hardware. It is applicable
to all categories of UEs.
For details about MOCN, see 3GPP TS 23.251.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD UCNOPERATOR to add a primary

operator. In this step, set Cn Operator Name, MCC, MNC, and Cn Operator
Index to appropriate values.
2.
Run the BSC6900 MML command ADD UCNOPERATOR to add a secondary

operator. In this step, set Cn Operator Name, MCC, MNC, and Cn Operator
Index to appropriate values.
649
RAN14.0
3.
Run the BSC6900 MML command SET LICENSE to activate the license for the
primary operator.
4.
Run the BSC6900 MML command SET LICENSE to activate the license for the
secondary operator.
5.
Run the BSC6900 MML command ADD UCNOPERATOR to add a common

operator.
NOTE
If the MOCN operator has applied for a new PLMN, a common operator needs to be configured.
If the MOCN operator does not apply for a new PLMN, a common operator does not need to
be configured.
6.
Run the BSC6900 MML command ADD UCNOPERGROUP to add an operator

group.
NOTE
When no common operator is configured, set the common operator index (CnOpIndex1) of the
operator group to the default value 255.
7.
Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set

the sharing mode for the operators. Set RAN Sharing Support to NO. Set MOCN
Support to YES. Set Intra RAT Inter Plmn Ho Allowed, Inter RAT Inter Plmn
Ho Allowed, Default CnOperator, and Mocn Control Switch to appropriate values
8.
Run the BSC6900 MML command SET UOPERATORCFGPARA to set

parameters for the primary operator.
9.
Run the BSC6900 MML command SET UOPERATORCFGPARA to set

parameters for the secondary operator.
10. Configure Iu interface transmission data between the BSC6900 and the primary and
secondary operators' CNs by referring to Configuring Interface Data.
11. Run the BSC6900 MML command ADD UCNNODE to add a CN node for the
primary operator.
12. Run the BSC6900 MML command ADD UCNNODE to add a CN node for the
secondary operator.
13. Run the BSC6900 MML command ADD UNRIGLBCNIDMAP to add a mapping
between Network Resource Identifiers (NRIs) and CN nodes.
NOTE
The mapping between NRIs and CN nodes needs to be configured based on the network plan.
If a CN node is configured with multiple NRIs, repeat this step until all the required mapping
relationships are configured.
14. Run the BSC6900 MML command ADD UNODEB to add an MOCN NodeB. In this
step, set Sharing Type Of NodeB to MOCN and set other parameters based on the
network plan.
15. (Optional) Run the BSC6900 MML command ADD UNODEB to add a dedicated
NodeB.
16. Configure the area information by referring to Configuring the Area Information.
NOTE
Location areas must be the same for the primary and secondary operators.
17. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add an MOCN
cell.
Issue 06 (2013-03-25)

650
RAN14.0

NOTE
A cell is a dedicated cell if its operator group is configured with only one operator.
18. Run the BSC6900 MML command ADD UEXT3GCELL to add a neighboring RNC
cell.
l
1.
Register supporting UEs and non-supporting UEs in MOCN cells of the primary and
secondary operators. The UEs are registered successfully and properly initiate CS and
PS services.
NOTE
The MOCN network has two types of UEs:

l Supporting UE: supports the MOCN feature. In an MOCN network, the RNC broadcasts the
PLMNs of the operators through system information messages (the Multiple-PLMN list IE).
Supporting UEs interpret such PLMN information or notify the RNC of their selected PLMNs
through initial direct transfer messages. Supporting UEs support 3GPP Release 6.
l Non-supporting UE: does not support the MOCN feature. Non-supporting UEs cannot interpret
the PLMN information in system information messages.
1.
Run the BSC6900 MML command RMV UCELL to remove the MOCN cell.
2.
Add a cell not enabled with the MOCN feature by referring to Configuring the Cell
Data.
NOTE
Deactivating the MOCN feature interrupts services. Therefore, perform the deactivation operations
early in the morning when the traffic is light.
----End
Example
//Configuring MOCN Introduction Package
ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PrimOp", MCC="302",
ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SecOp", MCC="302",
//Adding a common operator
ADD UCNOPERATOR: OperatorType=COMM, CnOperatorName="Common", MCC="302",
//Activating the license for the primary operator
FUNCTIONSWITCH2=ENHANCEDIUFLEX-1, FUNCTIONSWITCH4=MOCN_PACKAGE-1;
//Activating the license for the secondary operator
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=NO, CNOPERATORINDEX=1,
FUNCTIONSWITCH2=ENHANCEDIUFLEX-1, FUNCTIONSWITCH4=MOCN_PACKAGE-1;
//Adding an operator group
ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="ShareCnOpGrp",
CnOpNum=TWO, CnOpIndex1=0, CnOpIndex2=1, CnOpIndexComm=5;
Issue 06 (2013-03-25)

651
RAN14.0

SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES,
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO,
DefaultCnOp=255,
MocnControlSwitch=COMM_MOCN_NRI_GLOBAL_CONFIG_MODE_SWITCH-1&COMM_MIB_MULT
I_PLMN_LIST_ALLOWED_SWITCH-1;
//Setting parameters for the primary operator
SET UOPERATORCFGPARA: CnOpIndex=0, CsNriCfgMode=SUPP_IUFLEX_MOCN,
PsNriCfgMode=SUPP_IUFLEX_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=0;
//Setting parameters for the secondary operator
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX_MOCN,
PsNriCfgMode=SUPP_IUFLEX_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=1;
//Adding CN node 10 for the primary operator
CNProtclVer=R5, SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL,
AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF,
//Adding CN node 20 for the primary operator
//Adding CN node 11 for the secondary operator
//Adding CN node 21 for the secondary operator
//Adding the mapping between CN node 10 and an NRI for the primary
operator
ADD UNRIGLBCNIDMAP: CnOpIndex=0, CNId=10, NRI=10;
//Adding the mapping between CN node 20 and an NRI for the primary
operator
//Adding the mapping between CN node 11 and an NRI for the secondary
operator
//Adding the 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=SUPPORT, HostType=SINGLEHOST,
SharingType=MOCN;
//Adding a dedicated NodeB
ADD UNODEB: NodeBName="NodeB2", NodeBId=2, SRN=0, SN=0,
Issue 06 (2013-03-25)

652
RAN14.0
TnlBearerType=IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST,

SharingType=DEDICATED, CnOpIndex=0;
//Adding a location area for the primary operator
ADD ULAC:CNOPINDEX=0, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256;
//Adding a location area for the secondary operator
ADD ULAC:CNOPINDEX=1, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256;
//Adding an MOCN cell
ADD UCELLQUICKSETUP: CellId=1, CellName="Cell1", PeerIsValid=INVALID,
CnOpGrpIndex=0, BandInd=Band1, UARFCNDownlink=10562, PScrambCode=0,
TCell=CHIP256, LAC=H'2501, SAC=H'0000, CfgRacInd=REQUIRE, RAC=H'00,
SpgId=6, URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6,
URA7=7, URA8=8, NodeBName="NodeB1", LoCell=0, SupBmc=FALSE;
//Adding a neighboring RNC cell
ADD UEXT3GCELL: NRncId=RNC1, CellId=1, CellHostType=SINGLE_HOST,
CellName="Cell1", CnOpGrpIndex=0, PScrambCode=0, BandInd=Band1,
TxDiversityInd=FALSE, LAC=h'2506, CfgRacInd=NOT_REQUIRE,
QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE,
UseOfHcs=NOT_USED, CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE;
//Deactivating MOCN Introduction Package

//Removing an MOCN cell
//Adding a cell not enabled with the MOCN feature
Issue 06 (2013-03-25)

653
RAN14.0
195
Configuring Carrier Sharing by

Operators
Prerequisites
l

The feature WRFD-021311 MOCN Introduction Package has been configured before
License
Others
The CN supports the MOCN feature.
Context
This feature enables multiple operators to share the same carrier.
Procedure
l
1.
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD UCELLQUICKSETUP (CME single

configuration: Main View > Right click NodeB > Add UMTS Cell; CME batch
modification center: not supported) to add an MOCN cell so that multiple operators
can share the same carrier.
Check whether the MOCN introduction package is effective based on the message
traced on the Uu interface.
654
RAN14.0
If a cell is configured for only one operator, the system information message of
the cell does not contain the information element (IE) multiplePLMN-List.
If a cell is configured with multiple operators but is not configured with a common
operator, the system information message of the cell contains the PLMN of only
the first operator, and the value of the IE multiplePLMN-List is TRUE.
If a cell is configured with multiple operators and a common operator, the system
information message of the cell contains the IE multiplePLMN-List, broadcasting
all PLMNs of the MOCN cell.
As shown in Figure 195-1, the system information message broadcasts PLMN
302580 of the common operator.
As shown in Figure 195-2, the field PLMN Identity in the system information
message contains the IE multiplePLMN-List. This IE contains the PLMNs
(302221 and 302640) of two operators.
Figure 195-1 PLMN Identify field in the MIB message
The IE Multiple PLMN List contains the PLMNs (302221 and 302640) of the actual
operators.
Issue 06 (2013-03-25)

655
RAN14.0
Figure 195-2 Multiple PLMN List IE in the MIB message
1.
supported) to remove the MOCN cell.
----End
Example
//Configuring Carrier Sharing by Operators
ADD UCELLQUICKSETUP: PeerIsValid=INVALID, CnOpGrpIndex=0, LAC=H'7208,
SupBmc=FALSE;
//Deactivating Carrier Sharing by Operators
Issue 06 (2013-03-25)

656
RAN14.0
196
Configuring Dedicated NodeB/Cell

for Operators
WRFD-02131102 Dedicated NodeB/Cell for Operators.
Prerequisites
l

License
Context
This feature enables operators to independently control a NodeB or cell when the MOCN feature
is enabled.
Procedure
l
1.
Main View > Right Click RNC > Create Logical NodeB; CME batch modification
center: not supported) to add a dedicated NodeB.
2.

modification center: not supported) to add a dedicated cell.
1.
Issue 06 (2013-03-25)
Check whether this feature has been activated based on the master information block
(MIB) message traced on the Uu interface.
657
RAN14.0
As shown in Figure 196-1, the MIB message of the dedicated cell contains the operator
information (302640).
Figure 196-1 PLMN Identify IE in the MIB message
1.
supported) to remove the dedicated cell.
2.
NodeB; CME batch modification center: not supported) to change a dedicated NodeB
into a shared NodeB.
3.

modification center: not supported) to add a shared cell.
----End
Example
//Activating Dedicated NodeB/Cell for Operators
Issue 06 (2013-03-25)

658
RAN14.0
//Adding a dedicated NodeB

ADD UNODEB: NodeBName="1", NodeBId=1, SRN=0, SN=0,
TnlBearerType=ATM_TRANS, HostType=SINGLEHOST, SharingType=DEDICATED,
CnOpIndex=0;
//Adding a dedicated cell
ADD UCELLQUICKSETUP: CellId=1, CellName="1", PeerIsValid=INVALID,
TCell=CHIP0, LAC=1, SAC=0, CfgRacInd=NOT_REQUIRE, SpgId=1, URANUM=D1,
URA1=0, NodeBName="1", LoCell=1, SupBmc=FALSE;
//Deactivating Dedicated NodeB/Cell for Operators
//Removing a dedicated cell
//Changing a dedicated NodeB into a shared NodeB
MOD UNODEB: NodeBId=1, SharingType=MOCN;
//Adding a shared cell
ADD UCELLQUICKSETUP: CellId=1, CellName="1", PeerIsValid=INVALID,
URA1=0, NodeBName="1", LoCell=1, SupBmc=FALSE;
Issue 06 (2013-03-25)

659
RAN14.0
197
Configuring MOCN Mobility

Management
WRFD-02131103 MOCN Mobility Management.
Prerequisites
l

License
Context
This feature is applicable to different MOCN mobility strategies. This feature enables the
BSC6900 to determine whether to hand over a UE to a target cell based on the ID of the operator
to which the UE belongs and the PLMN ID of the target cell.
By default, the BSC6900 allows inter-RAT cross-PLMN handovers. You can prohibit this type
of handover by running the command SET UOPERATORSHARINGMODE (CME single
configuration: UMTS Global Configuration Express > Operator Configuration > RNC
Operators Sharing Mode; CME batch modification center: not supported).
Procedure
l
1.
Issue 06 (2013-03-25)

not supported). In this step, set MOCN Support, Intra RAT Inter Plmn Ho
Allowed, and Inter RAT Inter Plmn Ho Allowed to YES.
660
RAN14.0
1.
When the cross-PLMN handover switch is turned on, check whether UEs can perform
cross-PLMN handovers, relocations, and cell updates. If UEs can perform crossPLMN handovers, relocations, and cell updates, this feature has been activated.
1.

not supported). In this step, set MOCN Support to YES, Intra RAT Inter Plmn Ho
Allowed to NO, and Inter RAT Inter Plmn Ho Allowed to NO.
----End
Example
//Activating MOCN Mobility Management
InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES;
//Deactivating MOCN Mobility Management
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
Issue 06 (2013-03-25)

661
RAN14.0
198
Configuring MOCN Load Balance
WRFD-02131104 MOCN Load Balance.
Prerequisites
l

License
Context
This feature enables multiple operators to achieve load balance and network fairness.
Procedure
l
1.

not supported). In this step, set MOCN Support to YES.
NOTE
In this step, set Default CnOperator to 255. The BSC6900 selects operators in Round Robin
mode.
1.
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command LST UOPERATORSHARINGMODE to query

the parameter settings of the feature MOCN Load Balance.
662
RAN14.0
not supported). In this step, set MOCN Support to YES and Default CnOperator
to 0. The BSC6900 preferentially selects the default operator (operator 0).
----End
Example
//Activating MOCN Load Balance
SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=255;
//Deactivating MOCN Load Balance
SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=0;
Issue 06 (2013-03-25)

663
RAN14.0
199
Configuring Routing Roaming UEs

in Proportion
WRFD-02131106 Routing Roaming UEs in Proportion.
Prerequisites
l

License
Others
The CN supports this feature. During initial registration of a roaming UE, the UE selects
the same operator for CS and PS services, and the IMSI is carried to the RNC.
Context
When roaming UEs of one operator move to the area served by the RNC that is shared among
multiple operators using the Multi-Operator Core Network (MOCN), the RNC routes the UEs
to CN nodes that belong to different operators according to the preset ratio if the UEs are under
the roaming agreement with these operators.
Procedure
l
NOTE
Assume that operator1 and operator2 share the same RNC by using the MOCN and operator A signs
a roaming agreement with the two operators.
1.
Issue 06 (2013-03-25)
To add operator A to the roaming relation list of operator1, run the BSC6900 MML
command ADD UROAMMAP (CME single configuration: UMTS Global
664
RAN14.0
Configuration Express > Operator Configuration > UROAM MAP; CME batch
modification center: not supported). In this step, set MCC for operator A to 460,
MNC to 09, Cn Operator Index for operator1 to 1, Cn Operator Group Index for
operator1 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 relation list of operator2, run the BSC6900 MML
command ADD UROAMMAP (CME single configuration: UMTS Global
Configuration Express > Operator Configuration > UROAM MAP; CME batch
modification center: not supported). In this step, set Cn Operator Index for operator2
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.
NOTE
After the parameter settings are complete, the UEs that belong to operator A are distributed to
operator1 and operator2 according to the preset ratio (30:70).
If operator B also signs a roaming agreement with operator1 and operator2, 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 relation lists of the two operators.
1.
Run the BSC6900 MML command LST UROAMMAP to query the roaming
capacity of operator A. Expected result: Capability of Roaming Operator for
operator1 is set to 30, and Capability of Roaming Operator for operator2 is set to
70.
2.
When UEs belonging to operator A roam to the RNC shared by operator1 and
operator2 by using the MOCN for a long measurement period, view the performance
counter VS.ROAM.MOCN.NUM on the M2000. Expected result: The roaming UEs
of operator A are routed to CN nodes of operator1 and operator2 in a preset proportion
of 30:70.
NOTE
UEs of the non-supporting UE type do not support network sharing, as defined in the feature
This feature is not applicable to UEs of the supporting UE type (supporting network sharing).
1.
Run the BSC6900 MML command RMV UROAMMAP (CME single configuration:
UMTS Global Configuration Express > Operator Configuration > UROAM
MAP; CME batch modification center: not supported) to remove operator A from the
roaming relation list of operator1.
2.
Run the BSC6900 MML command RMV UROAMMAP (CME single configuration:
UMTS Global Configuration Express > Operator Configuration > UROAM
MAP; CME batch modification center: not supported) to remove operator A from the
roaming relation list of operator2.
----End
Example
/*Activating Routing Roaming UEs in Proportion*/
//Adding operator A serving roaming UEs to the roaming relation list of
operator1
ADD UROAMMAP: MCC="460", MNC="09", CnOpIndex=1, CnOpGrpIndex =
1,AvailRoamCap =30;
Issue 06 (2013-03-25)

665
RAN14.0
//Adding operator A serving roaming UEs to the roaming relation list of

operator2
ADD UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex =
1,AvailRoamCap =70;
/*Deactivating Routing Roaming UEs in Proportion*/
//Removing operator A serving roaming UEs from the roaming relation list
of operator1
RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=1, CnOpGrpIndex = 1;
//Removing operator A serving roaming UEs from the roaming relation list
of operator2
RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex = 1;
Issue 06 (2013-03-25)

666
RAN14.0
200
Configuring MOCN Cell Resource

Demarcation
MOCN Cell Resource Demarcation.
Prerequisites
l
Only the 3900 series base stations configured with the WBBPb, WBBPd, or WBBPf
board support this feature.

The feature WRFD-021311 MOCN Introduction Package must be configured before
License
Context
This feature provides a mechanism for predefining the percentage of cell resources available to
UEs of each operator involved in the MOCN cell. This feature helps prevent the UEs of an
operator from occupying excessive cell resources.
If the MOCN cell has idle resources, the UEs of each operator can use more resources than their
predefined resource percentage. If the MOCN cell is congested, the RNC performs preemption
and congestion control on the operator whose actual resource percentage has exceeded the
predefined value. By doing so, the RNC keeps resource usage of each operator in the MOCN
cell during busy hours close to their respective predefined resource percentage.
You are not advised to use this feature with WRFD-010696 DC-HSDPA. That is because
enabling DC-HSDPA affects power measurement accuracy.
l
Precautions
None
l
Issue 06 (2013-03-25)
Data Preparation
667
RAN14.0
Scenario 1: Using cell resources based on the HSDPA power percentages for MOCNenabled operators in a cell
Parameter Name
Parameter ID
Setting
Description
Source
Iub Private
Interface Switch
IubPrivateInterfaceSwitch
PSCRR_OpInde
x_INCLUDED
and
RL_OpIndex_IN
CLUDED should
be selected.
Network plan
Cell CAC
algorithm switch
NBMCacAlgoSwi
tch
HSDPA_GBP_M
EAS should be
selected.
Network plan
Non-HSPA Power
Threshold for
GBP-based
Preemption
NonHPwrForGBP
Preemp
Use the
recommended
value.
Network plan
Cell ID
CellId
This parameter
should be set
according to the
network plan.
Network plan
CN Operator index
CnOpIndex
This parameter
should be set
according to the
network plan.
Network plan
HSDPA Power
Availability
Percentage
DPAAvaiPwrRati
o
Use the
recommended
value.
Network plan
Demarcation
Preemption Switch
DemarcPreemptSwitch
MOCN_DEMAR
C_PREEMPT_G
BP should be
selected.
Network plan
Function Switch1
FuncSwitch1
CELL_MOCN_
DEMARCATIO
N_SWITCH
should be selected.
Network plan
Resource Allocate
Method
RSCALLOCM
Set this parameter

to
POWERCODE_
BAL.
Network plan
Scenario 2: Using cell resources based on the R99 SF percentages for MOCN-enabled
operators in a cell
Issue 06 (2013-03-25)

668
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Cell ID
CellId
This parameter
should be set
according to the
network plan.
Network plan
CN Operator index
CnOpIndex
This parameter
should be set
according to the
network plan.
Network plan
DL R99 SF
Availability
Percentage
DLAvaiSFRatio
Use the
recommended
value.
Network plan
Demarcation
Preemption Switch
DemarcPreemptSwitch
MOCN_DEMAR
C_PREEMPT_S
F should be
selected.
Network plan
Switch for Cell

Load Control
NBMLdcAlgoSwi
tch
CELL_CODE_L
DR should be
selected.
Network plan
R99 SC LDR User

Selection
NbmSFLdcUeSel
Switch
NBM_SF_LDC_
DEMARC should
be selected.
Network plan
Function Switch1
FuncSwitch1
CELL_MOCN_
DEMARCATIO
N_SWITCH
should be selected.
Network plan
Resource Allocate
Method
RSCALLOCM
Set this parameter

to
POWERCODE_
BAL.
Network plan
Procedure
l
Configuration on the RNC side
Using cell resources based on the HSDPA power percentages for MOCN-enabled
operators in a cell
1.
Issue 06 (2013-03-25)

PSCRR_OpIndex_INCLUDED (Switch for carrying operator indexes in the
PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST
669
RAN14.0
message) under Iub Private Interface Switch to enable the Physical Shared
Channel Reconfiguration Request message to carry the operator index.
2.

RL_OpIndex_INCLUDED (Switch for carrying operator indexes in the
RADIO LINK message) under Iub Private Interface Switch to enable the Radio
Link Setup Request message to carry the operator index.
3.

Cell Parameters in Batches). 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 a neighboring RNC exists, Run the BSC6900 MML command MOD
UNRNC (CME single configuration: IUR Configuration Express >
Neighbouring RNC > Neighboring RNC; CME batch modification center: not
supported). In this step, select PLMNID_INCLUDED (Switch for Carrying
PLMN ID) under Iur Private Interface Switch to turn on the Iur-interface
proprietary IE switch with PLMN ID included.
5.

Modifying UMTS Cell Parameters in Batches). In this step, set Non-HSPA
Power Threshold for GBP-based Preemption to according to the network plan.
6.
Run the BSC6900 MML command ADD

UCELLMOCNDPAPOWERDEMAR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell-Oriented Operator HSDPA
Power Availability Percentage Parameters; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches). In this step, set Cell
Index, Cn Operator Index, and HSDPA Power Availability Percentage to
configure the HSDPA power percentage for an operator of an operator group in a
cell.
7.

Cell Parameters in Batches). In this step, select
MOCN_DEMARC_PREEMPT_GBP under Demarcation Preemption
Switch to enable preemption based on HSDPA power percentages of operators in
a cell.
8.
Run the BSC6900 MML command ADD UCELLLICENSE (CME single

License Resource/Function Item; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches). 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.
Using cell resources based on the R99 SF percentages for MOCN-enabled operators in
a cell
Issue 06 (2013-03-25)

670
RAN14.0
1.
Run the BSC6900 MML command ADD UCELLMOCNSFDEMAR (CME

single configuration: UMTS Cell Configuration Express > Cell Parameters >
Cell-Oriented Operator DL R99 SF Availability Percentage Parameters;
Batches). In this step, set Cell Index, Cn Operator Index, and DL R99 SC
Availability Percentage.
2.

Cell Parameters in Batches). In this step, select
MOCN_DEMARC_PREEMPT_SF under Demarcation Preemption Switch
to enable preemption based on R99 SF percentages of operators in a cell.
3.

Cell Parameters in Batches). In this step, select CELL_CODE_LDR(Code
LDR Algorithm) under Switch for Cell Load Control to enable the cell-level
code LDR algorithm.
4.

Cell Parameters in Batches). In this step, select 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.

License Resource/Function Item; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches). In this step, select
Switch) under Function Switch1 to activate the license for MOCN Cell Resource
Configuration on the NodeB side

1.
3.17 Modifying Physical NodeB Parameters in Batches).In this step, set Resource
Allocate Method to POWERCODE_BAL(Balance between Code and Power).
operators in a cell
1.
Start the Iub-interface message tracing task. Check whether the

NBAP_PHY_SHARED_CH_RECFG_REQ message carries the mOCNOperator-Hsdpa-Operator-Index-private IE and the mOCN-Operator-Hsdpa-PwrRatio-private IE. If yes, the feature based on the HSDPA power percentage has
been activated.
Using cell resources based on the R99 SF percentages for MOCN-enabled operators in
a cell
Issue 06 (2013-03-25)

671
RAN14.0
1.
View the following counters of operators on the M2000:

VS.RAB.SFOccupy.MAX.SharedOperator0,
VS.RAB.SFOccupy.SharedOperator0,
VS.RAB.SFOccupy.SharedOperator3, VS.HSDPAPwrRatio.SharedOperator0,
VS.HSDPAPwrRatio.SharedOperator1, VS.HSDPAPwrRatio.SharedOperator2,
VS.HSDPAPwrRatio.SharedOperator3. If any value of these counters is not 0, the
feature based on the R99 SF percentage has been activated.
1.

License Resource/Function Item; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches). In this step, clear
Switch) under Function Switch1 to deactivate the license for MOCN Cell Resource
----End
Example
//Activating MOCN Cell Resource Demarcation
operators in a cell
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=1, NonHPwrForGBPPreemp=40;
ADD UCELLMOCNDPAPOWERDEMAR: CellId=1, CnOpIndex=0, DPAAvaiPwrRatio=10;
DemarcPreemptSwitch=MOCN_DEMARC_PREEMPT_GBP-1;
ADD UCELLLICENSE: CellId=1, FuncSwitch1=CELL_MOCN_DEMARCATION_SWITCH-1;
Using cell resources based on the R99 SF percentages for MOCN-enabled
operators in a cell
ADD UCELLMOCNSFDEMAR: CellId=1, CnOpIndex=0, DLAvaiSFRatio=10;
DemarcPreemptSwitch=MOCN_DEMARC_PREEMPT_SF-1;
MOD UCELLALGOSWITCH: CellId=1, NbmSFLdcUeSelSwitch=NBM_SF_LDC_DEMARC;
ADD UCELLLICENSE: CellId=1, FuncSwitch1=CELL_MOCN_DEMARCATION_SWITCH-1;
SET MACHSPARA: LOCELL=0, RSCALLOCM=POWERCODE_BAL;
//Deactivating MOCN Cell Resource Demarcation
MOD UCELLLICENSE: FuncSwitch1=CELL_MOCN_DEMARCATION_SWITCH-0;
Issue 06 (2013-03-25)

672
RAN14.0
201
Configuring HCS (Hierarchical Cell

Structure)
HCS (Hierarchical Cell Structure).
Prerequisites
l

License
Context
Based on speed estimation, the BSC6900 hands over fast-moving UEs to low-priority cells to
reduce the number of handovers, and hands over slow-moving UEs to high-priority cells to
increase network capacity.
Procedure
l
1.

Parameters in Batches).
In this step, set HoSwitch to the following parameter value.
HO_ALGO_HCS_SPEED_EST_SWITCH
HO_INTRA_FREQ_SOFT_HO_SWITCH
HO_INTER_FREQ_HARD_HO_SWITCH
Issue 06 (2013-03-25)

673
RAN14.0
HO_INTER_RAT_PS_OUT_SWITCH
HO_INTER_RAT_CS_OUT_SWITCH
In this step, set ReservedSwitch0 to RESERVED_SWITCH_0_BIT5.
2.
Run the BSC6900 MML command ADD UCELLHCS (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell HCS Parameters;
Batches). In this step, set Use of HCS to USED.
3.
Set the HCS parameters for different types of neighboring cells as follows:
configuration: UMTS Cell Configuration Express > Neighboring Cell > Intrafrequency Neighboring Cell; CME batch modification center: not supported) to
add an intra-frequency neighboring cell and set the HCS parameters.
Run the BSC6900 MML command ADD UINTERFREQNCELL (CME single
configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell; CME batch modification center: not supported) to
add an inter-frequency neighboring cell and set the HCS parameters.
Run the BSC6900 MML command ADD U2GNCELL (CME single
configuration: UMTS Cell Configuration Express > Neighboring Cell > GSM
Neighboring Cell; CME batch modification center: not supported) to add an interRAT GSM neighboring cell and set the HCS parameters.
Issue 06 (2013-03-25)
4.
For the cells whose HCS parameters have been set, run the BSC6900 MML
command ADD UCELLHCSHO (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented HCS Handover
Cell Parameters in Batches). In this step, set SpdEstSwitch to ON.
5.
Run the BSC6900 MML command SET UHCSHO (CME single configuration:
Configuration > RNC Oriented HCS HO Algorithm Parameters; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches) to set the RNClevel HCS parameters according to network plan.
1.
If the moving speed of a UE is higher than the fast-moving handover threshold (the
number of 1D events reported by the UE in the specified period reaches the preset
number), an inter-frequency or inter-RAT HCS handover is triggered.
2.
If the moving speed of a UE is lower than the slow-moving handover threshold (the
number of 1D events reported by the UE in the specified period is smaller than the
slow-moving handover threshold), slow-moving HCS handover measurement is
triggered, and a slow-moving inter-frequency or inter-RAT HCS handover is
performed.
3.
If a measurement-based inter-frequency or inter-RAT handover is triggered, check

whether compressed mode is started by using a RRC_PH_CH_RECFG message on
the Uu interface on the BSC6900 LMT. If compressed mode is started, this feature is
activated.
4.
If an inter-frequency blind handover is triggered, check whether the handover is

triggered by using a RRC_PH_CH_RECFG message on the Uu interface on the
BSC6900 LMT. If the handover is triggered by using the message, this feature is
activated.
674
RAN14.0
5.
If an inter-RAT blind handover is triggered, check whether 3G-to-2G handovers are

performed on the Uu and Iu interfaces on the BSC6900 LMT. If 3G-to-2G handovers
are performed, this feature is activated.
1.

HO_ALGO_HCS_SPEED_EST_SWITCH from the HoSwitch parameter.
2.
Run the BSC6900 MML command MOD UCELLHCS (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell HCS Parameters;
Batches). In this step, set Use of HCS to NOT_USED.
3.
Run the BSC6900 MML command MOD UCELLHCSHO (CME single

Oriented HCS Handover Algorithm Parameters; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches). In this step, set
SpdEstSwitch to OFF.
----End
Example
/*Activating HCS (Hierarchical Cell Structure).*/
//Set HandOver Switch
HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-1&HO_INTRA_FREQ_SOFT_HO_SWITCH-1&HO
_INTER_FREQ_HARD_HO_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1&HO_INTER_RAT_CS
_OUT_SWITCH-1, ReservedSwitch0=RESERVED_SWITCH_0_BIT5-0;
//Set HCS cell to Use of HCS
ADD UCELLHCS: CellId=11, UseOfHcs=USED;
//Add an intra-frequency neighboring cell
SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE,
TpenaltyHcsReselect=D0, NPrioFlag=FALSE;
//Add an inter-frequency neighboring cell
ADD UINTERFREQNCELL:RncId=1, CellId=11, NCellRncId=9, NCellId=100,
CIOOffset=0, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0,
HOCovPrio=1, BlindHOFlag=FALSE, NPrioFlag=FALSE;
//Add a GSM inter-RAT neighboring cell
ADD U2GNCELL: RncId=1, CellId=11, GSMCellIndex=0, CIOOffset=0,
Qoffset1sn=0, Qrxlevmin=-50, TpenaltyHcsReselect=D0, TempOffset1=D3,
BlindHoFlag=TRUE, BlindHOPrio=30, NPrioFlag=FALSE;
//Set Algorithm Switch for UE Speed Estimation
ADD UCELLHCSHO: CellId=11, SpdEstSwitch=ON;
//Deactivating HCS (Hierarchical Cell Structure).
SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-0;
MOD UCELLHCS: CellId=11, UseOfHcs=NOT_USED;
MOD UCELLHCSHO: CellId=11, SpdEstSwitch=OFF;
Issue 06 (2013-03-25)

675
RAN14.0
202
Configuring One Tunnel
One Tunnel.
Prerequisites
l

License
Others
The SGSN, GGSN and S-GW need to support the feature One Tunnel.
The control plane of the Iu-PS interface has been configured. For details in IP pool
networking, see Configuring the Control Plane of the Iu-PS Interface (over IP), For
details in IP path networking, see Configuring the Control Plane of the Iu-PS Interface
(over Transmission Resource Pool).
Context
The feature One Tunnel is available between the RNC and the GGSN and between the RNC and
the S-GW. This feature improves the efficiency of processing PS traffic and prevents the
capabilities of the SGSN from becoming the bottleneck under heavy PS traffic. The network
plan specifies which tunnel to be configured.
Issue 06 (2013-03-25)

676
RAN14.0
Figure 202-1 Networking diagram
NOTE
l In IP pool networking, you do not need to activate or deactivate this feature. Related configurations are
included in initial configuration. IP pool networking does not consider whether the peer NE is the SGSN,
GGSN, or S-GW. Instead, only an Iu-PS adjacent node needs to be configured. This operation is mandatory
in the section that describes how to configure user-plane data over the Iu-PS interface in BSC6900 UMTS
Initial Configuration Guide. For details, see Configuring the User Plane of the Iu-PS Interface (over
Transmission Resource Pool).
l In IP path networking, this feature needs to be configured. This section describes about how to activate and
deactivate this feature.
Precautions
You are advised to configure this feature during off-peak hours because configuring
this feature involves transmission mode reconfiguration which interrupts services.
Issue 06 (2013-03-25)
Data Preparation
Parameter Name
Parameter ID
Setting
Description
Source
Adjacent Node
Type
NODET
Set this parameter

to IUPS.
Network plan
Transport Type
TRANST
Set this parameter

to IP.
Network plan
SGSN FLAG
SGSNFLG
Set this parameter

to NO(GGSN or SGW).
Network plan

677
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Peer IP address
PEERIPADDR
Set this parameter

to GGSN IP address
or S-GW IP
address, and this
parameter should
not be the same as
the local address.
Network plan
Procedure
l
1.
Run the MML command ADD ADJNODE (CME single configuration: IUPS
Configuration Express > IP Transport > Adjacent Node; CME batch modification
center: not supported) to add basic information about the adjacent nodes. In this step,
set parameters as follows:
Set Adjacent Node Type to IUPS so that the node type is set to Iu PS.
Set Transport Type to IP so that the transport type is IP.
Set SGSN FLAG to NO. Depending on the configured adjacent node, set the
parameter to GGSN or S-GW.
2.
Run the MML command ADD IPPATH (CME single configuration: IUPS
Configuration Express > IP Transport > IP Path; CME batch modification center:
not supported) to add an IP path. In this step, set the PEERIPADDR parameter to the
IP address of the GGSN or S-GW.
3.
Optional: If layer 3 networking is deployed between the BSC6900 and the peer node,
run the MML command ADD IPRT (CME single configuration: IUPS
Configuration Express > IP Transport > IP Route; CME batch modification center:
not supported) to add an IP path.
NOTE
l On the SGSN, GGSN, or S-GW side, you can run associated commands to check whether the
feature One Tunnel is supported.
1.
Issue 06 (2013-03-25)
On the BSC6900 LMT, start signaling tracing over the Iu interface. For details, see
Tracing Messages on the Iu Interface.

678
RAN14.0
Figure 202-2 Setting Iu interface tracing
2.
Use a UE to start a PS service.
3.
In the Iu interface tracing data, check the information element

transportLayerAddress in the RANAP_RAB_ASSIGNMENT_REQ message.
Figure 202-3 Iu interface tracing
4.
If the value of the information element transportLayerAddress is the IP address

configured for the GGSN or S-GW during transmission resources configuration, this
Figure 202-4 IP address configured for the GGSN or S-GW
Issue 06 (2013-03-25)

679
RAN14.0
1.
Run the MML command RMV ADJNODE (CME single configuration: IUPS
Configuration Express > IP Transport > Adjacent Node; CME batch modification
center: not supported) to remove the corresponding adjacent node.
----End
Example
//Activation procedure:
ADD ADJNODE: ANI=0, NAME="S-GW NAME", NODET=IUPS, TRANST=IP, ISIPPOOL=NO,
SGSNFLG=NO;
/Adding an IP path for the adjacent node
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUPS, PATHT=BE, IPADDR="80.1.1.1",
PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000;
//Adding a layer 3 route to this adjacent node
NEXTHOP="80.1.1.10", PRIORITY=HIGH, REMARK="TO S-GW ROUTE";
//Deactivation procedure:
RMV ADJNODE: ANI=0;
Issue 06 (2013-03-25)

680
RAN14.0
203
Configuring Overbooking on ATM

Transmission
Overbooking on ATM Transmission.
Prerequisites
l
The backpressure and VP shaping mechanism depends on the ATM interface board on
RNC like AOUa/UOIa/AEUa/AOUc/UOIc.

License
Context
This feature improves the resource usage and provides a method for greatly saving OPEX on
ATM transmission, especially on Iub interface, when deploying HSDPA services. Other
strategies applied in overbooking are as follows:
l
RLC retransmission rate-based downlink congestion control
Backpressure-based downlink congestion control
VP shaping
Procedure
Activating RLC retransmission rate-based downlink congestion control
configuration: UMTS Radio Global Configuration Express > Connection_Oriented
RRM Switch Configuration > Connection Oriented Algorithm Switches; CME
Issue 06 (2013-03-25)

681
RAN14.0
batch modification center: 3.15 Modifying RNC Parameters in Batches) to turn on

the flow control switch.
For R99 BE services, select DRA_R99_DL_FLOW_CONTROL_SWITCH in
For HSDPA BE services, select
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH in Dynamic Resource
Allocation Switch.
Activating backpressure-based downlink congestion control
1.

PORTFLOWCTRLPARA (CME single configuration: UMTS Global
Configuration Express > Transmission Resources Configuration > Port Flow
Control Parameters; CME batch modification center: not supported). In this step,
set Port protocol type to ATM and set other flow control parameters.
2.
Turn on the flow control switch of physical port based on your configuration.
Run the BSC6900 MML command ADD IMAGRP (CME single
Transport > IMA Group; CME batch modification center: not supported). In
this step, set Flow control switch to ON.
Run the BSC6900 MML command ADD UNILNK (CME single
Transport > UNI Link; CME batch modification center: not supported). In
this step, set Flow control switch to ON.
Run the BSC6900 MML command ADD FRALNK (CME single
Transport > Fractional ATM Link; CME batch modification center: not
supported). In this step:
Set Fractional link type to FRAATM.
Set Flow control switch to ON.
3.
Optional: When the logical port is configured, Run the BSC6900 MML
command ADD ATMLOGICPORT (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > ATM Logical Port;
CME batch modification center: not supported). In this step:
Set Type of the logic port to Leaf.
Set Flow control switch to ON.
Activating VP shaping
1.
Run the BSC6900 MML command ADD ATMLOGICPORT (CME single

> ATM Logical Port; CME batch modification center: not supported). In this step,
set Type of the logic port to Leaf and Flow control switch to ON.
2.

> AAL2 Path; CME batch modification center: not supported) to add a logical
port. In this step, set Bearing type to ATMLOGICPORT.
Take RNC configured with the AOU interface board as an example to describe how to
verify backpressure-based flow control.
Issue 06 (2013-03-25)

682
RAN14.0
1.
On the BSC6900 LMT, start downlink traffic and bandwidth tracing tasks on the Uu,
Iub, and Iu interfaces.
2.
Register an R99 user UE1 in the HLR. Enable UE1 with streaming services and with
both highest uplink rate and highest downlink rate of 384 kbit/s.
3.
Register an HSDPA user UE2 in the HLR. Enable UE2 with background services and
with highest uplink rate of 384 kbit/s and highest downlink rate of 1450 kbit/s.
4.
Run the BSC6900 MML command ADD TRMMAP to map R99 services to the highpriority queue and HSDPA services to the low-priority queue.
5.
All AAL2 paths of the RNC are carried on an IMA port (IMA port is configured to
1Mbit/s). Enable the port flow control when adding the IMA port.
6.
Enable UE1 and UE2 to stay in idle mode and camp on the test cell. The test cell must
7.
Use UE1 to perform PS streaming services, that is, use UE1 to download files from
the FTP server.
Expected result: The IMA port is not congested and UE1 downloads data at the highest
rate.
8.
Use UE2 to perform PS BE services, that is, use UE2 to download files from the FTP
server.
Expected result: The IMA port is congested and the backpressure function is triggered.
The downloading rate of UE2 decreases and that of UE1 remains unchanged. This is
because R99 services have a higher priority.
Deactivating RLC retransmission rate-based downlink congestion control
batch modification center: 3.15 Modifying RNC Parameters in Batches) to turn off
the flow control switch.
For R99 BE services, deselect DRA_R99_DL_FLOW_CONTROL_SWITCH in
For HSDPA BE services, deselect
Allocation Switch.
Deactivating backpressure-based downlink congestion control
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD IMAGRP (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > IMA
Group; CME batch modification center: not supported). In this step, set Flow
control switch to OFF.
2.
Run the BSC6900 MML command MOD UNILNK (CME single configuration:
NodeB Configuration Express > IUB_RNC > ATM Transport > UNI Link;
CME batch modification center: not supported). In this step, set Flow control
switch to OFF.
3.
Run the BSC6900 MML command MOD FRALNK (CME single configuration:
ATM Link; CME batch modification center: not supported). In this step, set Flow
control switch to OFF.
4.
Run the BSC6900 MML command MOD ATMLOGICPORT (CME single

683
RAN14.0
> ATM Logical Port; CME batch modification center: not supported). In this step,
set Flow control switch to OFF.
----End
Example
//Activating RLC retransmission rate-based downlink congestion control
DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-1&DRA_R99_DL_FLOW_CONTROL_SWIT
CH-1;
//Activating backpressure-based downlink congestion control
ADD PORTFLOWCTRLPARA: FCINDEX=10, PORTPROTYPE=ATM;
MOD IMAGRP: SRN=1, SN=14, BT=AOUc, IMAGRPN=1, FLOWCTRLSWITCH=ON,
FCINDEX=100;
ADD UNILNK: SRN=1, SN=14, UNILNKN=1, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
ADD FRALNK: SRN=1, SN=14, FRALNKN=12, E1T1PN=0, TSBITMAP=TS1-1,
FRALNKT=FRAATM, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
ADD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUc, LPN=0,
CARRYT=ATMLOGICPORT, UPPERVP=0, TXBW=512, RXBW=512, FLOWCTRLSWITCH=ON;
//Activating VP shaping
ADD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUc, LPN=0,
CARRYT=ATMLOGICPORT, UPPERVP=0, TXBW=512, RXBW=512, FLOWCTRLSWITCH=ON;
ADD AAL2PATH: ANI=0, PATHID=1, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=0,
CARRYVPN=0, VPI=0, VCI=200, TXTRFX=150, RXTRFX=150, AAL2PATHT=HSPA;
//Deactivating RLC retransmission rate-based downlink congestion control
CH-0;
//Deactivating backpressure-based downlink congestion control
MOD IMAGRP: SRN=1, SN=14, BT=AOUc, IMAGRPN=1, FLOWCTRLSWITCH=OFF,
FCINDEX=100;
MOD UNILNK: SRN=1, SN=14, UNILNKN=1, FLOWCTRLSWITCH=OFF, OPSEPFLAG=OFF;
MOD FRALNK: SRN=1, SN=14, FRALNKN=12, E1T1PN=0, TSBITMAP=TS1-1,
FRALNKT=FRAATM, FLOWCTRLSWITCH=OFF, OPSEPFLAG=OFF;
MOD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUc, LPN=0, CARRYT=IMA,
CARRYIMAGRPN=1, TXBW=512, RXBW=512, RSCMNGMODE=SHARE, FLOWCTRLSWITCH=OFF;
Issue 06 (2013-03-25)

684
RAN14.0
204
Configuring ATM Switching-Based

Hub NodeB
ATM Switching-Based Hub NodeB.
Prerequisites
l

License
Context
This feature enables NodeB to provide the transmission convergence function in ATM mode.
Thus, the convergence gain is achieved and the transmission line cost is reduced.
Procedure
l
1.
1.
Run the NodeB MML command ADD TREELNKPVC (CME single configuration:
NodeB Configuration Express > IUB_NodeB > ATM Transport Layer >
NetWork > TreeLink PVC; CME batch modification center: not supported) to add
a tree link PVC.
Run the NodeB MML command LST TREELNKPVC to query the tree link PVC.
1.
Run the NodeB MML command RMV TREELNKPVC (CME single configuration:
NetWork > TreeLink PVC; CME batch modification center: not supported) to
remove the tree link PVC.
----End
Issue 06 (2013-03-25)

685
RAN14.0
Example
l
NodeB V200R014
ADD TREELNKPVC: NO=1, JNRSCGRP=DISABLE, VST=VC_SWITCH, SRCSRN=0,
SRCSN=7, SRCSBT=BASE_BOARD,
SRCPT=IMA, SRCPN=0, SRCVPI=7, SRCVCI=33, DSTSRN=0, DSTSN=5,
DSTSBT=E1_COVERBOARD, DSTPT=IMA,
DSTPN=1, DSTVPI=8, DSTVCI=33, RU=kbps, ST=RTVBR, PCR=1000, SCR=800;
LST TREELNKPVC:;
RMV TREELNKPVC: NO=1;
NodeB V100R014
ADD TREELNKPVC: NO=1, VST=VC_SWITCH, SRCSRN=0, SRCSN=15,
SRCSBT=BASE_BOARD,
SRCPT=IMA, SRCPN=0, SRCVPI=7, SRCVCI=33, DSTSRN=0, DSTSN=12,
DSTSBT=E1_COVERBOARD, DSTPT=IMA,
DSTPN=1, DSTVPI=8, DSTVCI=33, RU=KBPS, ST=RTVBR, PCR=1000, SCR=800;
LST TREELNKPVC:;
RMV TREELNKPVC: NO=1;
Issue 06 (2013-03-25)

686
RAN14.0
205
Configuring AAL2 Switching-Based

Hub NodeB
AAL2 Switching-Based Hub NodeB.
Prerequisites
l
DBS 3800 does not support this feature.
BTS 3902E does not support this feature.

The feature WRFD-050105 ATM Switching-Based Hub NodeB must be configured
License
Context
This feature enables Huawei NodeB to provide the AAL2 transmission convergence function
in ATM mode. Thus, the convergence gain is achieved and the transmission line cost is reduced.
Procedure
l
l
Issue 06 (2013-03-25)
1.
Run the NodeB MML command ADD AAL2NODE (CME single configuration:
ALCAP > AAL2 Node; CME batch modification center: 3.17 Modifying Physical
NodeB Parameters in Batches) to add an AAL2 node. In this step, set Node Type
to HUB(Switching Node).
2.
Run the NodeB MML command ADD AAL2ADJNODE (CME single configuration:
ALCAP > AAL2 Adjacent Node; CME batch modification center: not supported) to
add an AAL2 adjacent node to the lower-level NodeB.
687
RAN14.0
1.
Run the NodeB MML command DSP AAL2NODE to query the configuration of the
AAL2 node.
2.
Run the NodeB MML command DSP AAL2ADJNODE to query the configuration
of the AAL2 adjacent node.
1.
Run the NodeB MML command RMV AAL2ADJNODE (CME single

configuration: NodeB Configuration Express > IUB_NodeB > ATM Transport
Layer > ALCAP > AAL2 Adjacent Node; CME batch modification center: not
supported) to remove the AAL2 adjacent node.
2.
Run the NodeB MML command RMV AAL2NODE (CME single configuration:
ALCAP > AAL2 Node; CME batch modification center: not supported) to remove
an AAL2 node. In this step, set Node Type to HUB(Switching Node).
NOTE
There is a relation between the AAL2 adjacent node and the AAL2 node. Therefore, you need
to remove the AAL2 adjacent nodes first and then remove the AAL2 node. Note that the AAL2
node can be removed only after all the AAL2 adjacent nodes are removed. Otherwise, the
command execution fails.
----End
Example
ADD AAL2NODE: NT=HUB, LN=1;
ADD AAL2ADJNODE: ANI=1,
ADDR="H'3912323232323232333333333333333333333333", LN=2;
DSP AAL2NODE:;
DSP AAL2ADJNODE:;
RMV AAL2ADJNODE: ANI=1;
RMV AAL2NODE: NT=HUB;
Issue 06 (2013-03-25)

688
RAN14.0
206 Configuring IP Transmission Introduction on Iub

Interface
206
Configuring IP Transmission
Introduction on Iub Interface
IP Transmission Introduction on Iub Interface. (This feature cannot be configured using the
CME. )
Prerequisites
l
To use the IP header compression function on the Iub interface, the PEUa or POUa
board is required.
Only the Dopra Linux OS supports the built-in firewall function for O&M.
Only the FG2c and GOUc boards of the BSC6900 support the built-in firewall function
for interfaces.
Only the FG2a, GOUa, FG2c and GOUc boards of the BSC6900 support Bidirectional
Forwarding Detection (BFD).
Dependencies on base stations:
NUTI board is needed with BTS3812E/AE to support this feature.
Only the 3900 series NodeB supports inter-board ML-PPP.

License
Context
This feature provides a new lub transmission solution for operators. Compared with ATM
transmission, IP transmission reduces the transmission costs of HSDPA and HSUPA services.
This feature enhances Iub transmission by introducing the following functions: BFD-based IP
fault detection, built-in firewall on the RNC side, and built-in firewall on the NodeB side.
Issue 06 (2013-03-25)

689
RAN14.0

Interface
If BFD-based IP fault detection is enabled, the BSC6900 triggers a port switchover, board
switchover, or IP rerouting when detecting that the gateway or the peer entity becomes
faulty. BFD can be classified into multi-hop BFD and single-hop BFD:
In multi-hop BFD, the IP addresses of the local and peer ports must be on different
network segments.
In single-hop BFD, the IP addresses of the local and peer ports must be on the same
network segment.
The built-in firewall on the RNC side safeguards IP Ethernet ports on interface boards and
O&M ports against network attacks.
The built-in firewall on the NodeB side safeguards the Iub interface against network attacks
during IP transmission.
Procedure
1.
Run the BSC6900 MML command SET ETHPORT to set the attributes of an
Ethernet port. In this step, takes the FG2c board as an example.
2.
Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet
port.
3.
Run the BSC6900 MML command STR IPCHK to configure the BFD check. In this
step, set Check type to SBFD.
4.
Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall
function for an interface board. In this step, set Board type. to FG2c and ARP
Learning Strict Switch to ON.
NOTE
The FG2c and GOUc boards support both the invalid packet detection function and the ARP learning
strict function. The FG2a and GOUa boards support only the ARP learning strict function.
5.
(Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS
supports the built-in firewall function) by performing the following operations: Log
in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux
command iptables -A INPUT -s restricted IP -i Ethernet adapter -p transport
protocol --dport restricted port -j DROP. Here, restricted IP refers to the IP address
that needs to be prohibited or allowed, and it can be a single IP address or a network
segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport
protocol can be TCP or UDP; restricted port is the port to be prohibited. If -p transport
protocol and --dport restricted port are not specified, all ports are disabled.
6.
Run the BSC6900 MML command ADD PPPLNK to configure head compress for
a PPP link. In this step, set Head compress to UDP/IP_HC(UDP/IP_HC). Run the
BSC6900 MML command ADD MPGRP to configure head compress for a PPP link
group. In this step, set Head compress to UDP/IP_HC(UDP/IP_HC).
NOTE
Head compress must be configured on peer equipment.
7.
Run the NodeB MML command ADD PPPLNK to enable head compress for a PPP
link. Run the NodeB MML command ADD MPGRP to enable head compress for a
PPP link group.
8.
Activating the built-in firewall function on the NodeB.

a.
Issue 06 (2013-03-25)
Run the NodeB MML command ADD ACL to add an access control list (ACL).
690
RAN14.0

Interface
b.
Run the NodeB MML command ADD ACLRULE to add a rule to the ACL.
NOTE
Before adding a rule to an ACL, ensure that the ACL has already existed.
c.
9.
Run the NodeB MML command ADD PACKETFILTER to bind an ACL to a

port so that packets received at the port are filtered by the ACL.
Optional: Activating layer 2 ACL packet filter.

a.
Run the NodeB MML command ADD ACL to add an access control list (ACL).
b.
Run the NodeB MML command ADD ACLRULE to add a rule to the ACL.
NOTE
The ACL used in layer 2 packet filter is an extended ACL. According to the ACL
specifications, the ID of an extended ACL ranges from 4000 to 4999. Therefore, the ACL
ID configured in layer 2 ACL packet filter must also range from 4000 to 4999.
c.
Run the NodeB MML command ADD PACKETFILTER to bind an ACL to a

port so that packets received at the port are filtered by the ACL.
10. Optional: Run the NodeB MML command ADD FLOODDEFEND to activate flood
attack prevention.
11. Optional: Run the NodeB MML command SET IPGUARD to activate ARP spoofing
prevention.
l
1.
Run the BSC6900 MML command DSP ETHPORT to query the attributes of an
Ethernet port.
2.
Run the BSC6900 MML command LST ETHIP to query the IP address of the
Ethernet port.
3.
Run the BSC6900 MML command DSP IPCHK to query whether the Check state
is UP.
4.
Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP

Connectivity Check Failure is reported.
5.
Run the BSC6900 MML command LST IPGUARD to check whether the value of
ARP Learning Strict Switch is ON.
6.
Built response messages to ARP requests and sent to interface boards. Run the
BSC6900 MML command DSP ARP to query the ARP table of interface boards. If
the information of interface boards in ARP table do not update, the ARP Learning
Strict Switch is valid.
7.
If any invalid packet exists, run the BSC6900 MML command DSP
INVALIDPKTINFO to query the detailed information.
8.
(Optional) Log in to the computer whose IP address is prohibited and check whether
the prohibited services can be performed. Run the Dopra Linux command iptables L. All the filtering rules on the OMU will be listed, and check whether new rules are
added successfully.
If port 80 is disabled, logging in to the BSC6900 LMT is prohibited. Check whether
you can log in to the BSC6900 LMT on the PC whose port 80 is disabled.
If port 22 is disabled, the OMU cannot be logged in to remotely. Check whether
you can log in to the BSC6900 OMU through Putty on the PC whose port 22 is
disabled.
Issue 06 (2013-03-25)

691
RAN14.0

Interface
If port 21 is disabled, FTP services of the OMU cannot be used. Check whether
you can connect to the FTP server of the BSC6900 OMU through an FTP client
on the PC whose port 21 is disabled.
9.
Run the BSC6900 MML command DSP PPPLNK or DSP MPGRP to query whether
the Code compress type is UDP/IP_HC.
10. Run the NodeB MML command DSP PPPLNK or DSP MPGRP to check whether
the compress state is enable.
11. Run the NodeB MML command LST ACL to check whether an ACL has been
configured.
12. Run the NodeB MML command LST ACLRULE to check whether a rule has been
added to the ACL.
13. Run the NodeB MML command DSP PACKETFILTER to check whether a port is
bound to the ACL.
14. Run the NodeB MML command PING to use IP addresses that are not listed in the
ACL to ping the port supporting the packet filtering function. If no response is
received, the built-in firewall on the NodeB side has been activated.
15. Optional: To check whether layer 2 ACL packet filter has been activated, Run the
NodeB MML command DSP PACKETFILTER to query the junk packets that have
been filtered out.
16. Optional: To check whether flood attack prevention has been activated, Run the
NodeB MML command DSP FLOODDEFEND to query the discarded attack
packets.
17. Optional: To check whether malformed packet attack prevention and ARP spoofing
prevention have been activated, Run the NodeB MML command DSP
INVALIDPKTINFO to query the discarded attack packets.
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command STP IPCHK to stop the BFD.
2.
Run the BSC6900 MML command SET IPGUARD. In this step, set Board type to
FG2c and ARP Learning Strict Switch to OFF.
3.
Run the BSC6900 MML command RMV ETHIP to remove an IP address from the
Ethernet port.
4.
Run the BSC6900 MML command SET ETHPORT. In this step, set Port type to
FE.
5.
(Optional) Log in to the OMU through the LMT locally or through Putty remotely.
Run the Dopra Linux command iptables -D INPUT -s restricted IP -i Ethernet
adapter -p transport protocol --dport restricted port -j DROP. Here, restricted IP
is the IP address that needs to be prohibited or allowed, and it can be a single IP address
or a network segment; Ethernet adapter is the name of the OMU external Ethernet
adapter; transport protocol can be TCP or UDP; restricted port is the port to be
prohibited, and it is used together with the transport protocol. If -p transport protocol
and --dport restricted port are not specified, all ports are disabled.
6.
(Optional) Run the Dopra Linux command iptables -L. All the filtering rules on the
OMU will be listed, and check whether new rules are removed successfully.
7.
Run the BSC6900 MML command MOD PPPLNK or MOD MPGRP. In this step,
set Head compress to No_HC.
8.
Run the NodeB MML command RMV PPPLNK to remove a PPP link. Run the
NodeB MML command RMV MPGRP to remove a PPP link group.
692
RAN14.0

Interface
9.
Run the NodeB MML command RMV PACKETFILTER to remove the binding
relationship between the port and the ACL.
10. Run the NodeB MML command RMV ACLRULE to remove all the rules from the
ACL.
11. Run the NodeB MML command RMV ACL to remove the ACL.
12. Optional: Run the NodeB MML command RMV PACKETFILTER to deactivate
layer 2 ACL packet filter for a port.
13. Optional: Run the NodeB MML command RMV FLOODDEFEND to deactivate
flood attack prevention.
14. Optional: Run the NodeB MML command SET IPGUARD with ARP Spoofing
Check Switch and ARP Learning Strict Switch set to DISABLE(Disable) to
deactivate ARP spoofing prevention.
----End
Example
//Configuring the attributes of an Ethernet port and adding an IP address
to the port
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, SPEED=AUTO;
ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.171.35.123",
MASK="255.255.255.0";
//Activating BFD-based IP fault detection on an interface board
STR IPCHK: SRN=0, SN=14, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=0,
PEERIP="10.171.35.126";
//Activating the built-in firewall function on an RNC interface board
SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=ON;
//Activating the built-in firewall function for O&M on the RNC
//For example, only the IP addresses on the 10.141.148.0 network segment
is allowed to access the LMT
iptables -A INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport
80 -j DROP
//Activating IP head compress for a PPP link
ADD PPPLNK: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=0, DS1=0,
TSBITMAP=TS1-1, BORROWDEVIP=NO, LOCALIP="5.5.5.5", MASK="255.255.255.0",
PEERIP="5.5.5.6", IPHC=UDP/IP_HC, PPPMUX=Disable, AUTHTYPE=NO_V,
FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF, OPSEPFLAG=OFF;
//Activating IP head compress for a PPP link group
ADD MPGRP: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=0,
MPTYPE=MCPPP, BORROWDEVIP=NO, LOCALIP="5.5.5.5", MASK="255.255.255.0",
PEERIP="5.5.5.6", MHF=LONG, PPPMUX=Disable, FLOWCTRLSWITCH=ON,
AUTHTYPE=NO_V, ERRDETECTSW=OFF, ANTIERRFLAG=OFF, OPSEPFLAG=OFF;
//Activating IP head compress for a PPP link on NodeB
ADD PPPLNK: SRN=0, SN=0, SBT=E1_COVERBOARD, AUTH=NONAUTH, TSN=TS1-1,
IPHC=ENABLE;
//Activating IP head compress for a PPP link group on NodeB
ADD MPGRP: SRN=0, SN=0, SBT=E1_COVERBOARD, AUTH=NONAUTH, IPHC=ENABLE;
//Activating the built-in firewall function on the NodeB
ADD ACL: ACLID=3000, ACLDESC="ACL_TEST";
ADD ACLRULE: ACLID=3000, RULEID=1, PT=IP, SIP="192.168.1.1",
SWC="0.0.0.0", DIP="10.10.1.101", DWC="0.0.0.0", MDSCP=NO;
ADD PACKETFILTER: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, ACLID=3000;
//(Optional)Activating layer 2 ACL packet filter
ADD ACL: ACLID=4000, ACLDESC="Acl Group is created";
ADD ACLRULE: ACLID=4000, VLANIDOP=OP_RANGE, VLANID1=100, VLANID2=105;
ADD PACKETFILTER: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, FM=L2_ACL,
ACLID2=4000;
//(Optional)Activating flood attack prevention
Issue 06 (2013-03-25)

693
RAN14.0

Interface
ADD FLOODDEFEND: FLDTYPE=ARP, DFDSW=ENABLE, DFDTHD=512, ALMSW=ENABLE,

ALMTHD=256;
//(Optional)Activating ARP spoofing prevention
SET IPGUARD: ARPSPOOFCHKSW=ENABLE, ARPSPOOFALMTHD=120,
ARPLRNSTRICTSW=ENABLE;
//Querying the attributes and IP address of an Ethernet port
DSP ETHPORT: SRN=0, SN=14;
LST ETHIP: SRN=0, SN=14, PN=0;
//Verifying BFD-based IP fault detection
DSP IPCHK: SRN=0, SN=14;
//Verifying the built-in firewall function on an RNC interface board
LST IPGUARD: SRN=0, SN=14;
DSP ARP: SRN=0, SN=14;
DSP INVALIDPKTINFO: SRN=0, SN=14;
//Verifying IP head compress for a PPP link
DSP PPPLNK: SRN=0, SN=14, PPPLNKN=0;
//Verifying IP head compress for a PPP link group
DSP MPGRP: SRN=0, SN=14, MPGRPN=0;
//Verifying IP head compress for a PPP link on NodeB
DSP PPPLNK:;
//Verifying IP head compress for a PPP link group
DSP MPGRP:;
//Verifying the built-in firewall function on the NodeB
LST ACL: ACLID=3000;
LST ACLRULE: ACLID=3000, RULEID=1;
DSP PACKETFILTER:;
PING: SN=7, SRCIP="192.168.1.1", DSTIP="192.168.2.2", CONTPING=DISABLE,
APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
//(Optional) Verifying layer 2 ACL packet filter
DSP PACKETFILTER:;
//(Optional) Verifying flood attack prevention
DSP FLOODDEFEND: FLDTYPE=ICMP;
//(Optional) Verifying ARP apoofing prevention
DSP INVALIDPKTINFO:;
//Deactivating BFD-based IP fault detection
STP IPCHK: SRN=0, SN=14, CHKN=0;
//Deactivating the built-in firewall function on an RNC interface board
SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=OFF;
//Removing an IP address from an Ethernet port and modifying the
attributes of the Ethernet port
RMV ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0;
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=FE, PN=0;
//Deactivating the built-in firewall function for O&M
iptables -D INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport
80 -j DROP
//Deactivating IP head compress for a PPP link
MOD PPPLNK: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=0,
IPHC=No_HC;
//Deactivating IP head compress for a PPP link group
IPHC=No_HC;
//Deactivating IP head compress for a PPP link on NodeB
RMV PPPLNK: SRN=0, SN=0, SBT=E1_COVERBOARD;
//Deactivating IP head compress for a PPP link group on NodeB
RMV MPGRP: SRN=0, SN=0, SBT=E1_COVERBOARD;
//Deactivating the built-in firewall function on the NodeB
RMV PACKETFILTER: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0;
RMV ACLRULE: ACLID=3000, RULEID=1;
RMV ACL: ACLID=3000;
//(Optional) Deactivating layer 2 ACL packet filter
RMV PACKETFILTER: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, FM=L2_ACL;
//(Optional) Deactivating flood attack prevention
Issue 06 (2013-03-25)

694
RAN14.0

Interface
RMV FLOODDEFEND: FLDTYPE=ARP;

//(Optional) Deactivating ARP apoofing prevention
SET IPGUARD: ARPSPOOFCHKSW=DISABLE, ARPLRNSTRICTSW=DISABLE;
Issue 06 (2013-03-25)

695
RAN14.0
207
Configuring Hybrid Iub IP

Transmission
Hybrid Iub IP Transmission.
Prerequisites
l

feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub
Interface.
License
Others
The RNC and NodeB support IP transmission.
The control-plane data and physical device data of the IP-based Iub interface is
configured.
Context
In hybrid IP transmission, real-time services and non-real-time services are transmitted on
discrete paths to meet different requirements of services in the UMTS system. Two types of
hybrid transmission are available: FE+E1/T1 and FE+FE.
Procedure
l
1.
Issue 06 (2013-03-25)
696
RAN14.0
center: not supported) to add a NodeB. In this step, set IUB Trans Bearer Type to
HYBRID_IP_TRANS.
2.
NodeB Configuration Express > IUB_RNC > IP Transport > Adjacent Node;
CME batch modification center: not supported) to add an adjacent node. In this step,
set the parameter Adjacent Node Type to IUB and the parameter Transport Type
to HYBIRD_IP.
3.
NodeB Configuration Express > IUB_RNC > IP Transport > IP Path; CME batch
modification center: not supported) to add an IP path. In this step, set the parameter
Interface Type to IUB and the parameter Transport Type to HYBIRD_IP.
NOTE
If IP Path Type is set to QOS or BE-EF, the path is a high-priority path and usually E1/T1
transmission is applied.
If IP Path Type is set to LQ_QOS or LQ_BE-LQ_EF, the path is a low-priority path and usually
FE transmission is applied.
4.
> Transport Resource Mapping; CME batch modification center: not supported).
In this step, set Interface Type to IUB and Transport Type to HYBIRD_IP.
5.
NodeB Configuration Express > IUB_RNC > IP Transport > Adjacent Node
Mapping; CME batch modification center: not supported). In this step, set Interface
Type to IUB, and Transport Type of the adjacent node and interface type and
Interface type to HYBIRD_IP.
1.
Use the UE to make a call. If the call is connected, you can infer that high-priority
services can access the high-priority IP paths normally and low-priority services can
access the low-priority IP paths normally.
2.
Run the BSC6900 MML command DSP IPCHN to query the type of services carried
in the IP path, and the forward bit rate and backward bit rate of the services.
1.
Run the BSC6900 MML command RMV ADJMAP (CME single configuration:
Mapping; CME batch modification center: not supported) to remove the TRM
mapping to the adjacent node on the Iub interface.
2.
Run the BSC6900 MML command RMV TRMMAP (CME single configuration:
> Transport Resource Mapping; CME batch modification center: not supported) to
remove the transmission resource mapping on the Iub interface.
3.
Run the BSC6900 MML command RMV IPPATH (CME single configuration:
modification center: not supported) to remove the IP path on the Iub interface.
----End
Example
//Activating Hybrid Iub IP Transmission
//Adding a NodeB
Issue 06 (2013-03-25)

697
RAN14.0
ADD UNODEB: NodeBName="test", NodeBId=115, SRN=0, SN=0,

TnlBearerType=HYBRID_IP_TRANS, IPTRANSAPARTIND=SUPPORT,
HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0;
ADD ADJNODE: ANI=115, NAME="test", NODET=IUB, NODEBID=115,
TRANST=HYBRID_IP;
//Adding an IP path
ADD IPPATH: ANI=115, PATHID=115, ITFT=IUB, TRANST=HYBRID_IP, PATHT=QoS,
//Adding another IP path
ADD IPPATH: ANI=115, PATHID=116, ITFT=IUB, TRANST=HYBRID_IP,
PATHT=LQ_QOS, IPADDR="165.11.81.1", PEERIPADDR="22.22.22.23", TXBW=10000,
RXBW=10000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Adding the transmission resource mapping
ADD TRMMAP: TMI=115, ITFT=IUB, TRANST=HYBRID_IP, CCHPRIPATH=EF,
CCHSECPATH=LQEF, SIPPRIPATH=EF, SIPSECPATH=LQEF, SRBPRIPATH=EF,
SRBSECPATH=LQEF, VOICEPRIPATH=EF, VOICESECPATH=LQEF, CSCONVPRIPATH=AF42,
CSCONVSECPATH=LQAF42, CSSTRMPRIPATH=AF42, CSSTRMSECPATH=LQAF42,
PSCONVPRIPATH=AF42, PSCONVSECPATH=LQAF42, PSSTRMPRIPATH=AF42,
PSSTRMSECPATH=LQAF42, PSINTHGHPRIPATH=AF21, PSINTHGHSECPATH=LQAF21,
PSINTMIDPRIPATH=AF21, PSINTMIDSECPATH=LQAF21, PSINTLOWPRIPATH=AF21,
PSINTLOWSECPATH=LQAF21, PSBKGPRIPATH=AF21, PSBKGSECPATH=LQAF21,
HDSRBPRIPATH=EF, HDSRBSECPATH=LQEF, HDSIPPRIPATH=EF, HDSIPSECPATH=LQEF,
HDVOICEPRIPATH=AF42, HDVOICESECPATH=LQAF42, HDCONVPRIPATH=AF42,
HDCONVSECPATH=LQAF42, HDSTRMPRIPATH=AF42, HDSTRMSECPATH=LQAF42,
HDINTHGHPRIPATH=LQBE, HDINTHGHSECPATH=BE, HDINTMIDPRIPATH=LQBE,
HDINTMIDSECPATH=BE, HDINTLOWPRIPATH=LQBE, HDINTLOWSECPATH=BE,
HDBKGPRIPATH=LQBE, HDBKGSECPATH=BE, HUSRBPRIPATH=EF, HUSRBSECPATH=LQEF,
HUSIPPRIPATH=EF, HUSIPSECPATH=LQEF, HUVOICEPRIPATH=AF42,
HUVOICESECPATH=LQAF42, HUCONVPRIPATH=AF42, HUCONVSECPATH=LQAF42,
HUSTRMPRIPATH=AF42, HUSTRMSECPATH=LQAF42, HUINTHGHPRIPATH=LQBE,
HUINTHGHSECPATH=BE, HUINTMIDPRIPATH=LQBE, HUINTMIDSECPATH=BE,
HUINTLOWPRIPATH=LQBE, HUINTLOWSECPATH=BE, HUBKGPRIPATH=LQBE,
HUBKGSECPATH=BE;
//Adding the TRM mapping to the adjacent node
ADD ADJMAP: ANI=115, ITFT=IUB, TRANST=HYBRID_IP, CNMNGMODE=EXCLUSIVE,
CNOPINDEX=0, TMIGLD=115, TMISLV=115, TMIBRZ=115, FTI=0, LEIGLD=0,
LEISLV=0, LEIBRZ=0;
//Verifying Hybrid Iub IP Transmission
DSP IPCHN: ANI=115, PATHID=115;
//Deactivating Hybrid Iub IP Transmission
//Removing the TRM mapping to the adjacent node
RMV ADJMAP: ANI=115,ITFT=IUB,CNMNGMODE=EXCLUSIVE;
//Removing the transmission resource mapping
RMV TRMMAP: TMI=115;
//Removing IP paths
RMV IPPATH: ANI=115, PATHID=115;
Issue 06 (2013-03-25)

698
RAN14.0
208
Configuring ATM/IP Dual Stack

NodeB
ATM/IP Dual Stack NodeB.
Prerequisites
l
BSC6900 is configured with both ATM interface boards and IP interface boards.

The feature WRFD-050402 IP Transmission Introduction on Iub Interface must be
License
Others
The ATM/IP transmission link from the RNC to the NodeB is configured.
Context
This feature allows NodeB to support the ATM/IP dual-stack transmission. Services with
different QoS requirements can be carried on the links of different protocols. In addition, the
transmission backup is also provided.
Procedure
l
Issue 06 (2013-03-25)

699
RAN14.0

NOTE
When you allocate resources for ATM/IP dual stack-based transport on the Iub interface, take the
following suggestions into consideration:
l ATM transport, IP transport, or ATM/IP hybrid transport is applicable to control plane data. It
is recommended that ATM/IP hybrid transport be applied to control plane data for security
purposes. That is, the SAAL and SCTP links together carry an NCP or a CCP, and the SAAL
link is the active link.
l ATM transport, IP transport, or ATM/IP hybrid transport is applicable to user plane data. It is
recommended that:
l ATM transport be applied to signaling, voice services, CS conversational services, CS
streaming services, PS conversational services, and PS streaming services.
l IP transport be applied to PS interactive services, PS background services, HSDPA
conversational services, HSDPA streaming services, HSDPA interactive services, HSDPA
background services, HSUPA conversational services, HSUPA streaming services, HSUPA
interactive services, and HSUPA background services.
l Either ATM or IP transport is applicable to management plane data. It is recommended that IP
transport be applied.
Issue 06 (2013-03-25)
1.
center: not supported) to add a NodeB. In this step, set IUB Trans Bearer Type to
ATMANDIP_TRANS.
2.
> Transport Resource Mapping; CME batch modification center: not supported).
In this step, set Interface Type to IUB and Transport Type to ATM_IP.
3.
Node; CME batch modification center: not supported) to add an adjacent node. In this
step, set Adjacent Node Type to IUB and Transport Type to ATM_IP. If the node
is a leaf node, set Is Root Node to YES; otherwise, set Is Root Node to NO.
4.
NodeB Configuration Express > IUB_RNC > ATM Transport > AAL2 Path;
CME batch modification center: not supported) to add an AAL2 path.
5.
modification center: not supported) to add an IP path. In this step, set Interface
Type to IUB and Transport Type to IP.
6.
NodeB Configuration Express > IUB_RNC > ATM Transport > Adjacent Node
Mapping; CME batch modification center: not supported). In this step, set Interface
Type to IUB and Transport Type of the adjacent node and interface type to
ATM_IP.
1.
Use a UE to make a call and perform FTP downloading. High-priority services (such
as calls and web browsing) can be carried on ATM paths and low-priority services
(FTP downloading) can be carried on IP paths.
2.
Run the BSC6900 MML command DSP IPPATH to check the state of the IP path
and whether any resources of the path are occupied.

700
RAN14.0
Expected result: Operation state is Available, and some resources of the path are
occupied.
3.
Run the BSC6900 MML command DSP AAL2PATH to check the state of the AAL2
path and whether any resources of the path are occupied.
Expected result: Operation state is Available, and some resources of the path are
occupied.
1.
NodeB Configuration Express > IUB_RNC > ATM Transport > Adjacent Node
mapping to the adjacent node.
2.
remove the transmission resource mapping on the Iub interface.
3.
Run the BSC6900 MML command RMV IPPATH (CME single configuration:
modification center: not supported) to remove the IP path on the Iub interface.
----End
Example
//Configuring ATM/IP Dual Stack NodeB
//Adding a NodeB
ADD UNODEB: NodeBName="test", NodeBId=115, SRN=0, SN=0,
TnlBearerType=ATMANDIP_TRANS, IPTRANSAPARTIND=SUPPORT,
HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0;
//Adding the transmission resource mapping
ADD TRMMAP: TMI=115, ITFT=IUB, TRANST=ATM_IP;
ADD ADJNODE: ANI=115, NAME="test", NODET=IUB, NODEBID=115, TRANST=ATM_IP,
IsROOTNODE=YES, SAALLNKN=1;
AAL2PATHT=R99;
//Adding an IP path
ADD IPPATH: ANI=115, PATHID=115, ITFT=IUB, TRANST=IP, PATHT=QoS,
//Adding the TRM mapping to the adjacent node
ADD ADJMAP: ANI=115, ITFT=IUB, TRANST=ATM_IP, CNMNGMODE=EXCLUSIVE,
CNOPINDEX=0, TMIGLD=115, TMISLV=115, TMIBRZ=115, FTI=0, LEIGLD=0,
LEISLV=0, LEIBRZ=0;
//Verifying ATM/IP Dual Stack NodeB
DSP IPPATH: ANI=115, PATHID=115;
DSP AAL2PATH: ANI=115, PATHID=115;
//Deactivating ATM/IP Dual Stack NodeB
//Removing the TRM mapping to the adjacent node
RMV ADJMAP: ANI=115,ITFT=IUB,CNMNGMODE=EXCLUSIVE;
//Removing the transmission resource mapping
RMV TRMMAP: TMI=115;
Issue 06 (2013-03-25)

701
RAN14.0
//Removing the IP path

Issue 06 (2013-03-25)

702
RAN14.0
209
Introduction on Iu Interface
IP Transmission Introduction on Iu Interface.
Prerequisites
l
for interfaces.

License
Context
This feature provides a new lu transmission solution for operators. Compared with ATM
transmission, IP transmission can significantly reduce the transmission cost.
This feature enhances Iu transmission by introducing the following functions: BFD-based IP
fault detection and built-in firewall on the RNC side.
l
network segments.
network segment.
Issue 06 (2013-03-25)

703
RAN14.0
Procedure
Step 1 For configurations of Iu interface, see Initial Configuration Guide.
----End
Issue 06 (2013-03-25)

704
RAN14.0
210 Configuring IP Transmission Introduction on Iur

Interface
210
Introduction on Iur Interface
IP Transmission Introduction on Iur Interface.
Prerequisites
l
for interfaces.

License
The neighboring RNC supports IP transmission on the Iur interface.
Context
This feature provides a new lur transmission solution for operators. Compared with ATM
transmission, IP transmission can significantly reduce the transmission cost.
This feature enhances Iur transmission by introducing the following functions: BFD-based IP
fault detection and built-in firewall on the RNC side.
l
network segments.
Issue 06 (2013-03-25)

705
RAN14.0
210 Configuring IP Transmission Introduction on Iur

Interface
network segment.
l
Procedure
Step 1 For configurations of Iur interface, see Initial Configuration Guide.
----End
Issue 06 (2013-03-25)

706
RAN14.0
211
Configuring FP MUX for IP

Transmission
Configuring FP MUX for IP Transmission.
Prerequisites
l
The FG2a/FG2c, GOUa/GOUc, and POUc support FP multiplexing for BSC6900.

The feature WRFD-050402 IP Transmission Introduction on Iub Interface has been
License
Others
The receive end of IP packets support FP mulptiplexing.
Context
The FP MUX feature encapsulates multiple packets with the same source IP address, destination
IP address, and DiffServ Code Point (DSCP) into one UDP/IP packet. This reduces the overhead
of packet headers and therefore improves the transmission efficiency.
FP MUX is a Huawei proprietary protocol. Both RNC and NodeB must support this feature.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD IPMUX (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > IP MUX Pipe; CME batch
modification center: not supported) to enable frame multiplexing on the Iub interface.
In this step, set IP MUX Type to FPMUX.
707
RAN14.0

NOTE
You do not need to configure the number of packets for multiplexing, the BSC6900 selects
proper subframes for multiplexing based on the length of subframes. Subframes that meet the
following conditions are multiplexed into packets:
1. The total sending duration of subframes is smaller than Maximum Delay Time.
2. The length of the subframe is smaller than Max subframe length.
3. The total length of subframes plus eight is smaller than or equal to Maximum Frame
Length.
2.
Run the NodeB MML command SET FPMUX (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Basic Information > Transport
Management > FP Multiplexing Switch; CME batch modification center: not
supported) to configure FP multiplexing on the Iub interface on the NodeB side.
1.
Run the BSC6900 MML command DSP IPMUX to check IP packet multiplexing
conditions.
2.
Run the NodeB MML command LST FPMUX to query the FP multiplexing condition
of an IP path.
1.
Run the BSC6900 MML command RMV IPMUX (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > IP MUX Pipe; CME
batch modification center: not supported) to disable the FP multiplexing function for
the IP path.
2.
Run the NodeB MML command SET FPMUX (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Basic Information > Transport
Management > FP Multiplexing Switch; CME batch modification center: not
supported) to disable FP multiplexing on the NodeB side.
----End
Example
//Acitvating FP MUX for IP Transmission on the RNC side
ADD IPMUX: MUXTYPE=FPMUX, ANI=1, PATHID=1, ISQOSPATH=NO, SUBFRAMELEN=352,
MAXFRAMELEN=1031;
//Acitvating FP MUX for IP Transmission on the NodeB side
SET FPMUX: FPMUXSWITCH =ENABLE;
//Verifying FP MUX for IP Transmission on the RNC side
DSP IPMUX: IPMUXINDEX=1;
//Verifying FP MUX for IP Transmission on the NodeB side
LST FPMUX:;
//Deacitvating FP MUX for IP Transmission on the RNC side
RMV IPMUX: IPMUXINDEX=1;
//Deacitvating FP MUX for IP Transmission on the NodeB side
SET FPMUX: FPMUXSWITCH =DISABLE;
Issue 06 (2013-03-25)

708
RAN14.0
212
Configuring Dynamic Bandwidth

Control of Iub IP
Dynamic Bandwidth Control of Iub IP.
Prerequisites
l
The FG2a, FG2c, GOUa and GOUc support this feature for BSC6900.

feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub
Interface.
License
Context
This feature enables the RNC to adjust the transmission bandwidth according to the packet loss
ratio and jitter over links detected by the IP performance monitor (PM).
Procedure
l
Issue 06 (2013-03-25)
Activating Procedure
1.
Run the BSC6900 MML command ADD IPLOGICPORT (CME single

configuration: NodeB Configuration Express > IUB_RNC > IP Transport > IP
Logical Port; CME batch modification center: not supported). In this step, set Auto
adjust bandwidth switch to ON, Max bandwidth and Min bandwidth to
appropriate values.
2.
modification center: not supported) to add a new IP PATH over the new logic port.
709
RAN14.0
3.
Run the BSC6900 MML command ACT IPPM (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > IPPM; CME batch
modification center: not supported) to activate the IP PM of the new IP PATH.
1.
Log on the BSC6900 LMT. On the displayed monitoring navigation tree, choose
Monitor > Common Monitoring > Link Performance Monitoring to create a task
of logical port bandwidth monitoring.
NOTE
l Configure monitoring parameters, select Logical Port Bandwidth for Monitor Item, and set the
Subrack No. and Slot No. of the logical port.
l Expected result: when the rate of packet discard and delay exceed the threshold (which can be
set by running the BSC6900 MML command ADD IPLOGICPORT), you can obtain that the
logic port bandwidth changes within the range defined by Max bandwidth and Min
bandwidth.
Deactivating Procedure
1.
Run the BSC6900 MML command MOD IPLOGICPORT (CME single

configuration: NodeB Configuration Express > IUB_RNC > IP Transport > IP
Logical Port; CME batch modification center: not supported). In this step, set Auto
adjust bandwidth switch to OFF.
2.
Run the BSC6900 MML command DEA IPPM (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > IPPM; CME batch
modification center: not supported) to deactivate the IP PM.
----End
Example
ADD IPLOGICPORT: SRN=0, SN=14, BT=FG2a, LPN=0, CARRYT=ETHER, PN=0,
RSCMNGMODE=SHARE, BWADJ=ON, MAXBW=100, MINBW=50, FLOWCTRLSWITCH=ON,
OPSEPFLAG=OFF;
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=BE,
CARRYFLAG=IPLGCPORT, LPNSN=14, LPN=0, VLANFlAG=DISABLE, PATHCHK=DISABLED;
ACT IPPM: ANI=0, PATHID=1, ISQOSPATH=NO, LOSTPKTDETECTSW=OFF;
//Deactivating dynamic bandwidth control of Iub IP
MOD IPLOGICPORT: SRN=0, SN=14, BT=FG2a, LPN=0, BWADJ=OFF, CIR=100;
DEA IPPM: ANI=0, PATHID=1;
Issue 06 (2013-03-25)

710
RAN14.0
213
Configuring Overbooking on IP
Transmission
Overbooking on IP Transmission.
Prerequisites
l
BSC6900 IP interface boards (PEUa/FG2a/FG2c/GOUa/GOUc board) all support
backpressure mechanism
FG2a/FG2c/GOUa/GOUc/ in BSC6900 support LP shaping.

License
Context
The transmission rate of UMTS services varies during the transmission. For example, the rate
of a speech service is 12.2 kbit/s when someone is speaking and is low when no one is speaking.
Overbooking on IP Transmission helps save transmission resources on the Iub interface,
reducing the CAPEX and OPEX of the operator on transmission resources.
This feature consists of the following algorithms:
l
RLC retransmission rate-based downlink congestion control
Fast backpressure on interface boards
IP shaping
Procedure
Issue 06 (2013-03-25)

711
RAN14.0
Activating RLC retransmission rate-based downlink congestion control

batch modification center: 3.15 Modifying RNC Parameters in Batches) to switch on
flow control.
For R99 BE services, select DRA_R99_DL_FLOW_CONTROL_SWITCH in
For HSDPA BE services, select
Allocation Switch.
Activating backpressure-based downlink congestion control
1.

PORTFLOWCTRLPARA (CME single configuration: UMTS Global
Configuration Express > Transmission Resources Configuration > Port Flow
Control Parameters; CME batch modification center: not supported). In this step,
set Port protocol type to IP and set other flow control parameters.
2.
Switch on flow control.

a.
IP over E1/T1
If the E1/T1 link carries a PPP link, run the BSC6900 MML command
ADD PPPLNK (CME single configuration: NodeB Configuration
Express > IUB_RNC > IP Transport > PPP Link; CME batch
modification center: not supported). In this step, set Flow control
switch to ON.
If the E1/T1 link carries a MP link group, run the BSC6900 MML
command ADD MPGRP (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > MP Group;
CME batch modification center: not supported). In this step, set Flow
control switch to ON.
b.
IP over Ethernet
Run the BSC6900 MML command SET ETHPORT (CME single
configuration: Device Panel > Right click Board > Properties >
Ethernet Port Parameters; CME batch modification center: not
supported). In this step, set Flow control switch to ON.
c.
Optional: Run the BSC6900 MML command ADD IPLOGICPORT (CME

single configuration: NodeB Configuration Express > IUB_RNC > IP
Transport > IP Logical Port; CME batch modification center: not
supported). In this step, set Flow control switch to ON.
Activating IP shaping
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD IPLOGICPORT (CME single

IP Logical Port; CME batch modification center: not supported). In this step, set
Flow control switch to ON(ON).
2.
batch modification center: not supported) to add a logical port. In this step, set
Bearing type to IPLGCPORT.
712
RAN14.0
Take the FE/GE-based IP transmission on the Iub interface as an example to describe how
to verify backpressure-based downlink flow control.
1.
On the BSC6900 LMT, start downlink traffic and bandwidth tracing tasks on the Uu,
Iub, and Iu interfaces.
2.
Register an R99 user UE1 in the HLR. Enable UE1 with streaming services and with
both highest uplink rate and highest downlink rate of 384 Kbit/s.
3.
Register an HSDPA user UE2 in the HLR. Enable UE2 with background services and
with highest uplink rate of 384 Kbit/s and highest downlink rate of 1450 Kbit/s.
4.
Run the BSC6900 MML command ADD TRMMAP to map R99 services to highpriority queue and HSDPA services to low-priority queue.
5.
All IP paths of the RNC are carried on a logical port. Enable the port flow control
when adding the logical port.
6.
Enable UE1 and UE2 to stay in idle mode and camp on the test cell. The test cell must
7.
Use UE1 to perform PS streaming services, that is, use UE1 to download files from
the FTP server.
Expected result: The logical port is not congested and UE1 downloads data at the
highest rate.
8.
Use UE2 to perform PS BE services, that is, use UE2 to download files from the FTP
server.
Expected result: The logical port is congested and the backpressure function is
triggered. The downloading rate of UE2 decreases and that of UE1 remains
unchanged. This is because R99 services have a higher priority.
Deactivating RLC retransmission rate-based downlink congestion control
batch modification center: 3.15 Modifying RNC Parameters in Batches) to switch off
flow control.
For R99 BE services, deselect DRA_R99_DL_FLOW_CONTROL_SWITCH in
For HSDPA BE services, deselect
Allocation Switch.
Deactivating backpressure-based downlink congestion control
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD PPPLNK (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > PPP Link; CME
batch modification center: not supported). In this step, set Flow control switch to
OFF.
2.
Run the BSC6900 MML command MOD MPGRP (CME single configuration:
NodeB Configuration Express > IUB_RNC > IP Transport > MP Group; CME
batch modification center: not supported). In this step, set Flow control switch to
OFF.
3.
Run the BSC6900 MML command SET ETHPORT (CME single configuration:
Device Panel > Right click Board > Properties > Ethernet Port Parameters;
713
RAN14.0
CME batch modification center: not supported). In this step, set Flow control
switch to OFF.
4.

Flow control switch to OFF.
Deactivating IP shaping
1.
Run the BSC6900 MML command MOD IPPATH (CME single configuration:
batch modification center: not supported) to modify a logical port. In this step, set
Bearing type to NULL(NULL).
2.

Flow control switch to OFF(OFF).
3.
batch modification center: not supported) to add a logical port. In this step, set
Bearing type to IPLGCPORT.
----End
Example
//Activating RLC retransmission rate-based downlink congestion control
CH-1;
//Activating backpressure-based downlink congestion control
ADD PORTFLOWCTRLPARA: FCINDEX=10, PORTPROTYPE=IP;
ADD PPPLNK: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=1, DS1=2,
TSBITMAP=TS1-1, BORROWDEVIP=NO, LOCALIP="5.5.5.5",MASK="255.255.255.0",
PEERIP="5.5.5.6", PPPMUX=Enable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON;
ADD MPGRP: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=1,
MPTYPE=MCPPP, BORROWDEVIP=No, LOCALIP="9.9.9.99", MASK="255.255.255.0",
PEERIP="9.9.9.98", MHF=LONG, PPPMUX=Disable, FLOWCTRLSWITCH=ON,
AUTHTYPE=NO_V, ERRDETECTSW=OFF;
SET ETHPORT: SRN=0, SN=27, BRDTYPE=FG2a, FLOWCTRLSWITCH=ON;
ADD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPNTYPE=Leaf, LPN=0,
CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000,
FLOWCTRLSWITCH=ON;
//Activating IP shaping
ADD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPNTYPE=Leaf, LPN=0,
CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000,
FLOWCTRLSWITCH=ON;
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=BE,
TXBW=1000, RXBW=1000, CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=0,
VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Deactivating RLC retransmission rate-based downlink congestion control
CH-0
Issue 06 (2013-03-25)

714
RAN14.0
//Deactivating backpressure-based downlink congestion control

MOD PPPLNK: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=1,
FLOWCTRLSWITCH=OFF;
FLOWCTRLSWITCH=OFF;
SET ETHPORT: SRN=0, SN=27, BRDTYPE=FG2a, FLOWCTRLSWITCH=OFF;
MOD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPN=0, FLOWCTRLSWITCH=OFF;
//Deactivating IP shaping
MOD IPPATH: ANI=0, PATHID=1, ITFT=IUB, CARRYFLAG=NULL;
MOD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPN=0, FLOWCTRLSWITCH=OFF;
Issue 06 (2013-03-25)

715
RAN14.0
214
Configuring IP Routing-Based Hub

NodeB
IP Routing-Based Hub NodeB.
Prerequisites
l
Only 3900 series base stations support this feature.
BTS3902E doesn't support this feature.

License
Context
This feature enables Huawei NodeBs to provide the transmission convergence function in IP
mode, therefore increasing transmission efficiency and reducing transmission costs.
Procedure
l
1.
1.
l
Issue 06 (2013-03-25)
On NodeBs locating on all leaf nodes and root nodes, run the NodeB MML
command ADD IPRT (CME single configuration: NodeB Configuration Express
> IUB_NodeB > IP Transport Layer > IPRoute > IP Route; CME batch
modification center: not supported) to add an IP route from the NodeB to the
BSC6900 or M2000.
Run the NodeB MML command DSP IPRT to query the configuration of the newly
added IP route.
716
RAN14.0
1.
Run the NodeB MML command RMV IPRT (CME single configuration: NodeB
Configuration Express > IUB_NodeB > IP Transport Layer > IPRoute > IP
Route; CME batch modification center: not supported) to remove the IP route.
----End
Example
l
NodeB V200R014
ADD IPRT: SRN=0, SN=7, SBT=BASE_BOARD, DSTIP="11.11.11.11",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.10.10.10";
DSP IPRT: CN=0, SRN=0, SN=7;
RMV IPRT: SRN=0, SN=7, SBT=BASE_BOARD, DSTIP="11.11.11.11",
NodeB V100R014
ADD IPRT: SRN=0, SN=12, SBT=BASE_BOARD, DSTIP="11.11.11.11",
DSP IPRT:;
RMV IPRT: SRN=0, SN=12, SBT=BASE_BOARD, DSTIP="11.11.11.11",
Issue 06 (2013-03-25)

717
RAN14.0
215
Configuring PDCP Header

Compression (RFC2507)
PDCP Header Compression (RFC2507).
Prerequisites
l

License
Others
The UE should support the compression function.
Context
This feature complies with the header compression function of data packet as defined in RFC
2507. It enables the deletion of redundant information such as TCP/IP header. The system
compresses the redundant protocol header before the data is transmitted on a link. In addition,
the system can decompress the received data. This feature can decrease the throughput on the
Uu interface and improve the efficiency of radio links.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches) to select the CFG_PDCP_RFC2507_HC_SWITCH check
box under the Channel configuration strategy switch parameter.
718
RAN14.0
1.
Initiate UE tracing on the BSC6900 LMT.
2.
Establish a PS service on the UE. Observe the CRLC _SETUP_REQ message in the
traced UE data. Check the bit1RfcInfo2507 IE in the following path in the message:
pdcpSetupInfo> pdcpInfo> pdcpInfoBmp> bit1RfcInfo2507.
If the value of the bit1RfcInfo2507 IE is 1, you can infer that this feature has been
activated.
If the value of the bit1RfcInfo2507 IE is 0, you can infer that this feature has not
been activated.
1.

Parameters in Batches) to clear the CFG_PDCP_RFC2507_HC_SWITCH check
box under the Channel configuration strategy switch parameter.
----End
Example
//Activating PDCP Header Compression (RFC2507).
//Deactivating PDCP Header Compression (RFC2507).
Issue 06 (2013-03-25)

719
RAN14.0
216
Configuring RNC Offload
RNC Offload. With this feature, the RNC can send some PS service data directly to Internet
over the offload Gi interface.
Prerequisites
l
The Gi interface between the RNC and the Internet is supported only by the FG2c board
and the GOUc board.

License
Others
The RNC supports the Network Address Translation (NAT) technology.
Context
The RNC Offload function is applied by means of NAT. The RNC analyzes the uplink data flow,
performs NAT on some service data, and then sends the service data to the Internet over the
offload Gi interface. Figure 216-1 shows the offload Gi interface between the RNC and the
Internet.
Figure 216-1 Offload Gi interface
Issue 06 (2013-03-25)

720
RAN14.0
To enable data packets from the Internet to directly arrive at the RNC (instead of the GGSN),
the source IP address of an uplink data packet must be changed to the public IP address of the
offload Gi interface by means of NAT. In this way, the downlink data packets can flow into the
UTRAN over the offload Gi interface.
The RNC Offload function can be configured on the basis of IMEI, IMSI, cell, service type,
Access Point Name (APN), and destination IP address.
Procedure
l
1.
Run the BSC6900 MML command ADD BRD (CME single configuration: Device
Panel > Add Board; CME batch modification center: not supported) to add an FG2c
board.
2.
Run the BSC6900 MML command SET ETHPORT (CME single configuration:
Device Panel > Right click Board > Properties > Ethernet Port Parameters; CME
batch modification center: not supported) to set the Ethernet port attributes of the FG2c
board.
3.
Run the BSC6900 MML command ADD ETHREDPORT (CME single

configuration: Device Panel > Right click Board > Properties > Ethernet Red
Port; CME batch modification center: not supported) to add two Ethernet ports as
active and standby ports.
4.
Run the BSC6900 MML command ADD UGIPORT (CME single configuration: Gi
Configuration Express > IP Transport > Gi port; CME batch modification center:
not supported) to add a Gi interface.
5.
Run the BSC6900 MML command ADD ETHIP (CME single configuration: Gi
Configuration Express > IP Transport > Ethernet Port IP Address; CME batch
modification center: not supported) to add an IP address of the Gi interface.
6.
Run the BSC6900 MML command ADD IPRT (CME single configuration: Gi
Configuration Express > IP Transport > IP Route; CME batch modification center:
not supported) to add a route from the Gi interface to the firewall.
7.
Run the BSC6900 MML command ADD UNATRESPOOL (CME single

configuration: Gi Configuration Express > IP Transport > NAT resource pool;
CME batch modification center: not supported) to add a NAT resource pool.
8.
Run the BSC6900 MML command SET UNATSWITCH (CME single

configuration: Gi Configuration Express > IP Transport > NAT function switch;
CME batch modification center: not supported) to enable the NAT function.
9.
Run the BSC6900 MML command SET UNATALG (CME single configuration: Gi
Configuration Express > IP Transport > NAT function parameters; CME batch
modification center: not supported) to set the Application Level Gateway (ALG)
function for the protocols over the Gi interface.
10. Run the BSC6900 MML command ADD UOFFLOAD (CME single configuration:
UMTS Radio Global Configuration Express > Local Break Out Configuration >
Global SIPTO Parameters; CME batch modification center: not supported) to
configure RNC Offload for the operator.
11. Run the BSC6900 MML command ADD UOFFLOADRAB (CME single
configuration: UMTS Radio Global Configuration Express > Local Break Out
Configuration > SIPTO RAB Restriction; CME batch modification center: not
supported) to configure RNC Offload based on user priority and service type.
12. (Optional) To configure RNC Offload based on IMEI, run the BSC6900 MML
command MOD UOFFLOAD (CME single configuration: UMTS Radio Global
Issue 06 (2013-03-25)

721
RAN14.0
Configuration Express > Local Break Out Configuration > Global SIPTO
Parameters; CME batch modification center: not supported) to enable the TAC-level
offload function. Then, run the BSC6900 MML command ADD
UOFFLOADIMEITAC (CME single configuration: UMTS Radio Global
Configuration Express > Local Break Out Configuration > TAC to Be Enabled
with Offload; CME batch modification center: not supported) to configure the TAClevel offload function. For details about Type Allocation Code (TAC), see the MML
command ADD UIMEITAC (CME single configuration: UMTS Global
Configuration Express > RNC Basic Configuration > IMEI TAC; CME batch
modification center: not supported).
13. (Optional) To configure RNC Offload based on APN, run the BSC6900 MML
command ADD UOFFLOADAPN (CME single configuration: UMTS Radio
Global Configuration Express > Local Break Out Configuration > APN; CME
batch modification center: not supported) to add a registered APN for the operator.
Then, run the BSC6900 MML command MOD UOFFLOAD (CME single
configuration: UMTS Radio Global Configuration Express > Local Break Out
Configuration > Global SIPTO Parameters; CME batch modification center: not
supported) to enable RNC Offload based on APN.
14. (Optional) To configure RNC Offload based on IMSI, run the BSC6900 MML
command ADD UOFFLOADIMSI (CME single configuration: UMTS Radio
Global Configuration Express > Local Break Out Configuration > SIPTO IMSI
Range; CME batch modification center: not supported) to set the range of IMSIs
supporting RNC Offload.
15. (Optional) To configure RNC Offload based on the cell, run the BSC6900 MML
command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) to enable
RNC Offload for the cell.
16. (Optional) To configure RNC Offload based on the destination IP address, run the
BSC6900 MML command ADD UUNOFFLOADIP (CME single configuration:
Host IP Address/Host Network Segment That not Allow Visit in Offload Mode;
CME batch modification center: not supported) to set the IP addresses or network
segment that are not allowed to access the Internet using RNC Offload.
l
Issue 06 (2013-03-25)
1.
On the BSC6900 LMT, choose Monitor > UMTS monitoring, and then double-click
Cell Performance Monitoring. The Cell Performance Monitoring dialog box is
displayed.
2.
Set Monitor Item to Cell User Number, and then set Monitor Period and Cell ID.
Click OK.
3.
Choose Monitor > Common Monitoring. Double-click Link Performance

Monitoring. The Link Performance Monitoring dialog box is displayed.
4.
Set Monitor Item to FE/GE, Subrack No. to 0, Slot No. to 14, Monitor Type to
Port, and FE/GE Port No. to 0. Click OK.
5.
Power on a UE and enable the UE to camp on CELL1. Use the UE to initiate a PS

service.
6.
Check the Cell User Number parameter. The number of UEs supporting RNC Offload
in the cell changes from 0 to 1.
7.
The UE starts data transmission.

722
RAN14.0
8.
l
Check the FE/GE parameter. The data throughput over the FE/GE port increases.
1.
Run the BSC6900 MML command MOD UOFFLOAD (CME single configuration:
Global SIPTO Parameters; CME batch modification center: not supported) to
disable RNC Offload for the operator.
----End
Example
//Configuring the Gi interface
ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=FG2c, SN=14, RED=YES, MPUSUBRACK=0,
MPUSLOT=0;
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0, SPEED=AUTO;
ADD ETHREDPORT: SRN=0, SN=14, PN=0;
ADD UGIPORT: SRN=0, SN=14, PN=0, ISPSSHAREPORT=NO;
ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.53.50.69",
MASK="255.255.255.240";
NEXTHOP="10.53.50.68", PRIORITY=HIGH, REMARK="Gi";
//Configuring the NAT function
ADD UNATRESPOOL: SRN=0, SN=14, PN=0, NATINDEX=0,
STARTADDR="172.168.0.100", ENDADDR="172.168.0.101", MAXPN=65535,
MINPN=10000;
SET UNATSWITCH: NATSW=ON;
SET UNATALG: PROTOCOLTYPE=FTP, ALGSW=ON, AGINGTIMER=600;
//Activating RNC Offload
ADD UOFFLOAD: CnOpIndex=0, OffloadSwitch=ON, NonDTRAB=PERMIT_OFFLOAD;
ADD UOFFLOADRAB: CnOpIndex=0, UserPriority=GOLDEN_USER,
OffloadService=STREAMING-1&INTERACTIVE-1&BACKGROUND-0;
//Configuring RNC Offload based on IMEI
MOD UOFFLOAD: CnOpIndex=0, RsvdPara1=LBO_IMEITAC_SWITCH-1;
ADD UOFFLOADIMEITAC: TAC=12345678, Description="iphone";
//Configuring RNC Offload based on APN
MOD UOFFLOAD: CnOpIndex=0, OffloadSwitch=ON, NonDTRAB=NOT_PERMIT_OFFLOAD,
RegAPN=PERMIT_OFFLOAD;
//Configuring RNC Offload based on IMSI
ADD UOFFLOADIMSI: CnOpIndex=0, IMSIStart="000000000000000",
IMSIEnd="999999999999999";
//Configuring RNC Offload based on the cell
MOD UCELLALGOSWITCH: CellId=111, OffloadSwitch=ON;
//Configuring RNC Offload based on destination IP address
ADD UUNOFFLOADIP: CnOpIndex=0, IpAddr="10.10.10.10",
Mask="255.255.255.255";
//Deactivating RNC Offload
MOD UOFFLOAD: CnOpIndex=0, OffloadSwitch=OFF;
Issue 06 (2013-03-25)

723
RAN14.0
217
Configuring UDP MUX for Iu-CS

Transmission
This section describes how to activate, verify, and deactivate the feature WRFD-050412 UDP
MUX for Iu-CS Transmission.
Prerequisites
l
This feature is supported only by the BSC6900 that is configured with the FG2a/GOUa/
FG2c/GOUc/POUc boards.

The feature WRFD-050409 IP Transmission Introduction on Iu Interface has been
License
Other Prerequisites
The CS CN element (MGW) supports UDP MUX.
The RTCP switch has been opened. Run the BSC6900 MML command ADD
UCNNODE (CME single configuration: UMTS Global Configuration Express >
Core Network > UMTS CN Node; CME batch modification center: not supported) to
set the RTCP SWITCH to ON.
Context
After IP transmission is introduced to the Iu-CS interface, UP packets, especially short packets
like CS packets, cannot be transmitted efficiently after being encapsulated at the RTP, UDP, and
IP layers.
This feature helps solve this problem by using a UDP subheader shorter than UDP to encapsulate
multiple RTP packets into a UDP. This reduces resources used by packet headers and therefore
improves the efficiency of Iu-CS transmission.
Issue 06 (2013-03-25)

724
RAN14.0
This feature supports UDP MUX, regardless of whether compression of RTP headers is enabled.
After this feature is enabled, transmission efficiency can be increased by 30% to 40%, depending
on the number of RTP packets that are encapsulated into a UDP.
Procedure
l
NOTE
Configure IP paths based on the network plan.
1.
1.
Run the BSC6900 MML command ADD IPMUX (CME single configuration: IUCS
Configuration Express > IP Transport > IP MUX Pipe; CME batch modification
center: not supported) or MOD IPMUX (CME single configuration: IUCS
center: not supported) to enable the Iu-CS UDP MUX function. In this step, set IP
MUX Type to UDPMUX, and set Max subframe length[byte], Maximum Frame
Length[byte], and Maximum Delay Time[ms] to appropriate values based on the
network plan. To enable the UDP MUX function for multiple links, run this command
for each of the links.
Run the BSC6900 MML command DSP IPMUX to query the application of UDP
MUX for Iu Transmission. Check whether the feature has been activated based on the
values of IPMUX Status, Number of MUX packets, and Number of MUX Subframes.
1.
Run the BSC6900 MML command RMV IPMUX (CME single configuration: IUCS
center: not supported) to remove the IP MUX paths or run the BSC6900 MML
command MOD IPMUX (CME single configuration: IUCS Configuration
Express > IP Transport > IP MUX Pipe; CME batch modification center: not
supported) to set IP MUX Type to FPMUX.
----End
Example
//Activating UDP MUX for Iu-CS Transmission
ADD IPMUX: MUXTYPE=UDPMUX, SUBFRAMELEN=352, MAXFRAMELEN=1031, FPTIMER=2;
//Checking whether UDP MUX for Iu-CS Transmission has been activated for
an IP MUX path of which the index is 1
DSP IPMUX: IPMUXINDEX=1;
//Deactivating UDP MUX for Iu-CS Transmission
MOD IPMUX: MUXTYPE=FPMUX;
Issue 06 (2013-03-25)

725
RAN14.0
218
Configuring Iu/Iur Transmission

Resource Pool in RNC
Iu/Iur Transmission Resource Pool in RNC.
Prerequisites
l
The GOUc and FG2c boards support this feature.

Configurations of other features on which this feature depends are complete.This feature
depends on features WRFD-050409 IP Transmission Introduction on Iu Interface or
WRFD-050410 IP Transmission Introduction on Iur Interface.
License
Other Prerequisites
The RNC can communicate with an interconnected NE by any route using their
respective user-plane IP addresses.
Deploying this feature on RNC transmission ports that work in active/standby mode
requires Huawei professional services.
Context
With this feature, multiple Iu or Iur interface boards form a transmission resource pool. A
network element (NE) interconnected with the RNC, such as a neighboring RNC (NRNC), the
MGW, the SGSN, or the GGSN, can access all boards in this pool. This helps balance the load
among these boards.
l
Data Preparation
See Data Preparation for Initial Configuration in the Initial Configuration Guide.
Issue 06 (2013-03-25)

726
RAN14.0
Procedure
l
Initial configuration scenarios
Iu-CS interface
1.
See Configuring the Physical Layer and Data Link Layer for the FG2c/GOUc
Board in the Initial Configuration Guide.
2.
See Configuring the Transmission Resource Pool in the Initial Configuration

Guide.
3.
See Configuring the Control Plane of the Iu-CS Interface (over Transmission
Resource Pool) in the Initial Configuration Guide.
4.
See Configuring the User Plane of the Iu-CS Interface (over Transmission
5.
See Configuring the Mapping Between Service Types and Transmission

Resources for the Adjacent Node in the Initial Configuration Guide.
Iu-PS interface
1.
2.

Guide.
3.
See Configuring the Control Plane of the Iu-PS Interface (over Transmission
4.
See Configuring the User Plane of the Iu-PS Interface (over Transmission
5.

Iur interface
1.
2.

Guide.
3.
See Configuring the Control Plane of the Iur Interface (over Transmission
4.
See Configuring the User Plane of the Iur Interface (over Transmission
5.

NOTE
For details about the initial configuration on the CME, see Initial Configuration of the BSC6900
(V900R014) > BSC6900 UMTS Initial Configuration (V900R014) > Configuring the BSC6900 in
the General Configuration Procedure > Configuring Iu-CS Interface Data (in Transmission Resource
Pool Mode)/Configuring Iu-PS Interface Data (in Transmission Resource Pool Mode)/Configuring
Iur Interface Data (in Transmission Resource Pool Mode) in the documentation CD-ROM of (For
Customer) M2000-CME Product Documentation (V200R012)(HDX)-EN.
Reconfiguration scenarios
Iu-CS interface
Issue 06 (2013-03-25)

727
RAN14.0
See Configuring the IP Pool Networking Mode on the Iu-CS Interface in the
Reconfiguration Guide.
Iu-PS interface
See Configuring the IP Pool Networking Mode on the Iu-PS Interface in the
Iur interface
See Configuring the IP Pool Networking Mode on the Iur Interface in the
l
1.
Run the BSC6900 MML commandDSP ETHPORT to query the port rate and work
mode.
Expected result: Speed is 1000M and Duplex is FULL.
2.
Run the BSC6900 MML commandDSP SRCIPRT to check whether the transmitted
and received data over the source IP address uses an interface board in the same slot.
If the values of Number of Packets Sent and Number of Packets Received
increase in the same slot, it indicates that the route priority on the RNC side is
consistent with that on the peer router side.
If the value of Number of Packets Received increases in the active and standby
slots, it indicates that an equal-cost route has been configured from the router to
the RNC. In this case, change the route to active and standby routes.
If the slot where the value of Number of Packets Received increases is different
from the slot where the value of Number of Packets Sent increases, it indicates
that the route priority on the RNC side is inconsistent with that on the peer router
side. In this case, change the route priority.
3.
Run the ping command and check for relevant alarms. Verify that the alarms
ALM-21392 Adjacent Node IP Address Ping Failure, ALM-21393 Adjacent Node IP
Path Ping Failure are not reported and ALM-21394 Transmission Resource Pool Ping
Packet Loss.
4.
Run the BSC6900 MML commandDSP IPPOOL. In this step, check the values of
Send bit rate of the port[bps], Receive bit rate of the port[bps], Send bit rate load
of the board, Receive bit rate load of the board, Send packets load of the board,
and Receive packets load of the board for all egress ports corresponding to the source
IP addresses in transmission resource pools. Verify that these values of the egress
ports are close to each other.
----End
Example
//Refer to the example of a typical configuration script in the Initial
Configuration Guide.
//Not involved.
Issue 06 (2013-03-25)

728
RAN14.0
219
Configuring Iub Transmission

Resource Pool in RNC
Iub Transmission Resource Pool in RNC.
Prerequisites
l
The GOUc and FG2c boards support this feature.
For NodeBs, only the 3900 series base stations support this feature.

Configurations of other features on which this feature depends are complete. This
feature depends on feature WRFD-050402 IP Transmission Introduction on Iub
Interface.
License
Others
The RNC can communicate with an interconnected NE by any route using their
respective user-plane IP addresses.
The requirements for the routers on the RNC side are as follows:
If the RNC boards work in active/standby mode, dynamic routing protocols such as
Open Shortest Path First (OSPF) and Intermediate System-to-Intermediate System
(ISIS) must be configured on the RNC, and policy-based routing must be configured
on routers.
Bidirectional Forwarding Detection (BFD) is configured for static routes on routers,
configuring fast reroute (FRR) is recommended to implement second-level fast
reroute.
Deploying this feature on RNC transmission ports that work in active/standby mode
requires Huawei professional services.
Issue 06 (2013-03-25)

729
RAN14.0
Context
With this feature, multiple Iub interface boards form a transmission resource pool. Each NodeB
interconnected with the RNC can access all boards in this pool. This helps balance the load
among these boards.
l
Data Preparation
Data preparation on the RNC side
See Data Preparation for Initial Configuration in the Initial Configuration Guide.
Data preparation on the NodeB side
Parameter Name
Parameter ID
Setting
Description
Source
Service IP Type
SERVTYPE
None
Internal plan
IP Address
IP
None
Network plan
Procedure
l
Initial configuration scenarios
1.
2.

Guide.
3.
See Configuring the Control Plane of the Iub Interface (over Transmission
4.
See Configuring the User Plane of the Iub Interface (over Transmission
5.

Resources in the Initial Configuration Guide.
6.
See Configuring the OM Channel over the Iub Interface (over Transmission
NOTE
For details about the initial configuration on the CME, see Initial Configuration of the BSC6900
(V900R014) > BSC6900 UMTS Initial Configuration (V900R014) > Configuring the BSC6900
in the General Configuration Procedure > Configuring Iub Interface Data (in Transmission
Resource Pool Mode) in the documentation CD-ROM of (For Customer) M2000-CME Product
Documentation (V200R012)(HDX)-EN.
Issue 06 (2013-03-25)
1.
Run the NodeB MML commandADD DEVIP (CME single configuration:

IPPort > Device IP Address; CME batch modification center: 3.17 Modifying
Physical NodeB Parameters in Batches) to add a device IP address.
2.
Run the NodeB MML commandADD SERVIP (CME single configuration:

NodeB Configuration Express > IUB_NodeB > IP Transport Layer > Basic
Configuration > ServerIP > Service IP; CME batch modification center: not
730
RAN14.0
supported) to add a service IP address. In this step, set Service IP Type to

IUB and IP Address to the device IP address in step 1.
3.
Run the NodeB MML commandADD IPRT (CME single configuration:

IPRoute > IP Route; CME batch modification center: not supported) to add
an IP route.
4.
Run the NodeB MML commandADD SCTPLNK (CME single configuration:

SCTP > SCTP Link; CME batch modification center: 3.17 Modifying
Physical NodeB Parameters in Batches) twice to add two SCTP links for
NCP and CCP, respectively.
5.
Run the NodeB MML commandADD IUBCP (CME single configuration:

NBAP > NBIUBCP; CME batch modification center: not supported) to add
an Iub control port. In this step, set Port Type to NCP.
6.
Run the NodeB MML commandADD IUBCP (CME single configuration:

NBAP > NBIUBCP; CME batch modification center: not supported) to add
an Iub control port. In this step, set Port Type to CCP.
7.
Run the NodeB MML commandSET HSDPAFLOWCTRLPARA (CME

single configuration: NodeB Configuration Express > IUB_NodeB > ATM
Transport Layer > ATMPort > HSDPA Flow Control > HSDPA Flow
Control Parameters; CME batch modification center: not supported) to set
the parameters related to HSDPA flow control. In this step, set Hsdpa
Switch to DYNAMIC_BW_SHAPING.
For details about reconfiguration scenarios,

see Configuring the IP Pool Networking Mode on the Iub Interface in the
l
1.
Run the BSC6900 MML commandDSP ETHPORT to query the port rate and work
mode.
Expected result: Speed is 1000M and Duplex is FULL.
2.
Run the BSC6900 MML commandDSP SRCIPRT to check whether the transmitted
and received data over the source IP address uses an interface board in the same slot.
If the values of Number of Packets Sent and Number of Packets Received
increase in the same slot, it indicates that the route priority on the RNC side is
consistent with that on the peer router side.
If the value of Number of Packets Received increases in the active and standby
slots, it indicates that an equal-cost route has been configured from the router to
the RNC. In this case, change the route to active and standby routes.
If the slot where the value of Number of Packets Received increases is different
from the slot where the value of Number of Packets Sent increases, it indicates
that the route priority on the RNC side is inconsistent with that on the peer router
side. In this case, change the route priority.
3.
Issue 06 (2013-03-25)
Run the ping command and check for relevant alarms. Verify that the alarms
ALM-21392 Adjacent Node IP Address Ping Failure, ALM-21393 Adjacent Node IP
Path Ping Failure are not reported and ALM-21394 Transmission Resource Pool Ping
Packet Loss.
731
RAN14.0
4.
Run the BSC6900 MML commandACT IPPOOLPM to activate performance

detection for the transmission resource pools. Verify that the counters related to IP
performance monitoring (IPPM) are in the normal value range and the alarm
ALM-21395 Adjacent Node IP Path Excessive Packet Loss Rate is not reported.
5.
Run the BSC6900 MML commandDSP IPPOOL. In this step, check the values of
Send bit rate of the port[bps], Receive bit rate of the port[bps], Send bit rate load
of the board, Receive bit rate load of the board, Send packets load of the board,
and Receive packets load of the board for all egress ports corresponding to the source
IP addresses in transmission resource pools. Verify that these values of the egress
ports are close to each other.
----End
Example
//Refer to the example of a typical configuration script in the Initial
Configuration Guide.
//Not involved.
Issue 06 (2013-03-25)

732
RAN14.0
220
Configuring Satellite Transmission

on Iub Interface
Satellite Transmission on Iub Interface.
Prerequisites
l

License
Context
This feature supports satellite transmission on the Iub interface, which is useful to cover remote
areas, such as an island.
When satellite transmission is applied over the Iub interface, the delay increases. The default
setting of the SAAL/SCTP timer on the Iub interface can meet the satellite transmission
requirements.
Procedure
l
Issue 06 (2013-03-25)
1.
NodeB; CME batch modification center: not supported). In this step, set Satellite
Trans Ind to TRUE, and set IUB Transport Delay to 600.
2.
Modifying UMTS Cell Parameters in Batches) to activate a cell.
733
RAN14.0
1.
Run the BSC6900 MML command DSP UCELL to check whether cell settings are
successful.
2.
Establish an AMR service in the cell. The AMR service is established successfully
and the speech quality is satisfactory.
3.
Establish a PS BE service in a cell. The service is established successfully and the

data download rate is steady.
1.
2.
NodeB; CME batch modification center: not supported). In this step, set Satellite
Trans Ind to FALSE, and set IUB Transport Delay to 10.
----End
Example
//Activating Satellite Transmission on Iub Interface
MOD UNODEB: IDTYPE=BYID, NodeBId=1, TRANSDELAY=600, SATELLITEIND=TRUE;
//Deactivating Satellite Transmission on Iub Interface
MOD UNODEB: IDTYPE=BYID, NodeBId=1, TRANSDELAY=10, SATELLITEIND=FALSE;
Issue 06 (2013-03-25)

734
RAN14.0
221
Configuring Satellite Transmission

on Iu Interface
Satellite Transmission on Iu Interface.
Prerequisites
l

License
Context
This feature solves the communication problems of base stations in remote areas, such as remote
regions, islands, and deserts, where there is no transmission system or the terrestrial transmission
system is difficult to deploy
Satellite transmission may bring extra delay and therefore timers of signaling plane and user
plane need to be adjusted to prevent transmission delay from causing data loss.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD SAALLNK (CME single configuration:
IUCS Configuration Express > ATM Transport > SAAL Signaling Link; CME
batch modification center: not supported) or MOD SAALLNK (CME single
configuration: IUCS Configuration Express > ATM Transport > SAAL Signaling
Link; CME batch modification center: not supported) to add or modify the settings
of SAAL links on the Iu interface. Modify the values of parameters associated with
satellite transmission, as described in Table 221-1.
735
RAN14.0
Table 221-1 Timers related to SAAL links of satellite transmission

Parameter ID
Parameter
Name
Default Value
Recommended
Value
MPS
Management
proving status
MPS_NEUTRAL
MPS_EMERGEN
CY
CCTMR
Timer_CC{ms}
200
800
POLLTMR
Timer_Poll{ms}
100
300
IDLETMR
Timer_Idle{ms}
500
3000
RSPTMR
Timer_NoResponse{ms}
1500
3000
KEEPTMR
Timer_KeepAlive{ms}
100
1000
NOTE
In the signaling plane of the Iu interface, except that the timer of SAAL links is set to a smaller
value, timers of other links are set to 1s or longer. The delay of satellite transmission is about 600
ms and therefore the settings of timers in other signaling planes do not need to be changed. Timers
of links in the user plane of the Iu interface are also set to 1s or longer and do not need to be changed,
either.
1.
Run the BSC6900 MML command LST SAALLNK to check whether the setting of
the timer is modified correctly.
2.
Run the BSC6900 MML command DSP SAALLNK to query the status of SAAL
links. The result shows that SAAL link state is AVAILABLE.
1.
Run the BSC6900 MML command MOD SAALLNK (CME single configuration:
IUCS Configuration Express > ATM Transport > SAAL Signaling Link; CME
batch modification center: not supported) to change associated parameters to the
default values.
----End
Example
//Activating Satellite Transmission on Iu Interface
MOD SAALLNK: SRN=0, SN=0, SAALLNKN=1, CARRYT=NCOPT, CARRYSRN=0,
CARRYSN=14, CARRYNCOPTN=0, SAALLNKT=NNI, CCTMR=800, POLLTMR=300,
IDLETMR=3000, RSPTMR=3000, KEEPTMR=1000;
Issue 06 (2013-03-25)

736
RAN14.0
222 Configuring Clock Synchronization on Ethernet in

NodeB
222
Configuring Clock Synchronization

on Ethernet in NodeB
Clock Synchronization on Ethernet in NodeB.
Prerequisites
l

License
Others
Huawei clock server should support this feature.
Context
This feature provides a solution for clock synchronization in the all-IP network. The clock
synchronization of the base station can be achieved for the operator without changing the existing
data network and introducing additional QoS requirements for the transport network.
Procedure
l
NodeB V200R014
Issue 06 (2013-03-25)
1.
Run the NodeB MML command ADD IPCLKLINK (CME single configuration:
IPCLKLNK > IP Clock Link Management; CME batch modification center: not
supported) to add an IP clock link.
2.
737
RAN14.0

NodeB
Set Clock Working Mode to MANUAL(Manual).
Set Selected Clock Source to IPCLK(IP Clock).
1.
Run the NodeB MML command DSP IPCLKLINK to query the running status of
all IP clock links.
Expected result: The value of Link Available State is Available.
2.
Run the NodeB MML command DSP CLKSTAT to query the status of the system
clock.
1.
supported) to set the working mode of the reference clock source. Set Clock Working
Mode to FREE(Free).
2.
Run the NodeB MML command RMV IPCLKLINK (CME single configuration:
supported) to remove a specified IP clock link.
NodeB V100R014
1.
Run the NodeB MML command ADD IPCLKLINK (CME single configuration:
supported) to add an IP clock link.
2.
Set System Clock Working Mode to MANUAL(Manual).
Set Clock Source Type to IPCLK(IP clock source).
1.
Run the NodeB MML command DSP IPCLKLINK to query the running status of
all IP clock links.
Expected result: The value of IP Clock Link Status is Normal.
2.
Run the NodeB MML command DSP CLKSTAT to query the status of the system
clock.
1.
Issue 06 (2013-03-25)
738
RAN14.0

NodeB
supported) to set the working mode of the reference clock source. Set System Clock
Working Mode to FREE(Free).
2.
Run the NodeB MML command RMV IPCLKLINK (CME single configuration:
supported) to remove a specified IP clock link.
----End
Example
l
NodeB V200R014
ADD IPCLKLINK: ICPT=HW_DEFINED, SN=7, CIP="82.0.1.107",
SIP="82.0.1.128";
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SYNMODE=OFF;
DSP IPCLKLINK:;
DSP CLKSTAT: SN=7;
SET CLKMODE: MODE=FREE;
RMV IPCLKLINK:;
NodeB V100R014
ADD IPCLKLINK: SRN=0, SN=12, CIP="11.11.11.11", SIP="10.10.12.12",
ICPT=HW_DEFINED;
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, IPMODE=AUTO;
DSP IPCLKLINK: SN=12;
DSP CLKSTAT:;
RMV IPCLKLINK: SRN=0, SN=12;
Issue 06 (2013-03-25)

739
RAN14.0
223
Configuring Synchronous Ethernet
Synchronous Ethernet.
Prerequisites
l
Only the BSC6900 supports this feature.
Only the 3900 series base stations support this feature.

feature depends on features WRFD-050402 IP Transmission Introduction on Iub
Interface.
License
Others
The synchronous Ethernet technology requires that all the equipments on the clock relay
path must support the synchronous Ethernet.
Context
This feature provides the solution for clock synchronization in all-IP networking scenarios. It
enables the clock extraction and recovery in the physical layer of the Ethernet.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the NodeB MML command ADD SYNCETH (CME single configuration:
Source > Synchronous Ethernet Clock Link Management; CME batch
modification center: not supported) to add a synchronous-Ethernet clock link.
2.
740
RAN14.0
Set Clock Working Mode to MANUAL(Manual).
Set Selected Clock Source to SYNCETH(SyncEth Clock).
l
1.
clock source.
1.
supported) to set the working mode of the reference clock source. In this step, set
Clock Working Mode to FREE(Free).
2.
Run the NodeB MML command RMV SYNCETH (CME single configuration:
Source > Synchronous Ethernet Clock Link Management; CME batch
modification center: not supported) to remove a synchronous-Ethernet clock link.
----End
Example
ADD SYNCETH: SN=7, PN=0;
SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH;
DSP CLKSTAT: SN=7:;
RMV SYNCETH:;
Issue 06 (2013-03-25)

741
RAN14.0
224
Configuring Ethernet OAM
Ethernet OAM. (This feature cannot be configured using the CME. )
Prerequisites
l
Dependency on RNC Hardware

RAN11.0, BTS3812E/AE and DBS3800 can only support IEEE 802.1ag draft 7. 3900
series NodeB can support IEEE 802.3ah and IEEE 802.1ag draft 7.
RAN12.0, BTS3812E/AE, DBS3800, 3900 series NodeB can support both IEEE
802.3ah and IEEE 802.1ag draft 8.

feature depends on the feature WRFD-050402 IP Transmission Introduction on the Iub
Interface, or WRFD-050409 IP Transmission Introduction on the Iu Interface, or
WRFD-050410 IP Transmission Introduction on the Iur Interface.
License
Context
With the evolution from WCDMA to IPRAN, the Ethernet transmission network is widely used.
As a layer-2 protocols, the Ethernet OAM can report the status of the network on the data link
layer. In this way, the Ethernet can be more efficiently monitored and managed. The Ethernet
OAM functions include detection, notification, verification, and fault location functions. These
faults include the hard faults (such as the link interruption) that can be detected on the physical
layer or the soft faults (such as the fault of the memory or the bridge) that cannot be detected on
the physical layer. The Ethernet OAM plays a significant role in cutting the CAPEX/OPEX cost
and complies with the service level (SLA).
The RAN supports two kinds of Ethernet OAM features, that is, the PPP Ethernet OAM feature
defined by the 802.3ah and the E2E Ethernet OAM defined by 802.1ag.
1.
PPP Ethernet OAM

The PPP Ethernet OAM complies with the IEEE 802.3ah protocol. It is the last-mile OAM
solution. It implements the PPP maintenance of the Ethernet through detection, loopback,
Issue 06 (2013-03-25)

742
RAN14.0
link monitoring, and fault detection and is not service, and it is not service-specific, as
Figure 224-1 PPP Ethernet OAM network
2.
E2E Ethernet OAM

The E2E Ethernet OAM complies with IEEE 802.1ag draft 7 or IEEE 802.1ag draft 8. It
is implemented based on services, maintenance domains, and E2E detection.
Procedure
l
Activating the Ethernet OAM 3AH Function

1.
Run the BSC6900 MML command ACT EFMAH to activate the Ethernet OAM 3AH
function.
NOTE
The OAM 3AH function on peer equipment must be activated.
Activating the Ethernet OAM 1AG Function

1.
Run the BSC6900 MML command ADD CFMMD to add the Ethernet OAM
maintenance domain (MD). The Ethernet OAM MD consists of bridges and
maintenance equipment. Each MD is associated with a maintenance level. There are
eight maintenance levels, that is level 0 to level 7.
2.
Run the BSC6900 MML command ADD CFMMA to add the Ethernet OAM
maintenance association (MA). Each MD can be divided into several MAs. Each MA
corresponds to a service instance identified by the VLAN in the MD.
3.
Run the BSC6900 MML command ADD CFMMEP to add an Ethernet OAM
maintenance end point (MEP). You can add different local or remote maintenance
points of different MEP types to the MA.
NOTE
l The MEPID of the RemoteMep configured on the peer equipment must be consistent with
the MEPID of the LocalMep configured on the local equipment.
l MD, MA or MEP must be configured on the peer equipment when the MD, MA or MEP
has be added on BSC6900.
4.
Verifying the Ethernet OAM 3AH Function

1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ACT CFMCCMTST to activate the Ethernet
OAM unidirectional connectivity detection between the local MEP and the remote
MEP.
Activate the Ethernet OAM 3AH function. The Alarm-21371 ETHOAM 3AH
Detection Failure alarm is reported when Ethernet OAM detection fails. The
743
RAN14.0
ALM-21345 Ethernet Link Fault alarm is report when Ethernet OAM detection is
enable, because link on local end and peer end fails.
2.
Verifying the Ethernet OAM 1AG Function

1.
Activate the Ethernet OAM 1AG function. The running of the PING MAC and TRC
MAC fails if the transmission between the local MEP and the remote MEP is faulty
because the local MEP fails to receive the connectivity detection packet from the
remote MEP.
2.
OAM 1AG function on the peer equipment must be activated, and the transmission is
functional that the local MEP succeeds to receive the CCM packets from the peer
MEP, the running of the PING MAC and TRC MAC succeeds.
Deactivating the Ethernet OAM 3AH Function

1.
Activate the Ethernet OAM 3AH loopback function. If the loopback succeeds, the
Alarm-21374 ETHOAM 3AH Remote Loopback is reported due to service
congestion.
Run the BSC6900 MML command DEA EFMAH to deactivate the Ethernet OAM
3AH function.
Deactivating the Ethernet OAM 1AG Function

1.
Run the BSC6900 MML command DEA CFMCCMTST to deactivate the Ethernet
OAM unidirectional connectivity detection.
2.
Run the BSC6900 MML command RMV CFMMD to delete the Ethernet OAM
maintenance domain (MD).
3.
Run the BSC6900 MML command RMV CFMMA to delete the Ethernet OAM
maintenance association (MA).
4.
Run the BSC6900 MML command RMV CFMMEP to delete the Ethernet OAM
maintenance end point (MEP).
----End
Example
//Activating the Ethernet OAM 3AG function
ACT EFMAH: SRN=0, SN=18, PN=0;
//Activating the Ethernet OAM 1AG function
ADD CFMMD: SRN=0, SN=18, MDIDX=0, MDName="md0";
ADD CFMMA: SRN=0, SN=18, MDIDX=0, VLANID=2, MAIDX=0, MANAME="ma0";
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=LocalMep, MEPID=1, PORTTYPE=ETHER,
SN=18, PN=0;
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=RemoteMep, MEPID=11, SN=18;
ACT CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
//Verifying the Ethernet OAM 1AG function
PING MAC: SRN=0, SN=18, MAIDX=0, SRCMEPID=1, DESTMEPID=11;
TRC MAC: SRN=0, SN=18, MAIDX=0, SRCMEPID=1, DESTMEPID=11;
//Deactivating the Ethernet OAM 3AG function
DEA EFMAH: SRN=0, SN=18, PN=0;
//Deactivating the Ethernet OAM 1AG function
DEA CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
RMV CFMMD: SRN=0, SN=18, MDIDX=0;
RMV CFMMA: SRN=0, SN=18, MAIDX=0;
RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=11;
RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=1;
Issue 06 (2013-03-25)

744
RAN14.0
225
Configuring RNC Node Redundancy
RNC Node Redundancy.
Prerequisites
l
This feature does not depend on hardware.

License
Others
The Iur, Iu-CS, Iub and Iu-PS interfaces have been configured. For details, see
Configuring the Interfaces.
Context
This feature improves the reliability and robustness of RAN and shortens the service interruption
due to single-point failure in the RNC. In this way, the service quality is improved. With this
feature, a NodeB can be connected to two RNCs and heartbeat detection is performed on the Iur
interface between the two RNCs. When the primary RNC is faulty, the NodeB can be fast
switched to the secondary RNC for service provisioning.
The primary RNC and the secondary RNC form an RNC pool, as shown in Figure 225-1 and
Figure 225-2.
Issue 06 (2013-03-25)

745
RAN14.0
Figure 225-1 Network topology not configured with RNC pool
Figure 225-2 Network topology configured with RNC pool
NOTE
l When the serving RNC is faulty, the maximum service capability (such as CS Erlang and PS
throughput) decreases from the combined capability of two RNCs to the capability of one RNC. As a
result, the processing specifications of the network decrease.
l To activate this feature, data configurations related to this feature are required on the RNC and the
NodeB. The CN and M2000 do not require data configurations specific to this feature. You can check
the homing state of the NodeB on the M2000.
Procedure
l
Issue 06 (2013-03-25)

746
RAN14.0

NOTE
This document uses RNC202, RNC203, and NodeB1 as examples to describe the procedures. Assume
that RNC202 and RNC203 are initially configured as the primary homing and secondary homing
RNC of NodeB1 respectively.
1.
Data configurations on the primary homing RNC (RNC202)

a.
Run the BSC6900 MML command ADD URNCPOOL (CME single

configuration: UMTS Global Configuration Express > Redundancy Backup
Configuration > RNC Pool; CME batch modification center: not supported) to
add an RNC pool. In this step, set the parameters such as RncPool Index,
RncPool Name, Supporting Auto-Rehoming Switch and so on.
CAUTION
If the license is activated , the primary homing RNC is physically broken down
and Supporting Auto-Rehoming Switch is set to OFF, the feature
WRFD-040300 License Control for Urgency will be activated.
WRFD-040300 License Control for Urgency can be enabled only fifteen times
for each R version for this kind of reason.
2.
b.
Run the BSC6900 MML command ADD URNCPOOLMEMBER (CME single

Configuration > RNC Pool Member; CME batch modification center: not
supported) to add the primary homing RNC (RNC203) to the RNC pool.
c.
Run the BSC6900 MML command ACT URNCPOOL (CME single

configuration: UMTS GLOBAL Configuration Express > Redundancy
Backup Configuration > RNC Pool. Set active status to Activated; CME batch
modification center: not supported) to activate the RNC node redundancy feature.
d.
Add a NodeB (NodeB1) of which the primary homing RNC is RNC202: Run the
BSC6900 MML command ADD UNODEB (CME single configuration: Main
View > Right Click RNC > Create Logical NodeB; CME batch modification
center: not supported) to add a NodeB of which the primary homing RNC is
RNC202.
e.

modification center: not supported) to add the cell to the primary homing RNC
and specify the peer cell ID under the secondary homing RNC.
f.
Run the BSC6900 MML command SET UPOOLPRIMHOSTPOLICY (CME

single configuration: UMTS Global Configuration Express > Redundancy
Backup Configuration > Re-host Policy; CME batch modification center: 3.15
Modifying RNC Parameters in Batches) to set the rehoming strategy of the
NodeB.
Data configurations on the secondary homing RNC (RNC203)

a.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD URNCPOOL (CME single

Configuration > RNC Pool; CME batch modification center: not supported) to
add an RNC pool. In this step, set the parameters such as RncPool Index,
RncPool Name, Supporting Auto-Rehoming Switch and so on.
747
RAN14.0
CAUTION
If the license is activated , the secondary homing RNC is physically broken down
and Supporting Auto-Rehoming Switch is set to OFF, and the feature
WRFD-040300 License Control for Urgency will be activated.
WRFD-040300 License Control for Urgency can be enabled only fifteen times
for each R version for this kind of reason.
3.
b.
Run the BSC6900 MML command ADD URNCPOOLMEMBER (CME single

Configuration > RNC Pool Member; CME batch modification center: not
supported) to add the primary homing RNC (RNC202) to the RNC pool.
c.
Run the BSC6900 MML command ACT URNCPOOL (CME single

configuration: UMTS GLOBAL Configuration Express > Redundancy
Backup Configuration > RNC Pool. Set active status to Activated; CME batch
modification center: not supported) to activate the RNC node redundancy feature.
d.
Add a NodeB (NodeB1) of which the secondary homing RNC is RNC203: Run
the BSC6900 MML command ADD UNODEB (CME single configuration:
modification center: not supported) to add a NodeB of which the secondary
homing RNC is RNC203.
e.

modification center: not supported) to add the cell to the secondary homing RNC
and specify the peer cell ID under the primary homing RNC.
Data configurations on the NodeB (NodeB1) side

a.
b.
a.
Run the NodeB MML command ADD IUBCP (CME single configuration:
NodeB Configuration Express > IUB_NodeB > ATM Transport
Layer > NBAP > NBIUBCP; CME batch modification center: not
supported) to add an NCP link.
b.
supported) to add a CCP link.
Configure information about the secondary homing RNC.

a.
supported) to add an NCP link.
b.
supported) to add a CCP link.
1.
Method 1: Verifying data configurations

a.
Issue 06 (2013-03-25)
Configure information about the primary homing RNC.
Run the BSC6900 MML command DSP UCELL on the RNC202 LMT. The
query result shows that cell 1 is functional. Run the BSC6900 MML command
748
RAN14.0
DSP UCELL on the RNC203 LMT. The query result shows that cell 2 is
unavailable due to no control rights.
b.
Perform an emulation test of the primary RNC fault.

Run the BSC6900 MML command RST UIU on RNC202 to make RNC202
become faulty.
If the BSC6900 recovers too fast after the BSC6900 MML command RST
UIU is executed, you can remove the cable on the Iu-CS/Iu-PS interface
instead.
c.
After RNC203 detects that RNC202 is faulty through the Iur interface, RNC203
takes over the NodeB and initiates cell2 reestablishment.
d.
(Optional) When the connection between the NodeB and the primary homing
RNC is disconnected, the secondary homing RNC cannot obtain the NodeB
control rights automatically. To solve this problem, run the BSC6900 MML
command FOC UHOSTNODEB on the RNC203 LMT to manually switch over
the NodeB control rights to the secondary homing RNC.
CAUTION
Switching over NodeB control rights manually disrupts the ongoing services
when the connection between the NodeB and the primary homing RNC is normal.
e.
2.
On both the RNC203 LMT and the RNC202 LMT, run the BSC6900 MML
command DSP UCELL. If the query result on the RNC203 LMT shows that cell
2 is operational and the query result on the RNC202 LMT shows that cell 1 is
unavailable due to no control rights, this feature has been activated. Otherwise,
this feature is not activated.
Method 2: Verifying services

a.
Check whether the heartbeat between RNC202 and RNC203 is normal, as shown
in Figure 225-3.
Figure 225-3 Normal heartbeat between RNC202 and RNC203
b.
Issue 06 (2013-03-25)
Check that the cell under RNC202 is available, and then use the UE to establish
a CS AMR service, as shown in Figure 225-4 and Figure 225-5.

749
RAN14.0
Figure 225-4 NodeB control rights obtained by RNC202
Figure 225-5 CS AMR service set up successfully
3.
c.
Power off RNC202 when RNC203 works properly. RNC203 then takes over the
NodeB control rights.
d.
When RNC202 restores normal services, it takes over the NodeB control rights
again according to the rehoming strategy, and RNC203 releases the NodeB
control rights.
Method 3: Verifying this feature on the M2000

a.
Create the RNCs and NodeB on the RNC POOL monitor of the M2000. When
creating a NodeB, the M2000 checks the homing state of the NodeB. If the RNC
is the secondary homing RNC of the NodeB, the NodeB cannot be created under
that RNC.
b.
When the M2000 starts, it starts NE status subscribing. When the homing state
of the NodeB changes, the RNC reports the NodeB homing state to the M2000.
The M2000 then updates the network topology displayed in the RNC POOL
monitor.
1.
On RNC202 and RNC203, run the BSC6900 MML command DEA URNCPOOL
(CME single configuration: UMTS GLOBAL Configuration Express >
Redundancy Backup Configuration > RNC Pool. Set active status to
Deactivated; CME batch modification center: not supported) to deactivate the feature.
----End
Issue 06 (2013-03-25)

750
RAN14.0
Example
/*Data configuration script on the primary homing RNC side*/
/*Configuring an RNC pool*/
ADD URNCPOOL: RncPoolIndex=0, RncPoolName="redundancy_RNCPOOL";
ADD URNCPOOLMEMBER: RncPoolIndex=0, NrncId=203;
ACT URNCPOOL: RncPoolIndex=0;
//Adding a dual-homing NodeBADD UNODEB: NodeBName="Redundancy_NODEB500",
NodeBId=500, SRN=0, SN=0, SSN=1,
TnlBearerType=IP_TRANS,IPTRANSAPARTIND=NOT_SUPPORT, HostType=PRIMHOST,
PeerRncId=203, PeerNodebId=500, SharingType=RANSHARING;
//Setting cell parameters
ADD UCELLQUICKSETUP: CellId=1, CellName="Redundancy_NODEB500_00",
PeerIsValid=VALID, PeerCellId=2, CnOpGrpIndex=0, BandInd=Band1,
UARFCNDownlink=10668, PScrambCode=500, TCell=CHIP0, LAC=H'0046,
SAC=H'0000, CfgRacInd=REQUIRE, RAC=H'00, SpgId=1, URANUM=D1, URA1=0,
NodeBName="Redundancy_NODEB500", LoCell=500, SupBmc=FALSE;
/*Data configuration script on the secondary homing RNC side*/
/*Configuring an RNC pool*/
ADD URNCPOOL: RncPoolIndex=0, RncPoolName="redundancy_RNCPOOL";
ADD URNCPOOLMEMBER: RncPoolIndex=0, NrncId=202;
ACT URNCPOOL: RncPoolIndex=0;
//Adding a dual-homing NodeB
ADD UNODEB: NodeBName="Redundancy_NODEB500", NodeBId=500, SRN=0, SN=0,
SSN=1, TnlBearerType=IP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT,
HostType=SECHOST, PeerRncId=202, PeerNodebId=500, SharingType=RANSHARING;
//Setting cell parameters
ADD UCELLQUICKSETUP: CellId=2, CellName="Redundancy_NODEB500_00",
PeerIsValid=VALID, PeerCellId=1, CnOpGrpIndex=0, BandInd=Band1,
UARFCNDownlink=10668, PScrambCode=500, TCell=CHIP0, LAC=H'0046,
SAC=H'0000, CfgRacInd=REQUIRE, RAC=H'00, SpgId=1, URANUM=D1, URA1=0,
NodeBName="Redundancy_NODEB500", LoCell=500, SupBmc=FALSE;
/*Data configuration script on the NodeB side*/
/*Configuring information about the primary homing RNC on the NodeB*/
/*Configuring NCP and CCP*/
ADD IUBCP: CPPT=NCP, BEAR=IPV4;
ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=1;
/*Configuring information about the secondary homing RNC on the NodeB*/
/*Configuring NCP and CCP*/
ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=2, BELONG=SLAVE;
ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=3, BELONG=SLAVE;
/*Verifying RNC Node Redundancy*///RNC202
//RNC203
//RNC202
RST UIU: CnOpIndex=0, CNDOMAINID= ALL_DOMAIN, RSTCNTYPE=ALL_NODES;
//RNC202
Issue 06 (2013-03-25)

751
RAN14.0
//RNC203
//Deactivating RNC Node Redundancy
//RNC202&RNC203
DEA URNCPOOL: RncPoolIndex=0;
Issue 06 (2013-03-25)

752
RAN14.0
226
Configuring RRU Redundancy
RRU Redundancy.
Prerequisites
l

License
Context
RRU redundancy can improve the reliability and robustness of the RAN and shorten the duration
of service disruption caused by an RRU failure, improving service quality.
Procedure
l
l
Issue 06 (2013-03-25)
1.
If a cell is configured as a MIMO cell or a transmit diversity cell, run the BSC6900
MML command ADD UCELLALGOSWITCH (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell Algorithm Switches; CME
batch modification center: 3.18 Modifying UMTS Cell Parameters in Batches) or
modification center: 3.18 Modifying UMTS Cell Parameters in Batches). In this
step, set Cell Capability Auto Handle Switch to TX_DIVERSITY_ON_TO_OFF
(TX diversity capability is on to off) or TX_DIVERSITY_OFF_TO_ON(TX
diversity capability is off to on). Both the options can be selected.
2.
Batches) to ensure the local cell uses two power amplifiers.
753
RAN14.0
1.
Run the BSC6900 MML command LST UCELLALGOSWITCH to check that Cell
Capability Auto Handle Switch is set to TX diversity capability is on to off::ON
or TX diversity capability is off to on::ON.
2.
Run the NodeB MML command LST LOCELL to query whether the local cell is
configured with two power amplifiers.
----End
Example
//When a cell is configured as a MIMO and transmit diversity cell, do as
follows:
ADD UCELLALGOSWITCH: CellId=1, NBMUlCacAlgoSelSwitch=ALGORITHM_SECOND,
NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND,
CellCapacityAutoHandleSwitch=TX_DIVERSITY_ON_TO_OFF-1&TX_DIVERSITY_OFF_TO
_ON-1;
//Or
CellCapacityAutoHandleSwitch=TX_DIVERSITY_ON_TO_OFF-1&TX_DIVERSITY_OFF_TO
_ON-1;
//Ensure that the local cell uses two power amplifiers.
ADD LOCELL: LOCELL=0, STN=0, SECN=0, SECT=REMOTE_SECTOR, RADIUS=10000,
HORAD=150, TTW=TRUE, SRN1=60, SRN2=61, SN2=0, ULFREQ=9610, DLFREQ=10560,
MXPWR=430, HISPM=TRUE, SPR=250, RMTCM=FALSE, VAM=FALSE;,
//Querying the cell algorithm switch
LST UCELLALGOSWITCH: CellId=1;
//Checking whether the local cell is configured with two power
amplifiers
Issue 06 (2013-03-25)

754
RAN14.0
227
Configuring Iu Flex
Iu Flex.
Prerequisites
l

License
Others
The MSC and the serving GPRS support node (SGSN) support this feature.
Context
This feature allows one BSC6900 to connect to multiple MSCs and/or SGSNs, and these CS/
PS domain nodes can form different pools that serve the same pool area.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command SET UOPERATORCFGPARA (CME single

RNC Operator Configuration Information; CME batch modification center: not
supported). In this step, set Feature Supporting Mode of CS Domain to
SUPP_IUFLEX, set Feature Supporting Mode of PS Domain to
SUPP_IUFLEX, and set Length of CS NRI in bits and Length of PS NRI in bits
2.
Configure the Iu interface transmission between BSC6900 and multiple core networks
(CNs) by referring to Configuring the Interfaces.
3.
755
RAN14.0
batch modification center: not supported) to add multiple CN nodes for an operator
4.
Run the BSC6900 MML command ADD UNRIGLBCNIDMAP (CME single

configuration: UMTS Global Configuration Express > Core Network > NRI And
CN Node Mapping Information; CME batch modification center: not supported).
In this step, set Cn Operator Index, CN node ID, and Network resource identity
to configure the mapping relationships between NRI and CN nodes.
5.
Optional: Run the BSC6900 MML command ADD UIMSIIDNNSCNIDMAP

(CME single configuration: UMTS Global Configuration Express > Core
Network > IMSI Route Parameters and CN Node Mapping Information; CME
batch modification center: not supported) to configure the mapping relationships
between international mobile subscriber identity (IMSI) ranges and CN nodes.
After configuring the mapping relationships, the RNC routes the UE whose IMSI is
within the IMSI range to the specified CN.
1.
Enable the UE to access a cell and register in the cell.
2.
According to the mapping relationships between IMSI ranges and CN nodes and the
load balance algorithm, the RNC selects a CN node for the UE, and the UE registers
successfully.
3.
Then, if the UE initiates a service, the RNC routes the UE to the corresponding CN
node according to the mapping relationships between NRI and CN nodes.
1.
Run the BSC6900 MML command RMV UIMSIIDNNSCNIDMAP (CME single

configuration: UMTS Global Configuration Express > Core Network > IMSI
Route Parameters and CN Node Mapping Information; CME batch modification
center: not supported) to remove IMSI Route Parameters and CN Node Mapping
Information (Keep Mapping of one CN Node).
2.
Run the BSC6900 MML command RMV UNRIGLBCNIDMAP (CME single

configuration: UMTS Global Configuration Express > Core Network > NRI And
CN Node Mapping Information; CME batch modification center: not supported) to
remove NRI and all of CN Node Mapping Information.
3.
Run the BSC6900 MML command RMV UCNNODE (CME single configuration:
batch modification center: not supported) to remove CN Node (Keep one CN Node).
4.

RNC Operator Configuration Information; CME batch modification center: not
supported) to deactivate this feature. In this step, set Feature Supporting Mode of
CS Domain to SUPP_NONE, set Feature Supporting Mode of PS Domain to
SUPP_NONE.
----End
Example
//Activating Iu Flex
//Configuring the RNC supporting Iu Flex with Length of CS NRI in bits and
Length of PS NRI in bits set to appropriate values
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX,
PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, PSNRILength=5;
Issue 06 (2013-03-25)

756
RAN14.0
//Configuring the first CN node

CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000,
TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;
//Configuring the second CN node
//Configuring the mapping relationship between NRI and the first CN node
//Configuring the mapping relationship between NRI and the second CN node
//Configuring the mapping relationship between the IMSI range and the
first CN node
ADD UIMSIIDNNSCNIDMAP: ImsiRtMin=0, ImsiRtMax=666, CnOpIndex=1, CNId=17;
//Configuring the mapping relationship between the IMSI range and the
second CN node
ADD UIMSIIDNNSCNIDMAP: ImsiRtMin=667, ImsiRtMax=999, CnOpIndex=1,
CNId=18;
//Deactivating Iu Flex
RMV UIMSIIDNNSCNIDMAP: ImsiRtMin=667, ImsiRtMax=999, CnOpIndex=1,
CNId=18;
RMV UNRIGLBCNIDMAP: CnOpIndex=1, CNId=18, NRI=9;
RMV UNRIGLBCNIDMAP: CnOpIndex=1, CNId=17, NRI=8;
RMV UCNNODE: CnOpIndex=1, CNId=18;
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_NONE,
PsNriCfgMode=SUPP_NONE;
Issue 06 (2013-03-25)

757
RAN14.0
228
Configuring Iu Flex Load
Distribution Management
Iu Flex Load Distribution Management.
Prerequisites
l

The feature WRFD-021302 Iu Flex has been configured before this feature is activated.
License
Other Prerequisites
The CN supports dynamic capacity management and load redistribution.
Context
This feature enables load balancing and load redistribution among multiple CN nodes when Iu
Flex is deployed. The BSC6900 supports dynamic and static management of CN capacity and
status information.
Procedure
l
Configuring load balancing in static capacity mode
1.
UMTS Global Configuration Express > Core Network > UMTS CN Node;
CME batch modification center: not supported). In this step, set Capability of CN
Node to an appropriate value. The BSC6900 performs load balancing between CN
nodes based on the configured CN capacities.
Configuring load balancing in dynamic capacity mode

Issue 06 (2013-03-25)

758
RAN14.0
1.

configuration: UMTS Global Configuration Express > Operator
Configuration > RNC Operator Configuration Information; CME batch
modification center: not supported). In this step:
Set Feature Supporting Mode of CS Domain to SUPP_IUFLEX.
Set Feature Supporting Mode of PS Domain to SUPP_IUFLEX.
Set CS Information Update Switch to ON.
Set PS Information Update Switch to ON.
NOTE
Load balancing in dynamic capacity mode takes effect only when the BSC6900 is
connected to Huawei CN and the preceding switches related to Iu Flex are turned on.
Configuring load redistribution based on NullNRI

1.
Run the BSC6900 MML command MOD UCNNODE (CME single

configuration: UMTS Global Configuration Express > Core Network > UMTS
CN Node; CME batch modification center: not supported). In this step, set Status
of CN Node to OFFLOAD.
2.

modification center: not supported). In this step, set NullNRI VALUE to an
appropriate value based on the network plan.
Configuring load redistribution based on Block CN Node

1.

of CN Node to NORMAL and select the RSVDBIT1_BIT1 check box under the
parameter Reserved parameter 1.
Verifying load balancing in static capacity mode
1.
Run the BSC6900 MML command DSP UCNNODE to query the capacity ratio
of CN nodes.
2.
Check the following performance counters on the M2000 to verify that the
BSC6900 performs load balancing based on the preconfigured CN capacity:
Performance counters for CS service setup:
VS.IU.LdBalRtCS.IMSI
VS.IU.LdBalRtCS.InValidNRI
VS.IU.LdBalRtCS.IMEI
Performance counters for PS service setup:
VS.IU.Load.RoutePS.IMSI
VS.IU.Load.RoutePS.NRI
VS.IU.Load.RoutePS.IMEI
Verifying load balancing in dynamic capacity mode

1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command DSP UCNNODE to query the capacity ratio
of CN nodes.
759
RAN14.0
2.
On the BSC6900 LMT, choose Trace > UMTS Services to initiate Uu and Iu
interface message tracing.
3.
Check the traced messages. If the CN sends the BSC6900 an INFORMATION

TRANSFER INDICATION message, the dynamic CN capacity ratio is updated
and used. If the CN does not send any INFORMATION TRANSFER
INDICATION message to the BSC6900, the static CN capacity ratio is used.
4.
Check the following performance counters on the M2000 to verify that the
BSC6900 performs load balancing based on the dynamic CN capacity ratio:
Performance counters for CS service setup:
VS.IU.LdBalRtCS.IMSI
VS.IU.LdBalRtCS.InValidNRI
VS.IU.LdBalRtCS.IMEI
Performance counters for PS service setup:
VS.IU.Load.RoutePS.IMSI
VS.IU.Load.RoutePS.NRI
VS.IU.Load.RoutePS.IMEI
Verifying load redistribution based on NullNRI

1.
2.
Power off the UE. The PTMSI of the UE is assigned by SGSN1.
3.
Set SGSN1 to the OFFLOAD state and SGSN2 to the NORMAL state on the RNC.
4.
Set SGSN1 to the OFFLOAD state on SGSN1.
5.
Power on the UE and the UE makes an attach request. Check the traced Iu interface
messages. The expected result is as follows:
The BSC6900 routes the RRC_INIT_DIRECT_TRANSFER message to
SGSN1 based on NULL NRI. The attach reception message from SGSN1
contains NULL NRI and non-broadcasting location areas.
After receiving the non-broadcasting location areas, the UE sends a new routing
area update (RAU) request and contains NULL NRI in the
RRC_INIT_DIRECT_TRANSFER message. The BSC6900 routes the
RRC_INIT_DIRECT_TRANSFER message to SGSN2, of which the state
is not OFFLOAD, based on NULL NRI.
Verifying load redistribution based on Block CN Node

1.
2.
Power off the UE. The PTMSI of the UE is assigned by SGSN1.
3.
Set SGSN1 to the BLOCK state and SGSN2 to the NORMAL state on the RNC.
4.
Power on the UE and the UE makes an attach request. Check the

RRC_INIT_DIRECT_TRANSFER message traced on the Iu interface.
Expected result: The RRC_INIT_DIRECT_TRANSFER message contains
NRI of SGSN1. The BSC6900 routes the RRC_INIT_DIRECT_TRANSFER
message to SGSN2 because SGSN1 is in the BLOCK state.
Deactivating load balancing in static capacity mode
Issue 06 (2013-03-25)

760
RAN14.0
Load balancing in static capacity mode does not need to be deactivated.

Deactivating load balancing in dynamic capacity mode
1.

modification center: not supported). In this step, set CS Information Update
Switch to OFF and PS Information Update Switch to OFF.
Deactivating load redistribution based on NullNRI

1.

of CN Node to NORMAL.
Deactivating load redistribution based on Block CN Node

1.

of CN Node to NORMAL and deselect the RSVDBIT1_BIT1 check box under
the parameter Reserved parameter 1.
----End
Example
//Activating Iu Flex Load Distribution Management
//Configuring Load balancing in static capacity mode
//Configuring load balancing in dynamic capacity mode
PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=ON,
PsInfoUpdFlag=ON;
//Configuring load redistribution based on NullNRI
MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN,
CNLoadStatus=OFFLOAD, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;
CSNRILength=5, NullNRI=31;
//Configuring load redistribution based on Block CN Node
MOD UCNNODE: CnOpIndex=1, CNId=17,
CNDomainId=CS_DOMAIN,CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS,
Switch3GPP25415CR0125=OFF, RsvdPara1=RSVDBIT1_BIT1-1;
//Deactivating Iu Flex Load Distribution Management
//Deactivating load balancing in dynamic capacity mode
PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=OFF,
PsInfoUpdFlag=OFF;
//Deactivating load redistribution based on NullNRI
CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;
//Deactivating load redistribution based on Block CN Node
Issue 06 (2013-03-25)

761
RAN14.0

CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF,
RsvdPara1=RSVDBIT1_BIT1-0;
Issue 06 (2013-03-25)

762
RAN14.0
229
Configuring Transmit Diversity
Transmit Diversity. Transmit diversity enables the NodeB to provide twice the number of RF
DL channels compared with no transmit diversity.
Prerequisites
l
TX diversity requires the NodeB to provide two times RF channel resources compared
with no TX diversity mode. In TX diversity mode, the UE must support diversity
reception, STTD, TSTD, and CLD1.

License
Others
The UE must support diversity reception, STTD, TSTD, and CLD1.
Context
l
The feature supports STTD, TSTD, and CLD1 to effectively improve the reception
performance of the UE.
The transmit diversity feature improves terminal performance in special circumstances.

Especially when multipath fading is not obvious and the UE is not moving fast, capacity
and coverage can be significantly improved. The investment can be reduced while the same
QoS is guaranteed. In this way, operators can reduce the CAPEX and the OPEX.
Procedure
1.
Issue 06 (2013-03-25)

Parameters in Batches) to set the transmit diversity mode. Transmit diversity mode
consists of Space Time Transmit Diversity (STTD) mode and closed loop TX diversity
mode 1 (CP1).
763
RAN14.0
Set TX Diversity Indication to TRUE.
b.
Set STTD Support Indicator to STTD_Supported.
c.
Set CP1 Support Indicator to CP1_Supported.
d.
Set Tx Diversity Mode for User to STTD or CP1. As specified in 3GPP TS

25.211, the FDPCH can only use the STTD mode.
2.
modification center: not supported) to add a sector. In this step, set Diversity Mode
to COMMON_MODE(COMMON MODE) and configure the antenna data in line
with the hardware deployment scheme.
3.
Batches) to add a sector. In this step, set Two Tx Way to TRUE and configure the
antenna data in line with the hardware deployment scheme.
1.
a.
Run the NodeB MML command DSP LOCELL to query the status of a specified
local cell.
Expected result: The value of Cell Transmit Diversity Status is Enabled.
----End
Example
MOD UCELLSETUP: CellId=2, TxDiversityInd=TRUE, STTDSupInd=STTD_Supported,
CP1SupInd=CP1_Supported, ClosedLoopTimeAdjustMode=OFFSET1,
DpchDivModforOther=STTD, FdpchDivModforOther=STTD,
DpchDivModforMIMO=STTD, FdpchDivModforMIMO=STTD, DivModforDCHSDPA=STTD;
SRN1=60, SRN2=61, ULFREQ=9700, DLFREQ=10650, MXPWR=430, HISPM=FALSE,
RMTCM=FALSE, VAM=FALSE;
Issue 06 (2013-03-25)

764
RAN14.0
230
Configuring 4-Antenna Receive

Diversity
4-Antenna Receive Diversity.
Prerequisites
l
The RX diversity requires the Node B to provide enough RF channels and demodulation
resources that can match the number of diversity antennas.
BTS3902E can't support this feature.

License
Context
l
Compared with 2-Antenna Receive Diversity, 4-Antenna Receive Diversity provides the
NodeB with twice the number of RF UL channels. In this way, a bigger UL coverage gain
can be obtained.
4-antenna Receive Diversity improves the receiver sensitivity and the uplink coverage, so
that the CAPEX can be reduced.
Procedure
Issue 06 (2013-03-25)
1.
modification center: not supported). In this step, set Antenna Magnitude to 4. Set
Antenna Channel1 No., Antenna Channel2 No., Antenna Channel3 No., Antenna
Channel4 No., their respective cabinet numbers, and subrack numbers.
2.
Run the NodeB MML command ADD ULGROUP (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Radio Layer > UL/DL BB
Resource Group > ULGROUP; CME batch modification center: not supported). In
765
RAN14.0
this step, set Demodulation Work Mode to DEM_4_CHAN(4-Channels

Demodulation Mode) or DEM_ECON_4_CHAN(Economical 4-Channels
Demodulation Mode).
l
1.
Run the NodeB MML command LST SEC to check that the preceding parameters
are correctly configured.
----End
Example
l
NodeB V200R014
ADD SEC: STN=0, SECN=0, SECT=LOCAL_SECTOR, ANTM=4, ANT1CN=0,
ANT1SRN=4, ANT1N=N0A, ANT2CN=0, ANT2SRN=4, ANT2N=N0B, ANT3CN=0,
ANT3SRN=4, ANT3N=N1A, ANT4CN=0, ANT4SRN=4, ANT4N=N1B;
ADD ULGROUP: ULGROUPN=0, DEMMODE=DEM_4_CHAN, SNE1=0;
NodeB V100R014
ADD SEC: STN=0, SECN=0, SECT=LOCAL_SECTOR, ANTM=4, ANT1SRN=2,
ANT1N=N0A, ANT2SRN=2, ANT2N=N0B, ANT3SRN=2, ANT3N=N1A, ANT4SRN=2,
ANT4N=N1B;
Issue 06 (2013-03-25)

766
RAN14.0
231
Configuring Extended Cell Coverage

up to 200km
Extended Cell Coverage up to 200km.
Prerequisites
l
All types of baseband boards support this feature. However, only the WBBPb, WBBPd
(3900 series NodeB), EBBI, EBOI, EULP, EULPd (BTS3812E/AE), and EBBC/
EBBCd/EBBM (DBS3800) support remote cell groups.
BTS3902E can't support this feature.

License
Context
l
This feature enables the operator to use a few NodeBs to extend the cell coverage.
This feature extends the cell coverage to very remote areas with the fewest sites.
Procedure
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD UAICH (CME single configuration: UMTS
Cell Configuration Express > Channel Configuration > AICH; CME batch
modification center: not supported). In this step, set AICH Transmission Timing to
1.
2.
Run the BSC6900 MML command ADD UPRACHBASIC (CME single

PRACH Basic Information; CME batch modification center: not supported). In this
step, select available RACH sub channels in the cell from the RACH Sub Channel
No. list.
3.
Run the BSC6900 MML command MOD UCELL (CME single configuration:
UMTS Cell Configuration Express > Cell Basic Information > Cell Basic
767
RAN14.0
Information; CME batch modification center: 3.18 Modifying UMTS Cell

Parameters in Batches). In this step, set Max Transmit Power of Cell to the
maximum cell transmit power that is configured on the NodeB side.
4.
Run the NodeB MML command ADD REMOTECELLGRP (CME single

Other Information > REMOTECELLGRP; CME batch modification center: not
supported). In this step, set Remote Cell Group No and Remote Cell Group
Name.
In case of setting the remote cell to save boards, carry out Step 6. Otherwise, do not
carry out Step 6.
5.
Batches). In this step, set Remote Cell Mode to TRUE and set Index of Remote
Cell Group to the same value as that of Remote Cell Group No.
6.
Optional: Run the BSC6900 MML command MOD UPRACH (CME single
PRACH Basic Information; CME batch modification center: not supported), set sub
channel of every cell, select sub channel from RACH Sub Channel No..
NOTE
l Only 3 sub channels can be set for every cell, and no repeated sub channel exists. The 3 sub
channels need to be fixed as follows:
l sub-channel 0, sub-channel 1 and sub-channel 2
l When adding logical cell on BSC6900, the parameter Time Offset needs to be set to CHIP0,
CHIP256 or CHIP512.
1.
Run the NodeB MML command LST REMOTECELLGRP to check that the remote
cell group is configured.
2.
Run the NodeB MML command LST LOCELL to check that the local cell is set to
a remote cell and that Remote Cell Mode is set to TRUE.
----End
Example
//Configuration on the BSC6900 side
ADD UAICH: CELLID=1;
ADD UPRACHBASIC: CellId=1, PhyChId=4, PreambleSignatures=SIGNATURE0-1,
RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1, Constantvalue=-23,
PreambleRetransMax=20, PowerRampStep=2, CTFCSize=BIT2;
MOD UCELL: CellId=2, MaxTxPower=430;
ADD UPCPICH: CELLID=1, PHYCHID=2, PCPICHPOWER=330, MAXPCPICHPOWER=346,
MINPCPICHPOWER=313;
//Configuration on the NodeB side
ADD REMOTECELLGRP: REMOTECELLGRPINDEX=1, REMOTECELLGRPNAME="test";
ADD LOCELL: LOCELL=1, STN=1, SECN=1, SECT=LOCAL_SECTOR, CN1=0, SRN1=4,
SN1=0, ULFREQ=9700, DLFREQ=10600, MXPWR=430, HISPM=FALSE,
Issue 06 (2013-03-25)

768
RAN14.0
RMTCM=TRUE, RMTCGRPID=1, VAM=FALSE;

Configuration on the BSC6900 side
MOD UPRACH: CellId=1, PhyChId=0,
RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1;
LST REMOTECELLGRP: REMOTECELLGRPINDEX=1;
Issue 06 (2013-03-25)

769
RAN14.0
232 Configuring HSUPA Coverage Enhancement at UE

Power Limitation
232
Configuring HSUPA Coverage
Enhancement at UE Power Limitation
HSUPA Coverage Enhancement at UE Power Limitation.
Prerequisites
l
There is no requirement for BSC6900or NodeB.

License
Others
The UE needs to support 3GPP Release 8 or later. It also needs to support improved
EUL power control at UE power limitation.
Context
Compared with the traditional power compression technology, this feature provides an enhanced
power compression function. This feature optimizes the size of a data block and the E-DPDCH
power offset, improving the HSUPA performance at cell edge.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches) to select
770
RAN14.0

Power Limitation
PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH check box from Power

Control Switch to activate the feature.
2.
Run the BSC6900 MML command MOD UTYPRABHSUPAPC (CME single

Configuration > Typical RAB HSUPA Power Control Parameters; CME batch
modification center: not supported) to set Minimum Reduced E-DPDCH Gain
Factor.
Start Uu Interface Trace on the LMT to trace messages on the Uu interface.
View the RRC_RB_SETUP message, as shown in Figure 232-1. If the e-DPDCH-info
message contains the minReduced-E-DPDCH-GainFactor information element (IE), it
indicates that this feature takes effect, and the BSC6900 sends the UE the transmit power
of the data channel.
Figure 232-1 Viewing the minReduced-E-DPDCH-GainFactor IE
1.

Parameters in Batches) to clear
PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH check box from Power
Control Switch to deactivate the feature.
----End
Example
//Enabling the feature
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH-1;
//Setting the Minimum Reduced E-DPDCH Gain Factor parameter
MOD UTYPRABHSUPAPC:RABINDEX=0, SUBFLOWINDEX=0, TRCHTYPE=TRCH_EDCH_2MS,
UL16QAMIND=FALSE, ULL2ENHANCEIND=FALSE, EDPWRINTERPOLATIONIND=FALSE,
ULECBOOSTINGIND=FALSE, BETAEDMIN=4;
Issue 06 (2013-03-25)

771
RAN14.0

Power Limitation
//Disabling the feature

SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH-0;
Issue 06 (2013-03-25)

772
RAN14.0
233 Configuring Flexible frequency bandwidth of UMTS

carrier
233
Configuring Flexible frequency

bandwidth of UMTS carrier
Flexible frequency bandwidth of UMTS carrier.
Prerequisites
l
For 4.6M~5M(including 4.6M), all the RF module can support this feature.
For 4.0M~4.6M(excluding 4.6M), only 850M/1900M RRU3804, 850M WRFU, MRFU
V1/V2 and MRRU V1/V2, WRFUd, RRU3828, RRU3829, RRU3928, RRU3929,
MRFUd, MRFUe can support this feature.

License
Context
To help an operator adapt to insufficient frequency resources, Huawei supports flexible
frequency spacing. In network planning, to address insufficient bandwidth resources, an operator
can plan a frequency spacing that is lower than the frequency spacing in the case of 5.0 MHz
UMTS carrier bandwidth. Accordingly, the effective bandwidth of the RRU or RFU carrier is
adjusted so that the carrier works in a suitable status with suitable algorithms and parameters.
In this way, network performance on a low- spacing frequency is optimized as much as possible.
When deploying a UMTS site, one needs to adjust the minimal effective bandwidth of a UMTS
carrier based on the GSM frequency configuration. Otherwise, TRX alarms may occur or
network performance may deteriorate.
Procedure
l
1.
Issue 06 (2013-03-25)
Before configuring the effective bandwidth of the carrier, run the NodeB MML
command LST RRU (CME single configuration: NodeB Configuration Express >
773
RAN14.0
233 Configuring Flexible frequency bandwidth of UMTS

carrier
IUB_NodeB > Device Panel > RXU Topology) to check that an RRU is configured
for the cell that requires setting of carrier effective bandwidth. If an RRU is not
configured, run the NodeB MML command ADD RRU (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Device Panel > TOPO > Right
click RXU CHAIN > Add RXU Board; CME batch modification center: not
supported) to add an RRU.
2.
Run the NodeB MML command SET FREQBWH (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Device Panel > RUX Topology >
Right click RRU > RXU Board Property > Radio Frequency Unit; CME batch
modification center: not supported) to set the minimal effective bandwidth of the RRU
carrier (parameter: Frequency Min Bandwidth).
Run the NodeB MML command LST FREQBWH to query the effective bandwidth of the
RRU carrier and check the returned message.
If...
Then...
The effective bandwidth of the carrier

matches the configuration.
The configuration succeeds.
The effective bandwidth of the carrier does

not match the configuration.
The configuration fails.
Run the NodeB MML command SET FREQBWH (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > RUX Topology > Right click
RRU > RXU Board Property > Radio Frequency Unit; CME batch modification center:
not supported) to set the RRU effective bandwidth to 5000 Hz so that the standard
configuration of the system is restored.
----End
Example
SET FREQBWH: CN=0, SRN=60, SN=0, FMBWH=4200;
LST FREQBWH;
Issue 06 (2013-03-25)

774
RAN14.0
234
Configuring High Speed Access
High Speed Access.
Prerequisites
l
All boards of the 3900 series base stations support High Speed Access.
All boards of the DBS3800 support High Speed Access.
All boards, except the NBBI and NULP, of the BTS3812E and BTS3812AE support
the high speed access feature.

License
Context
The time-selective fading caused by the Doppler effect of a fast-moving UE increases the BER
and affects the signals received by the NodeB. The high speed access feature provides the
automatic frequency control (AFC) function for the uplink, reducing the Doppler effect and
offering reliable services for the UE in high-speed movement.
NOTE
l The local sectors, remote sectors and distributed sectors support the high speed access feature.
l When the HULP, HBBI, HBBU, or WBBPa is configured to support the high speed access feature, the
capability for the board to carry access channels decreases. Each board can support the access channels
of only one cell. In addition, the board in a common four-channel demodulation mode does not support
high speed access.
l When the WBBPb, WBBPd, EBBI, EBOI, EULP, EULPd, EBBC, or EBBCd is configured to support
the high speed access feature, the capability of the board does not decrease. The board supports high
speed access in any demodulation mode.
Issue 06 (2013-03-25)

775
RAN14.0
CAUTION
To enable the high speed access feature in the cells carrying services, deactivate these cells,
modify these cells, and then activate these cells. This process disrupts the ongoing services.
Procedure
l
1.
cell.
2.
Batches) to modify the attributes of the specified local cell. In this step, set, High
Speed Movement Mode to TRUE. Set Speed Rate as required.
3.
cell.
1.
information about the local cell. The query result is returned on the LMT. Check that
the values of High Speed Movement Mode and Speed Rate match the configuration.
1.
cell.
2.
Batches) to modify the attributes of the local cell. In this step, set, High Speed
Movement Mode to FALSE.
3.
cell.
----End
Example
Issue 06 (2013-03-25)

776
RAN14.0
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, HISPM=TRUE, SPR=400;

MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, HISPM=FALSE;
Issue 06 (2013-03-25)

777
RAN14.0
235 Configuring Independent Demodulation of Signals from

Multiple RRUs in One Cell
235
Configuring Independent
Demodulation of Signals from Multiple RRUs in

One Cell
Independent Demodulation of Signals from Multiple RRUs in One Cell.
Prerequisites
l
This feature supports only DBS3900 series base stations.
The WBBPb, WBBPd, or WBBPf board needs to be configured.

This feature is mutually exclusive to the following features:
WRFD-010203 Transmit Diversity
WRFD-010209 4-Way Receive Diversity
WRFD-010684 2x2 MIMO
WRFD-021308 Extended Cell Coverage up to 200km
WRFD-010701 Uplink Enhanced CELL_FACH
WRFD-010692 HSUPA FDE
WRFD-020102 Load Measurement (based on the report of actual service load)
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period
WRFD-140216 Load-based Uplink Target BLER Configuration
License
Context
l
Issue 06 (2013-03-25)
Precautions
778
RAN14.0

In multi-RRU cell scenarios, this feature reduces handovers between cells and increases
cell capacity and cell throughput.
This feature cannot be used if a base station is configured with the feature transmit
diversity, 4-Antenna Receive Diversity, or multiple-input multiple-output (MIMO).
This feature is suitable for high-speed scenarios, such as freeways, high-speed railways,
and F1 racing arenas.
l
Data Preparation
Configuring an uplink baseband resource group
Parameter Name
Parameter ID
Recommended
Parameter
Settings
Date Source
Demodulation
Work Mode
DEMMODE
Set this parameter

to
DEM_2_CHAN
(2-Channels
Demodulation
Mode). This
feature supports
only 2-channel
demodulation
mode.
Network plan
Parameter Name
Parameter ID
Recommended
Parameter
Settings
Data Source
Sector Type
SECT
Set this parameter Network plan

to
MULTIRRU_SE
CTOR
(MULTIRRU_S
ECTOR). This
parameter value is
for the exclusive
use of the cell with
this feature.
Configuring a sector
Issue 06 (2013-03-25)

779
RAN14.0

Parameter Name
Parameter ID
Recommended
Parameter
Settings
Data Source
Antenna
Magnitude
ANTM
Set this parameter

based on the site
conditions.
Network plan
l Set it to 2 in
1TX+2RX
configuration.
l Set it to 1 in the
1TX+1RX
configuration.
l Set it to 2 in the
1TX+1RX and
1TX+2RX
hybrid
configuration.
RRU Number
RRUCOUNT
Number of RRUs
used by the cell
with this feature.
Network plan
Subrack No.of
RRU1
RRU1SRN
Subrack number of Network plan

RRU 1. Other
RRUs have similar
slot numbers.
Configuring a local cell
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Recommended
Parameter
Settings
Data Source
Local Cell ID
LOCELL
None
Network plan
Sector Type
SECT
Set this parameter

to
MULTIRRU_SE
CTOR
(MULTIRRU_S
ECTOR). The
configured sector
type must be
consistent with that
of the sector
controlling the
local cell.
Network plan

780
RAN14.0
Issue 06 (2013-03-25)

Parameter Name
Parameter ID
Recommended
Parameter
Settings
Data Source
RRU Mode
RRUMODE
Set this parameter

to SYNC(SYNC)
when all RRUs of a
sector are used. Set
this parameter to
UNSYNC
(UNSYNC) when
some RRUs of a
sector are used and
set other
parameters to
specify the number
of RRUs to be used
and their slots.
Network plan
High Speed
Movement Mode
HISPM
Setting this
parameter to
TRUE(TRUE) is
recommended if
UEs move at 200
km/h or higher.
This parameter
must be set to
FALSE(FALSE)
in the case of
indoor coverage.
Network plan
Speed Rate
SPR
A high parameter
value indicates that
a high moving
speed of UEs is
supported. If the
moving speed of
UEs exceeds this
parameter value,
network access
performance will
decrease sharply.
If UEs move at
different speeds in
the coverage area,
set this parameter
to the highest
moving speed of
UEs.
Network plan

781
RAN14.0

Parameter Name
Parameter ID
Recommended
Parameter
Settings
Data Source
Local Cell Radius
RADIUS
The parameter
value cannot
exceed 30 km
when a cell is
configured with
this feature.
Network plan
Procedure
l
Scenario 1: 1TX+2RX configuration
Figure 235-1 shows the hardware configuration of this scenario. The following
procedure assumes that RRU 1 is installed at slot 60 and RRU 2 is at slot 61.
Figure 235-1 1TX+2RX configuration
Issue 06 (2013-03-25)
1.
Run the NodeB MML command ADD BRD (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Device Panel > Universal Satellite
Control Unit; CME batch modification center: not supported) to add a baseband
processing board.
2.
Resource Group > ULGROUP; CME batch modification center: not supported)
to add an uplink resource group.
3.
Run the NodeB MML command ADD DLGROUP (CME single configuration:
782
RAN14.0

Resource Group > DLGROUP; CME batch modification center: not supported)
to add a downlink resource group.
4.
an RRU chain.
5.
RXU CHAIN > Add RXU Board; CME batch modification center: not supported)
to add an RRU to the RRU chain.
6.
Run the NodeB MML command ADD SITE (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Site; CME batch
modification center: not supported) to add a site.
7.
modification center: not supported) to add a sector.
8.
Parameters in Batches) to add a local cell.
9.

modification center: not supported) to add a cell.
Scenario 2: 1TX+1RX configuration

procedure assumes that RRU 1 to RRU 3 are installed in slot 60 to 62, respectively.
Figure 235-2 1TX+1RX configuration
Issue 06 (2013-03-25)

783
RAN14.0

1.
processing board.
2.
3.
4.
an RRU chain.
5.
6.
7.
8.
9.

Scenario 3: 1TX+1RX and 1TX+2RX hybrid configuration

procedure assumes that RRU 1 to RRU 4 are installed in slot 60 to 63, respectively.
Issue 06 (2013-03-25)

784
RAN14.0

Figure 235-3 1TX+1RX and 1TX+2RX hybrid configuration
Issue 06 (2013-03-25)
1.
processing board.
2.
3.
4.
an RRU chain.
5.
6.
7.

785
RAN14.0

NOTE
If an RRU requires only one antenna, set the unused antenna to NULL for the RRU by
running the ADD SEC (CME single configuration: NodeB Configuration Express >
IUB_NodeB > Radio Layer > Sector; CME batch modification center: not supported)
command.
8.
9.

1.
Run the NodeB MML command LST SEC to query configured sectors.
Expected result: The value of Sector Type is MULTIRRU_SECTOR
(MULTIRRU_SECTOR).
2.
Run the NodeB MML command DSP LOCELL to query the local cell.
Expected result: The value of Local Cell Status is Local Cell Available.
3.
Optional: After the corresponding logical cell is activated, perform drive tests to
check for coverage holes and weak coverage areas.
Deactivate the corresponding logical cell on the RNC, and then remove the local cell and
sector on the NodeB. After this feature is deactivated, the released resources, such as the
RF components and baseband processing board, can be used for other cells.
1.
Modifying UMTS Cell Parameters in Batches) to deactivate a specified logical cell
on the RNC.
2.
Run the NodeB MML command RMV LOCELL (CME single configuration: NodeB
batch modification center: not supported) to remove a specified local cell of the
NodeB.
3.
Run the NodeB MML command RMV SEC (CME single configuration: NodeB
modification center: not supported) to remove a specified sector of the NodeB.
----End
Example
//Scenario 1: 1TX+2RX configuration
ADD BRD: SN=3, BT=WBBP, WM=FDD, HCE=FULL;
ADD DLGROUP: DLGROUPN=0, SNE1=3;
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, HCN=0, HSRN=0, HSN=3, HPN=0;
RXNUM=2, TXNUM=1;
RXNUM=2, TXNUM=1;
Issue 06 (2013-03-25)

786
RAN14.0

ADD SITE: STN=0, STNAME="Dongguan Station on Guangzhou-Shenzhen Express";

ADD SEC: STN=0, SECN=0, SECT=MULTIRRU_SECTOR, ANTM=2, RRUCOUNT=2,
RRU1SRN=60, RRU2SRN=61;
ADD LOCELL: LOCELL=102001, STN=0, SECN=0, SECT=MULTIRRU_SECTOR,
RRUMODE=SYNC, ULFREQ=10560, DLFREQ=9610, MXPWR=430, HISPM=TRUE, SPR=250;
//Scenario 2: 1TX+1RX configuration
RXNUM=2, TXNUM=1;
RXNUM=2, TXNUM=1;
RXNUM=2, TXNUM=1;
ADD SITE: STN=0, STNAME="Jinmao Building";
RRU1SRN=60, RRU2SRN=61, RRU3SRN=62;
RRUMODE=SYNC, ULFREQ=10560, DLFREQ=9610, MXPWR=430, HISPM=FALSE;
//Scenario 3: 1TX+1RX and 1TX+2RX hybrid configuration
RXNUM=2, TXNUM=1;
RXNUM=2, TXNUM=1;
RXNUM=2, TXNUM=1;
RXNUM=2, TXNUM=1;
ADD SITE: STN=0, STNAME="Zone C in Tianfu Software Park";
RRU1SRN=60, RRU1ANT2N=NULL, RRU2SRN=61, RRU2ANT2N=NULL, RRU3SRN=62,
RRU4SRN=63;
RRUMODE=SYNC, ULFREQ=10560, DLFREQ=9610, MXPWR=430, HISPM=FALSE;
Issue 06 (2013-03-25)

787
RAN14.0
236 Configuring Inter Frequency Hard Handover Based on

Coverage
236
Configuring Inter Frequency Hard

Handover Based on Coverage
Inter Frequency Hard Handover Based on Coverage.
Prerequisites
l

License
Other Prerequisites
The UE supports relevant measurements and the handover procedure.
Context
This feature introduces inter-frequency hard handover triggered by Active Set quality
measurement event 2D or by Uplink Radio Link Qos or emergency blind handover triggered by
event 1F.
Procedure
l
Issue 06 (2013-03-25)
1.

HO_INTER_FREQ_HARD_HO_SWITCH from the HandOver Switch dropdown list.
2.

configuration: UMTS Cell Configuration Express > Neighboring Cell > InterHuawei Proprietary and Confidential
788
RAN14.0

Coverage
frequency Neighboring Cell; CME batch modification center: not supported) to add
an inter-frequency neighboring cell.
3.
Run the BSC6900 MML command ADD UCELLINTERFREQHOCOV (CME

Oriented Coverage Based Inter-frequency Handover Measurement Algorithm
Parameters in Batches) (cell level) or SET UINTERFREQHOCOV (CME single
Parameter Configuration > RNC Oriented Coverage Based Inter-frequency
Handover Measurement Algorithm Parameters; CME batch modification center:
3.15 Modifying RNC Parameters in Batches) (RNC level) to configure parameters
related to coverage-based inter-frequency hard handover.
1.
Attenuate signals in the current cell that the UE accesses to trigger reporting of event
2D by the UE.
2.
Click to display Uu Interface Trace on the BSC6900 LMT.
3.
Check whether the RNC has sent the UE an RRC_MEAS_CTRL message and the
traced message contains thresholds for triggering events 2D and 2F and the reporting
mode.
4.
Check whether the RNC has sent the UE an RRC_MEAS_RPRT message and the
traced message contains an event 2D measurement report shown in Figure 236-1.
Figure 236-1 Event 2D measurement report
5.
Issue 06 (2013-03-25)
After the event 2D measurement report is reported, check whether the RNC has sent
the UE an RRC_MEAS_CTRL message and the traced message contains the
information element interFrequencyMeasurement, as shown in Figure 236-2.

789
RAN14.0

Coverage
Figure 236-2 Inter-frequency measurement control message
6.
Issue 06 (2013-03-25)
After the inter-frequency measurement control message is reported, check whether

the RNC has sent the UE an RRC_PH_CH_RECFG message, and the UE has sent
the RNC RRC_PH_CH_RECFG_CMP message, as shown in Figure 236-3 and
Figure 236-4.

790
RAN14.0

Coverage
Figure 236-3 Physical channel reconfiguration message
Figure 236-4 Physical channel reconfiguration complete message
1.

HO_INTER_FREQ_HARD_HO_SWITCH from HandOver Switch.
----End
Example
//Activating Inter Frequency Hard Handover Based on Coverage
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1
ADD UCELLINTERFREQHOCOV: CellId=1,
InterFreqReportMode=PERIODICAL_REPORTING, InterFreqMeasTime=60;
//Deactivating Inter Frequency Hard Handover Based on Coverage
Issue 06 (2013-03-25)

791
RAN14.0

DL QoS
237
Configuring Inter Frequency Hard

Handover Based on DL QoS
Inter Frequency Hard Handover Based on DL QoS.
Prerequisites
l

The feature WRFD-020302 Inter Frequency Hard Handover Based on Coverage must
be configured before this feature is activated.
License
Context
When the load of services is high in a cell and downlink QoS decreases, this feature enables the
UE to be handed over to an inter-frequency cell, guaranteeing QoS requirements.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to activate the inter-frequency hard handover.
2.

configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell; CME batch modification center: not supported) to add
an inter-frequency neighboring cell.
3.
Run the BSC6900 MML command ADD UCELLINTERFREQHOCOV (CME

792
RAN14.0

DL QoS
Oriented Coverage Based Inter-frequency Handover Measurement Algorithm

Parameters in Batches) (cell level) or SET UINTERFREQHOCOV (CME single
Parameter Configuration > RNC Oriented Coverage Based Inter-frequency
3.15 Modifying RNC Parameters in Batches) (BSC6900 level) to configure
parameters related to DL-QoS-based inter-frequency hard handover.
4.
modification center: 3.15 Modifying RNC Parameters in Batches) to activate interfrequency hard handover based on downlink QoS for BE services.
5.
modification center: 3.15 Modifying RNC Parameters in Batches) to activate interfrequency hard handover based on downlink QoS for AMR and AMR-WB services.
6.
modification center: 3.15 Modifying RNC Parameters in Batches) to activate interfrequency hard handover based on downlink QoS for VP services.
1.
Log in to the BSC6900 LMT and start Uu Interface Trace.
2.
Ensure that the RNC sends to the NodeB an NBAP_DEDI_MEAS_INIT_REQ

message, which carries the event E parameter, as shown in Figure 237-1.
Figure 237-1 NBAP_DEDI_MEAS_INIT_REQ message
Issue 06 (2013-03-25)

793
RAN14.0

DL QoS
3.
Ensure that the NodeB reports to the RNC an NBAP_DEDI_MEAS_RPRT message,

which carries the event E parameter.
4.
Ensure that the RNC sends to the UE an RRC_MEAS_CTRL message and starts
inter-frequency measurement of the event or period type. Then, check that the
corresponding traced message indicates that the RNC has sent the inter-frequency
measurement control message to the UE.
1.
modification center: 3.15 Modifying RNC Parameters in Batches) to deactivate
inter-frequency hard handover based on downlink QoS for BE services.
2.
inter-frequency hard handover based on downlink QoS for AMR and AMR-WB
services.
3.
inter-frequency hard handover based on downlink QoS for VP services.
----End
Example
//Activating Inter Frequency Hard Handover Based on DL QoS
ADD UCELLQOSHO: CellId=111, DlRscpQosHyst=5, DLQosMcTimerLen=20,
ULQosMcTimerLen=20;
SET UQOSACT: BEQosPerform=YES, BeDlAct1=InterFreqHO;
SET UQOSACT: AMRQosPerform=YES, DlQosAmrInterFreqHoSwitch=YES,
DlQosWAmrInterFreqHoSwitch=YES;
SET UQOSACT: VPQosPerform=YES, DlQosVpInterFreqHoSwitch=YES;
//Deactivating Inter Frequency Hard Handover Based on DL QoS
RMV UCELLQOSHO: CellId=111;
SET UQOSACT: BEQosPerform=NO; or SET UQOSACT: BEQosPerform=YES,
BeDlAct1=None, BeDlAct2=None, BeDlAct3=None;
SET UQOSACT: AMRQosPerform=NO; or SET UQOSACT: AMRQosPerform=YES,
DlQosAmrInterFreqHoSwitch=NO, DlQosWAmrInterFreqHoSwitch=NO;
SET UQOSACT: VPQosPerform=NO; or SET UQOSACT: VPQosPerform=YES,
DlQosVpInterFreqHoSwitch=NO;
Issue 06 (2013-03-25)

794
RAN14.0
238
Configuring SRNS Relocation (UE

Not Involved)
WRFD-02060501 SRNS Relocation (UE Not Involved). (This feature cannot be configured
using the CME. )
Prerequisites
l

The feature WRFD-020605 SRNS Relocation Introduction Package has been
License
The CN supports this feature.
Both the SRNC and the DRNC support this feature.
Context
This feature supports the SRNS relocation procedure based on the standard Iu interface defined
by 3GPP specifications. The static SRNS relocation procedure does not involve the UE and radio
connections are not affected during the relocation. Therefore, static SRNS relocation is an
optimal relocation mode.
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command ADD DEVIP to add a device IP address to an
interface board.
2.
Run the BSC6900 MML command ADD IPOAPVC to add an Internet Protocol over
ATM (IPoA) permanent virtual circuit (PVC). In this step:
795
RAN14.0
Set IP address to the device IP address of the interface board.

Set Peer IP address to the IP address of the serving GPRS support node (SGSN).
The VPI and VCI must be the same as those configured on the SGSN side. You
can run the command LST IPOA on the SGSN maintenance terminal to query the
settings of the VPI and VCI on the SGSN side.
3.
Run the BSC6900 MML command ADD IPRT to add a route from the BSC6900 to
the DRNC. In this step:
Set Subrack No. and Slot No. respectively to the subrack number and slot number
of the Iu-PS interface board carrying the IP path.
Set Destination IP Address to the IP address of the DRNC on the Iu interface.
Set Forward route address to the IP address of the SGSN gateway.
4.
Run the BSC6900 MML command ADD IPPATH to add an IP path for static SRNS
relocation. In this step:
Set Adjacent Node ID to the adjacent node ID of the SGSN.
Set Interface Type to IUR(Iur Interface).
Set Local IP address to the IP address of the SRNC on the Iu interface.
Set Peer IP address to the Iu IP address of the DRNC on the Iu interface.
5.
Run the BSC6900 MML command ADD UEXT3GCELL to add a cell to the
neighboring RNC.
6.
Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell.
7.

select the HO_INTRA_FREQ_SOFT_HO_SWITCH check box under the
parameter HandOver Switch and select the
SRNSR_DSCR_PROPG_DELAY_SWITCH check box under the parameter
SRNSR Algorithm Switch.
NOTE
SRNS relocation can be triggered by Iur transmission resource optimization, location

separation, delay optimization, and separation time.
The preceding procedure takes delay optimization as an example to describe the data
configuration.
8.
Run the BSC6900 MML command SET USRNSR. In this step, select the All
service check box under the parameter SRNS Relocation-Allowed Traffic Type.
9.
Run the BSC6900 MML command MOD UNRNC. In this step, set SHO cross IUR
trigger to an appropriate value based on the network plan, and set Handover Type
for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC.
1.
Issue 06 (2013-03-25)
The following procedure takes SRNS relocation from SRNC (RNC1) to DRNC
(RNC2) as an example. Initiate interface message tracing on both RNC1 LMT and
RNC2 LMT. Configure Iu interface message tracing, as shown in Figure 238-1.
Configure Iur interface message tracing, as shown in Figure 238-2.

796
RAN14.0
Figure 238-2 Iur Interface Trace dialog box
Call drops do not occur during SRNS relocation if all the following messages are
traced:
On the Iu interface of RNC1:
RNC1->CN RANAP_RELOCATION_REQUIRED
CN->RNC1 RANAP_RELOCATION_COMMAND
RNC2->CN RANAP_RELOCATION_REQ
CN->RNC2 RANAP_RELOCATION_REQ_ACK
RNC2->CN RANAP_RELOCATION_DETECT
RNC2->CN RANAP_RELOCATION_COMPLETE
On the Iur interface between RNC1 and RNC2:
RNC1->RNC2: RNSAP_RELOCATION_COMMIT
Issue 06 (2013-03-25)

797
RAN14.0

CN->RNC1 RANAP_IU_RELEASE_COMMAND
RNC1->CN RANAP_IU_RELEASE_COMPLETE
l
1.

deselect the HO_INTRA_FREQ_SOFT_HO_SWITCH check box under the
parameter HandOver Switch and deselect the
SRNSR_DSCR_PROPG_DELAY_SWITCH check box under the parameter
SRNSR Algorithm Switch.
----End
Example
//Activating SRNS Relocation (UE Not Involved)
//Adding a device IP address to an interface board
ADD DEVIP:IPADDR="172.12.10.181", SRN=0, SN=24, MASK="255.255.255.0",
DEVTYPE=IPOA_CLIENT_IP, MTU=1696;
//Adding an Internet Protocol over ATM (IPoA) permanent virtual circuit
(PVC)
ADD IPOAPVC:IPADDR="172.12.10.181", PEERIPADDR="172.12.10.254",
CARRYT=NCOPT, CARRYNCOPTN=0, CARRYVPI=182, CARRYVCI=50, TXTRFX=105,
RXTRFX=105, PEERT=IUPS;
//Adding an IP route from the BSC6900 to the DRNC
ADD IPRT:SRN=0, SN=24, DSTIP="172.12.10.226", DSTMASK="255.255.255.255",
NEXTHOP="172.12.10.254", REMARK="Reloc route-RNC226", PRIORITY=HIGH;
//Adding an IP path for static SRNS relocation
ADD IPPATH:ANI=1, PATHID=3, IPADDR="172.12.10.181",
PEERIPADDR="172.12.10.226", VLANFLAG=DISABLE, PATHT=EF,
PEERMASK="255.255.255.255", TXBW=100000, RXBW=100000, PATHCHK=DISABLED,
ITFT=IUPS, TRMLOADTHINDEX=2;
//Adding a cell to the neighboring RNC
TxDiversityInd=FALSE, LAC=1, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE,
QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED,
CellCapContainerFdd=DELAY_ACTIVATION_SUPPORT-0,
OverLayMobilityFlag=FORBIDDEN, EFachSupInd=FALSE;
//Adding an intra-frequency neighboring cell
//Setting the BSC6900-level algorithm switch
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1,
SrnsrSwitch=SRNSR_DSCR_PROPG_DELAY_SWITCH-1;
//Setting the type of service that allows SRNS relocation
SET USRNSR: SrnsRabCnDomainType=ALL;
//Setting the type of service that allows cross-Iur handovers
Issue 06 (2013-03-25)

798
RAN14.0
PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
//Deactivating SRNS Relocation (UE Not Involved)
//Setting the BSC6900-level algorithm switch
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0,
SrnsrSwitch=SRNSR_DSCR_PROPG_DELAY_SWITCH-0;
Issue 06 (2013-03-25)

799
RAN14.0
239
Configuring SRNS Relocation with

Hard Handover
WRFD-02060502 SRNS Relocation with Hard Handover.
Prerequisites
l

License
Other Prerequisites
The SRNC and the DRNC must support this feature simultaneously.
The CN must support this feature simultaneously.
Context
When the Iur interface is unavailable, this feature enables the UE to move between RNCs.
This feature is enabled when the Iur interface does not exist, or the resources for the connection
setup on the Iur interface are insufficient.
Procedure
l
Issue 06 (2013-03-25)
1.

2.
UE1 and UE2 are in idle mode and camp on Cell 111.
800
RAN14.0
3.

Parameters in Batches) to select HO_INTRA_FREQ_HARD_HO_SWITCH and
HO_INTER_FREQ_HARD_HO_SWITCH from the HandOver switch list.
4.
modification center: not supported) to set HHO cross IUR trigger to ON and
Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC.
1.
Initiate standard interface tracing on the BSC6900 LMT to perform the verifying
procedure. No call drops occur during the transition.
You can view the transition procedure on the Iu interface tracing pane of RNC1, as
Take RNC1 as the SRNC, and RNC2 as the DRNC for example. When the Iur interface
between RNC1 and RNC2 is unavailable, this feature enables the UE to move between
RNCs.
Issue 06 (2013-03-25)

801
RAN14.0
Figure 239-1 SRNS Relocation with Hard Handover
----End
Example
//Activating SRNS Relocation with Hard Handover
//Add an intra-frequency neighboring cell
Issue 06 (2013-03-25)

802
RAN14.0
ADD UINTERFREQNCELL: RncId=1, CellId=111, NCellRncId=2, NCellId=312,

SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHOFlag=FALSE,
NPrioFlag=FALSE;
//Select HO_INTER_FREQ_HARD_HO_SWITCH and HO_INTRA_FREQ_HARD_HO_SWITCH
from the HandOver switch list
HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1&HO_INTRA_FREQ_HARD_HO_SWITCH-1;
//Turn on HHO cross IUR trigger, and set Handover Type for PS BE Traffic
to CORRM_SRNSR_PSBE_RELOC
MOD UNRNC: NRncId=2, HHOTRIG=ON, PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
Issue 06 (2013-03-25)

803
RAN14.0
240
Configuring SRNS Relocation with

Cell/URA Update
WRFD-02060503 SRNS Relocation with Cell/URA Update.
Prerequisites
l

feature depends on the feature WRFD-020605 SRNS Relocation Introduction Package.
License
Other Prerequisites
The CN and the DRNC must support this feature simultaneously.
Context
If the Iur interface supports the Iur-CCH, inter-RNC cell/URA update normally does not trigger
the relocation. Instead, the relocation is triggered through the static relocation procedure. SNSR
relocation triggered by cell/URA update is performed when the following conditions are met:
l
The cell update is complete.
The source cell and target cell belong to different RNCs.
Between the RNCs exist the Iur interface. The interface does not support the CCH, or the
Iur-CCH is not available.
The SNSR relocation can be triggered by cell reselection of UEs in the CELL_FACH,
CELL_PCH, or URA_PCH state. The relocation is started after the Cell Update or URA Update
message from the UE is forwarded from the target RNC to the source RNC over the Iur interface.
Issue 06 (2013-03-25)

804
RAN14.0
Procedure
l
1.

Parameters in Batches) to set the following switches in the Dynamic resource
allocation switch parameter:
Set DRA_DCCC_SWITCH to 1.
Set DRA_PS_BE_STATE_TRANS_SWITCH to 1.
Set DRA_PS_NON_BE_STATE_TRANS_SWITCH to 1.
2.

modification center: 3.15 Modifying RNC Parameters in Batches) to set BE DCH
to FACH Transition Timer to 10.
3.
modification center: not supported) to set IUR CCH support flag to NO and
Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC.
1.
The Iur interface between RNC1 and RNC2 is working properly. On the HLR, set the
UE to support background services.
2.
UE1 and UE2 are in idle mode and camp on Cell 111.
3.
Trigger state transition so that the UE transits to the CELL_FACH, CELL_PCH, or

URA_PCH state.
4.
Initiate standard interface tracing on the RNC LMT to perform the verifying procedure
as follows:
If the following messages are displayed, you can infer that no call drops occur during
the transition.
On the Iu interface tracing pane of RNC1
RNC1->CN RANAP_RELOCATION_REQUIRED
CN->RNC1 RANAP_RELOCATION_COMMAND
On the Iu interface tracing pane of RNC2
RNC2->CN RANAP_RELOCATION_REQ
CN->RNC2 RANAP_RELOCATION_REQ_ACK
RNC2->CN RANAP_RELOCATION_COMPLETE
RNC2->CN RANAP_RELOCATION_DETECT
On the Uu interface tracing pane of RNC2
UE->RNC2 URA_UPDATE/URA_UPDATE
RNC2->UE URA_UPDATE_CONFIRM/CELL_UPDATE_CONFIRM
On the Iur interface tracing pane between RNC1 and RNC2
RNC2->RNC1 UL_SIGNAL_TRANSF_IND
Issue 06 (2013-03-25)

805
RAN14.0
RNC1->RNC2: RNSAP_RELOCATION_COMMIT
l
----End
Example
//Activating SRNS Relocation with Cell/URA Update.
DraSwitch=DRA_DCCC_SWITCH-1&DRA_PS_BE_STATE_TRANS_SWITCH-1&DRA_PS_NON_BE_
STATE_TRANS_SWITCH-1;
MOD UNRNC: NRncId=2, SuppIurCch=NO, PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
Issue 06 (2013-03-25)

806
RAN14.0
241
Configuring Multiple RAB Package

(PS RAB 2)
Multiple RAB Package (PS RAB 2).
Prerequisites
l

License
Other Prerequisites
The CN node and UE must have the corresponding multi-RAB support capability.
Context
With the Multiple RAB feature, operators have relatively diversified choices of service solutions.
If the Multiple RAB feature is enabled, a large quantity of services can be provided for the upper
layers. Huawei products support the following solutions with more than one PS RAB:
l
Combination of two PS services
Combination of one CS service and two PS services
Combination of three PS services
Combination of one CS service and three PS services
Combination of four PS services
Procedure
1.
Issue 06 (2013-03-25)

807
RAN14.0

Parameters in Batches) to select the CFG_MULTI_RAB_SWITCH check box
under the Channel configuration strategy switch parameter.
l
1.
Details see the verification procedure of following features: 242 Configuring

Combination of Two PS Services, 243 Configuring Combination of One CS
Service and Two PS Services, 244 Configuring Combination of Three PS
Services, 245 Configuring Combination of One CS Service and Three PS
Services and 246 Configuring Combination of Four PS Services.
1.

Parameters in Batches) to clear the CFG_MULTI_RAB_SWITCH check box
----End
Example
//Activating Multiple RAB Package (PS RAB 2).
SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1;
//Deactivating Multiple RAB Package (PS RAB 2).
Issue 06 (2013-03-25)

808
RAN14.0
242
Configuring Combination of Two PS

Services
WRFD-01061501 Combination of Two PS Services.
Prerequisites
l

feature depends on the feature WRFD-010615 Multiple RAB Package (PS RAB 2).
License
Other Prerequisites
The UE supports the combination of two PS services.
Context
Procedure
l
1.
l
Issue 06 (2013-03-25)

809
RAN14.0
1.
Connect the UE to the portable computer so as to use the UE as a modem.
2.
Visit the Internet on the UE. Verify that web pages are displayed normally.
3.
On the portable computer, connect to an FTP server and download data. Verify that
the data is downloaded normally.
1.

----End
Example
//Activating Combination of Two PS Services.
//Deactivating Combination of Two PS Services.
Issue 06 (2013-03-25)

810
RAN14.0
243 Configuring Combination of One CS Service and Two

PS Services
243
Configuring Combination of One CS

Service and Two PS Services
WRFD-01061502 Combination of One CS Service and Two PS Services.
Prerequisites
l

License
Other Prerequisites
The UE supports the combination of One CS Service and Two PS Services.
Context
Procedure
l
1.
l
Issue 06 (2013-03-25)

811
RAN14.0
243 Configuring Combination of One CS Service and Two

PS Services
1.
Have two UEs ready: UE 1 and UE 2.
2.
Connect UE 1 to the portable computer so as to use the UE 1 as a modem.
3.
Visit the Internet on UE 1. Verify that web pages are displayed normally (a PS
Service).
4.
the data is downloaded normally (a PS Service).
5.
Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable (a
CS Service).
1.

----End
Example
//Activating Combination of One CS Service and Two PS Services.
//Deactivating Combination of One CS Service and Two PS Services.
Issue 06 (2013-03-25)

812
RAN14.0
244
Configuring Combination of Three

PS Services
WRFD-01061503 Combination of Three PS Services.
Prerequisites
l

License
Other Prerequisites
The UE supports the Combination of Three PS Services.
Context
Procedure
l
1.
l
Issue 06 (2013-03-25)

813
RAN14.0
1.
Connect UE to the portable computer so as to use the UE as a modem.
2.
Visit the Internet on UE. Verify that web pages are displayed normally.
3.
Visit the Multimedia service on the UE. Verify that this service is played normally.
4.
1.

----End
Example
//Activating Combination of Three PS Services.
//Deactivating Combination of Three PS Services.
Issue 06 (2013-03-25)

814
RAN14.0
245 Configuring Combination of One CS Service and Three

PS Services
245
Configuring Combination of One CS

Service and Three PS Services
WRFD-01061504 Combination of One CS Service and Three PS Services.
Prerequisites
l

License
Other Prerequisites
The UE supports the combination of one CS service and three PS services.
The CN node and UE have the corresponding multi-RAB support capability.
Context
Procedure
l
1.
l
Issue 06 (2013-03-25)

815
RAN14.0
245 Configuring Combination of One CS Service and Three

PS Services
1.
Have two UEs ready: UE 1 and UE 2.
2.
Connect UE 1 to the portable computer so as to use the UE 1 as a modem.
3.
Visit the Internet on UE 1. Verify that web pages are displayed normally (a PS
Service).
4.
Visit the Multimedia service on the UE 1. Verify that this service is played normally
(a PS Service).
5.
the data is downloaded normally (a PS Service).
6.
Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable (a
CS Service).
1.

----End
Example
//Activating Combination of One CS Service and Three PS Services.
//Deactivating Combination of One CS Service and Three PS Services.
Issue 06 (2013-03-25)

816
RAN14.0
246
Configuring Combination of Four PS

Services
WRFD-01061505 Combination of Four PS Services.
Prerequisites
l

feature depends on the feature WRFD-010615 Multiple RAB Package.
License
Other Prerequisites
The UE supports the combination of Four PS Services.
The CN node and UE have the corresponding multi-RAB support capability.
Context
RAN11.0 supports up to four PS RABs per user. A typical application of Multi-RAB is VoIP
plus BE service where VoIP may need up to three RABs to transmit SIP signaling, Real-Time
Transport Protocol (RTP) (voice), and Real-Time Control Protocol (RTCP) (media monitoring)
respectively, as shown in Figure 246-1.
Figure 246-1 VoIP service
Issue 06 (2013-03-25)

817
RAN14.0
RAN11.0 supports four PS RABs per user, and the service combination VoIP + BE is supported.
Other service combination like 4PS BE is also supported.
Procedure
l
1.

2.

modification center: 3.15 Modifying RNC Parameters in Batches) command to set
the VOIP channel type parameter to DCH(UL_DCH,DL_DCH).
NOTE
The BSC6900 defines the default value of the VOIP channel type parameter. Retain the default value
in normal situations.
1.
Initiate Iu interface tracing on the BSC6900 LMT.
2.
Connect the UE to the portable computer so as to use the UE as a modem.
3.
Establish a VoIP service on the UE. View the

"RANAP_RAB_ASSIGNMENT_REQ" message traced on the Iu interface. If you
find that the CN assigns three RABs at the same time, you can infer that the VoIP
service is established successfully. (If RTCP is assigned, SIP signaling and RTP must
be assigned at the same time.)
4.
1.

----End
Example
//Activating Combination of Four PS Services
SET UFRCCHLTYPEPARA: VoipChlType=DCH;
//Deactivating Combination of Four PS Services
Issue 06 (2013-03-25)

818
RAN14.0
247
Configuring Inter Frequency Load

Balance
Inter Frequency Load Balance.
Prerequisites
l

The two optional features WRFD-010610 HSDPA Introduction Package and
WRFD-010612 HSUPA Introduction Package have been configured before this feature
is activated.
License
Context
This feature enables some UEs in a cell to be handed over to the inter-frequency same-coverage
cells if the cell is in the basic congestion state. The purpose is to reduce the load of this cell.
l
Precautions
None
Issue 06 (2013-03-25)
Data Preparation
Parameter Name
Parameter ID
Setting
Description
Source
Switch for Cell

Load Control
NBMLdcAlgoSwit
ch
The UL_UU_LDR,
DL_UU_LDR and
CELL_CODE_L
DR should be
selected.
Network Plan

819
RAN14.0
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
load control
algorithm switch
LdcSwitch
The
NODEB_CREDI
T_LDR_SWITCH
and
LCG_CREDIT_L
DR_SWITCH
should be selected.
Network Plan
NodeB LDC
algorithm switch
NodeBLdcAlgoSwitch
The
HO_ALGO_LDR
_ALLOW_SHO_
SWITCH and
HO_INTER_FRE
Q_HARD_HO_S
WITCH should be
selected.
Network Plan
DrdOrLdrFlag
DrdOrLdrFlag
Set this parameter

to TRUE
Network Plan
InterFreq Load
Handover Method
Selection
InterFreqLDHOMe
thodSelection
In the case of
measurementbased interfrequency load
handovers, set this
parameter to
MEASUREHO or
use the
recommended
value.
Network Plan
Code congestion
select inter-freq
indication
CodeCongSelInterFreqHoInd
Set this parameter

to TRUE
Network Plan
LDR period timer

length
LdrPeriodTimerLen
Use the
recommended
value.
Network Plan
DL LDR second
action
DlLdrSecondAction
Use the
recommended
value for a cell.
Network Plan
UL LDR first action
UlLdrFirstAction
Use the
recommended
value for a cell.
Network Plan
UL LDR first action
UlLdrFirstAction
Set this parameter

to
InterFreqLDHO
for a NodeB.
Network Plan

820
RAN14.0
Procedure
l
1.
Enable load reshuffling (LDR) algorithms.

Enabling uplink load reshuffling on the Uu interface
a.
Run the Run the BSC6900 MML command ADD UCELLALGOSWITCH

Parameters > Cell Algorithm Switches; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches). In this step, select the
UL_UU_LDR(Uplink UU LDR Algorithm) check box under the parameter
Switch for Cell Load Control.
Enabling downlink load reshuffling on the Uu interface

a.

DL_UU_LDR(Downlink UU LDR Algorithm) check box under the parameter
Enabling load reshuffling based on cell code resources

a.

CELL_CODE_LDR(Code LDR Algorithm) check box under the parameter
Enabling NodeB-level or cell group-level load reshuffling based on credit resources
2.
Issue 06 (2013-03-25)
a.
Run the Run the BSC6900 MML command SET ULDCALGOPARA (CME
single configuration: UMTS Radio Global Configuration Express > Load
Control Parameter Configuration > RNC Configuration of Load Control;
Batches). In this step, select the NodeB-level
NODEB_CREDIT_LDR_SWITCH(NodeB Credit LDR Switch) or cell
group-level LCG_CREDIT_LDR_SWITCH(Local Cell Group Credit LDR
Switch) check box under the parameter load control algorithm switch.
b.
Run the Run the BSC6900 MML command ADD UNODEBALGOPARA

NodeB Basic Information > NodeB Algorithm Parameters; CME batch
modification center: 3.16 Modifying Logical NodeB Parameters in Batches).
In this step, select the NodeB-level NODEB_CREDIT_LDR(NodeB Credit
LDR Algorithm) or cell group-level LCG_CREDIT_LDR(LCG Credit LDR
Algorithm) check box under the parameter NodeB LDC algorithm switch.
Run the Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME
Parameters in Batches) to enable inter-frequency handover. In this command, select
the HO_ALGO_LDR_ALLOW_SHO_SWITCH and
HO_INTER_FREQ_HARD_HO_SWITCH check boxes under the parameter
HandOver Switch.
821
RAN14.0
3.
Run the Run the BSC6900 MML command ADD UINTERFREQNCELL (CME
single configuration: UMTS Cell Configuration Express > Neighboring Cell >
Inter-frequency Neighboring Cell; CME batch modification center: not supported)
to add an inter-frequency neighboring cell supporting blind handover, or to add an
inter-frequency neighboring cell supporting measurement by setting the parameter
DrdOrLdrFlag to an appropriate value.
4.
Run the Run the BSC6900 MML command ADD

UCELLINTERFREQHONCOV (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented None-Coverage Based
Inter-frequency Handover Measurement Algorithm Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) (cell level)
or SET UINTERFREQHONCOV (CME single configuration: UMTS Radio
Global Configuration Express > HandOver Parameter Configuration > RNC
Oriented None-Coverage Based Inter-frequency Handover Measurement
Parameters in Batches) (RNC level) to set parameters related to load-based interRAT hard handovers to appropriate values based on the network plan.
5.
For a load-based inter-frequency handover that is based on measurement, run the Run
the BSC6900 MML command MOD UCELLLDR (CME single configuration:
Parameters in Batches). In this step, set InterFreq Load Handover Method
Selection to MEASUREHO(MEASUREHO).
6.
Set LDR-related thresholds based on the network plan.

For uplink and downlink load reshuffling on the Uu interface, run the Run the
BSC6900 MML command MOD UCELLLDM (CME single configuration:
Cell Parameters in Batches). In this step, set the following LDR-related
thresholds: UL LDR trigger threshold, UL LDR release threshold, DL LDR
trigger threshold, DL LDR release threshold, and DlLdTrnsHysTime.
For uplink and downlink load reshuffling on the Uu interface and load reshuffling
based on cell code resources, run the Run the BSC6900 MML command MOD
UCELLLDR (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell LDR Algorithm Parameters; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set the
following LDR-related threshold: Cell LDR SF reserved threshold.
For NodeB-level or cell group-level load reshuffling based on credit resources, run
the Run the BSC6900 MML command MOD UNODEBLDR (CME single
center: 3.16 Modifying Logical NodeB Parameters in Batches). In this step, set
the following LDR-related threshold: UL LDR Credit SF reserved threshold.
Issue 06 (2013-03-25)
7.
For load reshuffling based on cell code resources, run the Run the BSC6900 MML
command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters;
Batches) to allow inter-frequency handovers in cases of code resource congestion. In
this step, set Code congestion select inter-freq indication to TRUE(TRUE).
8.
Run the Run the BSC6900 MML command SET ULDCPERIOD (CME single
configuration: UMTS Radio Global Configuration Express > Load Control
822
RAN14.0
Parameter Configuration > RNC Oriented LDC Algorithm Cycle Length; CME
step, set the LDR period LDR period timer length to an appropriate value.
9.
For uplink and downlink load reshuffling on the Uu interface and load reshuffling
based on cell code resources, run the Run the BSC6900 MML command MOD
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set the DL
LDR second action and DL LDR first action and set other parameters related to the
LDR action based on the network plan.
10. For NodeB-level or cell group-level load reshuffling based on credit resources, run
the Run the BSC6900 MML command MOD UNODEBLDR (CME single
center: 3.16 Modifying Logical NodeB Parameters in Batches). In this step, select
the InterFreqLDHO(inter-freq load handover) check box under the parameter UL
LDR first action and set other parameters related to the LDR action based on the
network plan.
l
1.
Run the following BSC6900 to check whether this feature has been activated.
LST UCELLALGOSWITCH
LST UCELLLDR
LST UCELLLDM
LST ULDCPERIOD
LST UCORRMALGOSWITCH
LST UINTERFREQNCELL
LST UCELLINTERFREQHONCOV (cell level)
LST UINTERFREQHONCOV (RNC level)
LST ULDCALGOPARA
LST UNODEBALGOPARA
LST UNODEBLDR
2.
Check the value of the counter VS.LCC.LDR.InterFreq (Number of UEs Performing

Inter-Frequency Load Handovers in Basic Congestion for Cell). If the values is not 0,
1.
Disabling load reshuffling algorithms

Disabling uplink LDR on the Uu interface
a.
Run the Run the BSC6900 MML command MOD UCELLALGOSWITCH

Modifying UMTS Cell Parameters in Batches). In this step, clear the
UL_UU_LDR(Uplink UU LDR Algorithm) check box under the parameter
Disabling downlink LDR on the Uu interface

a.
Issue 06 (2013-03-25)

823
RAN14.0
DL_UU_LDR(Downlink UU LDR Algorithm) check box under the parameter
Disabling load reshuffling based on cell code resources
a.

CELL_CODE_LDR(Code LDR Algorithm) check box under the parameter
Disabling NodeB-level or cell-level load reshuffling based on credit resources

a.
Run the Run the BSC6900 MML command SET ULDCALGOPARA (CME
single configuration: UMTS Radio Global Configuration Express > Load
Control Parameter Configuration > RNC Configuration of Load Control;
Batches). In this step, clear the NodeB-level
NODEB_CREDIT_LDR_SWITCH(NodeB Credit LDR Switch) or cell
group-level LCG_CREDIT_LDR_SWITCH(Local Cell Group Credit LDR
Switch) check box under the parameter load control algorithm switch.
b.
Run the Run the BSC6900 MML command MOD UNODEBALGOPARA

NodeB Basic Information > NodeB Algorithm Parameters; CME batch
modification center: 3.16 Modifying Logical NodeB Parameters in Batches).
In this step, clear the NodeB-level NODEB_CREDIT_LDR(NodeB Credit
LDR Algorithm) or cell group-level LCG_CREDIT_LDR(LCG Credit LDR
Algorithm) check box under the parameter NodeB LDC algorithm switch.
2.
Run the Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME
Parameters in Batches) to disable inter-frequency handover. In this command, clear
the HO_ALGO_LDR_ALLOW_SHO_SWITCH and
HO_INTER_FREQ_HARD_HO_SWITCH check boxes under the parameter
HandOver Switch.
3.
Run the Run the BSC6900 MML command MOD UCELLLDR (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell LDR
Cell Parameters in Batches) to prohibit inter-frequency handovers in cases of code
resource congestion. In this step, set Code congestion select inter-freq indication to
FALSE(FALSE).
4.
Restore the parameter settings modified in the activation procedure.
----End
Example
//Activating Inter Frequency Load Balance
Issue 06 (2013-03-25)

824
RAN14.0
HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-1&HO_INTER_FREQ_HARD_HO_SWITCH-1;
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE,
NPrioFlag=FALSE, DrdOrLdrFlag=TRUE, InterNCellQualReqFlag=FALSE;
ADD UCELLINTERFREQHONCOV: CellId=111, InterFreqFilterCoef=D3,
Hystfor2C=6, TrigTime2C=D640, InterFreqCovHOThdEcN0=-16,
InterFreqMeasTime=60, PeriodFor2C=4, AmntOfRpt2C=5;
MOD UCELLLDR: CellId=111, InterFreqLDHOMethodSelection=MEASUREHO;
MOD UCELLLDM: CellId=111, UlLdrTrigThd=55, UlLdrRelThd=45,
DlLdrTrigThd=70, DlLdrRelThd=60, DlLdTrnsHysTime=1000;
MOD UCELLLDR: CellId=111, CellLdrSfResThd=SF8;
MOD UCELLLDR: CellId=111, CodeCongSelInterFreqHoInd=TRUE;
SET ULDCPERIOD: LdrPeriodTimerLen=10;
MOD UCELLLDR: CellId=111, DlLdrFirstAction=InterFreqLDHO,
DlInterFreqHoCellLoadSpaceThd=20, DlInterFreqHoBWThd=200000;
SET ULDCALGOPARA:
LdcSwitch=NODEB_CREDIT_LDR_SWITCH-1&LCG_CREDIT_LDR_SWITCH-1;
ADD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=10,
NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
MOD UNODEBLDR: IDTYPE=BYID, NodeBId=10, UlLdrFirstAction=InterFreqLDHO,
UlLdrCreditSfResThd=SF8, UlInterFreqHoCeLDRSpaceThd=SF8;
//Deactivating Inter Frequency Load Balance
HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-0&HO_INTER_FREQ_HARD_HO_SWITCH-0;
MOD UCELLLDR: CellId=111, CodeCongSelInterFreqHoInd= FALSE;
SET ULDCALGOPARA:
LdcSwitch=NODEB_CREDIT_LDR_SWITCH-0&LCG_CREDIT_LDR_SWITCH-0;
MOD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=11,
NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR_SWITCH-0;
MOD UNODEBLDR: IDTYPE=BYID, NodeBId=10, UlLdrFirstAction=NoAct;
Issue 06 (2013-03-25)

825
RAN14.0
248
Configuring Domain Specific Access

Control (DSAC)
Domain Specific Access Control (DSAC).
Prerequisites
l

License
Others
Only the UEs of R6 (or later) can support this function.
DSAC is a feature specified in 3GPP Release 6, and therefore only the UEs of Release
6 or later support this feature.
Context
DSAC specifies the UE access restriction based on the domain type (CS, PS, or CS+PS). The
feature can be triggered either manually or automatically.
Procedure
l
1.
Issue 06 (2013-03-25)
To activate manual DSAC, run the BSC6900 MML command ADD

UCELLDSACMANUALPARA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > The Parameters of The Manually
Triggered DSAC Algorithm in the Cell; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches).
826
RAN14.0
To restrict the UE access to the CS domain, set Restriction for CS to TRUE; to

restrict the UE access to the PS domain, set Restriction for PS to TRUE.
To set a fixed access restriction, set Restriction Type to RestrictionFixed and
select the access classes (ACs) to be restricted from the drop-down list of AC
Restriction Indicator. To set a flexible access restriction, set Restriction Type
to RestrictionFlexible, and set Number of restrained AC every time, Range of
restrained AC, and Interval of DSAC Restriction to appropriate values.
2.
To activate automatic DSAC, run the BSC6900 MML command SET

UDSACAUTOALGO (CME single configuration: UMTS Radio Global
Configuration Express > Access Restriction Algorithm Parameters
Configuration > The Parameters of the Automatically Triggered DSAC
Algorithm; CME batch modification center: 3.15 Modifying RNC Parameters in
Batches). In this step, set Switch for auto DSAC to ON.
To restrict the UE access to the CS domain, set Restriction for CS to TRUE; to
restrict the UE access to the PS domain, set Restriction for PS to TRUE.
Set Number of restrained Access Class every time, Range of restrained Access
Class, Access Class Restriction interval between Cells, and Interval length of
Domain Specific Access Class Restriction to appropriate values.
1.
Start Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select
RRC_SYS_INFO_TYPE3.
2.
Check whether manual DSAC is activated by viewing the IE

domainSpecificAccessRestrictionParametersForPLMNOfMIB in the SIB3
message traced on the Uu interface.
If the AccessClassBarred in the IE
domainSpecificAccessRestrictionParametersForPLMNOfMIB exists, as
shown in Figure 248-1, this feature has been activated.
If the AccessClassBarred in the IE
domainSpecificAccessRestrictionParametersForPLMNOfMIB does not exist,
this feature is not activated.
Figure 248-1 DSAC activated
1.
Issue 06 (2013-03-25)
To deactivate manual DSAC, run the BSC6900 MML command RMV

UCELLDSACMANUALPARA (CME single configuration: UMTS Cell
827
RAN14.0
Configuration Express > Cell Parameters > The Parameters of The Manually
Triggered DSAC Algorithm in the Cell; CME batch modification center: not
supported).
2.
To deactivate automatic DSAC, run the BSC6900 MML command SET

UDSACAUTOALGO (CME single configuration: UMTS Radio Global
Configuration Express > Access Restriction Algorithm Parameters
Configuration > The Parameters of the Automatically Triggered DSAC
Algorithm; CME batch modification center: 3.15 Modifying RNC Parameters in
Batches). In this step, set Switch for auto DSAC to OFF.
----End
Example
//Activating DSAC
ADD UCELLDSACMANUALPARA: CellId=223, CnOpIndex=0, CsRestriction=TRUE,
PsRestriction=TRUE, RestrictionType=RestrictionFlexible, NumberOfACs=4,
AcRange=AC0-1&AC1-1&AC2-1&AC3-1&AC4-1&AC5-1&AC6-1&AC7-1&AC8-1&AC9-1&AC100&AC11-0&AC12-0&AC13-0&AC14-0&AC15-0, AcRstrctIntervalLen=10;
SET UDSACAUTOALGO: DsacAutoSwitch=ON, CsRestriction=TRUE,
PsRestriction=TRUE, NumberOfACs=2,
AcRange=AC0-1&AC1-1&AC2-1&AC3-1&AC4-1&AC5-1&AC6-1&AC7-1&AC8-1&AC9-1&AC100&AC11-0&AC12-0&AC13-0&AC14-0&AC15-0, AcIntervalOfCells=1,
AcRstrctIntervalLen=10;
//Deactivating DSAC
RMV UCELLDSACMANUALPARA: CellId=223, CnOpIndex=0;
SET UDSACAUTOALGO: DsacAutoSwitch=OFF;
Issue 06 (2013-03-25)

828
RAN14.0
249 Configuring Multi Frequency Band Networking

Management
249
Configuring Multi Frequency Band

Networking Management
Multi Frequency Band Networking Management.
Prerequisites
l

WRFD-020400 DRD Introduction Package
WRFD-020302 Inter Frequency Hard Handover Based on Coverage
WRFD-020303 Inter-RAT Handover Based on Coverage should be enabled
WRFD-020306 Inter-RAT Handover Based on Load
WRFD-020305 Inter-RAT Handover Based on Service
WRFD-021200 HCS (Hierarchical Cell Structure)
WRFD-020103 Inter Frequency Load Balance
NOTE
If one of these dependent features is not enabled, the corresponding function will not be available in the
multi frequency band networking solution. Operator can choose which feature to use or not.
License
Context
With this feature, the operator can simultaneously provide services on multiple frequency bands.
This feature implements the functions such as mobility management, load balancing, and traffic
balancing between frequency bands. In multi-frequency-band networking scenarios, this feature
can provide seamless communication to improve the system capacity.
In RAN14.0, inter-band blind handovers can be triggered by basic congestion of uplink credit
resources. This helps mitigate basic congestion of uplink credit resources and therefore lowers
Issue 06 (2013-03-25)

829
RAN14.0
249 Configuring Multi Frequency Band Networking

Management
the probability of admission failures due to uplink credit resource congestion. For details about
the activation procedure, verification procedure, and deactivation procedure of this function, see
the dependent feature 247 Configuring Inter Frequency Load Balance.
l
Precautions
None
Data Preparation
None
Procedure
l
None
None
None
----End
Example
None
Issue 06 (2013-03-25)

830
RAN14.0
250
Configuring Enhanced Multiband

Management
Enhanced Multiband Management.
Prerequisites
l

WRFD-020110 Multi Frequency Band Networking Management and
WRFD-020400 DRD Introduction Package when traffic steering is implemented
among inter-frequency cells
WRFD-020110 Multi Frequency Band Networking Management and
WRFD-020103 Inter-Frequency Load Balance when load sharing is performed
among inter-frequency cells
If a feature is not activated, the corresponding function is unavailable in the multifrequency band networking solution. Features can be configured according to
operator requirements.
License
Context
In a multiband network, the cells that work in different frequency bands have different coverage
areas. In this case, blind handovers may lead to call drops. When this feature is enabled, handover
decisions are made based on inter-frequency measurement results. This increases the handover
success rate.
In inter-frequency traffic steering, each cell is configured with the priority for carrying a type
of service (R99 RT, R99 NRT, HSPA, and others). After the RAB is set up, inter-band
measurement is performed to ensure that a UE accesses the cell with the highest priority.
Issue 06 (2013-03-25)

831
RAN14.0
In inter-band load sharing, load reshuffling (LDR) may trigger a load-based inter-frequency
handover after RAB setup. A target cell is selected based on the quality measurement of cells.
Only the cell that meets the quality requirement is selected. Before RAN14.0, measurementbased inter-band handovers for inter-band load balancing are triggered only by basic congestion
of power resources. In RAN14.0, inter-band handovers can also be triggered by basic congestion
of uplink credit resources. This balances uplink credit resources between cell groups or NodeBs
and increases uplink credit resource utilization.
l
Precautions
None
Data Preparation
Parameter Name
Parameter ID
Setting
Description
Source
MeasurementBased DRD Switch
BasedOnMeasHRe
tryDRDSwitch
Set this parameter

to ON.
Network plan
DrdOrLdrFlag
DrdOrLdrFlag
Set this parameter

to TRUE.
Network plan
InterFreq Load
Handover Method
Selection
InterFreqLDHOMe
thodSelection
Set this parameter

to MEASUREHO.
Network plan
Aperiodic DRD
Retry Switch
BlindDrdExceptHRetrySwitch
Use the
recommended
value.
Network plan
DRD Measurement
Period Retry Timer
Length
HRetryTimerLength
Use the
recommended
value.
Network plan
Inter-frequency
Measure Periodical
Measurement
Report Period
PrdReportInterval
Use the
recommended
value.
Network plan
Target Frequency
RSCP Trigger
Threshold
TargetFreqThdRscp
Use the
recommended
value.
Network plan
Target Frequency
EcNo Trigger
Threshold
TargetFreqThdEcN
0
Use the
recommended
value.
Network plan
DRD Measurement
Failure Punish
Periods
DrdFaiPenaltyPeriodNum
Use the
recommended
value.
Network plan
Procedure
l
Configuring this feature based on traffic steering
Issue 06 (2013-03-25)

832
RAN14.0
1.
Run the Run the BSC6900 MML command MML command SET UDRD (CME
single configuration: UMTS Radio Global Configuration Express > Directed
Retry Parameter Configuration > RNC-Oriented DRD Algorithm
Parameters; CME batch modification center: 3.15 Modifying RNC Parameters
in Batches). In this step, set Measurement-Based DRD Switch to ON.
2.
Run the Run the BSC6900 MML command MML command MOD
modification center: not supported). In this step, set DrdOrLdrFlag to TRUE
(Send).
Configuring this feature based on load sharing
1.
modification center: not supported). In this step, set DrdOrLdrFlag to TRUE
(Send).
2.
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set
InterFreq Load Handover Method Selection to MEASUREHO
(MEASUREHO).
3.
Run the BSC6900 MML commandSET UMCDRD (CME single configuration:

UMTS Radio Global Configuration Express > Directed Retry Parameter
Configuration > RNC Based Measurement DRD Algorithm Parameters;
CME batch modification center: 3.15 Modifying RNC Parameters in Batches)
to set RNC-oriented DRD algorithm parameters.
Verifying this feature based on traffic steering
1.
Configure cells A and B. Cell A provides R99 services, and cell B provides HSPA
services.
2.
Enable the UE to establish an R99 service in cell A. Use the UE to download a large
file.
3.
View the RRC_MEAS_CTRL message transmitted on the Uu interface. You can find
that this message contains inter-frequency measurement control information, as
Figure 250-1 IEs contained in RRC_MEAS_CTRL
4.
After the UE sends an inter-frequency measurement report, the UE is handed over to

cell B if inter-frequency cell B meets the related threshold requirements.
Verifying this feature based on load sharing
Issue 06 (2013-03-25)
1.
Configure cells A and B. Both the cells provide R99 services.
2.
Enable the UE to establish an R99 service in cell A.

833
RAN14.0
3.
If a large number of users access cell A, cell A is congested. View the

RRC_MEAS_CTRL message transmitted on the Uu interface. You can find that this
message contains inter-frequency measurement control information.
4.
After the UE sends an inter-frequency measurement report, the UE is handed over to

cell B if inter-frequency cell B meets the related threshold requirements.
Deactivating this feature based on traffic steering
1.
Run the Run the BSC6900 MML command MML command SET UDRD (CME
Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters;
CME batch modification center: 3.15 Modifying RNC Parameters in Batches). In
this step, set BasedOnMeasHRetryDRDSwitch to OFF.
Deactivating this feature based on load sharing

1.
Run the Run the BSC6900 MML command MML command MOD UCELLLDR
Parameters > Cell LDR Algorithm Parameters; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches). In this step, set
InterFreqLDHOMethodSelection to BLINDHO(BLINDHO).
----End
Example
//Configuring this feature based on traffic steering
//Turning on the measurement-based DRD switch SET UDRD:
BasedOnMeasHRetryDRDSwitch=ON;
//Turning on the measurement indication switch of an inter-frequency
neighboring cell MOD UINTERFREQNCELL: RNCId=2021, CellId=3000,
NCellRncId=2021, NCellId=3002, DrdOrLdrFlag=TRUE;
//Configuring this feature based on load sharing

//Turning on the measurement switch of an inter-frequency neighboring cell
MOD UINTERFREQNCELL: RNCId=2021, CellId=3000, NCellRncId=2021,
NCellId=3002, DrdOrLdrFlag=TRUE;
//Setting the load-based inter-frequency handover policy to measurementbased handover MOD UCELLLDR: CellId=3000,
InterFreqLDHOMethodSelection=MEASUREHO;
//Deactivating this feature based on traffic steering

//Turning off the measurement-based DRD switch SET UDRD:
BasedOnMeasHRetryDRDSwitch=OFF;
//Deactivating this feature based on load sharing
Issue 06 (2013-03-25)

834
RAN14.0
//Setting the load-based inter-frequency handover policy to blind

handover MOD UCELLLDR: CellId=3000, InterFreqLDHOMethodSelection=BLINDHO;
Issue 06 (2013-03-25)

835
RAN14.0
251
Configuring DRD Introduction

Package
DRD Introduction Package.
Prerequisites
l
None

None
License
Context
This feature supports DRD and redirection for users between inter-frequency/inter-RAT cells
covering the same area. DRD Introduction Package includes five features: WRFD-02040001
Intra System Direct Retry, WRFD-02040002 Inter System Direct Retry, WRFD-02040003 Inter
System Redirect, WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup, and
Inter-frequency Redirection Based on Distance.
l
Precautions
The following describes how to activate, verify, and deactivate inter-frequency redirection
based on distance. For details about how to activate, verify, and deactivate the other
features, see the corresponding feature activation guide.
255 Configuring Traffic Steering and Load Sharing During RAB Setup
Issue 06 (2013-03-25)
Data Preparation

836
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Inter-freq Redirect
Propa Delay Thres
InterFreqRedirDelayThd
10
Network plan
(internal plan)
Inter-freq
Redirection Factor
of LDR
InterFreqRedirFactorOfLDR
50
Network plan
(internal plan)
Inter-freq
Redirection Factor
of Normal
InterFreqRedirFactorOfNorm
Network plan
(internal plan)
ReDirection target
band indicator
RedirBandInd
DependOnNCell
Network plan
(internal plan)
Redirection Target
UL Frequency
Index
ReDirUARFCNUplinkInd
None
Network plan
Redirection target
uplink UARFCN
ReDirUARFCNUplink
None
Network plan
Redirection target
downlink
UARFCN
ReDirUARFCNDo
wnlink
None
Network plan
Procedure
l
Activating Inter-frequency Redirection Based on Distance

1.
Run the BSC6900 MML command SET UDISTANCEREDIRECTION (CME

Retry Parameter Configuration > RNC-Oriented Delay Based RRC Redirection
Batches) for the RNC or ADD UCELLDISTANCEREDIRECTION (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > CellOriented Delay Based RRC Redirection Parameters; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches) for a cell. In this step,
turn on InterFreqRedirSwitch, set RedirBandInd based on the network plan, and
set other parameters according to the prepared data.
If RedirBandInd is set to DependOnNCell, you do not need to set
ReDirUARFCNUplinkInd, ReDirUARFCNDownlink, and
ReDirUARFCNUplink.
If RedirBandInd is set to other values, set ReDirUARFCNUplinkInd,
ReDirUARFCNDownlink, and ReDirUARFCNUplink based on the network
plan.
NOTE
Inter-frequency redirection based on distance does not select the inter-frequency neighboring
cell under the DRNC as the target cell. DRD and redirection at RRC connection setup do not
select the inter-frequency neighboring cell that uses a different frequency band from the cell
where the RRC connection is to access.
Issue 06 (2013-03-25)

837
RAN14.0
Verifying Inter-frequency Redirection Based on Distance

1.
Start Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select
RRC_RRC_CONN_REJ.
2.
Move a UE to a position where it has a distance from the NodeB but can still detect
pilot signals. Initiate a service using the UE, such as cs service.
NOTE
The distance between the UE and the NodeB must be larger than InterFreqRedirDelayThd
x 78.125 m/chip x 3 chips.
3.
View the Uu interface tracing data.

If the RRC CONNECTION REJECT message includes the redirectionInfo IE
and this IE contains frequencyInfo (information about the cell), as shown in
Figure 251-1, the RNC has redirected the UE to an inter-frequency neighboring
cell and this feature has been activated.
If the RRC CONNECTION REJECT message does not include the
redirectionInfo IE, this feature has not been activated.
Figure 251-1 redirectionInfo IE
Deactivating Inter-frequency Redirection Based on Distance

To deactivate Inter-frequency Redirection Based on Distance at the RNC level, Run the
BSC6900 MML command SET UDISTANCEREDIRECTION (CME single
configuration: UMTS Radio Global Configuration Express > Directed Retry
Parameter Configuration > RNC-Oriented Delay Based RRC Redirection
Batches) to turn off InterFreqRedirSwitch.
To deactivate Inter-frequency Redirection Based on Distance at the cell level, Run the
BSC6900 MML command MOD UCELLDISTANCEREDIRECTION (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > CellOriented Delay Based RRC Redirection Parameters; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches) to turn off
InterFreqRedirSwitch.
----End
Example
//Activating Inter-frequency Redirection Based on Distance
SET UDISTANCEREDIRECTION: InterFreqRedirSwitch=ON,
InterFreqRedirDelayThd=10, InterFreqRedirFactorOfLDR=50,
InterFreqRedirFactorOfNorm=0, RedirBandInd=DependOnNCell;
ADD UCELLDISTANCEREDIRECTION: CellId=1, InterFreqRedirSwitch=ON,
InterFreqRedirDelayThd=10, InterFreqRedirFactorOfLDR=50,
InterFreqRedirFactorOfNorm=0, RedirBandInd=DependOnNCell;
Issue 06 (2013-03-25)

838
RAN14.0
//Deactivating Inter-frequency Redirection Based on Distance

SET UDISTANCEREDIRECTION: InterFreqRedirSwitch =OFF;
MOD UCELLDISTANCEREDIRECTION: CellId=1, InterFreqRedirSwitch =OFF;
Issue 06 (2013-03-25)

839
RAN14.0
252
Configuring Intra System Direct

Retry
WRFD-02040001 Intra System Direct Retry.
Prerequisites
l

The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
License
Context
This feature supports inter-RAT directed retries during RRC connection or radio resource bearer
(RAB) assignment.
Procedure
l
Issue 06 (2013-03-25)
1.

DR_RRC_DRD_SWITCH, DR_RAB_SING_DRD_SWITCH, and
DR_RAB_COMB_DRD_SWITCH.
2.
Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS
Radio Global Configuration Express > Directed Retry Parameter
Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches). In this step, turn
840
RAN14.0
on the RNC-level switches: Service Steering DRD Switch, Load balance DRD
switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD
Switch, Uplink load balance DRD Switch for DC-HSDPA, Measurement-Based
DRD Switch, and Device Type Steering DRD Switch.
3.
Optional: Run the BSC6900 MML command ADD UCELLDRD (CME single
Oriented DRD Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches). In this step, turn on the cell-level
switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load
balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load
balance DRD Switch for DC-HSDPA, and Device Type Steering DRD Switch.
CAUTION
l If a cell is configured with both the RNC-level and cell-level parameters, the celllevel parameter settings take effect. Therefore, do not modify the parameters to
default values when you are configuring the cell-level parameters.
l Intra system direct retry does not select the inter-frequency neighboring cell under
the DRNC as the target cell. DRD and redirection at RRC connection setup do not
select the inter-frequency neighboring cell that uses a different frequency band
from the cell where the RRC connection is to access.
l
1.
2.
Issue 06 (2013-03-25)
Method 1: Verifying this feature during RRC connection setup

a.
Start Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS

interactive service.
b.
The UE sends an RRC_RRC_CONNECT_REQ message from cell 1 to the

BSC6900. The BSC6900 sends the UE an RRC_RRC_CONN_SETUP
message containing the scrambling code of cell 2.
c.
The UE sends an RRC_RRC_CONNECT_SETUP_CMP message from cell

2 to the BSC6900. This indicates that this feature has been activated.
Method 2: Verifying this feature during radio bearer (RB) setup

a.
Start Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS

interactive service.
b.
The BSC6900 sends an RRC_RB_SETUP message from cell 1 to the UE. The
UE sends an RRC_RB_SETUP_CMP message from cell 2 to the BSC6900. If
the service is set up successfully in cell 2 and the data transmission is normal,
1.
modification center: 3.15 Modifying RNC Parameters in Batches) to turn off the
RNC-level switches.
2.
Optional: Run the BSC6900 MML command MOD UCELLDRD (CME single
841
RAN14.0

Modifying UMTS Cell Parameters in Batches) to turn off the cell-level switches.
----End
Example
//Activating Intra System Direct Retry
DrSwitch=DR_RRC_DRD_SWITCH-1&DR_RAB_SING_DRD_SWITCH-1&DR_RAB_COMB_DRD_SWI
TCH-1;
SET UDRD: ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON,
LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON,
ULLdbDRDSwitchDcHSDPA=ON, BasedOnMeasHRetryDRDSwitch=ON, DPGDRDSwitch=ON;
ADD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON,
ULLdbDRDSwitchDcHSDPA=ON, DPGDRDSwitch=ON;
//Deactivating Intra System Direct Retry
SET UDRD: ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF,
LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF,
ULLdbDRDSwitchDcHSDPA=OFF, BasedOnMeasHRetryDRDSwitch=OFF,
DPGDRDSwitch=OFF;
MOD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF,
ULLdbDRDSwitchDcHSDPA=OFF, DPGDRDSwitch=OFF;
Issue 06 (2013-03-25)

842
RAN14.0
253
Configuring Inter System Direct

Retry
WRFD-02040002 Inter System Direct Retry.
Prerequisites
l

License
Context
This feature supports inter-RAT directed retries during RAB assignment.
Procedure
l
Issue 06 (2013-03-25)
1.

DR_RAB_SING_DRD_SWITCH, DR_RAB_COMB_DRD_SWITCH, and
DR_INTER_RAT_DRD_SWITCH.
2.
the RNC-level parameter Max inter-RAT direct retry number to a value other than
843
RAN14.0
zero, and turn on the following RNC-level switches: Service Steering DRD
Switch, Load balance DRD switch for DCH, Load balance DRD switch for
HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DCHSDPA, Measurement-Based DRD Switch, and Device Type Steering DRD
Switch.
3.
Modifying UMTS Cell Parameters in Batches). In this step, set the cell-level
parameter Max inter-RAT direct retry number to a value other than zero. Turn on
the following cell-level switches: Service Steering DRD Switch, Load balance DRD
switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD
Switch, Uplink load balance DRD Switch for DC-HSDPA, and Device Type
Steering DRD Switch.
CAUTION
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level
parameter settings take effect. Therefore, do not modify the parameters to default
values when you are configuring the cell-level parameters.
l
1.
Start Iu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive

service.
2.
In the Iu Interface Trace dialog box, view the following procedure:

a.
The core network (CN) sends a RAB_ASSIGNMENT_REQ message to the

BSC6900.
b.
The BSC6900 responds to the CN with a RAB_ASSIGNMENT_RSP message

containing the cause value "direct retry."
c.
The BSC6900 sends the CN a RELOCATION REQUIRED message

containing the cause value "direct retry."
1.
Max Inter-RAT direct retry number to 0. Turn off the RNC-level switches.
2.
Modifying UMTS Cell Parameters in Batches). In this step, set Max inter-RAT
direct retry number to 0. Turn off the cell-level switches.
----End
Example
//Activating Inter System Direct Retry
DrSwitch=DR_RAB_SING_DRD_SWITCH-1&DR_RAB_COMB_DRD_SWITCH-1&DR_INTER_RAT_D
Issue 06 (2013-03-25)

844
RAN14.0
RD_SWITCH-1;
SET UDRD: DRMaxGSMNum=3, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON,
ULLdbDRDSwitchDcHSDPA=ON, BasedOnMeasHRetryDRDSwitch=ON, DPGDRDSwitch=ON;
ADD UCELLDRD: CellId=11, DRMaxGSMNum=3, ServiceDiffDrdSwitch=ON,
LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON,
ULLdbDRDSwitchDcHSDPA=ON, DPGDRDSwitch=ON;
//Deactivating Inter System Direct Retry
SET UDRD: DRMaxGSMNum=0, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF,
ULLdbDRDSwitchDcHSDPA=OFF, BasedOnMeasHRetryDRDSwitch=OFF,
DPGDRDSwitch=OFF;
MOD UCELLDRD: CellId=11, DRMaxGSMNum=0, ServiceDiffDrdSwitch=OFF,
LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF,
ULLdbDRDSwitchDcHSDPA=OFF, DPGDRDSwitch=OFF;
Issue 06 (2013-03-25)

845
RAN14.0
254
Configuring Inter-System Redirect
WRFD-02040003 Inter System Redirect.
Prerequisites
l

License
Context
This feature allows inter-system redirection during RRC connection setup.
Procedure
l
l
Issue 06 (2013-03-25)
1.

Parameters in Batches). In this step, set Direct Retry Switch to
DR_RRC_DRD_SWITCH.
2.
ConnectFailRrcRedirSwitch to Allowed_To_Inter_RAT.
846
RAN14.0
1.
Start Uu Interface Trace on the BSC6900 LMT. Use a UE to initiate an RRC

connection setup request.
2.
The following procedure is traced on the Uu interface:

a.
The UE sends an RRC_SETUP_REQ message.
b.
The BSC6900 responds with an RRC_CONN_REJ message, carrying GSMTargetCellInfo in the IE redirectioninfo.
1.
RRC redirect switch to OFF or Only_To_Inter_Frequency.
----End
Example
//Activating Inter-System Redirect
SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1;
SET UDRD: ConnectFailRrcRedirSwitch=Allowed_To_Inter_RAT;
//Deactivating Inter-System Redirect
SET UDRD: ConnectFailRrcRedirSwitch=OFF;
Issue 06 (2013-03-25)

847
RAN14.0
255 Configuring Traffic Steering and Load Sharing During

RAB Setup
255
Configuring Traffic Steering and

Load Sharing During RAB Setup
WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup.
Prerequisites
l

License
Context
With this feature, service steering and load sharing among different frequencies or bands are
implemented during RAB setup based on the service type and cell load.
Procedure
l
Issue 06 (2013-03-25)
1.

configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell; CME batch modification center: not supported). In this
step, add an inter-frequency cell by setting the related parameters according to the
network plan.
2.
Run the BSC6900 MML command ADD USPG (CME single configuration: UMTS
Global Configuration Express > Radio Basic Data Configuration > Service
Priority Group; CME batch modification center: not supported). In this step, add a
service priority group and set the service priority of each type of service according to
the network plan.
3.
848
RAN14.0

RAB Setup

Parameters in Batches). In this step, set the cell service priority by setting the related
parameters according to the network plan.
4.

DR_RAB_SING_DRD_SWITCH.
5.
on Service differential drd switch and Measurement-Based DRD Switch.
1.
Start Uu interface tracing on the BSC6900 LMT.
2.
Use a UE in a cell to initiate a PS interactive service. This cell carries low-priority

services. The target inter-frequency neighboring cell has light load and carries highpriority services.
In the Uu Interface Trace dialog box, view the following procedure:
After the UE in a cell sends an RRC_RB_SETUP_CMP message, the BSC6900
sends an RRC_PH_CH_RECFG message to the UE.
The UE responds with an RRC_PH_CH_RECFG_CMP message.
The BSC6900 enters the compressed mode.
The UE in periodical mode sends an RRC_MEAS_CTRL message to the
BSC6900 to measure the signal quality of the target cell.
The BSC6900 sends the UE an RRC_RB_RECFG message containing the primary
scrambling code and frequency of the inter-frequency neighboring cell.
The UE sends an RRC_RB_RECFG_CMP message from the inter-frequency
neighboring cell.
1.
off Service differential drd switch and Measurement-Based DRD Switch.
----End
Example
//Activating Service Steering and Load Sharing During RAB Setup
ADD USPG: SpgId=1, PriorityServiceForR99RT=2, PriorityServiceForR99NRT=2,
PriorityServiceForHSDPA=2, PriorityServiceForHSUPA=2,
PriorityServiceForExtRab=1;
Issue 06 (2013-03-25)

849
RAN14.0

RAB Setup
ADD USPG: SpgId=2, PriorityServiceForR99RT=1, PriorityServiceForR99NRT=1,

PriorityServiceForHSDPA=1, PriorityServiceForHSUPA=1,
PriorityServiceForExtRab=1;
MOD UCELL: CellId=1, SpgId=1;
MOD UCELL: CellId=2, SpgId=2;
SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1;
SET UDRD: ServiceDiffDrdSwitch=ON, BasedOnMeasHRetryDRDSwitch=ON;
//Deactivating Service Steering and Load Sharing During RAB Setup
SET UDRD: ServiceDiffDrdSwitch=OFF, BasedOnMeasHRetryDRDSwitch=OFF;
Issue 06 (2013-03-25)

850
RAN14.0
256
Configuring Measurement Based

Direct Retry
Measurement Based Direct Retry.
Prerequisites
l
None

The feature WRFD-020400 DRD Introduction Package has been configured before this
License
Context
After a UE has successfully set up the RRC connection, the RNC instructs the UE to initiate
inter-frequency or inter-system measurements. Upon receipt of a radio access bearer (RAB)
assignment request from the CN, the RNC performs Directed Retry Decision (DRD) based on
the measurement results.
This feature increases the success rate of DRD and reduces the call drop rate caused by DRD
with blind handovers.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML commandADD UCELLMBDRINTERFREQ (CME single

Oriented Inter-frequency Measurement Parameters for MBDR Algorithm; CME
batch modification center: 3.18 Modifying UMTS Cell Parameters in Batches). In
this step, set MBDR Switch, Inter-freq Measure Quantity, and other parameters
related to MBDR inter-frequency measurements.
851
RAN14.0
2.
Run the BSC6900 MML commandSET UNBMPARA (CME single configuration:

UMTS Radio Global Configuration Express > NodeB Management
Configuration > Algorithm Parameters Related to NodeB Configuration and
Maintenance; CME batch modification center: not supported). In this step, select
PERFENH_MBDR_LOADCOND_OPT_SWITCH under Performance
Enhancement Switch.
3.
Run the BSC6900 MML commandSET UCORRMPARA (CME single

RNC Parameters in Batches). In this step, select
PERFENH_MBDR_TARCELLSEL_OPT_SWITCH under Performance
Enhancement Switch, and preferentially select a cell with the optimum signal quality
as the target cell.
NOTE
When selecting the target cell after the MBDR algorithm is enabled, sort the candidate cells based
on Inter-freq Measure Quantity of MBDR (by running the ADD
UCELLMBDRINTERFREQ (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell Oriented Inter-frequency Measurement Parameters for MBDR
Algorithm; CME batch modification center: 3.18 Modifying UMTS Cell Parameters in
Batches) command), and select a cell with the optimum signal quality as the target cell.
4.
Run the BSC6900 MML commandADD UCELLMBDRINTERRAT (CME single

Oriented Inter-RAT Measurement Parameters for MBDR Algorithm; CME
this step, set MBDR switch in the parameters related to MBDR inter-RAT
measurements.
5.
Run the BSC6900 MML commandADD UINTERFREQNCELL (CME single

configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell; CME batch modification center: not supported). In this
step, set Flag of MBDR Cell to TRUE(send), and set MBDR Cell Priority based
1.
Congestion may occur when a large number of UEs access a cell. If a handover based
on inter-frequency measurements is used to achieve load reshuffling (LDR), you can
view the inter-frequency measurement control information on the Uu interface. After
a UE sends the inter-frequency measurement report, the UE will be handed over to
another cell.
1.
Run the BSC6900 MML commandMOD UCELLMBDRINTERFREQ (CME

Oriented Inter-frequency Measurement Parameters for MBDR Algorithm; CME
batch modification center: 3.18 Modifying UMTS Cell Parameters in Batches) to
clear the MBDR Switch check box.
----End
Example
//Activating the feature Measurement-based Direct Retry
//Enabling the MBDR algorithm
ADD UCELLMBDRINTERFREQ: CellId=1,
Issue 06 (2013-03-25)

852
RAN14.0
InterFreqActiveType=CSAMR_INTERFREQ-1&CSNONAMR_INTERFREQ-1&PSR99_INTERFRE
Q-1&PSHSPA_INTERFREQ-1, InterFreqReportMode=EVENT_TRIGGER;
SET UNBMPARA: PerfEnhanceSwitch=PERFENH_MBDR_LOADCOND_OPT_SWITCH-1;
SET UCORRMPARA: PerfEnhanceSwitch=PERFENH_MBDR_TARCELLSEL_OPT_SWITCH-1;
//Setting the parameters related to cell-level MBDR inter-RAT
measurements
ADD UCELLMBDRINTERRAT: CellId=1, InterRatActiveType=CSAMR_INTERRAT-1;
//Setting the MBDR cell flag of the inter-frequency neighboring cell and
the MBDR cell priority
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE,
NPrioFlag=FALSE, MBDRFlag=TRUE, MBDRPrio=2, InterNCellQualReqFlag=FALSE;
//Deactivating the feature Measurement-based Direct Retry
//Disabling the MBDR algorithm
MOD UCELLMBDRINTERFREQ: CellId=1,
InterFreqActiveType=CSAMR_INTERFREQ-0&CSNONAMR_INTERFREQ-0&PSR99_INTERFRE
Q-0&PSHSPA_INTERFREQ-0;
Issue 06 (2013-03-25)

853
RAN14.0
257 Configuring Service Steering and Load Sharing in RRC

Connection Setup
257
Configuring Service Steering and
Load Sharing in RRC Connection Setup

Service Steering and Load Sharing in RRC Connection Setup.
Prerequisites
l

License
Others
The UE needs to be compliant with 3GPP Release 6 (or later) to support the feature.
Context
With this feature, service steering and load sharing among different frequencies, bands, or radio
access technologies (RATs) can be achieved during radio resource control (RRC) connection
setup based on the service type and cell load.
Procedure
l
NOTE
The adaptive multirate (AMR) service that is redirected to an inter-RAT cell during RRC connection setup
is used as an example.
1.
Issue 06 (2013-03-25)

854
RAN14.0

Connection Setup
Parameters in Batches) to enable the RRC directed retry decision (DRD) function.
In this step, set Direct Retry Switch to DR_RRC_DRD_SWITCH.
2.
Run the BSC6900 MML command SET UREDIRECTION (CME single

Parameter Configuration > RNC-Oriented RRC Redirection Parameters; CME
step, set RNC-level Traffic Type to AMR and Redirection Switch to
ONLY_TO_INTER_RAT.
3.
Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION

Parameters > Cell-level RRC Redirection Parameters; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set celllevel Traffic Type to AMR and Redirection Switch to
ONLY_TO_INTER_RAT.
NOTE
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter
settings take effect.
1.
Use a UE to send an RRC_SETUP_REQ message with the cause value "Originating

Conversational Call."
2.
The BSC6900 responds with an RRC_CONN_REJ message. If "redirectioninfo" of

the message contains "GSM-TargetCellInfo," this feature has been activated.
1.

Parameters in Batches) to disable the RRC DRD function.
2.
Run the BSC6900 MML command SET UREDIRECTION (CME single

Parameter Configuration > RNC-Oriented RRC Redirection Parameters; CME
step, set Redirection Switch to an appropriate value to disable the RNC-level RRC
DRD based on service steering.
3.
Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION

Parameters > Cell-level RRC Redirection Parameters; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set
Redirection Switch to an appropriate value to disable the cell-level RRC DRD based
on service steering.
----End
Example
/*Activating Service Steering and Load Sharing in RRC Connection Setup*/
/*Enabling the RRC DRD function*/
//Setting the RNC-level DRD switch
SET UREDIRECTION: TrafficType=AMR, RedirSwitch=ONLY_TO_INTER_RAT,
Issue 06 (2013-03-25)

855
RAN14.0

Connection Setup
RedirFactorOfNorm=0, RedirFactorOfLDR=0, RedirBandInd=BAND1,

ReDirUARFCNUplinkInd=FALSE, ReDirUARFCNDownlink=10713;
//Setting the cell-level DRD switch
MOD UCELLREDIRECTION: CellId=1, TrafficType=AMR,
RedirSwitch=ONLY_TO_INTER_RAT, RedirFactorOfNorm=0,
RedirFactorOfLDR=100, RedirBandInd=BAND1, ReDirUARFCNUplinkInd=FALSE,
ReDirUARFCNDownlink=10563;
/*Deactivating Service Steering and Load Sharing in RRC Connection
Setup*/
//Disabling the RRC DRD function
//Setting the RNC-level DRD switch
SET UREDIRECTION: TrafficType=PSHSPA, RedirSwitch=OFF;
//Setting the cell-level DRD switch
MOD UCELLREDIRECTION: CellId=100, TrafficType=PSHSPA, RedirSwitch=OFF;
Issue 06 (2013-03-25)

856
RAN14.0
258
Configuring Uplink Flow Control of

User Plane
Uplink Flow Control of User Plane.
Prerequisites
l

License
Context
The Uplink Flow Control of User Plane feature is a Huawei proprietary feature. This feature
detects uplink packet loss for R99 services by using private information elements (IEs) on the
Iub interface. In addition, this feature controls uplink traffic by sending Transport Format
Combination Control messages. By doing this, this feature prevents uplink packet loss caused
by lack of flow control, and increases transmission efficiency.
Procedure
l
1.
Issue 06 (2013-03-25)

RNC Parameters in Batches). In this step, set Process switch to
NODEB_PRIVATE_INTERFACE_SWITCH.

857
RAN14.0

NOTE
NODEB_PRIVATE_INTERFACE_SWITCH controls all the functions that are achieved

by using the private messages on the Iub interface. Turn on other related switches if flow control
over the uplink user plane is required.
2.
Run the NodeB MML command SET R99FLOWCTRLSWTCH (CME single

Locell Algorithm Parameters > Locell Parameters >
R99FLOWCTRLSWTCH; CME batch modification center: not supported) to turn
on the cell-level switch for uplink user plane flow control.
1.
Start an Iub interface tracing task on the BSC6900 LMT, as shown in Figure 258-1.
Figure 258-1 Iub interface trace dialog box
2.
Issue 06 (2013-03-25)
Establish an R99 BE service on the UE. Observe the NBAP_RL_RECFG_PREP

message in the traced Iub data. Check the IE iE-Extensions in DCH-FDDInformationItem. If there is an IE trafficClass-Private, as shown in Figure 258-2,
the feature at the BSC6900 has been activated.

858
RAN14.0
Figure 258-2 TrafficClass-Private
1.
Run the NodeB MML command SET R99FLOWCTRLSWTCH (CME single

Locell Algorithm Parameters > Locell Parameters >
R99FLOWCTRLSWTCH; CME batch modification center: not supported) to turn
off the cell-level switch for uplink user plane flow control.
----End
Example
//Activating Uplink Flow Control of User Plane
SET R99FLOWCTRLSWTCH: SWITCH=OPEN, LOCELL=1;
//Deactivating Uplink Flow Control of User Plane
SET R99FLOWCTRLSWTCH: SWITCH=CLOSE, LOCELL=1;
Issue 06 (2013-03-25)

859
RAN14.0
259
Configuring Intra Frequency Load

Balance
Intra Frequency Load Balance.
Prerequisites
l

License
Context
This feature enables the change in cell load by adjusting the cell PCPICH power. For those UEs
in soft handover state, this feature enables the intra-frequency neighboring cells to share the cell
load by removing high load cell from the active set.
Procedure
l
Issue 06 (2013-03-25)
1.

2.

Parameters in Batches). In this step, select INTRA_FREQUENCY_LDB(Intra
Frequency LDB Algorithm) from the Cell LDC algorithm switch drop-down list.
3.
860
RAN14.0
Intra-frequency LDB period timer length to an appropriate value.
4.
Run the BSC6900 MML command MOD UCELLLDB (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Oriented LDB
Cell Parameters in Batches) to set the following parameters associated with the celllevel intra-frequency load balancing (LDB) algorithm to appropriate values:
Cell overload threshold
Pilot power adjustment step
Cell under load threshold
5.
Run the BSC6900 MML command MOD UPCPICHPWR (CME single

PCPICH; CME batch modification center: 3.20 Modifying UMTS Channel
Parameters in Batches). In this step, set P-CPICH parameters associated with intrafrequency LDB, including Max transmit power of PCPICH and Min transmit
power of PCPICH to appropriate values.
To verify that the RNC can balance the cell load by adjusting the P-CPICH power of a cell,
perform the following steps:
1.
On the BSC6900 LMT, open the Monitor tab page. Create the task of monitoring
PCPICH TxPower of CELL_A11.
2.
Run the NodeB MML command STR DLSIM to simulate high load in CELL_A11.
3.
In the Cell Performance Monitoring dialog box, check the pilot power of
CELL_A11.
Expected result: As the cell load increases, the pilot power periodically decreases. The
actual pilot power must not be decreased to a level lower than the configured minimum
pilot power.
4.
The NBAP_CELL_RECFG_REQ and NBAP_CELL_RECFG_RSP messages

should be displayed in the Iub tracing result. In the NBAP_CELL_RECFG_REQ
message, check whether the RNC has reduced the pilot power.
5.
Run the NodeB MML command STR DLSIM to stop simulating high load in
CELL_A11.
6.
In the Cell Performance Monitoring dialog box, check the pilot power of
CELL_A11.
Expected result: As the cell load becomes normal, the pilot power periodically
increases. The actual pilot power must not be increased to a level higher than the
configured maximum pilot power.
1.

Parameters in Batches). In this step, deselect INTRA_FREQUENCY_LDB from
the Cell LDC algorithm switch drop-down list.
2.
Restore the parameter settings modified in the activation procedure.
----End
Issue 06 (2013-03-25)

861
RAN14.0
Example
//Activating Intra Frequency Load Balance
//Configuring intra-frequency neighboring cells
//Enabling the cell-oriented intra-frequency LDB algorithm
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-1;
//Setting the intra-frequency LDB period
SET ULDCPERIOD: IntraFreqLdbPeriodTimerLen=1800;
//Setting parameters associated with the cell-oriented intra-frequency
LDB algorithm to appropriate values
MOD UCELLLDB: CellId=111, PCPICHPowerPace=2, CellOverrunThd=90,
CellUnderrunThd=30;
//Setting the P-CPICH associated parameters for intra-frequency LDB
MOD UPCPICHPWR: CellId=111, MaxPCPICHPower=346, MinPCPICHPower=313;
//Verifying Intra Frequency Load Balance
STR DLSIM: LOCELL=111, LR=90;
STP DLSIM: LOCELL=111;
//Deactivating Intra Frequency Load Balance
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-0;
Issue 06 (2013-03-25)

862
RAN14.0
260
Configuring Dynamic Target ROT

Adjustment
Dynamic Target RoT Adjustment.
Prerequisites
l
The BTS3812E, BTS3812A, or BTS3812AE must be configured with the EBBI, EBOI,
EULP+EDLP, or EULPd+EDLP boards. Downlink cells must be set up on the EBBI,
EBOI, or EDLP board.
The DBS3800 must be configured with the EBBC or EBBCd board, and downlink cells
must be set up on the EBBC or EBBCd board.
The 3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf
board. Downlink cells must be set up on the WBBPb, WBBPd, or WBBPf board.

feature depends on feature WRFD-010612 HSUPA Introduction Package.
License
Others
This feature should be used with professional services.
Context
l
Precautions
None
Issue 06 (2013-03-25)
Data Preparation

863
RAN14.0
Parameter Name
Parameter ID
Recomme
nded
Parameter
Settings
Data Source
Switch for Dynamically

Adjusting RoT
DynTgtRoTCtrlSwitch
ON
None
Interval for Deciding

Whether to Adjust RoT
TgtRoTAdjPeriod
None
Step for Increasing RoT
TgtRoTUpAdjStep
10
None
Step for Decreasing RoT
TgtRoTDownAdjStep
20
None
Upper Limit for the

Maximum Uplink Load
Factor
UpLimitForMaxULTgtLdFactor
90
None
Procedure
l
1.
Run the BSC6900 MML commandADD UCELLLICENSE (CME single

UMTS Cell Parameters in Batches). In this step, select
DYN_TGTROT_CTRL_SWITCH(Dynamic Target RoT Adjustment) under
Function Switch1 to enable the license of dynamic target ROT adjustment for a
specified cell.
2.
Run the BSC6900 MML command MML command ADD UCELLHSUPA (CME
UMTS Cell Parameters in Batches) or MOD UCELLHSUPA (CME single
UMTS Cell Parameters in Batches) to enable Dynamic Target RoT Adjustment. In
this step, set Switch for Dynamically Adjusting RoT to ON(ON).
Check the related performance counters on the M2000.

1.
Issue 06 (2013-03-25)
On the M2000, check the counter VS.HSUPA.TgtRoTInc or

VS.HSUPA.TgtRoTDec. If the value of either counter is not 0, this feature has
been activated.
Initiate message tracing on the LMT.

1.
On the Run the BSC6900 MML command LMT, click Trace and display the
Iub Interface Trace dialog box. On the Basic tab page, select the NBAP check
box under the Trace Type parameter. On the NBAP tab page, select the
NBAP_COMM_MEAS_RPRT check box under the Message Type parameter.
Then, click Submit to enter the Iub interface trace page.
2.
On the Iub interface trace page, check Message Type. If

NBAP_COMM_MEAS_RPRT is displayed and the measurement type is uLTimeslot ISCP, this feature has been activated, as shown in Figure 260-1.
864
RAN14.0
Figure 260-1 Iub message tracing
1.
UCELLHSUPA (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Configuration of HSUPA in Cell; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches) to disable Dynamic
Target RoT Adjustment. In this step, set Switch for Dynamically Adjusting RoT to
OFF(OFF).
----End
Example
//Activating Dynamic Target RoT Adjustment
ADD UCELLLICENSE: CellId=1, FuncSwitch1=DYN_TGTROT_CTRL_SWITCH-1;
ADD UCELLHSUPA: CellId=1, DynTgtRoTCtrlSwitch=ON;
//Deactivating Dynamic Target RoT Adjustment
MOD UCELLHSUPA: CellId=1, DynTgtRoTCtrlSwitch= OFF;
Issue 06 (2013-03-25)

865
RAN14.0
261
Configuring CE Overbooking
CE Overbooking.
Prerequisites
l
The 3900 series base station must be configured with the WBBPb, WBBPd, or
WBBPf board.
The DBS3800 must be configured with the EBBC or EBBCd board.
EBOI, or EULPd board.

feature depends on features WRFD-010638 Dynamic CE Resource Management.
License
Others
This feature should be used with Huawei professional services.
Procedure
l
Issue 06 (2013-03-25)
1.
2.
Run the BSC6900 MML command SET UALGORSVPARA (CME single

configuration: UMTS Global Configuration Express > Reserved Parameters >
System Level Reserved Parameters; CME batch modification center: 3.15
Modifying RNC Parameters in Batches). In this step, set Reserved Switch 1 to
RESERVED_SWITCH_1_BIT5.

866
RAN14.0

NOTE
The NodeB baseband board uses different processing specifications for users with different
uplink bearer services, for example, HSUPA TTI 2 ms service,s HSUPA TTI 10 ms services,
and R99 services. When multiple users access the network,
l If this function is disabled, the system attempts to admit all new users using the highest
service bearers supported by the terminal. In this way, accessed users occupy too many
uplink processing specifications and therefore the total number of accessed users decreases.
l If this function is enabled, the NodeB baseband board dynamically selects proper uplink
service bearers for users to maximize the number of accessed users according to actual
NodeB processing specifications.
Verify that the value of the new counter VS.NodeB.ULCreditUsed.Mean,
VS.NodeB.ULCreditUsed.Max or VS.NodeB.ULCreditUsed.Min is not 0. A non-zero
value indicates that CE Overbooking takes effect.
None
----End
Example
//Activation Procedure SET
UALGORSVPARA:RsvSwitch1=RESERVED_SWITCH_1_BIT5-1;
Issue 06 (2013-03-25)

867
RAN14.0
262
Configuring Intelligent Access Class

Control
Intelligent Access Class Control.
Prerequisites
l
This feature does not depend on Hardware.
Dependencies on other Features

License
Others
UEs must support access class control delivered in system information.
For UEs complying with 3GPP Release 5 and earlier releases, access class control
cannot be performed on CS and PS services separately. If the access class of such a UE
is barred, the UE can process neither CS nor PS services.
For UEs complying with 3GPP Release 6 and later releases, access class control can be
performed on CS and PS services separately. Therefore, such a UE can process CS
services while being barred from processing PS services.
Context
This feature prevents a large number of UEs from sending RRC connection setup requests
simultaneously. When the RNC determines that a cell is congested, the RNC restricts the access
of UEs of more access classes. When the RNC determines that congestion is relieved in the cell,
the RNC reduces the number of access classes on which access control is performed. This
prevents excessive RRC connection setup requests from wasting Uu interface resources and
RNC processing resources, relieves network congestion, and improves system stability.
l
Issue 06 (2013-03-25)
Precautions
868
RAN14.0
None.
l
Issue 06 (2013-03-25)
Data Preparation
Paramet
er Name
Parame
ter ID
Parameter Setting
Data Source
Switch
for
Intelligen
t Access
Class
Control
CongAC
Switch
Turn on CongACSwitch for cells

where this feature is planned to be
activated.
Network plan
Cell Cong
Thre with
RRC or
RAB
Setup
Req
Rejection
CongRej
TrigThd
Congestion trigger threshold of the

RRC/RAB setup rejection rate. The
smaller the parameter value, the more
likely the network increases the
number of barred ACs. The default
value is recommended for this
parameter. You can also set the value
for this parameter based on your
expectations on the network KPI.
Network plan
Cell
Restore
Thre with
RRC or
RAB
Setup
Req Rej
CongRej
RelThd
Congestion release threshold of the

RRC/RAB setup rejection rate. The
smaller the parameter value, the less
likely the network decreases the
number of barred ACs. The default
value is recommended for this
parameter. You can also set the value
for this parameter based on your
expectations on the network KPI.
Network plan
Consideri
ng RAB
Rej Rate
in Cell
Cong
Decision
CongOf
RABRej
RateSwi
tch
If the RRC admission threshold is

higher than the RAB admission
threshold, there is a possibility that the
RRC setup rejection rate is not high but
the RAB setup rejection rate is high. In
this case, system resources are wasted.
To prevent this problem, you are
advised to turn on
CongOfRABRejRateSwitch so that
the RAB setup rejection rate is
considered during the cell congestion
decision.
Network plan
Consideri
ng UL
Load in
Cell Cong
Decision
CongOf
UlLoadS
witch
Turn on this switch only when you

want to take the uplink power load
congestion as a necessary condition for
increasing the number of barred ACs.
Network plan

869
RAN14.0
Issue 06 (2013-03-25)
Paramet
er Name
Parame
ter ID
Parameter Setting
Data Source
UL Cell
Power
Load
Threshol
d For Cell
Congesti
on
UlLoad
CongTri
gThd
This parameter is valid only when

CongOfUlLoadSwitch is set to ON.
The default value is recommended for
this parameter.
Network plan
UL Cell
Power
Load
Thre For
Cell Reso
Restorati
on
UlLoad
CongRel
Thd

CongOfUlLoadSwitch is set to ON.
this parameter.
Network plan
Consideri
ng CPU
Usage in
Cell Cong
Decision
CongOf
CpuSwit
ch
Turn on this switch only when you

want to take the SPU CPU usage as a
necessary condition for increasing the
number of barred ACs.
Network plan
CPU
Usage
Threshol
d for Cell
Congesti
on
CpuCon
gTrigTh
d

CongOfCpuSwitch is set to ON. The
default value is recommended for this
parameter.
Network plan
CPU
Usage
Thre for
Cell
Resource
Restorati
on
CpuCon
gRelThd

CongOfCpuSwitch is set to ON. The
default value is recommended for this
parameter.
Network plan
Cell
Congesti
on Check
Interval
CongCh
eckPerio
d

this parameter.
Network plan
Polling
Interval
for
Access
Control
ACPollP
eriod

this parameter.
Network plan

870
RAN14.0
Paramet
er Name
Parame
ter ID
Parameter Setting
Data Source
Range of
Restricte
d Access
Classes
ACRstrc
tRange
This parameter must be configured

when CongACSwitch is set to ON.
The value recommended for this
parameter is AC0, AC1, AC2, AC3,
AC4, AC5, AC6, AC7, AC8, or
AC9. You are not advised to select
AC10 for this parameter. If AC10 is
indicated as barred in a cell, UEs from
AC0 to AC9 and UEs without an IMSI
are not allowed to initiate emergency
calls in this cell.
Network plan
Max No.
of PS
Restricte
d AC for
R6 or
Later
RstrctR6
PSMax
ACNum

this parameter.
Network plan
Max No.
of
Restricte
d Access
Class for
R5 or
Early
RstrctR5
MaxAC
Num

this parameter.
Network plan
Max No.
of PS
Restricte
d AC for
R6 or
Later
RstrctR6
CSMax
ACNum

this parameter.
Network plan
Procedure
l
Run the BSC6900 MML command ADD UCELLCONGACALGO (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Control
Parameters for Intelligent Access; CME batch modification center: 3.18 Modifying
UMTS Cell Parameters in Batches). In this step, perform the following steps:
1.
Set CongACSwitch to ON.
2.
Set ACRstrctRange to an appropriate value.
3.
Optional: Perform the following operations based on the network plan:

If the radio access bearer (RAB) rejection rate needs to be considered during a
congestion decision, set CongOfRABRejRateSwitch to ON, and set
CongRejTrigThd and CongRejRelThd based on site requirements.
Issue 06 (2013-03-25)

871
RAN14.0
If uplink load needs to be considered during a congestion decision, set

CongOfUlLoadSwitch to ON, and set UlLoadCongTrigThd and
UlLoadCongRelThd based on site requirements.
If central processing unit (CPU) load needs to be considered during a congestion
decision, set CongOfCpuSwitch to ON, and set CpuCongTrigThd and
CpuCongRelThd based on site requirements.
Set CongCheckPeriod, ACPollPeriod, RstrctR5MaxACNum,
RstrctR6CSMaxACNum, and RstrctR6PSMaxACNum based on site
requirements.
l
The VS.AC.CongCtl.Time counter reflects feature effectiveness. If the value of the
VS.AC.CongCtl.Time counter is not zero, this feature has taken effect.
1.
Run the BSC6900 MML command MOD UCELLCONGACALGO (CME single

Control Parameters for Intelligent Access; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches). In this step, set CongACSwitch to
OFF.
----End
Example
//Activating Intelligent Access Class Control for cell1 where the access
class ranges from AC0 to AC9
ADD UCELLCONGACALGO: CellId=1, CongACSwitch=ON,
ACRstrctRange=AC0-1&AC1-1&AC2-1&AC3-1&AC4-1&AC5-1&AC6-1&AC7-1&AC8-1&AC9-1
;
//Deactivating Intelligent Access Class Control for cell1
MOD UCELLCONGACALGO: CellId=1, CongACSwitch=OFF;
Issue 06 (2013-03-25)

872
RAN14.0
263 Configuring Dynamic Configuration of HSDPA CQI

Feedback Period
263
Configuring Dynamic Configuration

Dynamic Configuration of HSDPA CQI Feedback Period.
Prerequisites
l
To implement dynamic configuration of CQI feedback period based on the uplink load,
the NodeB needs to reports actual service load. The reported value has the following
requirements for the NodeB configuration:
The BTS3812E, BTS3812A and BTS3812AE do not support this feature.
20 W, this feature is not supported. In other configurations, this feature is supported.
To implement dynamic configuration of CQI feedback period based on CS+PS services
or based on limited coverage, the NodeB does not require any dependency.

feature depends on feature WRFD-010610 HSDPA Introduction Package.
This feature is not supported when WRFD-021350 Independent Demodulation of
Signals from Multiple RRUs in One Cell is enabled.
License
Dependencies on Others
This feature needs UE to suport HSDPA.
Context
This feature considers the uplink load as the criterion for dynamically adjusting the channel
quality indicator (CQI) feedback period for HSDPA UEs. The goal is to ensure high downlink
rates when only a small number of HSDPA UEs are online and to increase the uplink capacity
Issue 06 (2013-03-25)

873
RAN14.0

Feedback Period
when a large number of HSDPA UEs are online. For HSUPA UEs at cell edges or UEs engaged
in CS/PS combined services, a longer CQI feedback period reduces the call drop rate and
improves user experience.
l
Precautions
None
Issue 06 (2013-03-25)
Data Preparation
Parameter Name
Parameter ID
Setting
Description
Source
Function Switch1
FuncSwitch1
The
DYN_CQI_ADJU
ST should be
selected.
Network Plan
Power Control
Switch
PcSwitch
The
PC_CQI_CYCLE
_BASE_CELLLO
AD_SWITCH,
PC_CQI_CYCLE
_BASE_COVER
AGE_SWITCH
and
PC_CQI_CYCLE
_BASE_CS_PLU
S_PS_SWITCH
should be selected.
Network Plan
CORRM
Algorithm
Reserved Switch 0
ReservedSwitch0
The
RESERVED_SWI
TCH_0_BIT5 or
RESERVED_SWI
TCH_0_BIT7
should be selected.
Network Plan
Load-based CQI
Feedback Period
CQIFBckBaseCellLoad
Use the
recommended
value.
Network Plan
Coverage-based
CQI Feedback
Period
CQIFBckBaseCoverage
Use the
recommended
value.
Network Plan
Combined-ServiceSpecific CQI
Feedback Period
CQIFBckBaseCsCombServ
Use the
recommended
value.
Network Plan
UL Actual Load
Trigger Threshold
UlActualloadTrigLdrThd
Use the
recommended
value.
Network Plan

874
RAN14.0

Feedback Period
Procedure
l
1.

UMTS Cell Parameters in Batches) or MOD UCELLLICENSE (CME single
UMTS Cell Parameters in Batches). In this step, select DYN_CQI_ADJUST under
Function Switch1 to enable the license of dynamic configuration of HSDPA CQI
feedback period for a specified cell.
2.

Parameters in Batches), with the following parameter settings:
To enable the load-based algorithm for periodically selecting the CQI feedback
period, select PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH under the
Power Control Switch parameter.
To enable the coverage-based algorithm for periodically selecting the CQI
feedback period, select PC_CQI_CYCLE_BASE_COVERAGE_SWITCH
under the Power Control Switch parameter.
To enable the algorithm based on CS/PS combined services for periodically
selecting the CQI feedback period, select
PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH under the Power Control
Switch parameter.
3.
When enabling the coverage-based algorithm for periodically selecting the CQI
feedback period, you need to run the BSC6900 MML command SET
Modifying RNC Parameters in Batches), with RESERVED_SWITCH_0_BIT5
or RESERVED_SWITCH_0_BIT7 selected under the CORRM Algorithm
Reserved Switch 0 parameter to enable the algorithm for shifting BE services from
HSUPA to R99 in the case of weak coverage or the coverage-based algorithm for BE
services on E-DCHs to fall back to DCHs.
NOTE
The coverage-based algorithm for periodically selecting the CQI feedback period depends on the
algorithm for shifting BE services from HSUPA to R99 in the case of weak coverage or the coveragebased algorithm for BE services on E-DCHs to fall back to DCHs. That is, enable at least one of the
two algorithms before enabling the coverage-based algorithm for periodically selecting the CQI
feedback period.
4.
Issue 06 (2013-03-25)
Optional: Run the BSC6900 MML command SET UHSDPCCH (CME single
configuration: UMTS Radio Global Configuration Express > HS-DPCCH Power
Control Configuration > RNC-Oriented HS-DPCCH Power Control Algorithm
Batches) (RNC level), ADD UCELLHSDPCCH (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell-Oriented HS-DPCCH
Power Control Algorithm Parameters; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) (cell level), or MOD
UCELLHSDPCCH (CME single configuration: UMTS Cell Configuration
875
RAN14.0

Feedback Period
Express > Cell Parameters > Cell-Oriented HS-DPCCH Power Control

Cell Parameters in Batches) (cell level), with the Load-based CQI Feedback
Period parameter set to the load-based CQI feedback period, the Coverage-based
CQI Feedback Period parameter set to the coverage-based CQI feedback period and
Combined-Service-Specific CQI Feedback Period set to the CQI feedback period
for CS/PS combined services.
NOTE
Set the preceding cell-level parameters separately based on the network plan only when the celllevel parameter values to be used are different from the RNC-level parameter values.
5.
Run the BSC6900 MML commandADD UCELLLDM (CME single configuration:

Cell Parameters in Batches) to set the value of UL Actual Load Trigger
Threshold.
Check the value of the counter VS.HSDPA.DynCfgAtt.LongCQI, which indicates the
number of attempts to set a long CQI feedback period in the cell. If the value of this counter
is not 0, this feature has been activated.
1.
Run the BSC6900 MML command MOD UCELLLICENSE (CME single

UMTS Cell Parameters in Batches). In this step, clear DYN_CQI_ADJUST under
Function Switch1 to disable the license of dynamic configuration of HSDPA CQI
feedback period for a specified cell.
2.

Parameters in Batches), with the following parameter settings:
To disable the load-based algorithm for periodically selecting the CQI feedback
period, clear PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH under the
Power Control Switch parameter.
To disable the coverage-based algorithm for periodically selecting the CQI
feedback period, clear PC_CQI_CYCLE_BASE_COVERAGE_SWITCH
under the Power Control Switch parameter.
To disable the algorithm based on CS/PS combined services for periodically
selecting the CQI feedback period, clear
PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH under the Power Control
Switch parameter.
----End
Example
//Activating Dynamic Configuration of HSDPA CQI Feedback Period
ADD UCELLLICENSE: CellId=1, FuncSwitch1=DYN_CQI_ADJUST-1;
PcSwitch=PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH-1&PC_CQI_CYCLE_BASE_COVERAGE_S
WITCH-1&PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH-1;
Issue 06 (2013-03-25)

876
RAN14.0

Feedback Period
SET UCORRMALGOSWITCH: ReservedSwitch0=RESERVED_SWITCH_0_BIT7-1;

SET UHSDPCCH: CQIFBckBaseCellLoad=D8, CQIFBckBaseCoverage=D8,
CQIFBckBaseCsCombServ=D20;
ADD UCELLLDM: UlActualloadTrigLdrThd=50;
//Deactivating Dynamic Configuration of HSDPA CQI Feedback Period
MOD UCELLLICENSE: CellId=1, FuncSwitch1=DYN_CQI_ADJUST-0;
PcSwitch=PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH-0&PC_CQI_CYCLE_BASE_COVERAGE_S
WITCH-0&PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH-0;
Issue 06 (2013-03-25)

877
RAN14.0
264 Configuring Load-based Uplink Target BLER

Configuration
264
Configuring Load-based Uplink

Target BLER Configuration
Load-based Uplink Target BLER Configuration.
Prerequisites
l
This features requires the NodeB to report the value of the uplink actual service load.
The reported value has the following requirements for the NodeB configuration:
The BTS3812E, BTS3812A and BTS3812AE do not support this feature.
20W, this feature is not supported. In other configurations, this feature is supported.

This feature is not supported when WRFD-021350 Independent Demodulation of
Signals from Multiple RRUs in One Cell is enabled.
License
Context
This feature is designed for UEs whose services carried by DCHs are all BE services. When the
uplink load on the cell causes congestion, this feature configures a large target BLER. This
mechanism lowers the uplink load on the cell, increases the cell capacity, and reduces the
possibility of call drops for cell edge users (CEUs).
l
Precautions
None
Issue 06 (2013-03-25)
Data Preparation

878
RAN14.0

Configuration
Parameter Name
Parameter ID
Setting
Description
Source
Function Switch1
FuncSwitch1
The
DYN_BLER_PS
should be selected.
Network Plan
Power Control
Switch
PcSwitch
The
PC_BLER_TAR
GET_BASE_CEL
LLOAD_SWITC
H should be
selected.
Network Plan
Uplink Target
BLER for Heavily
Loaded Cells
BlerTargetBaseCellLoad
Use the
recommended
value.
Network Plan
UL Actual Load
Trigger Threshold
UlActualloadTrigLdrThd
Use the
recommended
value.
Network Plan
Procedure
l
Issue 06 (2013-03-25)
1.

UMTS Cell Parameters in Batches). In this step, select DYN_BLER_PS under
Function Switch1,to enable the license of load-based uplink target BLER
configuration for a specified cell.
2.

Parameters in Batches), with
PC_BLER_TARGET_BASE_CELLLOAD_SWITCH under Power Control
Switch selected. This operation enables the load-based algorithm for selecting the
target BLER.
3.
Optional: Run the BSC6900 MML command SET UOLPC (CME single
configuration: UMTS radio global Configuration Express > RNC-Oriented
OLPC Algorithm Parameters Configuration > RNC-Oriented OLPC Algorithm
Batches), with Uplink Target BLER for Heavily Loaded Cells set to a large value.
4.
Optional: Run the BSC6900 MML commandADD UCELLLDM (CME single


879
RAN14.0

Configuration
Modifying UMTS Cell Parameters in Batches) to set the value of UL Actual Load
Trigger Threshold.
5.
Optional: To maximize the gain of the feature Load-based Uplink Target BLER
Configuration, it is recommended that you activate the optimized outer loop power
control. For details, see "Activating optimized outer loop power control" in 22
Configuring Outer Loop Power Control.
Check the value of the counter VS.ULBler.BE.Large, which indicates the number of
attempts to set the target BLER when the uplink load on the cell causes congestion. If the
value of this counter is not 0, this feature has been activated.
1.

UMTS Cell Parameters in Batches). In this step, clear DYN_BLER_PS(Loadbased Uplink Target BLER Configuration) under Function Switch1, to disable the
license of dynamic configuration of load-based uplink target BLER configuration for
a specified cell.
2.

Parameters in Batches), with
PC_BLER_TARGET_BASE_CELLLOAD_SWITCH under Power Control
Switch cleared. This operation disables the load-based algorithm for selecting the
target BLER.
----End
Example
//Activate the feature Load-based Uplink Target BLER Configuration
ADD UCELLLICENSE: CellId=1, FuncSwitch1=DYN_BLER_PS-1;
SET UCORRMALGOSWITCH: PcSwitch=PC_BLER_TARGET_BASE_CELLLOAD_SWITCH-1;
ADD UCELLLDM: UlActualloadTrigLdrThd=50;
SET UOLPC: BlerTargetBaseCellLoad=-10;
//Deactivate the feature Load-based Uplink Target BLER Configuration
MOD UCELLLICENSE: CellId=1, FuncSwitch1=DYN_BLER_PS-0;
SET UCORRMALGOSWITCH: PcSwitch=PC_BLER_TARGET_BASE_CELLLOAD_SWITCH-0;
Issue 06 (2013-03-25)

880
RAN14.0
265 Configuring Inter-Frequency Load Balancing Based on

Configurable Load Threshold
265
Configuring Inter-Frequency Load

Threshold
Inter-Frequency Load Balancing Based on Configurable Load Threshold.
Prerequisites
l
This feature does not depend on Hardware.

This feature depends on the feature WRFD-020110 Multi Frequency Band Networking
Management in the inter-band networking scenario.
License
Context
This feature balances the load among inter-frequency cells by triggering measurement-based
inter-frequency handovers. With this feature, the RNC compares measurement results of uplink
and downlink power resource, code resource, and channel element (CE) resource in a cell with
load thresholds for the corresponding services. Based on the comparison result, the RNC selects
the UEs and target cell for an inter-frequency handover. This feature supports load balancing
between cells on the following frequencies.
l
Intra-band frequencies
Inter-band frequencies
Inter-RNC frequencies
Inter-vendor frequencies
Frequencies between the macro network and the micro network
Precautions
Issue 06 (2013-03-25)

881
RAN14.0

None
l
Issue 06 (2013-03-25)
Data Preparation
Parameter Name
Parameter ID
Setting
Description
Source
Function Switch1
FuncSwitch1
The
INTER_FREQ_L
OAD_BALANCE
_BASEON_CFG_
THD should be
selected.
Network Plan
Switch for Cell

Load Control
NBMLdcAlgoSwit
ch
The UL_UU_CLB,
DL_UU_CLB,
CELL_CODE_C
LB and
CELL_CREDIT_
CLB should be
selected.
Network Plan
NodeB LDC
algorithm switch
NodeBLdcAlgoSwitch
The
NODEB_CREDI
T_CLB_SWITCH
and
LCG_CREDIT_C
LB_SWITCH
should be selected.
Network Plan
Candidate Flag of
Cell for Inter-Freq
Ho by CLB
CLBFlag
Set this parameter

to TRUE.
Network Plan
Candidate Cell
Priority in InterFreq HO by CLB
CLBPrio
This parameter
should be set
according to the
network plan.
Network Plan
Range of Target
Cell Involved in
CLB
CellLoadBalanceRange
ONLY_TO_INTR
A_RNC,
ONLY_TO_INTE
R_RNC or
BOTH_TO_INTR
A_RNC_AND_IN
TER_RNC should
be selected.
Network Plan
Interval for InterFreq HO Decision

in CLB
ClbPeriodTimerLen
Use the
recommended
value.
Network Plan
SWH for Control

No. of Half-SF
Changed-SC Comp
UE
NCovCMUserNumCtrlSwitch
Use the
recommended
value.
Network Plan

882
RAN14.0

Parameter Name
Parameter ID
Setting
Description
Source
Threshold for No.

of Half-SF
Changed-SC Comp
UE
CellSFCMUserNumThd
Use the
recommended
value.
Network Plan
Procedure
l
Issue 06 (2013-03-25)
1.

UMTS Cell Parameters in Batches). In this step, under FuncSwitch1, select
INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD(Inter-Frequency
Load Balancing Based on Config Load Thd) to enable the license of CLB for a
specified cell.
2.
Run the BSC6900 MML commandADD UCELLALGOSWITCH (CME single

Parameters in Batches) or MOD UCELLALGOSWITCH (CME single
Parameters in Batches). In this step, under NBMLdcAlgoSwitch, select
UL_UU_CLB to enable uplink Uu-interface load balancing, select DL_UU_CLB to
enable downlink Uu-interface load balancing, select CELL_CODE_CLB to enable
cell code resource load balancing, and select CELL_CREDIT_CLB to enable cell
credit load balancing for a specified cell.
3.
Run the BSC6900 MML commandADD UNODEBALGOPARA (CME single

Modifying Logical NodeB Parameters in Batches) or MOD
UNODEBALGOPARA (CME single configuration: NodeB Configuration
Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm
Parameters; CME batch modification center: 3.16 Modifying Logical NodeB
Parameters in Batches). In this step, under NodeBLdcAlgoSwitch, select
NODEB_CREDIT_CLB_SWITCH(NodeB Credit CLB Algorithm) to enable
NodeB credit load balancing and select LCG_CREDIT_CLB_SWITCH(Local Cell
Group Credit CLB Algorithm) to enable local cell group credit load balancing for
a specified NodeB.
4.
Run the BSC6900 MML commandADD UINTERFREQNCELL (CME single

configuration: UMTS Cell Configuration Express > Neighboring Cell > Interfrequency Neighboring Cell; CME batch modification center: not supported) or
MOD UINTERFREQNCELL (CME single configuration: UMTS Cell
Configuration Express > Neighboring Cell > Inter-frequency Neighboring Cell;
CME batch modification center: not supported). In this step, set CLBFlag for the
883
RAN14.0

inter-frequency neighboring cell of a specified cell to TRUE, and set CLBPrio based
NOTE
The inter-frequency neighboring cell of intra-RNC whose CLBFlag is TRUE can be the target
cell of an inter-frequency handover using CLB only after step 1 is performed.
Issue 06 (2013-03-25)
5.
Run the BSC6900 MML command ADD UCELLCLB (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell-Oriented
Parameters for CLB interfreq Load Banlance Algorithm; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) or MOD
UCELLCLB (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell-Oriented Parameters for CLB interfreq Load Banlance
Algorithm; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches). In this step, set the feature parameters for a specified cell.
Based on the site requirements, set CellLoadBalanceRange to
ONLY_TO_INTRA_RNC, ONLY_TO_INTER_RNC, or
BOTH_TO_INTRA_RNC_AND_INTER_RNC to enable intra-RNC interfrequency load balancing, inter-RNC inter-frequency load balancing, or intra- and
inter-RNC inter-frequency load balancing, respectively. Keep the default settings of
other parameters, which are the thresholds for inter-frequency load balancing because
of code resource, cell credit resource, and MaxUserNumforCLBIFHO.
6.
Optional: If CellLoadBalanceRange in step 5 is set to ONLY_TO_INTER_RNC

or BOTH_TO_INTRA_RNC_AND_INTER_RNC, Run the BSC6900 MML
commandSET UCLB (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC
Parameters for CLB interfreq Load Banlance Algorithm; CME batch
parameters related to the cell load status of the neighboring RNC.
7.
Optional: Run the BSC6900 MML commandSET ULDCPERIOD (CME single

configuration: UMTS Radio Global Configuration Express > Load Control
Parameter Configuration > RNC Oriented LDC Algorithm Cycle Length; CME
step, set ClbPeriodTimerLen.
8.
Optional: If NODEB_CREDIT_CLB_SWITCH(NodeB Credit CLB

Algorithm) or LCG_CREDIT_CLB_SWITCH(Local Cell Group Credit CLB
Algorithm)is selected under NodeBLdcAlgoSwitch in step 3, Run the BSC6900
MML commandADD UNODEBCLB (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeBOriented Parameters for CLB interfreq Load Banlance Algorithm; CME batch
modification center: 3.16 Modifying Logical NodeB Parameters in Batches) or
MOD UNODEBCLB (CME single configuration: NodeB Configuration Express
> IUB_RNC > NodeB Basic Information > NodeB-Oriented Parameters for CLB
interfreq Load Banlance Algorithm; CME batch modification center: 3.16
Modifying Logical NodeB Parameters in Batches). In this step, set the feature
parameters for a specified NodeB. Keep the default parameter settings, which are the
thresholds for inter-frequency load balancing because of cell group credit resource
and NodeB credit resource.
9.
Optional: If UL_UU_CLB or DL_UU_CLB is selected under

NBMLdcAlgoSwitch in step 2, Run the BSC6900 MML commandADD
UCELLLDM (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) or MOD
884
RAN14.0

UCELLLDM (CME single configuration: UMTS Cell Configuration Express >

Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches). In this
step, set the threshold for inter-frequency load balancing because of power resource
for a specified cell. Keep the default parameter settings.
10. Optional: Run the BSC6900 MML commandSET UCMCF (CME single
configuration: UMTS Radio Global Configuration Express > Compression Mode
Parameter Configuration > RNC Oriented CMCF Algorithm Parameters; CME
step, set NCovCMUserNumCtrlSwitch and CellSFCMUserNumThd.
11. Optional: Run the BSC6900 MML commandADD UCELLMCLDR (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > CellOriented Based Measurement Inter-frequency LDR Handover Algorithm
Parameters in Batches) or MOD UCELLMCLDR (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell-Oriented Based
Measurement Inter-frequency LDR Handover Algorithm Parameters; CME
this step, set UESpdOptSwitch.
l
Check the value of the counter VS.LCC.CLB.CS.InterFreq or VS.LCC.CLB.PS.InterFreq
on the M2000. If the value is not 0, this feature has been activated successfully.
1.

UMTS Cell Parameters in Batches). In this step, clear
INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD under FuncSwitch1
to disable the license of the feature for a specified cell.
2.

Parameters in Batches). In this step, under NBMLdcAlgoSwitch, clear
UL_UU_CLB to disable uplink Uu-interface load balancing, clear DL_UU_CLB to
disable downlink Uu-interface load balancing, clear CELL_CODE_CLB to disable
cell code resource load balancing, and clear CELL_CREDIT_CLB to disable cell
credit load balancing for a specified cell.
3.

Modifying Logical NodeB Parameters in Batches). In this step, under
NodeBLdcAlgoSwitch, clear NODEB_CREDIT_CLB_SWITCH to disable
NodeB credit load balancing and clear LCG_CREDIT_CLB_SWITCH to disable
local cell group credit load balancing for a specified NodeB.
----End
Example
/*Activating the feature WRFD-140217 Inter-Frequency Load Balancing Based on
Configurable Load Threshold*/
Issue 06 (2013-03-25)

885
RAN14.0

//Enabling the license of CLB for a specified cell

ADD UCELLLICENSE: CellId=1,
FuncSwitch1=INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD-1; or
MOD UCELLLICENSE: CellId=1,
FuncSwitch1=INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD-1;
//Enabling uplink Uu-interface load balancing, downlink Uu-interface load
balancing, cell code resource load balancing, and cell credit load
balancing for a specified cell
ADD UCELLALGOSWITCH: CellId=1,
NBMLdcAlgoSwitch=UL_UU_CLB-1&DL_UU_CLB_1&CELL_CODE_CLB-1&CELL_CREDIT_CLB1, NBMUlCacAlgoSelSwitch=ALGORITHM_OFF,
NBMDlCacAlgoSelSwitch=ALGORITHM_OFF; or
NBMLdcAlgoSwitch=UL_UU_CLB-1&DL_UU_CLB_1&CELL_CODE_CLB-1&CELL_CREDIT_CLB1;
NOTE
NBMUlCacAlgoSelSwitch and NBMDlCacAlgoSelSwitch in the ADD UCELLALGOSWITCH

command are the mandatory parameters,their values are based on site configurations. Take it as
example ,they are set to ALGORITHM_OFF.
//Enabling NodeB credit load balancing and local cell group credit load
balancing for a specified NodeB
ADD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=1,
NodeBLdcAlgoSwitch=NODEB_CREDIT_CLB_SWITCH-1&LCG_CREDIT_CLB_SWITCH-1; or
NodeBLdcAlgoSwitch=NODEB_CREDIT_CLB_SWITCH-1&LCG_CREDIT_CLB_SWITCH-1;
//Setting the CLB priority for the inter-frequency neighboring cell of a
specified cell
CLBFlag=TRUE, CLBPrio=1; or
MOD UINTERFREQNCELL: RNCId=0, CellId=1, NCellRncId=1, NCellId=2,
CLBFlag=TRUE, CLBPrio=1;
//Setting the CLB parameters for a specified cell
ADD UCELLCLB: CellId=1,
CellLoadBalanceRange=BOTH_TO_INTRA_RNC_AND_INTER_RNC; or
MOD UCELLCLB: CellId=1,
CellLoadBalanceRange=BOTH_TO_INTRA_RNC_AND_INTER_RNC;
/*Deactivating the feature WRFD-140217 Inter-Frequency Load Balancing Based on

Configurable Load Threshold*/
//Disabling the license of CLB for a specified cell
MOD UCELLLICENSE: CellId=1,
FuncSwitch1=INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD-0;
//Disabling uplink Uu-interface load balancing, downlink Uu-interface
load balancing, cell code resource load balancing, and cell credit load
balancing for a specified cell
NBMLdcAlgoSwitch=UL_UU_CLB-0&DL_UU_CLB_0&CELL_CODE_CLB-0&CELL_CREDIT_CLB0;
//Disabling NodeB credit load balancing and local cell group credit load
balancing for a specified NodeB
NodeBLdcAlgoSwitch=NODEB_CREDIT_CLB_SWITCH-0&LCG_CREDIT_CLB_SWITCH-0;
Issue 06 (2013-03-25)

886
RAN14.0
266 Configuring Load Based GSM and UMTS Handover

Enhancement Based on Iur-g
266
Configuring Load Based GSM and
UMTS Handover Enhancement Based on Iur-g

Load Based GSM and UMTS Handover Enhancement Based on Iur-g.
Prerequisites
l
The BSC model is the BSC6900.
A GSM+UMTS dual-mode MS is required.
Interface board FG2a/FG2c/GOUa/GOUc should be configured to support Iur-g.

feature depends on features GBFD-511101 Load Based Handover Enhancement on Iurg, WRFD-020306 Inter-RAT Handover Based on Load or WRFD-021200 HCS
(Hierarchical Cell Structure).
License
Others
Both the 2G network and the 3G network are deployed.
IP transmission mode is used on the Iur-g interface.
A GSM cell and a UMTS cell are configured and the GSM cell is configured as the
neighboring cell of the UMTS cell.
Data is negotiated and planned for the inter-BSC6900 Iur-g interface. For details you
can refer to Configuring the inter-BSC6900 Iur-g interface.
NOTE
l The licenses on the BSC and the RNC sides are activated separately.
Context
This feature is based on Huawei private information exchange mechanism over the Iur-g
interface. With this feature, the traffic is distributed through the RRC redirection and load-based
Issue 06 (2013-03-25)

887
RAN14.0

handover from the 3G network to the 2G network on the basis of the service attributes and the
load of the 2G networks when 3G cell enters LDR status. In this manner, the load is shared by
the GSM network when the load of UMTS network is heavy.
Procedure
l
1.

a.
Run the BSC6900 MML command SET UMBSCCRRM (CME single

Configuration > MBSC Comm-RRM Algorithm Parameters; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches) to enable
the non-coverage-based handover. In this step, set Non-Coverage Handover
Based on 2G Load Indication to ON(ON), Adjustment Coefficient of 2G
Load Value to 1 and Load-base Handover Based on 3G2G Load Difference
Indication to ON(ON).
b.

Parameters in Batches) to enable the inter-RAT handover. In this step, select
HO_INTER_RAT_CS_OUT_SWITCH and
HO_INTER_RAT_PS_OUT_SWITCH in the HandOver switch drop-down
list box.
c.

UMTS Cell Parameters in Batches) to enable UL and DL load reshuffling
(LDR) on the Uu interface. In this step, select UL_UU_LDR(Uplink UU LDR
Algorithm) and DL_UU_LDR(Downlink UU LDR Algorithm) in the Switch
for Cell Load Control drop-down list box.
d.

UMTS Cell Parameters in Batches) to configure LDR actions. In this step, set
DL LDR first action and UL LDR first action to CSInterRatShouldBeLDHO
(CS domain inter-rat should be load handover); set DL LDR second action
and UL LDR second action to PSInterRatShouldBeLDHO(PS domain interrat should be load handover); set DL LDR third action and UL LDR third
action to CSInterRatShouldNotLDHO(CS domain inter-rat should not be
load handover); set DL LDR fourth action and UL LDR fourth action to
PSInterRatShouldNotLDHO(PS domain inter-rat should not be load
handover).
NOTE
You need to configure UL and DL LDR actions according to the actual situation.
2.
Configuration on the BSC side

a.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET GCELLHOINTERRATLDB (CME

single configuration: Cell Configuration Express > Handover Data > InterRAT Handover Parameters; CME batch modification center: Modifying GSM
Cell Parameters in Batches) to activate MBSC Handover based on Load
888
RAN14.0

Enhancement on the GSM side. In this step, set Allow Inter-RAT Load HO in
Connect State to YES(Yes).
b.
Run the BSC6900 MML command SET GCELLHOBASIC (CME single

configuration: Cell Configuration Express > Handover Data > Basic
Handover Parameters of Cell; CME batch modification center: Modifying
GSM Cell Parameters in Batches) to enable inter-RAT handovers. In this step,
set Inter-RAT Out BSC Handover Enable and Inter-RAT In BSC Handover
Enable to YES(Yes) .
c.

Cell Parameters in Batches) to set 2G Load Adjustment Coefficient. Setting 2G
Load Adjustment Coefficient to 10 is recommended.
NOTE
l If the verification achieves the following results as expected, the configuration succeeds. Otherwise,
the configuration fails.
1.
3G-to-2G Load Based Handover Enhancement
CAUTION
The verification can be done when only the UMTS cell is in the basic congestion state.
a.
Use the dual-mode MS to call a fixed telephone in the UMTS cell. Trace signaling
on the Iu interface on the LMT. RANAP_RELOCATION_REQUIRED
message is reported. The RANAP_RELOCATION_REQUIRED message
contains reduce-load-in-serving-cell. Trace signaling on the A interface on the
LMT. Handover Request message is reported. The Handover Request
message contains reduce-load-in-serving-cell.
NOTE
After the verification, set the value of system to the value before the verification.
2.
2G-to-3G Load Based Handover Enhancement

a.
Use the MS to initiate a call in the GSM cell, and the call is successfully
established.
b.
When the GSM cell is in the basic congestion state, the MS hand over to 3G
neighbor cell. Trace signaling on the A interface. Check that Assignment
Request, Handover Required, and Handover Command messages are
reported and cause in the Handover Required message is reduce-load-inserving-cell.
1.

MBSC Handover based on Load Enhancement on the UMTS side. In this step, set
Issue 06 (2013-03-25)

889
RAN14.0

Non-coverage handover based on 2G load Indication to OFF(OFF) and Loadbase handover based on 3G2G load difference Indication to OFF(OFF).
2.

For the deactivation procedure on the BSC side you can refer to GBFD-511101
Configuring Load Based Handover Enhancement on Iur-g.
----End
Example
//Activating Handover based on Load Enhancement
//Configuration on the RNC side
/*Enabling the non-coverage-based handover*/
SET UMBSCCRRM: MbscNcovHoOn2GldInd=ON, LoadHoOn3G2GldInd=ON;
/*Enabling the inter-RAT handover*/
HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1;
/*Enabling UL and DL load reshuffling (LDR) on the Uu interface*/
MOD UCELLALGOSWITCH: CellId=0, NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1;
/*Configuring LDR actions*/
MOD UCELLLDR: CellId=0, DlLdrFirstAction=CSInterRatShouldBeLDHO,
DlLdrSecondAction=PSInterRatShouldBeLDHO,
DlLdrThirdAction=CSInterRatShouldNotLDHO,
DlLdrFourthAction=PSInterRatShouldNotLDHO,
UlLdrFirstAction=CSInterRatShouldBeLDHO,
UlLdrSecondAction=PSInterRatShouldBeLDHO,
UlLdrThirdAction=CSInterRatShouldNotLDHO,
UlLdrFourthAction=PSInterRatShouldNotLDHO;
//Configuration on the BSC side
/*Enabling the Handover Enhancement Based on Iur-g*/
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=YES;
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATOUTBSCHOEN=YES,
INTERRATINBSCHOEN=YES;
/*Setting 2G Load Adjustment Coefficient*/
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, G2GLoadAdjustCoeff=10;
//Deactivating UMTS Handover based on Load Enhancement
SET UMBSCCRRM: MbscNcovHoOn2GldInd=OFF, LoadHoOn3G2GldInd=OFF;
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=NO;
Issue 06 (2013-03-25)

890
RAN14.0

Procedure Optimization Based on Iur-g
267
Configuring NACC(Network
Assisted Cell Change) Procedure Optimization

Based on Iur-g
NACC Procedure Optimization Based on Iur-g.
Prerequisites
l

feature depends on features WRFD-020303 Inter-RAT Handover Based on Coverage,
WRFD-020305 Inter-RAT Handover Based on Service, WRFD-020306 Inter-RAT
Handover Based on Load, GBFD-511102 NACC Procedure Optimization Based on Iurg between GSM and WCDMA, or WRFD-021200 HCS (Hierarchical Cell Structure).
License
Others
UEs must support NACC procedure.
IP transmission mode is used on the Iur-g interface.
The MS supports NACC.
Both the 2G network and the 3G network are deployed.
A GSM cell and a UMTS cell are configured and the GSM cell is configured as the
Issue 06 (2013-03-25)

891
RAN14.0

NOTE
l The licenses on the BSC and the RNC sides are activated separately.
Context
With this feature, the network assisted cell change (NACC) procedure is performed through the
internal information exchange mechanism of the MBSC. As a result, the interoperability of PS
services between GSM cells and UMTS cells under the same MBSC does not involve the CN.
In this manner, the time taken to perform the NACC procedure is shortened by about 680ms and
therefore the handover delay is reduced. In addition, the NACC procedure does not require the
support of the CN.
Procedure
l
1.
2.

a.

Parameters in Batches) to enable the NACC function. In this step, select
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH in the
HandOver switch drop-down list box.
b.

direct GERAN system information exchange. In this step, set GERAN System
Information Exchange Switch to ON.
c.

HO_INTER_RAT_PS_OUT_SWITCH in the HandOver switch drop-down
list box.
d.

configuration: Object Group > UMTS Service Configuration and
Maintenance Management > External Cell Configuration > RNC 2G
External Cell; CME batch modification center: 3.19 Modifying RNC External
Cell Parameters in Batches) to enable the inter-RAT cell to support indication
of the RIM procedure. In this step, set Inter-RAT cell support RIM
indicator to TRUE. If multiple neighboring cells are planned, repeat this step
to enable the inter-RAT cell to support indication of the RIM for all the
neighboring cells.

For the configuration on the BSC side you can refer to GBFD-511102 Configuring
NACC(Network Assisted Cell Change) Procedure Optimization Based on Iur-g
between GSM and WCDMA.
Issue 06 (2013-03-25)

892
RAN14.0

1.
Trace Iur-g and Um interfaces on the LMT.
2.
Use a dual-mode MS to download data in the UMTS cell and then switch the MS to
the GSM cell.
3.
Check that INFO_EXCHG_INIT_REQ and INFO_EXCHG_INIT_RSP

messages are reported on the Iur-g interface. The value of informationTypeItem in
the INFO_EXCHG_INIT_REQ message is nACC-Related-Data(8) and the
INFO_EXCHG_INIT_RSP message contains nACC-Related-Data.
1.

a.

Parameters in Batches) on the RNC to deactivate NACC Procedure
Optimization. In this step, deselect
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH in the
HandOver switch drop-down list box.
----End
Example
//Activating NACC Procedure Optimization
/*Enabling the NACC function*/
HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-1;
/*Enabling direct GERAN system information exchange*/
SET UMBSCCRRM: MbscReqGeranInfoSwitch=ON;
/*Enabling the inter-RAT cell to support indication of the RIM
procedure*/
MOD UEXT2GCELL: GSMCellIndex=0, SuppRIMFlag=TRUE;
/*Allowing NACC-related information exchange on the Iur-g interface*/
MOD GNRNC: RNCINDEX=0, SPTINFOEXCHG=YES, INFOEXCHGLIST=NACCRELATED-1;
/*Setting basic GPRS attributes of the GSM cell*/
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NACCSPT=YES;
//Deactivating NACC Procedure Optimization
HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-0;
Issue 06 (2013-03-25)

893
RAN14.0
268 Configuring GSM and UMTS Load Balancing Based on

Iur-g
268
Configuring GSM and UMTS Load

Balancing Based on Iur-g
GSM and UMTS Load Balancing Based on Iur-g.
Prerequisites
l

feature depends on features GBFD-511103 GSM and UMTS Load Balancing Based on
Iur-g, WRFD-020400 DRD Introduction Package and WRFD-020305 Inter-RAT
Handover Based on Service.
License
Others
2G and 3G networks cover the same area.
IP transmission mode is used over the Iur-g interface.
A GSM cell and a UMTS cell are configured, and the GSM cell is configured as a
NOTE
l The licenses on the BSC and RNC sides are activated separately.
Context
This feature implements RRC redirection and the load-based GSM/UMTS handover through
the exchange of Huawei proprietary IE over the Iur-g interface. The Iur-g protocol stack complies
Issue 06 (2013-03-25)

894
RAN14.0

Iur-g
with the 3GPP specifications. With this feature, the traffic is distributed on the basis of the service
handover indicator and the load of the GSM network and UMTS network during RRC connection
setup or after RAB setup. In this way, a load balance is achieved between the GSM network and
UMTS network.
Procedure
l
1.
2.

a.

load balancing and set load difference thresholds. In this step, set Service
Distribution and Load Balancing Switch to LOAD-BASED(LOADBASED), Load Difference Threshold Between 3G And 2G of CS Service to
10, PS Load Difference Threshold Between 3G And 2G of Ps Service to 30,
and Adjustment Coefficient of 2G Load Value to 1.
b.

Parameters in Batches) to enable inter-RAT handover. In this step, select the
HO_INTER_RAT_PS_OUT_SWITCH check boxes under the parameter
HandOver switch.

a.

Cell Parameters in Batches) to turn on the load balancing switch and set the load
adjustment coefficient. In this step, set Allow Inter-RAT Load HO in Access
State to Load-based(Load-based), and set 2G Load Adjustment
Coefficient to 10.
b.
Run the BSC6900 MML command SET OTHSOFTPARA (CME single

configuration: GSM Global Configuration Express > Software Parameter
Configuration > Other Software Parameters of BSC; CME batch
modification center: Modifying GBSC Parameters in Batches). In this step, set
CS 2G 3G Load Balance Delta Threshold to 110.
NOTE
If the verification achieves the following results as expected, the configuration succeeds. Otherwise, the
configuration fails.
1.
3G-to-2G Load Balancing
CAUTION
Issue 06 (2013-03-25)

895
RAN14.0

Iur-g
a.
The verification procedure consists of the RRC setup phase and the RAB
connection phase. The verification in the latter phase involves CS speech services
and PS data services.
a.
Verifying that CS speech services in UMTS cell1 are handed over to GSM
cell2 at the RRC setup phase
1)
b.
c.
Issue 06 (2013-03-25)
Use the dual-mode MS to call a fixed telephone in cell1. The call is

successfully established. Initiate Uu-interface signaling tracing on the
LMT. The RRC_RRC_CONNECT_REQ and
RRC_RRC_CONN_REJECT messages are reported, and the
RRC_RRC_CONN_REJECT message contains GSMTargetCellInfo. That is, information about cell2 is contained,
indicating that the MS accesses cell2.
Verifying that PS data services in UMTS cell1 are handed over to GPRS
cell3 at the RAB connection phase
1)
Use the MS to browse the Internet.
2)
Initiate Uu-interface message tracing on the LMT. You can find that
the messages RRC_RB_SETUP, RRC_RB_SETUP_CMP,
RRC_MEAS_CTRL, and
RRC_CELL_CHANGE_ORDER_FROM_UTRAN are reported, and
that the value of InterRATEvent in the RRC_MEAS_CTRL message
is event3c.
3)
Initiate Iu-interface signaling tracing on the LMT. You can find that
the RANAP_SRNS_CONTEXT_REQ message is sent from the CN
to the RNC and then the RANAP_SRNS_CONTEXT_RESP message
is sent from the RNC to the CN.
4)
the RANAP_SRNS_DATA_FORWARD_COMMAND and
RANAP_IU_RELEASE_COMMAND messages are sent from the
CN to the RNC and then the RANAP_IU_RELEASE_COMPLETE
message is sent from the RNC to the CN.
5)
When the MS attempts to reselect cell3, Internet browsing is slightly

affected. After the MS reselects cell3, Internet browsing returns to
normal.
Verifying that CS speech services in UMTS cell1 are handed over to GSM
cell2 at the RAB connection phase
1)
Use the dual-mode MS to call a fixed telephone in cell1. The call is

successfully established.
2)
Initiate Uu-interface tracing on the LMT. You can find that the
messages RRC_RB_SETUP, RRC_RB_SETUP_CMP,
RRC_MEAS_CTRL, and RRC_HO_FROM_UTRAN_CMD_GSM
are reported, and that the value of InterRATEvent in the
RRC_MEAS_CTRL message is event3c.
3)
the RANAP_RELOCATION_REQUIRED message is sent from the
RNC to the CN and then the RANAP_RELOCATION_COMMAND
and RANAP_IU_RELEASE_COMMAND messages are sent from
the CN to the RNC.

896
RAN14.0

Iur-g
4)
2.
the RANAP_IU_RELEASE_COMPLETE message is sent from the
RNC to the CN.
2G-to-3G Load Balancing
CAUTION
The verification can be done when only the GSM cell is in the basic congestion state.
a.
Use the MS to initiate a call in the GSM cell. The directed retry procedure is
triggered so that the MS accesses the neighboring UMTS cell. The call is
successfully established. Initiate A-interface signaling tracing on the LMT. You
can find that the Assignment Request, Handover Required, and Handover
Command messages are reported and that the value of cause in the Handover
Required message is directed-retry(13).
1.

a.
2.

modification center: 3.15 Modifying RNC Parameters in Batches) to
deactivate MBSC load balancing. In this step, set Service Distribution and
Load Balancing Switch to OFF(OFF).

For the deactivation procedure on the BSC side you can refer to GBFD-511103
Configuring GSM and UMTS Load Balancing Based on Iur-g.
----End
Example
//Activating Load Balancing Based on Iur-g
/*Enabling load balancing and setting load difference thresholds*/
SET UMBSCCRRM: MbscServiceDiffLdbSwitch=LOAD-BASED,
Mbsc3G2GLdBlcCsDeltaThrd=10, Mbsc3G2GLdBlcPsDeltaThrd=30;
/*Enabling inter-RAT handover*/
/*Enabling load balancing*/
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=YES,
InterRatServiceLoadHoSwitch=Load-based, G2GLoadAdjustCoeff=10;
SET GCELLHOBASIC: IDTYPE=BYNAME, CELLNAME="0", INTERRATOUTBSCHOEN=YES,
INTERRATINBSCHOEN=YES;
/*Setting load difference thresholds*/
SET OTHSOFTPARA: G2G3GLdBlcDeltaThrd=110;
//Deactivating Load Balancing Based on Iur-g
SET UMBSCCRRM: MbscServiceDiffLdbSwitch=OFF;
Issue 06 (2013-03-25)

897
RAN14.0

Iur-g
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0,

InterRatServiceLoadHoSwitch=OFF;
Issue 06 (2013-03-25)

898
RAN14.0
269 Configuring GSM and UMTS Traffic Steering Based on

Iur-g
269
Configuring GSM and UMTS Traffic

Steering Based on Iur-g
GSM and UMTS Traffic Steering Based on Iur-g.
Prerequisites
l

feature depends on features GBFD-511104 GSM and WCDMA Traffic Steering Based
on Iur-g, WRFD-020400 DRD Introduction Package and WRFD-020305 Inter-RAT
Handover Based on Service.
License
Others
2G and 3G networks cover the same area.
IP transmission mode is used over the Iur-g interface.
A GSM cell and a UMTS cell are configured, and the GSM cell is configured as a
NOTE
l The licenses on the BSC and RNC sides are activated separately.
Context
This feature supports RRC redirection and GSM/UMTS inter-RAT handover based on service.
With this feature, services are steered on the basis of the service handover indicator, hierarchical
Issue 06 (2013-03-25)

899
RAN14.0

Iur-g
network planning, and the load of the GSM network and UMTS network when an MS accesses
the network. Service steering enables UEs requesting speech or low-speed PS services to access
the GSM network and those requesting high-speed PS services to access the UMTS network.
Procedure
l
1.
2.

a.

traffic steering. In this step, set Service Distribution and Load Balancing
Switch to SERVICE-BASED(SERVICE-BASED) and Adjustment
Coefficient of 2G Load Value to 1.
b.

Parameters in Batches) to enable inter-RAT handover. In this step, select the
HandOver switch.
c.
Run the BSC6900 MML command ADD UCELLHOCOMM (CME single

Oriented Handover Common Algorithm Parameters; CME batch
modification center: 3.18 Modifying UMTS Cell Parameters in Batches) to
enable inter-RAT CS handover. In this step, set Inter-RAT CS Handover
Switch to ON. Run the ADD UCELLHOCOMM (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Oriented
Handover Common Algorithm Parameters; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches) command to enable interRAT CS handover for each cell.

For the configuration on the BSC side you can refer to GBFD-511104 Configuring
GSM and WCDMA Traffic Steering Based on Iur-g.
1.
The verification procedure of 3G-to-2G Traffic Steering
CAUTION
a.
Issue 06 (2013-03-25)
Use the dual-mode MS to call a fixed telephone in the UMTS cell. Initiate Iuinterface tracing on the LMT. You can find that the
RANAP_RELOCATION_REQUIRED message is reported and the handover
cause value in the message is resource-optimisation-relocation. Initiate A
900
RAN14.0

Iur-g
interface tracing. You can find that the Handover Request message is reported
and the handover cause value in the message is traffic.
CAUTION
Ensure that the GSM cell is not in the congestion state.
2.
The verification procedure of 2G-to-3G Traffic Steering
CAUTION
The verification can be done when only the GSM cell is in the basic congestion state.
a.
Use the dual-mode MS to call a fixed telephone in the GSM cell. Initiate CS
Domain Messages of a Single Subscriber tracing on the LMT. You can find that
the call is in GSM cell, and don't hand over to UMTS cell.
1.

a.

modification center: 3.15 Modifying RNC Parameters in Batches) to
deactivate traffic steering. In this step, set Service Distribution and Load
Balancing Switch to OFF(OFF).
----End
Example
//Activating 3G-to-2G traffic steering
/*Enabling traffic steering*/
SET UMBSCCRRM: MbscServiceDiffLdbSwitch=SERVICE-BASED;
/*Enabling inter-RAT CS handover*/
ADD UCELLHOCOMM: CellId=1, CSServiceHOSwitch=ON;
/*Enabling inter-RAT incoming BSC handover*/
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0,
InterRatServiceLoadHoSwitch=Service-based;
//Deactivating 3G-to-2G traffic steering
SET UMBSCCRRM: MbscServiceDiffLdbSwitch=OFF;
Issue 06 (2013-03-25)

901
RAN14.0
270
Configuring Inter-RAT Handover

Based on Coverage
Inter-RAT Handover Based on Coverage.
Prerequisites
l

License
Other Prerequisites
Context
This feature supports measurement-based inter-RAT handover triggered by event 2D or uplink
UE QoS and urgent blind inter-RAT handover triggered by event 1F. This type of handover is
applicable to inter-RAT interworking based on coverage or caused by moving UEs.
Procedure
l
Issue 06 (2013-03-25)
1.

HO_INTER_RAT_PS_OUT_SWITCH from the HandOver Switch list.
2.
Run the BSC6900 MML command ADD U2GNCELL (CME single configuration:
UMTS Cell Configuration Express > Neighboring Cell > GSM Neighboring
902
RAN14.0
Cell; CME batch modification center: not supported) to add an inter-frequency

neighboring GSM cell.
3.
Run the BSC6900 MML command ADD UCELLINTERRATHOCOV (CME

Oriented Coverage Based Inter-rat Handover Measurement Algorithm
Parameters in Batches) (cell level) or SET UINTERRATHOCOV (CME single
Parameter Configuration > RNC Oriented Coverage based Inter-rat Handover
Modifying RNC Parameters in Batches) (RNC level) to configure parameters
related to coverage-based inter-RAT handover to GSM.
4.
Run the BSC6900 MML command MOD UTYPRABBASIC (CME single

Configuration > Basic Information for Typical Traffic Radio Access Bearer;
CME batch modification center: not supported). In this step, set Service Handover
Indicator to HO_TO_GSM_SHOULD_NOT_BE_PERFORM.
1.
Attenuate signals in the current cell that the UE accesses to trigger reporting of event
2D by the UE.
2.

Type, select RRC_MEAS_RPRT.
3.
Check whether event 2D shown in Figure 270-1 has been reported in the traced
messages.
Figure 270-1 Event 2D measurement report
Issue 06 (2013-03-25)
4.

Type, select RRC_MEAS_CTRL.
5.
Check in the traced messages whether the RNC has sent the UE an inter-RAT
measurement control message shown in Figure 270-2.

903
RAN14.0
NOTE
l To verify the measurement-based inter-RAT handover triggered by uplink QoS of UEs,

you need to Run the BSC6900 MML command SET UQOSACT to turn on the QoS
switches of different service types and attenuate the signals of the current cell. Check
whether UEs send the uplink QoS measurement reports to the RNC. The verification steps
are the same as those for event 2D.
l The inter-RAT blind handover triggered by event 1F is a special application. You need to
measure the pilot strength and quality scope of the best cell where the blind handover is to
be triggered. Generally, the inter-RAT blind handover is not needed and therefore does not
need to be verified.
1.

Parameters in Batches) to deactivate this feature.
2.
Run the BSC6900 MML command RMV UCELLINTERRATHOCOV (CME

Oriented Coverage Based Inter-rat Handover Measurement Algorithm
Parameters; CME batch modification center: not supported) (cell level) or SET
UINTERRATHOCOV (CME single configuration: UMTS Radio Global
Configuration Express > HandOver Parameter Configuration > RNC Oriented
Coverage based Inter-rat Handover Measurement Algorithm Parameters; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) (RNC
level) to remove or restore the parameters related to coverage-based inter-RAT
handover to GSM.
----End
Example
//Activating Inter-RAT Handover Based on Coverage
Issue 06 (2013-03-25)

904
RAN14.0
MOD UTYPRABBASIC: RabIndex=0, SHInd=HO_TO_GSM_SHOULD_NOT_BE_PERFORM;
//Deactivating Inter-RAT Handover Based on Coverage
Issue 06 (2013-03-25)

905
RAN14.0
271

Based on DL QoS
Inter-RAT Handover Based on DL QoS.
Prerequisites
l

License
Others
Context
When the load of voice and PS BE services is high in a cell and downlink QoS decreases, this
feature enables the UE to be handed over to an inter-RAT cell, guaranteeing QoS requirements.
Procedure
l
1.
Issue 06 (2013-03-25)

Parameters in Batches). In this step, set HandOver Switch to

906
RAN14.0

NOTE
Before activating this feature, perform Step 1 if HO_INTER_RAT_CS_OUT_SWITCH and

HO_INTER_RAT_PS_OUT_SWITCH are not turned on. You can run the BSC6900 MML
command LST UCORRMALGOSWITCH (CME single configuration: UMTS Radio
Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches) to check whether these switches have been turned
on.
2.
Cell; CME batch modification center: not supported) to add an inter-RAT neighboring
cell.
3.
Run the BSC6900 MML command SET UQOSHO (CME single configuration:
RNC Oriented QoS Handover Measurement Algorithm Parameters; CME batch
modification center: 3.15 Modifying RNC Parameters in Batches) to set
BSC6900-level parameters related to Inter-RAT Handover Based on DL QoS.
4.
modification center: 3.15 Modifying RNC Parameters in Batches) to turn on QoS
switches for different traffic classes.
1.
Log in to the BSC6900 LMT and start Uu Interface Trace.
2.
Ensure that the RNC sends to the NodeB an NBAP_DEDI_MEAS_INIT_REQ

message, which carries the event E parameter, as shown in Figure 271-1.
Figure 271-1 NBAP_DEDI_MEAS_INIT_REQ message
3.
Issue 06 (2013-03-25)
Ensure that the NodeB reports to the RNC an NBAP_DEDI_MEAS_RPRT message,

which carries the event E parameter.
907
RAN14.0
4.
Ensure that the RNC sends to the UE an RRC_MEAS_CTRL message and starts
inter-frequency measurement of the event or period type. Then, check that the
corresponding traced message indicates that the RNC has sent the inter-frequency
measurement control message to the UE.
1.

HO_INTER_RAT_CS_OUT_SWITCH and the
HO_INTER_RAT_PS_OUT_SWITCH under the HandOver Switch.
NOTE
Do not perform Step 1 if HO_INTER_RAT_CS_OUT_SWITCH and

HO_INTER_RAT_PS_OUT_SWITCH have been turned on before activating this feature.
2.
modification center: 3.15 Modifying RNC Parameters in Batches) to turn off QoS
switches for different traffic classes.
----End
Example
//Activating Inter-RAT Handover Based on DL QoS
SET UQOSACT: BEQosPerform=YES, AMRQosPerform=YES, VPQosPerform=YES,
BeDlAct1=InterRatHO, DlQosAmrInterRatHoSwitch=YES,
DlQosWAmrInterRatHoSwitch=YES;
//Deactivating Inter-RAT Handover Based on DL QoS
SET UQOSACT: BEQosPerform=NO, AMRQosPerform=NO, VPQosPerform=NO;
Issue 06 (2013-03-25)

908
RAN14.0
272 Configuring Video Telephony Fallback to Speech

(AMR) for Inter-RAT HO
272
Configuring Video Telephony
Fallback to Speech (AMR) for Inter-RAT HO

Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
Prerequisites
l

One or multiple of the following features must be configured before this feature is
activated:
WRFD-020303 Inter-RAT Handover Based on Coverage
License
Others
The UE needs to be compliant with 3GPP Release 6 to support the feature.
The MSC needs to be compliant with 3GPP Release 6 to support the feature.
Context
Before videophone services are handed over to the 2G system, this feature enables the fallback
of video telephony to speech to ensure continuous calls. However, due to the limitation of UE
and network support capability, the service may not be implemented. Therefore, Service Change
and UDI Fallback (SCUDIF) is introduced in 3GPP Release 6 to provide the mechanism to
provide the mechanism to fall back to speech without experiencing call drops in these scenarios.
Issue 06 (2013-03-25)

909
RAN14.0
272 Configuring Video Telephony Fallback to Speech

(AMR) for Inter-RAT HO
Procedure
l
The license controlling this feature has been activated. For details on how to activate the
license, see 4 Activating the UMTS License. For details about license items, see 2 Feature
Activation and License Item Descriptions.
1.
Start Iu Interface Trace and Uu Interface Trace on the BSC6900 LMT.
2.
After videophone services are established, check in the Uu Interface Trace dialog
box that the UE sends to the BSC6900 an RRC_MEAS_RPRT message, which
contains the 3A report.
3.
In the Iu Interface Trace dialog box, check that the BSC6900 sends an
RAB_MODIFY_REQ message to the CN. In the RAB_MODIFY_REQ message,
the value of the IE alternativeRABConfigurationRequest is alternative-RABconfiguration-Requested.
----End
Issue 06 (2013-03-25)

910
RAN14.0
273

Phase 2
Inter-RAT Handover Phase 2.
Prerequisites
l
BSC should support NACC RIM (RAN Information Management) and PS handover
procedure.

This feature is required only when one or several of the following inter-RAT handover
features are introduced:
WRFD-020303 Inter-RAT Handover Based on Coverage
License
Others
UE should support NACC and PS handover procedure.
GSM BSC should support NACC RIM (RAN Information Management) and PS
handover procedure.
SGSN supports NACC and PS handover procedure.
Context
This feature provides the inter-RAT relocation procedure for NACC and PS services to shorten
the interruption time of PS services caused by inter-RAT handover.
The inter-RAT Handover Enhanced Package includes the following features:
l
Issue 06 (2013-03-25)
WRFD-02030801 NACC (Network Assisted Cell Change)

911
RAN14.0
WRFD-02030802 PS Handover between UMTS and GPRS
For details about how to activate, verify, and deactivate this feature, see the following
sections:
Procedure

----End
Issue 06 (2013-03-25)

912
RAN14.0
274
Configuring NACC(Network
Assisted Cell Change)
WRFD-02030801 NACC(Network Assisted Cell Change).
Prerequisites
l

feature depends on the feature WRFD-020308 PS Inter-RAT Handover Phase 2.
License
Others
UE should support NACC procedure.
GSM BSC should support NACC RIM (RAN Information Management).
SGSN should support NACC procedure.
Context
This feature supports the standard NACC procedure defined in 3GPP specifications.
The NACC refers to Network Assisted Cell Change from UTRAN to GERAN, which is different
from the normal cell change order procedure, because the network provides GERAN (P) SI for
the UE.
Procedure
l
1.
Issue 06 (2013-03-25)

913
RAN14.0

Parameters in Batches) to open the following switches in the HandOver switch
parameter:
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH
NOTE
When PS_3G2G_RELOCATION_SWITCH is ON, this switch no longer takes effect.
2.

(for new neighboring cell) or MOD UEXT2GCELL (CME single configuration:
External Cell Configuration > RNC 2G External Cell; CME batch modification
center: 3.19 Modifying RNC External Cell Parameters in Batches) (for the existing
neighboring cell) to set Inter-RAT cell support RIM indicator to TRUE.
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the

settings of the PS inter-RAT handover, NACC, and Relocation switches.
2.
Run the BSC6900 MML command LST UEXT2GCELL to check whether the interRAT neighboring cell supports the RIM procedure.
NOTE
To implement this feature, the UE should support NACC. Therefore, the NACC-supportive UEs are
required for activation.
1.

Parameters in Batches) to set
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH in the HandOver
switch parameter to 0.
2.

to set Inter-RAT cell support RIM indicator to FALSE.
----End
Example
//Activating NACC(Network Assisted Cell Change)
HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-1&HO_INTER_RAT_PS_3G2G_
RELOCATION_SWITCH-0&HO_INTER_RAT_PS_OUT_SWITCH-1;
//Deactivating NACC(Network Assisted Cell Change)
MOD UEXT2GCELL: SuppRIMFlag=FALSE;
Issue 06 (2013-03-25)

914
RAN14.0
275
Configuring PS Handover between

UMTS and GPRS
WRFD-02030802 PS Handover between UMTS and GPRS.
Prerequisites
l

feature depends on the feature WRFD-020308 PS Inter-RAT Handover Phase 2.
License
Others
UE should support PS handover procedure.
GSM BSC should support PS handover procedure.
SGSN should support PS handover procedure.
Context
This feature enables the relocation of PS services (including non-real-time PS services and realtime PS services) between systems. In inter-system handover scenarios, this feature can greatly
improve user perception, especially for real-time PS services.
The PS handover is different from NACC or normal cell change function, with which the
relocation procedure between 3G and 2G is applied, just like the CS inter-system handover. With
this feature, the service interruption for PS service inter-system handover is reduced by a great
extent.
In this feature, both the handover from UTRAN to GERAN and the handover from GERAN to
UTRAN are supplied. If both the UE and the network support PS handover, handover between
UTRAN and GERAN would be performed. Otherwise, either NACC or normal cell change order
would be selected.
Issue 06 (2013-03-25)

915
RAN14.0
Procedure
l
1.

Parameters in Batches) to open the following switches in the HandOver switch
parameter:
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH
2.

to add a neighboring GSM cell to the UMTS coverage and to set the Inter-RAT cell
support PS HO indicator parameter to TRUE.
3.
Cell; CME batch modification center: not supported) to add a neighboring GSM cell
for the UMTS cell.
4.
Optional: Run the BSC6900 MML command SET UINTERRATHOCOV (CME

single configuration: UMTS Radio Global Configuration Express > HandOver
Parameter Configuration > RNC Oriented Coverage based Inter-rat Handover
Modifying RNC Parameters in Batches) to set inter-RAT handover measurement
related parameters.
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the

status of PS inter-RAT handover switch and the Relocation HO switch.
2.
Run the BSC6900 MML command LST UEXT2GCELL to ensure the inter-RAT
cell supports PS Handover.
3.
Run the BSC6900 MML command LST UINTERRATHOCOV to check inter-RAT

handover measurement related parameters.
1.

Parameters in Batches) to set
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH in the HandOver
switch parameter to 0.
2.

to set the SuppPSHOFlag parameter to FALSE.
----End
Issue 06 (2013-03-25)

916
RAN14.0
Example
//Activating PS Handover between UMTS and GPRS
HoSwitch=HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH-1&HO_INTER_RAT_PS_OUT_SWI
TCH-1;
ADD UEXT2GCELL: GSMCellIndex=1, GSMCellName="GSMCELL1", NBscIndex=1,
LdPrdRprtSwitch=ON, MCC="460", MNC="01", CnOpGrpIndex=1, LAC=1,
CfgRacInd=REQUIRE, RAC=1, CID=1, NCC=1, BCC=1, BcchArfcn=512,
RatCellType=GPRS, UseOfHcs=NOT_USED, SuppPSHOFlag=TRUE;
ADD U2GNCELL: RNCId=1, CellId=100, GSMCellIndex=1;
SET UINTERRATHOCOV: InterRatReportMode=PERIODICAL_REPORTING,
FilterCoefOf2D2F=D4, InterRATFilterCoef=D6;
//Deactivating PS Handover between UMTS and GPRS
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH-0;
MOD UEXT2GCELL: SuppPSHOFlag=FALSE;
Issue 06 (2013-03-25)

917
RAN14.0
276

Based on Service
Inter-RAT Handover Based on Service.
Prerequisites
l

License
Context
This feature provides a mechanism for performing handover between GSM/GPRS and UMTS
systems on the basis of services. This feature forwards appropriate services in a UMTS system
to a GSM/GPRS system, balancing load between the two systems. This feature also prevents
the handover from adversely affecting services based on service attributes.
Procedure
l
Issue 06 (2013-03-25)
1.

HO_INTER_RAT_PS_OUT_SWITCH from the HandOver Switch list.
2.

918
RAN14.0

to add a neighboring GSM cell.
3.
Cell; CME batch modification center: not supported) to set neighbor relation with the
neighboring GSM cell.
4.
Run the BSC6900 MML command ADD UCELLHOCOMM (CME single

Oriented Handover Common Algorithm Parameters; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set InterRAT CS handover switch or Inter-RAT PS handover switch to ON.
5.
Run the BSC6900 MML command ADD UCELLINTERRATHONCOV (CME

Oriented None-Coverage Based Inter-rat Handover Measurement Algorithm
Parameters in Batches) (cell level) or SET UINTERRATHONCOV (CME single
Parameter Configuration > RNC Oriented None-Coverage based Inter-rat
3.15 Modifying RNC Parameters in Batches) (RNC level) to configure parameters
related to non-coverage-based inter-frequency handover to GSM.
1.

Type, select RRC_MEAS_CTRL.
2.
After services are set up, view in the traced messages whether the RNC has sent the
UE an inter-frequency measurement control message shown in Figure 276-1.
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD UCELLHOCOMM (CME single

919
RAN14.0
Oriented Handover Common Algorithm Parameters; CME batch modification

center: 3.18 Modifying UMTS Cell Parameters in Batches). In this step, set InterRAT CS handover switch or Inter-RAT PS handover switch to OFF.
----End
Example
//Activating Inter-RAT Handover Based on Service
ADD UCELLHOCOMM: CellId=111, CSServiceHOSwitch=ON, PSServiceHOSwitch=ON;
//Deactivating Inter-RAT Handover Based on Service
MOD UCELLHOCOMM: CellId=111, CSServiceHOSwitch=OFF, PSServiceHOSwitch=OFF;
Issue 06 (2013-03-25)

920
RAN14.0
277

Based on Load
Inter-RAT Handover Based on Load.
Prerequisites
l

If this feature is used for HSDPA or HSUPA load control, the feature WRFD-010610
HSDPA Introduction Package or WRFD-010612 HSUPA Introduction Package has
been configured correspondingly before this feature is activated.
License
Context
This feature is an important part of Load Reshuffling (LDR). It enables some UEs in a UMTS
cell to be blindly handed over to a GSM or GPRS cell to reduce the load of the UMTS cell.
Procedure
l
Issue 06 (2013-03-25)
1.

Parameters in Batches) to activate the inter-RAT handover. In this step, select the
HandOver Switch.
2.

921
RAN14.0
to add the information about a GSM cell.
3.
Cell; CME batch modification center: not supported) to add the GSM cell as a
4.
Run the BSC6900 MML command ADD UCELLLDR (CME single configuration:
Parameters in Batches) to set the inter-RAT handover policy for the UMTS cell. In
this step, set DL LDR fourth action to CSInterRatShouldBeLDHO(CS domain
inter-rat should be load handover), DL LDR fifth action to
PSInterRatShouldBeLDHO(PS domain inter-rat should be load handover), UL
LDR fourth action to CSInterRatShouldBeLDHO(CS domain inter-rat should
be load handover), and UL LDR fifth action to PSInterRatShouldBeLDHO(PS
domain inter-rat should be load handover).
5.
Run the BSC6900 MML command ADD UCELLINTERRATHONCOV (CME

Oriented None-Coverage Based Inter-rat Handover Measurement Algorithm
Parameters in Batches) (at the cell level) or SET UINTERRATHONCOV (CME
single configuration: UMTS Radio Global Configuration Express > HandOver
3.15 Modifying RNC Parameters in Batches) (at the RNC level) to configure
parameters related to non-coverage-based inter-frequency handover to GSM.
1.
Initiate Iu interface message tracing and Uu interface message tracing on the

BSC6900 LMT.
2.
Use a UE in the UMTS cell to call another UE in the same cell. The call is set up
successfully.
3.
Run the BSC6900 MML command MOD UCELLLDM to reduce the downlink LDR
threshold.
The following messages can be traced on the Iu interface: the
RANAP_RELOCATION_REQUIRED message from the RNC to the CN, and the
RANAP_RELOCATION_COMMAND message from the CN to the RNC.
The following message can be traced on the Uu interface: the
RRC_HO_FROM_UTRAN_CMD_GSM message from the RNC to the UE.
The following messages can be traced on the Iu interface: the
RANAP_RELOCATION_REQUIRED message from the RNC to the CN, the
RANAP_RELOCATION_COMMAND message from the CN to the RNC, the
RANAP_IU_RELEASE_COMMAND message from the CN to the RNC, and the
RANAP_IU_RELEASE_COMPLETE message from the RNC to the CN.
1.
Issue 06 (2013-03-25)
Parameters in Batches) to deactivate the load-based handover. In this step, set DL
922
RAN14.0
LDR fourth action, DL LDR fifth action, UL LDR fourth action, and UL LDR
fifth action to NoAct.
2.

Parameters in Batches) to deactivate the inter-RAT handover. In this step, deselect
the HO_INTER_RAT_CS_OUT_SWITCH and
HandOver Switch.
----End
Example
//Activating Inter-RAT Handover Based on Load
ADD UEXT2GCELL: GSMCellIndex=2, GSMCellName="2", NBscIndex=2,
LdPrdRprtSwitch=OFF, MCC="460", MNC="07", CnOpGrpIndex=1, LAC=H'0012,
CfgRacInd=REQUIRE, RAC=H'01, CID=2, NCC=2, BCC=2, BcchArfcn=1000,
RatCellType=GSM, UseOfHcs=NOT_USED;
ADD U2GNCELL: RncId=1, CellId=2, GSMCellIndex=2, BlindHoFlag=TRUE,
BlindHOPrio=1, NPrioFlag=FALSE;
ADD UCELLLDR: CellId=1, DlLdrFourthAction=CSInterRatShouldBeLDHO,
DlLdrFifthAction=PSInterRatShouldBeLDHO,
UlLdrFourthAction=CSInterRatShouldBeLDHO,
UlLdrFifthAction=PSInterRatShouldBeLDHO;
ADD UCELLINTERRATHONCOV: CellId=1;
//Deactivating Inter-RAT Handover Based on Load
MOD UCELLLDR: CellId=1, DlLdrFourthAction=NoAct, DlLdrFifthAction=NoAct,
UlLdrFourthAction=NoAct, UlLdrFifthAction=NoAct;
Issue 06 (2013-03-25)

923
RAN14.0
278
Configuring Inter-RAT Redirection

Based on Distance
This section describes how to activate and verify the optional feature WRFD-020401 Inter-RAT
Redirection Based on Distance.
Prerequisites
l

The feature WRFD-020400 DRD Introduction Package has been configured before this
License
Context
If a UE initiates a CS voice call with a long distance to the antenna of a 3G cell, the UE may
experience call drops when the UE moves out of the pilot polluted area. To solve this problem,
the RAN redirects a UE to a GSM cell based on the distance threshold when the UE initiates an
RRC connection setup request.
Procedure
l
1.
run the BSC6900 MML command SET UDISTANCEREDIRECTION (CME

Batches) to set the BSC6900-level parameters.
Set Redirection Switch to ON.
Set Propagation delay threshold as specified in 3GPP TS 25.433
Issue 06 (2013-03-25)

924
RAN14.0
Set Redirection Factor Of LDR and Redirection Factor Of Normal to

2.
run the BSC6900 MML command ADD UCELLDISTANCEREDIRECTION

Parameters > Cell-Oriented Delay Based RRC Redirection Parameters; CME
set the cell-level parameters.
Set Redirection Switch to ON.
Set Propagation delay threshold as specified in 3GPP TS 25.433.
Set Redirection Factor Of LDR and Redirection Factor Of Normal to
NOTE
If cell-level redirection parameters are set for a cell, the cell-level settings take effect. If no
cell-level redirection parameters are set for the cell, the BSC6900-level settings take effect.
1.
Initiate Uu interface message tracing on the BSC6900 LMT, as shown in Figure

278-1.
2.
Simulate a scenario where pilot pollution occurs. Place the UE in a place where the
UE is far away from the NodeB and pilot signals are strong. Then, use the UE to
establish a CS voice call.
3.
Check the messages traced on the Uu interface.

As shown in Figure 278-2, if the RRC CONNECTION REJECT message
contains the information element (IE) GSM-Targetcellinfo, the RAN has
redirected the UE to the GSM network, and this feature has been activated.
Issue 06 (2013-03-25)

925
RAN14.0
If the RRC CONNECTION REJECT message does not contain the IE GSMTargetcellinfo, this feature is not activated.
Figure 278-2 GSM-Targetcellinfo IE
1.
run the BSC6900 MML command SET UDISTANCEREDIRECTION (CME

Batches) to deactivate this feature in the BSC6900 level. In this step, set Redirection
Switch to OFF.
2.
run the BSC6900 MML command MOD UCELLDISTANCEREDIRECTION

Parameters > Cell-Oriented Delay Based RRC Redirection Parameters; CME
deactivate this feature in the cell level. In this step, set Redirection Switch to OFF.
NOTE
If cell-level redirection parameters are set for a cell, the cell-level settings take effect. If no
cell-level redirection parameters are set for the cell, the BSC6900-level settings take effect.
----End
Example
//Activating Inter-RAT Redirection Based on Distance
//Activating this feature in the BSC6900 level
SET UDISTANCEREDIRECTION: RedirSwitch=ON, DelayThs=100,
RedirFactorOfLDR=70, RedirFactorOfNorm=60;
//Activating this feature in the cell level
ADD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=ON, DelayThs=100,
RedirFactorOfLDR=80, RedirFactorOfNorm=60;
//Deactivating Inter-RAT Redirection Based on Distance
//Deactivating this feature in the BSC6900 level
SET UDISTANCEREDIRECTION: RedirSwitch=OFF;
//Deactivating this feature in the cell level
MOD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=OFF;
Issue 06 (2013-03-25)

926
RAN14.0
279
Configuring 3G/2G Common Load

Management
3G/2G Common Load Management.
Prerequisites
l

This feature is required only when one of the following features is available:
WRFD-020400 DRD Introduction Package
WRFD-020308 Inter-RAT Handover Phase 2
License
Others
The CN supports this feature.
The BSS supports this feature.
Context
The 3G/2G Common Load Management applies to inter-RAT handover and inter system direct
retry. The load of source cell and target cell is considered during inter-RAT handover from 3G
to 2G or from 2G to 3G and inter system direct retry.
Procedure
l
Issue 06 (2013-03-25)
927
RAN14.0
1.

HO_INTER_RAT_PS_OUT_SWITCH through the HandOver Switch.
2.
Run the BSC6900 MML command SET UINTERRATHONCOV (CME single

3.15 Modifying RNC Parameters in Batches) to enable the 3G/2G common load
management function. In this step, select the Send Load Info to GSM Ind and NCOV
Reloc Ind Based on GSM Cell Load.
3.

to add a GSM cell neighboring to the UMTS coverage.
1.
Run the BSC6900 MML command LST UINTERRATHONCOV to check whether

the parameters Send Load Info to GSM Ind and NCOV Reloc Ind based on GSM
cell load are set to ON.
2.
Run the BSC6900 MML command LST U2GNCELL to ensure the inter-RAT
neighboring cell for the GSM system is added correctly.
NOTE
Consult Huawei engineers about the verification solution to obtain professional technical support.
1.
Run the BSC6900 MML command SET UINTERRATHONCOV (CME single

3.15 Modifying RNC Parameters in Batches) to set the parameter Send Load Info
to GSM Ind to OFF and the parameter NCOV Reloc Ind based on GSM cell load
to OFF.
----End
Example
//Activating 3G/2G Common Load Management
SET UINTERRATHONCOV: SndLdInfo2GsmInd=ON, NcovHoOn2GldInd=ON;
//Deactivating 3G/2G Common Load Management
SET UINTERRATHONCOV: SndLdInfo2GsmInd=OFF, NcovHoOn2GldInd=OFF;
Issue 06 (2013-03-25)

928
RAN14.0
280
Configuring Mobility Between

UMTS and LTE Phase 1
Mobility Between UMTS and LTE Phase 1. For details about how to configure this feature on
the LTE side, see the related documents provided by the LTE equipment vendor. (This feature
Prerequisites
l

License
Other Prerequisites
The UE supports both UMTS and LTE.
The LTE network supports this feature.
Context
The feature Mobility Between UMTS and LTE Phase 1 provides the following functions:
l
UMTS supports bidirectional cell reselection between a UMTS cell and an LTE cell.
UMTS supports PS handovers from an LTE cell to a UMTS cell.
Procedure
1.
Run the BSC6900 MML command ADD UCELLSIBSWITCH or MOD

UCELLSIBSWITCH. In this step, set SIB Switch to SIB19.
After the information about the frequencies of neighboring LTE cells is configured
and SIB Switch is set to SIB19, the BSC6900 sends SIB19 messages to UEs. The
Issue 06 (2013-03-25)

929
RAN14.0
SIB19 message contains the neighboring LTE cell list and LTE cell reselection
parameters.
2.
Run the BSC6900 MML command ADD UCELLSELRESEL or MOD

UCELLSELRESEL. In this step, set Absolute priority level of the serving cell to
Inter-RAT measurement is performed based on the settings of RSCP threshold for
low-prio-freq measurement initiation and Ec/No threshold for low-prio-freq
measurement initiation. The measurement result provides a reference to cell
reselection.
3.
Run the BSC6900 MML command ADD UCELLNFREQPRIOINFO or MOD

UCELLNFREQPRIOINFO to configure the information about the frequencies of
neighboring cells.
The UE makes cell reselection decisions based on the configured information about
the frequencies of neighboring cells.
4.
Configure the related data, such as the neighboring cell relationships between cells,
on the LTE side.
by Huawei, see the LTE document Mobility Management in Connected Mode
Parameter Description.
5.
Run the BSC6900 MML command ADD UNODEB or MOD UNODEB. In this step,
set NodeB Protocol Version to R8 or the higher version.
1.
Issue 06 (2013-03-25)
Trace dialog box, select RRC_SYS_INFO_TYPE19 to trace Uu interface SIB19
message.

930
RAN14.0
2.

If the SIB19 message has been traced on the Uu interface, as shown in Figure
If the SIB19 message is not traced on the Uu interface, this feature is not activated.
Figure 280-2 SIB message tracing
NOTE
To deactivate this feature, you can either turn off the SIB19 switch or deactivate the license.
l To deactivate this feature in a specific cell, you are advised to turn off the SIB19 switch.
l To deactivate this feature in all cells under a BSC6900, deactivate the license. This method is
not recommended.
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD UCELLSIBSWITCH. In this step,

deselect the SIB19 check box under the parameter SIB Switch to turn off the SIB19
switch in a cell. After the switch is turned off, the BSC6900 stops sending SIB19
messages to UEs. In such a case, the configured absolute priority of the serving cell
931
RAN14.0
and the configured information about the frequencies of neighboring cells become
ineffective.
2.
Run the BSC6900 MML command SET LICENSE to deactivate the license
controlling the feature Mobility Between UMTS and LTE Phase 1.
----End
Example
//Activating Mobility Between UMTS and LTE Phase 1
MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-1;
MOD UCELLSELRESEL: CellId=1, QualMeas=CPICH_ECNO, QrxlevminExtSup=FALSE,
NonhcsInd=NOT_CONFIGURED, ThdPrioritySearch1=2, ThdPrioritySearch2=2;
MOD UCELLNFREQPRIOINFO: CellId=1, EARFCN=1, NPriority=2,
BlacklstCellNumber=D0;
MOD UNODEB: NodeBId=1, NodeBProtclVer=R9;
//Deactivating Mobility Between UMTS and LTE Phase 1
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES,
FUNCTIONSWITCH5=LQW1ULM01-0;
Issue 06 (2013-03-25)

932
RAN14.0
281 Configuring Service-Based PS Service Redirection from

UMTS to LTE
281
Configuring Service-Based PS
Service Redirection from UMTS to LTE
Service-Based PS Service Redirection from UMTS to LTE.
Prerequisites
l
There is no requirement for BSC6900 and NodeB.

License
Others
The UE must support 3GPP Release 8 (Sept. 2008) or later. It also must support both
UMTS and LTE.
The SGSN support this feature.
CN should support cooperation from UMTS to LTE.
The neighboring LTE cell has been configured. For details, see Configuring a
Neighboring LTE Cell.
Context
With this feature, the operator can choose to hand over the high-speed PS services from the
UMTS network to the LTE network. This helps fully utilize the UMTS and LTE network
resources, improving the user experience.
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD ULTECELL (CME single configuration:
933
RAN14.0

UMTS to LTE
External Cell Configuration > RNC LTE External Cell; CME batch modification
center: not supported) to set an LTE cell. In this step, set LTE Cell Supporting PS
HO Indicator to NotSupport and set BlackCell List Flag to False.
2.
Run the BSC6900 MML command SET UU2LTEHONCOV (CME single

Parameter Configuration > RNC-Oriented Non-Coverage-Based UMTS-LTE
not supported) to set RNC-Oriented Non-Coverage-Based UMTS-LTE Handover
Measurement Algorithm Parameters. The BSC6900 sends these parameters to the UE
by means of a measurement control message.
3.
Optional: Run the BSC6900 MML command ADD UCELLU2LTEHONCOV

Parameters > Cell-Oriented Non-Coverage-Based UMTS-LTE Handover
Modifying UMTS Cell Parameters in Batches) to set the cell-level non-coveragebased UMTS-to-LTE handover measurement parameters for a cell.
4.

CME batch modification center: not supported) to modify the basic configuration of
a typical radio access bearer (RAB). In this step, set EUTRANSHIND to
HO_TO_EUTRAN_SHOULD_BE_PERFORM.
5.

Parameters in Batches) to select HO_LTE_PS_OUT_SWITCH and
HO_LTE_SERVICE_PS_OUT_SWITCH from HandOver Switch drop list.
Start Uu interface tracing on the LMT to trace messages on the Uu interface.
View the RRC_MEAS_CTRL message, as shown in Figure 281-1. If the
measurementCommand message contains the information element (IE) e-UTRAFrequencyInfo, this feature takes effect. The measurement control message sent by the
BSC6900 contains the LTE cell information.
After receiving the message, the UE measures the signal quality in the LTE cell. The
measurement result serves as the basis for handover decision.
Issue 06 (2013-03-25)

934
RAN14.0

UMTS to LTE
Figure 281-1 Viewing the IE e-UTRA-FrequencyInfo
View the RRC_CONN_REL message, as shown in Figure 281-2. If in the message the
rrcConnectionRelease message contains the IE EUTRA-TargetFreqInfo, the RRC
connection release message carries the LTE cell information.
After receiving this message, the UE is handed over to the LTE network and the UE
reestablishes PS services in the LTE cell.
Figure 281-2 Viewing the IE EUTRA-TargetFreqInfo
1.

Parameters in Batches) to deselect HO_LTE_SERVICE_PS_OUT_SWITCH
from the HandOver Switch drop list.
----End
Example
/Configuring an LTE cell
MOD ULTECELL: LTECellIndex=1, SuppPSHOFlag=NotSupport, BlackFlag=False;
Issue 06 (2013-03-25)

935
RAN14.0

UMTS to LTE
//Setting the parameters related to the RNC-oriented non coverage-based

UMTS-to-LTE handover measurement algorithm
SET UU2LTEHONCOV:
LTEMeasTypOf3C=MeasurementQuantity, U2LTEFilterCoef=D6,
U2LTEMeasTime=30, LTEMeasQuanOf3C=RSRP, Hystfor3C=2, TrigTime3C=D10,
TargetRatThdRSRP=20, TargetRatThdRSRQ=30;
//Setting the parameters related to the cell-oriented non coverage-based
UMTS-to-LTE handover measurement algorithm
ADD UCELLU2LTEHONCOV: CellId=1, LTEMeasTypOf3C=MeasurementQuantity,
U2LTEFilterCoef=D6, U2LTEMeasTime=30, LTEMeasQuanOf3C=RSRP, Hystfor3C=2,
TrigTime3C=D10, TargetRatThdRSRP=20, TargetRatThdRSRQ=30;
//Modifying the basic configuration of a typical RAB
MOD UTYPRABBASIC: RabIndex=1, EUTRANSHIND=HO_TO_EUTRAN_SHOULD_BE_PERFORM;
//Enabling HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH
HoSwitch=HO_LTE_PS_OUT_SWITCH-1&HO_LTE_SERVICE_PS_OUT_SWITCH-1;
//Disabling HO_LTE_SERVICE_PS_OUT_SWITCH
SET UCORRMALGOSWITCH: HoSwitch=HO_LTE_SERVICE_PS_OUT_SWITCH-0;
Issue 06 (2013-03-25)

936
RAN14.0
282 Configuring Service-Based PS Handover from UMTS to

LTE
282
Configuring Service-Based PS
Service-Based PS Handover from UMTS to LTE.
Prerequisites
l
This BSC6900 supports this feature.

License
Other Prerequisites
The UE must comply with 3GPP Release 8 or later and support UMTS-to-LTE PS
handovers and LTE measurement.
The eNodeB and MME must support UMTS-to-LTE PS handovers.
The SGSN must support UMTS-to-LTE PS handovers.
Context
With this feature, the operator can choose to hand over the high-speed PS services from the
UMTS network to the LTE network. In this way, user experience is improved, and the network
resources of UMTS and LTE are fully utilized.
l
Precautions
None
Issue 06 (2013-03-25)
Data Preparation

937
RAN14.0

LTE
Parameter Name
Parameter ID
Setting
Description
Source
Inter-RAT cell
support PS HO
indicator
SuppPSHOFlag
Set this parameter

to Support.
Network plan
BlackCell List Flag
BlackFlag
Set this parameter

to False.
Network plan
Service-Based
Handover to LTE
Allowed
EUTRANSHIND
Set this parameter

to
HO_TO_EUTRA
N_SHOULD_BE_
PERFORM.
Network plan
HandOver Switch
HoSwitch
The
HO_LTE_PS_OU
T_SWITCH and
HO_LTE_SERVI
CE_PSHO_OUT_
SWITCH should
be selected.
Network plan
Procedure
l
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command MOD ULTECELL (CME single configuration:
External Cell Configuration > RNC LTE External Cell; CME batch modification
center: not supported) to set an LTE cell. In this step, set LTE Cell Supporting PS
HO Indicator to Support(Support) and set BlackCell List Flag to False.
2.
Run the BSC6900 MML command SET UU2LTEHONCOV (CME single

Parameter Configuration > RNC-Oriented Non-Coverage-Based UMTS-LTE
not supported) to set the RNC-level non-coverage-based UMTS-to-LTE handover
measurement parameters. These parameter settings are to be delivered in the
measurement control information by the BSC6900 to UEs.
3.
Optional: Run the BSC6900 MML command ADD UCELLU2LTEHONCOV

Parameters > Cell-Oriented Non-Coverage-Based UMTS-LTE Handover
Modifying UMTS Cell Parameters in Batches) to set the cell-level non-coveragebased UMTS-to-LTE handover measurement parameters for a cell.
4.

CME batch modification center: not supported) to allow the UMTS-to-LTE PS
handovers. In this step, set Service-Based Handover to LTE Allowed to
HO_TO_EUTRAN_SHOULD_BE_PERFORM.
938
RAN14.0

LTE
5.

Parameters in Batches). In this step, select HO_LTE_PS_OUT_SWITCH and
HO_LTE_SERVICE_PSHO_OUT_SWITCH under HandOver Switch to enable
the service-based UMTS-to-LTE PS handovers.
6.
Optional: When the target LTE network is an MOCN and the PLMN of the primary
operator is the same as the primary PLMN of the LTE cell or when the target LTE
network is not an MOCN but the PLMNs of UMTS and LTE are different, the
following configurations are required to implement UMTS-to-LTE PS handovers.
a.

Configuration > CN Operator; CME batch modification center: not supported).
In this step, add the operator to which the target LTE network belongs to the
operator list, and configure the operator information about the LTE network, such
as OperatorType, CnOperatorName, MCC, MNC, and CnOpIndex.
b.

Configuration > CN Operator Group; CME batch modification center: not
supported). In this step, associate CnOpGrpIndex of the external cell with the
operator of the target LTE network.
c.
Run the BSC6900 MML command SET UOPERATORSHARINGMODE

(CME single configuration: UMTS Global Configuration Express > Operator
Configuration > RNC Operators Sharing Mode; CME batch modification
center: not supported). In this step, turn on the InterPlmnHoAllowedInterRat
switch to support inter-PLMN interoperations.
Start Iu interface message tracing on the LMT.
View the RANAP_RELOCATION_REQUIRED message. If the value of ucChoice in
the message is IU_RELOC_U2L, the feature has been activated.
1.

Parameters in Batches). In this step, clear
HO_LTE_SERVICE_PSHO_OUT_SWITCH under HandOver Switch to disable
the service-based UMTS-to-LTE PS handovers.
----End
Example
//Activating Service-Based PS Handover from UMTS to LTE
//Configuring an LTE cell
MOD ULTECELL: LTECellIndex=1, SuppPSHOFlag=Support, BlackFlag=False;
//Setting the RNC-level non-coverage-based UMTS-to-LTE handover
measurement parameters
SET UU2LTEHONCOV: LTEMeasTypOf3C=MeasurementQuantity, U2LTEFilterCoef=D6,
U2LTEMeasTime=30, LTEMeasQuanOf3C=RSRP, Hystfor3C=2, TrigTime3C=D10,
Issue 06 (2013-03-25)

939
RAN14.0

LTE
TargetRatThdRSRP=20, TargetRatThdRSRQ=30;
//Setting the cell-level non-coverage-based UMTS-to-LTE handover
measurement parameters
ADD UCELLU2LTEHONCOV: CellId=1, LTEMeasTypOf3C=MeasurementQuantity,
U2LTEFilterCoef=D6, U2LTEMeasTime=30, LTEMeasQuanOf3C=RSRP, Hystfor3C=2,
TrigTime3C=D10, TargetRatThdRSRP=20, TargetRatThdRSRQ=30;
//Modifying the basic information about RAB of the typical service
MOD UTYPRABBASIC: RabIndex=1, EUTRANSHIND=HO_TO_EUTRAN_SHOULD_BE_PERFORM;
//Enabling the service-based UMTS-to-LTE PS handovers
HoSwitch=HO_LTE_PS_OUT_SWITCH-1&HO_LTE_SERVICE_PSHO_OUT_SWITCH-1;
//Deactivating Service-Based PS Handover from UMTS to LTE
///Disabling the service-based UMTS-to-LTE PS handovers
SET UCORRMALGOSWITCH: HoSwitch=HO_LTE_SERVICE_PSHO_OUT_SWITCH-0;
Issue 06 (2013-03-25)

940
RAN14.0
283
Configuring Fast CS Fallback Based

on RIM
fast CS fallback based on RIM. For details about how to configure this feature on the LTE side,
see the related documents provided by the LTE equipment vendor.
Prerequisites
l

License
Other Prerequisites
The UE must support flash CSFB in Release 9.
The mobility management entity (MME) and serving GPRS support node (SGSN) must
support the RIM procedure in 3GPP release 9. If the core network (CN) is earlier than
3GPP release 9, it must support eNodeB ID conversion.
Context
This feature enables the eNodeB to obtain and maintain the system information of the UMTS
cell, including the ID of the target cell and convolutional code, through the RAN Information
Management (RIM) procedure and sends the information to the UE in the RRC Connection
Release message. This can reduce the access time when the UE is redirected from an LTE
network to a UMTS network without reading system information, improving user experience.
l
Precautions
None
l
Issue 06 (2013-03-25)
Data Preparation
941
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Process Control
Switch 2
PROCESSSWITC
H2
The
FAST_CS_FB_B
ASEDON_RIM_S
WITCH should be
deselected.
Network plan
Procedure
l
1.
Configure the data on the LTE side, including setting the neighbor relationships
between cells.
by Huawei, see the LTE document CS Fallback Parameter Description.
2.
1.
Trace the Iu-interface and UE signaling on the RNC LMT. Trace the S1 interface
signaling (on the eNodeB LMT for Huawei eNodeBs) and the UE signaling (on the
M2000 for Huawei eNodeBs).
2.
Verify that the Direct Information Transfer message that contains RANINFORMATION PDU REQUEST or RAN-INFORMATION PDU REPORT is
transmitted over the Iu and S1 interfaces.
3.
Initiate a CS service in an LTE cell. Check the UE signaling and verify that the IE
CellInfoListUTRA-FDD-r9 in the RRC Connection Release message contains the
frequency, primary scrambling code, and system information (including MIB, SIB1,
SIB3, SIB5, and SIB7) of the target UMTS cell.
4.
Check the UE log and measure the duration between the UE receiving an RRC
Connection Release from the eNodeB and the UE sending an RRC Connection
Request to the target UMTS cell. Verify that during this duration the UE does not read
the system information of the target UMTS cell, and that this duration is shorter than
the duration measured when Fast CS Fallback Based on RIM is disabled.
5.
Check the UE signaling and verify that the RNC sends the UE an RRC_RB_SETUP
message that contains the IE rrc-StateIndicator and instructs the UE to move to the
CELL_DCH state.
1.
Issue 06 (2013-03-25)

RNC Parameters in Batches). In this step, select
FAST_CS_FB_BASEDON_RIM_SWITCH under Process Control Switch 2 to
enable this feature.

RNC Parameters in Batches). In this step, clear
942
RAN14.0
FAST_CS_FB_BASEDON_RIM_SWITCH under Process Control Switch 2 to

disable this feature.
----End
Example
//Activating fast CS fallback based on RIM
SET URRCTRLSWITCH: PROCESSSWITCH2=FAST_CS_FB_BASEDON_RIM_SWITCH-0;
//Deactivating fast CS fallback based on RIM
SET URRCTRLSWITCH: PROCESSSWITCH2=FAST_CS_FB_BASEDON_RIM_SWITCH-1;
Issue 06 (2013-03-25)

943
RAN14.0
284
Configuring Queuing and

Preemption
Queuing and Preemption.
Prerequisites
l
None.

WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA
License
Others
To enable the preemption function, the CN must send the allocation/retention priority
(ARP) IE to the RNC during the RAB assignment procedure so that the RNC can obtain
RAB service priorities. The forced preemption function does not depend on the CN.
Context
This feature supports queuing and preemption to implement service differentiation in congested
networks, providing better service for high-priority users.
Procedure
l
1.
Issue 06 (2013-03-25)

944
RAN14.0
Batches) to turn on the queuing and preemption switches. In this step, set Preempt
algorithm switch to ON and set Queue algorithm switch to ON.
l
1.
Check the value of the counter.

Check the value of the counter VS.RAB.Estab.QueueTime.CS and
VS.RAB.Estab.QueueTime.PS, if the value of any one of these counters is not 0,
the function of queuing has been activated.
Check the value of the counter VS.RAB.AbnormRel.CS.Preempt,
VS.RAB.AbnormRel.PS.Preempt, RRC.AttConnRelDCCH.Preempt and
RRC.AttConnRelCCCH.Preempt, if the value of any one of these counters is not
0, the function of preemption has been activated.
1.

Batches) to turn off the queuing and preemption switches. In this step, set Preempt
algorithm switch to OFF and set Queue algorithm switch to OFF.
----End
Example
//Activating Queuing and Preemption
SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, QueueAlgoSwitch=ON;
//Deactivating Queuing and Preemption
SET UQUEUEPREEMPT: PreemptAlgoSwitch=OFF, QueueAlgoSwitch=OFF;
Issue 06 (2013-03-25)

945
RAN14.0
285
Configuring Access Class Restriction
Access Class Restriction.
Prerequisites
l
None.

License
Context
When the cell or system is overloaded, this feature can restrict user access based on the allowed
service class by broadcasting system information, controlling potential load requirements of the
system.
Procedure
l
1.
Run the BSC6900 MML command SET UACALGO (CME single configuration:
UMTS Radio Global Configuration Express > Access Restriction Algorithm
Parameters Configuration > AC Algorithm Parameters; CME batch modification
center: 3.15 Modifying RNC Parameters in Batches). In this step, set AC
Restriction Switch to ON and other parameters to appropriate values.
Verifying Access Class Restriction based on CPU overload
Issue 06 (2013-03-25)
1.
Start Uu Interface Trace on the BSC6900 LMT.
2.
Run the BSC6900 MML command LST FCCPUTHD to query the settings of
AC control threshold and AC restore threshold.
946
RAN14.0
3.
Run the BSC6900 MML command SET FCCPUTHD. In this step, set AC control
threshold and AC restore threshold to appropriate values.
4.
Enable a large number of UEs to access a cell until the CPU usage exceeds the AC
restore threshold.
5.
Start Uu Interface Trace on the BSC6900 LMT and select

RRC_SYS_INFO_TYPE3 as the message type. If the value of barred IE in the
RRC_SYS_INFO_TYPE3 message is 0, as shown in Figure 285-1, the feature
has been activated. If the value is not 0, the feature is not activated.
Figure 285-1 RRC_SYS_INFO_TYPE3 message
6.
Reduce the number of UEs in the cell until the CPU usage is lower than the AC
restore threshold.
7.
Run the BSC6900 MML command SET FCCPUTHD. In this step, set AC control
threshold and AC restore threshold to their original values.
Verifying Access Class Restriction based on the access failure on the Iu interface
Issue 06 (2013-03-25)
1.
Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set
Process switch to SYS_INFO_UPDATE_FOR_IU_RST and
BARRED_CELL_FOR_CSDOMAIN_RST.
2.
Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step,

set Cell CAC algorithm switch to SYS_INFO_UPDATE_FOR_IU_RST
(System Info Update Switch for Iu Reset).
3.
Start Uu Interface Trace on the BSC6900 LMT and select

RRC_SYS_INFO_TYPE3 as the message to be traced. Interrupt the Iu-interface
947
RAN14.0
connection and wait for a period of time. If the traced

RRC_SYS_INFO_TYPE3 message indicates that the cell is barred, as shown in
Figure 285-2, the feature has been activated. If the traced message does not
indicate that the cell is barred, the feature is not activated.
Figure 285-2 RRC_SYS_INFO_TYPE3 message
1.
Run the BSC6900 MML command SET UACALGO (CME single configuration:
UMTS Radio Global Configuration Express > Access Restriction Algorithm
Parameters Configuration > AC Algorithm Parameters; CME batch modification
center: 3.15 Modifying RNC Parameters in Batches). In this step, set AC
Restriction Switch to OFF.
----End
Example
//Activating Access Class Restriction
SET UACALGO: AcRstrctSwitch=ON, AcRstrctPercent=5, AcIntervalOfCell=1,
AcRstrctIntervalLen=6;
//Verifying Access Class Restriction based on CPU overload
SET FCCPUTHD: BRDCLASS=XPU, ACCTHD=40, ACRTHD=35;
SET FCCPUTHD: BRDCLASS=XPU, ACCTHD=80, ACRTHD=70;
//Verifying Access Class Restriction based on the access failure on the
Iu interface
Issue 06 (2013-03-25)

948
RAN14.0
SET URRCTRLSWITCH:
PROCESSSWITCH=SYS_INFO_UPDATE_FOR_IU_RST-1&BARRED_CELL_FOR_CSDOMAIN_RST-1
;
MOD UCELLALGOSWITCH: NBMCacAlgoSwitch=SYS_INFO_UPDATE_FOR_IU_RST-1;
//Deactivating Access Class Restriction
SET UACALGO: AcRstrctSwitch=OFF;
Issue 06 (2013-03-25)

949
RAN14.0
286 Configuring Traffic Priority Mapping onto Transmission

Resources
286
Configuring Traffic Priority
Mapping onto Transmission Resources
Traffic Priority Mapping onto Transmission Resources.
Prerequisites
l

License
Context
This feature enables the dynamical mapping of the services onto the transport bearers according
to the TC, ARP, and THP of the user. Operators can flexibly configure the mapping to provide
differentiated services while guaranteeing the QoS.
Procedure
l
1.
add the transport resource mapping.
NOTE
l Before setting the type of a mapping path for a service, ensure that this type of path is
available. Otherwise, the service may fail to be set up.
l The primary path and the secondary path for the same service type must be different.
l The default 14 transport resource mappings (indexed from 0 to 13) are added when the
system is initialized, and you cannot modify them.
Issue 06 (2013-03-25)

950
RAN14.0
286 Configuring Traffic Priority Mapping onto Transmission

Resources
2.
Mapping; CME batch modification center: not supported) to add the TRM mapping
to the adjacent node.
NOTE
Before running this command, ensure that the adjacent node or the NodeB is added by running
the BSC6900 MML command ADD ADJNODE (CME single configuration: NodeB
Configuration Express > IUB_RNC > IP Transport > Adjacent Node; CME batch
modification center: not supported) or ADD UNODEB (CME single configuration: Main
View > Right Click RNC > Create Logical NodeB; CME batch modification center: not
supported).
This feature can be verified only by running the LST commands.
1.
Run the BSC6900 MML command LST TRMMAP to check whether the transport
resource mapping is correct.
2.
If the mapping is incorrect, run the BSC6900 MML command MOD TRMMAP to
modify the mapping.
NOTE
Do not modify Interface Type and Transport Type in the MOD TRMMAP command.
1.
mapping to the adjacent node.
2.
remove the transport resource mapping.
----End
Example
//Activating Traffic Priority Mapping onto Transmission Resources
ADD TRMMAP: TMI=15, REMARK="15", ITFT=IUB, TRANST=IP, VOICEPRIPATH=AF11;
//Verifying Traffic Priority Mapping onto Transmission Resources
LST TRMMAP: TMI=15;
MOD TRMMAP: TMI=15, ITFT=IUB, TRANST=IP, CCHSECPATH=RT_VBR;
//Deactivating Traffic Priority Mapping onto Transmission Resources
RMV ADJMAP: ANI=10,ITFT=IUB,CNMNGMODE=SHARE;
RMV TRMMAP: TMI=15;
Issue 06 (2013-03-25)

951
RAN14.0
287
Configuring Differentiated Service

Based on SPI Weight
Differentiated Service Based on SPI Weight.
Prerequisites
l

WRFD-01061103 Scheduling based on EPF and GBR has been configured before
this feature is applied in the downlink over the Uu interface.
WRFD-01061402 Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE
Resource Management has been configured before this feature is applied in the
uplink over the Uu interface. When this feature is enabled together with the optional
feature WRFD-01061402 Enhanced Fast UL Scheduling, only uplink Uu interface
resources can be differentially scheduled. When this feature is enabled together with
the optional feature RFD-010638 Dynamic CE Resource Management, both uplink
Uu interface resources and CE resources can be differentially scheduled.
WRFD-010610 HSDPA Introduction Package and WRFD-050405 Overbooking on
ATM Transmission, or WRFD-010610 HSDPA Introduction Package and
WRFD-050408 Overbooking on IP Transmission have been configured before this
feature is applied in the downlink over the Iub interface.
WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion has been
configured before this feature is applied in the uplink over the Iub interface.
License
Context
When Uu interface resources, CE resources, and Iub transmission resources do not meet the
GBR requirements of all online users, this feature enables the RAN to preferentially guarantee
Issue 06 (2013-03-25)

952
RAN14.0
the GBR of high-priority users. The RAN can thereby provide differentiated services under a
certain level of fairness.
Procedure
l
1.
Run the BSC6900 MML command SET UUSERPRIORITY (CME single

configuration: UMTS Radio Global Configuration Express > User Integrated
Priority Parameters Configuration > RNC Oriented User Priority Related
Batches) to configure gold, silver, and copper users.
2.
Run the BSC6900 MML command SET UTHPCLASS (CME single configuration:
UMTS Radio Global Configuration Express > Channel Management
Configuration > THP Class for Interactive Users; CME batch modification center:
3.15 Modifying RNC Parameters in Batches) to set priorities of PS interactive
services to appropriate values.
3.
Run the BSC6900 MML command SET USCHEDULEPRIOMAP (CME single

configuration: UMTS Radio Global Configuration Express > Channel
Management Configuration > Schedule Priority Map Information; CME batch
modification center: not supported) to set the scheduling priority mapping
information.
4.
Run the BSC6900 MML command SET UCAPARATERANGE (CME single

configuration: UMTS Radio Global Configuration Express > Channel
Management Configuration > Rate Thresholds for Differentiated HSPA Services
Based on SPI Weight; CME batch modification center: not supported) to set RNCspecific reference rates and rate thresholds of all levels in the uplink and downlink.
5.

UOPERCAPARATERANGE (CME single configuration: UMTS Radio Global
Configuration Express > Channel Management Configuration > Operator-Level
Rate Thresholds for SPI Weight of HSPA Services; CME batch modification
center: not supported) to set operator-specific reference rates and rate thresholds of
all levels in the uplink and downlink.
6.
Run the BSC6900 MML command SET USPIWEIGHT (CME single configuration:
UMTS Radio Global Configuration Express > Channel Management
Configuration > Factor of Schedule Priority; CME batch modification center: 3.15
Modifying RNC Parameters in Batches) to set RNC-specific scheduling priority
weight.
7.
Optional: Run the BSC6900 MML command ADD UOPERSPIWEIGHT (CME

single configuration: UMTS Radio Global Configuration Express > Channel
Management Configuration > Operator-Oriented Factor of Schedule Priority;
CME batch modification center: not supported) to set operator-specific scheduling
priority weight.
8.

RNC Parameters in Batches). In this step, set Process switch to
NODEB_PRIVATE_INTERFACE_SWITCH.
1.
Issue 06 (2013-03-25)
Establish services on UE A and UE B. Assume that the SPI and SPI weight of UE A
are 7 and 50 respectively and the SPI and SPI weight of UE B are 7 and 100
953
RAN14.0
respectively. In the traced Iub interface messages, check the information element (IE)
schedulingPriorityIndicator in the NBAP_RL_RECFG_PREP message to obtain
the SPI value; check the IE schedule-Prior-Indication-Weight-Private to obtain the
SPI weight, which is the actual SPI value for the NodeB, as shown in Figure 287-1,
Figure 287-2, Figure 287-3, and Figure 287-4.
Figure 287-1 SPI and SPI weight of UE A in the uplink
Issue 06 (2013-03-25)

954
RAN14.0
Figure 287-2 SPI and SPI weight of UE A in the downlink
Figure 287-3 SPI and SPI weight of UE B in the uplink
Issue 06 (2013-03-25)

955
RAN14.0
Figure 287-4 SPI and SPI weight of UE B in the downlink
2.
Check the real-time throughput of UEs by referring to Monitoring UL Throughput

and Bandwidth and Monitoring DL Throughput and Bandwidth.
Generally, if the throughput of users with higher SPI weight is higher than that of users
with lower SPI weight, this feature has taken effect. The throughput of UE B is
approximately twice the throughput of UE A, as shown in the
NBAP_RL_RECFG_PREP message. If the throughput of users with higher SPI
weight is lower than that of users with lower SPI weight, this feature has not taken
effect.
1.
----End
Example
/*Activating Differentiated Service Based on SPI Weight*/
//Configuring gold, silver, and copper users
SET UUSERPRIORITY: ARP1Priority=Gold, ARP2Priority=Gold,
ARP3Priority=Gold, ARP4Priority=Gold, ARP5Priority=Gold,
ARP6Priority=Silver, ARP7Priority=Silver, ARP8Priority=Silver,
ARP9Priority=Silver, ARP10Priority=Silver, ARP11Priority=Copper,
ARP12Priority=Copper, ARP13Priority=Copper, ARP14Priority=Copper,
ARP15Priority=Copper, PriorityReference=ARP, CarrierTypePriorInd=NONE;
//Setting the priorities of PS interactive services
Issue 06 (2013-03-25)

956
RAN14.0
SET UTHPCLASS: THP1Class=High, THP2Class=High, THP3Class=High,

THP4Class=High, THP5Class=High, THP6Class=Medium, THP7Class=Medium,
THP8Class=Medium, THP9Class=Medium, THP10Class=Medium, THP11Class=Low,
THP12Class=Low, THP13Class=Low, THP14Class=Low, THP15Class=Low;
//Setting the scheduling priority mapping information
SET USCHEDULEPRIOMAP: TrafficClass=INTERACTIVE, UserPriority=GOLD,
THPClass=High, SPI=7;
//Setting the RNC-specific reference rates and rate thresholds of all
levels in the uplink and downlink
SET UCAPARATERANGE: DlCapacitySelect=MBR, DlRateThreshold1=128,
DlRateThreshold2=256, DlRateThreshold3=512, DlRateThreshold4=1000,
DlRateThreshold8=20000, DlRateThreshold9=45000, UlCapacitySelect=MBR,
UlRateThreshold1=128, UlRateThreshold2=256, UlRateThreshold3=512,
UlRateThreshold7=10000, UlRateThreshold8=20000, UlRateThreshold9=45000;
//Setting the operator-specific reference rates and rate thresholds of all
levels in the uplink and downlink
ADD UOPERCAPARATERANGE: CnOpIndex=0, DlRateThreshold1=128,
DlRateThreshold8=16000, DlRateThreshold9=32000, UlRateThreshold1=128,
UlRateThreshold8=5500, UlRateThreshold9=7500;
//Setting the RNC-specific scheduling priority weight
SET USPIWEIGHT: SPI=7, SpiWeight=100, RateRangeSPIWeightInd=TRUE,
DlRateRange1SPIWeight=10, DlRateRange2SPIWeight=20,
UlRateRange1SPIWeight=10, UlRateRange2SPIWeight=20,
UlRateRange9SPIWeight=90, UlRateRange10SPIWeight=100;
//Setting the operator-specific scheduling priority weight
ADD UOPERSPIWEIGHT: CnOpIndex=0, SPI=7, RateRangeSPIWeightInd=TRUE;
//Enabling the switch for a NodeB private interface
Issue 06 (2013-03-25)

957
RAN14.0
288 Configuring Optimization of R99 and HSUPA Users

Fairness
288
Configuring Optimization of R99 and

HSUPA Users Fairness
Optimization of R99 and HSUPA Users Fairness.
Prerequisites
l
The HBBI and HULP boards in the BTS3812E/BTS3812AE do not support this feature.
To support this feature, the BTS3812E/BTS3812AE must be configured with the EBBI
or EDLP board.
The BBU3806 in the DBS3800 does not support this feature. To support this feature,
the DBS3800 must be configured with the EBBC or EBBCd board.
To support this feature, the 3900 series base stations must be configured with WBBPb
or WBBPd boards. WBBPa boards in the 3900 series base stations do not support this
feature.

License
Context
In scenarios where R99 and HUSUPA users share the same TRX, this feature provides fair
services for the two types of users and improves HSUPA user experience by considering R99
and HSUPA user satisfaction with throughput, that is, the ratio of effective rate to guaranteed
bit rate (GBR).
Procedure
l
1.
Issue 06 (2013-03-25)
To enable the algorithm switch for cell-level rate reduction for BE services based on
R99 and HSUPA user fairness, run the BSC6900 MML command MOD
958
RAN14.0

Fairness

center: 3.18 Modifying UMTS Cell Parameters in Batches) with BE rate reduction
switch based on fairness set to ON(Algorithm is ON).
2.
To set the common measurement period based on R99 and HSUPA user fairness, run
the BSC6900 MML command SET ULDCPERIOD (CME single configuration:
modification center: 3.15 Modifying RNC Parameters in Batches) with Fairness
period timer length set to an appropriate value according to the network plan.
3.
To set the common measurement period based on R99 and HSUPA user fairness in a
satellite communications environment, run the BSC6900 MML command SET
USATLDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC
Oriented LDC Algorithm Cycle Length Under Satellite Circuit Emulation; CME
batch modification center: 3.15 Modifying RNC Parameters in Batches) with
Fairness period timer length set to an appropriate value according to the network
plan.
4.
To set the fairness threshold for R99 and HSUPA users, run the BSC6900 MML
command MOD UCELLLDM (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented LDM Algorithm
Parameters in Batches) with Fairness threshold set to an appropriate default value
5.
To enable the DCCC algorithm switch for applying the dynamic channel
reconfiguration control algorithm to the RNC, run the BSC6900 MML command SET
Modifying RNC Parameters in Batches) to select the DRA_DCCC_SWITCH
from the drop-down list Dynamic Resource Allocation Switch.
1.
Issue 06 (2013-03-25)
Initiate Iub interface tracing on the BSC6900 LMT, as shown in Figure 288-1.

959
RAN14.0

Fairness
Figure 288-1 Iub interface tracing dialog box
2.
Establish PS BE services on the HSUPA and R99 UEs.
3.
The BSC6900 side sends a COMMON MEASUREMENT INITIATION

REQUEST message to the NodeB side. The NodeB side submits fairness common
measurement reports to the BSC6900 side, as shown in Figure 288-2.
Figure 288-2 fairness common measurement report
1.
To disable the algorithm switch for cell-level rate reduction for BE services based on
R99 and HSUPA user fairness, run the BSC6900 MML command MOD
center: 3.18 Modifying UMTS Cell Parameters in Batches) with BE rate reduction
switch based on fairness set to OFF(Algorithm is OFF).
----End
Example
/*Activating the Optimization of R99 and HSUPA Users Fairness feature
//Enabling the algorithm switch for cell-level rate reduction for BE
Issue 06 (2013-03-25)

960
RAN14.0

Fairness
services based on R99 and HSUPA user fairness

MOD UCELLALGOSWITCH: CellId=11011, BERateReduceOnFairnessSwitch=ON;
Where, [PARA]CellId[/PARA] is set to the cell ID for the algorithm
switch.
//Setting the common measurement period based on R99 and HSUPA user
fairness
SET ULDCPERIOD: FairnessPeriodTimerLen=11;
//Setting the common measurement period based on R99 and HSUPA user
fairness in a satellite communications environment
SET USATLDCPERIOD: FairnessPeriodTimerLen=11;
//Setting the fairness threshold for R99 and HSUPA users
MOD UCELLLDM: CellId=11011,FairnessThd=150;
switch.
//Enable the DCCC algorithm switch
/*Deactivating the Optimization of R99 and HSUPA Users Fairness feature
//Disabling the algorithm switch for cell-level rate reduction for BE
services based on R99 and HSUPA user fairness
MOD UCELLALGOSWITCH: CellId=11011, BERateReduceOnFairnessSwitch=OFF;
switch.
Issue 06 (2013-03-25)

961
RAN14.0
289
Configuring Active Queue

Management (AQM)
Active Queue Management (AQM).
Prerequisites
l

License
Context
The AQM feature can improve user's feeling when HTTP and download services simultaneously
exist.
Procedure
l
1.
1.
Issue 06 (2013-03-25)

Parameters in Batches) to turn on the RNC-level AQM switch. In this step, select
the Dynamic resource allocation switch check box under the parameter
DRA_AQM_SWITCH.
Initiate UE tracing on the BSC6900 LMT. In the displayed UE Trace dialog box,
select the Debug Mode check box, as shown in Figure 289-1.
962
RAN14.0
Figure 289-1 UE Trace dialog box
2.
Establish a BE service on the UE. Verify the value of the information element (IE)
"ucAqmSwitch" contained in the message PdcpSetupInfo as follows:
If the value of the IE "ucAqmSwitch" is 1, this feature has been activated.
If the value of the IE "ucAqmSwitch" is 0, this feature is not activated.
1.

Parameters in Batches). In this step, deselect the DRA_AQM_SWITCH check box
under the parameter Dynamic resource allocation switch.
----End
Example
//Activating Active Queue Management (AQM)
SET UCORRMALGOSWITCH: DraSwitch=DRA_AQM_SWITCH-1;
//Deactivating Active Queue Management (AQM)
SET UCORRMALGOSWITCH: DraSwitch=DRA_AQM_SWITCH-0;
Issue 06 (2013-03-25)

963
RAN14.0
290 Configuring Quality Improvement for Subscribed

Service
290
Configuring Quality Improvement

for Subscribed Service
Quality Improvement for Subscribed Service.
Prerequisites
l
For BTS3812E and BTS3812AE, EBBI, EBOI, EULP or EULPd board is needed.
For BBU3806, EBBC/EBBCd is needed.
For BBU3900, WBBPb or WBBPd is needed.

License
Others
None.
Context
This feature enables BSC6900 to adjust the user scheduling priority by identifying the
characteristics of IP data streams and modifying the initial Scheduling Priority Indicator (SPI)
Weight of downlink services.
The feature grants high scheduling priorities to specific services on which telecom operators
focus, such as services from specific servers or http services. By doing this, the bandwidth
required for processing the services is guaranteed.
In addition, the feature lowers the scheduling weight of some non-paying services that consume
a large amount of bandwidth. By doing this, sufficient bandwidth is available for services with
high scheduling priorities.
Issue 06 (2013-03-25)

964
RAN14.0

Service
Procedure
l
1.
Set the initial SPI Weight on the BSC6900 LMT.

If the license controlling the feature WRFD-020806 Differentiated Service Based
on SPI Weight has been activated, run the BSC6900 MML command SET
USPIWEIGHT (CME single configuration: UMTS Radio Global
Configuration Express > Channel Management Configuration > Factor of
Schedule Priority; CME batch modification center: 3.15 Modifying RNC
Parameters in Batches). In this step, set the parameters Scheduling Priority
Indicator and SPI Weight based on the actual network plan.
If the license controlling the feature WRFD-020806 Differentiated Service Based
on SPI Weight is not activated, run the BSC6900 MML command SET UFRC
Basic Resource Control Parameter Configuration > RNC Oriented FRC
Parameters in Batches). In this step, set Default SPI Weight based on the actual
network plan.
2.

NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter
Process switch.
3.

DRA_IP_SERVICE_QOS_SWITCH check box under the parameter Dynamic
4.
Run the BSC6900 MML command ADD UIPSERVICEQOS (CME single

Simple Packet Identify Three Element Parameter; CME batch modification center:
not supported). In this step, set the parameters related to the Quality Improvement for
Subscribed Service feature to appropriate values based on the network plan.
5.

3.15 Modifying RNC Parameters in Batches). In this step, set Service Priority
Adjusting Coefficient to an appropriate value.
1.
1.
Issue 06 (2013-03-25)
When the resources (for example, resources on the air interface) are limited, activating
this feature may increase the throughput of FTP services and shorten the network delay
of HTTP services.
965
RAN14.0

Service

DRA_IP_SERVICE_QOS_SWITCH check box under the parameter Dynamic
----End
Example
//Activating Quality Improvement for Subscribed Service
//Setting the initial SPI weight value if the license control switch for
the feature WRFD-020806 Differentiated Service Based on SPI Weight is
turned on
//Setting the initial SPI weight value if the license control switch for
the feature WRFD-020806 Differentiated Service Based on SPI Weight is not
turned on
//Turning on the switch for the Quality Improvement for Subscribed
Service feature
SET UCORRMALGOSWITCH: DraSwitch=DRA_IP_SERVICE_QOS_SWITCH-1;
//Setting the parameters related to the Quality Improvement for Subscribed
Service feature
ADD UIPSERVICEQOS: CnOpIndex=0, RecIndex=1, TrafficType=SPI,
MatchType=IPAndPort, IPAddress="192.168.0.100",
IPMask="255.255.255.255", PortNum=8080, ProtocolType=TCP,
TrafficPriority=HIGH;
//Setting the scheduling priority weight corresponding to high-priority
services
SET UDPUCFGDATA: ServPriAdjCoefHigh=100;
//Deactivating Quality Improvement for Subscribed Service
SET UCORRMALGOSWITCH: DraSwitch=DRA_IP_SERVICE_QOS_SWITCH-0;
Issue 06 (2013-03-25)

966
RAN14.0
291
Configuring TCP Accelerator
TCP Accelerator.
Prerequisites
l

License
Other Prerequisites
The TCP Accelerator feature takes effect only when the server has the Time Stamp
option in the TCP deselected.
Downlink TCP accelerator requires that the BSC6900 version is RAN11.0 or later.
Uplink TCP accelerator requires that the BSC6900 version is RAN12.0 or later.
Context
The TCP Accelerator feature in RAN11.0 optimizes the data transmission performance in the
downlink.
Based on this feature in RAN11.0, RAN12.0 introduces the TCP Accelerator feature to optimize
the data transmission in the uplink. In addition, the Acknowledgment (ACK) splitting
technology, ACK splitting monitoring technology, and uplink data packet sequencing
technology are adopted. These technologies aim at accelerating the slow start and restore
processes during uplink data transmission, reducing the impact of packet loss on the performance
of uplink TCP data transmission.
NOTE
Data configurations are required only at the BSC6900 to activate, verify, and deactivate this feature.
Issue 06 (2013-03-25)

967
RAN14.0
Procedure
l
1.

3.15 Modifying RNC Parameters in Batches) to turn on the TCP accelerator switch.
In this step, select TPE_DOWNLINK_SWITCH or TPE_UPLINK_SWITCH
from TPE switch according to the actual requirements.
1.
Run the BSC6900 MML command LST UDPUCFGDATA to check whether the
TCP accelerator switch is turned on. If the switch is turned on, this feature has been
activated.
2.
Use a test terminal to download a file of 200 KB from the FTP server. Then, compare
the download time taken before and after the TPE_DOWNLINK_SWITCH is turned
on.
3.
Use a test terminal to upload a file of 200 KB to the FTP server. Then, compare the
upload time taken before and after the TPE_UPLINK_SWITCH is turned on.
1.

3.15 Modifying RNC Parameters in Batches) to turn off the TCP accelerator switch.
In this step, deselect TPE_DOWNLINK_SWITCH or TPE_UPLINK_SWITCH
from TPE switch according to the actual requirements.
----End
Example
//Activating TCP Accelerator
Turning on the TCP accelerator switch at the RNC
SET UDPUCFGDATA: TpeSwitch=TPE_DOWNLINK_SWITCH-1&TPE_UPLINK_SWITCH-1;
//Deactivating TCP Accelerator
Turning off the TCP accelerator switch at the RNC
SET UDPUCFGDATA: TpeSwitch=TPE_DOWNLINK_SWITCH-0&TPE_UPLINK_SWITCH-0;
Issue 06 (2013-03-25)

968
RAN14.0
292
Configuring Rate Negotiation at

Admission Control
Rate Negotiation at Admission Control.
Prerequisites
l

License
Other Prerequisites
For Iu QoS negotiation, the CN nodes must support this feature.
For RAB rate reduction, the CN nodes do not need to support this feature.
Context
This feature supports the procedures for Iu QoS negotiation and RAB rate reduction.
Procedure
l
Activating QoS negotiation
1.
Issue 06 (2013-03-25)

Parameters in Batches). In this step, set Dynamic Resource Allocation
Switch to DRA_DCCC_SWITCH, and set PS rate negotiation switch to
969
RAN14.0
PS_BE_IU_QOS_NEG_SWITCH and
PS_STREAM_IU_QOS_NEG_SWITCH.
Activating RAB rate reduction
1.

Parameters in Batches). In this step, set Dynamic Resource Allocation
Switch to DRA_DCCC_SWITCH, and set PS rate negotiation switch to
PS_RAB_DOWNSIZING_SWITCH.
Verifying QoS negotiation
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to query

the activation result.
2.
Start Iu message tracing on the BSC6900 LMT and establish a PS service, as shown
in Figure 292-1.
Figure 292-1 Iu message tracing
3.
Issue 06 (2013-03-25)
View the RANAP_RAB_ASSIGNMENT_REQ message. If it contains the IE "altRAB-Parameters", the CN supports Iu QoS negotiation, as shown in Figure
292-2.

970
RAN14.0
Figure 292-2 RANAP_RAB_ASSIGNMENT_REQ message on the Iu interface
Verifying RAB rate reduction

1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH to query

the activation result.
2.
Start Iu message tracing on the BSC6900 LMT and establish a PS service, as shown
in Figure 292-3.
Figure 292-3 Iu message tracing
3.
Issue 06 (2013-03-25)
View the RANAP_RAB_ASSIGNMENT_RESP message. If it contains the IE

"ass-RAB-Parameters", rate negotiation at admission control takes effect, and the
MaxBitrate is the data rate negotiated by the RNC, as shown in Figure 292-4.

971
RAN14.0
Figure 292-4 RANAP_RAB_ASSIGNMENT_RESP message on the Iu interface
Deactivating QoS negotiation
1.

Parameters in Batches). In this step, deselect DRA_DCCC_SWITCH from the
Dynamic Resource Allocation Switch drop-down list box, and deselect
PS_BE_IU_QOS_NEG_SWITCH and
PS_STREAM_IU_QOS_NEG_SWITCH from the PS rate negotiation
switch drop-down list box.
Deactivating RAB rate reduction

1.

Parameters in Batches). In this step, deselect DRA_DCCC_SWITCH from the
Dynamic Resource Allocation Switch drop-down list box, and deselect
PS_RAB_DOWNSIZING_SWITCH from the PS rate negotiation switch dropdown list box.
----End
Example
//Activating Rate Negotiation at Admission Control
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1, PsSwitch
=PS_BE_IU_QOS_NEG_SWITCH-1&PS_STREAM_IU_QOS_NEG_SWITCH-1;
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1,
PsSwitch=PS_RAB_DOWNSIZING_SWITCH-1;
//Deactivating Rate Negotiation at Admission Control
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-0, PsSwitch
=PS_BE_IU_QOS_NEG_SWITCH-0&PS_STREAM_IU_QOS_NEG_SWITCH-0;
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-0,
PsSwitch=PS_RAB_DOWNSIZING_SWITCH-0;
Issue 06 (2013-03-25)

972
RAN14.0
293
Configuring Videophone Service

Restriction
Videophone Service Restriction.
Prerequisites
l

License
Context
This feature disables the videophone (VP) function of a cell through cell-level configurations to
meet telecom operators' requirements for information security in restricted areas.
Procedure
l
Issue 06 (2013-03-25)
1.
Modifying UMTS Cell Parameters in Batches) to deactivate the cell. In this step,
set Cell ID to an appropriate value.
2.

Parameters in Batches). In this step, set Cell VP Limit Indicator to TRUE.
3.
973
RAN14.0

Modifying UMTS Cell Parameters in Batches) to activate the cell. In this step, set
Cell ID to an appropriate value.
4.

on another RNC that controls the neighboring cell. In this step, set Cell VP Limit
Indicator to TRUE.
1.
Use two VP-capable UEs to camp on the same cell, and then use one UE to initiate a
VP to the other UE.
2.
Initiate Iu Interface Trace on the BSC6900 LMT.

The BSC6900 sends an RANAP_RAB_ASSIGNMENT_RSP message to the CN.
1.
Modifying UMTS Cell Parameters in Batches) to deactivate the cell. In this step,
set Cell ID to an appropriate value.
2.

Parameters in Batches). In this step, set Cell VP Limit Indicator to FALSE.
3.
Modifying UMTS Cell Parameters in Batches) to activate the cell. In this step, set
Cell ID to an appropriate value.
4.

on another RNC that controls the neighboring cell. In this step, set Cell VP Limit
Indicator to FALSE.
----End
Example
//Activating Videophone Service Restriction
MOD UCELLSETUP: CellId=1111, VPLimitInd=TRUE;
MOD UEXT3GCELL: NRncId=1, CellId=1111, VPLimitInd=TRUE;
//Deactivating Videophone Service Restriction
DEA
MOD
ACT
MOD
Issue 06 (2013-03-25)
UCELL: CellId=1111;
UCELLSETUP: CellId=1111, VPLimitInd=FALSE;
UCELL: CellId=1111;
UEXT3GCELL: NRncId=1, CellId=1111, VPLimitInd=FALSE;

974
RAN14.0
294 Configuring Intelligent Inter-Carrier UE Layered

Management
294
Configuring Intelligent Inter-Carrier

UE Layered Management
Intelligent Inter-Carrier UE Layered Management.
Prerequisites
l

License
Context
This feature allows the RAN to intelligently distinguish between UEs and data cards in multicarrier scenarios and to separately set up services on different carriers.
Procedure
l
The following methods assume that cell F1 and cell F2 are used.
Issue 06 (2013-03-25)
1.
Device Type Steering DRD Switch to ON.
2.

UMTS Cell Parameters in Batches) twice to enable the layered terminal
975
RAN14.0

Management
management function for cell F1 and cell F2 respectively. In this step, set
FuncSwitch1 to INTELLIGENT_INTERFREQ_UE_TYPE_STEERING.
3.

DR_RAB_SING_DRD_SWITCH.
4.
Run the BSC6900 MML command ADD UDEVICETYPEIMSI (CME single

Parameter Configuration > IMSI segment; CME batch modification center: not
supported). In this step, set IMSI Segment Choice to MultiIMSI and specify the
IMSI number range by setting IMSI Segment Start Value and IMSI Segment End
Value. If the IMSI of a terminal falls into the IMSI number range, the terminal is
regarded as a data card.
5.
Run the BSC6900 MML command ADD UDEVICETYPEPRIOGROUP (CME

Retry Parameter Configuration > Device Type Steering Priority Group; CME
batch modification center: not supported) to add terminal type priorities.
6.
Parameters in Batches) twice to bind a terminal type priority to cell F1 and cell F2
respectively.
7.
Optional: Configure preferred camping. Cell F1 is a preferred camping frequency,

and cell F2 is a services balancing frequency.
NOTE
This feature does not depend on the camping policy setting of an existing network. When this
feature is activated and cell F2 provides discontinuous coverage, you must configure interfrequency neighboring cells for cell F2 during network optimization so that this feature can be
enabled.
Method 1
Issue 06 (2013-03-25)
a.
Run the BSC6900 MML command MOD UCELLSELRESEL (CME single

Cell Selection And Reselection; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to make it difficult for UEs
in idle mode to trigger inter-frequency measurement. In this step, set Interfreq cell reselection threshold for idle mode of cell F1 to 0.
b.
Run the BSC6900 MML command MOD UCELLSELRESEL (CME single

Cell Selection And Reselection; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to make UEs in idle mode
keep triggering inter-frequency measurement. In this step, set Inter-freq cell
reselection threshold for idle mode of cell F2 to 127.
c.
Run the BSC6900 MML command MOD UINTERFREQNCELL (CME

single configuration: UMTS Cell Configuration Express > Neighboring
Cell > Inter-frequency Neighboring Cell; CME batch modification center:
not supported) to set inter-frequency neighboring cell parameters (cell F1 to
cell F2).
976
RAN14.0

Management
Set SIB11 Indicator to TRUE(Send).

Set IdleQoffset1sn and IdleQoffset2sn to 20.
Set SIB12 Indicator to FALSE(Do not send).
d.
Run the BSC6900 MML command MOD UINTERFREQNCELL (CME

single configuration: UMTS Cell Configuration Express > Neighboring
Cell > Inter-frequency Neighboring Cell; CME batch modification center:
not supported) to set inter-frequency neighboring cell parameters (cell F2 to
cell F1).
Set SIB11 Indicator to TRUE(Send).
Set IdleQoffset1sn and IdleQoffset2sn to -20.
Set SIB12 Indicator to FALSE(Do not send).
e.
Optional: For cell F2 that provides discontinuous coverage, it is

recommended to Run the BSC6900 MML command MOD
UCELLSELRESEL (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Selection And
Reselection; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to prevent UEs in idle mode from camping on the
edge of cell F2. In this step, set Min Quality Level to -10 and Min RX
level to -48.
f.
Optional: When the UE state transition function is enabled, it is

recommended to turn on the SIB4 message switch. Run the BSC6900 MML
command MOD UCELLSIBSWITCH (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell SIB Switch; CME
Batches) to turn on the SIB4 message switch of cell F2. In this step, select
the SIB4 check box under the parameter SIB Switch.
Method 2
Run the BSC6900 MML command MOD UCELLACCESSSTRICT (CME
Cell Access Restriction Information; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) to forbid UE access to cell F2.
Set the parameters according to the network condition.
l
1.
Issue 06 (2013-03-25)
On the Trace tab page of the BSC6900 LMT, initiate Uu interface tracing, as shown
in Figure 294-1.

977
RAN14.0

Management
Figure 294-1 Uu interface tracing task
2.
3.
Check that data card A is in idle mode and camps on cell F2. The priority of data cards
in cell F1 (the cell ID is 11013) is higher than that of data cards in cell F2 (the cell ID
is 11014).
4.
Use data card A to establish an R99 PS service, and check the messages traced on the
Uu interface.
The BSC6900 sends an RRC_RB_SETUP message to data card A in cell F2. Data
card A responds to the BSC6900 with an RRC_RB_SETUP_CMP message in cell
F1. The R99 PS service is established in cell F1, as shown in Figure 294-2.
Figure 294-2 Message tracing
l
Issue 06 (2013-03-25)
978
RAN14.0

Management
1.
Device Type Steering DRD Switch to OFF.
2.
Run the BSC6900 MML command RMV UCELLLICENSE (CME single

License Resource/Function Item; CME batch modification center: not supported)
to disable the layered terminal management function for the cell.
----End
Example
//Activating Intelligent Inter-Carrier UE Layered Management
//Turning on the layered terminal management switch
SET UDRD: DPGDRDSwitch=ON;
//Enabling the layered terminal management function for cell F1 and cell
F2
ADD UCELLLICENSE: CellId=11013, INTELLIGENT_INTERFREQ_UE_TYPE_STEERING-1;
ADD UCELLLICENSE: CellId=11014, INTELLIGENT_INTERFREQ_UE_TYPE_STEERING-1;
//Turning on the single-service DRD switch
SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1;
//Configuring an IMSI number range
ADD UDEVICETYPEIMSI: IMSISegIndex=1, IMSISegChoice=MultiIMSI,
IMSIStart="502808888800070", IMSIEnd="502808888800080";
//Adding terminal type priorities
ADD UDEVICETYPEPRIOGROUP: DPGId=1, UEDP=1, DataCardDP=1, ReservedDP=1;
ADD UDEVICETYPEPRIOGROUP: DPGId=2, UEDP=2, DataCardDP=2, ReservedDP=1;
//Binding terminal type priorities to cells
MOD UCELL: CellId=11013, DPGId=1;
MOD UCELL: CellId=11014, DPGId=2;
//Configuring cell reselection for cell F1
MOD UCELLSELRESEL:CellId=11013, QualMeas=CPICH_ECNO, IdleSintersearch=0;
//Configuring cell reselection for cell F2
MOD UCELLSELRESEL:CellId=11014, QualMeas=CPICH_ECNO,
IdleSintersearch=127, ConnSintrasearch=5, ConnSintersearch=2,
SsearchRat=2;
//Configuring co-coverage inter-frequency neighboring cell parameters
(cell F1 to cell F2)
NCellId=11014, SIB11Ind=TRUE, SIB12Ind=FALSE, IdleQoffset1sn=20,
IdleQoffset2sn=20;
//Configuring co-coverage inter-frequency neighboring cell parameters
(cell F2 to cell F1)
NCellId=11013, SIB11Ind=TRUE, SIB12Ind=FALSE, IdleQoffset1sn=-20,
IdleQoffset2sn=-20;
//Turning on the SIB4 message switch for cell F2
MOD UCELLSELRESEL: CellId=11014, QualMeas=CPICH_ECNO, Qqualmin=-10,
Qrxlevmin=-48;
//Deactivating Intelligent Inter-Carrier UE Layered Management
//Turning off the layered terminal management switch
SET UDRD: DPGDRDSwitch=OFF;
//Disabling the layered terminal management function for a cell
RMV UCELLLICENSE: CellId=11013;
RMV UCELLLICENSE: CellId=11014;
Issue 06 (2013-03-25)

979
RAN14.0
295
Configuring Micro NodeB SelfPlanning
Micro NodeB Self-Planning.
Prerequisites
l
Only the BTS3902E supports this feature.
The BTS3902E has been configured with the SON receiver (default configuration) and
antenna.
If the BTS3902E uses an integrated antenna, the integrated antenna incorporates the
function of the SON receiver antenna and therefore a SON receiver antenna does
not need to be configured.
If the BTS3902E uses an external antenna, a SON receiver antenna needs to be
configured.
The RNC version must be RAN13.0 or later, and the RNC data can be configured and
modified on the M2000.

The feature WRFD-031101 NodeB Self-discovery Based on IP Mode and
WRFD-031102 NodeB Remote Self-configuration must be configured before this
License
Others
Data has been configured for micro NodeBs on the RNC side. The UARFCN,
scrambling code, LAC, RAC, and SAC do not need to be planned, but they must have
initial values in the data configuration file. The initial SAC value is configured in the
core network.
Issue 06 (2013-03-25)

980
RAN14.0
OM channels have been established for micro NodeBs, and micro NodeBs have
obtained their configuration files from the M2000. The UARFCN does not need to be
planned, but it must have an initial value in the data configuration file.
Necessary information has been obtained for SON receiver parameter settings.
The NodeB auto deployment function is enabled on the M2000 side.
The M2000 must support BTS3902E WCDMA self-planning.
The RNC version must be RAN13.0 or later, and the RNC data can be configured and
modified on the M2000.
The GBSC version must be GBSS 14.0 or later to support remote configuration by the
M2000.
Context
l
This feature automatically plans the following information for micro NodeBs:
Available UTRA Absolute Radio Frequency Channel Numbers (UARFCNs)
Scrambling codes
Intra-frequency neighboring cells
Inter-frequency neighboring cells
Inter-RAT neighboring cells between UMTS and GSM
LAC/SAC/RAC parameters, in which SAC self-planning results is cell ID.
Precautions
This feature interrupts micro NodeB services.
In micro NodeB self-planning, ensure that the logical cell on the RNC has been
deactivated when preparing the RNC-side micro NodeB configuration file. The
UARFCN, scrambling code, intra-frequency neighboring cell, inter-frequency
neighboring cell, and neighboring GSM cell, LAC, RAC, and SAC in the logical micro
NodeB configuration file on the RNC are initial values, not optimal values. They may
cause interference to neighboring cells.
Data Preparation
Preparing Data for SON Receivers
Before enabling this feature, SON receiver parameters must be preconfigured.
Issue 06 (2013-03-25)
SON Receiver
Parameter
Description
Source
RNC Name
Name of the radio network

controller in the WCDMA
system.
Network plan
MCC
The mobile country code

(MCC) consists of three
digits and identifies a
country to which a mobile
subscriber belongs.
Network plan

981
RAN14.0
SON Receiver
Parameter
Description
Source
MNC
The mobile network code

(MNC) consists of two or
three digits and identifies
a PLMN to which a mobile
subscriber belongs.
Network plan
Macro Frequency
Downlink UARFCNs
available to the macro
NodeB, which are listed
on the UARFCN list of the
macro NodeB. Value
range: 0 to 16383
Network plan is not

required. The range is
provided by operators.
NOTE
As specified in 3GPP TS
25.133, the UE in idle or
connected mode can
measure inter-frequency
neighboring cells
corresponding to only two
inter-frequency UARFCNs.
Therefore, the RNC
instructs the UE to measure
not greater than two
UARFCNs of interfrequency neighboring cells
delivered in the system
broadcast message and
measurement control. To
ensure continuous mobility,
UARFCNs for continuous
coverage must be specified
when macro downlink
UARFCNs are configured,
so that the micro NodeB can
select the macro cells
corresponding to the
UARFCNs for continuous
coverage as inter-frequency
neighboring cells.
Micro Frequency
Downlink UARFCNs
available to the micro
NodeB, which are listed
on the UARFCN list of the
micro NodeB. Value
range: 0 to 16383
Network plan is not

NOTE
If necessary, the operator
can directly add a specific
UARFCN to the UARFCN
list of the micro NodeB.
Issue 06 (2013-03-25)

982
RAN14.0
SON Receiver
Parameter
Description
Source
Micro Scrambling Code
Primary scrambling code

available to the micro
NodeB. Value range: 0 to
511
Network plan is not

Preparing Configuration Files

During initial deployment, data configuration files need to be prepared on both the RNC
and micro NodeBs. The usual method is to prepare configuration files based on the
network plan. Since micro NodeB self-planning generates the settings of parameters
such as the UARFCN, scrambling code, intra-frequency neighboring cell, interfrequency neighboring cell, and neighboring GSM cell, and LAC/RAC/SAC, these
parameters do not need to be included in the network plan. However, these parameters
are mandatory in configuration files. The following table describes how to configure
them in default settings. For the other parameters such as transmission parameters,
configure them using the usual method.
Parameter Name
Setting Description
Source
UARFCN
Select the first downlink

UARFCN in the range
available to the SON
receiver as the downlink
UARFCN in the initial
configuration file.
Operating parameter of
the SON receiver
Calculate the uplink

UARFCN based on the
correlation between the
uplink and downlink
UARFCNs.
Issue 06 (2013-03-25)
Scrambling Code
Select the first scrambling

code in the range available
to the SON receiver as the
scrambling code in the
initial configuration file.
the SON receiver
Neighbor Relationship
It is null in the initial

configuration file.
the SON receiver
LAC/RAC
Select the LAC and RAC

that have been configured
on the RNC to which the
micro NodeB belongs.
the SON receiver
SAC
Equal to the cell ID of the

micro NodeB.
the SON receiver

983
RAN14.0
Procedure
l
Configuring SON Receiver Parameters on the M2000
After necessary data has been collected, perform the following steps on the M2000 to
configure SON receiver parameters.
1.
Choose Configuration > UMTS Self-Planning.
2.
Click the Receiver Parameter Settings tab.
3.
Under the Parameters node, select the data type to be configured.

and configure parameters in the added pre-configuration data. To
Click
change the value of a parameter, double-click the parameter and enter the new
value.
To delete a parameter value, click
4.
Click Save. In the confirmation dialog box, click OK.
5.
to manually synchronize the self-planning parameters configured by

Click
other clients on the M2000 for other self-planning regions.
Enabling Self-Planning on the M2000

After configuring SON receiver parameters, perform the following steps to enable selfplanning on the M2000.
1.
On the M2000, choose Configuration > Auto Deployment > NodeB Auto
Deployment.
2.
On the Deployment List tab, right-click one or more commissioning tasks and
choose Start from the shortcut menu. The Task Settings dialog box is displayed.
3.
Based on site conditions, select micro NodeB self-planning on the Select column.
After NodeB auto deployment starts, it will automatically start self-planning upon
the completion of self-discovery and self-configuration.
Check the progress and result of self-planning. A report is also available.
1.
Choose Configuration > UMTS Self-Planning.
2.
Check the task progress.

Click the Task Monitor tab to check ongoing and finished tasks. If required, click
to synchronize the self-planning tasks on the M2000 server.
3.
View the task report.

On the Task Monitor tab, right-click a finished task and choose View Report from
the shortcut menu. A report will be displayed in a browser window. Save the report
locally.
On the M2000 side, you can suspend a NodeB auto deployment task before the system
proceeds to the self-planning step. Once the self-planning step starts, it cannot be
suspended.
Issue 06 (2013-03-25)

984
RAN14.0
Once a micro NodeB receives a self-planning command, it starts procedures such as SON
receiver scanning and scanning result reporting. You cannot suspend self-planning.
----End
Example
None
Issue 06 (2013-03-25)

985
RAN14.0
296
Configuring NodeB Integrated IPSec
NodeB Integrated IPSec.
Prerequisites
l
Only the 3900 series base stations equipped with the UMPT board support this feature
on Ethernet ports.

This feature depends on the feature WRFD-050402 IP Transmission Introduction on
Iub Interface.
When a digital certificate is used for authentication, this feature depends on the feature
WRFD-140210 NodeB PKI Support.
This feature cannot be used with the Automatic Address Configuration Protocol
(AACP) function in the feature WRFD-031101 NodeB Self-Discovery Based on IP
Route.
License
Other Prerequisites
On a UMTS network, an SeGW must be deployed on the RNC side to support IP
Security (IPSec).
Context
l
IPSec policies include access control list (ACL) rules, IPSec protocols, and Internet Key
Exchange (IKE).
An ACL consists of a series of ACL rules, which are used to specify the data streams
to be protected. Only data streams that comply with ACL rules can enter an IPSec tunnel.
An IPSec protocol defines how to protect data streams and includes the protocol type,
encapsulation mode, and encryption and verification algorithms.
Issue 06 (2013-03-25)

986
RAN14.0
IKE is used to authenticate IPSec peers, negotiate encryption algorithms, and generate
session keys before an IPSec SA is established. IKE supports two methods for
authenticating IPSec peers: pre-shared key (PSK) and digital certificate.
l
During IPSec deployment, base station data can be encrypted in two modes: unified
encryption and separate encryption.
In unified encryption mode, O&M data streams are protected by IPSec. Secure Sockets
Layer (SSL) encryption can be implemented before IPSec encryption.
In separate encryption mode, O&M data streams are protected by SSL, not by IPSec.
Accordingly, IPSec networking scenarios are classified into the following types:
PKI-based networking in unified encryption mode
PKI-based networking in separate encryption mode
PSK-based networking in unified encryption mode
PSK-based networking in separate encryption mode
Precautions
IPSec ensures transmission security by encapsulating and encrypting IP packets. This
reduces the transmission efficiency of service packets on the bearer network.
Data Preparation
Prepare the data required for the IKE proposal (the IKEPROPOSAL MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Proposal ID
PROPID
User-defined
Encryption
Algorithm
ENCALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
Authentication
Algorithm
AUTHALG
The parameter
setting on the base
station and SeGW
sides must be the
same.

987
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Authentication
Method
AUTHMETH
If digital
certificates are
used for identity
authentication, this
parameter must be
set to
IKE_RSA_SIG
(RSA Digital
Certificate
Signature).
Source
If a PSK is used for

identity
parameter must be
set to
PRE_SHARED_
KEY(Pre-shared
Key).
Diffie-Hellman
Group
DHGRP
The parameter
setting on the base
station and SeGW
sides must be the
same.
PRF Algorith
PRFALG
This parameter
must be specified
when Version in
the IKEPEER MO
is set to IKE_V2
(IKE V2). The
default value is
recommended.
ISAKMP SA
Duration(s)
DURATION
The parameter
setting on the base
station and SeGW
sides must be the
same.
Prepare the data required for the IKE peer (the IKEPEER MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
IKE Peer Name
PEERNAME
User-defined

988
RAN14.0
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
IKE Proposal ID
PROPID
The value of this

parameter must be
the same as the
value of Proposal
ID in the
IKEPROPOSAL
MO.
Version
IKEVERSION
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)
Exchange Mode
EXCHMODE
This parameter
must be specified
when Version is
set to IKE_V1
(IKE V1). The
parameter setting
on the base station
and SeGW sides
must be the same.
Network plan
(negotiation with
the IPSec peer)
Local ID Type
IDTYPE
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)

Source
989
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Remote IP Address
REMOTEIP
If ENCAPMODE
in the
IPSECPROPOS
AL MO is set to
TRANSPORT,
the value of this
parameter must be
the same as that of
DIP in the
ACLRULE MO.
Otherwise,
encrypted packets
cannot be
decrypted.
Network plan
When
Encapsulation
Mode in the
IPSECPROPOS
AL MO is set to
TUNNEL
(Tunnel), the
value of this
parameter must be
the same as the IP
address of the peer
security gateway
and the
subjectaltname
field of the local
certificate.
Issue 06 (2013-03-25)

990
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Remote Name
REMOTENAME
The value of this

parameter must be
the same as the
IKE name
configured at the
IKE peer (for
example, the
SeGW).
Network plan
l If a PSK is used
for
authentication,
the value of this
parameter must
be the same as
that of Local
NAME of the
IKE peer.
l If digital
certificates are
used for
authentication,
the
subjectaltname
fields in the
certificates
used by the
local and peer
ends must be
set to the same
value.
Pre-shared Key
PKEY
If digital
Network plan
certificates are
(negotiation with
used for identity
the IPSec peer)
parameter does not
need to be
configured.
identity
parameter must be
specified and the
parameter value
must be the same
as that of the IKE
peer.
Issue 06 (2013-03-25)

991
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
DPD Mode
DPD
Network plan
DPD Idle Time(s)
DPDIDLETIME
DPD
Retransmission
Interval(s)
DPDRETRI
DPD
Retransmission
Count
DPDRETRN
DPD is enabled by
default. It is
recommended that
the values of DPDrelated parameters
be the same at both
IKE ends. If the
values are
different, the IKE
SA end with a
shorter timer
length will detect
that the peer is
offline before the
other IKE SA end
does and an IKE
re-negotiation will
be triggered.
Local IP Address
LOCALIP
When Version is
set to IKE_V1
(IKE V1) and
Local ID Type is
set to IP(IP
Identify), the
value of this
parameter must be
the same as the port
ID bound to the
IPSec.
Network plan
Prepare the data required for the ACL rule (the ACL MO).
One or multiple ACLs need to be configured based on the planned IPSec tunnels. In the
IPSECPOLICY MO, an IPSec policy is bound to an ACL based on the ACLID setting.
Only data streams that comply with ACL rules are processed according to the operations
defined in the IPSec policy.
Parameter Name
Parameter ID
Setting
Description
Source
ACL ID
ACLID
An ACL must
contain at least one
ACL rule.
Network plan
If an ACL is bound
to an IPSec policy,
the value of this
parameter ranges
from 3000 to 3999.
Issue 06 (2013-03-25)

992
RAN14.0
Prepare the data required for the ACL rule (the ACLRULE MO).
Depending on the network plan, an IPSec tunnel may require multiple ACL rules to
protect different types of data streams.
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
ACL ID
ACLID
The value of this

parameter must be
the same as that of
ACL ID in the
ACL MO.
Network plan
Rule ID
RULEID
Each ACL rule in

an ACL must have
a unique ID.
Protocol Type
PT
Source IP Address
SIP
If ENCAPMODE
in the
IPSECPROPOS
AL MO is set to
TRANSPORT,
the value of this
parameter must be
an existing device
IP address.
Otherwise,
encrypted packets
cannot be
decrypted.
Source Wildcard
SWC
Match Source Port
SMPT
This parameter and

the Match
Fragment
Messageparamete
r cannot be set to
YES
simultaneously.
Source Port
Operate
SOP
Source Port 1
SPT1
Source Port 2
SPT2

993
RAN14.0
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Destination IP
Address
DIP
If ENCAPMODE
in the
IPSECPROPOS
AL MO is set to
TRANSPORT,
the value of this
parameter must be
a host IP address.
The value of this
parameter must be
the same as that of
REMOTEIP in
the IKEPEER
MO. Otherwise,
encrypted packets
cannot be
decrypted.
Destination
Wildcard
DWC
Match Destination
Port
DMPT
This parameter and

the Match
Fragment
Messageparamete
r cannot be set to
YES
simultaneously.
Destination Port
Operate
DOP
Destination Port 1
DPT1
Destination Port 2
DPT2
Match DSCP
MDSCP
DSCP
DSCP
Match Fragment
Message
MFRG
VLAN ID Operate
VLANIDOP
If an ACL is bound
to an IPSec policy,
this parameter does
not need to be
configured.

Source
994
RAN14.0
Parameter Name
Parameter ID
Setting
Description
VLAN ID 1
VLANID1
If an ACL is bound
to an IPSec policy,
this parameter does
not need to be
configured.
VLAN ID 2
VLANID2
If an ACL is bound
to an IPSec policy,
this parameter does
not need to be
configured.
Source
Prepare the data required for the IPSec proposal (the IPSECPROPOSAL MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
IPSec Proposal
Name
PROPNAME
User-defined
Encapsulation
Mode
ENCAPMODE
The tunnel mode is

recommended.
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)
Transform
TRANMODE
The parameter
setting on the base
station and SeGW
sides must be the
same.
AH Authentication
Algorithm
AHAUTHALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
ESP
Authentication
Algorithm
ESPAUTHALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
ESP Encryption
Algorithm
ESPENCALG
The parameter
setting on the base
station and SeGW
sides must be the
same.

995
RAN14.0
Prepare the data required for the IPSec policy (the IPSECPOLICY MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Policy Group
Name
SPGN
User-defined
IPSec Sequence
No.
SPSN
User-defined
ACL ID
ACLID
An IPSec policy is
bound to an ACL
by using the ACL
IDparameter. Only
data streams that
comply with the
ACL are processed
according to the
operations defined
in the IPSec policy.
User-defined
IPsec Proposal
Name
PROPNAME
The value of this

parameter must be
the same as the
value of IPSec
Proposal Namein
the
IPSECPROPOS
AL MO.
User-defined
IKE Peer Name
PEERNAME
The value of this

parameter must be
the same as the
value of IKE Peer
Name in the
IKEPEER MO.
User-defined
Perfect Forward
Secrecy
PFS
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)

996
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Lefttime Config
LTCFG
If this parameter is
set to GLOBAL,
the IPSec SA
lifetime is
permanently set to
3600 seconds. If
this parameter is
set to LOCAL, the
IPSec SA lifetime
is specified by
LTS and LTKB.
Network plan
Lifetime Based On
Time(s)
LTS
This parameter
needs to be
specified when
LTCFG is set to
LOCAL.
Network plan
Lifetime Based On
Traffic(KB)
LTKB
This parameter
needs to be
specified when
LTCFG is set to
LOCAL.
Network plan
Anti-Replay
Windows
REPLAYWND
set to 0, the antireplay function
does not take
effect.
Network plan
Prepare the data required for binding an IPSec policy group to a port (the
IPSECBIND MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Cabinet No.
CN
Network plan
Subrack No.
SRN
Slot No.
SN
Subboard Type
SBT
Port Type
PT
Port No.
PN
If PT is set to ETH,
the port specified
by PN must not be
a member of an
Ethernet trunk.

997
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Policy Group
Name
SPGN
The value of this

parameter must be
the same as the
value of Policy
Group Namein
the
IPSECPOLICY
MO.
User-defined
If a PSK is used for authentication, prepare the IKE configuration data (the IKECFG
MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Local Name
IKELNM
This parameter
must be specified
when Local ID
Typeis set to
FQDN(Name
Identify). The
value of this
parameter must be
the same as the
IKE peer name
configured at the
SeGW.
Network plan
Keepalive Interval
IKEKLI
Keepalive
Timeout
IKEKLT
These two
parameters need to
be specified when
the keepalive
function is
required by IKEv1
entities. If
Keepalive
Timeout or
Keepalive
Interval is set to 0,
the keepalive
function is
disabled. The
value of Keepalive
Timeout must be
greater than that of
Keepalive
Interval.

998
RAN14.0
Parameter Name
Parameter ID
Setting
Description
DSCP
DSCP
This parameter
specifies the
differentiated
services code point
(DSCP) for IKE
negotiation
packets. The
recommended
value of this
parameter is 48.
Source
Procedure
l
Scenario 1: PKI-based Networking for a NodeB Using Unified Encryption
Figure 296-1 Example of PKI-based networking for a NodeB using unified encryption
In this networking scenario:

The UMTS UMPT provides IPSec and PKI.
The UMTS UMPT provides IPSec for the following data streams:
Signaling, service, and O&M data streams on the NodeB
Certificate-management-related data streams between the NodeB and the CA server
Data streams generated when the NodeB obtains the CRL from the CRL server
Issue 06 (2013-03-25)
1.
Run the NodeB MML command ADD IKEPROPOSAL (CME single configuration:
NodeB Configuration Express > IUB_NodeB > IP Transport Layer > Feature
Configuration > IPSecurity > IKE > IKE Proposal; CME batch modification
center: not supported) to add an IKE proposal.
2.
Run the NodeB MML command ADD IKEPEER (CME single configuration: NodeB
Configuration Express > IUB_NodeB > IP Transport Layer > Feature
999
RAN14.0
Configuration > IPSecurity > IKE > IKE Peer; CME batch modification center:
not supported) to add an IKE peer.
3.
Run the NodeB MML command ADD ACL (CME single configuration: NodeB
Configuration > IPSecurity > ACL > Access Control List; CME batch modification
center: not supported) to add an ACL.
4.
Run the NodeB MML command ADD ACLRULE (CME single configuration:
Configuration > Ipsecurity > ACL > Access Control List Rule; CME batch
modification center: not supported) to add a rule to the ACL.
5.
Run the NodeB MML command ADD IPSECPROPOSAL (CME single

Layer > Feature Configuration > IPSecurity > IPSec > IPSec Proposal; CME
batch modification center: not supported) to add an IPsec proposal.
6.
Run the NodeB MML command ADD IPSECPOLICY (CME single configuration:
Configuration > IPSecurity > IPSec > IPSec Policy; CME batch modification
center: not supported) to add an IPSec policy.
7.
Run the NodeB MML command ADD IPSECBIND (CME single configuration:
Configuration > IPSecurity > IPSec > IPSec Policy Group Binding; CME batch
modification center: not supported) to bind an IPSec policy to a port.
Scenario 2: PKI-based Networking for a NodeB Using Separate Encryption

Figure 296-2 Example of PKI-based networking for a NodeB using separate encryption

The UMTS UMPT does not provide IPSec for O&M data streams on the NodeB. It
provides IPSec for the following data streams:
Signaling and service data streams on the NodeB
1.
Issue 06 (2013-03-25)
1000
RAN14.0
2.
3.
4.
5.

6.
7.
Scenario 3: PSK-based Networking for a NodeB Using Unified Encryption

Figure 296-3 Example of PSK-based networking for a NodeB using unified encryption

The UMTS UMPT provides IPSec and PSK.
The UMTS UMPT provides IPSec for signaling, service, and O&M data streams on the
NodeB.
1.
Issue 06 (2013-03-25)
Run the NodeB MML command SET IKECFG (CME single configuration: NodeB
1001
RAN14.0
Configuration > IPSecurity > IKE > IKE Basic Configuration; CME batch
modification center: not supported) to set local IKE configurations.
2.
3.
4.
5.
6.

7.
8.
Scenario 4: PSK-based Networking for a NodeB Using Separate Encryption

Figure 296-4 Example of PSK-based networking for a NodeB using separate encryption

Issue 06 (2013-03-25)

1002
RAN14.0
The UMTS UMPT provides IPSec for signaling and service data streams on the NodeB,
not for O&M data streams on the NodeB.
l
Issue 06 (2013-03-25)
1.
2.
3.
4.
5.
6.

7.
8.
1.
Run the NodeB MML command DSP IKESA. Check whether IKE SA data is
displayed in the returned result. If IKE SA data is displayed, go to step 2. If IKE SA
data is not displayed, IPSec fails to be activated.
2.
Run the NodeB MML command DSP IPSECSA. Check whether IPSec SA data is
displayed in the returned result. If IPSec SA data is displayed, this feature has been
activated.
3.
Run the NodeB MML command LST ACLRULE to check the ACL rules and
determine whether service data is protected by IPSec tunnels. Check whether the
protected services are running normally. For example, if voice services are protected
by IPSec tunnels, place a call to check whether voice services are still running
normally; if management plane packets are protected by IPSec tunnels, check whether
the corresponding NodeB is still online on the topology view of the M2000.
1003
RAN14.0
1.
Run the NodeB MML command RMV IPSECBIND (CME single configuration:
modification center: not supported) to remove the binding between an IPSec policy
and a port.
2.
Run the NodeB MML command RMV IPSECPOLICY (CME single configuration:
center: not supported) to remove an IPSec policy.
3.
Run the NodeB MML command RMV IPSECPROPOSAL (CME single

batch modification center: not supported) to remove an IPSec proposal.
4.
Run the NodeB MML command RMV ACLRULE (CME single configuration:
modification center: not supported) to remove a rule from an ACL.
5.
Run the NodeB MML command RMV ACL (CME single configuration: NodeB
center: not supported) to remove the ACL.
6.
Run the NodeB MML command RMV IKEPEER (CME single configuration:
not supported) to remove an IKE peer.
7.
Run the NodeB MML command RMV IKEPROPOSAL (CME single configuration:
center: not supported) to remove an IKE proposal.
----End
Example
//Scenario 1: PKI-based Networking for a NodeB Using Unified Encryption
//Adding an IKE proposal
ADD IKEPROPOSAL: PROPID=10, ENCALG=3DES, AUTHALG=MD5,
AUTHMETH=IKE_RSA_SIG, DHGRP=DH_GROUP14, DURATION=86400;
//Adding an IKE peer
ADD IKEPEER: PEERNAME="ike", PROPID=10, IKEVERSION=IKE_V1, EXCHMODE=MAIN,
IDTYPE=IP, REMOTEIP="90.90.90.90", REMOTENAME="secgw", DPD=PERIODIC,
DPDIDLETIME=20, DPDRETRI=4, DPDRETRN=6, LOCALIP="20.20.20.188";
//Adding an ACL
ADD ACL: ACLID=3000, ACLDESC="for IPsec";
//Adding a rule to the ACL
//Adding an IPSec proposal
Issue 06 (2013-03-25)

1004
RAN14.0
ADD IPSECPROPOSAL: PROPNAME="prop0", ENCAPMODE=TUNNEL, TRANMODE=ESP,

ESPAUTHALG=MD5,ESPENCALG=DES;
//Adding an IPSec policy
ADD IPSECPOLICY: SPGN="Policy0", SPSN=1, ACLID=3000, PROPNAME="prop0",
PEERNAME="ike", PFS= DISABLE, LTCFG=LOCAL, LTS=86400,
REPLAYWND=WND_DISABLE;
//Adding the binding between an IPSec policy and a port
ADD IPSECBIND: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=1,
SPGN="Policy0";
//Adding an ACL
SPGN="Policy0";
//Set local IKE configurations
SET IKECFG: IKELNM="IKECFG1", IKEKLI=20, IKEKLT=60, DSCP=48;
ADD IKEPROPOSAL: PROPID=10, ENCALG=3DES, AUTHALG=MD5, AUTHMETH=PRE-SHAREDKEY, DHGRP=DH_GROUP14, PRFALG=AES128_XCBC, DURATION=86400;
IDTYPE=IP, REMOTEIP="90.90.90.90", REMOTENAME="secgw", PKEY="ikekey",
DPD=PERIODIC, DPDIDLETIME=20, DPDRETRI=4, DPDRETRN=6,
LOCALIP="20.20.20.188";
//Adding an ACL
Issue 06 (2013-03-25)

1005
RAN14.0
SPGN="Policy0";
//Scenario 4: PSK-based Networking for a NodeB Using Separate Encryption
LOCALIP="20.20.20.188";
//Adding an ACL
SPGN="Policy0";
DSP IKESA:;
DSP IPSECSA: SN=7, SPGN="Policy0", SPSN=1;
LST ACLRULE:;
RMV IPSECBIND: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1;
RMV IPSECPOLICY: SPGN="Policy0, SPSN=1;
RMV IPSECPROPOSAL: PROPNAME="prop0";
(Optional)RMV ACLRULE: ACLID=3000, RULEID=2;
RMV IKEPEER: PEERNAME="ike";
RMV IKEPROPOSAL: PROPID=10;
Issue 06 (2013-03-25)

1006
RAN14.0
297
Configuring NodeB PKI Support
NodeB PKI Support. (This feature cannot be configured using the CME. )
Prerequisites
l
The 3900 series base stations must be configured with the UTRPc or UMPT board to
support this feature.

License
Other Prerequisites
On a live network, the operator's Certificate Authority (CA) that supports Certificate
Management Protocol version 2 (CMPv2) has been deployed.
An SeGW has been deployed to support IP Security (IPSec) on the RNC side.
The device certificate has been obtained.
Huawei device certificates have been configured for the NodeB.
Context
l
Precautions
Public key infrastructure (PKI) is implemented on the M2000. Therefore, you must run
MML commands on the M2000 to activate PKI.
Data Preparation
Prepare the data related to certificate deployment on the NodeB (the
CERTDEPLOY MO).
Issue 06 (2013-03-25)

1007
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Certification
Deploy Position
Type
DEPLOYTYPE
If a digital
certificate is
deployed on the
main control
board, this
parameter must be
set to DEFAULT
(Default). If a
digital certificate is
deployed on
another board in a
specified slot, this
parameter must be
set to SPECIFIC
(Specific). If no
digital certificate is
deployed on the
NodeB, this
parameter must be
set to NULL
(NULL).
Network plan
Cabinet No.
CN
Subrack No.
SRN
Slot No.
SN
Prepare the data related to the CA server (the CA MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Certificate
Authority Name
CANAME
This parameter is
set based on the
subject of the
operator's CA. For
example, the value
of this parameter is
as follows: C = cn,
S = sh, CN = enbca.
Network plan

1008
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Certificate
Authority URL
URL
Currently, NodeBs
cannot translate
domain names.
Therefore, an IP
address instead of a
domain name is
used in the uniform
resource locator
(URL). The default
TCP port number
is 80 for HTTP
services and 443
for HTTPS
services. For
example, http://
10.121.0.81:80/
pkix is an HTTP
URL.
Signature
Algorithm
SIGNALG
Source
Prepare the data related to the certificate request template (the CERTREQ MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Common Name
COMMNAME
Network plan
Common Name
Additional Info.
USERADDINFO
When automatic
base station
deployment is
used, this
parameter is set
to .huawei.com by
default.
Country
COUNTRY
Organization
ORG
Organizational
Unit
ORGUNIT
State or Province
STATEPROVINC
ENAME
Locality
LOCALITY
Key Usage
KEYUSAGE

1009
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Signature
Algorithm
SIGNALG
The secure hash

algorithm 1
(SHA1) is
recommended for
signing a
certificate request
file.
Key Size
KEYSIZE
Local Name
LOCALNAME
XXX.huawei.com
Source
Here, XXX
indicates the ESN.
Local IP
LOCALIP
The value of this

parameter must be
the same as the
value of Local IP
Address in the
IKEPEER MO.
Prepare the data related to the device certificate (the CERTMK MO).
Issue 06 (2013-03-25)

1010
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Certificate File
Name
APPCERT
l When
automatic base
station
deployment is
used, two
CERTMK
MOs must be
configured to
specify an
operator-issued
device
certificate and a
Huawei-issued
device
certificate. This
parameter must
be set to
OPKIDevCert
.cer for the
operator-issued
device
certificate and
appcert.pem for
the Huaweiissued device
certificate.
Network plan
l When base
station
deployment by
a USB flash
drive is used,
only one
CERTMK
MO can be
configured to
specify a
Huawei-issued
device
certificate. This
parameter is set
to appcert.pem
accordingly.
Users cannot
modify or
remove this
MO.
Prepare the data related to the active certificate.
Issue 06 (2013-03-25)

1011
RAN14.0
The active certificate is the device certificate that is currently used by a NodeB (the
APPCERT MO).
Parameter Name
Parameter ID
Setting
Description
Source
Application Type
APPTYPE
This parameter
must be set to IKE
(IKE).
Network plan
Certificate File
Name
APPCERT
l When
automatic base
station
deployment is
used, this
parameter must
be set to
OPKIDevCert
.cer.
l When PKIbased base
station
deployment by
a USB flash
drive is used,
this parameter
must be set to
appcert.pem.
Prepare the data related to the trust certificate (the TRUSTCERT MO).
Issue 06 (2013-03-25)

1012
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Certificate File
Name
CERTNAME
The NodeB must

be configured with
an operator-issued
trust certificate and
a Huawei-issued
trust certificate.
This parameter is
set to caroot.pem
for the Huaweiissued trust
certificate and is
set to the name of
the operator's root
certificate for the
operator-issued
trust certificate. If
the operator's CA
has multiple
layers, the NodeB
must be configured
with all trust
certificates in the
certificate chain.
Network plan
Prepare the data related to the task of periodically checking certificate validity (the
CERTCHKTSK MO).
Parameter Name
Parameter ID
Setting
Description
Source
Certificate
Validity Period
Checking
ISENABLE
The recommended
value of this
parameter is
ENABLE.
Network plan
Checking Period
PERIOD
The default value

is recommended
for this parameter.
Alarm Threshold
ALMRNG
The default value

is recommended
for this parameter.
Update Method
UPDATEMETHO
D
This parameter
must be set to
CMP.
(Optional) If the NodeB needs to obtain certificate revocation list (CRL) information
from the CA, prepare the data related to the CRL (the CRL MO).
Issue 06 (2013-03-25)

1013
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
CRL File Name
CERTNAME
Network plan
Prepare the data related to the CRL application policy (the CRLPOLICY MO).
Parameter Name
Parameter ID
Setting
Description
Source
CRLPOLICY
CRLPOLICY
The recommended
value of this
parameter is
NOVERIFY,
indicating that the
base station does
not perform CRLbased certificate
validity checks.
Network plan
Prepare the data related to the task of periodically downloading the CRL (the
CRLTSK MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
IP Address
IP
This parameter is
set to the IP
address of the CRL
server.
Network plan
User Name
USR
Password
PWD
File Name
FILENAME
Using CRL's Next

Update
ISCRLTIME
This parameter
specifies whether
to update the CRL
at the next update
time. If this
parameter is set to
ENABLE, the
NodeB downloads
the CRL when the
next update time
arrives.

1014
RAN14.0
Parameter Name
Parameter ID
Setting
Description
CRL Updating
Period
PERIOD
This parameter
must be specified
when
ISCRLTIME is
set to DISABLE.
Access Method
CRLGETMETHO
D
Distinguish Name
SEARCHDN
This parameter
must be specified
when
CRLGETMETH
OD is set to
LDAP.
Task ID
TSKID
Source
Procedure
l
1.
Run the NodeB MML command SET CERTDEPLOY to set the board where a
certificate is to be deployed on the NodeB.
2.
Run the NodeB MML command ADD CA to add the operator's CA server.
3.
Run the NodeB MML command DLD CERTFILE to download an operator's trust
root certificate.
4.
Run the NodeB MML command ADD TRUSTCERT to add an operator's trust
certificate.
5.
Run the NodeB MML command MOD CERTREQ to modify configurations of a

certificate request template.
6.
Run the NodeB MML command REQ DEVCERT to apply for a device certificate
through a CMP session.
7.
Run the NodeB MML command MOD APPCERT to modify configurations of an

active certificate. In this step, set Application Type to IKE(IKE).
8.
Run the NodeB MML command SET CERTCHKTSK to set a task of periodically
checking certificate validity.
9.
Optional: Run the NodeB MML command DLD CERTFILE to download the CRL
file.
10. Optional: Run the NodeB MML command ADD CRL to add a CRL.
11. Optional: Run the NodeB MML command ADD CRLTSK to add a task of
periodically downloading the CRL.
l
1.
Issue 06 (2013-03-25)
Run the NodeB MML command DSP APPCERT. Check the value of Status in the
returned result. If NORMALLY is displayed, the device certificate has been loaded
to the NodeB.
1015
RAN14.0
2.
Run the NodeB MML command DSP TRUSTCERT. Check the value of Status in
the returned result. If NORMALLY is displayed, the trust certificate has been loaded
to the NodeB.
3.
Optional: Run the NodeB MML commandDSP CRL. Check the value of Status in
the returned result. If NORMALLY is displayed, the CRL has been loaded to the
NodeB.
4.
After IPSec policies authenticated by the digital certificate take effect, Run the NodeB
MML commandDSP IKESA. Check the value of SA Flag in the returned result. If
READY is displayed, an IKE SA has been established.
1.
Run the NodeB MML command SET CERTDEPLOY. In this step, set Certification
Deploy Position Type to NULL(NULL).
----End
Example
//Setting the board where a certificate is to be deployed on the NodeB
SET CERTDEPLOY: DEPLOYTYPE=SPECIFIC, CN=0, SRN=0, SN=7;
//Adding the operator's CA server
ADD CA: CANAME="C=AU, S=Some-State, O=Internet Widgits Pty Ltd, CN=eca1",
URL="http://88.88.88.88:80/pkix/";
//Downloading the operator's trust root certificate
DLD CERTFILE:
IP="60.60.60.60",USR="admin",PWD="*****",SRCF="OperationCA.cer",DSTF="Ope
rationCA.cer";
//Adding an operator's trust certificate
ADD TRUSTCERT: CERTNAME="OperationCA.cer";
//Modifying configurations of a certificate request template
MOD CERTREQ: COMMNAME=ESN, USERADDINFO=".huawei.com", COUNTRY="CN",
ORG="ITEF", ORGUNIT="Hw", STATEPROVINCENAME="sc", LOCALITY="cd",
KEYUSAGE=DATA_ENCIPHERMENT-1&DIGITAL_SIGNATURE-1&KEY_AGREEMENT-1&KEY_ENCI
PHERMENT_1, SIGNALG=SHA1, KEYSIZE=KEYSIZE1024,
LOCALNAME="abcdefghijklmn.huawei.com", LOCALIP="20.20.20.188";
//Starting the CMP session to apply for a device certificate
REQ DEVCERT: CANAME="C=AU, S=Some-State, O=Internet Widgits Pty Ltd,
CN=eca1", APPCERT="OPKIDevCert.cer";
//Adding the active certificate
MOD APPCERT: APPTYPE=IKE, APPCERT="OPKIDevCert.cer";
//Setting a task of periodically checking certificate validity
SET CERTCHKTSK: ISENABLE=ENABLE, PERIOD=7, ALMRNG=30, UPDATEMETHOD=CMP;
//(Optional)Downloading a CRL file to a base station
DLD CERTFILE:
IP="60.60.60.60",USR="admin",PWD="*****",SRCF="NodeB.crl",DSTF="NodeB.crl
";
//(Optional)Adding a CRL
ADD CRL: CERTNAME="NodeB.crl";
Issue 06 (2013-03-25)

1016
RAN14.0
//(Optional) Adding a task of periodically downloading the CRL

ADD CRLTSK: IP="86.86.86.86", USR="admin", PWD="*****",
FILENAME="NodeB.crl", ISCRLTIME=DISABLE, TSKID=0, CRLGETMETHOD=FTP;
DSP APPCERT: APPTYPE=IKE;
DSP TRUSTCERT: CERTNAME="OperationCA.cer";
DSP CRL: CERTNAME="NodeB.crl";
DSP IKESA: CN=0, SRN=0, SN=4, IKEVSN=IKE_V1;
SET CERTDEPLOY: DEPLOYTYPE=null;
Issue 06 (2013-03-25)

1017
RAN14.0
298
Configuring Intelligent Battery

Management
Intelligent Battery Management. (This feature cannot be configured using the CME. )
Prerequisites
l
The APM30H (Ver. C), BTS3900AL, TP48600A, and batteries must be configured.

License
Others
In a base station newly updated to RAN14.0 or later, update the PMU software version
to version corresponding to R14.0 or later and then activate the PMU software. In
addition, ensure that the PMU software version can work with the software version of
the base station.
In a new base station, activating the PMU software is not required because the PMU
software version delivered with the software version of the base station has been up to
date.
Context
The intelligent power management feature has the following functions: automatic switch
between the charge and discharge modes, self-protection under high temperature, and battery
runtime display. This feature enables the base station to prolong the battery lifespan by battery
self-protection, and therefore increase profits of operators by reducing operating expenses.
l
Precautions
Check the local grip type. If the grid type is 1 or 2, it is recommended that the function
of automatic switch between the charge and discharge modes be enabled.
Issue 06 (2013-03-25)

1018
RAN14.0
Check the ambient temperature of the base stations and determine the policies and
parameters for battery self-protection under high temperature.
l
Data Preparation
Paramet
er Name
Parame
ter ID
Description
Data Source
Battery
Intelligen
t
Manage
ment
Swtich
BATIM
S
Whether to activate Intelligent Battery

Management. This switch takes effect
only when the license controlling this
feature has been obtained.
Data plan
High
Temperat
ure
Shutdow
n Flag
HTSDF
Whether to power off batteries under

high temperature. When this parameter
is set to ENABLE, batteries are
powered off. When this parameter is
set to DISABLE, the base station
lowers the battery charging voltage. It
is recommended that this parameter be
set to ENABLE under high
temperature.
Data plan
Shutdow
n
Temperat
ure
SDT
Temperature threshold for powering

off batteries or decreasing the battery
charging voltage. The default value
53C is recommended for this
parameter.
Data plan
If the battery temperature exceeds this

threshold for 5 minutes, the power
monitoring unit (PMU) performs
either of the following operations to
prolong the battery lifespan: powering
off batteries when HTSDF is set to
ENABLE, or decreasing the battery
charging voltage to 50.5 V when
HTSDF is set to DISABLE.
Temperat
ure Alarm
Upper
Threshol
d
Issue 06 (2013-03-25)
TUTHD
Threshold for reporting the

ALM-25654 Battery Temperature
Unacceptable. If the battery
temperature exceeds this threshold for
5 minutes, the ALM-25654 Battery
Temperature Unacceptable is
generated. If the battery temperature
decreases to a temperature 5 degree
lower than this threshold for 5 minutes,
batteries enter the floating charge state
and no alarms are generated. The
default value 50C is recommended for
this parameter.

Data plan
1019
RAN14.0
Procedure
l
1.
(Optional) Activate the PMU software: Run the NodeB MML command ACT
SOFTWARE to activate the PMU software. Run the NodeB MML command DSP
BRDVER to query the PMU software version and ensure the version has been
upgraded to version corresponding to R14.0 or later.
2.
Run the NodeB MML command SET EQUIPMENT. In this step, set Battery
Intelligent Management Swtich to ON.
3.
Run the NodeB MML command ADD BATTERY or MOD BATTERY. In this step,
set High Temperature Shutdown Flag to ENABLE, Shutdown Temperature to
53, and Temperature Alarm Upper Threshold to 50.
1.
Intelligent Battery Management: Run the NodeB MML command DSP PMU to check
the values of Battery Intelligent Management Capability and Battery Intelligent
Management Mode.
Expected result: The value of Battery Intelligent Management Capability is
Support, and the value of Battery Intelligent Management Mode is ENABLE.
2.
Self-Protection Under High Temperature: Run the NodeB MML command LST
BATTERY to check the values High Temperature Shutdown Flag, Shutdown
Temperature, and Temperature Alarm Upper Threshold.
Expected result: The value of High Temperature Shutdown Flag is ENABLE. The
value of Shutdown Temperature is 53. The value of Temperature Alarm Upper
Threshold is 50.
3.
l
Battery Runtime Display: Run the NodeB MML command DSP BATTERY to check
the value of Remaining Time to get the battery leftover capacity.
1.
Run the NodeB MML command SET EQUIPMENT. In this step, set Battery
Intelligent Management Swtich to OFF.
----End
Example
//Activating BIMS
SET EQUIPMENT: BATIMS=ON;
//Setting HTSDF, SDT, and TUTHD
ADD BATTERY: HTSDF=ENABLE, SDT=53, TUTHD=50;
//Deactivating BATIMS
SET EQUIPMENT: BATIMS=OFF;
Issue 06 (2013-03-25)

1020
RAN14.0
299 Configuring Multi-mode Dynamic Power Sharing

(UMTS)
299
Configuring Multi-mode Dynamic

Power Sharing (UMTS)
Multi-mode Dynamic Power Sharing (UMTS).
Prerequisites
l
Only the MRFU and the MRRU supports GSM and UMTS Dynamic Power Sharing at
present.

This feature can't be activated with WRFD-010684 22 MIMO or WRFD-010693 DL
64QAM+MIMO simultaneously.
This feature has to be activated with MRFD-211801 Multi-mode Dynamic Power
Sharing (GSM) simultaneously.
License
Other Prerequisites
The UMTS cell must exist HSDPA Carry.
Context
In the case of a 3900 series multi-mode base station, the GSM and UMTS TRXs can share one
power amplifier. When there is unbalanced traffic in the GSM and the UMTS, the power can be
used more efficiently in an effective way, namely, sharing the power amplifier. The overall
network quality of the GSM and the UMTS is therefore improved.
Issue 06 (2013-03-25)

1021
RAN14.0

(UMTS)
NOTE
l The feature may fail to recall the shared power in one second when the GSM services increase suddenly.
As a result, internal GSM peak clipping occurs, which affects service quality.
l Enabling the feature may cause the UMTS coverage to shrink and therefore increase the drop rate. The
problem can be addressed by handing over services in marginal coverage to a GSM/UMTS cell under
the same coverage as the original UMTS.
l The switch and other parameter configurations are performed only on the GSM side. The UMTS side
requires no configuration.
Procedure
l
1.
Run the BSC6900 MML command SET BTSGUPWRSHRFP (CME single

configuration: BTS Configuration Express > BTS Power > BTS GU Dynamic
Power Sharing Parameters; CME batch modification center: not supported). In this
step, set Board Parameter Configuration Enabled to YES(YES) and set the period
for enabling GU power sharing.
2.
Run the BSC6900 MML command SET BTSRXUBP (CME single configuration:
BTS Device Panel > RXU Topology > Right click RXU Board > RXU Board
Porperties > RUX board Parameters; CME batch modification center: not
supported). In this step, setRXU Board Type to MRRU(MRRU) or MRFU
(MRFU), set GU Dynamic Power Sharing Switchto YES(YES), and set parameters
Minimum Number of Non-BCCH TRXs in GSM for GU Power Sharing, GSM
Power Load Threshold for GU Power Sharing, Number of Checked Timeslots
for Retrieving Shared Power, Num of Timeslots Meet Requirements for
Retrieving Shared Pwr, GSM Power Reserve Coefficient for Retrieving Shared
Power, GSM Idle Channel Threshold for GU Power Sharing, GSM Idle Channel
Hysteresis for GU Power Sharing, GSM Power Reserve in Low Load for GU
Power Sharing, GSM Power Reserve in High Load for GU Power Sharing,
Maximum Accumulated Shared Power That UMTS Can Accept, Maximum
Shared Power That UMTS Can Accept In Each Period to actual conditions.
3.
Batches), set GU Power Share Flag to TRUE(TRUE).
1.
Run the BSC6900 MML command LST BTSGUPWRSHRFP and LST

BTSRXUBP and check the returned message.
Exception result: Board Parameter Configuration Enabled and GU Dynamic
Power Sharing Switch are YES.
2.
Run the NodeB MML command LST LOCELL, and check the returned message.
Exception result: GU Power Share Flag is YES.
Issue 06 (2013-03-25)
1.
Batches), set GU Power Share Flag to FALSE(FALSE).
2.
Run the BSC6900 MML command SET BTSGUPWRSHRFP (CME single

configuration: BTS Configuration Express > BTS Power > BTS GU Dynamic
1022
RAN14.0

(UMTS)
Power Sharing Parameters; CME batch modification center: not supported). In this
step, set Board Parameter Configuration Enabled to NO(NO).
3.
Run the BSC6900 MML command SET BTSRXUBP (CME single configuration:
BTS Device Panel > RXU Topology > Right click RXU Board > RXU Board
Porperties > RUX board Parameters; CME batch modification center: not
supported). In this step, set GU Dynamic Power Sharing Switch to NO(NO).
NOTE
GSM and UMTS Dynamic Power Sharing can be deactivated by performing either of the two
steps discussed above.
----End
Example
SET BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, CFGFLAG=YES,
GUPWRSHARESTM1=07&00, GUPWRSHAREETM1=09&00, GUPWRSHARESTM2=10&00,
GUPWRSHAREETM2=12&00, GUPWRSHARESTM3=14&00, GUPWRSHAREETM3=16&00,
GUPWRSHARESTM4=20&00, GUPWRSHAREETM4=22&00;
SET BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0,
RXUTYPE=MRFU, GUPWRSHARESWITCH=YES,
GUPWRSHARETRXNUM=1, GUPWRSHAREPWRLOAD=80, GUPWRSHAREN=8, GUPWRSHAREP=6,
GUPWRSHARERSVFACTOR=50, GUPWRSHAREGSMIDLETH=12,
GUPWRSHAREGSMIDLEHS=2, GUPWRSHAREGSMIDLERSVPWR=5,
GUPWRSHAREGSMBUSYRSVPWR=10, GUPWRSHAREURCVPWR=15, GUPWRSHAREURCVPWRPD=5;
MOD LOCELL: LOCELL=0, SECT=LOCAL_SECTOR, GUPOWERSHARE=TRUE;
LST BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, LSTFORMAT=VERTICAL;
LST BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0,
LSTFORMAT=VERTICAL;
SET BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, CFGFLAG=NO;
SET BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0,
RXUTYPE=MRFU, GUPWRSHARESWITCH=NO;
MOD LOCELL: LOCELL=0, SECT=LOCAL_SECTOR, GUPOWERSHARE=FALSE;
Issue 06 (2013-03-25)

1023
RAN14.0
300 Configuring GSM and UMTS Dynamic Spectrum

Sharing (UMTS)
300
Configuring GSM and UMTS
Dynamic Spectrum Sharing (UMTS)
GSM and UMTS Dynamic Spectrum Sharing (UMTS). This feature enables the spectrum
resources to be dynamically shared between the GSM and UMTS networks based on their traffic
load, improving frequency utilization.
Prerequisites
l
The 900 MHz MRFU and MRRU must support this feature.
GSM and UMTS sharing the same MRFU/MRRU.

On the dynamic spectrum shared carrier, this feature can not be activated with
MRFD-211703 2.0MHz Central Frequency point separation between GSM and UMTS
mode(GSM), MRFD-221703 2.0MHz Central Frequency point separation between
GSM and UMTS mode(UMTS) simultaneously
This feature can not be activated with GBFD-117001 Flex MAIO simultaneously.
This feature has to be activated with MRFD-211802 GSM and UMTS Dynamic
Spectrum Sharing (GSM) simultaneously.
License
Start Dynamic Spectrum Sharing on the M2000 by referring to the M2000 Online Help.
Other Prerequisites
A specific M2000 V200R011 version that matches SRAN6.0 is required to support this
feature.
GSM and UMTS sharing the same MRFU/MRRU.
Context
The dynamic spectrum sharing (DSS) between GSM and UMTS increases network throughput
and reduces the total cost of data services because UMTS has higher spectral efficiency than
Issue 06 (2013-03-25)

1024
RAN14.0

Sharing (UMTS)
GSM. In theory, the maximum throughput gain is about 50%. After this feature is used, the total
cost of ownership (TCO) of mobile broadband (MBB) can be reduced, and dynamic GSM/
UMTS refarming can be implemented. Thus, the maintenance cost of manual refarming is
reduced.
Procedure
l
1.
Issue 06 (2013-03-25)

a.
Run the BSC6900 MML command MOD UNODEB (CME single

Information > NodeB; CME batch modification center: not supported) with
DSS NodeB Flag set to TRUE.
b.

modification center: not supported) to set up a DSS cell, set DSS Cell Flag to
TRUE, and set Maximum TX Power in Small DSS Coverage and PCPICH
TX Power in Small DSS Coverage based on network conditions.
c.
Run the BSC6900 MML command MOD UCELLACCESSSTRICT (CME

> Cell Access Restriction Information; CME batch modification center: 3.18
Modifying UMTS Cell Parameters in Batches) with both Cell barred
indicator for SIB3 and Cell barred indicator for SIB4 of DSS cells set to
BARRED.
d.

configuration: UMTS Cell Configuration Express > Neighboring Cell >
Inter-frequency Neighboring Cell; CME batch modification center: not
supported) to add the neighbor 3G cells of DSS cells as inter-frequency
neighboring cells, and set Blind Handover Flag to TRUE and
DrdOrLdrFlag to TRUE.
e.

Neighboring Cell; CME batch modification center: not supported) to add the
neighboring GSM cells for DSS cells, and set Blind Handover Flag to TRUE.
f.

Neighboring Cell; CME batch modification center: not supported) to add the
neighboring DSS cells as intra-frequency neighboring cells.
g.

Parameters in Batches) with both DRD switch for single RAB and
HO_INTER_FREQ_HARD_HO_SWITCH set to ON.
h.
Run the BSC6900 MML command SET UDRD (CME single configuration:
UMTS Radio Global Configuration Express > Directed Retry Parameter
modification center: 3.15 Modifying RNC Parameters in Batches) with Load
balance DRD switch for HSDPA set to ON and Load Balancing DRD
Choice set to UserNumber.
1025
RAN14.0

Sharing (UMTS)
2.
i.
Run the BSC6900 MML command ADD UCELLDRD (CME single

Modifying UMTS Cell Parameters in Batches) with Load balance DRD
switch for HSDPA set to ON and Load Balancing DRD Choice set to
UserNumber.
j.
Run the BSC6900 MML command ACT UCELL (CME single configuration:
Information. Set Validation indication to Activated; CME batch modification
center: 3.18 Modifying UMTS Cell Parameters in Batches) to activate the cell.

Parameters in Batches) to add local DSS cells, and set GU Power Share Flag
to FALSE.
3.

a.
Run the BSC6900 MML command ADD GEXT3GCELL (CME single

configuration: Object Group > GSM Service Configuration and
Maintenance Management > External Cell Configuration > BSC 3G
External Cell; CME batch modification center: Modifying BSC External Cell
Parameters in Batches) to add 3G external cells.
b.
Run the BSC6900 MML command ADD G3GNCELL (CME single

configuration: Cell Configuration Express > Neighboring Cell > BSC 3G
Neighbor Cell; CME batch modification center: not supported) to add 3G
neighboring cells.
c.
Run the BSC6900 MML command SET GDSSPARA (CME single

configuration: BTS Configuration Express > BTS Basic Attributes > BTS
Spectrum Sharing Parameters; CME batch modification center: not supported)
with Spectrum Sharing Allowed set to YES(Yes).
d.
Run the BSC6900 MML command SET GTRXDEV (CME single

configuration: TRX Configuration Express > Site TRX Dev Property > Site
TRX Dev Property; CME batch modification center: Modifying GSM TRX
Parameters in Batches) with Spectrum Sharing Shutdown Allowed set to YES
(Yes).
CAUTION
The parameter Spectrum Sharing Shutdown Allowed for all TRXs to be shared
under a base station should be set to YES(Yes) except for the BCCH TRX.
l
1.
Start spectrum sharing on the M2000 manually.
2.
Run the BSC6900 MML command DSP UNODEB to query the DSS status of a
NodeB.
Expected result: The value of NodeB DSS state is Actived in Normal DSS
coverage.
Issue 06 (2013-03-25)

1026
RAN14.0

Sharing (UMTS)
3.
Run the BSC6900 MML command DSP UCELL to query the DSS status of a cell.
Expected result: The value of DSS state is Actived in Normal DSS coverage.
4.
Run the NodeB MML command LST LOCELL to check the value of GU Power
Share Flag.
Expected result: The value of GU Power Share Flag is TRUE.
5.
Run the BSC6900 MML command DSP BTSSTAT to query the value of Dynamic
Spectrum Sharing. Expected result: The value of Dynamic Spectrum Sharing is
Yes.
1.
Stop Dynamic Spectrum Sharing on the M2000 by referring to the M2000 Online
Help.
2.
NodeB; CME batch modification center: not supported) with DSS NodeB Flag set to
FALSE.
3.
Run the BSC6900 MML command SET GDSSPARA (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS Spectrum Sharing
Parameters; CME batch modification center: not supported) with Spectrum Sharing
Allowed set to NO(No).
4.
Run the BSC6900 MML command SET GTRXDEV (CME single configuration:
TRX Configuration Express > Site TRX Dev Property > Site TRX Dev
Property; CME batch modification center: Modifying GSM TRX Parameters in
Batches) with Spectrum Sharing Shutdown Allowed set to NO(No).
5.
Remove the neighboring cell by referring to Reconfiguration Guide.
6.
Modifying UMTS Cell Parameters in Batches) to deactivate a cell.
----End
Example
MOD UNODEB: NodeBId=1, DSSFlag=TRUE;
ADD UCELLQUICKSETUP: CellId=102, CellName="dss102", PeerIsValid=INVALID,
URA1=0, NodeBName="102", LoCell=102, SupBmc=FALSE, DSSFlag=TRUE,
DSSSmallCovMaxTxPower=431, DSSSmallCovPCPICHPower=331;
MOD UCELLACCESSSTRICT: CellId=102, IdleCellBarred=BARRED,
IdleIntraFreqReselection=ALLOWED, IdleTbarred=D320,
ConnCellBarred=BARRED, ConnIntraFreqReselection=ALLOWED,
ConnTbarred=D320;
ADD U2GNCELL: RNCId=2, CellId=102, GSMCellIndex=120, BlindHoFlag=TRUE,
NPrioFlag=FALSE;
ADD UINTRAFREQNCELL: RNCId=0, CellId=102, NCellRncId=3, NCellId=121,
SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1,
HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1;
Issue 06 (2013-03-25)

1027
RAN14.0

Sharing (UMTS)
SET UDRD: LdbDRDSwitchHSDPA=ON, LdbDRDchoice=UserNumber;

ADD UCELLDRD: CellId=120, LdbDRDSwitchHSDPA=ON,
ReDirBandInd=DependOnNCell;
ADD LOCELL: LOCELL=102, STN=1, SECN=0, GUPOWERSHARE=FALSE;
ADD GEXT3GCELL: EXT3GCELLID=120, EXT3GCELLNAME="120", MCC="460",
MNC="10", LAC=10, CI=60, RNCID=0, DF=412, SCRAMBLE=0, DIVERSITY=NO,
UTRANCELLTYPE=TDD, SYNCCASE=SyncCase1;
ADD G3GNCELL: IDTYPE=BYID, SRC3GNCELLID=102, NBR3GNCELLID=120;
SET GDSSPARA: IDTYPE=BYID, BTSID=102, DSSENABLE=YES;
SET GTRXDEV: TRXID=1002, DSSTRXOFFLINE=YES;
SET GTRXDEV: TRXID=1003, DSSTRXOFFLINE=YES;
MOD UNODEB: NodeBId=1, DSSFlag=FALSE;
SET GDSSPARA: IDTYPE=BYID, BTSID=102, DSSENABLE=NO;
HO UCELL: CellId=102, CellChoice=ALLCELL;
RMV UNRELATION: RNCId=0, CellId=102,
NCellType=IntraFreqNCell&InterFreqNCell&InterRatNCell;
Issue 06 (2013-03-25)

1028
RAN14.0
301
301 Configuring IP-Based Multi-Mode Co-Transmission on

Base Station Side (NodeB)
Configuring IP-Based Multi-Mode
Co-Transmission on Base Station Side (NodeB)

IP-Based Multi-Mode Co-Transmission on Base Station Side. For details about data
configurations, see section Configuration Reference > MBTS Configuration Reference
(V100R007C00) > Common Transmission in the 3900 Series Base Station Initial
Configuration Guide, or see section Common Transmission in the WCDMA RAN Feature
Documentation. The latest 3900 Series Base Station Initial Configuration Guide can be obtained
from the following path: HUAWEI Technical Support (support.huawei.com), Support >
Documentation > SingleRAN > MBTS > SingleRAN7.0.
Issue 06 (2013-03-25)

1029
RAN14.0
302 Configuring TDM-Based Multi-mode Co-Transmission

via Backplane on BS side (NodeB)
302
Configuring TDM-Based Multi-
mode Co-Transmission via Backplane on BS side

(NodeB)
TDM-Based Multi-mode Co-Transmission via Backplane on BS side (NodeB). (This feature
Prerequisites
l
A GSM and UMTS dual-mode base station supports this feature.
When the TDM timeslot cross connection co-transmission feature is supported by a
GSM and UMTS dual-mode base station, a UTRP should be configured for the BTS.
The UTRP type must be UTRP3, UTRP4, or UTRPb4.

WRFD-050302 Fractional ATM Function on Iub Interface
WRFD-050411 Fractional IP Function on Iub Interface
License
Context
This feature enables the BTS and NodeB to share E1/T1 transmission resources through a
backplane clock channel with the effective TDM timeslot cross connection function.
Backplane-based co-transmission is classified into the following scenarios:
l
Issue 06 (2013-03-25)
In the scenario of GTMU-based TDM timeslot cross connection co-transmission, E1/T1

timeslots on the UMTS side are transmitted to the GTMU through the backplane TOP
channel on the WMPT. E1/T1 ports on the GTMU are connected to the transmission
network. The TDM timeslot cross connection function enables GSM data and UMTS data
to be multiplexed on the transmission network. Therefore, E1/T1 transmission resources
are shared by the GSM and UMTS modes by timeslot, as shown in Figure 302-1.

1030
RAN14.0

Figure 302-1 GTMU-based TDM timeslot cross connection co-transmission
In the scenario of GSM-UTRP-based TDM timeslot cross connection co-transmission, a

UTRP is configured on the GSM side. Therefore, extra E1/T1 resources can be shared by
the UMTS mode through the backplane TOP channel to extend E1/T1 transmission
resources for the UMTS mode, as shown in Figure 302-2.
NOTE
l The number of E1/T1 on the BTS backplane is within the range of 16 through 19. E1/T1 numbers 16 through
19 on the BTS backplane correspond to E1/T1 numbers 0 through 3 on the NodeB backplane. Cross
connection is not supported. For example, E1/T1 No. 16 on the BTS backplane only corresponds to E1/T1
No. 0 on the NodeB backplane.
l E1 timeslot numbers configured on the BTS side must be consistent with those configured on the NodeB
side.
Figure 302-2 GSM-UTRP-based TDM timeslot cross connection co-transmission
Procedure
l
Activating the BTS data (GTMU-based)

1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command ADD BTSCONNECT to add a connection

between a GTMU port and the NodeB. Set Dest Node Type (select Connect to
BSC on the CME) to OTHER.
1031
RAN14.0

2.
Run the BSC6900 MML command ADD BTSTOPCONFIG to configure the TOP
switching parameters.
Set Port Subrack No. and Port Slot No. to numbers of the subrack and slot where
the BTS port connected to the NodeB interface board is located. Set TOP Board
Subrack No. and TOP Board Slot No. to numbers of the subrack and slot where
the NodeB interface board is located.
Set Port Type to TOPEXTOUTPORT.
Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
Activating the NodeB data (GTMU-based)

1.
Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link.
Set Subrack No. and Slot No. to numbers of the subrack and slot that house the
Iub interface board.
Set Subboard Type to BACK_BOARD.
Set Destination Slot No. to the number of the slot that houses the GTMU.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It,
however, does not support the configuration of the operating work mode and loopback mode, and
online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual
networking mode.
2.
Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step,
set Subboard Type to BASE_BOARD.
3.
Run the NodeB MML command ADD IMALNK to add an IMA link and then add it
to the MP group. In this step, set Subboard Type to BACK_BOARD or
BASE_BOARD.
4.
Run the NodeB MML command ADD SAALLNK to add an SAAL link.
Set Subboard Type to BASE_BOARD.
Set Rate Unit to KBPS or CELL/S. Only one rate unit can be used. Therefore,
rate units in other configuration must be consistent.
5.
Run the NodeB MML command ADD AAL2NODE to add an AAL2 node.
Set Node Type to LOCAL(LOCAL).
Set ATM Address to a valid ATM address. The recommended value is
H'3900000000000000000000000000000000000000.
6.
Run the NodeB MML command ADD AAL2PATH to add an AAL2 path.
Set Node Type to LOCAL(End Node).
Issue 06 (2013-03-25)
7.
Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set
NCP/CCP Port Type to NCP(NCP Port).
8.
Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP(CCP Port).
1032
RAN14.0

NOTE
Before a CCP link is added, the number of the CCP port must be the same as that of the CCP port
on the BSC6900 side. To query information about the CCP link on the BSC6900 side, run the
BSC6900 MML command LST UIUBCP.
Activating the BTS data (GSM-UTRP-based)

1.
Run the BSC6900 MML command ADD BTSCONNECT to add a connection

between a UTRP port and the NodeB. Set Dest Node Type (select Connect to BSC
on the CME) to OTHER.
2.
Run the BSC6900 MML command ADD BTSTOPCONFIG to configure the TOP
switching parameters.
Set Port Type to TOPEXTOUTPORT.
Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
Activating the NodeB data (GSM-UTRP-based)

1.
Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link.
Set Cabinet No., Subrack No., and Slot No. to the numbers of the cabinet,
subrack, and slot that house the Iub interface board.
Set Subboard Type to BACK_BOARD.
Set Destination Slot No. to the number of the slot that houses the UTRP.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It,
however, does not support the configuration of the operating work mode and loopback mode, and
online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual
networking mode.
2.
Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step,
set Subboard Type to BASE_BOARD.
3.
Run the NodeB MML command ADD IMALNK to add an IMA link and then add it
to the MP group. In this step, set Subboard Type to BACK_BOARD or
BASE_BOARD.
4.
Run the NodeB MML command ADD SAALLNK to add an SAAL link.
5.
Run the NodeB MML command ADD AAL2NODE to add an AAL2 node.
Set Node Type to LOCAL(LOCAL).
Set ATM Address to a valid ATM address. The recommended value is
H'3900000000000000000000000000000000000000.
6.
Run the NodeB MML command ADD AAL2PATH to add an AAL2 path.
Set Node Type to LOCAL(End Node).
Issue 06 (2013-03-25)

1033
RAN14.0

7.
Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set
NCP/CCP Port Type to NCP.
8.
Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP.
NOTE
Before a CCP link is added, the number of the CCP port must be the same as that of the CCP port
on the BSC6900 side. To query information about the CCP link on the BSC6900 side, run the
BSC6900 MML command LST UIUBCP.
----End
Example
//Activating the BTS data (GTMU-based)
//Configuring a connection between a GTMU port and the NodeB
ADD BTSCONNECT: IDTYPE=BYID, BTSID=255, INPN=1, INCN=0, INSRN=0, INSN=6,
DESTNODE=OTHER;
//Configuring the TOP switching relation between the GTMU and the WMPT:
E1 port 16 on the backplane corresponds to port 0 on the WMPT, the GTMU
provides the WMPT with a transmission path, the port type is TOPEXTINPO,
and the output port is E1 port 1 on the GTMU
ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=6,
E1T1PORTNO=16, TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7,
PORTTYPE=TOPEXTOUTPORT, ORIPORT=1,
TSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS111&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&T
S22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
//Activating the NodeB data (GTMU-based)
//Adding a backplane E1/T1 link
ADD BACKE1T1: SRN=0, SN=7, SBT=BACK_BOARD, DSTSN=6;
//Adding an IMA group
ADD IMAGRP: SRN=0, SN=7, SBT=BASE_BOARD;
//Adding an IMA link
ADD IMALNK: SRN=0, SN=7, SBT=BACK_BOARD, IMAGRPSBT=BASE_BOARD;
//Adding three SAAL links
ADD SAALLNK: SAALNO=4, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA,
JNRSCGRP=DISABLE, VPI=0, VCI=32, RU=KBPS, ST=CBR, PCR=1024;
//Adding an AAL2 node
ADD AAL2NODE: NT=LOCAL, LN=4,
ADDR="H'3900000000000000000000000000000000001980";
ADD AAL2PATH: NT=LOCAL, PATHID=23, CN=0, SRN=0, SN=7, SBT=BASE_BOARD,
PT=IMA, JNRSCGRP=DISABLE, VPI=4, VCI=36, RU=KBPS, ST=RTVBR, PCR=1024,
SCR=512, RCR=512;
//Adding an NCP or CCP link
ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5;
ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6;
//Activating the BTS data (GSM-UTRP-based)
//Configuring a connection between a UTRP port and the NodeB
ADD BTSCONNECT: IDTYPE=BYID, BTSID=255, INPN=1, INCN=0, INSRN=0, INSN=0,
DESTNODE=OTHER;
//Configuring the TOP switching relation between the UTRP and the WMPT:
E1 port 16 on the backplane corresponds to port 0 on the WMPT, the UTRP
provides the WMPT with a transmission path, the port type is TOPEXTINPO,
and the output port is E1 port 1 on the UTRP
Issue 06 (2013-03-25)

1034
RAN14.0

ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=0,

E1T1PORTNO=16, TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7,
PORTTYPE=TOPEXTOUTPORT, ORIPORT=1,
TSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS111&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&T
S22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
Activating the NodeB data (GSM-UTRP-based)
//Adding a backplane E1/T1 link
ADD BACKE1T1: SRN=0, SN=7, SBT=BACK_BOARD, DSTSN=0;
//Adding an IMA group
ADD IMAGRP: SRN=0, SN=7, SBT=BASE_BOARD;
//Adding an IMA link
ADD IMALNK: SRN=0, SN=7, SBT=BACK_BOARD, IMAGRPSBT=BASE_BOARD;
//Adding three SAAL links
//Adding an AAL2 node
ADD AAL2NODE: NT=LOCAL, LN=4,
ADDR="H'3900000000000000000000000000000000001980";
ADD AAL2PATH: NT=LOCAL, PATHID=23, CN=0, SRN=0, SN=7, SBT=BASE_BOARD,
PT=IMA, JNRSCGRP=DISABLE, VPI=4, VCI=36, RU=KBPS, ST=RTVBR, PCR=1024,
SCR=512, RCR=512;
//Adding an NCP or CCP link
ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5;
ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6;
Issue 06 (2013-03-25)

1035
RAN14.0
303 Configuring Multi-Mode BS Common Reference Clock

(NodeB)
303
Configuring Multi-Mode BS
Common Reference Clock (NodeB)
Multi-Mode BS Common Reference Clock (NodeB). For details about data configurations, see
section Configuration Reference > MBTS Configuration Reference (V100R007C00) >
Common Clock in the 3900 Series Base Station Initial Configuration Guide, or see section
Common Clock in the WCDMA RAN Feature Documentation. The latest 3900 Series Base
Station Initial Configuration Guide can be obtained from the following path: HUAWEI
Technical Support (support.huawei.com), Support > Documentation > SingleRAN > MBTS
> SingleRAN7.0.
Issue 06 (2013-03-25)

1036
RAN14.0
304
Multi-mode BS Common IPSec

(UMTS)
MRFD-221602 Multi-mode BS Common IPSec(UMTS).
Prerequisites
l

UMPT or UTRPc
Dependencies on other features

MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side (NodeB).
One mode of multi-mode shall support IPSec feature (GBFD-113524 BTS Integrated
IPsec, WRFD-140209 NodeB Integrated IPSec, LOFD-003009 IPsec).
This feature must be used together with one of features MRFD-211602 Multi-mode BS
Common IPSec (GSM) and MRFD-231602 Multi-mode BS Common IPSec (LTE), or
both.
License
Context
IPSec Networking of an MBTS
l
IPSec networking for a GU, GL, and UL dual-mode base station: IPSec-related data on the
UTRPc board is configured by the mode with the highest priority. During secure base
station deployment, all security-related configuration data is configured by the mode with
a higher priority. The mode with a lower priority does not participate in secure base station
deployment.
IPSec networking for a GUL triple-mode base station:

GU+L (BBU interconnection): IPSec is implemented on the LMPT board, and the
UTRPc board forwards the LTE service data and processes UMTS and GSM IPSec
data. IPSec-related data on the UTRPc board is configured by the mode with a higher
Issue 06 (2013-03-25)

1037
RAN14.0
priority. If digital certificates are used for identity authentication, the LMPT and UTRPc
boards use their respective digital certificates to authenticate with the SeGW.
GU+L (BBU interconnection): IPSec is implemented on the UMPT board, and the
UTRPc board forwards the UMTS service data and processes LTE and GSM IPSec
data. IPSec-related data on the UTRPc board is configured by the mode with a higher
priority. If digital certificates are used for identity authentication, the UMPT and UTRPc
boards use their respective digital certificates to authenticate with the SeGW.
In other BBU interconnection scenarios: The UTRPc board performs IPSec-related
processing. IPSec-related data on the UTRPc board is configured by the mode with a
higher priority. If digital certificates are used for identity authentication, the UTRPc
board uses its digital certificate to authenticate with SeGW, and the three mode of the
base station share the same IPSec tunnels and digital certificate.
l
Data Preparation
Prepare the data required for the IKE proposal (the IKEPROPOSAL MO).
Parameter Name
Parameter ID
Setting
Description
Source
Proposal ID
PROPID
User-defined
Encryption
Algorithm
ENCALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
Authentication
Algorithm
AUTHALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
Authentication
Method
AUTHMETH
If digital
certificates are
used for identity
parameter must be
set to
IKE_RSA_SIG
(RSA Digital
Certificate
Signature).
identity
parameter must be
set to
PRE_SHARED_
KEY(Pre-shared
Key).
Issue 06 (2013-03-25)

1038
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Diffie-Hellman
Group
DHGRP
The parameter
setting on the base
station and SeGW
sides must be the
same.
PRF Algorith
PRFALG
This parameter
must be specified
when Version in
the IKEPEER MO
is set to IKE_V2
(IKE V2). The
default value is
recommended.
ISAKMP SA
Duration(s)
DURATION
The parameter
setting on the base
station and SeGW
sides must be the
same.
Source
Prepare the data required for the IKE peer (the IKEPEER MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
IKE Peer Name
PEERNAME
User-defined
IKE Proposal ID
PROPID
The value of this

parameter must be
the same as the
value of Proposal
ID in the
IKEPROPOSAL
MO.
Version
IKEVERSION
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)
Exchange Mode
EXCHMODE
This parameter
must be specified
when Version is
set to IKE_V1
(IKE V1). The
parameter setting
on the base station
and SeGW sides
must be the same.
Network plan
(negotiation with
the IPSec peer)

1039
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Local ID Type
IDTYPE
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)
Remote IP Address
REMOTEIP
If ENCAPMODE
in the
IPSECPROPOS
AL MO is set to
TRANSPORT,
the value of this
parameter must be
the same as that of
DIP in the
ACLRULE MO.
Otherwise,
encrypted packets
cannot be
decrypted.
Network plan
When
Encapsulation
Mode in the
IPSECPROPOS
AL MO is set to
TUNNEL
(Tunnel), the
value of this
parameter must be
the same as the IP
address of the peer
security gateway
and the
subjectaltname
field of the local
certificate.
Issue 06 (2013-03-25)

1040
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Remote Name
REMOTENAME
The value of this

parameter must be
the same as the
IKE name
configured at the
IKE peer (for
example, the
SeGW).
Network plan
l If a PSK is used
for
authentication,
the value of this
parameter must
be the same as
that of Local
NAME of the
IKE peer.
l If digital
certificates are
used for
authentication,
the
subjectaltname
fields in the
certificates
used by the
local and peer
ends must be
set to the same
value.
Pre-shared Key
PKEY
If digital
Network plan
certificates are
(negotiation with
used for identity
the IPSec peer)
parameter does not
need to be
configured.
identity
parameter must be
specified and the
parameter value
must be the same
as that of the IKE
peer.
Issue 06 (2013-03-25)

1041
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
DPD Mode
DPD
Network plan
DPD Idle Time(s)
DPDIDLETIME
DPD
Retransmission
Interval(s)
DPDRETRI
DPD
Retransmission
Count
DPDRETRN
DPD is enabled by
default. It is
recommended that
the values of DPDrelated parameters
be the same at both
IKE ends. If the
values are
different, the IKE
SA end with a
shorter timer
length will detect
that the peer is
offline before the
other IKE SA end
does and an IKE
re-negotiation will
be triggered.
Local IP Address
LOCALIP
When Version is
set to IKE_V1
(IKE V1) and
Local ID Type is
set to IP(IP
Identify), the
value of this
parameter must be
the same as the port
ID bound to the
IPSec.
Network plan
Prepare the data required for the ACL rule (the ACL MO).
One or multiple ACLs need to be configured based on the planned IPSec tunnels. In the
IPSECPOLICY MO, an IPSec policy is bound to an ACL based on the ACLID setting.
Only data streams that comply with ACL rules are processed according to the operations
defined in the IPSec policy.
Parameter Name
Parameter ID
Setting
Description
Source
ACL ID
ACLID
An ACL must
contain at least one
ACL rule.
Network plan
If an ACL is bound
to an IPSec policy,
the value of this
parameter ranges
from 3000 to 3999.
Issue 06 (2013-03-25)

1042
RAN14.0
Prepare the data required for the ACL rule (the ACLRULE MO).
Depending on the network plan, an IPSec tunnel may require multiple ACL rules to
protect different types of data streams.
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
ACL ID
ACLID
The value of this

parameter must be
the same as that of
ACL ID in the
ACL MO.
Network plan
Rule ID
RULEID
Each ACL rule in

an ACL must have
a unique ID.
Protocol Type
PT
Source IP Address
SIP
If ENCAPMODE
in the
IPSECPROPOS
AL MO is set to
TRANSPORT,
the value of this
parameter must be
an existing device
IP address.
Otherwise,
encrypted packets
cannot be
decrypted.
Source Wildcard
SWC
Match Source Port
SMPT
This parameter and

the Match
Fragment
Messageparamete
r cannot be set to
YES
simultaneously.
Source Port
Operate
SOP
Source Port 1
SPT1
Source Port 2
SPT2

1043
RAN14.0
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Destination IP
Address
DIP
If ENCAPMODE
in the
IPSECPROPOS
AL MO is set to
TRANSPORT,
the value of this
parameter must be
a host IP address.
The value of this
parameter must be
the same as that of
REMOTEIP in
the IKEPEER
MO. Otherwise,
encrypted packets
cannot be
decrypted.
Destination
Wildcard
DWC
Match Destination
Port
DMPT
This parameter and

the Match
Fragment
Messageparamete
r cannot be set to
YES
simultaneously.
Destination Port
Operate
DOP
Destination Port 1
DPT1
Destination Port 2
DPT2
Match DSCP
MDSCP
DSCP
DSCP
Match Fragment
Message
MFRG
VLAN ID Operate
VLANIDOP
If an ACL is bound
to an IPSec policy,
this parameter does
not need to be
configured.

Source
1044
RAN14.0
Parameter Name
Parameter ID
Setting
Description
VLAN ID 1
VLANID1
If an ACL is bound
to an IPSec policy,
this parameter does
not need to be
configured.
VLAN ID 2
VLANID2
If an ACL is bound
to an IPSec policy,
this parameter does
not need to be
configured.
Source
Prepare the data required for the IPSec proposal (the IPSECPROPOSAL MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
IPSec Proposal
Name
PROPNAME
User-defined
Encapsulation
Mode
ENCAPMODE
The tunnel mode is

recommended.
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)
Transform
TRANMODE
The parameter
setting on the base
station and SeGW
sides must be the
same.
AH Authentication
Algorithm
AHAUTHALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
ESP
Authentication
Algorithm
ESPAUTHALG
The parameter
setting on the base
station and SeGW
sides must be the
same.
ESP Encryption
Algorithm
ESPENCALG
The parameter
setting on the base
station and SeGW
sides must be the
same.

1045
RAN14.0
Prepare the data required for the IPSec policy (the IPSECPOLICY MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Policy Group
Name
SPGN
User-defined
IPSec Sequence
No.
SPSN
User-defined
ACL ID
ACLID
An IPSec policy is
bound to an ACL
by using the ACL
IDparameter. Only
data streams that
comply with the
ACL are processed
according to the
operations defined
in the IPSec policy.
User-defined
IPsec Proposal
Name
PROPNAME
The value of this

parameter must be
the same as the
value of IPSec
Proposal Namein
the
IPSECPROPOS
AL MO.
User-defined
IKE Peer Name
PEERNAME
The value of this

parameter must be
the same as the
value of IKE Peer
Name in the
IKEPEER MO.
User-defined
Perfect Forward
Secrecy
PFS
The parameter
setting on the base
station and SeGW
sides must be the
same.
Network plan
(negotiation with
the IPSec peer)

1046
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Lefttime Config
LTCFG
set to GLOBAL,
the IPSec SA
lifetime is
permanently set to
3600 seconds. If
this parameter is
set to LOCAL, the
IPSec SA lifetime
is specified by
LTS and LTKB.
Network plan
Lifetime Based On
Time(s)
LTS
This parameter
needs to be
specified when
LTCFG is set to
LOCAL.
Network plan
Lifetime Based On
Traffic(KB)
LTKB
This parameter
needs to be
specified when
LTCFG is set to
LOCAL.
Network plan
Anti-Replay
Windows
REPLAYWND
set to 0, the antireplay function
does not take
effect.
Network plan
Prepare the data required for binding an IPSec policy group to a port (the
IPSECBIND MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Cabinet No.
CN
Network plan
Subrack No.
SRN
Slot No.
SN
Subboard Type
SBT
Port Type
PT
Port No.
PN
If PT is set to ETH,
the port specified
by PN must not be
a member of an
Ethernet trunk.

1047
RAN14.0
Parameter Name
Parameter ID
Setting
Description
Source
Policy Group
Name
SPGN
The value of this

parameter must be
the same as the
value of Policy
Group Namein
the
IPSECPOLICY
MO.
User-defined
If a PSK is used for authentication, prepare the IKE configuration data (the IKECFG
MO).
Issue 06 (2013-03-25)
Parameter Name
Parameter ID
Setting
Description
Source
Local Name
IKELNM
This parameter
must be specified
when Local ID
Typeis set to
FQDN(Name
Identify). The
value of this
parameter must be
the same as the
IKE peer name
configured at the
SeGW.
Network plan
Keepalive Interval
IKEKLI
Keepalive
Timeout
IKEKLT
These two
parameters need to
be specified when
the keepalive
function is
required by IKEv1
entities. If
Keepalive
Timeout or
Keepalive
Interval is set to 0,
the keepalive
function is
disabled. The
value of Keepalive
Timeout must be
greater than that of
Keepalive
Interval.

1048
RAN14.0
Parameter Name
Parameter ID
Setting
Description
DSCP
DSCP
This parameter
specifies the
differentiated
services code point
(DSCP) for IKE
negotiation
packets. The
recommended
value of this
parameter is 48.
Source
Procedure
l
Scenario 1: PKI-based Networking for a NodeB Using Unified Encryption
Figure 304-1 Example of PKI-based networking for a NodeB using unified encryption

The UMTS UMPT provides IPSec for the following data streams:
Signaling, service, and O&M data streams on the NodeB
Issue 06 (2013-03-25)
1.
2.
1049
RAN14.0
3.
4.
5.

6.
7.

Figure 304-2 Example of PKI-based networking for a NodeB using separate encryption

The UMTS UMPT does not provide IPSec for O&M data streams on the NodeB. It
provides IPSec for the following data streams:
Signaling and service data streams on the NodeB
1.
Issue 06 (2013-03-25)
1050
RAN14.0
2.
3.
4.
5.

6.
7.

Figure 304-3 Example of PSK-based networking for a NodeB using unified encryption

The UMTS UMPT provides IPSec for signaling, service, and O&M data streams on the
NodeB.
1.
Issue 06 (2013-03-25)
1051
RAN14.0
2.
3.
4.
5.
6.

7.
8.
Scenario 4: PSK-based Networking for a NodeB Using Separate Encryption

Figure 304-4 Example of PSK-based networking for a NodeB using separate encryption

Issue 06 (2013-03-25)

1052
RAN14.0
The UMTS UMPT provides IPSec for signaling and service data streams on the NodeB,
not for O&M data streams on the NodeB.
l
Issue 06 (2013-03-25)
1.
2.
3.
4.
5.
6.

7.
8.
1.
Run the NodeB MML command DSP IKESA. Check whether IKE SA data is
displayed in the returned result. If IKE SA data is displayed, go to step 2. If IKE SA
data is not displayed, IPSec fails to be activated.
2.
Run the NodeB MML command DSP IPSECSA. Check whether IPSec SA data is
displayed in the returned result. If IPSec SA data is displayed, this feature has been
activated.
3.
Run the NodeB MML command LST ACLRULE to check the ACL rules and
determine whether service data is protected by IPSec tunnels. Check whether the
protected services are running normally. For example, if voice services are protected
by IPSec tunnels, place a call to check whether voice services are still running
normally; if management plane packets are protected by IPSec tunnels, check whether
the corresponding NodeB is still online on the topology view of the M2000.
1053
RAN14.0
1.
Run the NodeB MML command RMV IPSECBIND (CME single configuration:
modification center: not supported) to remove the binding between an IPSec policy
and a port.
2.
Run the NodeB MML command RMV IPSECPOLICY (CME single configuration:
center: not supported) to remove an IPSec policy.
3.
Run the NodeB MML command RMV IPSECPROPOSAL (CME single

batch modification center: not supported) to remove an IPSec proposal.
4.
Run the NodeB MML command RMV ACLRULE (CME single configuration:
modification center: not supported) to remove a rule from an ACL.
5.
Run the NodeB MML command RMV ACL (CME single configuration: NodeB
center: not supported) to remove the ACL.
6.
Run the NodeB MML command RMV IKEPEER (CME single configuration:
not supported) to remove an IKE peer.
7.
Run the NodeB MML command RMV IKEPROPOSAL (CME single configuration:
center: not supported) to remove an IKE proposal.
----End
Example
//Scenario 1: PKI-based Networking for a NodeB Using Unified Encryption
//Adding an ACL
Issue 06 (2013-03-25)

1054
RAN14.0

SPGN="Policy0";
//Adding an ACL
SPGN="Policy0";
LOCALIP="20.20.20.188";
//Adding an ACL
Issue 06 (2013-03-25)

1055
RAN14.0
SPGN="Policy0";
//Scenario 4: PSK-based Networking for a NodeB Using Separate Encryption
LOCALIP="20.20.20.188";
//Adding an ACL
SPGN="Policy0";
DSP IKESA:;
DSP IPSECSA: SN=7, SPGN="Policy0", SPSN=1;
LST ACLRULE:;
RMV IPSECBIND: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1;
RMV IPSECPOLICY: SPGN="Policy0, SPSN=1;
RMV IPSECPROPOSAL: PROPNAME="prop0";
RMV IKEPEER: PEERNAME="ike";
RMV IKEPROPOSAL: PROPID=10;
Issue 06 (2013-03-25)

1056
RAN14.0
305 Configuring 2.0MHz Central Frequency point separation

between GSM and UMTS mode(UMTS)
305
Configuring 2.0MHz Central
Frequency point separation between GSM and

UMTS mode(UMTS)
2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS).
Prerequisites
l
MRFU and RRU3908 of V2 or later versions support the feature.
UMTS:900M MRRU, 900M MRFU (excluding V1), 850M MRRU V2.

GBFD-114801 Discontinuous Transmission (DTX) Downlink
GBFD-117601 HUAWEI III Power Control Algorithm
GBFD-117602 Active Power Control
MRFD-211703 2.0 MHz Central Frequency Point Separation Between GSM and UMTS
Mode (GSM)
License
Other Prerequisites
GSM and UMTS Dynamic Power Sharing is not supported in GSM dynamic transmit
diversity.
It is not recommended that GSM and UMTS Dynamic Power Sharing coexist with the
baseband frequency hopping algorithm involving two power amplifiers because their
coexistence would result in a certain level of performance loss.
GSM and UMTS Dynamic Power Sharing in MIMO is not recommended.
It needs to purchase professional service additionally to minimize the KPI losses.
Issue 06 (2013-03-25)

1057
RAN14.0

Context
This feature improves frequency utilization. It enables the UMTS carriers to use the bandwidth
3.8 MHz and therefore increase the capacity of the GSM network.
Procedure
l
1.
modification center: not supported) to set the minimal frequency bandwidth on the
UMTS side. In this step, set Frequency Min Bandwidth to 3800.
2.
To ensure that the UMTS carrier bandwidth is 3.8 MHz and the frequency spacing
between GSM and UMTS carriers is 2.0 MHz, as set in step 1, do as follows to modify
frequency points on the GSM or UMTS side:
Modify the UMTS carrier Central Frequency Point
a.
Run the BSC6900 MML command DEA UCELL (CME single

configuration: UMTS Cell Configuration Express > Cell Basic
Information > Cell Basic Information. Set Validation indication to
Parameters in Batches) to deactivate a cell.
b.

Information > Cell Basic Information; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches). In this step, modify
frequency points for UMTS cells at the BSC6900. Set Band Indicator, UL
Frequency Ind, Uplink UARFCN and Downlink UARFCN.
c.
Run the NodeB MML command MOD LOCELL (CME single

configuration: NodeB Configuration Express > IUB_NodeB > Radio
Layer > xx Sector > Locell; CME batch modification center: 3.17 Modifying
Physical NodeB Parameters in Batches) to modify some properties of a
local cell. In this step, set UL Frequency Channel Number and DL
Frequency Channel Number.
d.
Run the BSC6900 MML command ACT UCELL (CME single

Activated; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to activate a cell.
Modify the GSM central frequency point separation

a.
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command MOD GTRX (CME single configuration:
BTS Topology > Right click Cell > Configure TRX Frequency; CME
batch modification center: not supported) to modify the frequency of a TRX.
In this step, set Frequency to ensure that the frequency spacing between GSM
and UMTS carriers is 2.0 MHz.
Run the NodeB MML command LST FREQBWH to check whether the UMTS
carrier bandwidth is 3.8 MHz.
1058
RAN14.0

2.
Check on the NodeB side whether all TRXs work properly when the frequency spacing
between GSM and UMTS carriers is 2.0 MHz.
3.
Check on the BSC side whether services in all cells are normal when the frequency
spacing between GSM and UMTS carriers is 2.0 MHz.
1.
modification center: not supported) to set the UMTS carrier bandwidth. The UMTS
carrier bandwidth should range from 4.2 MHz to 5.0 MHz.
2.
To ensure that the UMTS carrier bandwidth is the bandwidth set in step 1, do as follows
to modify frequency points on the GSM or UMTS side:
Modify the UMTS central frequency point separation
a.
Run the BSC6900 MML command DEA UCELL (CME single

Parameters in Batches) to deactivate a cell.
b.

Information > Cell Basic Information; CME batch modification center:
3.18 Modifying UMTS Cell Parameters in Batches). In this step, modify
frequency points for UMTS cells at the BSC6900 and set Band Indicator,
UL Frequency Ind and Downlink UARFCN.
c.
Run the NodeB MML command MOD LOCELL (CME single

configuration: NodeB Configuration Express > IUB_NodeB > Radio
Layer > xx Sector > Locell; CME batch modification center: 3.17 Modifying
Physical NodeB Parameters in Batches) to modify some properties of a
local cell. In this step, set UL Frequency Channel Number and DL
Frequency Channel Number.
d.
Run the BSC6900 MML command ACT UCELL (CME single

Activated; CME batch modification center: 3.18 Modifying UMTS Cell
Parameters in Batches) to activate a cell.
Modify the GSM central frequency point separation

a.
Run the BSC6900 MML command MOD GTRX (CME single configuration:
BTS Topology > Right click Cell > Configure TRX Frequency; CME
batch modification center: not supported) to modify the frequency of a TRX.
In this step, set Frequency to ensure that the frequency spacing between GSM
and UMTS carriers no less than 2.2 MHz.
----End
Example
//Setting the UMTS carrier bandwidth to 3.8 MHz
//Setting the uplink and downlink frequencies of a UMTS cell to 2815 and
Issue 06 (2013-03-25)

1059
RAN14.0

3040
MOD UCELLSETUP: CellId=101, BandInd=Band8, UARFCNUplinkInd=FALSE,
UARFCNDownlink=3040;
MOD LOCELL: LOCELL=101, SECT=LOCAL_SECTOR, ULFREQ=2815, DLFREQ=3040;
//Setting the frequency of a specified GSM TRX to 55
MOD GTRX: TRXID=122, FREQ=55;
LST FREQBWH: CN=0, SRN=4, SN=0;
//Setting the UMTS carrier bandwidth to 5.0 MHz
//Setting the uplink and downlink frequencies of a UMTS cell to 2821 and
3046
MOD UCELLSETUP: CellId=101, BandInd=Band8, UARFCNUplinkInd=FALSE,
UARFCNDownlink=3046;
MOD LOCELL: LOCELL=101, SECT=LOCAL_SECTOR, ULFREQ=2821, DLFREQ=3046;
//Setting the frequency of a specificed GSM TRX to 52
MOD GTRX: TRXID=122, FREQ=52;
Issue 06 (2013-03-25)

1060
RAN14.0
306 Configuring Dynamic MA for GU Dynamic Spectrum

Sharing (UMTS)
306
Configuring Dynamic MA for GU
Dynamic Spectrum Sharing (UMTS)
MRFD-221803 Dynamic MA for GU Dynamic Spectrum Sharing(UMTS).
Prerequisites
l

MRFD-221802 GSM and UMTS Dynamic Spectrum Sharing(UMTS).
This feature cannot be used together with MRFD-211703 2.0MHz Central Frequency
point separation between GSM and UMTS mode(GSM) and MRFD-221703 2.0MHz
Central Frequency point separation between GSM and UMTS mode(UMTS).
The feature must be used together with the feature MRFD-211803 Dynamic MA for
GU Dynamic Spectrum Sharing (GSM).
License
Requirements for the Operating Environment

The M2000 is of the V200R011 version.
A common M2000 configuration is required.
Context
After this feature is activated, the BSC starts spectrum sharing when the traffic volume of a cell
is lighter than what can be carried on two or three TRXs, increasing the spectrum sharing time.
Operators are advised to enable this feature in the scenario where the GSM and UMTS Dynamic
Spectrum Sharing feature is enabled.
l
Precautions
After this feature is activated, dynamically changing an absolute radio frequency
channel number (ARFCN) of a cell leads to cell reset.
This feature affects the following algorithms:
Issue 06 (2013-03-25)

1061
RAN14.0

Sharing (UMTS)
Handover algorithm: During dynamic MA changing, the BSC performs an intra-cell

handover on MSs in the GSM cell.
Admission algorithm: During dynamic MA changing, the BSC preferentially
allocates timeslots with new MA to new MSs.
l
Data Preparation
Paramet
er Name
Parame
ter ID
Description
Data Source
FH Index
Used
After
Frequenc
y
Spectrum
Sharing
TRXDS
SHOPIN
DEX
FH index of channels after spectrum

sharing
Network planning
MAIO
Used
After
Frequenc
y
Spectrum
Sharing
TRXDS
SMAIO
MAIO of channels after spectrum

sharing
Network planning
Procedure
l
1.
Run the BSC6900 MML command ADD GCELLMAGRP (CME single

configuration: BTS Topology > Cell > Configure MA Group; CME batch
modification center: not supported) to add the mobile allocations (MAs) before and
after dynamic spectrum sharing is enabled.
2.
Run the BSC6900 MML command SET GTRXCHANHOP (CME single

modification center: not supported). In this step, set FH Index Used After Frequency
Spectrum Sharing and MAIO Used After Frequency Spectrum Sharing for the
channels in the cell.
1.
Check that this feature has taken effect by viewing the value of the Number of dynamic
MA changing requests counter.
1.
Run the BSC6900 MML command SET GTRXCHANHOP (CME single

modification center: not supported). In this step, set FH Index Used After Frequency
Spectrum Sharing to 255.
----End
Example
//GSM and UMTS Dynamic Spectrum Sharing must have been configured before
Issue 06 (2013-03-25)

1062
RAN14.0

Sharing (UMTS)

//Setting the cell frequency hopping (FH) group
ADD GCELLMAGRP: IDTYPE=BYID, CELLID=100, HOPINDEX=1, HSN=0, TSC=0,
HOPMODE=1, FREQ1=802, FREQ2=804, FREQ3=806, FREQ4=808;
HOPMODE=1, FREQ1=802, FREQ2=804;
HOPMODE=1, FREQ1=806, FREQ2=808;
//Setting the FH groups for a channel
SET GTRXCHANHOP: TRXID=1001, CHNO=0, TRXHOPINDEX=1, TRXMAIO=0,
IDTYPE=BYID, TRXDSSHOPINDEX=2, TRXDSSMAIO=0;
Issue 06 (2013-03-25)

1063
RAN14.0
307 Configuring GSM Power Control on Interface Frequency

for GU Small Frequency Gap (UMTS)
307
Configuring GSM Power Control on
Interface Frequency for GU Small Frequency

Gap (UMTS)
MRFD-221804 GSM Power Control on Interference Frequency for GU Small Frequency gap
(UMTS).
Prerequisites
l
Requirements on Hardware
Only 3900 series base stations support this feature.

The feature GBFD-113701 Frequency Hopping (RF hopping, baseband hopping) has
been configured before this feature is activated.
MRFD-221703 2.0MHz Central Frequency point separation between GSM and UMTS
mode (UMTS) or WRFD-021001 Flexible frequency bandwidth of UMTS.
The feature must be used together with MRFD-211804 GSM Power Control on
Interference Frequency for GU Small Frequency gap (GSM).
License
Context
This feature is recommended for the GU refarming 3.8 MHz or 4.2 MHz scenario where the
number of FH TCH frequencies is greater than or equal to 6.
l
Precautions
The interfering frequencies must join in FH.
Operators are not advised to enable this feature together with the feature MRFD-211801
Multi-mode Dynamic Power Sharing(GSM) or MRFD-221801 Multi-mode Dynamic
Power Sharing(UMTS).
Issue 06 (2013-03-25)

1064
RAN14.0

This feature affects the following features: GBFD-117002 IBCA (Interference Based
Channel Allocation), GBFD-118106 Dynamic Power Sharing, GBFD-113201
Concentric Cell, GBFD-115507 WB AMR, and GBFD-115830 VAMOS.
l
Data Preparation
When this feature is used together with the feature 2.0MHz Central Frequency point
separation between GSM and UMTS mode, operators only need to prepare the data for
the feature 2.0MHz Central Frequency point separation between GSM and UMTS
mode.
When this feature is used together with the function GU Refarming 4.2 MHz of the
Flexible Frequency Bandwidth of UMTS Carrier feature, the data for this feature is the
same as the data for the function GU Refarming 4.2 MHz.
The following table describes the parameters that are specific to this feature.
Issue 06 (2013-03-25)
Paramet
er Name
Parame
ter ID
Description
Data Source
Cell
Index
CELLI
D
Cell in which frequency-based power

control is enabled
Network planning
Frequenc
y-based
Power
Control
GUDegr
atePwrC
trl
Whether to enable frequency-based

power control.
Network planning
Interfere
nce
Coordina
tion
Policy
GUDegr
atePwrP
ri
Frequency-based power control

policy. If this parameter is set to GSM
(GSM), this feature preferentially
guarantees the GSM network quality
while minimizing interference to the
UMTS network. If this parameter is
set to UMTS(UMTS), this feature
preferentially guarantees the UMTS
network quality. The specific setting
depends on customers' requirements.
Network planning

1065
RAN14.0
Issue 06 (2013-03-25)

Paramet
er Name
Parame
ter ID
Description
Data Source
GU2.0
MHz
Max.
Power
Decrease
for
Interferin
g
Frequenc
y
GU2000
KHzMa
xVal
Maximum power decrease for the

interfering frequency when there is a
2.0 MHz frequency spacing between
the GSM and UMTS networks. The
expected transmit power of the
interfering frequency can be
calculated with the following
formula: Expected transmit power of
the interfering frequency =
Maximum TRX transmit power GU2.0 MHz Max. Power Decrease
for Interfering Frequency. The larger
the parameter value, the lower the
interfering frequency is, and the more
GSM users are affected in terms of
service quality. In this case, if this
parameter is set to UMTS(UMTS),
the UMTS network has more
performance gains; if this parameter
is set to GSM(GSM), the GSM users
on which power compression is
performed are more closer to the cell
center.
Network planning
GU2.2
MHz
Max.
Power
Decrease
for
Interferin
g
Frequenc
y
GU2200
KHzMa
xVal
Maximum power decrease for the

interfering frequency when there is a
2.2 MHz frequency spacing between
the GSM and UMTS networks. The
interfering frequency can be
calculated with the following
formula: Expected transmit power of
the interfering frequency =
Maximum TRX transmit power GU2.2 MHz Max. Power Decrease
for Interfering Frequency. The larger
the parameter value, the lower the
interfering frequency is, and the more
GSM users are affected in terms of
service quality. In this case, if this
parameter is set to UMTS(UMTS),
the UMTS network has more
performance gains; if this parameter
is set to GSM(GSM), the GSM users
on which power compression is
performed are more closer to the cell
center.
Network planning

1066
RAN14.0
Issue 06 (2013-03-25)

Paramet
er Name
Parame
ter ID
Description
Data Source
UMTS
Center
Frequenc
y1
UMTSF
reqNum
1
Downlink absolute radio frequency

channel number (ARFCN) for the
first UMTS frequency that has a 2.0
MHz or 2.2 MHz spacing with the
GSM frequency in GU refarming
scenarios. When one UMTS
frequency is deployed in GU
refarming scenarios, one ARFCN is
configured. When multiple UMTS
frequencies are deployed in GU
refarming scenarios, multiple
ARFCNs are configured. Currently,
a maximum of two such ARFCNs
can be configured.
Network planning
UMTS
Center
Frequenc
y2
UMTSF
reqNum
2
Downlink ARFCN for the second

UMTS frequency that has a 2.0 MHz
or 2.2 MHz spacing with the GSM
frequency in GU refarming
scenarios. The value of this
parameter ranges from 0 to 1023.
When one UMTS frequency is
deployed in GU refarming scenarios,
one ARFCN is configured. When
multiple UMTS frequencies are
deployed in GU refarming scenarios,
multiple ARFCNs are configured.
Currently, a maximum of two such
ARFCNs can be configured.
Network planning
NonAHR
Power
Compens
ation
Proportio
n
NAHR
CompC
oeff
Proportion of power compensation

for the non-interfering frequencies to
power decrease each time the
transmit power of the interfering
frequency is decreased by 1 dB for
enhanced full rate (EFR), full rate
(FR), half rate (HR), and adaptive
multirate (AMR) FR calls. Increasing
the value of this parameter increases
the power compensation amplitude.
Network planning

1067
RAN14.0

Paramet
er Name
Parame
ter ID
Description
Data Source
NonAHR
Power
Compens
ation
Offset
NAHR
CompO
ffVal
Power compensation offset for EFR,

FR, HR, and AMR FR calls. Power
decrease amplitude that requires
power compensation =
NAHRCompOffVal/
NAHRCompCoeff. When
NAHRCompCoeff is set to 0, this
parameter does not need to be
configured. When this parameter is
set to a smaller value, the power
decrease amplitude that does not
require power compensation
increases.
Network planning
AHR
Power
Compens
ation
Proportio
n
AHRCo
mpCoef
f
Proportion of power compensation

for the non-interfering frequencies to
power decrease each time the
transmit power of the interfering
frequency is decreased by 1 dB for
AMR HR calls. Increasing the value
of this parameter increases the power
compensation amplitude.
Network planning
AHR
Power
Compens
ation
Offset
AHRCo
mpOffV
al
Power compensation offset for AMR

HR calls. Power decrease amplitude
that requires power compensation =
AHRCompOffVal/
AHRCompCoeff. When
AHRCompCoeff is set to 0, this
parameter does not need to be
configured. When this parameter is
set to a smaller value, the power
decrease amplitude that does not
require power compensation
increases.
Network planning
Procedure
l
1.
Issue 06 (2013-03-25)
Run the BSC6900 MML command SET GCELLNONSTANDARDBW (CME

single configuration: Cell Configuration Express > Power Control > GSM/UMTS
Small Frequency Spacing Interference Control Parameters; CME batch
modification center: Modifying GSM Cell Parameters in Batches). In this step, set
Frequency-based Power Control to ON and set the other parameters to appropriate
values. The other parameters are Cell Index, Interference Coordination Policy,
GU2.0 MHz Max. Power Decrease for Interfering Frequency, GU2.2 MHz Max.
Power Decrease for Interfering Frequency, UMTS Center Frequency 1, UMTS
Center Frequency 2, Non-AHR Power Compensation Proportion, Non-AHR

1068
RAN14.0

Power Compensation Offset, AHR Power Compensation Proportion, and AHR

Power Compensation Offset.
l
1.
When this feature is used together with the feature 2.0MHz Central Frequency point
separation between GSM and UMTS mode, the procedure used to verify this feature
is the same as that used to verify the feature 2.0MHz Central Frequency point
separation between GSM and UMTS mode.
2.
When this feature is used together with the GU Refarming 4.2 MHz function of the
Flexible Frequency Bandwidth of UMTS Carrier feature, the procedure used to verify
this feature is the same as that used to verify the Flexible Frequency Bandwidth of
UMTS Carrier feature.
3.
Run the NodeB MML command DSP LICENSE to query whether the license
controlling this feature has been activated.
4.
Run the BSC6900 MML command LST GCELLNONSTANDARDBW to query

whether Frequency-based Power Control is set to ON and whether Cell Index is
set to the index of the cell where this feature is to be enabled.
5.
Check the values of the counters in the following table.

Counter ID
Counter Name
Description
1282449360
CELL.
2MDISTURB.AVG.FAL
L.POWER.RANGE
Average Power Decrease

on GSM 2.0 MHz
Interfering Frequency
1282449361
CELL.
2.2MDISTURB.AVG.F
ALL.POWER.RANGE
Average Power Decrease

on GSM 2.2 MHz
Interfering Frequency
1282449362
CELL.UNDISTURB.AV
G.UP.POWER.RANGE
Average Power Increase

on GSM Non-Interfering
Frequency
1.
Run the BSC6900 MML command SET GCELLNONSTANDARDBW (CME

single configuration: Cell Configuration Express > Power Control > GSM/UMTS
Small Frequency Spacing Interference Control Parameters; CME batch
modification center: Modifying GSM Cell Parameters in Batches). In this step, set
Frequency-based Power Control to OFF.
----End
Example
SET GCELLNONSTANDARDBW: IDTYPE=BYID, CELLID=2, GUDegratePwrCtrl=ON,
GUDegratePwrPri=GSM, GU2000KHzMaxVal=10, GU2200KHzMaxVal=3,
UMTSFreqNum1=0, UMTSFreqNum2=0, NAHRCompCoeff=5, NAHRCompOffVal=-15,
AHRCompCoeff=5, AHRCompOffVal=-15;
SET GCELLNONSTANDARDBW: IDTYPE=BYID, CELLID=2, GUDegratePwrCtrl=OFF;
Issue 06 (2013-03-25)

1069

RAN14.0 Feature Activation Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RAN14.0 Feature Activation Guide

Загружено:

Авторское право:

Доступные форматы

RAN14.

Feature Activation Guide

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Technical support engineers

Network optimization engineers

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

12 Configuring 2-Way Antenna Receive Diversity

Huawei Proprietary and Confidential

About This Document

24 Configuring Admission Control

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

49 Configuring Link Aggregation

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

85 Configuring MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

110 Configuring TTI Switch for BE Services Based on Coverage

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

147 Configuring HSPA+ Downlink 28Mbps per User

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

172 Configuring Flexible HSPA+ Technology Selection

Huawei Proprietary and Confidential

About This Document

184 Configuring Multi-Carrier Switch off Based on QoS

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

209 Configuring IP Transmission Introduction on Iu Interface

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

234 Configuring High Speed Access

Huawei Proprietary and Confidential

About This Document