Hsdpa Basic

HSDPA/HSUPA
High speed packet access

March 22nd 2005
Salo, Finland
Harri Holma, Principal Engineer

Antti Toskala, HSDPA Chief Architect
Nokia, Finland
1 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

Agenda
• WCDMA R99 performance today
• HSDPA standard
• HSDPA performance
• HSUPA standard
• HSUPA performance

WCDMA Performance in Commercial
Networks

WCDMA Release’99 Terminal Capability
– Nokia 6630
Downlink 384 kbps
EDGE included Uplink 128 kbps
• Data rates
• WCDMA up to 384 kbps (DL) and 128 kbps (UL)
• EDGE 4+2 = 236 kbps (DL) and 118 kbps (UL)
• WCDMA2100, GSM900/1800/1900
• Symbian Series 60 platform
• Colour display 176 x 208 pixels & 65k colours
• Camera 1.3 Mpixel
• Stand-by up to 11 days
• Talk time up to 3 hours
• Weight/volume: 127 g

WCDMA Coverage – Noise Limited
384 kbps can be provided
down to approx– 105 dBm if
no other-cell interference
3 parallel users in WCDMA
400
384 kbps WCDMA2100
350 EDGE900
300
250
kbps
200
Similar average data rate of
150
approx 200 kbps with
WCDMA2100 and EDGE900
100
50
0
-115 -110 -105 -100 -95 -90 -85 -80
CPICH RSCP [dBm]

WCDMA Coverage – Interference Limited
3 parallel users in WCDMA

400
350 WCDMA2100
EDGE900
300
250
kbps
200
150
Approx 2 x higher data rate
in WCDMA than in EDGE
100
Data rate other-cell
50 interference limited at
the cell edge
0
-100 -95 -90 -85 -80 -75 -70
CPICH RSCP [dBm]

WCDMA Round Trip Time (RTT)
• Typical round trip time 150-200 ms for small IP packets in today’s networks
• R99 round trip time expected to go below 120 ms with 10-ms TTI
End-to-end Round Trip Time (RTT)

150 – 200 ms
Radio transmission UMTS RAN + core Internet
UE BTS RNC SGSN GGSN Server

Download of 1st WAP Page Today
• 384 kbps DCH is fully used only <1 s out of 10 s
• Packet setup times must get (and will get!) shorter to get full benefit from HSDPA
1 2 3 4 5 6 7 8 9 10 11 12 13
HTTP 384 kbps

RB TCPrequest
RRC PDP reconfig 32 RB reconfig
kbps
1.5 s 0.7 s 0.4 2.0 s 1.4 s 0.5 0.4 0.6 s 0.9 s 0.7 0.4 0.5
= 10 s
1 User pushes WAP home page key
2 UE internal delay (in Nokia browser in Charlie)
3 RRC connection activation
4 Security mode
5 PDP context activation + signaling radio bearer setup + measurement control
6 Radio bearer reconfiguration from 0/0 kbps to 16/32 kbps – uplink initiated
7 UE internal delay
8 TCP connection establishment
9 HTTP request in uplink
10 Radio bearer reconfiguration to 16/384 kbps – downlink initiated
11 Page download starts over 384 kbps. TCP slow start takes about 0.7 s.
12 Rest of the page downloaded with full 384 kbps speed, depends on the page size.
13 UE display rendering
Optimized 1st WAP Page Download
• WAP page download time could be reduced from 10 s below 5 s without increasing bit rate
• Setup time is reduced from 5.7 to 1.6 s, the rest is application signalling and UE delays
1st WAP Page Download Time

12.0 1 UE Symbian delay reduced from 1.5 to 0.5 s
2 RRC setup on common channels
10.3 s Authentication done with GPRS attach already
3
10.0 4 Direct RB allocation after PDP context
5 UE delay removed
6 6 Seamless RB upgrade
8.0 Display rendering
Download over 384 kbps
TCP slow start
5 DCH upgrade
DNS query and HTTP request
s 6.0
4 4.7 s
TCP connection establishment
UE internal delay
RB reconfiguration
PDP context activation
4.0 Security mode
Authentication and ciphering
RRC connection establishment
3 UE internal delay
2.0 2
1
= Setup times
0.0
RAN04 Optimized
Summary of Voice Capacity Tests
• Typical voice capacity 60-70 users per cell with AMR 12.2 kbps. Up to 2x more
with lower rate AMR.
AMR 12.2 kbps users with 50% voice activity

80
70
Voice users per 5 MHz
60
50
40
30
20
10
0
European Example last Asia, high Asia, low Asia, Asia, drive
op slide result result stationary test

Summary of Data Capacity Tests
• Typical data capacity 600-1000 kbps per cell
1000
Measured stationary
900
Measured drive test
Aggregate cell throughput
800
700
600
500
400
300
200
100
0
Packet throughput Packet throughput Packet throughput Packet throughput
uplink downlink (64) downlink (128) downlink (384)

WCDMA High Speed Downlink Packet
Access (HSDPA) of Release 5
Reference: WCDMA for UMTS, 3rd edition, Chapter 11

Outline
• HSDPA Introduction
• HSPDA Protocol Architecture
• New Node B & UE functions
• Modulation and coding
• HSDPA & Soft Handover
• HSDPA vs DCH/DSCH
• HSDPA & Iub
• Summary

High Speed Downlink Packet Access HSDPA
• Peak data rates increased to significantly higher than 2 Mbps;
Theoretically exceeding 10 Mbps
• Packet data throughput increased 50-100% compared to 3GPP
release 4
• Reduced delay from retransmissions.
• Solutions
• Adaptive modulation and coding QPSK and 16-QAM
• Layer 1 hybrid ARQ
• Short frame 2 ms
• Schedule in 3GPP
• Part of Release 5
• First specifications version completed 03/02

HSDPA – General Principle
Downlink fast scheduling

L1 Feedback done directly by Node B
(BTS) based on
Data knowledge of:
• UE's channel quality

Terminal 1 (UE) • UE's capability
L1 Feedback • QoS demands
Data
• Power and code resource
availability
• Node B buffer status
Terminal 2
Users may be time and/or code multiplexed

Multi-user Diversity (Fast Scheduling)
Node-B scheduling can utilize
Channel quality information on the
(CQI, Ack/Nack, TPC) instantaneous channel
conditions for each user.
Data
UE1 TTI 1 TTI 2 TTI 3 TTI 4

Scheduled user
Multi-user selection diversity
(give shared channel to “best” user)
Channel quality
(CQI, Ack/Nack, TPC) Data
UE2 USER 2 Es/N0 USER 1 Es/N0

Fast Link Adaptation in HSDPA
16 C/I received by C/I varies
Instantaneous EsNo [dB]
14 UE with fading
12
10
8
6
4
2
0
-2
0 20 40 60 80 100 120 140 160
Time [number of TTIs]
16QAM3/4 Link BTS adjusts link adaptation
adaptation mode with a few ms delay
16QAM2/4 mode based on channel quality
QPSK3/4 reports from the UE
QPSK2/4
QPSK1/4
Release’99 RRM Functional Split
•• Mapping
MappingRABRABQoS
QoSParameters
Parametersintointoair
airinterface
interface
L1/L2 parameters (incl. transport channel selection)
L1/L2 parameters (incl. transport channel selection)
•• Air
Airinterface
interfacescheduling
scheduling(for (fordedicated
dedicatedchannels)
channels)
•• Handover Control
Handover Control
•• Outer
Outerloop
looppower
powercontrol
controland
andpower
powerbalancing
balancing
RR
C
••Fast
Fastpower
power Iub
control Iur Iu
control MSC
••Overload
Overloadcontrol
control Drift RNC
Node B
Serving
•• Admission RNC SGSN
Admissioncontrol
controlon
oninterference
interferenceand
andpower
powerlevel
level
•• Initial power and SIR setting
Initial power and SIR setting
•• Radio
Radioresource
resourcereservation
reservation
•• Air
Air interface schedulingfor
interface scheduling forcommon
commonchannels
channels Radio
•• DL code allocation and code three handling Radionetwork
network
DL code allocation and code three handling topology
topologyhidden
hiddentotothe
the
•• Load
Loadand andoverload
overloadcontrol
control CN
CN
HSDPA Protocol Architecture
• New MAC entity, MAC-hs added to the Node B
• Layers above, such as RLC, unchanged.
UE Node B SRNC
NAS
RLC
RLC MAC-d Iu
MAC MAC-hs FRAME FRAME
PROTOCOL PROTOCOL
WCDMA L1 WCDMA L1
TRANSPORT TRANSPORT
Uu Iub/Iur
HSDPA user plane

Release’99 vs HSDPA Retransmissions
Rel’99 DCH/DSCH Rel’5 HS-DSCH
RNC
Packet Retransmission
Packet Retransmission
BTS
RLC ACK/NACK L1 ACK/NACK
Terminal

HSDPA L1 Retransmissions
• The L1 retransmission procedure (Hybrid ARQ, HARQ) achieves following
• L1 signaling to indicate need for retransmission -> fast round trip time facilitated
between UE and BTS
• Decoder does not get rid off the received symbols when decoding fails but combines the
new transmisssion with the old one in the buffer.
• There are two ways of operating:

• A) Identical retransmission (soft/chase combining): where exactly same bits are
transmitted during each transmission for the packet
• B) Non-identical retransmission (incremental redundancy): Channel encoder output is
used so that 1st transmission has systematic bits and less or not parity bits and in case
retransmission needed then parity bits (or more of them) form the second transmission.

New Node B functionality for HSDPA
RNC Node B Terminals
Packets
Scheduler ARQ &
& Buffer Coding
Flow Control
ACK/NACK &
Feedback
Decoding
New Node B functions:

• Scheduler: Terminal scheduling, Coding & Modulation selection (16QAM as
new modulation)
• ARQ Retransmissions Handling
• Uplink Feedback Decoding
• Flow Control towards SRNC

New terminal functionality for HSDPA
RNC Node B Terminal
Packets ARQ Soft Buffer

Decoding & Combining
Flow Control
ACK/NACK &
Feedback
Generation
New terminal functions:

• 16 QAM demodulation
• ARQ Retransmissions Handling
• Soft buffer & combining
• Fast Uplink Feedback Generation & encoding

Adaptive Modulation – QPSK and 16QAM
• Release’99 uses QPSK
• HSDPA uses both QPSK and 16-QAM
• 16-QAM requires also amplitude estimation from CPICH for detection
QPSK 16QAM
HSDPA - UE Categories
• Theoretical peak bit rate up to 14 Mbps
• 1.8 Mbps and 3.6 Mbps capability expected initially
HSDPA Transport
Modulation Inter-TTI 5 Codes 10 Codes 15 Codes
Category Block size
11 QPSK only 2 3630 0.9 Mbps - -
12 QPSK only 1 3630 1.8 Mbps - -
1/2 QPSK/16QAM 3 7298 1.2 Mbps - -
3/4 QPSK/16QAM 2 7298 1.8 Mbps - -
5/6 QPSK/16QAM 1 7298 3.6 Mbps - -
7/8 QPSK/16QAM 1 14411 - 7.2 Mbps -
9 QPSK/16QAM 1 20251 - - 10.1 Mbps
10 QPSK/16QAM 1 27952 - - 14.0 Mbps

HSDPA - UE Categories (cont.)
• Inter-TTI interval > 1 means that terminal can not receive data in consecutive TTIs
• No indication of actually being used in the market place
• Other key issues are:
• 16QAM support (not part of 2 categories)
• The key different in the first devices
• Size of the memory: Larger memory per class allows incremental redundancy even
with full rate
• Number of HS-DSCH codes supported (5, 10 or 15)
Not permitted for the same user with Inter TTI > 1
HS-DSCH

HSDPA DL Channel Structure
• High speed downlink shared channel (HS-DSCH) carries the user data in the
downlink direction, with the peak rate up to 10 Mbps
• High speed shared control channel (HS-SCCH) carries the necessary physical layer
control information to enable decoding of the data on HS-DSCH
• Only one HS-SCCH needed if only time multiplexing is used
• DCH always running in parallel
HS-SCCHs
…
Control
Controldata
data …
HS-DSCH Demodulation information
User
Userdata
data
2 ms

r s b
HS-SCCH RV
coding
Xrv
Xccs Xms Xtbs Xhap Xnd
• The HS-SCCH is fixed data rate channel
with SF 128 (60 kbps)
• The content is divided in two parts mux mux
• First part carries X1 X2

• Channelisation-code-set info
Xue
• Modulation info UE specific
CRC
attachment
• Second Part Y
• Transport-block size information Channel Channel

Coding 1 Coding 2
• Hybrid-ARQ process information
Z1 Z2
• Redundancy and constellation version
• New data indicator Rate
matching 1
Rate
matching 2
• Additionally UE identify information is R1 R2

used target the information to correct
user Xue UE
specific
• To separate which of the 4 HS-SCCHs UE masking
S1
needs to decode (UE specific masking)
• Decoder matrix to be observed….. Physical
channel
mapping

HS-SCCH
aim1 ,aim2 ,aim3 ,...aimA
HS-DSCH CRC attachment
bim1 ,bim2 ,bim3 ,...bimB
• The HS-DSCH uses 1 to 15 codes with fixed Bit Scrambling
SF 16 dim1 ,dim2 ,dim3 ,...dimB
• Specific parts in the channel coding chain Code block segmentation
are related to HARQ and 16QAM oir1,oir2,oir3,...oirK
modulation (and some simplifications as Channel Coding
there is no DTX, compressed mode etc…) ci1,ci2,ci3,...c iE
• Impacted by 16QAM Physical Layer Hybrid-ARQ

functionality
• Interleaving (two identical interleavers w1,w2,w3,...wR
with 16QAM TTIs) Physical channel

