09b HSUPA RU10 v1.0 RRM

HSUPA RRM
RANPAR I RU10
Nokia Siemens Networks
HSUPA RRM: Content
HSUPA Principles
HSUPA Protocols and Procedures
HSUPA Physical Channels
Enabling HSUPA
Basics of HSUPA Power Control
Basic of HSUPA Load Control
Basics of HSUPA Congestion Control
HSUPA Mobility
HSUPA Channel Type Selection and Switching
HSUPA Principles: Content
Comparison of HSUPA with HSDPA

Adaptive Coding
E-DCH
Network Modifications
Comparison of HSUPA with HSDPA (1/2)

TS 25.309 HSUPA technical requirements
Node B controlled scheduling
Hybrid ARQ
same
Shorter TTI (2 ms / 10 ms)
sameas
asHSDPA
HSDPA
Downward compatibility to R99, R4 and R5
HSUPA requires HSDPA
Minimise HSUPA (UE and UTRAN) complexity
Full mobility support and urban, suburban & rural deployment
HHSSUUP
PAA
RNC
Node
B
Iub
HHSSDDP
PAA
Uu
UEs
Comparison of HSUPA with HSDPA (2/2)

Why not
adapting
HSDPA solutions
to UL?
Problems / differences
Power Control PC
On DL centralized PC
On UL individual PC
pure time multiplexing difficult
On UL fast PC still necessary
(UL interference UL scrambling codes)
On UL no code (CC) limitation

more Codes available
high order modulation not so important
Higher order modulation difficult for UE,

but coming with Rel.7
SHO requested (full mobility and coverage)
HSUPA (similar to HSDPA) is based on

Fast H-ARQ terminated at Node B
Fast Node B controlled UL scheduling
Fast link adaptation
Adaptive coding (1/4-4/4 code rate)
5
E-DCH
E-DCH transport channel characteristics

UL (only) transport channel
Dedicated to 1 UE
Subject to Node-B controlled scheduling & HARQ
Supports 2 ms TTI and 10 ms TTI
Enhanced
Enhanceddedicated
dedicatedchannel
channelE-DCH
E-DCH
Dedicated channel DCH
A channel dedicated to 1 UE
used in UL or DL.
SRNC
Iub
6
Node
B
Uu
UE
Network Modifications
UTRAN and UE
modified PHY layer
modified MAC
HSUPA: functionalities shifted from

RNC to Node B
Acknowledged transmission (H-ARQ)
faster retransmission / reduced delays !
less Iub traffic !
UL packet scheduling
fast UL resource allocation !
Uu
RNC
(SW
(SW
modifications)
modifications)
Reduced
Reduced
Retransmission
Retransmission
newfunctions
functions
new
Iub
Node
B
more
more
intelligence
intelligence
(SWmodifications)
modifications)
(SW
modified transport and

physical channels
modified coding
UE
newUE`s
UE`s
new
HSUPA Protocols and Procedures: Content
Protocol Stack
Fast Packet Scheduling
Fast Link Adaptation
Fast HARQ
Packaging of MAC-d and MAC-es PDUs
Protocol Stack
MAC-es/e layer within the UE
Multiplexing of MAC-d PDUs
E-TFC selection based upon Node B
MAC-e layer within the Node B

HARQ
Extracting MAC-es PDUs
E-DCH scheduling and control
scheduling
HARQ
MAC-es layer within the RNC

ensures in sequence delivery
soft handover combining
UE
Node B
SRNC
RLC
MAC-d
MAC-es
RLC
MAC-d
MAC-es/e
MAC-e
WCDMA L1
WCDMA L1
Uu
Frame
Protocol
Frame
Protocol
Transport
Transport
Iub
Iu
Fast Packet Scheduling

HSUPA fast packet scheduling
Node B controlled
Resources allocated upon scheduling request
Short TTI = 2 (not in RU10) / 10 ms
Scheduling decision on basis of actual physical layer load (available in Node B)
up-to date / fast scheduling decision high UL resource efficiency
higher load target (closer to overload threshold) possible high UL resource efficiency
L1 signalling overhead
Scheduling request
(buffer occupation,...)
Scheduling grants
SRNC
Iub
Node
B
(max. amount of
UL resources to be used)
E-DCH
E-DCH
data
datatransmission
transmission
10
UE
Fast Link Adaptation

MAC-e (UE) decides
E-DCH link adaptation (TFC,
Scheduling
request
effective coding)
On basis of channel quality
estimates (CPICH Ec/Io)
Every TTI (2/10 ms)
Scheduling
grants
Node
B
EE--DP
DPDDCH
CH
R6
R6HSUPA
HSUPA
R99
R99
Fixed
Fixed
turbocoding
coding1/3
1/3
turbo
11
dynamic
dynamiclink
linkadaptation
adaptation
effective
coding
effective coding1/4
1/4 - -4/4
4/4
higher
higherUL
ULdata
datarates
rates
higher
resource
efficiency
higher resource efficiency
UE
Fast HARQ (1/4)

HSUPA: Fast H-ARQ with UL E-DCH
Node B (MAC-e) controlled
Stop & wait HARQ protocol
max. 4 SAW processes / UE for 10 ms TTI

max. 8 SAW processes / UE for 2 ms TTI
each process has own physical buffer
E-DCH maximum number of HARQ retransmissions

EDCHMaxNumberOfHARQReTx (RNC) (0..3) ( = 1) (3)
HARQ RV Configuration
HARQRVConfiguration (WBTS) (0..1) ( = 1) (1 = IR)
Based on synchronous DL (L1) ACK/NACK

Retransmission
1st retransmission after 40 / 16 ms (TTI = 10 / 2 ms)

Limited number of retransmissions
Lower probability for RLC retransmission
IR & CC
Support of soft & softer Handover
Short delay times

Short delay times
(support
(supportof
ofQoS
QoSservices)
services)
Less Iub/Iur traffic
Less Iub/Iur traffic
E-DCH
E-DCHPackets
Packets
SRNC
correctly
correctlyreceived
received
packets
packets
Iub
12
Node
B
L1ACK/NACK
ACK/NACK
L1
Retransmission
Retransmission
SAW: Stop and Wait
IR: Incremental Redundancy
CC: Chase Combining
UE
Fast HARQ (2/4)
d
cceeiviveed
e
r
y
l
ct tly reet
ccoorrrerec
ppaacckket
S-RNC
Iub
E-DCH AS
MAC-es
Reordering
SHO data combining
11HARQ
HARQentity
entityper
perUE
UE
inineach
eachNode-B
Node-Bof
ofE-DCH
E-DCHactive
activeset
set
Node
B
ACCK
K
1 Node B / H-ARQ entity
Send same ACK / NACK (E-HICH) to UE

Soft combining in case of retransmission
t
kkeet
c
Deliver correctly received packets to RNC
ppaac
H
CH
MAC-es
EE-D
-DC
CKK
A
UE
C
NA
CHHN
I
C
H
-I
EE-H
Node
B
13
EE-D
-DCCH
Hppa
-H I
acckke
EE-H
ICCHH A
et t
UE
Receives / evaluates ACK /
NACK
Combines E-HICH values of
serving radio link set
Retransmission if all RL
send NACK for MAC-e
Fast HARQ (4/4)

E-DCH maximum number of HARQ retransmissions
EDCHMaxNumberOfHARQReTx (RNC) (0..3) ( = 1) (3)
HARQ RV Configuration
HARQRVConfiguration (WBTS) (0..1) ( = 1) (1 = incremental redundancy)
15
HSUPA Physical Channels: Content
18
Overview
E-DPDCH and E-DPCCH
E-TFC Selection
DPDCH, DPCCH and HS-DPCCH
E-AGCH
E-RGCH
E-HICH
Transmission Power Settings
Basics of BTS Scheduling
Overview
Scheduling Request
Scheduling information or happy bit (E-DPCCH)
Scheduling
Grants
(UE
E-AGCH
identity E-RNTI and max. power ratio E-DPDCH/DPCCH)
E-RGCH
(UP / HOLD / DOWN)
E-DPCCH
(E-TFCI, re-transmission sequence number, happy bit)
E-DPDCH
User data and CRC
Node
B
19
E-HICH
(ACK/NACK)
UE
E-DPDCH and E-DPCCH (1/3)

E-DPDCH
Carries UL packet data
Up to 4 E-DPDCHs for 1 radio link
Maximum configuration according 3GPP: 2 * SF2 + 2 * SF4

Maximum configuration according RU10: 2 * SF2
SF = 256 2 (BPSK)
Pure user data and CRC (1 CRC per TTI, size 24 bit)
TTI = 2 / 10 ms (at cell edge 10 ms required for sufficient performance)
UE receives resource allocation via grant channels
Managed by MAC-e/-es
Error protection based on turbo coding 1/3
Soft / softer handover support
20

E-DPCCH
E-TFCI information (7 bit)
Indicates E-DCH Transport Block Size i.e. Coding at given TTI
Retransmission Sequence Number RSN (2 bit)
Value = 0 / 1 / 2 / 3 for initial transmission, 1st / 2nd / further retransmission
Happy bit (1 bit)
Indicating if UE could use more resources or not
Happy = 1
Not happy = 0
These 10 bits are channel coded to generate 30 bits per 2 ms sub-frame
21
2 ms TTI => the 30 bits are transmitted once during the 2 ms

10 ms TTI => the 30 bits are repeated 5 times during the 10 ms

Happy bit
Forms input for MAC-e scheduler in Node B
Included as part of E-DPCCH
Happy bit delay condition
Defines time over which to evaluate the current serving grant relative to total buffer status
Happy bit set to unhappy if all 3 of the following conditions are true
UE transmitting as much scheduled data as allowed by current serving grant
UE has sufficient power to transmit at higher data rate
With actual serving grant, UE would need at least the following time to transmit the total
amount of data in its buffer
HappyBitDelayConditionEDCH * (number of active HARQ processes / total number of HARQ processes)

For 10 ms TTI number of active HARQ processes = total number of HARQ processes
Happy bit delay condition for E-DCH

HappyBitDelayConditionEDCH (RNC) (2, 10, 20, 50, 100, 200, 500, 1000 ms) (-) (50
ms)
22
E-TFC Selection
Idea
UE has to select appropriate transport block size
in dependence on
Capability
Transmission power
Service grant
Transport block size derived from transport block
index with help of TBS size table
One TBS size table for each TTI (2 ms and 10 ms)
TBS size tables optimised for MAC-d PDU sizes of
336 and 656 bits
23
DPDCH, DPCCH and HS-DPCCH

DPDCH
Continues to transfer the set of SRBs

3.4 kbps SRB uses SF128
DPCCH
Continues to transfer TPC, TFCI and pilot bits

HS-DPCCH
HSUPA always used in combination with HSDPA
Necessary for UE to transmit HSDPA CQI and HARQ ACK/NACK
27
E-AGCH
Transfers a total of 6 bits per 2 ms sub-frame
Absolute grant value (5 bits)
signals transmit power allowed for E-DPDCH relative

to DPCCH
Absolute grant scope (1 bit) - only applicable to 2 ms
TTI
indicates whether grant applies to single HARQ
process or to all HARQ processes
Transfers E-RNTI
Transmitted by serving HSUPA cell
SF 256 used
2 ms TTI 60 coded bits occupy TTI
10 ms TTI 60 coded bits repeated 5 times to occupy
TTI
28
E-RGCH
Transfers relative grant value
Can be transmitted by any active HSUPA cell
Cells belonging to serving radio link set may command up, down and hold
Other cells only able to command down and hold
SF 128 used
E-RGCH can occupy
2 ms TTI and serving radio link set occupies 2 ms
Non serving radio link set occupies 10 ms
Channelization code
For specific UE, channelization code used for E-RGCH and E-HICH shall be the same
40 orthogonal signatures defined to allow multiple UEs to share same channelization code
29
E-HICH
Transfers E-DCH HARQ acknowledgement
Transmitted by all active set cells
UE continues to re-transmit until ACK received from at least one cell (or until re-transmission
time out)
SF 128 used
E-HICH can occupy
Channelization code
For specific UE, same channelization code used as for E-RGCH
40 orthogonal signatures defined to allow multiple UEs to share same channelization code
30
Transmission Power Settings

Transmission power offset of the E-AGCH (relative to PtxCPICH)
PtxOffsetEAGCH (WCEL) (-32..31.75 dB) ( = 0.25 dB) (-5 dB)
Settings for fixed power
Transmission power offset of the R-AGCH (relative to PtxCPICH)

PtxOffsetERGCH (WCEL) (-32..31.75 dB) ( = 0.25 dB) (-11 dB)
Transmission power offset of the E-AGCH (relative to DL DPCCH pilot field)
PtxOffsetEAGCHDPCCH (WCEL) (-32..31.75 dB) ( = 0.25 dB) (0 dB)
Transmission power offset of the R-AGCH (relative to DL DPCCH pilot field)
PtxOffsetERGCHDPCCH (WCEL) (-32..31.75 dB) ( = 0.25 dB) (0 dB)
Transmission power offset of the E-HICH (relative to DL DPCCH pilot field)
PtxOffsetEHICHDPCCH (WCEL) (-32..31.75 dB) ( = 0.25 dB) (0 dB)
Maximum transmission power of the E-HICH (relative to PtxCPICH)
PtxMaxEHICH (WCEL) (-32..31.75 dB) ( = 0.25 dB) (-11 dB)
31
Settings for power parallel

to DPCCH
BTS Scheduling (1/7)

Principles
BTS scheduler shares resources between UEs with HSUPA connections

Absolute and relative grants
Scheduling period 10 ms
Scheduling decisions based on
Uplink interference (noise rise)

Physical layer feedback (happy bit)
Iub resources
Baseband processing resources
BTS
384
UE
384
256
128
256
128
256
128
64
32
16
64
32
16
64
32
16
8
Zero Grant
8
Zero Grant
8
Zero Grant
RNC
384
32
1.
2.
1.
2.
3.
4.
3.
4.
RNC limits E-TFC based upon UE

capability and QoS profile
Node B limits E-TFC based upon
packet scheduling principles
UE limits E-TFC based upon
transmit power capability
UE selects E-TFC based upon data
to be transferred

Throughput and load based scheduling
HSUPA scheduler combines throughput and load based algorithms

Throughput based scheduling applied for lower load
Power based scheduling applied for higher load
Maximum cell load for
HSUPA scheduling
Lmin_cell
-95
Throughput based
Load derived from
throughput
-96
Power based
Load derived
from RTWP
-97
R T W P (d B m )
-98
-99
PrxMaxTargetBTS
Relative to PrxNoise
Should be >
PrxTarget + PrxOffset
-100
-101
-102
PrxLoadMarginEDCH
Relative to PrxNoise
-103
-104
-105
0
33
0.1
0.2
0.3
0.4
0.5
Load
0.6
0.7
0.8
0.9
PrxNoise

UL noise level
PrxNoise (WCEL) (-130..-50 dBm) ( = 0.1 dB) (-105 dBm)
Interference margin for the minimum E-DCH load
PrxLoadMarginEDCH (WCEL) (0..30 dB) ( = 0.1 dB) (2 dB)
Corresponding load factor = 1 - 1 / 100.2 = 0.37 (37 %)
Load factor < margin throughput based load estimation
Otherwise
RTWP based load estimation
Maximum target received wide band power for BTS
PrxMaxTargetBTS (WCEL) (0..30 dB) ( = 0.1 dB) (6 dB)
Corresponding load factor = 1 - 1 / 100.6 = 0.75 (75 %)
RTWP < maximum target
more HSUPA service can be offered
Otherwise
more HSUPA service can not be offered any more
HSUPA service has to be downgraded if too much RWP
from non served UEs in comparison to E-DCH RWP
34

Absolute grant
BTS signals maximum allowed power ratio E-DPDCH / DPCCH by
service grant value

Mapping between service grant values and power ratios hardcoded
Mapping between power ratios and E-TFCs hardcoded
Initial power ratio = (21/15)2 independent on service profile and UL
load (corresponds to 32 kbps)
35
E-TFC
Amplitude Ratio
21/15
27/15
11
34/15
19
47/15
39
60/15
67
60/15
85
75/15
103
84/15
E-TFC
Serving grant
values
Power ratio
E-DPDCH / DPCCH

Relative grant
BTS signals to increase / reduce maximum allowed E-DPDCH /
DPCCH power ratio
When UE receives relative grant UP command, service grant
value increases by 1
When UE receives relative grant DOWN command, service
grant value decreases by 1
UP e.g. from
23 to 24
DOWN e.g.
from 19 to 18
36

Relative grant
BTS allowed to transmit relative grant DOWN command if
Measured RTWP > PrxMaxTargetBTS AND
Ratio RWP due to UEs not served by BTS / E-DCH RWP > TargetNSEDCHToTotalEDCHPR
Target non-serving E-DCH to total E-DCH power ratio
TargetNSEDCHToTotalEDCHPR (WCEL) (0..100 %) ( = 1 %) (30 %)
Example
BTS measures RTWP = -98 dBm
Noise rise = -98 dBm - (-105 dBm) = 7 dB > PrxMaxTargetBTS
Total UL load from RTWP = 1 1 / 100.7 = 0.80 (80 %)
BTS measures from throughput own cell load = 40 % for E-DCH and 20 % for DCH
Load from UEs not served by BTS = 80 % - 40 % - 20 % = 20 %
Target non-serving E-DCH to total E-DCH power ratio = 20 % / 40 % = 0.5 (50 %) >
TargetNSEDCHToTotalEDCHPR
Both conditions fulfilled DOWN command allowed
37

Serving E-DCH RLS cells
(under same Node B)
Transmit same relative grant
on E-RGCH
Allowed UP, HOLD, DOWN
Node B
E-DCH
Serving E-DCH cell

Defined by serving
HSDPA cell
Transmits absolute
grant on E-AGCH
Node B
Iub
R
N
C
Iu
38
Iub
Non-serving RLS cells

(under different Node B)
may transmit different relative
grants
Allowed HOLD, DOWN
DOWN = overload indication
HOLD = dont care
Enabling HSUPA: Content

Enabling HSUPA in general
Maximum Number of Connections
Maximum Bit Rate
39
Enabling HSUPA in general

Possible only in combination with HSDPA
HSUPA enabled using the parameters
HSUPAEnabled (in general)
EDCHQOSClasses (for certain traffic classes)
HSUPA enabled
HSUPAEnabled (WCEL) (0..1) ( = 1) (0 = disabled)
E-DCH QoS classes
EDCHQOSClasses (RNC) (0..31) ( = 1) (31 = all traffic classes
enabled)
5 bit parameter
Bit 1 = background
Bits 2/3/4 = interactive with THP = 3/2/1
Bit 5 = streaming
40
Maximum Number of Connections

Maximum number of E-DCH allocations defined by
MaxNumberEDCHCell for individual cell
MaxNumberEDCHLCG for cell group
Specific number of E-DCH allocations can be reserved for soft / softer HO
NumberEDCHReservedSHOBranchAdditions both for individual cells and cell groups
Maximum number of new E-DCH = NumberEDCHReservedSHOBranchAdditions MaxNumberEDCHCell(LCG)
Maximum number of E-DCHs in the cell

MaxNumberEDCHCell (WCEL) (1..20) ( = 1) (20)
Maximum number of E-DCHs in the local cell group
MaxNumberEDCHLCG (WBTS) (1..60) ( = 1) (60)
Number of E-DCHs reserved for SHO branch additions
NumberEDCHReservedSHOBranchAdditions (WCEL) (0..5) ( = 1) (2)
According default settings
20 - 2 = 18 new E-DCH allowed in individual cell
60 - 2 = 58 new E-DCH allowed in cell group
41
Maximum Bit Rate

Definition on the basis of the maximum symbol rate by
MaxTotalUplinkSymbolRate
1 bit per symbol on E-DPDCH raw bit rate = symbol rate
1920 Ksps often quoted as 1.4 Mbps HSUPA
3840 Ksps often quoted as 2.0 Mbps HSUPA
Maximum bit rate on E-DCH may exceed maximum bit rate defined by QoS profile by factor
FactorEDCHMaxBitRate
If set to 0, QoS profile is ignored
If set to 1, maximum E-DCH bit rate = maximum bit rate defined by QoS profile
For multi-RAB combinations own specific factors can be set
Maximum total uplink symbol rate

MaxTotalUplinkSymbolRate (WCEL) (1xSF4 960 K, 2xSF4 1920 K, 2xSF2 3840 K) (-) (1xSF4 960 K)
Factor to calculate EDCH maximum bit rate
FactorEDCHMaxBitRate (RNC) (0.1..5) ( = 0.1) (1.5)
42
Basics of HSUPA Power Control: Content

Power Control for E-AGCH, E-RGCH and E-HICH
Inner Loop Power Control for E-DPDCH and E-DPCCH
Outer Loop Power Control for E-DPDCH and E-DPCCH
43
Power Control for E-xCH

Power of grant channels
Fixed, if set relative to PtxCPICH (PtxOffsetEAGCH and PtxOffsetERGCH)
Follows DPCCH, if set relative to power of DPCCH pilot filed
(PtxOffsetEAGCHDPCCH
and PtxOffsetERGCHDPCCH)
Power of HARQ channel

Follows DPCCH (PtxOffsetEHICHDPCCH)
But maximum power defined relative to PtxCPICH (PtxMaxEHICH)
Power of E-DPDCH and E-DPCCH is coupled to power of DPCCH
44
Basics of HSUPA Load Control: Content
51
Dynamic Load Target

DCH Congestion
E-DCH Congestion
Actions in Case of Congestion
Dynamic Load Target (1/2)

Static load target
Fixed thresholds PrxTarget and PrxOffset for cell without active HSUPA service
Dynamic load target
Similar concept as for HSDPA for cell with active HSUPA service
For NRT traffic adjustable load target PrxTargetPS
PrxTargetPSMin (minimum value)

PrxTargetPSMax (maximum value, also initial value)
Fixed threshold PrxTarget still used for non controllable traffic

Same PrxOffset used as in static case to decide about overload actions, but
now relative to PrxTargetPS
Ideal load target

Estimated by RNC in dependence on
Non controllable traffic
NRT DCH traffic (including weights of individual services)
NRT E-DCH traffic (including weights of individual services)
52
Dynamic Load Target (2/2)

No HSUPA users
HSUPA active
No HSUPA users
PrxMaxTargetBTS (6 dB)
PrxTarget (4 dB)
PrxTargetPSMax (e.g. 3 dB)
PrxEDCH
PrxTargetPS
PrxTargetPSMin (e.g. 2 dB)
PrxNRT
PrxNC
Minimum PS target in HSPA-DCH interference sharing

PrxTargetPSMin (WCEL) (0.1..30 dB) ( = 0.1 dB) (4 dB)
Maximum PS target in HSPA-DCH interference sharing
PrxTargetPSMax (WCEL) (0.1..30 dB) ( = 0.1 dB) (4 dB)
53
DCH Congestion
PrxTargetPS (e.g. 2.5 dB)
PrxTotal
Margin (given by adjustable

step size to update
PrxTargetPS, default 0.5 dB)
PrxNonEDCH
Calculated by RNC
Requirements to indicate DCH congestion
PrxNonEDCH PrxTargetPS - margin AND

Throughput based non EDCH load > min (load factor based on PrxTargetPS,
load factor based on PrxLoadMarginEDCH)
Example
Input values
PrxTargetPS = 2.5 dB (from RNC) load factor 1 - 1 / 10 0.25 = 0.44 (44 %)

Margin = 0.5 dB (from operator)
PrxNonEDCH = 2.3 dB (from RNC)
Throughput based non EDCH load = 30 % (from RNC)
PrxLoadMarginEDCH = 2 dB (from operator) load factor 1 - 1 / 10 0.2 = 0.37 (37 %)
Check for DCH congestion
54
2.3 dB 2.5 dB 0.5 dB OK

30 % > min (44 %, 37 %) not OK no DCH congestion yet
E-DCH Congestion
Margin (default 0.5 dB)
PrxTargetPS (e.g. 2.5 dB)
PrxTotal
Requirements to indicate DCH congestion
PrxTotal PrxMaxTargetBTS - margin AND

Throughput based non EDCH + EDCH load > load factor based on PrxLoadMarginEDCH
Example
Input values
PrxMaxTargetBTS = 6 dB (from operator)

Margin = 0.5 dB (from operator)
PrxTotal = 5.9 dB (from Node B)
Throughput based non EDCH load = 30 % (from RNC)
Throughput based EDCH load = 30 % (from Node B)
PrxLoadMarginEDCH = 2 dB (from operator) load factor 1 - 1 / 10 0.2 = 0.37 (37 %)
Check for E-DCH congestion
55
5.9 dB 6 dB 0.5 dB OK
30 % + 30 % > 37 % OK E-DCH congestion

DCH congestion only
Increase PrxTargetPS by configurable step (default 0.5 dB), if currently below ideal
load target (but not above maximum target)
E-DCH congestion only

Decrease PrxTargetPS by configurable step (default 0.5 dB), if currently above ideal
load target (but not below minimum target)
Both DCH and E-DCH congestion

Increase PrxTargetPS, if currently below ideal load target
Decrease PrxTargetPS, if currently above ideal load target
56
Basics of HSUPA Iub Congestion Control: Content
57
Principles
Data Flow from UE to RNC
Congestion Detection
Principles
RNC responsible to detect congestion on Iub and to inform Node B
Node B HSUPA scheduler takes actions on the air-interface to relieve
congestion on Iub to avoid

RLC re-transmissions resulting from Iub congestion
Generation of air-interface load for data which cannot be transferred to RNC
58
Data Flow from UE to RNC

RNC
BTS
TNL
E-DCH FP
Uplink
E-DPCH
E-DCH_FP_UP
(data)
E-DCH FP
Congestion
Detection
E-DCH
Packet
Scheduler
UE
Sends HSUPA data
carrying one transport
block (MAC-e PDU)
E-DCH FP
Downlink
Node B
Decodes E-DPDCH
Extracts MAC-es PDU
Constructs E-DCH UL FP frame from
MAC-es PDUs
Send E-DCH UL FP frame to RNC
59
Congestion
Indication
Congestion Detection
RNC
BTS
E-DCH FP
TNL
E-DCH FP
Uplink
E-DPCH
Congestion
Detection
E-DCH_FP_UP
(data)
E-DCH
Packet
Scheduler
Delay
Frame loss
E-DCH FP
Downlink
RNC
Congestion detection entity detects possible TNL congestion
based upon
Delay build-up
Lost frames
and informs congestion indication entity

60
Congestion indication entity compares delay with thresholds
Congestion
Indication

RNC
BTS
TNL
E-DPCH
E-DCH FP
Uplink
E-DCH_FP_UP
(data)
Relative Grant
E-DCH
[DOWN]
Packet
Scheduler
Congestion indication
(delay OR frame loss)
E-DCH FP
Downlink
E-DCH FP
Congestion
Detection
Delay
Frame loss
E-DCH_FP_CTRL
(delay OR Frame loss)
Congestion
Indication
In case of congestion RNC sends E-DCH FP control frame to Node B

E-DCH FP entity in BTS receives congestion indication and forwards it to
E-DCH packet scheduler
Packet Scheduler decreases UE bit rate by sending relative grant DOWN
command
61
Transmission power taken away from UE due to congestion is kept

reserved and cannot be given to other UEs in a cell
HSUPA Mobility
Soft and Softer HO
Inter-Frequency and Inter-System HHO
Basics of HSUPA Layering
62
Soft and Softer HO (1/2)

Types of mobility
Intra-frequency mobility allows
Softer handover
Intra-RNC Soft handover
Inter-RNC Soft handover
SHO Trigger
Same events (1a, 1b, 1c) as for DCH
But specific FMCS parameter set available for
User both with HSDPA + HSUPA
User both with HSDPA + HSUPA and AMR
HSDPA serving cell change not affected by HSUPA SHO
HSPA FMCS identifier
HSPAFmcsIdentifier (WCEL) (1..100) ( = 1) (-)
HSPA FMCS identifier for AMR multi-service
RTWithHSPAFmcsIdentifier (WCEL) (1..100) ( = 1) (-)
63
Soft and Softer HO (2/2)

E-DCH and DCH active set
E-DCH active set is subset of DCH active set
Cells can be left out from E-DCH active set but included within DCH active set due to
HSUPA not enabled for DCH active cell
Maximum number of E-DCH users reached for that cell or cell group to which it belongs
No free E-DCH resources within cell group to which it belongs
Softer HO E-DCH and DCH active sets have to be identical
Soft HO E-DCH and DCH active sets can be different

Cell shall be added to E-DCH active set later if possible (by using internal retry timer)
HSDPA cell is also HSUPA serving cell
If SHO failure for E-DCH

E-DCH
Channel type switch to DCH, if non active cell becomes

too strong in comparison to best active cell
In case of softer HO for DCH no active set update either
E-DCH
(RRC connection release due to DCH SHO failure

possible as usual)
DCH
64
Inter-Frequency and Inter-System HHO

Inter-Frequency HHO
Not yet supported for HSUPA
Same FMCI parameter set used as for HSDPA
Same HOPI parameter set used as for R99
Inter-System HHO
Same FMCG parameter set used as for HSDPA
Same HOPG parameter set used as for R99
65
Basics of HSUPA Layering (1/2)

From RRC_Idle
HSUPA capability of UE taken into account only, if enhanced layering enabled with
DirectedRRCForHSDPALayerEnhanc
To be redirected to HSUPA layer, UE must indicate with RRC connection request
Is of R6 or newer
Is HSDPA + HSUPA capable
At least one cell must be available fulfilling the following requirements
Number of HS-DSCH allocations has not reached maximum allowed value
HSUPA is enabled
Only single HSUPA capable cell available
Shall be selected without checking if maximum allowed number of HSUPA users
has been reached
Several HSUPA capable cells available
Cells which have not reached maximum allowed number of HSUPA users are
prioritised
DRRC connection setup for HSDPA layer enhancements
DirectedRRCForHSDPALayerEnhanc (RNC) (0..1) ( = 1) (0 = disabled)
66
Basics of HSUPA Layering (2/2)

From Cell_FACH
Must be enabled with HSDPALayeringCommonChEnabled
Redirection Cell_FACH to Cell_DCH to HSPA layer triggered if
UE is HSPA capable
HSDPA not enabled for current cell
HSDPA enabled for at least one cell in same sector
UE is requesting service for which state transition is enabled with ServicesToHSDPALayer
HSUPA capability is taken into account if
UE is HSUPA capable
HSUPA enabled target cell available
Layering from Cell_FACH not affected by settings for layering from RRC_idle
HSDPA layering for UEs in common channels enabled
HSDPALayeringCommonChEnabled (WCEL) (0..1) ( = 1) (0 = disabled)
Services to HSDPA layer in state transition
ServicesToHSDPALayer (RNC) (any service, NRT RAB) (-) (any service)
67
HSUPA Channel Type Selection and Switching: Content

Basics of E-DCH Establishment
Basics of Channel Type Switching
Basics of E-DCH Release
68
Basics of E-DCH Establishment (1/2)

Channel type
selection started
UE specific
PS
Uplink NRT RB
mapped to DCH > 0
kbpsNo
Yes
UE capability
supports E-DCH
Yes
No
RAB combination
allows use of EDCHYes
No
Traffic class and THP

allowed on E-DCH
No
No
No
HC
Yes
DCH
selecte
d
No
Number of E-DCH
allocations is below the
maximum
Yes
No
Cell specific PS
(can be more
than 1)
Final E-DCH active set is

acceptable
Yes
No
E-DCH
selecte
d
UE specific PS
DCH
selecte
d
1) Channel type switching running

2) RAB combinations allowed for HSUPA
Up to three NRT RAB (any combination E-DCH RABs / DCH RABs)
With or without AMR
3) Preliminary active set = all active cells with HSUPA enabled

4) Minimum active set = all HSUPA enabled active cells with sufficient quality
69
HSPA serving cell

selected +
Preliminary E-DCH
active set selected
Minimum E-DCH
active set selected
No
Preliminary E-DCH
active set is
acceptable
Yes
HS-DSCH possible to
select in the downlink
Yes
Yes
HSDPA mobility
enabled and HS-DSCH
available
and no IFHO/ISHO
measurements
IFHO/ISHO measurements
Yes
prevent HSUPA
HS-DSCH possible to
select in the downlink
Basics of E-DCH Establishment (2/2)

Minimum E-DCH active set
Exclude all active cells for which HSUPA is disabled
Exclude all active cells which satisfy following equation
EC/I0 of non E-DCH cell < EC/I0 of serving E-DCH cell + EDCHAddEcNoOffset
DCH active set step 1

HSUPA
enabled
Preliminary E-DCH active set step 2

HSUPA
enabled
HSUPA
enabled
HSUPA
enabled
HSUPA
disabled
Minimum E-DCH active set step 3

CPICH Ec/Io
= -5 dB
70
CPICH Ec/Io
= -7 dB
Allow E-DCH usage EcNo offset

EDCHAddEcNoOffset (FMCS) (-10..6 dB) ( = 0.5 dB) (0 dB)
Basics of Channel Type Switching

Overview
Channel type switching
DCH -> E-DCH transition or
E-DCH -> DCH transition
HS-DSCH related trigger

DCH <-> HS-DSCH channel type switching
HS-DSCH serving cell change
Quality related trigger

EC/I0 of serving HSDPA cell becomes acceptable for E-DCH
EC/I0 of serving HSDPA cell becomes unacceptable for E-DCH
EC/I0 is reported periodically like for HSDPA serving cell change
Other
Guard timer started after transition E-DCH -> DCH expires
Re-try timer started after unsuccessful attempts to get E-DCH (due to
too high number of E-DCH users) expires
Node B initiated transition E-DCH -> DCH
71

09b HSUPA RU10 v1.0 RRM

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

09b HSUPA RU10 v1.0 RRM

Загружено:

Авторское право:

Доступные форматы

HSUPA RRM

Nokia Siemens Networks

HSUPA RRM: Content

Nokia Siemens Networks

HSUPA Principles: Content

Comparison of HSUPA with HSDPA

Nokia Siemens Networks

Comparison of HSUPA with HSDPA (1/2)

Nokia Siemens Networks

Comparison of HSUPA with HSDPA (2/2)

On UL no code (CC) limitation

Higher order modulation difficult for UE,

HSUPA (similar to HSDPA) is based on

Nokia Siemens Networks

E-DCH transport channel characteristics

Nokia Siemens Networks

HSUPA: functionalities shifted from

Nokia Siemens Networks

modified transport and

HSUPA Protocols and Procedures: Content

Nokia Siemens Networks

MAC-e layer within the Node B

MAC-es layer within the RNC

Nokia Siemens Networks

Fast Packet Scheduling

Nokia Siemens Networks

Fast Link Adaptation

Nokia Siemens Networks

Fast HARQ (1/4)

max. 4 SAW processes / UE for 10 ms TTI

E-DCH maximum number of HARQ retransmissions

Based on synchronous DL (L1) ACK/NACK

1st retransmission after 40 / 16 ms (TTI = 10 / 2 ms)

Support of soft & softer Handover

Short delay times

Nokia Siemens Networks

Fast HARQ (2/4)

Nokia Siemens Networks

1 Node B / H-ARQ entity

Send same ACK / NACK (E-HICH) to UE

Receives / evaluates ACK /

Fast HARQ (4/4)

Nokia Siemens Networks

HSUPA Physical Channels: Content

Nokia Siemens Networks

identity E-RNTI and max. power ratio E-DPDCH/DPCCH)

(UP / HOLD / DOWN)

(E-TFCI, re-transmission sequence number, happy bit)

User data and CRC

Nokia Siemens Networks

E-DPDCH and E-DPCCH (1/3)

Maximum configuration according 3GPP: 2 * SF2 + 2 * SF4

Nokia Siemens Networks

E-DPDCH and E-DPCCH (2/3)

These 10 bits are channel coded to generate 30 bits per 2 ms sub-frame

2 ms TTI => the 30 bits are transmitted once during the 2 ms

Nokia Siemens Networks

E-DPDCH and E-DPCCH (3/3)

HappyBitDelayConditionEDCH * (number of active HARQ processes / total number of HARQ processes)

Happy bit delay condition for E-DCH

Nokia Siemens Networks

Nokia Siemens Networks

DPDCH, DPCCH and HS-DPCCH