Académique Documents
Professionnel Documents
Culture Documents
V900R013C00
Issue 02
Date 2011-07-11
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.
Website: http://www.huawei.com
Email: support@huawei.com
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.
BSC6900 V900R013C00
NodeB V100R013
NodeB V200R013
Intended Audience
This document is intended for:
l Technical support engineers
l Maintenance engineers
l Field engineers
l Network optimization engineers
Organization
1 Changes in the RAN Feature Activation Guide
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 license-
controlled 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)
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020108
Code Resource Management.
This section describes how to activate, verify, and deactivate the basic feature WRFD-021301
Shared Network Support in Connected Mode.
This section describes how to activate, verify, and deactivate the basic feature WRFD-020201
Intra NodeB Softer Handover.
This section describes how to activate, verify, and deactivate the basic feature WRFD-020202
Intra RNC Soft Handover.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020203
Inter RNC Soft Handover.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020301
Intra Frequency Hard Handover.
This section describes how to activate, verify, and deactivate the basic feature WRFD-010801
Intra RNC Cell Update.
This section describes how to activate, verify, and deactivate the basic feature WRFD-010802
Inter RNC Cell Update.
This section describes how to activate, verify, and deactivate the basic feature WRFD-010901
Intra RNC URA Update.
This section describes how to activate, verify, and deactivate the basic feature WRFD-010902
Inter RNC URA Update.
This section describes how to activate, verify, and deactivate the basic feature WRFD-021400
Direct Signaling Connection Re-establishment (DSCR).
This section describes how to activate, verify, and deactivate the basic feature MRFD-210501
NodeB Clock.
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.
This section describes how to activate, verify, and deactivate the basic feature WRFD-031500
Solar Power Device Management.
This section describes how to activate, verify, and deactivate the basic feature MRFD-210601
Connection with TMA (Tower Mounted Amplifier).
This section describes how to activate, verify, and deactivate the basic feature MRFD-210602
Remote Electrical Tilt.
This section describes how to activate, verify, and deactivate the basic feature WRFD-060003
Configuring Same Band Antenna Sharing Unit (900 MHz).
This section describes how to activate, verify, and deactivate the optional feature WRFD-010615
Multiple RAB Package (PS RAB 2).
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061501 Combination of 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.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061503 Combination of 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.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061505 Combination of Four PS Services.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010610
HSDPA Introduction Package.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061001 15 Codes per Cell.
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
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.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061401 E-AGCH Power Control (Based on CQI or HS-SCCH).
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061403 HSUPA 2ms TTI.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061405 HSUPA 5.74Mbps per User.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010632
Streaming Traffic Class on HSUPA.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010634
60 HSUPA Users per Cell.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010635
HSUPA over Iur.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010636
SRB over HSUPA.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010641
HSUPA Adaptive Transmission.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010690
TTI Switch for BE Services Based on Coverage.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020138
HSUPA Coverage Enhancement at UE Power Limitation.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010712
Adaptive Configuration of Traffic Channel Power.
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010700
Performance Improvement of MIMO and HSDPA.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010704
Flexible HSPA+ Technology Selection.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010686
CPC - DTX /DRX.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010687
CPC-HS-SCCH Less operation.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010653
96 HSDPA Users per Cell.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010639
96 HSUPA Users per Cell.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010654
128 HSDPA Users per Cell.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010670
128 HSUPA Users per Cell.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010691
HSUPA UL Interference Cancellation.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020137
Dual-Threshold Scheduling with HSUPA Interference Cancellation.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020136
Anti-Interference Scheduling for HSUPA.
This section describes how to activate, verify, and deactivate the optional feature HSUPA
Frequency Domain Equalization.
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020135
Intelligent Inter-Carrier UE Layered Management.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020302
Inter Frequency Hard Handover Based on Coverage.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020304
Inter Frequency Hard Handover Based on DL QoS.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02060501 SRNS Relocation (UE Not Involved).
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02060502 SRNS Relocation with Hard Handover.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02060503 SRNS Relocation with Cell/URA Update.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020303
Inter-RAT Handover Based on Coverage.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020309
Inter-RAT Handover Based on DL QoS.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020307
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020308
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02030801 NACC(Network Assisted Cell Change).
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02030802 PS Handover between UMTS and GPRS.
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-021102
Cell Barring.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020310
3G/2G Common Load Management.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010506
RAB Quality of Service Renegotiation over Iu Interface.
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020123
TCP Accelerator.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020124
Uplink Flow Control of User Plane.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020130
Videophone Service Restriction.
This section describes how to activate, verify, and deactivate the optional feature WRFD-011502
Active Queue Management (AQM).
This section describes how to activate, verify, and deactivate the optional feature WRFD-020128
Quality Improvement for Subscribed Service.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020131
Optimization of R99 and HSUPA Users Fairness.
This section describes how to activate, verify, and deactivate the optional feature WRFD-011000
Cell Broadcast Service.
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.
This section describes how to activate, verify, and deactivate the basic feature WRFD-010618
IMS Signaling over HSPA.
This section describes how to activate, verify, and deactivate the optional feature WRFD-011501
PDCP Header Compression (RoHC).
This section describes how to activate, verify, and deactivate the optional feature WRFD-010619
CS Voice over HSPA/HSPA+.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020801
Cell ID + RTT Function Based LCS.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020802
OTDOA Based LCS.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020803
A-GPS Based LCS.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020804
LCS Classified Zone.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020805
Configuring LCS over Iur.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020807
Iupc Interface for LCS service.
This section describes how to activate, verify and deactivate the optional feature WRFD-021304
RAN Sharing Introduction Package.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02130401 Dedicated Carrier for Each Operator.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02130402 Flexible Network Architecture.
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-020160
Enhanced Multiband Management.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050104
Satellite Transmission on Iub Interface.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050108
Satellite Transmission on Iu Interface.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010616
MBMS Introduction Package.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061602 MBMS Admission Control.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061603 MBMS Load Control.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061605 MBMS Transport Resource Management.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061606 Streaming Service on MBMS.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061608 16/32/64/128Kbps Channel Rate on MBMS.
This section describes how to activate, verify, and deactivate the optional feature WRFD-010660
MBMS Phase 2.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01066001 MBMS Enhanced Broadcast Mode.
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01066002 MBMS P2P over HSDPA.
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.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050409
IP Transmission Introduction on Iu Interface.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050410
IP Transmission Introduction on Iur Interface.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050420
Configuring FP MUX for IP Transmission.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050422
Dynamic Bandwidth Control of Iub IP.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050408
Overbooking on IP Transmission.
This section describes how to activate, verify, and deactivate the feature WRFD-050412 UDP
MUX for Iu-CS Transmission.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050105
ATM Switching-Based Hub NodeB.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050106
AAL2 Switching-Based Hub NodeB.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050107
IP Routing-Based Hub NodeB.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050425
Ethernet OAM.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050501
Clock Synchronization on Ethernet in NodeB.
This section describes how to activate, verify, and deactivate the optional feature WRFD-050502
Synchronous Ethernet.
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
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).
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
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
274 Configuring 2.0 MHz Central Frequency Point Separation Between GSM and UMTS
Mode (UMTS)............................................................................................................................274-1
Figures
Tables
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:
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:
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:
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:
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.
RAN features are classified into basic and optional features. Basic features are not license-
controlled 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.
WRFD-05030110 F5 42 Configuring F5
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.
Prerequisite
l The LMT is started and you have logged in to the BSC6900.
l 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 does not comply with the Exit the task and contact Huawei.
information of the file that you apply for,
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 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 End the task and contact Huawei.
that on the OMU
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
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.
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
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.
----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.
This section describes how to activate, verify, and deactivate the basic feature WRFD-010510
3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
l Verification Procedure
1. Start Iub interface tracing on the BSC6900 LMT, as shown in Figure 4-1
2. Establish a service on the UE. Among the traced Iub data, view the dCH-ID in the
DCH-Specific-FDD-Item IE in the NBAP_RL_SETUP_REQ message. The result
shows that the ID of the transport channel that carries signaling is 32.
3. View the transmissionTimeInterval and nrOfTransportBlocks IEs in the ul-
TransportFormatSet IE associated with the DCH whose dCH-ID value is 32.
If the value of transmissionTimeInterval is 40, you can infer that an RRC
connection is established for a 3.4 kbit/s service.
If the value of transmissionTimeInterval is 20, you can infer that an RRC
connection is established for a 6.8 kbit/s service.
If the value of transmissionTimeInterval is 10 and the maximum value of
nrOfTransportBlocks is 1, you can infer that an RRC connection is established
for a 13.6 kbit/s service.
If the value of transmissionTimeInterval is 10 and the maximum value of
nrOfTransportBlocks is 2, you can infer that an RRC connection is established
for a 27.2 kbit/s service.
4. Release the service on the UE, and perform Uu interface tracing. If you find an
RRC_RRC_CONN_REL_CMP message in the traced data, you can infer that the
RRC connection is released.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
//Activating 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer
Establishment and Release.
//set the channel type and bit rate corresponding to a specific RRC
connection establishment cause
This section describes how to activate, verify, and deactivate the basic feature WRFD-010501
Conversational QoS Class.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Others
The UE and the CN support the conversational class.
Context
Based on QoS requirements, 3GPP defines four traffic classes: conversational, streaming,
interactive, and background.
They differ in their sensitivity to delay. The conversational class is highly sensitive to the delay
and therefore has a high requirement on real-time transmission. The conversational class has the
following fundamental characteristics:
l Preservation of the time relationships between information entities in a stream and
limitation of the transmission delay and delay jitter within an acceptable range.
l Conversational pattern (stringent requirement on the delay).
Conversational services are applicable in both the CS and PS domains. Most typical applications
of the conversational class are voice services and videophone services in the CS domain and
VoIP services in the PS domain.
Huawei RAN supports the following basic types of conversational services:
l CS AMR speech services at the rates of 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7
kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s
l CS transparent data services (conversational class) at the rates of 64 kbit/s, 56 kbit/s, 32
kbit/s, and 28.8 kbit/s
l 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. 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).
l Verification Procedure
1. Initiate Iub interface tracing on the BSC6900 LMT, as shown in Figure 5-1.
2. Establish a conversational service on the UE. Check the DPC (that is, the source) of
the RANAP_RAB_ASSIGNMENT_REQ message among the traced Iu data to
determine whether the service is a CS service or PS service.
3. View the trafficClass IE in the rRB-Parameters IE of the
RANAP_RAB_ASSIGNMENT_REQ message to verify that the traffic class is
conversational.
4. View the maxBitrate and rAB-AsymmetryIndicator IEs in the
RANAP_RAB_ASSIGNMENT_REQ message.
If the value of the rAB-AsymmetryIndicator IE is Asymmetric bidirectional,
then the maxBitrate IE contains two values. The first value indicates the downlink
rate of the conversational service, and the second indicates the uplink rate of the
service. That is, the uplink and downlink transmission uses asymmetric rates.
If the value of the rAB-AsymmetryIndicator IE is Symmetric bidirectional,
then the maxBitrate IE contains one value, which indicates the rate applicable in
both the uplink and the downlink. That is, the uplink and downlink transmission
uses symmetric rates.
If the value of the rAB-AsymmetryIndicator IE is Asymmetric Uni directional
downlink, then the maxBitrate IE contains one value, which indicates the
downlink rate of the conversational service. In this case, the uplink rate of the
service is 0.
If the value of the rAB-AsymmetryIndicator IE is Asymmetric Uni directional
Uplink, then the maxBitrate IE contains one value, which indicates the uplink
rate of the conversational service. In this case, the downlink rate of the service is
0.
5. View the guaranteedBitRate (the guaranteed bit rate of the conversational service)
and rAB-AsymmetryIndicator IEs in the RANAP_RAB_ASSIGNMENT_REQ
message by following the same rules as those for viewing maxBitrate.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
//Activating conversational QoS class
SET UFRCCHLTYPEPARA: CSVoiceChlType=DCH, VoipChlType=DCH;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010502
Streaming QoS Class.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Others
The UE and CN support streaming services.
Context
Based on QoS requirements, there are four traffic classes: conversational, streaming, interactive,
and background.
QoS indicates the sensitivity of services to the delay. The streaming class is a relatively recent
development in data communications, which raises a number of new requirements in both
telecommunication and data communication systems. The transmission of streaming services
must follow the time sequence of information entities . The streaming class has the following
features:
l The time sequence of information entities in a stream is not changed.
l 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 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. Optional: Run the BSC6900 MML command DEA UCELLHSDPA to disable the
HSDPA capability of the cell.
3. Optional: Run the BSC6900 MML command DEA UCELLHSUPA to disable the
HSUPA capability of the cell.
l Verification Procedure
1. Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 6-1
2. Use a UE to set up a streaming service. Check the DPC (that is, the source) of the
RANAP_RAB_ASSIGNMENT_REQ message among the traced Iu data to
determine whether the service is a CS service or PS service.
3. Check the RANAP_RAB_ASSIGNMENT_REQ message and check that the value
of the trafficClass information element (IE) in rRB-Parameters is streaming.
4. 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.
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.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010503
Interactive QoS Class.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Others
The UE and CN support interactive services.
Context
Based on QoS requirements, there are four traffic classes: conversational, streaming, interactive,
and background. QoS indicates the sensitivity of services to the delay.
The interactive class is a typical data communication solution. It is characterized by the request/
response pattern of end users. For example, a person or an entity at the destination sends a data
request to a remote server and expects a response message within a specific time. In this situation,
the Round Trip Time (RTT) is one of the key attributes of the interactive class. Another
characteristic is that the packets should be transparently transferred at a low Bit Error Rate
(BER). In summary, the interactive class has the following fundamental characteristics: request/
response pattern and preservation of the payload.
Interactive services are applicable in the PS domain and not applicable in the CS domain. The
most typical application of the interactive class is web browsing.
Huawei RAN supports the following types of interactive services: PS bidirectional symmetric
or asymmetric interactive services at the rates of 384 kbit/s, 285 kbit/s, 144 kbit/s, 128 kbit/s,
64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the HSDPA/
HSUPA rate threshold for interactive services. If the assigned rate of an interactive
service is lower than this threshold, the interactive service is set up on R99 channels.
l Verification Procedure
1. Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 7-1
Example
//Activating Interactive QoS Class
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900,
UlBeTraffThsOnHsupa=D5440;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010504
Background QoS Class.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Others
The UE and CN support this feature.
Context
Based on QoS requirements, there are four traffic classes: conversational, streaming, interactive,
and background.
QoS indicates the sensitivity of services to the delay. A typical type of background service is
data services. One of the characteristics of the background class is that the destination does not
expect data within a specific time, and therefore the background class is delay-insensitive.
Another characteristic is that the packets should be transparently transferred at a low Bit Error
Rate (BER).
In summary, the background class has the following fundamental characteristics: destination not
expecting data within a specific time and preservation of the payload.
Background services are applicable in the PS domain and not applicable in the CS domain. The
most typical applications of the background class are download and emails.
Huawei RAN supports the following types of background services: PS bidirectional symmetric
or asymmetric background services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s,
64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set the HSDPA/
HSUPA rate threshold for background services. If the assigned rate of a background
service is lower than this threshold, the background service is set up on R99 channels.
l Verification Procedure
1. Start Iu interface tracing on the BSC6900 LMT, as shown in Figure 8-1
Example
//Activating Background QoS Class
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D13900,
UlBeTraffThsOnHsupa=D5440;
This section describes how to activate, verify, and deactivate the basic feature WRFD-021104
Emergency Call.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
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 Activation Procedure
This feature need not be activated.
l Verification Procedure
1. Use a UE to initiate an emergency call.. The emergency call is successfully established.
l Deactivation Procedure
This feature need not be deactivated.
----End
This section describes how to activate, verify, and deactivate the basic feature MRFD-210604
2-Way Antenna Receive Diversity.
Prerequisite
l 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.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. Run the NodeB MML command ADD SEC. In this step, set Antenna Magnitude to
2.
l Verification Procedure
1. 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
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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010205
Cell Digital Combination and Split.
Prerequisite
l 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. Multiple-
antenna receive modes are not supported.
One CPRI port supports a maximum of eight cascaded RRUs. A maximum of eight
RRUs share one cell. A maximum of three distributed cells are supported.
One BBU supports combination of UL digital signals on a maximum of two CPRI ports.
A maximum of 16 RRUs share one cell.
With the delay considered, the optical fiber for interconnecting RRUs in one cell and
with neighboring coverage areas should be less than 4 km in length.
RF modules, RRU 3828 and RRU3829 can only support maximum of 4 carriers when
they are implemented for Cell Digital Combination and Split.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
Procedure
l Activation Procedure
1. Run the NodeB MML command ADD RRUCHAIN to add an RRU chain. In this
step, set Topo Type to CHAIN.
2. 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.
3. Run the NodeB MML command ADD SEC to add a sector. In this step, set Sector
Type to DIST_SECTOR(DIST_SECTOR).
4. Run the NodeB MML command ADD LOCELL to add a local cell. In this step, set
Sector Type to DIST_SECTOR(DIST_SECTOR).
l Verification Procedure
1. Run the NodeB MML command LST SEC. In this step, check that Sector Type is
set to DIST_SECTOR(DIST_SECTOR).
2. Run the NodeB MML command LST LOCELL. In this step, check that Sector
Type is set to DIST_SECTOR(DIST_SECTOR).
l 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010202
UE State in Connected Mode (CELL_DCH, CELL_PCH, URA_PCH, CELL_FACH).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l 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 Activation Procedure
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.
2. 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.
3. Run the BSC6900 MML command SET UUESTATETRANS. In this step, set Cell
Reselection Counter Threshold to an appropriate value.
NOTE
l This feature involves the parameter settings of state transition from CELL_FACH or CELL_DCH to
CELL_PCH or URA_PCH. For the parameter settings of other types of state transition, see 15
Configuring Dynamic Channel Configuration Control.
l For the parameter settings related to fast dormancy, see 162 Configuring Enhanced Fast
Dormancy.
l 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.
l 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;;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010301
Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. (Optional) Run the BSC6900 MML command SET UCORRMALGOSWITCH to
turn on the RNC-oriented PS BE service state transition switch.
2. 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.
3. Run the BSC6900 MML command SET UUESTATETRANS to set the parameter
Cell Reselection Counter Threshold to 1.
4. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity
detection timers for PS services.
l Verification Procedure (Paging a UE in Idle Mode)
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, Trace Mode and Save
File. Then, click Submit.
3. Power on UE1 and UE2, and camp on CELL1. Use UE2 to call UE1. The
RRC_PAGING_TYPE1 message should be displayed on the Trace Data tab page.
l Commissioning Procedure (Paging a UE in CELL_PCH State)
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. On the HLR, set the PS service type to background or interactive.
3. Establish an R99 PS service on UE1. The RRC_RB_SETUP message should be
displayed in trace data, and the value of the rrc-stateindicator IE should be
CELL_DCH.
4. Do not send any data from UE1 for 30 seconds. Then, the network side should perform
UE1 transition to CELL_FACH state through the RRC_RB_RECFG message, and
the value of rrc-stateindicator IE should be CELL_FACH.
5. Do not send any data from UE1 for another while. Then, the network side should
perform UE1 transition to CELL_PCH state through the RRC_RB_RECFG message,
and the value of rrc-stateindicator IE should be CELL_PCH.
6. Use UE2 to call UE1. The RRC_PAGING_TYPE1 message should be displayed.
l Verification Procedure (Paging a UE in URA_PCH)
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. 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 rrc-
stateindicator IE should be URA_PCH.
3. Use UE2 to call UE1. The RRC_PAGING_TYPE1 message should be displayed.
NOTE
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).
l Deactivation Procedure
1. This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010302
Paging UE in CELL_FACH, CELL_DCH State (Type 2).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. (Optional) Run the BSC6900 MML command SET UCORRMALGOSWITCH to
turn on the RNC-oriented PS BE service state transition switch.
2. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the
parameter BE DCH to FACH Transition Timer[s] to 30s.
3. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity
detection timers for PS services.
l Verification Procedure (Paging a UE in CELL_DCH State)
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, Trace Mode and Save
File. Then, click Submit.
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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-021101
Dynamic Channel Configuration Control (DCCC).
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l 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:
TimetoTrigger4B
PendingTime4A
PendingTime4B
(2) Run the BSC6900 MML command SET UDCCC to set the following RNC-
level 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
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
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. Run the BSC6900 MML command MOD UCELLHOCOMM. In this step,
set Inter-Frequency and Inter-RAT Coexist Switch to INTERFREQ.
b. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In
this step, set HandOver Switch to
HO_INTER_FREQ_HARD_HO_SWITCH.
(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.
b. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In
this step, set HandOver Switch to
HO_INTER_RAT_PS_OUT_SWITCH.
(10) To configure inter-frequency handover and inter-RAT handover for the link
stability of BE services, perform the following steps:
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 RNC-
level DCCC algorithm parameters:
DCCC Rate Up Fail Time Threshold
DCCC Rate Up Fail Monitor Time length
DCCC Rate Up Fail Penalty Time Length
l 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. Run the BSC6900 MML command SET UUESTATETRANS to set the measurement
control parameters of the UE state transition algorithm.
3. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the
timer parameters of the UE state transition algorithm.
4. Run the BSC6900 MML command SET UDCCC to set Low Activity Bit Rate
Threshold.
l Activating always online
1. Run the BSC6900 MML command SET UPSINACTTIMER to set the following
timer parameters for checking the low activity of PS users:
Conversational service T1
Streaming service T1
Interactive service T1
Background service T1
IMS signal T1
Conversational service T2
Streaming service T2
Interactive service T2
Background service T2
IMS signal T2
l Verifying DCCC
1. Traffic-based BE service rate adjustment
(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 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.
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 Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn off the
related switches.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH.
----End
Example
//Activating DCCC
//Activating the DCCC algorithm
SET UCORRMALGOSWITCH: DraSwitch=DRA_DCCC_SWITCH-1;
//Activating traffic-based BE service rate adjustment
MOD UTYPRABDCCCMC: RabIndex=1, Direction=DOWNLINK, Event4aThd=D1024,
Event4bThd=D16, TimetoTrigger4A=D240, PendingTime4A=D4000,
TimetoTrigger4B=D2560, PendingTime4B=D4000;
SET UDCCC: UlDcccRateThd=D64, DlDcccRateThd=D64,
DcccStg=RATE_UP_AND_DOWN_ON_DCH, UlRateUpAdjLevel=3_Rates,
UlRateDnAdjLevel=3_Rates, UlMidRateCalc=HAND_APPOINT, UlMidRateThd=D128,
DlRateUpAdjLevel=3_Rates, DlRateDnAdjLevel=3_Rates,
DlMidRateCalc=HAND_APPOINT, DlMidRateThd=D128;
//Activating throughput-based BE service rate adjustment
SET UCORRMALGOSWITCH: DraSwitch=DRA_THROUGHPUT_DCCC_SWITCH-1;
SET UDCCC: HsupaDcccStg=RATE_UP_AND_DOWN_ON_EDCH, DchThrouMeasPeriod=100;
MOD UTYPRABDCCCMC: RabIndex=1, Direction=UPLINK, Event4bThd=D64,
DchThrouTimetoTrigger4B=2, DchThrouPendingTime4B=16;
SET UUESTATETRANS: E2FThrouMeasPeriod=30;
//Activating link-stability-based BE service rate adjustment
//Setting the QoS-related parameters
SET UQOSACT: BEQosPerform=YES, BeUlAct1=RateDegrade,
BeUlAct2=InterFreqHO, BeUlAct3=InterRatHO, BeDlAct1=RateDegrade,
BeDlAct2=InterFreqHO, BeDlAct3=InterRatHO, BeUlEvTrigInd=SINGLE,
SrncBeDlRlcQosSwitch=YES, DrncBeDlRlcQosSwitch=YES,
BeUlQos6A1McSwitch=YES, BeUlQos5AMcSwitch=YES, BeUlQos6DMcSwitch=YES;
SET UQUALITYMEAS: UlBeTrigTime6A1=D640, UlBeTrigTime6B1=D2560,
UlBeTrigTime6A2=D1280, UlBeTrigTime6B2=D1280, UlBeTrigTime6D=D240,
UlMeasFilterCoef=D19, DlMeasFilterCoef=D1, DlBeTrigTimeE=64,
ChoiceRptUnitForBeE=TEN_MSEC, TenMsecForBeE=480, DlBeTrigTimeF=64,
ChoiceRptUnitForBeF=TEN_MSEC, TenMsecForBeF=480;
MOD UCELLRLPWR: CellId=1, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200,
RLMAXDLPWR=-30, RLMINDLPWR=-180, DLSF=D128;
MOD UTYPRABQUALITYMEAS: RabIndex=1, UlThd6a1=1, UlThd6a2=5, UlThd6b1=1,
UlThd6b2=5, StaBlkNum5A=500, Thd5a=280, HangBlockNum5a=512, ThdEa=2,
ThdEb=2;
MOD UTYPRABRLC: RabIndex=1, SubflowIndex=0, TrchType=TRCH_DCH,
OppositeTrchType=TRCH_DCH, DelayClass=1, RlcMode=AM,
AmRlcCfgPara=FLOWCONTROL_PARA, TimeToMoniter=6000, MoniterPrd=1000,
ReTransRatioFilterCoef=1, EventAThred=160, TimeToTriggerA=2,
PendingTimeA=1;
//Configuring inter-frequency handover for the link stability of BE
services
MOD UCELLHOCOMM: CellId=1, InterFreqRATSwitch=INTERFREQ,
CoexistMeasThdChoice=COEXIST_MEAS_THD_CHOICE_INTERFREQ,
CSServiceHOSwitch=OFF, PSServiceHOSwitch=OFF;
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1;
//Configuring inter-RAT handover for the link stability of BE services
MOD UCELLHOCOMM: CellId=1, InterFreqRATSwitch=INTERRAT,
CoexistMeasThdChoice=COEXIST_MEAS_THD_CHOICE_INTERFREQ,
CSServiceHOSwitch=OFF, PSServiceHOSwitch=ON;
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_OUT_SWITCH-1;
//Setting the DCCC algorithm parameters
This section describes how to activate, verify, and deactivate the basic feature WRFD-011401
Integrity Protection.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
This feature protects the network and user data from being listened and modified illegally.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UUIA to enable the RNC to support the
integrity protection algorithm.
l Verification Procedure
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu
Interface Trace. The Iu Interface Trace dialog box is displayed.
2. Keep UE1 and UE2 in idle mode in CELL1.
3. Use UE2 to call UE1.
4. The messages RANAP_SECURITY_ MODE_COMMAND and
RANAP_SECURITY_MODE_COMPLETE should be displayed. The
chosenIntegrityProtectionAlgorithm IE of the latter message indicates the integrity
protection algorithm.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
//Activating integrity protection
SET UUIA: IntegrityProtectAlgo=UIA1-1;
17 Configuring Encryption
This section describes how to activate, verify, and deactivate the basic feature WRFD-011402
Encryption.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
The encryption algorithms supported by Huawei RAN include UEA0 and UEA1.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UUEA to enable the RNC to support the
encryption algorithm.
l Verification Procedure
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu
Interface Trace. The Iu Interface Trace dialog box is displayed.
2. Keep UE1 and UE2 in idle mode in CELL1.
3. Use UE2 to call UE1.
4. The messages RANAP_SECURITY_ MODE_COMMAND and
RANAP_SECURITY_MODE_COMPLETE should be displayed. The
chosenEncryptionAlgorithm IE of the latter message indicates the encryption
algorithm.
5. End the calling. UE1 and UE2 return to the idle mode.
6. The messages RANAP_SECURITY_MODE_COMMAND and
RANAP_SECURITY_MODE_COMPLETE should be displayed. The
Example
//Activating encryption
SET UUEA: EncryptionAlgo=UEA0-1&UEA1-1;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020501
Open Loop Power Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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.
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.
1. Run the BSC6900 MML command MOD UPRACHUUPARAS. In this step, set the
parameters related to the PARCH to appropriate values.
l Verification Procedure
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.
Example
//Activating open loop power control on the uplink DPCH
SET UFRC: DefaultConstantValue=-22;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020502
Downlink Power Balance.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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.
l Verification Procedure
1. On the BSC6900 LMT, choose Trace > UMTS Services and double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set Cell Config, Uu Message Type, and Save File. Then click Submit.
3. Move a UE from cell 1 to cell 2 to ensure that the UE performs a soft handover.
4. Check whether the active cell set update is complete in the traced Uu-interface
messages. Figure 19-1 shows the expected result.
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-code-
power(2) shown in Figure 19-2.
l 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020503
Outer Loop Power Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the
OLPC function.
2. Optional: Run the BSC6900 MML command MOD UTYPRABOLPC to set the
parameters related to OLPC according to network plan.
l Verification Procedure
1. 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.
l 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,
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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020504
Inner Loop Power Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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 Activation Procedure
1. The feature does not need to be activated.
l Verification Procedure
1. 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.
2. UE 1 calls UE 2. UE 2 rings, answers and starts the conversation.
3. Observe the variation of UL SIR and UE Tx Power in the UL SIR and UE Tx
Power Connection Performance Monitoring window.
4. UE 1 moves in the cell to change radio link quality.
5. When you move UE 1 away from the cell center, UE_1 transmit power increases.
6. When you move UE_1 towards cell center, UE_1 transmit power decreases.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
This section describes how to activate, verify, and deactivate the basic feature WRFD-020101
Admission Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
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. 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. Activating Iub resource admission
This feature does not need to be activated.
l 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. Enable a UE in the idle state to camp on CELL_A11.
2. Set the PS service type to interactive on the HLR.
3. Run the BSC6900 MML command MOD UCELLCAC. In this step, set DL total
equivalent user number of CELL_A11 to 1.
4. Connect the UE to a laptop through the USB port and initiate a PS service.
Expected result: The UE fails to initiate the PS service. In the Iu Interface Trace
window, an RANAP_RAB_ASSIGNBMENT_RESP message sent from the RNC to
the CN is displayed, containing the cause value no-radio-resources-available-in-
target-cell.
5. Run the BSC6900 MML command MOD UCELLCAC. In this step, set DL total
equivalent user number of CELL_A11 to 80.
6. Connect the UE to a laptop through the USB port and initiate a PS service.
Expected result: The data service is set up successfully.
l Deactivation Procedure
1. Deactivating code resource admission
This feature does not need to be deactivated.
2. 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020102
Load Measurement.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
This feature is used to measure the load for the load control feature.
Procedure
l Activation Procedure
1. The function of measurement on RTWP, TCP, and non-HSPA power is always
activated. Therefore, this feature does not need to be activated.
2. 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.
3. 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.
4. 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.
l Verification Procedure
1. On the BSC6900 LMT, open the Monitor page. In the Monitor navigation tree,
double-click UMTS Monitoring > Cell Performance Monitoring, and create tasks
of monitoring Cell DL Carrier TX Power and RTWP.
2. Check whether the uplink full-bandwidth RX power of the cell is displayed in the
RTWP monitoring window.
3. Check whether the downlink carrier TX power is displayed in the Cell DL Carrier
TX Power monitoring window.
l Deactivation Procedure
1. The measurement on RTWP, TCP, and non-HSPA power has been activated and
cannot be deactivated.
2. 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.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020106
Load Reshuffling.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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 real-
time 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
(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-group-
level 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. Run the BSC6900 MML command SET ULDCPERIOD to set the LDR period (LDR
period timer length).
4. 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. Enable a UE in idle mode to camp on CELL_A11.
2. On the BSC6900 LMT, open the Monitor tab page. In the Monitor Navigation
Tree tab page, double-click UMTS Monitoring > Cell Performance Monitoring.
In the displayed dialog box, create a Cell DL Throughput monitoring task.
3. Connect the UE to a laptop through the USB port and initiate a data service. Check
the rb-mappinginfo information element (IE) contained in the RRC_RB_SETUP
message traced over the Uu interface. The value of rrc-Stateinditator is
CELL_DCH.
4. Use the UE to log in to the FTP server and then start FTP downloading. Data
downloading is normal.
5. To simulate the scenario where power load reaches 75%, run the NodeB MML
command STR DLSIM. The RRC_RB_RECFG message is displayed in the Uu
Interface Trace dialog box. In the Cell DL Throughput of the Connection
Performance Monitoring dialog box, you can view the downlink RB rate decrease
configured on the RNC.
6. To stop simulating power load, run the NodeB MML command STP DLSIM. In the
Uu Interface Trace dialog box, the RRC_RB_RECFG message is displayed. In the
Cell DL Throughput of the Connection Performance Monitoring dialog box, you can
view the downlink RB rate increase configured on the RNC.
l Deactivation Procedure
1. 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
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_LDR-
1;
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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020107
Overload Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license 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.
2. Run the BSC6900 MML command MOD UNODEBALGOPARA to enable the OLC
algorithm. Select the IUB_OLC check box under the parameter NodeB LDC
algorithm.
3. 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.
4. Run the BSC6900 MML command SET ULDCPERIOD to set the OLC period (OLC
period timer value).
5. Run the BSC6900 MML command ADD UCELLOLC to set the parameter related
to OLC-related actions.
l Verification Procedure
1. Run the following BSC6900 MML commands to verify whether the activation is
successful.
LST UCELLALGOSWTICH
LST UCELLLDM
LST UNODEBALGOPARA
LST ULDCPERIOD
LST UCELLOLC
NOTE
Consult Huawei engineers about the verification solution to obtain professional technical support.
NOTE
l 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.
2. Run the BSC6900 MML command MOD UNODEBALGOPARA to disenable the
OLC algorithm, Clear the IUB_OLC check box under the parameter NodeB LDC
algorithm.
----End
Example
//Activating Overload Control
MOD UCELLALGOSWITCH: CellId=111,
NBMLdcAlgoSwitch=UL_UU_OLC-1&DL_UU_OLC-1;
MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-1;
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020108
Code Resource Management.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
This feature provides downlink code tree allocation and reshuffling. Through this, the code
resources can be rationally allocated, therefore increasing the utilization efficiency of the
resources.
Procedure
l Activation Procedure
NOTE
The code allocation function is always activated. The activation procedure applies to only the code
reshuffling function.
1. Run the BSC6900 MML command MOD UCELLALGOSWITCH, and then enable
the required LDR algorithm switches for resources (CELL_CODE_LDR(Code
LDR Algorithm)) through setting the Cell LDC algorithm switch parameter.
2. 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.
3. Run the BSC6900 MML command SET ULDCPERIOD to set the length of LDR
period (LDR period timer length).
l Verification Procedure
1. Enable the UE in the idle state to camp on CELL_A11.
2. Set the PS service type to interactive on the HLR.
3. Run the BSC6900 MML command MOD UCELLLDR with Cell LDR SF reserved
threshold set to SF8 and Max user number for code adjust to 1.
4. Connect the UE to a laptop on the USB port and enable the UE to initiate a data service.
Expected result: Services are set up on the DCH successfully. You can view the rb-
mappinginfo information element (IE) in the RRC_RB_SETUP message traced over
the Uu interface. In the Cell Code Tree Monitor window, you can view that the
service occupies code SF32(4).
5. Enable the UE to log in to the FTP Internet server and then enable FTP download.
6. Run the BSC6900 MML command DSP UCELLCHK to check the cell health status.
The status of cell code congestion is displayed as basic congestion.
7. Run the BSC6900 MML command RMV URESERVEOVSF to release the service
that occupies code SF32(1).
8. Run the BSC6900 MML command DSP UCELLCHK to check the cell health status.
The status of cell code congestion is displayed as not congested.
l Deactivation Procedure
1. 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.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-021301
Shared Network Support in Connected Mode.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l 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. For the CS service, configure two SNAs (for example, SNA1 and SNA2) on the MSC.
2. For the PS service, run the MML command ADD SNA on the SGSN to add SNA,
SNA1, and SNA2.
3. Run the BSC6900 MML command MOD UCELLACINFO to modify the RACs of
CELL1 and CELL2.
4. Set up a cell. For details, see the BSC6900 UMTS Initial Configuration Guide.
5. Run the BSC6900 MML command to turn on the soft handover switch.
6. Run the BSC6900 MML command to enable the SNA function.
l Verifying the SNA Function of the CS Service
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Iu
Interface Trace. The Iu Interface Trace dialog box is displayed.
2. Keep UE1 and UE2 in idle mode in CELL1.
3. Run the BSC6900 MML command to disable the SNA function.
4. Use UE1 to call UE2. The RANAP_COMMON_ID message from UE1 should be
displayed in Iu trace data, and it should include the SNA ACCESS information IE.
5. Move UE1 to CELL2 to trigger soft handover. The RRC_ACTIVE_SET_UPDATE
message from the RNC to UE1 and the RRC_ACTIVE_SET_UPDATE_CMP
message from UE1 to the RNC should be displayed in Uu trace data.
6. End the calling. UE1 and UE2 return to the idle mode in CELL1.
7. Run the BSC6900 MML command to enable the SNA function.
8. Add a mapping relation between IMSI of UE1 and SNA1 on the MSC.
9. Use UE1 to call UE2. The RANAP_COMMON_ID message from UE1 should be
displayed in Iu trace data, and it should include the SNA ACCESS information IE.
NOTE
CELL2 belongs to SNA2 but not SNA1. Therefore, the RRC_MEAS_CTRL message sent from
the RNC to UE1 on the Uu interface should indicate that CELL2 is not in the monitoring cell.
10. Move UE1 to CELL2, which will not trigger soft handover because UE1 does not
belong to SNA_2.
11. End the calling. UE1 and UE2 return to the idle mode in CELL1.
l Verifying the SNA Function of the PS Service
1. Run the MML command ADD SNA on the SGSN to add SNA information.
2. Run the BSC6900 MML command to disable the SNA function.
3. Keep the UE in idle mode in CELL1.
4. Establish a PS service on UE1. The RANAP_COMMON_ID message from UE1
should be displayed in Iu trace data, and it should include the SNA ACCESS
information IE.
5. Move UE1 to CELL2 to trigger soft handover. The RRC_ACTIVE_SET_UPDATE
message from the RNC to UE1 and the RRC_ACTIVE_SET_UPDATE_CMP
message from UE1 to the RNC should be displayed in Uu trace data.
6. End the PS service of UE1. UE1 returns to the idle mode in CELL1.
7. Run the BSC6900 MML command to enable the SNA function.
8. Establish a PS service on UE1. The RANAP_COMMON_ID message from UE1
should be displayed in Iu trace data, and it should include the SNA ACCESS
information IE.
9. CELL2 belongs to SNA2 but not SNA1. Therefore, the RRC_MEAS_CTRL message
sent from the RNC to UE1 on the Uu interface should indicate that CELL2 is not in
the monitoring set.
10. Move UE1 to CELL2, which will not trigger soft handover because UE1 does not
belong to SNA_2.
11. End the PS service of UE1. UE1 returns to the idle mode in CELL1.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the
SNA function.
----End
Example
//Adding two SNAs (for example, SNA1 and SNA2) on the MSC
ADD LOCNOLAI: LOCNONAME="SNA_1", LAI="460020001";
ADD LOCSNA: LOCNONAME=" SNA_1", SNAC=1;
ADD SNAGRPCODE: SNAGRPN="1", SNAC=1;
ADD LOCNOLAI: LOCNONAME="SNA_2", LAI="460020002";
ADD LOCSNA: LOCNONAME=" SNA_2", SNAC=2;
ADD SNAGRPCODE: SNAGRPN="2", SNAC=2;
//Activating the SNA function of the CS Service
MOD UCELLACINFO: CellId=1, LAC=1, SAC=0, CfgRacInd=REQUIRE, RAC=1;
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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020201
Intra NodeB Softer Handover.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable soft
handover.
2. Run the BSC6900 MML command SET UHOCOMM to set Softer handover
combination indicator switch to MAY or MUST.
3. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell.
4. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter
related to handover.
l Verification Procedure
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. UE is in idle mode and camps on the CELL1.
4. UE initiates PS Dial-up, and service is set up successfully.
5. UE moves from CELL1 to CELL2, through the Trace Data, it can be observed RNC
sends the RRC_ACTIVE_SET_UPDATE message to UE and UE sends the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC.
6. The data transmission remains normal while UE is moving to CELL2.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UHOCOMM to set Softer handover
combination indicator switch to MUST_NOT.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020202
Intra RNC Soft Handover.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable soft
handover.
2. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell.
3. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter
related to handover.
l Verification Procedure
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. Both UE1 and UE2 are in idle mode and camp on the CELL1.
4. UE1 calls UE2, and the conversation clear.
5. UE1 moves from CELL1 to CELL2, through the Trace Data, it can be observed that
RNC1 sends the RRC_ACTIVE_SET_UPDATE message to UE1, and UE1 sends the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC1.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set Softer
handover combination indicator to disable the soft handover.
----End
Example
//Activating Intra RNC Soft Handover
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1;
ADD UINTRAFREQNCELL: RNCId=202, CellId=2381, NCellRncId=203,
NCellId=3291, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0,
NPrioFlag=FALSE;
SET UINTRAFREQHO: FilterCoef=D3, IntraFreqMeasQuantity=CPICH_EC/NO,
PeriodMRReportNumfor1C=D16, ReportIntervalfor1C=D4000;
//Deactivating Intra RNC Soft Handover
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-0;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020203
Inter RNC Soft Handover.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Other Prerequisites
The Iur interface is configured between adjacent RNCs.
Context
Inter-RNC soft handover is one type of soft handover. To implement inter-RNC soft handover,
multiple RLs need to be established between different RNCs. In such a case, macro diversity
combining is performed by the SRNC connected through the Iur interface. The SRNC sends the
DRNC the radio link establishment signaling over the Iur interface. Based on the signaling, the
DRNC establishes a radio link in the new NodeB. Other procedures are similar to those of intra-
RNC 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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable soft
handover.
2. Run the BSC6900 MML command ADD UNRNC or MOD UNRNC to enable cross-
Iur soft handover.
3. Run the BSC6900 MML command ADD UEXT3GCELL to add a neighboring RNC
cell.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020301
Intra Frequency Hard Handover.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select
HO_INTRA_FREQ_HARD_HO_SWITCH from the HandOver switch list.
2. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency or inter-RNC neighboring cell.
3. If cross-Iur hard handover is required, add the neighboring RNC and neighboring RNC
cell. Run the 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.
4. Run the BSC6900 MML command SET UINTRAFREQHO to set the parameter
related to handover.
l Verification Procedure
1. On the BSC6900 LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. Both UE1 and UE2 are subscribed in HLR to support speech service.
4. 4. Both UE1 and UE2 are in idle mode and camp on the CELL1.
5. UE1 calls UE2, and the conversation is clear.
6. UE1 moved from CELL1 to CELL2, through the Trace Date, it can be observed
RRC_MEAS_RPRT message with 1D event that UE1 sends to RNC1.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010801
Intra RNC Cell Update.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
Cell update is mainly used to update the UE information on the network side when the UE
location or behavior is changed. Intra-RNC cell update means cell update within the RNC.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the
RNC-oriented PS BE service state transition switch.
2. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the
parameters BE DCH to FACH Transition Timer[s] and BE FACH or E_FACH to
PCH Transition Timer[s] to 30s and 60s respectively.
3. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity
detection timers for PS services.
4. Run the BSC6900 MML command SET UCONNMODETIMER to set the periodic
cell update timer to 5 minutes.
5. Set CELL1 and CELL2 of the RNC as intra-frequency neighboring cells. For details,
see the BSC6900 UMTS Initial Configuration Guide.
l Verifying Cell Update Triggered by Cell Reselection
1. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click
Uu Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. Keep the UE in idle mode in CELL1.
4. On the HLR, set the PS service type to background or interactive.
5. 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.
6. Do not send any data from UE for 30 seconds. Then, the network side should perform
UE transition to CELL_FACH state through the RRC_RB_RECFG message, and the
value of the rrc-stateindicator IE should be CELL_FACH.
7. Cause the UE to reselect a new cell so as to trigger cell update. The UE should send
the RRC_CELL_UPDATE message to the RNC, with the cell update cause of cell
reselection, and the RNC should send the RRC_CELL_UPDATE_CONFIRM
message to the UE.
l Verifying Cell Update Triggered by Uplink Data Transmission
1. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click
Uu Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Keep the UE in idle mode in CELL1.
3. On the HLR, set the PS service type to background or interactive.
4. 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.
5. 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.
6. Do not send any data from UE1 for another while. Then, the network side should
perform UE transition to CELL_PCH state through the RRC_RB_RECFG message,
and the value of the rrc-stateindicator IE should be CELL_PCH.
7. Use the UE to transmit data so as to trigger cell update. The UE should send the
RRC_CELL_UPDATE message to the RNC, with the cell update cause of
uplinkdatatransmission, and the RNC should send the
RRC_CELL_UPDATE_CONFIRM message to the UE.
l Verifying Periodic Cell Update
1. 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;
2. 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. Keep the UE in idle mode in CELL1.
4. On the HLR, set the PS service type to background or interactive.
5. 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.
6. Do not send any data from UE for 30 seconds. Then, the network side should perform
UE transition to CELL_FACH state through the RRC_RB_RECFG message, and the
value of the rrc-stateindicator IE should be CELL_FACH.
7. 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.
l Deactivation Procedure
1. None
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010802
Inter RNC Cell Update.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the
RNC-oriented PS BE service state transition switch.
2. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set the
parameter BE DCH to FACH Transition Timer to 30s.
3. Run the BSC6900 MML command SET UPSINACTTIMER to set inactivity
detection timers for PS services.
4. Configure intra-frequency neighboring cells controlled by different BSC6900s. For
details, see the Configuring an Intra-Frequency Neighboring Cell.
5. Run the BSC6900 MML command MOD UNRNC to set the parameter IUR CCH
support flag to ON.
NOTE
1. Log on the BSC6900 LMT, click Trace > UMTS Services, and then double-click
Uu Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. Keep the UE in idle mode in CELL.
4. On the HLR, set the PS service type to background or interactive.
5. 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.
6. Do not send any data from UE for 30 seconds. Then, the network side should perform
UE transition to CELL_FACH state through the RRC_RB_RECFG message, and the
value of the rrc-stateindicator IE should be CELL_FACH.
7. Cause the UE to 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.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010901
Intra RNC URA Update.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Intra-
RNC 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.
2. Run the BSC6900 MML command ADD UCELLURA to configure CELL1 and
CELL2 to make them belong to different URAs.
3. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the
RNC-oriented PS BE service state transition switch.
4. 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.
5. Run the BSC6900 MML command SET UUESTATETRANS to set the parameter
Cell Reselection Counter Threshold to 1.
Example
//Activating intra-RNC URA update
MOD UCELLACINFO: CellId=111, LAC=1, SAC=1, CfgRacInd=REQUIRE, RAC=1;
MOD UCELLACINFO: CellId=121, LAC=1, SAC=1, CfgRacInd=REQUIRE, RAC=1;
ADD UCELLURA: CellId=111, URAId=0;
ADD UCELLURA: CellId=121, URAId=1;
SET UCORRMALGOSWITCH: DraSwitch=DRA_PS_BE_STATE_TRANS_SWITCH-1;
SET UUESTATETRANSTIMER: CellReSelectTimer=60, BeD2FStateTransTimer=10,
BeF2PStateTransTimer=10;
SET UUESTATETRANS: CellReSelectCounter=1;
SET UPSINACTTIMER: PsInactTmrForInt=0, PsInactTmrForBac=0;
SET UCONNMODETIMER: T305=D5;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010902
Inter RNC URA Update.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
Inter-RNC URA update means URA update between RNCs.
Procedure
l Activation Procedure
1. Configure the Iur interface. For details, see the BSC6900 UMTS Initial Configuration
Guide.
2. 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.
4. 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.
5. Run the BSC6900 MML command SET UUESTATETRANS to set the parameter
Cell Reselection Counter Threshold to 1.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-021400
Direct Signaling Connection Re-establishment (DSCR).
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
During a DSCR procedure, the RNC autonomously releases the RRC connection carrying non-
real-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.
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.
NOTE
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;
This section describes how to activate, verify, and deactivate the basic feature MRFD-210501
NodeB Clock.
Prerequisite
l 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.
l Dependencies on Other Features
This feature does not depend on other features.
l 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 Synchronization with the Iub clock (default mode)
l Synchronization with GPS
l 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.
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
Activation Procedure
1. Run the NodeB MML command SET CLKMODE to set the working mode of the
reference 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
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;
l 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:;
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030104
Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.
Prerequisite
l Dependencies on Hardware
BTS3902E does not support this feature.
l Dependencies on Other Features
The feature WRFD-050301 ATM Transmission Introduction Package must be
configured before this feature is activated.
l License
This feature is not under license control.
l 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.
NOTE
For an adjacent node on the Iur or Iu-CS interface, the parameter Adjacent Node Type of its upper-
level 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.
l Verification Procedure
1. Run the BSC6900 MML command DSP AAL2PATH to query the status of the AAL2
path on the Iub interface.
Expected result: The value of Operation state is Available.
2. In the Iub/Iu-CS ATM transmission scenario, a UE in idle state camps on CELL1 and
the control plane is correctly configured. Originate the speech and data services. If the
service access is normal, the AAL2 path on the Iub/Iu-CS interface is set up
successfully.
3. Optional: In the ATM transmission scenario on the Iur interface, a UE in idle state
camps on CELL1 and the control plane is correctly configured. Originate a cross-Iur
handover. If the handover is successful, the AAL2 path on the Iur interface is set up
successfully.
l Deactivation Procedure
This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030105
Permanent AAL5 Connections for Control Plane Traffic.
Prerequisite
l Dependencies on Hardware
BTS3902E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l 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 (UNI-
SAAL) 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.
2. Optional: Run the BSC6900 MML command ADD UNCP to add a NodeB Control
Port (NCP) link.
3. 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.
l 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.
l Deactivation Procedure
NOTE
An SAAL link can carry only one NCP or CCP link. Therefore, choose to remove the NCP or CCP
link carried by the SAAL link, based on the actual situation.
1. Optional: Run the BSC6900 MML command RMV UNCP to remove the NCP link
carried by the SAAL link.
2. Optional: Run the BSC6900 MML command RMV UCCP to remove the CCP link
carried by the SAAL link.
3. Run the BSC6900 MML command RMV SAALLNK to remove the SAAL link.
----End
Example
//Activating Permanent AAL5 Connections for Control Plane Traffic
ADD SAALLNK: SRN=1, SN=2, SAALLNKN=10, CARRYT=UNI, CARRYSRN=0,
CARRYSN=14, CARRYUNILNKN=2, CARRYVPI=10, CARRYVCI=55, TXTRFX=100,
RXTRFX=100, SAALLNKT=UNI;
ADD UCCP: NODEBNAME="NodeB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=10;
//Verifying Permanent AAL5 Connections for Control Plane Traffic
DSP SAALLNK: SRN=1, SN=2, SAALLNKN=10;
//Deactivating Permanent AAL5 Connections for Control Plane Traffic
RMV UCCP: NODEBNAME="NodeB1", PN=0;
RMV SAALLNK: SRN=1, SN=2, SAALLNKN=10;
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030106
Call Admission Based on Used AAL2 Path Bandwidth.
Prerequisite
l Dependencies on Hardware
BTS3902E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
2. 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.
l Verification Procedure
1. Assume that the verification is based on the preceding parameter settings and the peer
end is configured with the corresponding AAL2 path link. Originate a PS interactive
service. If the data rate is 64 kbit/s, the UE successfully accesses the network.
2. Run the BSC6900 MML command DSP AAL2PATH to view that the used bandwidth
of the path is about 37 kbit/s, which is the admission bandwidth of the control plane.
3. Originate a PS interactive service. If the data rate is 128 kbit/s, the UE fails to access
the network.
l Deactivation Procedure
This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the basic feature
"WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes".
Prerequisite
l Dependencies on Hardware
BTS3902E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
Huawei RAN supports service type of ATM :
l Constant Bit Rate (CBR)
l Real time Variable Bit Rate (rt-VBR)
l Non-real time Variable Bit Rate (nrt-VBR)
l Unspecified Bit Rate (UBR)
l 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.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command ADD ATMTRF to add an ATM traffic record.
To add more ATM traffic records, run this command repeatedly.
l Verification Procedure
1. 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.
l Deactivation Procedure
1. 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;
42 Configuring F5
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110
F5.
Prerequisite
l Dependencies on Hardware
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.
BTS3902E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l The basic information about the BSC6900 is configured. For details, see the Configuring
the Basic Data.
l The SAALLNK, AAL2PATH, or IPOAPVC link exists.
Context
This feature supports:
l ATM CC provides E2E continuity detection on the VCL.
l PM function provides performance monitoring on the VCL.
l 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.
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.
l Verification Procedure
1. Run the BSC6900 MML command DSP VCLCC to query the CC result of a VCL.
If the VCL CC is activated and the PVC is functional, the SINK activated state
and SOURCE activated state are UP, and LOC, AIS, and RDI alarm state is
normal.
If the loopback is activated and the PVC is functional, the loopback query result
is UP, and LOC, AIS, and RDI alarm state is normal.
2. Run the BSC6900 MML command DSP VCLPM to query the PM result of a VCL.
If the VCL PM is activated, the SINK activated state and SOURCE activated
state are PM_UP, and PM Active Fail Alarm is Normal.
l 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.
2. Run the BSC6900 MML command DEA VCLPM to deactivate the VCL PM for a
link. To deactivate the function for multiple links, run this command repeatedly. There
are three types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.
----End
Example
//Activating F5
ACT VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0, VCLTYPE=CC;
ACT VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
//Verifying F5
DSP VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
DSP VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
//Deactivating F5
DEA VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
DEA VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
This section describes how to activate, verify, and deactivate the basic feature "WRFD-050305
UBR+ ATM QoS Class".
Prerequisite
l Dependencies on Hardware
BTS3902E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l 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. 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.
l Verification Procedure
1. Run the MML command LST ATMTRF to query the ATM traffic configuration.
Expected result: The query result is consistent with the configuration information.
l Deactivation Procedure
1. 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.
----End
Example
//Adding UBR+ ATM QoS Class
ADD ATMTRF: TRFX=105, ST=UBR_PLUS, UT=CELL/S, MCR=100;
//Verifying UBR+ ATM QoS Class
LST ATMTRF: TRFX=105;
//Deactivating UBR+ ATM QoS Class
RMV ATMTRF: TRFX=105;
This section describes how to activate, verify, and deactivate the basic feature WRFD-040100
Flow Control.
Prerequisite
l Dependencies on Hardware
NodeB RRC link priority based flow control is depended on WMPT and WBBP boards.
l Dependencies on Other Features
This feature does not depend on other features.
l License
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.
Procedure
l Activation Procedure
Activating board flow control
1. Run the BSC6900 MML command SET FCSW to switch on the flow control and
related flow control items.
2. Run the BSC6900 MML command SET FCCPUTHD to configure the CPU usage
threshold for each flow control item according to the network plan.
NOTE
l Flow control is triggered when the CPU usage exceeds the related threshold.
l The CPU usage thresholds must meet the following condition: 100 Critical threshold
Threshold for a flow control item Restore threshold for a flow control item
l The critical threshold is of the highest priority. That is, other thresholds take effect only
when the CPU usage is lower than the critical threshold.
l The flow control based on the packet usage and that based on the CPU usage are independent.
The system limits the flow to the lower one allowed by these two flow control algorithms.
3. Run the BSC6900 MML command SET FCMSGQTHD 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. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set
Process switch to RNC_SHARE_SWITCH to switch on load sharing.
2. (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.
Activating flow control based on RRC request queuing
1. Run the BSC6900 MML command SET UCACALGOSWITCH. In this step,
select RSVDBIT14 in Reserved parameter 1.
Activating flow control based on MPU load
1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, select
RSVDBIT1_BIT19 in Reserved parameter 1.
Activating flow control based on traffic growth
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.
l Verification Procedure
Verifying board flow control
1. Run the BSC6900 MML command LST FCSW to query the state of the flow
control switch.
2. Run the BSC6900 MML command LST FCCPUTHD to query the CPU usage
threshold for flow control.
3. Run the BSC6900 MML command LST FCMSGQTHD to query the packet usage
threshold for flow control.
Verifying control-plane and user-plane load sharing
1. On the LMT, choose Monitor > Common Monitoring > CPU/DSP Usage
Monitoring to observe the CPU usage of each subsystem. If the CPU usage of
each subsystem is almost the same, load sharing takes effect.
Verifying flow control based on RRC request queuing
1. Run the BSC6900 MML command LST UCACALGOSWITCH to query the
state of the switch for flow control based on RRC request queuing.
Verifying flow control based on MPU load
1. Run the BSC6900 MML command LST URRCTRLSWITCH to query the state
of the switch for flow control based on MPU load.
Verifying flow control based on traffic growth
1. Run the BSC6900 MML command LST UCALLSHOCKCTRL to query the
state of the switch for flow control based on traffic growth.
l Deactivation Procedure
Deactivating board flow control
1. Run the BSC6900 MML command SET FCSW to switch off flow control.
Deactivating control-plane load sharing
1. Run the BSC6900 MML command SET URRCTRLSWITCH to deselect
RNC_SHARE_SWITCH in Process switch.
Deactivating user-plane load sharing
1. User-plane load sharing does not need to be deactivated.
Deactivating flow control based on RRC request queuing
1. Run the BSC6900 MML command SET UCACALGOSWITCH. In this step,
deselect RSVDBIT14 in Reserved parameter 1.
Deactivating flow control based on MPU load
1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step,
deselect RSVDBIT1_BIT19 in Reserved parameter 1.
Deactivating flow control based on traffic growth
1. Run the BSC6900 MML command SET UCALLSHOCKCTRL. In this step,
deselect CELL_LEVEL in Call Shock Control Switch.
----End
Example
//Activating board flow control
//Switching on XPU load 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.
Prerequisite
l Dependencies on Hardware
The transmission equipment is in the connected state.
BOOTP applies only to ATM networking scenarios.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
2. Run the BSC6900 MML command ADD IPOAPVC to add the IPoA PVC for bearing
the OM channel.
3. Run the BSC6900 MML command ADD UNODEBIP to add the IP address for the
OM channel of the NodeB.
l Verification Procedure
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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-031101
NodeB Self-discovery Based on IP Mode.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
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.
l 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. Run the BSC6900 MML command ADD UNODEBESN to add the NodeB ESN in
response to the DHCP request reported by the NodeB.
2. 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.
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.
l 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.
l 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";
This section describes how to activate, verify, and deactivate the basic feature WRFD-040300
License Control for Urgency.
Prerequisite
l Dependencies on Hardware
Since RAN13.0, both BSC6900 and NodeB support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. On the BSC6900 side: Run the BSC6900 MML command SET LICENSECTRL. In
this step, set Grace Protection Period Switch to ON(ON).
2. On the NodeB V200R013 side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch State to ON.
3. On the NodeB V100R013 side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch to ON(ON).
l Verification Procedure
1. 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.
l Deactivation Procedure
1. On the BSC6900 Side: Run the BSC6900 MML command SET LICENSECTRL.
In this step, set Grace Protection Period Switch to OFF(OFF).
2. On the NodeB V200R013 Side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch State to OFF.
3. On the NodeB V100R013 Side: Run the NodeB MML command SET
LICENSECTRL. In this step, set Grace Protection Period Switch to OFF(OFF).
----End
This section describes how to activate, verify, and deactivate the basic feature WRFD-031000
Intelligently Out of Service.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. Run the NodeB MML command SET SMTHPWRSWTCH. In this step, set Smooth
Power Change Function Switch to OPEN(Open).
2. Run the NodeB MML command SET SMTHPWRPARA. In this step, set Smart
default step(0.5dB) and Smart default time ratio(100ms).
l Verification Procedure
1. Run the NodeB MML command LST SMTHPWRSWTCH. In this step, check
whether Smooth Power Change Function Switch is set to OPEN.
2. 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.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
Example
//Activation procedure
SET SMTHPWRSWTCH: SWITCH=OPEN;
SET SMTHPWRPARA: STEP=10, PERIOD=1;
//Verification procedure
LST SMTHPWRSWTCH:;
LST SMTHPWRPARA:;
49 Configuring OCNS
This section describes how to activate, verify, and deactivate the basic feature WRFD-031200
OCNS (Orthogonal Channel Noise Simulator).
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
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.
l Verification Procedure
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.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-031400
Power Off the Equipment Level by Level.
Prerequisite
l Dependencies on Hardware
Cabinets providing AC input power such as APM30, APM100, and APM200. These
cabinets can be used for outdoor NodeBs.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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. 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.
2. 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).
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. Run the NodeB MML command MOD BATTERY and set Low Voltage Shutdown
Flag to DISABLE(Disable).
2. Run the NodeB MML command MOD PMU and set Load Shutdown Flag to
DISABLE(Disable).
l 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;
l 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-031500
Solar Power Device Management.
Prerequisite
l Dependencies on Hardware
Only 3900 series base stations support the feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. Run the NodeB MML command ADD PMU to add a PMU. In this step, set Power
System Type to SC48200.
2. Optional: If a diesel generator is required, run the NodeB MML command ADD
DIESELGEN.
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.
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;
This section describes how to activate, verify, and deactivate the basic feature MRFD-210601
Connection with TMA (Tower Mounted Amplifier).
Prerequisite
l Dependencies on Hardware
The base station is connected to the Antenna Line Device (ALD) normally.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l 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. Run the NodeB MML command MOD ANTENNAPORT to set ALD Power
Switch to ON.
2. Run the NodeB MML command SCN ALD to scan the Device Name, Vendor
Code and Serial No..
3. Run the NodeB MML command ADD TMA to add a TMA.
4. If the device supports TMA gain, run the NodeB MML command MOD
TMASUBUNIT to set the TMA gain.
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. Run the NodeB MML command SET ALDPWRSW to set Power Supply Switch to
ON(On).
2. Run the NodeB MML command SCN ALD to scan Device Name, Vendor Code and
Serial No..
3. Run the NodeB MML command ADD ALD to add a TMA.
4. 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. Run the NodeB MML command LST TMAGAIN to query the TMA gain.
2. Run the NodeB MML command LST RXATTEN to query the RX attenuation value.
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 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;
This section describes how to activate, verify, and deactivate the basic feature MRFD-210602
Remote Electrical Tilt.
Prerequisite
l 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.
l Dependencies on Other Features
This feature does not depend on other features.
l 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 Calibrating the RET antenna may affect its coverage for a short period of time.
l Calibrating an RET antenna takes up to 4 minutes.
Procedure
l NodeB V200R013
Activation Procedure
1. If the antenna port is used, run the NodeB MML command MOD
ANTENNAPORT. In this step, set ALD Power Switch to ON.
2. If the RET antenna port is used, run the NodeB MML command MOD RETPORT.
In this step, set ALD Power Switch to ON.
3. Run the NodeB MML command SCN ALD to obtain the ESN of an ALD.
4. Run the NodeB MML command ADD RET to add an RET antenna.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
5. Run the NodeB MML command CLB RET to calibrate the RET antenna.
6. Run the NodeB MML command MOD RETSUBUNIT to modify parameters
concerning an RET antenna subunit.
7. Run the NodeB MML command MOD RETDEVICEDATA to modify parameters
concerning the attributes of an RET device.
8. Run the NodeB MML command MOD RETTILT to modify the tilt of the RET
antenna.
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. Run the NodeB MML command DSP RET to query information about the RET
antenna.
4. Run the NodeB MML command DSP RETSUBUNIT to query the dynamic
information on an RET antenna subunit and an RET antenna's tilt.
Deactivation Procedure
This feature does not need to be deactivated.
l NodeB V100R013
Activation Procedure
1. Run the NodeB MML command SET ALDPWRSW. In this step, set Power Supply
Switch to ON.
2. Run the NodeB MML command SCN ALD to obtain the ESN of an ALD.
3. Run the NodeB MML command ADD ALD to add an antenna device.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
4. Run the NodeB MML command CLB ANT to calibrate the antenna device.
5. Run the NodeB MML command SET ANTTILT to set the tilt of antenna device.
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;
l 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-060003
Configuring Same Band Antenna Sharing Unit (900 MHz).
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
l The introduction of the feature enables UMTS900 and GSM900 to share the same antenna.
l 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. Run the NodeB MML command MOD ANTENNAPORT to set ALD Power
Switch to ON.
2. Run the NodeB MML command SCN ALD to scan antenna devices and obtain the
serial number of the SASU.
3. Run the NodeB MML command ADD SASU to configure the SASU and set the
antenna DC power switch state of the SASU.
4. Run the NodeB MML command MOD SASUSUBUNIT to set the SASU working
mode and the gain of the SASU.
Verification Procedure
1. Run the NodeB MML command DSP SASU to query the antenna DC power switch
state of the SASU.
2. Run the NodeB MML command DSP SASUSUBUNIT to query the SASU working
mode and the gain of the SASU.
l NodeB V100R013
Activation Procedure
1. Run the NodeB MML command SET ALDPWRSW to turn on the power supply
switch of the SASU (Same band Antenna Sharing Unit) port.
2. Run the NodeB MML command SCN ALD to scan antenna devices and obtain the
serial number of the SASU.
3. Run the NodeB MML command ADD ALD to configure the SASU.
4. Run the NodeB MML command SET SASUMODE to set the SASU working mode.
5. Run the NodeB MML command SET SASUGAIN to set the gain of the SASU.
6. Run the NodeB MML command SET SASUDCSW to set the antenna DC power
switch state of the SASU.
7. Run the NodeB MML command SET SASUDCLD to set the DC load of the SASU.
Verification Procedure
1. Run the NodeB MML command LST ALD to query the configuration information
about the SASU.
2. Run the NodeB MML command LST SASUMODE to query the SASU working
mode.
3. Run the NodeB MML command LST SASUGAIN to query the gain of the SASU.
4. Run the NodeB MML command LST SASUDCSW to query the antenna DC power
switch state of the SASU.
5. Run the NodeB MML command LST SASUDCLD to query the DC load of the SASU.
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;
l NodeB V100R013
//Activation procedure
SET ALDPWRSW: CN=0, SRN=60, CASE=REGULAR, AST=CUSTOM, PSP=R0A,
This section describes how to activate, verify, and deactivate the optional feature WRFD-010615
Multiple RAB Package (PS RAB 2).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l Other Prerequisites
The CN node and UE must have the corresponding multi-RAB support capability.
Context
With the Multiple RAB feature, operators have relatively diversified choices of service solutions.
If the Multiple RAB feature is enabled, a large quantity of services can be provided for the upper
layers. Huawei products support the following solutions with more than one PS RAB:
l Combination of two PS services
l Combination of one CS service and two PS services
l Combination of three PS services
l Combination of one CS service and three PS services
l 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.
l Verification Procedure
1. Details see the verification procedure of following features: 56 Configuring
Combination of Two PS Services, 57 Configuring Combination of One CS Service
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061501 Combination of Two PS Services.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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.
l Verification Procedure
1. Connect the UE to the portable computer so as to use the UE as a modem.
2. Visit the Internet on the UE. Verify that web pages are displayed normally.
3. On the portable computer, connect to an FTP server and download data. Verify that
the data is downloaded normally.
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 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061502 Combination of One CS Service and Two PS Services.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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
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.
l Verification Procedure
1. Have two UEs ready: UE 1 and UE 2.
2. Connect UE 1 to the portable computer so as to use the UE 1 as a modem.
3. Visit the Internet on UE 1. Verify that web pages are displayed normally (a PS
Service).
4. On the portable computer, connect to an FTP server and download data. Verify that
the data is downloaded normally (a PS Service).
5. Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable (a
CS Service).
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 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061503 Combination of Three PS Services.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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
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.
l Verification Procedure
1. Connect UE to the portable computer so as to use the UE as a modem.
2. Visit the Internet on UE. Verify that web pages are displayed normally.
3. Visit the Multimedia service on the UE. Verify that this service is played normally.
4. On the portable computer, connect to an FTP server and download data. Verify that
the data is downloaded normally.
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 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061504 Combination of One CS Service and Three PS Services.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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
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.
l Verification Procedure
1. Have two UEs ready: UE 1 and UE 2.
2. Connect UE 1 to the portable computer so as to use the UE 1 as a modem.
3. Visit the Internet on UE 1. Verify that web pages are displayed normally (a PS
Service).
4. Visit the Multimedia service on the UE 1. Verify that this service is played normally
(a PS Service).
5. On the portable computer, connect to an FTP server and download data. Verify that
the data is downloaded normally (a PS Service).
6. Use UE 2 to call UE 1. Verify that UE 1 rings and the speech quality is acceptable (a
CS Service).
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 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061505 Combination of Four PS Services.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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.
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.
2. Run the BSC6900 MML command SET UFRCCHLTYPEPARA command to set
the VOIP channel type parameter to DCH(UL_DCH,DL_DCH).
NOTE
The BSC6900 defines the default value of the VOIP channel type parameter. Retain the default value
in normal situations.
l Verification Procedure
1. Initiate Iu interface tracing on the BSC6900 LMT.
2. Connect the UE to the portable computer so as to use the UE as a modem.
3. Establish a VoIP service on the UE. View the
RANAP_RAB_ASSIGNMENT_REQ message traced on the Iu interface. If you
find that the CN assigns three RABs at the same time, you can infer that the VoIP
service is established successfully. (If RTCP is assigned, SIP signaling and RTP must
be assigned at the same time.)
4. On the portable computer, connect to an FTP server and download data. Verify that
the data is downloaded normally.
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 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010610
HSDPA Introduction Package.
Prerequisite
l Dependencies on Hardware
NDLP and NBBI in the NodeB do not support this feature.
l 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 License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command ADD UCELLHSDPA to set HSDPA-related
parameters based on the network plan.
2. Run the BSC6900 MML command ACT UCELLHSDPA to activate this feature.
3. Configure Iub transport for HSDPA.
In an ATM network:
(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.
l 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.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELLHSDPA to deactivate this feature.
2. Run the BSC6900 MML command DSP UCELL to check whether the HSDPA
feature is deactivated. If HSDPA Operational State is set to Disabled, this feature
has been deactivated.
----End
Example
// Setting HSDPA-related parameters
ADD UCELLHSDPA: CellId=3000, AllocCodeMode=Automatic,
HsPdschMaxCodeNum=4, HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON;
//Activating HSDPA Introduction Package
ACT UCELLHSDPA: CellId=3000;
//Configuring Iub transport for HSDPA
//ATM network
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061001 15 Codes per Cell.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
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 HS-
SCCHs.
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. Run the BSC6900 MML command MOD UCELLHSDPA to set Allocate Code
Mode to Manual(Manual) and Code Number for HS-PDSCH to 15.
l Verification Procedure
1. Initialize UMTS monitoring on the BSC6900 LMT, as shown in Figure 62-1. Click
Submit. A real-time monitoring window is displayed.
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.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
//Verifying 15 Codes per Cell
MOD UCELLHSDPA: CellId=1, HsScchCodeNum=1;
MOD UCELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=15;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l 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 Activation Procedure
This feature does not need to be activated.
l Verification Procedure
This feature does not need to be verified.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been activated.
Context
Huawei provides multiple HSDPA scheduling algorithms such as maximum C/I (MAXCI),
round-robin (RR), proportional fair (PF), and Enhanced Proportional Fair (EPF).Before the
HSDPA feature is enabled, HARQ must be enabled and HSDPA scheduling algorithms must be
set.
Procedure
l Activation Procedure
NOTE
1. Run the NodeB MML command LST MACHSPARA to query the settings of the
parameter Scheduling Method.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
Example
//Activation procedure
SET MACHSPARA: LOCELL=0, SM=MAXCI;
//Verification procedure
LST MACHSPARA: LOCELL=0;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code
Allocation.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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 RNC-
controlled 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 HS-
PDSCH to specify the maximum number of HS-PDSCH codes and set Code Min
Number for HS-PDSCH to specify the minimum number of HS-PDSCH codes.
l Verification Procedure
1. Run the BSC6900 MML command LST UCELLHSDPA to query code allocation
mode.
2. On the BSC6900 LMT, click to display Cell Performance Monitoring. Set Monitor
Item to Cell Code Tree Monitor and click Submit. The Cell Performance Monitoring
tab page is displayed.
3. View the number of codes allocated to the HS-PDSCH in the cell. If Allocate Code
Mode is set to Manual, the monitoring window of cell code tree usage shows that the
number of codes allocated to the HS-PDSCH remains unchanged. If Allocate Code
Mode is set to Automatic, the monitoring window of cell code tree usage shows that
the number of codes allocated to the HS-PDSCH varies with service access requests
in the cell. For example, the number of codes allocated to the HS-PDSCH increases
with the increase of HSDPA access requests and decreases with the decrease of
HSDPA access requests.
l Deactivation Procedure
This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061004 HSDPA Power Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package must be configured before
this feature is configured.
l License
The license controlling this feature has been activated.
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)
(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 HS-
SCCH 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 HS-
SCCH 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061003 HSDPA Admission Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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 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.
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.
NOTE
The Iub interface bandwidth can be changed by running the BSC6900 MML command MOD
IPPATH or MOD AAL2PATH.
l Verification Procedure
1. Enable two UEs UE1 and UE2 in idle mode to camp on the test cell, and the test cell
must support HSDPA.
2. On the HLR, set PS service type to background or interactive.
3. Run the BSC6900 MML command MOD UCELLCAC to set the maximum number
of HSDPA users to 1.
4. Use UE1 to initiate an HSDPA PS service. After the service is set up successfully,
check the RRC_RB_SETUP message over the Uu interface. You can view that the
new-H-RNTI IE is under the rb-mappinginfo IE, and the value of the dl-
TransportChannel-Type IE is hsdsch.
5. Use UE2 to initiate an HSDPA PS service. The service should fail to set up. Check
the RRC_RB_SETUP message over the Uu interface. You can view that the new-H-
RNTI IE is not under the rb-mappinginfo IE, and the value of the dl-
TransportChannel-Type IE is dch.
6. Release all the PS services.
7. Run the BSC6900 MML command MOD UCELLCAC. In this step, set Maximum
HSDPA user number of the test cell to 64.
8. Use UE1 and UE2 to initiate an HSDPA PS service.
Expected result: Services are set up successfully on UE1 and UE2.
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.
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061010 HSDPA Flow Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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
For each MAC-hs queue, HSDPA Flow Control calculates the pre-allocated Iub bandwidth based
on the Uu transmission rate and the amount of data buffered in the NodeB. The Uu transmission
rate of the MAC-hs queue is determined by the scheduling algorithm. For each MAC-hs queue,
if the Iub transmission rate is higher than the Uu transmission rate, the data packets are buffered.
Too much data buffered in the NodeB leads to transmission delay and even packet loss.
Therefore, each MAC-hs queue should not have too much data buffered in the NodeB. However,
it should retain a certain amount of data to prevent wasting the Uu resources due to not having
data to transmit.
The procedure for HSDPA Flow Control is briefly described as follows:
1. The NodeB measures the buffered data amount of each MAC-hs queue and the average Uu
transmission rate.
2. The NodeB estimates the buffering time based on the measurements.
3. The NodeB adjusts the Iub bandwidth pre-allocated to the MAC-hs queue.
Procedure
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.
Expected result:
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
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061006 HSDPA Mobility Management.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 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
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061002 HSDPA UE Category 1 to 28.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature can provide proper HSDPA services for the UEs of category 1 to category 28.
Procedure
l Activation Procedure
This feature does not need to be activated.
l Verification Procedure
This feature does not need to be verified.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061020 Improvement of User Experience in Low Traffic Service.
Prerequisite
l 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.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
WRFD-010612 HSUPA Introduction Package
l License
The license controlling this feature has been activated.
l 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 The NodeB detects HSPA services with low traffic, such as gaming services and instant
messaging services (such as MSN).
l 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 Activation Procedure
1. 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.
l Verification Procedure
1. Run the NodeB MML command LST UEQOSENHANCEPARA to query the burst
packet sizes of the gold, silver, and copper users.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010629
16QAM Modulation.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l License
The license controlling this feature has been activated.
l 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 The HS-PDSCH is used to carry the HS-DSCH data. The HS-PDSCH may use QPSK or
16QAM modulation symbols.
l 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.
l 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.
l 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
l Activation 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. Run the NodeB MML command SET MACHSPARA. In this step, set 16QAM
Switch to OPEN(open).
l Verification Procedure
NOTE
l For the 16QAM modulation of the HSDPA UE, the NodeB license control item must be enabled.
l As defined in 3GPP 25.306, the UE in category 8 can support both QPSK and 16QAM modulation
schemes. Only 16QAM modulation, however, enables the throughput of category 8 UE to reach
5 Mbit/s.
NOTE
Only in case of good environment quality of the channel, the throughput of category 8 UE can
reach 5 Mbit/s.
Perform the following steps to check whether the download rate can reach 5 Mbit/s.
1. Use the UE to start a PS interactive service of DL 7200 kbit/s. The PS service is carried
on the HS-DSCH. The UE keeps in Cell-DCH state.
2. Start FTP (10 threads) to download given files, which are larger than 1 GB. By
monitoring the DL throughput and bandwidth, you find that the PS downloading
service is normal and the bit rate is higher than 5 Mbit/s.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010631
Dynamic Code Allocation Based on NodeB.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l 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
l Activation 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. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic
Code Switch to OPEN(open).
l Verification Procedure
1. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic
Code Switch to CLOSE(close).
2. Run the BSC6900 MML command MOD UCELLHSDPA.
set Allocate Code Mode to Manual.
6. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic
Code Switch to OPEN(open).
7. Trace (DL)Hsdpa User Enhanced Schedule Data message,
ucMaxPdschCodeNum is less than the value of 5, it indicates the feature has been
enabled. as shown in Figure 73-3.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010611
HSDPA Enhanced Package.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
l 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:
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
NOTE
HS-DPCCH Preamble Support does not need to be activated, verified, or deactivated.
----End
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061103 Scheduling based on EPF and GBR.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l 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. Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling
Method to EPF(Enhanced PF).
l Verification Procedure
1. Run the NodeB MML command LST MACHSPARA to check that Scheduling
Method is set to EPF.
l Deactivation Procedure
1. Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling
Method to an option other than EPF(Enhanced PF).
----End
Example
//Activation procedure
SET MACHSPARA: SM=EPF;
//Verification procedure
LST MACHSPARA;
//Deactivation procedure
SET MACHSPARA: SM=PF;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061111 HSDPA State Transition.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
Context
l This feature enables the switching between the DCH and HS-DSCH and makes it possible
for UEs to enjoy high-speed services.
l 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.
l Verification Procedure
1. Log in to the BSC6900 LMT and initiate Uu interface message tracing.
2. Set up an HSDPA BE service, and do not perform any data operation for a period of
time. Then, search for the RRC_RB_RECFG in the traced Uu interface message.
Check the traced data to ensure that the value of the IE rrc-StateIndicator is cell-FACH
(1), as shown in Figure 76-1.
l 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061112 HSDPA DRD.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been activated.
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.
l Verification Procedure
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check
whether DR_RAB_SING_DRD_SWITCH or
DR_RAB_COMB_DRD_SWITCH is set to ON.
Expected result: The value of DR_RAB_SING_DRD_SWITCH or
DR_RAB_COMB_DRD_SWITCH is ON.
2. Run the BSC6900 MML command LST UINTERFREQNCELL to query the inter-
frequency neighboring cells of cell 1 and whether Blind handover flag is set to
TRUE. If Blind handover flag is set to FALSE, run the BSC6900 MML command
MOD UINTERFREQNCELL. In this step, set Blind Handover Flag of cell 2 (inter-
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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010630
Interactive and Background Traffic Class on HSDPA.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature enables the streaming services to be mapped onto the HS-DSCH, which improves
the utilization of cell resources.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to select
MAP_PS_STREAM_ON_HSDPA_SWITCH from the drop-down list Service
mapping strategy switch.
l Verification Procedure
1. Initiate Uu interface tracing on the BSC6900 LMT, as shown in Figure 78-1.
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 dl-
TransportChannelType in the rb-MappingInfo information element (IE) is set to
hsdsch in the Uu interface trace data.
3. Check whether the service can receive the data successfully.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to clear
MAP_PS_STREAM_ON_HSDPA_SWITCH from the drop-down list Service
mapping strategy switch.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010651
HSDPA over Iur.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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.
2. Run the BSC6900 MML command MOD UNRNC. In this step, set Hsdpa cap ind
over IUR for NRNC to ON.
l Verification Procedure
1. Verify that the feature HSDPA over Iur has been activated by performing the following
operations:
Run the BSC6900 MML command LST UNRNC to query the configuration of
the neighboring RNC.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010652
SRB over HSDPA.
Prerequisite
l 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.
l Dependencies on Other Features
The WRFD-010610 HSDPA Introduction Package feature must be configured before
this feature is configured.
l License
The license controlling this feature has been activated.
l 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. Run the MML command SET UFRCCHLTYPEPARA on the BSC6900. In this step,
set Type of Channel Preferably Carrying Signaling RB to HSDPA or HSPA.
2. 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
2. To verify whether this feature is activated , view the information element (IE) dl-
TransportChannelType and rb-Identity in the RRC_RB SETUP message from the
Uu interface trace data.
l 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 type of channel on which SRBs are preferably carried with
SrbChlType set to DCH
SET UFRCCHLTYPEPARA: SrbChlType=DCH;
This section describes how to activate, verify, and deactivate the basic feature WRFD-030010
CQI Adjustment Based on Dynamic BLER Target.
Prerequisite
l 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 Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l 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).
l Verification Procedure
1. Run the NodeB MML command LST MACHSPARA. In this step, check that CQI
Adjust Algorithm Switch of non-Conversational Service is set to
CQI_ADJ_BY_DYN_BLER.
2. 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
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010612
HSUPA Introduction Package.
Prerequisite
l Dependencies on Hardware
The NBBI and the NULP do not support this feature.
The UE supports the HSUPA function.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. Run the BSC6900 MML command ADD UCELLHSUPA to add HSUPA functions
of a cell.
2. Run the BSC6900 MML command ACT UCELLHSUPA to activate the HSUPA
function of the cell.
l Verification Procedure
1. Ensure that the HSUPA function of the cell is activated.
Run the BSC6900 MML command DSP UCELL to verify that the HSUPA function
of the cell is activated.
2. Establish a PS service.
The IE E-DCH FDD information in the RL SETUP message on the Iub interface and
the IE rb-mappinginfo in the RRC_RB_SETUP message on the Uu interface should
indicate that the service has been set up and carried on the E-DCH.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELLHSUPA to deactivate the HSUPA
function of the cell.
2. Run the BSC6900 MML command RMV UCELLHSUPA to remove the HSUPA
functions of a cell.
----End
Example
//Activating HSUPA Introduction Package
ADD UCELLHSUPA: CellId=111;
ACT UCELLHSUPA: CellId=111;
//Verifying HSUPA Introduction Package
DSP UCELL: DSPT=BYCELL, CellId=111;
//Deactivating HSUPA Introduction Package
DEA UCELLHSUPA: CellId=111;
RMV UCELLHSUPA: CellId=111;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061202 HSUPA Admission Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been 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.
l Verification Procedure
1. UE1 and UE2 are in idle state and camp on CELL_A11. CELL_A11 supports HSUPA.
2. On the HLR, set the PS service type to background or interactive.
3. Run the BSC6900 MML command MOD UCELLCAC to set the maximum number
of HSUPA users supported by CELL_A11 to 1.
4. Establish an HSUPA PS service on UE1, and then check the rb-mappinginfo
information element in the RRC_RB_SETUP message traced over the Uu interface.
The value of ul-TrCH-Type is e-dch.
5. Establish an HSUPA PS service on UE2, and then check the rb-mappinginfo
information element in the RRC_RB_SETUP message traced over the Uu interface.
The value of rrc-Stateinditator is CELL_DCH.
6. Release all PS services.
7. Run the BSC6900 MML command MOD UCELLCAC to set Maximum HSUPA
user number of CELL_A11 to 20.
8. Establish an HSUPA PS service on UE1 and UE2 respectively.
Expected result: An HSUPA PS service is successfully established on UE1 and UE2
respectively.
9. Run the following command to check whether Iub resource admission is activated.
Run the BSC6900 MML command DSP IPPATH or DSP AAL2PATH to check
whether any bandwidth is occupied.
l 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:
(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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061203 HSUPA Power Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been 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 E-
HICH HPC Parameters for Service Radio Links Set to YES.
2. 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.
3. 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 E-
HICH Power Offset for Single Radio Link(0.25dB) to appropriate values according
to the network plan.
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061204 HSUPA Mobility Management.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been 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
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061208 HSUPA DCCC.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been 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.
2. 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.
3. Optional: Run the BSC6900 MML command SET UDCCC. In this step, select
RATE_UP_AND_DOWN_ON_EDCH from the HSUPA DCCC Strategy drop-
down list so that the data rate of HSUPA services on the EDCH can increase or
decrease.
NOTE
After the preceding optional step is performed, the data rate of HSUPA services on the EDCH can
increase or decrease as required. If the data rate of HSUPA services on the EDCH is expected to
increase only, select RATE_UP_ONLY_ON_EDCH from the HSUPA DCCC Strategy drop-
down 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.
l 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.
2. Make the UE establish an HSUPA Best Effort (BE) service. After the service is
established, layer 3 of the RNC sends an uplink throughput measurement control
message to layer 2.
3. Upload a large file for a period of time. Then, view the RRC_RB_RECFG message
on the Uu interface and check that the data rate increases. In UL Throughput
Bandwidth of Connection Performance Monitoring, the bandwidth increases.
4. Stop the data upload and wait for a period of time. Then, view the RRC_RB_RECFG
message on the Uu interface and check that the data rate decreases. In UL Throughput
Bandwidth of Connection Performance Monitoring, the bandwidth decreases.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
deselect DRA_HSUPA_DCCC_SWITCH from the Dynamic Resource Allocation
Switch drop-down list.
----End
Example
//Activating HSUPA DCCC
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1;
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_608KBPS-
1&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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061211 20 HSUPA Users per Cell.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package must be configured before
this feature is activated.
l 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.
2. Run the BSC6900 MML command MOD UCELLCAC to set the maximum number
of HSUPA users supported by the cell to 20.
l Verification Procedure
1. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance
Monitoring in the Monitor Navigation Tree pane. In the displayed Cell
Performance Monitoring dialog box, set Monitor Item to Cell User Number.
2. Use UEs to access the cell one by one. Then, make UEs establish PS services, for
example, upload files through FTP.
Expected result: Each UE establishes PS services successfully.
If the number of UEs is less than or equal to 20, uplink services are carried on
HSUPA channels and downlink services are carried on HSDPA channels.
If the number of UEs is greater than 20, HSPA services of the excessive UEs are
carried on R99 channels.
3. View the maximum number of users indicated by the counter
VS.HSUPA.UE.Max.Cell on the M2000.
NOTE
The 20 HSUPA users referred to in this feature are of the SRB Over HSPA type.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061401 E-AGCH Power Control (Based on CQI or HS-SCCH).
Prerequisite
l Dependencies on Hardware
This feature does not depend on hardware.
l 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.
l License
The license controlling this feature has been activated.
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. Use an HSUPA-capable UE to perform PS services over the E-DCH.
2. Move the UE and observe power changes on each channel carrying HSUPA services.
Expected result:
When the UE moves away from the antenna, the transmit power of the E-AGCH
increases.
When the UE moves towards the antenna, the transmit power of the E-AGCH
decreases.
l 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061403 HSUPA 2ms TTI.
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, 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.
l 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 License
The license controlling this feature has been activated.
l 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.
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.
3. Configure SRB over HSPA by referring to 95 Configuring SRB over HSUPA.
l Verification Procedure
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify that
the MAP_HSUPA_TTI_2MS_SWITCH check box is selected.
2. Use an HSPA-capable UE to establish an HSUPA service. If the
RRC_RB_SETUP message shown in Figure 89-1 is traced on the Uu interface, an
HSUPA service with 2 ms TTI has been set up on the E-DCH.
l 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
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061404 HSUPA 2 ms/10 ms TTI Handover.
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, 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.
l Dependencies on Other Features
The feature WRFD-010614 HSUPA Phase 2 has been configured before this feature is
activated.
l License
The license controlling this feature has been 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.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
Example
//Activating HSUPA 2 ms/10 ms TTI Handover
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES,
FUNCTIONSWITCH3=HSUPA_2ms_10ms-1;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061405 HSUPA 5.74Mbps per User.
Prerequisite
l 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.
l Dependencies on Other Features
The feature WRFD-010636 SRB over HSUPA has been configured before this feature
is activated.
l License
The license controlling this feature has been activated.
l 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.
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.
3. 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).
l Verification Procedure
1. Use an HSPA-capable UE to establish a PS service on the E-DCH and HS-DSCH.
2. Start Uu interface tracing on the BSC6900 LMT. The RRC_RB_SETUP message
shows that the 2 ms TTI is used in the uplink and the maximum channelization code
IE is 2SF2+2SF4.
3. The real-time monitoring result of UL Throughput & Bandwidth on the BSC6900
side shows that the bandwidth is 5440 kbit/s and that upload through FTP is normal.
l Deactivation Procedure
1. 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.
2. 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).
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010632
Streaming Traffic Class on HSUPA.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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.
2. 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.
l Verification Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010634
60 HSUPA Users per Cell.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been activated.
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.
2. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB
over HSPA.
3. Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources
to E-AGCHs and E-RGCHs.
4. 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.
l Verification Procedure
The 60 HSUPA users referred to in this feature are of the SRB Over HSPA type.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----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;
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010635
HSUPA over Iur.
Prerequisite
l Dependencies on Hardware
The neighboring RNC supports this feature.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package has been configured before
this feature is activated.
l License
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.
2. 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.
l Verification Procedure
1. Verify that the feature HSUPA over Iur has been activated by performing the following
operations:
Run the BSC6900 MML command LST UNRNC to query the configuration of
the neighboring RNC.
Run the BSC6900 MML command LST UEXT3GCELL to query the
configuration of the neighboring RNC's cell.
2. Verify that an HSUPA service has been established on the Iur interface by performing
the following operations:
Configure the neighboring RNC and its cell with the HSUPA function.
Establish an HSUPA service under the serving RNC.
Add a cross-Iur soft handover link.
If the RNSAP_RL_SETUP_REQ message traced on the Iur interface contains
HSUPA-related information elements, an HSUPA service has been set up
successfully.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010636
SRB over HSUPA.
Prerequisite
l Dependencies on Hardware
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.
l Dependencies on Other Features
The WRFD-010612 HSUPA Introduction Package feature must be configured before
this feature is configured.
l License
The license controlling this feature has been activated.
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 Verification Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010641
HSUPA Adaptive Transmission.
Prerequisite
l 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.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been 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.
2. 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.
3. Run the NodeB MML command SET ADPRETRANSSWTCH to activate HSUPA
Adaptive Transmission on the NodeB side.
l Verification Procedure
l 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.
2. Run the NodeB MML SET ADPRETRANSSWTCH to deactivate HSUPA Adaptive
Transmission on the NodeB side.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010690
TTI Switch for BE Services Based on Coverage.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010614 HSUPA Phase 2 has been configured before this feature is
activated.
l License
The license controlling this feature has been 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.
2. 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.
NOTE
2. Adjust the distance between the UE and the NodeB to trigger a switching of the TTI
from 2 ms to 10 ms.
3. Analyze the traced messages shown in Figure 97-2 and Figure 97-3. The TTI has
switched from 2 ms to 10 ms.
l 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
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020138
HSUPA Coverage Enhancement at UE Power Limitation.
Prerequisite
l Dependencies on Hardware
There is no requirement for BSC6900 or NodeB.
The UE supports this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
2. Run the BSC6900 MML command MOD UTYPRABHSUPAPC to set Minimum
Reduced E-DPDCH Gain Factor.
l Verification Procedure
indicates that this feature takes effect, and the BSC6900 sends the UE the transmit power
of the data channel.
l 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
This section describes how to activate, verify, and deactivate the optional feature WRFD-010712
Adaptive Configuration of Traffic Channel Power.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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 Activation Procedure
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.
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 E-
DPCCH 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.
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.
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.
(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.
(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.
l 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;
//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;
//Deactivation procedure
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-0;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010637
HSUPA Iub Flow Control in Case of Iub Congestion.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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.
2. Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set HSUPA
Congestion Control Switch to ON(ON).
l Verification Procedure
NOTE
1. UE is of HSUPA category 5 and is correctly registered at the HLR. That is, traffic
class is set to background, the maximum bit rates are set to UL 2048 kbit/s and DL
7200 kbit/s.
2. On the BSC6900 LMT, start Monitoring UL Throughput and Bandwidth.
3. The uplink throughput of UE is stable and is about 1M.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set HSUPA
Congestion Control Switch to OFF(OFF).
----End
Example
//Activation procedure
SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
SET UDPUCFGDATA: HsupaTnlSwitch=ON;
//Deactivation procedure
SET UDPUCFGDATA: HsupaTnlSwitch=OFF;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010638
Dynamic CE Resource Management.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been activated.
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 Activation Procedure
1. The feature does not need to be activated.
l Verification Procedure
1. Start Tracing Messages on the Iub Interface on BSC6900 LMT and check whether the
value of dynamic-CE-Switch-Private in NBAP_AUDIT_RSP is 1.
If the value is 1, it indicates the feature is activated. Else, it indicates the feature is not
activated. When the value of dynamic-CE-Switch-Private is 1, see Figure 101-1.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELLHSUPA to deactivate HSUPA for
the cell.
2. 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.
3. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010680
HSPA+ Downlink 28Mbps per User.
Prerequisite
l Dependencies on Hardware
BSC6900
This feature does not have any special requirements for hardware.
NodeB
The BTS3812E, BTS3812A, and BTS3812AE should be configured with the EBBI,
EBOI or EDLP board.
The BBU3806 should be configured with the EBBC or EBBCd board; the
BBU3806C should be configured with the EBBM board.
The BBU3900 should be configured with the WBBPb or WBBPd board.
For the RF part, the RF module of Huawei Node B supports one TX channel each,
and two interconnected RF modules can provide two TX channels to support 2 x 2
MIMO.
l 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 License
The license controlling this feature has been activated.
l Other Prerequisites
CN support user rate of 28Mbps or above.
The UE category must support cat16, cat18(or later).
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. Activate the feature WRFD-010684 2 x 2 MIMO by referring to 111 Configuring
2x2 MIMO.
2. Run the BSC6900 MML command SET LICENSE to turn on the license switch for
the HSPA+ Downlink 28Mbps per User feature.
3. Enable the UE to subscribe to this feature by referring to CN documents.
l Verification Procedure
1. Enable a UE in a 2 x 2 MIMO cell to download a 500 MB file from the FTP server.
Then, detect the download transmission rate. At this time, the UE initiates BE services
in the 2 x 2 MIMO cell and the RNC establishes services on the 2 x 2 MIMO.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010681
HSPA+ Downlink 21Mbps per User.
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.
l Dependencies on Other Features
The following features have been configured before this feature is activated:
WRFD-010683 Downlink 64QAM, WRFD-010685 Downlink Enhanced L2.
l License
The license controlling this feature has been activated.
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 Activation Procedure
The theoretical peak rate of a UE can reach 21 Mbps when 64QAM is used and the following
conditions are met:
1. Run the BSC6900 MML command SET LICENSE to activate the license controlling
the HSPA+ Downlink 21Mbps per User feature.
2. Use the UE to subscribe to this feature by referring to CN documents.
3. Activate the feature WRFD-010683 Downlink 64QAM by referring to 110
Configuring Downlink 64QAM.
l Verification Procedure
1. Use the UE in a 64QAM cell to download a 500 MB file from the FTP server. Then,
check the downloading rate.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010685
Downlink Enhanced L2.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l 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 cell-
edge 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.
2. 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.
l Verification Procedure
1. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 104-1.
2. Use the UE to establish an HSDPA service. Check whether the value of the IE dl-
TransportChannelType in the rb-MappingInfo of the RRC_RB_SETUP message
is hsdsch.
3. View the value of the IE dL RLC PDU size in the RRC_RB_SETUP message.
If the value of the IE dL RLC PDU size is flexibleSize, as shown in Figure
104-2, this feature has been activated.
If the value of the IE dL RLC PDU size is fixedSize, this feature is not activated.
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010688
Downlink Enhanced CELL_FACH.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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.
2. Run the BSC6900 MML command ADD UCELLHSDPA to add HUDPA parameters
of a cell.
3. Run the BSC6900 MML command ADD UCELLEFACH to add enhanced
CELL_FACH state parameters of a cell.
4. Run the BSC6900 MML command ACT UCELLHSDPA to activate HSDPA
feature.
5. Run the BSC6900 MML command ACT UCELLEFACH to activate this feature.
l Verification Procedure
1. Run the BSC6900 MML command DSP UCELL to check whether EFACH is
available.
The value of Status of EFACH is EFACH available.
l Deactivation Procedure
1. Run the BSC6900 MML command MOD UCELLALGOSWITCH to clear
E_FACH and DL_L2ENHANCED from the drop-down list Cell Hspa Plus
function switch.
2. Run the BSC6900 MML command DEA UCELLEFACH to deactivate this feature.
----End
Example
//Activating Downlink Enhanced CELL_FACH
This section describes how to activate, verify, and deactivate the optional feature WRFD-010701
Uplink Enhanced CELL_FACH.
Prerequisite
l 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.
l 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 License
The license controlling this feature has been activated.
l 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.
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.
2. 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.
3. Run the BSC6900 MML command ADD UERACHACTOASCMAP to add
mapping of Access Classes (ACs) to an ASC for Uplink Enhanced CELL_FACH.
4. Run the BSC6900 MML command ACT UCELLERACH to activate this feature.
l Verification Procedure
1. Run the BSC6900 MML command DSP UCELL to check whether the ERACH is
available.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELLERACH to deactivate this feature.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010702
Enhanced DRX.
Prerequisite
l Dependencies on Hardware
NodeB:
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.
l 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 License
The license controlling this feature has been activated.
l 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
l Activation Procedure
The BSC6900 MML command ADD UCELLEDRX fails to be executed in an active cell enabled
with enhanced downlink for CELL_FACH. Therefore, you need to deactivate enhanced downlink
for CELL_FACH before configuring the related parameters.
3. Run the BSC6900 MML command ADD UCELLEDRX to set parameters related to
enhanced DRX based on network planning requirements.
4. Run the BSC6900 MML command ACT UCELLEFACH to activate this feature.
l Verification Procedure
1. Start Uu Interface Trace on the LMT to trace messages on the Uu interface.
2. If the UE is not enabled with enhanced uplink for CELL_FACH, the information
element DRX Interruption by HS-DSCH data in the system information message
SIB5/5bis should be set to TRUE, as shown in Figure 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-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.
l 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;
This chapter describes how to activate, verify, and deactivate the basic feature WRFD-030011
MIMO Prime.
Prerequisite
l 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 Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l License
The license that supports this feature is activated.
Context
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.
l 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.
l Verification Procedure
1. Run the NodeB MML command LST MACHSPARA. In this step, check that MIMO
Prime Switch is set to Open.
2. 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.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010689
HSPA+ Downlink 42Mbps per User.
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
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 Activation Procedure
1. This feature does not need to be activated.
l Verification Procedure
1. Set the BE service rate of the UE at the Home Location Register (HLR) to 42 Mbit/
s.
2. Enable a UE in an HSDPA cell to download a 500 MB file from the FTP server. Then,
check whether the download transmission rate is 42 Mbit/s. If yes, this feature has
been activated. At this time, the UE initiates BE services in the HSDPA cell and the
BSC6900 establishes services on the HS-DSCH.
3. Start Monitoring DL Throughput and Bandwidth on the BSC6900 LMT, as shown in
Figure 109-1.
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. This feature does not need to be deactivated.
----End
Example
N/A
This section describes how to activate, verify, and deactivate the optional feature WRFD-010683
Downlink 64QAM.
Prerequisite
l 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.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
WRFD-010685 Downlink Enhanced L2
l License
The license controlling this feature has been activated.
l 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.
2. Optional: Run the BSC6900 MML command SET UFRC to configure preferential
use of 64QAM.
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.
4. 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).
l Verification Procedure
1. As Figure 110-1 shows, start Uu interface tracing on the BSC6900 LMT.
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 rb-
MappingInfo is hsdsch.
3. In the Uu interface tracing data, check the value of the dl-64QAM-Configured
information element under dl-HSPDSCH-Information in the RRC_RB_SETUP
message.
l 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.
2. 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).
----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;
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.
Prerequisite
l Dependencies on Hardware
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 License
The license controlling this feature has been activated.
l 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.
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.
2. 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
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 cell-
level MIMO switch and enhanced L2 function switch. In this step, set Cell Hspa Plus
function switch to MIMO, DL_L2ENHANCED(Cell DL L2ENHANCED
Function Switch), and UL_L2ENHANCED(Cell UL L2ENHANCED Function
Switch).
4. Run the BSC6900 MML command DEA UCELL to deactivate the cell.
5. Configure the related data on the NodeB according to the MIMO hardware
configuration scheme. The following procedure takes the RRU3804 as an example to
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.
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.
(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.
(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 MIMO-
related parameter settings.
l Verification Procedure
1. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 111-1.
2. Use the UE to establish an HSDPA service. Check whether the value of the information
element (IE) dl-TransportChannelType in the rb-MappingInfo of the
RRC_RB_SETUP message is hsdsch.
3. In the traced Uu interface data, check whether the RRC_RB_SETUP message
contains the IE mimoParameters.
If the RRC_RB_SETUP message contains the IE mimoParameters, as shown in
Figure 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.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELL to deactivate the cell.
2. Run the BSC6900 MML command DEA UCELLMIMO to deactivate the MIMO-
related 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. Optional: When PSP is used, run the BSC6900 MML command RMV USCPICH
to remove the S-CPICH of the cell.
5. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step,
clear MIMO from the HspaPlusSwitch drop-down list.
6. Run the BSC6900 MML command ACT UCELL to activate the cell.
----End
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;
FdpchDivModforMIMO=STTD;
//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;
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;
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010693
DL 64QAM+MIMO.
Prerequisite
l 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.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
WRFD-010685 Downlink Enhanced L2
WRFD-010684 22 MIMO
WRFD-010683 Downlink 64 QAM
l License
The license controlling this feature has been activated.
l 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
Procedure
l Activation Procedure
1. Run the NodeB MML command MOD LOCELL to modify a local cell. In this step,
set DL 64QAM MIMO to TRUE.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to turn on the
following three BSC6900-level switches: In this step, select
CFG_HSDPA_64QAM_SWITCH, CFG_HSDPA_MIMO_SWITCH, and
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH from the Channel
Configuration Strategy Switch list.
3. 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.
4. 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.
5. 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.
6. 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.
l Verification Procedure
1. Run the NodeB MML command LST LOCELL to query the configuration
information of the local cell. In this step, set Query Mode to LOCALCELL(Query
Localcell by ID) and then specify Local Cell ID. The execution result displayed on
the LMT shows the DL 64QAM+MIMO capability.
2. Run the BSC6900 MML command LST UCELLALGOSWITCH to verify the
configuration result of the cell algorithm switch.
3. Run the BSC6900 MML command LST UCORRMALGOSWITCH to verify the
configuration result of the connection-oriented algorithm switch.
4. Run the BSC6900 MML command DSP UCELLCHK to check that the cell supports
64QAM+MIMO.
l Deactivation Procedure
1. 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.
2. 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.
----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;
113
Improvement of MIMO and HSDPA Co-carrier
Configuring Performance
This section describes how to activate, verify, and deactivate the optional feature WRFD-010700
Performance Improvement of MIMO and HSDPA.
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 License
The license controlling this feature has been activated.
l 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
Procedure
l Activation Procedure
1. Run the BSC6900 MML command DEA UCELL to deactivate MIMO cells.
2. 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. Run the NodeB MML command SET MACHSPARA. Set IIC Switch to OPEN
(open).
4. 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. Run the BSC6900 MML command ACT UCELL to activate the cell.
l Verification Procedure
1. Run the NodeB MML command LST LOCELL and check whether the value of
VAM is TRUE.
2. Run the NodeB MML command LST MACHSPARA and check whether the value
of IIC Switch is OPEN.
3. Run the BSC6900 MML command LST USCPICH and check whether an SCPICH
is already configured.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELL to deactivate MIMO cells.
2. 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. Run the NodeB MML command SET MACHSPARA. Set IIC Switch to CLOSE
(close).
4. 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. Run the BSC6900 MML command ACT UCELL to activate the cell.
----End
Example
l NodeB V200R013
//Activation procedure
//Operations at the BSC6900
//Deactivating an MIMO cell
DEA UCELL: CellId=1;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010704
Flexible HSPA+ Technology Selection.
Prerequisite
l 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.
l 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 License
The license controlling this feature has been activated.
l 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.
2. 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.
3. 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.
l Verification Procedure
1. Set the TX power threshold and HSDPA user number threshold of the secondary cell
for the DC/MIMO dynamic selection algorithm. Run the BSC6900 MML command
SET UFRC with DL TX Power Threshold of Secondary Cell and Threshold of
HSDPA Users in Secondary Cell set to appropriate values.
2. Have a UE access the secondary cell and initiate an HSDPA service.
3. Query the DL power load of the secondary cell covered by the DC carrier group. On
the BSC6900 LMT, choose Monitor > Monitor > UMTS Monitoring > Cell
Performance Monitoring and select Cell DL Carrier TX Power in the Monitor
Item: drop-down list.
4. Check whether the value of the IE dl-TransportChannelType in the rb-MappingInfo
of the RRC_RB_SETUP message is hsdsch.
Expected result: As shown in Figure 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 dl-
SecondaryCellInfoFDD 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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010686
CPC - DTX /DRX.
Prerequisite
l 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.
l 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 License
The license controlling this feature has been activated.
l 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.
dtx-drx-TimingInfo
dtx-drx-Info
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010687
CPC-HS-SCCH Less operation.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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.
2. 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.
l 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.
l 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.
2. 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.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010653
96 HSDPA Users per Cell.
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.
l 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.
l License
The license controlling this feature has been activated.
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.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable
HSPA state transition.
3. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to enable SRB
over HSPA.
4. Run the BSC6900 MML command MOD UCELLHSUPA to allocate code resources
to E-AGCHs and E-RGCHs.
5. 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.
l Verification Procedure
1. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance
Monitoring in the Monitor Navigation Tree pane. In the displayed Cell
Performance Monitoring dialog box, set Monitor Item to Cell User Number.
2. Use UEs to access the cell 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.
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.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----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;
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010639
96 HSUPA Users per Cell.
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.
l 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.
l License
The license controlling this feature has been activated.
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.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable
HSPA state transition.
The 96 HSUPA users referred to in this feature are of the SRB Over HSPA type.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----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;
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010654
128 HSDPA Users per Cell.
Prerequisite
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.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature can increase the capacity of voice services in a cell, especially in cells with VoIP
users or a large number of low-rate users.
This feature enables an HSDPA cell to serve a maximum of 128 users performing VoIP or other
low-rate services. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
l 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.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable
HSPA state transition.
The 128 HSDPA users referred to in this feature are of the SRB Over HSPA type.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
/*Activating 128 HSDPA Users per Cell*/
//Stop reserving uplink and downlink credit resources and setting the
maximum number of HSDPA users to 128
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=128, UlHoCeResvSf=SFOFF,
DlHoCeCodeResvSf=SFOFF;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010670
128 HSUPA Users per Cell.
Prerequisite
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.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature can increase the capacity of voice services in a cell with a large number of low-rate
users, such as VoIP users.
This feature enables an HSUPA cell to serve a maximum of 128 users performing VoIP or other
low-rate services. Note that these users must adopt the CPC-DTX/DRX mode.
Procedure
l 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.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable
HSPA state transition.
The 128 HSUPA users referred to in this feature are of the SRB Over HSPA type.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
/*Activating 128 HSUPA Users per Cell*/
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010691
HSUPA UL Interference Cancellation.
Prerequisite
l 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 Dependencies on Other Features
WRFD-010612 HSUPA Introduction Package.
l License
The license controlling this feature has been activated.
l 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. If the UMTS cell has been activated, run the BSC6900 MML command DEA
UCELL to deactivate the cell.
2. Run the NodeB MML command MOD LOCELL to modify the local cell. In this
step, set IC to TRUE.
3. Run the BSC6900 MML command ACT UCELL to activate the cell.
l Verification Procedure
1. Run the NodeB MML command DSP LOCELL to query the status of a specified
local cell.
Expected result: The value of IC MODE is ENABLED.
2. 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.
l Deactivation Procedure
1. Run the NodeB MML command MOD LOCELL to modify the local cell. In this
step, set IC to FALSE.
----End
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020137
Dual-Threshold Scheduling with HSUPA Interference Cancellation.
Prerequisite
l 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.
l Dependencies on Other Features
WRFD-010612 HSUPA Introduction Package
WRFD-010691 HSUPA UL Interference Cancellation
l License
The license controlling this feature has been activated.
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 Verification Procedure
1. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set
Max Target RoT Difference Before and After IC to 0.
2. Use multi users to carry out upload service.
3. 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.
4. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set
Max Target RoT Difference Before and After IC to 2.
5. Check the Cell RTWP window. If the value of column 1-4 is less than the value of
column 1-3, and the values of column 1-4 and column 1-3 increase by 10, it indicates
dual-threshold scheduling with HSUPA interference cancellation feature has been
enabled.
NOTE
The prerequisite of the foregoing result is the cell power limit does not over.
l Deactivation Procedure
1. Run the NodeB MML command SET MACEPARA to set Mac-e parameters. Set
Max Target RoT Difference Before and After IC to 0.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020136
Anti-Interference Scheduling for HSUPA.
Prerequisite
l 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 Dependencies on Other Features
WRFD-010612 HSUPA Introduction Package
l 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. Run the NodeB MML command SET MACEPARA to set Mac-e parameters.
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.
l 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;
//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;
This section describes how to activate, verify, and deactivate the optional feature HSUPA
Frequency Domain Equalization.
Prerequisite
l 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.
l Dependencies on Other Features
WRFD-010612 HSUPA Introduction Package.
WRFD-01061403 HSUPA 2ms TTI.
l License
The license controlling this feature has been activated.
l 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 E-
DPDCH. In this manner, the SNR on the EDPDCH is increased and the UL system capacity of
the HSUPA network is expanded. The rate of HSUPA services is also increased in 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. Run the NodeB MML command MOD LOCELL to modify the local cell. In this
step, set FDE to TRUE.
l Verification Procedure
1. 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.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010694
Uplink 16QAM.
Prerequisite
l 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.
l Dependencies on Other Features
WRFD-010612 HSUPA Introduction Package
WRFD-010652 SRB over HSDPA
WRFD-01061403 HSUPA 2ms TTI
l License
The license controlling this feature has been activated.
l 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 This feature can help increase the system capacity in the uplink so that HSUPA users can
obtain a higher peak rate.
l It is recommended that the feature WRFD-010692 HSUPA FDE be activated to help
increase the data throughput on the Uu interface.
Procedure
l Activation Procedure
1. Run the NodeB MML command MOD LOCELL to modify a local cell. In this step,
set UL 16QAM to TRUE.
l Verification Procedure
1. Run the NodeB MML command DSP LOCELL to query the configuration
information of the local cell.
2. As Figure 125-1 shows, start Uu interface tracing on the BSC6900 LMT.
3. Use the UE to perform a dialing test of the PS service. Ensure that an HSUPA service
is established.
4. Analyze the trace messages. In the Uu interface trace data, view the EDCH
information information element (IE) in the RRC_RB_SETUP message.
As shown in Figure 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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010697
E-DPCCH Boosting.
Prerequisite
l 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.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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
l Activation 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
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. Establish PS BE HSUPA services with the uplink rate higher than 1 Mbit/s.
2. Trace messages over the Uu interface by referring to Tracing Messages on the Uu
Interface to check whether the RRC_RB_SETUP message carries the e-TFC-Boost-
Info information element (IE) that includes the e-TFCI-Boost and delta-T2TP fields,
as shown in Figure 126-1.
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 e-
TFCI-Boost-Information IE that includes the e-TFCI-BetaEC-Boost and uL-
Delta-T2TP fields, as shown in Figure 126-2.
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.
2. 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 E-
DPCCH Boosting function in a cell on the NodeB side.
----End
Example
/*Activating E-DPCCH Boosting */
//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 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;
//Disabling the E-DPCCH Boosting function in all cells on the RNC side
SET UCORRMALGOSWITCH: CfgSwitch= CFG_EDPCCH_BOOSTING_SWITCH-0;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010698
HSPA+ Uplink 11.5Mbps per User.
Prerequisite
l 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.
l 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 E-
DPCCH Boosting.
l License
The license controlling this feature has been activated.
l 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
Example
/* Activating the HSPA+ Uplink 11.5Mbps per User feature*/
This section describes how to activate, verify, and deactivate the optional feature WRFD-010695
UL Layer 2 Improvement.
Prerequisite
l Dependencies on Hardware
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 License
The license controlling this feature has been activated.
l 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.
l 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.
l 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.
3. 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.
4. 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.
l Verification Procedure
1. Start Uu interface tracing on the BSC6900 LMT, as shown in Figure 128-1.
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) rlc-
PDU-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.
l 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.
2. 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.
3. 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.
----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
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010696
DC-HSDPA.
Prerequisite
l Dependencies on Hardware
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 License
The license controlling this feature has been activated.
l 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.
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 DC-
HSDPA 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.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of
local cell 1.
2. Run the BSC6900 MML command DEA UCELL to deactivate the logical cell of
local cell 2.
3. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
select CFG_HSDPA_DC_SWITCH from the Channel Configuration Strategy
Switch list.
4. Run the BSC6900 MML command SET UFRC. In this step, set Prefered
MIMO_64QAM or DC_HSDPA character to DC_HSDPA.
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.
2. For cells with Cell DC-HSDPA Function Switch turned on, trace
RRC_RB_SETUP messages on the Uu interface.
3. Perform dialing tests on FTP services for a UE to ensure that data is transmitted on
HSDPA channels.
4. On the Trace tab page of the LMT, check whether RRC_RB_SETUP messages
contain the dl-SecondaryCellInfoFDD information element.
If the dl-SecondaryCellInfoFDD information element is contained, as shown in
Figure 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.
l Deactivation Procedure
To remove a DC-HSDPA cell group, you only need to remove one local cell in the group.
4. Run the BSC6900 MML command ACT UCELL to activate the logical cell of the
local cell 1.
----End
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;
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.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
WRFD-010696 DC-HSDPA
l License
The license controlling this feature has been activated.
l Other Prerequisites
The UE must be of HS-DSCH category 21, 22, 23, 24 to support DC-HSDPA or HS-
DSCH 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 single-
carrier user.
l 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).
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.
l 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.
2. 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.
3. Use a DC-HSDPA UE to perform PS services in a DC-HSDPA cell. Do not upload
or download data after required connections are established. Five seconds later, the
UE becomes an SC UE, which indicates that the feature has been activated.
l Deactivation Procedure
1. 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).
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010699
DC-HSDPA+MIMO (trial).
Prerequisite
l Dependencies on Hardware
The HBBI and HDLP boards in the BTS3812E/BTS3812AE do not support the DC-
HSDPA+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.
l 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 License
The license controlling this feature has been activated.
l Others
This feature is dependent on the UE capability (class 25, 26, 27, and 28 on the HS-
DSCH).
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 Activation Procedure
Example
/*Activating DC-HSDPA+MIMO*/
/*Deactivating DC-HSDPA+MIMO*/
This section describes how to activate, verify, and deactivate the optional feature WRFD-010505
Queuing and Preemption.
Prerequisite
l 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.
l 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 License
The license controlling this feature has been activated.
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.
l Verification Procedure
1. Run the BSC6900 MML command LST UQUEUEPREEMPT to check whether the
queuing and preemption switches are turned on.
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021103
Access Class Restriction.
Prerequisite
l 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.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. Run the BSC6900 MML command SET UACALGO. In this step, set AC Restriction
Switch to ON and other parameters to appropriate values.
l Verification Procedure
Verifying Access Class Restriction based on CPU overload
1. Start Uu Interface Trace on the BSC6900 LMT.
2. Run the BSC6900 MML command LST FCCPUTHD to query the settings of
AC control threshold and AC restore threshold.
3. Run the BSC6900 MML command SET FCCPUTHD. In this step, set AC control
threshold and AC restore threshold to appropriate values.
4. Enable a large number of UEs to access a cell until the CPU usage exceeds the AC
restore threshold.
5. Start Uu Interface Trace on the BSC6900 LMT and select
RRC_SYS_INFO_TYPE3 as the message type. If the value of barred IE in the
RRC_SYS_INFO_TYPE3 message is 0, as shown in Figure 133-1, the feature
has been activated. If the value is not 0, the feature is not activated.
6. Reduce the number of UEs in the cell until the CPU usage is lower than the AC
restore threshold.
7. Run the BSC6900 MML command SET FCCPUTHD. In this step, set AC control
threshold and AC restore threshold to their original values.
Verifying Access Class Restriction based on the access failure on the Iu interface
1. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set
Process switch to SYS_INFO_UPDATE_FOR_IU_RST and
BARRED_CELL_FOR_CSDOMAIN_RST.
2. Run the BSC6900 MML command RST UIU. In this step, set CN Domain ID to
CS_DOMAIN.
3. 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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050424
Traffic Priority Mapping onto Transmission Resources.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
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.
l Verification Procedure
This feature can be verified only by running the LST commands.
1. Run the BSC6900 MML command LST TRMMAP to check whether the transport
resource mapping is correct.
2. If the mapping is incorrect, run the BSC6900 MML command MOD TRMMAP to
modify the mapping.
NOTE
Do not modify Interface Type and Transport Type in the MOD TRMMAP command.
l Deactivation Procedure
1. Run the BSC6900 MML command RMV ADJMAP to remove the TRM mapping to
the adjacent node.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020806
Differentiated Service Based on SPI Weight.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command SET UUSERPRIORITY to configure gold,
silver, and copper users.
2. Run the BSC6900 MML command SET UTHPCLASS to set priorities of PS
interactive services to appropriate values.
3. Run the BSC6900 MML command SET USCHEDULEPRIOMAP to set the
scheduling priority mapping information.
4. Run the BSC6900 MML command SET UCAPARATERANGE to set RNC-specific
reference rates and rate thresholds of all levels in the uplink and downlink.
5. 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.
6. Run the BSC6900 MML command SET USPIWEIGHT to set RNC-specific
scheduling priority weight.
7. Optional: Run the BSC6900 MML command ADD UOPERSPIWEIGHT to set
operator-specific scheduling priority weight.
8. Run the BSC6900 MML command SET URRCTRLSWITCH. In this step, set
Process switch to NODEB_PRIVATE_INTERFACE_SWITCH.
l Verification Procedure
1. 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.
----End
Example
/*Activating Differentiated Service Based on SPI Weight*/
This section describes how to activate, verify, and deactivate the optional feature WRFD-020132
Web Browsing Acceleration.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command ADD BRD to add a NIUa board. In this step, set
the Board Class to NIU, and set the Board Type to NIUa.
2. Set the initial Scheduling Priority Indicator (SPI) weight on the BSC6900 LMT.
If the switch for the license control item of the feature WRFD-020806
Differentiated Service Based on SPI Weight is turned on, run the BSC6900
MML command SET USPIWEIGHT to configure weight of each SPI. In this
step, set Scheduling Priority Indicator and SPI Weight to appropriate values
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.
4. Run the BSC6900 MML command ADD UIPSERVICEQOS to add the priority
mapping of HTTP services.
5. Run the BSC6900 MML command SET UDPUCFGDATA to set scheduling priority
weight that corresponds to services of each priority to appropriate values.
l Verification Procedure
1. Verify that the value of the counter VS.IuPS.BytesPayldHTTP.Rx is not 0. If it is not
0, this feature has been activated.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
//Activating Web Browsing Acceleration
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020133
P2P Downloading Rate Control during Busy Hour.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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 non-
busy 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.
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.
4. Run the BSC6900 MML command ADD UIPSERVICEQOS to add the priority
mapping of P2P services.
5. Run the BSC6900 MML command SET UDPUCFGDATA to set scheduling priority
weight that corresponds to services of each priority to appropriate values.
l Verification Procedure
1. Verify that the value of the counter VS.IuPS.BytesPayldP2P.Rx is not 0. If it is not 0,
this feature has been activated.
l Deactivation Procedure
1. This feature does not need to be deactivated.
----End
Example
//Activating P2P Downloading Rate Control during Busy Hour
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020135
Intelligent Inter-Carrier UE Layered Management.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
l License
The license controlling this feature has been activated.
Context
This feature allows the RAN to intelligently distinguish between UEs and data cards in multi-
carrier 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. Run the BSC6900 MML command SET UDRD. In this step, set Device Type
Steering DRD Switch to ON.
2. 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.
3. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set Direct Retry Switch to DR_RAB_SING_DRD_SWITCH.
4. Run the BSC6900 MML command ADD UDEVICETYPEIMSI. In this step, set
IMSI Segment Choice to MultiIMSI and specify the IMSI number range by setting
IMSI Segment Start Value and IMSI Segment End Value. If the IMSI of a terminal
falls into the IMSI number range, the terminal is regarded as a data card.
5. Run the BSC6900 MML command ADD UDEVICETYPEPRIOGROUP to add
terminal type priorities.
6. Run the BSC6900 MML command ADD UCELLSETUP twice to bind a terminal
type priority to cell F1 and cell F2 respectively.
7. Optional: Configure preferred camping. Cell F1 is a preferred camping frequency,
and cell F2 is a services balancing frequency.
NOTE
This feature does not depend on the camping policy setting of an existing network. When this
feature is activated and cell F2 provides discontinuous coverage, you must configure inter-
frequency 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.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UDRD. In this step, set Device Type
Steering DRD Switch to OFF.
2. Run the BSC6900 MML command RMV UCELLLICENSE to disable the layered
terminal management function for the cell.
----End
Example
//Activating Intelligent Inter-Carrier UE Layered Management
//Turning on the layered terminal management switch
SET UDRD: DPGDRDSwitch=ON;
//Enabling the layered terminal management function for cell F1 and cell
F2
ADD UCELLLICENSE: CellId=11013, INTELLIGENT_INTERFREQ_UE_TYPE_STEERING-1;
ADD UCELLLICENSE: CellId=11014, INTELLIGENT_INTERFREQ_UE_TYPE_STEERING-1;
//Turning on the single-service DRD switch
SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1;
//Configuring an IMSI number range
ADD UDEVICETYPEIMSI: IMSISegIndex=1, IMSISegChoice=MultiIMSI,
IMSIStart="502808888800070", IMSIEnd="502808888800080";
//Adding terminal type priorities
ADD UDEVICETYPEPRIOGROUP: DPGId=1, UEDP=1, DataCardDP=1, ReservedDP=1;
ADD UDEVICETYPEPRIOGROUP: DPGId=2, UEDP=2, DataCardDP=2, ReservedDP=1;
//Binding terminal type priorities to cells
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020302
Inter Frequency Hard Handover Based on Coverage.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
2. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-
frequency neighboring cell.
3. 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.
l Verification Procedure
1. Attenuate signals in the current cell that the UE accesses to trigger reporting of event
2D by the UE.
2. Click to display Uu Interface Trace on the BSC6900 LMT.
3. Check whether the RNC has sent the UE an RRC_MEAS_CTRL message and the
traced message contains thresholds for triggering events 2D and 2F and the reporting
mode.
4. Check whether the RNC has sent the UE an RRC_MEAS_RPRT message and the
traced message contains an event 2D measurement report shown in Figure 139-1.
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.
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020304
Inter Frequency Hard Handover Based on DL QoS.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to activate the
inter-frequency hard handover.
2. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-
frequency neighboring cell.
3. 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.
4. Run the BSC6900 MML command SET UQOSACT to activate inter-frequency hard
handover based on downlink QoS for BE services.
5. Run the BSC6900 MML command SET UQOSACT to activate inter-frequency hard
handover based on downlink QoS for AMR and AMR-WB services.
6. Run the BSC6900 MML command SET UQOSACT to activate inter-frequency hard
handover based on downlink QoS for VP services.
l Verification Procedure
1. Log in to the BSC6900 LMT and start Uu Interface Trace.
2. 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.
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.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UQOSACT to deactivate inter-frequency
hard handover based on downlink QoS for BE 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02060501 SRNS Relocation (UE Not Involved).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-020605 SRNS Relocation Introduction Package has been
configured before this feature is activated.
l License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command ADD DEVIP to add a device IP address to an
interface board.
2. Run the BSC6900 MML command ADD IPOAPVC to add an Internet Protocol over
ATM (IPoA) permanent virtual circuit (PVC). In this step:
Set IP address to the device IP address of the interface board.
Set Peer IP address to the IP address of the serving GPRS support node (SGSN).
The VPI and VCI must be the same as those configured on the SGSN side. You
can run the command LST IPOA on the SGSN maintenance terminal to query the
settings of the VPI and VCI on the SGSN side.
3. Run the BSC6900 MML command ADD IPRT to add a route from the BSC6900 to
the DRNC. In this step:
Set Subrack No. and Slot No. respectively to the subrack number and slot number
of the Iu-PS interface board carrying the IP path.
Set Destination IP Address to the IP address of the DRNC on the Iu interface.
Set Forward route address to the IP address of the SGSN gateway.
4. Run the BSC6900 MML command ADD IPPATH to add an IP path for static SRNS
relocation. In this step:
Set Adjacent Node ID to the adjacent node ID of the SGSN.
Set Interface Type to IUR(Iur Interface).
Set Local IP address to the IP address of the SRNC on the Iu interface.
Set Peer IP address to the Iu IP address of the DRNC on the Iu interface.
5. Run the BSC6900 MML command ADD UEXT3GCELL to add a cell to the
neighboring RNC.
6. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell.
7. 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
Call drops do not occur during SRNS relocation if all the following messages are
traced:
Example
//Activating SRNS Relocation (UE Not Involved)
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02060502 SRNS Relocation with Hard Handover.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell.
2. UE1 and UE2 are in idle mode and camp on Cell 111.
3. 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.
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.
l Verification Procedure
1. Initiate standard interface tracing on the BSC6900 LMT to perform the verifying
procedure. No call drops occur during the transition.
You can view the transition procedure on the Iu interface tracing pane of RNC1, as
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.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
Example
//Activating SRNS Relocation with Hard Handover
//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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02060503 SRNS Relocation with Cell/URA Update.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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:
The SNSR relocation can be triggered by cell reselection of UEs in the CELL_FACH,
CELL_PCH, or URA_PCH state. The relocation is started after the Cell Update or URA Update
message from the UE is forwarded from the target RNC to the source RNC over the Iur interface.
Procedure
l Activation Procedure
1. The Iur interface between RNC1 and RNC2 is working properly. On the HLR, set the
UE to support background services of UL64K/DL 384K.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set the
related switches so that the DCCC and state transition are supported.
3. 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. Run the BSC6900 MML command SET UUESTATETRANSTIMER to set BE
DCH to FACH Transition Timer to 10.
5. UE1 and UE2 are in idle mode and camp on Cell 111.
6. 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.
l Verification Procedure
1. 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.
RNC1->CN RANAP_RELOCATION_REQUIRED
CN to RNC1: RANAP_RELOCATION_COMMAND
CN->RNC2 RANAP_RELOCATION_REQ
RNC2->CN RANAP_RELOCATION_REQ_ACK
RNC2->CN RANAP_RELOCATION_DETECT
RNC2->CN RANAP_RELOCATION_COMPLETE
RNC1->RNC2: RNSAP_RELOCATION_COMMIT
l Deactivation Procedure
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020303
Inter-RAT Handover Based on Coverage.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l Other Prerequisites
The UE supports relevant measurements and the handover procedure.
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.
2. Run the BSC6900 MML command ADD U2GNCELL to add an inter-frequency
neighboring GSM cell.
3. 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.
l Verification Procedure
1. Attenuate signals in the current cell that the UE accesses to trigger reporting of event
2D by the UE.
2. Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message
Type, select RRC_MEAS_RPRT.
3. Check whether event 2D shown in Figure 144-1 has been reported in the traced
messages.
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020309
Inter-RAT Handover Based on DL QoS.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l Other Prerequisites
The UE supports relevant measurements and the handover procedure.
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.
2. Run the BSC6900 MML command ADD U2GNCELL to add an inter-RAT
neighboring cell.
3. Run the BSC6900 MML command SET UQOSHO to set BSC6900-level parameters
related to Inter-RAT Handover Based on DL QoS.
4. Run the BSC6900 MML command SET UQOSACT to turn on QoS switches for
different traffic classes.
l Verification Procedure
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.
l Deactivation Procedure
1. Run the BSC6900 command SET UCORRMALGOSWITCH. In this step, deselect
HO_INTER_RAT_CS_OUT_SWITCH and
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020307
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
Prerequisite
l Dependencies on Hardware
The CN complies with 3GPP Release 6 or later.
l 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 License
The license controlling this feature has been activated.
l 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.
l Verification Procedure
1. Start Iu Interface Trace and Uu Interface Trace on the BSC6900 LMT.
2. 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.
3. In the Iu Interface Trace dialog box, check that the BSC6900 sends an
RAB_MODIFY_REQ message to the CN. In the RAB_MODIFY_REQ message,
the value of the IE alternativeRABConfigurationRequest is alternative-RAB-
configuration-Requested.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
This section describes how to activate, verify, and deactivate the optional feature WRFD-020308
Video Telephony Fallback to Speech (AMR) for Inter-RAT HO.
Prerequisite
l Dependencies on Hardware
BSC should support NACC RIM (RAN Information Management) and PS handover
procedure.
l 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)
l License
The license controlling this feature has been activated.
Context
This feature provides the inter-RAT relocation procedure for NACC and PS services to shorten
the interruption time of PS services caused by inter-RAT handover.
The inter-RAT Handover Enhanced Package includes the following features:
l WRFD-02030801 NACC (Network Assisted Cell Change)
l 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)
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02030801 NACC(Network Assisted Cell Change).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature supports the standard NACC procedure defined in 3GPP specifications.
The NACC refers to Network Assisted Cell Change from UTRAN to GERAN, which is different
from the normal cell change order procedure, because the network provides GERAN (P) SI for
the UE.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to open the
following switches in the HandOver switch parameter:
HO_INTER_RAT_PS_OUT_SWITCH
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH
NOTE
When PS_3G2G_RELOCATION_SWITCH is ON, this switch no longer takes effect.
2. Run the BSC6900 MML command ADD UEXT2GCELL(for new neighboring cell)
or MOD UEXT2GCELL (for the existing neighboring cell) to set Inter-RAT cell
support RIM indicator to TRUE.
l Verification Procedure
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the
settings of the PS inter-RAT handover, NACC, and Relocation switches.
2. Run the BSC6900 MML command LST UEXT2GCELL to check whether the inter-
RAT 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.
l 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.
2. Run the BSC6900 MML command MOD UEXT2GCELL to set Inter-RAT cell
support RIM indicator to FALSE.
----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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02030802 PS Handover between UMTS and GPRS.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature enables the relocation of PS services (including non-real-time PS services and real-
time PS services) between systems. In inter-system handover scenarios, this feature can greatly
improve user perception, especially for real-time PS services.
The PS handover is different from NACC or normal cell change function, with which the
relocation procedure between 3G and 2G is applied, just like the CS inter-system handover. With
this feature, the service interruption for PS service inter-system handover is reduced by a great
extent.
In this feature, both the handover from UTRAN to GERAN and the handover from GERAN to
UTRAN are supplied. If both the UE and the network support PS handover, handover between
UTRAN and GERAN would be performed. Otherwise, either NACC or normal cell change order
would be selected.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to open the
following switches in the HandOver switch parameter:
HO_INTER_RAT_PS_OUT_SWITCH
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH
2. Run the BSC6900 MML command ADD UEXT2GCELL to add a neighboring GSM
cell to the UMTS coverage and to set the Inter-RAT cell support PS HO
indicator parameter to TRUE.
3. Run the BSC6900 MML command ADD U2GNCELL to add a neighboring GSM
cell for the UMTS cell.
4. Optional: Run the BSC6900 MML command SET UINTERRATHOCOV to set
inter-RAT handover measurement related parameters.
l Verification Procedure
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check the
status of PS inter-RAT handover switch and the Relocation HO switch.
2. Run the BSC6900 MML command LST UEXT2GCELL to ensure the inter-RAT
cell supports PS Handover.
3. Run the BSC6900 MML command LST UINTERRATHOCOV to check inter-RAT
handover measurement related parameters.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to set
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH in the HandOver
switch parameter to 0.
2. Run the BSC6900 MML command MOD UEXT2GCELL to set the
SuppPSHOFlag parameter to FALSE.
----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;
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.
Prerequisite
l Dependencies on Hardware
The UE is a UMTS<E dual-mode terminal.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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 Huawei UMTS supports bidirectional cell reselection between a UMTS cell and an LTE
cell.
l 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.
l 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_SYS_INFO_TYPE19 to trace Uu interface SIB19
message.
l Deactivation Procedure
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
and the configured information about the frequencies of neighboring cells become
ineffective.
2. Run the BSC6900 MML command SET LICENSE to deactivate the license
controlling the feature Mobility Between UMTS and LTE Phase 1.
----End
Example
//Activating Mobility Between UMTS and LTE Phase 1
MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-1;
MOD UCELLSELRESEL: CellId=1, QualMeas=CPICH_ECNO, QrxlevminExtSup=FALSE,
NonhcsInd=NOT_CONFIGURED, ThdPrioritySearch1=2, ThdPrioritySearch2=2;
MOD UCELLNFREQPRIOINFO: CellId=1, EARFCN=1, NPriority=2,
BlacklstCellNumber=D0;
//Deactivating Mobility Between UMTS and LTE Phase 1
MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-0;
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES,
FUNCTIONSWITCH5=LQW1ULM01-0;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020129
Service-Based PS Service Redirection from UMTS to LTE (trial).
Prerequisite
l Dependencies on Hardware
There is no requirement for BSC6900 and NodeB.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable
HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH.
2. 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.
3. Run the BSC6900 MML command ADD ULTENCELL to configure a neighboring
LTE cell.
4. Run the BSC6900 MML command SET UU2LTEHONCOV to set RNC-Oriented
Non-Coverage-Based UMTS-LTE Handover Measurement Algorithm
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.
l 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
//Deactivation procedure
This section describes how to activate, verify, and deactivate the optional feature WRFD-020103
Inter Frequency Load Balance.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been 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.
3. Run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-
frequency neighboring cell supporting blind handover, or to add an inter-frequency
HO_ALGO_LDR_ALLOW_SHO_SWITCH and
HO_INTER_FREQ_HARD_HO_SWITCH through HandOver Switch.
3. Run the BSC6900 MML command MOD UCELLLDR. In this step, set Code
congestion select inter-freq indication to FALSE(FALSE).
4. Restore the parameter settings modified in the activation procedure.
----End
Example
//Activating Inter Frequency Load Balance
MOD UCELLALGOSWITCH: CellId=111,
NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR-
1;
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_LDR-
0;
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020305
Inter-RAT Handover Based on Service.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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.
2. Run the BSC6900 MML command ADD UEXT2GCELL to add a neighboring GSM
cell.
3. Run the BSC6900 MML command ADD U2GNCELL to set neighbor relation with
the neighboring GSM cell.
4. Run the BSC6900 MML command ADD UCELLHOCOMM. In this step, set Inter-
RAT CS handover switch or Inter-RAT PS handover switch to ON.
l Deactivation Procedure
1. Run the BSC6900 MML command MOD UCELLHOCOMM. In this step, set Inter-
RAT 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020306
Inter-RAT Handover Based on Load.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been 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.
2. Run the BSC6900 MML command ADD UEXT2GCELL to add the information
about a GSM cell.
3. Run the BSC6900 MML command ADD U2GNCELL to add the GSM cell as a
neighboring cell of the UMTS cell.
4. 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
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020400
DRD Introduction Package.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
Context
This feature supports co-coverage inter-frequency or inter-RAT directed retries and redirection.
This feature consists of the following features:
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
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02040001 Intra System Direct Retry.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
l License
The license controlling this feature has been 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.
2. 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.
3. 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.
NOTE
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter
settings take effect.
l 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.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UDRD to turn off the RNC-level switches.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02040002 Inter System Direct Retry.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
l License
The license controlling this feature has been activated.
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.
2. 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, Measurement-
Based DRD Switch, and Device Type Steering DRD Switch.
3. 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
Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, and
Device Type Steering DRD Switch.
NOTE
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter
settings take effect.
l Verification Procedure
1. Start Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive
service.
2. 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."
l Deactivation Procedure
1. 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.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02040003 Inter System Redirect.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
l License
The license controlling this feature has been activated.
Context
This feature allows inter-system redirection during RRC connection setup.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set Direct Retry Switch to DR_RRC_DRD_SWITCH.
2. Run the BSC6900 MML command SET UDRD. In this step, set
ConnectFailRrcRedirSwitch to Allowed_To_Inter_RAT.
l Verification Procedure
1. Start Uu Interface Trace on the BSC6900 LMT. Use a UE to initiate an RRC
connection setup request.
2. The following procedure is traced on the Uu interface:
(1) The UE sends an RRC_SETUP_REQ message.
(2) The BSC6900 responds with an RRC_CONN_REJ message, carrying GSM-
TargetCellInfo in the IE redirectioninfo.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UDRD. In this step, set RRC redirect
switch to OFF or Only_To_Inter_Frequency.
----End
Example
//Activating Inter-System Redirect
SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1;
SET UDRD: ConnectFailRrcRedirSwitch=Allowed_To_Inter_RAT;
//Deactivating Inter-System Redirect
SET UDRD: ConnectFailRrcRedirSwitch=OFF;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02040004 Service Steering and Load Sharing During RAB Setup.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
l License
The license controlling this feature has been activated.
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. 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.
2. 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.
3. 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.
4. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set Direct Retry Switch to DR_RAB_SING_DRD_SWITCH.
5. Run the BSC6900 MML command SET UDRD. In this step, turn on Service
differential drd switch and Measurement-Based DRD Switch.
l Verification Procedure
1. Start Uu interface tracing on the BSC6900 LMT.
2. Use a UE in a cell to initiate a PS interactive service. This cell carries low-priority
services. The target inter-frequency neighboring cell has light load and carries high-
priority 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.
l 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;
This section describes how to activate and verify the optional feature WRFD-020401 Inter-RAT
Redirection Based on Distance.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package has been configured before this
feature is activated.
l License
The license controlling this feature has been 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.
2. Simulate a scenario where pilot pollution occurs. Place the UE in a place where the
UE is far away from the NodeB and pilot signals are strong. Then, use the UE to
establish a CS voice call.
3. Check the messages traced on the Uu interface.
As shown in Figure 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 GSM-
Targetcellinfo, this feature is not activated.
l 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;
This section describes how to activate, verify and deactivate the optional feature WRFD-020402
Measurement based Direct Retry.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command ADD UCELLMBDRINTERFREQ, turn on the
switch of Cell-Oriented inter-frequency measurement MBDR Switch.
2. Run the BSC6900 MML command ADD UCELLMBDRINTERRAT, turn on the
switch of Cell-Oriented inter-RAT measurement MBDR Switch.
3. 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 Verification Procedure
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.
l Deactivation Procedure
1. Run the BSC6900 MML command MOD UCELLMBDRINTERFREQ, close the
MBDR Switch.
----End
Example
//Activating Measurement based Direct Retry
This section describes how to activate, verify, and deactivate the optional feature WRFD-020500
Enhanced Fast Dormancy.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l 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 Enhancement-
per PS Active User to an appropriate value.
l 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 The BSC6900 receives an SCRI message from the UE.
l 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.
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
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.
7. 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.
8. 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.
9. Run the BSC6900 MML command SET UUESTATETRANS. In this step, set Fast
Dormancy User FACH/E_FACH2DCH/HSPA 4A Threshold to D1k.
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:
4. Keep the UE in idle mode for a period. For example, perform no operation for four
seconds after a Web page is opened.
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.
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.
l 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.
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
This section describes how to activate, verify, and deactivate the optional feature WRFD-021102
Cell Barring.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
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 drop-
down list.
2. Run the BSC6900 MML command SET UIUTIMERANDNUM to enable
interruption protection by specifying CN protection timer.
Setting manual cell barring
1. Run the BSC6900 MML command ADD URNCALLCELLBLK to configure
parameters related to barring of all cells served by an RNC in a network.
2. Run the BSC6900 MML command ADD UCNOPALLCELLBLK to configure
parameters related to operator-specific barring of all cells in a network.
l Verification Procedure
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.
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. Click to display Uu Interface Trace on the BSC6900 LMT. Under Uu Message
Type, select RRC_SYS_INFO_TYPE3.
2. View whether IE information related to CS and PS domains is contained in the
traced messages. Expected result: The IE information is not contained, as shown
in Figure 163-2.
Bar PS services of UEs served by an operator. Perform the following steps to verify
whether this feature is activated:
NOTE
Perform the same verification procedure when barring CS services of UEs served by an operator.
l 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 drop-
down list.
Deactivating manual cell barring
1. Run the BSC6900 MML command RMV URNCALLCELLBLK to remove
parameters related to barring of all cells served by an RNC in a network.
2. Run the BSC6900 MML command RMV UCNOPALLCELLBLK to remove
parameters related to operator-specific barring of all cells in a network.
----End
Example
//Activating Cell Barring
SET URRCTRLSWITCH: PROCESSSWITCH = SYS_INFO_UPDATE_FOR_IU_RST-1;
SET URRCTRLSWITCH: PROCESSSWITCH = BARRED_CELL_FOR_CSDOMAIN_RST-1;
SET UIUTIMERANDNUM: CnOpIndex=0, CNId=0, StateIndTmr=20000;
//Deactivating Cell Barring
SET URRCTRLSWITCH: PROCESSSWITCH = SYS_INFO_UPDATE_FOR_IU_RST-0;
SET URRCTRLSWITCH: PROCESSSWITCH = BARRED_CELL_FOR_CSDOMAIN_RST-0;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020310
3G/2G Common Load Management.
Prerequisite
l Dependencies on Hardware
The CN should support this feature.
The BSS should support this feature.
l 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
l License
The license controlling this feature has been activated.
Context
The 3G/2G Common Load Management applies to inter-RAT handover and inter system direct
retry. The load of source cell and target cell is considered during inter-RAT handover from 3G
to 2G or from 2G to 3G and inter system direct retry.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to enable the
inter-RAT handover. In this step, select HO_INTER_RAT_CS_OUT_SWITCH
and HO_INTER_RAT_PS_OUT_SWITCH through the HandOver Switch.
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.
3. Run the BSC6900 MML command ADD UEXT2GCELL to add a GSM cell
neighboring to the UMTS coverage.
l Verification Procedure
1. Run the BSC6900 MML command LST UINTERRATHONCOV to check whether
the parameters Send Load Info to GSM Ind and NCOV Reloc Ind based on GSM
cell load are set to ON.
2. Run the BSC6900 MML command LST U2GNCELL to ensure the inter-RAT
neighboring cell for the GSM system is added correctly.
NOTE
Consult Huawei engineers about the verification solution to obtain professional technical support.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010506
RAB Quality of Service Renegotiation over Iu Interface.
Prerequisite
l Dependencies on Hardware
The NEs in the core network must support selective configuration of the maximum bit
rate (MBR) and guaranteed bit rate (GBR).
l Dependencies on Other Features
This feature does not depend on other features.
l 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 real-
time 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.
2. 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.
3. 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.
4. 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
Example
/*Activating RAB Quality of Service Renegotiation over Iu Interface*/
This section describes how to activate, verify, and deactivate the optional feature WRFD-010507
Rate Negotiation at Admission Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
Activating RAB rate reduction
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_RAB_DOWNSIZING_SWITCH.
l Verification Procedure
Verifying QoS negotiation
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query
the activation result.
2. Start Iu message tracing on the BSC6900 LMT and establish a PS service, as shown
in Figure 166-1.
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020120
Service Steering and Load Sharing in RRC Connection Setup.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-020400 DRD Introduction Package must be configured before this
feature is activated.
l License
The license controlling this feature has been activated.
Context
With this feature, service steering and load sharing among different frequencies, bands, or radio
access technologies (RATs) can be achieved during radio resource control (RRC) connection
setup based on the service type and cell load.
Procedure
l Activation 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.
2. Run the BSC6900 MML command SET UREDIRECTION. In this step, set RNC-
level Traffic Type to AMR and Redirection Switch to
ONLY_TO_INTER_RAT.
3. Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION. In
this step, set cell-level Traffic Type to AMR and Redirection Switch to
ONLY_TO_INTER_RAT.
NOTE
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter
settings take effect.
l Verification Procedure
1. Use a UE complying with the 3GPP Release 5 to send an RRC_SETUP_REQ
message with the cause value "Originating Conversational Call."
2. The BSC6900 responds with an RRC_CONN_REJ message. If "redirectioninfo" of
the message contains "GSM-TargetCellInfo," this feature has been activated.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH to disable the
RRC DRD function.
2. 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.
3. 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.
----End
Example
/*Activating Service Steering and Load Sharing in RRC Connection Setup*/
This section describes how to activate, verify, and deactivate the optional feature WRFD-020123
TCP Accelerator.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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
l Activation Procedure
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.
l Verification Procedure
1. Run the BSC6900 MML command LST UDPUCFGDATA to check whether the
TCP accelerator switch is turned on. If the switch is turned on, this feature has been
activated.
2. Use a test terminal to download a file of 200 KB from the FTP server. Then, compare
the download time taken before and after the TPE_DOWNLINK_SWITCH is turned
on.
3. Use a test terminal to upload a file of 200 KB to the FTP server. Then, compare the
upload time taken before and after the TPE_UPLINK_SWITCH is turned on.
l Deactivation Procedure
1. 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.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020124
Uplink Flow Control of User Plane.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. Run the NodeB MML command SET R99FLOWCTRLSWTCH to turn on the cell-
level switch for uplink user plane flow control.
l Verification Procedure
1. Start an Iub interface tracing task on the BSC6900 LMT, as shown in Figure 169-1.
l Deactivation Procedure
1. Run the NodeB MML command SET R99FLOWCTRLSWTCH to turn off the cell-
level 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020130
Videophone Service Restriction.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command DEA UCELL to deactivate the cell. In this step,
set Cell ID to an appropriate value.
2. Run the BSC6900 MML command MOD UCELLSETUP. In this step, set Cell VP
Limit Indicator to TRUE.
3. Run the BSC6900 MML command ACT UCELLL to activate the cell. In this step,
set Cell ID to an appropriate value.
4. 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.
l Verification Procedure
1. Use two VP-capable UEs to camp on the same cell, and then use one UE to initiate a
VP to the other UE.
2. Initiate Iu Interface Trace on the BSC6900 LMT.
Example
//Activating Videophone Service Restriction
This section describes how to activate, verify, and deactivate the optional feature WRFD-011502
Active Queue Management (AQM).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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.
l Verification Procedure
1. 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.
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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020128
Quality Improvement for Subscribed Service.
Prerequisite
l 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.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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.
3. 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.
4. 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.
5. Run the BSC6900 MML command SET UDPUCFGDATA. In this step, set Service
Priority Adjusting Coefficient to an appropriate value.
l Verification Procedure
1. 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.
l Deactivation Procedure
1. 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.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020131
Optimization of R99 and HSUPA Users Fairness.
Prerequisite
l 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.
l Dependencies on Other Features
The feature WRFD-010612 HSUPA Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been 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
l 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
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-011000
Cell Broadcast Service.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature and the feature WRFD-011001 Simplified Cell Broadcast cannot be used
together.
l License
The license controlling this feature has been activated.
l 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.
NOTE
8. Run the BSC6900 MML command ADD UCELLCBSDRX to add the CBS
discontinuous reception (DRX) scheduling parameter.
9. 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.
(5) Run the BSC6900 MML command DSP UCELL to check whether the CBS
function works, as shown in Figure 174-3.
(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. Run the BSC6900 MML command RMV UCBSADDR to disable Cell Broadcast
Service.
----End
Example
//Activating Cell Broadcast Service
This section describes how to activate, verify, and deactivate the optional feature WRFD-011001
Simplified Cell Broadcast.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature and the feature WRFD-011000 Cell Broadcast Service cannot be used
together.
l License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command RMV UCBSADDR to remove the IP address of
the external CBC.
2. Run the BSC6900 MML command ADD URNCCBCPUID to configure the SPU
subsystem of the built-in CBC.
3. 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.
4. Run the BSC6900 MML command ADD UCTCH to add the common traffic channel
(CTCH) to a cell.
5. Run the BSC6900 MML command ADD UCELLCBSDRX to add the CBS
discontinuous reception (DRX) scheduling parameter.
6. Run the BSC6900 MML command ADD UCELLCBSSAC to add a CBS area and a
broadcast message.
7. Run the BSC6900 MML command ACT UCELLCBS to enable the CBS function
for a cell.
l Verification Procedure
1. Check whether the CBS function works properly.
After activating the CBS function on the RNC, if the UU_BMC_MSG_TYPE
message beginning with 01 is traced on the Uu interface, as shown in Figure 175-1,
the CBS function works properly.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELLCBS to disable the CBS function
for a cell.
2. 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
This section describes how to activate, verify, and deactivate the optional feature WRFD-011600
TFO/TrFO.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
l Verification Procedure
1. Start Uu interface tracing on the BSC6900 LMT.
2. Enable UE1 to call UE2. UE2 answers and starts a conversation with UE1. When UE1
moves to the cell edge, you can view the RRC TFC CTRL message indicating rate
reduction sent from RNC to UE1 over the Uu interface. This indicates that this feature
is activated.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020116
Dynamic Power Sharing of Multi-Carriers.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
NOTE
Example
//Activation procedure
ADD PAGRP: SLOCELL=1, DLOCELL=2, MAXSHRTO=50, SHMGN=10;
//Deactivation procedure
RMV PAGRP: DLOCELL=2;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020117
Multi-Carrier Switch off Based on Traffic Load.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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.
l 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
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
This feature takes effect only when the GBP measurement switch for the inter-frequency co-
coverage neighboring cell is turned on.
l Verification Procedure
1. Start alarm browsing on the BSC6900 LMT.
2. Ensure that the total number of users in cell 1 and cell 2 is 0. Alternatively, set up two
inter-frequency co-coverage neighboring cells where no user is admitted.
3. At a time during the period specified by running the BSC6900 MML command ADD
UCELLDYNSHUTDOWN (for example, 09:10):
If an ALM-22202 UMTS Cell Unavailable is reported at cell 1 with the cause value
of cell dynamic shutdown, this feature has been activated.
If this alarm is not reported or is reported but the cause value is not cell dynamic
shutdown, this feature is not activated.
4. Check whether this feature is activated by viewing the counter
VS.DynOpen.CellSetup and check whether this feature is deactivated by viewing the
counter VS.DynClose.CellDel on the M2000.
l 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).
2. Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN to
deactivate this feature for cell 1.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020118
Energy Efficiency Improved.
Prerequisite
l Dependencies on Hardware
MTRU of the BTS3812E/BTS3812AE does not support this feature.
The RRU3801C of the NodeB does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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 When there is no HSDPA service, the function is supported by the system as long as the
license is activated.
l 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 Activation Procedure
1. Run the NodeB MML command SET OPTDYNADJPARA to set the dynamic
voltage adjustment parameters.
set Dynamic Voltage Adjustment Switch to ON.
Set Start Time and End Time as required.
l 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.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020122
Multi-Carrier Switch off Based on QoS.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
Context
This feature guarantees the data rate for only DCH and high-priority HSDPA users. For low-
priority 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. Run the BSC6900 MML command SET URNCCELLSHUTDOWNPARA. In this
step, set Cell Dynamic ShutDown Switch for RNC to ON(switch on).
2. Assume that the cell ID is 2003. Run the BSC6900 MML command LST
UCELLDYNSHUTDOWN 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
This feature takes effect only when the GBP measurement switches of both cell 2003 and cell
2004 are turned on.
l Verification Procedure
1. Start alarm browsing on the BSC6900 LMT.
2. Ensure that the total number of users in cell 2003 and cell 2004 is 0. Alternatively,
add two inter-frequency co-coverage cells that have bidirectional neighboring cell
relationships, and these cells do not carry any services.
3. At a time during the period specified in the BSC6900 MML command ADD
UCELLDYNSHUTDOWN (for example, 09:10):
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.
l Deactivation Procedure
1. 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).
2. Optional: Run the BSC6900 MML command RMV UCELLDYNSHUTDOWN. In
this step, set Cell ID to 2003 to deactivate this feature for cell 2003.
----End
Example
/*Activation procedure*/
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020119
Multi-Carrier Switch off Based on Power Backup.
Prerequisite
l Dependencies on Hardware
This feature does not have special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
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 P-
CPICH 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.
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.
3. 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.
Deactivation Procedure
1. Run the NodeB MML command MOD LOWPOWERPARA to turn off the
intelligent power shutdown switch with the NodeB ISD Switch set to DISABLE.
l 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.
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 P-
CPICH 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.
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.
3. 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.
Deactivation Procedure
1. Run the NodeB MML command SET ITELSHUTDOWN to turn off the intelligent
power shutdown switch with the ISD Switch set to DISABLE.
----End
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;
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020121
Intelligent Power Management.
Prerequisite
l Dependencies on Hardware
The NodeB type is BTS3900A or DBS3900.
Huawei APM30 and batteries are used.
l Dependencies on Other Features
This feature does not depend on other features.
l 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. Run the NodeB MML command SET PSUISS with the PSU Intelligent Shutdown
Switch set to ENABLE(ENABLE).
l Verification Procedure
1. Run the NodeB MML command LST PSUISS to check whether the PSU Intelligent
Shutdown Switch is set to ENABLE(ENABLE).
l Deactivation Procedure
1. Run the NodeB MML command SET PSUISS with the PSU Intelligent Shutdown
Switch set to DISABLE(DISABLE).
----End
Example
//Activation procedure
SET PSUISS: PSUISS=ENABLE;
//Verification procedure
LST PSUISS:;
//Deactivation procedure
SET PSUISS: PSUISS=DISABLE;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010613
AMR-WB (Adaptive Multi Rate Wide Band).
Prerequisite
l Dependencies on Hardware
The CN supports associated specifications.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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 Activation Procedure
1. Optional: Run the BSC6900 MML command SET UAMRCWB to set the RNC-
level speech rates for the gold, silver, and bronze users.
2. Optional: Run the BSC6900 MML command ADD UCELLAMRCWB to set cell-
level speech rates for the gold, silver, and bronze users.
l Verification Procedure
1. Optional: Run the BSC6900 MML command LST UAMRCWB to query the AMR-
WB speech rates of the gold, silver, and bronze users.
2. Optional: Run the BSC6900 MML command LST UCELLAMRCWB to query the
AMR-WB speech rates for the gold, silver, and bronze users.
3. On the BSC6900 LMT, open the Monitor tab page, choose Monitor > Monitor >
UMTS Monitoring > Cell Performance Monitoring, and create a task of AMR
Mode.
4. Enable the AMR-WB function on UE1 and UE2, and enable the UEs to camp on the
cell CELL_A11.
5. Use UE1 to initiate a voice call to UE2. The call is successfully established and the
voice is clear.
6. Check the AMR mode on the LMT and verify that the downlink rate of UE1 reaches
the specified value.
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 (WB-
AMRC) 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;
This section describes how to activate, verify, and deactivate the basic feature WRFD-020701
AMR/WB-AMR Speech Rates Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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 License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set CS Algorithm Switch to CS_AMRC_SWITCH.
2. Run the BSC6900 MML command SET UQOSACT to turn on the QoS switches for
AMR services.
3. Optional: Run the BSC6900 MML command SET UQUALITYMEAS or MOD
UTYPRABQUALITYMEAS to set the parameters for RNC-level AMR and AMR-
WB speech rate control based on link stability.
4. Optional: Set the parameters for AMR and AMR-WB speech rate control.
3. Two test UEs supporting AMR WB are available and camp on the cell named
CELL_A11. Use UE A to call UE B. The call is established.
4. Check whether the following information elements (IEs) are contained in the traced
RRC_MEAS_CTR message, as shown in Figure 184-2.
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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050405
Overbooking on ATM Transmission.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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:
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.
Take RNC configured with the AOU interface board as an example to describe how to
verify backpressure-based flow control.
1. On the BSC6900 LMT, start downlink traffic and bandwidth tracing tasks on the Uu,
Iub, and Iu interfaces.
2. Register an R99 user UE1 in the HLR. Enable UE1 with streaming services and with
both highest uplink rate and highest downlink rate of 384 kbit/s.
3. Register an HSDPA user UE2 in the HLR. Enable UE2 with background services and
with highest uplink rate of 384 kbit/s and highest downlink rate of 1450 kbit/s.
4. Run the BSC6900 MML command ADD TRMMAP to map R99 services to the high-
priority queue and HSDPA services to the low-priority queue.
5. All AAL2 paths of the RNC are carried on an IMA port. Enable the port flow control
when adding the IMA port.
6. Enable UE1 and UE2 to stay in idle mode and camp on the test cell. The test cell must
support HSDPA services.
7. Use UE1 to perform PS streaming services, that is, use UE1 to download files from
the FTP server.
Expected result: The IMA port is not congested and UE1 downloads data at the highest
rate.
8. Use UE2 to perform PS BE services, that is, use UE2 to download files from the FTP
server.
Expected result: The IMA port is congested and the backpressure function is triggered.
The downloading rate of UE2 decreases and that of UE1 remains unchanged. This is
because R99 services have a higher priority.
l 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. Run the BSC6900 MML command MOD IMAGRP. In this step, set Flow control
switch to OFF.
2. Run the BSC6900 MML command MOD UNILNK. In this step, set Flow control
switch to OFF.
3. Run the BSC6900 MML command MOD FRALNK. In this step, set Flow control
switch to OFF.
4. 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 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010617
VoIP over HSPA/HSPA+.
Prerequisite
l Dependencies on Hardware
This feature depends on the UE capability and the IP multimedia subsystem (IMS).
l 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 License
The license controlling this feature has been activated.
l 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.
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).
2. 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.
3. Optional: If VoIP services need to use the WRFD-01061403 HSUPA 2ms TTI
feature, run the BSC6900 MML command SET UCORRMALGOSWITCH. In this
step, select the MAP_HSUPA_TTI_2MS_SWITCH check box under the parameter
Service Mapping Strategy Switch. Go to Step 4.
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.
b. 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.
2) Run the BSC6900 MML command SET
UCORRMALGOSWITCH to select the
DRA_VOICE_SAVE_CE_SWITCH check box under the
parameter Dynamic Resource Allocation Switch.
5. Optional: To use the WRFD-01061404 HSUPA 2ms/10ms TTI HO feature, run the
BSC6900 MML command SET UCORRMALGOSWITCH. In this step, select the
DRA_VOICE_TTI_RECFG_SWITCH check box under the parameter Dynamic
Resource Allocation Switch.
6. To configure the EPF scheduling strategy, run the NodeB MML command SET
MACHSPARA to set Scheduling Method to EPF(Enhanced PF).
l 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 as shown in
Figure 186-1 to trace Uu interface signaling messages.
l Deactivation Procedure
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
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061703 Optimized Scheduling for VoIP over HSPA.
Prerequisite
l Dependencies on Hardware
The CN and UE support voice over IP (VoIP).
l 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+.
l License
The license controlling this feature has been activated.
Context
RAN10.0 supports VoIP over HSPA. To ensure the QoS of VoIP carried over HSPA, the non-
scheduling 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. Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling
Method to EPF(Enhanced PF).
l Verification Procedure
1. Run the NodeB MML command LST MACHSPARA to query the configuration
result.
l Deactivation Procedure
1. Run the NodeB MML command SET MACHSPARA. In this step, set Scheduling
Method to MAXCI(Max C/I), RR(Round Robin), or PF(PF).
----End
Example
//Activation procedure
SET MACHSPARA: LOCELL=0, SM=EPF;
//Verification procedure
LST MACHSPARA: LOCELL=0;
//Deactivation procedure
SET MACHSPARA: LOCELL=0, SM=PF;
This section describes how to activate, verify, and deactivate the basic feature WRFD-010618
IMS Signaling over HSPA.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command SET UFRCCHLTYPEPARA to set IMS
channel type to HSPA.
l 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 as shown in
Figure 188-1 to trace Uu interface signaling messages.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-011501
PDCP Header Compression (RoHC).
Prerequisite
l Dependencies on Hardware
The UE supports this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
l Verification Procedure
1. Initiate UE tracing on the BSC6900 LMT.
2. 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 Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010619
CS Voice over HSPA/HSPA+.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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.
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.
2. 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.
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.
b. 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.
2) Run the BSC6900 MML command SET
UCORRMALGOSWITCH to select the
DRA_VOICE_SAVE_CE_SWITCH check box under the
parameter Dynamic Resource Allocation Switch.
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.
5. To configure the EPF scheduling strategy, run the NodeB MML command SET
MACHSPARA to set Scheduling Method to EPF(Enhanced PF).
l 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
l Deactivation Procedure
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
This section describes how to activate, verify, and deactivate the optional feature WRFD-020801
Cell ID + RTT Function Based LCS.
Prerequisite
l Dependencies on Hardware
If SAS-CENTRIC locating is required, SAS equipment has been configured.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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 RNC-
CENTRIC 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.
Procedure
l Activation Procedure
1. Optional: If inter-RNC locating is required, the Iur interface needs to be configured.
For details, see 195 Configuring LCS over Iur.
2. Optional: If SAS-CENTRIC mode needs to be supported, the Iupc interface is
required. For details, see 196 Configuring Iupc Interface for LCS Service.
3. 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.
4. 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.
2. Use a UE to access the cell and enable the CN to send a locating request message.
3. The message LOCATION REPORTING CONTROL and LOCATION
REPORT are traced on the Iu interface, as shown in Figure 191-4 and Figure
191-5.
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.
5. From the traced Uu interface messages, you can see the information about the UE Rx-
Tx 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 Rx-
Tx time difference type 2 measurement is adopted), as shown in Figure 191-8 and
Figure 191-9.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020802
OTDOA Based LCS.
Prerequisite
l Dependencies on Hardware
The NodeB is configured with the Universal Satellite Card and Clock Unit (USCU)
board that is equipped with a GPS card.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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).
Procedure
l Activation Procedure
1. Optional: Configure the Iur interface if inter-RNC locating is required. For details,
see 195 Configuring LCS over Iur.
2. 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
Example
//Activating OTDOA Based LCS
//Setting the parameters for the SMLC algorithm
SET USMLC: SmlcMethod=OTDOA-1, OTDOAMethodType=UE_BASED,
LcsWorkMode=RNC_CENTRIC;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020803
A-GPS Based LCS.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
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.
l If the accurate location information about the antenna of the GPS receiver cannot be
obtained, the auto search mode can be selected.
Procedure
l Activation Procedure
NOTE
The BSC6900 and NodeB must be configured with the related data to activate this feature.
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.
7. 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.
8. 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.
9. Optional: Run the BSC6900 MML command STR POSAVE with Maximum time
for posave set to 12. Then, check the single point positioning results of the GPS
receiver in the \bam\common\fam\smlc directory.
Activation Procedure for NodeB 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. Run the NodeB MML command SET CLKMODE to set the working mode of the
reference clock source.
3. Run the NodeB MML command ADD GPS to add a GPS clock link.
4. Run the NodeB MML command MOD GPSPOS to add a GPS receiver.
If Way to Get Position is set to USER_CONFIG(User Config), set Antenna
Longitude, Antenna Latitude, and Antenna Altitude to appropriate values.
If Way to Get Position is set to SEARCH_WITH_DURATION(Search with
duration), set Duration to an appropriate value.
If Way to Get Position is set to SEARCH_WITH_PRECISION(Search with
precision), set Precision to an appropriate value.
l 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.
2. Make a UE access the network and enable the CN to send a positioning request.
3. Over the Iu interface, you can view the Location Reporting Control and Location
Report messages, as shown in Figure 193-3 and Figure 193-4.
4. The Uu interface tracing messages contain the information about A-GPS positioning
measurement, as shown in Figure 193-5 and Figure 193-6.
Example
/*Activating A-GPS Based LCS*/
This section describes how to activate, verify, and deactivate the optional feature WRFD-020804
LCS Classified Zone.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
l Verification Procedure
1. Initiate Iub interface message tracing on the BSC6900 LMT, as shown in Figure
194-1.
2. Enable the UE to establish a service of any type. Move the UE from cell A (whose
LAC and SAC are 9513 and 272 respectively) to cell B (whose LAC and SAC are
9514 and 273 respectively), to add cell B to the active set.
If a LOCATION REPORT message is displayed, this feature has been activated.
If the value of the information element (IE) "Cause" in the LOCATION REPORT
message is "User Restriction Start Indication", the UE enters the classified zone.
The SAI of the UE is also contained in the message, as shown in Figure 194-2.
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.
l 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
This section describes how to activate, verify, and deactivate the optional feature WRFD-020805
Configuring LCS over Iur.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
l 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
l Activation 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.
2. Configure cell information exchange over the Iur interface.
(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.
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.
NOTE
You can see INFORMATION EXCHANGE INITIATION REQUEST and
INFORMATION EXCHANGE INITIATION RESPONSE messages only after the
BSC6900 MML command ACT GPS is executed.
3. Establish a service, and then perform a soft handover over the Iur interface.
4. Enable the CN to send a LOCATION REPORTING CONTROL message with the
cause "DIRECT".
5. Check messages traced over the Iur interface. You can find an Information Exchange
Initiation procedure. In this procedure, the local RNC sends the NRNC an
INFORMATION EXCHANGE INITIATION REQUEST message, in which the
value of Information Type is UTRAN Access Point Position with Altitude, as
shown in Figure 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.
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.
l 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.
2. Run the BSC6900 MML command RMV UIURCOMMSCCP to deactivate LCS
over Iur.
----End
Example
/*Activating LCS over Iur*/
//Setting the positioning method
SET USMLC: SmlcMethod=CELLID_RTT-1&OTDOA-0&AGPS-0;
/*Configuring cell information exchange over the Iur interface*/
ADD UIURCOMMSCCP: SRN=0, SN=1;
ADD USMLCCELL: RNCId=29, CellId=1, CellLocCfgType=CELL_ANTENNA, GCDF=DEG,
MTRLGY=MET, AntennaLatitudeDegree=31245560,
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020807
Iupc Interface for LCS service.
Prerequisite
l Dependencies on Hardware
IP interface boards of the BSC6900 support this feature.
A Stand-Alone SMLC (SAS) is configured.
l 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 License
The license controlling this feature has been activated.
l Other Prerequisites
The UE supports at least one of the following positioning methods:
UE-assisted CELLID+RTT
UE-based A-GPS
UE-assisted A-GPS
The global data is configured by performing the following procedure:
1. Configuring the Basic Data
2. Configuring the OPC and DPC
3. Configuring the Area Information
4. Configuring the M3UA Local and Destination Entities
Physical layer data and data link layer data are configured by performing the following
procedure:
1. Configuring the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/
GOUc Board
2. Configuring the Physical Layer and Data Link Layer for the PEUa Board
3. Configuring the Physical Layer and Data Link Layer for the POUa/POUc Board
4. Configuring the User Plane of the Iub Interface (over ATM)
Context
Only IP transmission can be applied between the BSC6900 and the SAS. The transport network
layer data on the Iupc interface needs to be configured at the BSC6900. When the BSC6900 is
connected to multiple SASs through IP transmission, you need to configure this feature on each
Iupc interface. One BSC6900 can be connected to a maximum of four SASs simultaneously.
NOTE
Before configuring the Iupc interface data, familiarize yourself with Protocol Structure and Links on the
Iupc Interface.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command ADD N7DPC to add the destination signaling
point (DSP) data that corresponds to the SAS.
2. 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.
3. 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. Run the BSC6900 MML command ADD M3RT to add an M3UA route.
6. Run the BSC6900 MML command ADD M3LNK to add an M3UA link. To add more
M3UA links, run this command repeatedly.
7. Run the BSC6900 MML command ADD USAS to add the SAS.
8. 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.
l Verification Procedure
1. Perform the verification procedures by referring to 191 Configuring Cell ID + RTT
Function Based LCS or 193 Configuring A-GPS Based LCS.
l 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;
This section describes how to activate, verify and deactivate the optional feature WRFD-021304
RAN Sharing Introduction Package.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature cannot be used together with the feature WRFD-021311 MOCN
Introduction Package.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this
step, set RAN Sharing Support to YES to turn on the RAN sharing switch.
2. Run the BSC6900 MML command ADD UCNOPERATOR twice to add the primary
and secondary operators respectively.
3. Run the BSC6900 MML command ADD UCNOPERGROUP twice to add an
operator group respectively for the primary and secondary operators.
4. Run the BSC6900 MML command ADD OPC for multiple times to add OSPs for
primary and secondary operators.
NOTE
Primary and secondary operators can have their own OSPs for the same BSC6900.
l Primary and secondary operators can share the same Network ID when required.
l When primary and secondary operators share the same Network ID, they must use the
same OSP code bits but different OSP code[Whole Number].
l When primary and secondary operators do not share Network ID, they can have different
values for OSP code bits.
5. Run the BSC6900 MML command ADD N7DPC for multiple times to add DSPs for
primary and secondary operators.
6. Configure Iu data for the primary and secondary operators.
7. Run the BSC6900 MML command ADD UCNNODE for multiple times to add CN
nodes for the primary operator.
8. Configure Iub data and add a dedicated cell.
NOTE
Example
//Activating RAN Sharing Introduction Package
//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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02130401 Dedicated Carrier for Each Operator.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021304 RAN Sharing Introduction Package has been configured
before this feature is activated.
l License
The license controlling this feature has been activated.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this
step, set RAN Sharing Support to YES to turn on the RAN sharing switch.
2. Run the BSC6900 MML command ADD UCNOPERATOR to add the primary and
secondary operators.
3. Run the BSC6900 MML command ADD UCNOPERGROUP twice to add an
operator group respectively for the primary and secondary operators.
4. Configure Iu data for the primary and secondary operators.
5. Configure Iub data and add a dedicated cell.
NOTE
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. Run the BSC6900 MML command SET UOPERATORSHARINGMODE. In this
step, set RAN Sharing Support to NO to turn off the RAN sharing switch.
2. Run the BSC6900 MML command RMV UCELL to remove all cells configured for
the operator.
----End
Example
//Activating Dedicated Carrier for Each Operator
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02130402 Flexible Network Architecture.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
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.
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
This section describes how to activate, verify, and deactivate the optional feature
WRFD02130403 Mobility Control and Service Differentiation.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
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.
l Verification Procedure
The cells that belong to different operators can be configured as intra-frequency, inter-
frequency, or inter-RAT neighboring cells.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set
the parameter RAN Sharing Support to YES. Then, set the parameters Intra RAT
Inter Plmn Ho Allowed and Inter RAT Inter Plmn Ho Allowed to NO.
----End
Example
//Activating Mobility Control and Service Differentiation
SET UOPERATORSHARINGMODE: RANSharingSupport=YES,
InterPlmnHoAllowedIntraRat=YES, InterPlmnHoAllowedInterRat=YES;
//Deactivating Mobility Control and Service Differentiation
SET UOPERATORSHARINGMODE: RANSharingSupport=YES,
InterPlmnHoAllowedIntraRat=NO, InterPlmnHoAllowedInterRat=NO;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02130404 Independent License Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021304 RAN Sharing Introduction Package has been configured
before this feature is activated.
l License
The license controlling this feature has been 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. Run the BSC6900 MML command SET LICENSE to configure a license for the
primary operator.
2. Run the BSC6900 MML command SET LICENSE to configure a license for the
secondary operator.
l Verification Procedure
This feature does not need to be verified.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
Example
//Activating Independent License Control
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, CNOPERATORINDEX=0,
CsErlang=30000, FUNCTIONSWITCH1=PDCP-1;
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=NO, CNOPERATORINDEX=1,
CsErlang=20000;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021305
RAN Sharing Phase 2.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The features WRFD-021304 RAN Sharing Introduction Package must be configured
before this feature is activated.
l 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 Verification Procedure
This feature does not need to be verified.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02130501 Dedicated Iub Transmission Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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 License
The license controlling this feature has been activated.
Context
This feature provides separate admission control policies for operators that share the same port,
thereby ensuring the basic bandwidth available to each operator and improving bandwidth
efficiency when the Iub resources are idle.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command ADD OPSEPINFO to add the separate
information for operators, including bandwidth ratio and load threshold for each
operator.
NOTE
This feature can be enabled for one to four operators as required. The bandwidth ratios and load
thresholds for these operators need to be separately configured. Note that the sum of the bandwidth
ratios for all valid operators must be 100%.
2. Run the BSC6900 MML command ADD FRALNK, ADD UNILNK, or ADD
IMAGRP to add a physical port and configure Index of Separate Information for
Operators for the links carried on the physical port. In addition, set Operator
Separated Flag to ON(ON).
NOTE
If IP transmission is used on the port, configure separate information for operators based on IP
transmission by repeating the BSC6900 MML command ADD PPPLNK or ADD MPGRP.
3. Run the BSC6900 MML command ADD UNODEB to add a NodeB. In this step, set
Sharing Type Of NodeB to RANSHARING(RAN Sharing).
4. Run the BSC6900 MML command ADD ADJNODE to add an adjacent node.
5. Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path.
6. 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.
l 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.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021303
IMSI-Based Handover.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to
enable RAN Sharing.
2. Run the BSC6900 MML command ADD ULASNAMAP. In this step, set PLMN to
46000, LAC to 1234, and SNAC to 1.
3. 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.
l Verification Procedure
1. Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of
H'1234. The UE is admitted to the cell.
2. Use the UE with the IMSI of 460071234000006 to access the cell with the LAC of
H'1235. The UE is rejected by the cell. In this case, you can view the RRC
CONNECTION REJECT message on the Uu interface.
NOTE
The restrictions on cell update, UTRAN registration area (URA) update, handovers,
relocations, and handling COMMON ID messages are the same as that on RRC connection
request.
l Deactivation Procedure
1. Run the BSC6900 MML command RMV ULASNAMAP to remove a mapping
relationship between LAC and SNA.
2. Run the BSC6900 MML command RMV UIMSISNAMAP to remove a mapping
relationship between IMSI and SNA.
----End
Example
//Activating IMSI-Based Handover
This section describes how to activate, verify, and deactivate the optional feature WRFD-021311
MOCN (Multi-Operator Core Network) Introduction Package.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature cannot be used together with the feature WRFD-021304 RAN Sharing
Introduction Package.
l License
The license controlling this feature has been activated.
l 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.
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.
2. Run the BSC6900 MML command ADD UCNOPERATOR to add a secondary
operator. In this step, set Cn Operator Name, MCC, MNC, and Cn Operator
Index to appropriate values.
3. Run the BSC6900 MML command SET LICENSE to activate the license for the
primary operator.
4. Run the BSC6900 MML command SET LICENSE to activate the license for the
secondary operator.
5. Run the BSC6900 MML command ADD UCNOPERATOR to add a common
operator.
NOTE
If the MOCN operator has applied for a new PLMN, a common operator needs to be configured.
If the MOCN operator does not apply for a new PLMN, a common operator does not need to
be configured.
6. Run the BSC6900 MML command ADD UCNOPERGROUP to add an operator
group.
NOTE
When no common operator is configured, set the common operator index (CnOpIndex1) of the
operator group to the default value 255.
7. Run the BSC6900 MML command SET UOPERATORSHARINGMODE to set
the sharing mode for the operators. Set RAN Sharing Support to NO. Set MOCN
Support to YES. Set Intra RAT Inter Plmn Ho Allowed, Inter RAT Inter Plmn
Ho Allowed, Default CnOperator, and Mocn Control Switch to appropriate values
based on the network plan.
8. Run the BSC6900 MML command SET UOPERATORCFGPARA to set
parameters for the primary operator.
9. Run the BSC6900 MML command SET UOPERATORCFGPARA to set
parameters for the secondary operator.
10. Configure Iu interface transmission data between the BSC6900 and the primary and
secondary operators' CNs by referring to Configuring Interface Data.
11. Run the BSC6900 MML command ADD UCNNODE to add a CN node for the
primary operator.
12. Run the BSC6900 MML command ADD UCNNODE to add a CN node for the
secondary operator.
13. Run the BSC6900 MML command ADD UNRIGLBCNIDMAP to add a mapping
between Network Resource Identifiers (NRIs) and CN nodes.
NOTE
The mapping between NRIs and CN nodes needs to be configured based on the network plan.
If a CN node is configured with multiple NRIs, repeat this step until all the required mapping
relationships are configured.
14. Run the BSC6900 MML command ADD UNODEB to add an MOCN NodeB. In this
step, set Sharing Type Of NodeB to MOCN and set other parameters based on the
network plan.
15. (Optional) Run the BSC6900 MML command ADD UNODEB to add a dedicated
NodeB.
16. Configure the area information by referring to Configuring the Area Information.
NOTE
Location areas must be the same for the primary and secondary operators.
17. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add an MOCN
cell.
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
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 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02131101 Carrier Sharing by Operators.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021311 MOCN Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l The CN supports the MOCN feature.
Context
This feature enables multiple operators to share the same carrier.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add an MOCN
cell so that multiple operators can share the same carrier.
l Verification Procedure
1. 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.
The IE Multiple PLMN List contains the PLMNs (302221 and 302640) of the actual
operators.
l 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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02131102 Dedicated NodeB/Cell for Operators.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021311 MOCN Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
Context
This feature enables operators to independently control a NodeB or cell when the MOCN feature
is enabled.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command ADD UNODEB to add a dedicated NodeB.
2. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add a dedicated
cell.
l Verification Procedure
1. 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).
l Deactivation Procedure
1. Run the BSC6900 MML command RMV UCELL to remove the dedicated cell.
2. Run the BSC6900 MML command MOD UNODEB to change a dedicated NodeB
into a shared NodeB.
3. Run the BSC6900 MML command ADD UCELLQUICKSETUP to add a shared
cell.
----End
Example
//Activating Dedicated NodeB/Cell for Operators
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02131103 MOCN Mobility Management.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021311 MOCN Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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.
l Verification Procedure
1. When the cross-PLMN handover switch is turned on, check whether UEs can perform
cross-PLMN handovers, relocations, and cell updates. If UEs can perform cross-
PLMN handovers, relocations, and cell updates, this feature has been activated.
l Deactivation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02131104 MOCN Load Balance.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021311 MOCN Introduction Package has been configured before
this feature is activated.
l 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.
l Verification Procedure
1. Run the BSC6900 MML command LST UOPERATORSHARINGMODE to query
the parameter settings of the feature MOCN Load Balance.
l Deactivation Procedure
1. 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
Example
//Activating MOCN Load Balance
SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=255;
//Deactivating MOCN Load Balance
SET UOPERATORSHARINGMODE: MOCNSupport=YES, DefaultCnOp=0;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-02131106 Routing Roaming UEs in Proportion.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-021311 MOCN Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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
l Activation 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
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.
l 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.
2. When UEs belonging to operator A roam to the RNC shared by operator1 and
operator2 by using the MOCN for a long measurement period, view the performance
counter VS.ROAM.MOCN.NUM on the M2000. Expected result: The roaming UEs
of operator A are routed to CN nodes of operator1 and operator2 in a preset proportion
of 30:70.
NOTE
UEs of the non-supporting UE type do not support network sharing, as defined in the feature
WRFD-02131101 Carrier Sharing by Operators.
This feature is not applicable to UEs of the supporting UE type (supporting network sharing).
l Deactivation Procedure
1. Run the BSC6900 MML command RMV UROAMMAP to remove operator A from
the roaming relation list of operator1.
2. 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*/
//Removing operator A serving roaming UEs from the roaming relation list
of operator1
//Removing operator A serving roaming UEs from the roaming relation list
of operator2
RMV UROAMMAP: MCC="460", MNC="09", CnOpIndex=2, CnOpGrpIndex = 1;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021302
Iu Flex.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
2. Configure the Iu interface transmission between BSC6900 and multiple core networks
(CNs) by referring to Configuring the Interfaces.
3. Run the BSC6900 MML command ADD UCNNODE to add multiple CN nodes for
an operator according to the network plan.
4. 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.
After configuring the mapping relationships, the RNC routes the UE whose IMSI is
within the IMSI range to the specified CN.
l Verification Procedure
1. Enable the UE to access a cell and register in the cell.
2. According to the mapping relationships between IMSI ranges and CN nodes and the
load balance algorithm, the RNC selects a CN node for the UE, and the UE registers
successfully.
3. Then, if the UE initiates a service, the RNC routes the UE to the corresponding CN
node according to the mapping relationships between NRI and CN nodes.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UOPERATORCFGPARA to deactivate
this feature.
----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 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
This section describes how to activate, verify, and deactivate the optional feature WRFD-021306
Iu Flex Load Distribution Management.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-021302 Iu Flex has been configured before this feature is activated.
l License
The license controlling this feature has been activated.
l 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.
Configuring load balancing in dynamic capacity mode
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.
Load balancing in dynamic capacity mode takes effect only when the BSC6900 is
connected to Huawei CN and the preceding switches related to Iu Flex are turned on.
Configuring load redistribution based on NullNRI
1. Run the BSC6900 MML command MOD UCNNODE. In this step, set Status of
CN Node to OFFLOAD.
2. Run the BSC6900 MML command SET UOPERATORCFGPARA. In this step,
set NullNRI VALUE to an appropriate value based on the network plan.
Configuring load redistribution based on Block CN Node
1. 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.
l Verification Procedure
Verifying load balancing in static capacity mode
1. Run the BSC6900 MML command DSP UCNNODE to query the capacity ratio
of CN nodes.
2. Check the following performance counters on the M2000 to verify that the
BSC6900 performs load balancing based on the preconfigured CN capacity:
Performance counters for CS service setup:
VS.IU.LdBalRtCS.IMSI
VS.IU.LdBalRtCS.InValidNRI
VS.IU.LdBalRtCS.IMEI
Performance counters for PS service setup:
VS.IU.Load.RoutePS.IMSI
VS.IU.Load.RoutePS.NRI
VS.IU.Load.RoutePS.IMEI
Verifying load balancing in dynamic capacity mode
1. Run the BSC6900 MML command DSP UCNNODE to query the capacity ratio
of CN nodes.
2. On the BSC6900 LMT, choose Trace > UMTS Services to initiate Uu and Iu
interface message tracing.
3. Check the traced messages. If the CN sends the BSC6900 an INFORMATION
TRANSFER INDICATION message, the dynamic CN capacity ratio is updated
and used. If the CN does not send any INFORMATION TRANSFER
INDICATION message to the BSC6900, the static CN capacity ratio is used.
4. Check the following performance counters on the M2000 to verify that the
BSC6900 performs load balancing based on the dynamic CN capacity ratio:
Performance counters for CS service setup:
VS.IU.LdBalRtCS.IMSI
VS.IU.LdBalRtCS.InValidNRI
VS.IU.LdBalRtCS.IMEI
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020160
Enhanced Multiband Management.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been activated.
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 inter-
frequency 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. Run the BSC6900 MML command SET UDRD to set Measurement-Based DRD
Switch to ON.
2. 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. Run the BSC6900 MML command MOD UINTERFREQNCELL to set
DrdOrLdrFlag to TRUE(Send).
2. Run the BSC6900 MML command MOD UCELLLDR to set InterFreq Load
Handover Method Selection to MEASUREHO.
l Verification Procedure
Verify this feature based on the traffic steering-based handover function.
1. Configure cell A to provide R99 services and configure cell B to provide HSPA
services.
2. Enable the UE to set up an R99 service in cell A and then raise the service rate of the
UE.
3. Monitor the RRC_MEAS_CTRL message on the Uu interface to view the inter-
frequency measurement control information element (IE), as shown in Figure
213-1.
1. Run the BSC6900 MML command SET UDRD to set Measurement-Based DRD
Switch to OFF.
Deactivate this feature based on the load sharing-based handover function.
1. Run the BSC6900 MML command MOD UCELLLDR to set InterFreq Load
Handover Method Selection to BLINDHO.
----End
Example
//Configuring this feature based on the traffic steering-based function
This section describes how to activate, verify, and deactivate the optional feature WRFD-050104
Satellite Transmission on Iub Interface.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command MOD UNODEB. In this step, set Satellite Trans
Ind to TRUE.
2. Run the BSC6900 MML command ACT UCELL to activate a cell.
l Verification Procedure
1. Run the BSC6900 MML command DSP UCELL to check whether cell settings are
successful.
2. Establish an AMR service in the cell. The AMR service is established successfully
and the speech quality is satisfactory.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050108
Satellite Transmission on Iu Interface.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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.
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.
l Verification Procedure
1. Run the BSC6900 MML command LST SAALLNK to check whether the setting of
the timer is modified correctly.
2. Run the BSC6900 MML command DSP SAALLNK to query the status of SAAL
links. The result shows that SAAL link state is AVAILABLE.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010616
MBMS Introduction Package.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command SET UMBMSSWITCH to set MBMS Control
Switch to ON(ON).
2. Run the BSC6900 MML command ADD UMBMSSA to add the MBMS service area
according to the network plan.
3. 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.
4. Run the BSC6900 MML command ADD USCCPCHBASIC to add the SCCPCH
according to the network plan.
5. Run the BSC6900 MML command ADD UFACH to add the FACH according to the
network plan.
6. Run the BSC6900 MML command ADD UFACHDYNTFS to add the transport
format set (TFS) of an FACH according to the network plan.
7. Run the BSC6900 MML command ADD UFACH to add a logical channel mapped
to an FACH according to the network plan.
8. Run the BSC6900 MML command ADD USCCPCHTFC to add the Calculated
Transport Format Combination (CTFC) of an SCCPCH according to the network plan.
9. Run the BSC6900 MML command ADD UCELLMCCH to add the MCCH and the
MICH for the cell according to the network plan.
10. Configure the cell-level MBMS parameters according to the network plan.
(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.
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. Run the BSC6900 MML command DSP UCELLMBMSSERVICE to query the
MBMS status in the cell.
2. Conduct a test to check whether the MBMS UE can receive the corresponding MBMS
data successfully.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UMBMSSWITCH to set MBMS Control
Switch to OFF(OFF).
----End
Example
//Activation MBMS Introduction Package
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061602 MBMS Admission Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been 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.
l Verification Procedure
1. 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:
(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. Disable the MBMS admission algorithm, and the services are successfully admitted.
l Deactivation Procedure
1. 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.
----End
Example
//Activating MBMS Admission Control
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=MBMS_UU_ADCTRL-1,
NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061603 MBMS Load Control.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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.
2. Run the BSC6900 MML command MOD UCELLLDR to set the congestion-relief
action triggered by Load Reshuffling (LDR).
3. Run the BSC6900 MML command ADD UCELLOLC to set the sequence and
number of MBMS services to be released for Overload Control (OLC).
l Verification Procedure
1. Originate an MBMS service on the BSC6900, and ensure that service data is sent.
2. Run the BSC6900 MML command MOD UCELLLDM. Based on the current load
of the cell, set the triggering thresholds for LDR and OLC. Ensure that the
corresponding load control actions can be triggered.
3. When the cell load exceeds the LDR threshold, the power of MBMS services is
reduced in the cell. Check the maxFACH Power information element in the
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST
message on the Iub interface.
4. When the cell load exceeds the OLC threshold, MBMS services are released.
l Deactivation Procedure
1. 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.
2. Optional: Run the BSC6900 MML command MOD UCELLLDR to remove the
MBMS service power reduction from the LDR-triggered actions.
----End
Example
//Activating MBMS Load Control
//Enabling downlink load reshuffling and downlink overload congestion
control on the Uu interface
MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR-1&DL_UU_OLC-1;
//Setting the first LDR-triggered action to power reduction of MBMS
services
MOD UCELLLDR: CellId=1, DlLdrFirstAction=MBMSDECPOWER;
//Enabling the triggered OLC to release MBMS services on a one-by-one
basis
ADD UCELLOLC: CellId=1, SeqOfUserRel=MBMS_REL, MbmsOlcRelNum=1;
//Verifying MBMS Load Control
MOD UCELLLDM: CellId=1, DlLdrTrigThd=2, DlLdrRelThd=1, DlOlcTrigThd=2,
DlOlcRelThd=1;
//Deactivating MBMS Load Control
MOD UCELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch= DL_UU_LDR-0&DL_UU_OLC-0;
MOD UCELLLDR: CellId=1, DlLdrFirstAction=NoAct;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061605 MBMS Transport Resource Management.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The features WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been 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.
Procedure
l Activation Procedure
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061606 Streaming Service on MBMS.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l License
The license controlling this feature has been activated.
Context
This feature enables the MBMS service to be carried on the PS streaming class, therefore
ensuring QoS.
Procedure
l Activation Procedure
This feature can be activated only after MBMS basic functions are enabled. For details, see
the section "Configuring MBMS Introduction Package".
The 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. Use an MBMS-supportive UE to request an MBMS mobile television service and
receive the corresponding data.
2. The UE receives the data of the MBMS mobile television service successfully.
l Deactivation Procedure
This feature is used as long as MBMS is configured. There is no need to deactivate this
feature.
----End
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01061608 16/32/64/128Kbps Channel Rate on MBMS.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The features WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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
----End
This section describes how to activate, verify, and deactivate the optional feature WRFD-010660
MBMS Phase 2.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The features WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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:
Procedure
l Activation Procedure
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01066001 MBMS Enhanced Broadcast Mode.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The features WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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 Activation Procedure
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;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01066002 MBMS P2P over HSDPA.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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.
l License
The license controlling this feature has been 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. Run the BSC6900 MML command SET URNCMBMSPARA. In this step, set Mbms
Transfer Mode to DYNAMIC.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
set Service Mapping Strategy Switch to
MAP_PS_STREAM_ON_HSDPA_SWITCH.
l Verification Procedure
1. Set up a 256 kbit/s MBMS streaming service.
2. Use an MBMS-capable UE to request the MBMS service and receive the
corresponding data.
l Deactivation Procedure
To deactivate this feature, switch off the license item of the feature.
----End
Example
//Activating MBMS P2P over HSDPA
SET URNCMBMSPARA: MbmsTransMode= DYNAMIC;
SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01066003 MBMS Admission Enhancement.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package must be configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command SET UQUEUEPREEMPT to set Mbms
PreemptAlgoSwitch and Preempt algorithm switch to ON.
2. 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 Verification Procedure
Example
//Activating MBMS Admission Enhancement
SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, MbmsPreemptAlgoSwitch=ON;
SET URNCMBMSPARA: MbmsTransMode=PTM, PtmPreemptSwitch=ON,
PtmStrmPasiSwitch=ON, PtmNullStrmPasiSwitch=ON;
This section describes how to activate, verify, and deactivate the optional feature
WRFD-01066004 Inter-Frequency Neighboring Cell Selection for MBMS PTP Users.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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 Activation Procedure
The feature does not need to be activated.
l Verification Procedure
This feature does not need to be verified.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
This section describes how to activate, verify, and deactivate the optional feature WRFD-010627
FACH Transmission Sharing for MBMS.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been 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. Run the BSC6900 MML command SET UMBMSSWITCH. In this step, set MBMS
Iub Sharing Switch to ON(ON).
l Verification Procedure
1. Before turning on the transmission sharing switch, activate the MBMS services in two
cells served by the same NodeB. View the tracing messages over the Iub interface.
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.
2. Turn on the transmission sharing switch, activate the MBMS services in two cells
served by the same NodeB, and view the tracing messages over the Iub interface.
Example
//Activating FACH Transmission Sharing for MBMS
SET UMBMSSWITCH: MbmsSwitch=ON, MbmsIubSharingSwitch=ON;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010626
MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer Dispersion).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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.
Procedure
l Activation 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. Run the BSC6900 MML command MOD UCELLMCCH. In this step, set Flc Algo
Switch to ON(ON).
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
select the HO_ALGO_MBMS_FLC_SWITCH check box under the parameter
HandOver Switch.
l Verification Procedure
1. Configure an MCCH in an R99 cell and set an MBMS cell to the neighboring cell of
the R99 cell.
2. Make UEs camp on the R99 cell, activate the MBMS service, and accept the MBMS
service.
If UEs are reselected to the MBMS cell successfully and transmit and receive data
normally, FLC is activated.
3. Move UEs to the MBMS cell edge and terminate the MBMS service.
If some UEs are reselected to the R99 cell, FLD is activated.
l Deactivation Procedure
1. Run the BSC6900 MML command MOD UCELLMCCH. In this step, set Flc Algo
Switch to OFF(OFF).
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
deselect the HO_ALGO_MBMS_FLC_SWITCH check box under the parameter
HandOver Switch.
----End
Example
//Activating MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer
Dispersion)
MOD UCELLMCCH: CellId=1, FlcAlgoSwitch=ON;
SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-1;
//Deactivating MBMS FLC(Frequency Layer Convergence)/FLD(Frequency Layer
Dispersion)
MOD UCELLMCCH: CellId=1, FlcAlgoSwitch=OFF;
SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_MBMS_FLC_SWITCH-0;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010661
MBMS over Iur.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010660 MBMS Phase 2 has been configured before this feature is
activated.
l License
The license controlling this feature has been activated.
l 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 Deactivation Procedure
This section describes how to activate, verify, and deactivate the optional feature WRFD-010662
Dynamic Power Estimation for MTCH.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010660 MBMS Phase 2 has been configured before this feature is
activated.
l License
The license controlling this feature has been 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.
l 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.
2. Use an MBMS-capable UE to initiate an MBMS service in cell A. View the
NBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub interface to
check the power of the FACH that carries the service.
3. Set cell B to send MBMS data in the same channel in PTM mode. In this manner, the
rate of the intra-frequency neighboring cells that apply the PTM mode exceeds the
value of the preset Combine Neighbour Cell Percent.
4. View the NBAP_COMM_TRANSP_CH_SETUP_REQ message traced on the Iub
interface to check the power of the FACH that carries the service.
Expected result: The power of the FACH that carries data of the MBMS channel
decreases by 5 dB.
l Deactivation Procedure
This feature does not need to be deactivated.
----End
Example
//Setting the Power Adjusting Threshold
SET URNCMBMSPARA: CombNCellPercent=50;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010663
MSCH Scheduling.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
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).
l Verification Procedure
1. Use an MBMS-capable UE to initiate an MBMS service and ensure that the UE can
receive the MBMS data.
2. Check messages traced on the Uu interface. If MSCH configuration information is
found in the MBMS CURRENT CELL P-T-M RB INFORMATION, MBMS
GENERAL INFORMATION, and MBMS NEIGHBOURING CELL P-T-M RB
INFORMATION messages, this feature has been activated.
l Deactivation 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 OFF(OFF).
----End
Example
//Activating MSCH scheduling
SET UMBMSSWITCH: MbmsSwitch=ON, MschSwitchForNonMtchMulti=ON,
MschSwitchForMtchMulti=ON;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010665
Configuring MBMS Channel Audience Rating Statistics.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010616 MBMS Introduction Package has been configured before
this feature is activated.
l License
The license controlling this feature has been activated.
l 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 Activation Procedure
This feature does not need to be activated.
l 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
This section describes how to activate, verify, and deactivate the optional feature WRFD-020114
Domain Specific Access Control (DSAC).
Prerequisite
l Dependencies on Hardware
DSAC is based on the CN overload message and therefore the CN nodes should support
this message on the Iu interface.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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
l Deactivation Procedure
1. To deactivate manual DSAC, run the BSC6900 MML command RMV
UCELLDSACMANUALPARA.
2. 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&AC10-
0&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&AC10-
0&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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020111
One Tunnel.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
l Verification Procedure
1. Start message tracing on the Iu interface on the BSC6900 LMT by referring to Tracing
Messages on the Iu Interface.
l Deactivation Procedure
This section describes how to activate, verify, and deactivate the optional feature WRFD-050402
IP Transmission Introduction on Iub Interface.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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:
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.
l The built-in firewall on the NodeB side safeguards the Iub interface against network attacks
during IP transmission.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command SET ETHPORT to set the attributes of an
Ethernet port. In this step, takes the FG2c board as an example.
2. Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet
port.
3. Run the BSC6900 MML command STR IPCHK to configure the BFD check. In this
step, set Check type to SBFD.
4. Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall
function for an interface board. In this step, set Board type. to FG2c and ARP
Learning Strict Switch to ON.
NOTE
The FG2c and GOUc boards support both the invalid packet detection function and the ARP learning
strict function. The FG2a and GOUa boards support only the ARP learning strict function.
5. (Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS
supports the built-in firewall function) by performing the following operations: Log
in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux
command iptables -A INPUT s restricted IP -i Ethernet adapter p transport
protocol --dport restricted port j DROP. Here, restricted IP refers to the IP address
that needs to be prohibited or allowed, and it can be a single IP address or a network
segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport
protocol can be TCP or UDP; restricted port is the port to be prohibited. If p transport
protocol and --dport restricted port are not specified, all ports are disabled.
6. Run the BSC6900 MML command ADD PPPLNK to configure head compress for
a PPP link. In this step, set Head compress to UDP/IP_HC(UDP/IP_HC). Run the
BSC6900 MML command ADD MPGRP to configure head compress for a PPP link
group. In this step, set Head compress to UDP/IP_HC(UDP/IP_HC).
NOTE
Head compress must be configured on peer equipment.
7. Run the NodeB MML command ADD PPPLNK to enable head compress for a PPP
link. Run the NodeB MML command ADD MPGRP to enable head compress for a
PPP link group.
8. Run the NodeB MML command ADD ACL to add an access control list (ACL).
9. Run the NodeB MML command ADD ACLRULE to add a rule to the ACL.
NOTE
Before adding a rule to an ACL, ensure that the ACL has already existed.
l Verification Procedure
1. Run the BSC6900 MML command DSP ETHPORT to query the attributes of an
Ethernet port.
2. Run the BSC6900 MML command LST ETHIP to query the IP address of the
Ethernet port.
3. Run the BSC6900 MML command DSP IPCHK to query whether the Check state
is UP.
4. Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP
Connectivity Check Failure is reported.
5. Run the BSC6900 MML command LST IPGUARD to check whether the value of
ARP Learning Strict Switch is ON.
6. Built response messages to ARP requests and sent to interface boards. Run the
BSC6900 MML command DSP ARP to query the ARP table of interface boards. If
the information of interface boards in ARP table do not update, the ARP Learning
Strict Switch is valid.
7. If any invalid packet exists, run the BSC6900 MML command DSP
INVALIDPKTINFO to query the detailed information.
8. (Optional) Log in to the computer whose IP address is prohibited and check whether
the prohibited services can be performed. Run the Dopra Linux command iptables
L. All the filtering rules on the OMU will be listed, and check whether new rules are
added successfully.
If port 80 is disabled, logging in to the BSC6900 LMT is prohibited. Check whether
you can log in to the BSC6900 LMT on the PC whose port 80 is disabled.
If port 22 is disabled, the OMU cannot be logged in to remotely. Check whether
you can log in to the BSC6900 OMU through Putty on the PC whose port 22 is
disabled.
If port 21 is disabled, FTP services of the OMU cannot be used. Check whether
you can connect to the FTP server of the BSC6900 OMU through an FTP client
on the PC whose port 21 is disabled.
9. Run the BSC6900 MML command DSP PPPLNK or DSP MPGRP to query whether
the Code compress type is UDP/IP_HC.
10. Run the NodeB MML command DSP PPPLNK or DSP MPGRP to check whether
the compress state is enable.
11. Run the NodeB MML command LST ACL to check whether an ACL has been
configured.
12. Run the NodeB MML command LST ACLRULE to check whether a rule has been
added to the ACL.
13. Run the NodeB MML command DSP PACKETFILTER to check whether a port is
bound to the ACL.
14. Run the NodeB MML command PING to use IP addresses that are not listed in the
ACL to ping the port supporting the packet filtering function. If no response is
received, the built-in firewall on the NodeB side has been activated.
l Deactivation Procedure
1. Run the BSC6900 MML command STP IPCHK to stop the BFD.
2. Run the BSC6900 MML command SET IPGUARD. In this step, set Board type to
FG2c and ARP Learning Strict Switch to OFF.
3. Run the BSC6900 MML command RMV ETHIP to remove an IP address from the
Ethernet port.
4. Run the BSC6900 MML command SET ETHPORT. In this step, set Port type to
FE.
5. (Optional) Log in to the OMU through the LMT locally or through Putty remotely.
Run the Dopra Linux command iptables -D INPUT s restricted IP -i Ethernet
adapter p transport protocol --dport restricted port j DROP. Here, restricted
IP is the IP address that needs to be prohibited or allowed, and it can be a single IP
address or a network segment; Ethernet adapter is the name of the OMU external
Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to
be prohibited, and it is used together with the transport protocol. If p transport
protocol and --dport restricted port are not specified, all ports are disabled.
6. (Optional) Run the Dopra Linux command iptables L. All the filtering rules on the
OMU will be listed, and check whether new rules are removed successfully.
7. Run the BSC6900 MML command MOD PPPLNK or MOD MPGRP. In this step,
set Head compress to No_HC.
8. Run the NodeB MML command RMV PPPLNK to remove a PPP link. Run the
NodeB MML command RMV MPGRP to remove a PPP link group.
9. Run the NodeB MML command RMV PACKETFILTER to remove the binding
relationship between the port and the ACL.
10. Run the NodeB MML command RMV ACLRULE to remove all the rules from the
ACL.
11. Run the NodeB MML command RMV ACL to remove the ACL.
----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,
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;
This section describes how to activate, verify and deactivate the optional feature WRFD-050403
Hybrid Iub IP Transmission.
Prerequisite
l Dependencies on Hardware
BTS3902E does not support this feature.
l 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 License
The license controlling this feature has been activated.
l 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. Run the BSC6900 MML command ADD UNODEB to add a NodeB. In this step, set
IUB Trans Bearer Type to HYBRID_IP_TRANS.
2. 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.
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. Run the BSC6900 MML command ADD TRMMAP. In this step, set Interface
Type to IUB and Transport Type to HYBIRD_IP.
5. 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.
l Verification Procedure
1. Use the UE to make a call. If the call is connected, you can infer that high-priority
services can access the high-priority IP paths normally and low-priority services can
access the low-priority IP paths normally.
2. Run the BSC6900 MML command DSP IPCHN to query the type of services carried
in the IP path, and the forward bit rate and backward bit rate of the services.
l Deactivation Procedure
1. Run the BSC6900 MML command RMV ADJMAP to remove the TRM mapping to
the adjacent node on the Iub interface.
2. Run the BSC6900 MML command RMV TRMMAP to remove the transmission
resource mapping on the Iub interface.
3. Run the BSC6900 MML command RMV IPPATH to remove the IP path on the Iub
interface.
----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,
This section describes how to activate, verify, and deactivate the optional feature WRFD-050404
ATM/IP Dual Stack NodeB.
Prerequisite
l Dependencies on Hardware
BSC6900 is configured with both ATM interface boards and IP interface boards.
BTS3902E does not support this feature.
l Dependencies on Other Features
The feature WRFD-050402 IP Transmission Introduction on Iub Interface must be
configured before this feature is activated.
l License
The license controlling this feature has been activated.
l 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
l Activation Procedure
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. Run the BSC6900 MML command ADD UNODEB to add a NodeB. In this step, set
IUB Trans Bearer Type to ATMANDIP_TRANS.
2. 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.
3. Run the BSC6900 MML command ADD TRMMAP. In this step, set Interface
Type to IUB and Transport Type to ATM_IP.
4. Run the BSC6900 MML command ADD AAL2PATH to add an AAL2 path.
5. 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.
6. 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.
l Verification Procedure
1. Use a UE to make a call. High-priority services can be carried on ATM paths and low-
priority services can be carried on IP paths.
2. Run the BSC6900 MML command DSP IPPATH to check the state of the IP path
and whether any resources of the path are occupied.
Expected result: Operation state is Available, and some resources of the path are
occupied.
3. Run the BSC6900 MML command DSP AAL2PATH to check the state of the AAL2
path and whether any resources of the path are occupied.
Expected result: Operation state is Available, and some resources of the path are
occupied.
l Deactivation Procedure
1. Run the BSC6900 MML command RMV ADJMAP to remove the TRM mapping to
the adjacent node.
2. Run the BSC6900 MML command RMV TRMMAP to remove the transmission
resource mapping on the Iub interface.
3. Run the BSC6900 MML command RMV IPPATH to remove the IP path on the Iub
interface.
----End
Example
//Configuring ATM/IP Dual Stack NodeB
//Adding a NodeB
ADD UNODEB: NodeBName="test", NodeBId=115, SRN=0, SN=0,
TnlBearerType=ATMANDIP_TRANS, IPTRANSAPARTIND=SUPPORT,
HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0;
//Adding 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050409
IP Transmission Introduction on Iu Interface.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
Context
This feature provides a new lu transmission solution for operators. Compared with ATM
transmission, IP transmission can significantly reduce the transmission cost.
Procedure
l Activation Procedure
The following takes the FG2c board as an example to describe the configuration operations.
1. Run the BSC6900 MML command SET ETHPORT to set the attributes of an
Ethernet port.
2. Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet
port.
3. Run the BSC6900 MML command STR IPCHK. In this step, set Check type to
SBFD.
4. Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall
function for an interface board. In this step, set Board type. to FG2c and ARP
Learning Strict Switch to ON.
NOTE
The FG2c and GOUc boards support both the invalid packet detection function and the ARP learning
strict function. The FG2a and GOUa boards support only the ARP learning strict function.
5. (Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS
supports the built-in firewall function) by performing the following operations: Log
in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux
command iptables -A INPUT s restricted IP -i Ethernet adapter p transport
protocol --dport restricted port j DROP. Here, restricted IP refers to the IP address
that needs to be prohibited or allowed, and it can be a single IP address or a network
segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport
protocol can be TCP or UDP; restricted port is the port to be prohibited. If p transport
protocol and --dport restricted port are not specified, all ports are disabled.
l Verification Procedure
1. Run the BSC6900 MML command DSP ETHPORT to query the attributes of an
Ethernet port.
2. Run the BSC6900 MML command LST ETHIP to query the IP address of the
Ethernet port.
3. Run the BSC6900 MML command DSP IPCHK to query whether the Check state
is UP.
4. Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP
Connectivity Check Failure is reported.
5. Run the BSC6900 MML command LST IPGUARD to check whether the value of
ARP Learning Strict Switch is ON.
6. Built response messages to ARP requests and sent to interface boards. Run the
BSC6900 MML command DSP ARP to query the ARP table of interface boards. If
the information of interface boards in ARP table do not update, the ARP Learning
Strict Switch is valid.
7. If any invalid packet exists, run the BSC6900 MML command DSP
INVALIDPKTINFO to query the detailed information.
8. (Optional) Log in to the computer whose IP address is prohibited and check whether
the prohibited services can be performed. Run the Dopra Linux command iptables
L. All the filtering rules on the OMU will be listed, and check whether new rules are
added successfully.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050410
IP Transmission Introduction on Iur Interface.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l 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.
l 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. Run the BSC6900 MML command SET ETHPORT to set the attributes of an
Ethernet port.
2. Run the BSC6900 MML command ADD ETHIP to add an IP address to the Ethernet
port.
3. Run the BSC6900 MML command STR IPCHK. In this step, set Check type to
SBFD.
4. Run the BSC6900 MML command SET IPGUARD to configure the built-in firewall
function for an interface board. In this step, set Board type. to FG2c and ARP
Learning Strict Switch to ON.
NOTE
The FG2c and GOUc boards support both the invalid packet detection function and the ARP learning
strict function. The FG2a and GOUa boards support only the ARP learning strict function.
5. (Optional) Activate the built-in firewall function for O&M (only the Dopra Linux OS
supports the built-in firewall function) by performing the following operations: Log
in to the OMU through LMT locally or through Putty remotely. Run the Dopra Linux
command iptables -A INPUT s restricted IP -i Ethernet adapter p transport
protocol --dport restricted port j DROP. Here, restricted IP refers to the IP address
that needs to be prohibited or allowed, and it can be a single IP address or a network
segment; Ethernet adapter is the name of the OMU external Ethernet adapter; transport
protocol can be TCP or UDP; restricted port is the port to be prohibited. If p transport
protocol and --dport restricted port are not specified, all ports are disabled.
l Verification Procedure
1. Run the BSC6900 MML command DSP ETHPORT to query the attributes of an
Ethernet port.
2. Run the BSC6900 MML command LST ETHIP to query the IP address of the
Ethernet port.
3. Run the BSC6900 MML command DSP IPCHK to query whether the Check state
is UP.
4. Start BFD-based IP fault detection. If a BFD fails, an alarm ALM-21346 IP
Connectivity Check Failure is reported.
5. Run the BSC6900 MML command LST IPGUARD to check whether the value of
ARP Learning Strict Switch is ON.
6. Built response messages to ARP requests and sent to interface boards. Run the
BSC6900 MML command DSP ARP to query the ARP table of interface boards. If
the information of interface boards in ARP table do not update, the ARP Learning
Strict Switch is valid.
7. If any invalid packet exists, run the BSC6900 MML command DSP
INVALIDPKTINFO to query the detailed information.
8. (Optional) Log in to the computer whose IP address is prohibited and check whether
the prohibited services can be performed. Run the Dopra Linux command iptables
L. All the filtering rules on the OMU will be listed, and check whether new rules are
added successfully.
If port 80 is disabled, logging in to the BSC6900 LMT is prohibited. Check whether
you can log in to the BSC6900 LMT on the PC whose port 80 is disabled.
If port 22 is disabled, the OMU cannot be logged in to remotely. Check whether
you can log in to the BSC6900 OMU through Putty on the PC whose port 22 is
disabled.
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. Run the BSC6900 MML command STP IPCHK to stop the BFD.
2. Run the BSC6900 MML command SET IPGUARD. In this step, set Board type to
FG2c and ARP Learning Strict Switch to OFF.
3. Run the BSC6900 MML command RMV ETHIP to remove an IP address from the
Ethernet port.
4. Run the BSC6900 MML command SET ETHPORT. In this step, set Port type to
FE.
5. (Optional) Log in to the OMU through the LMT locally or through Putty remotely.
Run the Dopra Linux command iptables -D INPUT s restricted IP -i Ethernet
adapter p transport protocol --dport restricted port j DROP. Here, restricted
IP is the IP address that needs to be prohibited or allowed, and it can be a single IP
address or a network segment; Ethernet adapter is the name of the OMU external
Ethernet adapter; transport protocol can be TCP or UDP; restricted port is the port to
be prohibited, and it is used together with the transport protocol. If p transport
protocol and --dport restricted port are not specified, all ports are disabled.
6. (Optional) Run the Dopra Linux command iptables L. All the filtering rules on the
OMU will be listed, and check whether new rules are removed successfully.
----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
This section describes how to activate, verify, and deactivate the optional feature WRFD-050420
Configuring FP MUX for IP Transmission.
Prerequisite
l Dependencies on Hardware
The FG2a/FG2c, GOUa/GOUc, and POUc support FP multiplexing.
l Dependencies on Other Features
The feature WRFD-050402 IP Transmission Introduction on Iub Interface has been
configured before this feature is activated.
l License
The license controlling this feature has been activated.
l 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.
NOTE
You do not need to configure the number of packets for multiplexing, the BSC6900 selects
proper subframes for multiplexing based on the length of subframes. Subframes that meet the
following conditions are multiplexed into packets:
1. The total sending duration of subframes is smaller than Maximum Delay Time.
2. The length of the subframe is smaller than Max subframe length.
3. The total length of subframes plus eight is smaller than or equal to Maximum Frame
Length.
2. Run the NodeB MML command SET FPMUX to configure FP multiplexing on the
Iub interface on the NodeB side.
l Verification Procedure
1. Run the BSC6900 MML command DSP IPMUX to check IP packet multiplexing
conditions.
2. Run the NodeB MML command LST FPMUX to query the FP multiplexing condition
of an IP path.
l Deactivation Procedure
1. Run the BSC6900 MML command RMV IPMUX to disable the FP multiplexing
function for the IP path.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050422
Dynamic Bandwidth Control of Iub IP.
Prerequisite
l Dependencies on Hardware
The FG2a, FG2c, GOUa and GOUc support this feature for BSC6900.
l 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 License
The license controlling this feature has been activated.
Context
This feature enables the RNC to adjust the transmission bandwidth according to the packet loss
ratio and jitter over links detected by the IP performance monitor (PM). It is recommended that
flow control algorithm for bandwidth dynamic adjustment do not to use.
Procedure
l Activating Procedure
1. Run the BSC6900 MML command ADD IPLOGICPORT. In this step, set Auto
adjust bandwidth switch to ON.
2. Run the BSC6900 MML command ACT IPPM to activate the IP PM.
l Verification Procedure
1. Log on the BSC6900 LMT, click the Monitor tab. The Monitor Navigation Tree tab
page is displayed.
2. On the displayed monitoring navigation tree, choose Monitor > Common
Monitoring > Link Performance Monitoring. The Link Performance
Monitoring dialog box is displayed.
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.
l Deactivating Procedure
1. Run the BSC6900 MML command MOD IPLOGICPORT. In this step, set Auto
adjust bandwidth switch to OFF.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050408
Overbooking on IP Transmission.
Prerequisite
l 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.
l Dependencies on Other Features
The feature WRFD-050402 IP Transmission Introduction on Iub Interface must be
configured before this feature is activated.
l License
The license controlling this feature has been 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 RLC retransmission rate-based downlink congestion control
l Fast backpressure on interface boards
l 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.
Take the FE/GE-based IP transmission on the Iub interface as an example to describe how
to verify backpressure-based downlink flow control.
1. On the BSC6900 LMT, start downlink traffic and bandwidth tracing tasks on the Uu,
Iub, and Iu interfaces.
2. Register an R99 user UE1 in the HLR. Enable UE1 with streaming services and with
both highest uplink rate and highest downlink rate of 384 Kbit/s.
3. Register an HSDPA user UE2 in the HLR. Enable UE2 with background services and
with highest uplink rate of 384 Kbit/s and highest downlink rate of 1450 Kbit/s.
4. Run the BSC6900 MML command ADD TRMMAP to map R99 services to high-
priority queue and HSDPA services to low-priority queue.
5. All IP paths of the RNC are carried on a logical port. Enable the port flow control
when adding the logical port.
6. Enable UE1 and UE2 to stay in idle mode and camp on the test cell. The test cell must
support HSDPA services.
7. Use UE1 to perform PS streaming services, that is, use UE1 to download files from
the FTP server.
Expected result: The logical port is not congested and UE1 downloads data at the
highest rate.
8. Use UE2 to perform PS BE services, that is, use UE2 to download files from the FTP
server.
Expected result: The logical port is congested and the backpressure function is
triggered. The downloading rate of UE2 decreases and that of UE1 remains
unchanged. This is because R99 services have a higher priority.
l 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. Run the BSC6900 MML command MOD PPPLNK. In this step, set Flow control
switch to OFF.
2. Run the BSC6900 MML command MOD MPGRP. In this step, set Flow control
switch to OFF.
3. Run the BSC6900 MML command MOD IPLOGICPORT. In this step, set Flow
control switch to OFF.
Deactivating IP shaping
1. Run the BSC6900 MML command MOD IPPATH to modify a logical port. In
this step, set Bearing type to NULL(NULL).
2. Run the BSC6900 MML command MOD IPLOGICPORT. In this step, set Flow
control switch to OFF(OFF).
3. Run the BSC6900 MML command ADD IPPATH to add a logical port. In this
step, set Bearing type to IPLGCPORT.
----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 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,
VLANFlAG=DISABLE, PATHCHK=DISABLED;
//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;
This section describes how to activate, verify, and deactivate the feature WRFD-050412 UDP
MUX for Iu-CS Transmission.
Prerequisite
l Dependencies on Hardware
This feature is supported only by the BSC6900 that is configured with the FG2a/GOUa/
FG2c/GOUc/POUc boards.
l Dependencies on Other Features
The feature WRFD-050409 IP Transmission Introduction on Iu Interface has been
configured before this feature is activated.
l License
The license controlling this feature has been activated.
l 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 Activation Procedure
NOTE
Configure IP paths based on the network plan.
1. Run the BSC6900 MML command ADD IPMUX or MOD IPMUX to enable the Iu-
CS UDP MUX function. In this step, set IP MUX Type to UDPMUX, and set Max
subframe length[byte], Maximum Frame Length[byte], and Maximum Delay
Time[ms] to appropriate values based on the network plan. To enable the UDP MUX
function for multiple links, run this command for each of the links.
l Verification Procedure
1. 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 Sub-
frames.
l Deactivation Procedure
1. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050105
ATM Switching-Based Hub NodeB.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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 Activation Procedure
1. Run the NodeB MML command ADD TREELNKPVC to add a tree link PVC.
l Verification Procedure
1. Run the NodeB MML command LST TREELNKPVC to query the tree link PVC.
l Deactivation Procedure
1. Run the NodeB MML command RMV TREELNKPVC to remove the tree link PVC.
----End
Example
l NodeB V200R013
//Activation procedure
ADD TREELNKPVC: NO=1, JNRSCGRP=DISABLE, VST=VC_SWITCH, SRCSRN=0,
SRCSN=7, SRCSBT=BASE_BOARD,
This section describes how to activate, verify, and deactivate the optional feature WRFD-050106
AAL2 Switching-Based Hub NodeB.
Prerequisite
l Dependencies on Hardware
DBS 3800 does not support this feature.
l Dependencies on Other Features
WRFD-050105 ATM Switching-Based Hub NodeB
l 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. Run the NodeB MML command ADD AAL2NODE to add an AAL2 node. In this
step, set Node Type to HUB(Switching Node).
2. Run the NodeB MML command ADD AAL2ADJNODE to add an AAL2 adjacent
node to the lower-level NodeB.
l Verification Procedure
1. Run the NodeB MML command DSP AAL2NODE to query the configuration of the
AAL2 node.
2. Run the NodeB MML command DSP AAL2ADJNODE to query the configuration
of the AAL2 adjacent node.
l Deactivation Procedure
1. Run the NodeB MML command RMV AAL2ADJNODE to remove the AAL2
adjacent node.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050107
IP Routing-Based Hub NodeB.
Prerequisite
l Dependencies on Hardware
Only 3900 series base stations support this feature.
l Dependencies on Other Features
WRFD-050402 IP Transmission Introduction on Iub Interface
l 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. 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.
l Verification Procedure
1. Run the NodeB MML command DSP IPRT to query the configuration of the newly
added IP route.
l Deactivation Procedure
1. Run the NodeB MML command RMV IPRT to remove the IP route.
----End
Example
l NodeB V200R013
//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";
l 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";
This section describes how to activate, verify, and deactivate the optional feature WRFD-050425
Ethernet OAM.
Prerequisite
l Dependency on RNC Hardware
Only BSC6900 supports this feature.
l Dependency on NodeB Hardware
BTS3812E/AE, DBS3800,3900 series NodeB can support both IEEE 802.3ah and IEEE
802.1ag draft 8;
l 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.
l 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.
link monitoring, and fault detection and is not service, and it is not service-specific, as
shown in Figure 247-1.
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.
l Activating the Ethernet OAM 1AG Function
1. Run the BSC6900 MML command ADD CFMMD to add the Ethernet OAM
maintenance domain (MD). The Ethernet OAM MD consists of bridges and
maintenance equipment. Each MD is associated with a maintenance level. There are
eight maintenance levels, that is level 0 to level 7.
2. Run the BSC6900 MML command ADD CFMMA to add the Ethernet OAM
maintenance association (MA). Each MD can be divided into several MAs. Each MA
corresponds to a service instance identified by the VLAN in the MD.
3. Run the BSC6900 MML command ADD CFMMEP to add an Ethernet OAM
maintenance end point (MEP). You can add different local or remote maintenance
points of different MEP types to the MA.
NOTE
l The MEPID of the RemoteMep configured on the peer equipment must be consistent with
the MEPID of the LocalMep configured on the local equipment.
l MD, MA or MEP must be configured on the peer equipment when the MD, MA or MEP
has be added on BSC6900.
4. Run the BSC6900 MML command ACT CFMCCMTST to activate the Ethernet
OAM unidirectional connectivity detection between the local MEP and the remote
MEP.
l Verifying the Ethernet OAM 3AH Function
1. Activate the Ethernet OAM 3AH function. The Alarm-21371 ETHOAM 3AH
Detection Failure alarm is reported when Ethernet OAM detection fails. The
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.
l Verifying the Ethernet OAM 1AG Function
1. Activate the Ethernet OAM 1AG function. The running of the PING MAC and TRC
MAC fails if the transmission between the local MEP and the remote MEP is faulty
because the local MEP fails to receive the connectivity detection packet from the
remote MEP.
2. OAM 1AG function on the peer equipment must be activated, and the transmission is
functional that the local MEP succeeds to receive the CCM packets from the peer
MEP, the running of the PING MAC and TRC MAC succeeds.
l Deactivating the Ethernet OAM 3AH Function
1. Run the BSC6900 MML command DEA EFMAH to deactivate the Ethernet OAM
3AH function.
l Deactivating the Ethernet OAM 1AG Function
1. Run the BSC6900 MML command DEA CFMCCMTST to deactivate the Ethernet
OAM unidirectional connectivity detection.
2. Run the BSC6900 MML command RMV CFMMD to delete the Ethernet OAM
maintenance domain (MD).
3. Run the BSC6900 MML command RMV CFMMA to delete the Ethernet OAM
maintenance association (MA).
4. Run the BSC6900 MML command RMV CFMMEP to delete the Ethernet OAM
maintenance end point (MEP).
----End
Example
//Activating the Ethernet OAM 3AG function
ACT EFMAH: SRN=0, SN=18, PN=0;
//Activating the Ethernet OAM 1AG function
ADD CFMMD: SRN=0, SN=18, MDIDX=0, MDName="md0";
ADD CFMMA: SRN=0, SN=18, MDIDX=0, VLANID=2, MAIDX=0, MANAME="ma0";
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=LocalMep, MEPID=1, PORTTYPE=ETHER,
SN=18, PN=0;
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=RemoteMep, MEPID=11, SN=18;
ACT CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
//Verifying the Ethernet OAM 1AG function
PING MAC: SRN=0, SN=18, MAIDX=0, SRCMEPID=1, DESTMEPID=11;
TRC MAC: SRN=0, SN=18, MAIDX=0, SRCMEPID=1, DESTMEPID=11;
//Deactivating the Ethernet OAM 3AG function
DEA EFMAH: SRN=0, SN=18, PN=0;
//Deactivating the Ethernet OAM 1AG function
DEA CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
RMV CFMMD: SRN=0, SN=18, MDIDX=0;
RMV CFMMA: SRN=0, SN=18, MAIDX=0;
RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=11;
RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=1;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050501
Clock Synchronization on Ethernet in NodeB.
Prerequisite
l Dependencies on Hardware
Huawei clock server should support this feature.
l Dependencies on Other Features
WRFD-050402 IP Transmission Introduction on Iub Interface
l 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. 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).
Verification Procedure
1. Run the NodeB MML command DSP IPCLKLINK to query the running status of
all IP clock links.
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;
l NodeB V100R013
//Activation procedure
ADD IPCLKLNK: SRN=0, SN=12, CIP="11.11.11.11", SIP="10.10.12.12",
ICPT=HW_DEFINED;
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, IPMODE=AUTO;
//Verification procedure
DSP IPCLKLNK: SN=12;
DSP CLKSTAT:;
//Deactivation procedure
RMV IPCLKLNK: SRN=0, SN=12;
SET CLKMODE: MODE=FREE;
This section describes how to activate, verify, and deactivate the optional feature WRFD-050502
Synchronous Ethernet.
Prerequisite
l Dependencies on Hardware
Only the BSC6900 supports this feature.
Only the 3900 series base stations support this feature.
l Dependencies on Other Features
WRFD-050402 IP Transmission Introduction on Iub Interface
l License
The license controlling this feature has been activated.
l 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. Run the NodeB MML command ADD SYNCETH to add a synchronous-Ethernet
clock link.
l Verification Procedure
1. Run the NodeB MML command DSP CLKSTAT to query the status of the current
clock source.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-040202
RNC Node Redundancy.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
l The Iur, Iu-CS, Iub and Iu-PS interfaces have been configured. For details, see Configuring
the Interfaces.
l 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.
NOTE
l When the serving RNC is faulty, the maximum service capability (such as CS Erlang and PS
throughput) decreases from the combined capability of two RNCs to the capability of one RNC. As a
result, the processing specifications of the network decrease.
l To activate this feature, data configurations related to this feature are required on the RNC and the
NodeB. The CN and M2000 do not require data configurations specific to this feature. You can check
the homing state of the NodeB on the M2000.
Procedure
l Activation Procedure
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. Run the NodeB MML command ADD IUBCP to add an NCP link.
b. Run the NodeB MML command ADD IUBCP to add a CCP link.
(2) Configure information about the secondary homing RNC.
a. Run the NodeB MML command ADD IUBCP to add an NCP link.
b. Run the NodeB MML command ADD IUBCP to add a CCP link.
l Verification Procedure
1. 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. Method 2: Verifying services
(1) Check whether the heartbeat between RNC202 and RNC203 is normal, as shown
in Figure 250-3.
(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.
(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. On RNC202 and RNC203, run the BSC6900 MML command DEA URNCPOOL to
deactivate the feature.
----End
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;
//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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-040203
RRU Redundancy.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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.
2. Run the NodeB MML command ADD LOCELL to ensure the local cell uses two
power amplifiers.
l Verification Procedure
1. Run the BSC6900 MML command LST UCELLALGOSWITCH to check that Cell
Capability Auto Handle Switch is set to TX diversity capability is on to off::ON
or TX diversity capability is off to on::ON.
2. Run the NodeB MML command LST LOCELL to query whether the local cell is
configured with two power amplifiers.
l 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;
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.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
l The feature supports STTD, TSTD, and CLD1 to effectively improve the reception
performance of the UE.
l 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.
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.
3. 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.
l Verification Procedure
1. 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.
l Deactivation Procedure
This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010209
4-Antenna Receive Diversity.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
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.
l 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.
2. 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).
l Verification Procedure
1. Run the NodeB MML command LST SEC to check that the preceding parameters
are correctly configured.
l Deactivation Procedure
This feature does not need to be deactivated.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021308
Extended Cell Coverage up to 200km.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
Context
l This feature enables the operator to use a few NodeBs to extend the cell coverage.
l This feature extends the cell coverage to very remote areas with the fewest sites.
Procedure
l Activation Procedure
1. Run the BSC6900 MML command ADD UAICH. In this step, set AICH
Transmission Timing to 1.
2. 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.
3. 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.
4. Run the NodeB MML command ADD REMOTECELLGRP. In this step, set
Remote Cell Group No and Remote Cell Group Name.
In case of setting the remote cell to save boards, carry out Step 6. Otherwise, do not
carry out Step 6.
5. 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.
6. Optional: Run BSC6900 MML command MOD UPRACH, set sub channel of every
cell, select sub channel from RACH Sub Channel No..
NOTE
l Only 3 sub channels can be set for every cell, and no repeated sub channel exists. The 3 sub
channels need to be fixed as follows:
l sub-channel 0, sub-channel 1 and sub-channel 2
l 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.
l Verification Procedure
1. Run the NodeB MML command LST REMOTECELLGRP to check that the remote
cell group is configured.
2. Run the NodeB MML command LST LOCELL to check that the local cell is set to
a remote cell and that Remote Cell Mode is set to TRUE.
l Deactivation Procedure
This feature does not need to be deactivated.
----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;
//Verification procedure
LST REMOTECELLGRP: REMOTECELLGRPINDEX=1;
LST LOCELL: MODE=LOCALCELL, LOCELL=1;
This section describes how to activate, verify, and deactivate the optional feature WRFD-010206
High Speed Access.
Prerequisite
l 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.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
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.
l Verification Procedure
1. 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.
l Deactivation Procedure
1. 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;
256
Demodulation of Signals from Multiple RRUs in
Configuring Independent
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.
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).
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-011500
PDCP Header Compression (RFC2507).
Prerequisite
l Dependencies on Hardware
The UE supports this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l 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.
l Verification Procedure
1. Initiate UE tracing on the BSC6900 LMT.
2. Establish a PS service on the UE. Observe the CRLC _SETUP_REQ message in the
traced UE data. Check the bit1RfcInfo2507 IE in the following path in the message:
pdcpSetupInfo> pdcpInfo> pdcpInfoBmp> bit1RfcInfo2507.
If the value of the bit1RfcInfo2507 IE is 1, you can infer that this feature has been
activated.
If the value of the bit1RfcInfo2507 IE is 0, you can infer that this feature has not
been activated.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021200
HCS (Hierarchical Cell Structure).
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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.
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.
3. Set the HCS parameters for different types of neighboring cells as follows:
Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell and set the HCS parameters.
Run the BSC6900 MML command ADD UINTERFREQNCELL to add an inter-
frequency 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. For the cells whose HCS parameters have been set, run the BSC6900 MML command
ADD UCELLHCSHO. In this step, set SpdEstSwitch to ON.
5. Run the BSC6900 MML command SET UHCSHO to set the RNC-level HCS
parameters according to network plan.
l Verification Procedure
1. If the moving speed of a UE is higher than the fast-moving handover threshold (the
number of 1D events reported by the UE in the specified period reaches the preset
number), an inter-frequency or inter-RAT HCS handover is triggered.
2. If the moving speed of a UE is lower than the slow-moving handover threshold (the
number of 1D events reported by the UE in the specified period is smaller than the
slow-moving handover threshold), slow-moving HCS handover measurement is
triggered, and a slow-moving inter-frequency or inter-RAT HCS handover is
performed.
3. If a measurement-based inter-frequency or inter-RAT handover is triggered, check
whether compressed mode is started by using a RRC_PH_CH_RECFG message on
the Uu interface on the BSC6900 LMT. If compressed mode is started, this feature is
activated.
4. If an inter-frequency blind handover is triggered, check whether the handover is
triggered by using a RRC_PH_CH_RECFG message on the Uu interface on the
BSC6900 LMT. If the handover is triggered by using the message, this feature is
activated.
5. If an inter-RAT blind handover is triggered, check whether 3G-to-2G handovers are
performed on the Uu and Iu interfaces on the BSC6900 LMT. If 3G-to-2G handovers
are performed, this feature is activated.
l Deactivation Procedure
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH. In this step,
deselect HO_ALGO_HCS_SPEED_EST_SWITCH from the HoSwitch
parameter.
2. Run the BSC6900 MML command MOD UCELLHCS. In this step, set Use of
HCS to NOT_USED.
3. Run the BSC6900 MML command MOD UCELLHCSHO. In this step, set
SpdEstSwitch to OFF.
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020104
Intra Frequency Load Balance.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell.
2. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step,
select INTRA_FREQUENCY_LDB from the Cell LDC algorithm switch drop-
down list.
3. Run the BSC6900 MML command SET ULDCPERIOD. In this step, set Intra-
frequency LDB period timer length to an appropriate value.
4. 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
----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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020105
Potential User Control.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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. Run the BSC6900 MML command MOD UCELLALGOSWITCH to enable the
cell-oriented PUC algorithm.
2. 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.
3. Run the BSC6900 MML command ADD UCELLPUC to set the cell-oriented PUC
algorithm parameters.
l Verification Procedure
1. Configure two cells CELL_A11 and CELL_A12 as inter-frequency neighboring cells
on the NodeB.
2. Run the BSC6900 MML command MOD UCELLPUC to change the potential user
control threshold for CELL_A11.
3. Run the NodeB MML command STR DLSIM to simulate a situation where the cell
has a high load.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-070004
Load Based GSM and UMTS Handover Enhancement Based on Iur-g.
Prerequisite
l 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 License
The license controlling this feature has been activated.
l Both the 2G network and the 3G network are deployed.
l IP transmission mode is used on the Iur-g interface.
l A GSM cell and a UMTS cell are configured and the GSM cell is configured as the
neighboring cell of the UMTS cell.
l 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 non-
coverage-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 inter-
RAT 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.
l Verification Procedure
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.
(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).
l 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 Non-
coverage 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;
262
Assisted Cell Change) Procedure Optimization
Configuring NACC(Network
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.
Prerequisite
l 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 License
The license controlling this feature has been activated.
l IP transmission mode is used on the Iur-g interface.
l The MS supports NACC.
l Both the 2G network and the 3G network are deployed.
l A GSM cell and a UMTS cell are configured and the GSM cell is configured as the
neighboring cell of the UMTS cell.
l 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
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 inter-
RAT cell to support indication of the RIM procedure. In this step, set Inter-RAT
cell support RIM indicator to TRUE. If multiple neighboring cells are planned,
repeat this step to enable the inter-RAT cell to support indication of the RIM for
all the neighboring cells.
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. Trace Iur-g and Um interfaces on the LMT.
2. Use a dual-mode MS to download data in the UMTS cell and then switch the MS to
the GSM cell.
3. Check that INFO_EXCHG_INIT_REQ and INFO_EXCHG_INIT_RSP
messages are reported on the Iur-g interface. The value of informationTypeItem in
the INFO_EXCHG_INIT_REQ message is nACC-Related-Data(8) and the
INFO_EXCHG_INIT_RSP message contains nACC-Related-Data.
l Deactivation Procedure
1. Configuration on the RNC side
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-070006
GSM and UMTS Load Balancing Based on Iur-g.
Prerequisite
l 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.
l 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 Inter-
RAT Handover Based on Service.
l License
The license controlling this feature has been activated.
l 2G and 3G networks cover the same area.
l IP transmission mode is used over the Iur-g interface.
l 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.
l 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.
l A GSM cell and a UMTS cell are configured, and the GSM cell is configured as a
neighboring cell of the UMTS cell.
l 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 RNC sides are activated separately.
Context
This feature implements RRC redirection and the load-based GSM/UMTS handover through
the exchange of Huawei proprietary IE over the Iur-g interface. The Iur-g protocol stack complies
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(LOAD-
BASED), 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(Load-
based), 2G Load Adjustment Coefficient to 10.
(2) Run the BSC6900 MML command SET GCELLHOBASIC to enable inter-
RAT 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 GSM-
TargetCellInfo. 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) Use the MS to browse the Internet.
2) Initiate Uu-interface message tracing on the LMT. You can find that
the messages RRC_RB_SETUP, RRC_RB_SETUP_CMP,
RRC_MEAS_CTRL, and
RRC_CELL_CHANGE_ORDER_FROM_UTRAN are reported, and
that the value of InterRATEvent in the RRC_MEAS_CTRL message
is event3c.
3) Initiate Iu-interface signaling tracing on the LMT. You can find that
the RANAP_SRNS_CONTEXT_REQ message is sent from the CN
to the RNC and then the RANAP_SRNS_CONTEXT_RESP message
is sent from the RNC to the CN.
4) 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.
5) When the MS attempts to reselect cell3, Internet browsing is slightly
affected. After the MS reselects cell3, Internet browsing returns to
normal.
c. Verifying that CS speech services in UMTS cell1 are handed over to GSM
cell2 at the RAB connection phase
1) Use the dual-mode MS to call a fixed telephone in cell1. The call is
successfully established.
2) Initiate Uu-interface tracing on the LMT. You can find that the
messages RRC_RB_SETUP, RRC_RB_SETUP_CMP,
RRC_MEAS_CTRL, and RRC_HO_FROM_UTRAN_CMD_GSM
are reported, and that the value of InterRATEvent in the
RRC_MEAS_CTRL message is event3c.
3) 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.
4) 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.
2. 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-070007
GSM and UMTS Traffic Steering Based on Iur-g.
Prerequisite
l 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.
l 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 Inter-
RAT Handover Based on Service.
l License
The license controlling this feature has been activated.
l 2G and 3G networks cover the same area.
l IP transmission mode is used over the Iur-g interface.
l 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.
l 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.
l A GSM cell and a UMTS cell are configured, and the GSM cell is configured as a
neighboring cell of the UMTS cell.
l 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 RNC sides are activated separately.
Context
This feature supports RRC redirection and GSM/UMTS inter-RAT handover based on service.
With this feature, services are steered on the basis of the service handover indicator, hierarchical
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 inter-
RAT 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 Iu-
interface 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.
CAUTION
Ensure that the GSM cell is not in the congestion state.
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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020127
Warning of Disaster.
Prerequisite
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l 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.
l 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
Procedure
l Activation Procedure
1. For detailed operations for activating license, see 3.1 Activating the BSC6900
License.
2. (Optional) Run the BSC6900 MML command RMV UCBSADDR to remove the
CBS configuration, if the operator configured the CBS function using external CBC.
3. 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.
4. Run the BSC6900 MML command ADD URNCCBCPUID to configure the SPU
subsystem for the built-in CBC.
5. 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.
6. 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.
l 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.
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-021001
Flexible frequency bandwidth of UMTS carrier.
Prerequisite
l 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 Dependencies on Other Features
This feature does not depend on other features.
l License
The license controlling this feature has been activated.
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
setting of carrier effective bandwidth. If an RRU is not configured, run the NodeB
MML command ADD RRU to add an RRU.
2. Run the NodeB MML command SET FREQBWH to set the minimal effective
bandwidth of the RRU carrier (parameter: Frequency Min Bandwidth).
l Verification Procedure
Run the NodeB MML command LST FREQBWH to query the effective bandwidth of the
RRU carrier and check the returned message.
If... Then...
l 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;
This section describes how to activate, verify, and deactivate the optional feature WRFD-020134
Push to Talk.
Prerequisite
l Dependencies on Hardware
This feature does not depend on the hardware.
l 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 License
The license controlling this feature has been activated.
l 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.
2. 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.
Example
//Activating Push to Talk
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.
Prerequisite
l Dependencies on Hardware
The Gi interface between the RNC and the Internet is supported only by the FG2c board
and the GOUc board.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l 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.
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. Run the BSC6900 MML command ADD BRD to add an FG2c board.
2. Run the BSC6900 MML command SET ETHPORT to set the Ethernet port attributes
of the FG2c board.
3. Run the BSC6900 MML command ADD ETHREDPORT to add two Ethernet ports
as active and standby ports.
4. Run the BSC6900 MML command ADD UGIPORT to add a Gi interface.
5. Run the BSC6900 MML command ADD ETHIP to add an IP address of the Gi
interface.
6. Run the BSC6900 MML command ADD IPRT to add a route from the Gi interface
to the firewall.
7. Run the BSC6900 MML command ADD UNATRESPOOL to add a NAT resource
pool.
8. Run the BSC6900 MML command SET UNATSWITCH to enable the NAT
function.
9. 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 TAC-
level 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.
l 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.
2. Set Monitor Item to Cell User Number, and then set Monitor Period and Cell ID.
Click OK.
3. Choose Monitor > Common Monitoring. Double-click Link Performance
Monitoring. The Link Performance Monitoring dialog box is displayed.
4. Set Monitor Item to FE/GE, Subrack No. to 0, Slot No. to 14, Monitor Type to
Port, and FE/GE Port No. to 0. Click OK.
5. Power on a UE and enable the UE to camp on CELL1. Use the UE to initiate a PS
service.
6. Check the Cell User Number parameter. The number of UEs supporting RNC Offload
in the cell changes from 0 to 1.
7. The UE starts data transmission.
8. Check the FE/GE parameter. The data throughput over the FE/GE port increases.
l Deactivation Procedure
1. Run the BSC6900 MML command MOD UOFFLOAD to disable RNC Offload for
the operator.
----End
Example
//Configuring the Gi interface
ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=FG2c, SN=14, RED=YES, MPUSUBRACK=0,
MPUSLOT=0;
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0, SPEED=AUTO;
ADD ETHREDPORT: SRN=0, SN=14, PN=0;
ADD UGIPORT: SRN=0, SN=14, PN=0, ISPSSHAREPORT=NO;
ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.53.50.69",
MASK="255.255.255.240";
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;
This section describes how to activate, verify, and deactivate the optional feature MRFD-221801
Multi-mode Dynamic Power Sharing (UMTS).
Prerequisite
l Dependencies on Hardware
Only the MRFU and the RRU3908 supports GSM and UMTS Dynamic Power Sharing
at present.
l 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 License
The license controlling this feature has been activated.
l 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.
2. 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.
3. Run the NodeB MML command MOD LOCELL, set GU Power Share Flag to
TRUE(TRUE).
l Verification Procedure
1. Run the BSC6900 MML command LST BTSGUPWRSHRFP and LST
BTSRXUBP and check the returned message.
Exception result: Board Parameter Configuration Enabled and GU Dynamic
Power Sharing Switch are YES.
2. Run the NodeB MML command LST LOCELL, and check the returned message.
Exception result: GU Power Share Flag is YES.
l Deactivation Procedure
1. Run the NodeB MML command MOD LOCELL, set GU Power Share Flag to
FALSE(FALSE).
2. Run the BSC6900 MML command SET BTSGUPWRSHRFP. In this step, set
Board Parameter Configuration Enabled to NO(NO).
3. Run the BSC6900 MML command SET BTSRXUBP. In this step, set GU Dynamic
Power Sharing Switch to NO(NO).
NOTE
GSM and UMTS Dynamic Power Sharing can be deactivated by performing either of the two
steps discussed above.
----End
Example
//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;
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.
Prerequisite
l Dependencies on Hardware
The 900 MHz MRFU and RRU3908 must support this feature.
l 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 License
The license that supports this feature is activated.
l 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. 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. 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. Run the BSC6900 MML command DSP UCELL to query the DSS status of a cell.
Expected result: The value of DSS state is Actived in Normal DSS coverage.
4. Run the NodeB MML command LST LOCELL to check the value of GU Power
Share Flag.
Expected result: The value of GU Power Share Flag is TRUE.
5. Run the BSC6900 MML command DSP BTSSTAT to query the value of Dynamic
Spectrum Sharing. Expected result: The value of Dynamic Spectrum Sharing is
Yes.
l Deactivation Procedure
1. Stop Dynamic Spectrum Sharing on the M2000 by referring to the M2000 Online
Help.
2. Run the BSC6900 MML command MOD UNODEB with DSS NodeB Flag set to
FALSE.
3. Run the BSC6900 MML command SET GDSSPARA with Spectrum Sharing
Allowed set to NO(No).
4. Run the BSC6900 MML command SET GTRXDEV with Spectrum Sharing
Shutdown Allowed set to FALSE.
5. Remove the neighboring cell by referring to Reconfiguration Guide.
6. Run the BSC6900 MML command DEA UCELL to deactivate a cell.
----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;
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.
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
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
Parameter Example
BSC IP 17.0.0.17
Table 271-2 IP Planning of connecting between NodeB and RNC (IP over FE/GE)
Parameter Example
IP of BSC 17.0.0.17
Parameter Example
Table 271-3 IP planning of connection between NodeB and RNC (IP over E1/T1)
Parameter Example
Procedure
l Procedure for Activating the BTS Data
1. Run the BSC6900 MML command ADD BTSESN to add the ESN of the GBTS.
2. Run the BSC6900 MML command SET BTSIP to set the IP address of the GBTS.
3. 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.
4. 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.
2. 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.
3. 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.
4. 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. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP.
7. 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. 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.
2. 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.
3. 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).
4. 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.
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. 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.
7. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP.
8. 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,
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",
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. 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.
2. 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.
3. Run the NodeB MML command ADD IPRT to add an IP route from the NodeB to
BSC6900 in case of layer 3 networking.
Set Destination IP Address to the gateway IP address of the BSC6900.
Set Next Hop IP Address to the gateway IP address of the NodeB.
NOTE
Next Hop IP Address is the IP address of the eNodeB port connected to the NodeB.
4. Run the NodeB MML command ADD SCTPLNK to add an SCTP link.
Set Cabinet No., Subrack No., and Slot No. to the numbers of the cabinet,
subrack, and slot that house the Iub interface board.
Set Local IP Address to the device IP address in step 2.
Set Peer IP Address to the IP address of the port on the BSC6900 side.
Run the BSC6900 MML command LST SCTPSRVPORT to query the value of
Peer SCTP Port.
5. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP(CCP Port).
6. 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.
l 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.
5. Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to
the BSC6900.
6. Run the eNodeB MML command ADD RSCGRP to add a transmission resource
group.
7. 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. 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.
9. 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. Run the eNodeB MML command ADD MPGRP to add an MP group.
3. Run the eNodeB MML command ADD MPLNK to add an MP link and then add it
to the MP group.
4. Run the eNodeB MML command ADD DEVIP to add the IP address of FE interface
on eNodeB.
5. Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to
the MME.
Set Destination IP Address to the destination IP address of the route.
Set Subboard Type to E1_COVERBOARD(E1 Cover Board)
Set Route Type to IF(Exit Interface).
6. Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to
the SGW.
7. Run the eNodeB MML command ADD IPRT to add an IP route from the eNodeB to
the BSC6900.
8. Run the eNodeB MML command ADD RSCGRP to add a transmission resource
group.
9. 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.
----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
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;
This section describes how to activate, verify, and deactivate the optional feature MRFD-221504
TDM-Based Multi-mode Co-Transmission via Backplane on BS side (NodeB).
Prerequisite
l 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.
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.
Procedure
l Activating the BTS data (GTMU-based)
1. Run the BSC6900 MML command ADD BTSCONNECT to add a connection
between a GTMU port and the NodeB. Set Dest Node Type to OTHER.
2. Run the BSC6900 MML command ADD BTSTOPCONFIG to configure the TOP
switching parameters.
Set Port Subrack No. and Port Slot No. to numbers of the subrack and slot where
the BTS port connected to the NodeB interface board is located. Set TOP Board
Subrack No. and TOP Board Slot No. to numbers of the subrack and slot where
the NodeB interface board is located.
Set Port Type to TOPEXTOUTPORT.
Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
l Activating the NodeB data (GTMU-based)
1. Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link.
Set Subrack No. and Slot No. to numbers of the subrack and slot that house the
Iub interface board.
Set Subboard Type to BACK_BOARD.
Set Destination Slot No. to the number of the slot that houses the GTMU.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It,
however, does not support the configuration of the operating work mode and loopback mode, and
online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual
networking mode.
2. Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step,
set Subboard Type to BASE_BOARD.
3. Run the NodeB MML command ADD IMALNK to add an IMA link and then add it
to the MP group. In this step, set Subboard Type to BACK_BOARD or
BASE_BOARD.
4. Run the NodeB MML command ADD SAALLNK to add an SAAL link.
Set Subboard Type to BASE_BOARD.
Set Rate Unit to KBPS or CELL/S. Only one rate unit can be used. Therefore,
rate units in other configuration must be consistent.
5. Run the NodeB MML command ADD AAL2NODE to add an AAL2 node.
Set Node Type to LOCAL(LOCAL).
Set ATM Address to a valid ATM address. The recommended value is
H'3900000000000000000000000000000000000000.
6. Run the NodeB MML command ADD AAL2PATH to add an AAL2 path.
Set Node Type to LOCAL(End Node).
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. Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set
NCP/CCP Port Type to NCP(NCP Port).
8. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP(CCP Port).
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.
l Activating the BTS data (GSM-UTRP-based)
1. Run the BSC6900 MML command ADD BTSCONNECT to add a connection
between a UTRP port and the NodeB. Set Dest Node Type to OTHER.
2. Run the BSC6900 MML command ADD BTSTOPCONFIG to configure the TOP
switching parameters.
Set Port Type to TOPEXTOUTPORT.
Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
l Activating the NodeB data (GSM-UTRP-based)
1. Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link.
Set Cabinet No., Subrack No., and Slot No. to the numbers of the cabinet,
subrack, and slot that house the Iub interface board.
Set Subboard Type to BACK_BOARD.
Set Destination Slot No. to the number of the slot that houses the UTRP.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It,
however, does not support the configuration of the operating work mode and loopback mode, and
online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual
networking mode.
2. Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step,
set Subboard Type to BASE_BOARD.
3. Run the NodeB MML command ADD IMALNK to add an IMA link and then add it
to the MP group. In this step, set Subboard Type to BACK_BOARD or
BASE_BOARD.
4. Run the NodeB MML command ADD SAALLNK to add an SAAL link.
Set Subboard Type to BASE_BOARD.
Set Rate Unit to KBPS or CELL/S. Only one rate unit can be used. Therefore,
rate units in other configuration must be consistent.
5. Run the NodeB MML command ADD AAL2NODE to add an AAL2 node.
Set Node Type to LOCAL(LOCAL).
Set ATM Address to a valid ATM address. The recommended value is
H'3900000000000000000000000000000000000000.
6. Run the NodeB MML command ADD AAL2PATH to add an AAL2 path.
Set Node Type to LOCAL(End Node).
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. Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set
NCP/CCP Port Type to NCP.
8. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
NCP/CCP Port Type to CCP.
NOTE
Before a CCP link is added, the number of the CCP port must be the same as that of the CCP port
on the BSC6900 side. To query information about the CCP link on the BSC6900 side, run the
BSC6900 MML command LST UIUBCP.
----End
Example
//Activating the BTS data (GTMU-based)
//Configuring a connection between a GTMU port and the NodeB
ADD BTSCONNECT: IDTYPE=BYID, BTSID=255, INPN=1, INCN=0, INSRN=0, INSN=6,
DESTNODE=OTHER;
//Configuring the TOP switching relation between the GTMU and the WMPT:
E1 port 16 on the backplane corresponds to port 0 on the WMPT, the GTMU
provides the WMPT with a transmission path, the port type is TOPEXTINPO,
and the output port is E1 port 1 on the GTMU
ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=6,
E1T1PORTNO=16, TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7,
PORTTYPE=TOPEXTOUTPORT, ORIPORT=1,
TSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-
1&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;
This section describes how to activate, verify, and deactivate the optional feature MRFD-221601
Multi-Mode BS Common Reference Clock (NodeB).
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 License
The license controlling this feature has been activated.
l 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.
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)
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)
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.
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. 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 synchronous-
Ethernet 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... Then...
The clock conflict alarm is generated. 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;
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 License
The license controlling this feature has been activated.
l 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.
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.
NOTE
As shown in Figure 273-7, only one USCU can be configured on either the UMTS side or the LTE side.
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.
NOTE
As shown in Figure 273-8, only one USCU can be configured on either the UMTS side or the LTE side.
Figure 273-9 Common E1/T1 reference clock on the UMTS side (WMPT)
Figure 273-10 Common Ethernet 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. 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. Configuration on the eNodeB side
(1) Run the eNodeB MML command ADD SYNCETH to add a synchronous-
Ethernet clock link.
Set Subrack No. to the number of the subrack where the synchronous-
Ethernet 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... Then...
If... Then...
----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;
274
Frequency Point Separation Between GSM and
Configuring 2.0 MHz Central
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).
Prerequisite
l Dependencies on Hardware
MRFU and RRU3908 of V2 or later versions support the feature.
l 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 License
The license controlling this feature has been activated.
l 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. 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.
2. To ensure that the UMTS carrier bandwidth is 3.8 MHz and the frequency spacing
between GSM and UMTS carriers is 2.0 MHz, as set in step 1, do as follows to modify
frequency points on the GSM or UMTS side:
Modify the UMTS carrier Central Frequency Point
(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. Run the NodeB MML command LST FREQBWH to check whether the UMTS
carrier bandwidth is 3.8 MHz.
2. Check on the NodeB side whether all TRXs work properly when the frequency spacing
between GSM and UMTS carriers is 2.0 MHz.
3. Check on the BSC side whether services in all cells are normal when the frequency
spacing between GSM and UMTS carriers is 2.0 MHz.
l Deactivation Procedure
1. 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.
2. To ensure that the UMTS carrier bandwidth is the bandwidth set in step 1, do as follows
to modify frequency points on the GSM or UMTS side:
Modify the UMTS central frequency point separation
(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 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;