Introduction to HSDPA

QUALCOMM CDMA Technologies

80-V9924-1 A

QUALCOMM Proprietary
Restricted Distribution: This document contains critical information about QUALCOMM products and may not be distributed to anyone that
is not an employee of QUALCOMM, its affiliates or subsidiaries without the approval of Configuration Management.
Export of this technology may be controlled by the United States Government. Diversion contrary to U.S. law prohibited.
All data and information contained in or disclosed by this document is confidential and proprietary information of QUALCOMM Incorporated
and all rights therein are expressly reserved. By accepting this material the recipient agrees that this material and the information contained
therein is to be held in confidence and in trust and will not be used, copied, or reproduced in whole or in part, nor its contents revealed in any
manner to others without the express written permission of QUALCOMM Incorporated.
QUALCOMM is a registered trademark and registered service mark of QUALCOMM Incorporated. cdma2000 is a registered certification
mark of the Telecommunications Industry Association. Used under license. Other product and brand names may be trademarks or registered
trademarks of their respective owners.

QUALCOMM Incorporated
5775 Morehouse Dr.
San Diego, CA 92121-1714
Copyright 2005 QUALCOMM Incorporated. All rights reserved.

80-V9924-1 A Page 1 QUALCOMM Proprietary

January 2005
 The following information
is licensed and
proprietary material.

Copyright 2005

Revision history

Version Date Description

A Jan 2005 Initial release

80-V9924-1 A Page 2 QUALCOMM Proprietary

January 2005
 Contents
Overview
3GPP Specifications
HS Channels
Physical Layer Timeline
General Procedure
HSDPA Upper Layer Stack
Hybrid ARQ
Reordering Protocol
MAC-d Multiplexing
RRC Layer
Typical Call Flows

80-V9924-1 A Page 3 QUALCOMM Proprietary

January 2005
 Overview

80-V9924-1 A Page 4 QUALCOMM Proprietary

January 2005
 Overview
HSDPA stands for High-Speed Downlink Packet Access
Introduced in 3GPP Release 5 specifications
Trades off the uncertainty of delivery latency for better
support of bursty traffic
Greatly improves network capacity and user perception of
network latency
Replaces:
High data rate (HDR) dedicated setups (144, 384 kbps)
PDSCH (will probably never be supported)

80-V9924-1 A Page 5 QUALCOMM Proprietary

January 2005
 Overview Whats wrong with R99?
In Release 99, DPCH does most of the data transport
Problems with DPCH + bursty data
Difficult to match OVSF code allocation with varying data
rate requirements
DPCH is power-controlled; there is no way to avoid
transmitting to the UE when it is in a temporary fade.
Retransmission has a very high latency (hundreds of ms),
thus, a good BLER target is necessary.
Soft handover occupies resources from multiple base
stations.

80-V9924-1 A Page 6 QUALCOMM Proprietary

January 2005
 Overview Solution: HSDPA
In HSDPA, HS-PDSCH (a new shared channel) does most of
the data transport
Key aspects
In essence, reconfigure the physical/transport channel every 2 ms TTI.
Transmit over very short intervals to only a few users in good coverage
Hybrid ARQ improves both the efficiency and latency of retransmission;
lower the BLER quality target requirement to 20~30%
Adaptive modulation and coding (AMC) QPSK and 16-QAM available;
adaptive according to network resources and channel conditions
No soft handover
Other benefits
Salvage unused channels/leftover power
Better QoS support due to easier OVSF management

80-V9924-1 A Page 7 QUALCOMM Proprietary

January 2005
 3GPP Specifications

80-V9924-1 A Page 8 QUALCOMM Proprietary

January 2005
 3GPP Specifications
3GPP Release 5 specifications are:
25.308 3GPP HSDPA; overall description
25.211 3GPP physical channels and mapping of transport
channels onto physical channels (FDD )
25.212 3GPP multiplexing and channel coding (FDD)
25.213 3GPP spreading and modulation (FDD)
25.214 3GPP physical layer procedures (FDD)
25.101 3GPP UE radio transmission and reception (FDD)
25.306 3GPP UE radio access capabilities
25.321 3GPP MAC protocol specification
25.322 3GPP RLC protocol specification
25.331 3GPP RRC protocol specification
34.108 3GPP common test environments for UE; conformance
testing
34.123 3GPP user equipment (UE) conformance specification
Revisions after Jun 2004 are fairly stable.

