RAN Re Configuration Guide (V900R012C01 - 03)

RAN V900R012C01
Reconfiguration Guide
Issue Date 03 2010-09-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 03 (2010-09-20)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
RAN Reconfiguration Guide
About This Document
About This Document

Purpose
This document describes how to reconfigure the BSC6900 during network optimization and how to configure the optional features.
Product Versions
The following table lists the product version related to this document. Product Name BSC6900 NodeB NodeB Product Version V900R012C01 V100R012 V200R012
Intended Audience
This document is intended for: l l l l Technical support engineers Maintenance engineers Field engineers Network optimization engineers
Organization
1 Changes in the RAN Reconfiguration Guide This chapter describes the changes in the RAN Reconfiguration Guide. 2 Introduction to Reconfiguration This chapter defines reconfiguration and describes the reconfiguration tools. 3 Checking the License
Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
About This Document
This chapter describes how to check the newly granted license. 4 Reconfiguring the BSC6900 This chapter describes how to reconfigure the running BSC6900 or expand its capacity. 5 Adjusting the NodeB This chapter describes how to adjust or expand the operational NodeB. 6 Reconfiguring the UMTS Network This chapter describes how to carry out common network reconfiguring tasks in the functioning BSC6900. 7 Configuring UMTS Features This chapter describes how to configure the features of the BSC6900 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 of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected 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. Convention Times New Roman Boldface Italic
iv
Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-09-20)
About This Document
Convention Courier New
Description 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 Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. 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. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description 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. Format Key
Issue 03 (2010-09-20)
Description Press the key. For example, press Enter and press Tab.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
About This Document
Format Key 1+Key 2 Key 1, Key 2
Description Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. 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. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
vi
Issue 03 (2010-09-20)
Contents
Contents
About This Document...................................................................................................................iii 1 Changes in the RAN Reconfiguration Guide.......................................................................1-1 2 Introduction to Reconfiguration.............................................................................................2-1
2.1 Definition........................................................................................................................................................2-2 2.2 Tools................................................................................................................................................................2-2
3 Checking the License.................................................................................................................3-1 4 Reconfiguring the BSC6900......................................................................................................4-1

4.1 Changing Signaling Points..............................................................................................................................4-2 4.2 Configuring Link Stability Control for BE.....................................................................................................4-2 4.3 Changing the Work Mode of a Board.............................................................................................................4-7 4.4 Adding Boards and Subracks..........................................................................................................................4-8 4.4.1 Adding a Subrack...................................................................................................................................4-8 4.4.2 Adding the SPUa/SPUb Board ............................................................................................................4-12 4.4.3 Adding the DPUb/DPUe Board...........................................................................................................4-14 4.4.4 Adding Interface Boards......................................................................................................................4-16 4.5 Removing Boards and Subracks...................................................................................................................4-18 4.5.1 Removing the SPUa/SPUb Board........................................................................................................4-18 4.5.2 Removing the DPUb/DPUe Board.......................................................................................................4-25 4.5.3 Removing Subracks..............................................................................................................................4-26
5 Adjusting the NodeB.................................................................................................................5-1

5.1 Modifying the NodeB Clock Source or the Clock Working Mode.................................................................5-2 5.2 Modifying NodeB Time Information..............................................................................................................5-2 5.3 Adding the Board/Equipment to the NodeB...................................................................................................5-3 5.3.1 Adding the Board to the BTS3812E/BTS3812AE.................................................................................5-3 5.3.2 Adding the BBU3806/BBU3806C Equipment......................................................................................5-4 5.3.3 Adding the EBBC/EBBCd Board..........................................................................................................5-5 5.3.4 Adding the EBBM Board.......................................................................................................................5-6 5.3.5 Adding the Board to 3900 Series Base Stations.....................................................................................5-6 5.4 Configuring a Custom NodeB Alarm..............................................................................................................5-7
6 Reconfiguring the UMTS Network........................................................................................6-1

6.1 Reconfiguring a Cell.......................................................................................................................................6-2 Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
RAN Reconfiguration Guide 6.1.1 Modifying the Power of a Cell...............................................................................................................6-2 6.1.2 Modifying Cell Frequencies...................................................................................................................6-5 6.1.3 Modifying the Scrambling Code of a Cell.............................................................................................6-6 6.1.4 Modifying Cell System Message Parameters.........................................................................................6-6 6.1.5 Modifying Cell Radio Link Parameters.................................................................................................6-7 6.1.6 Modifying Cell Synchronization Parameters.........................................................................................6-8 6.1.7 Modifying the Area Information of a Cell.............................................................................................6-9 6.1.8 Modifying the UTRAN Registration Area of a Cell..............................................................................6-9 6.1.9 Renaming a Cell...................................................................................................................................6-10 6.1.10 Changing the ID of a Cell..................................................................................................................6-11
6.2 Reconfiguring the Channel............................................................................................................................6-11 6.2.1 Modifying a PRACH............................................................................................................................6-12 6.2.2 Removing a PRACH............................................................................................................................6-15 6.2.3 Modifying an SCCPCH........................................................................................................................6-16 6.2.4 Removing an SCCPCH........................................................................................................................6-21 6.3 Reconfiguring Neighboring Cells.................................................................................................................6-22 6.3.1 Adding an Intra-Frequency Neighboring Cell.....................................................................................6-22 6.3.2 Adding an Inter-Frequency Neighboring Cell.....................................................................................6-24 6.3.3 Adding a Neighboring GSM Cell.........................................................................................................6-25 6.3.4 Modifying a Neighboring Cell.............................................................................................................6-26 6.3.5 Removing a Neighboring Cell..............................................................................................................6-27 6.4 Reconfiguring Timeslot Cross Connection...................................................................................................6-28 6.4.1 Configuring a Timeslot Cross Connection on a BSC6900..................................................................6-28 6.4.2 Configuring a Timeslot Cross Connection on a NodeB.......................................................................6-29
7 Configuring UMTS Features....................................................................................................7-1

7.1 Overview of Feature Configuration..............................................................................................................7-19 7.2 Activating the UMTS License.......................................................................................................................7-53 7.2.1 Activating the BSC6900 License.........................................................................................................7-54 7.2.2 Allocating a license to Telecom Operators..........................................................................................7-55 7.2.3 Allocating a License to NodeBs...........................................................................................................7-55 7.3 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment.............................................7-57 7.4 Configuring Conversational QoS Class .......................................................................................................7-59 7.5 Configuring Streaming QoS Class................................................................................................................7-61 7.6 Configuring Interactive QoS Class...............................................................................................................7-63 7.7 Configuring Background QoS Class.............................................................................................................7-65 7.8 Configuring Emergency Call........................................................................................................................7-67 7.9 Configuring 2-Antenna Receive Diversity(NodeB)......................................................................................7-67 7.10 Configuring Cell Digital Combination and Split........................................................................................7-68 7.11 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).......7-70 7.12 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)..................................................7-71 7.13 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2).....................................................7-73 7.14 Configuring Dynamic Channel Configuration Control...............................................................................7-74 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-09-20)
Contents
7.15 Configuring Integrity Protection.................................................................................................................7-79 7.16 Configuring Encryption...............................................................................................................................7-79 7.17 Configuring Open Loop Power Control .....................................................................................................7-80 7.18 Configuring Downlink Power Balance.......................................................................................................7-82 7.19 Configuring Outer Loop Power Control ....................................................................................................7-82 7.20 Configuring Inner Loop Power Control .....................................................................................................7-83 7.21 Configuring Admission Control..................................................................................................................7-84 7.22 Configuring Load Measurement.................................................................................................................7-86 7.23 Configuring Load Reshuffling....................................................................................................................7-87 7.24 Configuring Overload Control....................................................................................................................7-89 7.25 Configuring Code Resource Management..................................................................................................7-90 7.26 Configuring Shared Network Support in Connected Mode........................................................................7-91 7.27 Configuring Intra Node B Softer Handover................................................................................................7-94 7.28 Configuring Intra RNC Soft Handover.......................................................................................................7-95 7.29 Configuring Inter RNC Soft Handover.......................................................................................................7-96 7.30 Configuring Intra Frequency Hard Handover.............................................................................................7-98 7.31 Configuring Intra RNC Cell Update...........................................................................................................7-99 7.32 Configuring Inter RNC Cell Update.........................................................................................................7-101 7.33 Configuring Intra RNC URA Update........................................................................................................7-103 7.34 Configuring Inter RNC URA Update........................................................................................................7-104 7.35 Configuring Direct Signaling Connection Re-establishment (DSCR)......................................................7-106 7.36 Configuring Base Station Clock(NodeB)..................................................................................................7-108 7.37 Configuring ATM Transmission Introduction Package............................................................................7-110 7.38 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.......................................................7-111 7.39 Configuring Permanent AAL5 Connections for Control Plane Traffic....................................................7-112 7.40 Configuring Call Admission Based on Used AAL2 Path Bandwidth......................................................7-113 7.41 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes...............................................................7-113 7.42 Configuring F5..........................................................................................................................................7-115 7.43 Configuring UBR+ ATM QoS Class........................................................................................................7-116 7.44 Configuring Flow Control.........................................................................................................................7-117 7.45 Configuring BOOTP.................................................................................................................................7-120 7.46 Configuring NodeB Self-discovery Based on IP Mode............................................................................7-121 7.47 Configuring Intelligently Out of Service..................................................................................................7-123 7.48 Configuring OCNS....................................................................................................................................7-123 7.49 Configuring Power Off the Equipment Level by Level............................................................................7-124 7.50 Configuring Connection with TMA(NodeB)............................................................................................7-125 7.51 Configuring Remote Electrical Tilt(UMTS).............................................................................................7-126 7.52 Configuring Same Band Antenna Sharing Unit (900 MHz).....................................................................7-127 7.53 Configuring Multi-mode BS Common CPRI Interface (NodeB).............................................................7-128 7.54 Configuring Multiple RAB Package ........................................................................................................7-130 7.55 Configuring Combination of Two PS Services.........................................................................................7-131 7.56 Configuring Combination of One CS Service and Two PS Services.......................................................7-132 Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
7.57 Configuring Combination of Three PS Services.......................................................................................7-133 7.58 Configuring Combination of One CS Service and Three PS Services.....................................................7-134 7.59 Configuring Combination of Four PS Services.........................................................................................7-135 7.60 Configuring HSDPA Introduction Package..............................................................................................7-137 7.61 Configuring 15 Codes per Cell..................................................................................................................7-138 7.62 Configuring Time and HS-PDSCH Codes Multiplex...............................................................................7-139 7.63 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).....................................................7-140 7.64 Configuring HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation..............7-141 7.65 Configuring HSDPA Power Control.........................................................................................................7-142 7.66 Configuring HSDPA Admission Control..................................................................................................7-143 7.67 Configuring HSDPA Dynamic Power Allocation....................................................................................7-145 7.68 Configuring HSDPA Flow Control...........................................................................................................7-146 7.69 Configuring HSDPA Mobility Management............................................................................................7-148 7.70 Configuring Interactive and Background Traffic Class on HSDPA.........................................................7-149 7.71 Configuring HSDPA UE Category 1 to 24...............................................................................................7-149 7.72 Configuring Improvement of User Experience in Low Traffic Service...................................................7-150 7.73 Configuring DL 16QAM Modulation.......................................................................................................7-151 7.74 Configuring Dynamic Code Allocation Based on NodeB........................................................................7-153 7.75 Configuring HSDPA Enhanced Package..................................................................................................7-154 7.76 Configuring Scheduling based on EPF and GBR.....................................................................................7-154 7.77 Configuring HSDPA State Transition.......................................................................................................7-155 7.78 Configuring HSDPA DRD........................................................................................................................7-156 7.79 Configuring Interactive and Background Traffic Class on HSDPA.........................................................7-158 7.80 Configuring HSDPA over Iur...................................................................................................................7-159 7.81 Configuring SRB over HSDPA.................................................................................................................7-160 7.82 Configuring HSUPA Introduction Package..............................................................................................7-163 7.83 Configuring HSUPA Admission Control..................................................................................................7-164 7.84 Configuring HSUPA Power Control.........................................................................................................7-167 7.85 Configuring HSUPA Mobility Management............................................................................................7-168 7.86 Configuring HSUPA DCCC.....................................................................................................................7-169 7.87 Configuring Interactive and Background Traffic Class on HSUPA.........................................................7-171 7.88 Configuring 20 HSUPA Users per Cell....................................................................................................7-171 7.89 Configuring HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH)........................................7-172 7.90 Configuring HSUPA 2ms TTI..................................................................................................................7-173 7.91 Configuring HSUPA 2 ms/10 ms TTI Handover......................................................................................7-175 7.92 Configuring HSUPA 5.74Mbps per User ................................................................................................7-175 7.93 Configuring Streaming Traffic Class on HSUPA.....................................................................................7-177 7.94 Configuring 60 HSUPA Users per Cell....................................................................................................7-178 7.95 Configuring HSUPA over Iur...................................................................................................................7-179 7.96 Configuring SRB over HSUPA.................................................................................................................7-180 7.97 Configuring Uplink Macro Diversity Intelligent Receiving.....................................................................7-181 7.98 Configuring HSUPA Adaptive Transmission...........................................................................................7-182 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-09-20)
Contents
7.99 Configuring TTI Switch for BE Services Based on Coverage..................................................................7-183 7.100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion........................................................7-186 7.101 Configuring Dynamic CE Resource Management..................................................................................7-187 7.102 Configuring HSPA+ Downlink 28Mbps per User..................................................................................7-189 7.103 Configuring HSPA+ Downlink 21Mbps per User..................................................................................7-190 7.104 Configuring Downlink Enhanced L2......................................................................................................7-191 7.105 Configuring Enhanced CELL-FACH......................................................................................................7-193 7.106 Configuring HSPA+ Downlink 42Mbps per User..................................................................................7-194 7.107 Configuring Downlink 64QAM..............................................................................................................7-196 7.108 Configuring 2x2 MIMO..........................................................................................................................7-198 7.109 Configuring Downlink 64QAM+MIMO................................................................................................7-202 7.110 Configuring CPC - DTX / DRX..............................................................................................................7-205 7.111 Configuring CPC-HS-SCCH Less Operation.........................................................................................7-207 7.112 Configuring 96 HSDPA Users per Cell..................................................................................................7-209 7.113 Configuring 96 HSUPA Users per Cell..................................................................................................7-210 7.114 Configuring 128 HSDPA Users per Cell................................................................................................7-212 7.115 Configuring 128 HSUPA Users per Cell................................................................................................7-213 7.116 Configuring HSUPA UL Interference Cancellation...............................................................................7-214 7.117 Configuring HSUPA Frequency Domain Equalization..........................................................................7-216 7.118 Configuring Uplink 16QAM...................................................................................................................7-218 7.119 Configuring UL Layer 2 Improvement...................................................................................................7-220 7.120 Configuring DC-HSDPA........................................................................................................................7-223 7.121 Configuring Queuing and Preemption....................................................................................................7-227 7.122 Configuring Access Class Restriction.....................................................................................................7-228 7.123 Configuring Traffic Priority Mapping onto Transmission Resources....................................................7-231 7.124 Configuring Differentiated Service Based on SPI Weight......................................................................7-232 7.125 Configuring Inter-Frequency Hard Handover Based on Coverage.........................................................7-233 7.126 Configuring Inter-Frequency Hard Handover Based on DL QoS...........................................................7-234 7.127 Configuring SRNS Relocation (UE Not Involved).................................................................................7-236 7.128 Configuring SRNS Relocation with Hard Handover..............................................................................7-238 7.129 Configuring SRNS Relocation with Cell/URA Update..........................................................................7-239 7.130 Configuring Inter-RAT Handover Based on Coverage...........................................................................7-241 7.131 Configuring Inter-RAT Handover Based on DL QoS............................................................................7-242 7.132 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO......................................7-243 7.133 Configuring Inter-RAT Handover Phase 2.............................................................................................7-244 7.134 Configuring NACC(Network Assisted Cell Change).............................................................................7-245 7.135 Configuring PS Handover between UMTS and GPRS...........................................................................7-246 7.136 Configuring Mobility Between UMTS and LTE Phase 1.......................................................................7-248 7.137 Configuring Inter-Frequency Load Balance............................................................................................7-250 7.138 Configuring Inter-RAT Handover Based on Service..............................................................................7-252 7.139 Configuring Inter-RAT Handover Based on Load..................................................................................7-254 7.140 Configuring DRD Introduction Package.................................................................................................7-255 Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
7.141 Configuring Intra-System Direct Retry...................................................................................................7-256 7.142 Configuring Inter-System Direct Retry...................................................................................................7-257 7.143 Configuring Inter-System Redirect.........................................................................................................7-258 7.144 Configuring Traffic Steering and Load Sharing During RAB Setup......................................................7-259 7.145 Configuring Inter-RAT Redirection Based on Distance.........................................................................7-260 7.146 Configuring Measurement-based Direct Retry.......................................................................................7-263 7.147 Configuring Enhanced Fast Dormancy...................................................................................................7-264 7.148 Configuring Cell Barring........................................................................................................................7-269 7.149 Configuring 3G/2G Common Load Management..................................................................................7-271 7.150 Configuring RAB Quality of Service Renegotiation over Iu Interface...................................................7-272 7.151 Configuring Rate Negotiation at Admission Control..............................................................................7-274 7.152 Configuring Service Steering and Load Sharing in RRC Connection Setup..........................................7-275 7.153 Configuring TCP Accelerator.................................................................................................................7-276 7.154 Configuring Uplink Flow Control of User Plane....................................................................................7-278 7.155 Configuring Active Queue Management (AQM)...................................................................................7-280 7.156 Configuring Quality Improvement for Subscribed Service....................................................................7-281 7.157 Configuring Cell Broadcast Service........................................................................................................7-283 7.158 Configuring Simplified Cell Broadcast...................................................................................................7-292 7.159 Configuring TFO/TrFO...........................................................................................................................7-294 7.160 Configuring Dynamic Power Sharing of Multi-Carriers.........................................................................7-295 7.161 Configuring Multi-Carrier Switch off Based on Traffic Load................................................................7-296 7.162 Configuring Energy Efficiency Improved...............................................................................................7-299 7.163 Configuring Multi-Carrier Switch off Based on Power Backup.............................................................7-300 7.164 Configuring AMR-WB (Adaptive Multi Rate Wide Band)....................................................................7-302 7.165 Configuring AMR/WB-AMR Speech Rates Control..............................................................................7-302 7.166 Configuring Overbooking on ATM Transmission..................................................................................7-303 7.167 Configuring VoIP over HSPA/HSPA+...................................................................................................7-306 7.168 Configuring Optimized Scheduling for VoIP over HSPA......................................................................7-309 7.169 Configuring IMS Signaling over HSPA..................................................................................................7-310 7.170 Configuring PDCP Header Compression (RoHC)..................................................................................7-311 7.171 Configuring CS Voice over HSPA/HSPA+............................................................................................7-312 7.172 Configuring Cell ID + RTT Function-Based LCS..................................................................................7-315 7.173 Configuring OTDOA-Based LCS...........................................................................................................7-322 7.174 Configuring A-GPS-Based LCS.............................................................................................................7-324 7.175 Configuring LCS Classified Zone...........................................................................................................7-331 7.176 Configuring LCS over Iur.......................................................................................................................7-333 7.177 Configuring Iupc Interface for LCS Service...........................................................................................7-339 7.178 Configuring RAN Sharing Introduction Package Package.....................................................................7-341 7.179 Configuring Dedicated Carrier for Each Operator..................................................................................7-343 7.180 Configuring Flexible Network Architecture...........................................................................................7-344 7.181 Configuring Mobility Control and Service Differentiation.....................................................................7-345 7.182 Configuring Independent License Control..............................................................................................7-346 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-09-20)
Contents
7.183 Configuring RAN Sharing Phase 2.........................................................................................................7-347 7.184 Configuring WRFD-02130501 Dedicated Iub Transmission Control....................................................7-348 7.185 Configuring IMSI-Based Handover........................................................................................................7-349 7.186 Configuring MOCN Introduction Package.............................................................................................7-351 7.187 Configuring Carrier Sharing by Operators..............................................................................................7-353 7.188 Configuring Dedicated NodeB/Cell for Operators..................................................................................7-357 7.189 Configuring MOCN Mobility Management...........................................................................................7-358 7.190 Configuring MOCN Load Balance.........................................................................................................7-359 7.191 Configuring Flexible Network Architecture...........................................................................................7-360 7.192 Configuring Iu Flex Load Distribution Management.............................................................................7-361 7.193 Configuring Multi-Frequency Band Networking Management..............................................................7-363 7.194 Configuring Enhanced Multiband Management.....................................................................................7-363 7.195 Configuring Satellite Transmission on Iub Interface..............................................................................7-365 7.196 Configuring Satellite Transmission on Iu Interface................................................................................7-366 7.197 Configuring MBMS Introduction Package.............................................................................................7-367 7.198 Configuring MBMS Broadcast Mode.....................................................................................................7-369 7.199 Configuring MBMS Admission Control.................................................................................................7-370 7.200 Configuring MBMS Load Control..........................................................................................................7-371 7.201 Configuring MBMS Soft/Selective Combination...................................................................................7-372 7.202 Configuring MBMS Transport Resource Management..........................................................................7-373 7.203 Configuring Streaming Service on MBMS.............................................................................................7-375 7.204 Configuring MBMS 2 Channels per Cell................................................................................................7-375 7.205 Configuring 16/32/64/128Kbps Channel Rate on MBMS......................................................................7-376 7.206 Configuring MBMS Phase 2...................................................................................................................7-377 7.207 Configuring MBMS Enhanced Broadcast Mode....................................................................................7-378 7.208 Configuring MBMS P2P over HSDPA...................................................................................................7-379 7.209 Configuring MBMS Admission Enhancement.......................................................................................7-380 7.210 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users.................................7-381 7.211 Configuring FACH Transmission Sharing for MBMS...........................................................................7-382 7.212 Configuring MBMS FLC (Frequency Layer Convergence)/FLD (Frequency Layer Dispersion).........7-384 7.213 Configuring MBMS over Iur...................................................................................................................7-385 7.214 Configuring Dynamic Power Estimation for MTCH..............................................................................7-386 7.215 Configuring MSCH and MSCH Scheduling...........................................................................................7-387 7.216 Configuring MBMS Channel Audience Rating Statistics.......................................................................7-388 7.217 Configuring Domain Specific Access Control (DSAC).........................................................................7-389 7.218 Configuring One Tunnel.........................................................................................................................7-393 7.219 Configuring Hybrid Iub IP Transmission................................................................................................7-394 7.220 Configuring ATM/IP Dual Stack Node B...............................................................................................7-395 7.221 Configuring FP MUX for IP Transmission.............................................................................................7-396 7.222 Configuring IP Fault Detection Based on BFD......................................................................................7-397 7.223 Configuring Dynamic Bandwidth Control of Iub IP...............................................................................7-398 7.224 Configuring Overbooking on IP Transmission.......................................................................................7-399 Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
7.225 Configuring UDP MUX for Iu-CS Transmission...................................................................................7-402 7.226 Configuring ATM Switching-Based Hub NodeB...................................................................................7-402 7.227 Configuring AAL2 Switching-Based Hub NodeB..................................................................................7-403 7.228 Configuring IP Routing-Based Hub NodeB............................................................................................7-404 7.229 Configuring Overbooking on Hub Node B Transmission......................................................................7-405 7.230 Configuring Ethernet OAM....................................................................................................................7-406 7.231 Configuring Clock Synchronization on Ethernet in NodeB....................................................................7-409 7.232 Configuring Synchronous Ethernet.........................................................................................................7-410 7.233 Configuring RNC Node Redundancy.....................................................................................................7-411 7.234 Configuring RRU Redundancy...............................................................................................................7-423 7.235 Configuring Transmit Diversity..............................................................................................................7-424 7.236 Configuring 4-Antenna Receive Diversity..............................................................................................7-426 7.237 Configuring Extended Cell Coverage up to 200km................................................................................7-427 7.238 Configuring High Speed Access.............................................................................................................7-428 7.239 Configuring PDCP Header Compression (RFC2507)............................................................................7-429 7.240 Configuring HCS (Hierarchical Cell Structure)......................................................................................7-430 7.241 Configuring Intra Frequency Load Balance............................................................................................7-432 7.242 Configuring Potential User Control........................................................................................................7-433 7.243 Configuring License Control for Urgency..............................................................................................7-434 7.244 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g.............................7-435 7.245 Configuring NACC Procedure Optimization Based on Iur-g.................................................................7-437 7.246 Configuring MBSC Load Balancing.......................................................................................................7-440 7.247 Configuring GSM and UMTS Traffic Steering Based on Iur-g..............................................................7-444 7.248 Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority .......................................7-446 7.249 Configuring Warning of Disaster............................................................................................................7-448 7.250 Configuring Multi-mode Dynamic Power Sharing (UMTS)..................................................................7-450 7.251 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB)...........................7-452 7.251.1 Configuring IP-Based GSM and UMTS Co-Transmission on Base Station Side.........................7-452 7.251.2 Configuring IP-Based UMTS and LTE Co-Transmission on Base Station Side...........................7-455 7.252 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side(NodeB)................7-460 7.253 Configuring Multi-Mode BS Common Reference Clock (NodeB)........................................................7-465 7.253.1 Configuring GSM and UMTS Common Reference Clock............................................................7-465 7.253.2 Configuring UMTS and LTE Common Reference Clock.............................................................7-472
xiv
Issue 03 (2010-09-20)
Figures
Figures
Figure 4-1 Floating nuts installation..................................................................................................................4-10 Figure 4-2 Checking the subrack configuration mode.......................................................................................4-11 Figure 4-3 Floating nuts installation..................................................................................................................4-28 Figure 7-1 Iub Interface Trace dialog box..........................................................................................................7-58 Figure 7-2 Iub interface trace dialog box ..........................................................................................................7-60 Figure 7-3 Iu Interface Trace dialog box............................................................................................................7-62 Figure 7-4 Iu Interface Trace dialog box............................................................................................................7-64 Figure 7-5 Iu Interface Trace dialog box............................................................................................................7-66 Figure 7-6 Message Tracing on the Uu Interface.............................................................................................7-107 Figure 7-7 RRC CONNECTION RELEASE...................................................................................................7-108 Figure 7-8 Network topology of Multi-mode BS Common CPRI Interface....................................................7-129 Figure 7-9 VoIP service...................................................................................................................................7-136 Figure 7-10 Cell Performance Monitoring.......................................................................................................7-139 Figure 7-11 Cell performance monitoring........................................................................................................7-142 Figure 7-12 RRC_RB_RECFG/RRC_RB_SETUP Information.....................................................................7-157 Figure 7-13 Uu Interface Trace dialog box......................................................................................................7-159 Figure 7-14 Uu Interface Trace dialog box......................................................................................................7-162 Figure 7-15 SRB Over HSPA during signaling establishment........................................................................7-162 Figure 7-16 SRB Over HSPA during traffic establishment.............................................................................7-163 Figure 7-17 Uu Interface Trace dialog box......................................................................................................7-185 Figure 7-18 Trace result when TTI is 2 ms......................................................................................................7-185 Figure 7-19 Trace result when TTI is 10 ms....................................................................................................7-186 Figure 7-20 Uu Interface Tracing dialog box...................................................................................................7-192 Figure 7-21 Viewing dl-RLC-PDU-Size IE....................................................................................................7-193 Figure 7-22 Uu interface tracing......................................................................................................................7-197 Figure 7-23 Checking the dl-64QAM-Configured information element.......................................................7-198 Figure 7-24 Uu interface tracing......................................................................................................................7-201 Figure 7-25 Checking the mimoParameters information element.................................................................7-201 Figure 7-26 Uu Interface Tracing dialog box...................................................................................................7-206 Figure 7-27 IE Information..............................................................................................................................7-207 Figure 7-28 RRC_RB_SETUP Information.....................................................................................................7-208 Figure 7-29 Uu Interface tracing......................................................................................................................7-219 Figure 7-30 Indication of uplink 16QAM........................................................................................................7-220 Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Figures
RAN Reconfiguration Guide Figure 7-31 Uu Interface tracing......................................................................................................................7-222
Figure 7-32 Viewing the rlc-PDU-Size IE......................................................................................................7-222 Figure 7-33 Uu Interface Trace dialog box......................................................................................................7-229 Figure 7-34 RRC_SYS_INFO_TYPE3 message.............................................................................................7-230 Figure 7-35 Uu Interface Trace dialog box......................................................................................................7-249 Figure 7-36 Tracing the SIB19 message..........................................................................................................7-250 Figure 7-37 Uu Interface Tracing dialog box...................................................................................................7-262 Figure 7-38 Viewing GSM-Targetcellinfo IE................................................................................................7-262 Figure 7-39 Status of the Enhanced Fast Dormancy license............................................................................7-267 Figure 7-40 UE in CELL_DCH state ..............................................................................................................7-267 Figure 7-41 UE in CELL_PCH state................................................................................................................7-268 Figure 7-42 Cell update....................................................................................................................................7-268 Figure 7-43 Channel reconfiguration...............................................................................................................7-268 Figure 7-44 Uu Interface Trace dialog box......................................................................................................7-270 Figure 7-45 AccessClassBarredList.................................................................................................................7-270 Figure 7-46 Iub interface trace dialog box ......................................................................................................7-279 Figure 7-47 TrafficClass-Private......................................................................................................................7-279 Figure 7-48 UE Trace dialog box.....................................................................................................................7-281 Figure 7-49 Viewing the SABP_LOAD_QUERY messages...........................................................................7-285 Figure 7-50 Viewing the SABP_LOAD_QUERY_CMP messages................................................................7-285 Figure 7-51 Viewing the CBS function status..................................................................................................7-286 Figure 7-52 Viewing the SABP_WRITE_REPLACE messages.....................................................................7-287 Figure 7-53 Viewing the SABP_WRITE_REPLACE_CMP messages...........................................................7-288 Figure 7-54 Viewing the UU_BMC_MSG_TYPE messages..........................................................................7-289 Figure 7-55 Viewing the SAB_KILL messages...............................................................................................7-290 Figure 7-56 Viewing the SABP_KILL_CMP messages..................................................................................7-291 Figure 7-57 UU_BMC_MSG_TYPE message................................................................................................7-293 Figure 7-58 Uu Interface Trace dialog box......................................................................................................7-307 Figure 7-59 UE in CELL_DCH state...............................................................................................................7-308 Figure 7-60 VoIP services established on the HSPA/HSPA+.........................................................................7-308 Figure 7-61 Type of TTI carried in the message..............................................................................................7-308 Figure 7-62 Uu Interface Trace dialog box......................................................................................................7-314 Figure 7-63 UE in CELL_DCH state...............................................................................................................7-314 Figure 7-64 CS voice services established on the HSPA/HSPA+...................................................................7-314 Figure 7-65 Type of TTI carried in the message..............................................................................................7-315 Figure 7-66 Iu interface trace dialog box ........................................................................................................7-317 Figure 7-67 Iub interface trace dialog box ......................................................................................................7-317 Figure 7-68 Uu interface trace dialog box .......................................................................................................7-318 Figure 7-69 Location reporting control............................................................................................................7-318 Figure 7-70 Location report.............................................................................................................................7-319 Figure 7-71 Dedicated measurement type........................................................................................................7-320 Figure 7-72 Round trip time.............................................................................................................................7-320 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-09-20)
Figures
Figure 7-73 UE Rx-Tx time difference............................................................................................................7-321 Figure 7-74 UE Rx-Tx time difference type 1.................................................................................................7-321 Figure 7-75 Iu Interface Trace dialog box........................................................................................................7-327 Figure 7-76 Uu Interface Trace dialog box......................................................................................................7-327 Figure 7-77 Location reporting control............................................................................................................7-328 Figure 7-78 Location report.............................................................................................................................7-329 Figure 7-79 ue-positioning-GPS-AssistanceData............................................................................................7-329 Figure 7-80 GPS-MeasurementParam..............................................................................................................7-330 Figure 7-81 Message Tracing on the Iu Interface............................................................................................7-332 Figure 7-82 LOCATION REPORT.................................................................................................................7-333 Figure 7-83 Message Tracing on the Iur Interface...........................................................................................7-335 Figure 7-84 GPS assistance data......................................................................................................................7-336 Figure 7-85 INFORMATION EXCHANGE INITIATION REQUEST.........................................................7-337 Figure 7-86 INFORMATION EXCHANGE INITIATION RESPONSE.......................................................7-337 Figure 7-87 DEDICATED MEASUREMENT INITIATION REQUEST......................................................7-338 Figure 7-88 DEDICATED MEASUREMENT INITIATION RESPONSE....................................................7-338 Figure 7-89 multiplePLMN-List IE in RRC_MASTER_INFO_BLOCK.......................................................7-355 Figure 7-90 plmn-Identity IE in RRC_MASTER_INFO_BLOCK.................................................................7-356 Figure 7-91 plmn-identity IE in the MIB.........................................................................................................7-358 Figure 7-92 Uu Interface Trace dialog box......................................................................................................7-391 Figure 7-93 DSAC activated............................................................................................................................7-391 Figure 7-94 DSAC not activated......................................................................................................................7-392 Figure 7-95 RNC-based cell blocking activated (for CS or PS)......................................................................7-392 Figure 7-96 RNC-based cell blocking activated (for both CS and PS)............................................................7-393 Figure 7-97 Link performance monitoring.......................................................................................................7-399 Figure 7-98 PPP Ethernet OAM network.........................................................................................................7-407 Figure 7-99 Network topology when RNC pool is not configured..................................................................7-412 Figure 7-100 Network topology when RNC pool is configured......................................................................7-412 Figure 7-101 Normal heartbeat between RNC202 and RNC203.....................................................................7-417 Figure 7-102 RNC202 obtains the NodeB control rights.................................................................................7-417 Figure 7-103 CS AMR service be set up successfully.....................................................................................7-418 Figure 7-104 RNC203 takes over the NodeB control rights............................................................................7-418 Figure 7-105 CS AMR service be set up successfully.....................................................................................7-418 Figure 7-106 RNC202 takes over the NodeB control rights again..................................................................7-419 Figure 7-107 CS AMR service be set up successfully.....................................................................................7-419 Figure 7-108 IP-over-FE/GE UMTS and LTE co-transmission on base station side......................................7-456 Figure 7-109 IP-over-E1/T1 UMTS and LTE co-transmission on base station side.......................................7-456 Figure 7-110 GTMU-based TDM timeslot cross connection co-transmission................................................7-461 Figure 7-111 GSM-UTRP-based TDM timeslot cross connection co-transmission........................................7-461 Figure 7-112 Common GPS reference clock...................................................................................................7-467 Figure 7-113 Common BITS reference clock..................................................................................................7-467 Figure 7-114 Common E1/T1 reference clock on the GSM side (GTMU).....................................................7-468 Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Figures
RAN Reconfiguration Guide Figure 7-115 Common E1/T1 reference clock on the UMTS side (WMPT)...................................................7-468 Figure 7-116 Common Ethernet reference clock on the UMTS side (WMPT)...............................................7-468 Figure 7-117 Common IP reference clock on the UMTS side (WMPT).........................................................7-469
Figure 7-118 Common GPS reference clock...................................................................................................7-473 Figure 7-119 Common BITS reference clock..................................................................................................7-474 Figure 7-120 Common E1/T1 reference clock on the UMTS side (WMPT)...................................................7-474 Figure 7-121 Common Ethernet reference clock on the LTE side (LMPT)....................................................7-475 Figure 7-122 Common IP reference clock on the LTE side (LMPT)..............................................................7-475
xviii
Issue 03 (2010-09-20)
Tables
Tables
Table 2-1 Reconfiguration tools...........................................................................................................................2-2 Table 4-1 License for inter-frequency handover or inter-RAT handover............................................................4-3 Table 4-2 Measurement items and events for BE services...................................................................................4-3 Table 4-3 Operation overview and impact on services ..................................................................................... 4-19 Table 4-4 Establishing transmission links on other SPUa/SPUb boards............................................................4-21 Table 4-5 Removing other configuration objects on the board..........................................................................4-22 Table 5-1 Data to be negotiated and planned for configuring a custom NodeB alarm........................................5-7 Table 7-1 UMTS Basic Feature List...................................................................................................................7-19 Table 7-2 UMTS Optional Feature List............................................................................................................. 7-25 Table 7-3 Requirements on NEs.......................................................................................................................7-124 Table 7-4 Processing procedure after the comparison......................................................................................7-266 Table 7-5 Requirements on NEs.......................................................................................................................7-299 Table 7-6 Requirements on NEs.......................................................................................................................7-300 Table 7-7 Timers related to SAAL links of satellite transmission...................................................................7-367
Issue 03 (2010-09-20)
xix
1 Changes in the RAN Reconfiguration Guide
Changes in the RAN Reconfiguration Guide

This chapter describes the changes in the RAN Reconfiguration Guide.
04 (2010-09-20)
This is the fourth commercial release of V900R012C01. Compared with issue 03 (2010-07-30), this issue includes the following new topics: l l 4.4 Adding Boards and Subracks 4.5 Removing Boards and Subracks
Compared with issue 03 (2010-07-30), this issue does not incorporate any changes. Compared with issue 03 (2010-07-30), this issue does not exclude any topics.
03 (2010-07-30)
This is the third commercial release of V900R012C01. Compared with issue 02 (2010-06-21), this issue includes the following new topics: l 4.2 Configuring Link Stability Control for BE
Compared with issue 02 (2010-06-21), this issue incorporates the following changes: Content 7.60 Configuring HSDPA Introduction Package 7.72 Configuring Improvement of User Experience in Low Traffic Service 7.99 Configuring TTI Switch for BE Services Based on Coverage 7.116 Configuring HSUPA UL Interference Cancellation Description The example is modified. The description of the prerequisites are modified. The figure of Uu interface trace dialog box is modified. The activation procedure is modified.
Issue 03 (2010-09-20)
1-1
Content 7.117 Configuring HSUPA Frequency Domain Equalization 7.106 Configuring HSPA+ Downlink 42Mbps per User 7.120 Configuring DC-HSDPA 7.137 Configuring Inter-Frequency Load Balance 7.146 Configuring Measurement-based Direct Retry 7.156 Configuring Quality Improvement for Subscribed Service 7.147 Configuring Enhanced Fast Dormancy
Description The example is modified. The example is modified. The activation procedure is modified. The example is modified. The activation procedure is modified. The activation procedure and script are modified. The activation procedure is modified.
Compared with issue 02 (2010-06-21), this issue does not exclude any topics.
02 (2010-06-21)
This is the second commercial release of V900R012C01. Compared with issue 01 (2010-04-10), this issue includes the following new topics: l 5.4 Configuring a Custom NodeB Alarm
Compared with issue 01 (2010-04-10), this issue does not incorporate any changes. Compared with issue 01 (2010-04-10), this issue does not exclude any topics.
01 (2010-04-10)
This is the first commercial release of V900R012C01. Compared with issue 04 (2010-01-30) of V900R011C00, this issue includes the following new topics: l l l l l l l 7.50 Configuring Connection with TMA(NodeB) 7.51 Configuring Remote Electrical Tilt(UMTS) 7.9 Configuring 2-Antenna Receive Diversity(NodeB) 7.36 Configuring Base Station Clock(NodeB) Configuring IP-Based Multi-mode Co-Transmission on BS side (GBTS) Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side(GBTS) Configuring Multi-Mode BS Common Reference Clock (GBTS)
Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not incorporate any changes.
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-09-20)
Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not exclude any topics.
Issue 03 (2010-09-20)
1-3
2 Introduction to Reconfiguration
Introduction to Reconfiguration
About This Chapter

This chapter defines reconfiguration and describes the reconfiguration tools. 2.1 Definition Reconfiguration refers to a process of adding, deleting, or modifying the data of the RAN system (consisting of at least one BSC6900 and one base station) after it starts operating. 2.2 Tools The Local Maintenance Terminal (LMT) and the Configuration Management Express (CME) can be used to configure the BSC6900.
Issue 03 (2010-09-20)
2-1
2.1 Definition
Reconfiguration refers to a process of adding, deleting, or modifying the data of the RAN system (consisting of at least one BSC6900 and one base station) after it starts operating. The RAN is reconfigured in the following scenarios: l Network optimization Network optimization is a process of adjusting and optimizing the network performance based on the data that is obtained from performance measurements or drive tests when the network is in service. l System capacity expansion System capacity expansion enables the BSC system to serve more users through hardware addition or configuration modification in the existing network. l Feature configuration Feature configuration is a process of activating an optional feature by configuring its key parameters. This document focuses on the data to be prepared and reconfiguration procedures. However, it does not focus on the data analysis process of network optimization and the number of boards and links for capacity expansion that are subject to actual network conditions. Feature configuration provides guidelines for activating a feature, but it cannot guarantee the optimum feature performance in the network.
2.2 Tools
The Local Maintenance Terminal (LMT) and the Configuration Management Express (CME) can be used to configure the BSC6900. Table 2-1 describes the tools used in reconfiguration. This document only describes the data reconfiguration through MML commands on the LMT. Table 2-1 Reconfiguration tools Data Configuration Tool LMT CME Function Online or offline configuration of the BSC6900 can be performed through MML commands. BSC6900 configuration can be performed through the CME graphic user interface. l In integrated mode, the configuration data can be sent to the BSC6900 through the M2000 immediately or at a specified time. This mode is used for data reconfiguration. l In standalone mode, the configuration file needs to be exported after the configuration and then loaded to the BSC6900 through the LMT or M2000 for the data to take effect. This mode applies to BSC6900 initial configuration.
Issue 03 (2010-09-20)
2-3
3 Checking the License
3
Prerequisite
l l l A new license is granted.
Checking the License
This chapter describes how to check the newly granted license.
The BSC6900 is in the minimum configuration. The license file is loaded. For details, see FTP Server.
Context
A new license is required in the following situations: l l l A network is deployed. New license control items are introduced to the C version to be upgraded. These license control items, however, are not defined in the license file of the earlier version. New license control items are introduced to the C version to be upgraded. These license control items are defined in the license file of the earlier version, but their values are incorrect. The R version is upgraded. The Equipment Serial Number (ESN) is changed. The functions restricted by the license need to be enabled. The license is about to expire.
l l l l
Procedure
Step 1 Run the CHK DATA2LIC command to check the license. In this step, set File Name. ----End
Example
/*Check the license file named ON1020691_GU2.dat*/
CHK DATA2LIC: FN="ON1020691_GU2.dat"
Issue 03 (2010-09-20)
3-1
3 Checking the License
Postrequisite
After checking the license, run the ACT LICENSE command to activate the license.
3-2
Issue 03 (2010-09-20)
4 Reconfiguring the BSC6900
4
About This Chapter
Reconfiguring the BSC6900
This chapter describes how to reconfigure the running BSC6900 or expand its capacity. 4.1 Changing Signaling Points When the BSC6900 is relocated or network optimization is performed, the destination signaling point code (DPC) and originating signaling point code (OPC) are changed. Therefore, you need to change the signaling points. 4.2 Configuring Link Stability Control for BE Link stability control for BE services is implemented by the BSC6900. Excessively high TX power means that UE's links are unstable. In this case, link stability control is performed through rate decrease, inter-frequency handover, or inter-RAT handover to ensure link stability and the QoS. Rate decrease in link stability control for BE is implemented through DCCC. 4.3 Changing the Work Mode of a Board To improve the reliability of a BSC6900 board, you can change the work mode of the board in offline mode. 4.4 Adding Boards and Subracks As traffic volume increases, the BSC6900 cannot meet the increasing service requirements. In this case, you can add boards or subracks to expand system capacity. 4.5 Removing Boards and Subracks Removing boards interrupts services on these boards. Therefore, remove boards in the early morning when the traffic is low.
Issue 03 (2010-09-20)
4-1
4.1 Changing Signaling Points

When the BSC6900 is relocated or network optimization is performed, the destination signaling point code (DPC) and originating signaling point code (OPC) are changed. Therefore, you need to change the signaling points.
Prerequisite
l l l The LMT runs normally. The LMT communicates with the BSC6900 properly. A new license is granted.
Procedure
Step 1 Run the MOD OPC command to change OSP name or The host type of signalling point of the OPC. Step 2 Run the MOD N7DPC command to change a DPC. ----End
Example
/*Change an OPC*/
MOD OPC: SPX=1, NAME="MBSC_01", HOSTTYPE=SINGLEHOST;
/*Change a DPC*/
MOD N7DPC: DPX=0, SPDF=WNF, DPC=500;
Postrequisite
Deactivate the old license and then activate the new license. All the links and adjacent nodes mapping to the original signaling points are mapped to the new signaling points.
4.2 Configuring Link Stability Control for BE

Link stability control for BE services is implemented by the BSC6900. Excessively high TX power means that UE's links are unstable. In this case, link stability control is performed through rate decrease, inter-frequency handover, or inter-RAT handover to ensure link stability and the QoS. Rate decrease in link stability control for BE is implemented through DCCC.
Prerequisite
l l l The LMT of the BSC6900 runs normally. The LMT communicates with the BSC6900 properly. The license for inter-frequency handover or inter-RAT handover is activated. Table 4-1 lists the licenses for inter-frequency handover and inter-RAT handover.
4-2
Table 4-1 License for inter-frequency handover or inter-RAT handover Feature ID WRFD-020 302 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS Inter-RAT Handover Based on Coverage License Control Item Inter frequency hard handover License Configured on... BSC6900 Configuration Method 7.125 Configuring InterFrequency Hard Handover Based on Coverage 7.126 Configuring InterFrequency Hard Handover Based on DL QoS 7.130 Configuring Inter-RAT Handover Based on Coverage 7.131 Configuring Inter-RAT Handover Based on DL QoS
WRFD-020 304
Inter Frequency Hard Handover Based on DL QoS
BSC6900
WRFD-020 303
Coverage Based Inter-RAT Handover Between UMTS and GSM/GPRS Inter-RAT Handover Based on DL QoS
BSC6900
WRFD-020 309
Inter-RAT Handover Based on DL QoS
BSC6900
Context
The procedure of link stability control is as follows: Firstly, measurement control is performed. Secondly, service rates are adjusted or other kinds of link stability control actions are performed according to the measurement results. Measurement results for BE services are reported by events. Table 4-2 lists the measurement items and events of BE services. Table 4-2 Measurement items and events for BE services Measurement Item UL TX power of the UE UL BLER DL TX power in the pilot field of the DPCCH
Issue 03 (2010-09-20)
Event 6A1, 6A2, 6B1, 6B2, and 6D 5A E and F

4-3
Measurement Item DL RLC PDU retransmission ratio
Event A
Procedure
Step 1 Run the BSC6900 MML command SET UQOSACT to set RNC-Oriented QoS Enhancement Algorithm Parameters. The parameters for ensuring link stability are as below. l QOS Switch for BE Traffic l First Action for BE Uplink QOS l Second Action for BE Uplink QOS l Third Action for BE Uplink QOS l Wait Timer for BE Uplink Rate l First Action for BE Downlink QOS l Second Action for BE Downlink QOS l Third Action for BE Downlink QOS l Indicator for BE Uplink QOS Event l Srnc Parameter for BE Downlink RLC QOS l DRNC Parameter for BE Downlink RLC QOS l Measurement of 6A1 Switch l Measurement of 5A Switch l Measurement of 6D Switch Step 2 Run the BSC6900 MML command SET UQUALITYMEAS to set RNC-Oriented QoS quality measurement parameters. The parameters for ensuring link stability are as below. l BE Trigger Time 6A1 l BE Trigger Time 6B1 l BE Trigger Time 6A2 l BE Trigger Time 6B2 l BE Trigger Time 6D l UL Measurement Filter Coefficient l DL TCP Measurement Filter Coefficient l BE Trigger Time of Event E l BE Reporting Period Unit for Event E l BE Event E Reporting Period or BE Event E Reporting Period minute l BE Trigger Time of Event F l BE Reporting Period Unit for Event F l BE Event F Reporting Period or BE Event F Reporting Period minute Step 3 Run the BSC6900 MML command ADD UCELLCAC to add cell-oriented Call Admission Control (CAC) algorithm parameters. The parameters for ensuring link stability are as below. l Max UL TX power of interactive service
l Max UL TX power of background service

NOTE
The BSC6900 defines the default values for Max UL TX power of interactive service and Max UL TX power of background service. Retain the default value in normal situations.
Step 4 Run the BSC6900 MML command ADD UCELLRLPWR to add cell oriented downlink transmit power parameters. Step 5 Run the BSC6900 MML command ADD UCELLQUALITYMEAS to add Cell-Oriented QoS quality measurement parameters. The parameters for ensuring link stability are as below. l BE Trigger Time 6A1 l BE Trigger Time 6B1 l BE Trigger Time 6A2 l BE Trigger Time 6B2 l BE Trigger Time 6D l BE Trigger Time of Event E l BE Reporting Period Unit for Event E l BE Event E Reporting Period l BE Trigger Time of Event F l BE Reporting Period Unit for Event F l BE Event F Reporting Period
NOTE
The BSC6900 defines the default value for the above parameter. Retain the default value in normal situations.
Step 6 Run the BSC6900 MML command ADD UTYPRABQUALITYMEAS to add typical RAB parameters of quality measurement. l Uplink Event 6A1 Relative Threshold l Uplink Event 6A2 Relative Threshold l Uplink Event 6B1 Relative Threshold l Uplink Event 6B2 Relative Threshold l Statistic Block Number for 5A Event l Event 5A Threshold l Interval Block Number l Event Ea Relative Threshold l Event Eb Relative Threshold Step 7 Run the BSC6900 MML command ADD UTYPRABRLC to add Radio Link Control (RLC) parameters for a subflow of a typical Radio Access Bearer (RAB). The parameters for ensuring link stability are as below. l re-TX monitor period l Event A threshold l Hysteresis of Event A l Event A pending time after trigger l Filter Coefficient of RLC Retransmission Ratio
Issue 03 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-5

NOTE
The BSC6900 defines the default value for above parameters. Retain the default value in normal situations.
Step 8 Link Stability Control for BE Implemented through DCCC Run the BSC6900 MML command SET UCORRMALGOSWITCH and set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH in order to activate DCCC algorithm. Details of other procedures see "Activating Rate Adjustment Based on Link Quality" of 7.14 Configuring Dynamic Channel Configuration Control. Step 9 Link Stability Control for BE Implemented through Inter-frequency Iandover 1. 2. Run the BSC6900 MML command ADD UCELLHOCOMM to set Inter-Frequency and Inter-RAT Coexist Switch to INTERFREQ(inter-frequency handover only). Run the BSC6900 MML command SET UCORRMALGOSWITCH to set HandOver Switch to HO_INTER_FREQ_HARD_HO_SWITCH. Run the BSC6900 MML command ADD UCELLHOCOMM to set Inter-Frequency and Inter-RAT Coexist Switch to INTERRAT(inter-RAT handover only), and to set Inter-RAT PS Handover Switch to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set HandOver Switch to HO_INTER_RAT_PS_OUT_SWITCH.
Step 10 Link Stability Control for BE Implemented through Inter-RAT Handover 1.
2.
Step 11 Link Stability Control for BE Implemented through both inter-frequency Handover and InterRAT Handover 1. Run the BSC6900 MML command ADD UCELLHOCOMM to set Inter-Frequency and Inter-RAT Coexist Switch to SIMINTERFREQRAT(inter-frequency and interRAT handover), and to set Inter-RAT PS Handover Switch to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set HandOver Switch to HO_INTER_FREQ_HARD_HO_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH.
2.
----End
Example
//Set QoS Enhancement Algorithm 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; //Activate DCCC Algorithm SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1; //Link Stability Control for BE Implemented through Inter-frequency Iandover ADD 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; //Link Stability Control for BE Implemented through Inter-RAT Handover
4-6
Issue 03 (2010-09-20)
ADD 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;
4.3 Changing the Work Mode of a Board

To improve the reliability of a BSC6900 board, you can change the work mode of the board in offline mode.
Prerequisite
l l l The board works in independent mode. The board supports the active/standby mode. No other board of the same type as the original board is configured in the standby slot.
Context
CAUTION
The board of the DPU type does not support the active/standby mode. Therefore, the following steps cannot be performed on such a board. After the work mode of a board is changed, the corresponding subrack must be reset. In this case, the related services are affected. Therefore, perform this operation with caution. After the work mode of a board is changed, must do Verifying Network Reliability. A BSC6900 board works in two modes: independent mode and active/standby mode. To improve the reliability, the board can be changed from the independent mode to the active/standby mode. After a board is changed to the active/standby mode, its configuration is automatically copied to the active and standby boards. The device IP address of the standby IP-based interface board or the active/standby relationship between the ports on the active and standby boards need to be manually set. When data is transmitted on the ports of the boards in non-active/standby mode, you need to run the ADD ETHIP command to configure the device IP address of the standby board. If data is transmitted on the ports of the boards in active/standby mode, you need to run the ADD ETHREDPORT to configure the active/standby relationship between the ports on the active and standby boards. This operation applies to all the boards except the OMU board. For details on how to change an OMU board from the independent mode to the active/standby mode, see Switchover Between the Active and Standby OMUs.
Procedure
Step 1 Run the SET CFGDATAINEFFECTIVE command to set a subrack to ineffective mode. Step 2 Run the MOD BRD command to change the work mode of a board. Step 3 Run the SET CFGDATAEFFECTIVE command to set the subrack to effective mode.
Step 4 Run the RST SUBRACK command to reset the subrack and make the changed work mode of the board take effect. ----End
Example
/*Set subrack 1 to ineffective mode*/
SET CFGDATAINEFFECTIVE: SRN=1;
/*Change the work mode of the board in slot 14 of subrack 1*/

MOD BRD: SRN=1, SN=14, RED=YES;
/*Set all subracks to effective mode*/

SET CFGDATAEFFECTIVE;
/*Reset subrack 1*/

RST SUBRACK: SRN=1;
Postrequisite
Verifying Network Reliability.
4.4 Adding Boards and Subracks

As traffic volume increases, the BSC6900 cannot meet the increasing service requirements. In this case, you can add boards or subracks to expand system capacity. 4.4.1 Adding a Subrack This section describes procedures and precautions for adding subracks. 4.4.2 Adding the SPUa/SPUb Board This section describes procedures and precautions for adding the SPUa/SPUb board. 4.4.3 Adding the DPUb/DPUe Board This section describes procedures and precautions for adding the DPUb/DPUe board. 4.4.4 Adding Interface Boards This section describes procedures and precautions for adding interface boards.
4.4.1 Adding a Subrack

This section describes procedures and precautions for adding subracks.
Prerequisite
l Network design is complete. Network design involves planning of traffic volume in each subrack, planning of the quantity of subracks, and planning of the quantity of boards and types of boards. Contact Huawei to obtain the detailed network design and planning scheme. l Tools required for adding subracks are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, ESD box or bag, dustfree cotton cloth, and fiber cleaner.
4-8
l l l l
The parts needed for adding subracks are all ready. The parts include subracks, screws, power cables, PGND cables, and signal cables connecting new subracks and NEs. Subracks to be added are ready. If there is space in the cabinet, add a subrack there. If idle space is not available, another cabinet is needed. Check whether the program files of the OMU board in the OMU active workspace installation directory\bin\fam are correct.
Context
CAUTION
To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD wrist strap properly. Ensure that the ESD wrist strap is properly connected to the ESD connector on the cabinet. If no ESD wrist strap or no proper grounding point is available, wear ESD gloves. When original subracks are in effective mode, adding subracks does not affect ongoing service. When original subracks are in ineffective mode, the BSC6900 needs restarting to add a subrack. Restarting the BSC6900 interrupts the ongoing services. Therefore, adding new subracks when original subracks are in effective mode is recommended.
Procedure
Step 1 Set the DIP switches according to the location of the new subrack, by referring toDIP Switch on the Subrack.
CAUTION
l Checking and Setting the Subrack DIP Switch; then, power on the subracks. Set the DIP switches before powering on the subrack. Settings of the DIP switches after powering on the subrack are invalid. l Set the DIP switches for the new subrack by referring to Checking and Setting the Subrack DIP Switch. Different subracks must have different settings of DIP switches. If two subracks in the BSC6900 share the same settings of the DIP switches, services on the two subracks will be disrupted. Step 2 Turn off the power switch for the new subrack by referring to Distribution of Power Switches. Step 3 Make sure floating nuts are installed in the mounting bar at the front side of the cabinet. If no floating nuts are available, take floating nuts out of the ESD bag at the bottom of the cabinet and install them in the place highlighted in yellow shown in Figure 4-1.
Issue 03 (2010-09-20)
4-9
Figure 4-1 Floating nuts installation
NOTE
Three holes in the mounting bar are known as one U space. One subrack occupies 36 holes. One subrack is fixed by 4 pairs of floating nuts installed symmetrically. The floating nuts are installed in the 3rd, the 12th, the 25th, and the 34th holes in the mounting bar where the subrack will be installed.
Step 4 Two people hold the mounting ears and support the base of the subrack. Slide the subrack along the guiding rail into the cabinet, and then fasten the screws to fix the subrack. Step 5 Install the power cables for the new subrack by referring to Connections of Power Cables and PGND Cables in the Cabinet. Step 6 Install the boards in the new subrack by referring to Installing Boards and Setting Board DIP Switches. Step 7 Install the total four network cables connecting the active/standby SCUa in the MPS subrack with the active/standby SCUa in the new subrack by referring to Installing the Inter-SCUa Cables Between Different Subracks. Step 8 Install other connecting cables for the new subrack by referring to Installing the Signal Cables. Step 9 Check whether cables in the new subrack are connected correctly. Step 10 Attaching the Engineering Labels to the Signal Cables. Step 11 Turn on the power switch for the new subrack. Step 12 Log in to the LMT, and check the subrack configuration mode at the top right corner of the GUI as shown in a red circle in Figure 4-2.
4-10
Issue 03 (2010-09-20)
If... Some subracks are in ineffective mode.
Then... 1. Run the SET CFGDATAEFFECTIVE command in MML to set all the subracks in effective mode. 2. Go to step Step 13.
All the subracks are in ineffective Go to step Step 13. mode.
Figure 4-2 Checking the subrack configuration mode
Step 13 Run the ADD SUBRACK MML command to add a subrack. Step 14 Run the SET CFGDATAEFFECTIVE command in MML to set the new subrack to effective mode. After adding the subrack by running the ADD SUBRACK command, Data Configuration Modes of the new subrack is set to ineffective mode by default. Step 15 Add the SPUa/SPUb board. Step 16 Add the DPU board. Step 17 Add the interface board. Step 18 Check the process of adding the boards in the Device Maintenance window on the LMT. When all the boards in the subrack are added ten minutes later, the subrack begins to work normally. Open the Device Maintenance window on the LMT, and check whether all the boards work normally in the BSC Device Panel tab page. Step 19 In the Browse Alarm tab page on the LMT, check whether alarms such as board fault alarms are reported.
Issue 03 (2010-09-20)
4-11
If... Alarms such as board fault alarms are reported.
Then... 1. Find out the reason according to the alarms and clear them. 2. Go back to step Step 19.
Alarms such as board fault alarms are not Go to step Step 20. reported. Step 20 Run the DSP BRDVER to query the software version of the new board. Compare the query results with the version configuration information file of the boards to check whether software versions of the new boards follow the version mapping of the boards. If... Then...
Software versions of the new boards Go to step Step 21. follow the version mapping of the boards. Software versions of the new boards do not follow the version mapping of the boards. 1. Check whether the program files of the OMU board in the OMU active workspace installation directory\LoadData are correct. If the program files are not correct, contact engineers in Huawei to obtain the correct files. 2. Run the RST BRD command to reset the board. 3. Go back to step Step 19.
NOTE
You can obtain the correct board version mapping table by referring to section "Board Versions" in the release notes.
Step 21 Perform dialing tests and browse webpages to check that the boards provide functions properly. ----End
4.4.2 Adding the SPUa/SPUb Board

This section describes procedures and precautions for adding the SPUa/SPUb board.
Prerequisite
l Network design is complete. Network design involves planning of the quantity of NodeBs carried by each subrack, planning of the quantity of NodeBs carried by the SPUa/SPUb board or by each subsystem, and planing of slots for holding the boards. Contact Huawei to obtain the detailed network design scheme. l
4-12
The SPUa/SPUb board is ready.

Tools required for installing boards are ready. Tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, ESD box or bag, and dustfree cotton cloth.
Context
CAUTION
To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD wrist strap properly. Ensure that the ESD wrist strap is properly connected to the ESD connector on the cabinet. If no ESD wrist strap or no proper grounding point is available, wear ESD gloves.
WARNING
l Each MPU subsystem is in charge of 24 CPUS subsystems. l If slots in the subrack are all installed with SPUa boards, only one MPU subsystem must be configured. l If more than 24 CPUS subsystems are in the subrack, two MPU subsystems are required. If more than three pairs of active/standby SPUb boards are installed in the subrack, two MPU subsystems must be configured. l The SPUa/SPUb board works in active/standby mode; therefore, boards must be added in pairs. For example, add one or two pairs of active/standby SPUb boards. l When Data Configuration Modes of the subrack is effective mode, adding boards does not disrupt ongoing services of the BSC6900. l When the subrack is in ineffective mode, the subrack needs to be restarted after installing boards. Restarting subracks interrupts ongoing services.
Procedure
Step 1 Install the SPUb boards by referring to Inserting a Board. Step 2 Run the ADD BRD command to add the SPUa/SPUb board. For example,
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=SPUb, LGCAPPTYPE=UCP, SN=4, MPUSUBRACK=0, MPUSLOT=0;
Step 3 When the RUN on the board blinks every second (1s on, 1s off), run the DSP BRD command to query the new board status. If... The SPUb board does not work in active/standby mode. CPU status is Active normal. Then... Go to step Step 5.
Issue 03 (2010-09-20)
4-13
If... The SPUb boards work in active/standby mode. CPU status is Standby normal. CPU status is set to another value.
Then... Go to step Step 5.
Go to step Step 4.
Step 4 In the Browse Alarm tab page on the LMT, check whether alarms such as board fault alarms are reported. If... Alarms such as board fault alarms are reported. Then... 1. Find out the reason according to the alarms and clear them. 2. Go back to step Step 4. Alarms such as board fault alarms are not Go to step Step 5. reported. Step 5 Run the ADD BRD command to add the next SPUa/SPUb board. l Add the SPUa/SPUb board one by one. l Check board status after adding the board. If the board is normal and no alarm is generated, add the next board. Step 6 Configure the new board by referring to Configuring the Cell Data. If the NodeBs need to be reparented from another SPUa/SPUb board to the new board, perform the reparenting by referring to section "Reparenting UMTS NodeBs" in the RAN Reconfiguration Guide (CME-Based). Visit http://support.huawei.com to download the WRAN Reconfiguration Guide (CME-Based). ----End
4.4.3 Adding the DPUb/DPUe Board

This section describes procedures and precautions for adding the DPUb/DPUe board.
Prerequisite
l Network design is complete. Network design involves planning of traffic volume in each subrack, planning of the quantity of the DPUb/DPUe board, and planing of slots for holding the boards. Contact Huawei to obtain the detailed network design and planning scheme. l l The DPUb/DPUe board is ready. Tools required for replacing boards are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, and ESD box or bag.
4-14
Issue 03 (2010-09-20)
Context
CAUTION
CAUTION
l A board must be installed in the slot configured for this type of board. l If the DPUb board is configured in slot n of subrack m,then the DPUb board must be installed in slot n of subrack m. l Similarly, if the DPUe board is configured in slot n of subrack m, then the DPUe board instead of the DPUb board must be installed in slot n of subrack m. l Configure a slot for a DPU board each time; configuring slots for many DPU boards at the same time is forbidden. Adding the DPUb/DPUe board does not disrupt ongoing services of the BSC6900. You do not need to set the Data Configuration Modes of the subrack to .
Procedure
Step 1 Run the ADD BRD command to add a board.
ADD BRD: SRN=m, BRDCLASS=DPU, BRDTYPE=DPUe, SN=n, MPUSUBRACK=x, MPUSLOT=x;
Step 2 Run the INH BRD command to logically disable the board.
INH BRD: INHT=LOGIC, SRN=m, SN=n; //Logically disable the DPUb/DPUe board in slot n of subrack m.
Step 3 Install the board in slot n of subrack m. See Inserting a Board. Step 4 In five minutes, run the DSP DSP command to check the state of the DSP chip in the DPUb/ DPUe board.
DSP DSP: SRN=m, SN=n; Check the state of the DPUb/DPUe board in slot n of subrack m.
Step 5 After all the DSP chips in the DPUb/DPUe board are disabled, run the UIN BRD command to enable the DPUb/DPUe board.
UIN BRD: INHT=LOGIC, SRN=m, SN=n; //Enable the DPUb/DPUe board in slot n of subrack m.
Step 6 Repeat Step 1 through Step 5 to add the DPUb/DPUe board one by one. Step 7 Checking the boards status by referring to Checking the DPUb Board Status. ----End
4.4.4 Adding Interface Boards

This section describes procedures and precautions for adding interface boards.
Prerequisite
l Network design is complete. Network design involves planning of transmission methods of connecting the interface boards to other NEs, planning of types of interface boards, planning of overloads in each interface board, and planning of slots for holding interface boards. Contact Huawei to obtain the detailed network design and planning scheme. l Cables for connecting the interface boards are ready.
NOTE
Cables for connecting the interface boards are prepared according to the site survey report. Check cables used in the BSC6900 by referring to Cables.
l l
Peer equipment and transmission equipment connected to interface boards are ready. Tools required for installation are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, ESD box or bag, dustfree cotton cloth, and fiber cleaner.
Context
CAUTION
To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD wrist strap properly. Ensure that the ESD wrist strap is properly connected to the ESD connector on the cabinet. If no ESD wrist strap or no proper grounding point is available, wear ESD gloves. l l When the Data Configuration Modes of the subrack is effective mode, adding interface boards does not interrupt ongoing services of the BSC6900. When the subrack is in ineffective mode, the subrack needs to be restarted to add boards. Restarting subracks interrupts ongoing services.
Procedure
Step 1 If the new interface board adopts E1/T1 transmission or transmission over channelized STM-1 ports, the DIP switch for the board must be set. For example: AEUa/PEUa/EIUa, AOUa/POUa. See DIP Switches on Components to obtain the rules for setting the DIP switches. Step 2 Install the signal cable (Ethernet cable or optical fiber) and cables for extracting clock signals by referring to Installing the Signal Cables. Step 3 Install interface boards by referring to Inserting a Board. Step 4 Attaching the Engineering Labels to the Signal Cables. Step 5 Configure the new interface boards by referring to Configuring the Interfaces.
Step 6 Check the port according to the board type. For example, if the AOUa board is added, run the DSP OPT command to query the optical port status. Step 7 Query transmission link status according to the board type and transmission mode of the board. For example, if an AOUa board in ATM IMA transmission mode is added, run the DSP IMAGRP, DSP SAALLNK command to query the status of the IMA group and SAALLNK. Step 8 When the RUN on the board blinks every second (1s on, 1s off), run the DSP BRD command to query the new board status. If... The CPU Status is ACTIVE or STANDBY. The CPU Status is other status. Then... Go to step Step 10. Go to step Step 9.
Step 9 In the Browse Alarm tab page on the LMT, check whether alarms such as board fault alarms are reported. If... Alarms such as board fault alarms are reported. Then... 1. Find out the reason according to the alarms and clear them. 2. Go back to step Step 8. Alarms such as board fault alarms are not Go to step Step 10. reported. Step 10 Run the CMP BRDVER command to check whether software versions of the new boards follow the version mapping of the boards. If... Then...
The software versions of the new boards Go to Step 11. follow the version mapping of the boards. The software versions of the new boards 1. Check whether the program files of the OMUa board in the OMU active workspace do not follow the version mapping of the installation directory\bin\fam are correct. If boards. the program files are incorrect, contact Huawei engineers to obtain the correct files. 2. Run the RST BRD command to reset the board. 3. Go back to step Step 8.
NOTE
You can obtain the correct board version mapping table by referring to section "Board Versions" in the release notes.
Issue 03 (2010-09-20)
4-17
Step 11 Perform dialing test and browse websites to check that the new board provides functions properly. Step 12 Verifying Network Reliability. ----End
4.5 Removing Boards and Subracks

Removing boards interrupts services on these boards. Therefore, remove boards in the early morning when the traffic is low. 1. 2. 3. 4.5.1 Removing the SPUa/SPUb Board This section describes the procedures and precautions for removing the SPUa/SPUb board. 4.5.2 Removing the DPUb/DPUe Board This section describes procedures and precautions for removing the DPUb/DPUe board. 4.5.3 Removing Subracks This section describes procedures and precautions for removing subracks.
4.5.1 Removing the SPUa/SPUb Board

This section describes the procedures and precautions for removing the SPUa/SPUb board.
Context
In terms of logical function, the SPUa/SPUb board can be categorized into two types: Resource Management and UMTS RNC Control plane Process (RUCP) and UMTS RNC Control plane Process (UCP).
NOTE
l Subsystem 0 of the RUCP SPUa/SPUb board is the Main Processing Unit (MPU). The MPU manages other boards, such as the SPUs, DPUs, and interface boards in the same subrack. The RUCP SPUa/SPUb board can be removed only by modifying the MML command script in ineffective mode. l The MPU is not contained in the UCP SPUa/SPUb board and all subsystems are Signaling Processing Units (SPUs). The RUCP SPUa/SPUb board carries only the NodeB and transmission links. The UCP SPUa/SPUb board can be removed in effective mode.
The logical function of the board to be removed can be obtained by running the LST BRD command.
CAUTION
l Removing the SPUa/SPUb board disrupts the services in the cell and disconnects transmission links. It is not recommended that the SPUa/SPUb be removed. l If the SPUa/SPUb board must be removed in special scenarios, it is recommended that only the UCP SPUa/SPUb board be removed. l In principle, removing the RUCP SPUa/SPUb board is prohibited.
4-18
Issue 03 (2010-09-20)
Removing the SPUa/SPUb Board (UCP)

This section describes procedures and precautions for removing the SPUa/SPUb board whose logical function type is UCP.
Prerequisite
l Risk assessment is complete. Risk assessment is performed to evaluate the impact on services and transmission links due to NodeB reparenting, and the impact of NodeB reparenting on the target board. l Network design is complete. Network planning involves planning the quantity of NodeBs that can be carried by each subrack, each SPUa/SPUb board, and each subsystem. Contact Huawei to obtain the detailed risk assessment report and the network design scheme. l Tools required for removing the SPUa/SPUb board are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, and ESD box or bag.
Context
CAUTION
Table 4-3 Operation overview and impact on services Configuration Object on the Board BTS Impact on Services The BTS services are interrupted. l If all sublinks involved in a transmission link is configured on the board to be removed, this transmission link is disrupted. l If some sublinks involved in a transmission link is configured in another board, The transmission link is still available but the link capacity is reduced.
Operation Overview Configure the BTS on another board through the CME. 1. Remove the transmission links configured on the board. 2. Establish the transmission links on other SPUa/SPUb boards.
Transmission links such as the MTP3 link, SAAL link, M3UA link, and SCTP link
Configuration Object on the Board Iur SCCP connection
Impact on Services No impact
Operation Overview 1. Run the LST UIURCOMMSCCP command to check whether the board to be removed is configured with an Iur SCCP connection. 2. If an Iur SCCP connection is configured, run the MOD UIURCOMMSCCP command to configure the Iur SCCP connection on another SPUa/SPUb board. If no Iur SCCP connection is configured, no operation is required.
CBS address
No impact
1. Run the LST UCBSADDR command to check whether the board to be removed is configured with a CBS address. 2. If a CBS address is configured, run the MOD UCBSADDR command to configure the CBS address on another SPUa/ SPUb board. If no CBS address is configured, no operation is required.
4-20
Issue 03 (2010-09-20)
Configuration Object on the Board Iur-g interface connection
Operation Overview 1. Run the LST UIURGCONN command to check whether the board to be removed is configured with an Iur-g interface connection. 2. If an Iur-g interface connection is configured, run the MOD UIURGCONN command to configure the Iur-g interface connection on another SPUa/SPUb board. If no Iur-g interface connection is configured, no operation is required.
Procedure
Step 1 Backing Up the MML script and Database. Step 2 Record the slot number of the board to be removed for future check. Step 3 Reparent all NodeBs carried by the board to other boards. For the detailed operations, see RAN Reconfiguration Guide (CME-Based). Visit http://support.huawei.com to download the RAN Reconfiguration Guide (CME-Based). Step 4 Establish transmission links on other SPUa/SPUb boards. Table 4-4 Establishing transmission links on other SPUa/SPUb boards Transmission Links on the Board to Be Removed Searching Method Removing Procedure Establishing Transmission Links on Other SPUa/SPUb Boards Run the ADD MTP3LNK command to move the MTP3 link to another SPUa/SPUb board.
MTP3 link
Search for the command ADD MTP3LNK in the script to obtain the configuration of MTP3 links and SAAL links carried by the board to be removed.
Run the RMV MTP3LNK command to remove the MTP3 link.
Issue 03 (2010-09-20)
4-21
Transmission Links on the Board to Be Removed
Searching Method
Removing Procedure
Establishing Transmission Links on Other SPUa/SPUb Boards Run the MOD SAALLNK command to move the SAAL link to another SPUa/SPUb board.
SAAL link
For example, if the SPUa board to be removed locates in slot 2 of subrack o, search for SRN=0, SN=2.
The SAAL link does not need to be removed before being reestablished.
M3UA link
SCTP link
Search for the command ADD M3LNK in the script to obtain the configuration of M3UA links and SCTP links carried by the board to be removed. For example, if the SPUa board to be removed locates in slot 2 of cabinet o, search for SRN=0, SN=2.
Run the RMV M3LNK command to remove the M3UA link. The SCTP link does not need to be removed before being reestablished.
Run the ADD M3LNK command to move the M3UA link to another SPUa/ SPUb board. Run the MOD SCTPLNK command to move the SCTP link to another SPUa/SPUb board.
Step 5 Remove other configuration objects on the board. Table 4-5 Removing other configuration objects on the board Configuration Object on the Board The board added through the ADD UIURCOMMSCCP command when configuring the LCS feature is the board to be removed. Impact on Services No impact Operation Overview 1. Run the LST UIURCOMMSCCP command to check whether the board to be removed is the board added when configuring the Iur-g feature. 2. If yes, run the MOD UIURCOMMSCCP command to configure the LCS feature on another SPUa/SPUb board.
4-22
Issue 03 (2010-09-20)
Configuration Object on the Board The board added through the ADD UCBSADDR command when configuring the CBS feature is the board to be removed.
Operation Overview 1. Run the LST UCBSADDR command to check whether the board to be removed is the board added when configuring the CBS feature. 2. If yes, run the MOD UCBSADDR command to configure the CBS feature on another SPUa/SPUb board.
The board added through the ADD UIURGCONN command when configuring the Iur-g feature is the board to be removed.
No impact
1. Run the LST UIURGCONN command to check whether the board to be removed is the board added when configuring the Iur-g feature. 2. If yes, run the MOD UIURGCONN command to configure the Iur-g feature on another SPUa/SPUb board.
Step 6 Run the RMV BRD command to remove the board. Step 7 Remove the board by referring to Removing a Board. Step 8 Perform the drive tests to check that the BTS and transmission links are normal. ----End
Postrequisite
Put the removed board into the ESD box or bag to protect the board from ESD damage.
Removing the SPUa/SPUb Board (RUCP)

This section describes the procedures and precautions for removing the SPUa/SPUb board whose logical function type is RUCP.
Prerequisite
l Risk assessment is complete. Risk assessment includes assessment of the impact of the BSC6900 restart during board removal, assessment of the impact of NodeB reparenting during board removal on ongoing services, and assessment of the impact of NodeB reparenting on the target board. l Network design is complete. Network design involves planning of the quantity of NodeBs that can be carried by each subrack, each SPUa/SPUb board, and each subsystem. Contact Huawei to obtain the detailed risk assessment report and network design scheme. l Tools required for removing boards are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, and ESD box or bag.
Issue 03 (2010-09-20)
4-23
Context
CAUTION
To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD wrist strap properly. Ensure that the ESD wrist strap is properly connected to the ESD connector on the cabinet. If no ESD wrist strap or no proper grounding point is available, wear ESD gloves. The RUCP SPUa/SPUb board can be removed by modifying the MML script only in ineffective mode.
Procedure
Step 1 Backing Up the MML script and Database. Step 2 Record the slot number of the board to be removed for future check. Step 3 According to network design scheme, reparent the NodeBs carried by the board to be removed to another board. For details of the reparenting operations, see section "Reparenting UMTS NodeBs" in the RAN Reconfiguration Guide (CME-Based). Visit http://support.huawei.com to download the RAN Reconfiguration Guide (CME-Based). Step 4 Modify the MML script. 1. //Setting all subracks to ineffective mode Add the following MML command at the beginning of the exported configuration script. SET CFGDATAINEFFECTIVE:; 2. //Initializing configuration data on the OMU Add the following MML command following SET CFGDATAINEFFECTIVE in the MML script. RST DATA:; 3. Configure the logical function type of another SPUa/SPUb board in the same subrack as the RUCP SPUa/SPUb to be removed as RUCP. Add the following MML command following RST DATA:; //Configuring subsystem 0 of the SPUb board in slot 4 of subrack 0 as the MPU subsystem (Configuration data on the MPU subsystem of the board to be removed will be configured on this MPU subsystem.) ADD BRD: SRN=0, SN=4, BRDCLASS=XPU, BRDTYPE=SPUb, LGCAPPTYPE=RUCP; 4. Activate the license again. Add the following MML command at the end of the script. ACT LICENSE:; 5. Set all subracks to effective mode. Add the following MML command at the end of the script. SET CFGDATAEFFECTIVE:; 6.
4-24
Generate configuration data files

Add the following MML command at the end of the script. FMT DATA:; 7. Modify the script to configure the data configured in the SPUa/SPUb board to be removed in another SPUa/SPUb board. Search the script for the configuration data of the board to be removed. Then, configure this configuration data on another SPUa/SPUb board. For example, if you want to configure the configuration data of the board to be removed in slot 0 of subrack 1 on the SPUa/SPUb board in slot 4 of subrack 1, a. b. Type SRN=1, SN=0, in the Search dialog box to find all the configuration data in the board to be removed in slot 0 of subrack 1. Replace all SRN=1, SN=0, with SRN=1, SN=4, in the MML script.
NOTE
After this operation, l The boards in subrack 1 are affiliated to the MPU subsystem of the board in slot 4 instead of the original MPU subsystem of the board in slot 0. l Transmission links carried by the board to be removed in slot 0 of subrack 1 are carried by the SPUb board in slot 4 of subrack 1.
Step 5 Load the MML script by referring to Loading the MML Script. Step 6 Reset the BSC6900 by referring to Restarting the BSC6900. Step 7 Remove the board by referring to Removing a Board. Step 8 Perform dailing tests to check that the reparented NodeBs and transmission links are normal. ----End
Postrequisite
4.5.2 Removing the DPUb/DPUe Board

This section describes procedures and precautions for removing the DPUb/DPUe board.
Prerequisite
l Risk assessment is complete. Removing the DPUb/DPUe board decreases the capacity of the BSC6900. Risk evaluation is performed to evaluate the impact of capacity decrease of the BSC6900 on the network. Contact Huawei to obtain the detailed risk assessment report. l Tools required for removing boards are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver,and ESD box or bag.
Issue 03 (2010-09-20)
4-25
Context
CAUTION
CAUTION
Removing the DPUb/DPUe board decreases the capacity of the BSC6900.
Procedure
Step 1 Run the INH BRD command to logically disable the DPUb/DPUe board.
INH BRD: INHT=LOGIC, SRN=m, SN=n;
Step 2 In five minutes, remove the DPUb/DPUe board in slot n of subrack m. See Removing a Board. Step 3 Run the RMV BRD command to remove the DPUb/DPUe board in slot n of subrack m.
RMV BRD: SRN=m, SN=n;
Step 4 Repeat Step 1 through Step 3 to remove the DPUb/DPUe board one by one. ----End
Postrequisite
4.5.3 Removing Subracks

This section describes procedures and precautions for removing subracks.
Prerequisite
l Risk assessment is complete. Risk evaluation is performed to evaluate the risk of reparenting the NodeB when the subrack is removed (NodeB reparenting interrupts its ongoing services) and the impact of NodeB reparenting on the target subrack. l Network planning is complete. Network planning involves planning of NodeB carried by each subrack, by the SPUa/ SPUb board or by each subsystem. Contact Huawei to obtain the detailed risk assessment report and network design scheme. l Tools required for removing subracks are ready. The tools are the ESD wrist strap, Phillips screwdriver, straight screwdriver, ESD box or bag, and dustproof cap for optical fiber.
4-26
Context
CAUTION
CAUTION
Removing subracks interrupts services on these subracks.
Procedure
Step 1 Based on the network design, configure the target subrack to achieve NodeB reparenting by referring to WRAN Reconfiguration Guide (CME-Based). Visit http://support.huawei.com to download WRAN Reconfiguration Guide (CME-Based). Step 2 Remove the SPUa/SPUb board. Step 3 Remove the DPU board. Step 4 Remove the interface board. Step 5 Run the RMV BRD command to remove the MPU board. Step 6 Run the RMV SUBRACK command to remove the subrack. Step 7 Disconnect all the signal cables in the subrack. Disconnect optical fibers and put dustproof caps on the optical fiber connectors to keep them clean. Step 8 Unfasten the screws in the subrack by referring to Figure 4-3.
Issue 03 (2010-09-20)
4-27
Figure 4-3 Floating nuts installation
Step 9 Two people hold the mounting ears and support the base of the subrack, slide the subrack out of the cabinet. ----End
4-28
Issue 03 (2010-09-20)
5 Adjusting the NodeB
5
About This Chapter
Adjusting the NodeB
This chapter describes how to adjust or expand the operational NodeB. 5.1 Modifying the NodeB Clock Source or the Clock Working Mode This section describes how to modify the NodeB clock source and the working mode of the clock when the transport network is replanned. 5.2 Modifying NodeB Time Information This section describes how to modify NodeB time information when network time synchronization is not enabled on a NodeB and the time or time zone of the NodeB is inconsistent with the local time or time zone. The modifiable information consists of the NodeB time zone, daylight saving information, and SNTP synchronization period. 5.3 Adding the Board/Equipment to the NodeB This chapter describes how to add the board/equipment to the NodeB, including the board to the BTS3812E/BTS3812AE, the BBU3806/BBU3806C equipment to the DBS3800, the EBBC/ EBBCd board to the BBU3806, the EBBM board to the BBU3806C, and the WBBP board to the 3900 series base stations. 5.4 Configuring a Custom NodeB Alarm This section describes how to configure a custom NodeB alarm, including the custom alarm ID and alarm port.
Issue 03 (2010-09-20)
5-1
5.1 Modifying the NodeB Clock Source or the Clock Working Mode
This section describes how to modify the NodeB clock source and the working mode of the clock when the transport network is replanned.
Prerequisite
l The NodeB works properly.
Context
l l The type of clock source to be used by the NodeB may be line clock, IP clock, BITS clock, or GPS clock. The working mode may be MANUAL or FREE.
Procedure
Step 1 Run the NodeB MML command DSP CLKSTAT to query the current settings of the clock source and clock working mode. Step 2 If you need to change the current clock source, run the NodeB MML command SET CLKMODE to set the parameters. Otherwise, finish the task. Step 3 Run the NodeB MML command DSP CLKSTAT to check that the clock source and clock working mode are correctly modified. ----End
5.2 Modifying NodeB Time Information

This section describes how to modify NodeB time information when network time synchronization is not enabled on a NodeB and the time or time zone of the NodeB is inconsistent with the local time or time zone. The modifiable information consists of the NodeB time zone, daylight saving information, and SNTP synchronization period.
Prerequisite
The NodeB works properly.
Procedure
Step 1 Run the NodeB MML command LST TZ to query the time zone of the NodeB. If... The result shows that the time zone is incorrect, The result shows that the time zone is correct, Then... Go to step Step 2. Go to step Step 4.
5-2
Issue 03 (2010-09-20)
Step 2 Run the NodeB MML command SET TZ to modify the time zone and daylight saving information of the NodeB. When modifying the daylight saving policy, you need to specify the time offset and the start time and end time of the daylight saving period. Step 3 Run the NodeB MML command LST TZ to check that the time zone of the NodeB is correctly modified. Step 4 Run the NodeB MML command LST SNTPCLTPARA to query the SNTP client. If... The result is inconsistent with the SNTP server information, The result is consistent with the SNTP server information, Then... Go to step Step 5. End this task.
Step 5 Run the NodeB MML command SET SNTPCLTPARA to modify the SNTP client. Step 6 Run the NodeB MML command LST SNTPCLTPARA to check that the SNTP client is correctly modified. ----End
5.3 Adding the Board/Equipment to the NodeB

This chapter describes how to add the board/equipment to the NodeB, including the board to the BTS3812E/BTS3812AE, the BBU3806/BBU3806C equipment to the DBS3800, the EBBC/ EBBCd board to the BBU3806, the EBBM board to the BBU3806C, and the WBBP board to the 3900 series base stations. 5.3.1 Adding the Board to the BTS3812E/BTS3812AE This section describes how to expand the capacity of the BTS3812E/BTS3812AE by adding the baseband board, HBBI, EBBI, EULP/EULPd, or EDLP. 5.3.2 Adding the BBU3806/BBU3806C Equipment This section describes how to expand the capacity of the DBS3800 by adding the BBU3806/ BBU3806C equipment. 5.3.3 Adding the EBBC/EBBCd Board This section describes how to expand the capacity of the BBU3806 by adding the EBBC/EBBCd baseband board. 5.3.4 Adding the EBBM Board This section describes how to expand the capacity of the BBU3806C by adding the EBBM baseband board. 5.3.5 Adding the Board to 3900 Series Base Stations This section describes how to expand the capacity of the 3900 series base stations by adding the WBBP baseband board.
5.3.1 Adding the Board to the BTS3812E/BTS3812AE

This section describes how to expand the capacity of the BTS3812E/BTS3812AE by adding the baseband board, HBBI, EBBI, EULP/EULPd, or EDLP.
Prerequisite
l Before the board for capacity expansion is installed, the NodeB is upgraded to a version that is not earlier than the corresponding board-introducing version. For detailed operation steps, see the Upgrade Guide of the target version. Board HBBI EBBI EULP EDLP EULPd Board-Introducing Version Version earlier than RAN10.0 RAN10.0 RAN10.0 RAN11.0 RAN12.0
The HBBI, EBBI, EULP/EULPd, or EDLP board is installed and runs normally. For detailed installation steps, see the section "Installing the Boards and Modules" in the BTS3812E Installation Guide and the BTS3812AE Installation Guide. A license allowing a larger capacity is obtained and sent from the M2000 to the NodeB.
Procedure
Step 1 Log in to the NodeB LMT or the M2000. Step 2 Run the NodeB MML command ADD BRD to add the corresponding baseband board to the current NodeB. Step 3 Run the NodeB MML command MOD ULGROUP and MOD DLGROUP to add the new board to the corresponding uplink and downlink baseband resource groups. After the commands are executed successfully, the NodeB records the uplink and downlink baseband resource groups and the corresponding uplink and downlink resources. Step 4 Run the NodeB MML command ADD LOCELL to establish the relationship between the uplink and downlink baseband resource groups and the local cell. By doing this, the resources in the resource groups can be used by the NodeB to handle the uplink and downlink traffic. ----End
5.3.2 Adding the BBU3806/BBU3806C Equipment

This section describes how to expand the capacity of the DBS3800 by adding the BBU3806/ BBU3806C equipment.
Prerequisite
l Before the equipment for capacity expansion is installed, the NodeB is upgraded to a version that is not earlier than the corresponding equipment-introducing version. For detailed operation steps, see the Upgrade Guide of the target version. Equipment BBU3806/BBU3806C
5-4
Board-Introducing Version Version earlier than RAN10.0

Issue 03 (2010-09-20)
l l
The BBU3806/BBU3806C is installed and runs normally. For detailed installation steps, see the hardware installation part in the BBU3806 User Guide/BBU3806C User Guide. A license allowing a larger capacity is obtained and sent from the M2000 to the NodeB.
Procedure
Step 1 Log in to the NodeB LMT or the M2000. Step 2 Run the NodeB MML command ADD BRD to add the corresponding baseband board, UBTI to the current NodeB. Step 3 Run the NodeB MML command MOD ULGROUP and MOD DLGROUP to add the new board to the corresponding uplink and downlink baseband resource groups. After the commands are executed successfully, the NodeB records the uplink and downlink baseband resource groups and the corresponding uplink and downlink resources. Step 4 Run the NodeB MML command ADD LOCELL to establish the relationship between the uplink and downlink baseband resource groups and the local cell. By doing this, the resources in the resource groups can be used by the NodeB to handle the uplink and downlink traffic. ----End
5.3.3 Adding the EBBC/EBBCd Board

This section describes how to expand the capacity of the BBU3806 by adding the EBBC/EBBCd baseband board.
Prerequisite
l Before the board for capacity expansion is installed, the NodeB is upgraded to a version that is not earlier than the corresponding board-introducing version. For detailed operation steps, see the Upgrade Guide of the target version. Board EBBC EBBCd Board-Introducing Version RAN10.0 RAN12.0
l l
The EBBC/EBBCd board is installed and runs normally. For detailed installation steps, see the hardware installation part in the BBU3806 User Guide. A license allowing a larger capacity is obtained and sent from the M2000 to the NodeB.
Procedure
Step 1 Log in to the NodeB LMT or the M2000. Step 2 Run the NodeB MML command ADD BRD to add the corresponding baseband board to the current NodeB. Step 3 Run the NodeB MML command MOD ULGROUP and MOD DLGROUP to add the new board to the corresponding uplink and downlink baseband resource groups. After the commands
are executed successfully, the NodeB records the uplink and downlink baseband resource groups and the corresponding uplink and downlink resources. Step 4 Run the NodeB MML command ADD LOCELL to establish the relationship between the uplink and downlink baseband resource groups and the local cell. By doing this, the resources in the resource groups can be used by the NodeB to handle the uplink and downlink traffic. ----End
5.3.4 Adding the EBBM Board

This section describes how to expand the capacity of the BBU3806C by adding the EBBM baseband board.
Prerequisite
l Before the board for capacity expansion is installed, the NodeB is upgraded to a version that is not earlier than the corresponding board-introducing version. For detailed operation steps, see the Upgrade Guide of the target version. Board EBBM l l Board-Introducing Version RAN10.0
The EBBM board is installed and runs normally. For detailed installation steps, see the hardware installation part in the BBU3806C User Guide. A license allowing a larger capacity is obtained and sent from the M2000 to the NodeB.
Procedure
5.3.5 Adding the Board to 3900 Series Base Stations

This section describes how to expand the capacity of the 3900 series base stations by adding the WBBP baseband board.
Prerequisite
l Before the board for capacity expansion is installed, the NodeB is upgraded to a version that is not earlier than the corresponding board-introducing version. For detailed operation steps, see the Upgrade Guide of the target version.
5-6
Board WBBPa/WBBPb WBBPd
Board-Introducing Version RAN10.0 RAN12.0
l l
The WBBP board is installed and runs normally. For detailed installation steps, see the BBU3900 Installation Guide. A license allowing a larger capacity is obtained and sent from the M2000 to the NodeB.
Procedure
5.4 Configuring a Custom NodeB Alarm

This section describes how to configure a custom NodeB alarm, including the custom alarm ID and alarm port.
Prerequisite
l l l The board and the cable corresponding to the external alarm are installed. The board corresponding to the external alarm is configured. You have logged in to the M2000 client successfully.
Context
The following table lists the data to be negotiated and planned for configuring a custom NodeB alarm. Table 5-1 Data to be negotiated and planned for configuring a custom NodeB alarm Parameter Cabinet No. Subrack No.
Issue 03 (2010-09-20)
Example 0 0
Source Network planning Network planning

5-7
Parameter Slot No. Port No. Working mode Port type Alarm ID Alarm level
Example 0 6 CUSTOM BOOL 65035 HIGH
Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 Run the NodeB MML command SET ALMPORT to set the external alarm port and bind the custom alarm ID to the external alarm port. Step 2 On the M2000, choose Monitor > Alarm Setting > NE Alarm Setting. Step 3 In the displayed window, click the User-Defined Alarm > Alarm Definition tab page and click Add. Then set the parameters related to a custom alarm such as NE Type, Alarm Name, Alarm ID, and Alarm Level (alarm severity). ----End
5-8
Issue 03 (2010-09-20)
6 Reconfiguring the UMTS Network
Reconfiguring the UMTS Network
About This Chapter

This chapter describes how to carry out common network reconfiguring tasks in the functioning BSC6900. 6.1 Reconfiguring a Cell This section describes how to reconfigure a cell, including cell parameters. 6.2 Reconfiguring the Channel This section describes how to reconfigure the channel parameters. 6.3 Reconfiguring Neighboring Cells This section describes how to reconfigure neighboring cells, including intra-frequency cells, inter-frequency cells, and neighboring GSM cells. 6.4 Reconfiguring Timeslot Cross Connection This section describes how to reconfigure timeslot cross connection on a BSC6900 and on a NodeB.
Issue 03 (2010-09-20)
6-1
6.1 Reconfiguring a Cell

This section describes how to reconfigure a cell, including cell parameters. 6.1.1 Modifying the Power of a Cell This section describes how to modify the maximum transmit power of a cell or the power of different channels in the cell when the network is optimized. 6.1.2 Modifying Cell Frequencies This section describes how to modify cell frequencies (including UL frequency and DL frequency) when the capacity of a TRX is expanded or cell frequencies are replanned. 6.1.3 Modifying the Scrambling Code of a Cell This section describes how to modify the DL primary scramble code of a cell when cell scramble codes are replanned after capacity expansion. 6.1.4 Modifying Cell System Message Parameters This section describes how to modify cell system information parameters when the network is optimized. The parameters are cell system information block switch, cell access restriction information, cell selection/reselection information, and cell measurement control information. 6.1.5 Modifying Cell Radio Link Parameters This section describes how to modify cell radio link parameters when the network is optimized to solve the specific call drop problem. The modifiable parameter is the radio link power. 6.1.6 Modifying Cell Synchronization Parameters This section describes how to modify the cell synchronization parameters when the network is optimized to solve problems such as access problems and call drops. 6.1.7 Modifying the Area Information of a Cell This section describes how to modify the area information of a cell when some areas are replanned or a NodeB is cut over. These areas are location areas, service areas, and routing areas. 6.1.8 Modifying the UTRAN Registration Area of a Cell This section describes how to modify the UTRAN registration area (URA) of a cell when URAs are replanned. 6.1.9 Renaming a Cell This section describes how to rename a cell when the network is optimized, such as, when cell information is replanned. 6.1.10 Changing the ID of a Cell This section describes how to change the ID of a cell when the network is optimized, such as, when cell information is replanned.
6.1.1 Modifying the Power of a Cell

This section describes how to modify the maximum transmit power of a cell or the power of different channels in the cell when the network is optimized.
Prerequisite
l The BSC6900 and the NodeB work properly.
6-2
Issue 03 (2010-09-20)
The current user has the BSC6900 control rights concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Context
You can modify the following power parameters: l l l l l l l l l l Maximum transmit power of the cell PCPICH power Max./Min. TX power of the PCPICH PSCH power SSCH power AICH power PICH power BCH power PCH power Max. TX power of the FACH
CAUTION
l If the Max. TX power of the cell at the BSC6900 is greater than that at the NodeB, the logical cell cannot be set up or the cell reconfiguration process fails. l If the Max. TX power of the cell at the BSC6900 is too small, the cell reconfiguration process fails. l The Max. TX power of the BSC6900 and NodeB must be the same.
NOTE
Among these parameters, the Physical Common Pilot Channel (PCPICH) power, Max./Min. TX power of the PCPICH, and Max. TX power of the cell are absolute values. The rest of the parameters are power offsets from the PCPICH power. If the cell is in service, modifying the Max. TX power of the cell or the PCPICH/PSCH /SSCH/BCH power can trigger the CELL RECONFIGURATION process on the Iub interface. If the Secondary-Common Control Physical Channel (SCCPCH) or Physical Random Access Channel (PRACH) is in service, modifying the Max. TX power of the FACH or the PCH/PICH/ AICH power can trigger the COMMON TRANSPORT CHANNEL RECONFIGURATION process on the Iub interface.
l l
Procedure
l Modify the maximum transmit power of the cell. 1. 2. On the BSC6900 LMT, run the LST UCELL command to view the maximum transmit power of the logical cell. On the BSC6900 LMT, run the MOD UCELL command to modify the maximum transmit power of the logical cell.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6-3
Issue 03 (2010-09-20)
3. 4. 5. l
On the NodeB LMT, run the LST LOCELL command to view the maximum transmit power of the local cell that corresponds to the logical cell. On the NodeB LMT, run the MOD LOCELL command to change the maximum transmit power of the local cell that corresponds to the logical cell. On the BSC6900 LMT, run the LST UCELL and on the NodeB LMT run the LST LOCELL commands to check whether the modification is successful. Run the LST UPCPICH command to view the transmit power of the PCPICH. Run the MOD UCELL command to modify the transmit power of the PCPICH. Run the LST UPCPICH command to check whether the modification is successful. Run the LST UPCPICH command to view the transmit power of the PCPICH. Run the MOD UPCPICHPWR command to modify the transmit power of the PCPICH. Run the LST UPCPICH command to check whether the modification is successful. Run the LST UPCPICH command to view the transmit power of the PCPICH. Run the MOD UPCPICHPWR command to modify the transmit power of the PCPICH. Run the LST UPCPICH command to check whether the modification is successful. Run the LST UPSCH command to view the power of the PSCH. Run the MOD UCELL command to modify the power of the PSCH. Run the LST UPSCH command to check whether the modification is successful. Run the LST USSCH command to view the power of the SSCH. Run the MOD UCELL command to modify the power of the SSCH. Run the LST USSCH command to check whether the modification is successful. Run the LST UCHPWROFFSET command to view the power offset of the AICH. Run the MOD UAICHPWROFFSET command to modify the power offset of the AICH. Run the LST UCHPWROFFSET command to check whether the modification is successful. Run the LST UCHPWROFFSET command to view the power offset of the PICH. Run the MOD UPICHPWROFFSET command to modify the power offset of the PICH. Run the LST UCHPWROFFSET command to check whether the modification is successful. Run the LST UBCH command to view the power of the BCH.
Modify the transmit power of the PCPICH. 1. 2. 3.
Modify the maximum transmit power of the PCPICH. 1. 2. 3.
Modify the minimum transmit power of the PCPICH. 1. 2. 3.
Modify the power of the PSCH. 1. 2. 3.
Modify the power of the SSCH. 1. 2. 3.
Modify the power offset of the AICH. 1. 2. 3.
Modify the power offset of the PICH. 1. 2. 3.
Modify the transmit power of the BCH. 1.
6-4
2. 3. l 1. 2. 3. l 1. 2. 3. ----End
Run the MOD UCELL command to modify the power of the BCH. Run the LST UBCH command to check whether the modification is successful. Run the LST UPCH command to view the power of the PCH. Run the MOD USCCPCH command to modify the power of the PCH. Run the LST UPCH command to check whether the modification is successful. Run the LST UFACH command to view the maximum transmit power of the FACH. Run the MOD USCCPCH command to modify the maximum transmit power of the FACH. Run the LST UFACH command to check whether the modification is successful.
Modify the power of the PCH.
Modify the maximum transmit power of the FACH.
6.1.2 Modifying Cell Frequencies

This section describes how to modify cell frequencies (including UL frequency and DL frequency) when the capacity of a TRX is expanded or cell frequencies are replanned.
Prerequisite
l l The BSC6900 and the NodeB work properly. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Context
When the cell frequency is changed, the neighbor relations are deleted. Plan and add the neighboring cells by referring to 6.3 Reconfiguring Neighboring Cells.
Procedure
Step 1 On the BSC6900 LMT: 1. 2. 3. Run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. Run the DEA UCELL command to deactivate the cell. Run the RMV UNRELATION command to remove the bidirectional neighbor relations of the cell.
NOTE
The RMV UNRELATION command can only remove the bidirectional neighbor relations of the cell in only one BSC6900. To remove the relationship between the existing cell and the neighboring cells in another BSC6900, use this command on that BSC6900.
4. 5.
Issue 03 (2010-09-20)
Run the MOD UCELLSETUP command to modify cell frequencies. Run the LST UCELL command to check whether the modification is correct.
Step 2 On the NodeB LMT, run the MOD LOCELL command to modify cell frequencies. Step 3 On the BSC6900 LMT, run the ACT UCELL command to activate the cell. Step 4 On the BSC6900 LMT, run the DSP UCELL command to check whether the status of the cell is normal. Step 5 Reconfigure the neighboring cell data after the cell frequencies are changed by referring to 6.3 Reconfiguring Neighboring Cells. ----End
6.1.3 Modifying the Scrambling Code of a Cell

This section describes how to modify the DL primary scramble code of a cell when cell scramble codes are replanned after capacity expansion.
Prerequisite
l l The BSC6900 works properly. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Procedure
Step 1 Run the HO UCELL command to force the handover of UEs in a cell to a neighboring cell. Step 2 Run the DEA UCELL command to deactivate the cell. Step 3 Run the LST UCELL command to view the basic data of the cell. Step 4 Run the MOD UCELLSETUP command to modify the primary DL scrambling code of the cell. Step 5 Run the ACT UCELL command to activate the cell. Step 6 Run the DSP UCELL command to check whether the status of the cell is normal. Step 7 Run the LST UCELL command to check whether the modification is successful. ----End
6.1.4 Modifying Cell System Message Parameters

This section describes how to modify cell system information parameters when the network is optimized. The parameters are cell system information block switch, cell access restriction information, cell selection/reselection information, and cell measurement control information.
Prerequisite
l
6-6
The BSC6900 works properly.

The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Procedure
l Modify cell system information block switch. 1. 2. 3. l Run the LST UCELLSIBSWITCH command to view the cell system information switches. Run the MOD UCELLSIBSWITCH command to modify the cell system information switches. Run the LST UCELLSIBSWITCH command to check whether the modification is correct. Run the LST UCELLACCESSSTRICT command to view the cell access restriction information. Run the MOD UCELLACCESSSTRICT command to modify the cell access restriction information. Run the LST UCELLACCESSSTRICT command to check whether the modification is correct. Run the LST UCELLSELRESEL command to view the cell selection/reselection information. Run the MOD UCELLSELRESEL command to modify the cell selection/reselection information. Run the LST UCELLSELRESEL command to check whether the modification is correct. Run the LST UCELLMEAS command to view the cell measurement control information. Run the MOD UCELLMEAS command to modify the cell measurement control information. Run the LST UCELLMEAS command to check whether the modification is correct.
Modify the cell access restriction information. 1. 2. 3.
Modify the cell selection/reselection information. 1. 2. 3.
Modify the cell measurement control information. 1. 2. 3.
----End
6.1.5 Modifying Cell Radio Link Parameters

This section describes how to modify cell radio link parameters when the network is optimized to solve the specific call drop problem. The modifiable parameter is the radio link power.
Prerequisite
l The BSC6900 works properly.
Issue 03 (2010-09-20)
6-7
Context
When the cell is activated, you can view, modify, remove, or add the cell radio link power of the CS/PS traffic rate. The new settings are sent to the NodeB in the NBAP RADIO LINK SETUP REQUEST message through the Iub interface. The settings are used to control the power. If there are no data matching the traffic rate requested by the UE in the database, the system uses the power data with the closest rate.
Procedure
l Set the cell radio link power. 1. 2. Run the LST UCELLRLPWR command to view the settings of the cell radio link power. Set the cell radio link power. Run the MOD UCELLRLPWR command to modify cell DL transmit power. Run the ADD UCELLRLPWR command to add cell DL transmit power parameter. Run the RMV UCELLRLPWR command to remove cell DL transmit power. 3. ----End Run the LST UCELLRLPWR command to check whether the modification is correct.
6.1.6 Modifying Cell Synchronization Parameters

This section describes how to modify the cell synchronization parameters when the network is optimized to solve problems such as access problems and call drops.
Prerequisite
Context
CAUTION
Modifying the cell synchronization attributes can trigger the CELL RECONFIGURATION process on the Iub interface.
6-8
Issue 03 (2010-09-20)
Cell synchronization parameters include: l l l NInsyncInd: Number of successive synchronization indications NOutsyncInd: Number of successive out-of-synchronization indications TRlFailure: Timer length of radio link failure
Procedure
Step 1 Run the LST UCELL command to view the cell information. Step 2 Run the MOD UCELL command to modify the cell synchronization parameters. Step 3 Run the LST UCELL command to check whether the modification is successful. ----End
6.1.7 Modifying the Area Information of a Cell

This section describes how to modify the area information of a cell when some areas are replanned or a NodeB is cut over. These areas are location areas, service areas, and routing areas.
Prerequisite
Context
The area information of a cell is configured.
Procedure
Step 1 Run the LST UCELL command to view the basic data of the cell. Step 2 Run the MOD UCELLACINFO command to modify the LAC, RAC, and SAC of the cell. Step 3 Run the LST UCELL command to check whether the modification is successful. ----End
6.1.8 Modifying the UTRAN Registration Area of a Cell

This section describes how to modify the UTRAN registration area (URA) of a cell when URAs are replanned.
Prerequisite
l l The BSC6900 works properly. The specified URA ID of the cell must be configured as the global information. You can check the information through the LST UURA command.
Context
A cell can belong to up to eight URAs. After the cell is activated, you can add the URA dynamically according to your requirements.
Procedure
Step 1 Run the LST UCELLURA command to view the cell URA information. Step 2 Configure the cell URA. If... You need to remove a cell URA, You need to add a cell URA, Then... Run the RMV UCELLURA command. Run the ADD UCELLURA command.
You need to modify the cell URA from 1. Run the ADD UCELLURA to add the A to B, reference of the cell to URA B. 2. Run the RMV UCELLURA to remove the reference of the cell to URA A. Step 3 Run the LST UCELLURA command to check whether the modification is correct. ----End
6.1.9 Renaming a Cell

This section describes how to rename a cell when the network is optimized, such as, when cell information is replanned.
Prerequisite
l The basic data of the cell is added. Run the LST UCELL command to view the basic data of the cell. If the basic data of the cell is not configured, run the ADD UCELLSETUP to add the basic data of the cell. l l The BSC6900 and the NodeB work properly. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
6-10
Procedure
Step 1 Run the LST UCELL command to view the cell name. Step 2 Run the MOD UCELLNAME command to modify the cell name. Step 3 Run the LST UCELL command to check whether the modification is correct. ----End
6.1.10 Changing the ID of a Cell

This section describes how to change the ID of a cell when the network is optimized, such as, when cell information is replanned.
Prerequisite
l l l The BSC6900 and the NodeB work properly. The cell is configured. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Procedure
Step 1 Run the DSP UCELL command to view the status of the cell. If... The cell is in an active state, The cell is not in an active state, Then... Go to step Step 2. Go to step Step 4.
Step 2 Run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. Step 3 Run the DEA UCELL command to deactivate the cell. Step 4 Run the MOD UCELLID command to modify the cell ID. Step 5 Run the LST UCELL command to check that the modification is correct. Step 6 Run the ACT UCELL command to reactivate the cell, and then run the DSP UCELL command to check that the status of the cell is normal. ----End
6.2 Reconfiguring the Channel

This section describes how to reconfigure the channel parameters.
Issue 03 (2010-09-20)
6-11
6.2.1 Modifying a PRACH This section describes how to modify a physical random access channel (PRACH) in the cell when the network is optimized to solve an access problem. The modifiable data is the preamble signature, RACH subchannel ID, PRACH timeslot format, Uu interface update parameters of the PRACH, access service class information of the PRACH, information on the mapping between the access class and access service class of the PRACH, CTFC information of the PRACH, timeslot format information of the PRACH, random back-off lower limit of the RACH, random back-off upper limit of the RACH, maximum times of preamble loop of the RACH, basic information of the RACH, dynamic TX format set information of the RACH, and AICH information. 6.2.2 Removing a PRACH This section describes how to remove a PRACH from a logical cell when the network is optimized to solve an access problem. 6.2.3 Modifying an SCCPCH This section describes how to modify a secondary-common control physical channel (SCCPCH) in a cell when the network is optimized. The modifiable data is time window and power of the PCH, time window and power of the FACH, CTFC information of the SCCPCH, basic information of the FACH, dynamic TX format set of the FACH, logical channels mapped to the FACH, basic information of the PCH, dynamic TX format set of the PCH, and PICH information. 6.2.4 Removing an SCCPCH This section describes how to remove an SCCPCH from a logical cell when the network is optimized.
6.2.1 Modifying a PRACH

This section describes how to modify a physical random access channel (PRACH) in the cell when the network is optimized to solve an access problem. The modifiable data is the preamble signature, RACH subchannel ID, PRACH timeslot format, Uu interface update parameters of the PRACH, access service class information of the PRACH, information on the mapping between the access class and access service class of the PRACH, CTFC information of the PRACH, timeslot format information of the PRACH, random back-off lower limit of the RACH, random back-off upper limit of the RACH, maximum times of preamble loop of the RACH, basic information of the RACH, dynamic TX format set information of the RACH, and AICH information.
Prerequisite
l l l The PRACH to be modified exists in the cell. The BSC6900 works properly. The current user has the BSC6900 control rights concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Context
NOTE
To make the settings of the PRACH take effect after the modification, you need to use the DEA UPRACH command to deactivate the PRACH before the modification. After the modification, run the ACT UPRACH command to activate the PRACH.
6-12
Issue 03 (2010-09-20)
Procedure
l To modify the preamble signature, RACH subchannel ID or PRACH timeslot format, perform the following steps: 1. 2. Run the LST UPRACH command to view the configuration information of the specified PRACH. Run the MOD UPRACH command to reconfigure the PRACH.
NOTE
If the PRACH is in service, operations in previous steps can trigger the COMMON TRANSPORT CHANNEL RECONFIGURATION process on the Iub interface.
3. l 1. 2. 3. l 1. 2. 3. l
Run the LST UPRACH command to check whether the modification is correct. Run the LST UPRACH command to view the Uu interface update parameters of the PRACH. Run the MOD UPRACHUUPARAS command to modify the Uu interface update parameters of the PRACH. Run the LST UPRACH command to check whether the modification is correct. Run the LST UPRACH command to view the access service class information of the PRACH. Run the MOD UPRACHASC command to modify the access service class information of the PRACH. Run the LST UPRACH command to check whether the modification is correct.
To modify the Uu interface update parameters of the PRACH, perform the following steps:
To modify the access service class information of the PRACH, perform the following steps:
To modify the information on the mapping between the access class and access service class of the PRACH, perform the following steps: 1. 2. 3. Run the LST UPRACH command to view the information on the mapping between the access class and access service class of the PRACH. Run the MOD UPRACHACTOASCMAP command to modify the information on the mapping between the access class and access service class of the PRACH. Run the LST UPRACH command to check whether the modification is correct. If the cell is in service and there is only one PRACH in the cell, run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. If the cell is in an active state and there is only one PRACH in the cell, run the DEA UCELL command to deactivate the cell. If the PRACH is in active state, run the DEA UPRACH command to deactivate it. Run the LST UPRACH command to view the CTFC information of the PRACH. To remove the CTFC information of the PRACH, run the RMV UPRACHTFC command. To add the CTFC information of the PRACH, run the ADD UPRACHTFC command. Run the ACT UPRACH command to activate the PRACH. Run the ACT UCELL command to activate the cell. Run the LST UPRACH command to check whether the operation result is correct.
To modify the CTFC information of the PRACH, perform the following steps: 1. 2. 3. 4. 5. 6. 7. 8. 9.
l
Issue 03 (2010-09-20)
To modify the timeslot format of the PRACH, perform the following steps:
1. 2. 3. 4. 5. 6. 7. 8. 9. l
If the cell is in service and there is only one PRACH in the cell, run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. If the cell is in an active state and there is only one PRACH in the cell, run the DEA UCELL command to deactivate the cell. If the PRACH is in active state, run the DEA UPRACH command to deactivate it. Run the LST UPRACH command to view the timeslot format information of the PRACH. To remove the timeslot format information of the PRACH, run the RMV UPRACHSLOTFORMAT command. To add the timeslot format information of the PRACH, run the ADD UPRACHSLOTFORMAT command. Run the ACT UPRACH command to activate the PRACH. Run the ACT UCELL command to activate the cell. Run the LST UPRACH command to check whether the operation result is correct.
To modify the random back-off lower limit, random back-off upper limit and maximum number of preamble loops of the RACH, perform the following steps: 1. 2. 3. 4. 5. 6. 7. 8. If the cell is in service and there is only one PRACH in the cell, run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. If the cell is in an active state and there is only one PRACH in the cell, run the DEA UCELL command to deactivate the cell. If the PRACH is in active state, run the DEA UPRACH command to deactivate it. Run the LST URACH command to view the TX parameters of the RACH. Run the MOD URACH command to modify the TX parameters of the RACH. Run the ACT UPRACH command to activate the PRACH. Run the ACT UCELL command to activate the cell. Run the LST URACH command to check whether the operation result is correct. If the cell is in service and there is only one PRACH in the cell, run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. If the cell is in an active state and there is only one PRACH in the cell, run the DEA UCELL command to deactivate the cell. If the PRACH is in active state, run the DEA UPRACH command to deactivate it. Run the LST URACH command to view the RACH information. To remove the basic data of the RACH, run the RMV URACH command. Ensure that the dynamic TX format set information of the RACH is removed before this operation. To add the basic data of the RACH, run the ADD URACH command. Run the ADD URACHDYNTFS command to restore the dynamic TX format set information of the RACH, and then run the ACT UPRACH command to activate the PRACH. Run the ACT UCELL command to activate the cell. Run the LST URACH command to check whether the operation result is correct.
To modify the basic data of the RACH, perform the following steps: 1. 2. 3. 4. 5.
6. 7.
8. 9. l
To modify the dynamic TX format set information of the RACH, perform the following steps:
6-14
1. 2. 3. 4. 5. 6. 7. 8. 9. l 1. 2. 3. 4. 5. 6. 7. 8. 9. ----End
If the cell is in service and there is only one PRACH in the cell, run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. If the cell is in an active state and there is only one PRACH in the cell, run the DEA UCELL command to deactivate the cell. If the PRACH is in active state, run the DEA UPRACH command to deactivate it. Run the LST URACH command to view the RACH information. To remove the dynamic TX format set information of the RACH, run the RMV URACHDYNTFS command. To add the dynamic TX format set information of the RACH, run the ADD URACHDYNTFS command. Run the ACT UPRACH command to activate the PRACH. Run the ACT UCELL command to activate the cell. Run the LST URACH command to check whether the operation result is correct. If the cell is in service and there is only one PRACH in the cell, run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. If the cell is in an active state and there is only one PRACH in the cell, run the DEA UCELL command to deactivate the cell. If the PRACH is in active state, run the DEA UPRACH command to deactivate it. Run the LST UAICH command to view the AICH information. To remove the AICH, run the RMV UAICH command. To add the AICH, run the ADD UAICH command. Run the ACT UPRACH command to activate the PRACH. Run the ACT UCELL command to activate the cell. Run the LST UAICH command to check whether the operation result is correct.
To modify the AICH information, perform the following steps:
6.2.2 Removing a PRACH

This section describes how to remove a PRACH from a logical cell when the network is optimized to solve an access problem.
Prerequisite
Issue 03 (2010-09-20)
6-15
Context
NOTE
Whether to activate the cell before running the RMV UPRACH command depends on the number of PRACHs in the cell. You are advised, however, to deactivate the cell. l l If the cell has only one PRACH, you must deactivate the cell before running the RMV UPRACH command. If there are two PRACHs in the cell, you can run the RMV UPRACH command to remove a PRACH with the larger channel ID when the cell is in an active state.
Procedure
Step 1 On the RNC LMT, run the LST UPRACH command to view the PRACH of the cell. Step 2 Perform the appropriate step based on the status of the cell. If... The cell is in service, and you want to remove the PRACH when the cell is in an active state, If the cell is in an active state and you want to remove the PRACH when the cell is not in an active state, Then... Run the DEA UPRACH to deactivate the PRACH to be removed.
1. Force the handover of UEs from the cell to a neighboring cell by running the HO UCELL command. 2. Run the DEA UCELL command to deactivate the cell.
Step 3 Run the RMV UPRACH command to remove the PRACH. Step 4 If the cell has another PRACH and you need the deactivated cell to re-enter the service state, run the ACT UCELL command to activate the cell. Step 5 Run the LST UPRACH command to check whether the operation is successful. ----End
6.2.3 Modifying an SCCPCH

This section describes how to modify a secondary-common control physical channel (SCCPCH) in a cell when the network is optimized. The modifiable data is time window and power of the PCH, time window and power of the FACH, CTFC information of the SCCPCH, basic information of the FACH, dynamic TX format set of the FACH, logical channels mapped to the FACH, basic information of the PCH, dynamic TX format set of the PCH, and PICH information.
Prerequisite
l l The BSC6900 works properly. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL.
6-16
The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Context
CAUTION
Recalculate the CTFC of the SCCPCH if any one of the following parameters changes: number of FACHs, number of PCHs, TFS of the FACH, and TFS of the PCH.
Procedure
l Modify the attributes of the PCH and FACH. 1. 2. 3. l Run the LST UFACH command or LST UPCH command to view the data of the SCCPCH to be modified. Run the MOD USCCPCH command to reconfigure the SCCPCH. Run the LST UFACH command or LST UPCH command to check whether the modification is correct.
NOTE
Modify the CTFC of the SCCPCH.

If the cell in service has only one SCCPCH, or if it has two SCCPCHs but the one with the smaller channel ID needs to be modified, then do as follows: 1. Run the HO UCELL command to force the handover of UEs from the cell to a neighboring cell. 2. Run the DEA UCELL command to deactivate the cell. 3. After the modification, run the ACT UCELL command to activate the cell.
1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST USCCPCH command to view the CTFC of the SCCPCH. Modify the CTFC of the SCCPCH. If... You need to remove the CTFC of the SCCPCH, You need to add the CTFC of the SCCPCH, Then... Run the RMV USCCPCHTFC command. Run the ADD USCCPCHTFC command.
4. 5. l
Run the LST USCCPCH command to check whether the modification is correct. Run the ACT USCCPCH command to activate the SCCPCH.
NOTE
Modify the basic data of the FACH.

Issue 03 (2010-09-20)
6-17
1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST UFACH command to view the basic data of the FACH. Modify the basic data of the FACH. Before removing the basic data of the FACH, ensure that the FACH dynamic transport format, FACH logical channel, and carried CTCH are removed. You can restore the removed basic data of the FACH. The data includes the FACH dynamic transport format, FACH logical channel, and carried CTCH. If... You need to remove the basic data of the FACH, You need to add the basic data of the SCCPCH, Then... Run the RMV UFACH command.
Run the ADD UFACH command.
4. 5. l
Run the LST UFACH command to check whether the modification is correct. Run the ACT USCCPCH command to activate the SCCPCH.
NOTE
Modify the FACH dynamic transport format set.

1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST UFACH command to view the FACH dynamic transport format set. Modify the dynamic transport format set of the FACH. If... You need to remove the FACH dynamic transport format set, You need to add the FACH dynamic transport format set, Then... Run the RMV UFACHDYNTFS command.
Run the ADD UFACHDYNTFS command.
4. 5. l
Run the LST UFACH command to check whether the FACH dynamic transport format is correctly modified. Run the ACT USCCPCH command to activate the SCCPCH.
Modify the logical channels mapped to the FACH.
6-18
Issue 03 (2010-09-20)

NOTE
1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST UFACH command to view the logical channels mapped to the FACH. Modify the logical channels mapped to the FACH. Before removing the logical channels mapped to the FACH, ensure that the CTCH carried on the FACH is removed. You can restore the removed logical channels mapped to the FACH. For example, you can restore the CTCH carried on the FACH. If... You need to delete the logical channels mapped to the FACH, You need to add the logical channels mapped to the FACH, Then... Run the RMV UFACHLOCH command. Run the ADD UFACHLOCH command.
4. 5. l
Run the LST UFACH command to check whether the information about the logical channels mapped to the FACH is correct. Run the ACT USCCPCH command to activate the SCCPCH.
NOTE
Modify the basic data of the PCH.

1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST UPCH command to view the data of the PCH. Modify the basic data of the PCH. Before removing the basic data of the PCH, ensure that the dynamic transport format set of the PCH is removed. You can restore the removed basic data of the PCH, such as the dynamic transport format set of the PCH. If... You need to delete the basic data of the PCH, You need to add the basic data of the PCH, Then... Run the RMV UPCH command. Run the ADD UPCH command.
Issue 03 (2010-09-20)
6-19
4. 5. l
Run the LST UPCH command to check whether the modification is correct. Run the ACT USCCPCH command to activate the SCCPCH.
Modify the PCH dynamic transport format set.

NOTE
1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST UPCH command to view the PCH dynamic transport format set. Modify the dynamic transport format set of the PCH. If... You need to remove the PCH dynamic transport format set, You need to add the PCH dynamic transport format set, Then... Run the RMV UPCHDYNTFS command. Run the ADD UPCHDYNTFS command.
4. 5. l
Run the LST UPCH command to check whether the PCH dynamic transport format set is correctly modified. Run the ACT USCCPCH command to activate the SCCPCH.
Modify the data of the PICH.

NOTE
1. 2. 3.
Run the DEA USCCPCH command to deactivate the SCCPCH. Run the LST UPICH command to view the data of the PICH. Modify the PICH data. If... You need to remove the PICH data, You need to add the PICH data, Then... Run the RMV UPICH command. Run the ADD UPICH command.
4. 5. ----End
6-20
Run the LST UPICH command to check whether the modification is correct. Run the ACT USCCPCH command to activate the SCCPCH.
Issue 03 (2010-09-20)
6.2.4 Removing an SCCPCH

This section describes how to remove an SCCPCH from a logical cell when the network is optimized.
Prerequisite
Context
NOTE
In this operation, you have to consider the following: l l l If the cell has only one SCCPCH before the removal, a call drop or out-of-control failure occurs on non-dedicated channels and no new UE can be admitted. If the cell has two SCCPCHs, the SCCPCH with the smaller ID number must carry the only PCH in the cell. This is ensured when the SCCPCHs are created. You are advised to deactivate the cell before removing an SCCPCH.
Procedure
Step 1 Run the LST USCCPCH command to view the SCCPCHs in the cell. Step 2 Perform the appropriate step based on the status of the cell. If... Then...
The cell is in service, and you want to Run the DEA USCCPCH to deactivate the remove the SCCPCH when the cell is in PRACH to be removed. an active state, The cell is in activated state, and you do 1. Run the HO UCELL command to force the handover of UEs from the cell to a not want to remove the SCCPCH when neighboring cell. the cell is not in an active state, 2. Run the DEA UCELL command to deactivate the cell. Step 3 Run the LST UFACH command to check whether the FACH carries the CTCH. Step 4 If the FACH carries the CTCH, run the DEA UCELLCBS command to deactivate cell CBS, and then run the RMV UCTCH command to remove the CTCH. Step 5 Run the RMV USCCPCH command to remove the SCCPCH. Step 6 If there is still another SCCPCH in the cell after one SCCPCH is removed, and you need to make the cell enter the service state, run the ACT UCELL command to activate the cell.
Step 7 Run the LST USCCPCH command to check whether the SCCPCH is removed from the cell. ----End
6.3 Reconfiguring Neighboring Cells

This section describes how to reconfigure neighboring cells, including intra-frequency cells, inter-frequency cells, and neighboring GSM cells. 6.3.1 Adding an Intra-Frequency Neighboring Cell This section describes how to add an intra-frequency neighboring cell to a specified cell when the capacity of the network is expanded, for example, NodeBs are added. 6.3.2 Adding an Inter-Frequency Neighboring Cell This section describes how to add an inter-frequency neighboring cell to a specified cell when the capacity of the network is expanded, for example, NodeBs are added. 6.3.3 Adding a Neighboring GSM Cell This section describes how to add a neighboring GSM cell on the coverage edge of the WCDMA when the neighbor relations between WCDMA and GSM changes after capacity expansion. 6.3.4 Modifying a Neighboring Cell This section describes how to modify the neighboring cell of a specified cell when the neighbor relation changes after capacity expansion or network optimization. For example, you can change the neighboring cell of cell A from cell B to cell C. 6.3.5 Removing a Neighboring Cell This section describes how to remove a neighbor relation of a cell when the neighbor relation changes after capacity expansion or network optimization. Neighbor relations are classified into unidirectional neighbor relation and bidirectional neighbor relation.
6.3.1 Adding an Intra-Frequency Neighboring Cell

This section describes how to add an intra-frequency neighboring cell to a specified cell when the capacity of the network is expanded, for example, NodeBs are added.
Prerequisite
l l l The cell to be configured with the neighbor relation is available. The BSC6900 works properly. If the neighboring cell is at a neighboring BSC6900, the basic data of that RNC is configured at the BSC6900 where the cell is located. You can run the LST UNRNC command to view the basic data of the neighboring BSC6900. If the basic data does not exist, you can run the ADD UNRNC command to add the basic data of the neighboring BSC6900 at the local BSC6900. l The current user has the BSC6900 control rights concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
6-22
Issue 03 (2010-09-20)
Context
CAUTION
The primary scrambling codes of intra-frequency neighboring cells of a cell should be different from each other.
Procedure
Step 1 Check the intra-frequency neighboring cells to be added. If... There are cells that belong to a neighboring BSC6900, No cell belongs to a neighboring BSC6900, Then... Go to step Step 2. Go to step Step 4.
Step 2 Run the LST UEXT3GCELL command to check whether all the parameters are configured at the local BSC6900. If... Then...
There are cells that are not configured 1. Run the ADD UEXT3GCELL command to at the BSC6900, add the parameters of a neighboring BSC6900 cell. If multiple basic parameters of the neighboring BSC6900 cell are not configured, repeat this step. 2. Go to step Step 3. All cells are configured at the BSC6900, Go to step Step 3.
Step 3 Run the LST UNRNCURA command, enter Neighboring RNC ID, and then check whether all the URAs are configured at the BSC6900. If... There are URA IDs that are not configured, Then... 1. Run the ADD UNRNCURA command to add the URA ID at the neighboring RNC. If multiple URA IDs are not configured, repeat this step. 2. Go to step Step 4. All URA IDs are configured, Go to step Step 4.
Issue 03 (2010-09-20)
6-23
Step 4 Run the ADD UINTRAFREQNCELL command to add an intra-frequency neighboring cell. If there are multiple intra-frequency neighboring cells, repeat this step. Step 5 Run the LST UINTRAFREQNCELL command to check whether the data configured for the neighboring cell is correct. ----End
6.3.2 Adding an Inter-Frequency Neighboring Cell

This section describes how to add an inter-frequency neighboring cell to a specified cell when the capacity of the network is expanded, for example, NodeBs are added.
Prerequisite
l l l The cell to be configured with the neighbor relation is available. The BSC6900 works properly. If the neighboring cell is at a neighboring BSC6900, the basic data of that RNC is configured at the BSC6900 where the cell is located. You can run the LST UNRNC command to view the basic data of the neighboring BSC6900. If the basic data does not exist, you can run the ADD UNRNC command to add the basic data of the neighboring BSC6900 at the local BSC6900. l The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Context
CAUTION
l Any two inter-frequency neighboring cells of a cell must have different UL frequencies, DL frequencies, or scrambling codes at the same time. l The maximum number of pairs formed by a UL frequency and a DL frequency of that interfrequency neighboring cell is two.
Procedure
Step 1 Check the inter-frequency cell to be added. If... The cell is located at a neighboring BSC6900, No cell is located at a neighboring BSC6900, Then... Go to step Step 2. Go to step Step 4.
6-24
Issue 03 (2010-09-20)
Step 2 Run the LST UEXT3GCELL command to check whether the basic parameters of the neighboring cell at another RNC are configured at the local BSC6900. If... Then...
There are basic parameters that are not 1. Run the ADD UEXT3GCELL command to add the parameters of a neighboring configured on the neighboring BSC6900 cell. If multiple basic parameters of BSC6900 cell, the neighboring BSC6900 cell are not configured, repeat this step. 2. Go to step Step 3. All basic parameters of the neighboring Go to step Step 3. BSC6900 cell are configured, Step 3 Run the LST UNRNCURA command and enter Neighboring RNC ID to check whether all URAs are configured at the local BSC6900. If... There are URA IDs that are not configured, Then... 1. Run the ADD UNRNCURA command to add the URA ID at the neighboring BSC6900. If multiple URA IDs are not configured, repeat this step. 2. Go to Step 4. All URA IDs are configured, Go to step Step 4.
Step 4 Run the ADD UINTERFREQNCELL command to add an inter-frequency neighboring cell. If there are multiple inter-frequency neighboring cells, repeat this step. Step 5 Run the LST UINTERFREQNCELL command to check whether the data of the interfrequency cell is correct. ----End
6.3.3 Adding a Neighboring GSM Cell

This section describes how to add a neighboring GSM cell on the coverage edge of the WCDMA when the neighbor relations between WCDMA and GSM changes after capacity expansion.
Prerequisite
l l l The cell to be configured with the neighbor relation is available. The BSC6900 works properly. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Issue 03 (2010-09-20)
Context
CAUTION
l l Any two neighboring GSM cells of a cell must have different network color codes, BS color codes, frequencies, or band indicators. A maximum of 32 neighboring GSM cells can be added.
Procedure
Step 1 Run the LST U2GNCELL command to check whether all the data is configured at the BSC6900 where the cell is located. If... Then...
The basic data of the neighboring GSM 1. Run the ADD UEXT2GCELL command to cell is not configured, add the basic data of the neighboring GSM cell. 2. Go to step Step 2. The basic data of the neighboring GSM Go to step Step 2. cell is configured, Step 2 Run the ADD U2GNCELL command to add a neighboring GSM cell. Step 3 Run the LST U2GNCELL command to check whether the data of the neighboring GSM cell is correct. ----End
6.3.4 Modifying a Neighboring Cell

This section describes how to modify the neighboring cell of a specified cell when the neighbor relation changes after capacity expansion or network optimization. For example, you can change the neighboring cell of cell A from cell B to cell C.
Prerequisite
None.
Procedure
Step 1 Add a neighboring cell. l 6.3.1 Adding an Intra-Frequency Neighboring Cell l 6.3.2 Adding an Inter-Frequency Neighboring Cell l 6.3.3 Adding a Neighboring GSM Cell Step 2 Remove a neighboring cell. ----End
6.3.5 Removing a Neighboring Cell

This section describes how to remove a neighbor relation of a cell when the neighbor relation changes after capacity expansion or network optimization. Neighbor relations are classified into unidirectional neighbor relation and bidirectional neighbor relation.
Prerequisite
Context
NOTE
Assume that the RNC has cell A and cell B, and the two cells are neighboring cells. Removing a unidirectional neighbor relation means, for example, cell B is removed as a neighboring cell from cell A, but cell A is not removed from cell B. Removing a bidirectional neighbor relation means that cell B is removed from cell A, and likewise, cell A is removed from cell B.
Procedure
l Remove a unidirectional intra-frequency neighbor relation of a cell. 1. 2. 3. l Run the LST UINTRAFREQNCELL command to view intra-frequency neighboring cells. Run the RMV UINTRAFREQNCELL command to remove an intra-frequency neighboring cell. Run the LST UINTRAFREQNCELL command to check whether the neighboring cell is correctly removed. Run the LST UINTERFREQNCELL command to view inter-frequency neighboring cells of the specified cell. Run the RMV UINTERFREQNCELL command to remove an inter-frequency neighboring cell. Run the LST UINTERFREQNCELL command to check whether the neighboring cell is removed. Run the LST U2GNCELL command to view the neighboring GSM cells of the specified cell. Run the RMV U2GNCELL command to remove a neighboring GSM cell. Run the LST U2GNCELL command to check whether the neighboring cell is removed. If the current cell is in service, run the HO UCELL command to force the handover of UEs from the current cell to another cell.
Remove a unidirectional inter-frequency neighbor relation of a cell. 1. 2. 3.
Remove a unidirectional inter-RAT neighbor relation of a cell. 1. 2. 3.
Remove a bidirectional neighbor relation between the current cell and another cell. 1.
Issue 03 (2010-09-20)
2. 3.
If the current cell is in an active state, run the DEA UCELL command to deactivate the cell. Run the RMV UNRELATION command and specify one or several types of neighboring cells in Neighboring Cell Type, and then remove the bidirectional neighbor relations between the current cell and the specified neighboring cells within the RNC.
NOTE
l The RMV UNRELATION command can remove only the bidirectional neighboring cells that are controlled by the local BSC6900. l To remove the bidirectional neighboring cells that are controlled by another BSC6900, you need to perform the operation on the other BSC6900.
4. 5. ----End
Run the ACT UCELL command to make the cell enter the service state again. Run the DSP UCELL command to check whether the status of the cell is correct.
6.4 Reconfiguring Timeslot Cross Connection

This section describes how to reconfigure timeslot cross connection on a BSC6900 and on a NodeB. 6.4.1 Configuring a Timeslot Cross Connection on a BSC6900 This section describes how to configure a timeslot cross connection between narrow-band transmission devices. 6.4.2 Configuring a Timeslot Cross Connection on a NodeB This section describes how to add a timeslot cross connection on a running NodeB, thus providing a transfer channel between narrow-band transmission devices.
6.4.1 Configuring a Timeslot Cross Connection on a BSC6900

This section describes how to configure a timeslot cross connection between narrow-band transmission devices.
Prerequisite
l l l The E1/T1 links on the AEUa or PEUa board are configured as fractional ATM, fractional IMA, or PPP links. In addition, these links have idle timeslots. The BSC6900 works properly. The current user has the BSC6900 control right concerning data configuration management. The control rights of data configuration management can be queried through LST CMCTRL. The BSC6900 is online. The current data configuration mode of the BSC6900 can be queried through the LST CFGMODE.
Procedure
Step 1 On the RNC LMT, run the ADD TSCROSS command to add a timeslot cross connection to the AEUa or PEUa board. If there are multiple timeslot cross connections, repeat this step.
Step 2 Run the LST TSCROSS command to check whether the configuration is correct. ----End
6.4.2 Configuring a Timeslot Cross Connection on a NodeB

This section describes how to add a timeslot cross connection on a running NodeB, thus providing a transfer channel between narrow-band transmission devices.
Prerequisite
l l The E1/T1 link is configured as a fractional ATM or PPP link. The link has idle timeslots. The NodeB works properly.
Procedure
Step 1 On the NodeB LMT, run the ADD TSCROSS command to add a timeslot cross connection to the NodeB. Step 2 On the NodeB LMT, run the LST TSCROSS command to check whether the configuration is correct. ----End
Issue 03 (2010-09-20)
6-29
7 Configuring UMTS Features
7
About This Chapter
Configuring UMTS Features
This chapter describes how to configure the features of the BSC6900 UMTS. 7.1 Overview of Feature Configuration UMTS features are classified into basic and optional features. Basic features are not licensecontrolled and therefore do not require license activation before use. On the contrary, optional features are license-controlled and therefore require license activation before use. 7.2 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. 7.3 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment This section describes how to activate, verify, and deactivate the basic feature WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment. 7.4 Configuring Conversational QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010501 Conversational QoS Class. 7.5 Configuring Streaming QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010502 Streaming QoS Class. 7.6 Configuring Interactive QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010503 Interactive QoS Class. 7.7 Configuring Background QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010504 Background QoS Class. 7.8 Configuring Emergency Call This section describes how to activate, verify, and deactivate the basic feature WRFD-021104 Emergency Call.
7.9 Configuring 2-Antenna Receive Diversity(NodeB) This section describes how to activate, verify, and deactivate the basic feature MRFD-210604 2-Antenna Receive Diversity on the UMTS side. 7.10 Configuring Cell Digital Combination and Split This section describes how to activate, verify, and deactivate the basic feature WRFD-010205 Cell Digital Combination and Split. 7.11 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH) This section describes how to activate, verify, and deactivate the basic feature WRFD-010202 UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH). 7.12 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) This section describes how to activate, verify, and deactivate the basic feature WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1). 7.13 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2) This section describes how to activate, verify, and deactivate the basic feature WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2). 7.14 Configuring Dynamic Channel Configuration Control This section describes how to activate, verify, and deactivate the basic feature WRFD-021101 Dynamic Channel Configuration Control. 7.15 Configuring Integrity Protection This section describes how to activate, verify, and deactivate the basic feature WRFD-011401 Integrity Protection. 7.16 Configuring Encryption This section describes how to activate, verify, and deactivate the basic feature WRFD-011402 Encryption. 7.17 Configuring Open Loop Power Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020501 Open Loop Power Control. 7.18 Configuring Downlink Power Balance This section describes how to activate, verify, and deactivate the basic feature WRFD-020502 Downlink Power Balance. 7.19 Configuring Outer Loop Power Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020503 Outer Loop Power Control. 7.20 Configuring Inner Loop Power Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020504 Inner Loop Power Control. 7.21 Configuring Admission Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020101 Admission Control. 7.22 Configuring Load Measurement This section describes how to activate, verify, and deactivate the basic feature WRFD-020102 Load Measurement. 7.23 Configuring Load Reshuffling
This section describes how to activate, verify, and deactivate the optional feature WRFD-020106 Load Reshuffling. 7.24 Configuring Overload Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020107 Overload Control. 7.25 Configuring Code Resource Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020108 Code Resource Management. 7.26 Configuring Shared Network Support in Connected Mode This section describes how to activate, verify, and deactivate the basic feature WRFD-021301 Shared Network Support in Connected Mode. 7.27 Configuring Intra Node B Softer Handover This section describes how to activate, verify, and deactivate the basic feature WRFD-020201 Intra Node B Softer Handover. 7.28 Configuring Intra RNC Soft Handover This section describes how to activate, verify, and deactivate the basic feature WRFD-020202 Intra RNC Soft Handover. 7.29 Configuring Inter RNC Soft Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-020203 Inter RNC Soft Handover. 7.30 Configuring Intra Frequency Hard Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-020301 Intra Frequency Hard Handover. 7.31 Configuring Intra RNC Cell Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010801 Intra RNC Cell Update. 7.32 Configuring Inter RNC Cell Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010802 Inter RNC Cell Update. 7.33 Configuring Intra RNC URA Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010901 Intra RNC URA Update. 7.34 Configuring Inter RNC URA Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010902 Inter RNC URA Update. 7.35 Configuring Direct Signaling Connection Re-establishment (DSCR) This section describes how to activate, verify, and deactivate the basic feature WRFD-021400 Direct Signaling Connection Re-establishment (DSCR). 7.36 Configuring Base Station Clock(NodeB) This section describes how to activate, verify, and deactivate the basic feature MRFD-210501 NodeB Clock on the UMTS side. 7.37 Configuring ATM Transmission Introduction Package This section describes how to activate, verify, and deactivate the basic feature WRFD-050301 ATM Transmission Introduction Package.
7.38 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface This section describes how to activate and verify the basic feature WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface. 7.39 Configuring Permanent AAL5 Connections for Control Plane Traffic This section describes how to activate, verify, and deactivate the basic feature WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic. 7.40 Configuring Call Admission Based on Used AAL2 Path Bandwidth This section describes how to activate and verify the basic feature WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth. 7.41 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". 7.42 Configuring F5 This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110 F5. 7.43 Configuring UBR+ ATM QoS Class This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305 UBR+ ATM QoS Class". 7.44 Configuring Flow Control This section describes how to activate, verify, and deactivate the basic feature WRFD-040100 Flow Control. 7.45 Configuring BOOTP This section describes how to activate, verify, and deactivate the basic feature WRFD-031100 BOOTP. In ATM transport mode, the NodeB can automatically set up the OM channel with the BSC6900 by using the BOOTSTRAP Protocol (BOOTP) function. 7.46 Configuring NodeB Self-discovery Based on IP Mode This section describes how to activate, verify, and deactivate the basic feature WRFD-031101 NodeB Self-discovery Based on IP Mode. 7.47 Configuring Intelligently Out of Service This section describes how to activate, verify, and deactivate the basic feature WRFD-031000 Intelligently Out of Service. 7.48 Configuring OCNS This section describes how to activate, verify, and deactivate the basic feature WRFD-031200 OCNS (Orthogonal Channel Noise Simulator). 7.49 Configuring Power Off the Equipment Level by Level This section describes how to activate, verify, and deactivate the basic feature WRFD-031400 Power Off the Equipment Level by Level. 7.50 Configuring Connection with TMA(NodeB) This section describes how to activate, verify, and deactivate the basic feature MRFD-210601 Connection with TMA (Tower Mounted Amplifier) on the UMTS side. 7.51 Configuring Remote Electrical Tilt(UMTS) This section describes how to activate, verify, and deactivate the basic feature MRFD-210602 Remote Electrical Tilt on the UMTS side. 7.52 Configuring Same Band Antenna Sharing Unit (900 MHz)
This section describes how to activate, verify, and deactivate the basic feature WRFD-060003 Configuring Same Band Antenna Sharing Unit (900 MHz). 7.53 Configuring Multi-mode BS Common CPRI Interface (NodeB) This section describes how to activate, verify, and deactivate the basic feature MRFD-220001 Multi-mode BS Common CPRI Interface (NodeB). 7.54 Configuring Multiple RAB Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010615 Multiple RAB Package (PS RAB 2). 7.55 Configuring Combination of Two PS Services This section describes how to activate, verify, and deactivate the optional feature WRFD-01061501 Combination of Two PS Services. 7.56 Configuring Combination of One CS Service and Two PS Services This section describes how to activate, verify, and deactivate the optional feature WRFD-01061502 Combination of One CS Service and Two PS Services. 7.57 Configuring Combination of Three PS Services This section describes how to activate, verify, and deactivate the optional feature WRFD-01061503 Combination of Three PS Services. 7.58 Configuring Combination of One CS Service and Three PS Services This section describes how to activate, verify, and deactivate the optional feature WRFD-01061504 Combination of One CS Service and Three PS Services. 7.59 Configuring Combination of Four PS Services This section describes how to activate, verify, and deactivate the optional feature WRFD-01061505 Combination of Four PS Services. 7.60 Configuring HSDPA Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010610 HSDPA Introduction Package. 7.61 Configuring 15 Codes per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-01061001 15 Codes per Cell. 7.62 Configuring Time and HS-PDSCH Codes Multiplex This section describes how to activate, verify, and deactivate the optional feature WRFD-01061018 Time and HS-PDSCH Codes Multiplex. 7.63 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF) This section describes how to activate, verify, and deactivate the optional feature WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF) 7.64 Configuring HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation This section describes how to activate, verify, and deactivate the optional feature WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation. 7.65 Configuring HSDPA Power Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061004 HSDPA Power Control. 7.66 Configuring HSDPA Admission Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061003 HSDPA Admission Control. 7.67 Configuring HSDPA Dynamic Power Allocation This section describes how to activate, verify, and deactivate the optional feature WRFD-01061019 HSDPA Dynamic Power Allocation. 7.68 Configuring HSDPA Flow Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061010 HSDPA Flow Control. 7.69 Configuring HSDPA Mobility Management This section describes how to activate, verify, and deactivate the optional feature WRFD-01061006 HSDPA Mobility Management. 7.70 Configuring Interactive and Background Traffic Class on HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-01061008 Interactive and Background Traffic Class on HSDPA. 7.71 Configuring HSDPA UE Category 1 to 24 This section describes how to activate, verify, and deactivate the optional feature WRFD-01061002 HSDPA UE Category 1 to 24. 7.72 Configuring Improvement of User Experience in Low Traffic Service This section describes how to activate, verify, and deactivate the optional feature WRFD-01061020 Improvement of User Experience in Low Traffic Service. 7.73 Configuring DL 16QAM Modulation This section describes how to activate, verify, and deactivate the optional feature WRFD-010629 16QAM Modulation. 7.74 Configuring Dynamic Code Allocation Based on NodeB This section describes how to activate, verify, and deactivate the optional feature WRFD-010631 Dynamic Code Allocation Based on NodeB. 7.75 Configuring HSDPA Enhanced Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010611 HSDPA Enhanced Package. 7.76 Configuring Scheduling based on EPF and GBR This section describes how to activate, verify, and deactivate the optional feature WRFD-01061103 Scheduling based on EPF and GBR. 7.77 Configuring HSDPA State Transition This section describes how to activate, verify, and deactivate the optional feature WRFD-01061111 HSDPA State Transition. 7.78 Configuring HSDPA DRD This section describes how to activate, verify, and deactivate the optional feature WRFD-01061112 HSDPA DRD. 7.79 Configuring Interactive and Background Traffic Class on HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010630 Interactive and Background Traffic Class on HSDPA. 7.80 Configuring HSDPA over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-010651 IHSDPA over Iur.
7.81 Configuring SRB over HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010652 SRB over HSDPA. 7.82 Configuring HSUPA Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010612 HSUPA Introduction Package. 7.83 Configuring HSUPA Admission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061202 HSUPA Admission Control. 7.84 Configuring HSUPA Power Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061203 HSUPA Power Control. 7.85 Configuring HSUPA Mobility Management This section describes how to activate, verify, and deactivate the optional feature WRFD-01061204 HSUPA Mobility Management. 7.86 Configuring HSUPA DCCC This section describes how to activate, verify, and deactivate the optional feature WRFD-01061208 HSUPA DCCC. 7.87 Configuring Interactive and Background Traffic Class on HSUPA This section describes how to activate the optional feature WRFD-01061206 Interactive and Background Traffic Class on HSUPA. 7.88 Configuring 20 HSUPA Users per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-01061211 20 HSUPA Users per Cell. 7.89 Configuring HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH) This section describes how to activate, verify, and deactivate the optional feature WRFD-01061401 HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH). 7.90 Configuring HSUPA 2ms TTI This section describes how to activate, verify, and deactivate the optional feature WRFD-01061403 HSUPA 2ms TTI. 7.91 Configuring HSUPA 2 ms/10 ms TTI Handover This section describes how to activate and deactivate the optional feature WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover. 7.92 Configuring HSUPA 5.74Mbps per User This section describes how to activate, verify, and deactivate the optional feature WRFD-01061405 HSUPA 5.74Mbps per User. 7.93 Configuring Streaming Traffic Class on HSUPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010632 Streaming Traffic Class on HSUPA. 7.94 Configuring 60 HSUPA Users per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-010634 60 HSUPA Users per Cell. 7.95 Configuring HSUPA over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-010635 HSUPA over Iur.
7.96 Configuring SRB over HSUPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010636 SRB over HSUPA. 7.97 Configuring Uplink Macro Diversity Intelligent Receiving This section describes how to activate, verify, and deactivate the optional feature WRFD-010640 Uplink Macro Diversity Intelligent Receiving. 7.98 Configuring HSUPA Adaptive Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-010641 HSUPA Adaptive Transmission. 7.99 Configuring TTI Switch for BE Services Based on Coverage This section describes how to activate, verify, and deactivate the optional feature WRFD-010690 TTI Switch for BE Services Based on Coverage. 7.100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion This section describes how to activate, verify, and deactivate the optional feature WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion. 7.101 Configuring Dynamic CE Resource Management This section describes how to activate, verify, and deactivate the optional feature WRFD-010638 Dynamic CE Resource Management. 7.102 Configuring HSPA+ Downlink 28Mbps per User This section describes how to activate, verify, and deactivate the optional feature WRFD-010680 HSPA+ Downlink 28Mbps per User. 7.103 Configuring HSPA+ Downlink 21Mbps per User This section describes how to activate, verify, and deactivate the optional feature WRFD-010681 HSPA+ Downlink 21Mbps per User. 7.104 Configuring Downlink Enhanced L2 This section describes how to activate, verify, and deactivate the optional feature WRFD-010685 Downlink Enhanced L2. 7.105 Configuring Enhanced CELL-FACH This section describes how to activate, verify, and deactivate the optional feature WRFD-010688 Enhanced CELL-FACH. 7.106 Configuring HSPA+ Downlink 42Mbps per User This section describes how to activate, verify, and deactivate the optional feature WRFD-010689 HSPA+ Downlink 42Mbps per User. 7.107 Configuring Downlink 64QAM This section describes how to activate, verify, and deactivate the optional feature WRFD-010683 Downlink 64QAM. 7.108 Configuring 2x2 MIMO This section describes how to activate, verify, and deactivate the optional feature WRFD-010684 2x2 MIMO. 7.109 Configuring Downlink 64QAM+MIMO This section describes how to activate, verify, and deactivate the optional feature WRFD-010693 DL 64QAM+MIMO. 7.110 Configuring CPC - DTX / DRX This section describes how to activate, verify, and deactivate the optional feature WRFD-010686 CPC-DTX/DRX.
7.111 Configuring CPC-HS-SCCH Less Operation This section describes how to activate, verify, and deactivate the optional feature WRFD-010687 CPC-HS-SCCH Less operation. 7.112 Configuring 96 HSDPA Users per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-010653 96 HSDPA Users per Cell. 7.113 Configuring 96 HSUPA Users per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-010639 96 HSUPA Users per Cell. 7.114 Configuring 128 HSDPA Users per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-010654 128 HSDPA Users per Cell. 7.115 Configuring 128 HSUPA Users per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-010670 128 HSUPA Users per Cell. 7.116 Configuring HSUPA UL Interference Cancellation This section describes how to activate, verify, and deactivate the optional feature WRFD-010691 HSUPA UL Interference Cancellation. 7.117 Configuring HSUPA Frequency Domain Equalization This section describes how to activate, verify, and deactivate the optional feature HSUPA Frequency Domain Equalization. 7.118 Configuring Uplink 16QAM This section describes how to activate, verify, and deactivate the optional feature WRFD-010694 Uplink 16QAM. 7.119 Configuring UL Layer 2 Improvement This section describes how to activate, verify, and deactivate the optional feature WRFD-010695 UL Layer 2 Improvement. 7.120 Configuring DC-HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010696 DC-HSDPA. 7.121 Configuring Queuing and Preemption This section describes how to activate, verify, and deactivate the optional feature WRFD-010505 Queuing and Preemption. 7.122 Configuring Access Class Restriction This section describes how to activate, verify, and deactivate the optional feature WRFD-021103 Access Class Restriction. 7.123 Configuring Traffic Priority Mapping onto Transmission Resources This section describes how to activate, verify, and deactivate the optional feature WRFD-050424 Traffic Priority Mapping onto Transmission Resources. 7.124 Configuring Differentiated Service Based on SPI Weight This section describes how to activate, verify, and deactivate the optional feature WRFD-020806 Differentiated Service Based on SPI Weight. 7.125 Configuring Inter-Frequency Hard Handover Based on Coverage This section describes how to activate, verify, and deactivate the optional feature WRFD-020302 Inter Frequency Hard Handover Based on Coverage.
7.126 Configuring Inter-Frequency Hard Handover Based on DL QoS This section describes how to activate, verify, and deactivate the basic feature WRFD-020304 Inter Frequency Hard Handover Based on DL QoS. 7.127 Configuring SRNS Relocation (UE Not Involved) This section describes how to activate, verify, and deactivate the optional feature WRFD-02060501 SRNS Relocation (UE Not Involved). 7.128 Configuring SRNS Relocation with Hard Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-02060502 SRNS Relocation with Hard Handover. 7.129 Configuring SRNS Relocation with Cell/URA Update This section describes how to activate, verify, and deactivate the optional feature WRFD-02060503 SRNS Relocation with Cell/URA Update. 7.130 Configuring Inter-RAT Handover Based on Coverage This section describes how to activate, verify, and deactivate the optional feature WRFD-020303 Inter-RAT Handover Based on Coverage. 7.131 Configuring Inter-RAT Handover Based on DL QoS This section describes how to activate, verify, and deactivate the optional feature WRFD-020309 Inter-RAT Handover Based on DL QoS. 7.132 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO This section describes how to activate, verify, and deactivate the optional feature WRFD-020307 Video Telephony Fallback to Speech (AMR) for Inter-RAT HO. 7.133 Configuring Inter-RAT Handover Phase 2 This section describes how to activate, verify, and deactivate the optional feature WRFD-020308 Video Telephony Fallback to Speech (AMR) for Inter-RAT HO. 7.134 Configuring NACC(Network Assisted Cell Change) This section describes how to activate, verify, and deactivate the optional feature WRFD-02030801 NACC(Network Assisted Cell Change). 7.135 Configuring PS Handover between UMTS and GPRS This section describes how to activate, verify, and deactivate the optional feature WRFD-02030802 PS Handover between UMTS and GPRS. 7.136 Configuring Mobility Between UMTS and LTE Phase 1 This section describes how to activate, verify, and deactivate the optional feature WRFD-020126 Mobility Between UMTS and LTE Phase 1. For information about how to configure this feature on the LTE side, see the related documents provided by the LTE equipment vendor. 7.137 Configuring Inter-Frequency Load Balance This section describes how to activate, verify, and deactivate the optional feature WRFD-020103 Inter Frequency Load Balance. 7.138 Configuring Inter-RAT Handover Based on Service This section describes how to activate, verify, and deactivate the optional feature WRFD-020305 Inter-RAT Handover Based on Service. 7.139 Configuring Inter-RAT Handover Based on Load This section describes how to activate, verify, and deactivate the optional feature WRFD-020306 Inter-RAT Handover Based on Load. 7.140 Configuring DRD Introduction Package
This section describes how to activate, verify, and deactivate the basic feature WRFD-020400 DRD Introduction Package. 7.141 Configuring Intra-System Direct Retry This section describes how to activate, verify, and deactivate the optional feature WRFD-02040001 Intra System Direct Retry. 7.142 Configuring Inter-System Direct Retry This section describes how to activate, verify, and deactivate the optional feature WRFD-02040002 Inter System Direct Retry. 7.143 Configuring Inter-System Redirect This section describes how to activate, verify, and deactivate the optional feature WRFD-02040003 Inter System Redirect. 7.144 Configuring Traffic Steering and Load Sharing During RAB Setup This section describes how to activate, verify, and deactivate the optional feature WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup. 7.145 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. 7.146 Configuring Measurement-based Direct Retry This section describes how to activate, verify and deactivate the optional feature WRFD-020402 Measurement based Direct Retry. 7.147 Configuring Enhanced Fast Dormancy This section describes how to activate, verify, and deactivate the optional feature WRFD-020500 Enhanced Fast Dormancy. 7.148 Configuring Cell Barring This section describes how to activate, verify, and deactivate the optional feature WRFD-021102 Cell Barring. 7.149 Configuring 3G/2G Common Load Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020310 3G/2G Common Load Management. 7.150 Configuring RAB Quality of Service Renegotiation over Iu Interface This section describes how to activate, verify, and deactivate the optional feature WRFD-010506 RAB Quality of Service Renegotiation over Iu Interface. 7.151 Configuring Rate Negotiation at Admission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-010507 Rate Negotiation at Admission Control. 7.152 Configuring Service Steering and Load Sharing in RRC Connection Setup This section describes how to activate, verify, and deactivate the optional feature WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup. 7.153 Configuring TCP Accelerator This section describes how to activate, verify, and deactivate the optional feature WRFD-020123 TCP Accelerator. 7.154 Configuring Uplink Flow Control of User Plane This section describes how to activate, verify, and deactivate the optional feature WRFD-020124 Uplink Flow Control of User Plane.
7.155 Configuring Active Queue Management (AQM) This section describes how to activate, verify, and deactivate the optional feature WRFD-011502 Active Queue Management (AQM). 7.156 Configuring Quality Improvement for Subscribed Service This section describes how to activate, verify, and deactivate the optional feature WRFD-020128 Quality Improvement for Subscribed Service. 7.157 Configuring Cell Broadcast Service This section describes how to activate, verify, and deactivate the optional feature WRFD-011000 Cell Broadcast Service. 7.158 Configuring Simplified Cell Broadcast This section describes how to activate, verify, and deactivate the optional feature WRFD-011001 Simplified Cell Broadcast. 7.159 Configuring TFO/TrFO This section describes how to activate, verify, and deactivate the basic feature WRFD-011600 TFO/TrFO. 7.160 Configuring Dynamic Power Sharing of Multi-Carriers This section describes how to activate, verify, and deactivate the optional feature WRFD-020116 Dynamic Power Sharing of Multi-Carriers. 7.161 Configuring Multi-Carrier Switch off Based on Traffic Load This section describes how to activate, verify, and deactivate the optional feature WRFD-020117 Multi-Carrier Switch off Based on Traffic Load. 7.162 Configuring Energy Efficiency Improved This section describes how to activate, verify, and deactivate the optional feature WRFD-020118 Energy Efficiency Improved. 7.163 Configuring Multi-Carrier Switch off Based on Power Backup This section describes how to activate, vertify, and deactivate the optional feature WRFD-020119 Multi-Carrier Switch off Based on Power Backup. 7.164 Configuring AMR-WB (Adaptive Multi Rate Wide Band) This section describes how to activate, verify, and deactivate the basic feature WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band). 7.165 Configuring AMR/WB-AMR Speech Rates Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020701 AMR/WB-AMR Speech Rates Control. 7.166 Configuring Overbooking on ATM Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-050405 Overbooking on ATM Transmission. 7.167 Configuring VoIP over HSPA/HSPA+ This section describes how to activate, verify, and deactivate the optional feature WRFD-010617 VoIP over HSPA/HSPA+. 7.168 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. 7.169 Configuring IMS Signaling over HSPA This section describes how to activate, verify, and deactivate the basic feature WRFD-010618 IMS Signaling over HSPA.
7.170 Configuring PDCP Header Compression (RoHC) This section describes how to activate, verify, and deactivate the optional feature WRFD-011501 PDCP Header Compression (RoHC). 7.171 Configuring CS Voice over HSPA/HSPA+ This section describes how to activate, verify, and deactivate the optional feature WRFD-010619 CS Voice over HSPA/HSPA+. 7.172 Configuring Cell ID + RTT Function-Based LCS This section describes how to activate, verify, and deactivate the optional feature WRFD-020801 Cell ID + RTT Function Based LCS. 7.173 Configuring OTDOA-Based LCS This section describes how to activate, verify, and deactivate the optional feature WRFD-020802 OTDOA Based LCS. 7.174 Configuring A-GPS-Based LCS This section describes how to activate, verify, and deactivate the optional feature WRFD-020803 A-GPS Based LCS. 7.175 Configuring LCS Classified Zone This section describes how to activate, verify, and deactivate the optional feature WRFD-020804 LCS Classified Zone. 7.176 Configuring LCS over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-020805 LCS over Iur. 7.177 Configuring Iupc Interface for LCS Service This section describes how to activate, verify, and deactivate the optional feature WRFD-020807 Iupc Interface for LCS service. 7.178 Configuring RAN Sharing Introduction Package Package This section describes how to activate, verify and deactivate the optional feature WRFD-021304 RAN Sharing Introduction Package. 7.179 Configuring Dedicated Carrier for Each Operator This section describes how to activate, verify, and deactivate the optional feature WRFD-02130401 Dedicated Carrier for Each Operator. 7.180 Configuring Flexible Network Architecture This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402 Flexible Network Architecture. 7.181 Configuring Mobility Control and Service Differentiation This section describes how to activate, verify, and deactivate the optional feature WRFD02130403 Mobility Control and Service Differentiation. 7.182 Configuring Independent License Control This section describes how to activate, verify, and deactivate the optional feature WRFD-02130404 Independent License Control. 7.183 Configuring RAN Sharing Phase 2 This section describes how to activate, verify, and deactivate the optional feature WRFD-021305 RAN Sharing Phase 2. 7.184 Configuring WRFD-02130501 Dedicated Iub Transmission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-02130501 Dedicated Iub Transmission Control.
7.185 Configuring IMSI-Based Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-021303 IMSI Based Handover. 7.186 Configuring MOCN Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-021311 MOCN(Multi-operator core network) Introduction Package. 7.187 Configuring Carrier Sharing by Operators This section describes how to activate, verify, and deactivate the optional feature WRFD-02131101 Carrier Sharing by Operators. 7.188 Configuring Dedicated NodeB/Cell for Operators This section describes how to activate, verify, and deactivate the optional feature WRFD-02131102 Dedicated NodeB/Cell for Operators. 7.189 Configuring MOCN Mobility Management This section describes how to activate, verify, and deactivate the optional feature WRFD-02131103 MOCN Mobility Management. 7.190 Configuring MOCN Load Balance This section describes how to activate, verify, and deactivate the optional feature WRFD-02131104 MOCN Load Balance. 7.191 Configuring Flexible Network Architecture This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402 Flexible Network Architecture. 7.192 Configuring Iu Flex Load Distribution Management This section describes how to activate the optional feature WRFD-021306 Iu Flex Load Distribution Management. 7.193 Configuring Multi-Frequency Band Networking Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020110 Multi Frequency Band Networking Management. 7.194 Configuring Enhanced Multiband Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020160 Enhanced Multiband Management. 7.195 Configuring Satellite Transmission on Iub Interface This section describes how to activate, verify, and deactivate the optional feature WRFD-050104 Satellite Transmission on Iub Interface. 7.196 Configuring Satellite Transmission on Iu Interface This section describes how to activate, verify, and deactivate the optional feature WRFD-050108 Satellite Transmission on Iu Interface. 7.197 Configuring MBMS Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010616 MBMS Introduction Package. 7.198 Configuring MBMS Broadcast Mode This section describes how to activate, verify, and deactivate the optional feature WRFD-01061601 MBMS Broadcast Mode. 7.199 Configuring MBMS Admission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061602 MBMS Admission Control.
7.200 Configuring MBMS Load Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061603 MBMS Load Control. 7.201 Configuring MBMS Soft/Selective Combination This section describes how to activate, verify, and deactivate the optional feature WRFD-01061604 MBMS Soft/Selective Combination. 7.202 Configuring MBMS Transport Resource Management This section describes how to activate, verify, and deactivate the optional feature WRFD-01061605 MBMS Transport Resource Management. 7.203 Configuring Streaming Service on MBMS This section describes how to activate, verify, and deactivate the optional feature WRFD-01061606 Streaming Service on MBMS. 7.204 Configuring MBMS 2 Channels per Cell This section describes how to activate the optional feature WRFD-01061607 MBMS 2 Channels per Cell. 7.205 Configuring 16/32/64/128Kbps Channel Rate on MBMS This section describes how to activate, verify, and deactivate the optional feature WRFD-01061608 16/32/64/128Kbps Channel Rate on MBMS. 7.206 Configuring MBMS Phase 2 This section describes how to activate, verify, and deactivate the optional feature WRFD-010660 MBMS Phase 2. 7.207 Configuring MBMS Enhanced Broadcast Mode This section describes how to activate, verify, and deactivate the optional feature WRFD-01066001 MBMS Enhanced Broadcast Mode. 7.208 Configuring MBMS P2P over HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-01066002 MBMS P2P over HSDPA. 7.209 Configuring MBMS Admission Enhancement This section describes how to activate, verify, and deactivate the optional feature WRFD-01066003 MBMS Admission Enhancement. 7.210 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users This section describes how to activate, verify, and deactivate the optional feature WRFD-01066004 Inter-Frequency Neighboring Cell Selection for MBMS PTP Users. 7.211 Configuring FACH Transmission Sharing for MBMS This section describes how to activate, verify, and deactivate the optional feature WRFD-010627 FACH Transmission Sharing for MBMS. 7.212 Configuring MBMS FLC (Frequency Layer Convergence)/FLD (Frequency Layer Dispersion) This section describes how to activate, verify, and deactivate the optional feature WRFD-010626 MBMS FLC (Frequency Layer Convergence)/FLD (Frequency Layer Dispersion). 7.213 Configuring MBMS over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-010661 MBMS over Iur. 7.214 Configuring Dynamic Power Estimation for MTCH
This section describes how to activate, verify, and deactivate the optional feature WRFD-010662 Dynamic Power Estimation for MTCH. 7.215 Configuring MSCH and MSCH Scheduling This section describes how to activate, verify, and deactivate the optional feature WRFD-010626 MSCH and MSCH Scheduling. 7.216 Configuring MBMS Channel Audience Rating Statistics This section describes how to activate, verify, and deactivate the optional feature WRFD-010665 MBMS Channel Audience Rating Statistics. 7.217 Configuring Domain Specific Access Control (DSAC) This section describes how to activate, verify, and deactivate the optional feature WRFD-020114 Domain Specific Access Control (DSAC). 7.218 Configuring One Tunnel This section describes how to activate, verify, and deactivate the optional feature WRFD-020111 One Tunnel. 7.219 Configuring Hybrid Iub IP Transmission This section describes how to activate, verify and deactivate the optional feature WRFD-050403 Hybrid Iub IP Transmission. 7.220 Configuring ATM/IP Dual Stack Node B This section describes how to activate, verify and deactivate the optional feature WRFD-050404 ATM/IP Dual Stack Node B. 7.221 Configuring FP MUX for IP Transmission This section describes how to activate, verify and deactivate the optional feature WRFD-050420 FP MUX for IP Transmission. 7.222 Configuring IP Fault Detection Based on BFD This section describes how to activate and deactivate the optional feature WRFD-050421 IP Fault Detection Based on BFD. 7.223 Configuring Dynamic Bandwidth Control of Iub IP This section describes how to activate, verify, and deactivate the optional feature WRFD-050422 Dynamic Bandwidth Control of Iub IP. 7.224 Configuring Overbooking on IP Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-050408 Overbooking on IP Transmission. 7.225 Configuring UDP MUX for Iu-CS Transmission This section describes how to activate the optional feature WRFD-050412 UDP MUX for IuCS Transmission. 7.226 Configuring ATM Switching-Based Hub NodeB This section describes how to activate, verify, and deactivate the optional feature WRFD-050105 ATM Switching-Based Hub NodeB. 7.227 Configuring AAL2 Switching-Based Hub NodeB This section describes how to activate, verify, and deactivate the optional feature WRFD-050106 AAL2 Switching-Based Hub NodeB. 7.228 Configuring IP Routing-Based Hub NodeB This section describes how to activate, verify, and deactivate the optional feature WRFD-050107 IP Routing-Based Hub NodeB.
7.229 Configuring Overbooking on Hub Node B Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-050406 ATM QoS Introduction on Hub Node B (Overbooking on Hub Node B Transmission). 7.230 Configuring Ethernet OAM This section describes how to activate, verify, and deactivate the optional feature WRFD-050425 Ethernet OAM. 7.231 Configuring Clock Synchronization on Ethernet in NodeB This section describes how to activate, verify, and deactivate the optional feature WRFD-050501 Clock Synchronization on Ethernet in NodeB. 7.232 Configuring Synchronous Ethernet This section describes how to activate, verify, and deactivate the optional feature WRFD-050502 Synchronous Ethernet. 7.233 Configuring RNC Node Redundancy This section describes how to activate, verify, and deactivate the optional feature WRFD-040202 RNC Node Redundancy. 7.234 Configuring RRU Redundancy This section describes how to activate, verify, and deactivate the optional feature WRFD-040203 RRU Redundancy. 7.235 Configuring Transmit Diversity This section describes how to activate, verify, and deactivate the optional feature WRFD-010203 Transmit Diversity. 7.236 Configuring 4-Antenna Receive Diversity This section describes how to activate, verify, and deactivate the optional feature WRFD-010209 4-Antenna Receive Diversity. 7.237 Configuring Extended Cell Coverage up to 200km This section describes how to activate, verify, and deactivate the optional feature WRFD-021308 Extended Cell Coverage up to 200km. 7.238 Configuring High Speed Access This section describes how to activate, verify, and deactivate the optional feature WRFD-010206 High Speed Access. 7.239 Configuring PDCP Header Compression (RFC2507) This section describes how to activate, verify, and deactivate the optional feature WRFD-011500 PDCP Header Compression (RFC2507). 7.240 Configuring HCS (Hierarchical Cell Structure) This section describes how to activate, verify, and deactivate the optional feature WRFD-021200 HCS (Hierarchical Cell Structure). 7.241 Configuring Intra Frequency Load Balance This section describes how to activate, verify, and deactivate the optional feature WRFD-020104 Intra Frequency Load Balance. 7.242 Configuring Potential User Control This section describes how to activate, verify, and deactivate the optional feature WRFD-020105 Potential User Control. 7.243 Configuring License Control for Urgency This section describes how to configure and verify the optional feature WRFD-040300 license control for urgency.
7.244 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g This section describes how to activate, verify, and deactivate the optional feature WRFD-070004 Load Based GSM and UMTS Handover Enhancement Based on Iur-g. 7.245 Configuring NACC Procedure Optimization Based on Iur-g This section describes how to activate, verify, and deactivate the optional feature WRFD-070005 NACC Procedure Optimization Based on Iur-g between GSM and UMTS. 7.246 Configuring MBSC Load Balancing This section describes how to activate, verify, and deactivate the optional feature MRFD-211402 MBSC Load Balancing. 7.247 Configuring GSM and UMTS Traffic Steering Based on Iur-g This section describes how to activate, verify, and deactivate the optional feature WRFD-070007 GSM and UMTS Traffic Steering Based on Iur-g. 7.248 Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority This section describes how to activate, verify, and deactivate the optional feature WRFD-070201 GSM and UMTS Intelligent Shutdown Based on RAT Priority. 7.249 Configuring Warning of Disaster This section describes how to activate, verify, and deactivate the optional feature WRFD-020127 Warning of Disaster. 7.250 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). 7.251 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB) This section describes how to activate, verify, and deactivate the optional feature MRFD-221501 IP-Based Multi-Mode Co-Transmission on Base Station Side. 7.252 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side (NodeB) This section describes how to activate, verify, and deactivate the optional feature MRFD-221504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side(NodeB). 7.253 Configuring Multi-Mode BS Common Reference Clock (NodeB) This section describes how to activate, verify, and deactivate the basic feature MRFD-221601 Multi-Mode BS Common Reference Clock (NodeB).
7-18
Issue 03 (2010-09-20)
7.1 Overview of Feature Configuration

UMTS features are classified into basic and optional features. Basic features are not licensecontrolled and therefore do not require license activation before use. On the contrary, optional features are license-controlled and therefore require license activation before use. Table 7-1 lists the basic features. Table 7-2 lists the optional features. Table 7-1 UMTS Basic Feature List Feature ID WRFD-000001 WRFD-000002 WRFD-000003 WRFD-000004 WRFD-000005 WRFD-000006 WRFD-000007 WRFD-010101 WRFD-010102 WRFD-010201 WRFD-010510 Feature Name System Improvement for RAN5.1 System Improvement for RAN6.0 System Improvement for RAN6.1 System Improvement for RAN10.0 System Improvement for RAN11.0 System Improvement for RAN11.1 System Improvement for RAN12.0 3GPP Specifications Operating Multi-band FDD Mode 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class Configuration Method None None None None None None None None None None 7.3 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment 7.4 Configuring Conversational QoS Class 7.5 Configuring Streaming QoS Class 7.6 Configuring Interactive QoS Class 7.7 Configuring Background QoS Class
WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504
Issue 03 (2010-09-20)
7-19
Feature ID WRFD-010609 WRFD-01060901
Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Two CS Services (Except for Two AMR Speech Services) Combination of One CS Service and One PS Service Combination of Two CS Services and One PS Service (Except for Two AMR Speech Services) Emergency Call 2-Antenna Receive Diversity Cell Digital Combination and Split Fast Power Congestion Control (FCC) Active TX Chain Gain Calibration UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
Configuration Method None None
WRFD-01060902 WRFD-01060903
None None
WRFD-021104 MRFD-210604 WRFD-010205
7.8 Configuring Emergency Call 7.9 Configuring 2-Antenna Receive Diversity(NodeB) 7.10 Configuring Cell Digital Combination and Split None None 7.11 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH) None 7.12 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) 7.13 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2) None None
WRFD-010208 WRFD-010211 WRFD-010202
WRFD-010401 WRFD-010301
System Information Broadcasting Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2) Logical Channel Management Transport Channel Management
WRFD-010302
WRFD-020900 WRFD-021000
7-20
Issue 03 (2010-09-20)
Feature ID WRFD-022000 WRFD-021101
Feature Name Physical Channel Management Dynamic Channel Configuration Control (DCCC) Integrity Protection Encryption Open Loop Power Control Downlink Power Balance Outer Loop Power Control Inner Loop Power Control Admission Control Load Measurement Load Reshuffling Overload Control Code Resource Management Shared Network Support in Connected Mode BSC/RNC Resource Sharing Intra NodeB Softer Handover Intra NodeB Softer Handover Inter RNC Soft Handover
Configuration Method None 7.14 Configuring Dynamic Channel Configuration Control 7.15 Configuring Integrity Protection 7.16 Configuring Encryption 7.17 Configuring Open Loop Power Control 7.18 Configuring Downlink Power Balance 7.19 Configuring Outer Loop Power Control 7.20 Configuring Inner Loop Power Control 7.21 Configuring Admission Control 7.22 Configuring Load Measurement 7.23 Configuring Load Reshuffling 7.24 Configuring Overload Control 7.25 Configuring Code Resource Management 7.26 Configuring Shared Network Support in Connected Mode None 7.27 Configuring Intra Node B Softer Handover 7.28 Configuring Intra RNC Soft Handover 7.29 Configuring Inter RNC Soft Handover
WRFD-011401 WRFD-011402 WRFD-020501 WRFD-020502 WRFD-020503 WRFD-020504 WRFD-020101 WRFD-020102 WRFD-020106 WRFD-020107 WRFD-020108 WRFD-021301
MRFD-210104 WRFD-020201 WRFD-020202 WRFD-020203
Issue 03 (2010-09-20)
7-21
Feature ID WRFD-020301 WRFD-010801 WRFD-010802 WRFD-010901 WRFD-010902 WRFD-021400
Feature Name Intra Frequency Hard Handover Intra RNC Cell Update Inter RNC Cell Update Intra RNC URA Update Inter RNC URA Update Direct Signaling Connection Re-establishment (DSCR) Star Topology Chain Topology Tree Topology BTS/NodeB Clock BSC/RNC Clock ATM Transmission Introduction Package ATM over E1T1 on Iub Interface ATM over Channelized STM-1/OC-3 on Iub Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Permanent AAL5 Connections for Control Plane Traffic
Configuration Method 7.30 Configuring Intra Frequency Hard Handover 7.31 Configuring Intra RNC Cell Update 7.32 Configuring Inter RNC Cell Update 7.33 Configuring Intra RNC URA Update 7.34 Configuring Inter RNC URA Update 7.35 Configuring Direct Signaling Connection Reestablishment (DSCR) None None None 7.36 Configuring Base Station Clock(NodeB) None 7.37 Configuring ATM Transmission Introduction Package None None
MRFD-210204 MRFD-210205 MRFD-210206 MRFD-210501 MRFD-210502 WRFD-050301
WRFD-05030101 WRFD-05030102
WRFD-05030103
None
WRFD-05030104
7.38 Configuring Dynamic AAL2 Connections in Iub/ IuCS/Iur Interface 7.39 Configuring Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
7-22
Issue 03 (2010-09-20)
Feature ID WRFD-05030106
Feature Name Call Admission Based on Used AAL2 Path Bandwidth CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes F5 IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface UBR+ ATM QoS Class Link aggregation Flow Control DPU Board Replaced without Service Interruption in RNC System Redundancy Operate System Security Management Performance Management Faulty Management Inventory Management Configuration Management Security Management Interface Message Tracing User Signaling Tracing BSC/RNC Software Management BTS/NodeB Software Management BTS/NodeB Software USB Download BOOTP
Configuration Method 7.40 Configuring Call Admission Based on Used AAL2 Path Bandwidth 7.41 Configuring CBR, rtVBR, nrt-VBR, UBR ATM QoS Classes 7.42 Configuring F5 None
WRFD-05030107
WRFD-05030110 WRFD-050304
WRFD-050305 MRFD-210103 WRFD-040100 WRFD-040101
7.43 Configuring UBR+ ATM QoS Class None 7.44 Configuring Flow Control None
MRFD-210101 MRFD-210102 MRFD-210302 MRFD-210304 MRFD-210303 MRFD-210301 MRFD-210305 MRFD-210801 MRFD-210802 MRFD-210401 MRFD-210402 MRFD-210310 WRFD-031100
None None None None None None None None None None None None 7.45 Configuring BOOTP
Issue 03 (2010-09-20)
7-23
Feature ID WRFD-031101
Feature Name NodeB Self-discovery Based on IP Mode NodeB Remote Selfconfiguration NodeB Self-test License Management DBS Topology Maintenance Intelligently Out of Service OCNS Power off the equipment level by level Solar Power Device Management Single IP Address for NodeB Improved CE Mapping for EDCH Documentation Connection with TMA (Tower Mounted Amplifier) Remote Electrical Tilt Same Band Antenna Sharing Unit (900Mhz) Multi-mode BS Common CPRI Interface(NodeB) Multi-mode BS RRU/RFU star-connection with separate CPRI interface(NodeB)
Configuration Method 7.46 Configuring NodeB Self-discovery Based on IP Mode None None None None 7.47 Configuring Intelligently Out of Service 7.48 Configuring OCNS 7.49 Configuring Power Off the Equipment Level by Level None None None None 7.50 Configuring Connection with TMA (NodeB) 7.51 Configuring Remote Electrical Tilt(UMTS) 7.52 Configuring Same Band Antenna Sharing Unit (900 MHz) 7.53 Configuring Multimode BS Common CPRI Interface (NodeB) None
WRFD-031102 WRFD-031103 MRFD-210403 MRFD-210309 WRFD-031000 WRFD-031200 WRFD-031400
WRFD-031500 WRFD-021404 WRFD-010212 MRFD-210701 MRFD-210601
MRFD-210602 WRFD-060003
MRFD-220001
MRFD-220002
7-24
Issue 03 (2010-09-20)
Table 7-2 UMTS Optional Feature List Feature ID Feature Name License Control Item Multiple RAB License Configured on... BSC6900 Configuration Method 7.54 Configuring Multiple RAB Package 7.55 Configuring Combination of Two PS Services 7.56 Configuring Combination of One CS Service and Two PS Services 7.57 Configuring Combination of Three PS Services 7.58 Configuring Combination of One CS Service and Three PS Services 7.59 Configuring Combination of Four PS Services 7.60 Configuring HSDPA Introduction Package None
WRFD-010615
Multiple RAB Package
WRFD-010615 01
Combination of Two PS Services
Multiple RAB
BSC6900
WRFD-010615 02
Combination of One CS Service and Two PS Services
Multiple RAB
BSC6900
WRFD-010615 03
Combination of Three PS Services
Multiple RAB
BSC6900
WRFD-010615 04
Combination of One CS Service and Three PS Services
Multiple RAB
BSC6900
WRFD-010615 05
Combination of Four PS Services
Multiple RAB
BSC6900
WRFD-010610
HSDPA Introduction Package
High Speed Downlink Packet Access
BSC6900
WRFD-010610 17
QPSK Modulation
BSC6900&Nod eB
Issue 03 (2010-09-20)
7-25
Feature ID
Feature Name
License Control Item High Speed Downlink Packet Access High Speed Downlink Packet Access
License Configured on... BSC6900&Nod eB BSC6900
Configuration Method 7.61 Configuring 15 Codes per Cell 7.62 Configuring Time and HSPDSCH Codes Multiplex 7.63 Configuring HSDPA HARQ & Scheduling (MAX C/I, RR, and PF) 7.64 Configuring HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation 7.65 Configuring HSDPA Power Control 7.66 Configuring HSDPA Admission Control 7.67 Configuring HSDPA Dynamic Power Allocation 7.68 Configuring HSDPA Flow Control
WRFD-010610 01 WRFD-010610 18
15 Codes per Cell Time and HSPDSCH Codes Multiplex
WRFD-010610 09
HSDPA HARQ & Scheduling (MAX C/I, RR and PF)
BSC6900
WRFD-010610 05
HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation
BSC6900
WRFD-010610 04
HSDPA Power Control
High Speed Downlink Packet Access High Speed Downlink Packet Access
BSC6900
WRFD-010610 03
HSDPA Admission Control
BSC6900
WRFD-010610 19
HSDPA Dynamic Power Allocation
BSC6900
WRFD-010610 10
HSDPA Flow Control
BSC6900
7-26
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item High Speed Downlink Packet Access
License Configured on... BSC6900
Configuration Method 7.69 Configuring HSDPA Mobility Management None
WRFD-010610 06
HSDPA Mobility Management
WRFD-010610 14
HSDPA Transport Resource Management Interactive and Background Traffic Class on HSDPA
High Speed Downlink Packet Access High Speed Downlink Packet Access
BSC6900
WRFD-010610 08
BSC6900
7.70 Configuring Interactive and Background Traffic Class on HSDPA 7.71 Configuring HSDPA UE Category 1 to 24 None
WRFD-010610 02
HSDPA UE Category 1 to 24
BSC6900
WRFD-010610 15 WRFD-010610 16 WRFD-010610 20
HSDPA 1.8Mbps per User 16 HSDPA Users per Cell Improvement of User Experience in Low Traffic Service
High Speed Downlink Packet Access High Speed Downlink Packet Access High Speed Downlink Packet Access
BSC6900
BSC6900
None
BSC6900
7.72 Configuring Improvement of User Experience in Low Traffic Service None
WRFD-010620
HSDPA 3.6Mbps per User DL 16QAM Modulation
High Speed Downlink Packet Access Function 3.6M 16QAM (per NodeB)
BSC6900
WRFD-010629
NodeB
7.73 Configuring DL 16QAM Modulation
Issue 03 (2010-09-20)
7-27
Feature ID
Feature Name
License Control Item Dynamic HSDPA Code Allocation Based on NodeB (per NodeB) High Speed Downlink Packet Access Function 7.2M 32 HSDPA Users per Cell None
License Configured on... NodeB
Configuration Method 7.74 Configuring Dynamic Code Allocation Based on NodeB None
WRFD-010631
Dynamic Code Allocation Based on NodeB
WRFD-010621
HSDPA 7.2Mbps per User 32 HSDPA Users per Cell HSDPA Enhanced Package
BSC6900
WRFD-010622 WRFD-010611
BSC6900 None
None 7.75 Configuring HSDPA Enhanced Package 7.76 Configuring Scheduling based on EPF and GBR 7.77 Configuring HSDPA State Transition 7.78 Configuring HSDPA DRD None
WRFD-010611 03
Scheduling based on EPF and GBR
None
None
WRFD-010611 11
HSDPA State Transition
HSDPA State Transition
BSC6900
WRFD-010611 12 WRFD-010611 13 WRFD-010630
HSDPA DRD
HSDPA DRD
BSC6900
HS-DPCCH Preamble Support Streaming Traffic Class on HSDPA
HS-DPCCH Preamble support Streaming Traffic Class on HSDPA
BSC6900
BSC6900
7.79 Configuring Interactive and Background Traffic Class on HSDPA None
WRFD-010650
HSDPA 13.976Mbps per User
HSDPA 13.976Mbps per User
BSC6900
7-28
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item HSDPA over Iur
Configuration Method 7.80 Configuring HSDPA over Iur 7.81 Configuring SRB over HSDPA None 7.82 Configuring HSUPA Introduction Package
WRFD-010651
HSDPA over Iur
WRFD-010652
SRB over HSDPA
SRB over HSDPA
BSC6900
WRFD-010623 WRFD-010612
64 HSDPA Users per Cell HSUPA Introduction Package
64 HSDPA Users per Cell RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB)
BSC6900 BSC6900&Nod eB
WRFD-010612 01
HSUPA UE Category 1 to 6
RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB)
BSC6900&Nod eB
None
WRFD-010612 09
HSUPA HARQ and Fast UL Scheduling in NodeB
RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB) RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB)
BSC6900&Nod eB
None
WRFD-010612 02
HSUPA Admission Control
BSC6900&Nod eB
7.83 Configuring HSUPA Admission Control
Issue 03 (2010-09-20)
7-29
Feature ID
Feature Name
License Control Item RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB)
License Configured on... BSC6900&Nod eB
Configuration Method 7.84 Configuring HSUPA Power Control
WRFD-010612 03
HSUPA Power Control
WRFD-010612 04
HSUPA Mobility Management
BSC6900&Nod eB
7.85 Configuring HSUPA Mobility Management
WRFD-010612 08
HSUPA DCCC
BSC6900&Nod eB
7.86 Configuring HSUPA DCCC
WRFD-010612 07
HSUPA Transport Resource Management
RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB) RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB)
BSC6900&Nod eB
None
WRFD-010612 06
Interactive and Background Traffic Class on HSUPA
BSC6900&Nod eB
7.87 Configuring Interactive and Background Traffic Class on HSUPA
7-30
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item RNC: High Speed Uplink Packet Access NodeB: HSUPA Introduction Package (per NodeB)
License Configured on... BSC6900&Nod eB
Configuration Method None
WRFD-010612 10
HSUPA 1.44Mbps per User
WRFD-010612 11
20 HSUPA Users per Cell
BSC6900&Nod eB
7.88 Configuring 20 HSUPA Users per Cell
WRFD-010614 WRFD-010614 01
HSUPA Phase 2 HSUPA EAGCH Power Control (Based on CQI or HSSCCH)
None HSUPA Phase2 (per NodeB)
None NodeB
None 7.89 Configuring HSUPA EAGCH Power Control (Based on CQI or HSSCCH) None 7.90 Configuring HSUPA 2ms TTI 7.91 Configuring HSUPA 2 ms/ 10 ms TTI Handover 7.92 Configuring HSUPA 5.74Mbps per User
WRFD-010614 02 WRFD-010614 03
Enhanced Fast UL Scheduling HSUPA 2ms TTI
None None
None None
WRFD-010614 04
HSUPA 2ms/ 10ms TTI Handover
HSUPA 2ms/ 10ms TTI handover
BSC6900
WRFD-010614 05
BSC6900
Issue 03 (2010-09-20)
7-31
Feature ID
Feature Name
License Control Item Streaming Traffic Class on HSUPA
Configuration Method 7.93 Configuring Streaming Traffic Class on HSUPA 7.94 Configuring 60 HSUPA Users per Cell 7.95 Configuring HSUPA over Iur 7.96 Configuring SRB over HSUPA 7.97 Configuring Uplink Macro Diversity Intelligent Receiving 7.98 Configuring HSUPA Adaptive Transmission 7.99 Configuring TTI Switch for BE Services Based on Coverage 7.100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion
WRFD-010632
Streaming Traffic Class on HSUPA
WRFD-010634
BSC6900
WRFD-010635
HSUPA over Iur
HSUPA over Iur
BSC6900
WRFD-010636
SRB over HSUPA
SRB over HSUPA
BSC6900
WRFD-010640
Uplink Macro Diversity Intelligent Receiving
Uplink Macro Diversity Intelligent Receiving
BSC6900
WRFD-010641
HSUPA Adaptive Transmission
HSUPA Adaptive Retransmission
BSC6900
WRFD-010690
TTI Switch for BE Services Based on Coverage
TTI Switch for BE Services Based on Coverage
BSC6900
WRFD-010637
HSUPA Iub Flow Control in Case of Iub Congestion
None
None
7-32
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item Dynamic CE Resource Management (per NodeB) HSPA + Downlink 28 Mbit/s Per User
Configuration Method 7.101 Configuring Dynamic CE Resource Management 7.102 Configuring HSPA+ Downlink 28Mbps per User 7.103 Configuring HSPA+ Downlink 21Mbps per User 7.104 Configuring Downlink Enhanced L2 7.105 Configuring Enhanced CELL-FACH 7.106 Configuring HSPA+ Downlink 42Mbps per User 7.107 Configuring Downlink 64QAM 7.108 Configuring 2x2 MIMO
WRFD-010638
Dynamic CE Resource Management
WRFD-010680
HSPA+ Downlink 28Mbps per User
BSC6900
WRFD-010681
HSPA + Downlink 21 Mbit/s Per User
BSC6900
WRFD-010685
Downlink Enhanced L2
Downlink Enhanced L2
BSC6900
WRFD-010688
Enhanced CELL-FACH
Enhanced CELL_FACH
BSC6900
WRFD-010689
BSC6900
WRFD-010683
Downlink 64 QAM
DL 64QAM Function (per Cell) 2*2 MIMO Function (per Cell)
NodeB
WRFD-010684
2x2 MIMO
NodeB
Issue 03 (2010-09-20)
7-33
Feature ID
Feature Name
License Control Item the number of cells with DL 64QAM +MIMO function enabled CPC-DTX / DRX
Configuration Method 7.109 Configuring Downlink 64QAM +MIMO 7.110 Configuring CPC - DTX / DRX 7.111 Configuring CPC-HSSCCH Less Operation 7.112 Configuring 96 HSDPA Users per Cell 7.113 Configuring 96 HSUPA Users per Cell 7.114 Configuring 128 HSDPA Users per Cell 7.115 Configuring 128 HSUPA Users per Cell 7.116 Configuring HSUPA UL Interference Cancellation 7.117 Configuring HSUPA Frequency Domain Equalization
WRFD-010693
DL 64QAM +MIMO
WRFD-010686
CPC - DTX / DRX
BSC6900
WRFD-010687
CPC - HSSCCH less operation
CPC-HS-SCCH Less Operation
BSC6900
WRFD-010653
96 HSDPA Users per Cell
BSC6900
WRFD-010639
BSC6900
WRFD-010654
BSC6900
WRFD-010670
BSC6900
WRFD-010691
HSUPA UL Interference Cancellation
the number of cells with IC function enabled the number of cells with FDE function enabled
NodeB
WRFD-010692
HSUPA FDE
NodeB
7-34
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item the number of cells with UL 16QAM function enabled the number of cells with UL L2 Enhanced function enabled the number of cells with DCHSDPA function enabled Queuing and Pre-emption
Configuration Method 7.118 Configuring Uplink 16QAM 7.119 Configuring UL Layer 2 Improvement 7.120 Configuring DC-HSDPA
WRFD-010694
UL 16QAM
WRFD-010695
UL Layer 2 Improvement
NodeB
WRFD-010696
DC-HSDPA
NodeB
WRFD-010505
Queuing and Pre-Emption
BSC6900
7.121 Configuring Queuing and Preemption 7.122 Configuring Access Class Restriction 7.123 Configuring Traffic Priority Mapping onto Transmission Resources 7.124 Configuring Differentiated Service Based on SPI Weight 7.125 Configuring InterFrequency Hard Handover Based on Coverage
WRFD-021103
Access Class Restriction
Access Class Restriction when SPU overload Traffic Priority Mapping on Transport
BSC6900
WRFD-050424
Traffic Priority Mapping onto Transmission Resources
BSC6900
WRFD-020806
Differentiated Service Based on SPI Weight
Differentiated Service Based on SPI Weight
BSC6900
WRFD-020302
Inter Frequency Hard Handover Based on Coverage
Inter frequency hard handover
BSC6900
Issue 03 (2010-09-20)
7-35
Feature ID
Feature Name
License Control Item Inter Frequency Hard Handover Based on DL QoS
Configuration Method 7.126 Configuring InterFrequency Hard Handover Based on DL QoS None
WRFD-020304
Inter Frequency Hard Handover Based on DL QoS
WRFD-020605
SRNS Relocation Introduction Package SRNS Relocation (UE Not Involved)
SRNS Relocation (UE Not Involved) SRNS Relocation (UE Not Involved)
BSC6900
WRFD-020605 01
BSC6900
7.127 Configuring SRNS Relocation (UE Not Involved) 7.128 Configuring SRNS Relocation with Hard Handover 7.129 Configuring SRNS Relocation with Cell/URA Update None
WRFD-020605 02
SRNS Relocation with Hard Handover
SRNS Relocation (UE Not Involved)
BSC6900
WRFD-020605 03
SRNS Relocation with Cell/URA Update
SRNS Relocation (UE Not Involved)
BSC6900
WRFD-020605 04 WRFD-020303
Lossless SRNS Relocation Inter-RAT Handover Based on Coverage
SRNS Relocation (UE Not Involved) Coverage Based Inter-RAT Handover Between UMTS and GSM/ GPRS Inter-RAT Handover Based on DL QoS
BSC6900
BSC6900
7.130 Configuring Inter-RAT Handover Based on Coverage 7.131 Configuring Inter-RAT Handover Based on DL QoS
Issue 03 (2010-09-20)
WRFD-020309
Inter-RAT Handover Based on DL QoS
BSC6900
7-36
Feature ID
Feature Name
License Control Item Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
Configuration Method 7.132 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO 7.133 Configuring Inter-RAT Handover Phase 2 7.134 Configuring NACC (Network Assisted Cell Change) 7.135 Configuring PS Handover between UMTS and GPRS 7.136 Configuring Mobility Between UMTS and LTE Phase 1 7.137 Configuring InterFrequency Load Balance 7.138 Configuring Inter-RAT Handover Based on Service
WRFD-020307
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
WRFD-020308
Inter-RAT Handover Phase 2
None
None
WRFD-020308 01
NACC (Network Assisted Cell Change)
NACC (Network Assisted Cell Change)
BSC6900
WRFD-020308 02
PS Handover Between UMTS and GPRS
PS Handover Between UMTS and GPRS
BSC6900
WRFD-020126
Mobility Between UMTS and LTE Phase1
Mobility Between UMTS and LTE Phase 1
BSC6900
WRFD-020103
Inter Frequency Load Balance
Inter frequency load handover
BSC6900
WRFD-020305
Inter-RAT Handover Based on Service
Inter system Service Handover
BSC6900
Issue 03 (2010-09-20)
7-37
Feature ID
Feature Name
License Control Item Inter system Load Handover
Configuration Method 7.139 Configuring Inter-RAT Handover Based on Load 7.140 Configuring DRD Introduction Package 7.141 Configuring Intra-System Direct Retry 7.142 Configuring Inter-System Direct Retry 7.143 Configuring Inter-System Redirect 7.144 Configuring Traffic Steering and Load Sharing During RAB Setup 7.145 Configuring Inter-RAT Redirection Based on Distance 7.146 Configuring Measurementbased Direct Retry
WRFD-020306
Inter-RAT Handover Based on Load
WRFD-020400
DRD Introduction Package
None
None
WRFD-020400 01
Intra System Direct Retry
Intra System Direct Retry
BSC6900
WRFD-020400 02
Inter System Direct Retry
Inter System Direct Retry
BSC6900
WRFD-020400 03
Inter System Redirect
Inter System Redirect
BSC6900
WRFD-020400 04
Traffic Steering and Load Sharing During RAB Setup
None
None
WRFD-020401
Inter-RAT Redirection Based on Distance
Inter System Redirect Based on Distance
BSC6900
WRFD-020402
Measurement Based Direct Retry
Measurement Based Direct Retry Function
BSC6900
7-38
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item Fast Dormancy Enhancement (per PS Active User) Cell Barring when IU in fault 3G/2G Common Load Management
Configuration Method 7.147 Configuring Enhanced Fast Dormancy 7.148 Configuring Cell Barring 7.149 Configuring 3G/2G Common Load Management 7.150 Configuring RAB Quality of Service Renegotiation over Iu Interface 7.151 Configuring Rate Negotiation at Admission Control 7.152 Configuring Service Steering and Load Sharing in RRC Connection Setup 7.153 Configuring TCP Accelerator 7.154 Configuring Uplink Flow Control of User Plane
WRFD-020500
Fast Dormancy Enhancement
WRFD-021102
Cell Barring
BSC6900
WRFD-020310
3G/2G Common Load Management
BSC6900
WRFD-010506
RAB Quality of Service Renegotiation over Iu Interface
RAB Quality of Service Renegotiation over Iu
BSC6900
WRFD-010507
Rate Negotiation at Admission Control
RAB Downsizing at Admission Control
BSC6900
WRFD-020120
Service Steering and Load Sharing in RRC Connection Setup
Service Steering in RRC Connection Setup
BSC6900
WRFD-020123
TCP Accelerator
TCP Accelerator
BSC6900
WRFD-020124
Uplink Flow Control of User Plane
Uplink Flow Control of User Plane
BSC6900
Issue 03 (2010-09-20)
7-39
Feature ID
Feature Name
License Control Item Active Queue Management (AQM)
Configuration Method 7.155 Configuring Active Queue Management (AQM) 7.156 Configuring Quality Improvement for Subscribed Service 7.157 Configuring Cell Broadcast Service 7.158 Configuring Simplified Cell Broadcast 7.159 Configuring TFO/TrFO 7.160 Configuring Dynamic Power Sharing of MultiCarriers 7.161 Configuring Multi-Carrier Switch off Based on Traffic Load 7.162 Configuring Energy Efficiency Improved
WRFD-011502
Active Queue Management (AQM)
WRFD-020128
Quality Improvement for Subscribed Service
Quality Improvement for Subscribed Service
BSC6900
WRFD-011000
Cell Broadcast Service
Cell broadcast service
BSC6900
WRFD-011001
Simplified Cell Broadcast
Simplified Cell Broadcast Service TFO/TrFO
BSC6900
WRFD-011600
TFO/TrFO
BSC6900
WRFD-020116
Dynamic Power Sharing in Multi-Carriers
Dynamic Power Sharing in Multi-Carriers Function (per Cell) Multi-carrier switch off based on traffic load
NodeB
WRFD-020117
Multi-Carrier Switch off Based on Traffic Load
BSC6900
WRFD-020118
Energy Efficiency Improved
Energy Efficiency Improved Function (per NodeB)
NodeB
7-40
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item None
License Configured on... None
Configuration Method 7.163 Configuring Multi-Carrier Switch off Based on Power Backup 7.164 Configuring AMR-WB (Adaptive Multi Rate Wide Band) 7.165 Configuring AMR/WBAMR Speech Rates Control 7.166 Configuring Overbooking on ATM Transmission 7.167 Configuring VoIP over HSPA/HSPA+ None
WRFD-020119
Multi-Carrier Switch off Based on Power Backup
WRFD-010613
AMR-WB (Adaptive Multi Rate Wide Band)
Wide Band AMR
BSC6900
WRFD-020701
AMR/WBAMR Speech Rates Control
AMR voice coding rate control
BSC6900
WRFD-050405
Overbooking on ATM Transmission
ATM IUB overbooking Function
BSC6900
WRFD-010617
VoIP over HSPA/HSPA+
VoIP over HSPA Introduction Pakage VoIP over HSPA Introduction Pakage VoIP over HSPA Introduction Pakage
BSC6900
WRFD-010617 01
RAB Mapping
BSC6900
WRFD-010617 03
Optimized Scheduling for VoIP over HSPA
BSC6900
7.168 Configuring Optimized Scheduling for VoIP over HSPA 7.169 Configuring IMS Signaling over HSPA
WRFD-010618
IMS Signaling over HSPA
IMS Signaling over HSPA
BSC6900
Issue 03 (2010-09-20)
7-41
Feature ID
Feature Name
License Control Item PDCP ROHC Function
Configuration Method 7.170 Configuring PDCP Header Compression (RoHC) 7.171 Configuring CS Voice over HSPA/HSPA+ 7.172 Configuring Cell ID + RTT FunctionBased LCS 7.173 Configuring OTDOABased LCS 7.174 Configuring AGPS-Based LCS 7.175 Configuring LCS Classified Zone 7.176 Configuring LCS over Iur 7.177 Configuring Iupc Interface for LCS Service 7.178 Configuring RAN Sharing Introduction Package Package
WRFD-011501
PDCP Header Compression (RoHC)
WRFD-010619
CS voice over HSPA/HSPA+
CS voice over HSPA
BSC6900
WRFD-020801
Cell ID + RTT Function Based LCS
Cell ID LCS
BSC6900
WRFD-020802
OTDOA Based LCS
OTDOA LCS
BSC6900
WRFD-020803
A-GPS Based LCS
AGPS LCS
BSC6900
WRFD-020804
LCS Classified Zones
LCS Classified Zones
BSC6900
WRFD-020805
LCS over Iur
LCS over Iur
BSC6900
WRFD-020807
Iupc Interface for LCS service
Iu-PC Interface for LCS service
BSC6900
WRFD-021304
RAN Sharing Introduction Package
RAN Sharing Function
BSC6900
7-42
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item RAN Sharing Function
Configuration Method 7.179 Configuring Dedicated Carrier for Each Operator 7.180 Configuring Flexible Network Architecture 7.181 Configuring Mobility Control and Service Differentiation 7.182 Configuring Independent License Control None
WRFD-021304 01
Dedicated Carrier for Each Operator
WRFD-021304 02
Flexible Network Architecture
BSC6900
WRFD-021304 03
Mobility Control and Service Differentiation
BSC6900
WRFD-021304 04
Independent License Control
BSC6900
WRFD-021304 05 WRFD-021304 06
Independent Cell-level FM/ PM/CM Transmission Recourse Sharing on Iub/ Iur Interface RAN Sharing Phase 2
RAN Sharing Function RAN Sharing Function
BSC6900
BSC6900
None
WRFD-021305
RAN Sharing Enhanced Package None
BSC6900
7.183 Configuring RAN Sharing Phase 2 7.184 Configuring WRFD-021305 01 Dedicated Iub Transmission Control 7.185 Configuring IMSI-Based Handover
WRFD-021305 01
Dedicated Iub Transmission Control
None
WRFD-021303
IMSI Based Handover
IMSI Based Handover
BSC6900
Issue 03 (2010-09-20)
7-43
Feature ID
Feature Name
License Control Item MOCN Introduction Package
Configuration Method 7.186 Configuring MOCN Introduction Package 7.187 Configuring Carrier Sharing by Operators 7.188 Configuring Dedicated NodeB/Cell for Operators 7.189 Configuring MOCN Mobility Management 7.190 Configuring MOCN Load Balance None
WRFD-021311
MOCN Introduction Package
WRFD-021311 01
Carrier Sharing by Operators
BSC6900
WRFD-021311 02
Dedicated NodeB/Cell for Operators
BSC6900
WRFD-021311 03
MOCN Mobility Management
BSC6900
WRFD-021311 04
MOCN Load Banlance
MOCN Introduction Package MOCN Introduction Package IU FLEX
BSC6900
WRFD-021311 05
MOCN Independent Performance Management Iu Flex
BSC6900
WRFD-021302
BSC6900
7.191 Configuring Flexible Network Architecture 7.192 Configuring Iu Flex Load Distribution Management
WRFD-021306
Iu Flex Load Distribution Management
Enhanced Iu Flex
BSC6900
7-44
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item Multi Frequency Band Networking Management
Configuration Method 7.193 Configuring MultiFrequency Band Networking Management 7.194 Configuring Enhanced Multiband Management 7.195 Configuring Satellite Transmission on Iub Interface 7.196 Configuring Satellite Transmission on Iu Interface 7.197 Configuring MBMS Introduction Package 7.198 Configuring MBMS Broadcast Mode 7.199 Configuring MBMS Admission Control 7.200 Configuring MBMS Load Control
WRFD-020110
Multi Frequency Band Networking Management
WRFD-020160
Enhanced Multiband Management
Enhancement for Multi frequency band Networking management Satellite Communication in Iub Interface
BSC6900
WRFD-050104
Satellite Transmission on Iub Interface
BSC6900
WRFD-050108
Satellite Transmission on Iu Interface
Satellite Transmission on Iu Interface
BSC6900
WRFD-010616
MBMS Introduction Package
MBMS Function
BSC6900
WRFD-010616 01
MBMS Broadcast Mode
MBMS Function
BSC6900
WRFD-010616 02
MBMS Admission Control
MBMS Function
BSC6900
WRFD-010616 03
MBMS Load Control
MBMS Function
BSC6900
Issue 03 (2010-09-20)
7-45
Feature ID
Feature Name
License Control Item MBMS Function
Configuration Method 7.201 Configuring MBMS Soft/ Selective Combination 7.202 Configuring MBMS Transport Resource Management 7.203 Configuring Streaming Service on MBMS 7.204 Configuring MBMS 2 Channels per Cell 7.205 Configuring 16/32/64/128K bps Channel Rate on MBMS 7.206 Configuring MBMS Phase 2 7.207 Configuring MBMS Enhanced Broadcast Mode 7.208 Configuring MBMS P2P over HSDPA
WRFD-010616 04
MBMS Soft/ Selective Combining
WRFD-010616 05
MBMS Transport Resource Management
MBMS Function
BSC6900
WRFD-010616 06
Streaming Service on MBMS
MBMS Function
BSC6900
WRFD-010616 07
MBMS 2 Channels per Cell
MBMS Function
BSC6900
WRFD-010616 08
16/32/64/128K bps Channel Rate on MBMS
MBMS Function
BSC6900
WRFD-010660
MBMS Phase 2
MBMS P2P over HSDPA MBMS Enhanced Broadcast Mode
None
WRFD-010660 01
MBMS Enhanced Broadcast Mode
BSC6900
WRFD-010660 02
MBMS P2P over HSDPA
MBMS P2P over HSDPA
BSC6900
7-46
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item MBMS Admission Enhancement
Configuration Method 7.209 Configuring MBMS Admission Enhancement 7.210 Configuring InterFrequency Neighboring Cell Selection for MBMS PTP Users 7.211 Configuring FACH Transmission Sharing for MBMS 7.212 Configuring MBMS FLC (Frequency Layer Convergence)/ FLD (Frequency Layer Dispersion) None
WRFD-010660 03
MBMS Admission Enhancement
WRFD-010660 04
Inter-Frequency Neighboring Cell Selection for MBMS PTP Users
None
None
WRFD-010627
FACH Transmission Sharing for MBMS
None
None
WRFD-010626
MBMS FLC (Frequency Layer Convergence)/ FLD(Frequency Layer Dispersion)
MBMS FLC (Frequency Layer Convergence)/ FLD(Frequency Layer Dispersion)
BSC6900
WRFD-010624
MBMS 8 Channels per Cell 256Kbps Channel Rate on MBMS MBMS 16 Channels per Cell MBMS over Iur
MBMS 8 Channels per Cell 256Kbps Channel Rate on MBMS MBMS 16 Channels per Cell MBMS over Iur
BSC6900
WRFD-010625
BSC6900
None
WRFD-010628
BSC6900
None
WRFD-010661
BSC6900
7.213 Configuring MBMS over Iur
Issue 03 (2010-09-20)
7-47
Feature ID
Feature Name
License Control Item Dynamic Power Estimation for MTCH
Configuration Method 7.214 Configuring Dynamic Power Estimation for MTCH 7.215 Configuring MSCH and MSCH Scheduling 7.216 Configuring MBMS Channel Audience Rating Statistics 7.217 Configuring Domain Specific Access Control (DSAC) 7.218 Configuring One Tunnel None
WRFD-010662
Dynamic Power Estimation for MTCH
WRFD-010663
MSCH and MSCH Scheduling
MSCH Scheduling
BSC6900
WRFD-010665
MBMS Channel Audience Rating Statistics
MBMS Channel Audience Rating Statistics
BSC6900
WRFD-020114
Domain Specific Access Control (DSAC)
Domain Specific Access Control (DSAC)
BSC6900
WRFD-020111
One Tunnel
One Tunnel
BSC6900
WRFD-050402
IP Transmission Introduction on Iub Interface Fractional IP Function on Iub Interface Hybrid Iub IP Transmission
IP Transportation in Iub Interface Fractional IP
BSC6900
WRFD-050411
BSC6900
None
WRFD-050403
IUB Hybrid IP Transportation Function IUB ATM/IP Dual Stack Transportation Function
BSC6900
7.219 Configuring Hybrid Iub IP Transmission 7.220 Configuring ATM/IP Dual Stack Node B
WRFD-050404
ATM/IP Dual Stack NodeB
BSC6900
7-48
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item IP Transportation in Iu Interface IP Transportation in Iur Interface FP MUX
WRFD-050409
IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface FP MUX for IP Transmission
WRFD-050410
BSC6900
None
WRFD-050420
BSC6900
7.221 Configuring FP MUX for IP Transmission 7.222 Configuring IP Fault Detection Based on BFD 7.223 Configuring Dynamic Bandwidth Control of Iub IP 7.224 Configuring Overbooking on IP Transmission 7.225 Configuring UDP MUX for Iu-CS Transmission 7.226 Configuring ATM SwitchingBased Hub NodeB 7.227 Configuring AAL2 SwitchingBased Hub NodeB
WRFD-050421
IP Fault Detection Based on BFD Dynamic Bandwidth Control of Iub IP
BFD/ARP IP Re-route
BSC6900
WRFD-050422
Dynamic Bandwidth Control of Iub IP
BSC6900
WRFD-050408
Overbooking on IP Transmission
IP IUB overbooking Function
BSC6900
WRFD-050412
UDP MUX for Iu-CS Transmission
UDP MUX for Iu-CS Transmission
BSC6900
WRFD-050105
ATM Switching Based Hub NodeB
None
None
WRFD-050106
AAL2 Switching Based Hub NodeB
None
None
Issue 03 (2010-09-20)
7-49
Feature ID
Feature Name
License Control Item None
License Configured on... None
Configuration Method 7.228 Configuring IP Routing-Based Hub NodeB 7.229 Configuring Overbooking on Hub Node B Transmission 7.230 Configuring Ethernet OAM 7.231 Configuring Clock Synchronizatio n on Ethernet in NodeB 7.232 Configuring Synchronous Ethernet 7.233 Configuring RNC Node Redundancy 7.234 Configuring RRU Redundancy 7.235 Configuring Transmit Diversity 7.236 Configuring 4Antenna Receive Diversity
WRFD-050107
IP routing Based Hub NodeB
WRFD-050406
ATM QoS Introduction on Hub NodeB (Overbooking on Hub NodeB Transmission) Ethernet OAM
HUB IUB overbooking Function
BSC6900
WRFD-050425
None
None
WRFD-050501
Clock Sync on Ethernet in NodeB
IP Clock Sync on Ethernet in NodeB (per NodeB)
NodeB
WRFD-050502
Synchronous Ethernet
Ethernet Synchronizatio n Function (per NodeB) RNC Node Redundancy
NodeB
WRFD-040202
RNC Node Redundancy
BSC6900
WRFD-040203
RRU Redundancy
None
None
WRFD-010203
Transmit Diversity
None
None
WRFD-010209
4-Antenna Receive Diversity
None
None
7-50
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item Common Channel Parallel Interference Cancellation (CCPIC) (per NodeB) None
WRFD-010210
Control Channel Parallel Interference Cancellation (CCPIC) Extended Cell Coverage up to 200km
WRFD-021308
None
7.237 Configuring Extended Cell Coverage up to 200km None
WRFD-021309
Improved Downlink Coverage High Speed Access
Improved Downlink Coverage None
BSC6900
WRFD-010206
None
7.238 Configuring High Speed Access 7.239 Configuring PDCP Header Compression (RFC2507) None
WRFD-011500
PDCP Header Compression (RFC2507)
PDCP Header compression
BSC6900
WRFD-050302
Fractional ATM Function on Iub Interface HCS (Hierarchical Cell Structure)
Fractional ATM
BSC6900
WRFD-021200
Hierarchical Cell Structure
BSC6900
7.240 Configuring HCS (Hierarchical Cell Structure) 7.241 Configuring Intra Frequency Load Balance 7.242 Configuring Potential User Control
WRFD-020104
Intra Frequency Load Balance
Intra frequency load balancing
BSC6900
WRFD-020105
Potential User Control
Potential user control
BSC6900
Issue 03 (2010-09-20)
7-51
Feature ID
Feature Name
License Control Item License Control for Urgency
Configuration Method 7.243 Configuring License Control for Urgency 7.244 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g 7.245 Configuring NACC Procedure Optimization Based on Iur-g 7.246 Configuring MBSC Load Balancing 7.247 Configuring GSM and UMTS Traffic Steering Based on Iur-g 7.248 Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority 7.249 Configuring Warning of Disaster
WRFD-040300
License Control for Urgancy
WRFD-070004
Load Based GSM and UMTS Handover Enhancement Based on Iur-g
Handover Based on Load on Iur-g
BSC6900
WRFD-070005
NACC Procedure Optimization Based on Iur-g
NACC Procedure Optimization Based on Iur-g
BSC6900
WRFD-070006
GSM and UMTS Load Balancing Based on Iur-g GSM and UMTS Traffic Steering Based on Iur-g
BSC Load Balancing Based on Iur-g BSC Service Distribution Based on Iur-g
BSC6900
WRFD-070007
BSC6900
WRFD-070201
GSM and UMTS Intelligent Shutdown Based on RAT Priority
None
None
WRFD-020127
Warning of Disaster
Warning of Disaster
BSC6900
7-52
Issue 03 (2010-09-20)
Feature ID
Feature Name
License Control Item Flexible frequency bandwidth of UMTS carrier function enabled None
WRFD-021001
Flexible frequency bandwidth of UMTS carrier
MRFD-221801
Multi-mode Dynamic Power Sharing (UMTS)
None
7.250 Configuring Multi-mode Dynamic Power Sharing (UMTS) 7.251 Configuring IP-Based Multi-Mode CoTransmission on Base Station Side (NodeB) 7.252 Configuring TDM-Based Multi-mode CoTransmission via Backplane on BS side (NodeB) 7.253 Configuring Multi-Mode BS Common Reference Clock (NodeB)
MRFD-221501
IP-Based Multimode CoTransmission on BS side (NodeB)
None
None
MRFD-221504
TDM-Based Multi-mode CoTransmission via Backplane on BS side (NodeB)
None
None
MRFD-221601
Multi-mode BS Common Reference Clock(NodeB)
None
None
7.2 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. 7.2.1 Activating the BSC6900 License
This describes how to activate the BSC6900 license. 7.2.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. 7.2.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.
7.2.1 Activating the BSC6900 License

This describes how to activate the BSC6900 license.
Prerequisite
l l The LMT is started and you are logged in to the BSC6900. The BSC6900 is in service.
Procedure
Step 1 Run BSC6900 MML commond LST ESN and record the Equipment Serial Number (ESN) of the BSC. Step 2 Run BSC6900 MML commond DLD LICENSE to download the license file from the FTP server to OMU active workspace\FTP\License. Step 3 Run LST LICENSE commond and enter the name of the license file to be activated to query the file information. If... Then...
The file information comply with the information of the Go to Step 4. 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 LST CFGMODE commond to query the BSC6900 configuration status. If the BSC6900 is ineffective, run SET CFGDATAEFFECTIVE commond to switch it to effective. Step 5 Run ACT LICENSE commond to activate the license file. Step 6 (Optional)If primary operator and secondary operators exist, run SET LICENSE to active the license for the primary operator first and then for secondary operators. If multiple secondary operators exist, run SET LICENSE repeatedly. Step 7 Run BSC6900 MML commondCMP LICENSE to check whether the running license on the host is consistent with that on the OMU.
7-54
Issue 03 (2010-09-20)
If...
Then...
If the running license on the host is consistent with that Exit the task or go to Step 8. on the OMU If the running license on the host is not consistent with Exit the task and contact Huawei. that on the OMU Step 8 (Optional) When the traffic volume is high, run SET LICENSECTRL commond and set the grace guard switch to "ON" to enable the BSC6900 function control item for emergency scenario . For details, see BSC6900 License Operations in Emergency Scenario. ----End
7.2.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.
Prerequisite
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
7.2.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.
Prerequisite
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 7.2.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. 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. 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 choose License 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
7-56
Issue 03 (2010-09-20)
Result
When delivering license allocation information to NodeBs, the M2000 delivers only new control item values and the control item values that are inconsistent on the NodeBs and the M2000.
NOTE
The control item values that have been delivered to NodeBs are still valid after an M2000 upgrade or a license capacity expansion.
If resource control item values are incorrectly set, the total number of resources used by NodeBs may exceed the maximum available resource number specified in the license, and the license may fail to be allocated to NodeBs. In this case, you need to set the resource control items and allocate the license to NodeBs again. If setting resource control item values fails or the resource control item values used by NodeBs are inconsistent with the corresponding values set on the M2000, and you need to synchronize the license allocation information saved on the M2000 to the NodeBs.
7.3 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment

This section describes how to activate, verify, and deactivate the basic feature WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment.
Prerequisite
l l l Dependency on Hardware None Dependency on Other Features None License None
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 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.
Verification Procedure 1. Start Iub interface tracing on the BSC6900 LMT, as shown in Figure 7-1
Issue 03 (2010-09-20)
Figure 7-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. 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.
3.
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. This feature does not need to be deactivated.
Deactivation Procedure 1.
----End
Example
//Activating 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release. //set the channel type and bit rate corresponding to a specific RRC connection establishment cause
7-58
Issue 03 (2010-09-20)

SET URRCESTCAUSE: RrcCause=ORIGCONVCALLEST, SigChType=DCH_3.4K_SIGNALLING, EFachSwitch=OFF; SET URRCESTCAUSE: RrcCause=ORIGCONVCALLEST, SigChType=DCH_6.8K_SIGNALLING, EFachSwitch=OFF; SET URRCESTCAUSE: RrcCause=ORIGCONVCALLEST, SigChType=DCH_13.6K_SIGNALLING, EFachSwitch=OFF; SET URRCESTCAUSE: RrcCause=ORIGCONVCALLEST, SigChType=DCH_27.2K_SIGNALLING, EFachSwitch=OFF;
7.4 Configuring Conversational QoS Class

This section describes how to activate, verify, and deactivate the basic feature WRFD-010501 Conversational QoS Class.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License None 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 thus has a high requirement on real-time transmission. The conversational class has the following fundamental characteristics: l 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 l 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 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
Issue 03 (2010-09-20)
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set CS voice channel type and VOIP channel type to DCH(UL_DCH,DL_DCH). Initiate Iub interface tracing on the BSC6900 LMT, as shown in Figure 7-2. Figure 7-2 Iub interface trace dialog box
Verification Procedure 1.
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. View the trafficClass IE in the rRB-Parameters IE of the RANAP_RAB_ASSIGNMENT_REQ message to verify that the traffic class is conversational. 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
3.
4.
7-60
Issue 03 (2010-09-20)
downlink rate of the conversational service. In this case, the uplink rate of the service is 0. If the value of the rAB-AsymmetryIndicator IE is Asymmetric Uni directional Uplink, then the maxBitrate IE contains one value, which indicates the uplink 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. This feature does not need to be deactivated.
----End
Example
//Activating conversational QoS class SET UFRCCHLTYPEPARA: CSVoiceChlType=DCH, VoipChlType=DCH;
7.5 Configuring Streaming QoS Class

This section describes how to activate, verify, and deactivate the basic feature WRFD-010502 Streaming QoS Class.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License None 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 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.
Issue 03 (2010-09-20)
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 Activation Procedure 1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA 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. 3. l
Optional: Run the BSC6900 MML command DEA UCELLHSDPA to disable the HSDPA capability of the cell. Optional: Run the BSC6900 MML command DEA UCELLHSUPA to disable the HSUPA capability of the cell. Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 7-3 Figure 7-3 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. Check the RANAP_RAB_ASSIGNMENT_REQ message and check that the value of the trafficClass information element (IE) in rRB-Parameters is streaming. View the maxBitrate and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ message.
3. 4.
7-62
The expected result: If the value of the rAB-AsymmetryIndicator IE is Asymmetric bidirectional, 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. 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. If the value of the rAB-AsymmetryIndicator IE is Asymmetric Uni directional 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. If the value of the rAB-AsymmetryIndicator IE is Asymmetric Uni directional 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. This feature does not need to be deactivated.
----End
Example
//Activating Streaming Class QoS SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D384, UlStrThsOnHsupa=D384; DEA UCELLHSDPA: CellId=1; DEA UCELLHSUPA: CellId=1;
7.6 Configuring Interactive QoS Class

This section describes how to activate, verify, and deactivate the basic feature WRFD-010503 Interactive QoS Class.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License None Others The UE and CN support interactive 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 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.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the 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. Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 7-4 Figure 7-4 Iu Interface Trace dialog box
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. View the maxBitrate and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ message.
3.
7-64
The expected result: If the value of the rAB-AsymmetryIndicator IE is Asymmetric bidirectional, the maxBitrate IE contains two values. The first value indicates the downlink rate of the interactive service, and the second indicates the uplink rate of the service. 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. l Deactivation Procedure 1. ----End This feature does not need to be deactivated.
Example
//Activating Interactive QoS Class SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900, UlBeTraffThsOnHsupa=D5740;
7.7 Configuring Background QoS Class

This section describes how to activate, verify, and deactivate the basic feature WRFD-010504 Background QoS Class.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License None Others The UE and CN support this feature.
Context
Based on QoS requirements, there are four traffic classes: conversational, streaming, interactive, 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.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the 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. Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 7-5 Figure 7-5 Iu Interface Trace dialog box
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. View the maxBitrate and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ message. The expected result: If the value of the rAB-AsymmetryIndicator IE is Asymmetric bidirectional, the maxBitrate IE contains two values. The first value indicates the downlink rate of the background service, and the second indicates the uplink rate of the service. 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.
3.
l
7-66
Deactivation Procedure
1. ----End
This feature does not need to be deactivated.
Example
//Activating Background QoS Class SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900, UlBeTraffThsOnHsupa=D5740;
7.8 Configuring Emergency Call

This section describes how to activate, verify, and deactivate the basic feature WRFD-021104 Emergency Call.
Prerequisite
Context
This feature grants higher priority to emergency calls so that they are preferentially processed, compared to normal calls.
Procedure
l l l Activation Procedure This feature need not be activated. Verification Procedure 1. Use a UE to initiate a emergency call. The emergency call is successfully established. Deactivation Procedure This feature need not be deactivated.
----End
7.9 Configuring 2-Antenna Receive Diversity(NodeB)

This section describes how to activate, verify, and deactivate the basic feature MRFD-210604 2-Antenna Receive Diversity on the UMTS side.
Prerequisite
l l
Issue 03 (2010-09-20)
Dependency on Hardware None Dependency on Other Features

None l License None
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 Activation Procedure 1. l Run the NodeB MML command ADD SEC. In this step, set Antenna Magnitude to 2. Run the NodeB MML command LST SEC to query the value of Antenna Magnitude. The expected result: Antenna Magnitude is 2. l Deactivation Procedure This feature does not need to be deactivated. ----End
7.10 Configuring Cell Digital Combination and Split

This section describes how to activate, verify, and deactivate the basic feature WRFD-010205 Cell Digital Combination and Split.
Prerequisite
l Dependency on Hardware The DBS3900, DBS3800, iDBS3900, and iDBS3800 support the feature. In the 0.5/0.5 configuration mode, the dependency between NodeB hardware is as follows: A maximum of two RRUs share one cell. Each RRU can be configured with the oneantenna or two-antenna receive mode. During baseband demodulation, signals from the two RRUs are processed as two-antenna or four-antenna receive diversity. One CPRI port supports a maximum of four RRUs. A maximum of two RRUs share one cell, so a maximum of two cells are supported on one CPRI port. The two RRUs connected to different CPRI ports cannot be configured in a one cell. One BBU supports a maximum of six CPRI ports and thus a maximum of 24 RRUs. A maximum of two RRUs share one cell, so a maximum of 12 cells are supported. In four-antenna receive diversity, the cell-supporting specification of the WBBPb3 and WBBPb4 boards reduces from six cells to three cells. One WBBPb board including the WBBPb1/2/3/4 supports three cells and three CPRI ports. Limited by the processing capability for three cells, one WBBPb board supports a maximum of six RRUs.
Mixing the 0.5/0.5 cells with common cells is not recommended. With the delay considered, the optical fiber for interconnecting RRUs in one cell should be less than 4 km in length. In the distributed sector configuration mode, the dependency between NodeB hardware is as follows: In the case of the DBS3900 and iDBS3900, when the WBBPa board is configured, each RRU supports only the one-antenna receive mode; when other baseband boards are configured, each RRU can support the one-antenna or two-antenna receive mode. In the case of DBS3800 and iDBS3800, each RRU supports only the one-antenna receive mode. Multiple-antenna receive modes are not supported. One CPRI port supports a maximum of eight cascaded RRUs. A maximum of eight RRUs share one cell. A maximum of three distributed cells are supported. One BBU supports combination of UL digital signals on a maximum of two CPRI ports. A maximum of 16 RRUs share one cell. With the delay considered, the optical fiber for interconnecting RRUs in one cell and with neighboring coverage areas should be less than 4 km in length. l l Dependency on Other Features None License None
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.
Procedure
l Activation Procedure 1. Activate the 0.5/0.5 configuration. (1) Run the NodeB MML command ADD SEC. In this step, set Antenna Magnitude, the corresponding Antenna Channel, cabinet number, and subrack number. (2) Run the NodeB MML command ADD ULGROUP. In this step, set Demodulation Work Mode.
NOTE
l When the RRUs use the one-antenna receive mode, Demodulation Work Mode is set to DEM_2_CHAN(2-Channels Demodulation Mode). l When the RRUs use the two-antenna receive mode, Demodulation Work Mode is set to DEM_4_CHAN(4-Channels Demodulation Mode).
(3) Run the NodeB MML command ADD SEC. In this step, set Diversity Mode to HALFFREQ(HALFFREQ). Set Cover Type to SAMEZONE(SAME ZONE) or DIFFZONE(DIFFZONE).

NOTE
l Under same-zone coverage, two RRUs cover the same zone. The output power sum of both RRUs is the cell output power. l Under different-zone coverage, two RRUs cover different zones. The output power of each RRU equals the cell output power.
2.
Activate the configuration of a distributed sector. (1) Run the NodeB MML command ADD RRUCHAIN. In this step, set Topo Type to CHAIN(Chain Topology Type). Set a group of RRUs in consecutive numbering to the RRUs to be used by the distributed sector.
NOTE
In the case of the DBS3900 and iDBS3900, when the WBBPa board is configured, each RRU supports only the one-antenna receive mode; when other baseband boards are configured, each RRU can support the one-antenna or two-antenna receive mode. Antenna Magnitude can be set to 2 to use the two-antenna receive mode. In addition, you need to set the corresponding Antenna Channel, cabinet number, and subrack number.
(2) Run the NodeB MML command ADD SEC. In this step, set Sector Type to DIST_SECTOR(DIST_SECTOR). (3) Run the NodeB MML command ADD LOCELL. In this step, set Sector Type to DIST_SECTOR(DIST_SECTOR) and set RRU Mode to UNSYNC (UNSYNC) or SYNC(SYNC). l Verification Procedure Verify the 0.5/0.5 configuration. 1. Run the NodeB MML command LST SEC. In this step, check that Diversity Mode is set to HALFFREQ(HALFFREQ).
Verify the configuration of the distributed sector. 1. 2. l Run the NodeB MML command LST SEC. In this step, check that Sector Type is set to DIST_SECTOR(DIST_SECTOR). Run the NodeB MML command LST LOCELL. In this step, check that Sector Type is set to DIST_SECTOR(DIST_SECTOR).
Deactivation Procedure This feature does not need to be deactivated.
----End
7.11 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH)

This section describes how to activate, verify, and deactivate the basic feature WRFD-010202 UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).
Prerequisite
l l
7-70

None l l License None Other Prerequisites The UE must support related states.
Context
This feature enables Huawei RAN to support four states of UE in connected mode: CELL_DCH, CELL_PCH, URA_PCH, and CELL_FACH. This feature helps save radio resources efficiently.
Procedure
l l Activation Procedure This feature need not be activated. Verification Procedure 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 section 7.14 Configuring Dynamic Channel Configuration Control. l Deactivation Procedure This feature need not be deactivated. ----End
7.12 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)

This section describes how to activate, verify, and deactivate the basic feature WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1).
Prerequisite
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 03 (2010-09-20)
Activation Procedure
1. 2.
(Optional) Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented PS BE service state transition switch. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the parameters Cell Reselection Timer, BE DCH to FACH Transition Timer, and BE FACH or E_FACH to PCH Transition Timer to 60s, 30s, and 30s respectively. Run the BSC6900 MML command SET UUESTATETRANS to set the parameter Cell Reselection Counter Threshold to 1. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, Trace Mode and Save File. Then, click Submit. 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. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. On the HLR, set the PS service type to background or interactive. 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. 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. 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. Use UE2 to call UE1. The RRC_PAGING_TYPE1 message should be displayed. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. 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. Use UE2 to call UE1. The RRC_PAGING_TYPE1 message should be displayed.
NOTE
3. 4. l
Verification Procedure (Paging a UE in Idle Mode) 1. 2. 3.
Commissioning Procedure (Paging a UE in CELL_PCH State) 1. 2. 3.
4.
5.
6. l 1. 2.
Verification Procedure (Paging a UE in URA_PCH)
3.
For details about how to enable UE transition to CELL_PCH or URA_PCH state, see 7.11 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).
l
7-72
1. ----End
This feature does not need to be deactivated.
Example
//Activating paging type 1 SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: CellReSelectTimer=60, BeD2FStateTransTimer=30, BeF2PStateTransTimer=30; SET UUESTATETRANS: CellReSelectCounter=1; SET UPSINACTTIMER: PsInactTmrForInt=1440, ProtectTmrForInt=20, PsInactTmrForBac=1440, ProtectTmrForBac=20;
7.13 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2)

This section describes how to activate, verify, and deactivate the basic feature WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2).
Prerequisite
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 Activation Procedure 1. 2. 3. l (Optional) Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented PS BE service state transition switch. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the parameter BE DCH to FACH Transition Timer[s] to 30s. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, Trace Mode and Save File. Then, click Submit.
Verification Procedure (Paging a UE in CELL_DCH State) 1. 2.
Issue 03 (2010-09-20)
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. Use UE2 to call UE1. The RRC_PAGING_TYPE2 message should be displayed. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, and Save File, and then click Submit. The Trace Data tab page is displayed. On the HLR, set the PS service type to background or interactive. 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. Do not send any data from UE1 for 30 seconds. Then, you can view that the network side perform UE transition to CELL_FACH state through the RRC_RB_RECFG message. The value of rrc-stateindicator IE should be CELL_FACH. Use UE2 to call UE1. The RRC_PAGING_TYPE2 message should be displayed. This feature does not need to be deactivated.
4. l 1. 2. 3. 4.
Verification Procedure (Paging a UE in CELL_FACH State)
5.
6. l 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;
7.14 Configuring Dynamic Channel Configuration Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-021101 Dynamic Channel Configuration Control.
Prerequisite
Context
This feature is implemented on the BSC6900. It enables dynamic rate adjustment and UE state transition triggered by various reasons. With this feature, the BE service rate can be adjusted on the basis of traffic, throughput, radio link quality or cell congestion state. In this way, the utilization of radio resources is improved and the stability of radio links is ensured.
This feature provides two major functions: rate adjustment and UE state transition. It comprises rate adjustment based on traffic, rate adjustment based on throughput, rate adjustment based on link quality, BE service rate reduction and recovery based on basic congestion, UE state transition algorithm, and always online.
Procedure
l Activating DCCC 1. 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the DCCC algorithm. Activating Traffic Volume-Based BE Service Rate Adjustment (1) Run the BSC6900 MML command MOD UTYPRABDCCCMC to set the following 4A and 4B parameters: Direction Event4AThd Event4BThd TimetoTrigger4A TimetoTrigger4B PendingTime4A PendingTime4B (2) Run the BSC6900 MML command SET UDCCC to set the following RNCoriented parameters related to the DCCC algorithm: DcccStg UlRateUpAdjLevel UlRateDnAdjLevel DlRateUpAdjLevel DlRateDnAdjLevel UlDcccRateThd DlDcccRateThd UlMidRateCalc DlMidRateCalc UlMidRateThd DlMidRateThd 3. Activating Throughput-Based BE Service Rate Adjustment (1) Run the BSC6900 MML command SET UCORRMALGOSWITCH to set DRA_THROU_DCCC_SWITCH to ON. (2) Run the BSC6900 MML command SET UDCCC to set DCH Throu Meas Period and HSUPA DCCC strategy. (3) Run the BSC6900 MML command ADD UTYPRABDCCCMC to set the following 4A and 4B parameters for E-DCH and DCH: Period Amount to trigger 4B on DCH Period Amount after trigger 4B on DCH 4.
Issue 03 (2010-09-20)
Activating Link Stability-Based BE Service Rate Adjustment

(1) Run the BSC6900 MML command SET UQOSACT to set the link stabilitybased DCCC algorithm parameters. Assume that the first action for BE QoS is rate decrease. Then, the following parameters need to be set: QOS Switch For BE Traffic First Action For BE Uplink QOS First Action For BE Downlink QOS Timer For BE Inter Iur Rate[s] (2) Run the BSC6900 MML command SET UDCCC to set the following RNCoriented parameters related to the DCCC algorithm: Uplink Full Coverage Bit Rate Downlink Full Coverage Bit Rate (3) Run the BSC6900 MML command ADD UCELLDCCC to set the following cell-oriented parameters related to the DCCC algorithm: Uplink Full Coverage Bit Rate Downlink Full Coverage Bit Rate
NOTE
For details about the settings of measurement control parameters, see 7.99 Configuring TTI Switch for BE Services Based on Coverage.
5.
Activating Basic Congestion-Based BE Service Rate Decrease (1) Run the BSC6900 MML command SET UUSERGBR to set the GBR for gold, silver, and copper users requesting interactive and background services. (2) Run the BSC6900 MML command SET UEDCHRATEADJUSTSET to set HSUPA Uplink Rate Adjust Set. (3) Run the BSC6900 MML command SET UDCCC to set the following RNCoriented parameters related to the DCCC algorithm: 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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set the following switches: DRA_PS_BE_STATE_TRANS_SWITCH DRA_PS_NON_BE_STATE_TRANS_SWITCH DRA_HSDPA_STATE_TRANS_SWITCH DRA_HSUPA_STATE_TRANS_SWITCH
NOTE
The HSDPA state transition license is activated before the HSDPA state transition switch is turned on.
2. 3.
Run the BSC6900 MML command SET UUESTATETRANS to set the following parameters related to the UE state transition algorithm: Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the timer parameters related to the UE state transition algorithm.
7-76
4. l
Run the BSC6900 MML command SET UDCCC to set Low Activity Bit Rate Threshold. Run the BSC6900 MML command SET UPSINACTTIMER to set the following parameters related to the timer 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
Activating Always Online 1.
Verification Procedure 1. 2. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether dynamic resource allocation switches are turned on. Run the following BSC6900 MML commands to check whether the parameters related to traffic volume-based BE service rate adjustment are correctly set: LST UTYPRABDCCCMC LST UDCCC 3. 4. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether the throughput-based BE service rate adjustment switch is turned on. Run the following BSC6900 MML commands to check whether the parameters related to link stability-based BE service rate adjustment are correctly set: LST UQOSACT LST UDCCC LST UCELLDCCC 5. Run the following BSC6900 MML commands to check whether the parameters related to basic congestion-based BE service rate decrease are correctly set: LST UUSERGBR LST UEDCHRATEADJUSTSET LST UDCCC
Verifying the UE State Transition Algorithm 1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether the UE state transition algorithm switches are turned on. Run the BSC6900 MML command LST UPSINACTTIMER to check whether the parameters related to always online are correctly set.
Verifying Always Online 1.
l
Issue 03 (2010-09-20)
1. 2. ----End
Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the associated switches. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set DRA_DCCC_SWITCH to OFF.
Example
//Activating the DCCC algorithm SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1; //Activating traffic volume-based BE service rate adjustment MOD UTYPRABDCCCMC: RabIndex=9, Direction=DOWNLINK, Event4aThd=D1024, Event4bThd=D16, TimetoTrigger4A=D240, PendingTime4A=D4000, TimetoTrigger4B=D2560, PendingTime4B=D4000;%% RETCODE = 235217157 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_DCCC_SWITCH-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_THROUGHPUT_DCCC_SWITCH-1; SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH, DchThrouMeasPeriod=100; ADD UTYPRABDCCCMC: RabIndex=1, Direction=UPLINK, Event4bThd=D64, DchThrouTimetoTrigger4B=2, DchThrouPendingTime4B=16; SET UUESTATETRANS: E2FThrouMeasPeriod=30; //Activating link stability-based BE service rate adjustment SET UQOSACT: BEQosPerform=YES, BeUlAct1=RateDegrade, BeDlAct1=RateDegrade, BEInterIurRateUpTimer=20; SET UDCCC: UlFullCvrRate=D64, DlFullCvrRate=D64; ADD UCELLDCCC: CellId=0, UlFullCvrRate=D64, DlFullCvrRate=D64; //Activating basic congestion-based BE service rate decrease 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 SET UCORRMALGOSWITCH: 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; 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,
7-78
Issue 03 (2010-09-20)
PsInactTmrForBac=240, ProtectTmrForBac=10, PsInactTmrForCon=240, ProtectTmrForCon=10,PsInactTmrForStr=240, ProtectTmrForStr=10, PSInactTmrForImsSig=3600, ProtectTmrForImsSig=10;
7.15 Configuring Integrity Protection

This section describes how to activate, verify, and deactivate the basic feature WRFD-011401 Integrity Protection.
Prerequisite
Context
This feature protects the network and user data from being listened and modified illegally.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UUIA to enable the RNC to support the integrity protection algorithm. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu Interface Trace. The Iu Interface Trace dialog box is displayed. Keep UE1 and UE2 in idle mode in CELL1. Use UE2 to call UE1. 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. This feature does not need to be deactivated.
Verification Procedure 1. 2. 3. 4.
----End
Example
//Activating integrity protection SET UUIA: IntegrityProtectAlgo=UIA1-1;
7.16 Configuring Encryption

This section describes how to activate, verify, and deactivate the basic feature WRFD-011402 Encryption.
Prerequisite
Context
The encryption algorithms supported by Huawei RAN include UEA0 and UEA1.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UUEA to enable the RNC to support the encryption algorithm. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu Interface Trace. The Iu Interface Trace dialog box is displayed. Keep UE1 and UE2 in idle mode in CELL1. Use UE2 to call UE1. The messages RANAP_SECURITY_ MODE_COMMAND and RANAP_SECURITY_MODE_COMPLETE should be displayed. The chosenEncryptionAlgorithm IE of the latter message indicates the encryption algorithm. End the calling. UE1 and UE2 return to the idle mode. The messages RANAP_SECURITY_MODE_COMMAND and RANAP_SECURITY_MODE_COMPLETE should be displayed. The chosenEncryptionAlgorithm IE of the latter message indicates the encryption algorithm. This feature does not need to be deactivated.
5. 6.
----End
Example
//Activating encryption SET UUEA: EncryptionAlgo=UEA0-1&UEA1-1;
7.17 Configuring Open Loop Power Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020501 Open Loop Power Control.
Prerequisite
Context
Open loop power control measures the power of received signals, sets the network parameters, considers the QoS requirements, and roughly estimates the path loss. Based on the measurement and estimation results, the BSC6900 instructs the UE or the NodeB about its initial transmit power.
Procedure
l l Activation Procedure 1. The feature does not need to be activated. Verification Procedure Verify the downlink DPCH open loop power control. 1. 2. Use UE 2 to establish a conversation with UE 1. The message NBAP_RL_SETUP_REQ on the Iub interface shows the value of the initialDL-transmissionPower IE. This value is used for the downlink DPCH open loop power control.
Verify the uplink DPCH open loop power control. 1. 2. Run the BSC6900 MML command SET UFRC to set the power control parameter for uplink DPCH. Check the Uplink power control info IE in the RRC messages of the Radio Bearer Setup and DPCCH_Power_Offset = PCPICHPower + Uplink interference + DefaultConstantValue.
Verify the uplink PRACH open loop power control. 1. 2. l 1. ----End Run the BSC6900 MML command MOD UPRACHUUPARAS to configure the parameters for PRACH. The SIB contains the "Constant value" IE that is set to -20. This feature does not need to be deactivated.
Example
//Verifying open loop power control SET UFRC: DefaultConstantValue=-22; MOD UPRACHUUPARAS: CellId=111, PhyChId=1, Constantvalue=-20, PowerRampStep=2, PreambleRetransMax=20;
Issue 03 (2010-09-20)
7-81
7.18 Configuring Downlink Power Balance

This section describes how to activate, verify, and deactivate the basic feature WRFD-020502 Downlink Power Balance.
Prerequisite
Context
In the case of soft handover, error codes in the TPC lead to downlink power drift. Configuring downlink power balance solves the problem of power imbalance between uplink and downlink, and optimizes the gains of soft handover. The severer the downlink power drift is, the less the macro diversity gains. Downlink power balance feature is used to adjust the power drift and improve the performance of the soft handover.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select PC_DOWNLINK_POWER_BALANCE_SWITCH from the Power Control Switch drop-down list box. Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify that PC_DOWNLINK_POWER_BALANCE_SWITCH is selected. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect PC_DOWNLINK_POWER_BALANCE_SWITCH.
----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;
7.19 Configuring Outer Loop Power Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020503 Outer Loop Power Control.
Prerequisite
Context
Outer loop power control guarantees the satisfying quality of services by adjusting the SIR target of the 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 SIR target needs to be adjusted to ensure a desirable service quality. Otherwise, the service quality may be too high or too low. This will accordingly lead to severe interference and power waste.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the OLPC function. Run the BSC6900 MML command ADD UTYPRABOLPC to set the OLPC parameters. Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify that the PC_OLPC_SWITCH is set to ON. Run the BSC6900 MML command LST UTYPRABOLPC to verify that the related OLPC parameters are configured. Run the BSC6900 MML command SET UCORRMALGOSWITCH to deactivate the OLPC function.
Verification Procedure 1. 2.
----End
Example
//Activating outer loop power control SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_SWITCH-1; ADD UTYPRABOLPC: RabIndex=11, SubflowIndex=0, TrchType=TRCH_DCH, DelayClass=1, BLERQuality=-20; //Deactivating outer loop power control SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_SWITCH-0;
7.20 Configuring Inner Loop Power Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020504 Inner Loop Power Control.
Prerequisite
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 l Activation Procedure 1. 1. 2. The feature does not require activation. UE1 calls UE2. UE2 rings, answers and starts the conversation. Observe the variation of the [UL SIR] and [OLPC SIR Target] in the [UL SIR connection performance monitoring] and [OLPC connection performance monitoring] window. UE1 moves in the CELL_A11 to change radio link quality. When you move UE1 away from the CELL_A11, UE transmit power increases and the uplink SIR is approximate to the SIR Target. When you move UE towards CELL_A11, UE transmit power decreases and the uplink SIR is approximate to the SIR Target. This feature does not need to be deactivated. Verification Procedure
3. 4. 5. l
----End
7.21 Configuring Admission Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020101 Admission Control.
Prerequisite
l l l
7-84
Dependency on Hardware None Dependency on Other Features None License

None
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 Activation Procedure 1. Run the BSC6900 MML command ADD UCELLCAC to enable code resource admission through setting the Dl handover credit and code reserved SF code resource admission parameter. To enable Power Resource Admission, perform the following steps: Run the BSC6900 MML command ADD UCELLALGOSWITCH or MOD UCELLALGOSWITCH to set the cell-oriented power resource admission switch to on and select an algorithm (Uplink/Downlink CAC algorithm switch). Run the BSC6900 MML command ADD UCELLCAC or MOD UCELLCAC to set power resource admission parameters. 3. To enable NodeB Credit Resource Admission, perform the following steps: Run the BSC6900 MML command SET UCACALGOSWITCH to open the NodeB-oriented CE admission switch (NODEB_CREDIT_CAC_SWITCH). Run the BSC6900 MML command ADD UCELLALGOSWITCH or MOD UCELLALGOSWITCH to open the cell-oriented NodeB credit resource admission switch (CRD_ADCTRL). Run the BSC6900 MML command ADD UCELLCAC or MOD UCELLCAC to set NodeB credit resource admission parameters (Ul handover credit reserved SF and Dl handover credit and code reserved SF). l Verification Procedure 1. Run the following BSC6900 MML commands to verify whether the activation is successful. LST UCELLALGOSWITCH LST UCACALGOSWITCH LST UCELLCAC l Deactivation Procedure 1. To disable Power Resource Admission, perform the following steps: Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the celloriented power resource admission switch (Uplink/Downlink CAC algorithm switch) to ALGORITHM_OFF. 2. To disable NodeB Credit Resource Admission, perform the following steps: Run the BSC6900 MML command SET UCACALGOSWITCH to close the NodeB-oriented CE admission switch (NODEB_CREDIT_CAC_SWITCH). Run the BSC6900 MML command MOD UCELLALGOSWITCH to close celloriented NodeB credit resource admission switch (CRD_ADCTRL). ----End
2.
7.22 Configuring Load Measurement

This section describes how to activate, verify, and deactivate the basic feature WRFD-020102 Load Measurement.
Prerequisite
Context
This feature is used to perform load measurement for the load control feature.
Procedure
l Activation Procedure 1. 2. 3. 4. l The measurement on RTWP, TCP, and non-HSPA power is always activated. Therefore, no action is required. Run the BSC6900 MML command ADD UCELLALGOSWITCH to enable the celloriented load measurement for HSDPA and HSUPA. Run the BSC6900 MML command ADD UCELLLDM or SET ULDM to configure UL/DL LDR trigger/release threshold and UL/DL OLC trigger/release threshold. Run the BSC6900 MML command SET ULDM to set the parameters related to filtering coefficient of load measurement, report interval, and smooth window length. Run the following BSC6900 commands to verify whether the activation is successful. LST UCELLALGOSWITCH LST UCELLLDM LST ULDM l Deactivation Procedure 1. The measurement on RTWP, TCP, and non-HSPA power is always activated. Therefore, it cannot be deactivated. Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the celloriented power resource admission switch (Uplink/Downlink CAC algorithm switch) to ALGORITHM_OFF. 2. ----End
Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the cell-oriented load measurement switch.
Example
//Activating Load Measurement ADD UCELLALGOSWITCH: CellId=100, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1&HSDPA_PBR_MEAS-1&HSUPA_PBR_MEAS-1&HSUPA _EDCH_RSEPS_MEAS-1; ADD 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 MOD UCELLALGOSWITCH: CellId=100, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-0&HSDPA_PBR_MEAS-0&HSUPA_PBR_MEAS-0&HSUPA _EDCH_RSEPS_MEAS-0;
7.23 Configuring Load Reshuffling

This section describes how to activate, verify, and deactivate the optional feature WRFD-020106 Load Reshuffling.
Prerequisite
Context
This feature provides load reshuffling policies to reduce the load in cells in the basic congestion state, so that the access success rate can be increased.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCELLALGOSWITCH and ADD UNODEBALGOPARA to enable the required LDR algorithms: UL_UU_LDR: UL UU load reshuffling algorithm DL_UU_LDR: DL UU load reshuffling algorithm CELL_CODE_LDR: Code reshuffling algorithm CELL_CREDIT_LDR:Credit reshuffling algorithm IUB_LDR: NodeB Iub reshuffling algorithm. NODEB_CREDIT_LDR: NodeB level credit reshuffling algorithm LCG_CREDIT_LDR: cell group level credit reshuffling algorithm 2.
Issue 03 (2010-09-20)
Set associated thresholds as follows:

Run the BSC6900 MML command ADD UCELLLDM to set power LDR thresholds (UL/DL LDR Trigger/release threshold and DL State Trans Hysteresis threshold). Run the BSC6900 MML command ADD UCELLLDR to set code LDR threshold (Cell LDR SF reserved threshold) and LDR actions. Run the BSC6900 MML command ADD UNODEBLDR to set the cell group/ NodeB LDR thresholds (Ul/DL LDR Credit SF reserved threshold). Run the BSC6900 MML command ADD UCELLLDR to set the local cell NodeB credit LDR thresholds (Ul/DL LDR Credit SF reserved threshold). 3. 4. Run the BSC6900 MML command SET ULDCPERIOD to set the length of LDR period (LDR period timer length). Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the functions used in the LDR actions. DRA_DCCC_SWITCH: DCCC algorithm DRA_IU_QOS_RENEG_SWITCH:Iu QoS renegotiation algorithm HO_INTER_RAT_CS_OUT_SWITCH: CS Inter-RAT handover HO_INTER_RAT_PS_OUT_SWITCH: PS inter-RAT handover CS_AMRC_SWITCH: AMRC. l Verification Procedure 1. Run the following BSC6900 MML commands to verify whether the activation is successful. LST UCELLALGOSWITCH LST UNODEBALGOPARA LST UCELLLDR LST UCELLLDM LST UNODEBLDR LST ULDCPERIOD LST UCORRMALGOSWITCH l Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH and MOD UNODEBALGOPARA to deactivate the required LDR algorithm switches for resources to 0: UL_UU_LDR: UL UU load reshuffling algorithm DL_UU_LDR: DL UU load reshuffling algorithm CELL_CODE_LDR: Code reshuffling algorithm CELL_CREDIT_LDR:Credit reshuffling algorithm IUB_LDR: NodeB Iub reshuffling algorithm NODEB_CREDIT_LDR: NodeB level credit reshuffling algorithm LCG_CREDIT_LDR: cell group level credit reshuffling algorithm ----End
Example
//Activating Load Reshuffling ADD UCELLALGOSWITCH: CellId=100,
7-88
Issue 03 (2010-09-20)
NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR1; ADD UNODEBALGOPARA: NodeBName="nodeb1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1&DRA_IU_QOS_RENEG_SWITCH-1,CsSwitch=CS_AMRC_SW ITCH-1, HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1&HO_I NTER_RAT_PS_OUT_SWITCH-1; //Deactivating Load Reshuffling MOD UCELLALGOSWITCH: CellId=100, NBMLdcAlgoSwitch=UL_UU_LDR-0&DL_UU_LDR-0&CELL_CODE_LDR-0&CELL_CREDIT_LDR0; MOD UNODEBALGOPARA: NodeBName="nodeb1", NodeBLdcAlgoSwitch=IUB_LDR-0&NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR-0;
7.24 Configuring Overload Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020107 Overload Control.
Prerequisite
Context
This feature provides load adjustment means to quickly lower the load in overloaded cells.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the required Uu OLC algorithm. UL_UU_OLC: UL UU overload congestion control algorithm DL_UU_OLC: DL UU overload congestion control algorithm 2. 3. 4. 5. l
Issue 03 (2010-09-20)
Run the BSC6900 MML command MOD UNODEBALGOPARA to enable the NodeB Iub overload congestion control algorithm. Run the BSC6900 MML command MOD UCELLLDM to set OLC-related thresholds (UL/DL OLC trigger threshold and UL/DL OLC release threshold). Run the BSC6900 MML command SET ULDCPERIOD to set the length of OLC period (OLC period timer length). Run the BSC6900 MML command ADD UCELLOLC to set the parameter related to OLC-related actions.
Verification Procedure
1.
Run the following BSC6900 MML commands to verify whether the activation is successful. LST UCELLALGOSWTICH LST UCELLLDM LST UNODEBALGOPARA LST ULDCPERIOD LST UCELLOLC
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the UU OLC algorithm: UL_UU_OLC: UL UU overload congestion control algorithm DL_UU_OLC: DL UU overload congestion control algorithm 2. Run the BSC6900 MML command MOD UNODEBALGOPARA to disable the NodeB Iub overload congestion control algorithm. UL_UU_OLC: UL UU overload congestion control algorithm DL_UU_OLC: DL UU overload congestion control algorithm
----End
Example
//Activating Overload Control MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_OLC-1&DL_UU_OLC-1; MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-1; //Deactivating Overload Control MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_OLC-0&DL_UU_OLC-0; MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-0;
7.25 Configuring Code Resource Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-020108 Code Resource Management.
Prerequisite
Context
This feature provides downlink code tree allocation and reshuffling. Through this, the code resources can be rationally allocated, thus increasing the utilization efficiency of the resources.
Procedure
l Activation Procedure
NOTE
The code allocation function is always activated. The activation procedure applies to only the code reshuffling function.
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the required LDR algorithm switches for resources(CELL_CODE_LDR(Code LDR Algorithm)). CELL_CODE_LDR: Code reshuffling algorithm. Run the BSC6900 MML command MOD UCELLLDR to set code LDR threshold (Cell LDR SF reserved threshold) and set code tree reshuffling as one of the DL LDR actions. Run the BSC6900 MML command SET ULDCPERIOD to set the length of LDR period (LDR period timer length). Run the following BSC6900 MML commands to verify whether the activation is successful. LST UCELLALGOSWTICH LST UCELLLDR LST ULDCPERIOD
2.
3. l
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the required LDR algorithm switches for resources to 0:
----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; //Deactivating Code Resource Management MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=CELL_CODE_LDR-0;
7.26 Configuring Shared Network Support in Connected Mode

This section describes how to activate, verify, and deactivate the basic feature WRFD-021301 Shared Network Support in Connected Mode.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features None
l l
License None Other Prerequisites The CN supports the shared network area (SNA) function.
Context
This feature enables the RAN and CN together to perform UE access restriction in specified location areas.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. 6. l 1. 2. 3. 4. 5. For the CS service, configure two SNAs (for example, SNA1 and SNA2) on the MSC. For the PS service, run the MML command ADD SNA on the SGSN to add SNA, SNA1, and SNA2. Run the BSC6900 MML command MOD UCELLACINFO to modify the RACs of CELL1 and CELL2. Set up a cell. For details, see the BSC6900 UMTS Initial Configuration Guide. Run the BSC6900 MML command to turn on the soft handover switch. Run the BSC6900 MML command to enable the SNA function. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu Interface Trace. The Iu Interface Trace dialog boxe is displayed. Keep UE1 and UE2 in idle mode in CELL1. Run the BSC6900 MML command to disable the SNA function. 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. 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. End the calling. UE1 and UE2 return to the idle mode in CELL1. Run the BSC6900 MML command to enable the SNA function. Add a mapping relation between IMSI and SNA1. 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
Verifying the SNA Function of the CS Service
6. 7. 8. 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 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. 2.
7-92
Run the MML command ADD SNA on the SGSN to add SNA information. Run the BSC6900 MML command to disable the SNA function.
3. 4.
Keep the UE in idle mode in CELL1. 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. 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. End the PS service of UE1. UE1 returns to the idle mode in CELL1. Run the BSC6900 MML command to enable the SNA function. 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. 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.
5.
6. 7. 8.
9.
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 Deactivation Procedure 1. ----End Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the SNA function.
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; MOD UCELLACINFO: CellId=2, LAC=2, SAC=0, CfgRacInd=REQUIRE, RAC=2; 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 SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1; ///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 SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; //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 MOD UCELLACINFO: CellId=1, LAC=1, SAC=0, CfgRacInd=REQUIRE, RAC=1; MOD UCELLACINFO: CellId=2, LAC=2, SAC=0, CfgRacInd=REQUIRE, RAC=2; SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1;
Issue 03 (2010-09-20)
7-93
//Adding SNA information on the SGSN ADD SNAA: BEGIMSI="460071104008338", ENDIMSI="460071104008338", PLMN="46002", SNAC=1; //Verifying the SNA function of the PS Service SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-1; //Deactivating the SNA function SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0;
7.27 Configuring Intra Node B Softer Handover

This section describes how to activate, verify, and deactivate the basic feature WRFD-020201 Intra Node B Softer Handover.
Prerequisite
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.
Procedure
l Activation Procedure 1. 2. 3. 4. l Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable soft handover. Run the BSC6900 MML command SET UHOCOMM to set Softer handover combination indicator switch to MAY or MUST. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter related to handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query whether the soft handover switch is enabled. Run the BSC6900 MML command LST UHOCOMM to query the combination status of softer handover.
7-94
3. 4.
Run the BSC6900 MML command LST UINTRAFREQNCELL to verify the configuration of the added intra-frequency neighboring cell. Run the BSC6900 MML command LST UINTRAFREQHO to verify the configuration of the parameters related to intra-frequency handover.
NOTE
You also can verify whether the softer handover function is enabled through signaling analysis of the link information of a UE.
Deactivation Procedure 1. Run the BSC6900 MML command SET UHOCOMM to set Softer handover combination indicator switch to MUST_NOT.
----End
Example
//Activating Intra Node B Softer Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1; 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 Node B Softer Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0;
7.28 Configuring Intra RNC Soft Handover

This section describes how to activate, verify, and deactivate the basic feature WRFD-020202 Intra RNC Soft Handover.
Prerequisite
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 Activation Procedure 1. 2. 3. l Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable soft handover. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter related to handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query whether the soft handover switch is enabled. Run the BSC6900 MML command LST UINTRAFREQNCELL to verify the configuration of the added intra-frequency neighboring cell. Run the BSC6900 MML command LST UINTRAFREQHO to verify the configuration of the parameters related to intra-frequency handover.
NOTE
Verification Procedure 1. 2. 3.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set Softer handover combination indicator to disable the soft handover.
----End
Example
//Activating Intra RNC Soft Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1; 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 RNC Soft Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0;
7.29 Configuring Inter RNC Soft Handover

This section describes how to activate, verify, and deactivate the optional feature WRFD-020203 Inter RNC Soft Handover.
Prerequisite
l l l
7-96

None l 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 Activation Procedure 1. 2. 3. 4. l Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable soft handover. Run the BSC6900 MML command ADD UNRNC or MOD UNRNC to enable crossIur soft handover. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter related to handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query whether the soft handover switch is enabled. Run the BSC6900 MML command LST UNRNC to query the status of cross-Iur soft handover. Run the BSC6900 MML command LST UINTRAFREQNCELL to verify the configuration of the added intra-frequency neighboring cell. Run the BSC6900 MML command LST UINTRAFREQHO to verify the configuration of the parameters related to intra-frequency handover.
NOTE
Deactivation Procedure 1. Run the BSC6900 MML command MOD UNRNC to disable the cross-Iur soft handover.
----End
Example
//Activating Inter RNC Soft Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1; MOD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1;
Issue 03 (2010-09-20)
7-97
ADD UINTRAFREQNCELL: RNCId=1, CellId=221, NCellRncId=2, NCellId=222, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Deactivating Inter RNC Soft Handover MOD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-0&HSPA_SHO_SWITCH-0&NON_HSPA_SHO_SWITCH-0;
7.30 Configuring Intra Frequency Hard Handover

This section describes how to activate, verify, and deactivate the optional feature WRFD-020301 Intra Frequency Hard Handover.
Prerequisite
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 Activation Procedure 1. 2. 3. Run the RNC MML command SET UCORRMALGOSWITCH to select HO_INTRA_FREQ_HARD_HO_SWITCH from the HandOver switch list. Run the RNC MML command ADD UINTRAFREQNCELL to add an intrafrequency or inter-RNC neighboring cell. If cross-Iur hard handover is required, add the neighboring RNC and neighboring RNC cell. Run the RNC MML command ADD UNRNC to add a neighboring RNC. Run the RNC MML command ADD UEXT3GCELL to add a neighboring RNC cell. Run the RNC MML command ADD UINTRAFREQNCELL to set the neighboring cell relations. Run the RNC MML command SET UINTRAFREQHO to set the parameter related to handover. Run the RNC MML command LST UCORRMALGOSWITCH to query whether the intra-frequency hard handover switch is enabled. Run the RNC MML command LST UNRNC to query the status of cross-Iur intrafrequency hard handover. Run the RNC MML command LST UINTRAFREQNCELL to verify the configuration of the added intra-frequency neighboring cell. Run the RNC MML command LST UINTRAFREQHO to verify the configuration of the parameters related to intra-frequency handover.
4. l
7-98
Deactivation Procedure 1. Run the RNC MML command SET UCORRMALGOSWITCH 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_SOFT_HO_SWITCH-1; ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=1, NCellId=211, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; 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; ADD UEXT3GCELL: NRncId=2, CellId=311, CellHostType=SINGLE_HOST, CellName="311", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1, UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700, TxDiversityInd=FALSE, LAC=H'2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE; ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=2, NCellId=311, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Deactivating Intra Frequency Hard Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0;
7.31 Configuring Intra RNC Cell Update

This section describes how to activate, verify, and deactivate the basic feature WRFD-010801 Intra RNC Cell Update.
Prerequisite
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 Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented PS BE service state transition switch.
Issue 03 (2010-09-20)
2.
Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the parameters BE DCH to FACH Transition Timer[s] and BE FACH or E_FACH to PCH Transition Timer[s] to 30s and 60s respectively. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. Run the BSC6900 MML command SET UCONNMODETIMER to set the periodic cell update timer to 5 minutes. Set CELL1 and CELL2 of the RNC as intra-frequency neighboring cells. For details, see the BSC6900 UMTS Initial Configuration Guide. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then, click Submit. Keep the UE in idle mode in CELL1. On the HLR, set the PS service type to background or interactive. Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be displayed in trace data, and the value of the rrc-stateindicator IE should be CELL_DCH. 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. 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. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Keep the UE in idle mode in CELL1. On the HLR, set the PS service type to background or interactive. Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be displayed in trace data, and the value of the rrc-stateindicator IE should be CELL_DCH. 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. 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. 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. Run the MML command SET UUESTATETRANSTIMER to set the parameter BE FACH or E_FACH to PCH Transition Timer[s] to 65535.
3. 4. 5. l
Verifying Cell Update Triggered by Cell Reselection 1. 2. 3. 4. 5.
6.
7.
Verifying Cell Update Triggered by Uplink Data Transmission 1. 2. 3. 4.
5.
6.
7.
Verifying Periodic Cell Update 1.
7-100
For example,
SET UUESTATETRANSTIMER: BeF2PStateTransTimer=65535;
2. 3. 4. 5.
Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Keep the UE in idle mode in CELL1. On the HLR, set the PS service type to background or interactive. Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be displayed in trace data, and the value of the rrc-stateindicator IE should be CELL_DCH. 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. 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. None
6.
7.
----End
Example
//Activating intra-RNC cell update SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: BeD2FStateTransTimer=30, BeF2PStateTransTimer=60; SET UPSINACTTIMER: PsInactTmrForInt=0, PsInactTmrForBac=0; SET UCONNMODETIMER: T305=D5;
7.32 Configuring Inter RNC Cell Update

This section describes how to activate, verify, and deactivate the basic feature WRFD-010802 Inter RNC Cell Update.
Prerequisite
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 Activation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented PS BE service state transition switch. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the parameters BE DCH to FACH Transition Timer[s]. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. Configure intra-frequency neighboring cells. For details, see the BSC6900 UMTS Initial Configuration Guide. Run the BSC6900 MML command MOD UNRNC to enable the setup of command channels on the Iur interface.
NOTE
Run the command on both RNC1 and RNC2.
Verifying Cell Update Triggered by Cell Reselection 1. 2. 3. 4. 5. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then, click Submit. Keep the UE in idle mode in CELL1. On the HLR, set the PS service type to background or interactive. Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be displayed in trace data, and the value of the rrc-stateindicator IE should be CELL_DCH. 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. Cause the UE to perform cell reselection from CELL1 to CELL2 so as to trigger cell update. The UE should send the RRC_CELL_UPDATE message to RNC2, with the cell update cause of cell reselection, and RNC1 should send the RRC_CELL_UPDATE_CONFIRM message to the UE. This feature does not need to be deactivated.
6.
7.
----End
Example
//Activating inter-RNC cell update SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: BeD2FStateTransTimer=30; SET UPSINACTTIMER: PsInactTmrForInt=0, PsInactTmrForBac=0; MOD UNRNC: NRncId=2, SuppIurCch=YES; MOD UNRNC: NRncId=1, SuppIurCch=YES;
7-102
Issue 03 (2010-09-20)
7.33 Configuring Intra RNC URA Update

This section describes how to activate, verify, and deactivate the basic feature WRFD-010901 Intra RNC URA Update.
Prerequisite
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 Activation Procedure 1. Run the BSC6900 MML command MOD UCELLACINFO to set CELL1 and CELL2 as the intra-frequency neighboring cells that belong to the same location area, route area, and service area. Run the BSC6900 MML command ADD UCELLURA to configure CELL1 and CELL2 to make them belong to different URAs. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented PS BE service state transition switch. Run the BSC6900 MML command SET UUESTATETRANSTIMER 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. Run the BSC6900 MML command SET UUESTATETRANS to set the parameter Cell Reselection Counter Threshold to 1. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. Run the BSC6900 MML command SET UCONNMODETIMER to set the periodic cell update timer to 5 minutes. Configure intra-frequency neighboring cells. For details, see the BSC6900 UMTS Initial Configuration Guide. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then, click Submit.
2. 3. 4.
5. 6. 7. 8. l
Verifying URA Update Triggered by URA Reselection 1. 2.
Issue 03 (2010-09-20)
3. 4. 5.
Keep the UE in idle mode in CELL1. On the HLR, set the PS service type to background or interactive. Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be displayed in trace data, and the value of the rrc-stateindicator IE should be CELL_DCH. 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. 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 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. 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 sent the RRC_URA_UPDATE_CONFIRM message to the UE. This feature does not need to be deactivated.
6.
7.
8.
9.
Verifying Periodic URA Update 1.
----End
Example
//Activating intra-RNC URA update MOD UCELLACINFO: CellId=111, LAC=1, SAC=1, CfgRacInd=REQUIRE, RAC=1; MOD UCELLACINFO: CellId=121, LAC=1, SAC=1, CfgRacInd=REQUIRE, RAC=1; ADD UCELLURA: CellId=111, URAId=0; ADD UCELLURA: CellId=121, URAId=1; SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: CellReSelectTimer=60, BeD2FStateTransTimer=10, BeF2PStateTransTimer=10; SET UUESTATETRANS: CellReSelectCounter=1; SET UPSINACTTIMER: PsInactTmrForInt=0, PsInactTmrForBac=0; SET UCONNMODETIMER: T305=D5;
7.34 Configuring Inter RNC URA Update

This section describes how to activate, verify, and deactivate the basic feature WRFD-010902 Inter RNC URA Update.
7-104
Issue 03 (2010-09-20)
Prerequisite
Context
Inter-RNC URA update means URA update between RNCs.
Procedure
l Activation Procedure 1. 2. Configure the Iur interface. For details, see the BSC6900 UMTS Initial Configuration Guide. Run the BSC6900 MML command ADD UCELLURA to configure CELL1 and CELL2 to make them belong to different URAs.
NOTE
Cell1 belongs to RNC_1, Cell2 belongs to RNC_2.
3.
On the RNC1 side, run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented PS BE service state transition switch. Run the BSC6900 MML command SET UUESTATETRANSTIMER 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. Run the BSC6900 MML command SET UUESTATETRANS to set the parameter Cell Reselection Counter Threshold to 1. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. Configure intra-frequency neighboring cells. For details, see the BSC6900 UMTS Initial Configuration Guide. Run the BSC6900 MML command MOD UNRNC to enable the setup of command channels on the Iur interface. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then, click Submit. Keep the UE in idle mode in CELL1. On the HLR, set the PS service type to background or interactive. Establish an R99 PS service on the UE. The RRC_RB_SETUP message should be displayed in trace data, and the value of the rrc-stateindicator IE should be CELL_DCH.
4.
5. 6. 7. 8. l
Verification Procedure 1. 2. 3. 4. 5.
Issue 03 (2010-09-20)
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. 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 the UE perform another cell reselection after the Cell Reselection Timer[s] expires. Search for the last RRC_CELL_UPDATE_CONFIRM message in Uu trace data. The value of rrc-stateindicator IE should be URA_PCH. 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 URA reselection, and the RNC should sent the RRC_URA_UPDATE_CONFIRM message to the UE. This feature does not need to be deactivated.
7.
8.
9.
----End
Example
//Activating inter-RNC URA update ADD UCELLURA: CellId=111, URAId=0; ADD UCELLURA: CellId=121, URAId=1; SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: CellReSelectTimer=60, BeD2FStateTransTimer=10, BeF2PStateTransTimer=10; SET UUESTATETRANS: CellReSelectCounter=1; SET UPSINACTTIMER: PsInactTmrForInt=0, PsInactTmrForBac=0; MOD UNRNC: NRncId=2, SuppIurCch=YES; MOD UNRNC: NRncId=1, SuppIurCch=YES;
7.35 Configuring Direct Signaling Connection Reestablishment (DSCR)

This section describes how to activate, verify, and deactivate the basic feature WRFD-021400 Direct Signaling Connection Re-establishment (DSCR).
Prerequisite
Context
During the DSCR procedure, the RNC takes the initiative to release the RRC connection associated with non-real-time RABs and then immediately requests the UE to re-establish the
RRC connection and set up the service. The RRC connection re-establishment procedure is initiated with an RRC CONNECTION RELEASE message with the cause 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 can ensure uninterrupted PS service provision.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UNRNC to set Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_DSCR.
NOTE
On the BSC6900, Handover Type for PS BE Traffic adopts the default value, CORRM_SRNSR_PSBE_RELOC. Normally, you need to change the setting.
2. l
For DSCR at the presence of the Iur interface, run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the switches related to relocation. Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 7-6 and Figure 7-7. Figure 7-6 Message Tracing on the Uu Interface
Issue 03 (2010-09-20)
7-107
Figure 7-7 RRC CONNECTION RELEASE
2. 3.
Establish a PS BE service on the UE. Perform a soft handover by adding a cell under the DRNC and then removing the source cell. Observe the RRC_RRC_CONN_REL message in the data traced on the Uu interface. Check releaseCause IE in the rrcConnectionRelease IE. If the cause is Directed Signaling Connection re-establishment, you can infer that this feature has been activated. Run the BSC6900 MML command MOD UNRNC to 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; SET UCORRMALGOSWITCH: 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 //Deactivating Direct Signaling Connection Re-establishment (DSCR). MOD UNRNC: NRncId=20, PsBeProcType= CORRM_SRNSR_PSBE_RELOC;
7.36 Configuring Base Station Clock(NodeB)

This section describes how to activate, verify, and deactivate the basic feature MRFD-210501 NodeB Clock on the UMTS side.
Prerequisite
l
7-108
Dependency on Hardware
Ensure that a clock link is available before configuring the LINE clock source. Ensure that the GPS card is configured before configuring the GPS clock source. Ensure that the USCU is configured before configuring the BITS clock source. l l Dependency on Other Features None License None
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 l l Synchronization with the Iub/Abis clock (default mode) Synchronization with GPS Synchronization with the BITS clock
Procedure
l Activation Procedure Synchronization with the Iub clock (default mode) 1. Run the NodeB MML command SET CLKMODE to set the LINE clock source for the NodeB. Run the NodeB MML command SET CLKMODE to set the GPS clock source for the NodeB. Run the NodeB MML command SET CLKMODE to set the BITSclock source for the NodeB. Run the NodeB MML command LST CLKMODE to query the current configuration of the system clock. The expected result: If... The clock information corresponds to the clock type configured The clock information is inconsistent with the configuration l Deactivation Procedure This feature does not need to be deactivated. Then... The configuration is successful. The configuration is unsuccessful.
Synchronization with the GPS clock 1.
Synchronization with the BITS clock 1. l
----End
Example
//Configure the LINE clock source for the NodeB. SET CLKMODE: MODE=MANUAL, CLKSRC= LINE; //Configure the GPS clock source for the NodeB. SET CLKMODE: MODE=MANUAL, CLKSRC= GPS; //Configure the BITS clock source for the NodeB. SET CLKMODE: MODE=MANUAL, CLKSRC= BITS;
7.37 Configuring ATM Transmission Introduction Package

This section describes how to activate, verify, and deactivate the basic feature WRFD-050301 ATM Transmission Introduction Package.
Context
ATM transmission introduction package covers the following sub-features: l l l l l l l l ATM over E1T1 on Iub interface ATM over channelized STM-1/OC-3 on Iub interface ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface IMA for E1T1 or channelized STM-1/OC-3 on Iub interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Permanent AAL5 Connections for Control Plane Traffic Call Admission Based on Used AAL2 Path Bandwidth CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
Procedure
l Activation Procedure For configuring ATM over E1T1 on Iub interface, see WRFD-05030101 ATM over E1T1 on Iub Interface. For configuring ATM over channelized STM-1/OC-3 on Iub interface, see WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub Interface. For configuring ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface, see WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface. For configuring IMA for E1T1 or channelized STM-1/OC-3 on Iub interface, see WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub Interface. For configuring dynamic AAL2 connections in Iub/IuCS/Iur Interface, see WRFD-05030104 Dynamic AAL2 Connections in Iub or IuCS or Iur Interface. For configuring permanent AAL5 Connections for Control Plane Traffic, see WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic. For configuring call Admission Based on Used AAL2 path bandwidth, see WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth. For configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes, see WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes. l
7-110
None l Deactivation Procedure None ----End
7.38 Configuring Dynamic AAL2 Connections in Iub/IuCS/ Iur Interface

This section describes how to activate and verify the basic feature WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050301 ATM Transmission Introduction Package. l l License None Other Prerequisites The RAN network is based on ATM transmission.
Context
In ATM transmission mode, AAL2 paths are used to carry the user plan data for Iub/Iur/Iu-CS interface. AAL2 paths are provided according to traffic classes (conversational, streaming, interactive, and background) and bearer types (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 Activation Procedure 1. Run the BSC6900 MML command ADD ADJNODE 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, the parameter Is Root Node is set to YES; otherwise, Is Root Node is set to NO.
NOTE
For an adjacent node on the Iur or Iu-CS interface, its upper-level hub node must be NNI_AAL2SWITCH; for an adjacent node on the Iub interface, its upper-level hub node must be UNI_AAL2SWITCH.
2.
Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path. The parameters CARRYVPI and CARRYVCI must be consistent with those of the peer end.
l
Issue 03 (2010-09-20)
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 Iub/Iu-CS ATM transmission scenario, make speech and data services. If the service access normally, you can infer that the AAL2 connections set up for Iub/Iu-CS successfully. Optional: In Iur ATM transmission scenario, make a cross-Iur handover. If the handover is succeed, you can infer that the AAL2 connections set up for Iur successfully.
3.
Deactivation Procedure This feature need not be deactivated.
----End
7.39 Configuring Permanent AAL5 Connections for Control Plane Traffic

This section describes how to activate, verify, and deactivate the basic feature WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License None Other Prerequisites 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 the section Configuring the Equipment Data of the BSC6900 UMTS Initial Configuration Guide.
Context
In ATM RAN, AAL5 connections are used to bear Iub/Iur/ Iu signaling and Iub OAM traffic. 3GPP specified UNI-SAAL is used for Iub control plane connections, and NNI-SAAL is used for Iur and Iu control plane connections. The AAL5 connections for Iub, Iur, and Iu interfaces are all set up by configuring Signaling ATM adaptation layer (SAAL) links.
Procedure
7-112
Issue 03 (2010-09-20)
1.
Run the BSC6900 MML command ADD SAALLNK 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. Run the BSC6900 MML command DSP SAALLNK to query the status of the SAAL link.
----End
7.40 Configuring Call Admission Based on Used AAL2 Path Bandwidth

This section describes how to activate and verify the basic feature WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth.
Context
With the Call Admission Based on Used AAL2 Path Bandwidth (AAL2 CAC) feature, some admission requests are accepted or rejected selectively. This feature maximizes the usage of transmission resources in addition to guaranteeing the QoS.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD ATMTRF to set the parameter Service type to NRTVBR, the parameter Rate unit to KBIT/S, and the parameter Peak cell rate to 100. Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path. Run the PS interactive service. If the subscriber rate is 64 kbit/s, you can infer that the UE gets access to the network. Run the BSC6900 MML command DSP AAL2PATH to check that the used bandwidth of the path is 75 kbit/s. Run the PS interactive service. If the subscriber rate is 128 kbit/s, you can infer that the UE fails to access the network.
2. l 1.
2. l
Deactivation Procedure None.
----End
7.41 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".
Prerequisite
Context
Huawei RAN supports four types of ATM service: l l l l Constant Bit Rate (CBR) Real time Variable Bit Rate (rt-VBR) Non-real time Variable Bit Rate (nrt-VBR) Unspecified Bit Rate (UBR)
For details, see the ATM forum specification Traffic Management 4.1. The traffic volume on the VCC depends on the parameters (SCR, PCR, and CDVT) associated with each type of ATM service. These four types of service provide differentiated services at the ATM layer. Two of them are used for R99 services and the other two are used for HSDPA/HSUPA services. Generally, rtVBR 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.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command ADD ATMTRF 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. Run the BSC6900 MML command RMV ATMTRF to delete an ATM traffic record. To delete more ATM traffic records, run this command repeatedly.
Verify Procedure 1.
----End
Example
//Activating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes ADD ATMTRF: TRFX=105, ST=CBR, UT=CELL/S, PCR=1000; //Verfying 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;
7-114
Issue 03 (2010-09-20)
7.42 Configuring F5
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110 F5.
Prerequisite
l l l l l Dependency on Hardware None Dependency on Other Features None License None The basic information about the BSC6900 is configured. For details, see the Configuring the Basic Data. The SAALLNK, AAL2PATH, or IPOAPVC link exists.
Context
This feature supports: l l 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
l Activation Procedure 1. 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. 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. 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_IN_PROESS, and PM Active Fail Alarm is Normal. l
Issue 03 (2010-09-20)
2.
Verify Procedure 1.
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. 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.
2.
----End
Example
//Activating F5 ACT VCLCC: LNKT=SAALLNK, ACT VCLPM: LNKT=SAALLNK, //Verfying F5 DSP VCLCC: LNKT=SAALLNK, DSP VCLPM: LNKT=SAALLNK, //Deactivating F5 DEA VCLCC: LNKT=SAALLNK, DEA VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0, VCLTYPE=CC; SRN=3, SN=2, SAALLNKN=0; SRN=3, SN=2, SAALLNKN=0; SRN=3, SN=2, SAALLNKN=0; SRN=3, SN=2, SAALLNKN=0; SRN=3, SN=2, SAALLNKN=0;
7.43 Configuring UBR+ ATM QoS Class

This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305 UBR+ ATM QoS Class".
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License None 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
7-116
1. l
Run the MML command ADD ATMTRF 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. Run the MML command RMV ATMTRF to delete an ATM traffic record of the UBR + class. To delete more ATM traffic records, run this command repeatedly.
Verify Procedure 1.
----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;
7.44 Configuring Flow Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-040100 Flow Control.
Prerequisite
Context
Flow control refers to the internal flow control of the Radio Network Controller (RNC) by regulating the input transmission rate, which is called feedback flow control mechanism. The flow control procedure is as follows: l l l l l Flow Control For Boards Load Sharing in Control Plane Load Sharing in User Plane RRC Shaping and Queuing Backpressure based on MPU Load
Procedure
l
Issue 03 (2010-09-20)
Activating Flow Control For Boards 1. 2. Run the BSC6900 MML command SET FCSW to enable the flow control switch and the switch of the corresponding flow control item. Run the BSC6900 MML command SET FCCPUTHD to configure the CPU usage threshold for each flow control item.
NOTE
l Although the flow control switch is ON, flow control is enabled only when the CPU usage reaches the specified threshold. l The restrictions on CPU usage thresholds are as follows: 100 Critical threshold Control threshold Restore threshold l The control priority of a critical threshold is higher than that of any other threshold. The control mechanism of other thresholds can work only when the CPU usage does not reach the critical threshold. l The flow control based on message block usage and that based on CPU usage are independent from each other. The lesser allowed flow is the flow allowed in the system.
3.
Run the BSC6900 MML command SET FCMSGQTHD to configure the message block usage threshold for each flow control item.
NOTE
l Although the flow control switch is ON, flow control is enabled only when the message block usage reaches the specified threshold. l The restrictions on message block usage thresholds are as follows: 100 Critical threshold Control threshold Restore threshold l The control priority of a critical threshold is higher than that of any other threshold. The control mechanism of other thresholds can work only when the message block usage does not reach the critical threshold. l The flow control based on message block usage and that based on CPU usage are independent from each other. The lesser allowed flow is the flow allowed in the system.
Activating Load Sharing in Control Plane 1. Run the BSC6900 MML command SET URRCTRLSWITCH to set the parameter Process switch to RNC_SHARE_SWITCH to enable the switch of the traffic load sharing function. (Optional) Run the BSC6900 MML command SET UCTRLPLNSHAREPARA to set the parameter Control Plane Sharing Out Threshold to 40 to trigger the load sharing function. Run the BSC6900 MML command SET UUSERPLNSHAREPARA to set the parameter Percentage of User Plane Sharing Out Threshold to 90 to trigger the load sharing function. Run the BSC6900 MML command SET UCACALGOSWITCH to set the parameter RsvdPara1 to RSVDBIT14-1 to trigger RRC Shaping and Queuing function. Run the BSC6900 MML command SET URRCTRLSWITCH to set the parameter RsvdPara1 to RSVDBIT1_BIT19-1 to trigger the Backpressure based on MPU Load function.
2.
Activating Load Sharing in User Plane 1.
Activating RRC Shaping and Queuing 1.
Activating Backpressure based on MPU Load 1.
7-118

NOTE
Verification Procedure Verification Flow Control For Boards 1. 2. 3. Run the BSC6900 MML commands LST FCSW to query the settings of switches and flow control thresholds. Run the BSC6900 MML commands LST FCCPUTHD to query the CPU usage thresholds. Run the BSC6900 MML commands LST FCMSGQTHD to query the message block usage of thresholds. Start the CPU/DSP usage monitoring on the WebLMT to query the CPU usage of each subsystem. If the CPU usage of each subsystem is almost equal, the function of the Load Sharing is activated. Run the BSC6900 MML commands LST UCACALGOSWITCH to query the settings of switch. Run the BSC6900 MML commands LST URRCTRLSWITCH to query the settings of switch.
Verification Load Sharing 1.
Verification RRC Shaping and Queuing 1.
Verification Backpressure based on MPU Load 1. l
Deactivation Procedure Deactivation Flow Control For Boards 1. 1. Run the BSC6900 MML command SET FCSW to disable the flow control switch. Run the BSC6900 MML command SET URRCTRLSWITCH to disable the switch of the load sharing function. Does not need to be deactivated Run the BSC6900 MML command SET UCACALGOSWITCH to set the parameter RsvdPara1 to RSVDBIT14-0 to disable the switch. Run the BSC6900 MML command SET URRCTRLSWITCH to set the parameter RsvdPara1 to RSVDBIT1_BIT19-0 to disable the switch. Deactivation Load Sharing in Control Plane
Deactivation Load Sharing in User Plane 1. 1. Deactivation RRC Shaping and Queuing
Deactivation Backpressure based on MPU Load 1. ----End
Example
/*Activating Flow Control For Boards*/ //Enable the flow control switches of the XPU-type boards: SET FCSW: BRDCLASS=XPU, FCSW=ON, PRINTSW=ON, TRACESW=ON, PMSW=ON, LOGSW=ON; //Set the CPU usage thresholds for the DPU-type boards: SET FCCPUTHD:
Issue 03 (2010-09-20)
7-119
BRDCLASS=DPU, SMWINDOW=6, FDWINDOW=2, CTHD=95, PRINTCTHD=60, PRINTRTHD=50, TRACECTHD=60, TRACERTHD=50, LOGCTHD=60, LOGRTHD=50; //Set the message block usage thresholds for the DPU-type boards: SET FCMSGQTHD: BRDCLASS=DPU, SMWINDOW=9, CTHD=95, PRINTCTHD=60, PRINTRTHD=50, TRACECTHD=60, TRACERTHD=50, LOGCTHD=60, LOGRTHD=50; /*Activating Load Sharing in Control Plane*/ SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-1; SET UCTRLPLNSHAREPARA: CtrlPlnSharingOutThd=40; /*Activating Load Sharing in User Plane*/ SET UUSERPLNSHAREPARA: UserPlnSharingOutThd=90; /*Activating RRC Shaping and Queuing*/ SET UCACALGOSWITCH:RsvdPara1=RSVDBIT14-1; /*Activating Backpressure based on MPU Load*/ SET URRCTRLSWITCH:RsvdPara1=RSVDBIT1_BIT19-1; //Verification Flow Control For Boards LST FCSW: LstFormat=VERTICAL; LST FCCPUTHD: LstFormat=VERTICAL; LST FCMSGQTHD: LstFormat=VERTICAL; /*Verification RRC Shaping and Queuing*/ LST UCACALGOSWITCH: LstFormat=VERTICAL; /*Verification Backpressure based on MPU Load*/ LST URRCTRLSWITCH: LstFormat=VERTICAL; //Deactivation Flow Control of the XPU-type boards SET FCSW: BRDCLASS=XPU, FCSW=OFF; /*Deactivation Load Sharing in Control Plane*/ SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-0; /*Deactivation RRC Shaping and Queuing*/ SET UCACALGOSWITCH: RsvdPara1=RSVDBIT14-0; /*Deactivation Backpressure based on MPU Load*/ SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT19-0;
7.45 Configuring BOOTP

This section describes how to activate, verify, and deactivate the basic feature WRFD-031100 BOOTP. In ATM transport mode, the NodeB can automatically set up the OM channel with the BSC6900 by using the BOOTSTRAP Protocol (BOOTP) function.
Prerequisite
l Dependency on Hardware The transmission equipment is in the connected state. BOOTP applies only to ATM networking scenarios. l l
7-120
Dependency on Other Features None License

None
Context
If the NodeB does not have a configuration file or its configuration file is incorrect, the BOOTP feature enables the NodeB to set up the IPoA channel so that the M2000 can maintain the NodeB remotely.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD DEVIP 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. Run the BSC6900 MML command ADD IPOAPVC to add the IPoA PVC for bearing the OM channel. Run the BSC6900 MML command ADD UNODEBIP to add the IP address for the OM channel of the NodeB.
2. 3. l
Verification Procedure If the BOOTP configurations at the BSC6900 are completed but no configuration file is downloaded to 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
//Run the following command to add the logical IP address for the interface board. ADD DEVIP: SRN=0, SN=14, DEVTYPE=IPOA_CLIENT_IP, IPADDR="131.131.131.132", MASK="255.255.255.0"; //Run the following command to add the IPoA PVC. ADD IPOAPVC: IPADDR="131.131.131.132", PEERIPADDR="131.131.131.131", CARRYT=IMA, CARRYIMAGRPN=0, CARRYVPI=83, CARRYVCI=80, TXTRFX=100; //Run the following command to add the IP address for the OM channel of the NodeB. ADD UNODEBIP: NODEBID=0, NBTRANTP=ATMTRANS_IP, NBATMOAMIP="131.131.131.131", NBATMOAMMASK="255.255.255.0", ATMSRN=0, ATMSN=14;
7.46 Configuring NodeB Self-discovery Based on IP Mode

This section describes how to activate, verify, and deactivate the basic feature WRFD-031101 NodeB Self-discovery Based on IP Mode.
Prerequisite
l Dependency on Hardware The transmission equipment is in the connected state. The DHCP applies to the IP network.
The DHCP+AACP applies to only BTS3900, BTS3900A, and DBS3900. l l l l Dependency on Other Features None License None The transmission equipment is in the connected state. This feature has no requirement for other NEs, no dependence on other features, and is not restricted by the license.
Context
l l If the NodeB does not have a configuration file or its configuration file is incorrect, the DHCP feature enables the NodeB to set up the OM channel for its remote maintenance. No configuration is required on the NodeB side. If Hub NodeB networking is used, relevant configurations are required on the Hub NodeB side. Relevant configurations are required at the DHCP server, which is BSC6900 or M2000. The following example describes the configurations at the BSC6900.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command ADD UNODEBESN to add the NodeB ESN in response to the DHCP request reported by the NodeB. Run the BSC6900 MML command ADD UNODEBIP to add the IP address for the OM of the NodeB. In the case that DHCP response is made, the BSC6900 will send the IP address to the NodeB. Optional: In the case that Hub NodeB networking is used, run the NodeB MML command ADD DHCPSVRIP to add the IP address for the DHCP server. Then the lower-level node can obtain the IP address through DHCP.
3.
Verification Procedure If the following conditions are met: No configuration file is downloaded to the NodeB. The DHCP configurations are completed at the BSC6900. If Hub NodeB networking is used, the IP address for the DHCP server is configured at the Hub NodeB. The NodeB can be maintained on the M2000. It indicates that the NodeB has successfully set up the OM channel by using this feature.
----End
Example
//Run the following command to add the NodeB ESN. ADD UNODEBESN: NODEBID=0, NBLB1="020GKV1082000126", USENBLB2=Disable, NODEBPT=ETH/TRUNK, PTIP="131.131.131.132", PTIPMASK="255.255.255.0"; //Run the following command to add the IP address for the OM of the NodeB.
7-122
Issue 03 (2010-09-20)
ADD UNODEBIP: NODEBID=0, NBTRANTP=IPTRANS_IP, NBIPOAMIP="131.131.131.131", NBIPOAMMASK="255.255.255.0", IPSRN=0, IPSN=18, IPLOGPORTFLAG=NO; //Run the following command to add the IP address for the DHCP server. ADD DHCPSVRIP: DHCPSVRIP="13.13.13.13";
7.47 Configuring Intelligently Out of Service

This section describes how to activate, verify, and deactivate the basic feature WRFD-031000 Intelligently Out of Service.
Prerequisite
Context
Insufficient battery voltage, Node B reset, or cell blocking may lead to service disruption. When the preceding problems occur, this feature enables the Node B to automatically reduce the pilot transmit power and hand over the UE to other cells, thus preventing service disruption.
Procedure
l Activation Procedure 1. l Run the NodeB MML command SET SMTHPWRSWTCH. In this step, set Smooth Power Change Function Switch to OPEN. Run the NodeB MML command LST SMTHPWRSWTCH. In this step, check whether Smooth Power Change Function Switch is set to OPEN.
----End
7.48 Configuring OCNS

This section describes how to activate, verify, and deactivate the basic feature WRFD-031200 OCNS (Orthogonal Channel Noise Simulator).
Prerequisite
l l
Issue 03 (2010-09-20)

None l License None
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 Activation Procedure 1. l Run the NodeB MML command STR DLSIM to start downlink load simulation. In this step, set Local Cell ID and Load Ratio (%). 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. Run the NodeB MML command STP DLSIM to stop the downlink load simulation. In this step, specify Local Cell ID.
----End
Example
// Activation Procedure: To start downlink load simulation of a cell, do as follows: STR DLSIM: LOCELL=1, LR=80; // Verification Procedure: To check the simulated load rate, do as follows: DSP DLSIM: LOCELL=1; // Deactivation Procedure: To stop downlink load simulation of the cell, do as follows: STP DLSIM: LOCELL=1;
7.49 Configuring Power Off the Equipment Level by Level

This section describes how to activate, verify, and deactivate the basic feature WRFD-031400 Power Off the Equipment Level by Level.
Prerequisite
l The network is ready. Table 7-3 describes the requirements on NEs. Table 7-3 Requirements on NEs NE CN
7-124
Requirements None.
NE RNC NodeB
Requirements None. NodeB must be configured with APM30/APM100/APM200 (the type of outdoor NodeB cabinet for AC input) to support the function. None.
UE
Power off the equipment level by level is a basic feature of the UMTS and has no license control items.
Context
After a mains failure, the operator can power off the equipment level by level by setting different DC voltage thresholds to implement intelligent shutdown of RF modules and sites. The battery capacity is sufficient for the system to work for a longer period of time.
Procedure
l Activation Procedure 1. l Run the NodeB MML command SET SDPA to set the parameters Load Shutdown Flag to ON, and set Shutdown Voltage as required. Run the NodeB MML command LST SDPA to query the settings of the parameters Load Shutdown Flag and Shutdown Voltage. Run the NodeB MML command SET SDPA to set the parameters Load Shutdown Flag to OFF.
----End
7.50 Configuring Connection with TMA(NodeB)

This section describes how to activate, verify, and deactivate the basic feature MRFD-210601 Connection with TMA (Tower Mounted Amplifier) on the UMTS side.
Prerequisite
l l l l Dependency on Hardware The base station is connected to the Antenna Line Device (ALD) normally. Dependency on Other Features None License None 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. It is recommended that you query the gain range supported by the STMA using theDSP TMAFUN command before adjusting the gain.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. l l Run the NodeB MML command SET ALDPWRSW to set PWRSW of the TMA to ON. Run the NodeB MML command SCN ALD to scan the ESN of the ALD. Run the NodeB MML command ADD ALD to add a TMA. Optional: If the device supports TMA gain, run the NodeB MML command SET TMAGAIN to set the TMA gain. Run the NodeB MML command SET RXATTEN to set the attenuation of the RX channel. Run the NodeB MML command LST TMAGAIN to query the TMA gain.
Verification Procedure 1. Deactivation Procedure This feature does not need to be deactivated.
----End
7.51 Configuring Remote Electrical Tilt(UMTS)

This section describes how to activate, verify, and deactivate the basic feature MRFD-210602 Remote Electrical Tilt on the UMTS side.
Prerequisite
l Dependency on Hardware The base station is connected to the RET antenna normally. The Remote Control Unit (RCU) matches the antenna, and the RCU is loaded with the configuration data file corresponding to this antenna. The RCU is loaded with basic software for its normal operation. l l Dependency on Other Features None License None
Context
After an antenna is installed, the antenna tilt needs to be adjusted to optimize the network. The RET antenna tilt can be remotely adjusted through the electrical control. l l
7-126
Calibrating the RET antenna will impact its coverage range. Calibrating an RET antenna takes up to four minutes.
Procedure
l Activation Procedure 1. 2. 3. 4. l l 1. Run the NodeB MML command SET ALDPWRSW to set PWRSW of the RET antenna to ON. Run the NodeB MML command ADD ALD to add an RET antenna. Run the NodeB MML command CLB AN to calibrate the RET antenna. Run the NodeB MML command SET ANTTILT to set the RET antenna tilt. Run the NodeB MML command DSP ANTTILT to query the RET antenna tilt.
Verification Procedure Deactivation Procedure This feature does not need to be deactivated.
----End
7.52 Configuring Same Band Antenna Sharing Unit (900 MHz)

This section describes how to activate, verify, and deactivate the basic feature WRFD-060003 Configuring Same Band Antenna Sharing Unit (900 MHz).
Prerequisite
Context
l l The introduction of the feature enables UMTS900 and GSM900 to share the same antenna. The feature helps to share an antenna in the same band and causes little uplink division loss. Compared with the traditional combiner and diplexer, the feature achieves a 3 dB gain.
Procedure
l Activation Procedure 1. 2. 3. 4. 5.
Issue 03 (2010-09-20)
Run the NodeB MML command SET ALDPWRSW to turn on the power supply switch of the SASU (Same band Antenna Sharing Unit) port. Run the NodeB MML command SCN ALD to scan antenna devices and obtain the serial number of the SASU. Run the NodeB MML command ADD ALD to configure the SASU. Run the NodeB MML command SET SASUMODE to set the SASU working mode. Run the NodeB MML command SET SASUGAIN to set the gain of the SASU.
6. 7. l 1. 2. 3. 4. 5. l
Run the NodeB MML command SET SASUDCSW to set the antenna DC power switch state of the SASU. Run the NodeB MML command SET SASUDCLD to set the DC load of the SASU. Run the NodeB MML command LST ALD to query the configuration information about the SASU. Run the NodeB MML command LST SASUMODE to query the SASU working mode. Run the NodeB MML command LST SASUGAIN to query the gain of the SASU. Run the NodeB MML command LST SASUDCSW to query the antenna DC power switch state of the SASU. Run the NodeB MML command LST SASUDCLD to query the DC load of the SASU.
----End
Example
// To activate the SASU, do as follows: 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; // To verify the SASU, do as follows: 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";
7.53 Configuring Multi-mode BS Common CPRI Interface (NodeB)

This section describes how to activate, verify, and deactivate the basic feature MRFD-220001 Multi-mode BS Common CPRI Interface (NodeB).
Prerequisite
l Dependency on Hardware As Figure 7-8 shows, the hardware of the base station is installed.
7-128
Issue 03 (2010-09-20)
Figure 7-8 Network topology of Multi-mode BS Common CPRI Interface
NOTE
As Figure 7-8 shows, CPRI0, CPRI1, and CPRI2 on the GTMU board are respectively connected to one CPRI port on the WBBP board. CPRI3, CPRI4, and CPRI5 are connected to the RRU3908.
l l
Dependency on Other Features None License None
Context
In the traditional GSM+UMTS dual-mode solution, the GSM and UMTS base stations use the same site. Different RF modules are used for different radio standards and thus separate optical cables are required. As a result, many optical cables are required for the entire system, which increases the deployment cost. After this feature is applied, the demand of optical cables is reduced by 50%, which helps reduce the cost of the optical modules and optical cables and reduce the expense in the installation and maintenance of the optical cables between the BBU and RF modules.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD BTSSFPMODE to configure the switching relation of the SFP ports and switch the data of CPRI0, CPRI1, and CPRI2 on the GTMU to CPRI3, CPRI4, and CPRI5 on the GTMU.
NOTE
The switching relation of the SFP ports is configured only on the GSM side.
Verification Procedure 1. Run the BSC6900 MML command LST BTSSFPMODE to query the configurations of the SFP ports.
Issue 03 (2010-09-20)
7-129
1. ----End
Run the BSC6900 MML command RMV BTSSFPMODE to remove the SFP port switching relation.
Example
// To configure the switching relation between CPRI0 and CPRI3 on the GTMU, do as follows:
ADD BTSSFPMODE: IDTYPE=BYID, BTSID=161, CN=0, SRN=0, SN=6, SFPPORTNO=0, SWITCHPORTNO=3;
7.54 Configuring Multiple RAB Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-010615 Multiple RAB Package (PS RAB 2).
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. 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 l l l 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
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter. Details see the verification procedure of following features: 7.55 Configuring Combination of Two PS Services, 7.56 Configuring Combination of One CS Service and Two PS Services, 7.57 Configuring Combination of Three PS
7-130
Services, 7.58 Configuring Combination of One CS Service and Three PS Services and 7.59 Configuring Combination of Four PS Services. l Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
----End
Example
//Activating Multiple RAB Package (PS RAB 2). SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1; //Deactivating Multiple RAB Package (PS RAB 2). SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-0;
7.55 Configuring Combination of Two PS Services

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061501 Combination of Two PS Services.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010615 Multiple RAB Package (PS RAB 2). l l License The license is activated. Other Prerequisites The UE supports the combination of two PS services. 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.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter. Connect the UE to the portable computer so as to use the UE as a modem. Visit the Internet on the UE. Verify that web pages are displayed normally.
Issue 03 (2010-09-20)
3. l
On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
----End
Example
//Activating Combination of Two PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1; //Deactivating Combination of Two PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-0;
7.56 Configuring Combination of One CS Service and Two PS Services

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061502 Combination of One CS Service and Two PS Services.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010615 Multiple RAB Package (PS RAB 2). l l License The license is activated. Other Prerequisites The UE supports the combination of One CS Service and Two PS Services. The CN node and UE must have the corresponding multi-RAB support capability.
Context
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter. Have two UEs ready: UE 1 and UE 2. Connect UE 1 to the portable computer so as to use the UE as a modem.
7-132
3. 4. 5. l 1.
Visit the Internet on UE 1. Verify that web pages are displayed normally. On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally. Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
----End
Example
//Activating Combination of One CS Service and Two PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1; //Deactivating Combination of One CS Service and Two PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-0;
7.57 Configuring Combination of Three PS Services

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061503 Combination of Three PS Services.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010615 Multiple RAB Package (PS RAB 2). l l License The license is activated. Other Prerequisites The UE supports the Combination of Three PS Services. The CN node and UE must have the corresponding multi-RAB support capability.
Context
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter. Connect UE to the portable computer so as to use the UE as a modem.
Issue 03 (2010-09-20)
2. 3. 4. l
Visit the Internet on UE. Verify that web pages are displayed normally. On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally. Start a Video on Demand (VOD) program on the UE. Verify that the video is played normally. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
----End
Example
//Activating Combination of Three PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1; //Deactivating Combination of Three PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-0;
7.58 Configuring Combination of One CS Service and Three PS Services

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061504 Combination of One CS Service and Three PS Services.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010615 Multiple RAB Package (PS RAB 2). l l License The license is activated. Other Prerequisites The UE supports the combination of One CS Service and Three PS Services. The CN node and UE must have the corresponding multi-RAB support capability.
Context
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
7-134
Verification Procedure 1. 2. 3. 4. Have two UEs ready: UE 1 and UE 2. Initiate Iu interface tracing on the BSC6900 LMT. Connect UE 1 to the portable computer so as to use the UE as a modem. Visit an IMS website on UE 1 to start IMS signaling. If the value of the trafficClass IE in the RANAP_RAB_ASSIGNMENT_REQ message is Interactive and the value of the SigInd IE in the same message is IU_SIG, you can infer that the service is an IMS service. At the IMS website, start a browsing service. Verify that the service can be started properly. On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally. Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
5. 6. 7. l 1.
----End
Example
//Activating Combination of One CS Service and Three PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1; //Deactivating Combination of One CS Service and Three PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-0;
7.59 Configuring Combination of Four PS Services

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061505 Combination of Four PS Services.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010615 Multiple RAB Package (PS RAB 2). l l License The license is activated. Other Prerequisites The UE supports the combination of Four PS Services. The CN node and UE must 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 7-9. Figure 7-9 VoIP service
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 Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter. Run the BSC6900 MML command SET UFRCCHLTYPEPARA command to set the VOIP channel type parameter to DCH(UL_DCH,DL_DCH).
NOTE
2.
The BSC6900 defines the default value of the VOIP channel type parameter. Retain the default value in normal situations.
Verification Procedure 1. 2. 3. Initiate Iu interface tracing on the BSC6900 LMT. Connect the UE to the portable computer so as to use the UE as a modem. 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. On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_MULTI_RAB_SWITCH check box under the Channel configuration strategy switch parameter.
4. l
----End
Example
//Activating Combination of Four PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-1; SET UFRCCHLTYPEPARA: VoipChlType=DCH; //Deactivating Combination of Four PS Services. SET UCORRMALGOSWITCH: CfgSwitch=CFG_MULTI_RAB_SWITCH-0;
7-136
Issue 03 (2010-09-20)
7.60 Configuring HSDPA Introduction Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-010610 HSDPA Introduction Package.
Prerequisite
l l Dependency on Hardware NDLP and NBBI do not support this feature. Dependency on Other Features The HSDPA feature provides a number of methods to increase system throughput. It has to coordinate with other features, such as admission control, load control, and mobility management. l l License The license is activated. Other Prerequisites The UE should have the HSDPA capability.
Context
High Speed Downlink Packet Access (HSDPA) is one of the important features defined in 3GPP specifications. HSDPA can greatly increase the peak rate per user, shorten the round trip delay, and improve the system capacity. This feature package provides the basic functions of HSDPA to meet the requirements for test or trial operations of HSDPA services.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command ADD UCELLHSDPA to add HSDPA-related parameters. Run the BSC6900 MML command ACT UCELLHSDPA to activate this feature. Configure Iub transport for HSDPA. For example, Run the BSC6900 MML command ADD ATMTRF to configure new records of ATM traffic. Run the BSC6900 MML command ADD AAL2PATH to configure a AAL2PATH for HSDPA. Run the NodeB MML command ADD AAL2PATH to configure a AAL2PATH for HSDPA. l Verification Procedure 1. Run the BSC6900 MML command DSP UCELL to check that the feature HSDPA Introduction Package has been activated. If the HSDPA Operate State is HSDPA Enabled, it indicates that the feature HSDPA Introduction Package has been activated.
l
Issue 03 (2010-09-20)
1. 2.
Run the BSC6900 MML command DEA UCELLHSDPA to deactivate the feature HSDPA Introduction Package. Run the BSC6900 MML command DSP UCELL to check that the feature HSDPA Introduction Package has been deactivated. If the HSDPA Operate State is HSDPA Disabled, it indicates that the feature HSDPA Introduction Package has been deactivated.
----End
Example
//Adding 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 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; //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;
7.61 Configuring 15 Codes per Cell

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061001 15 Codes per Cell.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l License The license is activated.
Context
This feature provides code resources occupied by Huawei HSDPA services. The HS-PDSCHs can use up to 15 codes in a cell.
Procedure
l
7-138
1.
This feature does not need to be activated.

NOTE
Each HS-SCCH uses an SF128 code. The default number of HS-SCCH each cell is 4, which is specified by the parameter Code Number for HS-SCCH through the BSC6900 MML command MOD UCELLHSDPA. If the default setting is used, the HS-PDSCH can use only 14 SF16 codes. To enable the HS-PDSCH to use 15 SF16 codes, you are advised to configure 2 HS-SCCHs.
Verification Procedure 1. 2. 3. Run the BSC6900 MML command MOD UCELLHSDPA to configure 1 HSSCCHs. Run the BSC6900 MML command MOD UCELLHSDPA to set the Allocate Code Mode to Manual, and the Code Number for HS-PDSCH to 15. Initial the UMTS monitoring in the BSC6900 LMT, as shown in Figure 7-10. Click Submit, and the monitoring is started. A real-time monitoring window on the title bar is displayed. Figure 7-10 Cell Performance Monitoring
4.
Check if 15 codes is assigned to HSPDSCH of the code tree performance monitor in the cell performance monitoring window. Expected result: 15 codes is assigned to HSPDSCH of the code tree performance monitor.
Deactivation Procedure 1. This feature does not need to be deactivated.
----End
Example
//Verifying 15 Codes per Cell MOD UCELLHSDPA: CellId=1, HsScchCodeNum=1; MOD UCELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=15;
7.62 Configuring Time and HS-PDSCH Codes Multiplex

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
Prerequisite
l
Issue 03 (2010-09-20)
None l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l License The license is activated.
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 l l Activation Procedure This feature does not need to be activated. Verification Procedure This feature does not need to be verified. Deactivation Procedure This feature does not need to be deactivated. ----End
7.63 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
Prerequisite
Context
This feature is related to hybrid automatic repeat request (HARQ) and HSDPA scheduling algorithms. 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.

NOTE
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.
Procedure
l Activation Procedure 1. To activate the scheduling algorithm, run the NodeB MML command SET MACHSPARA to set the parameter Scheduling Method to MAXCI(Max C/I Algorithm), RR(Round Robin Algorithm) or PF(PF Algorithm). Run the NodeB MML command LST MACHSPARA to query the settings of the parameter Scheduling Method.
----End
7.64 Configuring HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation.
Prerequisite
Context
This feature is related to HSDPA static code allocation and RNC-controlled dynamic code allocation. When R99 and HSDPA services co-exist, this feature enables full use of channelized code resources to improve the efficiency and system capacity.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLHSDPA to set Allocate Code Mode to Manual or Automatic. If the parameter Allocate Code Mode is set to Manual, set the parameter Code Number for HS-PDSCH to specify the number of HS-PDSCH codes.
If the parameter Allocate Code Mode is set to Automatic, set the parameter Code Max Number for HS-PDSCH to specify the maximum number of HS-PDSCH codes and set the parameter Code Min Number for HS-PDSCH to specify the minimum number of HS-PDSCH codes. l Verification Procedure 1. 2. Run the BSC6900 MML command LST UCELLHSDPA to query the code allocation mode. Start the cell performance monitoring task, as shown in Figure 7-11. If Allocate Code Mode is set to Manual, the number of HS-PDSCH codes remains unchanged. If Allocate Code Mode is set to Automatic, the number of HS-PDSCH codes changes all the time. Figure 7-11 Cell performance monitoring
----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;
7.65 Configuring HSDPA Power Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061004 HSDPA Power Control.
Prerequisite
l l
7-142

The feature WRFD-010610 HSDPA Introduction Package on which this feature depends has been activated. l License The license is activated.
Context
After the HSDPA service is introduced, the total downlink transmit power of each cell is classified into power of common channels, power of DPCHs, and power of physical HSDPA channels (HS-PDSCH and HS-SCCH). To achieve better HSDPA performance, power resources except those reserved for common channels are dynamically assigned to DPCHs and HSDPAs. For the R99 service, the DPCH power can be adjusted through the control of the inner loop power and outer loop power. The NodeB dynamically assigns the HSDPA power to users through the scheduling algorithm. The HS-PDSCH power is controlled by the TFRC algorithm, and thus no power control is required. This feature enables the operator to properly configure the power control mode of the HS-SCCH, which improves the power efficiency and increases system capacity and user experience.
Procedure
l Activation Procedure 1. To activate HS-SCCH power control, run the NodeB MML command SET MACHSPARA to set HS-SCCH Power Control Method in CELL DCH state to CQI or FIXED. By default, HS-SCCH Power Control Method in CELL DCH state is set to FIXED. l Verification Procedure 1. l Run the NodeB MML command LST MACHSPARA to query the setting of HSSCCH Power Control Method in CELL DCH state.
Deactivation Procedure This feature does not need to be deactivated. To use the HSDPA, this feature must be configured.
----End
7.66 Configuring HSDPA Admission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061003 HSDPA Admission Control.
Prerequisite
l l
Issue 03 (2010-09-20)

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l License The license is activated.
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. HSDPA Admission Control consist of code resource admission, power resource admission and NodeB credit resource admission.
Procedure
l Activation Procedure 1. Activate Code Resource Admission Code resource-based admission is mandatory for services access. It is enabled by default. 2. Activate Power Resource Admission Run the BSC6900 MML command MOD UCELLALGOSWITCH to select HSDPA_UU_ADCTRL through the parameter Cell CAC algorithm switch and select an appropriate algorithm through the parameters Uplink CAC algorithm switch and Downlink CAC algorithm switch. For HSDPA services, run the BSC6900 MML command MOD UCELLALGOSWITCH to set the associated admission algorithm switches through the parameter Cell CAC algorithm switch (including HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm), HSDPA_PBR_MEAS (HSDPA PBR Meas Algorithm) and HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm)). Run the BSC6900 MML command MOD UCELLCAC to set power resource admission related parameters. 3. Activate NodeB Credit Resource Admission Run the BSC6900 MML command SET UCACALGOSWITCH to select NODEB_CREDIT_CAC_SWITCH through the parameter CAC algorithm switch. Run the BSC6900 MML command MOD UCELLALGOSWITCH to select CRD_ADCTRL through the parameter Cell CAC algorithm switch. Run the BSC6900 MML command MOD UCELLCAC to set Ul handover credit reserved SF and Dl handover credit and code reserved SF to appropriate values. l Verification Procedure 1. Run the following BSC6900 MML commands to verify whether the activation is successful. LST UCELLALGOSWITCH LST UCACALGOSWITCH LST UCELLCAC
Deactivation Procedure 1. Deactivate Code Resource Admission. Code resource-based admission is mandatory for services access. It can not be disabled. 2. Deactivate Power Resource Admission: Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the cell-oriented power resource admission switch (Uplink CAC algorithm switch and Downlink CAC algorithm switch) to ALGORITHM_OFF. Deactivate NodeB Credit Resource Admission. To disable NodeB Credit Resource Admission, perform the following steps: Run the BSC6900 MML command SET UCACALGOSWITCH to close NODEB_CREDIT_CAC_SWITCH(NodeB Credit CAC Switch). Run the BSC6900 MML command MOD UCELLALGOSWITCH to close CRD_ADCTRL(Credit Admission Control Algorithm) switch.
3.
----End
Example
//Activate Power Resource Admission MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1,NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST; 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; //Activate 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, DlHoCeCodeResvSf=SF32; //Deactivate Power Resource Admission SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_HSSCCH_LESS_OP_SWITCH-0; //Deactivate NodeB Credit Resource Admission SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-0; MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=HS_SCCH_LESS_OPERATION-0;
7.67 Configuring HSDPA Dynamic Power Allocation

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061019 HSDPA Dynamic Power Allocation.
Prerequisite
Context
This feature enables R99 and HSDPA services to share the cell power. This feature can ensure the requirements of R99 users and make HSDPA users obtain a higher throughput, thus greatly improving the power efficiency.
Procedure
7.68 Configuring HSDPA Flow Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061010 HSDPA Flow Control.
Prerequisite
Context
For each MAC-hs queue, 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. On the other hand, it should keep a certain amount of data to avoid wasting the Uu resources due to no data to transmit. The flow control procedure is as follows: 1. 2. 3.
7-146
The NodeB measures the buffered data amount of each MAC-hs queue and the average Uu transmission rate. The NodeB estimates the buffering time based on the measurements. The NodeB adjusts the Iub bandwidth pre-allocated to the MAC-hs queue.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET HSDPAFLOWCTRLPARA to set the parameter Flow Control Switch to trigger the NodeB HSDPA flow control function. There are three types of flow control algorithms as follows: When the Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does not adjust the available bandwidth for HSDPA users based on the delay and packet loss condition 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 the Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB adjusts the available bandwidth for HSDPA users based on the delay and packet loss condition on the Iub interface. Then, considering the rate on the air interface, the NodeB performs Iub shaping and distributes flow to HSDPA users. When the Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not adjust the bandwidth based on the delay and packet loss condition on the Iub interface. The NodeB reports the conditions on the air interface to the RNC, and then the RNC performs bandwidth allocation. When the 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. l Verification Procedure 1. 2. Create UL Throughput Bandwidth and DL Throughput Bandwidth tasks in the LMT. UE1 accesses the network and make a PS service and record the throughput of the UE1. Expected result: The throughput of the UE1 is about 2Mbps and keep stable. 3. UE2 accesses the network and make a download service and record the throughput of the two UEs. Expected result: The throughput of UE1 is degraded. The throughput of the two UEs is stable. And the proportion of the two UEs' throughput is about 1:1. l Deactivation Procedure You can choose one of the other flow control algorithms to deactivate the current algorithms. ----End
Example
//Activation Procedure 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 03 (2010-09-20)
7-147
7.69 Configuring HSDPA Mobility Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061006 HSDPA Mobility Management.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The feature WRFD-010610 HSDPA Introduction Package on which this feature depends has been activated. l License The license is activated.
Context
This feature enables an HSDPA-capable UE to be handed over to an R99 cell or another HSDPA cell when the UE is moving. This feature also enables an HSDPA-capable UE to change the cell with a small probability of service interruption.
Procedure
l Activation Procedure 1. The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers are the same for HSDPA users and common users. For details, see the following sections: 7.30 Configuring Intra Frequency Hard Handover 7.125 Configuring Inter-Frequency Hard Handover Based on Coverage 7.126 Configuring Inter-Frequency Hard Handover Based on DL QoS 7.137 Configuring Inter-Frequency Load Balance 7.130 Configuring Inter-RAT Handover Based on Coverage 7.131 Configuring Inter-RAT Handover Based on DL QoS 7.138 Configuring Inter-RAT Handover Based on Service 7.139 Configuring Inter-RAT Handover Based on Load l l Verification Procedure None Deactivation Procedure This feature does not need to be deactivated. ----End
7-148
Issue 03 (2010-09-20)
7.70 Configuring Interactive and Background Traffic Class on HSDPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061008 Interactive and Background Traffic Class on HSDPA.
Prerequisite
Context
This feature enables interactive and background services to be mapped to the HS-DSCH to obtain a higher service rate and enhance user experience.
Procedure
l Activation Procedure 1. This feature is dependent on the feature HSDPA Introduction Package. In other words, this feature takes effect if the feature HSDPA Introduction Package has been activated. For information on activating the feature HSDPA Introduction Package, see the section 7.60 Configuring HSDPA Introduction Package. None None
l l
Verification Procedure 1. 1. Deactivation Procedure
----End
7.71 Configuring HSDPA UE Category 1 to 24

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061002 HSDPA UE Category 1 to 24.
Prerequisite
l l
Issue 03 (2010-09-20)

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l License The license is activated.
Context
This feature can provide proper HSDPA services for the UEs of category 1 to category 24.
Procedure
7.72 Configuring Improvement of User Experience in Low Traffic Service

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061020 Improvement of User Experience in Low Traffic Service.
Prerequisite
l l Dependency on Hardware Only BSC6900 supports this function. Dependency on Other Features The BSC6900 software version should be not earlier than RAN12.0. The NodeB software version should be not earlier than RAN12.0. The UE supports HSPA. WRFD-010610 HSDPA Introduction Package l License The license is activated.
Context
This feature improves user experience in low traffic service. The NodeB detects HSPA services with low traffic, such as gaming services and instant messaging services (such as MSN). Then, 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.
7-150
Issue 03 (2010-09-20)
Procedure
l Activation Procedure 1. 2. Run the NodeB MML command SET UEQOSENHANCEPARA to set the burst packet sizes of the gold, silver, and copper users according to the actual conditions. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select NODEB_PRIVATE_INTERFACE_SWITCH from the Process switch list. As a result of the action, the BSC6900 sends the NodeB the information of the gold, silver, and copper users through the private interface. Run the NodeB MML command LST UEQOSENHANCEPARA to query the burst packet sizes of the gold, silver, and copper users. Run the NodeB MML command SET UEQOSENHANCEPARA. 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
// Activation procedure // To set the burst packet sizes of the gold, silver, and copper users, run the following command: SET UEQOSENHANCEPARA: ULGOLDUEBPS=10, ULSILVERUEBPS=11, ULCOPPERUEBPS=12, DLGOLDUEBPS=13, DLSILVERUEBPS=14, DLCOPPERUEBPS=15; // To set the process control switch, run the following command: SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; // Verification procedure // To query the burst packet sizes of the gold, silver, and copper users, run the following command: LST UEQOSENHANCEPARA:; // Deactivation procedure SET UEQOSENHANCEPARA: ULGOLDUEBPS=0, ULSILVERUEBPS=0, ULCOPPERUEBPS=0, DLGOLDUEBPS=0, DLSILVERUEBPS=0, DLCOPPERUEBPS=0;
7.73 Configuring DL 16QAM Modulation

This section describes how to activate, verify, and deactivate the optional feature WRFD-010629 16QAM Modulation.
Prerequisite
l l l Dependency on Hardware None Dependency on Other Features WRFD-010610 HSDPA Introduction Package License The license is activated.
Others UE should support the demodulation of 16QAM.
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. Note that the peak rate on the Uu interface can reach 14.4 Mbit/s only when the following conditions are met: l l l The UE belongs in category 10 or supports high-order HSDPA. The HS-PDSCHs can use up to 15 codes in a cell. The DL 16QAM modulation scheme is used.
Procedure
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
Run the NodeB MML command SET MACHSPARA. In this step, set 16QAM Switch to 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 6 Mbit/s.
Perform the following steps to check whether the download rate can reach 6 Mbit/s. 1. 2. 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. Start FTP (using 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 6 Mbit/s. Run the NodeB MML command SET MACHSPARA. In this step, set 16QAM Switch to CLOSE.
----End
Example
//Activating DL 16QAM Modulation SET MACHSPARA: 16QAMSW=OPEN; //Deactivating DL 16QAM Modulation SET MACHSPARA: 16QAMSW=CLOSE;
7-152
Issue 03 (2010-09-20)
7.74 Configuring Dynamic Code Allocation Based on NodeB

This section describes how to activate, verify, and deactivate the optional feature WRFD-010631 Dynamic Code Allocation Based on NodeB.
Prerequisite
l l l Dependency on Hardware None Dependency on Other Features WRFD-010610 HSDPA Introduction Package License The license is activated.
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 Activation Procedure This feature depends on the feature HSDPA Introduction Package. In other words, to activate this feature, HSDPA Introduction Package must be activated first. For information on activating HSDPA Introduction Package, see the section "Configuring HSDPA Introduction Package." 1. l Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to OPEN. Run the NodeB MML command LST MACHSPARA to query that Dynamic Code Switch is set to OPEN. Run the BSC6900 MML command MOD UCELLHSDPA. In this step, set Allocate Code Mode to Manual and Code Number for HS-PDSCH to 5. 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. On the BSC6900 LMT, check the trace item Cell Code Tree Monitor in Dynamic Code Switch to CLOSE. If the number of HS-PDSCH codes in use exceeds five, you can infer that this feature has been activated. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to CLOSE.
----End
7.75 Configuring HSDPA Enhanced Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-010611 HSDPA Enhanced Package.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l l License The license is activated. 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 l l l WRFD-01061103 Scheduling based on EPF and GBR WRFD-01061111 HSDPA State Transition WRFD-01061112 HSDPA DRD WRFD-01061113 HS-DPCCH Preamble Support
Procedure
l For details about activate, verify, and deactivate procedures, see the following sections: 7.76 Configuring Scheduling based on EPF and GBR 7.77 Configuring HSDPA State Transition 7.78 Configuring HSDPA DRD
NOTE
HS-DPCCH Preamble Support does not need to be activated, verified, or deactivated.
----End
7.76 Configuring Scheduling based on EPF and GBR

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061103 Scheduling based on EPF and GBR.
Prerequisite
l
7-154
None l l Dependency on Other Features None License The license is activated.
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 Activation Procedure 1. l Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling Method to EPF(Enhanced PF). Run the NodeB MML command LST MACHSPARA to check that Scheduling Method is set to EPF. Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling Method to an option other than EPF(Enhanced PF).
----End
Example
// Activation Procedure SET MACHSPARA: SM=EPF; // Verification Procedure LST MACHSPARA; // Deactivation Procedure SET MACHSPARA: SM=PF;
7.77 Configuring HSDPA State Transition

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061111 HSDPA State Transition.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l
Issue 03 (2010-09-20)
License
The license is activated.
Context
This feature enables the handover between the DCH and HS-DSCH and makes it possible for the UE to leverage the high-speed service. When the UE is inactive, this feature enables the handover of the UE to the CELL_FACH to save system resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DRA_HSDPA_STATE_TRANS_SWITCH and DRA_PS_BE_STATE_TRANS_SWITCH from the drop-down list Dynamic resource allocation switch. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether DRA_HSDPA_STATE_TRANS_SWITCH and DRA_PS_BE_STATE_TRANS_SWITCH are selected from the drop-down list Dynamic resource allocation switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear DRA_HSDPA_STATE_TRANS_SWITCH and DRA_PS_BE_STATE_TRANS_SWITCH from the drop-down list Dynamic resource allocation switch.
----End
Example
//Activating HSDPA State Transition SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-1&DRA_PS_BE_STATE_TRANS_SWITCH-1; //Deactivating HSDPA State Transition SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_PS_BE_STATE_TRANS_SWITCH-0;
7.78 Configuring HSDPA DRD

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061112 HSDPA DRD.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features 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-020400 DRD Introduction Package. l
7-156
License
Context
This feature enables HSDPA suitable service to be established on the HS-DSCH cell as much as possible if a UE is HS-DSCH capable, thus achieving better service performance.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command ADD UCELLDRD to set the parameter Load balance DRD switch for HSDPA to ON. Run the BSC6900 MML command LST UCELLDRD to check whether the parameter Load balance DRD switch for HSDPA is set to ON. The expected result: The value of Load balance DRD switch for HSDPA is ON. 2. The load in cell 1 is lighter than that in cell 2. The UE accesses the network from cell 2 and then attempts to establish an HSDPA service. The UE may be handed over to cell 1 through a directed retry procedure. 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 2 and the RRC_RB_RECFG_CMP/RRC_RB_SETUP_CMP message is sent to the RNC in cell 1, as shown in Figure 7-12. Figure 7-12 RRC_RB_RECFG/RRC_RB_SETUP Information
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLDRD to set the parameter Load balance DRD switch for HSDPA to OFF.
----End
Example
//Activating HSDPA DRD ADD UCELLDRD: LdbDRDSwitchHSDPA=ON; //Deactivating HSDPA DRD MOD UCELLDRD: LdbDRDSwitchHSDPA=OFF;
Issue 03 (2010-09-20)
7-157
7.79 Configuring Interactive and Background Traffic Class on HSDPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-010630 Interactive and Background Traffic Class on HSDPA.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010611 HSDPA Enhanced Package. l License The license is activated.
Context
This feature enables the streaming services to be mapped onto the HS-DSCH, which improves the utilization of cell resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH 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 7-13.
7-158
Issue 03 (2010-09-20)
Figure 7-13 Uu Interface Trace dialog box
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. Check whether the service can receive the data successfully. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear MAP_PS_STREAM_ON_HSDPA_SWITCH from the drop-down list Service mapping strategy switch.
3. l 1.
----End
Example
//Activating Interactive and Background Traffic Class on HSDPA SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; //Deactivating Interactive and Background Traffic Class on HSDPA SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-0;
7.80 Configuring HSDPA over Iur

This section describes how to activate, verify, and deactivate the optional feature WRFD-010651 IHSDPA over Iur.
Prerequisite
l l
Issue 03 (2010-09-20)

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l l License The license is activated. Other Prerequisites The neighboring RNC should also support HSDPA over Iur.
Context
HSDPA over Iur provides continuous HSDPA services for mobile users moving between RNCs. It enlarges the range of HSDPA services to the RNCs that have Iur connections with a certain RNC.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UEXT3GCELL to select HSDSCH support indicator and F-DPCH support indicator from the parameter Cell Capability Container. Enable the cross-Iur hard handover and soft handover. Run the BSC6900 MML command MOD UNRNC to set the parameter Hsdpa cap ind over IUR for NRNC to ON, enable the handover function. Run the BSC6900 MML command MOD UNRNC to set the parameter Hsdpa cap ind over IUR for NRNC to OFF. Run the BSC6900 MML command MOD UEXT3GCELL to deselect HSDSCH support indicator and F-DPCH support indicator from the parameter Cell Capability Container.
2. l
Deactivation Procedure 1. 2.
----End
Example
//Activating HSDPA over Iur MOD UEXT3GCELL: NRncId=1, CellId=1, CellCapContainerFdd=HSDSCH_SUPPORT-1&FDPCH_SUPPORT-1; MOD UNRNC: NRncId=1, IurHsdpaSuppInd=ON; //Deactivating HSDPA over Iur MOD UNRNC: NRncId=1, IurHsdpaSuppInd=OFF; MOD UEXT3GCELL: NRncId=1, CellId=1, CellCapContainerFdd=HSDSCH_SUPPORT-0&FDPCH_SUPPORT-0;
7.81 Configuring SRB over HSDPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-010652 SRB over HSDPA.
Prerequisite
l Dependency on Hardware BSC6900 None
NodeB The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board,EBOI board or EDLP board. The BBU3806 need to configure EBBC or EBBCd board; the BBU3806C need to configure EBBM board. The BBU3900 need to configure WBBPb or WBBPd board. UE None l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l License The license is activated.
Context
This feature uses the FDPCH multiplexing technology to carry the Down Link Signalling Radio Bearer (DL SRB) of multiple users over the HSDPA. This reduces the consumption of DL code resources and transmission resources and the delay of call establishment. During RRC connection establishment, this feature can be activated according to the following procedure. During RAB establishment, the SRB is carried on the HSDPA only when all the downlink services of the UE are carried on the HSDPA channel. This feature is dependent on the Fractional Dedicated Physical Channel (F-DPCH) function.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET URRCESTCAUSE to set the SRB bearer channel type during RRC connection establishment, based on the RRC connection establishment cause. For example, if the Cause of RRC connection establishment is ORIGCONVCALLEST, set the channel type for RRC establishment parameter to DCH_6.8K_SIGNALLING and the switch for RRC established on E_FACH parameter to OFF.
NOTE
The parameters Cause of RRC connection establishment and channel type for RRC establishment must be set based on the actual network planning.
2. 3.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the parameter SRB channel type RRC effect flag to TRUE. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the parameter SRB channel type to HSDPA(UL_DCH,DL_HSDSCH) or HSPA (UL_EDCH,DL_HSDSCH). Initiate Uu interface tracing on the BSC6900 LMT to select RRC_RB_SETUP and RRC_RRC_CONN_SETUP, as shown in Figure 7-14.
Issue 03 (2010-09-20)
2.
Verify this feature during signaling establishment. In the Uu interface trace data, view the dl-TransportChannelType information element (IE) in the RRC_RRC_CONN_SETUP message. If the dl-TransportChannelType IE is hsdsch as shown in Figure 7-15, you can infer that this feature has been activated. If the dl-TransportChannelType IE is not hsdsch, you can infer that this feature has not been activated. Figure 7-15 SRB Over HSPA during signaling establishment
3.
Verify this feature during traffic establishment. In the Uu interface trace data, view the dl-TransportChannelType IE in the RRC_RB_SETUP message. If the dl-TransportChannelType IE is hsdsch as shown in Figure 7-16, you can infer that this feature has been activated.
7-162
Issue 03 (2010-09-20)
If the dl-TransportChannelType IE is not hsdsch, you can infer that this feature has not been activated. Figure 7-16 SRB Over HSPA during traffic establishment
Deactivation Procedure 1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the parameter SRB channel type RRC effect flag to FALSE.
----End
Example
//Activating SRB over HSDPA. SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH3=SRB_OVER_HSDPA-1; SET URRCESTCAUSE: RrcCause=ORIGCONVCALLEST, SigChType=DCH_6.8K_SIGNALLING, EFachSwitch=OFF; SET UFRCCHLTYPEPARA: SrbChlTypeRrcEffectFlag=TRUE; SET UFRCCHLTYPEPARA: SrbChlType=HSDPA; //Deactivating SRB over HSDPA. SET UFRCCHLTYPEPARA: SrbChlTypeRrcEffectFlag=FALSE;
7.82 Configuring HSUPA Introduction Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-010612 HSUPA Introduction Package.
Prerequisite
l Dependency on Hardware NBBI does not support this feature. UE should have HSUPA capability. l l Dependency on Other Features None License The license is activated.
Context
WRFD-010612 HSUPA Introduction Package enables the system to process HSUPA services, thus increasing the uplink rate and system throughput. This package provides basic functions of HSUPA to meet the requirements for test or trial operation of HSUPA services.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command ADD UCELLHSUPA to add an HSUPA cell. Run the BSC6900 MML command ACT UCELLHSUPA to activate the HSUPA function of the cell. Ensure that the HSUPA function of the cell is activated. Run the BSC6900 MML command DSP UCELL to show that HSUPA is enabled. Establish a PS service. The E-DCH FDD IE in the RL SETUP message on the Iub interface and the rbmappinginfo IE in the RRC_RB_SETUP message on the Uu interface indicate that the service is set up and carried on the E-DCH. l Deactivation Procedure 1. 2. ----End Run the BSC6900 MML command DEA UCELLHSUPA to deactivate the HSUPA function of the cell. Run the BSC6900 MML command RMV UCELLHSUPA to remove the HSUPA cell.
Example
//Activation Procedure ADD UCELLHSUPA: CellId=111; ACT UCELLHSUPA: CellId=111; //Verification Procedure DSP UCELL: Cell HSUPA State=AVAILABLE(HSUPA Available cell); CELLID=111; //Deactivation Procedure DEA UCELLHSUPA: CellId=111; RMV UCELLHSUPA: CellId=111;
7.83 Configuring HSUPA Admission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061202 HSUPA Admission Control.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package.
License The license is activated.
Context
This feature enables HSUPA and R99 services to simultaneously access the network by using the remaining uplink cell load and other resources, thus improving the utilization of system resources and ensuring QoS.
Procedure
l Activation Procedure 1. Activating Power Resource Admission (1) Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the cell-oriented power resource admission switch to ON and select an uplink and downlink CAC algorithm through the parameters Uplink CAC algorithm switch and Downlink CAC algorithm switch. (2) For HSUPA services, run the BSC6900 MML command MOD UCELLALGOSWITCH to set the associated admission algorithm switches (HSUPA_PBR_MEAS, HSUPA_EDCH_RSEPS_MEAS, HSUPA_UU_ADCTRL) to 1. (3) Run the MML command MOD UCELLCAC to set power resource admission parameters and maximum HSUPA user number. 2. Activating NodeB Credit Resource Admission (1) Run the BSC6900 MML command SET UCACALGOSWITCH to set the NodeB-oriented CE admission switch NODEB_CREDIT_CAC_SWITCH to 1. (2) Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the cell-oriented credit resource admission switch CRD_ADCTRL to 1. (3) Run the BSC6900 MML command MOD UCELLCAC command to set NodeB credit resource admission parameters (Ul handover credit reserved SF and Dl handover credit and code reserved SF). 3. Activating Iub Resource Admission (1) Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. (2) Run the BSC6900 MML command ADD IPPATH or ADD AAL2PATH to add a path.
NOTE
When adding an AAL2 path, set AAL2 Path Type to HSPA or SHARE.
(3) Run the BSC6900 MML command ADD TRMMAP to add a transport resource mapping table.
NOTE
If a transport resource mapping table is not added, the default transport resource mapping table is used. When adding a transport resource mapping table, set the path type of an HSUPA service to the service type for the traffic record index of the configured AAL2 path in the case of ATM transport, or to the path type of the configured IP path in the case of IP transport.
(4) Run the BSC6900 MML command ADD ADJMAP to add an adjacent node mapping relationship.

NOTE
If the user-defined TRMMAP or activity factor is used, use this command to configure the related data. If the ADJMAP is not configured, the default TRMMAP or activity factor is used.
Verification Procedure 1. Run the following BSC6900 MML commands to verify whether power pesource admission and NodeB credit resource admission are activated. LST UCELLALGOSWITCH LST UCACALGOSWITCH LST UCELLCAC 2. Run the following command to check whether Iub resource admission is activated. (1) Run the BSC6900 MML command ACT UCELL to activate the cell. (2) Run the BSC6900 MML command DSP IPPATH or DSP AAL2PATH to check whether any bandwidth is occupied.
Deactivation Procedure 1. To disable Power Resource Admission, perform the following steps: Run the BSC6900 MML command MOD UCELLALGOSWITCH to set the cell-oriented power resource admission switches (Uplink CAC algorithm switch and Downlink CAC algorithm switch) to ALGORITHM_OFF. 2. To disable NodeB Credit Resource Admission, perform the following steps: (1) Run the BSC6900 MML command SET UCACALGOSWITCH to set the NodeB-oriented CE admission switch NODEB_CREDIT_CAC_SWITCH to 0. (2) Run the BSC6900 MML command MOD UCELLALGOSWITCH command to set the cell-oriented NodeB credit resource admission switch CRD_ADCTRL to 0. 3. Deactivating Iub Resource Admission Run the BSC6900 MML command RMV IPPATH or RMV AAL2PATH to remove the path over the Iub interface.
----End
Example
//Activating Power Resource Admission MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=HSUPA_UU_ADCTRL-1&HSUPA_PBR_MEAS-1&HSUPA_EDCH_RSEPS_MEAS -1; MOD UCELLCAC: CellId=11, MaxUlTxPowerforConv=24, MaxUlTxPowerforInt=24, MaxHsupaUserNum=20; //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, DlHoCeCodeResvSf=SF32; //Activating Iub Resource Admission ADD ADJNODE: ANI=0, NAME="IUB-ADJNODE", NODET=IUB, NODEBID=0, TRANST=ATM, IsROOTNODE=YES, SAALLNKN=20; ADD AAL2PATH: ANI=0, PATHID=1, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=26, CARRYVPN=2, VPI=51, VCI=52, TXTRFX=104, RXTRFX=104, AAL2PATHT=SHARE; ADD TRMMAP: TMI=14, REMARK="IUB-HSUPA", ITFT=IUB, TRANST=ATM,
7-166
Issue 03 (2010-09-20)
HUVOICEPRIPATH=RT_VBR, HUVOICESECPATH=NRT_VBR, HUCONVPRIPATH=RT_VBR, HUCONVSECPATH=NRT_VBR, HUSTRMPRIPATH=RT_VBR, HUSTRMSECPATH=NRT_VBR; ADD ADJMAP: ANI=0, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE, TMIGLD=14, TMISLV=14, TMIBRZ=14, FTI=0; //Deactivating Power Resource Admission MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_OFF, NBMDlCacAlgoSelSwitch=ALGORITHM_OFF; //Deactivating NodeB Credit Resource Admission SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-0; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=CRD_ADCTRL-0; //Deactivating Iub Resource Admission RMV AAL2PATH: ANI=0, PATHID=1;
7.84 Configuring HSUPA Power Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061203 HSUPA Power Control.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The feature WRFD-010612 HSUPA Introduction Package on which this feature depends has been activated. l License The license is activated.
Context
Through power control of new physical channels, this feature can improve the power efficiency of the system, reduce UL and DL interference, and increase the system capacity.
Procedure
l l Activation Procedure 1. 1. None Run the NodeB MML command SET MACEPARA to set the power control mode for HSUPA. The options of power control are as follows: FIXED(Fixed transmit power) RNC_BASED (Dynamic Transmit Power Control Based on the Pilot of DPCH or F-DPCH) FOLLOW_TPC(Dynamic Transmit Power Control Based on the TPC of DPCH or F-DPCH) CQI_BASED(Dynamic transmit power control based on CQI), HSSCCH_BASED(Dynamic transmit power control based on HS-SCCH) 2.
Issue 03 (2010-09-20)
Use an HSUPA-capable UE to establish a PS service over the E-DCH.

3.
Move the UE to view the power changes on each HSUPA channel. If a static power control mode is used, the channel power should remain unchanged. If a dynamic power control mode is used, then: When the UE is moved away from the antenna, the transmit power of the EAGCH increases. When the UE is moved towards the antenna, the transmit power of the E-AGCH decreases.
Deactivation Procedure 1. None
----End
Example
//Activating HSUPA Power Control //Set the power control mode for the E-AGCH to FOLLOW_TPC SET MACEPARA: LOCELL=111, EAGCHPCPARA=YES, EAGCHPCMOD=FOLLOW_TPC;
7.85 Configuring HSUPA Mobility Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061204 HSUPA Mobility Management.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The feature WRFD-010612 HSUPA Introduction Package on which this feature depends has been activated. l License The license is activated.
Context
This feature enables an HSDPA-capable UE to be handed over to an R99 cell or another HSDPA cell when the HSDPA-capable UE is moving. This feature also enables an HSDPA-capable UE to change the cell with a small probability of service interruption.
Procedure
l Activation Procedure 1. The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers are the same for HSUPA users and common users. For details, see the following sections: 7.30 Configuring Intra Frequency Hard Handover 7.125 Configuring Inter-Frequency Hard Handover Based on Coverage
7.126 Configuring Inter-Frequency Hard Handover Based on DL QoS 7.137 Configuring Inter-Frequency Load Balance 7.130 Configuring Inter-RAT Handover Based on Coverage 7.131 Configuring Inter-RAT Handover Based on DL QoS 7.138 Configuring Inter-RAT Handover Based on Service 7.139 Configuring Inter-RAT Handover Based on Load l Verification Procedure 1. 2. 3. 4. 5. l Set up HSUPA cell A. Set up HSUPA cell B which is the neighboring cell of CELL A. Use an HSUPA-capable UE to upload files in size of 200 MB in the cell A. Move the UE to the location under the coverage of the cell B. If the upload service of the UE is not interrupted, you can infer that this feature is successful activated. The methods of deactivating intra-frequency, inter-frequency, and inter-RAT handovers are the same for HSUPA users and common users. For details, see the following sections: 7.30 Configuring Intra Frequency Hard Handover 7.125 Configuring Inter-Frequency Hard Handover Based on Coverage 7.126 Configuring Inter-Frequency Hard Handover Based on DL QoS 7.137 Configuring Inter-Frequency Load Balance 7.130 Configuring Inter-RAT Handover Based on Coverage 7.131 Configuring Inter-RAT Handover Based on DL QoS 7.138 Configuring Inter-RAT Handover Based on Service 7.139 Configuring Inter-RAT Handover Based on Load ----End
7.86 Configuring HSUPA DCCC

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061208 HSUPA DCCC.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package and WRFD-021101 Dynamic Channel Configuration Control (DCCC). This feature cannot be used together with the feature WRFD-010638 Dynamic CE Resource Management. If dynamic CE resource management of a NodeB and HSUPA DCCC are activated together, HSUPA DCCC of the BSC6900 that controls the NodeB
will become ineffective, and thus none of the NodeBs under the BSC6900 can be enabled with HSUPA DCCC. l License The license is activated.
Context
HSUPA DCCC can dynamically adjust the minimum SF code of HSUPA based on the user throughput and flexibly switch the UE state based on the user traffic, which improves the CE resource utilization and system efficiency.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DRA_DCCC_SWITCH and DRA_HSUPA_DCCC_SWITCH from the Dynamic resource allocation switch drop-down list box. Optional: Run the BSC6900 MML command SET UDCCC. In this step, select RATE_UP_AND_DOWN_ON_EDCH from the HSUPA DCCC Strategy dropdown list box so that the data rate of an HSUPA service can be increased or decreased.
NOTE
2.
After this step is performed, the rate of HSUPA services on an EDCH can be increased or decreased as required. If the rate of HSUPA services on the EDCH is expected to increase only, set HSUPA DCCC Strategy to RATE_UP_ONLY_ON_EDCH.
3.
Optional: Run the BSC6900 MML command SET UEDCHRATEADJUSTSET. In this step, set the HSUPA UpLink Rate Adjust Set parameter to the data rate set for rate adjustment by the HSUPA DCCC algorithm.
NOTE
This step sets the available rate set of the HSUPA DCCC algorithm. After this step is performed, HSUPA services can be of any rate in the set by using the HSUPA DCCC algorithm.
Verificaion Procedure 1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether DRA_DCCC_SWITCH and DRA_HSUPA_DCCC_SWITCH are selected. Make the UE establish an HSUPA BE service. After the service is established, layer 3 of the RNC sends an uplink throughput measurement control message to layer 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear DRA_HSUPA_DCCC_SWITCH from the Dynamic resource allocation switch drop-down list box.
2. l
----End
Example
//Activating HSUPA DCCC SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1&DRA_HSUPA_DCCC_SWITCH-1; SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH; SET UEDCHRATEADJUSTSET: EdchRateAdjustSet=RATE_8KBPS-0&RATE_16KBPS-0&RATE_32KBPS-0&RATE_64KBPS-0&
7-170
Issue 03 (2010-09-20)
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;
7.87 Configuring Interactive and Background Traffic Class on HSUPA

This section describes how to activate the optional feature WRFD-01061206 Interactive and Background Traffic Class on HSUPA.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package l License The license is activated.
Context
This feature enables interactive and background services to be mapped to the E-DCH to obtain a higher service rate and enhance the user experience.
Procedure
l Activation Procedure This feature depends on the HSUPA basic functions (WRFD-010612 HSUPA Introduction Package). This feature does not need to be activated. It takes effect only if the HSUPA basic functions are activated. For detailed configuration, see the section 7.82 Configuring HSUPA Introduction Package. ----End

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061211 20 HSUPA Users per Cell.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The feature WRFD-010612 HSUPA Introduction Package on which this feature depends has been activated.
Context
This feature enables a single HSUPA cell to support 20 HSUPA users simultaneously. If the number of HSUPA users exceeds 20, the DCH is attempted for service provisioning.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm). Run the BSC6900 MML command MOD UCELLCAC to set the maximum number of HSUPA users supported by the cell to 20. Click the "Monitor" tab on the top of the LMT of the BSC6900. Monitor Navigation Tree is displayed on the left panel. In the "UMTS monitoring", double-click "Cell performance monitoring". The cell performance monitoring dialog box is displayed. Select "Cell user number" in the "Monitor item list". Enable UEs to access the cell. Activate the PS service for such UEs, for example, the UEs upload files to the FTP server one by one. Expected Result The PS service is started successfully. When no more than 20 UEs is served in a cell, the uplink service is established on HSUPA and the downlink service is established on HSDPA. If more than 20 UEs are served in the cell, the HSUPA service is degraded to the R99 service for retry admission. l Deactivation Procedure 1. ----End This feature does not need to be deactivated.
2. l
2.
Example
//Activating 20 HSUPA Users per Cell MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0; MOD UCELLCAC: CellId=111, MaxHsupaUserNum=20;
7.89 Configuring HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH)

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061401 HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH).
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package. l License The license is activated.
Context
This feature enables the RAN to use the reported CQI and HS-SCCH information to effectively reduce the power consumption of the E-AGCH.
Procedure
l l Activation Procedure 1. 1. 2. Run the NodeB MML command SET MACEPARA to set the power control mode. Use an HSUPA-capable UE to establish a PS service over the E-DCH. Move the UE to view the power changes on each HSUPA channel. When the UE is moved away from the antenna, the transmit power of the E-AGCH increases. When the UE is moved towards the antenna, the transmit power of the E-AGCH decreases. l Deactivation Procedure 1. ----End Run the NodeB MML command SET MACEPARA to change the E-AGCH power control mode. Verification Procedure
Example
//Activating HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH) SET MACEPARA: EAGCHPCPARA=YES, EAGCHPCMOD=CQI_BASED; //Deactivating HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH) SET MACEPARA: EAGCHPCPARA=YES, EAGCHPCMOD=FIXED;
7.90 Configuring HSUPA 2ms TTI

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061403 HSUPA 2ms TTI.
Prerequisite
l Dependency on Hardware BSC6900
None NodeB The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board,EBOI board, EDLP or EDLPd board. The BBU3806 need to configure EBBC/EBBCd board; the BBU3806C need to configure EBBM board. The BBU3900 need to configure WBBPb/WBBPd board. BOOTP applies to only ATM networking scenarios. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package. l l License The license is activated. Other Prerequisites UE should have the capability of HSDPA Category 2,4,6,7,8,9.
Context
This feature enables a single user to obtain higher UL throughput and shorter delay.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select MAP_HSUPA_TTI_2MS_SWITCH from the Service Mapping Strategy Switch list. Run the BSC6900 MML command LST UCORRMALGOSWITCH to ensure that the HSUPA 2 ms TTI function is enabled. Use an HSPA UE to establish an HSUPA service. The RB SETUP message should show that the service is carried on the E-DCH and the 2 ms TTI is used. Run the BSC6900 MML command SET UCORRMALGOSWITCH to deselect MAP_HSUPA_TTI_2MS_SWITCH from the Service Mapping Strategy Switch list.
----End
Example
//Activating HSUPA 2ms TTI //Set the BSC6900 level swithch SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; Deactivating HSUPA 2ms TTI //Set the BSC6900 level swithch SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0;
7-174
Issue 03 (2010-09-20)
7.91 Configuring HSUPA 2 ms/10 ms TTI Handover

This section describes how to activate and deactivate the optional feature WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover.
Prerequisite
l Dependency on Hardware NodeB requirements The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board,EBOI board, EDLP or EDLPd board. The BBU3806 need to configure EBBC/EBBCd board; the BBU3806C need to configure EBBM board. The BBU3900 need to configure WBBPb/WBBPd board. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010614 HSUPA Phase 2.
Context
WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover supports mobility between 2 ms-TTIcapable cell and 10 ms-TTI-capable cell. Because 2 ms-TTI-capable cells and 10 ms-TTI-capable cells coexist in the network and different TTIs are required for different throughputs, the handover between 2 ms TTI and 10 ms TTI is necessary. This feature can ensure that HSUPA users smoothly move between different cells and resources are allocated to meet throughput requirements. This feature depends on the HSUPA and HSUPA 2ms TTI features. This feature does not need to be activated. It automatically takes effect only if the 2 ms-TTI-capable cells and 10 ms-TTIcapable cells coexist in the network.
Procedure
l Activation Procedure This feature requires a license and does not need to be activated. ----End
Example
//Activating HSUPA 2 ms/10 ms TTI Handover. SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH3=HSUPA_2ms_10ms-1;
7.92 Configuring HSUPA 5.74Mbps per User

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061405 HSUPA 5.74Mbps per User.
Prerequisite
l Dependency on Hardware The BTS3812E, BTS3812A, and BTS3812AE should be configured with the EULP, EBBI, EBOI board. The BBU3806 should be configured with the EBBC board; the BBU3806C should be configured with the EBBM board. The BBU3900 should be configured with the WBBPb board. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the features WRFD-010636 SRB over HSUPA. l l License The license is activated. Other Prerequisites CN support the uplink speed of 5.74Mbps (or more). UE should have the capability of HSDPA Category 6,7,8,9.
Context
This feature enables the HSUPA rate per user at the MAC layer to reach a maximum of 5.74 Mbit/s, which is the HSUPA peak rate defined in 3GPP technical specifications.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable HSUPA services to use the 2 ms TTI. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRBs to be carried on HSPA channels. Use an HSPA-capable UE to establish a PS service on the E-DCH and HS-DSCH. The RB SETUP message shows that the 2 ms TTI is used in the uplink and the maximum channelization code IE indicates 2SF2+2SF4. The real-time monitoring result of "UL Throughput & Bandwidth" on the BSC6900 side shows that bandwidth is 5740 kbit/s. Upload through FTP is normal. l Deactivation Procedure 1. 2. ----End Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the use of the 2 ms TTI on HSUPA channels. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRBs to be carried on DCHs.
Example
//Activating HSUPA 5.74 Mbit/s per user SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; SET UFRCCHLTYPEPARA: SrbChlType=HSPA;
7-176
Issue 03 (2010-09-20)
//Deactivating HSUPA 5.74 Mbit/s per user SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0; SET UFRCCHLTYPEPARA: SrbChlType=DCH;
7.93 Configuring Streaming Traffic Class on HSUPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-010632 Streaming Traffic Class on HSUPA.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package. l License The license is activated.
Context
This feature enables the streaming service to be mapped onto the E-DCH, thus increasing the utilization of cell resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select MAP_PS_STREAM_ON_HSUPA_SWITCH from the Service Mapping Strategy Switch list. Run the BSC6900 MML command SET UFRC to set the rate threshold in the case of the 2 ms TTI. The default value is 384 kbit/s. Run the BSC6900 MML command LST UCORRMALGOSWITCH. Ensure that the streaming service is carried on HSUPA. Establish a PS service. The rb-mappinginfo IE in the RRC_RB_SETUP message on the UU interface should indicate that the PS service is set up. Run the BSC6900 MML command SET UCORRMALGOSWITCH to deselect MAP_PS_STREAM_ON_HSUPA_SWITCH from the Service Mapping Strategy Switch list.
2. l
----End
Example
//Activating Streaming Traffic Class on HSUPA. SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSUPA_SWITCH-1; SET UFRC: StreamHsupa2msTtiRateThs=D384;
Issue 03 (2010-09-20)
7-177
//Verifying Streaming Traffic Class on HSUPA. LST UCORRMALGOSWITCH:; //Deactivating Streaming Traffic Class on HSUPA. SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSUPA_SWITCH-0;

Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the features WRFD-010612 HSUPA Introduction Package, WRFD-010614 HSUPA Phase 2, and WRFD-010636 SRB over HSUPA. l License The license is activated.
Context
This feature enables a single HSUPA cell to support 60 HSUPA users simultaneously. If the number of HSUPA users exceeds 60, the DCH is attempted for service provisioning.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the CELL HSPA admission control function. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate codes for EAGCH and E-RGCH. Run the BSC6900 MML command MOD UCELLCAC to disable the code reservation and set the maximum number of HSUPA users supported by the cell to 60. Click the "Monitor" tab at the top of the BSC6900 LMT. Monitor Navigation Tree is displayed on the left pan. In the "UMTS monitoring", double-click the "Cell performance monitoring". The cell performance monitoring dialog box is displayed. Select "Cell user number" in the Monitor item list. The UEs log in to the FTP server one by one and upload files to the server. The expected result: The PS service is started successfully. The uplink is established on HSUPA. The downlink is established on HSDPA.
2.
If the number of the HSUPA users in the cell exceeds 60, the HSUPA service is degraded to the R99 service to retry admission. l Deactivation Procedure 1. ----End This feature does not need to be deactivated.
Example
//Activating 60 HSUPA Users per Cell //Disabling CELL HSPA admission control MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0; //Enabling SRB over HSPA SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; //Allocating code resources for E-AGCH and E-RGCH MOD UCELLHSUPA: CellId=111, EagchCodeNum=3, ErgchEhichCodeNum=3; //Disabling the code reservation and setting the maximum number of HSUPA users supported by the cell to 60 MOD UCELLCAC: CellId=111, MaxHsupaUserNum=60, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
7.95 Configuring HSUPA over Iur

This section describes how to activate, verify, and deactivate the optional feature WRFD-010635 HSUPA over Iur.
Prerequisite
l l Dependency on Hardware The neighboring RNC should support this feature. Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package. l License The license is activated.
Context
This feature enables HSUPA services to be carried on the Iur interface and provides continuous HSUPA services for UEs moving between RNCs.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command MOD UEXT3GCELL, and set the parameter Cell Capability Container to modify the information about a neighboring RNC cell. Run the BSC6900 MML command MOD UNRNC to set the Iur capability on the local BSC6900, and set the parameter Hsupa cap ind over IUR for NRNC to ON. Ensure the function of the HSUPA over Iur is activated.
Issue 03 (2010-09-20)
Run the BSC6900 MML command LST UNRNC to query the NRNC configuration. Run the BSC6900 MML command LST UEXT3GCELL to query the configuration of NRNC cells. 2. Service Verification The neighboring RNC that configured is supporting HSUPA over Iur function. Establish a HSUPA service on local RNC. Add a path cross-Iur soft handover. The HSUPA IE in the RNSAP_RL_SETUP_REQ message on the Iur interface should indicate that the service is set up. l Deactivation Procedure 1. ----End Run the BSC6900 MML command MOD UNRNC and set the parameter Hsupa cap ind over IUR for NRNC to OFF.
Example
//Activation Procedure MOD UEXT3GCELL: NRncId=2, CellId=2, CellCapContainerFdd=EDCH_SUPPORT-1&EDCH_2SF4_SUPPORT-1&EDCH_HARQ_IR_COMBI N_SUPPORT-1; //Set the Iur interface to support cross-Iur soft handover and PS and CS services, and set the Iur existence indication MOD UNRNC: NRncId=2, SHOTRIG=CS_SHO_SWITCH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, TnlBearerType=IP_TRANS, Dpx=2, IurHsupaSuppInd=ON; //Deactivation Procedure MOD UNRNC: NRNCID=1, IurHsupaSuppInd=OFF
7.96 Configuring SRB over HSUPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-010636 SRB over HSUPA.
Prerequisite
l Dependency on Hardware BSC6900 None NodeB The 38XX series NodeB supports this feature, and the EBBI, EBOI, EULP, EBBC, EBBM is required. The 3900 series NodeB supports this feature, and the WBBPb is required. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package.
Context
This feature enables UL SRBs to be carried over HSUPA. This feature can reduce call delay and save transmission resources.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the Type of Channel Preferably Carrying Signaling RB parameter to HSUPA or HSPA. Run the BSC6900 MML command LST UFRCCHLTYPEPARA to enable the SRB to be carried on HSUPA. Use a HSPA UE to establish a PS service over E-DCH and HS-DSCH. Upload a file with a size larger than 200 MB through FTP. The messages RRC_RRC_CONN_SETUP and RRC_RB_SETUP should include the IEs new-H-RNTI, newPrimary-E-RNTI, srb-InformationSetupList, and Fdpch, where the last two IEs carry the HSPA-associated information. l Deactivation Procedure 1. ----End Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the Type of Channel Preferably Carrying Signaling RB parameter to DCH.
Example
//Activating SRB over HSUPA. SET UFRCCHLTYPEPARA: SrbChlType=HSPA; //Verifying SRB over HSUPA. LST UFRCCHLTYPEPARA: LstFormat=HORIZONTAL; //Deactivating SRB over HSUPA. SET UFRCCHLTYPEPARA: SrbChlType=DCH;
7.97 Configuring Uplink Macro Diversity Intelligent Receiving

This section describes how to activate, verify, and deactivate the optional feature WRFD-010640 Uplink Macro Diversity Intelligent Receiving.
Prerequisite
l l
Issue 03 (2010-09-20)

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion, WRFD-010638 Dynamic CE Resource Management. l License The license is activated.
Context
Based on the resource occupation, this feature enables the dynamic selection of different macro diversity combining modes for high-speed non-real-time services in the uplink and low-speed real-time services (such as SRB and VoIP). This feature can save Iub and Iur transmission resources and CE resources, affect the preemption policy, and improve the investment return.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET URRCTRLSWITCH to turn on the corresponding switch. Run the BSC6900 MML command LST URRCTRLSWITCH to check whether the switch is turned on. Run the BSC6900 MML command SET URRCTRLSWITCH to turn off the switch. For example:
----End
Example
//Activation Procedure SET URRCTRLSWITCH: PROCESSSWITCH=UPLINK_MDC_ENHENCEMENT_SWITCH-1; //Verification Procedure LST URRCTRLSWITCH; Result list format=VERTICAL; //Deactivation Procedure SET URRCTRLSWITCH: PROCESSSWITCH=UPLINK_MDC_ENHENCEMENT_SWITCH-0;
7.98 Configuring HSUPA Adaptive Transmission

This section describes how to activate, verify, and deactivate the optional feature WRFD-010641 HSUPA Adaptive Transmission.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010612 HSUPA Introduction Package. l License The license is activated.
Context
With comprehensive considerations of cell uplink power load, CE resources, and limited uplink coverage, this feature enables the adaptive adjustment of the target number of uplink retransmissions to increase the throughput per user and cell uplink capacity.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the adaptive retransmission switch. Run the NodeB MML command SET ADPRETRANSSWTCH to set the algorithm switch of HSUPA adaptive transmission on the NodeB side. Run the BSC6900 command LST UCORRMALGOSWITCH to check whether the adaptive retransmission switch is turned on. Run the NodeB MML command LST ADPRETRANSSWTCH to check whether the adaptive retransmission switch is turned on. Make the UE establish an HSUPA BE service. Then, check whether the RL Setup message over the Iub interface carries the target number of HSUPA adaptive retransmissions. The expected result: The RL Setup message over the Iub interface carries the target number of HSUPA adaptive retransmissions. Run the BSC6900 command SET UCORRMALGOSWITCH to turn off the adaptive retransmission switch. Run the NodeB MML command SET ADPRETRANSSWTCH to turn off the algorithm switch of HSUPA adaptive transmission on the NodeB side.
----End
Example
//Activating HSUPA Adaptive Transmission SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-1; SET ADPRETRANSSWTCH: SWITCH =OPEN;(NodeB MML command) //Deactivating HSUPA Adaptive Transmission SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-0; SET ADPRETRANSSWTCH: SWITCH=CLOSE;(NodeB MML command)
7.99 Configuring TTI Switch for BE Services Based on Coverage

This section describes how to activate, verify, and deactivate the optional feature WRFD-010690 TTI Switch for BE Services Based on Coverage.
Prerequisite
l Dependency on Hardware None.
Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010614 HSUPA Phase 2.
Context
With this feature, the transmit power of the UE and the uplink service throughput are monitored. The TTI of UEs in the cell center is switched to 2 ms to enhance the service rate, while the TTI of UEs in the cell edge is switched to 10 ms to expand the coverage.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to switch on this feature. In this step, select DRA_BASE_COVER_BE_TTI_RECFG_SWITCH in the Dynamic Resource Allocation Switch parameter. (Optional) If you want to activate this feature after the Uplink Enhanced L2 feature is activated, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH in the Dynamic Resource Allocation Switch parameter.
NOTE
2.
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH takes effect only after DRA_BASE_COVER_BE_TTI_RECFG_SWITCH is selected.
Verification Procedure 1. In the Navigation Tree pane on the LMT, click the Trace tab. In the displayed Trace Navigation Tree pane, double-click UMTS Services. On the expanded list, doubleclick Uu Interface Trace. In the displayed Uu Interface Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG as shown in Figure 7-17 to trace Uu interface signaling messages.
7-184
Issue 03 (2010-09-20)
2.
Check the traced signaling. Figure 7-18 and Figure 7-19 show the transfer of TTI from 2 ms to 10 ms. Figure 7-18 Trace result when TTI is 2 ms
Issue 03 (2010-09-20)
7-185
Figure 7-19 Trace result when TTI is 10 ms
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to switch off this feature. In this step, deselect DRA_BASE_COVER_BE_TTI_RECFG_SWITCH in the Dynamic Resource Allocation Switch parameter.
----End
Example
//Activating TTI Switch for BE Services Based on Coverage SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH-1; //Deactivating TTI Switch for BE Services Based on Coverage SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-0;
7.100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion

This section describes how to activate, verify, and deactivate the optional feature WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion.
Prerequisite
l l l Dependency on Hardware None Dependency on Other Features WRFD-010612 HSUPA Introduction Package License The license is activated.
Context
By monitoring Iub transmission resources, this feature dynamically adjusts the uplink Uu throughput and thus greatly improves resource utilization.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select NODEB_PRIVATE_INTERFACE_SWITCH from the PROCESSSWITCH list.
NOTE
l UE 1 and UE 2 are in idle mode and camp on CELL_ALL. CELL_ALL supports the HSUPA and HSDPA functions. l The bandwidth between the BSC6900 and the NodeB is 2 MHz.
1.
UE 1 and UE 2 that are in HSUPA category 5 are 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, and the same ARP priority is configured. Start the NodeB private interface switch on the BSC6900. On the BSC6900 LMT, start tracing of Uu, Iub, Iu interfaces, UL Throughput Bandwidth, and DL Throughput Bandwidth. Dialing Test Use UE 1 to access the network and initiate an uplink PS service. Record the throughput of the UE. Use UE 2 to access the network and initiate a downlink service. Record the throughput of the two UEs. Terminate the PS service. Expected Result The throughput of UE 1 is stable.
2. 3.
The throughput of the two UEs is stable and their ratio is 1:1. -
Deactivation Procedure 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, deselect NODEB_PRIVATE_INTERFACE_SWITCH from the PROCESSSWITCH list.
----End
Example
//Activation procedure SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; //Deactivation procedure SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-0;
7.101 Configuring Dynamic CE Resource Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-010638 Dynamic CE Resource Management.
Prerequisite
l l l Dependency on Hardware None Dependency on Other Features None License The license is activated.
Context
To improve the utilization efficiency of channel element (CE) resources, Huawei RAN introduces the dynamic CE resource management feature. Based on the Guaranteed Bit Rate (GBR) and the actual rate of an UE, this feature enables the fast adjustment of CE allocation. When CE resources are preempted, this feature enables the proper allocation of CE resources to ensure the preemption equity.
Procedure
l Activation Procedure 1. Enable the license item of this feature through the M2000.
NOTE
l We recommend not activating this feature when the HSUPA DCCC function is enabled. l If this feature and the HSUPA DCCC function are activated at the same time, HSUPA DCCC automatically becomes ineffective. After this feature is deactivated, HSUPA DCCC automatically becomes effective.
Verification Procedure 1. 2. Run the NodeB MML command DSP LICENSE to check that this feature is activated. Check the values of the CE counters for the NodeB. When there are too many HSUPA users, fewer CE resources are assigned after this feature is activated. Run the BSC6900 MML command DEA UCELLHSUPA to deactivate HSUPA for the cell, thus ensuring no HSUPA service is proceeding under the NodeB. Disable the license item of this feature through the M2000. Run the BSC6900 MML command ACT UCELLHSUPA to activate HSUPA again for the cell.
Deactivation Procedure 1. 2. 3.
----End
Example
// Deactivation Procedure // To deactivate HSUPA for a cell, do as follows: DEA UCELLHSUPA: CellId=80; // To activate HSUPA for the cell, do as follows: ACT UCELLHSUPA: CellId=80;
7-188
Issue 03 (2010-09-20)
7.102 Configuring HSPA+ Downlink 28Mbps per User

This section describes how to activate, verify, and deactivate the optional feature WRFD-010680 HSPA+ Downlink 28Mbps per User.
Prerequisite
l Dependency on Hardware BSC6900 None 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 BBU3806C should be configured with the EBBM board. The BBU3900 should be configured with the WBBPb or WBBPd board. For the RF part, the RF module of Huawei Node B supports one TX channel each, and two interconnected RF modules can provide two TX channels to support 2 x 2 MIMO. UE The UE category must support cat16, cat18(or later). l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature: WRFD-010684 2*2 MIMO or WRFD-010696 DC-HSDPA WRFD-010650 HSDPA 13.976Mbps per User l l License The license is activated. Other Prerequisites CN support user rate of 28Mbps or above.
Context
This feature enables the theoretical HSPA+ MIMO rate per user to reach a maximum of 28 Mbit/ s. This feature enhances the user experience for high-speed data services. This feature is dependent on the feature WRFD-010684 22 MIMO.
Procedure
l Activation Procedure The theoretical UE peak rate reaches 28 Mbit/s when the UE services are carried on 22 MIMO and the following conditions are met: 1. Run the BSC6900 MML command SET LICENSE to turn on the license switch for the HSPA+ Downlink 28Mbps per User feature.
Issue 03 (2010-09-20)
2. 3. l
Enable the UE to subscribe to this feature by referring to CN documents. Activate the feature WRFD-010684 2x2 MIMO by referring to 7.108 Configuring 2x2 MIMO. Enable a UE in a 22 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 22 MIMO cell and the RNC establishes services on the 22 MIMO. Run the BSC6900 MML command SET LICENSE to deactivate the associated license.
----End
Example
//Activating HSPA+ Downlink 28Mbps per User. SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN28_PER_USER-1; //Deactivating HSPA+ Downlink 28Mbps per User. SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN28_PER_USER-0;

Prerequisite
l Dependency on Hardware BSC6900 None NodeB The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board, EBOI board or EDLP board. The BBU3806 need to configure EBBC or EBBCd board; the BBU3806C need to configure EBBM board. The BBU3900 need to configure WBBPb or WBBPd board. UE The UE category must support cat 14,18,20,24 or 28. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010683 64QAM, WRFD-010650 HSDPA 13.976 Mbit/s per User. l Other Prerequisites CN support user rate of 21Mbps or above.
Context
This feature enables the theoretical HSPA+ 64QAM rate per user to reach a maximum of 21 Mbit/s. It provides users with high-speed data services. This feature is dependent on the features WRFD-010683 Downlink 64QAM and WRFD-010650 HSDPA 13.976Mbps per User.
Procedure
l Activation Procedure The theoretical UE peak rate reaches 21 Mbit/s when the UE services are carried on 64QAM and the following conditions are met: 1. 2. 3. l Run the BSC6900 MML command SET LICENSE to turn on the license switch for the HSPA+ Downlink 21Mbps per User feature. Enable the UE to subscribe to this feature by referring to CN documents. Activate the feature WRFD-010683 Downlink 64QAM by referring to 7.107 Configuring Downlink 64QAM. Enable a UE in a 64QAM 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 64QAM cell and the RNC establishes services on the 64QAM. Run the BSC6900 MML command SET LICENSE to deactivate the associated license.
----End
Example
//Activating HSPA+ Downlink 21Mbps per User. SET LICENSE: ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN21_PER_USER-1; //Deactivating HSPA+ Downlink 21Mbps per User. SET LICENSE: ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN21_PER_USER-0;
7.104 Configuring Downlink Enhanced L2

This section describes how to activate, verify, and deactivate the optional feature WRFD-010685 Downlink Enhanced L2.
Prerequisite
l l Dependency on Hardware UE should support this feature. Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package. l License The license is activated.
Context
The Downlink Enhanced L2 feature supports flexible Protocol Data Unit (PDU) size, which eliminates the contradictions between the high-speed transmission that requires a large PDU size and the cell-edge coverage that requires a small PDU size. This feature enables the dynamic adjustment of the PDU size. This is to improve the transmission efficiency on the Iub and Uu interfaces and increase the cell-edge throughput and coverage radius. This feature is a prerequisite for the DL 64QAM, 2x2 MIMO, and Enhanced CELL-FACH features.
Procedure
l Activation Procedure 1. (Optional) Run the BSC6900 MML command SET UFRC to set the parameters Cell_DCH DL L2 enhance max PDU size, Cell_DCH UL L2 enhance max RLC PDU size, Cell_DCH UL L2 enhance min RLC PDU size and Cell_FACH L2 enhance max PDU size. Run the BSC6900 MML command MOD UCELLALGOSWITCH to select DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch) and UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch) from the Cell Hspa Plus function switch list. Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 7-20. Figure 7-20 Uu Interface Tracing dialog box
2.
2.
Establish an HSDPA 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. View the dl-RLC-PDU-Size IE in the RRC_RB_SETUP message.
3.
7-192
If the dl-RLC-PDU-Size IE is set to flexibleSize as shown in Figure 7-21, you can infer that this feature has been activated. If the dl-RLC-PDU-Size IE is set to fixedSize, you can infer that this feature has not been activated. Figure 7-21 Viewing dl-RLC-PDU-Size IE
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to deselect DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch) and UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch) from the Cell Hspa Plus function switch list.
----End
Example
//Activating Downlink Enhanced L2 MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-1&UL_L2ENHANCED-1; //Deactivating Downlink Enhanced L2 MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-0&UL_L2ENHANCED-0;
7.105 Configuring Enhanced CELL-FACH

This section describes how to activate, verify, and deactivate the optional feature WRFD-010688 Enhanced CELL-FACH.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010685 Downlink Enhanced L2. l License The license is activated.
Other Prerequisites The UE should 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 Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to select E_FACH and DL_L2ENHANCED from the drop-down list Cell Hspa Plus function switch. Run the BSC6900 MML command ADD UCELLEFACH to add enhanced CELL_FACH state parameters of a cell. Run the BSC6900 MML command ACT UCELLEFACH to activate this feature. Run the BSC6900 MML command DSP UCELL to check whether EFACH is available. Run the BSC6900 MML command MOD UCELLALGOSWITCH to clear E_FACH and DL_L2ENHANCED from the drop-down list Cell Hspa Plus function switch. Run the BSC6900 MML command DEA UCELLEFACH to deactivate this feature.
2. 3. l 1. l
2. ----End
Example
//Activating Enhanced CELL-FACH MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_FACH-1&DL_L2ENHANCED-1; ADD UCELLEFACH: CellId=11; ACT UCELLEFACH: CellId=11; //Deactivating Enhanced CELL-FACH MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_FACH-0&DL_L2ENHANCED-0; DEA UCELLEFACH: CellId=11;

Prerequisite
l Dependency on Hardware The BSC6900 is configured with the DPUe board. On the NodeB side: The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board.

NOTE
The BBU3806C that is configured with the EBBM board supports the HSPA+ Downlink 42Mbps per User feature only in 64QAM+DC HSDPA mode, rather than in 2x2 MIMO +64QAM mode.
The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI or EDLP board. The BBU3900 is configured with the WBBPb or WBBPd board. To enable the 2x2 MIMO feature, configure either two interconnected RF modules with one Tx channel or one RF module with two Tx channels. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the following features: WRFD-010681 HSPA+ Downlink 21Mbps per User, WRFD-010696 DC-HSDPA, and WRFD-010612 HSUPA Introduction Package. Or WRFD-010681 HSPA+ Downlink 21Mbps per User, WRFD-010680 HSPA+ Downlink 28Mbps per User, WRFD-010693 DL 64QAM+MIMO, and WRFD-010612 HSUPA Introduction Package. l l l License The license is activated. The UE must belong to categories 20 to 24 as defined in 3GPP specifications. The CN needs to support the RAB assignment with the relate data rate.
Context
According to 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.
NOTE
If the 2x2 MIMO, 64QAM, and DC-HSDPA features have been activated on the NodeB, you only need to configure data on the BSC6900 to activate the HSPA+ Downlink 42Mbps per User feature.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET LICENSE. In this step, set Function Switch5 to HSPA+ Downlink 42 Mbit/s per User. On the HLR, set the BE service rate for UEs. Enable a UE in an HSDPA 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 HSDPA cell and the BSC6900 establishes services on the HS-DSCH. Run the BSC6900 MML command SET LICENSE. In this step, deselect HSPA+ Downlink 42 Mbit/s per User from Function Switch5.
----End
Example
//Activating HSPA+ Downlink 42Mbps per User SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH5=EHSPA_42M_DL-1; //Deactivating HSPA+ Downlink 42Mbps per User SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH5=EHSPA_42M_DL-0;
7.107 Configuring Downlink 64QAM

This section describes how to activate, verify, and deactivate the optional feature WRFD-010683 Downlink 64QAM.
Prerequisite
l Dependency on Hardware The BTS3812E, BTS3812A and BTS3812AE need to configure EBBI board, EBOI board or EDLP board. The BBU3806 need to configure EBBC,EBBCd board; the BBU3806C need to configure EBBM board. The BBU3900 need to configure WBBPb,WBBPd board. l Dependency on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010685 Downlink Enhanced L2 WRFD-010629 DL 16QAM modulation l l License The license is activated. Others The UE category must support 64QAM. That is, the UE must belong to category 13, 14, 17, 18, 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 Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select CFG_HSDPA_64QAM_SWITCH from the Channel Configuration Strategy Switch list. Optional: Run the BSC6900 MML command SET UFRC to configure preferential use of 64QAM. In this step, set Preferred MIMO or 64QAM character to 64QAM.
2.
7-196

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.
Run the BSC6900 MML command MOD UCELLALGOSWITCH 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. As Figure 7-22 shows, start Uu interface tracing on the BSC6900 LMT. Figure 7-22 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. 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 7-23 shows, you can infer that this feature has been activated. Otherwise, you can infer that this feature has not been activated.
3.
Issue 03 (2010-09-20)
7-197
Figure 7-23 Checking the dl-64QAM-Configured information element
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect 64QAM(Cell 64QAM Function Switch) from the Cell Hspa Plus function switch list.
----End
Example
// Activation procedure // To set Channel Configuration Strategy Switch, run the following command: SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1; // To activate Downlink 64QAM, run the following command: SET UFRC: MIMOor64QAMSwitch=64QAM; // To turn on the cell-level 64QAM switch and enhanced downlink layer 2 function switch, run the following command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-1&DL_L2ENHANCED-1; // Deactivation procedure // To modify Cell Hspa Plus function switch, run the following command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-0;
7.108 Configuring 2x2 MIMO

This section describes how to activate, verify, and deactivate the optional feature WRFD-010684 2x2 MIMO.
Prerequisite
l Dependency on Hardware The BTS3812E/BTS3812A and BTS3812AE are separately configured with the EBBI, EBOI, and EDLP board. The EBBC board is configured for the BBU3806. In the case of the BBU3900, the WBBPb board is configured. The RRU3801C, RRU3804, RRU3808, and WRFU support the VAM and PSP functions. The MTRU does not support the VAM function.
NOTE
The VAM and PSP functions need to be supported when MIMO and HSDPA are used together.
Dependency on Other Features WRFD-010610 HSDPA Introduction Package
7-198
Issue 03 (2010-09-20)
WRFD-010685 Downlink Enhanced L2 l l License The license is activated. Others The BSC6900 software version must be RAN11.0 or later. The NodeB software version must be RAN11.0 or later. The UE must be of a type that supports 2x2 MIMO. To be more precise, the UE must belong in category 15, 16, 17, or 18, as defined in 3GPP specifications. For the MIMO hardware configuration scheme, see the 2x2 MIMO Configuration section in the NodeB Technical Description.
Context
CAUTION
You must activate this feature when the traffic volume in the cell is low. Before this feature can be activated, the cell must be deactivated. After the cell is deactivated, the services in this cell are disrupted. MIMO is a multi-antenna technology, in which multiple antennas receive and transmit data. In this way, the data transmission rate is increased. The 2x2 MIMO function was introduced in 3GPP Release 7. With the 2x2 MIMO function, the NodeB uses two antennas to transmit data and the UE uses two antennas to receive data. After the introduction of this 2x2 MIMO function, the theoretical peak rate of HSDPA users increases from 14 Mbit/s to 28 Mbit/s. Data Planning Parameter Site No. RRU Chain No. RRU Inserted Position Sector No. Local Cell ID Cell ID Example 0 0 1 2 1 1 Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-level MIMO switch. In this step, select CFG_HSDPA_MIMO_SWITCH from the Channel Configuration Strategy Switch list. Run the BSC6900 MML command SET UFRC. In this step, set Preferred MIMO or 64QAM character to MIMO to configure that MIMO is selected preferentially.
2.
Issue 03 (2010-09-20)

NOTE
l For UEs to 3GPP R7 specifications, MIMO and 64QAM cannot be used together. l If Preferred MIMO or 64QAM character is set to MIMO, MIMO is preferentially configured for the UE. l Before verifying the feature, you need to set Preferred MIMO or 64QAM character to MIMO. After the verification, you can set the parameter according to the actual network planning.
3.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to turn on the cell-level MIMO switch and enhanced layer 2 switch. In this step, select MIMO(Cell MIMO Function Switch) and L2ENHANCED(Cell L2ENHANCED Function Switch) from the Cell Hspa Plus function switch list. Run the BSC6900 MML command DEA UCELL to deactivate the HSDPA cell. Configure related data on the NodeB according to the MIMO hardware configuration scheme. The following content takes the RRU3804 as an example to describe how to configure data for the change from one RRU to two cascaded RRUs. (1) Run the NodeB MML command ADD RRUCHAIN to add an RRU chain. (2) Run the NodeB MML command ADD RRU to add RRUs to the chain.
4. 5.
6.
On the NodeB side, modify the Diversity Mode of the sector and the Two Tx Way and VAM of the cell. (1) Run the NodeB MML command RMV LOCELL to remove the local cell. (2) Run the NodeB MML command RMV SEC to remove the sector. (3) Run the NodeB MML command ADD SEC to add a sector. In this step, set Diversity Mode to COMMON_MODE(COMMON MODE) and configure the antenna data in line with the MIMO hardware deployment scheme. (4) Run the NodeB MML command ADD LOCELL to add a local cell. In this step, set both Two Tx Way and VAM to TRUE and configure the antenna data in line with the MIMO hardware deployment scheme.
7. 8.
Run the NodeB MML command SET MACHSPARA to set the IIC switch to OPEN. Configure the PSP funtion on the BSC6900 side. Run the MML command MOD UCELLSETUP. In this step, set TX diversity indication to FALSE. Run the MML command ADD USCPICH to add a secondary common pilot channel (SCPICH).
9.
Run the BSC6900 MML command ACT UCELL to activate the cell.
10. Run the BSC6900 MML command ACT UCELLMIMO to activate the parameters configured for the MIMO feature in the cell. l Verification Procedure 1. As Figure 7-24 shows, start Uu interface tracing on the BSC6900 LMT.
7-200
Issue 03 (2010-09-20)
Figure 7-24 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. Check whether the RRC_RB_SETUP message contains the mimoParameters information element. If the RRC_RB_SETUP message contains the mimoParameters information element, as Figure 7-25 shows, you can infer that this feature has been activated. If the RRC_RB_SETUP message does not contain the mimoParameters information element, you can infer that this feature has not been activated. Figure 7-25 Checking the mimoParameters information element
3.
Deactivation Procedure 1. Run the BSC6900 MML command DEA UCELLMIMO to deactivate the parameters configured for the feature.
Issue 03 (2010-09-20)
2.
Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, clear MIMO(Cell MIMO Function Switch) from the Cell Hspa Plus function switch list.
----End
Example
//Activation procedure //Configuring the BSC6900 //Turning on the BSC6900-level MIMO switch SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-1; //Configuring preferential use of MIMO SET UFRC: MIMOor64QAMSwitch=MIMO; //Turning on the cell-level MIMO switch and enhanced layer 2 switch MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch= MIMO-1&L2ENHANCED-1; //Deactivating the HSDPA cell DEA UCELL: CellId=1; //Configuring the NodeB //Adding a RRU to the chain ADD RRU: SRN=61, TP=TRUNK, RCN=0, PS=1, RT=MRRU; //Removing the local cell and the sector RMV LOCELL: LOCELL=1; RMV SEC: STN=0, SECN=2; //Adding a sector and setting the diversity mode ADD SEC: STN=0, SECN=2, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE, ANT1SRN=60, ANT1N=R0A, ANT2SRN=61, ANT2N=R0A; //Adding a local cell and setting Two Tx Way and VAM ADD LOCELL: LOCELL=0, STN=0, SECN=2, SECT=REMOTE_SECTOR, TTW=TRUE, SRN1=60, SRN2=61, SN2=0, ANT2N=ANTA, ULFREQ=9845, DLFREQ=10795, MXPWR=460, HISPM=FALSE, RMTCM=FALSE, VAM=TRUE; //Turing on the IIC switch SET MACHSPARA: IICSW=Open; //Configuring the BSC6900 //Configuring the PSP funtion MOD UCELLSETUP: CellId=01, TxDiversityInd=FALSE; ADD USCPICH: CellId=01, ScpichPhyId=5, ScpichPower=0; //Activating the cell ACT UCELL: CellId=1; //Activating the parameters configured for the MIMO feature ACT UCELLMIMO: CellId=1;
7.109 Configuring Downlink 64QAM+MIMO

This section describes how to activate, verify, and deactivate the optional feature WRFD-010693 DL 64QAM+MIMO.
Prerequisite
l Dependency on Hardware In the case of the 3900 series base station, the WBBPb1, WBBPb2, WBBPb3, WBBPb4, WBBPd1, or WBBPd2 board needs to be 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. l Dependency on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010685 Downlink Enhanced L2 WRFD-010684 22 MIMO WRFD-010683 Downlink 64 QAM l l License The license is activated. Others The CN supports 3GPP Release 8. The BSC6900 software version should be not earlier than RAN12.0. The NodeB software version should be not earlier than RAN12.0. The UE must belong in HS-DSCH category 19 or 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. With 64QAM+MIMO, the peak throughput of a single user can reach 42Mbit/s, compared to 28Mbit/s with 16QAM+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 Local Cell ID Cell ID DL streaming traffic threshold on HSDPA DL BE traffic threshold on HSDPA Example 1 1 D64 D64 Source Network planning Network planning Network planning Network planning
Procedure
l Activation Procedure 1. Run the NodeB MML command MOD LOCELL to modify a local cell. In this step, set DL 64QAM MIMO to TRUE.
Issue 03 (2010-09-20)
2.
Run the BSC6900 MML command SET UCORRMALGOSWITCH 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. Run the BSC6900 MML command SET UFRC to configure preferential use of 64QAM+MIMO. In this step, select MIMO_64QAM from the Prefered MIMO_64QAM or DC_HSDPA character list. Optional: If the streaming service needs to use HSDPA, run the BSC6900 MML commandSET UCORRMALGOSWITCH. In this step, select MAP_PS_STREAM_ON_HSDPA_SWITCH from the Service Mapping Strategy Switch list. Optional: Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set DL streaming traffic threshold on HSDPA and DL BE traffic threshold on HSDPA according to the actual network planning. Run the BSC6900 MML command MOD UCELLALGOSWITCH 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. 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. Run the BSC6900 MML command LST UCELLALGOSWITCH to verify the configuration result of the cell algorithm switch. Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify the configuration result of the connection-oriented algorithm switch. Run the BSC6900 MML command DSP UCELLCHK to check that the cell supports 64QAM+MIMO. Run the BSC6900 MML command MOD UCELLALGOSWITCH 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. Run the BSC6900 MML command SET UCORRMALGOSWITCH 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.
3.
4.
5.
6.
2. 3. 4. l
2.
----End
Example
// Activation procedure // To modify a local cell with Downlink 64QAM+MIMO, run the following command: MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, DL64QAM_MIMO=TRUE; // To turn on the switches for the algorithms of 64QAM+MIMO, 64QAM, and MIMO, run the following command: SET UCORRMALGOSWITCH:
7-204
Issue 03 (2010-09-20)
CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1&CFG_HSDPA_MIMO _WITH_64QAM_SWITCH-1; // To preferentially use 64QAM+MIMO, run the following command: SET UFRC: MIMO64QAMorDCHSDPASwitch=MIMO_64QAM; // To turn on the algorithm switch for the streaming services carried on HSDPA, run the following command: SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; // To set HSDPA thresholds for the DL streaming service and the DL BE service, run the following command: SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; // To modify cell algorithm switch: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-1&MIMO-1&DL_L2ENHANCED-1&64QAM_MIMO-1; // Verification procedure // To query the configuration information of the local cell, run the following command: LST LOCELL: MODE=LOCALCELL, LOCELL=1; // To verify the configuration result of the cell algorithm switch, run the following command: LST UCELLALGOSWITCH:CellId=1; // To verify the configuration result of the connection-oriented algorithm switch, run the following command: LST UCORRMALGOSWITCH: LstFormat=VERTICAL; // To check that the cell supports 64QAM+MIMO, run the following command: DSP UCELLCHK:CellId=1; // Deactivation procedure // To turn off the cell-level 64QAM+MIMO switch, run the following command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM_MIMO-0; // To turn off the BSC6900-level 64QAM+MIMO switch, run the following command: SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_WITH_64QAM_SWITCH-0;
7.110 Configuring CPC - DTX / DRX

This section describes how to activate, verify, and deactivate the optional feature WRFD-010686 CPC-DTX/DRX.
Prerequisite
l Dependency on Hardware For the BTS3812E, BTS3812A and BTS3812AE, the EBBI, EBOI, EULP/EULPd (supporting uplink DTX), and EDLP (supporting downlink DRX) should be configured. For the BBU3806, the EBBC/EBBCd should be configured. For the BBU3806C, the EBBM should be configured. For the BBU3900, the WBBPb/WBBPd should be configured. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010636 SRB over HSUPA, WRFD-010652 SRB over HSDPA. l l
Issue 03 (2010-09-20)
License The license is activated. Other Prerequisites

The UE must be Release-7 (or later) to support this feature.
Context
This feature is related to uplink DTX and downlink DRX. This feature can reduce the interference between UEs and improve the HSPA+ user capacity per cell.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCELLALGOSWITCH to select DTX_DRX from the drop-down list of Cell Hspa Plus function switch.
NOTE
If the information that the cell algorithm switches has been added is displayed after the ADD UCELLALGOSWITCH command is executed, run the BSC6900 MML command MOD UCELLALGOSWITCH to set Cell Hspa Plus function switch to DTX_DRX(Cell DTX_DRX Function Switch).
2.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on CFG_HSPA_DTX_DRX_SWITCH through Channel Configuration Strategy Switch. Initiate Uu interface tracing on the BSC6900 LMT, as shown in the Figure 7-26. Figure 7-26 Uu Interface Tracing dialog box
2. 3.
Use an HSPA-capable UE to establish a new service. Check whether the following IEs are included in the RRC_RB_SETUP message, as shown in the Figure 7-26.
7-206
Issue 03 (2010-09-20)
Figure 7-27 IE Information
dtx-drx-TimingInfo dtx-drx-Info l Deactivation Procedure 1. ----End Run the BSC6900 MML command MOD UCELLALGOSWITCH to clear DTX_DRX from the drop-down list Cell Hspa Plus function switch.
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;
7.111 Configuring CPC-HS-SCCH Less Operation

This section describes how to activate, verify, and deactivate the optional feature WRFD-010687 CPC-HS-SCCH Less operation.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010652 SRB over HSDPA, WRFD-010636 SRB over HSUPA. l l License The license is activated. 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 Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select CFG_HSPA_HSSCCH_LESS_OP_SWITCH in the Channel configuration strategy switch parameter to switch on the HS-SCCH less operation function. Run the BSC6900 MML command ADD UCELLALGOSWITCH. In this step, select HS_SCCH_LESS_OPERATION in the Cell Hspa Plus function switch parameter to activate the HS-SCCH less operation function at the cell level. Use an HSPA-supportive UE to initiate a PS service. The service is carried on E-DCH and HS-DSCH. Sunch as upload a file (larger than 200 MB) to the FTP server to initiate data transfer.
NOTE
2.
How to make the service on E-DCH and HS-DSCH, see section 7.60 Configuring HSDPA 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 the figureFigure 7-28. Figure 7-28 RRC_RB_SETUP Information
l
7-208
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect CFG_HSPA_HSSCCH_LESS_OP_SWITCH in the Channel configuration strategy switch parameter to switch off the HS-SCCH less operation function. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect HS_SCCH_LESS_OPERATION in the Cell Hspa Plus function switch parameter to deactivate the HS-SCCH less operation function at the cell level.
2.
----End
Example
//Activating CPC-HS-SCCH Less operation SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_HSSCCH_LESS_OP_SWITCH-1; ADD UCELLALGOSWITCH: CellId=0, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST, 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;
7.112 Configuring 96 HSDPA Users per Cell

This section describes how to activate, verify, and deactivate the optional feature WRFD-010653 96 HSDPA Users per Cell.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the features WRFD-010623 64 HSDPA Users per Cell and WRFD-010686 CPC - DTX/DRX. l License The license is activated.
Context
This feature enables a single HSDPA cell to simultaneously support 96 HSDPA VoIP or other low-rate users.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the CELL HSPA admission control function and enable the DTX-DRX. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HSPA state transition. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA.
Issue 03 (2010-09-20)
4.
Run the BSC6900 MML command MOD UCELLCAC to disable the code reservation and set the maximum number of HSDPA users supported by the cell to 96. Click "Monitor" tab at the top of the BSC6900 LMT. Monitor Navigation Tree is displayed on the left pan. In the "UMTS monitoring", double-click the "Cell performance monitoring". The cell performance monitoring dialog box is displayed. Select "Cell user number" in the Monitor item list. The UEs log in to the FTP server one by one and upload files to the server. The expected result: The PS service started successfully, the uplink is established on HSUPA, and the downlink is established on HSDPA. If the number of the HSDPA users in the cell exceeds 96, the HSDPA service is degraded to the R99 service to retry admission.
2.
----End
Example
//Activating 96 HSDPA Users per Cell MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=96, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;

Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010634 60 HSUPA Users per Cell and WRFD-010653 96 HSDPA Users per Cell. l License The license is activated.
7-210
Issue 03 (2010-09-20)
Context
This feature enables a single HSUPA cell to simultaneously support 96 HSUPA VoIP or other low-rate users. This feature can increase the capacity of voice services or other low-rate services per cell.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the CELL HSPA admission control function and enable the DTX-DRX. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HSPA state transition. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate codes for EAGCH and E-RGCH. Run the BSC6900 MML command MOD UCELLCAC to disable the code reservation and set the maximum number of HSUPA users supported by the cell to 96. Click the "Monitor" tab at the top of the BSC6900 LMT. Monitor Navigation Tree is displayed on the left pan. In the "UMTS monitoring", double-click the "Cell performance monitoring". The cell performance monitoring dialog box is displayed. Select "Cell user number" in the Monitor item list. The UEs log in to the FTP server one by one and upload files to the server. The expected result: The PS service started successfully, the uplink is established on HSUPA, and the downlink is established on HSDPA. If the number of the HSUPA users in the cell exceeds 96, the HSUPA service is degraded to the R99 service to retry admission. l Deactivation Procedure 1. ----End This feature does not need to be deactivated.
2.
Example
//Activating 96 HSUPA Users per Cell MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; MOD UCELLHSUPA: CellId=111, EagchCodeNum=5, ErgchEhichCodeNum=3; MOD UCELLCAC: CellId=111, MaxHsupaUserNum=96, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF ;
Issue 03 (2010-09-20)
7-211
7.114 Configuring 128 HSDPA Users per Cell

This section describes how to activate, verify, and deactivate the optional feature WRFD-010654 128 HSDPA Users per Cell.
Prerequisite
l Dependency on Hardware The 3900 series base station is configured with the WBBPd2 board. Note that only 3900 series base stations support this feature. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010653 96 HSDPA Users per Cell and WRFD-010670 128 HSUPA Users per Cell. l License The license is activated.
Context
This feature increases the capacity of a single cell for voice services so that this cell serves more VoIP-enabled or low-rate users. This feature has a greater impact on cells with low user rate and a large number of users. In the case of VoIP services or other low-rate services, a single cell supports a maximum of 128 HSDPA users. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the CELL HSPA admission control function and enable the DTX-DRX. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HSPA state transition. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLCAC to disable the code reservation and set the maximum number of HSDPA users supported by the cell to 128. Click "Monitor" tab in the top of the BSC6900 LMT. Monitor Navigation Tree is displyed on the left pan. In the "UMTS monitoring", double click the "Cell performance monitoring". The cell performance monitoring dialog box is displayed. Select "Cell user number" in the Monitor item list. The UEs log in to the FTP server one by one and upload files to the server. The expected result: The PS service started successfully, the uplink is established on HSUPA, and the downlink is established on HSDPA.
2.
If the number of the HSDPA users in the cell exceeds 128, the HSDPA service is degraded to R99 service to retry admission. 3. View the maximum number of users through the counter VS.HSDPA.UE.Max.Cell on the M2000.
NOTE
The 128 HSDPA users mentioned in this feature are SRB Over HSDPA users.
----End
Example
//Activating 128 HSDPA Users per Cell MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=128, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;

Prerequisite
l Dependency on Hardware The 3900 series base station is configured with the WBBPd2 board. Note that only 3900 series base stations support this feature. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010639 96 HSUPA Users per Cell and WRFD-010654 128 HSDPA Users per Cell. l License The license is activated.
Context
This feature increases the capacity of a single cell for voice services so that this cell serves more VoIP-enabled or low-rate users. In the case of VoIP services or other low-rate services, a single cell supports a maximum of 128 HSUPA users. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
l
Issue 03 (2010-09-20)
1. 2. 3. 4. 5.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the CELL HSPA admission control function and enable the DTX-DRX. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HSPA state transition. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate codes for EAGCH and E-RGCH. Run the BSC6900 MML command MOD UCELLCAC to disable the code reservation and set the maximum number of HSUPA users supported by the cell to 128. Click "Monitor" tab in the top of the BSC6900 LMT. Monitor Navigation Tree is displyed on the left pan. In the "UMTS monitoring", double click the "Cell performance monitoring". The cell performance monitoring dialog box is displayed. Select "Cell user number" in the Monitor item list. The UEs log in to the FTP server one by one and upload files to the server. Expected result: The PS service started successfully, the uplink is established on HSUPA, and the downlink is established on HSDPA. If the number of the HSUPA users in the cell exceeds 128, the HSUPA service is degraded to R99 service to retry admission.
2.
3.
View the maximum number of users through the performance measurement counter VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
The 128 HSUPA users mentioned in this feature are SRB Over HSUPA users.
----End
Example
//Activating 128 HSUPA Users per Cell MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; MOD UCELLHSUPA: CellId=111, EagchCodeNum=5, ErgchEhichCodeNum=3; MOD UCELLCAC: CellId=111, MaxHsupaUserNum=128, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
7.116 Configuring HSUPA UL Interference Cancellation

This section describes how to activate, verify, and deactivate the optional feature WRFD-010691 HSUPA UL Interference Cancellation.
Prerequisite
l Dependency on Hardware In the case of the DBS3800, the EBBCd board needs to be configured. In the case of the BTS3812E or BTS3812AE, the EULPd board needs to be configured. In the case of the 3900 series base station, the WBBPb board needs to be configured. l l l Dependency on Other Features WRFD-010612 HSUPA Introduction Package. License The license is activated. Others The NodeB software version should be not earlier than RAN12.0. The BSC6900 software version should be not earlier than RAN12.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, thus 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 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. Therefore, cell of the group can support the IC feature. For details, see 5.3.5 Adding the Board to 3900 Series Base Stations. 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 5.3.3 Adding the EBBC/EBBCd Board. 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 5.3.1 Adding the Board to the BTS3812E/BTS3812AE.
Procedure
l Activation Procedure 1. 2. 3.
Issue 03 (2010-09-20)
If the UMTS cell has been activated, run the BSC6900 MML command DEA UCELL to deactivate the cell. Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set IC_MODE to TRUE. Run the BSC6900 MML command ACT UCELL to activate the cell.
Verification Procedure You can use the following methods to verify this feature. 1. 2. Verifying the status of the HSUPA uplink interference cancellation switch Run the NodeB MML command DSP LOCELL to list the configuration information of the local cells. The execution result is displayed on the LMT. If the value of IC_MODE is TRUE, you can infer that this feature has been activated. If the value of IC_MODE is FALSE, you can infer that this feature has not been activated. Verifying the license status Run the NodeB MML command DSP LICENSE to query the information about the license.
NOTE
1.
The execution result is displayed on the LMT. The Local Cell Number Support IC parameter indicates the maximum number of cells supporting IC.
Deactivation Procedure 1. Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set IC_MODE to FALSE.
----End
Example
//Deactivating a cell DEA UCELL: CellId=1; //Modifying the local cell MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, IC_MODE=TRUE; //Activating the cell ACT UCELL: CellId=1; //Verifying the status of the HSUPA uplink interference cancellation switch DSP LOCELL: MODE=LOCALCELL, LOCELL=1; //Verifying the license status DSP LICENSE:; //Deactivation Procedure //Modifying the local cell MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, IC_MODE=FALSE;
7.117 Configuring HSUPA Frequency Domain Equalization

This section describes how to activate, verify, and deactivate the optional feature HSUPA Frequency Domain Equalization.
Prerequisite
l Dependency on Hardware In the case of the 3900 series base stations, the WBBPd 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. When configured with EBBI/EDLP+EULPd, the base station can support HSUPA frequency domain equalization (FDE). In this case, the EULPd board must be
included in the uplink resource group, and the downlink resource group must be set up on the EBBI or EDLP board. When configured with HBBI/HDLP+EULPd, the base station does not support HSUPA FDE. l l l Dependency on Other Features WRFD-010612 HSUPA Introduction Package. License The license is activated. Others The BSC6900 software version should be not earlier than RAN12.0. The NodeB software version should be not earlier than RAN12.0. The UEs must belong in E-DCH categories 1 to 7, as specified by the 3GPP specifications.
Context
HSUPA FDE equalizes the spectrum in the frequency domain on the HSUPA E-DPDCH through the UL receiver of the NodeB, thus suppressing the inter-path interference on the E-DPDCH. 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 multi-path environment.
NOTE
For UEs of category 6 and category 7 at a transmission rate higher than 2 Mbit/s, significant gain can be achieved through HSUPA FDE.
Procedure
l Activation Procedure 1. l Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set FDE_MODE to TRUE.
Verification Procedure The following two methods can be used to verify whether HSUPA FDE is activated. 1. To verify that the HSUPA FDE switch is turned on: Run the NodeB MML command DSP LOCELL to query the configuration information about the local cell. Set Query Mode to LOCALCELL(Query Localcell by ID). Specify Local Cell ID. 2. The execution result is displayed on the LMT. If FDE_MODE is TRUE, you can infer that the feature is activated. If FDE_MODE to FALSE, you can infer that the feature is not activated. To verify that the license function is activated: Run the NodeB MML command DSP LICENSE to query the information about the license. The execution result is displayed on the LMT. Number of Local Cells Supporting FDE indicates the maximum number of cells supporting HSUPA FDE under the NodeB.
1. 2.
Issue 03 (2010-09-20)
Deactivation Procedure 1. Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set FDE_MODE to FALSE.
----End
Example
// Activation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, FDE_MODE=TRUE; // Verification procedure DSP LOCELL: MODE=LOCALCELL, LOCELL=1; // Deactivation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, FDE_MODE=FALSE;
7.118 Configuring Uplink 16QAM

This section describes how to activate, verify, and deactivate the optional feature WRFD-010694 Uplink 16QAM.
Prerequisite
l Dependency on Hardware In the case of the 3900 series base station, the WBBPd1 or WBBPd2 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 and EBBI/EDLP boards need 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. l Dependency on Other Features WRFD-010612 HSUPA Introduction Package WRFD-010652 SRB over HSDPA WRFD-01061403 HSUPA 2ms TTI l l License The license is activated. Others The CN supports the "peak rate per user" introduced by UL 16QAM. The BSC6900 software version should be not earlier than RAN12.0. The NodeB software version should be not earlier than RAN12.0. The UE must belong in E-DCH category 7, as specified by the 3GPP specifications.
Context
l 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.
7-218
Procedure
l Activation Procedure 1. l Run the NodeB MML command MOD LOCELL to modify a local cell. In this step, set UL 16QAM to TRUE. Run the NodeB MML command LST LOCELL to query the configuration information of the local cell. Set Query Mode to LOCALCELL(Query Localcell by ID). Specify Local Cell ID. 2. As Figure 7-29 shows, start Uu interface tracing on the BSC6900 LMT. Figure 7-29 Uu Interface tracing
3. 4.
Use the UE to perform a dialing test of the PS service. Ensure that an HSUPA service is established. 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 7-30, 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 03 (2010-09-20)
7-219
Figure 7-30 Indication of uplink 16QAM
Deactivation Procedure 1. Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set UL_16QAM to FALSE.
----End
Example
// Activation procedure // To configure a local cell, run the following command: MOD LOCELL: LOCELL=1, UL_16QAM=TRUE; // Verification procedure // To query the configuration information of the local cell, run the following command: LST LOCELL: MODE=LOCALCELL, LOCELL=1; // Deactivation procedure // To modify the local cell, run the following command: MOD LOCELL: LOCELL=1, UL_16QAM=FALSE;
7.119 Configuring UL Layer 2 Improvement

This section describes how to activate, verify, and deactivate the optional feature WRFD-010695 UL Layer 2 Improvement.
Prerequisite
l Dependency on Hardware In the case of the BTS3900, BTS3900A, or DBS3900, the WBBPb board (WBBPb1, WBBPb2, WBBPb3, or WBBPb4) or the WBBPd board (WBBPd1 or WBBPd2) needs to be configured. In the case of the DBS3800, BBU3806+EBBC or BBU3806+EBBCd need to be configured. In the case of the BTS3812E or BTS3812AE, the EBBI, EDLP, or EULP (or EULPd) board needs to be configured. l Dependency on Other Features The BSC6900 software version should be not earlier than RAN12.0. The NodeB software version should be not earlier than RAN12.0.
The UE supports UL Layer 2 Improvement. WRFD-010612 HSUPA Introduction Package l License The license is activated.
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 When the UE is located at the cell edge, data is transmitted in a small PDU size, thus reducing the bit error rate (BER) caused by power limitation and improving the data transmission efficiency. When the UE is located in the cell center, data is transmitted in a large PDU size, thus 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
l Activation Procedure 1. Optional: Run the BSC6900 MML command SET UFRC to set theBSC6900-level parameters related to UL Layer 2 Improvement. In this step, set Cell_DCH UL L2 enhance max RLC PDU size and Cell_DCH UL L2 enhance min RLC PDU size.
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 under the BSC6900.
2.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to turn on the cell-level switch for UL Layer 2 Improvement. In this step, select UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch) from the Cell Hspa Plus function switch list. Run the NodeB MML command MOD LOCELL to turn on the cell-level switch for UL Layer 2 Improvement. In this step, set UL_L2+ to TRUE. As Figure 7-31 shows, start Uu interface tracing on the BSC6900 LMT.
3. l
Issue 03 (2010-09-20)
7-221
Figure 7-31 Uu Interface tracing
2.
Use the UE to perform a dialing test of the PS service. Ensure that an HSUPA service is established.
NOTE
The type of services that use this feature is limited by the HSUPA rate threshold.
3.
In the Uu interface trace data, view the rlc-PDU-Size information element (IE) in the RRC_RB_SETUP message. If the rlc-PDU-Size IE is flexibleSize as shown in Figure 7-32, you can infer that this feature has been activated. If the rlc-PDU-Size IE is fixedSize, you can infer that this feature has not been activated. Figure 7-32 Viewing the rlc-PDU-Size IE
7-222
Issue 03 (2010-09-20)
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to turn off the cell-level switch for UL Layer 2 Improvement. In this step, deselect UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch) from the Cell Hspa Plus function switch list. Run the NodeB MML command MOD LOCELL to turn off the cell-level switch for UL Layer 2 Improvement. In this step, set UL_L2+ to FALSE.
2. ----End
Example
// Activation procedure // To turn on the cell-level switch for UL Layer 2 Improvement, run the following BSC6900 MML command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_L2ENHANCED-1; // To turn on the cell-level switch for UL Layer 2 Improvement, run the following NodeB MML command: MOD LOCELL: CellId=1, UL_L2+=TRUE; // Deactivation procedure // To turn off the cell-level switch for UL Layer 2 Improvement, run the following BSC6900 MML command: MOD UCELLALGOSWITCH: HspaPlusSwitch=UL_L2ENHANCED-0; // To turn off the cell-level switch for UL Layer 2 Improvement, run the following NodeB MML command: MOD LOCELL: UL_L2+=FALSE;
7.120 Configuring DC-HSDPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-010696 DC-HSDPA.
Prerequisite
l Dependency on Hardware For 3900 series base station, BBU3900 needs to be configured with the WBBPb3, WBBPb4 or WBBPd. For DBS3800 base station, the BBU3806 needs to be configured with the EBBC or EBBCd, the BBU3806C needs to be configured with the EBBM. The BTS3812E or BTS3812AE needs to be configured with the EBBI or EDLP board, and the UL baseband resource of DC-HSDAP cell can not be carried on HBBI or HULP board. The UL baseband resource of DC-HSDAP cell can be carried on EBBI or EULP board. l Dependency on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010685 Downlink Enhanced L2 l Dependency on Other Configuration One local cell can belong to only one DC group. The two cells must belong to the same DL resource group. The two cells must belong to the same sector.
If the two local cells in the same DC group are distributed cells, their RRU must be the same one. l l License The license is activated. Others The CN and HLR support a downlink peak rate of 42 Mbit/s per user. The BSC6900 software version should be not earlier than RAN12.0. The NodeB software version should be not earlier than RAN12.0. The UEs must belong in categories 21 to 24, 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, thus 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 Planning Parameter First Local Cell ID Second Local Cell ID Cell ID DL streaming traffic threshold on HSDPA DL BE traffic threshold on HSDPA Example 1 2 1, 2 D64 D64 Source Network planning Network planning Network planning Network planning Network planning
7-224
Issue 03 (2010-09-20)
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of the local cell 1. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of the local cell 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select CFG_HSDPA_DC_SWITCH from the Channel Configuration Strategy Switch list. Run the BSC6900 MML command SET UFRC. In this step, set Prefered MIMO_64QAM or DC_HSDPA character to DC_HSDPA.
NOTE
4.
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.
5.
Optional: If streaming services need to use HSDPA, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select MAP_PS_STREAM_ON_HSDPA_SWITCH from the Service Mapping Strategy Switch list. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set DL streaming traffic threshold on HSDPA and DL BE traffic threshold on HSDPA. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select DC_HSDPA and DL_L2ENHANCED from the Cell Hspa Plus function switch list. Run the BSC6900 MML command MOD UCELLHSDPA. Set Allocate Code Mode to Automatic. Select Code Adjust Switch for HSDPA to ON. Set User Number for Code Adjust for HSDPA.
6. 7.
8.
9.
Ensure that the two cells in the DC-HSDPA work in the neighboring frequencies. Run the BSC6900 MML command LST UCELL to view the UARFCNDownnlink of the two cells.
NOTE
With neighboring frequencies, the UARFCNDownnlinks of the two cells differ in the range of a value that is greater than 0 to a value that is smaller than or equal to 25.
10. Optional: Run the BSC6900 MML command LST UCELL to query the parameter Time Offset (TCELL) of the two cells. Ensure that the parameter is set to the same value. 11. Optional: Run the BSC6900 MML command MOD UCELLSETUP to change the time offset of a cell. 12. Run the NodeB MML command ADD DUALCELLGRPadd a DC group of local cell 1 and local cell 2. In this step, set First Local Cell ID and Second Local Cell ID respectively to the ID of local cell 1 and local cell 2. 13. Run the BSC6900 MML command ACT UCELL to activate the logical cell of the local cell 1.
14. Run the BSC6900 MML command ACT UCELL to activate the logical cell of the local cell 2. l Verification Procedure 1. l Run the NodeB MML command LST DUALCELLGRP to query the configured DCHSDPA cell group. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect CFG_HSDPA_DC_SWITCH from the Channel Configuration Strategy Switch list. Run the NodeB MML command RMV DUALCELLGRP to remove the DC-HSDPA cell group.
NOTE
2.
When removing a DC-HSDPA cell group, you only need to remove one local cell in the group.
----End
Example
// Activation procedure // To deactivate cells, run the following command repeatedly: DEA UCELL: CellId=1; DEA UCELL: CellId=2; // To set Channel Configuration Strategy Switch, run the following command: SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DC_SWITCH-1; // To set Prefered MIMO_64QAM or DC_HSDPA character, run the following command: SET UFRC: MIMO64QAMorDcHSDPASwitch= DC_HSDPA; // To set Service Mapping Strategy Switch, run the following command: SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; // To set the HSDPA threshold for DL streaming services, run the following command: SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; // To set Cell Hspa Plus function switch, run the following command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-1&DC_HSDPA-1; // To set Allocate Code Mode, run the following command: MOD UCELLHSDPA: CellId=1, AllocCodeMode=Automatic, CodeAdjForHsdpaSwitch=ON, CodeAdjForHsdpaUserNumThd=3; // To query the UARFCNDownnlink of the two cells, run the following command: LST UCELL: LstType=ByCellId, CellId=1; // To query the parameter Time Offset (TCELL) of the two cells, run the following command: LST UCELL: LstType=ByCellId, CellId=1; // To change the time offset of a cell, run the following command: MOD UCELLSETUP: CellId=1, TCell=CHIP512; // To configure local cell 1 and local cell 2 as a DC-HSDPA cell group, run the following command: ADD DUALCELLGRP: FIRSTLOCELL=1, SECONDLOCELL=2; // To activate the cells, run the following command repeatedly: ACT UCELL: CellId=1; ACT UCELL: CellId=2; // Verification procedure // To query the configured DC-HSDPA cell group, run the following command: LST DUALCELLGRP:; // Deactivation procedure // To set Channel Configuration Strategy Switch, run the following
7-226
Issue 03 (2010-09-20)
command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DC_HSDPA-0; // To remove the DC-HSDPA cell group, run the following command: RMV DUALCELLGRP: LOCELL=1;
7.121 Configuring Queuing and Preemption

This section describes how to activate, verify, and deactivate the optional feature WRFD-010505 Queuing and Preemption.
Prerequisite
l Dependency on Hardware This feature needs the core network to bring the ARP IE to BSC6900 during RAB assignment procedure so that BSC6900 can get the service priority with those RAB parameters. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package and RFD-010612 HSUPA Introduction Package. l License The license is activated.
Context
This feature enables service differentiation when the network is congested to provide better services for high-priority users.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UQUEUEPREEMPT to turn on the queuing and preemption switch. Run the BSC6900 MML command LST UQUEUEPREEMPT to check whether the queuing and preemption switch are turned on. Run the BSC6900 MML command SET UQUEUEPREEMPT to turn off the queuing and preemption switch.
----End
Example
//Activating Queuing and Preemption SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, QueueAlgoSwitch=ON, EmcPreeRefVulnSwitch=ON; //Deactivating Queuing and Preemption SET UQUEUEPREEMPT: PreemptAlgoSwitch=OFF, QueueAlgoSwitch=OFF;
Issue 03 (2010-09-20)
7-227
7.122 Configuring Access Class Restriction

This section describes how to activate, verify, and deactivate the optional feature WRFD-021103 Access Class Restriction.
Prerequisite
Context
When the cell or system is overloaded, this feature can restrict user access based on the allowed service class by broadcasting system information, thereby controlling potential load requirements of the system.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UACALGO to set AC Restriction Switch to ON and set other related parameters. Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 7-33.
7-228
Issue 03 (2010-09-20)
2. 3. 4. 5.
Run the BSC6900 MML command SET UACALGO. Run the BSC6900 MML command SET FCCPUTHD to specify the thresholds related to access class restriction. Run the BSC6900 MML command STR CPUUSAGETST to simulate system overload. Observe the traced Uu data. If there is an RRC_SYS_INFO_TYPE3 message and half of the IEs in the accessClassBarredList IE have a value of 0 as shown in Figure 7-34, you can infer that this feature has been activated. If there is no RRC_SYS_INFO_TYPE3 message, you can infer that this feature has not been activated.
Issue 03 (2010-09-20)
7-229
Figure 7-34 RRC_SYS_INFO_TYPE3 message
6. 7. l 1. ----End
Run the BSC6900 MML command STP CPUUSAGETST to stop simulating system overload. Run the BSC6900 MML command SET FCCPUTHD to set the thresholds back. Run the BSC6900 MML command SET UACALGO to set AC Restriction Switch to OFF.
Example
//Activating Access Class Restriction SET UACALGO: AcRstrctSwitch=ON, AcRstrctPercent=5, AcIntervalOfCell=1, AcRstrctIntervalLen=6; //Verifying Access Class Restriction SET FCCPUTHD: BRDCLASS=XPU, ACCTHD=40, ACRTHD=35; STR CPUUSAGETST: SRN=0, SN=2, SSN=1, ACU=45, STPMODE=MANULSTP; STP CPUUSAGETST: SRN=0, SN=2, SSN=1; SET FCCPUTHD: BRDCLASS=XPU, ACCTHD=80, ACRTHD=70; //Deactivating Access Class Restriction SET UACALGO: AcRstrctSwitch=OFF;
7-230
Issue 03 (2010-09-20)
7.123 Configuring Traffic Priority Mapping onto Transmission Resources

This section describes how to activate, verify, and deactivate the optional feature WRFD-050424 Traffic Priority Mapping onto Transmission Resources.
Prerequisite
Context
This feature enables the dynamical mapping of the services onto the transport bearers according to the TC, ARP, and THP of the user. The operator can flexibly configure the mapping to fulfill differentiated services while guaranteeing the QoS. This feature implements the mapping from traffic priorities to transmission resources and provides flexible configuration means for differentiated services and for guarantee of QoS.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD TRMMAP or MOD TRMMAP to configure the transport resource mapping. For example,
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 For the same service type, the primary path and the secondary path cannot be the same. l The default 14 transport resource mappings (indexed from 0 to 13) are added when the system is initialized, and you cannot modify them. l Interface Type and Transport Type cannot be modified.
2. l
Run the BSC6900 MML command ADD ADJMAP to add the transport resource mapping to an adjacent node. Run the BSC6900 MML command LST TRMMAP to check whether the added transport resource mapping is correct. If the mapping is not correct, run the RNC MML command MOD TRMMAP to modify the mapping. Run the BSC6900 MML command RMV TRMMAP to remove a mapping.
----End
Example
//Activating to configure the transport resource mapping ADD TRMMAP: TMI=44, REMARK="44", ITFT=IUB, TRANST=IP, VOICEPRIPATH=AF11; MOD TRMMAP: TMI=44, ITFT=IUB, TRANST=IP, VOICEPRIPATH=EF;
7.124 Configuring Differentiated Service Based on SPI Weight

This section describes how to activate, verify, and deactivate the optional feature WRFD-020806 Differentiated Service Based on SPI Weight.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the following features: When applied in the downlink on the Uu interface, this feature depends on the feature WRFD-01061103 Scheduling based on EPF and GBR. When applied in the uplink on the Uu interface, this feature depends on the feature WRFD-01061402 Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE Resource Management. When this feature is enabled together with the feature WRFD-01061402 Enhanced Fast UL Scheduling, only the uplink Uu interface resources can be differentially scheduled. When this feature is enabled together with the feature WRFD-010638 Dynamic CE Resource Management, both the uplink Uu interface resources and CE resources can be differentially scheduled. When applied in the downlink on the Iub interface, this feature depends on the features WRFD-010610 HSDPA Introduction Package and WRFD-050405 Overbooking on ATM Transmission, or depends on the features WRFD-010610 HSDPA Introduction Package and WRFD-050408 Overbooking on IP Transmission. When applied in the uplink on the Iub interface, this feature depends on the feature WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion. l License The license is activated.
Context
When Uu interface resources, CE resources, and Iub interface resources do not meet the GBR of all online users, this feature can preferentially guarantee the GBR of high-priority users to provide differentiated services while ensuring the fairness. This feature can ensure the service experience of high-priority users and provide differentiated services while ensuring equity.
Procedure
l
7-232
1. 2. l
Run the BSC6900 MML command SET USCHEDULEPRIOMAP to set the scheduling priority mapping information. Run the BSC6900 MML command SET USPIWEIGHT to set the factor associated with each scheduling priority. Run theBSC6900 MML command LST USCHEDULEPRIOMAP to check whether the added mapping information is correct. Run the BSC6900 MML command LST USPIWEIGHT to check whether the factor is set correctly. This feature does not need to be deactivated.
----End
Example
//Activating Differentiated Service Based on SPI Weight. SET USCHEDULEPRIOMAP: TrafficClass=INTERACTIVE, UserPriority=GOLD, THPClass=High, SPI=2; SET USPIWEIGHT: SPI=2, SPIWEIGHT=100; //Through the previous setting, the factor of scheduling priority 2 is set to 100%.
7.125 Configuring Inter-Frequency Hard Handover Based on Coverage

This section describes how to activate, verify, and deactivate the optional feature WRFD-020302 Inter Frequency Hard Handover Based on Coverage.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites The UE should support the relevant measurements and the handover procedure.
Context
This feature is applicable only to the inter-frequency handovers based on coverage, including the measurement-based inter-frequency handover triggered by the measurement of the quality of the active set.
Procedure
l Activation Procedure The HSUPA DCCC feature depends on the DCCC feature. Before using HSUPA DCCC, you must activate the DCCC feature first. 1. 2. 3. Run the BSC6900 MML command SET UCORRMALGOSWITCH to switch on the feature. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell. Run the BSC6900 MML command ADD UCELLINTERFREQHOCOV (cell level) or SET UINTERFREQHOCOV (RNC level) to configure proper parameters associated with coverage-based inter-frequency hard handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the status of the inter-frequency hard handover switch and the status of the active set quality measurement switch. Run the BSC6900 MML command LST UINTERFREQNCELL to check whether the configuration of the inter-frequency neighboring cell is proper. Run the BSC6900 MML command LST UCELLINTERFREQHOCOV(cell level) or LST UINTERFREQHOCOV(RNC level) to check whether the configurations of the inter-frequency hard handover parameters are proper. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the feature.
2. 3.
----End
Example
//Activating Inter Frequency Hard Handover Based on Coverage SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1&HO_INTER_FREQ_RPRT_2D2F_SWITCH-1; ADD UINTERFREQNCELL:RncId=1, CellId=1, NCellRncId=9, NCellId=100, CIOOffset=0, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, HOCovPrio=1, BlindHOFlag=FALSE, NPrioFlag=FALSE; ADD UCELLINTERFREQHOCOV: CellId=1, InterFreqReportMode=EVENT_TRIGGER, InterFreqMeasTime=60; //Deactivating Inter Frequency Hard Handover Based on Coverage SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-0;
7.126 Configuring Inter-Frequency Hard Handover Based on DL QoS

This section describes how to activate, verify, and deactivate the basic feature WRFD-020304 Inter Frequency Hard Handover Based on DL QoS.
Prerequisite
l Dependency on Hardware None
l l
Dependency on Other Features None License The license is activated.
Context
If downlink (DL) QoS is detected in the case of severe conditions, inter-frequency handover is triggered in the inter-frequency network. AMR and VP inter-frequency handovers can be triggered on the basis of TCP. PS BE inter-frequency handover can be triggered on the basis of TCP and RLC retransmission. The activation or deactivation of this feature for AMR, VP, and PS BE services can be performed separately.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable inter frequency hard handover. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell. Run the BSC6900 MML command ADD UCELLQOSHO (cell level) or SET UQOSHO (RNC level) configure proper parameters associated with DL QoS-based inter-frequency hard handover. Run the BSC6900 MML command SET UQOSACT to activate DL QoS-based interfrequency hard handover for BE services. Run the BSC6900 MML command SET UQOSACT to activate DL QoS-based interfrequency hard handover for AMR and AMR-WB speech services. Run the BSC6900 MML command SET UQOSACT to activate DL QoS-based interfrequency hard handover for VP services. Run the following BSC6900 MML command to check the configuration results. LST UCORRMALGOSWITCH LST UINTERFREQNCELL LST UCELLQOSHO LST UQOSACT l Deactivation Procedure 1. 2. 3. ----End Run the BSC6900 MML command SET UQOSACT to deactivate DL QoS-based inter-frequency hard handover for BE services. Run the BSC6900 MML command SET UQOSACT to deactivate DL QoS-based inter-frequency hard handover for AMR and AMR-WB speech services. Run the BSC6900 MML command SET UQOSACT to deactivate DL QoS-based inter-frequency hard handover for VP services.
4. 5. 6. l
Example
//Activating Inter Frequency Hard Handover Based on DL QoS SET UCORRMALGOSWITCH:
Issue 03 (2010-09-20)
7-235
HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1&HO_INTER_FREQ_RPRT_2D2F_SWITCH-1; ADD UINTERFREQNCELL:RncId=1, CellId=1, NCellRncId=9, NCellId=100, CIOOffset=0, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, HOCovPrio=1, BlindHOFlag=FALSE, NPrioFlag=FALSE; 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 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;
7.127 Configuring SRNS Relocation (UE Not Involved)

This section describes how to activate, verify, and deactivate the optional feature WRFD-02060501 SRNS Relocation (UE Not Involved).
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020605 SRNS Relocation Introduction Package. l l License The license is activated. Other Prerequisites The CN node and DRNC must support this feature.
Context
This feature supports the SRNS procedure based on the standard Iu interface defined by 3GPP. The static relocation procedure does not involve the UE and radio connections are affected during the relocation. The static relocation is an optimal relocation mode.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. Keep UE stay in idle mode and camp on cell 111. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select HO_INTRA_FREQ_SOFT_HO_SWITCH from the HandOver Switch and select SRNSR_DSCR_PROPG_DELAY_SWITCH from the SRNSR Algorithm Switch.
7-236
4. 5. l
Run the BSC6900 MML command SET USRNSR to set SRNS Relocation-Allowed Traffic Type to All service. Run the BSC6900 MML command MOD UNRNC to set the traffic classes for interIur handovers. Enable the standard interface tracing function on the BSC6900 LMT. Verification the function by querying the following messages. During relocation, UEs can make calls without call drops. Messages queried from the Iu interface of RNC1 are as follows: RNC1 to CN: RANAP_RELOCATION_REQUIRED CN to RNC1: RANAP_RELOCATION_COMMAND Messages queried from the Iu interface of RNC2 are as follows: RNC2 to CN: RANAP_RELOCATION_REQ CN to RNC2: RANAP_RELOCATION_REQ_ACK RNC2 to CN: RANAP_RELOCATION_DETECT RNC2 to CN: RANAP_RELOCATION_COMPLETE Message queried from the Iur interface between RNC1 and RNC2 is as follows: RNC1 to RNC2: RNSAP_ RELOCATION_COMMIT
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCHto clear HO_INTRA_FREQ_SOFT_HO_SWITCH from the parameter HoSwitch and SRNSR_DSCR_PROPG_DELAY_SWITCH from the parameter SrnsrSwitch.
----End
Example
//Activating SRNS Relocation (UE Not Involved) //Add an intra-frequency neighboring cell ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=2, NCellId=311, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Set the BSC6900 level switch SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1, SrnsrSwitch=SRNSR_DSCR_PROPG_DELAY_SWITCH-1; //Set the parameter of SRNS Relocation-Allowed Traffic Type SET USRNSR: SrnsRabCnDomainType=ALL; //Set the traffic classes for inter-Iur handovers MOD UNRNC: NRncId=2, SHOTRIG=CS_SHO_SWITCH-1, ServiceInd=SUPPORT_CS_AND_PS, PsBeProcType=CORRM_SRNSR_PSBE_RELOC; MOD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-1, ServiceInd=SUPPORT_CS_AND_PS, PsBeProcType=CORRM_SRNSR_PSBE_RELOC; //Deactivating SRNS Relocation (UE Not Involved). //Set the BSC6900 level switch SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0, SrnsrSwitch=SRNSR_DSCR_PROPG_DELAY_SWITCH-0;
Issue 03 (2010-09-20)
7-237
7.128 Configuring SRNS Relocation with Hard Handover

This section describes how to activate, verify, and deactivate the optional feature WRFD-02060502 SRNS Relocation with Hard Handover.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020605 SRNS Relocation Introduction Package. l l License The license is activated. Other Prerequisites The CN and the DRNC must support this feature simultaneously.
Context
The SRNS relocation triggered by hard handover applies to UEs in the CELL_DCH state. The relocation is performed when the following conditions are met: l l l The inter-frequency or intra-frequency handover is complete. The source cell and target cell belong to different RNCs. The Iur interface does not exist, or the resources for the connection setup on the Iur interface are insufficient.
In the preceding cases, the relocation triggered by hard handover needs to be performed on the UE to prevent the call drop.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. UE1 and UE2 are in idle mode and camp on Cell 111. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select HO_INTRA_FREQ_HARD_HO_SWITCH andHO_INTER_FREQ_RPRT_2D2F_SWITCH from the HandOver switch list. Run the BSC6900 MML command MOD UNRNC to set HHO cross IUR trigger to ON and Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC. Initiate standard interface tracing on the BSC6900 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.
4.
On the Iu interface tracing pane of RNC1 RNC1->CN RANAP_RELOCATION_REQUIRED CN to RNC1: RANAP_RELOCATION_COMMAND Messages queried from the Iu interface of RNC2 are as follows: RNC2 to CN: RANAP_RELOCATION_REQ CN to RNC2: RANAP_RELOCATION_REQ_ACK RNC2 to CN: RANAP_RELOCATION_COMPLETE On the Uu interface tracing pane of RNC1 RNC1->UE: RRC_RB_RECFG On the Uu interface tracing pane of RNC2 RRC_RB_RECFG_CMP l Deactivation Procedure This feature does not need to be deactivated. ----End
Example
//Activating SRNS Relocation with Hard Handover. ADD UINTERFREQNCELL: RncId=1, CellId=111, NCellRncId=2, NCellId=312, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHOFlag=FALSE, NPrioFlag=FALSE; SET UCORRMALGOSWITCH: HoSwitch= HO_INTRA_FREQ_HARD_HO_SWITCH-1&HO_INTER_FREQ_RPRT_2D2F_SWITCH-1; MOD UNRNC: NRncId=2, HHOTRIG=ON, PsBeProcType=CORRM_SRNSR_PSBE_RELOC; //Deactivating SRNS Relocation with Hard Handover. None.
7.129 Configuring SRNS Relocation with Cell/URA Update

This section describes how to activate, verify, and deactivate the optional feature WRFD-02060503 SRNS Relocation with Cell/URA Update.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020605 SRNS Relocation Introduction Package. l l License The license is activated. 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 l 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.
Procedure
l Activation Procedure 1. 2. 3. The Iur interface between RNC1 and RNC2 is working properly. On the HLR, set the UE to support background services of UL64K/DL 384K. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set the related switches so that the DCCC and state transition are supported. Run the BSC6900 MML command SET UCORRMALGOSWITCH 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. 4. 5. 6. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set BE DCH to FACH Transition Timer to 10. UE1 and UE2 are in idle mode and camp on Cell 111. Run the BSC6900 MML command MOD UNRNC to set IUR CCH support flag to NO and Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC. 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 to RNC1: RANAP_RELOCATION_COMMAND On the Uu interface tracing pane of RNC2 CN->RNC2 RANAP_RELOCATION_REQ RNC2->CN RANAP_RELOCATION_REQ_ACK RNC2->CN RANAP_RELOCATION_DETECT
RNC2->CN RANAP_RELOCATION_COMPLETE On the Iur interface tracing between of RNC1 RNC2 RNC1->RNC2: RNSAP_RELOCATION_COMMIT l Deactivation Procedure This feature does not need to be deactivated. ----End
Example
//Activating SRNS Relocation with Cell/URA Update. SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1&DRA_PS_BE_STATE_TRANS_SWITCH-1&DRA_PS_NON_BE_ STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: BeD2FStateTransTimer=10; MOD UNRNC: NRncId=2, SuppIurCch=NO, PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
7.130 Configuring Inter-RAT Handover Based on Coverage

This section describes how to activate, verify, and deactivate the optional feature WRFD-020303 Inter-RAT Handover Based on Coverage.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites The UE should support the relevant measurements and the handover procedure.
Context
This feature provides flexibility for telecom operators during UMTS and GSM network planning. In addition, it reduces the costs by using the existing GSM network resources, and provides extended coverage, load sharing, and hierarchical services.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the function. Run the BSC6900 MML command ADD U2GNCELL to add a GSM inter-frequency neighboring cell.
Issue 03 (2010-09-20)
3.
Run the BSC6900 MML command ADD UCELLINTERRATHOCOV (cell level) or SET UINTERRATHOCOV (RNC level) to configure proper parameters associated with coverage-based GSM inter-RAT handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the status of the inter-RAT handover switch and the status of the active set quality measurement switch. Run the BSC6900 MML command LST U2GNCELL to check whether the configuration of the GSM inter-RAT neighboring cell is correct. Run the BSC6900 MML command LST UCELLINTERRATHOCOV(cell level) or LST UINTERRATHOCOV (RNC level) to check whether the configurations of the GSM inter-RAT handover parametes are correct. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the feature. Run the BSC6900 MML command RMV UCELLINTERRATHOCOV (cell level) or SET UINTERRATHOCOV (RNC level) to restore the parameter associated with coverage-based GSM inter-RAT handover.
2. 3.
----End
Example
//Activating Inter-RAT Handover Based on Coverage SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_RPRT_2D2F_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1&HO _INTER_RAT_PS_OUT_SWITCH-1; //Deactivating Inter-RAT Handover Based on Coverage SET UCORRMALGOSWITCH: HoSwitch= HO_INTER_RAT_CS_OUT_SWITCH-0&HO_INTER_RAT_PS_OUT_SWITCH-0;
7.131 Configuring Inter-RAT Handover Based on DL QoS

This section describes how to activate, verify, and deactivate the optional feature WRFD-020309 Inter-RAT Handover Based on DL QoS.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites The UE should support related measurement and handover procedures.
Context
When the load of voice and PS BE services is higher in the cell and downlink QoS drops, this feature enables the UE to be handed over to an inter-RAT cell, thus guaranteeing QoS
requirements. DL QoS based inter-RAT handover provides the method to prevent call drop and guarantee the QoS in inter-RAT networking, which improves the network performance and enhances the end user experience.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set the open HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH switches in the HandOver switch parameter. Run the BSC6900 MML command ADD U2GNCELL to add an inter-RAT neighboring cell. Run the BSC6900 MML command SET UQOSHO to set the RNC-level DL QoSbased inter-RAT handover related parameters. Run the BSC6900 MML command SET UQOSACT to set the QoS switches for different traffic classes to ON. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the status of inter-RAT handover switches. Run the BSC6900 MML command LST UQOSACT to check whether the QoS switches for different traffic classes is ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH to close HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH switches in the HandOver switch parameter. Run the BSC6900 MML command SET UQOSACT to set the QoS switches for different traffic classes to OFF.
2. 3. 4. l
2. ----End
Example
//Activating Inter-RAT Handover Based on DL QoS SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1; SET UQOSACT: BEQosPerform=YES, AMRQosPerform=YES, VPQosPerform=YES, BeUlAct1=InterRatHO, UlQosAmrInterRatHoSwitch=YES, UlQosWAmrInterRatHoSwitch=YES, DlQosAmrInterRatHoSwitch=YES, DlQosWAmrInterRatHoSwitch=YES; //Deactivating Inter-RAT Handover Based on DL QoS SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-0&HO_INTER_RAT_PS_OUT_SWITCH-0; SET UQOSACT: BEQosPerform=NO, AMRQosPerform=NO, VPQosPerform=NO;
7.132 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO

This section describes how to activate, verify, and deactivate the optional feature WRFD-020307 Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
Prerequisite
l l Dependency on Hardware The MSC need to be compliant with 3GPP Release 6 to support the feature. Dependency on Other Features 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 WRFD-020305 Inter-RAT Handover Based on Service WRFD-020306 Inter-RAT Handover Based on Load WRFD-021200 HCS (Hierarchical Cell Structure) l l License The license is activated. Other Prerequisites The UE need to be compliant with 3GPP Release 6 to support the feature.
Context
Before VP services are handed over to the 2G system, this feature enables the fallback of video telephony to speech to ensure continuous calls. Video telephony is a service exclusive for 3G. However, due to the limitations of UE and network support capabilities, it is possible that the service cannot be implemented. Therefore, Service Change and UDI Fallback (SCUDIF) is introduced in Release 6. This feature provides the mechanism to fall back to speech instead of experiencing call drops in these scenarios.
Procedure
7.133 Configuring Inter-RAT Handover Phase 2

This section describes how to activate, verify, and deactivate the optional feature WRFD-020308 Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
Prerequisite
l Dependency on Hardware BSC should support NACC RIM (RAN Information Management) and PS handover procedure. l
7-244
Dependency on Other Features

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 WRFD-020305 Inter-RAT Handover Based on Service WRFD-020306 Inter-RAT Handover Based on Load WRFD-021200 HCS (Hierarchical Cell Structure) l License The license is activated.
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 l WRFD-02030801 NACC (Network Assisted Cell Change) WRFD-02030802 PS Handover between UMTS and GPRS
Procedure
l For details about how to activate, verify, and deactivate this feature, see the following sections: 7.134 Configuring NACC(Network Assisted Cell Change) 7.135 Configuring PS Handover between UMTS and GPRS ----End
7.134 Configuring NACC(Network Assisted Cell Change)

This section describes how to activate, verify, and deactivate the optional feature WRFD-02030801 NACC(Network Assisted Cell Change).
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020308 PS Inter-RAT Handover Phase 2. l License The license is activated.
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 Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to open the following switches in the HandOver switch parameter: HO_INTER_RAT_PS_OUT_SWITCH 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.
Run the BSC6900 MML command ADD UEXT2GCELL(for new neighboring cell) or MOD UEXT2GCELL (for the exist neighboring cell) to set Inter-RAT cell support RIM indicator to TRUE. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the settings of the PS inter-RAT handover, NACC, and Relocation switches. 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.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH in the HandOver switch parameter to 0. Run the BSC6900 MML command MOD UEXT2GCELL to set Inter-RAT cell support RIM indicator to FALSE.
2. ----End
Example
//Activating NACC(Network Assisted Cell Change) SET UCORRMALGOSWITCH: 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;
7.135 Configuring PS Handover between UMTS and GPRS

This section describes how to activate, verify, and deactivate the optional feature WRFD-02030802 PS Handover between UMTS and GPRS.
Prerequisite
l l
7-246

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020308 PS Inter-RAT Handover Phase 2. l License The license is activated.
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.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to open the following switches in the HandOver switch parameter: HO_INTER_RAT_PS_OUT_SWITCH HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH 2. Run the BSC6900 MML command ADD UEXT2GCELL to add a neighboring GSM cell to the UMTS coverage and to set the Inter-RAT cell support PS HO indicator parameter to TRUE. Run the BSC6900 MML command ADD U2GNCELL to add a neighboring GSM cell for the UMTS cell. Optional: Run the BSC6900 MML command SET UINTERRATHOCOV to set inter-RAT handover measurement related parameters. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the status of PS inter-RAT handover switch and the Relocation HO switch. Run the BSC6900 MML command LST UEXT2GCELL to ensure the inter-RAT cell supports PS Handover. Run the BSC6900 MML command LST UINTERRATHOCOV to check inter-RAT handover measurement related parameters. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH in the HandOver switch parameter to 0. Run the BSC6900 MML command MOD UEXT2GCELL to set the SuppPSHOFlag parameter to FALSE.
3. 4. l
2. ----End
Issue 03 (2010-09-20)
7-247
Example
//Activating PS Handover between UMTS and GPRS SET UCORRMALGOSWITCH: 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;
7.136 Configuring Mobility Between UMTS and LTE Phase 1

This section describes how to activate, verify, and deactivate the optional feature WRFD-020126 Mobility Between UMTS and LTE Phase 1. For information about how to configure this feature on the LTE side, see the related documents provided by the LTE equipment vendor.
Prerequisite
l l l l Dependency on Hardware The UE is a UMTS/LTE dual-mode terminal, complying with 3GPP Release 8. Dependency on Other Features None License The license is activated. Other Prerequisites The LTE network supports this feature.
Context
The Mobility Between UMTS and LTE Phase 1 feature provides the following functions: l l Cell reselection between a UMTS cell and an LTE cell. PS handover from an LTE cell to a UMTS cell
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCELLSIBSWITCH or MOD UCELLSIBSWITCH. Select SIB19 from the SIB Switch list. If the information about the frequencies of neighboring LTE cells is configured, the BSC6900 sends an SIB19 message to the UE after the switch is turned on. The information contained in the SIB19 message includes neighboring LTE cell list and LTE cell reselection parameters.
2.
Run the BSC6900 MML command ADD UCELLSELRESEL or MOD UCELLSELRESEL to configure the absolute priority of the serving cell. The BSC6900 performs inter-RAT measurement according to the values of the parameters 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 BSC6900 makes cell reselection decisions according to the configured information about the frequencies of neighboring cells.
4.
Configure the related data, such as the neighbor relations between cells, on the LTE side. For information about how to configure the related information on the LTE side, see the related documents provided by the LTE equipment vendor. If the LTE equipment is provided by Huawei, see the Idle Mode Management parameter description.
Verification Procedure 1. In the navigation pane, click the Trace tab. In the displayed Trace Navigation Tree pane, expand Trace and UMTS Services and then double-click Uu Interface Trace. In the displayed dialog box, set Uu Message Type to RRC_SYS_INFO_TYPE19, as shown in Figure 7-35. Figure 7-35 Uu Interface Trace dialog box
2.
Analyze the trace messages. If the SIB19 message can be traced over the Uu interface, as shown in Figure 7-36, you can infer that this feature is enabled. If the SIB19 message cannot be traced over the Uu interface, you can infer that this feature is not enabled.
Issue 03 (2010-09-20)
7-249
Figure 7-36 Tracing the SIB19 message
NOTE
To deactivate this feature, you can either turn off the SIB19 switch or deactivate the associated license. l To disable this feature in specified cells, you are recommended to turn off the SIB19 switch. l To disable this feature in all cells under a BSC6900, you are recommended to deactivate the associated license.
1.
Run the BSC6900 MML command MOD UCELLSIBSWITCH to turn off the SIB19 switch of the cell. As a result of the action, the BSC6900 stops sending the SIB19 message to the UE. In such a case, the configured absolute priority of the serving cell and the configured information about the frequencies of neighboring cells become idle. Run the BSC6900 MML command SET LICENSE to deactivate the associated license.
2. ----End
Example
//Activating Mobility Between UMTS and LTE Phase1 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; //Deactivating Mobility Between UMTS and LTE Phase1 MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-0; SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH5=LQW1ULM01-0;
7.137 Configuring Inter-Frequency Load Balance

This section describes how to activate, verify, and deactivate the optional feature WRFD-020103 Inter Frequency Load Balance.
Prerequisite
l l
7-250

The configurations of the features on which this feature depends are complete. When this feature is used for HSDPA/HSUPA load control, WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package. l License The license is activated.
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 primary congestion state. The purpose is to reduce the load of this cell.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the required LDR algorithms: UL_UU_LDR: UL UU load reshuffling algorithm. DL_UU_LDR: DL UU load reshuffling algorithm CELL_CODE_LDR: Code reshuffling algorithm 2. 3. 4. Run the BSC6900 MML command SET UCORRMALGOSWITCH and MOD UCELLHOCOMM to enable the inter frequency handover functions. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell that supports blind handover. Run the BSC6900 MML command ADD UCELLINTERFREQHONCOV (cell level) or SET UINTERFREQHONCOV (RNC level) to configure proper parameters associated with load-based inter-frequency hard handover. Set LDR associated thresholds as follows: Run the BSC6900 MML command MOD UCELLLDM to set power LDR thresholds (UL/DL LDR Trigger/release threshold and DL State Trans Hysteresis threshold). Run the BSC6900 MML command MOD UCELLLDR to set code LDR threshold (Cell LDR SF reserved threshold). 6. Run the BSC6900 MML command MOD UCELLLDR to set the inter-frequency handover for code resource congestion switches to TRUE (Code congestion select inter-freq indication). Run the BSC6900 MML command SET ULDCPERIOD to set the length of LDR period (LDR period timer length). Run the BSC6900 MML command MOD UCELLLDR to select InterFreqLDHO as one of the LDR actions and set parameters related to LDR actions. Run the following commands to verify whether the activation is successful. LST UCELLALGOSWITCH LST UCELLLDR LST UCELLLDM LST ULDCPERIOD LST UCORRMALGOSWITCH
5.
7. 8. l
LST UINTERFREQNCELL LST UCELLHOCOMM LST UCELLINTERFREQHONCOV(cell level) LST UINTERFREQHONCOV(RNC level) l Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the LDR algorithms. UL_UU_LDR: UL UU load reshuffling algorithm DL_UU_LDR: DL UU load reshuffling algorithm CELL_CODE_LDR: Code reshuffling algorithm 2. 3. Run the BSC6900 MML command SET UCORRMALGOSWITCH and MOD UCELLHOCOMM to disable the inter frequency handover functions. Run the BSC6900 MML command MOD UCELLLDR to recover the interfrequency handover for code resource congestion switches to FALSE (Code congestion select inter-freq indication). Restore the parameters value that is changed in the activation procedure.
4. ----End
Example
//Activating Inter Frequency Load Balance MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR1; SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-1&HO_INTER_FREQ_HARD_HO_SWITCH-1; MOD UCELLHOCOMM: CellId=111, InterFreqRATSwitch=INTERFREQ; MOD UCELLLDR: CellId=111, CodeCongSelInterFreqHoInd=TRUE; //Deactivating Inter Frequency Load Balance MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_LDR-0&DL_UU_LDR-0&CELL_CODE_LDR-0&CELL_CREDIT_LDR0; SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-0&HO_INTER_FREQ_HARD_HO_SWITCH-0; MOD UCELLHOCOMM: CellId=111, InterFreqRATSwitch=INTERRAT; MOD UCELLLDR: CellId=111, CodeCongSelInterFreqHoInd= FALSE;
7.138 Configuring Inter-RAT Handover Based on Service

This section describes how to activate, verify, and deactivate the optional feature WRFD-020305 Inter-RAT Handover Based on Service.
Prerequisite
l l l
7-252

Context
This feature provides a mechanism where handover is performed between the GSM/GPRS and UTRAN systems on the basis of services. This feature enables proper services to be forwarded to the GSM/GPRS system to balance the load between the two systems. It also prevents the handover from adversely affecting services according to the service attribute.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the inter-RAT handover. Run the BSC6900 MML command ADD UEXT2GCELL to add the basic information about a GSM cell. Run the BSC6900 MML command ADD U2GNCELL to set the neighbor relation with a neighboring GSM cell. Run the BSC6900 MML command ADD UCELLHOCOMM to set the parameter Inter-RAT CS handover switch or Inter-RAT PS handover switch to ON as required. Run the BSC6900 MML command ADD UCELLINTERRATHONCOV (cell level) or SET UINTERRATHONCOV (RNC level) to configure proper parameters associated with non-coverage-based inter-RAT handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the status of the inter-RAT handover switch and the status of the active set quality measurement switch. Run the BSC6900 MML command LST UEXT2GCELL to ensure the configuration of the GSM inter-RAT neighboring cell is correct. Run the BSC6900 MML command LST UINTERRATHOCOV to check whether the parameter Inter-RAT CS handover switch or Inter-RAT PS handover switch is set to ON. Run the BSC6900 MML command LST UCELLINTERRATHONCOV (cell level) or LST UINTERRATHONCOV (RNC level) to ensure the configurations of the GSM inter-RAT handover parametes are correct. Run the BSC6900 MML command MOD UCELLHOCOMM to set the parameter Inter-RAT CS handover switch or Inter-RAT PS handover switch to OFF as required.
5.
2. 3.
4.
----End
Example
//Activating Inter-RAT Handover Based on Service SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_RPRT_2D2F_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1&HO _INTER_RAT_PS_OUT_SWITCH-1; ADD UCELLHOCOMM: CellId=111, CSServiceHOSwitch=ON, PSServiceHOSwitch=ON; //Deactivating Inter-RAT Handover Based on Service MOD UCELLHOCOMM: CellId=111, CSServiceHOSwitch=OFF, PSServiceHOSwitch=OFF;
Issue 03 (2010-09-20)
7-253
7.139 Configuring Inter-RAT Handover Based on Load

This section describes how to activate, verify, and deactivate the optional feature WRFD-020306 Inter-RAT Handover Based on Load.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. When this feature is used for HSDPA/HSUPA load control, WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package. l License The license is activated.
Context
This feature is an important part of LDR. It enables some UEs to be handed over to inter-RAT same-coverage cells when the current cell is in the primary congestion state. The UEs are blindly handed over to GSM/GPRS cells to reduce the load of the current cell.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the inter-RAT handover. Run the BSC6900 MML command ADD UEXT2GCELL to add the information of a neighboring GSM cell to the UMTS coverage. Run the BSC6900 MML command ADD U2GNCELL to add a neighboring GSM cell for a UMTS cell. Run the BSC6900 MML command ADD UCELLLDR to configure inter-RAT load handover actions for the corresponding cell. Run the BSC6900 MML command ADD UCELLINTERRATHONCOV (cell level) or SET UINTERRATHONCOV (RNC level) to configure correct parameters associated with non-coverage-based GSM inter-RAT handover. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the status of the inter-RAT handover switch and the status of the active set quality measurement switch. Run the BSC6900 MML command LST U2GNCELL to ensure the configuration of the GSM inter-RAT neighboring cell is proper. Run the MML command LST UCELLLDR to check the inter-RAT load handover actions of the corresponding cell.
2. 3.
7-254
Issue 03 (2010-09-20)
4.
Run the BSC6900 MML command LST UCELLINTERRATHONCOV (cell level) or LST UINTERRATHONCOV (RNC level) to ensure the configurations of the GSM inter-RAT handover parametes are correct. Run the BSC6900 command MOD UCELLLDR to deactivate the load handover actions as required.
----End
Example
//Activating Inter-RAT Handover Based on Load SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_RPRT_2D2F_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1&HO _INTER_RAT_PS_OUT_SWITCH-1;
7.140 Configuring DRD Introduction Package

This section describes how to activate, verify, and deactivate the basic feature WRFD-020400 DRD Introduction Package.
Prerequisite
Context
This feature supports inter-frequency or inter-system directed retry and redirection. The DRD Introduction Package contains the following features: l l l WRFD-02040001 Intra System Direct Retry WRFD-02040002 Inter System Direct Retry WRFD-02040003 Inter System Redirect
Procedure
l For detailed procedures about how to activate, verify, and deactivate the previous three features, see the following sections: 7.141 Configuring Intra-System Direct Retry 7.142 Configuring Inter-System Direct Retry 7.143 Configuring Inter-System Redirect ----End
7.141 Configuring Intra-System Direct Retry

This section describes how to activate, verify, and deactivate the optional feature WRFD-02040001 Intra System Direct Retry.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020400 DRD Introduction Package. l License The license is activated.
Context
This feature is related to intra-system direct retry during the RRC or RAB assignment.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DR_RRC_DRD_SWITCH and DR_RAB_COMB_DRD_SWITCH from the drop-down list of the parameter Direct retry switch. Run the BSC6900 MML command SET UDRD to set the RNC-level switches Service differential drd switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, and Code balance DRD switch to ON. Optional: Run the BSC6900 MML command ADD UCELLDRD to set the cell-level switches Service differential drd switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, and Code balance DRD switch to ON. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether the RRC DRD and RAB DRD switches are selected. Run the BSC6900 MML command LST UDRD to check whether the RNC-level switches are set to ON. Run the BSC6900 MML command LST UCELLDRD to check whether the cell-level switches are set to ON. Run the BSC6900 MML command SET UDRD to set the RNC-level switches to OFF. Run the BSC6900 MML command MOD UCELLDRD to set the cell-level switches to OFF.
2.
3.
----End
Example
//Activating Intra System Direct Retry SET UCORRMALGOSWITCH: 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; ADD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON; //Verifying Intra System Direct Retry //Deactivating Intra System Direct Retry SET UDRD: ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF; MOD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF;
7.142 Configuring Inter-System Direct Retry

This section describes how to activate, verify, and deactivate the optional feature WRFD-02040002 Inter System Direct Retry.
Prerequisite
Context
This feature is related to inter-system direct retry during the RAB assignment.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DR_RAB_SING_DRD_SWITCH and DR_RAB_COMB_DRD_SWITCH from the drop-down list Direct retry switch. Run the BSC6900 MML command SET UDRD to set the RNC-level parameter Max inter-RAT direct retry number to the required value but not 0. Run the BSC6900 MML command ADD UCELLDRD to set the cell-level parameter Max inter-RAT direct retry number to the required value but not 0. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether the RAB DRD switches are selected.
2. 3. l
Issue 03 (2010-09-20)
7-257
2.
Run the BSC6900 MML command LST UDRD to check whether the RNC-level parameter Max inter-RAT direct retry number is set to the required value but not 0. Run the BSC6900 MML command LST UCELLDRD to check whether the cell-level parameter Max inter-RAT direct retry number is set to the required value but not 0. Run the BSC6900 MML command SET UDRD to set Max inter-RAT direct retry number to 0. Run the BSC6900 MML command MOD UCELLDRD to set Max inter-RAT direct retry number to 0.
3.
----End
Example
//Activating Inter System Direct Retry SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1&DR_RAB_COMB_DRD_SWITCH-1; SET UDRD: DRMaxGSMNum=3; ADD UCELLDRD: CellId=11, DRMaxGSMNum=3; //Verifying Inter System Direct Retry //Deactivating Inter System Direct Retry SET UDRD: DRMaxGSMNum=0; MOD UCELLDRD: CellId=11, DRMaxGSMNum=0;
7.143 Configuring Inter-System Redirect

This section describes how to activate, verify, and deactivate the optional feature WRFD-02040003 Inter System Redirect.
Prerequisite
Context
This feature is related to inter-system redirect during the RRC assignment.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DR_RRC_DRD_SWITCH from the drop-down list Direct retry switch.
7-258
2. l
Run the BSC6900 MML command SET UDRD to set ConnectFailRrcRedirSwitch to Allowed_To_Inter_RAT. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether DR_RRC_DRD_SWITCH is selected from the drop-down list Direct retry switch. Run the MML command LST UDRD to check whether ConnectFailRrcRedirSwitch is set to Allowed_To_Inter_RAT. Run the BSC6900 MML command SET UDRD to set RRC redirect switch to OFF or Only_To_Inter_Frequency.
2. l
----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;
7.144 Configuring Traffic Steering and Load Sharing During RAB Setup
This section describes how to activate, verify, and deactivate the optional feature WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup.
Prerequisite
Context
With this feature, the load of the service and the required service type are considered during RAB setup to implement traffic steering and load sharing between different frequencies or different frequency bands.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell.
Issue 03 (2010-09-20)
2. 3. 4. 5. l
Run the BSC6900 MML command ADD USPG to add service priority group. Run the BSC6900 MML command MOD UCELLSETUP to set a cell to belong to service priority group. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DR_RAB_SING_DRD_SWITCH from the drop-down list Direct retry switch. Run the BSC6900 MML command SET UDRD to set Service differential drd switch and Measurement-Based DRD Switch to ON. Start the Uu interface tracing on the BSC6900 LMT. The UE initiates a PS interactive service in the cell. The Uu Interface Tracing window shows the following Procedure: After UE response "RRC_RB_SETUP_CMP" in the cell. BSC6900 sends an "RRC_PH_CH_RECFG" message to the UE. The UE responds with an "RRC_PH_CH_RECFG_CMP" message from the cell. Then BSC6900 enters in compress mode state and sends an "RRC_MEAS_CTRL" message for periodical mode to the UE. The UE reports signal quality of the periodic reports. BSC6900 sends an "RRC_RB_RECFG" message to the UE, which indicates the primary scrambling code and frequency of inter-frequency neighboring cell; The UE responds an "RRC_RB_RECFG_CMP" message from inter-frequency neighboring cell.
Deactivation Procedure 1. Run the BSC6900 MML command SET UDRD to set Service differential drd switch and Measurement-Based DRD Switch to OFF.
----End
Example
//Activating Traffic Steering and Load Sharing During RAB Setup ADD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=1, NCellId=2, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE, NPrioFlag=FALSE, DrdOrLdrFlag=TRUE, InterNCellQualReqFlag=FALSE; ADD USPG: SpgId=1, PriorityServiceForR99RT=2, PriorityServiceForR99NRT=2, PriorityServiceForHSDPA=2, PriorityServiceForHSUPA=2, PriorityServiceForExtRab=1; ADD USPG: SpgId=2, PriorityServiceForR99RT=1, PriorityServiceForR99NRT=1, PriorityServiceForHSDPA=1, PriorityServiceForHSUPA=1, PriorityServiceForExtRab=1; MOD UCELLSETUP: CellId=1, SpgId=1; MOD UCELLSETUP: CellId=2, SpgId=2; SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1; //Deactivating Traffic Steering and Load Sharing During RAB Setup SET UDRD: ServiceDiffDrdSwitch=OFF, BasedOnMeasHRetryDRDSwitch=OFF;
7.145 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.
Prerequisite
Context
If UE initialize a voice call with a long distance to the antenna, UMTS RAN can consider it as a call attempt in the pilot contaminated area, and redirect it to GSM to avoid handover drop in the following call procedure.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UDISTANCEREDIRECTION to select ON from Redirection Switch. See 3GPP25.433 to set the Propagation delay threshold parameter. Set the Redirection Factor Of LDR and Redirection Factor Of Normal parameters according to the actual network planning. Run the BSC6900 MML command ADD UCELLDISTANCEREDIRECTION to select ON from Redirection Switch. See 3GPP25.433 to set the Propagation delay threshold parameter. Set the Redirection Factor Of LDR and Redirection Factor Of Normal parameters according to the actual network planning. Run the BSC6900 MML command LST UDISTANCEREDIRECTION,LST UCELLDISTANCEREDIRECTION to query the configuration information. Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 7-37.
2.
Issue 03 (2010-09-20)
7-261
Figure 7-37 Uu Interface Tracing dialog box
3.
Simulate a scenario where pilot contamination occurs. Place the UE in a place where the UE is far away from the NodeB and pilot signals are strong. Then, enable the UE to make CS voice calls. Analyze the trace messages. In the Uu interface trace data, view the GSMTargetcellinfo information element (IE) in the RRC CONNECTION REJECT message. If the RRC CONNECTION REJECT IE contains the IE of GSMTargetcellinfo as shown in Figure 7-38, you can infer that this feature has been activated. If the RRC CONNECTION REJECT IE does not contain the IE of GSMTargetcellinfo, you can infer that this feature has not been activated. Figure 7-38 Viewing GSM-Targetcellinfo IE
4.
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLDISTANCEREDIRECTION to select OFF from Redirection Switch, disable this feature in specified cells.
7-262
2. ----End
Run the BSC6900 MML command SET UDISTANCEREDIRECTION to select OFF from Redirection Switch, disable this feature in all cells.
Example
//Activating Inter-RAT Redirection Based on Distance SET UDISTANCEREDIRECTION: RedirSwitch=ON, RedirFactorOfNorm=100; ADD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=ON, DelayThs=50, RedirFactorOfNorm=0, RedirFactorOfLDR=100; //Deactivating Inter-RAT Redirection Based on Distance MOD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=OFF; SET UDISTANCEREDIRECTION: RedirSwitch=OFF;
7.146 Configuring Measurement-based Direct Retry

This section describes how to activate, verify and deactivate the optional feature WRFD-020402 Measurement based Direct Retry.
Prerequisite
Context
After the setup of the UE RRC connection, the RNC can immediately initiate inter-frequency or inter-system measurements. The RNC can then perform direct retries according to the measurement results when the RAB assignment is received from the CN. This feature can increase the success rate of DRD and reduce the drop rate caused by DRD with blind handover, thus improving the network performance.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command ADD UCELLMBDRINTERFREQ, turn on MBDR Switch. Run the BSC6900 MML command ADD UCELLMBDRINTERRAT, turn on MBDR Switch. Run the BSC6900 MML command ADD UINTERFREQNCELL, set the Flag of MBDR Cell. Optional: Run the BSC6900 MML command ADD UINTERFREQNCELL, set the Flag of MBDR Cell to TRUE(send).
Issue 03 (2010-09-20)
5. l
Optional: Run the BSC6900 MML command ADD UINTERFREQNCELL, set the Flag of MBDR Cell to TRUE(send). When a large number of UEs access the cell, cell congestion occurs. At this time, if handover based on inter-frequency measurement is used to achieve load reshuffling (LDR), you can view the inter-frequency measurement control information on the Uu interface. After the UE sends the inter-frequency measurement report, the UE will be handed over to another cell. Run the BSC6900 MML command MOD UCELLMBDRINTERFREQ, close the MBDR Switch.
----End
Example
//Activating Measurement based Direct Retry ADD UCELLMBDRINTERFREQ: CellId=1, InterFreqActiveType=CSAMR_INTERFREQ-1&CSNONAMR_INTERFREQ-1;&PSR99_INTERFR EQ-1;&PSHSPA_INTERFREQ-1; InterFreqReportMode=EVENT_TRIGGER; ADD UCELLMBDRINTERRAT: CellId=1, InterRatActiveType=CSAMR_INTERRAT-1; ADD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=2, NCellId=2, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE, NPrioFlag=FALSE, MBDRFlag=TRUE, InterNCellQualReqFlag=FALSE; ADD U2GNCELL: RNCId=1, CellId=1, BlindHoFlag=FALSE, NPrioFlag=FALSE, MBDRFlag=TRUE; //Deactivating Measurement based Direct Retry MOD UCELLMBDRINTERFREQ: InterFreqActiveType=CSAMR_INTERFREQ-0&CSNONAMR_INTERFREQ-0;&PSR99_INTERFR EQ-0;&PSHSPA_INTERFREQ-0;
7.147 Configuring Enhanced Fast Dormancy

This section describes how to activate, verify, and deactivate the optional feature WRFD-020500 Enhanced Fast Dormancy.
Prerequisite
l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. To activate the license, do as follows: Run the SET LICENSE command. In this step, specify Fast Dormancy Enhancement-per PS Active User. l Other Prerequisites The Iu-PS activation factor is changed.
To change the Iu-PS activation factor, run the ADD TRMFACTOR and MOD ADJMAP commands in sequence. The recommended value for the activation factor is 10%.
NOTE
After this feature is enabled, the number of UEs in CELL_PCH or URA_PCH state increases sharply. UEs in CELL_PCH or URA_PCH state consume a large number of Iu-PS resources although they do not transmit any data. To avoid the admission failure on the Iu-PS interface due to the increase of UEs in CELL_PCH or URA_PCH state, change the Iu-PS activation factor.
It is recommended that an SCCPCH be added to avoid FACH congestion.

NOTE
After this feature is enabled, the number of FACH users increases and thus the traffic on the FACH becomes higher. This may lead to FACH congestion. For details on how to add an SCCPCH, see the Typical Script for Adding Two SCCPCHs.
Context
In the traditional fast dormancy mode, the BSC6900 transits the UE state from CELL_FACH or CELL_DCH to IDLE if no operation is performed on the UE for a certain period. After this feature is enabled, the BSC6900 transits the UE state from CELL_FACH or CELL_DCH to CELL_PCH when one of the following conditions is met, thus reducing the signaling traffic on the control plane. l l The BSC6900 receives the Signaling Connection Release Indication (SCRI) message from the UE. The CELL_FACH inactivity timer or CELL_DCH inactivity timer on the BSC6900 expires.
Procedure
l Activation Procedure 1. Run the SET URRCTRLSWITCH command to disable the state transition of the UE from CELL_PCH or URA_PCH to CELL_DCH triggered during CS call origination or CS call termination, thus avoiding the effect on this feature caused by UE incompatibility. Run the SET URRCTRLSWITCH command to enable the enhanced fast dormancy feature at the BSC6900 level. Run the SET UPSINACTTIMER command to set the value of the CELL_DCH inactivity timer. The recommended value is 4s. 4. Run the SET UPSINACTTIMER command to set the value of the CELL_FACH inactivity timer. The recommended value is 10s. 5. Run the SET UPSINACTTIMER command to set the value of the CELL_PCH inactivity timer. The recommended value is 360s. 6. Run the SET UUESTATETRANS command to set the traffic threshold for event 4A that triggers the CELL_FACH to CELL_DCH state transition to D3K.
2. 3.
Issue 03 (2010-09-20)
7. 8.
Run the SET URRCTRLSWITCH command to set whether the Type Allocation Code (TAC) match function is to be enabled. Run the ADD UIMEITAC command to add the IMEI TAC of the Smart Phone. The BSC6900 compares the queried UE IMEI with the configured IMEI TAC, and than performs certain operations as follows: Table 7-4 Processing procedure after the comparison Setting of FD_TAC_MAT CH_SWITCH in the SET URRCTRLSWI TCH Command (BSC6900 Level) ON Setting of TAC in the ADD UIMEITAC Command Setting of Fast Dormancy Switch in theADD UIMEITAC Command (UE Level) ON Processing Procedure
Set
BSC6900 enables the enhanced fast dormancy feature for UEs with a matched TAC. BSC6900 enables the enhanced fast dormancy feature for UEs with a matched TAC. You can set a specified procedure for some UEs through the ADD UIMEITAC command. For example, you can set UEs of a certain module to support the CELL_DCH-toCELL_FCH-toCELL_PCH procedure rather than the CELL_DCH-toCELL_PCH procedure.
OFF
Set
ON
7-266
Issue 03 (2010-09-20)
Setting of FD_TAC_MAT CH_SWITCH in the SET URRCTRLSWI TCH Command (BSC6900 Level) OFF
Setting of TAC in the ADD UIMEITAC Command
Setting of Fast Dormancy Switch in theADD UIMEITAC Command (UE Level) Not involved
Processing Procedure
Not set
BSC6900 enables the enhanced fast dormancy feature for all UEs with a software version later than R5. BSC6900 does not enable the enhanced fast dormancy feature for UEs with a matched TAC.
OFF
Set
OFF
9. l
Run the ADD UCELLALGOSWITCH command to enable enhanced fast dormancy feature at the cell level. Run the DSP LICUSAGE command to check whether the license of this feature is activated. The license is activated, as shown in Figure 7-39.
Figure 7-39 Status of the Enhanced Fast Dormancy license
2. 3.
Start Uu interface tracing on the LMT. Use an Smart Phone to perform PS services. For example, browse websites by using an Smart Phone. The RRC_RB_SETUP message shows that the UE is in CELL_DCH state, as shown in Figure 7-40. Figure 7-40 UE in CELL_DCH state
4.
Keep the UE in idle state for a period. For example, perform no operation for four seconds after a website is opened.
Issue 03 (2010-09-20)
The RRC_RB_RECFG message shows that the UE state is transited from CELL_DCH to CELL_PCH, as shown in Figure 7-41. Figure 7-41 UE in CELL_PCH state
5.
Continue to perform PS services such as website browsing by using the Smart Phone. Cell update or channel reconfiguration occurs. Check the RRC_CELL_UPDATE message as shown in Figure 7-42 and Figure 7-43.
Figure 7-42 Cell update
Figure 7-43 Channel reconfiguration
Deactivation Procedure 1. Run the SET URRCTRLSWITCH command to disable the enhanced fast dormancy feature at the BSC6900 level.
----End
Example
//Activating the enhanced fast dormancy feature //Activating the license of this feature SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FastDormancyEnhancement=141120; //Disabling the state transition of the UE from CELL_PCH or URA_PCH to CELL_DCH triggered during CS call origination or CS call termination SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT20-1; //Enabling the enhanced fast dormancy feature at the BSC6900 level
7-268
Issue 03 (2010-09-20)
SET URRCTRLSWITCH: PROCESSSWITCH=FAST_DORMANCY_SWITCH-1; //Setting the value of the CELL_DCH inactivity timer SET UPSINACTTIMER: PsInactTmrForFstDrmDch=4; //Setting the value of the CELL_FACH inactivity timer SET UPSINACTTIMER:PsInactTmrForFstDrmFach=10; //Setting the value of the CELL_PCH inactivity timer SET UPSINACTTIMER: PsInactTmrForPreFstDrm=360; //Setting the traffic threshold for event 4A that triggers the CELL_FACH to CELL_DCH state transition to D3K SET UUESTATETRANS: FastDormancyF2DHTvmThd=D3K; //Enabling the IMEI TAC match function SET URRCTRLSWITCH: PROCESSSWITCH=FD_TAC_MATCH_SWITCH-1; //Adding the IMEI TAC of the Smart Phone ADD UIMEITAC: TAC_FUNC=Fast_Dormancy, TAC=01177600, Description="iPhone", FastDormancy=ON; //Enabling the enhanced fast dormancy feature at the cell level ADD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=FAST_DORMANCY_ADCTRL-1; //Deactivating the enhanced fast dormancy feature //Disabling the enhanced fast dormancy feature at the BSC6900 level SET URRCTRLSWITCH: PROCESSSWITCH=FAST_DORMANCY_SWITCH-0;
7.148 Configuring Cell Barring

This section describes how to activate, verify, and deactivate the optional feature WRFD-021102 Cell Barring.
Prerequisite
Context
If the cell barring feature is enabled, cells can be barred either automatically or manually to facilitate maintenance by the operator when the cells are running improperly.
Procedure
l Activation Procedure 1. l
Issue 03 (2010-09-20)
Run the BSC6900 MML command MOD UCELLACCESSSTRICT to bar a specific access class.
1.
Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 7-44. Figure 7-44 Uu Interface Trace dialog box
2. 3.
Run the BSC6900 command MOD UCELLACCESSSTRICT. Observe the accessClassBarredList IE at the end of the RRC_SYS_INFO_TYPE3 message in the traced Uu data, as shown in Figure 7-45 Figure 7-45 AccessClassBarredList
7-270
Issue 03 (2010-09-20)
If the value of the last AccessClassBarred IE is 0, you can infer that this feature has been activated. If the value of the last AccessClassBarred IE is 1, you can infer that this feature has not been activated. l Deactivation Procedure 1. ----End Run the BSC6900 command MOD UCELLACCESSSTRICT to remove the barring on that class.
Example
//Activating Cell Barring MOD UCELLACCESSSTRICT: CellId=1, IsAccessClass15Barred=BARRED; //Deactivating Cell Barring MOD UCELLACCESSSTRICT: CellId=1, IsAccessClass15Barred=NOT_BARRED;
7.149 Configuring 3G/2G Common Load Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-020310 3G/2G Common Load Management.
Prerequisite
l Dependency on Hardware The CN should support this feature. The BSS should support this feature. l Dependency on Other Features This feature is required only when one of the following features is available: WRFD-020305 Inter-RAT Handover Based on Service WRFD-020306 Inter-RAT Handover Based on Load WRFD-021200 HCS (Hierarchical Cell Structure) WRFD-020400 DRD Introduction Package WRFD-020308 Inter-RAT Handover Phase 2 l License The license is activated.
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 Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the inter-RAT handover.
Issue 03 (2010-09-20)
2. 3. l
Run the BSC6900 MML command SET UINTERRATHONCOV to enable the 3G/ 2G common load management function. Run the BSC6900 MML command ADD UEXT2GCELL to add a GSM cell neighboring to the UMTS coverage. 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. Run the BSC6900 MML command LST U2GNCELL to ensure the inter-RAT neighboring cell for the GSM system is added correctly. Run the BSC6900 MML command SET UINTERRATHONCOV 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.
2. l
----End
Example
//Activating 3G/2G Common Load Management SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_RPRT_2D2F_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1&HO _INTER_RAT_PS_OUT_SWITCH-1; SET UINTERRATHONCOV: SndLdInfo2GsmInd=ON, NcovHoOn2GldInd=ON; //Deactivating 3G/2G Common Load Management SET UINTERRATHONCOV: SndLdInfo2GsmInd=OFF, NcovHoOn2GldInd=OFF;
7.150 Configuring RAB Quality of Service Renegotiation over Iu Interface

This section describes how to activate, verify, and deactivate the optional feature WRFD-010506 RAB Quality of Service Renegotiation over Iu Interface.
Prerequisite
l l l Dependency on Hardware The core NEs should support selective configuration for MBR and GBR. Dependency on Other Features None License The license is activated.
Context
During basic congestion, this feature enables the BSC6900 to perform Iu renegotiation on the maximum rate and guaranteed rate of PS real-time services. This reduces the rate of real-time services.
7-272
Issue 03 (2010-09-20)
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCELLALGOSWITCH and ADD UNODEBALGOPARA to enable the required LDR algorithm. UL_UU_LDR: UL UU load reshuffling algorithm. DL_UU_LDR: DL UU load reshuffling algorithm. CELL_CREDIT_LDR: Credit reshuffling algorithm.
ADD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
IUB_LDR: NodeB Iub reshuffling algorithm LCG_CREDIT_LDR: cell group level credit reshuffling algorithm. NODEB_CREDIT_LDR: NodeB level credit reshuffling algorithm. 2. 3. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the required Iu QoS renegotiation algorithm. Set associated thresholds as follows: Run the BSC6900 MML command ADD UCELLLDM to set power LDR thresholds (UL/DL LDR Trigger threshold and DL State Trans Hysteresis threshold). Run the BSC6900 MML command ADD UNODEBLDR to set the cell group/ NodeB LDR thresholds (Ul/DL LDR Credit SF reserved threshold). Run the BSC6900 MML command ADD UCELLLDR to set the local cell NodeB credit LDR thresholds (Ul/DL LDR Credit SF reserved threshold). 4. 5. l Run the BSC6900 MML command SET ULDCPERIOD to set the length of LDR period (LDR period timer length). Run the BSC6900 MML command ADD UCELLLDR to select QoSRenego as one of the LDR actions and set parameters related to LDR actions. Run the following BSC6900 commands to verify whether the activation is successful. LST UCELLALGOSWTICH LST UNODEBALGOPARA LST UCELLLDR LST UCELLLDM LST UNODEBLDR LST ULDCPERIOD LST UCORRMALGOSWITCH l Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to close the required LDR algorithm switches for resources. UL_UU_LDR: UL UU load reshuffling algorithm. DL_UU_LDR: DL UU load reshuffling algorithm. CELL_CREDIT_LDR: Credit reshuffling algorithm. 2. Run the BSC6900 MML command MOD UNODEBALGOPARA to set IUB_LDR to OFF to disable NodeB Iub reshuffling algorithm.
Issue 03 (2010-09-20)
3.
Run the BSC6900 MML command MOD UNODEBALGOPARA to set NODEB_CREDIT_LDR to OFF to disable NodeB level credit reshuffling algorithm. Run the BSC6900 MML command MOD UNODEBALGOPARA to set LCG_CREDIT_LDR to OFF to disable cell group level credit reshuffling algorithm.
4. ----End
Example
//Activating RAB Quality of Service Renegotiation over Iu Interface ADD UCELLALGOSWITCH: CellId=111, NBMUlCacAlgoSelSwitch=ALGORITHM_SECOND, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CREDIT_LDR-1; ADD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_IU_QOS_RENEG_SWITCH-1;
7.151 Configuring Rate Negotiation at Admission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-010507 Rate Negotiation at Admission Control.
Prerequisite
l Dependency on Hardware For Iu QoS negotiation, the CN node needs to support this feature, but for RAB downsizing, the CN node does not need to support this feature. l l Dependency on Other Features None License The license is activated.
Context
This feature supports the processes of QoS negotiation over Iu and RAB rate reduction.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select PS_BE_IU_QOS_NEG_SWITCH from the drop-down list PS rate negotiation switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select PS_STREAM_IU_QOS_NEG_SWITCH from the drop-down list PS rate negotiation switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select PS_RAB_DOWNSIZING_SWITCH from the drop-down list PS rate negotiation switch.
2.
3.
l
7-274
1. l
Run the BSC6900 MML command LST UCORRMALGOSWITCH to query the activation result. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear PS_BE_IU_QOS_NEG_SWITCH from the drop-down list PS rate negotiation switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear PS_STREAM_IU_QOS_NEG_SWITCH from the drop-down list PS rate negotiation switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear PS_RAB_DOWNSIZING_SWITCH from the drop-down list PS rate negotiation switch.
2.
3.
----End
Example
//Activating Rate Negotiation at Admission Control SET UCORRMALGOSWITCH: PsSwitch =PS_BE_IU_QOS_NEG_SWITCH-1; SET UCORRMALGOSWITCH: PsSwitch=PS_STREAM_IU_QOS_NEG_SWITCH-1; SET UCORRMALGOSWITCH: PsSwitch=PS_RAB_DOWNSIZING_SWITCH-1; //Deactivating Rate Negotiation at Admission Control SET UCORRMALGOSWITCH: PsSwitch =PS_BE_IU_QOS_NEG_SWITCH-0; SET UCORRMALGOSWITCH: PsSwitch=PS_STREAM_IU_QOS_NEG_SWITCH-0; SET UCORRMALGOSWITCH: PsSwitch=PS_RAB_DOWNSIZING_SWITCH-0;
7.152 Configuring Service Steering and Load Sharing in RRC Connection Setup
This section describes how to activate, verify, and deactivate the optional feature WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020400 DRD Introduction Package. l l License The license is activated. Other Prerequisites The UE need to be compliant with 3GPP Release 6(or later) to support the feature.
Context
With this feature, service and load sharing between frequencies, bands, or RATs can be achieved during RRC connection setup on the basis of the service type and the load of the current cell.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the RRC DRD function. Run the BSC6900 MML command SET UREDIRECTION (RNC level) or ADD UCELLREDIRECTION (cell level) to enable the RNC-oriented or cell-oriented switch of RRC direction for service steering (Redirection Switch) to ONLY_TO_INTER_FREQUENCY or ONLY_TO_INTER_RAT.
NOTE
l The parameters set through the SET UREDIRECTION command take effect at the RNC level, whereas the parameters set through the ADD UCELLREDIRECTION command take effect in only a specific cell. l If a cell is configured with both RNC-oriented and cell-oriented parameters, the cell-oriented parameters take precedence over the RNC-oriented parameters.
Verification Procedure 1. Run the following BSC6900 MML commands to verify whether the activation is successful. LST UCORRMALGOSWITCH LST UREDIRECTION LST UCELLREDIRECTION
Deactivation Procedure 1. 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable RRC DRD function. Run the BSC6900 MML command SET UREDIRECTION or MOD UCELLREDIRECTION to disable the RNC-oriented related switch of RRC direction for service steering (Redirection Switch) to OFF.
----End
Example
//Activating Service Steering and Load Sharing in RRC Connection Setup SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1; SET UREDIRECTION: TrafficType=PSHSPA, RedirSwitch=ONLY_TO_INTER_FREQUENCY, RedirFactorOfNorm=0, RedirFactorOfLDR=0, RedirBandInd=BAND1, ReDirUARFCNUplinkInd=FALSE, ReDirUARFCNDownlink=10713; ADD UCELLREDIRECTION: CellId=1, TrafficType=AMR, RedirSwitch=ONLY_TO_INTER_FREQUENCY, RedirFactorOfNorm=0, RedirFactorOfLDR=100, RedirBandInd=BAND1, ReDirUARFCNUplinkInd=FALSE, ReDirUARFCNDownlink=10563; //Deactivating Service Steering and Load Sharing in RRC Connection Setup SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-0; SET UREDIRECTION: TrafficType=PSHSPA, RedirSwitch=OFF; MOD UCELLREDIRECTION: CellId=100, TrafficType=PSHSPA, RedirSwitch=OFF;
7.153 Configuring TCP Accelerator

This section describes how to activate, verify, and deactivate the optional feature WRFD-020123 TCP Accelerator.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Others In the case of downlink TCP accelerator, the BSC6900 version is RAN11.0 or later. In the case of uplink TCP accelerator, the BSC6900 version is RAN12.0 or later.
Context
The TCP Accelerator feature in RAN11.0 optimizes the data transmission in the downlink. The TCP Accelerator feature in RAN12.0 is based on that in RAN11.0. It is introduced 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 focus on accelerating the slow start and restore processes during uplink data transmission, thus reducing the impact of packet loss on the performance of uplink TCP data transmission.
NOTE
Data configurations are required only on the BSC6900 side to activate, verify, and deactivate this feature.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UDPUCFGDATA to turn on the RNCoriented TpeSwitch. In this step, select TPE_DOWNLINK_SWITCH and TPE_UPLINK_SWITCH from the TPE switch drop-down list box according to the actual requirements. Run the BSC6900 MML command LST UDPUCFGDATA to check whether the TCP accelerator switch is turned on. If the switch is turned on, you can infer that this feature is activated. 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. Calculate the rate of download increased by the downlink TCP accelerator. Use a test terminal to upload a file of 200 KB from the FTP server. Then, compare the upload time taken before and after the TPE_DOWNLINK_SWITCH is turned on. Calculate the rate of upload increased by the uplink TCP accelerator. Run the BSC6900 MML command SET UDPUCFGDATA to turn off the RNCoriented TpeSwitch. In this step, deselect TPE_DOWNLINK_SWITCH and TPE_UPLINK_SWITCH from the TPE switch drop-down list box according to the actual requirements.
2.
3.
----End
Example
//Activating TCP accelerator Turning on the RNC-oriented TpeSwitch SET UDPUCFGDATA: TpeSwitch=TPE_DOWNLINK_SWITCH-1&TPE_UPLINK_SWITCH-1; //Deactivating TCP Accelerator Turning off the RNC-oriented TpeSwitch SET UDPUCFGDATA: TpeSwitch=TPE_DOWNLINK_SWITCH-0&TPE_UPLINK_SWITCH-0;
7.154 Configuring Uplink Flow Control of User Plane

This section describes how to activate, verify, and deactivate the optional feature WRFD-020124 Uplink Flow Control of User Plane.
Prerequisite
Context
The Uplink Flow Control of User Plane feature is a Huawei proprietary feature. This feature detects uplink packet loss for R99 services based on the private IEs on the Iub interface. In addition, this feature controls uplink traffic based on the Transport Format Combination Control message. In this way, this feature prevents uplink packet loss caused by lack of flow control, and increases transmission efficiency.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET URRCTRLSWITCH to turn on the RNCoriented Iub private interface switch. In this step, select NODEB_PRIVATE_INTERFACE_SWITCH from the Process Switch dropdown list box.
NOTE
NODEB_PRIVATE_INTERFACE_SWITCH controls the functionality of all private messages on the Iub interface, rather than only the private messages for uplink user plane flow control.
2. l
Run the NodeB MML command SET R99FLOWCTRLSWTCH to turn on the celloriented switch for uplink user plane flow control. Initiate Iub interface tracing on the BSC6900 LMT, as shown in Figure 7-46.
7-278
Issue 03 (2010-09-20)
Figure 7-46 Iub interface trace dialog box
2.
Establish an R99 BE service on the UE. Observe the NBAP_RL_RECFG_PREP message in the traced Iub data. Check the iE-ExtensionsIE in the DCH-FDDInformationItem. If there is a trafficClass-Private IE, as shown in Figure 7-47, you can infer that this feature of the BSC6900 has been activated. Figure 7-47 TrafficClass-Private
l
Issue 03 (2010-09-20)
1. ----End
Run the NodeB MML command SET R99FLOWCTRLSWTCH to turn off the celloriented switch for uplink user plane flow control.
Example
Activating uplink flow control of user plane SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; SET R99FLOWCTRLSWTCH: SWITCH=OPEN, LOCELL=1; Deactivating uplink flow control of user plane SET R99FLOWCTRLSWTCH: SWITCH=CLOSE, LOCELL=1;
7.155 Configuring Active Queue Management (AQM)

This section describes how to activate, verify, and deactivate the optional feature WRFD-011502 Active Queue Management (AQM).
Prerequisite
Context
The AQM feature provides a buffering optimization method to achieve friendly communication with the TCP protocols and shorten the buffer delay.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-oriented AQM switch. In this step, set Dynamic resource allocation switch to DRA_AQM_SWITCH. Start UE tracing on the BSC6900 LMT. In the displayed UE Trace dialog box, select the Debug Mode check box, as shown in Figure 7-48.
7-280
Issue 03 (2010-09-20)
Figure 7-48 UE Trace dialog box
2.
Establish a BE service on the UE. View the ucAqmSwitch IE in the PdcpSetupInfo IE in the CRLC_SETUP_MSG message among the traced UE data. If the value of the ucAqmSwitch IE is 1, you can infer that this feature has been activated. If the value of the ucAqmSwitch IE is 0, you can infer that this feature has not been activated.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect DRA_AQM_SWITCH from 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;
7.156 Configuring Quality Improvement for Subscribed Service

This section describes how to activate, verify, and deactivate the optional feature WRFD-020128 Quality Improvement for Subscribed Service.
Prerequisite
l Dependency on Hardware The BTS3812E is configured with the EBBI or EDLP board. The DBS3800 is configured with the EBBC or EBBCd board. The 3900 series base station are configured with the WBBPb or WBBPd board.
l l l
Dependency on Other Features None License The license is activated. Other Prerequisites Only the BSC6900 supports this feature. The BSC6900 software version is RAN12.0 or later. The NodeB software version is RAN12.0 or later.
Context
This feature adjusts the user scheduling priority by identifying the characteristics of IP packets and modifying the Scheduling Priority Indicator (SPI) of downlink services. This feature grants high scheduling priority to specific services on which telecom operators focus, such as services from specific servers or http services to guarantee the bandwidth. This feature can also lower the scheduling priority of the non-subscribed services that consume a large amount of bandwidth. The purpose is to provide sufficient bandwidth for services with high scheduling priority.
Procedure
l Activation Procedure 1. Set the initial SPI weight on the BSC6900 LMT. After this feature is activated, the scheduling priority of a service is changed when the service is given an SPI weight different from the initial one. If the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight has been activated, run the BSC6900 MML command SET USPIWEIGHT to set the parameters Scheduling Priority Indicator and SPI Weight according to the actual network planning. If the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is not activated, run the BSC6900 MML command SET UFRC to set the parameter Default SPI Weight according to the actual network planning. 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DRA_IP_SERVICE_QOS_SWITCH from the Dynamic resource allocation switch list. Run the BSC6900 MML command SET UDPUCFGDATA to set Service Priority Adjusting Coefficient. Run the BSC6900 MML command ADD UIPSERVICEQOS to set the parameter triplet related to a service to be given a high scheduling priority.
NOTE
3. 4.
The parameter triplet comprises IP Address, IP Port, and IP Protocol Type.
Verification Procedure 1. Check the transmission quality of services with high scheduling priority when the cell is overloaded.
l
7-282
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to deselect DRA_IP_SERVICE_QOS_SWITCH from the Dynamic resource allocation switch list.
----End
Example
//Activating Quality Improvement for Subscribed Service //Setting the initial SPI weight value when the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight has been activated SET USPIWEIGHT: SPI=4, SPIWEIGHT=81; //Setting the initial SPI weight value when the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is not activated SET UFRC: DefaultSPIWeight=20; SET UCORRMALGOSWITCH: DraSwitch=DRA_IP_SERVICE_QOS_SWITCH-1; SET UDPUCFGDATA: ServicePriAdjCoef=10; //Setting the parameter triplet ADD UIPSERVICEQOS: CnOpIndex=0, RecIndex=1, MatchType=IPAndPort, IPAddress="192.168.0.100", PortNum=8080, ProtocolType=TCP; //Deactivating Quality Improvement for Subscribed Service SET UCORRMALGOSWITCH: DraSwitch=DRA_IP_SERVICE_QOS_SWITCH-0;
7.157 Configuring Cell Broadcast Service

This section describes how to activate, verify, and deactivate the optional feature WRFD-011000 Cell Broadcast Service.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites The UE should have the capability to receive cell broadcast messages.
Context
This feature supports the standard cell broadcast procedure as stipulated in protocols to assist the CBC for the cell broadcast service.
Procedure
l Activation Procedure The external CBC has two networking modes, ATM and IP. Here take the ATM networking as an example. 1. 2. 3. 4. Run the BSC6900 MML command RMV URNCCBCPUID to disable the configuration of CBC. Run the BSC6900 MML command SET URNCCBPARA to built-in CBC. Run the BSC6900 MML command ADD DEVIP to add the device IP addresses of an interface board. Run the BSC6900 MML command ADD IPOAPVC to add an IPoA 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 SGSN and RNC. The VPI and VCI must be consistent with those of the SGSN. For details, run the SGSN MML command LST IPOA to query the configuration.
5. 6. 7.
Run the BSC6900 MML command ADD IPRT to add a route from the interface board to the CBC. The route passes through the IP address between SGSN and BSC6900. Run the BSC6900 MML command ADD UCBSADDR to add the CBS socket IP address. Run the BSC6900 MML command ADD UCTCH to add the CTCH (Common Traffic CHannel) of the cell.
NOTE
When the CTCH is set up on FACH5, run the following commands to add the CTCH:
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. 9.
Run the BSC6900 MML command ADD UCELLCBSDRX to set the CBS DRX (Discontinuous Reception Mechanism) scheduling parameter. Run the BSC6900 MML command ADD UCELLCBSSAC to add a CBS service area.
10. Run the BSC6900 MML command ACT UCELLCBS to activate the CBS function of the cell. l Verification Procedure 1. Check whether the CBS function works properly. (1) Ping the CBS IP address of the RNC on the CBC side. If the IP address is pinged successfully, you can infer that the CBC can be connected to the RNC. (2) 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. (3) Check whether the CBS socket is connected properly. Trace messages on the Iu interface to check whether the SABP_LOAD_QUERY message is sent to the RNC, as shown in Figure 7-49.
7-284
Issue 03 (2010-09-20)
Figure 7-49 Viewing the SABP_LOAD_QUERY messages
(4) The SABP_LOAD_QUERY_CMP message returned by the RNC is contained in the IE available-bandwidth, as shown in Figure 7-50. Figure 7-50 Viewing the SABP_LOAD_QUERY_CMP messages
(5) Run the BSC6900 MML command DSP UCELL to check whether the CBS function works, as shown in Figure 7-51.
Issue 03 (2010-09-20)
7-285
Figure 7-51 Viewing the CBS function status
2.
Check how to deliver a broadcast message (1) Use the MTC tool to deliver messages on the CBC side. It is recommended that the time interval be within 10s and messages be delivered more than two times (0 times represent infinity). (2) Trace messages on the Iu interface to check whether the SABP_WRITE_REPLACE message is sent to the RNC, as shown in Figure 7-52.
7-286
Issue 03 (2010-09-20)
Figure 7-52 Viewing the SABP_WRITE_REPLACE messages
(3) The SABP_WRITE_REPLACE_CMP message returned by the RNC is contained in the IE number-of-broadcasts-completed, as shown in Figure 7-53.
Issue 03 (2010-09-20)
7-287
Figure 7-53 Viewing the SABP_WRITE_REPLACE_CMP messages
(4) Trace messages on the Uu interface and check whether the UU_BMC_MSG_TYPE message beginning with 01 is delivered from the RNC, as shown in Figure 7-54.
7-288
Issue 03 (2010-09-20)
Figure 7-54 Viewing the UU_BMC_MSG_TYPE messages
3.
Check how to stop delivering the broadcast message. (1) On the CBC side, select the message being delivered and click the delete button. (2) Trace messages on the Iu interface to check whether the SABP_KILL message is sent to the RNC, as shown in Figure 7-55.
Issue 03 (2010-09-20)
7-289
Figure 7-55 Viewing the SAB_KILL messages
(3) The SABP_KILL_CMP message returned by the RNC contains the IE numberof-broadcast-completed, as shown in Figure 7-56.
7-290
Issue 03 (2010-09-20)
Figure 7-56 Viewing the SABP_KILL_CMP messages
(4) Trace messages on the Uu interface to find that the RNC no long delivers the UU_BMC_MSG_TYPE message beginning with 01. l Deactivation Procedure 1. ----End Run the BSC6900 MML command RMV UCBSADDR to deactivate the Cell Broadcast Service.
Example
//Activating Cell Broadcast Service. SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=1, FUNCTIONSWITCH1=CBS-1; RMV URNCCBCPUID: CnOpIndex=1; SET URNCCBPARA: CBSwitch=OFF; ADD DEVIP: SRN=5, SN=18, DEVTYPE=IPOA_CLIENT_IP, IPADDR="12.12.12.12",
Issue 03 (2010-09-20)
7-291
MASK="255.255.255.0"; 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; ADD IPRT: SRN=5, SN=18, DSTIP="11.11.11.12", DSTMASK="255.255.255.0", NEXTHOP="12.12.12.120", PRIORITY=HIGH, REMARK="SGSN_CBS"; ADD UCBSADDR: SRN=5, SN=2, CnOpIndex=1, RNCIPADDR="12.12.12.12", CBCIPADDR="11.11.11.11", CBCMASK="255.255.255.0"; ADD UCTCH: CellId=0, FachId=4; ADD UCELLCBSDRX: CellId=0; ADD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=OFF; ACT UCELLCBS: CellId=0; //Deactivating Cell Broadcast Service. RMV UCBSADDR: CnOpIndex=0;
7.158 Configuring Simplified Cell Broadcast

This section describes how to activate, verify, and deactivate the optional feature WRFD-011001 Simplified Cell Broadcast.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features This feature is mutually exclusive to the feature WRFD-011000 Cell Broadcast Service feature. l l License The license is activated. Other Prerequisites The UE should have the capability to receive cell broadcast messages. Only BSC6900 supports this feature.
Context
Huawei Simplified Cell Broadcast function performs through a built-in cell broadcast processing module in the RNC without CBC, and thus reduces equipment costs.
Procedure
l Activation Procedure 1. 2. 3. 4. 5.
7-292
Run the BSC6900 MML command RMV UCBSADDR to remove the IP address of external CBS. Run the BSC6900 MML command RMV URNCCBCPUID to configure the SPU subsystem for the built-in CBC. Run the BSC6900 MML command SET URNCCBPARA to set CBSwitch to ON. Run the BSC6900 MML command SET LICENSE to activate the built-in CBC license. Run the BSC6900 MML command ADD UCTCH to add the CTCH for the cell.
6. 7. 8. l
Run the BSC6900 MML command ADD UCELLCBSDRX to set the CBS DRX scheduling parameter. Run the BSC6900 MML command ADD UCELLCBSSAC to add the CBS service area and broadcast message. Run the BSC6900 MML command ACT UCELLCBS to activate the CBS function of the cell. Check whether the CBS function works properly. After the activation, if the UU_BMC_MSG_TYPE message beginning with 01 issued from the RNC is traced on the Uu interface, as shown in Figure 7-57, you can infer that the CBS function works properly: Figure 7-57 UU_BMC_MSG_TYPE message
2.
Check how to deliver a broadcast message (1) Run the BSC6900 MML command DEA UCELLCBS to deactivate the CBS function. (2) Run the BSC6900 MML command MOD UCELLCBSSAC to modify the content of cell broadcast message. (3) Run the BSC6900 MML command ACT UCELLCBS to activate the CBS function.
3.
Check how to stop delivering the broadcast message. Run the BSC6900 MML command DEA UCELLCBSto deactivate the CBS function. The BSC6900 will stop sending broadcast messages to the Uu interface. In Uu interface tracing, the RNC no longer sends the UU_BMC_MSG_TYPE message beginning with 01 to the cell.
4.
Check how to query whether the RNC completes X times of broadcast message delivery. Simplified cell broadcast belongs to the built-in CBS, which continuously sends messages containing information like cell names. Therefore, the exchange message unable to be traced on the standard interface can be queried from the Uu interface. When the CBS function is activated, the UU_BMC_MSG_TYPE message beginning with 01 delivered by the RNC can be traced on the Uu interface. When the CBS function is deactivated, the RNC stops delivering the message.
Issue 03 (2010-09-20)
7-293
Deactivation Procedure 1. 2. Run the BSC6900 MML command DEA UCELLCBS to activate the CBS function of the cell. Run the BSC6900 MML command SET URNCCBPARAto set CB Switch to OFF.
----End
Example
//Activating Simplified Cell Broadcast RMV UCBSADDR: CnOpIndex=1; ADD URNCCBCPUID: CnOpIndex=1, SRN=0, SN=2, SSN=1; SET URNCCBPARA: CBSwitch=ON, RepeatPeriod=10, RepeatNum=0; SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=1, FUNCTIONSWITCH4=SIMPLE_CELL_BORADCAST-1; ADD UCTCH: CellId=0, FachId=4; ADD UCELLCBSDRX: CellId=0; ADD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=ON, MsgContent="welcome! it is cell 0"; ACT UCELLCBS: CellId=0; //Verifying Simplified Cell Broadcast DEA UCELLCBS: CellId=0; MOD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=ON, MsgContent="HELLO,SIMPLE CBS"; ACT UCELLCBS: CellId=0; //Deactivating Simplified Cell Broadcast DEA UCELLCBS: CellId=0; SET URNCCBPARA: CBSwitch=OFF
7.159 Configuring TFO/TrFO

This section describes how to activate, verify, and deactivate the basic feature WRFD-011600 TFO/TrFO.
Prerequisite
l l l Dependency on Hardware The CN node needs to support the feature at the same time. Dependency on Other Features None License The license is activated.
Context
This feature implements the functions of TFO/TrFO through the identification of the IUUP V2 core network.
Procedure
l
7-294
1. l
Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable TFO/ TrFO. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether CS_IUUP_V2_SUPPORT_SWITCH is selected from the drop-down list CS algorithm switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable TFO/TrFO.
----End
Example
//Activating TFO/TrFO SET UCORRMALGOSWITCH: CsSwitch=CS_IUUP_V2_SUPPORT_SWITCH-1; //Deactivating TFO/TrFO SET UCORRMALGOSWITCH: CsSwitch=CS_IUUP_V2_SUPPORT_SWITCH-0;
7.160 Configuring Dynamic Power Sharing of MultiCarriers

This section describes how to activate, verify, and deactivate the optional feature WRFD-020116 Dynamic Power Sharing of Multi-Carriers.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Others The NodeB software version should be no earlier than RAN11.0.
Context
This feature enables multiple carriers to share power, which improves the utilization of power resources. The NodeB in RAN11.0 allows the carrier carrying HSDPA services to share the unused power resources of another carrier carrying R99 services.
Procedure
l Activation Procedure 1.
Issue 03 (2010-09-20)
Run the NodeB MML command ADD PAGRP to add a power sharing group.

NOTE
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.
(1) The source local cell is identified through the Source Local Cell ID parameter and the destination local cell is identified through the Destination Local Cell ID parameter. (2) Max Sharing Power Ratio(%) specifies the maximum rate of idle power that the source local cell is allowed to share with the destination local cell. This rate is based on the configured maximum transmit power of the source local cell. We recommend setting the rate to a value that is not more than 50%. (3) Sharing Power Margin(%) specifies 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. l Verification Procedure 1. 2. 3. 4. Before configuring the power sharing group, increase the load in the destination local cell to 90% by means of load simulation. Use multiple HSDPA UEs to perform high-speed downloading in the destination local cell. Check the throughput of the destination local cell. Run the NodeB MML command ADD PAGRP to add a power sharing group. 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. Run the NodeB MML command RMV PAGRP to remove the power sharing group.
----End
Example
// Activation Procedure // To configure Sharing Power Margin(%), do as follows: ADD PAGRP: SLOCELL=1, DLOCELL=2, MAXSHRTO=50, SHMGN=10; // Deactivation Procedure // To remove the power sharing group, do as follows: RMV PAGRP: DLOCELL=2;
7.161 Configuring Multi-Carrier Switch off Based on Traffic Load

This section describes how to activate, verify, and deactivate the optional feature WRFD-020117 Multi-Carrier Switch off Based on Traffic Load.
7-296
Issue 03 (2010-09-20)
Prerequisite
Context
l The power consumption evaluation of the products in mobile networks shows that the radio access network (and particularly the base stations) is the highest contributor of power consumption and CO2 emissions in the operation. If multiple carriers are used in the same coverage area, Huawei provides operators with adaptive carrier power management to reduce the power consumption. The traffic volume varies with the time. For example, a base station in the Central Business District (CBD) has a relatively high traffic volume in the daytime, which requires more than one carrier to serve all the subscribers; however, from midnight to early morning of the next day, the traffic volume is relatively low. Since RAN10.0, during the idle periods that are configurable by operators, the RNC can dynamically shut down the carrier on which there is no service and maintain the other carriers in the same area. The carrier will be turned on again when the traffic volume on the other carriers enters into the basic congestion state or when the idle period ends. In this manner, energy is saved.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA. 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. Run the BSC6900 MML command LST UCELLDYNSHUTDOWN to check whether the cell-oriented switch for dynamic shutdown is turned on. If the switch is not turned on, run the BSC6900 MML command ADD UCELLDYNSHUTDOWN to turn on the cell-level dynamic shutDown switch, specify the shutdown period, and set the following parameters. 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 If the switch is turned on, you can run the MOD UCELLDYNSHUTDOWN command to modify the related parameters.
2.
Issue 03 (2010-09-20)
7-297

NOTE
The RNC defines the default values of the following parameters . l Cell Dynamic ShutDown Type l Cell Dynamic ShutDown Total User number Threshold l Cell Dynamic ShutDown Hsdpa User number Threshold l Cell Dynamic ShutDown Hsupa User number Threshold l Cell Dynamic ShutDown Neighbour Cell Load Remain threshold Retain the default values in normal situation.
3.
Run the BSC6900 MML command LST UINTERFREQNCELL to check whether an inter-frequency co-coverage neighboring cell is configured for the cell where the Multi-Carrier Switch off Based on Traffic Load feature is set. If the neighboring cell is not configured, run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-frequency co-coverage neighboring cell. If the neighboring cell is configured, you can run the BSC6900 MML command MOD UINTERFREQNCELL to modify the related parameters.
Verification Procedure 1. 2. 3. Start alarm browsing on the BSC6900 LMT. Keep the total number of users at 0 in a cell (cell 1), or do not perform services in cell 1. When the time is within the time period specified in the activation procedure (for example, when it is ten past nine), If the alarm "UMTS Cell Unavailable" (ID: 22202) is reported for cell 1 as the cause of cell dynamic shutdown, you can infer that this feature is in effect. If the alarm "UMTS Cell Unavailable" (ID: 22202) is not reported for cell 1 or the cause of the alarm is not cell dynamic shutdown, you can infer that this feature is not in effect.
Deactivation Procedure 1. Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA. In this step, set Cell Dynamic ShutDown Switch For RNC to OFF(switch off) to deactivate this feature at the RNC. Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN to deactivate this feature at cell 1.
2. ----End
Example
/*Activating Multi-Carrier Switch off Based on Traffic Load*/ //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 set. Cell 1 and cell 2 in the following command are under 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; //Deactivating Multi-Carrier Switch off Based on Traffic Load //Deactivating Multi-Carrier Switch off Based on Traffic Load at the RNC
7-298
Issue 03 (2010-09-20)
SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=OFF; //Deactivating Multi-Carrier Switch off Based on Traffic Load at cell 1 RMV UCELLDYNSHUTDOWN: CellId=1;
7.162 Configuring Energy Efficiency Improved

This section describes how to activate, verify, and deactivate the optional feature WRFD-020118 Energy Efficiency Improved.
Prerequisite
l The network is ready. Table 7-5 describes the requirements on NEs. Table 7-5 Requirements on NEs NE CN RNC NodeB UE l The license is activated. Requirements None. None. The RRU3801C and MTRU do not support the energy efficiency improved feature. None.
Context
l RAN11.0 supports dynamic adjustment of power amplifier parameters only when there is no HSDPA service. If HSDPA services exist, the dynamic adjustment of power amplifier parameters cannot be enabled for RF modules. In RAN12.0, the algorithm for dynamic adjustment of power amplifier parameters is improved. By setting parameters for the energy efficiency improved feature in the HSDPA scenario, you can enable the equipment to automatically adjust the power amplifier parameters according to the traffic load. By doing this, efficiency is improved.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET OPTDYNADJPARA to set the dynamic voltage adjustment parameters. Set Dynamic Voltage Adjustment Switch to ON. Set Start Time and End Time as required. For example,
SET OPTDYNADJPARA: DYNADJSWITCH=ON, DYNADJSTARTTIME=0, DYNADJENDTIME=6;
Verification Procedure 1. Run the NodeB MML command DSP LICENSE to query the license information. According to the execution result displayed on the LMT, you can check the setting of the parameter DYNAMIC Voltage (Yes indicates that the function is activated. For example,
Issue 03 (2010-09-20)
7-299

DSP LICENSE:;
2.
Run the NodeB MML command LST OPTDYNADJPARA to list the dynamic voltage adjustment parameters. According to the execution result displayed on the LMT, you can check the setting of the parameters Dynamic Voltage Adjustment Switch (ON indicates that the function is activated), Start Time, and End Time. For example,
LST OPTDYNADJPARA:;
Deactivation Procedure 1. Run the NodeB MML command SET OPTDYNADJPARA to set Dynamic Voltage Adjustment Switch to OFF. For example,
SET OPTDYNADJPARA: DYNADJSWITCH=OFF;
----End
7.163 Configuring Multi-Carrier Switch off Based on Power Backup

This section describes how to activate, vertify, and deactivate the optional feature WRFD-020119 Multi-Carrier Switch off Based on Power Backup.
Prerequisite
l The network is ready. Table 7-6 describes the requirements on NEs. Table 7-6 Requirements on NEs NE CN RNC NodeB UE l Requirements None. None. None. None.
This feature has no license control items.
Context
In case of a main failure, the backup power system starts to operate. In this case, this feature can achieve hierarchical carrier shutdown based on the shutdown duration and cell priority.
Procedure
l Activation Procedure 1. Run the NodeB MML command MOD LOCELL to modify the local cells. For the cells that need continue services in the level 1 shutdown period, set Reserved Cell to TRUE.
7-300
For example,
MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, RSV=TRUE;
NOTE
It is recommended that at least one cell be reserved for a sector. In case of a main failure, this reserved cell retains services for the users in this sector.
2.
Run the NodeB MML command SET ITELSHUTDOWN to set the intelligent power management switch. Set ISD SWITCH to ENABLE. Set LEVEL1 DELAY(s) as required. The default value is 60 seconds. Set LEVEL2 DELAY(s) as required. The default value is 120 seconds.
3.
Optional: If you need to use the smooth power change function, run the NodeB MML command SET SMTHPWRSWTCH to set the intelligent power management switch. Set Smooth Power Change Function Switch to OPEN. For example,
SET SMTHPWRSWTCH: SWITCH=OPEN;
NOTE
Before a cell is shut down, the smooth power change function gradually reduces the TX power of the P-CPICH so that the services in the cell are handed over to neighboring cells. This prevents an abrupt cell shutdown from disrupting services.
Vertification Procedure 1. Run the NodeB MML command LST ITELSHUTDOWN to list the status of the intelligent power management switch. According to the execution result displayed on the LMT, you can check whether the parameters NodeB ISD Switch (ENABLE indicates that the function is enabled), Level 1 power off, and Level 2 power off are set correctly. For example,
LST ITELSHUTDOWN:;
2.
Run the NodeB MML command LST LOCELL to list the configuration information of the local cells. According to the execution result displayed on the LMT, you can check whether the Reserve Cell parameter is correctly set for each cell. For example,
LST LOCELL: MODE=LOCALCELL, LOCELL=1;
3.
Optional: If you use the smooth power change function, run the NodeB MML command LST SMTHPWRSWTCH to list the status of the intelligent power management switch. According to the execution result displayed on the LMT, you can check the setting of the parameter Smooth Power Change Function Switch (OPEN indicates that the function is enabled). For example,
LST SMTHPWRSWTCH:;
Deactivation Procedure 1. Run the NodeB MML command SET ITELSHUTDOWN to set the intelligent power management switch. Set ISD SWITCH to DISABLE. For example,
Issue 03 (2010-09-20)
7-301

SET ITELSHUTDOWN: ISD=DISABLE;
----End
7.164 Configuring AMR-WB (Adaptive Multi Rate Wide Band)

This section describes how to activate, verify, and deactivate the basic feature WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band).
Prerequisite
l l l l Dependency on Hardware The CN node must have the corresponding support capability. Dependency on Other Features None License The license is activated. Other Prerequisites The UE must have the corresponding support capability.
Context
This feature supports AMR-WB services so that telecom operators can improve the quality of speech services when resources are sufficient.
Procedure
7.165 Configuring AMR/WB-AMR Speech Rates Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020701 AMR/WB-AMR Speech Rates Control.
Prerequisite
l l
7-302

If this feature is to be applied to the AMR-WB, then the Dependency is: WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band). l l License The license is activated. Other Prerequisites The UE should support the processing of TFC control procedure.
Context
This feature enables the adjustment of AMR/AMR-WB speech rates triggered by multiple factors. This feature can ensure a continuous service, expand the service coverage, and reduce the cell load.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select CS_AMRC_SWITCH from the drop-down list CS algorithm switch. Run the BSC6900 MML command SET UQOSACT to set the QoS switches for AMR services to ON. Run the BSC6900 MML command SET UAMRC or SET UAMRCWB to set the RNC-level AMR/AMR-WB voice rate control parameters. Run the BSC6900 MML command SET UQUALITYMEAS or ADD UTYPRABQUALITYMEAS to set the parameters of RNC-level AMR/AMR-WB voice rate control based on link stability. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether CS_AMRC_SWITCH is selected from the drop-down list CS algorithm switch. Run the BSC6900 MML command LST UQOSACT to check whether the QoS switches for AMR or AMR WB services are set to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear CS_AMRC_SWITCH from the drop-down list CS algorithm switch.
2. l
----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; //Deactivating AMR/WB-AMR Speech Rates Control SET UCORRMALGOSWITCH: CsSwitch=CS_AMRC_SWITCH-0;
7.166 Configuring Overbooking on ATM Transmission

This section describes how to activate, verify, and deactivate the optional feature WRFD-050405 Overbooking on ATM Transmission.
Prerequisite
l Dependency on Hardware The backpressure and VP shaping mechanism especially requests ATM interface board (WOSEc board for BSC6800 & AOUa/UOIa/AEUa boards for BSC6900) to be installed in the RNC. The Iub connection to Node B shall be configured through the optical or electrical port. l l Dependency on Other Features None License The license is activated.
Context
This feature provides a method for greatly saving OPEX on ATM transmission, especially on Iub interface, and when deploying HSDPA high speed service. Services are admitted based on different activity factors, and admission of more services can be allowed to the bandwidth. Other strategies applied in overbooking are as follows: l l l RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm RNC Backpressure-Based Downlink Congestion Control Algorithm Shaping
Procedure
l Activating BSC6900 RLC Retransmission Rate-Based Downlink Congestion Control Algorithm 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the service flow control switch. For R99 BE services, set DRA_R99_DL_FLOW_CONTROL_SWITCH to ON. For HSDPA BE services, set DRA_HSDPA_DL_FLOW_CONTROL_SWITCH to ON. l Activating BSC6900 Backpressure-Based Downlink Congestion Control Algorithm 1. 2. Optional: Run the BSC6900 MML command ADD PORTFLOWCTRLPARA to configure the flow control parameters. Enable the flow control switch. You can run the BSC6900 MML command ADD/MOD IMAGRP, ADD/MOD UNILNK, ADD/MOD FRALNK, ADD/MOD ATMLOGICPORT, or SET OPT to enable the flow control switch. l Activating Shaping Function 1. 2. l Run the BSC6900 MML command ADD ATMLOGICPORT to add an ATM logical port (LP). Run the BSC6900 MML command ADD AAL2PATH to add the path to the LP. Set Bearing type to ATMLOGICPORT.
Verification Procedure Take RNC configured with the AOU interface board as an example to describe how to verify backpressure-based flow control.
7-304
Issue 03 (2010-09-20)
1.
Set the subscriber information in the HLR for R99 UE1. The traffic class is streaming service, and the maximum bit rate (MBR) is 384 kbit/s in the uplink and 384 kbit/s in the downlink. Set the subscriber information in the HLR for HSDPA UE2. The traffic class is background service, and the MBR is 384 kbit/s in the uplink and 1450 kbit/s in the downlink. Set all AAL2 paths to be added to IMA port, and enable the flow control switch of LP1. Enable UE1 and UE2 to stay in idle mode and camp on CELL_A11. CELL_A11 must support HSDPA services. Set the threshold of HSDPA BE services to 768 kbit/s. Enable uplink throughput and bandwidth of Uu, Iub, and Iu interface on the BSC6900 LMT. Dialing Test Activate PS streaming services on UE1 and keep downloading file from one FTP server. Activate PS BE services on UE2 and keep downloading file from one FTP server. Expected Result IMA port is not congested and UE1 downloads data at MBR. IMA port is congested and the backpressure function is triggered. The throughput of UE2 decreases and that of UE1 remains unchanged. -
2.
3. 4. 5. 6.
Release the services.
Deactivation Procedure Deactivating BSC6900 RLC Retransmission Rate-Based Downlink Congestion Control Algorithm 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the service flow control switch. For R99 BE services, set DRA_R99_DL_FLOW_CONTROL_SWITCH to OFF. For HSDPA BE services, set DRA_HSDPA_DL_FLOW_CONTROL_SWITCH to OFF.
Deactivating RNC Backpressure-Based Downlink Congestion Control Algorithm 1. Disable the flow control switch. You can run the BSC6900 MML command ADD/MOD IMAGRP, MOD UNILNK, MOD FRALNK, MOD ATMLOGICPORT, or SET OPT to disable the flow control switch.
----End
Example
//Verifying Overbooking on ATM Transmission ADD IMAGRP: SRN=0, SN=14, BT=AOUa, IMAGRPN=0, FLOWCTRLSWITCH=ON, FCINDEX=1; //Set all AAL2 paths to be added to IMA port//
Issue 03 (2010-09-20)
7-305
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D768; //Set the threshold of HSDPA BE services//
7.167 Configuring VoIP over HSPA/HSPA+

This section describes how to activate, verify, and deactivate the optional feature WRFD-010617 VoIP over HSPA/HSPA+.
Prerequisite
l l Dependency on Hardware This feature is dependant on the UE capability and the IP multimedia subsystem (IMS). Dependency on Other Features The configurations of the features on which this feature depends are complete. In the case of VoIP over HSPA, the following features should be activated in advance: WRFD-010610 HSDPA Introduction Package, WRFD-010612 HSUPA Introduction Package. In the case of VoIP over HSPA+, the following feature should be activated in advance: WRFD-010686 CPC-DTX/DRX. l l License The license is activated. The VoIP over HSPA/HSPA+ feature requires IMS. The IMS signaling transmission must be configured on the BSC6900BSC6900.
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 is significantly increased. When the Robust Header Compression (RoHC) technique is used, the data transmission efficiency of VoIP services is greatly improved.
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 Activation Procedure 1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set VOIP channel type to HSPA(UL_EDCH,DL_HSDSCH), and set IMS channel type to HSPA(UL_EDCH,DL_HSDSCH). In this manner, the uplink channel is EDCH and the downlink channel is HS-DSCH. (Optional) To enable the RoHC algorithm, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Channel Configuration Strategy Switch to CFG_PDCP_RFC3095_HC_SWITCH.
2.
7-306
3.
(Optional) If VoIP services need to use the WRFD-01061403 HSUPA 2ms TTI feature, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Service Mapping Strategy Switch to MAP_HSUPA_TTI_2MS_SWITCH, so that the HSUPA 2ms scheduling algorithm switch is turned on. Go to Step 4. (Optional) Run the BSC6900 MML command SET UFRC. In this step, set HSUPA TTI type of VOIP traffic to EDCH_TTI_2ms, so that the type of HSUPA TTI for VoIP services is set to 2ms TTI. (Optional) If the WRFD-01061404 HSUPA 2 ms/10 ms TTI HO feature needs to be used, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic Resource Allocation Switch to DRA_VOICE_TTI_RECFG_SWITCH, so that the voice service dynamic TTI adjustment switch is turned on. To configure the EPF scheduling strategy, run the NodeB MML command SET MACHSPARA to set the parameter Scheduling Method to EPF(Enhanced PF). 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 expanded 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 7-58 to trace Uu interface signaling messages.
4.
5.
6. l
2.
Analyze the traced messages. If the data traced on the Uu interface is shown in Figure 7-59, you can infer that the UE is in CELL_DCH state.
Issue 03 (2010-09-20)
7-307
If the data traced on the Uu interface is shown in Figure 7-60, you can infer that VoIP services are established on the HSPA/HSPA+. Figure 7-59 UE in CELL_DCH state
Figure 7-60 VoIP services established on the HSPA/HSPA+
3.
If VoIP services are carried on the HSPA or HSPA+, trace the RRC_RB_SETUP or RRC_RB_RECFG message on the Uu interface to view the type of carried TTI, as shown in Figure 7-61. Figure 7-61 Type of TTI carried in the message
NOTE
The services admitted before the deactivation of this feature are not affected. The services admitted after the deactivation will not use this feature.
1.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set VOIP channel type to DCH(UL_DCH,DL_DCH), and set IMS channel type to DCH(UL_DCH,DL_DCH), so that the uplink of the VoIP/IMS transmission channel is UL_DCH and the downlink is DL_DCH.
----End
Example
//Activating VoIP over HSPA/HSPA+ /*BSC6900 side*/ SET UFRCCHLTYPEPARA: VoipChlType=HSPA, ImsChlType=HSPA //Enabling RoHC algorithm SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-1; //Enabling HSUPA 2ms scheduling algorithm SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; //Setting HSUPA TTI of VoIP services to 2ms TTI SET UFRC: VoipHsupaTti=EDCH_TTI_2ms; //Enabling voice service dynamic TTI adjustment algorithm SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_TTI_RECFG_SWITCH-1; //Configuring the EPF scheduling strategy on NodeB SET MACHSPARA: SM=EPF; //Deactivating VoIP over HSPA/HSPA+ SET UFRCCHLTYPEPARA: VoipChlType=DCH, ImsChlType=DCH;
7.168 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.
Prerequisite
l l Dependency on Hardware The CN and UE must support VoIP. Dependency on Other Features The configurations of the features on which this feature depends are complete. VoIP over HSPA rely on: WRFD-010611 HSDPA Enhanced Package and WRFD-010612 HSUPA Introduction Package. VoIP over HSPA+ rely on: WRFD-010611 HSDPA Enhanced Package and WRFD-010686 CPC- DTX/DRX. l License The license is activated.
Context
RAN10.0 support 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
Issue 03 (2010-09-20)
1. l
Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling Method to EPF. Run the NodeB MML command LST MACHSPARA to query the configuration result. Use UE 1 to initiate a VoIP service, and then use UE 2 to initiate a BE service. Deteriorate the signal quality in the cell gradually until congestion occurs in the downlink. Check the services of the two UEs. You can find that the service rate of UE 2 decreases whereas the speech quality of UE 1 remains good. Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling Method to MAX CI, RR, or PF.
----End
Example
//Activating optimized scheduling for VoIP over HSPA SET MACHSPARA: SM=EPF; //Deactivating optimized scheduling for VoIP over HSPA SET MACHSPARA: SM=PF;
7.169 Configuring IMS Signaling over HSPA

This section describes how to activate, verify, and deactivate the basic feature WRFD-010618 IMS Signaling over HSPA.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features 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. l l License The license is activated. Other Prerequisites The CN and UE must support this feature.
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. Note that this feature requires that the UE should support IMS signaling over HSPA.
Procedure
l
7-310
1. l
Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set IMS channel type to HSPA. Run the BSC6900 MML command LST UFRCCHLTYPEPARA to verify that IMS channel type is set to HSPA. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set IMS channel type to DCH.
----End
Example
//Activating IMS Signaling over HSPA. SET UFRCCHLTYPEPARA: ImsChlType=HSPA; //Verifying IMS Signaling over HSPA. LST UFRCCHLTYPEPARA:; //Deactivating IMS Signaling over HSPA. SET UFRCCHLTYPEPARA: ImsChlType=DCH;
7.170 Configuring PDCP Header Compression (RoHC)

This section describes how to activate, verify, and deactivate the optional feature WRFD-011501 PDCP Header Compression (RoHC).
Prerequisite
l l l Dependency on Hardware The UE supports this feature. Dependency on Other Features None License The license is activated.
Context
PDCP header compression (RoHC) mainly applies to VoIP services and it can decrease the overhead of IP data. This feature provides the IP data header compression mechanism which aims to save the bandwidth of the Uu interface, and thus reduces occupancy of radio resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Channel configuration strategy switch to CFG_PDCP_RFC3095_HC_SWITCH. Start UE tracing on the BSC6900 LMT. Establish a PS service on the UE. Observe the CRLC _SETUP_REQ message in the traced UE data. Check the bit1RfcInfo3095 IE in the following path in the message: pdcpSetupInfo > pdcpInfo > pdcpInfoBmp > bit1RfcInfo3095.
Issue 03 (2010-09-20)
If the value of the bit1RfcInfo3095 IE is 1, you can infer that this feature has been activated. If the value of the bit1RfcInfo3095 IE is 0, you can infer that this feature has not been activated. l Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect CFG_PDCP_RFC3095_HC_SWITCH from Channel configuration strategy switch.
----End
Example
//Activating PDCP Header Compression (RoHC) SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-1; //Deactivating PDCP Header Compression (RoHC) SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-0;
7.171 Configuring CS Voice over HSPA/HSPA+

This section describes how to activate, verify, and deactivate the optional feature WRFD-010619 CS Voice over HSPA/HSPA+.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature In the case of CS service over HSPA, the following features should be activated in advance: 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 CS service over HSPA+, the following feature should be activated in advance: WRFD-010686 CPC-DTX/DRX. l l License The license is activated. Other Prerequisites The UE must be Release-8 (or later) and support CS voice over HSPA/HSPA+. The BSC6900 and NodeB software versions should be no earlier than RAN11.0.
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.
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 Activation Procedure 1. 2. Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set CS voice channel type to HSPA(UL EDCH,DL HSDSCH). Optional: If CS voice services need to be carried on the 2 ms Transmission Time Interval (TTI), run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Service mapping strategy switch to MAP_HSUPA_TTI_2MS_SWITCH. Go to Step 3. Optional: Run the BSC6900 MML command SET UFRC. In this step, set HSUPA TTI type of CS voice traffic to EDCH_TTI_2ms. Optional: If the dynamic adjustment of CS voice services over HSUPA from 2 ms TTI to 10 ms TTI needs to be used, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic resource allocation switch to DRA_VOICE_TTI_RECFG_SWITCH. To configure the EPF scheduling strategy, run the NodeB MML command SET MACHSPARA to set the parameter Scheduling Method to EPF(Enhanced PF). 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 expanded 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 7-62 to trace Uu interface signaling messages.
3. 4.
5. l
Issue 03 (2010-09-20)
7-313
2.
Analyze the traced messages. If the data traced on the Uu interface is shown in Figure 7-63, you can infer that the UE is in CELL_DCH state. If the data traced on the Uu interface is displayed, as shown in Figure 7-64, you can infer that CS voice services are established on the HSPA/HSPA+. Figure 7-63 UE in CELL_DCH state
Figure 7-64 CS voice services established on the HSPA/HSPA+
3.
If CS voice services are carried on the HSPA or HSPA+, trace the RRC_RB_SETUP or RRC_RB_RECFG message on the Uu interface to view the type of carried TTI, as shown in Figure 7-65.
7-314
Issue 03 (2010-09-20)
Figure 7-65 Type of TTI carried in the message
NOTE
The services admitted before the deactivation of this feature are not affected. The services admitted after the deactivation will not use this feature.
1. ----End
Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the parameter CS voice channel type to DCH(UL_DCH,DL_DCH).
Example
//Activating CS Voice over HSPA/HSPA+. SET UFRCCHLTYPEPARA: CSVoiceChlType =HSPA; SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; SET UFRC: CSVoiceHsupaTti=EDCH_TTI_2ms; SET UCORRMALGOSWITCH DraSwitch= DRA_VOICE_TTI_RECFG_SWITCH-1; SET MACHSPARA: SM=EPF; //Deactivating CS Voice over HSPA/HSPA+. SET UFRCCHLTYPEPARA: CSVoiceChlType=DCH;
7.172 Configuring Cell ID + RTT Function-Based LCS

This section describes how to activate, verify, and deactivate the optional feature WRFD-020801 Cell ID + RTT Function Based LCS.
Prerequisite
l l l l Dependency on Hardware If SAS-CENTRIC locating is required, SAS equipment must be configured. Dependency on Other Features None License The license is activated. Others The NodeB and the BSC6900 software versions must be RAN3.0 or later, and the BSC6900 supports "Cell ID + RTT Function Based LCS" function. 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 + RTT locating method is to directly use the geographical center of the coverage area of the reference cell as the locating result. If the CN requires a high locating accuracy in the locating request, 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 can calculate the distance between a certain cell and the UE. If three TOA circles intersect, the BSC6900 can calculate the accurate location of the UE.
Procedure
l Activation Procedure 1. 2. 3. Optional: If inter-RNC locating is required, the Iur interface needs to be configured. See 7.176 Configuring LCS over Iur. Optional: If SAS-CENTRIC mode needs to be supported, the Iupc interface is required. See 7.177 Configuring Iupc Interface for LCS Service. Run the BSC6900 MML command SET USMLC to configure the parameters for the SMLC algorithm. In this step, set UE Positioning Method, CELLID+RTT Method Type, and Location Working Mode. Run the BSC6900 MML command ADD USMLCCELL to set the location information parameters of the cell. In this step, set Cell Location Setting Type, geographical location information of antenna and cell coverage information . Set geographical location information about the antenna. Cell Antenna Latitude Cell Antenna Altitude Cell Antenna Longitude Set cell coverage information. Cell Antenna Max Coverage Cell Antenna Orientation Cell Antenna Opening l Verification Procedure 1. Check whether the parameters that are required for successful locating are correctly set. Run the BSC6900 MML command LST USMLC to query the parameters of the SMLC algorithm. Run the BSC6900 MML command LST USMLCCELL to query the location information parameters of the cell. 2. Initiate Iu, Iub, and Uu interface tracing, as shown in Figure 7-66, Figure 7-67 and Figure 7-68 respectively.
4.
7-316
Issue 03 (2010-09-20)
Figure 7-66 Iu interface trace dialog box
Figure 7-67 Iub interface trace dialog box
Issue 03 (2010-09-20)
7-317
Figure 7-68 Uu interface trace dialog box
3. 4.
Use a UE to access the cell and enable the CN to send a locating request. From the Iu interface, you can see the Location Reporting Control and Location Report messages, as shown in Figure 7-69 and Figure 7-70. Figure 7-69 Location reporting control
7-318
Issue 03 (2010-09-20)
Figure 7-70 Location report
5.
From the Iub interface, you can see that all the links in the active set have the Dedicated Measurement Initiation process, where Dedicated Measurement Type is Round Trip Time, as shown in Figure 7-71 and Figure 7-72.
Issue 03 (2010-09-20)
7-319
Figure 7-71 Dedicated measurement type
Figure 7-72 Round trip time
6.
From the Uu interface, you can see the information about the UE Rx-Tx time difference measurement, which is a type of internal measurement (if UE supports UE Rx-Tx time difference type 2 measurement, locating measurement of Rx-Tx time difference type 2 measurement is adopted), as shown in Figure 7-73 and Figure 7-74.
7-320
Issue 03 (2010-09-20)
Figure 7-73 UE Rx-Tx time difference
Figure 7-74 UE Rx-Tx time difference type 1
Deactivation Procedure 1. Run the BSC6900 MML command SET USMLC to deactivate CELLID + RTT locating.
----End
Example
//Activating Cell ID + RTT Function Based LCS //Set the parameters of the SMLC algorithm SET USMLC: SmlcMethod=CELLID_RTT-1, CELLIDRTTMethodType=UE_ASSISTED, ForcedSHOSwitch=ON, IntraRelThdFor1A=2, IntraRelThdFor1B=2, TrigTime1A=D10, TrigTime1B=D10, SHOQualmin=-20, LcsWorkMode=RNC_CENTRIC; //Set the location information parameters of the cell 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;
Issue 03 (2010-09-20)
7-321

//Deactivating Cell ID + RTT Function Based LCS SET USMLC: SmlcMethod=CELLID_CENTER-0;
7.173 Configuring OTDOA-Based LCS

This section describes how to activate, verify, and deactivate the optional feature WRFD-020802 OTDOA Based LCS.
Prerequisite
l l l l Dependency on Hardware The NodeB is configured with USCU board that is equipped with GPS. Dependency on Other Features None License The license is activated. Others The BSC6900 supports this feature. The CN can initiate positioning requests. 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, the BSC6900 initiates and traces the SFN-SFN observed time difference measurement. The BSC6900 can calculate the relative time difference (RTD) of the cell related to positioning based on the latest measurement reports (MRs). After the BSC6900 receives a Location 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, the BSC6900 calculates the location of the UE. For accurate location calculation, the BSC6900 may request the NodeB to perform RTT measurement or request the UE to perform Rx-Tx time difference measurement.
Procedure
l Activation Procedure 1. 2. Optional: If inter-RNC positioning is required, configure the Iur interface by referring to 7.176 Configuring LCS over Iur. Run the BSC6900 MML command SET USMLC to set the SMLC algorithm parameters. In this step, set UE Positioning Method and Location Working Mode.
NOTE
Location Working Mode must be set to RNC_CENTRIC(RNC CENTRIC Mode).
7-322
Issue 03 (2010-09-20)
3.
Run the BSC6900 MML command ADD USMLCCELL to add the location information about a cell. In this step, set Cell Location Setting Type, geographical location information about the antenna , and cell coverage information . Set geographical location information about the antenna. Cell Antenna Latitude Cell Antenna Altitude Cell Antenna Longitude Set cell coverage information. Cell Antenna Max Coverage Cell Antenna Orientation Cell Antenna Opening
4.
Run the BSC6900 MML command ADD UCELLGPSFRMTIMING to set the parameters related to UTRAN GPS cell frame timing measurement. In this step, set Cell ID and GPS Frame Timing Active Flag. Check whether the parameters required for positioning are correctly set. Run the BSC6900 MML command LST USMLC to query the SMLC algorithm parameters. 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.
Deactivation Procedure 1. Run the BSC6900 MML command SET USMLC to deactivate the OTDOA-based location service.
----End
Example
//Activating OTDOA Based LCS //Set the parameters of the SMLC algorithm SET USMLC: SmlcMethod=OTDOA-1, OTDOAMethodType=UE_BASED, LcsWorkMode=RNC_CENTRIC; //Set the location information parameters of the cellADD 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; //Set the parameters of UTRAN GPS cell frame timing measurement ADD UCELLGPSFRMTIMING: CellId=80, StartFlag=ACTIVE; //Deactivating OTDOA Based LCS SET USMLC: SmlcMethod=OTDOA-0;
Issue 03 (2010-09-20)
7-323
7.174 Configuring A-GPS-Based LCS

This section describes how to activate, verify, and deactivate the optional feature WRFD-020803 A-GPS Based LCS.
Prerequisite
l Dependency on Hardware If a GPS receiver needs to be configured on the BSC6900 side, the BSC6900 must be configured with the GCGa board. If the SAS-CENTRIC location service is required, the BSC6900 should be configured with an SAS device. If a GPS receiver (in RNC-CENTRIC mode) needs to be 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 correctly installed and connected. l l l Dependency on Other Features None License The license is activated. Others The BSC6900 supports this feature. The UE supports UE-based A-GPS positioning or UE-assisted A-GPS positioning or both. The CN can trigger 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, reduce positioning time, and save power. The location information about the GPS reference receiver can be automatically searched by the reference receiver itself or be configured by users. l If the accurate location information (to be provided by the surveying and mapping authorities) about the antenna of the GPS reference receiver can be obtained, it is recommended that the information be specified when the receiver is being configured. By doing this, the 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 reference receiver cannot be obtained, the auto search mode can be selected.
NOTE
The BSC6900 and NodeB must be configured with the related data to activate this feature.
Procedure
l Activation Procedure Activation Procedure on the BSC6900 Side
1. 2.
Optional: If inter-RNC positioning is required, configure the Iur interface by referring to 7.176 Configuring LCS over Iur. Optional: If the GPS positioning method in SAS-CENTRIC mode is required, configure the Iu-PC interface by referring to 7.177 Configuring Iupc Interface for LCS Service. 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. Run the BSC6900 MML command SET USMLC to set the SMLC algorithm parameters. In this step, set UE Positioning Method and Location Working Mode. Run the BSC6900 MML command ADD USMLCCELL to add the location information about a cell. In this step, set Cell Location Setting Type, geographical location information about the antenna and cell coverage information. Set geographical location information about the antenna. Cell Antenna Latitude Cell Antenna Altitude Cell Antenna Longitude Set cell coverage information. Cell Antenna Max Coverage Cell Antenna Orientation Cell Antenna Opening
3.
4.
5.
6.
In RNC-CENTRIC mode, run the command ADD GPS to set the parameters related to the GPS reference receiver. In this step, set GPS ID, GPS type, GPS antenna latitude, GPS antenna longitude, and GPS antenna altitude. In RNC-CENTRIC mode, run the command ACT GPS to activate the specified GPS reference receiver. In this step, set AGPS ID and Type. Optional: Run the ADD UCELLGPSFRMTIMING to set the parameters related to UTRAN GPS cell frame timing measurement. In this step, set Cell ID and GPS Frame Timing Active Flag.
7. 8.
Activation Procedure on the NodeB Side

NOTE
In RNC-CENTRIC mode, a GPS reference 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 correctly installed and connected.
1.
Run the NodeB MML command ADD BRD to add a USCU board. Set the Cabinet No (CN), Subrack No (SRN), and Slot No (SN) based on the actual location of the USCU board. Set the Board Type (BT) to USCU.
2.
Run the NodeB MML command ADD NGRU to add a GPS reference receiver. (1) Set the Way to Get Position (WPOS).
Issue 03 (2010-09-20)
7-325
If the WPOS is set to USER_CONFIG, you need to set the GPS Antenna Longitude (LONGITUDE), GPS Antenna Latitude (LATITUDE), and GPS Antenna Altitude (ALTITUDE). If the WPOS is set to SEARCH_WITH_DURATION, you need to set the Duration (DURATION). If the WPOS is set to SEARCH_WITH_PRECISION, you need to set the Precision (PRECISION). (2) Set the GPS delay parameter Clock Offset (DELAY). If the Way to Get Position (WPOS) has been set to auto search when you run the ADD NGRU command, it is recommended that the GPS receiver be configured with the obtained location information through the MML command MOD NGRU after the location of the receiver is locked up. In this way, the GPS receiver does not have to search for the location upon restart. l Verification Procedure Verification Procedure on the BSC6900 Side 1. 2. 3. 4. Run the BSC6900 MML command LST USMLC to query the settings of the SMLC algorithm parameters. Run the BSC6900 MML command LST USMLCCELL to query the location parameter settings of a cell. In RNC-CENTRIC mode, run the BSC6900 MML command LST GPS to query the configuration about the GPS reference receiver. Optional: If UTRAN GPS cell frame timing measurement is configured, run the BSC6900 MML command LST UCELLGPSFRMTIMING to query the parameter settings of UTRAN GPS cell frame timing measurement. In RNC-CENTRIC mode, run the BSC6900 MML command DSP UGPSDATA to query the GPS assistance data. Initiate Iu and Uu interface tracing, as shown in Figure 7-75 and Figure 7-76 respectively.
5. 6.
7-326
Issue 03 (2010-09-20)
Figure 7-75 Iu Interface Trace dialog box
7. 8.
Make a UE access the network and enable the CN to send a positioning request. The Iu tracing messages include the Location Reporting Control and Location Report messages, as shown in Figure 7-77 and Figure 7-78 respectively.
Issue 03 (2010-09-20)
7-327
Figure 7-77 Location reporting control
7-328
Issue 03 (2010-09-20)
Figure 7-78 Location report
9.
The Uu tracing messages contain the information about A-GPS positioning measurement, as shown in Figure 7-79 and Figure 7-80. Figure 7-79 ue-positioning-GPS-AssistanceData
Issue 03 (2010-09-20)
7-329
Figure 7-80 GPS-MeasurementParam
Verification Procedure on the NodeB Side 1. Run the NodeB MML command DSP BRD, and then check whether the USCU board and the GPS reference receiver are normal, based on the command execution results displayed on the LMT. Run the NodeB MML command DSP NGRU, and then check whether the location of the GPS reference receiver is locked up and whether the operating status of the receiver is normal, based on the command execution results displayed on the LMT. Run the BSC6900 MML command SET USMLC to deactivate the A-GPS location service.
2.
----End
Example
//Activating A-GPS Based LCS //BSC6900 Side //Set the type of BSC6900 clock board to GCGa SET CLKTYPE:CLKTYPE=GCGa; //Set the parameters of the SMLC algorithm SET USMLC: SmlcMethod=AGPS-1, AGPSMethodType=UE_ASSISTED, UeBasAgpsAssDataSwitch=REFERENCE_TIME_FOR_GPS-1&REFERENCE_LOCATION_FOR_GP S-1&DGPS_CORRECT-1&GPS_IONOSPHERIC_MODEL-1&GPS_NAVGMODEL-1&GPS_UTC_MODEL1&GPS_ALMANAC-1&GPS_ACQ_ASSIST-1&GPS_REALTIME_INTEGRITY-1;LcsWorkMode=RNC _CENTRIC; //Set the location information parameters of the cell 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;
7-330
Issue 03 (2010-09-20)
//Set the parameters of the A-GPS reference receiver ADD GPS: AGPSRECEIVERID=0, AGPSRECEIVERTYPE=RNC, GCDF=DEG, MTRLGY=MET, LATITUDE=31243596, LONGITUDE=121590603, ALTITUDE=20; //Set the parameters of the A-GPS reference receiver ADD GPS: AGPSRECEIVERID=0, AGPSRECEIVERTYPE=NODEB, CellId=82, GCDF=DEG, MTRLGY=MET, LATITUDE=31243596, LONGITUDE=121590603, ALTITUDE=20; //Activate the specified A-GPS reference receiver ACT GPS: AGPSRECEIVERID=0, ACTTYPE=BOTH; //Set the parameters of UTRAN GPS cell frame timing measurement ADD UCELLGPSFRMTIMING: CellId=80, StartFlag=ACTIVE; //Deactivating A-GPS Based LCS SET USMLC: SmlcMethod=AGPS-0;
7.175 Configuring LCS Classified Zone

This section describes how to activate, verify, and deactivate the optional feature WRFD-020804 LCS Classified Zone.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Others The CN must support this feature.
Context
This feature defines a restricted area. Once the UE enters or leaves the restricted area, the RNC automatically reports the service area identity (SAI).
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCZ to add a classified zone.
NOTE
l In this step, you need to set Cn Operator Index, Location Area Code, Service Area Code, and Classified Zone ID. More than one classified zones can be set for one operator. l Before running the ADD UCZ command, ensure that Location Area Code and Service Area Code are configured at the local RNC. Otherwise, the classified zone cannot be configured.
Verification Procedure 1. Trace messages on the Iu interface on the BSC6900 LMT, as shown in Figure 7-81.
Issue 03 (2010-09-20)
Figure 7-81 Message Tracing on the Iu Interface
2.
Establish a service of any type on the UE. 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). Add cell B to the active set. If you find a LOCATION REPORT message from the data traced on the Iu interface, you can infer that this feature has been activated. If you find that the NAS cause is "user-restriction-start-indication", you can infer that the UE enters the classified zone. You can also find the SAI of the current cell from the message, as shown in Figure 7-82.
7-332
Issue 03 (2010-09-20)
Figure 7-82 LOCATION REPORT
3.
Remove cell B from the active set by, for example, performing a handover or SRNS relocation. If you find a LOCATION REPORT message from the data traced on the Iu interface, you can infer that this feature has been activated. If you find that the NAS cause is "user-restriction-end-indication", you can infer that the UE moves out of the classified zone. You can also find the SAI of the current cell from the message.
Deactivation Procedure 1. Run theBSC6900 MML command RMV UCZ. In this step, remove the classified zones for all operators. Then, the LCS Classified Zone feature is deactivated.
----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;
7.176 Configuring LCS over Iur

This section describes how to activate, verify, and deactivate the optional feature WRFD-020805 LCS over Iur.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020801 Cell ID + RTT Function Based LCS or WRFD-020803 A-GPS Based LCS. l l License The license is activated. Other Prerequisites The UE and the neighboring RNC must support this feature. To support the A-GPS location method, the UE must support the A-GPS measurement. To support the A-GPS location method, the neighboring RNC must be configured with an A-GPS receiver.
Context
With the LCS over Iur feature, Huawei RAN can provide location services (LCS) through the Iur interface to extend the LCS area. This feature enables exchange of cell information and GPS assistance information over the Iur interface and supports the dedicated measurement on the Iur interface.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UIURCOMMSCCP to BSC6900specify the MPU subsystem for information exchange. In this step, you need to set the subrack number and slot number of the MPU subsystems.
NOTE
You need to set the location methods and add the geographical information of the cell at the RNC. For cell information exchange over the Iur interface, you need to configure the geographical information about the neighboring cell that is configured at the neighboring RNC. Assume that the BSC6900 needs to support WRFD-020803 A-GPS Based LCS and WRFD-020805 LCS over Iur.
2. 3.
Optional: To support the SAS-CENTRIC mode, you need to configure the Iupc interface, as shown in 7.177 Configuring Iupc Interface for LCS Service. To support the RNC-CENTRIC mode and configure the GPS receiver on the BSC6900, you need to run the BSC6900 MML command SET CLKTYPE to set the clock board type to the GCGa on the BSC6900. Run theBSC6900 MML command SET USMLC to set the SMLC algorithm parameters. In this step, set UE Positioning Method and Location Working Mode. Run the BSC6900 MML command ADD USMLCCELL to set cell location parameters. In this step, set Cell Location Setting Type, geographical location information of the antenna such as Cell Center Longitude, Cell Center Latitude, and Cell Center Altitude, cell coverage information such as Cell Antenna Max Coverage, Cell Antenna Opening , and Cell Center Orientation Of Major Axis. To enable the exchange of the GPS information over the Iur feature in RNC-CENTRIC mode, run the BSC6900 MML command ADD GPS to add a GPS receiver at the
4.
5.
6.
7-334
neighboring RNC. In this step, set GPS type to NRNC_RNC (Neighboring RNC), indicating that the GPS receiver is installed on the neighboring RNC.
NOTE
l If the GPS receiver at the neighboring RNC is installed on the NodeB, set GPS type to NRNC_NODEB (NodeB in Neighboring RNC). l Before configuring a GPS receiver at the neighboring RNS, ensure that the GPS receiver is installed at the neighboring RNS and the ADD GPS command is executed at the neighboring RNC to add the GPS receiver (GPS type is set to RNC(Local RNC) or NODEB(NodeB in Local RNC) indicating that the GPS receiver is installed on the RNC or the NodeB).
7. 8.
Run the BSC6900MML command ACT GPS to activate the GPS receiver. Optional: Run the ADD UCELLGPSFRMTIMING command to set parameters related to periodic frame measurement of the UTRAN GPS cell. In this step, set Cell ID and GPS Frame Timing Active Flag. Trace messages on the Iur interface on the BSC6900 LMT, as shown in Figure 7-83. Figure 7-83 Message Tracing on the Iur Interface
2.
Observe the information traced on the Iur interface. You can find an information exchange initiation procedure. In this case, the local RNC sends the neighboring RNC an INFORMATION EXCHANGE INITIATION REQUEST message, in which Information Type is GPS information. The neighboring RNC sends the local RNC an NFORMATION EXCHANGE INITIATION REPONSE and INFORMATION REPORT messages, which contain the GPS assistance data, as shown in Figure 7-84.
Issue 03 (2010-09-20)
7-335
Figure 7-84 GPS assistance data
NOTE
You can see the INFORMATION EXCHANGE INITIATION REQUEST and INFORMATION EXCHANGE INITIATION REPONSE messages only after the ACT GPS command is executed.
3. 4. 5.
Establish a service of any type, and then perform a soft handover over the Iur interface. Send a LOCATION REPORTING CONTROL message of DIRECT type from the CN. Observe the information traced on the Iur interface. You can find an information exchange initiation procedure. In this procedure the local RNC sends the neighboring an INFORMATION EXCHANGE INITIATION REQUEST, in which Information Type is UTRAN Access Point Position with Altitude, as shown in Figure 7-85. The neighboring RNC sends the local RNC an INFORMATION EXCHANGE INITIATION REPONSE, which contains the geographical information about the neighboring cell over the Iur interface, as shown in Figure 7-86.
7-336
Issue 03 (2010-09-20)
Figure 7-85 INFORMATION EXCHANGE INITIATION REQUEST
Figure 7-86 INFORMATION EXCHANGE INITIATION RESPONSE
6.
Observe the information traced on the Iur interface, you can find the DEDICATED MEASUREMENT INITIATION REQUEST and DEDICATED MEASUREMENT INITIATION RESPONSE messages, as shown in Figure 7-87 and Figure 7-88 respectively. As indicated in the DEDICATED MEASUREMENT INITIATION REQUEST message, Dedicated Measurement Type is Round Trip Time.
Issue 03 (2010-09-20)
7-337
Figure 7-87 DEDICATED MEASUREMENT INITIATION REQUEST
Figure 7-88 DEDICATED MEASUREMENT INITIATION RESPONSE
Deactivation Procedure 1. Run the BSC6900 MML command DEA GPS to deactivate the GPS receiver. Alternatively, run theRMV GPS command to remove the GPS receiver of the neighboring RNC. Then, the GPS information exchange over the Iur interface is disabled.
7-338
Issue 03 (2010-09-20)
2. ----End
Run the BSC6900 MML command RMV UIURCOMMSCCP to deactivate the LCS over Iur feature.
Example
//Activating the LCS over Iur feature 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; ACT GPS: AGPSRECEIVERID=0, ACTTYPE=BOTH; SET USMLC: SmlcMethod=CELLID_RTT-1&OTDOA-0&AGPS-0; ADD USMLCCELL: RNCId=29, CellId=1, CellLocCfgType=CELL_ANTENNA, GCDF=DEG, MTRLGY=MET, AntennaLatitudeDegree=31245560, AntennaLongitudeDegree=121588234, AntennaAltitudeMeter=20, MaxAntennaRange=2000, AntennaOrientation=0, AntennaOpening=1200; CellAverageHeight=25; ADD USMLCCELL: RNCId=250, CellId=12, CellLocCfgType=CELL_ANTENNA, GCDF=DEG, MTRLGY=MET, AntennaLatitudeDegree=31245540, AntennaLongitudeDegree=121588231, AntennaAltitudeMeter=20, MaxAntennaRange=2000, AntennaOrientation=0, AntennaOpening=1200; CellAverageHeight=25; //Deactivating LCS over Iur. RMV GPS: AGPSRECEIVERID=0;
7.177 Configuring Iupc Interface for LCS Service

This section describes how to activate, verify, and deactivate the optional feature WRFD-020807 Iupc Interface for LCS service.
Prerequisite
l Dependency on Hardware IP interface boards of BSC6900support this feature. Stand Alone SMLC (SAS) is configured. l Dependency on Other Features The configurations of the features on which this feature depends are complete. The features on which this feature depends are determined by the location algorithms adopted by the operator: When the operator employs the Cell ID+RTT algorithm, the feature WRFD-020801 Cell ID + RTT Function Based LCS is needed. When the operator employs the A-GPS algorithm, the feature WRFD-020803 AGPS Based LCS is needed. l l License The license is activated. Other Prerequisites The UE supports at least one of the following location methods: UE-assisted CELLID + RTT location
UE-based A-GPS location UE-assisted A-GPS location The global data is configured. The procedure is as follows: 1. 2. 3. 4. Configuring the Basic Data Configuring the OPC and DPC Configuring the Area Information Configuring the M3UA Local and Destination Entities
The data at the physical layer and data link layer are configured. The procedure is as follows: 1. 2. 3. 4. Configuring the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/ GOUc Board Configuring the Physical Layer and Data Link Layer for the PEUa Board Configuring the Physical Layer and Data Link Layer for the POUa/POUc Board Configuring the User Plane of the Iub Interface (over ATM)
Context
Only IP transmission can be applied between the BSC6900and 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 between the BSC6900 and the SAS. 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 Activation Procedure (Configuring the Iupc Interface) 1. 2. Run the BSC6900 MML command ADD N7DPC to add the destination signaling point (DSP) data that corresponds to the SAS. Run the BSC6900 MML command ADD M3LE and ADD M3DE to add the M3UA local entity (M3LE) and the M3UA destination entity (M3DE) that correspond to the SAS respectively. Run the BSC6900MML command ADD SCTPLNK to add an SCTP link. To add more SCTP links, repeat this command. 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 M3LKSto add an M3UA link set. When Local entity type is set to M3UA_IPSP, set Work mode to M3UA_IPSP. When Local entity type is set to M3UA_ASP, set Work mode to M3UA_IPSP if Destination entity type is set to M3UA_SP. When Local entity
3.
type is set to M3UA_ASP, set Work mode to M3UA_ASP if Destination entity type is not set to M3UA_SP. 5. 6. 7. 8. Run the BSC6900 MML command ADD M3RT to add an M3UA route. Run the BSC6900 MML command ADD M3LNK to add an M3UA link. To add more M3UA links, repeat this command. Run the BSC6900 MML command ADD USAS to add an SAS. Run the BSC6900 MML command SET USMLC to enable the SAS-CENTRIC locating function and to enable the CELLID + RTT locating function or AGPS function. For details, see 7.172 Configuring Cell ID + RTT Function-Based LCS and 7.174 Configuring A-GPS-Based LCS. For details, see 7.172 Configuring Cell ID + RTT Function-Based LCS and 7.174 Configuring A-GPS-Based LCS. For details, see 7.172 Configuring Cell ID + RTT Function-Based LCS and 7.174 Configuring A-GPS-Based LCS.
----End
Example
//Activating Iupc Interface for LCS service ADD N7DPC:DPX=4, SPDF=WNF, DPC=8345, STP=OFF, SLSMASK=B0000, NEIGHBOR=YES, NAME="SAS", DPCT=IUPC, PROT=ITUT, BEARTYPE=M3UA, SPX=4; ADD M3LE:LENO=0, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME="IUPC", SPX=4; ADD M3DE:DENO=0, LENO=0, DPX=4, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME="IUPC"; 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; ADD M3LKS: SIGLKSX=0, DENO=0, NAME="IUPC"; ADD M3RT: DENO=0, SIGLKSX=0, NAME="IUPC"; ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=0, SCTPLNKN=0, NAME="IUPC"; ADD USAS: CnOpIndex=0, SasId=0, Dpx=4; SET USMLC: SmlcMethod=CELLID_RTT-1, AGPSMethodType=UE_ASSISTED, LcsWorkMode=SAS_CENTRIC;
7.178 Configuring RAN Sharing Introduction Package Package

This section describes how to activate, verify and deactivate the optional feature WRFD-021304 RAN Sharing Introduction Package.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features This feature is mutually exclusive to the feature WRFD-021311 MOCN Introduction Package.
Context
This feature enables multiple operators to share the same RAN equipment and have their own independent cells. The same RAN equipment can provide different operators with rich and personalized services.
Procedure
l Activation Procedure The theoretical UE peak rate reaches 21 Mbit/s when the UE services are carried on 64QAM and the following conditions are met: 1. 2. 3. 4. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to configure the basic information about the RNC. Run the BSC6900 MML command ADD UCNOPERATOR to configure the information about the primary and secondary operators. Run the BSC6900 MML command ADD UCNOPERGROUP to configure an operator group for the primary and secondary operators respectively. Run the BSC6900 MML command to add Iu interface-related configurations to operators 0 and 1 respectively. The following takes Iu over ATM as an example. Configure the N7DPC, CN NODE, SAAL/MTP3B link/MTP3B route, IuCS AAL2, and IuPS IPOA. 5. Run the BSC6900 MML command ADD UCELLQUICKSETUP to configure Iub data and add dedicated cells.
NOTE
There are three 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 NodeBs are shared by operators. Shared cells or dedicated cells can be configured under the shared NodeBs.
l l
Verification Procedure There are no specific operations for verifying this feature. Deactivation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the parameter RAN Sharing Support to NO.
----End
Example
//Activating RAN Sharing Introduction Package Package SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES;//To configure the basic information about the RNC ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502", MNC="10", CnOpIndex=0; ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310",
7-342
Issue 03 (2010-09-20)
MNC="30", CnOpIndex=1;//To configure the information about the primary and secondary operators ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE, CnOpIndex1=0; ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE, CnOpIndex1=1;//To configure an operator group for the primary and secondary operators respectively ADD UCELLQUICKSETUP: CnOpGrpIndex=0;// To configure Iub data and add dedicated cells //Deactivating RAN Sharing Introduction Package Package SET UOPERATORSHARINGMODE: RANSharingSupport=NO;
7.179 Configuring Dedicated Carrier for Each Operator

This section describes how to activate, verify, and deactivate the optional feature WRFD-02130401 Dedicated Carrier for Each Operator.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-021304 RAN Sharing Introduction Package. l License The license is activated.
Context
This feature enables the allocation of frequency resources to different operators for independent operation.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. Activate the RAN Sharing license of operators. Configure the basic information about the BSC6900. Configure the information about the primary and secondary operators. Configure an operator group for the primary and secondary operators respectively. Add Iu configurations to operators 0 and 1 respectively. The following takes Iu over ATM as an example. Configure the N7DPC, CN NODE, SAAL/MTP3B link/MTP3B route, IuCS AAL2, and IuPS IPOA. 6. Configure Iub data and add dedicated cells.
Issue 03 (2010-09-20)
7-343

NOTE
There are three 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 NodeBs are shared by operators. Shared cells or dedicated cells can be configured under the shared NodeBs.
Verification Procedure Use a UE to access cells 1000 and 1001. If the access is successful, you can infer that carriers are shared by the operators.
Deactivation Procedure 1. 2. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the parameter RAN Sharing Support to NO. Run the BSC6900 MML command RMV UCELL to remove the cell.
----End
Example
//Activating Dedicated Carrier for Each Operator //Configure the basic information about the BSC6900 SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES; //Configure the information about the primary operator ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502", MNC="10", CnOpIndex=0; //Configure the information about the secondary operator ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310", MNC="30", CnOpIndex=1; //Configure an operator group for the primary and secondary operators respectively ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE, CnOpIndex1=0; ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE, CnOpIndex1=1; //Add dedicated cell for Each Operator ADD UCELLQUICKSETUP: CellId=1000, CnOpGrpIndex=0; ADD UCELLQUICKSETUP: CellId=1001, CnOpGrpIndex=1; //Deactivating Dedicated Carrier for Each Operator //Set the swithch SET UOPERATORSHARINGMODE: RANSharingSupport=NO; //Remove the cell RMV UCELL: CellId=1;
7.180 Configuring Flexible Network Architecture

This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402 Flexible Network Architecture.
Prerequisite
Context
This feature can meet the networking requirements of different operators.
Procedure
l Activation Procedure For information on activating the Iu Flex feature, see 7.191 Configuring Flexible Network Architecture. For information on activating the Cell Broadcast Service feature, see 7.157 Configuring Cell Broadcast Service. For information on activating the RAN Sharing feature, see 7.178 Configuring RAN Sharing Introduction Package Package. ----End
7.181 Configuring Mobility Control and Service Differentiation

This section describes how to activate, verify, and deactivate the optional feature WRFD02130403 Mobility Control and Service Differentiation.
Prerequisite
Context
This feature supports the configuration of different service support for multiple operators to meet their individual requirements.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE 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.
Verification Procedure The cells that belong to different operators can be configured as intra-frequency, interfrequency, or inter-RAT neighboring cells.
Deactivation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE 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 SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES; //Deactivating Mobility Control and Service Differentiation SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
7.182 Configuring Independent License Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-02130404 Independent License Control.
Prerequisite
Context
With this feature, operators can have their independent capacity and choose optional features, thus meeting different service and operation requirements.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET LICENSE to set the license control item for the primary operator to 0.
7-346
2. l l
Run the BSC6900 MML command SET LICENSE to set the license control item for the secondary operator to 1.
Verification Procedure None Deactivation Procedure None
----End
Example
//Activating Independent License Control SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=0, CsErlang=30000, FUNCTIONSWITCH1=PDCP-1; SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=NO, CNOPERATORINDEX=1, CsErlang=20000;
7.183 Configuring RAN Sharing Phase 2

This section describes how to activate, verify, and deactivate the optional feature WRFD-021305 RAN Sharing Phase 2.
Prerequisite
Context
This feature provides independent Iub transmission resource management for multiple telecom operators to ensure the QoS of their respective users.
Procedure
l Activation Procedure For information on activating this feature, see the feature WRFD-02130501 Dedicated Iub Transmission Control. l l Verification Procedure None Deactivation Procedure None ----End
7.184 Configuring WRFD-02130501 Dedicated Iub Transmission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-02130501 Dedicated Iub Transmission Control.
Prerequisite
Context
This feature provides separate admission control policies for operators that share the same port, thereby ensuring the basic bandwidth available to each operator and improving bandwidth efficiency when the Iub resources are idle.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD OPSEPINFO to add the separate information for operators, including bandwidth ratio and load threshold for each operator.
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, ADD UNILNK, or ADD IMAGRP to add a physical port and configure Index of Separate Information for Operators for the links carried on the physical port. In addition, set Operator Separated Flag to ON(ON).
NOTE
If IP transmission is used on the port, configure separate information for operators based on IP transmission by repeating the BSC6900 MML command ADD PPPLNK or ADD MPGRP.
3. 4. 5. 6.
Run the BSC6900 MML command ADD UNODEB to add a NodeB. In this step, set Sharing Type Of NodeB to RANSHARING(RAN Sharing). Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path. Run the BSC6900 MML command ADD TRMMAP to configure the TRM mapping table.
7-348

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 to add the TRM mapping to the adjacent node. In this step, set Resource Management Mode to SHARE(SHARE) or EXCLUSIVE(EXCLUSIVE). If you set Resource Management Mode to EXCLUSIVE(EXCLUSIVE), you are advised to add the TRM mapping to the adjacent node for each operator. Otherwise, the operator for whom the TRM mapping to the adjacent node is not added cannot admit services.
Verification Procedure 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. Run the BSC6900 MML command MOD FRALNK, MOD UNILNK, or MOD IMAGRP as required. In this step, set Operator Separated Flag to OFF(OFF).
----End
Example
//*Activation procedure*// 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; //*Deactivation procedure*// MOD IMAGRP: SRN=0, SN=26, BT=AEUa, IMAGRPN=0, OPSEPFLAG=OFF;
7.185 Configuring IMSI-Based Handover

This section describes how to activate, verify, and deactivate the optional feature WRFD-021303 IMSI Based Handover.
Prerequisite
l l Dependency on Hardware None License The license is activated.
Context
This feature supports the configuration of SNA-related information on the RNC side. When the CN does not support the SNA function, this feature enables the UTRAN to limit mobile areas of the UE.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. l Run the BSC6900 MML command SET LICENSE to activate the license of IMSIbased handover. Run the BSC6900 MML command SET URRCTRLSWITCH to select RNCAP_IMSI_HO_SWITCH from the parameter PROCESSSWITCH. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select HO_MC_SNA_RESTRICTION_SWITCH from the parameter HoSwitch. Run the BSC6900 MML command ADD ULASNAMAP to set the shared network area information. Run the BSC6900 MML command ADD UIMSISNAMAP to add the mapping between the IMSI and SNA. Set up cell 1 and configure the LAC as H'1234. Set up cell 2 and configure the LAC as H'1235. UE 1 with IMS "460071234000006" initiates an RRC Connection Request and tries to access cell 1. The expected result: UE 1 is admitted to cell 1. UE 2 with IMS "460071234000007" initiates an RRC Connection Request and tries to access cell 2. The expected result: UE 2 is rejected by cell 2.
NOTE
4.
The restrictions on Cell Update, URA Update, Handover, Relocation, Handling Common ID Message features are the same as those on the RRC Connection Request message.
Deactivation Procedure 1. Run the BSC6900 MML command SET LICENSE to disable the IMSI-based handover.
----End
Example
//Activating IMSI Based Handover
7-350
Issue 03 (2010-09-20)
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH2=IMSIBH-1;//to activate the license of IMSI-based handover// SET URRCTRLSWITCH: PROCESSSWITCH=RNCAP_IMSI_HO_SWITCH-1; SET UCORRMALGOSWITCH: HoSwitch=HO_MC_SNA_RESTRICTION_SWITCH-0; ADD ULASNAMAP: MCC="460", MNC="00", LAC=H'1234, SNAC=1;//To set the shared network area information// ADD UIMSISNAMAP: ImsiMin = "460071234000000", ImsiMax = "460071234500000", MCC="460", MNC="07", SnaExistInd=TRUE,SNAC=1;//To add the mapping// //Deactivating IMSI Based Handover SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH2=IMSIBH-0;//To disable the IMSI-based handover
7.186 Configuring MOCN Introduction Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-021311 MOCN(Multi-operator core network) Introduction Package.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features This feature is mutually exclusive to the feature WRFD-021304 RAN Sharing Introduction Package. l l License The license is activated. Other Prerequisites The CN and UE should support the MOCN function.
Context
MOCN is introduced in 3GPP Release 6. It enables multiple operators to share the network and thus reduces the cost of network construction. For details about MOCN, see 3GPP TS 23.251. MOCN is implemented on the RNC and CN. It is applicable to all types of terminal.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command SET LICENSE to activate the license of the primary operator. Run the BSC6900 MML commandSET LICENSE to activate the license of the secondary operator. Run the BSC6900 MML command ADD UCNOPERATOR to add the primary operator. Run the BSC6900 MML command ADD UCNOPERATOR to add a secondary operator. Run the BSC6900 MML command ADD UCNOPERATOR to add a common operator.
Issue 03 (2010-09-20)

NOTE
The common operator may be configured or not. It is recommended that it 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) to the default value 255.
7. 8. 9.
Run the BSC6900 MML command SET UOPERATORSHARINGMODE to the sharing mode for the operators. Run the BSC6900 MML command SET UOPERATORCFGPARA to set parameters for the primary operator. Run the BSC6900 MML command SET UOPERATORCFGPARA to set parameters for the secondary operator.
10. Run the BSC6900 MML command ADD UCNNODE to add CN nodes for the primary operator. 11. Run the BSC6900 MML command ADD UCNNODE to add CN nodes for the secondary operator. 12. Run the BSC6900 MML command ADD UNRIGLBCNIDMAP to add the mapping between NRIs and CN node IDs.
NOTE
The mapping between NRIs and CN node IDs is subject to the network plan. If an operator is configured with multiple NRIs, the ADD UNRIGLBCNIDMAP command must be executed repeatedly.
13. Run the BSC6900 MML command ADD UNODEB to add an MOCN NodeB. 14. Run the BSC6900 MML command ADD UNODEB add a dedicated NodeB. 15. Run the BSC6900 MML command ADD ULAC to add location areas.
NOTE
Location areas must be set the same for the primary and secondary operators.
16. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add an MOCN cell.
NOTE
A cell is a dedicated cell if its operator group is configured with only one operator during cell setup.
17. Run the BSC6900 MML command ADD UEXT3GCELL to add a neighboring RNC cell. l Verification Procedure 1. 2. l 1. ----End
Register MOCN-supportive and non-MOCN-supportive UEs in MOCN cells of the primary and secondary operators. The UEs should be registered successfully. Originate CS and PS services. The services should be provided properly. Run the BSC6900 MML command RMV UCELL to remove an MOCN cell.
Example
//Activating MOCN Introduction Package. SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=0, FUNCTIONSWITCH2=ENHANCEDIUFLEX-1, FUNCTIONSWITCH4=MOCN_PACKAGE-1, ACTOBJECT=LOCAL; SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=NO, CNOPERATORINDEX=1, FUNCTIONSWITCH2=ENHANCEDIUFLEX-1, FUNCTIONSWITCH4=MOCN_PACKAGE-1, ACTOBJECT=LOCAL; ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PrimOp", MCC="302", MNC="221", CnOpIndex=0; ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SecOp", MCC="302", MNC="640", CnOpIndex=1; ADD UCNOPERATOR: OperatorType=COMM, CnOperatorName="Common", MCC="302", MNC="580", CnOpIndex=5; ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="ShareCnOpGrp", CnOpNum=TWO, CnOpIndex1=0, CnOpIndex2=1, CnOpIndexComm=5; SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO, CommPlmnUsingType=NON-SUPPORTING_UE_ONLY, DefaultCnOp=0, MocnControlSwitch=COMM_MOCN_NRI_GLOBAL_CONFIG_MODE_SWITCH-1&COMM_MIB_MULT I_PLMN_LIST_ALLOWED_SWITCH-1; SET OPERATORCFGPARA: CnOpIndex=0, CsNriCfgMode=SUPP_IUFLEX_MOCN, PsNriCfgMode=SUPP_IUFLEX_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=0; SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX_MOCN, PsNriCfgMode=SUPP_IUFLEX_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=1; ADD UCNNODE: CnOpIndex=0, CNId=10, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL; ADD UCNNODE: CnOpIndex=0, CNId=20, CNDomainId=PS_DOMAIN, CNLoadStatus=NORMAL; ADD UCNNODE: CnOpIndex=1, CNId=11, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL; ADD UCNNODE: CnOpIndex=1, CNId=21, CNDomainId=PS_DOMAIN, CNLoadStatus=NORMAL; ADD UNRIGLBCNIDMAP: CnOpIndex=0, CNId=10, NRI=10; ADD UNRIGLBCNIDMAP: CnOpIndex=0, CNId=20, NRI=20; ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=11, NRI=100; ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=21, NRI=600; ADD UNODEB: TnlBearerType=IP_TRANS, HostType=SINGLEHOST, SharingType=MOCN; ADD UNODEB: TnlBearerType=IP_TRANS, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; ADD ULAC:CNOPINDEX=0, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256; ADD ULAC:CNOPINDEX=1, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256; ADD UCELLQUICKSETUP: PeerIsValid=INVALID, CnOpGrpIndex=0, LAC=H'7208, SupBmc=FALSE; ADD UEXT3GCELL: CellHostType=SINGLE_HOST, CnOpGrpIndex=0, QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED; //Deactivating MOCN Introduction Package. RMV UCELL: CellId=1;
7.187 Configuring Carrier Sharing by Operators

This section describes how to activate, verify, and deactivate the optional feature WRFD-02131101 Carrier Sharing by Operators.
Prerequisite
l
Issue 03 (2010-09-20)
None l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-021311 MOCN Introduction Package. l l License The license is activated. Other Prerequisites The network is ready. The CN supports multi-operator core network (MOCN).
Context
This feature enables multiple operators to share the same RAN equipment and frequency. One cell can belong to and provide services to multiple operators.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command ADD UCELLQUICKSETUP to add an MOCN cell so that multiple operators can share the same frequency. Check whether the settings of the MOCN cell are effective, based on the master information block (MIB) traced on the Uu interfaces. If the RNC supports MOCN and the cell is configured with multiple operators, the system information broadcast in the cell includes the multiplePLMN-List IE. This IE carries the information about all the PLMNs configured for this cell, and the plmnidentity IE carries the information about the common PLMN configured for this cell. For example, the multiplePLMN-List IE carries the PLMN IDs (302221 and 302640) of two operators, as shown in Figure 7-89; the plmn-Identity IE carries the PLMN ID (320580) of a common operator, as shown in Figure 7-90.
7-354
Issue 03 (2010-09-20)
Figure 7-89 multiplePLMN-List IE in RRC_MASTER_INFO_BLOCK
Issue 03 (2010-09-20)
7-355
Figure 7-90 plmn-Identity IE in RRC_MASTER_INFO_BLOCK
Deactivation Procedure 1. 2. Run the BSC6900 MML command RMV UCELL to remove the MOCN cell. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add a dedicated cell.
----End
Example
//Activating Carrier Sharing by Operators. ADD UCELLQUICKSETUP: PeerIsValid=INVALID, CnOpGrpIndex=0, LAC=H'7208, SupBmc=FALSE; //Deactivating Carrier Sharing by Operators. RMV UCELL: CellId=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;
7-356
Issue 03 (2010-09-20)
7.188 Configuring Dedicated NodeB/Cell for Operators

This section describes how to activate, verify, and deactivate the optional feature WRFD-02131102 Dedicated NodeB/Cell for Operators.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-021311 MOCN Introduction Package. l l License The license is activated. Other Prerequisites The network is ready. The CN supports multi-operator core network (MOCN).
Context
This feature enables multiple operators control their own NodeBs and cells in the case of MOCN.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command SET UOPERATORSHARINGMODE to add a dedicated NodeB. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add a dedicated cell. Check whether this feature is effective, based on the master information block (MIB) traced on the Uu interfaces. Assume that a cell is configured with only one operator. Then, the MIB broadcast in the cell carriers the PLMN ID (302640) of this operator, as shown in the following figure.
NOTE
If the RNC supports MOCN but the cell is configured with only one operator, the MIB broadcast does not carry the multiplePLMN-List IE.
Issue 03 (2010-09-20)
7-357
Figure 7-91 plmn-identity IE in the MIB
Deactivation Procedure 1. Run the BSC6900 MML command RMV UCELL to remove the dedicated cell of this operator.
----End
Example
//Activating Dedicated NodeB/Cell for Operators. SET UOPERATORSHARINGMODE: MOCNSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO, DefaultCnOp=0; //Deactivating Dedicated NodeB/Cell for Operators. RMV UCELL: CellId=1;
7.189 Configuring MOCN Mobility Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-02131103 MOCN Mobility Management.
7-358
Issue 03 (2010-09-20)
Prerequisite
Context
This feature is applicable to different MOCN mobility strategies. It determines whether to hand over a UE to a target cell based on the index of the operator to which the UE belongs and the PLMN ID of the cell.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the parameters MOCN Support, Intra RAT Inter Plmn Ho Allowed, and Inter RAT Inter Plmn Ho Allowed to YES.
Verification Procedure Check whether handover, relocation, and cell change between PLMNs can be performed when the inter-PLMN handover switches are turned on.
Deactivation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the parameters MOCN Support, Intra RAT Inter Plmn Ho Allowed, and Inter RAT Inter Plmn Ho Allowed to NO.
----End
Example
//Activating MOCN Mobility Management SET UOPERATORSHARINGMODE: MOCNSupport=YES, InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES; Deactivating MOCN Mobility Management SET UOPERATORSHARINGMODE: MOCNSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
7.190 Configuring MOCN Load Balance

This section describes how to activate, verify, and deactivate the optional feature WRFD-02131104 MOCN Load Balance.
Issue 03 (2010-09-20)
7-359
Prerequisite
Context
This feature enables multiple operators to achieve load balance and network fairness.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the parameter MOCN Support to YES and the parameter Default CnOperator to 255.
NOTE
The default value 255 of Default CnOperator indicates that there is no default operator. In this case, the system selects operators in polling mode.
Verification Procedure 1. Run the BSC6900 MML command LST UOPERATORSHARINGMODE to query the parameter settings for MOCN load balance. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the parameter MOCN Support to YES and the parameter Default CnOperator to 0. Subsequently, the RNC selects operator 0 preferentially.
----End
Example
//Activating MOCN Load Balance. SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=255; //Verifying MOCN Load Balance. LST UOPERATORSHARINGMODE: LstFormat=HORIZONTAL; //Deactivating MOCN Load Balance. SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=0;
7.191 Configuring Flexible Network Architecture

This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402 Flexible Network Architecture.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites Require MSC or SGSN support such feature at the same time.
Context
In RAN Sharing solution, the flexibility of the network architecture is well supported. The involved interfaces are Iub, Iur, Iu, and Iu-BC.
Procedure
l Activation Procedure For information on activating the Iu Flex feature, see the feature WRFD-021302 Iu Flex. For information on activating the Cell Broadcast Service feature, see the feature WRFD-011000 Cell Broadcast Service. For information on activating the RAN Sharing feature, see the feature WRFD-021304 RAN Sharing Introduction Package. l Verification Procedure None l Deactivation Procedure None ----End
7.192 Configuring Iu Flex Load Distribution Management

This section describes how to activate the optional feature WRFD-021306 Iu Flex Load Distribution Management.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-021302 Iu Flex. l License The license is activated.
Context
This feature enables load balancing between multiple CN nodes in Iu Flex scenarios.
Procedure
l Activation Procedure 1. 2. 3. 4. l Run the BSC6900 MML command ADD UCNNODE to set the parameter Capability of CN Node. Run the BSC6900 MML command SET UOPERATORCFGPARA to set the parameter CS Information Update Switch to ON. Run the BSC6900 MML command MOD UCNNODE to set the parameter Status of CN Node to OFFLOAD. Run the BSC6900 MML command SET UOPERATORCFGPARA to set the parameter NullNRI VALUE.
Verification Procedure 100 UEs initiate the registration processes. The RNC cannot route the UEs to a CN node according to the intraDomainNasNodeSelector parameter contained in the RRC_INIT_DIRECT_TRANSFER message. The RNC route these UEs to the corresponding CNs. The first 40 UEs are routed to CN 1 and the remaining 60 UEs are routed to CN 2.
Deactivation Procedure 1. Run the BSC6900 MML command SET UOPERATORCFGPARA to set the parameter CS Information Update Switch to OFF. Deactivate the function of enhanced load balancing. Run the BSC6900 MML command MOD UCNNODE to set the parameter Status of CN Node to NORMAL. Deactivate the function of load re-distribution.
2. ----End
Example
//Activating Iu Flex Load Distribution Management. ADD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=ON,CsInfoUpdTmr=900; MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=OFFLOAD, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, NullNRI=31; //Deactivating Iu Flex Load Distribution Management. SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=OFF; MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;
7-362
Issue 03 (2010-09-20)
7.193 Configuring Multi-Frequency Band Networking Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-020110 Multi Frequency Band Networking Management.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020400 DRD Introduction Package, or WRFD-020302 Inter Frequency Hard Handover Based on Coverage, or WRFD-020303 Inter-RAT Handover Based on Coverage should be enabled, or WRFD-020306 InterRAT Handover Based on Load, or WRFD-020305 Inter-RAT Handover Based on Service or WRFD-021200 HCS (Hierarchical Cell Structure).
NOTE
If one of these dependent features is not enabled, the corresponding function will not be available in the multi-frequency band networking solution. The operator can choose which feature to use or not.
Context
This feature enables telecom operators to run services on multiple frequency bands simultaneously. In addition, it supports inter-band mobility management, load balancing, and service distribution.
Procedure
l Activation Procedure None l Verification Procedure None l Deactivation Procedure None ----End
7.194 Configuring Enhanced Multiband Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-020160 Enhanced Multiband Management.
Prerequisite
l l Dependency on Hardware None. Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-020110 Multi Frequency Band Networking Management and WRFD-020400 DRD Introduction Package or WRFD-020110 Multi Frequency Band Networking Management and WRFD-020103 Inter-Frequency Load Balance. l License The license is activated.
Context
In a multiband network, the cells that operate on different frequency bands have different coverage areas. Blind handover performed in this situation may lead to call drops. After this feature is applied, when an inter-frequency handover is required, the RNC performs the handover decision according to the inter-frequency measurement result rather than perform a blind handover. This increases the handover success rate.
Procedure
l Activation Procedure 1. For detailed operations for activating the license, see 7.2.1 Activating the BSC6900 License.
NOTE
Steps 2 through 5 describe the handover activation based on service steering. Steps 6 through 7 describe the handover activation based on load sharing.
2. 3. 4. 5.
Run the BSC6900 MML command SET UDRD to set the Measurement-Based DRD Switch parameter to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DR_RAB_SING_DRD_SWITCH from the Direct Retry Switch list. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select DR_RAB_COMB_DRD_SWITCH from the Direct Retry Switch list. Run the BSC6900 MML command MOD UINTERFREQNCELL to set the following parameters as required: RNC ID, Cell ID, RNC ID of a neighboring cell, and Neighboring Cell ID. Then, set the DrdOrLdrFlag parameter to TRUE. Run the BSC6900 MML command MOD UINTERFREQNCELL to set the following parameters as required: RNC ID, Cell ID, RNC ID of a neighboring cell, and Neighboring Cell ID. Then, set the DrdOrLdrFlag parameter to TRUE. Run the BSC6900 MML command MOD UCELLLDR to set the Cell ID parameter. Then, set the InterFreq Load Handover Method Selection parameter to MEASUREHO(MEASUREHO). When a large number of UEs access the cell, cell congestion occurs. At this time, if handover based on inter-frequency measurement is used to achieve load reshuffling (LDR), you can view the inter-frequency measurement control information on the Uu
6.
7.
7-364
interface. After the UE sends the inter-frequency measurement report, the UE will be handed over to another cell. l Deactivation Procedure 1. ----End Run the BSC6900 MML command MOD UCELLLDR to set the InterFreq Load Handover Method Selection parameter to BLINDHO(BLINDHO).
Example
//Activating Enhanced Multiband Management SET UDRD: BasedOnMeasHRetryDRDSwitch=ON; SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1; SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_COMB_DRD_SWITCH-1; MOD UINTERFREQNCELL: RNCId=2021, CellId=3000, NCellRncId=2021, NCellId=3002, DrdOrLdrFlag=TRUE; MOD UINTERFREQNCELL: RNCId=2021, CellId=3000, NCellRncId=2021, NCellId=3002, DrdOrLdrFlag=TRUE; MOD UCELLLDR: CellId=3000, InterFreqLDHOMethodSelection=MEASUREHO; //Deactivating Enhanced Multiband Management MOD UCELLLDR: CellId=3000, InterFreqLDHOMethodSelection=BLINDHO;
7.195 Configuring Satellite Transmission on Iub Interface

This section describes how to activate, verify, and deactivate the optional feature WRFD-050104 Satellite Transmission on Iub Interface.
Prerequisite
Context
This function supports satellite transmission on the Iub interface, which is useful to cover remote districts, such as an island. When satellite transmission is applied over the Iub interface, the delay increases and the timer in SAAL/NBAP/ALCAP should be adjusted to avoid data or link error due to transmission delay. These related parameters are configurable to meet satellite transmission requirements.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command MOD UNODEB to set the Satellite Trans Ind parameter to TRUE. Run the BSC6900 MML command ACT UCELL to activate the cell under the NodeB.
Issue 03 (2010-09-20)
Verification Procedure 1. 2. 3. Run the BSC6900 MML command DSP UCELL. The result shows that the cell is set up successfully. Establish an AMR speech service in the cell. The service is established successfully, and the speech quality is satisfactory. Establish a PS BE service in the cell. The service is established successfully, and data is downloaded at a stable rate. Run the BSC6900 MML command DEA UCELL to deactivate the cell. Run the BSC6900 MML command MOD UNODEB to set the Satellite Trans Ind parameter to FALSE.
----End
Example
//Activating Satellite Transmission on Iub Interface MOD UNODEB: NodeBId=1, SATELLITEIND=TRUE; CT UCELL: CellId=1; //Verifying Satellite Transmission on Iub Interface //Deactivating Satellite Transmission on Iub Interface DEA UCELL: CellId=1; MOD UNODEB: NodeBId=1, SATELLITEIND=FALSE;
7.196 Configuring Satellite Transmission on Iu Interface

This section describes how to activate, verify, and deactivate the optional feature WRFD-050108 Satellite Transmission on Iu Interface.
Prerequisite
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
7-366
1.
Run the BSC6900 MML command ADD SAALLNK or MOD SAALLNK 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 7-7. Table 7-7 Timers related to SAAL links of satellite transmission Parameter ID MPS CCTMR POLLTMR IDLETMR RSPTMR KEEPTMR Parameter Name Management proving status Timer_CC{ms} Timer_Poll{ms} Timer_Idle{ms} Timer_NoResponse{ms} Timer_KeepAlive{ms} Default Value MPS_NEUTRAL 200 100 500 1500 100 Recommended Value MPS_EMERGEN CY 800 300 3000 3000 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.
Verification Procedure 1. 2. Run the BSC6900 MML command LST SAALLNK to check whether the setting of the timer is modified correctly. Run the BSC6900 MML command DSP SAALLNK to query the status of SAAL links. The result shows that SAAL link state is AVAILABLE. Run the BSC6900 MML command MOD SAALLNK 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;
7.197 Configuring MBMS Introduction Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-010616 MBMS Introduction Package.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites The existing PS Domain functional entities (GGSN, SGSN, UTRAN and UE) need to be enhanced to provide the 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 users Services. The UE should support MBMS functions.
Context
WRFD-010616 MBMS Introduction Package supports the basic MBMS functions to meet operators' requirements for applying the MBMS feature. For details, see the Optional Feature Description of Huawei UMTS.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. 6. 7. 8. 9. Run the BSC6900 MML command SET UMBMSSWITCH to set the MBMS switch. The MBMS takes effect only when the MBMS switch is turned on. Run the BSC6900 MML command ADD UMBMSSA to add the MBMS service area. Run the BSC6900 MML command ADD UCELLMBMSSA to add the mapping between the cell and the MBMS service area (SA). Run the BSC6900 MML command ADD USCCPCHBASIC to add SCCPCH channel which are used by MCCH. Run the BSC6900 MML command ADD UFACH to add FACH channel which are mapped by MCCH. Run the BSC6900 MML command ADD UFACHDYNTFS to add the transport format set (TFS) of a FACH. Run the BSC6900 MML command ADD UFACHLOCH to add a logical channel mapped to a FACH. Run the BSC6900 MML command ADD USCCPCHTFC to add the Calculated Transport Format Combination (CTFC) of a SCCPCH. Run the BSC6900 MML command ADD UCELLMCCH to activate SCCPCH. Run the BSC6900 MML command ADD UCELLMCCH to add the MCCH and the MICH for the cell. Run the BSC6900 MML command ACT UCELLMBMS to activate the MBMS configuration data for the cell.
10. Configure the cell-level MBMS parameters.
11. Run the BSC6900 MML command SET UMTCH to set MBMS service type and MBMS service bit rate. 12. Run the BSC6900 MML command SET URNCMBMSPARA to set the RNC-level MBMS parameters, such as MBMS transmit mode, for the RNC. l Verification Procedure 1. 2. l Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the MBMS status in the cell. Use an MBMS UE to request an MBMS service, the MBMS UE can receive the corresponding MBMS data successfully. Run the BSC6900 MML command SET UMBMSSWITCH. In this step, set turn off the MBMS switch.
----End
Example
//Activating MBMS Introduction Package SET UMBMSSWITCH: MbmsSwitch=ON; ADD UMBMSSA: CnOpIndex=0, MbmsSaId=1; ADD UCELLMBMSSA: CellId=2, CnOpIndex=0, MbmsSaId=1; ADD USCCPCHBASIC: CellId=2, PhyChId=11, ScrambCode=0, SlotFormat=D8, TFCIpresence=NOT_EXISTS, MbmsChInd=MCCH; ADD UFACH: CellId=2, PhyChId=11, TrChId=10, RateMatchingAttr=220, ToAWS=20, ToAWE=10, MaxFachPower=-10, ChCodingType=CONVOLUTIONAL; ADD UFACHDYNTFS: CellId=2, TrChId=10, RLCSize=168, TFsNumber=D3, TbNumber1=0, TbNumber2=1, TbNumber3=2; ADD UFACHLOCH: CellId=2, TrChId=10; ADD USCCPCHTFC: CellId=2, PhyChId=11, CTFC=0; ADD USCCPCHTFC: CellId=2, PhyChId=11, CTFC=1; ADD USCCPCHTFC: CellId=2, PhyChId=11, CTFC=1; ACT USCCPCH: CellId=2, PhyChId=11; ADD UCELLMCCH: CellId=2, MichId=19, PhyChIdforMcch=11, FachIdforMcch=10; ACT UCELLMBMS: CellId=100; SET UMTCH: ServiceType=STREAMING, ServiceBitRate=D128; SET URNCMBMSPARA: MbmsTransMode=DYNAMIC; //Deactivating MBMS Introduction Package SET UMBMSSWITCH: MbmsSwitch=OFF;
7.198 Configuring MBMS Broadcast Mode

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061601 MBMS Broadcast Mode.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package. l
Issue 03 (2010-09-20)
License
Context
The broadcast mode is the unidirectional point-to-multipoint transmission of multimedia data (such as text, audio, picture, video) from a single source entity to multiple users. In broadcast mode, the transmission mode is fixed to PtM.
Procedure
l Activation Procedure This feature takes effect when the cell is enabled with the feature WRFD-010616 MBMS Introduction Package and the CN specifies that broadcast mode is applied. For details on how to activate MBMS, see the section "Configuring MBMS Introduction Package". l l Verification Procedure None Deactivation Procedure None ----End
7.199 Configuring MBMS Admission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061602 MBMS Admission Control.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package. l License The license is activated.
Context
The admission criteria of Iub resources and credit resources for the MBMS PtP/PtM RB requests are the same as that for other services. Only the activation procedure of the resource admission on the Uu interface is provided in this section. For details, see the Optional Feature Description of Huawei UMTS.
Procedure
l
7-370
1. l
Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the MBMS admission control on the Uu interface and select an admission algorithm. Disable the admission algorithm. In this manner, service admission is always successful. Enable the admission algorithm, and then limit cell resources to ensure that the admission resources are insufficient. In this manner, the admission fails. Run the BSC6900 MML command ADD URESERVEOVSF to reserve the DL OVSF for the cell to ensure that only 64 kbit/s services are supported. Initiate a 265 kbit/s service. Check the messages traced on the Iu interface at the BSC side. You may find the MBMS SESSION START message from the CN to the RNC and the MBMS SESSION START RSPPONSE message from the RNC to the CN.
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the MBMS admission algorithm.
----End
Example
//Activating MBMS Admission Control MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-1, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST; //Deactivating MBMS Admission Control MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-0;
7.200 Configuring MBMS Load Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061603 MBMS Load Control.
Prerequisite
Context
The feature helps to decrease the cell load when the cell enters the congestion state and ensures the system stability. When the cell is in the basic congestion, reduction of the MBMS service power may be triggered when the downlink congestion is detected.
Issue 03 (2010-09-20)
7-371
Procedure
l Activation Procedure This feature depends on the MBMS basic functions. This feature can be activated only after MBMS basic functions are enabled. For details, see the section "Configuring MBMS Introduction Package". 1. 2. 3. l Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the DL load reshuffling and the DL overload congestion control on the Uu interface. Run the BSC6900 MML command MOD UCELLLDR to set the congestion-relieve action that LDR will trigger. Run the BSC6900 MML command MOD UCELLOLC to set the sequence and number of MBMS services to be released for OLC. Originate an MBMS service in the MBSC, and ensure that service data is sent. Based on the current load of the cell, set the triggering thresholds for LDR and OLC to ensure that the corresponding load control actions will be triggered. When the cell load exceeds the LDR threshold, the power of the MBMS service is reduced in the cell. Check the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message traced on the Iub interface. The maxFACH Power IE in this message indicates that the power of the MBMS service is reduced. When the cell load exceeds the OLC threshold, the MBMS service is released. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the DL load reshuffling and the DL overload congestion control on the Uu interface. Optional: If either of the function cannot be disabled, remove the MBMS service power reduction from the LDR-triggered actions, and then set the number of OLCtriggered MBMS services to be 0.
4. l 1. 2.
----End
Example
//Activating MBMS Load Control MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR -1&DL_UU_OLC-1; MOD UCELLLDR: CELLID=1, DlLdrFirstAction=MBMSDECPOWER; MOD UCELLOLC: CellId=1, SeqOfUserRel=MBMS_REL, MbmsOlcRelNum=1; //Verifying MBMS Load Control MOD CELLLDM: 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; OD UCELLLDR: CELLID=1, DlLdrFirstAction=NoAct; MOD UCELLOLC: CellId=1, SeqOfUserRel= USER_REL, MbmsOlcRelNum=0;
7.201 Configuring MBMS Soft/Selective Combination

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061604 MBMS Soft/Selective Combination.
Prerequisite
Context
Selective combination and soft combination aim to improve the receive sensitivity of UEs in PtM mode and obtain a higher reception gain. The common channel soft combination is a function introduced for the MBMS. It means that the UE receiver combines the signal from the multiple cells either in the RAKE receiver or after the RAKE receiver in the receiver chain prior to the decoding of the soft combination transport channel. The maximum time difference between the S-CCPCHs carrying the same service in different cells should be less than 1TTI+1slot. The selective combination (SC) is an enhancement for the Release 6 PtM MBMS. The network is to simulcast the PtM MBMS contents on the S-CCPCH, and the UE receives and decodes the MBMS data from multiple radio links simultaneously. The selection of the radio link is to be performed on a transport block basis at the RLC, based on the CRC results and sequence numbers. The RNC should ensure that the services data sent to the UE from different cells are synchronized.
Procedure
l Activation Procedure This feature takes effect when the cell is enabled with the feature WRFD-010616 MBMS Introduction Package and the transmission mode is PtM. For detailed information about MBMS activation, see the section "Configuring MBMS Introduction Package". l Verification Procedure None l Deactivation Procedure None ----End
7.202 Configuring MBMS Transport Resource Management

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061605 MBMS Transport Resource Management.
Prerequisite
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.
Procedure
l Activation Procedure This feature depends on MBMS basic functions. This feature takes effect as long as the cell is enabled with the feature WRFD-010616 MBMS Introduction Package. For details, see the section Configuring MBMS Introduction Package. l Verification Procedure 1. Use UEs to require an MBMS service in the two cells under the same NodeB. 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, where 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. You may also find that both the COMMON TRANSPORT CHANNEL SETUP RESPONSE messages contain the TLA and Binding ID.
Deactivation Procedure None
----End
7-374
Issue 03 (2010-09-20)
7.203 Configuring Streaming Service on MBMS

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061606 Streaming Service on MBMS.
Prerequisite
Context
This feature enables the MBMS service to be carried on the PS streaming class, thus ensuring QoS.
Procedure
l Activation Procedure 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 Verification Procedure 1. 2. l Use an MBMS-supportive UE to request an MBMS mobile television service and receive the corresponding data. The UE receives the data of the MBMS mobile television service successfully.
Deactivation Procedure This feature is used as long as MBMS is configured. There is no need to deactivate this feature.
----End
7.204 Configuring MBMS 2 Channels per Cell

This section describes how to activate the optional feature WRFD-01061607 MBMS 2 Channels per Cell.
Prerequisite
Context
This feature enables configuring a maximum of two channels for each MBMS cell. If this feature is enabled, the cell can provide service data in two MBMS channels.
Procedure
l Activation Procedure This feature depends on MBMS basic functions. This feature takes effect as long as the cell is enabled with the feature WRFD-010616 MBMS Introduction Package. For detail information about MBMS activation, see the section 7.197 Configuring MBMS Introduction Package. ----End
7.205 Configuring 16/32/64/128Kbps Channel Rate on MBMS

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061608 16/32/64/128Kbps Channel Rate on MBMS.
Prerequisite
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 Activation Procedure This feature depends on MBMS basic functions. This feature can be activated only after MBMS basic functions are enabled. For details, see the section 7.197 Configuring MBMS Introduction Package. l Verification Procedure 1. 2. l Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the MBMS status in the cell and the bandwidth of the MBMS service. Use an MBMS-supportive UE to request an MBMS service, the UE can receive the corresponding data successfully.
Deactivation Procedure This feature is used as long as the feature WRFD-010616 MBMS Introduction Package is configured. There is no need to deactivate this feature.
----End
7.206 Configuring MBMS Phase 2

This section describes how to activate, verify, and deactivate the optional feature WRFD-010660 MBMS Phase 2.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package. l l License The license is activated. 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 l l 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
l
Issue 03 (2010-09-20)
For details about activation procedures, see the following sections: Configuring MBMS Enhanced Broadcast Mode Configuring MBMS P2P over HSDPA Configuring MBMS Admission Enhancement Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users l l Verification Procedure None Deactivation Procedure None ----End
7.207 Configuring MBMS Enhanced Broadcast Mode

This section describes how to activate, verify, and deactivate the optional feature WRFD-01066001 MBMS Enhanced Broadcast Mode.
Prerequisite
Context
Compared with broadcast mode, it is a more efficient way to deploy the point-to-multipoint services, such as mobile TV.
Procedure
l Activation Procedure 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:
1. 2. 3. 4.
Run theBSC6900 MML command SET URNCMBMSPARA to set the transmission mode at the RNC level through the Mbms Transfer Mode parameter. Optional: Run the BSC6900 MML command ADD USAMBMSPARA to set the transmission mode at the SA level through the Mbms Transfer Mode parameter. Optional: Run the BSC6900 MML command ADD UCELLMBMSPARA to set the transmission mode at the cell level through the Mbms Transfer Mode parameter. Run the BSC6900 MML command SET URNCMBMSPARA to set the transfer threshold between PtP and PtM mode through the Counting Threshold and the Ptp To Ptm Offset parameters. Use an MBMS-supportive UE to request an MBMS service and receive the corresponding data. 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. 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.
3.
Deactivation Procedure 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;
7.208 Configuring MBMS P2P over HSDPA

This section describes how to activate, verify, and deactivate the optional feature WRFD-01066002 MBMS P2P over HSDPA.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package, WRFD-010610 HSDPA Introduction Package. l License The license is activated.
Issue 03 (2010-09-20)
7-379
Context
This feature enables MBMS PtP services to be carried on the HS-DSCH, thus saving cell resources. For details, see the Optional Feature Description of Huawei UMTS.
Procedure
l Activation Procedure This feature depends on the MBMS enhanced broadcast mode and the HSDPA. Before activating this feature, activate the MBMS enhanced broadcast mode and the HSDPA. 1. 2. l Run the BSC6900 MML command SET URNCMBMSPARA to set the MBMS transmission mode to be either of a mode except PtM. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable streaming services to be carried on HSDPA. Set up a 256 kbit/s MBMS streaming service. Use an MBMS-supportive UE to request this MBMS service and receive the corresponding data.
Deactivation Procedure 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;
7.209 Configuring MBMS Admission Enhancement

This section describes how to activate, verify, and deactivate the optional feature WRFD-01066003 MBMS Admission Enhancement.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WWRFD-010616 MBMS Introduction Package. l License The license is activated.
Context
This feature provides different admission policies for PtM and PtP MBMS 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 too many resources to block non-MBMS connection admission. In addition, some resources should be reserved for the use of MBMS PtM.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET UQUEUEPREEMPT to enable the preemption algorithm and the MBMS preemption algorithm. For example, Run the BSC6900 MML command SET URNCMBMSPARA to set the preemption parameters for PtM services. The actual preemption capabilities are determined by both the settings of these parameters and the settings sent by the CN. The settings of PtP services are sent by the CN and need to be set manually. Run the BSC6900 MML command LST URNCMBMSPARA command to check the configuration. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the MBMS preemption algorithm.
----End
Example
//Activating MBMS Admission Enhancement SET UQUEUEPREEMPT: PreemptAlgoSwitch= ON, MbmsPreemptAlgoSwitch=ON; SET URNCMBMSPARA:MbmsTransMode = PTM, PtmPreemptSwitch = ON, PtmStrmPasiSwitch = ON, PtmNullStrmPasiSwitch = ON; //Deactivating MBMS Admission Enhancement MOD UQUEUEPREEMPT: MbmsPreemptAlgoSwitch=OFF;
7.210 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users
This section describes how to activate, verify, and deactivate the optional feature WRFD-01066004 Inter-Frequency Neighboring Cell Selection for MBMS PTP Users.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package, WRFD-010660 MBMS Phase 2. l
Issue 03 (2010-09-20)
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, thus ensuring the continuity of the MBMS service.
Procedure
l Activation Procedure This feature takes effect as long as the cell is enabled with WRFD-010616 MBMS Introduction Package. For details on how to activate, verify, and deactivate the feature, see the section 7.197 Configuring MBMS Introduction Package. l Verification Procedure None l Deactivation Procedure None ----End
7.211 Configuring FACH Transmission Sharing for MBMS

This section describes how to activate, verify, and deactivate the optional feature WRFD-010627 FACH Transmission Sharing for MBMS.
Prerequisite
Context
To maximize the bandwidth usage on the Iub interface, the FACH Transmission Sharing for MBMS feature is introduced in 3GPP R6 to share transport bearers. RNC transports only single FACH data. The NodeB transport module performs data duplication and distributes them to different FACH Channels, as shown in the following figure, where the common transport bearer is shared over Iub. Obviously, two-third of Iub bandwidth is saved by the improved Iub transport.
7-382
Issue 03 (2010-09-20)
For details, see the Optional Feature Description of Huawei UMTS.
Procedure
l Activation Procedure This feature depends on MBMS basic functions. This feature can be activated only after MBMS basic functions are enabled. For details, see the Configuring MBMS Introduction Package. 1. l Run the BSC6900 MML command SET UMBMSSWITCH to enable FACH transmission sharing. Before enabling this feature, use UEs to require an MBMS service in the two cells under the same NodeB. 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, where 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. You may also find that both the COMMON TRANSPORT CHANNEL SETUP RESPONSE messages contain TLA and Binding ID. Enabling this feature. Then, use UEs to require an MBMS service in the two cells. 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, where the BROADCAST REFERENCE IEs in the two COMMON TRANSPORT CHANNEL SETUP REQUEST messages are the same. This indicates that the messages are from the same Iub interfaces. You may also find that only the first COMMON TRANSPORT CHANNEL SETUP RESPONSE message contains TLA and Binding ID. The second COMMON TRANSPORT CHANNEL SETUP RESPONSE message does not contain TLA and Binding ID, but contains the BROADCAST COMMON TRANSPORT BEARER INDICATION IE. Run the BSC6900 MML command SET UMBMSSWITCH to disable FACH transmission sharing.
2. 3.
----End
Example
//Deactivating FACH Transmission Sharing for MBMS SET UMBMSSWITCH: MbmsSwitch=ON, MbmsIubSharingSwitch=OFF;
Issue 03 (2010-09-20)
7-383
7.212 Configuring MBMS FLC (Frequency Layer Convergence)/FLD (Frequency Layer Dispersion)
This section describes how to activate, verify, and deactivate the optional feature WRFD-010626 MBMS FLC (Frequency Layer Convergence)/FLD (Frequency Layer Dispersion).
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package. l l License The license is activated. Other Prerequisites The UE should support this feature.
Context
Frequency Layer Convergence (FLC) denotes the process where the UTRAN requests UEs to preferentially re-select 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 the frequencies after an MBMS service is finished.
Procedure
NOTE
l This feature depends on the MBMS basic function. This feature can be activated only after MBMS basic functions are enabled. For details, see the Configuring MBMS Introduction Package. l In the overlapping area, ensure that 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.
Activate FLC in each cell. Run the BSC6900 MML command ADD UCELLMCCH. In this step, set FlcAlgoSwitch to ON to enable the FLC function in PtM mode. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select HO_ALGO_MBMS_FLC_SWITCH in the HoSwitch parameter to enable the FLC function in PtP mode.
2. l
Activate the FLD function. The FLD function is activated automatically when the FLC function is activated.
Verification Procedure 1. Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the MBMS status in the cell and whether FLC and FLD are enabled.
7-384
2. 3. 4. l 1.
Use an MBMS-supportive UE to access a cell that works in a frequency other than F1. Use the UE to request an MBMS service and receive the corresponding data. You can detect that the UE reselects F1 to receive MBMS data. Deactivate the FLC function. Run the BSC6900 MML command ADD UCELLMCCH. In this step, set FlcAlgoSwitch to OFF to disable the FLC function in PtM mode. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect HO_ALGO_MBMS_FLC_SWITCH in the HoSwitch parameter to disable the FLC function in PtP mode.
2. ----End
Deactivate the FLD function.
Example
//Activating MBMS FLC (Frequency Layer Convergence)/FLD (Frequency Layer Dispersion) ADD UCELLMCCH: FlcAlgoSwitch=ON; SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-1;
7.213 Configuring MBMS over Iur

This section describes how to activate, verify, and deactivate the optional feature WRFD-010661 MBMS over Iur.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010660 MBMS Phase 2. l l License The license is activated. Other Prerequisites The neighboring RNC should support MBMS Iur function.
Context
This feature supports the MBMS service crossing the Iur interface to extend the application scope of the MBMS service.
Procedure
l
Issue 03 (2010-09-20)
This feature takes effect when the cell is enabled with WRFD010616 MBMS Introduction Package and the license for this feature is activated, and also, the feature is deactivated as long as the license for this feature is deactivated. For details on how to activate the MBMS, see the section "Configuring MBMS Introduction Package". l l Verification Procedure None Deactivation Procedure None ----End
7.214 Configuring Dynamic Power Estimation for MTCH

This section describes how to activate, verify, and deactivate the optional feature WRFD-010662 Dynamic Power Estimation for MTCH.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010660 MBMS Phase 2. l License The license is activated.
Context
This feature enables the dynamic adjustment of the transmit power of the MTCH based on the number of neighboring cells in PTM mode. This feature depends on the basic MBMS functions. For details, see the section Configuring MBMS Introduction Package.
Procedure
l Activation Procedure This feature is activated as long as the corresponding license is activated and the power adjusting threshold is set. 1. Run the BSC6900 MML command SET URNCMBMSPARA to set the rate of the intra-frequency neighboring cells that applies the PTM mode for reducing the FACH power for MBMS services. 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 PTM mode in cell A and PTP mode in cell B.
7-386
2.
Activate an MBMS service. View theNBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub interface to check the power of the FACH that carries the service. Set cell B to send the MBMS services in the same channel in PtM mode. In this manner, the rate of the intra-frequency neighboring cells that applies the PTM mode exceeds the value of the preset CombNCellPercent parameter. 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. The power should have decreased by 5 dB.
3.
4.
Deactivation Procedure This feature is deactivated as long as the license for this feature is deactivated.
----End
Example
//Activating Dynamic Power Estimation for MTCH SET URNCMBMSPARA: CombNCellPercent=50;
7.215 Configuring MSCH and MSCH Scheduling

This section describes how to activate, verify, and deactivate the optional feature WRFD-010626 MSCH and MSCH Scheduling.
Prerequisite
l l The network is ready. For the dependency on other NEs, see the Optional Feature Description of Huawei UMTS. The license has been activated.
Context
This feature enables the UE to perform DRX on the MTCH based on MSCH scheduling, thus saving the power consumption of the UE. For details, see the Optional Feature Description of Huawei UMTS.
Procedure
l Activation Procedure This feature depends on the basic MBMS functions. For details, see the section "Configuring MBMS Introduction Package". 1. Run the RNC MML command SET UMBMSSWITCH to enable MSCH scheduling.
SET UMBMSSWITCH: MbmsSwitch=ON, MschSwitchForNonMtchMulti=ON, MschSwitchForMtchMulti=ON;
Verification Procedure 1. 2. Make the RNC to start an MBMS PtM service Check the MBMS CURRENT CELL P-T-M RB INFORMATION, MBMS GENERAL INFORMATION, and MBMS NEIGHBOURING CELL P-T-M RB
Issue 03 (2010-09-20)
INFORMATION messages traced over the Uu interface. The MSCH configuration information is contained in the messages. 3. l Use an MBMS-supportive UE to request an MBMS service. The UE can receiver the MBMS data successfully. Run the RNC MML command SET UMBMSSWITCH to disable MSCH scheduling.
SET UMBMSSWITCH: MschSwitchForNonMtchMulti=OFF, MschSwitchForMtchMulti=OFF;
----End
7.216 Configuring MBMS Channel Audience Rating Statistics

This section describes how to activate, verify, and deactivate the optional feature WRFD-010665 MBMS Channel Audience Rating Statistics.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010616 MBMS Introduction Package. l l License The license is activated. Other Prerequisites The BMSC on the CN side shall identify the channels with a fixed TMGI when delivering the program source.
Context
This feature enables the statistics of the information on MBMS channels to help the operator obtain the audience rating of the MBMS channels. It contains the following counters: l l l l l l l l l l
7-388
VS.MBMS.PTM.Channel0.Dur.Cell VS.MBMS.PTM.Channel1.Dur.Cell VS.MBMS.PTM.Channel2.Dur.Cell VS.MBMS.PTM.Channel3.Dur.Cell VS.MBMS.PTM.Channel4.Dur.Cell VS.MBMS.PTP.Channel0.Dur.Cell VS.MBMS.PTP.Channel1.Dur.Cell VS.MBMS.PTP.Channel2.Dur.Cell VS.MBMS.PTP.Channel3.Dur.Cell VS.MBMS.PTP.Channel4.Dur.Cell
l l l l l l l l l l
VS.MBMS.PTM.UE.Channel0.Mean.Cell VS.MBMS.PTM.UE.Channel1.Mean.Cell VS.MBMS.PTM.UE.Channel2.Mean.Cell VS.MBMS.PTM.UE.Channel3.Mean.Cell VS.MBMS.PTM.UE.Channel4.Mean.Cell VS.MBMS.PTP.UE.Channel0.Mean.Cell VS.MBMS.PTP.UE.Channel1.Mean.Cell VS.MBMS.PTP.UE.Channel2.Mean.Cell VS.MBMS.PTP.UE.Channel3.Mean.Cell VS.MBMS.PTP.UE.Channel4.Mean.Cell
Procedure
l Activation Procedure This feature takes effect when the cell is enabled with MBMS and the license for this feature is activated. For detailed MBSM activation, see the section "Configuring MBMS Introduction Package". For the counter detail information about the audience rating of the MBMS channels, see the MBSC 6900 Performance Counter Reference. l Verification Procedure None l Deactivation Procedure None ----End
7.217 Configuring Domain Specific Access Control (DSAC)

This section describes how to activate, verify, and deactivate the optional feature WRFD-020114 Domain Specific Access Control (DSAC).
Prerequisite
l Dependency on Hardware DSAC is based on the CN overload message and so the CN nodes should support this message on the Iu interface. The software version is RAN11.0 or later. l l l
Issue 03 (2010-09-20)
Dependency on Other Features None License The license is activated. Other Prerequisites
Because this is a feature specified in 3GPP R6, only the UEs of R6 support this function.
Context
l l The DSAC feature specifies the UE access restriction based on the domain type (CS, PS, or CS+PS). The feature can be triggered either manually or automatically. Quick blocking/unblocking of cells is activated by setting the access restriction information element (IE) in the system information of cells. This feature applies to only idle UEs.
Procedure
l Activation Procedure 1. Activate manual DSAC. Run the BSC6900 MML command ADD UCELLDSACMANUALPARA. To set the access restriction for the CS domain, set Restriction for CS to TRUE. To set the access restriction for the PS domain, set Restriction for PS to TRUE. To set a fixed access restriction, set Restriction Type to RestrictionFixed, and then select the access class (AC) to be restrained through AC Restriction Indicator. To set a flexible access restriction, set Restriction Type to RestrictionFlexible, and then set the number of ACs to be restrained every time, range of restrained ACs, and polling interval through Number of restrained AC every time, Range of restrained AC, and Interval of DSAC Restriction. 2. Activate automatic DSAC. Run the BSC6900 MML command SET UDSACAUTOALGO to set Switch for auto DSAC to ON. To set the access restriction for the CS domain, set Restriction for CS to TRUE. To set the access restriction for the PS domain, set Restriction for PS to TRUE. Set the number of ACs to be restrained every time and the range of restrained ACs through Number of restrained Access Class every time and Range of restrained Access Class. Set the polling interval through Interval length of Domain Specific Access Class Restriction. Then set the system information update interval for cells through Access Class Restriction interval between Cells. 3. Activate quick blocking/unblocking of cells. To perform quick blocking/unblocking of cells based on the BSC6900, run the BSC6900 MML command ADD URNCALLCELLBLK. To perform quick blocking/unblocking of cells based on the telecom operator, run the BSC6900 MML command ADD UCNOPALLCELLBLK. Set the domain type for the blocking through Blocked domain type. Set the blocking duration through Processing duration. l Verification Procedure 1. Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 7-92.
7-390
Issue 03 (2010-09-20)
2.
Check whether the DSAC feature is activated. Check the domainSpecificAccessRestrictionParametersForPLMNOfMIB IE in the SIB3 message traced over the Uu interface. If the value of one or more AccessClassBarred parameters in the domainSpecificAccessRestrictionParametersForPLMNOfMIB IE is barred (0), as shown in Figure 7-93, the feature is activated. If the values of all AccessClassBarred parameters in the domainSpecificAccessRestrictionParametersForPLMNOfMIB IE are notBarred (1), as shown in Figure 7-94, the feature is not activated. Figure 7-93 DSAC activated
Issue 03 (2010-09-20)
7-391
Figure 7-94 DSAC not activated
3.
Check whether the quick blocking/unblocking of cells based on the RNC for CS or PS is activated: Check whether the CN-DomainSysInfoList IE in the SIB1 message traced over the Uu interface contains the cn-DomainIdentity:ps-domain (0) or cnDomainIdentity:cs-domain (0) parameter. If either of the two parameters exist, as shown in Figure 7-95, the feature is activated. If neither of the two parameters exist, the feature is not activated. Figure 7-95 RNC-based cell blocking activated (for CS or PS)
4.
Check whether the quick blocking/unblocking of cells based on the RNC for both CS and PS is activated. Check whether the cellAccessRestriction IE in the SIB3 message traced on the Uu interface contains the intraFreqCellReselectionInd: allowed (0) tBarred:s10(0) parameter. If the parameter exists, as shown in Figure 7-96, the feature is activated. If the parameter does not exist, the feature is not activated.
7-392
Issue 03 (2010-09-20)
Figure 7-96 RNC-based cell blocking activated (for both CS and PS)
Deactivation Procedure 1. 2. 3. Deactivate manual DSAC: Run the BSC6900 MML command RMV UCELLDSACMANUALPARA. Deactivate automatic DSAC: Run the BSC6900 MML command SET UDSACAUTOALGO to set Switch for auto DSAC to OFF. Deactivate quick blocking/unblocking of cells. For RNC-based quick blocking of cells, run the BSC6900 MML command RMV URNCALLCELLBLK. For operatorbased cell quick blocking, run the BSC6900 MML command RMV UCNOPALLCELLBLK.
----End
Example
//Verifying Domain Specific Access Control (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; ADD URNCALLCELLBLK: DomainType=CsAndPsBlk, ProcessDuration=10; ADD UCNOPALLCELLBLK: CnOpIndex=0, DomainType=CsAndPsBlk, ProcessDuration=10; //Deactivating Domain Specific Access Control (DSAC) RMV UCELLDSACMANUALPARA: CellId=223, CnOpIndex=0; SET UDSACAUTOALGO: DsacAutoSwitch=OFF; RMV URNCALLCELLBLK RMV UCNOPALLCELLBLK: CnOpIndex=0;
7.218 Configuring One Tunnel

This section describes how to activate, verify, and deactivate the optional feature WRFD-020111 One Tunnel.
Prerequisite
l l
Issue 03 (2010-09-20)

None l l License The license is activated. Other Prerequisites Require GGSN and SGSN support such feature at the same time.
Context
With this feature, there is only one tunnel between the BSC6900 and GGSN. This feature improves efficiency for PS traffic. It prevents the SGSN from being the bottleneck of the network in the case of heavy PS traffic.
Procedure
l The One Tunnel feature is available after the license is activated and the transmission resources are configured. For details about transmission resource configuration, see the section Configuring the Iu-PS Interface (over IP) in the BSC6900 UMTS Initial Configuration Guide.
NOTE
l To check whether the SGSN supports the One Tunnel feature, run the MML command DSP LICENSE at the SGSN. To check whether the GGSN supports the One Tunnel feature, run the CLI command display license config at the GGSN.
----End
7.219 Configuring Hybrid Iub IP Transmission

This section describes how to activate, verify and deactivate the optional feature WRFD-050403 Hybrid Iub IP Transmission.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub Interface. l License The license is activated.
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.
7-394
Issue 03 (2010-09-20)
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. Set the parameter Adjacent Node Type to IUB and the parameter Transport Type to HYBIRD_IP. Run the BSC6900 MML command ADD IPPATH to add an IP path. Set the parameter Interface Type to IUB and the parameter Transport Type to HYBIRD_IP. IP Path Type is set to QOS or BE~EF, indicating a high-priority path that corresponds to a high-priority transport link (usually E1/T1). IP Path Type is set to LQ_QOS or LQ_BE~LQ_EF, indicating a low-priority path that corresponds to a low-priority transport link (usually FE). Run the BSC6900 MML command ADD TRMMAP to set the parameter Interface Type to IUB and the parameter Transport Type to HYBIRD_IP. Run the BSC6900 MML command ADD ADJMAP to set the parameter Interface Type to IUB, and the parameter Transport Type of the adjacent node and interface type to HYBIRD_IP. 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.
NOTE
2.
3. 4.
Run the BSC6900 MML command DSP IPCHN to check the access service type, forward bit rate and backward bit rate of the IP path.
----End
7.220 Configuring ATM/IP Dual Stack Node B

This section describes how to activate, verify and deactivate the optional feature WRFD-050404 ATM/IP Dual Stack Node B.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub Interface. l l License The license is activated. Othters ATM/IP physical transport links from the RNC to the NodeB have been configured.
Context
With this feature, the services with different QoS requirements can be carried on the links of different protocols. This feature helps protect operators investment and provide flexible networking.
Procedure
l Activation Procedure For details, see section "Configuring the Iub Interface (over ATM and IP)" of the BSC6900 UMTS Initial Configuration Guide . l Verification Procedure None l Deactivation Procedure None l ----End
7.221 Configuring FP MUX for IP Transmission

This section describes how to activate, verify and deactivate the optional feature WRFD-050420 FP MUX for IP Transmission.
Prerequisite
l l Dependency on Hardware The FG2a/GOUa/FG2c/GOUc/POUc support FP MUX for BSC6900. Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub Interface. l License The license is activated.
Context
In the case of IP transmission on the Iub interface, the packets of the user plane are encapsulated within UDP/IP/L2. However, the UDP, IP, and L2 encapsulated head is too large for short packets, which leads to low transmission efficiency. FP multiplexing is to multiplex the qualified UDP packets at the transmitting end to improve transmission efficiency, and to demultiplex the UDP packets at the receiving end to restore the original UDP contents.
Procedure
l
7-396
Activating Procedure
1.
Run the BSC6900 MML command ADD IPMUX to activate the FPMUX function for the configured IPPATH of the Iub type. If the FP MUX function is configured for multiple paths, run this command repeatedly. Run the NodeB MML command SET FPMUX to configure the Iub MUX function on the NodeB side. Run the BSC6900 MML command LST IPMUX to check whether the user-plane packet sent by the FPMUX-activated IPPATH of the IUB type is in the FP frame. Run the BSC6900 MML command RMV IPMUX to delete the IP MUX pipe.
2. l
Deactivating Procedure 1.
----End
Example
//Activating FP MUX for IP transmission ADD IPMUX: MUXTYPE=FPMUX, ANI=1, PATHID=1, ISQOSPATH=NO; //Verfying FP MUX for IP transmission LST IPMUX: IPMUXINDEX=1, MUXTYPE=FPMUX; //Deactivating FP MUX for IP transmission RMV IPMUX: IPMUXINDEX=1;
7.222 Configuring IP Fault Detection Based on BFD

This section describes how to activate and deactivate the optional feature WRFD-050421 IP Fault Detection Based on BFD.
Prerequisite
l Dependency on Hardware BSC6900 The FG2a/FG2c and GOUa/GOUc support BFD/ARP for BSC6900. NodeB In RAN11.0, only 3900 series NodeB support this feature. In RAN12.0, BTS3812E/AE, DBS3800, 3900 NodeB support this feature. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub Interface, or WRFD-050409 IP Transmission Introduction on Iu Interface, or WRFD-050410 IP Transmission Introduction on Iur Interface. l l License The license is activated. Other Prerequisites Router or peer entity should support BFD.
Context
When the gateway or peer entity is faulty, this feature enables the RNC to trigger IP re-route or board switch, thus avoiding packet loss and call drop.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command STR IPCHK to trigger IP re-route or board switch.
NOTE
l To trigger BFD-based re-route, set Check type to SBFD or MBFD. l If the peer router supports and starts the BFD function, set Check type to SBFD or MBFD. l If the Ethernet port is the active port, the check mode is CHECK_ON_PRIMARY_PORT; if the Ethernet port is a standby port, the check mode is CHECK_ON_INDEPENDENT_PORT. l If the Ethernet port is in active/standby mode and WHETHERAFFECTSWAP is set to YES, the Ethernet port switches from active to standby mode when BFD is faulty.
l l
Verification Procedure None Deactivation Procedure 1. Run the BSC6900 MML command STP IPCHK to stop.
----End
7.223 Configuring Dynamic Bandwidth Control of Iub IP

This section describes how to activate, verify, and deactivate the optional feature WRFD-050422 Dynamic Bandwidth Control of Iub IP.
Prerequisite
l Dependency on Hardware The FG2a and GOUa support this feature for BSC6900. The NUTI supports this feature for NodeB. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub Interface. l License The license is activated.
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 l
7-398
Activating Procedure 1. Run the BSC6900 MML command ACT IPPM to activate the IP PM. Verification Procedure
1. 2.
Log on the BSC6900 LMT, click the Monitor tab. The Monitor Navigation Tree tab page is displayed. On the displayed monitoring navigation tree, choose Monitor > Common Monitoring > Link Performance Monitoring. The Link Performance Monitoring dialog box is displayed. Configure monitoring parameters, select Logical Port Bandwidth for Monitor Item, and set the Subrack No. and Slot No. of the logical port. Observe the bandwidth change of the logical port. Click Submit, as shown in Figure 7-97.
3.
Figure 7-97 Link performance monitoring
Deactivating Procedure 1. Run the BSC6900 MML command DEA IPPM to deactivate the IP PM.
----End
Example
//Activating dynamic bandwidth control of Iub IP ACT IPPM: ANI=0, PATHID=1, ISQOSPATH=NO, LOSTPKTDETECTSW=OFF; //Deactivating dynamic bandwidth control of Iub IP DEA IPPM: ANI=0, PATHID=1;
7.224 Configuring Overbooking on IP Transmission

This section describes how to activate, verify, and deactivate the optional feature WRFD-050408 Overbooking on IP Transmission.
Prerequisite
l Dependency on Hardware RNC IP interface boards (WFIE / WFEE / WEIE board for BSC6800 & PEUa / FG2a/ FG2c / UOIa IP/UOIc_IP/ GOUa/GOUc board for BSC6900) all support backpressure
mechanism. FG2a/FG2c/GOUa/GOUc/UOIa_IP/UOIc_IP in BSC6900 and WFIE board in BSC6800 support LP shaping. l Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub Interface. l License The license is activated.
Context
Since services are incontinuous, there are periods with transmission activities and periods without transmission activities. For better use of Iub transmission resources, Huawei provides the Iub Overbooking function. Iub Overbooking adopts the admission control strategy to admit services. Services are admitted based on different activity factors, and admission of more services can be allowed to the bandwidth. Other strategies applied in overbooking are as follows: l l l RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm RNC Backpressure-Based Downlink Congestion Control Algorithm Shaping
Procedure
l Activation Procedure Activating RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the service flow control switch. For R99 BE services, set DRA_R99_DL_FLOW_CONTROL_SWITCH to ON. For HSDPA BE services, set DRA_HSDPA_DL_FLOW_CONTROL_SWITCH to ON. Activating RNC Backpressure-Based Downlink Congestion Control Algorithm 1. 2. Optional: Run the BSC6900 MML command ADD PORTFLOWCTRLPARA to configure the flow control parameters. Enable the flow control switch. You can run the RNC MML command SET OPT, SET ETHPORT, ADD/MOD IPLOGICPORT, ADD/MOD PPPLNK, or ADD/ MOD MPGRP to enable the flow control switch.
Activating Shaping Function 1. 2. l Run the BSC6900 MML command ADD IPLOGICPORT to add an IP LP. Run the BSC6900 MML command ADD IPPATH to add the path to the LP. Set Bearing type to IPLGCPORT.
Verification Procedure Take FE/GE-based IP transmission on the Iub interface as an example to describe how to verify backpressure-based flow control.
7-400
Issue 03 (2010-09-20)
1.
Set the subscriber information in the HLR for R99 UE1. The traffic class is streaming service, and the maximum bit rate (MBR) is 64 kbit/s in the uplink and 384 kbit/s in the downlink. Set the subscriber information in the HLR for HSDPA UE2. The traffic class is background service, and the MBR is 64 kbit/s in the uplink and 2048 kbit/s in the downlink. Set all IP paths to be carried on LP1, a 1920 kbit/s LP, and enable the flow control switch of LP1. Enable UE1 and UE2 to stay in idle mode and camp on CELL_A11. CELL_A11 must support HSDPA services. Set the threshold of HSDPA BE services to 768 kbit/s. Enable Uu, Iub, and Iu interface tracing on the LMT, and start the Du Meter software to query the throughput of the application layer. Dialing Test Activate PS streaming services on UE1 and keep downloading file from one FTP server. Activate PS BE services on UE2 and keep downloading file from one FTP server. Release the services. Expected Result LP1 is not congested and UE1 downloads data at MBR. LP1 is congested and the backpressure function is triggered. The throughput of UE2 decreases and that of UE1 remains unchanged. -
2.
3. 4. 5. 6.
Deactivation Procedure Deactivating RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the service flow control switch. For R99 BE services, set DRA_R99_DL_FLOW_CONTROL_SWITCH to OFF. For HSDPA BE services, set DRA_HSDPA_DL_FLOW_CONTROL_SWITCH to OFF. Deactivating RNC Backpressure-Based Downlink Congestion Control Algorithm 1. Disable the flow control switch. You can run the BSC6900 MML command SET OPT, SET ETHPORT, MOD IPLOGICPORT, MOD PPPLNK, or MOD MPGRP to disable the flow control switch.
----End
Example
//Verifying Overbooking on IP Transmission ADD IPLOGICPORT: SRN=0, SN=14, BT=FG2a, LPN=0, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=30, FLOWCTRLSWITCH=ON, FCINDEX=0; SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D768;
Issue 03 (2010-09-20)
7-401
7.225 Configuring UDP MUX for Iu-CS Transmission

This section describes how to activate the optional feature WRFD-050412 UDP MUX for IuCS Transmission.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050409 IP Transmission Introduction on Iu Interface. l l License The license is activated. Other Prerequisites The feature requires the CS CN element (MGW) to support UDP MUX.
NOTE
For detailed configuration, see the section "Configuring the Equipment Data" and the section "Configuring the Iu-CS Interface (over IP)" of the BSC6900 UMTS Initial Configuration Guide .
Context
This feature enables multiple RTP units to be encapsulated in one UDP packet on the Iu-CS interface to improve the transmission efficiency.
Procedure
l Activation Procedure 1. 2. Log in to the BSC6900 through the LMT. Run the BSC6900 MML command ADD IPMUX to configure the Iu-CS UDP MUX function on the BSC6900 side. Set the parameter IP MUX Type to UDPMUX. The parameters Max subframe length[byte], Maximum Frame Length[byte], and FPTIMER[ms] need to be planned based on actual networking. If the UDP MUX function is configured for multiple paths, run this command repeatedly.
l l
Verification Procedure None Deactivation Procedure None
----End
7.226 Configuring ATM Switching-Based Hub NodeB

This section describes how to activate, verify, and deactivate the optional feature WRFD-050105 ATM Switching-Based Hub NodeB.
Prerequisite
Context
This feature enables Huawei 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 l l Activation Procedure 1. 1. 1. ----End Run the NodeB MML command ADD TREELNKPVC to add a tree link PVC. Run the NodeB MML command LST TREELNKPVC to query the tree link PVCs. Run the NodeB MML command RMV TREELNKPVC to remove a tree link PVC. Verification Procedure Deactivation Procedure
Example
//Run the following command to add a tree link PVC. 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; //Run the following command to list a tree link PVC. RMV TREELNKPVC:; //Run the following command to remove a tree link PVC. RMV TREELNKPVC: NO=1;
7.227 Configuring AAL2 Switching-Based Hub NodeB

This section describes how to activate, verify, and deactivate the optional feature WRFD-050106 AAL2 Switching-Based Hub NodeB.
Prerequisite
l l Dependency on Hardware None Dependency on Other Features The configuration of the optional feature WRFD-050105 ATM Switching-Based Hub NodeB is completed. l
Issue 03 (2010-09-20)
License
None
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 Activation Procedure 1. 2. l Run the NodeB MML command ADD AAL2NODE to add an AAL2 node. In this step, set Node Type to HUB. Run the NodeB MML command ADD AAL2ADJNODE to add an AAL2 adjacent node. Run the NodeB MML command LST AAL2NODE to query the configurations of the AAL2 nodes. Run the NodeB MML command LST AAL2ADJNODE to query the configurations of the AAL2 adjacent nodes. Run the NodeB MML command RMV AAL2ADJNODE to remove an AAL2 adjacent node. Run the NodeB MML command RMV AAL2NODE to remove an AAL2 node. In this step, set Node Type to HUB.
NOTE
There is a relationship 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
//Run the following command to activate AAL2 switching-based Hub NodeB. ADD AAL2NODE: NT=HUB, LN=1; ADD AAL2ADJNODE: ANI=1, ADDR="0x3912323232323232333333333333333333333333", LN=2; //Run the following command to verify AAL2 switching-based Hub NodeB. LST AAL2NODE:; LST AAL2ADJNODE:; //Run the following command to deactivate AAL2 switching-based Hub NodeB. RMV AAL2ADJNODE: ANI=1; RMV AAL2NODE: NT=HUB;
7.228 Configuring IP Routing-Based Hub NodeB

This section describes how to activate, verify, and deactivate the optional feature WRFD-050107 IP Routing-Based Hub NodeB.
Prerequisite
l l Dependency on Hardware Only the 3900 series base stations support this feature. Dependency on Other Features The configuration of the optional feature WRFD-050402 IP Transmission Introduction on Iub Interface is completed. l License None
Context
This feature enables Huawei NodeB to provide the transmission convergence function in IP mode, thus increasing transmission efficiency and reducing transmission cost.
Procedure
l Activation Procedure 1. l Run the NodeB MML command ADD IPRT to add the IP route from the NodeB to BSC6900 or M2000. Run the NodeB MML command LST IPRT to query the configurations of the IP routes. Run the NodeB MML command RMV IPRT to remove an IP route.
----End
Example
//Activating IP routing-based Hub NodeB. 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"; //Verifying IP routing-based Hub NodeB. LST IPRT:; //Deactivating IP routing-based Hub NodeB. RMV 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";
7.229 Configuring Overbooking on Hub Node B Transmission

This section describes how to activate, verify, and deactivate the optional feature WRFD-050406 ATM QoS Introduction on Hub Node B (Overbooking on Hub Node B Transmission).
Prerequisite
l l
Issue 03 (2010-09-20)

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-050405 Overbooking on ATM transmission. l License The license is activated.
Context
Since services are incontinuous, there are periods with transmission activities and periods without transmission activities. For better use of Iub transmission resources, Huawei provides the Iub Overbooking function. Iub Overbooking adopts the admission control strategy to admit services. Services are admitted based on different activity factors, and admission of more services can be allowed to the bandwidth. Other strategies applied in overbooking are as follows: l l l RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm RNC Backpressure-Based Downlink Congestion Control Algorithm Shaping
Procedure
l Activation Procedure For details, see WRFD-050405 Overbooking on ATM Transmission. l Verification Procedure None l Deactivation Procedure None ----End
7.230 Configuring Ethernet OAM

This section describes how to activate, verify, and deactivate the optional feature WRFD-050425 Ethernet OAM.
Prerequisite
l l Dependency on RNC Hardware Only BSC6900 supports this feature. Dependency on NodeB 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; l Dependency on Other Features The configurations of the features on which this feature depends are complete. This 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 None
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, link monitoring, and fault detection and is not service, and it is not service-specific, as shown inFigure 7-98. Figure 7-98 PPP Ethernet OAM network
2.
E2E Ethernet OAM The E2E Ethernet OAM complies with IEEE 802.1ag draft 7. It is implemented based on services, maintenance domains, and E2E detection. When the RNC detects an Ethernet fault or degraded network performance using the Ethernet OAM feature, it can perform rerouting, port switchover, or board switchover to ensure the reliability of Ethernet link connections.
Procedure
l Activating the Ethernet OAM 3AH Function 1. l Run the BSC6900 MML command ACT EFMAH to activate the Ethernet OAM 3AH function. 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.
Activating the Ethernet OAM 1AG Function 1.
Issue 03 (2010-09-20)
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. 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
3.
The MEPID of the RemoteMep configured on the peer equipment must be consistent with the MEPID of the LocalMep configured on the local equipment.
4.
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 because transmission links are faulty or the peer side does not support the Ethernet OAM 3AH function. Activate the Ethernet OAM 3AH loopback function. If the loopback succeeds, the Alarm-21374 ETHOAM 3AH Remote Loopback is reported due to service congestion. 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. If 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. Run the BSC6900 MML command DEA EFMAH to deactivate the Ethernet OAM 3AH function. Run the BSC6900 MML command DEA CFMCCMTST to deactivate the Ethernet OAM unidirectional connectivity detection. Run the BSC6900 MML command RMV CFMMD to delete the Ethernet OAM maintenance domain (MD). Run the BSC6900 MML command RMV CFMMA to delete the Ethernet OAM maintenance association (MA). Run the BSC6900 MML command RMV CFMMEP to delete the Ethernet OAM maintenance end point (MEP).
Verifying the Ethernet OAM 3AH Function 1.
2.
Verifying the Ethernet OAM 1AG Function 1.
2. l
Deactivating the Ethernet OAM 3AH Function 1.
Deactivating the Ethernet OAM 1AG Function 1. 2. 3. 4.
----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,
7-408
Issue 03 (2010-09-20)
SN=18, PN=0; ACT CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1; //Verfying 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=1;
7.231 Configuring Clock Synchronization on Ethernet in NodeB

This section describes how to activate, verify, and deactivate the optional feature WRFD-050501 Clock Synchronization on Ethernet in NodeB.
Prerequisite
l l Dependency on Hardware The support from Huawei clock server is required. Dependency on Other Features The configuration of the optional feature WRFD-050402 IP Transmission Introduction on Iub Interface is completed. l License The license is activated.
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 Activation Procedure 1. 2. l l 1. 1. 2. Run the NodeB MML command ADD IPCLKLNK to add an IP clock link. Run the NodeB MML command SET CLKMODE to set the clock mode. Run the NodeB MML command LST IPCLKLNK to query the IP clock links. Run the NodeB MML command RMV IPCLKLNK to remove an IP clock link. Run the NodeB MML command SET CLKMODE to set the clock mode of the NodeB. Here, Set Clock Source Type to PEER. Set System Clock Working Mode to FREE. ----End
Verification Procedure Deactivation Procedure
Example
//Activating clock synchronization on Ethernet in NodeB. ADD IPCLKLNK: SRN=0, SN=7, LN=1, CIP="11.11.11.11", SIP="10.10.12.12", ICPT=HW_DEFINED; NEXTHOP="10.10.10.10"; SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, IPMODE=MANUAL, LN=1; //Verifying clock synchronization on Ethernet in NodeB. LST IPCLKLNK:; //Deactivating clock synchronization on Ethernet in NodeB. RMV IPCLKLNK: SRN=0, SN=7, LN=1; SET CLKMODE: MODE=MANUAL, CLKSRC=PEER;
7.232 Configuring Synchronous Ethernet

This section describes how to activate, verify, and deactivate the optional feature WRFD-050502 Synchronous Ethernet.
Prerequisite
l Dependency on Hardware Only the BSC6810 and BSC6900 support this feature. Only the 3900 series base stations support this feature. l l Dependency on Other Features None License The license is activated.
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 Activation Procedure 1. 2. l l Run the NodeB MML command SET CLKMODE to set the clock synchronization mode. Run the NodeB MML command ADD LNKSRC to set the line clock source as being extracted over the Ethernet port. Run the NodeB MML command LST CLKMODE to query the clock mode. Run the NodeB MML command SET CLKMODE to set the clock mode to free-run. In this step, set Clock Source Type to PEER. Run the NodeB MML command RMV LNKSRC to remove the line clock source.
Verification Procedure 1. 1. 2. Deactivation Procedure
----End
7-410
Issue 03 (2010-09-20)
Example
//Activating synchronous Ethernet. SET CLKMODE: MODE=MANUAL, CLKSRC= LINE; ADD LNKSRC: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=1; //Verifying synchronous Ethernet. LST CLKMODE:; //Deactivating synchronous Ethernet. SET CLKMODE: MODE=MANUAL, CLKSRC= PEER; RMV LNKSRC: SRN=0, SN=7;
7.233 Configuring RNC Node Redundancy

This section describes how to activate, verify, and deactivate the optional feature WRFD-040202 RNC Node Redundancy.
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None Dependency on License The license for this feature is activated. The Iur, Iu-CS and Iu-PS interfaces are configured. For the configuration procedure, see Configuring the Interfaces.
Context
With this feature, NodeBs can be connected to multiple RNCs and heartbeat detection is performed on the interfaces of the active RNC. When the active RNC is faulty, the NodeBs can be fast switched to the standby RNC for service provisioning. In this manner, the reliability and robustness of the network are improved. A primary RNC and a secondary RNC compose an RNC pool, as shown in Figure 7-99 and Figure 7-100.
Issue 03 (2010-09-20)
7-411
Figure 7-99 Network topology when RNC pool is not configured
Figure 7-100 Network topology when RNC pool is configured
NOTE
l When the serving RNC is faulty, the maximum service capability (such as Erlang of CS domain and the throughput of PS domain) decreases from the combined capability of two RNCs to the capability of one RNC. As a result, the processing specifications of the network decreases. l The configuration is mainly performed on the RNC and NodeB, and there are no specific configuration on the CN and M2000. You can check the homing state of the NodeB on the M2000.
Procedure
NOTE
This section takes RNC202 and RNC203 as examples. Assume that RNC202 is the primary RNC and RNC203 is the secondary RNC.
7-412
Issue 03 (2010-09-20)
1.
Configuration at Primary RNC (RNC202) (1) Run the BSC6900 MML command ADD URNCPOOL to add an RNC pool. In this step, set the parameters such as HeatBeat Sending Time Interval, HeatBeat Lost Times Threshold, HeatBeat Recover Times Threshold, and Iu State Policy For RncPool.
NOTE
The four parameters HeatBeat Sending Time Interval, HeatBeat Lost Times Threshold, HeatBeat Recover Times Threshold, and Iu State Policy For RncPool have default values, which are recommended to be used.
(2) Run the BSC6900 MML command ADD UNRNC to configure a neighboring RNC. (3) Run the BSC6900 MML command ADD URNCPOOLMEMBER to add a primary RNC to the RNC pool. (4) Run the BSC6900 MML command ACT URNCPOOL to activate the RNC node redundancy feature. (5) Configuring the alternative route between the primary RNC and the secondary RNC. a. When the transmission modes used over the Iu-CS/Iu-PS interface and Iur interface are the same, run the BSC6900 MML command ADD M3RT if IP transmission is used, and run the BSC6900 MML command ADD MTP3RT if ATM transmission is used. When the transmission modes used over the Iu-CS/Iu-PS interface and Iur interface are different, the STP function of the DSP should be enabled and the DSP should support both MTP3 and M3UA. Assume that IP transmission is applied over the Iur interface and ATM transmission is applied in the CN. 1) Run the BSC6900 MML command MOD N7DPC. In this step, setSTP function switch to ON(ON) and set DSP bear type to MTP3_M3UA(MTP3 and M3UA).
NOTE
b.
If the original value of STP function switch is OFF(OFF), this value can be changed when DSP bear type is set to MTP3(MTP3), and this value cannot be changed when DSP bear type is set to M3UA(M3UA) or MTP3_M3UA(MTP3 and M3UA).
2)
Run the BSC6900 MML command ADD MTP3RT to configure routes.
CAUTION
Alternative routes must cover all CNs to which the primary RNC and the secondary RNC are connected. Alternative routes refer to the routes between the primary RNC and the secondary RNC through the CN. (6) Add a NodeB who takes RNC202 as its primary-homing RNC. a. Run the BSC6900 MML command ADD UNODEB to add a NodeB who takes RNC202 as its primary-homing RNC.
7-413
Issue 03 (2010-09-20)
b. c. d.
Run the BSC6900 MML command ADD UNODEBALGOPARA to add NodeB algorithm parameters. Run the BSC6900 MML command ADD UNODEBLDR to and the load reshuffling parameters for the NodeB. Run the BSC6900 MML command ADD UNODEBOLC to add overload control (OLC) parameters for the NodeB. Run the BSC6900 MML command ADD ETHIP to add the IP address of the Ethernet port. Run the BSC6900 MML command ADD SCTPLNK to add an SCTP link. Run the BSC6900 MML command ADD SCTPLNK to add another SCTP link.
(7) Configure the IP transmission over the Iub interface. a. b. c.
(8) Run the BSC6900 MML command ADD UNCP to add a NodeB Control Port (NCP) link. (9) Run the BSC6900 MML command ADD UCCP to add a Communication Control Port (CCP) link. (10) Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. (11) Run the BSC6900 MML command ADD ADJMAP to add the transmission resource management mapping to the adjacent node. (12) Run the BSC6900 MML command ADD IPPATH to add an IP path. (13) Run the BSC6900 MML command ADD ULOCELL to add a local cell. (14) Run the BSC6900 MML command ADD UCELLQUICKSETUP to add the cell under the primary RNC and specify the cell ID under the secondary RNC. (15) Run the BSC6900 MML command ACT UCELL to activate the cell. (16) Run the BSC6900 MML command SET UPOOLPRIMHOSTPOLICY to set the re-host policy for the primary NodeB. 2. Configuration at Secondary RNC (RNC203) (1) Run the BSC6900 MML command ADD URNCPOOL to add an RNC pool. (2) Run the BSC6900 MML command ADD URNCPOOLMEMBER to add a secondary RNC to the RNC pool. (3) Run the BSC6900 MML command ADD UNRNC to configure a neighboring RNC. (4) Run the BSC6900 MML command ACT URNCPOOL to activate the RNC node redundancy feature. (5) Configuring the alternative route between the primary RNC and the secondary RNC. a. When the transmission modes used over the Iu-CS/Iu-PS interface and Iur interface are the same, run the BSC6900 MML command ADD M3RT if IP transmission is used, and run the BSC6900 MML command ADD MTP3RT if ATM transmission is used. When the transmission modes used over the Iu-CS/Iu-PS interface and Iur interface are different, the STP function of the DSP should be enabled and the DSP should support both MTP3 and M3UA. Assume that IP transmission is applied over the Iur interface and ATM transmission is applied in the CN.
Issue 03 (2010-09-20)
b.
7-414
1)
Run the BSC6900 MML command MOD N7DPC. In this step, setSTP function switch to ON(ON) and set DSP bear type to MTP3_M3UA(MTP3 and M3UA).
NOTE
If the original value of STP function switch is OFF(OFF), this value can be changed when DSP bear type is set to MTP3(MTP3), and this value cannot be changed when DSP bear type is set to M3UA(M3UA) or MTP3_M3UA(MTP3 and M3UA).
2)
Run the BSC6900 MML command ADD MTP3RT to configure routes.
CAUTION
Alternative routes must cover all CNs to which the primary RNC and the secondary RNC are connected. Alternative routes refer to the routes between the primary RNC and the secondary RNC through the CN. (6) Add a NodeB who takes RNC203 as its secondary-homing RNC. a. b. c. d. Run the BSC6900 MML command ADD UNODEB to add a secondary NodeB. Run the BSC6900 MML command ADD UNODEBALGOPARA to add NodeB parameters. Run the BSC6900 MML command ADD UNODEBLDR to and the load reshuffling parameters for the NodeB. Run the BSC6900 MML command ADD UNODEBOLC to add overload control (OLC) parameters for the NodeB. Run the BSC6900 MML command ADD ETHIP to add the IP address of the Ethernet port. Run the BSC6900 MML command ADD SCTPLNK to add an SCTP link. Run the BSC6900 MML command ADD SCTPLNK to add another SCTP link.
(7) Configure the IP transmission over the Iub interface. a. b. c.
(8) Run the BSC6900 MML command ADD UNCP to add a NodeB Control Port (NCP) link. (9) Run the BSC6900 MML command ADD UCCP to add a Communication Control Port (CCP) link. (10) Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. (11) Run the BSC6900 MML command ADD ADJMAP to add the transmission resource management mapping to the adjacent node. (12) Run the BSC6900 MML command ADD IPPATH to add an IP path. (13) Run the BSC6900 MML command ADD ULOCELL to add a local cell. (14) Run the BSC6900 MML command ADD UCELLQUICKSETUP to add the cell under the secondary RNC and specify the cell ID under the primary RNC. (15) Run the BSC6900 MML command ACT UCELL to activate the cell. 3.
Issue 03 (2010-09-20)
Configuration at the NodeB

(1) Configure the information of the primary RNC. a. Configure the IP transmission over the Iub interface. 1) 2) 3) b. c. d. a. Run the NodeB MML command ADD DEVIP to add the device IP address of the IP port. Run the NodeB MML command ADD SCTPLNK to add an SCTP link. Run the NodeB MML command ADD SCTPLNK to add another SCTP link.
Run the NodeB MML command ADD IUBCP to add an NCP link. Run the NodeB MML command ADD IUBCP to add an CCP link. Run the NodeB MML command ADD IPPATH to add an IP path. Configure the IP transmission over the Iub interface. 1) 2) 3) Run the NodeB MML command ADD DEVIP to add the device IP address of the IP port. Run the NodeB MML command ADD SCTPLNK to add an SCTP link. Run the NodeB MML command ADD SCTPLNK to add another SCTP link.
(2) Configure the information of the secondary RNC.
b. c. d. l
Run the NodeB MML command ADD IUBCP to add an NCP link. Run the NodeB MML command ADD IUBCP to add an CCP link. Run the NodeB MML command ADD IPPATH to add an IP path.
(3) Run the NodeB MML command ADD LOCELL to add a local cell. Verification Procedure 1. Method 1: Verifying the Configuration (1) Run the BSC6900 MML command DSP UCELL on the RNC202 LMT. The query result shows that cell 1 is available and normal. Run the BSC6900 MML command DSP UCELL on the RNC203 LMT. The query result shows that cell 2 is unavailable because of the absence of the control rights. (2) Perform analog test of the primary RNC fault Run the BSC6900 MML command RST UIU on the RNC202 LMT. If the system recovers too fast after the RST UIU command is executed, you can also remove the cable that connects the RNC to the CN. (3) Observe RNC203. You can find that after detecting the fault in RNC202 over the Iur interface, RNC203 takes over the NodeB. In addition, setup of cell 2 is initiated. (4) (Optional) When the connection between the NodeB and the primary RNC fails, the secondary RNC cannot obtain the NodeB control rights automatically. To solve this problem, run the BSC6900 MML command FOC UHOSTNODEB on the RNC203 LMT to make the NodeB be homed to the secondary RNC.
7-416
Issue 03 (2010-09-20)
CAUTION
This homing action disrupts the services if the connection between the NodeB and the primary RNC is normal. (5) At RNC203 and RNC202, run the BSC6900 MML command DSP UCELL. If the result at RNC203 shows that cell 2 is available and normal and the result at RNC202 shows that cell 1 is unavailable because of the absence of the control right, you can infer that the RNC node redundancy feature has been activated. Otherwise, you can infer that the RNC node redundancy feature has not been activated. 2. Method 2: Verifying the Function (1) Check that the heartbeat between RNC202 and RNC203 is normal. See Figure 7-101. Figure 7-101 Normal heartbeat between RNC202 and RNC203
(2) Check that the cell under RNC202 is available, and then set up a CS AMR service through a UE. See Figure 7-102 and Figure 7-103. Figure 7-102 RNC202 obtains the NodeB control rights
Issue 03 (2010-09-20)
7-417
Figure 7-103 CS AMR service be set up successfully
(3) Power off RNC202 when RNC203 works properly. RNC203 then takes over the NodeB control rights. Set up a CS AMR service through a UE. See Figure 7-104 and Figure 7-105. Figure 7-104 RNC203 takes over the NodeB control rights
(4) When RNC202 comes back to normal, it takes over the NodeB control rights again according to the re-homing policy, and RNC203 releases the NodeB control rights. Set up a CS AMR service through a UE. See Figure 7-106 and Figure 7-107.
Figure 7-106 RNC202 takes over the NodeB control rights again
3.
Verification through M2000 (1) The RNCs and NodeBs are created in the RNC POOL monitor. When creating a NodeB, the M2000 checks the homing state of the NodeB. If the RNC is a secondary-homing RNC for the NodeB, the NodeB cannot be created under that RNC. (2) When the homing state of the NodeB changes, the RNC reports the NodeB homing state to the M2000. The M2000 then update the network topology displayed in the RNC POOL monitor.
Deactivation Procedure 1. At RNC203 and RNC202, run the BSC6900 MML command DEA URNCPOOL to deactivate the feature.
----End
Example
//Activating RNC Node Redundancy //Configuration on Primary RNC /*Configuring RNC POOL*/ ADD URNCPOOL: RncPoolIndex=0, RncPoolName="redundancy_RNCPOOL";
Issue 03 (2010-09-20)
7-419

ADD URNCPOOLMEMBER: RncPoolIndex=0, NrncId=203; ACT URNCPOOL: RncPoolIndex=0;
//Configuring alternative route between primary RNC and secondary RNC (assume that ATM transmission is applied over Iu-CS/Iu-PS and Iur interfaces) ADD MTP3RT:DPX=12, SIGLKSX=1, PRIORITY=3, NAME="3#iupsyuhuiluyou"; /*Adding a dual-homing NodeB*/ ADD UNODEB: NodeBName="Redundancy_NODEB500", NodeBId=500, SRN=[spu Subrack No], SN=[spu Slot No.], SSN=1, TnlBearerType=IP_TRANS,IPTRANSAPARTIND=NOT_SUPPORT, HostType=PRIMHOST, PeerRncId=203, PeerNodebId=500, SharingType=RANSHARING; ADD UNODEBALGOPARA: NodeBName="Redundancy_NODEB500"; ADD UNODEBLDR: NodeBName="Redundancy_NODEB500"; ADD UNODEBOLC: NodeBName="Redundancy_NODEB500"; /*Configuring Iub over IP*/ ADD ETHIP: SRN=[INT Board's Subrack No.], SN=[INT Board's Slot No.], PN= [INT Board's Port No.], IPINDEX=0, IPADDR="150.150.150.150", MASK="255.255.255.0"; ADD SCTPLNK: SRN=[spu Subrack No], SN=[spu Slot No.], SCTPLNKN=500, MODE=SERVER, APP=NBAP, DSCP=62, LOCIP1="150.150.150.150", LOCIP2="0.0.0.0", PEERIP1="150.150.150.151", PEERIP2="0.0.0.0", PEERPN=1024, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=60000, RTOINIT=3000, RTOALPHA=12, RTOBETA=25, HBINTER=5000, MAXASSOCRETR=10, MAXPATHRETR=5, MTU=1500, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=1; ADD SCTPLNK: SRN=[spu Subrack No], SN=[spu Slot No.],SCTPLNKN=501, MODE=SERVER, APP=NBAP, DSCP=62, LOCIP1="150.150.150.150", LOCIP2="0.0.0.0", PEERIP1="150.150.150.151", PEERIP2="0.0.0.0", PEERPN=1025, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=60000, RTOINIT=3000, RTOALPHA=12, RTOBETA=25, HBINTER=5000, MAXASSOCRETR=10, MAXPATHRETR=5, MTU=1500, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=1; /*Configuring NCP,CCP*/ ADD UNCP: NODEBNAME="Redundancy_NODEB500", CARRYLNKT=SCTP, SCTPLNKN=500; ADD UCCP: NODEBNAME="Redundancy_NODEB500", PN=0, CARRYLNKT=SCTP, SCTPLNKN=501; ADD ADJNODE: ANI=500, NAME="Redundancy_NODEB500", NODET=IUB, NodeBId=500, TRANST=IP; ADD ADJMAP: ANI=500, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=1, TMISLV=1, TMIBRZ=1, FTI=0; ADD IPPATH: ANI=500, PATHID=0, ITFT=IUB, TRANST=IP, PATHT=QoS, IPADDR="150.150.150.150", PEERIPADDR="150.150.150.151", PEERMASK="255.255.255.0", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, TRMLOADTHINDEX=2, VLANFlAG=DISABLE, PATHCHK=DISABLED; /*Adding a local cell*/ ADD ULOCELL: NodeBName="Redundancy_NODEB500", LoCell=500; /*Configuring cell parameters*/ ADD UCELLQUICKSETUP: CellId=1, CellName="Redundancy_NODEB500_00",
7-420
Issue 03 (2010-09-20)
PeerIsValid=VALID, PeerCellId=2, CnOpGrpIndex=[Cn Operator Group Index], BandInd=Band1, UARFCNDownlink=10668, PScrambCode=500, TCell=CHIP0, LAC= [Location Area Code], SAC=[Service Area Code], CfgRacInd=REQUIRE, RAC= [Routing Area Code], SpgId=1, URANUM=D1, URA1=[UTRAN ID 1], NodeBName="Redundancy_NODEB500", LoCell=500, SupBmc=FALSE; //Configuration on Secondary RNC /*Configuring RNC POOL*/ ADD URNCPOOL: RncPoolIndex=0, RncPoolName="redundancy_RNCPOOL"; ADD URNCPOOLMEMBER: RncPoolIndex=0, NrncId=202; ACT URNCPOOL: RncPoolIndex=0; //Configuring alternative route between primary RNC and secondary RNC (assume that ATM transmission is applied over Iu-CS/Iu-PS and Iur interfaces) ADD MTP3RT: DPX=12, SIGLKSX=19, PRIORITY=2, NAME="yuhuipsto_121"; /*Adding a dual-homing NodeB*/ ADD UNODEB: NodeBName="Redundancy_NODEB500", NodeBId=500, SRN=SRN=[spu subrack No], SN=[spu slot No.], SSN=1, TnlBearerType=IP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT, HostType=SECHOST, PeerRncId=202, PeerNodebId=500, SharingType=RANSHARING; ADD UNODEBALGOPARA: NodeBName="Redundancy_NODEB500"; ADD UNODEBLDR: NodeBName="Redundancy_NODEB500"; ADD UNODEBOLC: NodeBName="Redundancy_NODEB500"; /*Configuring Iub over IP*/ ADD ETHIP: SRN=[INT Board's Subrack No.], SN=[INT Board's Slot No.], PN= [INT Board's Port No.], IPINDEX=0, IPADDR="160.160.160.160", MASK="255.255.255.0"; ADD SCTPLNK: SRN=[spu Subrack No], SN=[spu Slot No.], SCTPLNKN=500, MODE=SERVER, APP=NBAP, DSCP=62, LOCIP1="160.160.160.160", LOCIP2="0.0.0.0", PEERIP1="160.160.160.161", PEERIP2="0.0.0.0", PEERPN=1024, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=60000, RTOINIT=3000, RTOALPHA=12, RTOBETA=25, HBINTER=5000, MAXASSOCRETR=10, MAXPATHRETR=5, MTU=1500, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=1; ADD SCTPLNK: SRN=[spu Subrack No], SN=[spu Slot No.], SCTPLNKN=501, MODE=SERVER, APP=NBAP, DSCP=62, LOCIP1="160.160.160.160", LOCIP2="0.0.0.0", PEERIP1="160.160.160.161", PEERIP2="0.0.0.0", PEERPN=1025, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=60000, RTOINIT=3000, RTOALPHA=12, RTOBETA=25, HBINTER=5000, MAXASSOCRETR=10, MAXPATHRETR=5, MTU=1500, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=1; /*Configuring NCP,CCP*/ ADD UNCP: NODEBNAME="Redundancy_NODEB500", CARRYLNKT=SCTP, SCTPLNKN=500; ADD UCCP: NODEBNAME="Redundancy_NODEB500", PN=0, CARRYLNKT=SCTP, SCTPLNKN=501; ADD ADJNODE: ANI=500, NAME="Redundancy_NODEB500", NODET=IUB, NodeBId=500, TRANST=IP; ADD ADJMAP: ANI=500, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=1,
Issue 03 (2010-09-20)
7-421
TMISLV=1, TMIBRZ=1, FTI=0; ADD IPPATH: ANI=500, PATHID=0, ITFT=IUB, TRANST=IP, PATHT=QoS, IPADDR="160.160.160.160", PEERIPADDR="160.160.160.161", PEERMASK="255.255.255.0", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, TRMLOADTHINDEX=2, VLANFlAG=DISABLE, PATHCHK=DISABLED; /*Adding a local cell*/ ADD ULOCELL: NodeBName="Redundancy_NODEB500", LoCell=500; /*Configuring cell parameters*/ ADD UCELLQUICKSETUP: CellId=2, CellName="Redundancy_NODEB500_00", PeerIsValid=VALID, PeerCellId=1, CnOpGrpIndex=[Cn Operator Group Index], BandInd=Band1, UARFCNDownlink=10668, PScrambCode=500, TCell=CHIP0, LAC= [Location Area Code], SAC=[Service Area Code], CfgRacInd=REQUIRE, RAC= [Routing Area Code], SpgId=1, URANUM=D1, URA1=[URA ID 1], NodeBName="Redundancy_NODEB500", LoCell=500, SupBmc=FALSE; //Configuration on NodeB //Configuring primary RNC information on NodeB /*Configuring Iub over IP*/ ADD DEVIP: SRN=0, SN=0, SBT=BASE_BOARD, PT=ETH, PN=[BBU port No.], IP="150.150.150.151", MASK="255.255.255.0"; ADD SCTPLNK: SRN=0, SN=0, LOCIP="150.150.150.151", LOCPORT=1024, PEERIP="150.150.150.150", PEERPORT=58080; ADD SCTPLNK: SCTPNO=1, SRN=0, SN=0, LOCIP="150.150.150.151", LOCPORT=1025, PEERIP="150.150.150.150", PEERPORT=58080; /*Configuring NCP,CCP*/ ADD IUBCP: CPPT=NCP, BEAR=IPV4; ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=1; ADD IPPATH: PATHID=0, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, NODEBIP="150.150.150.151", RNCIP="150.150.150.150", DSCP=63, RXBW=100000, TXBW=100000, TXCBS=50000, TXEBS=50000, FPMUXSWITCH=DISABLE; //Configuring secondary RNC information on NodeB /*Configuring Iub over IP*/ ADD DEVIP: SRN=0, SN=0, SBT=BASE_BOARD, PT=ETH, PN=1, IP="160.160.160.161", MASK="255.255.255.0"; ADD SCTPLNK: SCTPNO=2, SRN=0, SN=0, LOCIP="160.160.160.161", LOCPORT=1024, PEERIP="160.160.160.160", PEERPORT=58080; ADD SCTPLNK: SCTPNO=3, SRN=0, SN=0, LOCIP="160.160.160.161", LOCPORT=1025, PEERIP="160.160.160.160", PEERPORT=58080; /*Configuring NCP,CCP*/ ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=2, BELONG=SLAVE; ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=3, BELONG=SLAVE; ADD IPPATH: PATHID=1, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETH, PN=1, JNRSCGRP=ENABLE, RSCGRPID=1, NODEBIP="160.160.160.161", RNCIP="160.160.160.160", DSCP=63, RXBW=100000, TXBW=100000, TXCBS=50000, TXEBS=50000, FPMUXSWITCH=DISABLE;
7-422
Issue 03 (2010-09-20)
//Adding a local cell ADD LOCELL: LOCELL=500, STN=0, SECN=0, SECT=REMOTE_SECTOR, SRN1=60, ULFREQ=9718, DLFREQ=10668, MXPWR=430, HISPM=FALSE, RMTCM=FALSE; //Verifying RNC Node Redundancy //RNC202 DSP UCELL: DSPT=BYCELL, CellId=1; //RNC203 DSP UCELL: DSPT=BYCELL, CellId=2; //RNC202 RST UIU: CnOpIndex=0, CNDOMAINID= ALL_DOMAIN, RSTCNTYPE=ALL_NODES; //RNC202 DSP UCELL: DSPT=BYCELL, CellId=1; //RNC203 DSP UCELL: DSPT=BYCELL, CellId=2; //Deactivating RNC Node Redundancy //RNC202&RNC203 DEA URNCPOOL: RncPoolIndex=0;
7.234 Configuring RRU Redundancy

This section describes how to activate, verify, and deactivate the optional feature WRFD-040203 RRU Redundancy.
Prerequisite
Context
RRU redundancy can improve the reliability and robustness of the RAN and shorten the duration of service disruption caused by an RRU failure, which improves service quality.
Procedure
l Activation Procedure 1. If a cell is configured as a MIMO and transmit diversity cell, run the BSC6900 MML command ADD UCELLALGOSWITCH or MOD UCELLALGOSWITCH. In this step, set Cell Capability Auto Handle Switch to TX_DIVERSITY_ON_TO_OFF or TX_DIVERSITY_OFF_TO_ON or to both. Run the NodeB MML command ADD LOCELL to ensure the local cell uses two power amplifiers.
2.
Issue 03 (2010-09-20)
Verification Procedure 1. Run the BSC6900 MML command LST UCELLALGOSWITCH to check that Cell Capability Auto Handle Switch is set to TX_DIVERSITY_ON_TO_OFF or TX_DIVERSITY_OFF_TO_ON. Run the NodeB MML command LST LOCELL to query whether the local cell is configured with two power amplifiers.
2. l
----End
Example
// Activation Procedure // When a cell is configured as a MIMO and transmit diversity cell, do as follows: ADD CELLALGOSWITCH: CellId=1, NBMUlCacAlgoSelSwitch=ALGORITHM_SECOND, NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND, CellCapacityAutoHandleSwitch=TX_DIVERSITY_ON_TO_OFF-1&TX_DIVERSITY_OFF_TO _ON-1; // Or MOD CELLALGOSWITCH: CellId=1, CellCapacityAutoHandleSwitch=TX_DIVERSITY_ON_TO_OFF-1&TX_DIVERSITY_OFF_TO _ON-1; // Ensure that the local cell uses two power amplifiers. // Add a local cell with the ID of 10 under sector 0 at site 1. Do as follows: ADD LOCELL: LOCELL=10, STN=1, SECN=0, SECT=REMOTE_SECTOR, RADIUS=10000, HORAD=150, CN1=0, SRN1=60, ULFREQ=9610, DLFREQ=10560, MXPWR=200, DI=0, HISPM=TRUE, SPR=250; // Verification Procedure // Query the cell algorithm switch. Do as follows: LST CELLALGOSWITCH: CellId=1; // Query whether the local cell is configured with two power amplifiers. Do as follows: LST LOCELL: MODE=LOCALCELL, LOCELL=10;
7.235 Configuring Transmit Diversity

This section describes how to activate, verify, and deactivate the optional feature WRFD-010203 Transmit Diversity.
Prerequisite
7-424
Issue 03 (2010-09-20)
Context
l l l Transmit diversity enables the Node B to provide twice the number of RF DL channels compared with no transmit diversity. 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.
Data Planning Parameter Site No. Cell ID Local Cell ID Sector No. Example 0 1 1 1 Source Network planning Network planning Network planning Network planning
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLSETUP 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). (1) In this step, set TX Diversity Indication to TRUE. (2) (Optional) Set STTD Support Indicator to STTD_Supported. (3) (Optional) Set CP1 Support Indicator to CP1_Supported. (4) (Optional) Set DPCH Tx Diversity Mode for Other User to STTD or CP1. (5) (Optional) Set FDPCH Tx Diversity Mode for Other User to STTD. As specified in 3GPP TS 25.211, the FDPCH can only use the STTD mode. 2. Run the NodeB MML command ADD SEC 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. Run the NodeB MML command ADD LOCELL 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. Run the NodeB MML command LST LOCELL. In this step, set Query Mode to LOCALCELL(Query Localcell by ID) and then specify Local Cell ID. Check the returned result on the LMT.
3.
----End
Example
// Activation Procedure MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE, STTDSupInd=STTD_Supported, CP1SupInd=CP1_not_Supported, DpchPrioTxDiversityMode=STTD, HspdschPrioTxDiversityMode=STTD, DpchDivModforMIMO=STTD; ADD SEC: STN=0, SECN=1, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE, ANT1SRN=20, ANT1N=R0A, ANT2SRN=21, ANT2N=R0A; ADD LOCELL: LOCELL=1, STN=0, SECN=1, SECT=REMOTE_SECTOR, TTW=TRUE, SRN1=20, SRN2=21, SN2=0, HISPM=FALSE, RMTCM=FALSE; // Verification Procedure LST LOCELL: MODE=LOCALCELL, LOCELL=1;
7.236 Configuring 4-Antenna Receive Diversity

This section describes how to activate, verify, and deactivate the optional feature WRFD-010209 4-Antenna Receive Diversity.
Prerequisite
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. 4antenna Receive Diversity improves the receiver sensitivity and the uplink coverage, so that the CAPEX can be reduced.
Procedure
l Activation Procedure 1. Run the NodeB MML command ADD SEC. 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. Run the NodeB MML command ADD ULGROUP. In this step, set Demodulation Work Mode to DEM_4_CHAN(4-Channels Demodulation Mode) or DEM_ECON_4_CHAN(Economical 4-Channels Demodulation Mode). Run the NodeB MML command LST SEC to check that the preceding parameters are correctly configured.
2.
----End
7.237 Configuring Extended Cell Coverage up to 200km

This section describes how to activate, verify, and deactivate the optional feature WRFD-021308 Extended Cell Coverage up to 200km.
Prerequisite
l Dependency on Hardware In the case of the NodeB 3900 series base stations, the WBBPb board needs to be configured. In the case of the BTS3812E and BTS3812AE, the EBBI board needs to be configured. In the case of the DBS3800, the EBBC or EBBM board needs to be configured. l l Dependency on Other Features None License None
Context
l 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
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command ADD UAICH. In this step, set AICH Transmission Timing to 1. Run the BSC6900 MML command ADD UPRACHBASIC. In this step, select available RACH sub channels in the cell from the RACH Sub Channel No. list. Run the BSC6900 MML command ADD UCELLSETUP. In this step, set Max Transmit Power of Cell to the maximum cell transmit power that is configured on the NodeB side. Run the BSC6900 MML command ADD UPCPICH. In this step, set PCPICH Transmit Power. Run the NodeB MML command ADD REMOTECELLGRP. In this step, set Remote Cell Group No and Remote Cell Group Name. Run the NodeB MML command ADD LOCELL. 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. Run the NodeB MML command LST REMOTECELLGRP to check that the remote cell group is configured. 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.
4. 5. 6.
l
Issue 03 (2010-09-20)
This feature does not need to be deactivated. ----End
7.238 Configuring High Speed Access

This section describes how to activate, verify, and deactivate the optional feature WRFD-010206 High Speed Access.
Prerequisite
l Dependency on Hardware 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. l l Dependency on Other Features None License None
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, thus reducing the Doppler effect and offering reliable services for the UE in high-speed movement.
NOTE
l Only the local sectors and remote sectors support the high speed access feature. Distributed sectors do not 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.
CAUTION
To enable the high speed access feature in the cells carrying services, first remove these cells, and then set up new cells. This process disrupts the ongoing services.
Procedure
l
7-428
1.
Run the NodeB MML command MOD LOCELL to modify the attributes of the specified local cell. In this step, set, High Speed Movement Mode to TRUE. Set Speed Rate as required. Run the NodeB MML command LST LOCELL to query the configuration 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. Run the NodeB MML command MOD LOCELL to modify the attributes of the local cell. In this step, set, High Speed Movement Mode to FALSE.
----End
Example
// Activation Procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, HISPM=TRUE, SPR=400; // Verification Procedure LST LOCELL: MODE=LOCALCELL, LOCELL=1; // Deactivation Procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, HISPM=FALSE;
7.239 Configuring PDCP Header Compression (RFC2507)

This section describes how to activate, verify, and deactivate the optional feature WRFD-011500 PDCP Header Compression (RFC2507).
Prerequisite
l l l l Dependency on Hardware None Dependency on Other Features None License The license is activated. Other Prerequisites The UE should support the compression function.
Context
This feature complies with the header compression function of packet data 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
Issue 03 (2010-09-20)
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the CFG_PDCP_RFC2507_HC_SWITCH check box under the Channel configuration strategy switch parameter. Initiate UE tracing on the BSC6900 LMT. 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.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear the CFG_PDCP_RFC2507_HC_SWITCH check box under the Channel configuration strategy switch parameter.
----End
Example
//Activating PDCP Header Compression (RFC2507). SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC2507_HC_SWITCH-1; //Deactivating PDCP Header Compression (RFC2507). SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC2507_HC_SWITCH-0;
7.240 Configuring HCS (Hierarchical Cell Structure)

This section describes how to activate, verify, and deactivate the optional feature WRFD-021200 HCS (Hierarchical Cell Structure).
Prerequisite
Context
According to speed estimation, the BSC6900 orders the fast-moving UE to handover to the cells of lower priority to reduce the number of handovers, and orders the slow-moving UEs to handover to the cells of higher priority to increase network capacity.
Procedure
l
7-430
1. 2. 3.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to select HO_ALGO_HCS_SPEED_EST_SWITCH in the HoSwitch parameter. Run the BSC6900 MML command ADD UCELLHCS to set HSC cell related parameters. Set the HCS parameters for different types of neighboring cells as follows: Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell and set the HCS related parameters. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell and set the HCS related parameters. Run the BSC6900 MML command ADD U2GNCELL to add a GSM inter-RAT neighboring cell and set the HCS related parameters.
4. l
For the cells whose HCS parameters have been set, run the BSC6900 MML command ADD UCELLHCSHO to set SpdEstSwitch to ON. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether the HCS switch is selected. Run the BSC6900 MML command LST UCELLHCS to check the setting of HCS parameters of the cell. Run the BSC6900 MML command LST UCELLHCSHO to check whether SpdEstSwitch is set to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear HO_ALGO_HCS_SPEED_EST_SWITCH from the HoSwitch parameter. Run the BSC6900 MML command MOD UCELLHCS to set the Use of HCS parameter to NOT_USED. Run the BSC6900 MML command MOD UCELLHCSHO to set the SpdEstSwitch parameter to OFF.
Deactivation Procedure 1. 2. 3.
----End
Example
//Activating HCS (Hierarchical Cell Structure). SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-1; ADD UCELLHCS: CellId=11, UseOfHcs=USED; ADD UINTRAFREQNCELL: RncId=1, CellId=11, NCellRncId=9, NCellId=100, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; 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 U2GNCELL: RncId=1, CellId=11, GSMCellIndex=0, CIOOffset=0, Qoffset1sn=0, Qrxlevmin=-50, TpenaltyHcsReselect=D0, TempOffset1=D3, BlindHoFlag=TRUE, BlindHOPrio=30, NPrioFlag=FALSE; 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;
Issue 03 (2010-09-20)
7-431
7.241 Configuring Intra Frequency Load Balance

This section describes how to activate, verify, and deactivate the optional feature WRFD-020104 Intra Frequency Load Balance.
Prerequisite
Context
This feature enables the change in cell load through the adjustment of cell PCPICH power.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the cell-oriented intra-frequency LDB algorithm. Run the BSC6900 MML command SET ULDCPERIOD to specify the period of intra-frequency LDB. Run the BSC6900 MML command MOD UCELLLDB to set the cell-oriented intrafrequency LDB algorithm parameters. Run the BSC6900 MML command MOD UPCPICHPWR to set the P-CPICH related parameters for intra-frequency LDB (Max transmit power of PCPICH and Min transmit power of PCPICH). Run the following commands to verify whether the activation is successful. LST UCELLALGOSWTICH LST ULDCPERIOD LST UCELLLDB LST UPCPICH l Deactivation Procedure 1. 2. ----End Run the MML command MOD UCELLALGOSWITCH to disable the cell-oriented intra-frequency LDB algorithm. Restore the parameters value that is changed in the activation procedure.
Example
//Activating Intra Frequency Load Balance MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-1;
7-432
Issue 03 (2010-09-20)
SET ULDCPERIOD: IntraFreqLdbPeriodTimerLen=1800; MOD UCELLLDB: CellId=111, PCPICHPowerPace=2, CellOverrunThd=90, CellUnderrunThd=30; MOD UPCPICHPWR: CellId=111, MaxPCPICHPower=313, MinPCPICHPower=346; //Deactivating Intra Frequency Load Balance MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-0;
7.242 Configuring Potential User Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-020105 Potential User Control.
Prerequisite
l l The network is ready. The license has been activated.
Context
This feature enables the reduction of system load through the modification of UE cell selection and reselection parameters. In this way, the cell where the UE camps can be controlled on the basis of cell load.
Procedure
l Activation Procedure 1. Run the MML command MOD UCELLALGOSWITCH to enable the cell-oriented PUC algorithm. For example,
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-1;
2.
Run the MML command SET ULDCPERIOD to specify the period of potential user control (PucPeriodTimerLen). For example,
SET ULDCPERIOD: PucPeriodTimerLen=1800;
3.
Run the MML command ADD UCELLPUC to set the cell-oriented PUC algorithm parameters. For example,
ADD UCELLPUC: CELLID=1, SPUCLIGHT=45, SPUCHEAVY=70, SPUCHYST=5, OFFSINTERLIGHT=-2, OFFSINTERHEAVY=2, OFFQOFFSET1LIGHT=-4, OFFQOFFSET2LIGHT=-4, OFFQOFFSET1HEAVY=4, OFFQOFFSET2HEAVY=4;
Verification Procedure 1. Run the following commands to verify whether the activation is successful. LST UCELLALGOSWTICH LST ULDCPERIOD LST UCELLPUC
Deactivation Procedure 1. Run the MML command MOD UCELLALGOSWITCH to close the cell-oriented PUC algorithm switch (PUC) (set NBMLdcAlgoSwitch to 0).
Issue 03 (2010-09-20)
For example,
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-0;
----End
7.243 Configuring License Control for Urgency

This section describes how to configure and verify the optional feature WRFD-040300 license control for urgency.
Prerequisite
l l l Dependency on Hardware Only the BSC6900 supports this feature. Dependency on Other Features None License The license is activated.
Context
CAUTION
This feature is enabled only in scenarios where the traffic volume increases abruptly, for example, in a disaster. This feature can be enabled only three time for each R version and it is valid only in seven days since it is enabled. l The license file includes function items and resource items. The use limit function of license function items can be enabled through the configuration of this feature. In this way, the hardware capacity is maximized.
Procedure
l Activation Procedure 1. l Run the BSC6900MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch to ON. Run the BSC6900MML command DSP LICUSAGE to view the resource items of the license. The returned result shows that all the values of the resource items reach the maximum values. 2. Run the BSC6900MML command LST LICENSECTRL to query the setting of Grace Protection Period Switch State.
7-434
The returned result shows the settings of Remaining Grace Protection Times, Remaining Grace Protection Days, and Grace Protection Period Switch State (the state is ON). l Deactivation Procedure 1. ----End Run the BSC6900MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch to OFF.
7.244 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g
This section describes how to activate, verify, and deactivate the optional feature WRFD-070004 Load Based GSM and UMTS Handover Enhancement Based on Iur-g.
Prerequisite
l Dependency on Hardware The BSC model is the BSC6900. A GSM+UMTS dual-mode MS is required. l Dependency on Other Features Configurations of other features on which this feature depends are complete. The features include WRFD-020306 Inter-RAT Handover Based on Load or WRFD-021200 HCS (Hierarchical Cell Structure). l l l License The license is activated. Both the 2G network and the 3G network are deployed. IP transmission mode is used on the Iur-g interface.
NOTE
l The licenses on the BSC and the RNC sides are activated separately. l Data is negotiated and planned for the inter-BSC6900 Iur-g interface.
Context
With the Co-RRM feature, the non-coverage-based handover is enhanced through common measurement and information interaction on the Iur-g interface.
Procedure
l Activation Procedure 1. Configuration on the RNC side (1) Run the BSC6900 MML command SET UMBSCCRRM to enable the noncoverage-based handover. In this step, set Non-coverage handover based on 2G load Indication to ON and Load-base handover based on 3G2G load difference Indication to ON. (2) Run the BSC6900 MML command SET UCORRMALGOSWITCH 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. (3) Run the BSC6900 MML command MOD UCELLALGOSWITCH 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 Cell LDC algorithm switch drop-down list box. (4) Run the BSC6900 MML command MOD UCELLLDR 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 inter-rat 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 (1) Run the BSC6900 MML command SET GCELLHOBASIC to enable interRAT handovers. In this step, set Inter-RAT Out BSC Handover Enable and Inter-RAT In BSC Handover Enable to YES(Yes) . (2) Run the BSC6900 MML command SET GCELLHOINTERRATLDB to set 2G Load Adjustment Coefficient. Setting 2G Load Adjustment Coefficient to 10 is recommended.
Verification Procedure 1. Verifying UMTS-to-GSM handover based on load enhancement (1) Run the following commands to put a UMTS cell into the basic congestion state: a. b. c. d. e. Run the BSC6900 MML command DEA UCELLHSDPA to deactivate the HSDPA function of the UMTS cell. Run the BSC6900 MML command ADD URESERVEOVSF to add a reserved DL code OVSF to the UMTS cell. Run the BSC6900 MML command ACT UCELLHSDPA to activate the HSDPA function in the UMTS cell. Run the BSC6900 MML command MOD UCELLLDM. In this step, set DL LDR trigger threshold to 30 and DL LDR release threshold to 30. Run the NodeB MML command STR DLSIM. In this step, set Load Ratio (%) to 30.
(2) Use the dual-mode MS to call a fixed telephone in the UMTS cell. Trace signaling on the Uu interface on the LMT. RRC_RRC_CONNECT_REQ and RRC_RRC_CONN_REJECT messages are reported. The RRC_RRC_CONN_REJECT message contains GSM-TargetCellInfo. That is, GSM cell information is contained. You can infer that the MS accesses the network in a GSM cell. 2.
7-436
Verifying GSM-to-UMTS handover based on load enhancement

(1) Run the MML command SET GTRXCHANADMSTAT to lock TCHs in the GSM cell and make the load in the GSM cell satisfy the load requirement for the inter-RAT load-based handover in the connection state. (2) Use the MS to initiate a call in the GSM cell. Trace signaling on the A interface on the LMT. Messages show that the MS succeeds in accessing the GSM cell. As measurement reports are reported, the MS initiates a load-based handover to a neighboring UMTS cell. The handover succeeds and the handover cause value in the Handover Required message is traffic(15). l Deactivation Procedure 1. Run the BSC6900 MML command SET UMBSCCRRM to deactivate MBSC Handover based on Load Enhancement on the UMTS side. In this step, set Noncoverage handover based on 2G load Indication to OFF(OFF) and Load-base handover based on 3G2G load difference Indication to OFF(OFF). Run the BSC6900 MML command SET GCELLHOINTERRATLDB to deactivate MBSC Handover based on Load Enhancement on the GSM side. In this step, set Allow Inter-RAT Load HO in Connect State to NO(No).
2.
----End
Example
//Activating MBSC 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*/ SET UCORRMALGOSWITCH: 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 inter-RAT handover*/ SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATOUTBSCHOEN=YES, INTERRATINBSCHOEN=YES; /*Setting 2G Load Adjustment Coefficient*/ SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0 G2GLoadAdjustCoeff=10; //Deactivating MBSC Handover based on Load Enhancement SET UMBSCCRRM: MbscNcovHoOn2GldInd=OFF, LoadHoOn3G2GldInd=OFF; SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=NO;
7.245 Configuring NACC Procedure Optimization Based on Iur-g

This section describes how to activate, verify, and deactivate the optional feature WRFD-070005 NACC Procedure Optimization Based on Iur-g between GSM and UMTS.
Prerequisite
l Dependency on Hardware The BSC model is the BSC6900. A GSM+UMTS dual-mode MS is required. l Dependency on Other Features Configurations of other features on which this feature depends are complete. This feature is necessary only when more than one of the following features exist: 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 Iur-g between GSM and UMTS, or HCS (Hierarchical Cell Structure). l l l l l License The license is activated. IP transmission mode is used on the Iur-g interface. The UE 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 neighboring cell of the UMTS cell.
NOTE
l The licenses on the BSC and the RNC sides are activated separately. l Data is negotiated and planned for the inter-BSC6900 Iur-g interface.
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 thus the handover delay is reduced. In addition, the NACC procedure does not require the support of the CN.
Procedure
l Activation Procedure 1. Configuration on the RNC side (1) Run the BSC6900 MML command SET UCORRMALGOSWITCH 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. (2) Run the BSC6900 MML command SET UMBSCCRRM to enable direct GERAN system information exchange. In this step, set GERAN System Information Exchange Switch to ON. (3) Run the BSC6900 MML command SET UCORRMALGOSWITCH 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.
(4) Run the BSC6900 MML command MOD UEXT2GCELL to enable the interRAT cell to support indication of the RIM procedure. In this step, set Inter-RAT cell support RIM indicator to TRUE. 2. Configuration on the BSC side (1) Run the BSC6900 MML command MOD GNRNC to allow NACC-related information exchange on the Iur-g interface. In this step, set Allow Info Exchange at Iur-g to YES(Support) and Info Exchange Content to NACCRELATED(NACC Info). (2) Run the BSC6900 MML command SET GCELLGPRS to set basic GPRS attributes of the GSM cell. In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU) and Support NACC to YES(Yes). l Verification Procedure 1. 2. 3. Trace Iur-g and Um interfaces on the LMT. Use a dual-mode MS to download data in the UMTS cell and then move the MS to the GSM cell. 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. Run the BSC6900 MML command SET UCORRMALGOSWITCH 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 //Configuration on the RNC side /*Enabling the NACC function*/ SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-1; /*Enabling direct GERAN system information exchange*/ SET UMBSCCRRM: MbscReqGeranInfoSwitch=ON; /*Enabling the inter-RAT handover*/ SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1; /*Enabling the inter-RAT cell to support indication of the RIM procedure*/ MOD UEXT2GCELL: GSMCellIndex=0, SuppRIMFlag=TRUE; //Configuration on the BSC side /*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 SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-0;
Issue 03 (2010-09-20)
7-439
7.246 Configuring MBSC Load Balancing

This section describes how to activate, verify, and deactivate the optional feature MRFD-211402 MBSC Load Balancing.
Prerequisite
l Dependency on Hardware The BSC model is the BSC6900. A GSM+UMTS dual-mode MS is required. l Dependency on Other Features Configurations of other features on which this feature depends are complete. This feature depends on features WRFD-020400 DRD Introduction Package and WRFD-020305 Inter-RAT Handover Based on Service. l l l l l License The license is activated. Both the 2G network and the 3G network are deployed. IP transmission mode is used on the Iur-g interface. The information element Service Handover in the RAB ASSIGNMENT REQUEST message sent from the CN to the RNC is Handover to GSM should be performed. The information element Service Handover in the RAB ASSIGNMENT REQUEST message sent from the CN to the BSC is Handover to UTRAN or cdma2000 should be performed. A GSM cell and a UMTS cell are configured and the GSM cell is configured as the neighboring cell of the UMTS cell.
NOTE
l The licenses on the BSC and the RNC sides are activated respectively. l Data is negotiated and planned for the inter-BSC6900 Iur-g interface.
Context
This feature is based on the internal information exchange mechanism of the MBSC. It enables load to be distributed on the basis of service attributes and load conditions in GSM and UMTS networks when an MS accesses a network. Load is distributed through RRC redirection and the load-based inter-RAT handover. In this manner, load in GSM and UMTS networks is balanced.
Procedure
l 3G-to-2G Load Balancing 1. Activation Procedure (1) Configuration on the RNC side a. Run the BSC6900 MML command SET UMBSCCRRM to enable load balancing and set the 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
Issue 03 (2010-09-20)
7-440
Service to 10, and PS Load Difference Threshold Between 3G And 2G of Ps Service to 30. b. Run the BSC6900 MML command SET UCORRMALGOSWITCH 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 dropdown list box. Run the BSC6900 MML command SET GCELLHOBASIC to enable the inter-RAT incoming BSC handover. In this step, set Inter-RAT In BSC Handover Enable to YES(Yes). If multiple neighboring cells are planned, repeat this step to enable the inter-RAT incoming BSC handover for all the neighboring cells.
(2) Configuration on the BSC side a.
2.
NOTE
If the verification achieves the following results as expected, the configuration is successful. Otherwise, the configuration is unsuccessful.
(1) Run the following commands to put a UMTS cell into the basic congestion state: a. b. c. d. e. Run the BSC6900 MML command DEA UCELLHSDPA to deactivate the HSDPA function of the UMTS cell. Run the BSC6900 MML command ADD URESERVEOVSF to add a reserved DL code OVSF to the UMTS cell. Run the BSC6900 MML command ACT UCELLHSDPA to activate the HSDPA function in the UMTS cell. Run the BSC6900 MML command MOD UCELLLDM. In this step, set DL LDR trigger threshold to 30 and DL LDR release threshold to 30. Run the NodeB MML command STR DLSIM. In this step, set Load Ratio (%) to 30.
(2) The verification procedure is divided into the RRC setup phase and RAB connection phase. The verification in the latter phase is divided into verification of CS speech services and PS data services. a. Verifying that CS speech services in UMTS cell 1 is reselected to GSM cell 2 during the RRC setup phase 1) Use the dual-mode MS to call a fixed telephone in cell 1. The call is successfully established. Trace signaling on the Uu interface on the LMT. RRC_RRC_CONNECT_REQ and RRC_RRC_CONN_REJECT messages are reported. The RRC_RRC_CONN_REJECT message contains GSMTargetCellInfo. That is, information about cell 2 is contained. You can infer that the MS accesses the network in cell 2.
b.
Verifying that PS data services in UMTS cell 1 is handed over to GPRS cell 3 during the RAB connection phase 1) 2) Use the MS to browse the Internet. Trace the Uu interface on the LMT. You can find that the RRC_CELL_CHANGE_ORDER_FROM_UTRAN message is sent from the RNC to the MS.
7-441
Issue 03 (2010-09-20)
3)
Trace the Iu interface 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. Trace the Iu interface on the LMT. You can find that 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. When the MS attempts to reselect to cell 3, Internet browsing is affected to some degree. After the MS reselects to cell 3, Internet browsing returns to normal.
4)
5)
c.
Verifying that CS speech services in UMTS cell 1 is handed over to GSM cell 2 during the RAB connection phase 1) 2) Use the dual-mode MS to call a fixed telephone in cell 1. The call is successfully established. Trace the Uu interface on the LMT. You can find that the RRC_HO_FROM_UTRAN_CMD_GSM message is sent from the RNC to the MS. Trace the Iu interface on the LMT. You can find that the RANAP_RELOCATION_REQUIRED message is sent from the RNC to the CN and then the RANAP_RELOCATION_COMMAND and RANAP_IU_RELEASE_COMMAND message is sent from the CN to the RNC. Trace the Iu interface on the LMT. You can find that the RANAP_IU_RELEASE_COMPLETE message is sent from the RNC to the CN.
3)
4)
3.
Deactivation Procedure (1) Run the BSC6900 MML command SET UMBSCCRRM to deactivate MBSC Load Balancing. In this step, set Service Distribution and Load Balancing Switch to OFF(OFF).
2G-to-3G Load Balancing 1. Activation Procedure Configuration on the BSC side (1) Configuring neighbor relation on the BSC side (2) Run the BSC6900 MML command SET GCELLHOINTERRATLDB to enable load balancing and set the load adjustment coefficient. In this step, set Allow Inter-RAT Load HO in Access State to Load-based(Load-based) and 2G Load Adjustment Coefficient to 10. (3) Run the BSC6900 MML command SET GCELLHOBASIC to enable the inter-RAT outgoing BSC handover. In this step, set Inter-RAT Out BSC Handover Enable to YES(Yes). (4) Run the BSC6900 MML command SET OTHSOFTPARA. In this step, set CCS 2G 3G Load Balance Delta Threshold to 110. Configuration on the RNC side
7-442
Issue 03 (2010-09-20)
(1) Run the BSC6900 MML command SET UMBSCCRRM. In this step, set Service Distribution and Load Balancing Switch to LOAD-BASED (LOAD-BASED). 2. Verification Procedure
NOTE
If the verification achieves the following results as expected, the configuration is successful. Otherwise, the configuration is successful.
(1) Run the MML command SET GTRXCHANADMSTAT to lock TCHs in the GSM cell and enable the load in the GSM cell to exceed the value of 2G Cell UL Basic Congest Thred. (2) Use the MS to initiate a call in the GSM cell. The directed retry procedure is triggered so that the MS accesses the network in the UMTS cell. The call is successfully established. 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 directed-retry(13). 3. Deactivation Procedure (1) Run the BSC6900 MML command SET GCELLHOINTERRATLDB to deactivate 2G-to-3G Load Balancing. In this step, set Allow Inter-RAT Load HO in Access State to OFF(OFF). ----End
Example
//Activating 3G-to-2G load balancing //Configuration on the RNC side /*Enabling load balancing and setting the load difference thresholds*/ SET UMBSCCRRM: MbscServiceDiffLdbSwitch=LOAD-BASED, Mbsc3G2GLdBlcCsDeltaThrd=10, Mbsc3G2GLdBlcPsDeltaThrd=30; /*Enabling the inter-RAT handover*/ SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1; //Configuration on the BSC side /*Enabling the inter-RAT incoming BSC handover*/ SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATINBSCHOEN=YES; //Deactivating 3G-to-2G load balancing SET UMBSCCRRM: MbscServiceDiffLdbSwitch=OFF; //Activating 2G-to-3G load balancing //Configuration on the BSC side /*Enabling load balancing*/ SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=YES, InterRatServiceLoadHoSwitch=Load-based, G2GLoadAdjustCoeff=10; /*Enabling the inter-RAT handover*/ SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATOUTBSCHOEN=YES; /*Setting Load Balance Delta Threshold*/ SET OTHSOFTPARA: G2G3GLdBlcDeltaThrd=110; //Deactivating 2G-to-3G load balancing SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, InterRatServiceLoadHoSwitch=OFF;
Issue 03 (2010-09-20)
7-443
7.247 Configuring GSM and UMTS Traffic Steering Based on Iur-g

This section describes how to activate, verify, and deactivate the optional feature WRFD-070007 GSM and UMTS Traffic Steering Based on Iur-g.
Prerequisite
l Dependency on Hardware The base station controllers are multi-mode BSCs (MBSCs), namely, the BSC6900s. A GSM+UMTS dual-mode MS is required. l Dependency on Other Features Configurations of other features on which this feature depends are complete. This feature depends on features WRFD-020400 DRD Introduction Package and WRFD-020305 Inter-RAT Handover Based on Service. l l l l l License The license is activated. Both the 2G network and the 3G network are deployed. IP transmission mode is used on the Iur-g interface. The information element Service Handover in the RAB ASSIGNMENT REQUEST message sent from the CN to the RNC is Handover to GSM should be performed. The information element Service Handover in the RAB ASSIGNMENT REQUEST message sent from the CN to the BSC is Handover to UTRAN or cdma2000 should be performed or Handover to UTRAN or cdma2000 should not be performed. A GSM cell and a UMTS cell are configured and the GSM cell is configured as the neighboring cell of the UMTS cell.
NOTE
l The licenses on the BSC and the RNC sides are activated respectively. l Data is negotiated and planned for the inter-BSC6900 Iur-g interface.
Context
With the Co-RRM feature, service distribution is enhanced through common measurement and information interaction on the Iur-g interface.
Procedure
l Activation Procedure 1. Configuration on the RNC side (1) Run the BSC6900 MML command SET UMBSCCRRM enable service distribution. In this step, set Service Distribution and Load Balancing Switch to SERVICE-BASED(SERVICE-BASED). (2) Run the BSC6900 MML command SET UCORRMALGOSWITCH 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. (3) Run the BSC6900 MML command ADD UCELLHOCOMM to enable interRAT CS and PS handovers. In this step, set Inter-RAT CS Handover Switch and Inter-RAT PS Handover Switch to ON respectively. If multiple cells are planned for service distribution, repeat this step. 2. Configuration on the BSC side (1) Run the BSC6900 MML command SET GCELLHOINTERRATLDB. In this step, set Allow Inter-RAT Load HO in Access State to Service-based(Servicebased). l Verification Procedure 1. Run the following commands to put a UMTS cell into the basic congestion state: (1) Run the BSC6900 MML command DEA UCELLHSDPA to deactivate the HSDPA function of the UMTS cell. (2) Run the BSC6900 MML command ADD URESERVEOVSF to add a reserved DL code OVSF to the UMTS cell. (3) Run the BSC6900 MML command ACT UCELLHSDPA to activate the HSDPA function in the UMTS cell. (4) Run the BSC6900 MML command MOD UCELLLDM. In this step, set DL LDR trigger threshold to 30 and DL LDR release threshold to 30. (5) Run the NodeB MML command STR DLSIM. In this step, set Load Ratio (%) to 30. 2. The verification procedure is divided into the RRC setup phase and RAB connection phase. The verification in the latter phase is divided into verification of CS speech services and PS data services. Verifying that CS speech services in UMTS cell 1 is reselected to GSM cell 2 during the RRC setup phase (1) Use the dual-mode MS to call a fixed telephone in cell 1. The call is successfully established. Trace signaling on the Uu interface on the LMT. RRC_RRC_CONNECT_REQ and RRC_RRC_CONN_REJECT messages are reported. The RRC_RRC_CONN_REJECT message contains GSM-TargetCellInfo. That is, information about cell 2 is contained. You can infer that the MS accesses the network in cell 2. Verifying that PS data services in UMTS cell 1 is handed over to GPRS cell 3 during the RAB connection phase (1) Use the MS to browse the Internet. (2) Trace the Uu interface on the LMT. You can find that the RRC_CELL_CHANGE_ORDER_FROM_UTRAN message is sent from the RNC to the MS. (3) Trace the Iu interface 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) Trace the Iu interface on the LMT. You can find that 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 to cell 3, Internet browsing is affected to some degree. After the MS reselects to cell 3, Internet browsing returns to normal. Verifying that CS speech services in UMTS cell 1 is handed over to GSM cell 2 during the RAB connection phase (1) Use the dual-mode MS to call a fixed telephone in cell 1. The call is successfully established. (2) Trace the Uu interface on the LMT. You can find that the RRC_HO_FROM_UTRAN_CMD_GSM message is sent from the RNC to the MS. (3) Trace the Iu interface on the LMT. You can find that the RANAP_RELOCATION_REQUIRED message is sent from the RNC to the CN and then the RANAP_RELOCATION_COMMAND and RANAP_IU_RELEASE_COMMAND message is sent from the CN to the RNC. (4) Trace the Iu interface on the LMT. You can find that the RANAP_IU_RELEASE_COMPLETE message is sent from the RNC to the CN. l Deactivation Procedure 1. Run the BSC6900 MML command ADD UCELLHOCOMM to disable inter-RAT CS and PS handovers. In this step, set Inter-RAT CS Handover Switch and InterRAT PS Handover Switch to OFF respectively. Run the BSC6900 MML command SET UMBSCCRRM to deactivate MBSC service distribution. In this step, set Service Distribution and Load Balancing Switch to OFF(OFF).
2.
----End
Example
//Activating 3G-to-2G service distribution //Configuration on the RNC side /*Enabling service distribution*/ SET UMBSCCRRM: MbscServiceDiffLdbSwitch=SERVICE-BASED; /*Enabling the inter-RAT handover*/ SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1; /*Enabling inter-RAT CS and PS handovers*/ ADD UCELLHOCOMM: CellId=1, CSServiceHOSwitch=ON, PSServiceHOSwitch=ON; //Configuration on the BSC side /*Enabling the inter-RAT incoming BSC handover*/ SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATINBSCHOEN=YES; //Deactivating 3G-to-2G service distribution SET UMBSCCRRM: MbscServiceDiffLdbSwitch=OFF;
7.248 Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority
This section describes how to activate, verify, and deactivate the optional feature WRFD-070201 GSM and UMTS Intelligent Shutdown Based on RAT Priority.
Prerequisite
Context
The operator can set the intelligent shutdown switch. With the switch set, closing the RF module is allowed or forbidden when the power-off alarm of the mains power is reported.
Procedure
l Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority on the NodeB Side 1. Activation Procedure Run the NodeB MML command SET ITELSHUTDOWN. In this step, set ISD SWITCH to ENABLE(Enable Itel Shutdown) and set LEVEL1 DELAY(s) and LEVEL2 DELAY(s) according to actual conditions. 2. Verification Procedure Run the NodeB MML command LST ITELSHUTDOWN and check the returned message. If... Information about the switch for intelligent shutdown matches the configuration. Information about the switch for intelligent shutdown does not match the configuration. Then... The configuration succeeds.
The configuration fails.
3.
Deactivation Procedure Run the NodeB MML command SET ITELSHUTDOWN. In this step, set ISD SWITCH to DISABLE(Disable Itel Shutdown).
Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority on the GBTS Side 1. Activation Procedure Run the BSC6900 MML command SET BTSBAKPWR. In this step, set Backup Power Saving Method to BYPWR(Reduce Backup Power). Then set Backup Power Saving Policy to BYCOVER(Cover Priority), BYCAP(Capability Priority), or BYSAVING(Saving Priority) according to the scenario. Set other parameters according to actual conditions.
Issue 03 (2010-09-20)
7-447
2.
Verification Procedure Run the BSC6900 MML command LST BTSBAKPWR and check the returned message. If... Information about the switch for intelligent shutdown matches the configuration. Information about the switch for intelligent shutdown does not match the configuration. Then... The configuration succeeds.
The configuration fails.
3.
Deactivation Procedure Run the BSC6900 MML command SET BTSBAKPWR. In this step, set Backup Power Saving Method to BYTRX(Turn off TRX).
----End
Example
// Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority on the NodeB side // Activation procedure SET ITELSHUTDOWN: ISD=ENABLE, LEVEL1=60, LEVEL2=120; // Verification procedure LST ITELSHUTDOWN: // Deactivation procedure SET ITELSHUTDOWN: ISD=DISABLE; // Configuring GSM and UMTS Intelligent Shutdown Based on RAT Priority on the GBTS side // Activation procedure SET BTSBAKPWR: IDTYPE=BYID, BTSID=123, BAKPWRSAVMETHOD=BYPWR, BAKPWRSAVPOLICY=BYSAVING, DROPPWRSTARTTIME=1, SHUTDOWNTRXSTARTTIME=2, DROPPWRINTERVAL=30, DROPPWRSTEP=2, MAXDROPPWRTHRESHOLD=20, PWROFFPROTECTSTARTTIME=30; // Verification procedure LST BTSBAKPWR: IDTYPE=BYID, BTSID=123; // Deactivation procedure SET BTSBAKPWR: IDTYPE=BYID, BTSID=123, BAKPWRSAVMETHOD=BYTRX.
7.249 Configuring Warning of Disaster

This section describes how to activate, verify, and deactivate the optional feature WRFD-020127 Warning of Disaster.
Prerequisite
l l
7-448

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-011000 Cell Broadcast Service. l License None
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, thus minimizing the impact of the disaster.
NOTE
Activating this feature requires operations on only the RNC.
Procedure
l Activation Procedure 1. 2. 3. For detailed operations for activating license, see 7.2.1 Activating the BSC6900 License. (Optional) Run the BSC6900 MML command RMV UCBSADDR to remove the CBS configuration, if the operator configured the CBS function using external CBC. Run the BSC6900 MML command SET URNCCBPARA to set CB switch and CTCH switch of cell broadcast to ON. By doing this, the system can configure the disaster warning message and send the message to UEs. Run the BSC6900 MML command ADD URNCCBCPUID to configure the SPU subsystem for the built-in CBC. Run the BSC6900 MML command ADD UCBSAREA to configure the broadcast area. The broadcast area can be a LAC, a cell, or all cells under the RNC. (The following procedure uses a cell as an example.) Run the BSC6900 MML command ADD UCBSMSG or MOD UCBSMSG to configure the broadcast message.
NOTE
4. 5.
6.
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.
Verification Procedure 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.
Deactivation Procedure 1. Run the BSC6900 MML command SET URNCCBPARA to set CTCH switch of cell broadcast to OFF.
----End
Example
//Activating warning of disaster RMV UCBSADDR: CnOpIndex=0; 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 waring of disaster SET URNCCBPARA: CTCHSwitch=OFF;
7.250 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).
Prerequisite
l Dependency on Hardware Only the MRFU and the RRU3908 supports GSM and UMTS Dynamic Power Sharing at present. l Dependency on Other Features 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 coexists with the baseband frequency hopping algorithm involving two power amplifiers. Their coexistence results in a certain level of performance loss. GSM and UMTS Dynamic Power Sharing under the MIMO is not considered. l License A license is required to activate GSM and UMTS Dynamic Power Sharing.
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 thus improved.
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 thus 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.
7-450
Issue 03 (2010-09-20)
Procedure
Step 1 Activation Procedure 1. Run the BSC6900 MML command SET BTSGUPWRSHRFP. In this step, set Board Parameter Configuration Enabled to YES(YES) and set the period for enabling GU power sharing. Run the BSC6900 MML command SET BTSRXUBP. In this step, set RXU Board Type to MRRU(MRRU) or MRFU(MRFU), set GU Dynamic Power Sharing Switch to YES(YES) and set other parameters according to actual conditions. Run the BSC6900 MML command LST BTSGUPWRSHRFP and LST BTSRXUBP and check the returned message. If... Board Parameter Configuration Enabled is YES(YES). GU Dynamic Power Sharing Switch is YES(YES). 2. Step 3 Deactivation Procedure 1. 2. Run the BSC6900 MML command SET BTSGUPWRSHRFP. In this step, set Board Parameter Configuration Enabled to NO(NO). Run the BSC6900 MML command SET BTSRXUBP. In this step, set GU Dynamic Power Sharing Switch to NO(NO).
NOTE
2.
Step 2 Verification Procedure 1.
Then... The sharing period of GSM and UMTS Dynamic Power Sharing is configured successfully. GSM and UMTS Dynamic Power Sharing is configured successfully.
GSM and UMTS Dynamic Power Sharing can be deactivated by performing either of the two steps discussed above.
----End
Example
// To activate GSM and UMTS Dynamic Power Sharing, run the following commands: 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; // To verify GSM and UMTS Dynamic Power Sharing, run the following commands: LST BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, LSTFORMAT=VERTICAL; LST BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0, LSTFORMAT=VERTICAL;
Issue 03 (2010-09-20)
7-451
// To deactivate GSM and UMTS Dynamic Power Sharing, run the following commands: 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.
7.251 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB)

This section describes how to activate, verify, and deactivate the optional feature MRFD-221501 IP-Based Multi-Mode Co-Transmission on Base Station Side. 7.251.1 Configuring IP-Based GSM and UMTS Co-Transmission on Base Station Side This section describes how to activate, verify, and deactivate the optional feature IP-Based GSM and UMTS Co-Transmission on Base Station Side. 7.251.2 Configuring IP-Based UMTS and LTE Co-Transmission on Base Station Side This section describes how to activate, verify, and deactivate the optional feature IP-Based UMTS and LTE Co-Transmission on Base Station Side.
7.251.1 Configuring IP-Based GSM and UMTS Co-Transmission on Base Station Side
This section describes how to activate, verify, and deactivate the optional feature IP-Based GSM and UMTS Co-Transmission on Base Station Side.
Prerequisite
Procedure
Step 1 Procedure for Activating the NodeB Data 1. Check whether the UTRP board is correctly configured, provided that the NodeB connects to the transport network through the UTRP board. a. Run the NodeB MML command DSP BRD to check whether the UTRP board is configured. If the UTRP board is not configured, run the NodeB MML command ADD BRD to add the UTRP board. Run the NodeB MML command LST SUBBRD to check whether the sub-board of the UTRP board is correctly configured. In the FE/GE co-transmission mode, the subboard is UEOC or UQEC. In the E1/T1 co-transmission mode, the sub-board is UAEC or UPEC. If the sub-board is not configured, run the NodeB MML command SET SUBBRD to add the sub-board.
b.
7-452
2.
Run the NodeB MML command SET ETHPORT to set the attributes of the port (This operation is performed when the planned data is inconsistent with the default data in the database). To view the default configuration, run the NodeB MML command LST ETHPORT. Run the NodeB MML command ADD DEVIP to add IP Address to the IP address of the FE interconnection port on the NodeB side. Run the NodeB MML command ADD MPGRP to add an MP group (This operation is performed when E1/T1 transmission is used on the base station side). Add an MP link to the MP group in E1/T1 co-transmission mode on the base station side. To do so, run the NodeB MML command ADD MPGRP.
NOTE
3. 4. 5.
l When the base station uses the E1/T1 transmission mode, the upper-layer link can be configured as a PPPLNK or in an MP group. The MP group is recommended because it provides greater bandwidth than the PPPLNK group. l A maximum of eight MP links can be configured for the UTRP board, and a maximum of four MP links are configured for the WMPT board. If the transmission requirement is not met, another WMPT or UTRP board can be added.
6.
Run the NodeB MML command ADD IPRT to add the route from the NodeB to BSC6900. In this step, set Destination IP address to the gateway IP address of the BSC6900 and Next Hop IP Address to the gateway IP address of the NodeB. This operation is performed in layer 3 networking when the IP address of the NodeB and that of the BSC6900 are not on the same network segment. Run the NodeB MML command ADD SCTPLNK to add an SCTP link. In this step, set Cabinet No., Subrack No., and Slot No. to the number of the cabinet, subrack, and slot where the Iub interface board is installed, set Local IP Address to the device IP address set in step 1.3, set Peer IP Address to the port IP address on the BSC6900 side, view Peer SCTP Port to the port number that is queried by running the BSC6900 MML command LST SCTPSRVPORT. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set NCP/ CCP Port Type to CCP. Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set NCP/ CCP Port Type to NCP.
NOTE
7.
8. 9.
CCP Port No. must be set to the same value as that on the BSC6900 side. You can query the information about the CCP link on the BSC6900 side by running the BSC6900 MML command LST UIUBCP.
10. Run the NodeB MML command ADD IPPATH to add the path to the adjacent node. In this step, set Cabinet No., Subrack No., and Slot No. to the number of the cabinet, subrack, and slot where the Iub interface board is installed. The Rx Bandwidth and Tx Bandwidth must be the same as the Rx Bandwidth and Tx Bandwidth of the IP path connected to the BSC6900. 11. Run the NodeB MML command SET DHCPRELAYSWITCH to enable the DHCP relay function of the base station. In this step, set Enable Switch to ENABLE. 12. Run the NodeB MML command ADD DHCPSVRIP to set the IP address of the DHCP server. In this step, set DHCP Server IP Address to that of the BSC6900. Step 2 Procedure for Activating the BTS Data 1. Run the BSC6900 MML command ADD BTSESN to add an equipment serial number (ESN) of the BTS. In this step, set BTS Index Type and BTS Interface Board Bar Code 1.
Issue 03 (2010-09-20)
2.
Run the BSC6900 MML command SET BTSIP to set BTS IP. In this step, set BTS IP and BSC IP. We recommend setting BTS Communication Type to LOGICIP(Logic IP) and Carry Flag to IPLGCPORT(IP Logic Port). Run the BSC6900 MML command ADD BTSDEVIP to set the IP address of the FE interconnection port on the BTS side. In this step, set Physical IP to the IP address of the FE interconnection port on the BTS side. Run the BSC6900 MML command ADD BTSIPRT to add an IP route from the BTS to the BSC6900. In this step, set Destination IP Address to the gateway IP address of the BSC6900. Set Route Type to NEXTHOP(Next Hop) and then set Forward Route Address to the IP address of the port that is connected to the transport network on the BTS side.
NOTE
3.
4.
l The IP-based co-transmission is implemented by FE interconnection on the panel on the base station side. That is, the FE port on the GTMU of the BTS is interconnected with the FE port on the WMPT of the NodeB on the panel, and then the NodeB is connected to the transport network by its port. l The NodeB is connected to the transport network through the WMPT or UTRP board.
5.
Run the BSC6900 MML command ADD IPRT to add an IP route from the BSC6900 to the BTS. In this step, set Destination IP Address to the gateway IP address of the FE interconnection port on the BTS side. Set Forward Route Address to the IP address of the port that is connected to the transport network on the NodeB side.
----End
Example
// To configure the NodeB data, do as follows: // To add the IP address of the FE interconnection port on the NodeB side, do as follows: ADD DEVIP: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="199.2.2.2", MASK="255.255.255.0"; // To add an SCTP signaling link, do as follows: ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=7, LOCIP="199.2.2.2", LOCPORT=1024, PEERIP="17.0.0.17", PEERPORT=58080; ADD SCTPLNK: SCTPNO=1, CN=0, SRN=0, SN=7, LOCIP="199.2.2.2", LOCPORT=1025, PEERIP="17.0.0.17", PEERPORT=58080; // To add an NCP link, do as follows: ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=0; // To add a UCP link, do as follows: ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=1; // To add an IP path to the adjacent node, do as follows: ADD IPPATH: PATHID=0, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="199.2.2.2", RNCIP="17.0.0.17", DSCP=0, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="199.2.2.2", RNCIP="17.0.0.17", DSCP=0, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; // To enable the DHCP relay function of the BTS, do as follows: SET DHCPRELAYSWITCH: EnableSwitch=ENABLE; ADD DHCPSVRIP: DHCPSVRIP="17.0.0.17"; // To configure the BTS data, do as follows: // To add the ESN of the BTS, do as follows: ADD BTSESN:BTSID=2000, IDTYPE=BYID, MAINDEVTAB="020GKV1083000212"; // To set the BTS IP address, do as follows: SET BTSIP:BTSID=2000, IDTYPE=BYID, BSCIP="17.0.0.17", BTSIP="199.2.2.1", BTSCOMTYPE=PORTIP, HOSTTYPE=SINGLEHOST, CFGFLAG=NULL;
7-454
Issue 03 (2010-09-20)
// To set the IP address of the FE interconnection port on the BTS side, do as follows: ADD BTSDEVIP:PN=0, BTSID=2000, IDTYPE=BYID, CN=0, SRN=0, SN=6, IP="199.2.2.1", MASK="255.255.255.0", AUTONEG=DISABLED, RATE=100M, DUPLEX=FULL, MTU=1500, FC=CLOSE; // To add an IP route from the BTS to the BSC6900, do as follows: ADD BTSIPRT:RTIDX=0, BTSID=2000, IDTYPE=BYID, PRI=60, DSTIP="17.0.0.0", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="199.2.2.2"; // To add an IP route from the BSC6900 to the BTS, do as follows: (If the IP route has been added, skip this step.) ADD IPRT:DSTIP="199.2.2.0", DSTMASK="255.255.255.0", NEXTHOP="17.0.0.13", SRN=0, SN=17, REMARK="0", PRIORITY=HIGH;
7.251.2 Configuring IP-Based UMTS and LTE Co-Transmission on Base Station Side
This section describes how to activate, verify, and deactivate the optional feature IP-Based UMTS and LTE Co-Transmission on Base Station Side.
Prerequisite
l Dependency on Hardware A UMTS and LTE dual-mode base station whose UMTS and LTE modes share the BBU supports this feature. A UTRP needs to be added at the eNodeB to support IP over E1/T1. l Dependency on Other Features WRFD-050402 IP Transmission Introduction on Iub Interface MRFD-221601 Multi-Mode BS Common Reference Clock (NodeB) l License The license is activated.
Context
The feature IP-Based UMTS and LTE Co-Transmission on Base Station Side requires a UMTS and LTE dual-mode base station to connect the FE port on the WMPT and one FE port on the LMPT together and to share transmission ports on the LTE side and the transmission network, therefore sharing transmission resources.
NOTE
In the scenario of UMTS and LTE co-transmission, transmission resource sharing can be achieved by connecting FE, GE, or E1/T1 ports together. Connecting FE ports, however, is recommended.
Co-transmission modes can be IP over FE/GE and IP over E1/T1, as shown in Figure 7-108 and Figure 7-109 respectively.
Issue 03 (2010-09-20)
7-455
Figure 7-108 IP-over-FE/GE UMTS and LTE co-transmission on base station side
Figure 7-109 IP-over-E1/T1 UMTS and LTE co-transmission on base station side
Procedure
l Activating the NodeB data 1. 2. 3. If the planned data is inconsistent with the default data in the database, run the NodeB MML command SET ETHPORT to set parameters for an Ethernet port. Run the NodeB MML command ADD DEVIP to add a device IP address. In this step, set IP Address to the IP address of FE interconnection port on the NodeB side. Run the NodeB MML command ADD IPRT to add an IP route from the NodeB to BSC6900 in case of layer 3 networking. Set Destination IP Address to the gateway IP address of the BSC6900. Set Next Hop IP Address to the gateway IP address of the NodeB.
NOTE
Next Hop IP Address is the IP address of the eNodeB port connected to the NodeB.
4.
Run the NodeB MML command ADD SCTPLNK to add an SCTP 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 Local IP Address to the device IP address in step 2. Set Peer IP Address to the IP address of the port on the BSC6900 side.
7-456
Issue 03 (2010-09-20)
Run the BSC6900 MML command LST SCTPSRVPORT to query the value of Peer SCTP Port. 5. 6. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set NCP/CCP Port Type to CCP(CCP Port). Run the NodeB MML command ADD IUBCP to add a NCP link. In this step, set NCP/CCP Port Type to NCP(NCP Port).
NOTE
Before a CCP link is added, the value of CCP Port Number must be the same as that on the BSC6900 side. You can query information about the CCP link on the BSC6900 side by running the BSC6900 MML command LST UIUBCP.
7.
Run the NodeB MML command ADD IPPATH to add an IP path to the adjacent node. Set Cabinet No., Subrack No., and Slot No. to the numbers of the cabinet, subrack, and slot that house the Iub interface board. The value of Rx Bandwidth must be the same as that of Tx Bandwidth of the IP path on the BSC6900 side. The value of Tx Bandwidth must be the same as that of Rx Bandwidth of the IP path on the BSC6900 side.
8. 9.
Run the NodeB MML command SET DHCPRELAYSWITCH to enable the DHCP relay function of the base station. In this step, set Enable Switch to ENABLE. Run the NodeB MML command ADD DHCPSVRIP to add an IP address for a DHCP server. In this step, set DHCP Server IP Address to the IP address of the BSC6900 DHCP Server. This DHCP server is shared between the NodeB and the BSC6900. Run the eNodeB MML command SET ETHPORT to set parameters for the LMPT port connected to the WMPT.
NOTE
Activating the eNodeB data (IP over FE/GE) 1.
When the WMPT is connected to the LMPT, the LMPT must be configured to work in 100M/ FULL mode.
2.
Run the eNodeB MML command ADD DEVIP to add an IP address for the main control board on the eNodeB side and an IP address for the S1 interface on the CN side. Set IP Address to the IP address of the S1 interface on the eNodeB side. In this step, set Port Type to ETH(Ethernet Port). Set Port No. based on the actual situation.
3.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the MME. Set Destination IP Address to the destination IP address of the route. Set Route Type to NEXTHOP(IP Address of The Next Hop). Next Hop IP Address must be on the same network segment as the IP address of the eNodeB.
4. 5.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the SGW. Run the eNodeB MML command ADD IPLGCPORT to add an IP logical port. In this step, set Port Type to ETH(Ethernet Port).
Issue 03 (2010-09-20)
6.
Run the eNodeB MML command ADD IPPATH to add an IP path between the eNodeB and the SGW. Set Join Logical Port to YES. Set PATH Type to ANY.
7. 8. l 1.
Run the eNodeB MML command ADD SCTPLNK to add a signaling link between the eNodeB and the MME. Run the eNodeB MML command ADD S1INTERFACE to add an S1 interface. Run the eNodeB MML command SET ETHPORT to set parameters for the LMPT port connected to the WMPT.
NOTE
Activating the eNodeB data (IP over E1/T1)
When the WMPT is connected to the LMPT, the LMPT must be configured to work in 100M/ FULL mode.
2. 3. 4.
Run the eNodeB MML command ADD MPGRP to add an MP group. Run the eNodeB MML command ADD MPLNK to add an MP link and then add it to the MP group. Run the eNodeB MML command ADD DEVIP to add an IP address for the main control board on the eNodeB side and an IP address for the S1 interface on the CN side. Set IP Address to the IP address of the S1 interface on the eNodeB side. In this step, set Port Type to MP(Multi-link PPP Group). Set Port No. based on the actual situation.
5.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the MME. Set Destination IP Address to the destination IP address of the route. Set Route Type to NEXTHOP(IP Address of The Next Hop). Next Hop IP Address must be on the same network segment as the IP address of the eNodeB.
6. 7. 8.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the SGW. Run the eNodeB MML command ADD IPLGCPORT to add an IP logical port. In this step, set Port Type to MP(Multi-link PPP Group). Run the eNodeB MML command ADD IPPATH to add an IP path between the eNodeB and the SGW. Set Join Logical Port to YES. Set PATH Type to ANY.
9.
Run the eNodeB MML command ADD SCTPLNK to add a signaling link between the eNodeB and the MME.
10. Run the eNodeB MML command ADD S1INTERFACE to add an S1 interface. ----End
Example
//Activating the NodeB data //Setting parameters for an Ethernet port
7-458
Issue 03 (2010-09-20)
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=DISABLE, OAM3AHSW=DISABLE; //Adding an IP address for the FE interconnection port on the NodeB side ADD DEVIP: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="199.2.2.2", MASK="255.255.255.0"; //Adding an IP route from the NodeB to the RNC ADD IPRT:CN=0,SRN=0,SN=7,DSTIP="17.0.0.17",MASK="255.255.255.0",RTTYPE=NEXTHO P,NEXTHOPIP="199.2.2.3",PREF=80; //Adding an SCTP signaling link ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=7, LOCIP="199.2.2.2", LOCPORT=1024, PEERIP="17.0.0.17", PEERPORT=58080; ADD SCTPLNK: SCTPNO=1, CN=0, SRN=0, SN=7, LOCIP="199.2.2.2", LOCPORT=1025, PEERIP="17.0.0.17", PEERPORT=58080; //Adding a NCP link ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=0; //Adding a CCP link ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=1; //Adding an IP path to the adjacent node ADD IPPATH: PATHID=0, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="199.2.2.2", RNCIP="17.0.0.17", DSCP=0, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="199.2.2.2", RNCIP="17.0.0.17", DSCP=0, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; //Enabling the DHCP relay function of the base station SET DHCPRELAYSWITCH: EnableSwitch=ENABLE; ADD DHCPSVRIP: DHCPSVRIP="17.0.0.17"; //Activating the eNodeB data (IP over FE/GE) //Setting parameters for the LMPT port connected to the WMPT SET ETHPORT: CN=0, SRN=0, SN=6, PN=0, PA=COPPER, MTU=1500, SPEED=100M, DUPLEX=FULL, FC=OPEN; //Adding an IP address for the eNodeB ADD DEVIP: CN=0, SRN=0, SN=6, PT=ETH, PN=1, IP="70.83.26.1", MASK="255.0.0.0"; //Adding an IP route from the eNodeB to the MME ADD IPRT:CN=0,SRN=0,SN=6,DSTIP="138.20.5.0",MASK="255.255.255.0",RTTYPE=NEXTH OP,NEXTHOPIP="70.20.3.51",PREF=80; //Adding an IP route from the eNodeB to the SGW ADD IPRT:CN=0,SRN=0,SN=6,DSTIP="138.30.20.0",MASK="255.255.255.0",RTTYPE=NEXT HOP,NEXTHOPIP="70.20.6.55",PREF=80; //Adding an IP logical port ADD IPLGCPORT: CN=0, SRN=0, SN=6, LPT=USERDEF, LPN=0, PT=ETH, PN=0, TXBW=150000, RXBW=200000, TXCBS=200000, TXEBS=200000; //Adding an IP path between the eNodeB and the SGW ADD IPPATH: PATHID=0, SN=6, JNLGCPORT=YES, LPN=0, LOCALIP="70.83.26.1", PEERIP="138.20.5.20", QT=HQ, PATHTYPE=ANY; //Adding a signaling link between the eNodeB and the MME ADD SCTPLNK: SCTPNO=0, SN=6, LOCIP="70.83.26.1", LOCPORT=2907, PEERIP="138.30.20.60", PEERPORT=2910, SWITCHBACKFLAG=YES; //Adding an S1 interface ADD S1INTERFACE: S1INTERFACEID=0, S1SCTPLINKID=0, CnOperatorId=0; //Activating the eNodeB data (IP over E1/T1) //Setting parameters for the LMPT port connected to the WMPT SET ETHPORT: CN=0, SRN=0, SN=6, PN=0, PA=COPPER, MTU=1500, SPEED=100M, DUPLEX=FULL, FC=OPEN; //Adding an MP group ADD MPGRP: CN=0, SRN=0, SN=6, MPGRPN=0, MCPPP=DISABLE, AUTHTYPE=NOAUTH,
Issue 03 (2010-09-20)
7-459
LOCALIP="70.83.26.1", MASK="255.0.0.0", PPPMUX=DISABLE; //Adding an MP link and then adding it to the MP group ADD MPLNK: CN=0, SRN=0, SN=6, PPPLNKN=0, E1T1SN=0, E1T1PN=0, TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS1 1-1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1 &TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1; //Adding an IP address for the eNodeB ADD DEVIP: CN=0, SRN=0, SN=6, PT=MP, PN=1, IP="70.83.26.1", MASK="255.0.0.0"; //Adding an IP route from the eNodeB to the MME ADD IPRT: CN=0,SRN=0,SN=6,DSTIP="138.20.5.0",MASK="255.255.255.0",RTTYPE=NEXTHOP,NE XTHOPIP="70.20.3.51",PREF=80; //Adding an IP route from the eNodeB to the SGW ADD IPRT: CN=0,SRN=0,SN=6,DSTIP="138.30.20.0",MASK="255.255.255.0",RTTYPE=NEXTHOP,N EXTHOPIP="70.20.6.55",PREF=80; //Adding an IP logical port ADD IPLGCPORT: CN=0, SRN=0, SN=6, LPT=USERDEF, LPN=0, PT=ETH, PN=0, TXBW=150000, RXBW=200000, TXCBS=200000, TXEBS=200000; //Adding an IP path between the eNodeB and the SGW ADD IPPATH: PATHID=0, SN=6, JNLGCPORT=YES, LPN=0, LOCALIP="70.83.26.1", PEERIP="138.20.5.20", QT=HQ, PATHTYPE=ANY; //Adding a signaling link between the eNodeB and the MME ADD SCTPLNK: SCTPNO=0, SN=6, LOCIP="70.83.26.1", LOCPORT=2907, PEERIP="138.30.20.60", PEERPORT=2910, SWITCHBACKFLAG=YES; //Adding an S1 interface ADD S1INTERFACE: S1INTERFACEID=0, S1SCTPLINKID=0, CnOperatorId=0;
7.252 Configuring TDM-Based Multi-mode CoTransmission via Backplane on BS side(NodeB)

This section describes how to activate, verify, and deactivate the optional feature MRFD-221504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side(NodeB).
Prerequisite
l Dependency on Hardware A GSM and UMTS dual-mode base station supports this feature. When the TDM timeslot cross connection co-transmission feature is suppported 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. l Dependency on Other Features WRFD-050302 Fractional ATM Function on Iub Interface or WRFD-050411 Fractional IP Function on Iub Interface l License The license is activated.
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:
In the scenario of GTMU-based TDM timeslot cross connection co-transmission, E1/T1 timeslots on the UMTS side are transmistted 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 7-110. Figure 7-110 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 7-111.
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 7-111 GSM-UTRP-based TDM timeslot cross connection co-transmission
Issue 03 (2010-09-20)
7-461
Procedure
l Activating the BTS data (GTMU-based) 1. 2. Run the BSC6900 MML command ADD BTSCONNECT to add a connection between a GTMU port and the NodeB. Set Dest Node Type to OTHER. 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 a 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. 3.
Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step, set Subboard Type to BASE_BOARD. 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. 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.
4.
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). 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.
7-462
Issue 03 (2010-09-20)
7. 8.
Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set NCP/CCP Port Type to NCP(NCP Port). Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set NCP/CCP Port Type to CCP(CCP Port).
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. 2. Run the BSC6900 MML command ADD BTSCONNECT to add a connection between a UTRP port and the NodeB. Set Dest Node Type to OTHER. 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. 3.
Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step, set Subboard Type to BASE_BOARD. 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. 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.
4.
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 03 (2010-09-20)
7-463
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. 7. 8. Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set NCP/CCP Port Type to NCP. 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; ADD SAALLNK: SAALNO=5, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA, JNRSCGRP=DISABLE, VPI=1, VCI=33, RU=KBPS, ST=CBR, PCR=256; ADD SAALLNK: SAALNO=6, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA, JNRSCGRP=DISABLE, VPI=2, VCI=34, RU=KBPS, ST=CBR, PCR=256; //Adding an AAL2 node ADD AAL2NODE: NT=LOCAL, LN=4, ADDR="H'3900000000000000000000000000000000001980"; //Adding an AAL2 path 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 a NCPor 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;
7-464
Issue 03 (2010-09-20)
//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 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 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; ADD SAALLNK: SAALNO=5, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA, JNRSCGRP=DISABLE, VPI=1, VCI=33, RU=KBPS, ST=CBR, PCR=256; ADD SAALLNK: SAALNO=6, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA, JNRSCGRP=DISABLE, VPI=2, VCI=34, RU=KBPS, ST=CBR, PCR=256; //Adding an AAL2 node ADD AAL2NODE: NT=LOCAL, LN=4, ADDR="H'3900000000000000000000000000000000001980"; //Adding an AAL2 path 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 a NCPor CCP link ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5; ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6;
7.253 Configuring Multi-Mode BS Common Reference Clock (NodeB)

This section describes how to activate, verify, and deactivate the basic feature MRFD-221601 Multi-Mode BS Common Reference Clock (NodeB). 7.253.1 Configuring GSM and UMTS Common Reference Clock This section describes how to activate, verify, and deactivate the feature GSM and UMTS Common Reference Clock. 7.253.2 Configuring UMTS and LTE Common Reference Clock This section describes how to activate, verify, and deactivate the feature UMTS and LTE Common Reference Clock.
7.253.1 Configuring GSM and UMTS Common Reference Clock

This section describes how to activate, verify, and deactivate the feature GSM and UMTS Common Reference Clock.
Issue 03 (2010-09-20)
7-465
Prerequisite
l Dependency on Hardware A GSM and UMTS dual-mode base station whose GSM and UMTS modes share the BBU supports this feature. If Global Positioning System (GPS) or Building Integrated Timing Supply System (BITS) clock signals are shared, the USCU must be configured on the BBU. l Dependency on Other Features GBFD-510401 BTS GPS Synchronization GBFD-118202 Synchronous Ethernet WRFD-050502 Synchronous Ethernet l License The license is activated.
Context
The feature GSM and UMTS common reference clock enables the GSM and UMTS modes to share the same clock source. Therefore, an external clock source must be configured for one mode while the other mode is configured to share the opposite mode's clock source. Scenarios of this feature are as follows: l Common GPS reference clock Common GPS reference clock on the GSM side (GSM USCU) Common GPS reference clock on the UMTS side (UMTS USCU) l Common BITS reference clock Common BITS reference clock on the GSM side (GSM USCU) Common BITS reference clock on the UMTS side (UMTS USCU) l Common E1/T1 reference clock Common E1/T1 reference clock on the GSM side (GTMU) Common E1/T1 reference clock on the UMTS side (WMPT) Common E1/T1 reference clock on the UMTS side (UMTS UTRP) (non-typical scenario) l Common Ethernet reference clock Common Ethernet reference clock on the UMTS side (WMPT) Common Ethernet reference clock on the GSM side (GTMU) (non-typical scenario) Common E1/T1 reference clock on the UMTS side (UMTS UTRP) (non-typical scenario) l Common IP reference clock Common IP reference clock on the UMTS side (WMPT) Common IP reference clock on the GSM side (GTMU) (non-typical scenario) Common IP reference clock on the UMTS side (UMTS UTRP) (non-typical scenario)
NOTE
For non-typical scenarios, further descriptions are not provided.
Common GPS reference clock

When a USCU and an external GPS clock are configured for a GSM and UMTS dual-mode base station, GPS clock signals are transmitted through a GPS clock interface. The GSM and UMTS modes obtain the GPS clock signals through a backplane clock channel, as shown in Figure 7-112. Figure 7-112 Common GPS reference clock
NOTE
As shown in Figure 7-112, only one USCU can be configured on either the GSM side or the UMTS side.
Common BITS reference clock When a USCU and an external BITS clock are configured for a GSM and UMTS dual-mode base station, BITS clock signals are transmitted through a BITS clock interface. The GSM and UMTS modes obtain the BITS clock signals through a backplane clock channel, as shown in Figure 7-113. Figure 7-113 Common BITS reference clock
NOTE
As shown in Figure 7-113, only one USCU can be configured on either the GSM side or the UMTS side.
Issue 03 (2010-09-20)
7-467
Common E1/T1 reference clock When a common E1/T1 reference clock is used on a GSM and UMTS dual-mode base station, clock signals can be obtained from the E1/T1 port on the side of one mode while the other mode is configured to share the opposite mode's clock source. Followings are examples of common E1/T1 reference clock on the GSM side (GTMU) and common E1/T1 reference clock on the UMTS side (WMPT), as shown in Figure 7-114 and Figure 7-115. Figure 7-114 Common E1/T1 reference clock on the GSM side (GTMU)
Figure 7-115 Common E1/T1 reference clock on the UMTS side (WMPT)
Common Ethernet reference clock When a common Ethernet reference clock is used on a GSM and UMTS dual-mode base station, one mode obtains Ethernet clock signals from the transmission network through a FE transmission link while the other mode is configured to share the opposite mode's clock source. Following is an example of common Ethernet reference clock on the UMTS side (WMPT), as shown in Figure 7-116. Figure 7-116 Common Ethernet reference clock on the UMTS side (WMPT)
7-468
Issue 03 (2010-09-20)
Common IP reference clock When the IEEE1588 clock is used on a GSM and UMTS dual-mode base station, the common IP reference clock is shared by two modes. Only one mode needs to be configured with an IEEE1588 client, and then clock signals can be obtained from the IEEE1588 server by connecting a FE transmission link to the transmission network. The other mode should be configured to share the opposite mode's clock source. Following is an example of common IP reference clock on the UMTS side (WMPT), as shown in Figure 7-117. Figure 7-117 Common IP reference clock on the UMTS side (WMPT)
Procedure
l Common GPS reference clock 1. Configuration on the GBTS side (1) Run the BSC6900 MML command SET BTSUSCUBP. Set GPS or Glonass to GPS(GPS). Set Antenna Power Supply Switch to NOPOWER(No Power). Set GPS Antenna Delay based on the actual situation. (2) Run the BSC6900 MML command SET BTSCLK to set Clock Type to TRCGPS_CLK. (3) Run the BSC6900 MML command SET BTSCLKPARA to set BTS clock parameters based on the actual situation. 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to configure the USCUGPS clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to USCUGPS(USCUGPS clock source). l Common BITS reference clock 1.
Issue 03 (2010-09-20)
Configuration on the GBTS side

(1) Run the BSC6900 MML command SET BTSCLK to set an external clock source. In this step, set Clock Type to EXCLK. 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to configure the BITS clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to BITS(BITS clock source). l Common E1/T1 reference clock on the GSM side (GTMU) 1. Configuration on the GBTS side Run the BSC6900 MML command SET BTSCLK to set the BTS to track the clock signals received from the BSC. In this step, set Clock Type to TRCBSC_CLK. 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to configure the PEER clock source.
NOTE
Before configuring on the NodeB side, ensure that the clock source on the GBTS side is E1/ T1 clock.
Common E1/T1 reference clock on the UMTS side (WMPT) 1. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to configure the LINE clock source.
NOTE
Before configuring the LINE clock source, ensure that an E1/T1 clock link is available.
2.
Configuration on the GBTS side Run the BSC6900 MML command SET BTSCLK to configure the PEER clock source. In this step, set Clock Type to PEER(PEER Clock).
Common Ethernet reference clock on the UMTS side (WMPT) 1. Configuration on the NodeB side (1) Run the NodeB MML command ADD LNKSRC to configure the Ethernet clock source. In this step, set Port Type to ETH. (2) Run the NodeB MML command SET CLKMODE to set Clock Source Type to LINE(LINE clock source). 2. Configuration on the GBTS side Run the BSC6900 MML command SET BTSCLK to configure the PEER clock source. In this step, set Clock Type to PEER(PEER Clock).
Common IP reference clock on the UMTS side (WMPT) 1. Configuration on the NodeB side (1) Run the NodeB MML command SET CLKMODE to set Clock Source Type to IPCLK(IP clock source). 2. Configuring on the GBTS side
7-470
Run the BSC6900 MML command SET BTSCLK to configure the PEER clock source. In this step, set Clock Type to PEER_CLK(Peer Clock). l Verification Procedure 1. Run the NodeB MML command LST CLKMODE and the BSC6900 MML command LST BTSCLK. Then, check the returned packets. If... The clock source information matches the configuration. The clock source information mismatch the configuration. 2. Check whether any alarm is generated. If... The clock conflict alarm is generated. Then... The configurations on the GSM and UMTS sides conflict with each other. Therefore, the configuration fails. Then... The configuration succeeds. The configuration fails.
----End
Example
//Common GPS reference clock //Configuring the GPS clock source on the GBTS side SET BTSUSCUBP: IDTYPE=BYID, BTSID=120, CN=0, SRN=0, SN=2, CFGFLAG=YES, GPSORGLONASS=GPS, ANTENNALONG=0, ANTENNAPOWERSWITCH=NOPOWER; SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=TRCGPS_CLK; SET BTSCLKPARA: IDTYPE=BYID, BTSID=120, CN=0, SRN=0, SN=2, CLKMOD=GPSCLK, TRCRNGLMT=ENABLE, CALVAL=2222; //Configuring the USCUGPS clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=USCUGPS; //Common BITS reference clock //Configuring the external clock source on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=EXTSYN_CLK; //Configuring the BITS clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Common E1/T1 reference clock on the GSM side (GTMU) //Setting the BTS to track the clock signals received from the BSC on the GBTS side on BTS 120 SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=TRCBSC_CLK; //Configuring the PEER clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=PEER; //Common E1/T1 reference clock on the UMTS side (WMPT) //Configuring the LINE clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=LINE; //Configuring the PEER clock source on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=PEER_CLK; //Common Ethernet reference clock on the UMTS side (WMPT) //Configuring the Ethernet clock source on the NodeB side ADD LNKSRC: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH; SET CLKMODE: MODE=MANUAL, CLKSRC=LINE;
Issue 03 (2010-09-20)
7-471

//Configuring the PEER clock source on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=PEER_CLK; //Common IP reference clock on the UMTS side (WMPT) //Configuring the IP clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK; //Configuring the PEER clock source on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=PEER_CLK;
7.253.2 Configuring UMTS and LTE Common Reference Clock

This section describes how to activate, verify, and deactivate the feature UMTS and LTE Common Reference Clock.
Prerequisite
l Dependency on Hardware A UMTS and LTE dual-mode base station whose UMTS and LTE modes share the BBU supports this feature. If Global Positioning System (GPS) or Building Integrated Timing Supply System (BITS) clock signals are shared, the USCU must be configured on the BBU. l Dependency on Other Features WRFD-050502 Synchronous Ethernet LOFD-00301301 Synchronization with Ethernet(ITU-T G.8261) LOFD-00301302 IEEE1588 V2 Clock Synchroniztion LOFD-003020 UMTS and LTE Common Reference Clock l License The license is activated.
Context
The feature UMTS and LTE common reference clock enables the UMTS and LTE modes to share the same clock source. Therefore, an external clock source must be configured for one mode while the other mode is configured to share the opposite mode's clock source. Scenarios of this feature are as follows: l Common GPS reference clock Common GPS reference clock on the UMTS side (UMTS USCU) Common GPS reference clock on the LTE side (LTE USCU) l Common BITS reference clock Common BITS reference clock on the UMTS side (UMTS USCU) Common BITS reference clock on the LTE side (LTE USCU) l Common E1/T1 reference clock Common E1/T1 reference clock on the UMTS side (WMPT) Common E1/T1 reference clock on the UMTS side (UMTS UTRP) (non-typical scenario) Common E1/T1 reference clock on the LTE side (LTE UTRP) (non-typical scenario) l
7-472
Common Ethernet reference clock

Common Ethernet reference clock on the LTE side (LMPT) Common Ethernet reference clock on the UMTS side (WMPT) (non-typical scenario) Common Ethernet reference clock on the UMTS side (UMTS UTRP) (non-typical scenario) Common Ethernet reference clock on the LTE side (LTE UTRP) (non-typical scenario) l Common IP reference clock Common IP reference clock on the LTE side (LMPT) Common IP reference clock on the UMTS side (WMPT) (non-typical scenario) Common IP reference clock on the UMTS side (UMTS UTRP) (non-typical scenario) Common IP reference clock on the LTE side (LTE UTRP) (non-typical scenario)
NOTE
For non-typical scenarios, further descriptions are not provided.
Common GPS reference clock When a USCU and an external GPS clock are configured for a UMTS and LTE dual-mode base station, GPS clock signals are transmitted through a GPS clock interface. The UMTS and LTE modes obtain the GPS clock signals through a backplane clock channel, as shown in Figure 7-118. Figure 7-118 Common GPS reference clock
NOTE
As shown in Figure 7-118, only one USCU can be configured on either the UMTS side or the LTE side.
Common BITS reference clock When a USCU and an external BITS clock are configured for a UMTS and LTE dual-mode base station, BITS clock signals are transmitted through a BITS clock interface. The UMTS and LTE modes obtain the BITS clock signals through a backplane clock channel, as shown in Figure 7-119.
Figure 7-119 Common BITS reference clock
NOTE
As shown in Figure 7-119, only one USCU can be configured on either the UMTS side or the LTE side.
Common E1/T1 reference clock When a common E1/T1 reference clock is used on a UMTS and LTE dual-mode base station, clock signals can be obtained from the E1/T1 port on the side of one mode while the other mode is configured to share the opposite mode's clock source. Following is an example of common E1/T1 reference clock on the UMTS side (WMPT), as shown in Figure 7-120. Figure 7-120 Common E1/T1 reference clock on the UMTS side (WMPT)
Common Ethernet reference clock When a common Ethernet reference clock is used on a UMTS and LTE dual-mode base station, one mode obtains Ethernet clock signals from the transmission network through a FE/GE transmission link while the other mode is configured to share the opposite mode's clock source. Following is an example of common Ethernet reference clock on the LTE side (LMPT), as shown in Figure 7-121.
7-474
Issue 03 (2010-09-20)
Figure 7-121 Common Ethernet reference clock on the LTE side (LMPT)
Common IP reference clock When the IEEE1588 clock is used on a UMTS and LTE dual-mode base station, the common IP reference clock is shared by two modes. Only one mode needs to be configured with an IEEE1588 client, and then clock signals can be obtained from the IEEE1588 server by connecting a FE/GE transmission link to the transmission network. The other mode should be configured to share the opposite mode's clock source. Following is an example of common IP reference clock on the LTE side (LMPT), as shown in Figure 7-122. Figure 7-122 Common IP reference clock on the LTE side (LMPT)
Procedure
l Common GPS reference clock 1. Configuration on the NodeB side (1) Run the NodeB MML command SET CLKMODE to configure the USCUGPS clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to USCUGPS(USCUGPS clock source). 2.
Issue 03 (2010-09-20)
Configuration on the eNodeB side

(1) Run the eNodeB MML command ADD GPS to add a GPS clock link. In this step, set Slot No. to the number of the slot that houses the USCU. (2) Run the eNodeB MML command SET CLKMODE.In this step, set the GPS clock source. Set System Clock Working Mode to MANUAL. Set Selected Clock Source to GPS(GPS). l Common BITS reference clock 1. Configuration on the NodeB side (1) Run the NodeB MML command SET CLKMODE to configure the BITS clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to BITS(BITS clock source). 2. Configuration on the eNodeB side (1) Run the eNodeB MML comand ADD BITS to add a BITS clock source. In this step, set Slot No. to the number of the slot that houses the USCU. (2) Run the eNodeB MML command SET CLKMODE.In this step, set the BITS clock source. Set System Clock Working Mode to MANUAL. Set Selected Clock Source to BITS(BITS). l Common E1/T1 reference clock on the UMTS side (WMPT) 1. Configuration on the NodeB side (1) Run the NodeB MML command ADD LNKSRC to a line clock source. In this step, set Port Type to E1T1. (2) Run the NodeB MML command SET CLKMODE to configure the LINE clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to LINE(LINE clock source).
NOTE
Before configuring the LINE clock source, ensure that an E1/T1 clock link is available.
2.
Configuration on the eNodeB side (1) Run the eNodeB MML command ADD PEERCLK to add a Peer clock source link. In this step, set PeerClk No. to the number of the peer reference clock. (2) Run the eNodeB MML command SET CLKMODE.In this step, set the PEER clock source. Set System Clock Working Mode to MANUAL. Set Selected Clock Source to PEERCLK(PeerClk).
NOTE
Before configuration, ensure that the clock source on the NodeB side is E1/T1 clock.
Common Ethernet reference clock on the LTE side (LMPT) 1. Configuration on the eNodeB side (1) Run the eNodeB MML command ADD SYNCETH command to add an Ethernet clock source.
7-476
Issue 03 (2010-09-20)
Set Subrack No. to the number of the subrack where the synchronousEthernet clock link is configured. The recommended value is 7. Set Port No. to the number of the port where the synchronous-Ethernet clock link is configured. (2) Run the eNodeB MML command SET CLKMODE. In this step, set the Ethernet clock source. Set System Clock Working Mode to MANUAL. Set Selected Clock Sourcee to SYNCETH(SyncEth). 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to configure the PEER clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to PEER(PEER clock source). l Common IP reference clock on the LTE side (LMPT) 1. Configuration on the eNodeB side (1) Run the eNodeB MML command ADD IPCLKLNK to add an IP clock link. Set Protocol Type to PTP(PTP). Set Slot No. to the number of the slot where the IP clock link is configured. Set Client IP to the client IP address of the IP clock link. Set Server IP to the server IP address of the IP clock link. (2) Run the eNodeB MML command SET CLKMODE.In this step, set the IP clock source. Set System Clock Working Mode to MANUAL. Set Selected Clock Source Type to IPCLK(IPClk). 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to configure the PEER clock source. Set System Clock Working Mode to MANUAL. Set Clock Source Type to PEER(PEER clock source). l Verification Procedure 1. Run the DSP CLKSTAT command on the NodeB and eNodeB sides and check the returned message. If... The clock source information matches the configuration. The clock source information mismatch the configuration. Then... The configuration succeeds. The configuration fails.
2.
Issue 03 (2010-09-20)
Check whether any alarm is generated.

If... The Inter-System BBU Board Parameter Settings Conflict (alarm ID: 26273) is generated.
Then... The configurations on the UMTS and LTE sides conflict with each other. Therefore, the configuration fails.
----End
Example
//Common GPS reference clock //Configuring the USCU GPS clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=USCUGPS; //Adding a USCU GPS clock source on the LTE side ADD GPS:SN=4; //Setting the USCU GPS clock source on the LTE side SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; //Common BITS reference clock //Configuring the BITS clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Adding a BITS clock source on the LTE side ADD BITS:SN=4; //Setting the BITS clock source on the LTE side SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; // Common UMTS E1/T1 reference clock //Configuring a LINE clock source on the NodeB side ADD LNKSRC: SRN=0, SN=7, SBT=BASE_BOARD, PT=E1T1; SET CLKMODE: MODE=MANUAL, CLKSRC=LINE; //Adding a PEER clock source on the LTE side ADD PEERCLK: PN=0; //Setting the PEER clock source on the LTE side: SET CLKMODE: MODE=MANUAL, CLKSRC=PEERCLK; //Common Ethernet reference clock on the LTE side (LMPT) //Adding an Ethernet clock source on the LTE side ADD SYNCETH: SN=6, PN=0; //Setting the Ethernet clock source on the LTE side SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH; //Setting the PEER clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=PEER; //Common IP reference clock on the LTE side (LMPT) //Adding an IP clock source on the LTE side ADD IPCLKLINK: TYPE=PTP, SN=7, NWTYPE=UNICAST, CIP="82.0.1.107", SIP="82.0.1.128"; //Setting the IP clock source on the LTE side SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK; //Setting the PEER clock source on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=PEER;
7-478
Issue 03 (2010-09-20)

RAN Re Configuration Guide (V900R012C01 - 03)

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

RAN Re Configuration Guide (V900R012C01 - 03)

Enviado por

Direitos autorais:

Formatos disponíveis

RAN V900R012C01

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.