Happy Bit 6g31

HSUPA (E-DCH) introduction & parameters Jens Kuhr – Network Engineering COO RA RD SA NE

For internal use 1 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

Outline HSUPA Channels HSUPA Scheduling mechanism HARQ Process HSUPA RAB-Handling HSUPA Mobility aspects HSUPA ission Control HSUPA Congestion Control HSUPA OLPC UE categories + E-TFCI selection

For internal use 2 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

Outline • HSUPA (High Speed Uplink Packet Access) is used to improve uplink data rates in WCDMA networks.

• It is reusing the available infrastructure by using enhanced techniques (e.g. adaptive coding) thus allowing to make better use of the available ressources.

• Provides higher peak rates and increases coverage for high datarates • Shorter round trip times (RTT) make the HSPA WCDMA network more interesting for real time applications like online gaming

• HSUPA uses an enhanced dedicated transport channel in uplink (E-DCH), unlike HSDPA, where only one downlink channel is shared among the s.

• HSUPA is specified for data rates of up to 5.76 Mbps

For internal use 3 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

Comparison between HSUPA and HSDPA Similarities with HSDPA: - NodeB controlled scheduling - HARQ process - Shorter TTI than classic DCH (10ms, 2ms (HSDPA 2ms TTI only)) - Fast link adaptation techniques

Differences to HSDPA: - dedicated channel (E-DCH) instead of shared channel in HSDPA - no adaptive modulation - full mobility (soft handover possible)

Like HSDPA, HSUPA is based on scheduling in the NodeB, link adaptation and HARQ process For internal use 4 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

In UMR and RAS currently only 10ms TTI implemented.

HSUPA Principles

1-4 Code Multi-Code transmission

TTI = 2 / 10 ms

Hybrid ARQ with incr. redundancy

Fast Power Control

Benefit Higher Uplink Peak rates: 2-5.76 Mbps Higher Capacity: +50-100% Reduced Latency: ~50-75 ms

For internal use 5 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

Scheduling

HSPA Scheduling

D

CH D

-A

CH

-B

H DC

-C

Node B Rel. 99

Dedicated pipe for every UE

h Sc

e

ng i l du

-A

H DC E

-B

H DC E

C B, , A

Node B w/ HSDPA 3GPP Rel. 5

Fast pipe is shared among UEs For internal use 6 © Nokia Siemens Networks

H DC E

HSUPA / JKuhr / September 2007

-C

Node B w/ HSUPA 3GPP Rel. 6

Dedicated pipe for every UE in UL Pipe (codes and grants) changing with time E-DCH scheduling

HSUPA Channels - Uplink

For internal use 7 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

Channel mapping • For HSUPA, the E-DCH is introduced as a new transport channel for carrying data on the uplink. • On physical layer, this translates into 2 new uplink channels.

E-DCH

E-DPDCH

For internal use 8 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

Transport channel

E-DPCCH

Physical channel

E-DCH: Enhanced Dedicated Channel • Dedicated uplink transport channel • Dedicated to 1 UE • 2ms or 10ms TTI • Controlled by NodeB scheduling process • Holds one or more dedicated physical data channels (E-DPDCH)

For internal use 9 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

E-DPDCH: E-DCH Dedicated Physical Data Channel • Dedicated uplink physical channel • 2ms or 10ms TTI • Controlled by NodeB scheduling process • The E-DPDCH is used by E-DCH for the transmission of data and Scheduling information (SI)

• Up to 4 E-DPDCH per radio link for higher throughput • s soft handover

For internal use 10 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

E-DPCCH: E-DCH Dedicated Physical Control Channel • Dedicated uplink physical channel. • Transmits control information about the E-DPDCH transmission: – E-TFCI (Transport block format combination indicator) – RSN (Retransmission sequence number) for the HARQ process – Happy Bit

• There is at most one E-DPCCH on each radio link. • Carries the „Happy Bit“

For internal use 11 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

With the Happy Bit the UE tells the NodeB scheduler every 2ms whether the ressource allocation was sufficient to transmit all data or not.

E-DPDCH & E-DPCCH

E-DPD CH ( data, SI) (contr o

For internal use 12 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

E-DP l data CCH , e.g H appy B

it)

E-DCH serving cell • E-DCH and HSDPA serving link is always assigned by RNC to the same cell (Best Cell) based on UE measurements.

NodeB 1

Non Serving RLS (1 RL)

NodeB 2

Serving RLS Serving E-DCH Cell

same RG information (per RLS)

RG information per RL HICH information per RLS

same HICH information (per RLS)

E-HICH E-AGCH E-RGCH

For internal use 13 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

HSUPA Channels - Downlink

For internal use 14 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

E-AGCH: E-DCH Absolute Grant Channel • Common downlink physical channel • Time-multiplexed shared channel with explicit UE addressing using ERNTI • On the E-AGCH, the NodeB tells the UE an absolute power level (alsolute grant, AG) for the E-DPDCH relative the DPCCH (precise value, thus also more information to be transmitted) • In soft handover state, the E-AGCH is transmitted by the serving E-DCH cell only • Uses SF256 E-AGC H E-RGC

For internal use 15 © Nokia Siemens Networks

(absolu

te pwr )

H (u p , down, hold)

, hold (down H C E-RG

E-DPDC H ( da ta)

CH D P D Eata) d r e ( us

HSUPA / JKuhr / September 2007

)

E-AGCH: primary & secondary absolute grant • An UE can get two E-RNTIs allocated (primary & secondary E-RNTI) that it needs to listen to on the E-AGCH.

• The UE always follows the AG transmitted for the primary E-RNTI (primary AG). – It can be commanded to follow the AG transmitted for the secondary E-RNTI as well.

• This mechanism can be used to control a group of UEs together (which will then all have the same secondary E-RNTI assigned) – E.g. group of “always on” UEs, that only occasionally send data – They will then be controlled as a group by a limited “secondary AG” – If one of that UE have needs to send more uplink data, it will then get an primary grant assigned via the primary R-RNTI. – As soon the primary grant is not needed anymore, the UE can be switched to secondary grant again.

For internal use 16 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

E-AGCH power settings in RNC Name

Q3-Name

Shortname

Longname

LMT-Name

Type

Range

Unit

R/ W

Default

E-AGCH Power Offset

sbs3gRanAg chPwrOffset

AGCHPWR OFF

agchPower Offset

po_agch

Integer

0..255 (0..2.55)

LMT: dB

RW

128 (RC)

Mapping to -32..+31.75 by step of 0.25 Indicates the Power offset relative to the pilot bits on the DL DPCCH

Example of command execution (hmi): cre hsupa cellid=1 nodebid=1 no_rgch_hich=4 po_agch=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30

For internal use 17 © Nokia Siemens Networks

HSUPA / JKuhr / September 2007

RC: 0.01*d B

1.28 (LMT)

Scheduler in NodeB, O&M parameter description Name

Range

Unit

R/W

Default

hsupaPowerOffsetEAGCH

Range: -32..31.75 Step: 0.25

dB

V

76 (-13 dB)

Mapped in database to range 0..255 Power offset of E-AGCH (secondary E-RNTI) (configurable only at CHC start-up time). Relative to ICH power. Vendor parameter: not recommended to be changed by the operator. Name

Range

Unit

R/ W

Default

maxSecondAbsGrant

Value range: [0…31]

-

R

5

5 ~ 32 kbps 9 ~ 128 kbps 9 shall not be exeeded

index value of 3GPP 25.212, section4.10.1A.1, table 16B Upper limit to the Secondary AG that may be assigned to all UEs in a radio cell. When doing RTT ("ping") measurements, note that the default value of 5 will have negative impacts on the RTT, as it does not allow a ping of 32 bytes to be sent within one MAC-e PDU: 2 PDUs are needed. To have an optimal RTT, either ensure that you have a Primary Grant active or set this value to a minimum of 7. Name maxNumberPrimaryGrantUe

Range 0..255

Unit

R/W

Default

-

V

4

Example of command execution (xml):

Maximum number of simultaneous UEs with Primary_Grant_Available = “True” Vendor parameter: not recommended to be changed by the operator.