Contents

UMTS/HSPA Radio Resource Management & Parameter

 Introduction to Radio Resource Management
 Power Control
 Load Control
 Admission Control
 Packet Scheduling
 Code Tree Management
 PLMN and Cell Selection
 Handover Procedures
 HSDPA Protocol Features
 HSDPA Power Management
 HSDPA Code Resource Management
 HSDPA Mobility
 HSUPA Protocol Features
 HSUPA Power Management
 HSUPA Mobility
 HSPA+

00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Content
HSUPA Mobility
 SHO
 Inward and Outward Mobility
 Directed RRC Setup
 Interfrequency & Intersystem Mobility
 Activity States

00-3 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 SHO Parameter and Restrictions

- SHO for E-DCH is done exactly by the same way as for R99 DCH

- Nokia
Specific settings with templates for HSUPA RAB and multi-RAB voice + HSUPA
- Ericsson and Huawei
Same settings as for R99
- Restrictions
All active cells must support HSUPA
If non-HSUPA cell becomes active, HSUPA switched back to R99 (see outward mobility)
All active HSUPA cells must support same TTI
If cell supporting 10 ms TTI only becomes active, switch back from 10 ms to 2 ms TTI

00-4 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 E-DCH and DCH Active Set

- Nokia allows, that in soft HO the E-DCH active set is smaller than the DCH active
set
- In softer HO E-DCH and DCH active set always must be identical

Serving E-DCH Cell Serving E-DCH RLS cell

. (under same Node B)
Defined by serving
HSDPA cell Transmit same relative grant on
E-RGCH
Transmits absolute grant Node B
on E-AGCH Allowed UP, HOLD, DOWN
.

Non serving RLS cell

(under different Node B)

Node B Transmit relative grants on E-

RGCH

Iub R Allowed HOLD, DOWN

N DOWN = overload indication
C Iub
HOLD = don‘t care

Iu

00-6 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Content
HSUPA Mobility Features
 SHO
 Inward and Outward Mobility
 Directed RRC Setup
 Interfrequency and Intersystem Mobility
 Activity States

00-9 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Inward Mobility
- UE moves from R99 to HSUPA coverage area
HSUPA cell becomes active by event 1A or 1C
UE still has DCH only
- Transition to E-DCH triggered, when
Soft HO HSUPA cell becomes best active cell according a certain margin (Nokia)
Softer HO R99 cell removed from active set (Nokia)
Last R99 cell removed from active set (Ericsson, Huawei)

M Transition to
Addition Cell 2 / Node B 2 HSUPA
Time becomes active
CPICH 1 (R99)
CPICH 2 (HSUPA)
DCH to E-DCH switch
Addition
window
window

HSUPA cell best active

cell according margin

Reports time
Nokia Ericsson, Huawei

DCH to E-DCH switch window EDCHAddEcNoOffset Last R99 cell removed

-10..6 dB, 0 dB from active set
00-10 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved
 Outward Mobility
- UE moves from HSUPA to R99 coverage area
R99 cell becomes active by event 1A or 1C
UE still has HSUPA
- Transition to E-DCH triggered, when
Soft HO cell becomes best active cell according a certain margin
(Nokia)
Softer HO cell just becomes active (Nokia)
First R99 cell enters active set (Ericsson, Huawei)
M Transition to R99
Addition Cell 2 becomes
Time active
CPICH 1 (HSUPA)
CPICH 2 (R99)
Addition E-DCH to DCH switch
window window

R99 cell best active cell

according margin

Reports
Ericsson, Huawei time
Nokia

E-DCH to DCH switch window EDCHRemEcNoOffset First R99 cell

-10..6 dB, 2 dB enters active set
00-12 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved
 Content
HSUPA Mobility Features
 SHO
 Inward & Outward Mobility
 Directed RRC Setup
 Interfrequency & Intersystem Mobility
 Activity States

00-15 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 On Bases of UE Capability

- Two (or more) carriers serving the same coverage area, e.g.
1st carrier for R99
2nd carrier for HSDPA
3rd carrier for HSDPA + HSUPA
- Allocation of the UE to the correct carrier on basis of its capability

f1 only R99 UMTS

R99 UMTS UE allocated to f1

f2 support of HSDPA
HSDPA UE allocated to f2

f2 support of HSUPA
HSUPA UE allocated to f3

00-16 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 On Basis of Load

- Two (or more) HSUPA carriers serving the same coverage area
1st carrier overloaded
2nd carrier not overloaded
3rd carrier not overloaded, but more load than under f2
- Allocation of the UE to the correct carrier on basis of the load
Load
f1 support of HSUPA
But overloaded

Load
f2 support of HSUPA (same Node B)
No overload

Load

f3 support of HSUPA (same Node B)

No overload, but more load than under f2

00-18 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Content
HSUPA Mobility Features
 SHO
 Inward and Outward Mobility
 Directed RRC Setup
 Interfrequency & Intersystem Mobility
 Activity States

00-21 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Inter-frequency & Inter-system Mobility (1/2)

- Compressed mode in HSUPA

Nokia: Not allowed in any case, switch back to R99
Ericsson, Huawei: Allowed for inter-frequency HHO, switch back to R99 for inter-RAT HHO only
- HHO triggered and done exactly by the same way as for R99 DCH
- Some vendors offer independent parameters settings by RAB specific templates

Interfreq template 5 Intersys template 5

HSUPA HSUPA
EC/I0 HHO threshold = ... EC/I0 HHO threshold = ...
Interfreq template 6 Intersys template 6
... ...
HSUPA + voice HSUPA + voice
EC/I0 HHO threshold = ... EC/I0 HHO threshold = ...
... ...

00-22 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Inter-frequency & Inter-system Mobility (2/2)

- Nokia
HSUPA specific HHO trigger settings by parameter templates
- Ericsson
HSUPA specific HHO trigger settings by service offset parameter
Basic thresholds for HHO events identical for R99, HSDPA and HSUPA

- Huawei
For HSUPA same HHO trigger settings as for HSDPA

00-24 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Content
HSUPA Mobility Features
 SHO
 Inward and Outward Mobility
 Directed RRC Setup
 Interfrequency & Intersystem Mobility
 Activity States

00-27 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Channel Type Selection (1/2)

UE HSUPA capable ?
HSUPA for requested
HSUPA enabled ?
RAB allowed ?

No HHO process preventing

HSUPA running ?

HSDPA
Active set Possible ?

Less than the maximum acceptable ?

number of HSUPA users ?

00-28 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Channel Type Selection (2/2)

- To offer E-DCH in SHO with HSUPA and R99 cells, the following checks are needed
1) Smaller E-DCH active set supported (Nokia with soft HO situation)
HSUPA cell must be better than R99 cell according DCH to E-DCH switch window
2) Smaller E-DCH active set NOT supported (Nokia with softer HO situation, Ericsson and
Huawei in general)
HSUPA not offered in any case

HSUPA
e.g. Ec/I0 = -10 dB
E-DCH (1)
Node B DCH (2)
HSUPA .
e.g. Ec/I0 = -8 dB
E-DCH (1)
DCH (2)
R99
e.g. Ec/I0 = -13 dB
DCH (1)
DCH (2)

00-30 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Transition from Cell_FACH to HSUPA

- Based on huge amount of data in RLC buffer as for R99

Procedure performed exactly by the same way as for R99
- Nokia + Ericsson
Exactly same buffer threshold and timer as for R99

- Huawei
HSUPA specific buffer threshold and timer

Huawei

FTOETVMTHD
RLC buffer threshold
16 byte..768 Kbyte, 1 Kbyte

FTOETVMTIMETOTRIG
Time hysteresis
0..5000 ms, 240 ms

Settings per RNC only

00-32 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Transition from HSUPA to Cell_FACH (1/2)

- Nokia
Based on low data rate
Network does not now, whether still data in UE buffer
Cannot distinguish between low utilization / throughput as done for HSDPA

Nokia

EDCHMACdFlowThroughputRelThr
Throughput threshold
0..64 Kbit/s, 256 bit/s

EDCHMACdFlowThroughputTimetoTrigger
Time hysteresis
0..300 s, 5 s

Settings per RNC only

00-34 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

 Transition from HSDPA to Cell_FACH (2/2)

- Ericsson
Based on low data rate (exactly like R99)
Same timer and throughput thresholds as for HSDPA
- Huawei
Based on low data rate instead of low amount of data in RLC buffer

Huawei

E2FTHROUTHD E2FTHROUPTAT
Data rate threshold Time hysteresis to abort pending procedure
0..384, 8 Kbit/s 0..1023 s, 16 s

E2FTHROUTIMETOTRIG E2FSTATETRANSTIMER
Time hysteresis to initiate downgrade procedure Time hysteresis to execute downgrade
0..1023 s, 2 s 0..65535 s, 180 s

Settings per RNC only

00-36 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved