Hspa

High Speed Packet Access HSDPA/HSUPA
October 8th 2007 Tampere

Harri Holma, Principal Engineer Antti Toskala, Senior Manager, Standardisation Nokia Siemens Networks, Finland
HSPA course.PPT / 08-10-2007 / AT&HH
Agenda
HSDPA in Release 5 HSUPA in Release 6 HSPA evolution in Release 7 HSPA evolution in Release 8
WCDMA High Speed Downlink Packet Access (HSDPA) of Release 5
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 Part of Release 5 First specifications version completed 03/02
Schedule in 3GPP

HSPA Pushes Functionalities to Base Station

HSDPA = High Speed Downlink Packet Access HSUPA = High Speed Uplink Packet Access HSPA = HSDPA + HSUPA HSDPA HSUPA WCDMA R99 uplink/downlink Mobile Base station Radio network controller RNC
HSPA scheduling and HSPA scheduling and retransmission control retransmission control in base station in base station
6 HSPA course.PPT / 08-10-2007 / AT&HH
WCDMA R99 scheduling WCDMA R99 scheduling and retransmission and retransmission control in RNC control in RNC
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

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

8
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 tree handling DL code allocation and code tree 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
10
Release99 vs HSDPA Retransmissions

Rel99 DCH/DSCH Rel5 HS-DSCH
RNC
Packet
Retransmission Packet Retransmission
BTS
RLC ACK/NACK
L1 ACK/NACK
Terminal
11
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.
12
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
13
Hybrid ARQ (HARQ): Chase Combining

Turbo Encoder
Rate Matching (Puncturing) Original transmission

Retransmission
Chase Combining (at Receiver)

14
Hybrid ARQ (HARQ): Incremental Redundancy

Turbo Encoder
Rate Matching (Puncturing) Original transmission

Retransmission
Incremental Redundancy Combining

15
HARQ Processes
Up to 8 processes can be configured per UE HARQ principle used is stop-and-wait-ARQ For continuous operation at least 6 processes is needed
1 HS-DSCH 2 3 4 5 6
From scheduler buffer
1st TX (new packet) 1st TX 1st TX
CK NA
K AC
2nd TX
CRC Check Result Fail Pass
RLC layer
New Functionality in RAN/Terminals

HSDPA Radio Resource & Mobility Management HSDPA Iub Traffic Management Larger Data Volume
RNC
BTS
Data Buffering ARQ Handling Feedback Decoding Flow Control Towards RNC Downlink Scheduling 16QAM Modulation
Terminal
ARQ Handling with Soft Value Buffer Feedback Generation & Transmission 16QAM Demodulation
17
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 For the market 1.8 Mbps and 3.6 Mbps capability expected initially, then 7.2 Mbps
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
19
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
HSDPA DL Channel Structure: HS-DSCH

HS-DSCH does not carry any physical layer control or pilot info, only user data (+ MAC layer/RLC layer headers) Only difference in the slot formats is the use of QPSK or 16QAM modululation
Data Ndata1 bits Tslot = 2560 chips, M*10*2 k bits (k=4)
Slot #0
Slot#1 1 subframe: Tf = 2 ms
Slot #2
Slot format #i
Channel Bit Rate (kbps)
Channel Symbol Rate (ksps) 240 240
SF
Bits/ HSDSCH subframe 960 1920
Bits/ Slot
Ndata
0(QPSK) 1(16QAM)
21
480 960
16 16
320 640
320 640
HS-SCCH
The HS-SCCH is fixed data rate channel with SF 128 (60 kbps) First part carries

code-set info Modulation info
Channelisation codes Modulation
Transport Block Size HARQ Process Redundancy and Constellation Version New Data Indicator UE Specific CRC Attachment
Second Part
Channel coding Transport-block size & Rate Matching Hybrid-ARQ process Redundancy and constellation version New data indicator UE Specific Additionally UE identify information Masking is used target the information to
Channel coding & Rate Matching
correct user
To separate which of the 4 HS-SCCHs UE needs to decode (UE specific masking) Decoder matrix to be observed..
Physical Channel Mapping
HS-SCCH
HS-DSCH TX Chain
CRC Attachment Physical Channel Segmentation
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
Interleaving
Interleaving
Code Block Segmentation
16QAM Constellation Re-arrangement
Channel Coding
Physical Channel Mapping
Interleaving (two identical interleavers with 16QAM TTIs) Constellation rearrangement (same bits not in same constellation point between retransmissions
HARQ Functionality
HS-PDSCHs
23
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.)
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
25
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
(20,5)
For CQI one of the 0 .. 30 values transmitted (one unused value) 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 Mi,2 Mi,3 0 0 0 1 0 0 1 0 0 0 1 0 0 1 0 1 1 0 1 1 0 0 0 1 0 0 1 1 0 1 1 0 1 0 1 1 0 1 1 Party omitted 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
26
HS-DPCCH Slot Format

The HS-DPCCH fields may have different power offsets One may also repeat the ACK/NACK and/or CQI over more than one subframe
This
is needed for cell edge operation (subject to cell edge coverage level) ACK/NACK CQI
Power offset As configured 2560 Chips 5120 Chips
One HS-DPCCH subframe of 2 ms
HS-DPCCH is symbol aligned with the uplink DPCCH/DPDCH BTS channel estimation done based on DPCCH (which carrier TPC, Pilot and TFCI)
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
28
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
29
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 QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK 16-QAM 16-QAM Reference power Number of Modulation adjustment HS-PDSCH Out of range 0 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
31
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 Node B RNC
32
HSPA Mobility Procedure

UE Node-B #1 Node-B #2 RNC
t1
Measurement report t2 Radio link reconfiguration and AAL2 setup to Node-B #2 t3 Reroute data from Node-B #1 to Node-B #2
Radio bearer reconfiguration RLC ACK

HS-DSCH from Node-B #1
B t4
HS-DSCH from Node-B #2
Radio bearer reconfiguration complete Radio link reconfiguration and AAL2 deletion to Node-B #1 A = procedural delay B = gap in data flow
HSDPA & Compressed mode

The inter-frequency measurement is handled by scheduling HS-SCCH/HS-PDSCH are always trasnsmitted fully or then not at all if there is any overlapp during the 2 ms TTI Alternatively one can switch back to DCH for inter-frequency measurements
DL DCH for Terminal 1
HS-SCCH
Compressed frame
HS-DSCH 2 ms
Not permitted HS-DSCH TTI for Terminal 1
HS-DSCH vs. DCH

When compared to DCH, the key difference is the replacement of power control with link adaptation and L1 HARQ. Also the multicode operation has been extended. Feature Variable spreading factor Fast power control Adaptive modulation and coding Fast L1 HARQ BTS based scheduling Multi-code operation DCH No Yes No No No Yes HS-DSCH No No Yes Yes Yes Yes, extended
35
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
36
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
37
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 = Code which cannot be allocated at the same time as C3(1) = Code which can be allocated at the same time as C3(1)
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 ]
...
... ... ...
...
... ... ... ... ...
... ...
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 ]
...
...
C3(6) = [ 1 0 0 1 1 0 0 1 ] C2(3) = [ 1 0 0 1 ]
. .... .
... ...
Spreading factor: SF = 1
38
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 signaling

Parameters for Node B resource allocation , to indicate e.g. which HS-SCCH use and which codes are available for HS-DSCH as well as how much power to use for HSDPA. Scheduler parameters, to control the scheduler behavior, such as scheduling priority indicator and guaranteed bit rate Terminal specific parameters, such a terminal capability and terminal specific HSDPA parameters (like the set of HS-SCCH codes the terminal is monitoring)
UE capability Data + Scheduling priority, discard timer, resources, CQI parameters Data + QoS parameters (larger data rates than Rel99) PS Core
Iub Node B
Iu-ps RNC
HSDPA Data Rate on different interfaces

Release99 DCH
Uu Iub Iu-ps Data from GGSN
Terminal
DCH Peak Rate: 384 kbps
Node B
RNC
SGSN
QoS Parameter: Maximum Bit Rate: 384 kbps
Iub Bit Rate: 0 - 384 kbps
Release 5 HSDPA
Uu Iub Iu-ps Data from GGSN
Terminal
Node B
RNC
SGSN
QoS Parameter: Maximum Bit Rate: 1 Mbps
HS-DSCH Peak Rate: 7.2 Mbps over 2 ms

Iub Bit Rate: 0 - 1 Mbps
Iub Flow Control

RNC Flow control is needed To avoid buffer overflow In Node B One unit responding to Flow control in RNC can maximise the Iub usage
Maximise Iub capacity utilisation in response to credits
Data
Increase Credits to UE1, Reduce Credits to UE2
BTS
Scheduler buffer level For UE1 Scheduler buffer level For UE2
UE2 with low CQI UE1 with high CQI

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 Performance
43
HSDPA Peak Data Rates

Max Layer 1 and Layer 2 (RLC) throughput shown below Max application layer throughput can be very close to RLC throughput
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
Max L1 data rate 1.8 Mbps 3.6 Mbps 7.2 Mbps 10.7 Mbps 14.0 Mbps
Max RLC data rate 1.6 Mbps 3.36 Mbps 6.72 Mbps 9.6 Mbps 13.3 Mbps
Phase 1 Phase 2
44
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]

Link Simulations in Fading Channel

Including Link Adaptation, CQI Errors and Feedback Delay
12 5 codes, PedA 5 codes VehA 5 codes fit 10 codes PedA 10 codes VehA 10 codes fit 15 codes PedA 15 codes VehA 15 codes fit
10 Mbps requires very high SINR >30 dB

15-code
10
Throughput (Mbits/s)
10-code
3 Mbps requires very high SINR >24 dB

5-code
0 -10
-5
10
15 20 SINR(dB)
25
30
35
With low SINR < 5 dB, 5-code HSDPA gives similar throughput as 10/15-code 40 HSDPA since the throughput is interference, not code limited
46
HSDPA SINR Definition

SF16 = HS-DSCH spreading factor = 16 PHS-DSCH = Received power of HS-DSCH channel Pown = Own cell interference with orthogonal codes Pother = Other cell interference Pnoise = Receiver thermal noise = Own cell orthogonality
SINR = SF16
SINR is increased with

PHS DSCH (1 ) Pown + Pother + Pnoise
Higher HS-DSCH power network planning and dimensioning Less own cell and other cell interference network planning and dimensioning Better orthogonality multipath propagation or mobile equalizer
47
HSDPA Data Rate vs RSCP

RLC throughput shown, 5 codes, total BTS power 20 W, Release 99 power 0-10 W
4000 3500 3000 2500 kbps 2000 1500 1000 500 0 -115 15 W HS-DSCH 10 W HS-DSCH 5 W HS-DSCH
More power increases data rate
-110
-105
-100 -95 CPICH RSCP [dBm]
-90
-85
-80
48
HSDPA Scheduling and Cell Capacity
49
Fast Proportional Fair 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 In practise, the gain in cell capacity is up to 30%
Mk
Rk [n] Tk [n]
Rk = instantaneous supported data rate for user k based on CQI report Tk = average throughput for user k with 100-200 ms averaging period Mk = selection metric where higher value gives higher probability of being scheduled
51
3GPP HSDPA Terminal Performance Requirements

Performance requirements Minimum requirement Enhanced type 1 Baseline receiver 1-antenna Rake 2-antenna Rake 3GPP Release Release 5 Release 6 Performance gain Basic receiver Better performance also against other cell interference with 2 antennas. HSDPA reference receiver for relative LTE performance evaluation. Improved performance against intra-cell interference Combines the gain mechanisms of intracell interference mitigation and receiver diversity
Enhanced type 2 Enhanced type 3
1-antenna Equalizer 2-antenna Equalizer
Release 6 Release 7
52
HSDPA Capacity [kbps/Sector/5 MHz]

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.5 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.5 Mbps 15-code BTS and dual antenna UE provides 4 Mbps
Maximum HSDPA Subscribers

Traffic volume based dimensioning
Cell capacity 2.5 Mbps Convert Mbps to GBytes 3600 seconds per hour Busy hour average loading 60% Busy hour carries 20% of daily traffic 30 days per month 3 sectors per site 1 GB traffic per user Total From simulations / 8192 x 3600 x 60% / 20% x 30 x3 / 1 GB (300 GB/site/month) 300 subs/site
Data rate based dimensioning

Cell capacity 2.5 Mbps Required user data rate Overbooking factor 3 sectors per site Total From simulations 0.5 Mbps 20 x3 300 subs/site
54
HSDPA Measurements
55
Data Rate in Elisa Network, 3xE1 Site
Stabile approx 400 kB/s = 3.28 Mbps which is max application bit rate with 3.6 Mbps L1 capability terminal
56
HSDPA Round Trip Time

200 180 160 140 120 [ms] 100 80 60 40 20 0
HSDPA R5 <80 ms on average WCDMA R99 130 ms on average (384/128 kbps)
WCDMA (128/384 kbps) HSDPA (384 kbps/1.8 Mbps)
57
HSDPA Multiuser Capacity Sharing

User throughput depends directly on the number of users while the cell throughput remains constant
Impact of 3 Users on Throughput

1600000 A pp lication Th ro ug hp u t (b p s) 1400000 1200000 1000000 800000 600000 400000 200000 0 Time (s)
1 user
2 users
3 users
2 users
1 user
58
Uplink Data Rate for HSDPA Feedback

TCP acknowledgements required approx 3% of the downlink bandwidth in typical TCP case. 64 kbps uplink is required to support 1.8 Mbps 128 kbps uplink is required to support 3.6 Mbps The uplink bandwidth may be smaller in case of multiple TCP packets are acknowledged at once.
42 kbps application layer data rate in uplink when 1.6 Mbps in downlink
59
HS-DSCH Cell Change Break

L1 break is 28 ms between correctly received blocks from Cell A and Cell B The break is short enough even for seamless VoIP voice service. For reference: the break in GSM handovers is typically >50 ms.
L1 log of received transport blocks

0,17:13:43:779,513,1,74,QPSK,16,3,0,0,62,0,4,5,2046,0,PASS 0,17:13:43:781,513,2,-,-,-,-,-,-,-,-,-,-,-,-,0,17:13:43:783,513,3,74,QPSK,16,2,0,1,63,0,4,5,2046,0,FAIL 0,17:13:43:785,513,4,-,-,-,-,-,-,-,-,-,-,-,-,0,17:13:43:787,514,0,74,QPSK,25,0,0,0,2,0,4,5,2404,0,FAIL 0,17:13:43:789,514,1,-,-,-,-,-,-,-,-,-,-,-,-,0,17:13:43:791,514,2,-,-,-,-,-,-,-,-,-,-,-,-,0,17:13:43:793,514,3,-,-,-,-,-,-,-,-,-,-,-,-,0,17:13:43:795,514,4,-,-,-,-,-,-,-,-,-,-,-,-,1,17:13:43:797, 1,17:13:43:799, 1,17:13:43:801, 1,17:13:43:803, 1,17:13:43:805, 0,17:13:43:807,920,0,10,QPSK,19,0,0,0,0,0,4,1,365,0,PASS 0,17:13:43:809,920,1,-,-,-,-,-,-,-,-,-,-,-,-,0,17:13:43:811,920,2,10,QPSK,19,1,0,0,1,0,4,1,365,0,PASS
Connected to Cell A
L1 break = 43:807 43:779 = 28 ms
Connected to Cell B
1 2
60
= Last correctly received transport block from Cell A = First correctly received transport block from Cell B
Asian customer
African customer
Middle East customer
62
61
10.00%
12.00%
14.00%
16.00%
18.00%
0.00%
2.00%
4.00%
6.00%
8.00%
70% of time CQI>15 and 16QAM would be used
Most typical CQI = 18 corresponds to 2.1 Mbps with BLER=10%
QPSK 16QAM
16 TB/week 800 sites 20 GB/week/site on average Single frequency layer shared by R99 and HSDPA
10 TB/week 1000 sites 10 GB/week/site on average Single frequency layer shared by R99 and HSDPA
Example Traffic Figures

Max rate with 16QAM
0.00% 20.00% 40.00% 60.00% % CDF
40 TB/week 2130 sites 20 GB/week/site on average Peak cells carry >1 Mbps/cell during busy hour and up to 8 GB/day Approx 400.000 subs approx 0.5 GB/sub/month (not flat rate) HSDPA carrier (two carriers)
80.00% 100.00%
CQI Reports in Live Network
C Q I C _DI Q S I T C _D I _C Q S L I T _ C _DI _C 0 ( Q S L H I T C _D I _ C _ 1 s dp Q S L (H a I w T _ C _ D I _C 2 ( s d p ) Q S L H a I w T _ C _D I _ C 3 ( s dp ) Q S L H a I w T _ C _ D I _C 4 ( s dp ) Q S L H a I w T _ C _D I _ C 5 ( s dp ) Q S L H a I w T _ C _ D I _C 6 ( s dp ) Q S L H a C I_D T_ _7 sd w) Q I_ IST CL (H paw C D I _ _8 s d ) Q S C ( p I H a T C _DI _C L_9 sd w) Q S L ( p I T _ H a C _DI _C 10 sd w) Q S L ( p I T _ H a C _DI _C 11 sd w) Q S L ( p I T _ H a C _D I _ C 1 2 s d w ) Q S L ( p I H a T C _ D I _C _1 3 s d w ) Q S L ( p I H a T C _D I _ C _1 4 s d w ) Q S L ( p I H a T C _ D I _C _1 5 s d w ) Q S L ( p I T _ H a C _D I _ C 1 6 s d w ) Q S L ( p I T _ H a C _ D I _C 1 7 s d w ) Q S L ( p I T _ H a C _D I _ C 1 8 s d w ) Q S L ( p I H a T C _ D I _C _1 9 s d w ) Q S L ( p I H a T C _D I _ C _2 0 s d w ) Q S L ( p I H a T C _ D I _C _2 1 s d w ) Q S L ( p I T _ H a C _D I _ C 2 2 s d w ) Q S L ( p I T _ H a C _ D I _C 2 3 s d w ) Q S L ( p I T _ H a C _D I _ C 2 4 s d w ) Q S L ( p I H a T C _ D I _C _2 5 s d w ) Q S L ( p I H a T C _D I _ C _2 6 s d w ) Q S L ( p I H a T C _ D I _C _2 7 s d w ) Q S L ( p I _ T _ H aw D _C 2 8 s d ) IS L ( p T_ _2 Hs aw C 9 dp ) L_ (H a 3 0 s d w) ( H pa s d w) pa w )
120.00%
HSDPA and Iub Capacity
63
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
Achievable Throughputs with 1-3 x E1

HSDPA throughput is in most cases Iub limited not radio limited
Iub 3*E1 Iub 1*E1
Iub 2*E1
Approx 400 kB/s = 3.28 Mbps which is max application bit rate with 3.6 Mbps L1 capability terminal
65
Iub Capacity with Multiple E1s

10.0 9.0 8.0 7.0 Mbps 6.0 5.0 4.0 3.0 2.0 1.0 0.0 1 x E1
5-code QPSK UE (Cat 12) 5-code 16QAM UE (Cat 6) 10-code 16QAM UE (Cat 8) 15-code 16QAM UE (Cat 9) Iub limit
2 x E1
3 x E1
4 x E1
5 x E1
6 x E1
7 x E1
Transport Solution Must Support High Data Rates

Peak Data rate 10 G
Downstream / Downlink
Ethernet
Upstream / Uplink
Ethernet GPON
1G
GPON DSM L3 VDSL2

ADSL2+ 10 M ADSL SHDSL.bis 1M E1 WCDMA EDGE evolution EDGE
100 M
LTE WiMAX HSPA
DSM L3 VDSL2 LTE WiMAX

SHDSL.bis ADSL2+ E1 ADSL
HSPA
WCDMA EDGE evolution EDGE EDGE
0,1 M
= Very high data rate solutions beyond 100 Mbps = High data rate solutions beyond 10 Mbps = Voice and low data rate solutions
HSDPA Terminals
68
HSDPA Terminals Initially

Data rate 1.8/3.6 Mbps downlink Data rate 384 kbps uplink Power class 3 = 24 dBm
Novatel
Option
Sierra wireless
69
Nokia Multimedia HSDPA Terminal N95

HSDPA 3.6 Mbps 5-megapixel Camera 2.6 display with 16 M colors Integrated GPS WLAN 802.11g Standard 3.5 mm audio jack Weight 120 g Volume 90 cc
Also E90 Communicator, 6110 Navigator, 6120, E51
70
WCDMA High Speed Uplink Packet Access (HSUPA) of Release 6
71
Outline
HSUPA Introduction HSUDA Protocol Architecture HSUPA Retransmissions HSUPA Peak Bit Rates HSUPA UE Capabilites HSUPA Channel Stuctures Uplink and Downlink Summary
72
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 Not fully mature version (see later 3GPP slides) In 3GPP specs with the name Enhanced uplink DCH (E-DCH)
Schedule in 3GPP

73
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 Additions to physical layer (WCDMA L1) Additions to user plane Iub/Iur DCH data stream protocol (Frame Protocol)
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 + 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 Mean: 4.1 (dB) StD: 1.2 (dB) 0.5 RNC sheduling Node B scheduling
0.4
Operation point can be increased because variance is reduced.
0.3
0.2
0.1
10
NR [dB]
76
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
77
Scheduling in soft handover

There is one serving cell Serving cell sends either up or down command, also the absolute grant channel is monitored from serving cell only Other cells in the active set (assuming they also support HSUPA) send only relative grant down commands Those can be configured in such a way that multiple terminals listen to same command -> overload handling
Ab
Serving Cell
Up
so l
/D
u te
E-D CH
ow
Gr
n /H
ant
d at
old
E-DCH data Hold/Down
RNC
Part of active set
BTS
UE
78
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
Packet Reordering HARQ control and soft combining
AC K/
E-D CH
NA
d at
E-DCH data ACK/NAK
RNC
Correctly received packet
Node B
Terminal
79
Feedback from UE to BTS

The UE provides the BTS scheduler with (in MAC-e header) UE buffer occupancy: how much data in RLC buffers Information about the priority of the data in the buffer Available transmission power resource
In physical layer (E-DPCCH) the UE provides to BTS the following E-TFI indicating what is transmitted in the E-DPDCH Information of the HARQ redundancy version for the packet
MAC-e PDU on E-DPDCH (L2) E-DPCCH (L1)
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, I.e. have enough data in its buffers and would have sufficient power resource to transmit with a higher power than currently
80
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 Peak Bit Rates Initially 1.46-2 Mbps

Theoretical peak bit rate up to 5.76 Mbps

Two SF2 and two SF4 codes in parallel No channel coding, 0% initial transmission BLER Two SF2 codes reaches 2 Mbps (with 10 ms TTI)
Initial capability
Only 10 ms TTI expected to be supported initially

# of codes 2 x SF4 2 x SF2 2 x SF2 2 x SF2 + 2 x SF4 TTI 2 ms 10 ms 10 ms 2 ms 2 ms Max data rate 1.46 Mbps 2.0 Mbps 2.9 Mbps 5.76 Mbps * Devices not yet published, not 100% realiable
Phase 1
82
HSUPA Peak Data Rates

Theoretical peak bit rate up to 5.76 Mbps

Two SF2 and two SF4 codes in parallel No channel coding, 0% initial transmission BLER Ericsson RAN initial support only Category 3 with 2 x SF4 providing 1.46 Mbps
Max L1 data rate Max RLC data rate 10 ms 0.67 Mbps 1.38 Mbps 1.38 Mbps 1.88 Mbps 1.88 Mbps 1.88 Mbps 2 ms 1.28 Mbps 2.72 Mbps 5.44 Mbps
Initial capability Category 5 with 2 x SF2 providing 2 Mbps with 10 ms TTI
UE category 1 2 3 4 5 6
83
# of codes 1 x SF4 2 x SF4 2 x SF4 2 x SF2 2 x SF2 2 x SF2 + 2 x SF4
10 ms 0.73 Mbps 1.46 Mbps 1.46 Mbps 2.0 Mbps 2.0 Mbps 2.0 Mbps
2 ms 1.46 Mbps 2.9 Mbps 5.76 Mbps
HSUPA structures in more detail
84
HSUPA building blocks - data path

A new uplink data path below the RLC layer parallel to DCH

E-DCH - Uplink transport channel E-DPDCH - Dedicated physical data channel for E-DCH E-DPCCH - Dedicated physical control channel for E-DCH Iub Frame protocol frame for E-DCH E-DCH is parallel to and coexisting with the uplink DCH
DTCH DCCH
MAC-es PDUs MAC-e PDUs
DCCH DTCH
MAC-d
MAC-d
MAC-es / MAC-e MAC-e MAC-e EDCH FP
MAC-es
EDCH FP
PHY
PHY
TNL
TNL
UE
Uu
NodeB
Iub
SRNC
E-DCH in E-DPDCH, Control in E-DPCCH

MAC-es PDUs in E-DCH FP
HSUPA building blocks - HARQ

Uplink HARQ functionality and control
Synchronous N-process SAW HARQ Timing of the uplink packet defines to which HARQ process it belongs to Timing of the downlink ACK/NACK defines which packet is E-DPCCH carrying HARQ information to the Node B E-HICH carrying HARQ ACK/NACK back to the UE MAC-es in the RNC to reorder the packets arriving in disorder due to HARQ
Corresponding ACK or NACK
Downlink
E-HICH Node B processing UE processing 8 ms
E-DPCCH
Uplink
E-DPDCH E-DCH TTI 10 ms 10 ms 30 ms between end of 1st TX and start of retransmission (14 ms with 2 ms TTI) Potential retransmission
86
HSUPA UL/DL Timing

For the different TTIs, 2 ms and 10 ms, there is fixed number of ARQ subchannels

For 2 ms TTI there are 8 ARQ sub-channels For 10 ms TTI there are 4 ARQ sub-channels, see below
Note the difference to HSDPA, where number of ARQ sub-channel may be configured (up to 8) + need to signal in downlink which process in used (as e.g. downlink scheduling needs to have timing freedom)
E-HICH 8 ms E-DPCCH E-DCH
14 16 ms DL ACK/NACK E-DPCCH E-DCH
5.5 7.5 ms
UL
10 ms
30 ms (3 TTIs) Timing with 10 ms TTI
1st retransmission
HSUPA building blocks - Scheduling

Uplink Node B scheduling

E-RGCH and E-AGCH - DL physical channels for scheduling control Happy-bit on UL E-DPCCH to indicate Node B of the instantaneous UE status Scheduling Info in MAC-e header to give Node B more detailed information
E-DPDCH (SI in MAC-e header) E-DPCCH (happy bit) E-RGCH (Relative Grant) E-AGCH (Absolute Grant)
BTS
UE
RG and AG control the UEs maximum allowed E-DPDCH to DPCCH power ratio

RG carries one bit only: UP/DOWN by one step relative to currently used max E-DPDCH/DPCCH power ratio AG carries a command informing the UE of the E-DPDCH/DPCCH power ratio to be used at maximum See a separate slide

88
Happy-bit and SI provide the Node B with information of the UEs status
RNC is a master that provides the Node B scheduler with limits RNC can allocate non-scheduled transmissions for specific data flows over which the Node B has no control over Control over specific HARQ processes and data flows
Physical channels with HSUPA, HSDPA and DCH

DPCCH (Pilot, TPC, TFCI) DPDCH (DCHs) HS-DPCCH (CQI, ACK/NACK) E-DPCCH (RSN, H-bit, E-TFCI)
BTS
UE
N x E-DPDCH (E-DCH) DPCCH (Pilot, TPC, TFCI)* DPDCH (DCHs) HS-SCCH (TFRI, HARQ info) N x HS-PDSCH (HS-DSCH) E-RGCH (RG) E-AGCH (AG) E-HICH (ACK/NACK)
UPLINK

DPCCH is always present DPDCH needed for DCH HS-DPCCH used for HSDPA feedback E-DPCCH needed if E-DCH transmitted E-DPDCH needed if E-DCH transmitted
DOWNLINK

* Downlink DPCCH could be replaced with F-DPCH (TPC only) if no DL DCH configured
DPCCH is always present* DPDCH used for DCH HS-SCCH needed if HSDPA transmitted HS-PDSCHs needed if HSDPA transmitted E-RGCH needed if RG transmitted E-AGCH needed if AG transmitted E-HICH needed if E-DCH received
Uplink physical control channels with HSUPA

DPCCH is required for power control and uplink channel estimation
Must be present even if the DPDCH is not used (and HS-DPCCH if HSDPA is used) Delivers 10 information bits related to the E-DPDCH transmitted in parallel

E-DPCCH - (E-DCH Dedicated Physical Control Channel)
Retransmission Sequence Number for HARQ, 2 bits Happy-bit for scheduling, 1 bit E-TFCI 7 bits 30 channel bits result with 2 ms sub-frame
SF256 physical channel (10 channel bits per slot)
With 10 ms E-DCH TTI the 2 ms sub-frame is repeated 5 times

Data: 10 info bits coded to 30 channel bits
3 slots, 7680 chips
E-DPCCH
Slot#0
Slot#1
2 ms Sub-Frame
Slot#2
Slot#i
Slot#14
10ms Radio Frame

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
91
Uplink physical data channel with HSUPA

DPDCH is needed if uplink DCHs are configured (AMR speech etc.) E-DPDCH (E-DCH Dedicated Physical Data Channel) Used to transmit the coded E-DCH transport channel Turbo coding, 24 bit CRC, HARQ with incremental redundancy SF 256/128/64/32/16/8/4/2 (SF 256/128 late additions!) Two TTI lengths supported, 2 ms and 10 ms 10 ms TTI better from Range point of view
E-DPDCH Data: 2560/SF bits
1 slot, 2560 chips, 2560/SF b its
Slot#0
Slot#1
2 ms Sub-Frame
Slot#2
Slot#i
Slot#14
10ms Radio Frame

HSUPA Physical channels in the downlink

E-HICH & E-RGCH share the same structure and the same code channel

E-HICH transmits one ACK/NACK per received uplink E-DCH TTI E-RGCH transmits UP/DOWN (dtx for hold) scheduling commands A 40-bit long orthogonal sequence is QPSK modulated and sent in one slot.

Up to 40 sequences can be fitted in one SF128 code channel E-HICH and E-RGCH meant to a UE must be in the same code channel
3-slot long (2 ms) sub-frame is formed by concatenating 3 sequences E-HICH length

2 ms - From all cells in the E-DCH active set with 2 ms E-DCH TTI 8 ms - (4 times repetition) from all cells in the E-DCH AS with 10 ms TTI 2 ms - Sent by the Serving HSUPA RLS with 2 ms E-DCH TTI 8 ms - (4 times repetition) Sent by the Serving HSUPA RLS with 10 ms E-DCH TTI 10 ms - (5 times repetition) Sent by cells not belonging to the Serving HSUPA RLS
bi,39 Tslot = 2560 chip
E-RGCH length

bi,0 bi,1
Slot #0
Slot #1
Slot #2
Slot #i
Slot #14
1 subframe = 2 ms 1 radio frame, Tf = 10 ms

E-HICH/E-RGCH (sub-)frame structure
HSUPA Physical channels in the downlink

E-AGCH
SF256 channel transmitting 6 information bits and a 16-bit UE-specific CRC 5 bits for E-DPDCH/DPCCH power ratio 1 bit for process applicability 16-bit CRC used to identify to which UE the AG is for 1/3 convolutional coding, resulting 72 bits 2 ms sub-frame structure, 60 channel bits per sub-frame 12 bits from the 72 punctured away to fit in the subframe Sub-frame is repeated 5 times when 10 ms E-DCH TTI is used
E-AGCH (sub-)frame structure
E-AGCH 20 bits Tslot = 2560 chips
xag,1, xag,2,..., xag,w ID specific CRC attachment
y1, y2,..., yw+16
Channel coding
z1, z2,..., z3x(w+24)
Rate matching
r1, r2,..., r60 Physical channel mapping
E-AGCH
Slot #0 Slot #1 Slot #2 Slot #i Slot #14
Coding chain for E-AGCH
1 subframe = 2 ms 1 radio frame, Tf = 10 ms
94
E-DCH (E-DPDCH) Coding

One transport block once per TTI 24 bit CRC Code block segmentation similar to DCH 1/3 turbo coding (as rel99) Most of the blocks similar to Release99 HARQ handling additional functionality
Transport block
E-DCH
CRC attachment Code block segmentation Channel coding
Physical layer HARQ functionality/ rate matching
Physical channel segmentation Interleaving and physical channel mapping E-DPDCH#1

E-DPDCH#n
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
96
HSDPA vs HSUPA Concepts

HSUPA is like reversed HSDPA, except HSDPA HSDPA
Modulation Modulation Soft handover Soft handover Fast power Fast power control control Scheduling Scheduling Non-scheduled Non-scheduled transmission transmission QPSK and 16-QAM QPSK and 16-QAM No No No No Point to Point to multipoint multipoint No No
HSUPA HSUPA
BPSK and Dual-BPSK BPSK and Dual-BPSK Yes Yes Yes Yes Multipoint Multipoint to point to point Yes, for minimum/ Yes, for minimum/ guaranteed bit rate guaranteed bit rate
Efficient UE power amplifier
Required for near-far avoidance Scheduling cannot be as fast as in HSDPA Similar to R99 DCH but with HARQ
HSUPA could be better described as Enhanced DCH in the uplink than reversed HSDPA
HSUPA vs UL DCH
HSUPA (E-DCH) is an uplink DCH with Node B based HARQ and scheduling and true multicode support Feature Variable spreading factor Multicode transmission Fast power control Soft handover Adaptive modulation BTS based scheduling Fast L1 HARQ DCH Yes Yes
(No in practice)
HSUPA Yes Yes Yes Yes No Yes Yes
HSDPA No Yes No No
(associated DCH only)
Yes Yes No No No
Yes Yes Yes
98
HSUPA Iub signaling

Parameters for Node B resource allocation , to indicate e.g. which codes to use for DL signaling channels, which signatures to use for which UE etc. Scheduler parameters, to control the scheduler behavior, such as scheduling priority and guaranteed bit rate Terminal specific parameters, such a terminal capability and peak rate to be used
UE capability Scheduling priority, resources, data rates Control
QoS parameters PS Core
Data
Iub Node B RNC
Iu-ps
99
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. Fundamental differences to DCH not big as with HSDPA
100
HSUPA Performance
101
Benefit of Fast Retransmissions

HSUPA allows to use higher BLER because of fast retransmissions
6 No HARQ HARQ (IR) 5
Effective Eb/N0 [dB]
4 3
R99
0.8 dB gain providing 20% higher cell throughput
2 1 0
HSUPA
10
10 BLEP at 1st transmission
10
102
Benefit of Node-B Based Fast Scheduling

VA 3 km/h 20 users/cell 5% NR outage = 6 dB 0.8 RNC PS 0.7 0.6 Node B PS
Probability
0.5 0.4 0.3 0.2 0.1 0 1 2 3 4 5 Noise Rise [dB] 6
5-10% cell throughput gain
103
HSUPA Capacity
Uplink cell throughput [kbps] 1600 1400 1200 1000 kbps 800 600 400 200 0 WCDMA R99
HSUPA Release99
HSUPA
HSUPA Coverage
2000 1800 1600 RLC data rate [kbps] 1400 1200 1000 800 600 400 200 0 -120 -115 -110 -105 -100 -95 RSCP [dBm] -90 -85 -80
Uplink data rate limited by UE tx power
High data rates if RSCP > -100 dBm
105
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
Cell throughput gain
Savings in BB capacity costs
Peak data rate 1.4-5.8 Mbps

Higher add-on PS Traffic
Lower costs in transport
Coverage of high data-rate
Quality of end user experience

Higher add-on PS traffic
Saves BTS sites Savings in (~10%) and adds transport in PS traffic Dedicated VCC solution max 25%
106
HSUPA Status in 3GPP
107
HSUPA Standardisation Timeline

03/04 Study item for 3GPP Release 6 completed and work item initiated 12/04 First versions of HSUPA specs published 03/05 Official work item completion date for RAN1/RAN2/RAN3 06/05 Specifications stabilising 09/05 Remaining open issues closed 09/05 Performance requirement work item completion (RAN4) 03/06 ASN.1 of RRC, NBAP and RNSAP protocols freezing
Backwards compatibility started
2003
3GPP study item
Study item completed
2004
2005
2006
2007
1st version in 3GPP spec
Official work item completion date
Issues closed, performance WI closed
ASN.1 frozen
Key 3GPP specifications affected by HSUPA

TS25.309; FDD Enhanced Uplink; overall description; Stage 2

06/05 version (v. 6.3.0) is quite mature, no major open issues 06/05 versions are mature and practically complete 06/05 version has the HSUPA UE categories, 06/05 version is still not fully stabile, user plane data flow is finalised, but the UE interaction with the scheduling commands requires further work 06/05 version requires still further work to align with stage 2 and physical layer. 06/05 versions quite mature, some alignment to stage 2 and L1 still to be done 06/05 version is mature and complete
TS25.211 - 25.215; Physical layer specifications TS25.306; UE radio access capabilities TS25.321; MAC specification TS25.331; RRC Protocol Specification

TS25.423/25.433; RNSAP/NBAP signalling TS25.427; Iur/Iub user plane protocols for DCH data streams Performance requirement specifications TS25.101, 104, 133, 141 And others
109
HSUPA measurements in Lahti 10.9.2007 Elisa Network, Ericsson RAN
110
Tested card
Option GlobeTrotter GT MAX HSUPA PCMCIA modem

Engineering sample Drivers 5.1.0.1071 Firmware 2.7.0
111
HSUPA Latency in the Field

HSUPA brings network latency below 70 ms HSUPA improves latency by 20 ms compared to HSDPA + R99 uplink
Channel HSDPA HSDPA + HSUPA Improvement with HSUPA
Ericsson Lahti live 90 ms 69 ms 21 ms
Nokia VF trial 84 ms 65 ms 19 ms
112
HSUPA Latency <45 ms

NSN Nokia End-to-end Measurement
Nokia Siemens networks Nokia HSUPA terminal prototype Node-B RNC Packet core
50 45 40 35 30 ms 25 RNC + core BTS + Iub Air interface UE
Server
Lab measurements Minimum = 38ms, Maximum = 57ms, Average = 42ms Minimum = 38ms, Maximum = 58ms, Average = 45ms Minimum = 39ms, Maximum = 52ms, Average = 41ms Minimum = 39ms, Maximum = 51ms, Average = 41ms
20 15 10 5 0 Latency
113
HSUPA Throughput with FTP

The bit rate steps are explained by the scheduling grant resolution
840 kbps 710 kbps 560 kbps
114
HSPA Evolution
115
UTRAN Evolution
HSDPA/HSUPA HSDPA/HSUPA 3GPP R6 3GPP R6
HSPA evolution HSPA evolution in R7/R8 in R7/R8

Best CS + PS combined radio Spectrum shared with current 3G Reduced latency Lower mobile power consumption Flat architecture option Simple upgrade on top of HSPA
LTE new radio LTE new radio access in R8 access in R8

Optimized for PS only New architecture New modulation Spectrum and bandwidth flexibility Further reduced latency
Similar technical solutions applied both in HSPA evolution and in LTE

3GPP Evolution in Release 5 Release 8

Long term evolution (LTE) + Basic HSDPA+HSUPA HSPA R5 HSPA R5
HSDPA 14 Mbps
HSPA evolution HSPA R7 HSPA R7

Continuous packet connectivity L2 optimization in downlink Enhanced FACH Flat architecture MIMO 64QAM downlink 16QAM uplink MBMS evolution
Further HSPA evolution 3GPP R8 3GPP R8

LTE: New PS only radio L2 optimization in uplink Enhanced RACH Enhanced UE DRX Flat architecture enhancements CS voice service over HSPA 64QAM+MIMO Downlink only broadcast Synchronized E-DCH.
HSPA R6 HSPA R6
HSUPA 5.76 Mbps MBMS
117
HSPA Deployment Schedule

HSUPA commercial 2007 HSPA evolution commercial 2009 LTE commercial 2010 and beyond
3GPP schedule 3GPP R5 2002 2003 3GPP R6 2004 2005 2006 3GPP3GPP R8 R7 2007 3GPP R6 2008 2009 2010
Commercial
3GPP R5
3GPP R7 3GPP R8
118
MIMO and 64QAM
119
HSPA Peak Data Rate Evolution

HSPA downlink data rate increases with 2x2 MIMO and 64QAM up to 42 Mbps and uplink data rate with 16QAM up to 11 Mbps LTE further increases the data rate beyond 100 Mbps with larger bandwidth of 20 MHz
3GPP R5
3GPP R6
te k peak ra Downlin
3GPP R71
3GPP R8 LTE: 170 Mbps HSPA: 42 Mbps2 LTE: 50 Mbps
14 Mbps 0.4 Mbps
14 Mbps 5.7 Mbps

e Uplink p
28
Mbps1
11 Mbps
ak rate
1With 2With
2x2 MIMO and 16QAM 2x2 MIMO and 64QAM likely for R8
120
Terminal Categories in Release 7

HSDPA
Category 12 5/6 7/8 9 10 13 14 15 16 Codes 5 5 10 15 15 15 15 15 15 Modulation QPSK 16QAM 16QAM 16QAM 16QAM 64QAM 64QAM 16QAM 16QAM MIMO 2x2 2x2 Coding rate Approx 1/1 5/6 Approx 1/1 5/6 Approx 1/1 Peak bit rate 1.8 Mbps 3.6 Mbps 7.2 Mbps 10.1 Mbps 14.0 Mbps 17.4 Mbps 21.1 Mbps 23.4 Mbps 28.0 Mbps 3GPP release Release 5 Release 5 Release 5 Release 5 Release 5 Release 7 Release 7 Release 7 Release 7
HSUPA
Category 3 5 6 7
121
TTI 10 ms 10 ms 2 ms 2 ms
Modulation QPSK QPSK QPSK 16QAM
Coding rate 1/1 1/1
Peak bit rate 1.4 Mbps 2.0 Mbps 5.7 Mbps 11.5 Mbps
3GPP release Release 6 Release 6 Release 6 Release 7
MIMO in HSDPA in Release 7

MIMO for HSDPA is based on D-TxAA (Double Transmit Adaptive Array) with fast L1 feedback 2x2 MIMO peak data rate 28 Mbps with 16QAM and up to 42 Mbps with 64QAM Feedback weights from UE
Base station
+
Terminal
Coding, spreading Demux Coding, spreading
Transmitter with 2 branches per sector
2 antennas & MIMO decoding capability
122
MIMO Modes
High CQI Multistream transmission
Double data rate
Low CQI
Single stream diversity transmission
Interference resistance
Single stream transmission is similar to Release99 closed loop transmit diversity, but with two differences

The preferred antenna weights are delivered from UE to Node-B on HS-DPCCH, not on DPCCCH The used antenna weights in downlink are signaled on HS-SCCH while in Release 99 no explicit signaling was used. Therefore, Release 99 UE had to use antenna verification to identify the used antenna weights.
123
MIMO Multistream Usage in Macro Cells

Percentage of MIMO Multistream Usage
100 % 90 % 80 % 70 % 60 % 50 % 40 % 30 % 20 % 10 % 0% Vehicular A, round robin Pedestrian A, round robin Vehicular A, proportional fair Pedestrian A, proportional fair
Multistream usage 70% with proportional fair
Multistream usage 15% with round robin
124
64QAM Modulation in Release 7

QPSK 2 bits/symbol 16QAM 4 bits/symbol 64QAM 6 bits/symbol
R5/R6 HSPA modulation

R7 HSPA modulation

Dowlink QPSK and 16QAM Uplink QPSK
Dowlink QPSK, 16QAM and 64QAM Uplink QPSK and 16QAM
125
64QAM Usage in Macro Cells

Percentage of 64QAM usage
100 % 90 % 80 % 70 % 60 % 50 % 40 % 30 % 20 % 10 % 0% Vehicular A, round robin Pedestrian A, round robin Vehicular A, proportional fair Pedestrian A, proportional fair
64QAM usage 35% in favorable case 64QAM usage 10% for 1-antenna terminals 64QAM usage 20% for 2-antenna terminals
1-rx 2-rx
These simulations with full loading. 64QAM usage is higher in fractional load case. If 2x2 MIMO is used, then 64QAM usage is <<10%.
126
Cell Capacity with Enhanced Terminals and R7 Features

Cell throughput
8.0 7.0 6.0 5.0 Mbps 4.0 3.0 2.0 1.0 0.0 HSPA 1-Equalizer (no 64QAM) HSPA R7 2HSPA R7 with Equalizer (no MIMO, no 64QAM MIMO, no 64QAM) HSPA R7 with MIMO+64QAM
+20% +40%
127
Uplink 16QAM
128
Performance of Uplink 16QAM with Equalizer

Up to 2x higher data rate in multipath channel with equalizer receiver compared to Rake receiver
Rake receiver
BTS equalizer
Above 7 Mbps with Ec/N0=15 dB
Max 3.3 Mbps with Ec/N0=15 dB
129
Enhanced Cell FACH (High Speed FACH)
130
Enhanced Cell_FACH Concept

R99 solution Cell_FACH state FACH HS-DSCH R7 solution Cell_FACH state
HS-DSCH HS-DSCH in CELL_DCH state
S-CCPCH
32 kbps
HS-PDSCH
Up to 14 Mbps
HS-PDSCH Up to 14 Mbps
1. 2. 3.
Benefits Seamless state transition since no physical channel reconfiguration Higher bit rate on CELL_FACH state (today 32 kbps for data) No changes to Release 5 physical channels (HS-DSCH and HS-SCCH)
131
Fast State Transitions with Enhanced FACH

Release 99 Release 6 RRC States PCH
RB reconfiguration Cell update and CRNTI allocation takes >300 ms
Release 7 RRC States
PCH
Immediate transmission w/o cell update. No PCH required.
FACH
RB reconfiguration No data flow during transition >500 ms
HS-FACH
Data flows on HS-FACH also during transition
DCH /HSPA
HSPA
132
Optimized Layer 2
133
Optimized Layer 2 Concept (Flexible RLC)

3GPP Release 6 RNC PDCP RLC
IP packet 1500 B RLC packet 40 B
3GPP Release 7 PDCP RLC

IP packet 1500 B RLC packet size flexible between 10B -1500 B
Node-B
MAC-hs
Transport block size depending on scheduling
MAC-hs
Transport block size depending on scheduling
UE MAC + RLC + PDCP

134
MAC + RLC + PDCP
Basic RLC functions are kept: Ciphering, polling, retransmission Smaller RLC overhead Less packet processing required in UE and in RNC No RLC optimization required for each service
Optimized Layer 2 RLC Header + Padding Overhead

Rel6: RLC PDU header 2 bytes; PDU size fixed to 336 bit Rel7: RLC PDU header 2 bytes; PDU size flexible from 80 12000 bits
50 % 45 % 40 % 35 % 30 % 25 % 20 % 15 % 10 % 5% 0% 0
Release 6 RLC (40-B RLC packet) Release 7 RLC (Flexible RLC)
500
IP packet size
1000
1500
Continuous Packet Connectivity
136
Continuous Packet Connectivity in 3GPP R7

Continuous packet connectivity includes
1. 2. 3.
Uplink discontinuous transmission Downlink discontinuous reception HS-SCCH less HSDPA for VoIP Low mobile power consumption for packet applications Higher capacity due to less interference transmitted
Web page download User reading web page User moved to FACH/PCH Connection goes immediately to gating mode to save mobile power when data transfer is over
Continuous packet connectivity gives

HSPA R6
HS-DSCH DPCCH
HSPA R7
HS-DSCH DPCCH
137
Continuous Packet Connectivity for VoIP

Continuous packet connectivity improves also the capacity of low data rate services, like VoIP Data can be transmitted in short bursts and discontinuous operation can be utilized between the bursts
WCDMA R99 CS voice DPDCH DPCCH 20 ms HSPA with continuous packet connectivity No transmission less power consumption and less interference
UE Radio Modem Power Consumption

Power consumption relative to continuous rx/tx
100 % 90 % 80 % 70 % 60 % 50 % 40 % 30 % 20 % 10 % 0% Tx/(Rx+Tx)=30% Tx/(Rx+Tx)=50% Tx/(Rx+Tx)=70%
VoIP assumptions - E-DCH activity 15% - DPCCH activity during E-DCH inactive 10% - DRX 60% Inactive user - E-DCH activity 0% - DPCCH activity during E-DCH inactive 10% - DRX 80%
VoIP call (2-ms TTI) Inactive user on Cell_DCH
70% savings in VoIP calls
85% savings when inactive
139
Uplink Gating Gain for VoIP Capacity

Reference case: Release 6 HSUPA Different configurations studied for signaling

OFF=0 means CQI sent simultaneously with data OFF=3 means CQI sent after data
Gating capacity gain 50%
From simulations it can be though concluded that for 50% improvement for uplink VoIP capacity could be achieved
140
VoIP Capacity
HSPA R7 VoIP can provide up to 2x higher voice capacity than CS voice
160 140 120 Users 100 80 60 40 20 0 WCDMA R99 CS voice
AMR12.2 kbps
Downlink Uplink
2x
HSPA R6 VoIP
HSPA R7 VoIP
VoIP Optimization Features in 3GPP Release 7

CS voice of Release 99 Packet bundling Packet retransmissions L1 control overhead Packet scheduling Advanced terminals Single packet transmission Retransmissions not possible due to excessive delay Continuous L1 control channel No scheduling No equalize HSPA VoIP of Release 7 Packet bundling Retransmissions possible due to fast L1 ARQ Low overhead due to fractional DPCH and discontinuous uplink Advanced HSDPA scheduling HSDPA equalizer
142
Voice Spectral Efficiency Evolution from GSM to LTE

20 x more users per MHz with 3GPP LTE than with GSM EFR! VoIP is the way to go for future voice in mobile systems
60 50 User per MHz 40 30 20 10 0 GSM EFR
CS voice
VoIP
GSM AMR
GSM DFCA
WCDMA HSPA R7 CS voice
LTE
Round Trip Time Evolution
144
HSPA Round Trip Time

End-to-end round trip time <30 ms expected with HSPA
UE tx x ms Align 1 = UE processing time = TTI alignment = 0..1 x TTI = Air interface transmission time HSUPA TTI Node-B rx 2 ms RNC+core 1 1 Node-B tx 2 ms Align+SCCH+HSDPA TTI 1 1.3 2 ms UE rx x ms = Network processing times
2 ms
Realistic RTT with HSPA evolution
Network RTT 13.3 ms
TTI align HSUPA TTI 1
3GPP limit for RTT (theory)
2 ms Align+SCCH+HSDPA TTI 1 1.3 2 ms
7.3 ms
145
Single Frequency MBMS

Carrier can be shared with unicast
Different scrambling codes Different cells = inter-cell interference
MBMS Release 6
Same scrambling code in all cells Different cells = multipath propagation

Dedicated MBMS carrier required
MBMS Release 7
146
HSPA+ Architecture Evolution
147
Architecture Evolution
Packet Domain User Plane
Flat architecture = single network element in user plane in radio network and in core network Same architecture in I-HSPA, LTE and in WiMAX
HSPA (3GPP R6) GGSN I-HSPA (3GPP R7) GGSN LTE (3GPP R8) SAE GW WiMAX ASN GW
SGSN
RNC
Ciphering and header compression
Node-B
Node-B with RNC functions
eNode-B
Base station
I-HSPA Specified as Part of 3GPP Release 7

3GPP Release 7 has specified flat architecture for HSPA A change to RANAP specification to extend the RNC-ID to allow it to be longer than 4096 values

Introduction of an Extended RNC-ID IE TS25.331, TS25.413, TS25.423, TS25.433, TS25.453, TS48.008, TS48.018
A clarifying description how existing 3GPP functionalities can be used to allow UE mobile-originated and mobile-terminated CS call re-direction
TR25.999, Section 7.1.4.4 CS Service in stand-alone scenario: Evolved HSPA system focuses on PS services. Due to the PS optimized architecture in the stand-alone scenario, the HSPA UE should be served in the evolved HSPA when it requests a PS service only, and in the legacy architecture (WCDMA or GSM) when it requests a CS service
Carrier sharing solution between RNC based architecture and flat architecture accepted using UE involved SRNS relocation procedure Soft handover optimization for Signalling Radio Bearers was included to Iur specifications
HSPA Evolution in Release 8
150
New Release 8 Items for HSPA Evolution

Approved in 3GPP RAN September 2007
New items in Release 8
Title
Enhanced Uplink for CELL_FACH State in FDD Enhanced UE DRX SRNS Relocation Enhancement Enhancement for HSPA Architecture Improved L2 for uplink CS voice service over HSPA HSDPA demodulation requirements for 16QAM and QPSK with 15-codes Synchronized E-DCH Continuation from Release 7 64QAM+MIMO Downlink only broadcast
Work or study item Work item Work item Work item Work item Work item Work item Work item Study item
Raporteur Nokia/NSN Nokia/NSN Nokia/NSN Nokia/NSN Ericsson Nokia/NSN Vodafone Nokia/NSN
Target completion 05/08 09/08 03/08 06/08 03/08 03/08 06/08 03/08
Work item Work item
Ericsson Ericsson
03/08 06/08
Note: 6 out of 8 new items have Nokia/NSN as raporteur

Enhanced RACH Item (One Proposal Below)

Fast access to high data rates also in uplink to complement R7 Enhanced FACH
1. PRACH preamble ramp-up phase with PRACH sub-channels and/or PRACH signature sequences reserved for enhanced RACH 2. Acquisition indication and E-DCH resource allocation, extended AICH 3. UL data transmission 4. MAC-e header with UE-id for contention resolution 6. E-DCH with a new data rate after reception of E-AGCH
5. Collision resolution: UE id is returned on E-AGCH
E-HICH F-DPCH
E-HICH
E-HICH
#0 #1 #2 #3 #4 #5 AICH
E-AGCH
E-DPDCH E-DPDCH E-DPDCH E-DPDCH E-DPCCH E-DPCCH E-DPCCH E-DPCCH #1 #2 #3 #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10#11 #12 #13 #14 #0 DPCCH #4 #5 #6 #7 #8 #9 #10#11 #12 #13 #14 #0 DPCCH #4 #5 #1 #2 #3 DPCCH DPCCH
Enhanced UE DRX Item

UE must decode all FACH frames in Release 7 receiver is running continuously eating batteries The target in Release 8 is to enable Discontinuous reception (DRX) on FACH Example keep alive transmission below, where FACH DRX can lead to considerable battery savings The work item also explores the state transition to PCH without any RRC signalling
RACH FACH in R7 FACH in R8
= Keep alive transmission = No data coming to UE, but UE must still decode all FACH frames = UE uses discontinuous reception when no data coming
153
RRC States in 3GPP Release 7/8

The RRC states remain in Release 7/8 (DCH, FACH, PCH, idle), but the states will have more similarities and the state transitions will be faster Similar transport channels in DCH and FACH DRX can be used in all states
DRX period longer in PCH state than in DCH or FACH
Cell_DCH
Cell_FACH
Cell_PCH
Direct mapping to HS-SCCH
HS-DSCH
DRX in Release 7 DRX in Release 8
PCH
Long DRX periods (>500 ms)
E-DCH
DTX in Release 7
Transmission only when needed
Improved L2 in Uplink
Follows the same principle that was applied in downlink in Release 7 The benefits

Reduced L2 overhead MAC + RLC Lower processing power requirements in UE and in RNC No RLC optimization required per service
155
CS Voice over HSPA Concept

The target to use HSPA transport channels for carrying CS voice service to get end user and operator performance benefits No difference from service point of view compared to current CS voice : CS core is not aware of radio mapping and roaming and charing remains the same No changes to HSPA Layer 1 required
Current CS voice CS voice over HSPA VoIP PS core Dejitter buffer Under discussion PDCP1 UM RLC
1IP
CS core Application layer Layer 2 TM RLC Transport channel

DCH
HS-DSCH + E-DCH
2TM=transparent
3UM=unacknowledged
header compression mode mode
CS Voice over HSPA Benefits Compared to CS Voice over Release 99 Channels

Improved talk-time

Uplink gating and downlink DRX can be used according to Release 7 Continuous packet connectivity (CPC) Talk time improvement expected clearly more than 50% Core signalling runs fast on HSPA HSPA allows asynchronous RAB Setup without slow DCH reconfiguration procedures UE-UE call setup time could ideally be below 1 s Equaliser, L1 retransmissions, uplink gating, HS-SCCHless features. No VoIP related overhead required : no IP, RTP headers
Faster call setup time

Higher capacity

157
CS Voice over HSPA Dejitter Buffer

L1 retransmissions and downlink scheduling will cause delay fluctuations. The order of the packets may also change in L1 processes Dejitter buffer is required in RNC in uplink and internally in UE in downlink to hide the delay variations Dejitter buffers are not specified in 3GPP. The requirements for UE VoIP dejitter developed in 3GPP (memory, etc) can be reused for CS-HSPA
Dejitter buffer in RNC
2 1
RNC
CS core
158
Synchronized E-DCH Motivation

HSPA uplink cell throughput is low compared to traffic requirements and compared to LTE

Expected traffic asymmetry DL:UL 2:1 HSPA downlink is 72% x LTE while uplink is 45% x LTE
Preferably 50% uplink cell throughput gain required in HSUPA

Cell throughput 5 MHz
10 9 8 7 Mbps 6 5 4 3 2 1 0 Downlink
HSPA LTE
Uplink
Synchronized E-DCH Concept

Orthogonal uplink transmission by using the same scrambling code for all intra-cell users with synchronous transmission.
Expected uplink capacity gain up to 70% in macro cells
Simple upgrade to terminal transmission and BTS reception since existing channels are used Soft handover less important than in HSUPA R6 well suited for I-HSPA Required changes to 3GPP specifications and implementations

new downlink scheduling channels slow timing advance adjustment updated scheduling algorithm
Node-B based scheduling in HSUPA makes synchronous transmission more feasible compared to 3GPP USTS 2001
160
Synchronized E-DCH Code Allocation

Uplink code tree allocation given with HS-SCCH like channel (CRC for reliability) with 2 ms x N duration (range for N to be defined) based in happy bit/HSUPA MAC header info
These codes cannot be used at the same time as C3(1)
C2(0) = [ 1 1 1 1 ]
...
C3(0) = [ 1 1 1 1 1 1 1 1 ]
...
... ...
Code allocated with HS-CACH
C3(1) = [ 1 1 1 1 0 0 0 0 ]
C1(0) = [ 1 1 ] C2(1) = [ 1 1 0 0 ] C3(3) = [ 1 1 0 0 0 0 1 1] C3(2) = [ 1 1 0 0 1 1 0 0 ]
... ...
... ... ... ... ... ... ... ...
... ...
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 ]
...
...
C3(6) = [ 1 0 0 1 1 0 0 1 ] C2(3) = [ 1 0 0 1 ] C3(7) = [ 1 0 0 1 0 1 1 0 ]
. .... .
... ...
...
...
Codes at SF 256 allocated each users DPCCH and E-DPCCH
SF = 2
SF = 4
SF = 8
Synchronized E-DCH Timing Control and Soft Handover

No soft handover intended for data (as other Node B would have to detect the code allocation blindly (not desirable to signal all the time, keeping EDPCCH unchanged expect spreading/scrambling code different that usually) F-DPCH+ provides now both power control and uplink timing control (latter e.g. by puncturing some of the power control commands Timing adjustment resolution e.g. 1/6 to chips in order not to mandate a particular sampling rate
F-DPCH Node B F-DPCH+, O-HSUPA, HSDPA
Timing advance command rate max. 40 Hz (investigated in 2001 with USTS)
Node B
Architecture Work Items

SRNS Relocation Enhancement
Approved as the continuation of the HSPA Architecture Evolution work, aiming at optimizing the relocation procedures. The results may be applicable for both legacy and flat UTRAN architectures.
Enhancement for HSPA Architecture
Continuing the HSPA architecture evolution work on the topics of e.g., optimizing the RRM and introducing MBMS for a flat architecture.
163

Hspa

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

Hspa

Uploaded by

Copyright:

Available Formats

High Speed Packet Access HSDPA/HSUPA

October 8th 2007 Tampere

HSPA course.PPT / 08-10-2007 / AT&HH

HSPA course.PPT / 08-10-2007 / AT&HH

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

HSPA course.PPT / 08-10-2007 / AT&HH

HSPA course.PPT / 08-10-2007 / AT&HH

High Speed Downlink Packet Access HSDPA

HSPA course.PPT / 08-10-2007 / AT&HH

HSPA Pushes Functionalities to Base Station

HSDPA General Principle

Terminal 2 Users may be time and/or code multiplexed

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

HSPA course.PPT / 08-10-2007 / AT&HH

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

HSPA course.PPT / 08-10-2007 / AT&HH

Release99 vs HSDPA Retransmissions

Retransmission Packet Retransmission

HSPA course.PPT / 08-10-2007 / AT&HH

There are two ways of operating:

HSPA course.PPT / 08-10-2007 / AT&HH

Rate Matching (Puncturing)

HSPA course.PPT / 08-10-2007 / AT&HH

Hybrid ARQ (HARQ): Chase Combining

Rate Matching (Puncturing) Original transmission

Chase Combining (at Receiver)

HSPA course.PPT / 08-10-2007 / AT&HH

Hybrid ARQ (HARQ): Incremental Redundancy

Rate Matching (Puncturing) Original transmission

Incremental Redundancy Combining

HSPA course.PPT / 08-10-2007 / AT&HH

From scheduler buffer

1st TX (new packet) 1st TX 1st TX

CRC Check Result Fail Pass

New Functionality in RAN/Terminals

HSPA course.PPT / 08-10-2007 / AT&HH

Adaptive Modulation QPSK and 16QAM

HSDPA Category 11 12 1/2 3/4 5/6 7/8 9 10

10 Codes 7.2 Mbps -

15 Codes 10.1 Mbps 14.0 Mbps

HSPA course.PPT / 08-10-2007 / AT&HH

HSDPA DL Channel Structure

Control data Control data

User data User data

HSDPA DL Channel Structure: HS-DSCH

Channel Bit Rate (kbps)

Channel Symbol Rate (ksps) 240 240

Bits/ HSDSCH subframe 960 1920

HSPA course.PPT / 08-10-2007 / AT&HH

code-set info Modulation info

Channelisation codes Modulation

Channel coding & Rate Matching