RAN Feature Activation Guide (V900R013C00 - 02) (PDF) - en

RAN V900R013C00
Feature Activation Guide

Issue Date 02 2011-07-11
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. 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 02 (2011-07-11)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
RAN Feature Activation Guide
About This Document
About This Document

Purpose
This document provides guidelines for enabling or disabling a feature after initial configuration. Based on the activation, verification, and deactivation of a feature in the feature list, the guidelines aim to ensure that the feature is available on the network. This document describes how to activate a license and configure a feature in RAN.
NOTE
The BSC6900 is used as an example to describe the network controller in this document.
Product Version
The following table lists the product version related to this document. Product Name BSC6900 NodeB NodeB Product Version V900R013C00 V100R013 V200R013
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 Feature Activation Guide
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
About This Document
This chapter describes the changes in the RAN Feature Activation Guide. 2 Overview of Feature Activation Guide RAN features are classified into basic and optional features. Basic features are not licensecontrolled and therefore do not require license activation before use. Optional features are license-controlled and therefore require license activation before use. 3 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. 4 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. 5 Configuring Conversational QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010501 Conversational QoS Class. 6 Configuring Streaming QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010502 Streaming QoS Class. 7 Configuring Interactive QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010503 Interactive QoS Class. 8 Configuring Background QoS Class This section describes how to activate, verify, and deactivate the basic feature WRFD-010504 Background QoS Class. 9 Configuring Emergency Call This section describes how to activate, verify, and deactivate the basic feature WRFD-021104 Emergency Call. 10 Configuring 2-Way Antenna Receive Diversity This section describes how to activate, verify, and deactivate the basic feature MRFD-210604 2-Way Antenna Receive Diversity. 11 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. 12 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). 13 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
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). 14 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). 15 Configuring Dynamic Channel Configuration Control This section describes how to activate, verify, and deactivate the basic feature WRFD-021101 Dynamic Channel Configuration Control (DCCC). 16 Configuring Integrity Protection This section describes how to activate, verify, and deactivate the basic feature WRFD-011401 Integrity Protection. 17 Configuring Encryption This section describes how to activate, verify, and deactivate the basic feature WRFD-011402 Encryption. 18 Configuring Open Loop Power Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020501 Open Loop Power Control. 19 Configuring Downlink Power Balance This section describes how to activate, verify, and deactivate the basic feature WRFD-020502 Downlink Power Balance. 20 Configuring Outer Loop Power Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020503 Outer Loop Power Control. 21 Configuring Inner Loop Power Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020504 Inner Loop Power Control. 22 Configuring Admission Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020101 Admission Control. 23 Configuring Load Measurement This section describes how to activate, verify, and deactivate the basic feature WRFD-020102 Load Measurement. 24 Configuring Load Reshuffling This section describes how to activate, verify, and deactivate the basic feature WRFD-020106 Load Reshuffling. 25 Configuring Overload Control This section describes how to activate, verify, and deactivate the basic feature WRFD-020107 Overload Control.
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
About This Document
26 Configuring Code Resource Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020108 Code Resource Management. 27 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. 28 Configuring Intra NodeB Softer Handover This section describes how to activate, verify, and deactivate the basic feature WRFD-020201 Intra NodeB Softer Handover. 29 Configuring Intra RNC Soft Handover This section describes how to activate, verify, and deactivate the basic feature WRFD-020202 Intra RNC Soft Handover. 30 Configuring Inter RNC Soft Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-020203 Inter RNC Soft Handover. 31 Configuring Intra Frequency Hard Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-020301 Intra Frequency Hard Handover. 32 Configuring Intra RNC Cell Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010801 Intra RNC Cell Update. 33 Configuring Inter RNC Cell Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010802 Inter RNC Cell Update. 34 Configuring Intra RNC URA Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010901 Intra RNC URA Update. 35 Configuring Inter RNC URA Update This section describes how to activate, verify, and deactivate the basic feature WRFD-010902 Inter RNC URA Update. 36 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). 37 Configuring NodeB Clock This section describes how to activate, verify, and deactivate the basic feature MRFD-210501 NodeB Clock. 38 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface. 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. 40 Configuring Call Admission Based on Used AAL2 Path Bandwidth This section describes how to activate, verify, and deactivate the basic feature WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth. 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". 42 Configuring F5 This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110 F5. 43 Configuring UBR+ ATM QoS Class This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305 UBR+ ATM QoS Class". 44 Configuring Flow Control This section describes how to activate, verify, and deactivate the basic feature WRFD-040100 Flow Control. 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. 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. 47 Configuring License Control for Urgency This section describes how to activate, verify, and deactivate the basic feature WRFD-040300 License Control for Urgency. 48 Configuring Intelligently Out of Service This section describes how to activate, verify, and deactivate the basic feature WRFD-031000 Intelligently Out of Service. 49 Configuring OCNS This section describes how to activate, verify, and deactivate the basic feature WRFD-031200 OCNS (Orthogonal Channel Noise Simulator). 50 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.
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
About This Document
51 Configuring Solar Power Device Management This section describes how to activate, verify, and deactivate the basic feature WRFD-031500 Solar Power Device Management. 52 Configuring Connection with TMA (Tower Mounted Amplifier) This section describes how to activate, verify, and deactivate the basic feature MRFD-210601 Connection with TMA (Tower Mounted Amplifier). 53 Configuring Remote Electrical Tilt This section describes how to activate, verify, and deactivate the basic feature MRFD-210602 Remote Electrical Tilt. 54 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). 55 Configuring Multiple RAB Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010615 Multiple RAB Package (PS RAB 2). 56 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. 57 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. 58 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. 59 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. 60 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. 61 Configuring HSDPA Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010610 HSDPA Introduction Package. 62 Configuring 15 Codes per Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-01061001 15 Codes per Cell. 63 Configuring Time and HS-PDSCH Codes Multiplex
viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061018 Time and HS-PDSCH Codes Multiplex. 64 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). 65 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. 66 Configuring HSDPA Power Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061004 HSDPA Power Control. 67 Configuring HSDPA Admission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061003 HSDPA Admission Control. 68 Configuring HSDPA Flow Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061010 HSDPA Flow Control. 69 Configuring HSDPA Mobility Management This section describes how to activate, verify, and deactivate the optional feature WRFD-01061006 HSDPA Mobility Management. 70 Configuring HSDPA UE Category 1 to 28 This section describes how to activate, verify, and deactivate the optional feature WRFD-01061002 HSDPA UE Category 1 to 28. 71 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. 72 Configuring DL 16QAM Modulation This section describes how to activate, verify, and deactivate the optional feature WRFD-010629 16QAM Modulation. 73 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. 74 Configuring HSDPA Enhanced Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010611 HSDPA Enhanced Package. 75 Configuring Scheduling based on EPF and GBR
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061103 Scheduling based on EPF and GBR. 76 Configuring HSDPA State Transition This section describes how to activate, verify, and deactivate the optional feature WRFD-01061111 HSDPA State Transition. 77 Configuring HSDPA DRD This section describes how to activate, verify, and deactivate the optional feature WRFD-01061112 HSDPA DRD. 78 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. 79 Configuring HSDPA over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-010651 HSDPA over Iur. 80 Configuring SRB over HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010652 SRB over HSDPA. 81 Configuring CQI Adjustment Based on Dynamic BLER Target This section describes how to activate, verify, and deactivate the basic feature WRFD-030010 CQI Adjustment Based on Dynamic BLER Target. 82 Configuring HSUPA Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010612 HSUPA Introduction Package. 83 Configuring HSUPA Admission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061202 HSUPA Admission Control. 84 Configuring HSUPA Power Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061203 HSUPA Power Control. 85 Configuring HSUPA Mobility Management This section describes how to activate, verify, and deactivate the optional feature WRFD-01061204 HSUPA Mobility Management. 86 Configuring HSUPA DCCC This section describes how to activate, verify, and deactivate the optional feature WRFD-01061208 HSUPA DCCC. 87 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.
x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
88 Configuring E-AGCH Power Control (Based on CQI or HS-SCCH) This section describes how to activate, verify, and deactivate the optional feature WRFD-01061401 E-AGCH Power Control (Based on CQI or HS-SCCH). 89 Configuring HSUPA 2ms TTI This section describes how to activate, verify, and deactivate the optional feature WRFD-01061403 HSUPA 2ms TTI. 90 Configuring HSUPA 2 ms/10 ms TTI Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover. 91 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. 92 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. 93 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. 94 Configuring HSUPA over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-010635 HSUPA over Iur. 95 Configuring SRB over HSUPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010636 SRB over HSUPA. 96 Configuring HSUPA Adaptive Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-010641 HSUPA Adaptive Transmission. 97 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. 98 Configuring HSUPA Coverage Enhancement at UE Power Limitation This section describes how to activate, verify, and deactivate the optional feature WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation. 99 Configuring Adaptive Configuration of Traffic Channel Power This section describes how to activate, verify, and deactivate the optional feature WRFD-010712 Adaptive Configuration of Traffic Channel Power. 100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion. 101 Configuring Dynamic CE Resource Management This section describes how to activate, verify, and deactivate the optional feature WRFD-010638 Dynamic CE Resource Management. 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. 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. 104 Configuring Downlink Enhanced L2 This section describes how to activate, verify, and deactivate the optional feature WRFD-010685 Downlink Enhanced L2. 105 Configuring Downlink Enhanced CELL_FACH This section describes how to activate, verify, and deactivate the optional feature WRFD-010688 Downlink Enhanced CELL_FACH. 106 Configuring Uplink Enhanced CELL_FACH This section describes how to activate, verify, and deactivate the optional feature WRFD-010701 Uplink Enhanced CELL_FACH. 107 Configuring Enhanced DRX This section describes how to activate, verify, and deactivate the optional feature WRFD-010702 Enhanced DRX. 108 Configuring MIMO Prime This chapter describes how to activate, verify, and deactivate the basic feature WRFD-030011 MIMO Prime. 109 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. 110 Configuring Downlink 64QAM This section describes how to activate, verify, and deactivate the optional feature WRFD-010683 Downlink 64QAM. 111 Configuring 2x2 MIMO This section describes how to activate, verify, and deactivate the optional feature WRFD-010684 2x2 MIMO. Multiple Input Multiple Output (MIMO) is a multi-antenna technology, which enables multiple antennas to receive and transmit data. This increases the data transmission rate. 112 Configuring Downlink 64QAM+MIMO This section describes how to activate, verify, and deactivate the optional feature WRFD-010693 DL 64QAM+MIMO.
xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
113 Configuring Performance Improvement of MIMO and HSDPA Co-carrier This section describes how to activate, verify, and deactivate the optional feature WRFD-010700 Performance Improvement of MIMO and HSDPA. 114 Configuring Flexible HSPA+ Technology Selection This section describes how to activate, verify, and deactivate the optional feature WRFD-010704 Flexible HSPA+ Technology Selection. 115 Configuring CPC - DTX /DRX This section describes how to activate, verify, and deactivate the optional feature WRFD-010686 CPC - DTX /DRX. 116 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. 117 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. 118 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. 119 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. 120 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. 121 Configuring HSUPA UL Interference Cancellation This section describes how to activate, verify, and deactivate the optional feature WRFD-010691 HSUPA UL Interference Cancellation. 122 Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation This section describes how to activate, verify, and deactivate the optional feature WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation. 123 Configuring Anti-Interference Scheduling for HSUPA This section describes how to activate, verify, and deactivate the optional feature WRFD-020136 Anti-Interference Scheduling for HSUPA. 124 Configuring HSUPA Frequency Domain Equalization This section describes how to activate, verify, and deactivate the optional feature HSUPA Frequency Domain Equalization. 125 Configuring Uplink 16QAM
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-010694 Uplink 16QAM. 126 Configuring E-DPCCH Boosting This section describes how to activate, verify, and deactivate the optional feature WRFD-010697 E-DPCCH Boosting. 127 Configuring HSPA+ Uplink 11.5Mbps per User This section describes how to activate, verify, and deactivate the optional feature WRFD-010698 HSPA+ Uplink 11.5Mbps per User. 128 Configuring UL Layer 2 Improvement This section describes how to activate, verify, and deactivate the optional feature WRFD-010695 UL Layer 2 Improvement. 129 Configuring DC-HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-010696 DC-HSDPA. 130 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier This section describes how to activate, verify, and deactivate the optional feature WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier. 131 Configuring DC-HSDPA+MIMO (trial) This section describes how to activate, verify, and deactivate the optional feature WRFD-010699 DC-HSDPA+MIMO (trial). 132 Configuring Queuing and Preemption This section describes how to activate, verify, and deactivate the optional feature WRFD-010505 Queuing and Preemption. 133 Configuring Access Class Restriction This section describes how to activate, verify, and deactivate the optional feature WRFD-021103 Access Class Restriction. 134 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. 135 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. 136 Configuring Web Browsing Acceleration This section describes how to activate, verify, and deactivate the optional feature WRFD-020132 Web Browsing Acceleration. 137 Configuring P2P Downloading Rate Control during Busy Hour This section describes how to activate, verify, and deactivate the optional feature WRFD-020133 P2P Downloading Rate Control during Busy Hour.
xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
138 Configuring Intelligent Inter-Carrier UE Layered Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020135 Intelligent Inter-Carrier UE Layered Management. 139 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. 140 Configuring Inter Frequency Hard Handover Based on DL QoS This section describes how to activate, verify, and deactivate the optional feature WRFD-020304 Inter Frequency Hard Handover Based on DL QoS. 141 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). 142 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. 143 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. 144 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. 145 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. 146 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. 147 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. 148 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). 149 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. 150 Configuring Mobility Between UMTS and LTE Phase 1
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-020126 Mobility Between UMTS and LTE Phase 1. For details about how to configure this feature on the LTE side, see the related documents provided by the LTE equipment vendor. 151 Configuring Service-Based PS Service Redirection from UMTS to LTE (trial) This section describes how to activate, verify, and deactivate the optional feature WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE (trial). 152 Configuring Inter Frequency Load Balance This section describes how to activate, verify, and deactivate the optional feature WRFD-020103 Inter Frequency Load Balance. 153 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. 154 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. 155 Configuring DRD Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-020400 DRD Introduction Package. 156 Configuring Intra System Direct Retry This section describes how to activate, verify, and deactivate the optional feature WRFD-02040001 Intra System Direct Retry. 157 Configuring Inter System Direct Retry This section describes how to activate, verify, and deactivate the optional feature WRFD-02040002 Inter System Direct Retry. 158 Configuring Inter-System Redirect This section describes how to activate, verify, and deactivate the optional feature WRFD-02040003 Inter System Redirect. 159 Configuring Traffic Steering and Load Sharing During RAB Setup This section describes how to activate, verify, and deactivate the optional feature WRFD-02040004 Service Steering and Load Sharing During RAB Setup. 160 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. 161 Configuring Measurement-based Direct Retry This section describes how to activate, verify and deactivate the optional feature WRFD-020402 Measurement based Direct Retry. 162 Configuring Enhanced Fast Dormancy This section describes how to activate, verify, and deactivate the optional feature WRFD-020500 Enhanced Fast Dormancy.
xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
163 Configuring Cell Barring This section describes how to activate, verify, and deactivate the optional feature WRFD-021102 Cell Barring. 164 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. 165 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. 166 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. 167 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. 168 Configuring TCP Accelerator This section describes how to activate, verify, and deactivate the optional feature WRFD-020123 TCP Accelerator. 169 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. 170 Configuring Videophone Service Restriction This section describes how to activate, verify, and deactivate the optional feature WRFD-020130 Videophone Service Restriction. 171 Configuring Active Queue Management (AQM) This section describes how to activate, verify, and deactivate the optional feature WRFD-011502 Active Queue Management (AQM). 172 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. 173 Configuring Optimization of R99 and HSUPA Users Fairness This section describes how to activate, verify, and deactivate the optional feature WRFD-020131 Optimization of R99 and HSUPA Users Fairness. 174 Configuring Cell Broadcast Service This section describes how to activate, verify, and deactivate the optional feature WRFD-011000 Cell Broadcast Service. 175 Configuring Simplified Cell Broadcast
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-011001 Simplified Cell Broadcast. 176 Configuring TFO/TrFO This section describes how to activate, verify, and deactivate the optional feature WRFD-011600 TFO/TrFO. 177 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. 178 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. 179 Configuring Energy Efficiency Improved This section describes how to activate, verify, and deactivate the optional feature WRFD-020118 Energy Efficiency Improved. 180 Configuring Multi-Carrier Switch off Based on QoS This section describes how to activate, verify, and deactivate the optional feature WRFD-020122 Multi-Carrier Switch off Based on QoS. 181 Configuring Multi-Carrier Switch off Based on Power Backup This section describes how to activate, verify, and deactivate the optional feature WRFD-020119 Multi-Carrier Switch off Based on Power Backup. 182 Configuring Intelligent Power Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020121 Intelligent Power Management. 183 Configuring AMR-WB (Adaptive Multi Rate Wide Band) This section describes how to activate, verify, and deactivate the optional feature WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band). 184 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. 185 Configuring Overbooking on ATM Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-050405 Overbooking on ATM Transmission. 186 Configuring VoIP over HSPA/HSPA+ This section describes how to activate, verify, and deactivate the optional feature WRFD-010617 VoIP over HSPA/HSPA+. 187 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.
xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
188 Configuring IMS Signaling over HSPA This section describes how to activate, verify, and deactivate the basic feature WRFD-010618 IMS Signaling over HSPA. 189 Configuring PDCP Header Compression (RoHC) This section describes how to activate, verify, and deactivate the optional feature WRFD-011501 PDCP Header Compression (RoHC). 190 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+. 191 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. 192 Configuring OTDOA Based LCS This section describes how to activate, verify, and deactivate the optional feature WRFD-020802 OTDOA Based LCS. 193 Configuring A-GPS Based LCS This section describes how to activate, verify, and deactivate the optional feature WRFD-020803 A-GPS Based LCS. 194 Configuring LCS Classified Zone This section describes how to activate, verify, and deactivate the optional feature WRFD-020804 LCS Classified Zone. 195 Configuring LCS over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-020805 Configuring LCS over Iur. 196 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. 197 Configuring RAN Sharing Introduction Package This section describes how to activate, verify and deactivate the optional feature WRFD-021304 RAN Sharing Introduction Package. 198 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. 199 Configuring Flexible Network Architecture This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402 Flexible Network Architecture. 200 Configuring Mobility Control and Service Differentiation
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD02130403 Mobility Control and Service Differentiation. 201 Configuring Independent License Control This section describes how to activate, verify, and deactivate the optional feature WRFD-02130404 Independent License Control. 202 Configuring RAN Sharing Phase 2 This section describes how to activate, verify, and deactivate the optional feature WRFD-021305 RAN Sharing Phase 2. 203 Configuring Dedicated Iub Transmission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-02130501 Dedicated Iub Transmission Control. 204 Configuring IMSI-Based Handover This section describes how to activate, verify, and deactivate the optional feature WRFD-021303 IMSI-Based Handover. 205 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. 206 Configuring Carrier Sharing by Operators This section describes how to activate, verify, and deactivate the optional feature WRFD-02131101 Carrier Sharing by Operators. 207 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. 208 Configuring MOCN Mobility Management This section describes how to activate, verify, and deactivate the optional feature WRFD-02131103 MOCN Mobility Management. 209 Configuring MOCN Load Balance This section describes how to activate, verify, and deactivate the optional feature WRFD-02131104 MOCN Load Balance. 210 Configuring Routing Roaming UEs in Proportion This section describes how to activate, verify, and deactivate the optional feature WRFD-02131106 Routing Roaming UEs in Proportion. 211 Configuring Iu Flex This section describes how to activate, verify, and deactivate the optional feature WRFD-021302 Iu Flex. 212 Configuring Iu Flex Load Distribution Management This section describes how to activate, verify, and deactivate the optional feature WRFD-021306 Iu Flex Load Distribution Management.
xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
213 Configuring Enhanced Multiband Management This section describes how to activate, verify, and deactivate the optional feature WRFD-020160 Enhanced Multiband Management. 214 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. 215 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. 216 Configuring MBMS Introduction Package This section describes how to activate, verify, and deactivate the optional feature WRFD-010616 MBMS Introduction Package. 217 Configuring MBMS Admission Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061602 MBMS Admission Control. 218 Configuring MBMS Load Control This section describes how to activate, verify, and deactivate the optional feature WRFD-01061603 MBMS Load Control. 219 Configuring MBMS Transport Resource Management This section describes how to activate, verify, and deactivate the optional feature WRFD-01061605 MBMS Transport Resource Management. 220 Configuring Streaming Service on MBMS This section describes how to activate, verify, and deactivate the optional feature WRFD-01061606 Streaming Service on MBMS. 221 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. 222 Configuring MBMS Phase 2 This section describes how to activate, verify, and deactivate the optional feature WRFD-010660 MBMS Phase 2. 223 Configuring MBMS Enhanced Broadcast Mode This section describes how to activate, verify, and deactivate the optional feature WRFD-01066001 MBMS Enhanced Broadcast Mode. 224 Configuring MBMS P2P over HSDPA This section describes how to activate, verify, and deactivate the optional feature WRFD-01066002 MBMS P2P over HSDPA. 225 Configuring MBMS Admission Enhancement
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-01066003 MBMS Admission Enhancement. 226 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. 227 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. 228 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). 229 Configuring MBMS over Iur This section describes how to activate, verify, and deactivate the optional feature WRFD-010661 MBMS over Iur. 230 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. 231 Configuring MSCH Scheduling This section describes how to activate, verify, and deactivate the optional feature WRFD-010663 MSCH Scheduling. 232 Configuring MBMS Channel Audience Rating Statistics This section describes how to activate, verify, and deactivate the optional feature WRFD-010665 Configuring MBMS Channel Audience Rating Statistics. 233 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). 234 Configuring One Tunnel This section describes how to activate, verify, and deactivate the optional feature WRFD-020111 One Tunnel. 235 Configuring IP Transmission Introduction on Iub Interface This section describes how to activate, verify, and deactivate the optional feature WRFD-050402 IP Transmission Introduction on Iub Interface. 236 Configuring Hybrid Iub IP Transmission This section describes how to activate, verify and deactivate the optional feature WRFD-050403 Hybrid Iub IP Transmission. 237 Configuring ATM/IP Dual Stack NodeB This section describes how to activate, verify, and deactivate the optional feature WRFD-050404 ATM/IP Dual Stack NodeB.
xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
238 Configuring IP Transmission Introduction on Iu Interface This section describes how to activate, verify, and deactivate the optional feature WRFD-050409 IP Transmission Introduction on Iu Interface. 239 Configuring IP Transmission Introduction on Iur Interface This section describes how to activate, verify, and deactivate the optional feature WRFD-050410 IP Transmission Introduction on Iur Interface. 240 Configuring FP MUX for IP Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-050420 Configuring FP MUX for IP Transmission. 241 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. 242 Configuring Overbooking on IP Transmission This section describes how to activate, verify, and deactivate the optional feature WRFD-050408 Overbooking on IP Transmission. 243 Configuring UDP MUX for Iu-CS Transmission This section describes how to activate, verify, and deactivate the feature WRFD-050412 UDP MUX for Iu-CS Transmission. 244 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. 245 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. 246 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. 247 Configuring Ethernet OAM This section describes how to activate, verify, and deactivate the optional feature WRFD-050425 Ethernet OAM. 248 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. 249 Configuring Synchronous Ethernet This section describes how to activate, verify, and deactivate the optional feature WRFD-050502 Synchronous Ethernet. 250 Configuring RNC Node Redundancy
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-040202 RNC Node Redundancy. 251 Configuring RRU Redundancy This section describes how to activate, verify, and deactivate the optional feature WRFD-040203 RRU Redundancy. 252 Configuring Transmit Diversity This section describes how to activate, verify, and deactivate the optional feature WRFD-010203 Transmit Diversity. Transmit diversity enables the NodeB to provide twice the number of RF DL channels compared with no transmit diversity. 253 Configuring 4-Antenna Receive Diversity This section describes how to activate, verify, and deactivate the optional feature WRFD-010209 4-Antenna Receive Diversity. 254 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. 255 Configuring High Speed Access This section describes how to activate, verify, and deactivate the optional feature WRFD-010206 High Speed Access. 256 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell This section describes how to activate, verify, and deactivate the optional feature WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell. 257 Configuring PDCP Header Compression (RFC2507) This section describes how to activate, verify, and deactivate the optional feature WRFD-011500 PDCP Header Compression (RFC2507). 258 Configuring HCS (Hierarchical Cell Structure) This section describes how to activate, verify, and deactivate the optional feature WRFD-021200 HCS (Hierarchical Cell Structure). 259 Configuring Intra Frequency Load Balance This section describes how to activate, verify, and deactivate the optional feature WRFD-020104 Intra Frequency Load Balance. 260 Configuring Potential User Control This section describes how to activate, verify, and deactivate the optional feature WRFD-020105 Potential User Control. 261 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. 262 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based on Iur-g
xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
About This Document
This section describes how to activate, verify, and deactivate the optional feature WRFD-070005 NACC Procedure Optimization Based on Iur-g. 263 Configuring GSM and UMTS Load Balancing Based on Iur-g This section describes how to activate, verify, and deactivate the optional feature WRFD-070006 GSM and UMTS Load Balancing Based on Iur-g. 264 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. 265 Configuring Warning of Disaster This section describes how to activate, verify, and deactivate the optional feature WRFD-020127 Warning of Disaster. 266 Configuring Flexible frequency bandwidth of UMTS carrier This section describes how to activate, verify, and deactivate the optional feature WRFD-021001 Flexible frequency bandwidth of UMTS carrier. 267 Configuring Push to Talk This section describes how to activate, verify, and deactivate the optional feature WRFD-020134 Push to Talk. 268 Configuring RNC Offload (Trial) This section describes how to activate, verify, and deactivate the optional feature WRFD-012001 RNC Offload (Trial). With this feature, the RNC can send some PS service data directly to Internet over the offload Gi interface. 269 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). 270 Configuring GSM and UMTS Dynamic Spectrum Sharing This section describes how to activate, verify, and deactivate the optional feature MRFD-221802 GSM and UMTS Dynamic Spectrum Sharing. This feature enables the spectrum resources to be dynamically shared between the GSM and UMTS networks based on their traffic load, improving frequency utilization. 271 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. 272 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). 273 Configuring Multi-Mode BS Common Reference Clock (NodeB) This section describes how to activate, verify, and deactivate the optional feature MRFD-221601 Multi-Mode BS Common Reference Clock (NodeB).
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
About This Document
274 Configuring 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (UMTS) This section describes how to activate, verify, and deactivate the optional feature MRFD-221703 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (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 Courier New 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. 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.
xxvi
Issue 02 (2011-07-11)
About This Document
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 Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. 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.
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
About This Document
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.
xxviii
Issue 02 (2011-07-11)
Contents
Contents
About This Document...................................................................................................................iii 1 Changes in the RAN Feature Activation Guide...................................................................1-1 2 Overview of Feature Activation Guide..................................................................................2-1 3 Activating the UMTS License..................................................................................................3-1
3.1 Activating the BSC6900 License....................................................................................................................3-2 3.2 Allocating a license to Telecom Operators.....................................................................................................3-3 3.3 Allocating a License to NodeBs......................................................................................................................3-4
4 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment.................4-1 5 Configuring Conversational QoS Class ................................................................................5-1 6 Configuring Streaming QoS Class.........................................................................................6-1 7 Configuring Interactive QoS Class.........................................................................................7-1 8 Configuring Background QoS Class......................................................................................8-1 9 Configuring Emergency Call...................................................................................................9-1 10 Configuring 2-Way Antenna Receive Diversity..............................................................10-1 11 Configuring Cell Digital Combination and Split............................................................11-1 12 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH)................................................................................................................................12-1 13 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1).....................13-1 14 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2).........................14-1 15 Configuring Dynamic Channel Configuration Control.................................................15-1 16 Configuring Integrity Protection........................................................................................16-1 17 Configuring Encryption........................................................................................................17-1 18 Configuring Open Loop Power Control............................................................................18-1 19 Configuring Downlink Power Balance.............................................................................19-1 20 Configuring Outer Loop Power Control ...........................................................................20-1
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Contents
21 Configuring Inner Loop Power Control ...........................................................................21-1 22 Configuring Admission Control.........................................................................................22-1 23 Configuring Load Measurement.........................................................................................23-1 24 Configuring Load Reshuffling............................................................................................24-1 25 Configuring Overload Control............................................................................................25-1 26 Configuring Code Resource Management........................................................................26-1 27 Configuring Shared Network Support in Connected Mode.........................................27-1 28 Configuring Intra NodeB Softer Handover......................................................................28-1 29 Configuring Intra RNC Soft Handover.............................................................................29-1 30 Configuring Inter RNC Soft Handover.............................................................................30-1 31 Configuring Intra Frequency Hard Handover..................................................................31-1 32 Configuring Intra RNC Cell Update..................................................................................32-1 33 Configuring Inter RNC Cell Update..................................................................................33-1 34 Configuring Intra RNC URA Update.................................................................................34-1 35 Configuring Inter RNC URA Update.................................................................................35-1 36 Configuring Direct Signaling Connection Re-establishment (DSCR) .......................36-1 37 Configuring NodeB Clock....................................................................................................37-1 38 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.........................38-1 39 Configuring Permanent AAL5 Connections for Control Plane Traffic.......................39-1 40 Configuring Call Admission Based on Used AAL2 Path Bandwidth.........................40-1 41 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes......................................41-1 42 Configuring F5........................................................................................................................42-1 43 Configuring UBR+ ATM QoS Class..................................................................................43-1 44 Configuring Flow Control....................................................................................................44-1 45 Configuring BOOTP..............................................................................................................45-1 46 Configuring NodeB Self-discovery Based on IP Mode..................................................46-1 47 Configuring License Control for Urgency.........................................................................47-1 48 Configuring Intelligently Out of Service..........................................................................48-1 49 Configuring OCNS................................................................................................................49-1 50 Configuring Power Off the Equipment Level by Level.................................................50-1
xxx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
Contents
51 Configuring Solar Power Device Management...............................................................51-1 52 Configuring Connection with TMA (Tower Mounted Amplifier)..............................52-1 53 Configuring Remote Electrical Tilt.....................................................................................53-1 54 Configuring Same Band Antenna Sharing Unit (900 MHz)..........................................54-1 55 Configuring Multiple RAB Package .................................................................................55-1 56 Configuring Combination of Two PS Services................................................................56-1 57 Configuring Combination of One CS Service and Two PS Services...........................57-1 58 Configuring Combination of Three PS Services.............................................................58-1 59 Configuring Combination of One CS Service and Three PS Services........................59-1 60 Configuring Combination of Four PS Services................................................................60-1 61 Configuring HSDPA Introduction Package.....................................................................61-1 62 Configuring 15 Codes per Cell............................................................................................62-1 63 Configuring Time and HS-PDSCH Codes Multiplex.....................................................63-1 64 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)..........................64-1 65 Configuring HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation......................................................................................................................................65-1 66 Configuring HSDPA Power Control .................................................................................66-1 67 Configuring HSDPA Admission Control.........................................................................67-1 68 Configuring HSDPA Flow Control....................................................................................68-1 69 Configuring HSDPA Mobility Management...................................................................69-1 70 Configuring HSDPA UE Category 1 to 28.........................................................................70-1 71 Configuring Improvement of User Experience in Low Traffic Service......................71-1 72 Configuring DL 16QAM Modulation................................................................................72-1 73 Configuring Dynamic Code Allocation Based on NodeB..............................................73-1 74 Configuring HSDPA Enhanced Package...........................................................................74-1 75 Configuring Scheduling based on EPF and GBR............................................................75-1 76 Configuring HSDPA State Transition...............................................................................76-1 77 Configuring HSDPA DRD...................................................................................................77-1 78 Configuring Interactive and Background Traffic Class on HSDPA............................78-1 79 Configuring HSDPA over Iur..............................................................................................79-1 80 Configuring SRB over HSDPA...........................................................................................80-1
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Contents
81 Configuring CQI Adjustment Based on Dynamic BLER Target..................................81-1 82 Configuring HSUPA Introduction Package......................................................................82-1 83 Configuring HSUPA Admission Control..........................................................................83-1 84 Configuring HSUPA Power Control .................................................................................84-1 85 Configuring HSUPA Mobility Management...................................................................85-1 86 Configuring HSUPA DCCC.................................................................................................86-1 87 Configuring 20 HSUPA Users per Cell..............................................................................87-1 88 Configuring E-AGCH Power Control (Based on CQI or HS-SCCH)...........................88-1 89 Configuring HSUPA 2ms TTI.............................................................................................89-1 90 Configuring HSUPA 2 ms/10 ms TTI Handover..............................................................90-1 91 Configuring HSUPA 5.74Mbps per User...........................................................................91-1 92 Configuring Streaming Traffic Class on HSUPA............................................................92-1 93 Configuring 60 HSUPA Users per Cell..............................................................................93-1 94 Configuring HSUPA over Iur..............................................................................................94-1 95 Configuring SRB over HSUPA............................................................................................95-1 96 Configuring HSUPA Adaptive Transmission..................................................................96-1 97 Configuring TTI Switch for BE Services Based on Coverage.......................................97-1 98 Configuring HSUPA Coverage Enhancement at UE Power Limitation......................98-1 99 Configuring Adaptive Configuration of Traffic Channel Power.................................99-1 100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion.........................100-1 101 Configuring Dynamic CE Resource Management......................................................101-1 102 Configuring HSPA+ Downlink 28Mbps per User......................................................102-1 103 Configuring HSPA+ Downlink 21Mbps per User......................................................103-1 104 Configuring Downlink Enhanced L2.............................................................................104-1 105 Configuring Downlink Enhanced CELL_FACH.........................................................105-1 106 Configuring Uplink Enhanced CELL_FACH...............................................................106-1 107 Configuring Enhanced DRX............................................................................................107-1 108 Configuring MIMO Prime...............................................................................................108-1 109 Configuring HSPA+ Downlink 42Mbps per User......................................................109-1 110 Configuring Downlink 64QAM......................................................................................110-1
xxxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
Contents
111 Configuring 2x2 MIMO....................................................................................................111-1 112 Configuring Downlink 64QAM+MIMO......................................................................112-1 113 Configuring Performance Improvement of MIMO and HSDPA Co-carrier..........113-1 114 Configuring Flexible HSPA+ Technology Selection..................................................114-1 115 Configuring CPC - DTX /DRX.........................................................................................115-1 116 Configuring CPC-HS-SCCH Less Operation...............................................................116-1 117 Configuring 96 HSDPA Users per Cell..........................................................................117-1 118 Configuring 96 HSUPA Users per Cell..........................................................................118-1 119 Configuring 128 HSDPA Users per Cell........................................................................119-1 120 Configuring 128 HSUPA Users per Cell........................................................................120-1 121 Configuring HSUPA UL Interference Cancellation....................................................121-1 122 Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation .......................................................................................................................................................122-1 123 Configuring Anti-Interference Scheduling for HSUPA.............................................123-1 124 Configuring HSUPA Frequency Domain Equalization.............................................124-1 125 Configuring Uplink 16QAM............................................................................................125-1 126 Configuring E-DPCCH Boosting....................................................................................126-1 127 Configuring HSPA+ Uplink 11.5Mbps per User.........................................................127-1 128 Configuring UL Layer 2 Improvement..........................................................................128-1 129 Configuring DC-HSDPA..................................................................................................129-1 130 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier..........................................................................................................................130-1 131 Configuring DC-HSDPA+MIMO (trial).......................................................................131-1 132 Configuring Queuing and Preemption..........................................................................132-1 133 Configuring Access Class Restriction ...........................................................................133-1 134 Configuring Traffic Priority Mapping onto Transmission Resources....................134-1 135 Configuring Differentiated Service Based on SPI Weight........................................135-1 136 Configuring Web Browsing Acceleration.....................................................................136-1 137 Configuring P2P Downloading Rate Control during Busy Hour.............................137-1 138 Configuring Intelligent Inter-Carrier UE Layered Management.............................138-1 139 Configuring Inter Frequency Hard Handover Based on Coverage..........................139-1
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Contents
140 Configuring Inter Frequency Hard Handover Based on DL QoS............................140-1 141 Configuring SRNS Relocation (UE Not Involved)......................................................141-1 142 Configuring SRNS Relocation with Hard Handover.................................................142-1 143 Configuring SRNS Relocation with Cell/URA Update..............................................143-1 144 Configuring Inter-RAT Handover Based on Coverage..............................................144-1 145 Configuring Inter-RAT Handover Based on DL QoS.................................................145-1 146 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO .......................................................................................................................................................146-1 147 Configuring Inter-RAT Handover Phase 2...................................................................147-1 148 Configuring NACC(Network Assisted Cell Change).................................................148-1 149 Configuring PS Handover between UMTS and GPRS..............................................149-1 150 Configuring Mobility Between UMTS and LTE Phase 1...........................................150-1 151 Configuring Service-Based PS Service Redirection from UMTS to LTE (trial) .......................................................................................................................................................151-1 152 Configuring Inter Frequency Load Balance..................................................................152-1 153 Configuring Inter-RAT Handover Based on Service..................................................153-1 154 Configuring Inter-RAT Handover Based on Load......................................................154-1 155 Configuring DRD Introduction Package.......................................................................155-1 156 Configuring Intra System Direct Retry..........................................................................156-1 157 Configuring Inter System Direct Retry..........................................................................157-1 158 Configuring Inter-System Redirect................................................................................158-1 159 Configuring Traffic Steering and Load Sharing During RAB Setup......................159-1 160 Configuring Inter-RAT Redirection Based on Distance............................................160-1 161 Configuring Measurement-based Direct Retry............................................................161-1 162 Configuring Enhanced Fast Dormancy..........................................................................162-1 163 Configuring Cell Barring..................................................................................................163-1 164 Configuring 3G/2G Common Load Management.......................................................164-1 165 Configuring RAB Quality of Service Renegotiation over Iu Interface...................165-1 166 Configuring Rate Negotiation at Admission Control.................................................166-1 167 Configuring Service Steering and Load Sharing in RRC Connection Setup.........167-1 168 Configuring TCP Accelerator..........................................................................................168-1
xxxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
Contents
169 Configuring Uplink Flow Control of User Plane........................................................169-1 170 Configuring Videophone Service Restriction..............................................................170-1 171 Configuring Active Queue Management (AQM)........................................................171-1 172 Configuring Quality Improvement for Subscribed Service......................................172-1 173 Configuring Optimization of R99 and HSUPA Users Fairness................................173-1 174 Configuring Cell Broadcast Service...............................................................................174-1 175 Configuring Simplified Cell Broadcast.........................................................................175-1 176 Configuring TFO/TrFO.....................................................................................................176-1 177 Configuring Dynamic Power Sharing of Multi-Carriers...........................................177-1 178 Configuring Multi-Carrier Switch off Based on Traffic Load..................................178-1 179 Configuring Energy Efficiency Improved.....................................................................179-1 180 Configuring Multi-Carrier Switch off Based on QoS.................................................180-1 181 Configuring Multi-Carrier Switch off Based on Power Backup...............................181-1 182 Configuring Intelligent Power Management...............................................................182-1 183 Configuring AMR-WB (Adaptive Multi Rate Wide Band)........................................183-1 184 Configuring AMR/WB-AMR Speech Rates Control...................................................184-1 185 Configuring Overbooking on ATM Transmission.....................................................185-1 186 Configuring VoIP over HSPA/HSPA+...........................................................................186-1 187 Configuring Optimized Scheduling for VoIP over HSPA........................................187-1 188 Configuring IMS Signaling over HSPA........................................................................188-1 189 Configuring PDCP Header Compression (RoHC)......................................................189-1 190 Configuring CS Voice over HSPA/HSPA+...................................................................190-1 191 Configuring Cell ID + RTT Function Based LCS........................................................191-1 192 Configuring OTDOA Based LCS....................................................................................192-1 193 Configuring A-GPS Based LCS.......................................................................................193-1 194 Configuring LCS Classified Zone...................................................................................194-1 195 Configuring LCS over Iur.................................................................................................195-1 196 Configuring Iupc Interface for LCS Service.................................................................196-1 197 Configuring RAN Sharing Introduction Package.......................................................197-1 198 Configuring Dedicated Carrier for Each Operator......................................................198-1
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv
Contents
199 Configuring Flexible Network Architecture.................................................................199-1 200 Configuring Mobility Control and Service Differentiation......................................200-1 201 Configuring Independent License Control...................................................................201-1 202 Configuring RAN Sharing Phase 2.................................................................................202-1 203 Configuring Dedicated Iub Transmission Control.....................................................203-1 204 Configuring IMSI-Based Handover...............................................................................204-1 205 Configuring MOCN Introduction Package...................................................................205-1 206 Configuring Carrier Sharing by Operators...................................................................206-1 207 Configuring Dedicated NodeB/Cell for Operators......................................................207-1 208 Configuring MOCN Mobility Management................................................................208-1 209 Configuring MOCN Load Balance.................................................................................209-1 210 Configuring Routing Roaming UEs in Proportion......................................................210-1 211 Configuring Iu Flex............................................................................................................211-1 212 Configuring Iu Flex Load Distribution Management.................................................212-1 213 Configuring Enhanced Multiband Management........................................................213-1 214 Configuring Satellite Transmission on Iub Interface.................................................214-1 215 Configuring Satellite Transmission on Iu Interface...................................................215-1 216 Configuring MBMS Introduction Package...................................................................216-1 217 Configuring MBMS Admission Control.......................................................................217-1 218 Configuring MBMS Load Control..................................................................................218-1 219 Configuring MBMS Transport Resource Management.............................................219-1 220 Configuring Streaming Service on MBMS...................................................................220-1 221 Configuring 16/32/64/128Kbps Channel Rate on MBMS...........................................221-1 222 Configuring MBMS Phase 2............................................................................................222-1 223 Configuring MBMS Enhanced Broadcast Mode..........................................................223-1 224 Configuring MBMS P2P over HSDPA..........................................................................224-1 225 Configuring MBMS Admission Enhancement............................................................225-1 226 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users .......................................................................................................................................................226-1 227 Configuring FACH Transmission Sharing for MBMS...............................................227-1
xxxvi
Issue 02 (2011-07-11)
Contents
228 Configuring MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion) ................................................................................................................................228-1 229 Configuring MBMS over Iur...........................................................................................229-1 230 Configuring Dynamic Power Estimation for MTCH..................................................230-1 231 Configuring MSCH Scheduling......................................................................................231-1 232 Configuring MBMS Channel Audience Rating Statistics.........................................232-1 233 Configuring Domain Specific Access Control (DSAC)..............................................233-1 234 Configuring One Tunnel..................................................................................................234-1 235 Configuring IP Transmission Introduction on Iub Interface....................................235-1 236 Configuring Hybrid Iub IP Transmission....................................................................236-1 237 Configuring ATM/IP Dual Stack NodeB......................................................................237-1 238 Configuring IP Transmission Introduction on Iu Interface......................................238-1 239 Configuring IP Transmission Introduction on Iur Interface.....................................239-1 240 Configuring FP MUX for IP Transmission...................................................................240-1 241 Configuring Dynamic Bandwidth Control of Iub IP..................................................241-1 242 Configuring Overbooking on IP Transmission...........................................................242-1 243 Configuring UDP MUX for Iu-CS Transmission.........................................................243-1 244 Configuring ATM Switching-Based Hub NodeB........................................................244-1 245 Configuring AAL2 Switching-Based Hub NodeB.......................................................245-1 246 Configuring IP Routing-Based Hub NodeB.................................................................246-1 247 Configuring Ethernet OAM.............................................................................................247-1 248 Configuring Clock Synchronization on Ethernet in NodeB......................................248-1 249 Configuring Synchronous Ethernet................................................................................249-1 250 Configuring RNC Node Redundancy............................................................................250-1 251 Configuring RRU Redundancy.......................................................................................251-1 252 Configuring Transmit Diversity.....................................................................................252-1 253 Configuring 4-Antenna Receive Diversity....................................................................253-1 254 Configuring Extended Cell Coverage up to 200km.....................................................254-1 255 Configuring High Speed Access.....................................................................................255-1 256 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell .......................................................................................................................................................256-1
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvii
Contents
257 Configuring PDCP Header Compression (RFC2507)..................................................257-1 258 Configuring HCS (Hierarchical Cell Structure)...........................................................258-1 259 Configuring Intra Frequency Load Balance..................................................................259-1 260 Configuring Potential User Control...............................................................................260-1 261 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g .......................................................................................................................................................261-1 262 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based on Iur-g........................................................................................................................................262-1 263 Configuring GSM and UMTS Load Balancing Based on Iur-g................................263-1 264 Configuring GSM and UMTS Traffic Steering Based on Iur-g................................264-1 265 Configuring Warning of Disaster...................................................................................265-1 266 Configuring Flexible frequency bandwidth of UMTS carrier..................................266-1 267 Configuring Push to Talk.................................................................................................267-1 268 Configuring RNC Offload (Trial)...................................................................................268-1 269 Configuring Multi-mode Dynamic Power Sharing (UMTS).....................................269-1 270 Configuring GSM and UMTS Dynamic Spectrum Sharing......................................270-1 271 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB) .......................................................................................................................................................271-1
271.1 Configuring IP-Based GSM and UMTS Co-Transmission on Base Station Side..................................271-2 271.2 Configuring IP-Based UMTS and LTE Co-Transmission on Base Station Side....................................271-8
272 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side (NodeB).......................................................................................................................................272-1 273 Configuring Multi-Mode BS Common Reference Clock (NodeB)..........................273-1
273.1 Configuring GSM and UMTS Common Reference Clock.....................................................................273-2 273.2 Configuring UMTS and LTE Common Reference Clock......................................................................273-9
274 Configuring 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (UMTS)............................................................................................................................274-1
xxxviii
Issue 02 (2011-07-11)
Figures
Figures
Figure 3-1 License Distributed to Operator..........................................................................................................3-3 Figure 4-1 Iub Interface Trace dialog box............................................................................................................4-2 Figure 5-1 Iub interface trace dialog box ............................................................................................................5-2 Figure 6-1 Iu Interface Trace dialog box..............................................................................................................6-2 Figure 7-1 Iu Interface Trace dialog box..............................................................................................................7-2 Figure 8-1 Iu Interface Trace dialog box..............................................................................................................8-2 Figure 15-1 IE trafficVolumeMeasurement.......................................................................................................15-6 Figure 15-2 IE periodicalOrEventTrigger..........................................................................................................15-6 Figure 15-3 IE measurementQuantity................................................................................................................15-7 Figure 15-4 IE periodicalOrEventTrigger..........................................................................................................15-7 Figure 15-5 IE rrc-StateIndicator....................................................................................................................15-7 Figure 18-1 ul-DPCH-PowerControlIonfo IE....................................................................................................18-2 Figure 19-1 RRC_ACTIVE_SET_UPDATE_CMP message traced in Uu interface message tracing.............19-2 Figure 19-2 Information element dedicatedMeasurementType......................................................................19-3 Figure 20-1 UL SIR............................................................................................................................................20-2 Figure 20-2 OLPC..............................................................................................................................................20-2 Figure 21-1 UL SIR Tracing..............................................................................................................................21-2 Figure 21-2 UE Tx Power Tracing.....................................................................................................................21-2 Figure 36-1 Uu interface tracing dialog box .....................................................................................................36-2 Figure 36-2 RRC CONNECTION RELEASE...................................................................................................36-3 Figure 41-1 Service type of ATM......................................................................................................................41-2 Figure 60-1 VoIP service...................................................................................................................................60-1 Figure 62-1 Cell Performance Monitoring.........................................................................................................62-2 Figure 73-1 User Tracing...................................................................................................................................73-2 Figure 73-2 Message Browser............................................................................................................................73-3 Figure 73-3 Message Browser............................................................................................................................73-4 Figure 76-1 RRC_RB_RECFG message...........................................................................................................76-2 Figure 78-1 Uu Interface Trace dialog box........................................................................................................78-2 Figure 80-1 Uu Interface Trace dialog box........................................................................................................80-2 Figure 80-2 Value of the dl-TransportChannelType IE.................................................................................80-3 Figure 80-3 Value of the rb-Identity IE............................................................................................................80-3 Figure 89-1 HSUPA service with 2 ms TTI carried on the E-DCH...................................................................89-2 Figure 96-1 IE information.................................................................................................................................96-2 Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxix
Figures
RAN Feature Activation Guide Figure 97-1 Uu Interface Trace dialog box........................................................................................................97-2
Figure 97-2 2 ms TTI.........................................................................................................................................97-3 Figure 97-3 10 ms TTI.......................................................................................................................................97-3 Figure 98-1 Viewing the minReduced-E-DPDCH-GainFactor IE ................................................................98-2 Figure 99-1 PO parameters of typical services...................................................................................................99-3 Figure 99-2 Rate of the new BE service ............................................................................................................99-4 Figure 99-3 HARQ PO (4) of a UE for small retransmission at a low speed (256 kbit/s).................................99-4 Figure 99-4 HARQ PO (0) of a UE for small retransmission at a high speed...................................................99-5 Figure 99-5 HARQ PO (0) of a UE for small retransmission at a high speed ..................................................99-6 Figure 99-6 HARQ PO (4) of a UE for small retransmission at a low speed ...................................................99-6 Figure 99-7 HARQ PO (0) of a UE for large retransmission at a low speed ....................................................99-7 Figure 101-1 dynamic-CE-Switch-Private....................................................................................................101-2 Figure 104-1 Uu Interface Trace dialog box....................................................................................................104-2 Figure 104-2 Value of the IE dL RLC PDU size............................................................................................104-2 Figure 107-1 Information element in the system information message of enhanced DRX.............................107-2 Figure 107-2 Indication sent from the RNC to the NodeB on the DCCH or DTCH.......................................107-3 Figure 107-3 HS-DSCH DATA FRAME type2..............................................................................................107-3 Figure 109-1 Connection Performance Monitoring dialog box.......................................................................109-2 Figure 110-1 Uu interface tracing....................................................................................................................110-2 Figure 110-2 Checking the dl-64QAM-Configured information element.....................................................110-3 Figure 111-1 Uu Interface Trace dialog box....................................................................................................111-4 Figure 111-2 IE mimoParameters..................................................................................................................111-5 Figure 114-1 mimoParameters message........................................................................................................114-3 Figure 114-2 dl-SecondaryCellInfoFDD IE...................................................................................................114-3 Figure 115-1 Uu interface tracing task.............................................................................................................115-2 Figure 115-2 IE information.............................................................................................................................115-2 Figure 116-1 RRC_RB_SETUP Information...................................................................................................116-2 Figure 121-1 Cell RTWP 1..............................................................................................................................121-2 Figure 122-1 Cell RTWP 1..............................................................................................................................122-2 Figure 122-2 Cell RTWP 2..............................................................................................................................122-2 Figure 123-1 Cell RTWP (feature disabled)....................................................................................................123-2 Figure 123-2 Cell RTWP (feature enabled).....................................................................................................123-3 Figure 125-1 Uu Interface tracing....................................................................................................................125-2 Figure 125-2 Indication of uplink 16QAM......................................................................................................125-3 Figure 126-1 Tracing messages over the Uu interface.....................................................................................126-3 Figure 126-2 Tracing messages over the Iub interface....................................................................................126-4 Figure 128-1 Uu Interface Trace dialog box....................................................................................................128-2 Figure 128-2 Value of the IE rlc-PDU-Size....................................................................................................128-3 Figure 129-1 Uu Interface Trace dialogue box..............................................................................................129-4 Figure 129-2 RRC_RB_SETUP message.......................................................................................................129-4 Figure 133-1 RRC_SYS_INFO_TYPE3 message...........................................................................................133-2 Figure 133-2 RRC_SYS_INFO_TYPE3 message...........................................................................................133-3 xl Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
Figures
Figure 135-1 SPI and SPI weight of UE A in the uplink ................................................................................135-3 Figure 135-2 SPI and SPI weight of UE A in the downlink ...........................................................................135-4 Figure 135-3 SPI and SPI weight of UE B in the uplink ................................................................................135-4 Figure 135-4 SPI and SPI weight of UE B in the downlink ............................................................................135-5 Figure 138-1 Uu interface tracing task.............................................................................................................138-3 Figure 138-2 Message tracing..........................................................................................................................138-3 Figure 139-1 Event 2D measurement report....................................................................................................139-2 Figure 139-2 Inter-frequency measurement control message..........................................................................139-2 Figure 140-1 RRC_RB_RECFG message.......................................................................................................140-2 Figure 140-2 RRC_RB_RECFG message.......................................................................................................140-3 Figure 140-3 RRC_RB_RECFG message.......................................................................................................140-3 Figure 141-1 Iu Interface Trace dialog box......................................................................................................141-3 Figure 141-2 Iur Interface Trace dialog box....................................................................................................141-3 Figure 142-1 SRNS Relocation with Hard Handover......................................................................................142-3 Figure 144-1 Event 2D measurement report....................................................................................................144-2 Figure 144-2 Inter-frequency measurement control message..........................................................................144-2 Figure 145-1 RRC_RB_RECFG message.......................................................................................................145-2 Figure 145-2 RRC_RB_RECFG message.......................................................................................................145-3 Figure 145-3 RRC_RB_RECFG message.......................................................................................................145-3 Figure 150-1 Uu Interface Trace dialog box....................................................................................................150-3 Figure 150-2 SIB message tracing...................................................................................................................150-3 Figure 151-1 Viewing the IE e-UTRA-FrequencyInfo .................................................................................151-2 Figure 151-2 Viewing the IE EUTRA-TargetFreqInfo ................................................................................151-3 Figure 153-1 Inter-frequency measurement control message..........................................................................153-2 Figure 160-1 Uu Interface Trace dialog box....................................................................................................160-2 Figure 160-2 GSM-Targetcellinfo IE.............................................................................................................160-3 Figure 162-1 Status of the Enhanced Fast Dormancy license..........................................................................162-5 Figure 162-2 UE in the CELL_DCH state.......................................................................................................162-5 Figure 162-3 State transition to the CELL_PCH state.....................................................................................162-6 Figure 162-4 Cell update..................................................................................................................................162-6 Figure 162-5 Channel reconfiguration.............................................................................................................162-6 Figure 163-1 Uu Interface Trace dialog box....................................................................................................163-2 Figure 163-2 Uu Interface Trace dialog box....................................................................................................163-3 Figure 163-3 Uu Interface Trace dialog box....................................................................................................163-4 Figure 166-1 Iu message tracing......................................................................................................................166-2 Figure 166-2 RANAP_RAB_ASSIGNMENT_REQ message on the Iu interface .........................................166-2 Figure 166-3 Iu message tracing......................................................................................................................166-3 Figure 166-4 RANAP_RAB_ASSIGNMENT_RESP message on the Iu interface .......................................166-3 Figure 169-1 Iub interface trace dialog box ....................................................................................................169-2 Figure 169-2 TrafficClass-Private....................................................................................................................169-3 Figure 171-1 UE Trace dialog box...................................................................................................................171-2 Figure 173-1 Iub interface tracing dialog box .................................................................................................173-2 Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xli
Figures
RAN Feature Activation Guide Figure 173-2 fairness common measurement report........................................................................................173-3
Figure 174-1 Viewing the SABP_LOAD_QUERY message..........................................................................174-3 Figure 174-2 Viewing the SABP_LOAD_QUERY_CMP message................................................................174-3 Figure 174-3 Viewing the CBS function..........................................................................................................174-4 Figure 174-4 Viewing the SABP_WRITE_REPLACE message ....................................................................174-5 Figure 174-5 Viewing the SABP_WRITE_REPLACE_CMP message .........................................................174-6 Figure 174-6 Viewing the UU_BMC_MSG_TYPE message .........................................................................174-7 Figure 174-7 Viewing the SAB_KILL message..............................................................................................174-8 Figure 174-8 Viewing the SABP_KILL_CMP message.................................................................................174-9 Figure 175-1 UU_BMC_MSG_TYPE message .............................................................................................175-2 Figure 184-1 Uu interface tracing....................................................................................................................184-3 Figure 184-2 IEs contained in RRC_MEAS_CTRL........................................................................................184-3 Figure 184-3 AMR mode.................................................................................................................................184-4 Figure 186-1 Uu Interface Trace dialog box....................................................................................................186-3 Figure 186-2 UE in CELL_DCH state.............................................................................................................186-3 Figure 186-3 VoIP services carried on HSPA/HSPA+....................................................................................186-4 Figure 186-4 Type of TTI carried in the message............................................................................................186-4 Figure 188-1 Uu Interface Trace dialog box....................................................................................................188-2 Figure 188-2 UE in CELL_DCH state.............................................................................................................188-2 Figure 188-3 VoIP services carried on HSPA/HSPA+....................................................................................188-3 Figure 188-4 Type of TTI carried in the message............................................................................................188-3 Figure 190-1 Uu Interface Trace dialog box....................................................................................................190-3 Figure 190-2 UE in CELL_DCH state.............................................................................................................190-3 Figure 190-3 CS voice services carried on HSPA/HSPA+..............................................................................190-3 Figure 190-4 Type of TTI carried in the message............................................................................................190-4 Figure 191-1 Iu Interface Trace dialog box .....................................................................................................191-2 Figure 191-2 Iub Interface Trace dialog box ...................................................................................................191-3 Figure 191-3 Uu Interface Trace dialog box ...................................................................................................191-3 Figure 191-4 LOCATION REPORTING CONTROL....................................................................................191-4 Figure 191-5 LOCATION REPORT...............................................................................................................191-5 Figure 191-6 Dedicated Measurement Type....................................................................................................191-6 Figure 191-7 Round Trip Time........................................................................................................................191-6 Figure 191-8 UE Rx-Tx time difference..........................................................................................................191-7 Figure 191-9 UE Rx-Tx time difference type 1...............................................................................................191-7 Figure 193-1 Iub interface tracing....................................................................................................................193-4 Figure 193-2 Uu Interface Trace dialog box ...................................................................................................193-4 Figure 193-3 LOCATION REPORTING CONTROL....................................................................................193-5 Figure 193-4 LOCATION REPORT...............................................................................................................193-6 Figure 193-5 ue-positioning-GPS-AssistanceData..........................................................................................193-6 Figure 193-6 GPS-MeasurementParam............................................................................................................193-7 Figure 194-1 Iub Interface Trace dialog box....................................................................................................194-2 Figure 194-2 LOCATION REPORT message.................................................................................................194-3 xlii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
Figures
Figure 195-1 Iur Interface Trace dialog box....................................................................................................195-3 Figure 195-2 GPS assistance data carried in the INFORMATION REPORT message...............................195-3 Figure 195-3 INFORMATION EXCHANGE INITIATION REQUEST.......................................................195-4 Figure 195-4 INFORMATION EXCHANGE INITIATION RESPONSE.....................................................195-5 Figure 195-5 DEDICATED MEASUREMENT INITIATION REQUEST....................................................195-5 Figure 195-6 DEDICATED MEASUREMENT INITIATION RESPONSE..................................................195-6 Figure 206-1 PLMN Identify field in the MIB message..................................................................................206-2 Figure 206-2 Multiple PLMN List IE in the MIB message.............................................................................206-3 Figure 207-1 PLMN Identify IE in the MIB message......................................................................................207-2 Figure 213-1 Message containing the IE..........................................................................................................213-2 Figure 233-1 DSAC activated..........................................................................................................................233-2 Figure 233-2 DSAC not activated....................................................................................................................233-3 Figure 234-1 Iu Interface Trace dialog box......................................................................................................234-2 Figure 234-2 Iu Interface Trace dialog box......................................................................................................234-2 Figure 234-3 Configured GGSN IP address.....................................................................................................234-2 Figure 241-1 Link performance monitoring.....................................................................................................241-2 Figure 247-1 PPP Ethernet OAM network.......................................................................................................247-2 Figure 250-1 Network topology not configured with RNC pool.....................................................................250-2 Figure 250-2 Network topology configured with RNC pool...........................................................................250-2 Figure 250-3 Normal heartbeat between RNC202 and RNC203.....................................................................250-5 Figure 250-4 NodeB control rights obtained by RNC202...............................................................................250-5 Figure 250-5 CS AMR service set up successfully..........................................................................................250-5 Figure 268-1 Offload Gi interface....................................................................................................................268-1 Figure 271-1 IP-over-FE GSM and UMTS co-transmission on base station side...........................................271-2 Figure 271-2 IP-over-E1/T1 GSM and UMTS co-transmission on base station side......................................271-3 Figure 271-3 IP-over-GE GSM and UMTS co-transmission on base station side..........................................271-3 Figure 271-4 IP over FE/GE UMTS and LTE co-transmission on base station side.......................................271-9 Figure 271-5 IP over E1/T1 UMTS and LTE co-transmission on base station side........................................271-9 Figure 272-1 GTMU-based TDM timeslot cross connection co-transmission................................................272-2 Figure 272-2 GSM-UTRP-based TDM timeslot cross connection co-transmission........................................272-2 Figure 273-1 Common GPS reference clock...................................................................................................273-3 Figure 273-2 Common BITS reference clock..................................................................................................273-4 Figure 273-3 Common E1/T1 reference clock on the GSM side (GTMU).....................................................273-4 Figure 273-4 Common E1/T1 reference clock on the UMTS side (WMPT)...................................................273-4 Figure 273-5 Common Ethernet reference clock on the UMTS side (WMPT)...............................................273-5 Figure 273-6 Common IP reference clock on the UMTS side (WMPT).........................................................273-5 Figure 273-7 Common GPS reference clock.................................................................................................273-10 Figure 273-8 Common BITS reference clock................................................................................................273-11 Figure 273-9 Common E1/T1 reference clock on the UMTS side (WMPT).................................................273-11 Figure 273-10 Common Ethernet reference clock on the LTE side (LMPT)................................................273-12 Figure 273-11 Common IP reference clock on the LTE side (LMPT)..........................................................273-12
Issue 02 (2011-07-11)
xliii
Tables
Tables
Table 2-1 RAN Basic Feature List.......................................................................................................................2-1 Table 2-2 RAN Optional Feature List..................................................................................................................2-7 Table 37-1 Parameters........................................................................................................................................37-2 Table 37-2 Parameters........................................................................................................................................37-2 Table 162-1 Processing procedure after the comparison..................................................................................162-4 Table 215-1 Timers related to SAAL links of satellite transmission...............................................................215-2 Table 271-1 IP Planning of connecting between BTS and BSC......................................................................271-3 Table 271-2 IP Planning of connecting between NodeB and RNC (IP over FE/GE)......................................271-3 Table 271-3 IP planning of connection between NodeB and RNC (IP over E1/T1).......................................271-4
Issue 02 (2011-07-11)
xlv
Changes in the RAN Feature Activation Guide

This chapter describes the changes in the RAN Feature Activation Guide.
02 (2011-07-11)
This is the second commercial release of V900R013C00. Compared with issue 01 (2011-04-25), this issue includes the following new topics: l l 81 Configuring CQI Adjustment Based on Dynamic BLER Target 108 Configuring MIMO Prime
Compared with issue 01 (2011-04-25), this issue does not incorporate any changes. Compared with issue 01 (2011-04-25), this issue does not exclude any topics.
01 (2011-04-25)
This is the first commercial release of V900R013C00. Compared with issue Draft B (2011-03-21), this issue includes the following new topics: l 170 Configuring Videophone Service Restriction
Compared with issue Draft B (2011-03-21), this issue does not incorporate any changes. Compared with issue Draft B (2011-03-21), this issue does not exclude any topics.
Draft B (2011-03-21)
This is the Draft B release of V900R013C00. Compared with issue Draft A (2011-01-31), this issue includes the following new topics: l l l l
Issue 02 (2011-07-11)
136 Configuring Web Browsing Acceleration 137 Configuring P2P Downloading Rate Control during Busy Hour 235 Configuring IP Transmission Introduction on Iub Interface 238 Configuring IP Transmission Introduction on Iu Interface
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
239 Configuring IP Transmission Introduction on Iur Interface
Compared with issue Draft A (2011-01-31), this issue does not incorporate any changes. Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.
Draft A (2011-01-31)
This is the Draft A release of V900R013C00. Compared with issue 06 (2010-11-30) of V900R012C01, this issue includes the following new topics: l l l l l l l l l l l l l l l l l l l l l l 98 Configuring HSUPA Coverage Enhancement at UE Power Limitation 99 Configuring Adaptive Configuration of Traffic Channel Power 106 Configuring Uplink Enhanced CELL_FACH 107 Configuring Enhanced DRX 114 Configuring Flexible HSPA+ Technology Selection 122 Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation 123 Configuring Anti-Interference Scheduling for HSUPA 126 Configuring E-DPCCH Boosting 127 Configuring HSPA+ Uplink 11.5Mbps per User 130 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier 131 Configuring DC-HSDPA+MIMO (trial) 138 Configuring Intelligent Inter-Carrier UE Layered Management 151 Configuring Service-Based PS Service Redirection from UMTS to LTE (trial) 173 Configuring Optimization of R99 and HSUPA Users Fairness 180 Configuring Multi-Carrier Switch off Based on QoS 182 Configuring Intelligent Power Management 210 Configuring Routing Roaming UEs in Proportion 256 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell 267 Configuring Push to Talk 268 Configuring RNC Offload (Trial) 270 Configuring GSM and UMTS Dynamic Spectrum Sharing 274 Configuring 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (UMTS)
Compared with issue 06 (2010-11-30) of V900R012C01, this issue does not incorporate any changes. Compared with issue 06 (2010-11-30) of V900R012C01, this issue does not exclude any topics.
1-2
Issue 02 (2011-07-11)
2 Overview of Feature Activation Guide
Overview of Feature Activation Guide
RAN features are classified into basic and optional features. Basic features are not licensecontrolled and therefore do not require license activation before use. Optional features are license-controlled and therefore require license activation before use. Table 2-1 lists the RAN basic features. Table 2-2 lists the RAN optional features. Table 2-1 RAN Basic Feature List Feature ID WRFD-000001 WRFD-000002 WRFD-000003 WRFD-000004 WRFD-000005 WRFD-000006 WRFD-000007 WRFD-000008 WRFD-010101 WRFD-010102 WRFD-010201 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 System Improvement for RAN13.0 3GPP R9 Specifications Operating Multi-band FDD Mode Configuration Method None None None None None None None None None None None
Issue 02 (2011-07-11)
2-1
Feature ID WRFD-010510
Feature Name 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 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-Way 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 4 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment 5 Configuring Conversational QoS Class 6 Configuring Streaming QoS Class 7 Configuring Interactive QoS Class 8 Configuring Background QoS Class None None
WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 WRFD-010609 WRFD-01060901
WRFD-01060902 WRFD-01060903
None None
WRFD-021104 MRFD-210604 WRFD-010205 WRFD-010208 WRFD-010211 WRFD-010202
9 Configuring Emergency Call 10 Configuring 2-Way Antenna Receive Diversity 11 Configuring Cell Digital Combination and Split None None 12 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH) None
WRFD-010401
System Information Broadcasting
2-2
Issue 02 (2011-07-11)
Feature Name 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 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
Configuration Method 13 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) 14 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2) None None None 15 Configuring Dynamic Channel Configuration Control 16 Configuring Integrity Protection 17 Configuring Encryption 18 Configuring Open Loop Power Control 19 Configuring Downlink Power Balance 20 Configuring Outer Loop Power Control 21 Configuring Inner Loop Power Control 22 Configuring Admission Control 23 Configuring Load Measurement 24 Configuring Load Reshuffling 25 Configuring Overload Control 26 Configuring Code Resource Management 27 Configuring Shared Network Support in Connected Mode
2-3
WRFD-010302
WRFD-020900 WRFD-021000 WRFD-022000 WRFD-021101
WRFD-011401 WRFD-011402 WRFD-020501 WRFD-020502 WRFD-020503 WRFD-020504 WRFD-020101 WRFD-020102 WRFD-020106 WRFD-020107 WRFD-020108 WRFD-021301
Issue 02 (2011-07-11)
Feature ID MRFD-210104 WRFD-020201 WRFD-020202 WRFD-020203 WRFD-020301 WRFD-010801 WRFD-010802 WRFD-010901 WRFD-010902 WRFD-021400
Feature Name BSC/RNC Resource Sharing Intra NodeB Softer Handover Intra NodeB Softer Handover Inter RNC Soft Handover 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 NodeB Clock 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
Configuration Method None 28 Configuring Intra NodeB Softer Handover 29 Configuring Intra RNC Soft Handover 30 Configuring Inter RNC Soft Handover 31 Configuring Intra Frequency Hard Handover 32 Configuring Intra RNC Cell Update 33 Configuring Inter RNC Cell Update 34 Configuring Intra RNC URA Update 35 Configuring Inter RNC URA Update 36 Configuring Direct Signaling Connection Reestablishment (DSCR) None None None 37 Configuring NodeB Clock None None None None
MRFD-210204 MRFD-210205 MRFD-210206 MRFD-210501 MRFD-210502 WRFD-050301 WRFD-05030101 WRFD-05030102
WRFD-05030103
None
2-4
Issue 02 (2011-07-11)
Feature Name 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 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 Interrupt in RNC System Redundancy Operate System Security Management Performance Management Fault Management Inventory Management Configuration Management Security Management Interface Tracing Call Tracing RNC Software Management NodeB Software Management
Configuration Method 38 Configuring Dynamic AAL2 Connections in Iub/ IuCS/Iur Interface 39 Configuring Permanent AAL5 Connections for Control Plane Traffic 40 Configuring Call Admission Based on Used AAL2 Path Bandwidth 41 Configuring CBR, rtVBR, nrt-VBR, UBR ATM QoS Classes 42 Configuring F5 None
WRFD-05030105
WRFD-05030106
WRFD-05030107
WRFD-05030110 WRFD-050304
WRFD-050305 MRFD-210103 WRFD-040100 WRFD-040101
43 Configuring UBR+ ATM QoS Class None 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
None None None None None None None None None None None
Issue 02 (2011-07-11)
2-5
Feature ID MRFD-210310 WRFD-031100 WRFD-031101
Feature Name NodeB Software USB Download BOOTP NodeB Self-discovery Based on IP Mode NodeB Remote Selfconfiguration NodeB Self-test License Management License Control for Urgency DBS Topology Maintenance Intelligently Out of Service OCNS Power off the equipment level by level Solar Power Device Management Single IP Address for NodeB Intelligent Power Measurement 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)
Configuration Method None 45 Configuring BOOTP 46 Configuring NodeB Selfdiscovery Based on IP Mode None None None 47 Configuring License Control for Urgency None 48 Configuring Intelligently Out of Service 49 Configuring OCNS 50 Configuring Power Off the Equipment Level by Level 51 Configuring Solar Power Device Management None None None None 52 Configuring Connection with TMA (Tower Mounted Amplifier) 53 Configuring Remote Electrical Tilt 54 Configuring Same Band Antenna Sharing Unit (900 MHz) None
WRFD-031102 WRFD-031103 MRFD-210403 WRFD-040300 MRFD-210309 WRFD-031000 WRFD-031200 WRFD-031400
WRFD-031500 WRFD-021404 WRFD-020406 WRFD-010212 MRFD-210701 MRFD-210601
MRFD-210602 WRFD-060003
MRFD-220001
2-6
Issue 02 (2011-07-11)
Feature ID MRFD-220002
Feature Name Multi-mode BS RRU/RFU star-connection with separate CPRI interface(NodeB)
Configuration Method None
Table 2-2 RAN Optional Feature List Feature ID Feature Name License Control Item Multiple RAB License Configured on... BSC6900 Configuration Method 55 Configuring Multiple RAB Package 56 Configuring Combination of Two PS Services 57 Configuring Combination of One CS Service and Two PS Services 58 Configuring Combination of Three PS Services 59 Configuring Combination of One CS Service and Three PS Services 60 Configuring Combination of Four PS Services
WRFD-010615
Multiple RAB Package Combination of Two PS Services Combination of One CS Service and Two PS Services
WRFD-010615 01
Multiple RAB
BSC6900
WRFD-010615 02
Multiple RAB
BSC6900
WRFD-010615 03
Combination of Three PS Services Combination of One CS Service and Three PS Services
Multiple RAB
BSC6900
WRFD-010615 04
Multiple RAB
BSC6900
WRFD-010615 05
Combination of Four PS Services
Multiple RAB
BSC6900
Issue 02 (2011-07-11)
2-7
Feature ID
Feature Name
License Control Item RNC:High Speed Downlink Packet Access NODEB:the number of NodeBs with HSDPA function enabled
License Configured on... BSC6900&Nod eB
Configuration Method 61 Configuring HSDPA Introduction Package
WRFD-010610
HSDPA Introduction Package
WRFD-010610 17
QPSK Modulation
RNC:High Speed Downlink Packet Access NODEB:the number of NodeBs with HSDPA function enabled
BSC6900&Nod eB
None
WRFD-010610 01
15 Codes per Cell
BSC6900&Nod eB
62 Configuring 15 Codes per Cell
WRFD-010610 18
Time and HSPDSCH Codes Multiplex
BSC6900&Nod eB
63 Configuring Time and HSPDSCH Codes Multiplex
2-8
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item RNC:High Speed Downlink Packet Access NODEB:the number of NodeBs with HSDPA function enabled RNC:High Speed Downlink Packet Access NODEB:the number of NodeBs with HSDPA function enabled RNC:High Speed Downlink Packet Access NODEB:the number of NodeBs with HSDPA function enabled
Configuration Method 64 Configuring HSDPA HARQ & Scheduling (MAX C/I, RR, and PF)
WRFD-010610 09
HSDPA HARQ & Scheduling (MAX C/I, RR and PF)
WRFD-010610 05
HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation
BSC6900&Nod eB
65 Configuring HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation
WRFD-010610 04
HSDPA Power Control
BSC6900&Nod eB
66 Configuring HSDPA Power Control
WRFD-010610 03
HSDPA Admission Control
BSC6900&Nod eB
67 Configuring HSDPA Admission Control
Issue 02 (2011-07-11)
2-9
Feature ID
Feature Name
WRFD-010610 19
HSDPA Dynamic Power Allocation
WRFD-010610 10
HSDPA Flow Control
BSC6900&Nod eB
68 Configuring HSDPA Flow Control
WRFD-010610 06
HSDPA Mobility Management
BSC6900&Nod eB
69 Configuring HSDPA Mobility Management
WRFD-010610 14
HSDPA Transport Resource Management
BSC6900&Nod eB
None
2-10
Issue 02 (2011-07-11)
Feature ID
Feature Name
WRFD-010610 08
Interactive and Background Traffic Class on HSDPA
WRFD-010610 02
HSDPA UE Category 1 to 28
BSC6900&Nod eB
70 Configuring HSDPA UE Category 1 to 28
WRFD-010610 15
HSDPA 1.8Mbps per User
BSC6900&Nod eB
None
WRFD-010610 16
16 HSDPA Users per Cell
BSC6900&Nod eB
None
Issue 02 (2011-07-11)
2-11
Feature ID
Feature Name
Configuration Method 71 Configuring Improvement of User Experience in Low Traffic Service
WRFD-010610 20
Improvement of User Experience in Low Traffic Service
WRFD-010620
HSDPA 3.6Mbps per User DL 16QAM Modulation
High Speed Downlink Packet Access Function 3.6M the number of NodeBs with HSDPA RRM package 1 enabled the number of NodeBs with HSDPA RRM package 1 enabled High Speed Downlink Packet Access Function 7.2M 32 HSDPA Users per Cell None
BSC6900
None
WRFD-010629
NodeB
72 Configuring DL 16QAM Modulation
WRFD-010631
Dynamic Code Allocation Based on NodeB HSDPA 7.2Mbps per User 32 HSDPA Users per Cell HSDPA Enhanced Package Scheduling based on EPF and GBR HSDPA State Transition
NodeB
73 Configuring Dynamic Code Allocation Based on NodeB None
WRFD-010621
BSC6900
WRFD-010622 WRFD-010611
BSC6900 None
None 74 Configuring HSDPA Enhanced Package 75 Configuring Scheduling based on EPF and GBR 76 Configuring HSDPA State Transition
WRFD-010611 03
None
None
WRFD-010611 11
HSDPA State Transition
BSC6900
2-12
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item HSDPA DRD HS-DPCCH Preamble support Streaming Traffic Class on HSDPA
License Configured on... BSC6900 BSC6900
Configuration Method 77 Configuring HSDPA DRD None
WRFD-010611 12 WRFD-010611 13 WRFD-010630
HSDPA DRD HS-DPCCH Preamble Support Streaming Traffic Class on HSDPA
BSC6900
78 Configuring Interactive and Background Traffic Class on HSDPA None
WRFD-010650
HSDPA 13.976Mbps per User HSDPA over Iur
HSDPA 13.976Mbps per User HSDPA over Iur
BSC6900
WRFD-010651
BSC6900
79 Configuring HSDPA over Iur 80 Configuring SRB over HSDPA None 81 Configuring CQI Adjustment Based on Dynamic BLER Target 82 Configuring HSUPA Introduction Package
WRFD-010652
SRB over HSDPA 64 HSDPA Users per Cell CQI Adjustment based on dynamic BLER target HSUPA Introduction Package
SRB over HSDPA 64 HSDPA Users per Cell CQI Adjustment Based on Dynamic BLER Target(per Cell) RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled
BSC6900
WRFD-010623 WRFD-030010
BSC6900 NodeB
WRFD-010612
BSC6900&Nod eB
Issue 02 (2011-07-11)
2-13
Feature ID
Feature Name
License Control Item RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled
WRFD-010612 01
HSUPA UE Category 1 to 7
WRFD-010612 09
HSUPA HARQ and Fast UL Scheduling in NodeB
RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled
BSC6900&Nod eB
None
WRFD-010612 02
HSUPA Admission Control
BSC6900&Nod eB
83 Configuring HSUPA Admission Control
WRFD-010612 03
HSUPA Power Control
RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled
BSC6900&Nod eB
84 Configuring HSUPA Power Control
2-14
Issue 02 (2011-07-11)
Feature ID
Feature Name
Configuration Method 85 Configuring HSUPA Mobility Management
WRFD-010612 04
HSUPA Mobility Management
WRFD-010612 08
HSUPA DCCC
BSC6900&Nod eB
86 Configuring HSUPA DCCC
WRFD-010612 07
HSUPA Transport Resource Management
RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled RNC:High Speed Uplink Packet Access NodeB:the number of NodeBs with HSUPA function enabled
BSC6900&Nod eB
None
WRFD-010612 06
Interactive and Background Traffic Class on HSUPA
BSC6900&Nod eB
None
Issue 02 (2011-07-11)
2-15
Feature ID
Feature Name
WRFD-010612 10
HSUPA 1.44Mbps per User
WRFD-010612 11
20 HSUPA Users per Cell
BSC6900&Nod eB
87 Configuring 20 HSUPA Users per Cell
WRFD-010614 WRFD-010614 01
HSUPA Phase 2 HSUPA EAGCH Power Control (Based on CQI or HSSCCH) Enhanced Fast UL Scheduling HSUPA 2ms TTI
None None
None None
None 88 Configuring E-AGCH Power Control (Based on CQI or HS-SCCH) None 89 Configuring HSUPA 2ms TTI
WRFD-010614 02 WRFD-010614 03
None the number of NodeBs with HSUPA 2ms TTI function enabled HSUPA 2ms/ 10ms TTI handover HSUPA 5.74Mbps per User
None NodeB
WRFD-010614 04
HSUPA 2ms/ 10ms TTI Handover HSUPA 5.74Mbps per User
BSC6900
90 Configuring HSUPA 2 ms/ 10 ms TTI Handover 91 Configuring HSUPA 5.74Mbps per User
WRFD-010614 05
BSC6900
2-16
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item Streaming Traffic Class on HSUPA 60 HSUPA Users per Cell HSUPA over Iur
License Configured on... BSC6900
Configuration Method 92 Configuring Streaming Traffic Class on HSUPA 93 Configuring 60 HSUPA Users per Cell 94 Configuring HSUPA over Iur 95 Configuring SRB over HSUPA None
WRFD-010632
Streaming Traffic Class on HSUPA 60 HSUPA Users per Cell HSUPA over Iur
WRFD-010634
BSC6900
WRFD-010635
BSC6900
WRFD-010636
SRB over HSUPA Uplink Macro Diversity Intelligent Receiving HSUPA Adaptive Transmission TTI Switch for BE Services Based on Coverage HSUPA Coverage Enhancement at UE power limitation Adaptive Configuration of Traffic Channel Power offset for HSUPA
SRB over HSUPA Uplink Macro Diversity Intelligent Receiving HSUPA Adaptive Retransmission TTI Switch for BE Services Based on Coverage HSUPA Coverage Enhancement at UE power limitation Adaptive Config of Traffic Channel Power for HSUPA
BSC6900
WRFD-010640
BSC6900
WRFD-010641
BSC6900
96 Configuring HSUPA Adaptive Transmission 97 Configuring TTI Switch for BE Services Based on Coverage 98 Configuring HSUPA Coverage Enhancement at UE Power Limitation 99 Configuring Adaptive Configuration of Traffic Channel Power
WRFD-010690
BSC6900
WRFD-020138
BSC6900
WRFD-010712
BSC6900
Issue 02 (2011-07-11)
2-17
Feature ID
Feature Name
License Control Item None
License Configured on... None
Configuration Method 100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion 101 Configuring Dynamic CE Resource Management 102 Configuring HSPA+ Downlink 28Mbps per User 103 Configuring HSPA+ Downlink 21Mbps per User 104 Configuring Downlink Enhanced L2 105 Configuring Downlink Enhanced CELL_FACH 106 Configuring Uplink Enhanced CELL_FACH 107 Configuring Enhanced DRX
WRFD-010637
HSUPA Iub Flow Control in Case of Iub Congestion
WRFD-010638
Dynamic CE Resource Management
the number of NodeBs with dynamic CE function enabled HSPA + Downlink 28 Mbit/s Per User
NodeB
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
Downlink Enhanced CELL_FACH
Enhanced CELL_FACH
BSC6900
WRFD-010701
Uplink Enhanced CELL_FACH
Enhanced Uplink for CELL_FACH
BSC6900
WRFD-010702
Enhanced DRX
Enhanced DRX
BSC6900
2-18
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item MIMO Prime (per Cell) HSPA+ Downlink 42Mbps per User
License Configured on... NodeB
Configuration Method 108 Configuring MIMO Prime 109 Configuring HSPA+ Downlink 42Mbps per User 110 Configuring Downlink 64QAM None
WRFD-030011
MIMO Prime
WRFD-010689
BSC6900
WRFD-010683
Downlink 64QAM
the number of cells with 64QAM function enabled HSPA+ Downlink 84Mbit/s per User the number of cells with MIMO function enabled the number of Cells with DL 64QAM +MIMO function enabled The number of cells with performace improvement of MIMO and HSDPA cocarrier function enabled Flexible HSPA + Technology Selection
NodeB
WRFD-010703
HSPA+ Downlink 84Mbit/s per User (trial) 2x2 MIMO
BSC6900
WRFD-010684
NodeB
111 Configuring 2x2 MIMO 112 Configuring Downlink 64QAM +MIMO 113 Configuring Performance Improvement of MIMO and HSDPA Cocarrier 114 Configuring Flexible HSPA + Technology Selection
WRFD-010693
DL 64QAM +MIMO
NodeB
WRFD-010700
Performance Improvement of MIMO and HSDPA Cocarrier
NodeB
WRFD-010704
Flexible HSPA + Technology Selection
BSC6900
Issue 02 (2011-07-11)
2-19
Feature ID
Feature Name
License Control Item CPC-DTX / DRX
Configuration Method 115 Configuring CPC - DTX / DRX 116 Configuring CPC-HSSCCH Less Operation 117 Configuring 96 HSDPA Users per Cell 118 Configuring 96 HSUPA Users per Cell 119 Configuring 128 HSDPA Users per Cell 120 Configuring 128 HSUPA Users per Cell 121 Configuring HSUPA UL Interference Cancellation 122 Configuring DualThreshold Scheduling with HSUPA Interference Cancellation
WRFD-010686
CPC - DTX / DRX
WRFD-010687
CPC - HSSCCH less operation
CPC-HS-SCCH Less Operation
BSC6900
WRFD-010653
BSC6900
WRFD-010639
BSC6900
WRFD-010654
BSC6900
WRFD-010670
BSC6900
WRFD-010691
HSUPA UL Interference Cancellation
The number of Cells with UL IC function enabled the number of NodeBs with dual-threshold scheduling with HSUPA interference cancellation function enabled
NodeB
WRFD-020137
Dual-Threshold Scheduling with HSUPA Interference Cancellation
NodeB
2-20
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item the number of cells with antiinterference scheduling for HSUPA function enabled The number of Cells with FDE function enabled
Configuration Method 123 Configuring AntiInterference Scheduling for HSUPA 124 Configuring HSUPA Frequency Domain Equalization 125 Configuring Uplink 16QAM 126 Configuring EDPCCH Boosting
WRFD-020136
AntiInterference Scheduling for HSUPA
WRFD-010692
HSUPA FDE
NodeB
WRFD-010694
UL 16QAM
The number of Cells with UL 16QAM function enabled the number of cells with EDPCCH boosting function enabled HSPA+ Uplink 11.5Mbit/s per User
NodeB
WRFD-010697
E-DPCCH Boosting
NodeB
WRFD-010698
HSPA+ Uplink 11.5Mbit/s per User
BSC6900
127 Configuring HSPA+ Uplink 11.5Mbps per User 128 Configuring UL Layer 2 Improvement
WRFD-010695
UL Layer 2 Improvement
The number of Cells with UL L2 Improvement function enabled The number of Cells with DL DC function enabled
NodeB
WRFD-010696
DC-HSDPA
NodeB
129 Configuring DC-HSDPA
Issue 02 (2011-07-11)
2-21
Feature ID
Feature Name
Configuration Method 130 Configuring Traffic-Based Activation and Deactivation of the Supplementar y Carrier In Multi-carrier 131 Configuring DC-HSDPA +MIMO (trial)
WRFD-010713
Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multicarrier
WRFD-010699
DC-HSDPA +MIMO (trial)
the number of cells with DCHSDPA +MIMO function enabled Queuing and Pre-emption
NodeB
WRFD-010505
Queuing and Pre-Emption
BSC6900
132 Configuring Queuing and Preemption 133 Configuring Access Class Restriction 134 Configuring Traffic Priority Mapping onto Transmission Resources 135 Configuring Differentiated Service Based on SPI Weight 136 Configuring Web Browsing Acceleration
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-020132
Web browsing acceleration
Web Page Access Acceleration
BSC6900
2-22
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item P2P Rate Restriction During Busy Hours
Configuration Method 137 Configuring P2P Downloading Rate Control during Busy Hour 138 Configuring Intelligent Inter-Carrier UE Layered Management 139 Configuring Inter Frequency Hard Handover Based on Coverage 140 Configuring Inter Frequency Hard Handover Based on DL QoS None
WRFD-020133
P2P Downloading Rate Control during Busy Hour
WRFD-020135
Intelligent InterCarrier UE Layered Management
Intelligent InterCarrier UE Layered Management (per Cell) Inter frequency hard handover
BSC6900
WRFD-020302
Inter Frequency Hard Handover Based on Coverage
BSC6900
WRFD-020304
Inter Frequency Hard Handover Based on DL QoS
Inter Frequency Hard Handover Based on DL QoS
BSC6900
WRFD-020605
SRNS Relocation Introduction Package SRNS Relocation (UE Not Involved)
SRNS Relocation (UE Not Involved) None
BSC6900
WRFD-020605 01
None
141 Configuring SRNS Relocation (UE Not Involved) 142 Configuring SRNS Relocation with Hard Handover
WRFD-020605 02
SRNS Relocation with Hard Handover
SRNS Relocation with Hard Handover
BSC6900
Issue 02 (2011-07-11)
2-23
Feature ID
Feature Name
License Control Item SRNS Relocation with Cell/URA Update
Configuration Method 143 Configuring SRNS Relocation with Cell/URA Update None 144 Configuring Inter-RAT Handover Based on Coverage 145 Configuring Inter-RAT Handover Based on DL QoS 146 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO 147 Configuring Inter-RAT Handover Phase 2 148 Configuring NACC (Network Assisted Cell Change)
WRFD-020605 03
SRNS Relocation with Cell/URA Update
WRFD-020605 04 WRFD-020303
Lossless SRNS Relocation Inter-RAT Handover Based on Coverage
Lossless SRNS Relocation Coverage Based Inter-RAT Handover Between UMTS and GSM/ GPRS Inter-RAT Handover Based on DL QoS
BSC6900 BSC6900
WRFD-020309
Inter-RAT Handover Based on DL QoS
BSC6900
WRFD-020307
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
BSC6900
WRFD-020308
Inter-RAT Handover Phase 2
None
None
WRFD-020308 01
NACC (Network Assisted Cell Change)
NACC (Network Assisted Cell Change)
BSC6900
2-24
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item PS Handover Between UMTS and GPRS
Configuration Method 149 Configuring PS Handover between UMTS and GPRS 150 Configuring Mobility Between UMTS and LTE Phase 1 151 Configuring Service-Based PS Service Redirection from UMTS to LTE (trial) 152 Configuring Inter Frequency Load Balance 153 Configuring Inter-RAT Handover Based on Service 154 Configuring Inter-RAT Handover Based on Load 155 Configuring DRD Introduction Package 156 Configuring Intra System Direct Retry
2-25
WRFD-020308 02
PS Handover Between UMTS and GPRS
WRFD-020126
Mobility Between UMTS and LTE Phase 1
Mobility Between UMTS and LTE Phase 1
BSC6900
WRFD-020129
Service-Based PS Service Redirection from UMTS to LTE (trial)
PS Service Redirection from UMTS to LTE
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
WRFD-020306
Inter-RAT Handover Based on Load
Inter system Load Handover
BSC6900
WRFD-020400
DRD Introduction Package
None
None
WRFD-020400 01
Intra System Direct Retry
Intra System Direct Retry
BSC6900
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item Inter System Direct Retry
Configuration Method 157 Configuring Inter System Direct Retry 158 Configuring Inter-System Redirect 159 Configuring Traffic Steering and Load Sharing During RAB Setup 160 Configuring Inter-RAT Redirection Based on Distance 161 Configuring Measurementbased Direct Retry 162 Configuring Enhanced Fast Dormancy 163 Configuring Cell Barring 164 Configuring 3G/2G Common Load Management
WRFD-020400 02
Inter System Direct Retry
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
WRFD-020500
Enhanced Fast Dormancy
Fast Dormancy Enhancement (per PS Active User) Cell Barring when IU in fault 3G/2G Common Load Management
BSC6900
WRFD-021102
Cell Barring
BSC6900
WRFD-020310
3G/2G Common Load Management
BSC6900
2-26
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item RAB Quality of Service Renegotiation over Iu
Configuration Method 165 Configuring RAB Quality of Service Renegotiation over Iu Interface 166 Configuring Rate Negotiation at Admission Control 167 Configuring Service Steering and Load Sharing in RRC Connection Setup 168 Configuring TCP Accelerator 169 Configuring Uplink Flow Control of User Plane 170 Configuring Videophone Service Restriction 171 Configuring Active Queue Management (AQM)
WRFD-010506
RAB Quality of Service Renegotiation over Iu Interface
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
WRFD-020130
Videophone Service Restriction
Videophone Service Restriction
BSC6900
WRFD-011502
Active Queue Management (AQM)
Active Queue Management (AQM)
BSC6900
Issue 02 (2011-07-11)
2-27
Feature ID
Feature Name
License Control Item Quality Improvement for Subscribed Service
Configuration Method 172 Configuring Quality Improvement for Subscribed Service 173 Configuring Optimization of R99 and HSUPA Users Fairness 174 Configuring Cell Broadcast Service 175 Configuring Simplified Cell Broadcast 176 Configuring TFO/TrFO 177 Configuring Dynamic Power Sharing of MultiCarriers 178 Configuring Multi-Carrier Switch off Based on Traffic Load 179 Configuring Energy Efficiency Improved
WRFD-020128
Quality Improvement for Subscribed Service
WRFD-020131
Optimization of R99 and HSUPA Users Fairness
Optimization of R99 and HSUPA Users Fairness
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
the number of NodeBs with PA-SHARING function enabled 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
the number of NodeBs with energy efficiency improved function enabled
NodeB
2-28
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item the number of cells with multicarrier switch off based on QoS function enabled Multi-Carrier Switch off Based on Power Backup
Configuration Method 180 Configuring Multi-Carrier Switch off Based on QoS 181 Configuring Multi-Carrier Switch off Based on Power Backup 182 Configuring Intelligent Power Management 183 Configuring AMR-WB (Adaptive Multi Rate Wide Band) 184 Configuring AMR/WBAMR Speech Rates Control 185 Configuring Overbooking on ATM Transmission 186 Configuring VoIP over HSPA/HSPA+ None
WRFD-020122
Multi-Carrier Switch off Based on QoS
WRFD-020119
Multi-Carrier Switch off Based on Power Backup
NodeB
WRFD-020121
Intelligent Power Management
None
None
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
BSC6900
WRFD-010617 01
RAB Mapping
BSC6900
Issue 02 (2011-07-11)
2-29
Feature ID
Feature Name
License Control Item VoIP over HSPA Introduction Pakage
Configuration Method 187 Configuring Optimized Scheduling for VoIP over HSPA 188 Configuring IMS Signaling over HSPA 189 Configuring PDCP Header Compression (RoHC) 190 Configuring CS Voice over HSPA/HSPA+ 191 Configuring Cell ID + RTT Function Based LCS 192 Configuring OTDOA Based LCS 193 Configuring AGPS Based LCS 194 Configuring LCS Classified Zone 195 Configuring LCS over Iur
WRFD-010617 03
Optimized Scheduling for VoIP over HSPA
WRFD-010618
IMS Signaling over HSPA
IMS Signaling over HSPA
BSC6900
WRFD-011501
PDCP Header Compression (RoHC)
PDCP ROHC Function
BSC6900
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
2-30
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item Iu-PC Interface for LCS service
Configuration Method 196 Configuring Iupc Interface for LCS Service 197 Configuring RAN Sharing Introduction Package 198 Configuring Dedicated Carrier for Each Operator 199 Configuring Flexible Network Architecture 200 Configuring Mobility Control and Service Differentiation 201 Configuring Independent License Control None
WRFD-020807
Iupc Interface for LCS service
WRFD-021304
RAN Sharing Introduction Package
RAN Sharing Function
BSC6900
WRFD-021304 01
Dedicated Carrier for Each Operator
BSC6900
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
BSC6900
202 Configuring RAN Sharing Phase 2
Issue 02 (2011-07-11)
2-31
Feature ID
Feature Name
Configuration Method 203 Configuring Dedicated Iub Transmission Control 204 Configuring IMSI-Based Handover 205 Configuring MOCN Introduction Package 206 Configuring Carrier Sharing by Operators 207 Configuring Dedicated NodeB/Cell for Operators 208 Configuring MOCN Mobility Management 209 Configuring MOCN Load Balance None
WRFD-021305 01
Dedicated Iub Transmission Control
WRFD-021303
IMSI Based Handover
IMSI Based Handover
BSC6900
WRFD-021311
MOCN Introduction Package
BSC6900
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 MOCN Introduction Package
BSC6900
WRFD-021311 05
MOCN Independent Performance Management Routing Roaming UEs in Proportion
BSC6900
WRFD-021311 06
BSC6900
210 Configuring Routing Roaming UEs in Proportion
2-32
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item IU FLEX
Configuration Method 211 Configuring Iu Flex 212 Configuring Iu Flex Load Distribution Management None
WRFD-021302
Iu Flex
WRFD-021306
Iu Flex Load Distribution Management
Enhanced Iu Flex
BSC6900
WRFD-020110
Multi Frequency Band Networking Management Enhanced Multiband Management
Multi Frequency Band Networking Management Enhancement for Multi frequency band Networking management Satellite Communication in Iub Interface
BSC6900
WRFD-020160
BSC6900
213 Configuring Enhanced Multiband Management 214 Configuring Satellite Transmission on Iub Interface 215 Configuring Satellite Transmission on Iu Interface 216 Configuring MBMS Introduction Package None 217 Configuring MBMS Admission Control
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 WRFD-010616 02
MBMS Broadcast Mode MBMS Admission Control
MBMS Function MBMS Function
BSC6900 BSC6900
Issue 02 (2011-07-11)
2-33
Feature ID
Feature Name
License Control Item MBMS Function
Configuration Method 218 Configuring MBMS Load Control None
WRFD-010616 03
MBMS Load Control
WRFD-010616 04 WRFD-010616 05
MBMS Soft/ Selective Combining MBMS Transport Resource Management
BSC6900
BSC6900
219 Configuring MBMS Transport Resource Management 220 Configuring Streaming Service on MBMS None
WRFD-010616 06
Streaming Service on MBMS
MBMS Function
BSC6900
WRFD-010616 07 WRFD-010616 08
MBMS 2 Channels per Cell 16/32/64/128K bps Channel Rate on MBMS
BSC6900
BSC6900
221 Configuring 16/32/64/128K bps Channel Rate on MBMS 222 Configuring MBMS Phase 2 223 Configuring MBMS Enhanced Broadcast Mode 224 Configuring MBMS P2P over HSDPA
WRFD-010660
MBMS Phase 2
MBMS P2P over HSDPA MBMS Enhanced Broadcast Mode
BSC6900
WRFD-010660 01
MBMS Enhanced Broadcast Mode
BSC6900
WRFD-010660 02
MBMS P2P over HSDPA
MBMS P2P over HSDPA
BSC6900
2-34
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item MBMS Admission Enhancement
Configuration Method 225 Configuring MBMS Admission Enhancement 226 Configuring InterFrequency Neighboring Cell Selection for MBMS PTP Users 227 Configuring FACH Transmission Sharing for MBMS 228 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
229 Configuring MBMS over Iur
Issue 02 (2011-07-11)
2-35
Feature ID
Feature Name
License Control Item Dynamic Power Estimation for MTCH
Configuration Method 230 Configuring Dynamic Power Estimation for MTCH 231 Configuring MSCH Scheduling 232 Configuring MBMS Channel Audience Rating Statistics 233 Configuring Domain Specific Access Control (DSAC) 234 Configuring One Tunnel 235 Configuring IP Transmission Introduction on Iub Interface None
WRFD-010662
Dynamic Power Estimation for MTCH
WRFD-010663
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
IP Transportation in Iub Interface
BSC6900
WRFD-050411
Fractional IP Function on Iub Interface Hybrid Iub IP Transmission
Fractional IP
BSC6900
WRFD-050403
IUB Hybrid IP Transportation Function IUB ATM/IP Dual Stack Transportation Function
BSC6900
236 Configuring Hybrid Iub IP Transmission 237 Configuring ATM/IP Dual Stack NodeB
WRFD-050404
ATM/IP Dual Stack NodeB
BSC6900
2-36
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item IP Transportation in Iu Interface
Configuration Method 238 Configuring IP Transmission Introduction on Iu Interface 239 Configuring IP Transmission Introduction on Iur Interface 240 Configuring FP MUX for IP Transmission 241 Configuring Dynamic Bandwidth Control of Iub IP 242 Configuring Overbooking on IP Transmission 243 Configuring UDP MUX for Iu-CS Transmission 244 Configuring ATM SwitchingBased Hub NodeB 245 Configuring AAL2 SwitchingBased Hub NodeB
WRFD-050409
IP Transmission Introduction on Iu Interface
WRFD-050410
IP Transmission Introduction on Iur Interface
IP Transportation in Iur Interface
BSC6900
WRFD-050420
FP MUX for IP Transmission
FP MUX
BSC6900
WRFD-050422
Dynamic Bandwidth Control of Iub IP
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 02 (2011-07-11)
2-37
Feature ID
Feature Name
Configuration Method 246 Configuring IP Routing-Based Hub NodeB None
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
247 Configuring Ethernet OAM 248 Configuring Clock Synchronizatio n on Ethernet in NodeB 249 Configuring Synchronous Ethernet
WRFD-050501
Clock Sync on Ethernet in NodeB
the number of NodeBs with IP Clock function enabled
NodeB
WRFD-050502
Synchronous Ethernet
The Number of NodeBs with Ethernet Synchronizatio n Function Enabled RNC Node Redundancy
NodeB
WRFD-040202
RNC Node Redundancy
BSC6900
250 Configuring RNC Node Redundancy 251 Configuring RRU Redundancy 252 Configuring Transmit Diversity 253 Configuring 4Antenna Receive Diversity
WRFD-040203
RRU Redundancy
None
None
WRFD-010203
Transmit Diversity
None
None
WRFD-010209
4-Antenna Receive Diversity
None
None
2-38
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item the number of NodeBs with CCPIC function enabled
WRFD-010210
Control Channel Parallel Interference Cancellation (CCPIC) Extended Cell Coverage up to 200km
WRFD-021308
None
None
254 Configuring Extended Cell Coverage up to 200km None
WRFD-021309
Improved Downlink Coverage High Speed Access
Improved Downlink Coverage None
BSC6900
WRFD-010206
None
255 Configuring High Speed Access 256 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell 257 Configuring PDCP Header Compression (RFC2507) None
WRFD-021350
Independent Demodulation of Signals from Multiple RRUs in One Cell
the number of RRUs with in independent demodulation of signals in one cell PDCP Header compression
NodeB
WRFD-011500
PDCP Header Compression (RFC2507)
BSC6900
WRFD-050302
Fractional ATM Function on Iub Interface HCS (Hierarchical Cell Structure)
Fractional ATM
BSC6900
WRFD-021200
Hierarchical Cell Structure
BSC6900
258 Configuring HCS (Hierarchical Cell Structure) 259 Configuring Intra Frequency Load Balance
WRFD-020104
Intra Frequency Load Balance
Intra frequency load balancing
BSC6900
Issue 02 (2011-07-11)
2-39
Feature ID
Feature Name
License Control Item Potential user control
Configuration Method 260 Configuring Potential User Control 261 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g 262 Configuring NACC (Network Assisted Cell Change) Procedure Optimization Based on Iur-g 263 Configuring GSM and UMTS Load Balancing Based on Iur-g 264 Configuring GSM and UMTS Traffic Steering Based on Iur-g 265 Configuring Warning of Disaster 266 Configuring Flexible frequency bandwidth of UMTS carrier
WRFD-020105
Potential User Control
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
BSC Load Balancing Based on Iur-g
BSC6900
WRFD-070007
GSM and UMTS Traffic Steering Based on Iur-g
BSC Service Distribution Based on Iur-g
BSC6900
WRFD-020127
Warning of Disaster
Warning of Disaster
BSC6900
WRFD-021001
Flexible frequency bandwidth of UMTS carrier
None
None
2-40
Issue 02 (2011-07-11)
Feature ID
Feature Name
License Control Item Push To Talk
Configuration Method 267 Configuring Push to Talk 268 Configuring RNC Offload (Trial) 269 Configuring Multi-mode Dynamic Power Sharing (UMTS) 270 Configuring GSM and UMTS Dynamic Spectrum Sharing 271 Configuring IP-Based Multi-Mode CoTransmission on Base Station Side (NodeB) 272 Configuring TDM-Based Multi-mode CoTransmission via Backplane on BS side (NodeB)
WRFD-020134
Push to Talk
WRFD-012001
RNC offload (trial)
None
None
MRFD-221801
Multi-mode Dynamic Power Sharing (UMTS)
the number of NodeBs with Multi-mode Dynamic Power Sharing function enabled GSM and UMTS Dynamic Spectrum Sharing (UMTS) None
NodeB
MRFD-221802
GSM and UMTS Dynamic Spectrum Sharing (UMTS) IP-Based Multimode CoTransmission on BS side (NodeB)
NodeB
MRFD-221501
None
MRFD-221504
TDM-Based Multi-mode CoTransmission via Backplane on BS side (NodeB)
None
None
Issue 02 (2011-07-11)
2-41
Feature ID
Feature Name
License Control Item the number of NodeBs with Bandwidth sharing of MBTS Multimode CoTransmission function enabled None
MRFD-221505
Bandwidth sharing of MBTS Multimode CoTransmission (NodeB)
MRFD-221601
Multi-mode BS Common Reference Clock(NodeB)
None
273 Configuring Multi-Mode BS Common Reference Clock (NodeB) 274 Configuring 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (UMTS)
MRFD-221703
2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS)
2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS)
NodeB
2-42
Issue 02 (2011-07-11)
3 Activating the UMTS License
3
About This Chapter
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. 3.1 Activating the BSC6900 License This section describes how to activate the BSC6900 license. 3.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. 3.3 Allocating a License to NodeBs After uploading a NodeB license file of a RAN to the M2000 server, you need to allocate the license to the NodeBs in the RAN. Then you can activate the license for it to take effect.
Issue 02 (2011-07-11)
3-1
3.1 Activating the BSC6900 License

This section describes how to activate the BSC6900 license.
Prerequisite
l l The LMT is started and you have logged in to the BSC6900. The BSC6900 is in service.
Procedure
Step 1 Run the BSC6900 MML command LST ESN and record the Equipment Serial Number (ESN) of the BSC. Step 2 Run the BSC6900 MML command DLD LICENSE to download the license file from the FTP server to the \ftp\license directory of the main area directory of the OMU. Step 3 Run the LST LICENSE command and enter the filename of the license to be activated to query the file information. If... Then...
The file information complies with the information of Go to Step 4. the file that you apply for, The file information does not comply with the information of the file that you apply for, Exit the task and contact Huawei.
Step 4 Run the LST CFGMODE command to query the BSC6900 configuration status. If the BSC6900 is ineffective, run the SET CFGDATAEFFECTIVE command to switch it to the effective state. Step 5 Run the ACT LICENSE command to activate the license. Step 6 If the primary operator and secondary operators exist, run the SET LICENSE command to active the license for the primary operator first and then for secondary operators. If multiple secondary operators exist, run the SET LICENSE command repeatedly. Step 7 Run the BSC6900 MML command CMP LICENSE to check whether the running license on the host is consistent with that on the OMU. If... Then...
If the running license on the host is consistent with that End the task or go to Step 8. on the OMU If the running license on the host is inconsistent with that on the OMU End the task and contact Huawei.
3-2
Issue 02 (2011-07-11)
Step 8 In the case of high traffic, run the SET LICENSECTRL command to enable the license control function of the BSC6900 to enter the grace protection period. For details, see License Control in Emergencies. ----End
3.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. As show in Figure 3-1. Figure 3-1 License Distributed to Operator
Issue 02 (2011-07-11)
3-3
Step 4 In the License Distributed to Operator window, set available functions and resources for each telecom operator, and then click OK. For details about the parameters, see Parameters of NodeB License Information. ----End
3.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 3.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. To view the values indicating that the control item is not supported by NodeBs, click the status description on the right in the Modify dialog box. For descriptions of the values, see Parameter Description in the dialog box. l When setting a certain control item, you can click Clear to clear the preset values in the column of the control item. l You can click Settings in the Modify dialog box to add or delete one or multiple control items to be set.
Step 5 Perform operations according to license allocation policies. After a NodeB license file is uploaded to the M2000, you can allocate the license to NodeBs immediately. You can also create a scheduled task for delivering preset license allocation information to NodeBs at a certain non-busy hour. You can allocate an inactive license to NodeBs. After an inactive license is allocated to NodeBs, it is activated automatically.
3-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
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 1. In the license information area, right-click a license record, and then choose License NodeBs on a scheduled basis 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. For details about the task parameters, see Parameters for Setting the Common Information About Timing TasksCommon Information About Timing Tasks and Parameters for Creating/Modifying/Copying Scheduled NodeB License Allocation Tasks. ----End
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, the M2000 reports the EVT-513 The Amount of Used NodeB License's Resource Exceeds the Threshold event, and 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, the M2000 reports the EVT-514 Changes in the Usage of NE License Resources event, and you need to synchronize the license allocation information saved on the M2000 to the NodeBs. For details, see Synchronizing a NodeB License.
Issue 02 (2011-07-11)
3-5
4 Configuring 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment
4
Prerequisite
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.
l l l
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
This feature enables RRC connection establishment and release and RAB assignment for services of different rates, so as to meet different QoS requirements. This feature is fundamental to service provision.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET URRCESTCAUSE 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 4-1
Issue 02 (2011-07-11)
4-1
Figure 4-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
4-2
Issue 02 (2011-07-11)
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;
Issue 02 (2011-07-11)
4-3
5 Configuring Conversational QoS Class
5
Prerequisite
Configuring Conversational QoS Class

This section describes how to activate, verify, and deactivate the basic feature WRFD-010501 Conversational QoS Class.
l l l l
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. Others The UE and the CN support the conversational class.
Context
Based on QoS requirements, 3GPP defines four traffic classes: conversational, streaming, interactive, and background. They differ in their sensitivity to delay. The conversational class is highly sensitive to the delay and therefore has a high requirement on real-time transmission. The conversational class has the following fundamental characteristics: l 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 CS AMR speech services at the rates of 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s CS transparent data services (conversational class) at the rates of 64 kbit/s, 56 kbit/s, 32 kbit/s, and 28.8 kbit/s
Issue 02 (2011-07-11)
PS bidirectional symmetric voice services at the rates of 64 kbit/s, 42.8 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s
Procedure
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 5-1.
Verification Procedure 1.
Figure 5-1 Iub interface trace dialog box
2.
Establish a conversational service on the UE. Check the DPC (that is, the source) of the RANAP_RAB_ASSIGNMENT_REQ message among the traced Iu data to determine whether the service is a CS service or PS service. 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 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.
3.
4.
5-2
Issue 02 (2011-07-11)
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;
Issue 02 (2011-07-11)
5-3
6 Configuring Streaming QoS Class
6
Prerequisite
l l l l License
Configuring Streaming QoS Class
This section describes how to activate, verify, and deactivate the basic feature WRFD-010502 Streaming QoS Class.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. This feature is not under license control. 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.
Streaming services are real-time services, such as audio and video programs. They are transmitted in only one direction and serve individual users.
Procedure
l
Issue 02 (2011-07-11)
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 6-1
Figure 6-1 Iu Interface Trace dialog box
2.
Use a UE to set up a streaming service. Check the DPC (that is, the source) of the RANAP_RAB_ASSIGNMENT_REQ message among the traced Iu data to determine whether the service is a CS service or PS service. 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. 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.
3. 4.
6-2
Issue 02 (2011-07-11)
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;
Issue 02 (2011-07-11)
6-3
7 Configuring Interactive QoS Class
7
Prerequisite
l l l l
Configuring Interactive QoS Class
This section describes how to activate, verify, and deactivate the basic feature WRFD-010503 Interactive QoS Class.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. 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.
Issue 02 (2011-07-11)
7-1
7 Configuring Interactive QoS Class
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-1
2.
Use a UE to set up an interactive service. Check the RANAP_RAB_ASSIGNMENT_REQ message and check that the value of the trafficClass information element (IE) in rRB-Parameters is interactive. View the maxBitrate and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ message. 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.
3.
Deactivation Procedure 1. This feature does not need to be deactivated.
----End
Example
//Activating Interactive QoS Class SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900, UlBeTraffThsOnHsupa=D5440;
7-2
Issue 02 (2011-07-11)
8 Configuring Background QoS Class
8
Prerequisite
l l l l
Configuring Background QoS Class
This section describes how to activate, verify, and deactivate the basic feature WRFD-010504 Background QoS Class.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. 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.
Issue 02 (2011-07-11)
8-1
8 Configuring Background QoS Class
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 8-1
2.
Use a UE to set up a background service. Check the RANAP_RAB_ASSIGNMENT_REQ message and check that the value of the trafficClass information element (IE) in rRB-Parameters is background. View the maxBitrate and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ message. 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.
----End
Example
//Activating Background QoS Class SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900, UlBeTraffThsOnHsupa=D5440;
8-2
Issue 02 (2011-07-11)
9 Configuring Emergency Call
9
Prerequisite
l l l License
Configuring Emergency Call
This section describes how to activate, verify, and deactivate the basic feature WRFD-021104 Emergency Call.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. This feature is not under license control.
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 an emergency call.. The emergency call is successfully established. Deactivation Procedure This feature need not be deactivated.
----End
Issue 02 (2011-07-11)
9-1
10 Configuring 2-Way Antenna Receive Diversity
10
Prerequisite
l l l
Configuring 2-Way Antenna Receive Diversity
This section describes how to activate, verify, and deactivate the basic feature MRFD-210604 2-Way Antenna Receive Diversity.
Dependencies on Hardware In receive diversity mode, the NodeB should provide sufficient RF channels and demodulation resources to meet the requirements for the number of antenna diversities. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
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. Expected result: Antenna Magnitude is 2. l Deactivation Procedure This feature does not need to be deactivated. ----End
Issue 02 (2011-07-11) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-1
10 Configuring 2-Way Antenna Receive Diversity
Example
//Activation procedure ADD SEC: STN=1, SECN=0, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE, ANT1SRN=60, ANT1N=R0A, ANT2SRN=60, ANT2N=R0B; //Verification procedure LST SEC: STN=1, SECN=0;
10-2
Issue 02 (2011-07-11)
11 Configuring Cell Digital Combination and Split
11
Prerequisite
l
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.
Dependencies on Hardware Only DBS3800, DBS3900 and iDBS3900 support this feature. 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, each RRU supports only the one-antenna receive mode. Multipleantenna 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. RF modules, RRU 3828 and RRU3829 can only support maximum of 4 carriers when they are implemented for Cell Digital Combination and Split.
l l
Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
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.
11 Configuring Cell Digital Combination and Split
Procedure
l Activation Procedure 1. 2. 3. 4. l Run the NodeB MML command ADD RRUCHAIN to add an RRU chain. In this step, set Topo Type to CHAIN. Run the NodeB MML command ADD RRU to add an RRU. Set a group of RRUs in consecutive numbering to the RRUs to be used by the distributed sector. Run the NodeB MML command ADD SEC to add a sector. In this step, set Sector Type to DIST_SECTOR(DIST_SECTOR). Run the NodeB MML command ADD LOCELL to add a local cell. In this step, set Sector Type to DIST_SECTOR(DIST_SECTOR). 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).
Verification Procedure 1. 2.
Deactivation Procedure This feature does not need to be deactivated.
----End
Example
1. NodeB V200R013
//Activation procedure ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=2, HPN=0; ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO; ADD RRU: CN=0, SRN=61, SN=1, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=UO; ADD SEC: STN=0, SECN=1, SECT=DIST_SECTOR, SRNB=60, SRNE=61; ADD LOCELL: LOCELL=100, STN=0, SECN=1, SECT=DIST_SECTOR, RRUMODE=SYNC, ULFREQ=9610, DLFREQ=10560, HISPM=FALSE; //Verification procedure LST SEC: STN=0, SECN=1; LST LOCELL: MODE=LOCALCELL, LOCELL=100;
2.
NodeB V100R013
//Activation procedure ADD RRUCHAIN: RCN=0, TT=CHAIN, HSN=0, HPN=0; ADD RRU: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, RT=MRRU; ADD RRU: CN=0, SRN=61, TP=TRUNK, RCN=0, PS=0, RT=MRRU; ADD SEC: STN=0, SECN=1, SECT=DIST_SECTOR, SRNB=60, SRNE=61; ADD LOCELL: LOCELL=100, STN=0, SECN=1, SECT=DIST_SECTOR, BBPOOLTYPE=GEN_POOL, RRUMODE=SYNC, ULFREQ=9610, DLFREQ=10560, HISPM=FALSE; //Verification procedure LST SEC: STN=0, SECN=1; LST LOCELL: MODE=LOCALCELL, LOCELL=100;
11-2
Issue 02 (2011-07-11)
12 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH)
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).
12
l l l l
Configuring UE State in Connected
Prerequisite
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. Other Prerequisites The Iu-PS activity factor is already modified. The Iu-PS activity factor can be modified by running the ADD TRMFACTOR and MOD ADJMAP commands. The recommended value of the Iu-PS activity factor is 10%.
NOTE
If there are excessive users in the CELL_PCH or URA_PCH state, a large amount of bandwidth on the Iu-PS interface is consumed though such users do not have data to transmit. Adjusting the Iu-PS activity factor can prevent PS service admission failures due to the increase in the number of UEs in the CELL_PCH or URA_PCH state.
Context
Huawei RAN supports four states of UEs in connected mode: CELL_DCH, CELL_PCH, URA_PCH, and CELL_FACH. This feature helps save radio resources efficiently.
Procedure
l
Issue 02 (2011-07-11)
12 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH)
A UE can directly enter the CELL_FACH or CELL_DCH state. It can enter the CELL_PCH or URA_PCH state only through state transition from CELL_FACH or CELL_DCH. The settings of state transition are as follows: 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the DRA_PS_BE_STATE_TRANS_SWITCH check box under the parameter Dynamic Resource Allocation Switch. Run the BSC6900 MML command SET UUESTATETRANSTIMER. In this step, set BE FACH or E_FACH to PCH Transition Timer and Cell Reselection Timer to appropriate values. Run the BSC6900 MML command SET UUESTATETRANS. In this step, set Cell Reselection Counter Threshold to an appropriate value.
NOTE
2.
3.
l This feature involves the parameter settings of state transition from CELL_FACH or CELL_DCH to CELL_PCH or URA_PCH. For the parameter settings of other types of state transition, see 15 Configuring Dynamic Channel Configuration Control. l For the parameter settings related to fast dormancy, see 162 Configuring Enhanced Fast Dormancy.
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 15 Configuring Dynamic Channel Configuration Control. Deactivation Procedure This feature does not need to be deactivated.
----End
Example
//Activating UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH) SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1; SET UUESTATETRANSTIMER: BeD2FStateTransTimer=65535, CellReSelectTimer=180; SET UPSINACTTIMER: CellReSelectCounter=9;;
12-2
Issue 02 (2011-07-11)
13 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
13
Prerequisite
l l l
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).
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 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.
3. 4. l
Verification Procedure (Paging a UE in Idle Mode) 1.
Issue 02 (2011-07-11)
13 Configuring Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
2. 3. l
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
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 12 Configuring UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).
----End
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;
13-2
Issue 02 (2011-07-11)
14 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2)
14
Prerequisite
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).
l l l
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 02 (2011-07-11)
14 Configuring Paging UE in CELL_FACH, CELL_DCH State (Type 2)
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 performs 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
Deactivation Procedure
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;
14-2
Issue 02 (2011-07-11)
15 Configuring Dynamic Channel Configuration Control
15
Prerequisite
l l l
Configuring Dynamic Channel Configuration Control
This section describes how to activate, verify, and deactivate the basic feature WRFD-021101 Dynamic Channel Configuration Control (DCCC).
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
This feature allows dynamic rate adjustment and UE state transition triggered by various reasons. This improves the quality of services and increases resource utilization.
Procedure
l Activating DCCC 1. To activate the DCCC algorithm, perform the following steps: Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH. 2. To activate traffic-based BE service rate adjustment, perform the following steps: (1) Run the BSC6900 MML command MOD UTYPRABDCCCMC to set the following event 4A and 4B parameters: Direction Event4AThd Event4BThd TimetoTrigger4A
TimetoTrigger4B PendingTime4A PendingTime4B (2) Run the BSC6900 MML command SET UDCCC to set the following RNClevel DCCC algorithm parameters: DcccStg UlRateUpAdjLevel UlRateDnAdjLevel DlRateUpAdjLevel DlRateDnAdjLevel UlDcccRateThd DlDcccRateThd UlMidRateCalc DlMidRateCalc UlMidRateThd DlMidRateThd 3. To activate throughput-based BE service rate adjustment, perform the following steps: (1) Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic Resource Allocation Switch to DRA_THROUGHPUT_DCCC_SWITCH. (2) Run the BSC6900 MML command SET UDCCC. In this step, set DCH Throu Meas Period and HSUPA DCCC strategy. (3) Run the BSC6900 MML command MOD UTYPRABDCCCMC to set the following event 4B parameters for the DCH: Period Amount to trigger 4B on DCH Period Amount after trigger 4B on DCH 4. To activate link-stability-based BE service rate adjustment, perform the following steps: (1) Run the BSC6900 MML command SET UQOSACT to set the RNC-level QoS enhancement algorithm parameters. The parameters for ensuring link stability are: QOS Switch for BE Traffic First Action for BE Uplink QOS Second Action for BE Uplink QOS Third Action for BE Uplink QOS Wait Timer for BE Uplink Rate First Action for BE Downlink QOS Second Action for BE Downlink QOS Third Action for BE Downlink QOS Indicator for BE Uplink QOS Event Srnc Parameter for BE Downlink RLC QOS DRNC Parameter for BE Downlink RLC QOS
Measurement of 6A1 Switch Measurement of 5A Switch Measurement of 6D Switch (2) Run the BSC6900 MML command SET UQUALITYMEAS to set the RNClevel QoS measurement parameters. The parameters for ensuring link stability are: BE Trigger Time 6A1 BE Trigger Time 6B1 BE Trigger Time 6A2 BE Trigger Time 6B2 BE Trigger Time 6D UL Measurement Filter Coefficient DL TCP Measurement Filter Coefficient BE Trigger Time of Event E BE Reporting Period Unit for Event E BE Event E Reporting Period or BE Event E Reporting Period minute BE Trigger Time of Event F BE Reporting Period Unit for Event F BE Event F Reporting Period or BE Event F Reporting Period minute (3) Run the BSC6900 MML command MOD UCELLCAC to set the cell-level Call Admission Control (CAC) algorithm parameters. The parameters for ensuring link stability are: Max UL TX power of interactive service Max UL TX power of background service
NOTE
The BSC6900 defines default values for Max UL TX power of interactive service and Max UL TX power of background service. Retain the default values in normal situations.
(4) Run the BSC6900 MML command MOD UCELLRLPWR to set the cell-level downlink transmit power parameters. (5) Run the BSC6900 MML command MOD UCELLQUALITYMEAS to set the cell-level QoS measurement parameters. The parameters for ensuring link stability are: BE Trigger Time 6A1 BE Trigger Time 6B1 BE Trigger Time 6A2 BE Trigger Time 6B2 BE Trigger Time 6D BE Trigger Time of Event E BE Reporting Period Unit for Event E BE Event E Reporting Period BE Trigger Time of Event F
BE Reporting Period Unit for Event F BE Event E Reporting Period

NOTE
The BSC6900 defines default values for the preceding parameters. Retain the default values in normal situations.
(6) Run the BSC6900 MML command MOD UTYPRABQUALITYMEAS to set the following typical parameters for QoS measurement: Uplink Event 6A1 Relative Threshold Uplink Event 6A2 Relative Threshold Uplink Event 6B1 Relative Threshold Uplink Event 6B2 Relative Threshold Statistic Block Number for 5A Event Event 5A Threshold Event 5A Interval Block Number Event Ea Relative Threshold Event Eb Relative Threshold (7) Run the BSC6900 MML command MOD UTYPRABRLC to set Radio Link Control (RLC) parameters for a typical Radio Access Bearer (RAB). The parameters for ensuring link stability are: Re-TX monitor period Event A threshold Hysteresis of Event A Event A pending time after trigger Filter Coefficient of RLC Retransmission Ratio
NOTE
The BSC6900 defines default values for the preceding parameters. Retain the default values in normal situations.
(8) Link stability control for BE services is implemented through Inter-frequency handover. a. b. Run the BSC6900 MML command MOD UCELLHOCOMM. In this step, set Inter-Frequency and Inter-RAT Coexist Switch to INTERFREQ. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set HandOver Switch to HO_INTER_FREQ_HARD_HO_SWITCH.
(9) To configure inter-RAT handover for the link stability of BE services, perform the following steps: a. Run the BSC6900 MML command MOD UCELLHOCOMM. In this step, set Inter-Frequency and Inter-RAT Coexist Switch to INTERRAT and Inter-RAT PS Handover Switch to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set HandOver Switch to HO_INTER_RAT_PS_OUT_SWITCH.
b.
(10) To configure inter-frequency handover and inter-RAT handover for the link stability of BE services, perform the following steps:
a.
Run the BSC6900 MML command MOD UCELLHOCOMM. In this step, set Inter-Frequency and Inter-RAT Coexist Switch to SIMINTERFREQRAT and Inter-RAT PS Handover Switch to ON. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set HandOver Switch to HO_INTER_FREQ_HARD_HO_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH.
b.
(11) Run the BSC6900 MML command SET UDCCC to set the following RNClevel DCCC algorithm parameters: Uplink Full Coverage Bit Rate Downlink Full Coverage Bit Rate (12) Run the BSC6900 MML command MOD UCELLDCCC to set the following cell-level DCCC algorithm parameters: Uplink Full Coverage Bit Rate Downlink Full Coverage Bit Rate
NOTE
For details about the settings of measurement control parameters, see 97 Configuring TTI Switch for BE Services Based on Coverage.
5.
Activating basic-congestion-based BE service rate adjustment (1) Run the BSC6900 MML command SET UUSERGBR to set the guaranteed bit rates (GBRs) for gold, silver, and copper users requesting interactive and background services. (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 RNClevel DCCC algorithm parameters: 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. In this step, turn on the following switches of Dynamic Resource Allocation Switch: 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 must be activated before the HSDPA state transition switch is turned on.
2. 3.
Run the BSC6900 MML command SET UUESTATETRANS to set the measurement control parameters of the UE state transition algorithm. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the timer parameters of the UE state transition algorithm.
Issue 02 (2011-07-11)
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 timer parameters for checking the low activity of PS users: Conversational service T1 Streaming service T1 Interactive service T1 Background service T1 IMS signal T1 Conversational service T2 Streaming service T2 Interactive service T2 Background service T2 IMS signal T2
Activating always online 1.
Verifying DCCC 1. Traffic-based BE service rate adjustment Set up an R99 BE service. Check whether the information element (IE) trafficVolumeMeasurement exists in the RRC_MEAS_CTRL message traced on the Uu interface, as shown in Figure 15-1. In addition, check whether the value of the IE periodicalOrEventTrigger is eventTrigger (1), as shown in Figure 15-2. Figure 15-1 IE trafficVolumeMeasurement
Figure 15-2 IE periodicalOrEventTrigger
2.
Throughput-based BE service rate adjustment (1) On the BSC6900 LMT, open the Monitor window. In the Monitor tab page, double-click UMTS Monitoring > Connection Performance Monitoring. Create UL Throughput Bandwidth and DL Throughput Bandwidth monitoring tasks.
15-6
Issue 02 (2011-07-11)
(2) Set up an R99 BE service and maintain the service without data operations. In the Connection Performance Monitoring tab page, you can view the bandwidth reduction in UL Throughput Bandwidth. 3. Link-stability-based BE service rate adjustment Set up an R99 BE service. Check whether the value of measurementQuantity in the RRC_MEAS_CTRL message traced on the Uu interface is ue-TransmittedPower (0), as shown in Figure 15-3. In addition, check whether the value of the IE periodicalOrEventTrigger is eventTrigger (1), as shown in Figure 15-4. Figure 15-3 IE measurementQuantity
Figure 15-4 IE periodicalOrEventTrigger
4.
Basic-congestion-based BE service rate adjustment (1) On the BSC6900 LMT, open the Monitor window. In the Monitor tab page, double-click UMTS Monitoring > Connection Performance Monitoring. Create UL Throughput Bandwidth and DL Throughput Bandwidth monitoring tasks. (2) Set up an R99 BE service. Run the BSC6900 MML command DSP UCELLCHK to check the cell congestion status on the Uu interface (the cell is in the basic congestion state). You can view the bandwidth decrease in UL Throughput Bandwidth in the Connection Performance Monitoring tab page.
Verifying the UE state transition algorithm Set up an R99 BE service and maintain the service without data operations. Check whether the value of rrc-StateIndicator in the traced RRC_RB_RECFG message is cell-FACH (1), as shown in Figure 15-5. Figure 15-5 IE rrc-StateIndicator
Verifying always online Set up an R99 BE service and maintain the service without data operations. The message RRC_RB_REL is not traced on the Uu interface.
l
Issue 02 (2011-07-11)
1. 2. ----End
Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the related switches. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH.
Example
//Activating DCCC //Activating the DCCC algorithm SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1; //Activating traffic-based BE service rate adjustment MOD UTYPRABDCCCMC: RabIndex=1, Direction=DOWNLINK, Event4aThd=D1024, Event4bThd=D16, TimetoTrigger4A=D240, PendingTime4A=D4000, TimetoTrigger4B=D2560, PendingTime4B=D4000; SET UDCCC: UlDcccRateThd=D64, DlDcccRateThd=D64, DcccStg=RATE_UP_AND_DOWN_ON_DCH, UlRateUpAdjLevel=3_Rates, UlRateDnAdjLevel=3_Rates, UlMidRateCalc=HAND_APPOINT, UlMidRateThd=D128, DlRateUpAdjLevel=3_Rates, DlRateDnAdjLevel=3_Rates, DlMidRateCalc=HAND_APPOINT, DlMidRateThd=D128; //Activating throughput-based BE service rate adjustment SET UCORRMALGOSWITCH: DraSwitch=DRA_THROUGHPUT_DCCC_SWITCH-1; SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH, DchThrouMeasPeriod=100; MOD UTYPRABDCCCMC: RabIndex=1, Direction=UPLINK, Event4bThd=D64, DchThrouTimetoTrigger4B=2, DchThrouPendingTime4B=16; SET UUESTATETRANS: E2FThrouMeasPeriod=30; //Activating link-stability-based BE service rate adjustment //Setting the QoS-related parameters SET UQOSACT: BEQosPerform=YES, BeUlAct1=RateDegrade, BeUlAct2=InterFreqHO, BeUlAct3=InterRatHO, BeDlAct1=RateDegrade, BeDlAct2=InterFreqHO, BeDlAct3=InterRatHO, BeUlEvTrigInd=SINGLE, SrncBeDlRlcQosSwitch=YES, DrncBeDlRlcQosSwitch=YES, BeUlQos6A1McSwitch=YES, BeUlQos5AMcSwitch=YES, BeUlQos6DMcSwitch=YES; SET UQUALITYMEAS: UlBeTrigTime6A1=D640, UlBeTrigTime6B1=D2560, UlBeTrigTime6A2=D1280, UlBeTrigTime6B2=D1280, UlBeTrigTime6D=D240, UlMeasFilterCoef=D19, DlMeasFilterCoef=D1, DlBeTrigTimeE=64, ChoiceRptUnitForBeE=TEN_MSEC, TenMsecForBeE=480, DlBeTrigTimeF=64, ChoiceRptUnitForBeF=TEN_MSEC, TenMsecForBeF=480; MOD UCELLRLPWR: CellId=1, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200, RLMAXDLPWR=-30, RLMINDLPWR=-180, DLSF=D128; MOD UTYPRABQUALITYMEAS: RabIndex=1, UlThd6a1=1, UlThd6a2=5, UlThd6b1=1, UlThd6b2=5, StaBlkNum5A=500, Thd5a=280, HangBlockNum5a=512, ThdEa=2, ThdEb=2; MOD UTYPRABRLC: RabIndex=1, SubflowIndex=0, TrchType=TRCH_DCH, OppositeTrchType=TRCH_DCH, DelayClass=1, RlcMode=AM, AmRlcCfgPara=FLOWCONTROL_PARA, TimeToMoniter=6000, MoniterPrd=1000, ReTransRatioFilterCoef=1, EventAThred=160, TimeToTriggerA=2, PendingTimeA=1; //Configuring inter-frequency handover for the link stability of BE services MOD UCELLHOCOMM: CellId=1, InterFreqRATSwitch=INTERFREQ, CoexistMeasThdChoice=COEXIST_MEAS_THD_CHOICE_INTERFREQ, CSServiceHOSwitch=OFF, PSServiceHOSwitch=OFF; SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1; //Configuring inter-RAT handover for the link stability of BE services MOD UCELLHOCOMM: CellId=1, InterFreqRATSwitch=INTERRAT, CoexistMeasThdChoice=COEXIST_MEAS_THD_CHOICE_INTERFREQ, CSServiceHOSwitch=OFF, PSServiceHOSwitch=ON; SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_OUT_SWITCH-1; //Setting the DCCC algorithm parameters
15-8
Issue 02 (2011-07-11)
SET UDCCC: UlFullCvrRate=D64, DlFullCvrRate=D64; MOD UCELLDCCC: CellId=1, UlFullCvrRate=D64, DlFullCvrRate=D64; //Activating basic-congestion-based BE service rate adjustment SET UUSERGBR: TrafficClass=INTERACTIVE, THPClass=High, BearType=R99, UserPriority=GOLD, UlGBR=D16, DlGBR=D16; SET UEDCHRATEADJUSTSET: EdchRateAdjustSet=RATE_144KBPS-1&RATE_384KBPS-1&RATE_1280KBPS-1; SET UDCCC: FailTimeTh=4, MoniTimeLen=60, DcccUpPenaltyLen=30; //Activating the UE state transition algorithm 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, PsInactTmrForBac=240, ProtectTmrForBac=10, PsInactTmrForCon=240, ProtectTmrForCon=10,PsInactTmrForStr=240, ProtectTmrForStr=10, PSInactTmrForImsSig=3600, ProtectTmrForImsSig=10; //Deactivating DCCC SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-0;
Issue 02 (2011-07-11)
15-9
16 Configuring Integrity Protection
16
Prerequisite
l l l License
Configuring Integrity Protection
This section describes how to activate, verify, and deactivate the basic feature WRFD-011401 Integrity Protection.
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
16 Configuring Integrity Protection
Example
//Activating integrity protection SET UUIA: IntegrityProtectAlgo=UIA1-1;
16-2
Issue 02 (2011-07-11)
17 Configuring Encryption
17
Prerequisite
l l l Dependencies on Hardware License
Configuring Encryption
This section describes how to activate, verify, and deactivate the basic feature WRFD-011402 Encryption.
This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. This feature is not under license control.
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
5. 6.
Issue 02 (2011-07-11)
17 Configuring Encryption
chosenEncryptionAlgorithm IE of the latter message indicates the encryption algorithm. l Deactivation Procedure 1. ----End This feature does not need to be deactivated.
Example
//Activating encryption SET UUEA: EncryptionAlgo=UEA0-1&UEA1-1;
17-2
Issue 02 (2011-07-11)
18 Configuring Open Loop Power Control
18
Prerequisite
Configuring Open Loop Power Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020501 Open Loop Power Control.
l l l
Context
This feature enables BSC6900 to roughly estimate path loss based on power measurement results, network parameter settings, and QoS requirements. Based on the estimation results, BSC6900 sets the initial transmit power for a UE and a NodeB before connection is established between them.
Procedure
l Activation Procedure Activate open loop power control on the downlink DPCH. 1. This feature does not need to be activated on the downlink DPCH.
Activate open loop power control on the uplink DPCH. 1. Run the BSC6900 MML command SET UFRC. In this step, set the parameters related to uplink DPCH power control.
Issue 02 (2011-07-11)
18-1

NOTE
l The BSC6900 uses the Default Constant Value parameter to calculate the power offset on the uplink DPCCH (DPCCH_Power_offset). Based on the calculation result, the UE calculates the initial transmit power on the uplink DPCCH (DPCCH_Initial_Power). l The formula for calculating DPCCH_Power_offset is: DPCCH_Power_offset = Primary CPICH DL TX power + UL interference + Default Constant Value. Where, DPCCH_Power_offset indicates the initial transmit power offset on the DPCCH, Primary CPICH DL TX power indicates the downlink transmit power on the P-CPICH, UL interference indicates the uplink interference, and Default Constant Value is the value of Default Constant Value. l The formula for calculating DPCCH_Initial_Power is: DPCCH_Initial_Power = DPCCH_Power_offset - CPICH_RSCP. Where, CPICH_RSCP indicates the received signal code power (RSCP) that the UE measures on the P-CPICH. An excessively small value of DPCCH_Power_offset may lead to uplink synchronization failures at the cell edge during initial link establishment, which affects uplink coverage. An excessively great value of DPCCH_Power_offset may lead to instantaneous interference on uplink signal reception, which affects the uplink receiving performance. For details, see 3GPP TS 25.331.
Activate open loop power control on the uplink PRACH. 1. l Run the BSC6900 MML command MOD UPRACHUUPARAS. In this step, set the parameters related to the PARCH to appropriate values.
Verification Procedure Verify open loop power control on the downlink DPCH 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 IE initialDL-transmissionPower. This value is used for the downlink DPCH open loop power control.
Verify open loop power control on the uplink DPCH 1. Check the IE dpcch-PowerOffset, whose value is the same as that of DPCCH Power Offset, under the IE ul-DPCH-PowerControlIonfo contained in the RRC message Radio Bearer Setup, as shown in Figure 18-1. Based on the dpcch-PowerOffset value, the UE can further calculate the initial transmit power on the uplink DPCCH (DPCCH_Initial_Power) and perform uplink open loop power control. Figure 18-1 ul-DPCH-PowerControlIonfo IE
Verify open loop power control on the uplink PRACH 1. Check whether the IE constantValue whose value is -20 is contained in the RRC_SYS_INFO_TYPE5 message by referring to Tracing Messages on the Uu Interface. If the message contains this IE, parameters configured for the UE take effect. After obtaining values of these parameters, the UE calculates the initial transmit power and performs open look power control on the uplink PARCH.
l
18-2
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-07-11)
1. ----End
This feature does not need to be deactivated.
Example
//Activating open loop power control on the uplink DPCH SET UFRC: DefaultConstantValue=-22; //Activating open loop power control on the uplink PRACH MOD UPRACHUUPARAS: CellId=111, PhyChId=1, Constantvalue=-20, PowerRampStep=2, PreambleRetransMax=20;
Issue 02 (2011-07-11)
18-3
19 Configuring Downlink Power Balance
19
Prerequisite
l l l
Configuring Downlink Power Balance
This section describes how to activate, verify, and deactivate the basic feature WRFD-020502 Downlink Power Balance.
Context
In soft handover, error codes in a TPC command may lead to downlink transmit power drift. The downlink power balance feature solves the problem of power imbalance between links, thereby achieving best gain in soft handover. The greater the downlink transmit power drift, the smaller the macro diversity gain. Downlink power balance adjusts power drift and improves performance of soft handover.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Power Control Switch to PC_DOWNLINK_POWER_BALANCE_SWITCH. On the BSC6900 LMT, choose Trace > UMTS Services and double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed. Set Cell Config, Uu Message Type, and Save File. Then click Submit. Move a UE from cell 1 to cell 2 to ensure that the UE performs a soft handover. Check whether the active cell set update is complete in the traced Uu-interface messages. Figure 19-1 shows the expected result.
Issue 02 (2011-07-11)
Figure 19-1 RRC_ACTIVE_SET_UPDATE_CMP message traced in Uu interface message tracing
5.
Start Iub interface message tracing on the BSC6900 LMT. Check the value of the information element dedicatedMeasurementType in the NBAP_DEDIC_MEAS_INIT_REQ message. Expected result: the value of dedicatedMeasurementType is transmitted-codepower(2) shown in Figure 19-2.
19-2
Issue 02 (2011-07-11)
Figure 19-2 Information element dedicatedMeasurementType
Issue 02 (2011-07-11)
19-3
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set PC_DOWNLINK_POWER_BALANCE_SWITCH to 0.
----End
Example
//Activating downlink power balance SET UCORRMALGOSWITCH: PcSwitch=PC_DOWNLINK_POWER_BALANCE_SWITCH-1; //Deactivating downlink power balance SET UCORRMALGOSWITCH: PcSwitch=PC_DOWNLINK_POWER_BALANCE_SWITCH-0;
19-4
Issue 02 (2011-07-11)
20 Configuring Outer Loop Power Control
20
Prerequisite
Configuring Outer Loop Power Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020503 Outer Loop Power Control.
l l l
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. Optional: Run the BSC6900 MML command MOD UTYPRABOLPC to set the parameters related to OLPC according to network plan. Click the Monitor on the BSC6900 LMT main page. On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > Connection Performance Monitoring. The Connection Performance Monitoring dialog box is displayed. In the displayed dialog box, set Monitor Item to UL SIR and OLPC, and enter the corresponding IMSI. And then click Submit to initiate the trace.
Issue 02 (2011-07-11)
2. 3.
Use a UE to initiate a PS service. Check whether the values of UL SIR and OLPC are changed. If the values are changed, this feature is activated.
Figure 20-1 UL SIR
Figure 20-2 OLPC
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to deactivate the OLPC function.
----End
Example
//Activating outer loop power control SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_SWITCH-1; MOD UTYPRABOLPC: RabIndex=11, SubflowIndex=0, TrchType=TRCH_DCH,
20-2
Issue 02 (2011-07-11)
DelayClass=1, BLERQuality=-20; MOD UTYPRABOLPC: RabIndex=55, SubflowIndex=0, TrchType=TRCH_EDCH_10MS, DelayClass=1, EdchTargetLittleRetransNum=10, EdchTargetLargeRetransNum=1100; MOD UTYPRABHSUPAPC: RabIndex=55, SubflowIndex=0, TrchType=TRCH_EDCH_10MS, Ul16QamInd=FALSE, UlL2EnhanceInd=FALSE, EdPwrInterpolationInd=FALSE, MaxSirtarget=192, MinSirtarget=112, UlEcBoostingInd=FALSE; //Deactivating outer loop power control SET UCORRMALGOSWITCH: PcSwitch=PC_OLPC_SWITCH-0;
Issue 02 (2011-07-11)
20-3
21 Configuring Inner Loop Power Control
21
Prerequisite
Configuring Inner Loop Power Control

This section describes how to activate, verify, and deactivate the basic feature WRFD-020504 Inner Loop Power Control.
l l l
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. The feature does not need to be activated. Click the Monitor on the BSC6900 LMT main page. On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > Connection Performance Monitoring. The Connection Performance Monitoring dialog box is displayed. In the displayed dialog box, set Monitor Item to UL SIR and UE Tx Power, and enter the corresponding IMSI. And then click Submit to initiate the trace. UE 1 calls UE 2. UE 2 rings, answers and starts the conversation. Observe the variation of UL SIR and UE Tx Power in the UL SIR and UE Tx Power Connection Performance Monitoring window. UE 1 moves in the cell to change radio link quality. When you move UE 1 away from the cell center, UE_1 transmit power increases.
Verification Procedure
2. 3. 4. 5.
Issue 02 (2011-07-11)
21 Configuring Inner Loop Power Control
6.
When you move UE_1 towards cell center, UE_1 transmit power decreases.
Figure 21-1 UL SIR Tracing
Figure 21-2 UE Tx Power Tracing
----End
21-2
Issue 02 (2011-07-11)
22 Configuring Admission Control
22
Prerequisite
l l l License
Configuring Admission Control
This section describes how to activate, verify, and deactivate the basic feature WRFD-020101 Admission Control.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. This feature is not under license control.
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. Activating code resource admission Run the BSC6900 MML command MOD UCELLCAC with Dl handover credit and code reserved SF set to an appropriate value. 2. Activating power resource admission (1) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select associated cell-oriented power admission control algorithms from the Cell CAC algorithm switch drop-down list, and select an appropriate algorithm from both the Uplink CAC algorithm switch and Downlink CAC algorithm switch drop-down lists according to the network plan. (2) Run the BSC6900 MML command MOD UCELLCAC to set power resource admission parameters to appropriate values. 3.
Issue 02 (2011-07-11)
Activating NodeB credit resource admission

(1) Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, select NODEB_CREDIT_CAC_SWITCH from the CAC algorithm switch drop-down list to turn on the NodeB-level CE admission switch. (2) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select CRD_ADCTRL from the Cell CAC algorithm switch drop-down list to turn on the NodeB-level credit admission switch. (3) Run the BSC6900 MML command MOD UCELLCAC. In this step, set UL handover credit reserved SF to an appropriate value. 4. l Activating Iub resource admission This feature does not need to be activated. Verification Procedure The procedure for verifying downlink admission control on R99 non-real-time PS services based on the number of equivalent subscribers is as follows: 1. 2. 3. 4. Enable a UE in the idle state to camp on CELL_A11. Set the PS service type to interactive on the HLR. Run the BSC6900 MML command MOD UCELLCAC. In this step, set DL total equivalent user number of CELL_A11 to 1. Connect the UE to a laptop through the USB port and initiate a PS service. Expected result: The UE fails to initiate the PS service. In the Iu Interface Trace window, an RANAP_RAB_ASSIGNBMENT_RESP message sent from the RNC to the CN is displayed, containing the cause value no-radio-resources-available-intarget-cell. 5. 6. l Run the BSC6900 MML command MOD UCELLCAC. In this step, set DL total equivalent user number of CELL_A11 to 80. Connect the UE to a laptop through the USB port and initiate a PS service. Expected result: The data service is set up successfully. Deactivation Procedure 1. 2. Deactivating code resource admission This feature does not need to be deactivated. Deactivating power resource admission Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Uplink CAC algorithm switch and Downlink CAC algorithm switch to ALGORITHM_OFF. 3. Deactivating NodeB credit resource admission (1) Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, deselect NODEB_CREDIT_CAC_SWITCH from the CAC algorithm switch drop-down list. (2) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect CRD_ADCTRL from the Cell CAC algorithm switch drop-down list. 4. Deactivating Iub resource admission This feature does not need to be deactivated. ----End
Example
//Activating code resource admission MOD UCELLCAC: CellId=11, UlNonCtrlThdForAMR=75, UlNonCtrlThdForNonAMR=75, UlNonCtrlThdForOther=60, DlConvAMRThd=80, DlConvNonAMRThd=80, DlOtherThd=75, UlNonCtrlThdForHo=80, DlHOThd=85, UlCellTotalThd=83, DlCellTotalThd=90, DlHoCeCodeResvSf=SF32; //Activating power resource admission MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1&HSDPA_GBP_MEAS-1&HSDPA_PBR_MEAS-1; MOD UCELLCAC: CellId=11, MaxHsdpaUserNum=64, MaxUlTxPowerforConv=24, MaxUlTxPowerforInt=24; //Activating NodeB credit resource admission SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-1; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=CRD_ADCTRL-1; MOD UCELLCAC: CellId=11, UlHoCeResvSf=SF16; //Deactivating power resource admission MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_OFF, NBMDlCacAlgoSelSwitch=ALGORITHM_OFF; //Deactivating NodeB credit resource admission SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-0; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=CRD_ADCTRL-0;
Issue 02 (2011-07-11)
22-3
23 Configuring Load Measurement
23
Prerequisite
l l l License
Configuring Load Measurement
This section describes how to activate, verify, and deactivate the basic feature WRFD-020102 Load Measurement.
Context
This feature is used to measure the load for the load control feature.
Procedure
l Activation Procedure 1. 2. The function of measurement on RTWP, TCP, and non-HSPA power is always activated. Therefore, this feature does not need to be activated. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select HSDPA_PBR_MEAS and HSUPA_PBR_MEAS from the Cell CAC algorithm switch drop-down list to activate the cell-level load measurement for HSDPA and HSUPA. Run the BSC6900 MML command MOD UCELLLDM. In this step, set load monitoring parameters, including the uplink/downlink load reshuffling (LDR) algorithm trigger/release thresholds and uplink/downlink overload congestion (OLC) algorithm trigger/release thresholds to appropriate values. Run the BSC6900 MML command SET ULDM. In this step, set parameters associated with load measurement, report period, and smoothing filter length according to the network plan.
3.
4.
l
Issue 02 (2011-07-11)
23 Configuring Load Measurement
1.
On the BSC6900 LMT, open the Monitor page. In the Monitor navigation tree, double-click UMTS Monitoring > Cell Performance Monitoring, and create tasks of monitoring Cell DL Carrier TX Power and RTWP. Check whether the uplink full-bandwidth RX power of the cell is displayed in the RTWP monitoring window. Check whether the downlink carrier TX power is displayed in the Cell DL Carrier TX Power monitoring window. The measurement on RTWP, TCP, and non-HSPA power has been activated and cannot be deactivated. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect HSDPA_PBR_MEAS and HSUPA_PBR_MEAS from the Cell CAC algorithm switch drop-down list to deactivate the cell-level load measurement for HSDPA and HSUPA.
2. 3. l
Deactivation Procedure 1. 2.
----End
Example
//Activating load measurement MOD UCELLALGOSWITCH: CellId=100, NBMCacAlgoSwitch=HSDPA_PBR_MEAS-1&HSUPA_PBR_MEAS-1; MOD UCELLLDM: CellId=1, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70, DlLdrRelThd=60, UlOlcTrigThd=95, UlOlcRelThd=85, DlOlcTrigThd=95, DlOlcRelThd=85, HsupAuRetrnsLdTrigThd=70, HsupAuRetrnsLdRelThd=50; SET ULDM: UlBasicCommMeasFilterCoeff=D6, ChoiceRprtUnitForUlBasicMeas=TEN_MSEC, TenMsecForUlBasicMeas=100, DlBasicCommMeasFilterCoeff=D6; //Deactivating load measurement MOD UCELLALGOSWITCH: CellId=100, NBMCacAlgoSwitch=HSDPA_PBR_MEAS-0&HSUPA_PBR_MEAS-0;
23-2
Issue 02 (2011-07-11)
24 Configuring Load Reshuffling
24
Prerequisite
l l l License
Configuring Load Reshuffling
This section describes how to activate, verify, and deactivate the basic feature WRFD-020106 Load Reshuffling.
Context
This feature provides multiple load reshuffling policies for a cell in the basic congestion state to decrease the cell load and increase the access success rate. The load reshuffling policies are inter-frequency load handover, code reshuffling, BE service rate reduction, uncontrolled realtime traffic QoS renegotiation, CS domain inter-RAT load handover, PS domain inter-RAT load handover, downsizing the bit rate of AMR voice, and MBMS power downgrading.
Procedure
l Activation Procedure
NOTE
The following section provides the related parameters and commands. The parameter settings depend on the network plan.
1.
Enable the related load reshuffling algorithms. (1) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, turn on the following switches of Cell LDC algorithm switch: 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
Issue 02 (2011-07-11)
24-1
(2) Run the BSC6900 MML command MOD UNODEBALGOPARA. In this step, turn on the following switches of NodeB LDC algorithm switch: IUB_LDR: NodeB Iub reshuffling algorithm NODEB_CREDIT_LDR: NodeB-level credit reshuffling algorithm LCG_CREDIT_LDR: cell-group-level credit reshuffling algorithm 2. Set the related thresholds. Run the BSC6900 MML command MOD UCELLLDM to set 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) and LDR actions. Run the BSC6900 MML command MOD UNODEBLDR to set the cell-grouplevel or NodeB-level LDR thresholds (Ul/DL LDR Credit SF reserved threshold). Run the BSC6900 MML command MOD UCELLLDR to set the cell-level credit LDR thresholds (Ul/DL LDR Credit SF reserved threshold). 3. 4. Run the BSC6900 MML command SET ULDCPERIOD to set the LDR period (LDR period timer length). Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the functions used in the LDR actions. Inter-frequency load handover Set HandOver Switch to HO_ALGO_LDR_ALLOW_SHO_SWITCH. BE service rate reduction Set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH. Uncontrolled real-time traffic QoS renegotiation Set Dynamic Resource Allocation Switch to DRA_IU_QOS_RENEG_SWITCH. CS domain inter-RAT load handover Set HandOver Switch to HO_INTER_RAT_CS_OUT_SWITCH. PS domain inter-RAT load handover Set HandOver Switch to HO_INTER_RAT_PS_OUT_SWITCH. Downsizing the bit rate of AMR voice Set CS Algorithm Switch to CS_AMRC_SWITCH. l Verification Procedure The following section takes R99 non-real-time data services as examples to verify BE service rate reduction in the basic congestion state. 1. 2. Enable a UE in idle mode to camp on CELL_A11. On the BSC6900 LMT, open the Monitor tab page. In the Monitor Navigation Tree tab page, double-click UMTS Monitoring > Cell Performance Monitoring. In the displayed dialog box, create a Cell DL Throughput monitoring task. Connect the UE to a laptop through the USB port and initiate a data service. Check the rb-mappinginfo information element (IE) contained in the RRC_RB_SETUP message traced over the Uu interface. The value of rrc-Stateinditator is CELL_DCH. Use the UE to log in to the FTP server and then start FTP downloading. Data downloading is normal.
3.
4.
24-2
5.
To simulate the scenario where power load reaches 75%, run the NodeB MML command STR DLSIM. The RRC_RB_RECFG message is displayed in the Uu Interface Trace dialog box. In the Cell DL Throughput of the Connection Performance Monitoring dialog box, you can view the downlink RB rate decrease configured on the RNC. To stop simulating power load, run the NodeB MML command STP DLSIM. In the Uu Interface Trace dialog box, the RRC_RB_RECFG message is displayed. In the Cell DL Throughput of the Connection Performance Monitoring dialog box, you can view the downlink RB rate increase configured on the RNC. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect the following switches from Cell LDC algorithm switch: 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
6.
2.
Run the BSC6900 MML command MOD UNODEBALGOPARA. In this step, deselect the following switches from NodeB LDC algorithm switch: 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 //Enabling load reshuffling algorithms MOD UCELLALGOSWITCH: CellId=100, NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR1; MOD UNODEBALGOPARA: NodeBName="nodeb1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1; //Setting load reshuffling thresholds MOD UCELLLDM: CellId=100, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70, DlLdrRelThd=60, UlOlcTrigThd=95, UlOlcRelThd=85, DlOlcTrigThd=95, DlOlcRelThd=85, DlLdTrnsHysTime=1000; //Setting code reshuffling thresholds MOD UCELLLDR: CellId=100, DlLdrFirstAction=CodeAdj, DlLdrSecondAction=InterFreqLDHO, CellLdrSfResThd=SF8; //Setting NodeB-level credit reshuffling thresholds MOD UNODEBLDR: NodeBName="nodeb1", UlLdrCreditSfResThd=SF8, DlLdrCreditSfResThd=SF8; //Setting cell-level credit reshuffling thresholds MOD UCELLLDR: CellId=100, UlLdrCreditSfResThd=SF8, DlLdrCreditSfResThd=SF8; //Setting load reshuffling period SET ULDCPERIOD: LDRPERIODTIMERLEN=10; //Turning on load reshuffling function switches SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1&DRA_IU_QOS_RENEG_SWITCH-1,CsSwitch=CS_AMRC_SW ITCH-1, HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1&HO_I NTER_RAT_PS_OUT_SWITCH-1;
Issue 02 (2011-07-11)
24-3
//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;
24-4
Issue 02 (2011-07-11)
25 Configuring Overload Control
25
Prerequisite
l l l License
Configuring Overload Control
This section describes how to activate, verify, and deactivate the basic feature WRFD-020107 Overload Control.
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 air interface OLC algorithm. Select the UL_UU_OLC and DL_UU_OLC check boxes under the parameter Cell CAC algorithm. Run the BSC6900 MML command MOD UNODEBALGOPARA to enable the OLC algorithm. Select the IUB_OLC check box under the parameter NodeB LDC algorithm. Run the BSC6900 MML command MOD UCELLLDM to set UL OLC trigger threshold, DL OLC trigger threshold, UL OLC release threshold, and DL OLC release threshold. Run the BSC6900 MML command SET ULDCPERIOD to set the OLC period (OLC period timer value). Run the BSC6900 MML command ADD UCELLOLC to set the parameter related to OLC-related actions. Run the following BSC6900 MML commands to verify whether the activation is successful.
2.
3.
4. 5. l
Issue 02 (2011-07-11)
25 Configuring Overload Control
LST UCELLALGOSWTICH LST UCELLLDM LST UNODEBALGOPARA LST ULDCPERIOD LST UCELLOLC
NOTE
Consult Huawei engineers about the verification solution to obtain professional technical support.
NOTE
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to dienable the air interface OLC algorithm. Clear the UL_UU_OLC and DL_UU_OLC check boxes under the parameter Cell CAC algorithm. Run the BSC6900 MML command MOD UNODEBALGOPARA to disenable the OLC algorithm, Clear the IUB_OLC check box under the parameter NodeB LDC algorithm.
2.
----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; SET ULDCPERIOD: OlcPeriodTimerLen=3000; ADD UCELLOLC: CellId=111; //Deactivating Overload Control MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_OLC-0&DL_UU_OLC-0; MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-0;
25-2
Issue 02 (2011-07-11)
26 Configuring Code Resource Management
26
Prerequisite
l l l
Configuring Code Resource Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-020108 Code Resource Management.
Context
This feature provides downlink code tree allocation and reshuffling. Through this, the code resources can be rationally allocated, therefore increasing the utilization efficiency of the resources.
Procedure
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, and then enable the required LDR algorithm switches for resources (CELL_CODE_LDR(Code LDR Algorithm)) through setting the Cell LDC algorithm switch parameter. Run the BSC6900 MML command MOD UCELLLDR to set code LDR threshold (Cell LDR SF reserved threshold) and set CodeAdj(Code adjust) 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).
2.
3.
Issue 02 (2011-07-11)
26 Configuring Code Resource Management
Verification Procedure 1. 2. 3. 4. Enable the UE in the idle state to camp on CELL_A11. Set the PS service type to interactive on the HLR. Run the BSC6900 MML command MOD UCELLLDR with Cell LDR SF reserved threshold set to SF8 and Max user number for code adjust to 1. Connect the UE to a laptop on the USB port and enable the UE to initiate a data service. Expected result: Services are set up on the DCH successfully. You can view the rbmappinginfo information element (IE) in the RRC_RB_SETUP message traced over the Uu interface. In the Cell Code Tree Monitor window, you can view that the service occupies code SF32(4). Enable the UE to log in to the FTP Internet server and then enable FTP download. Run the BSC6900 MML command DSP UCELLCHK to check the cell health status. The status of cell code congestion is displayed as basic congestion. Run the BSC6900 MML command RMV URESERVEOVSF to release the service that occupies code SF32(1). Run the BSC6900 MML command DSP UCELLCHK to check the cell health status. The status of cell code congestion is displayed as not congested. Run the BSC6900 MML command MOD UCELLALGOSWITCH, and then deactivate the required LDR algorithm switches for resources (CELL_CODE_LDR (Code LDR Algorithm)) through setting the Cell LDC algorithm switch parameter.
5. 6. 7. 8. l
----End
Example
//Activating Code Resource Management MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=CELL_CODE_LDR-1; MOD UCELLLDR: CellId=111, DlLdrFirstAction=CodeAdj, CellLdrSfResThd=SF8; SET ULDCPERIOD: LdrPeriodTimerLen=10; //Verifying Code Resource Management MOD UCELLLDR: CellId=111, CellLdrSfResThd=SF8, MaxUserNumCodeAdj=1; DSP UCELLCHK: CHECKSCOPE=CELLID, CELLID=111; RMV URESERVEOVSF: CellId=111, DLOVSFSF=SF32, DLCODENO=1; //Deactivating Code Resource Management MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=CELL_CODE_LDR-0;
26-2
Issue 02 (2011-07-11)
27 Configuring Shared Network Support in Connected Mode
27
Prerequisite
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.
l l l l
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. 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
Issue 02 (2011-07-11)
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.
Verifying the SNA Function of the CS Service

1. 2. 3. 4. 5.
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. 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 of UE1 and SNA1 on the MSC. 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
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. 3. 4. Run the MML command ADD SNA on the SGSN to add SNA information. Run the BSC6900 MML command to disable the SNA function. 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; //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;
Issue 02 (2011-07-11)
27-3
28 Configuring Intra NodeB Softer Handover
28
Prerequisite
l l l
Configuring Intra NodeB Softer Handover
This section describes how to activate, verify, and deactivate the basic feature WRFD-020201 Intra NodeB Softer Handover.
Context
This feature enables softer handover within a NodeB. Intra-NodeB softer handover is one type of soft handover. To perform softer handover, multiple RLs need to be established. In this way, the uplink resources of a cell in the same uplink resource group can be fully shared. In contrast to soft handover, softer handover does not consume additional transmission resources on the Iub interface. Therefore, softer handover can provide higher combination gain and require less transmission resources on the Iub interface. Softer handover may occur within the same uplink resource group.
Procedure
l Activation Procedure 1. 2. 3. 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.
Issue 02 (2011-07-11)
28 Configuring Intra NodeB Softer Handover
4. l
Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter related to handover. 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. UE is in idle mode and camps on the CELL1. UE initiates PS Dial-up, and service is set up successfully. UE moves from CELL1 to CELL2, through the Trace Data, it can be observed RNC sends the RRC_ACTIVE_SET_UPDATE message to UE and UE sends the RRC_ACTIVE_SET_UPDATE_CMP message to RNC. The data transmission remains normal while UE is moving to CELL2. Run the BSC6900 MML command SET UHOCOMM to set Softer handover combination indicator switch to MUST_NOT.
Verification Procedure 1. 2. 3. 4. 5.
6. l 1. ----End
Example
//Activating Intra NodeB 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 NodeB Softer Handover SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0;
28-2
Issue 02 (2011-07-11)
29 Configuring Intra RNC Soft Handover
29
Prerequisite
l l l
Configuring Intra RNC Soft Handover
This section describes how to activate, verify, and deactivate the basic feature WRFD-020202 Intra RNC Soft Handover.
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. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu Interface Trace. The Uu Interface Trace dialog box is displayed.
Issue 02 (2011-07-11)
29 Configuring Intra RNC Soft Handover
2. 3. 4. 5.
Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then, click Submit. Both UE1 and UE2 are in idle mode and camp on the CELL1. UE1 calls UE2, and the conversation clear. UE1 moves from CELL1 to CELL2, through the Trace Data, it can be observed that RNC1 sends the RRC_ACTIVE_SET_UPDATE message to UE1, and UE1 sends the RRC_ACTIVE_SET_UPDATE_CMP message to RNC1. 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;
29-2
Issue 02 (2011-07-11)
30 Configuring Inter RNC Soft Handover
30
Prerequisite
l l l l
Configuring Inter RNC Soft Handover
This section describes how to activate, verify, and deactivate the optional feature WRFD-020203 Inter RNC Soft Handover.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. 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. 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 UEXT3GCELL to add a neighboring RNC cell.
Issue 02 (2011-07-11)
30 Configuring Inter RNC Soft Handover
4. 5. l
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. 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. Both UE1 and UE2 are in idle mode and camp on the CELL1. UE1 calls UE2, and the conversation clear. UE1 moves from CELL1 to CELL2, through the Trace Data, it can be observed that RNC1 sends the RRC_ACTIVE_SET_UPDATE message to UE1, and UE1 sends the RRC_ACTIVE_SET_UPDATE_CMP message to RNC1. 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; ADD UEXT3GCELL: NRncId=1, CellId=2381, CellHostType=SINGLE_HOST, CellName="2222", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1, UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700, TxDiversityInd=FALSE, LAC=2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED, CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE; ADD UINTRAFREQNCELL: RNCId=1, CellId=221, NCellRncId=2, NCellId=222, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Deactivating Inter RNC Soft Handover MOD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-0&HSPA_SHO_SWITCH-0&NON_HSPA_SHO_SWITCH-0;
30-2
Issue 02 (2011-07-11)
31 Configuring Intra Frequency Hard Handover
31
Prerequisite
l l l
Configuring Intra Frequency Hard Handover
This section describes how to activate, verify, and deactivate the optional feature WRFD-020301 Intra Frequency Hard Handover.
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 BSC6900 MML command SET UCORRMALGOSWITCH to select HO_INTRA_FREQ_HARD_HO_SWITCH from the HandOver switch list. Run the BSC6900 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 BSC6900 command ADD UNRNC to add a neighboring RNC. Run the BSC6900 MML command ADD UEXT3GCELL to add a neighboring RNC cell. Run the BSC6900 MML command ADD UINTRAFREQNCELL to set the neighboring cell relations. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter related to handover.
4. l
Issue 02 (2011-07-11)
31 Configuring Intra Frequency Hard Handover
1. 2. 3. 4. 5. 6. l
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. Both UE1 and UE2 are subscribed in HLR to support speech service. 4. Both UE1 and UE2 are in idle mode and camp on the CELL1. UE1 calls UE2, and the conversation is clear. UE1 moved from CELL1 to CELL2, through the Trace Date, it can be observed RRC_MEAS_RPRT message with 1D event that UE1 sends to RNC1. Run the BSC6900 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;
31-2
Issue 02 (2011-07-11)
32 Configuring Intra RNC Cell Update
32
Prerequisite
l l l
Configuring Intra RNC Cell Update
This section describes how to activate, verify, and deactivate the basic feature WRFD-010801 Intra RNC Cell Update.
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. 2. 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] 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.
3. 4. 5. l
Verifying Cell Update Triggered by Cell Reselection 1.
Issue 02 (2011-07-11)
2. 3. 4. 5.
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. For example,
SET UUESTATETRANSTIMER: BeF2PStateTransTimer=65535;
6.
7.
Verifying Cell Update Triggered by Uplink Data Transmission 1. 2. 3. 4.
5.
6.
7.
Verifying Periodic Cell Update 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. 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.
32-2
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 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
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;
Issue 02 (2011-07-11)
32-3
33 Configuring Inter RNC Cell Update
33
Prerequisite
l l l
Configuring Inter RNC Cell Update
This section describes how to activate, verify, and deactivate the basic feature WRFD-010802 Inter RNC Cell Update.
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 parameter BE DCH to FACH Transition Timer to 30s. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity detection timers for PS services. Configure intra-frequency neighboring cells controlled by different BSC6900s. For details, see the Configuring an Intra-Frequency Neighboring Cell. Run the BSC6900 MML command MOD UNRNC to set the parameter IUR CCH support flag to ON.
NOTE
IUR CCH support flag is also turned on neighboring BSC6900.
l
Issue 02 (2011-07-11)
Verifying Cell Update Triggered by Cell Reselection

33 Configuring Inter RNC Cell Update
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 CELL. 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 local cell to intra-frequency neighboring cell so as to trigger cell update. The UE should send the RRC_CELL_UPDATE message to neighboring BSC6900, with the cell update cause of cell reselection, and local BSC6900 should send the RRC_CELL_UPDATE_CONFIRM message to the UE. 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;
33-2
Issue 02 (2011-07-11)
34 Configuring Intra RNC URA Update
34
Prerequisite
l l l
Configuring Intra RNC URA Update
This section describes how to activate, verify, and deactivate the basic feature WRFD-010901 Intra RNC URA Update.
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.
2. 3. 4.
5.
Issue 02 (2011-07-11)
6. 7. 8. l
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. 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 send the RRC_URA_UPDATE_CONFIRM message to the UE. This feature does not need to be deactivated.
Verifying URA Update Triggered by URA Reselection 1. 2. 3. 4. 5.
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,
34-2
Issue 02 (2011-07-11)
BeF2PStateTransTimer=10; SET UUESTATETRANS: CellReSelectCounter=1; SET UPSINACTTIMER: PsInactTmrForInt=0, PsInactTmrForBac=0; SET UCONNMODETIMER: T305=D5;
Issue 02 (2011-07-11)
34-3
35 Configuring Inter RNC URA Update
35
Prerequisite
l l l
Configuring Inter RNC URA Update
This section describes how to activate, verify, and deactivate the basic feature WRFD-010902 Inter RNC URA Update.
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.
4.
5.
Issue 02 (2011-07-11)
35 Configuring Inter RNC URA Update
6. 7. 8. l
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. 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 CHANGE OF URA, and the RNC should send the RRC_URA_UPDATE_CONFIRM message to the UE. This feature does not need to be deactivated.
6.
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;
35-2
Issue 02 (2011-07-11)
36 Configuring Direct Signaling Connection Reestablishment (DSCR)
Connection Re-establishment (DSCR)

This section describes how to activate, verify, and deactivate the basic feature WRFD-021400 Direct Signaling Connection Re-establishment (DSCR).
36
Configuring Direct Signaling
Prerequisite
l l l Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
During a DSCR procedure, the RNC autonomously releases the RRC connection carrying nonreal-time RABs and then immediately requests the UE to re-establish an RRC connection for service setup. The RRC connection re-establishment procedure is triggered by an RRC CONNECTION RELEASE message with the cause value of Directed Signaling Connection re-establishment sent from the RNC to the UE. A routing area update follows the RRC connection re-establishment immediately. The DSCR feature is supplementary to the feature WRFD-020605 SRNS Relocation Introduction Package. When the Iur resources are insufficient or SRNS relocation fails, the DSCR feature ensures uninterrupted PS services. Only background and interactive services support this feature. The DSCR re-establishes a service through the routing area update procedure. Therefore, this feature is applicable only to PS services.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UNRNC. In this step, set Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_DSCR.
Issue 02 (2011-07-11)

NOTE
The default value of Handover Type for PS BE Traffic is CORRM_SRNSR_PSBE_RELOC. You can modify the value according to the actual requirements.
2. 3. l
If the Iur interface exists, run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the switches related to SRNS relocation. If the UE is not in the CELL_DCH state, run the BSC6900 MML command SET URRCTRLSWITCH to turn on the DSCR switch for the DRNC. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 36-1 and Figure 36-2.
Figure 36-1 Uu interface tracing dialog box
36-2
Issue 02 (2011-07-11)
Figure 36-2 RRC CONNECTION RELEASE
2. 3.
Use the UE to establish a PS BE service. Perform a handover by adding a cell under the DRNC and then removing the source cell. View the RRC_RRC_CONN_REL message traced on the Uu interface. Check the value of the IE releaseCause in the rrcConnectionRelease of the message. If the value is Directed Signaling Connection re-establishment, this feature has been activated. Run the BSC6900 MML command MOD UNRNC. In this step, set Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC.
----End
Example
//Activating Direct Signaling Connection Re-establishment (DSCR) MOD UNRNC: NRncId=20, PsBeProcType=CORRM_SRNSR_PSBE_DSCR; 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; SET URRCTRLSWITCH: PROCESSSWITCH=DRNC_DIRECT_DSCR-1; //Deactivating Direct Signaling Connection Re-establishment (DSCR) MOD UNRNC: NRncId=20, PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
Issue 02 (2011-07-11)
36-3
37 Configuring NodeB Clock
37
Prerequisite
l l l
Configuring NodeB Clock
This section describes how to activate, verify, and deactivate the basic feature MRFD-210501 NodeB Clock.
Dependencies 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 card clock source. Ensure that the USCU is configured before configuring the BITS clock source. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
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 clock (default mode) Synchronization with GPS Synchronization with the BITS clock
In addition to the preceding three synchronization modes, the MBTS internal clock can work in free-run mode to keep the MBTS running.
Procedure
l NodeB V200R013 Activation Procedure 1. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source.
Issue 02 (2011-07-11)
Table 37-1 Parameters Clock Synchronization Modes Synchronization with the Iub clock (default mode) Synchronization with GPS Synchronization with the BITS clock Parameter Name Parameter Value
Selected Clock Source
LINECLK(Line Clock) GPS(GPS Clock) BITS(BITS Clock)
Verification Procedure 1. Run the NodeB MML command DSP CLKSTAT to query the status of the current clock source. Expected result: The value of Current Clock Source State is Normal. Deactivation Procedure This feature does not need to be deactivated. l NodeB V100R013 Activation Procedure 1. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Table 37-2 Parameters Clock Synchronization Modes Synchronization with the Iub clock (default mode) Synchronization with GPS Synchronization with the BITS clock Parameter Name Parameter Value
Clock Source Type
LINE(LINE clock source) GPSCARD(GPS card clock source) BITS(BITS clock source)
Verification Procedure 1. Run the NodeB MML command DSP CLKSTAT to query the status of the current clock source. Expected result: The value of Current Clock Source State is Normal. Deactivation Procedure
This feature does not need to be deactivated. ----End
Example
l NodeB V200R013
//Activation procedure //Synchronization with the Iub clock SET CLKMODE: MODE=MANUAL, CLKSRC=LINECLK; //Synchronization with GPS SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; //Synchronization with the BITS clock SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Verification procedure DSP CLKSTAT: SN=7;
NodeB V100R013
//Activation procedure //Synchronization with the Iub clock SET CLKMODE: MODE=MANUAL, CLKSRC=LINE; //Synchronization with GPS SET CLKMODE: MODE=MANUAL, CLKSRC=GPSCARD; //Synchronization with the BITS clock SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Verification procedure DSP CLKSTAT:;
Issue 02 (2011-07-11)
37-3
38 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
Connections in Iub/IuCS/Iur Interface

This section describes how to activate, verify, and deactivate the basic feature WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.
38
Configuring Dynamic AAL2
Prerequisite
l l Dependencies on Hardware BTS3902E does not support this feature. Dependencies on Other Features The feature WRFD-050301 ATM Transmission Introduction Package must be configured before this feature is activated. l l License This feature is not under license control. Other Prerequisites The RAN is based on ATM transmission.
Context
In ATM transmission mode, the ATM Adaptation Layer type 2 (AAL2) path is used to carry the user plane data on the Iub/Iur/Iu-CS interface. The AAL2 path is provided according to service type (conversational, streaming, interactive, and background) and bearer type (R99, HSDPA, and HSUPA). Physical bandwidth resources are dynamically allocated to delay-sensitive services and delay-insensitive services, which improves the utilization of transmission links on the Iub interface.
Procedure
l 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, set the parameter Is Root Node to YES; otherwise, set the parameter Is Root Node to NO.
Issue 02 (2011-07-11)
38 Configuring Dynamic AAL2 Connections in Iub/IuCS/Iur Interface

NOTE
For an adjacent node on the Iur or Iu-CS interface, the parameter Adjacent Node Type of its upperlevel hub node must be NNI_AAL2SWITCH; for an adjacent node on the Iub interface, the parameter Adjacent Node Type of its upper-level hub node must be UNI_AAL2SWITCH.
2.
Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path. The parameters CARRYVPI and CARRYVCI must be consistent with those of the AAL2 path configured on the peer end. 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. In the Iub/Iu-CS ATM transmission scenario, a UE in idle state camps on CELL1 and the control plane is correctly configured. Originate the speech and data services. If the service access is normal, the AAL2 path on the Iub/Iu-CS interface is set up successfully. Optional: In the ATM transmission scenario on the Iur interface, a UE in idle state camps on CELL1 and the control plane is correctly configured. Originate a cross-Iur handover. If the handover is successful, the AAL2 path on the Iur interface is set up successfully.
2.
3.
----End
Example
//Activating Dynamic AAL2 Connections in Iub/IuCS/Iur Interface //Adding an adjacent node ADD ADJNODE: ANI=2, NAME="MSC1", NODET=IUCS, DPX=1, TRANST=ATM, IsROOTNODE=YES; //Adding an AAL2 path ADD AAL2PATH: ANI=2, PATHID=1, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0, RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=111, RXTRFX=111, AAL2PATHT=R99; //Verifying Dynamic AAL2 Connections in Iub/IuCS/Iur Interface DSP AAL2PATH: ANI=2, PATHID=1;
38-2
Issue 02 (2011-07-11)
39 Configuring Permanent AAL5 Connections for Control Plane Traffic
39
Prerequisite
l l l l
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.
Dependencies on Hardware BTS3902E does not support this feature. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. 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 section Configuring the Equipment Data of the BSC6900UMTS Initial Configuration Guide.
Context
In the RAN in ATM transmission mode, AAL5 connections are used to bear the Iub/Iur/Iu signaling and the Iub OAM traffic. As specified by 3GPP, User-Network Interface SAAL (UNISAAL) is used for control-plane connections on the Iub interface and Network-Network Interface SAAL (NNI-SAAL) is used for control-plane connections on the Iur/Iu interface. AAL5 connections on the Iub/Iur/Iu interface are all set up by configuring Signaling ATM adaptation layer (SAAL) links.
Procedure
l Activation Procedure 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.
Issue 02 (2011-07-11)
39 Configuring Permanent AAL5 Connections for Control Plane Traffic
2. 3.
Optional: Run the BSC6900 MML command ADD UNCP to add a NodeB Control Port (NCP) link. Optional: Run the BSC6900 MML command ADD UCCP to add a Communication Control Port (CCP) link.
NOTE
An SAAL link can carry only one NCP or CCP link. Therefore, choose to perform step 2 or step 3 based on the actual situation.
Verification Procedure 1. Run the BSC6900 MML command DSP SAALLNK to query the status of the SAAL link. Expected result: The value of SAAL link state is AVAILABLE.
NOTE
An SAAL link can carry only one NCP or CCP link. Therefore, choose to remove the NCP or CCP link carried by the SAAL link, based on the actual situation.
1. 2. 3. ----End
Optional: Run the BSC6900 MML command RMV UNCP to remove the NCP link carried by the SAAL link. Optional: Run the BSC6900 MML command RMV UCCP to remove the CCP link carried by the SAAL link. Run the BSC6900 MML command RMV SAALLNK to remove the SAAL link.
Example
//Activating Permanent AAL5 Connections for Control Plane Traffic ADD SAALLNK: SRN=1, SN=2, SAALLNKN=10, CARRYT=UNI, CARRYSRN=0, CARRYSN=14, CARRYUNILNKN=2, CARRYVPI=10, CARRYVCI=55, TXTRFX=100, RXTRFX=100, SAALLNKT=UNI; ADD UCCP: NODEBNAME="NodeB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=10; //Verifying Permanent AAL5 Connections for Control Plane Traffic DSP SAALLNK: SRN=1, SN=2, SAALLNKN=10; //Deactivating Permanent AAL5 Connections for Control Plane Traffic RMV UCCP: NODEBNAME="NodeB1", PN=0; RMV SAALLNK: SRN=1, SN=2, SAALLNKN=10;
39-2
Issue 02 (2011-07-11)
40 Configuring Call Admission Based on Used AAL2 Path Bandwidth
40
Prerequisite
l l l
Configuring Call Admission Based on Used AAL2 Path Bandwidth
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth.
Dependencies on Hardware BTS3902E does not support this feature. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
With the Call Admission Based on Used AAL2 Path Bandwidth (AAL2 CAC) feature, admission requests are accepted or rejected selectively. This feature maximizes the usage of transmission resources in addition to ensuring the QoS.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD ATMTRF to set parameters to appropriate values. For example, set Service type to NRTVBR, Peak cell rate to 100, and Sustainable cell rate to 80. Run the BSC6900 MML command ADD AAL2PATH to add an ATM Adaptation Layer type 2 (AAL2) path. In this step, set TXTRFX and RXTRFX in accordance with the settings in step 1. Assume that the verification is based on the preceding parameter settings and the peer end is configured with the corresponding AAL2 path link. Originate a PS interactive service. If the data rate is 64 kbit/s, the UE successfully accesses the network.
2.
Issue 02 (2011-07-11)
40 Configuring Call Admission Based on Used AAL2 Path Bandwidth
2. 3. l
Run the BSC6900 MML command DSP AAL2PATH to view that the used bandwidth of the path is about 37 kbit/s, which is the admission bandwidth of the control plane. Originate a PS interactive service. If the data rate is 128 kbit/s, the UE fails to access the network.
----End
Example
//Activation procedure ADD ATMTRF: TRFX=100, ST=NRTVBR, UT=CELL/S, PCR=100, SCR=80; ADD AAL2PATH: ANI=0, PATHID=10, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0, RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=100, RXTRFX=100, AAL2PATHT=R99;
40-2
Issue 02 (2011-07-11)
41 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
41
Prerequisite
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".
l l l
Dependencies on Hardware BTS3902E does not support this feature. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
Huawei RAN supports service type of ATM : l 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) Enhanced unspecified Bit Rate (UBR+)
Configuring UBR+ QoS Class feature, please refer to Configuring UBR+ ATM QoS Class. The traffic volume on the VCC depends on the parameters (SCR, PCR, and CDVT) associated with each type of ATM service. Generally, rt-VBR is applicable to delay-sensitive services and nrt-VBR is applicable to delay-insensitive services. In addition, UBR and nrt-VBR are applicable to None Delay Sensitive service mapping on the HSDPA/HSUPA. It is recommended for configuring service type of ATM shown as Figure 41-1.
Issue 02 (2011-07-11)
41-1
41 Configuring CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
Figure 41-1 Service type of ATM
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.
----End
Example
//Activating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes ADD ATMTRF: TRFX=105, ST=CBR, UT=CELL/S, PCR=1000; //Verifying CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes LST ATMTRF: TRFX=105; Deactivating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes RMV ATMTRF: TRFX=105;
41-2
Issue 02 (2011-07-11)
42 Configuring F5
42
Prerequisite
l Dependencies on Hardware BTS3902E does not support this feature. l l l l Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Configuring F5
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110 F5.
VCL CC is applicable to the AEUa, AOUa, AOUc, UOIa(ATM), and UOIc boards of the BSC6900. VCL PM is applicable to the AOUc and UOIc boards of the BSC6900.
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.
Issue 02 (2011-07-11)
42 Configuring F5
2.
Run the BSC6900 MML command ACT VCLPM to activate the VCL PM function for a link. To activate the function for multiple links, run this command repeatedly. There are three types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC. Run the BSC6900 MML command DSP VCLCC to query the CC result of a VCL. If the VCL CC is activated and the PVC is functional, the SINK activated state and SOURCE activated state are UP, and LOC, AIS, and RDI alarm state is normal. If the loopback is activated and the PVC is functional, the loopback query result is UP, and LOC, AIS, and RDI alarm state is normal.
2.
Run the BSC6900 MML command DSP VCLPM to query the PM result of a VCL. If the VCL PM is activated, the SINK activated state and SOURCE activated state are PM_UP, and PM Active Fail Alarm is Normal.
Deactivation Procedure 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, //Verifying 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;
42-2
Issue 02 (2011-07-11)
43 Configuring UBR+ ATM QoS Class
43
Prerequisite
l l l l
Configuring UBR+ ATM QoS Class
This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305 UBR+ ATM QoS Class".
Dependencies on Hardware BTS3902E does not support this feature. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. 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 Activation Procedure 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.
l
Issue 02 (2011-07-11)
43 Configuring UBR+ ATM QoS Class
1. ----End
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.
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;
43-2
Issue 02 (2011-07-11)
44 Configuring Flow Control
44
Prerequisite
l l l License
Configuring Flow Control
This section describes how to activate, verify, and deactivate the basic feature WRFD-040100 Flow Control.
Dependencies on Hardware NodeB RRC link priority based flow control is depended on WMPT and WBBP boards. Dependencies on Other Features This feature does not depend on other features. This feature is not under license control.
Context
Flow control is implemented by regulating the input transmission rate. This mechanism is called feedback flow control mechanism. The flow control measures are as follows: l l l l l l Board flow control Control-plane load sharing User-plane load sharing Flow control based on RRC request queuing Flow control based on MPU load Flow control based on traffic growth
Procedure
l Activation Procedure Activating board flow control 1. 2. Run the BSC6900 MML command SET FCSW to switch on the flow control and related flow control items. Run the BSC6900 MML command SET FCCPUTHD to configure the CPU usage threshold for each flow control item according to the network plan.
Issue 02 (2011-07-11)

NOTE
l Flow control is triggered when the CPU usage exceeds the related threshold. l The CPU usage thresholds must meet the following condition: 100 Critical threshold Threshold for a flow control item Restore threshold for a flow control item l The critical threshold is of the highest priority. That is, other thresholds take effect only when the CPU usage is lower than the critical threshold. l The flow control based on the packet usage and that based on the CPU usage are independent. The system limits the flow to the lower one allowed by these two flow control algorithms.
3.
Run the BSC6900 MML command SET FCMSGQTHD to configure the packet usage threshold for each flow control item according to the network plan.
NOTE
l Flow control is triggered when the packet usage exceeds the related threshold. l The packet usage thresholds must meet the following condition: 100 Critical threshold Threshold for a flow control item Restore threshold for a flow control item l The critical threshold is of the highest priority. That is, other thresholds take effect only when the packet usage is lower than the critical threshold. l The flow control based on the packet usage and that based on the CPU usage are independent. The system limits the flow to the lower one allowed by these two flow control algorithms.
Activating control-plane load sharing 1. 2. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set Process switch to RNC_SHARE_SWITCH to switch on load sharing. (Optional) Run the BSC6900 MML command SET UCTRLPLNSHAREPARA. In this step, set Control Plane Sharing Out Threshold to 40 so that the control-plane load sharing function can be triggered easily. The default value of Control Plane Sharing Out Threshold is 50.
NOTE
l If the CPU usage is higher than this threshold and lower than the overload threshold, new calls will be assigned to other SPUs. Overload threshold is set by the MML command SET SHARETHD. l Max capability middle load> Max capability normal load> Sharing out capability middle load.
Activating user-plane load sharing 1. Run the BSC6900 MML command SET UUSERPLNSHAREPARA. In this step, set Percentage of User Plane Sharing Out threshold according to the network plan. Inter-subrack user-plane load sharing is triggered when the user plane load on one subrack exceeds this threshold. Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, select RSVDBIT14 in Reserved parameter 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select RSVDBIT1_BIT19 in Reserved parameter 1. Run the BSC6900 MML command SET UCALLSHOCKCTRL. In this step, select CELL_LEVEL in Call Shock Control Switch to switch on the cell-level flow control based on traffic growth.
Activating flow control based on RRC request queuing 1.
Activating flow control based on MPU load 1.
Activating flow control based on traffic growth 1.
44-2
Verification Procedure Verifying board flow control 1. 2. 3. Run the BSC6900 MML command LST FCSW to query the state of the flow control switch. Run the BSC6900 MML command LST FCCPUTHD to query the CPU usage threshold for flow control. Run the BSC6900 MML command LST FCMSGQTHD to query the packet usage threshold for flow control. On the LMT, choose Monitor > Common Monitoring > CPU/DSP Usage Monitoring to observe the CPU usage of each subsystem. If the CPU usage of each subsystem is almost the same, load sharing takes effect. Run the BSC6900 MML command LST UCACALGOSWITCH to query the state of the switch for flow control based on RRC request queuing. Run the BSC6900 MML command LST URRCTRLSWITCH to query the state of the switch for flow control based on MPU load. Run the BSC6900 MML command LST UCALLSHOCKCTRL to query the state of the switch for flow control based on traffic growth.
Verifying control-plane and user-plane load sharing 1.
Verifying flow control based on RRC request queuing 1.
Verifying flow control based on MPU load 1.
Verifying flow control based on traffic growth 1. l
Deactivation Procedure Deactivating board flow control 1. 1. Run the BSC6900 MML command SET FCSW to switch off flow control. Run the BSC6900 MML command SET URRCTRLSWITCH to deselect RNC_SHARE_SWITCH in Process switch. User-plane load sharing does not need to be deactivated. Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, deselect RSVDBIT14 in Reserved parameter 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, deselect RSVDBIT1_BIT19 in Reserved parameter 1. Run the BSC6900 MML command SET UCALLSHOCKCTRL. In this step, deselect CELL_LEVEL in Call Shock Control Switch. Deactivating control-plane load sharing
Deactivating user-plane load sharing 1. 1. Deactivating flow control based on RRC request queuing
Deactivating flow control based on MPU load 1.
Deactivating flow control based on traffic growth 1. ----End
Example
//Activating board flow control //Switching on XPU load control
Issue 02 (2011-07-11)
44-3
SET FCSW: BRDCLASS=XPU, FCSW=ON, PRINTSW=ON, TRACESW=ON, PMSW=ON, LOGSW=ON; //Setting CPU usage threshold for DPU flow control SET FCCPUTHD:BRDCLASS=DPU, SMWINDOW=6, FDWINDOW=2, CTHD=95, PRINTCTHD=60, PRINTRTHD=50, TRACECTHD=60, TRACERTHD=50, LOGCTHD=60, LOGRTHD=50; //Setting packet usage threshold for DPU flow control SET FCMSGQTHD: BRDCLASS=DPU, SMWINDOW=9, CTHD=95, PRINTCTHD=60, PRINTRTHD=50, TRACECTHD=60, TRACERTHD=50, LOGCTHD=60, LOGRTHD=50; //Activating control-plane load sharing SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-1; SET UCTRLPLNSHAREPARA: CtrlPlnSharingOutThd=40; SET SHARETHD: BT=XPU, SMRRCCONNCCPUTHD=80, SMRRCCONNRCPUTHD=70, CRRCCONNCCPUTHD=80, CRRCCONNRCPUTHD=70, LRRCCONNCCPUTHD=80, LRRCCONNRCPUTHD=70, SMRRCCONNCMSGTHD=80, SMRRCCONNRMSGTHD=70, CRRCCONNCMSGTHD=80, CRRCCONNRMSGTHD=70, LRRCCONNCMSGTHD=80, LRRCCONNRMSGTHD=70; //Activating user-plane load sharing SET UUSERPLNSHAREPARA: UserPlnSharingOutThd=90; //Activating RRC Shaping and Queuing SET UCACALGOSWITCH:RsvdPara1=RSVDBIT14-1; //Activating flow control based on MPU load SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT19-1; //Activating flow control based on traffic growth SET UCALLSHOCKCTRL: CallShockCtrlSwitch=CELL_LEVEL-1; //Verifying board flow control LST FCSW: LstFormat=VERTICAL; LST FCCPUTHD: LstFormat=VERTICAL; LST FCMSGQTHD: LstFormat=VERTICAL; //Verifying flow control based on RRC request queuing LST UCACALGOSWITCH: LstFormat=VERTICAL; //Verifying flow control based on MPU load LST URRCTRLSWITCH: LstFormat=VERTICAL; //Verifying flow control based on traffic growth LST UCALLSHOCKCTRL: LSTFORMAT=VERTICAL; //Deactivating board flow control SET FCSW: BRDCLASS=XPU, FCSW=OFF; //Deactivating control-plane load sharing SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-0; //Deactivating flow control based on RRC request queuing SET UCACALGOSWITCH: RsvdPara1=RSVDBIT14-0; //Deactivating flow control based on MPU load SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT19-0; //Deactivating flow control based on traffic growth SET UCALLSHOCKCTRL: CallShockCtrlSwitch=CELL_LEVEL-0;
44-4
Issue 02 (2011-07-11)
45 Configuring BOOTP
45
Prerequisite
l Dependencies on Hardware l l Dependencies on Other Features
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.
The transmission equipment is in the connected state. BOOTP applies only to ATM networking scenarios. This feature does not depend on other features. License This feature is not under license control.
Context
This feature enables NodeB to set up the OM channel to the RNC automatically without configuration data. The maintenance staff can download the data and software to the NodeB through the OM channel at the far end. The feature decreases the operation and maintenance costs and enhances the network maintainability and maintenance quality. NodeB will automatically set up the OM channel using the BOOTP protocol. In addition, NodeB monitors the OM channel. When the OM channel is broken, NodeB can rebuild it.
Procedure
l 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
Issue 02 (2011-07-11)
45 Configuring BOOTP
If the BOOTP configurations at the BSC6900 are completed but no configuration at the NodeB and the NodeB can be maintained on the M2000, it indicates that the NodeB has successfully set up the OM channel by using the BOOTP feature. l Deactivation Procedure This feature does not need to be deactivated.
----End
Example
//Activation procedure ADD DEVIP: SRN=0, SN=14, DEVTYPE=IPOA_CLIENT_IP, IPADDR="131.131.131.132", MASK="255.255.255.0"; ADD IPOAPVC: IPADDR="131.131.131.132", PEERIPADDR="131.131.131.131", CARRYT=IMA, CARRYIMAGRPN=0, CARRYVPI=83, CARRYVCI=80, TXTRFX=100; ADD UNODEBIP: NODEBID=0, NBTRANTP=ATMTRANS_IP, NBATMOAMIP="131.131.131.131", NBATMOAMMASK="255.255.255.0", ATMSRN=0, ATMSN=14;
45-2
Issue 02 (2011-07-11)
46 Configuring NodeB Self-discovery Based on IP Mode
46
Prerequisite
l
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.
Dependencies on Hardware The transmission device is connected properly. DHCP applies only to IP networking scenarios. Only 3900 series base stations support the DHCP+AACP function.
l l
Context
l l If the configuration file of the NodeB 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 channel of the NodeB. In the case that DHCP response is made, the BSC6900 will send the IP address to the NodeB.
Issue 02 (2011-07-11)
46 Configuring NodeB Self-discovery Based on IP Mode
3.
Optional: If Hub NodeB is applied, run the NodeB MML command ADD DHCPSVRIP to add a DHCP server IP address. Therefore, a lower-level NodeB can obtain an IP address automatically by using the DHCP.
Verification Procedure In the case that 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), if the NodeB can be maintained on the M2000, it indicates that the NodeB has successfully set up the OM channel by using this feature.
Deactivation Procedure This feature need not be deactivated.
----End
Example
//Activation procedure //Running the following command at the BSC6900 ADD UNODEBESN: NODEBID=0, NBLB1="020GKV1082000126", USENBLB2=Disable, NODEBPT=ETH/TRUNK, PTIP="131.131.131.132", PTIPMASK="255.255.255.0"; ADD UNODEBIP: NODEBID=0, NBTRANTP=IPTRANS_IP, NBIPOAMIP="131.131.131.131", NBIPOAMMASK="255.255.255.0", IPSRN=0, IPSN=18, IPLOGPORTFLAG=NO; //(Optional) Running the following command at the NodeB ADD DHCPSVRIP: DHCPSVRIP="13.13.13.13";
46-2
Issue 02 (2011-07-11)
47 Configuring License Control for Urgency
47
Prerequisite
Configuring License Control for Urgency

This section describes how to activate, verify, and deactivate the basic feature WRFD-040300 License Control for Urgency.
l l l
Dependencies on Hardware Since RAN13.0, both BSC6900 and NodeB support this feature. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
CAUTION
This feature is enabled only in scenarios where the traffic volume increases abruptly, for example, in a disaster. It can be enabled only three times for each R version by BSC6900 MML command SET LICENSECTRL and it can be enabled only fifteen times by WRFD-040202 RNC Node Redundancy and it is valid only for seven days each time. After this function is enabled, a network can reach its maximum capacity that is supported by the hardware. This documentation describes the procedure of enabling the feature by BSC6900 MML command .
Procedure
l Activation Procedure 1. 2. On the BSC6900 side: Run the BSC6900 MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch to ON(ON). On the NodeB V200R013 side: Run the NodeB MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch State to ON.
Issue 02 (2011-07-11)
47 Configuring License Control for Urgency
3. l
On the NodeB V100R013 side: Run the NodeB MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch to ON(ON). On the BSC6900 Side (1) Run the BSC6900 MML command DSP LICUSAGE to view resource items of the license. Expected result: All the resource items reach their maximum values. (2) Run the BSC6900 MML command LST LICENSECTRL to query the setting of Grace Protection Period Switch State. Expected result: Values of Remaining Grace Protection Times and Remaining Grace Protection Days are displayed and the value of Grace Protection Period Switch State is ON.
2.
On the NodeB V200R013 side or NodeB V100R013 side (1) Run the NodeB MML command DSP LICENSE to view resource items of the license. Expected result: All the resource items reach their maximum values. (2) Run the NodeB MML command LST LICENSECTRL to query the setting of Grace Protection Period Switch State. Expected result: Values of Remaining Grace Protection Times and Remaining Grace Protection Days are displayed and the value of Grace Protection Period Switch State is ON.
Deactivation Procedure 1. 2. 3. On the BSC6900 Side: Run the BSC6900 MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch to OFF(OFF). On the NodeB V200R013 Side: Run the NodeB MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch State to OFF. On the NodeB V100R013 Side: Run the NodeB MML command SET LICENSECTRL. In this step, set Grace Protection Period Switch to OFF(OFF).
----End
47-2
Issue 02 (2011-07-11)
48 Configuring Intelligently Out of Service
48
Prerequisite
Configuring Intelligently Out of Service

This section describes how to activate, verify, and deactivate the basic feature WRFD-031000 Intelligently Out of Service.
l l l
Context
Insufficient battery voltage or NodeB reset may lead to service disruption. When the preceding problems occur, this feature enables the NodeB to automatically reduce the pilot transmit power and hand over the UE to other cells, preventing service disruption.
Procedure
l Activation Procedure 1. 2. l Run the NodeB MML command SET SMTHPWRSWTCH. In this step, set Smooth Power Change Function Switch to OPEN(Open). Run the NodeB MML command SET SMTHPWRPARA. In this step, set Smart default step(0.5dB) and Smart default time ratio(100ms). Run the NodeB MML command LST SMTHPWRSWTCH. In this step, check whether Smooth Power Change Function Switch is set to OPEN. Run the NodeB MML command LST SMTHPWRPARA. In this step, check whether Smart default step(0.5dB) and Smart default time ratio(100ms) are set correctly.
----End
48 Configuring Intelligently Out of Service
Example
//Activation procedure SET SMTHPWRSWTCH: SWITCH=OPEN; SET SMTHPWRPARA: STEP=10, PERIOD=1; //Verification procedure LST SMTHPWRSWTCH:; LST SMTHPWRPARA:;
48-2
Issue 02 (2011-07-11)
49 Configuring OCNS
49
Prerequisite
l l l Dependencies on Hardware Dependencies on Other Features License
Configuring OCNS
This section describes how to activate, verify, and deactivate the basic feature WRFD-031200 OCNS (Orthogonal Channel Noise Simulator).
This feature does not depend on the hardware. This feature does not depend on other features. This feature is not under license control.
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. Run the NodeB MML command STR DLSIM to start downlink load simulation. In this step, set Local Cell ID and Load Ratio (%).
NOTE
l This command can be successfully executed only when the corresponding logical cell exists. l The downlink network load simulation uses the channelization codes from 112 to 127 whose SF = 128. l If you start the downlink network load simulation, it is advised to reserve the channelization codes in the RNC. l After starting the DL load simulation, new service can not be built in the channel resource occupied by the simulation.
Issue 02 (2011-07-11)
49-1
49 Configuring OCNS
1.
Run the NodeB MML command DSP DLSIM to query the downlink load simulation result. In this step, specify Local Cell ID. The execution result displayed on the LMT shows the simulated load rate. Run the NodeB MML command STP DLSIM to stop the downlink load simulation. In this step, specify Local Cell ID.
----End
Example
//Activation procedure STR DLSIM: LOCELL=1, LR=80; //Verification procedure DSP DLSIM: LOCELL=1; //Deactivation procedure STP DLSIM: LOCELL=1;
49-2
Issue 02 (2011-07-11)
50 Configuring Power Off the Equipment Level by Level
50
Prerequisite
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.
Dependencies on Hardware Cabinets providing AC input power such as APM30, APM100, and APM200. These cabinets can be used for outdoor NodeBs.
l l
Context
After the mains supply is cut off, the NodeB powers off devices by level when certain DC voltage thresholds are reached. Intelligent shutdown of RF units and NodeBs can prolong the working time of the system by making efficient use of the available storage batteries.
Procedure
l NodeB V200R013 Activation Procedure 1. 2. Run the NodeB MML command MOD PMU. In this step, set Load Shutdown Flag to ENABLE(Enable) and set Load Shutdown Voltage(0.1V) if needed. Run the NodeB MML command MOD BATTERY. In this step, set Low Voltage Shutdown Flag to ENABLE and set Shutdown Voltage(0.1V) if needed.
Verification Procedure 1. Run the NodeB MML command LST PMU and query the values of Load Shutdown Flag and Load Shutdown Voltage(0.1V).
Issue 02 (2011-07-11)
50 Configuring Power Off the Equipment Level by Level
2.
Run the NodeB MML command LST BATTERY and query the values of Low Voltage Shutdown Flag and Shutdown Voltage(0.1V).
Deactivation Procedure 1. 2. l Run the NodeB MML command MOD BATTERY and set Low Voltage Shutdown Flag to DISABLE(Disable). Run the NodeB MML command MOD PMU and set Load Shutdown Flag to DISABLE(Disable).
NodeB V100R013 Activation Procedure 1. Run the NodeB MML command SET SDPA. In this step, set Load Shutdown Flag to ENABLE(Enable), set Load Shutdown Voltage(0.1V) if needed, set Low Voltage Shutdown Flag to ENABLE(Enable), set Shutdown Voltage(0.1V) if needed.
Verification Procedure 1. Run the NodeB MML command LST SDPA, query the values of Load Shutdown Flag and Load Shutdown Voltage(0.1V),, query the values of Low Voltage Shutdown Flag and Shutdown Voltage(0.1V),.
Deactivation Procedure 1. Run the NodeB MML command SET SDPA. In this step, set Load Shutdown Flag to DISABLE(Disable), and set Low Voltage Shutdown Flag to DISABLE (Disable).
----End
Example
l NodeB V200R013
//Activation procedure MOD PMU: CN=1, PTYPE=APM30, LSDF=ENABLE, LSDV=430; MOD BATTERY: CN=1, LVSDF=ENABLE, SDV=360; //Verification procedure LST PMU: CN=1; LST BATTERY: CN=1; //Deactivation procedure MOD BATTERY: CN=1, LVSDF=DISABLE; MOD PMU: CN=1, PTYPE=APM30, LSDF=DISABLE;
NodeB V100R013
//Activation procedure SET SDPA: CN=1, LSDF=ENABLE, LSDV=440, LVSDF=ENABLE, SDV=360, CSLSDF=DISABLE; //Verification procedure LST SDPA: CN=1; //Deactivation procedure SET SDPA: CN=1, LSDF=DISABLE, LVSDF=DISABLE, CSLSDF=DISABLE;
50-2
Issue 02 (2011-07-11)
51 Configuring Solar Power Device Management
51
Prerequisite
l l l
Configuring Solar Power Device Management
This section describes how to activate, verify, and deactivate the basic feature WRFD-031500 Solar Power Device Management.
Dependencies on Hardware Only 3900 series base stations support the feature. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
As green energy, solar power is being gradually introduced for supplying power for the NodeB. This feature enables the NodeB to communicate with a solar controller through the 485 serial port, therefore managing a solar power device, which makes the NodeB an eco-friendly base station.
Procedure
l Activation Procedure 1. 2. Run the NodeB MML command ADD PMU to add a PMU. In this step, set Power System Type to SC48200. Optional: If a diesel generator is required, run the NodeB MML command ADD DIESELGEN. Set Intelligent Control Flag to ENABLE(Enable). Set Rated Power(0.1kVA) based on the rated power specified on the nameplate of the diesel generator. l Verification Procedure 1. Run the NodeB MML command DSP PMU to query the configuration information about the PMU.
Issue 02 (2011-07-11)
51 Configuring Solar Power Device Management
Expected result: The value of Power System Type is SC48200. 2. Optional: Run the NodeB MML command LST DIESELGEN to query the configuration information about the diesel generator. Expected result: The value of Intelligent Control Flag is ENABLE. Run the NodeB MML command RMV DIESELGEN to remove a dieselgen. Run the NodeB MML command RMV PMU to remove a PMU.
----End
Example
//Activation procedure ADD PMU: CN=0, PTYPE=SC48200, MPN=0, LSDF=ENABLE; ADD DIESELGEN: CN=0, ICF=ENABLE, POWER=500; //Verification procedure DSP PMU: CN=0; LST DIESELGEN: CN=0; //Deactivation procedure RMV DIESELGEN: CN=0; RMV PMU: CN=0;
51-2
Issue 02 (2011-07-11)
52 Configuring Connection with TMA (Tower Mounted Amplifier)
52
Prerequisite
l l l l
Configuring Connection with TMA (Tower Mounted Amplifier)
This section describes how to activate, verify, and deactivate the basic feature MRFD-210601 Connection with TMA (Tower Mounted Amplifier).
Dependencies on Hardware The base station is connected to the Antenna Line Device (ALD) normally. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. Other Prerequisites The TMA is loaded with basic software for its normal operation.
Context
The gain range supported by the Smart Tower-Mounted Amplifier (STMA) varies with models and vendors.
Procedure
l NodeB V200R013 Activation Procedure 1. 2. 3. 4. Run the NodeB MML command MOD ANTENNAPORT to set ALD Power Switch to ON. Run the NodeB MML command SCN ALD to scan the Device Name, Vendor Code and Serial No.. Run the NodeB MML command ADD TMA to add a TMA. If the device supports TMA gain, run the NodeB MML command MOD TMASUBUNIT to set the TMA gain.
Issue 02 (2011-07-11)

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

//Activation procedure SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=TMA12DB_ONLY_NON_AISG, PSP=R0A, PWRSW=ON; SCN ALD: CN=0, SRN=60, ACN=R0A; ADD ALD: NAME="test", CASE=REGULAR, DEVTP=STMA, CN=0, SRN=60, ACN=R0A, SUBUNIT=1; SET TMAGAIN: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A, GAIN=48; SET RXATTEN: CN=0, SRN=60, SN=0, RXNO=0, ATTEN=0; //Verification procedure LST TMAGAIN: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A;
Issue 02 (2011-07-11)
52-3
53 Configuring Remote Electrical Tilt
53
Prerequisite
l l l
Configuring Remote Electrical Tilt
This section describes how to activate, verify, and deactivate the basic feature MRFD-210602 Remote Electrical Tilt.
Dependencies on Hardware The base station is connected to a remote electrical tilt (RET) antenna properly. The remote control unit (RCU) is compatible with the RET antenna. The RCU is loaded with a configuration file designated for the RET antenna. The RCU is loaded with the basic software. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
With this feature activated, users can remotely adjust the tilt of an RET antenna to optimize network performance. l l Calibrating the RET antenna may affect its coverage for a short period of time. Calibrating an RET antenna takes up to 4 minutes.
Procedure
l NodeB V200R013 Activation Procedure 1. 2. 3. 4.
Issue 02 (2011-07-11)
If the antenna port is used, run the NodeB MML command MOD ANTENNAPORT. In this step, set ALD Power Switch to ON. If the RET antenna port is used, run the NodeB MML command MOD RETPORT. In this step, set ALD Power Switch to ON. Run the NodeB MML command SCN ALD to obtain the ESN of an ALD. Run the NodeB MML command ADD RET to add an RET antenna.

NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
5. 6. 7. 8.
Run the NodeB MML command CLB RET to calibrate the RET antenna. Run the NodeB MML command MOD RETSUBUNIT to modify parameters concerning an RET antenna subunit. Run the NodeB MML command MOD RETDEVICEDATA to modify parameters concerning the attributes of an RET device. Run the NodeB MML command MOD RETTILT to modify the tilt of the RET antenna.
Verification Procedure 1. If the antenna port is used, run the NodeB MML command DSP ANTENNAPORT to query the power switch status for the port. Expected result: ALD Actual Power Switch is ON. 2. If the RET antenna port is used, run the NodeB MML command DSP RETPORT to query the power switch status for the port. Expected result:ALD Actual Power Switch is ON. 3. 4. Run the NodeB MML command DSP RET to query information about the RET antenna. Run the NodeB MML command DSP RETSUBUNIT to query the dynamic information on an RET antenna subunit and an RET antenna's tilt.
Deactivation Procedure This feature does not need to be deactivated. l NodeB V100R013 Activation Procedure 1. 2. 3. Run the NodeB MML command SET ALDPWRSW. In this step, set Power Supply Switch to ON. Run the NodeB MML command SCN ALD to obtain the ESN of an ALD. Run the NodeB MML command ADD ALD to add an antenna device.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
4. 5.
Run the NodeB MML command CLB ANT to calibrate the antenna device. Run the NodeB MML command SET ANTTILT to set the tilt of antenna device.
Verification Procedure 1. Run the NodeB MML command DSP ANTCON to query the power switch status for the antenna port. Expected result: Power Supply Switch Run Status is ON. 2. Run the NodeB MML command DSP ANTTILT to query the tilt of the RET antenna. Expected result: Current Tilt (0.1 degree) is set to the specified value. Deactivation Procedure This feature does not need to be deactivated. ----End
Example
l NodeB V200R013
//Activation procedure MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON; SCN ALD:; ADD RET: DEVICENO=0, DEVICENAME="RET1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET, POLARTYPE=SINGLE, SCENARIO=REGULAR; CLB RET: OPMODE=SUBUNIT, DEVICENO=0, SUBUNITNO=1; MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1; MOD RETDEVICEDATA: DEVICENO=0, SUBUNITNO=1; MOD RETTILT: OPMODE=DEVICENO, DEVICENO=0, TILT=45; //Verification procedure DSP ANTENNAPORT:; DSP RET: DEVICENO=0; DSP RETSUBUNIT: DEVICENO=0, SUBUNITNO=1;
NodeB V100R013
//Activation procedure SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=RET_ONLY_COAXIAL, PSP=R0A, PWRSW=ON; SCN ALD:; ADD ALD: NAME="test", CASE=REGULAR, DEVTP=SINGLE_RET, CN=0, SRN=60, ACN=R0A; CLB ANT: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A, DEVTP=SINGLE_RET; SET ANTTILT: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A, DEVTP=SINGLE_RET, TILT=20; //Verification procedure DSP ANTCON:; DSP ANTTILT: OPMODE=CSAT, CN=0, SRN=60, ACN=R0A;
Issue 02 (2011-07-11)
53-3
54 Configuring Same Band Antenna Sharing Unit (900 MHz)
54
Prerequisite
l l l
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).
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 NodeB V200R013 Activation Procedure 1. 2. 3. 4. Run the NodeB MML command MOD ANTENNAPORT to set ALD Power Switch to ON. 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 SASU to configure the SASU and set the antenna DC power switch state of the SASU. Run the NodeB MML command MOD SASUSUBUNIT to set the SASU working mode and the gain of the SASU.
1. 2. l
Run the NodeB MML command DSP SASU to query the antenna DC power switch state of the SASU. Run the NodeB MML command DSP SASUSUBUNIT to query the SASU working mode and the gain of the SASU.
NodeB V100R013 Activation Procedure 1. 2. 3. 4. 5. 6. 7. 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. 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.
Verification Procedure 1. 2. 3. 4. 5. 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.
Deactivation Procedure This feature need not be deactivated. ----End
Example
l NodeB V200R013
//Activation procedure MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON, THRESHOLDTYPE=UER_SELF_DEFINE, UOTHD=1000, UCTHD=1050, OOTHD=1200, OCTHD=1150; SCN ALD: CTRLCN=0, CTRLSRN=60, CTRLSN=0; ADD SASU: DEVICENO=0, DEVICENAME="0_0N0A0SASU_3G", CTRLCN=0, CTRLSRN=60, CTRLSN=0, DCSWITCH=UMTS; MOD SASUSUBUNIT: DEVICENO=0, SUBUNITNO=1, MODE=NORMAL, BSGAIN=12, UMTSGAIN=12, DCLOAD=20; //Verification procedure DSP SASU: DEVICENO=0; DSP SASUSUBUNIT: DEVICENO=0;
NodeB V100R013
//Activation procedure SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=CUSTOM, PSP=R0A,
54-2
Issue 02 (2011-07-11)

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; //Verification procedure LST ALD:; LST SASUMODE: OPMODE=NAME, NAME="0_0N0A0SASU_3G"; LST SASUGAIN: OPMODE=NAME, NAME="0_0N0A0SASU_3G"; LST SASUDCSW: OPMODE=NAME, NAME="0_0N0A0SASU_3G"; LST SASUDCLD: OPMODE=NAME, NAME="0_0N0A0SASU_3G";
Issue 02 (2011-07-11)
54-3
55 Configuring Multiple RAB Package
55
Prerequisite
l l l l
Configuring Multiple RAB Package
This section describes how to activate, verify, and deactivate the optional feature WRFD-010615 Multiple RAB Package (PS RAB 2).
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been 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: 56 Configuring Combination of Two PS Services, 57 Configuring Combination of One CS Service
Issue 02 (2011-07-11)
55 Configuring Multiple RAB Package
and Two PS Services, 58 Configuring Combination of Three PS Services, 59 Configuring Combination of One CS Service and Three PS Services and 60 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;
55-2
Issue 02 (2011-07-11)
56 Configuring Combination of Two PS Services
56
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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 controlling this feature has been 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. On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally.
Verification Procedure 1. 2. 3.
Issue 02 (2011-07-11)
56 Configuring Combination of Two PS Services
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 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;
56-2
Issue 02 (2011-07-11)
57 Configuring Combination of One CS Service and Two PS Services
57
Prerequisite
l l
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.
l l
License The license controlling this feature has been 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 1 as a modem. Visit the Internet on UE 1. Verify that web pages are displayed normally (a PS Service).
Issue 02 (2011-07-11)
57 Configuring Combination of One CS Service and Two PS Services
4. 5. l
On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally (a PS Service). Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable (a CS Service). 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;
57-2
Issue 02 (2011-07-11)
58 Configuring Combination of Three PS Services
58
Prerequisite
l l
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.
l l
License The license controlling this feature has been 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. Visit the Internet on UE. Verify that web pages are displayed normally. Visit the Multimedia service on the UE. Verify that this service is played normally.
Issue 02 (2011-07-11)
58 Configuring Combination of Three PS Services
4. 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 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;
58-2
Issue 02 (2011-07-11)
59 Configuring Combination of One CS Service and Three PS Services
59
Prerequisite
l l
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.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE supports the combination of one CS service and three PS services. The CN node and UE have the corresponding multi-RAB support capability.
Context
Procedure
l 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 1 as a modem. Visit the Internet on UE 1. Verify that web pages are displayed normally (a PS Service).
Issue 02 (2011-07-11)
59 Configuring Combination of One CS Service and Three PS Services
4. 5. 6. l
Visit the Multimedia service on the UE 1. Verify that this service is played normally (a PS Service). On the portable computer, connect to an FTP server and download data. Verify that the data is downloaded normally (a PS Service). Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable (a CS Service). 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 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;
59-2
Issue 02 (2011-07-11)
60 Configuring Combination of Four PS Services
60
Prerequisite
l l
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.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE supports the combination of Four PS Services. The CN node and UE have the corresponding multi-RAB support capability.
Context
RAN11.0 supports up to four PS RABs per user. A typical application of Multi-RAB is VoIP plus BE service where VoIP may need up to three RABs to transmit SIP signaling, Real-Time Transport Protocol (RTP) (voice), and Real-Time Control Protocol (RTCP) (media monitoring) respectively, as shown in Figure 60-1. Figure 60-1 VoIP service
Issue 02 (2011-07-11)
60-1
60 Configuring Combination of Four PS Services
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. (If RTCP is assigned, SIP signaling and RTP must be assigned at the same time.) 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;
60-2
Issue 02 (2011-07-11)
61 Configuring HSDPA Introduction Package
61
Prerequisite
l l
Configuring HSDPA Introduction Package
This section describes how to activate, verify, and deactivate the optional feature WRFD-010610 HSDPA Introduction Package.
Dependencies on Hardware NDLP and NBBI in the NodeB do not support this feature. Dependencies on Other Features HSDPA 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 controlling this feature has been activated. Other Prerequisites The UE is HSDPA-capable.
Context
High Speed Downlink Packet Access (HSDPA) is one of the important features defined in 3GPP specifications. HSDPA can significantly increase the downlink peak rate per user, shorten the round trip delay, and expand the system capacity. This feature package provides the basic functions of HSDPA to meet the requirements for test or trial operation of HSDPA services.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command ADD UCELLHSDPA to set HSDPA-related parameters based on the network plan. Run the BSC6900 MML command ACT UCELLHSDPA to activate this feature. Configure Iub transport for HSDPA. In an ATM network:
(1) Run the BSC6900 MML command ADD ATMTRF to configure new records of ATM traffic based on network planning requirements. (2) Run the BSC6900 MML command LST TRMMAP to query the transmission resource mapping. (3) Run the BSC6900 MML command ADD AAL2PATH to set associated parameters according to the network plan. TX traffic record index and RX traffic record index of the AAL2 path to be added must be the same as those set in the ADD ATMTRF command. In addition, AAL2 Path Type should be set according to the mapping between service types and AAL paths. (4) Run the NodeB MML command ADD AAL2PATH to configure an AAL2 path for HSDPA based on network planning requirements. In an IP network: (1) Run the BSC6900 MML command LST ADJMAP to query whether resource management mapping is configured for the adjacent node. If configured, check the TRMMAP index of the adjacent node. If not configured, run the BSC6900 MML command LST TRMMAP to query the default TRMMAP ID used by the adjacent node based on the settings of Interface Type and Transport Type. For example, if Interface Type is set to Iub Interface, then TRMMAP ID is 1. (2) Run the BSC6900 MML command LST TRMMAP to check whether the IP path mapping to the HSDPA service is configured according to the TRMMAP ID used by the adjacent node. If configured, no further action is required. If not configured, run the BSC6900 MML command ADD IPPATH to configure the IP path mapping to the HSDPA service.
NOTE
To ensure that HSDPA services can be set up successfully, HSDPA services must be mapped to the corresponding AAL2 paths or IP paths. To avoid the affect on ongoing services, you can add new AAL2 paths or IP paths.
Verification Procedure 1. Run the BSC6900 MML command DSP UCELL to check whether this feature is activated. If HSDPA Operational State is set to Enabled, this feature has been activated. Run the BSC6900 MML command DEA UCELLHSDPA to deactivate this feature. Run the BSC6900 MML command DSP UCELL to check whether the HSDPA feature is deactivated. If HSDPA Operational State is set to Disabled, this feature has been deactivated.
----End
Example
// Setting HSDPA-related parameters ADD UCELLHSDPA: CellId=3000, AllocCodeMode=Automatic, HsPdschMaxCodeNum=4, HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON; //Activating HSDPA Introduction Package ACT UCELLHSDPA: CellId=3000; //Configuring Iub transport for HSDPA //ATM network
61-2
Issue 02 (2011-07-11)
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; //Adding an AAL2 path ADD AAL2PATH: PATHID=2, SN=12, SBT=BASE_BOARD, PT=IMA, VPI=13, VCI=71, ST=RTVBR, PCR=5150, SCR=5149, RCR=5150, NT=LOCAL, PAT=H_NRT; //IP network ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP,PATHT=BE, IPADDR="80.1.1.1", PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000; //Verifying HSDPA Introduction Package DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL; //Deactivating HSDPA Introduction Package DEA UCELLHSDPA: CellId=3000; DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;
Issue 02 (2011-07-11)
61-3
62
Prerequisite
l l l License
Configuring 15 Codes per Cell
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061001 15 Codes per Cell.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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. The license controlling this feature has been activated.
Context
This feature provides code resources occupied by Huawei HSDPA services. An HS-PDSCH can use up to 15 SF16 codes in a cell.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLHSDPA to configure 1 HSSCCHs.
Issue 02 (2011-07-11)
62-1

NOTE
l The BSC6900 MML command MOD UCELLHSDPA fails to be executed when HSDPA is activated. Therefore, run the BSC6900 MML command DEA UCELLHSDPA to deactivate HSDPA before configuring this feature and run the BSC6900 MML command ACT UCELLHSDPA to reactivate HSDPA after configuring this feature. l The BSC6900 MML command MOD UCELLHSDPA fails to be executed when CELL-FACH enhancement is activated. Therefore, run the BSC6900 MML command DEA UCELLEFACH to deactivate enhanced CELL-FACH before configuring this feature and run the BSC6900 MML command ACT UCELLEFACH to reactivate enhanced CELL-FACH after configuring this feature. l By default, the number of HS-SCCH codes for each cell is 4. If the default number is used, the HS-PDSCH can use only 14 SF16 codes. To enable the HS-PDSCH to use all 15 SF16 codes, run the BSC6900 MML command MOD UCELLHSDPA to set the value of Code Number for HS-SCCH to 1.
2. l
Run the BSC6900 MML command MOD UCELLHSDPA to set Allocate Code Mode to Manual(Manual) and Code Number for HS-PDSCH to 15. Initialize UMTS monitoring on the BSC6900 LMT, as shown in Figure 62-1. Click Submit. A real-time monitoring window is displayed. Figure 62-1 Cell Performance Monitoring
2.
Check whether 15 SF16 codes are occupied by the HS-PDSCH in the Cell Performance Monitoring window. Expected result: The HS-PDSCH occupies 15 SF16 codes. 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;
62-2
Issue 02 (2011-07-11)
63 Configuring Time and HS-PDSCH Codes Multiplex
63
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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.
License The license controlling this feature has been 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
Issue 02 (2011-07-11)
63-1
64 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
64
Prerequisite
l l
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).
Dependencies on Hardware This feature does not depend on the hardware. Dependencies 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.
Context
Huawei provides multiple HSDPA scheduling algorithms such as maximum C/I (MAXCI), round-robin (RR), proportional fair (PF), and Enhanced Proportional Fair (EPF).Before the HSDPA feature is enabled, HARQ must be enabled and HSDPA scheduling algorithms must be set.
Procedure
NOTE
l HSDPA H-ARQ is activated automatically without any configuration. l This section describes how to set Max C/I, RR, and PF scheduling algorithms. For details on how to set the EPF scheduling algorithm, see the description of the feature WRFD-01061103 Scheduling based on EPF and GBR.
1.
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).
l
Issue 02 (2011-07-11)
64 Configuring HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
1. l
Run the NodeB MML command LST MACHSPARA to query the settings of the parameter Scheduling Method.
----End
Example
//Activation procedure SET MACHSPARA: LOCELL=0, SM=MAXCI; //Verification procedure LST MACHSPARA: LOCELL=0;
64-2
Issue 02 (2011-07-11)
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.
65
l l
Configuring HSDPA Static Code
Prerequisite
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated. l License The license controlling this feature has been activated.
Context
This feature provides two code allocation strategies: HSDPA static code allocation and RNCcontrolled dynamic code allocation. When R99 and HSDPA services co-exist, this feature enables full use of channelization code resources to expand system capacity.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLHSDPA. In this step, set Allocate Code Mode to Manual or Automatic. If Allocate Code Mode is set to Manual, set Code Number for HS-PDSCH to specify the number of HS-PDSCH codes. If Allocate Code Mode is set to Automatic, set Code Max Number for HSPDSCH to specify the maximum number of HS-PDSCH codes and set Code Min Number for HS-PDSCH to specify the minimum number of HS-PDSCH codes.
Verification Procedure 1. 2. Run the BSC6900 MML command LST UCELLHSDPA to query code allocation mode. On the BSC6900 LMT, click to display Cell Performance Monitoring. Set Monitor Item to Cell Code Tree Monitor and click Submit. The Cell Performance Monitoring tab page is displayed. View the number of codes allocated to the HS-PDSCH in the cell. If Allocate Code Mode is set to Manual, the monitoring window of cell code tree usage shows that the number of codes allocated to the HS-PDSCH remains unchanged. If Allocate Code Mode is set to Automatic, the monitoring window of cell code tree usage shows that the number of codes allocated to the HS-PDSCH varies with service access requests in the cell. For example, the number of codes allocated to the HS-PDSCH increases with the increase of HSDPA access requests and decreases with the decrease of HSDPA access requests.
3.
----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;
65-2
Issue 02 (2011-07-11)
66
Prerequisite
l l
Configuring HSDPA Power Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061004 HSDPA Power Control.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is configured.
Context
After an HSDPA service is introduced, the total downlink transmit power of each cell is classified into common channel power, dedicated physical channel (DPCH) power, and power of HSDPA physical channels (HS-PDSCH and HS-SCCH). To achieve high HSDPA performance, power resources except those reserved for common channels are dynamically allocated to DPCHs and HSDPA physical channels. For R99 services, the DPCH power can be adjusted by means of inner-loop and outer-loop power control. HSDPA channel power resources can be dynamically allocated and adjusted among users by using the NodeB scheduling algorithm. HS-PDSCH power is controlled by the transport format and resource combination (TFRC) algorithm and therefore does not require power control. This feature enables operators to configure the appropriate power control mode of the HS-SCCH, increasing the power efficiency and system capacity and improving the user experience.
Procedure
l Activation Procedure 1. Activating the adaptive HS-SCCH power control based on the channel quality indicator (CQI)
Issue 02 (2011-07-11)
66-1
(1) Run the BSC6900 MML command MOD UCELLHSDPA. In this step, set Allocate Code Mode to Manual, Code Number for HS-PDSCH to 5, and Code Number for HS-SCCH to 1. (2) Run the NodeB MML command SET MACHSPARA. In this step, set HSSCCH Power Control Method in CELL DCH state to CQI. 2. Activating the fixed HS-SCCH power control (1) Run the BSC6900 MML command MOD UCELLHSDPA. In this step, set Allocate Code Mode to Manual, Code Number for HS-PDSCH to 5, and Code Number for HS-SCCH to 1. (2) Run the NodeB MML command SET MACHSPARA. In this step, set HSSCCH Power Control Method in CELL DCH state to FIXED. l Verification Procedure 1. Verifying the adaptive HS-SCCH power control based on the CQI (1) Use an HSUPA-capable UE to set up a PS service over the HS-SCCH. (2) Move the UE between the cell center and the cell edge to view the power change on HS-SCCHs. Expected result: The HS-SCCH power changes with the CQI. 2. Verifying the fixed HS-SCCH power control (1) Use an HSUPA-capable UE to set up a PS service over the HS-SCCH. (2) Move the UE between the cell center and the cell edge to view the power change on the HS-SCCH. Expected result: The HS-SCCH power remains unchanged. l Deactivation Procedure This feature does not need to be deactivated. ----End
Example
//Activating HSUPA Power Control //Setting the adaptive HS-SCCH power control based on the CQI MOD UCELLHSDPA: CellId=111, AllocCodeMode=Manual, HsPdschCodeNum=5, HsScchCodeNum=1; SET MACHSPARA: LOCELL=111, HSSCCHPWRCMINDCH=CQI, HSSCCHFERTRGTINDCH=10; //Setting the fixed HS-SCCH power control MOD UCELLHSDPA: CellId=111, AllocCodeMode=Manual, HsPdschCodeNum=5, HsScchCodeNum=1; SET MACHSPARA: LOCELL=111, HSSCCHPWRCMINDCH=FIXED, SCCHPWR=0;
66-2
Issue 02 (2011-07-11)
67
Prerequisite
Configuring HSDPA Admission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061003 HSDPA Admission Control.
l l
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature 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.
Procedure
l Activation Procedure 1. Activate power resource admission. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Uplink CAC algorithm switch and Downlink CAC algorithm switch according to the network planning. For HSDPA services, run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select related admission algorithms in the Cell CAC algorithm switch parameter. The available admission algorithms are HSDPA_GBP_MEAS, HSDPA_PBR_MEAS, and HSDPA_UU_ADCTRL. Run the BSC6900 MML command MOD UCELLCAC to set power resource admission related parameters and the maximum number of HSDPA users.
Issue 02 (2011-07-11)
67-1

NOTE
If HSDPA_PBR_MEAS is selected in Cell CAC algorithm switch, set Hsdpa streaming PBR threshold and HSDPA best effort PBR threshold in this step.
2.
Activate NodeB credit resource admission. Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, select NODEB_CREDIT_CAC_SWITCH in CAC algorithm switch. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select CRD_ADCTRL in Cell CAC algorithm switch.
3.
Activate Iub interface resource admission. The Iub interface resource admission is mandatory and is activated automatically.
NOTE
The Iub interface bandwidth can be changed by running the BSC6900 MML command MOD IPPATH or MOD AAL2PATH.
Verification Procedure 1. 2. 3. 4. Enable two UEs UE1 and UE2 in idle mode to camp on the test cell, and the test cell must support HSDPA. On the HLR, set PS service type to background or interactive. Run the BSC6900 MML command MOD UCELLCAC to set the maximum number of HSDPA users to 1. Use UE1 to initiate an HSDPA PS service. After the service is set up successfully, check the RRC_RB_SETUP message over the Uu interface. You can view that the new-H-RNTI IE is under the rb-mappinginfo IE, and the value of the dlTransportChannel-Type IE is hsdsch. Use UE2 to initiate an HSDPA PS service. The service should fail to set up. Check the RRC_RB_SETUP message over the Uu interface. You can view that the new-HRNTI IE is not under the rb-mappinginfo IE, and the value of the dlTransportChannel-Type IE is dch. Release all the PS services. Run the BSC6900 MML command MOD UCELLCAC. In this step, set Maximum HSDPA user number of the test cell to 64. Use UE1 and UE2 to initiate an HSDPA PS service. Expected result: Services are set up successfully on UE1 and UE2.
5.
6. 7. 8. l
Deactivation Procedure 1. Deactivate power resource admission. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Uplink CAC algorithm switch and Downlink CAC algorithm switch to ALGORITHM_OFF. 2. Deactivate NodeB credit resource admission. Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, deselect NODEB_CREDIT_CAC_SWITCH in Cell CAC algorithm switch. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select CRD_ADCTRL in Cell CAC algorithm switch. 3. Deactivate Iub interface resource admission.
67-2
The Iub interface resource admission is mandatory and does not need to be deactivated. ----End
Example
//Activating power resource admission MOD UCELLALGOSWITCH: CellId=11, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1&HSDPA_GBP_MEAS-1&HSDPA_PBR_MEAS-1; MOD UCELLCAC: CellId=11, HsdpaStrmPBRThd=70, HsdpaBePBRThd=30, MaxHsdpaUserNum=64, MaxUlTxPowerforConv=24, MaxUlTxPowerforInt=24; //Activating NodeB credit resource admission SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-1; MOD UCELLALGOSWITCH: CellId=11, NBMCacAlgoSwitch=CRD_ADCTRL-1; MOD UCELLCAC: CellId=11, UlHoCeResvSf=SF16, DlHoCeCodeResvSf=SF32; //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;
Issue 02 (2011-07-11)
67-3
68
Prerequisite
l l l
Configuring HSDPA Flow Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061010 HSDPA Flow Control.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated. License The license controlling this feature has been activated.
Context
For each MAC-hs queue, HSDPA Flow Control calculates the pre-allocated Iub bandwidth based on the Uu transmission rate and the amount of data buffered in the NodeB. The Uu transmission rate of the MAC-hs queue is determined by the scheduling algorithm. For each MAC-hs queue, if the Iub transmission rate is higher than the Uu transmission rate, the data packets are buffered. Too much data buffered in the NodeB leads to transmission delay and even packet loss. Therefore, each MAC-hs queue should not have too much data buffered in the NodeB. However, it should retain a certain amount of data to prevent wasting the Uu resources due to not having data to transmit. The procedure for HSDPA Flow Control is briefly described as follows: 1. 2. 3. 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 enable the NodeB HSDPA flow control function. The adaptive flow control algorithm is recommended.
Issue 02 (2011-07-11)
There are four types of HSDPA flow control algorithm as follows: When Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does not adjust the available bandwidth for HSDPA users based on delay and packet loss on the Iub interface. Then, subtracting Iub bandwidth used by R99 from Iub bandwidth configured, the NodeB performs Iub shaping and distributes flow to HSDPA users. When Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB adjusts the available bandwidth for HSDPA users based on delay and packet loss on the Iub interface. Then, considering the data rate on the air interface, the NodeB performs Iub shaping and distributes flow to HSDPA users. When Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not adjust the bandwidth based on delay and packet loss on the Iub interface. The NodeB reports the conditions about the air interface to the RNC, and then the RNC allocates the bandwidth. When Flow Control Switch is set to BW_SHAPING_ONOFF_TOGGLE, the flow control policy for the ports of the NodeB is either DYNAMIC_BW_SHAPING or NO_BW_SHAPING in accordance with the congestion detection mechanism of the NodeB. This flow control algorithm is recommended. l Verification Procedure 1. Choose Monitor > UMTS Monitoring > Connection Performance Monitoring on the BSC6900 LMT. Create UL Throughput Bandwidth and DL Throughput Bandwidth tasks. Assume that the current Iub bandwidth is 4 MHz and the bandwidth usage is 100%. Enable an HSDPA-capable UE1 to access the network and originate a PS service. Record the throughput of UE1. Expected result: The throughput of UE1 is 4 Mbps. 3. Enable an HSDPA-capable UE2 to access the network (with the same configuration as UE1) and originate a download service. Record the throughput of the two UEs. Expected result: The throughput of UE1 decreases after UE2 accesses the network. When the throughput of the two UEs is stable, the total bandwidth of the two UEs is 4 MHz. If user priority, service type and Security Parameter Index (SPI) of the two UEs are the same, the final ratio of the two UEs' throughput is 1:1. l Deactivation Procedure You can deactivate the current algorithm by selecting one of the other flow control algorithms. ----End
2.
Example
//Activating HSDPA Flow Control and setting the flow control mode to adaptive flow control SET HSDPAFLOWCTRLPARA: SRN=0, SN=6, BEAR=ATM, SBT=BASE_BOARD, PT=IMA, PN=0, SWITCH= BW_SHAPING_ONOFF_TOGGLE, TD=2, DR=1, ITM=TERRESTRIAL;
68-2
Issue 02 (2011-07-11)
69
Prerequisite
l l
Configuring HSDPA Mobility Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061006 HSDPA Mobility Management.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated.
Context
This feature enables an HSDPA-capable UE to be handed over to an R99 cell or another HSDPA cell. This feature also enables an HSDPA-capable UE to change cells with a small probability of service interruption.
Procedure
l Activation Procedure 1. The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers are the same for HSDPA users and R99 users. For details, see the following sections: 31 Configuring Intra Frequency Hard Handover 139 Configuring Inter Frequency Hard Handover Based on Coverage 140 Configuring Inter Frequency Hard Handover Based on DL QoS 152 Configuring Inter Frequency Load Balance 144 Configuring Inter-RAT Handover Based on Coverage 145 Configuring Inter-RAT Handover Based on DL QoS
153 Configuring Inter-RAT Handover Based on Service 154 Configuring Inter-RAT Handover Based on Load l l Verification Procedure None Deactivation Procedure This feature does not need to be deactivated.
----End
69-2
Issue 02 (2011-07-11)
70 Configuring HSDPA UE Category 1 to 28
70
Prerequisite
Configuring HSDPA UE Category 1 to 28

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061002 HSDPA UE Category 1 to 28.
l l
Context
This feature can provide proper HSDPA services for the UEs of category 1 to category 28.
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
Issue 02 (2011-07-11)
70-1
71 Configuring Improvement of User Experience in Low Traffic Service
71
Prerequisite
l
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.
Dependencies on Hardware Only BSC6900 supports this function. The BTS3812E is configured with the EBBI or EDLP board. The DBS3800 is configured with the EBBC or EBBCd board. The DBS3900/BTS3900 is configured with the WBBPb or WBBPd board. The UE supports HSPA.
Dependencies on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010612 HSUPA Introduction Package
l l
License The license controlling this feature has been activated. Other Prerequisites The BSC6900 software version should not be earlier than RAN12.0. The NodeB protocol version configured at the BSC6900 should not be earlier than R8. The NodeB software version should not be earlier than RAN12.0.
Context
l l The NodeB detects HSPA services with low traffic, such as gaming services and instant messaging services (such as MSN). The NodeB enables low traffic services to obtain more resources based on the scheduling and flow control principles of HSPA, which reduces delay in low traffic services.
Procedure
l
Issue 02 (2011-07-11)
71 Configuring Improvement of User Experience in Low Traffic Service
1. l
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 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 SET UEQOSENHANCEPARA: ULGOLDUEBPS=10, ULSILVERUEBPS=11, ULCOPPERUEBPS=12, DLGOLDUEBPS=13, DLSILVERUEBPS=14, DLCOPPERUEBPS=15; //Verification procedure LST UEQOSENHANCEPARA:; //Deactivation procedure SET UEQOSENHANCEPARA: ULGOLDUEBPS=0, ULSILVERUEBPS=0, ULCOPPERUEBPS=0, DLGOLDUEBPS=0, DLSILVERUEBPS=0, DLCOPPERUEBPS=0;
71-2
Issue 02 (2011-07-11)
72
Prerequisite
l l l l
Configuring DL 16QAM Modulation
This section describes how to activate, verify, and deactivate the optional feature WRFD-010629 16QAM Modulation.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features WRFD-010610 HSDPA Introduction Package License The license controlling this feature has been activated. Other Prerequisites 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. l l l l The HS-PDSCH is used to carry the HS-DSCH data. The HS-PDSCH may use QPSK or 16QAM modulation symbols. When the UE is in poor radio environment, the transmission can adopt the low-order QPSK modulation mode and small transport blocks to ensure communication quality. When the UE is in good radio environment, the transmission can adopt the high-order 16QAM modulation mode and large transport blocks to achieve high peak rate. The UE of category 10 can support a maximum of 15 HS-PDSCH codes and 16QAM modulation mode. The supported peak rate on the air interface can reach 14.4 Mbit/s.
Procedure
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."
Issue 02 (2011-07-11)
72-1
1. l
Run the NodeB MML command SET MACHSPARA. In this step, set 16QAM Switch to OPEN(open).
NOTE
l For the 16QAM modulation of the HSDPA UE, the NodeB license control item must be enabled. l As defined in 3GPP 25.306, the UE in category 8 can support both QPSK and 16QAM modulation schemes. Only 16QAM modulation, however, enables the throughput of category 8 UE to reach 5 Mbit/s.
NOTE
Only in case of good environment quality of the channel, the throughput of category 8 UE can reach 5 Mbit/s.
Perform the following steps to check whether the download rate can reach 5 Mbit/s. 1. 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 (10 threads) to download given files, which are larger than 1 GB. By monitoring the DL throughput and bandwidth, you find that the PS downloading service is normal and the bit rate is higher than 5 Mbit/s. Run the NodeB MML command SET MACHSPARA. In this step, set 16QAM Switch to CLOSE(close).
----End
Example
//Activating procedure SET MACHSPARA: CME16QAMSW=OPEN; //Deactivating procedure SET MACHSPARA: CME16QAMSW=CLOSE;
72-2
Issue 02 (2011-07-11)
73 Configuring Dynamic Code Allocation Based on NodeB
73
Prerequisite
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.
l l l
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features WRFD-010610 HSDPA Introduction Package License The license controlling this feature has been 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
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 Dynamic Code Switch to OPEN(open). Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to CLOSE(close). Run the BSC6900 MML command MOD UCELLHSDPA. set Allocate Code Mode to Manual.
Issue 02 (2011-07-11)
73-1
set Code Number for HS-PDSCH to 5. 3. 4. 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. Select Service > Trace Management > Interface Trace Task > User from the navigation tree in Maintenance tab on NodeB LMT, select (DL)Hsdpa User Enhanced Schedule Data message, as shown in Figure 73-1.
Figure 73-1 User Tracing
5.
To query the ucMaxPdschCodeNum is 5, as shown in Figure 73-2.
73-2
Issue 02 (2011-07-11)
Figure 73-2 Message Browser
6. 7.
Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to OPEN(open). Trace (DL)Hsdpa User Enhanced Schedule Data message, ucMaxPdschCodeNum is less than the value of 5, it indicates the feature has been enabled. as shown in Figure 73-3.
Issue 02 (2011-07-11)
73-3
Figure 73-3 Message Browser
Deactivation Procedure 1. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to CLOSE(close).
----End
Example
//Activation procedure //Operations on the NodeB side SET MACHSPARA: DYNCODESW=OPEN; //Verification procedure //Operations on the NodeB side SET MACHSPARA: DYNCODESW=CLOSE; //Operations on the BSC6900 side MOD UCELLHSDPA: CellId=0, AllocCodeMode=Manual, HsPdschCodeNum=5; //Operations on the NodeB side SET MACHSPARA: DYNCODESW=OPEN; //Deactivation procedure //Operations on the NodeB side SET MACHSPARA: DYNCODESW=CLOSE;
73-4
Issue 02 (2011-07-11)
74 Configuring HSDPA Enhanced Package
74
Prerequisite
Configuring HSDPA Enhanced Package

This section describes how to activate, verify, and deactivate the optional feature WRFD-010611 HSDPA Enhanced Package.
l l
l l
License The license controlling this feature has been 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: 75 Configuring Scheduling based on EPF and GBR 76 Configuring HSDPA State Transition 77 Configuring HSDPA DRD
74 Configuring HSDPA Enhanced Package

NOTE
HS-DPCCH Preamble Support does not need to be activated, verified, or deactivated.
----End
74-2
Issue 02 (2011-07-11)
75 Configuring Scheduling based on EPF and GBR
75
Prerequisite
l l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features WRFD-010610 HSDPA Introduction Package License The license controlling this feature has been 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
75 Configuring Scheduling based on EPF and GBR
Example
//Activation procedure SET MACHSPARA: SM=EPF; //Verification procedure LST MACHSPARA; //Deactivation procedure SET MACHSPARA: SM=PF;
75-2
Issue 02 (2011-07-11)
76 Configuring HSDPA State Transition
76
Prerequisite
l l
Configuring HSDPA State Transition
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061111 HSDPA State Transition.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package has been configured before this feature is activated.
Context
l l This feature enables the switching between the DCH and HS-DSCH and makes it possible for UEs to enjoy high-speed services. This feature also enables a UE with an ongoing BE service or streaming service to move to the CELL_FACH state to save system resources when the UE does not have data transmission for a long period.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the DRA_HSDPA_STATE_TRANS_SWITCH and DRA_PS_BE_STATE_TRANS_SWITCH check boxes under the parameter Dynamic Resource Allocation Switch. Log in to the BSC6900 LMT and initiate Uu interface message tracing. Set up an HSDPA BE service, and do not perform any data operation for a period of time. Then, search for the RRC_RB_RECFG in the traced Uu interface message. Check the traced data to ensure that the value of the IE rrc-StateIndicator is cell-FACH (1), as shown in Figure 76-1.
Issue 02 (2011-07-11)
76 Configuring HSDPA State Transition
Figure 76-1 RRC_RB_RECFG message
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the DRA_HSDPA_STATE_TRANS_SWITCH and DRA_PS_BE_STATE_TRANS_SWITCH check boxes under the parameter 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;
76-2
Issue 02 (2011-07-11)
77 Configuring HSDPA DRD
77
Prerequisite
l l
Configuring HSDPA DRD
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061112 HSDPA DRD.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010610 HSDPA Introduction Package and WRFD-020400 DRD Introduction Package.
Context
This feature enables HSDPA-suitable services to be established on the HS-DSCH cell as much as possible if a UE is HS-DSCH capable, achieving better service performance.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Direct retry switch to DR_RAB_SING_DRD_SWITCH and DR_RAB_COMB_DRD_SWITCH. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH is set to ON. Expected result: The value of DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH is ON. Run the BSC6900 MML command LST UINTERFREQNCELL to query the interfrequency neighboring cells of cell 1 and whether Blind handover flag is set to TRUE. If Blind handover flag is set to FALSE, run the BSC6900 MML command MOD UINTERFREQNCELL. In this step, set Blind Handover Flag of cell 2 (interHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 77-1
2.
Issue 02 (2011-07-11)
77 Configuring HSDPA DRD
frequency neighboring cell of cell 1) to TRUE. If Blind handover flag is set to TRUE, go to Step 3. 3. 4. 5. Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set DL BE traffic threshold on HSDPA to an appropriate value. Run the BSC6900 MML command MOD UCELLCAC. In this step, set Maximum HSDPA user number of cell 1 to 0. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) to Cell CAC algorithm switch. Enable the UE in cell 1 to originate a PS FTP download service. The value of Maximum HSDPA user number in cell 1 is 0; therefore, the UE is handed over to cell 2 by using directed retry. The Uu message tracing or the UE CDT tracing shows that the RRC_RB_RECFG/RRC_RB_SETUP message is sent to the UE in cell 1 and the RRC_RB_RECFG_CMP/RRC_RB_SETUP_CMP message is sent to the RNC in cell 2.
NOTE
6.
This feature also supports the following scenario: If a UE in an R99 cell (cell 1) originates HSDPA streaming services or BE services, the UE can camp on an HSDPA cell (cell 2) through directed retry. In this scenario, cell 2 is the inter-frequency neighboring cell for blind handover of cell 1 and admission to cell 2 is allowed.
Deactivation Procedure 1. The feature does not need to be deactivated.
----End
Example
//Activating HSDPA DRD SET UCORRMALGOSWITCH: DrSwitch= DR_RAB_SING_DRD_SWITCH-1; SET UCORRMALGOSWITCH: DrSwitch= DR_RAB_COMB_DRD_SWITCH-1; //Verifying HSDPA DRD MOD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=2, NCellId=2, BlindHoFlag=TRUE; SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D384; MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=0; MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1;
77-2
Issue 02 (2011-07-11)
78 Configuring Interactive and Background Traffic Class on HSDPA
78
Prerequisite
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.
l l
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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.
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 78-1.
Issue 02 (2011-07-11)
78-1
78 Configuring Interactive and Background Traffic Class on HSDPA
Figure 78-1 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;
78-2
Issue 02 (2011-07-11)
79 Configuring HSDPA over Iur
79
Prerequisite
l l l l License
Configuring HSDPA over Iur
This section describes how to activate, verify, and deactivate the optional feature WRFD-010651 HSDPA over Iur.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package has been configured before this feature is activated. The license controlling this feature has been activated. Other Prerequisites The neighboring RNC supports this feature.
Context
This feature enables HSDPA services to be carried on the Iur interface and provides continuous HSDPA services for UEs moving between BSC6900s.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UEXT3GCELL to configure the neighboring RNC's cell with HSDSCH and Fractional-Dedicated Physical Control Channel (F-DPCH). In this step, select the HSDSCH support indicator and F-DPCH support indicator check boxes under the parameter Cell Capability Container. Run the BSC6900 MML command MOD UNRNC. In this step, set Hsdpa cap ind over IUR for NRNC to ON. Verify that the feature HSDPA over Iur has been activated by performing the following operations: Run the BSC6900 MML command LST UNRNC to query the configuration of the neighboring RNC.
2. l
79 Configuring HSDPA over Iur
Run the BSC6900 MML command LST UEXT3GCELL to query the configuration of the neighboring RNC's cell. 2. Verify that an HSDPA service has been set up by performing the following operations: Configure the neighboring RNC and its cell with the HSDPA function. Establish an HSDPA service under the serving RNC. The serving cell changes to a cell under the neighboring RNC. If the RNSAP_RL_SETUP_REQ message traced on the Iur interface contains HSDPA-related information elements, an HSDPA service has been set up successfully. l Deactivation Procedure 1. 2. Run the BSC6900 MML command MOD UNRNC. In this step, set Hsdpa cap ind over IUR for NRNC to OFF. Run the BSC6900 MML command MOD UEXT3GCELL. In this step, deselect the HSDSCH support indicator and F-DPCH support indicator check boxes under the parameter Cell Capability Container.
----End
Example
//Activating HSDPA over Iur 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;
79-2
Issue 02 (2011-07-11)
80 Configuring SRB over HSDPA
80
Prerequisite
l
Configuring SRB over HSDPA
This section describes how to activate, verify, and deactivate the optional feature WRFD-010652 SRB over HSDPA.
Dependencies on Hardware Requirement for the BSC6900 This feature does not depend on the hardware. Requirements for the NodeB The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI, or EDLP board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features The WRFD-010610 HSDPA Introduction Package feature must be configured before this feature is configured.
l l
License The license controlling this feature has been activated. Others The UE complies with the specifications of 3GPP Release 6 or higher versions and supports fractional DPCH (F-DPCH) or E-FDPCH.
Context
Using F-DPCH multiplexing, this feature enables downlink signaling radio bearers (SRBs) of multiple users to be carried over HSDPA. This helps reduce downlink code resource consumption and call setup delay. During radio access bearer (RAB) setup, SRBs can be carried over HSDPA only when all the downlink services of the UE are carried on the HSDPA channels. During radio resource control (RRC) connection setup, this feature can be activated by performing the following operations:
Procedure
l Activation Procedure 1. 2. Run the MML command SET UFRCCHLTYPEPARA on the BSC6900. In this step, set Type of Channel Preferably Carrying Signaling RB to HSDPA or HSPA. Run the MML command SET UFRCCHLTYPEPARA on the BSC6900 to set the phase at which this feature is activated by means of the Effective Flag of Signaling RB Channel Type parameter.
NOTE
l If Effective Flag of Signaling RB Channel Type is set to False, this feature is activated during RAB setup. Recommended Value is False. l If Effective Flag of Signaling RB Channel Type is set to TRUE, this feature is activated during RRC connection setup.
3.
Run the MML command MOD UCELLALGOSWITCH on the BSC6900 to set the E_F_DPCH is activated by means of the Cell Hspa Enhanced function switch parameter.
NOTE
l If Cell Hspa Enhanced function switch is set to E_F_DPCH_ON, E_F_DPCH is enabled. l If Cell Hspa Enhanced function switch is set to E_F_DPCH_OFF, E_F_DPCH is disabled.
Verification Procedure 1. Log in to the BSC6900 LMT to enable Uu interface tracing. In the displayed dialog box, select RRC_RB_SETUP, as shown in Figure 80-1. Figure 80-1 Uu Interface Trace dialog box
2.
To verify whether this feature is activated , view the information element (IE) dlTransportChannelType and rb-Identity in the RRC_RB SETUP message from the Uu interface trace data.
80-2
Issue 02 (2011-07-11)
If the value of dl-TransportChannelType is hsdsch, as shown in Figure 80-2, and the value of rb-Identity is less than or equal to 4, as shown in Figure 80-3, this feature is activated. Figure 80-2 Value of the dl-TransportChannelType IE
Figure 80-3 Value of the rb-Identity IE
Deactivation Procedure 1. Run the MML command SET UFRCCHLTYPEPARA on the BSC6900. In this step, set Type of Channel Preferably Carrying Signaling RB to HSUPA or DCH.
----End
Example
//Activating SRB over HSDPA //Activating LICENSE SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH3=SRB_OVER_HSDPA-1; //Setting the type of channel on which SRBs are preferably carried with SrbChlType set to HSDPA SET UFRCCHLTYPEPARA: SrbChlType=HSDPA; //Setting the type of channel on which SRBs are preferably carried with SrbChlTypeRrcEffectFlag set to False SET UFRCCHLTYPEPARA: SrbChlTypeRrcEffectFlag=False; //setting the E_F_DPCH function MOD UCELLALGOSWITCH: CellId=1, HspaEnhSwitch=E_F_DPCH_ON;
Issue 02 (2011-07-11)
80-3

//Deactivating SRB over HSDPA
//Setting the type of channel on which SRBs are preferably carried with SrbChlType set to DCH SET UFRCCHLTYPEPARA: SrbChlType=DCH;
80-4
Issue 02 (2011-07-11)
81 Configuring CQI Adjustment Based on Dynamic BLER Target
81
Prerequisite
Configuring CQI Adjustment Based on Dynamic BLER Target

This section describes how to activate, verify, and deactivate the basic feature WRFD-030010 CQI Adjustment Based on Dynamic BLER Target.
Dependencies on Hardware The BTS3812E and BTS3812AE are configured with the EBBI, EBOI, or EDLP board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
l l
Dependencies on Other Features WRFD-010610 HSDPA Introduction Package License The license that supports this feature is activated.
Context
With this feature, the NodeB can dynamically select the optimum BLER target value based on the channel quality fluctuation of HSDPA users. The NodeB then adjusts the Channel Quality Indicator (CQI) accordingly, improving user throughput and cell throughput.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET MACHSPARA. In this step, set CQI Adjust Algorithm Switch of non-Conversational Service to CQI_ADJ_BY_DYN_BLER (CQI Adjusted by Dynamic BLER). Run the NodeB MML command LST MACHSPARA. In this step, check that CQI Adjust Algorithm Switch of non-Conversational Service is set to CQI_ADJ_BY_DYN_BLER. Query the CQI and TBS reported by UEs in the NodeB log. If the data buffer has sufficient space and a CQI corresponds to multiple TBSs, this feature has been
2.
Issue 02 (2011-07-11)
81 Configuring CQI Adjustment Based on Dynamic BLER Target
activated. If the data buffer has sufficient space and a CQI corresponds only to one TBS, this feature has not been activated. l Deactivation Procedure 1. Run the NodeB MML command SET MACHSPARA. In this step, set CQI Adjust Algorithm Switch of non-Conversational Service to NO_CQI_ADJ(Not CQI Adjust Algorithm).
----End
Example
//Activating CQI Adjustment Based on Dynamic BLER Target SET MACHSPARA: LOCELL=0, CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER; //Verifying CQI Adjustment Based on Dynamic BLER Target LST MACHSPARA: LOCELL=0; //Deactivating CQI Adjustment Based on Dynamic BLER Target SET MACHSPARA: CQIADJALGOFNONCON=NO_CQI_ADJ;
81-2
Issue 02 (2011-07-11)
82 Configuring HSUPA Introduction Package
82
Prerequisite
l
Configuring HSUPA Introduction Package
This section describes how to activate, verify, and deactivate the optional feature WRFD-010612 HSUPA Introduction Package.
Dependencies on Hardware The NBBI and the NULP do not support this feature. The UE supports the HSUPA function.
l l
Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
This feature enables the system to process HSUPA services, therefore increasing the uplink rate and system throughput. It provides basic functions of HSUPA.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command ADD UCELLHSUPA to add HSUPA functions of a 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 verify that the HSUPA function of the cell is activated. 2.
Issue 02 (2011-07-11)
Establish a PS service.
82 Configuring HSUPA Introduction Package
The IE E-DCH FDD information in the RL SETUP message on the Iub interface and the IE rb-mappinginfo in the RRC_RB_SETUP message on the Uu interface should indicate that the service has been set up and carried on the E-DCH. 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 functions of a cell.
Example
//Activating HSUPA Introduction Package ADD UCELLHSUPA: CellId=111; ACT UCELLHSUPA: CellId=111; //Verifying HSUPA Introduction Package DSP UCELL: DSPT=BYCELL, CellId=111; //Deactivating HSUPA Introduction Package DEA UCELLHSUPA: CellId=111; RMV UCELLHSUPA: CellId=111;
82-2
Issue 02 (2011-07-11)
83
Prerequisite
Configuring HSUPA Admission Control

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061202 HSUPA Admission Control.
l l
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package must be configured before this feature 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, improving the utilization of system resources and ensuring QoS of admitted users.
Procedure
l Activation Procedure 1. Activating Power Resource Admission (1) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select an uplink Call Admission Control (CAC) algorithm through the parameter Uplink CAC algorithm switch and a downlink CAC algorithm through the parameter Downlink CAC algorithm switch. (2) For HSUPA services, run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select the corresponding admission algorithm switches from the Cell CAC algorithm switch drop-down list, such as HSUPA_PBR_MEAS(HSUPA PBR Meas Algorithm), HSUPA_EDCH_RSEPS_MEAS(HSUPA EDCH RSEPS Meas Algorithm), and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm).
(3) Run the BSC6900 MML command MOD UCELLCAC to set power resource admission parameters. 2. Activating NodeB Credit Resource Admission (1) Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, set CAC algorithm switch to NODEB_CREDIT_CAC_SWITCH(NodeB Credit CAC Switch). (2) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Cell CAC algorithm switch to CRD_ADCTRL(Credit Admission Control Algorithm) to turn on the cell-oriented credit resource admission switch. (3) Run the BSC6900 MML command MOD UCELLCAC. In this step, set the NodeB credit resource admission parameters Ul handover credit reserved SF and Dl handover credit and code reserved SF to appropriate values. 3. Activating Iub Resource Admission Iub resource admission is unconditionally performed and does not need to be activated.
NOTE
Run the BSC6900 MML command MOD IPPATH or MOD AAL2PATH to modify the Iub bandwidth.
Verification Procedure 1. 2. 3. 4. UE1 and UE2 are in idle state and camp on CELL_A11. CELL_A11 supports HSUPA. On the HLR, set the PS service type to background or interactive. Run the BSC6900 MML command MOD UCELLCAC to set the maximum number of HSUPA users supported by CELL_A11 to 1. Establish an HSUPA PS service on UE1, and then check the rb-mappinginfo information element in the RRC_RB_SETUP message traced over the Uu interface. The value of ul-TrCH-Type is e-dch. Establish an HSUPA PS service on UE2, and then check the rb-mappinginfo information element in the RRC_RB_SETUP message traced over the Uu interface. The value of rrc-Stateinditator is CELL_DCH. Release all PS services. Run the BSC6900 MML command MOD UCELLCAC to set Maximum HSUPA user number of CELL_A11 to 20. Establish an HSUPA PS service on UE1 and UE2 respectively. Expected result: An HSUPA PS service is successfully established on UE1 and UE2 respectively. 9. Run the following command to check whether Iub resource admission is activated. Run the BSC6900 MML command DSP IPPATH or DSP AAL2PATH to check whether any bandwidth is occupied.
5.
6. 7. 8.
Deactivation Procedure 1. To disable Power Resource Admission, do as follows: 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, do as follows:
83-2
(1) Run the BSC6900 MML command SET UCACALGOSWITCH. In this step, deselect the NodeB credit resource admission switch NODEB_CREDIT_CAC_SWITCH(NodeB Credit CAC Switch) from the CAC algorithm switch drop-down list. (2) Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect the cell-oriented credit resource admission switch CRD_ADCTRL(Credit Admission Control Algorithm) from the Cell CAC algorithm switch drop-down list. 3. Deactivating Iub Resource Admission Iub resource admission is unconditionally performed and does not need to be deactivated.
----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; //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;
Issue 02 (2011-07-11)
83-3
84
Prerequisite
l l
Configuring HSUPA Power Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061203 HSUPA Power Control.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The features WRFD-010612 HSUPA Introduction Package and WRFD-020504 Inner Loop Power Control must be configured before this feature is activated.
Context
This feature increases the system power efficiency, reduces the uplink and downlink interference, and improves the system capacity by controlling the power on HSUPA physical channels.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET MACEPARA. In this step, set E-AGCH HPC Parameters, E-RGCH HPC Parameters for Service Radio Links Set, and EHICH HPC Parameters for Service Radio Links Set to YES. Run the NodeB MML command SET MACEPARA. In this step, set E-AGCH HPC Mode, E-RGCH HPC Mode for Service Radio Links Set, and E-HICH HPC Mode for Service Radio Links Set to FOLLOW_TPC. Run the NodeB MML command SET MACEPARA. In this step, set E-AGCH Power Offset(0.25dB), E-RGCH Power Offset for Service Radio Links Set (0.25dB), E-HICH Power Offset for Service Radio Links Set(0.25dB), and EHICH Power Offset for Single Radio Link(0.25dB) to appropriate values according to the network plan.
2.
3.
Issue 02 (2011-07-11)
84-1
4.
Run the BSC6900 MML command MOD UTYPRABHSUPAPC to modify power control parameters related to HSUPA services. In this step, set E-RGCH 2-IndexStep Threshold to 9 and E-RGCH 3-Index-Step Threshold to 12. Run the BSC6900 MML command MOD UTYPRABOLPC. In this step, change the number of target retransmissions for large and small retransmissions related to HSUPA services according to the network plan. On the BSC6900 LMT, open the Monitor page. Then, double-click Connection Performance Monitoring under UMTS Monitoring. In the displayed dialog box, select OLPC and specify the IMSI. Use an HSUPA-capable UE to set up a PS service over the enhanced DCH (E-DCH). Move the UE between the cell center and the cell edge. View the monitor items related to the number of E-DCH retransmissions in the OLPC area. The values of the monitor items change with UE movement. View the power change on each HSUPA channel. If static power control is used, the channel power remains unchanged. If dynamic power control is used: When the UE is moving away from the antenna, the transmit power of the EAGCH increases. When the UE is moving towards the antenna, the transmit power of the EAGCH decreases.
5.
2. 3. 4. 5.
----End
Example
//Activating HSUPA Power Control //Setting the power control mode SET MACEPARA: LOCELL=111, EAGCHPCPARA=YES, SERGCHPCPARA=YES, SEHICHPCPARA=YES; SET MACEPARA: LOCELL=111, EAGCHPCMOD=FOLLOW_TPC, SERGCHPCMOD=FOLLOW_TPC, SEHICHPCMOD=FOLLOW_TPC; SET MACEPARA: LOCELL=111, EAGCHPWROFFSET=142, SERGCHPWROFFSET=100, SEHICHPWROFFSET=96, SRLEHICHPWROFFSET=88; //Modifying power control parameters related to HSUPA services MOD UTYPRABHSUPAPC: RabIndex=48, SubflowIndex=0, TrchType=TRCH_EDCH_2MS, Ul16QamInd=FALSE, UlL2EnhanceInd=FALSE, EdPwrInterpolationInd=FALSE, ERgch2IndStpThs=9, ERgch3IndStpThs=12, UlEcBoostingInd=FALSE; //Changing the number of target retransmissions for large and small retransmissions related to HSUPA services MOD UTYPRABOLPC: RabIndex=48, SubflowIndex=0, TrchType=TRCH_EDCH_2MS, DelayClass=1, EdchTargetLittleRetransNum=12, EdchTargetLargeRetransNum=20;
84-2
Issue 02 (2011-07-11)
85 Configuring HSUPA Mobility Management
85
Prerequisite
l l
Configuring HSUPA Mobility Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061204 HSUPA Mobility Management.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package must be configured before this feature is activated.
Context
This feature enables an HSUPA-capable UE to be handed over to an R99 cell or another HSUPA cell. This feature also enables an HSUPA-capable UE to change cells with a small probability of service interruption.
Procedure
l Activation Procedure 1. The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers are the same for HSUPA users and R99 users. For the activation procedures for configuring HSUPA Mobility Management, see the following sections: 31 Configuring Intra Frequency Hard Handover 139 Configuring Inter Frequency Hard Handover Based on Coverage 140 Configuring Inter Frequency Hard Handover Based on DL QoS 152 Configuring Inter Frequency Load Balance 144 Configuring Inter-RAT Handover Based on Coverage
85 Configuring HSUPA Mobility Management
145 Configuring Inter-RAT Handover Based on DL QoS 153 Configuring Inter-RAT Handover Based on Service 154 Configuring Inter-RAT Handover Based on Load 2. 3. ----End Verification Procedure None. Deactivation Procedure This feature does not need to be deactivated.
85-2
Issue 02 (2011-07-11)
86
Prerequisite
l l
Configuring HSUPA DCCC
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061208 HSUPA DCCC.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The features WRFD-010612 HSUPA Introduction Package and WRFD-021101 Dynamic Channel Configuration Control (DCCC) must be configured before this feature is activated.
Context
HSUPA DCCC can dynamically adjust the minimum spreading factor (SF) code of HSUPA based on the user throughput and flexibly switch the UE state based on the user traffic, which improves the Channel Element (CE) resource utilization and system efficiency.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select DRA_HSUPA_DCCC_SWITCH from the Dynamic Resource Allocation Switch drop-down list. Optional: If the NodeB does not enable dynamic CE, run the BSC6900 MML command MOD UNODEBALGOPARA. In this step, set HSUPA Credit Consume Type to MBR. 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 so that the data rate of HSUPA services on the EDCH can increase or decrease.
2.
3.
Issue 02 (2011-07-11)
86-1

NOTE
After the preceding optional step is performed, the data rate of HSUPA services on the EDCH can increase or decrease as required. If the data rate of HSUPA services on the EDCH is expected to increase only, select RATE_UP_ONLY_ON_EDCH from the HSUPA DCCC Strategy dropdown list.
4.
Optional: Run the BSC6900 MML command SET UEDCHRATEADJUSTSET. In this step, set HSUPA Uplink Rate Adjust Set to a data rate set for rate adjustment by the HSUPA DCCC algorithm.
NOTE
The preceding optional step sets the available data rate set of the HSUPA DCCC algorithm. After the step is performed, HSUPA services can be of any data rate in the data rate set by using the HSUPA DCCC algorithm.
Verification Procedure 1. On the BSC6900 LMT, display the Monitor page. In the Monitor Navigation Tree, double-click UMTS Monitoring > Connection Performance Monitoring. Select UL Throughput Bandwidth and DL Throughput Bandwidth respectively from the Monitor Item drop-down list to create two monitoring tasks. Make the UE establish an HSUPA Best Effort (BE) service. After the service is established, layer 3 of the RNC sends an uplink throughput measurement control message to layer 2. Upload a large file for a period of time. Then, view the RRC_RB_RECFG message on the Uu interface and check that the data rate increases. In UL Throughput Bandwidth of Connection Performance Monitoring, the bandwidth increases. Stop the data upload and wait for a period of time. Then, view the RRC_RB_RECFG message on the Uu interface and check that the data rate decreases. In UL Throughput Bandwidth of Connection Performance Monitoring, the bandwidth decreases. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect DRA_HSUPA_DCCC_SWITCH from the Dynamic Resource Allocation Switch drop-down list.
2.
3.
4.
----End
Example
//Activating HSUPA DCCC SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1; MOD UNODEBALGOPARA: NodeBName="NodeB1", HsupaCeConsumeSelection=MBR; SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH; SET UEDCHRATEADJUSTSET: EdchRateAdjustSet=RATE_8KBPS-0&RATE_16KBPS-0&RATE_32KBPS-0&RATE_64KBPS-0& RATE_128KBPS-1&RATE_144KBPS-0&RATE_256KBPS-1&RATE_384KBPS-0&RATE_608KBPS1&RATE_1280KBPS-0&RATE_2048KBPS-0&RATE_2720KBPS-0&RATE_5440KBPS-0&RATE_11 480KBPS-0; //Deactivating HSUPA DCCC SET UCORRMALGOSWITCH: DraSwitch= DRA_HSUPA_DCCC_SWITCH-0;
86-2
Issue 02 (2011-07-11)
87
Prerequisite
l l l
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.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package must be configured before this feature is activated. License The license controlling this feature has been activated.
Context
This feature enables a single HSUPA cell to serve a maximum of 20 HSUPA users simultaneously. After the maximum is reached, the cell attempts to establish services on DCHs to accommodate additional users.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) from the drop-down list of Cell CAC algorithm switch. Run the BSC6900 MML command MOD UCELLCAC to set the maximum number of HSUPA users supported by the cell to 20. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number. Use UEs to access the cell one by one. Then, make UEs establish PS services, for example, upload files through FTP. Expected result: Each UE establishes PS services successfully.
2. l
2.
Issue 02 (2011-07-11)
If the number of UEs is less than or equal to 20, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels. If the number of UEs is greater than 20, HSPA services of the excessive UEs are carried on R99 channels. 3. View the maximum number of users indicated by the counter VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
The 20 HSUPA users referred to in this feature are of the SRB Over HSPA type.
----End
Example
/*Activation procedure*/ //Disabling the admission control function in an HSPA cell on the Uu interface MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0; //Setting the maximum number of HSUPA users supported by the cell to 20 MOD UCELLCAC: CellId=111, MaxHsupaUserNum=20;
87-2
Issue 02 (2011-07-11)
88 Configuring E-AGCH Power Control (Based on CQI or HS-SCCH)
88
Prerequisite
l l
Configuring E-AGCH Power Control (Based on CQI or HS-SCCH)
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061401 E-AGCH Power Control (Based on CQI or HS-SCCH).
Dependencies on Hardware This feature does not depend on hardware. Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.
Context
This feature enables the RAN to use the channel quality indicator (CQI) and HS-SCCH information reported by UEs as a reference, therefore effectively reducing the power consumption of the E-AGCH.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET MACEPARA to set Mac-e parameters with the following parameter settings: E-AGCH HPC Parameters is set to YES(YES). E-AGCH HPC Mode is set to CQI_BASED(Tx Pwr Ctr based on CQI) or HSSCCH_BASED(Tx Pwr Ctr based on HS-SCCH). E-AGCH Power Offset(0.25dB), E-AGCH Max Power(0.1dB), and E-AGCH Min Power(0.1dB) are set to values that comply with the data plan. l Verification Procedure 1.
Issue 02 (2011-07-11)
Use an HSUPA-capable UE to perform PS services over the E-DCH.

88 Configuring E-AGCH Power Control (Based on CQI or HS-SCCH)
2.
Move the UE and observe power changes on each channel carrying HSUPA services. Expected result: When the UE moves away from the antenna, the transmit power of the E-AGCH increases. When the UE moves towards the antenna, the transmit power of the E-AGCH decreases.
Deactivation Procedure 1. Run the NodeB MML command SET MACEPARA. In this step, set E-AGCH HPC Parameters to NO(NO).
----End
Example
//Activation procedure SET MACEPARA: SCHEDULEPARA=NO, EAGCHPCPARA=YES, EAGCHPCMOD=CQI_BASED, EAGCHPWROFFSET=100, MAXAGCHPOWER=100, MINAGCHPOWER=-200, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; //Deactivation procedure SET MACEPARA: SCHEDULEPARA=NO, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
88-2
Issue 02 (2011-07-11)
89 Configuring HSUPA 2ms TTI
89
Prerequisite
l
Configuring HSUPA 2ms TTI
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061403 HSUPA 2ms TTI.
Dependencies on Hardware Dependencies on BSC6900 Hardware This feature does not depend on the BSC6900 hardware. Dependencies on NodeB Hardware The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI, EULP, or EULPd board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010612 HSUPA Introduction Package and WRFD-010636 SRB over HSUPA.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE is of HSUPA category 6, 7, 8, or 9.
Context
This feature enables a single user to obtain a higher uplink throughput and a shorter delay.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter Service Mapping Strategy Switch.
Issue 02 (2011-07-11)
89 Configuring HSUPA 2ms TTI
2.
Run the BSC6900 MML command SET UFRC. In this step, set Rate Threshold of Streaming Services on 2ms TTI of HSUPA and Ratethreshold of BE on 2ms TTI of HSUPA to appropriate values based on the network plan. Configure SRB over HSPA by referring to 95 Configuring SRB over HSUPA. Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify that the MAP_HSUPA_TTI_2MS_SWITCH check box is selected. Use an HSPA-capable UE to establish an HSUPA service. If the RRC_RB_SETUP message shown in Figure 89-1 is traced on the Uu interface, an HSUPA service with 2 ms TTI has been set up on the E-DCH. Figure 89-1 HSUPA service with 2 ms TTI carried on the E-DCH
3. l 1. 2.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter Service Mapping Strategy Switch.
----End
Example
//Activating HSUPA 2ms TTI SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; SET UFRC: StreamHsupa2msTtiRateThs=D64, BeHsupa2msTtiRateThs=D64; //Configuring SRB over HSPA SET UFRCCHLTYPEPARA: SrbChlType=HSPA; //Deactivating HSUPA 2ms TTI SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0;
89-2
Issue 02 (2011-07-11)
90 Configuring HSUPA 2 ms/10 ms TTI Handover
90
Prerequisite
l
Configuring HSUPA 2 ms/10 ms TTI Handover
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover.
Dependencies on Hardware Dependencies on BSC6900 Hardware This feature does not depend on the BSC6900 hardware. Dependencies on NodeB Hardware The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI, EULP, or EULPd board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features The feature WRFD-010614 HSUPA Phase 2 has been configured before this feature is activated.
Context
This feature enables 2 ms TTI UEs to obtain the best performance.
Procedure
l Activation Procedure This feature is license controlled. It takes effect after its license is activated. For details about how to activate the license, see 3.1 Activating the BSC6900 License. l Verification Procedure This feature does not need to be verified.
90 Configuring HSUPA 2 ms/10 ms TTI Handover
----End
Example
//Activating HSUPA 2 ms/10 ms TTI Handover SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH3=HSUPA_2ms_10ms-1;
90-2
Issue 02 (2011-07-11)
91 Configuring HSUPA 5.74Mbps per User
91
Prerequisite
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.
Dependencies on Hardware Dependencies on BSC6900 Hardware This feature does not have any special requirements for hardware. Dependencies on NodeB Hardware BTS3812E, BTS3812A, and BTS3812AE are configured with the EBBI, EBOI, EULP, or EULPd board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features The feature WRFD-010636 SRB over HSUPA has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Other Prerequisites The CN supports the UE rate of 5.74 Mbit/s or higher in the uplink. The UE is of HSUPA category 6, 7, 8, or 9.
Context
This feature enables the HSUPA rate at the MAC layer to reach a maximum of 5.74 Mbit/s, which is the HSUPA peak rate defined in 3GPP technical specifications.
Procedure
l Activation Procedure 1. Optional: Run the BSC6900 MML command MOD TRMMAP to configure the TRM mapping table based on the network plan. The TRM mapping table contains the mapping relationship between the transmission mode and the service type.
Issue 02 (2011-07-11)
91 Configuring HSUPA 5.74Mbps per User

NOTE
The BSC6900 provides a default TRM mapping table. Use an appropriate mapping policy when configuring the TRM mapping table. For example, if Transport Type is set to ATM, all HSUPA services, including signaling services, must be carried by AAL2PATH that supports HSUPA services.
2.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable HSUPA services to use the 2 ms TTI. In this step, set Service Mapping Strategy Switch to MAP_HSUPA_TTI_2MS_SWITCH. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRBs to be carried on HSPA channels. In this step, set Type of Channel Preferably Carrying Signaling RB to HSPA (Uplink is preferably carried on E-DCH and downlink is preferably carried on HS-DSCH). Use an HSPA-capable UE to establish a PS service on the E-DCH and HS-DSCH. Start Uu interface tracing on the BSC6900 LMT. The RRC_RB_SETUP message shows that the 2 ms TTI is used in the uplink and the maximum channelization code IE is 2SF2+2SF4. The real-time monitoring result of UL Throughput & Bandwidth on the BSC6900 side shows that the bandwidth is 5440 kbit/s and that upload through FTP is normal. Run the BSC6900 MML command SET UCORRMALGOSWITCH to prohibit the 2 ms TTI from being used on HSUPA channels. In this step, deselect the MAP_HSUPA_TTI_2MS_SWITCH check box under the Service Mapping Strategy Switch parameter. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to prohibit SRBs from being carried on HSPA channels. In this step, set Type of Channel Preferably Carrying Signaling RB to DCH(Both uplink and downlink are preferably carried on DCH).
3.
3. l
2.
----End
Example
//Activating HSUPA 5.74Mbps per User SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; SET UFRCCHLTYPEPARA: SrbChlType=HSPA; //Deactivating HSUPA 5.74Mbps per User SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0; SET UFRCCHLTYPEPARA: SrbChlType=DCH;
91-2
Issue 02 (2011-07-11)
92 Configuring Streaming Traffic Class on HSUPA
92
Prerequisite
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.
l l
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE supports streaming services.
Context
This feature allows PS streaming services to be carried on E-DCHs, thereby increasing the utilization of cell resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the MAP_PS_STREAM_ON_HSUPA_SWITCH check box under the parameter Service Mapping Strategy Switch. Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set UL streaming traffic threshold on HSUPA to an appropriate value. The default value is 256 kbit/s.
2.
Issue 02 (2011-07-11)
92-1
92 Configuring Streaming Traffic Class on HSUPA
1.
Run the BSC6900 MML command LST UCORRMALGOSWITCH. Ensure that the MAP_PS_STREAM_ON_HSUPA_SWITCH check box under the parameter Service Mapping Strategy Switch is selected. Use the UE to establish a PS service. Expected result: The traffic type in the RAB assignment message is streaming, and the RB setup message traced on the Uu interface indicates that the PS service is established on an E-DCH. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the MAP_PS_STREAM_ON_HSUPA_SWITCH check box under the parameter Service Mapping Strategy Switch.
2. 3.
----End
Example
//Activating Streaming Traffic Class on HSUPA SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSUPA_SWITCH-1; SET UFRCCHLTYPEPARA: UlStrThsOnHsupa=D256; //Deactivating Streaming Traffic Class on HSUPA SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSUPA_SWITCH-0;
92-2
Issue 02 (2011-07-11)
93
Prerequisite
l l
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010612 HSUPA Introduction Package, WRFD-010614 HSUPA Phase 2, and WRFD-010636 SRB over HSUPA.
Context
This feature enables a single HSUPA cell to serve a maximum of 60 HSUPA users simultaneously. After the maximum number of users is reached, the cell attempts to establish services on DCHs to accommodate additional users.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) from the drop-down list of Cell CAC algorithm switch. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources to E-AGCHs and E-RGCHs. Run the BSC6900 MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSUPA users to 60.
2. 3. 4. l
Issue 02 (2011-07-11)
1.
On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number. Use UEs to access the cell one by one. Then, make UEs establish PS services, for example, upload files through FTP. Expected result: Each UE establishes PS services successfully. If the number of UEs is less than or equal to 60, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels. If the number of UEs is greater than 60, HSPA services of the excessive UEs are carried on R99 channels.
2.
3.
View the maximum number of users indicated by the counter VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
----End
Example
/*Activation procedure*/ //Disabling the admission control function in an HSPA cell on the Uu interface 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 to E-AGCHs and E-RGCHs MOD UCELLHSUPA: CellId=111, EagchCodeNum=3, ErgchEhichCodeNum=3; //Stopping reserving uplink and downlink credit resources and setting the maximum number of HSUPA users to 60 MOD UCELLCAC: CellId=111, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF, MaxHsupaUserNum=60;
93-2
Issue 02 (2011-07-11)
94 Configuring HSUPA over Iur
94
Prerequisite
l l l License
Configuring HSUPA over Iur
This section describes how to activate, verify, and deactivate the optional feature WRFD-010635 HSUPA over Iur.
Dependencies on Hardware The neighboring RNC supports this feature. Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package has been configured before this feature is activated. The license controlling this feature has been activated.
Context
This feature enables HSUPA services to be carried on the Iur interface so that continuous HSUPA services can be provided for UEs moving between BSC6900s.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UEXT3GCELL to configure a neighboring RNC's cell with the E-DCH function. In this step, set Cell Capability Container to an appropriate value. Run the BSC6900 MML command MOD UNRNC to configure data about the neighboring RNC. In this step, set Hsupa cap ind over IUR for NRNC to ON to enable HSUPA services to be carried on the Iur interface. Verify that the feature HSUPA over Iur has been activated by performing the following operations: Run the BSC6900 MML command LST UNRNC to query the configuration of the neighboring RNC. Run the BSC6900 MML command LST UEXT3GCELL to query the configuration of the neighboring RNC's cell.
2.
94 Configuring HSUPA over Iur
2.
Verify that an HSUPA service has been established on the Iur interface by performing the following operations: Configure the neighboring RNC and its cell with the HSUPA function. Establish an HSUPA service under the serving RNC. Add a cross-Iur soft handover link. If the RNSAP_RL_SETUP_REQ message traced on the Iur interface contains HSUPA-related information elements, an HSUPA service has been set up successfully.
Deactivation Procedure 1. Run the BSC6900 MML command MOD UNRNC. In this step, set Hsupa cap ind over IUR for NRNC to OFF.
----End
Example
//Activation procedure MOD UEXT3GCELL: NRncId=2, CellId=2, CellCapContainerFdd=EDCH_SUPPORT-1&EDCH_2SF4_SUPPORT-1&EDCH_HARQ_IR_COMBI N_SUPPORT-1; 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;
94-2
Issue 02 (2011-07-11)
95 Configuring SRB over HSUPA
95
Prerequisite
l BSC6900
Configuring SRB over HSUPA
This section describes how to activate, verify, and deactivate the optional feature WRFD-010636 SRB over HSUPA.
Dependencies on Hardware This feature does not depend on the hardware. Requirements for the NodeB The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI, or EDLP board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features The WRFD-010612 HSUPA Introduction Package feature must be configured before this feature is configured.
Context
This feature provides high signaling rate and shortens call setup delay. Compared with the function of carrying SRBs on DCHs, this feature saves code resources and reduces cell load.
Procedure
l Activation Procedure 1. Run the MML command SET UFRCCHLTYPEPARA on the BSC6900. In this step, set Type of Channel Preferably Carrying Signaling RB to HSUPA (UL_EDCH,DL_DCH) or HSPA(UL_EDCH,DL_HSDSCH).
l
Issue 02 (2011-07-11)
95 Configuring SRB over HSUPA
1. 2.
Run the MML command LST UFRCCHLTYPEPARA on the BSC6900 to query whether the SRBs are carried over HSUPA. Use a UE with the HSPA function to set up an RRC connection on the enhanced DCH (E-DCH). View the RRC_RRC_CONN_SETUP message from the Uu interface trace data. If the EDCH information is contained in the message, this feature is activated.
Deactivation Procedure 1. Run the MML command SET UFRCCHLTYPEPARA on the BSC6900. In this step, set Type of Channel Preferably Carrying Signaling RB to DCH (UL_DCH,DL_DCH) and Effective Flag of Signaling RB Channel Type to FALSE.
----End
Example
//Activating SRB over HSUPA SET UFRCCHLTYPEPARA: SrbChlType=HSUPA, SrbChlTypeRrcEffectFlag=TRUE; //Verifying SRB over HSUPA LST UFRCCHLTYPEPARA:; //Deactivating SRB over HSUPA SET UFRCCHLTYPEPARA: SrbChlType=DCH, SrbChlTypeRrcEffectFlag=FALSE;
95-2
Issue 02 (2011-07-11)
96 Configuring HSUPA Adaptive Transmission
96
Prerequisite
l l
Configuring HSUPA Adaptive Transmission
This section describes how to activate, verify, and deactivate the optional feature WRFD-010641 HSUPA Adaptive Transmission.
Dependencies on Hardware The uplink resource group of the cells that support this feature must be established on a board other than the HBBI or WBBPa. Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package must be configured before this feature is activated.
Context
Considering cell uplink power load, CE resources, and limited uplink coverage, this feature enables the BTS to adjust the target number of uplink retransmissions to increase the throughput per user and cell uplink capacity.
Procedure
l Activation Procedure 1. To enable the message containing NodeB private interface data to be transmitted to the NodeB over the Iub interface, run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set Process switch to NODEB_PRIVATE_INTERFACE_SWITCH. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH from the Power Control Switch drop-down list to activate HSUPA Adaptive Transmission. Run the NodeB MML command SET ADPRETRANSSWTCH to activate HSUPA Adaptive Transmission on the NodeB side.
2.
3. l
Issue 02 (2011-07-11)
96 Configuring HSUPA Adaptive Transmission
1.
Enable the UE to establish an HSUPA BE service. Then, check whether the NBAP_RL_RECFG_PREP message over the Iub interface carries the target number of HSUPA adaptive retransmissions, as shown in Figure 96-1. Figure 96-1 IE information
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH from the Power Control Switch drop-down list to deactivate HSUPA Adaptive Transmission. Run the NodeB MML SET ADPRETRANSSWTCH to deactivate HSUPA Adaptive Transmission on the NodeB side.
2. ----End
Example
//Activating HSUPA Adaptive Transmission (BSC6900 MML command) SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-1; //Activating HSUPA Adaptive Retransmission (NodeB MML command) SET ADPRETRANSSWTCH: SWITCH =OPEN; //Deactivating HSUPA Adaptive Transmission (BSC6900 MML command) SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-0; //Deactivating HSUPA Adaptive Retransmission (NodeB MML command) SET ADPRETRANSSWTCH: SWITCH=CLOSE;
96-2
Issue 02 (2011-07-11)
97 Configuring TTI Switch for BE Services Based on Coverage
97
Prerequisite
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.
l l
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010614 HSUPA Phase 2 has been configured before this feature is activated.
Context
This feature dynamically adjusts transmission time intervals (TTIs) based on UE transmit power and uplink service throughput. The TTI of UEs in the cell center is switched to 2 ms to increase the service rate, whereas the TTI of UEs at the cell edge is switched to 10 ms to expand the coverage.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the switch for this feature. In this step, select the DRA_BASE_COVER_BE_TTI_RECFG_SWITCH check box under the parameter Dynamic Resource Allocation Switch. Optional: If the Uplink Enhanced L2 feature is used, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH check box under the parameter Dynamic Resource Allocation Switch.
2.
Issue 02 (2011-07-11)
97-1

NOTE
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH can be selected only when DRA_BASE_COVER_BE_TTI_RECFG_SWITCH has been selected.
Verification Procedure 1. In the Navigation Tree pane on the BSC6900 LMT, click the Trace tab. In the displayed Trace Navigation Tree pane, double-click UMTS Services. On the unfolded list, double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG to trace Uu interface signaling messages, as shown in Figure 97-1. Figure 97-1 Uu Interface Trace dialog box
2. 3.
Adjust the distance between the UE and the NodeB to trigger a switching of the TTI from 2 ms to 10 ms. Analyze the traced messages shown in Figure 97-2 and Figure 97-3. The TTI has switched from 2 ms to 10 ms.
97-2
Issue 02 (2011-07-11)
Figure 97-2 2 ms TTI
Figure 97-3 10 ms TTI
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the switch for this feature. In this step, deselect the DRA_BASE_COVER_BE_TTI_RECFG_SWITCH check box under the parameter Dynamic Resource Allocation Switch.
----End
Issue 02 (2011-07-11)
97-3
Example
//Activating TTI Switch for BE Services Based on Coverage //Turning on the switch for the feature TTI Switch for BE Services Based on Coverage SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-1; //Turning on the switch for TTI L2+ for BE services based on coverage SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH-1; //Deactivating TTI Switch for BE Services Based on Coverage //Turning off the switch for the feature TTI Switch for BE Services Based on Coverage SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-0;
97-4
Issue 02 (2011-07-11)
98 Configuring HSUPA Coverage Enhancement at UE Power Limitation
98
Prerequisite
l l l
Configuring HSUPA Coverage
Enhancement at UE Power Limitation
This section describes how to activate, verify, and deactivate the optional feature WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation.
Dependencies on Hardware There is no requirement for BSC6900 or NodeB. The UE supports this feature. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
Compared with the traditional power compression technology, this feature provides an enhanced power compression function. This feature optimizes the size of a data block and the E-DPDCH power offset, improving the HSUPA performance at cell edge.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH check box from Power Control Switch to activate the feature. Run the BSC6900 MML command MOD UTYPRABHSUPAPC to set Minimum Reduced E-DPDCH Gain Factor.
2. l
Verification Procedure Start Uu Interface Trace on the LMT to trace messages on the Uu interface. View the RRC_RB_SETUP message, as shown in Figure 98-1. If the e-DPDCH-info message contains the minReduced-E-DPDCH-GainFactor information element (IE), it
Issue 02 (2011-07-11)
98-1
98 Configuring HSUPA Coverage Enhancement at UE Power Limitation
indicates that this feature takes effect, and the BSC6900 sends the UE the transmit power of the data channel. Figure 98-1 Viewing the minReduced-E-DPDCH-GainFactor IE
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH check box from Power Control Switch to deactivate the feature.
----End
Example
//Activation procedure //Enabling the feature SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH-1; //Setting the Minimum Reduced E-DPDCH Gain Factor parameter MOD UTYPRABHSUPAPC:RABINDEX=0, SUBFLOWINDEX=0, TRCHTYPE=TRCH_EDCH_2MS, UL16QAMIND=FALSE, ULL2ENHANCEIND=FALSE, EDPWRINTERPOLATIONIND=FALSE, ULECBOOSTINGIND=FALSE, BETAEDMIN=4; //Deactivation procedure //Disabling the feature SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH-0;
98-2
Issue 02 (2011-07-11)
99 Configuring Adaptive Configuration of Traffic Channel Power
99
Prerequisite
Configuring Adaptive Configuration of Traffic Channel Power

This section describes how to activate, verify, and deactivate the optional feature WRFD-010712 Adaptive Configuration of Traffic Channel Power.
l l
Context
As the HSPA/HSPA+ becomes an increasingly popular mainstream technology, uplink system performance needs to be enhanced to adapt to the ever-refreshed HSUPA peak rate. Based on the changes in subscriber behaviors and network status, this feature adaptively configures the parameters related to power control on the optimum uplink data channel, increasing the HSUPA system capacity.
NOTE
l This feature applies only to HSUPA Best Effort (BE) services whose Transmission Timing Interval (TTI) is 10 ms. l This feature is applicable to the scenarios where dynamic channel configuration control (DCCC) takes effect and the scenarios where dynamic channel element (CE) takes effect (DCCC does not take effect). l This feature is highly dependent on parameter settings. The relevant parameters must retain the default values. This feature may fail to take effect if these parameter settings are changed.
Procedure
l
Issue 02 (2011-07-11)
CAUTION
Before activating this feature, check the settings of the following two parameters: if Reference E-TFCI Index1 is set to 4 and Reference E-TFCI Power Offset1 is set to 12, you are advised to set Reference E-TFCI Power Offset1 to 8. 1. Activation Procedure in the Scenario Where DCCC Takes Effect (1) Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH check box under the parameter Power Control Switch, and clear the MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter Service Mapping Strategy Switch. (2) Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable HSUPA DCCC. In this step, select the DRA_DCCC_SWITCH and DRA_HSUPA_DCCC_SWITCH check boxes under the parameter Dynamic Resource Allocation Switch. (3) (Optional) Run the BSC6900 MML command SET UEDCHRATEADJUSTSET to select adjustable rates for EDCH. In this step, select RATE_128KBPS, RATE_256KBPS, RATE_608KBPS, and RATE_2048KBPS check boxes under the parameter HSUPA UpLink Rate Adjust Set. (4) Run the BSC6900 MML command SET UFRC. In this step, set Initial rate of HSUPA BE traffic to D256. (5) Disable dynamic CE on the NodeB side. 2. Activation Procedure in the Scenario Where Dynamic CE Takes Effect (1) Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH check box under the parameter Power Control Switch. l Verification Procedure
NOTE
l In dynamic CE scenarios, the service rate assigned by the core network (CN) is 2048 kbit/s, and the BSC6900 configures the Hybrid Automatic Repeat Request (HARQ) power offset (PO) based on the realtime service rate. In the scenarios where DCCC takes effect, the actual service rate is variable, and the BSC6900 configures the HARQ PO based on the realtime service rate. l The HARQ PO is one of the variable that determines the power offset on the E-DPDCH compared with the DPCCH.
1.
Run the BSC6900 MML command LST UTYPRABHSUPAPC to check the parameters related to power offset for typical services. Figure 99-1 shows an interactive BE service with the CN-assigned rate of 2048 kbit/s, whose Service parameter index is set to 55, Traffic Subflow Index to 0, Transport channel type to TRCH_EDCH_10MS, and the Ul 16QAM Used Indication, Ul enhanced L2 Used Indication, EdPower Interpolation Priority Used Indication, and UL EDPCCH Boosting Indication parameters all set to FALSE. As shown in Figure 99-1, HARQ PO for Large Retransmission is set to 0, HARQ PO for small Retrans at Low Speed is set to 4, and HARQ PO for small Retrans at High Speed is set to 0.
99-2
Issue 02 (2011-07-11)
Figure 99-1 PO parameters of typical services
2.
Establish a PS interactive BE service over HSUPA, for example, upload files to the FTP server.
NOTE
l In multi-user scenarios where the target load is limited and the realtime service rate of a single user is lower than a low-rate threshold (such as 150 kbit/s), the user is in the small retransmission state at a low speed. The HARQ PO is the value of HARQ PO for small Retrans at Low Speed. l If the realtime service rate of a single user is higher than a high-rate threshold (such as 300 kbit/ s), the user is in the small retransmission state at a high speed. The HARQ PO is the value of HARQ PO for small Retrans at High Speed.
3.
Check the realtime rate of the new BE service and the CN-assigned rate by referring to Monitoring UL Throughput and Bandwidth, as shown in Figure 99-2.
Issue 02 (2011-07-11)
99-3
Figure 99-2 Rate of the new BE service
4.
Verification Procedure in the Scenario Where DCCC Takes Effect (1) Check the uplink throughput and bandwidth by referring to Monitoring UL Throughput and Bandwidth. The data rate of the HSUPA service when accessing the network is 256 kbit/s. Trace messages over the Uu interface by referring to Tracing Messages on the Uu Interface. The value of the HARQ PO in the RRC_RB_SETUP message shows that the user is in the small retransmission state at a high speed. The HARQ PO is equal to the value of HARQ PO for small Retrans at High Speed, as shown in Figure 99-3. Figure 99-3 HARQ PO (4) of a UE for small retransmission at a low speed (256 kbit/s)
(2) After the file upload on the FTP is complete, check the uplink data rate of the UE by referring to Monitoring UL Throughput and Bandwidth. When the data rate is 608 kbit/s, check the value of HARQ PO in the RRC_RB_RECFG message by referring to Tracing Messages on the Uu
Interface. The HARQ PO changes from HARQ PO for small Retrans at High Speed for 256 kbit/s to that for 608 kbit/s, as shown in Figure 99-4. Figure 99-4 HARQ PO (0) of a UE for small retransmission at a high speed
5.
Verification Procedure in the Scenario Where Dynamic CE Takes Effect (1) Trace messages over the Uu interface by referring to Tracing Messages on the Uu Interface. The value of the HARQ PO in the RRC_RB_SETUP message shows that the user is in the small retransmission state at a high speed when accessing the network. The HARQ PO is equal to the value of HARQ PO for small Retrans at High Speed, as shown in Figure 99-5.
Issue 02 (2011-07-11)
99-5
Figure 99-5 HARQ PO (0) of a UE for small retransmission at a high speed
(2) Simulate a situation that the uplink load is limited by changing the target uplink load to 10%. Run the BSC6900 MML command MOD UCELLHSUPA. In this step, set Maximum Target Uplink Load Factor to 10. After the uplink load is limited, check the uplink throughput and bandwidth by referring to Monitoring UL Throughput and Bandwidth. HARQ PO reconfiguration is triggered when the uplink throughput of the UE is lower than the low-rate threshold. Check the value of HARQ PO in the RRC_RB_RECFG message by referring to Tracing Messages on the Uu Interface. The HARQ PO changes from HARQ PO for small Retrans at High Speed to HARQ PO for small Retrans at Low Speed, as shown in Figure 99-6. Figure 99-6 HARQ PO (4) of a UE for small retransmission at a low speed
(3) If the feature WRFD-010641 HSUPA Adaptive Transmission takes effect, use another UE to perform a PS interactive service with an uplink rate of 2048 kbit/ s and downlink rate of 7200 kbit/s in the cell. There is a possibility that the UE
switches from small retransmission state to large retransmission state if the cell load increases to a certain value. Check the HARQ PO in the RRC_RB_RECFG message by referring to Tracing Messages on the Uu Interface. The HARQ PO changes from HARQ PO for Small Retrans at Low Speed to HARQ PO for Large Retransmission, as shown in Figure 99-7. Figure 99-7 HARQ PO (0) of a UE for large retransmission at a low speed
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the switch for this feature. In this step, clear the PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH check box under the parameter Power Control Switch.
----End
Example
//Activation procedure in the scenario where DCCC takes effect SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1&DRA_HSUPA_DCCC_SWITCH-1; SET UEDCHRATEADJUSTSET: EdchRateAdjustSet=RATE_128KBPS-1&RATE_256KBPS-1&RATE_608KBPS-1&RATE_2048K BPS-1; SET UFRC: HsupaInitialRate=D256; //Activation procedure in the scenario where dynamic CE takes effect SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-1; //Verification procedure LST UTYPRABHSUPAPC: QueryType=QUERY_BY_PROPERTY, CNDomainId=PS_DOMAIN, TrafficClass=INTERACTIVE, MaxBitRate=256000, TrchType=TRCH_EDCH_10MS, Ul16QamInd=FALSE, UlL2EnhanceInd=FALSE, EdPwrInterpolationInd=FALSE, UlEcBoostingInd=FALSE;
Issue 02 (2011-07-11)
99-7
//Verification procedure in the scenario where dynamic CE takes effect MOD UCELLHSUPA: CellId=x, MaxTargetUlLoadFactor=10 //Deactivation procedure SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-0;
99-8
Issue 02 (2011-07-11)
100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion
100
Prerequisite
l l
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.
Context
By monitoring Iub transmission resources, this feature dynamically adjusts the uplink Uu throughput and thereby greatly improves resource utilization.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select the NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter Process switch. Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set HSUPA Congestion Control Switch to ON(ON).
2. l
NOTE
l UE is in idle mode and supports the HSUPA and HSDPA functions. l The bandwidth between the BSC6900 and the NodeB is 1 MHz.
Issue 02 (2011-07-11)
100-1
100 Configuring HSUPA Iub Flow Control in Case of Iub Congestion
1.
UE is of HSUPA category 5 and is correctly registered at the HLR. That is, traffic class is set to background, the maximum bit rates are set to UL 2048 kbit/s and DL 7200 kbit/s. On the BSC6900 LMT, start Monitoring UL Throughput and Bandwidth. The uplink throughput of UE is stable and is about 1M. Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set HSUPA Congestion Control Switch to OFF(OFF).
2. 3. l 1. ----End
Example
//Activation procedure SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; SET UDPUCFGDATA: HsupaTnlSwitch=ON; //Deactivation procedure SET UDPUCFGDATA: HsupaTnlSwitch=OFF;
100-2
Issue 02 (2011-07-11)
101 Configuring Dynamic CE Resource Management
101
Prerequisite
l l
Configuring Dynamic CE Resource Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-010638 Dynamic CE Resource Management.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features When this feature and WRFD-01061208 HSUPA DCCC are activated at the NodeB at the same time, WRFD-01061208 HSUPA DCCC automatically becomes ineffective at the NodeB.
Context
To improve utilization efficiency of channel element (CE) resources, Huawei RAN introduces the Dynamic CE Resource Management feature. This feature helps to quickly adjust CE allocation by considering the Guaranteed Bit Rate (GBR) and the actual rate of a UE. During preemption of CE resources, this feature is used to allocate CE resources in a reasonable way, therefore ensuring preemption fairness.
Procedure
l l Activation Procedure 1. 1. The feature does not need to be activated. Start Tracing Messages on the Iub Interface on BSC6900 LMT and check whether the value of dynamic-CE-Switch-Private in NBAP_AUDIT_RSP is 1. If the value is 1, it indicates the feature is activated. Else, it indicates the feature is not activated. When the value of dynamic-CE-Switch-Private is 1, see Figure 101-1.
101 Configuring Dynamic CE Resource Management
Figure 101-1 dynamic-CE-Switch-Private
Deactivation Procedure 1. 2. 3. Run the BSC6900 MML command DEA UCELLHSUPA to deactivate HSUPA for the cell. Set NodeB license control item the number of NodeBs with dynamic CE function enabled to 0 on M2000 client . Details see Allocating a License to NodeBs. Run the BSC6900 MML command ACT UCELLHSUPA to activate HSUPA for the cell.
----End
Example
//Deactivation procedure DEA UCELLHSUPA: CellId=80; ACT UCELLHSUPA: CellId=80;
101-2
Issue 02 (2011-07-11)
102 Configuring HSPA+ Downlink 28Mbps per User
102
Prerequisite
l BSC6900 NodeB
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. 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.
Dependencies on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature: WRFD-010684 2 x 2 MIMO or WRFD-010696 DC-HSDPA WRFD-010650 HSDPA 13.976 Mbps per User
l l
License The license controlling this feature has been activated. Other Prerequisites CN support user rate of 28Mbps or above. The UE category must support cat16, cat18(or later).
Issue 02 (2011-07-11)
102-1
Context
This feature enables the theoretical HSPA+ MIMO rate per user to reach a maximum of 28 Mbps. This feature enhances the user experience for high-speed data services.
Procedure
l Activation Procedure The theoretical UE peak rate reaches 28 Mbps when the UE services are carried on 2 x 2 MIMO and the following conditions are met: 1. 2. 3. l 1. Activate the feature WRFD-010684 2 x 2 MIMO by referring to 111 Configuring 2x2 MIMO. Run the BSC6900 MML command SET LICENSE to turn on the license switch for the HSPA+ Downlink 28Mbps per User feature. Enable the UE to subscribe to this feature by referring to CN documents. Enable a UE in a 2 x 2 MIMO cell to download a 500 MB file from the FTP server. Then, detect the download transmission rate. At this time, the UE initiates BE services in the 2 x 2 MIMO cell and the RNC establishes services on the 2 x 2 MIMO. 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;
102-2
Issue 02 (2011-07-11)
103
Prerequisite
l
Dependencies on Hardware Dependencies on BSC6900 Hardware This feature does not depend on the BSC6900 hardware. Dependencies on NodeB Hardware The BTS3812E, BTS3812A, and BTS3812AE are configured with the EBBI, EBOI, or EDLP board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board. Dependencies on UE Hardware The UE supports 64QAM, that is, the UE is of category 13, 14, 17, or 18, as defined in 3GPP specifications.
Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010683 Downlink 64QAM, WRFD-010685 Downlink Enhanced L2.
Context
This feature enables the theoretical HSPA+ 64QAM rate per user to reach a maximum of 21 Mbps. It provides users with high-speed data services.
Procedure
l
Issue 02 (2011-07-11)
The theoretical peak rate of a UE can reach 21 Mbps when 64QAM is used and the following conditions are met: 1. 2. 3. l Run the BSC6900 MML command SET LICENSE to activate the license controlling the HSPA+ Downlink 21Mbps per User feature. Use the UE to subscribe to this feature by referring to CN documents. Activate the feature WRFD-010683 Downlink 64QAM by referring to 110 Configuring Downlink 64QAM. Use the UE in a 64QAM cell to download a 500 MB file from the FTP server. Then, check the downloading rate. Run the BSC6900 MML command SET LICENSE to deactivate the feature HSPA + Downlink 21Mbps per User.
----End
Example
//Activating HSPA+ Downlink 21Mbps per User SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN21_PER_USER-1; //Deactivating HSPA+ Downlink 21Mbps per User SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN21_PER_USER-0;
103-2
Issue 02 (2011-07-11)
104 Configuring Downlink Enhanced L2
104
Prerequisite
l l l l
Configuring Downlink Enhanced L2
This section describes how to activate, verify, and deactivate the optional feature WRFD-010685 Downlink Enhanced L2.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated. License The license controlling this feature has been activated. Others The UE is of 3GPP R7 or later and supports this feature.
Context
The Downlink Enhanced L2 feature eliminates contradictions between high-rate transmission that requires a large PDU size and cell-edge coverage that requires a small PDU size by using flexible Protocol Data Unit (PDU) sizes. This feature enables dynamic adjustment of the PDU size. This improves transmission efficiency on the Iub and Uu interfaces and increases the celledge throughput and coverage radius. This feature is a prerequisite for the features DL 64QAM, 2x2 MIMO, and Enhanced CELL_FACH.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UFRC to set the RNC-level downlink layer 2 enhancement parameters. In this step, set Cell_DCH DL L2 enhance max PDU size and Cell_FACH L2 enhance max PDU size. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Cell Hspa Plus function switch to DL_L2ENHANCED to turn on the cell-level layer 2 enhancement switch.
2.
Issue 02 (2011-07-11)
Verification Procedure 1. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 104-1. Figure 104-1 Uu Interface Trace dialog box
2.
Use the UE to establish an HSDPA service. Check whether the value of the IE dlTransportChannelType in the rb-MappingInfo of the RRC_RB_SETUP message is hsdsch. View the value of the IE dL RLC PDU size in the RRC_RB_SETUP message. If the value of the IE dL RLC PDU size is flexibleSize, as shown in Figure 104-2, this feature has been activated. If the value of the IE dL RLC PDU size is fixedSize, this feature is not activated. Figure 104-2 Value of the IE dL RLC PDU size
3.
104-2
Issue 02 (2011-07-11)
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect DL_L2ENHANCED from the Cell Hspa Plus function switch drop-down list box.
----End
Example
//Activating Downlink Enhanced L2 //Enabling the cell-level downlink L2 enhancement MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-1; //Deactivating Downlink Enhanced L2 //Disabling the cell-level downlink L2 enhancement MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-0;
Issue 02 (2011-07-11)
104-3
105 Configuring Downlink Enhanced CELL_FACH
105
Prerequisite
l l
Configuring Downlink Enhanced CELL_FACH
This section describes how to activate, verify, and deactivate the optional feature WRFD-010688 Downlink Enhanced CELL_FACH.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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 l
License The license controlling this feature has been activated. Other Prerequisites The UE should support this feature. HBBI and HDLP on BTS3812E/BTS3812AE do not support this feature, EBBI, EDLP is needed. BBU3806 does not support this feature, EBBC or EBBCd is needed. EBBM is needed by BBU3806C to support this feature. 3900 series NodeB: WBBPa does not support this feature, and WBBPb or WBBPd is needed.
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.
Issue 02 (2011-07-11)
105 Configuring Downlink Enhanced CELL_FACH
2. 3. 4. 5. l 1.
Run the BSC6900 MML command ADD UCELLHSDPA to add HUDPA parameters of a cell. Run the BSC6900 MML command ADD UCELLEFACH to add enhanced CELL_FACH state parameters of a cell. Run the BSC6900 MML command ACT UCELLHSDPA to activate HSDPA feature. Run the BSC6900 MML command ACT UCELLEFACH to activate this feature. Run the BSC6900 MML command DSP UCELL to check whether EFACH is available. The value of Status of EFACH is EFACH 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. ----End
Example
//Activating Downlink Enhanced CELL_FACH MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_FACH-1&DL_L2ENHANCED-1; ADD UCELLHSDPA: CellId=11, AllocCodeMode=Automatic, CodeAdjForHsdpaSwitch=ON; ADD UCELLEFACH: CellId=11; ACT UCELLHSDPA: CellId=11; ACT UCELLEFACH: CellId=11; //Deactivating Downlink Enhanced CELL_FACH MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_FACH-0&DL_L2ENHANCED-0; DEA UCELLEFACH: CellId=11;
105-2
Issue 02 (2011-07-11)
106 Configuring Uplink Enhanced CELL_FACH
106
Prerequisite
l
Configuring Uplink Enhanced CELL_FACH
This section describes how to activate, verify, and deactivate the optional feature WRFD-010701 Uplink Enhanced CELL_FACH.
Dependencies on Hardware Dependencies on the NodeB: The BTS3812E, BTS3812A, and BTS3812AE are configured with the EULPd, EBBI, EBOI, or EULP board. To support the E-AI, the BTS3812E, BTS3812A, and BTS3812AE are configured with the EULPd board. The BBU3806 is configured with the EBBC/EBBCd board. To support the E-AI, the BBU3806 is configured with the EBBCd board. The BBU3900 is configured with the WBBPb/WBBPd board. To support the E-AI, the BBU3900 is configured with the WBBPd board.
Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010688 Downlink Enhanced CELL_FACH WRFD-010695 UL Layer 2 Improvement WRFD-010652 SRB over HSDPA WRFD-010636 SRB over HSUPA
l l
License The license controlling this feature has been activated. Other Prerequisites The UE is of release 8 or a later version. It supports Uplink Enhanced CELL_FACH. The NodeB is of release 8 or a later version.
Context
This feature enables the random access channel (RACH) to be mapped onto the E-DCH Dedicated Physical Data Control Channel (E-DPDCH). With this feature, UEs in the CELL_FACH state can transmit uplink data at higher rates.
106 Configuring Uplink Enhanced CELL_FACH
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UERACHBASIC to add basic information about the Enhanced RACH (ERACH) function, namely Uplink Enhanced CELL_FACH in a cell. In this step, set TTI for Common E-DCH. Run the BSC6900 MML command ADD UERACHASC to add information about resources available for one Access Service Class (ASC) in Uplink Enhanced CELL_FACH to the cell. Run the BSC6900 MML command ADD UERACHACTOASCMAP to add mapping of Access Classes (ACs) to an ASC for Uplink Enhanced CELL_FACH. Run the BSC6900 MML command ACT UCELLERACH to activate this feature. Run the BSC6900 MML command DSP UCELL to check whether the ERACH is available. Run the BSC6900 MML command DEA UCELLERACH to deactivate this feature.
2.
3. 4. l 1. l
----End
Example
//Activating Uplink Enhanced CELL_FACH ADD UERACHBASIC: CellId=11, CommonEdchTTISelect=TTI_10MS; ADD UERACHASC: CellId=11; ADD UERACHACTOASCMAP: CellId=11; ACT UCELLERACH: CellId=11; //Verifying Uplink Enhanced CELL_FACH DSP UCELL: DSPT=BYCELL, CellId=11; //Deactivating Uplink Enhanced CELL_FACH DEA UCELLERACH: CellId=11;
106-2
Issue 02 (2011-07-11)
107 Configuring Enhanced DRX
107
Prerequisite
l NodeB:
Configuring Enhanced DRX
This section describes how to activate, verify, and deactivate the optional feature WRFD-010702 Enhanced DRX.
Dependencies on Hardware The BTS3812E, BTS3812A, or BTS3812AE is configured with the EULPd, EBBI, EBOI, or EULP board. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features Configurations of other features, on which this feature depends, are complete. This feature depends on the feature WRFD-010688 Enhanced CELL_FACH.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE must be of 3GPP Release-8 or later and support Enhanced DRX.
Context
The enhanced discontinuous reception (DRX) feature enables UEs in the enhanced downlink for CELL_FACH state to receive the HS-SCCH discontinuously. After this feature is enabled, the RAN and UEs in the enhanced downlink for CELL_FACH state transmit and receive data at a specified time. The UE detects the HS-SCCH at regular intervals instead of detecting the HS-SCCH continuously. When there is no data to transmit, the UE shuts down the receiver. As a result, the power consumption of the UE decreases.
Procedure
Issue 02 (2011-07-11)
107-1
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to select E_DRX(Enhanced Discontinous Reception Function Switch) for Cell Hspa Plus function switch. Run the BSC6900 MML command DSP UCELL to check whether enhanced downlink for CELL_FACH is activated. If the enhanced downlink for CELL_FACH is already activated, run the BSC6900 MML command DEA UCELLEFACH to deactivate enhanced downlink for CELL_FACH. If enhanced downlink for CELL_FACH is not activated, go to Step 3.
NOTE
2.
The BSC6900 MML command ADD UCELLEDRX fails to be executed in an active cell enabled with enhanced downlink for CELL_FACH. Therefore, you need to deactivate enhanced downlink for CELL_FACH before configuring the related parameters.
3. 4. l 1. 2.
Run the BSC6900 MML command ADD UCELLEDRX to set parameters related to enhanced DRX based on network planning requirements. Run the BSC6900 MML command ACT UCELLEFACH to activate this feature. Start Uu Interface Trace on the LMT to trace messages on the Uu interface. If the UE is not enabled with enhanced uplink for CELL_FACH, the information element DRX Interruption by HS-DSCH data in the system information message SIB5/5bis should be set to TRUE, as shown in Figure 107-1. If the UE is enabled with enhanced uplink for CELL_FACH, the information element Common E-DCH system info is carried in the system information message SIB5/5bis. Figure 107-1 Information element in the system information message of enhanced DRX
3. 4.
Start Cell Trace on the LMT to trace messages of a cell. When the UE is in the enhanced downlink for CELL_FACH state, the RNC carries the E-DRX indication in the HS-DSCH DATA FRAME type2 to the NodeB on the DCCH or DTCH. If enhanced DRX is enabled, you can view that the E-DRX bit is 1 in Cell Trace, as shown in Figure 107-2. If enhanced DRX is not enabled, the EDRX bit is 0.
107-2
Issue 02 (2011-07-11)
Figure 107-2 Indication sent from the RNC to the NodeB on the DCCH or DTCH
5.
If the UE is enabled with enhanced uplink for CELL_FACH, the HS-DSCH DATA FRAME type2 carries New IE Flag, H-RNTI, and E-RNTI, which can be viewed in Cell Trace, as shown in Figure 107-3. Figure 107-3 HS-DSCH DATA FRAME type2
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to deselect E_DRX(Enhanced Discontinous Reception Function Switch) for Cell Hspa Plus function switch.
----End
Example
//Activating enhanced DRX MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_DRX-1; DEA UCELLEFACH: CellId=11; ADD UCELLEDRX: CellId=11, EDRXT321=EDRXT321_100, EDRXCycle=EDRXCYCLE_8, EDRXBurst=EDRXBURST_1, EDRXInterruptbyHSDSCHData=INTERRUPTION_CFG; ACT UCELLEFACH: CellId=11; //Deactivating enhanced DRX MOD UCELLALGOSWITCH: CellId=11, HspaPlusSwitch=E_DRX-0;
Issue 02 (2011-07-11)
107-3
108 Configuring MIMO Prime
108
Prerequisite
l
Configuring MIMO Prime
This chapter describes how to activate, verify, and deactivate the basic feature WRFD-030011 MIMO Prime.
Dependencies on Hardware Only the 40 W RRU3801C, RRU3804, RRU3806, RRU3808, WRFU, RRU3805, and 850 MHz/900 MHz/1900 MHz RRU3908 V1support this feature. Two RF units, each with a TX channel, are configured. The BBU3900 is configured with the WBBPb or WBBPd board. The BTS3812E/AE does not support this feature.
l l
Dependencies on Other Features WRFD-010610 HSDPA Introduction Package License The license that supports this feature is activated.
Context
l l When the feature WRFD-010699 DC-HSDPA+MIMO has been activated, this feature is activated by default and therefore does not require license activation or other operations. MIMO Prime can increase the capacity of the cell in which MIMO has not been implemented by 5% to 10%. The increase in the overall cell throughput helps to greatly improve the experience of users in medium and bad radio conditions. MIMO Prime is applicable to various services such as HSDPA and 64QAM, whereas it does not have any special requirement for the capabilities of UEs and will not affect the performance of UEs that do not support MIMO.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET MACHSPARA. In this step, set MIMO Prime Switch to OPEN(open).
NOTE
Before activating this feature for a cell, enable virtual antenna mapping for the cell.
Issue 02 (2011-07-11)
108-1
108 Configuring MIMO Prime
Verification Procedure 1. 2. Run the NodeB MML command LST MACHSPARA. In this step, check that MIMO Prime Switch is set to Open. Observe the counters VS.APCPhase0CQI.MEAN and VS.APCCQI.MEAN. Before this feature is activated, the values of both counters are 0. After this feature is activated, the values of both counters differ from 0. Run the NodeB MML command SET MACHSPARA. In this step, set MIMO Prime Switch to CLOSE(close).
----End
Example
//Activating MIMO Prime SET MACHSPARA: LOCELL=0, MIMOPRIMESW=OPEN; //Verifying MIMO Prime LST MACHSPARA: LOCELL=0; //Deactivating MIMO Prime SET MACHSPARA: MIMOPRIMESW=CLOSE;
108-2
Issue 02 (2011-07-11)
109
Prerequisite
l
Dependencies on Hardware It is recommended that the BSC6900 be configured with the Data Processing Unit REV:e (DPUe) board to support more peak-rate users. On the NodeB side: BBU3806 is configured with the Enhanced Base Band Card (EBBC) or Enhanced Base Band Card REV:d (EBBCd) board. BBU3806C is configured with the Enhanced Baseband Module (EBBM) board.
NOTE
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.
In the case of BTS3812E, BTS3812A, or BTS3812AE, the NodeB Enhanced HSDPA Supported Baseband Processing and Interface Unit (EBBI) , NodeB Enhanced HSDPA Supported Baseband Processing and Optical Interface Unit (EBOI), or NodeB Enhanced Downlink Processing Unit (EDLP) board is configured. In addition, the uplink service cannot be established on the NodeB HSDPA supported Baseband processing and Interface Unit (HBBI) or NodeB HSUPA supported Uplink Processing Unit (HULP) board. BBU3900 is configured with the WBBPb or WBBPd board. To enable the 2x2 MIMO feature, either two interconnected RF modules with one TX channel or one RF module with two TX channels is configured. l Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010681 HSPA+ Downlink 21Mbps per User, WRFD-010696 DC-HSDPA, and WRFD-010612 HSUPA Introduction Package
Issue 02 (2011-07-11)
109-1
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 License The license controlling this feature has been activated. Other Prerequisites The CN supports the UE rate of 42 Mbit/s or higher. The UE is of HSDPA category 19 or higher in the range from 19 to 28.
Context
As indicated in 3GPP Release 8, the downlink peak rate per user reaches up to 42 Mbit/s by using the 2x2 MIMO+64QAM or 64QAM+DC-HSDPA technologies and by using enhanced functions of the related NEs.
Procedure
l l Activation Procedure 1. 1. 2. This feature does not need to be activated. Set the BE service rate of the UE at the Home Location Register (HLR) to 42 Mbit/ s. Enable a UE in an HSDPA cell to download a 500 MB file from the FTP server. Then, check whether the download transmission rate is 42 Mbit/s. If yes, this feature has been activated. At this time, the UE initiates BE services in the HSDPA cell and the BSC6900 establishes services on the HS-DSCH. Start Monitoring DL Throughput and Bandwidth on the BSC6900 LMT, as shown in Figure 109-1. Figure 109-1 Connection Performance Monitoring dialog box Verification Procedure
3.
The connection performance monitoring result indicates that the BSC6900 assigns a 42.1 Mbit/s bandwidth to the UE, that is, this feature has been activated. l Deactivation Procedure 1. ----End This feature does not need to be deactivated.
Example
N/A
109-2
Issue 02 (2011-07-11)
110 Configuring Downlink 64QAM
110
Prerequisite
l
Configuring Downlink 64QAM
This section describes how to activate, verify, and deactivate the optional feature WRFD-010683 Downlink 64QAM.
Dependencies on Hardware The BTS3812E, BTS3812A, and BTS3812AE need to be configured with the EBBI, EBOI, or EDLP board. The BBU3806 needs to be configured with the EBBC or EBBCd board. The BBU3806C needs to be configured with the EBBM board. The BBU3900 needs to be configured with the WBBPb or WBBPd board.
Dependencies on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010685 Downlink Enhanced L2
l l
License The license controlling this feature has been activated. Other Prerequisites The UE category supports 64QAM.
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.
2.
Issue 02 (2011-07-11)
Set Preferred MIMO or 64QAM character to 64QAM. Set HSPA Technologies Retried by UEs to 64QAM.
NOTE
l If the switch parameter is set to 64QAM, the network preferentially configures 64QAM for the UE. Otherwise, the network preferentially configures MIMO for the UE. l Before commissioning the feature, you need to set the switch parameter to 64QAM. After the commissioning, you can set the parameter according to the actual network planning. l For UEs to 3GPP R7 specifications, MIMO and 64QAM cannot be used together.
3.
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. Run the BSC6900 MML command MOD UEXT3GCELL to set neighboring BSC6900 cell support 64QAM. Set parameter Cell Capability Container and select HSPAPLUS_DL_64QAM_SUPPORT (downlink 64QAM support indicator). As Figure 110-1 shows, start Uu interface tracing on the BSC6900 LMT. Figure 110-1 Uu interface tracing
4.
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.
3.
110-2
If the value of dl-64QAM-Configured is true as Figure 110-2 shows, you can infer that this feature has been activated. Otherwise, you can infer that this feature has not been activated. Figure 110-2 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. Run the BSC6900 MML command MOD UEXT3GCELL to cancel neighboring BSC6900 cell support 64QAM. Set parameter Cell Capability Container and deselect HSPAPLUS_DL_64QAM_SUPPORT (downlink 64QAM support indicator).
2.
----End
Example
//Activation procedure SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1; SET UFRC: MIMOor64QAMSwitch=64QAM, RetryCapability=64QAM-1; MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-1&DL_L2ENHANCED-1; MOD UEXT3GCELL: NRncId=0, CellId=0, CellCapContainerFdd=HSPAPLUS_DL_64QAM_SUPPORT-1; //Deactivation procedure MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-0; MOD UEXT3GCELL: NRncId=0, CellId=0, CellCapContainerFdd=HSPAPLUS_DL_64QAM_SUPPORT-0;
Issue 02 (2011-07-11)
110-3
111 Configuring 2x2 MIMO
111
Prerequisite
l Dependencies on Hardware
Configuring 2x2 MIMO
This section describes how to activate, verify, and deactivate the optional feature WRFD-010684 2x2 MIMO. Multiple Input Multiple Output (MIMO) is a multi-antenna technology, which enables multiple antennas to receive and transmit data. This increases the data transmission rate.
The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EBBI, EBOI, or EDLP board. The BBU3806 must be configured with the EBBC or EBBCd board. The BBU3806C must be configured with the EBBM board. The BBU3900 must be configured with the WBBPb or WBBPd board. l Dependencies on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010685 Downlink Enhanced L2 WRFD-010629 DL 16QAM Modulation l l License The license controlling this feature has been activated. Other Prerequisites The software version must be RAN11.0 or later. The UE is of HSDPA category 15 or higher. Logical cells have been established on the BSC6900 side. For details about the hardware deployment related to MIMO, see "2x2 MIMO Configuration" in the NodeB Technical Description.
Issue 02 (2011-07-11)
111-1
Context
CAUTION
Before enabling this feature in an activated cell, you need to: l Deactivate the cell. This will interrupt services in the cell. Therefore, enable the feature when the traffic of the cell is light. l Ensure that there are sufficient baseband resources on the baseband processing board. Otherwise, this feature cannot be activated. 2x2 MIMO is introduced to HSDPA in 3GPP R7. To support this feature, the NodeB use two antennas to transmit signals, and UEs use two antennas to receive signals. When 2x2 MIMO is enabled, the theoretical peak rate of HSDPA users increases from 14 Mbit/s to 28 Mbit/s.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the BSC6900-level MIMO algorithm switch. In this step, set Channel Configuration Strategy Switch to CFG_HSDPA_MIMO_SWITCH. Run the BSC6900 MML command SET UFRC to set common parameters among the fundamental resource configuration (FRC) parameters. In this step, set Preferred MIMO or 64QAM character to MIMO.
NOTE
2.
l MIMO and 64QAM cannot be enabled together for UEs of 3GPP R7. l If Preferred MIMO or 64QAM character is set to MIMO, MIMO is preferentially configured for the UE. l Before verifying the feature, set Preferred MIMO or 64QAM character to MIMO. After the verification, set this parameter to a proper value according to the network plan.
3.
Run the BSC6900 MML command MOD UCELLALGOSWITCH turn on the celllevel MIMO switch and enhanced L2 function switch. In this step, set Cell Hspa Plus function switch to MIMO, DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch), and UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch). Run the BSC6900 MML command DEA UCELL to deactivate the cell. Configure the related data on the NodeB according to the MIMO hardware configuration scheme. The following procedure takes the RRU3804 as an example to describe how to configure data for the change from one RRU3804 to two cascading RRU3804s. (1) Run the NodeB MML command ADD RRUCHAIN to create an RRU chain. (2) Run the NodeB MML command ADD RRU to add an RRU to the chain.
4. 5.
6.
On the NodeB, modify Diversity Mode of the sector and Two Tx Way 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.
111-2
Issue 02 (2011-07-11)
(3) Run the NodeB MML command ADD SEC to add a sector. In this step, set Diversity Mode to COMMON_MODE and configure the antenna data based on the MIMO hardware deployment scheme. (4) Run the NodeB MML command ADD LOCELL to add a local cell. In this step, set Two Tx Way to TRUE and configure the antenna data based on the MIMO hardware deployment scheme.
NOTE
Transit diversity can be classified into PSP and Space Time Transmit Diversity (STTD). Step 7 describes the method of configuring STTD. Step 8 describes the method of configuring PSP.
7.
Configure STTD on the BSC6900. Modify the transmit diversity mode of a cell on the BSC6900. (1) If UPRACH exists, run the BSC6900 MML command RMV UPRACH to remove the PRACH. (2) Run the BSC6900 MML command ADD UPRACHBASIC to add PRACH basic information. (3) Run the BSC6900 MML command ADD UPRACHTFC to add TFC of PRACH. (4) Run the BSC6900 MML command ADD UPRACHASC to add ASC Of PRACH. (5) Run the BSC6900 MML command ADD UPRACHACTOASCMAP to Add AC-ASC mapping information of PRACH. (6) Run the BSC6900 MML command ADD UPRACHSLOTFORMAT to add slot format of PRACH. (7) Run the BSC6900 MML command ADD URACH to add RACH. (8) Run the BSC6900 MML command ADD URACHDYNTFS to add dynamic TFS of RACH. (9) If AICH exists, run the BSC6900 MML command RMV UAICH to remove AICH. (10) Run the BSC6900 MML command ADD UAICH to add AICH. Set STTD Indicator to TRUE. (11) Run the BSC6900 MML command ACT UPRACH to activate PRACH. (12) If an SCCPCH exists, run the BSC6900 MML command RMV USCCPCH to remove the SCCPCH. (13) Run the BSC6900 MML command ADD USCCPCHBASIC to add an SCCPCH. In this step, set STTD Indicator to TRUE. (14) Run the BSC6900 MML command ADD USCCPCHTFC to add the Calculated Transport Format Combination (CTFC) of an SCCPCH. (15) If a PICH exists, run the BSC6900 MML command RMV UPICH to remove the PICH. (16) Run the BSC6900 MML command ADD UPICH to add a PICH. In this step, set STTD Indicator to TRUE. (17) Run the BSC6900 MML command ADD UFACH to add a FACH. (18) Run the BSC6900 MML command ADD UFACHDYNTFS to add the transport format set (TFS) of the FACH. (19) Run the BSC6900 MML command ADD UFACHLOCH to add a logical channel mapped to the FACH.
Issue 02 (2011-07-11)
111-3
(20) Run the BSC6900 MML command ADD UPCH to add a PCH. (21) Run the BSC6900 MML command ADD UPCHDYNTFS to add the transport format set (TFS) of the PCH. (22) Run the BSC6900 MML command ACT USCCPCH to activate the SCCPCH. (23) Run the BSC6900 MML command MOD UCELLSETUP to set the transmit diversity mode of an MIMO-enabled cell to STTD. Set TX Diversity Indication to TRUE. Set STTD Support Indicator to STTD_Supported. Set CP1 Support Indicator to CP1_not_Supported. Set DPCH Tx Diversity Mode for Other User to STTD. Set DPCH Tx Diversity Mode for MIMO User to STTD. Set FDPCH Tx Diversity Mode for Other User to STTD. Set FDPCH Tx Diversity Mode for MIMO User to STTD. 8. Configure PSP on the BSC6900. (1) Run the BSC6900 MML command MOD UCELLSETUP. In this step, set TX Diversity Indication to FALSE. (2) Run the BSC6900 MML command ADD USCPICH to add an S-CPICH for the cell. 9. Run the BSC6900 MML command ACT UCELL to activate the cell. 10. Run the BSC6900 MML command ACT UCELLMIMO to activate the MIMOrelated parameter settings. l Verification Procedure 1. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 111-1.
111-4
Issue 02 (2011-07-11)
2.
Use the UE to establish an HSDPA service. Check whether the value of the information element (IE) dl-TransportChannelType in the rb-MappingInfo of the RRC_RB_SETUP message is hsdsch. In the traced Uu interface data, check whether the RRC_RB_SETUP message contains the IE mimoParameters. If the RRC_RB_SETUP message contains the IE mimoParameters, as shown in Figure 111-2, this feature has been activated. If the RRC_RB_SETUP message does not contain the IE mimoParameters, as shown in Figure 111-2, this feature is not activated. Figure 111-2 IE mimoParameters
3.
Deactivation Procedure 1. 2. Run the BSC6900 MML command DEA UCELL to deactivate the cell. Run the BSC6900 MML command DEA UCELLMIMO to deactivate the MIMOrelated parameter settings.
NOTE
Transit diversity can be classified into PSP and STTD. Step 3 describes the method of deactivating STTD. Step 4 describes the method of deactivating PSP.
3.
Optional: When STTD is used, (1) Run the BSC6900 MML command RMV USCCPCH to remove the SCCPCH. (2) Run the BSC6900 MML command MOD UCELLSETUP. In this step, set TX Diversity Indication to FALSE.
4. 5. 6. ----End
Optional: When PSP is used, run the BSC6900 MML command RMV USCPICH to remove the S-CPICH of the cell. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, clear MIMO from the HspaPlusSwitch drop-down list. Run the BSC6900 MML command ACT UCELL to activate the cell.
Example
l NodeB V200R013
//Activation procedure //Operations on the BSC6900 side //Turning on the BSC6900-level MIMO algorithm switch SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-1; //Setting MIMO as the preferred function SET UFRC: MIMOor64QAMSwitch=MIMO;
Issue 02 (2011-07-11)
111-5
//Enabling the cell-level MIMO and L2 enhancement MOD UCELLALGOSWITCH: HspaPlusSwitch=MIMO-1&DL_L2ENHANCED-1; //Deactivating the HSDPA cell DEA UCELL: CellId=1; //Activation operation when STTD is used RMV UPRACH: CellId=1, PhyChId=4; ADD UPRACHBASIC: CellId=1, PreambleSignatures=SIGNATURE0-1&SIGNATURE1-1&SIGNATURE2-1&SIGNATURE31&SIGNATURE4-1&SIGNATURE5-1&SIGNATURE6-1&SIGNATURE7-1, RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1&SUBCHANEL3-1&SUBCH ANEL4-1&SUBCHANEL5-1&SUBCHANEL6-1&SUBCHANEL7-1&SUBCHANEL8-1&SUBCHANEL 9-1&SUBCHANEL10-1&SUBCHANEL11-1, Constantvalue=-20, PowerRampStep=3; ADD UPRACHTFC: CellId=1, PhyChId=4, CTFC=0, PowerOffsetPpm=-3, GainFactorBetaC=13, GainFactorBetaD=15; ADD UPRACHTFC: CellId=1, PhyChId=4, CTFC=1, PowerOffsetPpm=-2, GainFactorBetaC=10, GainFactorBetaD=15; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC0; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC1; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC2, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC3, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC4, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC5, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC6, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC7, PersistScalingFactor=D0.9; ADD UPRACHACTOASCMAP: CellId=1, PhyChId=4; ADD UPRACHSLOTFORMAT: CellId=1, SlotFormatNum=D4; ADD URACH: CellId=1, PhyChId=4, TrChId=1; ADD URACHDYNTFS: CellId=1, RLCSize=168, TFsNumber=D1, TbNumber1=1; ADD URACHDYNTFS: CellId=1, RLCSize=360, TFsNumber=D1, TbNumber1=1; ADD UAICH: CellId=1, PRACHPhyChId=4, PhyChId=6, STTDInd=TRUE; ACT UPRACH: CellId=1, PhyChId=4; RMV USCCPCH: CellId=1, PhyChId=8; ADD USCCPCHBASIC: CellId=1, PhyChId=8, ScrambCode=0, STTDInd=TRUE, SlotFormat=D8, TFCIpresence=EXISTS; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=0; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=1; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=2; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=3; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=4; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=6; ADD UPICH: CellId=1, PhyChId=8, STTDInd=TRUE; ADD UFACH: CellId=1, PhyChId=8, TrChId=4, ToAWS=20, ToAWE=10, SigRbInd=FALSE, ChCodingType=CONVOLUTIONAL; ADD UFACH: CellId=1, PhyChId=8, TrChId=5, RateMatchingAttr=220, ToAWS=30, ToAWE=10, MaxCmchPi=D13, MinCmchPi=D0, ChCodingType=TURBO; ADD UFACHDYNTFS: CellId=1, TrChId=4, RLCSize=168, TFsNumber=D3; ADD UFACHDYNTFS: CellId=1, TrChId=5, RLCSize=168, TFsNumber=D2; ADD UFACHLOCH: CellId=1, TrChId=4; ADD UPCH: CellId=1, PhyChId=8; ADD UPCHDYNTFS: CellId=1, RLCSize=240, TFsNumber=D2; ACT USCCPCH:CELLID=1, PHYCHID=8; MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE, STTDSupInd=STTD_Supported, CP1SupInd=CP1_not_Supported, DpchDivModforOther=STTD, FdpchDivModforOther=STTD, DpchDivModforMIMO=STTD,
111-6
Issue 02 (2011-07-11)

FdpchDivModforMIMO=STTD;
//Activation operation when PSP is used MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE; ADD USCPICH: CellId=1, ScpichPhyId=5, ScpichPower=0; //Activating a cell ACT UCELL: CellId=1; //Activating the MIMO-related parameter settings ACT UCELLMIMO: CellId=1; //Operations on the NodeB side ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=2, HPN=0; ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO, ALMPROCSW=OFF; ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=UO, ALMPROCSW=OFF; //Removing a local cell and a sector RMV LOCELL: LOCELL=1; RMV SEC: STN=0, SECN=2; //Adding a sector and setting the transmit 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 2-way transmit diversity ADD LOCELL: LOCELL=1, 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=FALSE; //Deactivation procedure DEA UCELL: CellId=1; DEA UCELLMIMO: CellId=1; //Deactivation operation when PSP is used RMV USCPICH: CellId=1; //Deactivation operation when STTD is used RMV UPRACH: CellId=1, PhyChId=4; RMV USCCPCH: CellId=1, PhyChId=8; MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE; MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=MIMO-0; ACT UCELL: CellId=1;
NodeB V100R013
//Activation procedure //Activation procedure //Operations on the BSC6900 side //Turning on the BSC6900-level MIMO algorithm switch SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-1; //Setting MIMO as the preferred function SET UFRC: MIMOor64QAMSwitch=MIMO; //Enabling the cell-level MIMO and L2 enhancement MOD UCELLALGOSWITCH: HspaPlusSwitch=MIMO-1&DL_L2ENHANCED-1; //Deactivating the HSDPA cell DEA UCELL: CellId=1; //Activation operation when STTD is used RMV UPRACH: CellId=1, PhyChId=4; ADD UPRACHBASIC: CellId=1, PreambleSignatures=SIGNATURE0-1&SIGNATURE1-1&SIGNATURE2-1&SIGNATURE31&SIGNATURE4-1&SIGNATURE5-1&SIGNATURE6-1&SIGNATURE7-1, RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1&SUBCHANEL3-1&SUBCH ANEL4-1&SUBCHANEL5-1&SUBCHANEL6-1&SUBCHANEL7-1&SUBCHANEL8-1&SUBCHANEL 9-1&SUBCHANEL10-1&SUBCHANEL11-1, Constantvalue=-20, PowerRampStep=3; ADD UPRACHTFC: CellId=1, PhyChId=4, CTFC=0, PowerOffsetPpm=-3,
Issue 02 (2011-07-11)
111-7
GainFactorBetaC=13, GainFactorBetaD=15; ADD UPRACHTFC: CellId=1, PhyChId=4, CTFC=1, PowerOffsetPpm=-2, GainFactorBetaC=10, GainFactorBetaD=15; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC0; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC1; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC2, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC3, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC4, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC5, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC6, PersistScalingFactor=D0.9; ADD UPRACHASC: CellId=1, PhyChId=4, AccessServiceClass=ASC7, PersistScalingFactor=D0.9; ADD UPRACHACTOASCMAP: CellId=1, PhyChId=4; ADD UPRACHSLOTFORMAT: CellId=1, SlotFormatNum=D4; ADD URACH: CellId=1, PhyChId=4, TrChId=1; ADD URACHDYNTFS: CellId=1, RLCSize=168, TFsNumber=D1, TbNumber1=1; ADD URACHDYNTFS: CellId=1, RLCSize=360, TFsNumber=D1, TbNumber1=1; ADD UAICH: CellId=1, PRACHPhyChId=4, PhyChId=6, STTDInd=TRUE; ACT UPRACH: CellId=1, PhyChId=4; RMV USCCPCH: CellId=1, PhyChId=8; ADD USCCPCHBASIC: CellId=1, PhyChId=8, ScrambCode=0, STTDInd=TRUE, SlotFormat=D8, TFCIpresence=EXISTS; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=0; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=1; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=2; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=3; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=4; ADD USCCPCHTFC: CellId=1, PhyChId=8, CTFC=6; ADD UPICH: CellId=1, PhyChId=8, STTDInd=TRUE; ADD UFACH: CellId=1, PhyChId=8, TrChId=4, ToAWS=20, ToAWE=10, SigRbInd=FALSE, ChCodingType=CONVOLUTIONAL; ADD UFACH: CellId=1, PhyChId=8, TrChId=5, RateMatchingAttr=220, ToAWS=30, ToAWE=10, MaxCmchPi=D13, MinCmchPi=D0, ChCodingType=TURBO; ADD UFACHDYNTFS: CellId=1, TrChId=4, RLCSize=168, TFsNumber=D3; ADD UFACHDYNTFS: CellId=1, TrChId=5, RLCSize=168, TFsNumber=D2; ADD UFACHLOCH: CellId=1, TrChId=4; ADD UPCH: CellId=1, PhyChId=8; ADD UPCHDYNTFS: CellId=1, RLCSize=240, TFsNumber=D2; ACT USCCPCH:CELLID=1, PHYCHID=8; MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE, STTDSupInd=STTD_Supported, CP1SupInd=CP1_not_Supported, DpchDivModforOther=STTD, FdpchDivModforOther=STTD, DpchDivModforMIMO=STTD, FdpchDivModforMIMO=STTD; //Activation operation when PSP is used MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE; ADD USCPICH: CellId=1, ScpichPhyId=5, ScpichPower=0; //Activating a cell ACT UCELL: CellId=1; //Activating the MIMO-related parameter settings ACT UCELLMIMO: CellId=1; //Operations on the NodeB side ADD RRUCHAIN: RCN=0, TT=CHAIN, HSN=0, HPN=0; ADD RRU: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO, ALMPROCSW=OFF;
111-8
Issue 02 (2011-07-11)

ADD RRU: CN=0, SRN=61, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=UO, ALMPROCSW=OFF; //Removing a local cell and a sector RMV LOCELL: LOCELL=1; RMV SEC: STN=0, SECN=2; //Adding a sector and setting the transmit 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 sector and setting the transmit diversity mode (assuming that DBS3800 is used) ADD LOCELL: LOCELL=1, STN=0, SECN=1, SECT=REMOTE_SECTOR, TTW=TRUE, SRN1=60, SRN2=61, SN2=0, ANT2N=ANTB, ULFREQ=9630, DLFREQ=10580, MXPWR=430, HISPM=FALSE, RMTCM=FALSE, VAM=FALSE; //Deactivation procedure DEA UCELL: CellId=1; DEA UCELLMIMO: CellId=1; //Deactivation operation when PSP is used RMV USCPICH: CellId=1; //Deactivation operation when STTD is used RMV UPRACH: CellId=1, PhyChId=4; RMV USCCPCH: CellId=1, PhyChId=8; MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE; MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=MIMO-0; ACT UCELL: CellId=1;
Issue 02 (2011-07-11)
111-9
112 Configuring Downlink 64QAM+MIMO
112
Prerequisite
l
Configuring Downlink 64QAM +MIMO
This section describes how to activate, verify, and deactivate the optional feature WRFD-010693 DL 64QAM+MIMO.
Dependencies 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.
Dependencies 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 controlling this feature has been activated. Other Prerequisites The CN supports 3GPP Release 8. The BSC6900 software version should not be earlier than RAN12.0. The NodeB software version should not be earlier than RAN12.0. The UE is of 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 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. 2. Run the NodeB MML command MOD LOCELL to modify a local cell. In this step, set DL 64QAM MIMO to TRUE. 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 command SET 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
3.
4.
5.
6.
112-2
Localcell by ID) and then specify Local Cell ID. The execution result displayed on the LMT shows the DL 64QAM+MIMO capability. 2. 3. 4. l 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.
2.
----End
Example
//Activation procedure //Operations on the NodeB side MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, DL64QAM_MIMO=TRUE; //Operations on the BSC6900 side SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1&CFG_HSDPA_MIMO _WITH_64QAM_SWITCH-1; SET UFRC: MIMO64QAMorDCHSDPASwitch=MIMO_64QAM; SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-1&MIMO-1&DL_L2ENHANCED-1&64QAM_MIMO-1; //Verification procedure //Operations on the NodeB side LST LOCELL: MODE=LOCALCELL, LOCELL=1; //Operations on the BSC6900 side LST UCELLALGOSWITCH:CellId=1; LST UCORRMALGOSWITCH: LstFormat=VERTICAL; DSP UCELLCHK:CellId=1; //Deactivation procedure //Operations on the BSC6900 side MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM_MIMO-0; SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_WITH_64QAM_SWITCH-0;
Issue 02 (2011-07-11)
112-3
113 Configuring Performance Improvement of MIMO and HSDPA Co-carrier
Improvement of MIMO and HSDPA Co-carrier

This section describes how to activate, verify, and deactivate the optional feature WRFD-010700 Performance Improvement of MIMO and HSDPA.
113
Configuring Performance
Prerequisite
l Dependencies on Hardware This feature is only supported by 40W RRU3801C, RRU3804, RRU3806, RRU3808, WRFU, RRU3805, WRFUd, RRU3828, RRU3829, RRU3928, RRU3929, MRFUd, MRFUe, and 850M/900M/1900M RRU3908V1. l Dependencies on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010685 Enhanced L2 WRFD-010684 2x2 MIMO l l License The license controlling this feature has been activated. Other Prerequisites The software version should not be earlier than RAN12.0. The UE is of category 15, 16, 17, or 18, as specified by the 3GPP protocols.
Context
CAUTION
Before enabling the feature in an existing cell, you need to deactivate the cell. This, however, will interrupt services in the cell. Therefore, you should enable the feature when the traffic of the cell is low. The feature adopts MIMO in Primary/Secondary common Pilot (PSP) mode, Virtual Antenna Mapping (VAM), and Intelligent Interference Control (ICC), improving performance of MIMO and HSDPA co-carrier.
Data Planning Parameters Site Number Sector number Local cell ID Cell ID SCPICH ID Transmit power of SCPICH [0.1 dB] Example 0 2 1 1 5 0 Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command DEA UCELL to deactivate MIMO cells. Modify values of VAM for the cells. (1) Run the NodeB MML command RMV LOCELL to remove the local cell. (2) Run the NodeB MML command ADD LOCELL to add a local cell. Set VAM to TRUE(TRUE). 3. 4. Run the NodeB MML command SET MACHSPARA. Set IIC Switch to OPEN (open). Configure the PSP function on the BSC6900 side. Run the BSC6900 MML command MOD UCELLSETUP to modify the cell basic information. In this step, set TX Diversity Indication to FALSE. Run the BSC6900 MML command ADD USCPICH to add a secondary common pilot channel (SCPICH). 5. l 1. 2. 3. l Run the BSC6900 MML command ACT UCELL to activate the cell. Run the NodeB MML command LST LOCELL and check whether the value of VAM is TRUE. Run the NodeB MML command LST MACHSPARA and check whether the value of IIC Switch is OPEN. Run the BSC6900 MML command LST USCPICH and check whether an SCPICH is already configured. Run the BSC6900 MML command DEA UCELL to deactivate MIMO cells. Modify values of VAM for the cells. (1) Run the NodeB MML command RMV LOCELL to remove the local cell. (2) Run the NodeB MML command ADD LOCELL to add a local cell. Set VAM to FALSE(FALSE).
3. 4.
Run the NodeB MML command SET MACHSPARA. Set IIC Switch to CLOSE (close). Disable the PSP function on the BSC6900 side. Run the BSC6900 MML command RMV USCPICH to remove a secondary common pilot channel (SCPICH). Run the BSC6900 MML command MOD UCELLSETUP to modify the cell basic information. In this step, set TX Diversity Indication to TRUE.
5. ----End
Run the BSC6900 MML command ACT UCELL to activate the cell.
Example
l NodeB V200R013
//Activation procedure //Operations at the BSC6900 //Deactivating an MIMO cell DEA UCELL: CellId=1; //Operations at the NodeB //Removing a local cell RMV LOCELL: LOCELL=1; //Adding a local cell and setting Two Tx Way and VAM ADD LOCELL: LOCELL=1, STN=0, SECN=2, SECT=REMOTE_SECTOR, TTW=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; //Operations at the BSC6900 //Configuring the PSP function MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE; ADD USCPICH: CellId=1, ScpichPhyId=5, ScpichPower=0; //Activating a cell ACT UCELL: CellId=1; //Verification procedure //Operations at the NodeB //Checking parameter settings of VAM of the local cell LST LOCELL: MODE=LOCALCELL, LOCELL=1; //Checking whether IIC switch is turned on LST MACHSPARA: LOCELL=1; //Operations at the BSC6900 //Checking configuration information about an SCPICH LST USCPICH: CellId=1; //Deactivation procedure //Operations at the BSC6900 //Deactivating an MIMO cell DEA UCELL: CellId=1; //Operations at the NodeB //Removing a local cell RMV LOCELL: LOCELL=1; //Adding a local cell and setting VAM ADD LOCELL: LOCELL=1, 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=FALSE;
Issue 02 (2011-07-11)
113-3

//Turing off the IIC switch SET MACHSPARA: IICSW=CLOSE; //Operations at the BSC6900 //Removing an SCPICH RMV USCPICH: CellId=1; MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE; //Activating a cell ACT UCELL: CellId=1;
NodeB V100R013
//Activation procedure //Operations at the BSC6900 //Deactivating an MIMO cell DEA UCELL: CellId=1; //Operations at the NodeB //Removing a local cell RMV LOCELL: LOCELL=1; //Adding a local cell and setting Two Tx Way and VAM (assuming that DBS3800 is used) ADD LOCELL: LOCELL=1, STN=0, SECN=2, SECT=REMOTE_SECTOR, TTW=TRUE, SRN1=60, SRN2=61, SN2=0, ANT2N=ANTB, ULFREQ=9845, DLFREQ=10795, HISPM=FALSE, MXPWR=460, RMTCM=FALSE, VAM=TRUE; //Turing on the IIC switch SET MACHSPARA: IICSW=OPEN; //Operations at the BSC6900 //Configuring the PSP function MOD UCELLSETUP: CellId=1, TxDiversityInd=FALSE; ADD USCPICH: CellId=1, ScpichPhyId=5, ScpichPower=0; //Activating a cell ACT UCELL: CellId=1; //Verification procedure //Operations at the NodeB //Checking parameter settings of VAM of the local cell LST LOCELL: MODE=LOCALCELL, LOCELL=1; //Checking whether IIC switch is turned on LST MACHSPARA: LOCELL=1; //Operations at the BSC6900 //Checking configuration information about an SCPICH LST USCPICH: CellId=1; //Deactivation procedure //Operations at the BSC6900 //Deactivating an MIMO cell DEA UCELL: CellId=1; //Operations at the NodeB //Removing a local cell RMV LOCELL: LOCELL=1; //Adding a local cell and setting VAM (assuming that DBS3800 is used) ADD LOCELL: LOCELL=1, STN=0, SECN=2, SECT=REMOTE_SECTOR, TTW=TRUE, SRN1=60, SRN2=61, SN2=0, ANT2N=ANTB, ULFREQ=9845, DLFREQ=10795, HISPM=FALSE, MXPWR=460, RMTCM=FALSE, VAM=FALSE; //Turing off the IIC switch SET MACHSPARA: IICSW=CLOSE; //Operations at the BSC6900 //Removing an SCPICH RMV USCPICH: CellId=1;
113-4
Issue 02 (2011-07-11)

MOD UCELLSETUP: CellId=1, TxDiversityInd=TRUE; //Activating a cell ACT UCELL: CellId=1;
Issue 02 (2011-07-11)
113-5
114 Configuring Flexible HSPA+ Technology Selection
114
Prerequisite
l
Configuring Flexible HSPA+ Technology Selection
This section describes how to activate, verify, and deactivate the optional feature WRFD-010704 Flexible HSPA+ Technology Selection.
Dependencies on Hardware The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EBBI, EBOI, and EDLP boards. In addition, the uplink service cannot be established on the HBBI or HULP board. In DBS3800, the BBU3806 must be configured with the EBBC or EBBCd board, and the BBU3806C must be configured with the EBBM board. The 3900 series base stations must be configured with the WBBPb or WBBPd board.
Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010696 DC-HSDPA and RFD-010684 22 MIMO. This feature is mutually exclusive to the features WRFD-010699 DC-HSDPA+MIMO (trial).
l l
License The license controlling this feature has been activated. Other Prerequisites In 22 MIMO mode, two RF units must be interconnected. The UE has the HSDPA Category21 or higher capability, including HSDPA category 21, 22, 23, 24, 25, 26, 27, and 28.
Context
DC-HSDPA and MIMO can achieve gains under different conditions. DC-HSDPA ensures a comparatively high throughput for the UEs when few HSDPA-capable UEs camp on a cell that has a light load. MIMO ensures a comparatively high throughput for the UEs when a large number of HSDPA-capable UEs camp on an overloaded cell. When one or two carriers in DC-HSDPA networking support MIMO, Flexible HSPA+ Technology Selection dynamically selects DC-HSDPA or MIMO for newly accessing UEs,
based on the current number of HSDPA-capable UEs and downlink load of the carriers that support MIMO. This ensures an optimum service bearing mode.
Procedure
l Activation Procedure 1. Turn off the RNC-oriented DC+MIMO algorithm switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH with CFG_HSDPA_DCMIMO_SWITCH deselected in the Channel Configuration Strategy Switch drop-down list. Optional: Turn on the HSDPA algorithm switch for streaming services if HSDPA is required for streaming services. Run the BSC6900 MML command SET UCORRMALGOSWITCH with MAP_PS_STREAM_ON_HSDPA_SWITCH selected in the Service Mapping Strategy Switch drop-down list. Set HSDPA thresholds for downlink streaming services and HSDPA thresholds for downlink BE services. Run the BSC6900 MML command SET UFRCCHLTYPEPARA with DL streaming traffic threshold on HSDPA and DL BE traffic threshold on HSDPA set to appropriate values based on network planning. Set the TX power threshold and HSDPA user number threshold of the secondary cell for the DC/MIMO dynamic selection algorithm. Run the BSC6900 MML command SET UFRC with DL TX Power Threshold of Secondary Cell and Threshold of HSDPA Users in Secondary Cell set to appropriate values. Have a UE access the secondary cell and initiate an HSDPA service. Query the DL power load of the secondary cell covered by the DC carrier group. On the BSC6900 LMT, choose Monitor > Monitor > UMTS Monitoring > Cell Performance Monitoring and select Cell DL Carrier TX Power in the Monitor Item: drop-down list. Check whether the value of the IE dl-TransportChannelType in the rb-MappingInfo of the RRC_RB_SETUP message is hsdsch. Expected result: As shown in Figure 114-2, the RRC_RB_SETUP message in the Uu tracing result contains the mimoParameters IE when the downlink power of the secondary cell covered by the DC carrier group is greater than or equal to DL TX Power Threshold of Secondary Cell set in Step 1 and the number of HSDPA users is greater than or equal to Threshold of HSDPA Users in Secondary Cell set in Step 1. The RRC_RB_SETUP message in the Uu tracing result contains the dlSecondaryCellInfoFDD IE when the downlink power of the secondary cell covered by the DC carrier group is smaller than DL TX Power Threshold of Secondary Cell set in Step 1 and the number of HSDPA users is smaller than Threshold of HSDPA Users in Secondary Cell set in Step 1.
2.
3.
2. 3.
4.
114-2
Issue 02 (2011-07-11)
Figure 114-1 mimoParameters message
Figure 114-2 dl-SecondaryCellInfoFDD IE
Deactivation Procedure 1. Turn off the DC/MIMO dynamic selection algorithm switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH with CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH deselected in the Channel Configuration Strategy Switch drop-down list.
----End
Example
//Activation procedure //Turning off the RNC-oriented DC+MIMO algorithm switch SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DCMIMO_SWITCH-0; //(Optional) Enabling the HSDPA algorithm switch for streaming services if HSDPA is required for streaming services SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; //Setting the HSDPA threshold for downlink streaming services and HSDPA threshold for downlink BE services SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; //Verification procedure SET UFRC: SecCellTcpThd=10, SecCellHUserNumThd=1; //Deactivation procedure SET UCORRMALGOSWITCH: CfgSwitch=CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH-0;
Issue 02 (2011-07-11)
114-3
115 Configuring CPC - DTX /DRX
115
Prerequisite
l
Configuring CPC - DTX /DRX
This section describes how to activate, verify, and deactivate the optional feature WRFD-010686 CPC - DTX /DRX.
Dependencies on Hardware Dependencies on BSC6900 Hardware This feature does not depend on the hardware. Dependencies on NodeB Hardware The BTS3812E, BTS3812A, or BTS3812AE is configured with the EBBI, EBOI, EULP/EULPd (supporting DTX), and EDLP (supporting DRX) boards. The BBU3806 is configured with the EBBC or EBBCd board. The BBU3806C is configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010610 SRB over HSUPA and WRFD-010652 SRB over HSDPA.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE is of 3GPP Release 7 or later and supports this feature.
Context
This feature is related to DTX and DRX. It can reduce the interference between UEs, improve the HSPA+ user capacity per cell and save the battery consumption of the UE.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select DTX_DRX from the Cell Hspa Plus function switch drop-down list.
Issue 02 (2011-07-11)
2.
Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select CFG_HSPA_DTX_DRX_SWITCH from the Channel Configuration Strategy Switch drop-down list. Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, select HSPA (Uplink is preferably carried on E-DCH and downlink is preferably carried on HS-DSCH) from the Type of Channel Preferably Carrying Signaling RB drop-down list. Create a Uu tracing task on the BSC6900 LMT, as shown in Figure 115-1.
3.
Figure 115-1 Uu interface tracing task
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 Figure 115-2. Figure 115-2 IE information
dtx-drx-TimingInfo dtx-drx-Info l
115-2
1. ----End
Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect DTX_DRX from the Cell Hspa Plus function switch drop-down list.
Example
//Activating CPC - DTX /DRX MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=DTX_DRX-1; SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_DTX_DRX_SWITCH-1; SET UFRCCHLTYPEPARA: SrbChlType=HSPA; //Deactivating CPC - DTX /DRX MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=DTX_DRX-0;
Issue 02 (2011-07-11)
115-3
116 Configuring CPC-HS-SCCH Less Operation
116
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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 controlling this feature has been 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 MOD 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.
2.
Issue 02 (2011-07-11)
Verification Procedure 1. Use an HSPA-supportive UE to initiate a PS service. The service is carried on E-DCH and HS-DSCH.
NOTE
How to make the service on E-DCH, see section 82 Configuring HSUPA Introduction Package.
2.
Check the RRC_RB_SETUP message traced over the Uu interface. You can find the hs-scch-LessInfo IE which contains the parameters related to CPC-HSSCCH less operation, as shown in Figure 116-1.
Figure 116-1 RRC_RB_SETUP Information
Deactivation Procedure 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; MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=HS_SCCH_LESS_OPERATION-1; //Deactivating CPC-HS-SCCH Less operation SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_HSSCCH_LESS_OP_SWITCH-0; MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=HS_SCCH_LESS_OPERATION-0;
Issue 02 (2011-07-11)
116-3
117 Configuring 96 HSDPA Users per Cell
117
Prerequisite
l
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.
Dependencies on Hardware In order to support this feature, EBBI, EBOI, EULP, EULPd is needed for BTS3812E and BTS3812AE. EBBC, EBBCd is needed for BBU3806. EBBM is needed for BBU3806C. WBBPb, WBBPd is needed for BBU3900.
Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010623 64 HSDPA Users per Cell and WRFD-010686 CPC-DTX/DRX.
Context
This feature enables an HSDPA cell to serve a maximum of 96 users performing VoIP or other low-rate services, increasing capacity of voice services or other low-rate services.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect the HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes under the parameter Cell CAC algorithm switch, and select the DTX_DRX(Cell DTX_DRX Function Switch) check box under the parameter Cell Hspa Plus function switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HSPA state transition. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA.
2. 3.
Issue 02 (2011-07-11)
4. 5.
Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources to E-AGCHs and E-RGCHs. Run the BSC6900 MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSDPA users per cell to 96. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number. Use UEs to access the cell successively and then establish PS services, for example, download files through FTP. Expected result: Each UE establishes PS services successfully. If the number of UEs is less than or equal to 96, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels. If the number of UEs is greater than 96, HSPA services of the excessive UEs are carried on R99 channels.
2.
3.
Check the maximum number of users through the counter VS.HSDPA.UE.Max.Cell on the M2000.
NOTE
The 96 HSDPA users referred to in this feature are of the SRB Over HSPA type.
----End
Example
/*Activating 96 HSDPA Users per Cell*/ //Disabling the admission control function in an HSPA cell on the Uu interface and enabling the DTX-DRX function MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; //Disabling HSPA state transition SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; //Enabling SRB over HSPA SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; //Allocating code resources to E-AGCHs and E-RGCHs MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=6; //Stop reserving uplink and downlink credit resources and setting the maximum number of HSDPA users to 96 MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=96, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
117-2
Issue 02 (2011-07-11)
118
Prerequisite
l
Dependencies on Hardware In order to support this feature, EBBI, EBOI, EULP, EULPd is needed for BTS3812E and BTS3812AE. EBBC, EBBCd is needed for BBU3806.EBBM is needed for BBU3806C. WBBPb, WBBPd is needed for BBU3900.
Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010634 60 HSUPA Users per Cell and WRFD-010653 96 HSDPA Users per Cell.
Context
This feature enables an HSUPA cell to serve a maximum of 96 users performing VoIP or other low-rate services, increasing the capacity of voice services or other low-rate services per cell.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect the HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes under the parameter Cell CAC algorithm switch, and select the DTX_DRX(Cell DTX_DRX Function Switch) check box under the parameter Cell Hspa Plus function switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HSPA state transition.
2.
Issue 02 (2011-07-11)
3. 4. 5.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources to E-AGCHs and E-RGCHs. Run the BSC6900 MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSUPA users per cell to 96. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number. Use UEs to access the cell successively and then establish PS services, for example, upload files through FTP. Expected result: Each UE establishes PS services successfully. If the number of UEs is less than or equal to 96, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels. If the number of UEs is greater than 96, HSPA services of the excessive UEs are carried on R99 channels.
2.
3.
Check the maximum number of users indicated by the counter VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
----End
Example
/*Activation procedure*/ //Disabling the admission control function in an HSPA cell on the Uu interface and enabling the DTX-DRX function MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; //Disabling HSPA state transition SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; //Enabling SRB over HSPA SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; //Allocating code resources to E-AGCHs and E-RGCHs MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=6; //Stopping reserving uplink and downlink credit resources and setting the maximum number of HSUPA users to 96 MOD UCELLCAC: CellId=111, MaxHsupaUserNum=96, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
118-2
Issue 02 (2011-07-11)
119
Prerequisite
l l
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.
Dependencies on Hardware The feature is only available for 3900 series NodeB, 3900 series NodeB (except BTS3902E) requires WBBPd2/WBBPd3 board which is one type of WBBPd. Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010653 96 HSDPA Users per Cell and WRFD-010670 128 HSUPA Users per Cell.
Context
This feature can increase the capacity of voice services in a cell, especially in cells with VoIP users or a large number of low-rate users. This feature enables an HSDPA cell to serve a maximum of 128 users performing VoIP or other low-rate services. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
2.
Issue 02 (2011-07-11)
3. 4. 5.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources to E-AGCHs and E-RGCHs. Run the BSC6900 MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSDPA users per cell to 128. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number. Use UEs to access the cell successively and then establish PS services, for example, download files through FTP. Expected result: Each UE establishes PS services successfully. If the number of UEs is less than or equal to 128, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels. If the number of UEs is greater than 128, HSPA services of the excessive UEs are carried on R99 channels.
2.
3.
Check the maximum number of users through the counter VS.HSDPA.UE.Max.Cell on the M2000.
NOTE
The 128 HSDPA users referred to in this feature are of the SRB Over HSPA type.
----End
Example
/*Activating 128 HSDPA Users per Cell*/ //Disabling the admission control function in an HSPA cell on the Uu interface and enabling the DTX-DRX function MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; //Disabling HSPA state transition SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; //Enabling SRB over HSPA SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; //Allocating code resources to E-AGCHs and E-RGCHs MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=8; //Stop reserving uplink and downlink credit resources and setting the maximum number of HSDPA users to 128 MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=128, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
119-2
Issue 02 (2011-07-11)
120
Prerequisite
l l
Dependencies on Hardware The feature is only available for 3900 series NodeB, 3900 series NodeB (except BTS3902E) requires WBBPd2/WBBPd3 board which is one type of WBBPd. Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010639 96 HSUPA Users per Cell and WRFD-010654 128 HSDPA Users per Cell.
Context
This feature can increase the capacity of voice services in a cell with a large number of low-rate users, such as VoIP users. This feature enables an HSUPA cell to serve a maximum of 128 users performing VoIP or other low-rate services. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
2.
Issue 02 (2011-07-11)
3. 4. 5. l
Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources to E-AGCHs and E-RGCHs. Run the BSC6900 MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSUPA users to 128. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number. Use UEs to access the cell successively and then establish PS services, for example, upload files through FTP. Expected result: Each UE establishes PS services successfully. If the number of UEs is less than or equal to 128, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels. If the number of UEs is greater than 128, HSPA services of the excessive UEs are carried on R99 channels.
2.
3.
Check the maximum number of users indicated by the counter VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
----End
Example
/*Activating 128 HSUPA Users per Cell*/ //Disabling the admission control function in an HSPA cell on the Uu interface and enabling the DTX-DRX function MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1; //Disabling HSPA state transition SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0; //Enabling SRB over HSPA SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE; //Allocating code resources to E-AGCHs and E-RGCHs MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=8; //Stop reserving uplink and downlink credit resources and setting the maximum number of HSUPA users to 128 MOD UCELLCAC: CellId=111, MaxHsupaUserNum=128, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
120-2
Issue 02 (2011-07-11)
121 Configuring HSUPA UL Interference Cancellation
121
Prerequisite
l
Configuring HSUPA UL Interference Cancellation
This section describes how to activate, verify, and deactivate the optional feature WRFD-010691 HSUPA UL Interference Cancellation.
Dependencies 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. When configured with EBBI/EDLP+EULPd, the base station can support HSUPA UL Interference Cancellation. 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 UL Interference Cancellation. In the case of the 3900 series base station, the WBBPb board needs to be configured.
l l l
Dependencies on Other Features WRFD-010612 HSUPA Introduction Package. License The license controlling this feature has been activated. Other Prerequisites The NodeB software version should not be earlier than RAN12.0. The BSC6900 software version should not be 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, 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 Adding a Baseband Board to a 3900 Series Base Station. l If the DBS3800 is configured with two EBBCd boards, it is recommended that two uplink resource groups be allocated to the two boards separately. In this way, both the boards support HSUPA uplink interference cancellation. For details about how to configure the active and standby BTSs, see Adding an EBBC or EBBCd 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 Adding a Baseband Board to BTS3812E or BTS3812AE.
Procedure
l Activation Procedure 1. 2. 3. l 1. 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 to TRUE. Run the BSC6900 MML command ACT UCELL to activate the cell. Run the NodeB MML command DSP LOCELL to query the status of a specified local cell. Expected result: The value of IC MODE is ENABLED. 2. Select Service > Realtime Specific Monitoring > Cell RTWP from the navigation tree in Maintenance tab on NodeB LMT, as shown in Figure 121-1. The column 1-3 indicates the state of this feature disabled, the column 1-4 indicates the state of this feature enabled. If the value of column 1-4 is less than the value of column 1-3, it indicates the feature has been enabled. Figure 121-1 Cell RTWP 1
l
121-2
1. ----End
Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set IC to FALSE.
Example
//Activation procedure DEA UCELL: CellId=1; MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, IC_MODE=TRUE; ACT UCELL: CellId=1; //Verification procedure DSP LOCELL: LOCELL=1; //Deactivation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, IC_MODE=FALSE;
Issue 02 (2011-07-11)
121-3
122 Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation
122
Prerequisite
l
Configuring Dual-Threshold
Scheduling with HSUPA Interference Cancellation
This section describes how to activate, verify, and deactivate the optional feature WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation.
Dependencies on Hardware The BTS3812E or BTS3812AE must be configured with the EULPd board. The DBS3800 must be configured with the EBBCd board. The 3900 series base stations must be configured with the WBBPd board in slot 2 or slot 3. For detailed installation steps, see the BBU3900 Installation Guide.
Dependencies on Other Features WRFD-010612 HSUPA Introduction Package WRFD-010691 HSUPA UL Interference Cancellation
Context
This feature is applicable in cells enabled with the WRFD-010691 HSUPA UL Interference Cancellation feature.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set the MAC-e Schedule Para to YES. Set the Max Target RoT Difference Before and After IC to 2. l
Issue 02 (2011-07-11)
1. 2. 3.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set Max Target RoT Difference Before and After IC to 0. Use multi users to carry out upload service. Select Service > Realtime Specific Monitoring > Cell RTWP from the navigation tree in Maintenance tab on NodeB LMT, as shown in Figure 122-1. The column 1-3 indicates the state of this feature disabled, the column 1-4 indicates the state of this feature enabled. If the value of column 1-4 is less than the value of column 1-3, it indicates HSUPA UL Interference Cancellation feature has been enabled. Figure 122-1 Cell RTWP 1
4. 5.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set Max Target RoT Difference Before and After IC to 2. Check the Cell RTWP window. If the value of column 1-4 is less than the value of column 1-3, and the values of column 1-4 and column 1-3 increase by 10, it indicates dual-threshold scheduling with HSUPA interference cancellation feature has been enabled.
NOTE
The prerequisite of the foregoing result is the cell power limit does not over.
Figure 122-2 Cell RTWP 2
Deactivation Procedure 1. 2. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set Max Target RoT Difference Before and After IC to 0. Reallocate the license of this feature on M2000 LMT, and set Allocated to 0.
----End
Example
//Activation procedure SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, MAXDELTAOFTARGETROT=2, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; //Verification procedure SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, MAXDELTAOFTARGETROT=0, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, MAXDELTAOFTARGETROT=2, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; //Deactivation procedure SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, MAXDELTAOFTARGETROT=0, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
Issue 02 (2011-07-11)
122-3
123 Configuring Anti-Interference Scheduling for HSUPA
123
Prerequisite
l
Configuring Anti-Interference Scheduling for HSUPA
This section describes how to activate, verify, and deactivate the optional feature WRFD-020136 Anti-Interference Scheduling for HSUPA.
Dependencies on Hardware The BTS3812E/BTS3812AE must be configured with the HBBI/HULP/EBBI/EBOI/ EULP or EULPd board. Downlink services can be established only on the EBBI/EBOI or EDLP board. The BBU3806 must be configured with the EBBC or EBBCd board; the BBU3806C must be configured with the EBBM board. The BBU3900 is configured with the WBBPb or WBBPd board.
l l
Dependencies on Other Features WRFD-010612 HSUPA Introduction Package License The license controlling this feature has been activated.
Context
In commercial networks, the uplink data transmission of HSUPA at some sites is affected randomly by strong external interference. When a site is strongly interfered, the HSUPA throughput of the site is significantly reduced and user experience is affected. This feature can eliminate the strong external interference and maintain high HSUPA throughput, improving user experience.
NOTE
This feature is not proposed for multi-RRU cells.
Procedure
l Activation Procedure 1.
Issue 02 (2011-07-11)
Run the NodeB MML command SET MACEPARA to set Mac-e parameters.
(1) Set the MAC-e Schedule Para to YES(YES). (2) Set the Anti-Interference Scheduling Switch to ON(ON). (3) Own Cell UL Load Ratio In indoor coverage scenarios, the recommended value is 90. In non-indoor coverage scenarios, the recommended value is 60. (4) It is recommended to set the Min UL Cover Load Threshold(dB) to 13.
NOTE
If Local Cell ID is not specified, the Mac-e scheduling parameters of all local cells under the NodeB will be set.
2. l
Run the BSC6900 MML command MOD UCELLHSUPA, it is recommended to set the Maximum Target Uplink Load Factor to 75. Run the NodeB MML command DSP LICENSE to display license information. Exception result: the value of Anti-Interference Scheduling for HSUPA Function (per Cell) is bigger than 0. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set the MAC-e Schedule Para to YES(YES). Set the Anti-Interference Scheduling Switch to OFF(OFF).
2.
3.
Make interference. For example: Run the NodeB MML command SET DESENS, set Desensitization Intensity to 6. Use a UE to carry out HSUPA upload task. Select Service > Realtime Specific Monitoring > Cell RTWP from the navigation tree in Maintenance tab on NodeB LMT, as shown in Figure 123-1. The column 1-3 indicates the state of this feature disabled. Figure 123-1 Cell RTWP (feature disabled)
4. 5.
123-2
Issue 02 (2011-07-11)
6.
Run the NodeB MML command SET MACEPARA to set Mac-e parameters. (1) Set the Anti-Interference Scheduling Switch to ON(ON). (2) Own Cell UL Load Ratio In indoor coverage scenarios, the recommended value is 90. In non-indoor coverage scenarios, the recommended value is 60. (3) It is recommended to set the Min UL Cover Load Threshold(dB) to 13.
NOTE
If Local Cell ID is not specified, the Mac-e scheduling parameters of all local cells under the NodeB will be set.
7.
Select Service > Realtime Specific Monitoring > Cell RTWP from the navigation tree in Maintenance tab on NodeB LMT, as shown in Figure 123-1. The column 1-3 indicates the state of this feature enabled. If the values of column 1-3 in Figure 123-1 are bigger than the values of 1-3 in Figure 123-2, it indicates the feature has been enabled. Figure 123-2 Cell RTWP (feature enabled)
Deactivation Procedure 1. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set the MAC-e Schedule Para to YES(YES). Set the Anti-Interference Scheduling Switch to OFF(OFF).
----End
Example
//Activation procedure SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=ON, OWNCELLULLOADRATIO=60, LOADTHRESH4MINULCOV=13, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; MOD UCELLHSUPA: CellId=0, MaxTargetUlLoadFactor=75;
Issue 02 (2011-07-11)
123-3
//Verification procedure DSP LICENSE:; SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=OFF, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; SET DESENS: LOCELL=0, DI=6; SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=ON, OWNCELLULLOADRATIO=60, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO; //Deactivation procedure SET MACEPARA: LOCELL=0, SCHEDULEPARA=YES, OUTERSYSINTERSCHSW=OFF, EAGCHPCPARA=NO, SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
123-4
Issue 02 (2011-07-11)
124 Configuring HSUPA Frequency Domain Equalization
124
Prerequisite
l
Configuring HSUPA Frequency Domain Equalization
This section describes how to activate, verify, and deactivate the optional feature HSUPA Frequency Domain Equalization.
Dependencies 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.
Dependencies on Other Features WRFD-010612 HSUPA Introduction Package. WRFD-01061403 HSUPA 2ms TTI.
l l
License The license controlling this feature has been activated. Other Prerequisites The BSC6900 software version should not be earlier than RAN12.0. The NodeB software version should not be earlier than RAN12.0. The UEs must belong in E-DCH categories 6 or 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, therefore suppressing the inter-path interference on the EDPDCH. In this manner, the SNR on the EDPDCH is increased and the UL system capacity of
124 Configuring HSUPA Frequency Domain Equalization
the HSUPA network is expanded. The rate of HSUPA services is also increased in multipath environment.
NOTE
For UEs of category 6 and category 7 at a transmission rate higher than 2 Mbit/s, the feature brings notable gains if multipath channels are used in the uplink.
Procedure
l Activation Procedure 1. l Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set FDE to TRUE. Run the NodeB MML command DSP LOCELL to query the configuration information about the local cell. Expected result: The value of FDE MODE is ENABLED. Run the NodeB MML command MOD LOCELL to modify the local cell. In this step, set FDE to FALSE.
----End
Example
//Activation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, FDE_MODE=TRUE; //Verification procedure DSP LOCELL: LOCELL=1; //Deactivation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, FDE_MODE=FALSE;
124-2
Issue 02 (2011-07-11)
125 Configuring Uplink 16QAM
125
Prerequisite
l
Configuring Uplink 16QAM
This section describes how to activate, verify, and deactivate the optional feature WRFD-010694 Uplink 16QAM.
Dependencies 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.
Dependencies on Other Features WRFD-010612 HSUPA Introduction Package WRFD-010652 SRB over HSDPA WRFD-01061403 HSUPA 2ms TTI
l l
License The license controlling this feature has been activated. Other Prerequisites The CN supports the "peak rate per user" introduced by UL 16QAM. The BSC6900 software version should not be earlier than RAN12.0. The NodeB software version should not be earlier than RAN12.0. The UE is of 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.
Issue 02 (2011-07-11)
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 DSP LOCELL to query the configuration information of the local cell. As Figure 125-1 shows, start Uu interface tracing on the BSC6900 LMT. Figure 125-1 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 125-2, if the EDCH information IE contains the indicator of uplink 16QAM, you can infer that this feature has been activated. If the EDCH information IE does not contain the indicator of uplink 16QAM, you can infer that this feature has not been activated.
125-2
Issue 02 (2011-07-11)
Figure 125-2 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 MOD LOCELL: LOCELL=1, UL_16QAM=TRUE; //Verification procedure DSP LOCELL: LOCELL=1; //Deactivation procedure MOD LOCELL: LOCELL=1, UL_16QAM=FALSE;
Issue 02 (2011-07-11)
125-3
126 Configuring E-DPCCH Boosting
126
Prerequisite
l
Configuring E-DPCCH Boosting
This section describes how to activate, verify, and deactivate the optional feature WRFD-010697 E-DPCCH Boosting.
Dependencies on Hardware The BTS3812E/BTS3812AE is configured with the Enhanced NodeB HSPA supported Uplink Processing unit REV:d (EULPd) board. The DBS3800 is configured with the Enhanced Base Band Card REV:d (EBBCd) board. 3900 series base stations are configured with WCDMA Baseband Process Unit REV:d (WBBPd) boards.
Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. The UE is of 3GPP Release-7 or later and supports this feature.
Context
An E-DCH Dedicated Physical Control Channel (E-DPCCH) is used for channel estimation to improve the estimation accuracy when the HSUPA service data is demodulated. In this way, the requirement for Dedicated Physical Control Channel (DPCCH) power is lowered, increasing the HSUPA service rate.
Procedure
NOTE
When this feature is enabled together with the feature WRFD-010694 Uplink 16QAM, you are advised to configure the network bandwidth over the Iub interface to 16 Mbit/s or higher if ATM transmission is applied and to 15 Mbit/s or higher if IP transmission is applied.
1.
Configure the bandwidth over the Iub interface in ATM transmission mode. (1) Configure the type of primary and secondary paths required by various services: Run the BSC6900 MML command ADD TRMMAP. In this step, specify
Issue 02 (2011-07-11)
126-1
TRMMAP ID, set Interface Type to IUB (Iub Interface) and Transport Type to ATM(ATM), and specify SRB primary path and SRB secondary path. (2) Add an activation factor table: Run the BSC6900 MML command ADD TRMFACTOR. In this step, specify Factor table index and Remark, and change the activation factor. (3) Add the TRM mapping to an adjacent node: Run the BSC6900 MML command ADD ADJMAP. In this step, set Interface Type to IUB (Iub Interface) and Transport Type of the adjacent node and interface type to ATM(ATM), and specify Gold user TRMMAP index, Silver user TRMMAP index, Bronze user TRMMAP index, and Factor table index. (4) Add ATM traffic records corresponding to the type of the primary and secondary paths set in 1.1 (you are advised to configure the network bandwidth over the Iub interface to 16 Mbit/s or higher): Run the BSC6900 MML command ADD ATMTRF. In this step, specify Traffic index, Service type, Rate unit, and Peak cell rate. (5) Add an AAL2 path: Run the BSC6900 MML command ADD AAL2PATH. In this step, specify TX traffic record index and RX traffic record index. (6) Add an AAL2 route: Run the BSC6900 MML command ADD AAL2RT. 2. Configure the bandwidth over the Iub interface in IP transmission mode. (1) Configure the type of primary and secondary paths required by various services: Run the BSC6900 MML command ADD TRMMAP. In this step, specify TRMMAP ID, set Interface Type to IUB (Iub Interface) and Transport Type to IP(IP), and specify SRB primary path and SRB secondary path. (2) Add an activation factor table: Run the BSC6900 MML command ADD TRMFACTOR. In this step, specify Factor table index and Remark, and change the activation factor. (3) Add the TRM mapping to an adjacent node: Run the BSC6900 MML command ADD ADJMAP. In this step, set Interface Type to IUB (Iub Interface) and Transport Type of the adjacent node and interface type to IP(IP), and specify Gold user TRMMAP index, Silver user TRMMAP index, Bronze user TRMMAP index, and Factor table index. (4) Add an IP path (you are advised to configure the network bandwidth over the Iub interface to 15 Mbit/s or higher): Run the BSC6900 MML command ADD IPPATH. In this step, specify Interface Type, Transport Type, IP path type, Forward Bandwidth, and Backward Bandwidth. (5) Set the mapping from the PHB to the DSCP based on the service type: Run the BSC6900 MML command SET PHBMAP. 3. Configure the E-DPCCH Boosting function. (1) Turn on the E-DPCCH Boosting algorithm switch: Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Channel Configuration Strategy Switch to CFG_EDPCCH_BOOSTING_SWITCH. (2) If streaming services are to be enabled with E-DPCCH Boosting, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Service Mapping Strategy Switch to MAP_PS_STREAM_ON_HSUPA_SWITCH to ensure that streaming services are carried over HSUPA.
(3) Set the rate threshold for BE services and streaming services carried over HSUPA: Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, specify UL streaming traffic threshold on HSUPA and UL BE traffic threshold on HSUPA. (4) Configure HSUPA-related parameters for a cell: Run the BSC6900 MML command ADD UCELLHSUPA.
NOTE
Retain the default values of Code Number for E-AGCH, Code Number for E-RGCH/ E-HICH, Maximum Target Uplink Load Factor, and Target Non-serving E-DCH to Total E-DCH Power Ratio.
(5) Activate the HSUPA function for a cell: Run the BSC6900 MML command ACT UCELLHSUPA. (6) Enable the E-DPCCH Boosting function for a cell: Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Cell Hspa Plus function switch to EDPCCH_BOOSTING. (7) Turn on the E-DPCCH Boosting retry algorithm switch: Run the BSC6900 MML command SET UFRC. In this step, set HSPA Technologies Retried by UEs to EDPCCH_BOOSTING. (8) Enable the E-DPCCH Boosting function for a cell on the NodeB side: Run the NodeB MML command MOD LOCELL. l Verification Procedure 1. 2. Establish PS BE HSUPA services with the uplink rate higher than 1 Mbit/s. Trace messages over the Uu interface by referring to Tracing Messages on the Uu Interface to check whether the RRC_RB_SETUP message carries the e-TFC-BoostInfo information element (IE) that includes the e-TFCI-Boost and delta-T2TP fields, as shown in Figure 126-1. Figure 126-1 Tracing messages over the Uu interface
3.
Trace messages over the Iub interface by referring to Tracing Messages on the Iub Interface to check whether the NBAP_RL_RECFG_PREP message carries the eTFCI-Boost-Information IE that includes the e-TFCI-BetaEC-Boost and uLDelta-T2TP fields, as shown in Figure 126-2.
Issue 02 (2011-07-11)
126-3
Figure 126-2 Tracing messages over the Iub interface
If the messages described in the preceding two steps carry the corresponding IEs, the E-DPCCH Boosting function has taken effect. If either of the messages described in the preceding two steps does not carry the corresponding IEs, the E-DPCCH Boosting function has not taken effect. l Deactivation Procedure 1. To disable the E-DPCCH Boosting function of all cells under the BSC6900, do as follows: Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the CFG_EDPCCH_BOOSTING_SWITCH check box under the parameter Channel Configuration Strategy Switch. To disable the E-DPCCH Boosting function in a single cell, do as follows: (1) Method 1: Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect the EDPCCH_BOOSTING check box under the parameter Cell Hspa Plus function switch to disable the E-DPCCH Boosting function in a cell on the BSC6900 side. (2) Method 2: Run the NodeB MML command MOD LOCELL to disable the EDPCCH Boosting function in a cell on the NodeB side. ----End
2.
Example
/*Activating E-DPCCH Boosting */ /*Configuring the network bandwidth over the Iub interface in ATM transmission mode*/ //Configuring the type of the primary and secondary paths required by various services ADD TRMMAP: TMI=15, ITFT=IUB, TRANST=ATM, SRBPRIPATH=RT_VBR, SRBSECPATH=UBR; //Adding an activation factor table ADD TRMFACTOR: FTI=20, REMARK="Iub"; //Adding the TRM mapping to an adjacent node ADD ADJMAP: ANI=4, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE, TMIGLD=15, TMISLV=15, TMIBRZ=15, FTI=20;
126-4
Issue 02 (2011-07-11)
//Adding ATM traffic records corresponding to the type of the primary and secondary paths required by various services ADD ATMTRF: TRFX=150, ST=RTVBR, UT=KBIT/S, PCR=16000, SCR=15000; ADD ATMTRF: TRFX=151, ST=UBR, UT=KBIT/S, PCR=16000; //Adding AAL2 paths ADD AAL2PATH:ANI=4, PATHID=1, CARRYT=IMA, CARRYF=2, CARRYSN=14, CARRYIMAGRPN=0, RSCGRPFLAG=NO, VPI=7, VCI=71, TXTRFX=150, RXTRFX=150, OWNERSHIP=LOCAL, TIMERCU=10, TRMLOADTHINDEX=0, AAL2PATHT=SHARE; ADD AAL2PATH:ANI=4, PATHID=2, CARRYT=IMA, CARRYF=2, CARRYSN=14, CARRYIMAGRPN=0, RSCGRPFLAG=NO, VPI=7, VCI=72, TXTRFX=151, RXTRFX=151, OWNERSHIP=LOCAL, TIMERCU=10, TRMLOADTHINDEX=0, AAL2PATHT=SHARE; //Adding AAL2 routes ADD AAL2RT: NSAP="H'45020304050607088F0000000000000000000000", ANI=4, RTX=1, OWNERSHIP=YES; ADD AAL2RT: NSAP="H'45020304050607088F0000000000000000000000", ANI=4, RTX=2, OWNERSHIP=YES; /*Configuring the network bandwidth over the Iub interface in IP transmission mode*/ //Configuring the type of the primary and secondary paths required by various services ADD TRMMAP: TMI=16, ITFT=IUB, TRANST=IP, SRBPRIPATH=AF11, SRBSECPATH=AF12; //Adding an activation factor table ADD TRMFACTOR: FTI=21, REMARK="Iub"; //Adding the TRM mapping to an adjacent node ADD ADJMAP: ANI=0, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=16, TMISLV=16, TMIBRZ=16, FTI=21; //Adding IP paths ADD IPPATH: ANI=0, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF11, IPADDR="1.1.1.2", PEERIPADDR="1.1.1.1", PEERMASK="255.255.255.255", TXBW=45000, RXBW=30000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED; ADD IPPATH: ANI=0, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF12, IPADDR="1.1.1.2", PEERIPADDR="1.1.1.1", PEERMASK="255.255.255.255", TXBW=45001, RXBW=30001, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED; //(Optional) Setting the mapping from the PHB to the DSCP SET PHBMAP: SRN=0, SN=14, PHB=AF11, DSCP=40; SET PHBMAP: SRN=0, SN=14, PHB=AF12, DSCP=41; /*Configuring the E-DPCCH Boosting function*/ //Turning on the E-DPCCH Boosting algorithm switch SET UCORRMALGOSWITCH: CfgSwitch= CFG_EDPCCH_BOOSTING_SWITCH-1; //(Optional) Setting streaming services to ensure that they are carried over HSUPA SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSUPA_SWITCH-1; //Setting the rate threshold for BE services and streaming services carried over HSUPA SET UFRCCHLTYPEPARA: UlStrThsOnHsupa=D64, UlBeTraffThsOnHsupa=D64;
Issue 02 (2011-07-11)
126-5
//Configuring the HSUPA function for a cell ADD UCELLHSUPA: CellId=1, EagchCodeNum=1, ErgchEhichCodeNum=1, MaxTargetUlLoadFactor=75, NonServToTotalEdchPwrRatio=0; //Activating the HSUPA function for a cell ACT UCELLHSUPA: CellId=1; //Enabling the E-DPCCH Boosting function for a cell MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch= EDPCCH_BOOSTING-1; //Turning on the E-DPCCH Boosting retry algorithm switch SET UFRC: RetryCapability=EDPCCH_BOOSTING-1; //Enabling the E-DPCCH Boosting function in a cell on the NodeB side MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, Boosting=TRUE; /*Deactivating E-DPCCH Boosting */ //Disabling the E-DPCCH Boosting function in all cells on the RNC side SET UCORRMALGOSWITCH: CfgSwitch= CFG_EDPCCH_BOOSTING_SWITCH-0; //Disabling the E-DPCCH Boosting function in a cell on the BSC6900 side MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch= EDPCCH_BOOSTING-0; //Disabling the E-DPCCH Boosting function in a cell on the NodeB side MOD LOCELL: LOCELL=1, SECT=REMOTE_SECTOR, BOOST=FALSE;
126-6
Issue 02 (2011-07-11)
127 Configuring HSPA+ Uplink 11.5Mbps per User
127
Prerequisite
l
Configuring HSPA+ Uplink 11.5Mbps per User
This section describes how to activate, verify, and deactivate the optional feature WRFD-010698 HSPA+ Uplink 11.5Mbps per User.
Dependencies on Hardware The BTS3812E/BTS3812AE needs to be configured with the EULPd board. The DBS3800 needs to be configured with the EBBCd board. 3900 series base stations need to be configured with the WBBPd board.
Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010694 UL 16QAM, WRFD-010614 HSUPA Phase 2, and WRFD-010697 EDPCCH Boosting.
l l
License The license controlling this feature has been activated. Others The UE supports the feature WRFD-010697 E-DPCCH Boosting, and the UE belongs to class 7, 8, or 9 in terms of HSUPA capability classification. The CN supports this feature, and the UE uplink registration rate reaches 11.5 Mbps or higher.
Context
With the original HSUPA peak rate of 5.74 Mbps, the UE increases its uplink peak rate to 11.5 Mbps by using the technologies introduced in 3GPP Release 7, including 16QAM and E-DPCCH Boosting.
Procedure
l Activation Procedure 1. To enable the SRB to carry over HSUPA, run the BSC6900 MML command SET UFRCCHLTYPEPARA with Type of Channel Preferably Carrying Signaling
Issue 02 (2011-07-11)
RB set to HSUPA(Uplink is preferably carried on E-DCH, and downlink is preferably carried on DCH). 2. To enable the 2 ms TTI switch, run the BSC6900 MML command SET UCORRMALGOSWITCH with Service Mapping Strategy Switch set to MAP_HSUPA_TTI_2MS_SWITCH. To enable the switch for RNC-level UL 16QAM, run the BSC6900 MML command SET UCORRMALGOSWITCH with Channel Configuration Strategy Switch set to CFG_HSUPA_16QAM_SWITCH. To enable the algorithm switch for RNC-level E-DPCCH Boosting, run the BSC6900 MML command SET UCORRMALGOSWITCH with Channel Configuration Strategy Switch set to CFG_EDPCCH_BOOSTING_SWITCH. To enable the switch for cell-level UL 16QAM, run the BSC6900 MML command MOD UCELLALGOSWITCH with Cell Hspa Plus function switch set to UL_16QAM . To enable the switch for cell-level UL Layer 2 Improvement, run the BSC6900 MML command MOD UCELLALGOSWITCH with Cell Hspa Plus function switch set to UL_L2ENHANCED. To enable cell-level Boosting, run the BSC6900 MML command MOD UCELLALGOSWITCH with Cell Hspa Plus function switch set to EDPCCH_BOOSTING. Run the NodeB MML command MOD LOCELL with UL_16QAM set to TRUE, UL_L2ENHANCED to TRUE, and EDPCCH_BOOSTING to TRUE. Enable a UE of 3GPP Release 7 or later versions and supporting UL 16QAM to access the network and to establish PS services on the E-DCH and HS-DSCH. Create a task under UL Throughput and Bandwidth on the BSC6900 LMT. Upload by FTP is normal. Ideally, the uplink throughput of the UE in MAC layer can reach 11.5 Mbps. To disable the switch for RNC-level UL 16QAM, run the BSC6900 MML command SET UCORRMALGOSWITCH with Channel Configuration Strategy Switch deselect to CFG_HSUPA_16QAM_SWITCH . To disable the switch for cell-level UL 16QAM, run the BSC6900 MML command MOD UCELLALGOSWITCH with Cell Hspa Plus function switch deselect to UL_16QAM .
3.
4.
5.
6.
7.
8. l
2.
----End
Example
/* Activating the HSPA+ Uplink 11.5Mbps per User feature*/ //Enabling the SRB to carry over HSUPA SET UFRCCHLTYPEPARA: SrbChlType=HSUPA; //Enabling the 2ms TTI switch SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; //Enabling the switch for RNC-level UL 16QAM SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSUPA_16QAM_SWITCH-1;
127-2
Issue 02 (2011-07-11)
//Enabling the algorithm switch for RNC-level Boosting SET UCORRMALGOSWITCH: CfgSwitch= CFG_EDPCCH_BOOSTING_SWITCH-1; //Enabling the switch for cell-level UL 16QAM MOD UCELLALGOSWITCH: CellId=1,HspaPlusSwitch=UL_16QAM-1; //Enabling the switch for cell-level UL Layer 2 Improvement MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_L2ENHANCED-1; //Enabling the algorithm switch for cell-level Boosting MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch= EDPCCH_BOOSTING-1; //Setting the UL Layer 2 Improvement, UL 16QAM, and Boosting functions MOD LOCELL: CellId=1, SECT=LOCAL_SECTOR, UL_L2+=TRUE, UL_16QAM=TRUE, Boosting=TRUE; /* Deactivating the HSPA+ Uplink 11.5Mbps per User feature*/ //Disabling the switch for RNC-level UL 16QAM SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSUPA_16QAM_SWITCH-0; //Disabling the switch for cell-level UL 16QAM MOD UCELLALGOSWITCH: CellId=1,HspaPlusSwitch=UL_16QAM-0;
Issue 02 (2011-07-11)
127-3
128 Configuring UL Layer 2 Improvement
128
Prerequisite
Configuring UL Layer 2 Improvement
This section describes how to activate, verify, and deactivate the optional feature WRFD-010695 UL Layer 2 Improvement.
In the case of the BTS3900, BTS3900A, or DBS3900, the WCDMA Baseband Process Unit REV:b (WBBPb) board (including WBBPb1, WBBPb2, WBBPb3, and WBBPb4) or the WCDMA Baseband Process Unit REV:d (WBBPd) board (including WBBPd1 or WBBPd2) is configured. In the case of the DBS3800, the Base Band Processing Unit 3806 (BBU3806) and Enhanced Base Band Card (EBBC), or the BBU3806 and Enhanced Base Band Card REV:d (EBBCd) are configured. In the case of the BTS3812E or BTS3812AE, the NodeB Enhanced HSDPA Supported Baseband Processing and Interface Unit (EBBI), NodeB Enhanced Downlink Processing Unit (EDLP), NodeB Enhanced Uplink Processing Unit (EULP), or NodeB Enhanced Uplink Processing Unit REV:d (EULPd) board is configured. l Dependencies on Other Features The WRFD-010612 HSUPA Introduction Package feature has been configured before this feature is activated. l l License The license controlling this feature has been activated. Other Prerequisites The BSC6900 version is RAN12.0 or later. The NodeB version is RAN12.0 or later. The UE supports UL Layer 2 Improvement.
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.
When the UE is located at the cell edge, data is transmitted in a small PDU size, reducing the bit error rate (BER) caused by power limitation and improving the data transmission efficiency. When the UE is located in the cell center, data is transmitted in a large PDU size, meeting the high-speed data transmission requirement and increasing the data transmission efficiency. As a result, the effective throughput of the entire system is increased.
Procedure
l Activation Procedure 1. Optional: Run the BSC6900 MML command SET UFRC to set parameters related to UL Layer 2 Improvement at the BSC6900 level. In this step, set Cell_DCH UL L2 enhance max RLC PDU size and Cell_DCH UL L2 enhance min RLC PDU size to appropriate values.
NOTE
Generally, use the default values of Cell_DCH UL L2 enhance max RLC PDU size and Cell_DCH UL L2 enhance min RLC PDU size of the BSC6900.
2.
Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable UL Layer 2 Improvement at the cell level. In this step, select the DL_L2ENHANCED (Cell DL L2ENHANCED Function Switch) check box under the parameter Cell Hspa Plus function switch. NodeB V100R013: Run the NodeB MML command MOD LOCELL to enable UL Layer 2 Improvement at the cell level. In this step, set UL_L2+ to TRUE. NodeB V200R013: Run the NodeB MML command MOD LOCELL to enable UL Layer 2 Improvement at the cell level. In this step, set UL L2 Enhanced to TRUE. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 128-1. Figure 128-1 Uu Interface Trace dialog box
3. 4. l
128-2
Issue 02 (2011-07-11)
2.
Use an UE to establish an HSUPA service.

NOTE
The type of services that use this feature is limited by the HSUPA rate threshold.
3.
In the Uu interface tracing data, check the value of the information element (IE) rlcPDU-Size in the RRC_RB_SETUP message. If the value of the IE rlc-PDU-Size is flexibleSize, as shown in Figure 128-2, this feature has been activated. If the value of the IE rlc-PDU-Size is fixedSize, this feature is not activated. Figure 128-2 Value of the IE rlc-PDU-Size
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable UL Layer 2 Improvement at the cell level. In this step, deselect the DL_L2ENHANCED (Cell DL L2ENHANCED Function Switch) check box under the parameter Cell Hspa Plus function switch. NodeB V100R013: Run the NodeB MML command MOD LOCELL to disable UL Layer 2 Improvement at the cell level. In this step, set UL_L2+ to FALSE. NodeB V200R013: Run the NodeB MML command MOD LOCELL to disable UL Layer 2 Improvement at the cell level. In this step, set UL L2 Enhanced to FALSE.
2. 3.
----End
Example
//Activation procedure //Turning on the cell-level switch for UL Layer 2 Improvement on the BSC6900 side MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=UL_L2ENHANCED-1; //Enabling UL Layer 2 Improvement at the cell level on the NodeB side //NodeB V100R013 MOD LOCELL: CellId=1, UL_L2+=TRUE; //NodeB V200R013 MOD LOCELL: CellId=1, UL_L2PLUS=TRUE; //Deactivation procedure //Turning off the cell-level switch for UL Layer 2 Improvement on the
Issue 02 (2011-07-11)
128-3
BSC6900 side MOD UCELLALGOSWITCH: HspaPlusSwitch=UL_L2ENHANCED-0; //Disabling UL Layer 2 Improvement at the cell level on the NodeB side// NodeB V100R013 MOD LOCELL: CellId=1, UL_L2+=FALSE; //NodeB V200R013 MOD LOCELL: CellId=1, UL_L2PLUS=FALSE;
128-4
Issue 02 (2011-07-11)
129
Prerequisite
Configuring DC-HSDPA
This section describes how to activate, verify, and deactivate the optional feature WRFD-010696 DC-HSDPA.
For 3900 series base station, BBU3900 needs to be configured with the WBBPb 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 resources of DC-HSDPA cells cannot be carried on the HBBI or HULP board. They can be carried on the EBBI or EULP board. For the BSC6900, DPUe boards are recommended because the downlink 42 Mbit/s throughput of DC-HSDPA users may be affected if the BSC6900 is configured with DPUb boards. l Dependencies on Other Features WRFD-010610 HSDPA Introduction Package WRFD-010629 DL 16QAM Modulation WRFD-010685 Downlink Enhanced L2 l l License The license controlling this feature has been activated. Other Prerequisites 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. For distributed cells, two local cells of the same DC group should be served by the same RRU or by two cascaded RRUs respectively. The BSC6900 software version is RAN12.0 or later. The NodeB software version is RAN12.0 or later. The UEs must belong in categories 21 or later, as specified by the 3GPP specifications.
Context
CAUTION
Activate this feature when the traffic volume in a cell is low. The reason is that the cell must be deactivated before this feature is activated; after the cell is deactivated, the services in this cell are disrupted. Dual Cell-HSDPA (DC-HSDPA) allows an UE to establish downlink connections simultaneously to two inter-frequency co-coverage cells that are configured with consecutive frequencies and controlled by one NodeB. The two cells can schedule the UE simultaneously, therefore increasing the downlink peak throughput of the UE. The gain of downlink throughput is higher when the UE is located at the cell edge.
NOTE
l The CS service, IMS signaling, SRB signaling, or PS conversational service is carried on a single carrier instead of DC-HSDPA because the amount of data is small and the gain is insignificant when DCHSDPA is used. l The BE or streaming service can be carried over the DC-HSDPA. The BE/streaming combined service is carried over the DC-HSDPA preferentially.
Data Configuration Plan Parameters ID of local cell 1 ID of local cell 2 Cell ID DL streaming traffic threshold on HSDPA DL BE traffic threshold on HSDPA Example 1 2 1 and 2 D64 D64 Source Network planning Network planning Network planning Network planning Network planning
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of local cell 1. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of 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.
4.
129-2

NOTE
If the switch parameter is set to DC_HSDPA, the network preferentially configures DC_HSDPA for the UE. Set this parameter to DC_HSDPA before the verification. After the verification is complete, set this parameter according to actual network planning.
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. The parameter DL streaming traffic threshold on HSDPA is rate threshold for the decision to set up a PS domain background/interactive service on the DCH in the uplink. The parameter DL BE traffic DCH decision threshold rate threshold for the decision to set up a PS domain background/interactive service on the DCH in the downlink.
6.
7.
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. Set Code Adjust Switch for HSDPA to ON. Set User Number for Code Adjust for HSDPA.
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 or equal to 19 to a value that is smaller than or equal to 25.
10. Optional: Run the BSC6900 MML command MOD UCELLFREQUENCY to modify one of the two UARFCNDownnlink parameters. 11. 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. 12. Optional: Run the BSC6900 MML command MOD UCELLSETUP to change the time offset of a cell. 13. Run the NodeB MML command ADD DUALCELLGRP to add 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. 14. Run the BSC6900 MML command ACT UCELL to activate the logical cell of local cell 1. 15. Run the BSC6900 MML command ACT UCELL to activate the logical cell of local cell 2. l Verification Procedure 1. Click Uu Interface Trace on the LMT, as shown in Figure 129-1.
Issue 02 (2011-07-11)
129-3
Figure 129-1 Uu Interface Trace dialogue box
2. 3. 4.
For cells with Cell DC-HSDPA Function Switch turned on, trace RRC_RB_SETUP messages on the Uu interface. Perform dialing tests on FTP services for a UE to ensure that data is transmitted on HSDPA channels. On the Trace tab page of the LMT, check whether RRC_RB_SETUP messages contain the dl-SecondaryCellInfoFDD information element. If the dl-SecondaryCellInfoFDD information element is contained, as shown in Figure 129-2, it indicates that the feature is activated. If the dl-SecondaryCellInfoFDD information element is not contained, it indicates that the feature is not activated. Figure 129-2 RRC_RB_SETUP message
129-4
Issue 02 (2011-07-11)
1.
Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect CFG_HSDPA_DC_SWITCH from the Channel Configuration Strategy Switch list. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of the local cell 1. Run the NodeB MML command RMV DUALCELLGRP to remove the DC-HSDPA cell group.
NOTE
2. 3.
To remove a DC-HSDPA cell group, you only need to remove one local cell in the group.
4. ----End
Run the BSC6900 MML command ACT UCELL to activate the logical cell of the local cell 1.
Example
//Activation procedure //To deactivate cells, run the following command repeatedly: DEA UCELL: CellId=1; DEA UCELL: CellId=2; //Setting channel configuration strategy switch SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DC_SWITCH-1; //Setting preferred MIMO_64QAM or DC_HSDPA character SET UFRC: MIMO64QAMorDcHSDPASwitch= DC_HSDPA; //Setting service mapping strategy switch SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; //Setting DL streaming traffic threshold on HSDPA SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; //Setting Cell Hspa Plus function switch MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED-1&DC_HSDPA-1 //Setting allocate code mode MOD UCELLHSDPA: CellId=1, AllocCodeMode=Automatic, CodeAdjForHsdpaSwitch=ON, CodeAdjForHsdpaUserNumThd=3; //Querying the UARFCN of the cell LST UCELL: LstType=ByCellId, CellId=1; ////Querying the parameter Time Offset (TCELL) of the cell LST UCELL: LstType=ByCellId, CellId=1; //Modifying the time offset of the cell MOD UCELLSETUP: CellId=1, TCell=CHIP512; //Configuring local cell 1 and local cell 2 as a DC-HSDPA cell group ADD DUALCELLGRP: FIRSTLOCELL=1, SECONDLOCELL=2; //Activating the cells ACT UCELL: CellId=1; ACT UCELL: CellId=2; //Deactivation procedure //To set Channel Configuration Strategy Switch, run the following command: MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DC_HSDPA-0; //To deactivate cell, run the following command: DEA UCELL: CellId=1; //To remove the DC-HSDPA cell group, run the following command: RMV DUALCELLGRP: LOCELL=1; //To activate cell, run the following command: ACT UCELL: CellId=1;
Issue 02 (2011-07-11)
129-5
130 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier
Activation and Deactivation of the Supplementary Carrier In Multi-carrier

This section describes how to activate, verify, and deactivate the optional feature WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier.
130
Configuring Traffic-Based
Prerequisite
l l l l Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features WRFD-010696 DC-HSDPA License The license controlling this feature has been activated. Other Prerequisites The UE must be of HS-DSCH category 21, 22, 23, 24 to support DC-HSDPA or HSDSCH category 25, 26, 27, 28 to support DC-HSDPA+MIMO.
Context
For a user that uses DC-HSDPA/DC-HSDPA+MIMO in the downlink and DCH/SC-HSUPA in the uplink, the feature has the following functions: l Disables the downlink secondary carrier function when the downlink traffic is light but the buffer has been occupied by a large amount of data. In this case, the user becomes a singlecarrier user. Re-activate the downlink secondary carrier function when the buffer can accommodate a large amount of data and throughput is high. In this case, the user becomes a dual-carrier user.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET MACHSPARA to set the Mac-hs scheduling parameters with the DC HSDPA Cell Act Deact Switch set to ON(ON).
Issue 02 (2011-07-11)
130 Configuring Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier
NOTE
If the Mac-hs scheduling parameters of two DC-HSDPA cells must be set, set DC HSDPA Cell Act Deact Switch to ON(ON) for each cell.
Verification Procedure 1. Run the NodeB MML command LST MACHSPARA to query the Mac-hs scheduling parameters. Check whether the Secondary DC HSDPA Cell Act Deact Switch is turned on. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, clear DRA_HSDPA_STATE_TRANS_SWITCH, DRA_HSUPA_STATE_TRANS_SWITCH, and DRA_PS_BE_STATE_TRANS_SWITCH from the Dynamic Resource Allocation Switch list. Use a DC-HSDPA UE to perform PS services in a DC-HSDPA cell. Do not upload or download data after required connections are established. Five seconds later, the UE becomes an SC UE, which indicates that the feature has been activated. Run the NodeB MML command SET MACHSPARA to set the Mac-hs scheduling parameters with the Secondary DC HSDPA Cell Act Deact Switch set to OFF (OFF).
2.
3.
----End
Example
//Activation procedure SET MACHSPARA: LOCELL=1, SECCELLACTDEASW=ON; SET MACHSPARA: LOCELL=2, SECCELLACTDEASW=ON; //Verification procedure LST MACHSPARA: LOCELL=1; LST MACHSPARA: LOCELL=2; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0&D RA_PS_BE_STATE_TRANS_SWITCH-0; //Deactivation procedure SET MACHSPARA: LOCELL=1, SECCELLACTDEASW=OFF; SET MACHSPARA: LOCELL=2, SECCELLACTDEASW=OFF;
130-2
Issue 02 (2011-07-11)
131 Configuring DC-HSDPA+MIMO (trial)
131
Prerequisite
l
Configuring DC-HSDPA+MIMO (trial)
This section describes how to activate, verify, and deactivate the optional feature WRFD-010699 DC-HSDPA+MIMO (trial).
Dependencies on Hardware The HBBI and HDLP boards in the BTS3812E/BTS3812AE do not support the DCHSDPA+MIMO feature. To support this feature, the BTS3812E/BTS3812AE must be configured with the EBBI and EDLP boards. To support DC-HSDPA+MIMO, the DBS3800 must be configured with the EBBC or EBBCd boards. In addition, the maximum capability of the DBS3800 is DC+MIMOx1. That is, only one frequency in a dual cell (DC) group can be configured with MIMO. 3900 series base stations must be configured with the WBBPb or WBBPd boards.
Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010696 DC-HSDPA and WRFD-010684 22 MIMO.
l l
License The license controlling this feature has been activated. Others This feature is dependent on the UE capability (class 25, 26, 27, and 28 on the HSDSCH).
Context
Introduced in the R9 protocol, the DC-HSDPA+MIMO feature combines the DS-HSDPA feature in the R8 protocol and the MIMO feature in the R7 protocol. This feature allows two inter-frequency co-coverage neighboring carriers under a NodeB that use the same frequency band to simultaneously transmit HSDPA data to a UE.
Procedure
l
Issue 02 (2011-07-11)
1.
To enable the algorithm switch for RNC-level DC-HSDPA+MIMO, run theBSC6900 MML command SET UCORRMALGOSWITCH with Channel Configuration Strategy Switch set to CFG_HSDPA_DCMIMO_SWITCH and CFG_HSDPA_MIMO_SWITCH. Optional: If HSDPA is required for streaming services, you need to enable the algorithm switch for streaming services carried over HSDPA: Run theBSC6900 MML command SET UCORRMALGOSWITC with Service Mapping Strategy Switch set to MAP_PS_STREAM_ON_HSDPA_SWITCH. To set the HSDPA threshold for downlink streaming services and for downlink BE services, run the BSC6900 MML command SET UFRCCHLTYPEPARA with DL streaming traffic threshold on HSDPA and DL BE traffic threshold on HSDPA set to appropriate values according to the network plan. To enable the switch for cell-level DC-HSDPA+MIMO and the algorithm switch for DL Layer2 Improvement, run the BSC6900 MML command MOD UCELLALGOSWITCH with Cell Hspa Plus function switch set to DL_L2ENHANCED and DCMIMO_HSDPA. To add the HSDPA parameters for a cell, run the BSC6900 MML command ADD UCELLHSDPA with related parameters set to appropriate values according to the network plan. To activate the HSDPA function for a cell, run the BSC6900MML command ACT UCELLHSDPA. Optional: When the DC-HSDPA+MIMO feature is used, you need to activate the license controlling the downlink peak rate of 84 Mbit/s if the downlink throughput per user is expected to reach 84 Mbit/s. Run the BSC6900 MML command SET LICENSE with Function Switch5 set to HSPA_DL84M_PER_USER. To check the number of online DC-HSDPA+MIMO users, query the counter VS.HSDPA.UE.Mean.CAT25.28 to obtain the average number of HSDPA users of CAT25 to CAT28 in a cell, and query the counter VS.HSDPA.UE.Max.CAT25.28 to obtain the maximum number of HSDPA users of CAT25 to CAT28 in a cell. To check DC-HSDPA+MIMO service setup, query the counter VS.HSDPA.RAB.DCMIMO.AttEstab to obtain the number of DC-HSDPA-MIMO RAB setup attempts on the primary carrier in a DC group, and query the counter VS.HSDPA.RAB.DCMIMO.SuccEstab to obtain the number of successful DCHSDPA-MIMO RAB setups on the primary carrier in a DC group. To check DC-HSDPA+MIMO call drops, query the counter VS.HSDPA.RAB.DCMIMO.NormRel to obtain the number of DC-HSDPA-MIMO RABs normally released on the primary carrier in a DC group, and query the counter VS.HSDPA.RAB.DCMIMO.AbnormRel to obtain the number of DC-HSDPAMIMO RABs abnormally released on the primary carrier in a DC group (including RF Failure). Enable UE tracing and establish HSPA BE services. Then, check whether the values of HS-DSCH FDD Secondary Serving Information and MIMO Activation Indicator are contained in the RADIO LINK RECONFIGURATION READY message over the Iub interface and whether the values of Downlink secondary cell info FDD and Secondary cell MIMO parameters are contained in the RADIO BEARER SETUP message over the Uu interface.
2.
3.
4.
5.
6. 7.
2.
3.
4.
l
131-2
1.
To disable the algorithm switch for RNC-level DC-HSDPA+MIMO, run the BSC6900MML command SET UCORRMALGOSWITCH with Channel Configuration Strategy Switch not set to CFG_HSDPA_DCMIMO_SWITCH. To disable the switch for cell-level DC-HSDPA+MIMO, run the BSC6900 MML command MOD UCELLALGOSWITCH with Cell Hspa Plus function switch not set to DCMIMO_HSDPA.
2.
----End
Example
/*Activating DC-HSDPA+MIMO*/ //Enabling the algorithm switch for RNC-level DC-HSDPA+MIMO SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DCMIMO_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1; //(Optional) Enabling the algorithm switch for streaming services over HSDPA If HSDPA is required for streaming services SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; //Setting HSDPA thresholds for downlink streaming services and for downlink BE services SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; //Enabling the switch for cell-level DC-HSDPA+MIMO and the algorithm switch for DL Layer2 Improvement MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=64QAM-1&MIMO-1&DL_L2ENHANCED-1&64QAM_MIMO-1&DC_HSDPA-1&DCM IMO_HADPA-1 //Adding the HSDPA parameters for a cell ADD UCELLHSDPA: CellId=1, AllocCodeMode=Automatic, CodeAdjForHsdpaSwitch=ON; //Activating the HSDPA function for a cell ACT UCELLHSDPA: CellId=1; //Activating the downlink peak rate of 84 Mbit/s SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH5=HSPA_DL84M_PER_USER-1; /*Deactivating DC-HSDPA+MIMO*/ //Disabling the algorithm switch for RNC-level DC-HSDPA+MIMO SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DCMIMO_SWITCH-0; //Disable the switch for cell-level DC-HSDPA+MIMO MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DCMIMO_HSDPA-0;
Issue 02 (2011-07-11)
131-3
132 Configuring Queuing and Preemption
132
Prerequisite
l
Configuring Queuing and Preemption
This section describes how to activate, verify, and deactivate the optional feature WRFD-010505 Queuing and Preemption.
Dependencies on Hardware This feature requires the CN to bring the information element allocation/retention priority (ARP) to BSC6900 during RAB assignment so that BSC6900 can obtain service priorities with RAB parameters.
Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.
Context
This feature supports queuing and preemption to implement service differentiation in congested networks, providing better service for high-priority users.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UQUEUEPREEMPT to turn on the queuing and preemption switches. In this step, set Preempt algorithm switch to ON and set Queue algorithm switch to ON. Run the BSC6900 MML command LST UQUEUEPREEMPT to check whether the queuing and preemption switches are turned on.
l
Issue 02 (2011-07-11)
132 Configuring Queuing and Preemption
1.
Run the BSC6900 MML command SET UQUEUEPREEMPT to turn off the queuing and preemption switches. In this step, set Preempt algorithm switch to OFF and set Queue algorithm switch to OFF.
----End
Example
//Activating Queuing and Preemption SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, QueueAlgoSwitch=ON; //Deactivating Queuing and Preemption SET UQUEUEPREEMPT: PreemptAlgoSwitch=OFF, QueueAlgoSwitch=OFF;
132-2
Issue 02 (2011-07-11)
133 Configuring Access Class Restriction
133
Prerequisite
l l l
Configuring Access Class Restriction
This section describes how to activate, verify, and deactivate the optional feature WRFD-021103 Access Class Restriction.
Dependencies on Hardware BSC6900 supports NACC RAN Information Management (RIM) and PS handover. The UE supports NACC and PS handover. The CN SGSN supports NACC and PS handover. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
When the cell or system is overloaded, this feature can restrict user access based on the allowed service class by broadcasting system information, controlling potential load requirements of the system.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UACALGO. In this step, set AC Restriction Switch to ON and other parameters to appropriate values.
Verification Procedure Verifying Access Class Restriction based on CPU overload 1. 2. 3. Start Uu Interface Trace on the BSC6900 LMT. Run the BSC6900 MML command LST FCCPUTHD to query the settings of AC control threshold and AC restore threshold. Run the BSC6900 MML command SET FCCPUTHD. In this step, set AC control threshold and AC restore threshold to appropriate values.
Issue 02 (2011-07-11)
4. 5.
Enable a large number of UEs to access a cell until the CPU usage exceeds the AC restore threshold. Start Uu Interface Trace on the BSC6900 LMT and select RRC_SYS_INFO_TYPE3 as the message type. If the value of barred IE in the RRC_SYS_INFO_TYPE3 message is 0, as shown in Figure 133-1, the feature has been activated. If the value is not 0, the feature is not activated.
Figure 133-1 RRC_SYS_INFO_TYPE3 message
6. 7.
Reduce the number of UEs in the cell until the CPU usage is lower than the AC restore threshold. Run the BSC6900 MML command SET FCCPUTHD. In this step, set AC control threshold and AC restore threshold to their original values. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set Process switch to SYS_INFO_UPDATE_FOR_IU_RST and BARRED_CELL_FOR_CSDOMAIN_RST. Run the BSC6900 MML command RST UIU. In this step, set CN Domain ID to CS_DOMAIN. Start Uu Interface Trace on the BSC6900 LMT and select RRC_SYS_INFO_TYPE3 as the message to be traced. If the traced RRC_SYS_INFO_TYPE3 message indicates that the cell is barred, as shown in Figure 133-2, the feature has been activated. If the traced message does not indicate that the cell is barred, the feature is not activated.
Verifying Access Class Restriction based on the access failure on the Iu interface 1.
2. 3.
133-2
Figure 133-2 RRC_SYS_INFO_TYPE3 message
Deactivation Procedure 1. Run the BSC6900 MML command SET UACALGO. In this step, set AC Restriction Switch to OFF.
----End
Example
//Activating Access Class Restriction SET UACALGO: AcRstrctSwitch=ON, AcRstrctPercent=5, AcIntervalOfCell=1, AcRstrctIntervalLen=6; //Verifying Access Class Restriction based on CPU overload SET FCCPUTHD: BRDCLASS=XPU, ACCTHD=40, ACRTHD=35; 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; //Verifying Access Class Restriction based on the access failure on the Iu interface SET URRCTRLSWITCH: PROCESSSWITCH=SYS_INFO_UPDATE_FOR_IU_RST-1&BARRED_CELL_FOR_CSDOMAIN_RST-1 ; RST UIU: CnOpIndex=0, CNDOMAINID=CS_DOMAIN, RSTCNTYPE=ALL_NODES; //Deactivating Access Class Restriction SET UACALGO: AcRstrctSwitch=OFF;
Issue 02 (2011-07-11)
133-3
134 Configuring Traffic Priority Mapping onto Transmission Resources
134
Prerequisite
l l l
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.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
This feature enables the dynamical mapping of the services onto the transport bearers according to the TC, ARP, and THP of the user. Operators can flexibly configure the mapping to provide differentiated services while guaranteeing the QoS.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD TRMMAP to add the transport resource mapping.
NOTE
l Before setting the type of a mapping path for a service, ensure that this type of path is available. Otherwise, the service may fail to be set up. l The primary path and the secondary path for the same service type must be different. l The default 14 transport resource mappings (indexed from 0 to 13) are added when the system is initialized, and you cannot modify them.
2.
Run the BSC6900 MML command ADD ADJMAP to add the TRM mapping to the adjacent node.
Issue 02 (2011-07-11)
134 Configuring Traffic Priority Mapping onto Transmission Resources

NOTE
Before running this command, ensure that the adjacent node or the NodeB is added by running the BSC6900 MML command ADD ADJNODE or ADD UNODEB.
Verification Procedure This feature can be verified only by running the LST commands. 1. 2. Run the BSC6900 MML command LST TRMMAP to check whether the transport resource mapping is correct. If the mapping is incorrect, run the BSC6900 MML command MOD TRMMAP to modify the mapping.
NOTE
Do not modify Interface Type and Transport Type in the MOD TRMMAP command.
Deactivation Procedure 1. 2. Run the BSC6900 MML command RMV ADJMAP to remove the TRM mapping to the adjacent node. Run the BSC6900 MML command RMV TRMMAP to remove the transport resource mapping.
----End
Example
//Activating Traffic Priority Mapping onto Transmission Resources ADD TRMMAP: TMI=15, REMARK="15", ITFT=IUB, TRANST=IP, VOICEPRIPATH=AF11; ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=15, TMISLV=15, TMIBRZ=15, FTI=13; //Verifying Traffic Priority Mapping onto Transmission Resources LST TRMMAP: TMI=15; MOD TRMMAP: TMI=15, ITFT=IUB, TRANST=IP, CCHSECPATH=RT_VBR; //Deactivating Traffic Priority Mapping onto Transmission Resources RMV ADJMAP: ANI=10,ITFT=IUB,CNMNGMODE=SHARE; RMV TRMMAP: TMI=15;
134-2
Issue 02 (2011-07-11)
135 Configuring Differentiated Service Based on SPI Weight
135
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-01061103 Scheduling based on EPF and GBR has been configured before this feature is applied in the downlink over the Uu interface. WRFD-01061402 Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE Resource Management has been configured before this feature is applied in the uplink over the Uu interface. When this feature is enabled together with the optional feature WRFD-01061402 Enhanced Fast UL Scheduling, only uplink Uu interface resources can be differentially scheduled. When this feature is enabled together with the optional feature RFD-010638 Dynamic CE Resource Management, both uplink Uu interface resources and CE resources can be differentially scheduled. WRFD-010610 HSDPA Introduction Package and WRFD-050405 Overbooking on ATM Transmission, or WRFD-010610 HSDPA Introduction Package and WRFD-050408 Overbooking on IP Transmission have been configured before this feature is applied in the downlink over the Iub interface. WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion has been configured before this feature is applied in the uplink over the Iub interface.
Context
When Uu interface resources, CE resources, and Iub transmission resources do not meet the GBR requirements of all online users, this feature enables the RAN to preferentially guarantee the GBR of high-priority users. The RAN can thereby provide differentiated services under a certain level of fairness.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command SET UUSERPRIORITY to configure gold, silver, and copper users. Run the BSC6900 MML command SET UTHPCLASS to set priorities of PS interactive services to appropriate values. Run the BSC6900 MML command SET USCHEDULEPRIOMAP to set the scheduling priority mapping information. Run the BSC6900 MML command SET UCAPARATERANGE to set RNC-specific reference rates and rate thresholds of all levels in the uplink and downlink. Optional: Run the BSC6900 MML command ADD UOPERCAPARATERANGE to set operator-specific reference rates and rate thresholds of all levels in the uplink and downlink. Run the BSC6900 MML command SET USPIWEIGHT to set RNC-specific scheduling priority weight. Optional: Run the BSC6900 MML command ADD UOPERSPIWEIGHT to set operator-specific scheduling priority weight. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set Process switch to NODEB_PRIVATE_INTERFACE_SWITCH. Establish services on UE A and UE B. Assume that the SPI and SPI weight of UE A are 7 and 50 respectively and the SPI and SPI weight of UE B are 7 and 100 respectively. In the traced Iub interface messages, check the information element (IE) schedulingPriorityIndicator in the NBAP_RL_RECFG_PREP message to obtain the SPI value; check the IE schedule-Prior-Indication-Weight-Private to obtain the SPI weight, which is the actual SPI value for the NodeB, as shown in Figure 135-1, Figure 135-2, Figure 135-3, and Figure 135-4.
6. 7. 8. l
135-2
Issue 02 (2011-07-11)
Figure 135-1 SPI and SPI weight of UE A in the uplink
Issue 02 (2011-07-11)
135-3
Figure 135-2 SPI and SPI weight of UE A in the downlink
Figure 135-3 SPI and SPI weight of UE B in the uplink
135-4
Issue 02 (2011-07-11)
Figure 135-4 SPI and SPI weight of UE B in the downlink
2.
Check the real-time throughput of UEs by referring to Monitoring UL Throughput and Bandwidth and Monitoring DL Throughput and Bandwidth. Generally, if the throughput of users with higher SPI weight is higher than that of users with lower SPI weight, this feature has taken effect. The throughput of UE B is approximately twice the throughput of UE A, as shown in the NBAP_RL_RECFG_PREP message. If the throughput of users with higher SPI weight is lower than that of users with lower SPI weight, this feature has not taken effect.
----End
Example
/*Activating Differentiated Service Based on SPI Weight*/ //Configuring gold, silver, and copper users SET UUSERPRIORITY: ARP1Priority=Gold, ARP2Priority=Gold, ARP3Priority=Gold, ARP4Priority=Gold, ARP5Priority=Gold, ARP6Priority=Silver, ARP7Priority=Silver, ARP8Priority=Silver, ARP9Priority=Silver, ARP10Priority=Silver, ARP11Priority=Copper, ARP12Priority=Copper, ARP13Priority=Copper, ARP14Priority=Copper, ARP15Priority=Copper, PriorityReference=ARP, CarrierTypePriorInd=NONE; //Setting the priorities of PS interactive services SET UTHPCLASS: THP1Class=High, THP2Class=High, THP3Class=High,
Issue 02 (2011-07-11)
135-5
THP4Class=High, THP5Class=High, THP6Class=Medium, THP7Class=Medium, THP8Class=Medium, THP9Class=Medium, THP10Class=Medium, THP11Class=Low, THP12Class=Low, THP13Class=Low, THP14Class=Low, THP15Class=Low; //Setting the scheduling priority mapping information SET USCHEDULEPRIOMAP: TrafficClass=INTERACTIVE, UserPriority=GOLD, THPClass=High, SPI=7; //Setting the RNC-specific reference rates and rate thresholds of all levels in the uplink and downlink SET UCAPARATERANGE: DlCapacitySelect=MBR, DlRateThreshold1=128, DlRateThreshold2=256, DlRateThreshold3=512, DlRateThreshold4=1000, DlRateThreshold5=4000, DlRateThreshold6=8000, DlRateThreshold7=10000, DlRateThreshold8=20000, DlRateThreshold9=45000, UlCapacitySelect=MBR, UlRateThreshold1=128, UlRateThreshold2=256, UlRateThreshold3=512, UlRateThreshold4=1000, UlRateThreshold5=4000, UlRateThreshold6=8000, UlRateThreshold7=10000, UlRateThreshold8=20000, UlRateThreshold9=45000; //Setting the operator-specific reference rates and rate thresholds of all levels in the uplink and downlink ADD UOPERCAPARATERANGE: CnOpIndex=0, DlRateThreshold1=128, DlRateThreshold2=384, DlRateThreshold3=512, DlRateThreshold4=1000, DlRateThreshold5=2000, DlRateThreshold6=4000, DlRateThreshold7=8000, DlRateThreshold8=16000, DlRateThreshold9=32000, UlRateThreshold1=128, UlRateThreshold2=384, UlRateThreshold3=512, UlRateThreshold4=768, UlRateThreshold5=1000, UlRateThreshold6=1500, UlRateThreshold7=2500, UlRateThreshold8=5500, UlRateThreshold9=7500; //Setting the RNC-specific scheduling priority weight SET USPIWEIGHT: SPI=7, SpiWeight=100, RateRangeSPIWeightInd=TRUE, DlRateRange1SPIWeight=10, DlRateRange2SPIWeight=20, DlRateRange3SPIWeight=30, DlRateRange4SPIWeight=40, DlRateRange5SPIWeight=50, DlRateRange6SPIWeight=60, DlRateRange7SPIWeight=70, DlRateRange8SPIWeight=80, DlRateRange9SPIWeight=90, DlRateRange10SPIWeight=100, UlRateRange1SPIWeight=10, UlRateRange2SPIWeight=20, UlRateRange3SPIWeight=30, UlRateRange4SPIWeight=40, UlRateRange5SPIWeight=50, UlRateRange6SPIWeight=60, UlRateRange7SPIWeight=70, UlRateRange8SPIWeight=80, UlRateRange9SPIWeight=90, UlRateRange10SPIWeight=100; //Setting the operator-specific scheduling priority weight ADD UOPERSPIWEIGHT: CnOpIndex=0, SPI=7, RateRangeSPIWeightInd=TRUE; //Enabling the switch for a NodeB private interface SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
135-6
Issue 02 (2011-07-11)
136 Configuring Web Browsing Acceleration
136
Prerequisite
l
Configuring Web Browsing Acceleration
This section describes how to activate, verify, and deactivate the optional feature WRFD-020132 Web Browsing Acceleration.
Dependencies on Hardware BTS3812E and BTS3812AE series base stations are configured with EBBI or EDLP boards. HBBI and HDLP boards do not support this feature. DBS3800 series base stations are configured with EBBC or EBBCd boards. The HBBU board does not support this feature. 3900 series base stations are configured with WBBPb or WBBPd boards. The WBBPa board does not support this feature. The Network Intelligence Unit REV:a (NIUa) board is ready. The NIUa board can be housed in the same slot as the DPUb or DPUe board. For details of inserting a NIUa board, see Inserting a Board.
l l
Context
This feature enables the RNC to identify web browsing services by parsing packets and thereby to preferentially allocate higher bandwidth to these services. As a result, web browsing services take shorter time and the user experience is improved.
Procedure
l Activation Procedure 1. 2.
Issue 02 (2011-07-11)
Run the BSC6900 MML command ADD BRD to add a NIUa board. In this step, set the Board Class to NIU, and set the Board Type to NIUa. Set the initial Scheduling Priority Indicator (SPI) weight on the BSC6900 LMT.
136 Configuring Web Browsing Acceleration
If the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is turned on, run the BSC6900 MML command SET USPIWEIGHT to configure weight of each SPI. In this step, set Scheduling Priority Indicator and SPI Weight to appropriate values based on the network plan. If the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is not turned on, run the BSC6900 MML command SET UFRC to set Default SPI Weight to an appropriate value based on the network plan. 3. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select the NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter Process switch. Run the BSC6900 MML command ADD UIPSERVICEQOS to add the priority mapping of HTTP services. Run the BSC6900 MML command SET UDPUCFGDATA to set scheduling priority weight that corresponds to services of each priority to appropriate values. Verify that the value of the counter VS.IuPS.BytesPayldHTTP.Rx is not 0. If it is not 0, this feature has been activated. This feature does not need to be deactivated.
4. 5. l
----End
Example
//Activating Web Browsing Acceleration //ADD a NIUa Board ADD BRD: SRN=0, BRDCLASS=NIU, BRDTYPE=NIUa, SN=8, MPUSUBRACK=0, MPUSLOT=0; //Setting the initial SPI weight value if the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is turned on SET USPIWEIGHT: SPI=4, SPIWEIGHT=10; //Setting the initial SPI weight value if the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is not turned on SET UFRC: DefaultSPIWeight=10; //Turning on the switch for a NodeB private interface SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; //Adding the priority mapping of HTTP services ADD UIPSERVICEQOS: CnOpIndex=0, TrafficType=HTTP, TrafficPriority=HIGH; //Setting scheduling priority weight that corresponds to services of each priority SET UDPUCFGDATA: ServPriAdjCoefHigh=100, ServPriAdjCoefMiddle=10, ServPriAdjCoefLow=1;
136-2
Issue 02 (2011-07-11)
137 Configuring P2P Downloading Rate Control during Busy Hour
137
Prerequisite
l
Configuring P2P Downloading Rate Control during Busy Hour
This section describes how to activate, verify, and deactivate the optional feature WRFD-020133 P2P Downloading Rate Control during Busy Hour.
Dependencies on Hardware BTS3812E and BTS3812AE series base stations are configured with EBBI or EDLP boards. HBBI and HDLP boards do not support this feature. DBS3800 series base stations are configured with EBBC or EBBCd boards. The HBBU board does not support this feature. 3900 series base stations are configured with WBBPb or WBBPd boards. The WBBPa board does not support this feature. The Network Intelligence Unit REV:a (NIUa) board is ready. The NIUa board can be housed in the same slot as the DPUb or DPUe board. For details of inserting a NIUa board, see Inserting a Board.
l l
Context
This feature restricts point to point service (P2P) traffic during busy hours, thereby improving the user experience of other delay-sensitive services and reducing operating costs. During nonbusy hours, P2P downloads are not restricted, thereby improving the user experience of P2P users and full utilizing network resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD BRD to add a NIUa board. In this step, set the Board Class to NIU, and set the Board Type to NIUa.
Issue 02 (2011-07-11)
137 Configuring P2P Downloading Rate Control during Busy Hour
2.
Set the initial Scheduling Priority Indicator (SPI) weight on the BSC6900 LMT. If the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is turned on, run the BSC6900 MML command SET USPIWEIGHT to configure weight of each SPI. In this step, set Scheduling Priority Indicator and SPI Weight to appropriate values based on the network plan. If the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is not turned on, run the BSC6900 MML command SET UFRC to set Default SPI Weight to an appropriate value based on the network plan.
3.
Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select the NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter Process switch. Run the BSC6900 MML command ADD UIPSERVICEQOS to add the priority mapping of P2P services. Run the BSC6900 MML command SET UDPUCFGDATA to set scheduling priority weight that corresponds to services of each priority to appropriate values. Verify that the value of the counter VS.IuPS.BytesPayldP2P.Rx is not 0. If it is not 0, this feature has been activated. This feature does not need to be deactivated.
4. 5. l
----End
Example
//Activating P2P Downloading Rate Control during Busy Hour //ADD a NIUa Board ADD BRD: SRN=0, BRDCLASS=NIU, BRDTYPE=NIUa, SN=8, MPUSUBRACK=0, MPUSLOT=0; //Setting the initial SPI weight value if the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is turned on SET USPIWEIGHT: SPI=4, SPIWEIGHT=10; //Setting the initial SPI weight value if the switch for the license control item of the feature WRFD-020806 Differentiated Service Based on SPI Weight is not turned on SET UFRC: DefaultSPIWeight=10; //Turning on the switch for a NodeB private interface SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1; //Adding the priority mapping of P2P services ADD UIPSERVICEQOS: CnOpIndex=0, TrafficType=P2P, TrafficPriority=LOW; //Setting scheduling priority weight that corresponds to services of each priority SET UDPUCFGDATA: ServPriAdjCoefHigh=100, ServPriAdjCoefMiddle=10, ServPriAdjCoefLow=1;
137-2
Issue 02 (2011-07-11)
138 Configuring Intelligent Inter-Carrier UE Layered Management
138
Prerequisite
l l
Configuring Intelligent Inter-Carrier UE Layered Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-020135 Intelligent Inter-Carrier UE Layered Management.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-020400 DRD Introduction Package must be configured before this feature is activated.
Context
This feature allows the RAN to intelligently distinguish between UEs and data cards in multicarrier scenarios and to separately set up services on different carriers.
Procedure
l Activation Procedure The following methods assume that cell F1 and cell F2 are used. 1. 2. Run the BSC6900 MML command SET UDRD. In this step, set Device Type Steering DRD Switch to ON. Run the BSC6900 MML command ADD UCELLLICENSE twice to enable the layered terminal management function for cell F1 and cell F2 respectively. In this step, set FuncSwitch1 to INTELLIGENT_INTERFREQ_UE_TYPE_STEERING. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Direct Retry Switch to DR_RAB_SING_DRD_SWITCH. Run the BSC6900 MML command ADD UDEVICETYPEIMSI. In this step, set IMSI Segment Choice to MultiIMSI and specify the IMSI number range by setting
3. 4.
Issue 02 (2011-07-11)
IMSI Segment Start Value and IMSI Segment End Value. If the IMSI of a terminal falls into the IMSI number range, the terminal is regarded as a data card. 5. 6. 7. Run the BSC6900 MML command ADD UDEVICETYPEPRIOGROUP to add terminal type priorities. Run the BSC6900 MML command ADD UCELLSETUP twice to bind a terminal type priority to cell F1 and cell F2 respectively. Optional: Configure preferred camping. Cell F1 is a preferred camping frequency, and cell F2 is a services balancing frequency.
NOTE
This feature does not depend on the camping policy setting of an existing network. When this feature is activated and cell F2 provides discontinuous coverage, you must configure interfrequency neighboring cells for cell F2 during network optimization so that this feature can be enabled.
Method 1 (1) Run the BSC6900 MML command MOD UCELLSELRESEL to make it difficult for UEs in idle mode to trigger inter-frequency measurement. In this step, set Inter-freq cell reselection threshold for idle mode of cell F1 to 0. (2) Run the BSC6900 MML command MOD UCELLSELRESEL to make UEs in idle mode keep triggering inter-frequency measurement. In this step, set Inter-freq cell reselection threshold for idle mode of cell F2 to 127. (3) Run the BSC6900 MML command MOD UINTERFREQNCELL to set inter-frequency neighboring cell parameters (cell F1 to cell F2). Set SIB11 Indicator to TRUE(Send). Set IdleQoffset1sn and IdleQoffset2sn to 20. Set SIB12 Indicator to FALSE(Do not send). (4) Run the BSC6900 MML command MOD UINTERFREQNCELL to set inter-frequency neighboring cell parameters (cell F2 to cell F1). Set SIB11 Indicator to TRUE(Send). Set IdleQoffset1sn and IdleQoffset2sn to -20. Set SIB12 Indicator to FALSE(Do not send). (5) For cell F2 that provides discontinuous coverage, it is recommended to run the BSC6900 MML command MOD UCELLSELRESEL to prevent UEs in idle mode from camping on the edge of cell F2. In this step, set Min Quality Level to -10 and Min RX level to -48. (6) When the UE state transition function is enabled, it is recommended to turn on the SIB4 message switch. Run the BSC6900 MML command MOD UCELLSIBSWITCH to turn on the SIB4 message switch of cell F2. In this step, select the SIB4 check box under the parameter SIB Switch. Method 2 Run the BSC6900 MML command MOD UCELLACCESSSTRICT to forbid UE access to cell F2. Set the parameters according to the network condition. l Verification Procedure 1. On the Trace tab page of the BSC6900 LMT, initiate Uu interface tracing, as shown in Figure 138-1.
138-2
Figure 138-1 Uu interface tracing task
2. 3.
On the HLR, set the PS service type to background or interactive. Check that data card A is in idle mode and camps on cell F2. The priority of data cards in cell F1 (the cell ID is 11013) is higher than that of data cards in cell F2 (the cell ID is 11014). Use data card A to establish an R99 PS service, and check the messages traced on the Uu interface. The BSC6900 sends an RRC_RB_SETUP message to data card A in cell F2. Data card A responds to the BSC6900 with an RRC_RB_SETUP_CMP message in cell F1. The R99 PS service is established in cell F1, as shown in Figure 138-2.
4.
Figure 138-2 Message tracing
l
Issue 02 (2011-07-11)
1. 2. ----End
Run the BSC6900 MML command SET UDRD. In this step, set Device Type Steering DRD Switch to OFF. Run the BSC6900 MML command RMV UCELLLICENSE to disable the layered terminal management function for the cell.
Example
//Activating Intelligent Inter-Carrier UE Layered Management //Turning on the layered terminal management switch SET UDRD: DPGDRDSwitch=ON; //Enabling the layered terminal management function for cell F1 and cell F2 ADD UCELLLICENSE: CellId=11013, INTELLIGENT_INTERFREQ_UE_TYPE_STEERING-1; ADD UCELLLICENSE: CellId=11014, INTELLIGENT_INTERFREQ_UE_TYPE_STEERING-1; //Turning on the single-service DRD switch SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1; //Configuring an IMSI number range ADD UDEVICETYPEIMSI: IMSISegIndex=1, IMSISegChoice=MultiIMSI, IMSIStart="502808888800070", IMSIEnd="502808888800080"; //Adding terminal type priorities ADD UDEVICETYPEPRIOGROUP: DPGId=1, UEDP=1, DataCardDP=1, ReservedDP=1; ADD UDEVICETYPEPRIOGROUP: DPGId=2, UEDP=2, DataCardDP=2, ReservedDP=1; //Binding terminal type priorities to cells ADD UCELLSETUP: CellId=11013, CellName="Cell1", BandInd=Band1, PeerIsValid=VALID, PeerCellId=11014, CnOpGrpIndex=0, UARFCNUplinkInd=TRUE, UARFCNUplink=9612, UARFCNDownlink=10562, TCell=CHIP256, PScrambCode=2, TxDiversityInd=FALSE, SpgId=8, NodeBName="NodeB1", LoCell=0, LAC=H'2501, SAC=H'0000, CfgRacInd=REQUIRE, DPGId=1; ADD UCELLSETUP: CellId=11014, CellName="Cell2", BandInd=Band1, PeerIsValid=VALID, PeerCellId=11013, CnOpGrpIndex=0, UARFCNUplinkInd=TRUE, UARFCNUplink=9612, UARFCNDownlink=10562, TCell=CHIP256, PScrambCode=2, TxDiversityInd=FALSE, SpgId=8, NodeBName="NodeB2", LoCell=1, LAC=H'2501, SAC=H'0000, CfgRacInd=REQUIRE, DPGId=2; //Configuring cell reselection for cell F1 MOD UCELLSELRESEL:CellId=11013, QualMeas=CPICH_ECNO, IdleSintersearch=0; //Configuring cell reselection for cell F2 MOD UCELLSELRESEL:CellId=11014, QualMeas=CPICH_ECNO, IdleSintersearch=127, ConnSintrasearch=5, ConnSintersearch=2, SsearchRat=2; //Configuring co-coverage inter-frequency neighboring cell parameters (cell F1 to cell F2) MOD UINTERFREQNCELL: RNCId=3012, CellId=11013, NCellRncId=3012, NCellId=11014, SIB11Ind=TRUE, SIB12Ind=FALSE, IdleQoffset1sn=20, IdleQoffset2sn=20; //Configuring co-coverage inter-frequency neighboring cell parameters (cell F2 to cell F1) MOD UINTERFREQNCELL: RNCId=3012, CellId=11014, NCellRncId=3012, NCellId=11013, SIB11Ind=TRUE, SIB12Ind=FALSE, IdleQoffset1sn=-20, IdleQoffset2sn=-20; //Turning on the SIB4 message switch for cell F2 MOD UCELLSIBSWITCH: CellId=11014, SibCfgBitMap=SIB4-1; MOD UCELLSELRESEL: CellId=11014, QualMeas=CPICH_ECNO, Qqualmin=-10, Qrxlevmin=-48; //Deactivating Intelligent Inter-Carrier UE Layered Management //Turning off the layered terminal management switch SET UDRD: DPGDRDSwitch=OFF;
138-4
Issue 02 (2011-07-11)
//Disabling the layered terminal management function for a cell RMV UCELLLICENSE: CellId=11013; RMV UCELLLICENSE: CellId=11014;
Issue 02 (2011-07-11)
138-5
139 Configuring Inter Frequency Hard Handover Based on Coverage
139
Prerequisite
l l l l
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.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites The UE supports relevant measurements and the handover procedure.
Context
This feature introduces inter-frequency hard handover triggered by Active Set quality measurement event 2D or by Uplink Radio Link Qos or emergency blind handover triggered by event 1F.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select HO_INTER_FREQ_HARD_HO_SWITCH from the HandOver Switch drop-down list. 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 parameters related to coverage-based inter-frequency hard handover.
2. 3.
l
Issue 02 (2011-07-11)
1. 2. 3.
Attenuate signals in the current cell that the UE accesses to trigger reporting of event 2D by the UE. Click to display Uu Interface Trace on the BSC6900 LMT. Check whether the RNC has sent the UE an RRC_MEAS_CTRL message and the traced message contains thresholds for triggering events 2D and 2F and the reporting mode. Check whether the RNC has sent the UE an RRC_MEAS_RPRT message and the traced message contains an event 2D measurement report shown in Figure 139-1. Figure 139-1 Event 2D measurement report
4.
5.
After the event 2D measurement report is reported, check whether the RNC has sent the UE an RRC_MEAS_CTRL message and the traced message contains the information element interFrequencyMeasurement, as shown in Figure 139-2.
Figure 139-2 Inter-frequency measurement control message
l
139-2
1. ----End
Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect HO_INTER_FREQ_HARD_HO_SWITCH from HandOver Switch.
Example
//Activating Inter Frequency Hard Handover Based on Coverage SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_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;
Issue 02 (2011-07-11)
139-3
140 Configuring Inter Frequency Hard Handover Based on DL QoS
140
Prerequisite
l l l
Configuring Inter Frequency Hard Handover Based on DL QoS
This section describes how to activate, verify, and deactivate the optional feature WRFD-020304 Inter Frequency Hard Handover Based on DL QoS.
Context
When the load of services is high in a cell and downlink QoS decreases, this feature enables the UE to be handed over to an inter-frequency cell, guaranteeing QoS requirements.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the inter-frequency hard handover. 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 (BSC6900 level) to configure parameters related to DL-QoS-based inter-frequency hard handover. Run the BSC6900 MML command SET UQOSACT to activate inter-frequency hard handover based on downlink QoS for BE services. Run the BSC6900 MML command SET UQOSACT to activate inter-frequency hard handover based on downlink QoS for AMR and AMR-WB services.
4. 5.
Issue 02 (2011-07-11)
6. l
Run the BSC6900 MML command SET UQOSACT to activate inter-frequency hard handover based on downlink QoS for VP services. Log in to the BSC6900 LMT and start Uu Interface Trace. Ensure that the BSC6900 sends to the UE an RRC_MEAS_CTRL message, which carries the 6A measurement control information, as shown in Figure 140-1.
3.
Ensure that the UE reports to the BSC6900 an RRC_MEAS_RPRT message, which carries the 6A1 report, as shown in Figure 140-2.
140-2
Issue 02 (2011-07-11)
4.
Ensure that the BSC6900 sends to the UE an RRC_MEAS_CTRL message and starts inter-frequency measurement of the event or period type. Then, check that the corresponding traced message indicates that the BSC6900 has sent the inter-frequency measurement control message to the UE, as shown in Figure 140-3.
Deactivation Procedure 1. Run the BSC6900 MML command SET UQOSACT to deactivate inter-frequency hard handover based on downlink QoS for BE services.
Issue 02 (2011-07-11)
2. 3. ----End
Run the BSC6900 MML command SET UQOSACT to deactivate inter-frequency hard handover based on downlink QoS for AMR and AMR-WB services. Run the BSC6900 MML command SET UQOSACT to deactivate inter-frequency hard handover based on downlink QoS for VP services.
Example
//Activating Inter Frequency Hard Handover Based on DL QoS SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_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 RMV UCELLQOSHO: CellId=111; SET UQOSACT: BEQosPerform=NO; or SET UQOSACT: BEQosPerform=YES, BeDlAct1=None, BeDlAct2=None, BeDlAct3=None; SET UQOSACT: AMRQosPerform=NO; or SET UQOSACT: AMRQosPerform=YES, DlQosAmrInterFreqHoSwitch=NO, DlQosWAmrInterFreqHoSwitch=NO; SET UQOSACT: VPQosPerform=NO; or SET UQOSACT: VPQosPerform=YES, DlQosVpInterFreqHoSwitch=NO;
140-4
Issue 02 (2011-07-11)
141 Configuring SRNS Relocation (UE Not Involved)
141
Prerequisite
l l
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).
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-020605 SRNS Relocation Introduction Package has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Others Prerequisites The CN supports this feature. Both the SRNC and the DRNC support this feature.
Context
This feature supports the SRNS relocation procedure based on the standard Iu interface defined by 3GPP specifications. The static SRNS relocation procedure does not involve the UE and radio connections are not affected during the relocation. Therefore, static SRNS relocation is an optimal relocation mode.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command ADD DEVIP to add a device IP address to an interface board. Run the BSC6900 MML command ADD IPOAPVC to add an Internet Protocol over ATM (IPoA) permanent virtual circuit (PVC). In this step: Set IP address to the device IP address of the interface board. Set Peer IP address to the IP address of the serving GPRS support node (SGSN).
The VPI and VCI must be the same as those configured on the SGSN side. You can run the command LST IPOA on the SGSN maintenance terminal to query the settings of the VPI and VCI on the SGSN side. 3. Run the BSC6900 MML command ADD IPRT to add a route from the BSC6900 to the DRNC. In this step: Set Subrack No. and Slot No. respectively to the subrack number and slot number of the Iu-PS interface board carrying the IP path. Set Destination IP Address to the IP address of the DRNC on the Iu interface. Set Forward route address to the IP address of the SGSN gateway. 4. Run the BSC6900 MML command ADD IPPATH to add an IP path for static SRNS relocation. In this step: Set Adjacent Node ID to the adjacent node ID of the SGSN. Set Interface Type to IUR(Iur Interface). Set Local IP address to the IP address of the SRNC on the Iu interface. Set Peer IP address to the Iu IP address of the DRNC on the Iu interface. 5. 6. 7. Run the BSC6900 MML command ADD UEXT3GCELL to add a cell to the neighboring RNC. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the HO_INTRA_FREQ_SOFT_HO_SWITCH check box under the parameter HandOver Switch and select the SRNSR_DSCR_PROPG_DELAY_SWITCH check box under the parameter SRNSR Algorithm Switch.
NOTE
SRNS relocation can be triggered by Iur transmission resource optimization, location separation, delay optimization, and separation time. The preceding procedure takes delay optimization as an example to describe the data configuration.
8. 9.
Run the BSC6900 MML command SET USRNSR. In this step, select the All service check box under the parameter SRNS Relocation-Allowed Traffic Type. Run the BSC6900 MML command MOD UNRNC. In this step, set SHO cross IUR trigger to an appropriate value based on the network plan, and set Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC. The following procedure takes SRNS relocation from SRNC (RNC1) to DRNC (RNC2) as an example. Initiate interface message tracing on both RNC1 LMT and RNC2 LMT. Configure Iu interface message tracing, as shown in Figure 141-1. Configure Iur interface message tracing, as shown in Figure 141-2.
141-2
Issue 02 (2011-07-11)
Figure 141-2 Iur Interface Trace dialog box
Call drops do not occur during SRNS relocation if all the following messages are traced: On the Iu interface of RNC1: RNC1->CN RANAP_RELOCATION_REQUIRED CN->RNC1 RANAP_RELOCATION_COMMAND On the Iu interface of RNC2: RNC2->CN RANAP_RELOCATION_REQ CN->RNC2 RANAP_RELOCATION_REQ_ACK RNC2->CN RANAP_RELOCATION_DETECT RNC2->CN RANAP_RELOCATION_COMPLETE On the Iur interface between RNC1 and RNC2: RNC1->RNC2: RNSAP_RELOCATION_COMMIT
On the Iu interface of RNC1: CN->RNC1 RANAP_IU_RELEASE_COMMAND RNC1->CN RANAP_IU_RELEASE_COMPLETE l Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the HO_INTRA_FREQ_SOFT_HO_SWITCH check box under the parameter HandOver Switch and deselect the SRNSR_DSCR_PROPG_DELAY_SWITCH check box under the parameter SRNSR Algorithm Switch.
----End
Example
//Activating SRNS Relocation (UE Not Involved) //Adding a device IP address to an interface board ADD DEVIP:IPADDR="172.12.10.181", SRN=0, SN=24, MASK="255.255.255.0", DEVTYPE=IPOA_CLIENT_IP, MTU=1696; //Adding an Internet Protocol over ATM (IPoA) permanent virtual circuit (PVC) ADD IPOAPVC:IPADDR="172.12.10.181", PEERIPADDR="172.12.10.254", CARRYT=NCOPT, CARRYNCOPTN=0, CARRYVPI=182, CARRYVCI=50, TXTRFX=105, RXTRFX=105, PEERT=IUPS; //Adding an IP route from the BSC6900 to the DRNC ADD IPRT:SRN=0, SN=24, DSTIP="172.12.10.226", DSTMASK="255.255.255.255", NEXTHOP="172.12.10.254", REMARK="Reloc route-RNC226", PRIORITY=HIGH; //Adding an IP path for static SRNS relocation ADD IPPATH:ANI=1, PATHID=3, IPADDR="172.12.10.181", PEERIPADDR="172.12.10.226", VLANFLAG=DISABLE, PATHT=EF, PEERMASK="255.255.255.255", TXBW=100000, RXBW=100000, PATHCHK=DISABLED, ITFT=IUPS, TRMLOADTHINDEX=2; //Adding a cell to the neighboring RNC ADD UEXT3GCELL: NRncId=1, CellId=2, CellHostType=SINGLE_HOST, CellName="111", CnOpGrpIndex=0, PScrambCode=0, BandInd=Band2, UARFCNUplinkInd=TRUE, UARFCNUplink=12, UARFCNDownlink=412, TxDiversityInd=FALSE, LAC=1, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED, CellCapContainerFdd=DELAY_ACTIVATION_SUPPORT-0, OverLayMobilityFlag=FORBIDDEN, EFachSupInd=FALSE; //Adding an intra-frequency neighboring cell ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=2, NCellId=311, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Setting the BSC6900-level algorithm switch SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1, SrnsrSwitch=SRNSR_DSCR_PROPG_DELAY_SWITCH-1; //Setting the type of service that allows SRNS relocation SET USRNSR: SrnsRabCnDomainType=ALL; //Setting the type of service that allows cross-Iur handovers MOD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1,
141-4
Issue 02 (2011-07-11)
PsBeProcType=CORRM_SRNSR_PSBE_RELOC; MOD UNRNC: NRncId=2, SHOTRIG=CS_SHO_SWITCH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1, PsBeProcType=CORRM_SRNSR_PSBE_RELOC; //Deactivating SRNS Relocation (UE Not Involved) //Setting the BSC6900-level algorithm switch SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0, SrnsrSwitch=SRNSR_DSCR_PROPG_DELAY_SWITCH-0;
Issue 02 (2011-07-11)
141-5
142 Configuring SRNS Relocation with Hard Handover
142
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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 l
License The license controlling this feature has been activated. Other Prerequisites The SRNC and the DRNC must support this feature simultaneously. The CN must support this feature simultaneously.
Context
When the Iur interface is unavailable, this feature enables the UE to move between RNCs. This feature is enabled when the Iur interface does not exist, or the resources for the connection setup on the Iur interface are insufficient.
Procedure
l 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 and HO_INTER_FREQ_HARD_HO_SWITCH from the HandOver switch list.
Issue 02 (2011-07-11)
4.
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. No call drops occur during the transition. You can view the transition procedure on the Iu interface tracing pane of RNC1, as shown in Figure 142-1. Take RNC1 as the SRNC, and RNC2 as the DRNC for example. When the Iur interface between RNC1 and RNC2 is unavailable, this feature enables the UE to move between RNCs.
142-2
Issue 02 (2011-07-11)
Figure 142-1 SRNS Relocation with Hard Handover
----End
Example
//Activating SRNS Relocation with Hard Handover //Add an intra-frequency neighboring cell
Issue 02 (2011-07-11)
142-3
ADD UINTERFREQNCELL: RncId=1, CellId=111, NCellRncId=2, NCellId=312, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHOFlag=FALSE, NPrioFlag=FALSE; //Select HO_INTER_FREQ_HARD_HO_SWITCH and HO_INTRA_FREQ_HARD_HO_SWITCH from the HandOver switch list SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1&HO_INTRA_FREQ_HARD_HO_SWITCH-1; //Turn on HHO cross IUR trigger, and set Handover Type for PS BE Traffic to CORRM_SRNSR_PSBE_RELOC MOD UNRNC: NRncId=2, HHOTRIG=ON, PsBeProcType=CORRM_SRNSR_PSBE_RELOC;
142-4
Issue 02 (2011-07-11)
143 Configuring SRNS Relocation with Cell/URA Update
143
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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 controlling this feature has been 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
Issue 02 (2011-07-11)
143 Configuring SRNS Relocation with Cell/URA Update
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
----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;
143-2
Issue 02 (2011-07-11)
144 Configuring Inter-RAT Handover Based on Coverage
144
Prerequisite
l l l l
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.
Context
This feature supports measurement-based inter-RAT handover triggered by event 2D or uplink UE QoS and urgent blind inter-RAT handover triggered by event 1F. This type of handover is applicable to inter-RAT interworking based on coverage or caused by moving UEs.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH from the HandOver Switch list. Run the BSC6900 MML command ADD U2GNCELL to add an inter-frequency neighboring GSM cell. Run the BSC6900 MML command ADD UCELLINTERRATHOCOV (cell level) or SET UINTERRATHOCOV (RNC level) to configure parameters related to coverage-based inter-RAT handover to GSM.
2. 3.
l
Issue 02 (2011-07-11)
1. 2. 3.
Attenuate signals in the current cell that the UE accesses to trigger reporting of event 2D by the UE. Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_MEAS_RPRT. Check whether event 2D shown in Figure 144-1 has been reported in the traced messages. Figure 144-1 Event 2D measurement report
4. 5.
Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_MEAS_CTRL. Check in the traced messages whether the RNC has sent the UE an inter-RAT measurement control message shown in Figure 144-2.
l
144-2
1. 2.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to deactivate this feature. Run the BSC6900 MML command RMV UCELLINTERRATHOCOV (cell level) or SET UINTERRATHOCOV (RNC level) to remove or restore the parameters related to coverage-based inter-RAT handover to GSM.
----End
Example
//Activating Inter-RAT Handover Based on Coverage SET UCORRMALGOSWITCH: HoSwitch=&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;
Issue 02 (2011-07-11)
144-3
145 Configuring Inter-RAT Handover Based on DL QoS
145
Prerequisite
l l l l
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.
Context
When the load of voice and PS BE services is high in a cell and downlink QoS decreases, this feature enables the UE to be handed over to an inter-RAT cell, guaranteeing QoS requirements.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set HandOver Switch to HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH. Run the BSC6900 MML command ADD U2GNCELL to add an inter-RAT neighboring cell. Run the BSC6900 MML command SET UQOSHO to set BSC6900-level parameters related to Inter-RAT Handover Based on DL QoS. Run the BSC6900 MML command SET UQOSACT to turn on QoS switches for different traffic classes.
2. 3. 4. l
Issue 02 (2011-07-11)
1. 2.
Log in to the BSC6900 LMT and start Uu Interface Trace. Check that the BSC6900 sends to the UE an RRC_MEAS_CTRL message, which carries the 6A measurement control information, as shown in Figure 145-1.
3.
Ensure that the UE sends to the BSC6900 an RRC_MEAS_RPRT message, which carries the 6A1 report, as shown in Figure 145-2.
145-2
Issue 02 (2011-07-11)
4.
Ensure that the BSC6900 sends to the UE an RRC_MEAS_CTRL message and starts inter-frequency measurement of the event or period type. Then, check that the corresponding traced message indicates that the BSC6900 sends the inter-frequency measurement control message to the UE, as shown in Figure 145-3.
Deactivation Procedure 1. Run the BSC6900 command SET UCORRMALGOSWITCH. In this step, deselect HO_INTER_RAT_CS_OUT_SWITCH and
Issue 02 (2011-07-11)
HO_INTER_RAT_PS_OUT_SWITCH from the drop-down list of HandOver Switch. 2. ----End Run the BSC6900 MML command SET UQOSACT to turn off QoS switches for different traffic classes.
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, BeDlAct1=InterRatHO, DlQosAmrInterRatHoSwitch=YES, DlQosWAmrInterRatHoSwitch=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;
145-4
Issue 02 (2011-07-11)
146 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
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.
146
l l
Configuring Video Telephony
Prerequisite
Dependencies on Hardware The CN complies with 3GPP Release 6 or later. Dependencies on Other Features One or multiple of the following features must be configured before this feature is activated: 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 controlling this feature has been activated. Other Prerequisites The UE complies with 3GPP Release 6 or later.
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. However, due to the limitation of UE and network support capability, the service may not be implemented. Therefore, Service Change and UDI Fallback (SCUDIF) is introduced in 3GPP Release 6 to provide the mechanism to provide the mechanism to fall back to speech without experiencing call drops in these scenarios.
Procedure
l Activation Procedure The license controlling this feature has been activated.
146 Configuring Video Telephony Fallback to Speech (AMR) for Inter-RAT HO
Verification Procedure 1. 2. Start Iu Interface Trace and Uu Interface Trace on the BSC6900 LMT. After VP services are established, check in the Uu Interface Trace dialog box that the UE sends to the BSC6900 an RRC_MEAS_RPRT message, which contains the 3A report. In the Iu Interface Trace dialog box, check that the BSC6900 sends an RAB_MODIFY_REQ message to the CN. In the RAB_MODIFY_REQ message, the value of the IE alternativeRABConfigurationRequest is alternative-RABconfiguration-Requested.
3.
----End
146-2
Issue 02 (2011-07-11)
147 Configuring Inter-RAT Handover Phase 2
147
Prerequisite
l l
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.
Dependencies on Hardware BSC should support NACC RIM (RAN Information Management) and PS handover procedure. Dependencies 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)
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: 148 Configuring NACC(Network Assisted Cell Change)
147 Configuring Inter-RAT Handover Phase 2
149 Configuring PS Handover between UMTS and GPRS ----End
147-2
Issue 02 (2011-07-11)
148 Configuring NACC(Network Assisted Cell Change)
148
Prerequisite
l l
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).
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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.
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.
Issue 02 (2011-07-11)
148-1
148 Configuring NACC(Network Assisted Cell Change)
2.
Run the BSC6900 MML command ADD UEXT2GCELL(for new neighboring cell) or MOD UEXT2GCELL (for the existing 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;
148-2
Issue 02 (2011-07-11)
149 Configuring PS Handover between UMTS and GPRS
149
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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.
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:
Issue 02 (2011-07-11)
149 Configuring PS Handover between UMTS and GPRS
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
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;
149-2
Issue 02 (2011-07-11)
150 Configuring Mobility Between UMTS and LTE Phase 1
150
Prerequisite
l l l l
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 details about how to configure this feature on the LTE side, see the related documents provided by the LTE equipment vendor.
Dependencies on Hardware The UE is a UMTS&LTE dual-mode terminal. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites The UE supports both UMTS and LTE. The LTE network supports this feature.
Context
The feature Mobility Between UMTS and LTE Phase 1 provides the following functions: l l Huawei UMTS supports bidirectional cell reselection between a UMTS cell and an LTE cell. Huawei UMTS supports PS handovers from an LTE cell to a UMTS cell
For details, see the RAN12.0 Optional Feature Description.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCELLSIBSWITCH or MOD UCELLSIBSWITCH. In this step, set SIB Switch to SIB19. After the information about the frequencies of neighboring LTE cells is configured and SIB Switch is set to SIB19, the BSC6900 sends SIB19 messages to UEs. The
SIB19 message contains the neighboring LTE cell list and LTE cell reselection parameters. 2. Run the BSC6900 MML command ADD UCELLSELRESEL or MOD UCELLSELRESEL. In this step, set Absolute priority level of the serving cell to an appropriate value. Inter-RAT measurement is performed based on the settings of RSCP threshold for low-prio-freq measurement initiation and Ec/No threshold for low-prio-freq measurement initiation. The measurement result provides a reference to cell reselection. 3. Run the BSC6900 MML command ADD UCELLNFREQPRIOINFO or MOD UCELLNFREQPRIOINFO to configure the information about the frequencies of neighboring cells. The UE makes cell reselection decisions based on the configured information about the frequencies of neighboring cells. 4. Configure the related data, such as the neighboring cell relationships between cells, on the LTE side. For details about how to configure this feature on the LTE side, see the related documents provided by the LTE equipment vendor. If the LTE equipment is provided by Huawei, see the LTE document Idle Mode Management Parameter Description. In the Navigation Tree pane on the BSC6900 LMT, click the Trace tab. In the displayed Trace Navigation Tree pane, double-click UMTS Services. On the unfolded list, double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box, select RRC_SYS_INFO_TYPE19 to trace Uu interface SIB19 message.
150-2
Issue 02 (2011-07-11)
2.
Analyze the traced messages. If the SIB19 message has been traced on the Uu interface, as shown in Figure 150-2, this feature has been activated. If the SIB19 message is not traced on the Uu interface, this feature is not activated. Figure 150-2 SIB message tracing
NOTE
To deactivate this feature, you can either turn off the SIB19 switch or deactivate the license. l To deactivate this feature in a specific cell, you are advised to turn off the SIB19 switch. l To deactivate this feature in all cells under a BSC6900, deactivate the license. This method is not recommended.
1.
Run the BSC6900 MML command MOD UCELLSIBSWITCH. In this step, deselect the SIB19 check box under the parameter SIB Switch to turn off the SIB19 switch in a cell. After the switch is turned off, the BSC6900 stops sending SIB19 messages to UEs. In such a case, the configured absolute priority of the serving cell
Issue 02 (2011-07-11)
and the configured information about the frequencies of neighboring cells become ineffective. 2. ----End Run the BSC6900 MML command SET LICENSE to deactivate the license controlling the feature Mobility Between UMTS and LTE Phase 1.
Example
//Activating Mobility Between UMTS and LTE Phase 1 MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-1; MOD UCELLSELRESEL: CellId=1, QualMeas=CPICH_ECNO, QrxlevminExtSup=FALSE, NonhcsInd=NOT_CONFIGURED, ThdPrioritySearch1=2, ThdPrioritySearch2=2; MOD UCELLNFREQPRIOINFO: CellId=1, EARFCN=1, NPriority=2, BlacklstCellNumber=D0; //Deactivating Mobility Between UMTS and LTE Phase 1 MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-0; SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH5=LQW1ULM01-0;
150-4
Issue 02 (2011-07-11)
151 Configuring Service-Based PS Service Redirection from UMTS to LTE (trial)
Service Redirection from UMTS to LTE (trial)

This section describes how to activate, verify, and deactivate the optional feature WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE (trial).
151
l l l l
Configuring Service-Based PS
Prerequisite
Dependencies on Hardware There is no requirement for BSC6900 and NodeB. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Others The SGSN and UE support this feature.
Context
With this feature, the operator can choose to hand over the high-speed PS services from the UMTS network to the LTE network. This helps fully utilize the UMTS and LTE network resources, improving the user experience.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH. Run the BSC6900 MML command ADD ULTECELL. In this step, configure an LTE cell. Set LTE Cell Supporting PS HO Indicator to NotSupport and set BlackCell List Flag to False. After the UE reports a 3C measurement report of the LTE cell, the BSC6900 initiates a PS redirection procedure, not a PS handover procedure. Run the BSC6900 MML command ADD ULTENCELL to configure a neighboring LTE cell. Run the BSC6900 MML command SET UU2LTEHONCOV to set RNC-Oriented Non-Coverage-Based UMTS-LTE Handover Measurement Algorithm
3. 4.
Issue 02 (2011-07-11)
Parameters. The BSC6900 sends these parameters to the UE by means of a measurement control message. 5. Run the BSC6900 MML command ADD UCELLU2LTEHONCOV to set CellOriented Non-Coverage-Based UMTS-LTE Handover Measurement Algorithm Parameters. Run the BSC6900 MML command MOD UTYPRABBASIC to modify the basic configuration of a typical radio access bearer (RAB). In this step, set Service-Based Handover to LTE Allowed to HO_TO_EUTRAN_SHOULD_BE_PERFORM.
6.
Verification Procedure Start Uu interface tracing on the LMT to trace messages on the Uu interface. View the RRC_MEAS_CTRL message, as shown in Figure 151-1. If the measurementCommand message contains the information element (IE) e-UTRAFrequencyInfo, this feature takes effect. The measurement control message sent by the BSC6900 contains the LTE cell information. After receiving the message, the UE measures the signal quality in the LTE cell. The measurement result serves as the basis for handover decision. Figure 151-1 Viewing the IE e-UTRA-FrequencyInfo
View the RRC_CONN_REL message, as shown in Figure 151-2. If in the message the rrcConnectionRelease message contains the IE EUTRA-TargetFreqInfo, the RRC connection release message carries the LTE cell information. After receiving this message, the UE is handed over to the LTE network and the UE reestablishes PS services in the LTE cell.
151-2
Issue 02 (2011-07-11)
Figure 151-2 Viewing the IE EUTRA-TargetFreqInfo
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH.
----End
Example
//Activation procedure //Enabling HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH SET UCORRMALGOSWITCH: HoSwitch=HO_LTE_PS_OUT_SWITCH-1&HO_LTE_SERVICE_PS_OUT_SWITCH-1; //Configuring an LTE cell ADD ULTECELL: LTECellIndex=0, LTECellName="LTECELL", EUTRANCELLID=8, MCC="460", MNC="01", TAC=10, CnOpGrpIndex=1, CellPHYID=100, LTEBand=10, LTEArfcn=500; //Configuring a neighboring LTE cell ADD ULTENCELL: RNCId=1, CellId=2, LTECellIndex=1; //Setting the parameters related to the RNC-oriented non coverage-based UMTS-to-LTE handover measurement algorithm SET UU2LTEHONCOV: LTEMeasTypOf3C=MeasurementQuantity, U2LTEFilterCoef=D6, U2LTEMeasTime=30, LTEMeasQuanOf3C=RSRP, Hystfor3C=2, TrigTime3C=D10, TargetRatThdRSRP=20, TargetRatThdRSRQ=30; //Setting the parameters related to the cell-oriented non coverage-based UMTS-to-LTE handover measurement algorithm ADD UCELLU2LTEHONCOV: CellId=1, LTEMeasTypOf3C=MeasurementQuantity, U2LTEFilterCoef=D6, U2LTEMeasTime=30, LTEMeasQuanOf3C=RSRP, Hystfor3C=2, TrigTime3C=D10, TargetRatThdRSRP=20, TargetRatThdRSRQ=30; //Modifying the basic configuration of a typical RAB MOD UTYPRABBASIC: RabIndex=1, EUTRANSHIND=HO_TO_EUTRAN_SHOULD_BE_PERFORM;
//Deactivation procedure //Disabling HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH SET UCORRMALGOSWITCH: HoSwitch=HO_LTE_PS_OUT_SWITCH-0&HO_LTE_SERVICE_PS_OUT_SWITCH-0;
Issue 02 (2011-07-11)
151-3
152 Configuring Inter Frequency Load Balance
152
Prerequisite
l l
Configuring Inter Frequency Load Balance
This section describes how to activate, verify, and deactivate the optional feature WRFD-020103 Inter Frequency Load Balance.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The two optional features WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package must be configured before this feature 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 load reshuffling (LDR) algorithms: UL_UU_LDR(Uplink UU LDR Algorithm) DL_UU_LDR(Downlink UU LDR Algorithm) CELL_CODE_LDR(Code LDR Algorithm) 2. Run the BSC6900 MML commands SET UCORRMALGOSWITCH and MOD UCELLHOCOMM. In this step, set HandOver Switch to HO_ALGO_LDR_ALLOW_SHO_SWITCH and HO_INTER_FREQ_HARD_HO_SWITCH. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell supporting blind handover, or to add an inter-frequency
3.
Issue 02 (2011-07-11)
neighboring cell supporting measurement by setting the parameter DrdOrLdrFlag to an appropriate value. 4. Run the BSC6900 MML command ADD UCELLINTERFREQHONCOV (cell level) or SET UINTERFREQHONCOV (BSC6900 level) to set parameters related to load-based inter-RAT hard handover to appropriate values. In the case of measurement-based inter-frequency handover, run the BSC6900 MML command MOD UCELLLDR. In this step, set InterFreq Load Handover Method Selection to MEASUREHO(MEASUREHO). Set LDR-related thresholds as follows: Run the BSC6900 MML command MOD UCELLLDM to set power LDR thresholds (UL LDR trigger threshold, UL LDR release threshold, DL LDR trigger threshold, DL LDR release threshold, and DL State Trans Hysteresis threshold) to appropriate values. Run the BSC6900 MML command MOD UCELLLDR to set Cell LDR SF reserved threshold to an appropriate value. 7. 8. 9. Run the BSC6900 MML command MOD UCELLLDR. In this step, set Code congestion select inter-freq indication to TRUE(TRUE). Run the BSC6900 MML command SET ULDCPERIOD. In this step, set LDR period timer length to an appropriate value. Run the BSC6900 MML command MOD UCELLLDR. In this step, select InterFreqLDHO(inter-freq load handover) as an LDR action and set other parameters related to LDR actions to appropriate values. Run the following BSC6900 MML commands to check whether this feature has been activated. LST UCELLALGOSWITCH LST UCELLLDR LST UCELLLDM LST ULDCPERIOD LST UCORRMALGOSWITCH LST UINTERFREQNCELL LST UCELLHOCOMM LST UCELLINTERFREQHONCOV(cell level) LST UINTERFREQHONCOV (BSC6900 level) 2. l To check whether Inter Frequency Load Balance, which is one of LDR actions, has been activated, see the verification procedure in 24 Configuring Load Reshuffling. Run the BSC6900 MML command MOD UCELLALGOSWITCH to deactivate the following LDR algorithms: UL_UU_LDR(Uplink UU LDR Algorithm) DL_UU_LDR(Downlink UU LDR Algorithm) CELL_CODE_LDR(Code LDR Algorithm) 2. Run the BSC6900 MML commands SET UCORRMALGOSWITCH and MOD UCELLHOCOMM to deactivate the inter-frequency handover. In this step, close
5.
6.
152-2
HO_ALGO_LDR_ALLOW_SHO_SWITCH and HO_INTER_FREQ_HARD_HO_SWITCH through HandOver Switch. 3. 4. ----End Run the BSC6900 MML command MOD UCELLLDR. In this step, set Code congestion select inter-freq indication to FALSE(FALSE). Restore the parameter settings modified in the activation procedure.
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; ADD UINTERFREQNCELL: RNCId=11, CellId=111, NCellRncId=22, NCellId=222, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE, NPrioFlag=FALSE, DrdOrLdrFlag=TRUE, InterNCellQualReqFlag=FALSE; ADD UCELLINTERFREQHONCOV: CellId=111, InterFreqFilterCoef=D3, Hystfor2C=6, TrigTime2C=D640, InterFreqCovHOThdEcN0=-16, InterFreqMeasTime=60, PeriodFor2C=4, AmntOfRpt2C=5; MOD UCELLLDR: CellId=111, InterFreqLDHOMethodSelection=MEASUREHO; MOD UCELLLDM: CellId=111, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70, DlLdrRelThd=60, DlLdTrnsHysTime=1000; MOD UCELLLDR: CellId=111, CellLdrSfResThd=SF8; MOD UCELLLDR: CellId=111, CodeCongSelInterFreqHoInd=TRUE; SET ULDCPERIOD: LdrPeriodTimerLen=10; MOD UCELLLDR: CellId=111, DlLdrFirstAction=InterFreqLDHO, DlInterFreqHoCellLoadSpaceThd=20, DlInterFreqHoBWThd=200000; //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;
Issue 02 (2011-07-11)
152-3
153 Configuring Inter-RAT Handover Based on Service
153
Prerequisite
l l l
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.
Context
This feature provides a mechanism for performing handover between GSM/GPRS and UMTS systems on the basis of services. This feature forwards appropriate services in a UMTS system to a GSM/GPRS system, balancing load between the two systems. This feature also prevents the handover from adversely affecting services based on service attributes.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH from the HandOver Switch list. Run the BSC6900 MML command ADD UEXT2GCELL to add a neighboring GSM cell. Run the BSC6900 MML command ADD U2GNCELL to set neighbor relation with the neighboring GSM cell. Run the BSC6900 MML command ADD UCELLHOCOMM. In this step, set InterRAT CS handover switch or Inter-RAT PS handover switch to ON.
2. 3. 4.
Issue 02 (2011-07-11)
153 Configuring Inter-RAT Handover Based on Service
5.
Run the BSC6900 MML command ADD UCELLINTERRATHONCOV (cell level) or SET UINTERRATHONCOV (RNC level) to configure parameters related to non-coverage-based inter-frequency handover to GSM. Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_MEAS_CTRL. After services are set up, view in the traced messages whether the RNC has sent the UE an inter-frequency measurement control message shown in Figure 153-1.
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLHOCOMM. In this step, set InterRAT CS handover switch or Inter-RAT PS handover switch to OFF.
----End
Example
//Activating Inter-RAT Handover Based on Service SET UCORRMALGOSWITCH: HoSwitch=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;
153-2
Issue 02 (2011-07-11)
154 Configuring Inter-RAT Handover Based on Load
154
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features If this feature is used for HSDPA or HSUPA load control, the feature WRFD-010610 HSDPA Introduction Package or WRFD-010612 HSUPA Introduction Package has been configured correspondingly before this feature is activated.
Context
This feature is an important part of Load Reshuffling (LDR). It enables some UEs in a UMTS cell to be blindly handed over to a GSM or GPRS cell to reduce the load of the UMTS cell.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the inter-RAT handover. In this step, select the HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH check boxes under the parameter HandOver Switch. Run the BSC6900 MML command ADD UEXT2GCELL to add the information about a GSM cell. Run the BSC6900 MML command ADD U2GNCELL to add the GSM cell as a neighboring cell of the UMTS cell. Run the BSC6900 MML command ADD UCELLLDR to set the inter-RAT handover policy for the UMTS cell. In this step, set DL LDR fourth action to
2. 3. 4.
Issue 02 (2011-07-11)
CSInterRatShouldBeLDHO(CS domain inter-rat should be load handover), DL LDR fifth action to PSInterRatShouldBeLDHO(PS domain inter-rat should be load handover), UL LDR fourth action to CSInterRatShouldBeLDHO(CS domain inter-rat should be load handover), and UL LDR fifth action to PSInterRatShouldBeLDHO(PS domain inter-rat should be load handover). 5. Run the BSC6900 MML command ADD UCELLINTERRATHONCOV (at the cell level) or SET UINTERRATHONCOV (at the RNC level) to configure parameters related to non-coverage-based inter-frequency handover to GSM. Initiate Iu interface message tracing and Uu interface message tracing on the BSC6900 LMT. Use a UE in the UMTS cell to call another UE in the same cell. The call is set up successfully. Run the BSC6900 MML command MOD UCELLLDM to reduce the downlink LDR threshold. The following messages can be traced on the Iu interface: the RANAP_RELOCATION_REQUIRED message from the RNC to the CN, and the RANAP_RELOCATION_COMMAND message from the CN to the RNC. The following message can be traced on the Uu interface: the RRC_HO_FROM_UTRAN_CMD_GSM message from the RNC to the UE. The following messages can be traced on the Iu interface: the RANAP_RELOCATION_REQUIRED message from the RNC to the CN, the RANAP_RELOCATION_COMMAND message from the CN to the RNC, the RANAP_IU_RELEASE_COMMAND message from the CN to the RNC, and the RANAP_IU_RELEASE_COMPLETE message from the RNC to the CN. l Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLLDR to deactivate the load-based handover. In this step, set DL LDR fourth action, DL LDR fifth action, UL LDR fourth action, and UL LDR fifth action to NoAct. Run the BSC6900 MML command SET UCORRMALGOSWITCH to deactivate the inter-RAT handover. In this step, deselect the HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH check boxes under the parameter HandOver Switch.
2.
----End
Example
//Activating Inter-RAT Handover Based on Load SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1; ADD UEXT2GCELL: GSMCellIndex=2, GSMCellName="2", NBscIndex=2, LdPrdRprtSwitch=OFF, MCC="460", MNC="07", CnOpGrpIndex=1, LAC=H'0012, CfgRacInd=REQUIRE, RAC=H'01, CID=2, NCC=2, BCC=2, BcchArfcn=1000, RatCellType=GSM, UseOfHcs=NOT_USED; ADD U2GNCELL: RncId=1, CellId=2, GSMCellIndex=2, BlindHoFlag=TRUE, BlindHOPrio=1, NPrioFlag=FALSE; ADD UCELLLDR: CellId=1, DlLdrFourthAction=CSInterRatShouldBeLDHO, DlLdrFifthAction=PSInterRatShouldBeLDHO, UlLdrFourthAction=CSInterRatShouldBeLDHO, UlLdrFifthAction=PSInterRatShouldBeLDHO;
154-2
Issue 02 (2011-07-11)
ADD UCELLINTERRATHONCOV: CellId=1; //Deactivating Inter-RAT Handover Based on Load MOD UCELLLDR: CellId=1, DlLdrFourthAction=NoAct, DlLdrFifthAction=NoAct, UlLdrFourthAction=NoAct, UlLdrFifthAction=NoAct; SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-0&HO_INTER_RAT_PS_OUT_SWITCH-0;
Issue 02 (2011-07-11)
154-3
155 Configuring DRD Introduction Package
155
Prerequisite
l l l
Configuring DRD Introduction Package
This section describes how to activate, verify, and deactivate the optional feature WRFD-020400 DRD Introduction Package.
Context
This feature supports co-coverage inter-frequency or inter-RAT directed retries and redirection. This feature consists of the following features: l l l l WRFD-02040001 Intra System Direct Retry WRFD-02040002 Inter System Direct Retry WRFD-02040003 Inter System Redirect WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup
Procedure
l For the procedures for activating, verifying, and deactivating the preceding features, see the following sections: 156 Configuring Intra System Direct Retry 157 Configuring Inter System Direct Retry 158 Configuring Inter-System Redirect 159 Configuring Traffic Steering and Load Sharing During RAB Setup ----End
156 Configuring Intra System Direct Retry
156
Prerequisite
l l
Configuring Intra System Direct Retry
This section describes how to activate, verify, and deactivate the optional feature WRFD-02040001 Intra System Direct Retry.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-020400 DRD Introduction Package must be configured before this feature is activated.
Context
This feature supports inter-RAT directed retries during RRC connection or radio resource bearer (RAB) assignment.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Direct retry switch to DR_RRC_DRD_SWITCH, DR_RAB_SING_DRD_SWITCH, and DR_RAB_COMB_DRD_SWITCH. Run the BSC6900 MML command SET UDRD. In this step, turn on the RNC-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, Measurement-Based DRD Switch, and Device Type Steering DRD Switch. Optional: Run the BSC6900 MML command MOD UCELLDRD. In this step, turn on the cell-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, and Device Type Steering DRD Switch.
2.
3.
Issue 02 (2011-07-11)
156 Configuring Intra System Direct Retry

NOTE
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter settings take effect.
Verification Procedure 1. Method 1: Verifying this feature during RRC connection setup (1) Start Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive service. (2) The UE sends an RRC_RRC_CONNECT_REQ message from cell 1 to the BSC6900. The BSC6900 sends the UE an RRC_RRC_CONN_SETUP message containing the scrambling code of cell 2. (3) The UE sends an RRC_RRC_CONNECT_SETUP_CMP message from cell 2 to the BSC6900. This indicates that this feature has been activated. 2. Method 2: Verifying this feature during radio bearer (RB) setup (1) Start Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive service. (2) The BSC6900 sends an RRC_RB_SETUP message from cell 1 to the UE. The UE sends an RRC_RB_SETUP_CMP message from cell 2 to the BSC6900. If the service is set up successfully in cell 2 and the data transmission is normal, this feature has been activated.
Deactivation Procedure 1. 2. Run the BSC6900 MML command SET UDRD to turn off the RNC-level switches. Optional: Run the BSC6900 MML command MOD UCELLDRD to turn off the cell-level switches.
----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, ULLdbDRDSwitchDcHSDPA=ON, BasedOnMeasHRetryDRDSwitch=ON, DPGDRDSwitch=ON; MOD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, DPGDRDSwitch=ON; //Deactivating Intra System Direct Retry SET UDRD: ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, BasedOnMeasHRetryDRDSwitch=OFF, DPGDRDSwitch=OFF; MOD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, DPGDRDSwitch=OFF;
156-2
Issue 02 (2011-07-11)
157 Configuring Inter System Direct Retry
157
Prerequisite
l l
Configuring Inter System Direct Retry
This section describes how to activate, verify, and deactivate the optional feature WRFD-02040002 Inter System Direct Retry.
Context
This feature supports inter-RAT directed retries during RAB assignment.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Direct retry switch to DR_RAB_SING_DRD_SWITCH, DR_RAB_COMB_DRD_SWITCH, and DR_INTER_RAT_DRD_SWITCH. Run the BSC6900 MML command SET UDRD. In this step, set the RNC-level parameter Max inter-RAT direct retry number to a value other than zero, and turn on the following RNC-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, MeasurementBased DRD Switch, and Device Type Steering DRD Switch. Optional: Run the BSC6900 MML command MOD UCELLDRD. In this step, set the cell-level parameter Max inter-RAT direct retry number to a value other than zero. Turn on the following cell-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code
2.
3.
Issue 02 (2011-07-11)
157 Configuring Inter System Direct Retry
Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, and Device Type Steering DRD Switch.
NOTE
Verification Procedure 1. 2. Start Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive service. In the Uu Interface Trace dialog box, view the following procedure: (1) The core network (CN) sends a RAB_ASSIGNMENT_REQ message to the BSC6900. (2) The BSC6900 responds to the CN with a RAB_ASSIGNMENT_RSP message containing the cause value "direct retry." (3) The BSC6900 sends the CN a RELOCATION REQUIRED message containing the cause value "direct retry."
Deactivation Procedure 1. 2. Run the BSC6900 MML command SET UDRD. In this step, set Max Inter-RAT direct retry number to 0. Turn off the RNC-level switches. Optional: Run the BSC6900 MML command MOD UCELLDRD. In this step, set Max inter-RAT direct retry number to 0. Turn off the cell-level switches.
----End
Example
//Activating Inter System Direct Retry SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1&DR_RAB_COMB_DRD_SWITCH-1&DR_INTER_RAT_D RD_SWITCH; SET UDRD: DRMaxGSMNum=3, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, BasedOnMeasHRetryDRDSwitch=ON, DPGDRDSwitch=ON; MOD UCELLDRD: CellId=11, DRMaxGSMNum=3, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, DPGDRDSwitch=ON; //Deactivating Inter System Direct Retry SET UDRD: DRMaxGSMNum=0, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, BasedOnMeasHRetryDRDSwitch=OFF, DPGDRDSwitch=OFF; MOD UCELLDRD: CellId=11, DRMaxGSMNum=0, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, DPGDRDSwitch=OFF;
157-2
Issue 02 (2011-07-11)
158 Configuring Inter-System Redirect
158
Prerequisite
l l
Configuring Inter-System Redirect
This section describes how to activate, verify, and deactivate the optional feature WRFD-02040003 Inter System Redirect.
Context
This feature allows inter-system redirection during RRC connection setup.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Direct Retry Switch to DR_RRC_DRD_SWITCH. Run the BSC6900 MML command SET UDRD. In this step, set ConnectFailRrcRedirSwitch to Allowed_To_Inter_RAT. Start Uu Interface Trace on the BSC6900 LMT. Use a UE to initiate an RRC connection setup request. The following procedure is traced on the Uu interface: (1) The UE sends an RRC_SETUP_REQ message. (2) The BSC6900 responds with an RRC_CONN_REJ message, carrying GSMTargetCellInfo in the IE redirectioninfo. l
Issue 02 (2011-07-11)
158 Configuring Inter-System Redirect
1. ----End
Run the BSC6900 MML command SET UDRD. In this step, set RRC redirect switch to OFF or Only_To_Inter_Frequency.
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;
158-2
Issue 02 (2011-07-11)
159 Configuring Traffic Steering and Load Sharing During RAB Setup
159
Prerequisite
l l
Configuring Traffic Steering and Load Sharing During RAB Setup
This section describes how to activate, verify, and deactivate the optional feature WRFD-02040004 Service Steering and Load Sharing During RAB Setup.
Context
With this feature, service steering and load sharing among different frequencies or bands are implemented during RAB setup based on the service type and cell load.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command ADD UINTERFREQNCELL. In this step, add an inter-frequency cell by setting the related parameters according to the network plan. Run the BSC6900 MML command ADD USPG. In this step, add a service priority group and set the service priority of each type of service according to the network plan. Run the BSC6900 MML command MOD UCELLSETUP. In this step, set the cell service priority by setting the related parameters according to the network plan. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Direct Retry Switch to DR_RAB_SING_DRD_SWITCH. Run the BSC6900 MML command SET UDRD. In this step, turn on Service differential drd switch and Measurement-Based DRD Switch.
3. 4. 5.
Issue 02 (2011-07-11)
159 Configuring Traffic Steering and Load Sharing During RAB Setup
Verification Procedure 1. 2. Start Uu interface tracing on the BSC6900 LMT. Use a UE in a cell to initiate a PS interactive service. This cell carries low-priority services. The target inter-frequency neighboring cell has light load and carries highpriority services. In the Uu Interface Trace dialog box, view the following procedure: After the UE in a cell sends an RRC_RB_SETUP_CMP message, the BSC6900 sends an RRC_PH_CH_RECFG message to the UE. The UE responds with an RRC_PH_CH_RECFG_CMP message. The BSC6900 enters the compressed mode. The UE in periodical mode sends an RRC_MEAS_CTRL message to the BSC6900 to measure the signal quality of the target cell. The BSC6900 sends the UE an RRC_RB_RECFG message containing the primary scrambling code and frequency of the inter-frequency neighboring cell. The UE sends an RRC_RB_RECFG_CMP message from the inter-frequency neighboring cell.
Deactivation Procedure 1. Run the BSC6900 MML command SET UDRD. In this step, turn off Service differential drd switch and Measurement-Based DRD Switch.
----End
Example
//Activating Service 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; SET UDRD: ServiceDiffDrdSwitch=ON, BasedOnMeasHRetryDRDSwitch=ON; //Deactivating Service Steering and Load Sharing During RAB Setup SET UDRD: ServiceDiffDrdSwitch=OFF, BasedOnMeasHRetryDRDSwitch=OFF;
159-2
Issue 02 (2011-07-11)
160 Configuring Inter-RAT Redirection Based on Distance
160
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-020400 DRD Introduction Package has been configured before this feature is activated.
Context
If a UE initiates a CS voice call with a long distance to the antenna of a 3G cell, the UE may experience call drops when the UE moves out of the pilot polluted area. To solve this problem, the RAN redirects a UE to a GSM cell based on the distance threshold when the UE initiates an RRC connection setup request.
Procedure
l Activation Procedure 1. This feature can be activated by using either of the following methods according to the feature area: To activate this feature in the entire BSC6900, run the BSC6900 MML command SET UDISTANCEREDIRECTION to set the BSC6900-level parameters. Set Redirection Switch to ON. Set Propagation delay threshold as specified in 3GPP TS 25.433 Set Redirection Factor Of LDR and Redirection Factor Of Normal to appropriate values based on the network plan. To activate this feature in a cell, run the BSC6900 MML command ADD UCELLDISTANCEREDIRECTION to set the cell-level parameters.
Set Redirection Switch to ON. Set Propagation delay threshold as specified in 3GPP TS 25.433. Set Redirection Factor Of LDR and Redirection Factor Of Normal to appropriate values based on the network plan. l Verification Procedure 1. Initiate Uu interface message tracing on the BSC6900 LMT, as shown in Figure 160-1.
2.
Simulate a scenario where pilot pollution occurs. Place the UE in a place where the UE is far away from the NodeB and pilot signals are strong. Then, use the UE to establish a CS voice call. Check the messages traced on the Uu interface. As shown in Figure 160-2, if the RRC CONNECTION REJECT message contains the information element (IE) GSM-Targetcellinfo, the RAN has redirected the UE to the GSM network, and this feature has been activated. If the RRC CONNECTION REJECT message does not contain the IE GSMTargetcellinfo, this feature is not activated.
3.
160-2
Issue 02 (2011-07-11)
Figure 160-2 GSM-Targetcellinfo IE
Deactivation Procedure 1. This feature can be deactivated by using either of the following methods according to the feature area: To deactivate this feature in the entire BSC6900, run the BSC6900 MML command SET UDISTANCEREDIRECTION. In this step, set Redirection Switch to OFF. To deactivate this feature in a cell, run the BSC6900 MML command MOD UCELLDISTANCEREDIRECTION. In this step, set Redirection Switch to OFF.
----End
Example
//Activating Inter-RAT Redirection Based on Distance //Activating this feature in the entire BSC6900 SET UDISTANCEREDIRECTION: RedirSwitch=ON, DelayThs=100, RedirFactorOfLDR=70, RedirFactorOfNorm=60; //Activating this feature in a specified cell ADD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=ON, DelayThs=100, RedirFactorOfLDR=80, RedirFactorOfNorm=60; //Deactivating Inter-RAT Redirection Based on Distance //Deactivating this feature in the entire BSC6900 SET UDISTANCEREDIRECTION: RedirSwitch=OFF; //Deactivating this feature in a specified cell MOD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=OFF;
Issue 02 (2011-07-11)
160-3
161 Configuring Measurement-based Direct Retry
161
Prerequisite
l l
Configuring Measurement-based Direct Retry
This section describes how to activate, verify and deactivate the optional feature WRFD-020402 Measurement based Direct Retry.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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.
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, improving the network performance.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command ADD UCELLMBDRINTERFREQ, turn on the switch of Cell-Oriented inter-frequency measurement MBDR Switch. Run the BSC6900 MML command ADD UCELLMBDRINTERRAT, turn on the switch of Cell-Oriented inter-RAT measurement MBDR Switch. Run the BSC6900 MML command ADD UINTERFREQNCELL, set the Flag of MBDR Cell to TRUE(send), according network planning to set the MBDR Cell Periority.
l
Issue 02 (2011-07-11)
161 Configuring Measurement-based Direct Retry
1.
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 //Turn on the switch of Cell-Oriented inter-frequency measurement ADD UCELLMBDRINTERFREQ: CellId=1, InterFreqActiveType=CSAMR_INTERFREQ-1&CSNONAMR_INTERFREQ-1;&PSR99_INTERFR EQ-1;&PSHSPA_INTERFREQ-1; InterFreqReportMode=EVENT_TRIGGER; //Turn on the switch of Cell-Oriented inter-RAT measurement ADD UCELLMBDRINTERRAT: CellId=1, InterRatActiveType=CSAMR_INTERRAT-1; //Set the Flag of MBDR Cell to TRUE(send), according network planning to set the MBDR Cell Periority ADD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=2, NCellId=2, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE, NPrioFlag=FALSE, MBDRFlag=TRUE, MBDRPrio=2, InterNCellQualReqFlag=FALSE; //Deactivating Measurement based Direct Retry MOD UCELLMBDRINTERFREQ: InterFreqActiveType=CSAMR_INTERFREQ-0&CSNONAMR_INTERFREQ-0;&PSR99_INTERFR EQ-0;&PSHSPA_INTERFREQ-0;
161-2
Issue 02 (2011-07-11)
162 Configuring Enhanced Fast Dormancy
162
Prerequisite
l l l
Configuring Enhanced Fast Dormancy
This section describes how to activate, verify, and deactivate the optional feature WRFD-020500 Enhanced Fast Dormancy.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. The license can be activated by performing the following operation: Run the SET LICENSE command. In this step, set Fast Dormancy Enhancementper PS Active User to an appropriate value.
Other Prerequisites When the network is a service-layered network as follows and RSVDBIT1_BIT29 in the SET URRCTRLSWITCH command has been set to 0, Wait RB reconfiguration response timer and RL restoration timer in the SET USTATETIMER command are set to 11000 and 15000 respectively. Frequency F1 carries R99 services. Frequency F2 carries HSPA services. F2 cells are barred, and all users camp on F1 cells.
Context
As the number of smart UEs keeps increasing in mobile networks, the networks face signaling storms produced by these UEs. With rich experience in network optimization, Huawei provides a comprehensive end-to-end solution to respond to network challenges based on network characteristics. This feature is a component of the comprehensive solution. Deploying this feature only cannot solve the signaling storm problem produced by smart UEs. Operators should use this feature together with professional services to optimize the quality of service of the entire network.
CAUTION
l Consult Huawei engineers about the comprehensive solution to obtain professional technical support. l Huawei engineers will recommend appropriate parameter settings for this feature based on the network conditions. l Do not configure the parameters related to this feature without Huawei professional technical support. Inappropriate parameter settings may lead to network failures. Always on line can be provided for PS services of intelligent UEs to improve user experience. Always on line, however, will increase the power consumption of intelligent UEs. To prolong UE battery life, the Enhanced Fast Dormancy feature is introduced. When there is no PS data transfer, the UE will send a signaling connection release indication (SCRI) message to request the BSC6900 to release the RRC connection and move the UE state to idle mode, CELL_PCH, or URA_PCH. If this feature is not enabled, the BSC6900 will move the UE state to idle mode after the BSC6900 receives an SCRI message from the UE or the UE inactivity timer expires. If UEs are frequently switched between RRC connection states and idle mode, signaling storms occur. If this feature is enabled, the BSC6900 will move the UE to the CELL_PCH or URA_PCH state instead of the IDLE mode under either of the following conditions, reducing signaling processing costs: l l The BSC6900 receives an SCRI message from the UE. The CELL_FACH/CELL_DCH inactivity timer on the BSC6900 expires.
Procedure
l Activation Procedure 1. Run the MML commands ADD TRMFACTOR and MOD ADJMAP to change the Iu-PS activity factor. The recommended value of the Iu-PS activity factor is 10%. If the configured Iu-PS activity factor is smaller than 10%, retain the configured value.
NOTE
After this feature is enabled, the number of UEs in the CELL_PCH or URA_PCH state increases sharply. UEs in the CELL_PCH or URA_PCH state consume a large number of Iu-PS bandwidth resources although they do not transmit any data. Adjusting the Iu-PS activity factor can prevent PS service admission failures due to the increase in the number of UEs in the CELL_PCH or URA_PCH state.
CAUTION
The Iu-PS activity factor of all services must be set to an appropriate value. Otherwise, a large number of PS service setups fail, and the CPU usage of the SPU boards increases sharply. Modifying the Iu-PS activity factor does not bring a negative effect to the entire network. 2. Run the BSC6900 MML command SET URRCTRLSWITCH to enable the feature Enhanced Fast Dormancy at the BSC6900-level.
162-2
3.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable cell update during CS service setup. In this step, deselect the RSVDBIT1_BIT21 check box under the parameter Reserved Parameter 1.
NOTE
After this feature is enabled, the number of CELL_DCH-to-CELL_FACH (D2F) procedures performed increases. If a CS service is initiated after the UE performs a D2F procedure, a cell update procedure may be initiated during the CS service setup. The switch RSVDBIT1_BIT21 specifies whether to allow cell update during CS service setup. When this switch is turned off, cell update is allowed during CS service setup.
4.
Run the BSC6900 MML command SET URRCTRLSWITCH to enable the state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by FACH congestion. In this step, deselect the RSVDBIT1_BIT20 check box under the parameter Reserved Parameter 1. Run the BSC6900 MML command SET URRCTRLSWITCH to disable the state transition from CELL_DCH to CELL_PCH. In this step, deselect the RSVDBIT1_BIT29 check box under the parameter Reserved Parameter 1.
NOTE
5.
The switch RSVDBIT1_BIT29 specifies whether to allow the state transition from CELL_DCH to CELL_PCH. When this switch is turned on, the state transition from CELL_DCH to CELL_PCH is allowed. When this switch is turned off, the state transition from CELL_DCH to CELL_PCH is not allowed. After this feature is enabled, the FACH will carry a large amount of data, which may lead to FACH congestion. Therefore, it is recommended that a new SCCPCH be added.
6.
Run the BSC6900 MML command SET UPSINACTTIMER to set the value of the CELL_DCH inactivity timer. The recommended value of the CELL_DCH inactivity timer is 4 seconds. Run the BSC6900 MML command SET UPSINACTTIMER to set the value of the CELL_FACH inactivity timer. The recommended value of the CELL_FACH inactivity timer is 10 seconds. Run the BSC6900 MML command SET UPSINACTTIMER to set the value of the CELL_PCH inactivity timer. The recommended value of the CELL_PCH inactivity timer is 360 seconds. Run the BSC6900 MML command SET UUESTATETRANS. In this step, set Fast Dormancy User FACH/E_FACH2DCH/HSPA 4A Threshold to D1k.
7.
8.
9.
10. Run the BSC6900 MML command SET URRCTRLSWITCH to enable the Type Allocation Code (TAC) match function. 11. Optional: Run the BSC6900 MML command ADD UIMEITAC to add the IMEI TACs of smart UEs to the whitelist. In this step, set Fast Dormancy Switch to ON. The BSC6900 compares the queried UE IMEI with the configured IMEI TAC and then performs operations as follows:
Issue 02 (2011-07-11)
162-3
Table 162-1 Processing procedure after the comparison Setting of FD_TAC_MAT CH_SWITCH in the MML command SET URRCTRLSWI TCH (RNC level) ON Setting of IMEI TAC in the MML command ADD UIMEITAC Setting of Fast Dormancy Switch in the MML command ADD UIMEITAC (UE level) ON Processing Procedure
Configured
The BSC6900 enables the Enhanced Fast Dormancy feature for the UEs with a matched TAC. The BSC6900 enables the Enhanced Fast Dormancy feature for the UEs complying with 3GPP Release 5 or later. The BSC6900 does not enable this feature for the UEs that are added to the IMEI TAC list but not contained in the blacklist. You can set a procedure for specified UEs by running the MML command ADD UIMEITAC. For example, you can configure UEs of a certain type to support the CELL_DCH-toCELL_FACH-toCELL_PCH procedure rather than the CELL_DCH-toCELL_PCH procedure.
OFF
Configured
ON
OFF
Not configured
Not involved
The BSC6900 enables the Enhanced Fast Dormancy feature for the UEs complying with 3GPP Release 5 or later.
162-4
Issue 02 (2011-07-11)
Setting of FD_TAC_MAT CH_SWITCH in the MML command SET URRCTRLSWI TCH (RNC level) OFF
Setting of IMEI TAC in the MML command ADD UIMEITAC
Setting of Fast Dormancy Switch in the MML command ADD UIMEITAC (UE level) OFF
Processing Procedure
Configured
The BSC6900 does not enable the Enhanced Fast Dormancy feature for UEs with a matched TAC.
12. Optional: Run the BSC6900 MML command MOD UCELLALGOSWITCH to turn on the switch for the cell-level enhanced fast dormancy feature.
NOTE
By default, this switch is turned on.
Verification Procedure 1. Run the BSC6900 MML command DSP LICUSAGE to query the state of the license for this feature. If the result shown in Figure 162-1 is returned, the license for this feature has been configured.
Figure 162-1 Status of the Enhanced Fast Dormancy license
2. 3.
Initiate Uu interface message tracing on the BSC6900 LMT. Use a smart UE to set up a PS service in the CELL_DCH state. For example, use the UE to browse a Web page. If the RRC_RB_SETUP message shown in Figure 162-2 is traced, the UE is in the CELL_DCH state.
Figure 162-2 UE in the CELL_DCH state
4.
Keep the UE in idle mode for a period. For example, perform no operation for four seconds after a Web page is opened.
Issue 02 (2011-07-11)
If the RRC_RB_RECFG message shown in Figure 162-3 is traced, the UE will move from the CELL_DCH state to the CELL_FACH state and then to the CELL_PCH state. Figure 162-3 State transition to the CELL_PCH state
5.
Use the UE to continue PS services such as web page browsing. Cell update or channel reconfiguration occurs. Check the RRC_CELL_UPDATE message as shown in Figure 162-4 and Figure 162-5.
Figure 162-4 Cell update
Figure 162-5 Channel reconfiguration
Deactivation Procedure To deactivate this feature, you need to restore the values of all related function switches and parameters to their original values. For details, see the script in the example.
162-6
Issue 02 (2011-07-11)

NOTE
If this feature must be deactivated when the SPUa or SPUb board is being reset, do as follows: 1. Run the BSC6900 MML command SET CFGDATAINEFFECTIVE to set the subrack to ineffective mode. 2. Run the MML commands to deactivate this feature. For details, see the script in the example. 3. Run the BSC6900 MML command SET CFGDATAEFFECTIVE to set the subrack to effective mode.
----End
Example
//Activating Fast Dormancy Enhancement //Activating the license controlling Fast Dormancy Enhancement SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FastDormancyEnhancement=141120; //Enabling the Enhanced Fast Dormancy feature at the BSC6900 level SET URRCTRLSWITCH: PROCESSSWITCH=FAST_DORMANCY_SWITCH-1; //Enabling cell update during CS service setup SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT21-0; //Enabling the state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by FACH congestion SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT20-0; //Disabling the state transition from CELL_DCH to CELL_PCH triggered by UEs SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT29-0; //Setting the value of the CELL_DCH inactivity timer to 4 seconds SET UPSINACTTIMER: PsInactTmrForFstDrmDch=4; //Setting the value of the CELL_FACH inactivity timer to 10 seconds SET UPSINACTTIMER: PsInactTmrForFstDrmFach=10; //Setting the value of the CELL_PCH inactivity timer to 360 seconds SET UPSINACTTIMER: PsInactTmrForPreFstDrm=360; //Setting the traffic threshold of event 4A during the state transition from CELL_FACH to CELL_DCH to D1k SET UUESTATETRANS: FastDormancyF2DHTvmThd=D1k; //Enabling the IMEI Type Allocation Code (TAC) match function SET URRCTRLSWITCH: PROCESSSWITCH=FD_TAC_MATCH_SWITCH-1; //Adding the IMEI TACs of smart UEs to the whitelist ADD UIMEITAC: TAC_FUNC=Fast_Dormancy, TAC=01177600, Description="Smart Phone", FastDormancy=ON; //Enabling the Enhanced Fast Dormancy feature at the cell level ADD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=FAST_DORMANCY_ADCTRL-1; //Deactivating Fast Dormancy Enhancement //Disabling the Enhanced Fast Dormancy feature at the BSC6900 level SET URRCTRLSWITCH: PROCESSSWITCH=FAST_DORMANCY_SWITCH-0;
Issue 02 (2011-07-11)
162-7
//Setting the value of the CELL_DCH inactivity timer to 4 seconds SET UPSINACTTIMER: PsInactTmrForFstDrmDch=4; //Setting the value of the CELL_FACH inactivity timer to 10 seconds SET UPSINACTTIMER: PsInactTmrForFstDrmFach=10; //Setting the value of the CELL_PCH inactivity timer to 360 seconds SET UPSINACTTIMER: PsInactTmrForPreFstDrm=360; //Setting the traffic threshold of event 4A during the state transition from CELL_FACH to CELL_DCH to D1k SET UUESTATETRANS: FastDormancyF2DHTvmThd=D1k; //Enabling the IMEI Type Allocation Code (TAC) match function SET URRCTRLSWITCH: PROCESSSWITCH=FD_TAC_MATCH_SWITCH-1;
162-8
Issue 02 (2011-07-11)
163 Configuring Cell Barring
163
Prerequisite
l l l Dependencies on Hardware License
Configuring Cell Barring
This section describes how to activate, verify, and deactivate the optional feature WRFD-021102 Cell Barring.
This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. The license controlling this feature has been activated.
Context
If the cell barring feature is enabled, cells can be barred either automatically or manually to facilitate operators' maintenance when the cells are running improperly.
Procedure
l Activation Procedure Setting automatic cell barring 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select SYS_INFO_UPDATE_FOR_IU_RST and BARRED_CELL_FOR_CSDOMAIN_RST from the Process switch dropdown list. Run the BSC6900 MML command SET UIUTIMERANDNUM to enable interruption protection by specifying CN protection timer. Run the BSC6900 MML command ADD URNCALLCELLBLK to configure parameters related to barring of all cells served by an RNC in a network. Run the BSC6900 MML command ADD UCNOPALLCELLBLK to configure parameters related to operator-specific barring of all cells in a network.
2.
Setting manual cell barring 1. 2. l

Issue 02 (2011-07-11)
Block the PS domain or the PS domain is disconnected, which prevents UEs from being admitted to PS services. Perform the following steps to verify whether this feature is activated:
NOTE
Perform the same verification procedure when blocking the CS domain or the CS domain is disconnected.
1. 2.
Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_SYS_INFO_TYPE1. View whether information element (IE) information of the PS domain is contained in the traced messages. Expected result: PS domain IE information is not contained, as shown in Figure 163-1.
Block CS and PS domains, CS and PS domains are disconnected, or block the CS domain and turn on BARRED_CELL_FOR_CSDOMAIN_RST. Perform the following steps to verify whether this feature is activated: 1. 2. Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_SYS_INFO_TYPE3. View whether IE information related to CS and PS domains is contained in the traced messages. Expected result: The IE information is not contained, as shown in Figure 163-2.
163-2
Issue 02 (2011-07-11)
Bar PS services of UEs served by an operator. Perform the following steps to verify whether this feature is activated:
NOTE
Perform the same verification procedure when barring CS services of UEs served by an operator.
1. 2.
Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_SYS_INFO_TYPE3. View whether IE information related to CS and PS domains is contained in the traced messages. Expected result: The IE information is not contained, as shown in Figure 163-3.
Issue 02 (2011-07-11)
163-3
Deactivation Procedure Deactivating automatic cell barring 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, deselect SYS_INFO_UPDATE_FOR_IU_RST and BARRED_CELL_FOR_CSDOMAIN_RST from the Process switch dropdown list. Run the BSC6900 MML command RMV URNCALLCELLBLK to remove parameters related to barring of all cells served by an RNC in a network. Run the BSC6900 MML command RMV UCNOPALLCELLBLK to remove parameters related to operator-specific barring of all cells in a network.
Deactivating manual cell barring 1. 2. ----End
Example
//Activating Cell Barring SET URRCTRLSWITCH: PROCESSSWITCH SET URRCTRLSWITCH: PROCESSSWITCH SET UIUTIMERANDNUM: CnOpIndex=0, //Deactivating Cell Barring SET URRCTRLSWITCH: PROCESSSWITCH SET URRCTRLSWITCH: PROCESSSWITCH = SYS_INFO_UPDATE_FOR_IU_RST-1; = BARRED_CELL_FOR_CSDOMAIN_RST-1; CNId=0, StateIndTmr=20000; = SYS_INFO_UPDATE_FOR_IU_RST-0; = BARRED_CELL_FOR_CSDOMAIN_RST-0;
163-4
Issue 02 (2011-07-11)
164 Configuring 3G/2G Common Load Management
164
Prerequisite
l
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.
Dependencies on Hardware The CN should support this feature. The BSS should support this feature.
Dependencies 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
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. In this step, select HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH through the HandOver Switch.
Issue 02 (2011-07-11)
164 Configuring 3G/2G Common Load Management
2.
Run the BSC6900 MML command SET UINTERRATHONCOV to enable the 3G/ 2G common load management function. In this step, select the Send Load Info to GSM Ind and NCOV Reloc Ind Based on GSM Cell Load. 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.
NOTE
3. l
2.
Consult Huawei engineers about the verification solution to obtain professional technical support.
Deactivation Procedure 1. 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.
----End
Example
//Activating 3G/2G Common Load Management SET UCORRMALGOSWITCH: HoSwitch=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;
164-2
Issue 02 (2011-07-11)
165 Configuring RAB Quality of Service Renegotiation over Iu Interface
165
Prerequisite
l l l
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.
Dependencies on Hardware The NEs in the core network must support selective configuration of the maximum bit rate (MBR) and guaranteed bit rate (GBR). Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
This feature enables the BSC6900 to initiate Iu renegotiation on the MBR and GBR of PS realtime services to reduce the rate of real-time services.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the cell-level LDR algorithm. In this step, set Cell LDC algorithm switch to UL_UU_LDR, DL_UU_LDR, and CELL_CREDIT_LDR. Run the BSC6900 MML command MOD UNODEBALGOPARA to enable the NodeB-level LDR algorithm. In this step, set NodeB LDC algorithm switch to IUB_LDR, LCG_CREDIT_LDR, and NODEB_CREDIT_LDR. Run the BSC6900 MML command MOD UCELLLDM to set the cell-level LDR trigger threshold. In this step, set UL/DL LDR Trigger threshold and DL State Trans Hysteresis threshold according to the network plan. Run the BSC6900 MML command MOD UNODEBLDR to set the NodeB-level LDR credit spreading factor (SF) reserved threshold. In this step, set Ul LDR Credit
2.
3.
4.
Issue 02 (2011-07-11)
165 Configuring RAB Quality of Service Renegotiation over Iu Interface
SF reserved threshold and Dl LDR Credit SF reserved threshold according to the network plan. 5. Run the BSC6900 MML command MOD UCELLLDR to set the NodeB credit LDR threshold for the local cell. In this step, set Ul LDR Credit SF reserved threshold and DL LDR Credit SF reserved threshold according to the network plan. Run the BSC6900 MML command SET ULDCPERIOD. In this step, set LDR period timer length according to the network plan. Run the BSC6900 MML command MOD UCELLLDR to enable QoS renegotiation on real-time services. In this step, set DL LDR first action to QOSRENEGO. Establish a PS streaming service. Trigger LDR in the cell according to the cell LDR threshold specified in the activation procedure. If RAB MODIFY REQUEST is traced on the Iu interface, this feature has been activated. Run the BSC6900 MML command MOD UCELLALGOSWITCH to disable the cell-level LDR algorithm. In this step, deselect UL_UU_LDR, DL_UU_LDR, and CELL_CREDIT_LDR from the Cell LDC algorithm switch drop-down list box. Run the BSC6900 MML command MOD UNODEBALGOPARA to disable the NodeB-level LDR algorithm. In this step, deselect IUB_LDR, LCG_CREDIT_LDR, and NODEB_CREDIT_LDR from the NodeB LDC algorithm switch drop-down list box.
6. 7. l
2.
----End
Example
/*Activating RAB Quality of Service Renegotiation over Iu Interface*/ //Enabling the cell-level LDR algorithm MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch= UL_UU_LDR-1&DL_UU_LDR-1&CELL_CREDIT_LDR-1; //Enabling the NodeB-level LDR algorithm MOD UNODEBALGOPARA: NodeBName="NODEB1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1; //Enable QoS renegotiation on real-time services MOD UCELLLDR: CellId=111, DlLdrFirstAction=QoSRenego; /*Deactivating RAB Quality of Service Renegotiation over Iu Interface*/ //Disabling the cell-level LDR algorithm MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch= UL_UU_LDR-0&DL_UU_LDR-0&CELL_CREDIT_LDR-0; //Disabling the NodeB-level LDR algorithm MOD UNODEBALGOPARA: NodeBName="NODEB1", NodeBLdcAlgoSwitch=IUB_LDR-0&NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR-0;
165-2
Issue 02 (2011-07-11)
166 Configuring Rate Negotiation at Admission Control
166
Prerequisite
l l l l
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.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites For Iu QoS negotiation, the CN nodes must support this feature. For RAB rate reduction, the CN nodes do not need to support this feature.
Context
This feature supports the procedures for Iu QoS negotiation and RAB rate reduction.
Procedure
l Activation Procedure Activating QoS negotiation 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH, and set PS rate negotiation switch to PS_BE_IU_QOS_NEG_SWITCH and PS_STREAM_IU_QOS_NEG_SWITCH. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH, and set PS rate negotiation switch to PS_RAB_DOWNSIZING_SWITCH.
Activating RAB rate reduction 1.
Issue 02 (2011-07-11)
Verification Procedure Verifying QoS negotiation 1. 2. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query the activation result. Start Iu message tracing on the BSC6900 LMT and establish a PS service, as shown in Figure 166-1.
Figure 166-1 Iu message tracing
3.
View the RANAP_RAB_ASSIGNMENT_REQ message. If it contains the IE "altRAB-Parameters", the CN supports Iu QoS negotiation, as shown in Figure 166-2. Figure 166-2 RANAP_RAB_ASSIGNMENT_REQ message on the Iu interface
166-2
Issue 02 (2011-07-11)
Verifying RAB rate reduction 1. 2. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query the activation result. Start Iu message tracing on the BSC6900 LMT and establish a PS service, as shown in Figure 166-3.
Figure 166-3 Iu message tracing
3.
View the RANAP_RAB_ASSIGNMENT_RESP message. If it contains the IE "ass-RAB-Parameters", rate negotiation at admission control takes effect, and the MaxBitrate is the data rate negotiated by the RNC, as shown in Figure 166-4. Figure 166-4 RANAP_RAB_ASSIGNMENT_RESP message on the Iu interface
l
Issue 02 (2011-07-11)
Deactivating QoS negotiation 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect DRA_DCCC_SWITCH from the Dynamic Resource Allocation Switch drop-down list box, and deselect PS_BE_IU_QOS_NEG_SWITCH and PS_STREAM_IU_QOS_NEG_SWITCH from the PS rate negotiation switch drop-down list box. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect DRA_DCCC_SWITCH from the Dynamic Resource Allocation Switch drop-down list box, and deselect PS_RAB_DOWNSIZING_SWITCH from the PS rate negotiation switch drop-down list box.
Deactivating RAB rate reduction 1.
----End
Example
//Activating Rate Negotiation at Admission Control SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1, PsSwitch =PS_BE_IU_QOS_NEG_SWITCH-1&PS_STREAM_IU_QOS_NEG_SWITCH-1; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1, PsSwitch=PS_RAB_DOWNSIZING_SWITCH-1; //Deactivating Rate Negotiation at Admission Control SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-0, PsSwitch =PS_BE_IU_QOS_NEG_SWITCH-0&PS_STREAM_IU_QOS_NEG_SWITCH-0; SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-0, PsSwitch=PS_RAB_DOWNSIZING_SWITCH-0;
166-4
Issue 02 (2011-07-11)
167 Configuring Service Steering and Load Sharing in RRC Connection Setup
167
Prerequisite
l l
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.
Context
With this feature, service steering and load sharing among different frequencies, bands, or radio access technologies (RATs) can be achieved during radio resource control (RRC) connection setup based on the service type and cell load.
Procedure
NOTE
The adaptive multirate (AMR) service that is redirected to an inter-RAT cell during RRC connection setup is used as an example.
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the RRC directed retry decision (DRD) function. In this step, set Direct Retry Switch to DR_RRC_DRD_SWITCH. Run the BSC6900 MML command SET UREDIRECTION. In this step, set RNClevel Traffic Type to AMR and Redirection Switch to ONLY_TO_INTER_RAT. Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION. In this step, set cell-level Traffic Type to AMR and Redirection Switch to ONLY_TO_INTER_RAT.
2.
3.
Issue 02 (2011-07-11)
167 Configuring Service Steering and Load Sharing in RRC Connection Setup
NOTE
Verification Procedure 1. 2. Use a UE complying with the 3GPP Release 5 to send an RRC_SETUP_REQ message with the cause value "Originating Conversational Call." The BSC6900 responds with an RRC_CONN_REJ message. If "redirectioninfo" of the message contains "GSM-TargetCellInfo," this feature has been activated. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the RRC DRD function. Run the BSC6900 MML command SET UREDIRECTION. In this step, set Redirection Switch to an appropriate value to disable the RNC-level RRC DRD based on service steering. Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION. In this step, set Redirection Switch to an appropriate value to disable the cell-level RRC DRD based on service steering.
3.
----End
Example
/*Activating Service Steering and Load Sharing in RRC Connection Setup*/ /*Enabling the RRC DRD function*/ SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1; //Setting the RNC-level DRD switch SET UREDIRECTION: TrafficType=AMR, RedirSwitch=ONLY_TO_INTER_RAT, RedirFactorOfNorm=0, RedirFactorOfLDR=0, RedirBandInd=BAND1, ReDirUARFCNUplinkInd=FALSE, ReDirUARFCNDownlink=10713; //Setting the cell-level DRD switch MOD UCELLREDIRECTION: CellId=1, TrafficType=AMR, RedirSwitch=ONLY_TO_INTER_RAT, RedirFactorOfNorm=0, RedirFactorOfLDR=100, RedirBandInd=BAND1, ReDirUARFCNUplinkInd=FALSE, ReDirUARFCNDownlink=10563; /*Deactivating Service Steering and Load Sharing in RRC Connection Setup*/ //Disabling the RRC DRD function SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-0; //Setting the RNC-level DRD switch SET UREDIRECTION: TrafficType=PSHSPA, RedirSwitch=OFF; //Setting the cell-level DRD switch MOD UCELLREDIRECTION: CellId=100, TrafficType=PSHSPA, RedirSwitch=OFF;
167-2
Issue 02 (2011-07-11)
168 Configuring TCP Accelerator
168
Prerequisite
l l l l License
Configuring TCP Accelerator
This section describes how to activate, verify, and deactivate the optional feature WRFD-020123 TCP Accelerator.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. The license controlling this feature has been activated. Other Prerequisites Downlink TCP accelerator requires that the BSC6900 version is RAN11.0 or later. Uplink TCP accelerator requires that the BSC6900 version is RAN12.0 or later.
Context
The TCP Accelerator feature in RAN11.0 optimizes the data transmission performance in the downlink. Based on this feature in RAN11.0, RAN12.0 introduces the TCP Accelerator feature to optimize the data transmission in the uplink. In addition, the Acknowledgment (ACK) splitting technology, ACK splitting monitoring technology, and uplink data packet sequencing technology are adopted. These technologies aim at accelerating the slow start and restore processes during uplink data transmission, reducing the impact of packet loss on the performance of uplink TCP data transmission.
NOTE
Data configurations are required only at the BSC6900 to activate, verify, and deactivate this feature.
Procedure
Issue 02 (2011-07-11)
168-1
168 Configuring TCP Accelerator
1.
Run the BSC6900 MML command SET UDPUCFGDATA to turn on the TCP accelerator switch. In this step, select TPE_DOWNLINK_SWITCH or TPE_UPLINK_SWITCH from TPE switch according to the actual requirements. Run the BSC6900 MML command LST UDPUCFGDATA to check whether the TCP accelerator switch is turned on. If the switch is turned on, this feature has been activated. 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. Use a test terminal to upload a file of 200 KB to the FTP server. Then, compare the upload time taken before and after the TPE_UPLINK_SWITCH is turned on. Run the BSC6900 MML command SET UDPUCFGDATA to turn off the TCP accelerator switch. In this step, deselect TPE_DOWNLINK_SWITCH or TPE_UPLINK_SWITCH from TPE switch according to the actual requirements.
2.
3. l
----End
Example
//Activating TCP Accelerator Turning on the TCP accelerator switch at the RNC SET UDPUCFGDATA: TpeSwitch=TPE_DOWNLINK_SWITCH-1&TPE_UPLINK_SWITCH-1; //Deactivating TCP Accelerator Turning off the TCP accelerator switch at the RNC SET UDPUCFGDATA: TpeSwitch=TPE_DOWNLINK_SWITCH-0&TPE_UPLINK_SWITCH-0;
168-2
Issue 02 (2011-07-11)
169 Configuring Uplink Flow Control of User Plane
169
Prerequisite
l l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
The Uplink Flow Control of User Plane feature is a Huawei proprietary feature. This feature detects uplink packet loss for R99 services by using private information elements (IEs) on the Iub interface. In addition, this feature controls uplink traffic by sending Transport Format Combination Control messages. By doing this, this feature prevents uplink packet loss caused by lack of flow control, and increases transmission efficiency.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set Process switch to NODEB_PRIVATE_INTERFACE_SWITCH.
NOTE
NODEB_PRIVATE_INTERFACE_SWITCH controls all the functions that are achieved by using the private messages on the Iub interface. Turn on other related switches if flow control over the uplink user plane is required.
2. l
Issue 02 (2011-07-11)
Run the NodeB MML command SET R99FLOWCTRLSWTCH to turn on the celllevel switch for uplink user plane flow control.
1.
Start an Iub interface tracing task on the BSC6900 LMT, as shown in Figure 169-1. Figure 169-1 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 iE-Extensions in DCH-FDDInformationItem. If there is an IE trafficClass-Private, as shown in Figure 169-2, the feature at the BSC6900 has been activated.
169-2
Issue 02 (2011-07-11)
Figure 169-2 TrafficClass-Private
Deactivation Procedure 1. Run the NodeB MML command SET R99FLOWCTRLSWTCH to turn off the celllevel switch for uplink user plane flow control.
----End
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;
Issue 02 (2011-07-11)
169-3
170 Configuring Videophone Service Restriction
170
Prerequisite
l l l
Configuring Videophone Service Restriction
This section describes how to activate, verify, and deactivate the optional feature WRFD-020130 Videophone Service Restriction.
Context
This feature disables the videophone (VP) function of a cell through cell-level configurations to meet telecom operators' requirements for information security in restricted areas.
Procedure
l Activation Procedure 1. 2. 3. 4. l Run the BSC6900 MML command DEA UCELL to deactivate the cell. In this step, set Cell ID to an appropriate value. Run the BSC6900 MML command MOD UCELLSETUP. In this step, set Cell VP Limit Indicator to TRUE. Run the BSC6900 MML command ACT UCELLL to activate the cell. In this step, set Cell ID to an appropriate value. Run the BSC6900 MML command MOD UEXT3GCELL on another RNC that controls the neighboring cell. In this step, set Cell VP Limit Indicator to TRUE. Use two VP-capable UEs to camp on the same cell, and then use one UE to initiate a VP to the other UE. Initiate Iu Interface Trace on the BSC6900 LMT.
Issue 02 (2011-07-11)
170 Configuring Videophone Service Restriction
The BSC6900 sends an RANAP_RAB_ASSIGNMENT_RSP message to the CN. l Deactivation Procedure 1. 2. 3. 4. ----End Run the BSC6900 MML command DEA UCELL to deactivate the cell. In this step, set Cell ID to an appropriate value. Run the BSC6900 MML command MOD UCELLSETUP. In this step, set Cell VP Limit Indicator to FALSE. Run the BSC6900 MML command ACT UCELLL to activate the cell. In this step, set Cell ID to an appropriate value. Run the BSC6900 MML command MOD UEXT3GCELL on another RNC that controls the neighboring cell. In this step, set Cell VP Limit Indicator to FALSE.
Example
//Activating Videophone Service Restriction DEA UCELL: CellId=1111; MOD UCELLSETUP: CellId=1111, VPLimitInd=TRUE; ACT UCELL: CellId=1111; MOD UEXT3GCELL: NRncId=1, CellId=1111, VPLimitInd=TRUE; //Deactivating Videophone Service Restriction DEA MOD ACT MOD UCELL: CellId=1111; UCELLSETUP: CellId=1111, VPLimitInd=FALSE; UCELL: CellId=1111; UEXT3GCELL: NRncId=1, CellId=1111, VPLimitInd=FALSE;
170-2
Issue 02 (2011-07-11)
171 Configuring Active Queue Management (AQM)
171
Prerequisite
l l l
Configuring Active Queue Management (AQM)
This section describes how to activate, verify, and deactivate the optional feature WRFD-011502 Active Queue Management (AQM).
Context
The AQM feature can improve users feeling when HTTP and download services simultaneously exist.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the RNC-level AQM switch. In this step, select the Dynamic resource allocation switch check box under the parameter DRA_AQM_SWITCH. Initiate UE tracing on the BSC6900 LMT. In the displayed UE Trace dialog box, select the Debug Mode check box, as shown in Figure 171-1.
Issue 02 (2011-07-11)
171-1
171 Configuring Active Queue Management (AQM)
Figure 171-1 UE Trace dialog box
2.
Establish a BE service on the UE. Verify the value of the information element (IE) "ucAqmSwitch" contained in the message PdcpSetupInfo as follows: If the value of the IE "ucAqmSwitch" is 1, this feature has been activated. If the value of the IE "ucAqmSwitch" is 0, this feature is not activated.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the DRA_AQM_SWITCH check box under the parameter Dynamic resource allocation switch.
----End
Example
//Activating Active Queue Management (AQM) SET UCORRMALGOSWITCH: DraSwitch=DRA_AQM_SWITCH-1; //Deactivating Active Queue Management (AQM) SET UCORRMALGOSWITCH: DraSwitch=DRA_AQM_SWITCH-0;
171-2
Issue 02 (2011-07-11)
172 Configuring Quality Improvement for Subscribed Service
172
Prerequisite
l
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.
Dependencies on Hardware BTS3812E is configured with the Enhanced NodeB HSPA/HSPA+ supported Baseband processing and Interface unit (EBBI) or Enhanced NodeB HSPA supported Downlink Processing (EDLP) board. DBS3800 is configured with the Enhanced Base Band Card (EBBC) or Enhanced Base Band Card REV:d (EBBCd) board. DBS3900 or BTS3900 is configured with the WCDMA Baseband Process Unit REV:b (WBBPb) or WCDMA Baseband Process Unit REV:d (WBBPd) board.
Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Others Prerequisites Only BSC6900 supports this feature. The BSC6900 version is RAN12.0 or later. The NodeB software version is RAN12.0 or later.
Context
This feature enables BSC6900 to adjust the user scheduling priority by identifying the characteristics of IP data streams and modifying the initial Scheduling Priority Indicator (SPI) Weight of downlink services. The feature grants high scheduling priorities to specific services on which telecom operators focus, such as services from specific servers or http services. By doing this, the bandwidth required for processing the services is guaranteed.
In addition, the feature lowers the scheduling weight of some non-paying services that consume a large amount of bandwidth. By doing this, sufficient bandwidth is available for services with high scheduling priorities.
Procedure
l Activation Procedure 1. Set the initial SPI Weight on the BSC6900 LMT. If the license controlling the feature WRFD-020806 Differentiated Service Based on SPI Weight has been activated, run the BSC6900 MML command SET USPIWEIGHT. In this step, set the parameters Scheduling Priority Indicator and SPI Weight based on the actual network plan. If the license controlling the feature WRFD-020806 Differentiated Service Based on SPI Weight is not activated, run the BSC6900 MML command SET UFRC. In this step, set Default SPI Weight based on the actual network plan. 2. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select the NODEB_PRIVATE_INTERFACE_SWITCH check box under the parameter Process switch. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the DRA_IP_SERVICE_QOS_SWITCH check box under the parameter Dynamic Resource Allocation Switch. Run the BSC6900 MML command ADD UIPSERVICEQOS. In this step, set the parameters related to the Quality Improvement for Subscribed Service feature to appropriate values based on the network plan. Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set Service Priority Adjusting Coefficient to an appropriate value. When the resources (for example, resources on the air interface) are limited, activating this feature may increase the throughput of FTP services and shorten the network delay of HTTP services. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the DRA_IP_SERVICE_QOS_SWITCH check box under the parameter Dynamic Resource Allocation Switch.
3.
4.
5. l
----End
Example
//Activating Quality Improvement for Subscribed Service //Setting the initial SPI weight value if the license control switch for the feature WRFD-020806 Differentiated Service Based on SPI Weight is turned on SET USPIWEIGHT: SPI=4, SPIWEIGHT=10; //Setting the initial SPI weight value if the license control switch for the feature WRFD-020806 Differentiated Service Based on SPI Weight is not turned on SET UFRC: DefaultSPIWeight=10; //Turning on the switch for a NodeB private interface SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
172-2
Issue 02 (2011-07-11)
//Turning on the switch for the Quality Improvement for Subscribed Service feature SET UCORRMALGOSWITCH: DraSwitch=DRA_IP_SERVICE_QOS_SWITCH-1; //Setting the parameters related to the Quality Improvement for Subscribed Service feature ADD UIPSERVICEQOS: CnOpIndex=0, RecIndex=1, TrafficType=SPI, MatchType=IPAndPort, IPAddress="192.168.0.100", IPMask="255.255.255.255", PortNum=8080, ProtocolType=TCP, TrafficPriority=HIGH; //Setting the scheduling priority weight corresponding to high-priority services SET UDPUCFGDATA: ServPriAdjCoefHigh=100; //Deactivating Quality Improvement for Subscribed Service SET UCORRMALGOSWITCH: DraSwitch=DRA_IP_SERVICE_QOS_SWITCH-0;
Issue 02 (2011-07-11)
172-3
173 Configuring Optimization of R99 and HSUPA Users Fairness
173
Prerequisite
l
Configuring Optimization of R99 and HSUPA Users Fairness
This section describes how to activate, verify, and deactivate the optional feature WRFD-020131 Optimization of R99 and HSUPA Users Fairness.
Dependencies on Hardware The HBBI and HULP boards in the BTS3812E/BTS3812AE do not support this feature. To support this feature, the BTS3812E/BTS3812AE must be configured with the EBBI or EDLP board. The BBU3806 in the DBS3800 does not support this feature. To support this feature, the DBS3800 must be configured with the EBBC or EBBCd board. If the BBU3806C is configured, the EBBM board must be added. To support this feature, the 3900 series base stations must be configured with WBBPb or WBBPd boards. WBBPa boards in the 3900 series base stations do not support this feature.
Dependencies on Other Features The feature WRFD-010612 HSUPA Introduction Package must be configured before this feature is activated.
Context
In scenarios where R99 and HUSUPA users share the same TRX, this feature provides fair services for the two types of users and improves HSUPA user experience by considering R99 and HSUPA user satisfaction with throughput, that is, the ratio of effective rate to guaranteed bit rate (GBR).
Procedure
l Activation Procedure 1. To enable the algorithm switch for cell-level rate reduction for BE services based on R99 and HSUPA user fairness, run the BSC6900 MML command MOD
Issue 02 (2011-07-11)
UCELLALGOSWITCH with BE rate reduction switch based on fairness set to ON. 2. To set the common measurement period based on R99 and HSUPA user fairness, run the BSC6900 MML command SET ULDCPERIOD with Fairness period timer length set to an appropriate value according to the network plan. To set the common measurement period based on R99 and HSUPA user fairness in a satellite communications environment, run the BSC6900 MML command SET USATLDCPERIOD with Fairness period timer length set to an appropriate value according to the network plan. To set the fairness threshold for R99 and HSUPA users, run the BSC6900 MML command MOD UCELLLDM with Fairness threshold set to an appropriate default value according to the network plan. To enable the DCCC algorithm switch for applying the dynamic channel reconfiguration control algorithm to the RNC, run the BSC6900 MML command SET UCORRMALGOSWITCH to select the DRA_DCCC_SWITCH from the dropdown list Dynamic Resource Allocation Switch. Initiate Iub interface tracing on the BSC6900 LMT, as shown in Figure 173-1.
3.
4.
5.
Figure 173-1 Iub interface tracing dialog box
2. 3.
Establish PS BE services on the HSUPA and R99 UEs. The BSC6900 side sends a COMMON MEASUREMENT INITIATION REQUEST message to the NodeB side. The NodeB side submits fairness common measurement reports to the BSC6900 side, as shown in Figure 173-2.
173-2
Issue 02 (2011-07-11)
Figure 173-2 fairness common measurement report
Deactivation Procedure 1. To disable the algorithm switch for cell-level rate reduction for BE services based on R99 and HSUPA user fairness, run the BSC6900 MML command MOD UCELLALGOSWITCH with BE rate reduction switch based on fairness set to OFF.
----End
Example
/*Activating the Optimization of R99 and HSUPA Users Fairness feature //Enabling the algorithm switch for cell-level rate reduction for BE services based on R99 and HSUPA user fairness MOD UCELLALGOSWITCH: CellId=11011, BERateReductionOnFairnessSwitch=ON; Where, [PARA]CellId[/PARA] is set to the cell ID for the algorithm switch. //Setting the common measurement period based on R99 and HSUPA user fairness SET ULDCPERIOD: FairnessPeriodTimerLen=11; //Setting the common measurement period based on R99 and HSUPA user fairness in a satellite communications environment SET USATLDCPERIOD: FairnessPeriodTimerLen=11; //Setting the fairness threshold for R99 and HSUPA users MOD UCELLLDM: CellId=11011,FairnessThd=150; Where, [PARA]CellId[/PARA] is set to the cell ID for the algorithm switch. //Enable the DCCC algorithm switch SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1; /*Deactivating the Optimization of R99 and HSUPA Users Fairness feature //Disabling the algorithm switch for cell-level rate reduction for BE services based on R99 and HSUPA user fairness MOD UCELLALGOSWITCH: CellId=11011, BERateReductionOnFairnessSwitch=OFF; Where, [PARA]CellId[/PARA] is set to the cell ID for the algorithm switch.
Issue 02 (2011-07-11)
173-3
174 Configuring Cell Broadcast Service
174
Prerequisite
l l
Configuring Cell Broadcast Service
This section describes how to activate, verify, and deactivate the optional feature WRFD-011000 Cell Broadcast Service.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature and the feature WRFD-011001 Simplified Cell Broadcast cannot be used together.
l l
License The license controlling this feature has been activated. Others The UE is capable of receiving cell broadcast messages.
Context
This feature supports the standard cell broadcast procedure specified in the related protocol and therefore helps the cell broadcast center (CBC) implement cell broadcast services.
Procedure
l Activation Procedure External CBCs are deployed in an ATM or IP network. The ATM network is used as an example in this document. 1. 2. 3. 4. Run the BSC6900 MML command RMV URNCCBCPUID to disable the configuration of the built-in CBC. Run the BSC6900 MML command SET URNCCBPARA to turn off CB Switch. Run the BSC6900 MML command ADD DEVIP to add the device IP address of the interface board. Run the BSC6900 MML command ADD IPOAPVC to add an Internet Protocol over ATM (IPoA) permanent virtual circuit (PVC).
Issue 02 (2011-07-11)

NOTE
The IP address is the device IP address (DEVIP) of the interface board. The peer IP address is the IP address for interconnection between serving GPRS support node (SGSN) and RNC. The VPI and VCI must be the same as those configured on the SGSN. To query the specific settings, run the LST IPOA command on the SGSN maintenance terminal.
5. 6. 7.
Run the BSC6900 MML command ADD IPRT to add a route from the interface board to the CBC. The route passes the IP address of the SGSN. Run the BSC6900 MML command ADD UCBSADDR to add the CBS socket IP address. Run the BSC6900 MML command ADD UCTCH to add the common traffic channel (CTCH) to a cell.
NOTE
To set up a CTCH on FACH5, run the following commands:

DEA ADD ADD ACT USCCPCH: CellId=0, PhyChId=8; UFACHLOCH: CellId=0, TrChId=5; USCCPCHTFC: CellId=0, PhyChId=8, CTFC=7; USCCPCH: CellId=0, PhyChId=8;
8. 9.
Run the BSC6900 MML command ADD UCELLCBSDRX to add the CBS discontinuous reception (DRX) scheduling parameter. Run the BSC6900 MML command ADD UCELLCBSSAC to add a CBS area.
10. Run the BSC6900 MML command ACT UCELLCBS to enable 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. If the ping operation is successful, it indicates that the data transmission from CBC to RNC is normal. (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. PING IP: SRN=0, SN=16, SIPADDR="12.12.12.12", DESTIP="11.11.11.11"; If the ping operation is successful, it indicates that the data transmission from RNC to CBC is normal. If the ping operation fails, check the configuration. (3) Check whether the CBS socket is connected properly. To do this, trace messages over the Iu interface and view whether the SABP_LOAD_QUERY is sent to the RNC, as shown in Figure 174-1.
174-2
Issue 02 (2011-07-11)
Figure 174-1 Viewing the SABP_LOAD_QUERY message
(4) As shown in Figure 174-2, the 0SABP_LOAD_QUERY_CMP message returned from the RNC contains the information element (IE) availablebandwidth. Figure 174-2 Viewing the SABP_LOAD_QUERY_CMP message
(5) Run the BSC6900 MML command DSP UCELL to check whether the CBS function works, as shown in Figure 174-3.
Issue 02 (2011-07-11)
174-3
Figure 174-3 Viewing the CBS function
2.
Check the broadcast messages sent. (1) Use the MTC tool to send messages on the CBC. It is recommended that the time interval for sending messages be within 10s and the number of messages sent be more than two (0 indicates infinity). (2) Trace messages on the Iu interface to check whether the SABP_WRITE_REPLACE message is sent to the RNC, as shown in Figure 174-4.
174-4
Issue 02 (2011-07-11)
Figure 174-4 Viewing the SABP_WRITE_REPLACE message
(3) As shown in Figure 174-5, the SABP_WRITE_REPLACE_CMP message returned from the RNC contains a broadcast message with the IE number-ofbroadcasts-completed.
Issue 02 (2011-07-11)
174-5
Figure 174-5 Viewing the SABP_WRITE_REPLACE_CMP message
(4) Trace messages on the Uu interface to check whether the UU_BMC_MSG_TYPE message beginning with 01 is sent from the RNC, as shown in Figure 174-6.
174-6
Issue 02 (2011-07-11)
Figure 174-6 Viewing the UU_BMC_MSG_TYPE message
3.
Stop the RNC from sending broadcast messages. (1) On the CBC, select the message being sent and click delete. (2) Trace messages on the Iu interface to check whether the SABP_KILL message is sent to the RNC, as shown in Figure 174-7.
Issue 02 (2011-07-11)
174-7
Figure 174-7 Viewing the SAB_KILL message
(3) Trace messages on the Iu interface, as shown in Figure 174-8. The SABP_KILL_CMP message returned from the RNC contains the IE numberof-broadcast-completed.
174-8
Issue 02 (2011-07-11)
Figure 174-8 Viewing the SABP_KILL_CMP message
(4) It can be viewed from the Uu interface trace data that the RNC stops sending the UU_BMC_MSG_TYPE message beginning with 01. l Deactivation Procedure 1. ----End Run the BSC6900 MML command RMV UCBSADDR to disable Cell Broadcast Service.
Example
//Activating Cell Broadcast Service //Configuring the license controlling Cell Broadcast Service SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=1, FUNCTIONSWITCH1=CBS-1;
Issue 02 (2011-07-11)
174-9

//Removing the configuration of the built-in CBC RMV URNCCBCPUID: CnOpIndex=1; //Disabling the inner CBS function for the RNC SET URNCCBPARA: CBSwitch=OFF;
//Configuring the device IP address of the interface board ADD DEVIP: SRN=5, SN=18, DEVTYPE=IPOA_CLIENT_IP, IPADDR="12.12.12.12", MASK="255.255.255.0"; //Configuring the IPoA PVC ADD IPOAPVC: IPADDR="12.12.12.12", PEERIPADDR="12.12.12.120", CARRYT=NCOPT, CARRYNCOPTN=0, CARRYVPI=255, CARRYVCI=32, TXTRFX=103, RXTRFX=103, PEERT=OTHER; //Configuring a route from the interface board to CBC ADD IPRT: SRN=5, SN=18, DSTIP="11.11.11.12", DSTMASK="255.255.255.255", NEXTHOP="12.12.12.120", PRIORITY=HIGH, REMARK="SGSN_CBS"; //Configuring the CBS socket IP address ADD UCBSADDR: SRN=5, SN=2, CnOpIndex=1, RNCIPADDR="12.12.12.12", CBCIPADDR="11.11.11.11", CBCMASK="255.255.255.0"; //Configuring the CTCH for a cell ADD UCTCH: CellId=0, FachId=4; //Configuring the CBS DRX scheduling parameter ADD UCELLCBSDRX: CellId=0; //Configuring a CBS area ADD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=OFF; //Enabling the cell-level CBS ACT UCELLCBS: CellId=0;
//Deactivating Cell Broadcast Service //Removing the CBS socket IP address RMV UCBSADDR: CnOpIndex=1;
174-10
Issue 02 (2011-07-11)
175 Configuring Simplified Cell Broadcast
175
Prerequisite
l l
Configuring Simplified Cell Broadcast
This section describes how to activate, verify, and deactivate the optional feature WRFD-011001 Simplified Cell Broadcast.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature and the feature WRFD-011000 Cell Broadcast Service cannot be used together.
l l
License The license controlling this feature has been activated. Others Only BSC6900 supports this feature. The UE is capable of receiving cell broadcast messages.
Context
This feature is used to send simple cell broadcast messages by running a BSC6900 MML command on the M2000 or BSC6900 LMT when the cell broadcast center (CBC) is not configured.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command RMV UCBSADDR to remove the IP address of the external CBC. Run the BSC6900 MML command ADD URNCCBCPUID to configure the SPU subsystem of the built-in CBC. Run the BSC6900 MML command SET URNCCBPARA. In this step, set CB Switch to ON(ON) to enable the built-in CBC for the RNC.
Issue 02 (2011-07-11)
4. 5. 6. 7. l
Run the BSC6900 MML command ADD UCTCH to add the common traffic channel (CTCH) to a cell. Run the BSC6900 MML command ADD UCELLCBSDRX to add the CBS discontinuous reception (DRX) scheduling parameter. Run the BSC6900 MML command ADD UCELLCBSSAC to add a CBS area and a broadcast message. Run the BSC6900 MML command ACT UCELLCBS to enable the CBS function for a cell. Check whether the CBS function works properly. After activating the CBS function on the RNC, if the UU_BMC_MSG_TYPE message beginning with 01 is traced on the Uu interface, as shown in Figure 175-1, the CBS function works properly. Figure 175-1 UU_BMC_MSG_TYPE message
Deactivation Procedure 1. 2. Run the BSC6900 MML command DEA UCELLCBS to disable the CBS function for a cell. Run the BSC6900 MML command SET URNCCBPARA. In this step, set CB Switch to OFF(OFF) to turn off the CBS switch for the BSC6900.
----End
Example
//Activating Simplified Cell Broadcast //Enabling the license controlling Simplified Cell Broadcast SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=1, FUNCTIONSWITCH4=SIMPLE_CELL_BORADCAST-1; //Removing the IP address of an external CBS RMV UCBSADDR: CnOpIndex=1; //Configuring the SPU subsystem of the built-in CBC ADD URNCCBCPUID: CnOpIndex=1, SRN=0, SN=2, SSN=1; //Enabling the built-in CBC for the RNC SET URNCCBPARA: CBSwitch=ON, RepeatPeriod=10, RepeatNum=0;
175-2
Issue 02 (2011-07-11)
//Configuring the CTCH for a cell ADD UCTCH: CellId=0, FachId=4; //Configuring the CBS DRX scheduling parameter ADD UCELLCBSDRX: CellId=0; //Configuring a CBS area and a broadcast message ADD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=ON, MsgContent="welcome! it is cell 0"; //Enabling the CBS function for a cell ACT UCELLCBS: CellId=0;
//Verifying Simplified Cell Broadcast //Modifying the CBS configuration for a cell MOD UCELLCBSSAC: CellId=0, CnOpIndex=1, CBSSAC=0, MsgInd=ON, MsgContent="HELLO,SIMPLE CBS"; //Activating the CBS function for a cell ACT UCELLCBS: CellId=0;
//Deactivating Simplified Cell Broadcast //Disabling the CBS function for a cell DEA UCELLCBS: CellId=0; //Disabling the CBS function for the BSC6900 SET URNCCBPARA: CBSwitch=OFF;
Issue 02 (2011-07-11)
175-3
176 Configuring TFO/TrFO
176
Prerequisite
l l l l Dependencies on Hardware Dependencies on Other Features License
Configuring TFO/TrFO
This section describes how to activate, verify, and deactivate the optional feature WRFD-011600 TFO/TrFO.
This feature does not depend on the hardware. This feature does not depend on other features. The license controlling this feature has been activated. Other Prerequisites The CN node supports this feature. The UE supports this feature.
Context
This feature helps implement the functions of TFO/TrFO by identifying the Iu user plane (IuUP) V2 core network (CN) and processing related services. This feature can prevent speech quality deterioration caused by the interpretation between different coder and decoders (CODECs). The TrFO can also save the transmission resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the IuUP V2 switch to support TFO/TrFO. Select CS_IUUP_V2_SUPPORT_SWITCH from the CS Algorithm Switch drop-down list. Start Uu interface tracing on the BSC6900 LMT. Enable UE1 to call UE2. UE2 answers and starts a conversation with UE1. When UE1 moves to the cell edge, you can view the RRC TFC CTRL message indicating rate
Issue 02 (2011-07-11)
176 Configuring TFO/TrFO
reduction sent from RNC to UE1 over the Uu interface. This indicates that this feature is activated. l Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the IuUP switch. Deselect CS_IUUP_V2_SUPPORT_SWITCH from the CS Algorithm Switch drop-down list.
----End
Example
//Activation procedure SET UCORRMALGOSWITCH: CsSwitch=CS_IUUP_V2_SUPPORT_SWITCH-1; //Deactivation procedure SET UCORRMALGOSWITCH: CsSwitch=CS_IUUP_V2_SUPPORT_SWITCH-0;
176-2
Issue 02 (2011-07-11)
177 Configuring Dynamic Power Sharing of Multi-Carriers
177
Prerequisite
l l l l
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.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites The NodeB software version should be no earlier than RAN11.0.
Context
Dynamic Power Sharing of Multi-Carriers means that among multiple carriers, the carrier bearing HSPA service can dynamically share the unused power resource of another carrier. This function increases the utilization of the power amplifier as well as the HSPA service rate of the cell. For asymmetrical power configuration, the carrier with higher emitting power cannot share the unused power resource of the carrier with lower emitting power.
Procedure
l Activation Procedure 1. Run the NodeB MML command ADD PAGRP to add a power sharing group.
Issue 02 (2011-07-11)
177-1
177 Configuring Dynamic Power Sharing of Multi-Carriers

NOTE
l Dynamic spectrum sharing cannot be configured with dynamic power sharing. l A power sharing group consists of a source local cell and a destination local cell. l The source local cell must support only R99 services, and the destination local cell must support HSDPA services. l The source local cell and the destination local cell must use the same RF module and be configured with the same maximum power. l The maximum rate of idle power that the source local cell is allowed to share with the destination local cell is recommended to set to default value. This rate is based on the configured maximum transmit power of the source local cell. l The rate of idle power that must be reserved for the source local cell. This rate is based on the configured maximum transmit power of the source local cell. Reserving the idle power for the source local cell helps avoid power fluctuation in the source local cell caused by power sharing that is not timely.
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 ADD PAGRP: SLOCELL=1, DLOCELL=2, MAXSHRTO=50, SHMGN=10; //Deactivation procedure RMV PAGRP: DLOCELL=2;
177-2
Issue 02 (2011-07-11)
178 Configuring Multi-Carrier Switch off Based on Traffic Load
178
Prerequisite
l l l
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.
Context
l The power consumption evaluation of the products in mobile networks shows that the devices, particularly the base stations, in the radio access network are the principal contributor of power consumption and CO2 emissions when they are functioning. If multiple carriers are used in the same coverage area, Huawei provides operators with adaptive carrier power management to reduce power consumption. The traffic volume varies with time. For example, a base station in the Central Business District (CBD) has a higher traffic volume in the daytime, which requires more than one carrier to serve all the subscribers; the traffic volume becomes low from midnight to early morning of the next day. From RAN10.0 on, during an idle period that is configurable by operators, the RNC dynamically shuts down the carriers on which there is no service and uses the other carriers in the same area. The carriers will be turned on again when the traffic on the other carriers becomes congested or when the idle period ends. This reduces power consumption.
Procedure
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
Issue 02 (2011-07-11)
for Cell Dynamic Open, and Protect Timer Length for Cell Dynamic ShutDown to appropriate values. 2. Assume that the cell ID is 1. Run the BSC6900 MML command LST UCELLDYNSHUTDOWN to check whether Cell Dynamic ShutDown Switch is turned on. If Cell Dynamic ShutDown Switch is turned off, run the BSC6900 MML command ADD UCELLDYNSHUTDOWN to turn on Cell Dynamic ShutDown Switch, specify the shutdown period, and set the following parameters to appropriate values. Cell Dynamic ShutDown Type Cell Dynamic ShutDown Total User number Threshold Cell Dynamic ShutDown Hsdpa User number Threshold Cell Dynamic ShutDown Hsupa User number Threshold Cell Dynamic ShutDown Neighbour Cell Load Remain threshold
NOTE
Default values of the above parameters are recommended.
If Cell Dynamic ShutDown Switch is turned on, run the MML command MOD UCELLDYNSHUTDOWN to modify the related parameters. 3. Run the BSC6900 MML command LST UINTERFREQNCELL to check whether an inter-frequency co-coverage neighboring cell is configured for cell 1. Assume that the ID of the inter-frequency co-coverage neighboring cell is 2. This feature takes effect only when cell 2 is served by the same NodeB as cell 1. If the neighboring cell is not configured, run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-frequency co-coverage neighboring cell. In this step, set Blind Handover Flag to TRUE. If the neighboring cell is configured, run the BSC6900 MML command MOD UINTERFREQNCELL. In this step, set Blind Handover Flag to TRUE. 4. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set Cell CAC algorithm switch to HSDPA_GBP_MEAS.
NOTE
This feature takes effect only when the GBP measurement switch for the inter-frequency cocoverage neighboring cell is turned on.
Verification Procedure 1. 2. 3. Start alarm browsing on the BSC6900 LMT. Ensure that the total number of users in cell 1 and cell 2 is 0. Alternatively, set up two inter-frequency co-coverage neighboring cells where no user is admitted. At a time during the period specified by running the BSC6900 MML command ADD UCELLDYNSHUTDOWN (for example, 09:10): If an ALM-22202 UMTS Cell Unavailable is reported at cell 1 with the cause value of cell dynamic shutdown, this feature has been activated. If this alarm is not reported or is reported but the cause value is not cell dynamic shutdown, this feature is not activated. 4. Check whether this feature is activated by viewing the counter VS.DynOpen.CellSetup and check whether this feature is deactivated by viewing the counter VS.DynClose.CellDel on the M2000.
178-2
Deactivation Procedure 1. Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA to deactivate this feature at the RNC. In this step, set Cell Dynamic ShutDown Switch For RNC to OFF(switch off). Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN to deactivate this feature for cell 1.
2. ----End
Example
/*Activation procedure*/ //Turning on the RNC-level switch for dynamic shutdown SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=ON; //Turning on the cell-level switch for dynamic shutdown ADD UCELLDYNSHUTDOWN: CellId=1, DynShutdownSwitch=ON_1, StartTime1=08&59, EndTime1=10&59, DynShutDownType=CONDITIONALSHUTDOWN; //Adding inter-frequency co-coverage neighboring cells for the cell where this feature is activated (cell 1 and cell 2 in the following command are served by the same NodeB) ADD UINTERFREQNCELL: RNCId=110, CellId=1, NCellRncId=110, NCellId=2, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE; //Turning on the GBP measurement switch for an inter-frequency co-coverage neighboring cell MOD UCELLALGOSWITCH: CellId=2, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST; /*Deactivation procedure*/ //Deactivating Multi-Carrier Switch off Based on Traffic Load at the RNC SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=OFF; //Deactivating Multi-Carrier Switch off Based on Traffic Load for cell 1 RMV UCELLDYNSHUTDOWN: CellId=1;
Issue 02 (2011-07-11)
178-3
179 Configuring Energy Efficiency Improved
179
Prerequisite
l l l
Configuring Energy Efficiency Improved
This section describes how to activate, verify, and deactivate the optional feature WRFD-020118 Energy Efficiency Improved.
Dependencies on Hardware MTRU of the BTS3812E/BTS3812AE does not support this feature. The RRU3801C of the NodeB does not support this feature. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
l Based on efficient power amplifier (PA) techniques, the function dynamic adaptation of PA parameters is introduced in the case of HSDPA services to further improve the PA efficiency under the condition of low load. When HSDPA services are performed, the NodeB adjusts the PA bias voltage based on output power that varies with the traffic load, improving the PA efficiency and reducing the static PA power consumption. l l When there is no HSDPA service, the function is supported by the system as long as the license is activated. When HSDPA services are performed, the function is not supported by the system by default. To enable the system to support the function, perform the following operations to enable devices to adjust PA parameters dynamically based on the traffic load during a specified period of time, improving the PA efficiency.
Procedure
l
Issue 02 (2011-07-11)
179 Configuring Energy Efficiency Improved
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.
Verification Procedure 1. Run the NodeB MML command LST OPTDYNADJPARA to query the dynamic voltage adjustment parameters. In the returned result, check that Dynamic Voltage Adjustment Switch is set to ON, which indicates that the function is activated. Check that Start Time and End Time are set to the required values. Run the NodeB MML command SET OPTDYNADJPARA to set the dynamic voltage adjustment parameters. In this step, set Dynamic Voltage Adjustment Switch to OFF.
----End
Example
//Activation procedure SET OPTDYNADJPARA: DYNADJSWITCH=ON, DYNADJSTARTTIME=0, DYNADJENDTIME=6; //Verification procedure LST OPTDYNADJPARA:; //Deactivation procedure SET OPTDYNADJPARA: DYNADJSWITCH=OFF;
179-2
Issue 02 (2011-07-11)
180 Configuring Multi-Carrier Switch off Based on QoS
180
Prerequisite
l l
Configuring Multi-Carrier Switch off Based on QoS
This section describes how to activate, verify, and deactivate the optional feature WRFD-020122 Multi-Carrier Switch off Based on QoS.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010610 HSDPA Introduction Package has been configured before this feature is activated.
Context
This feature guarantees the data rate for only DCH and high-priority HSDPA users. For lowpriority HSDPA users, only Guaranteed Bit Rate (GBR) is guaranteed. If the remaining bandwidth of neighboring cells can meet the preceding requirements for rate, this feature can be enabled to reduce the power consumption, and therefore increase profits of operators.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA. In this step, set Cell Dynamic ShutDown Switch for RNC to ON(switch on). Assume that the cell ID is 2003. Run the BSC6900 MML command LST UCELLDYNSHUTDOWN to check whether Cell Dynamic ShutDown Switch is set to ON for this cell. (1) If Cell Dynamic ShutDown Switch is set to OFF, run the BSC6900 MML command ADD UCELLDYNSHUTDOWN. In this step, set Cell Dynamic ShutDown Switch to ON_1(switch on1), specify First Cell Dynamic ShutDown Interval Start Time, First Cell Dynamic ShutDown Interval End
Time, set Cell Dynamic ShutDown Type to QOSSHUTDOWN (QosShutDown), and specify High-Priority Scheduling Indicator. (2) If Cell Dynamic ShutDown Switch is turned on, run the BSC6900 MML command MOD UCELLDYNSHUTDOWN to modify the settings of the preceding parameters to the specified settings. 3. Run the BSC6900 MML command LST UINTERFREQNCELL to check whether cell 2003 is configured with an inter-frequency co-coverage neighboring cell. Assume that the ID of the inter-frequency co-coverage neighboring cell is 2004. (1) This feature takes effect only when cell 2004 is under the same NodeB as cell 2003. (2) If the neighboring cell is not configured, run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-frequency co-coverage neighboring cell. In this step, set Blind Handover Flag to TRUE. (3) If the neighboring cell is configured, run the BSC6900 MML command MOD UINTERFREQNCELL. In this step, set Blind Handover Flag set to TRUE. 4. Run the BSC6900 MML command ADD UCELLALGOSWITCH. In this step, set Cell CAC algorithm switch to HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm).
NOTE
This feature takes effect only when the GBP measurement switches of both cell 2003 and cell 2004 are turned on.
Verification Procedure 1. 2. Start alarm browsing on the BSC6900 LMT. Ensure that the total number of users in cell 2003 and cell 2004 is 0. Alternatively, add two inter-frequency co-coverage cells that have bidirectional neighboring cell relationships, and these cells do not carry any services. At a time during the period specified in the BSC6900 MML command ADD UCELLDYNSHUTDOWN (for example, 09:10): If the alarm ALM-22202 UMTS Cell Unavailable is reported at cell 2003 with a cause of cell dynamic shutdown, this feature has been activated. If the alarm is not reported or is reported at cell 2003 but the cause is not cell dynamic shutdown, this feature has not been activated. 4. You can also view whether the feature is activated by checking certain counters on the M2000: If the value of the counter VS.DynOpen.CellSetup is not 0, the feature is activated; If the value of the counter VS.DynClose.CellDel is not 0, the feature is not activated. Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA to deactivate this feature for the RNC. In this step, set Cell Dynamic ShutDown Switch for RNC to OFF(switch off). Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN. In this step, set Cell ID to 2003 to deactivate this feature for cell 2003.
3.
2. ----End
Example
/*Activation procedure*/
180-2
Issue 02 (2011-07-11)
//Turning on the cell dynamic shutdown switch for the RNC SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=ON; //Turning on the cell dynamic shutdown switch ADD UCELLDYNSHUTDOWN: CellId=2003, DynShutdownSwitch=ON_1, StartTime1=11&50, EndTime1=11&55, DynShutDownType=QOSSHUTDOWN, HighPriSPI=SPI11-1&SPI12-1&SPI13-1; //Adding an inter-frequency co-coverage neighboring cell (cell 2004) to a cell (cell 2003) whose TRXs are shut down (cells 2003 and 2004 are under the same NodeB) ADD UINTERFREQNCELL: RNCId=110, CellId=2003, NCellRncId=110, NCellId=2004, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE; //Turning on the GBP measurement switches for a cell (cell 2003)and its inter-frequency co-coverage neighboring cell (cell 2004) ADD UCELLALGOSWITCH: CellId=2003, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST; ADD UCELLALGOSWITCH: CellId=2004, NBMCacAlgoSwitch=HSDPA_GBP_MEAS-1, NBMUlCacAlgoSelSwitch=ALGORITHM_FIRST, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST; /*Deactivation procedure*/ //Deactivating Multi-Carrier Switch off Based on QoS for the RNC SET URNCCELLSHUTDOWNPARA: DynCellShutDownSwitch=OFF; //(Optional) Deactivating Multi-Carrier Switch off Based on QoS for cell 2003 RMV UCELLDYNSHUTDOWN: CellId=2003;
Issue 02 (2011-07-11)
180-3
181 Configuring Multi-Carrier Switch off Based on Power Backup
181
Prerequisite
l l l
Configuring Multi-Carrier Switch off Based on Power Backup
This section describes how to activate, verify, and deactivate the optional feature WRFD-020119 Multi-Carrier Switch off Based on Power Backup.
Dependencies on Hardware This feature does not have special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
In case of mains failure, the backup power system starts to operate. In this case, this feature can implement hierarchical carrier shutdown based on the shutdown duration and cell priority.
Procedure
l NodeB V200R013 Activation Procedure 1. Run the NodeB MML command MOD LOCELL with Local Cell ID and Sector Type specified in order to set reserved cells. For the cells that need to provide services continuously during the level-1 shutdown period, set Reserved Cell to TRUE.
NOTE
It is recommended that at least one cell be reserved for a sector. In case of mains failure, the reserved cell continues to provide services for the users in this sector.
2.
Run the NodeB MML command MOD LOWPOWERPARA to set the intelligent power shutdown switch with the NodeB ISD Switch set to ENABLE. Set Level 1 power off Delay (s) and Level 2 power off Delay (s) based on the backup capability of the batteries.
Issue 02 (2011-07-11)
3.
If you need to use the smooth power change function, run the NodeB MML command SET SMTHPWRSWTCH to set the intelligent power shutdown switch with the Smooth Power Change Function Switch set to OPEN.
NOTE
Before a cell is shut down, the smooth power change function reduces the TX power of the PCPICH so that the services in the cell are handed over to neighboring cells. This prevents service disruption due to abrupt cell shutdown.
Verification Procedure 1. Run the NodeB MML command LST LOWPOWERPARA to query the configuration information about the intelligent power shutdown switch. On the LMT, check whether the NodeB ISD Switch is set to ENABLE, and whether the Level 1 power off Delay (s) and Level 2 power off Delay (s) are set correctly. Run the NodeB MML command LST LOCELL to query the configuration information about local cells. Check whether the value of Reserve Cell of each local cell is correct. If the smooth power change function is already used, run the NodeB MML command LST SMTHPWRSWTCH to check whether the intelligent power shutdown switch is turned on. If the Smooth Power Change Function Switch is set to OPEN, it indicates that this function is enabled.
2.
3.
Deactivation Procedure 1. l Run the NodeB MML command MOD LOWPOWERPARA to turn off the intelligent power shutdown switch with the NodeB ISD Switch set to DISABLE.
NodeB V100R013 Activation Procedure 1. Run the NodeB MML command MOD LOCELL with Local Cell ID and Sector Type specified in order to set reserved cells. For the cells that need to provide services continuously during the level-1 shutdown period, set Reserved Cell to TRUE.
NOTE
It is recommended that at least one cell be reserved for a sector. In case of mains failure, the reserved cell continues to provide services for the users in this sector.
2.
Run the NodeB MML command SET ITELSHUTDOWN to set the intelligent power shutdown switch with the ISD SWITCH set to ENABLE. Set LEVEL1 DELAY and LEVEL2 DELAY based on the backup capability of the batteries. If you need to use the smooth power change function, run the NodeB MML command SET SMTHPWRSWTCH to set the intelligent power shutdown switch with the Smooth Power Change Function Switch set to OPEN.
NOTE
3.
Before a cell is shut down, the smooth power change function reduces the TX power of the PCPICH so that the services in the cell are handed over to neighboring cells. This prevents service disruption due to abrupt cell shutdown.
Verification Procedure 1. Run the NodeB MML command LST ITELSHUTDOWN to query the configuration information about the intelligent power shutdown switch. On the LMT, check whether the NodeB ISD Switch is set to ENABLE, and whether the Level 1 power off and Level w power off are set correctly.
181-2
2.
Run the NodeB MML command LST LOCELL to query the configuration information about local cells. Check whether the value of Reserve Cell of each local cell is correct. If the smooth power change function is already used, run the NodeB MML command LST SMTHPWRSWTCH to check whether the intelligent power shutdown switch is turned on. If the Smooth Power Change Function Switch is set to OPEN, it indicates that this function is enabled.
3.
Deactivation Procedure 1. ----End Run the NodeB MML command SET ITELSHUTDOWN to turn off the intelligent power shutdown switch with the ISD Switch set to DISABLE.
Example
l NodeB V200R013
//Activation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, RSV=TRUE; MOD LOWPOWERPARA: ISD=ENABLE, LEVEL1=60, LEVEL2=120; SET SMTHPWRSWTCH: SWITCH=OPEN; //Verification procedure LST LOWPOWERPARA:; LST LOCELL: MODE=LOCALCELL, LOCELL=1; LST SMTHPWRSWTCH:; //Deactivation procedure MOD LOWPOWERPARA: ISD=DISABLE;
NodeB V100R013
//Activation procedure MOD LOCELL: LOCELL=1, SECT=LOCAL_SECTOR, RSV=TRUE; SET ITELSHUTDOWN: ISD=ENABLE, LEVEL1=60, LEVEL2=120; SET SMTHPWRSWTCH: SWITCH=OPEN; //Verification procedure LST ITELSHUTDOWN:; LST LOCELL: MODE=LOCALCELL, LOCELL=1; LST SMTHPWRSWTCH:; //Deactivation procedure SET ITELSHUTDOWN: ISD=DISABLE;
Issue 02 (2011-07-11)
181-3
182 Configuring Intelligent Power Management
182
Prerequisite
l l l
Configuring Intelligent Power Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-020121 Intelligent Power Management.
Dependencies on Hardware The NodeB type is BTS3900A or DBS3900. Huawei APM30 and batteries are used. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
With this feature, certain Power Supply Units (PSUs) can be powered on or off according to the power consumption of the NodeB, reducing the power consumption.
Procedure
l Activation Procedure 1. l Run the NodeB MML command SET PSUISS with the PSU Intelligent Shutdown Switch set to ENABLE(ENABLE). Run the NodeB MML command LST PSUISS to check whether the PSU Intelligent Shutdown Switch is set to ENABLE(ENABLE). Run the NodeB MML command SET PSUISS with the PSU Intelligent Shutdown Switch set to DISABLE(DISABLE).
----End
182 Configuring Intelligent Power Management
Example
//Activation procedure SET PSUISS: PSUISS=ENABLE; //Verification procedure LST PSUISS:; //Deactivation procedure SET PSUISS: PSUISS=DISABLE;
182-2
Issue 02 (2011-07-11)
183 Configuring AMR-WB (Adaptive Multi Rate Wide Band)
183
Prerequisite
l l l l
Configuring AMR-WB (Adaptive Multi Rate Wide Band)
This section describes how to activate, verify, and deactivate the optional feature WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band).
Dependencies on Hardware The CN supports associated specifications. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites The UE supports associated specifications. The AMR-WB function is enabled on the MSC and UMG.
Context
This feature provides AMR-WB services, which help improve the QoS of voice services when resources are sufficient.
CAUTION
l This feature is an integrated solution. To enable this feature, specific parameters must be configured based on the actual network conditions. Contact Huawei for technical support. l Do not configure relevant parameters without the assistance of Huawei technical personnel; otherwise, the network capacity and KPI values may be affected.
Procedure
l
Issue 02 (2011-07-11)
183 Configuring AMR-WB (Adaptive Multi Rate Wide Band)
1. 2. l
Optional: Run the BSC6900 MML command SET UAMRCWB to set the RNClevel speech rates for the gold, silver, and bronze users. Optional: Run the BSC6900 MML command ADD UCELLAMRCWB to set celllevel speech rates for the gold, silver, and bronze users. Optional: Run the BSC6900 MML command LST UAMRCWB to query the AMRWB speech rates of the gold, silver, and bronze users. Optional: Run the BSC6900 MML command LST UCELLAMRCWB to query the AMR-WB speech rates for the gold, silver, and bronze users. On the BSC6900 LMT, open the Monitor tab page, choose Monitor > Monitor > UMTS Monitoring > Cell Performance Monitoring, and create a task of AMR Mode. Enable the AMR-WB function on UE1 and UE2, and enable the UEs to camp on the cell CELL_A11. Use UE1 to initiate a voice call to UE2. The call is successfully established and the voice is clear. Check the AMR mode on the LMT and verify that the downlink rate of UE1 reaches the specified value.
4. 5. 6. l
Deactivation Procedure Run the BSC6900 MML command SET LICENSE to deactivate the license controlling this feature.
NOTE
After deactivating the license controlling this feature, a WB-AMR cannot establish WB and NB services. If the WB rate for the RNC is disabled, a WB-AMR UE still can establish NB services.
----End
Example
//Activating AMR-WB //Setting RNC-level parameters for the WB-AMR speech rate control (WBAMRC) algorithm SET UAMRCWB: GoldMaxMode=WBAMR_BITRATE_12.65K, SilverMaxMode=WBAMR_BITRATE_12.65K, CopperMaxMode=WBAMR_BITRATE_12.65K; //Setting cell-level parameters for the WB-AMRC algorithm ADD UCELLAMRCWB: CellId=111, GoldMaxMode=WBAMR_BITRATE_12.65K, SilverMaxMode=WBAMR_BITRATE_12.65K, CopperMaxMode=WBAMR_BITRATE_12.65K; //Deactivating AMR-WB SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH2=WBAMR-0;
183-2
Issue 02 (2011-07-11)
184 Configuring AMR/WB-AMR Speech Rates Control
184
Prerequisite
l l
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.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features If this feature is to be applied to Adaptive Multi Rate Wide Band (AMR WB), this feature depends on WRFD-010613 AMR-WB.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE supports TFC control processing.
Context
This feature enables the adjustment of AMR/AMR-WB speech rates triggered by multiple factors. This ensures uninterrupted services, expands the service coverage area, and reduces the cell load.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set CS Algorithm Switch to CS_AMRC_SWITCH. Run the BSC6900 MML command SET UQOSACT to turn on the QoS switches for AMR services. Optional: Run the BSC6900 MML command SET UQUALITYMEAS or MOD UTYPRABQUALITYMEAS to set the parameters for RNC-level AMR and AMRWB speech rate control based on link stability. Optional: Set the parameters for AMR and AMR-WB speech rate control.
4.
Issue 02 (2011-07-11)
Set the AMR speech rate control parameters. (1) Run the BSC6900 MML command SET UCORRMPARA. In this step, deselect the RESERVED_SWITCH_0_BIT4 check box under parameter CORRM Algorithm Reserved Switch 0 to enable NB-AMRC.
NOTE
Select the RESERVED_SWITCH_0_BIT4 check box to disable NB-AMRC when there are some NB-AMRC compatibility problems.
(2) Run the BSC6900 MML command SET UAMRC to set the RNC-level AMR speech rate control parameters. Set the AMR-WB speech rate control parameters. (1) Run the BSC6900 MML command SET UCORRMPARA. In this step, deselect the RESERVED_SWITCH_0_BIT3 check box under parameter CORRM Algorithm Reserved Switch 0 to enable WB-AMRC.
NOTE
Select the RESERVED_SWITCH_0_BIT3 check box to disable WB-AMRC when there are some WB-AMRC compatibility problems.
(2) Run the BSC6900 MML command SET UAMRCWB to set the RNC-level AMR-WB speech rate control parameters. l Verification Procedure 1. On the BSC6900 LMT, open the Monitor tab page. In the Monitor tab page, doubleclick UMTS Monitoring > Connection Performance Monitoring. In the displayed dialog box, set Monitor Item to AMR Mode and specify IMSI. On the BSC6900 LMT, open the Trace tab page. In the Trace tab page, double-click UMTS Services > Uu Interface Trace. In the displayed dialog box, specify the IMSI, as shown in Figure 184-1.
2.
184-2
Issue 02 (2011-07-11)
Figure 184-1 Uu interface tracing
3. 4.
Two test UEs supporting AMR WB are available and camp on the cell named CELL_A11. Use UE A to call UE B. The call is established. Check whether the following information elements (IEs) are contained in the traced RRC_MEAS_CTR message, as shown in Figure 184-2. Figure 184-2 IEs contained in RRC_MEAS_CTRL
event6a event6a 5. Place UE B in the center of the cell, and move UE A towards or away from UE B. Check whether the AMR mode changes during performance monitoring, as shown in Figure 184-3.
Issue 02 (2011-07-11)
184-3
Figure 184-3 AMR mode
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set CS Algorithm Switch to CS_AMRC_SWITCH.
----End
Example
//Activating AMR/WB-AMR Speech Rates Control SET UCORRMALGOSWITCH: CsSwitch=CS_AMRC_SWITCH-1; SET UQOSACT: AMRQosPerform=YES, UlQosAmrAdjSwitch=YES, UlQosWAmrAdjSwitch=YES, DlQosAmrAdjSwitch=YES, DlQosWAmrAdjSwitch=YES; MOD UTYPRABQUALITYMEAS: RabIndex=1, UlThd6a1=1, UlThd6a2=5, UlThd6b1=1, UlThd6b2=5, StaBlkNum5A=500, Thd5a=280, HangBlockNum5a=512, ThdEa=2, ThdEb=2; //Setting the AMR speech rate control parameters SET UCORRMPARA: ReservedSwitch0=RESERVED_SWITCH_0_BIT4-0; SET UAMRC: GoldMaxMode=NBAMR_BITRATE_6.70K, SilverMaxMode=NBAMR_BITRATE_6.70K, CopperMaxMode=NBAMR_BITRATE_6.70K; //Setting the AMR-WB speech rate control parameters SET UCORRMPARA: ReservedSwitch0=RESERVED_SWITCH_0_BIT3-0; SET UAMRCWB: GoldMaxMode=WBAMR_BITRATE_12.65K, SilverMaxMode=WBAMR_BITRATE_12.65K, CopperMaxMode=WBAMR_BITRATE_12.65K; //Deactivating AMR/WB-AMR Speech Rates Control SET UCORRMALGOSWITCH: CsSwitch=CS_AMRC_SWITCH-0;
184-4
Issue 02 (2011-07-11)
185 Configuring Overbooking on ATM Transmission
185
Prerequisite
l
Configuring Overbooking on ATM Transmission
This section describes how to activate, verify, and deactivate the optional feature WRFD-050405 Overbooking on ATM Transmission.
Dependencies on Hardware The backpressure and VP shaping mechanism need the support of the ATM interface board (AOU, UOI, or AEU for BSC6900) in the RNC. E1/T1 transmission is applied on the Iub interface. BTS3902E does not support this feature.
l l
Context
This feature improves the resource usage and provides a method for greatly saving OPEX on ATM transmission, especially on Iub interface, when deploying HSDPA services. Other strategies applied in overbooking are as follows: l l l RLC retransmission rate-based downlink congestion control Backpressure-based downlink congestion control VP shaping
Procedure
l Activation Procedure Activating RLC retransmission rate-based downlink congestion control Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the flow control switch.
For R99 BE services, select DRA_R99_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. For HSDPA BE services, select DRA_HSDPA_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. Activating backpressure-based downlink congestion control 1. 2. Run the BSC6900 MML command ADD PORTFLOWCTRLPARA. In this step, set Port protocol type to ATM and set other flow control parameters. Turn on the flow control switch. (1) Run the BSC6900 MML command ADD IMAGRP. In this step, set Flow control switch to ON. (2) Run the BSC6900 MML command ADD UNILNK. In this step, set Flow control switch to ON. (3) Run the BSC6900 MML command ADD FRALNK. In this step: Set Fractional link type to FRAATM. Set Flow control switch to ON. (4) Run the BSC6900 MML command ADD ATMLOGICPORT. In this step: Set Type of the logic port to Leaf. Set Flow control switch to ON. Activating VP shaping 1. 2. l Run the BSC6900 MML command ADD ATMLOGICPORT. In this step, set Type of the logic port to Leaf and Flow control switch to ON. Run the BSC6900 MML command ADD AAL2PATH to add a logical port. In this step, 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. 1. 2. 3. 4. 5. 6. 7. On the BSC6900 LMT, start downlink traffic and bandwidth tracing tasks on the Uu, Iub, and Iu interfaces. Register an R99 user UE1 in the HLR. Enable UE1 with streaming services and with both highest uplink rate and highest downlink rate of 384 kbit/s. Register an HSDPA user UE2 in the HLR. Enable UE2 with background services and with highest uplink rate of 384 kbit/s and highest downlink rate of 1450 kbit/s. Run the BSC6900 MML command ADD TRMMAP to map R99 services to the highpriority queue and HSDPA services to the low-priority queue. All AAL2 paths of the RNC are carried on an IMA port. Enable the port flow control when adding the IMA port. Enable UE1 and UE2 to stay in idle mode and camp on the test cell. The test cell must support HSDPA services. Use UE1 to perform PS streaming services, that is, use UE1 to download files from the FTP server. Expected result: The IMA port is not congested and UE1 downloads data at the highest rate.
185-2
Issue 02 (2011-07-11)
8.
Use UE2 to perform PS BE services, that is, use UE2 to download files from the FTP server. Expected result: The IMA port is congested and the backpressure function is triggered. The downloading rate of UE2 decreases and that of UE1 remains unchanged. This is because R99 services have a higher priority.
Deactivation Procedure Deactivating RLC retransmission rate-based downlink congestion control Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the flow control switch. For R99 BE services, deselect DRA_R99_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. For HSDPA BE services, deselect DRA_HSDPA_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. Deactivating backpressure-based downlink congestion control 1. 2. 3. 4. Run the BSC6900 MML command MOD IMAGRP. In this step, set Flow control switch to OFF. Run the BSC6900 MML command MOD UNILNK. In this step, set Flow control switch to OFF. Run the BSC6900 MML command MOD FRALNK. In this step, set Flow control switch to OFF. Run the BSC6900 MML command MOD ATMLOGICPORT. In this step, set Flow control switch to OFF.
----End
Example
//Activating RLC retransmission rate-based downlink congestion control SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-1&DRA_R99_DL_FLOW_CONTROL_SWIT CH-1; //Activating backpressure-based downlink congestion control ADD PORTFLOWCTRLPARA: FCINDEX=10, PORTPROTYPE=ATM; MOD IMAGRP: SRN=1, SN=14, BT=AOUa, IMAGRPN=1, FLOWCTRLSWITCH=ON, FCINDEX=100; ADD UNILNK: SRN=1, SN=14, UNILNKN=1, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF; ADD FRALNK: SRN=1, SN=14, FRALNKN=12, E1T1PN=0, TSBITMAP=TS1-1, FRALNKT=FRAATM, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF; ADD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUa, LPN=0, CARRYT=ATMLOGICPORT, UPPERVP=0, TXBW=512, RXBW=512, FLOWCTRLSWITCH=ON; //Activating VP shaping ADD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUa, LPN=0, CARRYT=ATMLOGICPORT, UPPERVP=0, TXBW=512, RXBW=512, FLOWCTRLSWITCH=ON; ADD AAL2PATH: ANI=0, PATHID=1, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=0, CARRYVPN=0, VPI=0, VCI=0, TXTRFX=0, RXTRFX=0, AAL2PATHT=HSPA; //Deactivating RLC retransmission rate-based downlink congestion control SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-0&DRA_R99_DL_FLOW_CONTROL_SWIT CH-0;
Issue 02 (2011-07-11)
185-3
//Deactivating backpressure-based downlink congestion control MOD IMAGRP: SRN=1, SN=14, BT=AOUa, IMAGRPN=1, FLOWCTRLSWITCH=OFF, FCINDEX=100; MOD UNILNK: SRN=1, SN=14, UNILNKN=1, FLOWCTRLSWITCH=OFF, OPSEPFLAG=OFF; MOD FRALNK: SRN=1, SN=14, FRALNKN=12, E1T1PN=0, TSBITMAP=TS1-1, FRALNKT=FRAATM, FLOWCTRLSWITCH=OFF, OPSEPFLAG=OFF; MOD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUa, LPN=0, CARRYT=IMA, CARRYIMAGRPN=1, TXBW=512, RXBW=512, RSCMNGMODE=SHARE, FLOWCTRLSWITCH=OFF;
185-4
Issue 02 (2011-07-11)
186 Configuring VoIP over HSPA/HSPA+
186
Prerequisite
l l
Configuring VoIP over HSPA/HSPA +
This section describes how to activate, verify, and deactivate the optional feature WRFD-010617 VoIP over HSPA/HSPA+.
Dependencies on Hardware This feature depends on the UE capability and the IP multimedia subsystem (IMS). Dependencies on Other Features In the case of VoIP over HSPA, the following features have been configured before this feature is activated: WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package. In the case of VoIP over HSPA, the WRFD-010686 CPC-DTX/DRX feature has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. The VoIP over HSPA/HSPA+ feature requires the IMS, and the IMS signaling transmission needs to be configured on the BSC6900.
Context
VoIP services can be carried on the DCH or HSPA. When VoIP services are carried on the DCH, a large quantity of resources are consumed. When VoIP services are carried on the HSPA, the system capacity significantly increases. When the Robust Header Compression (RoHC) technique is used, the data transmission efficiency of VoIP services is greatly improved.
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.
Issue 02 (2011-07-11)
186-1
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 IMS channel type to HSPA(UL_EDCH,DL_HSDSCH). Optional: Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the RoHC algorithm. In this step, select the CFG_PDCP_RFC3095_HC_SWITCH check box under the parameter Channel Configuration Strategy Switch. Optional: If VoIP services need to use the WRFD-01061403 HSUPA 2ms TTI feature, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter Service Mapping Strategy Switch. Go to Step 4. Optional: (1) If the NodeB is configured with the WCDMA Baseband Process Unit REV:b (WBBPb) and Enhanced Base Band Card (EBBC) boards, it is recommended that 10 ms HSUPA TTI be set for VoIP services. Run the BSC6900 MML command SET UFRC. In this step, select the EDCH_TTI_10ms check box under the parameter HSUPA TTI type of VOIP service. (2) If the NodeB is configured with the WCDMA Baseband Process Unit REV:d (WBBPd) and Enhanced Base Band Card REV:d (EBBCd) boards, either 10 ms or 2 ms HSUPA TTI can be set for VoIP services. a. To set 10 ms HSUPA TTI for HSUPA services, run the BSC6900 MML command SET UFRC to select the EDCH_TTI_10ms check box under the parameter HSUPA TTI type of VOIP service. To set 2 ms HSUPA TTI for HSUPA services, do as follows: 1) Run the BSC6900 MML command SET UFRC. In this step, select the EDCH_TTI_2ms check box under the parameter HSUPA TTI type of VOIP service. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the DRA_VOICE_SAVE_CE_SWITCH check box under the parameter Dynamic Resource Allocation Switch.
2.
3.
4.
b.
2)
5.
Optional: To use the WRFD-01061404 HSUPA 2ms/10ms TTI HO feature, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the DRA_VOICE_TTI_RECFG_SWITCH check box under the parameter Dynamic Resource Allocation Switch. To configure the EPF scheduling strategy, run the NodeB MML command SET MACHSPARA to set 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 unfolded list, double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG as shown in Figure 186-1 to trace Uu interface signaling messages.
6. l
186-2
Issue 02 (2011-07-11)
2.
Analyze the traced messages. If data shown in Figure 186-2 is traced on the Uu interface, the UE is in the CELL_DCH state. If data shown in Figure 186-3 is traced on the Uu interface, VoIP services are carried on HSPA/HSPA+. Figure 186-2 UE in CELL_DCH state
Issue 02 (2011-07-11)
186-3
Figure 186-3 VoIP services carried on HSPA/HSPA+
3.
If VoIP services are carried on HSPA or HSPA+, trace the RRC_RB_SETUP or RRC_RB_RECFG message on the Uu interface to check the type of carried TTI, as shown in Figure 186-4. Figure 186-4 Type of TTI carried in the message
NOTE
The services admitted before deactivation of this feature are not affected. The services admitted after the deactivation will not use this feature.
1.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, select the DCH(UL_DCH,DL_DCH) check box under the parameter VOIP channel type, and select the DCH(UL_DCH,DL_DCH) check box under the parameter IMS channel type.
----End
Example
//Activating VoIP over HSPA/HSPA+ //Operations on the BSC6900 side //Configuring VoIP/IMS to be carried on the E-DCH in the uplink and HSDSCH in the downlink SET UFRCCHLTYPEPARA: VoipChlType=HSPA, ImsChlType=HSPA; //Enabling the RoHC algorithm SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-1;
186-4
Issue 02 (2011-07-11)
//Enabling the HSUPA 2 ms scheduling algorithm SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; //Setting the HSUPA TTI type of the VoIP service to 10 ms TTI SET UFRC: VoipHsupaTti=EDCH_TTI_10ms; //Setting the HSUPA TTI type of the VoIP service to 2 ms TTI SET UFRC: VoipHsupaTti=EDCH_TTI_2ms; //Turning off the switch of saving CE resources SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_SAVE_CE_SWITCH-1; //Enabling dynamic adjustment of TTI reconfiguration for CS voice services SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_TTI_RECFG_SWITCH-1; //Setting the EPF scheduling strategy on the NodeB side SET MACHSPARA: SM=EPF; /*Deactivating VoIP over HSPA/HSPA+*/ //Operations on the BSC6900 side SET UFRCCHLTYPEPARA: VoipChlType=DCH, ImsChlType=DCH;
Issue 02 (2011-07-11)
186-5
187 Configuring Optimized Scheduling for VoIP over HSPA
187
Prerequisite
l l
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.
Dependencies on Hardware The CN and UE support voice over IP (VoIP). Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010611 HSDPA Enhanced Package and WRFD-010612 HSUPA Introduction Package have been configured before this feature is activated for VoIP over HSPA. WRFD-010611 HSDPA Enhanced Package and WRFD-010686 CPC- DTX/DRX have been configured before this feature is activated for VoIP over HSPA+.
Context
RAN10.0 supports VoIP over HSPA. To ensure the QoS of VoIP carried over HSPA, the nonscheduling method is used for the HSUPA scheduling, and the delay-sensitive (DS) scheduling algorithm is used for optimized HSDPA scheduling.
Procedure
l 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 query the configuration result.
l
Issue 02 (2011-07-11)
187 Configuring Optimized Scheduling for VoIP over HSPA
1. ----End
Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling Method to MAXCI(Max C/I), RR(Round Robin), or PF(PF).
Example
//Activation procedure SET MACHSPARA: LOCELL=0, SM=EPF; //Verification procedure LST MACHSPARA: LOCELL=0; //Deactivation procedure SET MACHSPARA: LOCELL=0, SM=PF;
187-2
Issue 02 (2011-07-11)
188 Configuring IMS Signaling over HSPA
188
Prerequisite
l l
Configuring IMS Signaling over HSPA
This section describes how to activate, verify, and deactivate the basic feature WRFD-010618 IMS Signaling over HSPA.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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 controlling this feature has been 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.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set IMS channel type to HSPA. In the Navigation Tree pane on the BSC6900 LMT, click the Trace tab. In the displayed Trace Navigation Tree pane, double-click UMTS Services. On the unfolded list, double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG as shown in Figure 188-1 to trace Uu interface signaling messages.
Issue 02 (2011-07-11)
2.
Analyze the traced messages. If data shown in Figure 188-2 is traced on the Uu interface, the UE is in the CELL_DCH state. If data shown in Figure 188-3 is traced on the Uu interface, VoIP services are carried on HSPA/HSPA+. Figure 188-2 UE in CELL_DCH state
188-2
Issue 02 (2011-07-11)
Figure 188-3 VoIP services carried on HSPA/HSPA+
3.
If VoIP services are carried on HSPA or HSPA+, trace the RRC_RB_SETUP or RRC_RB_RECFG message on the Uu interface to check the type of carried TTI, as shown in Figure 188-4. Figure 188-4 Type of TTI carried in the message
Deactivation Procedure 1. 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; //Deactivating IMS Signaling over HSPA. SET UFRCCHLTYPEPARA: ImsChlType=DCH;
Issue 02 (2011-07-11)
188-3
189 Configuring PDCP Header Compression (RoHC)
189
Prerequisite
l l l
Configuring PDCP Header Compression (RoHC)
This section describes how to activate, verify, and deactivate the optional feature WRFD-011501 PDCP Header Compression (RoHC).
Dependencies on Hardware The UE supports this feature. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
PDCP header compression (RoHC) mainly applies to VoIP services to reduce IP overhead. This feature provides an IP header compression mechanism, which aims to save the bandwidth over the Uu interface, thereby reducing occupancy of radio resources.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the CFG_PDCP_RFC3095_HC_SWITCH check box under the parameter Channel configuration strategy switch. Initiate UE tracing on the BSC6900 LMT. Establish a PS service on the UE. Verify that the value of the information element (IE) "bit1RfcInfo3095" contained in the message CRLC _SETUP_REQ by choosing pdcpSetupInfo > pdcpInfo > pdcpInfoBmp > bit1RfcInfo3095 as follows: If the value of the IE "bit1RfcInfo3095" is 1, this feature has been activated. If the value of the IE "bit1RfcInfo3095" is 0, this feature is not activated. l
Issue 02 (2011-07-11)
189 Configuring PDCP Header Compression (RoHC)
1.
Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the CFG_PDCP_RFC3095_HC_SWITCH check box under the parameter 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;
189-2
Issue 02 (2011-07-11)
190 Configuring CS Voice over HSPA/HSPA+
190
Prerequisite
l l
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+.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-010610 HSDPA Introduction Package, WRFD-010612 HSUPA Introduction Package, WRFD-010652 SRB over HSDPA, and WRFD-010636 SRB over HSUPA, in the case of CS voice over HSPA. WRFD-010686 CPC-DTX/DRX, in the case of CS voice over HSPA+.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE is of 3GPP Release 8 or higher and CS voice services are capable of being carried on HSPA/HSPA+. The BSC6900 and NodeB versions are RAN11.0 or later.
Context
The implementation of CS voice services over HSPA is introduced in 3GPP Release 8. In the case of CS voice services over HSPA, uplink CS voice packets are carried on the E-DCH and downlink CS voice packets are carried on the HS-DSCH. CS Voice over HSPA is intended for CS conversational AMR and AMR WB. CS streaming services are still carried on the DCH. The IMS for VoIP services is not required because the CS voice services over HSPA are carried on the CS domain of the CN.
Issue 02 (2011-07-11)
190-1

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. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to configure the uplink EDCH and downlink HSDSCH as the channels carrying HSPA CS services. In this step, select the HSPA(UL EDCH,DL HSDSCH) check box under the parameter CS voice channel type. 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, select the MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter Service Mapping Strategy Switch. Go to Step 3. Optional: Configure the HSUPA TTI type of the VoIP service. (1) If the NodeB is configured with the WCDMA Baseband Process Unit REV:b (WBBPb) and Enhanced Base Band Card (EBBC) boards, it is recommended that 10 ms HSUPA TTI be set for VoIP services. Run the BSC6900 MML command SET UFRC. In this step, select the EDCH_TTI_10ms check box under the parameter HSUPA TTI type of VOIP service. (2) If the NodeB is configured with the WCDMA Baseband Process Unit REV:d (WBBPd) and Enhanced Base Band Card REV:d (EBBCd) boards, either 10 ms or 2 ms HSUPA TTI can be set for VoIP services. a. To set 10 ms HSUPA TTI for HSUPA services, run the BSC6900 MML command SET UFRC to select the EDCH_TTI_10ms check box under the parameter HSUPA TTI type of VOIP service. To set 2 ms HSUPA TTI for HSUPA services, do as follows: 1) Run the BSC6900 MML command SET UFRC. In this step, select the EDCH_TTI_2ms check box under the parameter HSUPA TTI type of VOIP service. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select the DRA_VOICE_SAVE_CE_SWITCH check box under the parameter Dynamic Resource Allocation Switch.
2.
3.
b.
2)
4.
Optional: If the dynamic adjustment of CS voice services over HSUPA from 2 ms TTI to 10 ms TTI is required, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the DRA_VOICE_TTI_RECFG_SWITCH check box under the parameter Dynamic Resource Allocation Switch. To configure the EPF scheduling strategy, run the NodeB MML command SET MACHSPARA to set 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
5. l
190-2
unfolded list, double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box, select RRC_RB_SETUP and RRC_RB_RECFG as shown in Figure 190-1 to trace Uu interface signaling messages. Figure 190-1 Uu Interface Trace dialog box
2.
Analyze the traced messages. If data shown in Figure 190-2 is traced on the Uu interface, the UE is in CELL_DCH state. If the data traced on the Uu interface is displayed, as shown in Figure 190-3, CS voice services are carried on HSPA/HSPA+. Figure 190-2 UE in CELL_DCH state
Figure 190-3 CS voice services carried on HSPA/HSPA+
3.
If CS voice services are carried on HSPA or HSPA+, trace the RRC_RB_SETUP or RRC_RB_RECFG message on the Uu interface to check the type of carried TTI, as shown in Figure 190-4.
Issue 02 (2011-07-11)
Figure 190-4 Type of TTI carried in the message
NOTE
The services admitted before deactivation of this feature are not affected. The services admitted after the deactivation will not use this feature.
1.
Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, select the DCH(UL_DCH,DL_DCH) check box under the parameter CS voice channel type.
----End
Example
/*Activation procedure*/ //Operations on the BSC6900 side //Configuring CS voice services to be carried on the EDCH in the uplink and HS-DSCH in the downlink SET UFRCCHLTYPEPARA: CSVoiceChlType =HSPA; //Enabling the HSUPA 2 ms scheduling algorithm SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1; //Setting the HSUPA TTI type of the VoIP service to 10 ms TTI SET UFRC: VoipHsupaTti=EDCH_TTI_10ms; //Setting the HSUPA TTI type of the VoIP service to 2 ms TTI SET UFRC: CSVoiceHsupaTti=EDCH_TTI_2ms; //Turning off the switch of saving CE resources SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_SAVE_CE_SWITCH-1; //Enabling dynamic adjustment of TTI reconfiguration for CS voice services SET UCORRMALGOSWITCH: DraSwitch=DRA_VOICE_TTI_RECFG_SWITCH-1; //Setting the EPF scheduling strategy on the NodeB side SET MACHSPARA: SM=EPF; /*Deactivating CS Voice over HSPA/HSPA+*/ //Operations on the BSC6900 side SET UFRCCHLTYPEPARA: CSVoiceChlType=DCH;
190-4
Issue 02 (2011-07-11)
191 Configuring Cell ID + RTT Function Based LCS
191
Prerequisite
l l l l
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.
Dependencies on Hardware If SAS-CENTRIC locating is required, SAS equipment has been configured. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Others Prerequisites The NodeB and the BSC6900 software versions are RAN3.0 or later, and the BSC6900 supports the 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 + Round Trip Time (RTT) locating method is to directly use the geographical center of the coverage area of the reference cell as the locating result. To achieve high locating accuracy, the BSC6900 demands RTT measurement in all cells in the active set and requests the UE to perform locating measurement on the corresponding cells. By means of the two types of measurement, the BSC6900 calculates the time of arrival (TOA) of signal from the cell antenna to the UE. By multiplying the TOA by the velocity of light, the BSC6900 obtains the distance between a certain cell and the UE. If three TOA circles intersect, the BSC6900 can obtain the accurate location of the UE.
Issue 02 (2011-07-11)
191-1
Procedure
l Activation Procedure 1. 2. 3. Optional: If inter-RNC locating is required, the Iur interface needs to be configured. For details, see 195 Configuring LCS over Iur. Optional: If SAS-CENTRIC mode needs to be supported, the Iupc interface is required. For details, see 196 Configuring Iupc Interface for LCS Service. Run the BSC6900 MML command SET USMLC to set the parameters of the SMLC algorithm. In this step, set UE Positioning Method, CELLID+RTT Method Type, and Location Working Mode to appropriate values. Run the BSC6900 MML command ADD USMLCCELL to set the following location information parameters of the cell: Cell location configuration type Geographical location information about the antenna: Cell Antenna Latitude Cell Antenna Altitude Cell Antenna Longitude Cell coverage information: Cell Antenna Max Coverage Cell Antenna Orientation Cell Antenna Opening l Verification Procedure 1. Initiate Iu, Iub, and Uu interface message tracing, as shown in Figure 191-1, Figure 191-2, and Figure 191-3 respectively. Figure 191-1 Iu Interface Trace dialog box
4.
191-2
Issue 02 (2011-07-11)
2. 3.
Use a UE to access the cell and enable the CN to send a locating request message. The message LOCATION REPORTING CONTROL and LOCATION REPORT are traced on the Iu interface, as shown in Figure 191-4 and Figure 191-5.
Issue 02 (2011-07-11)
191-3
Figure 191-4 LOCATION REPORTING CONTROL
191-4
Issue 02 (2011-07-11)
Figure 191-5 LOCATION REPORT
4.
The messages traced on the Iub interface show that the procedure Dedicated Measurement Initiation is performed on all links in the active set and that the value of Dedicated Measurement Type is Round Trip Time, as shown in Figure 191-6 and Figure 191-7.
Issue 02 (2011-07-11)
191-5
Figure 191-6 Dedicated Measurement Type
Figure 191-7 Round Trip Time
5.
From the traced Uu interface messages, you can see the information about the UE RxTx time difference measurement, which is a type of internal measurement (if the UE supports UE Rx-Tx time difference type 2 measurement, the locating method for RxTx time difference type 2 measurement is adopted), as shown in Figure 191-8 and Figure 191-9.
191-6
Issue 02 (2011-07-11)
Figure 191-8 UE Rx-Tx time difference
Figure 191-9 UE Rx-Tx time difference type 1
Deactivation Procedure 1. Run the BSC6900 MML command SET USMLC to deactivate the CELLID+RTT locating method. In this step, deselect the CELLID_RTT check box under parameter UE Positioning Method.
----End
Example
//Activating Cell ID + RTT Function Based LCS //Setting the parameters of the SMLC algorithm SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-1&OTDOA-0&AGPS-0, CELLIDRTTMethodType=UE_ASSISTED, ForcedSHOSwitch=ON, IntraRelThdFor1A=2, IntraRelThdFor1B=2, TrigTime1A=D10, TrigTime1B=D10, SHOQualmin=-20, LcsWorkMode=RNC_CENTRIC; //Setting 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,
Issue 02 (2011-07-11)
191-7
MaxAntennaRange=5678, AntennaOrientation=567, AntennaOpening=456, CellAverageHeight=6789; //Deactivating Cell ID + RTT Function Based LCS SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-0&OTDOA-0&AGPS-0;
191-8
Issue 02 (2011-07-11)
192 Configuring OTDOA Based LCS
192
Prerequisite
l l l l
Configuring OTDOA Based LCS
This section describes how to activate, verify, and deactivate the optional feature WRFD-020802 OTDOA Based LCS.
Dependencies on Hardware The NodeB is configured with the Universal Satellite Card and Clock Unit (USCU) board that is equipped with a GPS card. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Others Prerequisites 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, BSC6900 initiates and traces the SFN-SFN observed time difference measurement. BSC6900 calculates the relative time difference (RTD) of the cell related to positioning based on the latest measurement reports (MRs). After BSC6900 receives a LOCATON REPORT CONTROL message, it requests the UE to perform SFN-SFN observed time difference measurement if the IPDL-OTDOA positioning method is used. After receiving the corresponding MRs, BSC6900 calculates the location of the UE. For accurate location calculation, BSC6900 may request the NodeB to perform RTT measurement and request the UE to perform Rx-Tx time difference measurement.
Issue 02 (2011-07-11)
192-1
Procedure
l Activation Procedure 1. 2. Optional: Configure the Iur interface if inter-RNC locating is required. For details, see 195 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 to appropriate values.
NOTE
Location Working Mode must be set to RNC_CENTRIC(RNC CENTRIC Mode).
3.
Run the BSC6900 MML command ADD USMLCCELL to add the location information about a cell. In this step, set the following parameters to appropriate values: Cell Location Setting Type Parameters associated with the geographical location information about the antenna system Cell Antenna Longitude Cell Antenna Latitude Cell Antenna Altitude Parameters associated with the cell coverage information Cell Antenna Max Coverage Cell Antenna Opening Cell Antenna Orientation
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 to appropriate values. Check whether the parameters required for positioning are correctly set. Run the BSC6900 MML command LST USMLC to query SMLC algorithm parameter settings. Run the BSC6900 MML command LST USMLCCELL to query the settings of the location parameters of a cell. Run the BSC6900 MML command LST UCELLGPSFRMTIMING to query the parameter settings related to UTRAN GPS cell frame timing measurement.
Deactivation Procedure 1. Run the BSC6900 MML command SET USMLC to deactivate the OTDOA-based location service.
----End
Example
//Activating OTDOA Based LCS //Setting the parameters for the SMLC algorithm SET USMLC: SmlcMethod=OTDOA-1, OTDOAMethodType=UE_BASED, LcsWorkMode=RNC_CENTRIC; //Setting the location information parameters of the cell
192-2
Issue 02 (2011-07-11)
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; //Setting parameters related to UTRAN GPS cell frame timing measurement ADD UCELLGPSFRMTIMING: CellId=80, StartFlag=ACTIVE; //Deactivating OTDOA Based LCS SET USMLC: SmlcMethod=OTDOA-0;
Issue 02 (2011-07-11)
192-3
193 Configuring A-GPS Based LCS
193
Prerequisite
l
Configuring A-GPS Based LCS
This section describes how to activate, verify, and deactivate the optional feature WRFD-020803 A-GPS Based LCS.
Dependencies on Hardware When the RNC-CENTRIC locating service is required: If a Global Positioning System (GPS) receiver is configured on the BSC6900 side, the BSC6900 must be configured with the General Clock Unit with GPS REV:a (GCGa) board. If a GPS receiver is configured on the NodeB side, the NodeB must be configured with the Universal Satellite card and Clock Unit (USCU) and WCDMA GPS Receiving Unit (WGRU), and all the equipment (including the GPS antenna system) must be properly installed and connected. When the SAS-CENTRIC locating service is required, the BSC6900 must be configured with a Stand-Alone SMLC (SAS) device. SMLC refers to Serving Mobile Location Center.
NOTE
If A-GPS positioning is required, the GPS receiver does not need to be installed in BSC6900 side or NodeB side.
l l l
Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites NodeB V200R013 supports this feature while NodeB V100R013 does not support this feature. The UE supports UE-based A-GPS positioning or UE-assisted A-GPS positioning or both. The CN can send positioning requests.
Issue 02 (2011-07-11)
193-1
Context
A-GPS positioning is an application of GPS positioning in the WCDMA network. In open areas, A-GPS positioning can provide high positioning sensitivity, shorten positioning time, and save power. The location information about the GPS receiver can be automatically searched by the GPS receiver itself or be configured by a user. l If the accurate location information (to be provided by the surveying and mapping authorities) about the antenna of the GPS receiver can be obtained, it is recommended that the information be specified when the GPS receiver is being configured. In this way, the GPS receiver can quickly search for the satellite group in the area where it is located, and accurately calculate the differential GPS information. If the accurate location information about the antenna of the GPS receiver cannot be obtained, the auto search mode can be selected.
Procedure
NOTE
The BSC6900 and NodeB must be configured with the related data to activate this feature.
Activation Procedure on the BSC6900 Side 1. 2. Optional: If inter-RNC locating is required, configure the Iur interface by referring to 195 Configuring LCS over Iur. Optional: If the GPS positioning method in SAS-CENTRIC mode is required, configure the Iu-PC interface by referring to 196 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 to appropriate values. Run the BSC6900 MML command ADD USMLCCELL to set the parameters related to cell location information to appropriate values. Cell Location Setting Type Parameters associated with the geographical location information about the antenna system Cell Antenna Longitude Cell Antenna Latitude Cell Antenna Altitude Parameters associated with the cell coverage information Cell Antenna Max Coverage Cell Antenna Opening Cell Antenna Orientation
3.
4.
5.
6.
In RNC-CENTRIC mode, run the command ADD GPS to set the parameters related to the GPS receiver. In this step, set GPS ID, GPS type, GPS antenna latitude, GPS antenna longitude, and GPS antenna altitude to appropriate values. In RNC-CENTRIC mode, run the command ACT GPS to activate the specified GPS receiver. In this step, set AGPS ID and Type to appropriate values. Optional: 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 to appropriate values. Optional: Run the BSC6900 MML command STR POSAVE with Maximum time for posave set to 12. Then, check the single point positioning results of the GPS receiver in the \bam\common\fam\smlc directory.
7. 8.
9.
Activation Procedure for NodeB V200R013

NOTE
In RNC-CENTRIC mode, a GPS receiver can be configured on the NodeB side as required. If a GPS receiver is configured on the NodeB side, the NodeB must be configured with the USCU and WGRU, and all the equipment (including the GPS antenna system) must be properly installed and connected.
1.
Run the NodeB MML command ADD BRD to add a USCU board. Set Cabinet No., Subrack No., and Slot No. to appropriate values based on the actual location of the USCU board. Set Board Type to USCU.
2. 3. 4.
Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Run the NodeB MML command ADD GPS to add a GPS clock link. Run the NodeB MML command MOD GPSPOS to add a GPS receiver. If Way to Get Position is set to USER_CONFIG(User Config), set Antenna Longitude, Antenna Latitude, and Antenna Altitude to appropriate values. If Way to Get Position is set to SEARCH_WITH_DURATION(Search with duration), set Duration to an appropriate value. If Way to Get Position is set to SEARCH_WITH_PRECISION(Search with precision), set Precision to an appropriate value.
Verification Procedure Verification Procedure on the BSC6900 Side 1. Initiate Iu and Uu interface tracing, as shown in Figure 193-1 and Figure 193-2 respectively.
Issue 02 (2011-07-11)
193-3
Figure 193-1 Iub interface tracing
2. 3.
Make a UE access the network and enable the CN to send a positioning request. Over the Iu interface, you can view the Location Reporting Control and Location Report messages, as shown in Figure 193-3 and Figure 193-4.
193-4
Issue 02 (2011-07-11)
Figure 193-3 LOCATION REPORTING CONTROL
Issue 02 (2011-07-11)
193-5
Figure 193-4 LOCATION REPORT
4.
The Uu interface tracing messages contain the information about A-GPS positioning measurement, as shown in Figure 193-5 and Figure 193-6. Figure 193-5 ue-positioning-GPS-AssistanceData
193-6
Issue 02 (2011-07-11)
Figure 193-6 GPS-MeasurementParam
Verification Procedure for NodeB V200R013 1. Run the NodeB MML command DSP BRD to query the status of the USCU board and status of the GPS receiver. In the command output displayed on the LMT, check whether the USCU board and the GPS receiver are normal. Run the NodeB MML command DSP GPS to display the information of a GPS receiver, including receiver position, receiver version, receiver status, and receiver hardware information. In the command output displayed on the LMT, check whether the location of the GPS receiver is locked up and whether the operating state of the GPS receiver is normal. Run the BSC6900 MML command SET USMLC to deactivate the A-GPS location service. In this step, deselect the AGPS check box under parameter UE Positioning Method.
2.
----End
Example
/*Activating A-GPS Based LCS*/ /*Operations on the BSC6900 side* //Setting the type of clock board to GCGa SET CLKTYPE:CLKTYPE=GCGa; //Setting the parameters for the SMLC algorithm SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-0&OTDOA-0&AGPS-1, AGPSMethodType=UE_ASSISTED, UeAssAgpsAssDataSwitch=REFERENCE_TIME_FOR_GPS-1&REFERENCE_LOCATION_FOR_GP S-1&DGPS_CORRECT-0&GPS_NAVGMODEL-1&GPS_IONOSPHERIC_MODEL-1&GPS_UTC_MODEL1&GPS_ALMANAC-1&GPS_ACQ_ASSIST-1&GPS_REALTIME_INTEGRITY-1,LcsWorkMode=RNC _CENTRIC; //Setting the 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; //Setting the parameters of the GPS receiver ADD GPS: AGPSRECEIVERID=0, AGPSRECEIVERTYPE=RNC, GCDF=DEG, MTRLGY=MET,
Issue 02 (2011-07-11)
193-7
LATITUDE=31243596, LONGITUDE=121590603, ALTITUDE=20; ADD GPS: AGPSRECEIVERID=1, AGPSRECEIVERTYPE=NODEB, CellId=82, GCDF=DEG, MTRLGY=MET, LATITUDE=31243596, LONGITUDE=121590603, ALTITUDE=20; //Activating the specified GPS receiver ACT GPS: AGPSRECEIVERID=0, ACTTYPE=BOTH; //Setting parameters related to UTRAN GPS cell frame timing measurement ADD UCELLGPSFRMTIMING: CellId=80, StartFlag=ACTIVE; /*Operations on the NodeB V200R013 side* SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; ADD GPS: SN=0; MOD GPSPOS: WPOS=USER_CONFIG, LONG=160000000, LAT=80000000, ALT=900; //Deactivating A-GPS Based LCS SET USMLC: SmlcMethod=CELLID_CENTER-0&CELLID_RTT-0&OTDOA-0&AGPS-0;
193-8
Issue 02 (2011-07-11)
194 Configuring LCS Classified Zone
194
Prerequisite
l l l l License
Configuring LCS Classified Zone
This section describes how to activate, verify, and deactivate the optional feature WRFD-020804 LCS Classified Zone.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. The license controlling this feature has been activated. Other Prerequisites The core network (CN) supports this feature.
Context
This feature defines a classified zone. Once the UE enters or exits the zone, the RNC automatically reports the service area identity (SAI) of the UE.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCZ to add a classified zone.
NOTE
l In this step, you need to set the parameters Cn Operator Index, Location Area Code, Service Area Code, and Classified Zone ID. More than one classified zone can be set for each operator. l Before running the ADD UCZ 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. Initiate Iub interface message tracing on the BSC6900 LMT, as shown in Figure 194-1.
Issue 02 (2011-07-11)
2.
Enable the UE to establish a service of any type. Move the UE from cell A (whose LAC and SAC are 9513 and 272 respectively) to cell B (whose LAC and SAC are 9514 and 273 respectively), to add cell B to the active set. If a LOCATION REPORT message is displayed, this feature has been activated. If the value of the information element (IE) "Cause" in the LOCATION REPORT message is "User Restriction Start Indication", the UE enters the classified zone. The SAI of the UE is also contained in the message, as shown in Figure 194-2.
194-2
Issue 02 (2011-07-11)
Figure 194-2 LOCATION REPORT message
3.
Remove cell B from the active set by performing a handover or Serving Radio Network Subsystem (SRNS) relocation. If a LOCATION REPORT message is displayed, this feature has been activated. If the cause value of the LOCATION REPORT message is displayed as "User Restriction End Indication", the UE exits the classified zone. The SAI of the UE is also contained in the LOCATION REPORT message.
Deactivation Procedure 1. Run the BSC6900 MML command RMV UCZ to remove the classified zone from all operators at the RNC.
----End
Example
//Activating LCS Classified Zone ADD UCZ: CnOpIndex=0, LAC=9513, SAC=272, CZ=0; ADD UCZ: CnOpIndex=0, LAC=9514, SAC=273, CZ=1; //Deactivating LCS Classified Zone RMV UCZ: CnOpIndex=0, CZ=0; RMV UCZ: CnOpIndex=0, CZ=1;
Issue 02 (2011-07-11)
194-3
195 Configuring LCS over Iur
195
Prerequisite
l l Dependencies on Hardware
Configuring LCS over Iur
This section describes how to activate, verify, and deactivate the optional feature WRFD-020805 Configuring LCS over Iur.
This feature does not have any special requirements for hardware. Dependencies on Other Features The following feature has been configured before this feature is activated: WRFD-020801 Cell ID + RTT Function Based LCS or WRFD-020803 A-GPS Based LCS. l l License The license controlling this feature has been activated. Others Prerequisites The UE and the neighboring RNC (NRNC) support this feature. This feature is used only in RNC-CENTRIC mode.
Context
This feature enables Huawei RAN to provide location services (LCS) over the Iur interface, extending the LCS area. It enables exchange of cell information and GPS assistance information over the Iur interface.
Procedure
NOTE
In this procedure, you need to set the positioning method and add the geographical information about the cell at the RNC. For cell information exchange over the Iur interface, geographical information about a neighboring cell must be configured at the NRNC.
1.
Run the BSC6900 MML command SET USMLC to set the SMLC algorithm parameters, In this step, set UE Positioning Method and Location Working Mode. Configure cell information exchange over the Iur interface.
2.
Issue 02 (2011-07-11)
(1) Run the BSC6900 MML command ADD UIURCOMMSCCP. In this step, set the subrack number and slot number of the SPU subsystem that processes information exchange on the BSC6900. (2) Run the BSC6900 MML command ADD USMLCCELL to set the parameters related to cell location information. The parameters include: Cell location configuration type Geographical location information about the antenna: Cell Antenna Latitude Cell Antenna Altitude Cell Antenna Longitude Cell coverage information: Cell Antenna Max Coverage Cell Antenna Orientation Cell Antenna Opening and so on 3. Configure GPS assistance information exchange. (1) Run the BSC6900 MML command ADD UIURCOMMSCCP. In this step, set the subrack number and slot number of the SPU subsystem that processes information exchange on the BSC6900. (2) For GPS information exchange over the Iur interface, run the BSC6900 MML command ADD GPS to add a GPS receiver to the NRNC. In this step, set GPS type to NRNC_RNC(Nearby RNC), indicating that the GPS receiver is installed at the NRNC.
NOTE
l If a GPS receiver on the NRNC side is installed on the NodeB, set GPS type to NRNC_NODEB(NodeB in RNC). l Before adding a GPS receiver to the NRNC, ensure that the GPS receiver is installed at the NRNC. Run the BSC6900 MML command ADD GPS to add the GPS receiver. In this step, set GPS type to RNC(Local RNC) (when the GPS receiver is installed at the RNC) or to NODEB(Local NodeB) (when the GPS receiver is installed at the NodeB).
(3) If a GPS receiver needs to be configured on the BSC6900 side, run the BSC6900 MML command SET CLKTYPE with the type of clock board in the BSC6900 set to GCGa. (4) Run the BSC6900 MML command ACT GPS to activate the GPS reference receiver. (5) Run the BSC6900 MML command ADD UCELLGPSFRMTIMING to set parameters related to UTRAN GPS cell frame timing measurement to appropriate values. In this step, set Cell ID and GPS Frame Timing Active Flag. l Verification Procedure 1. Start Iur interface tracing on the BSC6900 LMT, as shown in Figure 195-1.
195-2
Issue 02 (2011-07-11)
Figure 195-1 Iur Interface Trace dialog box
2.
Check the information traced over the Iur interface. You can find an information exchange initiation procedure. In this procedure, the local RNC sends the NRNC an INFORMATION EXCHANGE INITIATION REQUEST message, in which the value of Information Type is GPS Information or DGPS. The NRNC sends the local RNC INFORMATION EXCHANGE INITIATION RESPONSE and INFORMATION REPORT messages, which contain GPS assistance data, as shown in Figure 195-2. Figure 195-2 GPS assistance data carried in the INFORMATION REPORT message
NOTE
You can see INFORMATION EXCHANGE INITIATION REQUEST and INFORMATION EXCHANGE INITIATION RESPONSE messages only after the BSC6900 MML command ACT GPS is executed.
Issue 02 (2011-07-11)
195-3
3. 4. 5.
Establish a service, and then perform a soft handover over the Iur interface. Enable the CN to send a LOCATION REPORTING CONTROL message with the cause "DIRECT". Check messages traced over the Iur interface. You can find an Information Exchange Initiation procedure. In this procedure, the local RNC sends the NRNC an INFORMATION EXCHANGE INITIATION REQUEST message, in which the value of Information Type is UTRAN Access Point Position with Altitude, as shown in Figure 195-3. The NRNC sends the local RNC an INFORMATION EXCHANGE INITIATION RESPONSE message, which contains geographical information about the neighboring cell over the Iur interface, as shown in Figure 195-4. Figure 195-3 INFORMATION EXCHANGE INITIATION REQUEST
195-4
Issue 02 (2011-07-11)
Figure 195-4 INFORMATION EXCHANGE INITIATION RESPONSE
6.
Check messages traced over the Iur interface. You can find DEDICATED MEASUREMENT INITIATION REQUEST and DEDICATED MEASUREMENT INITIATION RESPONSE messages, as shown in Figure 195-5 and Figure 195-6 respectively. In the former message, the value of Dedicated Measurement Type is Round Trip Time. Figure 195-5 DEDICATED MEASUREMENT INITIATION REQUEST
Issue 02 (2011-07-11)
195-5
Figure 195-6 DEDICATED MEASUREMENT INITIATION RESPONSE
Deactivation Procedure 1. Run the BSC6900 MML command DEA GPS to deactivate the GPS receiver. Alternatively, run the BSC6900 MML command RMV GPS to remove the GPS receiver from the NRNC. GPS information exchange over the Iur interface is thereby disabled. Run the BSC6900 MML command RMV UIURCOMMSCCP to deactivate LCS over Iur.
2. ----End
Example
/*Activating LCS over Iur*/ //Setting the positioning method SET USMLC: SmlcMethod=CELLID_RTT-1&OTDOA-0&AGPS-0; /*Configuring cell information exchange over the Iur interface*/ ADD UIURCOMMSCCP: SRN=0, SN=1; ADD USMLCCELL: RNCId=29, CellId=1, CellLocCfgType=CELL_ANTENNA, GCDF=DEG, MTRLGY=MET, AntennaLatitudeDegree=31245560, AntennaLongitudeDegree=121588234, AntennaAltitudeMeter=20, MaxAntennaRange=2000, AntennaOrientation=0, AntennaOpening=1200; CellAverageHeight=25; /*Configuring GPS assistance information exchange.*/ ADD UIURCOMMSCCP: SRN=0, SN=1; ADD GPS: AGPSRECEIVERID=0, AGPSRECEIVERTYPE=NRNC_RNC, RNCID=1, GCDF=DEG, MTRLGY=MET, LATITUDE=31245560, LONGITUDE=121588230, ALTITUDE=21; SET CLKTYPE: CLKTYPE=GCGa; ACT GPS: AGPSRECEIVERID=0, ACTTYPE=BOTH; ADD UCELLGPSFRMTIMING: CellId=1, StartFlag=ACTIVE; //Deactivating LCS over Iur RMV GPS: AGPSRECEIVERID=0;
195-6
Issue 02 (2011-07-11)
196 Configuring Iupc Interface for LCS Service
196
Prerequisite
l l
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.
Dependencies on Hardware IP interface boards of the BSC6900 support this feature. A Stand-Alone SMLC (SAS) is configured. Dependencies on Other Features The following features have been configured before this feature is activated: WRFD-020801 Cell ID + RTT Function Based LCS has been configured if the operator employs the Cell ID+RTT algorithm. WRFD-020803 A-GPS Based LCS has been configured if the operator employs the A-GPS algorithm.
l l
License The license controlling this feature has been activated. Other Prerequisites The UE supports at least one of the following positioning methods: UE-assisted CELLID+RTT UE-based A-GPS UE-assisted A-GPS The global data is configured by performing the following procedure: 1. 2. 3. 4. Configuring the Basic Data Configuring the OPC and DPC Configuring the Area Information Configuring the M3UA Local and Destination Entities
Physical layer data and data link layer data are configured by performing the following procedure:
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 BSC6900 and the SAS. The transport network layer data on the Iupc interface needs to be configured at the BSC6900. When the BSC6900 is connected to multiple SASs through IP transmission, you need to configure this feature on each Iupc interface. One BSC6900 can be connected to a maximum of four SASs simultaneously.
NOTE
Before configuring the Iupc interface data, familiarize yourself with Protocol Structure and Links on the Iupc Interface.
Procedure
l Activation Procedure 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 commands 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 BSC6900 MML command ADD SCTPLNK to add an SCTP link. To add multiple SCTP links, run this command for each SCTP link to be added. If Signalling link mode is set to Server at the SAS, set Signalling link mode to CLIENT at the BSC6900. If Signalling link mode is set to CLIENT at the SAS, set Signalling link mode to Server at the BSC6900. Set Application type to M3UA. 4. Run the BSC6900 MML command ADD M3LKS to add an M3UA link set. If Local entity type is set to M3UA_IPSP, set Work mode of the M3UA link set to M3UA_IPSP. If Local entity type is set to M3UA_ASP and Destination entity type is set to M3UA_SP, set Work mode to M3UA_IPSP. If Local entity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, set Work mode to M3UA_ASP. 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, run this command repeatedly. Run the BSC6900 MML command ADD USAS to add the SAS. Run the BSC6900 MML command SET USMLC to enable SAS-CENTRIC positioning based on CELLID + RTT or AGPS. For details, see 191 Configuring Cell ID + RTT Function Based LCS or 193 Configuring A-GPS Based LCS. Perform the verification procedures by referring to 191 Configuring Cell ID + RTT Function Based LCS or 193 Configuring A-GPS Based LCS.
3.
196-2
Deactivation Procedure 1. Perform the deactivation procedures by referring to 191 Configuring Cell ID + RTT Function Based LCS or 193 Configuring A-GPS Based LCS.
----End
Example
//Activating Iupc Interface for LCS Service //Adding the DSP data that corresponds to the SAS ADD N7DPC:DPX=4, SPDF=WNF, DPC=8345, STP=OFF, SLSMASK=B0000, NEIGHBOR=YES, NAME="SAS", DPCT=IUPC, PROT=ITUT, BEARTYPE=M3UA, SPX=4; //Adding the M3LE that corresponds to the SAS ADD M3LE:LENO=0, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME="IUPC", SPX=4; //Adding the M3DE that correspond to the SAS ADD M3DE:DENO=0, LENO=0, DPX=4, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME="IUPC"; //Adding an SCTP link ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=0, MODE=SERVER, APP=M3UA, LOCIP1="10.10.10.10", PEERIP1="10.10.11.11", PEERPN=3000, LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; //Adding an M3UA link set ADD M3LKS: SIGLKSX=0, DENO=0, NAME="IUPC"; //Adding an M3UA route ADD M3RT: DENO=0, SIGLKSX=0, NAME="IUPC"; //Adding an M3UA link ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=0, SCTPLNKN=0, NAME="IUPC"; //Adding the SAS ADD USAS: CnOpIndex=0, SasId=0, Dpx=4; //Setting SMLC-related parameters SET USMLC: SmlcMethod=CELLID_RTT-1, AGPSMethodType=UE_ASSISTED, LcsWorkMode=SAS_CENTRIC;
Issue 02 (2011-07-11)
196-3
197 Configuring RAN Sharing Introduction Package
197
Prerequisite
l l
Configuring RAN Sharing Introduction Package
This section describes how to activate, verify and deactivate the optional feature WRFD-021304 RAN Sharing Introduction Package.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature cannot be used together with the feature WRFD-021311 MOCN Introduction Package.
Context
This feature enables multiple operators to share the same set of RAN equipment but have their own independent cells. The same set of RAN equipment can provide different operators with rich and differentiated services.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set RAN Sharing Support to YES to turn on the RAN sharing switch. Run the BSC6900 MML command ADD UCNOPERATOR twice to add the primary and secondary operators respectively. Run the BSC6900 MML command ADD UCNOPERGROUP twice to add an operator group respectively for the primary and secondary operators. Run the BSC6900 MML command ADD OPC for multiple times to add OSPs for primary and secondary operators.
Issue 02 (2011-07-11)
197-1

NOTE
Primary and secondary operators can have their own OSPs for the same BSC6900. l Primary and secondary operators can share the same Network ID when required. l When primary and secondary operators share the same Network ID, they must use the same OSP code bits but different OSP code[Whole Number]. l When primary and secondary operators do not share Network ID, they can have different values for OSP code bits.
5. 6. 7. 8.
Run the BSC6900 MML command ADD N7DPC for multiple times to add DSPs for primary and secondary operators. Configure Iu data for the primary and secondary operators. Run the BSC6900 MML command ADD UCNNODE for multiple times to add CN nodes for the primary operator. Configure Iub data and add a dedicated cell.
NOTE
There are two types of RAN sharing: l NodeBs are independently deployed by operators. l NodeBs are shared by operators and cells are not shared by operators.
Verification Procedure If the CNs of the primary and secondary operators are working properly, dedicated cells can be set up for these operators, and the IDs of these operators can be displayed on the UE, this feature has been activated.
Deactivation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set RAN Sharing Support to NO to turn off the RAN sharing switch.
----End
Example
//Activating RAN Sharing Introduction Package //Setting the sharing mode for the operators SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES; //Adding a primary operator ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502", MNC="10", CnOpIndex=0; //Adding a secondary operator ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310", MNC="30", CnOpIndex=1; //Adding an operator group for the primary operator ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE, CnOpIndex1=0; //Adding an operator group for the secondary operator ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE, CnOpIndex1=1; //Adding the OSP for the primary operator ADD OPC: NAME="PRIM", SPX=0, NI=INT, SPCBITS=BIT14, SPDF=WNF, SPC=111;
197-2
Issue 02 (2011-07-11)
//Adding the OSP for a secondary operator ADD OPC: NAME="SEC", SPX=1, NI=NAT, SPCBITS=BIT24, SPDF=WNF, SPC=222; //Adding DSPs for the primary operator ADD N7DPC: NAME="PRIMCS", DPX=0, SPX=0, BEARTYPE=M3UA; ADD N7DPC: NAME="PRIMPS", DPX=1, SPX=0, BEARTYPE=M3UA; //Adding DSPs for a secondary operator ADD N7DPC: NAME="PRIMCS", DPX=2, SPX=1, BEARTYPE=M3UA; ADD N7DPC: NAME="PRIMPS", DPX=3, SPX=1, BEARTYPE=M3UA; SPDF=WNF, DPC=333, DPCT=IUCS, SPDF=WNF, DPC=444, DPCT=IUPS, SPDF=WNF, DPC=555, DPCT=IUCS, SPDF=WNF, DPC=666, DPCT=IUPS,
//Adding CN nodes for the primary operator ADD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R99, SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, AvailCap=60000, TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1, Switch3GPP25415CR0125=OFF; ADD UCNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=1, CNProtclVer=R99, SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, AvailCap=60000; //Adding CN nodes for a secondary operator ADD UCNNODE: CnOpIndex=1, CNId=2, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R99, SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, AvailCap=60000, TnlBearerType=IP_TRANS, RTCPSwitch=ON, RTCPBWRatio=1, Switch3GPP25415CR0125=OFF; ADD UCNNODE: CnOpIndex=1, CNId=3, CNDomainId=PS_DOMAIN, Dpx=3, CNProtclVer=R99, SupportCRType=CR527_NOT_SUPPORT, CNLoadStatus=NORMAL, AvailCap=60000; //Adding a cell ADD UCELLQUICKSETUP: CELLID=1, CELLNAME="Cell1", BANDIND=BAND1,PeerIsValid=VALID, PeerCellId=100, CnOpGrpIndex=0,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, PSCRAMBCODE=0, TCELL=CHIP256, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId = 6,URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8, NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430, PCPICHPOWER=330;
//Deactivating RAN Sharing Introduction Package //Setting the sharing mode for the operators SET UOPERATORSHARINGMODE: RANSharingSupport=NO;
Issue 02 (2011-07-11)
197-3
198 Configuring Dedicated Carrier for Each Operator
198
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-021304 RAN Sharing Introduction Package has been configured before this feature is activated.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set RAN Sharing Support to YES to turn on the RAN sharing switch. Run the BSC6900 MML command ADD UCNOPERATOR to add the primary and secondary operators. Run the BSC6900 MML command ADD UCNOPERGROUP twice to add an operator group respectively for the primary and secondary operators. Configure Iu data for the primary and secondary operators. Configure Iub data and add a dedicated cell.
NOTE
There are two types of RAN sharing: l NodeBs are independently deployed by operators. l NodeBs are shared by operators and cells are not shared by operators.
l
Issue 02 (2011-07-11)
Use a UE to access cells 1000 and 1001. If the network access is successful, carriers are exclusively used by the operators. l Deactivation Procedure 1. 2. ----End Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set RAN Sharing Support to NO to turn off the RAN sharing switch. Run the BSC6900 MML command RMV UCELL to remove all cells configured for the operator.
Example
//Activating Dedicated Carrier for Each Operator //Configuring basic information about the BSC6900 SET UOPERATORSHARINGMODE: RANSharingSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=YES; //Adding a primary operator ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PRIM", MCC="502", MNC="10", CnOpIndex=0; //Adding a secondary operator ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SEC", MCC="310", MNC="30", CnOpIndex=1; //Adding an operator group for the primary operator ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="PRIM", CnOpNum=ONE, CnOpIndex1=0; //Adding an operator group for the secondary operator ADD UCNOPERGROUP: CnOpGrpIndex=1, CnOpGrpName="SEC", CnOpNum=ONE, CnOpIndex1=1; //Adding dedicated cell 1 ADD UCELLQUICKSETUP: CELLID=1, CELLNAME="Cell1", BANDIND=BAND1,PeerIsValid=VALID, PeerCellId=100, CnOpGrpIndex=0,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, PSCRAMBCODE=0, TCELL=CHIP256, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId = 6,URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8, NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430, PCPICHPOWER=330; //Adding dedicated cell 2 ADD UCELLQUICKSETUP: CELLID=2, CELLNAME="Cell2", BANDIND=BAND1,PeerIsValid=VALID, PeerCellId=100, CnOpGrpIndex=1,UARFCNUPLINK=9622, UARFCNDOWNLINK=10572, PSCRAMBCODE=0, TCELL=CHIP256, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, SpgId = 6,URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8, NODEBNAME="NodeB1", LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430, PCPICHPOWER=330;
//Deactivating Dedicated Carrier for Each Operator //Turning off the RAN sharing switch SET UOPERATORSHARINGMODE: RANSharingSupport=NO;
198-2
Issue 02 (2011-07-11)

//Removing a dedicated cell RMV UCELL: CellId=1;
Issue 02 (2011-07-11)
198-3
199 Configuring Flexible Network Architecture
199
Prerequisite
l l
Configuring Flexible Network Architecture
This section describes how to activate, verify, and deactivate the optional feature WRFD-02130402 Flexible Network Architecture.
Context
This feature can meet the networking requirements of different operators.
Procedure
l Activation Procedure For information on activating the Iu Flex feature, see 211 Configuring Iu Flex. For information on activating the Cell Broadcast Service feature, see 174 Configuring Cell Broadcast Service. For information on activating the RAN Sharing feature, see 197 Configuring RAN Sharing Introduction Package. l Verification Procedure For information on verifying the Iu Flex feature, see 211 Configuring Iu Flex. For information on verifying the Cell Broadcast Service feature, see 174 Configuring Cell Broadcast Service.
199 Configuring Flexible Network Architecture
For information on verifying the RAN Sharing feature, see 197 Configuring RAN Sharing Introduction Package. l Deactivation Procedure For information on deactivating the Iu Flex feature, see 211 Configuring Iu Flex. For information on deactivating the Cell Broadcast Service feature, see 174 Configuring Cell Broadcast Service. For information on deactivating the RAN Sharing feature, see 197 Configuring RAN Sharing Introduction Package. ----End
199-2
Issue 02 (2011-07-11)
200 Configuring Mobility Control and Service Differentiation
200
Prerequisite
l l
Configuring Mobility Control and Service Differentiation
This section describes how to activate, verify, and deactivate the optional feature WRFD02130403 Mobility Control and Service Differentiation.
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
200 Configuring Mobility Control and Service Differentiation
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;
200-2
Issue 02 (2011-07-11)
201 Configuring Independent License Control
201
Prerequisite
l l
Configuring Independent License Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-02130404 Independent License Control.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-021304 RAN Sharing Introduction Package has been configured before this feature is activated.
Context
This feature enables operators to have their own network capacity and optional features, thereby meeting different service and operation requirements.
Procedure
l Activation Procedure 1. 2. l l Run the BSC6900 MML command SET LICENSE to configure a license for the primary operator. Run the BSC6900 MML command SET LICENSE to configure a license for the secondary operator.
Verification Procedure This feature does not need to be verified. Deactivation Procedure This feature does not need to be deactivated.
----End
201 Configuring Independent License Control
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;
201-2
Issue 02 (2011-07-11)
202 Configuring RAN Sharing Phase 2
202
Prerequisite
l l l
Configuring RAN Sharing Phase 2
This section describes how to activate, verify, and deactivate the optional feature WRFD-021305 RAN Sharing Phase 2.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The features WRFD-021304 RAN Sharing Introduction Package must be configured before this feature is activated. License The license controlling this feature has been activated.
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 203 Configuring Dedicated Iub Transmission Control. l l Verification Procedure This feature does not need to be verified. Deactivation Procedure This feature does not need to be deactivated. ----End
Issue 02 (2011-07-11)
202-1
203 Configuring Dedicated Iub Transmission Control
203
Prerequisite
l l
Configuring Dedicated Iub Transmission Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-02130501 Dedicated Iub Transmission Control.
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).
Issue 02 (2011-07-11)

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.
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;
203-2
Issue 02 (2011-07-11)
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;
Issue 02 (2011-07-11)
203-3
204 Configuring IMSI-Based Handover
204
Prerequisite
l l l
Configuring IMSI-Based Handover
This section describes how to activate, verify, and deactivate the optional feature WRFD-021303 IMSI-Based Handover.
Context
With this feature, configuring SNA-related information on the RNC is supported. This enables the UTRAN to limit UE mobility when the CN does not support the shared network area (SNA) function.
Procedure
l Activation Procedure 1. 2. 3. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to enable RAN Sharing. Run the BSC6900 MML command ADD ULASNAMAP. In this step, set PLMN to 46000, LAC to 1234, and SNAC to 1. Run the BSC6900 MML command ADD UIMSISNAMAP to add an IMSI-to-SNA mapping relationship. In this step, set The start of IMSI to 460071234000000, The end of IMSI to 460071234500000, PLMN to 46000, and SNAC to 1. Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of H'1234. The UE is admitted to the cell. Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of H'1235. The UE is rejected by the cell. In this case, you can view the RRC CONNECTION REJECT message on the Uu interface.
Issue 02 (2011-07-11)
204 Configuring IMSI-Based Handover

NOTE
The restrictions on cell update, UTRAN registration area (URA) update, handovers, relocations, and handling COMMON ID messages are the same as that on RRC connection request.
Deactivation Procedure 1. 2. Run the BSC6900 MML command RMV ULASNAMAP to remove a mapping relationship between LAC and SNA. Run the BSC6900 MML command RMV UIMSISNAMAP to remove a mapping relationship between IMSI and SNA.
----End
Example
//Activating IMSI-Based Handover //Enabling RAN Sharing SET UOPERATORSHARINGMODE: RANSharingSupport=YES; //Adding PLMN, LAN, and SNAC ADD ULASNAMAP: MCC="460", MNC="00", LAC=H'1234, SNAC=1; //Adding the PLMN and SNAC of the SNA ADD UIMSISNAMAP: ImsiMin = "460071234000000", ImsiMax = "460071234500000", MCC="460", MNC="07", SnaExistInd=TRUE,SNAC=1;
//Deactivating IMSI-Based Handover //Removing a mapping relationship between IMSI and SNA RMV ULASNAMAP: MCC="460", MNC="00", LAC=1234, SNAC=1; //Removing a mapping relationship between IMSI and SNA RMV UIMSISNAMAP: ImsiMin="460071234000000", ImsiMax="460071234500000", MCC="460", MNC="07", SnaExistInd=TRUE, SNAC=1;
204-2
Issue 02 (2011-07-11)
205 Configuring MOCN Introduction Package
205
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature cannot be used together with the feature WRFD-021304 RAN Sharing Introduction Package.
l l
License The license controlling this feature has been activated. The UE and CN support the MOCN feature.
Context
Multi-Operator Core Network (MOCN) was introduced in 3GPP Release 6. It enables multiple operators to share the network and therefore reduces the CAPEX and OPEX. The MOCN feature has no requirement for the RNC, NodeB, and UE hardware. It is applicable to all categories of UEs. For details about MOCN, see 3GPP TS 23.251.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD UCNOPERATOR to add a primary operator. In this step, set Cn Operator Name, MCC, MNC, and Cn Operator Index to appropriate values. Run the BSC6900 MML command ADD UCNOPERATOR to add a secondary operator. In this step, set Cn Operator Name, MCC, MNC, and Cn Operator Index to appropriate values.
2.
Issue 02 (2011-07-11)
3. 4. 5.
Run the BSC6900 MML command SET LICENSE to activate the license for the primary operator. Run the BSC6900 MML command SET LICENSE to activate the license for the secondary operator. Run the BSC6900 MML command ADD UCNOPERATOR to add a common operator.
NOTE
If the MOCN operator has applied for a new PLMN, a common operator needs to be configured. If the MOCN operator does not apply for a new PLMN, a common operator does not need to be configured.
6.
Run the BSC6900 MML command ADD UCNOPERGROUP to add an operator group.
NOTE
When no common operator is configured, set the common operator index (CnOpIndex1) of the operator group to the default value 255.
7.
Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set the sharing mode for the operators. Set RAN Sharing Support to NO. Set MOCN Support to YES. Set Intra RAT Inter Plmn Ho Allowed, Inter RAT Inter Plmn Ho Allowed, Default CnOperator, and Mocn Control Switch to appropriate values based on the network plan. 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.
8. 9.
10. Configure Iu interface transmission data between the BSC6900 and the primary and secondary operators' CNs by referring to Configuring Interface Data. 11. Run the BSC6900 MML command ADD UCNNODE to add a CN node for the primary operator. 12. Run the BSC6900 MML command ADD UCNNODE to add a CN node for the secondary operator. 13. Run the BSC6900 MML command ADD UNRIGLBCNIDMAP to add a mapping between Network Resource Identifiers (NRIs) and CN nodes.
NOTE
The mapping between NRIs and CN nodes needs to be configured based on the network plan. If a CN node is configured with multiple NRIs, repeat this step until all the required mapping relationships are configured.
14. Run the BSC6900 MML command ADD UNODEB to add an MOCN NodeB. In this step, set Sharing Type Of NodeB to MOCN and set other parameters based on the network plan. 15. (Optional) Run the BSC6900 MML command ADD UNODEB to add a dedicated NodeB. 16. Configure the area information by referring to Configuring the Area Information.
NOTE
Location areas must be the same for the primary and secondary operators.
17. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add an MOCN cell.

NOTE
A cell is a dedicated cell if its operator group is configured with only one operator.
18. Run the BSC6900 MML command ADD UEXT3GCELL to add a neighboring RNC cell. l Verification Procedure 1. Register supporting UEs and non-supporting UEs in MOCN cells of the primary and secondary operators. The UEs are registered successfully and properly initiate CS and PS services.
NOTE
The MOCN network has two types of UEs: l Supporting UE: supports the MOCN feature. In an MOCN network, the RNC broadcasts the PLMNs of the operators through system information messages (the Multiple-PLMN list IE). Supporting UEs interpret such PLMN information or notify the RNC of their selected PLMNs through initial direct transfer messages. Supporting UEs support 3GPP Release 6. l Non-supporting UE: does not support the MOCN feature. Non-supporting UEs cannot interpret the PLMN information in system information messages.
Deactivation Procedure 1. 2. Run the BSC6900 MML command RMV UCELL to remove the MOCN cell. Add a cell not enabled with the MOCN feature by referring to Configuring the Cell Data.
NOTE
Deactivating the MOCN feature interrupts services. Therefore, perform the deactivation operations early in the morning when the traffic is light.
----End
Example
//Configuring MOCN Introduction Package //Adding a primary operator ADD UCNOPERATOR: OperatorType=PRIM, CnOperatorName="PrimOp", MCC="302", MNC="221", CnOpIndex=0; //Adding a secondary operator ADD UCNOPERATOR: OperatorType=SEC, CnOperatorName="SecOp", MCC="302", MNC="640", CnOpIndex=1; //Adding a common operator ADD UCNOPERATOR: OperatorType=COMM, CnOperatorName="Common", MCC="302", MNC="580", CnOpIndex=5; //Activating the license for the primary operator SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=0, FUNCTIONSWITCH2=ENHANCEDIUFLEX-1, FUNCTIONSWITCH4=MOCN_PACKAGE-1; //Activating the license for the secondary operator SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=NO, CNOPERATORINDEX=1, FUNCTIONSWITCH2=ENHANCEDIUFLEX-1, FUNCTIONSWITCH4=MOCN_PACKAGE-1; //Adding an operator group ADD UCNOPERGROUP: CnOpGrpIndex=0, CnOpGrpName="ShareCnOpGrp", CnOpNum=TWO, CnOpIndex1=0, CnOpIndex2=1, CnOpIndexComm=5;
Issue 02 (2011-07-11)
205-3
//Setting the sharing mode for the operators SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO, DefaultCnOp=255, MocnControlSwitch=COMM_MOCN_NRI_GLOBAL_CONFIG_MODE_SWITCH-1&COMM_MIB_MULT I_PLMN_LIST_ALLOWED_SWITCH-1; //Setting parameters for the primary operator SET UOPERATORCFGPARA: CnOpIndex=0, CsNriCfgMode=SUPP_IUFLEX_MOCN, PsNriCfgMode=SUPP_IUFLEX_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=0; //Setting parameters for the secondary operator SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX_MOCN, PsNriCfgMode=SUPP_IUFLEX_MOCN, CSNRILength=7, PSNRILength=10, NullNRI=1; //Adding CN node 10 for the primary operator ADD UCNNODE: CnOpIndex=0, CNId=10, CNDomainId=CS_DOMAIN, Dpx=3, CNProtclVer=R5, SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF, Switch3GPP25415CR0125=OFF; //Adding CN node 20 for the primary operator ADD UCNNODE: CnOpIndex=0, CNId=20, CNDomainId=PS_DOMAIN, Dpx=3, CNProtclVer=R5, SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF, Switch3GPP25415CR0125=OFF; //Adding CN node 11 for the secondary operator ADD UCNNODE: CnOpIndex=1, CNId=11, CNDomainId=CS_DOMAIN, Dpx=3, CNProtclVer=R5, SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF, Switch3GPP25415CR0125=OFF; //Adding CN node 21 for the secondary operator ADD UCNNODE: CnOpIndex=1, CNId=21, CNDomainId=PS_DOMAIN, Dpx=3, CNProtclVer=R5, SupportCRType=CR529_SUPPORT, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF, Switch3GPP25415CR0125=OFF; //Adding the mapping between CN node 10 and an NRI for the primary operator ADD UNRIGLBCNIDMAP: CnOpIndex=0, CNId=10, NRI=10; //Adding the mapping between CN node 20 and an NRI for the primary operator ADD UNRIGLBCNIDMAP: CnOpIndex=0, CNId=20, NRI=20; //Adding the mapping between CN node 11 and an NRI for the secondary operator ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=11, NRI=100; //Adding the mapping between CN node 21 and an NRI for the secondary operator ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=21, NRI=600; //Adding an MOCN NodeB ADD UNODEB: NodeBName="NodeB1", NodeBId=1, SRN=0, SN=0, TnlBearerType=IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST, SharingType=MOCN; //Adding a dedicated NodeB ADD UNODEB: NodeBName="NodeB2", NodeBId=2, SRN=0, SN=0,
205-4
Issue 02 (2011-07-11)
TnlBearerType=IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; //Adding a location area for the primary operator ADD ULAC:CNOPINDEX=0, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256; //Adding a location area for the secondary operator ADD ULAC:CNOPINDEX=1, LAC=H'7208, PLMNVALTAGMIN=1, PLMNVALTAGMAX=256; //Adding an MOCN cell ADD UCELLQUICKSETUP: CellId=1, CellName="Cell1", PeerIsValid=INVALID, CnOpGrpIndex=0, BandInd=Band1, UARFCNDownlink=10562, PScrambCode=0, TCell=CHIP256, LAC=H'2501, SAC=H'0000, CfgRacInd=REQUIRE, RAC=H'00, SpgId=6, URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8, NodeBName="NodeB1", LoCell=0, SupBmc=FALSE; //Adding a neighboring RNC cell ADD UEXT3GCELL: NRncId=RNC1, CellId=1, CellHostType=SINGLE_HOST, CellName="Cell1", CnOpGrpIndex=0, PScrambCode=0, BandInd=Band1, UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700, TxDiversityInd=FALSE, LAC=h'2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE, QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED, CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE;
//Deactivating MOCN Introduction Package //Removing an MOCN cell RMV UCELL: CellId=1; //Adding a cell not enabled with the MOCN feature ADD UCELLQUICKSETUP: CellId=1, CellName="Cell1", PeerIsValid=INVALID, CnOpGrpIndex=1, BandInd=Band1, UARFCNDownlink=10562, PScrambCode=0, TCell=CHIP256, LAC=H'2501, SAC=H'0000, CfgRacInd=REQUIRE, RAC=H'00, SpgId=6, URANUM=D8, URA1=1, URA2=2, URA3=3, URA4=4, URA5=5, URA6=6, URA7=7, URA8=8, NodeBName="NodeB1", LoCell=0, SupBmc=FALSE;
Issue 02 (2011-07-11)
205-5
206 Configuring Carrier Sharing by Operators
206
Prerequisite
l l
Configuring Carrier Sharing by Operators
This section describes how to activate, verify, and deactivate the optional feature WRFD-02131101 Carrier Sharing by Operators.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-021311 MOCN Introduction Package has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. The CN supports the MOCN feature.
Context
This feature enables multiple operators to share the same carrier.
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 carrier. Check whether the MOCN introduction package is effective based on the message traced on the Uu interface. If a cell is configured for only one operator, the system information message of the cell does not contain the information element (IE) multiplePLMN-List. If a cell is configured with multiple operators but is not configured with a common operator, the system information message of the cell contains the PLMN of only the first operator, and the value of the IE multiplePLMN-List is TRUE.
If a cell is configured with multiple operators and a common operator, the system information message of the cell contains the IE multiplePLMN-List, broadcasting all PLMNs of the MOCN cell. As shown in Figure 206-1, the system information message broadcasts PLMN 302580 of the common operator. As shown in Figure 206-2, the field PLMN Identity in the system information message contains the IE multiplePLMN-List. This IE contains the PLMNs (302221 and 302640) of two operators. Figure 206-1 PLMN Identify field in the MIB message
The IE Multiple PLMN List contains the PLMNs (302221 and 302640) of the actual operators.
206-2
Issue 02 (2011-07-11)
Figure 206-2 Multiple PLMN List IE in the MIB message
Deactivation Procedure 1. Run the BSC6900 MML command RMV UCELL to remove the MOCN cell.
----End
Example
//Configuring Carrier Sharing by Operators ADD UCELLQUICKSETUP: PeerIsValid=INVALID, CnOpGrpIndex=0, LAC=H'7208, SupBmc=FALSE; //Deactivating Carrier Sharing by Operators RMV UCELL: CellId=1;
Issue 02 (2011-07-11)
206-3
207 Configuring Dedicated NodeB/Cell for Operators
207
Prerequisite
l l
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.
Context
This feature enables operators to independently control a NodeB or cell when the MOCN feature is enabled.
Procedure
l Activation Procedure 1. 2. l Run the BSC6900 MML command ADD UNODEB to add a dedicated NodeB. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add a dedicated cell. Check whether this feature has been activated based on the master information block (MIB) message traced on the Uu interface. As shown in Figure 207-1, the MIB message of the dedicated cell contains the operator information (302640).
Issue 02 (2011-07-11)
207-1
Figure 207-1 PLMN Identify IE in the MIB message
Deactivation Procedure 1. 2. 3. Run the BSC6900 MML command RMV UCELL to remove the dedicated cell. Run the BSC6900 MML command MOD UNODEB to change a dedicated NodeB into a shared NodeB. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add a shared cell.
----End
Example
//Activating Dedicated NodeB/Cell for Operators //Adding a dedicated NodeB ADD UNODEB: NodeBName="1", NodeBId=1, SRN=0, SN=0, TnlBearerType=ATM_TRANS, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; //Adding a dedicated cell ADD UCELLQUICKSETUP: CellId=1, CellName="1", PeerIsValid=INVALID, CnOpGrpIndex=0, BandInd=Band1, UARFCNDownlink=10562, PScrambCode=0, TCell=CHIP0, LAC=1, SAC=0, CfgRacInd=NOT_REQUIRE, SpgId=1, URANUM=D1, URA1=0, NodeBName="1", LoCell=1, SupBmc=FALSE;
207-2
Issue 02 (2011-07-11)
//Deactivating Dedicated NodeB/Cell for Operators //Removing a dedicated cell RMV UCELL: CellId=1; //Changing a dedicated NodeB into a shared NodeB MOD UNODEB: NodeBId=1, SharingType=MOCN; //Adding a shared cell ADD UCELLQUICKSETUP: CellId=1, CellName="1", PeerIsValid=INVALID, CnOpGrpIndex=1, BandInd=Band1, UARFCNDownlink=10562, PScrambCode=0, TCell=CHIP0, LAC=1, SAC=0, CfgRacInd=NOT_REQUIRE, SpgId=1, URANUM=D1, URA1=0, NodeBName="1", LoCell=1, SupBmc=FALSE;
Issue 02 (2011-07-11)
207-3
208 Configuring MOCN Mobility Management
208
Prerequisite
l l
Configuring MOCN Mobility Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-02131103 MOCN Mobility Management.
Context
This feature is applicable to different MOCN mobility strategies. This feature enables the BSC6900 to determine whether to hand over a UE to a target cell based on the ID of the operator to which the UE belongs and the PLMN ID of the target cell. By default, the BSC6900 allows inter-RAT cross-PLMN handovers. You can prohibit this type of handover by running the command SET UOPERATORSHARINGMODE.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set MOCN Support, Intra RAT Inter Plmn Ho Allowed, and Inter RAT Inter Plmn Ho Allowed to YES. When the cross-PLMN handover switch is turned on, check whether UEs can perform cross-PLMN handovers, relocations, and cell updates. If UEs can perform crossPLMN handovers, relocations, and cell updates, this feature has been activated.
l
Issue 02 (2011-07-11)
208 Configuring MOCN Mobility Management
1.
Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set MOCN Support to YES, Intra RAT Inter Plmn Ho Allowed to NO, and Inter RAT Inter Plmn Ho Allowed to NO.
----End
Example
//Activating MOCN Mobility Management SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES, InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES; //Deactivating MOCN Mobility Management SET UOPERATORSHARINGMODE: RANSharingSupport=NO, MOCNSupport=YES, InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
208-2
Issue 02 (2011-07-11)
209 Configuring MOCN Load Balance
209
Prerequisite
l l l
Configuring MOCN Load Balance
This section describes how to activate, verify, and deactivate the optional feature WRFD-02131104 MOCN Load Balance.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-021311 MOCN Introduction Package has been configured before this feature is activated. License The license controlling this feature has been activated.
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. In this step, set MOCN Support to YES.
NOTE
In this step, set Default CnOperator to 255. The BSC6900 selects operators in Round Robin mode.
Verification Procedure 1. Run the BSC6900 MML command LST UOPERATORSHARINGMODE to query the parameter settings of the feature MOCN Load Balance. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this step, set MOCN Support to YES and Default CnOperator to 0. The BSC6900 preferentially selects the default operator (operator 0).
----End
209 Configuring MOCN Load Balance
Example
//Activating MOCN Load Balance SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=255; //Deactivating MOCN Load Balance SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=0;
209-2
Issue 02 (2011-07-11)
210
Prerequisite
l l
Configuring Routing Roaming UEs in Proportion
This section describes how to activate, verify, and deactivate the optional feature WRFD-02131106 Routing Roaming UEs in Proportion.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-021311 MOCN Introduction Package has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Other Prerequisites The CN supports this feature. During initial registration of a roaming UE, the UE selects the same operator for CS and PS services, and the IMSI is carried to the RNC.
Context
When roaming UEs of one operator move to the area served by the RNC that is shared among multiple operators using the Multi-Operator Core Network (MOCN), the RNC routes the UEs to CN nodes that belong to different operators according to the preset ratio if the UEs are under the roaming agreement with these operators.
Procedure
NOTE
Assume that operator1 and operator2 share the same RNC by using the MOCN and operator A signs a roaming agreement with the two operators.
1.
To add operator A to the roaming relation list of operator1, run the BSC6900 MML command ADD UROAMMAP. In this step, set MCC for operator A to 460, MNC to 09, Cn Operator Index for operator1 to 1, Cn Operator Group Index for
Issue 02 (2011-07-11)
operator1 to 1, and Capability of Roaming Operator to an appropriate value according to the network plan, such as 30. 2. To add operator A to the roaming relation list of operator2, run the BSC6900 MML command ADD UROAMMAP. In this step, set Cn Operator Index for operator2 to 2, Cn Operator Group Index to 1, and Capability of Roaming Operator to an appropriate value according to the network plan, such as 70.
NOTE
After the parameter settings are complete, the UEs that belong to operator A are distributed to operator1 and operator2 according to the preset ratio (30:70). If operator B also signs a roaming agreement with operator1 and operator2, the roaming UE distribution ratio for operator B must be set to the same as that for operator A when operator B is added to the roaming relation lists of the two operators.
Verification Procedure 1. Run the BSC6900 MML command LST UROAMMAP to query the roaming capacity of operator A. Expected result: Capability of Roaming Operator for operator1 is set to 30, and Capability of Roaming Operator for operator2 is set to 70. When UEs belonging to operator A roam to the RNC shared by operator1 and operator2 by using the MOCN for a long measurement period, view the performance counter VS.ROAM.MOCN.NUM on the M2000. Expected result: The roaming UEs of operator A are routed to CN nodes of operator1 and operator2 in a preset proportion of 30:70.
NOTE
2.
UEs of the non-supporting UE type do not support network sharing, as defined in the feature WRFD-02131101 Carrier Sharing by Operators. This feature is not applicable to UEs of the supporting UE type (supporting network sharing).
Deactivation Procedure 1. 2. Run the BSC6900 MML command RMV UROAMMAP to remove operator A from the roaming relation list of operator1. Run the BSC6900 MML command RMV UROAMMAP to remove operator A from the roaming relation list of operator2.
----End
Example
/*Activating Routing Roaming UEs in Proportion*/ //Adding operator A serving roaming UEs to the roaming relation list of operator1 ADD UROAMMAP: MCC="460", MNC="09", CnOpIndex=1, CnOpGrpIndex = 1,AvailRoamCap =30; //Adding operator A serving roaming UEs to the roaming relation list of operator2 ADD UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex = 1,AvailRoamCap =70; /*Deactivating Routing Roaming UEs in Proportion*/ //Removing operator A serving roaming UEs from the roaming relation list of operator1
210-2
Issue 02 (2011-07-11)
RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=1, CnOpGrpIndex = 1; //Removing operator A serving roaming UEs from the roaming relation list of operator2 RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex = 1;
Issue 02 (2011-07-11)
210-3
211 Configuring Iu Flex
211
Prerequisite
l l l l Dependencies on Hardware Dependencies on Other Features License
Configuring Iu Flex
This section describes how to activate, verify, and deactivate the optional feature WRFD-021302 Iu Flex.
This feature does not depend on the hardware. This feature does not depend on other features. The license controlling this feature has been activated. Others The MSC and the serving GPRS support node (SGSN) support this feature.
Context
This feature allows one BSC6900 to connect to multiple MSCs and/or SGSNs, and these CS/ PS domain nodes can form different pools that serve the same pool area.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UOPERATORCFGPARA. In this step, set Feature Supporting Mode of CS Domain to SUPP_IUFLEX, set Feature Supporting Mode of PS Domain to SUPP_IUFLEX, and set Length of CS NRI in bits and Length of PS NRI in bits to appropriate values. Configure the Iu interface transmission between BSC6900 and multiple core networks (CNs) by referring to Configuring the Interfaces. Run the BSC6900 MML command ADD UCNNODE to add multiple CN nodes for an operator according to the network plan. Run the BSC6900 MML command ADD UNRIGLBCNIDMAP. In this step, set Cn Operator Index, CN node ID, and Network resource identity to configure the mapping relationships between NRI and CN nodes.
2. 3. 4.
Issue 02 (2011-07-11)
5.
Optional: Run the BSC6900 MML command ADD UIMSIIDNNSCNIDMAP to configure the mapping relationships between international mobile subscriber identity (IMSI) ranges and CN nodes. After configuring the mapping relationships, the RNC routes the UE whose IMSI is within the IMSI range to the specified CN.
Verification Procedure 1. 2. Enable the UE to access a cell and register in the cell. According to the mapping relationships between IMSI ranges and CN nodes and the load balance algorithm, the RNC selects a CN node for the UE, and the UE registers successfully. Then, if the UE initiates a service, the RNC routes the UE to the corresponding CN node according to the mapping relationships between NRI and CN nodes. Run the BSC6900 MML command SET UOPERATORCFGPARA to deactivate this feature.
3. l
----End
Example
//Activating Iu Flex //Configuring the RNC supporting Iu Flex with Length of CS NRI in bits and Length of PS NRI in bits set to appropriate values SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, PSNRILength=5; //Configuring the first CN node ADD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; //Configuring the second CN node ADD UCNNODE: CnOpIndex=1, CNId=18, CNDomainId=CS_DOMAIN, Dpx=3, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; //Configuring the mapping relationship between NRI and the first CN node ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=17, NRI=8; //Configuring the mapping relationship between NRI and the second CN node ADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=18, NRI=9; //Configuring the mapping relationship between the IMSI range and the first CN node ADD UIMSIIDNNSCNIDMAP: ImsiRtMin=0, ImsiRtMax=666, CnOpIndex=1, CNId=17; //Configuring the mapping relationship between the IMSI range and the second CN node ADD UIMSIIDNNSCNIDMAP: ImsiRtMin=667, ImsiRtMax=999, CnOpIndex=1, CNId=18;
//Deactivating Iu Flex
211-2
Issue 02 (2011-07-11)
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_NONE, PsNriCfgMode=SUPP_NONE;
Issue 02 (2011-07-11)
211-3
212 Configuring Iu Flex Load Distribution Management
212
Prerequisite
l l l l
Configuring Iu Flex Load
Distribution Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-021306 Iu Flex Load Distribution Management.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-021302 Iu Flex has been configured before this feature is activated. License The license controlling this feature has been activated. Other Prerequisites The CN supports dynamic capacity management and load redistribution.
Context
This feature enables load balancing and load redistribution among multiple CN nodes when Iu Flex is deployed. The BSC6900 supports dynamic and static management of CN capacity and status information.
Procedure
l Activation Procedure Configuring load balancing in static capacity mode 1. Run the BSC6900 MML command ADD UCNNODE. In this step, set Capability of CN Node to an appropriate value. The BSC6900 performs load balancing between CN nodes based on the configured CN capacities. Run the BSC6900 MML command SET UOPERATORCFGPARA. In this step: Set Feature Supporting Mode of CS Domain to SUPP_IUFLEX. Set Feature Supporting Mode of PS Domain to SUPP_IUFLEX.
Configuring load balancing in dynamic capacity mode 1.
Set CS Information Update Switch to ON. Set PS Information Update Switch to ON.
NOTE
Load balancing in dynamic capacity mode takes effect only when the BSC6900 is connected to Huawei CN and the preceding switches related to Iu Flex are turned on.
Configuring load redistribution based on NullNRI 1. 2. Run the BSC6900 MML command MOD UCNNODE. In this step, set Status of CN Node to OFFLOAD. Run the BSC6900 MML command SET UOPERATORCFGPARA. In this step, set NullNRI VALUE to an appropriate value based on the network plan. Run the BSC6900 MML command MOD UCNNODE. In this step, set Status of CN Node to NORMAL and select the RSVDBIT1_BIT1 check box under the parameter Reserved parameter 1.
Configuring load redistribution based on Block CN Node 1.
Verification Procedure Verifying load balancing in static capacity mode 1. 2. Run the BSC6900 MML command DSP UCNNODE to query the capacity ratio of CN nodes. Check the following performance counters on the M2000 to verify that the BSC6900 performs load balancing based on the preconfigured CN capacity: Performance counters for CS service setup: VS.IU.LdBalRtCS.IMSI VS.IU.LdBalRtCS.InValidNRI VS.IU.LdBalRtCS.IMEI Performance counters for PS service setup: VS.IU.Load.RoutePS.IMSI VS.IU.Load.RoutePS.NRI VS.IU.Load.RoutePS.IMEI Verifying load balancing in dynamic capacity mode 1. 2. 3. Run the BSC6900 MML command DSP UCNNODE to query the capacity ratio of CN nodes. On the BSC6900 LMT, choose Trace > UMTS Services to initiate Uu and Iu interface message tracing. Check the traced messages. If the CN sends the BSC6900 an INFORMATION TRANSFER INDICATION message, the dynamic CN capacity ratio is updated and used. If the CN does not send any INFORMATION TRANSFER INDICATION message to the BSC6900, the static CN capacity ratio is used. Check the following performance counters on the M2000 to verify that the BSC6900 performs load balancing based on the dynamic CN capacity ratio: Performance counters for CS service setup: VS.IU.LdBalRtCS.IMSI VS.IU.LdBalRtCS.InValidNRI VS.IU.LdBalRtCS.IMEI
4.
212-2
Issue 02 (2011-07-11)
Performance counters for PS service setup: VS.IU.Load.RoutePS.IMSI VS.IU.Load.RoutePS.NRI VS.IU.Load.RoutePS.IMEI Verifying load redistribution based on NullNRI 1. 2. 3. 4. 5. On the BSC6900 LMT, choose Trace > UMTS Services to initiate Uu and Iu interface message tracing. Power off the UE. The PTMSI of the UE is assigned by SGSN1. Set SGSN1 to the OFFLOAD state and SGSN2 to the NORMAL state on the RNC. Set SGSN1 to the OFFLOAD state on SGSN1. Power on the UE and the UE makes an attach request. Check the traced Iu interface messages. The expected result is as follows: The BSC6900 routes the RRC_INIT_DIRECT_TRANSFER message to SGSN1 based on NULL NRI. The attach reception message from SGSN1 contains NULL NRI and non-broadcasting location areas. After receiving the non-broadcasting location areas, the UE sends a new routing area update (RAU) request and contains NULL NRI in the RRC_INIT_DIRECT_TRANSFER message. The BSC6900 routes the RRC_INIT_DIRECT_TRANSFER message to SGSN2, of which the state is not OFFLOAD, based on NULL NRI. Verifying load redistribution based on Block CN Node 1. 2. 3. 4. On the BSC6900 LMT, choose Trace > UMTS Services to initiate Uu and Iu interface message tracing. Power off the UE. The PTMSI of the UE is assigned by SGSN1. Set SGSN1 to the BLOCK state and SGSN2 to the NORMAL state on the RNC. Power on the UE and the UE makes an attach request. Check the RRC_INIT_DIRECT_TRANSFER message traced on the Iu interface. Expected result: The RRC_INIT_DIRECT_TRANSFER message contains NRI of SGSN1. The BSC6900 routes the RRC_INIT_DIRECT_TRANSFER message to SGSN2 because SGSN1 is in the BLOCK state. l Deactivation Procedure Deactivating load balancing in static capacity mode Load balancing in static capacity mode does not need to be deactivated. Deactivating load balancing in dynamic capacity mode 1. Run the BSC6900 MML command SET UOPERATORCFGPARA. In this step, set CS Information Update Switch to OFF and PS Information Update Switch to OFF.
Deactivating load redistribution based on NullNRI 1. Run the BSC6900 MML command MOD UCNNODE. In this step, set Status of CN Node to NORMAL.
Deactivating load redistribution based on Block CN Node
Issue 02 (2011-07-11)
212-3
1.
Run the BSC6900 MML command MOD UCNNODE. In this step, set Status of CN Node to NORMAL and deselect the RSVDBIT1_BIT1 check box under the parameter Reserved parameter 1.
----End
Example
//Activating Iu Flex Load Distribution Management //Configuring Load balancing in static capacity mode ADD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; //Configuring load balancing in dynamic capacity mode SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=ON, PsInfoUpdFlag=ON; //Configuring load redistribution based on NullNRI MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=OFFLOAD, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, NullNRI=31; //Configuring load redistribution based on Block CN Node MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN,CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF, RsvdPara1=RSVDBIT1_BIT1-1; //Deactivating Iu Flex Load Distribution Management //Deactivating load balancing in dynamic capacity mode SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=OFF, PsInfoUpdFlag=OFF; //Deactivating load redistribution based on NullNRI MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF; //Deactivating load redistribution based on Block CN Node MOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF, RsvdPara1=RSVDBIT1_BIT1-0;
212-4
Issue 02 (2011-07-11)
213 Configuring Enhanced Multiband Management
213
Prerequisite
l l
Configuring Enhanced Multiband Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-020160 Enhanced Multiband Management.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The following features must be configured before this feature is activated: In the inter-frequency traffic steering, the features WRFD-020110 Multi Frequency Band Networking Management and WRFD-020400 DRD Introduction Package must be activated. In the inter-frequency load sharing, the features WRFD-020110 Multi Frequency Band Networking Management and WRFD-020103 Inter-Frequency Load Balance must be activated. If one of the required features is not activated, the corresponding function is unavailable in the multi-frequency band networking solution. Features can be configured according to operator requirements.
Context
Blind load-based inter-frequency handovers are previously performed. In a multiband network, cells in different frequency bands have different coverage areas, and therefore blind handovers performed in this scenario may lead to call drops. After this feature is applied, when an interfrequency handover is required, the RNC starts the inter-frequency measurement and makes a handover decision instead of performing a blind handover. This increases the handover success rate. In the inter-frequency traffic steering, each cell is configured with the priority for carrying each type of service (R99 RT, R99 NRT, HSPA, and others). After the radio access bearer (RAB) is set up, inter-frequency measurement is performed to ensure that the UE accesses the cell with the highest priority.
In the inter-frequency load sharing, after the RAB setup, load reshuffling (LDR) may trigger a load-based inter-frequency handover. The target cell is selected on the basis of the quality measurement of cells. Only the cell that meets the quality requirement is selected.
Procedure
l Activation Procedure Configure this feature based on the traffic steering-based handover function. 1. 2. Run the BSC6900 MML command SET UDRD to set Measurement-Based DRD Switch to ON. Run the BSC6900 MML command MOD UINTERFREQNCELL to set DrdOrLdrFlag to TRUE(Send).
Configure this feature based on the load sharing-based handover function. 1. 2. l Run the BSC6900 MML command MOD UINTERFREQNCELL to set DrdOrLdrFlag to TRUE(Send). Run the BSC6900 MML command MOD UCELLLDR to set InterFreq Load Handover Method Selection to MEASUREHO.
Verification Procedure Verify this feature based on the traffic steering-based handover function. 1. 2. 3. Configure cell A to provide R99 services and configure cell B to provide HSPA services. Enable the UE to set up an R99 service in cell A and then raise the service rate of the UE. Monitor the RRC_MEAS_CTRL message on the Uu interface to view the interfrequency measurement control information element (IE), as shown in Figure 213-1. Figure 213-1 Message containing the IE
4.
After reporting an inter-frequency measurement message, the UE switches to the target inter-frequency cell B if cell B meets the related threshold requirements.
Verify this feature based on the load sharing-based handover function. 1. 2. 3. Configure cell A and cell B to provide R99 services. Enable the UE to set up an R99 service in cell A. When a large number of UEs access cell A, cell congestion occurs. In this scenario, you can view the inter-frequency measurement control information in the RRC_MEAS_CTRL message on the Uu interface. After reporting an inter-frequency measurement message, the UE switches to the target inter-frequency cell B if cell B meets the related threshold requirements.
4. l
Deactivation Procedure Deactivate this feature based on the traffic steering-based handover function.
213-2
Issue 02 (2011-07-11)
1.
Run the BSC6900 MML command SET UDRD to set Measurement-Based DRD Switch to OFF. Run the BSC6900 MML command MOD UCELLLDR to set InterFreq Load Handover Method Selection to BLINDHO.
Deactivate this feature based on the load sharing-based handover function. 1. ----End
Example
//Configuring this feature based on the traffic steering-based function //Enabling the measurement-based directed retry decision (DRD) SET UDRD: BasedOnMeasHRetryDRDSwitch=ON; //Enabling the measurement switch for an inter-frequency neighboring cell MOD UINTERFREQNCELL: RNCId=2021, CellId=3000, NCellRncId=2021, NCellId=3002, DrdOrLdrFlag=TRUE;
//Configuring this feature based on the load sharing-based handover function //Enabling the measurement switch for an inter-frequency neighboring cell MOD UINTERFREQNCELL: RNCId=2021, CellId=3000, NCellRncId=2021, NCellId=3002, DrdOrLdrFlag=TRUE; //Configuring the load-based inter-frequency handover with InterFreqLDHOMethodSelection set to MEASUREHO MOD UCELLLDR: CellId=3000, InterFreqLDHOMethodSelection=MEASUREHO;
//Deactivating this feature based on the traffic steering-based handover function //Disabling the measurement-based DRD SET UDRD: BasedOnMeasHRetryDRDSwitch=OFF;
//Deactivating this feature based on the load sharing-based handover function. //Configuring the load-based inter-frequency handover with InterFreqLDHOMethodSelection set to BLINDHO MOD UCELLLDR: CellId=3000, InterFreqLDHOMethodSelection=BLINDHO;
Issue 02 (2011-07-11)
213-3
214 Configuring Satellite Transmission on Iub Interface
214
Prerequisite
l l l
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.
Context
This feature supports satellite transmission on the Iub interface, which is useful to cover remote areas, such as an island. When satellite transmission is applied over the Iub interface, the delay increases. The default setting of the SAAL/SCTP timer on the Iub interface can meet the satellite transmission requirements.
Procedure
l Activation Procedure 1. 2. l 1. 2. Run the BSC6900 MML command MOD UNODEB. In this step, set Satellite Trans Ind to TRUE. Run the BSC6900 MML command ACT UCELL to activate a cell. Run the BSC6900 MML command DSP UCELL to check whether cell settings are successful. Establish an AMR service in the cell. The AMR service is established successfully and the speech quality is satisfactory.
Issue 02 (2011-07-11)
214 Configuring Satellite Transmission on Iub Interface
3. l
Establish a PS BE service in a cell. The service is established successfully and the data download rate is steady. Run the BSC6900 MML command DEA UCELL to deactivate the cell. Run the BSC6900 MML command MOD UNODEB. In this step, set Satellite Trans Ind to FALSE.
----End
Example
//Activating Satellite Transmission on Iub Interface MOD UNODEB: NodeBId=1, SATELLITEIND=TRUE; ACT UCELL: CellId=1; //Deactivating Satellite Transmission on Iub Interface DEA UCELL: CellId=1; MOD UNODEB: NodeBId=1, SATELLITEIND=FALSE;
214-2
Issue 02 (2011-07-11)
215 Configuring Satellite Transmission on Iu Interface
215
Prerequisite
l l l
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.
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 Activation Procedure 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 215-1.
Issue 02 (2011-07-11)
215-1
215 Configuring Satellite Transmission on Iu Interface
Table 215-1 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;
215-2
Issue 02 (2011-07-11)
216 Configuring MBMS Introduction Package
216
Prerequisite
l l l l
Configuring MBMS Introduction Package
This section describes how to activate, verify, and deactivate the optional feature WRFD-010616 MBMS Introduction Package.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Others The existing PS domain functional entities (GGSN, SGSN, UTRAN, and UE) support the Multimedia Broadcast Multicast Service (MBMS) bearer service. A new functional entity, that is, the broadcast multicast service centre (BM-SC) is added to provide a set of functions for the MBMS services. The UE supports MBMS functions.
Context
The MBMS feature is an important feature specified by 3GPP Release 6. When MBMS is enabled, point-to-multipoint multimedia services can be forwarded from one entity to multiple entities over a common channel. In this way, the resources can be shared.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET UMBMSSWITCH to set MBMS Control Switch to ON(ON). Run the BSC6900 MML command ADD UMBMSSA to add the MBMS service area according to the network plan.
Issue 02 (2011-07-11)
3. 4. 5. 6. 7. 8. 9.
Run the BSC6900 MML command ADD UCELLMBMSSA to add the mapping between the cell and the MBMS service area (SA) according to the network plan. Run the BSC6900 MML command ADD USCCPCHBASIC to add the SCCPCH according to the network plan. Run the BSC6900 MML command ADD UFACH to add the FACH according to the network plan. Run the BSC6900 MML command ADD UFACHDYNTFS to add the transport format set (TFS) of an FACH according to the network plan. Run the BSC6900 MML command ADD UFACH to add a logical channel mapped to an FACH according to the network plan. Run the BSC6900 MML command ADD USCCPCHTFC to add the Calculated Transport Format Combination (CTFC) of an SCCPCH according to the network plan. Run the BSC6900 MML command ADD UCELLMCCH to add the MCCH and the MICH for the cell according to the network plan. (1) Run the BSC6900 MML command ACT USCCPCH to activate the configuration information of an SCCPCH. (2) Run the BSC6900 MML command ACT UCELLMBMS to activate the MBMS configuration data for the cell.
10. Configure the cell-level MBMS parameters according to the network plan.
11. Run the BSC6900 MML command SET UMTCH to set the MBMS service type and rate according to the network plan. 12. Run the BSC6900 MML command SET URNCMBMSPARA to set the RNC-level parameters for the MBMS algorithm according to the network plan. l Verification Procedure 1. 2. l Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the MBMS status in the cell. Conduct a test to check whether the MBMS UE can receive the corresponding MBMS data successfully. Run the BSC6900 MML command SET UMBMSSWITCH to set MBMS Control Switch to OFF(OFF).
----End
Example
//Activation MBMS Introduction Package //Enabling the MBMS control switch SET UMBMSSWITCH: MbmsSwitch=ON; //Adding the MBMS service area ADD UMBMSSA: CnOpIndex=0, MbmsSaId=1; //Adding the mapping between the cell and the MBMS service area (SA) ADD UCELLMBMSSA: CellId=2, CnOpIndex=0, MbmsSaId=1; //Adding the SCCPCH ADD USCCPCHBASIC: CellId=2, PhyChId=11, ScrambCode=0, SlotFormat=D8, TFCIpresence=NOT_EXISTS, MbmsChInd=MCCH; //Adding the FACH ADD UFACH: CellId=2, PhyChId=11, TrChId=10, RateMatchingAttr=220, ToAWS=20, ToAWE=10, MaxFachPower=-10, MAXCMCHPI=D15, MINCMCHPI=D14, SIGRBIND=TRUE, ChCodingType=CONVOLUTIONAL;
216-2
Issue 02 (2011-07-11)
//Adding the transport format set (TFS) of an FACH ADD UFACHDYNTFS: CellId=2, TrChId=10, RLCSize=168, TFsNumber=D3, TbNumber1=0, TbNumber2=1, TbNumber3=2; //Adding a logical channel mapped to an FACH ADD UFACHLOCH: CellId=2, TrChId=10; //Adding the Calculated Transport Format Combination (CTFC) of an SCCPCH ADD USCCPCHTFC: CellId=2, PhyChId=11, CTFC=0;ADD USCCPCHTFC: CellId=2, PhyChId=11, CTFC=1; //Adding the MCCH and the MICH for the cell ADD UCELLMCCH: CellId=2, MichId=19, PhyChIdforMcch=11, FachIdforMcch=10; //Activating the configuration information of an SCCPCH ACT USCCPCH: CellId=2, PhyChId=11; //Activating the MBMS configuration data for the cell ACT UCELLMBMS: CellId=100; //Setting the MBMS service type and rate SET UMTCH: ServiceType=STREAMING, ServiceBitRate=D128; //Setting the RNC-level parameters for the MBMS algorithm SET URNCMBMSPARA: MbmsTransMode=DYNAMIC; //Deactivation MBMS Introduction Package SET UMBMSSWITCH: MbmsSwitch=OFF;
Issue 02 (2011-07-11)
216-3
217 Configuring MBMS Admission Control
217
Prerequisite
l l
Configuring MBMS Admission Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061602 MBMS Admission Control.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The feature WRFD-010616 MBMS Introduction Package must be configured before this feature is activated.
Context
The admission criteria of Iub resources and credit resources for the Multimedia Broadcast and Multicast Service point-to-point/point-to-multipoint resource block (MBMS PtP/PtM RB) requests is the same as that for other services. The cell power resources are preferentially allocated to high-priority MBMS broadcasting services. Only the activation procedure of the resource admission on the Uu interface is provided in this section.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select MBMS_UU_ADCTRL from the Cell CAC algorithm switch drop-down list to enable the MBMS admission control on the Uu interface and select a proper admission algorithm according to the network plan. Enable the MBMS admission algorithm, and then limit cell resources to ensure that the admission resources are insufficient. In this manner, the admission fails. An example is given as follows:
Issue 02 (2011-07-11)
217 Configuring MBMS Admission Control
(1) Run the BSC6900 MML command ADD URESERVEOVSF to reserve the downlink Orthogonal Variable Spreading Factor (OVSF) for the cell so that only 64 kbit/s services are supported in the cell. (2) Originate a 256 kbit/s service. Check the messages traced on the Iu interface on the RNC side, which are the MBMS SESSION START message from the core network (CN) to the RNC and the MBMS SESSION START RSPPONSE message from the RNC to the CN. (3) Run the BSC6900 MML command DSP UCELLMBMSSERVICE. If the parameter Reason of service setup failure is Access Failure, the MBMS admission algorithm takes effect. 2. l 1. Disable the MBMS admission algorithm, and the services are successfully admitted. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect MBMS_UU_ADCTRL from the Cell CAC algorithm switch drop-down list to disable the MBMS admission algorithm. Deactivation Procedure
----End
Example
//Activating MBMS Admission Control MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-1, NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST; //Verifying MBMS Admission Control ADD URESERVEOVSF: CellId=1, DLOVSFSF=SF32, DLCODENO=20; DSP UCELLMBMSSERVICE: CellId=1; //Deactivating MBMS Admission Control MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-0;
217-2
Issue 02 (2011-07-11)
218 Configuring MBMS Load Control
218
Prerequisite
l l
Configuring MBMS Load Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061603 MBMS Load Control.
Context
The feature helps to lighten the cell load when the cell enters the congestion state and ensures the system stability. When the cell is in the basic congestion state and downlink congestion is detected, the power consumed by MBMS services is reduced.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select DL_UU_LDR(Downlink UU LDR Algorithm) and DL_UU_OLC (Downlink UU OLC Algorithm) from the Cell LDC algorithm switch drop-down list to enable downlink load reshuffling and downlink overload congestion control on the Uu interface. Run the BSC6900 MML command MOD UCELLLDR to set the congestion-relief action triggered by Load Reshuffling (LDR). Run the BSC6900 MML command ADD UCELLOLC to set the sequence and number of MBMS services to be released for Overload Control (OLC). Originate an MBMS service on the BSC6900, and ensure that service data is sent.
2. 3. l
Issue 02 (2011-07-11)
218 Configuring MBMS Load Control
2.
Run the BSC6900 MML command MOD UCELLLDM. Based on the current load of the cell, set the triggering thresholds for LDR and OLC. Ensure that the corresponding load control actions can be triggered. When the cell load exceeds the LDR threshold, the power of MBMS services is reduced in the cell. Check the maxFACH Power information element in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message on the Iub interface. When the cell load exceeds the OLC threshold, MBMS services are released. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect DL_UU_LDR(Downlink UU LDR Algorithm) and DL_UU_OLC (Downlink UU OLC Algorithm) from the Cell LDC algorithm switch drop-down list to disable downlink load reshuffling and downlink overload congestion control on the Uu interface. Optional: Run the BSC6900 MML command MOD UCELLLDR to remove the MBMS service power reduction from the LDR-triggered actions.
3.
4. l 1.
2. ----End
Example
//Activating MBMS Load Control //Enabling downlink load reshuffling and downlink overload congestion control on the Uu interface MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR-1&DL_UU_OLC-1; //Setting the first LDR-triggered action to power reduction of MBMS services MOD UCELLLDR: CellId=1, DlLdrFirstAction=MBMSDECPOWER; //Enabling the triggered OLC to release MBMS services on a one-by-one basis ADD UCELLOLC: CellId=1, SeqOfUserRel=MBMS_REL, MbmsOlcRelNum=1; //Verifying MBMS Load Control MOD UCELLLDM: CellId=1, DlLdrTrigThd=2, DlLdrRelThd=1, DlOlcTrigThd=2, DlOlcRelThd=1; //Deactivating MBMS Load Control MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR-0&DL_UU_OLC-0; MOD UCELLLDR: CellId=1, DlLdrFirstAction=NoAct;
218-2
Issue 02 (2011-07-11)
219 Configuring MBMS Transport Resource Management
219
Prerequisite
l l
Configuring MBMS Transport Resource Management
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061605 MBMS Transport Resource Management.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The features WRFD-010616 MBMS Introduction Package must be configured before this feature is activated.
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
Issue 02 (2011-07-11)
219 Configuring MBMS Transport Resource Management
The feature does not need to be activated. l Verification Procedure 1. 2. 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. The BROADCAST REFERENCE IEs in the two COMMON TRANSPORT CHANNEL SETUP REQUEST messages are different. This indicates that the messages are from different Iub interfaces. Both the COMMON TRANSPORT CHANNEL SETUP RESPONSE messages contain the TLA and Binding ID. l Deactivation Procedure This feature does not need to be deactivated. ----End
219-2
Issue 02 (2011-07-11)
220 Configuring Streaming Service on MBMS
220
Prerequisite
l l
Configuring Streaming Service on MBMS
This section describes how to activate, verify, and deactivate the optional feature WRFD-01061606 Streaming Service on MBMS.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies 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.
Context
This feature enables the MBMS service to be carried on the PS streaming class, therefore 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.
Issue 02 (2011-07-11)
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.
220 Configuring Streaming Service on MBMS
Deactivation Procedure This feature is used as long as MBMS is configured. There is no need to deactivate this feature.
----End
220-2
Issue 02 (2011-07-11)
221 Configuring 16/32/64/128Kbps Channel Rate on MBMS
221
Prerequisite
l l
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.
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 The feature does not need to be activated. 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.
----End
222 Configuring MBMS Phase 2
222
Prerequisite
l l
Configuring MBMS Phase 2
This section describes how to activate, verify, and deactivate the optional feature WRFD-010660 MBMS Phase 2.
l l
License The license controlling this feature has been 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 Activation Procedure For details about activation procedures, see the following sections: 223 Configuring MBMS Enhanced Broadcast Mode 224 Configuring MBMS P2P over HSDPA 225 Configuring MBMS Admission Enhancement
222 Configuring MBMS Phase 2
226 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users ----End
222-2
Issue 02 (2011-07-11)
223 Configuring MBMS Enhanced Broadcast Mode
223
Prerequisite
l l
Configuring MBMS Enhanced Broadcast Mode
This section describes how to activate, verify, and deactivate the optional feature WRFD-01066001 MBMS Enhanced Broadcast Mode.
Context
Compared with broadcast mode, it is a more efficient way to deploy the point-to-multipoint services, such as mobile TV. This feature can be activated only after MBMS basic functions are enabled. For details, see the section "Configuring MBMS Introduction Package". The CN specifies whether broadcast mode or enhanced broadcast mode is used for MBMS services. If the CN specifies the enhanced broadcast mode and the license for this mode is activated, then, enhanced broadcast mode is used. The MBMS transmission mode should be configured on the RNC. The MBMS transmission mode can be configured at the SA level, RNC level, or cell level. The cell level has the highest priority, while the RNC level has the lowest priority. That is, if the MBMS transmission mode is configured at both the RNC level and the cell level, the cell level configuration takes effect in the corresponding cell. The detailed process is as follows:
Procedure
l
Issue 02 (2011-07-11)
223 Configuring MBMS Enhanced Broadcast Mode
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;
223-2
Issue 02 (2011-07-11)
224 Configuring MBMS P2P over HSDPA
224
Prerequisite
l l
Configuring MBMS P2P over HSDPA
This section describes how to activate, verify, and deactivate the optional feature WRFD-01066002 MBMS P2P over HSDPA.
Dependencies on Hardware This feature does not depend on the hardware. Dependencies on Other Features The features WRFD-010616 MBMS Introduction Package and WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated.
Context
This feature enables Multimedia Broadcast and Multicast Service point-to-point (MBMS P2P) services to be carried on the HS-DSCH, saving cell resources.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET URNCMBMSPARA. In this step, set Mbms Transfer Mode to DYNAMIC. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set Service Mapping Strategy Switch to MAP_PS_STREAM_ON_HSDPA_SWITCH. Set up a 256 kbit/s MBMS streaming service. Use an MBMS-capable UE to request the MBMS service and receive the corresponding data.
l
Issue 02 (2011-07-11)
224 Configuring MBMS P2P over HSDPA
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;
224-2
Issue 02 (2011-07-11)
225 Configuring MBMS Admission Enhancement
225
Prerequisite
l l
Configuring MBMS Admission Enhancement
This section describes how to activate, verify, and deactivate the optional feature WRFD-01066003 MBMS Admission Enhancement.
Context
This feature provides different admission policies for Multimedia Broadcast and Multicast Service point-to-multipoint (MBMS PTM) services and MBMS point-to-point (MBMS PTP) services. MBMS PTP services use the same admission, preemption, and congestion criteria with normal services except MBMS HSDPA services. MBMS PTM services should be treated differently so that they do not occupy excessive resources to block non-MBMS connection admission. In addition, some resources should be reserved for MBMS PTM services.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command SET UQUEUEPREEMPT to set Mbms PreemptAlgoSwitch and Preempt algorithm switch to ON. 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 parameter settings sent by the CN. The parameter settings of PTP services are sent by the CN and do not need to be set manually.
l
Issue 02 (2011-07-11)
225 Configuring MBMS Admission Enhancement
1. 2. 3.
Run the BSC6900 MML command LST URNCMBMSPARA to check the configuration. Enable a low-priority user to access the cell. Enable the admission algorithm, and then limit cell resources so that the admission resources in the cell are insufficient. In this case, the MBMS services successfully preempt common services. An example is given as follows: (1) Run the BSC6900 MML command ADD URESERVEOVSF to reserve the downlink OVSF for the cell so that only 64 kbit/s services are supported in the cell. (2) Originate a 256 kbit/s service. Check the messages traced on the Iu interface on the RNC side, which are the MBMS SESSION START message from the CN to the RNC and the MBMS SESSION START RSPPONSE message from the RNC to the CN.
4.
Run the BSC6900 MML command DSP UCELLMBMSSERVICE. If the parameter Current State of Service Session is Setuping, the user connection is released due to preemption. Run the BSC6900 MML command MOD UCELLALGOSWITCH to set Mbms PreemptAlgoSwitch to OFF.
----End
Example
//Activating MBMS Admission Enhancement SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, MbmsPreemptAlgoSwitch=ON; SET URNCMBMSPARA: MbmsTransMode=PTM, PtmPreemptSwitch=ON, PtmStrmPasiSwitch=ON, PtmNullStrmPasiSwitch=ON; //Verifying MBMS Admission Enhancement ADD URESERVEOVSF: CellId=1, DLOVSFSF=SF32, DLCODENO=20; DSP UCELLMBMSSERVICE: CellId=1; //Deactivating MBMS Admission Enhancement SET UQUEUEPREEMPT: MbmsPreemptAlgoSwitch=OFF;
225-2
Issue 02 (2011-07-11)
226 Configuring Inter-Frequency Neighboring Cell Selection for MBMS PTP Users
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.
226
l l
Configuring Inter-Frequency
Prerequisite
Dependencies on Hardware This feature does not depend on the hardware. Dependencies 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 License The license controlling this feature has been activated.
Context
This feature enables the filtering and handover of a target cell based on the MBMS channel resources in the inter-frequency neighboring cells, therefore ensuring the continuity of the MBMS service.
Procedure
l l l Activation Procedure The 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
227 Configuring FACH Transmission Sharing for MBMS
227
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010616 MBMS Introduction Package has been configured before this feature is activated.
Context
This feature enables the FACHs that carry MBMS services to share transport resources over the Iub interface, thereby saving the Iub bandwidth.
Procedure
l Activation Procedure 1. l Run the BSC6900 MML command SET UMBMSSWITCH. In this step, set MBMS Iub Sharing Switch to ON(ON). Before turning on the transmission sharing switch, activate the MBMS services in two cells served by the same NodeB. View the tracing messages over the Iub interface. 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 transmitted over different Iub interfaces. Turn on the transmission sharing switch, activate the MBMS services in two cells served by the same NodeB, and view the tracing messages over the Iub interface.
2.
Issue 02 (2011-07-11)
227 Configuring FACH Transmission Sharing for MBMS
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 transmitted over the same Iub interface. This feature has been activated. l Deactivation Procedure 1. ----End Run the BSC6900 MML command SET UMBMSSWITCH. In this step, set MBMS Iub Sharing Switch to OFF(OFF).
Example
//Activating FACH Transmission Sharing for MBMS SET UMBMSSWITCH: MbmsSwitch=ON, MbmsIubSharingSwitch=ON; //Deactivating FACH Transmission Sharing for MBMS SET UMBMSSWITCH: MbmsSwitch=ON, MbmsIubSharingSwitch=OFF;
227-2
Issue 02 (2011-07-11)
228 Configuring MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion)
228
Prerequisite
l l
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).
l l
License The license controlling this feature has been activated. Others Prerequisites UEs support this feature.
Context
Frequency Layer Convergence (FLC) denotes the process where the UTRAN requests UEs to preferentially reselect to the frequency layer on which the MBMS service is intended to be transmitted. Frequency Layer Dispersion (FLD) denotes the process where the UTRAN redistributes UEs across frequencies. FLC helps users obtain the information about an MBMS service in real time. FLD reduces cell load after the MBMS service is finished. FLD is activated automatically after FLC takes effect, and is deactivated automatically after FLC is disabled.
Issue 02 (2011-07-11)
228-1
228 Configuring MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion)
Procedure
NOTE
Two overlapping cells covered by multiple carriers must be enabled with MBMS. The cell using frequency F1 is in the SA of MBMS, and other cells using other frequencies are not in the SA of MBMS.
1. 2.
Run the BSC6900 MML command MOD UCELLMCCH. In this step, set Flc Algo Switch to ON(ON). Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the HO_ALGO_MBMS_FLC_SWITCH check box under the parameter HandOver Switch. Configure an MCCH in an R99 cell and set an MBMS cell to the neighboring cell of the R99 cell. Make UEs camp on the R99 cell, activate the MBMS service, and accept the MBMS service. If UEs are reselected to the MBMS cell successfully and transmit and receive data normally, FLC is activated. Move UEs to the MBMS cell edge and terminate the MBMS service. If some UEs are reselected to the R99 cell, FLD is activated. Run the BSC6900 MML command MOD UCELLMCCH. In this step, set Flc Algo Switch to OFF(OFF). Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect the HO_ALGO_MBMS_FLC_SWITCH check box under the parameter HandOver Switch.
3. l
----End
Example
//Activating MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion) MOD UCELLMCCH: CellId=1, FlcAlgoSwitch=ON; SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-1; //Deactivating MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion) MOD UCELLMCCH: CellId=1, FlcAlgoSwitch=OFF; SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-0;
228-2
Issue 02 (2011-07-11)
229
Prerequisite
l l
Configuring MBMS over Iur
This section describes how to activate, verify, and deactivate the optional feature WRFD-010661 MBMS over Iur.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010660 MBMS Phase 2 has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Other Prerequisites The neighboring RNC supports the MBMS feature. The Point to Point (PTP) services are supported.
Context
This feature extends the application scope of the MBMS service.
Procedure
l Activation Procedure This feature does not need to be activated. It takes effect after the feature WRFD-010616 MBMS Introduction Package is activated. l Verification Procedure Initiate a softt handover by moving a UE that is in CELL_DCH state and receiving the MBMS data in PTP mode from the Serving RNC (SRNC) to the Drift RNC (DRNC). In this way, a Radio Link (RL) is established on the Iur interface. The cell to which the RL belongs performs the MBMS service in Point to Multipoint (PTM) mode. If at the time being the UE under the DRNC is receiving only MBMS data in PTM mode, this feature has been activated. l
Issue 02 (2011-07-11)
This feature does not need to be deactivated. ----End
229-2
Issue 02 (2011-07-11)
230 Configuring Dynamic Power Estimation for MTCH
230
Prerequisite
l l
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.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The feature WRFD-010660 MBMS Phase 2 has been configured before this feature is activated.
Context
This feature enables dynamic adjustment of the transmit power of the MTCH based on the number of neighboring cells that are in PTM mode. It does not conflict with the maximum power and minimum power defined in the MBMS service. In addition, this feature depends on the MBMS service, because it introduces only power deviation.
Procedure
l Activation Procedure This feature does not need to be activated. Telecom operators only need to set the power adjustment threshold to an appropriate value. 1. Run the BSC6900 MML command SET URNCMBMSPARA. In this step, set Combine Neighbour Cell Percent to an appropriate value based on the network plan. When the rate of PTM applications in a cell in PTM mode reach the value of this parameter, this feature brings a combining gain. If Combine Neighbour Cell Percent is set to a small value, the transmit power of the MBMS SCCPCH in the cell decreases.
Issue 02 (2011-07-11)
230 Configuring Dynamic Power Estimation for MTCH
Verification Procedure 1. Select two MBMS cells (cell A and cell B) that work in the same frequency. In cell A, configure only cell B as its intra-frequency neighboring cell. Apply the PTM mode in cell A and PTP mode in cell B. Use an MBMS-capable UE to initiate an MBMS service in cell A. View the NBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub interface to check the power of the FACH that carries the service. Set cell B to send MBMS data in the same channel in PTM mode. In this manner, the rate of the intra-frequency neighboring cells that apply the PTM mode exceeds the value of the preset Combine Neighbour Cell Percent. View the NBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub interface to check the power of the FACH that carries the service. Expected result: The power of the FACH that carries data of the MBMS channel decreases by 5 dB.
2.
3.
4.
----End
Example
//Setting the Power Adjusting Threshold SET URNCMBMSPARA: CombNCellPercent=50;
230-2
Issue 02 (2011-07-11)
231 Configuring MSCH Scheduling
231
Prerequisite
l l
Configuring MSCH Scheduling
This section describes how to activate, verify, and deactivate the optional feature WRFD-010663 MSCH Scheduling.
Context
This feature enables a UE to receive packets on the MTCH in Discontinuous Reception (DRX) mode, thereby reducing UE power consumption.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UMBMSSWITCH. In this step, set both Msch Switch For NonMtchMulti Sccpch and Msch Switch For MtchMulti Sccpch to ON(ON). Use an MBMS-capable UE to initiate an MBMS service and ensure that the UE can receive the MBMS data. Check messages traced on the Uu interface. If MSCH configuration information is found in the MBMS CURRENT CELL P-T-M RB INFORMATION, MBMS GENERAL INFORMATION, and MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages, this feature has been activated.
Issue 02 (2011-07-11)
231-1
231 Configuring MSCH Scheduling
1.
Run the BSC6900 MML command SET UMBMSSWITCH. In this step, set both Msch Switch For NonMtchMulti Sccpch and Msch Switch For MtchMulti Sccpch to OFF(OFF).
----End
Example
//Activating MSCH scheduling SET UMBMSSWITCH: MbmsSwitch=ON, MschSwitchForNonMtchMulti=ON, MschSwitchForMtchMulti=ON; //Deactivating MSCH scheduling SET UMBMSSWITCH: MschSwitchForNonMtchMulti=OFF, MschSwitchForMtchMulti=OFF;
231-2
Issue 02 (2011-07-11)
232 Configuring MBMS Channel Audience Rating Statistics
232
Prerequisite
l l
Configuring MBMS Channel Audience Rating Statistics
This section describes how to activate, verify, and deactivate the optional feature WRFD-010665 Configuring MBMS Channel Audience Rating Statistics.
l l
License The license controlling this feature has been activated. Other Prerequisites The BMSC on the CN side identifies the channel with a fixed Temporary Mobile Group Identity (TMGI) when delivering a program source.
Context
This feature enables statistics on MBMS channels to help the operator obtain the audience rating of the MBMS channels.
Procedure
l l Activation Procedure This feature does not need to be activated. Verification Procedure Set the MBMS channels (a maximum of five MBMS channels can be set) on which statistics is to be performed. Then, send the TMGIs of these channels from the M2000 to the RNC. The RNC then measures the following channel-related counters: Average number of users in PTP mode Average number of users in PTM mode
232 Configuring MBMS Channel Audience Rating Statistics
Time for channels remaining in PTM mode TTime for channels remaining in PTP mode Based on the preceding counters, the average duration for which each UE is connected to a channel can be calculated. l Deactivation Procedure This feature does not need to be deactivated.
----End
232-2
Issue 02 (2011-07-11)
233 Configuring Domain Specific Access Control (DSAC)
233
Prerequisite
l l l l
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).
Dependencies on Hardware DSAC is based on the CN overload message and therefore the CN nodes should support this message on the Iu interface. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Other Prerequisites DSAC is a feature specified in 3GPP Release 6, and therefore only the UEs of Release 6 or later support this feature.
Context
DSAC specifies the UE access restriction based on the domain type (CS, PS, or CS+PS). The feature can be triggered either manually or automatically.
Procedure
l Activation Procedure 1. To activate manual DSAC, run the BSC6900 MML command ADD UCELLDSACMANUALPARA. To restrict the UE access to the CS domain, set Restriction for CS to TRUE; to restrict the UE access to the PS domain, set Restriction for PS to TRUE. To set a fixed access restriction, set Restriction Type to RestrictionFixed and select the access classes (ACs) to be restricted from the drop-down list of AC Restriction Indicator. To set a flexible access restriction, set Restriction Type
to RestrictionFlexible, and set Number of restrained AC every time, Range of restrained AC, and Interval of DSAC Restriction to appropriate values. 2. To activate automatic DSAC, run the BSC6900 MML command SET UDSACAUTOALGO. In this step, set Switch for auto DSAC to ON. To restrict the UE access to the CS domain, set Restriction for CS to TRUE; to restrict the UE access to the PS domain, set Restriction for PS to TRUE. Set Number of restrained Access Class every time, Range of restrained Access Class, Access Class Restriction interval between Cells, and Interval length of Domain Specific Access Class Restriction to appropriate values. l Verification Procedure 1. 2. Start Uu Interface Trace on the BSC6900 LMT. Under Uu Message Type, select RRC_SYS_INFO_TYPE3. Check whether manual or automatic DSAC is activated by viewing the IE domainSpecificAccessRestrictionParametersForPLMNOfMIB in the SIB3 message traced on the Uu interface. If the value of AccessClassBarred in the IE domainSpecificAccessRestrictionParametersForPLMNOfMIB is barred (0), as shown in Figure 233-1, this feature has been activated. If the value of AccessClassBarred in the IE domainSpecificAccessRestrictionParametersForPLMNOfMIB is notBarred (1), as shown in Figure 233-2, this feature is not activated. Figure 233-1 DSAC activated
233-2
Issue 02 (2011-07-11)
Figure 233-2 DSAC not activated
Deactivation Procedure 1. 2. To deactivate manual DSAC, run the BSC6900 MML command RMV UCELLDSACMANUALPARA. To deactivate automatic DSAC, run the BSC6900 MML command SET UDSACAUTOALGO. In this step, set Switch for auto DSAC to OFF.
----End
Example
//Activating DSAC ADD UCELLDSACMANUALPARA: CellId=223, CnOpIndex=0, CsRestriction=TRUE, PsRestriction=TRUE, RestrictionType=RestrictionFlexible, NumberOfACs=4, AcRange=AC0-1&AC1-1&AC2-1&AC3-1&AC4-1&AC5-1&AC6-1&AC7-1&AC8-1&AC9-1&AC100&AC11-0&AC12-0&AC13-0&AC14-0&AC15-0, AcRstrctIntervalLen=10; SET UDSACAUTOALGO: DsacAutoSwitch=ON, CsRestriction=TRUE, PsRestriction=TRUE, NumberOfACs=2, AcRange=AC0-1&AC1-1&AC2-1&AC3-1&AC4-1&AC5-1&AC6-1&AC7-1&AC8-1&AC9-1&AC100&AC11-0&AC12-0&AC13-0&AC14-0&AC15-0, AcIntervalOfCells=1, AcRstrctIntervalLen=10; //Deactivating DSAC RMV UCELLDSACMANUALPARA: CellId=223, CnOpIndex=0; SET UDSACAUTOALGO: DsacAutoSwitch=OFF;
Issue 02 (2011-07-11)
233-3
234 Configuring One Tunnel
234
Prerequisite
l l l l Dependencies on Hardware License
Configuring One Tunnel
This section describes how to activate, verify, and deactivate the optional feature WRFD-020111 One Tunnel.
This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. The license controlling this feature has been activated. Other Prerequisites The gateway GPRS support node (GGSN) and Serving GPRS Support Node (SGSN) support this feature.
Context
With this feature, there is only one tunnel between the RNC and the GGSN and no tunnel between the SGSN and the RNC. This feature improves efficiency of PS traffic and prevents the SGSN from being the bottleneck of a network when PS traffic is heavy.
Procedure
l Activation Procedure 1. Configure transmission resources. For details about transmission resource configuration, see the section Configuring the Iu-PS Interface in the BSC6900 UMTS Initial Configuration Guide.
NOTE
l Whether the SGSN and GGSN support the one tunnel function can be queried by using commands on these two sides.
Verification Procedure 1. Start message tracing on the Iu interface on the BSC6900 LMT by referring to Tracing Messages on the Iu Interface.
Issue 02 (2011-07-11)
2. 3.
Use a UE to initiate a PS service. View the transportLayerAddress information element (IE) in the RANAP_RAB_ASSIGNMENT_REQ message traced during Iu interface message tracing. Figure 234-2 Iu Interface Trace dialog box
4.
If the value of the transportLayerAddress IE is the GGSN IP address preset during the transmission resource configuration, it indicates that this feature is activated.
Figure 234-3 Configured GGSN IP address
234-2
Issue 02 (2011-07-11)
1. ----End
The feature does not need to be deactivated on the RAN side.
Issue 02 (2011-07-11)
234-3
235 Configuring IP Transmission Introduction on Iub Interface
235
Prerequisite
l
Configuring IP Transmission Introduction on Iub Interface
This section describes how to activate, verify, and deactivate the optional feature WRFD-050402 IP Transmission Introduction on Iub Interface.
Dependencies on Hardware To use the IP header compression function on the Iub interface, the PEUa or POUa board is required. Only the Dopra Linux OS supports the built-in firewall function for O&M. Only the FG2c and GOUc boards of the BSC6900 support the built-in firewall function for interfaces. Only the FG2a, GOUa, FG2c and GOUc boards of the BSC6900 support Bidirectional Forwarding Detection (BFD). Dependencies on 3900 series base stations: In RAN11.0, only 3900 series base stations support this feature. In RAN12.0, BTS3812E/AE, DBS3800, and 3900 series base stations support this feature.
l l
Context
This feature provides a new lub transmission solution for operators. Compared with ATM transmission, IP transmission reduces the transmission costs of HSDPA and HSUPA services. This feature enhances Iub transmission by introducing the following functions: BFD-based IP fault detection, built-in firewall on the RNC side, and built-in firewall on the NodeB side. l If BFD-based IP fault detection is enabled, the BSC6900 triggers a port switchover, board switchover, or IP rerouting when detecting that the gateway or the peer entity becomes faulty. BFD can be classified into multi-hop BFD and single-hop BFD:
Issue 02 (2011-07-11)
In multi-hop BFD, the IP addresses of the local and peer ports must be on different network segments. In single-hop BFD, the IP addresses of the local and peer ports must be on the same network segment. l l The built-in firewall on the RNC side safeguards IP Ethernet ports on interface boards and O&M ports against network attacks. The built-in firewall on the NodeB side safeguards the Iub interface against network attacks during IP transmission.
Procedure
l Activation Procedure 1. 2. 3. 4. Run the BSC6900 MML command SET ETHPORT to set the attributes of an Ethernet port. In this step, takes the FG2c board as an example. Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet port. Run the BSC6900 MML command STR IPCHK to configure the BFD check. In this step, set Check type to SBFD. Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall function for an interface board. In this step, set Board type. to FG2c and ARP Learning Strict Switch to ON.
NOTE
The FG2c and GOUc boards support both the invalid packet detection function and the ARP learning strict function. The FG2a and GOUa boards support only the ARP learning strict function.
5.
(Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS supports the built-in firewall function) by performing the following operations: Log in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux command iptables -A INPUT s restricted IP -i Ethernet adapter p transport protocol --dport restricted port j DROP. Here, restricted IP refers to the IP address that needs to be prohibited or allowed, and it can be a single IP address or a network segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to be prohibited. If p transport protocol and --dport restricted port are not specified, all ports are disabled. Run the BSC6900 MML command ADD PPPLNK to configure head compress for a PPP link. In this step, set Head compress to UDP/IP_HC(UDP/IP_HC). Run the BSC6900 MML command ADD MPGRP to configure head compress for a PPP link group. In this step, set Head compress to UDP/IP_HC(UDP/IP_HC).
NOTE
6.
Head compress must be configured on peer equipment.
7.
Run the NodeB MML command ADD PPPLNK to enable head compress for a PPP link. Run the NodeB MML command ADD MPGRP to enable head compress for a PPP link group. Run the NodeB MML command ADD ACL to add an access control list (ACL). Run the NodeB MML command ADD ACLRULE to add a rule to the ACL.
NOTE
8. 9.
Before adding a rule to an ACL, ensure that the ACL has already existed.
l
235-2
1. 2. 3. 4. 5. 6.
Run the BSC6900 MML command DSP ETHPORT to query the attributes of an Ethernet port. Run the BSC6900 MML command LST ETHIP to query the IP address of the Ethernet port. Run the BSC6900 MML command DSP IPCHK to query whether the Check state is UP. Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP Connectivity Check Failure is reported. Run the BSC6900 MML command LST IPGUARD to check whether the value of ARP Learning Strict Switch is ON. Built response messages to ARP requests and sent to interface boards. Run the BSC6900 MML command DSP ARP to query the ARP table of interface boards. If the information of interface boards in ARP table do not update, the ARP Learning Strict Switch is valid. If any invalid packet exists, run the BSC6900 MML command DSP INVALIDPKTINFO to query the detailed information. (Optional) Log in to the computer whose IP address is prohibited and check whether the prohibited services can be performed. Run the Dopra Linux command iptables L. All the filtering rules on the OMU will be listed, and check whether new rules are added successfully. If port 80 is disabled, logging in to the BSC6900 LMT is prohibited. Check whether you can log in to the BSC6900 LMT on the PC whose port 80 is disabled. If port 22 is disabled, the OMU cannot be logged in to remotely. Check whether you can log in to the BSC6900 OMU through Putty on the PC whose port 22 is disabled. If port 21 is disabled, FTP services of the OMU cannot be used. Check whether you can connect to the FTP server of the BSC6900 OMU through an FTP client on the PC whose port 21 is disabled.
7. 8.
9.
Run the BSC6900 MML command DSP PPPLNK or DSP MPGRP to query whether the Code compress type is UDP/IP_HC.
10. Run the NodeB MML command DSP PPPLNK or DSP MPGRP to check whether the compress state is enable. 11. Run the NodeB MML command LST ACL to check whether an ACL has been configured. 12. Run the NodeB MML command LST ACLRULE to check whether a rule has been added to the ACL. 13. Run the NodeB MML command DSP PACKETFILTER to check whether a port is bound to the ACL. 14. Run the NodeB MML command PING to use IP addresses that are not listed in the ACL to ping the port supporting the packet filtering function. If no response is received, the built-in firewall on the NodeB side has been activated. l Deactivation Procedure 1. 2. Run the BSC6900 MML command STP IPCHK to stop the BFD. Run the BSC6900 MML command SET IPGUARD. In this step, set Board type to FG2c and ARP Learning Strict Switch to OFF.
Issue 02 (2011-07-11)
235-3
3. 4. 5.
Run the BSC6900 MML command RMV ETHIP to remove an IP address from the Ethernet port. Run the BSC6900 MML command SET ETHPORT. In this step, set Port type to FE. (Optional) Log in to the OMU through the LMT locally or through Putty remotely. Run the Dopra Linux command iptables -D INPUT s restricted IP -i Ethernet adapter p transport protocol --dport restricted port j DROP. Here, restricted IP is the IP address that needs to be prohibited or allowed, and it can be a single IP address or a network segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to be prohibited, and it is used together with the transport protocol. If p transport protocol and --dport restricted port are not specified, all ports are disabled. (Optional) Run the Dopra Linux command iptables L. All the filtering rules on the OMU will be listed, and check whether new rules are removed successfully. Run the BSC6900 MML command MOD PPPLNK or MOD MPGRP. In this step, set Head compress to No_HC. Run the NodeB MML command RMV PPPLNK to remove a PPP link. Run the NodeB MML command RMV MPGRP to remove a PPP link group. Run the NodeB MML command RMV PACKETFILTER to remove the binding relationship between the port and the ACL.
6. 7. 8. 9.
10. Run the NodeB MML command RMV ACLRULE to remove all the rules from the ACL. 11. Run the NodeB MML command RMV ACL to remove the ACL. ----End
Example
//Configuring the attributes of an Ethernet port and adding an IP address to the port SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0; ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.171.35.123", MASK="255.255.255.0"; //Activating BFD-based IP fault detection on an interface board STR IPCHK: SRN=0, SN=14, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=0, MODE=CHECK_ON_PRIMARY_PORT, PEERIP="99.9.9.100"; //Activating the built-in firewall function on an RNC interface board SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=ON; //Activating the built-in firewall function for O&M on the RNC //For example, only the IP addresses on the 10.141.148.0 network segment is allowed to access the LMT iptables -A INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport 80 -j DROP //Activating IP head compress for a PPP link ADD PPPLNK: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=0, DS1=0, TSBITMAP=TS1-1, BORROWDEVIP=NO, LOCALIP="5.5.5.5", MASK="255.255.255.0", PEERIP="5.5.5.6", IPHC=UDP/IP_HC, PPPMUX=Disable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF, OPSEPFLAG=OFF; //Activating IP head compress for a PPP link group ADD MPGRP: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=0, MPTYPE=MCPPP, BORROWDEVIP=NO, LOCALIP="5.5.5.5", MASK="255.255.255.0", PEERIP="5.5.5.6", MHF=LONG, PPPMUX=Disable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V, ERRDETECTSW=OFF, ANTIERRFLAG=OFF, OPSEPFLAG=OFF; //Activating IP head compress for a PPP link on NodeB ADD PPPLNK: SRN=0, SN=0, SBT=E1_COVERBOARD, AUTH=NONAUTH, TSN=TS1-1,
235-4
Issue 02 (2011-07-11)
IPHC=ENABLE; //Activating IP head compress for a PPP link group on NodeB ADD MPGRP: SRN=0, SN=0, SBT=E1_COVERBOARD, AUTH=NONAUTH, IPHC=ENABLE; //Activating the built-in firewall function on the NodeB ADD ACL: ACLID=3000, ACLDESC="ACL_TEST"; ADD ACLRULE: ACLID=3000, RULEID=1, PT=IP, SIP="192.168.1.1", SWC="0.0.0.0", DIP="10.10.1.101", DWC="0.0.0.0", MDSCP=NO; ADD PACKETFILTER: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, ACLID=3000; //Querying the attributes and IP address of an Ethernet port DSP ETHPORT: SRN=0, SN=14; LST ETHIP: SRN=0, SN=14, PN=0; //Verifying BFD-based IP fault detection DSP IPCHK: SRN=0, SN=14; //Verifying the built-in firewall function on an RNC interface board LST IPGUARD: SRN=0, SN=14; DSP ARP: SRN=0, SN=14; DSP INVALIDPKTINFO: SRN=0, SN=14; //Verifying IP head compress for a PPP link DSP PPPLNK: SRN=0, SN=14, PPPLNKN=0; //Verifying IP head compress for a PPP link group DSP MPGRP: SRN=0, SN=14, MPGRPN=0; //Verifying IP head compress for a PPP link on NodeB DSP PPPLNK:; //Verifying IP head compress for a PPP link group DSP MPGRP:; //Verifying the built-in firewall function on the NodeB LST ACL: ACLID=3000; LST ACLRULE: ACLID=3000, RULEID=1; DSP PACKETFILTER:; PING: SN=7, SRCIP="192.168.1.1", DSTIP="192.168.2.2", CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0; //Deactivating BFD-based IP fault detection STP IPCHK: SRN=0, SN=14, CHKN=0; //Deactivating the built-in firewall function on an RNC interface board SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=OFF; //Removing an IP address from an Ethernet port and modifying the attributes of the Ethernet port RMV ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0; SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=FE, PN=0; //Deactivating the built-in firewall function for O&M iptables -D INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport 80 -j DROP //Deactivating IP head compress for a PPP link MOD PPPLNK: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=0, IPHC=No_HC; //Deactivating IP head compress for a PPP link group MOD MPGRP: SRN=0, SN=14, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=0, IPHC=No_HC; //Deactivating IP head compress for a PPP link on NodeB RMV PPPLNK: SRN=0, SN=0, SBT=E1_COVERBOARD; //Deactivating IP head compress for a PPP link group on NodeB RMV MPGRP: SRN=0, SN=0, SBT=E1_COVERBOARD; //Deactivating the built-in firewall function on the NodeB RMV PACKETFILTER: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0; RMV ACLRULE: ACLID=3000, RULEID=1; RMV ACL: ACLID=3000;
Issue 02 (2011-07-11)
235-5
236 Configuring Hybrid Iub IP Transmission
236
Prerequisite
l l
Configuring Hybrid Iub IP Transmission
This section describes how to activate, verify and deactivate the optional feature WRFD-050403 Hybrid Iub IP Transmission.
Dependencies on Hardware BTS3902E does not support this feature. Dependencies 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 controlling this feature has been activated. Other Prerequisites The RNC and NodeB support IP transmission. The control-plane data and physical device data of the IP-based Iub interface is configured.
Context
In hybrid IP transmission, real-time services and non-real-time services are transmitted on discrete paths to meet different requirements of services in the UMTS system. Two types of hybrid transmission are available: FE+E1/T1 and FE+FE.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command ADD UNODEB to add a NodeB. In this step, set IUB Trans Bearer Type to HYBRID_IP_TRANS. Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. In this step, set the parameter Adjacent Node Type to IUB and the parameter Transport Type to HYBIRD_IP.
Issue 02 (2011-07-11)
3.
Run the BSC6900 MML command ADD IPPATH to add an IP path. In this step, set the parameter Interface Type to IUB and the parameter Transport Type to HYBIRD_IP.
NOTE
If IP Path Type is set to QOS or BE-EF, the path is a high-priority path and usually E1/T1 transmission is applied. If IP Path Type is set to LQ_QOS or LQ_BE-LQ_EF, the path is a low-priority path and usually FE transmission is applied.
4. 5.
Run the BSC6900 MML command ADD TRMMAP. In this step, set Interface Type to IUB and Transport Type to HYBIRD_IP. Run the BSC6900 MML command ADD ADJMAP. In this step, set Interface Type to IUB, and Transport Type of the adjacent node and interface type 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. Run the BSC6900 MML command DSP IPCHN to query the type of services carried in the IP path, and the forward bit rate and backward bit rate of the services. Run the BSC6900 MML command RMV ADJMAP to remove the TRM mapping to the adjacent node on the Iub interface. Run the BSC6900 MML command RMV TRMMAP to remove the transmission resource mapping on the Iub interface. Run the BSC6900 MML command RMV IPPATH to remove the IP path on the Iub interface.
2. l
Deactivation Procedure 1. 2. 3.
----End
Example
//Activating Hybrid Iub IP Transmission //Adding a NodeB ADD UNODEB: NodeBName="test", NodeBId=115, SRN=0, SN=0, TnlBearerType=HYBRID_IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; //Adding an adjacent node ADD ADJNODE: ANI=115, NAME="test", NODET=IUB, NODEBID=115, TRANST=HYBRID_IP; //Adding an IP path ADD IPPATH: ANI=115, PATHID=115, ITFT=IUB, TRANST=HYBRID_IP, PATHT=QoS, IPADDR="183.22.81.1", PEERIPADDR="22.22.22.23", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED; //Adding another IP path ADD IPPATH: ANI=115, PATHID=116, ITFT=IUB, TRANST=HYBRID_IP, PATHT=LQ_QOS, IPADDR="165.11.81.1", PEERIPADDR="22.22.22.23", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED; //Adding the transmission resource mapping ADD TRMMAP: TMI=115, ITFT=IUB, TRANST=HYBRID_IP, CCHPRIPATH=EF, CCHSECPATH=LQEF, SIPPRIPATH=EF, SIPSECPATH=LQEF, SRBPRIPATH=EF, SRBSECPATH=LQEF, VOICEPRIPATH=EF, VOICESECPATH=LQEF, CSCONVPRIPATH=AF42, CSCONVSECPATH=LQAF42, CSSTRMPRIPATH=AF42, CSSTRMSECPATH=LQAF42, PSCONVPRIPATH=AF42, PSCONVSECPATH=LQAF42, PSSTRMPRIPATH=AF42, PSSTRMSECPATH=LQAF42, PSINTHGHPRIPATH=AF21, PSINTHGHSECPATH=LQAF21,
236-2
Issue 02 (2011-07-11)
PSINTMIDPRIPATH=AF21, PSINTMIDSECPATH=LQAF21, PSINTLOWPRIPATH=AF21, PSINTLOWSECPATH=LQAF21, PSBKGPRIPATH=AF21, PSBKGSECPATH=LQAF21, HDSRBPRIPATH=EF, HDSRBSECPATH=LQEF, HDSIPPRIPATH=EF, HDSIPSECPATH=LQEF, HDVOICEPRIPATH=AF42, HDVOICESECPATH=LQAF42, HDCONVPRIPATH=AF42, HDCONVSECPATH=LQAF42, HDSTRMPRIPATH=AF42, HDSTRMSECPATH=LQAF42, HDINTHGHPRIPATH=LQBE, HDINTHGHSECPATH=BE, HDINTMIDPRIPATH=LQBE, HDINTMIDSECPATH=BE, HDINTLOWPRIPATH=LQBE, HDINTLOWSECPATH=BE, HDBKGPRIPATH=LQBE, HDBKGSECPATH=BE, HUSRBPRIPATH=EF, HUSRBSECPATH=LQEF, HUSIPPRIPATH=EF, HUSIPSECPATH=LQEF, HUVOICEPRIPATH=AF42, HUVOICESECPATH=LQAF42, HUCONVPRIPATH=AF42, HUCONVSECPATH=LQAF42, HUSTRMPRIPATH=AF42, HUSTRMSECPATH=LQAF42, HUINTHGHPRIPATH=LQBE, HUINTHGHSECPATH=BE, HUINTMIDPRIPATH=LQBE, HUINTMIDSECPATH=BE, HUINTLOWPRIPATH=LQBE, HUINTLOWSECPATH=BE, HUBKGPRIPATH=LQBE, HUBKGSECPATH=BE; //Adding the TRM mapping to the adjacent node ADD ADJMAP: ANI=115, ITFT=IUB, TRANST=HYBRID_IP, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=115, TMISLV=115, TMIBRZ=115, FTI=0, LEIGLD=0, LEISLV=0, LEIBRZ=0; //Verifying Hybrid Iub IP Transmission DSP IPCHN: ANI=115, PATHID=115; //Deactivating Hybrid Iub IP Transmission //Removing the TRM mapping to the adjacent node RMV ADJMAP: ANI=115,ITFT=IUB,CNMNGMODE=EXCLUSIVE; //Removing the transmission resource mapping RMV TRMMAP: TMI=115; //Removing IP paths RMV IPPATH: ANI=115, PATHID=115; RMV IPPATH: ANI=115, PATHID=116;
Issue 02 (2011-07-11)
236-3
237 Configuring ATM/IP Dual Stack NodeB
237
Prerequisite
l l
Configuring ATM/IP Dual Stack NodeB
This section describes how to activate, verify, and deactivate the optional feature WRFD-050404 ATM/IP Dual Stack NodeB.
Dependencies on Hardware BSC6900 is configured with both ATM interface boards and IP interface boards. BTS3902E does not support this feature. Dependencies on Other Features The feature WRFD-050402 IP Transmission Introduction on Iub Interface must be configured before this feature is activated.
l l
License The license controlling this feature has been activated. Other Prerequisites The ATM/IP transmission link from the RNC to the NodeB is configured.
Context
This feature allows Huawei NodeB to support the ATM/IP dual-stack transmission. Services with different QoS requirements can be carried on the links of different protocols. In addition, the transmission backup is also provided.
Procedure
Issue 02 (2011-07-11)
237-1

NOTE
When you allocate resources for ATM/IP dual stack-based transport on the Iub interface, take the following suggestions into consideration: l ATM transport, IP transport, or ATM/IP hybrid transport is applicable to control plane data. It is recommended that ATM/IP hybrid transport be applied to control plane data for security purposes. That is, the SAAL and SCTP links together carry an NCP or a CCP, and the SAAL link is the active link. l ATM transport, IP transport, or ATM/IP hybrid transport is applicable to user plane data. It is recommended that: l ATM transport be applied to signaling, voice services, CS conversational services, CS streaming services, PS conversational services, and PS streaming services. l IP transport be applied to PS interactive services, PS background services, HSDPA conversational services, HSDPA streaming services, HSDPA interactive services, HSDPA background services, HSUPA conversational services, HSUPA streaming services, HSUPA interactive services, and HSUPA background services. l Either ATM or IP transport is applicable to management plane data. It is recommended that IP transport be applied.
1. 2.
Run the BSC6900 MML command ADD UNODEB to add a NodeB. In this step, set IUB Trans Bearer Type to ATMANDIP_TRANS. Run the BSC6900 MML command ADD ADJNODE to add an adjacent node. In this step, set Adjacent Node Type to IUB and Transport Type to ATM_IP. If the node is a leaf node, set Is Root Node to YES; otherwise, set Is Root Node to NO. Run the BSC6900 MML command ADD TRMMAP. In this step, set Interface Type to IUB and Transport Type to ATM_IP. Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path. Run the BSC6900 MML command ADD IPPATH to add an IP path. In this step, set Interface Type to IUB and Transport Type to IP. Run the BSC6900 MML command ADD ADJMAP. In this step, set Interface Type to IUB and Transport Type of the adjacent node and interface type to ATM_IP. Use a UE to make a call. High-priority services can be carried on ATM paths and lowpriority services can be carried on IP paths. Run the BSC6900 MML command DSP IPPATH to check the state of the IP path and whether any resources of the path are occupied. Expected result: Operation state is Available, and some resources of the path are occupied.
3. 4. 5. 6.
3.
Run the BSC6900 MML command DSP AAL2PATH to check the state of the AAL2 path and whether any resources of the path are occupied. Expected result: Operation state is Available, and some resources of the path are occupied.
Deactivation Procedure 1. 2. Run the BSC6900 MML command RMV ADJMAP to remove the TRM mapping to the adjacent node. Run the BSC6900 MML command RMV TRMMAP to remove the transmission resource mapping on the Iub interface.
237-2
3. ----End
Run the BSC6900 MML command RMV IPPATH to remove the IP path on the Iub interface.
Example
//Configuring ATM/IP Dual Stack NodeB //Adding a NodeB ADD UNODEB: NodeBName="test", NodeBId=115, SRN=0, SN=0, TnlBearerType=ATMANDIP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; //Adding an adjacent node ADD ADJNODE: ANI=115, NAME="test", NODET=IUB, NODEBID=115, TRANST=ATM_IP, IsROOTNODE=YES, SAALLNKN=1; //Adding the transmission resource mapping ADD TRMMAP: TMI=115, ITFT=IUB, TRANST=ATM_IP; //Adding an AAL2 path ADD AAL2PATH: ANI=115, PATHID=115, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0, RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=115, RXTRFX=115, AAL2PATHT=R99; //Adding an IP path ADD IPPATH: ANI=115, PATHID=115, ITFT=IUB, TRANST=IP, PATHT=QoS, IPADDR="183.22.81.1", PEERIPADDR="22.22.22.23", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED; //Adding the TRM mapping to the adjacent node ADD ADJMAP: ANI=115, ITFT=IUB, TRANST=ATM_IP, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=115, TMISLV=115, TMIBRZ=115, FTI=0, LEIGLD=0, LEISLV=0, LEIBRZ=0; //Verifying ATM/IP Dual Stack NodeB DSP IPPATH: ANI=115, PATHID=115; DSP AAL2PATH: ANI=115, PATHID=115; //Deactivating ATM/IP Dual Stack NodeB //Removing the TRM mapping to the adjacent node RMV ADJMAP: ANI=115,ITFT=IUB,CNMNGMODE=EXCLUSIVE; //Removing the transmission resource mapping RMV TRMMAP: TMI=115; //Removing the IP path RMV IPPATH: ANI=115, PATHID=115;
Issue 02 (2011-07-11)
237-3
238 Configuring IP Transmission Introduction on Iu Interface
238
Prerequisite
l
Configuring IP Transmission Introduction on Iu Interface
This section describes how to activate, verify, and deactivate the optional feature WRFD-050409 IP Transmission Introduction on Iu Interface.
Dependencies on Hardware Only the Dopra Linux OS supports the built-in firewall function for O&M. Only the FG2c and GOUc boards of the BSC6900 support the built-in firewall function for interfaces. Only the FG2a, GOUa, FG2c and GOUc boards of the BSC6900 support Bidirectional Forwarding Detection (BFD).
l l
Context
This feature provides a new lu transmission solution for operators. Compared with ATM transmission, IP transmission can significantly reduce the transmission cost. This feature enhances Iu transmission by introducing the following functions: BFD-based IP fault detection and built-in firewall on the RNC side. l If BFD-based IP fault detection is enabled, the BSC6900 triggers a port switchover, board switchover, or IP rerouting when detecting that the gateway or the peer entity becomes faulty. BFD can be classified into multi-hop BFD and single-hop BFD: In multi-hop BFD, the IP addresses of the local and peer ports must be on different network segments. In single-hop BFD, the IP addresses of the local and peer ports must be on the same network segment. l The built-in firewall on the RNC side safeguards IP Ethernet ports on interface boards and O&M ports against network attacks.
Issue 02 (2011-07-11)
Procedure
l Activation Procedure The following takes the FG2c board as an example to describe the configuration operations. 1. 2. 3. 4. Run the BSC6900 MML command SET ETHPORT to set the attributes of an Ethernet port. Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet port. Run the BSC6900 MML command STR IPCHK. In this step, set Check type to SBFD. Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall function for an interface board. In this step, set Board type. to FG2c and ARP Learning Strict Switch to ON.
NOTE
5.
(Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS supports the built-in firewall function) by performing the following operations: Log in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux command iptables -A INPUT s restricted IP -i Ethernet adapter p transport protocol --dport restricted port j DROP. Here, restricted IP refers to the IP address that needs to be prohibited or allowed, and it can be a single IP address or a network segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to be prohibited. If p transport protocol and --dport restricted port are not specified, all ports are disabled. Run the BSC6900 MML command DSP ETHPORT to query the attributes of an Ethernet port. Run the BSC6900 MML command LST ETHIP to query the IP address of the Ethernet port. Run the BSC6900 MML command DSP IPCHK to query whether the Check state is UP. Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP Connectivity Check Failure is reported. Run the BSC6900 MML command LST IPGUARD to check whether the value of ARP Learning Strict Switch is ON. Built response messages to ARP requests and sent to interface boards. Run the BSC6900 MML command DSP ARP to query the ARP table of interface boards. If the information of interface boards in ARP table do not update, the ARP Learning Strict Switch is valid. If any invalid packet exists, run the BSC6900 MML command DSP INVALIDPKTINFO to query the detailed information. (Optional) Log in to the computer whose IP address is prohibited and check whether the prohibited services can be performed. Run the Dopra Linux command iptables L. All the filtering rules on the OMU will be listed, and check whether new rules are added successfully.
Verification Procedure 1. 2. 3. 4. 5. 6.
7. 8.
238-2
If port 80 is disabled, logging in to the BSC6900 LMT is prohibited. Check whether you can log in to the BSC6900 LMT on the PC whose port 80 is disabled. If port 22 is disabled, the OMU cannot be logged in to remotely. Check whether you can log in to the BSC6900 OMU through Putty on the PC whose port 22 is disabled. If port 21 is disabled, FTP services of the OMU cannot be used. Check whether you can connect to the FTP server of the BSC6900 OMU through an FTP client on the PC whose port 21 is disabled. l Deactivation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command STP IPCHK to stop the BFD. Run the BSC6900 MML command SET IPGUARD. In this step, set Board type to FG2c and ARP Learning Strict Switch to OFF. Run the BSC6900 MML command RMV ETHIP to remove an IP address from the Ethernet port. Run the BSC6900 MML command SET ETHPORT. In this step, set Port type to FE. (Optional) Log in to the OMU through the LMT locally or through Putty remotely. Run the Dopra Linux command iptables -D INPUT s restricted IP -i Ethernet adapter p transport protocol --dport restricted port j DROP. Here, restricted IP is the IP address that needs to be prohibited or allowed, and it can be a single IP address or a network segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to be prohibited, and it is used together with the transport protocol. If p transport protocol and --dport restricted port are not specified, all ports are disabled. (Optional) Run the Dopra Linux command iptables L. All the filtering rules on the OMU will be listed, and check whether new rules are removed successfully.
6. ----End
Example
//Configuring the attributes of an Ethernet port and adding an IP address to the port SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0; ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.171.35.123", MASK="255.255.255.0"; //Activating BFD-based IP fault detection STR IPCHK: SRN=0, SN=14, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=0, MODE=CHECK_ON_PRIMARY_PORT, PEERIP="99.9.9.100"; //Activating the built-in firewall function on an RNC interface board SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=ON; //Activating the built-in firewall function for O&M //For example, only the IP addresses on the 10.141.148.0 network segment is allowed to access the LMT iptables -A INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport 80 -j DROP //Querying the attributes and IP address of an Ethernet port DSP ETHPORT: SRN=0, SN=14; LST ETHIP: SRN=0, SN=14, PN=0; //Verifying BFD-based IP fault detection DSP IPCHK: SRN=0, SN=14; //Verifying the built-in firewall function on the RNC LST IPGUARD: SRN=0, SN=14; DSP ARP: SRN=0, SN=14; DSP INVALIDPKTINFO: SRN=0, SN=14;
Issue 02 (2011-07-11)
238-3
//Deactivating BFD-based IP fault detection STP IPCHK: SRN=0, SN=14, CHKN=0; //Deactivating the built-in firewall function on the RNC SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=OFF; //Removing an IP address from an Ethernet port and modifying the attributes of the Ethernet port RMV ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0; SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=FE, PN=0; //Deactivating the built-in firewall function for O&M iptables -D INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport 80 -j DROP
238-4
Issue 02 (2011-07-11)
239
Prerequisite
l
Configuring IP Transmission Introduction on Iur Interface
This section describes how to activate, verify, and deactivate the optional feature WRFD-050410 IP Transmission Introduction on Iur Interface.
Dependencies on Hardware Only the Dopra Linux OS supports the built-in firewall function for O&M. Only the FG2c and GOUc boards of the BSC6900 support the built-in firewall function for interfaces. Only the FG2a, GOUa, FG2c and GOUc boards of the BSC6900 support Bidirectional Forwarding Detection (BFD).
l l l
Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. Others Prerequisites The neighboring RNC supports IP transmission on the Iur interface.
Context
This feature provides a new lur transmission solution for operators. Compared with ATM transmission, IP transmission can significantly reduce the transmission cost. This feature enhances Iur transmission by introducing the following functions: BFD-based IP fault detection and built-in firewall on the RNC side. l If BFD-based IP fault detection is enabled, the BSC6900 triggers a port switchover, board switchover, or IP rerouting when detecting that the gateway or the peer entity becomes faulty. BFD can be classified into multi-hop BFD and single-hop BFD: In multi-hop BFD, the IP addresses of the local and peer ports must be on different network segments. In single-hop BFD, the IP addresses of the local and peer ports must be on the same network segment.
The built-in firewall on the RNC side safeguards IP Ethernet ports on interface boards and O&M ports against network attacks.
Procedure
l Activation Procedure The following takes the FG2c board as an example to describe the configuration operations. 1. 2. 3. 4. Run the BSC6900 MML command SET ETHPORT to set the attributes of an Ethernet port. Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet port. Run the BSC6900 MML command STR IPCHK. In this step, set Check type to SBFD. Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall function for an interface board. In this step, set Board type. to FG2c and ARP Learning Strict Switch to ON.
NOTE
5.
(Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS supports the built-in firewall function) by performing the following operations: Log in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux command iptables -A INPUT s restricted IP -i Ethernet adapter p transport protocol --dport restricted port j DROP. Here, restricted IP refers to the IP address that needs to be prohibited or allowed, and it can be a single IP address or a network segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to be prohibited. If p transport protocol and --dport restricted port are not specified, all ports are disabled. Run the BSC6900 MML command DSP ETHPORT to query the attributes of an Ethernet port. Run the BSC6900 MML command LST ETHIP to query the IP address of the Ethernet port. Run the BSC6900 MML command DSP IPCHK to query whether the Check state is UP. Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP Connectivity Check Failure is reported. Run the BSC6900 MML command LST IPGUARD to check whether the value of ARP Learning Strict Switch is ON. Built response messages to ARP requests and sent to interface boards. Run the BSC6900 MML command DSP ARP to query the ARP table of interface boards. If the information of interface boards in ARP table do not update, the ARP Learning Strict Switch is valid. If any invalid packet exists, run the BSC6900 MML command DSP INVALIDPKTINFO to query the detailed information. (Optional) Log in to the computer whose IP address is prohibited and check whether the prohibited services can be performed. Run the Dopra Linux command iptables
Verification Procedure 1. 2. 3. 4. 5. 6.
7. 8.
239-2
L. All the filtering rules on the OMU will be listed, and check whether new rules are added successfully. If port 80 is disabled, logging in to the BSC6900 LMT is prohibited. Check whether you can log in to the BSC6900 LMT on the PC whose port 80 is disabled. If port 22 is disabled, the OMU cannot be logged in to remotely. Check whether you can log in to the BSC6900 OMU through Putty on the PC whose port 22 is disabled. If port 21 is disabled, FTP services of the OMU cannot be used. Check whether you can connect to the FTP server of the BSC6900 OMU through an FTP client on the PC whose port 21 is disabled. l Deactivation Procedure 1. 2. 3. 4. 5. Run the BSC6900 MML command STP IPCHK to stop the BFD. Run the BSC6900 MML command SET IPGUARD. In this step, set Board type to FG2c and ARP Learning Strict Switch to OFF. Run the BSC6900 MML command RMV ETHIP to remove an IP address from the Ethernet port. Run the BSC6900 MML command SET ETHPORT. In this step, set Port type to FE. (Optional) Log in to the OMU through the LMT locally or through Putty remotely. Run the Dopra Linux command iptables -D INPUT s restricted IP -i Ethernet adapter p transport protocol --dport restricted port j DROP. Here, restricted IP is the IP address that needs to be prohibited or allowed, and it can be a single IP address or a network segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to be prohibited, and it is used together with the transport protocol. If p transport protocol and --dport restricted port are not specified, all ports are disabled. (Optional) Run the Dopra Linux command iptables L. All the filtering rules on the OMU will be listed, and check whether new rules are removed successfully.
6. ----End
Example
//Configuring the attributes of an Ethernet port and adding an IP address to the port SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0; ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.171.35.123", MASK="255.255.255.0"; //Activating BFD-based IP fault detection STR IPCHK: SRN=0, SN=14, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=0, MODE=CHECK_ON_PRIMARY_PORT, PEERIP="99.9.9.100"; //Activating the built-in firewall function on an RNC interface board SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=ON; //Activating the built-in firewall function for O&M //For example, only the IP addresses on the 10.141.148.0 network segment is allowed to access the LMT iptables -A INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport 80 -j DROP //Querying the attributes and IP address of an Ethernet port DSP ETHPORT: SRN=0, SN=14; LST ETHIP: SRN=0, SN=14, PN=0; //Verifying BFD-based IP fault detection DSP IPCHK: SRN=0, SN=14; //Verifying the built-in firewall function on the RNC
Issue 02 (2011-07-11)
239-3
LST IPGUARD: SRN=0, SN=14; DSP ARP: SRN=0, SN=14; DSP INVALIDPKTINFO: SRN=0, SN=14; //Deactivating BFD-based IP fault detection STP IPCHK: SRN=0, SN=14, CHKN=0; //Deactivating the built-in firewall function on the RNC SET IPGUARD: SRN=0, SN=14, BRDTYPE=FG2c, ARPLRNSTRICTSW=OFF; //Removing an IP address from an Ethernet port and modifying the attributes of the Ethernet port RMV ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0; SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=FE, PN=0; //Deactivating the built-in firewall function for O&M iptables -D INPUT -s ! 10.141.148.0/255.255.255.0 -i bond1 -p tcp --dport 80 -j DROP
239-4
Issue 02 (2011-07-11)
240 Configuring FP MUX for IP Transmission
240
Prerequisite
l l
Configuring FP MUX for IP Transmission
This section describes how to activate, verify, and deactivate the optional feature WRFD-050420 Configuring FP MUX for IP Transmission.
Dependencies on Hardware The FG2a/FG2c, GOUa/GOUc, and POUc support FP multiplexing. Dependencies on Other Features The feature WRFD-050402 IP Transmission Introduction on Iub Interface has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. The receive end of IP packets support FP mulptiplexing.
Context
The FP MUX feature encapsulates multiple packets with the same source IP address, destination IP address, and DiffServ Code Point (DSCP) into one UDP/IP packet. This reduces the overhead of packet headers and therefore improves the transmission efficiency. FP MUX is a Huawei proprietary protocol. Both RNC and NodeB must support this feature.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command ADD IPMUX to enable frame multiplexing on the Iub interface. In this step, set IP MUX Type to FPMUX.
Issue 02 (2011-07-11)
240-1
240 Configuring FP MUX for IP Transmission

NOTE
You do not need to configure the number of packets for multiplexing, the BSC6900 selects proper subframes for multiplexing based on the length of subframes. Subframes that meet the following conditions are multiplexed into packets: 1. The total sending duration of subframes is smaller than Maximum Delay Time. 2. The length of the subframe is smaller than Max subframe length. 3. The total length of subframes plus eight is smaller than or equal to Maximum Frame Length.
2. l
Run the NodeB MML command SET FPMUX to configure FP multiplexing on the Iub interface on the NodeB side. Run the BSC6900 MML command DSP IPMUX to check IP packet multiplexing conditions. Run the NodeB MML command LST FPMUX to query the FP multiplexing condition of an IP path. Run the BSC6900 MML command RMV IPMUX to disable the FP multiplexing function for the IP path. Run the NodeB MML command SET FPMUX to disable FP multiplexing on the NodeB side.
----End
Example
//Acitvating FP MUX for IP Transmission on the RNC side ADD IPMUX: MUXTYPE=FPMUX, ANI=1, PATHID=1, ISQOSPATH=NO, SUBFRAMELEN=352, MAXFRAMELEN=1031; //Acitvating FP MUX for IP Transmission on the NodeB side SET FPMUX: FPMUXSWITCH =ENABLE; //Verifying FP MUX for IP Transmission on the RNC side DSP IPMUX: IPMUXINDEX=1; //Verifying FP MUX for IP Transmission on the NodeB side LST FPMUX:; //Deacitvating FP MUX for IP Transmission on the RNC side RMV IPMUX: IPMUXINDEX=1; //Deacitvating FP MUX for IP Transmission on the NodeB side SET FPMUX: FPMUXSWITCH =DISABLE;
240-2
Issue 02 (2011-07-11)
241 Configuring Dynamic Bandwidth Control of Iub IP
241
Prerequisite
l l
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.
Dependencies on Hardware The FG2a, FG2c, GOUa and GOUc support this feature for BSC6900. Dependencies 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.
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). It is recommended that flow control algorithm for bandwidth dynamic adjustment do not to use.
Procedure
l Activating Procedure 1. 2. l 1. 2. Run the BSC6900 MML command ADD IPLOGICPORT. In this step, set Auto adjust bandwidth switch to ON. Run the BSC6900 MML command ACT IPPM to activate the IP PM. 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.
Issue 02 (2011-07-11)
241 Configuring Dynamic Bandwidth Control of Iub IP
3.
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 241-1.
Figure 241-1 Link performance monitoring
Deactivating Procedure 1. 2. Run the BSC6900 MML command MOD IPLOGICPORT. In this step, set Auto adjust bandwidth switch to OFF. Run the BSC6900 MML command DEA IPPM to deactivate the IP PM.
----End
Example
//Activating dynamic bandwidth control of Iub IP ADD IPLOGICPORT: SRN=0, SN=14, BT=FG2a, LPN=0, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=ON, MAXBW=100, MINBW=50, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF; ACT IPPM: ANI=0, PATHID=1, ISQOSPATH=NO, LOSTPKTDETECTSW=OFF; //Deactivating dynamic bandwidth control of Iub IP MOD IPLOGICPORT: SRN=0, SN=14, BT=FG2a, LPN=0, BWADJ=OFF, CIR=100; DEA IPPM: ANI=0, PATHID=1;
241-2
Issue 02 (2011-07-11)
242 Configuring Overbooking on IP Transmission
242
Prerequisite
l
Configuring Overbooking on IP Transmission
This section describes how to activate, verify, and deactivate the optional feature WRFD-050408 Overbooking on IP Transmission.
Dependencies on Hardware All IP interface boards of BSC6900 (PEUa, FG2a, FG2c, GOUa, GOUc, UOIa_IP, and UOIc_IP) support backpressure mechanism. In addition, FG2a, FG2c, GOUa, GOUc, UOIa_IP, and UOIc_IP support IP shaping.
Dependencies on Other Features The feature WRFD-050402 IP Transmission Introduction on Iub Interface must be configured before this feature is activated.
Context
The transmission rate of UMTS services varies during the transmission. For example, the rate of a speech service is 12.2 kbit/s when someone is speaking and is low when no one is speaking. Overbooking on IP Transmission helps save transmission resources on the Iub interface, reducing the CAPEX and OPEX of the operator on transmission resources. This feature consists of the following algorithms: l l l RLC retransmission rate-based downlink congestion control Fast backpressure on interface boards IP shaping
Procedure
l Activation Procedure Activating RLC retransmission rate-based downlink congestion control Run the BSC6900 MML command SET UCORRMALGOSWITCH to switch on flow control.
For R99 BE services, select DRA_R99_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. For HSDPA BE services, select DRA_HSDPA_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. Activating backpressure-based downlink congestion control 1. 2. Run the BSC6900 MML command ADD PORTFLOWCTRLPARA. In this step, set Port protocol type to IP and set other flow control parameters. Switch on flow control. (1) Run the BSC6900 MML command ADD PPPLNK. In this step, set Flow control switch to ON. (2) Run the BSC6900 MML command ADD MPGRP. In this step, set Flow control switch to ON. (3) Run the BSC6900 MML command ADD IPLOGICPORT. In this step, set Flow control switch to ON. Activating IP shaping 1. 2. l Run the BSC6900 MML command ADD IPLOGICPORT. In this step, set Flow control switch to ON(ON). Run the BSC6900 MML command ADD IPPATH to add a logical port. In this step, set Bearing type to IPLGCPORT.
Verification Procedure Take the FE/GE-based IP transmission on the Iub interface as an example to describe how to verify backpressure-based downlink flow control. 1. 2. 3. 4. 5. 6. 7. On the BSC6900 LMT, start downlink traffic and bandwidth tracing tasks on the Uu, Iub, and Iu interfaces. Register an R99 user UE1 in the HLR. Enable UE1 with streaming services and with both highest uplink rate and highest downlink rate of 384 Kbit/s. Register an HSDPA user UE2 in the HLR. Enable UE2 with background services and with highest uplink rate of 384 Kbit/s and highest downlink rate of 1450 Kbit/s. Run the BSC6900 MML command ADD TRMMAP to map R99 services to highpriority queue and HSDPA services to low-priority queue. All IP paths of the RNC are carried on a logical port. Enable the port flow control when adding the logical port. Enable UE1 and UE2 to stay in idle mode and camp on the test cell. The test cell must support HSDPA services. Use UE1 to perform PS streaming services, that is, use UE1 to download files from the FTP server. Expected result: The logical port is not congested and UE1 downloads data at the highest rate. 8. Use UE2 to perform PS BE services, that is, use UE2 to download files from the FTP server. Expected result: The logical port is congested and the backpressure function is triggered. The downloading rate of UE2 decreases and that of UE1 remains unchanged. This is because R99 services have a higher priority.
242-2
Issue 02 (2011-07-11)
Deactivation Procedure Deactivating RLC retransmission rate-based downlink congestion control Run the BSC6900 MML command SET UCORRMALGOSWITCH to switch off flow control. For R99 BE services, deselect DRA_R99_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. For HSDPA BE services, deselect DRA_HSDPA_DL_FLOW_CONTROL_SWITCH in Dynamic Resource Allocation Switch. Deactivating backpressure-based downlink congestion control 1. 2. 3. Run the BSC6900 MML command MOD PPPLNK. In this step, set Flow control switch to OFF. Run the BSC6900 MML command MOD MPGRP. In this step, set Flow control switch to OFF. Run the BSC6900 MML command MOD IPLOGICPORT. In this step, set Flow control switch to OFF. Run the BSC6900 MML command MOD IPPATH to modify a logical port. In this step, set Bearing type to NULL(NULL). Run the BSC6900 MML command MOD IPLOGICPORT. In this step, set Flow control switch to OFF(OFF). Run the BSC6900 MML command ADD IPPATH to add a logical port. In this step, set Bearing type to IPLGCPORT.
Deactivating IP shaping 1. 2. 3. ----End
Example
//Activating RLC retransmission rate-based downlink congestion control SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-1&DRA_R99_DL_FLOW_CONTROL_SWIT CH-1; //Activating backpressure-based downlink congestion control ADD PORTFLOWCTRLPARA: FCINDEX=10, PORTPROTYPE=IP; ADD PPPLNK: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=1, DS1=2, TSBITMAP=TS1-1, BORROWDEVIP=NO, LOCALIP="5.5.5.5",MASK="255.255.255.0", PEERIP="5.5.5.6", PPPMUX=Enable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON; ADD MPGRP: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=1, MPTYPE=MCPPP, BORROWDEVIP=No, LOCALIP="9.9.9.99", MASK="255.255.255.0", PEERIP="9.9.9.98", MHF=LONG, PPPMUX=Disable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V, ERRDETECTSW=OFF; ADD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPNTYPE=Leaf, LPN=0, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON; //Activating IP shaping ADD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPNTYPE=Leaf, LPN=0, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON; ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=BE, IPADDR="80.1.1.1", PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000, CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=0,
Issue 02 (2011-07-11)
242-3

VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Deactivating RLC retransmission rate-based downlink congestion control SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-0&DRA_R99_DL_FLOW_CONTROL_SWIT CH-0 //Deactivating backpressure-based downlink congestion control MOD PPPLNK: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=1, FLOWCTRLSWITCH=OFF; MOD MPGRP: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=1, FLOWCTRLSWITCH=OFF; MOD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPN=0, FLOWCTRLSWITCH=OFF; //Deactivating IP shaping MOD IPPATH: ANI=0, PATHID=1, ITFT=IUB, CARRYFLAG=NULL; MOD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPN=0, FLOWCTRLSWITCH=OFF;
242-4
Issue 02 (2011-07-11)
243 Configuring UDP MUX for Iu-CS Transmission
243
Prerequisite
l l
Configuring UDP MUX for Iu-CS Transmission
This section describes how to activate, verify, and deactivate the feature WRFD-050412 UDP MUX for Iu-CS Transmission.
Dependencies on Hardware This feature is supported only by the BSC6900 that is configured with the FG2a/GOUa/ FG2c/GOUc/POUc boards. Dependencies on Other Features The feature WRFD-050409 IP Transmission Introduction on Iu Interface has been configured before this feature is activated.
l l
License The license controlling this feature has been activated. Other Prerequisites The CS CN element (MGW) supports UDP MUX.
Context
After IP transmission is introduced to the Iu-CS interface, UP packets, especially short packets like CS packets, cannot be transmitted efficiently after being encapsulated at the RTP, UDP, and IP layers. This feature helps solve this problem by using a UDP subheader shorter than UDP to encapsulate multiple RTP packets into a UDP. This reduces resources used by packet headers and therefore improves the efficiency of Iu-CS transmission. This feature supports UDP MUX, regardless of whether compression of RTP headers is enabled. After this feature is enabled, transmission efficiency can be increased by 30% to 40%, depending on the number of RTP packets that are encapsulated into a UDP.
Procedure
l
Issue 02 (2011-07-11)
243 Configuring UDP MUX for Iu-CS Transmission

NOTE
Configure IP paths based on the network plan.
1.
Run the BSC6900 MML command ADD IPMUX or MOD IPMUX to enable the IuCS UDP MUX function. In this step, set IP MUX Type to UDPMUX, and set Max subframe length[byte], Maximum Frame Length[byte], and Maximum Delay Time[ms] to appropriate values based on the network plan. To enable the UDP MUX function for multiple links, run this command for each of the links. Run the BSC6900 MML command DSP IPMUX to query the application of UDP MUX for Iu Transmission. Check whether the feature has been activated based on the values of IPMUX Status, Number of MUX packets, and Number of MUX Subframes. Run the BSC6900 MML command RMV IPMUX to remove the IP MUX paths or run the BSC6900 MML command MOD IPMUX to set IP MUX Type to FPMUX.
----End
Example
//Activating UDP MUX for Iu-CS Transmission ADD IPMUX: MUXTYPE=UDPMUX, SUBFRAMELEN=352, MAXFRAMELEN=1031, FPTIMER=2; //Checking whether UDP MUX for Iu-CS Transmission has been activated for an IP MUX path of which the index is 1 DSP IPMUX: IPMUXINDEX=1; //Deactivating UDP MUX for Iu-CS Transmission MOD IPMUX: MUXTYPE=FPMUX;
243-2
Issue 02 (2011-07-11)
244 Configuring ATM Switching-Based Hub NodeB
244
Prerequisite
l l l
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.
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 PVC. Run the NodeB MML command RMV TREELNKPVC to remove the tree link PVC. Verification Procedure Deactivation Procedure
Example
l NodeB V200R013
//Activation procedure ADD TREELNKPVC: NO=1, JNRSCGRP=DISABLE, VST=VC_SWITCH, SRCSRN=0, SRCSN=7, SRCSBT=BASE_BOARD,
Issue 02 (2011-07-11)
244-1
244 Configuring ATM Switching-Based Hub NodeB
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; //Verification procedure LST TREELNKPVC:; //Deactivation procedure RMV TREELNKPVC: NO=1;
NodeB V100R013
//Activation procedure ADD TREELNKPVC: NO=1, VST=VC_SWITCH, SRCSRN=0, SRCSN=15, SRCSBT=BASE_BOARD, SRCPT=IMA, SRCPN=0, SRCVPI=7, SRCVCI=33, DSTSRN=0, DSTSN=12, DSTSBT=E1_COVERBOARD, DSTPT=IMA, DSTPN=1, DSTVPI=8, DSTVCI=33, RU=KBPS, ST=RTVBR, PCR=1000, SCR=800; //Verification procedure LST TREELNKPVC:; //Deactivation procedure RMV TREELNKPVC: NO=1;
244-2
Issue 02 (2011-07-11)
245 Configuring AAL2 Switching-Based Hub NodeB
245
Prerequisite
l l l
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.
Dependencies on Hardware DBS 3800 does not support this feature. Dependencies on Other Features WRFD-050105 ATM Switching-Based Hub NodeB License This feature is not under license control.
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(Switching Node). Run the NodeB MML command ADD AAL2ADJNODE to add an AAL2 adjacent node to the lower-level NodeB. Run the NodeB MML command DSP AAL2NODE to query the configuration of the AAL2 node. Run the NodeB MML command DSP AAL2ADJNODE to query the configuration of the AAL2 adjacent node. Run the NodeB MML command RMV AAL2ADJNODE to remove the AAL2 adjacent node.
Issue 02 (2011-07-11)
245 Configuring AAL2 Switching-Based Hub NodeB
2.
Run the NodeB MML command RMV AAL2NODE to remove an AAL2 node. In this step, set Node Type to HUB(Switching Node).
NOTE
There is a relation between the AAL2 adjacent node and the AAL2 node. Therefore, you need to remove the AAL2 adjacent nodes first and then remove the AAL2 node. Note that the AAL2 node can be removed only after all the AAL2 adjacent nodes are removed. Otherwise, the command execution fails.
----End
Example
//Activation procedure ADD AAL2NODE: NT=HUB, LN=1; ADD AAL2ADJNODE: ANI=1, ADDR="H'3912323232323232333333333333333333333333", LN=2; //Verification procedure DSP AAL2NODE:; DSP AAL2ADJNODE:; //Deactivation procedure RMV AAL2ADJNODE: ANI=1; RMV AAL2NODE: NT=HUB;
245-2
Issue 02 (2011-07-11)
246 Configuring IP Routing-Based Hub NodeB
246
Prerequisite
l l l
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.
Dependencies on Hardware Only 3900 series base stations support this feature. Dependencies on Other Features WRFD-050402 IP Transmission Introduction on Iub Interface License This feature is not under license control.
Context
This feature enables Huawei NodeBs to provide the transmission convergence function in IP mode, therefore increasing transmission efficiency and reducing transmission costs.
Procedure
l Activation Procedure 1. l On NodeBs locating on all leaf nodes and root nodes, run the NodeB MML command ADD IPRT to add an IP route from the NodeB to the BSC6900 or M2000. Run the NodeB MML command DSP IPRT to query the configuration of the newly added IP route. Run the NodeB MML command RMV IPRT to remove the IP route.
----End
Example
l
Issue 02 (2011-07-11)
NodeB V200R013
246 Configuring IP Routing-Based Hub NodeB
//Activation procedure 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"; //Verification procedure DSP IPRT: CN=0, SRN=0, SN=7; //Deactivation procedure 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";
NodeB V100R013
//Activation procedure ADD IPRT: SRN=0, SN=12, SBT=BASE_BOARD, DSTIP="11.11.11.11", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.10.10.10"; //Verification procedure DSP IPRT:; //Deactivation procedure RMV IPRT: SRN=0, SN=12, SBT=BASE_BOARD, DSTIP="11.11.11.11", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.10.10.10";
246-2
Issue 02 (2011-07-11)
247 Configuring Ethernet OAM
247
Prerequisite
l l
Configuring Ethernet OAM
This section describes how to activate, verify, and deactivate the optional feature WRFD-050425 Ethernet OAM.
Dependency on RNC Hardware Only BSC6900 supports this feature. Dependency on NodeB Hardware BTS3812E/AE, DBS3800,3900 series NodeB can support both IEEE 802.3ah and IEEE 802.1ag draft 8;
Dependencies 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 This feature is not under license control.
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 in Figure 247-1. Figure 247-1 PPP Ethernet OAM network
2.
E2E Ethernet OAM The E2E Ethernet OAM complies with IEEE 802.1ag draft 7 or IEEE 802.1ag draft 8. It is implemented based on services, maintenance domains, and E2E detection.
Procedure
l Activating the Ethernet OAM 3AH Function 1. Run the BSC6900 MML command ACT EFMAH to activate the Ethernet OAM 3AH function.
NOTE
The OAM 3AH function on peer equipment must be activated.
Activating the Ethernet OAM 1AG Function 1. Run the BSC6900 MML command ADD CFMMD to add the Ethernet OAM maintenance domain (MD). The Ethernet OAM MD consists of bridges and maintenance equipment. Each MD is associated with a maintenance level. There are eight maintenance levels, that is level 0 to level 7. 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
2.
3.
l The MEPID of the RemoteMep configured on the peer equipment must be consistent with the MEPID of the LocalMep configured on the local equipment. l MD, MA or MEP must be configured on the peer equipment when the MD, MA or MEP has be added on BSC6900.
4.
Run the BSC6900 MML command ACT CFMCCMTST to activate the Ethernet OAM unidirectional connectivity detection between the local MEP and the remote MEP. Activate the Ethernet OAM 3AH function. The Alarm-21371 ETHOAM 3AH Detection Failure alarm is reported when Ethernet OAM detection fails. The
Verifying the Ethernet OAM 3AH Function 1.
247-2
ALM-21345 Ethernet Link Fault alarm is report when Ethernet OAM detection is enable, because link on local end and peer end fails. 2. 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. OAM 1AG function on the peer equipment must be activated, and the transmission is functional that the local MEP succeeds to receive the CCM packets from the peer MEP, the running of the PING MAC and TRC MAC succeeds. 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 1AG Function 1.
2.
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, SN=18, PN=0; ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=RemoteMep, MEPID=11, SN=18; ACT CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1; //Verifying the Ethernet OAM 1AG function PING MAC: SRN=0, SN=18, MAIDX=0, SRCMEPID=1, DESTMEPID=11; TRC MAC: SRN=0, SN=18, MAIDX=0, SRCMEPID=1, DESTMEPID=11; //Deactivating the Ethernet OAM 3AG function DEA EFMAH: SRN=0, SN=18, PN=0; //Deactivating the Ethernet OAM 1AG function DEA CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1; RMV CFMMD: SRN=0, SN=18, MDIDX=0; RMV CFMMA: SRN=0, SN=18, MAIDX=0; RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=11; RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=1;
Issue 02 (2011-07-11)
247-3
248 Configuring Clock Synchronization on Ethernet in NodeB
248
Prerequisite
l l l
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.
Dependencies on Hardware Huawei clock server should support this feature. Dependencies on Other Features WRFD-050402 IP Transmission Introduction on Iub Interface License The license controlling this feature has been 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 NodeB V200R013 Activation Procedure 1. 2. Run the NodeB MML command ADD IPCLKLINK to add an IP clock link. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to IPCLK(IP Clock). Verification Procedure 1. Run the NodeB MML command DSP IPCLKLINK to query the running status of all IP clock links.
Issue 02 (2011-07-11)
Expected result: The value of Link Available State is Available. 2. Run the NodeB MML command DSP CLKSTAT to query the status of the system clock. Expected result: The value of Current Clock Source State is Normal. Deactivation Procedure 1. 2. l Run the NodeB MML command RMV IPCLKLINK to remove a specified IP clock link. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to FREE(Free).
NodeB V100R013 Activation Procedure 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 working mode of the reference clock source. Set System Clock Working Mode to MANUAL(Manual). Set Clock Source Type to IPCLK(IP clock source). Verification Procedure 1. Run the NodeB MML command DSP IPCLKLNK to query the running status of all IP clock links. Expected result: The value of IP Clock Link Status is Normal. 2. Run the NodeB MML command DSP CLKSTAT to query the status of the system clock. Expected result: The value of Current Clock Source State is Normal. Deactivation Procedure 1. 2. Run the NodeB MML command RMV IPCLKLNK to remove a specified IP clock link. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set System Clock Working Mode to FREE(Free).
----End
Example
l NodeB V200R013
//Activation procedure ADD IPCLKLINK: ICPT=HW_DEFINED, SN=7, CIP="82.0.1.107", SIP="82.0.1.128"; SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SYNMODE=OFF; //Verification procedure DSP IPCLKLINK:; DSP CLKSTAT: SN=7; //Deactivation procedure RMV IPCLKLINK:; SET CLKMODE: MODE=FREE;
NodeB V100R013
//Activation procedure ADD IPCLKLNK: SRN=0, SN=12, CIP="11.11.11.11", SIP="10.10.12.12",
248-2
Issue 02 (2011-07-11)

ICPT=HW_DEFINED; SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, IPMODE=AUTO; //Verification procedure DSP IPCLKLNK: SN=12; DSP CLKSTAT:; //Deactivation procedure RMV IPCLKLNK: SRN=0, SN=12; SET CLKMODE: MODE=FREE;
Issue 02 (2011-07-11)
248-3
249 Configuring Synchronous Ethernet
249
Prerequisite
l l l l
Configuring Synchronous Ethernet
This section describes how to activate, verify, and deactivate the optional feature WRFD-050502 Synchronous Ethernet.
Dependencies on Hardware Only the BSC6900 supports this feature. Only the 3900 series base stations support this feature. Dependencies on Other Features WRFD-050402 IP Transmission Introduction on Iub Interface License The license controlling this feature has been activated. Other Prerequisites The synchronous Ethernet technology requires that all the equipments on the clock relay path must support the synchronous Ethernet.
Context
This feature provides the solution for clock synchronization in all-IP networking scenarios. It enables the clock extraction and recovery in the physical layer of the Ethernet.
Procedure
l Activation Procedure 1. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to SYNCETH(SyncEth Clock). 2. l Run the NodeB MML command ADD SYNCETH to add a synchronous-Ethernet clock link. Run the NodeB MML command DSP CLKSTAT to query the status of the current clock source.
Issue 02 (2011-07-11)
249 Configuring Synchronous Ethernet
Expected result: The value of Current Clock Source State is Normal. l Deactivation Procedure 1. 2. ----End Run the NodeB MML command RMV SYNCETH to remove a synchronousEthernet clock link. Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. In this step, set Clock Working Mode to FREE(Free).
Example
//Activation procedure SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH; ADD SYNCETH: SN=7, PN=0; //Verification procedure DSP CLKSTAT: SN=7:; //Deactivation procedure RMV SYNCETH:; SET CLKMODE: MODE=FREE;
249-2
Issue 02 (2011-07-11)
250 Configuring RNC Node Redundancy
250
Prerequisite
l l l l l
Configuring RNC Node Redundancy
This section describes how to activate, verify, and deactivate the optional feature WRFD-040202 RNC Node Redundancy.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated. The Iur, Iu-CS, Iub and Iu-PS interfaces have been configured. For details, see Configuring the Interfaces. This feature has been available since RAN11.0 and is applicable only to the BSC6900.
Context
This feature improves the reliability and robustness of RAN and shortens the service interruption due to single-point failure in the RNC. In this way, the service quality is improved. With this feature, a NodeB can be connected to two RNCs and heartbeat detection is performed on the Iur interface between the two RNCs. When the primary RNC is faulty, the NodeB can be fast switched to the secondary RNC for service provisioning. The primary RNC and the secondary RNC form an RNC pool, as shown in Figure 250-1 and Figure 250-2.
Issue 02 (2011-07-11)
250-1
Figure 250-1 Network topology not configured with RNC pool
Figure 250-2 Network topology configured with RNC pool
NOTE
l When the serving RNC is faulty, the maximum service capability (such as CS Erlang and PS throughput) decreases from the combined capability of two RNCs to the capability of one RNC. As a result, the processing specifications of the network decrease. l To activate this feature, data configurations related to this feature are required on the RNC and the NodeB. The CN and M2000 do not require data configurations specific to this feature. You can check the homing state of the NodeB on the M2000.
Procedure
250-2
Issue 02 (2011-07-11)

NOTE
This document uses RNC202, RNC203, and NodeB1 as examples to describe the procedures. Assume that RNC202 and RNC203 are initially configured as the primary homing and secondary homing RNC of NodeB1 respectively.
1.
Data configurations on the primary homing RNC (RNC202) (1) Run the BSC6900 MML command ADD URNCPOOL to add an RNC pool. In this step, set the parameters such as RncPool Index, RncPool Name, Supporting Auto-Rehoming Switch and so on.
CAUTION
If the license is activated , the primary homing RNC is physically broken down and Supporting Auto-Rehoming Switch is set to OFF, the feature WRFD-040300 License Control for Urgency will be activated. WRFD-040300 License Control for Urgency can be enabled only fifteen times for each R version for this kind of reason. (2) Run the BSC6900 MML command ADD URNCPOOLMEMBER to add the primary homing RNC (RNC203) to the RNC pool. (3) Run the BSC6900 MML command ACT URNCPOOL to activate the RNC node redundancy feature. (4) Add a NodeB (NodeB1) of which the primary homing RNC is RNC202: Run the BSC6900 MML command ADD UNODEB to add a NodeB of which the primary homing RNC is RNC202. (5) Run the BSC6900 MML command ADD UCELLQUICKSETUP to add the cell to the primary homing RNC and specify the peer cell ID under the secondary homing RNC. (6) Run the BSC6900 MML command SET UPOOLPRIMHOSTPOLICY to set the rehoming strategy of the NodeB. 2. Data configurations on the secondary homing RNC (RNC203) (1) Run the BSC6900 MML command ADD URNCPOOL to add an RNC pool. In this step, set the parameters such as RncPool Index, RncPool Name, Supporting Auto-Rehoming Switch and so on.
CAUTION
If the license is activated , the secondary homing RNC is physically broken down and Supporting Auto-Rehoming Switch is set to OFF, and the feature WRFD-040300 License Control for Urgency will be activated. WRFD-040300 License Control for Urgency can be enabled only fifteen times for each R version for this kind of reason. (2) Run the BSC6900 MML command ADD URNCPOOLMEMBER to add the primary homing RNC (RNC202) to the RNC pool. (3) Run the BSC6900 MML command ACT URNCPOOL to activate the RNC node redundancy feature.
(4) Add a NodeB (NodeB1) of which the secondary homing RNC is RNC203: Run the BSC6900 MML command ADD UNODEB to add a NodeB of which the secondary homing RNC is RNC203. (5) Run the BSC6900 MML command ADD UCELLQUICKSETUP to add the cell to the secondary homing RNC and specify the peer cell ID under the primary homing RNC. 3. Data configurations on the NodeB (NodeB1) side (1) Configure information about the primary homing RNC. a. b. a. b. l 1. Run the NodeB MML command ADD IUBCP to add an NCP link. Run the NodeB MML command ADD IUBCP to add a CCP link. Run the NodeB MML command ADD IUBCP to add an NCP link. Run the NodeB MML command ADD IUBCP to add a CCP link.
(2) Configure information about the secondary homing RNC.
Verification Procedure Method 1: Verifying data configurations (1) Run the BSC6900 MML command DSP UCELL on the RNC202 LMT. The query result shows that cell 1 is functional. Run the BSC6900 MML command DSP UCELL on the RNC203 LMT. The query result shows that cell 2 is unavailable due to no control rights. (2) Perform an emulation test of the primary RNC fault. Run the BSC6900 MML command RST UIU on RNC202 to make RNC202 become faulty. If the BSC6900 recovers too fast after the BSC6900 MML command RST UIU is executed, you can remove the cable on the Iu-CS/Iu-PS interface instead. (3) After RNC203 detects that RNC202 is faulty through the Iur interface, RNC203 takes over the NodeB and initiates cell2 reestablishment. (4) (Optional) When the connection between the NodeB and the primary homing RNC is disconnected, the secondary homing RNC cannot obtain the NodeB control rights automatically. To solve this problem, run the BSC6900 MML command FOC UHOSTNODEB on the RNC203 LMT to manually switch over the NodeB control rights to the secondary homing RNC.
CAUTION
Switching over NodeB control rights manually disrupts the ongoing services when the connection between the NodeB and the primary homing RNC is normal. (5) On both the RNC203 LMT and the RNC202 LMT, run the BSC6900 MML command DSP UCELL. If the query result on the RNC203 LMT shows that cell 2 is operational and the query result on the RNC202 LMT shows that cell 1 is unavailable due to no control rights, this feature has been activated. Otherwise, this feature is not activated. 2.
250-4
Method 2: Verifying services

(1) Check whether the heartbeat between RNC202 and RNC203 is normal, as shown in Figure 250-3. Figure 250-3 Normal heartbeat between RNC202 and RNC203
(2) Check that the cell under RNC202 is available, and then use the UE to establish a CS AMR service, as shown in Figure 250-4 and Figure 250-5. Figure 250-4 NodeB control rights obtained by RNC202
Figure 250-5 CS AMR service set up successfully
(3) Power off RNC202 when RNC203 works properly. RNC203 then takes over the NodeB control rights. (4) When RNC202 restores normal services, it takes over the NodeB control rights again according to the rehoming strategy, and RNC203 releases the NodeB control rights. 3. Method 3: Verifying this feature on the M2000 (1) Create the RNCs and NodeB on the RNC POOL monitor of the M2000. When creating a NodeB, the M2000 checks the homing state of the NodeB. If the RNC
is the secondary homing RNC of the NodeB, the NodeB cannot be created under that RNC. (2) When the M2000 starts, it starts NE status subscribing. When the homing state of the NodeB changes, the RNC reports the NodeB homing state to the M2000. The M2000 then updates the network topology displayed in the RNC POOL monitor. l Deactivation Procedure 1. ----End On RNC202 and RNC203, run the BSC6900 MML command DEA URNCPOOL to deactivate the feature.
Example
/*Activation procedure*/ /*Data configuration script on the primary homing RNC side*/ /*Configuring an RNC pool*/ ADD URNCPOOL: RncPoolIndex=0, RncPoolName="redundancy_RNCPOOL"; ADD URNCPOOLMEMBER: RncPoolIndex=0, NrncId=203; ACT URNCPOOL: RncPoolIndex=0; //Adding a dual-homing NodeBADD UNODEB: NodeBName="Redundancy_NODEB500", NodeBId=500, SRN=0, SN=0, SSN=1, TnlBearerType=IP_TRANS,IPTRANSAPARTIND=NOT_SUPPORT, HostType=PRIMHOST, PeerRncId=203, PeerNodebId=500, SharingType=RANSHARING; //Setting cell parameters ADD UCELLQUICKSETUP: CellId=1, CellName="Redundancy_NODEB500_00", PeerIsValid=VALID, PeerCellId=2, CnOpGrpIndex=0, BandInd=Band1, UARFCNDownlink=10668, PScrambCode=500, TCell=CHIP0, LAC=H0046, SAC=H0000, CfgRacInd=REQUIRE, RAC=H00, SpgId=1, URANUM=D1, URA1=0, NodeBName="Redundancy_NODEB500", LoCell=500, SupBmc=FALSE; /*Data configuration script on the secondary homing RNC side*/ /*Configuring an RNC pool*/ ADD URNCPOOL: RncPoolIndex=0, RncPoolName="redundancy_RNCPOOL"; ADD URNCPOOLMEMBER: RncPoolIndex=0, NrncId=202; ACT URNCPOOL: RncPoolIndex=0; //Adding a dual-homing NodeB ADD UNODEB: NodeBName="Redundancy_NODEB500", NodeBId=500, SRN=0, SN=0, SSN=1, TnlBearerType=IP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT, HostType=SECHOST, PeerRncId=202, PeerNodebId=500, SharingType=RANSHARING; //Setting cell parameters ADD UCELLQUICKSETUP: CellId=2, CellName="Redundancy_NODEB500_00", PeerIsValid=VALID, PeerCellId=1, CnOpGrpIndex=0, BandInd=Band1, UARFCNDownlink=10668, PScrambCode=500, TCell=CHIP0, LAC=H0046, SAC=H0000, CfgRacInd=REQUIRE, RAC=H00, SpgId=1, URANUM=D1, URA1=0, NodeBName="Redundancy_NODEB500", LoCell=500, SupBmc=FALSE; /*Data configuration script on the NodeB side*/ /*Configuring information about the primary homing RNC on the NodeB*/ /*Configuring NCP and CCP*/ ADD IUBCP: CPPT=NCP, BEAR=IPV4; ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=1; /*Configuring information about the secondary homing RNC on the NodeB*/ /*Configuring NCP and CCP*/
250-6
Issue 02 (2011-07-11)
ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=2, BELONG=SLAVE; ADD IUBCP: CPPT=CCP, BEAR=IPV4, LN=3, BELONG=SLAVE; /*Verifying RNC Node Redundancy*///RNC202 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;
Issue 02 (2011-07-11)
250-7
251 Configuring RRU Redundancy
251
Prerequisite
l l l License
Configuring RRU Redundancy
This section describes how to activate, verify, and deactivate the optional feature WRFD-040203 RRU Redundancy.
Context
RRU redundancy can improve the reliability and robustness of the RAN and shorten the duration of service disruption caused by an RRU failure, improving service quality.
Procedure
l Activation Procedure 1. If a cell is configured as a MIMO cell or a 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(TX diversity capability is on to off) or TX_DIVERSITY_OFF_TO_ON(TX diversity capability is off to on). Both the options can be selected. Run the NodeB MML command ADD LOCELL to ensure the local cell uses two power amplifiers. Run the BSC6900 MML command LST UCELLALGOSWITCH to check that Cell Capability Auto Handle Switch is set to TX diversity capability is on to off::ON or TX diversity capability is off to on::ON. Run the NodeB MML command LST LOCELL to query whether the local cell is configured with two power amplifiers.
2. l
2.
Issue 02 (2011-07-11)
251 Configuring RRU Redundancy
Deactivation Procedure This feature need not be deactivated.
----End
Example
//Activation procedure //When a cell is configured as a MIMO and transmit diversity cell, do as follows: ADD UCELLALGOSWITCH: CellId=1, NBMUlCacAlgoSelSwitch=ALGORITHM_SECOND, NBMDlCacAlgoSelSwitch=ALGORITHM_SECOND, CellCapacityAutoHandleSwitch=TX_DIVERSITY_ON_TO_OFF-1&TX_DIVERSITY_OFF_TO _ON-1; //Or MOD UCELLALGOSWITCH: 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 LOCELL: LOCELL=0, STN=0, SECN=0, SECT=REMOTE_SECTOR, RADIUS=10000, HORAD=150, TTW=TRUE, SRN1=60, SRN2=61, SN2=0, ULFREQ=9610, DLFREQ=10560, MXPWR=430, HISPM=TRUE, SPR=250, RMTCM=FALSE, VAM=FALSE;, //Verification procedure //Querying the cell algorithm switch LST UCELLALGOSWITCH: CellId=1; //Checking whether the local cell is configured with two power amplifiers LST LOCELL: MODE=LOCALCELL, LOCELL=10;
251-2
Issue 02 (2011-07-11)
252 Configuring Transmit Diversity
252
Prerequisite
l l l License
Configuring Transmit Diversity
This section describes how to activate, verify, and deactivate the optional feature WRFD-010203 Transmit Diversity. Transmit diversity enables the NodeB to provide twice the number of RF DL channels compared with no transmit diversity.
Context
l l The feature supports STTD, TSTD, and CLD1 to effectively improve the reception performance of the UE. The transmit diversity feature improves terminal performance in special circumstances. Especially when multipath fading is not obvious and the UE is not moving fast, capacity and coverage can be significantly improved. The investment can be reduced while the same QoS is guaranteed. In this way, operators can reduce the CAPEX and the OPEX.
Procedure
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.
252 Configuring Transmit Diversity
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 DSP LOCELL to query the status of a specified local cell. Expected result: The value of Cell Transmit Diversity Status is Enabled.
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=60, ANT1N=R0A, ANT2SRN=61, ANT2N=R0A; ADD LOCELL: LOCELL=1, STN=0, SECN=1, SECT=REMOTE_SECTOR, TTW=TRUE, SRN1=60, SRN2=61, ULFREQ=9700, DLFREQ=10650, MXPWR=430, HISPM=FALSE, RMTCM=FALSE, VAM=FALSE; //Verification procedure DSP LOCELL: LOCELL=1;
252-2
Issue 02 (2011-07-11)
253 Configuring 4-Antenna Receive Diversity
253
Prerequisite
l l l
Configuring 4-Antenna Receive Diversity
This section describes how to activate, verify, and deactivate the optional feature WRFD-010209 4-Antenna Receive Diversity.
Context
l Compared with 2-Antenna Receive Diversity, 4-Antenna Receive Diversity provides the NodeB with twice the number of RF UL channels. In this way, a bigger UL coverage gain can be obtained. 4-antenna Receive Diversity improves the receiver sensitivity and the uplink coverage, so that the CAPEX can be reduced.
Procedure
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.
Issue 02 (2011-07-11)
253 Configuring 4-Antenna Receive Diversity
----End
Example
l NodeB V200R013
//Activation procedure ADD SEC: STN=0, SECN=0, SECT=LOCAL_SECTOR, ANTM=4, ANT1CN=0, ANT1SRN=4, ANT1N=N0A, ANT2CN=0, ANT2SRN=4, ANT2N=N0B, ANT3CN=0, ANT3SRN=4, ANT3N=N1A, ANT4CN=0, ANT4SRN=4, ANT4N=N1B; ADD ULGROUP: ULGROUPN=0, DEMMODE=DEM_4_CHAN, SNE1=0; //Verification procedure LST SEC: STN=0, SECN=0;
NodeB V100R013
//Activation procedure ADD SEC: STN=0, SECN=0, SECT=LOCAL_SECTOR, ANTM=4, ANT1SRN=2, ANT1N=N0A, ANT2SRN=2, ANT2N=N0B, ANT3SRN=2, ANT3N=N1A, ANT4SRN=2, ANT4N=N1B; ADD ULGROUP: ULGROUPN=0, DEMMODE=DEM_4_CHAN, SNE1=0; //Verification procedure LST SEC: STN=0, SECN=0;
253-2
Issue 02 (2011-07-11)
254 Configuring Extended Cell Coverage up to 200km
254
Prerequisite
l
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.
Dependencies on Hardware In the case of the NodeB 3900 series base stations, the WBBPb board or later version 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
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 NodeB MML command ADD REMOTECELLGRP. In this step, set Remote Cell Group No and Remote Cell Group Name.
4.
Issue 02 (2011-07-11)
In case of setting the remote cell to save boards, carry out Step 6. Otherwise, do not carry out Step 6. 5. 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. Optional: Run BSC6900 MML command MOD UPRACH, set sub channel of every cell, select sub channel from RACH Sub Channel No..
NOTE
6.
l Only 3 sub channels can be set for every cell, and no repeated sub channel exists. The 3 sub channels need to be fixed as follows: l sub-channel 0, sub-channel 1 and sub-channel 2 l sub-channel 4, sub-channel 5 and sub-channel 6 l sub-channel 8, sub-channel 9 and sub-channel 10 l When adding logical cell on BSC6900, the parameter Time Offset needs to be set to CHIP0, CHIP256 or CHIP512.
Verification Procedure 1. 2. 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.
----End
Example
//Activation procedure //Configuration on the BSC6900 side ADD UAICH: CELLID=1; ADD UPRACHBASIC: CellId=1, PhyChId=4, PreambleSignatures=SIGNATURE0-1, RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1, Constantvalue=-23, PreambleRetransMax=20, PowerRampStep=2, CTFCSize=BIT2; ADD UCELLSETUP:CELLID=1,CELLNAME="Cell1",MaxTxPower=430,BANDIND=BAND1,PeerIsV alid=VALID, PeerCellId=100, CnOpGrpIndex=0, UARFCNUplinkInd=TRUE,UARFCNUPLINK=9612, UARFCNDOWNLINK=10562, TCELL=CHIP256, NINSYNCIND=5, NOUTSYNCIND=50, TRLFAILURE=50, PSCRAMBCODE=2, TXDIVERSITYIND=TRUE, SpgId = 8,NODEBNAME="NodeB6", LOCELL=0, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00,CLTAModeInd=TRUE, STTDSUPIND = STTD_NOT_SUPPORTED, CP1SUPIND = CP1_NOT_SUPPORTED, DPCHDIVMODFOROTHER = NONE, DIVMODFORDCHSDPA = NONE; ADD UPCPICH: CELLID=1, PHYCHID=2, PCPICHPOWER=330, MAXPCPICHPOWER=346, MINPCPICHPOWER=313; //Configuration on the NodeB side ADD REMOTECELLGRP: REMOTECELLGRPINDEX=1, REMOTECELLGRPNAME="test"; ADD LOCELL: LOCELL=1, STN=1, SECN=1, SECT=LOCAL_SECTOR, CN1=0, SRN1=4, SN1=0, ULFREQ=9700, DLFREQ=10600, MXPWR=430, HISPM=FALSE, RMTCM=TRUE, RMTCGRPID=1, VAM=FALSE; Configuration on the BSC6900 side MOD UPRACH: CellId=1, PhyChId=0, RACHSubChNo=SUBCHANEL0-1&SUBCHANEL1-1&SUBCHANEL2-1;
254-2
Issue 02 (2011-07-11)
//Verification procedure LST REMOTECELLGRP: REMOTECELLGRPINDEX=1; LST LOCELL: MODE=LOCALCELL, LOCELL=1;
Issue 02 (2011-07-11)
254-3
255 Configuring High Speed Access
255
Prerequisite
l l l
Configuring High Speed Access
This section describes how to activate, verify, and deactivate the optional feature WRFD-010206 High Speed Access.
Dependencies 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. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control.
Context
The time-selective fading caused by the Doppler effect of a fast-moving UE increases the BER and affects the signals received by the NodeB. The high speed access feature provides the automatic frequency control (AFC) function for the uplink, reducing the Doppler effect and offering reliable services for the UE in high-speed movement.
NOTE
l The local sectors, remote sectors and distributed sectors support the high speed access feature. l When the HULP, HBBI, HBBU, or WBBPa is configured to support the high speed access feature, the capability for the board to carry access channels decreases. Each board can support the access channels of only one cell. In addition, the board in a common four-channel demodulation mode does not support high speed access. l When the WBBPb, WBBPd, EBBI, EBOI, EULP, EULPd, EBBC, or EBBCd is configured to support the high speed access feature, the capability of the board does not decrease. The board supports high speed access in any demodulation mode.
Issue 02 (2011-07-11)
255-1
255 Configuring High Speed Access
CAUTION
To enable the high speed access feature in the cells carrying services, deactivate these cells, modify these cells, and then activate these cells. This process disrupts the ongoing services.
Procedure
l Activation Procedure 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;
255-2
Issue 02 (2011-07-11)
256 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell
Demodulation of Signals from Multiple RRUs in One Cell

This section describes how to activate, verify, and deactivate the optional feature WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell.
256
Configuring Independent
Prerequisite
l Dependencies on Hardware DBS3900 series base stations only The WBBPb or WBBPd board needs to be configured. l Dependencies on Other Features This feature conflicts with the features WRFD-010203 Transmit Diversity, WRFD-010209 4-Antenna Receive Diversity, WRFD-010684 2x2 MIMO, and WRFD-021308 Extended Cell Coverage up to 200km. l License The license controlling this feature has been activated.
Context
In multi-RRU cell scenarios, this feature can reduce handovers between cells and increase cell capacity and cell throughput.
NOTE
l This feature cannot be used if a base station is configured with the feature transmit diversity, 4-Antenna Receive Diversity or MIMO. l This feature applies to high-speed moving scenarios such as highways, railways, and F1 raceways.
Procedure
l Activation Procedure 1. Run the NodeB MML command ADD SEC to add a sector. Set Sector Type to MULTIRRU_SECTOR(MULTIRRU_SECTOR).
256 Configuring Independent Demodulation of Signals from Multiple RRUs in One Cell
Set Diversity Mode to COMMON_MODE(Common Mode). 2. l Run the NodeB MML command ADD LOCELL to add a local cell. Set Sector Type to MULTIRRU_SECTOR(MULTIRRU_SECTOR). Verification Procedure 1. Run the NodeB MML command LST SEC to query configured sectors. Expected result: The value of Sector Type is MULTIRRU_SECTOR (MULTIRRU_SECTOR). Run the NodeB MML command DSP LOCELL to query the configuration of a local cell. Expected result: The value of Local Cell Status is Local Cell Available. Run the NodeB MML command RMV LOCELL to remove a local cell. Run the NodeB MML command RMV SEC to remove a specified sector.
2.
----End
Example
//Activation procedure ADD SEC: STN=0, SECN=0, SECT=MULTIRRU_SECTOR, RRUCOUNT=2, RRU1SRN=60, RRU2SRN=61; ADD LOCELL: LOCELL=0, STN=0, SECN=0, SECT=MULTIRRU_SECTOR, RRUMODE=SYNC, ULFREQ=9650, DLFREQ=10600, MXPWR=430, HISPM=FALSE; //Verification procedure LST SEC: STN=0, SECN=0; DSP LOCELL: LOCELL=0; //Deactivation procedure RMV LOCELL: LOCELL=0; RMV SEC: STN=0, SECN=0;
256-2
Issue 02 (2011-07-11)
257 Configuring PDCP Header Compression (RFC2507)
257
Prerequisite
l l l
Configuring PDCP Header Compression (RFC2507)
This section describes how to activate, verify, and deactivate the optional feature WRFD-011500 PDCP Header Compression (RFC2507).
Dependencies on Hardware The UE supports this feature. Dependencies on Other Features This feature does not depend on other features. License The license controlling this feature has been activated.
Context
This feature complies with the header compression function of data packet as defined in RFC 2507. It enables the deletion of redundant information such as TCP/IP header. The system compresses the redundant protocol header before the data is transmitted on a link. In addition, the system can decompress the received data. This feature can decrease the throughput on the Uu interface and improve the efficiency of radio links.
Procedure
l Activation Procedure 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.
Issue 02 (2011-07-11)
257 Configuring PDCP Header Compression (RFC2507)
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. l 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;
257-2
Issue 02 (2011-07-11)
258 Configuring HCS (Hierarchical Cell Structure)
258
Prerequisite
l l l
Configuring HCS (Hierarchical Cell Structure)
This section describes how to activate, verify, and deactivate the optional feature WRFD-021200 HCS (Hierarchical Cell Structure).
Context
Based on speed estimation, the BSC6900 hands over fast-moving UEs to low-priority cells to reduce the number of handovers, and hands over slow-moving UEs to high-priority cells to increase network capacity.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, set HoSwitch to the following parameter value. HO_ALGO_HCS_SPEED_EST_SWITCH HO_INTRA_FREQ_SOFT_HO_SWITCH HO_INTER_FREQ_HARD_HO_SWITCH HO_INTER_RAT_PS_OUT_SWITCH HO_INTER_RAT_CS_OUT_SWITCH 2. Run the BSC6900 MML command ADD UCELLHCS. In this step, set Use of HCS to USED.
Issue 02 (2011-07-11)
3.
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 parameters. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an interfrequency neighboring cell and set the HCS parameters. Run the BSC6900 MML command ADD U2GNCELL to add an inter-RAT GSM neighboring cell and set the HCS parameters.
4. 5. l
For the cells whose HCS parameters have been set, run the BSC6900 MML command ADD UCELLHCSHO. In this step, set SpdEstSwitch to ON. Run the BSC6900 MML command SET UHCSHO to set the RNC-level HCS parameters according to network plan. If the moving speed of a UE is higher than the fast-moving handover threshold (the number of 1D events reported by the UE in the specified period reaches the preset number), an inter-frequency or inter-RAT HCS handover is triggered. If the moving speed of a UE is lower than the slow-moving handover threshold (the number of 1D events reported by the UE in the specified period is smaller than the slow-moving handover threshold), slow-moving HCS handover measurement is triggered, and a slow-moving inter-frequency or inter-RAT HCS handover is performed. If a measurement-based inter-frequency or inter-RAT handover is triggered, check whether compressed mode is started by using a RRC_PH_CH_RECFG message on the Uu interface on the BSC6900 LMT. If compressed mode is started, this feature is activated. If an inter-frequency blind handover is triggered, check whether the handover is triggered by using a RRC_PH_CH_RECFG message on the Uu interface on the BSC6900 LMT. If the handover is triggered by using the message, this feature is activated. If an inter-RAT blind handover is triggered, check whether 3G-to-2G handovers are performed on the Uu and Iu interfaces on the BSC6900 LMT. If 3G-to-2G handovers are performed, this feature is activated. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect HO_ALGO_HCS_SPEED_EST_SWITCH from the HoSwitch parameter. Run the BSC6900 MML command MOD UCELLHCS. In this step, set Use of HCS to NOT_USED. Run the BSC6900 MML command MOD UCELLHCSHO. In this step, set SpdEstSwitch to OFF.
2.
3.
4.
5.
2. 3. ----End
Example
/*Activating HCS (Hierarchical Cell Structure).*/ //Set HandOver Switch SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-1&HO_INTRA_FREQ_SOFT_HO_SWITCH-1&HO _INTER_FREQ_HARD_HO_SWITCH-1&HO_INTER_RAT_PS_OUT_SWITCH-1&HO_INTER_RAT_CS _OUT_SWITCH-1;
258-2
Issue 02 (2011-07-11)
//Set HCS cell to Use of HCS ADD UCELLHCS: CellId=11, UseOfHcs=USED; //Add an intra-frequency neighboring cell ADD UINTRAFREQNCELL: RncId=1, CellId=11, NCellRncId=9, NCellId=100, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Add an inter-frequency neighboring cell ADD UINTERFREQNCELL:RncId=1, CellId=11, NCellRncId=9, NCellId=100, CIOOffset=0, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, HOCovPrio=1, BlindHOFlag=FALSE, NPrioFlag=FALSE; //Add a GSM inter-RAT neighboring cell ADD U2GNCELL: RncId=1, CellId=11, GSMCellIndex=0, CIOOffset=0, Qoffset1sn=0, Qrxlevmin=-50, TpenaltyHcsReselect=D0, TempOffset1=D3, BlindHoFlag=TRUE, BlindHOPrio=30, NPrioFlag=FALSE; //Set Algorithm Switch for UE Speed Estimation ADD UCELLHCSHO: CellId=11, SpdEstSwitch=ON; //Deactivating HCS (Hierarchical Cell Structure). SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-0; MOD UCELLHCS: CellId=11, UseOfHcs=NOT_USED; MOD UCELLHCSHO: CellId=11, SpdEstSwitch=OFF;
Issue 02 (2011-07-11)
258-3
259 Configuring Intra Frequency Load Balance
259
Prerequisite
l l l
Configuring Intra Frequency Load Balance
This section describes how to activate, verify, and deactivate the optional feature WRFD-020104 Intra Frequency Load Balance.
Context
This feature enables the change in cell load by adjusting the cell PCPICH power. For those UEs in soft handover state, this feature enables the intra-frequency neighboring cells to share the cell load by removing high load cell from the active set.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intrafrequency neighboring cell. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, select INTRA_FREQUENCY_LDB from the Cell LDC algorithm switch dropdown list. Run the BSC6900 MML command SET ULDCPERIOD. In this step, set Intrafrequency LDB period timer length to an appropriate value. Run the BSC6900 MML command MOD UCELLLDB to set the following parameters associated with the cell-level intra-frequency load balancing (LDB) algorithm to appropriate values: Cell overload threshold
3. 4.
Pilot power adjustment step Cell under load threshold 5. Run the BSC6900 MML command MOD UPCPICHPWR. In this step, set P-CPICH parameters associated with intra-frequency LDB, including Max transmit power of PCPICH and Min transmit power of PCPICH to appropriate values.
Verification Procedure To verify that the RNC can balance the cell load by adjusting the P-CPICH power of a cell, perform the following steps: 1. 2. 3. On the BSC6900 LMT, open the Monitor tab page. Create the task of monitoring PCPICH TxPower of CELL_A11. Run the NodeB MML command STR DLSIM to simulate high load in CELL_A11. In the Cell Performance Monitoring dialog box, check the pilot power of CELL_A11. Expected result: As the cell load increases, the pilot power periodically decreases. The actual pilot power must not be decreased to a level lower than the configured minimum pilot power. 4. The NBAP_CELL_RECFG_REQ and NBAP_CELL_RECFG_RSP messages should be displayed in the Iub tracing result. In the NBAP_CELL_RECFG_REQ message, check whether the RNC has reduced the pilot power. Run the NodeB MML command STR DLSIM to stop simulating high load in CELL_A11. In the Cell Performance Monitoring dialog box, check the pilot power of CELL_A11. Expected result: As the cell load becomes normal, the pilot power periodically increases. The actual pilot power must not be increased to a level higher than the configured maximum pilot power.
5. 6.
Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect INTRA_FREQUENCY_LDB from the Cell LDC algorithm switch dropdown list. Restore the parameter settings modified in the activation procedure.
2. ----End
Example
//Activating Intra Frequency Load Balance //Configuring intra-frequency neighboring cells ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=1, NCellId=211, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; //Enabling the cell-oriented intra-frequency LDB algorithm MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-1; //Setting the intra-frequency LDB period SET ULDCPERIOD: IntraFreqLdbPeriodTimerLen=1800; //Setting parameters associated with the cell-oriented intra-frequency LDB algorithm to appropriate values MOD UCELLLDB: CellId=111, PCPICHPowerPace=2, CellOverrunThd=90, CellUnderrunThd=30; //Setting the P-CPICH associated parameters for intra-frequency LDB MOD UPCPICHPWR: CellId=111, MaxPCPICHPower=346, MinPCPICHPower=313;
259-2
Issue 02 (2011-07-11)
//Verifying Intra Frequency Load Balance STR DLSIM: LOCELL=111, LR=90; STP DLSIM: LOCELL=111; //Deactivating Intra Frequency Load Balance MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-0;
Issue 02 (2011-07-11)
259-3
260 Configuring Potential User Control
260
Prerequisite
l l l
Configuring Potential User Control
This section describes how to activate, verify, and deactivate the optional feature WRFD-020105 Potential User Control.
Context
This feature reduces system load by modifying cell selection and reselection parameters. In this way, the cell where the UE camps can be controlled based on cell load.
Procedure
l Activation Procedure 1. 2. Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the cell-oriented PUC algorithm. Run the BSC6900 MML command SET ULDCPERIOD to specify the period of potential user control. In this step, set PUC period timer length to an appropriate value. Run the BSC6900 MML command ADD UCELLPUC to set the cell-oriented PUC algorithm parameters. Configure two cells CELL_A11 and CELL_A12 as inter-frequency neighboring cells on the NodeB. Run the BSC6900 MML command MOD UCELLPUC to change the potential user control threshold for CELL_A11. Run the NodeB MML command STR DLSIM to simulate a situation where the cell has a high load.
3. l
Issue 02 (2011-07-11)
260 Configuring Potential User Control
The following messages can be traced on the Iub interface: the NBAP_SYS_INFO_UPDATE_REQ from the RNC to the NodeB, and the NBAP_SYS_INFO_UPDATE_RSP message responded by the NodeB. The updated system information can be traced on the Uu interface. The value of the Sintersearch signaling element (IE) of the SIB3 of CELL_A11 decreases, and the values of the Qoffset1s,n and Qoffset2s,n IEs of the SIB11 of CELL_A11 increase. 4. 5. Run the BSC6900 MML command MOD UCELLPUC to change the potential user control threshold for CELL_A12. Run the NodeB MML command STR DLSIM to simulate a situation where CELL_A12 has a high downlink load. The following messages can be traced on the Iub interface: the NBAP_SYS_INFO_UPDATE_REQ message from the RNC to the NodeB, and the NBAP_SYS_INFO_UPDATE_RSP response message from the NodeB. The updated system information can be traced on the Uu interface. The value of the Sintersearch IE of the SIB3 of CELL_A11 decreases, and the values of the Qoffset1s,n and Qoffset2s,n IEs of the SIB11 of CELL_A11 increase. l Deactivation Procedure 1. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, deselect the PUC(Potential User Control Algorithm) check box under the parameter Cell LDC algorithm switch.
----End
Example
//Activating Potential User Control MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-1; SET ULDCPERIOD: PucPeriodTimerLen=1800; ADD UCELLPUC: CELLID=1, SPUCLIGHT=45, SPUCHEAVY=70, SPUCHYST=5, OFFSINTERLIGHT=-2, OFFSINTERHEAVY=2, OFFQOFFSET1LIGHT=-4, OFFQOFFSET2LIGHT=-4, OFFQOFFSET1HEAVY=4, OFFQOFFSET2HEAVY=4; //Deactivating Potential User Control MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-0;
260-2
Issue 02 (2011-07-11)
261 Configuring Load Based GSM and UMTS Handover Enhancement Based on Iur-g
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.
261
l
Configuring Load Based GSM and
Prerequisite
Dependencies on Hardware The BSC model is the BSC6900. A GSM+UMTS dual-mode MS is required. Interface board FG2a/FG2c/GOUa/GOUc should be configured to support Iur-g. l Dependencies on Other Features Configurations of other features on which this feature depends are complete. This feature depends on features GBFD-511101 Load Based Handover Enhancement on Iur-g, WRFD-020306 Inter-RAT Handover Based on Load or WRFD-021200 HCS (Hierarchical Cell Structure). l l l l l License The license controlling this feature has been activated. Both the 2G network and the 3G network are deployed. IP transmission mode is used on the Iur-g interface. A GSM cell and a UMTS cell are configured and the GSM cell is configured as the neighboring cell of the UMTS cell. Data is negotiated and planned for the inter-BSC6900 Iur-g interface. For details you can refer to Configuring the inter-BSC6900 Iur-g interface.
NOTE
l The licenses on the BSC and the RNC sides are activated separately.
Context
This feature is based on Huawei private information exchange mechanism over the Iur-g interface. With this feature, the traffic is distributed through the RRC redirection and load-based handover from the 3G network to the 2G network on the basis of the service attributes and the load of the 2G networks when 3G cell enters LDR status. In this manner, the load is shared by the GSM network when the load of UMTS network is heavy.
Procedure
l 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, Adjustment Coefficient of 2G Load Value to 1and 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.
NOTE
l If the verification achieves the following results as expected, the configuration succeeds. Otherwise, the configuration fails.
1.
3G-to-2G Load Based Handover Enhancement
CAUTION
The verification can be done when only the UMTS cell is in the basic congestion state.
261-2
Issue 02 (2011-07-11)
(1) Use the dual-mode MS to call a fixed telephone in the UMTS cell. Trace signaling on the Iu interface on the LMT. RANAP_RELOCATION_REQUIRED message is reported. The RANAP_RELOCATION_REQUIRED message contains reduce-load-in-serving-cell. Trace signaling on the A interface on the LMT. Handover Request message is reported. The Handover Request message contains reduce-load-in-serving-cell.
NOTE
After the verification, set the value of system to the value before the verification.
2.
2G-to-3G Load Based Handover Enhancement (1) Use the MS to initiate a call in the GSM cell, and the call is successfully established. (2) When the GSM cell is in the basic congestion state, the MS hand over to 3G neighbor cell. Trace signaling on the A interface. Check that Assignment Request, Handover Required, and Handover Command messages are reported and cause in the Handover Required message is directed-retry(13).
Deactivation Procedure 1. Configuration on the RNC side 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). 2. Configuration on the BSC side 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).
----End
Example
//Activating Handover based on Load Enhancement //Configuration on the RNC side /*Enabling the non-coverage-based handover*/ SET UMBSCCRRM: MbscNcovHoOn2GldInd=ON, LoadHoOn3G2GldInd=ON; /*Enabling the inter-RAT handover*/ 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;
Issue 02 (2011-07-11)
261-3
//Deactivating UMTS Handover based on Load Enhancement //Configuration on the RNC side SET UMBSCCRRM: MbscNcovHoOn2GldInd=OFF, LoadHoOn3G2GldInd=OFF; //Configuration on the BSC side SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=NO;
261-4
Issue 02 (2011-07-11)
262 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based on Iur-g
Assisted Cell Change) 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.
262
l
Configuring NACC(Network
Prerequisite
Dependencies on Hardware The BSC model is the BSC6900. A GSM+UMTS dual-mode MS is required. Interface board FG2a/FG2c/GOUa/GOUc should be configured to support Iur-g. l Dependencies on Other Features Configurations of other features on which this feature depends are complete. This feature depends on features WRFD-020303 Inter-RAT Handover Based on Coverage, WRFD-020305 Inter-RAT Handover Based on Service, WRFD-020306 Inter-RAT Handover Based on Load, GBFD-511102 NACC Procedure Optimization Based on Iur-g between GSM and WCDMA, or WRFD-021200 HCS (Hierarchical Cell Structure). l l l l l l License The license controlling this feature has been activated. IP transmission mode is used on the Iur-g interface. The MS supports NACC. Both the 2G network and the 3G network are deployed. A GSM cell and a UMTS cell are configured and the GSM cell is configured as the neighboring cell of the UMTS cell. Data is negotiated and planned for the inter-BSC6900 Iur-g interface. For details you can refer to Configuring the inter-BSC6900 Iur-g interface.
NOTE
l The licenses on the BSC and the RNC sides are activated separately.
Issue 02 (2011-07-11)
262-1
Context
With this feature, the network assisted cell change (NACC) procedure is performed through the internal information exchange mechanism of the MBSC. As a result, the interoperability of PS services between GSM cells and UMTS cells under the same MBSC does not involve the CN. In this manner, the time taken to perform the NACC procedure is shortened by about 680ms and therefore the handover delay is reduced. In addition, the NACC procedure does not require the support of the CN.
Procedure
l 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. If multiple neighboring cells are planned, repeat this step to enable the inter-RAT cell to support indication of the RIM for all the neighboring cells. 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 switch 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. Configuration on the RNC side
262-2
(1) Run the BSC6900 MML command SET UCORRMALGOSWITCH on the RNC to deactivate NACC Procedure Optimization. In this step, deselect HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH in the HandOver switch drop-down list box. ----End
Example
//Activating NACC Procedure Optimization //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 //Configuration on the RNC side SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-0;
Issue 02 (2011-07-11)
262-3
263 Configuring GSM and UMTS Load Balancing Based on Iur-g
263
Prerequisite
l
Configuring GSM and UMTS Load Balancing Based on Iur-g
This section describes how to activate, verify, and deactivate the optional feature WRFD-070006 GSM and UMTS Load Balancing Based on Iur-g.
Dependencies on Hardware The BSC model is BSC6900. The MS is in GSM+UMTS dual mode. Interface board FG2a/FG2c/GOUa/GOUc should be configured to support Iur-g.
Dependencies on Other Features Configurations of other features on which this feature depends are complete. This feature depends on features GBFD-511103 GSM and UMTS Load Balancing Based on Iur-g, WRFD-020400 DRD Introduction Package and WRFD-020305 InterRAT Handover Based on Service.
l l l l
License The license controlling this feature has been activated. 2G and 3G networks cover the same area. IP transmission mode is used over the Iur-g interface. The value of the information element (IE) Service Handover in the RAB ASSIGNMENT REQUEST message sent from the CN to the RNC is Handover to GSM should be performed. The value of the IE Service Handover in the 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 a neighboring cell of the UMTS cell. Data is negotiated and planned for the inter-BSC6900 Iur-g interface. For details you can refer to Configuring the inter-BSC6900 Iur-g interface.
NOTE
l l l
l The licenses on the BSC and RNC sides are activated separately.
Issue 02 (2011-07-11)
263-1
Context
This feature implements RRC redirection and the load-based GSM/UMTS handover through the exchange of Huawei proprietary IE over the Iur-g interface. The Iur-g protocol stack complies with the 3GPP specifications. With this feature, the traffic is distributed on the basis of the service handover indicator and the load of the GSM network and UMTS network during RRC connection setup or after RAB setup. In this way, a load balance is achieved between the GSM network and UMTS network.
Procedure
l Activation Procedure 1. Configuration on the RNC side (1) Run the BSC6900 MML command SET UMBSCCRRM to enable load balancing and set load difference thresholds. In this step, set Service Distribution and Load Balancing Switch to LOAD-BASED(LOADBASED), Load Difference Threshold Between 3G And 2G of CS Service to 10, PS Load Difference Threshold Between 3G And 2G of Ps Service to 30, and Adjustment Coefficient of 2G Load Value to 1. (2) Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable inter-RAT handover. In this step, select the HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH check boxes under the parameter HandOver switch. 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 Load-based(Loadbased), 2G Load Adjustment Coefficient to 10. (2) Run the BSC6900 MML command SET GCELLHOBASIC to enable interRAT incoming BSC handover. In this step, set Inter-RAT In BSC Handover Enable and Intra-RAT In BSC Handover Enable to YES(Yes). If multiple neighboring cells are planned, repeat this step to enable inter-RAT incoming BSC handover for all neighboring cells. (3) Run the BSC6900 MML command SET OTHSOFTPARA. In this step, set CS 2G 3G Load Balance Delta Threshold to 110. l Verification Procedure
NOTE
If the verification achieves the following results as expected, the configuration succeeds. Otherwise, the configuration fails.
1.
3G-to-2G Load Balancing
CAUTION
The verification can be done when only the UMTS cell is in the basic congestion state. (1) The verification procedure consists of the RRC setup phase and the RAB connection phase. The verification in the latter phase involves CS speech services and PS data services.
a.
Verifying that CS speech services in UMTS cell1 are handed over to GSM cell2 at the RRC setup phase 1) Use the dual-mode MS to call a fixed telephone in cell1. The call is successfully established. Initiate Uu-interface signaling tracing on the LMT. The RRC_RRC_CONNECT_REQ and RRC_RRC_CONN_REJECT messages are reported, and the RRC_RRC_CONN_REJECT message contains GSMTargetCellInfo. That is, information about cell2 is contained, indicating that the MS accesses cell2.
b.
Verifying that PS data services in UMTS cell1 are handed over to GPRS cell3 at the RAB connection phase 1) 2) Use the MS to browse the Internet. Initiate Uu-interface message tracing on the LMT. You can find that the messages RRC_RB_SETUP, RRC_RB_SETUP_CMP, RRC_MEAS_CTRL, and RRC_CELL_CHANGE_ORDER_FROM_UTRAN are reported, and that the value of InterRATEvent in the RRC_MEAS_CTRL message is event3c. Initiate Iu-interface signaling tracing on the LMT. You can find that the RANAP_SRNS_CONTEXT_REQ message is sent from the CN to the RNC and then the RANAP_SRNS_CONTEXT_RESP message is sent from the RNC to the CN. Initiate Iu-interface signaling tracing 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 cell3, Internet browsing is slightly affected. After the MS reselects cell3, Internet browsing returns to normal.
3)
4)
5)
c.
Verifying that CS speech services in UMTS cell1 are handed over to GSM cell2 at the RAB connection phase 1) 2) Use the dual-mode MS to call a fixed telephone in cell1. The call is successfully established. Initiate Uu-interface tracing on the LMT. You can find that the messages RRC_RB_SETUP, RRC_RB_SETUP_CMP, RRC_MEAS_CTRL, and RRC_HO_FROM_UTRAN_CMD_GSM are reported, and that the value of InterRATEvent in the RRC_MEAS_CTRL message is event3c. Initiate Iu-interface signaling tracing 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 messages are sent from the CN to the RNC. Initiate Iu-interface signaling tracing on the LMT. You can find that the RANAP_IU_RELEASE_COMPLETE message is sent from the RNC to the CN.
3)
4)
2.
Issue 02 (2011-07-11)
2G-to-3G Load Balancing

CAUTION
The verification can be done when only the GSM cell is in the basic congestion state. (1) Use the MS to initiate a call in the GSM cell. The directed retry procedure is triggered so that the MS accesses the neighboring UMTS cell. The call is successfully established. Initiate A-interface signaling tracing on the LMT. You can find that the Assignment Request, Handover Required, and Handover Command messages are reported and that the value of cause in the Handover Required message is directed-retry(13). l Deactivation Procedure 1. Configuration on the RNC side (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). 2. Configuration on the BSC side (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 Load Balancing Based on Iur-g //Configuration on the RNC side /*Enabling load balancing and setting load difference thresholds*/ SET UMBSCCRRM: MbscServiceDiffLdbSwitch=LOAD-BASED, Mbsc3G2GLdBlcCsDeltaThrd=10, Mbsc3G2GLdBlcPsDeltaThrd=30; /*Enabling 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 load balancing*/ SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=YES, InterRatServiceLoadHoSwitch=Load-based, G2GLoadAdjustCoeff=10; /*Enabling inter-RAT handover*/ SET GCELLHOBASIC: IDTYPE=BYNAME, CELLNAME="0", INTERRATOUTBSCHOEN=YES, INTERRATINBSCHOEN=YES; /*Setting load difference thresholds*/ SET OTHSOFTPARA: G2G3GLdBlcDeltaThrd=110; //Deactivating Load Balancing Based on Iur-g //Configuration on the RNC side SET UMBSCCRRM: MbscServiceDiffLdbSwitch=OFF; //Configuration on the BSC side SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, InterRatServiceLoadHoSwitch=OFF;
263-4
Issue 02 (2011-07-11)
264 Configuring GSM and UMTS Traffic Steering Based on Iur-g
264
Prerequisite
l
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.
Dependencies on Hardware The BSC model is BSC6900. The MS is in GSM+UMTS dual mode. Interface board FG2a/FG2c/GOUa/GOUc should be configured to support Iur-g.
Dependencies on Other Features Configurations of other features on which this feature depends are complete. This feature depends on features GBFD-511104 GSM and WCDMA Traffic Steering Based on Iur-g, WRFD-020400 DRD Introduction Package and WRFD-020305 InterRAT Handover Based on Service.
l l l l
License The license controlling this feature has been activated. 2G and 3G networks cover the same area. IP transmission mode is used over the Iur-g interface. The value of the information element (IE) Service Handover in the RAB ASSIGNMENT REQUEST message sent from the CN to the RNC is Handover to GSM should be performed. The value of the IE Service Handover in the 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 a neighboring cell of the UMTS cell. Data is negotiated and planned for the inter-BSC6900 Iur-g interface. For details you can refer to Configuring the inter-BSC6900 Iur-g interface.
NOTE
l l
l The licenses on the BSC and RNC sides are activated separately.
Issue 02 (2011-07-11)
264-1
Context
This feature supports RRC redirection and GSM/UMTS inter-RAT handover based on service. With this feature, services are steered on the basis of the service handover indicator, hierarchical network planning, and the load of the GSM network and UMTS network when an MS accesses the network. Service steering enables UEs requesting speech or low-speed PS services to access the GSM network and those requesting high-speed PS services to access the UMTS network.
Procedure
l Activation Procedure 1. Configuration on the RNC side (1) Run the BSC6900 MML command SET UMBSCCRRM to enable traffic steering. In this step, set Service Distribution and Load Balancing Switch to SERVICE-BASED(SERVICE-BASED) and Adjustment Coefficient of 2G Load Value to 1. (2) Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable inter-RAT handover. In this step, select the HO_INTER_RAT_CS_OUT_SWITCH and HO_INTER_RAT_PS_OUT_SWITCH check boxes under the parameter HandOver switch. (3) Run the BSC6900 MML command ADD UCELLHOCOMM to enable interRAT CS and PS handover. In this step, set both Inter-RAT CS Handover Switch and Inter-RAT PS Handover Switch to ON. Run the ADD UCELLHOCOMM command to enable inter-RAT CS and PS handover for each cell. 2. Configuration on the BSC side (1) Run the BSC6900 MML command SET GCELLHOINTERRATLDB to enable traffic steering. In this step, set Allow Inter-RAT Load HO in Access State to Service-based(Service-based). l Verification Procedure 1. The verification procedure of 3G-to-2G Traffic Steering
CAUTION
The verification can be done when only the UMTS cell is in the basic congestion state. (1) Use the dual-mode MS to call a fixed telephone in the UMTS cell. Initiate Iuinterface tracing on the LMT. You can find that the RANAP_RELOCATION_REQUIRED message is reported and the handover cause value in the message is resource-optimisation-relocation. Initiate A interface tracing. You can find that the Handover Request message is reported and the handover cause value in the message is traffic.
264-2
Issue 02 (2011-07-11)
CAUTION
Ensure that the GSM cell is not in the congestion state. 2. The verification procedure of 2G-to-3G Traffic Steering
CAUTION
The verification can be done when only the GSM cell is in the basic congestion state. (1) Use the dual-mode MS to call a fixed telephone in the GSM cell. Initiate CS Domain Messages of a Single Subscriber tracing on the LMT. You can find that the call is in GSM cell, and don't hand over to UMTS cell. l Deactivation Procedure 1. Configuration on the RNC side (1) Run the BSC6900 MML command SET UMBSCCRRM to deactivate traffic steering. In this step, set Service Distribution and Load Balancing Switch to OFF(OFF). ----End
Example
//Activating 3G-to-2G traffic steering //Configuration on the RNC side /*Enabling traffic steering*/ SET UMBSCCRRM: MbscServiceDiffLdbSwitch=SERVICE-BASED; /*Enabling 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 handover*/ ADD UCELLHOCOMM: CellId=1, CSServiceHOSwitch=ON, PSServiceHOSwitch=ON; //Configuration on the BSC side /*Enabling inter-RAT incoming BSC handover*/ SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, InterRatServiceLoadHoSwitch=Service-based; //Deactivating 3G-to-2G traffic steering //Configuration on the RNC side SET UMBSCCRRM: MbscServiceDiffLdbSwitch=OFF;
Issue 02 (2011-07-11)
264-3
265 Configuring Warning of Disaster
265
Prerequisite
l l
Configuring Warning of Disaster
This section describes how to activate, verify, and deactivate the optional feature WRFD-020127 Warning of Disaster.
Dependencies on Hardware This feature does not have any special requirements for hardware. Dependencies on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-011001 Simplified Cell Broadcast.
License This feature is not under license control.
Context
With this feature, the Cell Broadcast Center (CBC) incorporated into the RNC informs all users in specified cells of the disaster information through message broadcasting in the shortest time, therefore minimizing the impact of the disaster.
NOTE
Activating this feature requires operations on only the RNC.
Procedure
l Activation Procedure 1. 2. 3. For detailed operations for activating license, see 3.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.
4.
Issue 02 (2011-07-11)
265 Configuring Warning of Disaster
5. 6.
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. Run the BSC6900 MML command ADD UCBSMSG or MOD UCBSMSG to configure the broadcast message.
NOTE
l When disasters (such as earthquakes, tsunamis, and hurricanes) occur, Set Geography Scope to CellImmediate, and set CBS Message Priority to High so that users can receive the message in time. l It is recommended to set Number of CBS Messages to a value greater than 3 to ensure that all UEs can receive the message.
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 (The following procedure uses a cell as an example.) 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 warning of disaster SET URNCCBPARA: CTCHSwitch=OFF;
265-2
Issue 02 (2011-07-11)
266 Configuring Flexible frequency bandwidth of UMTS carrier
266
Prerequisite
l
Configuring Flexible frequency bandwidth of UMTS carrier
This section describes how to activate, verify, and deactivate the optional feature WRFD-021001 Flexible frequency bandwidth of UMTS carrier.
Dependencies on Hardware For 4.6M~5M(including 4.6M), all the RF module can support this feature. For 4.2M~4.6M(excluding 4.6M), only 850M/1900M RRU3804, 850M WRFU, MRFU V1/V2 and MRRU V1/V2, WRFUd, RRU3828, RRU3829, RRU3928, RRU3929, MRFUd, MRFUe can support this feature.
l l
Context
To help an operator adapt to insufficient frequency resources, Huawei supports flexible frequency spacing. In network planning, to address insufficient bandwidth resources, an operator can plan a frequency spacing that is lower than the frequency spacing in the case of 5.0 MHz UMTS carrier bandwidth. Accordingly, the effective bandwidth of the RRU or RFU carrier is adjusted so that the carrier works in a suitable status with suitable algorithms and parameters. In this way, network performance on a low- spacing frequency is optimized as much as possible. When deploying a UMTS site, one needs to adjust the minimal effective bandwidth of a UMTS carrier based on the GSM frequency configuration. Otherwise, TRX alarms may occur or network performance may deteriorate.
Procedure
l Activation Procedure 1. Before configuring the effective bandwidth of the carrier, run the NodeB MML command LST RRU to check that an RRU is configured for the cell that requires
Issue 02 (2011-07-11)
266 Configuring Flexible frequency bandwidth of UMTS carrier
setting of carrier effective bandwidth. If an RRU is not configured, run the NodeB MML command ADD RRU to add an RRU. 2. l Run the NodeB MML command SET FREQBWH to set the minimal effective bandwidth of the RRU carrier (parameter: Frequency Min Bandwidth).
Verification Procedure Run the NodeB MML command LST FREQBWH to query the effective bandwidth of the RRU carrier and check the returned message. If... The effective bandwidth of the carrier matches the configuration. The effective bandwidth of the carrier does not match the configuration. Then... The configuration succeeds. The configuration fails.
Deactivation Procedure Run the NodeB MML command SET FREQBWH to set the RRU effective bandwidth to 5000 Hz so that the standard configuration of the system is restored.
----End
Example
//Activation procedure SET FREQBWH: CN=0, SRN=60, SN=0, FMBWH=4200; //Verification procedure LST FREQBWH; //Deactivation procedure SET FREQBWH: CN=0, SRN=60, SN=0, FMBWH=5000;
266-2
Issue 02 (2011-07-11)
267 Configuring Push to Talk
267
Prerequisite
l l Dependencies on Hardware
Configuring Push to Talk
This section describes how to activate, verify, and deactivate the optional feature WRFD-020134 Push to Talk.
This feature does not depend on the hardware. Dependencies on Other Features The following features must be configured before this feature is activated: WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package. l l License The license controlling this feature has been activated. Other Prerequisites The UE and CN support the Push to Talk (PTT) solution.
Context
This feature is a part of the end-to-end PTT solution. PTT needs joint support from the UE, RAN, CN, and PTT server. With this feature, Huawei RAN can identify PTT services and implement technologies to reduce the delay of PTT services.
Procedure
l Activation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select CFG_PTT_SWITCH from the Channel Configuration Strategy Switch drop-down list. Run the BSC6900 MML command SET UFRC. In this step, based on the network plan, set parameters PTT ARP Priority, PTT ARP Preemption Capability, PTT ARP Preemption Vulnerability, and PTT ARP Queuing Allowed to the same values as those of Priority Level, Preemption Capability, Preemption Vulnerability, and Queuing Allowed respectively. The latter four ones are in allocation/retention priority (ARP) properties of the RNCAP_RAB_ASSIGNMENT_REQ message sent from the CN.
2.
Issue 02 (2011-07-11)
267 Configuring Push to Talk
3.
Run the BSC6900 MML command SET URRCTRLSWITCH to turn on switches PTT_EARLY_TRANS_SWITCH and PTT_SPEC_LI_SWITCH. In this step, deselect PTT_EARLY_TRANS_SWITCH_OFF and PTT_SPEC_LI_SWITCH_OFF from the Process switch drop-down list. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable PTT UEs to switch to the DCH for access reattempts when HSPA resources are insufficient. In this step, select the RESERVED_SWITCH_0_BIT19 check box under the parameter CORRM Algorithm Reserved Switch 0. On the BSC6900 LMT, start Iu Interface Trace to check whether the CN has sent an RNCAP_RAB_ASSIGNMENT_REQ message.
NOTE
4.
The RNC identifies PTT services based on information elements TrafficClass, Signaling Indication, ArpPriorityLevel, ArpPreEmptCap, ArpPreEmptVuln, and ArpQueuingAllowed in the RNCAP_RAB_ASSIGNMENT_REQ message. If some services are identified as PTT services, the RNC allocates a rate of 8 kbit/s to the services.
Deactivation Procedure 1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step, deselect CFG_PTT_SWITCH from the Channel Configuration Strategy Switch drop-down list.
----End
Example
//Activating Push to Talk SET UCORRMALGOSWITCH: CfgSwitch=CFG_PTT_SWITCH-1; SET UFRC: PTTARPPRIORITYLEVEL=1, PTTARPPREEMPTCAP=TRIGGER, PTTARPPREEMPTVULN=NOT_PRE_EMPTABLE, PTTARPQUEUINGALLOWED=ALLOWED; SET URRCTRLSWITCH: PROCESSSWITCH=PTT_EARLY_TRANS_SWITCH_OFF-0&PTT_SPEC_LI_SWITCH_OFF-0; SET UCORRMALGOSWITCH: ReservedSwitch0=RESERVED_SWITCH_0_BIT19-1; //Deactivating Push to Talk SET UCORRMALGOSWITCH: CfgSwitch=CFG_PTT_SWITCH-0;
267-2
Issue 02 (2011-07-11)
268 Configuring RNC Offload (Trial)
268
Prerequisite
l l l l
Configuring RNC Offload (Trial)
This section describes how to activate, verify, and deactivate the optional feature WRFD-012001 RNC Offload (Trial). With this feature, the RNC can send some PS service data directly to Internet over the offload Gi interface.
Dependencies on Hardware The Gi interface between the RNC and the Internet is supported only by the FG2c board and the GOUc board. Dependencies on Other Features This feature does not depend on other features. License This feature is not under license control. Others The RNC supports the Network Address Translation (NAT) technology.
Context
The RNC Offload function is applied by means of NAT. The RNC analyzes the uplink data flow, performs NAT on some service data, and then sends the service data to the Internet over the offload Gi interface. Figure 268-1 shows the offload Gi interface between the RNC and the Internet. Figure 268-1 Offload Gi interface
Issue 02 (2011-07-11)
268-1
To enable data packets from the Internet to directly arrive at the RNC (instead of the GGSN), the source IP address of an uplink data packet must be changed to the public IP address of the offload Gi interface by means of NAT. In this way, the downlink data packets can flow into the UTRAN over the offload Gi interface. The RNC Offload function can be configured on the basis of IMEI, IMSI, cell, service type, Access Point Name (APN), and destination IP address.
Procedure
l Activation Procedure 1. 2. 3. 4. 5. 6. 7. 8. 9. Run the BSC6900 MML command ADD BRD to add an FG2c board. Run the BSC6900 MML command SET ETHPORT to set the Ethernet port attributes of the FG2c board. Run the BSC6900 MML command ADD ETHREDPORT to add two Ethernet ports as active and standby ports. Run the BSC6900 MML command ADD UGIPORT to add a Gi interface. Run the BSC6900 MML command ADD ETHIP to add an IP address of the Gi interface. Run the BSC6900 MML command ADD IPRT to add a route from the Gi interface to the firewall. Run the BSC6900 MML command ADD UNATRESPOOL to add a NAT resource pool. Run the BSC6900 MML command SET UNATSWITCH to enable the NAT function. Run the BSC6900 MML command SET UNATALG to set the Application Level Gateway (ALG) function for the protocols over the Gi interface.
10. Run the BSC6900 MML command ADD UOFFLOAD to configure RNC Offload for the operator. 11. Run the BSC6900 MML command ADD UOFFLOADRAB to configure RNC Offload based on user priority and service type. 12. (Optional) To configure RNC Offload based on IMEI, run the BSC6900 MML command MOD UOFFLOAD to enable the TAC-level offload function. Then, run the BSC6900 MML command ADD UOFFLOADIMEITAC to configure the TAClevel offload function. For details about Type Allocation Code (TAC), see the MML command ADD UIMEITAC. 13. (Optional) To configure RNC Offload based on APN, run the BSC6900 MML command ADD UOFFLOADAPN to add a registered APN for the operator. Then, run the BSC6900 MML command MOD UOFFLOAD to enable RNC Offload based on APN. 14. (Optional) To configure RNC Offload based on IMSI, run the BSC6900 MML command ADD UOFFLOADIMSI to set the range of IMSIs supporting RNC Offload. 15. (Optional) To configure RNC Offload based on the cell, run the BSC6900 MML command MOD UCELLALGOSWITCH to enable RNC Offload for the cell. 16. (Optional) To configure RNC Offload based on the destination IP address, run the BSC6900 MML command ADD UUNOFFLOADIP to set the IP addresses or network segment that are not allowed to access the Internet using RNC Offload.
Verification Procedure 1. On the BSC6900 LMT, choose Monitor > UMTS monitoring, and then double-click Cell Performance Monitoring. The Cell Performance Monitoring dialog box is displayed. Set Monitor Item to Cell User Number, and then set Monitor Period and Cell ID. Click OK. Choose Monitor > Common Monitoring. Double-click Link Performance Monitoring. The Link Performance Monitoring dialog box is displayed. Set Monitor Item to FE/GE, Subrack No. to 0, Slot No. to 14, Monitor Type to Port, and FE/GE Port No. to 0. Click OK. Power on a UE and enable the UE to camp on CELL1. Use the UE to initiate a PS service. Check the Cell User Number parameter. The number of UEs supporting RNC Offload in the cell changes from 0 to 1. The UE starts data transmission. Check the FE/GE parameter. The data throughput over the FE/GE port increases. Run the BSC6900 MML command MOD UOFFLOAD to disable RNC Offload for the operator.
2. 3. 4. 5. 6. 7. 8. l 1. ----End
Example
//Configuring the Gi interface ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=FG2c, SN=14, RED=YES, MPUSUBRACK=0, MPUSLOT=0; SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0, SPEED=AUTO; ADD ETHREDPORT: SRN=0, SN=14, PN=0; ADD UGIPORT: SRN=0, SN=14, PN=0, ISPSSHAREPORT=NO; ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.53.50.69", MASK="255.255.255.240"; ADD IPRT: SRN=0, SN=14, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", NEXTHOP="10.53.50.68", PRIORITY=HIGH, REMARK="Gi"; //Configuring the NAT function ADD UNATRESPOOL: SRN=0, SN=14, PN=0, NATINDEX=0, STARTADDR="172.168.0.100", ENDADDR="172.168.0.101", MAXPN=65535, MINPN=10000; SET UNATSWITCH: NATSW=ON; SET UNATALG: PROTOCOLTYPE=FTP, ALGSW=ON, AGINGTIMER=600; //Activating RNC Offload ADD UOFFLOAD: CnOpIndex=0, OffloadSwitch=ON, NonDTRAB=PERMIT_OFFLOAD; ADD UOFFLOADRAB: CnOpIndex=0, UserPriority=GOLDEN_USER, OffloadService=STREAMING-1&INTERACTIVE-1&BACKGROUND-0; //Configuring RNC Offload based on IMEI MOD UOFFLOAD: CnOpIndex=0, RsvdPara1=LBO_IMEITAC_SWITCH-1; ADD UOFFLOADIMEITAC: TAC=12345678, Description="iphone"; //Configuring RNC Offload based on APN MOD UOFFLOAD: CnOpIndex=0, OffloadSwitch=ON, NonDTRAB=NOT_PERMIT_OFFLOAD, RegAPN=PERMIT_OFFLOAD; //Configuring RNC Offload based on IMSI ADD UOFFLOADIMSI: CnOpIndex=0, IMSIStart="000000000000000", IMSIEnd="999999999999999"; //Configuring RNC Offload based on the cell MOD UCELLALGOSWITCH: CellId=111, OffloadSwitch=ON;
Issue 02 (2011-07-11)
268-3
//Configuring RNC Offload based on destination IP address ADD UUNOFFLOADIP: CnOpIndex=0, IpAddr="10.10.10.10", Mask="255.255.255.255"; //Deactivating RNC Offload MOD UOFFLOAD: CnOpIndex=0, OffloadSwitch=OFF;
268-4
Issue 02 (2011-07-11)
269 Configuring Multi-mode Dynamic Power Sharing (UMTS)
269
Prerequisite
l l
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).
Dependencies on Hardware Only the MRFU and the RRU3908 supports GSM and UMTS Dynamic Power Sharing at present. Dependencies on Other Features GSM and UMTS Dynamic Power Sharing can not be configured with dynamic spectrum sharing. 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. This feature can't be activated with WRFD-010684 22 MIMO or WRFD-010693 DL 64QAM+MIMO simultaneously. This feature has to be activated with MRFD-211801 Multi-mode Dynamic Power Sharing (GSM) simultaneously.
l l
License The license controlling this feature has been activated. Other Prerequisites The UMTS cell must exist HSDPA Carry.
Context
In the case of a 3900 series multi-mode base station, the GSM and UMTS TRXs can share one power amplifier. When there is unbalanced traffic in the GSM and the UMTS, the power can be used more efficiently in an effective way, namely, sharing the power amplifier. The overall network quality of the GSM and the UMTS is therefore improved.

NOTE
l The feature may fail to recall the shared power in one second when the GSM services increase suddenly. As a result, internal GSM peak clipping occurs, which affects service quality. l Enabling the feature may cause the UMTS coverage to shrink and therefore increase the drop rate. The problem can be addressed by handing over services in marginal coverage to a GSM/UMTS cell under the same coverage as the original UMTS. l The switch and other parameter configurations are performed only on the GSM side. The UMTS side requires no configuration.
Procedure
l 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 parameters Minimum Number of Non-BCCH TRXs in GSM for GU Power Sharing, GSM Power Load Threshold for GU Power Sharing, Number of Checked Timeslots for Retrieving Shared Power, Num of Timeslots Meet Requirements for Retrieving Shared Pwr, GSM Power Reserve Coefficient for Retrieving Shared Power, GSM Idle Channel Threshold for GU Power Sharing, GSM Idle Channel Hysteresis for GU Power Sharing, GSM Power Reserve in Low Load for GU Power Sharing, GSM Power Reserve in High Load for GU Power Sharing, Maximum Accumulated Shared Power That UMTS Can Accept, Maximum Shared Power That UMTS Can Accept In Each Period to actual conditions. Run the NodeB MML command MOD LOCELL, set GU Power Share Flag to TRUE(TRUE). Run the BSC6900 MML command LST BTSGUPWRSHRFP and LST BTSRXUBP and check the returned message. Exception result: Board Parameter Configuration Enabled and GU Dynamic Power Sharing Switch are YES. 2. l Run the NodeB MML command LST LOCELL, and check the returned message. Exception result: GU Power Share Flag is YES. Deactivation Procedure 1. 2. 3. Run the NodeB MML command MOD LOCELL, set GU Power Share Flag to FALSE(FALSE). 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.
3. l
GSM and UMTS Dynamic Power Sharing can be deactivated by performing either of the two steps discussed above.
----End
Example
//Activation procedure SET BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, CFGFLAG=YES, GUPWRSHARESTM1=07&00, GUPWRSHAREETM1=09&00, GUPWRSHARESTM2=10&00, GUPWRSHAREETM2=12&00, GUPWRSHARESTM3=14&00, GUPWRSHAREETM3=16&00, GUPWRSHARESTM4=20&00, GUPWRSHAREETM4=22&00; SET BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0, RXUTYPE=MRFU, GUPWRSHARESWITCH=YES, GUPWRSHARETRXNUM=1, GUPWRSHAREPWRLOAD=80, GUPWRSHAREN=8, GUPWRSHAREP=6, GUPWRSHARERSVFACTOR=50, GUPWRSHAREGSMIDLETH=12, GUPWRSHAREGSMIDLEHS=2, GUPWRSHAREGSMIDLERSVPWR=5, GUPWRSHAREGSMBUSYRSVPWR=10, GUPWRSHAREURCVPWR=15, GUPWRSHAREURCVPWRPD=5; MOD LOCELL: LOCELL=0, SECT=LOCAL_SECTOR, GUPOWERSHARE=TRUE; //Verification procedure LST BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, LSTFORMAT=VERTICAL; LST BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0, LSTFORMAT=VERTICAL; LST LOCELL: MODE=LOCALCELL, LOCELL=0; //Deactivation procedure SET BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, CFGFLAG=NO; SET BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0, RXUTYPE=MRFU, GUPWRSHARESWITCH=NO; MOD LOCELL: LOCELL=0, SECT=LOCAL_SECTOR, GUPOWERSHARE=FALSE;
Issue 02 (2011-07-11)
269-3
270 Configuring GSM and UMTS Dynamic Spectrum Sharing
270
Prerequisite
l l
Configuring GSM and UMTS Dynamic Spectrum Sharing
This section describes how to activate, verify, and deactivate the optional feature MRFD-221802 GSM and UMTS Dynamic Spectrum Sharing. This feature enables the spectrum resources to be dynamically shared between the GSM and UMTS networks based on their traffic load, improving frequency utilization.
Dependencies on Hardware The 900 MHz MRFU and RRU3908 must support this feature. Dependencies on Other Features The configurations of the features on which this feature depends are complete. This feature depends on the feature MRFD-211802 GSM and UMTS Dynamic Spectrum Sharing(GSM). This feature cannot be used together with GBFD-117002 IBCA, GBFD-117001 Flex MAIO, GBFD-115830 VAMOS, or GBFD-510104 Multi-site Cell.
l l
License The license that supports this feature is activated. Start Dynamic Spectrum Sharing on the M2000 by referring to the M2000 Online Help.
Context
The dynamic spectrum sharing (DSS) between GSM and UMTS increases network throughput and reduces the total cost of data services because UMTS has higher spectral efficiency than GSM. In theory, the maximum throughput gain is about 50%. After this feature is used, the total cost of ownership (TCO) of mobile broadband (MBB) can be reduced, and dynamic GSM/ UMTS refarming can be implemented. Thus, the maintenance cost of manual refarming is reduced.
Procedure
l Activation Procedure 1.
Issue 02 (2011-07-11)
Configuration on the RNC side

(1) Run the BSC6900 MML command MOD UNODEB with DSS NodeB Flag set to TRUE. (2) Run the BSC6900 MML command ADD UCELLQUICKSETUP to set up a DSS cell, set DSS Cell Flag to TRUE, and set Maximum TX Power in Small DSS Coverage and PCPICH TX Power in Small DSS Coverage based on network conditions. (3) Run the BSC6900 MML command MOD UCELLACCESSSTRICT with both Cell barred indicator for SIB3 and Cell barred indicator for SIB4 of DSS cells set to BARRED. (4) Run the BSC6900 MML command ADD UINTERFREQNCELL to add the neighbor 3G cells of DSS cells as inter-frequency neighboring cells, and set Blind Handover Flag to TRUE. (5) Run the BSC6900 MML command ADD U2GNCELL to add the neighboring GSM cells for DSS cells, and set Blind Handover Flag to TRUE. (6) Run the BSC6900 MML command ADD U2GNCELL to add the neighboring DSS cells as intra-frequency neighboring cells. (7) Run the BSC6900 MML command SET UCORRMALGOSWITCH with both DRD switch for single RAB and HO_INTER_FREQ_HARD_HO_SWITCH set to ON. (8) Run the BSC6900 MML command SET UDRD with Load balance DRD switch for HSDPA set to ON and Load Balancing DRD Choice set to UserNumber. (9) Run the BSC6900 MML command ADD UCELLDRD with Load balance DRD switch for HSDPA set to ON and Load Balancing DRD Choice set to UserNumber. (10) Run the BSC6900 MML command ACT UCELL to activate the cell. 2. Configuration on the NodeB side Run the BSC6900 MML command ADD LOCELL to add local DSS cells, and set GUPOWERSHARE to FALSE. 3. Configuration on the BSC side (1) Run the BSC6900 MML command ADD GEXT3GCELL to add 3G external cells. (2) Run the BSC6900 MML command ADD G3GNCELL to add 3G neighboring cells. (3) Run the BSC6900 MML command SET GDSSPARA with Spectrum Sharing Allowed set to YES(Yes). (4) Run the BSC6900 MML command SET GTRXDEV with Spectrum Sharing Shutdown Allowed set to YES(Yes).
CAUTION
The parameter Spectrum Sharing Shutdown Allowed for all TRXs to be shared under a base station should be set to YES(Yes) except for the BCCH TRX. l Verification Procedure 1.
270-2
Start spectrum sharing on the M2000 manually.

2.
Run the BSC6900 MML command DSP UNODEB to query the DSS status of a NodeB. Expected result: The value of NodeB DSS state is Actived in Normal DSS coverage.
3. 4.
Run the BSC6900 MML command DSP UCELL to query the DSS status of a cell. Expected result: The value of DSS state is Actived in Normal DSS coverage. Run the NodeB MML command LST LOCELL to check the value of GU Power Share Flag. Expected result: The value of GU Power Share Flag is TRUE. Run the BSC6900 MML command DSP BTSSTAT to query the value of Dynamic Spectrum Sharing. Expected result: The value of Dynamic Spectrum Sharing is Yes. Stop Dynamic Spectrum Sharing on the M2000 by referring to the M2000 Online Help. Run the BSC6900 MML command MOD UNODEB with DSS NodeB Flag set to FALSE. Run the BSC6900 MML command SET GDSSPARA with Spectrum Sharing Allowed set to NO(No). Run the BSC6900 MML command SET GTRXDEV with Spectrum Sharing Shutdown Allowed set to FALSE. Remove the neighboring cell by referring to Reconfiguration Guide. Run the BSC6900 MML command DEA UCELL to deactivate a cell.
5.
Deactivation Procedure 1. 2. 3. 4. 5. 6.
----End
Example
//Activation procedure MOD UNODEB: NodeBId=1, DSSFlag=TRUE; ADD UCELLQUICKSETUP: CellId=102, CellName="dss102", PeerIsValid=INVALID, CnOpGrpIndex=0, BandInd=Band2, UARFCNDownlink=412, PScrambCode=0, TCell=CHIP256, LAC=1, SAC=0, CfgRacInd=NOT_REQUIRE, SpgId=1, URANUM=D1, URA1=0, NodeBName="102", LoCell=102, SupBmc=FALSE, DSSFlag=TRUE, DSSSmallCovMaxTxPower=431, DSSSmallCovPCPICHPower=331; MOD UCELLACCESSSTRICT: CellId=102, IdleCellBarred=BARRED, IdleIntraFreqReselection=ALLOWED, IdleTbarred=D320, ConnCellBarred=BARRED, ConnIntraFreqReselection=ALLOWED, ConnTbarred=D320; ADD UINTERFREQNCELL: RNCId=0, CellId=102, NCellRncId=1, NCellId=105, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE; ADD U2GNCELL: RNCId=2, CellId=102, GSMCellIndex=120, BlindHoFlag=TRUE, NPrioFlag=FALSE; ADD UINTRAFREQNCELL: RNCId=0, CellId=102, NCellRncId=3, NCellId=121, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE; SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1, HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1; SET UDRD: LdbDRDSwitchHSDPA=ON, LdbDRDchoice=UserNumber; ADD UCELLDRD: CellId=120, LdbDRDSwitchHSDPA=ON, ReDirBandInd=DependOnNCell; ACT UCELL: CellId=102;
Issue 02 (2011-07-11)
270-3
ADD LOCELL: LOCELL=102, STN=1, SECN=0, GUPOWERSHARE=FALSE; ADD GEXT3GCELL: EXT3GCELLID=120, EXT3GCELLNAME="120", MCC="460", MNC="10", LAC=10, CI=60, RNCID=0, DF=412, SCRAMBLE=0, DIVERSITY=NO, UTRANCELLTYPE=TDD, SYNCCASE=SyncCase1; ADD G3GNCELL: IDTYPE=BYID, SRC3GNCELLID=102, NBR3GNCELLID=120; SET GDSSPARA: IDTYPE=BYID, BTSID=102, DSSENABLE=YES; SET GTRXDEV: TRXID=1002, DSSTRXOFFLINE=YES; SET GTRXDEV: TRXID=1003, DSSTRXOFFLINE=YES; //Deactivation procedure MOD UNODEB: NodeBId=1, DSSFlag=FALSE; SET GDSSPARA: IDTYPE=BYID, BTSID=102, DSSENABLE=NO; SET GDSSPARA: IDTYPE=BYID, BTSID=1002, DSSENABLE=NO; SET GDSSPARA: IDTYPE=BYID, BTSID=1003, DSSENABLE=NO; HO UCELL: CellId=102, CellChoice=ALLCELL; DEA UCELL: CellId=102; RMV UNRELATION: RNCId=0, CellId=102, NCellType=IntraFreqNCell&InterFreqNCell&InterRatNCell;
270-4
Issue 02 (2011-07-11)
271 Configuring IP-Based Multi-Mode Co-Transmission on Base Station Side (NodeB)
Co-Transmission on Base Station Side (NodeB)

About This Chapter
This section describes how to activate, verify, and deactivate the optional feature MRFD-221501 IP-Based Multi-Mode Co-Transmission on Base Station Side. 271.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. 271.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.
271
Configuring IP-Based Multi-Mode
Issue 02 (2011-07-11)
271-1
271.1 Configuring IP-Based GSM and UMTS CoTransmission 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
l Dependencies on Hardware A GSM and UMTS dual-mode base station supports this feature. A UTRP board needs to be added when co-transmission is implemented on a GE port. A UTRP9 board needs to be added when co-transmission is implemented on a GE electrical port. A UTRP2 board needs to be added when co-transmission is implemented on a GE optical port. l Dependencies on Other Features GBFD-118601 Abis over IP GBFD-118611 Abis IP over E1/T1 WRFD-050402 IP Transmission Introduction on Iub Interface l License The license controlling this feature has been activated.
Context
The feature requires a GSM and UMTS dual-mode base station to connect the FE port on the GTMU and one FE port on the WMPT together and to share transmission ports on the UMTS side and the transmission network, therefore sharing transmission resources.
NOTE
In the scenario of GSM and UMTS co-transmission, it is recommended transmission resource sharing is achieved by connecting FE ports.
Co-transmission modes can be IP over FE/GE and IP over E1/T1, as shown in Figure 271-1, Figure 271-2, and Figure 271-3. Figure 271-1 IP-over-FE GSM and UMTS co-transmission on base station side
271-2
Issue 02 (2011-07-11)
Figure 271-2 IP-over-E1/T1 GSM and UMTS co-transmission on base station side
Figure 271-3 IP-over-GE GSM and UMTS co-transmission on base station side
IP PLAN Table 271-1 IP Planning of connecting between BTS and BSC Parameter BSC IP IP of FE interface on BTS IP of BTS route IP of BSC route Example 17.0.0.17 199.2.2.1 199.2.2.3 17.0.0.13
Table 271-2 IP Planning of connecting between NodeB and RNC (IP over FE/GE) Parameter IP of FE interface on NodeB IP of BSC IP of NodeB route
Issue 02 (2011-07-11)
Example 199.2.2.2 17.0.0.17 70.20.3.51

271-3
Parameter communication IP of IUB interface IP of BTS route IP of RNC route DHCP Server IP
Example 70.20.3.50 199.2.2.3 17.0.0.13 17.0.0.17
Table 271-3 IP planning of connection between NodeB and RNC (IP over E1/T1) Parameter IP of FE interface on NodeB IP of NodeB MP GROUP IP of RNC route IP of NodeB route DHCP Server IP Example 199.2.2.2 70.83.26.1 17.0.0.13 70.83.26.10 17.0.0.17
Procedure
l Procedure for Activating the BTS Data 1. 2. 3. Run the BSC6900 MML command ADD BTSESN to add the ESN of the GBTS. Run the BSC6900 MML command SET BTSIP to set the IP address of the GBTS. Run the BSC6900 MML command ADD BTSDEVIP to add an IP address to 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. Set Destination IP Address to the gateway IP address of the BSC6900. Set Route Type to NEXTHOP(IP Address of The Next Hop). Set Forward Route Address to the IP address of the port connected to the network on the GBTS side. 5. Run the BSC6900 MML command ADD IPRT to add an IP route from the BSC6900 to the GBTS. Set Destination IP Address to the gateway IP address of FE interconnection port on the GBTS side. Set Next Hop IP Address to the IP of BSC6900 gateway. l Activating the NodeB data (IP over FE/GE) 1. 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.
4.
271-4
2. 3. 4.
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 DEVIP to add a device IP address. In this step, set IP Address to an IP address in the network segment of BTS. 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.
5.
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 3. Set Peer IP Address to the IP address of the port on the BSC6900 side. Run the BSC6900 MML command LST SCTPSRVPORT to query the value of Peer SCTP Port.
6. 7.
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
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.
8.
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 number of the cabinet, subrack, and slot that house the Iub interface board. Set Rx Bandwidth and Tx Bandwidth to the same values as Rx Bandwidth and Tx Bandwidth of the corresponding IP path on the BSC6900 side.
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.
10. 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. l Activating the NodeB data (IP over E1/T1) 1. 2. 3. 4. 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 MPGRP to add an MP group (This operation is performed when E1/T1 transmission is used on the base station side). Run the NodeB MML command ADD MPLNK to add an MP link to the MP group when E1/T1 transmission is used on the base station side.
Issue 02 (2011-07-11)
271-5

NOTE
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.
5.
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.
6.
7. 8.
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
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.
9.
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 number of the cabinet, subrack, and slot that house the Iub interface board. Set Rx Bandwidth and Tx Bandwidth to the same values as Rx Bandwidth and Tx Bandwidth of the corresponding IP path on the BSC6900 side.
10. 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. 11. 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. ----End
Example
//Activating the GBTS data //Add the ESN of the BTS ADD BTSESN: IDTYPE=BYID, BTSID=2000, MAINDEVTAB="020GKV1083000212"; //Setting the BTS IP address SET BTSIP:BTSID=2000, IDTYPE=BYID, BSCIP="17.0.0.17", BTSIP="199.2.2.1", BTSCOMTYPE=PORTIP, HOSTTYPE=SINGLEHOST, CFGFLAG=NULL; //Setting the IP address of the FE interconnection port on the BTS side ADD BTSDEVIP: IDTYPE=BYID, BTSID=2000, PN=1, CN=0, SRN=0, SN=6,
271-6
Issue 02 (2011-07-11)
IP="199.2.2.1", MASK="255.255.255.0"; //Adding an IP route from the BTS to the BSC6900 ADD BTSIPRT:RTIDX=0, BTSID=2000, IDTYPE=BYID, PRI=60, DSTIP="17.0.0.10", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="199.2.2.3"; //Adding an IP route from the BSC6900 to the BTS(If the IP route has been added, skip this step): ADD IPRT:DSTIP="199.2.2.3", DSTMASK="255.255.255.255", NEXTHOP="17.0.0.10", SRN=0, SN=17, REMARK="0", PRIORITY=HIGH; //NodeB IP over FE/GE //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=1, IP="199.2.2.2", MASK="255.255.255.0"; ADD DEVIP: SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="70.20.3.50", MASK="255.255.255.0"; //Adding an IP route from the NodeB to the RNC ADD IPRT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, DSTIP="17.0.0.17", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="70.20.3.51", PREF=80; //Adding an SCTP signaling link ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=7, LOCIP="70.20.3.50", LOCPORT=1024, PEERIP="17.0.0.17", PEERPORT=58080; ADD SCTPLNK: SCTPNO=1, CN=0, SRN=0, SN=7, LOCIP="70.20.3.50", LOCPORT=1025, PEERIP="17.0.0.17", PEERPORT=58080; //Adding an NCP link ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=0; //Adding a UCP 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, LOCALIP="70.20.3.50", PEERIP="17.0.0.17", DSCP=46, 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, LOCALIP="70.20.3.50", PEERIP="17.0.0.17", DSCP=38, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=2, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, LOCALIP="70.20.3.50", PEERIP="17.0.0.17", DSCP=18, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=3, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, LOCALIP="70.20.3.50", PEERIP="17.0.0.17", DSCP=14, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; //Enabling the DHCP relay function of the base station SET DHCPRELAYSWITCH: ES=ENABLE; ADD DHCPSVRIP: DHCPSVRIP="17.0.0.17"; //Activating the NodeB data (IP over E1/T1) //Adding an IP address for the FE interconnection port on the NodeB side ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=MPGRP, PN=1, IP="199.2.2.2", MASK="255.255.255.0"; //Adding an MP group ADD MPGRP: SN=7, SBT=BASE_BOARD, MPGRPN=0, AUTH=NONAUTH, LOCALIP="70.83.26.1", IPMASK="255.0.0.0", PEERIP="70.83.26.10", MCPPP=DISABLE; //Adding an MP link and then adding it to the MP group ADD MPLNK: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PPPLNKN=0, E1T1SN=0, E1T1SBT=E1_COVERBOARD, E1T1PN=0, TSN=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&T S12-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 route from the NodeB to the RNC ADD IPRT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, DSTIP="17.0.0.13",
Issue 02 (2011-07-11)
271-7
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=MPGRP; //Adding an SCTP signaling link ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=7, LOCIP="70.83.26.10", LOCPORT=1024, PEERIP="17.0.0.13", PEERPORT=58080; ADD SCTPLNK: SCTPNO=1, CN=0, SRN=0, SN=7, LOCIP="70.83.26.10", LOCPORT=1025, PEERIP="17.0.0.13", PEERPORT=58080; //Adding an NCP link ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=0; //Adding a UCP 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, LOCALIP="70.83.26.10", PEERIP="17.0.0.13", DSCP=46, 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, LOCALIP="70.83.26.10", PEERIP="17.0.0.13", DSCP=38, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=2, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, LOCALIP="70.83.26.10", PEERIP="17.0.0.13", DSCP=18, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=3, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, LOCALIP="70.83.26.10", PEERIP="17.0.0.13", DSCP=14, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; //Enabling the DHCP relay function of the base station SET DHCPRELAYSWITCH: ES=ENABLE; ADD DHCPSVRIP: DHCPSVRIP="17.0.0.17";
271.2 Configuring IP-Based UMTS and LTE CoTransmission 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 Dependencies 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 Dependencies on Other Features WRFD-050402 IP Transmission Introduction on Iub Interface MRFD-221601 Multi-Mode BS Common Reference Clock (NodeB) l License The license controlling this feature has been 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, it is recommended transmission resource sharing is achieved by connecting FE ports.
Co-transmission modes can be IP over FE/GE and IP over E1/T1, as shown in Figure 271-4 and Figure 271-5 respectively. Figure 271-4 IP over FE/GE UMTS and LTE co-transmission on base station side
Figure 271-5 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.
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 an 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.
Activating the eNodeB data (IP over FE/GE) 1. Run the eNodeB MML command SET ETHPORT to set parameters for the LMPT port connected to the WMPT.
NOTE
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.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the SGW.
271-10
5. 6. 7.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the BSC6900. Run the eNodeB MML command ADD RSCGRP to add a transmission resource 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.
8. 9.
Run the eNodeB MML command SET DHCPRELAYSWITCH to enable the DHCP relay function of the base station. In this step, set Enable Switch to ENABLE. Run the eNodeB 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.
10. Run the eNodeB MML command ADD SCTPLNK to add a signaling link between the eNodeB and the MME. 11. Run the eNodeB MML command ADD S1INTERFACE to add an S1 interface. l Activating the eNodeB data (IP over E1/T1) 1. Run the eNodeB MML command SET ETHPORT to set parameters for the LMPT port connected to the WMPT.
NOTE
When the WMPT is connected to the LMPT, the LMPT must be configured to work in 100M/ FULL mode.
2. 3. 4. 5.
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 the IP address of FE interface on eNodeB. 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 Subboard Type to E1_COVERBOARD(E1 Cover Board) Set Route Type to IF(Exit Interface).
6. 7. 8. 9.
Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the SGW. Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to the BSC6900. Run the eNodeB MML command ADD RSCGRP to add a transmission resource 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.
Issue 02 (2011-07-11)
271-11
Run the eNodeB MML command SET DHCPRELAYSWITCH to enable the DHCP relay function of the base station. In this step, set Enable Switch to ENABLE. Run the eNodeB 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. 10. Run the eNodeB MML command ADD SCTPLNK to add a signaling link between the eNodeB and the MME. 11. Run the eNodeB MML command ADD S1INTERFACE to add an S1 interface. ----End
Example
//Activating the NodeB data //Setting parameters for an Ethernet port SET ETHPORT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=DISABLE, OAM3AHSW=DISABLE; //Set the IP of FE interface on NodeB ADD DEVIP: SRN=0, SN=6, 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=6,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=6, LOCIP="199.2.2.2", LOCPORT=1024, PEERIP="17.0.0.17", PEERPORT=58080; ADD SCTPLNK: SCTPNO=1, CN=0, SRN=0, SN=6, LOCIP="199.2.2.2", LOCPORT=1025, PEERIP="17.0.0.17", PEERPORT=58080; //Adding an 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=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, LOCALIP="199.2.2.2", PEERIP="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=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, LOCALIP="199.2.2.2", PEERIP="17.0.0.17", DSCP=0, RXBW=10000, TXBW=10000, TXCBS=15000, TXEBS=155000000, FPMUXSWITCH=DISABLE; //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=7, PN=0, PA=COPPER, MTU=1500, SPEED=100M, DUPLEX=FULL, FC=OPEN; //Set the IP of FE interface on eNodeB ADD DEVIP: CN=0, SRN=0, SN=7, PT=ETH, PN=1, IP="199.2.2.20", MASK="255.0.0.0"; //Adding an IP address for the eNodeB ADD DEVIP: CN=0, SRN=0, SN=7, 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=7,DSTIP="138.20.5.0",MASK="255.255.255.0",RTTYPE=NEXTH OP,NEXTHOPIP="199.2.2.20",PREF=80; //Adding an IP route from the eNodeB to the SGW
271-12
Issue 02 (2011-07-11)
ADD IPRT:CN=0,SRN=0,SN=7,DSTIP="138.30.20.0",MASK="255.255.255.0",RTTYPE=NEXT HOP,NEXTHOPIP="199.2.2.20",PREF=80; //Adding an IP route from eNodeB to BSC6900 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.20",PREF=80; //Adding a transmission resource group ADD RSCGRP: CN=0, SRN=0, SN=7, BEAR=IP, SBT=BASE_BOARD, PT=MPGRP, PN=0, RSCGRPID=0, RU=KBPS, TXBW=150000, RXBW=200000, TXCBS=200000, TXEBS=200000; //Adding an IP path between the eNodeB and the SGW ADD IPPATH: PATHID=0, SN=7, JNLGCPORT=YES, LPN=0, LOCALIP="70.83.26.1", PEERIP="138.20.5.20", QT=HQ, PATHTYPE=ANY; //Enabling the DHCP relay function of the base station SET DHCPRELAYSWITCH: EnableSwitch=ENABLE; ADD DHCPSVRIP: DHCPSVRIP="17.0.0.17"; //Adding a signaling link between the eNodeB and the MME ADD SCTPLNK: SCTPNO=0, SN=7, LOCIP="70.83.26.1", LOCPORT=2907, PEERIP="138.20.5.0", 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=4, PN=0, PA=COPPER, MTU=1500, SPEED=100M, DUPLEX=FULL, FC=OPEN; //Adding an MP group ADD MPGRP: CN=0, SRN=0, SN=4, MPGRPN=0, MCPPP=DISABLE, AUTHTYPE=NOAUTH, 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=4, PPPLNKN=0, E1T1SN=0, E1T1PN=0, TSBITMAP=TSBITMAP=TS1-1&TS2-1;&TS3-1;&TS4-1;&TS5-1;&TS6-1;&TS7-1;&TS8-1;& TS9-1;&TS10-1;&TS11-1;&TS12-1;&TS13-1;&TS14-1;&TS15-1;&TS16-1;&TS17-1;&TS 18-1;&TS19-1;&TS20-1;&TS21-1;&TS22-1;&TS23-1;&TS24-1;&TS25-1;&TS26-1;&TS2 7-1;&TS28-1;&TS29-1;&TS30-1;&TS31-1; //Set the IP of FE interface on eNodeB ADD DEVIP: CN=0, SRN=0, SN=4, PT=MP, PN=1, IP="199.2.2.20", MASK="255.0.0.0"; //Adding an IP route from the eNodeB to the MME ADD IPRT: CN=0, SRN=0, SN=4, DSTIP="138.20.5.0", MASK="255.255.255.0", RTTYPE=IF, PT=MP, PN=0; //Adding an IP route from the eNodeB to the SGW ADD IPRT: CN=0, SRN=0, SN=4, DSTIP="138.30.20.0", MASK="255.255.255.0", RTTYPE=IF, PT=MP, PN=1; //Add an IP route from eNodeB to BSC6900 ADD IPRT: CN=0, SRN=0, SN=4, DSTIP="17.0.0.17", MASK="255.255.255.0", RTTYPE=IF, PT=MP, PN=2; //Adding an IP logical port ADD IPLGCPORT: CN=0, SRN=0, SN=4, 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=4, JNLGCPORT=YES, LPN=0, LOCALIP="70.83.26.1", PEERIP="138.20.5.20", QT=HQ, PATHTYPE=ANY; //Enabling the DHCP relay function of the base station SET DHCPRELAYSWITCH: ES=ENABLE; ADD DHCPSVRIP: DHCPSVRIP="17.0.0.17"; //Adding a signaling link between the eNodeB and the MME ADD SCTPLNK: SCTPNO=0, SN=4, LOCIP="70.83.26.1", LOCPORT=2907, PEERIP="138.20.5.0", PEERPORT=2910, SWITCHBACKFLAG=YES; //Adding an S1 interface ADD S1INTERFACE: S1INTERFACEID=0, S1SCTPLINKID=0, CnOperatorId=0;
Issue 02 (2011-07-11)
271-13
272 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side (NodeB)
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).
272
l
Configuring TDM-Based Multi-
Prerequisite
Dependencies on Hardware A GSM and UMTS dual-mode base station supports this feature. When the TDM timeslot cross connection co-transmission feature is supported by a GSM and UMTS dual-mode base station, a UTRP should be configured for the BTS. The UTRP type must be UTRP3, UTRP4, or UTRPb4. l Dependencies on Other Features WRFD-050302 Fractional ATM Function on Iub Interface WRFD-050411 Fractional IP Function on Iub Interface l License The license controlling this feature has been 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: l In the scenario of GTMU-based TDM timeslot cross connection co-transmission, E1/T1 timeslots on the UMTS side are transmitted to the GTMU through the backplane TOP channel on the WMPT. E1/T1 ports on the GTMU are connected to the transmission network. The TDM timeslot cross connection function enables GSM data and UMTS data to be multiplexed on the transmission network. Therefore, E1/T1 transmission resources are shared by the GSM and UMTS modes by timeslot, as shown in Figure 272-1.
Issue 02 (2011-07-11)
272-1
Figure 272-1 GTMU-based TDM timeslot cross connection co-transmission
In the scenario of GSM-UTRP-based TDM timeslot cross connection co-transmission, a UTRP is configured on the GSM side. Therefore, extra E1/T1 resources can be shared by the UMTS mode through the backplane TOP channel to extend E1/T1 transmission resources for the UMTS mode, as shown in Figure 272-2.
NOTE
l The number of E1/T1 on the BTS backplane is within the range of 16 through 19. E1/T1 numbers 16 through 19 on the BTS backplane correspond to E1/T1 numbers 0 through 3 on the NodeB backplane. Cross connection is not supported. For example, E1/T1 No. 16 on the BTS backplane only corresponds to E1/T1 No. 0 on the NodeB backplane. l E1 timeslot numbers configured on the BTS side must be consistent with those configured on the NodeB side.
Figure 272-2 GSM-UTRP-based TDM timeslot cross connection co-transmission
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.
272-2
Set Port Subrack No. and Port Slot No. to numbers of the subrack and slot where the BTS port connected to the NodeB interface board is located. Set TOP Board Subrack No. and TOP Board Slot No. to numbers of the subrack and slot where the NodeB interface board is located. Set Port Type to TOPEXTOUTPORT. Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to TOPEXTOUTPORT.
Activating the NodeB data (GTMU-based) 1. Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link. Set Subrack No. and Slot No. to numbers of the subrack and slot that house the Iub interface board. Set Subboard Type to BACK_BOARD. Set Destination Slot No. to the number of the slot that houses the GTMU.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It, however, does not support the configuration of the operating work mode and loopback mode, and online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/ FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual networking mode.
2. 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. 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).
Issue 02 (2011-07-11)
272-3

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). 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.
272-4
Issue 02 (2011-07-11)
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 an NCP or CCP link ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5; ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6; //Activating the BTS data (GSM-UTRP-based) //Configuring a connection between a UTRP port and the NodeB ADD BTSCONNECT: IDTYPE=BYID, BTSID=255, INPN=1, INCN=0, INSRN=0, INSN=0, DESTNODE=OTHER; //Configuring the TOP switching relation between the UTRP and the WMPT: E1 port 16 on the backplane corresponds to port 0 on the WMPT, the UTRP provides the WMPT with a transmission path, the port type is TOPEXTINPO, and the output port is E1 port 1 on the UTRP
Issue 02 (2011-07-11)
272-5
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 an NCP or CCP link ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5; ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6;
272-6
Issue 02 (2011-07-11)
273 Configuring Multi-Mode BS Common Reference Clock (NodeB)
273
About This Chapter
Configuring Multi-Mode BS
Common Reference Clock (NodeB)
This section describes how to activate, verify, and deactivate the optional feature MRFD-221601 Multi-Mode BS Common Reference Clock (NodeB). 273.1 Configuring GSM and UMTS Common Reference Clock This section describes how to activate, verify, and deactivate the optional feature GSM and UMTS Common Reference Clock. 273.2 Configuring UMTS and LTE Common Reference Clock This section describes how to activate, verify, and deactivate the optional feature UMTS and LTE Common Reference Clock.
Issue 02 (2011-07-11)
273-1
273.1 Configuring GSM and UMTS Common Reference Clock

This section describes how to activate, verify, and deactivate the optional feature GSM and UMTS Common Reference Clock.
Prerequisite
l Dependencies on Hardware The GSM and UMTS dual-mode base station whose GSM and UMTS modes share the BBU supports this feature. If GPS or BITS clock signals are shared, the USCU board must be configured on the BBU. l Dependencies on Other Features MRFD-210501 BTS/NodeB Clock WRFD-050502 Synchronous Ethernet GBFD-118601 Abis over IP WRFD-050402 IP Transmission Introduction on Iub Interface WRFD-050501 Clock Sync on Ethernet in NodeB l l License The license controlling this feature has been activated. Other Prerequisites This feature has to be activated with MRFD-221601 Multi-mode BS Common Reference Clock (NodeB) simultaneously.
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)
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)
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 273-1. Figure 273-1 Common GPS reference clock
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 273-2.
Issue 02 (2011-07-11)
273-3
Figure 273-2 Common BITS reference clock
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 273-3 and Figure 273-4. Figure 273-3 Common E1/T1 reference clock on the GSM side (GTMU)
Figure 273-4 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 273-5. Figure 273-5 Common Ethernet reference clock on the UMTS side (WMPT)
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 273-6. Figure 273-6 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 to set the parameters of a USCU board.
Set Board Parameter Configuration Enabled to YES(YES). Set GPS Work Mode to GPS(GPS). Set Antenna Power Supply Switch to NOPOWER(No Power). (2) Run the BSC6900 MML command SET BTSCLK to set Clock Type to TRCGPS_CLK(Trace GPS Clock). (3) Run the BSC6900 MML command SET BTSCLKPARA to set BTS clock parameters based on the actual situation. (4) Run the BSC6900 MML command SAV BTSCLKPARA to save BTS clock parameters. 2. Configuration on the NodeB side (1) Run the NodeB MML command ADD GPS to add a GPS clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to GPS(GPS Clock). l Common BITS reference clock 1. 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 EXTSYN_CLK(External Sync clock). 2. Configuration on the NodeB side (1) Run the NodeB MML command ADD BITS to add a BITS clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to BITS(BITS Clock). 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 BSC6900. In this step, set Clock Type to TRCBSC_CLK (Trace BSC Clock). 2. Configuration on the NodeB side
NOTE
Before configuring on the NodeB side, ensure that the clock source on the GBTS side is E1/ T1 clock link.
(1) Run the NodeB MML command ADD PEERCLK to add a peer reference clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to PEERCLK(Peer Clock). l Common E1/T1 reference clock on the UMTS side (WMPT) 1.
273-6
Configuration on the NodeB side


NOTE
Before configuring the LINE clock source, ensure that an E1/T1 clock link is available.
(1) Run the NodeB MML command ADD LINECLK to configure the E1/T1 clock source. In this step, set Port Type to E1T1(E1T1). (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to LINECLK(Line Clock). 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). l Common Ethernet reference clock on the UMTS side 1. Configuration on the NodeB side (1) Run the NodeB MML command ADD SYNCETH to add a synchronousEthernet clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to SYNCETH(SyncEth Clock). 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_CLK(Peer Clock). l Common IP reference clock on the UMTS side 1. Configuration on the NodeB side (1) Run the NodeB MML command ADD IPCLKLINK to add an IP clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to IPCLK(IP Clock). 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_CLK(Peer Clock). l Verification Procedure 1. Run the NodeB MML command DSP CLKSTAT and the BSC6900 MML command LST BTSCLK. Check the results. If... The clock source information matches the configuration. The clock source information mismatches the configuration. Then... The configuration succeeds. The configuration fails.
Issue 02 (2011-07-11)
273-7
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.
----End
Example
//Common GPS reference clock //Configuration on the GBTS side SET BTSUSCUBP: IDTYPE=BYID, BTSID=120, SRN=0, SN=1, CFGFLAG=YES, GPSORGLONASS=GPS, ANTENNAPOWERSWITCH=NOPOWER; SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=TRCGPS_CLK; SET BTSCLKPARA: IDTYPE=BYID, BTSID=120, SRN=0, SN=1, CLKMOD=GPSCLK, TRCRNGLMT=ENABLE, CALVAL=2222; SAV BTSCLKPARA: IDTYPE=BYID, BTSID=120; //Configuration on the NodeB side ADD GPS: GN=0,SN=4; SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; //Common BITS reference clock //Configuration on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=EXTSYN_CLK; //Configuration on the NodeB side ADD BITS: SN=4; SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Common E1/T1 reference clock on the GBTS side (GTMU) //Configuration on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=TRCBSC_CLK; //Configuration on the NodeB side ADD PEERCLK:; SET CLKMODE: MODE=MANUAL, CLKSRC=PEERCLK; //Common E1/T1 reference clock on the UMTS side (WMPT) //Configuration on the NodeB side ADD LINECLK: SN=6, PT=E1T1, PN=0; SET CLKMODE: MODE=MANUAL, CLKSRC=LINE; //Configuration on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=PEER_CLK; //Common Ethernet reference clock on the UMTS side //Configuration on the NodeB side ADD SYNCETH: SN=7, PN=0; SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH; //Configuration on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=PEER_CLK; //Common IP reference clock on the UMTS side //Configuration on the NodeB side ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="82.0.1.107", SIP="82.0.1.128"; SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK; //Configuration on the GBTS side SET BTSCLK: IDTYPE=BYID, BTSID=120, ClkType=PEER_CLK;
273-8
Issue 02 (2011-07-11)
273.2 Configuring UMTS and LTE Common Reference Clock

This section describes how to activate, verify, and deactivate the optional feature UMTS and LTE Common Reference Clock.
Prerequisite
l Dependencies on Hardware The UMTS and LTE dual-mode base station whose UMTS and LTE modes share the BBU supports this feature. If GPS or BITS clock signals are shared, the USCU board must be configured on the BBU. The 1588V2 reference clock must be configured IP Clock Server. l Dependencies on Other Features MRFD-210501 BTS/NodeB Clock LOFD-00301301 Synchronization with Ethernet (ITU-T G.8261) WRFD-050402 IP Transmission Introduction on Iub Interface LOFD-00301302 IEEE1588 V2 Clock Synchronization l l License The license controlling this feature has been activated. Other Prerequisites This feature has to be activated with MRFD-231601 Multi-mode BS Common Reference Clock (eNodeB) simultaneously.
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)
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)
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 273-7. Figure 273-7 Common GPS reference clock
NOTE
As shown in Figure 273-7, 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 273-8.
Figure 273-8 Common BITS reference clock
NOTE
As shown in Figure 273-8, 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 273-9. Figure 273-9 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 273-10.
Issue 02 (2011-07-11)
273-11
Figure 273-10 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 273-11. Figure 273-11 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 ADD GPS to add a GPS clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to GPS(GPS Clock). 2.
273-12
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 to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to GPS(GPS Clock). l Common BITS reference clock 1. Configuration on the NodeB side (1) Run the NodeB MML command ADD BITS to add a BITS clock link. (2) Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to BITS(BITS Clock). 2. Configuration on the eNodeB side (1) Run the eNodeB MML command ADD BITS to add a BITS 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 to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to BITS(BITS Clock). l Common E1/T1 reference clock on the UMTS side 1. Configuration on the NodeB side
NOTE
Before configuring the LINE clock source, ensure that an E1/T1 clock link is available.
(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 set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to LINECLK(Line Clock). 2. Configuration on the eNodeB side
NOTE
Before configuring on the eNodeB side, ensure that the clock source on the NodeB side is E1/ T1 clock link.
(1) Run the eNodeB MML command ADD PEERCLK to add a peer reference clock link. In this step, set PeerClk No. to the number of the peer reference clock. (2) Run the eNodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to PEERCLK(Peer Clock). l Common Ethernet reference clock on the LTE side 1.
Issue 02 (2011-07-11)
Configuration on the eNodeB side

(1) Run the eNodeB MML command ADD SYNCETH to add a synchronousEthernet clock link. 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 to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to SYNCETH(SyncEth Clock). 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to PEERCLK(Peer Clock). l Common IP reference clock on the LTE side 1. Configuration on the eNodeB side (1) Run the eNodeB MML command ADD IPCLKLINK 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 to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to IPCLK(IP Clock). 2. Configuration on the NodeB side Run the NodeB MML command SET CLKMODE to set the working mode of the reference clock source. Set Clock Working Mode to MANUAL(Manual). Set Selected Clock Source to PEERCLK(Peer Clock). 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 mismatches the configuration. 2.
273-14
Then... The configuration succeeds. The configuration fails.
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 //Configuration on the NodeB side ADD GPS: SN=4; SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; //Configuration on the eNodeB side ADD GPS: SN=4; SET CLKMODE: MODE=MANUAL, CLKSRC=GPS, SRCNO=0; //Common BITS reference clock //Configuration on the NodeB side ADD BITS: SN=4; SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Configuration on the eNodeB side ADD BITS: SN=4; SET CLKMODE: MODE=MANUAL, CLKSRC=BITS; //Common UMTS E1/T1 reference clock //Configuration on the NodeB side ADD LINECLK: SN=6, PT=E1T1, PN=0; SET CLKMODE: MODE=MANUAL, CLKSRC=LINECLK; //Configuration on the eNodeB side ADD PEERCLK:; SET CLKMODE: MODE=MANUAL, CLKSRC=PEERCLK; //Common Ethernet reference clock on the LTE side //Configuration on the eNodeB side ADD SYNCETH: SN=7, PN=0; SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH; //Configuration on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=PEERCLK; //Common IP reference clock on the LTE side //Configuration on the eNodeB side ADD IPCLKLINK: ICPT=PTP, SN=7, PN=0, CNM=UNICAST, CIP="82.0.1.107", SIP="82.0.1.128", SYNMODE=OFF; SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SRCNO=0; //Configuration on the NodeB side SET CLKMODE: MODE=MANUAL, CLKSRC=PEERCLK;
Issue 02 (2011-07-11)
273-15
274 Configuring 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (UMTS)
Frequency Point Separation Between GSM and UMTS Mode (UMTS)

This section describes how to activate, verify, and deactivate the optional feature MRFD-221703 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (UMTS).
274
l l
Configuring 2.0 MHz Central
Prerequisite
Dependencies on Hardware MRFU and RRU3908 of V2 or later versions support the feature. Dependencies on Other Features GBFD-114801 Discontinuous Transmission (DTX) Downlink GBFD-117601 HUAWEI III Power Control Algorithm GBFD-117602 Active Power Control MRFD-211703 2.0 MHz Central Frequency Point Separation Between GSM and UMTS Mode (GSM) l l License The license controlling this feature has been activated. Other Prerequisites GSM and UMTS Dynamic Power Sharing is not supported in GSM dynamic transmit diversity. It is not recommended that GSM and UMTS Dynamic Power Sharing coexist with the baseband frequency hopping algorithm involving two power amplifiers because their coexistence would result in a certain level of performance loss. GSM and UMTS Dynamic Power Sharing in MIMO is not recommended.
Context
This feature improves frequency utilization. It enables the UMTS carriers to use the bandwidth 3.8 MHz and therefore increase the capacity of the GSM network.
Procedure
l Activation Procedure 1. 2. Run the NodeB MML command SET FREQBWH to set the minimal frequency bandwidth on the UMTS side. In this step, set Frequency Min Bandwidth to 3800. To ensure that the UMTS carrier bandwidth is 3.8 MHz and the frequency spacing between GSM and UMTS carriers is 2.0 MHz, as set in step 1, do as follows to modify frequency points on the GSM or UMTS side: Modify the UMTS carrier Central Frequency Point (1) Run the BSC6900 MML command DEA UCELL to deactivate a cell. (2) Run the BSC6900 MML command MOD UCELLSETUP. In this step, modify frequency points for UMTS cells at the BSC6900. Set Band Indicator, UL Frequency Ind, Uplink UARFCN and Downlink UARFCN. (3) Run the NodeB MML command MOD LOCELL to modify some properties of a local cell. In this step, set UL Frequency Channel Number and DL Frequency Channel Number. (4) Run the BSC6900 MML command ACT UCELL to activate a cell. Modify the GSM central frequency point separation (1) Run the BSC6900 MML command MOD GTRX to modify the frequency of a TRX. In this step, set Frequency to ensure that the frequency spacing between GSM and UMTS carriers is 2.0 MHz. l Verification Procedure 1. 2. 3. l Run the NodeB MML command LST FREQBWH to check whether the UMTS carrier bandwidth is 3.8 MHz. Check on the NodeB side whether all TRXs work properly when the frequency spacing between GSM and UMTS carriers is 2.0 MHz. Check on the BSC side whether services in all cells are normal when the frequency spacing between GSM and UMTS carriers is 2.0 MHz. Run the NodeB MML command SET FREQBWH to set the UMTS carrier bandwidth. The UMTS carrier bandwidth should range from 4.2 MHz to 5.0 MHz. To ensure that the UMTS carrier bandwidth is the bandwidth set in step 1, do as follows to modify frequency points on the GSM or UMTS side: Modify the UMTS central frequency point separation (1) Run the BSC6900 MML command DEA UCELL to deactivate a cell. (2) Run the BSC6900 MML command MOD UCELLSETUP. In this step, modify frequency points for UMTS cells at the BSC6900 and set Band Indicator, UL Frequency Ind and Downlink UARFCN. (3) Run the NodeB MML command MOD LOCELL to modify some properties of a local cell. In this step, set UL Frequency Channel Number and DL Frequency Channel Number. (4) Run the BSC6900 MML command ACT UCELL to activate a cell. Modify the GSM central frequency point separation
(1) Run the BSC6900 MML command MOD GTRX to modify the frequency of a TRX. In this step, set Frequency to ensure that the frequency spacing between GSM and UMTS carriers no less than 2.2 MHz. ----End
Example
//Activation procedure //Setting the UMTS carrier bandwidth to 3.8 MHz SET FREQBWH: CN=0, SRN=4, SN=0, FMBWH=3800; //Setting the uplink and downlink frequencies of a UMTS cell to 2815 and 3040 DEA UCELL: CellId=101; MOD UCELLSETUP: CellId=101, BandInd=Band8, UARFCNUplinkInd=FALSE, UARFCNDownlink=3040; MOD LOCELL: LOCELL=101, SECT=LOCAL_SECTOR, ULFREQ=2815, DLFREQ=3040; ACT UCELL: CellId=101; //Setting the frequency of a specified GSM TRX to 55 MOD GTRX: TRXID=122, FREQ=55; //Verification procedure LST FREQBWH: CN=0, SRN=4, SN=0; //Deactivation procedure //Setting the UMTS carrier bandwidth to 5.0 MHz SET FREQBWH: CN=0, SRN=4, SN=0, FMBWH=5000; //Setting the uplink and downlink frequencies of a UMTS cell to 2821 and 3046 DEA UCELL: CellId=101; MOD UCELLSETUP: CellId=101, BandInd=Band8, UARFCNUplinkInd=FALSE, UARFCNDownlink=3046; MOD LOCELL: LOCELL=101, SECT=LOCAL_SECTOR, ULFREQ=2821, DLFREQ=3046; ACT UCELL: CellId=101; //Setting the frequency of a specificed GSM TRX to 52 MOD GTRX: TRXID=122, FREQ=52;
Issue 02 (2011-07-11)
274-3

RAN Feature Activation Guide (V900R013C00 - 02) (PDF) - en

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RAN Feature Activation Guide (V900R013C00 - 02) (PDF) - en

Transféré par

Droits d'auteur :

Formats disponibles

RAN V900R013C00

Feature Activation Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

RAN Feature Activation Guide

About This Document

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

RAN Feature Activation Guide

About This Document

About This Document

RAN Feature Activation Guide

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

RAN Feature Activation Guide

About This Document

Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }*

About This Document

RAN Feature Activation Guide

Action Click Double-click Drag