segmentation
• Constellation re-arrangement (same bits
not in same constellation point between up,1 ,up,2 ,up,3 ,...up,U
retransmissions HS-DSCH
Interleaving
vp,1 ,vp,2 ,vp,3 ,...vp,U

Constellation
re-arrangement
for 16 QAM
rp,1 ,rp,2 ,rp,3 ,...rp,U
Physical channel mapping
PhCH#1 PhCH#P
HSDPA UL Channel Structure
• High Speed Dedicated Physical Control Channel (HS-DPCCH) carries the uplink
HSDPA related L1 control information to the BTS
• This is parallel to the Uplink DCH
• Timing from downlink packet to uplink feedback (ACK/NACK) is fixed thus
network knows for which packet the info is related to
ACK/NACK Channel Quality Information
HS-SCCHs HS-DPCCH
CRC result
2 ms
HS-DSCH
7.5 slots (approx.)

2 ms

HS-DPCCH
• The HS-DPCCH is fixed data rates channel with SF 256
• As this is BPSK channel, this gives 10 bits per slot
• 1 slot used for ACK/NACK code word, 2 slots for the CQI info
•For CQI one of the 0 .. 30 values transmitted (one unused value)
•(20,5) code used
i Mi,0 Mi,1 Mi,2 Mi,3 Mi,4
0 1 0 0 0 1
1 0 1 0 0 1
message w w w w w w w w w w 2 1 1 0 0 1
to be
transmitte
0 1 2 3 4 5 6 7 8 9
3 0 0 1 0 1
d 4 1 0 1 0 1
5 0 1 1 0 1
ACK 1 1 1 1 1 1 1 1 1 1 6 1 1 1 0 1
7 0 0 0 1 1
NACK 0 0 0 0 0 0 0 0 0 0
8 1 0 0 1 1
9 0 1 0 1 1
PRE 0 0 1 0 0 1 0 0 1 0
10 1 1 0 1 1
11 0 0 1 1 1
POST 0 1 0 0 1 0 0 1 0 0
12 1 0 1 1 1
Party omitted …

PAR Increase due HS-DPCCH
• Terminal TX power is allowed to be reduced with low DCH uplink data rates, due
to the added parallel channel -> increased peak to average ratio when channels have
close to equal power
Power Class 3 Power Class 4

Ratio of DPCCH/DPDCH
gain factors for all values of
HS-DPCCH gain factor Power Tol Power Tol
(dBm) (dB) (dBm) (dB)
1/15 ≤ βc/βd ≤ 12/15 +24 +1/-3 +21 +2/-2
13/15 ≤ βc/βd ≤ 15/8 +23 +2/-3 +20 +3/-2
15/7 ≤ βc/βd ≤ 15/0 +22 +3/-3 +19 +4/-2

MAC-hs Round-Trip Loop Timing
• Minimum retransmission delay 12 ms
18 slots = 12 ms 2 slots A = HS-DPCCH L1, MAC-hs,

HS-SCCH L1
2 x Tprop + 15.5 slots A B B = HS-PDSCH L1
HS-SCCH Retransmit
HS-PDSCH Retransmit
2 slots 3 slots
A/N CQI

Rate Matching
• Turbo encoder coding rate = 1/3.
• Rate Matching is used to adapt to the Data
desired coding rate.
• Either puncturing or repetition. Turbo Encoder
• In the example, RM punctures into
rate 3/4. Systematic
Parity 1
• Note: The systematic bits are more
Parity 2
important than parity bits!
Rate Matching (Puncturing)
Systematic
Parity 1
Parity 2

Hybrid ARQ (HARQ): Chase Combining
Turbo Encoder
Systematic
Parity 1
Parity 2
Original transmission Retransmission

Systematic
Parity 1
Parity 2
Chase Combining (at Receiver)
Systematic
Parity 1
Parity 2

Hybrid ARQ (HARQ): Incremental Redundancy
Turbo Encoder
Systematic
Parity 1
Parity 2
Original transmission Retransmission

Systematic
Parity 1
Parity 2
Incremental Redundancy Combining
Systematic
Parity 1
Parity 2

HSDPA Channel Quality Feedback
• This will depend on the location in the cell, expected BTS TX power for HSDPA
(parameter), channel condition & receiver etc. details
High CQI reported (close to BTS, high HSDPA power)

Low CQI reported (far from BTS, low HSDPA power)
High Throughput
Throughput (kbps)
-14 -12 -10 -8 -6 -4 -2 0

Tx Ec/Ior (dB) Low Throughput
Geometry=0dB Geometry=5dB Geometry=10dB

Example CQI Mapping Table
Transport Number of Reference power NIR XRV
CQI value Modulation adjustment ∆
• BTS can map the received Block Size HS-PDSCH
CQI value for the data rate 0 N/A Out of range

0 9600 0
to be used in the link 1 137 1 QPSK
0
adaptation 2 173 1 QPSK
3 233 1 QPSK 0
4 317 1 QPSK 0
• Necessary conversion to be 5 377 1 QPSK 0
done depending on BTS 6 461 1 QPSK 0
power availability 7 650 2 QPSK 0
8 792 2 QPSK 0
0
• Reference power 9 931 2 QPSK
0
adjustment used when 10 1262 3 QPSK
11 1483 3 QPSK 0
quality would allow higher
12 1742 3 QPSK 0
rate than UE capability
13 2279 4 QPSK 0
14 2583 4 QPSK 0
15 3319 5 QPSK 0
16 3565 5 16-QAM 0
17 4189 5 16-QAM 0
(continues until 31…)

HSDPA & Soft Handover
• In case of DCH all data is sent from all active set BTSs
• In case of HSDPA, HS-DSCH sent from one BTS only, associated DCH (can be
low rate if only signaling) from all cells
RNC RNC
DCH + Iub
Iub HS-DSCH
DCH Node B
Node B
DCH DCH
Node B Node B

HSDPA & Soft Handover (cont.)
• The intra-frequency measurement event ID is modified
• Now a measurement report will be initiated when the best serving cell changed
(parameters to have some hysteresis)
• This is needed to initiate the HS-DSCH serving cell change even when active set is
unchanged
• In case serving cell change, RLC layer (in the RNC) will handle unfinished ARQ
processes when Node B memory is flushed.
DCH +
HS-DSCH
Node B
DCH
RNC
Iub
Node B

HS-DSCH vs. DSCH
• DSCH of Release’99 uses variable spreading factor and fast power control
(otherwise like DCH)
• Principle agreement also to remove DSCH from Release 5 and onwards
from 3GPP specifications as part of feature clean-up (CRs for 06/05 specs)
• HS-DSCH of Release 5 uses adaptive modulation and coding and L1 Hybrid
ARQ
Feature DSCH HS-DSCH
Variable spreading factor Yes No
Fast power control Yes No
Adaptive modulation and coding No Yes
Fast L1 HARQ No Yes

HSDPA & DCH Resource Sharing
Node-B Tx power
Power measurements Max power
from the Node-B to
the RNC Power control head-room
PtxTarget
Total transmitted
carrier power
HSDPA NRT
NEW non-HSDPA Controllable power
power measurements
DCH NRT
DCH RT
In addition to power Non-controllable power
also code resource
shared! Common channels

HSDPA vs DCH Code Space Usage
• With Downlink DCH Time multiplexed DPCCH and DPDCH
• Variable rate with DTX -> Code space not released due inactivity
• Problematic for high bit rates -> Current highest DL rate 384 kbps
FULL RATE
Data TPC TFCI Data Pilot
DPDCH DPCCH DPDCH DPCCH

Slot 0.667 ms = 2/3 ms
HALF RATE
Data TPC TFCI Data DTX Pilot
DPDCH DPCCH DPDCH DPCCH

Slot 0.667 ms = 2/3 ms

HSDPA vs DCH code space usage (cont.)
• With HSDPA code resource (except what is needed for DCH) shared with 2 ms
resolution -> Optimum code resource use
• Also no soft handover related extra code use
...
C3(0) = [ 1 1 1 1 1 1 1 1 ]
... = Allocated code
...
C2(0) = [ 1 1 1 1 ] ...
C3(1) = [ 1 1 1 1 0 0 0 0 ]
... = Code which cannot
... be allocated at the same
...
C1(0) = [ 1 1 ]
C3(2) = [ 1 1 0 0 1 1 0 0 ]
... time as C3(1)
C2(1) = [ 1 1 0 0 ] ...
C3(3) = [ 1 1 0 0 0 0 1 1] ... = Code which can
C0(0) = [ 1 ] ...
...
be allocated at the same
C3(4) = [ 1 0 1 0 1 0 1 0 ] ... time as C3(1)
...
C2(2) = [ 1 0 1 0 ]
...
C1(1) = [ 1 0 ] C3(5) = [ 1 0 1 0 0 1 0 1 ] ...
...
...
C3(6) = [ 1 0 0 1 1 0 0 1 ]
These codes cannot
. ...
.. be used at the same
C2(3) = [ 1 0 0 1 ]
...
...
time as C3(1)
Spreading factor: C3(7) = [ 1 0 0 1 0 1 1 0 ]
...
SF = 1 ...
SF = 2 SF = 4 SF = 8
HSDPA & Iub
• HSDPA improves Iub efficiency compared to Release’99 packet data since HSDPA is
a time shared channel with a flow control in Iub
• Release’99 requires dedicated resources from RNC to UE. Those resources are not
fully utilized during TCP slow start, during data rate variations or during inactivity
timer
• Additionally, HSDPA does not use soft handover ⇒ no need for soft handover
overhead in Iub
Iub link 1 1 2 HSDPA Iub

capacity
Iub link 2 1 2
Iub efficiently
utilized by HSDPA
= User 1 1 = TCP slow start
= User 2 2 = Inactivity timer
= User 3
HSDPA & Iub (Cont.)
• The needed Iub capacity is NOT
equal to air interface peak rate
(e.g. 1.8 or 7.2 Mbps) 80% power and 15 codes allocated to HSDPA service
1
• The momentary data rate over 2
ms can be higher than the Iub 0.9
Cumulative distribution function [-]

capacity available, as BTS has 0.8 Macrocell/Veh A/3kmph
buffers and is scheduling to 0.7
multiple users Average data
0.6
• Iub loading thus more related to rate avaible
0.5
the actual air interface capacity
0.4
0.3 Microcell/Ped A/3kmph
0.2
0.1
0
0.01 0.1 1
Instantaneous (per 2 ms) user throughput [Mbps]

HSDPA - Summary
• Multi-code operation combined with lower coding rates and fast HARQ
improves link performance at cell edge (low SIR)
• Multi-code operation combined with increased coding rates (e.g. 3/4) fully
utilize favorable radio environments (high SIR) without running into code
shortage.
• HSDPA is backwards compatible and can be introduced gradually in the
network.
• Retransmission and scheduling into Node B
• -> reduces (re-)transmission delays; Improves QoS control.
Freely configurable transmission

HSDPA is a natural capacity evolution to WCDMA
and an enabler for higher speed data services

HSDPA Release 6 improvements
• The following items are added in Release 6 specifications
• Fractional DPCH
• To avoid need for full DCH in downlink when only PS
data (SRB in HS-DSCH), shared DL channel to provide
uplink TPC commands
• Pre/Post scheme
• To avoid DTX detection in BTS for ACK/NACK
commands -> smaller power offsets for the ACK/NACK –
> better uplink range
• RX diversity and improved receiver performance
• Latter still on-going
• L2/L3 Signaling improvements on-going as well….
• Proposed e.g. combined active set update and HS-DSCH
serving cell change
• Mandatory for a HSDPA capable Release 6 UE, RX diversity
and improved receiver optional from the spec …

HSDPA Performance

HSDPA RLC Layer Data Rates
• Max RLC layer throughput shown below
• Max application layer throughput can be very close to RLC throughput
• Difference <5% mainly due to IP headers
RLC blocks Transport Max RLC data

UE category # of codes Modulation
per 2 ms TTI1 block1 rate
12 5 codes QPSK 10 x 320 3440 1.6 Mbps
5/6 5 codes 16-QAM 21 x 320 7168 3.36 Mbps
7/8 10 codes 16-QAM 42 x 320 14155 6.72 Mbps
9 15 codes 16-QAM 60 x 320 20251 9.6 Mbps
10 15 codes 16-QAM 83 x 320 27952 13.3 Mbps
1RLC block size of 320 bits assumed

2Includes user plane + RLC headers + MAC headers + padding

Nokia HSDPA RAN Measurements

Nokia HSDPA RAN Throughput [kbps]
• Application throughput matches with the theoretical calculation
• >1.5 Mbps measured with FTP download
1.8 Mbps Throughput [kbps]

2000 5-code QPSK
1800 1.6 Mbps 1.53 Mbps
1600
1400
1200
1000
800
600
400
200
0
L1 throughput RLC throughput Application Application
(theory) (theory) throughput throughput
(theory) (measured)
Nokia HSDPA RAN Latency [ms]
• Measured round trip time 94 ms with 20-ms uplink TTI
• Approx 20 ms faster expected with 10-ms uplink TTI
Measured with Ubinetics
200
180 Calculated
Measured
160
140 94 ms measured
120 with 20-ms uplink
ms
100
80
60
40
20
0
RAN1.5ED2 RAN04 (20- RAN04 (20- RAN04 (10- 3GPP R5 3GPP R5 3GPP R6
ms UL+DL) ms UL 10-ms ms UL+DL) HSDPA (20- HSDPA (10- HSUPA (2-
DL) ms UL 2-ms ms UL 2-ms ms UL+DL)
DL) DL)
System Control Algorithms

Link Adaptation and Power Control
• HS-DSCH link adaptation has typically two loops
• A) Inner loop based on CQI reports from UE
• B) Outer loop in Node-B to control the BLER of the inner loop
• HS-SCCH power control has typically two loops as well

• A) Inner loop based on the fast power control commands from UE
• B) Outer loop in Node-B to control the BLER of the inner loop
• These algorithms are not standardized
HS-DSCH link adaptation
HS-SCCH power control

Link Adaptation

A Two-Step HS-DSCH Link Adaptation (1)
• Inner loop algorithms
• LA estimates based on UE feedback information, i.e. CQI reports.
• LA estimates based on Node-B measurements = UE power control commands
• Hybrid schemes using both UE/Node-B measurements.
• Outer loop algorithms

• The goal is to compensate for any bias introduced by the inner loop algorithm.
• Bias might be introduced due to offsets in relative UE performance caused by improved
receiver architecture, etc.
• The outer loop is based on Ack/Nack.
• The outer loop controls the residual BLER after 1st retransmissions (=2nd transmission)
• The 1st retransmission is used to take into account the gain from HARQ.

A Two-Step HS-DSCH Link Adaptation (2)
RNC Node-B
CQI Outer loop Inner loop HS-DSCH

settings LA algorithm LA algorithm
Handover
control
UL HS-DPCCH CQI PDCH
detection

CQI Based Inner Loop Procedure
• Step 1: CQI offset compensation
• Compensate for HS-PDSCH transmit power mismatch, if the CQI report at the UE is
derived for a different power level than the one used at the Node-B.
• Step 2: Mapping of CQI report to feasible LA estimate

• The offset compensated CQI report may not correspond to a feasible LA estimate, if for
instance the number of suggested multi-codes exceeds the number of HS-PDSCH multi-
codes available at the Node-B.
• Step 3: Transport block size adjustment

• Adjust the transport block size for the feasible LA estimate according to the number of
available bits to be transmitted to the UE, i.e., perform a simple “rounding” operation.

Outerloop Algorithm Based on Ack/Nack's
Start
Increase set-point if:
Set A equal to the Nack on 2nd trans.
predefined initial value
Decrease set-point if:
Ack on 1st or 2nd trans.
Ack
received from first Yes
transmission of
Ratio between up/down step

block ?
No determines the residual BLER,

I.e. similar as conventional
Ack
outerloop power control.
Increase A No received from first Yes Decrease A
by "AStepUp" [dB] re-transmission of by "AStepDown" [dB]
block ?

HS-SCCH Power Control

HS-SCCH PC Summary
RNC Node-B
P0 /P1
HS-SCCH or HS-SCCH
HSDPA power offset Outer loop β Inner loop transmit power
offset PC algorithm PC algorithm
Handover SHO: On\Off

control
UL HS-DPCCH CQI PDCH
detection
Inner loop
based on CQI

Outer Loop PC for the HS-SCCH
• The outer loop for HS-SCCH is similar to the standard outer loop PC algorithm
for dedicated channels.
• Uplink detection of DTX on the HS-DPCCH (when expecting an Ack/Nack) is
assumed to indicate that the HS-SCCH has been erroneously decoded.
• Algorithm
• DTX received : Increase target with Pup decibels
• Otherwise : Decrease target with Pdown decibels
• The outer loop algorithm is UE specific
• Given this approach, the HS-SCCH average BLER converges to
1
BLER =
Pup
+1
Pdown

System Performance and Simulations

HSDPA Performance
Link
Linkperformance
performance How far from Shannon limit?
Macro
Macrocell
cell
performance What can be achieved in macro cells if
performance––single
single all resources given to single user?
user
userper
percell
cell
Scheduler
Scheduler
performance How cell resources can be shared
performance–– between simultaneous users?
multiple
multipleusers
usersper
percell
cell
Application
Application
performance What is e2e application performance
performance––end
end over HSDPA?
user
userview
view

HSDPA Link Performance with Turbo Coding
Approaches Shannon Limit
Higher bit rates can be obtained only with more
antennas (MIMO) and/or wider bandwidth.
Supported effective data rate [Mbps]
10.0 Shannon limit:

3.84MHz*log2(1+C/I)
QPSK 16QAM
1.0
HSDPA link
adaptation curve
0.1
15 HS-PDSCH allocation
(Rake, Pedestrian-A, 3km/h)
0.01
-15 -10 -5 0 5 10 15 20
Instantaneous HS-DSCH C/I before processing gain [dB]
HSDPA Bit Rates
80% power and 15 codes allocated to HSDPA service
1
0.9
Cumulative distribution function [-]
0.8 Macrocell/Veh A/3kmph

0.7
Mean bit rate
0.6 1.5 Mbps in
macro cells
0.5
0.4
0.3 Microcell/Ped A/3kmph

Mean bit rate
0.2 >5 Mbps in
0.1 micro cells
0
0.01 0.1 1 10
Instantaneous (per 2 ms) user throughput [Mbps]
Bit Rate Coverage – Interference Limited Case
3 parallel users in WCDMA and in HSDPA
2000
HSDPA2100
1800 Average
Averagedata
datarates
rates WCDMA2100
HSDPA2100
HSDPA2100 19201920kbps
kbps(1
(1user)
user) EDGE900
1600 HSDPA2100 640 kbps (3 users)
HSDPA2100 640 kbps (3 users)
1400
WCDMA2100
WCDMA2100 250 250kbps
kbps(3
(3users)
users)
EDGE900
EDGE900 140 kbps
140 kbps
1200
kbps
1000
800 HSDPA2100
(3 users)
600
400 WCDMA2100 (3 users)

200 EDGE900
0
-100 -98 -96 -94 -92 -90 -88 -86 -84 -82 -80
CPICH RSCP [dBm]

HSDPA Coverage – Interference Limited
8000
Single user assumed on HS-DSCH
7000
7.2 Mbps 2-rx
6000 equalizer other
cells fully loaded
5000 Average data
rate 1-3 Mbps 7.2 Mbps 2-rx
equalizer other
kbps
4000
cells low loaded
3000
2000
3.6 Mbps 1-rx
1000 Rake with other
cells fully loaded
0 Advanced
terminals push
Base station data rates higher
Cell edge

Average HSDPA Bit Rates with Shared R99
Carrier
Average user data rate
Single user assumed on HS-DSCH
3000
10-code, 2-eq 0.5-1.5 Mbps in
2500 10-code, 1-eq macro cells if carrier
shared with R99
2000 5-code Rake
kbps
1500
1000
500
0
2 4 6 8 10 12
HS-DSCH power [W] out of 16-W BTS power

Packet Scheduling Strategies
Operator adjustable slopes for
Min. target Throughput

Fair Throughput
different service and user classes
Tradeoff between cell Fair time
throughput, coverage C/I based
and user fairness
Spectral Efficiency
Throughput Throughput coverage of Throughput coverage of

high C/I based scheduling fair throughput scheduling
low

Low coverage of high data rates
Packet Scheduling Strategies
PS Method Scheduling rate Serve order Allocation method

Fair throughput Slow Round robin in Resources according to same
(FT) (avg. over 20-100ms) random order throughput (up to max. alloc. time)
Fair resource Slow Round robin in Same resources (time/power/

(FR) (avg. over 20-100ms) random order codes) per allocation time
Served according to highest
C/I based Slow Same resources (time/power/
*) Note that
(CI) actual resource allocation
(avg. over 20-100ms) will be heavily
slow-averaged influenced
channel by QoS/delay requirements
codes) per allocation time
and user prioritization schemes! quality
Max C/I based Fast Same resources (time/power/
*) Note that
(M-CI) actual resource allocation
(Per-TTI basis) will be heavily
instantaneous influenced
channel by QoS/delay requirements
codes) per allocation time
and user prioritization schemes! quality
Proportional Fair Fast Resources according to same
relative instantaneous
throughput (P-FT) (Per-TTI basis) throughput (up to max. alloc. time)
channel quality (RICQ)
Proportional Fair Fast Same resources (time/power/
relative instantaneous
resource (P-FR) (Per-TTI basis) codes) per allocation time
channel quality (RICQ)

Multi-user Diversity (Fast Scheduling)
Node-B scheduling can
Channel quality utilize information on the
(CQI, Ack/Nack, TPC) instantaneous channel
conditions for each user.
Data
UE1 TTI 1 TTI 2 TTI 3 TTI 4

Scheduled user
Multi-user selection diversity
(give shared channel to “best” user)
Channel quality
(CQI, Ack/Nack, TPC) Data
UE2 USER 2 Es/N0 USER 1 Es/N0

Proportional Fair Algorithm
• Principle is to schedule the user who currently has the highest ratio of instantaneous
throughput to average throughput. The averaging time is typically a few 100 ms.
• The user with the highest selection metric at a given time is selected for scheduling
in the following TTI
Rk [n]
Mk ≡ Rk = instantaneous supported data rate for user k
Tk [n] Tk = average throughput for user k

Proportional Fair Scheduling as a Function of
Number of Users
• Significant gain 2.4
from proportional 2.2
fair scheduling if at
of PF PS over FR PS [dB]
least 3-5
Avg. cell capacity gain
2
simultaneous users.
1.8
1.6
1.4
1.2
Macrocell/Ped-A (3km/h), PCDE=-36dB
1 Macrocell/Veh-A (30km/h), PCDE=-36dB
Microcell/Ped-A (3km/h), PCDE=-36dB
0.8
0 5 10 15 20 25 30
User diversity order, UDO [-]

HSDPA Cell Throughput
Dynamic System Simulation Macro Cells Vehicular A Channel
4500
Round robin 5 codes
4 Mbps
4000
Round robin 10 codes
3500 Proportional fair 5 codes
Proportional fair 10 codes
3000
Proportional fair 15 codes
2500
2 Mbps
kbps
2000
1500
1 Mbps
1000
500
0
Rake 1-ant Equalizer 1-ant Rake 2-ant Equalizer 2-ant
• 5-code BTS and single antenna UE Rake provides 1 Mbps

• 10-code BTS and single antenna UE provides 2 Mbps
• 15-code BTS and dual antenna UE provides 4 Mbps
Transport Block Size Selection Statistics
10 HS-PDSCH codes 16-QAM selection
probability <5%
in macro cells
16-QAM selection
probability 25%
in micro cells
Break point for

16QAM selection

Co-Existence of R99 and HSDPA

Co-existence of R99 and HSDPA
= R5 HSDPA • HSDPA can be introduced to the network with shared or
= R99 DCH with dedicated frequency
• Carrier shared between HSDPA and R99

f1
f1 • Operator definable or dynamic resource sharing between
HSDPA and R99
f2
f2 • Dedicated HSDPA carrier
f1 • HSDPA UE directed to HSDPA carrier
f1
f2
f2 • HSDPA carrier, which can also be used for R99 traffic in
case of R99 high load
f1
f1 • UE moved by RRC connection setup or by handovers

HSDPA and Iub Capacity

HSDPA Improves Iub Efficiency by 50-100%
• In total, HSDPA improves Iub efficiency 50-100% compared to Release’99
• HSDPA requires more E1 lines? Yes, if we want to show higher peak rates. 2 x E1
is required to provide peak rate of 2 Mbps and 3 x E1 for 3.6 Mbps.
• HSDPA can be operated with 1 x E1? Yes, and it even improves Iub efficiency but
the peak data rate will be approx 1 Mbps. Also, the operator may want to provide a
minimum HSDPA throughput and single E1 is not enough in that case.
E1 capacity
Iub capacity
requirement Inactivity
Inactivity
Soft
SoftHO
HO
HSDPA
HSDPA
user
userdata
data
Release’99
Release’99
user
userdata
data
Common
Commonch
ch Common
Commonch
ch
DCH HSDPA
Trade-off Between HSDPA RF and Iub
Capacity
HSDPA RF vs Iub efficiency
100%
95%
90%
RF utilization [%]
85%
Iub utilization [%]
80%
75%
70% High Iub efficiency High RF efficiency
(95%) requires some (95%) requires some
65% overhead (15%) in air overhead (25%) in Iub
interface dimensioning dimensioning
60%
2.0 2.2 2.4 2.6 2.8 3.0 3.2 3.4 3.6 3.8
Iub capacity for 1+1+1 site [Mbps]
End User Capacity and Cost

HSDPA Enables Mass Market >1 GB/Sub/Month
1-carrier HSDPA assumed
2.5
HSDPA 2-rx UE
HSDPA 1-rx UE
2.0
1 GB/month for
GB/sub/month
1.5 300-600 subs
1.0
0.5
0.0
300 400 500 600 700 800 900 1000
Subscribers per site
HSDPA with 1rx UE 2.0 Mbps/cell
HSDPA with 2rx UE 3.6 Mbps/cell
Busy hour share 20%
Busy hour utilization 80%
Spectrum 2 x 5 MHz = 1 carrier dedicated for HSDPA
Cost of Data Delivery (Network Capex)
Delivery cost of downloaded GB

5.0
4.5
4.0 <4 €/GB data
[EURO €/GB]
3.5
3.0
2.5
2.0
1.5
1.0
0.5
0.0
14 16 18 20 22 24 26 28 30 32 34 36 38 40
Depreciation over 6 years Price per TRX [k€]
Other assumptions from previous slide

VoIP over HSPA

VoIP Usage Growing Fast in Fixed Internet
• Close to 100 M
downloads
and counting...
• Also Pocket PC
version, ca. 2 MB

VoIP Drivers and Challenges in Cellular
• Drivers
1. Enterprise VoIP extension to wide area
2. Rich call interworking
3. Plain vanilla VoIP for network simplicity
• Challenges
1. End-to-end delay capability
2. Bandwidth and delay during high load
3. Efficiency in the air interface and Iub
BTS RNC SGSN/GGSN

Potential VoIP Capacity on HSDPA
• HSDPA VoIP can increase voice capacity – but at the expense of end-to-end delay
• 80-150 ms was allowed for queuing and transmission in the results below, which
causes >250 ms worst case mobile-to-mobile delay
• At maximum load HSDPA VoIP delay was about 100 ms more than in CS voice.
During low load e2e delay with HSDPA VoIP is slightly less than with CS voice
AMR 12.2 kbps voice users per cell
120 Queuing +
transmission
100 delay in downlink
Voice users
80
150 ms delay
60
80 ms delay
40
20
0
R99 CS voice HSDPA VoIP with HSDPA VoIP with
round robin proportional fair

Radio Technology Evolution
VoIP feasible from e2e
performance point of view
End user bit rate
[kbps]
HSPA ADSL
1-2 Mbps 1-2 Mbps
3 50-100ms <50ms
Mbps
1
Mbps EVDO Rev 0
400 kbps
300 EGPRS, Rel. 99 200-300 ms WCDMA, R99
kbps 100-200kbps 200-300kbps
500-700ms 150-200ms
100
kbps EGPRS, Rel. 4
GPRS 100-200kbps
30 500-700ms 200-500ms
kbps 40kbps
600 500 400 300 200 100 0

Round trip time [ms]

Conclusions on HSDPA Performance
• End user capabilities
• Peak data rate 3.6 – 14.4 Mbps
• Macro cell data rates 1.0-2.5 Mbps with dedicated carrier and 0.5-1.5 Mbps when shared
carrier with R99
• Latency <100 ms
• Simultaneous CS voice + PS data on the same connection
• Capacity and cost

• Cell throughput 2 Mbps/carrier
• User capacity 1 GB/month/subscriber for 300-600 subs/site
• Delivery cost <4 €/GB for network capex
• Integration with WCDMA

• HSDPA can co-exist on the same carrier as WCDMA
• WCDMA integrates efficient voice network to the low latency high bit rate HSDPA
network

Mobile Broadband Access Landscape
Wireless DSL Mobile premium
Fixed Flat rate Cellular Value added services
broadband
wireless 802.16 EDGE, WCDMA, cdma
802.16e EV-DO
HSDPA
Mobile broadband
wireless access
Proprietary
Proprietary extensions
Flarion
LAN
802.11 WiFi

Technology Positioning - Use Cases
1 Fixed BWA “Wireless DSL”
• User uses wireless broadband service from fixed location, home or office,
in similar way as DSL or cable modem access
• Usually requires non-movable, outdoor antenna for coverage
2 Portable BWA “Laptop/PDA access from park”

• User uses wireless broadband service from any location within coverage
area
• Mobility of the user between cells is not supported (no handovers)
• Use case is very similar to that of hot spot WLAN access
3 Mobile BWA “Smart phone access from car”
• User uses wireless broadband service from any location within coverage
area including the mobility of the user (e.g. up to 250 km/h)
• Use case is very similar to that of 3G cellular data

Spectrum
= Expected bands for 802.16
= WCDMA/HSPA band with products today
= WCDMA/HSPA band - future
5 GHz Unlicenced Smallest

coverage
3.4 GHz Fixed wirelss access band in Europe
2.6 GHz 190 MHz New 3G band in Europe by 2008
2.5 GHz 190 MHz MMDS in USA
2.1 GHz 2x60 MHz Mainstream

. WCDMA
.
1900 2x60 MHz US PCS band
1700 2x45 MHz New USA 3G band by 2006
1800 2x75 MHz Europe and Asia
900 2x35 MHz Europe and Asia
850 2x25 MHz Americas, Japan, Asia Best coverage

HSDPA and EV-DO
• HSDPA and EV-DO have similar technical solutions, which is leads to similar
spectral efficiency for best effort data
• Fast retransmissions
• Hybrid ARQ
• Adaptive modulation and coding
• HSDPA allows simultaneous voice and packet data

• Simultaneous CS voice + PS video possible in HSDPA
• EV-DO Rev.A must use VoIP to carry voice
• HSDPA has higher bandwidth, which brings high user bit rates
• EV-DO downlink typical bit rate during low loading 300-500 kbps
• HSDPA downlink typical bit rate during low loading 1-2 Mbps

WCDMA High Speed Uplink Packet Access
(HSUPA) of Release 6
Reference: WCDMA for UMTS, 3rd edition, Chapter 11

Outline
• HSUPA Introduction
• HSUDA Protocol Architecture
• HSUPA Retransmissions
• HSUPA Peak Bit Rates
• HSUPA UE Capabilites
• HSUPA Channel Stuctures Uplink and Downlink
• Summary

High Speed Uplink Packet Access HSUPA
• Peak data rates increased to significantly higher than 2 Mbps;
Theoretically reaching 5.8 Mbps
• Packet data throughput increased, though not quite high
numbers expected as with HSDPA
• Reduced delay from retransmissions.
• Solutions
• Layer 1 hybrid ARQ
• Node B based scheduling for uplink
• Frame sizes 2ms & 10 ms
• Schedule in 3GPP
• Part of Release 6
• First specifications version completed 12/04
• In 3GPP specs with the name Enhanced uplink DCH (E-DCH)

HSUPA Status in 3GPP
• Study item for 3GPP Release 6 completed 03/04
• First versions of HSUPA specs published 12/04
• Work item completion date 03/05
• Remaining open issues closed 06-09/05
2003 2004 2005 2006 2007

3GPP study item
Study item 1st version in Official work item
completed 3GPP spec completion date

HSUPA Protocol Architecture
• New MAC entity, MAC-e added to the Node B
• In RNC MAC-es handling packet in-sequence delivery & soft handover combining
• Layers above, such as RLC, unchanged -> this required MAC-es to perform
reordering for packets
UE
Node B SRNC
NAS
RLC
RLC
RLC MAC-d
MAC MAC-es Iu
MAC-es/e MAC-e FRAME FRAME
PROTOCOL PROTOCOL
WCDMA L1 WCDMA L1
TRANSPORT TRANSPORT
Uu Iub/Iur
HSUPA user plane

Node B Controlled HSUPA Scheduling
New Node B functions:
Uplink packet data scheduling
HARQ control: ACK/NAKs
New L1
signalling ACK/NAK Mac-e
+ control
Mac-es
Iub
Data packet
Node B RNC
+ possible retransmissions
UE
+ control for scheduling New Iub signalling
• Target is to shorten the packet scheduling period ⇒ packet scheduler is able to

track burstiness of source application

Fast Scheduling Reduces Noise Variance
• Faster scheduling reduces PDF of the NR per BTS
0.7
noise rise variations Mean: 5 (dB)
RNC sheduling
Node B scheduling
StD: 0.72 (dB)
⇒ Less headroom needed 0.6
Mean: 4.1 (dB)
⇒ Cell capacity and user data StD: 1.2 (dB)
rates are increased 0.5

Operation point can
be increased because
• With low loaded uplink, the 0.4 variance is reduced.
users may get significantly
higher data rates as much
0.3
more aggressive data rates
can be granted to UEs
0.2
0.1
0
0 1 2 3 4 5 6 7 8 9 10
NR [dB]

DCH vs E-DCH Retransmissions
DCH E-DCH
RNC
Combining of
packet and
Packet Retransmission retransmission
Packet
(1st TX) Retransmission
BTS
L1 ACK/NACK
RLC ACK/NACK
Terminal

Fast Hybrid-ARQ between UE and BTS
• Fast ACK/NAK from BTS
• N-process Stop-And-Wait (SAW) HARQ (similar to HSDPA)
• short round trip delay => lower total delay
• Chase combining or Incremental Redundancy, soft buffering in BTS
• In SHO, each BTS sends ACK, retransmission if no ACKs
HARQ control and

soft combining AC
K/N
AK
E-D
CH
dat
a
E-DCH data
ACK/NAK
RNC Correctly BTS UE
received packet

RNC
Feedback from UE to BTS/RNC
• For the RNC UE provides the following information (MAC layer)
• UE buffer occupancy: how much data buffers
• Available transmission power resource
• For the BTS, the following is provided on E-DPCCH (L1)

• Information of the data rate for the frame (E-TFI) MAC-PDU
• Information of the redundancy version for the packet BTS
• Timing is known thus BTS knows which ARQ channel to
expect
• Happy bit: Is the current data rate satisfactory
• UE would not be happy of the data rate if it could transmit
with higher rate due: E-DPCCH
– Transmission power left
– Data left in the buffers (for more than X TTIs, X as
parameter)

Adaptive Modulation – Why not with HSUPA?
• In the downlink direction, BTS has limited power control dynamics, in the order of
10-20 dB
• However in the uplink received power level is kept constant with fast closed loop
power control with more than 70 dB dynamic range
• Thus there are no times when there would be “free lunch” to use higher order
modulation
• Other reasons why higher order modulation sounds interesting*…

• A) To get more bits per given bandwidth - > range problem
• B) To reduce the terminal peak to average ratio as having multicodes in use later ->
This would have resulted to higher average power even if the PAR would have
been smallel -> less capacity
* When searching from the web HSUPA info, often one sees adaptive modulation
as part of the story. This is based on the outdated stuff from the study item phase
HSUPA - UE Categories
• HSUPA uses BPSK modulation with multicode transmission to achieve high data
rates, 6 different UE categories defined, key element number of codes supported
and whether 2 ms TTI is supported or not
• Theoretical peak bit rate up to 5.76 Mbps
• 1.46 Mbps capability expected initially
HSUPA Transport
Codes x Spreading TTI Data rate
Category Block size
1 1 x SF4 10 7296 0.73 Mbps
2 2 x SF4 10 14592 1.46 Mbps
2 2 x SF4 2 2919 1.46 Mbps
3 2 x SF4 10 14592 1.46 Mbps
4 2 x SF2 10 20000 2 Mbps
4 2 x SF2 2 5837 2.9 Mbps
5 2 x SF2 10 20000 2 Mbps
6 2xSF2 + 2xSF4 10 20000 2 Mbps
6 2xSF2 + 2xSF4 2 11520 5.76 Mbps
HSUPA Channel Structure - Uplink
• E-DPDCH, (E-DCH Dedicated Physical
Data Channel)
- carries the user data in the uplink ced,1 β ed,1 iqed,1
direction, with the peak rate reaching E-DPDCH1
up to 5.76 Mbps .
.
- codes are not shared with HSUPA (no .
code shortage in the uplink) . ced,k β ed,k iqed,k
E-DPDCHk
• E-DPCCH (E-DCH Dedicated Physical
Σ
Control Channel ) .
I+jQ
.
- Parallel physical layer control channel .
Se-dpch
- carrying e.g. ARQ information needed . ced,K β ed,K iqed,K
for the BTS decoding process + UE tx E-DPDCHK
buffer status
cec β ec iqec
- Normal DCH operated in parallel E-DPCCH
(DPCCH always and DPDCH if there is
data)

HSUPA Channel Structure – Uplink (cont)
• With E-DPDCH, there are two transmission time intervals (TTIs):
a) 10 ms TTI (DCH has 10, 20, 40 and 80 ms)
- Best for range point of view, typically better capacity than 2 ms
b) 2 ms TTI
- Suffers in range, thus with larger cells not usable close to cell edge
- Can be used to delay reduction
• E-DPDCH uses multicode transmission

• Up to 4 parallel codes (see next slide)
E -DPDCH Data
N data bits
T = 2560 chips, N = 1 0*2 k+2 bits (k=0...5)

slot data
Slot #0 Slot #1 Slot #2 Slot #i Slot #14
1 subframe = 2 ms
1 radio frame: T = 10 ms

HSUPA Channel Structure – Uplink (cont)
• The smallest data rate with single SF 4 code
• Then two SF 4 codes
• Then two SF 2 codes
• And highest data rate with 2 times SF 2 & 2 times SF 4 (Highest PAR)
• Compare to Release’99 where after reaching SF 4 (e.g. 384 kbps),

higher data rates would be by adding more SF 4 codes (up to 6)
E-DPDCH slot formats
Slot Format Channel SF Bits/ Bits/ Bits/Slot
#i Bit Rate Frame Subframe Ndata
(kbps)
0 60 64 600 120 40
1 120 32 1200 240 80
2 240 16 2400 480 160
3 480 8 4800 960 320
4 960 4 9600 1920 640
5 1920 2 19200 3840 1280

E-DCH Coding
• One transport block once per TTI aim1 ,aim2 ,aim3 ,...,aimA
• CRC attachment: 24 bit CRC CRC attachment
• Code block segmentation similar to the rel’99/4/5 bim1 ,bim2 ,bim3 ,...,bimB
DCHs, the value of maximum code block size is
5114 for turbo coding Code block segmentation
• Channel coding: rate 1/3 turbo coding (as rel’99) oir1,oir2,oir3,...,oirK
• Physical layer HARQ functionality and rate Channel Coding
matching: SF and number of needed E-DPDCHs ci1,ci2,ci3,...,c i E

are determined (similar to rel’99/4/5, but different
Physical Layer Hybrid-ARQ
parameters) and the physical layer HARQ functionality/Rate matching
functionality (see next slide)
s 1,s 2,s 3,...,s R
• Physical Channel Segmentation: similar to the Physical Channel
rel’99/4/5 DCHs, when more than one E-DPDCH Segmentation
is used, physical channel segmentation distributes up,1 ,up,2 ,up,3 ,...,up,U(p)
the bits among the different physical channels
Interleaving &
• Interleaving and physical channel mapping: similar Physical channel mapping
to the rel’99/4/5 DCHs, rate matching output bits
are interleaved and mapped to the allocated E- Physical channel(s)
DPDCH(s)
Transport channel processing for E-DCH
E-DCH Channel Coding (cont.)
• Bit separation (similar to rel’99/4/5 turbo coded DCHs)

• Rate matching (similar to rel’99/4/5 DCHs)
• PLmax is equal to 0.44 for all E-DCH UE categories except the highest E-DCH
UE category, for which PLmax is equal to 0.33
• Parameters depend on the redundancy version (RV) parameters s and r similar to
HS-DSCH HARQ second rate matching stage
• Higher layers (RNC) configure, if only RV=0 is used or if RV can be 0, 1, 2 or 3
• Bit collection, similar to HS-DSCH HARQ

Rate Matching
Systematic
bits Nsys Nt,sys
RM_S
Parity 1
Ne,j bits Np1 Nt,p1 Ne,data,j
bit bit
RM_P1_2
separation collection
Parity2
bits Np2 Nt,p2
RM_P2_2
E-DCH hybrid ARQ functionality

E-DPCCH Coding
• Control information on E-DPCCH is multiplexed: xrsn,1, xrsn,2 xtfci,1, xtfci,2,..., xtfci,7 xh,1
•E-TFCI information (7 bits)
•Retransmission sequence number (RSN, 2 bits)
•‘Happy bit’ (Rate Request, 1 bit)
Multiplexing
• Channel Coding: a sub-code of the second order
Reed-Muller Code (similar to rel’99/4/5 TFCI x1, x2,..., x10
coding)
Channel
• Physical Channel Mapping: similar to rel’99/4/5, Coding
channel coding output bits are mapped to the z0, z1,..., z29
allocated E-DPCCH
Physical
channel
mapping
E-DPCCH
Coding chain for E-DPCCH

HSUPA Channel Structure - Downlink
• The following downlink control channels are defined
• E-RGCH (E-DCH Relative Grant Channel)
• Relative grants, to set data rate up/down or hold constant
• E-AGCH (E-DCH Absolute Grant Channel)
• Absolute grants, not only up/down
• E-HICH (E-DCH HARQ Acknowledgement Indicator Channel)
• Information on the packet transmission station (ACK/NACK)
• Shares the same code with E-RGCH
• E-RGCH and E-HICH share the same SF 128 code

• For one UE only one is relevant but single code can serve serveral UEs
bi,0 bi,1 bi,39
Tslot = 2560 chip
1 subframe = 2 ms
1 radio frame, T f = 10 ms

E-HICH (E-DCH Hybrid ARQ Indicator
Channel)
bi,0 bi,1 bi,39
Tslot = 2560 chip
1 subframe = 2 ms
1 radio frame, Tf = 10 ms
• E-DCH hybrid ARQ acknowledgement indicator a is mapped on E-HICH:

• ACK: +1
• NACK: –1 in cells belonging to the same Radio Link Set (RLS) as the E-DCH
serving cell and
0 in other cells (DTX)
• When Node B has not detected E-DPCCH in uplink, no ACK/NACK is transmitted in
the downlink
• ACK/NACK is transmitted using 3 (for 2ms E-DCH TTI) or 12 (for 10ms E-DCH
TTI) consecutive slots

E-RGCH (E-DCH Relative Grant Channel)
• The E-DCH relative grant (RG) a is mapped on E-RGCH:
• UP: +1 (possible only in serving E-DCH RLS)
• HOLD: 0 (Note: 0 means DTX, i.e, that HOLD is not transmitted)
• DOWN: –1
• An orthogonal signature sequence Css,40,m(i),j is assigned to the E-RGCH by higher layers
• One slot long orthogonal signature sequence is different in each slot of a 2ms sub-frame
• Higher layers define the sequence pattern
• The orthogonal signature sequence is used to identify the E-RGCH from the other E-RGCHs and E-HICHs
(to different UEs) transmitted on the same SF=128 channelisation code channel (there can be at maximum 40
different E-HICHs/E-RGCHs transmitted on the same SF=128 channelisation code channel )
• RG is transmitted using 3 (for 2ms E-DCH TTI from serving E-DCH cell), 12 (for 10ms
E-DCH TTI from serving E-DCH cell) or 15 (from non-serving E-DCH cells) consecutive
slots
• in each slot is transmitted a sequence bi,0, bi,1, …, bi,39 : bi,j = a Css,40,m(i),j
• Note, that the E-RGCH is a dedicated channel, defined by a channelisation code and a
signature sequence, and each E-HICH and E-RGCH transmitted on the same SF=128
channelisation code
• The channel can be independently power controlled by the Node B (vendor specific)

E-AGCH (E-DCH Absolute Grant Channel)
• The E-DCH absolute grant (AG) is mapped on E-AGCH xag,1, xag,2,..., xag,w
• content of AG and the number of AG bits are FFS ID specific

• E-AGCH is a shared channel, where only one AG is CRC attachment
transmitted at a time on one SF=256 channelisation y1, y2,..., yw+16

code channel
• CRC attachment: 16 bit CRC, masked with the UE identity Channel coding
(E-DCH Radio Network Identifier, E-RNTI, defined by

higher layers), is attached to the AG z1, z2,..., z3x(w+24)
• Channel coding: rate 1/3 convolutional coding Rate matching
• Rate matching: the number of channel coding output bits is

matched to the number of E-AGCH bits within 2ms r1, r2,..., r60
• Physical channel mapping: rate matching output bits are Physical channel
mapping
mapped to allocated E-AGCH
• E-AGCH has a 2ms sub-frame structure
• Note that some simplifications under discussion in 3GPP! E-AGCH
Coding for E-AGCH

HSUPA and DCH co-existance
• For an existing user, E-DCH users will only show as part
of the interference variations (at BTS receiver)
• -> Thus mixing DCH & E-DCH users is not a problem
• The load variation caused by DCH users are not under BTS
control (but under slower RNC based method)
• Depending on the allocation, there can be allocated both E-
DCH and DCH for the same terminal
• E.g. with AMR speech call active while having packet data
connection on-going
• This allows smooth introduction for the network as
separate carrier is not needed until single carrier capacity
fully utilised

E-DCH vs. DCH
• DCH does not use BTS based retransmission handling or BTS based scheduling
• Both the variable spreading factor principle as well as fast power control
unchanged from DCH to E-DCH
• Both support multicode use, though more practical with E-DCH
Feature DCH E-DCH
Variable spreading factor Yes Yes
Fast power control Yes Yes
Adaptive modulation No No
BTS based scheduling No Yes
Fast L1 HARQ No Yes

HSUPA - Summary
• Node B based uplink scheduling and HARQ for improved performance
• Adaptive modulation not part of HSUPA as power control maintained
• HSUPA is backwards compatible and can be introduced gradually in the
network.

HSUPA Capacity

HSUPA Capacity Gain
Node-B scheduling +
faster retransmissions
Uplink cell throughput [kbps]
1800
HSUPA
1600 HSUPA
1400
Release’99
1200
1000
kbps
800
600
Advanced
400 scheduling
200
0
R99 RNC scheduling HSUPA round robin HSUPA proportional
BLER=1% fair
HSUPA Performance Gains
UE capability
Capacity Iub capacity Coverage gain Latency gain
beyond
gain 20- gain 0.5 – 1.0 dB <50 ms
384 kbps
50%
HSUPA
Uplink data rate gain Cell Quality of

from 384 kbits
throughput Lower costs Coverage of
end user
(Rel99) to 1-5 Mbits
gain in transport high data-rate
(Rel6) experience
Æ Higher add-on ÆSavings in BB ÆSavings in Æ Saves BTS sites Æ Higher add-on

PS Traffic capacity costs transport – in (~10%) and adds PS traffic
Dedicated VCC PS traffic
solution max 25%

HSUPA – 3GPP Open Issues
Most of these for WG1, WG2 and WG3 should be closed for the
June 2005 spec versions.
For the ASN.1 backwards compatibility not likely to start before
end 2005 (est.)

3GPP open issues, WG1 (physical layer)
• Compressed mode with 10 ms TTI
• Need for new UTRAN/UE measurements or modifications to the existing ones.
• Possibility to do slot-by-slot power scaling of E-DPDCH only in case the UE runs
out of transmission power within a TTI.
• The exact contents of E-AGCH are not yet defined
• 5 bits for DPCCH to E-DPDCH power ratio is agreed
• Total # of bits open, inclusion of time duration, per process flag, etc.
• The exact number of bits may also have an impact to the E-AGCH coding and spreading
factor
• E-DPxCH gain factor quantisation.

3GPP open issues, WG2 (MAC, RRC, Stage 2)
• Scheduling behaviour simplifications being discussed
• Two schemes are well defined in general but there are some details that still need some
work.
• Trying to merge the two schemes as only one
• Details of E-TFC selection and restriction
• Priority based scheduling:
• In addition to UE and HARQ based scheduling, Ericsson and NEC are now proposing to
have some kind of priority based scheduling where the grants would be applicable up to
a given priority only.
• Content of the uplink MAC-signalling scheduling information:
• How many bits needed for the buffer occupancy report.
• Transport block sizes:
• Agreed to have 4 tables, but now we need to agree on the tables.
• Serving cell change:
• L2 based cell selection for faster cell change Nortel and Panasonic propose to have UE
based cell change. Benefits questionable
• Minimum bit rate for 2ms TTI:
• One PDU gives already quite a high minimum bit rate (320-bit PDU: 160 kbps)
• Potentially too high and something may have to be done to lower it.
3GPP open issues, WG3 (NBAP, FP)
• HARQ Failure indication signalling principles were agreed.
• No CR yet implementing the agreement.
• Iub congestion detection was agreed in principle.
• No agreement on the exact nature of loss detection. Whether we will use Frame
Sequence Number or Octet sequence number is FFS.
• The big open issue in Congestion notification is the NodeB action to
it.
• Agreed to signal Node B a three level congestion notification; no/mild/severe
congestion. Will be conveyed in its dedicated control frame.
• Support of 2ms TTI bundling is already there in the frame structure.
• Bundling: Bundle five 2 ms AIF packets to one 10 ms FP packet
• However, the support is still missing from NBAP and RNSAP.
• FFS how / by whom to decide the bundling in case of SHO. Can different branches have
different approach (bundling, no bundling) <-> RNSAP, NBAP
• FP Frame structure, a lot of things done
• The needed header CRC length is FFS. Header is getting longer and more CRC bits may
be needed.

3GPP open issues, WG4 (Performance)
• All the performance requirements are still open
• Beta factors for requirements and testing on E-DPDCH and E-DPCCH
• RAN4 assumptions on FRC, RV index sequence, Switching between different TTI, and
Number of HARQ processes needs to be revisited after RAN1/RAN2 decision
• Working points per FRC
• Requirements and testcases for E-RGCH and E-AGCH
• False alarm rate for E-RGCH
• False alarm rate and miss-detection for E-DPCCH
• E-HICH, False alarm ACK rate for serving and non-serving cell
• Requirements and tests for E-RGCH/E-AGCH
• PAR/CM
• E-TFC
• Active Set Size
• Implementation Margin
• Finalize ideal simulation results for all channels (DL & UL)
• How accurate can the scheduler follow the targets set by the RNC in x% of the time

UTRAN Long Term Evolution

General Requirements for UTRAN Evolution
• Feasibility study started in 3GPP for UTRAN Long Term Evolution
with the following requirements
• Packet switched domain optimized
• Server UE round trip time below 30 ms and access delay below 300 ms
• Peak rates uplink/downlink 50/100 Mbps
• Ensure good level of mobility and security
• Improve terminal power efficiency
• Frequency allocation flexibility with 1.25/2.5, 5, 10, 15 and 20 MHz
allocations, possibility to deploy adjacent to WCDMA
• WCDMA evolution work on-going to continue with full speed
• Technologies under consideration include also new radio access

technologies as well as new network architecture possibilities

UTRAN Evolution
3.5G
3.5GHSDPA/HSUPA
HSDPA/HSUPA
3GPP
3GPPRel.6
Rel.6
HSPA
HSPAevolution
evolution 3.9G
3.9Gnew
newradio
radioaccess
access
• Best CS + PS combined radio • Optimized for PS only

• Current RAN architecture • New architecture
• Spectrum shared with current 3G • New modulation
• Reduced latency • Spectrum and bandwidth flexibility
• Full service continuity with 2G and • Further reduced latency
3G • Interworking with 3.5G evolution

Hsdpa Basic

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hsdpa Basic

Uploaded by

Copyright:

Available Formats

HSDPA/HSUPA

High speed packet access

Harri Holma, Principal Engineer

1 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

2 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

3 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

4 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

5 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

3 parallel users in WCDMA

6 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

End-to-end Round Trip Time (RTT)

Radio transmission UMTS RAN + core Internet

UE BTS RNC SGSN GGSN Server

HTTP 384 kbps

1st WAP Page Download Time

AMR 12.2 kbps users with 50% voice activity

10 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

11 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

Reference: WCDMA for UMTS, 3rd edition, Chapter 11

12 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

13 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

14 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

Downlink fast scheduling

• UE's channel quality

15 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

UE1 TTI 1 TTI 2 TTI 3 TTI 4

UE2 USER 2 Es/N0 USER 1 Es/N0

16 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

HSDPA user plane

19 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

RLC ACK/NACK L1 ACK/NACK

20 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

• There are two ways of operating:

21 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

New Node B functions:

22 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

Packets ARQ Soft Buffer

New terminal functions:

23 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

25 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

26 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

HS-DSCH Demodulation information

27 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

• First part carries X1 X2

• Transport-block size information Channel Channel

• Additionally UE identify information is R1 R2

28 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT

HS-DSCH CRC attachment

bim1 ,bim2 ,bim3 ,...bimB

• The HS-DSCH uses 1 to 15 codes with fixed Bit Scrambling

SF 16 dim1 ,dim2 ,dim3 ,...dimB

• Specific parts in the channel coding chain Code block segmentation

are related to HARQ and 16QAM oir1,oir2,oir3,...oirK

modulation (and some simplifications as Channel Coding

there is no DTX, compressed mode etc…) ci1,ci2,ci3,...c iE

• Impacted by 16QAM Physical Layer Hybrid-ARQ

• Interleaving (two identical interleavers w1,w2,w3,...wR

with 16QAM TTIs) Physical channel

vp,1 ,vp,2 ,vp,3 ,...vp,U

rp,1 ,rp,2 ,rp,3 ,...rp,U

Physical channel mapping

ACK/NACK Channel Quality Information

7.5 slots (approx.)

30 © NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT