Hsdpa/Hsupa High Speed Packet Access: March 22 2005 Salo, Finland

HSDPA/HSUPA High speed packet access
March 22nd 2005 Salo, Finland

Harri Holma, Principal Engineer Antti Toskala, HSDPA Chief Architect Nokia, Finland
NOKIA
HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT
Agenda
WCDMA R99 performance today HSDPA standard HSDPA performance HSUPA standard HSUPA performance
NOKIA
WCDMA Performance in Commercial Networks
NOKIA
WCDMA Release99 Terminal Capability

Nokia 6630
EDGE included Data rates

Downlink 384 kbps Uplink 128 kbps
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
NOKIA
WCDMA Coverage Noise Limited

384 kbps can be provided down to approx 105 dBm if no other-cell interference
400 350 300 250 kbps 200 150 100 50 0 -115 -110 -105 -100 -95 CPICH RSCP [dBm] -90 -85 -80
3 parallel users in WCDMA

WCDMA2100 EDGE900
384 kbps
Similar average data rate of approx 200 kbps with WCDMA2100 and EDGE900
NOKIA
WCDMA Coverage Interference Limited

400 350 300 250 kbps 200 150 100 50 0 -100
3 parallel users in WCDMA

WCDMA2100 EDGE900
Approx 2 x higher data rate in WCDMA than in EDGE Data rate other-cell interference limited at the cell edge
-95 -90 -85 -80 CPICH RSCP [dBm] -75 -70
NOKIA
WCDMA Round Trip Time (RTT)

Typical round trip time 150-200 ms for small IP packets in todays 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
7 NOKIA
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
RRC
PDP
RB reconfig
HTTP 384 kbps TCPrequest 32 RB reconfig kbps
1.5 s
1 2 3 4 5 6 7 8 9 10
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
User pushes WAP home page key UE internal delay (in Nokia browser in Charlie) RRC connection activation Security mode PDP context activation + signaling radio bearer setup + measurement control Radio bearer reconfiguration from 0/0 kbps to 16/32 kbps uplink initiated UE internal delay TCP connection establishment HTTP request in uplink 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
8 NOKIA HSDPA/HSUPA.PPT / 22-03-2005 / HH+AT
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
10.3 s
10.0
6
1 UE Symbian delay reduced from 1.5 to 0.5 s 2 RRC setup on common channels 3 4 5 6 Authentication done with GPRS attach already Direct RB allocation after PDP context UE delay removed Seamless RB upgrade
8.0
5
s 6.0
4.7 s
4.0
3 2 1
Display rendering Download over 384 kbps TCP slow start DCH upgrade DNS query and HTTP request TCP connection establishment UE internal delay RB reconfiguration PDP context activation Security mode Authentication and ciphering RRC connection establishment UE internal delay
2.0
= Setup times
Optimized
0.0 RAN04
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 op
10 NOKIA
Example last slide
Asia, high result
Asia, low result
Asia, stationary
Asia, drive test
Summary of Data Capacity Tests

Typical data capacity 600-1000 kbps per cell
1000 900 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)
Measured stationary Measured drive test
WCDMA High Speed Downlink Packet Access (HSDPA) of Release 5

Reference: WCDMA for UMTS, 3rd edition, Chapter 11
12
NOKIA
Outline
HSDPA Introduction HSPDA Protocol Architecture New Node B & UE functions Modulation and coding HSDPA & Soft Handover HSDPA vs DCH/DSCH HSDPA & Iub Summary
13
NOKIA
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 Part of Release 5 First specifications version completed 03/02
Schedule in 3GPP

14
NOKIA
HSDPA General Principle

L1 Feedback Data Downlink fast scheduling done directly by Node B (BTS) based on knowledge of: UE's channel quality UE's capability QoS demands Power and code resource availability Node B buffer status
Terminal 1 (UE)
L1 Feedback Data
Terminal 2 Users may be time and/or code multiplexed

Multi-user Diversity (Fast Scheduling)

Channel quality (CQI, Ack/Nack, TPC) Data
Node-B scheduling can utilize information on the instantaneous channel conditions for each user.
UE1
Multi-user selection diversity (give shared channel to best user) Channel quality (CQI, Ack/Nack, TPC) Data
TTI 1
TTI 2
TTI 3
TTI 4 Scheduled user
UE2
USER 2 Es/N0
USER 1 Es/N0
Fast Link Adaptation in HSDPA

16 C/I received by UE 14 12 10 8 6 4 2 0 -2
0 20
Instantaneous EsNo [dB]
C/I varies with fading
40
16QAM3/4 16QAM2/4 QPSK3/4 QPSK2/4 QPSK1/4

17 NOKIA
Time [number of TTIs]
60
80
100
120
140
160
Link adaptation mode
BTS adjusts link adaptation mode with a few ms delay based on channel quality reports from the UE
Release99 RRM Functional Split

Mapping RAB QoS Parameters into air interface Mapping RAB QoS Parameters into air interface L1/L2 parameters (incl. transport channel selection) L1/L2 parameters (incl. transport channel selection) Air interface scheduling (for dedicated channels) Air interface scheduling (for dedicated channels) Handover Control Handover Control Outer loop power control and power balancing Outer loop power control and power balancing
RR C
Fast power Fast power control control Overload control Overload control
Iub
Iur
Iu
MSC
Node B
Drift RNC Serving RNC

SGSN
Admission control on interference and power level Admission control on interference and power level Initial power and SIR setting Initial power and SIR setting Radio resource reservation Radio resource reservation Air interface scheduling for common channels Air interface scheduling for common channels DL code allocation and code three handling DL code allocation and code three handling Load and overload control Load and overload control
Radio network Radio network topology hidden to the topology hidden to the CN CN
HSDPA Protocol Architecture

New MAC entity, MAC-hs added to the Node B Layers above, such as RLC, unchanged.
UE NAS RLC MAC WCDMA L1
Node B
SRNC RLC MAC-d FRAME PROTOCOL TRANSPORT
Iu
MAC-hs WCDMA L1
FRAME PROTOCOL TRANSPORT Iub/Iur
Uu
HSDPA user plane
19
NOKIA
Release99 vs HSDPA Retransmissions

Rel99 DCH/DSCH Rel5 HS-DSCH
RNC
Packet
Retransmission Packet Retransmission
BTS
RLC ACK/NACK
L1 ACK/NACK
Terminal
20
NOKIA
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.
21
NOKIA
New Node B functionality for HSDPA

RNC Node B Terminals
ARQ & Coding ACK/NACK & Feedback Decoding
Packets Flow Control
Scheduler & Buffer
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
ARQ Decoding Soft Buffer & Combining ACK/NACK & Feedback Generation
Packets Flow Control
New terminal functions: 16 QAM demodulation ARQ Retransmissions Handling Soft buffer & combining Fast Uplink Feedback Generation & encoding
23
NOKIA
Adaptive Modulation QPSK and 16QAM

Release99 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 Category 11 12 1/2 3/4 5/6 7/8 9 10
Modulation QPSK only QPSK only QPSK/16QAM QPSK/16QAM QPSK/16QAM QPSK/16QAM QPSK/16QAM QPSK/16QAM
Inter-TTI 2 1 3 2 1 1 1 1
Transport Block size 3630 3630 7298 7298 7298 14411 20251 27952
5 Codes 0.9 Mbps 1.8 Mbps 1.2 Mbps 1.8 Mbps 3.6 Mbps -
10 Codes 7.2 Mbps -
15 Codes 10.1 Mbps 14.0 Mbps
25
NOKIA
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
26
NOKIA
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 data Control data

HS-DSCH Demodulation information
User data User data

2 ms
HS-SCCH
The HS-SCCH is fixed data rate channel with SF 128 (60 kbps) The content is divided in two parts First part carries

Xccs Xms Xtbs Xhap mux
RV coding Xrv
Xnd
mux
Channelisation-code-set info Modulation info Transport-block size information Hybrid-ARQ process information Redundancy and constellation version New data indicator
X1 Xue
X2 UE specific CRC attachment Y
Second Part

Channel Coding 1
Channel Coding 2
Z1
Z2
Rate matching 1
Rate matching 2
Additionally UE identify information is used target the information to correct user
R1
R2
Xue
28 NOKIA
To separate which of the 4 HS-SCCHs UE needs to decode (UE specific masking) Decoder matrix to be observed..
UE specific masking S1
Physical channel mapping
HS-SCCH
aim1 ,aim2 ,aim3 ,...aimA
HS-DSCH
bim1 ,bim2 ,bim3 ,...bimB
CRC attachment
The HS-DSCH uses 1 to 15 codes with fixed SF 16 Specific parts in the channel coding chain are related to HARQ and 16QAM modulation (and some simplifications as there is no DTX, compressed mode etc) Impacted by 16QAM

Bit Scrambling dim1 ,dim2 ,dim3 ,...dimB Code block segmentation
oir1,oir2,oir3,...oirK Channel Coding ci1,ci2,ci3,...c iE Physical Layer Hybrid-ARQ functionality w1,w2,w3,...wR Physical channel segmentation up,1 ,up,2 ,up,3 ,...up,U HS-DSCH Interleaving
Interleaving (two identical interleavers with 16QAM TTIs) Constellation re-arrangement (same bits not in same constellation point between retransmissions
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
29
NOKIA
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 CRC result HS-DSCH
HS-DPCCH 2 ms
2 ms
7.5 slots (approx.)
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 0 1 2 3 4 5 6 7 8 9 10 11 12 Mi,0 1 0 1 0 1 0 1 0 1 0 1 0 1 Mi,1 0 1 1 0 0 1 1 0 0 1 1 0 0 Mi,2 0 0 0 1 1 1 1 0 0 0 0 1 1 Mi,3 0 0 0 0 0 0 0 1 1 1 1 1 1 Mi,4 1 1 1 1 1 1 1 1 1 1 1 1 1
message to be transmitte d
w
0
w
1
w
2
w
3
w
4
w
5
w
6
w
7
w
8
w
9
ACK
NACK
PRE
POST
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
Ratio of DPCCH/DPDCH gain factors for all values of HS-DPCCH gain factor
Power Class 3 Power (dBm) +24 +23 +22 Tol (dB) +1/-3 +2/-3 +3/-3
Power Class 4 Power (dBm) +21 +20 +19 Tol (dB) +2/-2 +3/-2 +4/-2
1/15 c/d 12/15 13/15 c/d 15/8 15/7 c/d 15/0
32
NOKIA
MAC-hs Round-Trip Loop Timing

Minimum retransmission delay 12 ms
18 slots = 12 ms 2 x Tprop + 15.5 slots
2 slots
B Retransmit
A = HS-DPCCH L1, MAC-hs, HS-SCCH L1 B = HS-PDSCH L1
HS-SCCH HS-PDSCH
2 slots 3 slots A/N CQI
Retransmit
33
NOKIA
Rate Matching
Turbo encoder coding rate = 1/3. Rate Matching is used to adapt to the desired coding rate. Either puncturing or repetition. In the example, RM punctures into rate 3/4. Note: The systematic bits are more important than parity bits!
Systematic Parity 1 Parity 2 Data
Turbo Encoder
Rate Matching (Puncturing)

Systematic Parity 1 Parity 2
34
NOKIA
Hybrid ARQ (HARQ): Chase Combining

Turbo Encoder
Rate Matching (Puncturing) Original transmission

Retransmission
Chase Combining (at Receiver)

35
NOKIA
Hybrid ARQ (HARQ): Incremental Redundancy

Turbo Encoder
Rate Matching (Puncturing) Original transmission

Retransmission
Incremental Redundancy Combining

36
NOKIA
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
Geometry=0dB
-8
-6 Tx Ec/Ior (dB)
Geometry=5dB
-4
Geometry=10dB
-2
Low Throughput
37
NOKIA
Example CQI Mapping Table

BTS can map the received CQI value for the data rate to be used in the link adaptation Necessary conversion to be done depending on BTS power availability Reference power adjustment used when quality would allow higher rate than UE capability
CQI value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Transport Block Size N/A 137 173 233 317 377 461 650 792 931 1262 1483 1742 2279 2583 3319 3565 4189 1 1 1 1 1 1 2 2 2 3 3 3 4 4 5 5 5 Reference power Number of Modulation adjustment HS-PDSCH Out of range 0 QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK 16-QAM 16-QAM 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 NIR XRV 9600 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
Iub DCH Node B DCH
DCH + HS-DSCH
Iub Node B
DCH
Node B
Node B
39
NOKIA
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 Iub RNC
Node B
40
NOKIA
HS-DSCH vs. DSCH

DSCH of Release99 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 Variable spreading factor Fast power control Adaptive modulation and coding Fast L1 HARQ
DSCH Yes Yes No No
HS-DSCH No No Yes Yes
41
NOKIA
HSDPA & DCH Resource Sharing

Node-B Tx power Max power Power measurements from the Node-B to the RNC Power control head-room Total transmitted carrier power HSDPA NRT NEW non-HSDPA power measurements DCH NRT Controllable power PtxTarget
DCH RT In addition to power also code resource shared! Non-controllable power Common channels
42
NOKIA
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 DPDCH HALF RATE Data DPDCH TPC TFCI Data DTX Pilot DPCCH TPC TFCI Data Pilot DPCCH
DPCCH
DPDCH Slot 0.667 ms = 2/3 ms
DPCCH
DPDCH Slot 0.667 ms = 2/3 ms
43
NOKIA
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 ] C2(0) = [ 1 1 1 1 ]
...
... ...
= Allocated code
C3(1) = [ 1 1 1 1 0 0 0 0 ]
C1(0) = [ 1 1 ] C2(1) = [ 1 1 0 0 ] C0(0) = [ 1 ] C3(3) = [ 1 1 0 0 0 0 1 1] C3(2) = [ 1 1 0 0 1 1 0 0 ]
... ...
... ... ... ... ... ... ... ...
= Code which cannot be allocated at the same time as C3(1)
... ...
C3(4) = [ 1 0 1 0 1 0 1 0 ] C2(2) = [ 1 0 1 0 ] C1(1) = [ 1 0 ] C3(5) = [ 1 0 1 0 0 1 0 1 ]
= Code which can be allocated at the same time as C3(1)
...
...
C3(6) = [ 1 0 0 1 1 0 0 1 ] C2(3) = [ 1 0 0 1 ]
. .... .
... ...
Spreading factor: SF = 1
44 NOKIA
C3(7) = [ 1 0 0 1 0 1 1 0 ]
These codes cannot be used at the same time as C3(1)
...
...
SF = 2
SF = 4
SF = 8
HSDPA & Iub

HSDPA improves Iub efficiency compared to Release99 packet data since HSDPA is a time shared channel with a flow control in Iub Release99 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 Iub link 2
1 1
2 2
HSDPA Iub capacity
= User 1 = User 2 = User 3

1 = TCP slow start 2 = Inactivity timer
Iub efficiently utilized by HSDPA
HSDPA & Iub (Cont.)

The needed Iub capacity is NOT equal to air interface peak rate (e.g. 1.8 or 7.2 Mbps)
Cumulative distribution function [-] 80% power and 15 codes allocated to HSDPA service
1 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0.01 0.1 1
The momentary data rate over 2 ms can be higher than the Iub capacity available, as BTS has buffers and is scheduling to multiple users Iub loading thus more related to the actual air interface capacity
Macrocell/Veh A/3kmph
Average data rate avaible
Microcell/Ped A/3kmph
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.
HSDPA is a natural capacity evolution to WCDMA and an enabler for higher speed data services
Freely configurable transmission
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
48
NOKIA
HSDPA Performance
49
NOKIA
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 per 2 ms TTI1 10 x 320 21 x 320 42 x 320 60 x 320 83 x 320 Transport block1 3440 7168 14155 20251 27952 Max RLC data rate 1.6 Mbps 3.36 Mbps 6.72 Mbps 9.6 Mbps 13.3 Mbps
UE category 12 5/6 7/8 9 10
# of codes 5 codes 5 codes 10 codes 15 codes 15 codes
Modulation QPSK 16-QAM 16-QAM 16-QAM 16-QAM
1RLC
2Includes
block size of 320 bits assumed user plane + RLC headers + MAC headers + padding
50
NOKIA
Nokia HSDPA RAN Measurements
51
NOKIA
Nokia HSDPA RAN Throughput [kbps]

Application throughput matches with the theoretical calculation >1.5 Mbps measured with FTP download 1.8 Mbps 5-code QPSK
Throughput [kbps]
2000 1800 1600 1400 1200 1000 800 600 400 200 0
1.6 Mbps
1.53 Mbps
L1 throughput (theory)
RLC throughput (theory)
Application throughput (theory)
Application throughput (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
200 180 160 140 120 ms 100 80 60 40 20 0
RAN1.5ED2 RAN04 (20- RAN04 (20- RAN04 (10ms UL+DL) ms UL 10-ms ms UL+DL) DL) 3GPP R5 HSDPA (20ms UL 2-ms DL) 3GPP R5 HSDPA (10ms UL 2-ms DL) 3GPP R6 HSUPA (2ms UL+DL)
Measured with Ubinetics
Calculated Measured
94 ms measured with 20-ms uplink
53
NOKIA
System Control Algorithms
54
NOKIA
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
55
NOKIA
Link Adaptation
56
NOKIA
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.
57
NOKIA
A Two-Step HS-DSCH Link Adaptation (2)

RNC Node-B
CQI settings Handover control
Outer loop LA algorithm
Inner loop LA algorithm
HS-DSCH
UL HS-DPCCH detection
CQI PDCH
58
NOKIA
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 multicodes 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.
59
NOKIA
Outerloop Algorithm Based on Ack/Nack's

Start
Increase set-point if: Nack on 2nd trans. Decrease set-point if: Ack on 1st or 2nd trans.
Set A equal to the predefined initial value
Ack received from first transmission of block ? No
Yes
Increase A by "AStepUp" [dB]
No
Ack received from first re-transmission of block ?
Ratio between up/down step determines the residual BLER, I.e. similar as conventional outerloop power control.
Yes Decrease A by "AStepDown" [dB]
60
NOKIA
HS-SCCH Power Control
61
NOKIA
HS-SCCH PC Summary
RNC Node-B P0 /P1 or
HSDPA offset Handover control
HS-SCCH power offset
Outer loop PC algorithm
Inner loop PC algorithm
HS-SCCH transmit power
SHO: On\Off UL HS-DPCCH detection CQI PDCH
Inner loop based on CQI
62
NOKIA
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
BLER =
1 Pup Pdown +1
63
NOKIA
System Performance and Simulations
64
NOKIA
HSDPA Performance
Link performance Link performance How far from Shannon limit?
Macro cell Macro cell performance single performance single user per cell user per cell Scheduler Scheduler performance performance multiple users per cell multiple users per cell Application Application performance end performance end user view user view
What can be achieved in macro cells if all resources given to single user?
How cell resources can be shared between simultaneous users?
What is e2e application performance over HSDPA?
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 HSDPA link adaptation curve 0.1
15 HS-PDSCH allocation (Rake, Pedestrian-A, 3km/h)
1.0
16QAM
0.01
-15
-10
-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 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0.01 0.1
Macrocell/Veh A/3kmph
Mean bit rate 1.5 Mbps in macro cells
Microcell/Ped A/3kmph
Mean bit rate >5 Mbps in micro cells

1 10
Instantaneous (per 2 ms) user throughput [Mbps]

Bit Rate Coverage Interference Limited Case

3 parallel users in WCDMA and in HSDPA
2000 1800 1600 1400 1200 kbps 1000 800 600 400 200 0 -100 -98 -96 -94
Average data rates Average data rates HSDPA2100 1920 kbps (1 user) HSDPA2100 1920 kbps (1 user) HSDPA2100 640 kbps (3 users) HSDPA2100 640 kbps (3 users) WCDMA2100 250 kbps (3 users) WCDMA2100 250 kbps (3 users) EDGE900 140 kbps EDGE900 140 kbps
HSDPA2100 WCDMA2100 EDGE900
HSDPA2100 (3 users) WCDMA2100 (3 users) EDGE900

-92 -90 -88 CPICH RSCP [dBm] -86 -84 -82 -80
68
NOKIA
HSDPA Coverage Interference Limited

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

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

Min. target Throughput
Operator adjustable slopes for different service and user classes Tradeoff between cell throughput, coverage and user fairness
Throughput
Fair Throughput Fair time C/I based

Spectral Efficiency
high
Throughput coverage of C/I based scheduling
Throughput coverage of fair throughput scheduling
low Low coverage of high data rates

Packet Scheduling Strategies

PS Method Scheduling rate
Fair throughput (FT) Fair resource (FR) Slow (avg. over 20-100ms) Slow (avg. over 20-100ms)
Serve order
Round robin in random order Round robin in random order
Allocation method
Resources according to same throughput (up to max. alloc. time) Same resources (time/power/ codes) per allocation time
Served according to highest C/I based Slow Same resources (time/power/ slow-averaged channel *) Note that actual resource allocation will be heavily influenced by QoS/delay requirements time (CI) (avg. over 20-100ms) codes) per allocation quality and user prioritization schemes! Served according to highest Max C/I based Fast Same resources (time/power/ *) Note that actual resource allocation willinstantaneous channel by QoS/delay requirements time be heavily influenced (M-CI) (Per-TTI basis) codes) per allocation quality and user prioritization schemes! Served according to highest 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 resource (P-FR) Fast (Per-TTI basis) Served according to highest relative instantaneous channel quality (RICQ) Same resources (time/power/ codes) per allocation time
72
NOKIA
Multi-user Diversity (Fast Scheduling)

Channel quality (CQI, Ack/Nack, TPC) Data
Node-B scheduling can utilize information on the instantaneous channel conditions for each user.
UE1
Multi-user selection diversity (give shared channel to best user) Channel quality (CQI, Ack/Nack, TPC) Data
TTI 1
TTI 2
TTI 3
TTI 4 Scheduled user
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 Tk [n]
Rk = instantaneous supported data rate for user k Tk = average throughput for user k
74
NOKIA
Proportional Fair Scheduling as a Function of Number of Users

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

Dynamic System Simulation Macro Cells Vehicular A Channel
4500 4000 3500 3000
kbps
Round robin 5 codes Round robin 10 codes Proportional fair 5 codes Proportional fair 10 codes Proportional fair 15 codes
4 Mbps
2500 2000 1500 1000 500 0 Rake 1-ant
2 Mbps 1 Mbps
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
77
NOKIA
Co-Existence of R99 and HSDPA
78
NOKIA
Co-existence of R99 and HSDPA

= R5 HSDPA = R99 DCH
HSDPA can be introduced to the network with shared or with dedicated frequency Carrier shared between HSDPA and R99 Operator definable or dynamic resource sharing between HSDPA and R99
f1 f1
f2 f2 f1 f1
Dedicated HSDPA carrier HSDPA UE directed to HSDPA carrier
f2 f2 f1 f1
HSDPA carrier, which can also be used for R99 traffic in case of R99 high load UE moved by RRC connection setup or by handovers
79
NOKIA
HSDPA and Iub Capacity
80
NOKIA
HSDPA Improves Iub Efficiency by 50-100%

In total, HSDPA improves Iub efficiency 50-100% compared to Release99 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. Iub capacity requirement E1 capacity
Inactivity Inactivity Soft HO Soft HO Release99 Release99 user data user data Common ch Common ch
HSDPA HSDPA user data user data
Common ch Common ch
DCH
HSDPA
Trade-off Between HSDPA RF and Iub Capacity

HSDPA RF vs Iub efficiency
100% 95% 90% 85% 80% 75% 70% 65% 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]
RF utilization [%] Iub utilization [%]
High Iub efficiency (95%) requires some overhead (15%) in air interface dimensioning
High RF efficiency (95%) requires some overhead (25%) in Iub dimensioning
End User Capacity and Cost
83
NOKIA
HSDPA Enables Mass Market >1 GB/Sub/Month

1-carrier HSDPA assumed
2.5
HSDPA 2-rx UE HSDPA 1-rx UE
2.0 GB/sub/month
1.5
1 GB/month for 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 3.5 3.0 2.5 2.0 1.5 1.0 0.5 0.0
<4 /GB data
[EURO /GB]
14 16 18 20 22 24 26 28 30 32 34 36 38 40
Depreciation over 6 years Other assumptions from previous slide
Price per TRX [k]
VoIP over HSPA
86
NOKIA
VoIP Usage Growing Fast in Fixed Internet
Close to 100 M downloads and counting... Also Pocket PC version, ca. 2 MB
87
NOKIA
VoIP Drivers and Challenges in Cellular

Drivers
1. 2. 3.
Enterprise VoIP extension to wide area Rich call interworking Plain vanilla VoIP for network simplicity
Challenges
1. 2. 3.
End-to-end delay capability Bandwidth and delay during high load Efficiency in the air interface and Iub
BTS
RNC
SGSN/GGSN
88
NOKIA
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 100 Voice users 80 60 40 20 0 R99 CS voice HSDPA VoIP with round robin HSDPA VoIP with proportional fair 150 ms delay 80 ms delay
Queuing + transmission delay in downlink
89
NOKIA
Radio Technology Evolution

End user bit rate [kbps] 3 Mbps 1 Mbps 300 kbps 100 kbps 30 kbps
EGPRS, Rel. 99 100-200kbps 500-700ms GPRS 500-700ms 40kbps EVDO Rev 0 400 kbps 200-300 ms VoIP feasible from e2e performance point of view HSPA 1-2 Mbps 50-100ms ADSL 1-2 Mbps <50ms
WCDMA, R99 200-300kbps 150-200ms
EGPRS, Rel. 4 100-200kbps 200-500ms
600
500
400 300 Round trip time [ms]
200
100
90
NOKIA
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
91
NOKIA
Mobile Broadband Access Landscape

Fixed broadband wireless 802.16
802.16e Wireless DSL Flat rate Mobile premium Cellular Value added services EDGE, WCDMA, cdma EV-DO HSDPA
Mobile broadband wireless access Proprietary

Flarion
Proprietary extensions
LAN
802.11 WiFi
92
NOKIA
Technology Positioning - Use Cases

1 Fixed BWA Wireless DSL 2 Portable BWA 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
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
93
NOKIA
Spectrum
= Expected bands for 802.16 = WCDMA/HSPA band with products today = WCDMA/HSPA band - future
5 GHz 3.4 GHz 2.6 GHz 2.5 GHz 2.1 GHz 1900 1700 1800 900 850
190 MHz 190 MHz 2x60 MHz 2x60 MHz 2x45 MHz 2x75 MHz 2x35 MHz 2x25 MHz
Unlicenced Fixed wirelss access band in Europe New 3G band in Europe by 2008 MMDS in USA Mainstream WCDMA . US PCS band
Smallest coverage
New USA 3G band by 2006 Europe and Asia Europe and Asia Americas, Japan, Asia Best coverage
94
NOKIA
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
95
NOKIA
WCDMA High Speed Uplink Packet Access (HSUPA) of Release 6

Reference: WCDMA for UMTS, 3rd edition, Chapter 11
96
NOKIA
Outline
HSUPA Introduction HSUDA Protocol Architecture HSUPA Retransmissions HSUPA Peak Bit Rates HSUPA UE Capabilites HSUPA Channel Stuctures Uplink and Downlink Summary
97
NOKIA
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 Part of Release 6 First specifications version completed 12/04 In 3GPP specs with the name Enhanced uplink DCH (E-DCH)
Schedule in 3GPP

98
NOKIA
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
3GPP study item
2004
Study item completed
2005
1st version in 3GPP spec
2006
Official work item completion date
2007
99
NOKIA
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 NAS RLC RLC MAC MAC-es/e WCDMA L1
Node B
SRNC RLC
MAC-e WCDMA L1
FRAME PROTOCOL TRANSPORT Iub/Iur
MAC-es FRAME PROTOCOL TRANSPORT
MAC-d
Iu
Uu
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 + control
Mac-e Mac-es Iub
Data packet
UE
+ possible retransmissions + control for scheduling
Node B
RNC
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 noise rise variations Less headroom needed Cell capacity and user data rates are increased With low loaded uplink, the users may get significantly higher data rates as much more aggressive data rates can be granted to UEs
PDF of the NR per BTS
0.7 Mean: 5 (dB) StD: 0.72 (dB)
0.6
RNC sheduling Node B scheduling
Mean: 4.1 (dB) StD: 1.2 (dB)

0.5
0.4
Operation point can be increased because variance is reduced.
0.3
0.2
0.1
10
NR [dB]
102
NOKIA
DCH vs E-DCH Retransmissions

DCH E-DCH
RNC
Packet
Retransmission Packet (1st TX)
Combining of packet and retransmission

Retransmission
BTS
RLC ACK/NACK
L1 ACK/NACK
Terminal
103
NOKIA
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 received packet
BTS
UE
104
NOKIA
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) Information of the redundancy version for the packet 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: Transmission power left Data left in the buffers (for more than X TTIs, X as parameter)
RNC
BTS
MAC-PDU
E-DPCCH
105
NOKIA
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 Category 1 2 2 3 4 4 5 6 6
Codes x Spreading 1 x SF4 2 x SF4 2 x SF4 2 x SF4 2 x SF2 2 x SF2 2 x SF2 2xSF2 + 2xSF4 2xSF2 + 2xSF4
TTI 10 10 2 10 10 2 10 10 2
Transport Block size 7296 14592 2919 14592 20000 5837 20000 20000 11520
Data rate 0.73 Mbps 1.46 Mbps 1.46 Mbps 1.46 Mbps 2 Mbps 2.9 Mbps 2 Mbps 2 Mbps 5.76 Mbps
HSUPA Channel Structure - Uplink

E-DPDCH, (E-DCH Dedicated Physical Data Channel) - carries the user data in the uplink direction, with the peak rate reaching up to 5.76 Mbps - codes are not shared with HSUPA (no code shortage in the uplink) E-DPCCH (E-DCH Dedicated Physical Control Channel ) - Parallel physical layer control channel - carrying e.g. ARQ information needed for the BTS decoding process + UE tx buffer status - Normal DCH operated in parallel (DPCCH always and DPDCH if there is data)
ced,1 E-DPDCH1 . . . . E-DPDCHk . . . . E-DPDCHK ec ed,1 iqed,1
ced,k
ed,k
iqed,k
ced,K
ed,K
iqed,K
I+jQ Se-dpch
cec E-DPCCH
iqec
108
NOKIA
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
slot
= 2560 chips, N
data
= 1 0*2 k+2 bits (k=0...5)
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 Release99 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 #i 0 1 2 3 4 5 Channel Bit Rate (kbps) 60 120 240 480 960 1920 SF Bits/ Frame 600 1200 2400 4800 9600 19200 Bits/ Subframe 120 240 480 960 1920 3840 Bits/Slot Ndata 40 80 160 320 640 1280
64 32 16 8 4 2
110
NOKIA
E-DCH Coding
One transport block once per TTI CRC attachment: 24 bit CRC Code block segmentation similar to the rel99/4/5 DCHs, the value of maximum code block size is 5114 for turbo coding Channel coding: rate 1/3 turbo coding (as rel99) Physical layer HARQ functionality and rate matching: SF and number of needed E-DPDCHs are determined (similar to rel99/4/5, but different parameters) and the physical layer HARQ functionality (see next slide) Physical Channel Segmentation: similar to the rel99/4/5 DCHs, when more than one E-DPDCH is used, physical channel segmentation distributes the bits among the different physical channels Interleaving and physical channel mapping: similar to the rel99/4/5 DCHs, rate matching output bits are interleaved and mapped to the allocated EDPDCH(s)
aim1 ,aim2 ,aim3 ,...,aimA CRC attachment
bim1 ,bim2 ,bim3 ,...,bimB Code block segmentation
oir1,oir2,oir3,...,oirK Channel Coding ci1,ci2,ci3,...,c i E Physical Layer Hybrid-ARQ functionality/Rate matching s 1,s 2,s 3,...,s R Physical Channel Segmentation up,1 ,up,2 ,up,3 ,...,up,U(p) Interleaving & Physical channel mapping
Physical channel(s)
Transport channel processing for E-DCH
E-DCH Channel Coding (cont.)

Bit separation (similar to rel99/4/5 turbo coded DCHs) Rate matching (similar to rel99/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
Ne,j bit separation
Parity 1 bits
Np1
RM_P1_2
Nt,p1
bit collection
Ne,data,j
Parity2 bits
Np2
RM_P2_2
Nt,p2
E-DCH hybrid ARQ functionality

E-DPCCH Coding
Control information on E-DPCCH is multiplexed: E-TFCI information (7 bits) Retransmission sequence number (RSN, 2 bits) Happy bit (Rate Request, 1 bit) Channel Coding: a sub-code of the second order Reed-Muller Code (similar to rel99/4/5 TFCI coding) Physical Channel Mapping: similar to rel99/4/5, channel coding output bits are mapped to the allocated E-DPCCH
xrsn,1, xrsn,2 xtfci,1, xtfci,2,..., xtfci,7 xh,1
Multiplexing
x1, x2,..., x10 Channel Coding z0, z1,..., z29 Physical channel mapping
E-DPCCH
Coding chain for E-DPCCH
113
NOKIA
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 For one UE only one is relevant but single code can serve serveral UEs
E-RGCH and E-HICH share the same SF 128 code
bi,0
bi,1 Tslot = 2560 chip
bi,39
Slot #0
Slot #1
Slot #2
Slot #i
Slot #14
1 subframe = 2 ms 1 radio frame, T f = 10 ms

E-HICH (E-DCH Hybrid ARQ Indicator Channel)

bi,0 bi,1 Tslot = 2560 chip bi,39
Slot #0
Slot #1
Slot #2
Slot #i
Slot #14
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 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 )
An orthogonal signature sequence Css,40,m(i),j is assigned to the E-RGCH by higher layers

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)
116
NOKIA
E-AGCH (E-DCH Absolute Grant Channel)

The E-DCH absolute grant (AG) is mapped on E-AGCH content of AG and the number of AG bits are FFS E-AGCH is a shared channel, where only one AG is transmitted at a time on one SF=256 channelisation code channel CRC attachment: 16 bit CRC, masked with the UE identity (E-DCH Radio Network Identifier, E-RNTI, defined by higher layers), is attached to the AG Channel coding: rate 1/3 convolutional coding Rate matching: the number of channel coding output bits is matched to the number of E-AGCH bits within 2ms Physical channel mapping: rate matching output bits are mapped to allocated E-AGCH E-AGCH has a 2ms sub-frame structure Note that some simplifications under discussion in 3GPP!
E-AGCH r1, r2,..., r60 Physical channel mapping xag,1, xag,2,..., xag,w ID specific CRC attachment
y1, y2,..., yw+16
Channel coding
z1, z2,..., z3x(w+24)
Rate matching
Coding for E-AGCH
117
NOKIA
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 EDCH 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
118
NOKIA
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 Variable spreading factor Fast power control Adaptive modulation BTS based scheduling Fast L1 HARQ
DCH Yes Yes No No No
E-DCH Yes Yes No Yes 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.
120
NOKIA
HSUPA Capacity
121
NOKIA
HSUPA Capacity Gain

Node-B scheduling + faster retransmissions
Uplink cell throughput [kbps]

1800 1600 1400 1200 kbps 1000 800 600 400 200 0 R99 RNC scheduling BLER=1%
HSUPA HSUPA Release99
Advanced scheduling
HSUPA round robin
HSUPA proportional fair
HSUPA Performance Gains

UE capability beyond 384 kbps Capacity gain 2050% Iub capacity gain Coverage gain 0.5 1.0 dB Latency gain <50 ms
HSUPA
Uplink data rate gain from 384 kbits (Rel99) to 1-5 Mbits (Rel6)
Cell throughput gain

Savings in BB capacity costs
Lower costs in transport
Coverage of high data-rate
Quality of end user experience

Higher add-on PS traffic
Higher add-on PS Traffic
Saves BTS sites Savings in (~10%) and adds transport in PS traffic Dedicated VCC solution max 25%
123
NOKIA
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.)
124
NOKIA
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.
125
NOKIA
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. How many bits needed for the buffer occupancy report. Agreed to have 4 tables, but now we need to agree on the tables. L2 based cell selection for faster cell change Nortel and Panasonic propose to have UE based cell change. Benefits questionable 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.
Content of the uplink MAC-signalling scheduling information:
Transport block sizes:
Serving cell change:
Minimum bit rate for 2ms TTI:

126 NOKIA
3GPP open issues, WG3 (NBAP, FP)

HARQ Failure indication signalling principles were agreed.
No CR yet implementing the agreement. No agreement on the exact nature of loss detection. Whether we will use Frame Sequence Number or Octet sequence number is FFS.
Iub congestion detection was agreed in principle.
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. 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 The needed header CRC length is FFS. Header is getting longer and more CRC bits may be needed.
Support of 2ms TTI bundling is already there in the frame structure.

FP Frame structure, a lot of things done
127
NOKIA
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
128
NOKIA
UTRAN Long Term Evolution
129
NOKIA
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
130
NOKIA
UTRAN Evolution
3.5G HSDPA/HSUPA 3.5G HSDPA/HSUPA
3GPP Rel.6 3GPP Rel.6
HSPA evolution HSPA evolution

Best CS + PS combined radio Current RAN architecture Spectrum shared with current 3G Reduced latency Full service continuity with 2G and 3G
3.9G new radio access 3.9G new radio access

Optimized for PS only New architecture New modulation Spectrum and bandwidth flexibility Further reduced latency Interworking with 3.5G evolution
131
NOKIA

Hsdpa/Hsupa High Speed Packet Access: March 22 2005 Salo, Finland

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hsdpa/Hsupa High Speed Packet Access: March 22 2005 Salo, Finland

Uploaded by

Copyright:

Available Formats

HSDPA/HSUPA High speed packet access

March 22nd 2005 Salo, Finland

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

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

WCDMA Performance in Commercial Networks

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

WCDMA Release99 Terminal Capability

Downlink 384 kbps Uplink 128 kbps

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

WCDMA Coverage Noise Limited

3 parallel users in WCDMA

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

WCDMA Coverage Interference Limited

3 parallel users in WCDMA

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

WCDMA Round Trip Time (RTT)

Download of 1st WAP Page Today

HTTP 384 kbps TCPrequest 32 RB reconfig kbps

0.7 s 0.4 2.0 s

0.5 0.4 0.6 s 0.9 s 0.7 0.4 0.5

Optimized 1st WAP Page Download

1st WAP Page Download Time

Summary of Voice Capacity Tests

Example last slide

Asia, high result

Asia, low result

Asia, drive test

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

Summary of Data Capacity Tests

Measured stationary Measured drive test

WCDMA High Speed Downlink Packet Access (HSDPA) of Release 5

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

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

High Speed Downlink Packet Access HSDPA

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

HSDPA General Principle

Terminal 2 Users may be time and/or code multiplexed

Multi-user Diversity (Fast Scheduling)

TTI 4 Scheduled user

Fast Link Adaptation in HSDPA

Instantaneous EsNo [dB]

C/I varies with fading

16QAM3/4 16QAM2/4 QPSK3/4 QPSK2/4 QPSK1/4

Time [number of TTIs]

Link adaptation mode

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

Release99 RRM Functional Split

Drift RNC Serving RNC

HSDPA Protocol Architecture

UE NAS RLC MAC WCDMA L1

SRNC RLC MAC-d FRAME PROTOCOL TRANSPORT

FRAME PROTOCOL TRANSPORT Iub/Iur

HSDPA user plane

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

Release99 vs HSDPA Retransmissions

Retransmission Packet Retransmission

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

There are two ways of operating:

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

New Node B functionality for HSDPA

Packets Flow Control

Scheduler & Buffer

New terminal functionality for HSDPA