RAN Feature Huawei

DB-HSDPA
Contents
3.2.4 DB-HSDPA
3.2.24 Power Sharing
WCDMA RAN
DB-HSDPA Feature Parameter Description
Issue 01
Date 2014-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: http://www.huawei.com/
Email: support@huawei.com
3.2.4 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between NodeB Types
2 Overview
2.1 Background
2.2 Definition
2.2.1 Introduction
2.2.2 Basic Concepts
2.2.3 Combination of Frequency Bands
2.3 Benefits
3 Technical Description
3.1 Introduction
3.1.1 DB-HSDPA Cell Group
3.1.2 Requirements for NEs
3.1.3 Function Summary
3.2 Radio Bearer Policy
3.3 Load Control
3.3.1 Load Evaluation
3.3.2 Selection of Primary and Secondary Cells
3.3.3 Periodic DRD
3.3.4 Call Admission Control
3.3.5 Preemption and Queuing
3.3.6 Congestion Control
3.4 Scheduling
3.5 State Transition
3.6 Mobility Management
3.6.1 Measurement Control
3.6.2 DB-HSDPA Handovers
3.7 Dynamic Shutdown of Cells
4 Related Features
4.1 WRFD-150209 DB-HSDPA
4.2 WRFD-150227 DB-HSDPA+MIMO
5 Network Impact
6 Engineering Guidelines
6.1.1 When to Use DB-HSDPA
6.1.2 Required Information
6.1.3 Planning
6.1.3.1 RF Planning
6.1.3.2 Network Planning
6.1.3.3 Hardware Planning
6.1.4 Deployment
6.1.4.1 Requirements
6.1.4.2 Data Preparation
6.1.4.3 Precautions
6.1.4.4 Activation
6.1.4.4.1 Using MML Commands
6.1.4.4.2 MML Command Examples
6.1.4.4.3 Using the CME
6.1.4.5 Activation Observation
6.1.4.6 Deactivation
6.1.5 Performance Monitoring
6.1.6 Parameter Optimization
6.1.7 Troubleshooting
6.2.1 When to Use DB-HSDPA+MIMO
6.2.3 Planning
6.2.3.1 RF Planning
6.2.4 Deployment
6.2.4.3 Precautions
6.2.4.4 Activation
7 Parameters
8 Counters
9 Glossary
10 Reference Documents
1.1 Scope
This document describes the Dual-Band HSDPA (DB-HSDPA) feature, including basic
principles, feature dependencies, network impact, and engineering guidelines.
DB-HSDPA involves the following features:
WRFD-150209 DB-HSDPA
WRFD-150227 DB-HSDPA+MIMO
This document applies to the following NE types.
NE Type Model
RNC BSC6900 and BSC6910
NodeB Macro 3900 series macro base stations: BTS3900, BTS3900A,

BTS3900L, BTS3900AL, DBS3900, and BTS3900C
3800 series macro base stations: DBS3800, BTS3812E, and
BTS3812AE
Micro The micro base stations do not support this feature.
LampSite The LampSite base stations do not support this feature.
This document is intended for personnel who:

Need to understand the features described herein
Work with Huawei products
1.3 Change History
This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version
RAN16.0 01 (2014-04-30)
This issue does not include any changes.
RAN16.0 Draft A (2014-01-20)
Compared with Issue 04 (2013-12-30) of RAN15.0, Draft A (2014-01-20) of RAN16.0 includes

the following changes.
Change Type Change Description Parameter Change
Feature change Changed DB-HSDPA to an optional None

feature.
Added NodeB counters. For details,
see section 6.1.5 Performance Monitoring.
Added the impacts of the WRFD-
160103 Terminal Black List feature on
DB-HSDPA. For details, see chapter 4
Related Features.
Editorial change Before activating the DB-HSDPA feature, None

run the DEA UCELL command to deactivate
cells with MIMO Prime. For details, see 6
Engineering Guidelines.
1.4 Differences Between NodeB Types
Feature Support by Macro, Micro, and LampSite NodeBs
Feature Feature Name Supported by Supported Supported by Micro Supported

ID Controller by Macro NodeBs by
NodeBs LampSite
BSC6900 BSC6910 BTS3803E BTS3902E NodeBs
WRFD- DB-HSDPA Y Y Y N N N
150209
WRFD- DB- Y Y Y N N N
150227 HSDPA+MIMO
NOTE:
Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE is not
involved, that is, a feature does not require the support of the NE.
2 Overview
2.1 Background
In releases earlier than 3GPP Release 8, UEs could use only single-carrier HSDPA (SC-HSDPA)
to transmit data. 3GPP Release 8 and later releases introduced multi-carrier HSDPA to improve
the performance and throughput of HSDPA services. Compared with SC-HSDPA, multi-carrier
HSDPA doubles user throughput or more.
This document addresses DB-HSDPA and DB-HSDPA+MIMO technologies. In 3GPP TSs, DB-
HSDPA and DB-HSDPA+MIMO technologies evolve as follows:
In 3GPP Release 8, a single user can use two carriers in the same frequency band for
downlink data transmission.
This is known as Dual-Carrier HSDPA (DC-HSDPA). In 3GPP Release 9, a single user can
use two carriers in different frequency bands for data transmission.
This is known as Dual-Band HSDPA (DB-HSDPA). In 3GPP Release 10, DB-HSDPA
works with MIMO (DB-HSDPA+MIMO for short) to further increase user throughput.
2.2 Definition
2.2.1 Introduction
This document describes two features:

The DB-HSDPA feature enables a UE to simultaneously establish HSDPA connections in
two inter-band co-coverage cells. With this feature, the UE can use the resources of two
cells operating in different frequency bands, which increases the peak throughput.
WRFD-150227 DB-HSDPA+MIMO
This feature enables the NodeB to simultaneously send HSDPA data to a UE over two
carriers in different frequency bands by using MIMO.
In RAN15.0, the DB-HSDPA+MIMO feature supports the following configurations:
Only one carrier in a DB-HSDPA cell group is configured to support MIMO. The
theoretical peak rate of this configuration is 63 Mbit/s.
Both carriers in a DB-HSDPA cell group are configured to support MIMO. The
theoretical peak rate of this configuration is 84 Mbit/s.
2.2.2 Basic Concepts
DB-HSDPA Cell Group
The DB-HSDPA feature enables a UE to simultaneously establish HSDPA connections in two

inter-band co-coverage cells. The two cells form a DB-HSDPA cell group. As shown in Figure 2-
1, the UE sends data in only one cell in the uplink. This cell is called the primary cell. The other
cell in a DB-HSDPA cell group is called the secondary cell. In the downlink, the UE can
simultaneously receive different data on the HS-DSCHs of the two cells.
Section 6.8.4.1 "Minimum Requirements" in 3GPP TS 25.104 (V9.7.0) specifies that the Time
Alignment Error (TAE) between signals from both cells in a DB-HSDPA cell group cannot
exceed 5 chips.
Figure 2-1 DB-HSDPA cell group
DB-HSDPA User
The concept of DB-HSDPA user is specific to a service. As shown in Figure 2-1, the UE that
simultaneously establishes connections with the primary and secondary cells in a DB-HSDPA
cell group is called a DB-HSDPA user. If a UE is not using DB-HSDPA to transmit data, this UE
is called a non-DB-HSDPA user.
2.2.3 Combination of Frequency Bands
To facilitate the radio frequency implementation of UEs, section 5.2 "Frequency bands" in 3GPP
TS 25.101 (V10.0.0) sets limits on paired bands of DB-HSDPA cell groups, as described in Table
2-1.
Table 2-1 DB-HSDPA frequency bands

DB-HSDPA Combination of Uplink Frequency Band Downlink Frequency
Configuration Frequency Bands Band
1 I + VIII (2100 MHz + I or VIII I and VIII

900 MHz)
2 II + IV (1900 MHz + II or IV II and IV

AWS)
3 I + V (2100 MHz + I or V I and V

850 MHz)
4 I + XI (2100 MHz + I or XI I and XI

1500 MHz)
5 II + V (1900 MHz + II or V II and V

850 MHz)
NOTE:
The NodeB radio frequency (RF) modules must support the frequency bands of DB-HSDPA cell groups.
However, Huawei RF modules do not support Band XI currently. Therefore, the frequency band combination of
2100 MHz + 1500 MHz in this table is not supported.
The UMTS 900 MHz frequencies used by DB-HSDPA support non-standard bandwidth, for
example, 4.2 MHz or 3.8 MHz. For details about non-standard bandwidth, see GU 900 MHz Non-
standard Frequency Spacing Feature Parameter Description .
2.3 Benefits
The DB-HSDPA feature provides the following benefits for multi-band networks:
Increased single-user throughput
DB-HSDPA doubles single-user throughput for multi-band networks. Specifically, this
feature provides up to 42 Mbit/s single-user throughput in the cell center with 64QAM
enabled in the downlink. The increase in single-user throughput reduces transmission delay,
which improves user experience.
Increased cell throughput
This feature increases cell throughput by 5% to 10% for multi-band networks. The
throughput gain is inversely proportional to the number of UEs that have data to receive in
the cell.
The DB-HSDPA+MIMO feature increases the downlink single-user throughput in multi-band
networks to 42 Mbit/s without 64QAM enabled and to 84 Mbit/s with 64QAM enabled.
This chapter describes the basic principles of DB-HSDPA. Unless otherwise specified, the
description in this chapter also applies to DB-HSDPA+MIMO.
3.1 Introduction
3.1.1 DB-HSDPA Cell Group
Characteristics
The primary and secondary cells in a DB-HSDPA cell group have the following characteristics:
Selection of the primary and secondary cells
For a DB-HSDPA user, the primary and secondary cells are determined by the RNC based
on the radio bearer policy. For a DB-HSDPA cell group, different DB-HSDPA users may
use different cells as their primary cells.
Uplink channels
DB-HSDPA users establish all uplink channels only in the primary cell. The uplink
channels include the DPCCH, DPDCH, HS-DPCCH, and HSUPA-related uplink channels.
Downlink channels
DB-HSDPA users establish HSDPA-related downlink channels (HS-SCCH and HS-
PDSCH) and R99 downlink channels (DPCH or F-DPCH) in the primary cell but establish
only HSDPA-related downlink channels in the secondary cell.
When a DB-HSDPA user processes combined services, HSDPA data is transmitted in both the
primary and secondary cells, whereas R99 data is transmitted only in the primary cell.
3.1.2 Requirements for NEs
describes the requirements of DB-HSDPA/DB-HSDPA+MIMO for network elements

Table 3-1
(NEs) in the network.
Table 3-1 Requirements of DB-HSDPA/DB-HSDPA+MIMO for NEs
NE Requirement
CN The CN must support a downlink peak rate of 42 Mbit/s (DB-HSDPA with 64QAM)
or 84 Mbit/s (DB-HSDPA+MIMO with 64QAM).
RNC The RNC must support Downlink Enhanced L2.

NE Requirement
The RNC must provide radio resource management for DB-HSDPA or DB-
HSDPA+MIMO, including the radio bearer policy, load control, state transition,
and mobility management.
NodeB The NodeB must support Downlink Enhanced L2, The NodeB enables a DB-
HSDPA user to simultaneously receive data in the primary and secondary cells.
UE A UE must comply with 3GPP Release 9 or later and support DC-HSDPA, which
means the UE is of HSDPA category 21 or higher and can indicate the multiband
support capability.
3.1.3 Function Summary
Table 3-2describes the main functions of DB-HSDPA that are different from SC-HSDPA. Other
functions of DB-HSDPA are similar to those of SC-HSDPA. For details, see HSDPA Feature
Parameter Description.
Table 3-2 Function summary of DB-HSDPA/DB-HSDPA+MIMO

Function Description See Section
Radio bearer When a UE accesses the network, the RNC determines 3.2 Radio
whether the UE can use DB-HSDPA/DB-HSDPA+MIMO based Bearer Policy
on the UE capability and the service to be established.
Load control When a cell is congested, the RNC performs load reshuffling 3.3 Load
(LDR) on DB-HSDPA users. Control
Scheduling The NodeB performs joint scheduling on DB-HSDPA data in 3.4 Scheduling
each DB-HSDPA cell group.
State transition DB-HSDPA users can perform state transitions based on traffic 3.5 State
volume. Transition
Mobility DB-HSDPA users can perform handovers between DB-HSDPA 3.6 Mobility
management cells and between non-DB-HSDPA cells and DB-HSDPA cells. Management
Traffic-Based The uplink HS-DPCCH needs to transmit channel quality For details
Activation and indicator (CQI) information about the primary and secondary about how to
Deactivation of DB-HSDPA cells. activate and
the This increases the uplink load compared with SC-HSDPA. deactivate
Supplementary When the traffic volume is low, the DB-HSDPA secondary cell the
Carrier In can be deactivated to reduce the uplink load. secondary
Multi-carrier cell, see
Traffic-Based
Activation and
Deactivation of
the
Supplementary
Carrier In Multi-
carrier Feature
Function Description See Section
Parameter
Description.
Dynamic cell A necessary condition is added for shutting down a cell. 3.7 Dynamic
shutdown Shutdown of
Cells
3.2 Radio Bearer Policy
DB-HSDPA brings considerable gains when there is a large amount of data to transmit. The
radio bearer policy determines whether to configure DB-HSDPA or a combination of DB-
HSDPA and other techniques for a UE based on the service type and other factors.
When a radio bearer (RB) is being established or a UE transits from the CELL_FACH,
CELL_PCH, or URA_PCH state to the CELL_DCH state, if both the cells and the UE support
DB-HSDPA, the radio bearer policy is as follows:
If the UE is to establish a streaming service, BE service, or streaming+BE combined
services and the HS-DSCH is used in the downlink, DB-HSDPA or a combination of DB-
HSDPA and other techniques can be used.
If the UE is to establish a CS service, PS conversational service, IP Multimedia Subsystem
(IMS) signaling, or SRB signaling, the RNC does not configure DB-HSDPA or a
combination of DB-HSDPA and other techniques for the UE. This is because DB-HSDPA
or a combination of DB-HSDPA and other techniques does not bring noticeable gains for
small-volume data services.
DB-HSDPA can be combined with other techniques as follows:
DB-HSDPA+DL 64QAM
DB-HSDPA and downlink 64QAM can be used together. Downlink 64QAM can be
configured in one cell or both cells of a DB-HSDPA cell group.
With DB-HSDPA and downlink 64QAM, the single-user peak rate can reach 42 Mbit/s.
DB-HSDPA+MIMO
DB-HSDPA and MIMO can be used together. MIMO can be configured in one cell or both
cells of a DB-HSDPA cell group.
When DB-HSDPA+MIMO is enabled in a cell and the UE is capable of DB-
HSDPA+MIMO, the peak downlink rate of the UE can reach 84 Mbit/s if the Downlink
64QAM feature is also enabled.
DB-HSDPA+CPC
The Continuous Packet Connectivity (CPC) feature can be used in a DB-HSDPA cell group.
However, note the following restrictions when using the combination:
CPC DTX is applied only to the primary cell because there is no uplink control
channel in the secondary cell.
CPC HS-SCCH Less Operation is applied only to the primary cell.
The primary and secondary cells must have the same CPC DRX activation states for a
DB-HSDPA user.
DB-HSDPA+space time transmit diversity (STTD)
When a UE uses STTD together with HSDPA, the HSDPA performance deteriorates.
Therefore, the RNC will not configure STTD for a DB-HSDPA UE. It is recommended that
STTD be disabled in DB-HSDPA cells. STTD can be disabled by setting the
TxDiversityInd(BSC6900,BSC6910)parameter to FALSE. For details, see TX Diversity and RX
Diversity Feature Parameter Description.
Uplink bearer
The TCP protocol is widely used during data transmission. When a UE downloads a file,
TCP acknowledgement messages are sent in the uplink. The higher the download rate, the
broader the required uplink bandwidth. The single-user peak rate can reach 42 Mbit/s or
higher in the downlink only when HSUPA is used in the uplink.
3.3 Load Control
3.3.1 Load Evaluation
DB-HSDPA affects the downlink cell load evaluation but does not affect the uplink cell load
evaluation.
The result of cell load evaluation is used during call admission control (CAC), directed retry
decision (DRD), Potential User Control (PUC), LDR, overload control (OLC), and load
balancing (LDB).
DB-HSDPA affects the following methods for evaluating downlink cell load: downlink cell
power, equivalent number of downlink users, and number of HSDPA users.
Downlink Cell Power
For details about how to calculate downlink power in a cell, see downlink algorithm 1 in power-
based CAC of the Call Admission Control Feature Parameter Description. This section describes only the
impact of DB-HSDPA on calculating downlink cell power.
The methods for calculating the downlink cell power are the same in a DC-HSDPA cell with the
Flexible Dual Carrier HSDPA feature enabled, DB-HSDPA cell, 3C-HSDPA cell, and 4C-
HSDPA cell. As shown in Figure 3-1, the downlink power in a cell consists of R99 user power,
SC-HSDPA user power, and DC/DB/3C/4C-HSDPA user power.
The transmit power of each DC/DB/3C/4C-HSDPA user in the primary or secondary cell equals
the user's total Guaranteed Bit rate Power (GBP) in the cell group multiplied by the proportion of
the transmit power in the cell.
NOTE:
The method for calculating the downlink cell power in a DC-HSDPA cell is the same as that for calculating
the downlink cell power in a DB-HSDPA, 3C-HSDPA, or 4C-HSDPA cell only when the DC-HSDPA cell
has the Flexible Dual Carrier HSDPA feature enabled. For details about the methods for calculation the
downlink cell power in a DC-HSDPA, DB-HSDPA, or 4C-HSDPA cell, see Call Admission Control Feature
Parameter Description. Huawei 4C-HSDPA feature includes 3C-HSDPA and 4C-HSDPA scenarios.
GBP is the power required for the guaranteed bit rate (GBR) in the downlink.
Figure 3-1 Composition of downlink cell power
Equivalent Number of Downlink Users
This section describes only the impact of DB-HSDPA on calculating the equivalent number of
downlink users in a cell. For details about how to calculate the equivalent number of downlink
users in a cell, see downlink algorithm 2 in power-based CAC of the Call Admission Control Feature
For a DB-HSDPA, DC-HSDPA, or 4C-HSDPA user, its equivalent number of downlink users is
calculated only in the primary cell.
Number of HSDPA Users
One DB-HSDPA, DC-HSDPA, or 4C-HSDPA user is calculated as one HSDPA user in the
primary cell.
3.3.2 Selection of Primary and Secondary Cells
When an RB is being established or a UE transitions from the CELL_FACH, CELL_PCH, or

URA_PCH state to the CELL_DCH state, the RNC selects the primary and secondary cells for
the UE by performing a DRD if the RNC determines to configure DB-HSDPA or a combination
of DB-HSDPA and other techniques based on the radio bearer policy.
Ranking Candidate Cells
The RNC performs a non-periodic DRD based on blind handovers to select the primary cell for a
DB-HSDPA user.
This section describes only the process of selecting the primary cell. For details about non-
periodic DRD based on blind handovers, see Directed Retry Decision Feature Parameter Description.
The RNC ranks candidate cells as follows:
1. The RNC checks the setting of the HSPAPlusSatisSwitch(BSC6900,BSC6910) switch.
If this switch is turned off, candidate cells have the same HSPA+ technological
satisfaction. The RNC proceeds with 2.
If this switch is turned on, the RNC ranks candidate cells in descending order by
HSPA+ technological satisfaction.
2. For all candidate cells with the same HSPA+ technological satisfaction, the RNC checks
the setting of the ServiceDiffDrdSwitch(BSC6900,BSC6910) switch.
If this switch is turned off, the RNC does not perform DRD based on traffic steering.
The RNC proceeds with 3.
If this switch is turned on, the RNC ranks the cells by service priority.
3. For all candidate cells with the same HSPA+ technological satisfaction and service
priority, the RNC checks the setting of the LdbDRDSwitchHSDPA(BSC6900,BSC6910)
switch.
If this switch is turned off, the RNC randomly ranks the cells.
If this switch is turned on, the RNC ranks the cell in descending order by cell load.
Determining the Primary and Secondary Cells
When a cell is being set up, the NodeB reports the possible secondary cell list of the cell.
Based on the ranking of candidate cells, the RNC performs CAC as follows:
If the cell in which the admission succeeds supports DB-HSDPA, the cell is the primary cell and
the other cell is the secondary cell for the DB-HSDPA user. If the cell in which the admission
succeeds does not support DB-HSDPA, DB-HSDPA cannot be configured for the UE. When this
occurs, the RNC configures the UE with a technique supported by the cell.
3.3.3 Periodic DRD
After a user establishes a service, the RNC starts the channel retry timer whose length is
specified by the ChannelRetryTimerLen(BSC6900,BSC6910) parameter if all the following
conditions are met:
DB-HSDPA/DB-HSDPA+MIMO is not configured for the user.
The user can use DB-HSDPA or DB-HSDPA+MIMO according to the radio bearer policy.
The DB_HSDPA&DBMIMO_HSDPA switch of the RetryCapability(BSC6900,BSC6910)
parameter is turned on.
When the timer expires, the RNC attempts to configure DB-HSDPA/DB-HSDPA+MIMO for the
user.
For details about periodic DRD, see Directed Retry Decision Feature Parameter Description.
3.3.4 Call Admission Control
In RAN15.0, CAC of DB-HSDPA users is the same as that of DC-HSDPA users. The RNC
performs admission in the following sequence: NodeB credit resources, Iub transmission
resources, the number of HSPA users, and cell power.
This section describes only the impact of DB-HSDPA on CAC. For details about CAC, see Call
Admission Control Feature Parameter Description.
NodeB Credit Resource-based CAC
The RNC performs admission based on NodeB credit resources only in the primary cell of a DB-
HSDPA user. The admission decision for DB-HSDPA users is the same as that for SC-HSDPA
users.
Iub Transmission Resource-based CAC
DB-HSDPA has no impact on admission based on Iub transmission resources.

For details about call admission based on Iub transmission resources, see Transmission Resource
Management Feature Parameter Description.
CAC Based on the Number of HSDPA Users
The RNC performs admission based on the number of HSDPA users only in the primary cell of a
DB-HSDPA user. The admission decision for DB-HSDPA users is the same as that for SC-
HSDPA users.
Downlink Cell Power Resource-based CAC
Downlink power-based admission algorithms 1, 2, and 3 can be used for DB-HSDPA users in
the downlink.
Impact of DB-HSDPA on downlink power-based admission algorithms 1 and 3
For DB-HSDPA users, the RNC performs admission in the primary or secondary cell. The
admission decision conditions for DB-HSDPA users are the same as those for SC-HSDPA
users. Admission based on downlink cell power is successful if the admission in either the
primary cell or the secondary cell succeeds. For R99 and SC-HSDPA users, the admission
decision conditions for accessing a DB-HSDPA cell are the same as those for accessing an
SC-HSDPA cell.
The method for evaluating the downlink load of a DB-HSDPA cell is different from that of
an SC-HSDPA cell. For details, see 3.3.1 Load Evaluation.
Impact of DB-HSDPA on downlink power-based admission algorithm 2 (admission based
on the equivalent number of downlink users)
The RNC performs admission based on the equivalent number of users only in the primary
cell. The admission decision for DB-HSDPA users is the same as that for SC-HSDPA users.
Admission based on downlink cell power is successful if the admission in the primary cell
succeeds.
3.3.5 Preemption and Queuing
When the RNC fails to admit a DB-HSDPA user in all candidate cells, the DB-HSDPA user
performs preemption or queuing in the highest-priority candidate cell during primary cell
selection if the UE supports preemption or queuing. This increases the access success rate.
The preemption and queuing functions for DB-HSDPA users are the same as those for SC-
HSDPA users. For details about preemption and queuing, see Load Control Feature Parameter
Description.
3.3.6 Congestion Control
Congestion control is performed separately in each cell of a DB-HSDPA cell group. For details
about congestion control, see Load Control Feature Parameter Description and Overload Control Feature
DB-HSDPA affects congestion control as follows:

When the downlink load in a cell exceeds the basic congestion threshold, the RNC cannot
perform inter-frequency or inter-RAT handovers on DB-HSDPA users whose secondary
cell is this cell. If the RNC performs inter-frequency handovers on DB-HSDPA users whose
primary cell is this cell, the target cells must not be the secondary cells of these DB-HSDPA
users.
When the downlink load in a cell exceeds the overload congestion threshold, the RNC takes
LDR actions on the DB-HSDPA users whose primary cell is this cell but cannot take LDR
actions on the DB-HSDPA users whose secondary cell is this cell.
3.4 Scheduling
The NodeB transmits downlink data to each DB-HSDPA user in the primary and secondary
cells. The data comes from the same MAC-ehs queue for a DB-HSDPA user. The NodeB jointly
schedules data from the MAC-ehs queue for transmission according to the resources of the
primary and secondary cells.
The method for calculating the scheduling priority of a DB-HSDPA user in the primary and
secondary cells is basically the same as the method for calculating the scheduling priority of an
SC-HSDPA user. For details about SC-HSDPA scheduling, see HSDPA Feature Parameter Description.
This section describes only the difference between the two methods.
When calculating the scheduling priority of a DB-HSDPA user in the primary and secondary
cells, the RNC considers the CQI in each cell and the sum of the Uu interface rates. In the
proportional fair (PF) and enhanced proportional fair (EPF) scheduling algorithms, the R/r value
is a major factor affecting the scheduling priority of a UE. The R/r value is positively correlated
to the scheduling priority. The method for calculating R/r for a DB-HSDPA user is different
from that for an SC-HSDPA user:
For an SC-HSDPA user, R indicates the throughput that corresponds to the CQI of the
current cell reported by the user, and r indicates the user's throughput in the current cell.
For a DB-HSDPA user, R indicates the throughput that corresponds to the CQI of the
current cell reported by the user, and r indicates the sum of the user's throughput in the
primary and secondary cells.
3.5 State Transition
The DB-HSDPA feature supports DB-HSDPA users' state transitions between

CELL_FACH/CELL_PCH/URA_PCH and CELL_DCH in the primary cell.
State transitions of DB-HSDPA users are classified into two types:
State transitions from CELL_FACH/CELL_PCH/URA_PCH to CELL_DCH
The RNC performs DRD to select the primary and secondary cells for a DB-HSDPA user
and transitions the user to the CELL_DCH state if the following conditions are met:
The conditions for the state transition from CELL_FACH/CELL_PCH/URA_PCH to
CELL_DCH are met. For example, the RNC receives an event 4A measurement report
from the user in the CELL_FACH state, or the smart P2D conditions are met.
The RNC determines that the service of the user can be carried on DB-HSDPA
according to the radio bearer policy.
State transitions from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH
When a DB-HSDPA user in the CELL_DCH state has a small amount of data to receive,
the RNC transitions the user state to CELL_FACH and then to CELL_PCH/URA_PCH, or
the RNC transitions the user state from CELL_DCH directly to CELL_PCH/URA_PCH
using the enhanced fast dormancy function.
3.6 Mobility Management
To ensure seamless roaming of DB-HSDPA users, RAN15.0 supports handovers between the
following cells:
DB-HSDPA cells
DB-HSDPA cells and R99/SC-HSDPA/DC-HSDPA/4C-HSDPA cells
DB-HSDPA cells and inter-RAT cells
DB-HSDPA does not affect the trigger of handover measurement and the handover procedure.
However, during a handover, the RNC needs to determine whether the user can go on to be a
DB-HSDPA user after the handover if the target cell supports DB-HSDPA.
This section describes only the mobility management of DB-HSDPA users. For details about
handovers, see Handover Feature Parameter Description.
3.6.1 Measurement Control
The active sets and measurement reports of DB-HSDPA users are processed based on the
primary cell during handovers.
If the radio signal quality of the primary cell does not trigger event 2D, DB-HSDPA users
measure the signal quality of only the primary cell and intra-frequency neighboring cells. If the
radio signal quality of the primary cell triggers event 2D, DB-HSDPA users start inter-frequency
measurement.
In inter-frequency measurement control, the RNC determines whether to start the compressed
mode indicator based on the inter-band measurement capability of the user:
If the CMP_UU_ADJACENT_FREQ_CM_SWITCH switch of the
CmpSwitch(BSC6900,BSC6910) parameter is turned off, the UE uses the compressed mode
to perform inter-frequency measurement.
If the CMP_UU_ADJACENT_FREQ_CM_SWITCH switch of the
CmpSwitch(BSC6900,BSC6910) parameter is turned on and the user supports inter-band
frequency measurement without compressed mode, the processing is as follows:
When the user is using DB-HSDPA (that is, a DB-HSDPA user):
If the inter-frequency neighboring cell to be measured and the secondary cell use the
same frequency in the same frequency band, the user does not start the compressed
mode. Otherwise, the user starts the compressed mode on both the primary and
secondary cells to perform inter-frequency measurement.
When the user does not use DB-HSDPA (that is, a non-DB-HSDPA user):
If the user supports inter-band measurement without compressed mode and the
frequencies to be measured are in the frequency bands supported by the user, the user
can perform inter-frequency measurement without starting the compressed mode. In
other conditions, the user needs to start the compressed mode for inter-band
measurement.
3.6.2 DB-HSDPA Handovers
DB-HSDPA supports intra-frequency and inter-frequency handovers. This section describes the
handovers of DB-HSDPA users and non-DB-HSDPA users.
DB-HSDPA Users
For DB-HSDPA users, the RNC determines whether to trigger a handover based on the radio
signal quality in the primary cell and determines whether the handover is an intra-frequency or
inter-frequency handover based on the frequencies of the primary cell and the target cell.
When an intra-frequency or inter-frequency handover is triggered for a DB-HSDPA user:
If DB-HSDPA is enabled in the target cell, the RNC hands over the DB-HSDPA user to the
target cell and configures the cell as the primary cell. If configuring DB-HSDPA in the
target cell fails, the user falls back to SC-HSDPA in the target cell.
If DB-HSDPA is not enabled in the target cell, the user is handed over to the target cell and
falls back to SC-HSDPA.
In RAN15.0, the Iur interface does not support DB-HSDPA. If the target cell and the primary
cell before the handover belong to different RNCs, the DB-HSDPA user falls back to SC-
HSDPA and then is handed over to the target cell.
Non-DB-HSDPA Users
When a non-DB-HSDPA user (for example, an SC-HSDPA or R99 user) performs a handover,
the user retains the original configuration after the user is handed over to the target cell if the
target cell is a DB-HSDPA cell.
If the user supports DB-HSDPA and the DB_HSDPA switch of the
RetryCapability(BSC6900,BSC6910) parameter has been turned on, the RNC attempts to
configure DB-HSDPA for the user a period after the handover. The period is specified by the
ChannelRetryHoTimerLen(BSC6900,BSC6910) parameter. If configuring DB-HSDPA fails,
the RNC starts the channel retry timer. When the timer expires, the RNC attempts to configure
DB-HSDPA for the user. The ChannelRetryTimerLen(BSC6900,BSC6910) parameter specifies
the timer length.
3.7 Dynamic Shutdown of Cells
During low-traffic hours, one or more cells in the co-coverage areas can be shut down to reduce
power consumption of the base station. The following two features implement dynamic
shutdown of cells: WRFD-020117 Multi-Carrier Switch off Based on Traffic Load and WRFD-
020122 Multi-Carrier Switch off Based on QoS.
After DB-HSDPA is introduced, the following necessary condition is added for shutting down a
cell:
The number of multi-carrier HSDPA users (including DC-HSDPA, DB-HSDPA, and 4C-
HSDPA users) that use the cell as the primary cell is smaller than the value of the
McHsdpaUserNumThd(BSC6900,BSC6910) parameter.
For details about dynamic shutdown of cells, see Green BTS Feature Parameter Description.
4 Related Features
Prerequisite Features
WRFD-010610 HSDPA Introduction Package

WRFD-010685 Downlink Enhanced L2
WRFD-010629 DL 16QAM Modulation
Mutually Exclusive Features
None
Impacted Features
DB-HSDPA is affected by the following feature and function:

WRFD-160103 Terminal Black List
UEs that are blacklisted by the DB-HSDPA feature are not allowed to use DB-HSDPA.
STTD
It is recommended that STTD be disabled in DB-HSDPA cells. STTD can be disabled by
setting the TxDiversityInd(BSC6900,BSC6910) parameter to FALSE. For details, see TX
Diversity and RX Diversity Feature Parameter Description.
WRFD-010684 22 MIMO
None
Impacted Features
DB-HSDPA+MIMO is affected by the following feature:

WRFD-160103 Terminal Black List
UEs that are blacklisted by the WRFD-160103 Terminal Black List feature are not allowed
to use DB-HSDPA+MIMO.
5 Network Impact
System Capacity
DB-HSDPA increases the single-user throughput and cell throughput in multi-band networks.
Increased single-user throughput
DB-HSDPA doubles single-user throughput both in the cell center and at the cell edge.
Specifically, DB-HSDPA can provide up to 42 Mbit/s single-user throughput in the cell
center with 64QAM enabled.
DB-HSDPA also increases average single-user throughput. The throughput gain is inversely
proportional to DB-HSDPA cell loads and is directly proportional to the ratio of UEs
supporting DB-HSDPA and the amount of data for a single UE to transmit in the downlink.
Increased cell throughput
DB-HSDPA increases cell throughput by 5% to 10%. The throughput gain is related to the
number of UEs performing data transmission or the proportion of UEs supporting DB-
HSDPA in the cell. When the number of UEs performing data transmission increases or the
proportion of UEs supporting DB-HSDPA decreases in the cell, the throughput gain
decreases.
Similar to DC-HSDPA and 4C-HSDPA UEs, a DB-HSDPA UE consumes one CE more than an
SC-HSDPA UE.
Network Performance
DB-HSDPA UEs report the CQI and hybrid automatic repeat request (HARQ) ACK/NACK
information about the primary and secondary cells to the RNC in the primary cell. As a result,
the uplink load of the primary cell is increased and the uplink coverage of DB-HSDPA UEs is
reduced. In addition, DB-HSDPA UEs consume more CPU resources than SC-HSDPA UEs. The
impact of DB-HSDPA on uplink load, uplink coverage, and CPU usage can be minimized by the
Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier feature.
This feature shuts down the secondary carrier when the traffic volume is low.
DB-HSDPA improves spectral efficiency and consequently slightly improves network KPIs such
as the access success rate and call drop rate.
System Capacity
This feature improves spectral efficiency to achieve the following benefits:

Increased single-user peak rate
Compared with DB-HSDPA, DB-HSDPA+MIMO uses two antennas to produce a spatial
multiplexing gain and maximally doubles the single-user peak rate:
Without 64QAM: from 28 Mbit/s to 56 Mbit/s
With 64QAM: from 42 Mbit/s to 84 Mbit/s
Compared with single-carrier MIMO, DB-HSDPA+MIMO uses the resources of two
carriers to maximally double the single-user peak rate:
Without 64QAM: from 28 Mbit/s to 56 Mbit/s
With 64QAM: from 42 Mbit/s to 84 Mbit/s
Increased cell capacity
Compared with DB-HSDPA, DB-HSDPA+MIMO improves spectral efficiency for carriers
on two different frequency bands. According to simulation results, system throughput is
increased by about 10%-20%.
Similar to DC-HSDPA, 3C-HSDPA, and 4C-HSDPA UEs, a DB-HSDPA UE consumes one CE
more than an SC-HSDPA UE.
Network Performance
None
6.1.1 When to Use DB-HSDPA
DB-HSDPA is recommended in the following scenarios:

Operators have inter-band co-coverage cells. In addition, these inter-band co-coverage cells
are in the same sector.
In urban areas where network capacity is not limited, DB-HSDPA provides more benefits if
most services on the live network are burst services.
In suburban or rural areas where network capacity is not limited, DB-HSDPA improves user
experience. The experience improvement is especially noticeable for the cell edge users.
DB-HSDPA can also be deployed in networks with limited capacity and high downlink load.
However, DB-HSDPA does not provide noticeable gain in this scenario.
Information Used to Evaluate Feature Deployment
Before feature deployment, operators need to collect the following information:

Proportion of UEs supporting DB-HSDPA
A higher proportion of UEs supporting DB-HSDPA results in better system throughput
gains.
Cell load
DB-HSDPA can provide better throughput gains in urban areas where network capacity is
not limited.
Uplink capabilities
If DB-HSDPA UEs use DCHs in the uplink, the downlink peak rates of DB-HSDPA UEs
are restricted, resulting in decreased gains. HSUPA is recommended in the uplink for DB-
HSDPA UEs.
Bandwidth over the Iub interface
If the bandwidth over the Iub interface is restricted, DB-HSDPA cannot provide significant
gains. It is recommended that the bandwidth required over the Iub interface be planned
according to the downlink peak throughput for DB-HSDPA UEs.
Packet loss rate on the CN side
If the packet loss rate on the CN side is high, gains provided by DB-HSDPA decrease
during single-thread File Transfer Protocol (FTP) sessions. It is recommended that an
appropriate packet loss rate be used on the CN side.
Information Used to Evaluate Feature Gains
Collect the values of counters listed in Table 6-1 before and after this feature is deployed to
evaluate feature gains. Some counters listed in Table 6-1 are measured only when
HSDPA_GBP_MEAS under the Cell CAC algorithm switch parameter in the MOD
UCELLALGOSWITCH command is set to 1. These counters are listed as follows:
VS.MinTCP.HSDPA.MC(BSC6900,BSC6910)
VS.MaxTCP.HSDPA.MC(BSC6900,BSC6910)
VS.MeanTCP.HSDPA.MC(BSC6900,BSC6910)
VS.HSDPA.MC.MinRequiredPwr(BSC6900,BSC6910)
VS.HSDPA.MC.MaxRequiredPwr(BSC6900,BSC6910)
VS.HSDPA.MC.MeanRequiredPwr(BSC6900,BSC6910)
Table 6-1 RNC counters for measuring the performance of DB-HSDPA
Counter Name Function Subset Description
VS.HSDPA.RAB.DB.AttEstab(BSC6900,BSC6910) HSDPA.Cell Number of RAB

Setup Attempts
for Cell When
DB-HSDPA
Applied
VS.HSDPA.RAB.DB.SuccEstab(BSC6900,BSC6910) HSDPA.Cell Number of

Successful RAB
Setups for Cell
When DB-
HSDPA Applied
VS.HSDPA.RAB.AbnormRel.DB(BSC6900,BSC6910) HSDPA.Cell Number of

Abnormally
Released RABs
for Cell When
DB-HSDPA
Applied (RF
Exceptions
Considered)
VS.HSDPA.RAB.NormRel.DB(BSC6900,BSC6910) HSDPA.Cell Number of

Normally
Released RABs
for Cell When
DB-HSDPA
Applied
VS.HSDPA.DB.PRIM.UE.Mean.Cell(BSC6900,BSC6910) HSDPA.Cell Average

Number of DB-
HSDPA UEs
Using This Cell
as the Primary
Carrier Cell
VS.HSDPA.MC.SEC.UE.Mean.Cell(BSC6900,BSC6910) HSDPA.Cell Average

Number of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs
Using This Cell
as the
Secondary
Carrier Cell
VS.MeanTCP.HSDPA.MC(BSC6900,BSC6910) RTWPTCP.Cell Average DL

Transmit Power
of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.MaxTCP.HSDPA.MC(BSC6900,BSC6910) RTWPTCP.Cell Maximum DL

Transmit Power
of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.MinTCP.HSDPA.MC(BSC6900,BSC6910) RTWPTCP.Cell Minimum DL

Transmit Power
of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.HSDPA.MC.MeanRequiredPwr(BSC6900,BSC6910) RTWPTCP.Cell Power Required

by 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.HSDPA.MC.MaxRequiredPwr(BSC6900,BSC6910) RTWPTCP.Cell Maximum Power

Required by 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.HSDPA.MC.MinRequiredPwr(BSC6900,BSC6910) RTWPTCP.Cell Minimum Power

Required by 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
Table 6-2 NodeB counters for measuring the performance of DB-HSDPA
VS.DataOutput.DBHSDPA.Traffic HSDPA.LOCELL MAC-ehs traffic volume of

DB-HSDPA/DB-HSDPA+
MIMO users
VS.DBHSDPA.DataTtiNum.User HSDPA.LOCELL Number of TTIs during

which the queues for DB-
HSDPA/DB-HSDPA+MIMO
users have data to transmit
in the buffer
6.1.3 Planning
6.1.3.1 RF Planning
The RF modules must support the frequency bands on which cells in a DB-HSDPA group
operate.
Only two inter-band co-coverage cells of the same NodeB can form a DB-HSDPA group.
If the license for the Flexible Dual Carrier HSDPA feature is not activated, a cell can belong
to only one DB-HSDPA group. When the license is activated, a cell can belong to multiple
DB-HSDPA, 3C-HSDPA, or 4C-HSDPA groups.
The two cells are in the same downlink resource group of a NodeB.
The two cells have the same time offset (specified by the TCELL parameter).
Cells in a DB-HSDPA group must be carried on the same baseband processing board.
If the base station is a distributed base station, the cells must be processed by the same RRU
or by two cascaded RRUs.
N/A
6.1.4 Deployment
Other Features
The prerequisite features for DB-HSDPA have been activated. The prerequisite features are
as follows:
WRFD-010685 Downlink Enhanced L2
WRFD-010629 DL 16QAM Modulation
Hardware
The RF modules must support the frequency bands serving the cells in a DB-HSDPA group.
The requirements of this feature on baseband processing boards are as follows:
The DBS3800 must be configured with a BBU3806 to support DB-HSDPA. The
BBU3806 must be configured with the EBBC or EBBCd board. The BBU3806C does
not support DB-HSDPA.
The 3900 series base stations must be configured with the WBBPb3, WBBPb4,
WBBPd, WBBPf, or UBBPd board.
License
This feature is not under license control.
Other Requirements
The UE must belong to HS-DSCH category 21 or higher. The UE notifies the RNC that it
supports DB-HSDPA.
Parameter Name Parameter ID Setting Notes
Channel Configuration CfgSwitch(BSC6900,BSC6910): Set Rad

Strategy Switch: CFG_HSDPA_DB_SWITCH CFG_HSDPA_DB_SWITCH (inte
CFG_HSDPA_DB_SWITCH in the Channel
Configuration Strategy
Switch parameter to ON.
Cell Hspa Plus function HspaPlusSwitch(BSC6900,BSC6910): Set DB_HSDPA(DB- Rad

switch: DB_HSDPA(DB- DB_HSDPA HSDPA Function Switch) (inte
HSDPA Function Switch) in the Cell Hspa Plus
function switch parameter
to ON.
HSPA Technologies Retried RetryCapability(BSC6900,BSC6910): After DB-HSDPA is Rad

by UEs: DB_HSDPA DB_HSDPA enabled, if a UE supports (inte
DB-HSDPA but is not
configured with a DB-
HSDPA RB, the
DB_HSDPA switch
specifies whether the UE
periodically performs DRD
to use DB-HSDPA.
Set this switch to ON.
Inter-PLMN Multicarrier InterPlmnMultiCarrSwitch(BSC6900,BSC6910) If cells belonging to different Defa

HSDPA Switch operators are allowed to valu
form a DB-HSDPA group, valu
set this parameter to YES.
Time Offset Tcell(BSC6900,BSC6910) Set this parameter to the Rad

same value as that for the (inte
other cell in the same DB-
HSDPA group.
6.1.4.3 Precautions
For 3900 series macro base stations and micro base stations, run the DEA UCELL command to
deactivate the cells to be added to a DB-HSDPA cell group before activating DB-HSDPA.
Otherwise, online UEs in these cells experience call drops.
For the DBS3800, BTS3812A, BTS3812E, and BTS3812AE, run the DEA UCELL command
to deactivate the cells to be added to a DB-HSDPA cell group before activating DB-HSDPA.
6.1.4.4 Activation
1. Configure a DB-HSDPA group on the NodeB side.

a. Run the ADD NODEBMULTICELLGRP command to set the ID of the DB-
HSDPA group.
b. Run the ADD NODEBMULTICELLGRPITEM command to add cells to the DB-
HSDPA group.
2. Run the RNC MML command MOD UCELLSETUP to set the Time Offset parameter
for the cells in the DB-HSDPA group according to the prepared data.
3. (Optional) Run the RNC MML command SET UOPERATORSHARINGMODE to set
the Inter-PLMN Multicarrier HSDPA Switch parameter according to the prepared data.
4. Run the RNC MML command SET UCORRMALGOSWITCH to enable DB-HSDPA at
the RNC level by selecting CFG_HSDPA_DB_SWITCH under the Channel
Configuration Strategy Switch parameter.
5. Run the RNC MML command MOD UCELLALGOSWITCH to enable DB-HSDPA at
the cell level by selecting DB-HSDPA(DB-HSDPA Function Switch) under the Cell
Hspa Plus function switch parameter.
6. (Optional) Run the RNC MML command SET UFRC to select DB_HSDPA under the
HSPA Technologies Retried by UEs parameter.
NOTE:
Before enabling periodic DRD for DB-HSDPA, enable periodic DRD for other features on which this feature
depends. That is, select the DL_L2_ENHANCE check box under the HSPA Technologies Retried by UEs
parameter.

//On the NodeB side
ADD NODEBMULTICELLGRP: MULTICELLGRPID=1, MULTICELLGRPTYPE=HSDPA;
ADD NODEBMULTICELLGRPITEM: MULTICELLGRPID=1, ULOCELLID=1;
ADD NODEBMULTICELLGRPITEM: MULTICELLGRPID=1, ULOCELLID=2;
//On the RNC side

MOD UCELLSETUP: CellId=1, TCell=CHIP0, TxDiversityInd=FALSE;
MOD UCELLSETUP: CellId=2, TCell=CHIP0, TxDiversityInd=FALSE;
SET UOPERATORSHARINGMODE:InterPlmnMultiCarrSwitch=YES;
SET UCORRMALGOSWITCH: CfgSwitch= CFG_HSDPA_DB_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DB_HSDPA-1;
SET UFRC: RetryCapability=DB_HSDPA-1;
Perform the following operations to check whether DB-HSDPA is working properly:

1. Use a test UE to perform PS services in a DB-HSDPA cell, and ensure that DB-HSDPA
connections are established.
2. Check the value of the VS.HSDPA.RAB.DB.AttEstab(BSC6900,BSC6910) counter.
Expected result: If the value of the preceding counter is not zero, DB-HSDPA is working
properly.
Operators can temporarily disable DB-HSDPA by performing steps 1 and 2. When DB-HSDPA
is temporarily disabled, operators can enable it by turning on the switches in steps 1 and 2. If you
need to completely disable DB-HSDPA, perform steps 1 through 4. Perform the following
operations to deactivate DB-HSDPA:
1. Run the RNC MML command MOD UCELLALGOSWITCH to disable DB-HSDPA at
the cell level by deselecting DB-HSDPA(DB-HSDPA Function Switch) under the Cell
Hspa Plus function switch parameter.
2. Run the RNC MML command SET UCORRMALGOSWITCH to disable DB-HSDPA
at the RNC level by deselecting CFG_HSDPA_DB_SWITCH under the Channel
Configuration Strategy Switch parameter.
3. Run the NodeB MML command RMV NODEBMULTICELLGRPITEM to remove
cells from the DB-HSDPA group.
4. Run the NodeB MML command RMV NODEBMULTICELLGRP to remove the DB-
HSDPA group.
//On the RNC side
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DB_SWITCH-0;
//On the NodeB side
RMV NODEBMULTICELLGRPITEM: MULTICELLGRPBID = 1, ULOCELLID =1;
RMV NODEBMULTICELLGRPITEM: MULTICELLGRPBID = 1, ULOCELLID =2;
RMV NODEBMULTICELLGRP: MULTICELLGRPID=1;
NOTE:
When configuring the DB-HSDPA feature on the CME, perform a single configuration first, and then perform a
batch modification if required. Configure the parameters of a single object before a batch modification. Perform a
batch modification before logging out of the parameter setting interface.
1. Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in Table 6-3. For
instructions on how to perform the CME single configuration, see CME Single Configuration
Operation Guide.
2. (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
Table 6-3 Configuring parameters on the CME
SN MO NE Parameter Parameter ID Configurable
Name in CME
Batch
Modification
Center
1 UCELLALGOSWITCH RNC Cell Hspa HspaPlusSwitch(BSC6900,BSC6910) Yes

Plus function
switch
2 UCORRMALGOSWITCH RNC Channel CfgSwitch(BSC6900,BSC6910) Yes

Configuration
Strategy
Switch
3 NODEBMULTICELLGRPITEM NodeB Local Cell ID ULOCELLID Yes
4 NodeBMultiCellGrp NodeB Multiple MULTICELLGRPID Yes

Carrier Cell
Group ID
and Table 6-5 list the RNC and NodeB counters that are used to measure the performance
Table 6-4
of DB-HSDPA.
The higher the proportion of UEs supporting DB-HSDPA, the greater the average user rate is.
The average user rate is indicated by the
VS.HSDPA.MeanChThroughput(BSC6900,BSC6910) counter.
Table 6-4 RNC counters for measuring the performance of DB-HSDPA
VS.HSDPA.RAB.DB.AttEstab(BSC6900,BSC6910) HSDPA.Cell Number of RAB

Setup Attempts
for Cell When
DB-HSDPA
Applied
VS.HSDPA.RAB.DB.SuccEstab(BSC6900,BSC6910) HSDPA.Cell Number of

Successful RAB
Setups for Cell
When DB-
HSDPA Applied
VS.HSDPA.RAB.AbnormRel.DB(BSC6900,BSC6910) HSDPA.Cell Number of

Abnormally
Released RABs
for Cell When
DB-HSDPA
Applied (RF
Exceptions
Considered)
VS.HSDPA.RAB.NormRel.DB(BSC6900,BSC6910) HSDPA.Cell Number of

Normally
Released RABs
for Cell When
DB-HSDPA
Applied
VS.HSDPA.DB.PRIM.UE.Mean.Cell(BSC6900,BSC6910) HSDPA.Cell Average

Number of DB-
HSDPA UEs
Using This Cell
as the Primary
Carrier Cell
VS.HSDPA.MC.SEC.UE.Mean.Cell(BSC6900,BSC6910) HSDPA.Cell Average

Number of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs
Using This Cell
as the
Secondary
Carrier Cell
VS.MeanTCP.HSDPA.MC(BSC6900,BSC6910) RTWPTCP.Cell Average DL

Transmit Power
of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.MaxTCP.HSDPA.MC(BSC6900,BSC6910) RTWPTCP.Cell Maximum DL

Transmit Power
of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.MinTCP.HSDPA.MC(BSC6900,BSC6910) RTWPTCP.Cell Minimum DL

Transmit Power
of 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.HSDPA.MC.MeanRequiredPwr(BSC6900,BSC6910) RTWPTCP.Cell Power Required

by 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.HSDPA.MC.MaxRequiredPwr(BSC6900,BSC6910) RTWPTCP.Cell Maximum Power

Required by 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
VS.HSDPA.MC.MinRequiredPwr(BSC6900,BSC6910) RTWPTCP.Cell Minimum Power

Required by 4C-
HSDPA/DB-
HSDPA/DC-
HSDPA UEs for
Cell
Table 6-5 NodeB counters for measuring the performance of DB-HSDPA

VS.DataOutput.DBHSDPA.Traffic HSDPA.LOCELL MAC-ehs traffic volume of

DB-HSDPA/DB-HSDPA+
MIMO users
VS.DBHSDPA.DataTtiNum.User HSDPA.LOCELL Number of TTIs during

which the queues for DB-
HSDPA/DB-HSDPA+MIMO
users have data to transmit
in the buffer
None
Table 6-6 describes the alarms related to DB-HSDPA.

Table 6-6 Alarms related to DB-HSDPA
Alarm ID Alarm Name NE Feature Description
ALM-22241 UMTS Cell RNC WRFD-150209 DB- This alarm is reported when
MC-HSDPA HSDPA DB-HSDPA cell
Function establishment fails.
Fault
ALM-26811 Configured NodeB WRFD-150209 DB- This alarm is reported when

Capacity Limit HSDPA the number of configured DB-
Exceeding HSDPA cells exceeds the
Licensed number allowed by the
Limit license.
ALM-28206 Local Cell NodeB WRFD-150209 DB- This alarm is reported when
Capability HSDPA a cell that does not support
Decline WRFD-150227 DB- DB-HSDPA/DB-
HSDPA+MIMO HSDPA+MIMO is enabled
with DB-HSDPA/DB-
HSDPA+MIMO.
6.2.1 When to Use DB-HSDPA+MIMO
DB-HSDPA+MIMO is recommended for heavy-traffic areas that have DB-HSDPA enabled. For
example, densely-populated urban areas.
Compared with DB-HSDPA, DB-HSDPA+MIMO further increases single-user throughput and
system capacity.
Before feature deployment, operators need to collect the following information:

Proportion of UEs supporting DB-HSDPA+MIMO
A higher proportion of UEs supporting DB-HSDPA+MIMO results in better system
throughput gains.
Radio environment
MIMO provides better gains in areas that often experience multipath propagation and where
the signal-to-interference ratio (SIR) is high. Therefore, DB-HSDPA+MIMO is
recommended in hotspot areas where the cell radius is small.
Traffic volume
DB-HSDPA+MIMO is recommended for areas where the downlink traffic volume is high.
Uplink capabilities
If DB-HSDPA+MIMO UEs use DCHs in the uplink, the downlink peak rates of DB-
HSDPA+MIMO UEs are restricted, resulting in decreased gains. HSUPA is recommended
in the uplink for DC-HSDPA+MIMO UEs.
Bandwidth over the Iub interface
If the bandwidth over the Iub interface is restricted, DB-HSDPA+MIMO cannot provide
significant gains. It is recommended that the bandwidth required over the Iub interface be
planned as required.
Packet loss rate on the CN side
If the packet loss rate on the CN side is high, gains provided by DB-HSDPA+MIMO
decrease during single-thread FTP sessions. It is recommended that an appropriate packet
loss rate be used on the CN side.
6.2.3 Planning
6.2.3.1 RF Planning
The RF modules must support the frequency bands on which cells in a DB-HSDPA group
operate and meet the hardware configuration requirements of MIMO. For details, see 2.2.3
Combination of Frequency Bands and MIMO Feature Parameter Description.
Cells in a DB-HSDPA group must belong to the same sector of a NodeB.

N/A
6.2.4 Deployment
Other Features
The prerequisite features for DB-HSDPA+MIMO have been activated. The prerequisite
features are as follows:
WRFD-010684 22 MIMO
Hardware
The DBS3800 must be configured with a BBU3806 to support DB-HSDPA+MIMO.
The BBU3806C does not support DB-HSDPA+MIMO. In addition, the BBU3806
must be configured with the EBBC or EBBCd board.
The 3900 series base stations must be configured with the WBBPb3, WBBPb4,
WBBPd, WBBPf, or UBBPd board.
License
This feature is not under license control.
Other Requirements
The UE must support DB-HSDPA and belong to HS-DSCH category 25, 26, 27, 28,
30, 32, 34, or 36.
The cells in DB-HSDPA groups must have 2X2 MIMO enabled.
Parameter Name Parameter ID Setting Notes D
Channel Configuration Strategy CfgSwitch(BSC6900,BSC6910): Set E

Switch: CFG_HSDPA_DBMIMO_SWITCH CFG_HSDPA_DBMIMO_SWITCH d
CFG_HSDPA_DBMIMO_SWITCH in the Channel Configuration
Strategy Switch parameter to
ON.
DB-HSDPA+MIMO HSDPADBMIMO Set the DB-HSDPA+MIMO E

parameter for cells in a DB- d
HSDPA group to TRUE.
Cell Hspa Plus function switch: HspaPlusSwitch(BSC6900,BSC6910): Set DBMIMO_HSDPA(DB- E

DBMIMO_HSDPA(DB- DBMIMO_HSDPA HSDPA+MIMO Function Switch) d
HSDPA+MIMO Function Switch) in the Cell Hspa Plus function
switch parameter to ON.
HSPA Technologies Retried by RetryCapability(BSC6900,BSC6910): After DB-HSDPA+MIMO is E

UEs: DBMIMO_HSDPA DBMIMO_HSDPA enabled, if a UE supports DB- d
HSDPA+MIMO but is not assigned
a DB-HSDPA+MIMO RB, the
DBMIMO_HSDPA switch
specifies whether the UE
periodically performs DR to use
DB-HSDPA+MIMO.
Set this switch to ON.
6.2.4.3 Precautions
For 3900 series macro base stations and micro base stations, run the DEA UCELL command to
deactivate the cells to be added to a DB-HSDPA+MIMO cell group before activating DB-
HSDPA. Otherwise, online UEs in these cells experience call drops.
For the DBS3800, BTS3812A, BTS3812E, and BTS3812AE, run the DEA UCELL command
to deactivate the cells to be added to a DB-HSDPA+MIMO cell group before activating DB-
HSDPA+MIMO.
6.2.4.4 Activation
Perform the following operations to activate DB-HSDPA+MIMO:

1. Run the NodeB MML command MOD ULOCELL to set DB-HSDPA+MIMO to
TRUE(TRUE).
2. Run the RNC MML command SET UCORRMALGOSWITCH to enable DB-
HSDPA+MIMO at the RNC level by selecting CFG_HSDPA_DBMIMO_SWITCH in
the Channel Configuration Strategy Switch parameter.
3. Run the RNC MML command MOD UCELLALGOSWITCH to enable DB-
HSDPA+MIMO at the cell level by selecting DBMIMO_HSDPA(DB-HSDPA+MIMO
Function Switch) in the Cell Hspa Plus function switch parameter.
4. (Optional) Based on the prepared data, run the RNC MML command SET UFRC to select
DBMIMO_HSDPA in the HSPA Technologies Retried by UEs parameter.
NOTE:
Before enabling periodic DRD for DB-HSDPA+MIMO, enable periodic DRD for other features on which
this feature depends. That is, select the DB_HSDPA and MIMO check boxes under the HSPA Technologies
Retried by UEs parameter.

//Operations on NodeB
MOD ULOCELL: ULOCELLID=1, LOCELLTYPE=NORMAL_CELL, HSDPADBMIMO=TURE;
MOD ULOCELL: ULOCELLID=2, LOCELLTYPE=NORMAL_CELL, HSDPADBMIMO=TURE;
//Operations on RNC
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DBMIMO_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=1,HspaPlusSwitch=DBMIMO_HSDPA-1;
SET UFRC: RetryCapability=DBMIMO_HSDPA-1;
NOTE:
When configuring the DB-HSDPA+MIMO feature on the CME, perform a single configuration first, and then
perform a batch modification if required.
Configure the parameters of a single object before a batch modification. Perform a batch modification before
logging out of the parameter setting interface.

Operation Guide.
To modify objects in batches, click on the CME to start the batch modification wizard.
For instructions on how to perform a batch modification through the CME batch
modification center, press F1 on the wizard interface to obtain online help.
SN MO NE Parameter Parameter ID Configurab
Name in CME
Batch
Modificatio
Center
1 ULOCELL NodeB DB- HSDPADBMIMO Yes

HSDPA+MIMO

Configuration
Strategy
Switch

Plus function
switch
4 UFRC RNC HSPA RetryCapability(BSC6900,BSC6910) Yes

(Optional) Technologies
Retried by
UEs
(This
parameter
must be set
according to
the prepared
data.)
Perform the following operations to check whether DB-HSDPA+MIMO is working properly:

1. Start UE signaling trace on the RNC side.
2. Use a test UE to perform PS services in a DB-HSDPA+MIMO cell, and ensure that DB-
HSDPA+MIMO connections are established.
3. Check whether the RADIO BEARER SETUP message includes the "Downlink secondary
cell info FDD" and "MIMO parameters" IEs or includes the "Secondary cell MIMO
parameters" IE.
Expected result: When either condition occurs, DB-HSDPA+MIMO is working properly.
Otherwise, DB-HSDPA+MIMO is not working properly.
Perform the following operations to deactivate DB-HSDPA+MIMO:

1. Run the RNC MML command MOD UCELLALGOSWITCH to disable DB-
HSDPA+MIMO at the cell level by deselecting DBMIMO_HSDPA(DB-
HSDPA+MIMO Function Switch) in the Cell Hspa Plus function switch parameter.
2. Run the RNC MML command SET UCORRMALGOSWITCH to disable DB-
HSDPA+MIMO at the RNC level by deselecting CFG_HSDPA_DBMIMO_SWITCH in
the Channel Configuration Strategy Switch parameter.
3. Run the NodeB MML command MOD ULOCELL to set DB-HSDPA+MIMO to
FALSE(FALSE).
//On the RNC side
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DBMIMO_SWITCH-0;
//On the NodeB side
MOD ULOCELL: ULOCELLID=1, HSDPADBMIMO=FALSE;
MOD ULOCELL: ULOCELLID=2, HSDPADBMIMO=FALSE;
NOTE:
When configuring the DB-HSDPA+MIMO feature on the CME, perform a single configuration first, and then
perform a batch modification if required.
Configure the parameters of a single object before a batch modification. Perform a batch modification before
logging out of the parameter setting interface.

Operation Guide.
modification center, press F1 on the wizard interface to obtain online help.
Name in CME
Batch
Modification
Center

Plus function
switch
Name in CME
Batch
Modification
Center

Configuration
Strategy
Switch
3 ULOCELL NodeB DB- HSDPADBMIMO Yes

HSDPA+MIMO
lists the new counters that are added on the RNC side and are used to measure the
Table 6-9
performance of DB-HSDPA+MIMO.
Table 6-9 New RNC counters for measuring the performance of DB-HSDPA+MIMO
Counter Name Function Description Feature Feature Na
Subset ID
VS.HSDPA.RAB.DBMIMO.AttEstab(BSC6900,BSC6910) HSDPA.Cell Number of WRFD- DB-

RAB Setup 150227 HSDPA+MI
Attempts for
Cell When
DB-HSDPA
with MIMO
Applied
This
counter is
measured
only in the
primary cell.
VS.HSDPA.RAB.DBMIMO.SuccEstab(BSC6900,BSC6910) HSDPA.Cell Number of WRFD- DB-

Successful 150227 HSDPA+MI
RAB Setups
for Cell
When DB-
HSDPA
with MIMO
Applied
This
counter is
measured
only in the
primary cell.
Counter Name Function Description Feature Feature Na
Subset ID
VS.HSDPA.RAB.AbnormRel.DBMIMO(BSC6900,BSC6910) HSDPA.Cell Number of WRFD- DB-

Abnormal 150227 HSDPA+MI
Released
RABs for
Cell When
DB-HSDPA
with MIMO
Applied (RF
Exceptions
Considered)
This
counter is
measured
only in the
primary cell.
VS.HSDPA.RAB.NormRel.DBMIMO(BSC6900,BSC6910) HSDPA.Cell Number of WRFD- DB-

Normally 150227 HSDPA+MI
Released
RABs for
Cell When
DB-HSDPA
with MIMO
Applied
This
counter is
measured
only in the
primary cell.
The counters that are added on the NodeB side and used to measure the performance of DB-
HSDPA+MIMO are the same as those for DB-HSDPA. For details, see Table 6-5.
The higher the proportion of UEs supporting DB-HSDPA+MIMO, the greater the average user
rate is. The average user rate is indicated by the
VS.HSDPA.MeanChThroughput(BSC6900,BSC6910) counter.
None
Table 6-10 describes the alarms related to DB-HSDPA/DB-HSDPA+MIMO.

Table 6-10 Alarms related to DB-HSDPA+MIMO
Alarm ID Alarm Name NE Feature Description
ALM-28206 Local Cell NodeB WRFD-150209 DB- This alarm is reported when
Capability HSDPA a cell that does not support
Decline WRFD-150227 DB- DB-HSDPA/DB-
HSDPA+MIMO HSDPA+MIMO is enabled
with DB-HSDPA/DB-
HSDPA+MIMO.
7 Parameters
Table 7-1 Parameters

Parameter ID NE MML Command Feature Feature Name
ID
TxDiversityInd BSC69 ADD UCELLSETUP WRFD- Physical Meaning: Whether to activate the tr
00 MOD UCELLSETUP 022000 Channel amplitude and phase, to improve th
WRFD- Management GUI Value Range: TRUE, FALSE
150209 DB-HSDPA Unit: None
WRFD- 2x2 MIMO Actual Value Range: TRUE, FALSE
010684 Transmit Default Value: None
WRFD- Diversity
010203 Flexible HSPA+
WRFD- Technology
010704 Selection
WRFD- Performace
010700 Improvement of
MIMO and
HSDPA Co-
carrier
TxDiversityInd BSC69 ADD UCELLSETUP WRFD- Physical Meaning: Whether to activate the tr
10 MOD UCELLSETUP 022000 Channel amplitude and phase, to improve th
WRFD- Management GUI Value Range: TRUE, FALSE
150209 DB-HSDPA Unit: None
WRFD- 2x2 MIMO Actual Value Range: TRUE, FALSE
010684 Transmit Default Value: None
WRFD- Diversity
010203 Flexible HSPA+
WRFD- Technology
010704 Selection
ID
WRFD- Performace
010700 Improvement of
MIMO and
HSDPA Co-
carrier
HSPAPlusSatisSwit BSC69 ADD UCELLDRD WRFD- DRD Meaning: Whether the HSPA+ tech
ch 00 MOD UCELLDRD 020400 Introduction compliance is preferentially selected
Package process.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: ON
HSPAPlusSatisSwit BSC69 ADD UCELLDRD WRFD- DRD Meaning: Whether the HSPA+ tech
ch 10 MOD UCELLDRD 020400 Introduction compliance is preferentially selected
Package process.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: ON
ServiceDiffDrdSwitc BSC69 ADD UCELLDRD WRFD- Traffic Steering Meaning: Whether to activate the se
h 00 MOD UCELLDRD 020400 and Load GUI Value Range: OFF, ON
04 Sharing During Unit: None
RAB Setup
Actual Value Range: ON, OFF
Default Value: OFF
ServiceDiffDrdSwitc BSC69 ADD UCELLDRD WRFD- Traffic Steering Meaning: Whether to activate the se
h 10 MOD UCELLDRD 020400 and Load GUI Value Range: OFF, ON
04 Sharing During Unit: None
RAB Setup
Actual Value Range: ON, OFF
Default Value: OFF
LdbDRDSwitchHSD BSC69 ADD UCELLDRD WRFD- Traffic Steering Meaning: Whether to enable the po
PA 00 MOD UCELLDRD 020400 and Load power resource usage in the curren
04 Sharing During GUI Value Range: OFF, ON
WRFD- RAB Setup Unit: None
010611 HSDPA DRD Actual Value Range: ON, OFF
12
Default Value: OFF
LdbDRDSwitchHSD BSC69 ADD UCELLDRD WRFD- Traffic Steering Meaning: Whether to enable the po
PA 10 MOD UCELLDRD 020400 and Load power resource usage in the curren
04 GUI Value Range: OFF, ON
ID
WRFD- Sharing During Unit: None

010611 RAB Setup Actual Value Range: ON, OFF
12 HSDPA DRD Default Value: OFF
ChannelRetryTimer BSC69 SET UCOIFTIMER WRFD- HSUPA 2ms TTI Meaning: This parameter specifies t
Len 00 010614 performed after this timer expires.
Dynamic
03 Channel GUI Value Range: 0~180
WRFD- Configuration Unit: s
021101 Control (DCCC) Actual Value Range: 0~180
WRFD- UL 16QAM Default Value: 5
010694 DL
WRFD- 64QAM+MIMO
010693 4C-HSDPA
WRFD- SRB over
150207 HSDPA
WRFD- CPC - DTX /
010652 DRX
WRFD- CPC - HS-
010686 SCCH less
WRFD- operation
010687 2x2 MIMO
WRFD- Downlink
010684 Enhanced L2
WRFD- Downlink
010685 64QAM
WRFD- Interactive and
010683 Background
WRFD- Traffic Class on
010610 HSDPA
08 DB-HSDPA
150209 Background
010612 HSUPA
06 DC-HSUPA
WRFD- DC-HSDPA
140204 3C-HSDPA
WRFD- SRB over
010696 HSUPA
WRFD- Streaming
150250 Traffic Class on
WRFD- HSDPA
010636
ID
WRFD- Streaming
WRFD- HSUPA
010632 HSDPA DRD
WRFD-
010611
12
ChannelRetryTimer BSC69 SET UCOIFTIMER WRFD- HSUPA 2ms TTI Meaning: This parameter specifies t
Len 10 010614 performed after this timer expires.
Dynamic
03 Channel GUI Value Range: 0~180
WRFD- Configuration Unit: s
021101 Control (DCCC) Actual Value Range: 0~180
WRFD- UL 16QAM Default Value: 5
010694 DL
WRFD- 64QAM+MIMO
010693 4C-HSDPA
WRFD- SRB over
150207 HSDPA
WRFD- CPC - DTX /
010652 DRX
WRFD- CPC - HS-
010686 SCCH less
WRFD- operation
010687 2x2 MIMO
WRFD- Downlink
010684 Enhanced L2
WRFD- Downlink
010685 64QAM
010683 Background
010610 HSDPA
08 DB-HSDPA
150209 Background
010612 HSUPA
06 DC-HSUPA
WRFD- DC-HSDPA
140204 3C-HSDPA
WRFD- SRB over
010696 HSUPA
ID
WRFD- Streaming
WRFD- HSDPA
010636 Streaming
010630 HSUPA
WRFD- HSDPA DRD
010632
WRFD-
010611
12
RetryCapability BSC69 SET UFRC WRFD- HSUPA 2ms TTI Meaning: This parameter specifies
00 010614 DC- only when services running on the U
03 HSDPA+MIMO GUI Value Range: SRB_OVER_HS
WRFD- Macro-Micro DCMIMO_HSDPA, DC_HSUPA, HS
010699 DC-HSDPA Unit: None
WRFD- 4C-HSDPA Actual Value Range: SRB_OVER_H
151209 SRB over DCMIMO_HSDPA, DC_HSUPA, HS
WRFD- HSDPA Default Value:
150207 CPC - DTX / SRB_OVER_HSDPA:0,SRB_OVER
WRFD- DRX O_HSDPA:0,DC_HSUPA:0,HSDPA
010652 CPC - HS-
WRFD- SCCH less
010686 operation
WRFD- 2x2 MIMO
010687 Downlink
WRFD- Enhanced L2
010684 UL Layer 2
WRFD- Improvement
010685 Downlink
WRFD- 64QAM
010695 E-DPCCH
WRFD- Boosting
010683 UL 16QAM
WRFD- DB-
010697 HSDPA+MIMO
WRFD- DB-HSDPA
010694
3C-HSDPA
WRFD-
150227 SRB over
HSUPA
WRFD-
150209 DC-HSDPA
ID
WRFD- MC-
150250 HSDPA+MIMO
WRFD- DL
010636 64QAM+MIMO
WRFD-
010696
WRFD-
150223
WRFD-
010693
RetryCapability BSC69 SET UFRC WRFD- HSUPA 2ms TTI Meaning: This parameter specifies
10 010614 DC- only when services running on the U
03 HSDPA+MIMO GUI Value Range: SRB_OVER_HS
WRFD- Macro-Micro DCMIMO_HSDPA, DC_HSUPA, HS
WRFD- 4C-HSDPA Actual Value Range: SRB_OVER_H
151209 SRB over DCMIMO_HSDPA, DC_HSUPA, HS
WRFD- HSDPA Default Value:
150207 CPC - DTX / SRB_OVER_HSDPA:0,SRB_OVER
WRFD- DRX O_HSDPA:0,DC_HSUPA:0,HSDPA
010652 CPC - HS-
WRFD- SCCH less
010686 operation
WRFD- 2x2 MIMO
010687 Downlink
WRFD- Enhanced L2
010684 UL Layer 2
WRFD- Improvement
010685 Downlink
WRFD- 64QAM
010695 E-DPCCH
WRFD- Boosting
010683 UL 16QAM
WRFD- DB-
010697 HSDPA+MIMO
WRFD- DB-HSDPA
010694
3C-HSDPA
WRFD-
150227 SRB over
HSUPA
WRFD-
150209 DC-HSDPA
WRFD- MC-
150250 HSDPA+MIMO
ID
WRFD- DL
010636 64QAM+MIMO
WRFD-
010696
WRFD-
150223
WRFD-
010693
CmpSwitch BSC69 SET WRFD- HSDPA Mobility Meaning:
00 UCORRMALGOSWITC 010610 Management
H 1. CMP_IU_IMS_PROC_AS_NORM
06 Inter RNC Soft 2. CMP_IU_QOS_ASYMMETRY_IN
WRFD- Handover "RNC" select the bigger rate as Iu Q
020203 Intra RNC Soft 3. CMP_IU_SYSHOIN_CMP_IUUP
WRFD- Handover 4. CMP_IUR_H2D_FOR_LOWR5_N
020202 DB-HSDPA version is earlier than R6 is added t
WRFD- DB- 5. CMP_IUR_SHO_DIVCTRL_SWI
150209 HSDPA+MIMO on the basis of services. The flag of
WRFD- HCS 6. CMP_UU_ADJACENT_FREQ_C
150227 (Hierarchical frequency measurement without ac
WRFD- Cell Structure) the inter-frequency measurement. T
021200 MC- 7. CMP_UU_AMR_DRD_HHO_CO
WRFD- HSDPA+MIMO is enabled, "RNC" will execute blind
150223 DC-HSDPA 8. CMP_UU_AMR_SID_MUST_CF
WRFD- UE State in 9. CMP_UU_FDPCH_COMPAT_SW
010696 Connected depends on that indicator. In other c
WRFD- Mode (CELL- "RRC_CONNECT_SETUP_CMP",
010202 DCH, CELL- 10. CMP_UU_IGNORE_UE_RLC_C
WRFD- PCH, URA-PCH, requirement of the RAB to be setup
010612 CELL-FACH) 11. CMP_UU_INTRA_FREQ_MC_B
04 HSUPA Mobility information of the best cell is not ca
WRFD- Management 12. CMP_UU_IOS_CELL_SYNC_IN
140204 DC-HSUPA
13. CMP_UU_SERV_CELL_CHG_W
WRFD- 3C-HSDPA set and delivers reconfiguration of p
150250
transition and delivers reconfiguratio
15. CMP_UU_VOIP_UP_PROC_AS
16. CMP_F2F_RLC_ONESIDE_RE
17. CMP_D2F_RLC_ONESIDE_RE
18. CMP_RAB_5_CFG_ROHC_SW
configured with the ROHC function.
ID
23. CMP_HSUPA_MACD_FLOW_M
MAC-d flow can be multiplexed.
24. CMP_SMLC_RSLT_MODE_TY
PLMN Operator - Target MS service
25. CMP_F2P_PROCESS_OPTIMI
channel reconfiguration procedure.W
26. CMP_UU_SIB11_SIB12_WITH
cannot promptly read parameters re
UCELLMEAS command.
GUI Value Range: CMP_IU_IMS_P
CMP_UU_AMR_SID_MUST_CFG_
CMP_UU_SERV_CELL_CHG_WIT
CMP_IU_QOS_ASYMMETRY_IND
CMP_UU_SIB11_SIB12_WITH_1A
CMP_RAB_7_CFG_ROHC_SWITC
Unit: None
Actual Value Range: CMP_IU_IMS_
CMP_IUR_SHO_DIVCTRL_SWITC
CMP_UU_IGNORE_UE_RLC_CAP
CMP_SMLC_RSLT_MODE_TYPE_
Default Value:
CMP_IU_IMS_PROC_AS_NORMA
TRL_SWITCH:0,CMP_UU_ADJACE
CH:1,CMP_UU_INTRA_FREQ_MC
UU_VOIP_UP_PROC_AS_NORMA
_7_CFG_ROHC_SWITCH:0,CMP_
WITCH:0,CMP_UU_SIB11_SIB12_
CmpSwitch BSC69 SET WRFD- HSDPA Mobility Meaning:
10 UCORRMALGOSWITC 010610 Management
H 1. CMP_IU_IMS_PROC_AS_NORM
06 Inter RNC Soft 2. CMP_IU_QOS_ASYMMETRY_IN
WRFD- Handover "RNC" select the bigger rate as Iu Q
020203 Intra RNC Soft 3. CMP_IU_SYSHOIN_CMP_IUUP
WRFD- Handover 4. CMP_IUR_H2D_FOR_LOWR5_N
020202 DB-HSDPA version is earlier than R6 is added t
WRFD- DB- 5. CMP_IUR_SHO_DIVCTRL_SWI
150209 HSDPA+MIMO on the basis of services. The flag of
WRFD- HCS 6. CMP_UU_ADJACENT_FREQ_C
150227 (Hierarchical frequency measurement without ac
WRFD- Cell Structure) the inter-frequency measurement. T
021200
ID
WRFD- MC- 7. CMP_UU_AMR_DRD_HHO_CO

150223 HSDPA+MIMO is enabled, "RNC" will execute blind
WRFD- DC-HSDPA 8. CMP_UU_AMR_SID_MUST_CF
010696 UE State in 9. CMP_UU_FDPCH_COMPAT_SW
WRFD- Connected depends on that indicator. In other c
010202 Mode (CELL- "RRC_CONNECT_SETUP_CMP",
WRFD- DCH, CELL- 10. CMP_UU_IGNORE_UE_RLC_C
010612 PCH, URA-PCH, requirement of the RAB to be setup
04 CELL-FACH) 11. CMP_UU_INTRA_FREQ_MC_B
WRFD- HSUPA Mobility information of the best cell is not ca
140204 Management 12. CMP_UU_IOS_CELL_SYNC_IN
WRFD- DC-HSUPA 13. CMP_UU_SERV_CELL_CHG_W
150250 3C-HSDPA set and delivers reconfiguration of p
transition and delivers reconfiguratio
15. CMP_UU_VOIP_UP_PROC_AS
16. CMP_F2F_RLC_ONESIDE_RE
17. CMP_D2F_RLC_ONESIDE_RE
configured with the ROHC function.
23. CMP_HSUPA_MACD_FLOW_M
MAC-d flow can be multiplexed.
24. CMP_SMLC_RSLT_MODE_TY
PLMN Operator - Target MS service
25. CMP_F2P_PROCESS_OPTIMI
channel reconfiguration procedure.W
26. CMP_UU_SIB11_SIB12_WITH
cannot promptly read parameters re
UCELLMEAS command.
GUI Value Range: CMP_IU_IMS_P
CMP_UU_AMR_SID_MUST_CFG_
CMP_IU_QOS_ASYMMETRY_IND
CMP_UU_SIB11_SIB12_WITH_1A
Unit: None
Actual Value Range: CMP_IU_IMS_
CMP_IUR_SHO_DIVCTRL_SWITC
CMP_UU_IGNORE_UE_RLC_CAP
ID
CMP_SMLC_RSLT_MODE_TYPE_
Default Value:
CMP_IU_IMS_PROC_AS_NORMA
TRL_SWITCH:0,CMP_UU_ADJACE
CH:1,CMP_UU_INTRA_FREQ_MC
UU_VOIP_UP_PROC_AS_NORMA
_7_CFG_ROHC_SWITCH:0,CMP_
WITCH:0,CMP_UU_SIB11_SIB12_
ChannelRetryHoTi BSC69 SET UCOIFTIMER WRFD- HSUPA 2ms TTI Meaning:
merLen 00 010614 Dynamic This parameter specifies the value o
03 Channel When handover is performed and s
WRFD- Configuration Pingpang will happen when the reco
021101 Control (DCCC)
In order to avoid the pingpang, this
WRFD- Downlink
010685 Enhanced L2 GUI Value Range: 0~999
WRFD- SRB over Unit: s
010652 HSDPA Actual Value Range: 0~999
WRFD- CPC - DTX / Default Value: 2
010686 DRX
WRFD- CPC - HS-
010687 SCCH less
WRFD- operation
010684 2x2 MIMO
WRFD- HSUPA
010614 2ms/10ms TTI
04 Handover
WRFD- Downlink
010683 64QAM
WRFD- DB-HSDPA
150209 SRB over
WRFD- HSUPA
010636 HCS
WRFD- (Hierarchical
021200 Cell Structure)
ChannelRetryHoTi BSC69 SET UCOIFTIMER WRFD- HSUPA 2ms TTI Meaning:
merLen 10 010614 Dynamic This parameter specifies the value o
03 Channel When handover is performed and s
WRFD- Configuration Pingpang will happen when the reco
021101 Control (DCCC)
In order to avoid the pingpang, this
WRFD- Downlink
010685 Enhanced L2 GUI Value Range: 0~999
ID
WRFD- SRB over Unit: s

010652 HSDPA Actual Value Range: 0~999
WRFD- CPC - DTX / Default Value: 2
010686 DRX
WRFD- CPC - HS-
010687 SCCH less
WRFD- operation
010684 2x2 MIMO
WRFD- HSUPA
010614 2ms/10ms TTI
04 Handover
WRFD- Downlink
010683 64QAM
WRFD- DB-HSDPA
150209 SRB over
WRFD- HSUPA
010636 HCS
WRFD- (Hierarchical
021200 Cell Structure)
McHsdpaUserNum BSC69 ADD WRFD- 4C-HSDPA Meaning: Threshold for the number
Thd 00 UCELLDYNSHUTDOW 150207
N DB-HSDPA GUI Value Range: 0~15
MOD WRFD- Flexible Dual Unit: None
UCELLDYNSHUTDOW 150209 Carrier HSDPA Actual Value Range: 0~15
N WRFD- 3C-HSDPA Default Value: 2
150208 Multi-Carrier
WRFD- Switch off Based
150250 on Traffic Load
WRFD- DC-HSDPA
010696 on QoS
WRFD-
020122
McHsdpaUserNum BSC69 ADD WRFD- 4C-HSDPA Meaning: Threshold for the number
Thd 10 UCELLDYNSHUTDOW 150207 DB-HSDPA
N GUI Value Range: 0~15
MOD WRFD- Flexible Dual Unit: None
UCELLDYNSHUTDOW 150209 Carrier HSDPA Actual Value Range: 0~15
N WRFD- 3C-HSDPA Default Value: 2
150250 on Traffic Load
DC-HSDPA
ID
WRFD- Multi-Carrier
020117 Switch off Based
WRFD- on QoS
010696
WRFD-
020122
CfgSwitch BSC69 SET WRFD- DC- Meaning:
00 UCORRMALGOSWITC 010699 HSDPA+MIMO
H Channel configuration strategy switc
WRFD- HSPA+ Uplink 1. CFG_DC_MIMO_DYNAMIC_SEL
010698 11.5Mbit/s per 2. CFG_DL_BLIND_DETECTION_S
WRFD- User 3GPP 25.212 section 4.3.1.
010693 DL 3. CFG_EDPCCH_BOOSTING_SW
WRFD- 64QAM+MIMO 4. CFG_FREE_USER_SWITCH: W
010694 UL 16QAM
5. CFG_HSDPA_64QAM_SWITCH
WRFD- E-DPCCH
6. CFG_HSDPA_DCMIMO_SWITC
010697 Boosting
WRFD- DC-HSDPA 7. CFG_HSDPA_DC_SWITCH: Wh
010696 Macro-Micro 8. CFG_HSDPA_MIMO_SWITCH: W
WRFD- DC-HSDPA 9. CFG_HSDPA_MIMO_WITH_64Q
151209 3C-HSDPA 10. CFG_HSDPA_4C_MIMO_SWIT
WRFD- 3GPP R9 services.
150250 Specifications 11. CFG_HSDPA_4C_SWITCH: W
WRFD- 3.4/6.8/13.6/27.2 12. CFG_HSDPA_DBMIMO_SWITC
010101 Kbps RRC 13. CFG_HSDPA_DB_SWITCH: W
WRFD- Connection and 14. CFG_HSPA_DTX_DRX_SWITC
010510 Radio Access 15. CFG_HSPA_HSSCCH_LESS_O
WRFD- Bearer 16. CFG_HSUPA_16QAM_SWITCH
011500 Establishment
17. CFG_HSUPA_DC_SWITCH: W
WRFD- and Release
18. CFG_IMS_SUPPORT_SWITCH
010686 PDCP Header
19. CFG_LOSSLESS_DLRLC_PDU
WRFD- Compression
cause RLC PDU size change which
010687 (RFC2507)
20. CFG_LOSSLESS_RELOC_CFG
WRFD- CPC - DTX /
are met. Then, lossless relocation is
010684 DRX
21. CFG_MULTI_RAB_SWITCH: W
WRFD- CPC - HS-
010683 SCCH less 22. CFG_PDCP_IPV6_HEAD_COM
operation 23. CFG_PDCP_RFC2507_HC_SW
WRFD-
010615 2x2 MIMO 24. CFG_PDCP_RFC3095_HC_SW
02 Downlink 25. CFG_PTT_SWITCH: When this
WRFD- 64QAM 26. CFG_RAB_REL_RMV_HSPAP
010615 Combination of That is, if an HSPA+ feature is requ
03 One CS Service support the fallback are MIMO, 64Q
ID
WRFD- and Two PS 27. CFG_RCS_E_SWITCH: Indicat

010615 Services RCS-e service is disabled. When th
01 Combination of 28. CFG_FACH_AM_RLC_RETRA
WRFD- Three PS UFACHCFGPARA" command are u
010615 Services used for the AM RLC retransmission
04 Combination of 29. CFG_DCH_SRB_AM_RLC_RE
WRFD- Two PS the RNC, the transmitting side of an
150207 Services switch is turned off or UEs not in the
WRFD- Combination of GUI Value Range: CFG_DL_BLIND
150227 One CS Service CFG_LOSSLESS_DLRLC_PDUSIZ
WRFD- and Three PS CFG_PDCP_RFC3095_HC_SWITC
020605 Services CFG_EDPCCH_BOOSTING_SWIT
04 4C-HSDPA CFG_HSDPA_4C_SWITCH, CFG_
WRFD- DB- Unit: None
150223 HSDPA+MIMO Actual Value Range:
WRFD- Lossless SRNS CFG_DC_MIMO_DYNAMIC_SELE
150209 Relocation CFG_HSDPA_DC_SWITCH, CFG_
WRFD- MC- CFG_HSPA_DTX_DRX_SWITCH,
010615 HSDPA+MIMO CFG_LOSSLESS_RELOC_CFG_S
WRFD- DB-HSDPA CFG_RAB_REL_RMV_HSPAPLUS
010617 Multiple RAB CFG_RCS_E_SWITCH, CFG_FAC
WRFD- Package(PS Default Value:
020134 RAB >= 2) CFG_DC_MIMO_DYNAMIC_SELE
VoIP over HSDPA_DC_SWITCH:0,CFG_HSD
HSPA/HSPA+ G_HSPA_DTX_DRX_SWITCH:0,C
SLESS_RELOC_CFG_SWITCH:0,C
Push to Talk SPAPLUS_SWITCH:0,CFG_RCS_
CfgSwitch BSC69 SET WRFD- DC- Meaning:
10 UCORRMALGOSWITC 010699 HSDPA+MIMO
H Channel configuration strategy switc
WRFD- HSPA+ Uplink 1. CFG_DC_MIMO_DYNAMIC_SEL
010698 11.5Mbit/s per 2. CFG_DL_BLIND_DETECTION_S
WRFD- User 3GPP 25.212 section 4.3.1.
010693 DL 3. CFG_EDPCCH_BOOSTING_SW
WRFD- 64QAM+MIMO 4. CFG_FREE_USER_SWITCH: W
010694 UL 16QAM
5. CFG_HSDPA_64QAM_SWITCH
WRFD- E-DPCCH
010697 Boosting 6. CFG_HSDPA_DCMIMO_SWITC
WRFD- DC-HSDPA 7. CFG_HSDPA_DC_SWITCH: Wh
010696 Macro-Micro 8. CFG_HSDPA_MIMO_SWITCH: W
WRFD- DC-HSDPA 9. CFG_HSDPA_MIMO_WITH_64Q
151209 3C-HSDPA 10. CFG_HSDPA_4C_MIMO_SWIT
WRFD- 3GPP R9 services.
150250 Specifications 11. CFG_HSDPA_4C_SWITCH: W
ID
WRFD- 3.4/6.8/13.6/27.2 12. CFG_HSDPA_DBMIMO_SWITC

010101 Kbps RRC 13. CFG_HSDPA_DB_SWITCH: W
WRFD- Connection and 14. CFG_HSPA_DTX_DRX_SWITC
010510 Radio Access
Bearer 15. CFG_HSPA_HSSCCH_LESS_O
WRFD- 16. CFG_HSUPA_16QAM_SWITCH
011500 Establishment
and Release 17. CFG_HSUPA_DC_SWITCH: W
WRFD-
010686 PDCP Header 18. CFG_IMS_SUPPORT_SWITCH
Compression 19. CFG_LOSSLESS_DLRLC_PDU
WRFD-
(RFC2507) cause RLC PDU size change which
010687
CPC - DTX / 20. CFG_LOSSLESS_RELOC_CFG
WRFD- DRX
010684 are met. Then, lossless relocation is
CPC - HS- 21. CFG_MULTI_RAB_SWITCH: W
WRFD- SCCH less
010683 22. CFG_PDCP_IPV6_HEAD_COM
operation
WRFD- 23. CFG_PDCP_RFC2507_HC_SW
2x2 MIMO
010615 24. CFG_PDCP_RFC3095_HC_SW
02 Downlink
25. CFG_PTT_SWITCH: When this
64QAM
WRFD- 26. CFG_RAB_REL_RMV_HSPAP
010615 Combination of
That is, if an HSPA+ feature is requ
03 One CS Service
support the fallback are MIMO, 64Q
and Two PS
WRFD- 27. CFG_RCS_E_SWITCH: Indicat
Services
010615 RCS-e service is disabled. When th
01 Combination of
Three PS 28. CFG_FACH_AM_RLC_RETRA
WRFD- Services UFACHCFGPARA" command are u
010615 used for the AM RLC retransmission
04 Combination of
Two PS 29. CFG_DCH_SRB_AM_RLC_RE
WRFD- Services the RNC, the transmitting side of an
150207 switch is turned off or UEs not in the
Combination of
WRFD- One CS Service GUI Value Range: CFG_DL_BLIND
150227 and Three PS CFG_LOSSLESS_DLRLC_PDUSIZ
WRFD- Services CFG_PDCP_RFC3095_HC_SWITC
020605 CFG_EDPCCH_BOOSTING_SWIT
4C-HSDPA
04 CFG_HSDPA_4C_SWITCH, CFG_
DB-
WRFD- Unit: None
HSDPA+MIMO
150223 Actual Value Range:
Lossless SRNS
WRFD- CFG_DC_MIMO_DYNAMIC_SELE
Relocation
150209 CFG_HSDPA_DC_SWITCH, CFG_
MC-
WRFD- CFG_HSPA_DTX_DRX_SWITCH,
HSDPA+MIMO
010615 CFG_LOSSLESS_RELOC_CFG_S
DB-HSDPA CFG_RAB_REL_RMV_HSPAPLUS
WRFD-
010617 Multiple RAB CFG_RCS_E_SWITCH, CFG_FAC
Package(PS
WRFD- Default Value:
RAB >= 2)
020134 CFG_DC_MIMO_DYNAMIC_SELE
HSDPA_DC_SWITCH:0,CFG_HSD
ID
VoIP over G_HSPA_DTX_DRX_SWITCH:0,C

HSPA/HSPA+ SLESS_RELOC_CFG_SWITCH:0,C
Push to Talk SPAPLUS_SWITCH:0,CFG_RCS_
HspaPlusSwitch BSC69 ADD WRFD- DC- Meaning:

00 UCELLALGOSWITCH 010699 HSDPA+MIMO This parameter is used to select a f
MOD
UCELLALGOSWITCH WRFD- HSPA+ Uplink such as license and the physical ca
010698 11.5Mbit/s per establishment of the E-FACH and th
WRFD- User 1. 64QAM: When the switch is on, 6
010401 System 2. MIMO: When the switch is on, MI
WRFD- Information 3. E_FACH: When the switch is on,
010504 Broadcasting
4. DTX_DRX: When the switch is on
WRFD- Background
QoS Class 5. HS_SCCH_LESS_OPERATION:
010693
DL 6. DL_L2ENHANCED: When the sw
WRFD-
010695 64QAM+MIMO 7. 64QAM_MIMO: When the switch
UL Layer 2 8. UL_16QAM: When the switch is o
WRFD-
010694 Improvement 9. DC_HSDPA: When the switch is
WRFD- UL 16QAM 10. UL_L2ENHANCED: When the s
010697 E-DPCCH 11. EDPCCH_BOOSTING: When th
WRFD- Boosting 12. DCMIMO_HSDPA: When this s
010696 DC-HSDPA 13. E_DRX: When the switch is on,
WRFD- Conversational 14. DC_HSUPA: When this switch i
010501 QoS Class 15. HSDPA_4C_MIMO: Whether th
WRFD- Combination of 16. HSDPA_4C: Whether the 3C-H
010615 Two PS
17. DBMIMO_HSDPA: Whether the
01 Services
18. DB_HSDPA: Whether the DB-H
WRFD- 3C-HSDPA
150250 GUI Value Range: 64QAM(Cell 64Q
Interactive and
OPERATION Function Switch), DL_
WRFD- Background
UL_L2ENHANCED(Cell UL L2ENH
Function Switch), DC_HSUPA(Cell
08 HSDPA
Function Switch)
Unit: None
010612 Background
06 Traffic Class on Actual Value Range: 64QAM, MIMO
HSUPA HSDPA_4C_MIMO, HSDPA_4C, D
WRFD-
140204 DC-HSUPA Default Value:
64QAM:0,MIMO:0,E_FACH:0,DTX_
WRFD- Combination of
4C_MIMO:0,HSDPA_4C:0,DBMIMO
010609 Two CS
01 Services (Except
WRFD- for Two AMR
010609 Speech
03 Services)
ID
010609 Two CS
02 Services and
WRFD- One PS Service
010702 (Except for Two
WRFD- AMR Speech
010701 Services)
010609 One CS Service
and One PS
WRFD- Service
010510
Enhanced DRX
WRFD-
010688 Uplink
Enhanced
WRFD-
CELL_FACH
010686
Multiple RAB
WRFD- Introduction
010687 Package (PS
WRFD- RAB < 2)
010684 3.4/6.8/13.6/27.2
WRFD- Kbps RRC
010685 Connection and
WRFD- Radio Access
010683 Bearer
WRFD- Establishment
021000 and Release
WRFD- Downlink
151209 Enhanced
WRFD- CELL_FACH
010503 CPC - DTX /
WRFD- DRX
010615 CPC - HS-
02 SCCH less
WRFD- operation
010615 2x2 MIMO
03 Downlink
WRFD- Enhanced L2
010502 Downlink
WRFD- 64QAM
010615 Transport
04 Channel
WRFD- Management
010615 Macro-Micro
05 DC-HSDPA
ID
WRFD- Interactive QoS

022000 Class
WRFD- and Two PS
150227 Services
150208 Three PS
WRFD- Services
150223 Streaming QoS
WRFD- Class
WRFD- One CS Service
150209 and Three PS
Services
WRFD-
Four PS
WRFD- Services
010632
Physical
WRFD- Channel
010630 Management
4C-HSDPA
DB-
HSDPA+MIMO
Flexible Dual
Carrier HSDPA
MC-
HSDPA+MIMO
Logical Channel
Management
DB-HSDPA
Multiple RAB
Package(PS
RAB >= 2)
Streaming
Traffic Class on
HSUPA
Streaming
Traffic Class on
HSDPA
HspaPlusSwitch BSC69 ADD WRFD- DC- Meaning:
10 UCELLALGOSWITCH 010699 HSDPA+MIMO
MOD
UCELLALGOSWITCH
ID
WRFD- HSPA+ Uplink This parameter is used to select a f

010698 11.5Mbit/s per such as license and the physical ca
WRFD- User establishment of the E-FACH and th
010401 System 1. 64QAM: When the switch is on, 6
WRFD- Information 2. MIMO: When the switch is on, MI
010504 Broadcasting 3. E_FACH: When the switch is on,
WRFD- Background 4. DTX_DRX: When the switch is on
010693 QoS Class
5. HS_SCCH_LESS_OPERATION:
WRFD- DL
6. DL_L2ENHANCED: When the sw
010695 64QAM+MIMO
UL Layer 2 7. 64QAM_MIMO: When the switch
WRFD-
010694 Improvement 8. UL_16QAM: When the switch is o
WRFD- UL 16QAM 9. DC_HSDPA: When the switch is
010697 E-DPCCH 10. UL_L2ENHANCED: When the s
WRFD- Boosting 11. EDPCCH_BOOSTING: When th
010696 DC-HSDPA 12. DCMIMO_HSDPA: When this s
WRFD- Conversational 13. E_DRX: When the switch is on,
010501 QoS Class 14. DC_HSUPA: When this switch i
WRFD- Combination of 15. HSDPA_4C_MIMO: Whether th
010615 Two PS 16. HSDPA_4C: Whether the 3C-H
01 Services
17. DBMIMO_HSDPA: Whether the
WRFD- 3C-HSDPA
18. DB_HSDPA: Whether the DB-H
150250 Interactive and
GUI Value Range: 64QAM(Cell 64Q
WRFD- Background
OPERATION Function Switch), DL_
UL_L2ENHANCED(Cell UL L2ENH
08 HSDPA
Function Switch), DC_HSUPA(Cell
WRFD- Interactive and Function Switch)
010612 Background
Unit: None
06 Traffic Class on
HSUPA Actual Value Range: 64QAM, MIMO
WRFD-
HSDPA_4C_MIMO, HSDPA_4C, D
140204 DC-HSUPA
Default Value:
64QAM:0,MIMO:0,E_FACH:0,DTX_
010609 Two CS
4C_MIMO:0,HSDPA_4C:0,DBMIMO
01 Services (Except
WRFD- for Two AMR
010609 Speech
03 Services)
010609 Two CS
02 Services and
WRFD- One PS Service
010702 (Except for Two
AMR Speech
WRFD- Services)
010701
ID
WRFD- and One PS
010510 Service
WRFD- Enhanced DRX
010688 Uplink
WRFD- Enhanced
010686 CELL_FACH
WRFD- Multiple RAB
010687 Introduction
WRFD- Package (PS
010684 RAB < 2)
WRFD- 3.4/6.8/13.6/27.2
010685 Kbps RRC
Connection and
WRFD- Radio Access
010683 Bearer
WRFD- Establishment
021000 and Release
WRFD- Downlink
151209 Enhanced
WRFD- CELL_FACH
010503 CPC - DTX /
WRFD- DRX
010615 CPC - HS-
02 SCCH less
WRFD- operation
010615 2x2 MIMO
03 Downlink
WRFD- Enhanced L2
010502 Downlink
WRFD- 64QAM
010615 Transport
04 Channel
WRFD- Management
010615 Macro-Micro
05
DC-HSDPA
WRFD- Interactive QoS
022000 Class
WRFD- and Two PS
150227 Services
ID
150208 Three PS
WRFD- Services
150223 Streaming QoS
WRFD- Class
WRFD- One CS Service
150209 and Three PS
WRFD- Services
WRFD- Four PS
010632 Services
WRFD- Physical
010630 Channel
Management
4C-HSDPA
DB-
HSDPA+MIMO
Flexible Dual
Carrier HSDPA
MC-
HSDPA+MIMO
Logical Channel
Management
DB-HSDPA
Multiple RAB
Package(PS
RAB >= 2)
Streaming
Traffic Class on
HSUPA
Streaming
Traffic Class on
HSDPA
InterPlmnMultiCarr BSC69 SET WRFD- DB-HSDPA Meaning: Whether to allow multi-ca
Switch 00 UOPERATORSHARIN 150209 switch is set to OFF, multi-carrier H
GMODE 3C-HSDPA
WRFD- 4C-HSDPA GUI Value Range: NO(NO), YES(Y
WRFD- Actual Value Range: NO, YES
150207 Default Value: YES(YES)
WRFD-
010696
ID
InterPlmnMultiCarr BSC69 SET WRFD- DB-HSDPA Meaning: Whether to allow multi-ca

Switch 10 UOPERATORSHARIN 150209 switch is set to OFF, multi-carrier H
GMODE 3C-HSDPA
WRFD- 4C-HSDPA GUI Value Range: NO(NO), YES(Y
WRFD- Actual Value Range: NO, YES
150207 Default Value: YES(YES)
WRFD-
010696
TCell BSC69 ADD UCELLSETUP WRFD- DC- Meaning: Difference between the S
00 MOD UCELLSETUP 010699 HSDPA+MIMO of DC carrier group cells or MC carr
WRFD- Macro-Micro GUI Value Range: CHIP0, CHIP256
151209 DC-HSDPA Unit: chip
WRFD- Physical Actual Value Range: CHIP0, CHIP2
022000 Channel Default Value: None
WRFD- Management
150207 4C-HSDPA
WRFD- DB-HSDPA
150209 Flexible Dual
WRFD- Carrier HSDPA
150208 3C-HSDPA
WRFD- MC-
150250 HSDPA+MIMO
WRFD- DC-HSDPA
150223 DB-
WRFD- HSDPA+MIMO
010696 Improved
WRFD- Downlink
150227 Coverage
WRFD- Extended Cell
021309 Coverage up to
WRFD- 200km
021308
TCell BSC69 ADD UCELLSETUP WRFD- DC- Meaning: Difference between the S
10 MOD UCELLSETUP 010699 HSDPA+MIMO of DC carrier group cells or MC carr
WRFD- Macro-Micro GUI Value Range: CHIP0, CHIP256
151209 DC-HSDPA Unit: chip
WRFD- Physical Actual Value Range: CHIP0, CHIP2
022000 Channel Default Value: None
WRFD- Management
150207 4C-HSDPA
WRFD- DB-HSDPA
150209
ID
WRFD- Flexible Dual

150208 Carrier HSDPA
WRFD- 3C-HSDPA
150250 MC-
WRFD- HSDPA+MIMO
150223 DC-HSDPA
WRFD- DB-
010696 HSDPA+MIMO
WRFD- Improved
150227 Downlink
WRFD- Coverage
021309 Extended Cell
WRFD- Coverage up to
021308 200km
MULTICELLGRPID BTS39 ADD None None Meaning: Uniquely identifies a multi
00, NODEBMULTICELLGR
P GUI Value Range: 0~95
BTS39 Unit: None
ADD
00 NODEBMULTICELLGR
WCDM Actual Value Range: 0~95
PITEM
A LST
Default Value: None
NODEBMULTICELLGR
P
LST
NODEBMULTICELLGR
PITEM
RMV
NODEBMULTICELLGR
P
RMV
NODEBMULTICELLGR
PITEM
MULTICELLGRPT BTS39 ADD WRFD- DC-HSDPA Meaning: Specifies the type of a mu

YPE 00, NODEBMULTICELLGR 010696
P DC-HSUPA GUI Value Range: HSDPA(HSDPA
BTS39 WRFD- DB-HSDPA Unit: None
LST
00 NODEBMULTICELLGR 140204 4C-HSDPA Actual Value Range: HSDPA, HSUP
WCDM P WRFD-
A 3C-HSDPA Default Value: HSDPA(HSDPA)
150209
Flexible Dual
WRFD- Carrier HSDPA
150207
MC-
WRFD- HSDPA+MIMO
150250
DB-
WRFD- HSDPA+MIMO
150208
DC-
HSDPA+MIMO
ID
WRFD-
150223
WRFD-
150227
WRFD-
010699
HSDPADBMIMO BTS39 ADD ULOCELL WRFD- DB- Meaning: Indicates whether the DB
00, MOD ULOCELL 150227 HSDPA+MIMO GUI Value Range: FALSE(FALSE),
BTS39 LST ULOCELL Unit: None
00
WCDM Actual Value Range: FALSE, TRUE
A Default Value: FALSE(FALSE)
8 Counters
Table 8-1 Counters

Counter Counter Name Counter NE Feature Feature Name
ID Description ID
50332168 VS.DataOutput.DBHSDPA.Traffic MAC-ehs traffic NodeB Multi- DB-HSDPA

volume of DB- mode:
HSDPA/DB- None
HSDPA+MIMO GSM:
users None
UMTS:
WRFD-
150209
LTE:
None
50332173 VS.DBHSDPA.DataTtiNum.User Total number of NodeB Multi- DB-HSDPA

user-level TTIs mode:
within which None
there is data to GSM:
transmit in DB- None
HSDPA/DB- UMTS:
HSDPA+MIMO WRFD-
user queue 150209
buffers
ID Description ID
LTE:
None
50341702 VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio The Ratio Of Dc NodeB Multi- DB-HSDPA

Deact mode: Traffic-Based
None Activation and
GSM: Deactivation of
None the
UMTS: Supplementary
WRFD- Carrier In
150209 Multi-carrier
WRFD- DC-
010713 HSDPA+MIMO
WRFD-
010699
LTE:
None
73425890 VS.HSDPA.MC.SEC.UE.Mean.Cell Average Number BSC6900 WRFD- 3C-HSDPA

of 4C- 150250 4C-HSDPA
HSDPA/DB- WRFD- DB-HSDPA
HSDPA/DC- 150207 DC-HSDPA
HSDPA UEs WRFD- Flexible Dual
Using This Cell 150209 Carrier
as the
Secondary WRFD- HSDPA
Carrier Cell 010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425890 VS.HSDPA.MC.SEC.UE.Mean.Cell Average Number BSC6910 WRFD- 3C-HSDPA

of 4C- 150250 4C-HSDPA
HSDPA UEs WRFD- Flexible Dual
Using This Cell 150209 Carrier
as the
Secondary WRFD- HSDPA
Carrier Cell 010696 DC-
HSDPA+MIMO
ID Description ID
WRFD- DB-
150208 HSDPA+MIMO
WRFD- MC-
010699 HSDPA+MIMO
WRFD-
150227
WRFD-
150223
73425893 VS.HSDPA.DB.PRIM.UE.Mean.Cell Average Number BSC6900 WRFD- DB-HSDPA

of DB-HSDPA 150209 DB-
UEs Using This WRFD- HSDPA+MIMO
Cell as the 150227
Primary Carrier
Cell
73425893 VS.HSDPA.DB.PRIM.UE.Mean.Cell Average Number BSC6910 WRFD- DB-HSDPA

of DB-HSDPA 150209 DB-
UEs Using This WRFD- HSDPA+MIMO
Cell as the 150227
Primary Carrier
Cell
73425896 VS.HSDPA.MC.MeanRequiredPwr Power Required BSC6900 WRFD- 3C-HSDPA

by 4C- 150250 4C-HSDPA
HSDPA UEs for WRFD- Flexible Dual
Cell 150209 Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425896 VS.HSDPA.MC.MeanRequiredPwr Power Required BSC6910 WRFD- 3C-HSDPA

by 4C- 150250 4C-HSDPA
HSDPA UEs for
Cell
ID Description ID
WRFD- Flexible Dual

150209 Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425901 VS.HSDPA.MC.MaxRequiredPwr Maximum Power BSC6900 WRFD- 3C-HSDPA

Required by 4C- 150250 4C-HSDPA
Cell 150209 Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425901 VS.HSDPA.MC.MaxRequiredPwr Maximum Power BSC6910 WRFD- 3C-HSDPA

Cell 150209 Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
ID Description ID
WRFD-
150223
73425903 VS.HSDPA.MC.MinRequiredPwr Minimum Power BSC6900 WRFD- 3C-HSDPA

Cell 150209 Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425903 VS.HSDPA.MC.MinRequiredPwr Minimum Power BSC6910 WRFD- 3C-HSDPA

Cell 150209 Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425905 VS.MeanTCP.HSDPA.MC Average DL BSC6900 WRFD- 3C-HSDPA

Transmit Power 150250 4C-HSDPA
of 4C- WRFD- DB-HSDPA
HSDPA/DB- 150207
HSDPA/DC- DC-HSDPA
WRFD- Flexible Dual
HSDPA UEs for 150209
Cell Carrier
HSDPA
ID Description ID
WRFD- DC-
010696 HSDPA+MIMO
WRFD- DB-
150208 HSDPA+MIMO
WRFD- MC-
010699 HSDPA+MIMO
WRFD-
150227
WRFD-
150223
73425905 VS.MeanTCP.HSDPA.MC Average DL BSC6910 WRFD- 3C-HSDPA

HSDPA/DB- 150207
HSDPA/DC- DC-HSDPA
WRFD- Flexible Dual
Cell Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425910 VS.MaxTCP.HSDPA.MC Maximum DL BSC6900 WRFD- 3C-HSDPA

HSDPA/DB- 150207
HSDPA/DC- DC-HSDPA
WRFD- Flexible Dual
Cell Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
ID Description ID
73425910 VS.MaxTCP.HSDPA.MC Maximum DL BSC6910 WRFD- 3C-HSDPA

HSDPA/DB- 150207
HSDPA/DC- DC-HSDPA
WRFD- Flexible Dual
Cell Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425912 VS.MinTCP.HSDPA.MC Minimum DL BSC6900 WRFD- 3C-HSDPA

HSDPA/DB- 150207
HSDPA/DC- DC-HSDPA
WRFD- Flexible Dual
Cell Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208 DB-
WRFD- HSDPA+MIMO
010699 MC-
WRFD- HSDPA+MIMO
150227
WRFD-
150223
73425912 VS.MinTCP.HSDPA.MC Minimum DL BSC6910 WRFD- 3C-HSDPA

HSDPA/DB- 150207
HSDPA/DC- DC-HSDPA
WRFD- Flexible Dual
Cell Carrier
WRFD- HSDPA
010696 DC-
WRFD- HSDPA+MIMO
150208
ID Description ID
WRFD- DB-
010699 HSDPA+MIMO
WRFD- MC-
150227 HSDPA+MIMO
WRFD-
150223
73425937 VS.HSDPA.RAB.AbnormRel.DB2P Number of BSC6900 WRFD- DB-HSDPA

Abnormal RAB 150209
Releases for
Cell During State
Transition of DB-
HSDPA UEs to
CELL/URA_PCH
73425937 VS.HSDPA.RAB.AbnormRel.DB2P Number of BSC6910 WRFD- DB-HSDPA

Abnormal RAB 150209
Releases for
Cell During State
Transition of DB-
HSDPA UEs to
CELL/URA_PCH
73425938 VS.HSDPA.RAB.AbnormRel.DBMIMO2P Number of BSC6900 WRFD- DB-

Abnormal RAB 150227 HSDPA+MIMO
Releases for
Cell During State
Transition of DB-
HSDPA+MIMO
UEs to
CELL/URA_PCH
73425938 VS.HSDPA.RAB.AbnormRel.DBMIMO2P Number of BSC6910 WRFD- DB-

Abnormal RAB 150227 HSDPA+MIMO
Releases for
Cell During State
Transition of DB-
HSDPA+MIMO
UEs to
CELL/URA_PCH
73425948 VS.HSDPA.RAB.NormRel.DB.All Number of BSC6900 WRFD- DB-HSDPA

Normal RAB 150209
Releases of DB-
HSDPA UEs for
Cell (All
Scenarios)
ID Description ID
73425948 VS.HSDPA.RAB.NormRel.DB.All Number of BSC6910 WRFD- DB-HSDPA

Normal RAB 150209
Releases of DB-
HSDPA UEs for
Cell (All
Scenarios)
73425949 VS.HSDPA.RAB.NormRel.DBMIMO.All Number of BSC6900 WRFD- DB-

Normal RAB 150227 HSDPA+MIMO
Releases of DB-
HSDPA+MIMO
UEs for Cell (All
Scenarios)
73425949 VS.HSDPA.RAB.NormRel.DBMIMO.All Number of BSC6910 WRFD- DB-

Normal RAB 150227 HSDPA+MIMO
Releases of DB-
HSDPA+MIMO
UEs for Cell (All
Scenarios)
73426106 VS.HSDPA.RAB.DBMIMO.AttEstab Number of RAB BSC6900 WRFD- DB-

Setup Attempts 150227 HSDPA+MIMO
for Cell When
DB-HSDPA with
MIMO Applied
73426106 VS.HSDPA.RAB.DBMIMO.AttEstab Number of RAB BSC6910 WRFD- DB-

Setup Attempts 150227 HSDPA+MIMO
for Cell When
DB-HSDPA with
MIMO Applied
73426107 VS.HSDPA.RAB.DBMIMO.SuccEstab Number of BSC6900 WRFD- DB-

Successful RAB 150227 HSDPA+MIMO
Setups for Cell
When DB-
HSDPA with
MIMO Applied
73426107 VS.HSDPA.RAB.DBMIMO.SuccEstab Number of BSC6910 WRFD- DB-

Successful RAB 150227 HSDPA+MIMO
Setups for Cell
When DB-
HSDPA with
MIMO Applied
ID Description ID
73426108 VS.HSDPA.RAB.AbnormRel.DBMIMO Number of BSC6900 WRFD- DB-

Abnormal 150227 HSDPA+MIMO
Released RABs
for Cell When
DB-HSDPA with
MIMO Applied
(RF Exceptions
Considered)
73426108 VS.HSDPA.RAB.AbnormRel.DBMIMO Number of BSC6910 WRFD- DB-

Abnormal 150227 HSDPA+MIMO
Released RABs
for Cell When
DB-HSDPA with
MIMO Applied
(RF Exceptions
Considered)
73426109 VS.HSDPA.RAB.NormRel.DBMIMO Number of BSC6900 WRFD- DB-

Normally 150227 HSDPA+MIMO
Released RABs
for Cell When
DB-HSDPA with
MIMO Applied
73426109 VS.HSDPA.RAB.NormRel.DBMIMO Number of BSC6910 WRFD- DB-

Normally 150227 HSDPA+MIMO
Released RABs
for Cell When
DB-HSDPA with
MIMO Applied
73426114 VS.HSDPA.RAB.DB.AttEstab Number of RAB BSC6900 WRFD- DB-HSDPA

Setup Attempts 150209
for Cell When
DB-HSDPA
Applied
73426114 VS.HSDPA.RAB.DB.AttEstab Number of RAB BSC6910 WRFD- DB-HSDPA

Setup Attempts 150209
for Cell When
DB-HSDPA
Applied
73426115 VS.HSDPA.RAB.DB.SuccEstab Number of BSC6900 WRFD- DB-HSDPA

Successful RAB 150209
Setups for Cell
ID Description ID
When DB-
HSDPA Applied
73426115 VS.HSDPA.RAB.DB.SuccEstab Number of BSC6910 WRFD- DB-HSDPA

Successful RAB 150209
Setups for Cell
When DB-
HSDPA Applied
73426116 VS.HSDPA.RAB.AbnormRel.DB Number of BSC6900 WRFD- DB-HSDPA

Abnormally 150209
Released RABs
for Cell When
DB-HSDPA
Applied (RF
Exceptions
Considered)
73426116 VS.HSDPA.RAB.AbnormRel.DB Number of BSC6910 WRFD- DB-HSDPA

Abnormally 150209
Released RABs
for Cell When
DB-HSDPA
Applied (RF
Exceptions
Considered)
73426117 VS.HSDPA.RAB.NormRel.DB Number of BSC6900 WRFD- DB-HSDPA

Normally 150209
Released RABs
for Cell When
DB-HSDPA
Applied
73426117 VS.HSDPA.RAB.NormRel.DB Number of BSC6910 WRFD- DB-HSDPA

Normally 150209
Released RABs
for Cell When
DB-HSDPA
Applied
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
1. Call Admission Control Feature Parameter Description
2. Directed Retry Decision Feature Parameter Description
3. MC-HSDPA Feature Parameter Description
4. Handover Feature Parameter Description
5. HSDPA Feature Parameter Description
6. HSPA Evolution Feature Parameter Description
7. License Management Feature Parameter Description
8. Load Control Feature Parameter Description
9. Overload Control Feature Parameter Description
10. Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier Feature Parameter
Description
11. Transmission Resource Management Feature Parameter Description
12.
WCDMA RAN
Power Sharing Feature Parameter
Description
Issue 01
Date 2014-04-30
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: http://www.huawei.com/
Email: support@huawei.com
3.2.24 Contents
1.1 Scope
1.3 Change History
1.4 Differences Between Base Station Types
2 Overview
2.1 Background
2.2 Introduction
2.3 Benefits
3.1 Dynamic Power Sharing in Multi-Carriers
3.2 HSDPA Inter-Cell Power Sharing
4 Related Features
4.1 WRFD-020116 Dynamic Power Sharing in Multi-Carriers
4.2 WRFD-160251 HSDPA Inter-Cell Power Sharing
5 Network Impact
6.1.1 When to Use Dynamic Power Sharing in Multi-Carriers
6.1.3 Deployment
6.1.3.3 Activation
6.2.1 When to Use HSDPA Inter-Cell Power Sharing
6.2.3 Deployment
6.2.3.3 Activation
7 Parameters
8 Counters
9 Glossary
1.1 Scope
This document describes the dynamic power sharing features, including the technical principles,
related features, network impact, and engineering guidelines. This document covers the
following features:
WRFD-020116 Dynamic Power Sharing in Multi-Carriers
WRFD-160251 HSDPA Inter-Cell Power Sharing
This document applies to the following NE types.
NE Type NE Model
RNC N/A
NodeB Macro 3900 series macro base stations: BTS3900, BTS3900A,

BTS3900L, BTS3900AL, DBS3900, and BTS3900C
3800 series macro base stations: DBS3800, BTS3812E, and
BTS3812AE
Micro BTS3803E and BTS3902E
LampSite DBS3900 LampSite
This document is intended for personnel who:

Need to understand the features described herein
Work with Huawei products
1.3 Change History
This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version
RAN16.0 01 (2014-04-30)
Compared with Issue 01 (2013-04-28) of RAN15.0, Issue 01 (2014-04-30) of RAN16.0 includes
the following changes.
Change Type Change Description Parameter Change
Feature change Added the WRFD-160251 None

HSDPA Inter-Cell Power
Sharing feature in the
following sections:
3.2 HSDPA Inter-Cell Power
Sharing
4.2 WRFD-160251 HSDPA
Inter-Cell Power Sharing
Editorial change None None
1.4 Differences Between Base Station Types
Feature Support by Macro, Micro, and LampSite Base Stations
Feature Feature Supported by Supported Supported by Micro LampSite

ID Name Controllers by Macro Base Stations
Base
BSC6900 BSC6910 Stations BTS3803E BTS3902E
WRFD- HSDPA N/A N/A Yes Yes Yes No

160251 Inter-Cell
Power
Sharing
WRFD- Dynamic N/A N/A Yes Yes Yes Yes

020116 Power
Sharing in
Multi-
Carriers
NOTE:
Y indicates that a feature is supported; N indicates that a feature is not supported; N/A indicates that an NE is not
involved, that is, a feature does not require the support of the NE.
2 Overview
2.1 Background
Along with the wide use of the WCDMA system, more and more hotspot areas use multi-carrier
power amplifiers (PAs). If traffic cannot be evenly distributed to different carriers, requirements
for downlink power resources will be unbalanced. In this situation, dynamic power sharing can
be used to balance the power requirements between carriers, thereby effectively increasing the
throughput.
2.2 Introduction
Power sharing means that power resources can be dynamically shared and allocated among
carriers or cells that use the same PA. Before the dynamic power sharing features are applied,
each cell is configured with the maximum transmit power. When traffic bursts in certain cells,
the maximum transmit power of these cells cannot be further improved. When multiple cells use
the same PA, power resources are not fully utilized if a cell has a great amount of data to
transmit while another cell has little data even no data to transmit. In this situation, the power
sharing features enable the cell with a great amount of data to transmit to use the remaining
power resources of the other cell, thereby improving cell performance and user experience.
The WRFD-020116 Dynamic Power Sharing in Multi-Carriers feature enables a cell that
carries HSDPA services to use the remaining power resources of another cell that carries
only R99 services with HSDPA services not enabled.
The WRFD-160251 HSDPA Inter-Cell Power Sharing feature enables cells that carry
HSDPA services to mutually share remaining power resources.
2.3 Benefits
After the WRFD-020116 Dynamic Power Sharing in Multi-Carriers feature is enabled, the
average throughput of HSDPA cells at busy hours can be increased by at least 5%.
After the WRFD-160251 HSDPA Inter-Cell Power Sharing feature is enabled, the RNC
automatically identifies inter-frequency co-coverage HSDPA cells that use the same PA in
multicarrier networks and puts these cells in a power sharing group. This feature can
increase the average user throughput of the HSDPA cells in the power sharing group by 5%
to 10% and increase the average throughput of users with a poor CQI by 10% to 50%.
3.1 Dynamic Power Sharing in Multi-Carriers
This chapter describes the WRFD-020116 Dynamic Power Sharing in Multi-Carriers feature.
Overview
This feature enables an R99 cell to share its remaining power resources with an HSDPA cell that
uses the same PA as this R99 cell, thereby increasing the HSDPA cell throughput and user
experience. When cells are configured with different transmit power, an HSDPA cell that is
configured with greater transmit power cannot use the remaining power resources of an R99 cell
that is configured with smaller transmit power.
Figure 3-1 shows how an R99 cell shares its power resources with an HSDPA cell.
Figure 3-1 R99 cell sharing its power resources with an HSDPA cell
Technical Description
The NodeB can be configured with a power sharing group by running the ADD
NODEBPAGRP command. In addition, the source cell is an R99 cell specified by the SLOCELL
parameter, and the target cell is an HSDPA cell specified by the DLOCELL parameter.
An R99 cell periodically calculates the maximum power that can be shared with an HSDPA cell.
The corresponding formula is as follows:
NOTE:
Psource-share indicates the maximum power of the R99 cell that can be shared by the HSDPA cell.
Pavailable indicates the remaining power of the R99 cell. It is calculated by the maximum configured power of
the R99 cell (specified by MaxTxPower) minus the power in use.
Pmax-share indicates the maximum power that can be shared by the R99 cell. It is calculated by multiplying
MaxTxPower and MAXSHRTO of the R99 cell.
Pmargin indicates the reserved power of the R99 cell. It is calculated by multiplying MaxTxPower and SHMGN
of the R99 cell.
The HSDPA cell allocates the power resources for its users based on its maximum configured
power and the maximum power that can be shared by the R99 cell.
3.2 HSDPA Inter-Cell Power Sharing
This chapter describes the WRFD-160251 HSDPA Inter-Cell Power Sharing feature.
Overview
With the HSDPA Inter-Cell Power Sharing feature, an HSDPA cell that has data to transmit but
suffers power resource insufficiency can dynamically share the remaining power resources of an
HSDPA cell in a power sharing group (with the same PA and sector). This feature supports a
maximum of 2 HSDPA cells for power sharing. This increases the power usage and HSDPA
throughput, thereby improving user experience.
The algorithm works as follows: If cell A has HSDPA data to transmit but suffers power
resource insufficiency while cell B has remaining power resources, cell B can share its remaining
power resources with cell A. When HSDPA data transmission in cell A is complete, cell B
reclaims the shared power resources. If cell B has HSDPA data to transmit while HSDPA data
transmission in cell A is in progress by sharing the power resources of cell B, cell B will
instantly reclaim the shared power resources to ensure good user experience. Figure 3-2 shows
details of the algorithm.
Figure 3-2 Dynamic power sharing between two HSDPA cells
If the average load of each cell in a power sharing group is heavy, the remaining power resources
for sharing become scarce. In this situation, the feature gains on the total throughput are not
obvious. If one cell in a power sharing group experiences heavy load while other cells experience
light load, the remaining power resources of lightly loaded cells are always shared by heavily
loaded cells. This affects the experience of users in the lightly loaded cells. Therefore, this
feature is recommended only when the average load of each cell in a power sharing group is
light. It is recommended that this function be used when the cells are both lightly loaded. For
details, see section When to Use HSDPA Inter-Cell Power Sharing.
Technical Description
This feature takes effect when a power sharing group is configured by running the NodeB MML
command ADD NODEBPAGRP with the PWSHM parameter set to HCELLTOHCELL.
This function adjusts the maximum transmit power through the following power sharing
mechanism:
1. Calculates the requested sharing-in or sharing-out power based on the average power usage
of the previous period.
If the average power usage in the previous period is greater than or equal to 80% of
Pmax (maximum configured power, specified by the MaxTxPower parameter), the cell is
set to the "request shared-in" state, and the requested sharing-in power equals the
smaller one between the value of the recommended value of the requested sharing-in
power and the value of Pmax multiplied by Rmax-share (ratio of the maximum cell power
available for sharing to the maximum configured power, specified by the MAXSHRTO
parameter). The recommended value of the requested sharing-in power considers the
average power usage of the cell in the previous period as well as the power sharing
step (15%).
If the average power usage in the previous period is less than 80% of Pmax, the cell is
set to the "request shared-out" state and the requested sharing-out power equals the
smaller one between the value of the recommended requested sharing-out power and
the value of Pmax x Rmax-share. The value of the recommended requested sharing-out
power is calculated as follows: The recommended value of the requested sharing-out
power is calculated as follows: Recommended requested sharing-out power =
Remaining power in the previous period Pmax Rshare-margin. Rshare-margin indicates the
ratio of the reserved power to the maximum configured power of the source cell,
which is specified by the SHMGN parameter.
2. Calculates the power that is actually shared between cells based on the requested sharing-
in or sharing-out power of each cell.
If one cell is in the "request sharing-in" state and the other is in the "request sharing-
out" state, the actual power to be shared is the smaller one between the requested
sharing-in power and requested sharing-out power.
Otherwise, Pshare is 0.Otherwise, the value of the power that is actually shared between
cells is 0.
3. Using es the shared power.
For a cell in the "request sharing-in" state, the power allocated to its HSDPA services
equals the value of Pmax plus the actual power to be shared between cells.
For a cell in the "request sharing-out" state, the power allocated to its HSDPA services
equals the value of Pmax minus the actual power to be shared between cells.
4 Related Features

WRFD-160251 HSDPA Inter-Cell Power Sharing

MRFD-221801 Multi-mode Dynamic Power Sharing (UMTS)
Impacted Features
None
WRFD-020116 Dynamic Power Sharing in Multi-Carriers

MRFD-221801 Multi-mode Dynamic Power Sharing (UMTS)
Impacted Features
WRFD-150236 Load Based Dynamic Adjustment of PCPICH

When the cell load is heavy, the Load Based Dynamic Adjustment of PCPICH feature
reduces pilot power to increase system capacity, which results in a decrease in the Ec/No
and an increase in the call drop rate. When the cell load is light, the HSDPA Inter-Cell
Power Sharing feature increases the maximum transmit power of the cell to improve user
experience, which further decreases the Ec/No. Therefore, it is recommended that these two
features not be enabled together.
WRFD-150235 DPCH Maximum Power Restriction
When the cell load is high, the DPCH Maximum Power Restriction feature restricts the
downlink DPCH transmit power, and therefore users at the cell edge may experience
downlink synchronization failures. If the HSDPA Inter-Cell Power Sharing feature is
enabled while the DPCH Maximum Power Restriction feature is enabled, the average cell
load becomes higher, and users at the cell edge are more likely to experience call drops.
Therefore, it is recommended that these two features not be enabled together.
WRFD-010696 DC-HSDPA/WRFD-150209 DB-HSDPA/WRFD-150250 3C-
HSDPA/WRFD-150207 4C-HSDPA/WRFD-150208 Flexible Dual Carrier HSDPA
The HSDPA Inter-Cell Power Sharing feature does not provide gains for multi-carrier users
when the power sharing cell groups belong to the same multi-carrier cell group, because
multi-carrier users can use available resources of multiple carriers. Since the multi-carrier
user penetration rate has increased on live networks, gains provided by this feature have
been declining.
WRFD-021311 MOCN Introduction Package
It is recommended that the HSDPA Inter-Cell Power Sharing feature not be enabled while
the MOCN feature is enabled, because power sharing between two cells owned by different
operators leads to unfair power resource allocation.

5 Network Impact
System Capacity
After the feature takes effect, the average throughput of HSDPA cells increases by a minimum of
5%.
Network Performance
After the feature takes effect, the average throughput of HSDPA cells increases by a minimum of
5%. However, the CS/PS call drop rate and CS/PS RAB setup success rate may slightly
deteriorate due to increased downlink HSDPA cell load and increased downlink inter-cell
interference.
System Capacity
When this feature is used in two cells with light load, the power resource usage increases. When
the maximum power sharing ratio is set to a value ranging from 40% to 50%, the average user
throughput increases by about 5% to 10%, and the average throughput of users with poor CQIs
(CQI 10) in the cells increases by 10%. The cell throughput gains are affected by the maximum
power configured for the cell. The greater the configured power, the smaller the gains.
If this feature is used in two cells with heavy load, the average user throughput does not increase
because such cells have high power resource usage and remain few resources.
If this feature is used between two cells with unbalanced load (for example, one cell always
shares its power resources with another cell), the average user throughput in the cell that shares
remaining power resources may deteriorate. It is recommended that this feature be disabled in
this scenario.
Network Performance
This feature increases the average transmit power of HS-PSDCHs that transmit data by 10% to
20% and the average cell load by 2% to 5%.
Due to increased downlink cell load and increased downlink inter-cell interference, any of the
following KPIs may deteriorate: CS call drop rate, PS call drop rate, CS RAB setup success rate,
and PS RAB setup success rate. If the deterioration is more serious than expected, lower the
value of the MAXSHRTO parameter.
NOTE:
About the KPI deterioration mentioned above, here is an example from an unnamed office, which is provided for
reference only: After this feature was enabled at an office where the original CS call drop rate was about 0.1% and
the original PS call drop rate was about 0.2%, the CS and PS RAB setup success rates did not change but the RRC
access success rate as well as the CS and PS call drop rates experienced decreases of 0.02%. The deterioration
degree of each site depends on the increase in the downlink load.
6.1.1 When to Use Dynamic Power Sharing in Multi-Carriers
For HSDPA cells, it is recommended that this feature be enabled to further improve the
experience in HSDPA data transmission of users in a cell which meets the following
conditions:
The value of the VS.MeanTCP.NonHS(BSC6900,BSC6910) counter (average
downlink non-HSDPA carrier transmit power) is less than 40%, indicating that the
downlink non-HSDPA carrier transmit power is low.
KPIs (such as the CS/PS call drop rate and CS/PS RAB setup success rate) are better
than the average KPIs of the entire network.
For R99 cells, it is recommended that this feature be enabled when the value of the
VS.MeanTCP.NonHS(BSC6900,BSC6910) counter (average downlink transmit power of
non-HSDPA carriers) is less than 60%.
This feature is not recommended between macro and micro cells in a macro and micro
combined network.
Collect the following data before feature deployment:

Network KPIs: CS call drop rate, PS call drop rate, CS RAB setup success rate, and PS RAB
setup success rate.
RNC performance counters: VS.MeanTCP(BSC6900,BSC6910) and
VS.MeanTCP.NonHS(BSC6900,BSC6910)
NodeB performance counters: VS.PdschPwrRatio.Mean, VS.HSDPA.DataOutput.Traffic,
and VS.HSDPA.All.ScheduledNum
6.1.3 Deployment
Hardware
None
Other Features
For prerequisite features, see 4.1 WRFD-020116 Dynamic Power Sharing in Multi-Carriers.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
Feature ID Feature License Control License License NE License Sales

Name Item ID Control Item Control Allocation Unit
Name Item for
Name Multiple
on Operators
U2000
GUI
WRFD- Dynamic LQW9PASHR01 Power PA NodeB Method 1 per

020116 Power Sharing Sharing Cell
Sharing in Function(per
Multi- NodeB)
Carriers
If RAN Sharing is enabled, the licensed value is allocated among the primary and secondary
operators according to the value of the License Allocation for Multiple Operators
parameter.
Method 1: some license control items, such as Dynamic CE Function (per NodeB), can be
allocated only through the common group. For the NodeB license allocation among
multiple operators, see License Management Feature Parameter Description.
Other Requirements
Dynamic Spectrum Sharing cannot be enabled together with dynamic power sharing.
The R99 cell and HSDPA cell must use the same RF module and be configured with the
same maximum power.
Parameter Parameter ID Setting Notes Data Source
Name
GU Power GUPOWERSHARE Set this parameter to Engineering design

Share Flag FALSE(FALSE).
Source Local SLOCELL Indicates the identity of the Engineering design

Cell ID source local cell that enables
bidirectional power sharing with
the local cell specified by the
Destination Local Cell ID
parameter. This parameter takes
effect when the Power Share
Method parameter is set to
HCELLTOHCELL(HSDPA cell
to HSDPA cell).
Destination DLOCELL Indicates the identity of the Engineering design

Local Cell ID destination local cell that
enables bidirectional power
sharing with the local cell
specified by the Source Local
Cell ID parameter. This
parameter takes effect when the
Power Share Method
parameter is set to
to HSDPA cell).
Max Sharing MAXSHRTO It is recommended that this Default

Power Ratio parameter be set to 50. value/Recommended
value
Sharing Power SHMGN It is recommended that this Recommended value

Margin parameter be set to 10.
6.1.3.3 Activation
Using MML Commands
For recommended values of parameters, see 6.1.3.2 Data Preparation.

1. Run the NodeB MML command MOD ULOCELL. In this step, set the GU Power Share
Flag parameter to FALSE(FALSE).
2. Run the NodeB MML command ADD NODEBPAGRP to configure a power sharing
group. In this step, set the following parameters: Destination Local Cell ID, Source Local
Cell ID, Max Sharing Power Ratio, and Sharing Power Margin. The source local cell
can share partial remaining power resources with the destination local cell.
MML Command Examples

//Running the following commands on the NodeB LMT
//Disabling the GU power sharing function for the cells that have
requirements for power sharing
MOD ULOCELL: ULOCELLID=1, LOCELLTYPE=NORMAL_CELL, GUPOWERSHARE=FALSE;
//Setting the parameters related to the R99-to-HSDPA cell power sharing

ADD NODEBPAGRP: SLOCELL=1, DLOCELL=2, MAXSHRTO=50, SHMGN=10;
Using the CME
NOTE:
When configuring the Dynamic Power Sharing in Multi-Carriers feature on the CME, perform a single configuration
first, and then perform a batch modification if required. Configure the parameters of a single object before a batch
modification. Perform a batch modification before logging out of the parameter setting interface.

Set the parameter described in Table 6-1 on the CME. . For instructions on how to perform
the CME single configuration, see CME Single Configuration Operation Guide.
modification center, press F1 while running the wizard to obtain online help.

Name in CME Batch
Modification
Center
1 NODEBPAGRP NodeB Source Local SLOCELL Yes

Cell ID
Destination DLOCELL Yes

Local Cell ID
Max Sharing MAXSHRTO Yes

Power Ratio
Sharing SHMGN Yes

Power Margin
1. Run the NodeB MML command DSP NODEBPAGRP to check whether a cell is added to
a power sharing group. If it is, this feature has taken effect. If it is not, the cell does not
meet the power sharing requirements.
2. Observe NodeB performance counters. This feature has taken effect if the value of the
following formula increases:
VS.HSDPA.DataOutput.Traffic/(VS.HSDPA.All.ScheduledNum x 2)
Using MML Commands
1. Run the NodeB MML command RMV NODEBPAGRP. In this step, set the Destination
Local Cell ID parameter to remove the corresponding power sharing group.
2. Run the NodeB MML command SET ULOCELLMACHSPARA. In this step, set
HSDPA L2 Optition Switch to OFF.
//Deactivation procedure
RMV NODEBPAGRP: DLOCELL=2;
//Turning off the R99-to-HSDPA cell power sharing switch for the cells that
are enabled with the power sharing function
//Turning off the switch controlling whether to enable Layer 2 optimization
for HSDPA services for all cells that are involved in power sharing
Using the CME
NOTE:
When configuring the Dynamic Power Sharing in Multi-Carriers feature on the CME, perform a single configuration
first, and then perform a batch modification if required. Configure the parameters of a single object before a batch

Operation Guide.
Name in CME Batch
Modification
Center
1 NODEBPAGR NodeB Destination DLOCELL Not supported

Local Cell ID
When the traffic volume is stable, the throughput of HSDPA users in a cell increases at the MAC
layer during data transmission. The throughput can be calculated as follows:
VS.HSDPA.DataOutput.Traffic/(VS.HSDPA.All.ScheduledNum x 2).
If the KPI deterioration is more serious than expected, lower the value of the MAXSHRTO
parameter.
Table 6-3 Alarm for the Dynamic Power Sharing in Multi-Carriers feature
Alarm ID Alarm Name NE Feature ID Feature Name
ALM-28207 Carrier Wave Share Failure NodeB WRFD-010610 HSDPA

Introduction
Package
If you cannot observe whether the WRFD-020116 Dynamic Power Sharing in Multi-Carriers
feature has taken effect in a cell, the cell does not meet the conditions for power sharing. For
details, see 6.1.3.1 Requirements. In this situation, it is recommended that this feature be enabled in
other cells under the same site as this cell or in the cells under other sites.
6.2.1 When to Use HSDPA Inter-Cell Power Sharing
It is recommended that this feature be enabled to further improve user experience in

HSDPA data transmission in a cell with light load and good kPI.
A cell is considered lightly loaded when the value of the
VS.MeanTCP(BSC6900,BSC6910)counter (average carrier transmit power during
busy hours) is less than 70% and the value of the
VS.MeanTCP.NonHS(BSC6900,BSC6910) counter is less than 40%.
A KPI is considered good when the KPI (such as the CS/PS call drop rate and CS/PS
RAB setup success rate) is better than the average KPI of the entire network.
This feature is not recommended when the proportion of multi-carrier users in a cell
exceeds 80%.
NOTE:
The multi-carrier users refer to users whose services are carried on DC/3C/4C carriers. The proportion of these
carriers is calculated as follows: (VS.HSDPA.DC.PRIM.UE.Mean.Cell(BSC6900,BSC6910) +
VS.HSDPA.3C.PRIM.UE.Mean.Cell(BSC6900,BSC6910) +
VS.HSDPA.4C.PRIM.UE.Mean.Cell(BSC6900,BSC6910))/VS.HSDPA.UE.Mean.Cell(BSC6900,BSC691
0). DB-HSDPA users are not considered during site selection because most RRUs and RFUs do not support
DB co-PA at present and only a few RF modules support DB co-PA.
This feature is not recommended between macro and micro cells in a macro and micro
combined network.
If the periodic power sharing function is enabled for small-traffic services or ping services,
the data transmission duration is very short, and therefore the shared power resources
cannot be reclaimed in time. As a result, the service rate on the air interface is lowered, and
the delay is prolonged. It is recommended that this feature be disabled for delay-sensitive
services, such as ping services.
Network KPIs collected before the deployment: CS call drop rate, PS call drop rate, CS
RAB setup success rate, and PS RAB setup success rate
RNC performance counters collected before the deployment:
VS.MeanTCP(BSC6900,BSC6910) and VS.MeanTCP.NonHS(BSC6900,BSC6910)
NodeB performance counters collected before the deployment: VS.PdschPwrRatio.Mean,
VS.HSDPA.DataOutput.Traffic, VS.DataTtiRatio.Mean, and
VS.HSDPA.InactiveDataTtiRatio.Mean
Whether the value of PWRMGN in the LST ULOCELLMACHSPARA command is less
than 10% and whether the value of HspaPower in the LST UCELLHSDPA command is
greater than -1 dB, which determines whether the available HSDPA power is sufficient for
inter-cell power sharing
6.2.3 Deployment
This section describes how to activate, verify, and deactivate HSDPA inter-cell power sharing.
Hardware
Dependency on NodeB hardware
3900 series base stations configured with the WBBPb, WBBPd, WBBPf, or UBBPd
board support this feature. RF modules that support this function are listed in the
following table.
RF Module Type Feature Supported or Not
MRFU Supported
RF Module Type Feature Supported or Not
MRFUd Supported
MRFUe Supported
RRU3804 Supported
RRU3805 Supported
RRU3806 Supported
RRU3824 Supported
RRU3826 Supported
RRU3828 Supported
RRU3829 Supported
RRU3832 Supported
RRU3838 Supported
RRU3908 Supported
RRU3926 Supported
RRU3928 Supported
RRU3929 Supported
RRU3936 Supported
RRU3938 Supported
RRU3942 Supported
WRFU Supported only by band 2.1 GHz
WRFUd Supported
WRFUe Supported
AAU3902 Supported
Other Features
For prerequisite features, see 4.2 WRFD-160251 HSDPA Inter-Cell Power Sharing.
License
None
Other requirements
Both of the cells must be served by one RF module. In the scenarios of multiple RRUs
in one cell, RF modules serving the two cells must be the same.
Both of the cells must be owned by one operator. In MOCN mode, both of the cells
must be owned by one carrier-sharing operator group.
Both of the cells must not be enabled with MIMO, two transmission channels, or
virtual antenna mapping (VAM).
Both of the cells must not be served by RRUs in cold backup mode.
Both of the cells cannot be configured as Integrated Mobile Broadcast (IMB) cells.
The inter-band inter-frequency power sharing is not supported.

Table 6-4 Data to prepare on the NodeB side before enabling this feature
Name
GU Power GUPOWERSHARE Set this parameter to Engineering design

Share Flag FALSE(FALSE).
Power Margin PWRMGN Set this parameter to a value Default

less than or equal to 10%. The value/Recommended
recommended value is 5%. value
Power Share PWSHM Set this parameter to Engineering design

Method HCELLTOHCELL(HSDPA cell
to HSDPA cell).
Source Local SLOCELL Indicates the identity of the Engineering design

Cell ID source local cell that enables
bidirectional power sharing with
the local cell specified by the
Destination Local Cell ID
parameter. This parameter takes
effect when the Power Share
Method parameter is set to
to HSDPA cell).
Destination DLOCELL Indicates the identity of the Engineering design

Local Cell ID destination local cell that
enables bidirectional power
sharing with the local cell
specified by the Source Local
Cell ID parameter. This
Name
parameter takes effect when the

Power Share Method
parameter is set to
to HSDPA cell).
Max Sharing MAXSHRTO It is recommended that this Default

Power Ratio parameter be set to 50. value/Recommended
value
Sharing Power SHMGN It is recommended that this Default

Margin parameter be set to 15. value/Recommended
value
Table 6-5 Data to prepare on the RNC side before enabling this feature
Parameter Name Parameter ID Setting Notes Data Source
Offset of HSPA Total HspaPower Set this parameter to a Default

Power value greater than or value/Recommended
equal to -1 dB. The value
recommended value is
0.
6.2.3.3 Activation
Using MML Commands
For recommended values of parameters, see 6.2.3.2 Data Preparation.

1. Run the NodeB MML command MOD ULOCELL. In this step, set the GU Power Share
Flag parameter to FALSE(FALSE).
2. Run the NodeB MML command SET ULOCELLMACHSPARA to configure the Power
Margin parameter.
3. Run the NodeB MML command ADD NODEBPAGRP to configure a power sharing
group. In this step, set the following parameters: Power Share Method, Source Local
Cell ID, Destination Local Cell ID, Max Sharing Power Ratio, and Sharing Power
Margin. The source local cell and destination local cell can share remaining power
resources with each other.
4. Run the RNC MML command MOD UCELLHSDPA to configure the Offset of HSPA
Total Power parameter.
//Running the following commands on the NodeB LMT

//Disabling the GU power sharing function for the cells that have
requirements for power sharing
MOD ULOCELL: ULOCELLID=1, LOCELLTYPE=NORMAL_CELL, GUPOWERSHARE=FALSE;
SET ULOCELLMACHSPARA: ULOCELLID=1, PWRMGN=5;
//Configuring a power sharing group
ADD NODEBPAGRP: PWSHM=HCELLTOHCELL, SLOCELL=1, DLOCELL=2, MAXSHRTO=50,
SHMGN=15;
//Configuring the available HSDPA power resources for all cells that have
requirements for power sharing by running the following command on the RNC
LMT
MOD UCELLHSDPA: CellId=1, HspaPower=0;
Using the CME
NOTE:
When configuring the HSDPA Inter-Cell Power Sharing feature on the CME, perform a single configuration first,
and then perform a batch modification if required. Configure the parameters of a single object before a batch

Operation Guide.

Name in CME
Batch
Modification
Center
1 ULOCELL NodeB GU Power GUPOWERSHARE Yes

Share Flag
2 UCELLHSDPA RNC Offset of HspaPower(BSC6910,BSC6900) Yes

HSPA
Total
Power
3 ULOCELLMACHSPARA NodeB Power PWRMGN Yes

Margin
Name in CME
Batch
Modification
Center
4 NODEBPAGRP NodeB Power PWSHM

Share
Method
Source SLOCELL
Local Cell
ID
Destination DLOCELL
Local Cell
ID
Max MAXSHRTO
Sharing
Power
Ratio
Sharing SHMGN
Power
Margin
1. Run the NodeB MML command DSP NODEBPAGRP to check whether a cell is added to
a power sharing group. If it is, this feature has taken effect. If it is not, the cell does not
meet the power sharing requirements.
2. If the value of the NodeB counter VS.HSDPAPwrShare.TtiNum is greater than zero, the
HSDPA inter-cell power sharing feature has been activated.
Using MML Commands
1. Run the NodeB MML command RMV NODEBPAGRP. In this step, set the Destination
Local Cell ID parameter to remove a specified cell from the power sharing group.
//Deactivation procedure
RMV NODEBPAGRP: DLOCELL=2;
Using the CME

NOTE:
When configuring the HSDPA Inter-Cell Power Sharing feature on the CME, perform a single configuration first,
and then perform a batch modification if required. Configure the parameters of a single object before a batch

Operation Guide.
Table 6-7 Configuring the parameter on the CME
SN MO NE Parameter Parameter ID Configurable in

Name CME Batch
Modification
Center
1 NODEBPAGR NodeB Destination DLOCELL No

Local Cell ID
Gain Evaluation
When the traffic volume is stable, the throughput of HSDPA users in a cell increases at the MAC
layer during data transmission.
The throughput can be calculated as follows:
VS.HSDPA.DataOutput.Traffic/[(VS.DataTtiRatio.Mean -
VS.HSDPA.InactiveDataTtiRatio.Mean) x {SP} x 60]. SP indicates the statistical periods of
the performance counters in the formula.
Impact on Performance Counters
On the NodeB side, the values of counters related to the HSDPA transmit power may exceed
100%.
Measurements on the RNC are based on reported NodeB common measurements. As specified in
3GPP specifications, the downlink transmit power in the reported common measurements ranges
from 0% to 100% relative to the maximum configured transmit power. Therefore, the downlink
transmit power in a cell cannot be accurately determined based on the performance counters on
the RNC side after this feature is enabled.
Relationships between the NodeB and RNC performance counters are changed as follows:
Before the HSDPA Inter-Cell Power Sharing feature is enabled, the sum of
VS.PdschPwrRatio.Mean and VS.MeanTCP.NonHS approaches to the value of
VS.MeanTCP.
After the HSDPA Inter-Cell Power Sharing feature is enabled, the sum of
VS.PdschPwrRatio.Mean and VS.MeanTCP.NonHS may be greater than the value of
VS.MeanTCP.
The calculation formula is as follows:
Where
VS.PdschPwrRatio.Mean indicates the average transmit power of the HS-PDSCH in the
observed cell, in the unit of . This is a NodeB counter.
VS.MeanTCP.NonHS(BSC6900,BSC6910) indicates the average downlink non-HSDPA
carrier transmit power in a cell, in the unit of dBm. This is an RNC counter.
VS.MeanTCP(BSC6900,BSC6910) indicates the average carrier transmit power in a cell, in the
unit of dBm. This is an RNC counter.
MaxTxPower: Indicates the maximum configured transmit power in a cell, in the unit of 0.1
dBm. This is an RNC counter.
KPI Monitoring
The CS/PS call drop rate and CS/PS RAB setup success rate slightly deteriorate after the
HSDPA Inter-Cell Power Sharing feature is enabled.
If the KPI deterioration is more serious than expected, lower the value of the MAXSHRTO
parameter.
Table 6-8lists the new alarm for this feature. When power sharing is configured for carriers, this
alarm is reported if the logical cell to be established does not meet the power sharing
requirements.
Table 6-8 Alarm for the HSDPA Inter-Cell Power Sharing feature
Alarm ID Alarm Name NE Feature ID Feature Name
ALM-28207 Carrier Wave Share Failure NodeB WRFD-010610 HSDPA

Introduction
Package
7 Parameters
Table 7-1 Parameters

Parameter ID NE MML Command Feature ID Feature Name Description
SLOCELL BTS3900, ADD NODEBPAGRP WRFD- Dynamic Meaning: When Power

BTS3900 MOD NODEBPAGRP 020116 Power Sharing Share Method is set to
WCDMA LST NODEBPAGRP WRFD- in Multi- R99CELLTOHCELL, only
010610 Carriers unidirectional power
HSDPA sharing from the source
Introduction cell (specified by
Package SLOCELL) to the target
cell (specified by
DLOCELL) is supported
and this parameter
specifies the source cell.
When Power Share
Method is set to
HCELLTOHCELL,
bidirectional power
sharing between local cell
1 (specified by SLOCELL)
and local cell 2 (specified
by DLOCELL) is
supported and this
parameter specifies local
cell 1.
GUI Value Range:
0~268435455
Unit: None
Actual Value Range:
0~268435455
Default Value: None
DLOCELL BTS3900, ADD NODEBPAGRP WRFD- Dynamic Meaning: When Power
BTS3900 RMV NODEBPAGRP 020116 Power Sharing Share Method is set to
WCDMA LST NODEBPAGRP WRFD- in Multi- R99CELLTOHCELL, only
010610 Carriers unidirectional power
HSDPA sharing from the source
Introduction cell (specified by
Package SLOCELL) to the target
cell (specified by
DLOCELL) is supported
and this parameter
specifies the target cell.

When Power Share
Method is set to
HCELLTOHCELL,
bidirectional power
sharing between local cell
1 (specified by SLOCELL)
and local cell 2 (specified
by DLOCELL) is
supported and this
parameter specifies local
cell 2.
GUI Value Range:
0~268435455
Unit: None
Actual Value Range:
0~268435455
Default Value: None
MAXSHRTO BTS3900, ADD NODEBPAGRP WRFD- Dynamic Meaning:
BTS3900 MOD NODEBPAGRP 020116 Power Sharing Indicates the maximum
WCDMA LST NODEBPAGRP WRFD- in Multi- proportion of the available
010610 Carriers power that can be shared
HSDPA if Power Share Method is
Introduction set to
Package R99CELLTOHCELL. The
proportion is the ratio of
the available power
shared by the source
local cell with the target
local cell to the maximum
transmit power of the
source cell.
Indicates the maximum
proportion of the available
power that can be shared
between two HSDPA cells
if Power Share Method is
set to HCELLTOHCELL.
The proportion is the ratio
of the available power
that a local cell can
provide or request for
sharing to the maximum
transmit power of the
local cell.
GUI Value Range: 1~80
Unit: %
Actual Value Range:
1~80
Default Value: 50
SHMGN BTS3900, ADD NODEBPAGRP WRFD- Dynamic Meaning: Indicates the
BTS3900 MOD NODEBPAGRP 020116 Power Sharing power sharing margin. If
WCDMA LST NODEBPAGRP WRFD- in Multi- Power Share Method is
010610 Carriers set to
HSDPA R99CELLTOHCELL, the
Introduction margin is used to
Package counteract power
fluctuation of R99 users
due to delayed power
sharing. If Power Share
Method is set to
HCELLTOHCELL, the
margin is used to
counteract power
fluctuation of R99 users
due to delayed power
sharing and the burst
services in the HSDPA
cell that provides power
for sharing.
Unit: %
Actual Value Range:
1~80
Default Value: 10
PWSHM BTS3900, ADD NODEBPAGRP WRFD- HSDPA Meaning:
BTS3900 MOD NODEBPAGRP 010610 Introduction Indicates the policy of
WCDMA LST NODEBPAGRP Package power sharing between
cells. If this parameter is
set to
R99CELLTOHCELL, only
one-way power sharing
from the source cell
(SLOCELL) to the target
cell (DLOCELL) is
supported.
If this parameter is set to
HCELLTOHCELL,
bilateral power sharing
between local cell 1
(SLOCELL) and local cell
2 (DLOCELL) is
supported.
GUI Value Range:
R99CELLTOHCELL(R99
cell to HSDPA cell),
HCELLTOHCELL(HSDPA
cell to HSDPA cell)
Unit: None
Actual Value Range:
R99CELLTOHCELL,
HCELLTOHCELL
Default Value:
R99CELLTOHCELL(R99
cell to HSDPA cell)
MaxTxPower BSC6900 ADD UCELLSETUP WRFD- Open Loop Meaning: Sum of the
MOD UCELL 020501 Power Control maximum transmit power
of all DL channels in a
cell. For detailed
information of this
parameter, see 3GPP TS
25.433.
Unit: 0.1dBm
Actual Value Range:
0~50
Default Value: 430
GUPOWERSHARE BTS3900, ADD ULOCELL MRFD- Multi-mode Meaning: Indicates
BTS3900 MOD ULOCELL 221801 Dynamic whether the local cell
WCDMA LST ULOCELL Power supports GU power
Sharing(UMTS) share. When the
parameter is set to TRUE,
the local cell supports GU
power share.
GUI Value Range:
FALSE(FALSE),
TRUE(TRUE)
Unit: None
Actual Value Range:
FALSE, TRUE
Default Value:
TRUE(TRUE)
PWRMGN BTS3900, SET WRFD- HSDPA Power Meaning: Indicates the

BTS3900 ULOCELLMACHSPARA 01061004 Control power margin reserved
WCDMA LST for R99 channels. It
ULOCELLMACHSPARA
specifies the power
percentage relative to the
maximum cell transmit
power.
Unit: %
Actual Value Range:
0~100
Default Value: 5
HspaPower BSC6900 ADD UCELLHSDPA WRFD- HSDPA Power Meaning: This parameter
MOD UCELLHSDPA 01061004 Control specifies the offset
between the total HSPA
power and the maximum
transmission power of a
cell. The total HSPA
power is the maximum
value of HSPA dynamical
power can be adjusted.
For details about this
25.308.
GUI Value Range: -500~0
Unit: 0.1dB
Actual Value Range: -
50~0
Default Value: 0
HspaPower BSC6910 ADD UCELLHSDPA WRFD- HSDPA Power Meaning: This parameter
MOD UCELLHSDPA 01061004 Control specifies the offset
between the total HSPA
power and the maximum
transmission power of a
cell. The total HSPA
power is the maximum
value of HSPA dynamical
power can be adjusted.
For details about this
25.308.
GUI Value Range: -500~0
Unit: 0.1dB
Actual Value Range: -

50~0
Default Value: 0
8 Counters
Table 8-1 Counters

Counter ID Counter Name Counter NE Feature ID Feature
Description Name
50332192 VS.HSDPAPwrShare.TtiNum Number of NodeB Multi-mode: HSDPA

TTIs within None Inter-Cell
which the GSM: None Power
HSDPA cell UMTS: Sharing
uses shared WRFD-
power 160251
LTE: None
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
1. License Management Feature Parameter Description
2. HSDPA Feature Parameter Description
3. GSM and UMTS Dynamic Power Sharing Feature Parameter Description

RAN Feature Huawei

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RAN Feature Huawei

Uploaded by

Copyright:

Available Formats

DB-HSDPA

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Huawei Technologies Co., Ltd.

1 About This Document

RNC BSC6900 and BSC6910

NodeB Macro 3900 series macro base stations: BTS3900, BTS3900A,

Micro The micro base stations do not support this feature.

LampSite The LampSite base stations do not support this feature.

1.2 Intended Audience

This document is intended for personnel who:

This issue does not include any changes.

RAN16.0 Draft A (2014-01-20)

Compared with Issue 04 (2013-12-30) of RAN15.0, Draft A (2014-01-20) of RAN16.0 includes

Change Type Change Description Parameter Change

Feature change Changed DB-HSDPA to an optional None

Editorial change Before activating the DB-HSDPA feature, None

1.4 Differences Between NodeB Types

Feature Support by Macro, Micro, and LampSite NodeBs

Feature Feature Name Supported by Supported Supported by Micro Supported

This document describes two features:

DB-HSDPA Cell Group

The DB-HSDPA feature enables a UE to simultaneously establish HSDPA connections in two

Table 2-1 DB-HSDPA frequency bands

1 I + VIII (2100 MHz + I or VIII I and VIII

2 II + IV (1900 MHz + II or IV II and IV

3 I + V (2100 MHz + I or V I and V

4 I + XI (2100 MHz + I or XI I and XI

5 II + V (1900 MHz + II or V II and V

3.1.1 DB-HSDPA Cell Group

describes the requirements of DB-HSDPA/DB-HSDPA+MIMO for network elements

RNC The RNC must support Downlink Enhanced L2.

3.1.3 Function Summary

Table 3-2 Function summary of DB-HSDPA/DB-HSDPA+MIMO

3.2 Radio Bearer Policy

3.3.1 Load Evaluation

Downlink Cell Power

Figure 3-1 Composition of downlink cell power

Equivalent Number of Downlink Users

Number of HSDPA Users

When an RB is being established or a UE transitions from the CELL_FACH, CELL_PCH, or

Ranking Candidate Cells

Determining the Primary and Secondary Cells

NodeB Credit Resource-based CAC

Iub Transmission Resource-based CAC

DB-HSDPA has no impact on admission based on Iub transmission resources.

CAC Based on the Number of HSDPA Users

Downlink Cell Power Resource-based CAC

3.3.6 Congestion Control

DB-HSDPA affects congestion control as follows:

The DB-HSDPA feature supports DB-HSDPA users' state transitions between

4.1 WRFD-150209 DB-HSDPA

WRFD-010610 HSDPA Introduction Package

Mutually Exclusive Features

DB-HSDPA is affected by the following feature and function:

4.2 WRFD-150227 DB-HSDPA+MIMO

Mutually Exclusive Features

DB-HSDPA+MIMO is affected by the following feature:

5.1 WRFD-150209 DB-HSDPA

This feature improves spectral efficiency to achieve the following benefits:

6.1 WRFD-150209 DB-HSDPA

6.1.1 When to Use DB-HSDPA

DB-HSDPA is recommended in the following scenarios:

Information Used to Evaluate Feature Deployment

Before feature deployment, operators need to collect the following information: