Hsdpa PDF

HSDPA Feature Parameter Description
Page 1 of 69
WCDMA RAN
RAN15.0

Issue
01
Date
2013-04-28
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

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

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

Address:
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
2 Overview
2.1 General Principles of HSDPA
2.2 HSDPA Channels
2.2.1 HS-DSCH and HS-PDSCH
2.2.2 HS-SCCH
2.2.3 HS-DPCCH
2.2.4 DPCCH and DPCH/F-DPCH
http://localhost:7890/pages/GEC0207J/02/GEC0207J/02/resources/en-us_bookmap_0... 20/04/2014
Page 2 of 69
2.3 Impact of HSDPA on NEs

2.4 HSDPA Functions
2.4.1 HSDPA Control Plane Functions
2.4.2 HSDPA User Plane Functions
3 Control Plane
3.1 Bearer Mapping
3.2 Access Control
3.3 Mobility Management
3.4 Channel Switching
3.5 Load Control
3.6 Power Resource Management
3.7 Code Resource Management
3.7.1 HS-SCCH Code Resource Management
3.7.2 HS-PDSCH Code Resource Management
3.7.3 Dynamic Code Tree Reshuffling
4 User Plane
4.1 Flow Control and Congestion Control
4.1.1 Flow Control
4.1.2 Congestion Control
4.2 Impact of HSDPA on the RLC and MAC-d Entities
4.2.1 Impact on the RLC Entity
4.2.2 Impact on the MAC-d Entity
4.3 MAC-hs Scheduling
4.3.1 Determining the Candidate Set
4.3.2 Calculating Scheduling Priorities
4.3.3 Time and HS-PDSCH Codes Multiplex
4.4 HARQ
4.4.1 HARQ Retransmission Principles
4.4.2 Soft Combining During HARQ
4.4.3 Preamble and Postamble
4.5 TFRC Selection
4.6 HSDPA Remaining Power Appending
4.7 CQI Adjustment Based on Dynamic BLER Target
4.8 BLER Optimization for HSDPA Burst Services
4.9 Modulation Scheme
5 QoS Management and Management over Differentiated Services

5.1 QoS Management
5.2 Diff-Serv Management
6 Related Features
6.1 WRFD-010610 HSDPA Introduction Package
6.1.1 Prerequisite Features
6.1.2 Mutually Exclusive Features
6.1.3 Impacted Features
6.2 WRFD-010653 96 HSDPA Users per Cell
6.4 WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
6.5 WRFD-140221 HSDPA Scheduling based on UE Location
7 Network Impact
7.1.1 System Capacity
7.1.2 Network Performance
Page 3 of 69

8 Engineering Guidelines
8.1.1 When to Use HSDPA Introduction Package
8.1.2 Information to Be Collected
8.1.3 Feature Deployment
8.1.4 Performance Monitoring
8.1.5 Parameter Optimization
8.1.6 Troubleshooting
8.2 WRFD-010650 HSDPA 13.976Mbps per User
8.2.1 When to Use HSDPA 13.976Mbps per User
8.3 WRFD-01061001 15 Codes per Cell
8.3.1 When to Use 15 Codes per Cell
8.4 WRFD-01061018 Time and HS-PDSCH Codes Multiplex
8.4.1 When to Use Time and HS-PDSCH Codes Multiplex
8.5 WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
8.5.1 When to Use HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
8.6 WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
8.6.1 When to Use HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
8.7 WRFD-01061010 HSDPA Flow Control
8.7.1 When to Use HSDPA Flow Control
8.8 WRFD-01061006 HSDPA Mobility Management
8.8.1 When to Use HSDPA Mobility Management
8.9 WRFD-01061002 HSDPA UE Category 1 to 28
8.9.1 When to Use HSDPA UE Category 1 to 28
8.10 WRFD-010629 DL 16QAM Modulation
8.10.1 When to Use DL 16QAM Modulation
8.11 WRFD-010631 Dynamic Code Allocation Based on NodeB
8.11.1 When to Use Dynamic Code Allocation Based on NodeB
8.12 WRFD-010611 HSDPA Enhanced Package
8.12.1 When to Use HSDPA Enhanced Package
8.13 WRFD-01061103 Scheduling based on EPF and GBR
8.13.1 When to Use Scheduling based on EPF and GBR
8.14.1 When to Use 96 HSDPA Users per Cell
8.16.1 When to Use CQI Adjustment Based on Dynamic BLER Target
Page 4 of 69

8.17.1 When to Use HSDPA Scheduling based on UE Location
8.18.1 When to Use HSDPA Remaining Power Appending
8.19.1 When to Use BLER Optimization for HSDPA Burst Services
9 Parameters
10 Counters
11 Glossary
12 Reference Documents
1 About This Document

1.1 Scope
This document describes the HSDPA functional area. It provides an overview of the main functions and goes into details regarding HSDPA control and user plane functions.
1.2 Intended Audience

This document is intended for personnel who:
Are familiar with WCDMA basics
Need to understand HSDPA
Work with Huawei products
1.3 Change History

This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
Feature change: refers to the change in the HSDPA feature.
Editorial change: refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Versions
The document versions are as follows:
01 (2013-04-28)
Draft A (2013-01-30)
01 (2013-04-28)
This is the first commercial release of RAN15.0. Compared with Issue Draft A (2013-01-30) of RAN15.0, 01 (2013-04-28) of RAN15.0 includes the following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
Added the description about related features and network impact of the following features and
optimized the description about engineering guidelines:
None
WRFD-010610 HSDPA Introduction Package

WRFD-010653 96 HSDPA Users per Cell
WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
WRFD-140221 HSDPA Scheduling Based on UE Location
For details, see chapters as follows:
6 Related Features
7 Network Impact
Draft A (2013-01-30)
This is a draft for RAN15.0.
Compared with Issue 03 (2012-11-30) of RAN14.0, Draft A (2013-01-30) of RAN15.0 includes the following changes.
Change Type
Feature change
Change Description
In section 4.6 HSDPA Remaining Power Appending, the

EXTRAPOWER parameter replaced the RESVERD3 parameter.
Added the BLER Optimization for HSDPA Burst Services function
and the engineering guidelines about this function. For details, see
section 4.8 BLER Optimization for HSDPA Burst Services and 8.19
BLER Optimization for HSDPA Burst Services.
The NodeB MML command name SET/LST MACHSPARA has
been changed to SET/LST ULOCELLMACHSPARA.
Parameter Change
The EXTRAPOWER parameter replaced the RESVERD3

parameter.
Changed the switch from RSVDBIT6 under the RsvdPara1
parameter of the ADD UCELLALGOSWITCH command to
FDPCH_SF_ALLOC_OPT_SWITCH under the
DlSfAdmAlgoSwitch(BSC6900,BSC6910) parameter of the
ADD UCELLALGOSWITCH command.
Editorial change
Page 5 of 69
Modified descriptions of the CME-based configuration. For details, see

chapter 8 Engineering Guidelines.
None
2 Overview
2.1 General Principles of HSDPA
To meet the rapidly growing demands for data services on the mobile network, 3GPP Release 5 introduced HSDPA in 2005. HSDPA improves the downlink capacity, increases the
user data rate greatly, and reduces the transmission delay on the WCDMA network.
The characteristics of HSDPA are as follows:
Fast scheduling
Fast scheduling introduced into the NodeB determines the UEs for data transmission in
each TTI (2 ms) and dynamically allocates resources to these UEs. It improves the
usage of system resources and increases the system capacity.
For details about how Huawei RAN implements fast scheduling, see section 4.3 MAChs Scheduling.
Fast HARQ
Fast hybrid automatic repeat request (HARQ) is used to rapidly request the
retransmission of erroneously received data.
Specifically, when the UE detects an erroneous data transmission, it saves the received
data and requests the NodeB to retransmit the original data at the physical layer.
Before decoding, the UE performs soft combining of the saved data and the
retransmitted data. The combining fully uses the data transmitted each time and
therefore increases the decoding success rate. In addition, the retransmission delay at
the physical layer is reduced greatly, compared with that at the RLC layer.
For details about how Huawei RAN implements fast HARQ, see section 4.4 HARQ.
Fast AMC
To compensate for channel variations, the DCH performs power control. To achieve
this goal, HSDPA also performs fast adaptive modulation and coding (AMC), that is,
adjusts the modulation scheme and coding rate in each TTI. AMC is based on the
channel quality indicator (CQI) reported by the UE, and its purpose is to select an
appropriate transmission rate to meet channel conditions. When the channel conditions
are good, 16QAM or 64QAM can be used to provide higher transmission rates. When
the channel conditions are poor, QPSK can be used to ensure the transmission quality.
For details about how Huawei RAN implements fast AMC, see section 4.5 TFRC
Selection.
The MAC-hs, a new MAC sublayer, is introduced into the UE and NodeB to support HSDPA.
2.2 HSDPA Channels

To support the HSDPA technologies, 3GPP defines one transport channel (HS-DSCH) and three physical channels (HS-PDSCH, HS-SCCH, and HS-DPCCH).
Figure 2-1 shows the physical channels of HSDPA in the shaded area.
Figure 2-1 Physical channels of HSDPA
2.2.1 HS-DSCH and HS-PDSCH

HS-DSCH is a high-speed downlink shared channel. Its TTI is fixed to 2 ms. It may be mapped onto one or more HS-PDSCHs.
HS-PDSCH is a high-speed physical downlink shared channel. Its spreading factor is fixed to 16. According to 3GPP TS 25.433, a maximum of 15 HS-PDSCHs can be used for
transmission at the same time. The number of HS-PDSCHs per cell is configurable.
The use of 2 ms TTI reduces the round trip time (RTT) on the Uu interface and, together with AMC, improves the tracking of channel variations. In addition, the use of 2 ms TTI
enables fast scheduling and resource allocation and therefore improves the usage of transmission resources.
In each TTI, HSDPA assigns the HS-PDSCHs onto which the HS-DSCH maps. More HS-PDSCHs can provide higher transmission rates.
Unlike the DCH, the HS-DSCH cannot support soft handover. The reason is that this type of handover requires different cells to use the same radio resource for sending the same
data to the UE, but the scheduling function can be performed only within the cell.
2.2.2 HS-SCCH
HS-SCCH is a high-speed shared control channel. It carries the control information related to the HS-PDSCH. The control information includes the UE identity, HARQ-related
information, and information about transport format and resource combination (TFRC). For each transmission of the HS-DSCH, one HS-SCCH is required to carry the related
control information. One cell can be configured with several HS-SCCHs. The number of HS-SCCHs determines the maximum number of UEs that can be scheduled
simultaneously in each TTI.
2.2.3 HS-DPCCH
HS-DPCCH is a high speed dedicated physical control channel. In the uplink, each HSDPA UE must be configured with an HS-DPCCH. This channel is mainly used by the UE to
report the CQI and whether a transport block is correctly received. The information about the transport block is used for fast retransmission at the physical layer. The CQI is used
for AMC and scheduling to allocate Uu resources.
2.2.4 DPCCH and DPCH/F-DPCH

DPCCH is a dedicated physical control channel in the uplink. DPCH is a dedicated physical channel in the downlink. F-DPCH is a fractional dedicated physical channel in the
downlink.
The HSDPA UE must be configured with dedicated physical control channels in both the uplink and the downlink.
The uplink DPCCH is used for closed-loop power control by working with the DPCH or F-DPCH. In addition, the uplink DPCCH power is used as a reference for the HS-DPCCH
power.
The downlink DPCH is used for inner-loop power control and as a reference for the HS-PDSCH power.
Like the downlink DPCH, the F-DPCH is also used for inner-loop power control. The difference is that each UE must have a downlink DPCH (SF256) whereas 10 UEs can share
an F-DPCH (SF256) to save downlink channel codes.
2.3 Impact of HSDPA on NEs
Page 6 of 69
HSDPA has the following impacts on the RNC, NodeB, and UE.
On the control plane of the network side, the RNC processes the signaling about HSDPA cell configuration, HS-DSCH related channel configuration, and mobility management. On
the user plane of the network side, the RLC layer and MAC-d of the RNC are unchanged. At the NodeB, the MAC-hs is added to implement HSDPA scheduling, Uu resource
allocation, AMC, and Iub flow control. The MAC-hs implements these management functions in a short time. Therefore, it reduces both unnecessary delays and processing
complexity caused by Iub message exchange.
On the UE side, the MAC-hs is added between the MAC-d and the physical layer for data reception. To support HSDPA (without considering HSPA evolution), 3GPP defines 12
UE categories. These UEs support different peak rates at the physical layer, ranging from 912 kbit/s to 14 Mbit/s. The UE of category 10 supports the highest rate. The UE of
category 11 or 12 supports only the QPSK mode. For details, see 3GPP TS 25.306. Huawei RAN supports all the UE categories.
Table 2-1 lists the capabilities of HSDPA UEs of different categories.
Table 2-1 Capabilities of HSDPA UEs of different categories
UE Category
Maximum Number of HS-DSCH

Codes
Minimum TTI
Maximum Number of Data Blocks Maximum Data Rate (Mbit/s)
7298
1.2
7298
1.2
7298
1.8
7298
1.8
7298
3.6
7298
3.6
10
14411
7.2
10
14411
7.2
15
20251
10.2
10
15
27952
14.4
11
3630
0.9
12
3630
1.8
2.4 HSDPA Functions

HSDPA functions are implemented on the HSDPA control plane and user plane.
2.4.1 HSDPA Control Plane Functions

The control plane is responsible for setting up and maintaining HS-DSCH connections and managing cell resources.
Figure 2-2 shows the HSDPA control plane functions based on the service connection setup and maintenance procedure.
Figure 2-2 HSDPA control plane functions
The HSDPA control plane functions are described as follows:
Bearer mapping
The bearer mapping is used by the network side to configure the RAB during the setup of a service connection in the cell. The network side then configures bearer channels
for the UE based on the requested service type, service rate, UE capability, and cell capability.
For details, see section 3.1 Bearer Mapping.
Access control
Access control, a sub-function of load control, checks whether the current resources of the cell are sufficient for the service connection setup. If the resources are insufficient,
intelligent access control is triggered. If the resources are sufficient, the service connection can be set up.
For details, see section 3.2 Access Control.
Mobility management
For the established HS-DSCH connection, mobility management decides whether to switch it to another cell for providing better services, based on the channel quality of the
UE.
For details, see section 3.3 Mobility Management.
Channel switching
Channel switching is responsible for switching the transport channel among the HS-DSCH, DCH, and FACH based on the requirements of mobility management or load
control.
For details, see section 3.4 Channel Switching.
Load control
When the cell load increases, the load control function adjusts the resources configured for the established radio connections to avoid cell overload.
For details, see section 3.5 Load Control.
Resource management
Resource management coordinates the power resource between the HS-DSCH and the DCH and the code resource between the HS-SCCH and the HS-PDSCH. The
downlink power and codes are the bottleneck resources of the cell. Resource management can increase the HSDPA capacity.
Page 7 of 69
Power resource management reserves power for channels of different types and allocates power for them. For details, see section 3.6 Power Resource Management.
Code resource management allocates and reserves code resources for channels of different types. In addition, it collects and reshuffles idle code resources.
For details, see section 3.7 Code Resource Management.
2.4.2 HSDPA User Plane Functions

After the service is set up, the user plane is responsible for implementing data transmission.Figure 2-3 shows the HSDPA user plane functions based on the data processing
procedure.
Figure 2-3 HSDPA user plane functions
The service data is passed to the RLC layer and MAC-d of the RNC for processing and encapsulation. Then, the MAC-d PDU is formed and passed through the Iub/Iur interface to
the NodeB/RNC. To avoid congestion, the flow control and congestion control functions control the traffic on the Iub/Iur interface through the HS-DSCH frame protocol (3GPP TS
25.435).
After the MAC-d PDU is received by the NodeB, it is passed through the MAC-hs to the physical layer and then sent out through the Uu interface. The MAC-hs provides MAC-hs
scheduling, TFRC selection, and HARQ. MAC-hs scheduling determines the HSDPA users in the cell for data transmission. TFRC selection determines the transmission rates and
Uu resources to be allocated to the HSDPA UEs. HARQ is used to implement the hybrid automatic repeat request function.
3 Control Plane
This chapter consists of the following sections:
3.1 Bearer Mapping
3.2 Access Control
3.5 Load Control
3.1 Bearer Mapping

The HS-DSCH can carry services of multiple types and service combinations, as listed in Table 3-1.
Table 3-1 Bearer mapping
CN Domain
Service Type
Can Be Carried on HS-DSCH?
Optional Feature?
Signaling (SRB)
Yes
Yes
Feature name: SRB over HSDPA
CS
Voice
Yes
Yes
Feature name: CS Voice over
HSPA/HSPA+
Videophone
No
No
Streaming
No
No
Conversational
Yes
Yes
Feature name: VoIP over HSPA/HSPA+
Streaming
Yes
Yes
Feature name: Streaming Traffic Class on
HSDPA
Interactive
Yes
No
Background
Yes
No
IMS signaling
Yes
Yes
Feature name: IMS Signaling over HSPA
MBMS PTP
Yes
Yes
Feature name: MBMS P2P over HSDPA
PS
During the service setup, the RNC selects appropriate channels based on the UE capability, cell capability, and service parameters to optimize the use of cell resources and
ensure the QoS. Huawei RAN supports the setting of the types of RABs carried on the HS-DSCH according to service requirements. For details, see Radio Bearers Feature
Parameter Description.
3.2 Access Control

Access control determines whether an HS-DSCH connection can be set up under the precondition that the QoS is ensured. The determination is based on the status of cell
resources and the situation of Iub/Iur congestion. When the resources are insufficient, the HS-DSCH is switched to the DCH and only the DCH connection is set up. When the
resources are sufficient, the DCH is switched to the HS-DSCH. The implementation of this function requires the support of channel switching. For details, see Call Admission
Control Feature Parameter Description.
Access control allows the HSDPA UE to access an inter-frequency neighboring cell that has the same-coverage area as the source cell. The purpose is to achieve load balance
Page 8 of 69
between the cells and improve HSDPA user experience. This is HSDPA directed retry decision (DRD), an optional feature. For details, see Directed Retry Decision Feature

The DCH supports soft handover, and therefore downlink data can be concurrently sent out from all the cells in the active set in DCH transmission. In comparison, the HS-DSCH
does not support soft handover, and therefore downlink data can be sent out only from the HS-DSCH serving cell and inter-cell handover has to be performed through the change
of the serving cell. Therefore, HSDPA mobility management (WRFD-01061006 HSDPA Mobility Management) focuses on the change of the HS-DSCH serving cell.
For the UE with the HS-DSCH service, the best cell in the active set acts as the HS-DSCH serving cell. When the best cell changes, the UE disconnects the HS-DSCH from the
source cell and attempts to set up a new HS-DSCH connection with the new best cell. For details, see Handover Feature Parameter Description. By changing the HS-DSCH
switching threshold, you can modify the conditions for triggering the change of the best cell. Lowering this threshold can increase both the handover frequency and the sensitivity of
HS-DSCH switching to signal variations in the serving cell. Raising this threshold can reduce the handover frequency but may increase the probability of the HS-DSCH service
being discontinuous or even dropping on the cell edge. For the HS-DSCH service, Huawei supports inter-cell intra-frequency handover, inter-cell inter-frequency handover, and
inter-RAT handover.
Mobility management may trigger the switching from the HS-DSCH to the DCH. If the UE with the HS-DSCH service cannot set up the HS-DSCH connection with the target cell,
the channel switching function, together with mobility management, switches the HS-DSCH to the DCH. When the HS-DSCH connection is available, the channel switching
function switches the DCH back to the HS-DSCH. When the HSDPA user returns from the DCH cell to the HSDPA cell, the DCH is set up to ensure successful handover. A certain
period (ChannelRetryHoTimerLen(BSC6900,BSC6910)) later after the handover, the channel switching function switches the DCH to the HS-DSCH. For details, see Handover
Feature Parameter Description and section 3.4 Channel Switching.

After the HS-DSCH is introduced, the UE can stay in a new state, CELL_DCH (with HS-DSCH). Therefore, there are additional transitions between CELL_DCH (with HS-DSCH)
and CELL_FACH and transitions between CELL_DCH (with HS-DSCH) and CELL_DCH even when both the cell and the UE support the HS-DSCH, as shown in Figure 3-1.
Figure 3-1 UE state transition (WRFD-01061111 HSDPA State Transition)
Table 3-2 lists new state transition and new channel switching.
Table 3-2 New state transition and new channel switching
New State Transition
New Channel Switching
CELL_DCH (with HS-DSCH) <-> CELL_FACH HS-DSCH <-> FACH

CELL_DCH (with HS-DSCH) <-> CELL_DCH
HS-DSCH <-> DCH
Here, the switching between HS-DSCH and FACH can be triggered by traffic volume, which is similar to the switching between DCH and FACH. For details, see State Transition
Feature Parameter Description.
In addition, when the cell load is too high, load control may also trigger the switching from the HS-DSCH to the FACH to relieve congestion. For details, see Load Control Feature
As the HS-DSCH is introduced later, it is inevitable that some cells support the HS-DSCH but others do not. This is also the case with UEs. When a service is set up, the channel
switching function selects an appropriate bearer channel based on the cell capability and UE capability to ensure the QoS while efficiently using the cell resources. When the user
is moving, the channel switching function adjusts the channel type based on the UE capability to ensure service continuity while improving user experience.
Figure 3-2 Relationships between channel switching and other functions
Triggers for switching from the HS-DSCH to the DCH are as follows:
The HS-DSCH is selected during the service setup but neither the resources of the serving cell nor the resources of the inter-frequency same-coverage neighboring cell are
sufficient. In this case, the HS-DSCH is switched to the DCH. This function is achieved by means of non-periodic directed retry decision (DRD). For details about non-periodic
DRD, see Directed Retry Decision Feature Parameter Description.
The HS-DSCH serving cell changes. The UE attempts to set up a new HS-DSCH connection with the new best cell. In such a case, the possible scenarios are as follows:
If the new best cell does not support the HS-DSCH, the UE cannot set up the HS-DSCH connection. In this case, the HS-DSCH is switched to the DCH.
If the new best cell supports the HS-DSCH but a new HS-DSCH connection cannot be set up because the resources are insufficient, the DCH connection is set up and
the HS-DSCH is switched to this DCH.
For details, see Handover Feature Parameter Description.
The user moves from a cell supporting the DCH but not supporting the HS-DSCH to a cell supporting the HS-DSCH. In this case, the DCH connection is also set up because
the DCH supports soft handover, which can increase the handover success rate.
In one of the cases described previously, the DCH connection is set up in a cell supporting the HS-DSCH or in an inter-frequency same-coverage neighboring cell supporting the
HS-DSCH. Then, the DCH is switched to the HS-DSCH by either of the following mechanisms:
Channel switching based on timer

After the DCH connection is set up, this mechanism periodically attempts to switch the DCH to the HS-DSCH. This function is achieved by means of periodic DRD. For details
about periodic DRD, see Directed Retry Decision Feature Parameter Description.
Channel switching based on traffic volume
Page 9 of 69
When the traffic volume of the UE increases and the RNC receives a 4A event report, this mechanism attempts to switch the DCH to the HS-DSCH. For details on the 4A
event report, see State Transition Feature Parameter Description.
3.5 Load Control

When the cell is congested, load control selects some users (including HSDPA users) for congestion relief. The selection is based on the integrated priority, which considers the
allocation retention priority (ARP), traffic class (TC), traffic handling priority (THP), and bearer type. When the cell load is high, the basic congestion control selects some HSDPA
users for handover to an inter-frequency same-coverage neighboring cell or an inter-RAT neighboring cell with lower load. When the cell load is too high, the overload congestion
control selects some HSDPA BE services for the switching to a common channel or releases some HSDPA services. For details, see Load Control Feature Parameter Description.

Power resource management (WRFD-01061019 HSDPA Dynamic Power Allocation) determines the transmit power of the HS-PDSCH, HS-SCCH, and HS-DPCCH.
The downlink power resources of HSDPA can be dynamically allocated as follows:
1. The downlink power resources are first reserved for common physical channels and allocated to the DPCH. The remaining power resources are available for HSPA, including
HSUPA and HSDPA.
2. The HSPA power resources are first allocated to the HSUPA downlink control channels, including the E-AGCH, E-RGCH, and E-HICH. The remaining power resources are
available for HSDPA.
3. The HSDPA power resources are first allocated to the downlink control channel HS-SCCH. For details, see Power Control Feature Parameter Description. The remaining
power resources are allocated to the traffic channel HS-PDSCH.
For details on power resource allocation, see section 4.5 TFRC Selection.
Figure 3-3 shows the dynamic HSDPA power resource allocation.
Figure 3-3 Dynamic HSDPA power resource allocation
Every TTI, the NodeB detects the power usage of R99 channels to determine the power available for HSPA. To reserve the power for R99 power control itself, the power margin
PwrMgn needs to be set on the NodeB side. In addition, the power allocated to HSPA must not exceed the maximum permissible power HspaPower(BSC6900,BSC6910), which
can be set on the RNC side.
For details on uplink HS-DPCCH power control, see Power Control Feature Parameter Description.

Code resource management allocates code resources to the HS-SCCH and HS-PDSCH.
The NodeB supports HS-DSCH transmissions to multiple users in parallel in a TTI. If more than one HS-PDSCH code can be allocated by the NodeB, then code multiplexing can
be used to allocate the codes to multiple users to improve resource usage and system throughput.
3.7.1 HS-SCCH Code Resource Management

Each HS-SCCH uses an SF128 code. The number of HS-SCCHs determines the maximum number of HSDPA users that can be scheduled simultaneously in a TTI. Generally, the
number of HS-SCCHs depends on the traffic characteristics of the cell. The default number is 4, which is specified by the parameter HsScchCodeNum(BSC6900,BSC6910) on
the RNC side. If the default number is used, the HS-PDSCH can use only 14 SF16 codes. To enable the HS-PDSCH to use 15 SF16 codes, you are advised to configure 2 HSSCCHs.
3.7.2 HS-PDSCH Code Resource Management

This section describes the feature WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation and the feature WRFD-010631 Dynamic Code
Allocation Based on NodeB.
The transport channel HS-DSCH is mapped on one or several High-Speed Physical Downlink Shared Channels (HS-PDSCHs) which are simultaneously received by the UE. As
indicated in 3GPP specifications, there are up to 15 HS-PDSCHs per cell with the spreading factor fixed to 16.
The number of the HS-PDSCHs per NodeB is configurable and dependent on the license. The license specifies the maximum number of SF16 codes purchased by the operator.
The license works at the NodeB level, which means all cells under a NodeB share the license. The NodeB can dynamically allocate license codes to the HS-PDSCHs between
cells based on the actual requirements. The number of available HS-PDSCH codes for a cell is the number of license codes allocated by the NodeB or the number of HS-PDSCH
codes allocated by the function of HS-PDSCH code resource management, whichever is smaller.
The function of HS-PDSCH code resource management is used to share the cell code resources between DPCH and HS-PPDCH in a cell. As the DPCH and the HS-PDSCH
coexist in a cell, sharing the cell code resources between them is of critical importance in HSDPA code resource management.
The function of HS-PDSCH code resource management supports both RNC-level and NodeB-level code resource management. RNC-controlled static or dynamic code allocation
is enabled through the parameter AllocCodeMode(BSC6900,BSC6910). NodeB-controlled dynamic code allocation is enabled through the parameter DynCodeSw.
If the RNC-controlled static code allocation is used:

The number of reserved HS-PDSCH codes is specified by the cell-level parameter HsPdschCodeNum(BSC6900,BSC6910). Based on the reserved number, the RNC
reserves codes for the HS-PDSCH. The DPCH, HS-SCCH, and common channels use the other codes. The cell-level parameter HsPdschCodeNum(BSC6900,BSC6910)
can be set based on the traffic characteristics of the cell.
Figure 3-4 shows the RNC-controlled static code allocation.

Figure 3-4 RNC-controlled static code allocation
Page 10 of 69
If the RNC-controlled dynamic code allocation is used:
The minimum number of HS-PDSCH codes is specified by the cell-level parameter HsPdschMinCodeNum(BSC6900,BSC6910). The purpose of this setting is to prevent
too many DCH users from being admitted and to ensure the basic data transmission of the HS-PDSCH.
The maximum number of HS-PDSCH codes is specified by the cell-level parameter HsPdschMaxCodeNum(BSC6900,BSC6910). The purpose of this setting is to
prevent too many codes from being allocated for the HS-PDSCH and to prevent DCH users from preempting codes during admission.
The number of codes that can be shared between HS-PDSCH and DPCH is equal to the value of HsPdschMaxCodeNum(BSC6900,BSC6910) minus the value of
HsPdschMinCodeNum(BSC6900,BSC6910), as shown in Figure 3-5. When a code that can be shared is idle, it can be allocated to the HS-PDSCH if the idle code is
adjacent to the allocated HS-PDSCH codes.
Figure 3-5 RNC-controlled dynamic code allocation
If the NodeB-Controlled Dynamic Code Allocation is used:

Generally, the NodeB can use the HS-PDSCH codes only allocated by the RNC. The NodeB-controlled dynamic code allocation, however, allows the NodeB to temporarily
allocate idle codes to the HS-PDSCH.
Every TTI, the NodeB detects the SF16 codes that are not allocated to the HS-PDSCH. If such an SF16 code or any of its subcodes is allocated by the RNC to the DCH or a
common channel, this SF16 code is regarded as occupied. Otherwise, it is regarded as unoccupied. Therefore, the available HS-PDSCH codes include the codes reserved by
the RNC and the idle codes adjacent to the allocated HS-PDSCH codes.
If the setup of an RL requires a DPCH code that is already allocated by the NodeB to the HS-PDSCH, the NodeB releases this code and allocates it to an R99 user. Then, the
NodeB sends an NBAP message to the RNC, indicating that the RL is set up successfully.
Figure 3-6 NodeB-controlled dynamic code allocation
The dynamic code allocation controlled by the NodeB is more flexible than the dynamic code allocation controlled by the RNC. The dynamic code allocation controlled by the
NodeB shortens the code allocation duration and reduces the number of Iub signaling messages transmitted for code reallocation.
If NodeB-controlled dynamic code allocation is enabled, the RNC-controlled dynamic code allocation is disabled dynamically.
Huawei recommends the following code allocation modes, where the first mode is preferred:
Configure the RNC to use static code allocation and the NodeB to use dynamic code allocation.
If the NodeB does not support dynamic code allocation, configure the RNC to use dynamic code allocation.
If not all the NodeBs controlled by an RNC support dynamic code allocation, the RNC-controlled dynamic code allocation is recommended. In this case, the NodeB-controlled
dynamic code allocation can also be enabled for those supporting NodeBs.
3.7.3 Dynamic Code Tree Reshuffling

The HS-PDSCH can use only continuous SF16 codes, regardless of whether the RNC or NodeB controls the dynamic code allocation. By reallocating DPCH or F-DPCH codes,
the dynamic code tree reshuffling function can maximize the number of continuous SF16 codes available for the HS-PDSCH.
Dynamic code tree reshuffling takes effect only when the following conditions are met:
The cell is not in the basic congestion state that is triggered by code resource. For details about basic congestion state, see Load Control Feature Parameter Description.
The switch parameter CodeAdjForHsdpaSwitch(BSC6900,BSC6910) is set to ON. In this case, the RNC moves the codes occupied by R99 users leftward along the code
tree and thereby releases shared codes that are close to HS-PDSCH codes. Figure 3-7 shows how this works.
When the RNC-controlled dynamic code allocation or the NodeB-Controlled Dynamic Code Allocation is enabled, codes released by means of dynamic code tree reshuffling can
be used by the HS-PDSCH to improve throughput for HSDPA users.
Whether the F-DPCH codes can be reallocated through dynamic code tree reshuffling is determined by the parameter DlSfAdmAlgoSwitch(BSC6900,BSC6910):
FDPCH_SF_ALLOC_OPT_SWITCH in the MML command ADD UCELLALGOSWITCH
When dynamic code tree reshuffling takes effect, the RNC reshuffles the codes used by the DPCH/F-DPCH to provide more continuous SF16 codes for HSDPA through this
function. This function is described as follows:
Every time the codes used by the DPCH are changed, the RNC will choose an SF16 subtree that is not used by HS-PDSCH from right to left. The selected subtree must meet the
following conditions:
The selected subtree belongs to the code trees that can be shared between HS-PDSCH and DPCH.
The number of DPCHs and F-DPCHs on the selected subtree is smaller than or equal to the threshold specified by the parameter CodeAdjForHsdpaUserNumThd
(BSC6900,BSC6910).
The parameter CodeAdjForHsdpaUserNumThd(BSC6900,BSC6910) limits the number of users that can be reshuffled each time, to prevent too many users from being
reshuffled in a short time and therefore to avoid affecting user experience.
When the above conditions are met, the RNC will select this subtree for reshuffling and relocate the users to the positions where the codes are idle.
Figure 3-7 Dynamic code tree reshuffling
Page 11 of 69
4 User Plane
4.4 HARQ
4.5 TFRC Selection

HSDPA flow control (WRFD-01061010 HSDPA Flow Control) and congestion control are used to control the HSDPA data flow on the Iub and Iur interfaces. HSDPA data packets
are sent through the Iub interface to the NodeB and then through the Uu interface to the UE. Therefore, congestion may occur on the Uu, Iub, or Iur interface. Flow control is used
to relieve Uu congestion, and congestion control is used to relieve Iub/Iur congestion. The two types of control are implemented by the NodeB. HSDPA flow control and congestion
control are part of the HSDPA Iub frame protocol (3GPP TS 25.435). They are implemented for each MAC-hs queue through the Capacity Request message sent by the RNC and
the Capacity Allocation message sent by the NodeB.
Figure 4-1 shows the basic principles of flow control and congestion control.
Figure 4-1 Basic principles of Iub flow control and congestion control
4.1.1 Flow Control

For each MAC-hs queue, flow control calculates the pre-allocated Iub bandwidth based on the Uu transmission rate and the amount of data buffered in the NodeB. The Uu
transmission rate of the MAC-hs queue is determined by the scheduling algorithm. For each MAC-hs queue, if the Iub transmission rate is higher than the Uu transmission rate, the
data packets are buffered. Too much data buffered in the NodeB leads to transmission delay and even packet loss. Therefore, each MAC-hs queue should not have too much data
buffered in the NodeB. On the other hand, it should keep a certain amount of data to avoid wasting the Uu resources due to no data to transmit.
The flow control procedure is as follows:
1. The NodeB measures the buffered data amount of each MAC-hs queue and the average Uu transmission rate.
2. The NodeB estimates the buffering time based on the measurements.
3. The NodeB adjusts the Iub bandwidth pre-allocated to the MAC-hs queue.
The pre-allocated Iub bandwidth is adjusted as follows:
If the buffering time is too short, you can infer that the RNC slows down the data transmission, that is, the Iub transmission rate is lower than the Uu transmission rate. In this
case, the pre-allocated Iub bandwidth is adjusted to a value greater than the average Uu transmission rate.
If the buffering time is appropriate, the pre-allocated Iub bandwidth is adjusted to the average Uu transmission rate.
If the buffering time is too long, the pre-allocated Iub bandwidth is adjusted to a value smaller than the average Uu transmission rate.
For details on flow control, see Transmission Resource Management Feature Parameter Description.
4.1.2 Congestion Control

The Iub bandwidth may be lower than the Uu bandwidth. If the RNC uses the Iub bandwidth pre-allocated to each MAC-hs queue, the Iub bandwidth for HSDPA is insufficient. This
may lead to congestion and even packet loss.
The amount of data to be transmitted is sent by the RNC to each MAC-hs queue through the Capacity Request message. Based on this amount and the total Iub bandwidth
available for HSDPA, the congestion control function adjusts the bandwidth pre-allocated to each MAC-hs queue. Therefore, congestion control ensures that the total bandwidth
actually allocated to all the MAC-hs queues is not higher than the total available Iub bandwidth.
The total Iub bandwidth available for HSDPA depends on the variations in HSDPA packet delay and the situation of packet loss. HSDPA shares the bandwidth with the DCH and
control signaling, and the DCH and control signaling has higher priorities than HSDPA. Therefore, when the HSDPA packet delay or packet loss increases, you can infer that the
Page 12 of 69
number of DCHs or the amount of control signaling increases. In such a case, the bandwidth available for HSDPA decreases and the bandwidth actually allocated for HSDPA
decreases.
For details on congestion control, see Transmission Resource Management Feature Parameter Description.
NOTE:
For the Iur interface, flow control and congestion control are also applied. The control principles and processing procedures are the same as those for the Iub interface.

4.2.1 Impact on the RLC Entity
One of the main purposes of HSDPA is to reduce latency by handling retransmissions at NodeB level. Retransmissions, however, may still be triggered at the RLC layer of the
RNC under the following circumstances:
The NodeB misinterprets an NACK sent by the UE.
The number of HARQ retransmissions exceeds the maximum permissible number.
The data buffered in the NodeB is lost when the HS-DSCH serving cell changes.
Therefore, HARQ retransmission cannot totally replace RLC retransmission, which is described in 3GPP TS 25.322. For services with high requirements for data transmission
reliability, Huawei recommends that the RLC acknowledged mode (AM) also be used to ensure correct transmission on the Uu interface even when the services such as the BE
service are carried on HSDPA channels.
Before the introduction of HSDPA, the size of an RLC PDU is usually 336 bits, where 320 bits are for the payload and 16 bits for the RLC header. Without additional overhead, the
MAC PDU is of the same size as the RLC PDU. According to the 3GPP specifications, a maximum of 2,047 RLC PDUs can be transmitted within an RLC window, and the RTT at
the RLC layer is about 100 ms (50 TTIs).
In this condition, the maximum peak rate can only be 336 bits x (2047/50)/2 ms = 6.88 Mbit/s. To reach higher rates, an RLC PDU of 656 bits is introduced, where 640 bits are for
the payload and 16 bits for the RLC header. The RLC PDU size can be set for each typical service. For high-speed services, the size is set to 656 bits by default.
In addition, the RLC PDU size is fixed to 656 bits, and a transport block of 27,952 bits can contain a maximum of 42 PDUs. Therefore, the maximum RLC payload rate is (656 bits 16 bits) x 42/2 ms = 13.44 Mbit/s.
For example, 3GPP specifies that the UE of category 10 can use a maximum of 15 codes and receive a transport block with a maximum of 27,952 bits. For details, see 3GPP TS
25.306. Therefore, the theoretical peak rate is 27952 bits/2 ms = 13.976 Mbit/s. In practice, the radio channel quality, retransmission probability, and available power also need to
be considered. Therefore, the UE of category 10 cannot reach 13.44 Mbit/s at the RLC layer in most tests.
A fixed RLC PDU size results in lower transmission efficiency due to unnecessary filler data and redundant RLC PDU headers. Another reason why a fixed RLC PDU size is not
desirable is that high-speed transmission requires a large RLC PDU size required whereas edge coverage requires a small RLC PDU size. Downlink layer 2 enhancement can be
used to address these problems.
With downlink layer 2 enhancement, the RLC AM entity supports a variable PDU size, and the RLC layer does not segment upper-layer packets whose sizes are smaller than the
maximum RLC PDU size. The RLC layer can flexibly adapt to traffic variations and reduce the overheads caused by RLC PDU headers. For details about downlink layer 2
enhancement, see HSPA Evolution Feature Parameter Description.
4.2.2 Impact on the MAC-d Entity

The MAC-d functionality is unchanged after the introduction of HSDPA. The HS-DSCH bearers are mapped onto MAC-d flows on the Iub/Iur interface. Each MAC-d flow has its
own priority queue.

This section describes the feature WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).
With the limited Uu resources for HSDPA in a cell, the user expects to maximize the service rate while the telecom operator expects to maximize the system capacity. MAC-hs
scheduling is used to coordinate the Uu resources, user experience, and system capacity. It is implemented at the NodeB MAC-hs.
The scheduling algorithm consists of two steps. At first, the algorithm determines which initial transmission queues or retransmission processes can be put into the candidate set
for scheduling. Then, the algorithm calculates their priorities based on factors such as the CQI, user fairness, and differentiated services. If the algorithm is weighted more towards
the channel quality of the UE, the HSDPA cell can have a higher capacity but user fairness and differentiated services may be affected. If the algorithm is weighted more towards
user fairness and differentiated services, the system capacity may be affected.
Huawei provides five scheduling algorithms: maximum C/I (MAXCI), round-robin (RR), proportional fair (PF), Enhanced Proportional Fair (EPF), and EPF based on UE location
(EPF_LOC). The EPF and EPF_LOC are optional.
4.3.1 Determining the Candidate Set

The candidate for scheduling contains new data packets (initial transmission queues) or data packets to be retransmitted (retransmission processes), with the following exceptions:
If the UE starts the compressed mode, its data cannot be put into the candidate set during the GAP.
If the UE category requires the UE to wait for several TTIs before it can be scheduled again, its data cannot be put into the candidate set in this period. The UE of category 1
or 2 needs to wait for 3 TTIs, and the UE of category 3, 4, and 11 must wait for 2 TTIs.
If the number of retransmissions of a data packet reaches or exceeds the maximum number, the data of this UE cannot be put into the candidate set. The data should be
discarded.
Huawei supports that the maximum number of retransmissions is set on a service basis:
MaxNonConverHarqRt: the maximum number of non-conversational service retransmissions in the CELL_DCH state
MaxEfachHarqRt: The UE in the enhanced CELL_FACH state does not report ACK, NACK, or CQI in the uplink. The HARQ processes of the UE use the blind
retransmission mechanism. The maximum number of retransmissions for the UE in Enhanced CELL_FACH Operation is specified by this parameter.
The CQI reported by the UE is 0.
There is no data in the Mac-ehs or Mac-hs queue for the UE.
The uplink channel quality of UEs is poor and the uplink channels of these UEs are carrying PS conversational services or SRBs.
NOTE:
The MAC-hs can schedule data packets and select Transport Format and Resource Combine (TFRC) entities for UEs whose uplink channel quality is poor and CQI is not 0 when
the following conditions are met:
The MAC-hs queue contains the data packets of these UEs and the data size is not 0.
The scheduling time does not fall into the GAP.
For new data packets, the MAC-hs calculates the scheduling priority for the follow-up data packet scheduling and TFRC entity selection based on the principle that applies to a CQI
of 12 (CQI adjustments are not performed). For data packets to be retransmitted, the MAC-hs schedules these data packets and selects TFRC entities in the same way as it
operates on UEs with good uplink channel quality.
4.3.2 Calculating Scheduling Priorities

Five algorithms are available for calculating the priorities of data packets in the candidate set. The scheduling policies vary according to the algorithms for calculating the priorities
of data packets. The algorithm to be used is specified by the parameter SM on the NodeB LMT.
Comparison of Five Algorithms

Table 4-1 lists the factors considered in the five scheduling algorithms.
Table 4-1 Factors considered in the five scheduling algorithms
Factor
MAXCI
RR
PF
EPF
EPF_LOC
Page 13 of 69
Service type
No
No
No
Yes
Yes
Initial transmission or
retransmission
Yes
Yes
Yes
Yes
Yes
Maximum power
No
No
No
Yes
Yes
Waiting time
No
Yes
No
Yes
Yes
CQI
Yes
No
Yes
Yes
Yes
Actual throughput
No
No
Yes
Yes
Yes
SPI
No
No
No
Yes
Yes
SPI Weight
No
No
No
Yes
Yes
GBR
No
No
No
Yes
Yes
HBR
No
No
No
Yes
Yes
UE Location
No
No
No
No
Yes
Table 4-2 lists the effects of the five scheduling algorithms.

Table 4-2 Effects of the five scheduling algorithms
Item
MAXCI
RR
PF
EPF
EPF_LOC
System capacity
Highest
High
Higher
Higher
Higher
User fairness
Not guaranteed
Best
Guaranteed
Guaranteed
Not guaranteed
Differentiated services
Not guaranteed
Not guaranteed
Not guaranteed
Guaranteed
Guaranteed
Real-time services
Not guaranteed
Not guaranteed
Not guaranteed
Guaranteed
Guaranteed
MAXCI Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues. The retransmission processes are sorted in first-in first-out (FIFO) mode.
The initial transmission queues are sorted in the CQI order. A higher CQI means a higher data priority.
The MAXCI algorithm aims to maximize the system capacity but cannot ensure user fairness and differentiated services.
The UE estimates the CQI based on the assumption that the transmit power of the HS-PDSCH on the network side is as follows:
where
PCPICH is the transmit power of the CPICH.
is the measurement power offset (MPO). It is specified by the parameter HsPdschMPOConstEnum(BSC6900,BSC6910) on the RNC side and sent to the NodeB and
UE.
is the reference power adjustment. It is set to 0 in most cases. For details, see 3GPP TS 25.214.
RR Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues. The retransmission processes are sorted in FIFO mode. The initial
transmission queues are sorted in the order of the waiting time in the MAC-hs queue. A longer waiting time means a higher data priority.
The RR algorithm aims to ensure user fairness but cannot provide differentiated services. Not considering the CQI reported by the UE leads to lower system capacity.
PF Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues. The retransmission processes are sorted in FIFO mode. The initial
transmission queues are sorted in the order of R/r. Here, R represents the throughput corresponding to the CQI reported by the UE, and r represents the throughput achieved by
the UE. A greater R/r value means a higher data priority.
The PF algorithm aims to make a tradeoff between system capacity and user fairness. It provides the user with an average throughput that is proportional to the actual channel
quality. The system capacity provided by PF is between the system capacity provided by RR and that provided by MAXCI.
EPF Algorithm
The EPF algorithm (WRFD-01061103 Scheduling based on EPF and GBR) is an enhanced algorithm developed based on the PF algorithm. The EPF algorithm defines more
priorities than the PF algorithm to better meet the QoS requirements of different services. The EPF algorithm can meet the requirements of telecom operators related to user
fairness and differentiated services and also provide a high system capacity.
The EPF algorithm follows certain criteria to prioritize queues:
Service types are the first to be considered. They are prioritized in a sequence: SRB and IMS > voice services > streaming services > BE services.
Different services of the same type are prioritized as follows:
Retransmission queues are prioritized over initial transmission queues.
Guaranteed bit rate (GBR) queues that have not arrived are prioritized over GBR queues that have already arrived.
Queues with high SPI weights are prioritized over those with low SPI weights.
High bit rate (HBR) queues that have not arrived are prioritized over HBR queues that have already arrived.
User fairness is implemented in EPF as follows:
EFP algorithm guarantees the user fairness in the same way as that PF algorithm. HBR and Resource Limit is used in EPF to limit the use of single users and improve
fairness.
HBR is used to determine the throughput expected by the user based on a study on user experience.
When the rate for a user reaches the HBR, the scheduling probability for the user is decreased. The HBR is specified by the parameter HappyBR(BSC6900,BSC6910)
on the RNC side.
Resource Limit is used to prevent the users in areas with poor coverage from consuming too many cell resources so that there is no decrease in system capacity.
When the resource limitation switch (RscLmSw) is on, the algorithm allocates the lowest priority to a queue whose power consumption exceeds the threshold. If the
power available to the queue is limited, the queue's priority is always considered as meeting the GBR. The ratio of the maximum available power of a queue to the total
power of the cell is specified by the NodeB MML command SET ULOCELLRSCLMTPARA.
Differentiated service is implemented in EPF as follows:
Differentiated services are provided based on SPI and SPI weights.
SPI(BSC6900,BSC6910) is a parameter specified based on service types and users priorities.
Page 14 of 69
SPIweight(BSC6900,BSC6910) can be specified according to the SPI to provide differentiated services.
The SPI weight affects the calculation of queue priorities. It is used to quantify the differentiated services. If resource is insufficient, the proportion of SPI weights determines
the approximate proportion of rates among users. For example, for three throughput-sensitive service users with the same channel quality, the same GBR and the proportion
of SPI weights is 100:50:30, the proportion of actual rates is close to 100:50:30.
For details on the parameters related to QoS management, such as the GBR, SPI, SPI weight, and HBR, see QoS Management Feature Parameter Description.
EPF_LOC Algorithm
UEs' location in a cell can be defined as a near, middle, or far distance from the NodeB. HSDPA UEs closer to the NodeB have better channel environments and report higher
CQIs, as shown in Figure 4-2.
Figure 4-2 UE locations and CQIs
With the EPF/PF algorithm, UEs that have the same SPI weight value but are at different distances from the NodeB have roughly equal scheduling opportunities.
The EPF_LOC algorithm (WRFD-140221 HSDPA Scheduling based on UE Location) builds on the EPF algorithm and considers UE locations as HSDPA scheduling weights.
While ensuring GBRs for all UEs, the EPF_LOC algorithm gives more scheduling opportunities to UEs that are close to the NodeB in order to improve throughput for these UEs.
Since these UEs can obtain larger transmission blocks than UEs farther from the NodeB, the overall throughput of the cell is improved.
CQIs indirectly reflect UE locations. A CQI reported by a UE implies the UE's location, a near, middle, or far distance either between the UE and the NodeB, or between the UEs
within a cell. Assuming that there are two UEs far from the NodeB and the CQIs reported by them are 15 and 13, respectively, the UE that reports the CQI 15 has more scheduling
opportunities and higher downlink throughput.
NOTE:
The PF and EPF algorithms consider the value R/r, where R is the throughput corresponding to the CQI reported by the UE. The EPF_LOC algorithm is based on the EPF
algorithm. In addition to R/r, the EPF_LOC algorithm also considers UE locations indicated by CQIs.
If a larger value is set for the LOCWEIGHT parameter, UE locations weigh more in the EPF_LOC algorithm. Theoretically, this results in a higher downlink throughput of the cell
and greater differentiation between UEs at different distances from the NodeB. UEs closer to the NodeB have more scheduling opportunities and higher throughput, which is the
other way around for UEs farther from the NodeB.
UEs closer to the NodeB have more scheduling opportunities and therefore higher throughput. This improves the cell throughput.
UEs farther from the NodeB have fewer scheduling opportunities and therefore lower throughput.
To ensure user experience at cell edges, it is recommended that GBRs be configured for all BE services. To configure GBRs, run the SET UUSERGBR command on the RNC.
NOTE:
The LOCWeight and SPIWeight(BSC6900,BSC6910) parameters simultaneously affect HSDPA scheduling weights. UEs far from the NodeB will experience decreased downlink
rates after this feature is activated. If high rates need to be ensured for gold users, it is recommended that higher GBRs or SPI weight values be set for gold users.
The EPF_LOC algorithm gives more scheduling opportunities to UEs closer to the NodeB and increases the downlink overall throughput of the cell. Cell throughput gains relate to
UEs' CQIs. With EPF_LOC algorithm, HSDPA UEs at cell edges have fewer scheduling opportunities and lower throughput. If GBRs are not configured for BE services, HSDPA
UEs at cell edges may have to wait a long time before they have scheduling opportunities. As a result, traffic radio bearers (TRBs) are more likely to reset and the call drop rate
increases. The magnitude of this impact depends on factors such as UE location distribution and service distribution in the cell. It is recommended that GBRs be configured for BE
services to ensure network performance.
4.3.3 Time and HS-PDSCH Codes Multiplex

This section describes the feature WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
After scheduling, HSDPA users will be allocated to different time and code. Figure 4-3 shows the time division and code division over the air interface for HSDPA users in one cell.
Figure 4-3 HSDPA scheduling based on time division and code division
The feature of time and HS-PDSCH codes multiplex enables the allocation of different codes in the same TTI to different users or the time division multiplexing of the same code in
different TTIs for different users to provide the utilization of code resources and the system throughput.
The parallel data transmission of multiple users over HS-DSCH requires more HS-SCCH codes and HS-PDSCH codes within a single TTI. Code multiplexing is adopted and is
found useful when the NodeB has more HS-PDSCH codes for allocation than those supported by the UE. For instance, the UE supports 5 codes and the NodeB has 10 codes
available in a single TTI. The code multiplexing can increase the resource utilization and system throughput.
4.4 HARQ
The main purpose of introducing HARQ is to reduce the retransmission delay and improve the retransmission efficiency. HARQ enables fast retransmission at the physical layer.
Before decoding, the UE combines the retransmitted data and the previously received data, making full use of the data transmitted each time. In addition, HARQ can fine-tune the
effective rate to compensate for the errors made by TFRC section.
4.4.1 HARQ Retransmission Principles

The HARQ process of HSDPA involves only the NodeB and the UE, without involving the RNC. After receiving a MAC-hs PDU sent by the NodeB, the UE performs a CRC check
and reports an ACK or NACK on the HS-DPCCH to the NodeB:
Page 15 of 69
If the UE reports an ACK, the NodeB transmits the next new data.
If the UE reports an NACK, the NodeB retransmits the original data. After receiving the data, the UE performs soft combining of this data and the data received before,
decodes the combined data, and then reports an ACK or NACK to the NodeB.
RLC retransmission on the DCH involves the RNC, and therefore the RTT is relatively long. In comparison, HARQ involves only the physical layer and MAC-hs of the NodeB and
those of the UE, and therefore the RTT is reduced to only 6 TTIs (12 ms).
After a transmission, the HARQ process must wait at least 10 ms before it can transmit the next new data or retransmit the original data. Therefore, to improve transmission
efficiency, other HARQ processes can transmit data during the waiting time. A maximum of six HARQ processes can be configured in each of the NodeB HARQ entity and the UE
HARQ entity. Note that not all UE categories support six HARQ processes. For example, the UEs of some categories can receive data every one or two TTIs. Therefore, only two
or three HARQ processes can be configured. The RAN can automatically choose the most appropriate configuration based on UE capability.
Figure 4-4 HARQ retransmission principles
4.4.2 Soft Combining During HARQ

Before decoding a MAC-hs PDU, the UE performs soft combining of all the data received before to improve the utilization of Uu resources and therefore increase the cell capacity.
The size of the UE buffer determines the number of coded bits or the size of transport blocks.
For HARQ retransmission between the NodeB and the UE, two combining strategies are available. They are Chase Combining (CC) and Incremental Redundancy (IR). In the case
of CC, all retransmitted data is the same as previously transmitted data. In the case of IR, the retransmitted data may be different from the previously transmitted data. In
comparison, IR has a higher gain than CC but requires more buffer space. CC can be regarded as a special case of IR. The IR strategy is hard-coded in Huawei RAN.
4.4.3 Preamble and Postamble

If the HS-SCCH is received, the UE checks whether the HS-PDSCH is also correctly received and then reports an ACK or NACK in the first slot of the HS-DPCCH subframe. If the
HS-SCCH is erroneously received, the UE does not report any information in the first slot of the HS-DPCCH subframe. This type of transmission is called DTX. In the case of high
interference, the NodeB may demodulate DTX as ACK by mistake when demodulating the HS-DPCCH. Therefore, the lost data blocks cannot be retransmitted through HARQ
retransmission, and the reception can be ensured only through RLC retransmission. To meet the requirement of the 3GPP specifications for a low DTX misjudgment probability,
more power has to be allocated for HS-DPCCH ACK/NACK.
To solve this problem, 3GPP TS 25.214 introduces preamble and postamble (WRFD-01061113 HS-DPCCH Preamble Support). When the NodeB demodulates an HS-DPCCH
ACK/NACK, it considers the subframe prior to and the subframe next to the HS-DPCCH subframe in addition to the HS-DPCCH subframe itself. Therefore, for a certain DTX
misjudgment probability, the introduction of preamble and postamble reduces the power required by ACK/NACK, lower the downlink load level, and increase the uplink capacity.
Figure 4-5 HS-DPCCH preamble and postamble
4.5 TFRC Selection

The TFRC selection algorithm handles the MAC-hs queues in descending order of their priorities determined by the scheduler. In each TTI, the TFRC entity of a cell selects one or
multiple queues and does the following:
Determining the amount of data that can be transmitted by the queue or queues
Determining the modulation scheme of the queue or queues
Allocating appropriate power and channelization codes to the queue or queues
The basic procedure for the TFRC selection algorithm is as follows:

1. Based on the CQI reported by the UE, available power, and available channelization codes, the algorithm searches a CQI mapping table for the TBSmax, that is, the
maximum MAC-hs transport block size (TBS). Note that the available power for every HSDPA user is restricted by MXPWRPHUSR.
2. Based on the TBSmax and the amount of data buffered in the queue, the algorithm determines the most appropriate MAC-hs TBS (TBSused).
If the data buffered in the MAC-hs queue is enough to fill the space for carrying data in a transport block with the TBSmax, then the TBSmax is taken as the TBS to be used
(TBSused). The TBSmax, however, may be much larger than the data buffered in the MAC-hs queue. If this TBS is used, too many padding bits reduce the spectrum
efficiency. To solve this problem, the algorithm searches the CQI mapping table backward for the CQI or the number of codes to obtain the most appropriate TBS and the
corresponding modulation scheme. This TBS should be the smallest one in the TBS set that can carry the buffered data. The power and code resources determined through
backward searching are taken as the ones for allocation.
Page 16 of 69
3. Based on the TBSused, the algorithm determines the most appropriate power, codes, and modulation scheme.
Huawei supports three backward-searching methods, which are specified by the parameter RscAllocM on the NodeB side:
If the parameter is set to Code_Pri, the TFRC algorithm prefers the use of codes. Under the precondition that the transport block with the TBS is large enough to carry the
buffered data, the algorithm first reduces the power. If the corresponding CQI decreases to the smallest one but the precondition is still met, the algorithm attempts to reduce
the number of codes. This setting is applicable the outdoor macro base station with limited power.
If the parameter is set to Power_Pri, the TFRC algorithm prefers the use of power. Under the precondition that the transport block with the TBS is large enough to carry the
buffered data, the algorithm first reduces the number of codes. If the number of codes decreases to 1 but the precondition is still met, the algorithm attempts to reduce the
power. This setting is applicable to indoor application with limited codes.
If the parameter is set to PowerCode_Bal, the TFRC algorithm balances the use of power and the use of codes. Under the precondition that the transport block with the TBS
is large enough to carry the buffered data, the algorithm reduces the power and codes in a balanced mode. This setting protects the codes or power from being used up,
improving the resource usage and increasing the cell capacity.
Figure 4-6 shows the backward-searching methods used when the parameter is set to Code_Pri or Power_Pri.
Figure 4-6 Backward-searching methods used when the parameter is set to Code_Pri or Power_Pri
Figure 4-7 shows the backward-searching methods used when the parameter is set to PowerCode_Bal.
Figure 4-7 Backward-searching methods used when the parameter is set to PowerCode_Bal

When only a small amount of data is buffered in the MAC-hs queue, the TFRC selection algorithm searches the CQI mapping table backward for the CQI or the number of codes to
obtain the most appropriate TBS. This TBS should be the smallest one in the TBS set that can carry the buffered data. Under this circumstance, the cell has a certain number of
remaining power resources. Full utilization of these power resources helps further reduce the downlink BLER and improve user experience.
The HSDPA remaining power appending algorithm helps fully utilize the remaining power resources. This algorithm appends certain power to the HS-PDSCH power calculated by
the TFRC selection algorithm if the last queue in a TTI carries streaming, interactive, or background data of a UE in CELL_DCH state (including initial transmission and
retransmission). After the introduction of the HSDPA remaining power appending algorithm, the NodeB parameter EXTRAPOWER is added to the SET ULOCELLMACHSPARA
command for specifying the maximum amount of power that can be allocated to HS-PDSCH power from the remaining power resources in the cell in question. This parameter is in
units of 0.25 dB. The value of this parameter must be equal to or less than the cell remaining power in a TTI.
With the increase in downlink power, the downlink load is also increased. When the downlink load becomes heavy, network KPIs are deteriorated. Therefore, the EXTRAPOWER
parameter cannot be set to a too large value.
Before enabling the HSDPA remaining power appending algorithm, ensure that HSDPA has been enabled on the network and that UEs support HSDPA.
NOTE:
When the EXTRAPOWER parameter is set to 0, the HSDPA remaining power appending algorithm does not take effect.
When the CQI adjustment based on a fixed BLER target algorithm is enabled on the NodeB, the HSDPA remaining power appending algorithm does not take effect. IBLER stands
for initial block error rate.

This section describes the feature WRFD-030010 CQI Adjustment Based on Dynamic BLER Target.
Overview
The CQI measures the channel conditions of a UE and is reported from the UE to the NodeB. Without this feature, the NodeB determines an appropriate TBS based on the
reported CQI, system resources, and the TFRC policy. If the reported CQI and related conditions remain the same, the NodeB does not change the TBS because it does not
consider the ever-changing radio environments.
The constant changes in radio environments, caused by multipath effects and UE mobility, lead to fluctuating channel quality. Under these circumstances, choosing a TBS based
on the reported CQI makes it difficult to always achieve the optimum downlink throughput.
Page 17 of 69
With the feature CQI adjustment based on dynamic BLER target, the NodeB monitors the channel quality fluctuations for HSDPA users in a cell in real time and dynamically
selects a proper BLER target based on the monitoring result. The NodeB then uses the BLER target to adjust the CQI reported by the UE. Based on the adjusted CQI, the NodeB
determines an appropriate TBS to achieve higher downlink throughput for HSDPA users and higher cell throughput.
NOTE:
The BLER described in this section refers to the SBLER at the MAC-(e)hs layer and reflects the average block error rate at the MAC layer. Accordingly, the BLER target described
in this section refers to the SBLER target at the MAC-(e)hs layer.
The required BLER target may be high in some environments; therefore this feature is not suitable for networks that limit the BLER target.
This feature requires that both the network and UE support HSDPA. This feature is applicable to all HSDPA terminals except for the terminals that are configured with MIMO.
Different terminals may have different performance for the same TB size. Some terminals may have greater BLERs. This feature adjusts the TB size for terminals based on data
transmission performance to achieve optimized performance.
This feature can be enabled by selecting the CQI_ADJ_BY_DYN_BLER check box under the CQIADJALGOFNONCON parameter.
CQI Adjustment Process

CQI adjustment based on dynamic BLER target is performed in each TTI. The following describes the adjustment process:
1. Based on the CQI reported by the UE, the NodeB checks the actual radio environment, which is affected by multipath effects and UE mobility.
2. Based on the actual radio environment and channel quality of the UE, the NodeB obtains an optimum BLER target, which helps to achieve the highest possible throughput for
the UE.
3. Based on the ACK, NACK, or DTX indication from the UE in the current TTI and on the optimum BLER target, the NodeB calculates the CQI offset, which can be a positive or
negative number. The NodeB then uses the CQI offset to adjust the CQI.
4. Based on the adjusted CQI, the NodeB selects an appropriate TBS by using the TFRC algorithm.

After a UE reports a CQI to the NodeB, the channel quality for the UE may change before the NodeB schedules this UE's data packets and selects TFRC entities for this UE. Such
changes are likely to occur in the following scenarios:
Scenario 1: The UE is engaged in initial HSDPA data transmission.
Scenario 2: The UE is processing burst services, for example, the UE is browsing web sites, sending heartbeat packets, microblogging, or using the QQ application.
If the NodeB uses the CQI that is reported by the UE when the UE does not process any data, the NodeB regards that the interference between channels is not strong. When the
UE starts processing data, the BLER may be high, prolonging the delay and affecting the burst service throughput.
The BLER Optimization for HSDPA Burst Services function calculates the interference of a UE when the UE reports a CQI to the NodeB and calculates the interference when the
UE starts data transmission. Then, this function works out the interference difference in the two scenarios. Based on the difference, this function adjusts the CQI. By doing this, the
NodeB can use an appropriate CQI when the UE is engaged in initial HSDPA data transmission or is processing burst services. This helps reduce the BLER and increase burst
service throughput.
The BLER Optimization for HSDPA Burst Services function is controlled by the BURSTBLEROPTSW parameter in the SET ULOCELLMACHSPARA command.
To use this function, the target network must support HSDPA and some UEs are HSDPA-capable. This function takes effect on all HSDPA-capable UEs.

QPSK and 16QAM
The HS-PDSCH is used to carry the HS-DSCH data. HS-PDSCH can use QPSK (WRFD-01061017 QPSK Modulation) or 16QAM (WRFD-010629 DL 16QAM Modulation)
modulation symbols.
When the UE is in the unfavorable radio environment, the transmission can adopt the low-order QPSK modulation mode and small transport blocks to ensure communication
quality.
When the UE is in the favorable radio environment, the transmission can adopt the high-order 16QAM modulation scheme and large transport blocks to reach a high peak
rate.
QPSK modulation is a basic downlink data modulation function that is used after HSDPA is introduced.
Compared with the QPSK modulation scheme, the 16QAM modulation scheme is a higher-order downlink data modulation scheme. This feature enables the peak rate on the Uu
interface to reach 14.4 Mbit/s.
64QAM
3GPP R5 introduces 16QAM to increase the peak rate per user and expands the system capacity, whereas 64QAM introduced in 3GPP R7 protocols is a further enhancement of
16QAM.
With downlink 64QAM, a higher-order modulation scheme than 16QAM can be used when the channel is of higher quality. Theoretically, 64QAM supports a peak data rate of 21
Mbit/s and at the same time increases the average throughput of the system. Simulation shows that compared with 16QAM, 64QAM can increase the average throughput by 7%
and 16% respectively in macro cell and in micro cell, if the UEs in the cells use the type 3 receivers.
The 3GPP R7 protocols define the categories of the UEs that support 64QAM, and add the information elements (IEs) that support 64QAM in the reporting of local cell capability.
The RNC determines whether the RL between the NodeB and the UE supports 64QAM according to the local cell capability reported by the NodeB and the UE capability. If the RL
supports 64QAM, the MAC-hs scheduler of the NodeB determines every 2 ms whether to use 64QAM according to the following aspects:
Channel Quality Indicator (CQI) reported by the UE
HS-PDSCH code resources and power resources of the NodeB
Compared with the 16QAM modulation scheme, the 64QAM modulation scheme is a higher-order downlink data modulation scheme. This feature enables the peak rate on the Uu
interface to reach 21 Mbit/s.
5 QoS Management and Management over Differentiated Services

5.1 QoS Management
5.1 QoS Management

The goal of service-oriented QoS management is to improve user experience by reducing the service delay and BLER and by increasing the service rate and continuity. The
requirements for QoS vary according to the type of service:
The conversational service (including the CS voice and VoIP) has a relatively high requirement for service delay and a certain requirement for BLER.
The streaming service has a requirement for guaranteed bit rate (GBR).
The FTP service has a high requirement for BLER and error-free transmission. In addition, this service requires higher service rates to provide better user experience.
The HTTP service has a high requirement for error-free transmission and a certain requirement for response delay. In addition, this service requires shorter delay to provide
better user experience.
HSDPA QoS management is implemented by related HSDPA functions. The following table lists the relationships between HSDPA functions and QoS indicators.
Table 5-1 Relationships between HSDPA functions and QoS indicators
Function
Service Connectivity
Mobility management
Page 18 of 69
Service Delay
Service Rate
HSDPA bearer mapping
Load control
RLC retransmission
Flow control
Congestion control
HARQ
MAC-hs scheduling
BLER
TFRC selection
These relationships between HSDPA functions and QoS indicators are described as follows:
Mobility management
Service continuity is implemented by mobility management.
For details, see section 3.3 Mobility Management and Handover Feature Parameter Description.
Bearer mapping
HSDPA bearers increase the service rate greatly and reduce the service delay.
For details, see section 3.1 Bearer Mapping.
Load control
The network resources are limited. Therefore, when a large number of users attempt to access the network, the access control function is required to control the access to
ensure the QoS of the admitted users.
The network resources consumed by the admitted users vary with the changed channel qualities, which may lead to network congestion. To relieve congestion, the overload
control function is required to ensure the QoS of most users.
For details on load control, see Load Control Feature Parameter Description.
RLC retransmission and HARQ

To achieve error-free transmission and improve transmission efficiency, HSDPA introduces HARQ at the physical layer. HARQ, however, cannot completely ensure error-free
transmission. Therefore, it should work with RLC retransmission and TCP retransmission.
For details, see sections 4.2 Impact of HSDPA on the RLC and MAC-d Entities and 4.4 HARQ.
Flow control and congestion control

By allocating appropriate Iub bandwidth to users, the flow control function reduces the transmission time. Therefore, it prevents too much data from waiting in the buffer at the
MAC-hs and avoids unnecessary RLC retransmissions. In addition, it protects service data from overflowing from the buffer at the MAC-hs.
Through congestion detection and congestion control, the congestion control function reduces the packet loss probability.
For details, see section 4.1 Flow Control and Congestion Control.
MAC-hs scheduling
Based on the waiting time, achieved service rate, and GBR, the MAC-hs scheduling function sorts the users to meet the requirements for transmission delay and transmission
rate on the Uu interface. For details, see section 4.3 MAC-hs Scheduling.
TFRC selection
Based on the available power, available codes, actual channel quality, and actual data amount, the TFRC selection function selects appropriate transport blocks and modulation
schemes to increase data rates. For details, see section 4.5 TFRC Selection.

Different services have different service types, and different users have different priorities. During resource allocation, differentiated services are provided. Differentiated services
for HSDPA users are as follows:
Differentiated services based on service types
Differentiated services based on user priorities
To further quantify the effect of Diff-Serv management, differentiated services based on SPI weights (WRFD-020806 Differentiated Service Based on SPI Weight) are
introduced.
For details, see Differentiated HSPA Service Feature Parameter Description.
6 Related Features
None

None

None

This feature depends on the following features:

None

None
Page 19 of 69


None

None

This feature depends on the feature WRFD-010610 HSDPA Introduction Package.

None

None

WRFD-010610HSDPA Introduction Package
WRFD-010611 HSDPA Enhanced Package

None

None
7 Network Impact
After activating HSDPA Introduction Package, the downlink cell throughput, downlink cell capacity, and downlink data rate (which can reach up to 13.9 Mbit/s at the MAC layer for
each HSDPA UE) increase.

The HSDPA Introduction Package feature provides:
Maximized power resource utilization

HSDPA Introduction Package adjusts the downlink power and data rate based on channel quality, maximizing the power resource utilization.
Shorter delay
With TTIs of 2 ms and 10 ms, which provide shorter scheduling intervals, the fast scheduling algorithm enables the NodeB to quickly schedule and retransmit data.
Higher uplink cell throughput

HARQ helps increase the downlink cell throughput.

This feature increases the downlink load but helps to admit more HSDPA users.In ideal conditions, a single cell can support a maximum of 96 HSDPA UEs simultaneously.

None

This feature increases the downlink load but helps to admit more HSDPA users.In ideal conditions, a single cell can support a maximum of 128 HSDPA UEs simultaneously.

None

This feature increases the downlink throughput for HSDPA users and cells by up to 10%.

Calculation for adjusting the CQI increases the downlink load of the NodeB DSP slightly.

This feature gives more scheduling opportunities to UEs closer to the NodeB and increases the downlink overall throughput of the cell. Cell throughput gains relate to UEs' CQIs.

With this feature, HSDPA UEs at cell edges have fewer scheduling opportunities and lower throughput. If GBRs are not configured for BE services, HSDPA UEs at cell edges may
have to wait a long time before they have scheduling opportunities. As a result, traffic radio bearers (TRBs) are more likely to reset and the call drop rate increases. The magnitude
of this impact depends on factors such as UE location distribution and service distribution in the cell. It is recommended that GBRs be configured for BE services to ensure network
Page 20 of 69
performance.
8.1.1 When to Use HSDPA Introduction Package
This feature is recommended for all scenarios. HSDPA can significantly increase the downlink peak rate per user, shorten the round trip delay, and expand the system capacity.
This feature package provides the basic functions of HSDPA to meet the requirements for test or trial operation of HSDPA services.

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-010610 HSDPA Introduction Package. (This feature cannot be configured using the CME.)
Requirements
Dependencies on Hardware
For the NodeB:
The NDLP and NBBI boards in the NodeB do not support this feature.
The DBS3800 must be configured with the HBBU/EBBC/EBBCd board or all these boards. These boards must support HSDPA.
The BTS3812E and BTS3812AE must be configured with the HBBI, EBOI, or EBBI board. Alternatively, they must be configured with at least one HDLP/EDLP/EDPLd
board and one HULP/EULP/EULPd board.
The 3900 series base stations support HSDPA.
The BTS3902E and BTS3803E support HSDPA.

For the UE:
The UE is HSDPA-capable.
Dependencies on Other Features

HSDPA provides a number of methods to increase system throughput. It has to coordinate with other features, such as admission control, load control, and mobility
management.
License
The license "High Speed Downlink Packet Access" on the RNC side has been activated. For details about how to activate the license, see License Management Feature
Dependencies on the Transport Network

After HSDPA is introduced, the downlink peak data rate per user can reach 14.4 Mbit/s. In this case, the bandwidth of an Iub over ATM transport network must reach 20 Mbit/s
or higher and the bandwidth of an Iub over IP transport network must reach 18 Mbit/s or higher. However, the Iub bandwidth in commercial networks must be higher because
R99 services exist in these networks. For the specific Iub bandwidth in a commercial network, you must refer to the results of network planning and network optimization.
Data Preparation
None
Activation(Using MML Commands)

1. Run the RNC MML command MOD UNODEB and set NodeB Protocol Version to R9.
2. Run the RNC MML command ADD UCELLHSDPA to set HSDPA-related parameters based on the network plan.
3. Run the RNC MML command ACT UCELLHSDPA to activate this feature.
4. Configure Iub-transmission-related parameters for HSDPA.
In an ATM network:
1. Run the RNC MML command ADD ATMTRF to configure new records of ATM traffic based on network planning requirements.
2. Run the RNC MML command LST TRMMAP to query the transmission resource mapping.
3. Run the RNC MML command ADD AAL2PATH to set associated parameters according to the network plan. TX traffic record index and RX traffic record index of the AAL2
path to be added must be the same as those set in the ADD ATMTRF command. In addition, AAL2 Path Type should be set according to the mapping between service types
and AAL paths.
4. Run the NodeB MML command ADD AAL2PATH to configure an AAL2 path for HSDPA based on network planning requirements.
NOTE:
The BTS3902E and BTS3803E do not support ATM transport.
In an IP network:
1. Run the RNC MML command LST ADJMAP to query whether resource management mapping is configured for the adjacent node.
If configured, check the TRMMAP index of the adjacent node.
If not configured, run the RNC MML command LST TRMMAP to query the default TRMMAP ID used by the adjacent node based on the settings of Interface Type and
Transport Type. For example, if Interface Type is set to Iub Interface, then the value for TRMMAP ID will be 1.
2. Run the RNC MML command LST TRMMAP to check whether the IP path mapping to the HSDPA service is configured according to the TRMMAP ID used by the adjacent
node.
If configured, no further action is required.
If not configured, run the RNC MML command ADD IPPATH to configure the IP path mapping to the HSDPA service.
NOTE:
To ensure that HSDPA services can be successfully set up, HSDPA services must be mapped to the corresponding AAL2 paths or IP paths. To prevent ongoing services from
being affected, you can add new AAL2 or IP paths.
The following ATM configurations are recommended:
To enable the peak data rate per user to reach 14.4 Mbit/s, the Synchronous Transport Module level-1 (STM-1) standard must be complied with. Note that the ATM over multiE1 transmission scheme cannot support a peak data rate per user of 14.4 Mbit/s.
The bandwidth of AAL2 paths is 20 Mbit/s and the bandwidth of intermediate transmission devices is not lower than 20 Mbit/s.
The following IP configurations are recommended:
To enable the peak data rate per user to reach 14.4 Mbit/s, the bandwidth of IP paths is 18 Mbit/s and the bandwidth of intermediate transmission devices is not lower than 18
Mbit/s.
For IP RANs, the recommended IP bandwidth is 18 Mbit/s because the physical bandwidth of IP paths must be higher than the Uu-interface data rate. For port configurations
Page 21 of 69
on the two ends in IP RANs, the port data rate must be 100 Mbit/s and the full duplex mode must be used.
MML Command Examples
//Modifying the protocol version for a NodeB

MOD UNODEB: NodeBId=1, NodeBProtclVer=R9;
//Setting HSDPA-related parameters based on the network plan
ADD UCELLHSDPA: CellId=3000, AllocCodeMode=Automatic, HsPdschMaxCodeNum=4, HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON;
//Activating HSDPA Introduction Package
ACT UCELLHSDPA: CellId=3000;
//Configuring Iub-transmission-related parameters
//Configuring Iub-transmission-related parameters for an Iub over ATM network
ADD ATMTRF: TRFX=118, ST=RTVBR, UT=KBIT/S, PCR=5150, SCR=5149, REMARK="5M-for-HSDPA";
ADD AAL2PATH: ANI=10, PATHID=2, CARRYT=IMA, CARRYF=1, CARRYSN=0, CARRYIMAGRPN=1, RSCGRPFLAG=NO, VPI=13, VCI=71, TXTRFX=118, RXTRFX=118,
//Adding an AAL2 path to the NodeB
ADD AAL2PATH: NT=LOCAL, PATHID=2, SN=2, SBT=E1_COVERBOARD, PT=IMA, JNRSCGRP=DISABLE, VPI=13, VCI=71, RU=KBPS, ST=NRTVBR, PCR=5150, SCR=
//Configuring Iub-transmission-related parameters for an Iub over IP network
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP,PATHT=BE, IPADDR="80.1.1.1", PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1
Activation Observation
Run the RNC MML command DSP UCELL to check whether HSDPA Introduction Package has been activated. If the value of the Cell HSDPA State parameter is AVAILABLE
(HSDPA Available cell), this feature has been activated.
//Verifying HSDPA Introduction Package

DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;
Deactivation
Using MML Commands
1. Run the RNC MML command DEA UCELLHSDPA to deactivate HSDPA Introduction Package.
2. Run the RNC MML command DSP UCELL to check whether HSDPA Introduction Package has been deactivated. If the value of the Cell HSDPA State parameter is
UNAVAILABLE(HSDPA Unavailable cell), this feature has been deactivated.
//Deactivating HSDPA Introduction Package

DEA UCELLHSDPA: CellId=3000;
DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;

8.2 WRFD-010650 HSDPA 13.976Mbps per User
8.2.1 When to Use HSDPA 13.976Mbps per User
None

None

Requirements
The DPUb or DPUe board in the RNC supports the data rate 14.4 Mbit/s.

The WRFD-010610 HSDPA Introduction Package feature that the HSDPA 13.976Mbps per User feature depends on has been activated.
License
The license "HSDPA 13.976Mbps per User" on the RNC side has been activated. For details about how to activate the license, see License Management Feature Parameter
Description.
Data Preparation
None
Activation
This feature is activated after the license controlling this feature is activated.
None
Deactivation
This feature does not need to be deactivated.
8.3 WRFD-01061001 15 Codes per Cell

8.3.1 When to Use 15 Codes per Cell
None

None
Page 22 of 69

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061001 15 Codes per Cell.
Requirements
None

The feature WRFD-010610 HSDPA Introduction Package that the 15 Codes per Cell feature depends has been configured.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated. For details about how to activate the license, see License Management
Data Preparation
Table 8-1 lists the data to prepare before deploying 15 Codes per Cell.
Table 8-1 Data to prepare before deploying 15 Codes per Cell
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
UCELLHSDPA
Allocate Code Mode
AllocCodeMode(BSC6900,BSC6910)
Set this parameter to Manual(Manual).
Radio network plan

(internal)
Code Number for HS-SCCH
HsScchCodeNum(BSC6900,BSC6910) none
Code Number for HS-PDSCH HsPdschCodeNum

(BSC6900,BSC6910)
Radio network plan

(internal)
none
Radio network plan

(internal)

NOTE:
Before running the RNC MML command MOD UCELLHSDPA, run the RNC MML command DEA UCELLHSDPA to deactivate HSDPA, configure HSDPA, and run the RNC MML
command ACT UCELLHSDPA to reactivate HSDPA.
Before running the RNC MML command MOD UCELLHSDPA, run the RNC MML command DEA UCELLEFACH to deactivate the enhanced CELL_FACH feature, configure
enhanced CELL_FACH, and run the RNC MML command ACT UCELLEFACH to reactivate enhanced CELL_FACH.
By default, each cell is configured with four HS-SCCH codes. If a cell has four HS-SCCH codes, the cell can use only 14 HS-PDSCH codes. If you want to configure 15 HSPDSCH codes for the cell, run the RNC MML command MOD UCELLHSDPA with Code Number for HS-SCCH set to 1.
1. Run the RNC MML command MOD UCELLHSDPA and set Code Number for HS-SCCH to 1.
2. Run the RNC MML command MOD UCELLHSDPA with Allocate Code Mode set to Manual(Manual) and Code Number for HS-PDSCH set to 15.
//Configuring 15 HS-PDSCH codes for a cell

MOD UCELLHSDPA: CellId=1, HsScchCodeNum=1;
MOD UCELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=15;
Activation(Using the CME)

NOTE:
When configuring the 15 Codes per Cell 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 8-2. For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
NOTE:
Before configuring HSDPA-related parameters for a cell (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches), deactivate HSDPA (CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell HSDPA Parameters. Set ACTSTATUS to Deactivated; CME batch configuration: No supported), configure HSDPA, and reactivate HSDPA (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA Parameters. Set ACTSTATUS to Activated; CME batch configuration: No supported).
Before configuring parameters related to enhanced CELL_FACH for a cell (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches), deactivate enhanced CELL_FACH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Enhanced FACH parameters. Set Validation indication to Deactivated; CME batch configuration: No supported),
configure enhanced CELL_FACH, and reactivate enhanced CELL_FACH (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell
Enhanced FACH parameters. Set Validation indication to Activated; CME batch configuration: No supported).
By default, the number of HS-SCCH codes for each cell is 4. If the default number is used, the HS-PDSCH can use only 14 SF16 codes. To enable the HS-PDSCH to use all
15 SF16 codes, set the value of Code Number for HS-SCCH to 1 (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches).
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 8-2 Configuring the parameters on the CME
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
Batch Modification
Center
UCELLHSDPA
RNC
Allocate Code Mode
AllocCodeMode
(BSC6900,BSC6910)
Yes
Code Number for HS-SCCH
HsScchCodeNum
(BSC6900,BSC6910)
Yes
Code Number for HS-PDSCH
HsPdschCodeNum
(BSC6900,BSC6910)
Yes
Page 23 of 69
1. Initialize UMTS monitoring on the RNC LMT, as shown in Figure 8-1. Click Submit. A real-time monitoring window is displayed.
Figure 8-1 Cell Performance Monitoring
2. Check whether 15 SF16 codes are occupied by the HS-PDSCH in the Cell Performance Monitoring window.
Expected result:
The HS-PDSCH occupies 15 SF16 codes.
----End
Deactivation
8.4 WRFD-01061018 Time and HS-PDSCH Codes Multiplex

8.4.1 When to Use Time and HS-PDSCH Codes Multiplex
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
Requirements
This feature does not have any special requirements for hardware.

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package.
License
Data Preparation
None
Activation
This feature does not need to be activated.
This feature does not need to be verified.
Deactivation
8.5 WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
8.5.1 When to Use HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).
Requirements
This feature does not depend on the hardware.

The configurations of the features on which this feature depends are complete. This feature depends on the feature WRFD-010610 HSDPA Introduction Package.
License
Data Preparation
Table 8-3 lists the data to prepare before deploying HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF).
Table 8-3 Data to prepare before deploying HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
MO
Parameter Name
Parameter ID
Setting Notes
ULOCELLMACHSPARA
Scheduling Method
SM
Set this parameter to MAXCI(Max Engineering Design

C/I Algorithm), RR(Round
Data Source
Page 24 of 69
Robin Algorithm), or PF(PF

Algorithm).

NOTE:
HSDPA H-ARQ is activated automatically without any configuration.
This section describes how to set Max C/I, RR, and PF scheduling algorithms. For details on how to set the EPF scheduling algorithm, see the description of the feature WRFD01061103 Scheduling based on EPF and GBR.
Run the NodeB MML command SET ULOCELLMACHSPARA with Scheduling Method set to MAXCI(Max C/I Algorithm), RR(Round Robin Algorithm), or PF(PF Algorithm).
//Activating HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
SET ULOCELLMACHSPARA: ULOCELLID=0, SM=MAXCI;

NOTE:
When configuring the HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF) feature on the CME, perform a single configuration first, and then perform a batch modification if
required.
Set the parameter described in Table 8-4 on the CME. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide.

----End
Table 8-4 Configuring the parameter on the CME
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
Batch Modification Center
ULOCELLMACHSPARA
NodeB
Scheduling Method
SM
Yes
Run the NodeB MML command LST ULOCELLMACHSPARA to query the value of the Scheduling Method parameter.
Deactivation
8.6 WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
8.6.1 When to Use HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation.
Requirements

Before this feature is activated, the feature WRFD-010610 HSDPA Introduction Package must be configured.
License
Data Preparation
Table 8-5 lists the data to prepare before deploying HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation.
Table 8-5 Data to prepare before deploying HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
UCELLHSDPA
Allocate Code Mode
AllocCodeMode(BSC6900,BSC6910)
Set this parameter based on

onsite conditions.
Radio network plan

(internal)
Code Number for HS-PDSCH
HsPdschCodeNum(BSC6900,BSC6910)
None
Radio network plan

(internal)
Code Max Number for HS-PDSCH
HsPdschMaxCodeNum(BSC6900,BSC6910)
Radio network plan

(internal)
Code Min Number for HS-PDSCH
HsPdschMinCodeNum(BSC6900,BSC6910)
Radio network plan

(internal)

Run the RNC MML command MOD UCELLHSDPA with Allocate Code Mode to Manual(Manual) or Automatic(Automatic).
If Allocate Code Mode is set to Manual, set Code Number for HS-PDSCH to specify the number of HS-PDSCH codes.
If Allocate Code Mode is set to Automatic, set Code Max Number for HS-PDSCH to specify the maximum number of HS-PDSCH codes and set Code Min Number for
Page 25 of 69
HS-PDSCH to specify the minimum number of HS-PDSCH codes.
//Activating HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Manual, HsPdschCodeNum=5, HsScchCodeNum=4;
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Automatic, HsPdschMaxCodeNum=5, HsPdschMinCodeNum=1;

NOTE:
When configuring the HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation feature on the CME, perform a single configuration first, and then perform a
batch modification if required.
Set parameters on the CME according to the operation sequence in Table 8-6 on the CME. For instructions on how to perform the CME single configuration, see CME Single

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
UCELLHSDPA
RNC
Allocate Code Mode
AllocCodeMode
(BSC6900,BSC6910)
Yes
NOTE:
If Allocate Code Mode is
set to Manual(Manual), go
to sequence 2.
If Allocate Code Mode is
set to Automatic
(Automatic), go to
sequence 3.
2 (Optional)
UCELLHSDPA
RNC
Code Number for HSPDSCH
HsPdschCodeNum
(BSC6900,BSC6910)
Yes
3 (Optional)
UCELLHSDPA
RNC
Code Max Number for HSPDSCH
HsPdschMaxCodeNum
(BSC6900,BSC6910)
Yes
Code Min Number for HSPDSCH
HsPdschMinCodeNum
(BSC6900,BSC6910)
Yes
Observation
1. Run the RNC MML command LST UCELLHSDPA to query code allocation mode.
2. On the RNC LMT, click to display Cell Performance Monitoring. Set Monitor Item to Cell Code Tree Monitor and click Submit. The Cell Performance Monitoring tab page
is displayed.
3. View the number of codes allocated to the HS-PDSCH in the cell. If Allocate Code Mode is set to Manual, the monitoring window of cell code tree usage shows that the
number of codes allocated to the HS-PDSCH remains unchanged. If Allocate Code Mode is set to Automatic, the monitoring window of cell code tree usage shows that the
number of codes allocated to the HS-PDSCH varies with service access requests in the cell. For example, the number of codes allocated to the HS-PDSCH increases with
the increase of HSDPA access requests and decreases with the decrease of HSDPA access requests.
----End
Deactivation
8.7 WRFD-01061010 HSDPA Flow Control

8.7.1 When to Use HSDPA Flow Control
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061010 HSDPA Flow Control.
Requirements

The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated.
License
Data Preparation
Table 8-7 lists the data to prepare before deploying HSDPA Flow Control.
Table 8-7 Data to prepare before deploying HSDPA Flow Control
MO
Parameter Name
Parameter ID
Setting Notes
Source
DLFLOWCTRLPARA
Flow Control Switch
SWITCH
You are advised to set this
Default/Recommended Value
Page 26 of 69
parameter to
BW_SHAPING_ONOFF_TOGGLE.

Run the NodeB MML command SET DLFLOWCTRLPARA with Flow Control Switch set to an appropriate value to enable the NodeB HSDPA flow control function. The adaptive
flow control algorithm is recommended.
There are four types of HSDPA flow control algorithm as follows:
When Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does not adjust the available bandwidth for HSDPA users based on delay and packet loss on the
Iub interface. Then, subtracting Iub bandwidth used by R99 from Iub bandwidth configured, the NodeB performs Iub shaping and distributes flow to HSDPA users.
When Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB adjusts the available bandwidth for HSDPA users based on delay and packet loss on the Iub
interface. Then, considering the data rate on the air interface, the NodeB performs Iub shaping and distributes flow to HSDPA users.
When Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not adjust the bandwidth based on delay and packet loss on the Iub interface. The NodeB reports
the conditions about the air interface to the RNC, and then the RNC allocates the bandwidth.
When Flow Control Switch is set to BW_SHAPING_ONOFF_TOGGLE, the flow control policy for the ports of the NodeB is either DYNAMIC_BW_SHAPING or
NO_BW_SHAPING in accordance with the congestion detection mechanism of the NodeB. This flow control algorithm is recommended.
//Activating HSDPA Flow Control and configuring the adaptive flow control algorithm
SET DLFLOWCTRLPARA: SRN=0, SN=6, BEAR=ATM, SBT=BASE_BOARD, PT=IMA, PN=0, SWITCH= BW_SHAPING_ONOFF_TOGGLE, TD=2, DR=1,ITM=TERRESTRIAL;

NOTE:
When configuring the HSDPA Flow Control feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
DLFLOWCTRLPARA
NodeB
Flow Control Switch
SWITCH
Yes
1. Choose Monitor > UMTS Monitoring > Connection Performance Monitoring on the RNC LMT. Create UL Throughput Bandwidth and DL Throughput Bandwidth
tasks.
2. Assume that the current Iub bandwidth is 4 MHz and the bandwidth usage is 100%. Enable an HSDPA-capable UE1 to access the network and originate a PS service.
Record the throughput of UE1.
Expected result:
The throughput of UE1 is 4 Mbps.
3. Enable an HSDPA-capable UE2 to access the network (with the same configuration as UE1) and originate a download service. Record the throughput of the two UEs.
Expected result:
The throughput of UE1 decreases after UE2 accesses the network. When the throughput of the two UEs is stable, the total bandwidth of the two UEs is 4 MHz. If user priority,
service type and Security Parameter Index (SPI) of the two UEs are the same, the final ratio of the two UEs' throughput is 1:1.
----End
Deactivation
You can deactivate the current algorithm by selecting one of the other flow control algorithms.
8.8 WRFD-01061006 HSDPA Mobility Management

8.8.1 When to Use HSDPA Mobility Management
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061006 HSDPA Mobility Management.
Requirements

The feature WRFD-010610 HSDPA Introduction Package must be configured before this feature is activated.
License
Data Preparation
None
Activation
The methods for activating intra-frequency, inter-frequency, and inter-RAT handovers are the same for HSDPA users and R99 users. For details on how to activate the WRFD-
Page 27 of 69
01061006 HSDPA Mobility Management feature, see Load Control Feature Parameter Description and Handover Feature Parameter Description.
None
Deactivation
8.9 WRFD-01061002 HSDPA UE Category 1 to 28

8.9.1 When to Use HSDPA UE Category 1 to 28
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061002 HSDPA UE Category 1 to 28.
Requirements

The feature WRFD-010610 HSDPA Introduction Package that the HSDPA UE Category 1 to 28 feature depends on has been activated.
License
Data Preparation
None
Activation
This feature does not need to be activated.
This feature does not need to be verified.
Deactivation
8.10 WRFD-010629 DL 16QAM Modulation

8.10.1 When to Use DL 16QAM Modulation
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-010629 DL 16QAM Modulation.
Requirements
UE should have the capability of HSDPA besides Category 11 and Category 12: category 1,2,3,4,5,6,7,8,9,10,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28.

License
Data Preparation
Table 8-9 lists the data to prepare before deploying DL 16QAM Modulation.
Table 8-9 Data to prepare before DL 16QAM Modulation
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
16QAM Switch
CME16QAMSW
Set this parameter to OPEN

(open).
Engineering Design

NOTE:
HSDPA Introduction Package must be activated before activating this feature. For the method of activating HSDPA Introduction Package, see the section "Configuring HSDPA
Introduction Package."
Run the NodeB MML command SET ULOCELLMACHSPARA with 16QAM Switch set to OPEN(open).
//Activating DL 16QAM Modulation

SET ULOCELLMACHSPARA: CME16QAMSW=OPEN;
Page 28 of 69
NOTE:
When configuring the DL 16QAM Modulation feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
16QAM Switch
CME16QAMSW
Yes
NOTE:
For the 16QAM modulation of the HSDPA UE, the NodeB license control item must be enabled.
As defined in 3GPP 25.306, the UE in category 8 can support both the QPSK and 16QAM modulation schemes. However, only the 16QAM modulation scheme enables the
throughput of category 8 UE to reach 5 Mbit/s. The throughput of category 8 UE can reach 5 Mbit/s only the radio environment is favorable.
Perform the following steps to check whether the download rate can reach 5 Mbit/s.
1. Use the UE to start a PS interactive service of DL 7200 kbit/s. The PS service is carried on the HS-DSCH. The UE keeps in Cell-DCH state.
2. Start FTP (10 threads) to download given files, which are larger than 1 GB. By monitoring the DL throughput and bandwidth, you find that the PS downloading service is
normal and the bit rate is higher than 5 Mbit/s.
----End
Deactivation(Using MML Commands)

Run the NodeB MML command SET ULOCELLMACHSPARA with 16QAM Switch set to CLOSE(close).
//Deactivating DL 16QAM Modulation

SET ULOCELLMACHSPARA: CME16QAMSW=CLOSE;
Deactivation(Using the CME)

NOTE:
When configuring the DL 16QAM Modulation feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
16QAM Switch
CME16QAMSW
Yes
8.11 WRFD-010631 Dynamic Code Allocation Based on NodeB

8.11.1 When to Use Dynamic Code Allocation Based on NodeB
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-010631 Dynamic Code Allocation Based on NodeB.
Requirements

License
The license "HSDPA RRM package 1" on the NodeB side has been activated. For details about how to activate the license, see License Management Feature Parameter
Description.
Data Preparation
Table 8-12 lists the data to prepare before deploying Dynamic Code Allocation Based on NodeB.
Table 8-12 Data to prepare before deploying Dynamic Code Allocation Based on NodeB
Page 29 of 69
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
Dynamic Code Switch
DYNCODESW
Set this parameter to OPEN

(open).
Engineering Design

NOTE:
HSDPA Introduction Package must be activated before activating this feature. For the method of activating HSDPA Introduction Package, see the section "Configuring HSDPA
Introduction Package."
Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code Switch set to OPEN(open).
//Activating Dynamic Code Allocation Based on NodeB on the NodeB side

SET ULOCELLMACHSPARA: DYNCODESW=OPEN;

NOTE:
When configuring the Dynamic Code Allocation Based on NodeB feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Dynamic Code Switch
DYNCODESW
Yes
Using MML commands:
1. Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code Switch set to CLOSE(close).
2. Run the RNC MML command MOD UCELLHSDPA.
3. Set Allocate Code Mode to Manual.
4. Set Code Number for HS-PDSCH to 5.
5. Use a UE of category 8 or higher to download 200 MB files from the FTP server in the serving cell.
6. Choose Service > Trace Management > Interface Trace Task > User from the navigation tree in the Maintenance tab page on NodeB LMT, and select (DL)Hsdpa User
Enhanced Schedule Data, as shown in Figure 8-2.
Figure 8-2 A user tracing task
7. Query the value of ucMaxPdschCodeNum, as shown in Figure 8-3.

Figure 8-3 Message Browser
Page 30 of 69
8. Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code Switch set to OPEN(open).
9. Trace the (DL)Hsdpa User Enhanced Schedule Data message and check the value for ucMaxPdschCodeNum. If the value is larger than 5, the feature has been enabled,
as shown in Figure 8-4.
Figure 8-4 Message Browser
//Deactivating Dynamic Code Allocation Based on NodeB on the NodeB

SET ULOCELLMACHSPARA: DYNCODESW=CLOSE;
//Configuring the Allocate Code Mode and Code Number for HS-PDSCH parameters on the RNC side:
MOD UCELLHSDPA: CellId=0, AllocCodeMode=Manual, HsPdschCodeNum=5;
//Reactivating Dynamic Code Allocation Based on NodeB on the NodeB
SET ULOCELLMACHSPARA: DYNCODESW=OPEN;

Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code Switch set to CLOSE(close).
//Deactivating Dynamic Code Allocation Based on NodeB on the NodeB

SET ULOCELLMACHSPARA: DYNCODESW=CLOSE;

NOTE:
When configuring the Dynamic Code Allocation Based on NodeB feature on the CME, perform a single configuration first, and then perform a batch modification if required.
Page 31 of 69

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Dynamic Code Switch
DYNCODESW
Yes
8.12 WRFD-010611 HSDPA Enhanced Package

8.12.1 When to Use HSDPA Enhanced Package
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-010611 HSDPA Enhanced Package.
Requirements
UE should support the functions related to HSDPA Enhanced Package.

The WRFD-010610 HSDPA Introduction Package feature that the HSDPA Enhanced Package feature depends has been configured.
License
This feature is not under license control.
Data Preparation
None
Activation/Activation Observation/Deactivation
For details on how to activate, verify, and deactivate the WRFD-010611 HSDPA Enhanced Package feature, see the following documents:
State Transition Feature Parameter Description
Directed Retry Decision Feature Parameter Description

NOTE:
HS-DPCCH Preamble Support does not need to be activated, verified, or deactivated.

8.13.1 When to Use Scheduling based on EPF and GBR
None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-01061103 Scheduling based on EPF and GBR.
Requirements

License
This feature is not under license control.
Data Preparation
Table 8-15 lists the data to prepare before deploying Scheduling based on EPF and GBR.
Table 8-15 Data to prepare before deploying Scheduling based on EPF and GBR
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
Scheduling Method
SM
Set this parameter to EPF

(Enhanced PF).
Engineering Design

Run the NodeB MML command SET ULOCELLMACHSPARA with Scheduling Method set to EPF(Enhanced PF).
//Activating Scheduling based on EPF and GBR

SET ULOCELLMACHSPARA: SM=EPF;

NOTE:
Page 32 of 69
When configuring the Scheduling based on EPF and GBR feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Scheduling Method
SM
Yes
Using MML Commands
Run the NodeB MML command LST ULOCELLMACHSPARA and check whether Scheduling Method is set to EPF.
//Verifying Scheduling based on EPF and GBR

LST ULOCELLMACHSPARA;

Run the NodeB MML command SET ULOCELLMACHSPARA with Scheduling Method set to a value other than EPF(Enhanced PF).
//Deactivating Scheduling based on EPF and GBR

SET MACHSPARA: SM=PF;

NOTE:
When configuring the Scheduling based on EPF and GBR feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Scheduling Method
SM
Yes

None

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-010653 96 HSDPA Users per Cell.
Requirements
The BTS3812E and BTS3812AE must be configured with the EBBI, EBOI, EULP, and EULPd boards.
The BBU3806 must be configured with the EBBC or EBBCd board.
The BBU3900 must be configured with the WBBPb or WBBPd board.

The WRFD-010623 64 HSDPA Users per Cell feature has been configured before the 96 HSDPA Users per Cell feature is activated.
License
The license "96 HSDPA Users per Cell" on the RNC side has been activated. For details about how to activate the license, see License Management Feature Parameter
Description.
Data Preparation
Table 8-18 lists the data to prepare before deploying 96 HSDPA Users per Cell.
Table 8-18 Data to prepare before deploying 96 HSDPA Users per Cell
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
UCELLALGOSWITCH
Cell CAC algorithm switch
NBMCacAlgoSwitch
Deselect the HSDPA_UU_ADCTRL(HSDPA UU
Radio network plan (internal)
Cell Hspa Plus function

switch
Page 33 of 69
(BSC6900,BSC6910)
Load Admission Control Algorithm) and

HSUPA_UU_ADCTRL(HSUPA UU Load
Admission Control Algorithm) check boxes.
HspaPlusSwitch
(BSC6900,BSC6910)
Select the DTX_DRX(Cell DTX_DRX Function

Switch) check box.
UCORRMALGOSWITCH
Dynamic Resource Allocation DraSwitch

Switch
(BSC6900,BSC6910)
Deselect the
DRA_HSDPA_STATE_TRANS_SWITCH and
DRA_HSUPA_STATE_TRANS_SWITCH check
boxes.
UFRCCHLTYPEPARA
Type of Channel Preferably

Carrying Signaling RB
SrbChlType
(BSC6900,BSC6910)
Set this parameter to HSPA

(UL_EDCH,DL_HSDSCH).
UCELLHSUPA
Code Number for E-AGCH
EagchCodeNum
(BSC6900,BSC6910)
Set this parameter to 1.
Default/Recommended value
Code Number for E-RGCH/E- ErgchEhichCodeNum Set this parameter to 6.

HICH
(BSC6900,BSC6910)
UCELLCAC
UL handover credit reserved

SF
UlHoCeResvSf
(BSC6900,BSC6910)
Set this parameter to SFOFF.
DL handover credit and code

reserved SF
DlHoCeCodeResvSf
(BSC6900,BSC6910)
Maximum HSDPA user

number
MaxHsdpaUserNum
(BSC6900,BSC6910)

1. Run the RNC MML command MOD UCELLALGOSWITCH. In this step, deselect the HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and
HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes under the parameter Cell CAC algorithm switch, and select the DTX_DRX(Cell
DTX_DRX Function Switch) check box under the Cell Hspa Plus function switch parameter.
2. Run the RNC MML command SET UCORRMALGOSWITCH. In this step, deselect DRA_HSDPA_STATE_TRANS_SWITCH and DRA_HSUPA_STATE_TRANS_SWITCH
from the Dynamic Resource Allocation Switch list to disable HSPA state transition.
3. Run the RNC MML command SET UFRCCHLTYPEPARA to enable SRB over HSPA. In this step, set Type of Channel Preferably Carrying Signaling RB to HSPA
(UL_EDCH,DL_HSDSCH) and Effective Flag of Signaling RB Channel Type to TRUE.
4. Run the RNC MML command MOD UCELLHSUPA with Code Number for E-AGCH and Code Number for E-RGCH/E-HICH set to appropriate values to allocate code
resources to E-AGCHs and E-RGCHs.
5. Run the RNC MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSDPA users per cell to 96. In this
step, set UL handover credit reserved SF and DL handover credit and code reserved SF to SFOFF(SFOFF) and set Maximum HSDPA user number to 96.
----End
/*Activating 96 HSDPA Users per Cell*/

//Deselecting the HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes
and selecting the DTX_DRX(Cell DTX_DRX Function Switch) check box
MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1;
//Disabling HSPA state transition
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0;
//Enabling SRB over HSPA
SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE;
//Allocating code resources to E-AGCHs and E-RGCHs
MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=6;
//Stop reserving uplink and downlink credit resources and setting the maximum number of HSDPA users to 96
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=96, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;

NOTE:
When configuring the 96 HSDPA Users per Cell feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
UCELLALGOSWITCH
RNC
NBMCacAlgoSwitch
(BSC6900,BSC6910)
Yes
Cell Hspa Plus function

switch
HspaPlusSwitch
(BSC6900,BSC6910)
UCORRMALGOSWITCH
RNC
Dynamic Resource
Allocation Switch
DraSwitch
(BSC6900,BSC6910)
Yes
UFRCCHLTYPEPARA
RNC

SrbChlType
(BSC6900,BSC6910)
Yes
UCELLHSUPA
RNC
EagchCodeNum
(BSC6900,BSC6910)
Yes
UCELLCAC
RNC
Page 34 of 69
Code Number for ERGCH/E-HICH
ErgchEhichCodeNum
(BSC6900,BSC6910)
UL handover credit
reserved SF
UlHoCeResvSf
(BSC6900,BSC6910)
DL handover credit and

code reserved SF
DlHoCeCodeResvSf
(BSC6900,BSC6910)
Maximum HSDPA user

number
MaxHsdpaUserNum
(BSC6900,BSC6910)
Yes
1. On the RNC LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring
dialog box, set Monitor Item to Cell User Number.
2. Use UEs to access the cell successively and then establish PS services, for example, download files through FTP.
Expected result:
Each UE establishes PS services successfully.
If the number of UEs is less than or equal to 96, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels.
If the number of UEs is greater than 96, HSPA services of the excess UEs are carried on R99 channels.
3. Check the value of the counter VS.HSDPA.UE.Max.Cell on the M2000 to determine the maximum number of users.
----End
NOTE:
The 96 HSDPA users referred to in this feature are enabled with the SRB over HSPA function.
Deactivation

This feature is recommended for cells with a large number of low-rate users.

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-010654 128 HSDPA Users per Cell.
Requirements
The feature is available only for 3900 series base stations. 3900 series base stations (except BTS3902E) must be configured with the WBBPd2 or WBBPd3.
BTS3803E base stations do not support this feature.

The following features must have been configured before this feature is activated:
License
The license "128 HSDPA Users per Cell" on the RNC side has been activated. For details about how to activate the license, see License Management Feature Parameter
Description.
Data Preparation
Table 8-20 lists the data to prepare before deploying 128 HSDPA Users per Cell.
Table 8-20 Data to prepare before deploying 128 HSDPA Users per Cell
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
UCELLALGOSWITCH
NBMCacAlgoSwitch
(BSC6900,BSC6910)
Deselect the HSDPA_UU_ADCTRL

(HSDPA UU Load Admission Control
Algorithm) and HSUPA_UU_ADCTRL
(HSUPA UU Load Admission Control
Algorithm) check boxes.
Cell Hspa Plus function switch
HspaPlusSwitch
(BSC6900,BSC6910)
Select the DTX_DRX(Cell DTX_DRX

Function Switch) check box.
UCORRMALGOSWITCH
Dynamic Resource Allocation

Switch
DraSwitch
(BSC6900,BSC6910)
Deselect the
DRA_HSDPA_STATE_TRANS_SWITCH
and
DRA_HSUPA_STATE_TRANS_SWITCH
check boxes.
UFRCCHLTYPEPARA

SrbChlType
(BSC6900,BSC6910)
Set this parameter to HSPA

(UL_EDCH,DL_HSDSCH).
UCELLHSUPA
EagchCodeNum
(BSC6900,BSC6910)
Code Number for E-RGCH/EHICH
ErgchEhichCodeNum
(BSC6900,BSC6910)
UL handover credit reserved SF UlHoCeResvSf

(BSC6900,BSC6910)

reserved SF
DlHoCeCodeResvSf
(BSC6900,BSC6910)
Maximum HSDPA user number
MaxHsdpaUserNum
(BSC6900,BSC6910)
UCELLCAC
Page 35 of 69

1. Run the RNC MML command MOD UCELLALGOSWITCH. In this step, deselect the HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and
HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes under the parameter Cell CAC algorithm switch, and select the DTX_DRX(Cell
DTX_DRX Function Switch) check box under the Cell Hspa Plus function switch parameter.
2. Run the RNC MML command SET UCORRMALGOSWITCH with the DRA_HSDPA_STATE_TRANS_SWITCH and DRA_HSUPA_STATE_TRANS_SWITCH check boxes
under the Dynamic Resource Allocation Switch parameter deselected to disable HSPA state transition.
3. Run the RNC MML command SET UFRCCHLTYPEPARA with Type of Channel Preferably Carrying Signaling RB set to HSPA(UL_EDCH,DL_HSDSCH) to enable SRB over
HSPA.
4. Run the RNC MML command MOD UCELLHSUPA with Code Number for E-AGCH and Code Number for E-RGCH/E-HICH set to appropriate values to allocate code
resources to E-AGCHs and E-RGCHs.
5. Run the RNC MML command MOD UCELLCAC to stop reserving uplink and downlink credit resources and set the maximum number of HSDPA users per cell to 128. In this
step, set UL handover credit reserved SF and DL handover credit and code reserved SF to SFOFF and set Maximum HSDPA user number to 128.
----End
/*Activating 128 HSDPA Users per Cell*/

//Deselecting the HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) and HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes
and selecting the DTX_DRX(Cell DTX_DRX Function Switch) check box
MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0, HspaPlusSwitch=DTX_DRX-1;
//Disabling HSPA state transition
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0;
//Enabling SRB over HSPA
SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE;
//Allocating code resources to E-AGCHs and E-RGCHs
MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=8;
//Stop reserving uplink and downlink credit resources and setting the maximum number of HSDPA users to 128
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=128, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;

NOTE:
When configuring the 128 HSDPA Users per Cell feature on the CME, perform a single configuration first, and then perform a batch modification if required.
Set parameters on the CME according to the operation sequence in Table 8-21 on the CME configuration interface. For instructions on how to perform the CME single
configuration, see CME Single Configuration Operation Guide.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
Batch Modification
Center
UCELLALGOSWITCH
RNC
NBMCacAlgoSwitch
(BSC6900,BSC6910)
Yes
Cell Hspa Plus function switch
HspaPlusSwitch(BSC6900,BSC6910)
UCORRMALGOSWITCH
RNC
Dynamic Resource Allocation

Switch
DraSwitch(BSC6900,BSC6910)
Yes
UFRCCHLTYPEPARA
RNC

SrbChlType(BSC6900,BSC6910)
Yes
UCELLHSUPA
RNC
EagchCodeNum(BSC6900,BSC6910) Yes
Code Number for E-RGCH/EHICH
ErgchEhichCodeNum
(BSC6900,BSC6910)
UCELLCAC
RNC
UL handover credit reserved SF UlHoCeResvSf(BSC6900,BSC6910)
Yes

reserved SF
DlHoCeCodeResvSf
(BSC6900,BSC6910)
Yes
Maximum HSDPA user number
MaxHsdpaUserNum
(BSC6900,BSC6910)
Yes
1. On the RNC LMT, click Monitor. Then, double-click Cell Performance Monitoring in the Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring
dialog box, set Monitor Item to Cell User Number.
2. Use UEs to access the cell successively and then establish PS services, for example, download files through FTP.
Expected result:
Each UE establishes PS services successfully.
If the number of UEs is less than or equal to 128, uplink services are carried on HSUPA channels and downlink services are carried on HSDPA channels.
If the number of UEs is greater than 128, HSPA services of the excess UEs are carried on R99 channels.
3. Check the value of the counter VS.HSDPA.UE.Max.Cell on the M2000 to determine the maximum number of users.
NOTE:
The 128 HSDPA users referred to in this feature are enabled with the SRB over HSPA function.
Deactivation
Page 36 of 69

8.16.1 When to Use CQI Adjustment Based on Dynamic BLER Target
This feature is recommended for all scenarios. It helps increase cell downlink throughput by up to 10%. It has no adverse impact on network performance.
This feature is not recommended if operators request a fixed target block error rate (BLER).

Check whether operators have requested a fixed target BLER.

This section describes how to activate, verify, and deactivate the optional feature WRFD-030010 CQI Adjustment Based on Dynamic BLER Target.
Requirements
The BTS3812E and BTS3812AE must be configured with the EBBI, EBOI, or EDLP board.
The BBU3806 must be configured with the EBBC or EBBCd board.
The BBU3900 must be configured with the WBBPb or WBBPd board.

License
The license controlling this feature has been activated. For details about license items, see License Management Feature Parameter Description.
Data Preparation
Table 8-22 lists the data to prepare before deploying CQI Adjustment Based on Dynamic BLER Target.
Table 8-22 Data to prepare before deploying CQI Adjustment Based on Dynamic BLER Target
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
CQI Adjust Algorithm Switch of

non-Conversational Service
CQIADJALGOFNONCON
To activate CQI Adjustment

Based on Dynamic BLER Target,
set this parameter to
CQI_ADJ_BY_DYN_BLER(CQI
Adjusted by Dynamic BLER).
To deactivate CQI Adjustment
Based on Dynamic BLER Target,
set this parameter to
NO_CQI_ADJ(Not CQI Adjust
Algorithm).
Engineering Design

Run the NodeB MML command SET ULOCELLMACHSPARA with CQI Adjust Algorithm Switch of non-Conversational Service set to CQI_ADJ_BY_DYN_BLER(CQI
Adjusted by Dynamic BLER).
//Activating CQI Adjustment Based on Dynamic BLER Target

SET ULOCELLMACHSPARA: ULOCELLID=0, CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER;

NOTE:
When configuring the CQI Adjustment Based on Dynamic BLER Target feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
CQI Adjust Algorithm

Switch of nonConversational Service
CQIADJALGOFNONCON
Yes
Using MML Commands
Run the NodeB MML command LST MACHSPARA. In this step, ensure that CQI Adjust Algorithm Switch of non-Conversational Service is set to CQI_ADJ_BY_DYN_BLER.
//Verifying CQI Adjustment Based on Dynamic BLER Target

LST ULOCELLMACHSPARA: ULOCELLID=0;
Page 37 of 69

Run the NodeB MML command SET MACHSPARA. In this step, set CQI Adjust Algorithm Switch of non-Conversational Service to NO_CQI_ADJ(Not CQI Adjust
Algorithm).
//Deactivating CQI Adjustment Based on Dynamic BLER Target

SET ULOCELLMACHSPARA: CQIADJALGOFNONCON=NO_CQI_ADJ;

NOTE:
When configuring the CQI Adjustment Based on Dynamic BLER Target feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
CQI Adjust Algorithm

Switch of nonConversational Service
CQIADJALGOFNONCON
Yes

This feature helps increase cell throughput. You can query the values of the following counters to track changes in cell throughput:
VS.HSDPA.MeanChThroughput: an RNC counter that measures the average downlink throughput of individual MAC-d flows for HSDPA in a cell
VS.DataOutput.Mean: a NodeB counter that measures the average cell throughput at the MAC-hs/MAC-ehs layer within a measurement period
The values of the preceding counters increase after this feature is activated. Note that gains brought by this feature vary in different scenarios.

8.17.1 When to Use HSDPA Scheduling based on UE Location
If telecom operators intend to give up some equity among UEs for higher HSDPA cell throughput, enable this feature for parts of or the entire network.

None

This section describes how to activate, verify, and deactivate the optional feature WRFD-140221 HSDPA Scheduling Based on UE Location.
Requirements
Dependencies on RNC Hardware
This feature does not depend on the RNC hardware.
Dependencies on NodeB Hardware
All 3900 series base stations must support this feature. To support this feature, the 3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf
board.
The DBS3800 must support this feature. To support this feature, the DBS3800 series base stations must be configured with the EBBC or EBBCd board.
The BTS3812E/BTS3812A/BTS3812AE supports this feature. To support this feature, the BTS3812E/BTS3812A/BTS3812AE must be configured with the EBBI, EDLP or
EBOI board.

WRFD-010611 HSDPA Enhanced Package
License
The license controlling this feature has been activated. For details about the license items and how to activate the license, seeLicense Management Feature Parameter
Description.
Others Prerequisites
It is recommended that GBRs be configured on the RNC for all BE services to guarantee basic user experience.
Data Preparation
Table 8-25 lists the data to prepare before deploying HSDPA Scheduling Based on UE Location.
Table 8-25 Data to prepare before deploying HSDPA Scheduling Based on UE Location
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
Scheduling algorithms
SM
Set this parameter to EPF_LOC(Location

based EPF).
Engineering Design
Location Weight
LOCWEIGHT
None
Engineering Design
Page 38 of 69

Run the NodeB MML command SET ULOCELLMACHSPARA. In this step, set Scheduling Method to EPF_LOC(Location based EPF) and Location Weight to appropriate
values.
//Activating HSDPA Scheduling based on UE Location

SET ULOCELLMACHSPARA: ULOCELLID=1, SM=EPF_LOC, LOCWEIGHT=1;

NOTE:
When configuring the HSDPA Scheduling based on UE Location feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
Batch Modification
Center
ULOCELLMACHSPARA
NodeB
Scheduling Method
SM
Yes
Location Weight
LOCWEIGHT
Yes
Run the NodeB MML command LST ULOCELLMACHSPARA. If the command output shows that the value of Scheduling Method is EPF_LOC(Location based EPF), this
feature has been activated for the target cell.

Run the NodeB MML command SET ULOCELLMACHSPARA. In this step, set Scheduling Method to a value other than EPF_LOC(Location based EPF).
//Deactivating HSDPA Scheduling based on UE Location

SET ULOCELLMACHSPARA: ULOCELLID=1, SM=EPF;

NOTE:
When configuring the HSDPA Scheduling based on UE Location feature on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Scheduling Method
SM
Yes

To monitor the effects of this feature, perform the following steps:
1. Before activating this feature for a cell, record the cell throughput of HSDPA according to the following formula:
VS.DataOutput.Mean/(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRation.Mean)
The descriptions of related counters in NodeB are as follows:
VS.DataOutput.Mean: the average cell throughput at the MAC-hs/MAC-ehs layer within a measurement period
VS.DataTtiRatio.Mean: ratio of the time when at least one HSDPA user has data to transmit in the queue buffer within a measurement period
VS.HSDPA.InactiveDataTtiRatio.Mean: average ratio of the time when at least one HSDPA user has data to transmit in the buffer but no HSDPA user transmits data at
the physical layer within a measurement period
2. Verify whether the value of the cell throughput of HSDPA is greater after this feature is activated.
How much the value of cell throughput of HSDPA increase depends on factors such as UE distribution and the service model.
----End

After the EPF_LOC scheduling algorithm is enabled, the value of the LOCWEIGHT parameter affects the cell throughput and the degree to which UEs are differentiated from each
other. A larger value for this parameter means that UE locations weigh more in scheduling. This gives more scheduling opportunities to UEs closer to the NodeB, increases the cell
throughput, and decreases the throughput at cell edges. In this case, to ensure equity among UEs, set the LOCWEIGHT parameter to a small value; to maximize the cell
throughput while ensuring a GBR for UEs at cell edges, set the LOCWEIGHT parameter to a large value.
Page 39 of 69
8.18.1 When to Use HSDPA Remaining Power Appending
The HSDPA remaining power appending algorithm applies to scenarios where network KPIs are better than the Acceptance Criterion (APC) and there are a certain number of
remaining power resources. Network KPIs refer to the CS call drop rate, PS call drop rate, CS RAB setup success rate, and PS RAB setup success rate.
When the downlink load is light, the HSDPA remaining power appending algorithm helps decrease the downlink BLER and improve user experience. However, this algorithm
increases the downlink load. When the downlink load becomes heavy, network KPIs are deteriorated. Therefore, the EXTRAPOWER parameter cannot be set to a too large value.
The recommended value for this parameter is 4, which is equal to 1 dB.
When the value of the VS.DataTtiRatio.Mean counter for a cell is greater than 50%, for example, in densely populated urban areas, the HSDPA remaining power appending
algorithm may decrease the CQI and cell throughput. Under this condition, the EXTRAPOWER parameter should be set to a value equal to or less than 4.
When the value of the VS.DataTtiRatio.Mean counter for a cell is less than 10%, for example, in suburban areas, the EXTRAPOWER parameter can be set to a comparatively
large value, for example, 12 (equal to 3 dB), to improve user experience.

Before feature deployment, collect the values of the following KPIs or counters:
Network KPIs
CS call drop rate
PS call drop rate
CS RAB setup success rate
PS RAB setup success rate
RNC counter
VS.MeanTCP
NodeB counters
VS.AckTotal
VS.NackTotal
VS.DtxTotal
VS.DataTtiRatio.Mean

This section describes how to activate, verify, and deactivate the function HSDPA Remaining Power Appending.
Requirements
None

None
License
None
Data Preparation
Table 8-28 lists the data to prepare before deploying HSDPA Remaining Power Appending.
Table 8-28 Data to prepare before deploying HSDPA Remaining Power Appending
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
Extra Power
EXTRAPOWER
Set this parameter to a

non-zero value.

Run the NodeB MML command SET ULOCELLMACHSPARA to set Extra Power to a non-zero value.
//Activating HSDPA Remaining Power Appending

SET ULOCELLMACHSPARA: ULOCELLID=1, EXTRAPOWER=1;

NOTE:
When configuring the HSDPA Remaining Power Appending function on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Extra Power
EXTRAPOWER
Yes
Page 40 of 69
Check the value of the RNC counter VS.MeanTCP for the following results:
The value of this counter is less than 80% before this algorithm is enabled.
The value of this counter is increased by a value less than the value specified by the Extra Power parameter after this algorithm is enabled.
Then, the HSDPA Remaining Power Appending algorithm is effective.

Alternatively, check the downlink BLER. If the downlink BLER is significantly decreased after this algorithm is enabled, this algorithm is effective. The downlink BLER can be
calculated using the following formula:
BLER = (VS.NackTotal + VS.DtxTotal)/(VS.AckTotal + VS.NackTotal + VS.DtxTotal)
where
The VS.AckTotal, VS.NackTotal, and VS.DtxTotal counters are NodeB counters.

Run the NodeB MML command SET ULOCELLMACHSPARA and set Extra Power to 0.
//Deactivating HSDPA Remaining Power Appending

SET ULOCELLMACHSPARA: ULOCELLID=1, EXTRAPOWER=0;

NOTE:
When configuring the HSDPA Remaining Power Appending function on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Extra Power
EXTRAPOWER
Yes

Decrease the value of the Extra Power parameter by one if some network KPIs, such as the CS call drop rate, PS call drop rate, CS RAB setup success rate, and PS RAB setup
success rate, deteriorate or cannot meet the Acceptance Criterion (APC). Then, check the values of network KIPs.
Increase the value of the Extra Power parameter by one if the values of network KPIs are better than the APC, a certain number of remaining power resources are left, and the
BLER is large. Then, check the values of network KIPs.
Decrease the value of the Extra Power parameter by one if cell throughput decreases due to the decrease in the mean CQI and increase in the value of the VS.DataTtiRatio.Mean
counter.
8.19.1 When to Use BLER Optimization for HSDPA Burst Services
Use the BLER Optimization for HSDPA Burst Services function if users want to decrease the BLER of HSDPA services and increase the UE and cell throughput. This function
provides noticeable throughput gains when the data transmission duration of HSDPA UEs is 20% shorter than the value of the VS.DataTtiRatio.Mean counter and the BLER of
HSDPA services is high.

Collect the values of the following NodeB counters before enabling this function:
VS.AckTotal
VS.NackTotal
VS.DtxTotal
VS.DataOutput.Mean
VS.HSDPA.InactiveDataTtiRatio.Mean

This section describes how to enable, verify, and disable the BLER Optimization for HSDPA Burst Services function.
Requirements
None
Data Preparation
Table 8-31 lists the data to prepare before deploying BLER Optimization for HSDPA Burst Services.
Table 8-31 Data to prepare before deploying BLER Optimization for HSDPA Burst Services
MO
Parameter Name
Parameter ID
Setting Notes
Data Source
ULOCELLMACHSPARA
Optimization Switch for BLER of

HSDPA Burst service
BURSTBLEROPTSW
Set this parameter to ON.

Run the NodeB MML command SET ULOCELLMACHSPARA with Optimization Switch for BLER of HSDPA Burst service set to ON.
Page 41 of 69
//Enabling BLER Optimization for HSDPA Burst Services

SET ULOCELLMACHSPARA: ULOCELLID=1, BURSTBLEROPTSW=ON;

NOTE:
When configuring the BLER Optimization for HSDPA Burst Services function on the CME, perform a single configuration first, and then perform a batch modification if required.
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Optimization Switch for

BLER of HSDPA Burst
service
BURSTBLEROPTSW
Yes
1. Check the values of the NodeB counters: VS.AckTotal, VS.NackTotal, and VS.DtxTotal.
2. Use the following formula to obtain the BLER of HSDPA burst services before and after function enabling:
BLER = (VS.NackTotal + VS.DtxTotal)/(VS.AckTotal +VS.NackTotal + VS.DtxTotal)
If the BLER decreases after function enabling, the function has taken effect. Otherwise, the function does not take effect yet.
3. Use the following formula to obtain the cell throughput before and after function enabling:
Cell throughput = VS.DataOutput.Mean/(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)
If the cell throughput increases after function enabling, the function has taken effect. Otherwise, the function does not take effect yet.
----End

Run the NodeB MML command SET ULOCELLMACHSPARA with Optimization Switch for BLER of HSDPA Burst service set to OFF.
//Disabling BLER Optimization for HSDPA Burst Services

SET ULOCELLMACHSPARA: ULOCELLID=1, BURSTBLEROPTSW=OFF;

NOTE:
When configuring the BLER Optimization for HSDPA Burst Services function on the CME, perform a single configuration first, and then perform a batch modification if required.

----End
SN
Managed Object (MO)
NE
Parameter Name
Parameter ID
Configurable in CME
ULOCELLMACHSPARA
NodeB
Optimization Switch for

BLER of HSDPA Burst
service
BURSTBLEROPTSW
Yes
9 Parameters
Table 9-1 Parameter description
Parameter ID
NE
MML Command
Feature ID
Feature Name
Description
EXTRAPOWER
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
None
None
Meaning:Indicates the maximum power used for

scheduled users after the scheduling.
GUI Value Range:0~40
Unit:0.25dB
Actual Value Range:0~40
Default Value:0
DlSfAdmAlgoSwitch
BSC6900
ADD
UCELLALGOSWITCH
MOD
UCELLALGOSWITCH
WRFD-020101
Admission Control
Meaning:1. CS_SETUP_OPT_SWITCH: Whether the

code resources reserved for handovers can be used
for CS RAB setups.When this switch is turned on, the
RNC is allowed to use the code resources reserved for
handovers for CS RAB setups.When this switch is
turned on, the RNC is not allowed to use the code
Page 42 of 69
resources reserved for handovers for CS RAB setups.

2. FDPCH_SF_ALLOC_OPT_SWITCH: Whether the
F-DPCH code allocation algorithm optimization
function is enabled.When this switch is turned on, the
RNC uses the vacant SF256 code with the smallest
number as the F-DPCH code. Moreover, if the RNC
finds that an SF256 code with the smaller number is
released, the RNC uses the released code as the FDPCH code.When this switch is turned off, the RNC
does not reallocate the SF256 code with the smaller
number as the F-DPCH code.
GUI Value Range:CS_SETUP_OPT_SWITCH,
FDPCH_SF_ALLOC_OPT_SWITCH
Unit:None
Actual Value Range:CS_SETUP_OPT_SWITCH,
Default Value:CS_SETUP_OPT_SWITCH0&FDPCH_SF_ALLOC_OPT_SWITCH-0
DlSfAdmAlgoSwitch
BSC6910
ADD
UCELLALGOSWITCH
MOD
UCELLALGOSWITCH
WRFD-020101
Admission Control
Meaning:1. CS_SETUP_OPT_SWITCH: Whether the

code resources reserved for handovers can be used
for CS RAB setups.When this switch is turned on, the
RNC is allowed to use the code resources reserved for
handovers for CS RAB setups.When this switch is
turned on, the RNC is not allowed to use the code
resources reserved for handovers for CS RAB setups.
2. FDPCH_SF_ALLOC_OPT_SWITCH: Whether the
F-DPCH code allocation algorithm optimization
function is enabled.When this switch is turned on, the
RNC uses the vacant SF256 code with the smallest
number as the F-DPCH code. Moreover, if the RNC
finds that an SF256 code with the smaller number is
released, the RNC uses the released code as the FDPCH code.When this switch is turned off, the RNC
does not reallocate the SF256 code with the smaller
number as the F-DPCH code.
GUI Value Range:CS_SETUP_OPT_SWITCH,
Unit:None
Actual Value Range:CS_SETUP_OPT_SWITCH,
Default Value:CS_SETUP_OPT_SWITCH0&FDPCH_SF_ALLOC_OPT_SWITCH-0
ChannelRetryHoTimerLen
BSC6900
SET UCOIFTIMER
WRFD01061403
WRFD01061404
WRFD-010636
WRFD-010652
WRFD-010683
WRFD-010684
WRFD-010685
WRFD-010686
WRFD-010687
WRFD-021101
WRFD-021200
HSUPA 2ms TTI

HSUPA 2ms/10ms
TTI Handover
SRB over HSUPA
SRB over HSDPA
Downlink 64QAM
2x2 MIMO
Downlink Enhanced
L2
CPC - DTX / DRX
CPC - HS-SCCH less
operation
Dynamic Channel
Configuration Control
(DCCC)
HCS (Hierarchical
Cell Structure)
Meaning:This parameter specifies the value of the

channel retry handover timer. When handover is
performed and some higher HSPA or HSPA plus
technique is supported, UTRAN will trigger the
reconfiguration for the higher techniques. Pingpang
will happen when the reconfiguration is triggered
immediately when handover succeeds, because
handover procedure is frequently. In order to avoid the
pingpang, this timer will start after handover procedure
is performed, and the reconfiguration will not be
triggered until the timer expires.
Unit:s
Default Value:2
ChannelRetryHoTimerLen
BSC6910
SET UCOIFTIMER
WRFD01061403
WRFD01061404
WRFD-010636
WRFD-010652
WRFD-010683
WRFD-010684
WRFD-010685
WRFD-010686
WRFD-010687
WRFD-021101
WRFD-021200
HSUPA 2ms TTI

HSUPA 2ms/10ms
TTI Handover
SRB over HSUPA
SRB over HSDPA
Downlink 64QAM
2x2 MIMO
Downlink Enhanced
L2
CPC - DTX / DRX
CPC - HS-SCCH less
operation
Dynamic Channel
(DCCC)
HCS (Hierarchical
Cell Structure)
Meaning:This parameter specifies the value of the

channel retry handover timer. When handover is
performed and some higher HSPA or HSPA plus
technique is supported, UTRAN will trigger the
reconfiguration for the higher techniques. Pingpang
will happen when the reconfiguration is triggered
immediately when handover succeeds, because
handover procedure is frequently. In order to avoid the
pingpang, this timer will start after handover procedure
is performed, and the reconfiguration will not be
triggered until the timer expires.
Unit:s
Default Value:2
PWRMGN
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061004
HSDPA Power
Control
Meaning:Indicates the power margin reserved for R99

channels. It specifies the power percentage relative to
the maximum cell transmit power.
Unit:%
Default Value:5
HspaPower
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061004
HSDPA Power
Control
Meaning:This parameter 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 parameter, see 3GPP TS 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 specifies the offset between
Page 43 of 69
MOD UCELLHSDPA
01061004
Control
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 parameter, see 3GPP TS 25.308.
GUI Value Range:-500~0
Unit:0.1dB
Actual Value Range:-50~0
Default Value:0
HsScchCodeNum
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD-010610
WRFD-020108
WRFD01061018
HSDPA Introduction
Package
Code Resource
Management
Time and HS-PDSCH
Codes Multiplex
Meaning:This parameter decides the maximum

number of HSDPA subscribers that the NodeB can
schedule in a TTI period. For detailed information of
this parameter, see 3GPP TS 25.308.
Unit:None
Default Value:4
HsScchCodeNum
BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD-010610
WRFD-020108
WRFD01061018
HSDPA Introduction
Package
Code Resource
Management
Time and HS-PDSCH
Codes Multiplex
Meaning:This parameter decides the maximum

number of HSDPA subscribers that the NodeB can
schedule in a TTI period. For detailed information of
this parameter, see 3GPP TS 25.308.
Unit:None
Default Value:4
AllocCodeMode
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Allocation and RNCControlled Dynamic
Code Allocation
Meaning:HS-PDSCH code allocation mode: Manual or

Automatic. If Manual is chosen, parameter " Code
Number for HS-PDSCH " determines HS-PDSCH code
number to be allocated. If Automatic is chosen,
according to the number of codes occupied by R99
services, allocate HS-PDSCH code number between
configured " Code Max Number for HS-PDSCH " and "
Code Min Number for HS-PDSCH ". For detailed
information of this parameter, see 3GPP TS 25.308.
GUI Value Range:Manual(Manual), Automatic
(Automatic)
Unit:None
Actual Value Range:Manual, Automatic
Default Value:Automatic(Automatic)
AllocCodeMode
BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Code Allocation
Meaning:HS-PDSCH code allocation mode: Manual or

Automatic. If Manual is chosen, parameter " Code
Number for HS-PDSCH " determines HS-PDSCH code
number to be allocated. If Automatic is chosen,
according to the number of codes occupied by R99
services, allocate HS-PDSCH code number between
configured " Code Max Number for HS-PDSCH " and "
Code Min Number for HS-PDSCH ". For detailed
GUI Value Range:Manual(Manual), Automatic
(Automatic)
Unit:None
Actual Value Range:Manual, Automatic
Default Value:Automatic(Automatic)
DYNCODESW
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD-010631
Dynamic Code
Allocation Based on
Node B
Meaning:Indicates the Dynamic Code Switch. The

function will be enabled if this parameter is set to
OPEN. When this switch is turned on, the cell codes
are used efficiently, and the system capacity is
improved.
GUI Value Range:OPEN(open), CLOSE(close)
Unit:None
Actual Value Range:OPEN, CLOSE
Default Value:OPEN(open)
HsPdschCodeNum
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Code Allocation
Meaning:Number of HS-PDSCH codes. For details

about this parameter, see 3GPP TS 25.308.
Unit:None
Default Value:5
HsPdschCodeNum
BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Code Allocation
Meaning:Number of HS-PDSCH codes. For details

about this parameter, see 3GPP TS 25.308.
Unit:None
Default Value:5
HsPdschMinCodeNum
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Code Allocation
Meaning:The parameter specifies the minimum

number of the HS-PDSCH codes. This parameter is
valid only when "Allocate Code Mode" is set to
Automatic. The number of codes used by the HSPDSCH is dynamically set between "Code Min
Number for HS-PDSCH" and "Code Max Number for
HS-PDSCH", based on the idle state of the code tree.
When the non-H services need more code resources,
the non-H service will gradually occupy the codes
used by the HS-PDSCH. The number of codes the
HS-DPSCH reserved is not less than the value of
"Code Min Number for HS-PDSCH". For detailed
Unit:None
Default Value:1
HsPdschMinCodeNum
BSC6910
ADD UCELLHSDPA
WRFD-
15 Codes per Cell
Meaning:The parameter specifies the minimum
Page 44 of 69
MOD UCELLHSDPA
01061001
WRFD01061005
HSDPA Static Code

Code Allocation
number of the HS-PDSCH codes. This parameter is

valid only when "Allocate Code Mode" is set to
Automatic. The number of codes used by the HSPDSCH is dynamically set between "Code Min
Number for HS-PDSCH" and "Code Max Number for
HS-PDSCH", based on the idle state of the code tree.
When the non-H services need more code resources,
the non-H service will gradually occupy the codes
used by the HS-PDSCH. The number of codes the
HS-DPSCH reserved is not less than the value of
"Code Min Number for HS-PDSCH". For detailed
Unit:None
Default Value:1
HsPdschMaxCodeNum
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Code Allocation
Meaning:The parameter determines the maximum

number of HS-PDSCH codes. This parameter is valid
only when "Allocate Code Mode" is set to "Automatic".
The number of codes used by the HS-PDSCH is
dynamically set between "Code Min Number for HSPDSCH" and "Code Max Number for HS-PDSCH",
based on whether the code tree is idle or busy. When
the code resource used by the non-HSPA services is
little, the HS-PDSCH uses the rest idle codes as much
as possible, and the maximum number of idle codes
(SF=16 continuous codes) is equal to the value of
"Code Max Number for HS-PDSCH". For detailed
Unit:None
Default Value:5
HsPdschMaxCodeNum
BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061001
WRFD01061005
15 Codes per Cell

HSDPA Static Code
Code Allocation
Meaning:The parameter determines the maximum

number of HS-PDSCH codes. This parameter is valid
only when "Allocate Code Mode" is set to "Automatic".
The number of codes used by the HS-PDSCH is
dynamically set between "Code Min Number for HSPDSCH" and "Code Max Number for HS-PDSCH",
based on whether the code tree is idle or busy. When
the code resource used by the non-HSPA services is
little, the HS-PDSCH uses the rest idle codes as much
as possible, and the maximum number of idle codes
(SF=16 continuous codes) is equal to the value of
"Code Max Number for HS-PDSCH". For detailed
Unit:None
Default Value:5
CodeAdjForHsdpaSwitch
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061005
HSDPA Static Code

Code Allocation
Meaning:Whether to enable the HSDPA-based code

reshuffling function. When the HSDPA-based code
reshuffling function is enabled, codes occupied by R99
services are reshuffled in descending order of the
code number to release the shared code resources of
adjacent HSDPA UEs.
GUI Value Range:OFF(OFF), ON(ON)
Unit:None
Actual Value Range:OFF, ON
Default Value:ON(ON)
CodeAdjForHsdpaSwitch
BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061005
HSDPA Static Code

Code Allocation
Meaning:Whether to enable the HSDPA-based code

reshuffling function. When the HSDPA-based code
reshuffling function is enabled, codes occupied by R99
services are reshuffled in descending order of the
code number to release the shared code resources of
adjacent HSDPA UEs.
Unit:None
Default Value:ON(ON)
CodeAdjForHsdpaUserNumThd BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061005
HSDPA Static Code

Code Allocation
Meaning:H-based code tree reshuffle user number

threshold. When the switch "Code Adjust Switch for
HSDPA"is enabled, if the number of users on the tree
to be reshuffled is no greater than this parameter, the
reshuffle is allowed. Otherwise, the reshuffle is given
up. This parameter limits the number of users involved
in one reshuffle so that reshuffle on mass users at a
time is avoided.
Unit:None
Default Value:3
CodeAdjForHsdpaUserNumThd BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD01061005
HSDPA Static Code

Code Allocation
Meaning:H-based code tree reshuffle user number

threshold. When the switch "Code Adjust Switch for
HSDPA"is enabled, if the number of users on the tree
to be reshuffled is no greater than this parameter, the
reshuffle is allowed. Otherwise, the reshuffle is given
up. This parameter limits the number of users involved
in one reshuffle so that reshuffle on mass users at a
time is avoided.
Unit:None
Default Value:3
Page 45 of 69
MAXNONCONVERHARQRT
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
Meaning:Indicates the MAX HARQ Retransmission

Times of Non-Conversational service in CELL DCH
state.
Unit:None
Default Value:4
MAXEFACHHARQRT
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD-010688
Downlink Enhanced
CELL_FACH
Meaning:Indicates the maximum number of blind

HARQ retransmissions for E-FACH users.
Unit:None
Default Value:2
SM
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
Meaning:Indicates the HSDPA Scheduling Method.

PF: The differences between channel environments of
users are considered in order to ensure equity among
users. Enhanced PF: This algorithm is an
enhancement to PF. Channel quality is considered in
order to reach high resource efficiency and gain a high
system capacity. Round Robin: Scheduling
opportunities are allocated among users simply and
effectively on a polling basis. The system throughput is
low. Max C/I: This algorithm brings about the
maximum possible system throughput, but it cannot
ensures equity between users or meet users' QoS
requirements.
GUI Value Range:EPF(Enhanced PF), PF(PF), RR
(Round Robin), MAXCI(Max C/I), EPF_LOC(Location
based EPF)
Unit:None
Actual Value Range:EPF, PF, RR, MAXCI, EPF_LOC
Default Value:EPF(Enhanced PF)
HsPdschMPOConstEnum
BSC6900
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD-010610
WRFD01061004
HSDPA Introduction
Package
HSDPA Power
Control
Meaning:This parameter named Measure Power

Offset Constant is used to compute measurement
power offset. Measurement power offset is used by UE
to obtain total received HS-PDSCH power. The
calculation for Measure Power Offset is shown below:
Measure Power Offset = Max(-6, Min
(13,CellMaxPower - PcpichPower - Measure Power
OffsetConstant)). For details of the IE "Measure Power
Offset", see 3GPP TS 25.214.
GUI Value Range:Minus3.0DB(-3.0dB), Minus2.5DB(2.5dB), Minus2.0DB(-2.0dB), Minus1.5DB(-1.5dB),
Minus1.0DB(-1.0dB), Minus0.5DB(-0.5dB), 0.0DB
(0.0dB), 0.5DB(0.5dB), 1.0DB(1.0dB), 1.5DB(1.5dB),
2.0DB(2.0dB), 2.5DB(2.5dB), 3.0DB(3.0dB), 3.5DB
(3.5dB), 4.0DB(4.0dB), 4.5DB(4.5dB), 5.0DB(5.0dB),
5.5DB(5.5dB), 6.0DB(6.0dB), 6.5DB(6.5dB), 7.0DB
(7.0dB), 7.5DB(7.5dB), 8.0DB(8.0dB), 8.5DB(8.5dB),
9.0DB(9.0dB), 9.5DB(9.5dB), 10.0DB(10.0dB), 10.5DB
(10.5dB), 11.0DB(11.0dB), 11.5DB(11.5dB), 12.0DB
(12.0dB), 12.5DB(12.5dB), 13.0DB(13.0dB), 13.5DB
(13.5dB), 14.0DB(14.0dB), 14.5DB(14.5dB), 15.0DB
(15.0dB), 15.5DB(15.5dB), 16.0DB(16.0dB), 16.5DB
(16.5dB), 17.0DB(17.0dB), 17.5DB(17.5dB), 18.0DB
(18.0dB), 18.5DB(18.5dB), 19.0DB(19.0dB)
Unit:dB
Actual Value Range:-3.0, -2.5, -2.0, -1.5, -1.0, -0.5,
0.0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5,
6.0, 6.5, 7.0, 7.5, 8.0, 8.5, 9.0, 9.5, 10.0, 10.5, 11.0,
11.5, 12.0, 12.5, 13.0, 13.5, 14.0, 14.5, 15.0, 15.5,
16.0, 16.5, 17.0, 17.5, 18.0, 18.5, 19.0
Default Value:2.5DB(2.5dB)
HsPdschMPOConstEnum
BSC6910
ADD UCELLHSDPA
MOD UCELLHSDPA
WRFD-010610
WRFD01061004
HSDPA Introduction
Package
HSDPA Power
Control
Meaning:This parameter named Measure Power

Offset Constant is used to compute measurement
power offset. Measurement power offset is used by UE
to obtain total received HS-PDSCH power. The
calculation for Measure Power Offset is shown below:
Measure Power Offset = Max(-6, Min
(13,CellMaxPower - PcpichPower - Measure Power
OffsetConstant)). For details of the IE "Measure Power
Offset", see 3GPP TS 25.214.
GUI Value Range:Minus3.0DB(-3.0dB), Minus2.5DB(2.5dB), Minus2.0DB(-2.0dB), Minus1.5DB(-1.5dB),
Minus1.0DB(-1.0dB), Minus0.5DB(-0.5dB), 0.0DB
(0.0dB), 0.5DB(0.5dB), 1.0DB(1.0dB), 1.5DB(1.5dB),
2.0DB(2.0dB), 2.5DB(2.5dB), 3.0DB(3.0dB), 3.5DB
(3.5dB), 4.0DB(4.0dB), 4.5DB(4.5dB), 5.0DB(5.0dB),
5.5DB(5.5dB), 6.0DB(6.0dB), 6.5DB(6.5dB), 7.0DB
(7.0dB), 7.5DB(7.5dB), 8.0DB(8.0dB), 8.5DB(8.5dB),
9.0DB(9.0dB), 9.5DB(9.5dB), 10.0DB(10.0dB), 10.5DB
(10.5dB), 11.0DB(11.0dB), 11.5DB(11.5dB), 12.0DB
(12.0dB), 12.5DB(12.5dB), 13.0DB(13.0dB), 13.5DB
(13.5dB), 14.0DB(14.0dB), 14.5DB(14.5dB), 15.0DB
(15.0dB), 15.5DB(15.5dB), 16.0DB(16.0dB), 16.5DB
(16.5dB), 17.0DB(17.0dB), 17.5DB(17.5dB), 18.0DB
(18.0dB), 18.5DB(18.5dB), 19.0DB(19.0dB)
Unit:dB
Actual Value Range:-3.0, -2.5, -2.0, -1.5, -1.0, -0.5,
0.0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5,
6.0, 6.5, 7.0, 7.5, 8.0, 8.5, 9.0, 9.5, 10.0, 10.5, 11.0,
11.5, 12.0, 12.5, 13.0, 13.5, 14.0, 14.5, 15.0, 15.5,
16.0, 16.5, 17.0, 17.5, 18.0, 18.5, 19.0
Default Value:2.5DB(2.5dB)
HappyBR
BSC6900
SET UUSERHAPPYBR
WRFD01061010
HSDPA Flow Control
Meaning:Happy bit rate. This parameter defines the

happy bit rate of the best effort (BE) service with
different user priorities. The RNC sends the happy bit
Page 46 of 69
rate to the NodeB through the Iub interface. When the

NodeB resource is limited and the HS-DSCH bit rate of
the user exceeds the Happy bit rate, the HS-DSCH
scheduling priority will be decreased. When this
parameter is set to 0, it indicates that NodeB will not
adjust the HS-DSCH scheduling priority. This value of
parameter can be set by "HappyBR" in the "ADD
UOPERUSERHAPPYBR" command. If the value of
"HappyBR" in the "ADD UOPERUSERHAPPYBR"
command is larger than 5000, it will be set to the
minimum of the "HappyBR" parameter value in the
"SET UUSERHAPPYBR" and 5000.
Unit:kbit/s
Default Value:0
HappyBR
BSC6910
SET UUSERHAPPYBR
WRFD01061010
HSDPA Flow Control
Meaning:Happy bit rate. This parameter defines the

happy bit rate of the best effort (BE) service with
different user priorities. The RNC sends the happy bit
rate to the NodeB through the Iub interface. When the
NodeB resource is limited and the HS-DSCH bit rate of
the user exceeds the Happy bit rate, the HS-DSCH
scheduling priority will be decreased. When this
parameter is set to 0, it indicates that NodeB will not
adjust the HS-DSCH scheduling priority. This value of
parameter can be set by "HappyBR" in the "ADD
UOPERUSERHAPPYBR" command. If the value of
"HappyBR" in the "ADD UOPERUSERHAPPYBR"
command is larger than 5000, it will be set to the
minimum of the "HappyBR" parameter value in the
"SET UUSERHAPPYBR" and 5000.
Unit:kbit/s
Default Value:0
RSCLMSW
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061103
Scheduling based on
EPF and GBR
Meaning:Indicates the Resource Limiting Switch. The

function will be enabled if this parameter is set to
OPEN. When this switch is turned on, the resources
available to GBR users are restricted. When the
resource usage is above the threshold, the throughput
may be improved (for example, large GBRs configured
for users at the cell edge).
Unit:None
SPI
BSC6900
SET USPIWEIGHT
WRFD-020806
WRFD-020128
WRFD-020132
Differentiated Service
Based on SPI Weight
Quality Improvement
for Subscribed
Service
Web browsing
acceleration
Meaning:Relative priority when RAB data in the PS

domain is scheduled. The larger the value of this
parameter, the higher the scheduling priority. Values
2-11 indicate the scheduling priorities of background
and interactive services.Value 12 indicates the
scheduling priority of the streaming service. Value 13
indicates the scheduling priority of the conversational
service. Value 14 indicates the scheduling priority of
the IMS signaling. Value 15 indicates the scheduling
priority of the SRB service. Values 0 and 1 are
reserved for other services.
Unit:None
Default Value:None
SPI
BSC6910
SET USPIWEIGHT
WRFD-020806
WRFD-020128
WRFD-020132
Based on SPI Weight
Quality Improvement
for Subscribed
Service
Web browsing
acceleration
Meaning:Relative priority when RAB data in the PS

domain is scheduled. The larger the value of this
parameter, the higher the scheduling priority. Values
2-11 indicate the scheduling priorities of background
and interactive services.Value 12 indicates the
scheduling priority of the streaming service. Value 13
indicates the scheduling priority of the conversational
service. Value 14 indicates the scheduling priority of
the IMS signaling. Value 15 indicates the scheduling
priority of the SRB service. Values 0 and 1 are
reserved for other services.
Unit:None
Default Value:None
SpiWeight
BSC6900
SET USPIWEIGHT
WRFD-020806
WRFD-020128
WRFD-020132
Based on SPI Weight
Quality Improvement
for Subscribed
Service
Web browsing
acceleration
Meaning:Weight for service scheduling priority. This

weight is used in two algorithms. In scheduling
algorithm, it is used to adjust the handling priority for
different services. In Iub congestion algorithm, it is
used to allocate bandwidth for different services. If the
weight is higher, it is more possible to increase the
handling priority of the user or get more Iub bandwidth,
respectively.
Unit:%
Default Value:100
SpiWeight
BSC6910
SET USPIWEIGHT
WRFD-020806
WRFD-020128
WRFD-020132
Based on SPI Weight
Quality Improvement
for Subscribed
Service
Web browsing
acceleration
Meaning:Weight for service scheduling priority. This

weight is used in two algorithms. In scheduling
algorithm, it is used to adjust the handling priority for
different services. In Iub congestion algorithm, it is
used to allocate bandwidth for different services. If the
weight is higher, it is more possible to increase the
handling priority of the user or get more Iub bandwidth,
Page 47 of 69
respectively.
Unit:%
Default Value:100
LOCWEIGHT
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD-140221
HSDPA Scheduling
Based on UE
Location
Meaning:Indicates the weight of the EPF_LOC (user

location-based EPF) algorithm. A larger parameter
value indicates more factors that should be considered
for user location-based HSDPA scheduling scheme.
GUI Value Range:0, 1, 2, 3
Unit:None
Actual Value Range:0, 1, 2, 3
Default Value:1
MXPWRPHUSR
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
Meaning:Indicates the Max Power Per Hs-user.

Unit:%
Default Value:100
RSCALLOCM
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
Meaning:Indicates the Resource Allocate Method.

Radio resources indicate HSDPA available power
resources and code resources. Code Priority: The
code resource priority allocation scheme mainly
applies to scenarios where power resources are
limited. In scenarios where power resources are not
limited, this scheme lowers the system throughput.
Power Priority: The power resource priority allocation
scheme mainly applies to scenarios where code
resources are limited. In scenarios where code
resources are not limited, this scheme lowers the
system throughput. Balance between Code and
Power: The power-code balanced scheme avoids
exhaustion of either type of resources, improves the
resource use efficiency and improves the cell capacity.
GUI Value Range:CODE_PRI(Code Priority),
POWER_PRI(Power Priority), POWERCODE_BAL
(Balance between Code and Power)
Unit:None
Actual Value Range:CODE_PRI, POWER_PRI,
POWERCODE_BAL
Default Value:POWERCODE_BAL(Balance between
Code and Power)
CQIADJALGOFNONCON
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD01061004
HSDPA Power
Control
Meaning:Indicates the Channel Quality Indicator(CQI)

Adjust Algorithm Switch of non-Conversational
Service. Not CQI Adjust Algorithm: CQI correction is
not performed. CQI Adjusted by IBLER: CQI correction
is performed for non-conversational services based on
the fixed IBLER. The IBLER will converge to this target
value.
GUI Value Range:NO_CQI_ADJ(Not CQI Adjust
Algorithm), CQI_ADJ_BY_IBLER(CQI Adjusted by
IBLER), CQI_ADJ_BY_DYN_BLER(CQI Adjusted by
Dynamic BLER)
Unit:None
Actual Value Range:NO_CQI_ADJ,
CQI_ADJ_BY_IBLER, CQI_ADJ_BY_DYN_BLER
Default Value:NO_CQI_ADJ(Not CQI Adjust
Algorithm)
BURSTBLEROPTSW
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
None
None
Meaning:When this switch is turned on, estimated

channel environment errors are corrected for burst
services and full buffer services at the startup of data
transmission to optimize the BLER.
Unit:None
Default Value:OFF(OFF)
SWITCH
BTS3900
ADD
DLFLOWCTRLPARA
SET
DLFLOWCTRLPARA
WRFD01061010
HSDPA Flow Control
Meaning:Indicates the switch for the DL flow control

algorithm. If this parameter is set to
DYNAMIC_BW_SHAPING, flow allocation for HSDPA
users is performed according to the delay and packet
loss of the transmission interface board in
STATIC_BW_SHAPING mode. This function requires
the network controller using the switch of the 3GPP R6
protocol. Therefore, you are advised to use this
function with the RNC that complies with the 3GPP R6
protocol. If this parameter is set to NO_BW_SHAPING,
the BS does not allocate bandwidth according to the
configuration and delay of the transmission interface
board. The BS reports the air interface conditions to
the controller, and then the controller allocates
bandwidth. When this parameter is set to
NO_BW_SHAPING, the backpressure function must
be enabled on the controller side. If this parameter is
set to BW_SHAPING_ONOFF_TOGGLE, the BS
automatically selects either DYNAMIC_BW_SHAPING
or NO_BW_SHAPING during a flow congestion
detection on a port. That is, DYNAMIC_BW_SHAPING
is selected if congestion is detected;
NO_BW_SHAPING is selected if congestion is not
detected for a certain period of time.
GUI Value Range:STATIC_BW_SHAPING
(STATIC_BW_SHAPING), DYNAMIC_BW_SHAPING
(DYNAMIC_BW_SHAPING), NO_BW_SHAPING
(NO_BW_SHAPING),
BW_SHAPING_ONOFF_TOGGLE
(BW_SHAPING_ONOFF_TOGGLE)
Page 48 of 69
Unit:None
Actual Value Range:STATIC_BW_SHAPING,
DYNAMIC_BW_SHAPING, NO_BW_SHAPING,
BW_SHAPING_ONOFF_TOGGLE
Default Value:BW_SHAPING_ONOFF_TOGGLE
(BW_SHAPING_ONOFF_TOGGLE)
CME16QAMSW
BTS3900
SET
ULOCELLMACHSPARA
LST
ULOCELLMACHSPARA
WRFD-010629
DL 16QAM
Modulation
Meaning:Indicates the 16QAM Switch. The function

will be enabled if this parameter is set to OPEN. When
this switch is turned on, the cell throughput improves.
Unit:None
NBMCacAlgoSwitch
BSC6900
ADD
UCELLALGOSWITCH
MOD
UCELLALGOSWITCH
WRFD-020101
WRFD-020102
WRFD-010202
WRFD-021102
WRFD-020117
WRFD-020136
WRFD-010653
WRFD-010654
WRFD-140223
WRFD-020122
WRFD-021104
Admission Control
Load Measurement
UE State in
Connected Mode
(CELL-DCH
CELL-PCH
URA-PCH
CELL-FACH)
Cell Barring
Multi-Carrier Switch
off Based on Traffic
Load
Anti-Interference
Scheduling for
HSUPA
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
MOCN Cell Resource
Demarcation
off Based on QoS
Emergency Call
Meaning:Whether to enable the algorithms related to

cell service admission. Selecting a switch enables the
corresponding algorithm and clearing a switch disables
the corresponding algorithm. 1. CRD_ADCTRL:
Whether to enable the credit admission control
algorithm. The credit admission control algorithm is
valid only when this switch is turned on and the
NODEB_CREDIT_CAC_SWITCH check box under the
"CAC algorithm switch" parameter in the "SET
UCACALGOSWITCH" command is selected. 2.
HSDPA_UU_ADCTRL: Whether to enable air-interface
load admission control algorithm for HSDPA UEs who
process uplink services over the DCHs and downlink
services over the HSDPA channels. This switch does
not take effect for UEs who process uplink services
over the HSUPA channels and downlink services over
the HSDPA channels. 3. HSUPA_UU_ADCTRL:
Whether to enable air-interface load admission control
algorithm for HSUPA UEs who process uplink services
the DCHs. This switch does not take effect for UEs
who process uplink services over the HSUPA
channels and downlink services over the HSDPA
channels. 4. MBMS_UU_ADCTRL: Whether to enable
air-interface load admission control algorithm for
Multimedia Broadcast Multicast Service (MBMS) UEs.
5. HSDPA_GBP_MEAS: Whether to enable GBP
measurement for HSDPA UEs. The NodeB reports the
GBP of HSDPA UEs to the RNC only after the
measurement is enabled. 6. HSDPA_PBR_MEAS:
Whether to enable provided bit rate (PBR)
PBR of HSDPA UEs to the RNC only after the
measurement is enabled. 7.
SYS_INFO_UPDATE_FOR_IU_RST: Whether to
update system information after the Iub interface
resets. The cell barring function in the event of Iu
interface faults can be enabled only when this switch is
turned on and the
SYS_INFO_UPDATE_FOR_IU_RST (RNC-level
switch) check box under the "Process switch"
parameter in the "SET URRCTRLSWITCH" command
is selected. 8. HSUPA_PBR_MEAS: Whether to
enable PBR measurement for HSUPA UEs. The
NodeB reports the PBR of HSUPA UEs to the RNC
only after the measurement is enabled. 9.
HSUPA_EDCH_RSEPS_MEAS: Whether to enable
the periodic measurement of total receive power
generated by scheduling services on E-DCHs. 10.
EMC_UU_ADCTRL: Whether to enable power
admission control for UEs initiating emergency calls.
11. Received total wideband
power_RESIST_DISTURB: Whether to enable antiinference processing when Received Total Wideband
Power (RTWP) is abnormal. 12.
SIGNALING_SHO_UL_AC_SWITCH: Whether to
enable uplink power-based soft handover control for
UEs who have established RRC connections but
process no services. If this switch is turned on, such
UEs cannot access target cells by using soft
handovers if the target cells are in the OLC state in the
uplink. 13. FACH_UU_ADCTRL: Whether to enable
admission control for UEs that establish services on
FACHs. If this switch is turned on and a UE initiates an
RAB or RRC connection setup request (with a cause
value other than Detach, Registration, or Emergency
Call) in an overloaded cell, the setup request is
rejected. If the cell is not overloaded, the FACH user
admission procedure is initiated and the UE can
access the cell after the procedure succeeds. If this
switch is turned off, the FACH user admission
procedure is initiated regardless of whether the cell is
overloaded and the UE can access the cell after the
procedure succeeds. 14.
MIMOCELL_LEGACYHSDPA_ADCTRL: Whether to
enable admission control for common HSDPA UEs in
MIMO cells. 15. FAST_DORMANCY_ADCTRL:
Whether to enable admission control for fast
dormancy-capable UEs. This switch is used to
alleviate FACH congestion by disabling state migration
for fast dormancy-capable UEs in the CELL-DCH
state. If this switch is turned off for many cells under
the RNC, signaling storms occur and CPU usage on
the RNC, NodeB, and SGSN increases significantly,
affecting service access. The function corresponding
to this switch has been deleted in R13, and this switch
is invalid. 16. FACH_USER_NUM_NOT_CTRL:
Whether to restrict the number of admitted FACH UEs.
GUI Value Range:CRD_ADCTRL(Credit Admission
Page 49 of 69
Control Algorithm), HSDPA_UU_ADCTRL(HSDPA UU

Load Admission Control Algorithm),
HSUPA_UU_ADCTRL(HSUPA UU Load Admission
Control Algorithm), MBMS_UU_ADCTRL(MBMS UU
HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm),
HSDPA_PBR_MEAS(HSDPA PBR Meas Algorithm),
SYS_INFO_UPDATE_FOR_IU_RST(System Info
Update Switch for Iu Reset), HSUPA_PBR_MEAS
(HSUPA PBR Meas Algorithm),
HSUPA_EDCH_RSEPS_MEAS(HSUPA EDCH
RSEPS Meas Algorithm), EMC_UU_ADCTRL
(emergency call power admission),
RTWP_RESIST_DISTURB(RTWP Resist Disturb
Switch), SIGNALING_SHO_UL_AC_SWITCH
(Signaling Sho Ul power cac switch),
FACH_UU_ADCTRL(FACH power cac switch),
MIMOCELL_LEGACYHSDPA_ADCTRL(Legacy
HSDPA Admission Control Algorithm in MIMO Cell ),
FAST_DORMANCY_ADCTRL(Fast Dormancy User
Admission Control Algorithm),
FACH_USER_NUM_NOT_CTRL(FACH USER
UNLIMITED)
Unit:None
Actual Value Range:CRD_ADCTRL,
HSDPA_UU_ADCTRL, HSUPA_UU_ADCTRL,
MBMS_UU_ADCTRL, HSDPA_GBP_MEAS,
HSDPA_PBR_MEAS,
SYS_INFO_UPDATE_FOR_IU_RST,
HSUPA_PBR_MEAS,
HSUPA_EDCH_RSEPS_MEAS, EMC_UU_ADCTRL,
RTWP_RESIST_DISTURB,
SIGNALING_SHO_UL_AC_SWITCH,
FACH_UU_ADCTRL,
MIMOCELL_LEGACYHSDPA_ADCTRL,
FAST_DORMANCY_ADCTRL,
FACH_USER_NUM_NOT_CTRL
Default Value:CRD_ADCTRL1&HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL0&MBMS_UU_ADCTRL-0&HSDPA_GBP_MEAS0&HSDPA_PBR_MEAS0&SYS_INFO_UPDATE_FOR_IU_RST0&HSUPA_PBR_MEAS0&HSUPA_EDCH_RSEPS_MEAS0&EMC_UU_ADCTRL-1&RTWP_RESIST_DISTURB0&SIGNALING_SHO_UL_AC_SWITCH0&FACH_UU_ADCTRL0&MIMOCELL_LEGACYHSDPA_ADCTRL0&FAST_DORMANCY_ADCTRL1&FACH_USER_NUM_NOT_CTRL-0
NBMCacAlgoSwitch
BSC6910
ADD
UCELLALGOSWITCH
MOD
UCELLALGOSWITCH
WRFD-020101
WRFD-020102
WRFD-010202
WRFD-021102
WRFD-020117
WRFD-020136
WRFD-010653
WRFD-010654
WRFD-140223
WRFD-020122
WRFD-021104
Admission Control
Load Measurement
UE State in
Connected Mode
(CELL-DCH
CELL-PCH
URA-PCH
CELL-FACH)
Cell Barring
off Based on Traffic
Load
Anti-Interference
Scheduling for
HSUPA
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
MOCN Cell Resource
Demarcation
off Based on QoS
Emergency Call
Meaning:Whether to enable the algorithms related to

cell service admission. Selecting a switch enables the
corresponding algorithm and clearing a switch disables
the corresponding algorithm. 1. CRD_ADCTRL:
Whether to enable the credit admission control
algorithm. The credit admission control algorithm is
valid only when this switch is turned on and the
NODEB_CREDIT_CAC_SWITCH check box under the
"CAC algorithm switch" parameter in the "SET
UCACALGOSWITCH" command is selected. 2.
HSDPA_UU_ADCTRL: Whether to enable air-interface
load admission control algorithm for HSDPA UEs who
process uplink services over the DCHs and downlink
services over the HSDPA channels. This switch does
not take effect for UEs who process uplink services
the HSDPA channels. 3. HSUPA_UU_ADCTRL:
Whether to enable air-interface load admission control
algorithm for HSUPA UEs who process uplink services
the DCHs. This switch does not take effect for UEs
who process uplink services over the HSUPA
channels and downlink services over the HSDPA
channels. 4. MBMS_UU_ADCTRL: Whether to enable
air-interface load admission control algorithm for
Multimedia Broadcast Multicast Service (MBMS) UEs.
5. HSDPA_GBP_MEAS: Whether to enable GBP
GBP of HSDPA UEs to the RNC only after the
measurement is enabled. 6. HSDPA_PBR_MEAS:
Whether to enable provided bit rate (PBR)
PBR of HSDPA UEs to the RNC only after the
measurement is enabled. 7.
SYS_INFO_UPDATE_FOR_IU_RST: Whether to
update system information after the Iub interface
resets. The cell barring function in the event of Iu
interface faults can be enabled only when this switch is
turned on and the
SYS_INFO_UPDATE_FOR_IU_RST (RNC-level
switch) check box under the "Process switch"
parameter in the "SET URRCTRLSWITCH" command
is selected. 8. HSUPA_PBR_MEAS: Whether to
enable PBR measurement for HSUPA UEs. The
NodeB reports the PBR of HSUPA UEs to the RNC
only after the measurement is enabled. 9.
HSUPA_EDCH_RSEPS_MEAS: Whether to enable
the periodic measurement of total receive power
generated by scheduling services on E-DCHs. 10.
EMC_UU_ADCTRL: Whether to enable power
admission control for UEs initiating emergency calls.
11. Received total wideband
power_RESIST_DISTURB: Whether to enable anti-
Page 50 of 69
inference processing when Received Total Wideband

Power (RTWP) is abnormal. 12.
SIGNALING_SHO_UL_AC_SWITCH: Whether to
enable uplink power-based soft handover control for
UEs who have established RRC connections but
process no services. If this switch is turned on, such
UEs cannot access target cells by using soft
handovers if the target cells are in the OLC state in the
uplink. 13. FACH_UU_ADCTRL: Whether to enable
admission control for UEs that establish services on
FACHs. If this switch is turned on and a UE initiates an
RAB or RRC connection setup request (with a cause
value other than Detach, Registration, or Emergency
Call) in an overloaded cell, the setup request is
rejected. If the cell is not overloaded, the FACH user
admission procedure is initiated and the UE can
access the cell after the procedure succeeds. If this
switch is turned off, the FACH user admission
procedure is initiated regardless of whether the cell is
overloaded and the UE can access the cell after the
procedure succeeds. 14.
MIMOCELL_LEGACYHSDPA_ADCTRL: Whether to
enable admission control for common HSDPA UEs in
MIMO cells. 15. FAST_DORMANCY_ADCTRL:
Whether to enable admission control for fast
dormancy-capable UEs. This switch is used to
alleviate FACH congestion by disabling state migration
for fast dormancy-capable UEs in the CELL-DCH
state. If this switch is turned off for many cells under
the RNC, signaling storms occur and CPU usage on
the RNC, NodeB, and SGSN increases significantly,
affecting service access. The function corresponding
to this switch has been deleted in R13, and this switch
is invalid. 16. FACH_USER_NUM_NOT_CTRL:
Whether to restrict the number of admitted FACH UEs.
GUI Value Range:CRD_ADCTRL(Credit Admission
Control Algorithm), HSDPA_UU_ADCTRL(HSDPA UU
HSUPA_UU_ADCTRL(HSUPA UU Load Admission
Control Algorithm), MBMS_UU_ADCTRL(MBMS UU
HSDPA_GBP_MEAS(HSDPA GBP Meas Algorithm),
HSDPA_PBR_MEAS(HSDPA PBR Meas Algorithm),
SYS_INFO_UPDATE_FOR_IU_RST(System Info
Update Switch for Iu Reset), HSUPA_PBR_MEAS
(HSUPA PBR Meas Algorithm),
HSUPA_EDCH_RSEPS_MEAS(HSUPA EDCH
RSEPS Meas Algorithm), EMC_UU_ADCTRL
(emergency call power admission),
RTWP_RESIST_DISTURB(RTWP Resist Disturb
Switch), SIGNALING_SHO_UL_AC_SWITCH
(Signaling Sho Ul power cac switch),
FACH_UU_ADCTRL(FACH power cac switch),
MIMOCELL_LEGACYHSDPA_ADCTRL(Legacy
HSDPA Admission Control Algorithm in MIMO Cell ),
FAST_DORMANCY_ADCTRL(Fast Dormancy User
Admission Control Algorithm),
FACH_USER_NUM_NOT_CTRL(FACH USER
UNLIMITED)
Unit:None
Actual Value Range:CRD_ADCTRL,
HSDPA_UU_ADCTRL, HSUPA_UU_ADCTRL,
MBMS_UU_ADCTRL, HSDPA_GBP_MEAS,
HSDPA_PBR_MEAS,
SYS_INFO_UPDATE_FOR_IU_RST,
HSUPA_PBR_MEAS,
HSUPA_EDCH_RSEPS_MEAS, EMC_UU_ADCTRL,
RTWP_RESIST_DISTURB,
SIGNALING_SHO_UL_AC_SWITCH,
FACH_UU_ADCTRL,
MIMOCELL_LEGACYHSDPA_ADCTRL,
FAST_DORMANCY_ADCTRL,
FACH_USER_NUM_NOT_CTRL
Default Value:CRD_ADCTRL1&HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL0&MBMS_UU_ADCTRL-0&HSDPA_GBP_MEAS0&HSDPA_PBR_MEAS0&SYS_INFO_UPDATE_FOR_IU_RST0&HSUPA_PBR_MEAS0&HSUPA_EDCH_RSEPS_MEAS0&EMC_UU_ADCTRL-1&RTWP_RESIST_DISTURB0&SIGNALING_SHO_UL_AC_SWITCH0&FACH_UU_ADCTRL0&MIMOCELL_LEGACYHSDPA_ADCTRL0&FAST_DORMANCY_ADCTRL1&FACH_USER_NUM_NOT_CTRL-0
HspaPlusSwitch
BSC6900
ADD
UCELLALGOSWITCH
MOD
UCELLALGOSWITCH
WRFD-010685
WRFD-010688
WRFD-010683
WRFD-010684
WRFD-010686
WRFD-010687
WRFD-010702
WRFD-010693
WRFD-010694
WRFD-010695
WRFD-010696
WRFD-010697
WRFD-010699
WRFD-150209
WRFD-150207
Downlink Enhanced
L2
Downlink Enhanced
CELL_FACH
Downlink 64QAM
2x2 MIMO
CPC - DTX / DRX
CPC - HS-SCCH less
operation
Enhanced DRX
DL 64QAM+MIMO
UL 16QAM
UL Layer 2
Improvement
DC-HSDPA
Meaning:This parameter is used to select a feature

related to HSPA+. If a feature is selected, it indicates
that the corresponding algorithm is enabled. If a
feature is not selected, it indicates that the
corresponding algorithm is disabled. Note that other
factors such as license and the physical capability of
NodeB restrict whether a feature can be used even if
this feature is selected. The EFACH/MIMO switch
determines whether the cell supports the EFACH/MIMO feature but does not affect the
establishment of the E-FACH and the MIMO cell. 1.
64QAM: When the switch is on, 64QAM can be
configured for the HSDPA service. 2. MIMO: When the
switch is on, MIMO can be configured for the HSDPA
service.The MIMO switch determines whether the cell
supports the MIMO feature but does not affect the
establishment of the the MIMO cell. 3. E_FACH: When
HspaPlusSwitch
BSC6910
ADD
UCELLALGOSWITCH
MOD
UCELLALGOSWITCH
Page 51 of 69
WRFD-150227
WRFD-010701
WRFD-140204
WRFD-150223
E-DPCCH Boosting
DC-HSDPA+MIMO
DB-HSDPA
4C-HSDPA
DB-HSDPA+MIMO
Uplink Enhanced
CELL_FACH
DC-HSUPA
MC-HSDPA+MIMO
the switch is on, E_FACH can be configured for the

HSDPA service.The E_FACH switch determines
whether the cell supports the E_FACH feature but
does not affect the establishment of the the MIMO cell.
4. DTX_DRX: When the switch is on, DTX_DRX can
be configured for the HSPA service. 5.
HS_SCCH_LESS_OPERATION: When the switch is
on, HS-SCCH Less Operation can be configured for
the HSPA service. 6. DL_L2ENHANCED: When the
switch is on, DL_L2ENHANCED can be configured for
the HSDPA service. 7. 64QAM_MIMO: When the
switch is on and the switches for 64QAM and MIMO
are on, 64QAM+MIMO can be configured for the
HSDPA service 8. UL_16QAM: When the switch is on,
16QAM can be configured for the HSUPA service. 9.
DC_HSDPA: When the switch is on, DC can be
configured for the HSDPA service. 10.
UL_L2ENHANCED: When the switch is on,
UL_L2ENHANCED can be configured for the HSUPA
service. 11. EDPCCH_BOOSTING: When the switch is
on, Boosting can be configured for the HSUPA
service. 12. DCMIMO_HSDPA: When this switch is
turned on, DC+MIMO can be configured for the
HSDPA service. 13. E_DRX: When the switch is on,
E_DRX can be configured for the HSUPA service. 14.
DC_HSUPA: When this switch is turned on, the DCHSUPA function can be enabled for HSUPA services.
15. HSDPA_4C_MIMO: Whether the 4CHSDPA+MIMO feature is allowed for HSDPA services.
When this switch is turned on, the 4C-HSDPA+MIMO
feature is allowed for HSDPA services. 16.
HSDPA_4C: Whether the 4C-HSDPA feature is
allowed for HSDPA services. When this switch is
turned on, the 4C-HSDPA feature is allowed for
HSDPA services. 17. DBMIMO_HSDPA: Whether the
DB-HSDPA+MIMO feature is allowed for HSDPA
services. When this switch is turned on, the DBHSDPA+MIMO feature is allowed for HSDPA services.
18. DB_HSDPA: Whether the DB-HSDPA feature is
turned on, the DB-HSDPA feature is allowed for
HSDPA services.
GUI Value Range:64QAM(Cell 64QAM Function
Switch), MIMO(Cell MIMO Function Switch), E_FACH
(Cell E_FACH Function Switch), DTX_DRX(Cell
DTX_DRX Function Switch),
HS_SCCH_LESS_OPERATION(Cell HS_SCCH LESS
OPERATION Function Switch), DL_L2ENHANCED
(Cell DL L2ENHANCED Function Switch),
64QAM_MIMO(Cell 64QAM+MIMO Function Switch),
UL_16QAM(Cell UL 16QAM Function Switch),
DC_HSDPA(Cell DC-HSDPA Function Switch),
UL_L2ENHANCED(Cell UL L2ENHANCED Function
Switch), EDPCCH_BOOSTING(Cell E-DPCCH
Boosting Function Switch), DCMIMO_HSDPA(Cell
DC-HSDPA Combined with MIMO Function Switch),
E_DRX(Enhanced Discontinuous Reception Function
Switch), DC_HSUPA(Cell DC-HSUPA Function
Switch), HSDPA_4C_MIMO(4C-HSDPA+MIMO
Function Switch), HSDPA_4C(4C-HSDPA Function
Switch), DBMIMO_HSDPA(DB-HSDPA+MIMO
Function Switch), DB_HSDPA(DB-HSDPA Function
Switch)
Unit:None
Actual Value Range:64QAM, MIMO, E_FACH,
DTX_DRX, HS_SCCH_LESS_OPERATION,
DL_L2ENHANCED, 64QAM_MIMO, UL_16QAM,
DC_HSDPA, UL_L2ENHANCED,
EDPCCH_BOOSTING, DCMIMO_HSDPA, E_DRX,
DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
DBMIMO_HSDPA, DB_HSDPA
Default Value:64QAM-0&MIMO-0&E_FACH0&DTX_DRX-0&HS_SCCH_LESS_OPERATION0&DL_L2ENHANCED-0&64QAM_MIMO0&UL_16QAM-0&DC_HSDPA-0&UL_L2ENHANCED0&EDPCCH_BOOSTING-0&DCMIMO_HSDPA0&E_DRX-0&DC_HSUPA-0&HSDPA_4C_MIMO0&HSDPA_4C-0&DBMIMO_HSDPA-0&DB_HSDPA-0
WRFD-010685
WRFD-010688
WRFD-010683
WRFD-010684
WRFD-010686
WRFD-010687
WRFD-010702
WRFD-010693
WRFD-010694
WRFD-010695
WRFD-010696
WRFD-010697
WRFD-010699
WRFD-150209
WRFD-150207
WRFD-150227
WRFD-010701
WRFD-140204
WRFD-150223
Downlink Enhanced
L2
Downlink Enhanced
CELL_FACH
Downlink 64QAM
2x2 MIMO
CPC - DTX / DRX
CPC - HS-SCCH less
operation
Enhanced DRX
DL 64QAM+MIMO
UL 16QAM
UL Layer 2
Improvement
DC-HSDPA
E-DPCCH Boosting
DC-HSDPA+MIMO
DB-HSDPA
4C-HSDPA
DB-HSDPA+MIMO
Uplink Enhanced
CELL_FACH
Meaning:This parameter is used to select a feature

related to HSPA+. If a feature is selected, it indicates
that the corresponding algorithm is enabled. If a
feature is not selected, it indicates that the
corresponding algorithm is disabled. Note that other
factors such as license and the physical capability of
NodeB restrict whether a feature can be used even if
this feature is selected. The EFACH/MIMO switch
determines whether the cell supports the EFACH/MIMO feature but does not affect the
establishment of the E-FACH and the MIMO cell. 1.
64QAM: When the switch is on, 64QAM can be
configured for the HSDPA service. 2. MIMO: When the
switch is on, MIMO can be configured for the HSDPA
service.The MIMO switch determines whether the cell
supports the MIMO feature but does not affect the
establishment of the the MIMO cell. 3. E_FACH: When
the switch is on, E_FACH can be configured for the
HSDPA service.The E_FACH switch determines
whether the cell supports the E_FACH feature but
does not affect the establishment of the the MIMO cell.
4. DTX_DRX: When the switch is on, DTX_DRX can
be configured for the HSPA service. 5.
HS_SCCH_LESS_OPERATION: When the switch is
on, HS-SCCH Less Operation can be configured for
DraSwitch
BSC6900
WRFDSET
UCORRMALGOSWITCH 01061111
WRFD01061208
WRFD01061404
WRFD-011502
WRFD-021101
WRFD-050405
WRFD-050408
WRFD-010690
WRFD01061403
WRFD-010202
WRFD-010507
WRFD-020106
WRFD-010653
WRFD-010654
WRFD-020131
WRFD-020128
WRFD-010301
WRFD-010302
WRFD-010801
WRFD-010802
WRFD-010901
WRFD-010902
Page 52 of 69
DC-HSUPA
MC-HSDPA+MIMO
the HSPA service. 6. DL_L2ENHANCED: When the

switch is on, DL_L2ENHANCED can be configured for
the HSDPA service. 7. 64QAM_MIMO: When the
switch is on and the switches for 64QAM and MIMO
are on, 64QAM+MIMO can be configured for the
HSDPA service 8. UL_16QAM: When the switch is on,
16QAM can be configured for the HSUPA service. 9.
DC_HSDPA: When the switch is on, DC can be
configured for the HSDPA service. 10.
UL_L2ENHANCED: When the switch is on,
UL_L2ENHANCED can be configured for the HSUPA
service. 11. EDPCCH_BOOSTING: When the switch is
on, Boosting can be configured for the HSUPA
service. 12. DCMIMO_HSDPA: When this switch is
turned on, DC+MIMO can be configured for the
HSDPA service. 13. E_DRX: When the switch is on,
E_DRX can be configured for the HSUPA service. 14.
DC_HSUPA: When this switch is turned on, the DCHSUPA function can be enabled for HSUPA services.
15. HSDPA_4C_MIMO: Whether the 4CHSDPA+MIMO feature is allowed for HSDPA services.
When this switch is turned on, the 4C-HSDPA+MIMO
feature is allowed for HSDPA services. 16.
HSDPA_4C: Whether the 4C-HSDPA feature is
turned on, the 4C-HSDPA feature is allowed for
HSDPA services. 17. DBMIMO_HSDPA: Whether the
DB-HSDPA+MIMO feature is allowed for HSDPA
services. When this switch is turned on, the DBHSDPA+MIMO feature is allowed for HSDPA services.
18. DB_HSDPA: Whether the DB-HSDPA feature is
turned on, the DB-HSDPA feature is allowed for
HSDPA services.
GUI Value Range:64QAM(Cell 64QAM Function
Switch), MIMO(Cell MIMO Function Switch), E_FACH
(Cell E_FACH Function Switch), DTX_DRX(Cell
DTX_DRX Function Switch),
HS_SCCH_LESS_OPERATION(Cell HS_SCCH LESS
OPERATION Function Switch), DL_L2ENHANCED
(Cell DL L2ENHANCED Function Switch),
64QAM_MIMO(Cell 64QAM+MIMO Function Switch),
UL_16QAM(Cell UL 16QAM Function Switch),
DC_HSDPA(Cell DC-HSDPA Function Switch),
UL_L2ENHANCED(Cell UL L2ENHANCED Function
Switch), EDPCCH_BOOSTING(Cell E-DPCCH
Boosting Function Switch), DCMIMO_HSDPA(Cell
DC-HSDPA Combined with MIMO Function Switch),
E_DRX(Enhanced Discontinuous Reception Function
Switch), DC_HSUPA(Cell DC-HSUPA Function
Switch), HSDPA_4C_MIMO(4C-HSDPA+MIMO
Function Switch), HSDPA_4C(4C-HSDPA Function
Switch), DBMIMO_HSDPA(DB-HSDPA+MIMO
Function Switch), DB_HSDPA(DB-HSDPA Function
Switch)
Unit:None
Actual Value Range:64QAM, MIMO, E_FACH,
DTX_DRX, HS_SCCH_LESS_OPERATION,
DL_L2ENHANCED, 64QAM_MIMO, UL_16QAM,
DC_HSDPA, UL_L2ENHANCED,
EDPCCH_BOOSTING, DCMIMO_HSDPA, E_DRX,
DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
DBMIMO_HSDPA, DB_HSDPA
Default Value:64QAM-0&MIMO-0&E_FACH0&DTX_DRX-0&HS_SCCH_LESS_OPERATION0&DL_L2ENHANCED-0&64QAM_MIMO0&UL_16QAM-0&DC_HSDPA-0&UL_L2ENHANCED0&EDPCCH_BOOSTING-0&DCMIMO_HSDPA0&E_DRX-0&DC_HSUPA-0&HSDPA_4C_MIMO0&HSDPA_4C-0&DBMIMO_HSDPA-0&DB_HSDPA-0
HSDPA State
Transition
HSUPA DCCC
HSUPA 2ms/10ms
TTI Handover
Active Queue
Management (AQM)
Dynamic Channel
(DCCC)
Overbooking on ATM
Transmission
Overbooking on IP
Transmission
TTI Switch for BE
Services Based on
Coverage
HSUPA 2ms TTI
UE State in
Connected Mode
(CELL-DCH
CELL-PCH
URA-PCH
CELL-FACH)
Rate Negotiation at
Admission Control
Load Reshuffling
96 HSDPA Users per
Cell
128 HSDPA Users
Meaning:Dynamic resource allocation switch group. 1.

DRA_AQM_SWITCH: When the switch is on, the
active queue management algorithm is used for the
RNC. 2.
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH:
When the switch is on, the TTI dynamic adjustment
algorithm for admission CE-based BE services applies
to the UE with the UL enhanced L2 feature. This
parameter is valid when
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH
(DraSwitch) is set to ON. 3.
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH:
algorithm is supported for admission CE-based BE
services. 4.
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH:
algorithm for coverage-based BE services applies to
the UE with the UL enhanced L2 feature. This
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH:
algorithm is supported for coverage-based BE
services. 6.
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH: When
the switch is on, the TTI dynamic adjustment algorithm
for differentiation-based BE services applies to the UE
with the UL enhanced L2 feature. This parameter is
valid when
DRA_BASE_RES_BE_TTI_RECFG_SWITCH
Page 53 of 69
per Cell
Optimization of R99
and HSUPA Users
Fairness
Quality Improvement
for Subscribed
Service
Paging UE in Idle
CELL_PCH
URA_PCH State
(Type 1)
Paging UE in
CELL_FACH
CELL_DCH State
(Type 2)
Intra RNC Cell
Update
Inter RNC Cell
Update
Intra RNC URA
Update
Inter RNC URA
Update
DRA_BASE_RES_BE_TTI_RECFG_SWITCH: When
is supported for differentiation-based BE services. 8.
DRA_DCCC_SWITCH: When the switch is on, the
dynamic channel reconfiguration control algorithm is
used for the RNC. 9.
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH:
When the switch is on, flow control is enabled for
HSDPA services in AM mode. 10.
DRA_HSDPA_STATE_TRANS_SWITCH: When the
switch is on, the status of the UE RRC that carrying
HSDPA services can be changed to CELL_FACH at
the RNC. If a PS BE service is carried over the HSDSCH, the switch PS_BE_STATE_TRANS_SWITCH
should be on simultaneously. If a PS real-time service
is carried over the HS-DSCH, the switch
PS_NON_BE_STATE_TRANS_SWITCH should be on
simultaneously. 11. DRA_HSUPA_DCCC_SWITCH:
When the switch is on, the DCCC algorithm is used for
HSUPA. The DCCC switch must be also on before this
switch takes effect. 12.
DRA_HSUPA_STATE_TRANS_SWITCH: When the
HSUPA services can be changed to CELL_FACH at
the RNC. If a PS BE service is carried over the EDCH, the switch PS_BE_STATE_TRANS_SWITCH
is carried over the E-DCH, the switch
simultaneously. 13.
DRA_IP_SERVICE_QOS_SWITCH: Switch of the
algorithm for increasing the quality of subscribed
services. When this parameter is set to ON, the
service priority weight of the subscriber whose key
parameters (IP Address, IP Port, and IP Protocol
Type) match the specified ones can be adjusted. In
this way, the QoS is improved. 14.
DRA_PS_BE_STATE_TRANS_SWITCH: When this
switch is turned on, UEs can be transited among the
CELL_DCH, CELL_FACH, CELL_PCH, and
URA_PCH states when they are processing PS BE
services. 15.
DRA_PS_NON_BE_STATE_TRANS_SWITCH: When
this switch is turned on, UEs can be transited between
the CELL_DCH and CELL_FACH states when they
are processing real-time PS services. 16.
DRA_R99_DL_FLOW_CONTROL_SWITCH: Under a
poor radio environment, the QoS of high speed
services drops considerably and the TX power is
overly high. In this case, the RNC can set restrictions
on low data rate transmission formats based on the
transmission quality, thus lowering traffic speed and
TX power. When the switch is on, the R99 downlink
flow control function is enabled. 17.
DRA_THROUGHPUT_DCCC_SWITCH: When the
switch is on, the DCCC based on traffic statistics is
supported over the DCH. 18.
DRA_VOICE_SAVE_CE_SWITCH: when the switch is
on, the TTI selection based on the voice service type
(including VoIP and CS over HSPA) is supported when
the service is initially established. 19.
DRA_VOICE_TTI_RECFG_SWITCH: when the switch
is on, the TTI adjustment based on the voice service
type (including VoIP and CS over HSPA) is supported.
20. DRA_CSPS_NO_PERIOD_RETRY_SWITCH:
Whether to prohibit channel retries for CS and PS
combined services. When this switch is turned on,
channel retries are prohibited for CS and PS combined
services. When this switch is turned off, channel
retries are allowed for CS and PS combined services.
21. DRA_SMART_FAST_STATE_TRANS_SWITCH:
Whether to activate the fast state transition algorithm.
When this switch is turned on, the RNC identifies UEs
supporting fast state transition and then quickly
transits the UEs from CELL_DCH to CELL_FACH. 22.
DRA_PCH_UE_SMART_P2D_SWITCH: Whether to
activate the algorithm for smart PCH-to-DCH state
transition specific to UEs in the CELL_PCH or
URA_PCH state. When this switch is turned on, the
RNC identifies UEs supporting smart PCH-to-DCH
state transition and then transits the UEs from
CELL_PCH or URA_PCH to CELL_DCH. 23.
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH:
Whether initial TTI selection is allowed for
differentiated BE services based on fairness 0: This
switch is turned off. The TTI is selected according to
the original algorithm. 1: This switch is turned on. In
the dynamic TTI adjustment algorithm for differentiated
BE services based on fairness, HSUPA UEs use 10ms TTI if the RTWP, occupied Iub bandwidth, or
consumed CE resources are congested. 24.
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITCH:
Whether to activate the coverage-based initial TTI
selection algorithm specific to BE services. When this
switch is turned on and conditions on 2 ms TTI specific
to BE services has been met, the RNC determines
uplink coverage wideness of specific cells based on
the Ec/N0 values reported by UEs during RRC
connection. If the uplink coverage of the cells is weak,
the RNC allocates a 10 ms TTI to BE services as their
initial TTI. 25. DRA_F2U_SWITCH: Whether to enable
state transition from CELL_FACH to URA_PCH.When
this switch is turned on, a UE can directly move from
the CELL_FACH to URA_PCH state. When this switch
is turned off, a UE must move from the CELL_FACH to
Page 54 of 69
CELL_PCH and then to URA_PCH state.

GUI Value Range:DRA_AQM_SWITCH,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH,
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_RES_BE_TTI_RECFG_SWITCH,
DRA_DCCC_SWITCH,
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH,
DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_DCCC_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH,
DRA_IP_SERVICE_QOS_SWITCH,
DRA_PS_BE_STATE_TRANS_SWITCH,
DRA_PS_NON_BE_STATE_TRANS_SWITCH,
DRA_R99_DL_FLOW_CONTROL_SWITCH,
DRA_THROUGHPUT_DCCC_SWITCH,
DRA_VOICE_SAVE_CE_SWITCH,
DRA_VOICE_TTI_RECFG_SWITCH,
DRA_CSPS_NO_PERIOD_RETRY_SWITCH,
DRA_SMART_FAST_STATE_TRANS_SWITCH,
DRA_PCH_UE_SMART_P2D_SWITCH,
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH,
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITCH,
DRA_F2U_SWITCH
Unit:None
Actual Value Range:DRA_AQM_SWITCH,
DRA_DCCC_SWITCH,
DRA_F2U_SWITCH
Default Value:DRA_AQM_SWITCH0&DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH0&DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH1&DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH0&DRA_BASE_COVER_BE_TTI_RECFG_SWITCH0&DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH0&DRA_BASE_RES_BE_TTI_RECFG_SWITCH1&DRA_DCCC_SWITCH1&DRA_HSDPA_DL_FLOW_CONTROL_SWITCH0&DRA_HSDPA_STATE_TRANS_SWITCH0&DRA_HSUPA_DCCC_SWITCH1&DRA_HSUPA_STATE_TRANS_SWITCH0&DRA_IP_SERVICE_QOS_SWITCH0&DRA_PS_BE_STATE_TRANS_SWITCH1&DRA_PS_NON_BE_STATE_TRANS_SWITCH0&DRA_R99_DL_FLOW_CONTROL_SWITCH0&DRA_THROUGHPUT_DCCC_SWITCH0&DRA_VOICE_SAVE_CE_SWITCH0&DRA_VOICE_TTI_RECFG_SWITCH0&DRA_CSPS_NO_PERIOD_RETRY_SWITCH0&DRA_SMART_FAST_STATE_TRANS_SWITCH0&DRA_PCH_UE_SMART_P2D_SWITCH0&DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH0&DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITCH0&DRA_F2U_SWITCH-0
DraSwitch
BSC6910
WRFDSET
UCORRMALGOSWITCH 01061111
WRFD01061208
WRFD01061404
WRFD-011502
WRFD-021101
WRFD-050405
WRFD-050408
WRFD-010690
WRFD01061403
WRFD-010202
WRFD-010507
WRFD-020106
WRFD-010653
WRFD-010654
WRFD-020131
WRFD-020128
WRFD-010301
WRFD-010302
WRFD-010801
HSDPA State
Transition
HSUPA DCCC
HSUPA 2ms/10ms
TTI Handover
Active Queue
Management (AQM)
Dynamic Channel
(DCCC)
Overbooking on ATM
Transmission
Overbooking on IP
Transmission
TTI Switch for BE
Services Based on
Coverage
HSUPA 2ms TTI
UE State in
Connected Mode
(CELL-DCH
CELL-PCH
URA-PCH
CELL-FACH)
Meaning:Dynamic resource allocation switch group. 1.

DRA_AQM_SWITCH: When the switch is on, the
active queue management algorithm is used for the
RNC. 2.
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH:
algorithm for admission CE-based BE services applies
to the UE with the UL enhanced L2 feature. This
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH:
algorithm is supported for admission CE-based BE
services. 4.
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH:
algorithm for coverage-based BE services applies to
the UE with the UL enhanced L2 feature. This
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH:
algorithm is supported for coverage-based BE
services. 6.
Page 55 of 69
WRFD-010802
WRFD-010901
WRFD-010902
Rate Negotiation at
Admission Control
Load Reshuffling
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
Optimization of R99
and HSUPA Users
Fairness
Quality Improvement
for Subscribed
Service
Paging UE in Idle
CELL_PCH
URA_PCH State
(Type 1)
Paging UE in
CELL_FACH
CELL_DCH State
(Type 2)
Intra RNC Cell
Update
Inter RNC Cell
Update
Intra RNC URA
Update
Inter RNC URA
Update
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH: When
for differentiation-based BE services applies to the UE
with the UL enhanced L2 feature. This parameter is
valid when
DRA_BASE_RES_BE_TTI_RECFG_SWITCH
DRA_BASE_RES_BE_TTI_RECFG_SWITCH: When
is supported for differentiation-based BE services. 8.
DRA_DCCC_SWITCH: When the switch is on, the
dynamic channel reconfiguration control algorithm is
used for the RNC. 9.
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH:
When the switch is on, flow control is enabled for
HSDPA services in AM mode. 10.
DRA_HSDPA_STATE_TRANS_SWITCH: When the
HSDPA services can be changed to CELL_FACH at
the RNC. If a PS BE service is carried over the HSDSCH, the switch PS_BE_STATE_TRANS_SWITCH
is carried over the HS-DSCH, the switch
simultaneously. 11. DRA_HSUPA_DCCC_SWITCH:
When the switch is on, the DCCC algorithm is used for
HSUPA. The DCCC switch must be also on before this
switch takes effect. 12.
DRA_HSUPA_STATE_TRANS_SWITCH: When the
HSUPA services can be changed to CELL_FACH at
the RNC. If a PS BE service is carried over the EDCH, the switch PS_BE_STATE_TRANS_SWITCH
is carried over the E-DCH, the switch
simultaneously. 13.
DRA_IP_SERVICE_QOS_SWITCH: Switch of the
algorithm for increasing the quality of subscribed
services. When this parameter is set to ON, the
service priority weight of the subscriber whose key
parameters (IP Address, IP Port, and IP Protocol
Type) match the specified ones can be adjusted. In
this way, the QoS is improved. 14.
DRA_PS_BE_STATE_TRANS_SWITCH: When this
switch is turned on, UEs can be transited among the
CELL_DCH, CELL_FACH, CELL_PCH, and
URA_PCH states when they are processing PS BE
services. 15.
DRA_PS_NON_BE_STATE_TRANS_SWITCH: When
this switch is turned on, UEs can be transited between
the CELL_DCH and CELL_FACH states when they
are processing real-time PS services. 16.
DRA_R99_DL_FLOW_CONTROL_SWITCH: Under a
poor radio environment, the QoS of high speed
services drops considerably and the TX power is
overly high. In this case, the RNC can set restrictions
on low data rate transmission formats based on the
transmission quality, thus lowering traffic speed and
TX power. When the switch is on, the R99 downlink
flow control function is enabled. 17.
DRA_THROUGHPUT_DCCC_SWITCH: When the
switch is on, the DCCC based on traffic statistics is
supported over the DCH. 18.
DRA_VOICE_SAVE_CE_SWITCH: when the switch is
on, the TTI selection based on the voice service type
(including VoIP and CS over HSPA) is supported when
the service is initially established. 19.
DRA_VOICE_TTI_RECFG_SWITCH: when the switch
is on, the TTI adjustment based on the voice service
type (including VoIP and CS over HSPA) is supported.
20. DRA_CSPS_NO_PERIOD_RETRY_SWITCH:
Whether to prohibit channel retries for CS and PS
combined services. When this switch is turned on,
channel retries are prohibited for CS and PS combined
services. When this switch is turned off, channel
retries are allowed for CS and PS combined services.
21. DRA_SMART_FAST_STATE_TRANS_SWITCH:
Whether to activate the fast state transition algorithm.
When this switch is turned on, the RNC identifies UEs
supporting fast state transition and then quickly
transits the UEs from CELL_DCH to CELL_FACH. 22.
DRA_PCH_UE_SMART_P2D_SWITCH: Whether to
activate the algorithm for smart PCH-to-DCH state
transition specific to UEs in the CELL_PCH or
URA_PCH state. When this switch is turned on, the
RNC identifies UEs supporting smart PCH-to-DCH
state transition and then transits the UEs from
CELL_PCH or URA_PCH to CELL_DCH. 23.
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH:
Whether initial TTI selection is allowed for
differentiated BE services based on fairness 0: This
switch is turned off. The TTI is selected according to
the original algorithm. 1: This switch is turned on. In
the dynamic TTI adjustment algorithm for differentiated
BE services based on fairness, HSUPA UEs use 10ms TTI if the RTWP, occupied Iub bandwidth, or
consumed CE resources are congested. 24.
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITCH:
Whether to activate the coverage-based initial TTI
selection algorithm specific to BE services. When this
switch is turned on and conditions on 2 ms TTI specific
to BE services has been met, the RNC determines
uplink coverage wideness of specific cells based on
the Ec/N0 values reported by UEs during RRC
Page 56 of 69
connection. If the uplink coverage of the cells is weak,

the RNC allocates a 10 ms TTI to BE services as their
initial TTI. 25. DRA_F2U_SWITCH: Whether to enable
state transition from CELL_FACH to URA_PCH.When
this switch is turned on, a UE can directly move from
the CELL_FACH to URA_PCH state. When this switch
is turned off, a UE must move from the CELL_FACH to
CELL_PCH and then to URA_PCH state.
GUI Value Range:DRA_AQM_SWITCH,
DRA_DCCC_SWITCH,
DRA_F2U_SWITCH
Unit:None
Actual Value Range:DRA_AQM_SWITCH,
DRA_DCCC_SWITCH,
DRA_F2U_SWITCH
Default Value:DRA_AQM_SWITCH0&DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITCH0&DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH1&DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH0&DRA_BASE_COVER_BE_TTI_RECFG_SWITCH0&DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH0&DRA_BASE_RES_BE_TTI_RECFG_SWITCH1&DRA_DCCC_SWITCH1&DRA_HSDPA_DL_FLOW_CONTROL_SWITCH0&DRA_HSDPA_STATE_TRANS_SWITCH0&DRA_HSUPA_DCCC_SWITCH1&DRA_HSUPA_STATE_TRANS_SWITCH0&DRA_IP_SERVICE_QOS_SWITCH0&DRA_PS_BE_STATE_TRANS_SWITCH1&DRA_PS_NON_BE_STATE_TRANS_SWITCH0&DRA_R99_DL_FLOW_CONTROL_SWITCH0&DRA_THROUGHPUT_DCCC_SWITCH0&DRA_VOICE_SAVE_CE_SWITCH0&DRA_VOICE_TTI_RECFG_SWITCH0&DRA_CSPS_NO_PERIOD_RETRY_SWITCH0&DRA_SMART_FAST_STATE_TRANS_SWITCH0&DRA_PCH_UE_SMART_P2D_SWITCH0&DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH0&DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITCH0&DRA_F2U_SWITCH-0
SrbChlType
BSC6900
SET
UFRCCHLTYPEPARA
WRFD-010510
WRFD-010636
WRFD-010686
WRFD-010653
WRFD-010654
3.4/6.8/13.6/27.2Kbps
RRC Connection and
Radio Access Bearer
Establishment and
Release
SRB over HSUPA
CPC - DTX / DRX
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
SrbChlType
BSC6910
SET
UFRCCHLTYPEPARA
WRFD-010510
WRFD-010636
3.4/6.8/13.6/27.2Kbps Meaning:Type of channel that preferably carries the

RRC Connection and signaling RB. - DCH: Both uplink and downlink are
Radio Access Bearer preferably carried on DCH. - HSDPA: Uplink is
Meaning:Type of channel that preferably carries the

signaling RB. - DCH: Both uplink and downlink are
preferably carried on DCH. - HSDPA: Uplink is
preferably carried on DCH, and downlink is preferably
carried on HS-DSCH. - HSUPA: Uplink is preferably
carried on E-DCH, and downlink is preferably carried
on DCH. - HSPA: Uplink is preferably carried on EDCH, and downlink is preferably carried on HS-DSCH.
GUI Value Range:DCH(UL_DCH,DL_DCH), HSDPA
(UL_DCH,DL_HSDSCH), HSUPA
(UL_EDCH,DL_DCH), HSPA
(UL_EDCH,DL_HSDSCH)
Unit:None
Actual Value Range:DCH, HSDPA, HSUPA, HSPA
Default Value:DCH(UL_DCH,DL_DCH)
Page 57 of 69
WRFD-010686
WRFD-010653
WRFD-010654
Establishment and
Release
SRB over HSUPA
CPC - DTX / DRX
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
preferably carried on DCH, and downlink is preferably

carried on HS-DSCH. - HSUPA: Uplink is preferably
carried on E-DCH, and downlink is preferably carried
on DCH. - HSPA: Uplink is preferably carried on EDCH, and downlink is preferably carried on HS-DSCH.
GUI Value Range:DCH(UL_DCH,DL_DCH), HSDPA
(UL_DCH,DL_HSDSCH), HSUPA
(UL_EDCH,DL_DCH), HSPA
(UL_EDCH,DL_HSDSCH)
Unit:None
Actual Value Range:DCH, HSDPA, HSUPA, HSPA
Default Value:DCH(UL_DCH,DL_DCH)
EagchCodeNum
BSC6900
ADD UCELLHSUPA
MOD UCELLHSUPA
WRFD-010612
WRFD-010634
WRFD-010639
WRFD-010670
WRFD-010653
WRFD-010654
HSUPA Introduction
Package
60 HSUPA Users per
Cell
96 HSUPA Users per
Cell
128 HSUPA Users
per Cell
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
Meaning:The parameter specifies the number of codes

used by the E-DCH Absolute Grant Channel (EAGCH). For details, see 3GPP TS 25.433.
GUI Value Range:1~8
Unit:None
Default Value:1
EagchCodeNum
BSC6910
ADD UCELLHSUPA
MOD UCELLHSUPA
WRFD-010612
WRFD-010634
WRFD-010639
WRFD-010670
WRFD-010653
WRFD-010654
HSUPA Introduction
Package
60 HSUPA Users per
Cell
96 HSUPA Users per
Cell
128 HSUPA Users
per Cell
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell

used by the E-DCH Absolute Grant Channel (EAGCH). For details, see 3GPP TS 25.433.
GUI Value Range:1~8
Unit:None
Default Value:1
ErgchEhichCodeNum
BSC6900
ADD UCELLHSUPA
MOD UCELLHSUPA
WRFD-010612
WRFD-010653
WRFD-010654
WRFD-010639
WRFD-010670
WRFD-010701
HSUPA Introduction
Package
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
96 HSUPA Users per
Cell
128 HSUPA Users
per Cell
Uplink Enhanced
CELL_FACH

used by the E-DCH Relative Grant Channel (ERGCH)/E-DCH Hybrid ARQ Indicator Channel (EHICH). For details, see 3GPP TS 25.433.
GUI Value Range:1~8
Unit:None
Default Value:1
ErgchEhichCodeNum
BSC6910
ADD UCELLHSUPA
MOD UCELLHSUPA
WRFD-010612
WRFD-010653
WRFD-010654
WRFD-010639
WRFD-010670
WRFD-010701
HSUPA Introduction
Package
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
96 HSUPA Users per
Cell
128 HSUPA Users
per Cell
Uplink Enhanced
CELL_FACH

used by the E-DCH Relative Grant Channel (ERGCH)/E-DCH Hybrid ARQ Indicator Channel (EHICH). For details, see 3GPP TS 25.433.
GUI Value Range:1~8
Unit:None
Default Value:1
UlHoCeResvSf
BSC6900
ADD UCELLCAC
MOD UCELLCAC
WRFD-020101
WRFD-010653
WRFD-010654
Admission Control
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
Meaning:Uplink credit resources (measured by the

spreading factor) reserved for handovers. When this
parameter is set to SFOFF, no credit resources are
reserved for handovers. After receiving a service
access request, the RNC evaluates the remaining
uplink credit resources after admitting the service. If
the remaining uplink credit resources are greater than
or equal to reserved resources specified by this
parameter, the RNC admits the service. Otherwise, the
RNC rejects the service. The larger the digit following
SF, the less the corresponding resources. For
example, the credit resources corresponding to SF32
are less than those corresponding to SF8.
GUI Value Range:SF4(SF4), SF8(SF8), SF16(SF16),
SF32(SF32), SF64(SF64), SF128(SF128), SF256
(SF256), SFOFF(SFOFF)
Unit:None
Actual Value Range:SF4, SF8, SF16, SF32, SF64,
SF128, SF256, SFOFF
Default Value:SF16(SF16)
UlHoCeResvSf
BSC6910
ADD UCELLCAC
MOD UCELLCAC
WRFD-020101
WRFD-010653
WRFD-010654
Admission Control
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
Meaning:Uplink credit resources (measured by the

spreading factor) reserved for handovers. When this
parameter is set to SFOFF, no credit resources are
reserved for handovers. After receiving a service
access request, the RNC evaluates the remaining
uplink credit resources after admitting the service. If
the remaining uplink credit resources are greater than
or equal to reserved resources specified by this
parameter, the RNC admits the service. Otherwise, the
RNC rejects the service. The larger the digit following
SF, the less the corresponding resources. For
example, the credit resources corresponding to SF32
are less than those corresponding to SF8.
SF32(SF32), SF64(SF64), SF128(SF128), SF256
Page 58 of 69
Unit:None
SF128, SF256, SFOFF
DlHoCeCodeResvSf
BSC6900
ADD UCELLCAC
MOD UCELLCAC
WRFD-020101
WRFD-010653
WRFD-010654
Admission Control
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
Meaning:Downlink credit and code resources

(measured by the spreading factor) reserved for
handovers. When this parameter is set to SFOFF, no
credit or code resources are reserved for handovers.
After receiving a service access request, the RNC
evaluates the remaining downlink credit and code
resources after admitting the service. If the remaining
downlink credit resources are greater than or equal to
reserved resources specified by this parameter, the
RNC admits the service. Otherwise, the RNC rejects
the service.
SF32(SF32), SF64(SF64), SF128(SF128), SF256
Unit:None
SF128, SF256, SFOFF
DlHoCeCodeResvSf
BSC6910
ADD UCELLCAC
MOD UCELLCAC
WRFD-020101
WRFD-010653
WRFD-010654
Admission Control
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
Meaning:Downlink credit and code resources

(measured by the spreading factor) reserved for
handovers. When this parameter is set to SFOFF, no
credit or code resources are reserved for handovers.
After receiving a service access request, the RNC
evaluates the remaining downlink credit and code
resources after admitting the service. If the remaining
downlink credit resources are greater than or equal to
reserved resources specified by this parameter, the
RNC admits the service. Otherwise, the RNC rejects
the service.
SF32(SF32), SF64(SF64), SF128(SF128), SF256
Unit:None
SF128, SF256, SFOFF
MaxHsdpaUserNum
BSC6900
ADD UCELLCAC
MOD UCELLCAC
WRFD-020101
WRFD01061003
WRFD-010653
WRFD-010654
WRFD01061112
Admission Control
HSDPA Admission
Control
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
HSDPA DRD
Meaning:Maximum number of users supported by the

HSDPA channel. The user in this parameter refers to
the user with services on the HSDPA channel,
regardless of the number of RABs carried on the
HSDPA channel. Maximum HSDPA user number
cannot exceed the HSDPA capability of the NodeB
product, In practice, the value can be set based on the
cell type and the richness of the available HSDPA
power and code resources.
Unit:None
Default Value:64
MaxHsdpaUserNum
BSC6910
ADD UCELLCAC
MOD UCELLCAC
WRFD-020101
WRFD01061003
WRFD-010653
WRFD-010654
WRFD01061112
Admission Control
HSDPA Admission
Control
96 HSDPA Users per
Cell
128 HSDPA Users
per Cell
HSDPA DRD
Meaning:Maximum number of users supported by the

HSDPA channel. The user in this parameter refers to
the user with services on the HSDPA channel,
regardless of the number of RABs carried on the
HSDPA channel. Maximum HSDPA user number
cannot exceed the HSDPA capability of the NodeB
product, In practice, the value can be set based on the
cell type and the richness of the available HSDPA
power and code resources.
Unit:None
Default Value:64
10 Counters
Table 10-1 Counter description
Counter ID
Counter Name
Counter Description
NE
Feature ID
Feature Name
50331654
VS.AckTotal
Total number of ACKs received
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331655
VS.NackTotal
Total number of NACKs received
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331656
VS.DtxTotal
Total number of TTIs when the NodeB can NodeB

not translate the acknowledgement
information from the UE
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331657
VS.AckFirst
Number of ACKs received after 1st

transmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331658
VS.AckRetrans.1
Number of ACKs received after 1st

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331659
VS.AckRetrans.2
Number of ACKs received after 2nd

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
Page 59 of 69
RR and PF)
50331660
VS.AckRetrans.3
Number of ACKs received after 3rd

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331661
VS.AckRetrans.4
Number of ACKs received after 4th

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331662
VS.AckRetrans.5

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331663
VS.AckRetrans.6

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331664
VS.AckRetrans.7

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331665
VS.AckRetrans.8

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331666
VS.AckRetrans.9

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331667
VS.AckRetrans.10

retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331668
VS.AckRemain
Number of times the NodeB does not

receive the ACK from the UE after the last
retransmission
NodeB
WRFD-01061009
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
50331717
VS.HSDPA.MIMO64QAMCfg.ActedNum
Number of times that all the users

configured in 64QAM+MIMO mode in a
cell employ 64QAM during the
measurement period
NodeB
WRFD-010693
WRFD-010689
WRFD-010610
DL 64QAM+MIMO
HSPA+ Downlink 42
Mbit/s per User
HSDPA Introduction
Package
50331718
VS.HSDPA.MIMO64QAMCfg.ScheduledNum Number of times that all the users

configured in 64QAM+MIMO mode in a
cell are scheduled during the
measurement period
NodeB
WRFD-010610
WRFD-010689
WRFD-010693
HSDPA Introduction
Package
HSPA+ Downlink 42
Mbit/s per User
DL 64QAM+MIMO
50331719
VS.HSDPA.DCCfg.AnchorCarrierActedNum
Number of times that all the users

configured in DC mode in a cell are
scheduled by AnchorCarrier during the
measurement period
NodeB
WRFD-010610
WRFD-010689
WRFD-010696
HSDPA Introduction
Package
HSPA+ Downlink 42
Mbit/s per User
DC-HSDPA
50331720
VS.HSDPA.DCCfg.SupCarrierActedNum
Total number of times DC-HSDPAenabled users are scheduled by the

supplementary carrier
NodeB
WRFD-010610
WRFD-010689
WRFD-010696
HSDPA Introduction
Package
HSPA+ Downlink 42
Mbit/s per User
DC-HSDPA
50331721
VS.HSDPA.DCCfg.DualCarrierActedNum
Total number of times DC-HSDPAenabled users are scheduled by the

anchor and supplementary carriers at the
same time
NodeB
WRFD-010610
WRFD-010689
WRFD-010696
HSDPA Introduction
Package
HSPA+ Downlink 42
Mbit/s per User
DC-HSDPA
50331722
VS.HSDPA.16QAMCfg.ActedNum
Total number of times all the users in a

cell use 16QAM mode
NodeB
WRFD-010610
WRFD-010629
HSDPA Introduction
Package
DL 16QAM
Modulation
50331723
VS.HSDPA.QPSKCfg.ActedNum
Total number of times users use the

QPSK mode
NodeB
WRFD-010610
WRFD-01061017
HSDPA Introduction
Package
QPSK Modulation
50331724
VS.HSDPA.All.ScheduledNum
Total number of times all the users are

scheduled in a cell
NodeB
WRFD-01061009
WRFD-010610
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
HSDPA Introduction
Package
50331745
VS.HSDPA.DataTtiNum.User
Total number of user-level TTIs within

which there is data to transmit in HSDPA
user queue buffers
NodeB
WRFD-010610
HSDPA Introduction
Package
50331746
VS.HSDPA.DataOutput.Traffic
Traffic volume of the MAC-hs/MAC-ehs

PDUs successfully received in a cell
NodeB
WRFD-010611
HSDPA Enhanced
Package
50331754
VS.UsedCQI0
Number of times the NodeB transmits data NodeB

with CQI=0
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Time and HSPDSCH Codes
Multiplex
HSDPA Dynamic
Power Allocation
50331755
VS.UsedCQI1

with CQI=1
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
Page 60 of 69
HSDPA Dynamic
Power Allocation
50331756
VS.UsedCQI2

with CQI=2
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331757
VS.UsedCQI3

with CQI=3
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331758
VS.UsedCQI4

with CQI=4
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331759
VS.UsedCQI5

with CQI=5
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331760
VS.UsedCQI6

with CQI=6
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331761
VS.UsedCQI7

with CQI=7
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331762
VS.UsedCQI8

with CQI=8
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331763
VS.UsedCQI9

with CQI=9
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331764
VS.UsedCQI10

with CQI=10
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331765
VS.UsedCQI11

with CQI=11
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331766
VS.UsedCQI12

with CQI=12
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331767
VS.UsedCQI13

with CQI=13
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331768
VS.UsedCQI14

with CQI=14
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Time and HS-
Page 61 of 69
PDSCH Codes
Multiplex
HSDPA Dynamic
Power Allocation
50331769
VS.UsedCQI15

with CQI=15
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331770
VS.UsedCQI16

with CQI=16
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331771
VS.UsedCQI17

with CQI=17
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331772
VS.UsedCQI18

with CQI=18
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331773
VS.UsedCQI19

with CQI=19
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331774
VS.UsedCQI20

with CQI=20
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331775
VS.UsedCQI21

with CQI=21
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331776
VS.UsedCQI22

with CQI=22
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331777
VS.UsedCQI23

with CQI=23
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331778
VS.UsedCQI24

with CQI=24
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331779
VS.UsedCQI25

with CQI=25
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331780
VS.UsedCQI26

with CQI=26
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331781
VS.UsedCQI27
WRFD-010610
HSDPA Introduction
Page 62 of 69
with CQI=27
WRFD-01061018
WRFD-01061019
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331782
VS.UsedCQI28

with CQI=28
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331783
VS.UsedCQI29

with CQI=29
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331784
VS.UsedCQI30

with CQI=30
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331785
VS.UsedCQI31to39

with CQI=[31
39]
WRFD-010610
WRFD-01061018
WRFD-01061019
HSDPA Introduction
Package
Multiplex
HSDPA Dynamic
Power Allocation
50331838
VS.HSDPA.DataOutput.TRB
HSDSCH TRB traffic volume in a cell
NodeB
WRFD-010611
HSDPA Enhanced
Package
50331839
VS.HSDPA.DataTtiNum.TRB
Number of TTIs in which TRB data is to be NodeB

transmitted in the HSDPA user queue in a
cell
WRFD-010611
HSDPA Enhanced
Package
50331840
VS.HSDPA.InactiveDataTtiNum.TRB
Number of TTIs in which at least one

HSDPA user in a cell has TRB data to
transmit in the queue buffer but no
HSDPA user transmits TRB data at the
physical layer
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341648
VS.ScchCodeUtil.Mean
Average usage of HS-SCCH code

resources in a cell
NodeB
WRFD-01061001
WRFD-01061018
WRFD-01061005
WRFD-010631
15 Codes per Cell

Multiplex
HSDPA Static Code
Code Allocation
Dynamic Code
Allocation Based on
Node B
50341649
VS.ScchCodeUtil.Max
Maximum usage of HS-SCCH code

resources in a cell
NodeB
WRFD-01061001
WRFD-01061018
WRFD-01061005
WRFD-010631
15 Codes per Cell

Multiplex
HSDPA Static Code
Code Allocation
Dynamic Code
Allocation Based on
Node B
50341650
VS.ScchCodeUtil.Min
Minimum usage of HS-SCCH code

resources in a cell
NodeB
WRFD-01061001
WRFD-01061018
WRFD-01061005
WRFD-010631
15 Codes per Cell

Multiplex
HSDPA Static Code
Code Allocation
Dynamic Code
Allocation Based on
Node B
50341651
VS.PdschCodeUtil.Mean
Average usage of HS-PDSCH code

resources in a cell
NodeB
WRFD-01061005
WRFD-010631
WRFD-01061001
WRFD-01061018
HSDPA Static Code

Code Allocation
Dynamic Code
Allocation Based on
Node B
15 Codes per Cell
Multiplex
50341652
VS.PdschCodeUtil.Max
Maximum usage of HS-PDSCH code

resources in a cell
NodeB
WRFD-01061005
WRFD-010631
HSDPA Static Code

Page 63 of 69
WRFD-01061001
WRFD-01061018
Code Allocation
Dynamic Code
Allocation Based on
Node B
15 Codes per Cell
Multiplex
50341653
VS.PdschCodeUtil.Min
Minimum usage of HS-PDSCH code

resources in a cell
NodeB
WRFD-01061005
WRFD-010631
WRFD-01061001
WRFD-01061018
HSDPA Static Code

Code Allocation
Dynamic Code
Allocation Based on
Node B
15 Codes per Cell
Multiplex
50341654
VS.ScchCodeUtil.Mean.User

resources when HSDPA users camp on
the cell
NodeB
WRFD-01061005
WRFD-010631
WRFD-01061001
WRFD-01061018
HSDPA Static Code

Code Allocation
Dynamic Code
Allocation Based on
Node B
15 Codes per Cell
Multiplex
50341655
VS.ScchCodeUtil.Mean.Data

resources when at least one HSDPA user
has data to transmit in the queue buffer
NodeB
WRFD-01061005
WRFD-010631
WRFD-01061001
WRFD-01061018
HSDPA Static Code

Code Allocation
Dynamic Code
Allocation Based on
Node B
15 Codes per Cell
Multiplex
50341656
VS.PdschCodeUtil.Mean.User

resources when HSDPA users camp on
the cell
NodeB
WRFD-01061001
WRFD-01061018
WRFD-01061005
WRFD-010631
15 Codes per Cell

Multiplex
HSDPA Static Code
Code Allocation
Dynamic Code
Allocation Based on
Node B
50341657
VS.PdschCodeUtil.Mean.Data

resources when at least one HSDPA user
NodeB
WRFD-01061005
WRFD-010631
WRFD-01061001
WRFD-01061018
HSDPA Static Code

Code Allocation
Dynamic Code
Allocation Based on
Node B
15 Codes per Cell
Multiplex
50341658
VS.UserTtiRatio.Mean
Ratio of the time when at least one

HSDPA UE camps on the cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341659
Ratio of the time when at least one

HSDPA user has data to transmit in the
queue buffer
NodeB
WRFD-010610
HSDPA Introduction
Package
50341660
VS.RabNum.Mean
Average number of HSDPA RABs in a cell NodeB
WRFD-010610
HSDPA Introduction
Package
50341661
VS.RabNum.Max
Maximum number of HSDPA RABs in a

cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341662
VS.RabNum.Min
Minimum number of HSDPA RABs in a

cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341663
VS.DataRabNum.Mean
Average number of HSDPA RABs have

data to transmit in the queue buffer in a
cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341664
VS.DataRabNum.Max
Maximum number of HSDPA RABs have

cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341665
VS.DataRabNum.Min
Minimum number of HSDPA RABs have

cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341666
VS.RabNumAve.User
Average number of HSDPA RABs when

HSDPA users camp on the cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341667
VS.RabNumAve.UserData
Average number of HSDPA RABs have

data to transmit in the queue buffer when
at least one HSDPA user has data to
transmit in the queue buffer in a cell
NodeB
WRFD-010610
HSDPA Introduction
Package
Page 64 of 69
50341668
VS.DataOutput.Mean
Average cell throughput at the MAChs/MAC-ehs layer
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341669
VS.DataOutput.Max
Maximum cell throughput at the MAChs/MAC-ehs layer
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341670
VS.DataOutput.Min
Minimum cell throughput at the MAChs/MAC-ehs layer
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341671
VS.DataOutput.User
Average cell throughput when HSDPA

users camp on the cell
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341672
VS.DataOutput.UserData
Average cell throughput when at least one NodeB

HSDPA user has data to transmit in the
queue buffer
WRFD-010611
HSDPA Enhanced
Package
50341673
VS.DataOutput.Rab
Average throughput of each RAB when

HSDPA users camp on the cell
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341674
VS.DataOutput.RabData
Average throughput of each RAB when at

least one HSDPA user has data to
transmit in the queue buffer
NodeB
WRFD-010611
HSDPA Enhanced
Package
50341675
VS.ScchPwrRatio.Mean
Average transmit power over the HSSCCH in a cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341676
VS.ScchPwrRatio.Max
Maximum transmit power over the HSSCCH in a cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341677
VS.ScchPwrRatio.Min
Minimum transmit power over the HSSCCH in a cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341678
VS.PdschPwrRatio.Mean
Average transmit power over the HSPDSCH in a cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341679
VS.PdschPwrRatio.Max
Maximum transmit power over the HSPDSCH in a cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341680
VS.PdschPwrRatio.Min
Minimum transmit power over the HSPDSCH in a cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341681
VS.ScchPwrRatio.User
Average transmit power over the HSSCCH when HSDPA users camp on the
cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341682
VS.PdschPwrRatio.User
Average transmit power over the HSPDSCH when HSDPA users camp on the
cell
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341683
VS.ScchPwrRatio.UserData
Average transmit power over the HSNodeB

SCCH when at least one HSDPA user has
data to transmit in the queue buffer
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341684
VS.PdschPwrRatio.Data
Average transmit power over the HSPDSCH when at least one HSDPA user
NodeB
WRFD-01061004
WRFD-01061019
HSDPA Power
Control
HSDPA Dynamic
Power Allocation
50341685
VS.DataDiscardRatio.Mean
Average ratio of discarded HSDPA data

due to timer expiry
NodeB
WRFD-01061009
WRFD-010610
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
HSDPA Introduction
Package
50341686
VS.DataDiscardRatio.Max
Maximum ratio of discarded HSDPA data

due to timer expiry
NodeB
WRFD-01061009
WRFD-010610
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
HSDPA Introduction
Package
50341687
VS.DataDiscardRatio.Min
Minimum ratio of discarded HSDPA data

due to timer expiry
NodeB
WRFD-01061009
WRFD-010610
HSDPA H-ARQ &

Scheduling (MAX C/I
RR and PF)
HSDPA Introduction
Package
50341688
VS.PdschCodeUsed.Mean
Average number of used HS-PDSCH

codes in a cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341689
VS.PdschCodeUsed.Max
Maximum number of used HS-PDSCH

codes in a cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341690
VS.PdschCodeAvail.Mean
Average number of available HS-PDSCH

codes in a cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341691
VS.PdschCodeAvail.Max
Maximum number of available HS-PDSCH NodeB

codes in a cell
WRFD-010610
HSDPA Introduction
Package
50341692
VS.PdschCodeUsed.Min
Minimum number of used HS-PDSCH

codes in a cell
WRFD-010610
HSDPA Introduction
Package
NodeB
Page 65 of 69
50341693
VS.HSDPA.InactiveDataTtiRatio.Mean
Average ratio of the time when at least

one HSDPA user has data to transmit in
the buffer but no HSDPA user transmits
data at the physical layer
NodeB
WRFD-010610
HSDPA Introduction
Package
50341694
VS.HSDPA.2ScchCodeRatio
The time ratio of only using two HS-SCCH NodeB

codes for cell
WRFD-010610
HSDPA Introduction
Package
50341695
The time ratio of only using three HSSCCH codes for cell
NodeB
WRFD-010610
HSDPA Introduction
Package
50341696
The time ratio of only using four HS-SCCH NodeB

codes for cell
WRFD-010610
HSDPA Introduction
Package
50341697
VS.HSDPAPwrRatio.Mean.FreeUser
Average usage of free users Hsdpa Power NodeB
WRFD-010610
HSDPA Introduction
Package
50341698
VS.HSDPAPwrRatio.Max.FreeUser
Maximum usage of free users Hsdpa

Power
NodeB
WRFD-010610
HSDPA Introduction
Package
50341699
VS.DataOutput.Mean.FreeUser
Average throughput of free users at the

MAC-hs/MAC-ehs layer
NodeB
WRFD-010610
HSDPA Introduction
Package
50341700
VS.DataOutput.Max.FreeUser
Maximum throughput of free users at the

NodeB
WRFD-010610
HSDPA Introduction
Package
50341701
VS.DataOutput.Min.FreeUser
Minimum throughput of free users at the

NodeB
WRFD-010610
HSDPA Introduction
Package
50341703
VS.AvaiHSDPAPwrRatio.Mean
Mean ratio of availble HSDPA Power

Ratio
NodeB
WRFD-010610
HSDPA Introduction
Package
50341704
VS.AvaiHSDPAPwrRatio.Max
Maximum ratio of availble HSDPA Power

Ratio
NodeB
WRFD-010610
HSDPA Introduction
Package
50341705
VS.AvaiHSDPAPwrRatio.Min
Minimum ratio of availble HSDPA Power

Ratio
NodeB
WRFD-010610
HSDPA Introduction
Package
50341706
VS.HSDPAPwrRatio.PLMN0
Mean Ratio of PLMN0 used HSDPA

Power
NodeB
WRFD-010610
HSDPA Introduction
Package
50341707

Power
NodeB
WRFD-010610
HSDPA Introduction
Package
50341708

Power
NodeB
WRFD-010610
HSDPA Introduction
Package
50341709

Power
NodeB
WRFD-010610
HSDPA Introduction
Package
50341739
VS.HSDPA.ScheInactiveDataTtiRatio.Mean
Average ratio of the time when some

HSDPA users are queued in the
scheduling candidate set but do not
transmit data
NodeB
WRFD-010610
HSDPA Introduction
Package
67189834
VS.HSDPA.MACD.SuccSetup
Number of Successful HSDPA MAC-d

Flow Establishments for Cell
BSC6900
WRFD-010610
HSDPA Introduction
Package
67189840
VS.HSDPA.MeanChThroughput.TotalBytes
Number of Total Bytes Sent in Downlink of BSC6900

HSDPA MAC-d Flow for Cell
WRFD-010610
HSDPA Introduction
Package
67190698
VS.HSDPA.SHO.ServCellChg.AttOut
Number of Intra-RNC HSDPA Serving Cell BSC6900

Change Attempts for Cell
WRFD-01061006
HSDPA Mobility
Management
67190699
VS.HSDPA.SHO.ServCellChg.SuccOut

Change Success in RNC for Cell
WRFD-01061006
HSDPA Mobility
Management
67190700
VS.HSDPA.HHO.H2H.AttOutIntraFreq
Number of Intra-Frequency HSDPA Hard

Handover Attempts Without Channel
Change for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67190701
VS.HSDPA.HHO.H2H.SuccOutIntraFreq
Number of Successful Intra-Frequency

BSC6900
HSDPA Hard Handovers Without Channel
Change for Cell
WRFD-01061006
HSDPA Mobility
Management
67190702
VS.HSDPA.HHO.H2H.AttOutInterFreq
Number of Inter-Frequency HSDPA Hard

Change for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67190703
VS.HSDPA.HHO.H2H.SuccOutInterFreq
Number of Successful Inter-Frequency

BSC6900
Change for Cell
WRFD-01061006
HSDPA Mobility
Management
67190708
VS.HSDPA.HHO.NoChR.Att.NCell
Number of HSDSCH-to-HSDSCH hard

Handover Requests Without Channel
Change Between Neighboring Cells
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67190709
VS.HSDPA.HHO.NoChR.Succ.NCell
Number of Successful HSDSCH-toHSDSCH hard Handovers Without

Channel Change Between Neighboring
Cells
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67190710
VS.HSDPA.ServCellChg.Att.NCell
Number of HSDPA Serving Cell Change

Attempts Between Neighboring Cells
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67190711
VS.HSDPA.ServCellChg.Succ.NCell
Number of Successful HSDPA Serving

Cell Changes Between Neighboring Cells
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67191155
VS.IRATHO.HSDPA.AttOutPSUTRAN
Number of PS Inter-RAT Outgoing

Handover Attempts for HSDPA Services
for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67191156
VS.IRATHO.HSDPA.SuccOutPSUTRAN
Number of Successful PS Outgoing InterRAT Handovers for HSDPA Services for

Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67191157
VS.HSDPA.HHO.H2D.AttOutIntraFreq
Number of Intra-Frequency H2D Hard

Handover Attempts for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
Page 66 of 69
67191158
VS.HSDPA.HHO.H2D.SuccOutIntraFreq

H2D Hard Handovers for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67191159
VS.HSDPA.HHO.H2D.AttOutInterFreq
Number of Inter-Frequency H2D Hard

BSC6900
WRFD-01061006
HSDPA Mobility
Management
67191160
VS.HSDPA.HHO.H2D.SuccOutInterFreq

BSC6900
WRFD-01061006
HSDPA Mobility
Management
67192975
VS.RAB.RelReqPS.BE.HSDPA.Cong.Golden Number of HSDPA RABs Carrying Golden BSC6900

Users BE Traffic Released Due to
Congestion for Cell
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
67192976
VS.RAB.RelReqPS.BE.HSDPA.Cong.Silver
BSC6900
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
67192977
VS.RAB.RelReqPS.BE.HSDPA.Cong.Copper Number of HSDPA RABs Carrying Copper BSC6900

Congestion for Cell
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
67192991
VS.HSDPAPSLoad.MaxDLThruput.RNC
Maximum Throughput of PS HSDPA

Traffic for RNC
BSC6900
WRFD-010610
HSDPA Introduction
Package
67193578
VS.HSDPA.UE.Max.CAT1.6
Maximum Number of HSDPA UEs with

Category 1-6 in a Cell
BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67193581

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67193584

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67193587

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67193590

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67193593

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67193596

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67195481
VS.HSDPA.SHO.ServCellChg.AttOutIur
Number of Inter-RNC HSDPA Serving Cell BSC6900

WRFD-01061006
HSDPA Mobility
Management
67195482
VS.HSDPA.SHO.ServCellChg.SuccOutIur

Change Success for Cell
WRFD-01061006
HSDPA Mobility
Management
67195483
VS.HSDPA.HHO.H2H.AttOutIur
Number of Inter-RNC HSDPA Hard

Change for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
67195484
VS.HSDPA.HHO.H2H.SuccOutIur
Number of Successful Inter-RNC HSDPA BSC6900

Hard Handovers Without Channel Change
for Cell
WRFD-01061006
HSDPA Mobility
Management
67202894
VS.HSDPA.MeanChThroughput
Mean Downlink Throughput of single

HSDPA MAC-d Flows for Cell
BSC6900
WRFD-010610
HSDPA Introduction
Package
67204137
VS.HSDPAPSLoad.DLThruput.RNC
Throughput of PS HSDPA Traffic for RNC
BSC6900
WRFD-010610
HSDPA Introduction
Package
67204259
VS.HSDPA.UE.Mean.CAT1.6
Average Number of HSDPA UEs with

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67204260

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67204261

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67204262

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67204263

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67204264

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
67204265

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
73393828
VS.HSDPA.MACD.AttSetup
Number of HSDPA MAC-d Flow

Establishment Requests for Cell
BSC6900
WRFD-010610
HSDPA Introduction
Package
73403764
VS.HSDPA.HHO.H2D.AttOutIur
number of Inter-RNC H2D Hard Handover

Attempts for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
73403765
VS.HSDPA.HHO.H2D.SuccOutIur
Number of Successful Inter-RNC H2D

Hard Handovers for Cell
BSC6900
WRFD-01061006
HSDPA Mobility
Management
73410499
VS.SRNCIubBytesHSDPA.Tx
Number of DL Bytes over Iub HSDSCH for BSC6900

Cell
WRFD-010610
HSDPA Introduction
Package
73422167
VS.HSDPA.RAB.AbnormRel.H2P
Number of RABs Abnormally Released for BSC6900

PS HSDPA Services during the State
Transition from CELL_DCH to CELL_PCH
or URA_PCH for Cell
WRFD-010202
WRFD-010610
UE State in
Connected Mode
(CELL-DCH
CELL-PCH
URA-PCH
CELL-FACH)
HSDPA Introduction
Package
73423462
VS.HSDPA.Traffic.HighLoad
Number of Bytes Sent on HSDPA MAC-d
WRFD-010610
HSDPA Introduction
Number of HSDPA RABs Carrying Silver

Congestion for Cell
BSC6900
Page 67 of 69
Flow for Cell (Excluding the Bytes of LowTraffic Users)
WRFD-01061008
Package
Interactive and
Background Traffic
Class on HSDPA
73425958
RRC.SuccConnEstab.HSDSCH.AllCAT
Number of Successful RRC Connection

Setups for Cell (Including All the HSDSCH Physical Layer Categories)
BSC6900
WRFD-01061002
WRFD-010699
WRFD-150207
WRFD-150223
HSDPA UE
Category 1 to 28
DC-HSDPA+MIMO
4C-HSDPA
MC-HSDPA+MIMO
73425959
RRC.SuccConnEstab.HSDSCH.CAT7.10

Setups for Cell (including the HS-DSCH
Physical Layer Categories 7 Through 10)
BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
73425960

Physical Layer Categories 13 and 14)
BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
73425961

Setups for Cell (Including the HS-DSCH
BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
73425962

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
73425963

BSC6900
WRFD-01061002
HSDPA UE
Category 1 to 28
73441141
VS.HSDPA.MeanChThrouput.HighLoad
Mean Throughput on HSDPA MAC-d Flow BSC6900

for Cell (Excluding the Data of Low-Traffic
Users)
WRFD-010610
WRFD-01061008
HSDPA Introduction
Package
Interactive and
Background Traffic
Class on HSDPA
67189834
VS.HSDPA.MACD.SuccSetup
Number of Successful HSDPA MAC-d

Flow Establishments for Cell
BSC6910
WRFD-010610
HSDPA Introduction
Package
67189840
VS.HSDPA.MeanChThroughput.TotalBytes
Number of Total Bytes Sent in Downlink of BSC6910

HSDPA MAC-d Flow for Cell
WRFD-010610
HSDPA Introduction
Package
67190698
VS.HSDPA.SHO.ServCellChg.AttOut

WRFD-01061006
HSDPA Mobility
Management
67190699
VS.HSDPA.SHO.ServCellChg.SuccOut

Change Success in RNC for Cell
WRFD-01061006
HSDPA Mobility
Management
67190700
VS.HSDPA.HHO.H2H.AttOutIntraFreq
Number of Intra-Frequency HSDPA Hard

Change for Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67190701
VS.HSDPA.HHO.H2H.SuccOutIntraFreq

BSC6910
Change for Cell
WRFD-01061006
HSDPA Mobility
Management
67190702
VS.HSDPA.HHO.H2H.AttOutInterFreq
Number of Inter-Frequency HSDPA Hard

Change for Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67190703
VS.HSDPA.HHO.H2H.SuccOutInterFreq

BSC6910
Change for Cell
WRFD-01061006
HSDPA Mobility
Management
67190708
VS.HSDPA.HHO.NoChR.Att.NCell
Number of HSDSCH-to-HSDSCH hard

Handover Requests Without Channel
Change Between Neighboring Cells
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67190709
VS.HSDPA.HHO.NoChR.Succ.NCell
Number of Successful HSDSCH-toHSDSCH hard Handovers Without

Channel Change Between Neighboring
Cells
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67190710
VS.HSDPA.ServCellChg.Att.NCell
Number of HSDPA Serving Cell Change

Attempts Between Neighboring Cells
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67190711
VS.HSDPA.ServCellChg.Succ.NCell
Number of Successful HSDPA Serving

Cell Changes Between Neighboring Cells
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67191155
VS.IRATHO.HSDPA.AttOutPSUTRAN
Number of PS Inter-RAT Outgoing

Handover Attempts for HSDPA Services
for Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67191156
VS.IRATHO.HSDPA.SuccOutPSUTRAN
Number of Successful PS Outgoing InterRAT Handovers for HSDPA Services for

Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67191157
VS.HSDPA.HHO.H2D.AttOutIntraFreq
Number of Intra-Frequency H2D Hard

BSC6910
WRFD-01061006
HSDPA Mobility
Management
67191158
VS.HSDPA.HHO.H2D.SuccOutIntraFreq

BSC6910
WRFD-01061006
HSDPA Mobility
Management
67191159
VS.HSDPA.HHO.H2D.AttOutInterFreq
Number of Inter-Frequency H2D Hard

BSC6910
WRFD-01061006
HSDPA Mobility
Management
67191160
VS.HSDPA.HHO.H2D.SuccOutInterFreq

BSC6910
WRFD-01061006
HSDPA Mobility
Management
67192975
VS.RAB.RelReqPS.BE.HSDPA.Cong.Golden Number of HSDPA RABs Carrying Golden BSC6910

Congestion for Cell
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
67192976
VS.RAB.RelReqPS.BE.HSDPA.Cong.Silver
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
Number of HSDPA RABs Carrying Silver

Congestion for Cell
BSC6910
Page 68 of 69
67192977
VS.RAB.RelReqPS.BE.HSDPA.Cong.Copper Number of HSDPA RABs Carrying Copper BSC6910

Congestion for Cell
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
67192991
VS.HSDPAPSLoad.MaxDLThruput.RNC
Maximum Throughput of PS HSDPA

Traffic for RNC
BSC6910
WRFD-010610
HSDPA Introduction
Package
67193578

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67193581

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67193584

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67193587

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67193590

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67193593

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67193596

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67195481
VS.HSDPA.SHO.ServCellChg.AttOutIur

WRFD-01061006
HSDPA Mobility
Management
67195482
VS.HSDPA.SHO.ServCellChg.SuccOutIur

Change Success for Cell
WRFD-01061006
HSDPA Mobility
Management
67195483
VS.HSDPA.HHO.H2H.AttOutIur
Number of Inter-RNC HSDPA Hard

Change for Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
67195484
VS.HSDPA.HHO.H2H.SuccOutIur
Number of Successful Inter-RNC HSDPA BSC6910

Hard Handovers Without Channel Change
for Cell
WRFD-01061006
HSDPA Mobility
Management
67202894
VS.HSDPA.MeanChThroughput
Mean Downlink Throughput of single

HSDPA MAC-d Flows for Cell
BSC6910
WRFD-010610
HSDPA Introduction
Package
67204137
VS.HSDPAPSLoad.DLThruput.RNC
Throughput of PS HSDPA Traffic for RNC
BSC6910
WRFD-010610
HSDPA Introduction
Package
67204259

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67204260

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67204261

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67204262

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67204263

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67204264

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
67204265

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
73393828
VS.HSDPA.MACD.AttSetup
Number of HSDPA MAC-d Flow

Establishment Requests for Cell
BSC6910
WRFD-010610
HSDPA Introduction
Package
73403764
VS.HSDPA.HHO.H2D.AttOutIur
number of Inter-RNC H2D Hard Handover

Attempts for Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
73403765
VS.HSDPA.HHO.H2D.SuccOutIur
Number of Successful Inter-RNC H2D

Hard Handovers for Cell
BSC6910
WRFD-01061006
HSDPA Mobility
Management
73410499
VS.SRNCIubBytesHSDPA.Tx
Number of DL Bytes over Iub HSDSCH for BSC6910

Cell
WRFD-010610
HSDPA Introduction
Package
73422167
VS.HSDPA.RAB.AbnormRel.H2P
Number of RABs Abnormally Released for BSC6910

PS HSDPA Services during the State
Transition from CELL_DCH to CELL_PCH
or URA_PCH for Cell
WRFD-010202
WRFD-010610
UE State in
Connected Mode
(CELL-DCH
CELL-PCH
URA-PCH
CELL-FACH)
HSDPA Introduction
Package
73423462
VS.HSDPA.Traffic.HighLoad
Number of Bytes Sent on HSDPA MAC-d

Flow for Cell (Excluding the Bytes of LowTraffic Users)
BSC6910
WRFD-010610
WRFD-01061008
HSDPA Introduction
Package
Interactive and
Background Traffic
Class on HSDPA
73425958
RRC.SuccConnEstab.HSDSCH.AllCAT

Setups for Cell (Including All the HSDSCH Physical Layer Categories)
BSC6910
WRFD-01061002
WRFD-010699
WRFD-150207
WRFD-150223
HSDPA UE
Category 1 to 28
DC-HSDPA+MIMO
4C-HSDPA
MC-HSDPA+MIMO
73425959

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
73425960

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
Page 69 of 69

73425961

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
73425962

BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
73425963
RRC.SuccConnEstab.HSDSCH.CAT21.24 BSC6910
WRFD-01061002
HSDPA UE
Category 1 to 28
73441141
VS.HSDPA.MeanChThrouput.HighLoad
Mean Throughput on HSDPA MAC-d Flow BSC6910

for Cell (Excluding the Data of Low-Traffic
Users)
WRFD-010610
WRFD-01061008
HSDPA Introduction
Package
Interactive and
Background Traffic
Class on HSDPA
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
12 Reference Documents
1. 3GPP TS 25.214, "Physical layer procedures (FDD)"
2. 3GPP TS 25.306, "UE Radio Access capabilities"
3. 3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSDPA); Overall description"
4. 3GPP TS 25.433, "UTRAN Iub interface NBAP signaling"
5. 3GPP TS 25.435, "UTRAN Iub interface user plane protocols for CCH data flows"
6. Transmission Resource Management Feature Parameter Description
7. Load Control Feature Parameter Description
8. Call Admission Control Feature Parameter Description
9. Directed Retry Decision Feature Parameter Description
10. Differentiated HSPA Service Feature Parameter Description
11. Radio Bearers Feature Parameter Description
12. State Transition Feature Parameter Description
13. Power Control Feature Parameter Description
14. Handover Feature Parameter Description
15. HSPA Evolution Feature Parameter Description
16. QoS Management Feature Parameter Description
17. License Management Feature Parameter Description

Hsdpa PDF

Uploaded by

Document Information

Original Title

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

Hsdpa PDF

Uploaded by

Copyright:

Available Formats

HSDPA Feature Parameter Description

HSDPA Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

HSDPA Feature Parameter Description

2.3 Impact of HSDPA on NEs

5 QoS Management and Management over Differentiated Services

HSDPA Feature Parameter Description

7.5.1 System Capacity

HSDPA Feature Parameter Description

8.16.5 Parameter Optimization

1 About This Document

1.2 Intended Audience

Are familiar with WCDMA basics

Need to understand HSDPA

Work with Huawei products

1.3 Change History

Feature change: refers to the change in the HSDPA feature.

WRFD-010610 HSDPA Introduction Package

For details, see chapters as follows:

In section 4.6 HSDPA Remaining Power Appending, the

The EXTRAPOWER parameter replaced the RESVERD3

HSDPA Feature Parameter Description

Modified descriptions of the CME-based configuration. For details, see

2.2 HSDPA Channels

2.2.1 HS-DSCH and HS-PDSCH

2.2.4 DPCCH and DPCH/F-DPCH

2.3 Impact of HSDPA on NEs

HSDPA Feature Parameter Description

Maximum Number of HS-DSCH

Maximum Number of Data Blocks Maximum Data Rate (Mbit/s)

2.4 HSDPA Functions

2.4.1 HSDPA Control Plane Functions

The HSDPA control plane functions are described as follows:

HSDPA Feature Parameter Description

2.4.2 HSDPA User Plane Functions

3.1 Bearer Mapping

3.2 Access Control

3.3 Mobility Management

3.4 Channel Switching

3.5 Load Control

3.6 Power Resource Management

3.7 Code Resource Management

3.1 Bearer Mapping

Can Be Carried on HS-DSCH?

3.2 Access Control

HSDPA Feature Parameter Description

3.3 Mobility Management

3.4 Channel Switching

New Channel Switching

CELL_DCH (with HS-DSCH) <-> CELL_FACH HS-DSCH <-> FACH

HS-DSCH <-> DCH

Channel switching based on timer

Channel switching based on traffic volume

HSDPA Feature Parameter Description

3.5 Load Control

3.6 Power Resource Management

3.7 Code Resource Management

3.7.1 HS-SCCH Code Resource Management

3.7.2 HS-PDSCH Code Resource Management

If the RNC-controlled static code allocation is used: