You are on page 1of 181

HSUPA RRM & Parameters

Slide 1

NokiaEDU
HSUPA RRM & Parameters

RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 1
HSUPA RRM & Parameters

Slide 2

Copyright and confidentiality

The contents of this document are proprietary Such Feedback may be used in Nokia products implied warranties of merchantability and
and confidential property of Nokia. This and related specifications or other fitness for a particular purpose, are made in
document is provided subject to confidentiality documentation. Accordingly, if the user of this relation to the accuracy, reliability or contents
obligations of the applicable agreement(s). document gives Nokia Feedback on the of this document. NOKIA SHALL NOT BE
contents of this document, Nokia may freely RESPONSIBLE IN ANY EVENT FOR ERRORS IN
This document is intended for use of Nokias use, disclose, reproduce, license, distribute and THIS DOCUMENT or for
customers and collaborators only for the otherwise commercialize the feedback in any any loss of data or income or any special,
purpose for which this document is submitted Nokia product, technology, service, incidental, consequential, indirect or direct
by Nokia. No part of this document may be specification or other documentation. damages howsoever caused, that might arise
reproduced or made available to the public or from the use of this document or any contents
to any third party in any form or means without Nokia operates a policy of ongoing of this document.
the prior written permission of Nokia. This development. Nokia reserves the right to make
document is to be used by properly trained changes and improvements to any of the This document and the product(s) it describes
professional personnel. Any use of the products and/or services described in this are protected by copyright according to the
contents in this document is limited strictly to document or withdraw this document at any applicable laws.
the use(s) specifically created in the applicable time without prior notice.
agreement(s) under which the document is Nokia is a registered trademark of Nokia
submitted. The user of this document may The contents of this document are provided "as Corporation. Other product and company
voluntarily provide suggestions, comments or is". Except as required by applicable law, no names mentioned herein may be trademarks or
other feedback to Nokia in respect of the warranties of any kind, either express or trade names of their respective owners.
contents of this document ("Feedback"). implied, including, but not limited to, the

2 13/07/2016 Nokia 2014 - RN3164AEN50GLA1


2 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 2
HSUPA RRM & Parameters

Slide 4

HSUPA RRM & parameters:


Module Objectives

At the end of the module you will be able to:

Explain the physical layer basics of HSUPA technology


List the key changes brought by HSUPA and their impact on the network and on
the protocol model
Explain HSUPA RRM and the related parameters in detail, including packet
scheduling, resource management, mobility and channel type selection

4 13/07/2016 Nokia 2014 - RN3164-16A WCD


4 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 3
HSUPA RRM & Parameters

Slide 5

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
5 13/07/2016 Nokia 2014 - RN3164-16A WCD
5 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 4
HSUPA RRM & Parameters

Slide 6

Comparing HSUPA & HSDPA (1/2)


3GPP Rel. 6: TS 25.309 HSUPA technical requirements
Node B controlled scheduling
Hybrid ARQ
Shorter TTI: 2 ms or 10 ms same as HSDPA
Downward compatibility to R99, R4 & R5
HSUPA requires HSDPA
Minimise HSUPA (UE and UTRAN) complexity
Full mobility support and urban, suburban & rural deployment

Iub
RNC Node B

Uu
UEs

6 13/07/2016 Nokia 2014 - RN3164-16A WCD


6 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 5
HSUPA RRM & Parameters

Slide 7

Comparing HSUPA & HSDPA (2/2)

HSUPA problems / differences to HSDPA:


Why not
Power Control PC: Fast Power Control
adapting
on DL centralized PC
HSDPA solutions on UL individual PC
to UL? pure time multiplexing difficult
on UL fast PC still necessary (same as Rel. 99)
(UL interference UL scrambling codes)
Higher order modulation difficult for UE (Rel.7)
Soft Handover required due to coverage reasons

HSUPA (similar to HSDPA) is based on


Fast H-ARQ terminated at Node B
Fast UL Packet Scheduling controlled by Node B
Fast Link Adaptation:
- Adaptive coding (1/4 - 4/4 code rate)
- Adaptive modulation (3GPP Rel. 7)

7 13/07/2016 Nokia 2014 - RN3164-16A WCD


7 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 6
HSUPA RRM & Parameters

Slide 8

E-DCH: Enhanced Dedicated Channel (TS 25.309)


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 dedicated channel E-DCH

Dedicated channel DCH


A channel dedicated to 1 UE
used in UL or DL.

Iub Uu UE
Node B
RNC

8 13/07/2016 Nokia 2014 - RN3164-16A WCD


8 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 7
HSUPA RRM & Parameters

Slide 9

E-DPDCH & E-DPCCH E-DPDCH:


carries E-DCH transport channel
cd,1 d user data only (+ 24 CRC bits/TTI)
DPDCH1
Rel. `99 SF = 256 2 !
Multi-Code Operation: there may be 0, 1, 2 or 4
cd,3 d E-DPDCH on each radio link
up to 2x SF2 + 2x SF4 up to 11.52 Mbps with

DPDCH3 I
16QAM
cd,5 d
DPDCH5
E-DPCCH:
transmits HSUPA L1 control information
associated with the E-DCH
I+jQ
SF = 256 fixed
cd,2 d
Sdpch content: E-TFCI, RSN & Happy Bit
DPDCH2
Rel. 6 UL: DCH & E-DCH Configurations
Configur HS- E- E-
cd,4 d DPDCH DPCCH
a-tion # DPCCH DPDCH DPCCH
DPDCH4
1 6 1 1 - -


Q
cd,6 d
2 1 1 1 2 1
DPDCH6 BW1
cc c
j 3 - 1 1 4 1
DPCCH

E-TFCI: Enhanced Transport Format Combination Indication


RSN: Retransmission Sequence Number

9 13/07/2016 Nokia 2014 - RN3164-16A WCD


9 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 8
HSUPA RRM & Parameters

Slide 10

HSUPA 5.8Mbps
MaxTotalUplinkSymbolRate
RAN 981: HSUPA 5.8 Mbps peak rate WCEL; 0 (960 kbps, SF4),
Optional Feature (ASW) 1 (1.92 Mbps; 2xSF4),
RNC License Key required (ON OFF) 2 (3.84 Mbps; 2xSF2),
3 (5.76 Mbps; 2xSF2 + 2xSF4);
HSUPA 5.8 Mbps active parameter value
3 allowed; else max. 2

Cch,4,3
Cch,2,1 To support an UL peak rate of 5.8 Mbps* the
E-DPDCH UE needs to send on 4 E-DCH channels in
(on I- and Q-branches 2SF2 parallel (2xSF2 + 2xSF4)
+ 2SF4 max) Cch,4,2
UE category 6 + 7, 8 enable transmission of
4 codes in parallel & support 5.76 Mbps at
Cch,4,1 maximum with QPSK modulation
In case of 4 code E-DCH transmission
Cch,2,0 3GPP defines that no DPDCH may be
Cch,4,0 allocated simultaneously
The SRB needs to be mapped on E-DCH in
SF2 SF4 SF8 this case. This requires RU20 RAN 1470
RU20: HSUPA 2ms TTI, which introduces the
mapping of UL SRBs on E-DCH
5.8 Mbps &
2 ms TTI * 5.76 Mbps

10 13/07/2016 Nokia 2014 - RN3164-16A WCD


10 RN31648EN16GLA0 2016 Nokia

Feature ID: RAN981


The peak bit rate on E-DCH for single user is increased up to 5.8 Mbps.

Benefits for the operator:


This feature enables operator to offer higher HSUPA bit rates to premium data subscribers and increase data service revenue.

Functional description:
HSUPA UE categories 4, 6 and 7 support higher peak bit rate than 2 Mbps. With this feature category 4, 6 and 7 UEs may transmit
data with their maximum bit rate, which is achieved with an E-DCH configuration of 2ms transmission time interval (TTI). Four
parallel codes are required for category 6 and 7. When four codes are transmitted in parallel, two codes are transmitted with
spreading factor two (2xSF2) and two with spreading factor four (2xSF4). Also intermediate bit rates are supported with 2 ms TTI.

The maximum theoretical throughput of category 6 and 7 terminal is 5.76 Mbps. Practical throughput achievable with this feature is
limited by radio reception and allowed noise rise:
Maximum theoretical throughput would require the use of coding rate close to 1. Coding rate 1 requires effectively error free
reception without error correction coding. Targeting to error free reception reduces the system efficiency and capacity. In all practical
conditions the throughput will be degraded if using coding rates close to 1.
Quality of radio reception depends on aspects such as received signal strength, radio channel and interference, transmitter and
receiver imperfections.

RN31648EN16GLA0 9
HSUPA RRM & Parameters

Slide 11

HSUPA 11.6Mbps
MaxTotalUplinkSymbolRate
RAN 1645: HSUPA 16QAM 11.6 Mbps peak rate WCEL; 0 (960 kbps, SF4),
Optional Feature (ASW) 1 (1.92 Mbps; 2xSF4),
RNC License with configurable number of cells 2 (3.84 Mbps; 2xSF2),
3 (5.76 Mbps; 2xSF2 + 2xSF4);
HSUPA 16QAM active parameter value 3
Cch,4,3
Cch,2,1 allowed;
E-DPDCH
(on I- and Q-branches 2SF2 11.6 Mbps* is supported with 4 E-DCH
+ 2SF4 max) Cch,4,2 channels in parallel (2xSF2 + 2xSF4)
UE category 7, 9 enable transmission of 4
codes in parallel & support 11.6 Mbps at
Cch,4,1 maximum with 16QAM modulation
RU20: Cch,2,0 In case of 4 code E-DCH transmission 3GPP
5.8 Mbps & defines that no DPDCH may be allocated
Cch,4,0 simultaneously
2 ms TTI
SF2 SF4 SF8 The SRB needs to be mapped on E-DCH in
this case. This requires RU20 RAN 1470
HSUPA 2ms TTI, which introduces the
mapping of UL SRBs on E-DCH
ETFCIBoost (non-configurable)
RNC; 0..127 ;1 102; Power boosting mode is used (refer to slide
Starting from the E-TFCI Default value, UE will select 16QAM & start to use boosted ILPC)
mode.
E-TFC 102 has TBS of 8105bits -> 4052.5 kbps is a starting MAC-e throughout for UL RLC PDU size of 656 bits
16QAM modulation

11 13/07/2016 Nokia 2014 - RN3164-16A WCD * 11.52 Mbps


11 RN31648EN16GLA0 2016 Nokia

FD HSUPA RRM in RNC p. 270

RN31648EN16GLA0 10
HSUPA RRM & Parameters

Slide 12

HSUPA UE Capability Classes / Throughput


E- DCH max. min. 2 & 10 ms TTI max. #. of max. # of Modulation Reference
Category# E-DCH SF E-DCH E-DCH Bits* / 10 E-DCH Bits* / 2 combination
Codes support ms TTI ms TTI Class
HSUPA UE
1 1 4 10 ms only 7296 - QPSK 0.73 Mbps
capability 2 2 4 10 & 2 ms 14592 2919 QPSK 1.46 Mbps
classes 3 2 4 10 ms only 14592 - QPSK 1.46 Mbps

(TS 25.306; 4 2 2 10 & 2 ms 20000 5772 QPSK 2.92 Mbps


5 2 2 10 ms only 20000 - QPSK 2.0 Mbps
Rel. 10)
6 4 2 10 & 2 ms 20000 11484 QPSK 5.76 Mbps
7 4 2 10 & 2 ms 20000 22996 QPSK & 16QAM 11.52 Mbps
8 4 2 2 ms TTI - 11484 QPSK 5.76 Mbps
9 4 2 2 ms TTI - 22996 QPSK & 16QAM 11.52 Mbps

2 x SF2 + 2 x SF2 +
Coding rate 1 x SF4 2 x SF4 2 x SF2
2 x SF4 2 x SF4
HSUPA
ThroughputBW3
1/2 480 kbps 960 kbps 1.92 Mbps 2.88 Mbps 2.88 Mbps
3/4 720 kbps 1.46 Mbps 2.88 Mbps 4.32 Mbps 4.32 Mbps
4/4 960 kbps 1.92 Mbps 3.84 Mbps 5.72 Mbps 11.52 Mbps BW2
RU40:
16QAM RAS06 RU10 RU20 RU40
RU50: DC-HSUPA enables 11.6Mbps and 23Mbps with E-DCH Cat 8 & 9 respectively
# further E-DCH categories are discussed in the HSPA+ sections
* maximum No. of bits / E-DCH transport block
12 13/07/2016 Nokia 2014 - RN3164-16A WCD
12 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 11
HSUPA RRM & Parameters

Slide 13

Network Modifications
UTRAN & UE: new Node B functionalities:
modified PHY layer Fast H-ARQ (Acknowledged transmission):
faster retransmission / reduced delays !
modified MAC less Iub retransmission traffic !
higher spectrum efficiency !
Fast Packet Scheduling
fast & efficient resource allocation !

Uu
modified transport and
Iub physical channels
RNC modified coding UE
Node B
new UE`s
retransmission

RNC: Node B
Reduced

functionalities more
Intelligence; new UE functionality:
shifted to
new functionalities Fast Link Adaptation
Node B
Adaptive Coding (& Modulation; from Rel. 7 on)
higher peak rates & spectrum efficiency !
13 13/07/2016 Nokia 2014 - RN3164-16A WCD
13 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 12
HSUPA RRM & Parameters

Slide 14

Protocol Stack
MAC-i layer within the Node B
MAC-is/i* layer within the UE H-ARQ
Multiplexing of MAC-d PDUs E-DCH Packet Scheduling & control
E-TFC selection (Link Adaptation) Extracting MAC-is PDUs (Scheduling Information)
based upon Node B scheduling Read UE id
HARQ
MAC-is layer within the RNC
ensures in sequence delivery
Soft Handover combining

UE Node B SRNC
RLC RLC
MAC-d MAC-d
MAC-is Iu
MAC-is/i
MAC-i Frame Frame
Protocol Protocol
WCDMA L1 WCDMA L1
Transport Transport

Uu Iub
* MAC-is and MAC-i is replacing MAC-es and MAC-e in RU40 with RAN1910 Flexible RLC in UL feature
14 13/07/2016 Nokia 2014 - RN3164-16A WCD
14 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 13
HSUPA RRM & Parameters

Slide 15

Flexible RLC packet size in UL

RLC Packet Data Unit (PDU) sizes for UL are flexible (optimal for UEs)
MAC-i in BTS and UE replaces MAC-e
MAC-is in UE and RNC replaces MAC-es
RU20 RU40
PDCP IP packet 1500B
PDCP IP packet 1500B
RLC Max RLC PDU size: 336b/656b RLC RLC PDU size up to 1505B

Benefits:
Reduction of RLC overhead
Reduced processing in UE and RNC
Optimum TB size selection for different radio conditions
Improves end user experience enabling higher bit rates for single users
Future proofed by allowing higher throughput rates with new modulation
schemes.

15 13/07/2016 Nokia 2014 - RN3164-16A WCD


15 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 14
HSUPA RRM & Parameters

Slide 16

Fast Packet Scheduling


HSUPA fast packet scheduling:
Node B controlled
Resources allocated upon scheduling request
Short TTI = 2 (RU20) / 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 signaling overhead

Scheduling request
(buffer occupation,...)

Scheduling grants UE
(max. amount of
UL resources to be used)
Iub
E-DCH
data transmission
RNC
Node B
16 13/07/2016 Nokia 2014 - RN3164-16A WCD
16 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 15
HSUPA RRM & Parameters

Slide 17

Fast Link Adaptation


MAC-e (UE) decides:
E-DCH link adaptation (TFC, effective coding)
on basis of scheduled power ratio E-DPDCH/DPCCH
every TTI (2/10 ms)
Scheduling
request
Scheduling
grants

UE

Node B
R6 HSUPA
dynamic link adaptation
HSUPA Rel. 7 & beyond:
R99 effective coding 1/4 - 4/4 Adaptive Coding
Fixed (QPSK/16QAM)
turbo coding 1/3 higher UL data rates
higher resource efficiency

17 13/07/2016 Nokia 2014 - RN3164-16A WCD


17 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 16
HSUPA RRM & Parameters

Slide 18

Fast HARQ (1/3)


EDCHMaxNumberOfHARQReTx
HSUPA: Fast H-ARQ with UL E-DCH E-DCH max. number of HARQ retransmissions
RNC; 0..3; 1; 3
Node B (MAC-e) controlled
Stop & wait H-ARQ protocol HARQRVConfiguration
WBTS; Chase Combining CC (0),
max. 4 SAW processes / UE for 10 ms TTI
Incremental Redundancy IR Combining (1)
max. 8 SAW processes / UE for 2 ms TTI
each process has own physical buffer
Based on synchronous DL (L1) ACK/NACK
Retransmission
1st retransmission after 40 / 16 ms (TTI = 10 / 2 ms)
Limited number of retransmissions
Short delay times
Lower probability for RLC retransmission (support of QoS services)
IR & CC Less Iub/Iur traffic
Support of soft & softer Handover Node B
E-DCH Packets
UE
L1 ACK/NACK
correctly received
packets Retransmission
RNC
Iub SAW: Stop and Wait
IR: Incremental Redundancy
CC: Chase Combining
18 13/07/2016 Nokia 2014 - RN3164-16A WCD
18 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 17
HSUPA RRM & Parameters

Slide 19

Fast HARQ (2/3) 1 H-ARQ entity per UE


in each Node-B of E-DCH active set

S-RNC Iub 1 Node B / H-ARQ entity


Send same ACK / NACK (E-HICH) to UE
E-DCH AS Soft combining in case of retransmission
Deliver correctly received packets to RNC UE
MAC-es MAC-es
Reordering
SHO data combining UE
receives/evaluates ACK/NACK
combines E-HICH values of
Serving Radio Link set
Retransmission if all RL send
NACK for MAC-e
Node B

19 13/07/2016 Nokia 2014 - RN3164-16A WCD


19 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 18
HSUPA RRM & Parameters

Slide 20

Fast HARQ (3/3)

Transport blocks generated according to instructions from E-TFC selection


Transport blocks moved into HARQ process buffer and kept there until
Positive acknowledgement has been received
Maximum number of re-transmissions has been reached

Buffered MAC-d PDUs

1 2 3 4
HARQ E-TFC Selection
process determines size of
buffers transport block

EDCHMaxNumberOfHARQReTx
E-DCH maximum number of HARQ
retransmissions; RNC; 0..3; 1; 3
To physical layer
HARQRVConfiguration
processing WBTS; Chase Combining (0), Incremental
Redundancy Combining (1)

20 13/07/2016 Nokia 2014 - RN3164-16A WCD


20 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 19
HSUPA RRM & Parameters

Slide 21

Scheduling Information SI Scheduling Information SI

MAC-es PDU SI Padding

MAC-e PDU optional


Scheduling Information SI periodically included in MAC-e PDU tail: PeriodicityForSI
Periodicity for scheduling info
UE power headroom (UPH) RNC; 4..1000 ms; 200 ms
Ratio maximum UE Tx power / current DPCCH Tx power
Total E-DCH buffer status (TEBS)
Total amount of data available across all logical channels for which reporting has been requested by RRC
Highest priority logical channel buffer status (HLBS)
Amount of data available from the logical channel identified by HLID,
Relative to highest value of buffer size range reported by TEBS when reported TEBS index is not 31
Relative to 50000 bits when reported TEBS index is 31
Highest priority logical channel identity (HLID)
Highest priority logical channel with available data
If multiple logical channels exist with same highest priority, that one corresponding to highest buffer occupancy will be
reported
PowerOffsetForSI
UPH TEBS HLBS HLID Power offset for
scheduling information
Total E-DCH Highest priority Highest priority RNC; 0..6; 1; 3 dB
UE power headroom
buffer status logical channel logical channel
buffer status identity
21 13/07/2016 Nokia 2014 - RN3164-16A WCD
21 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 20
HSUPA RRM & Parameters

Slide 22

NOKIA: Enabling HSUPA HSUPAEnabled


WCEL; 0 = disabled; 1 = enabled

only in combination with HSDPA EDCHQOSClasses


enabling certain E-DCH QoS classes (RNC); 5 bit
by HSUPAEnabled & EDCHQOSClasses parameter:
Maximum Number of Connections Bit 1 = Background BG
Bits 2/3/4 = Interactive with THP = 3/2/1
Maximum number of E-DCH allocations defined by Bit 5 = streaming
31 = all traffic classes enabled
MaxNumberEDCHCell for individual cell
MaxNumberEDCHLCG for Local Cell Group (LCG) MaxNumberEDCHCell
max. number of E-DCHs (serving+non-serving) in the cell
Number of E-DCH allocations reserved for SHO: WCEL; 1..72; 1; 20 (RU20)
NumberEDCHReservedSHOBranchAdditions both for 0, 1 1024; 1; 0 = not limited (RU30, RU40)
individual cells & cell groups. Note: This parameter has no
effect if HSPA128UsersPerCell=1 MaxNumberEDCHLCG
max. number of E-DCHs (serving+non-serving) in the LCG
According to default settings:
WBTS; 1..72; 1; 60 (RU20)
RU30: 72 - 2 = 70 new E-DCH allowed in cell
0, 1 1024; 1; 0 = not limited (RU30, RU40)
RU40: 128 = 128 new E-DCH allowed in cell
In RU30/40, max number of users (serving+non-serving) per LCG is NumberEDCHReservedSHOBranchAdditions
limited by HSUPA scheduler capacity: up to 480 HSUPA (2x Flexi Number of E-DCHs reserved for SHO branch additions
System Module) or 240 (1x Flexi System Module) users per LCG WCEL; 0..5; 1; 2

HSPA72UsersPerCell (RU20, RU30)


RU20: According default settings:
20 - 2 = 18 new E-DCH allowed in individual cell max. number of serving + non-serving E-DCHs per cell is 72
60 - 2 = 58 new E-DCH allowed in LCG WCEL; 0 = not enabled; 1 = enabled

LCG: Local Cell Group HSPA128UsersPerCell (RU40)


max. number of serving E-DCHs per cell is 128
WCEL; 0 = not enabled; 1 = enabled
22 13/07/2016 Nokia 2014 - RN3164-16A WCD
22 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 21
HSUPA RRM & Parameters

Slide 23

Advanced HSUPA Time Division Scheduling


Introduction

RAN3043 Advanced HSUPA Time Division Scheduling


introduces possibility to utilize only one HARQ process
per UE instead of eight HARQ processes, in consequence
of time division users scheduling. RAN3043 feature:

enables higher HSUPA cell throughput


allows increasing the number of admitted users
mapped on E-DCH transport channel
feature impacts 2ms TTI HSUPA scheduling only

RAN3043

Up to 30% UL Throughput Gain

23 RN31648EN16GLA0 2016 Nokia

RAN3043: Advanced HSUPA Time Division Scheduling

RN31648EN16GLA0 22
HSUPA RRM & Parameters

Slide 24

Advanced HSUPA Time Division Scheduling


Introduction

Before RU20 After WCDMA16

The HSUPA scheduler allocates single A single 2ms TTI HARQ processes is
2ms TTI HARQ process for a lower also available for a medium average
average bitrates only not exceeding 40 bitrates (40 kbps120 kbps)
kbps Time division scheduling benefits with a
For the average bitrates greater than 40 cell capacity gain
kbps, all the 2ms TTI HARQ processes
of the HARQ period are involved

24 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 23
HSUPA RRM & Parameters

Slide 25

Advanced HSUPA Time Division Scheduling


Introduction - HSUPA basics

The UE can start transferring user data on the


HSUPA basics
Enhanced Dedicated Channel (E-DCH) using the initial
HARQ 2ms TTI serving grant
legacy solution
The grant value determines the upper limit of the UE
HARQ 2ms TTI resources (the transmitted power) and allows to select
with TDS
the user data rate within the restrictions set by the
scheduler Node B
The transport block size (MAC-e PDU) identified by the
UE determines the quantity of MAC-d PDU blocks 2ms TTI UE
buffered within the terminal

Source: Radio Access Networks for UMTS: Principles and Practice. Chris Johnson

25 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 24
HSUPA RRM & Parameters

Slide 26

Advanced HSUPA Time Division Scheduling


Introduction - HSUPA basics - HARQ

There are 8 consecutive HARQ (HARQ 0HARQ 7) processes


to allow uninterrupted E-DCH transmission
The 8 consecutive HARQ processes belong to the one HARQ
cycle and are allocated to 2ms TTIs in a cyclic pattern
Node B
UE continues to re-transmit until an ACK is received from at
least one cell
2ms TTI UE
The HARQ acknowledgments (ACK) are carried by E-HICH
channel

HARQ cycle

HARQ HARQ HARQ HARQ HARQ HARQ HARQ HARQ HARQ HARQ ...
0 1 2 3 4 5 6 7 0 1
...
2 ms 2 ms 2 ms 2 ms 2 ms 2 ms 2 ms 2 ms 2 ms 2 ms
TTI TTI TTI TTI TTI TTI TTI TTI TTI TTI time

26 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 25
HSUPA RRM & Parameters

Slide 27

Advanced HSUPA Time Division Scheduling


Introduction - Data rates for UEs with the legacy 2ms HSUPA

The HSUPA scheduler allocates a single 2ms Average: Peak #RLC #of
(kbps) @2ms: PDUs HARQs
TTI HARQ processes for a lower average (kbps)

bitrates only (not exceeding 40 kbps) 5440 5440 8 8

Possible data-rates for UEs


The possible HARQ allocations with a legacy .. 8
(+25%) (+25%)
2ms HSUPA :
The one HARQ
- 1 HARQ process for the average bitrates no 480 480 3 8
allocations possible
more than 40 kbps (max 2 PDUs) 320 320 2 8 with legacy
HSUPA 2ms for UE
- at least one PDU in each HARQ or more 160 160 1 8 transmitting 1-2
than 2 PDUs in HARQ cycle PDUs
40 320 2 1
All the HARQ processes within the HARQ 20 160 1 1
cycle are assigned if the UE is granted with 0 0 0 0
more than 40 kbps of average throughput
Each MAC-d PDU has a fixed size of 336 bits (including the 16-bit RLC
header) with a user plane data payload of 320 bits. The minimum data-
rate@2ms = 500*320 = 160 kbps

27 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 26
HSUPA RRM & Parameters

Slide 28

Advanced HSUPA Time Division Scheduling


Introduction - Data rates for UEs with the Advanced HSUPA Time Division Scheduling

Average: Peak #RLC #of


(kbps) @2ms: PDUs HARQs
The HSUPA scheduler allocates a single 2ms (kbps)

TTI HARQ processes also for a medium 5440 5440 8 8


average bitrates (40 kbps 120 kbps) .. 8
(+25%) (+25%) The one HARQ

Possible data-rates for UEs


The possible HARQ allocations with a possible additional
480 480 3 8
RAN3043: allocations introduced
- 1 HARQ process for the average bitrates no 320 320 2 8 with Advanced
HSUPA TDS (for UE
more than 120 kbps (max 6 PDUs) 160 160 1 8 transmitting 3-6)
- at least one PDU in each HARQ or more than 6 120 960 6 1 PDUs
PDUs in HARQ cycle
100 800 5 1 The one HARQ
Allowing larger peak data-rates improves the 80 640 4 1 allocations possible
with legacy
air-interface capacity with intermediate number 60 480 3 1 HSUPA 2ms for UE
of UEs ~(8-16) UEs 40 320 2 1
transmitting 1-2
PDUs
20 160 1 1
0 0 0 0

28 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 27
HSUPA RRM & Parameters

Slide 29

Advanced HSUPA Time Division Scheduling


Introduction - HARQ 2ms TTI legacy solution

There are 8 HARQ (HARQ 0HARQ 7) processes to allow uninterrupted E-DCH transmission
HSUPA basics
The HARQ processes are allocated to consecutive 2ms TTI in a cyclic pattern
HARQ 2ms TTI
legacy solution
Example HARQ assignment for 5 UE per cell (legacy 2ms TTI scheduling):

HARQ 2ms TTI


- UE-a, UE-d, UE-e allocated to 2PDU one HARQ processes; UE-b, UE-c allocated to all
with TDS HARQ

The highest possible


one HARQ allocation
PDU with legacy 2ms TTI
PDU HSUPA for UEs
PDU transmitting 2PDUs
(up to 40 kbps)
PDU
PDU UE-c UE-c UE-c All HARQ allocation
PDU UE-b UE-b UE-b for UE transmitting
PDU UE-a UE-c UE-c UE-d UE-c UE-e UE-b UE-b more than 2PDUs
PDU UE-a UE-b UE-b UE-d UE-b UE-e UE-c UE-c
PDU each field HARQ HARQ HARQ HARQ HARQ HARQ HARQ HARQ
represents a single 0 1 2 3 4 5 6 7 time
MAC-d PDU payload

29 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 28
HSUPA RRM & Parameters

Slide 30

Advanced HSUPA Time Division Scheduling


Introduction - HSUPA 2ms TTI processes with Advanced HSUPA Time Division Scheduling

Time division scheduling is realized by a single HARQ scheduler, which allocates a higher
HSUPA basics grants
HARQ 2ms TTI Scheduling bases on radio conditions, available cell load, QoS parameters
legacy solution
The higher available throughput per one TTI allows to distribute more UEs on time axis
HARQ 2ms TTI
with TDS

One HARQ allocation


PDU UE-d UE-h UE-j UE-o for UEs transmitting
2PDUs
PDU UE-b UE-d UE-h UE-j UE-l UE-o
PDU UE-b UE-c UE-e UE-f UE-h UE-i UE-l UE-m
PDU UE-a UE-c UE-e UE-f UE-g UE-i UE-l UE-m The highest possible
PDU UE-a UE-c UE-e UE-f UE-g UE-i UE-l UE-m one HARQ allocation
with Advanced
PDU UE-a UE-c UE-e UE-f UE-g UE-i UE-l UE-m
HSUPA TDS for UE
PDU UE-a UE-c UE-e UE-f UE-g UE-i UE-k UE-m transmitting 6PDUs
PDU UE-a UE-c UE-e UE-f UE-g UE-i UE-k UE-m (120 kbps)
PDU each field HARQ HARQ HARQ HARQ HARQ HARQ HARQ HARQ
represents a single 0 1 2 3 4 5 6 7 time
MAC-d PDU payload

30 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 29
HSUPA RRM & Parameters

Slide 31

Advanced HSUPA Time Division Scheduling


Benefits and Gains

Time division scheduling of the UEs reduces intra UL: HSUPA 2ms TTI

cell interferences and benefits with a cell capacity


gain

The UL cell capacity gain is expected to be up to


30% (based on simulations results)

The uplink cell throughput is improved when there


is about 8-16 users in a cell
- link level simulations assume 16 UEs per cell
generating continuous UL traffic in PA3
propagation channel

31 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 30
HSUPA RRM & Parameters

Slide 32

HSUPA NOKIA Summary

Characteristic RU20 RU30 RU40 RU50 WCDMA16


E-DCH per cell 72 (RAN 1668) 72 128 (RAN2124) 128 208
240 (1x Flexi 240 (1x Flexi 240 (1x Flexi
E-DCH codes per System Module) System Module) System Module)
72 (RAN 1668) 320
LCG 480 (2x Flexi 480 (2x Flexi 480 (2x Flexi
System Module) System Module) System Module)
5.76 Mbps (RAN
Max. Bit Rate 11.52 Mbps 11.52 Mbps 23 Mbps 23 Mbps
981)
Modulation QPSK 16QAM 16QAM 16QAM 16QAM
10 ms & 2 ms
TTI 10 ms & 2 ms 10 ms & 2 ms 10 ms & 2 ms 10 ms & 2 ms
(RAN 1470)

+ CS Voice over
Traffic Classes all traffic classes all traffic classes all traffic classes all traffic classes
HSPA (RAN1689)

PF + QoS aware PF + QoS aware PF + QoS aware PF + QoS aware PF + QoS aware
Packet Scheduler
scheduling scheduling scheduling scheduling scheduling

FDE (RAN 1702),


FDE (RAN 1702),
FDE (RAN 1702), FDE (RAN 1702), IC (RAN1308),
Receiver RAKE IC (RAN1308),
IC (RAN1308) IC (RAN1308) EIC (RAN2250)
EIC (RAN2250)
IRC (RAN3040)

32 RN31648EN16GLA0 2016 Nokia

A WBTS with FSMF+2xFBBA+FSMF and 4 LCGs configured support up to 1280 HSUPA users.

RN31648EN16GLA0 31
HSUPA RRM & Parameters

Slide 33

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
33 13/07/2016 Nokia 2014 - RN3164-16A WCD
33 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 32
HSUPA RRM & Parameters

Slide 34

HSUPA: 10 ms & 2ms (RAN 1470) TTI


HSUPA2MSTTIEnabled
3GPP Rel. 6 defines both 10 ms & 2 ms TTI for RNC; 0 (Disabled), 1 (Enabled)
HSUPA
NOKIA RAS06 & RU10 support only 10 ms TTI
10 ms TTI improves cell edge performance 2 ms TTI:
2 ms TTI (RAN1470) support with NOKIA RU20: reduced latency
2 ms TTI reduces latency higher peak rates
2 ms supports increased peak throughputs (up to 5.811.6 Mbps)
prerequisite for HSUPA peak rates higher than 2Mbps (up
to 5.8 Mbps 11.6 Mbps)
2 ms TTI: SRB are mapped onto HSPA
(NOKIA implementation)
10 ms TTI:
10 ms TTI: SRB are mapped onto DPDCH Improved cell edge
(NOKIA implementation) performance
SRB mapping onto HSUPA is mandatory for the
2 SF2 + 2 SF4 configuration because the DPDCH
code is blocked by E-DPDCH codes (3GPP
specification)
PriForSRBsOnHSPA: RNC; 0..15; 1; 15
defines priority SPI for SRBs on E-DCH & HS-DSCH

34 13/07/2016 Nokia 2014 - RN3164-16A WCD


34 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 33
HSUPA RRM & Parameters

Slide 35

Selection of 2 ms TTI

The TTI selection procedure is triggered during:


UL channel type selection (DCH vs. E-DCH)
an ongoing existing HSUPA connection (TTI switching)
RAB establishment or release (TTI switching)
The 2 ms HSUPA TTI is selected if:
HSUPA 2 ms TTI is enabled by HSUPA2MSTTIEnabled
UE supports 2 ms TTI
RAB combination supports SRB on HSUPA
RNC reconfigures E-DCH 2ms TTI E-DCH 10ms TTI if
2ms TTI Coverage criteria not fulfilled

35 13/07/2016 Nokia 2014 - RN3164-16A WCD


35 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 34
HSUPA RRM & Parameters

Slide 36

Selection of 2 ms TTI

Selection starts from CELL_DCH CPICH RSCP (HSPA serving cell) must satisfy:
PtxPrimaryCPICH CableLoss* Meas CPICH RSCP < CPICHRSCPThreEDCH2MS + MAX(0,
UETxPowerMaxRef P_MAX)

UETxPowerMaxRef CPICHRSCPThreEDCH2MS
max. Tx power level a defines 2ms TTI coverage area
reference UE can use (max. path loss)
RNC; -50..33; 1; 24 dBm RNC; 50..160 dB; 1 dB; 136 dB
Selection starts from CELL_FACH, CELL_PCH or URA_PCH CPICH Ec/Io of current cell
must satisfy:
Meas CPICH Ec/Io > CPICHECNOThreEDCH2MS CPICHECNOThreEDCH2MS
defines 2ms TTI coverage area
(min. Ec/Io)
RNC; -24..0 dB; 1 dB; -6 dB

Selection starts from Inter-RAT Handover to UTRAN or from LTE (CPICH Ec/Io not known) Calculated CPICH Ec/Io of
current cell must satisfy:
c> LoadBasedCPICHEcNoThreEDCH2MS

C MAX MIN Ptx,CPICH P tx _ total ,0 ,24dB LoadBasedCPICHEcNoThreEDCH2MS
defines 2ms TTI coverage area
(min. calulated Ec/Io)
RNC; -25..0 dB; 1 dB; 0 dB (means only 10ms TTI
allowed)
36 13/07/2016 Nokia 2014 - RN3164-16A WCD
36 RN31648EN16GLA0 2016 Nokia * set to 0 dB if no MHA

RN31648EN16GLA0 35
HSUPA RRM & Parameters

Slide 37

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
37 13/07/2016 Nokia 2014 - RN3164-16A WCD
37 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 36
HSUPA RRM & Parameters

Slide 38

Overview Scheduling Request


Scheduling information (MAC-e on E-DPDCH) or happy bit (E-DPCCH)

E-AGCH
E-DCH Absolute Grant Channel
E-RNTI & max. power ratio E-DPDCH/DPCCH (Absolute Grant)
Scheduling
Grants E-RGCH
E-DCH Relative Grant Channel
UP / HOLD / DOWN (Relative Grant)

E-DPCCH
E-DCH Dedicated Physical Control Channel
L1 control: E-TFCI, RSN, happy bit
UE
E-DPDCH
E-DCH Dedicated Physical Data Channel
Node B User data & CRC

E-HICH
E-DCH Hybrid ARQ Indicator Channel
ACK/NACK

RSN: Re-transmission sequence number

38 13/07/2016 Nokia 2014 - RN3164-16A WCD


38 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 37
HSUPA RRM & Parameters

Slide 39

E-DPDCH
E-DPDCH
carries UL packet data
up to 4 E-DPDCHs for 1 RL
Max. configuration according 3GPP: 2 * SF2 + 2 * SF4
Max. configuration according RU40 2ms TTI: 2 * SF2 + 2 * SF4
Max. configuration according RU10 RU40 with 10ms TTI: 2 * SF2
SF = 256 2 (BPSK-like (QPSK) and Dual 4PAM (16QAM)
Pure user data & 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 (or MAC-i/is in RU40 with Flexible RLC feature)
Error protection based on turbo coding 1/3
Soft / softer handover support

39 13/07/2016 Nokia 2014 - RN3164-16A WCD


39 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 38
HSUPA RRM & Parameters

Slide 40

E-DPCCH
E-TFCI (7 bit): E-DCH Transport Block Size i.e. Coding at given TTI
RSN: Retransmission Sequence Number RSN (2 bit)
Value = 0 / 1 / 2 / 3 for initial transmission, 1st / 2nd / further retransmission
Happy bit (1 bit): indicates if UE needs more resources or not: = 1, = 0
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
10 ms TTI => the 30 bits are repeated 5 times during the 10 ms

Happy bit HappyBitDelayConditionEDCH


Forms input for MAC-e scheduler in Node B Happy bit delay condition for E-DCH
Included as part of E-DPCCH RNC; 2, 10, 20, 50, 100, 200, 500, 1000 ms; 50 ms
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 following conditions true:
1. UE transmitting as much scheduled data as allowed by current Serving Grant
2. UE has sufficient power to transmit at higher data rate
3. with current Serving Grant, UE would need at least the following time to transmit the total amount of data in
its buffer: HappyBitDelayConditionEDCH

40 13/07/2016 Nokia 2014 - RN3164-16A WCD


40 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 39
HSUPA RRM & Parameters

Slide 41

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. For 10ms TTI users the scope always
applies to all HARQ processes
Transfers E-RNTI (16 bit)
Timing information when Absolute Grants are sent in the
physical channel
Transmitted only 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

41 13/07/2016 Nokia 2014 - RN3164-16A WCD


41 RN31648EN16GLA0 2016 Nokia

HSUPA in BTS p.12

RN31648EN16GLA0 40
HSUPA RRM & Parameters

Slide 42

E-RGCH & E-HICH


E-RGCH: Enhanced Relative Grant Channel RG value RG value
Command
transfers Relative Grant value (Serving E-DCH RLS) (other Radio Links)
can be transmitted by any active HSUPA cell UP +1 Not allowed
Cells belonging to Serving Radio Link set may HOLD 0 0
command Up, Down & Hold DOWN -1 1
other cells only able to command Down & Hold
SF 128 used
E-RGCH can occupy
!2 ms TTI and serving radio link set occupies 2 ms!
10 ms TTI and serving radio link set occupies 8 ms Channelization Code(s):
2 ms TTI: E-RGCH is not used shared for specific UE by E-RGCH & E-HICH
Non serving radio link set occupies 2ms or 10 ms
40 orthogonal signatures/Code allow up to
20 UEs to be served with E-RGCH & E-HICH
E-HICH: Enhanced H-ARQ Indication Channel information (per code)

transfers E-DCH HARQ acknowledgements (ACK/NACK)


transmitted by all Active Set cells
Cell belongs to Radio Link Set, ACK NACK is transmitted
other cells transmit only ACK. (UE continues to re-transmit until ACK
received from at least one cell (or until re-transmission time out))
RG value RG value
SF 128 used Command
(Serving E-DCH RLS) (other Radio Links)
E-HICH can occupy ACK +1 +1
2 ms TTI and serving radio link set occupies 2 ms NACK -1 0
10 ms TTI and serving radio link set occupies 8 ms
42 13/07/2016 Nokia 2014 - RN3164-16A WCD
42 RN31648EN16GLA0 2016 Nokia

Leliwa HSUPA ch p. 300


RRM HSUPA p. 42

RN31648EN16GLA0 41
HSUPA RRM & Parameters

Slide 43

Serving / Non-Serving Radio Link Set RLS cells

Serving E-DCH RLS cells


.
(under same Node B)
Transmit same Relative Grant on E-RGCH
Allowed UP, HOLD, DOWN

E-DCH Non-serving RLS cells


Serving E-DCH cell . (under different Node B)
defined by Serving HSDPA cell transmit relative grants on E-RGCH
transmits Absolute Grant on E-AGCH Allowed HOLD, DOWN
DOWN = overload indication
HOLD = dont care

Iub
Iub

RNC
Iu

43 13/07/2016 Nokia 2014 - RN3164-16A WCD


43 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 42
HSUPA RRM & Parameters

Slide 44

Dynamic E-RGCH/E-HICH code allocation

max. 40 signatures available with 1 SF128 code


1 signature for coding of E-RGCH & E-HICH each
max. 20 UEs/code since RU30:
RNC checks requirement for a new
max. # E-RGCH/E-HICH codes: E-RGCH/E-HICH code every time an
using HSPA72UsersPerCell (RU30) (HSPA128UsersPerCell HSUPA connection is allocated
disabled) max. 4
using HSPA128UsersPerCell (RU40) max. 32
elsewise: 1

for signatures for further


RsrvdSignaturesOffset
dynamically allocate upgrades signatures upgrade
WCEL; 5..1118; 1; 10 40 more signatures (1 code) RsrvdSignaturesOffset

Allocation of additional code: Traffic increase


# of free signatures
Traffic decrease
RsrvdSignaturesOffset

Release of existing code (from RN6.0 onwards):


39 signatures
# of free signatures > dynamically release
39 + 2x RsrvdSignaturesOffset 40 signatures (1 code) 40 signatures

44 13/07/2016 Nokia 2014 - RN3164-16A WCD


44 RN31648EN16GLA0 2016 Nokia

RRM HSUPA p. 42
RRM HSUPA p. 43

RN31648EN16GLA0 43
HSUPA RRM & Parameters

Slide 45

DPDCH, DPCCH & HS-DPCCH

DPDCH E-AGCH
Absolute Grant
for Voice & SRB if CS Voice over HSPA not used
3.4 kbps SRB uses SF128
E-RGCH
DPCCH Relative Grant: UP / HOLD / DOWN
for TPC, TFCI & pilot bits,
if CPC not enabled E-DPCCH
HS-DPCCH L1 control: E-TFCI, RSN, happy bit

for HSDPA CQI & ACK/NACK


E-DPDCH
User data & CRC

E-HICH
Node B ACK/NACK UE
HS-DPCCH
ACK/NACK & CQI

a-DCH (DPDCH & DPCCH)

45 13/07/2016 Nokia 2014 - RN3164-16A WCD


45 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 44
HSUPA RRM & Parameters

Slide 46

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
46 13/07/2016 Nokia 2014 - RN3164-16A WCD
46 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 45
HSUPA RRM & Parameters

Slide 47

E-TFC Selection (1/4)

Idea:
UE selects appropriate Transport Block Size
depending on:
UE Capability
Transmission power
Service grant
TB size derived from TB index with help of TBS size
table
1 TBS size table for each TTI (2 ms & 10 ms)
Supported Tables with 10ms TTI
Table 0 and Table 1
Supported Tables with 2ms TTI
Table 0 and Table 1
TBS size tables optimized for MAC-d PDU sizes of 336
and 656 bits

TS 25.321 MAC
Annex B

47 13/07/2016 Nokia 2014 - RN3164-16A WCD


47 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 46
HSUPA RRM & Parameters

Slide 48

E-TFC Selection (2/4)

Step 1: Exclude E-TFC


based upon UE category
In blocked state
Excluded: UE without
sufficient transmit
power (blocked state)
0 2 Excluded: Transport
Block size too small for 336 bit
MAC-d PDU

0 3 Excluded: minimum E-
TFCI Set parameter
EDCHMinimumSetETFCI
minimum E-TFCI set
WCEL; 0..120; 1; 4 = 372 bit

minimum E-TFCI set


maximum E-TFC which cannot be
blocked due to lack of UE power Excluded: not
Can be used if supported by UE
absolute service grant given Category 3
no DCH transmission present

48 13/07/2016 Nokia 2014 - RN3164-16A WCD


48 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 47
HSUPA RRM & Parameters

Slide 49

E-TFC Selection (3/4)


Step 2
Identify E-TFC allowed by serving grant (maximum E-DPDCH / DPCCH power ratio)
Select E-TFC based upon quantity of data to be send

Excluded E-TFC:
based upon
UE can select e.g. this Serving Grant
E-TFC because if it has
less data to send

Max. available E-TFC


(UE has to send a lot of data)

49 13/07/2016 Nokia 2014 - RN3164-16A WCD


49 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 48
HSUPA RRM & Parameters

Slide 50

E-TFC Selection (4/4)


Puncturing Limit
Puncturing limit PLnon_max = 0.68 when 10ms TTI (also for HS-RACH)
UE selects appropriate SF & number of E-DPDCH PLnon_max = 0.6 when 2ms TTI (hard coded by NOKIA)
once it knows E-TFC PLmax = 0.44 when not using 2SF2 + 2SF4 (3GPP)
Maximum amount of puncturing PLmax = 0.33 when using 2SF2 + 2SF4 (3GPP)
1 - PLnon_max if number of code channels < maximum
1 - PLmax if number of code channels = maximum
User Data Rate = L1 Rate (SF) / ( Puncturing limit x 3 ) Turbo Coding 1/3
SF & E-DPDCH selection
Step 1 can transport block be accommodated using single E-DPDCH without puncturing?
Yes => select highest SF which avoids puncturing
No => go to step 2

Step 2 can transport block be accommodated using single E-DPDCH with PLnon_max ?
Yes => select lowest SF (minimise puncturing)
No => go to step 3

Step 3 last resort


select one or more E-DPDCH which offer highest number of bits without exceeding PLmax
Example:
TTI = 10 ms, TBS = 10 kbit 1 Mbps
Step 1) L1 Rate (SF) = User Data Rate x 3 = 3 Mbps go to step 2
Step 2) L1 Rate (SF) = User Data Rate x 3 x PLnon_max = 2.04 Mbps go to step 3
Step 3) L1 Rate (SF) = User Data Rate x 3 x PLmax = 1.32 Mbps 2 x SF4 required
50 13/07/2016 Nokia 2014 - RN3164-16A WCD
50 RN31648EN16GLA0 2016 Nokia

WCDMA RAN RRM HSUPA p.92

RN31648EN16GLA0 49
HSUPA RRM & Parameters

Slide 51

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
Throughput & Load Based Scheduling
Absolute & Relative Service Grant
Scheduling Process
Load Increase & Decrease
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
51 13/07/2016 Nokia 2014 - RN3164-16A WCD
51 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 50
HSUPA RRM & Parameters

Slide 52

Throughput & Load Based Scheduling (1/4)


Throughput & load based scheduling
HSUPA scheduler combines throughput & load based algorithms
Throughput based scheduling applied for lower load
Power based scheduling applied for higher load
Lmin_cell Maximum cell load for
HSUPA scheduling
-95
Throughput based Power based
-96
Load derived from Load derived
-97
throughput from RTWP
PrxMaxOrigTargetBTS
relative to PrxNoise;
-98
should be > PrxMaxTargetBTS
-99
RTWP (dBm)

PrxMaxTargetBTS
-100 relative to PrxNoise;
should be > PrxTarget + PrxOffset
-101

-102

-103 PrxLoadMarginEDCH
-104
relative to PrxNoise
PrxNoise
-105
WCEL: -130..-50; 0.1; -105 dBm
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
Load
52 13/07/2016 Nokia 2014 - RN3164-16A WCD
52 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 51
HSUPA RRM & Parameters

Slide 53

Throughput & Load Based Scheduling (2/4)


Throughput based scheduling PrxLoadMarginEDCH
Interference margin for minimum E-DCH
Node B calculates own cell load
load; WCEL; 0..30; 0.1; 2 dB 1.585
If own cell load < Lmin_cell then throughput based scheduling can be applied
Corresponding load factor LminCell =
to increase own cell load up to Lmin_cell 1 - 1/100.2 = 0.37 (37 %)
Actual own Load factor < margin
Lmin_cell Max. cell load for
cell load throughput based load estimation
HSUPA scheduling
-95 Otherwise
RTWP based load estimation
-96

-97 PrxMaxOrigTargetBTS

-98

-99 PrxMaxTargetBTS
RTWP (dBm)

-100 Schedulable
resource
-101

-102
PrxLoadMarginEDCH
WCEL; 0..30; 0.1; 2 dB 1.585
-103
LminCell 37%
-104
PrxNoise
-105 WCEL: -130..-50; 0.1; -105 dBm
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
Load
53 13/07/2016 Nokia 2014 - RN3164-16A WCD
53 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 52
HSUPA RRM & Parameters

Slide 54

Throughput & Load Based Scheduling (3/4)


PrxMaxTargetBTS
Load based scheduling Max. target Rx wide band power for BTS
WCEL; 0..30; 0.1; 6 dB = 2.0
if calculated own cell load > Lmincell power based scheduling is
applied to increase total cell load up to maximum cell load Corresponding load factor LmaxCell =
1 - 1 / 100.6 = 0.75 (75 %)
Node B measures actual RTWP & calculates actual total load
RTWP < maximum target more HSUPA service
can be offered
Lmin_cell Max. cell load for Otherwise
-95 HSUPA scheduling more HSUPA service can not be offered any more;
HSUPA service has to be down-graded if too much RWP
-96 Actual own Actual total cell from non served UEs in comparison to E-DCH RWP
cell load load =
-97
own cell load +
PrxMaxOrigTargetBTS
-98 inter cell
interference PrxMaxTargetBTS
-99
RTWP (dBm)

WCEL; 0..30; 0.1; 6 dB = 2.0


-100 LmaxCell = 75%
Schedulable
-101
resource

-102
PrxLoadMarginEDCH
-103 WCEL; 0..30; 0.1; 2 dB 1.585
LminCell 37%
-104

PrxNoise
-105
WCEL: -130..-50; 0.1; -105 dBm
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
Load
54 13/07/2016 Nokia 2014 - RN3164-16A WCD
54 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 53
HSUPA RRM & Parameters

Slide 55

Throughput & Load Based Scheduling (4/4)


PrxMaxOrigTargetBTS
Load based scheduling (Interference Cancellation feature Max target received wide band original power for BTS.
(RAN1308) is applied) Parameter used when Interference Cancellation
(RAN1308) is applied. WCEL; 0..30; 0.1; 8 dB
if calculated own cell load > Lmincell power based scheduling is Corresponding load factor LmaxCell =
applied to increase total cell load up to maximum cell load 1 - 1 / 100.8 = 0.85 (85 %)
Node B measures actual RTWP & calculates actual total load RTWP < maximum target more HSUPA
Lmin_cell Max. cell load for service can be offered
-95 HSUPA scheduling Otherwise
more HSUPA service can not be offered any more;
-96 Actual own Actual total cell
cell load load =
-97
PrxMaxOrigTargetBTS
own cell load + WCEL; 0..30; 0.1; 8 dB
-98 inter cell PrxMaxOrigTargetBTS= 85%
interference
-99
RTWP (dBm)

PrxMaxTargetBTS
WCEL; 0..30; 0.1; 6 dB = 2.0
-100 Schedulable
resource LmaxCell = 75%
-101 Defines the maximum target level for
residual received total wideband power in
-102
E-DCH scheduling.
The residual received total wideband
-103
power is the received interference power
-104 after interference cancellation has been
performed.
-105
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
Load
55 13/07/2016 Nokia 2014 - RN3164-16A WCD
55 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 54
HSUPA RRM & Parameters

Slide 56

Absolute & Relative Service Grant (1/2)

Absolute grant
BTS signals maximum allowed power ratio E-DPDCH / DPCCH by
service grant value
Mapping between service grant values & power ratios hardcoded
Mapping between power ratios & E-TFCs hardcoded
Initial power ratio = (21/15)2 independent on service profile and
UL load (corresponds to 32 kbps)

TB-Index Amplitude Ratio E-TFC


(= E-TFC)
3 21/15
Serving grant
7 27/15 values
11 34/15 Power ratio
19 47/15 E-DPDCH / DPCCH
39 60/15
67 60/15
85 75/15
103 84/15

TB Index 103 TB size = 15492 bit/10ms 1549.2 kbps

56 13/07/2016 Nokia 2014 - RN3164-16A WCD


56 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 55
HSUPA RRM & Parameters

Slide 57

Absolute & Relative Service Grant (2/2)

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

57 13/07/2016 Nokia 2014 - RN3164-16A WCD


57 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 56
HSUPA RRM & Parameters

Slide 58

Scheduling Process (1/4)


E-AGCH
First bit rate ramp up Absolute Grant
E-AGCH can rapidly increase bit rate allocated to an UE if only 1
Applicable if there is a single modifiable unhappy UE unhappy UE
UE bit rate is not allowed to increase while PS Upgrade Timer Tup is running
Value of Tup = 50 ms hardcoded
BTS attempts to assign the available resources to that UE using the E-AGCH

Handling Non-Serving Cell overload


Scheduling procedure is completed every 10 ms
Scheduler shall transmit DOWN grant to UE whose serving E-DCH Handling non-serving cell overload
RL is not provided by that BTS if the following criteria are true
RTWP Measured > PrxMaxTargetBTS AND TargetNSEDCHToTotalEDCHPR PrxMaxTargetBTS
Non-serving E-DCH to total E-DCH power ratio > Target non-serving E-DCH WCEL; 0..30; 0.1;
TargetNSEDCHToTotalEDCHPR to total E-DCH power ratio 6 dB = 2.0
WCEL; 0..100 %; = 1 %; 30 % LmaxCell = 75%

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 %)
Target non-serving E-DCH to total E-DCH power ratio e.g.: = 20% / 40% = 0.5 (50 %) >
TargetNSEDCHToTotalEDCHPR
both conditions fulfilled DOWN command allowed

58 13/07/2016 Nokia 2014 - RN3164-16A WCD


58 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 57
HSUPA RRM & Parameters

Slide 59

Scheduling Process (2/4): Handling congestion indicators


Downgrading phase (B C):
Iub congestion detected and reported on per UE basis Handling non-serving cell overload
(Frame Protocol from RNC)
Downgrading phase: PS gives relative grant DOWN in pre-defined
time interval based upon received congestion indicator Handling congestion indicators
Congestion cause can be either Delay Build-up or Frame Loss
Frame Loss cause results in more rapid decrease of
allocated grant (shorter time between down commands)
Remaining phase (C D):
Resource reserved & No Congestion indication received
not allocated to other UE Timer T2 started
DOWN grants generated periodically Packet scheduler does nothing
until No Congestion indication Resource reserved & ignores happy bit & low utilization ratio
Congestion
is received from the RNC not allocated to other UE holds current allocated E-TFCI &
indication while T3 is running reserves released power for UE
received from
the RNC
Timer T2 stopped if further congestion
indicators received
RG Down No Recovering phase (D E):
T2 expires
Congestion Packet scheduler gives relative grant
indication T3 starts command based upon Happy Bit & other
received available scheduling information
Rest of reserved power shall be kept for this
UE while T3 is running
B C D E
59 13/07/2016 Nokia 2014 - RN3164-16A WCD
59 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 58
HSUPA RRM & Parameters

Slide 60

Scheduling Process (3/4)

Handling low utilization Handling non-serving cell overload

Node B monitors utilization of each HSUPA connection


Utilization measured by comparing the E-DPDCH / DPCCH Handling congestion indicators
power ratios used by UE with those allocated by Node B
Measurements filtered prior to evaluation, memory factor
used for filtering Handling low utilization

Utilization

Handling low utilization


Low utilisation
flag set (downgrade queue)
Low utilisation
flag cleared
UE considered for downgrade once every
scheduling period
Scheduler checks for low utilisation UE
within the downgrade queue
Low utilisation threshold Relative grant channel (E-RGCH) used to
(0.8, hardcoded)
instruct downgrade
time
Low utilization time to Downgrade queue:
trigger (30 ms, hardcoded) highest allocated E-TFCI = highest priority;
lowest allocated E-TFCI = lowest priority
60 13/07/2016 Nokia 2014 - RN3164-16A WCD
60 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 59
HSUPA RRM & Parameters

Slide 61

Scheduling Process (4/4)


Handling non-serving cell overload
Handling load increase / decrease
Calculate maximum of the load increases Handling congestion indicators
allowed by throughput & power based
thresholds
If either is positive then E-DCH load can be Handling low utilization
increased
Otherwise E-DCH load is decreased Lrx_EDCH_Allowed =
Max(Lrx_EDCH_Power, Lrx_EDCH_Throughput)

Lrx_EDCH_Allowed > 0
PrxLoadMarginEDCH
0..30; 0.1; 2 dB 1.585 Yes No
LminCell 37%
Load increase Load decrease
estimation estimation
PrxMaxTargetBTS:
0..30; 0.1; 6 dB = 2.0
LmaxCell = 75% Allocate Grant Allocate Grant

61 13/07/2016 Nokia 2014 - RN3164-16A WCD


61 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 60
HSUPA RRM & Parameters

Slide 62

Load Increase & Decrease (1/2) Handling load increase (upgrade queue)
Node B maintains upgrade queue for each
Handling load increase HSUPA UE whose serving RL belongs to that Node
B
Node B sorts UEs according to their current max.
allocated E-TFCI
Yes UE with lowest allocated E-TFCI is allocated
Single Modifiable unhappy UE?
highest priority
If 2 UE have same allocated E-TFCI UE with
fast Ramp-Up No highest utilisation is assigned the highest priority
Procedure UEs with low utilisation shall not be considered
when allocating upgrades

No Modifiable unhappy UEs exists?

Exit Yes
Increase the bit rate of the modifiable
Load increase unhappy UEs using the E-RGCH
estimation

Yes

Yes
Sufficient margin to allow an Hardware resources available?
increase

No No

62 13/07/2016 Nokia 2014 - RN3164-16A WCD


62 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 61
HSUPA RRM & Parameters

Slide 63

Load Increase & Decrease (2/2)


Handling load decrease

PrxMaxTargetBTS:
Load > 0..30; 0.1; 6 dB = 2.0
No
PrxMaxTargetBTS ? LmaxCell = 75%
Exit Yes

No Active E-DCH Exists?

Exit Yes

Decrease the UEs bit rate


using the E-RGCH

Load decrease
estimation

63 13/07/2016 Nokia 2014 - RN3164-16A WCD


63 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 62
HSUPA RRM & Parameters

Slide 64

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
Power Control for HSUPA DL Channels
Power Control (Inner & Outer Loop) for HSUPA UL Channels
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix

64 13/07/2016 Nokia 2014 - RN3164-16A WCD


64 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 63
HSUPA RRM & Parameters

Slide 65

Power Control for HSUPA DL Channels (1/2)


Overview

RU40 introduces fully dynamic power control for HSUPA DL channels for Rel.2&3 HW
This saves a few % of DL power for user data
A proprietary algorithm using CQI, L1 ACK/NACK and DL TPC information

DL Power Tx Power F-DPCH


Control
CQI
Tx Power E-HICH
DL TPC Inner
Loop & Tx Power E-RGCH
L1 HSPA ACK & NACK Outer
Loop Tx Power E-AGCH

Power offsets from


RNC databuild
65 13/07/2016 Nokia 2014 - RN3164-16A WCD
65 RN31648EN16GLA0 2016 Nokia

WCDMA RAN RRM HSUPA p.169

RN31648EN16GLA0 64
HSUPA RRM & Parameters

Slide 66

Power Control for HSUPA DL Channels


E-AGCH, E-RGCH & E-HICH

PtxOffsetEAGCHDPCCH PtxOffsetExxCH2ms PtxOffsetExxCHSHO


PtxOffsetERGCHDPCCH power offset to E-xxCH power offsets power offset to E-xxCH power offsets for
PtxOffsetEHICHDPCCH for E-DCH 2 ms TTI case 2ms TTI E-DCH SHO case and F-DPCH
Tx power relative to pilot bits on DL DPCCH / WCEL; -5..15; 0.25; 5 dB does not exist
TPC bits on F-DPCH WCEL; -5..10; 0.25; 3 dB
WCEL; -32..31.75; 0.25; 0 dB

66 13/07/2016 Nokia 2014 - RN3164-16A WCD


66 RN31648EN16GLA0 2016 Nokia

WCDMA RAN RRM HSUPA p.169

RN31648EN16GLA0 65
HSUPA RRM & Parameters

Slide 67

Power Control for HSUPA DL Channels


F-DPCH

PtxFDPCHMax
max. power for TPC bits of F-DPCH
WCEL; -5..30; 0.1; 4 dB

PtxFDPCHMin
min. power for TPC bits of F-DPCH
WCEL; -5..30; 0.1; 10 dB

PtxOffsetFDPCHSHO
power offset to F-DPCH power for E-
DCH SHO case
WCEL; 0..10; 0.5; 3 dB

max. Tx power = PtxPrimaryCPICH - PtxFDPCHMax + PtxOffsetFDPCHSHO


e.g. 33 dBm 4 dB + 1 dB = 30 dBm
min. Tx power = PtxPrimaryCPICH - PtxFDPCHMin + PtxOffsetFDPCHSHO
e.g. 33 dBm 10 dB + 1 dB = 24 dBm

If PtxFDPCHMin=PtxFDPCHMax, then power control for DL HSUPA channels is deactivated.

67 13/07/2016 Nokia 2014 - RN3164-16A WCD


67 RN31648EN16GLA0 2016 Nokia

PKDB PtxFDPCHMax parameter description

RN31648EN16GLA0 66
HSUPA RRM & Parameters

Slide 68

Power Control for HSUPA DL Channels


Prior to RU40 HSUPA Downlink Physical Channel
Power Control
Transmitted Power of HSUPA Downlink Physical Transmitted Power of HSUPA Downlink Physical
channels is controlled through Power Offsets channels is controlled dynamically.
between HSUPA DL channels and: Value of Tx power is changed and is incremented for
CPICH RU10 the UE which are at a bigger distance from the
DL DPCCH RU20 & RU30 NodeB

E-AGCH Power Offset TX power is controlled dynamically


NodeB Tx Power NodeB Tx Power Level

35.00 35.00

30.00
NodeB Tx Power Level [dBm]
30.00
25.00
25.00
20.00
Tx power [dBm]

20.00 15.00

15.00 10.00

10.00
E-RGCH Power Offset / E- 5.00

HICH Power Offset 0.00


5.00 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 1.1 1.2 1.3 1.369
-5.00

0.00 -10.00
Distance from NodeB [km] UE Distance from NodeB [km]

CPICH E-AGCH E-EGCH/E-HICH CPICH E-AGCH E-RGCH/E-HICH

Better common control channels power utilization


The saved power of the DL HSUPA control channels provides increased HSDPA capacity
68 13/07/2016 Nokia 2014 - RN3164-16A WCD
68 RN31648EN16GLA0 2016 Nokia

PKDB PtxFDPCHMax parameter description

RN31648EN16GLA0 67
HSUPA RRM & Parameters

Slide 69

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
Power Control for HSUPA DL Channels
Power Control (Inner & Outer Loop) for HSUPA UL Channels
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix

69 13/07/2016 Nokia 2014 - RN3164-16A WCD


69 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 68
HSUPA RRM & Parameters

Slide 70

Inner Loop Power Control for E-DPDCH & E-DPCCH (1/3)


same as for Rel. 99 DCH
Gain Factor
Spreading with
Power relative to DPCCH channelization code

c ed,1 ed,1 iq ed,1 I- or Q- branch


DPCCH Cc = CC256,0 (Q-branch)
c signalled by higher layer E- DPDCH 1
= 1 if no DPDCH
.
.
E-DPCCH Cec = CC256,1 (I-branch)
.
ec = c * Aec . ed,k
c ed,k iq ed,k
E- DPDCH k
signaled by
index A = /


higher layer ec ec c .
. I+jQ
8 30/15 .
Aec: 7 24/15 . c ed,K ed,K iqed,K
amplitude 6 19/15
ratio E- DPDCH K
5 15/15
4 12/15
3 9/15 ec
cec iqec
2 8/15
1 6/15 E- DPCCH
0 5/15

70 13/07/2016 Nokia 2014 - RN3164-16A WCD


70 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 69
HSUPA RRM & Parameters

Slide 71

Inner Loop Power Control for E-DPDCH & E-DPCCH (2/3)


Aed
Gain Factor
Spreading with
Index = ed / c channelisation code

c ed,1 ed,1 iq ed,1 I- or Q- branch


E-DPDCHk
E- DPDCH 1
ed = c * Aed
.
.
.
. c ed,k ed,k iq ed,k


E- DPDCH k I+jQ
UE determines
gain factor ed,k .
based on maximum .
Aed given by service .
grant and selected . c ed,K ed,K iq ed,K
E-TFC
E- DPDCH K

cec ec iqec
E- DPCCH