80-V9924-1 A Page 9 QUALCOMM Proprietary

January 2005
 HS Channels

80-V9924-1 A Page 10 QUALCOMM Proprietary

January 2005
 HS Channel HS-PDSCH
High-Speed Physical Downlink Shared Channel
(HS-PDSCH)
Defined in 25.211 SF = 16; TTI = 3 slots or 2 ms (called
a subframe); timing = 2 slots offset from CPICH frame
boundary. The whole 3 slots contain only data bits, no
control bits. Either 16-QAM or QPSK can be used.
A UE can be given multiple HS-PDSCH codes
simultaneously; their code numbers must be contiguous
(25.212).
From one transmission to another, everything is subject to
change: OVSF codes, rate matching, modulation format,
etc.

80-V9924-1 A Page 11 QUALCOMM Proprietary

January 2005
 HS Channel HS-PDSCH (cont.)
Power control constant power over the 3 slots; Node B
is responsible for sending at reasonable Tx power
(25.214 5.2.10) based on UE feedback, priority, and
latency requirement, number of transmissions already
took place, etc.
Power control target around 20% one-shot error rate;
0% error rate after a few retransmissions
Timing offset 2 slots from CPICH boundary to make
causal processing possible

80-V9924-1 A Page 12 QUALCOMM Proprietary

January 2005
 HS Channel HS-PDSCH (cont.)
One subframe carries exactly one transport block
Coding chain very similar to DPCH
Can be very severely punctured to rate 3/4
A transport block is a concatenation of several MAC-d
PDUs; PDUs from multiple logical channels can be
multiplexed together in the same subframe, as long as
they have the same priority

80-V9924-1 A Page 13 QUALCOMM Proprietary

January 2005
 HS Channel HS-DPCCH
High Speed Dedicated Physical Control Channel
(HS-DPCCH)
Defined in 25.211, 5.2.1
TTI = 2 ms (subframe); contains two fields,
HARQ-ACK (1 slot) followed by CQI (2 slots)
Channelization Cch, 256, 64 on the Q branch (25.213)
Timing formula in 25211,7.7; it says ACK/NACK is
to be sent 7.5 slots after the reception of HS-PDSCH;
slot boundary of HS-DPCCH and UL DPCCH may
not align

80-V9924-1 A Page 14 QUALCOMM Proprietary

January 2005
 HS Channel HS-DPCCH (cont.)
Syntax
ACK/NACK (25.211, 7.7) to ACK if the CRC of the corresponding
HS-PDSCH passes
CQI (25.214, 6) UE declares that, during the 3 slots measurement
period, the UE could have received a PDSCH with transport format
indicated in Table 7 (25.214) with <10% error probability
ACK/NACK field can be configured to use repetition
CQI field can be configured to use repetition and reporting period
can be longer than 2 ms TTI
Power control
Power offset relative to DPCCH ACK, NACK, CQI are signaled by
the network
Power adjusted together with DPCCH

80-V9924-1 A Page 15 QUALCOMM Proprietary

January 2005
 HS Channel HS-SCCH
High-Speed Shared Control Channel (HS-SCCH)
TTI = 2 ms, subframe boundary aligned with P-CPICH
A Node B can send many HS-SCCHs in order to address
several UEs
A UE can be asked to monitor up to four HS-SCCH
At any time, only one of the four HS-SCCHs can address
a UE; UE uses information embedded in HS-SCCH to
identify which one is the right one
Expected error rate = 1%, unless UE is in a difficult region

80-V9924-1 A Page 16 QUALCOMM Proprietary

January 2005
 HS Channel HS-SCCH (cont.)
Power control only suggested that it follows DL DPCH
(25.214 5.2.11)
Tx diversity no TD, STTD only
Phase reference P-CPICH, S-CPICH mandatory;
dedicated pilot optional
Syntax
Timing 2 slots ahead of HS-PDSCH; makes causal
processing possible
Part 1 contains code and mod information; sufficient to
start Rake receiver
Part 2 contains transport block size information, hybrid
ARQ process information, redundancy and constellation
version; needed to do deinterleaving and decoding

80-V9924-1 A Page 17 QUALCOMM Proprietary

January 2005
 Physical Layer Timeline

80-V9924-1 A Page 18 QUALCOMM Proprietary

January 2005
 Physical Layer Timeline
CPICHframeboundary

P-CPICH P-CPICH P-CPICH P-CPICH P-CPICH P-CPICH

DL

HS-SCCH Part 1 HS-SCCH Part 2 HS-SCCH Part 1 HS-SCCH Part 2

DL

HS-DSCH HS-DSCH
DL

CQI ACK/NACK CQI ACK/NACK CQI

UL

d d d d d
T T T T T
a T a T a T a T a T
F data F data F data F data F data
DP t P
C
DP t P
C
DP t P
C
DP t P
C
DP t P
C
DP
a C 2 a C 2 a C 2 a C 2 a C 2
I I I I I
1 1 1 1 1

DL

80-V9924-1 A Page 19 QUALCOMM Proprietary

January 2005
 General Procedure

80-V9924-1 A Page 20 QUALCOMM Proprietary

January 2005
 General Procedure
DPCH must be on all the time for power control
Handset periodically tells Node B the instantaneous
channel quality via HS-DPCCH
Node B tells handset to receive from certain HS-PDSCH
channels via HS-SCCH
Node B sends data via HS-PDSCH(s)
Handset acknowledges the success reception via
HS-DPCCH

80-V9924-1 A Page 21 QUALCOMM Proprietary

January 2005
 HSDPA Upper Layer Stack

80-V9924-1 A Page 22 QUALCOMM Proprietary

January 2005
 HSDPA Upper Layer Stack

RLC
SN DATA . SN DATA . SN DATA

Logical Channel 1 Logical Channel i Logical Channel k

MAC-d
C/T DATA . C/T DATA . C/T DATA

Mac-d Flow (1) Mac-d Flow (n) Mac-d Flow (n)

Demulti-
plexing SID N1 F DATA . DATA . SID N2 F N3 F DATA DATA . DATA

N1 Blocks N2 Blocks N3 Blocks

Reordering
VF QID TSN DATA . VF QID TSN DATA .

HARQ
Color HID RID DATA . DATA .

2ms 2ms

HS Shared Control Channel

HS Shared Data Channel

80-V9924-1 A Page 23 QUALCOMM Proprietary

January 2005
 Hybrid ARQ

80-V9924-1 A Page 24 QUALCOMM Proprietary

January 2005
 Hybrid ARQ
Incremental Redundancy (IR) a procedure that
significantly improves the efficiency and latency of
retransmission
UE has a virtual IR buffer, which can be divided
(unevenly) among at most eight hybrid ARQ processes at
network command (25.331)
Virtual IR buffer used to store the failed retransmissions
If a transmission fails, network selects and sends (via rate
matching) a new set of parity bits that were not sent
during retransmission; UE is envisioned to accumulate at
the soft-bit level (25.212)

80-V9924-1 A Page 25 QUALCOMM Proprietary

January 2005
 Hybrid ARQ (cont.)
Sender side
Must wait for ACK/NACK to start retransmission
From transmission to retransmission, the least separation in
time is 12 ms (= RTT is 6 subframes)
At least six hybrid ARQ processes must be configured if
network wants to Tx to the same UE in every subframe
Receiver side
Hybrid ARQ causes out-of-order arrival at MAC
MAC implements reordering functionality before delivering to
RLC

80-V9924-1 A Page 26 QUALCOMM Proprietary

January 2005
 Reordering Protocol

80-V9924-1 A Page 27 QUALCOMM Proprietary

January 2005
 Reordering Protocol
Required because HARQ introduces out-of-sequence delivery of
data
Uses in-band control information
Queue ID (3 bits) identifies the reordering buffer for which the
payload is intended
TSN (6 bits) identifies the sequence of the packet
Uses a window to eliminate the ambiguity in the sequence
number space
Needs to handle delayed and missing payloads
Two schemes for flushing missing payloads
Timer
Window
Data from one reordering entity is mapped to one MAC-d entity
(configured by RRC)

80-V9924-1 A Page 28 QUALCOMM Proprietary

January 2005
 Window Mechanism
Used both for flushing holes and for eliminating sequence
number ambiguity
Sequence number space size is 64
Window size is configurable by RRC (max is 32)
independently for each reordering queue
Payloads are added in the position indicated by the TSN
Data received in sequence are delivered to higher layers
Window is advanced every time a payload is received
outside the window so as to include it
Payloads that are left out of the window after it is
advanced are flushed to the higher layers

80-V9924-1 A Page 29 QUALCOMM Proprietary

January 2005
 Timer Mechanism (cont.)
Single timer for each reordering queue
Value is configurable by RRC independently for each reordering
queue
Start timer when a hole is detected in the sequence
Timer is associated with the hole in the sequence that triggered
it
When timer expires:
Flush to the higher layers all the payloads within the window before
the associated hole.
Assume that all the data before and including the hole were
received successfully.
If there is still a hole, start the timer and associate it with the very
last hole.
Mitigates cascading timer problem

80-V9924-1 A Page 30 QUALCOMM Proprietary

January 2005
 MAC-d Multiplexing

80-V9924-1 A Page 31 QUALCOMM Proprietary

January 2005
 Multiplexing Architecture

U T R A N R `9 9 UTRAN HSDPA

RLC 2 RLC 2

RLC 3 R LC 3
RLC 1 RLC 1

L o g ic a l
C h a n n e ls

M A C -d M A C -d

C /T M U X C /T M U X

M A C -d F u n c tio n 1 M A C - d F u n c t io n 2 M A C - d F u n c t io n 1 M A C -d F u n c tio n 2

M A C -d
F lo w s

M A C -h s

M A C - d F lo w M U X

T ra n s p o rt
C h a n n e ls
PHY PHY

T rC h M U X (T F C I)

80-V9924-1 A Page 32 QUALCOMM Proprietary

January 2005
 Multiplexing Architecture (cont.)
Each RLC UM entity can support multiple PDU sizes (from
R99).
There is always a single RLC PDU per MAC-d PDU (from R99).
A MAC-hs PDU:
Can carry multiple MAC-d PDUs
Potentially of different sizes (every time the size changes a header
extension is required)
Is meant for a single reordering queue
Signaling for a set of PDUs of equal size
PDU size index (3 bits)
Number of PDUs of this size (7 bits)
Continue flag (1 bit)

80-V9924-1 A Page 33 QUALCOMM Proprietary

January 2005
 RRC Layer

80-V9924-1 A Page 34 QUALCOMM Proprietary

January 2005
 RRC Layer
HSDPA channels can exist only in CELL_DCH state.
Six RRC messages can be used to set up/reconfigure HSDPA
CELL UPDATE CONFIRM
RADIO BEARER SETUP
RADIO BEARER RECONFIGURATION
RADIO BEARER RELEASE
TRANSPORT CHANNEL RECONFIGURATION
PHYSICAL CHANNEL RECONFIGURATION
Event 1D has to report the best cell immediately.
After the initial report, each change of best cell will be reported as
in R99.
This is needed to always point the HSDPA channel to the best cell.

80-V9924-1 A Page 35 QUALCOMM Proprietary

January 2005
 RRC Layer (cont.)
H-RNTI (H_RNTI) is introduced and it is similar to C-RNTI for
HSDPA.
Unlike C-RNTI, the same H-RNTI may be valid in multiple cells.
A new H-RNTI may also be assigned every time HSDPA is
repointed.
H-RNTI management will depend on the network implementation.
To repoint the serving HS-DSCH cell in the active set, UTRAN
sends a reconfiguration message.
ACTIVE SET UPDATE cannot repoint the HSDPA channel.
The UE should not listen to the HSDPA channels during CM
gaps.

80-V9924-1 A Page 36 QUALCOMM Proprietary

January 2005
 Typical Call Flows

80-V9924-1 A Page 37 QUALCOMM Proprietary

January 2005
 Typical Call Flow

80-V9924-1 A Page 38 QUALCOMM Proprietary

January 2005
 Questions?

https://support.cdmatech.com/
80-V9924-1 A Page 39 QUALCOMM Proprietary
January 2005