14 Hsdpa

RAN Feature Description
Table of Contents
Table of Contents
Chapter 14 HSDPA...................................................................................................................... 14-1
14.1 Summary of Updates.................................................................................................... 14-1
14.2 Introduction................................................................................................................... 14-1
14.2.1 Definition............................................................................................................. 14-1
14.2.2 Purposes............................................................................................................ 14-1
14.2.3 Terms and Abbreviations....................................................................................14-2
14.2.4 Abbreviations...................................................................................................... 14-3
14.3 Availability..................................................................................................................... 14-4
14.3.1 Network Elements Required...............................................................................14-4
14.3.2 Software Releases............................................................................................. 14-4
14.4 Impact........................................................................................................................... 14-5
14.4.1 On System Performance....................................................................................14-5
14.4.2 On Other Features.............................................................................................. 14-5
14.5 Technical Description.................................................................................................... 14-5
14.5.1 HSDPA Configuration Model...............................................................................14-5
14.5.2 Overview............................................................................................................. 14-7
14.5.3 Realization of HSDPA......................................................................................... 14-8
14.5.4 HSDPA Physical Channel.................................................................................14-10
14.5.5 HSDPA Channel Mapping.................................................................................14-13
14.5.6 HSDPA Key Technologies.................................................................................14-15
14.5.7 HSDPA Power Allocation..................................................................................14-30
14.5.8 HSDPA Codes Allocation..................................................................................14-32
14.6 HSDPA and the Other RAN Features..........................................................................14-38
14.6.1 Overview........................................................................................................... 14-38
14.6.2 HSDPA Cell Load Control.................................................................................14-38
14.6.3 HSDPA Power Control......................................................................................14-38
14.6.4 HSDPA Channel Switch....................................................................................14-56
14.6.5 HSDPA Mobility Management...........................................................................14-59
14.6.6 HSDPA Direct Retry.......................................................................................... 14-69
14.6.7 Other Features.................................................................................................14-71
14.7 Capabilities................................................................................................................. 14-72
14.8 Implementation........................................................................................................... 14-72
14.8.1 Enabling HSDPA............................................................................................... 14-72
14.8.2 Reconfiguring Parameters................................................................................14-74
14.8.3 Disabling HSDPA.............................................................................................. 14-78
14.9 Maintenance Information.............................................................................................14-78
14.9.1 MML Commands Related with HSDPA on the RNC Side.................................14-78
Huawei Technologies Proprietary
i
Table of Contents
14.9.2 MML Commands Related with HSDPA on the NodeB Side..............................14-78

14.9.3 Related Alarms................................................................................................. 14-78
14.9.4 Counters........................................................................................................... 14-79
14.10 Reference................................................................................................................. 14-79

ii
List of Figures
List of Figures
Figure 14-1 HSDPA configuration model (1).......................................................................14-6
Figure 14-5 HS-DSCH protocol stack model (the SRNC and CRNC are the same)...........14-8
Figure 14-6 HSDPA protocol stack model when SRNC and CRNC are different (with flow
control)......................................................................................................................... 14-9
Figure 14-7 HSDPA protocol stack model when the SRNC and the CRNC are different
(without flow control).................................................................................................. 14-10
Figure 14-8 Subframe structure of the HS-SCCH.............................................................14-10
Figure 14-9 Subframe structure of the HS-PDSCH...........................................................14-11
Figure 14-10 Frame structure of uplink HS-DPCCH.........................................................14-12
Figure 14-11 Timing relation between PCCPCH, HS-SCCH and HS-PDSCH..................14-12
Figure 14-12 Timing structure at the UE for HS-DPCCH control signaling........................14-13
Figure 14-13 HS-PDSCH mapping...................................................................................14-15
Figure 14-14 Data transmission of the HARQ processes.................................................14-17
Figure 14-15 EPF-based scheduling algorithm periods....................................................14-23
Figure 14-16 HSDPA sharing mechanism.........................................................................14-26
Figure 14-17 Capacity request at the Iub interface...........................................................14-28
Figure 14-18 Structure of capacity request frame.............................................................14-28
Figure 14-19 Capacity allocation procedure at the Iub interface.......................................14-29
Figure 14-20 Structure of the capacity allocation frame....................................................14-30
Figure 14-21 Dynamic Power Allocation...........................................................................14-31
Figure 14-22 Static codes allocation.................................................................................14-34
Figure 14-23 Shared codes............................................................................................... 14-36
The RNC periodically monitors how the code resource is used and decides to extend or
reduce the codes reserved for the HS-PDSCH..........................................................14-36
Figure 14-24 Extending the codes reserved for HS-PDSCH.............................................14-36
Figure 14-25 Reducing the codes reserved for HS-PDSCH.............................................14-37
Figure 14-26 HS-DPCCH Power Offsets..........................................................................14-39
iii
List of Figures
Figure 14-27 Different status of the RRC of the UE..........................................................14-56

Figure 14-28 Soft handover between the HSDPA and R99 cells (HSDPAR99)...............14-61
Figure 14-29 Hard handover between the HSDPA and R99 cells (HSDPAR99)..............14-61
Figure 14-30 Soft handover between the HSDPA and R99 cells (R99HSDPA)...............14-62
Figure 14-31 Hard handover between the HSDPA and R99 cells (R99HSDPA)..............14-63
Figure 14-32 Soft handover between two HSDPA cells (the best cell changes)...............14-65
Figure 14-33 Hard handover between HSDPA cells..........................................................14-66
Figure 14-34 Soft handover between HSDPA cells (HSDPA service cell is deleted from active
set)............................................................................................................................. 14-67
Figure 14-35 Handover procedure from the UMTS to GSM/GPRS of the CS services.....14-68
Figure 14-36 Handover procedure from the UMTS to the GSM/GPRS of the PS services...1469
Figure 14-37 Direct retry procedure..................................................................................14-71

iv
List of Tables
List of Tables
Table 14-1 NEs required for HSDPA...................................................................................14-4
Table 14-2 RAN products and related versions...................................................................14-5
Table 14-3 Traffic classes supported by the HS-DSCH.....................................................14-13
Table 14-4 Factors affecting the mapping.........................................................................14-14
Table 14-5 Max Retransmission Count..............................................................................14-16
Table 14-6 Coding combination modes supported by HARQ............................................14-16
Table 14-7 UE categories at physical layer.......................................................................14-17
Table 14-8 Coding rate and modulation mode based on the CQI......................................14-18
Table 14-9 Resource Allocate Method...............................................................................14-19
Table 14-10 HS-PDSCH MPO Constant...........................................................................14-20
Table 14-11 Initial BLER.................................................................................................... 14-21
Table 14-12 Scheduling Method........................................................................................ 14-21
Table 14-13 Weight of SPI................................................................................................. 14-23
Table 14-14 SPI related parameter values........................................................................14-24
Table 14-15 Resource Limiting Switch..............................................................................14-25
Table 14-16 Resource Limiting Ratio for SPI.....................................................................14-25
Table 14-17 GBR for SPI................................................................................................... 14-26
Table 14-18 HSDPA scheduling sample............................................................................14-27
Table 14-19 HSDPA basic scheduling algorithms..............................................................14-27
Table 14-20 HS-PDSCH And HS-SCCH Power................................................................14-31
Table 14-21 Power Margin................................................................................................ 14-32
Table 14-22 Code Number for HS-SCCH..........................................................................14-33
Table 14-23 Allocate Code Mode......................................................................................14-33
Table 14-24 Code Number for HS-PDSCH.......................................................................14-34
Table 14-25 Code Max Number for HS-PDSCH................................................................14-35
Table 14-26 Code Min Number for HS-PDSCH.................................................................14-35
Table 14-27 Reserved SF threshold..................................................................................14-37
Table 14-28 ACK poweroffset............................................................................................ 14-40
Table 14-29 ACK poweroffset multi-RLS...........................................................................14-41

v
List of Tables
Table 14-30 NACK poweroffset......................................................................................... 14-42

Table 14-31 NACK poweroffset multi-RLS........................................................................14-43
Table 14-32 CQI Power Offset........................................................................................... 14-44
Table 14-33 CQI Power Offset multi-RLS..........................................................................14-44
Table 14-34 SIR Init Target Value......................................................................................14-45
Table 14-35 ACK-NACK Repetition Factor........................................................................14-46
Table 14-36 ACK-NACK Repetition Factor multi-RLS.......................................................14-47
Table 14-37 CQI Repetition Factor....................................................................................14-47
Table 14-38 CQI Repetition Factor multi-RLS...................................................................14-48
Table 14-39 CQI Feedback Cycle k...................................................................................14-48
Table 14-40 CQI Feedback Cycle k multi-RLS..................................................................14-49
Table 14-41 HS-SCCH Power Control Method..................................................................14-50
Table 14-42 HS-SCCH Power........................................................................................... 14-50
Table 14-43 HS-SCCH FER.............................................................................................. 14-51
Table 14-44 HS-SCCH SF4 Power Offset.........................................................................14-52
Table 14-45 HS-SCCH SF8 Power Offset.........................................................................14-52
Table 14-46 HS-SCCH SF16 Power Offset.......................................................................14-53
Table 14-49 HS-SCCH SF128 Power Offset.....................................................................14-55
Table 14-50 HS-SCCH SF256 Power Offset.....................................................................14-56
Table 14-51 Channel type transition after introducing HSDPA..........................................14-57
Table 14-52 Connections between the UE and network...................................................14-59
Table 14-53 Scenarios of handover between the HSDPA cell and R99 cell......................14-60
Table 14-54 Scenarios of handover between two HSDPA cells.........................................14-64
Table 14-55 HS-PDSCH TX diversity mode......................................................................14-71
Table 14-56 MAC-hs Reset Algorithm Switch....................................................................14-72
Table 14-57 Data reconfiguration commands for RNC-oriented HSDPA (on RNC side). . .14-74
Table 14-58 Data reconfiguration commands for cell-oriented HSDPA (on RNC side)......14-75
Table 14-59 HSDPA data reconfiguration commands (on NodeB side).............................14-77
Table 14-60 Alarms related to HSDPA...............................................................................14-79
Table 14-61 HSDPA counters............................................................................................ 14-79

vi
Chapter 14 HSDPA
Chapter 14 HSDPA
14.1 Summary of Updates
This section provides the update history of this manual and introduces the contents of
subsequent updates.
Manual Version
01 (2006-10-11)
Description
Modified the description of channel switching between HSDSCH and DCH in section 14.6.4
14.2 Introduction
14.2.1 Definition
High Speed Downlink Packet Access (HSDPA) is an important feature of the 3GPP
R5. As a downlink (DL) high-speed data transmission solution, its theoretical
maximum rate over the air interface is 14.4 Mbit/s.
The main features of HSDPA are as follows:
The frames transmitted over the air interface are 2 ms.
The HARQ and AMC technologies are applied by the physical lately.
The high order 16QAM modulation mode is used to improve spectral efficiency.
Both code division and time division are used to schedule UEs.
14.2.2 Purposes
HSDPA improves the performance of UMTS network in the following aspects:
Higher DL peak transmission rate: the highest rate reaches 14.4 Mbit/s
Shorter service delay: providing a faster service experience to the subscribers,

for example in receiving e-mails and browsing web pages
More efficient DL codes and power utilization: for macro cell coverage, the
capacity is 50% higher; for micro cell coverage, the capacity is 200%300% or
higher

1
Chapter 14 HSDPA
14.2.3 Terms and Abbreviations

I. Terms
Term
HARQ
Definition
The key technology of HSDPA, including two times of rate
matching and a virtual buffer. One HARQ entity provides
multiple HARQ processes for one UE. Only one HARQ
process runs in the transmission time interval (TTI) of the HSDSCH.
AMC
The UE sends CQI through the HS-DPCCH to the NodeB to

report the channel quality. The NodeB decides the size of the
transport blocks and modulation mode according to the CQI.
When the UE is in good radio environment, the transmission
can adopt the high order 16QAM modulation mode and large
transport blocks to achieve high peak rate.
When the UE is in poor radio environment, the transmission
can adopt low order QPSK modulation mode and small
transport blocks to ensure communication quality.
Servicing HSDPA
A cell that can provide HSDPA connection and HSDPA service
cell
to the UEs. One UE can have at most one servicing HSDPA

cell at one time.
MAC-hs
Divided into the MAC-hs on the NodeB side and the MAC-hs
on the UE side.
The MAC-hs on the NodeB side includes four entities: HARQ,
scheduling/priority handing, TFRC selection and flow control.
The MAC-hs on the UE side includes HARQ, reordering
queue distribution, reordering and disassembly.
scheduling/priority
To allocate the HS-DSCH resources between the data flow
handling
entity and the HARQ entity according to the priorities.

To decide whether to send or resend according to UL
feedback signaling (the ACK or the NACK).
To set priorities, queuing ID and data block number.
TFRI selection
The entity selects a transmission mode according to the

current channel and resources.

2
Chapter 14 HSDPA
Term
HSDPA cell
Definition
Refers to the cell that supports the HSDPA channel and
provides HSDPA service to the UEs.
R99 cell
Refers to the cell without the HSDPA channel and cannot

provide HSDPA service to UEs.
HSDPA channel
The physical channels of HSDPA, including HS-SCCH, HSPDSCH, and HS-DPCCH.
R99 channel
All physical channels other than the HSDPA channel.
HSDPA
A connection between a cell and a UE when the service the
connection
UE applies to is carried on HS-DSCH.
DPCH connection
A connection between a cell and a UE when the service the

UE applies to is totally carried on HS-DSCH.
HS-DSCH
The transmission channel of HSDPA
channel
14.2.4 Abbreviations
Abbreviation
Full name
16QAM
16 Quadrature Amplitude Modulation
ACK
Acknowledgement
AMC
Adaptive Modulation and Coding
BE
Best Effort
CAC
Call Admission Control
CmCH-PI
Common Transport Channel Priority Indicator
CQI
Channel Quality Indicator
CRNC
Controlling Radio Network Controller
DCH
Dedicated Channel
DPCH
Dedicated Physical Channel
DTCH
Dedicated Traffic Channel

3
Chapter 14 HSDPA
Abbreviation
Full name
EDGE
Enhanced Data rates for GSM Evolution
FACH
Forward Access Channel
FP
Frame Protocol
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communications
HARQ
Hybrid Automatic Repeat Request
HSDPA
High Speed Downlink Packet Access
HS-DPCCH
Dedicated Physical Control Channel (uplink) for HS-DSCH
HS-DSCH
High Speed Downlink Shared Channel
HS-PDSCH
High Speed Physical Downlink Shared Channel
HS-SCCH
Shared Control Physical Channel for HS-DSCH
IR
Increment Redundancy
LDM
Load Monitoring
MAC-hs
Medium Access Control for HSDPA
NACK
Negative Acknowledgement
PCCPCH
Primary Common Control Physical Channel
PDU
Protocol Data Unit
QoS
Quality of Service
QPSK
Quaternary Phase Shift Keying
RLC
Radio Link Control
RNC
Radio Network Controller
RTT
Round Trip Time
SF
Spreading Factor
UE
User Equipment
UTRAN
UMTS Radio Access Network
WCDMA
Wideband Code Division Multiple Access

4
Chapter 14 HSDPA
14.3 Availability
14.3.1 Network Elements Required
The realization of HSDPA depends on the cooperation of the NodeB, the RNC and
the CN.
Table 1.1 describes the NEs required for HSDPA.
Table 1.1 NEs required for HSDPA
UE
NodeB
RNC
MSC
MG
Server
SGSN
GGSN
HLR
Note:
: not required
: required
Note:
This chapter describes only the availability of the NodeB and the RNC.
14.3.2 Software Releases

Table 1.1 describes the versions of RAN products that support HSDPA.
Table 1.1 RAN products and related versions
Product
Version
RNC
BSC6800
V100R005 and later releases
NodeB
DBS3800
BTS3812A
BTS3812E

5
Chapter 14 HSDPA
14.4 Impact
14.4.1 On System Performance
HSDPA increases the system capacity and shortens the data transmission delay.
14.4.2 On Other Features

The impact of HSDPA on the other HUAWEI UMTS RAN features is as follows:
HSDPA does not prevent the other features from taking effect.
The realization of HSDPA needs the support of power control, load control,
admission control, and mobility management.
HSDPA and the other features have interactive influences on each other. For
details, see section 14.6"HSDPA and the Other RAN Features."
14.5 Technical Description

14.5.1 HSDPA Configuration Model
The configuration model for HSDPA is as show in Figure 1.1, Figure 1.2 and Figure
1.3.
RNC
NodeB
RadioClass
RadioClass
GlobalParaClass
CellClass
CellClass
HOCOMM .Class
CELLHSDPA .Class
MACHSPARA .Class
COIFTIMER .Class
CELLHSDPCCH .Class
MACHSSPIPARA.Class
UESTATETRANS .Class
CELLSETUP.Class
HSSCCH .Class
CELLALGOSWITCH.Class
Figure 1.1 HSDPA configuration model (1)

6
Chapter 14 HSDPA
MACHSPARA .Class
MACHSSPIPARA.Class
Initial BLER
Resource limiting ratio for SPI
Max Retransmission Count
GBR for SPI
Resource Allocate Method
Weight of SPI
Scheduling Method
CELLHSDPA .Class
Resource Limiting Switch
Code Number for HS-SCCH
Power Margin
Code Number for HS-PDSCH
HS-SCCH Power Control Method
Code Max Number for HS-PDSCH
HS-SCCH Power
HS-PDSCH MPO Constant

Code Min Number for HS-PDSCH
HS-SCCH FER
HS-PDSCH And HS-SCCH Power

Allocate Code Mode
Reserved SF threshold

CELLHSDPCCH .Class
UESTATETRANS .Class
NACK poweroffset
BE HS-DSCH to FACH transition timer
NACK poweroffset multi-RLS
Realtime Traff DCH to FACH transition timer
ACK poweroffset
ACK poweroffset multi-RLS
SIR Init Target Value
CQI Power Offset
ACK-NACK Repetition Factor
CQI Power Offset multi-RLS
ACK-NACK Repetition Factor multi-RLS
CQI Repetition Factor multi-RLS
CQI Repetition Factor
CQI Feedback Cycle k
CQI Feedback Cycle k multi-RLS
HOCOMM .Class
COIFTIMER .Class
The timer length of D2H handover
HSDPA hysteresis timer length
H Retry TimerLength

7
Chapter 14 HSDPA
HSSCCH .Class
CELLSETUP.Class
HS-SCCH SF4 POWER OFFSET
HS-PDSCH TX diversity mode
CELLALGOSWITCH.Class
MAC-hs Reset Algorithm Switch
14.5.2 Overview
This section introduces the following information of HSDPA:
Realization of HSDPA
HSDPA Physical Channel
HSDPA Channel Mapping
HSDPA Key Technologies
HSDPA Power Allocation
HSDPA Codes Allocation
14.5.3 Realization of HSDPA

I. Realization of HSDPA on the RAN Side
The feature of HSDPA is realized through enhancing the functions of the access
stratum:
Adding MAC-hs and HSDPA physical layer processing on both the UE and the
NodeB sides
Transmitting the user plane data flow through the HS-DSCH FP between the
SRNC, CRNC, and NodeB
II. Realization of HSDPA at the CN side

Because the UTRAN supports higher transmission rate, the PS domain needs to
support higher rate of service assignment and user plane transmission and switching.
III. HSDPA Protocol Stack

The MAC-hs are added on both the UE and NodeB sides after HSDPA is introduced.
HSDPA data and control frames on the SRNC side are transmitted to the MAC-hs of
NodeB in the following two ways:
Trough Iub when the SRNC and the CRNC are the same

8
Chapter 14 HSDPA
Trough lur and then Iub when the SRNC and the CRNC are different
See the following for details.

1)
HSDPA protocol stack model when the SRNC and the CRNC are the same
Figure 1.1 shows the model when the SRNC and CRNC are the same.
DTCH
DTCH
DCCH
MAC-d
DCCH
MAC-d
MAC-hs
MAC-hs
HS-DSCH
FP
HS-DSCH FP
PHY
PHY
TNL
TNL
Uu
UE
NodeB
PHY: Physical Layer
Iub
CRNC/SRNC
TNL: Transport Network Layer
Figure 1.1 HS-DSCH protocol stack model (the SRNC and CRNC are the same)
See the following description about the figure above:
The MAC-d of the SRNC sends the MAC-d PDUs through FP to the MAC-hs of
the NodeB.
The MAC-hs of the NodeB completes the scheduling of the data between the
UEs that camp on the HSDPA cells.
The MAC-hs of the NodeB sends the MAC-hs PDU through Uu interface to the
equivalent MAC-hs of the UE.
2)
HSDPA protocol stack model when the SRNC and the CRNC are different (with
flow control)
Figure 2.1 is the HSDPA protocol stack model under flow control when the SRNC and
the CRNC are different.
In this case, the MAC-d data flow of the SRNC is sent through the MAC-c/sh of the
CRNC. Compared with 3GPP R99 protocol, the CRNC can now take charge of flow
control and the data rate control between SRNC MAC-d and NodeB MAC-hs.

9
Chapter 14 HSDPA
DTCH DCCH
DTCH DCCH
MAC-d
MAC-d
MAC-hs
MAC-hs
HSDSCH
FP
PHY
PHY
TNL
UE
Uu
NodeB
CRNC HS-DSCH
flow control
HSHSDSCH
DSCH
FP
FP
TNL
Iub
HS-DSCH FP
TNL
CRNC
TNL
Iur
SRNC
Figure 2.1 HSDPA protocol stack model when SRNC and CRNC are different (with
flow control)
See the following description about the figure above:
The HS-DSCH FP of Iub interface controls the data flow between the NodeB
MAC-hs and the CRNC.
The Iur HS-DSCH FP controls the data flow between the SRNC MAC-d and the
CRNC.
3)
HSDPA protocol stack model when the SRNC and the CRNC are different
(without flow control)
Figure 3.1 is the HSDPA protocol stack model when the SRNC and the CRNC are
different (without flow control). In this case, the data flow of SRNC MAC-d is not sent
through the CNRC MAC-c/sh.

10
Chapter 14 HSDPA
DTCH DCCH
DTCH DCCH
MAC-d
MAC-d
MAC-hs
MAC-hs
PHY
PHY
UE
Uu
HSDSCH
FP
HS-DSCH FP
TNL
TNL
NodeB
Iub
TNL
CRNC
TNL
Iur
SRNC
Figure 3.1 HSDPA protocol stack model when the SRNC and the CRNC are different
(without flow control)
14.5.4 HSDPA Physical Channel

There are three types of channels added for HSDPA at the physical layer:
HS-SCCH
HS-PDSCH
HS-DPCCH
The following describes in details their functions.
I. HS-SCCH
The HS-SCCH is a fixed rate (60 kbps, SF=128) downlink physical channel used to
carry downlink signaling related to HS-DSCH transmission. Figure 1.1 shows the
subframe structure of the HS-SCCH.
Data
Ndata1 bits
Tslot = 2560 chips, 40 bits
Slot # 0
Slot # 1
1 subframe: Tf = 2 ms
Figure 1.1 Subframe structure of the HS-SCCH

The following control information is carried by HS-SCCH:

11
Slot # 2
Chapter 14 HSDPA
HS-PDSCH channelization code set information
HS-PDSCH modulation scheme information
Transport block size information
Hybrid ARQ process information
Redundancy and constellation version
New data indicator
UE identify
II. HS-PDSCH
The HS-PDSCH is used to carry the HS-DSCH data.
The spreading factor of the HS-PDSCH can be 16 only. Each cell can provide at most
15 HS-PDSCHs whose codes must be continuous. The number of HS-PDSCH codes
used by the UE depends on UE category. The UE of category 10 can support a
maximum of 15 HS-PDSCH codes and 16QAM modulation mode. The supported
peak rate on the air interface can reach 14.4 Mbps.
The subframe structure and slot structure are shown in Figure 1.1.
Data
Ndata1 bits
Tslot = 2560 chips, M * 10 * 2K bit/s ( k=4 )
Slot # 0
Slot # 1
Slot # 2
1 subframe: Tf = 2 ms
Figure 1.1 Subframe structure of the HS-PDSCH

An HS-PDSCH may use QPSK or 16QAM modulation symbols. In Figure 1.1, M is
the number of bits per modulation symbol, that is, M = 2 for QPSK and M = 4 for
16QAM.
III. HS-DPCCH
Figure 1.1 shows the subframe structure of HS-DPCCH. The HS-DPCCH carries
uplink feedback signaling related to downlink HS-DSCH transmission. The HS-DSCH
related feedback signaling consists of HARQ-ACK and CQI. The HARQ-ACK is
carried in the first slot of the HS-DPCCH subframe, and the CQI is carried in the
second slot and the third slot of a subframe.

12
Chapter 14 HSDPA
Tslot = 2560 chips
2 x Tslot = 5120 chips
HARQ-ACK
CQI
One HS-DPCCH subframe ( 2ms )
Subframe # 0
Subframe # i
Subframe # 4
One radio frame : Tf = 10 ms
Figure 1.1 Frame structure of uplink HS-DPCCH

The spreading factor of the HS-DPCCH is 256, that is, there are 10 bits per uplink
HS-DPCCH slot.
IV. PCCPCH, HS-SCCH and HS-PDSCH Timing

Figure 1.1 shows the timing relation between PCCPCH, HS-SCCH, and HS-PDSCH.
10 ms
PCCPCH
HS-SCCH
3 slot
HS-PDSCH
2 slot
Figure 1.1 Timing relation between PCCPCH, HS-SCCH and HS-PDSCH
V. Uplink DPCCH/HS-DPCCH/HS-PDSCH Timing at the UE

Figure 1.1 shows the timing offset between the uplink DPCH, the HS-PDSCH and the
HS-DPCCH at UE. An HS-DPCCH subframe starts with m 256 chips after the
start of an uplink DPCH frame that corresponds to the DL DPCH or F-DPCH frame
from the HS-DSCH serving cell that contains the beginning of the related HS-PDSCH
subframe.
m is calculated with the following formula:
m = (TTX_diff/256) + 101
13
Chapter 14 HSDPA
Where TTX_diff is the difference in chips (TTX_diff = 0, 256, ..., 38144), between
The transmit timing of the start of the related HS-PDSCH subframe, and
The transmit timing of the start of the downlink DPCH or F-DPCH frame from the
HS-DSCH serving cell that contains the beginning of the HS-PDSCH subframe.
Tslot 2560 chips
Uplink
DPCH
Slot # 0
Slot # 1
Slot # 2
Slot # 3
Slot # 4
Slot # 5
Slot # 6
Slot # 7
Slot # 8
3 x Tslot = 7680 chips

HS-PDSCH
at UE
UEP
19200 chips
Uplink
HS-DPCCH
M * 2560 chips
Figure 1.1 Timing structure at the UE for HS-DPCCH control signaling
14.5.5 HSDPA Channel Mapping

I. Services Supported by the HS-DSCH
The HS-DSCH supports three traffic classes, as listed in Table 1.1.
Table 1.1 Traffic classes supported by the HS-DSCH
Traffic classes
Streaming
Description
The switch [PS_STREAMING_ON_HSDPA_SWITCH] decides the
streaming service on the HS-DSCH.
When the switch is on, the streaming service is mapped to the

HS-DSCH.
When the switch is off, the streaming service is mapped to the

DPCH.
Interactive
The generic term for the two services is BE service.
Background
The BE services are mapped to the HS-DSCH whenever possible.
II. Factors Affecting the Mapping

When the UE initiates a service request, the RNC decides whether to map the service
to the HS-DSCH according to the factors listed in Table 1.1.

14
Chapter 14 HSDPA
Table 1.1 Factors affecting the mapping

Factor
Description
Traffic
Indicates whether the HS-DSCH supports this service or not, as
classes
listed in I. 1Table 1.1.
Service rate
The HS-DSCH can carry a service only when its service rate is
higher than the rate threshold.
The service rate thresholds are:
DL streaming service HSDPA threshold
DL BE service HSDPA threshold
Cell type
Indicates whether the cell provides the HS-DSCH
UE type
Indicates whether the UE supports HSDPA
Detail description of the mapping of HS-DSCH transport channel is written in section

Transport Channel Selection of feature Radio Bears.
Note:
The combination of the two HSDPA services can be carried by the same HSDSCH.
The UE needs admission of the HS-DSCH to access the network after the
mapping. For the process of the admission decision, see section 14.6.2"HSDPA
Cell Load Control."
III. HS-DSCH Mapping

The mapping from the traffic channel to HSDPA is shown in Figure 1.1.

15
Chapter 14 HSDPA
TRB
SRB
RLC
RLC
DTCH
DCCH
MAC - D
MAC - D
DCH
HS-DSCH FP
DCH
DCH FP
DCH FP
Iub
HS-DSCH
HS-SCCH
HS-PDSCH
DPCH
HS-DPCCH DPDCH DPDCH

DPCCH
DPCCH
DPCH
DPCCH DPDCH DPCCH DPDCH
Cell 2
Cell 1 HSDPA serving cell
Figure 1.1 HS-PDSCH mapping

When a DL RAB is mapped to the HS-DSCH, UL DCH is set up regardless of the
existence of UL data. UL DCH transmits the UL signaling, UL RLC acknowledgement
message and possible UL service data. DL DCH is set up to transmit the DL
signaling. These DCHs are called associated DCHs in the following sections, and the
corresponding DPCHs are called associated DPCHs.
Note:
When the UE is in soft handover, its HSDPA DL data can be carried by one HS-DSCH
cell at most while the non-HSDPA data can be carried by DPCHs in many cells.
14.5.6 HSDPA Key Technologies

HSDPA key technologies include:
2 ms TTI
Link adaptation through HARQ and AMC at the physical layer

16
Chapter 14 HSDPA
Flexible scheduling by code division and time division
I. 2 ms TTI
By using 2 ms TTI at the air interface, HSDPA acquires the following advantages:
Faster data scheduling
Faster data transmission
Shorter delay
II. HARQ
1)
HARQ technology
In R99, if errors occur when the UE decodes a transport block at the physical layer,
the block is discarded, and the block will be retransmitted at a higher layer, for
example, RLC. For HSDPA services at the physical layer, if errors happen to
decoding, the HARQ reserves the data before the decoding and combines it with the
retransmitted data.
Compared with R99, HARQ retransmission is faster and more efficient than RLC
retransmission. In this sense, the HARQ can be called a new technology and a
combination of the Forward Error Correction (FEC) and ARQ. HARQ has a higher
downlink performance gain.
The maximum retransmission count or attempts can be set on the NodeB LMT.
Table 1.1 Max Retransmission Count
Parameter Name
Max Retransmission Count
Parameter ID
MXRETRAN
GUI Range
010
Physical Range & Unit
Times
Default Value
Optional/Mandatory
Mandatory
MML Command
SET MACHSPARA
Description:
The maximum retransmission count or attempts of the HARQ process.
The HARQ supports two coding combination modes as listed in Table 1.2.

17
Chapter 14 HSDPA
Table 1.2 Coding combination modes supported by HARQ

Coding Combination
Chase combing
Increment redundancy
Description
Comparison
Retransmits the
The second mode is better in that the
same bit set.
inconsistency
Retransmits
different bit sets.
between
the
retransmitted bit set and the former

bit set increases the redundant data
and the possibility of recovery from
errors on the air interface.
2)
HARQ Entity and Process
Every HSDPA user has an HARQ entity on both the UE and NodeB sides, each
having up to six HARQ processes.
Several HARQ processes used together can fully utilize the transmission capability of
the air interface, as shown in Figure 2.1.
HS-SCCH
HS-SCCH
HS-PDSCH
HARQ process 1
HS-PDSCH
12 ms or more
HS-SCCH
HS-SCCH
HS-PDSCH
HARQ process 2
HS-PDSCH
12 ms or more
Figure 2.1 Data transmission of the HARQ processes

It takes about 12 ms for an HARQ from sending the MAC-hs PDU to receiving the
ACK/NACK (RTT). In an HARQ process, it takes only 2 ms to send data within an
RTT.
By using several HARQ processes, more data can be sent within an RTT, as shown
in Figure 2.1:
In this case, the first process sends data in the first 2 ms, and then starts to wait.
In the second 2 ms, the second process sends data, and then starts to wait.
With such multiple processes, each 2 ms can be used to send data to the UE.

18
Chapter 14 HSDPA
The capability to receive the data on the HS-PDSCH every 2 ms depends on UE

categories. UEs of some categories can only receive such data every 4 ms or 6 ms.
Table 1.1 describes the capabilities of UE with different categories.
Table 1.1 UE categories at physical layer
UE
Maximum
Minimum
Maximum Number
Total Number
Category
Number of
Inter-TTI
of Bits of an HS-
of Soft Channel
HS-DSCH
Interval
DSCH Transport
Bits
Codes
Block Received
Received
Within an HS-DSCH
TTI
Category 1
7298
19200
Category 2
7298
28800
Category 3
7298
28800
Category 4
7298
38400
Category 5
7298
57600
Category 6
7298
67200
Category 7
10
14411
115200
Category 8
10
14411
134400
Category 9
15
20251
172800
Category
15
27952
172800
3630
14400
3630
28800
10
Category
11
Category
12
UEs of Categories 11 and 12 support QPSK only.
III. AMC
The UE reports the CQI to the NodeB through the HS-DPCCH and the NodeB
decides the size of the transport block and the modulation mode according to the
radio environment indicated by the CQI, as listed in Table 1.1.

19
Chapter 14 HSDPA
Table 1.1 Coding rate and modulation mode based on the CQI
Condition of the Radio
Modulation Mode and
Environment
Coding Rate
Good (The UE is near
Poor (The UE is at the
Large transport block
QPSK low order
High communication
modulation
quality
boarder of the cell or

is
High peak rate
modulation
the NodeB)
there
16QAM high order
Result
severe
Small transport block
attenuation)
Identical transport blocks can use different combinations between code and power.
For example, a transport block with 3319 bits can be carried by four or five HSPDSCH codes. The difference is that the block carried by four codes consumes a
higher power. This involves the Resource Allocate Method parameter, a code power
priority rule that defines preferably used codes or power.
In general, macro cells have a poor radio environment, which results in restricted
power. In this situation, the downlink power of a cell is used up while the downlink
code resources are redundant. On the contrary, micro cells have a good radio
environment, which results in restricted codes resources. In this situation, the
downlink codes resources of a cell are used up, while there is extra power. To
improve cell throughput, the Resource Allocate Method parameter can be set on the
NodeB LMT.
Table 1.2 Resource Allocate Method
Parameter Name
Resource Allocate Method
Parameter ID
RSCALLOCM
GUI Range
CODE_pri (code priority), POWER_prj (power priority)
Method
Default Value
CODE_prj
Optional/Mandatory
Mandatory
MML Command
SET MACHSPARA
Description:
Selecting code priority or power priority.

20
Chapter 14 HSDPA
IV. CQI
The UE reports the CQI according to the measurement values of the pilot channel.
After demodulating and decoding the CQI on the HS-DPCCH, the NodeB obtains
CQI report reported by the UE.

For the purpose of CQI reporting, the UE shall assume a total received HS-PDSCH
power of
PHSPDSCH PCPICH in dB,
14-1
According to simulation results, we think that the MPO, that is
Max (6, Min (13, PCellMAX PCPICH MPO constant )) in dB
14-2
where PCellMAX PCPICH equals cell maximum transmitting power minus the CPICH
transmitting power in dB, HS-PDSCH MPO Constant parameter( MPO constant ) can
be set on the RNC LMT.
Table 1.1 HS-PDSCH MPO Constant
Parameter Name
HS-PDSCH MPO Constant
Parameter ID
HSPDSCHMPOCONSTENUM
GUI Range
Minus 3.0DB, Minus 2.5DB....... 18.5DB,19.0DB
-3.0dB, -2.5dB.....18.5dB, 19dB
Default Value
2.5DB(2.5dB)
Optional/Mandatory
Mandatory
MML Command
ADD CELLHSDPA
Unit:0.5dB
Description:
This parameter sets MPO constant( MPOcons tan t ).to calculate MPO( ).
Two factors may affect the accuracy of the CQI reported by the UE:
Channel environment of the UE
Measurement error of a specific UE

21
Chapter 14 HSDPA
If the CQI reported by the UE is too high, the BLER of the HS-PDSCH increases,
which affects the QoS and reduces the rate on the air interface. If the CQI is too low,
the power efficiency decreases.
To prevent the negative impact caused by inaccurate CQI, the NodeB corrects the
offset of the reported CQI according to the initial BLER target. The corrected CQI is
used for MAC-hs scheduling. The Initial BLER target can be set on the NodeB LMT.
Table 1.2 Initial BLER
Parameter Name
Initial BLER
Parameter ID
IBLER
GUI Range
150
Percent
Default Value
10
Optional/Mandatory
Mandatory
MML Command
SET MACHSPARA
Description:
Setting of the initial BLER target.
V. HSDPA Scheduling Algorithm

Huawei supports four scheduling algorithms:
Max C/I
RR (round Robin)
PF (proportional fair)
EPF (enhanced proportional fair)
The Scheduling Method parameter can be set on the NodeB LMT.

22
Chapter 14 HSDPA
Table 1.1 Scheduling Method

Parameter Name
Parameter ID
GUI Range
Scheduling Method
SM
EPF (Enhanced PF), PF (PF), RR (Round
Robin), MAXCI (Max C/I )

Default Value
Optional/Mandatory
MML Command
Method
EPF
Mandatory
SET MACHSPARA
Description:
Selecting the scheduling algorithms.
All scheduling algorithms support the retransmission priority rule. If a UE requires

retransmission at a certain scheduling time, the UE is scheduled at a higher priority.
Retransmission is not described in the algorithms below.
Max C/I
The CQI of the UE is taken into account. Retransmission is placed at the highest
priority. The UEs that require retransmission are scheduled first. The other UEs
are scheduled in the sequence based on CQI, starting from the UE with the
highest CQI.
The Max C/I algorithm enables higher cell throughput, but has unfair scheduling.
RR
The retransmission and waiting time of the UE are taken into account. The UEs
that require retransmission are schedules first. The other UEs are scheduled in
the sequence based on waiting time, starting from the UE with the longest
waiting time.
The RR algorithm does not take channel quality into account, which results in
low cell throughput, but the algorithm enables fair scheduling.
PF
Channel quality, UE scheduling equity, and UE priority are taken into account.
The scheduling priority is calculated with the following formula:
Pr iority i FUN ( Ri _ max (t ), ri (t ), SPI )

(1)
Where:
23
Chapter 14 HSDPA
Ri _ max (t ) is the instant rate at the scheduling time of t when UE i in the
radio environment is schedules.
SPI is the weighted coefficient related to UE priority.
ri (t ) is the filtered scheduling rate that is calculated with the following

formula:
ri (t ) FUN (Tc , ri (t 1), Ri (t 1))
(2)
Where:
Tc is the time smoothing constant.
Ri (t ) is the scheduling rate of the UE at the time of t.
Tc : Assuming that the typical value is 800 with the unit of 2 msTTI,
the rate filtering window is 1.6 s.
EPF
Based on the PF algorithm, the EPF algorithm can provides users with
Guaranteed Bit Rate (GBR) services such as streaming service.
Figure 1.2 shows the EPF-based scheduling algorithm periods. Each period is
segmented into three parts.
Scheduling
algorithm period
Scheduling
algorithm period
Scheduling
algorithm period
Scheduling
algorithm period
Time
GBR service s
cheduled with PF( X )
GBR service
forcibly scheduled ( Y )
All service
scheduled with PF( Z )
Figure 1.2 EPF-based scheduling algorithm periods

In Figure 1.2:
In the X time segment, GBR services are scheduled with the PF algorithm.
In the Y time segment, UEs accessing GBR services are scheduled according to
their priority.
In the Z time segment, all services are scheduled with the PF algorithm.
The sizes of the X, Y, and Z time segments can be dynamically changed to increase
cell throughput with guaranteed GBR.
24
Chapter 14 HSDPA
Table 2.1 describes SPI , the Weight of SPI parameter.

Table 2.1 Weight of SPI
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Weight of SPI
SPIWEIGHT
1100
Percent
Refer to Table 2.2.
Mandatory
SET MACHSSPIPARA
Description:
The parameter Weight of SPI is used in the scheduling algorithm to select the
queue to send data. The bigger the Weight of SPI is, the more the queue can be
scheduled.
Configuration Rule and Restriction:

This parameter is valid only when Scheduling Method is set to EPF.
For the values of the parameter, refer to Table 1.1.
Table 2.2 SPI related parameter values

SPI
Resource Limiting Ratio
GBR for SPI
Weight of SPI
for SPI (Percent)
(kbps)
(Percent)
15
64
80
15
64
80
15
64
80
15
64
80
15
64
80
15
64
80
15
64
90

25
SPI
Chapter 14 HSDPA
Resource Limiting Ratio
GBR for SPI
Weight of SPI
for SPI (Percent)
(kbps)
(Percent)
15
64
100
15
64
100
15
64
100
10
15
64
100
11
15
64
80
12
15
64
80
13
20
128
90
14
25
256
100
15
20
128
100
In a network, there may be some UEs with a poor radio environment. Much cell
resources will be consumed in order to guarantee these poor UEs GBR service rate,
and the cell resources left for other UE are quite few. To avoid this case, resource
limiting is used. This function can be enabled by the parameter Resource Limiting
Switch, which can be set on the NodeB LMT. See Table 2.3.
If some UEs GBR cannot be satisfied in one Scheduling Algorithm Period, the
Resource Limiting Switch is set to OPEN, and the Scheduling Method is set to
EPF, the resource limiting function will be triggered in the next Scheduling Algorithm
Period. Otherwise, the resource limiting function is turned off. The resource limiting
ratio is set according to the corresponding GBR, which is similar to the transmission
code power limiting of DCH. For parameters values, refer to Table 2.2.

26
Chapter 14 HSDPA
Table 2.3 Resource Limiting Switch

Parameter Name
Parameter ID
GUI Range
Resource Limiting Switch

RSCLMSW
OPEN, CLOSE
None
Default Value
OPEN
Optional/Mandatory
MML Command
Mandatory
SET MACHSPARA
Description:
Switch for resource limiting.

For the values of the parameter, refer to Table 1.1.
Table 2.4 Resource Limiting Ratio for SPI

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Resource limiting ratio for SPI

SPIRSCRATIO
1100
Percent
Refer to Table 2.2.
Mandatory
SET MACHSSPIPARA
Description:
Resource limiting ratio for SPIs.

27
Chapter 14 HSDPA
This parameter is valid only when Resource Limiting Switch is set to OPEN and
when Scheduling Method is set to EPF.
For the values of Scheduling Method, refer to Table 1.1.
For the values of Resource Limiting Switch, refer to Table 2.3.
For the streaming service, the RNC informs the UE of the GBR through Iub signaling.
For BE services, the guaranteed bit rate can be set on the basis of SPI on the NodeB
LMT. The BE GBR configured by the NodeB LMT and the RNC LMT should be
consistent for the same SPI.
Table 2.5 GBR for SPI
Parameter Name
GBR for SPI
Parameter ID
SPIGBR
GUI Range
016383
Kbps
Default Value
Refer to Table 2.2.
Optional/Mandatory
Mandatory
MML Command
SET MACHSSPIPARA
Description:
Guaranteed bit rate for SPI

For the values of Scheduling Method, refer to Table 1.1.
Scheduling based on time division and code division

Any scheduling algorithm of Huawei can be based on time division and code
division, as shown in Figure 1.3.

28
Chapter 14 HSDPA
All
channelization
codes available
for HSDPA
Channelization
code
Time
UE1 data
UE2 data
UE3 data
Figure 1.3 HSDPA sharing mechanism

Table 3.1 describes of resource allocation for six frames in the above example.
Table 3.1 HSDPA scheduling sample
Subframe
First
Codes Allocation
According to the sequence based on the scheduling algorithm, the
system allocates all the five channel codes to UE1.
Second

system allocates two channel codes to UE2 and three to UE3.
Third
UE2 is allocated with two codes and UE3 is allocated with three
codes.
Fourth

system allocates all the five channel codes to UE1.
By analogy
HSDPA basic scheduling algorithms
Table 3.2 HSDPA basic scheduling algorithms

Algorithm
Max C/I
Description
Allocates resources to the UE with the best channel
conditions at TTIs, maximizing the cell handling capacity.
Round Robin
Based on equity principle and ensures that every UE has

the same opportunity to be scheduled.

29
Chapter 14 HSDPA
Algorithm
Description
Proportional Fair (PF)
Gives attention to both allocation equity and efficiency of

resource usage.
Enhanced PF
Ensures the QoS of the streaming service and provides

the lowest rate for the BE service.
VI. HSDPA Flow Control
Purpose of the HSDPA flow control

-
Lower service delay: When the opportunity of scheduling arrives, the data is
already in the MAC-hs queue rather than being buffered by the RNC.
Smaller buffer size of the MAC-hs queue: If there are too much data saved
in the MAC-hs, the data transmission at the RLC layer may fail and packets
may be lost in the original cell during a handover.
Less UL flow control signaling
Principles for the HSDPA flow control algorithm

The HSDPA flow control is implemented through the capacity request and
allocation processes on the lub interface.
-
Capacity request on the Iub interface
The RNC sends a CAPACITY REQUEST control frame to the NodeB at the Iub,
as shown in Figure 1.1.
NodeB
SRNC
CAPACITY REQUEST
Figure 1.1 Capacity request at the Iub interface

The structure of capacity request frame is shown in Figure 1.2. The frame includes
the queue priority and the data buffer size in the RNC RLC layer.

30
Chapter 14 HSDPA
bit7
bit0
Spare bits 7-4
Number
of Octets
1
Cm CH-PI
User Buffer Size

User Buffer Size(cont)
Spare Extension
0-32
Payload
Figure 1.2 Structure of capacity request frame

-
Capacity allocation on the Iub interface

The NodeB preliminarily decides how much bandwidth on the Iub interface
shall be allocated to each UE according to the status of the MAC-hs queue
and rate on the Uu interface. This process is called the Early Allocation (EA)
of traffic. That is:
When there is not enough data in the queue, a large bandwidth is

allocated.
When there is enough data in the queue, a bandwidth that is close to

the rate on the Uu interface is allocated.
When there is too much data in the queue, a small bandwidth or no

bandwidth is allocated.
The total of the traffic that is allocated to each queue indicates that the Iub
interface bandwidth available for HSDPA is overused or is not used fully.
Therefore the EA of the traffic needs to be adjusted. This process is called the
shaping of the traffic.
The shaping of the traffic is completed by comparing the total of the allocated
traffic and the bandwidth on the Iub interface available for HSDPA. The GBR
service queue has the priority to emphasize the differentiated service and
ensure the equity at the same time.
After the EA and the shaping of the traffic, the NodeB sends a CAPACITY
ALLOCATION message to the RNC, as shown in Figure 1.3.

31
Chapter 14 HSDPA
NodeB
SRNC
CAPACITY ALLOCATION
Figure 1.3 Capacity allocation procedure at the Iub interface
Note:
The NodeB can also initiate capacity allocation to the RNC according to the buffer
size of the queue and the bandwidth available at the Iub interface.
The structure of the capacity allocation frame is shown as Figure 1.4.

bit7
bit0
Spare bits 7-4
Number
of Octets
1
Cm CH-PI
Maximum MAC-d PDU Length

Maximum MAC-d
PDU Length(cont)
HS-DSCH
Credits
Payload
HS-DSCH Credits(cont)
HS-DSCH Interval
HS-DSCH Repetition Period
Spare Extension
Figure 1.4 Structure of the capacity allocation frame

In Figure 1.4:
CmCH-PI: the queue with priority
HS-DSCH Interval: length of the cycle
HS-DSCH Credits: the number of data frames

32
Chapter 14 HSDPA
Maximum MAC-d PDU Length: the greatest PDU size
HS-DSCH Repetition Period: how many times at most the HS-DSCH Interval
can repeat
14.5.7 HSDPA Power Allocation

Note:
The power resources in this section refer to the power available in a cell. For
example, the HSDPA power refers to the maximum transmit power that can be used
by HS-SCCH and HS-PDSCH in a cell.
The actual power of DPCH is adjusted through the inner and outer loop power
control algorithm.
The actual power of the HSDPA channel is allocated dynamically among users
through the NodeB scheduling algorithm.
I. Introduction to Cell Total Power Resources

The cell total transmit power is the constant resources. The DL power consists of the
following three parts:
Power of the HSDPA DL physical channel (HS-SCCH and HS-PDSCH)
Common channel power
DPCH power
Among the three parts, common channel power is reserved and the maximum
available power of HSDPA DL physical channel can be set on the RNC LMT..

33
Chapter 14 HSDPA
Table 1.1 HS-PDSCH And HS-SCCH Power

Parameter Name
Parameter ID
GUI Range
HS-PDSCH And HS-SCCH Power

HSDPAPOWER
0500
0 dBm50 dBm
Unit: 0.1 dbm
Default Value
Optional/Mandatory
MML Command
380 (38 dBm)

Mandatory
ADD CELLHSDPA
Description:
This parameter sets the maximum available power for HS-PDSCH and HS-SCCH.
II. HSDPA Dynamic Power Resources Allocation

Except reserving for the common channels, the rest power resources of the cell are
allocated dynamically between the DPCH and HSDPA DL physical channels if the
value of the HS-PDSCH And HS-SCCH Power is equal to the maximum transmission
power of the cell. Moreover, the DPCH has higher priority to use the rest power
resources.
Full usage of power
Total Power
Power for HSDPA
Power for DPCH

Power for CCH
Flexible scheme
Time
Figure 1.1 Dynamic Power Allocation

As shown in Figure 1.1, the NodeB detects the R99 power load every 2ms to
determine the available power for HSDPA. In this way, the cell load is more stable.

34
Chapter 14 HSDPA
To obtain the available power for HSDPA, a power margin must be set aside to
handle power increase caused by R99 power control in each 2ms. The Power
Margin parameter can be set on the NodeB LMT.
Table 1.1 Power Margin
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Power Margin
PWRMGN
0100
Percent
10
Mandatory
SET MACHSPARA
Description:
Power margin for R99 power control in one TTI
14.5.8 HSDPA Codes Allocation

Note:
This section describes the allocation of cell DL codes.
The codes described in this section are the available channel codes. For example,
the HS-PDSCH codes are the maximum channel codes the HS-PDSCH can use.
The HSDPA enables the HSDPA UEs to share the channel codes dynamically as
scheduled by the NodeB.
I. Introduction to Cell Code Resources

The channel codes are constant resources consisting of the following three parts:
HS-PDSCH
Common channels and HS-SCCH
DPCH
The resources are reserved for the common channels and the HS-SCCH. The
parameter of the codes reserved for the HS-SCCH can be configured on the RNC
LMT. Table 1.1 describes the Code Number for HS-SCCH parameter.

35
Chapter 14 HSDPA
Table 1.1 Code Number for HS-SCCH

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Code Number for HS-SCCH

HSSCCHCODENUM
115
1Code15Codes
4
Mandatory
ADD CELLHSDPA
Description:
This parameter sets the number of HS-SCCH codes available in a cell.
Note:
The value of Code Number for HS-SCCH is determined by the service model and
the traffic model of the corresponding cell.
II. Introduction to the HS-PDSCH Codes Allocation

The codes of the HS-PDSCH physical channel can be allocated in two ways:
Static
RNC controlled dynamic
The code allocation method of HS-PDSCH is controlled by the RNC parameter

Allocate Code Mode which can be set on RNC LMT, see Table 1.1.

36
Chapter 14 HSDPA
Table 1.1 Allocate Code Mode

Parameter Name
Allocate Code Mode
Parameter ID
ALLOCCODEMODE
GUI Range
Manual, Automatic.
Static Allocation,
RNC-Controlled
Dynamic
Allocation.
Default Value
Optional/Mandatory
MML Command
Manual
Mandatory
ADD CELLHSDPA
Description:
This parameter is used to choose the mode of allocating HS-PDSCH codes. There
are two modes: Manual and Automatic.
The following describes the two kinds of allocation.
III. Static Allocation

In static allocation, the RNC reserves some codes for the HS-PDSCH. The DPCH
and other common channels use the rest. See Figure 1.1.
Code reserved for
common channel and
HS-SCCH
Codes available
for DPCH
Codes reserved for

HS-PDSCH
SF=16
Figure 1.1 Static codes allocation

The parameter of the codes reserved for the HS-PDSCH can be configured on the
RNC LMT. Table 1.1 describes the Code Number for HS-PDSCH parameter.

37
Chapter 14 HSDPA
Table 1.1 Code Number for HS-PDSCH

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Code Number for HS-PDSCH

HSPDSCHCODENUM
115
1Code15Codes
5
Mandatory
ADD CELLHSDPA
Description:
This parameter sets the number of HS-PDSCH codes available in a cell.
Note:
The value of Code Number for HS-PDSCH is determined by the service model and
the traffic model of the corresponding cell.
This parameter is valid only when Allocate Code Mode is set to Manual.
IV. RNC-Controlled Dynamic Allocation

1)
Introduction
In the RNC-controlled dynamic allocation, the RNC adjusts the reserved HS-PDSCH
codes according to the real-time usage status of the codes.
Configure the maximum and minimum numbers of codes available for HS-PDSCH on
the RNC LMT. The codes between the two parameters are called shared codes. See
Figure 3.1.

38
Chapter 14 HSDPA
Table 1.1 Code Max Number for HS-PDSCH

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Code Max Number for HS-PDSCH

HSPDSCHMAXCODENUM
115
1 Code 15 Codes
10
Mandatory
ADD CELLHSDPA
Description:
This parameter sets the maximum number of HS-PDSCH codes available in a cell.
This parameter is valid only when Allocate Code Mode is set to Automatic.
Table 1.2 Code Min Number for HS-PDSCH

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Code Min Number for HS-PDSCH

HSPDSCHMINCODENUM
115
1 Code 15 Codes
5
Mandatory
ADD CELLHSDPA
Description:
This parameter sets the minimum number of HS-PDSCH codes available in a cell.

39
Chapter 14 HSDPA
Code reserved for

common channel and
HS-SCCH
Shared codes
SF=16
Min number
of codes
Max number
of codes
Codes available for DPCH
Codes reserved for HS- PDSCH
Figure 1.2 Shared codes

The RNC periodically monitors how the code resource is used and decides to extend
or reduce the codes reserved for the HS-PDSCH.
2)
Extending the codes reserved for the HS-PDSCH
The RNC adds one of shared codes to the codes reserved for the HS-PDSCH if the
following cases are fulfilled:
If in cell's code tree there is at least one code can be reserved and this code's
SF is equal to or less than the Reserved SF threshold, NodeB will try to
increase HS-PDSCH code number.
Among shared codes, the code which neighbors to the reserved codes for the
HS-PDSCH is idle, which can be attained through reshuffling the cell code
resource.
See Figure 2.1 and Table 1.1.

Code reserved for
common channel
and HS-SCCH
Shared
codes
SF=16
RNC extends the codes
reserved for HS-PDSCH
Figure 2.1 Extending the codes reserved for HS-PDSCH
Note:
In Figure 2.1, the solid dots represent the occupied codes and the circles represent
the idle codes.

40
Chapter 14 HSDPA
Table 1.1 Reserved SF threshold

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Reserved SF threshold
REVSFTHD
SF8, SF16, SF32, SF64, SF128.
8, 16, 32, 64, 128
32
Mandatory
ADD CELLHSDPA
Description:
This parameter is used to decide whether to increase or decrease the HS-PDSCH
code number between the minimum number and maximum number. If in cell's
code tree there is at least one code can be reserved and this code's SF is equal to
or less than this parameter, which aims to increase HS-PDSCH code number. If
not, try to decrease HS-PDSCH code number.
3)
Reducing the codes reserved for HS-PDSCH
The RNC releases the minimum one of shared codes reserved for the HS-PDSCH to
the DPCH when the minimum spread factor of the free spread codes is larger than
the Reserved SF threshold. See Figure 3.1.
Code reserved for
common channel
and HS-SCCH
Shared
codes
SF=16
RNC reduces the codes

reserved for HS-PDSCH
Figure 3.1 Reducing the codes reserved for HS-PDSCH

41
Chapter 14 HSDPA
Note:
In Figure 3.1, the solid dots represent the occupied codes and the circles represent
the idle codes.
14.6 HSDPA and the Other RAN Features

14.6.1 Overview
This chapter describes how the HSDPA feature affects the following related
algorithms:
HSDPA Cell Load Control
HSDPA Power Control
HSDPA Channel Switch
HSDPA Mobility Management
HSDPA Direct Retry
14.6.2 HSDPA Cell Load Control

Note:
For details about the load control, see Chapter 11 "Load Control." This section gives a
brief introduction of the HSDPA cell load control.
The admission control of the HSDPA cell includes:
The admission decision based on the power resources
The admission decision based on the Iub interface resources
The admission decision based on the number of UEs
The UE can be accessed in the HSDPA cell only when all the three admission
decisions are approved.
14.6.3 HSDPA Power Control

Note:
This chapter only describes the power control of the new channels HSDPA
introduces. See Chapter 10 Power Control for the power control of the associated
DPCH.

42
Chapter 14 HSDPA
I. Overview
HSDPA introduces three new channels:
UL HS-DPCCH
DL HS-PDSCH
DL HS-SCCH
The HSDPA power control just refers to the power control of these three channels.
II. HS-DPCCH Power Control

1)
Power Offset of ACK, NACK and CQI (NonSHO & SHO)
There is no separate power control for HS-DPCCH but setting several power offsets
between HS-DPCCH and UL associated DPCCH. When ACK/NACK and CQI carried
on the HS-DPCCH, power offsets, that are ACK, NACK, CQI, are respectively set for
different part of one HS-DPCCH TTI. See 14.5.8 IVFigure 3.1.
Power
ACK / NACK
ACK / NACK
CQI
CQI
Time
Power
Uplink DPCCH
Time
Figure 1.1 HS-DPCCH Power Offsets

The transmitting power of HS-DPCCH is:
PHS DPCCH PUL DPCCH 10
HS DPCCH
10
14-3
Where, HS DPCCH , as for the first slot of one TTI, means ACK when UE replies
ACK, NACK when UE replies NACK., as for the second and third slots of one TTI,
means CQI. PUL DPCCH is the transmitting power of associated UL DPCCH.
In soft handover area, the UL combining gain reduces the necessary transmission
power of UL DPCCH. While HS-DPCCH does not has the UL combining gain, to

43
Chapter 14 HSDPA
maintain the receiving quality of the HS-DPCCH, higher power offset is needed. Thus,
when UE enters or leaves the soft handover area, the power offset for ACK/NACK
and CQI may have a change correspondingly.
The following parameters just decide the values of ACK, NACK, and CQI in NonSHO
and SHO status.
Table 1.1 ACK poweroffset
Parameter Name
Parameter ID
ACK poweroffset
ACKPO1,
ACKPO2,
ACKPO3
Note:
ACKPO1 is for such UEs whose Minimum inter-TTI
interval equals one, that is, such UEs can feedback
one ACK or NACK each TTI.
interval equals two, that is, such UEs can feed back
one ACK or NACK each at least two TTIs, so in the
two TTIs, UEs can repeat the same ACK or NACK.
interval equals three, that is, such UEs can feed back
one ACK or NACK each at least three TTIs, so in the
three TTI, UEs can repeat the same ACK or NACK.
GUI Range
PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15,

PO_15/15, PO_19/15, PO_24/15, PO_30/15,
5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,

30/15,
Default Value
Optional/Mandatory
MML Command
PO_24/15(24/15), PO_12/15(12/15), PO_9/15(9/15)

Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the power offset of ACK(ACK) comparing to uplink DPCCH
power in non-soft handover status.

44
Chapter 14 HSDPA
Table 1.2 ACK poweroffset multi-RLS

Parameter Name
Parameter ID
ACK poweroffset multi-RLS

ACKPO1FORSHO,
ACKPO2FORSHO,
ACKPO3FORSHO
Note:
ACKPO1FORSHO is for such UEs whose Minimum
inter-TTI interval equals one, that is, such UEs can
feedback one ACK or NACK each TTI.
inter-TTI interval equals two, that is, such UEs can
feedback one ACK or NACK each at least two TTIs, so
in the two TTIs, UEs can repeat the same ACK or
NACK.
inter-TTI interval equals three, that is, such UEs can
feedback one ACK or NACK each at least three TTIs,
so in the three TTI, UEs can repeat the same ACK or
NACK.
GUI Range
PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15,

PO_15/15, PO_19/15, PO_24/15, PO_30/15,
5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,

30/15,
Default Value
PO_24/15(24/15), PO_24/15(24/15), PO_24/15(24/15)
Optional/Mandatory
MML Command
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the power offset of ACK(ACK) comparing to uplink DPCCH
power in soft handover status.

45
Chapter 14 HSDPA
Table 1.3 NACK poweroffset

Parameter Name
Parameter ID
NACK poweroffset
NACKPO1,
NACKPO2,
NACKPO3
Note:
NACKPO1 is for such UEs whose Minimum inter-TTI
interval equals one, that is, such UEs can feedback
one ACK or NACK each TTI.
interval equals two, that is, such UEs can feedback one
ACK or NACK each at least two TTsI, so in the two
TTIs, UEs can repeat the same ACK or NACK.
interval equals three, that is, such UEs can feedback
one ACK or NACK each at least three TTIs, so in the
three TTI, UEs can repeat the same ACK or NACK.
GUI Range
PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15,

PO_15/15, PO_19/15, PO_24/15, PO_30/15,
5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,

30/15,
Default Value
PO_24/15(24/15), PO_12/15(12/15), PO_9/15(9/15)
Optional/Mandatory
MML Command
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the power offset of NACK(NACK) comparing to uplink DPCCH
power in non-soft handover status..

46
Chapter 14 HSDPA
Table 1.4 NACK poweroffset multi-RLS

Parameter Name
Parameter ID
NACK poweroffset multi-RLS

NACKPO1FORSHO,
NACKPO2FORSHO,
NACKPO3FORSHO
Note:
NACKPO1FORSHO is for such UEs whose Minimum
feedback one ACK or NACK each at least two TTIs, so
in the two TTIs, UEs can repeat the same ACK or
NACK.
NACK.
GUI Range
PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15,

PO_15/15, PO_19/15, PO_24/15, PO_30/15,
5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,

30/15,
Default Value
PO_24/15(24/15), PO_24/15(24/15), PO_24/15(24/15)
Optional/Mandatory
MML Command
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the power offset of NACK(NACK) comparing to uplink DPCCH

47
Chapter 14 HSDPA
Table 1.5 CQI Power Offset

Parameter Name
Parameter ID
CQI Power Offset

CQIPO
Note:
CQIPO is for all UEs without regard to Minimum interTTI interval.
GUI Range
PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15,

PO_15/15, PO_19/15, PO_24/15, PO_30/15,
5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,

30/15,
Default Value
Optional/Mandatory
MML Command
PO_24/15(24/15)
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the power offset of CQI(CQI) comparing to uplink DPCCH
power in non-soft handover status.

48
Chapter 14 HSDPA
Table 1.6 CQI Power Offset multi-RLS

Parameter Name
Parameter ID
CQI Power Offset multi-RLS

CQIPOFORSHO
Note:
CQIPOFORSHO is for all UEs without regard to
Minimum inter-TTI interval.
GUI Range
PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15,

PO_15/15, PO_19/15, PO_24/15, PO_30/15,
5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,

30/15,
Default Value
Optional/Mandatory
MML Command
PO_24/15(24/15)
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the power offset of CQI(CQI) comparing to uplink DPCCH
2)
This parameter sets the referenced UL DPCCH Initial SIR target. Different associated
UL DPCH may have different initial SIR target. When the referenced UL DPCCH
Initial SIR target set in this LMT command is different from the SIR Init Target Value
for UL DPCCH set in the LMT command ADD TYPRABOLPC or ADD TYPSRBOLPC,
the power offset for ACK, NACK and CQI will be adjusted. The adjusted method as
following, if the SIR Init Target Value set in the LMT command ADD TYPRABOLPC or
ADD TYPSRBOLPC is larger 1dB than the SIR Init Target Value set in this command,
then the power offset for ACK, NACK and CQI may be decreased 1dB.

49
Chapter 14 HSDPA
Table 1.1 SIR Init Target Value

Parameter Name
Parameter ID
GUI Range

SIRTARGET
0255

Default Value
Optional/Mandatory
MML Command
-8.2dB17.3dB
Unit: 0.1dB
112(3dB)
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the referenced initial SIR of UL DPCCH which HS-DPCCH
configures power offsets according to.
3)
Repetition Factor
Repetition factors of ACK/NACK and CQI are signalled to the UE and the Node B
from higher layers.
UE shall not attempt to receive nor decode transport blocks from the HS-PDSCH in
HS-DSCH sub-frames corresponding to HS-DPCCH sub-frames in which the
ACK/NACK information transmission is repeated.

50
Chapter 14 HSDPA
Table 1.1 ACK-NACK Repetition Factor

Parameter Name
Parameter ID
ACK-NACK Repetition Factor

ACKNACKREF1, ACKNACKREF2, ACKNACKREF3,
Note:
ACKNACKREF1 is for such UEs whose Minimum
feedback one ACK or NACK each at least two TTIs,
so in the two TTIs, UEs can repeat the same ACK or
NACK.
NACK.
GUI Range
14
Times
Default Value
Optional/Mandatory
MML Command
1, 2, 3
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the transmission times of single ACK/NACK information when
UE is in NonSHO.

51
Chapter 14 HSDPA
Table 1.2 ACK-NACK Repetition Factor multi-RLS

Parameter Name
Parameter ID
ACK-NACK Repetition Factor multi-RLS

ACKNACKREFFORSHO
Note:
ACKNACKREFFORSHO is for all UEs without regard
to Minimum inter-TTI interval.
GUI Range
14
Times
Default Value
Optional/Mandatory
MML Command
1
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the transmission times of single ACK/NACK information when
UE is in SHO.
Table 1.3 CQI Repetition Factor

Parameter Name
Parameter ID
CQI Repetition Factor

CQIREF
Note:
CQIREF is for all UEs without regard to Minimum
inter-TTI interval.
GUI Range
14
Times
Default Value
Optional/Mandatory
MML Command
1
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the transmission times of single CQI information when UE is in
NonSHO.
52
Chapter 14 HSDPA
Table 1.4 CQI Repetition Factor multi-RLS

Parameter Name
Parameter ID
CQI Repetition Factor multi-RLS

CQIREFFORSHO
Note:
CQIREFFORSHO is for all UEs without regard to
Minimum inter-TTI interval.
GUI Range
14
Times
Default Value
Optional/Mandatory
MML Command
1
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the transmission times of single CQI information when UE is in
SHO.
4)
CQI Feedback Cycle
CQI Feedback Cycle is signalled to the UE and the Node B from higher layers.

53
Chapter 14 HSDPA
Table 1.1 CQI Feedback Cycle k

Parameter Name
Parameter ID
GUI Range
CQI Feedback Cycle k

CQIFBCK
D0, D2, D4, D8, D10, D20, D40, D80, D160
0ms, 2ms, 4ms, 8ms,10ms,20ms, 40ms, 80ms,

160ms
Default Value
Optional/Mandatory
MML Command
D2(2ms)
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the CQI feedback cycle during which UE sends CQIREF times
CQI value when UE is in NonSHO. For D0(0ms), the UE shall not transmit the CQI
value.
Table 1.2 CQI Feedback Cycle k multi-RLS

Parameter Name
Parameter ID
GUI Range
CQI Feedback Cycle k multi-RLS

CQIFBCKFORSHO
D0, D2, D4, D8, D10, D20, D40, D80, D160
0ms, 2ms, 4ms, 8ms,10ms,20ms, 40ms, 80ms,

160ms
Default Value
Optional/Mandatory
MML Command
D2(2ms)
Mandatory
ADD CELLHSDPCCH
Description:
This parameter sets the CQI feedback cycle during which UE sends
CQIREFFORSHO times CQI value when UE is in SHO. For D0(0ms), the UE shall
not transmit the CQI value.

54
Chapter 14 HSDPA
UE does not support the case of CQIFBCK<CQIREF or CQIFBCKFORSHO<

CQIREFSFORSHO.
III. HS-SCCH and HS-PDSCH Power Control

The HS-SCCH and HS-PDSCH power control involves two steps:
1)
The HSDPA resource distribution mode (static or dynamic) determines the total
transmission power of the DL HSDPA channel. See 14.5.7HSDPA Power
Allocation" for details.
2)
The NodeB distributes the available DL HSDPA power to the HS-SCCH and the
HS-PDSCH based on the scheduling algorithm.
The power control of the HS-SCCH is of three types:
The transmitting power is fixed.
The power is dynamically controlled according to the CQI.
There is an offset between the HS-SCCH and the downlink associated DPCH.
The HS-SCCH Power Control Method parameter can be set on the NodeB LMT.
Table 1.1 HS-SCCH Power Control Method
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
HS-SCCH Power Control Method

SCCHPWRCM
FIXED, CQI, DCH
None
CQI
Mandatory
SET MACHSPARA
Description:
This parameter sets the power control method for HS-SCCH.
If the HS-SCCH Power Control Method parameter is set to FIXED, the power of HSSCCH must be set on the NodeB LMT. The HS-SCCH Power parameter is an offset
to the PCPICH power of a cell. Table 1.2 describes the HS-SCCH Power parameter.

55
Chapter 14 HSDPA
Table 1.2 HS-SCCH Power

Parameter Name
Parameter ID
GUI Range
HS-SCCH Power
SCCHPWR
080
From -10dB to 10dB Step:0.25dB
Default Value
28 (-3dB)
Optional/Mandatory
Mandatory
MML Command
SET MACHSPARA
Description:
When the HS-SCCH Power Control Method is set to FIXED, the parameter sets
the fixed transmit power of HS-SCCH.

This parameter is valid only when the HS-SCCH Power Control Method is set to
FIXED.
If the HS-SCCH Power Control Method parameter is set to CQI, the NodeB adjusts
the transmitting power of HS-SCCH, depending on the following information:
CQI reported by UE
DTX number received by NodeB
Target Frame Error Rate (FER) of HS-SCCH
The HS-SCCH FER parameter can be set on the NodeB LMT.

56
Chapter 14 HSDPA
Table 1.3 HS-SCCH FER

Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
HS-SCCH FER
SCCHFER
1999
Permillage
10(1%)
Mandatory
SET MACHSPARA
Description:
This parameter sets the target FER of the HS-SCCH. If the HS-SCCH FER is
larger than the HS-SCCH FER target, the HS-SCCH power will be increased.
Otherwise, the HS-SCCH power will be decreased.

This parameter is valid only when the HS-SCCH Power Control Method
parameter is set to CQI.
If the HS-SCCH Power Control Method parameter is set to DCH, the power offset
between HS-SCCH and DL associated DPCCH must be set on the RNC LMT.
In soft handover area, the DL combining gain reduces the necessary transmission
power of DL DPCCH. While HS-SCCH does not has the DL combining gain, to
maintain the receiving quality of the HS-SCCH, higher power offset is needed. Thus,
when UE enters or leaves the soft handover area, the power offset may have a
change correspondingly.

57
Chapter 14 HSDPA
Table 1.4 HS-SCCH SF4 Power Offset

Parameter Name
Parameter ID

HSSCCHPOFORSF4,
HSSCCHPOFORSF4SHO
Note:
HSSCCHPOFORSF4 is for NonSHO UE;
HSSCCHPOFORSF4SHO is for SHO UE.
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
-32dB31.75dB Step:0.25dB
-27(-6.75dB), -27(-6.75dB)
Mandatory
SET HSSCCH
Description:
This parameter sets the power offset of the HS-SCCH when the SF of Downlink
associated DPCH equals 4.

parameter is set to DCH.

58
Chapter 14 HSDPA

Parameter Name
Parameter ID

HSSCCHPOFORSF8,
HSSCCHPOFORSF8SHO
Note:
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
-15(-3.75dB), -15(-3.75dB)
Mandatory
SET HSSCCH
Description:
This parameter sets the power offset of the HS-SCCH when the SF of downlink


59
Chapter 14 HSDPA

Parameter Name
Parameter ID

HSSCCHPOFORSF16,
HSSCCHPOFORSF16SHO
Note:
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
-3(-0.75dB), -3(-0.75dB)
Mandatory
SET HSSCCH
Description:


60
Chapter 14 HSDPA

Parameter Name
Parameter ID

HSSCCHPOFORSF32,
HSSCCHPOFORSF32SHO
Note:
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
9(2.25dB), 9(2.25dB)
Mandatory
SET HSSCCH
Description:


61
Chapter 14 HSDPA

Parameter Name
Parameter ID

HSSCCHPOFORSF64,
HSSCCHPOFORSF64SHO
Note:
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
21(5.25dB), 21(5.25dB)
Mandatory
SET HSSCCH
Description:


62
Chapter 14 HSDPA

Parameter Name
Parameter ID

HSSCCHPOFORSF128,
HSSCCHPOFORSF128SHO
Note:
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
33(8.25dB), 33(8.25dB)
Mandatory
SET HSSCCH
Description:


63
Chapter 14 HSDPA

Parameter Name
Parameter ID

HSSCCHPOFORSF256,
HSSCCHPOFORSF256SHO
Note:
GUI Range
Default Value
Optional/Mandatory
MML Command
-128127
45(11.25dB), 45(11.25dB)
Mandatory
SET HSSCCH
Description:

14.6.4 HSDPA Channel Switch

I. HSDPA State Transition and Channel Switch
With introducing HSDPA technology, the UE has one more RRC state CELL_DCH
(with HS-DSCH). Figure 1.1 shows the RRC state transition.

64
Chapter 14 HSDPA
CELL_DCH
CELL_PCH
CELL_FACH
CELL_DCH
(with HS-DSCH)
Figure 1.1 Different status of the RRC of the UE

See Table 1.1 30 for the influences of HSDPA handover has on the types of the
channel.
Table 1.1 Channel type transition after introducing HSDPA
UE State Transition
Channel Switching
CELL_DCH (with HS-DSCH) CELL_DCH
HS-DSCH DCH
CELL_DCH (with HS-DSCH) CELL_FACH
HS-DSCH FACH
II. Channel Switching between HS-DSCH and FACH

Since the HSDPA UE occupies the DPCH, the UE will switch its state from the HSDSCH to the FACH to reduce occupation of the DPCH when the following conditions
are met.
The HS-DSCH carries the BE service or the PS streaming service for the UE.
There is no data flow of any of the services for a certain length of time, which is
set to BE HS-DSCH to FACH transition timer for BE service or Realtime Traff
DCH to FACH transition timer for realtime service.
On the other hand, when the data flow gets more active, for example, when the RNC
receives a 4a event measuring report, the UE is switched from the FACH to the HSDSCH.
Further descriptions about Channel Switching between HS-DSCH and FACH refer to
DCCC chapter.

65
Chapter 14 HSDPA
Parameter Name
BE HS-DSCH to FACH transition timer
Parameter ID
BeH2FStateTransTimer
GUI Range
165535
165535 (s)
Default Value
180
Optional/Mandatory
Optional
MML Command
SET UESTATETRANS
Description:
This parameter is used to detect the stability of a UE in low activity state in
CELL_DCH (with HS-DSCH) state.
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Realtime Traff DCH to FACH transition timer

RtDH2FStateTransTimer
165535
165535 (s)
180
Optional
SET UESTATETRANS
Description:
This timer is used in detecting whether a real-time service UE in CELL_DCH state
is in stable low activity state.
III. Channel Switching between HS-DSCH and DCH

The channel switching between HS-DSCH and DCH includes the switching from HSDSCH to DCH and the switching from DCH to HS-DSCH. The switching from DCH to
HS-DSCH can be triggered by mobility management, the traffic volume or the timer.
The switching from HS-DSCH to DCH can only be triggered by mobility management.
Triggered by mobility management
Refer to section 14.6.5"HSDPA Mobility Management" and 14.6.6"HSDPA Direct

Retry".
66
Chapter 14 HSDPA
Triggered by traffic volume
When the activity of the UE that performs data services increases and the RNC
receives the report of the 4a event, the channel type of this UE will switch from DCH
to HS-DSCH.
Further descriptions refer to DCCC chapter.
Triggered by timer
When a current service of the UE is suitable to be carried on HSDPA and the UE

supports HSDPA but the service is actually mapped onto the DCH (for reasons such
as the UE is rejected to access a HSDPA cell), a timer is used for periodical attempts
to map the service onto the HS-DSCH, first attempting to mapping to HS-DSCH of the
current cell, if failed, then attempting to mapping to HS-DSCH of the inter-frequency
cell with the same coverage. This timer length is set to H Retry TimerLength.
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
H Retry TimerLength
HRETRYTIMERLEN
0, 1000180000
0, 1000180000 (ms)
5000
Optional
SET COIFTIMER
Description:
Length of retry timer for periodical attempts to map the service onto the HS-DSCH.
The timer is started periodically, and there is no limit for starting number. When the
timer length is set to zero, the retry function is off.
14.6.5 HSDPA Mobility Management

I. Overview
A UE may have two connections with the network after introducing HSDPA. See Table
1.1.

67
Chapter 14 HSDPA
Table 1.1 Connections between the UE and network

Connection
Handover
HSDPA
A UE can keep only one HSDPA connection with the network at a
connection
time. The HSDPA handover includes:
HSDPA cell HSDPA cell
HSDPA cell R99 cell
HSDPA cell GSM/GPRS cell
DPCH
Similar to the R99 system handover, the DPCH handover includes
connection
soft handover, hard handover and inter-RAT handover.
The similarity of the HSDPA handover and DPCH handover lies in that they are based
on the measurement report of the UE and controlled by the network. If the UE has
both the HSDPA and the DPCH connections, the measurement and the handover
decision are made separately.
The following text describes the HSDPA handover, including:
HSDPA cell R99 cell
HSDPA cell HSDPA cell
HSDPA cell GSM/GPRS cell
II. Handover between HSDPA Cell and R99 Cell

Note:
If the activities of the UE are in both the R99 cell and HSDPA cell, the UE will keep
the HSDPA connection until the activities are not in the HSDPA cell.
1)
Scenarios
Table 1.1 lists the four scenarios of handover between the HSDPA cell and R99 cell.

68
Chapter 14 HSDPA
Table 1.1 Scenarios of handover between the HSDPA cell and R99 cell
No.
1
Scenario
Description
The UE moves from an HSDPA
The
cell to a R99 cell.
connection to the DPCH of the R99
The 1d event is triggered and the
cell.
RNC
sets
the
HSDPA
new best cell does not support

HSDPA.
The 1b or 1c event is triggered

and the new best cell does not
support HSDPA.
The UE moves from an HSDPA
The RNC sets the UE on the DPCH
cell to a R99 cell.
of
The 2b event is triggered or
handover.
the
R99
cell
through
hard
periodical measurement reports

by UE.
3
The UE moves from a R99 cell to
If the HS-PDSCH is suitable to carry
an HSDPA cell.
the service of the UE, the RNC
The 1d event is triggered and
switches the service to the HS-
new best cell supports HSDPA.
PDSCH of the HSDPA cell.
The 1b or 1c event is triggered

and the new best cell supports
HSDPA.
The UE moves from a R99 cell to
The RNC sets the UE to the HSDPA
an HSDPA cell.
cell through hard handover.
The 2b event is triggered or
If the HS-PDSCH is suitable to carry
periodical measurement reports
the service of the UE, the RNC
by UE.
switches the service to the HSPDSCH of the HSDPA cell.
The details are described in the following text.

2)
Scenario 1
Figure 2.1 is an example of scenario 1. Suppose the UE is moving from cell 1

(HSDPA) to cell 2 (R99). Cell 1 is the only HSDPA cell in the active set and cell 2 and
cell 1 are intra-frequency neighboring cells.

69
Chapter 14 HSDPA
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
before handover
Cell 2(R99)
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 2.1 Soft handover between the HSDPA and R99 cells (HSDPAR99)
When the UE moves, the 1b event is triggered if the signal quality of cell 1 is poor
enough to be deleted and then the 2A event is triggered. To ensure the continuity of
the service, the HSDPA connection between the UE and cell1 is switched to the
DPCH of cell 2.
3)
Scenario 2

(HSDPA) to cell 2 (R99) that is the inter-frequency neighboring cell of cell 1.
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
before handover
Cell 2(R99)
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 3.1 Hard handover between the HSDPA and R99 cells (HSDPAR99)
When the UE moves, if the UE switches from cell 1 to cell 2 through hard handover,
the services carried by HSDPA in cell 1will be switched to the DPCH of cell 2.

70
Chapter 14 HSDPA
Note:
The HSDPA handover decision is based on the measurement report of the pilot
channels of neighboring cells.
4)
Scenario 3
Figure 4.1 is an example of scenario 3. Suppose the UE is moving from cell 2 (R99)
to cell 1 (HSDPA) that is the intra-frequency neighboring cell of cell 1. The DPCH of
cell 2 carries the BE service or the PS streaming service of the UE.
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
before handover
Cell 2(R99)
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 4.1 Soft handover between the HSDPA and R99 cells (R99HSDPA)
When the UE moves, the 1a event is triggered if the quality of the signals in cell 1 is
good. The UE adds cell 1 to the active set and sets up a DPCH connection to cell 1.
When the cell 1 becomes the best cell and the 1d event is triggered, the service will
be switched from the DPCH to the HS-PDSCH of the cell 1 if it is suitable for the HSPDSCH to carry the BE service.
5)
Scenario 4
Figure 5.1 is an example of scenario 4, which supposes that UE is moving from cell 2
(R99) to cell 1 (HSDPA). Cell 1 is the inter-frequency neighboring cell of cell 2. The
DPCH of cell 2 carries the BE service or the PS streaming service of the UE.

71
Chapter 14 HSDPA
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
before handover
Cell 2(R99)
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 5.1 Hard handover between the HSDPA and R99 cells (R99HSDPA)
When the UE moves, inter-frequency handover is triggered if the quality of the signals
of cell 1 is good and the UE switches from cell 2 to cell 1. For better quality, the BE
service or the PS streaming service will be switched from the DPCH to the HSPDSCH.
Note:
When the UE moves from a R99 cell to an HSDPA cell, the BSC6800 hands over the
UE in the following sequence:
Inter-cell handover (intra-frequency soft handover, hard handover or interfrequency hard handover) for the DPCH UE.
6)
The RNC sets the data service on the HS-PDSCH if suitable.
Protection Timer to Anti-PingPong
To avoid the ping-pong update at the boundary of an HSDPA cell and a R99 cell, a
protection timer is used. After UE handover from an HSDPA cell to a R99 cell
successfully, the protection timer start. Then the RNC would switch UE's service
again to the HS-PDSCH of the HSDPA cell only after this timer expires.
The time length is set to The timer length of D2H handover.

72
Chapter 14 HSDPA
Parameter Name
The timer length of D2H handover
Parameter ID
D2HTIMERLEN
GUI Range
0180
0180 (s)
Default Value
Optional/Mandatory
Optional
MML Command
SET HOCOMM
Description:
Length of D2H penalty timer after the intra-frequency handover. It is a non-periodic
timer that defines the period for D2H penalty after the soft handover and intrafrequency hard handover and helps to avoid ping-pang effect.
III. Handover Between HSDPA Cell and HSDPA Cell

1)
Scenarios
An HSDPA to HSDPA handover may occur only when there are at least two HSDPA
cells in the active set. Table 1.1 lists the common scenarios.
Table 1.1 Scenarios of handover between two HSDPA cells
No.
1
Scenario
The RNC will
When the UE moves and
Update the HSDPA connection of the UE
another cell becomes the cell
to the target HSDPA cell.
of the best signal quality, 1d

event is triggered.
2
When the UE moves, inter-
Hard handover the UE to the target
frequency
HSDPA cell. Set the HSDPA connection in
handover
is
triggered and the target cell is
the HS-PDSCH of the target cell.
the HSDPA cell.

3
When the UE moves, the cell
Update the HSDPA cell. Set the HSDPA
that
connection in the HS-PDSCH of the new
provides
the
HSDPA
service for the UE is deleted,
best cell.
1b or 1c event is triggered and

the new best cell supports
HSDPA.

73
Chapter 14 HSDPA
The details are described in the following sections.

2)
Scenario 1

(HSDPA) to cell 2 (HSDPA) that is the intra-frequency neighboring cell of cell 1.
Cell 1(HSDPA)
Cell 2(HSDPA)
Cell 1(HSDPA)
before handover
Cell 2(HSDPA)
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 2.1 Soft handover between two HSDPA cells (the best cell changes)
When the UE moves and another cell becomes the cell of the best signal quality, 1d
event is triggered. The RNC will switch the HSDPA connection from cell 1 to cell 2.
[Internal] To avoid the ping-pong update at the boundary of the two HSDPA cells, a
protection timer HSDPA Timer is used. The time length is set to HSDPA hysteresis
timer length. The UE can update the HSDPA serving cell again only after this time
expires.

74
Chapter 14 HSDPA
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
HSDPA hysteresis timer length

HSDPATIMERLEN
01024
01024 (s)
0
Optional
SET HOCOMM
Description:
HSDPA handover is triggered by event 1D. To avoid frequently handover from
affecting the system performance, a protection timer HSDPA Timer is used.
After event 1D triggers HSDPA handover, this timer is started. Then, event 1D will
not trigger HSDPA handover any more before expiry of this timer.
The value 0 means this timer is not started; that is, HSDPA handover is trigger
immediately. The value 1024 means HSDPA handover will not be triggered before
the cell bearing the HSDPA service is removed.
3)
Scenario 2

(HSDPA) to cell 2 (HSDPA) that is the inter-frequency neighboring cell of cell 1.
Cell 1(HSDPA)
Cell 2(HSDPA)
Cell 1(HSDPA)
before handover
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 3.1 Hard handover between HSDPA cells

75
Cell 2(HSDPA)
Chapter 14 HSDPA
When the UE moves, inter-frequency is triggered if the quality of cell 2 is good

enough. While the UE is moving, if the signals are good in cell 2, the handover event
is triggered. The UE is handed over from cell 1 to cell 2. Meanwhile, the HSDPA
connection of the UE is set up on the HS-PDSCH.
Note:
The triggers and conditions of hard handover of the HSDPA cell are the same as
those of the R99 cell.
4)
Scenario 3

(HSDPA) to cell 2 (HSDPA) that is the intra-frequency neighboring cell of cell 1.
Cell 1(HSDPA)
Cell 2(HSDPA)
Cell 1(HSDPA)
before handover
Cell 2(HSDPA)
after handover
DPCH connection
HSDPA connection
UE moving direction
Figure 4.1 Soft handover between HSDPA cells (HSDPA service cell is deleted from
active set)
While the UE is moving, the HSDPA cell (cell 1) may be deleted from the active set
due to the poor quality of signals. This triggers the 1b event. The HSDPA connection
is set on the HS-PDSCH of the best HSDPA cell (cell 2) in the active set.
IV. Handover between the HSDPA Cell and GSM/GPRS Cell

1)
Scenarios
The causes of the handover include:
Coverage

76
Chapter 14 HSDPA
The initial UMTS network cannot continuously cover the area. The UE is handed over
to the GSM/GPRS when it is at the boundary of the network or the quality of the
signal is poor.
Services
Fully utilize the network and expand the system capacity by handing over the services
(for example, voice) to the GSM/GPRS network.
2)
Handover procedures
Different handover procedures are taken due to different services.
Real-time services: handover procedure from the UMTS to the GSM/GPRS of

the CS services (The PS services interrupt after handover.)
Non-real-time services: handover procedure from the UMTS to the GSM/GPRS

of the PS services
3)
Handover procedure from the UMTS to the GSM/GRPS of the CS services
The handover procedure from the UMTS to the GSM/GPRS of the CS services is as
shown in Figure 3.1.

77
UE
Chapter 14 HSDPA
NodeB
SRNC
CN
MSC
BSC
1. Relocation
Required
RANAP
RANAP
MAP/E
2. Prepare
Handover
MAP/E
3. Handover
Request
BSSMAP
BSSMAP
4. Handover
Request Ack
BSSMAP
BSSMAP
5. Prepare Handover
Pesponse
MAP/E
MAP/E
6. Relocation
Command
RANAP
RANAP
7. DCCH:Handover
from UTRAN Command
RRC
RRC
8. Handover Detect
BSSMAP
BSSMAP
9. Handover Complete
BSSMAP
BSSMAP
10. Handover
Complete
BSSMAP
BSSMAP
11. Send End

Signal Request
MAP/E
MAP/E
12. Iu Release
Command
RANAP
RANAP
13. Iu Release
Complete
RANAP
RANAP
14. Send End

Signal Response
MAP/E
MAP/E
Figure 3.1 Handover procedure from the UMTS to GSM/GPRS of the CS services
4)
Handover procedure from the UMTS to the GSM/GRPS of PS services
The handover procedure from the UMTS to the GSM/GPRS of the PS services is as
shown in Figure 4.1.

78
Chapter 14 HSDPA
UE
SRNC
CN
1. Cell Change Order from UTRAN

RRC
RRC
2. Iu Release Command
RANAP
RANAP
3. Iu Release Complete
RANAP
RANAP
Figure 4.1 Handover procedure from the UMTS to the GSM/GPRS of the PS services
V. Handover between GSM/GRPS Cell and HSDPA Cell

The scenario and procedure is similar to that from the GSM/GPRS to HSDPA. See
Chapter 9 "Inter-RAT Handover.
14.6.6 HSDPA Direct Retry

The HSDPA direct retry is triggered by the following factors:
HSDPA Request is Initiated in the R99 Cell
Traffic Volume Increases
Timer
Access to the Original HSDPA Cell is Rejected
I. HSDPA Request is Initiated in the R99 Cell

When the R99 cell and the HSDPA cell cover the same physical area and the UE
initiates a data service access request from the R99 cell, the system will assign it to
the HS-PDSCH of the HSDPA cell by direct retry.
II. Traffic Volume Increases

The HSDPA direct retry triggered by the increase of the traffic volume is of two types:
Suppose the R99 cell and the HSDPA cell cover the same physical area. When
the traffic volume of the UE that is in the R99 cell and is in the FACH state
increases, the system reassigns the service to the HS-PDSCH of the HSDPA
cell.
Suppose the R99 cell and the HSDPA cell cover the same physical area. For the
service that shall be set up on the HSDPA channel according to the service
mapping rules but is set up on the DCH of the R99 cell, the system reassigns it
to the HS-DSCH of the HSDPA cell when the traffic volume increases.

79
Chapter 14 HSDPA
III. Timer
Suppose the R99 cell and the HSDPA cell cover the same physical area. For the
service that shall be set up on the HSDPA channel according to the service mapping
rules but is set up on the DCH of the R99 cell, the system reassigns it to the HSDSCH of the HSDPA cell when the timer for the unconformity between the channel
that the service is suitable for and the channel that bears the service expires.
IV. Access to the Original HSDPA Cell is Rejected

The rejection of the access to the original HSDPA cell is of the following types:
The access to the HSDPA cell is rejected when the service is set up.
Suppose two HSDPA cells cover the same physical area. If the UE initiates a
data service request from one of the HSDPA cell but fails to be accessed to the
cell, the system reassigns the service to the HS-DSCH of the other HSDPA that
covers the same physical area through direct retry.
The access to the HSDPA cell is rejected when the channel transition from the
FACH to the HS-DSCH is triggered by the increase of the traffic volume.
Suppose two HSDPA cells cover the same physical area. The traffic volume of
the UE that is in the R5 cell and is in FACH state increases, the system attempts
to reassign the service to the HS-DSCH of the HSDPA cell. If the access to the
HSDPA cell fails, the system reassigns the service to the HS-PDSCH of the
other HSDPA cell that covers the same physical area.
DCH to the HS-DSCH is triggered by the increase of the traffic volume.
Suppose two HSDPA cells cover the same physical area. For the service that
shall be set up on the HSDPA channel according to the service mapping rules
but is set up on the DCH of one HSDPA cell, the system attempts to reassign it
to the HS-DSCH of the HSDPA cell when the traffic volume increases. If the
access to the HSDPA cell fails, the system reassigns the service to the HSDSCH of the other HSDPA cell that covers the same physical area.
DCH to the HS-DSCH is triggered by the timer.
Suppose two HSDPA cell cover the same physical area. For the service that
shall be set up on the HSDPA channel according to the service mapping rules
but is set up on the DCH of a HSDPA cell, the system attempts to reassign it to
the HS-DSCH of the HSDPA cell when the timer for the unconformity between
the channel that the service is suitable for and the channel that bears the service
expires. If the access to the HSDPA cell fails, the system reassigns the service to
the HS-DSCH of the other HSDPA cell that covers the same physical area.

80
Chapter 14 HSDPA
In this way, the HSDPA resources are shared between the inter-frequency R99 and
HSDPA cells and between the HSDPA cells.
Suppose cell b (R99) and cell a (HSDPA) are cells, and the UE stays in cell b.
When the UE initiates a BE service or PS streaming service request from cell b and
the rate of the service meets the requirement for the service to be mapped on the HSDSCH, the RNC triggers the direct retry procedure that assigns the UE accessing cell
and maps the service on the HS-PDSCH.
Cell a(f1,HSDPA)
Cell a(f1,HSDPA)
Cell b(f2, R99)
Cell b(f2, R99)
UE initiates
HSDPA service
request from cell b
After DRD, UE
HSDPA service
are set on cell a
service request
DPCH connection
HSDPA connection
Figure 1.1 Direct retry procedure
14.6.7 Other Features

On the RNC LMT, the HS-PDSCH TX diversity mode parameter can be set to
enable or disable the TX diversity mode of HS-PDSCH.

81
Chapter 14 HSDPA
Table 1.1 HS-PDSCH TX diversity mode

Parameter Name
HS-PDSCH TX diversity mode
Parameter ID
HSPDSCHTXDIVERSITYMODE
GUI Range
NONE, STTD
None
Default Value
None
Optional/Mandatory
MML Command
Optional
ADD CELLSETUP
Description:
This parameter is used to control the HS-PDSCH TX diversity function.
On the RNC LMT, the MAC-hs Reset Algorithm Switch parameter can be set to
enable or disable the reset of UE MAC-hs during the update of HSDPA serving cells.
Table 1.2 MAC-hs Reset Algorithm Switch
Parameter Name
Parameter ID
GUI Range
MAC-hs Reset Algorithm Switch

NBMMACHSRESETALGOSELSWITCH
ALGORITHM_REQUIRED,
ALGORITHM_DEPEND_ON_LCG
None
Default Value
None
Optional/Mandatory
MML Command
Mandatory
MOD CELLALGOSWITCH
Description:
The algorithms with the above values are as follow:
ALGORITHM_REQUIRED: Always reset the MAC-hs no matter whether the

cells in question are in the same NodeB or not.
ALGORITHM_DEPEND_ON_LCG: Reset the MAC-hs only when the cells in

question are in a different local cell group.

82
Chapter 14 HSDPA
14.7 Capabilities
The relative specifications of HSDPA are as follows:
Raise the DL data rate to the maximum of 14.4Mbit/s that is the theoretic
maximum rate on the Uu interface.
Expand the capacity of the macro cells to around 50% and the DL micro cells to
200%300%.
14.8 Implementation
14.8.1 Enabling HSDPA
I. Hardware Installation
The HSDPA algorithm module is integrated in RNC and NodeB. It does not need
extra hardware support.
II. Parameter Configuration of RNC-Oriented HSDPA

After the license is activated, the RNC automatically initializes the values of RNCoriented HSDPA.
These values can be changed upon practical requirements of network planning or
optimization through RNC LMTs.
III. Parameter Configuration of NodeB-Oriented HSDPA

After the license is activated, the NodeB automatically initializes the initial values of
NodeB-oriented HSDPA.
These values can be changed upon practical requirements of network planning or
optimization through NodeB LMTs.
IV. Parameter Configuration of Cell-Oriented HSDPA

To enable the HSDPA service in a cell, configure HSDPA data for the cell on the RNC
LMT and then activate the HSDPA service in the cell.
V. Feature Verification
Execute the LST CELLHSDPA command to list cell HSDPA parameters. If the result
shows that the Cell HSDPA active stats is activated, HSDPA is enabled in the cell.
VI. Examples
//(1)get the License. Download the license to the BAM installation directory\FTP\license through
FTP.

83
Chapter 14 HSDPA
//(2)execute ACT LICENSE command to activate the license. After the license is activated, the RNC
and the NodeB automatically initializes the values of the RNC-oriented and the NodeB-oriented
HSDPA.
ACT LICENSE: FN="Filename";
//(3)execute DSP LICENSE command to check if the RNC is authorized for the HSDPA service.
DSP LICENSE:;
//(4)execute LST CELL command to check if the data of the cell that is to be configured with
HSDPA exists.
LST CELLHSDPA: LstFormat=VERTICAL;
//(5)execute ADD CELLHSDPA command to add parameters of HSDPA to the cell.

ADD
CELLHSDPA:
CELLID=10101,
HSPDSCHCODENUM=5,
HSSCCHCODENUM=4,
HSDPAPOWER=380, HSPDSCHMPOCONSTENUM=2.5DB;
//(6)execute ACT CELLHSDPA command to activate HSDPA in the cell.

ACT CELLHSDPA: CELLID=10101;
//(7)execute LST CELLHSDPA command to check if HSDPA in the cell is enabled.

LST CELLHSDPA: CellId=10101, LstFormat=VERTICAL;
//in the result, the Cell HSDPA active stats is activated.
14.8.2 Reconfiguring Parameters

Note:
The HSDPA data on the RNC side is reconfigured on the RNC LMT. The HSDPA data
on the NodeB side is reconfigured on the NodeB LMT.
I. HSDPA Data Reconfiguration Commands on RNC Side

The HSDPA data reconfiguration commands on the RNC side are categorized into:
Data reconfiguration commands for RNC-oriented HSDPA, as listed in Table 1.1
Data reconfiguration commands for cell-oriented HSDPA, as listed in Table 1.2
Table 1.1 Data reconfiguration commands for RNC-oriented HSDPA (on RNC side)
Function
Configure RNC-oriented HS-SCCH power
Command
List
oriented

84
RNCHS-
LST HSSCCH
Chapter 14 HSDPA
Function
control algorithm parameters.
Command
SCCH
power
control algorithm
parameters.
Set
RNC-
oriented
SCCH
SET HSSCCH
HSpower
control algorithm
parameters.
Configure
RNC-oriented
HS-DPCCH
power control algorithm parameters.
List
RNC-
oriented
HS-
DPCCH
power
LST HSDPCCH
control algorithm
parameters.
Set
RNC-
oriented
HS-
DPCCH
power
SET HSDPCCH
control algorithm
parameters.
Configure HS-DSCH scheduling priority.
List
HS-DSCH
LST
scheduling
HSDSCHSCHEP
priority.
RIO
Set
HS-DSCH
SET
scheduling
HSDSCHSCHEP
priority.
RIO
Configure algorithm switches related to
List
HSDPA:
connection-
CORRMALGOS
The switch for setting up the streaming
oriented
WITCH
service in the HSDPA cell
algorithm
the
LST
switches.
[HSDPA_DRD_SWITCH]
[HSDPA_STATE_TRANS_SWITCH]
Set
SET
connection-
CORRMALGOS
oriented
WITCH
algorithm
switches.

85
the
Chapter 14 HSDPA
Function
Configure the LDM parameters of HSDPA:
Command
List
the
[CHOICERPRTUNITFORHSDPAPWR
oriented
MEAS]
algorithm
LST LDM
LDM
parameters.
[HSDPANEEDPWRFILTERLEN]
[CHOICERPRTUNITFORHSDPARATE
Set
MEAS]
algorithm
[HSDPAPRVIDBITRATEFILTERLEN]
parameters
RNC-
the
LDM
SET LDM
of
RNC.
Configure the WFMR/WFMRb data of
List
LST
HSDPA:
WFMR/WFMRb
WFMRCFGDATA
[HSDSCHFLOWCTRLWAITTIMERVAL
configuration
UE]
parameters.
[HSDSCHFLOWCTRLRETRANSNUM]
Set
SET
WFMR/WFMRb
WFMRCFGDATA
configuration
parameters.
Configure [HSDPATIMERLEN]
List
RNC-
LST HOCOMM
RNC-
SET HOCOMM
oriented
handover
algorithm
common
parameters.
Set
oriented
handover
algorithm
common
parameters.
Configure the HSDPA traffic for
List HSDPA
WFMR/WFMRb
traffic supported
LST HSDPATRF
by
WFMR/WFMRb.
Set HSDPA traffic
supported by
WFMR/WFMRb.

86
SET HSDPATRF
Chapter 14 HSDPA
Table 1.2 Data reconfiguration commands for cell-oriented HSDPA (on RNC side)
Function
Configure
cell
HSDPA
parameters
List
Command
cell
HSDPA
LST CELLHSDPA
parameters.
Modify cell HSDPA
MOD CELLHSDPA
parameters.
Remove cell HSDPA
RMV CELLHSDPA
parameters.
Activate cell HSDPA
ACT CELLHSDPA
parameters.
Deactivate cell HSDPA
DEA CELLHSDPA
parameters.
Configure cell-oriented HS-
List cell-oriented HS-
SCCH power control algorithm
SCCH power control
parameters.
algorithm parameters.
Modify cell-oriented HS-
LST CELLHSSCCH
MOD CELLHSSCCH
SCCH power control

Remove cell-oriented HS-
RMV CELLHSSCCH
SCCH power control

Configure cell-oriented HS-
List cell-oriented HS-
LST
DPCCH power control
DPCCH power control
CELLHSDPCCH
Modify cell-oriented HS-
MOD
DPCCH power control
CELLHSDPCCH
Remove cell-oriented HS-
RMV
DPCCH power control
CELLHSDPCCH
Configure cell-oriented the
List cell-oriented CAC
CAC algorithm parameters:

87
LST CELLCAC
Chapter 14 HSDPA
Function
Command
[DLTOTALEQUSERNUM]
Modify cell-oriented CAC
[ULHSDPCCHRSVDFACT
OR]
Remove cell-oriented
[HSDSCHGBRTHD]
[HSDSCHBETHD]
[MAXHSDSCHUSERNUM]
MOD CELLCAC
RMV CELLCAC
CAC algorithm
parameters.
II. HSDPA Data Reconfiguration Commands on NodeB Side

Table 1.1 lists the MML commands used for the HSDPA data reconfiguration on
NodeB side.
Table 1.1 HSDPA data reconfiguration commands (on NodeB side)
Function
Command
Listing cell MAC-hs parameters
LST MACHSPARA
Modifying cell MAC-hs parameters
SET MACHSPARA
Listing MAC-hs SPI scheduling parameters
LST MACHSSPIPARA
Modifying
SET MACHSSPIPARA
MAC-hs
SPI
scheduling
parameters
III. Parameter Reconfiguration Verification

Execute the LST CELLHSDPA command to check if the parameters are changed.
IV. Examples
// Reconfigure RNC-oriented HS-SCCH power control algorithm parameters.
//(1) List RNC-oriented HS-SCCH power control algorithm parameters.
LST HSSCCH: LstFormat=VERTICAL;
//(2) Set RNC-oriented HS-SCCH power control algorithm parameters.
SET
HSSCCH:
HsscchPOforSF4=-30,
HsscchPOforSF8SHO=-15,
HsscchPOforSF32=10,
HsscchPOforSF16=-3,
HsscchPOforSF32SHO=10,
HsscchPOforSF128=34,
HsscchPOforSF8=-15,
HsscchPOforSF64=22,
HsscchPOforSF256=46, HsscchPOforSF256SHO=46;
//(3)execute LST HSSCCH command to check if the RNC-oriented HS-SCCH power control
algorithm parameters are changed.

88
Chapter 14 HSDPA

//the results indicate that the parameters are changed.
// Reconfigure cell-oriented HS-SCCH power control algorithm parameters.

//(1) List cell-oriented HS-SCCH power control algorithm parameters.
LST CELLHSSCCH: CellId=10101, LstFormat=VERTICAL;
//(2)Modify cell-oriented HS-SCCH power control algorithm parameters.
MOD
CELLHSSCCH:
CellId=10101,
HsscchPOforSF4=-25,
HsscchPOforSF8=-15;
//(3)execute LST CELLHSSCCH command to check if the cell-oriented HS-SCCH power control
algorithm parameters are changed.
// the results indicate that the parameters are changed.
14.8.3 Disabling HSDPA

I. Disabling Method
Execute the DEA CELLHSDPA command to disable HSDPA in a cell.
HSDPA can be disabled only for a cell rather than for the RNC or the NodeB.
II. Verification
Execute the LST CELLHSDPA command to list cell HSDPA parameters. If the result
shows that the Cell HSDPA active stats is deactivated, HSDPA is disabled in the
cell.
III. Examples
//(1)disable HSDPA in a cell.
DEA CELLHSDPA: CellId=10101;
//(2) execute LST CELLHSDPA command to check if HSDPA in the cell is disabled.
LST CELLHSDPA: CellId=10101, LstFormat=VERTICAL;
// in the result, the Cell HSDPA active stats is deactivated.
14.9 Maintenance Information

14.9.1 MML Commands Related with HSDPA on the RNC Side
The MML commands related with HSDPA on the RNC side are as follows:
ADD CELLHSDPA: Add cell HSDPA parameters.
SET CORRMALGOSWITCH: Set connection-oriented algorithm switches.
SET HSDSCHSCHEPRIO: Set HS-DSCH schedule priority.
ADD CELLCAC: Add cell-oriented CAC algorithm parameters.

89
Chapter 14 HSDPA
ADD CELLHSSCCH: Add cell-oriented HS-SCCH power control algorithm

parameters.
SET HSDPCCH: Set RNC-oriented HS-DPCCH power control algorithm

parameters.
ADD CELLHSDPCCH: Add cell-oriented HS-DPCCH power control algorithm

parameters.
SET HOCOMM: Set RNC-oriented Handover algorithm common parameters.
14.9.2 MML Commands Related with HSDPA on the NodeB Side

The MML command related with HSDPA on the NodeB side is SET MACHSPARA
and SET MACHSSPIPARA.
14.9.3 Related Alarms

Table 1.1 lists alarms related to HSDPA.
Table 1.1 Alarms related to HSDPA
AlarmID
AlarmName
ALM_2027
Cell HSDPA Setup Failed
ALM_2028
Cell HSDPA Reconfiguration Failed
ALM_2029
Cell HSDPA Delete Failed
ALM_2030
Cell HSDPA Unavailable
14.9.4 Counters
HSDPA counters belong to CELL->HSDPA->HSDPA.Cell.
Table 1.1 lists the counters.
Table 1.1 HSDPA counters
Item
Description
VS.HSDPA.MACDSuccStpPerCell
Number
of
Successful
HSDPA
Service
of
Successful
HSDPA
Service
Setups
VS.HSDPA.MACDSuccDelPerCel
l
Number
Deletions
VS.HSDPA.MACDFailStpPerCell
Number of Unsuccessful HSDPA Service

Setups

90
Chapter 14 HSDPA
Item
Description
VS.HSDPA.MACDFailDelPerCell
Number of Unsuccessful HSDPA Service

Deletions
VS.HSDPA.ChR.DCHtoHSDSCH
Number of Successful Handovers from DCH

to HSDSCH
VS.HSDPA.ChR.FACHtoHSDSC
Number of Successful Handovers from FACH
to HSDSCH
VS.HSDPA.ChR.HSDSCHtoDCH
Number
of
Successful
Handovers
from
Handovers
from
HSDSCH to DCH
VS.HSDPA.ChR.HSDSCHtoFAC
H
Number
of
Successful
HSDSCH to FACH
VS.HSDPA.UE.Mean.Cell
Number of UEs in CELL_HSDPA State
Average
VS.HSDPA.MeanChThroughput
Mean Throughput of MAC-D Flows
14.10 Reference
3GPP TS 25.101, User Equipment (UE) radio transmission and reception

(FDD), V5.8.0.
3GPP TS 25.211, Physical channels and mapping of transport channels onto

physical channels (FDD), V5.5.0.
3GPP TS 25.212, Multiplexing and channel coding (FDD), V5.6.0.
3GPP TS 25.213, Spreading and modulation (FDD), V5.4.0.
3GPP TS 25.214,Physical layer procedures (FDD), V5.6.0.
3GPP 25.877, High Speed Downlink Packet Access (HSDPA) - Iub/Iur Protocol
Aspects.
3GPP 25.858,Physical layer aspects of UTRA High Speed Downlink Packet

Access.
3GPP 25.301,Radio Interface Protocol Architecture.
3GPP 25.302,Services provided by the physical layer.
3GPP 25.308,UTRA High Speed Downlink Packet Access (HSPDA); Overall

description.
3GPP 25.321,Medium Access Control (MAC) protocol specification.
3GPP 25.420,UTRAN Iur interface general aspects and principles.
3GPP 25.423,UTRAN Iur interface RNSAP signaling.
3GPP 25.425,UTRAN Iur interface user plane protocols for CCH data flows.

91
Chapter 14 HSDPA
3GPP TS 25.430,UTRAN Iub interface: general aspects and principles.
3GPP 25.433,UTRAN Iub interface NBAP signaling.
3GPP 25.435,UTRAN Iub interface user plane protocols for CCH data flows.

92

14 Hsdpa

Uploaded by

Copyright:

Available Formats

You might also like

14 Hsdpa

Uploaded by

Document Information

Original Description:

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

14 Hsdpa

Uploaded by

Copyright:

Available Formats

RAN Feature Description

RAN Feature Description

14.9.2 MML Commands Related with HSDPA on the NodeB Side..............................14-78

Huawei Technologies Proprietary

RAN Feature Description

RAN Feature Description

Figure 14-27 Different status of the RRC of the UE..........................................................14-56

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Table 14-30 NACK poweroffset......................................................................................... 14-42

Huawei Technologies Proprietary

RAN Feature Description

The frames transmitted over the air interface are 2 ms.

Shorter service delay: providing a faster service experience to the subscribers,

Huawei Technologies Proprietary

RAN Feature Description

14.2.3 Terms and Abbreviations

The UE sends CQI through the HS-DPCCH to the NodeB to

A cell that can provide HSDPA connection and HSDPA service

to the UEs. One UE can have at most one servicing HSDPA

To allocate the HS-DSCH resources between the data flow

entity and the HARQ entity according to the priorities.

The entity selects a transmission mode according to the

Huawei Technologies Proprietary

RAN Feature Description

Refers to the cell without the HSDPA channel and cannot

The physical channels of HSDPA, including HS-SCCH, HSPDSCH, and HS-DPCCH.

All physical channels other than the HSDPA channel.

A connection between a cell and a UE when the service the

UE applies to is carried on HS-DSCH.

A connection between a cell and a UE when the service the

The transmission channel of HSDPA

16 Quadrature Amplitude Modulation

Adaptive Modulation and Coding

Call Admission Control

Common Transport Channel Priority Indicator

Channel Quality Indicator

Controlling Radio Network Controller

Dedicated Physical Channel

Dedicated Traffic Channel

Huawei Technologies Proprietary

RAN Feature Description

Enhanced Data rates for GSM Evolution

Forward Access Channel

General Packet Radio Service

Global System for Mobile Communications

Hybrid Automatic Repeat Request

High Speed Downlink Packet Access

Dedicated Physical Control Channel (uplink) for HS-DSCH

High Speed Downlink Shared Channel

High Speed Physical Downlink Shared Channel

Shared Control Physical Channel for HS-DSCH

Medium Access Control for HSDPA

Primary Common Control Physical Channel

Protocol Data Unit