71 13/07/2016 Nokia 2014 - RN3164-16A WCD


71 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 70
HSUPA RRM & Parameters

Slide 72

Inner Loop Power Control for E-DPDCH & E-DPCCH (3/3)


Aed in case of 16 QAM
Power boosted mode (applicable to HSUPA 16 QAM)
Aed
PE-DPCCH/PE-E-DPDCH/ = const
Index
Signalled values for

= /
Quantized amplitude
ed c
E-DPDCH
ratios
Aed = ed/ c PE-DPDCH depended on E-DPDCH instead of DPCCH
31 377/15
30 336/15
29 299/15 Low E-TFCI High E-TFCI
28 267/15 Non boosted mode (non-16QAM)
27 237/15
26 212/15 PE-DPCCH/PDPCCH/ = const
25 189/15
24 168/15
Low E-TFCI High E-TFCI

(E-TFC2)
23 150/15
22 134/15
21 119/15
20 106/15 High own signal interference
E-DPCCH more robust to own E-DPDCH

PE-DPDCH
19 95/15 from E-DPDCH cause
18 84/15 received E-DPCCH too poor signal interferences from high
17 75/15 E-DPDH power

(E-TFC2)
16 67/15
15 60/15
14 53/15
E-DPDCH
PE-DPDCH
13 47/15
12 42/15
11 38/15
10 34/15
9 30/15
8 27/15

PE-DPCCH
7 24/15
PE-DPDCH (E-TFC1) E-DPDCH E-DPCCH
6 21/15 PE-DPDCH (E-TFC1) E-DPDCH
5 19/15
4 17/15
3 15/15 PE-DPCCH E-DPCCH E-DPCCH
PE-DPCCH E-DPCCH
2 13/15
1 11/15

PDPCCH
0 8/15 PDPCCH DPCCH DPCCH
PDPCCH DPCCH DPCCH

72 13/07/2016 Nokia 2014 - RN3164-16A WCD


72 RN31648EN16GLA0 2016 Nokia

3GPP 25.213 Table 1B.2A

RN31648EN16GLA0 71
HSUPA RRM & Parameters

Slide 73

Outer Loop Power Control OLPC for E-DPDCH & E-DPCCH


R99 HSUPA
1 OLPC entity for each transport channel 1 OLPC entity for DCH + 1 OLPC entity for E-DCH
1 OLPC controller for all entities belonging One OLPC entity per each RAB
to same RRC connection 1 OLPC controller for all entities belonging to
same RRC connection
BLER target for RAB fixed
Up to four OLPC entities per E-DCH connection
BLER target for RAB no longer fixed
Adjusted by OLPC controller both for DCH and E-DCH on
basis of current performance
Current BLER of DCH affects BLER target for E-DCH and
vice versa
OLPC controller selects entity which AC provides ideal and maximum BLER target both for DCH
indicates largest increase of SIR target and E-DCH
Change of SIR target calculated according OLPC controller selects entity which indicates largest
difference current BLER fixed BLER target difference current BLER ideal BLER target
Change of SIR target calculated according
difference current BLER current BLER target

RAN2302 Dynamic HSUPA BLER: Non Real Time (NRT) HSUPA Non-Real Time traffic
HSUPA BLER target is dynamically adapted based on HSUPA
user transmission constraints: 2msTTI:
10%BLER on 1%BLER on
Continuous data stream; Bursty traffic; close to Peak data 2nd ReTx*
10%BLER on 1st ReTx*
rates; 10ms TTI: 1st ReTx*
E-DCH TTI: 2ms TTI, 10 ms TTI; 20%BLER on
1st ReTx*
Number of Retransmissions (ReTx); *Example values.

73 13/07/2016 Nokia 2014 - RN3164-16A WCD


73 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 72
HSUPA RRM & Parameters

Slide 74

OLPC for E-DPDCH & E-DPCCH


MaxBLERTargetDCH
Max. BLER target on DCH
Maximum & ideal BLER target
RNC; -4..-0.3; 0.1; -2 1%
Provided by AC both for DCH and E-DCH BLERTargetDCH
Values hardcoded, not configurable by operator Ideal BLER target on DCH
BLER values given on logarithmic scale RNC; -4..-0.3; 0.1; -2 1%

MaxL1BLERTargetEDCH
Current BLER target on DCH Max. layer 1 BLER target on E-DCH
Combination of RNC; -4..-0.3; 0.1; -0.8 16%
Ideal BLER target on DCH L1BLERTargetEDCH
Deviation of current BLER from ideal BLER target on E-DCH Ideal layer 1 BLER target on E-DCH
BLER_Target_DCH = BLERTargetDCH + RNC; -4..-0.3;0.1; -1 10%
DCHSlopeOfTheCurve x (L1BLERTargetEDCH BLER_EDCH)
DCHSlopeOfTheCurve
DCH slope of the curve
RNC; 0.1..0.5; 0.1; 0.2
Current BLER target on E-DCH
Combination of EDCHSlopeOfTheCurve
Ideal BLER target on E-DCH EDCH slope of the curve
Deviation of current BLER from ideal BLER target on DCH RNC; 1..5; 0.5; 2

BLER_Target_E-DCH = L1BLERTargetEDCH +
EDCHSlopeOfTheCurve x (BLERTargetDCH BLER_DCH)

74 13/07/2016 Nokia 2014 - RN3164-16A WCD


74 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 73
HSUPA RRM & Parameters

Slide 75

OLPC for E-DPDCH & E-DPCCH

Example
Ideal BLER target on DCH = 1 %
Ideal BLER target on E-DCH = 10 %
DCHSlopeOfTheCurve = 1..3

15
BLER target on E-DCH / %

10
Increasing BLER on DCH
Lower BLER target on E-DCH
Stronger trend to increase SIR target
5 (even if DCH is not worst channel)

Decreasing BLER on DCH


0 Higher BLER target on E-DCH
0 1 2 3 4 5 Stronger trend to decrease SIR target
(even if DCH is not best channel)
current BLER on DCH / %

75 13/07/2016 Nokia 2014 - RN3164-16A WCD


75 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 74
HSUPA RRM & Parameters

Slide 76

OLPC for E-DPDCH & E-DPCCH


BLER target set by OLPC after number of ReTransmissions (ReTx)
BER target is adjusted by OLPC depending on
Values configurable by operator the data rate
DynHSUPABLERPeakRateRx Values configurable by operator
L1 HARQ retransmissions threshold to use Peak Rate BLER target in OLPC
RNC; 1..3; 1; 1 DynHSUPABLERMaxRateThrB
DynHSUPABLERContDataRx2 Peak rate threshold for Bursty data rates RNC;
L1 HARQ retransmissions threshold to use Continuous Data Rate BLER target 10..100; 1; 75 75%
in OLPC when TTI=2ms RNC; 1..3; 1; 2 Switch to Peak Rate BLER target when data rate is
DynHSUPABLERContDataRx10 higher than 75% of Max Data Rate
L1 HARQ retransmissions threshold to use Continuous Data Rate BLER target DynHSUPABLERMaxRateThrC10
in OLPC when TTI=10ms RNC; 1..3; 1; 1 Peak rate threshold for Continuous 10ms TTI
transmission RNC; 10..100; 1; 65 65% Switch to
BLER Target value for EDCH NRT OLPC is set with parameter Peak Rate BLER target when TTI=10ms and data rate
is higher than 75% of Max Data Rate
Values configurable by operator
DynHSUPABLERMaxRateThrC2
L1ContBLERTrgtEDCH10 Peak rate threshold for Continuous 2ms TTI
L1 BLER target for the Continuos E-DCH data stream when TTI = 10 ms. RNC; - transmission RNC; 10..100; 1; 60 60%
2..0; 0.1; -0.7 20% Switch to Peak Rate BLER target when TTI=2 ms and
L1ContBLERTrgtEDCH2 data rate is higher than 75% of Max Data Rate
L1 BLER target for the Continuos E-DCH data stream when TTI = 2 ms. RNC; -
2..0; 0.1; -1 10%
L1BurstDataBLERTrgtEDCH
L1 BLER target for the Bursty E-DCH data stream. RNC; -2..0; 0.1; -1 10%
L1PeakRateBLERTrgtEDCH
L1 BLER target for the Peak E-DCH data rate. RNC; -2..0; 0.1; -2 1%

RU40 RAN2302 Dynamic HSUPA BLER required


Note: parameter defaults are due to change at the time of creation of this document
76 13/07/2016 Nokia 2014 - RN3164-16A WCD
76 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 75
HSUPA RRM & Parameters

Slide 77

OLPC for E-DPDCH & E-DPCCH


Initial, minimum & maximum SIR target
SIRDPCCHInitialEDCH
R99 RAB: Configurable by operator Initial SIR Target for E-DCH
HSUPA RAB RNC; -8.2..-17.3 dB; 0.1 dB;
Provided by AC
Values hardcoded, not configurable by operator SIRDPCCHMinimumEDCH
Minimum SIR Target for E-DCH
Current SIR target RNC; -8.2..-17.3 dB; 0.1 dB; -
Change of SIR target based on difference current BLER SIRDPCCHMaximumEDCH
current BLER target Maximum SIR Target for E-DCH
Current BLER > current BLER target SIR target increase RNC; -8.2..-17.3 dB; 0.1 dB; -

StepUp(E)DCH (1 BLER_Target_(E)DCH) StepSizefo r(E)DCHBLER


Otherwise SIR target decrease
StepDown(E)DCH BLER_Targe t_(E)DCH StepSizefor(E)DCHBLER
Example
current BLER target = 10 % (0.1) StepSizeForDCHBLER
measured BLER = 20 % Step Size for DCH BLER calculation
On DCH SIR target increase = (1- 0.1) * 0.3 dB = 0.27 dB RNC; 0.1..1 dB; 0.1 dB; 0.3 dB
On E-DCH SIR target increase = (1 - 0.1) * 0.03 dB = 0.027 dB
StepSizeForEDCHBLER
measured BLER = 5 % (0.05) Step Size for E-DCH BLER calculation
On DCH SIR target decrease = 0.1 * 0.3 dB = 0.03 dB RNC, 0.01..0.1 dB, 0.01 dB; 0.03 dB
On E-DCH SIR target decrease = 0.1 * 0.03 dB = 0.003 dB
77 13/07/2016 Nokia 2014 - RN3164-16A WCD
77 RN31648EN16GLA0 2016 Nokia

SIRDPCCHInitialEDCH
Initial SIR Target for E-DCH
RNC; -8.2..-17.3 dB; 0.1 dB;
Default values are:
...........................1Rx ant...2 Rx ant..4 Rx ant
SF256.....................6 dB......3 dB......2 dB
SF128.....................6 dB......3 dB......2 dB
SF64.......................6 dB......3 dB......2 dB
SF32.......................6 dB......3 dB......2 dB
SF16.......................6 dB......3 dB......2 dB
SF8.........................6 dB......3 dB......2 dB
SF4.........................6 dB......3 dB......2 dB
2xSF4.....................7 dB......4 dB......3 dB
2xSF2.....................9 dB......6 dB......5 dB
2xSF2+2xSF4........9 dB.......6 dB......5 dB

RN31648EN16GLA0 76
HSUPA RRM & Parameters

Slide 78

OLPC for E-DPDCH & E-DPCCH

From RU40, OLPC DTX is configurable by operator.


The value for DTX period is no longer hardcoded to
200ms, but by default is equal to 0ms
SIR target change requests to be commanded DTX measurement report OLPC Entity selected as active
directly after data is available to be send on E-DCH
bearer
OLPC Entity active
OLPC Entity semi-active

OLPC Entity: OLPC Entity inactive


- active: can send SIR change UP/DOWN requests
- semi-active: can send SIR change UP requests
- inactive: cannot send SIR change requests DTX period

ULFastOLPCDTXthld*
DTX Threshold for uplink faster outer loop.
RNC;0 (200ms),1(0ms); 1(0ms)

*ULFastOLPCDTXthld determines the maximum length of the DTX period. During the DTX period the in-active UL OLPC entity
is not allowed to transmit the SIR target modification commands. In case, the controlled bearer has been in DTX for more than
DTX period value and being activated (data available on the Transport Channel), the UL outer loop PC Entity is allowed to send
SIR Target up modification command to the UL outer loop PC controller. RNFC-FasterOLPCEnabled parameter need to be set
to Enabled.

78 13/07/2016 Nokia 2014 - RN3164-16A WCD


78 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 77
HSUPA RRM & Parameters

Slide 79

OLPC for E-DPDCH & E-DPCCH

Minimum step size for SIR target modification


Minimum step for SIR target modification that PC
Entity can request for UL NRT return channel
Minimum step size = 0.1 ... 0.3 dB (PRFILE or PDDB SIR target [dB]
modifiable value)
minimal step is smaller thus SIR target modification is
more precise
Smaller step posssible
Initial SIR target
t [ms]

FOLPCStepSizSIRTgt*
Faster OLPC step size of SIR target changes.
RNC; 0.1..0.3 dB, step 0.1 dB 0.1dB

*FOLPCStepSizSIRTgt defines the minimum step size of the SIR target modification a PC Entity of UL NRT return channel
can request. The value of this parameter is used, if RNFC-FasterOLPCEnabled parameter is set to Enabled. Otherwise,
RNC internal constant value 0.3 dB is used. If the minimum value of parameter is used, OLPC adjust SIR target more
frequently in smaller steps than if the maximum value is used.

79 13/07/2016 Nokia 2014 - RN3164-16A WCD


79 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 78
HSUPA RRM & Parameters

Slide 80

OLPC for E-DPDCH & E-DPCCH

Minimum step size for SIR target modification


Minimum step for SIR target modification that PC
Entity can request for UL NRT return channel
Minimum step size = 0.1 ... 0.3 dB (PRFILE or PDDB SIR target [dB]
modifiable value)
minimal step is smaller thus SIR target modification is
more precise
If the minimum value of parameter is used, OLPC
Initial SIR target
entity sends SIR modification command more t [ms]
frequently than if the maximum value is used.
SIR target modification interval

FOLPCSIRTgtModInt *
Faster OLPC SIR target modification interval.
RNC; 100..700 ms, step 100 ms 200 ms

*This parameter defines the minimum interval between two SIR target modification commands sent by OLPC entity of UL
NRT return channel over the DMPG-DMPG interface. RNFC-FasterOLPCEnabled parameter need to be set to Enabled.
Otherwise, RNC internal constant value 500 ms is used.

80 13/07/2016 Nokia 2014 - RN3164-16A WCD


80 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 79
HSUPA RRM & Parameters

Slide 81

OLPC for E-DPDCH & E-DPCCH


OLPC Controller Activity reports and BLER
measurements arrive

Inactivity on both DCH and Yes


No update for
E-DCH SIR Target
No
Yes Only upgrades DCH inactive
Inactivity only
on DCH Allowed Consider E-DCH
No BLER only
E-DCH inactive
Only Upgrades Yes Inactivity only
Consider DCH Allowed on E-DCH
BLER only No
Measured BLER EDCH IdealBLER Target EDCH Both active
> OLPC for channel suffering from worst difference
Measured BLER DCH IdealBLER Target DCH
measured BLER ideal BLER target
No Yes

If BLER fails If BLER fails


SIRtarget = SIRtarget + stepupDCH SIRtarget = SIRtarget + stepupEDCH BLER failure:
Else Else measured BLER > current BLER target
SIRtarget = SIRtarget stepdownDCH SIRtarget = SIRtarget stepdownEDCH

DCH OLPC Entity E-DCH OLPC Entity

81 13/07/2016 Nokia 2014 - RN3164-16A WCD


81 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 80
HSUPA RRM & Parameters

Slide 82

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
Dynamic Load Target
Actions in Case of Congestion
DCH & E-DCH Congestion
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
82 13/07/2016 Nokia 2014 - RN3164-16A WCD
82 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 81
HSUPA RRM & Parameters

Slide 83

HSUPA Load Control: Dynamic Load Target

Static & dynamic load target


R99 static load target
For cells without active HSUPA service
Fixed load target PrxTarget (relative to PrxNoise)
Fixed overload threshold PrxOffset (relative to PrxTarget)
HSUPA dynamic load target
for cells with active HSUPA service similar concept as for HSDPA dynamic power allocation
for non-controllable traffic and semi-controllable same fixed load target PrxTarget as in static case
for NRT traffic adjustable load target PrxTargetPS
PrxTargetPSMin (minimum value)
PrxTargetPSMax (maximum value, also initial value)
same PrxOffset value used as in static case to decide about overload actions, but now relative to PrxTargetPS

83 13/07/2016 Nokia 2014 - RN3164-16A WCD


83 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 82
HSUPA RRM & Parameters

Slide 84

HSUPA Load Control: Dynamic Load Target


*PrxMaxOrigTargetBTS
WCEL; 0..30; 0.1; 8 dB
No HSUPA users HSUPA active No HSUPA users PrxMaxOrigTargetBTS= 85%

PrxMaxTargetBTS
0..30; 0.1; 6 dB = 2.0
LmaxCell = 75%
PrxTarget (4 dB)
PrxEDCH
PrxTargetPSMax (e.g. 3 dB)

PrxTargetPS

PrxNRT PrxTargetPSMin (e.g. 2 dB)


PrxTargetPSMin
PrxNC+PrxSC Minimum PS target in HSPA-DCH
interference sharing
NC-Non Controllable traffic WCEL; 0.1..30; 0.1; 4 dB
SC Semi Controllable traffic (Streaming) PrxTargetPSMax
Maximum PS target in HSPA-DCH
interference sharing
WCEL; 0.1..30; 0.1; 4 dB

PrxTargetPSMaxtHSRACH PrxTargetPSMaxtHSRACH - parameter defines the maximum i.e. fixed


0..30; 0.1; 32767 = special value allowed target level for the UL PS NRT DCH packet scheduling
PrxTargetPSMaxtHSRACH= PrxTargetPSMax when the HS-RACH** has been set up in the cell

*RAN1308 Interference Cancellation feature required


84 13/07/2016 Nokia 2014 - RN3164-16A WCD
84 RN31648EN16GLA0 **RAN1913 HSNokia
2016 Cell_FACH feature required

Non-controllable load
Bearer bit rates cannot be changed with the
link adaptation
Semi-controllable load
In the normal load conditions the bit rate is
guaranteed
In the overloaded conditions the resources
could even be released

RN31648EN16GLA0 83
HSUPA RRM & Parameters

Slide 85

HSUPA Load Control: Dynamic Load Target


When the HS-RACH has been set up in the cell, the Prx_target_PS is possible to adjust between the values of the
PrxTargetPSMin and PrxTargetPSMaxtHSRACH management parameters
When the HS-RACH has been set up in the cell, the initial value of the Prx_target_PS is equal to the value of the
PrxTargetPSMaxtHSRACH parameter. The following scenarios are considered:
Initial value is taken into use when the HS-RACH has been set up in the cell.
Initial value is taken into use also when the last NRT UL DCH is released in the cell.
If PrxTargetPSMaxtHSRACH and PrxTargetPSMin parameters are set to an equal value, the RNC does not adjust
the Prx_target_PS, but it is used as the target value in the UL NRT DCH resource allocation.
Prx_Target_PS is used always when the HS-RACH has been set up in the cell (although there is no E-DCH user on
CELL_FACH (HS-RACH user) or CELL_DCH (HSUPA user) states)
When the HS-RACH has been set up in the cell, the Prx_target_PS needs to be equal or lower than the value set by the
PrxTargetPSMaxtHSRACH parameter or than Prx_Target_PS_Target.

PrxMaxOrigTargetBTS
PrxMaxTargetBTS
PrxTarget (4 dB)
PrxTargetPSMax replaced with PrxTargetPSMaxtHSRACH
PrxEDCH
PrxTargetPS
PrxTargetPSMin (e.g. 2 dB)
PrxNRT

PrxNC + PrxSC

85 13/07/2016 Nokia 2014 - RN3164-16A WCD


85 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 84
HSUPA RRM & Parameters

Slide 86

HSUPA Load Control: Dynamic Load Target


Ideal load target
Dynamic load target adjusted if
High DCH load or total load AND
Current load target deviates from ideal load target
Ideal load target PrxTargetIdeal estimated by RNC in dependence on
Non controllable traffic PrxNC
Semi controllable traffic PrxSC (streaming services)
NRT DCH traffic (sum over all weights of R99 services WeightUL_DCH)
NRT E-DCH traffic (sum over all weights of HSUPA services WeightEDCH)

Weight UL_DCH
DCH NRT (PrxMaxTargetBTS - PrxNC - PrxSC)
Weight EDCH Weight UL_DCH

Ideal_PrxT argetPS Min[Max(PrxNC PrxSC DCH NRT , PrxPSMin), PrxPSMax]

Service weights WeightDCHBG Weight of NRT DCH UE BG RAB


can be set individually for each release RNC; 0 .. 100; 1; 15
R99 WeightDCHTHP1/2/3 Weight of NRT DCH UE THP1/2/3 RAB
HSPA RNC; 0 .. 100; 1; 90/65/40
can be set individually for each traffic class WeightHSPABG Weight of HSPA UE BG RAB
Interactive THP1, THP2, THP3
RNC; 1 .. 100; 1; 25
Background
in case of multi-RAB the average weight of the WeightHSPATHP1/2/3 Weight of HSPA UE THP1/2/3 RAB
individual RABs is taken for that user RNC; 0 .. 100; 1; 100/75/50
86 13/07/2016 Nokia 2014 - RN3164-16A WCD
86 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 85
HSUPA RRM & Parameters

Slide 87

HSUPA Load Control: Load Target Adjustment

Required information
Total load PrxTotal measured by Node B
Non E-DCH load PrxNonEDCH calculated by RNC
Both averaged according PSAveragingWindowSize (same parameter as for R99)
Need for adjustment checked periodically according PrxTargetPSAdjustPeriod
If adjustment needed
Increase by PrxTargetPSStepUp dB in case of DCH congestion
Decrease by PrxTargetPSStepDown dB in case of E-DCH congestion
PSAveragingWindowSize
Load measurement averaging window size for packet scheduling
WBTS; 1..20; 1; 4 scheduling periods
PrxTargetPSAdjustPeriod
PS target tune period in HSPA-DCH interference sharing
WBTS; 1 .. 255; 1; 5 RRI periods
PrxTargetPSStepUp
PS target step up in HSPA-DCH interference sharing
WCEL; 0.1 .. 1 dB; 0.1 dB; 0.5 dB
PrxTargetPSStepDown
PS target setup down in HSPA-DCH interference sharing
WCEL; 0.1 .. 1 dB; 0.1 dB; 0.5 dB

87 13/07/2016 Nokia 2014 - RN3164-16A WCD


87 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 86
HSUPA RRM & Parameters

Slide 88

HSUPA Load Control: Actions in Case of Congestion

DCH congestion only


Increase PrxTargetPS by PrxTargetPSStepUp, if currently < ideal
load target (but not above PrxTargetPSMax or PrxTargetIdeal)

E-DCH congestion only


Decrease PrxTargetPS by PrxTargetPSStepDown, if currently > ideal
load target (but not below PrxTargetPSMin or PrxTargetIdeal)

Both DCH & E-DCH congestion


Increase PrxTargetPS, if currently < ideal load target
Decrease PrxTargetPS, if currently > ideal load target

88 13/07/2016 Nokia 2014 - RN3164-16A WCD


88 RN31648EN16GLA0 2016 Nokia

HSUPa RRM p. 160

RN31648EN16GLA0 87
HSUPA RRM & Parameters

Slide 89

HSUPA Load Control: DCH Congestion


PrxMaxTargetBTS
0..30; 0.1; 6 dB

PrxTargetPS (e.g. 2.5 dB)

PrxTargetPSStepUp
PrxTotal WCEL; 0.1 .. 1; 0.1; 0.5 dB
PrxTargetPSStepDown
PrxNonEDCH WCEL; 0.1 .. 1; 0.1; 0.5 dB

Requirements to indicate DCH congestion

PrxNonEDCH PrxTargetPS - max (PrxTargetPSStepUp, PrxTargetPSStepDown)


Calculated by RNC

LoadNonEDCH min (Load (PrxTargetPS), Load (PrxLoadMarginEDCH))



Calculated by RNC Load factor corresponding Load factor corresponding
to current load target to PrxLoadMarginEDCH

PSAveragingWindowSize PrxLoadMarginEDCH
Load measurement averaging window size for PS 0..30; 0.1; 2 dB 1.585
WBTS; 1..20; 1; 4 scheduling periods LminCell 37%
PrxTargetPSAdjustPeriod
PS target tune period in HSPA-DCH interference sharing
WBTS; 1 .. 255; 1; 5 RRI periods

89 13/07/2016 Nokia 2014 - RN3164-16A WCD


89 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 88
HSUPA RRM & Parameters

Slide 90

E HSUPA Load Control: E-DCH Congestion


PrxMaxOrigTargetBTS
0..30; 0.1; 8 dB
PrxMaxTargetBTS
0..30; 0.1; 6 dB
Max (PrxTargetPSStepUp,
PrxTargetPSStepDown)
PrxTargetPS (e.g. 2.5 dB)

PrxTargetPSStepUp
PrxTotal WCEL; 0.1 .. 1; 0.1; 0.5 dB
PrxTargetPSStepDown
WCEL; 0.1 .. 1; 0.1; 0.5 dB

Requirements to indicate E-DCH congestion

PrxTotal PrxMaxTargetBTS - max (PrxTargetPSStepUp, PrxTargetPSStepDown)


Reported by Node B

LoadNonEDCH LoadEDCH Load (PrxLoadMarginEDCH)


Calculated by RNC Reported by Node B Load factor corresponding
to PrxLoadMarginEDCH
PrxLoadMarginEDCH
0..30; 0.1; 2 dB 1.585
LminCell 37%
90 13/07/2016 Nokia 2014 - RN3164-16A WCD
90 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 89
HSUPA RRM & Parameters

Slide 91

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
Soft/Softer HO
Inter-Frequency & Inter-System HHO
HSUPA Layering
HSUPA Compressed Mode for LTE and Inter-frequency Handover
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix
91 13/07/2016 Nokia 2014 - RN3164-16A WCD
91 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 90
HSUPA RRM & Parameters

Slide 92

Soft & Softer HO (1/2)

Types of mobility
Intra-frequency mobility allows
Intra-BTS intra-RNC Softer handover (between cells belonging to the same LCG)
Intra-BTS intra-RNC Soft handover (intra-frequency HO between cells belonging to different LCGs)
Inter-BTS Intra-RNC Soft handover
Inter-RNC Soft handover (If HSPA over Iur feature is enabled)

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 HSPAFmcsIdentifier
FMCS is used for intra-frequency measurement control HSPA FMCS identifier for Single or Multi PS RAB
WCEL; 1..100; 1; -
HSDPA serving cell change not affected by HSUPA SHO
RTWithHSPAFmcsIdentifier
HSPA FMCS identifier for AMR multi-service
WCEL; 1..100; 1; -

92 13/07/2016 Nokia 2014 - RN3164-16A WCD


92 RN31648EN16GLA0 2016 Nokia

HSUPA RRM 1.2.2 Hsupa handovers

RN31648EN16GLA0 91
HSUPA RRM & Parameters

Slide 93

Soft & Softer HO (2/2)


E-DCH & DCH Active Set (AS)
E-DCH AS: subset of DCH AS
E-DCH active set is built when the E-DCH channel type is selected. All cells in the DCH active set are added to the E-DCH
active set if possible
Cells can be left out from E-DCH AS but included within DCH AS due to
HSUPA not enabled for DCH active cell
A cell is under DRNC and HSPA over Iur is disabled
Max. 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
Some other reasons (for example, signaling problems)
Softer HO E-DCH & DCH AS have to be identical
Soft HO E-DCH & DCH AS can be different
Cell shall be added to E-DCH AS 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
E-DCH in comparison to best active cell
In case of Softer HO for DCH no AS update either (RRC
DCH connection release due to DCH SHO failure possible as usual)

93 13/07/2016 Nokia 2014 - RN3164-16A WCD


93 RN31648EN16GLA0 2016 Nokia

WCDMA RAM RRM p. 172

RN31648EN16GLA0 92
HSUPA RRM & Parameters

Slide 94

Inter-Frequency & 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
not yet supported by HSUPA
same FMCG parameter set used as for HSDPA
same HOPG parameter set used as for R99

94 13/07/2016 Nokia 2014 - RN3164-16A WCD


94 RN31648EN16GLA0 2016 Nokia

WCDMA RAN RRM HSUPA 14.4 Hard handovers p. 185

Inter-Frequency HHO
not supported for HSUPA until RU30
CTS E-DCH DCH required
same FMCI parameter set used as for HSDPA
same HOPI parameter set used as for R99

RN31648EN16GLA0 93
HSUPA RRM & Parameters

Slide 95

HSUPA Layering (1/3)

HSUPA layering features


Directed RRC Connection Establishment: Re-direction from RRC Idle mode
HSPA Layering in Common Channels: Layering from CELL_FACH

Directed RRC Connection HSPA Layering in


Establishment Common Channels
RRC Connected RRC Connected
Mode Mode
URA_PCH CELL_PCH HSPA Layer URA_PCH CELL_PCH

CELL_DCH CELL_FACH CELL_DCH CELL_FACH

DCH Layer
Camping on a UMTS cell Camping on a UMTS cell

Idle Mode Idle Mode

95 13/07/2016 Nokia 2014 - RN3164-16A WCD


95 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 94
HSUPA RRM & Parameters

Slide 96

HSUPA Layering (2/3): HSUPA directed RRC connection setup

Following parameters must be enabled: Further Requirements:


DirectedRRCEnabled
HSUPA capability of UE taken into account only, if
Directed RRC connection setup enabled
enhanced layering enabled with
WCEL; 0 or 1; 0 = disabled; 1 = enabled DirectedRRCForHSDPALayerEnhanc
To be redirected to HSUPA layer, UE must indicate
DirectedRRCForHSDPALayerEnabled
Directed RRC connection setup for HSDPA layer
with RRC connection request:
WCEL; 0 or 1; 0 = disabled; 1 = enabled - R6 or newer & HSDPA + HSUPA capable
at least 1 cell must be available fulfilling:
DirectedRRCForHSDPALayerEnhanc
Number of HS-DSCH allocations has not reached max.
DRRC connection setup for HSDPA layer enhancements
allowed value
RNC; 0 or 1; 0 = disabled; 1 = enabled HSUPA is enabled
DRRCForHSDPALayerServices only single HSUPA capable cell available
Services for DRRC connection setup for HSDPA layer* selected without checking max. allowed number of HSUPA
RNC; 0..32767; 1; 204 users
several HSUPA capable cells available
Cells having not reached max. allowed number of HSUPA
users are prioritised

Parameter dependencies: same as discussed under HSDPA


Feature details: same as discussed under HSDPA

96 13/07/2016 Nokia 2014 - RN3164-16A WCD


96 RN31648EN16GLA0 2016 Nokia

* 16 bit parameter to enable / disable enhanced layering for each traffic class & different types of signaling
procedures individually; by default enabled for interactive / background service & inter-RAT cell re-selection / cell
change order

RN31648EN16GLA0 95
HSUPA RRM & Parameters

Slide 97

HSUPA Layering (3/3): HSPA Layering in Common Channels

From Cell_FACH
Must be enabled with HSDPALayeringCommonChEnabled
HSDPALayeringCommonChEnabled
Redirection Cell_FACH to Cell_DCH to HSPA layer triggered if HSDPA layering for UEs in common channels enabled
UE is HSPA capable WCEL; 0 or 1; 0 = disabled; 1 = enabled
HSDPA not enabled for current cell
HSDPA enabled for at least one cell in same sector ServicesToHSDPALayer
UE is requesting service for which state transition is enabled Services to HSDPA layer in state transition
with ServicesToHSDPALayer RNC; any service, NRT RAB

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

97 13/07/2016 Nokia 2014 - RN3164-16A WCD


97 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 96
HSUPA RRM & Parameters

Slide 98

HSUPA Compressed Mode for LTE and Inter-frequency Handover

This feature introduces compressed mode measurements with HSPA active (HSUPA/HSDPA inter-
system LTE and Inter-frequency (IF) . (with no UL channel type switching to DCH)

HSUPA compressed mode measurement for inter-frequency handover and HSUPA/HSDPA inter-
frequency handover are part of this feature.

Instead of performing channel type switching to DCH/HS-DSCH or


DCH/DCH, Compress Mode (CM) is started immediately when HSPA is
configured .

Both 2ms and 10ms TTI HSUPA are supported

Used by:
Measurement based LTE layering
Smart LTE Handover
CM measurements
Benefits:
Faster Handover
Better User Experience
BTS UE

98 13/07/2016 Nokia 2014 - RN3164-16A WCD


98 RN31648EN16GLA0 2016 Nokia

HSUPA compressed mode configuration for inter-frequency measurement is a single


frame method with a 7 (or less) slot transmission gap pattern (TGP).
HSUPA CM configuration for LTE measurement is a double frame method with 7 (or
more) slots TGP.
The target cell can be an intra-RNC cell or inter-RNC cell
HSUPA IFHO can be caused by existing IFHO triggers:
Quality
Coverage
HSPA Capability Handover
Immediate IMSI based handover

RN31648EN16GLA0 97
HSUPA RRM & Parameters

Slide 99

HSUPA Compressed Mode for LTE and Inter-frequency Handover


New Inter-frequency scenarios
The RAN1668 HSUPA compressed mode adds the following new IFHO scenarios:

bearers configuration @ CM activation bearers configuration after IFHO

HSDPA DL/HSUPA UL
SRB on DCH or EDCH
HSDPA DL/HSUPA UL HSDPA DL/DCH UL
SRB on DCH or EDCH* SRB on DCH
NRT bearers, 2ms or 10ms TTI

DCH DL/DCH UL
SRB on DCH

* If Fractional-DPCH feature used and SRB DL/UL mapped to HS-DSCH/EDCH respectively

99 13/07/2016 Nokia 2014 - RN3164-16A WCD


99 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 98
HSUPA RRM & Parameters

Slide 100

HSUPA Compressed Mode for LTE and Inter-frequency Handover


connections types and features coexistance

The compressed mode can be started for HSPA connections (HSUPA configured in the UL*) with NRT
RABs. For RT or Streaming HSPA services the HSUPA must be reconfigured to DCH UL prior to CM
activation (CSoHSPA to AMR)

NRT HSPA with Streaming


NRT RAB CSoHSPA
AMR HSPA


CM activation with HSUPA
UL configured

The HSUPA compressed mode can be configured for cells or UEs using Frequency Domain
Equalizer or Parallel Interferance Cancellation or HSUPA 16QAM features.
UEs using DC HSUPA must be reconfigured to single cell HSUPA, while MIMO or DC HSDPA must be
deactivated prior to CM activation.

HSUPA
FDE PIC DC HSUPA DC HSDPA MIMO
16QAM


CM activation with
HSUPA UL configured

* UEs with any HSUPA category, including UEs with FDE or PIC or UL 16QAM activated
100 13/07/2016 Nokia 2014 - RN3164-16A WCD
100 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 99
HSUPA RRM & Parameters

Slide 101

HSUPA Compressed Mode for LTE and Inter-frequency Handover


HSUPA Compressed Mode exclussions

HSUPA compressed mode RAN1668 enabled in SRNC and DRNC BTSs


is supported in SRNC
cells
At RNC border the HSUPA Compressed Mode
DCH
may not be activated in some scenarios.
E-DCH
When any active set cell is located in drift RNC
upon receiving IF or IS HO trigger, the UL is
reconfigured from HSUPA to DCH prior to CM
activation (UE with HSPA service). The DL is
reconfigured to DCH as well if serving cell is
located in DRNC or in SRNC which does not
support HSDPA CM.

The HSUPA CM activation is not possible in


DRNC. With special settings the Nokia DRNC
does not reject RNSAP messages* with non-
active CM parameters included, sent by other
vendor SRNC.
RNS border active set cells Serving cell

101 13/07/2016 Nokia 2014 - RN3164-16A WCD


101 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 100
HSUPA RRM & Parameters

Slide 102

HSUPA Compressed Mode for LTE and Inter-frequency Handover


HSUPA Compressed Mode exclusions
RAN1668 enabled in RNC
Active set cells BTS:s must be HSUPA CM enabled to BTS1, BTS2, BTS3

enabled for HSPA CM to start


HSUPA Compressed Mode
DCH

E-DCH
HSUPA CM is enabled on BTS level.

All cells in EDCH active set (respective BTS:s)


must be enabled for HSPA CM to start HSUPA
CM.

Each time the RNC is about to start HSUPA


CM for given UE, the activation conditions are
verified. If all are passed the HSUPA CM is
enabled. The cross-check* is repeated on next
CM activation.

HSUPA CM disabled

* except the license key, which is verified once per call


HSUPA CM enabled active set cells Serving cell

102 13/07/2016 Nokia 2014 - RN3164-16A WCD


102 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 101
HSUPA RRM & Parameters

Slide 103

HSUPA Compressed Mode for LTE and Inter-frequency Handover


mechanisms to create measurement gaps

Compressed Mode allow UE with single receiver, connected to one carrier, to measure
another carrier in the same or other RAT.
The receiver must be tuned to the measured DL carrier, which prevents reception on
currently used frequency, in the same time (transmission gaps).
These gaps are created & controlled by the network in UL/DL, using one of available
methods: spreading factor halving (SF/2) or higher layer scheduling (HLS)
In SF/2 the time spend on IF/IS measurements is compensated by doubling the channel
rate in slots directly preceding/following measurement gaps (same data are sent in shorter
time in compressed slots using lower spreading factor / SF halving). Lower SF reduce
processing gain & rise Eb/No requirements, both resulting in raised transmission power* in
compressed slots.
~3 3.5dB

original SF SF/2 SF/2 original SF original SF SF/2 SF/2 original SF original SF


normal radio frame compressed radio normal radio frame normal radio frame compressed radio normal radio frame normal radio frame
frame frame
* For example Eb/No requirement for AMR12.2DL is increased by 0.5dB and processing gain by 3dB, which boost TxPwr by 3.5dB in compress slots

103 13/07/2016 Nokia 2014 - RN3164-16A WCD


103 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 102
HSUPA RRM & Parameters

Slide 104

HSUPA Compressed Mode for LTE and Inter-frequency Handover


mechanisms to create measurement gaps

SF/2 method is not possible for SF=4. In the DL the compressed frame may use the same
code tree or the one under secondary scrambling code (cons: lower codes orthogonality,
increased DL interferences). SF halving is used for: AMR, CS data, standalone DCH SRB,
Multi-RABs (most AMR + NRT DCH or CS data + NRT DCH, AMR + CS data), HSDPA UL
DCH1, A-DPCH2
In HLS method measurement gap is produced by the reducing user data rate (higher layers
restrict the use of higher rate TFCs in compressed slots). The maximum number of bits
provided to physical layer is known and measurement gap can be generated. HLS can not
be used with TrCh of fixed starting position in radio frame (DL AMR)

normal radio frame compressed radio normal radio frame normal radio frame compressed radio normal radio frame normal radio frame
frame frame

HLS is used for: NRT DCH (and related Multi-RABs), AMR+NRT384/256, HSDPA UL DCH3
The maximum length of a gap within one frame is 7 slots4 (Nokia use maximum length).
The compressed mode is not needed for DL F-DPCH (if configured)
1 3
If sum of used UL DCHs <=128kbp If sum of used UL DCHs > 128kbps
2 4
Associated DPCH (DL DCH SRB for HSPDA) If a gap is span over two frames the length can have 7 14 slots (Nokia use 10)
104 13/07/2016 Nokia 2014 - RN3164-16A WCD
104 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 103
HSUPA RRM & Parameters

Slide 105

HSUPA Compressed Mode for LTE and Inter-frequency Handover


mechanisms to create measurement gaps

The measurement gap can be entirely within one radio frame: single frame gap or span over
consecutive two frames: double frame gap.
A) Single frame gap: variable number of normal frames

normal radio frame compressed radio normal radio frame normal radio frame compressed radio normal radio frame normal radio frame
frame frame

variable number of normal frames


B) Double frame gap:

normal radio frame compressed radio compressed radio normal radio frame compressed radio compressed radio normal radio frame
frame frame frame frame

The single frame gaps are used for inter-frequency and GSM inter-system measurements.
(SF/2 or HLS methods are possible)
The double frame gaps are used for inter-frequency, GSM or LTE inter-system
measurements (HLS method is used in case of DCH/DCH or SF/2 in case of HSPA)
105 13/07/2016 Nokia 2014 - RN3164-16A WCD
105 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 104
HSUPA RRM & Parameters

Slide 106

HSUPA Compressed Mode for LTE and Inter-frequency Handover


3GPP parameters

In general the CM consists of TGSN


TGPL1

transmission gaps with predefined 123 4 TGD


starting slot, duration & number of TGL1 TGL2

normal slots, which all make up a


compressed radio normal radio frames compressed radio normal radio frames
transmission gap pattern (TGP). frames frames

One TGP is used for each CM


purpose, which can be IF, GSM
CFNTGCFN CFNTGCFN+1 CFNTGCFN+2 CFNTGCFN+TGPRC
and LTE measurements. Transmission Transmission Transmission Transmission Transmission
gap pattern1 gap pattern1 gap pattern1 gap pattern1 gap pattern1

TGP is repeated predefined #1 #2 #3 #4 TGPRC

number of times (TGPRC) or until


RNC stops CM (TGPRC=infinity / TGFCN Transmission Gap Connection Frame Number (CFN) of TGP #1
TGPL Transmission Gap Pattern Length (TGP duration in number of frames)
Nokia). TGSN Transmission Gap Startng Slot Number (first slot of TG1)
TGPRC Transmission Gap Pattern Sequence
There are 2 transmission gaps TGD Transmission Gap Distance (TG1 & TG2 distance in number of slots)
TGL1 Transmission Gap Length 1 (TG1 duration in number of slots)
(TG) defined in TGP, however TGL2 Transmission Gap Length 2 (TG2 duration in number of slots)
TPG2 is not used in Nokia
Note: If TGD is set to undefined then TGL2 is ignored (used by Nokia)
UTRAN. In Nokia UTRAN TGL1=7 (single frame gap) or 10 (double frame gap)

106 13/07/2016 Nokia 2014 - RN3164-16A WCD


106 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 105
HSUPA RRM & Parameters

Slide 107

HSUPA Compressed Mode for LTE and Inter-frequency Handover


HSUPA Compressed Mode

With HSUPA CM the DPCH channels, if exist in DL or UL (UL DPDCH SRB channel or A-
DPCH SRB channel), are compressed using spreading factor halving method SF/2
In case F-DPCH feature is used, SRBs are mapped to HS-DSCH/E-DCH and none of
channels are compressed but measurement gap parameters are signaled to BTS and UE
indicating SF/2 compressing method.
Transmissions in all non-DCH channels are not compressed but instead transmission is
suspended in TTIs overlaping* with scheduled transmission gap.
The CM gap length is always 7 slots for HSUPA IF measurments and 10 for (HSUPA) LTE
measurements.
The CM is not used if DC-HSUPA is configured. It must be first reconfigured to HSUPA.

107 13/07/2016 Nokia 2014 - RN3164-16A WCD


107 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 106
HSUPA RRM & Parameters

Slide 108

HSUPA Compressed Mode for LTE and Inter-frequency Handover


Activation

1 Activate licenses: 2 Enable RNC/BTS 3 Verify cells limts for


on/off parameters: #CM HSPA UEs:
RAN1276 license (HSDPA IFHO) Activate HSUPA CM in every Check that non-zero limit for
RAN1668 license (HSUPA CM): BTS in planned area: number of HSAPA CM UEs is set in
IPA-RNC, MML command: WBTS:BTSSupportForHSPACM = every HSPA cell in planned area:
HSPA CM Supported (2) WCEL:MaxNumberUEHSPACmHO >0
ZW7M: FEA=4783:ON; (if RAN1668 is to be used with critical
Enable CM in RNC (if not done): coverage/quality IF handovers)
RNCF:CMmasterSwitch =Used (0)
WCEL:MaxNumberUEHSPACmNCHO >0
Enable HSDPA mobility in RNC: (if RAN1668 is to be used with other IF
handovers Or LTE handovers/layering)
RNCF:HSDPAMobility =Enabled (1)

E-DCH RNFC:HSDPAMobility=Disabled
DCH a. CTS HSUPA to E-DCH
RNFC:CMmasterSwit CM trigger DCH
DCH
ch=Used CM trigger
b. start HSDPA
CM

RNFC:CMmasterSwitch= a. CTS HSUPA


Not used to DCH
HSDPAMobility=enabled
active set cells b. Start DCH CM
108 13/07/2016 Nokia 2014 - RN3164-16A WCD
108 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 107
HSUPA RRM & Parameters

Slide 109

HSUPA Compressed Mode for LTE and Inter-frequency Handover


Reused and extended parameters

RNFC: CMmasterSwitch WBTS: BTSSupportForHSPACM New


value
Enable/Disable Compressed Mode in RNC: Enable HSUPA/HSDPA/R99 CM in BTS:
BTSSupportForHSPACM =HSDPA CM supported
CMmasterSwitch=Used E-DCH (all active set cells)
Active
Set

CM trigger start HSUPA CM


CMmasterSwitch=Not used

BTSSupportForHSPACM = HDSPA CM supported (or Only DCH CM supported)


(any active set cell) DCH
E-DCH
RNFC: HSDPAMobility a. CTS HSUPA to DCH
Enable/Disable HSDPA Mobility in RNC: CM trigger
b. start CM

E-DCH
HSDPAMobility =Enabled
Active
Set

CM trigger start HSUPA CM

RNHSPA: GapPositionSingleFrame
First slot of measurement gap (Inter-freq / GSM HO):
HSDPAMobility =Disabled E-DCH DCH
a. CTS HSUPA to DCH TGSN= GapPositionSingleFrame
b. start CM
CM trigger TGL1
CM IFHO

compressed normal radio frame(s)


radio frame

109 13/07/2016 Nokia 2014 - RN3164-16A WCD


109 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 108
HSUPA RRM & Parameters

Slide 110

HSUPA Compressed Mode for LTE and Inter-frequency Handover


New and reused parameters

RNHSPA:TGPLHSPAInterFreq WCEL:MaxNumberUEHSPACm(NC)HO
Transmission gap pattern length (Inter-freq HO): Maximum number of HSDPA/HSPA CM Ues in the cell
TGPLHSPAInterFreq CrHO: #(HSDPA+HSPA) CM UEs <= MaxNumberUEHSPACmHO (+MaxNumberUEHSPACmNCHO)

TGL1
CM IFHO

Non-CM UE CM UE (DCH, HSDPA, HSPA)


compressed radio frame normal radio frame(s)
CrHO: #(DCH+HSDPA+HSPA) CM UEs < = WCEL:MaxNumberUECmHO (+WCEL:MaxNumberUECmSLHO)
NCHO: #(DCH+HSDPA+HSPA) CM UEs < = WCEL:MaxNumberUECmHO
CrHO=Critical HO (coverage or quality reasons)
NCHO=noncritical HO (other: capability/load/service based etc)

WCEL:AltScramblingCodeCM
Enable/Disable alternative scrambling code usage (SF/2 CM)
RNHSPA:TGPLForLTEMeas
AlrScramblingCodeCM = Allowed AlrScramblingCodeCM = Denied Transmission gap pattern length (LTE HO / Layering):
1 8191
(16384) TGPLForLTEMeas
or TGSN=10
SF/2 SF/2 original SF
compressed normal radio frame TGL1
radio frame CM LTE
spreading code tree spreading code tree Spreading code tree
under alternative scr under primary scr under primary scr code
code code compressed radio frame compressed radio frame normal radio frame(s)

110 13/07/2016 Nokia 2014 - RN3164-16A WCD


110 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 109
HSUPA RRM & Parameters

Slide 111

HSUPA RRM: Contents

HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
E-DCH Establishment
Channel Type Switching
E-DCH Release
HSUPA Improvements
Appendix
111 13/07/2016 Nokia 2014 - RN3164-16A WCD
111 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 110
HSUPA RRM & Parameters

Slide 112

E-DCH Establishment (1/4)

Signaling (establishment from RRC_Idle)


Same high level procedures as for NRT DCH
After PDP context activation RNC starts by allocating DCH 0/0 kbps connection
Selection between DCH and E-DCH completed when RNC receives UL capacity request
HSUPA can be allocated from CELL_FACH or CELL_PCH as well

UE Node B RNC SGSN

RRC Establishment

GPRS Attach

PDP Context Activation 0/0 kbps DCH


allocated
Measurement Report 4a
Uplink capacity request
RNC completes channel
type selection procedure

112 13/07/2016 Nokia 2014 - RN3164-16A WCD


112 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 111
HSUPA RRM & Parameters

Slide 113

E-DCH Establishment (2/4)

Direct Resource Allocation (DRA) for HSPA


HSDPA or HSPA transport channels are directly allocated in the RAB setup phase from
Cell_DCH or from Cell_FACH state
DRA for the new entering PS RABs of interactive and background traffic classes
Possible to define whether the DRA is to be used in CELL_DCH or CEL_FACH or both
UE Node B RNC SGSN

RRC Establishment

GPRS Attach

PDP Context Activation Radio Bearer setup


to HSPA (direct)
User Plane established
Measurement Control on HSPA
Uplink capacity request if
needed

RABDRAEnabled
Usage of the direct resource allocation for PS NRT HSPA
RNFC; Disabled (0), Enabled in Cell_FACH (1), Enabled in Cell_DCH (2), Enabled in Cell_FACH and Cell_DCH (3)

Further Requirements:
In case of DRA to HSPA channels (HS-DSCH & E-DCH), F-DPCH need to be allocated
113 13/07/2016 Nokia 2014 - RN3164-16A WCD
113 RN31648EN16GLA0 2016 Nokia

Basic call FD 2.3.12.3

RN31648EN16GLA0 112
HSUPA RRM & Parameters

Slide 114

E-DCH Establishment (3/4)


Direct Resource Allocation (DRA) for HSPA not used
Channel type selection
started
1
Uplink NRT RB mapped to Yes HS-DSCH possible to select No
DCH > 0 kbps in the downlink HC
HSPA serving cell
No Yes selected + Preliminary E-
UE capability No Preliminary E-DCH active No 3 DCH active set selected
supports E-DCH set is acceptable
Yes 2 Yes
Minimum E-DCH active set
UE specific selected
RAB combination No HS-DSCH possible to select No 4
PS
allows use of E-DCH in the downlink
Yes Cell specific PS (can be more than 1)
Yes
Traffic class and THP No Number of E-DCH allocations No
allowed on E-DCH is below the maximum
Yes Yes
HSDPA mobility enabled No Final E-DCH active set is No UE specific PS
and HS-DSCH available acceptable
and no IFHO/ISHO Yes
measurements E-DCH
DCH DCH
IFHO/ISHO measurements Yes selected
selected selected
prevent HSUPA

1) Channel type switching running


2) RAB combinations allowed for HSUPA
up to 3 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 AS = all HSUPA enabled active cells with sufficient quality

114 13/07/2016 Nokia 2014 - RN3164-16A WCD


114 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 113
HSUPA RRM & Parameters

Slide 115

E-DCH Establishment (4/4)


Minimum E-DCH Active Set: EDCHAddEcNoOffset
allow E-DCH usage EcNo offset
Exclude all active cells for which HSUPA is disabled FMCS; -10 .. 6; 0.5; 0 dB
Exclude all active cells which satisfy following equation
EC/I0 of E-DCH cell < EC/I0 of serving E-DCH cell + EDCHAddEcNoOffset
DCH active set step 1 Preliminary E-DCH active set step 2
HSUPA HSUPA
HSUPA HSUPA
enabled enabled enabled
enabled

HSUPA
disabled

Minimum E-DCH active set step 3


Multi-RAB
CPICH Ec/Io CPICH Ec/Io
= -5 dB = -7 dB HspaMultiNrtRabSupport
HSPA multi NRT RAB Support; up to 3 NRT RAB
WCEL; 0 or 1; 0 = disabled; 1 = enabled
AMRwithEDCH
Usage of AMR + E-DCH*
WCEL; 0 or 1; 0 = disabled; 1 = enabled
* AMR codec selection not affected by HSUPA

115 13/07/2016 Nokia 2014 - RN3164-16A WCD


115 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 114
HSUPA RRM & Parameters

Slide 116

Channel Type Switching CTS


Overview: Trigger causing Channel Type Switching
DCH E-DCH or E-DCH DCH
HS-DSCH related trigger:
1) DCH HS-DSCH channel type switching
2) HS-DSCH serving cell change
DCH E-DCH
Quality related trigger:
3) EC/I0 of serving HSDPA cell becomes acceptable for E-DCH
4) EC/I0 of serving HSDPA cell becomes unacceptable for E-DCH
EC/I0 is reported periodically like for HSDPA serving cell change

Other
5) Guard timer started after transition E-DCH DCH expires
6) Re-try timer expires; started after unsuccessful attempts to get E-DCH
(due to too high number of E-DCH users)
7) Node B initiated transition E-DCH DCH
8) PS streaming establishment
9) E-DCH active set update
10) CS voice RAB establishment (determines whether it is possible to switch to the full HSPA configuration)

116 13/07/2016 Nokia 2014 - RN3164-16A WCD


116 RN31648EN16GLA0 2016 Nokia

WCDMA RAN HSUPA 1.4.3.2 p. 176

RN31648EN16GLA0 115
HSUPA RRM & Parameters

Slide 117

Channel Type Switching CTS

1) Trigger DCH HS-DSCH switch


Attempt for DCH HS-DSCH
If succeeds then E-DCH may also be allocated (DCH/DCH -> E-DCH/HS-DSCH)
If fails then E-DCH cannot be allocated (DCH/DCH -> DCH/DCH)
HS-DSCH DCH
E-DCH->DCH switch also triggered (E-DCH/HS-DSCH -> DCH/DCH)
2) Trigger HS-DSCH Serving Cell change
DCH allocated in the UL RNC checks if E-DCH can be selected
E-DCH allocated in the UL RNC checks if E-DCH can be maintained
For both cases
Serving cell must support E-DCH
Non-serving active cells which cannot be added to E-DCH AS must not have too high CPICH Ec/Io (see minimum
AS & quality related trigger)

Non-E-DCH E-DCH area


area

Non-E-DCH
area

117 13/07/2016 Nokia 2014 - RN3164-16A WCD


117 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 116
HSUPA RRM & Parameters

Slide 118

Channel Type Switching CTS


CPICH Ec/Io DCH to E-DCH
3) Trigger EC/I0 of Serving HSDPA cell becomes
switch
acceptable for E-DCH
Serving HS-DSCH cell
Triggers DCH E-DCH switch E-DCH capable cell
Serving cell changes to acceptable if AS cell which
cannot be added to E-DCH AS becomes weak or is EDCHAddEcNoOffset
removed FMCS; -10..6; 0.5; 0 dB
Weak: defined relative to Serving HS-DSCH cell Non E-DCH
Threshold defined by EDCHAddEcNoOffset capable cell
no time to trigger
Time

4) Trigger EC/I0 of Serving HSDPA cell becomes CPICH Ec/Io


un-acceptable for E-DCH E-DCH to DCH
switch Non E-DCH
Triggers E-DCH DCH switch capable cell
Serving cell changes to unacceptable if AS cell
which is not E-DCH active becomes strong EDCHRemEcNoOffset
defined relative to Serving HS-DSCH cell FMCS; -10 .. 6; 0.5 dB; 2 dB
Threshold defined by EDCHRemEcNoOffset
no time to trigger Serving HS-DSCH cell
E-DCH capable cell
Time

118 13/07/2016 Nokia 2014 - RN3164-16A WCD


118 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 117
HSUPA RRM & Parameters

Slide 119

Channel Type Switching CTS EDCHCTSwitchGuardTimer


E-DCH CTS guard timer
RNC; 0..20 s; 0.5 s; 2 s
5) Trigger CTS guard timer expires
after CTS E-DCH DCH guard timer E-DCH DCH switch (guard Attempt for DCH E-DCH
EDCHCTSwitchGuardTimer is started timer started) switch allowed
after expiration of the timer switch back to E-
DCH allowed EDCHCTSwitchGuardTimer
Time

6) Trigger CTS re-try timer expires


If E-DCH cannot be allocated, because max. # of HSUPA users
users is reached, retry timer is started
Timer can be applied for initial channel type selection or CTS
after timer expiration next Capacity Request for E-DCH allowed
Re-try Timer = DCH E-DCH switch failed Consecutive DCH E-DCH
min (10 s, number of failures * 2 s) (re-try timer started) switch re-attempts
Re-try Timer

7) Trigger Node B initiated switch E-DCH DCH Time


Node B may need to release E-DCH resources to allocate HW resources more effectively
Node B sends RL failure message with cause UL radio resources not available to RNC
RNC shall change channel type from E-DCH to DCH
CTS retry timer applied to allow connection to return to E-DCH

119 13/07/2016 Nokia 2014 - RN3164-16A WCD


119 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 118
HSUPA RRM & Parameters

Slide 120

Channel Type Switching CTS


8) PS streaming RB establishment
Upon the establishment of the PS streaming RB, the channel type is selected
if HSPA streaming is not activated, or the use of HSUPA is not allowed, the NRT RB channel type is switched from E-DCH
to DCH
if there are no resources available, the channel type of the NRT RB is not switched to DCH, but E-DCH usage is continued.
The RT-over-NRT procedure is attempted for the streaming real-time bearer, and afterwards a DCH with 0/0 kbps is allocated
and a new capacity request is awaited.

9) E-DCH active set update


When DCH is allocated for streaming and NRT services and a soft handover branch is deleted from the active set, the RNC
checks whether all cells support E-DCH.
The RNC triggers channel type switching from DCH to E-DCH if all of the following conditions are true:
All cells support E-DCH.
The HSPAQoSEnabled parameter is set to ON for the serving HS-DSCH cell.

HSPAQoSEnabled
HSPA QoS enabled
WCEL; QoS prioritization is not in use for HS transport (0), QoS prioritization is used for HS NRT channels (1), HSPA streaming is in
use (2), HSPA CS voice is in use (3), HSPA streaming and CS voice are in use (4), QoS prioritization is used for HS NRT channels (1),
HSPA streaming is in use (2), HSPA CS voice is in use (3), HSPA streaming and CS voice are in use (4)

120 13/07/2016 Nokia 2014 - RN3164-16A WCD


120 RN31648EN16GLA0 2016 Nokia

10) HSPA to DCH switch triggered in case of CS voice RAB


If the UE has full HSPA configuration, a switch to another configuration is triggered in
the following cases:
CS voice RAB establishment
full HSPA (including CS voice over HSPA) configuration cannot be kept anymore, for
example, due to the following reasons:
not successful HSUPA TTI switch from 2 ms to 10 ms
quality reasons
start of compressed mode
a cell that does not support CS voice on HSPA is added to the active set
a cell that is under the DRNC is added to the active set
RAB combination not supported with full HSPA configuration (but supported with
DCH)

RN31648EN16GLA0 119
HSUPA RRM & Parameters

Slide 121

E-DCH Release
EDCHMACdFlowThroughputAveWin
Throughput measurement window size of E-DCH MAC-d flow throughput
taken every TTI measurement
RNC; 0.5..10; 0.5; 3 s
individual samples averaged over sliding window of size
EDCHMACdFlowThroughputAveWin
EDCHMACdFlowThroughputRelThr
first average available when sliding window full low throughput threshold of the E-DCH MAC-d flow
sliding window moved every TTI RNC; 0..64000; 256; 256 bps
Release Trigger: low throughput indication EDCHMACdFlowThroughputTimetoTrigger
After E-DCH allocation no MAC-d flow detected for low throughput time to trigger of the E-DCH MAC-d flow
EDCHMACdFlowThroughputAveWin + 2 s RNC; 0..300; 0.2 s; 5 s
Low throughput EDCHMACdFlowThroughputRelThr EDCHMACdFlowTputStrTtT
during EDCHMACdFlowThroughputTimetoTrigger (or low throughput time to trigger for streaming E-DCH
EDCHMACdFlowTputStrTtT for streaming E-DCH) MAC-d flow
if low throughput indication has been sent & throughput RNHSPA; 0..300; 0.2 s; 5 s
returns above threshold then normal throughput indication
Low
is triggered immediately EDCHMACdFlowThroughputAveWin throughput
HS-DSCH released indication
E-DCH release sent to
independent on layer 3
Throughput

Normal
actual throughput
throughput
TTI
Result

If low throughput in the UL is indicated indication sent to


for one RAB of a Multi PS RAB because layer 3
no data is to be transferred, the radio EDCHMACdFlowThroughputRelThr
bearer of the inactive RAB is released.
EDCHMACdFlowThroughputTimetoTrigger
121 13/07/2016 Nokia 2014 - RN3164-16A WCD
121 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 120
HSUPA RRM & Parameters

Slide 122

E-DCH Release for identified Smartphone


SmartHSPATputAveWin
The E-DCH inactivity control for the identified Smartphone Window size for Smartphone throughput measurement
follows the principles RNHSPA; 0.5..10; 0.5; 1 s
described in the MAC layer throughput measurements of Special value (0) Smartphone measurement not active
(non_Smartphone measurement active for
the E-DCH NRT and streaming Smartphones)
MAC-d, except the following new parameters:
SmartHSPATimeToTrigger
SmartHSPATputAveWin (used instead of Time-to-trigger for Smartphone throughput
EDCHMACdFlowThroughputAveWin) measurement
SmartHSPATimeToTrigger (used instead of RNC; 0.2..20; 0.2; 0.2 s
EDCHMACdFlowThroughputTimetoTrigger)

SmartHSPATputAveWin

Low throughput indication


Throughput

sent to layer 3

TTI Normal throughput indication


Result

sent to layer 3

EDCHMACdFlowThroughputRelThr
SmartHSPATimeToTrigger

122 13/07/2016 Nokia 2014 - RN3164-16A WCD


122 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 121
HSUPA RRM & Parameters

Slide 123

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
123 13/07/2016 Nokia 2014 - RN3164-16A WCD
123 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 122
HSUPA RRM & Parameters

Slide 124

Frequency Domain Equalizer fdeEnabled


BTSSCW; 0 (false), 1 (true)
Basics:
before RU30: Node B receiver based on RAKE receiver technology
RAKE unable to receive high data rates even in total absence of other cell
interference short spreading codes (SF2) vulnerable to ISI
RU30 introduces:
RAN1702: Frequency Domain Equalizer FDE
RAN1308: HSUPA Interference Cancellation IC
FDE can remove ISI, leaving other users of same cell & surrounding cells to be main
limiting factors for UL data rates
Interference from other users of the own cell can reduced by HSUPA IC
FDE is prerequisite for UL 16QAM (RU30)

removes ISI
UL Noise RAKE UL Noise FDE enables higher
Power Power
PrxMaxTargetBTS PrxMaxTargetBTS throughput
prerequisite for
HSUPA 16QAM

4 Mbps 8 Mbps

FDE: Frequency Domain Equalizer


IC: Interference Cancellation
ISI: Inter-Symbol-Interference
124 13/07/2016 Nokia 2014 - RN3164-16A WCD
124 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 123
HSUPA RRM & Parameters

Slide 125

Frequency Domain Equalizer


Challenges for UMTS receiver

Multipath delays --> handled by time delay synchronization


Phases of the multipath component --> handled by carrier phase synchronization
Amplitudes of the multipath components --> handled by amplitude tracking

125 13/07/2016 Nokia 2014 - RN3164-16A WCD


125 RN31648EN16GLA0 2016 Nokia

In practical RAKE receivers synchronization sets some requirements


Automatic Gain Control (AGC) loop is needed to keep the receiver at the dynamic range of the A/D
converter (Analog-to-Digital).
AGC must be fast and accurate enough to keep receiver at the linear range
Frame-by-frame data range change may set higher AGC and A/D converter requirements
The high sampling rates of few tens of MHz and high dynamics of the input signal (80 dB) require fast A/D
converters and high resolution

RN31648EN16GLA0 124
HSUPA RRM & Parameters

Slide 126

Frequency Domain Equalizer


Only rake receiver was used in RU20 & earlier releases

RAKE delivers adequate performance for data rates below 2 Mbps; its main tasks are:
Identify the time delay positions at which significant energy arrives and allocate
correlation receivers, i.e. Rake fingers, to those peaks.
Within each correlation receiver, track the fast-changing phase and amplitude values
originating from the fast fading process and utilize them.
Combine the demodulated and phase-adjusted symbols across all active fingers and
present them to the decoder for further processing.

126 13/07/2016 Nokia 2014 - RN3164-16A WCD


126 RN31648EN16GLA0 2016 Nokia

RAKE receiver functions


1. Channel delay estimation or Impulse Response (IR) Measurement for multipath components (The accuracy of the IR
measurement is chip (65,1 ns))
2. RAKE receiver finger allocation based on the channel delay estimation
3. RAKE receiver fingers to perform the descrambling and despreading operations
4. Adaptive Channel Estimation
5. Maximal-Ratio Combining
Matched filter:
-Impulse Response Measurement
-Largest peaks to RAKE fingers
-Timing and delay equalizer
-Tracks and monitors peaks with a measurement rate depending on speeds of mobile station and on propagation environment
Code Generators
-PN codes for the user or channel
Correlator:
-Despreading and integration of user data symbols
Channel Estimator:
-Channel state estimate
-Channel effect corrections
Phase Rotator:
-Phase correction
Delay Equalizer:
-Compensates delay for the difference in the arrival times of the symbols in each finger

RN31648EN16GLA0 125
HSUPA RRM & Parameters

Combiner:
-Adding of the channel compensated symbol
-Multipath diversity against fading

RAKE receiver uses a multipath diversity principle (it rakes the energy from the multipath propagated signal components)
* RAKE receiver utilizes multiple correlators to separately detect M strongest multipath components
* Each correlator detects a time-shifted version of the original transmission, and each finger correlates to a portion of the signal,
which is delayed by at least one chip in time from the other fingers.
The outputs of each correlator are weighted to provide better estimate of the transmitted signal than is provided by a single
component
Demodulation and bit decisions are then based on the weighted outputs of the M correlators

RN31648EN16GLA0 126
HSUPA RRM & Parameters

Slide 127

Frequency Domain Equalizer


FDE = linear equalizer + fast convolution
FDE (LMMSE) provides optimal linear estimate of transmitted signal accounting for both:
Channel impact (fading)
Interference + noise
FDE is a combination of linear equalization & fast convolution.
Convolution is relatively demanding in terms of computation
Convolution can be replaced by multiplication if completed in the frequency domain FFT
FDE reduces the effects of ISI arising from users own signal due to multipath propagation.
FDE applied to users with granted 2xSF2 + 2xSF4 (QPSK or 16-QAM) up to 11.5 Mbps.

signal FFT FDE scheme

Despreading
IFFT and bits
detection
Channel MMSE filter
pilot coefficient
estimation
calculation

Time domain Frequency domain (I)FFT: (Inverse) Fast Fourier Transformation


ISI: Inter-Symbol-Interference
LMMSE: Linear Minimum-Mean-Square-Error
127 13/07/2016 Nokia 2014 - RN3164-16A WCD
127 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 127
HSUPA RRM & Parameters

Slide 128

Frequency Domain Equalizer ETFCIBoost


E-DPCCH boosted mode RNC; 0..127; 1; 102

FDE sensitive to channel estimation => E-DPCCH boosted mode used for channel & SIR estimation
E-DPCCH boosted mode E-DPCCH bound to E-DPDCH power (not to DPCCH, as usual)
Starting from ETFCIBoost E-TFCI Default value, UE selects 16QAM & start to use boosted mode.
Boosted mode introduction to increase E-DPCCH power proportionally to high data rates. High data rates are source of
high self interferences boosted E-DPCCH useful for E-DPDCH channel estimation & demodulation.
not mandatory for UE to support E-DPCCH power boosting (requires Rel. 7 or newer UE)
UE indicates support of E-DPCCH power boosting within RRC Connection Setup Complete message
RNC signals E-DPCCH power boosting parameters to UE
boosted mode

non-boosted mode
non-boosted mode
boosted mode

E-DPDCH
E-DPDCH

E-DPDCH
E-DPDCH

E-DPCCH
E-DPDCH
E-DPDCH
E-DPDCH
E-DPDCH E-DPCCH

E-DPCCH
E-DPCCH E-DPCCH
E-DPCCH E-DPCCH
E-DPCCH
DPCCH
DPCCH DPCCH
DPCCH DPCCH DPCCH
DPCCH DPCCH

low E-TFC high E-TFC low E-TFC high E-TFC

128 13/07/2016 Nokia 2014 - RN3164-16A WCD


128 RN31648EN16GLA0 2016 Nokia

Boosted mode tries to reduce sensitivity of FDE to the channel estimation. Due to the fact that main part of FDE
process is based on multiplication by L-MMSE taps, that is why performance of FDE depends strongly on the channel
estimation. In increased noise level environment proper channel estimation based only on DPCCH could be not
enough, that is why in boosted mode E-DPCCH power level is increased, based on this better channel estimation is
possible.

RN31648EN16GLA0 128
HSUPA RRM & Parameters

Slide 129

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
129 13/07/2016 Nokia 2014 - RN3164-16A WCD
129 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 129
HSUPA RRM & Parameters

Slide 130

HSUPA Interference Cancellation Receiver


Basics:
reduces UL Intra-cell interference with non-linear Interference Cancellation IC
method called Parallel Interference Cancellation (PIC)
RAN1308: Basic PIC decreases interference from HSUPA 2 ms TTI users to other UL
channels
improved coverage e.g. for AMR calls existing in parallel with peak rate users
RAN2250: Enhanced PIC (RU50) decreases interference from HSUPA 2 ms TTI
users on each other
larger peak HSUPA data rates (also 16-QAM)
PIC works more efficiently with FDE (RU30)
Improving HSUPA 16QAM (RU40)
Feature activated by BTS license key

IC users: Non-IC users:


Users mapped on E-DCH with 2ms TTI for which Rest of 2ms TTI E-DCH users, all 10ms TTI E-
Interference Cancellation IC is applied usually DCH users and all DCH users
users with the highest power Interference is reduced for non-IC users only
IC users do not get any direct benefit from IC
(indirectly from lower Tx power of other users)

130 13/07/2016 Nokia 2014 - RN3164-16A WCD


130 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 130
HSUPA RRM & Parameters

Slide 131

Basic Parallel Interference Cancellation (PIC) method


UL signal received with Rake Receiver or FDE technique
Turbo decoding obtain 2 ms TTI E-DCH signals
Decoded data used to reconstruct original 2 ms TTI signals (interference for other users)
Reconstruction includes turbo encoding spreading & modulation.
Cancel interference from 2 ms TTI user: Reconstructed signals are summed up & subtracted from the
original antenna signal non-IC users signal (residual signal)
Non-IC users signals are demodulated on the residual signal, benefiting from a lower interference level
improving cell coverage & capacity

UL signal from
antenna
Non-IC users
10ms HSUPA,
De-modulate
2ms HSUPA
Re-modulate
2ms HSUPA De-modulate
other DCH
user data
IC users 2ms HSUPA
Interference cancelled
2ms HSUPA Non-IC users signal
user data (Residual signal)
FDE: Frequency Domain Equalizer
PIC: Parallel Interference Cancellation
131 13/07/2016 Nokia 2014 - RN3164-16A WCD
131 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 131
HSUPA RRM & Parameters

Slide 132

Enhanced PIC method


epicEnabled
Basic PIC: IC users do not benefit directly from reduced interference
BTSSCW; 0 (false), 1 (true)
their signals are demodulated in parallel on the original antenna signal
Enhanced PIC (RAN2250):
demodulate IC users signals again after residual signal reconstruction for these signals (to gain from IC of Basic PIC).
Residual Stream Reconstruction RSR: individual residual signal generated for each 2 ms TTI user, adding its
reconstructed signal to common residual signal.
interference from 2 ms TTI users canceled from other 2 ms TTI users signals

Non-IC users
2ms HSUPA
interference
10ms HSUPA,
UL signal from De-mod
cancelled all others DCH
antenna
user data
De-modulate
De-modulate Re-modulate
Re-modulate Common

De-modulate Re-modulate
2ms HSUPA
2ms HSUPA 2ms HSUPA
2ms HSUPA Residual signal
2ms HSUPA 2ms HSUPA
IC users

First stage De-mod 2ms HSUPA


RSR
detected 2ms HS
RAN1308 user data
IC users data
RAN2250 2nd stage detected
Individual signal of 2ms E-DCH user and residual Individual IC users data
signal are the streams used for the RSR process Residual signal
FDE: Frequency Domain Equalizer
PIC: Parallel Interference Cancellation
RSR: Residual Stream Reconstruction
132 13/07/2016 Nokia 2014 - RN3164-16A WCD
132 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 132
HSUPA RRM & Parameters

Slide 133

Effect of IC / HSUPA scheduling with Basic PIC


Part of received total wideband power is cancelled
RTWP = PNoise + PR99 + P10ms + P2ms
Residual RTWP = PNoise + PR99 + P10ms + (1-) * P2ms
Achievable interference reduction factor highly dependent on:
Quality of signal that should be cancelled (2ms TTI UEs) BTS uses 2 scheduling targets
Data rate of UE to be cancelled for HSUPA:
Radio channel of the UE: Multi-path profile, UE Velocity RTWP < PrxMaxOrigTargetBTS
Residual RTWP < PrxMaxTargetBTS
RTWP Residual PrxMaxOrigTargetBTS
RTWP WCEL; 0..30; 0.1; 8 dB
PrxMaxOrigTargetBTS
PrxMaxTargetBTS
HSUPA 2 ms WCEL; 0..30; 0.1; 6 dB
PrxMaxTargetBTS HSUPA 2 ms
HSUPA HSUPA
10 ms 10 ms

R99 users R99 users


RTWP: Received Total Wide Band Power

Noise Noise

133 13/07/2016 Nokia 2014 - RN3164-16A WCD


133 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 133
HSUPA RRM & Parameters

Slide 134

Effect of IC / HSUPA scheduling with Enhanced PIC

RRM algorithms (RAN1308) allows an


Scheduling period #0 Scheduling period #1 increase of the total cell throughput or the
peak data rate of NRT users mapped on the
PrxMaxOrigTargetBTS E-DCH transport channel with 2 ms TTI
2ms TTI
PrxMaxTargetBTS
UE #1
2ms TTI UE-specific RX power from residual stream
UE #1 2ms TTI reconstruction.
UE #1
2ms TTI
UE #1
RSR
2ms TTI 2ms TTI
2ms TTI UE #1 other
other 2ms TTI 2ms TTI
2ms TTI other other
other Power targets are set on original stream,
HSUPA HSUPA
CS AMR
2ms TTI HSUPA CS CS AMR HSUPA CS HSUPA CS however the targets are applied on the
AMR 2ms TTI 2ms TTI AMR 2ms TTI AMR 2ms TTI
common residual signal stream after
HSUPA HSUPA HSUPA HSUPA HSUPA cancellation.
10ms TTI 10ms TTI 10ms TTI 10ms TTI 10ms TTI

Better SIR allows for less transmit power


and more capacity or/and higher cell
DCH DCH DCH DCH DCH
throughput.

Original Residual Stream Original Residual Stream RAN2250


Stream (2ms TTI cancelled) Stream (2ms TTI cancelled) UE-specific residual stream after
residual stream reconstruction
RAN1308

134 13/07/2016 Nokia 2014 - RN3164-16A WCD


134 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 134
HSUPA RRM & Parameters

Slide 135

PIC pool & state


PIC pool:
set of cells within 1 BTS that are candidates for interference
cancellation (IC)
f1 f2 supports up to 6 cells
3 cells may perform IC simultaneously
PIC pool configuration done by operator via BTS configuration
max. 4 PIC pools per BTS
AssignedPICPool
AssignedPICPool indicates WCEL; 0 (off); 1; 2; 3; 4
which PIC pool the cell belongs to
Basic PIC functionality takes fixed number of CE per PIC pool:
48 CE
PIC-state of a cell in a PIC-Pool can be changed by
AdminPICState*.
PIC-deactivated, PIC-activated, PIC-automatic
PIC state change of cells with PIC-Automatic is controlled
cells in PIC pool by BTS
Cells with highest traffic shall be selected for IC
cells performing Cell are deselected for IC if traffic has decreased
Interference Cancellation

AdminPICState
*There may be restriction in WBTS for changing the PICState. If the WCEL; 0 (Enabled), 1 (Disabled), 2 (Automatic)
change is not possible, then the PICState remains.
PIC: Parallel Interference Cancellation
135 13/07/2016 Nokia 2014 - RN3164-16A WCD
135 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 135
HSUPA RRM & Parameters

Slide 136

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
136 13/07/2016 Nokia 2014 - RN3164-16A WCD
136 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 136
HSUPA RRM & Parameters

Slide 137

RAN3040: IRC (Interference Rejection Combining) receiver


Introduction

Recent large increase in traffic and cell density results


in increase of interference from adjacent cell. I1
interferer
I2
Especially UL interference are becoming more of an
issue due to increase popularity of smartphones, which
S1
are known to generate a lot of short data sessions and base
S2 station
associated signaling.
mobile
Nokia has implemented number of solutions to combat
UL interference issue, e.g.: Q Q
- RAN1308 HSUPA Interference Cancellation Receiver S2
S1
- RAN2250 Enhanced HSUPA Interference Cancellation I1
Icombined
N I N
IRC I
Scombined
RAN3040 Interference Rejection Combining Receiver is I2
the next step feature which brings further improvements
in UL interference cancellation

137 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 137
HSUPA RRM & Parameters

Slide 138

RAN3040: IRC (Interference Rejection Combining) receiver


Introduction - RAN3040 Interference Rejection Combining

Interference Rejection Combining at base station removes I1


dominant interference from a useful uplink signal before interferer
I2
demodulation and before possible further reduction of
interference by interference cancellation. S1
base
S2 station

The source of interference can be: mobile


intra-cell,
inter-cell, Q Q
inter-frequency
S2
or external from WCDMA. S1
I1
Icombined
N I N
IRC I
Scombined
I2
IRC supports 2Rx or 4Rx antenna setup (at least 2
antennas must be present in the BTS).

138 RN31648EN16GLA0 2016 Nokia

IRC (Interference Rejection Combining) receiver is based on combining the antenna


signals from more than 1 antenna so that interference is reduced. IRC process evaluates
the covariance of interference between the antennas, with the goal of whitening of
colored interference.
A 4Rx antenna setup would allow 3 noise sources to be rejected.
So theoretically the more antennas there are in the BTS
the more gain is expected.

In case of no interferers, no gain is expected.

RN31648EN16GLA0 138
HSUPA RRM & Parameters

Slide 139

RAN3040: IRC (Interference Rejection Combining) receiver


Introduction - RAN3040 Interference Rejection Combining

Two stage application of IRC when RAN2250 is in use. In this setting feature gains tops up. Without
RAN2250 single stage IRC is applied (IRC instead of Maximum Ratio Combining MRC).

r(k) Subgroup interference cancellation

Bank of single IC user


r(k)
detectors Total interference
reconstruction
DEM
DEM
(1)r(k) First stage detected
r(k)
DEM REM ? + + IRC symbols of non-IC
+ IRC 1
M
.. - users

RSR DEM Second stage detected


RAN1308
DEM symbols of IC users
+ IRC
RAN2250

With IRC at the first stage the interference estimation/elimination is improved


With IRC at the second stage the remaining external interference can be suppressed

139 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 139
HSUPA RRM & Parameters

Slide 140

RAN3040: IRC (Interference Rejection Combining) receiver


Improvements

Before After
Interference Rejection Combining is evaluating the
Maximum Ratio Combining - the gain of each channel
covariance of interference between the antennas, aiming
(finger) is made proportional to the rms signal level and
to whitening of interference, provides higher SINR =
inversely proportional to the mean square noise level in
S/(I+N) than MRC after combining.
that channel.
Q Q Q
Q
S2 Icombined S2 S1
S1 Icombined
I1 I1
N N I IRC I
NN I MRC I
Scombined N Scombined
N+I

N+I I2
I2
Higher UE
throughput
S
S

Better coverage

MRC maximizes wanted signal while ignores interference. Signals are combined so to achieve best possible SINR.

140 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 140
HSUPA RRM & Parameters

Slide 141

RAN3040: IRC (Interference Rejection Combining) receiver


Introduction - IRC Gains

Following gains are expected when


Cell Max Throughput UE Max Throughput IRC is used together with IC and
Up to ~20%* gain Up to ~20%* gain Enhanced IC:

Compared to MRC, IRC provides With IRC UE throughput increases Cell Max Throughput
more combining gain for UL services: which will positively influence user
AMR, R99, and HSUPA (2 and 10 ms perceived quality of service. Up to ~60%* gain
TTI). More cell throughput can be
obtained in the UL direction, which
can be mapped to more capacity in UE Max Throughput
terms of simultaneous users.
Up to ~60 %* gain
Cell coverage can be better kept than
without the feature.

*) according to system level simulation results, 2 antenna configuration. For 4 antenna gains can be higher.

141 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 141
HSUPA RRM & Parameters

Slide 142

RAN3040: IRC (Interference Rejection Combining) receiver


Deployment Aspects

RAN3040, Interference Cancellation and FDE

RAN RAN RAN


+ + IRC can be used with or without RAN1308 HSUPA Interference
3040 1308 2250 Cancellation Receiver (IC) and RAN2250 Enhance HSUPA Interference
Cancellation Receiver (eIC).
RAN RAN
+
3040 1308 When used without IC the IRC reduces dominant interference
independent on whether the interference is originated from users in the
same cell, surrounding cells or external sources.
RAN
3040 When used together with IC, IC provides the most efficient tool against
own cell interference while the role of IRC is to protect against dominant
interference from those sources which cannot be covered by IC.

For 2 RX antennas the following combinations are possible:


IRC, IRC+IC, IRC+FDE, IRC+IC+FDE
For 4 RX antennas only IRC is available in WCDMA16.

142 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 142
HSUPA RRM & Parameters

Slide 143

RAN3040: IRC (Interference Rejection Combining) receiver


Resource Consumption

IRC will take more BTS DSP resources than MRC, but it will not decrease the total number of
HSPA users one BTS can support as BTS will use the "best effort" mechanism to
activate/deactivate IRC for users.

BTS activate/deactivate IRC receiver for users based on the CPU load.

So the maximum number of HSPA users is not affected by IRC operation.

IRC order of UE prioritization:

- With IC enabled: 2ms to 10ms & AMR


- With IC disabled: 10ms & AMR to 2ms

143 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 143
HSUPA RRM & Parameters

Slide 144

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
144 13/07/2016 Nokia 2014 - RN3164-16A WCD
144 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 144
HSUPA RRM & Parameters

Slide 145

HSUPA 16QAM: RAN1645 HSUPA16QAMAllowed


WCEL; Disabled (0), Enabled (1)
Brief description of 16 QAM in UL
Dual 4PAM modulation is used (4PAM 4 symbols & 2 bits per symbol) Dual 4PAM
Variable SF2 for Bit Rate (BR) adjustment 4 bits/symbol
Multicode operation is needed to maximise Bit Rate after max SF is used (max 4
data codes in parallel when no DPDCH configured)
With W=3.84McpsSymbol rate=2W/SF2+ 2W/SF4=5760 ksps
BRmax=25760ksps=11520 kbps
Motivation & benefits
Using higher order modulation, more symbols can be transmitted, therefore more bits can be assigned
to each symbol, while the duration of symbol is kept. This results in higher Bit Rate.
Most beneficial with low intra-cell interferences.
Interference cancellation techniques are welcome to lower the intra-cell noise.
Drawbacks
Reduction of the Euclidean distance between adjacent symbols. This results in stricter requirement in
SNR per symbol to achieve the same BER
RoT limit requirement rises high, as the own signal interferences from 16QAM are high. Therefore this
feature is dedicated for micro, pico cells.
145 13/07/2016 Nokia 2014 - RN3164-16A WCD
145 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 145
HSUPA RRM & Parameters

Slide 146

HSUPA 16QAM: Spreading for E-DPDCH/E-DPCCH


Multi-code transmission
Eb Es Ec
4 symbols SF=2
Cch,2,1 ed,1
+ E-DPDCH1 4PAM modulation
mapper
SF=4
4 symbols Cch,4,1 ed,3


E-DPDCH3 I
4PAM modulation
mapper

Cch,256,1 ec
E-DPCCH BPSK modulation
mapper = 16 symbols
I+jQ
=16QAM
S
SF=2
Cch,2,1 ed,2
E-DPDCH2 4PAM modulation
4 symbols
mapper

+ SF=4
Cch,4,1 ed,4


Q
E-DPDCH4 4PAM modulation
mapper
4 symbols
Cch,256,0 c j

DPCCH BPSK modulation


mapper

146 13/07/2016 Nokia 2014 - RN3164-16A WCD


146 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 146
HSUPA RRM & Parameters

Slide 147

HSUPA 16QAM: Switching Point to 16QAM


Channel Bits per TTI vs RLC bitrate for 2ms TTI
Switch to 16 QAM when:
2xM2+2xM4
RLC Bit Rate>4000kbps (when
Effective Code Rate QPSK>0.712,
then switch to 16QAM)
Code and Modulation Combination

UE selects 16QAM when E-TFCI is


>103 (Table2) or >69 (Table3)

Table 2

Table 3 16QAM:
2xN2+2xN4

2xM2 means 2*SF2 modulated with 4PAM


2xM4 means 2*SF4 modulated with 4PAM
2xN2

Switch to QPSK:
16QAM
2xN4 2xN2 means 2*SF2 modulated with BPSK
2xN4 means 2*SF4 modulated with BPSK
N4
N8
N16
N32
2000 4000 6000 8000 10000 12000

RLC bitrate [kbps]

147 13/07/2016 Nokia 2014 - RN3164-16A WCD


147 RN31648EN16GLA0 2016 Nokia

For the tables definition please go to 3GPP TS 25.321 Annex B E-DCH Transport Block Size Tables for FDD

RN31648EN16GLA0 147
HSUPA RRM & Parameters

Slide 148

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
148 13/07/2016 Nokia 2014 - RN3164-16A WCD
148 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 148
HSUPA RRM & Parameters

Slide 149

Flexible RLC in UL: RAN1910


Included in RU40 basic software package no license needed
HW prerequisites: Flexi rel.2
Can be used if: Flexible RLC in DL and Basic HSUPA are both active
Prior Rel.8 Rel.8 Flexible RLC in UL
TCP/IP TCP/IP
header TCP/IP Payload header
TCP/IP Payload
MTU: 1500 bytes MTU: 1500 bytes

RLC SDU RLC SDU

MAC-es/e RLC MAC-is/i RLC


headers PDUs Paddings headers PDU Padding

19 MAC-es/e 19 fixed RLC PDUs One MAC-is/i One RLC PDU is


headers required + (656 bits each) required header required required per 1500
optional padding per 1500 bytes IP packet + optional padding bytes IP packet

Control data = 3.72% of whole transport block Control data = 0.27% of whole transport block
When the transmission error occurs one small RLC PDU It corresponds to 93% drop of control data for typical IP
needs to be retransmitted packet size of 1500 bytes
When the transmission errors occur one big RLC PDU
needs to be retransmitted
149 13/07/2016 Nokia 2014 - RN3164-16A WCD
149 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 149
HSUPA RRM & Parameters

Slide 150

Flexible RLC in UL: Background


UE selects the E-TFC and TBS according to current grant on TTI basis
RLC operations (segmentation and concatenation) on RLC SDUs are performed to fit
maximum RLC PDU size
New MAC-is/i are introduced in order to handle flexible instead of fixed size RLC PDUs
MAC-i is introduced in the UE and BTS
MAC-is is introduced in the UE and RNC

UE BTS RNC

RLC RLC

MAC-d MAC-d

MAC-is/i MAC-i MAC-is

Uu Iub
150 13/07/2016 Nokia 2014 - RN3164-16A WCD
150 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 150
HSUPA RRM & Parameters

Slide 151

Flexible RLC in UL: Advantages


Relative overhead and padding depends on the number of used PDUs
For the typical IP packet size the relative overhead and padding is reduced from
3.72% to 0.27%, it relates to 93% of drop of control data
25%
Fixed RLC PDU
Relative overhead and padding

20%
Length indicator changed
from 7 to 15 bits RLC PDU changed Relative overhead and
15% from 336 to 656 bits padding is equal to 3.72%

10% Relative overhead and


padding is equal to 0.27%

5%

0%
0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500
RLC SDU size [bytes]

Cell throughput for UE categories VIII and IX is increased


Peak RLC throughput for UE categories VIII and IX is also increased
151 13/07/2016 Nokia 2014 - RN3164-16A WCD
151 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 151
HSUPA RRM & Parameters

Slide 152

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
152 13/07/2016 Nokia 2014 - RN3164-16A WCD
152 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 152
HSUPA RRM & Parameters

Slide 153

Dynamic HSUPA BLER: RAN2302 HSUPADynBLEREnabled


WCEL; 0 (Disabled), 1 (Enabled)

Without the Dynamic HSUPA BLER With the Dynamic HSUPA BLER feature the
feature the BLER is fixed to 10% on first BLER target is optimized for different user
transmission (1st Tx) and on every ReTx scenarios and radio conditions:
Close to BTS: optimizing BLER to get peak rates
regardless to: Cell edge continuous data transmission: optimizing radio
UE - BTS distance (cell edge / close to the BTS) coverage and cell capacity
Bursty / continuous data transmission Bursty traffic: optimizing latency
E-DCH TTI length: 2ms / 10ms
OLPC algorithm (RNC) enhancement
Support for different BLER targets adapted
to current radio transmission conditions

HSUPA Capacity gain*: ~ 20%


HSUPA Coverage gain*: ~ 2dB
HSUPA *Preliminary gain figures from simulations, not
commercially bounding

10%BLER 1%BLER
10%BLER 10%BLER
10%BLER
after 1st
NACK
153 13/07/2016 Nokia 2014 - RN3164-16A WCD
153 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 153
HSUPA RRM & Parameters

Slide 154

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
154 13/07/2016 Nokia 2014 - RN3164-16A WCD
154 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 154
HSUPA RRM & Parameters

Slide 155

High Speed Cell_FACH: RAN1913

Included in RU40 application software package license required


HW prerequisites: Flexi rel.2
Can be used if both Flexible RLC Downlink and Flexible RLC in Uplink features are active
Brief Description:
This feature enables Fast Cell_PCH to Cell_FACH switching (transition <100ms)
Feature enhances High Speed Cell_FACH in DL
Increases possible throughputs on common channels to 1.45Mbps in UL
UL channel mapping:
CCCH DCCH DTCH
HSFACHVolThrDL
Logical channels
WCEL; (0, 8, 16, 32, 64, 128,
256, 512, 1024, 2048, 3072,
Transport channels RACH E-DCH 3GPP Rel8
4096, 8192, 16384) bytes

Physical channels
PRACH E-DPDCH

155 13/07/2016 Nokia 2014 - RN3164-16A WCD


155 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 155
HSUPA RRM & Parameters

Slide 156

High Speed Cell_FACH: With and Without the Feature


RAN1913 Data transmission RAN1913
Not activated Activated

HSPA only on HSPA also on


dedicated channels common channels

Common channels
Common channels
Dedicated channels Dedicated channels

Significant setup time reduction

Cell_PCH to Cell_DCH state change Cell_PCH to Cell_FACH state change


Cell Update required Cell Update not needed
600 ms <100 ms
Data appears in buffer Data appears in buffer

Transmission/recepti t [ms] Transmission/recepti t [ms]


Channel type
Cell switch on in Cell_DCH Channel on in Cell_FACH
update type switch

156 13/07/2016 Nokia 2014 - RN3164-16A WCD


156 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 156
HSUPA RRM & Parameters

Slide 157

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
157 13/07/2016 Nokia 2014 - RN3164-16A WCD
157 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 157
HSUPA RRM & Parameters

Slide 158

High Speed Cell_FACH Enhanced (RAN2518) (New in WCDMA16)


Introduction

More capacity share for common E-DCH


from 16 to 32 HS FACH users

HS FACH/RACH is the most efficient way to handle


bursty and small packet traffic
With increase in such traffic and availability of HS HS FACH/RACH
RACH/FACH capable terminals, more capacity will be
needed for common E-DCH resources
In current implementation it is possible to configure up AICH Common E-DCH resource assigned
to 10 common E-DCH resources per cell. Which means, response UE specific E-RNTI on E-AGCH
simultaneously up to 10 HS RACH users in a cell can DL
send data in the same TTI
AICH E-AGCH

UL
PRACH E-DPDCH E-DPDCH E-DPDCH
E-DPCCH E-DPCCH E-DPCCH

158 RN31648EN16GLA0 2016 Nokia

With High Speed Cell FACH Enabled up to 32 E-DCH common resources


can be configured per cell
E-DCH Common resource consist of:
Symbol offset (Soffset),
F-DPCH code number,
UL DPCH info (Scrambling code number/type),
E-HICH Information (Channelization Code and Signature Sequence)
E-DCH Common resources are reserved for High Speed Cell_FACH users
utilizing HS-RACH in UL (having HS-DCH and E-DCH in Cell_FACH state)

RN31648EN16GLA0 158
HSUPA RRM & Parameters

Slide 159

High Speed Cell_FACH Enhanced (RAN2518)


dimensioning

High Speed Cell_FACH feature dimensioning rules:


Up to eight steps are available for each LCG
single step provides baseband capacity for 10 HS Cell_FACH UL users
single step corresponds to the Baseband capacity equivalent of single HSUPA Resource
Step:
0.125 SU (FSMF)
0.25 SU (FSMC/D/E)

a maximum of 80 HS Cell_FACH UL users can be served in LCG, which corresponds to eight


HSUPA Resource Steps

If RAN2518: is deactivated, up to four steps can be effectively used (up to 40 HS


Cell_FACH UL users).

If RAN2518 is activated, up to eight steps can be used (up to 80 HS Cell_FACH UL users)

159 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 159
HSUPA RRM & Parameters

Slide 160

High Speed Cell_FACH Enhanced (RAN2518)


Configuration management

With RAN2902 RACH Capacity Increase enabled it is recommended that max number of
32 Common EDCH resources is setup

Value HSRACHCommonEDCHRes of 32 provides highest system capacity for HS FACH


users

- For HSRACHCommonEDCHRes=32 there might not be 15 HSPA codes available (2 HSDPA codes
are needed statically)

HSRACHCommonEDCHRes value can be adjusted based on M5000C489 AVERAGE


COMMON EDCH RESOURCE USAGE counter

160 RN31648EN16GLA0 2016 Nokia

HSRACHCommonEDCHRes
This parameter defines the number of Common E-DCH Resources of the HS-RACH configuration in the cell.
Common E-DCH resource(s) is(are) setup in the cell when the HS-RACH is setup in the cell and are under direct
control of the Node B and are shared by UEs in CELL_FACH and IDLE mode.
The RNC is not involved in the assignment of these resources to UEs.

RN31648EN16GLA0 160
HSUPA RRM & Parameters

Slide 161

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Frequency Domain Equalizer
HSUPA Interference Cancellation Receiver
IRC (Interference Rejection Combining) receiver (RAN3040) WCDMA16
HSUPA 16QAM
Flexible RLC in UL
Dynamic HSUPA BLER
High Speed Cell_FACH
High Speed Cell_FACH Enhanced (RAN2518) WCDMA16
Dual Cell HSUPA
Appendix
161 13/07/2016 Nokia 2014 - RN3164-16A WCD
161 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 161
HSUPA RRM & Parameters

Slide 162

Dual Cell HSUPA (RAN1905)


Simultaneous UL transmission (two carriers) maximum UL throughput of:
2 X 11.5Mbps = 23Mbps if 16QAM is used
11.5Mbps without 16QAM (QPSK modulation).

DC-HSUPA Non-
Real Time traffic

E-DCH 1 on frequency 1
Up to 11.5 Mbps per E-DCH 2 on frequency 2
UE (2x QPSK)

162 13/07/2016 Nokia 2014 - RN3164-16A WCD


162 RN31648EN16GLA0 2016 Nokia

3GPP Rel.9 introduces simultaneous UL transmission using two carriers allowing a maximum UL throughput of 2 X
11.5Mbps = 23Mbps if 16QAM is used and 11.5Mbps without 16QAM (QPSK modulation).

RN31648EN16GLA0 162
HSUPA RRM & Parameters

Slide 163

Dual Cell HSUPA (RAN1905) DCellHSUPAEnabled


WCEL; 0 (Disabled), 1 (Enabled)

DC-HSUPA is enabled using the WCEL parameter DCellHSUPAEnabled.


Power offset between the initial DPCCH power level on secondary UL frequency
when it is activated and the current DPCCH power level on primary UL frequency can
be defined with DPCCHPwrOffsetSecULFreq WCEL parameter.
MaxNumberEDCHS defines the maximum allowed number of SC-E-DCH and DC-E-
DCH users in the MAC-i/is specific BTS scheduler.
DPCCHPwrOffsetSecULFreq
MaxNumberEDCHS DC-HSUPA Non-Real Time traffic WCEL; 0..7 dB, step 1 dB; 3 dB
WCEL; 1..1023, step 1
0 Not restricted

E-DCH 1 on frequency 1
Up to 11.5 E-DCH 2 on frequency 2
Mbps per UE
(2x QPSK)

163 13/07/2016 Nokia 2014 - RN3164-16A WCD


163 RN31648EN16GLA0 2016 Nokia

DPCCHPwrOffsetSecULFreq:
3 dB means that the UE will use half of the current DPCCH power level on primary UL frequency as the
initial DPCCH power level on secondary UL frequency when it is activated
MaxNumberEDCHS:
RNC does not exceed the maximum number but admission of SC-E-DCH and DC-E-DCH user is inhibited in the
scheduler if the maximum number is to be exceeded
This parameter is defined per cell and because scheduler consists of several cells, lowest parameter values of cells
forming scheduler shall be used

RN31648EN16GLA0 163
HSUPA RRM & Parameters

Slide 164

Dual Cell HSUPA (RAN1905)

This feature allows the use of two adjacent WCDMA carriers simultaneously in the UL for a single UE

E-DPDCH
E_AGCH
HS-SCCH E-DPDCH
E-RGCH Primary
F1 HS-PDSCH HS-DPCCH (Ack/Nack/CQI)
E-HICH Carrier
F-DPCH E-DPCCH
E-DPCH
UL-DPCCH

E_AGCH E-DPDCH
HS-SCCH
E-RGCH E-DPDCH
HS-PDSCH
Secondary
F2
E-HICH E-DPCCH Carrier
F-DPCH
E-DPCH UL-DPCCH

164 13/07/2016 Nokia 2014 - RN3164-16A WCD


164 RN31648EN16GLA0 2016 Nokia

Scheduling information and power control is per carrier:


2x E-AGCH/E-RGCH: Independent data rate upgrade/downgrade
2x E-HICH: Independent ACK/NACK
2x F-DPCH: Independent UL Power Control Loop
2x E-DPCCH Independent Happy Bit (HB)
2x E-DPDCH Independent Scheduling Information (SI)

UE transmitting HSUPA NRT data on two carriers per one TTI


UE can actively use DC-HSUPA across whole cell range as long as throughput on secondary carrier is >168kbps
In contrast to HSUPA 16QAM, the radio conditions and Interference Margin is not so critical for the BTS to allow DC-
HSUPA UE transmission (DC likely to be used in mid-cell)
DC-HSUPA dynamically taken into use whenever capacity on secondary carrier exists

RN31648EN16GLA0 164
HSUPA RRM & Parameters

Slide 165

Dual Cell HSUPA (RAN1905)


Related (modified) parameters:
MaxNumberEDCHCell (Maximum number of E-DCHs in the cell): DC-E-DCH user is counted only in
the primary cell

MaxNumberEDCHLCG (Maximum number of E-DCHs in the Local Cell Group (LCG)): DC-E-DCH
user is counted once per LCG

DC-HSUPA
Frequency 1
LCG

Frequency 2

HSUPAXUsersEnabled defines maximum allowed number of (DC-)E-DCH users in LCG/BTS


165 13/07/2016 Nokia 2014 - RN3164-16A WCD
165 RN31648EN16GLA0 2016 Nokia

At least two frequencies (UARFCN parameter) need to be available and configured


Make sure DC-HSUPA UARFCNs are adjacent in frequency band
DC-HSUPA cells of one sector must be from the same Local Cell Group (precondition valid also for DC-HSDPA)
DC-HSUPA enabled cells in DL need to be handled by one HSDPA scheduler (DC-HSDPA precondition)
DC-HSDPA must be activated to those cells that are going to be DC-HSUPA enabled (DCellHSDPAEnabled)
up to 10 UEs per sector per cell can get the double throughput (comparing to SC HSUPA)
The following parameters must be enabled in order to activate DC_HSUPA:
HSUPA2MSTTIEnabled
FDPCHEnabled
FlexULRLCEnabled

RN31648EN16GLA0 165
HSUPA RRM & Parameters

Slide 166

HSUPA RRM: Contents


HSUPA Principles
TTI: 2 ms / 10 ms
HSUPA Physical Channels
E-TFC Selection
BTS Scheduling
HSUPA Power Control
HSUPA Load Control
HSUPA Mobility
HSUPA Channel Type Selection & Switching
HSUPA Improvements
Appendix:
Basics of HSUPA Congestion Control
Data Flow from UE to RNC
Congestion Detection
Actions in Case of Congestion
166 13/07/2016 Nokia 2014 - RN3164-16A WCD
166 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 166
HSUPA RRM & Parameters

Slide 167

HSUPA Congestion Control: Principles


RNC responsible to detect congestion on Iub & 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

Data Flow from UE to RNC (1/5) BTS RNC

E-DCH FP
E-DCH FP Congestion
Uplink Detection
E-DPCH

E-DCH
Packet
Scheduler

UE sends HSUPA data carrying one


transport block (MAC-e PDU)
E-DCH FP Congestion
Downlink Indication
N
DDI MAC-es PDU SI Padding

MAC-e PDU
167 13/07/2016 Nokia 2014 - RN3164-16A WCD
167 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 167
HSUPA RRM & Parameters

Slide 168

Data Flow from UE to RNC (2/5)

BTS RNC

E-DCH FP
E-DCH FP
E-DPCH Congestion
Uplink
Detection

E-DCH
Packet
Scheduler
Node B
Decodes E-DPDCH
Forwards MAC-e PDU with connection E-DCH FP Congestion
frame number CFN Downlink Indication

MAC-e entity
Extracts MAC-es PDU

N
CNF DDI MAC-es PDU SI Padding MAC-e PDU before extraction

CNF MAC-es PDU MAC-e PDU after extraction

168 13/07/2016 Nokia 2014 - RN3164-16A WCD


168 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 168
HSUPA RRM & Parameters

Slide 169

Data Flow from UE to RNC (3/5)

BTS RNC

E-DCH FP

E-DCH FP Congestion
E-DPCH
Uplink Detection

E-DCH
Packet
Scheduler
E-DCH FP entity
Constructs E-DCH FP frame from MAC- es
Congestion
PDUs and CFN E-DCH FP
Indication
Attaches frame sequence number FSN Downlink

FSN CNF MAC-es PDU MAC-es PDU MAC-es PDU

UL FP frame

169 13/07/2016 Nokia 2014 - RN3164-16A WCD


169 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 169
HSUPA RRM & Parameters

Slide 170

Data Flow from UE to RNC (4/5)

BTS RNC

E-DCH FP
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
E-DCH
Packet
Scheduler

E-DCH FP Congestion
Downlink Indication

Node B sends E-DCH UL FP frame (FSN,


CFN and MAC-es PDUs) to RNC

FSN CNF MAC-es PDU MAC-es PDU MAC-es PDU

170 13/07/2016 Nokia 2014 - RN3164-16A WCD


170 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 170
HSUPA RRM & Parameters

Slide 171

Data Flow from UE to RNC (5/5)


BTS RNC

TNL E-DCH FP
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
E-DCH
Packet
Scheduler

Congestion
E-DCH FP Indication
Downlink

Node B buffers user plane data at ATM layer


Buffering causes variable delay to E-DCH FP
transmission
Intermediate ATM nodes across transport
network generate further delay variance.

171 13/07/2016 Nokia 2014 - RN3164-16A WCD


171 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 171
HSUPA RRM & Parameters

Slide 172

Congestion Detection (1/4)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
E-DCH
Packet
Scheduler

E-DCH FP Congestion
Downlink Indication

RNC Congestion Detection entity detects possible


TNL congestion based upon
Delay build-up
Lost frames
172 13/07/2016 Nokia 2014 - RN3164-16A WCD
172 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 172
HSUPA RRM & Parameters

Slide 173

Congestion Detection (2/4)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
E-DCH
Packet
Scheduler

E-DCH FP Congestion
Downlink Indication

Frame loss detected from FSN if


FSN(n) != (FSN(n-1) +1) mod 16
Delay calculated from CFN and time of
receiving the E-DCH FP frame.

173 13/07/2016 Nokia 2014 - RN3164-16A WCD


173 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 173
HSUPA RRM & Parameters

Slide 174

Congestion Detection (3/4)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
Delay
E-DCH Frame loss
Packet
Scheduler

E-DCH FP Congestion
Downlink Indication

Congestion detection entity informs congestion


indication entity about delay & frame loss
Congestion indication entity compares delay with
thresholds analogue to those used for HSDPA
174 13/07/2016 Nokia 2014 - RN3164-16A WCD
174 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 174
HSUPA RRM & Parameters

Slide 175

Congestion Detection (4/4)

Probability for congestion indication P(t) DelayThresholdMin


Minimum Threshold value for
HSUPA congestion delay
1 WBTS; 0..320; 0.01; 50 ms
DelayThresholdMid
Pmax Middle Threshold value for HSUPA
congestion delay
Cong. ind. with slowly
WBTS; 0..320; 0.01; 70 ms
increasing P(t)
Cong. ind. in any case
DelayThresholdMax
Maximum Threshold for HSUPA
congestion handling delay
WBTS; 0.01..320; 0.01; 100 ms
Cong. ind. with rapidly
increasing P(t) DelayThresholdMax2msTTI
Delay t Maximum Threshold for HSUPA
50 ms 70 ms 100 ms congestion handling delay 2ms
TTI
WBTS; 0.01..320; 0.01; 100 ms

For HSUPA configurable

175 13/07/2016 Nokia 2014 - RN3164-16A WCD


175 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 175
HSUPA RRM & Parameters

Slide 176

Actions in Case of Congestion (1/5)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
E-DCH Delay
Packet Frame loss
Scheduler

E-DCH_FP_CTRL
E-DCH FP (delay OR Frame loss) Congestion
Downlink Indication

In case of too high delay or frame loss congestion indication entity


sends E-DCH FP control frame to Node B
E-DCH FP control frame type is TNL congestion indication with value
TNL congestion detected by delay build-up or
TNL congestion detected by frame loss
176 13/07/2016 Nokia 2014 - RN3164-16A WCD
176 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 176
HSUPA RRM & Parameters

Slide 177

Actions in Case of Congestion (2/5)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection

E-DPCH
E-DCH Delay
Packet Frame loss
Scheduler
Congestion indication
(delay OR frame loss)
E-DCH_FP_CTRL
E-DCH FP (delay OR Frame loss) Congestion
Downlink Indication

E-DCH FP entity in BTS receives congestion indication & forwards it


to E-DCH packet scheduler

177 13/07/2016 Nokia 2014 - RN3164-16A WCD


177 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 177
HSUPA RRM & Parameters

Slide 178

Actions in Case of Congestion (3/5)


BTS RNC

TNL E-DCH FP

E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection
E-DPCH

Relative Grant
[DOWN] E-DCH Delay
Packet Frame loss
Scheduler
Congestion indication
(delay OR frame loss)
E-DCH_FP_CTRL
E-DCH FP (delay OR Frame loss) Congestion
Downlink Indication

Packet Scheduler decreases UE bit rate by sending


relative grant DOWN command
E-DCH Packet Scheduler decreases UE bit rate more
aggressively in case of frame loss, compared to delay
build-up
178 13/07/2016 Nokia 2014 - RN3164-16A WCD
178 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 178
HSUPA RRM & Parameters

Slide 179

Actions in Case of Congestion (4/5)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection
E-DPCH

Relative Grant
[DOWN] E-DCH Delay
Packet Frame loss
Scheduler
Congestion indication
(delay OR frame loss)
E-DCH_FP_CTRL
E-DCH FP (delay OR Frame loss) Congestion
Downlink Indication

Transmission power taken away from UE due to


congestion is kept reserved & cannot be given to
other UEs in a cell

179 13/07/2016 Nokia 2014 - RN3164-16A WCD


179 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 179
HSUPA RRM & Parameters

Slide 180

Actions in Case of Congestion (5/5)


BTS RNC

E-DCH FP
TNL
E-DCH FP Congestion
Uplink E-DCH_FP_UP (data) Detection
E-DPCH

Relative Grant
[UP] E-DCH Small delay
Packet No frame loss
Scheduler
Congestion indication
(no TNL congestion)
E-DCH_FP_CTRL
E-DCH FP (no TNL congestion) Congestion
Downlink Indication

once congestion is over congestion indication entity send E-DCH FP control frame to Node B
Frame type is TNL congestion indication with value no TNL congestion
receiving no TNL congestion indication E-DCH packet scheduler
stops sending DOWN commands to UE
recovers gradually back to normal operation
180 13/07/2016 Nokia 2014 - RN3164-16A WCD
180 RN31648EN16GLA0 2016 Nokia

RN31648EN16GLA0 180
HSUPA RRM & Parameters

Slide 181

RN31648EN16GLA0 181