05 RN31575EN40GLA0 Capacity Enhancement

3G RANOP RU40
Capacity Enhancement
LTE Layering! A new Module Interworking;
For internal use
RN31575EN40GLA0
2013 Nokia Solutions and Networks. All rights reserved.
Nokia Solutions and Networks Academy

Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Solutions and Networks training
documentation, product documentation and slide presentation material, all of which are forthwith
known as Nokia Solutions and Networks training material, are the exclusive property of Nokia
Solutions and Networks. Nokia Solutions and Networks owns the rights to copying, modification,
translation, adaptation or derivatives including any improvements or developments. Nokia
Solutions and Networks has the sole right to copy, distribute, amend, modify, develop, license,
sublicense, sell, transfer and assign the Nokia Solutions and Networks training material.
Individuals can use the Nokia Solutions and Networks training material for their own personal
self-development only, those same individuals cannot subsequently pass on that same
Intellectual Property to others without the prior written agreement of Nokia Solutions and
Networks. The Nokia Solutions and Networks training material cannot be used outside of an
agreed Nokia Solutions and Networks training session for development of groups without the
prior written agreement of Nokia Solutions and Networks.
For internal use
RN31575EN40GLA0
Module Objectives
At the end of the module you will be able to:
Describe capacity enhancing R99 features
Discuss the impact of R5 and R6 HSPA features on capacity
Demonstrate the capacity enhancement potentials of HSPA
features introduced with R7 and beyond
For internal use
RN31575EN40GLA0
R99 Features
Load Based AMR Codec Mode Selection

BLER target settings
Eb/No settings
Throughput based optimization

Maximum radio link power
4Rx diversity
Network load reduction features in RU40

HSDPA
HSUPA
HSDPA+
HSUPA+
Capacity Usage Optimization
For internal use
RN31575EN40GLA0
Load Based AMR Codec Mode Selection Idea

Enabling Load Based AMR Codec Mode Selection (RAN580) the voice capacity can
be improved:
Voice calls performed as FR or HR calls in dependence on
Non controllable load on DL
Code tree occupation
Iub throughput
For each criterion there is a load indicator having three thresholds

Underload threshold
Target threshold
Overload threshold
FR call
Voice codec sample = {12.2/7.95/5.9/4.75} Kbit/s
DL SF = 128 fixed
HR call
Voice codec sample = {5.9/4.75} Kbit/s
DL SF = 128 or 256 in dependence on code tree occupation
For internal use
RN31575EN40GLA0
AMR - Role of Load

Load
If one load indicator exceeds overload threshold
New calls start as HR
Running FR calls automatically switched to HR
Overload threshold
At least one load indicator exceeds target threshold

But no load indicator exceeds overload threshold
New calls start as HR

Running FR calls remain FR
Target threshold
At least one load indicator exceeds underload threshold
But no load indicator exceeds target threshold
New calls start as FR
Running HR calls remain HR
Underload threshold
If no load indicator exceeds underload threshold
New calls start as FR

Running HR calls automatically switched to FR
For internal use
RN31575EN40GLA0
AMR - Role of Load

Load thresholds for non controllable load on DL
Set relative to PtxTarget (default 40 dBm)
AMRUnderTxNc (default -10 dB)
AMRTargetTxNc (default -2 dB)
AMROverTxNc (default -1 dB)
Load thresholds for code tree occupation
AMRUnderSC (default 50%)
AMRTargetSC (default 70%)
AMROverSC (default 90%)
Load thresholds for Iub throughput
AMRUnderTransmission (default 200 Kbit/s)
AMRTargetTransmission (default 800 Kbit/s)
AMROverTransmission (default 900 Kbit/s)
For internal use
RN31575EN40GLA0
AMR - Selection of SF for HR Calls
AMRSF set relative to maximum allowed RL power determined by AC (default -2 dB)

In case of high RL power SF128 (NOT SF256) better for voice transmission due to DPCCH overhead
For internal use
RN31575EN40GLA0
BLER Target Settings - Idea

For R99 bearers the operator can define the BLER target controlled by outer
loop power control
Strict BLER target (low BLER)

Little throughput degradation and delay by re-transmission good quality for user
But higher Eb/No needed higher power consumption per radio link
Less strict BLER target (high BLER)

Strong throughput degradation and delay by re-transmission bad quality for user
But less Eb/No needed lower power consumption per radio link
For internal use
10
RN31575EN40GLA0
BLER Target Settings - Role of Service

BLER target can be defined for the following services
SRB of 3.4 and 13.6 Kbit/s (EbNoDCHOfSRB34/136Qua, default 1%)
Narrowband and wideband AMR (EbNoDCHOfCSN/WBAMRQua, default 1%)
Streaming service
NRT service
In case of streaming and NRT service one can define two BLER targets
Strict target for low bit rate up to 64 Kbit/s (EbNoDCHOfPSStr/NRTPriQua, default = 1%)
Less strict target for high bit rate > 64 Kbit/s (EbNoDCHOfPSStr/NRTSecQua, default = 5%)
One can select per bit rate, which of the two BLER targets shall be used
For internal use
11
RN31575EN40GLA0
BLER Target Settings - Example
Consider DL bearer with 256 Kbit/s

Default target 5%
Pedestrian Eb/No = 3.6 dB
Fast vehicle Eb/No = 7.3 dB
Less strict target 10%
Pedestrian Eb/No = 3.4 dB (0.2 dB gain)
Fast vehicle Eb/No = 6.9 dB (0.4 dB gain)
Source
J.J. Olmos, S.Ruiz, Transport Block
Error Rates for UTRA FDD
Downlink with Transmission Diversity
and Turbo Coding
In Proc. IEEE 13th PIMRC 2002, vol.1,
pp 31-35, Sept. 2002.
For internal use
12
RN31575EN40GLA0
BLER Target Settings - Example

Consider load factor for previous example in typical macro cell
Orthogonality = 0.6
Adjacent to own cell interference ratio i = 0.6
Consider activity factor = 1 for NRT service
DL
Eb / N 0
[(1 ) i]
W /R
5% BLER target
15.3% load for pedestrian
35.8% load for fast vehicle
Small capacity gain obtained with less

strict BLER target only especially for slow
moving user;
10% BLER target

14.6% load for pedestrian (0.7% gain)
32.7% load for fast vehicle (3.1% gain)
For internal use
13
RN31575EN40GLA0
Eb/No Settings - Restrictions

For R99 and HSUPA bearers the operator can define Eb/No values as well
Eb/No settings cannot be treated as independent configuration, as Eb/No affects BLER
Eb/No settings offered by NSN applied to initial radio link power only
Afterwards Eb/No adjusted by outer loop power control to follow BLER target
Thus Eb/No settings affect setup and access only, but not load in the network
High initial Eb/No

High initial radio link power high blocking probability
But low initial BLER low risk of drop during initial phase
Low initial Eb/No

Low initial radio link power low blocking probability
But high initial BLER high risk of drop during initial phase
For internal use
14
RN31575EN40GLA0
Eb/No Settings - Role of Service

The initial Eb/No can be defined for the following services
SRB of 3.4 and 13.6 Kbit/s (EbNoDCHOfSRB34/136, default 8 dB)
AMR 12.2 and 5.9 Kbit/s (EbNoDCHOfCSN/BAMR122/59, default 8 dB)
Streaming service
NRT service
In case of streaming and NRT service one can define Eb/No in dependence on
BLER target
Strict target (EbNoDCHOfPSStr/NRTPri, default = 8 dB)
Less strict target (EbNoDCHOfPSStr/NRTSec, default = 6.5 dB)
For the following situations gain factors can be specified

Receive diversity (EbNoDCHRxDiv2/4, default 3 and 4 dB gain for 2 and 4 Rx diversity)
Rate matching (one parameter for each type of service, up to 2 dB gain for effective coding
rate < 1:3)
For internal use
15
RN31575EN40GLA0
Eb/No Settings - Example

Consider initial radio link power in typical macro cell
Total power = 20 Watt
CPICH power = 2 Watt
Ec/Io = -10 dB
Orthogonality = 0.6
R = 256 Kbit/s
R 1
Initial _ RL _ power
E CPICH_power total_power
W c I0
Eb
N0
5% BLER initially (Eb/No = 3.6 and 7.3 dB)

2.1 W power for pedestrian
5.0 W power for fast vehicle
Small power gain obtained with less strict

initial BLER only especially for slow moving
user;
10% BLER initially (Eb/No = 3.4 and 6.9 dB)

2.0 W power for pedestrian (0.1 W gain)
4.6 W load for fast vehicle (0.4 W gain)
For internal use
16
RN31575EN40GLA0
Throughput Based Optimization - Idea

Consider NRT DCH of low utilization
Inactivity timers do not expire in case of frequent transmission of small packets
Huge amount of resources might be reserved unnecessarily
Code of low SF (blocks many codes of high SF)
Channel elements
Iub resources
Throughput based optimization

Downgrade DCH to lower level in this case
Can be enabled for each NRT traffic class individually
Inactive with traffic handling priority 1/2/3
Background
For internal use
17
RN31575EN40GLA0
Throughput Based Optimization - Mechanism

Actual throughput suddenly drops
Consider throughput averaged over sliding window
Short window to react to strong drops
Long window to react to moderate drops
Compare average throughput with thresholds

Downgrade upper threshold (long time to trigger)
Downgrade lower threshold (short time to trigger)
Release threshold (short time to trigger)
Throughput
Actual DCH level
Average
long window
Downgrade upper threshold
Default 2 levels below actual DCH
Average
short window
Actual throughput
Short time
to triggger
For internal use
18
RN31575EN40GLA0
Long time
to triggger
Downgrade upper threshold

Default 3 levels below actual DCH
Release threshold
Default 256 Bit/s

Time
Throughput Based Optimization - Example

Usage of channel elements
Feature OFF
Feature ON
For internal use
19
RN31575EN40GLA0
AMR traffic no
impact, as not
considered by
feature;
PS traffic
about 1/3 less
CE occupied in
the average;

Reservation of ATM resources on Iub
Feature OFF
Feature ON
About 5% less resources reserved on Iub;

For internal use
20
RN31575EN40GLA0

Blocking on Iub
Feature OFF
Feature ON
Due to lower resource reservation about 2/3 less blocking on Iub;

For internal use
21
RN31575EN40GLA0
Throughput Based Optimization Example

Downgrade causes
Feature ON
Feature OFF
Less downgrades required due to
Preemption
Overload control
Dynamic link adaptation
But dramatic increase of downgrades due to TBO
Ping-Pong RB reconfiguration upgrade-downgrade
Define bigger guard timer against consecutive bit
rate adaptations
Enable TBO for certain traffic classes only
For internal use
22
RN31575EN40GLA0
Maximum Radio Link Power Mechanism

Maximum radio link power set automatically by RNC
Three different thresholds based on different criteria
1) Relative to maximum cell power (same threshold for any service)
2) Relative to CPICH power (corrected by SF adjustment in dependence on service)
3) Absolute threshold (for PS services)
Finally lowest threshold is used

the smaller value between the PtxCellMax
and MaxDLPowerCapability
PtxDPCHMax (Default 3 dB)
PtxDLabsMax (Default 37 dBm)

PtxPSstreamAbsMax (Default 37 dBm)
Maximum RL power
PS service
Criterion 3
Maximum RL power
Any service
Criterion 2
Radio Link established or modified

both max. DL Tx power & min. DL Tx
power has to be determined for it.
The average power of transmitted DPDCH
symbols over 1 timeslot must not exceed
maximum DL Tx power, or it can not be
below minimum DL Tx power.
The Power Control Dynamic Range of
BTS is the difference between the max.
and the min. transmit output power of a
code channel.
SF adjustment
Calculated by RNC
Maximum RL power
Criterion 1
PtxPrimaryCPICH (Default 33 dBm)

CPICHtoRefRABOffset (Default 2 dB)
Maximum RL power
Reference service
(Default 12.2 Kbit/s voice)
Criterion 2
For internal use
23
RN31575EN40GLA0
Maximum Radio Link Power SF Adjustment

Comparison of actual service with reference service based on
SF
Eb/No
If several bearers are running simultaneously, all of them are taken into account
SF _ adjustment
EbNo
DCHCCTrCH
DCH
RDCH
EbNoref Rref
Examples
Reference service = voice R = 12.2 Kbit/s, Eb/No = 7 dB
Actual service PS R = 64 Kbit/s, Eb/No = 7 dB
Actual service PS R = 384 Kbit/s, Eb/No = 5 dB
Results
64K PS SF adjustment = (100.7 * 64) / (100.7 * 12.2) = 5.2 = 7.2 dB
Maximum RL power = 33 dBm 2 dB + 7.2 dB = 38.2 dBm
384K PS SF adjustment = (100.5 * 384) / (100.7 * 12.2) = 19.9 = 13.0 dB
Maximum RL power = 33 dBm 2 dB + 13.0 dB = 44.0 dBm
In both cases cutoff due to criterion 3 at 37 dBm

For internal use
24
RN31575EN40GLA0
Maximum Radio Link Power Key Parameters

CPICHtoRefRABOffset
Maximum power of reference service relative to CPICH power
Shifts all services to higher or lower maximum radio link power
Low power for reference service
Low coverage in general
But higher capacity, as no single user can take away too much power
High power for reference service

High coverage in general
But lower capacity, as single user can take away much power
PtxDLAbsMax / PtxPSstreamAbsMax
Maximum power of NRT / RT PS service
Cutoff to avoid, that single user takes too much power
Similar compromise between coverage and capacity needed as for CPICHtoRefRABOffset
For internal use
25
RN31575EN40GLA0
Maximum Radio Link Power Dynamic Link Optimization

Radio link power comes close to maximum power
Reduce bit rate of NRT services by increasing SF
Reduce bit rate of AMR voice service by taking more robust voice codec
128kbps
384kbps
UE
BTS
distance
For internal use
26
RN31575EN40GLA0

BTS measures power of each radio links and sends periodic report to RNC
RNC averages reports over settable sliding window (default 4 reports)
Dynamic link optimization triggered if
Average RL power > Maximum RL power - DLOptimisationPwrOffset
Average RL power
Maximum RL power (Default for PS = 37 dBm)
DLOptimisationPwrOffset (Default = 2 dB)
Triggering of DyLO (Default = 35 dBm)
time
For internal use
27
RN31575EN40GLA0

Dynamic link optimization not performed any more, if
Actual bit rate MinAllowedBitRateDL (Default 8 Kbit/s) OR
Actual bit rate HHoMaxAllowedBitRateDL (Default 32 Kbit/s)
In the latter case HHO will be triggered instead

In case of AMR voice HHO will be triggered, if even with the most robust codec
too much RL power is consumed
HHO area
32 K
128 K
64 K
384 K
UE
BTS
distance
For internal use
28
RN31575EN40GLA0
4Rx Diversity - Idea

2 Rx diversity
Compensation of fast fading on the UL by usage of two receive paths
Space diversity
Horizontal separation (gain depends on azimuth)
Vertical separation
Polarization diversity
Coverage gain on UL about 3 dB (less Eb/No and SIR target needed)
2-3 m
space
diversity
polarization
diversity
For internal use
29
RN31575EN40GLA0
4Rx Diversity - Idea

4 Rx diversity
Enhanced compensation of fast fading on the UL by usage of four
receive paths
Combined space and polarization diversity (two cross-polarized antennas)
Pure space diversity (four single-polarized antennas)
Additional coverage gain against 2 Rx diversity around 1-3 dB (again
less Eb/No and SIR target needed)
Combined space
and polarization
diversity
Pure space
diversity
For internal use
30
RN31575EN40GLA0
4Rx Diversity - Interoperability

4 Rx diversity can be realized together with the following features,
defined by the following implementation phases
Phase 1 MIMO
Phase 2 + Frequency domain equalizer
Phase 3 + HSUPA Interference cancellation receiver
For internal use
31
RN31575EN40GLA0
4Rx Diversity Impact on HW

2 additional
RAKE
antennas
(one in case
dual beam
antenna)
2 times more
fibers
and jumpers
or feeders
At least two additional strong

signals on RAKE input
For internal use
32
RN31575EN40GLA0
4Rx Diversity Example

UE transmission power during drive test
Consider UE transmission power during

drive test
2Rx diversity average UE power 4.4 dBm
4Rx diversity average UE power 1.6 dBm
Gain = 4.4 dBm 1.6 dBm = 2.8 dB
For internal use
33
Source
Antti Tlli and Harri Holma
Comparison of WCDMA UL antenna
solutions with 4Rx branches
In: Proceedings of the CDMA
International Conference (CIC), South
Korea, 25-28 October 2000, pp. 57-61
RN31575EN40GLA0

Coverage enhancement
3dB gain in UL
Area size 1000 km2
Clutter type urban
Output power 40W
Number of sites reduction

could be reached only in UL
limited scenarios
Cell Range [km]

Site-to-Site Distance [sqkm]
Number of sites
2 Rx Diversity
1.341
2.011
857
4 Rx Diversity
1.631
2.447
579
Total Network Cost

1.20
-27%
32% less sites
1.00
0.80
0.60
Include:
Lower number of sites
2x more number of antennas
0.40
0.20
0.00
2Rx Diversity
4Rx Diversity
For internal use
34
RN31575EN40GLA0

Capacity enhancement
Without feature
With feature
Active Users: 53
Mean throughput: 248.7
UL Power Outage: 4.79
Active Users: 68
Mean throughput: 318.5
UL Power Outage: 4.44
Mean HSUPA throughput [kbps]
28%
350
300
250
200
150
100
50
0
For internal use
35
2Rx Diversity
RN31575EN40GLA0
4Rx Diversity
R99 Features
Network load reduction features in RU40:

Fast Cell_PCH Switching
Fast Dormancy Profiling
HSDPA
HSUPA
HSDPA+
HSUPA+
For internal use
36
RN31575EN40GLA0
Fast Cell_PCH Switching 1/2
Faster Cell_PCH to Cell_DCH transition time

Reduced signaling messages (UE RNC)
RNC resources reserved faster
RNC overload handling enhanced
UE
UE
RNC
Cell_PCH
State transition time: 350ms

lowered network signaling load
Improved end user experience
automatic change of transition timers in
dependence of the load
Cell_PCH
RNC
RRC: Cell Update
RRC: Cell Update

RNC processing
RRC Cell Update Confirm

ready to send
RRC: Cell Update Confirm
Waiting for RNC resources

reservation
Cell_FACH/Cell_DCH
RNC processing
RRC: Cell Update Confirm
RNC resources reservation
Cell_FACH/Cell_DCH
With Fast Cell_PCH Switching
Without Fast Cell_PCH Switching

For internal use
37
RN31575EN40GLA0
RRC Cell Update Confirm sent

+
RNC resources reservation
No activity detected
Fast Cell_PCH Switching 2/2

High RNC resources availability
through timer scaling
Exceptional handling for
ul_dl_activation_timer higher than 10s
Cell_DCH
Cell_FACH
Cell_PCH
IDLE_Mode
100
%
90 %
Low
Resources
availability
UL_DL_activation_timer x 0.4
Cell_DCH
75 %
Med
Cell_FACH
Cell_PCH
Resources
Occupation
IDLE_Mode
UL_DL_activation_timer x 0.7
High
Cell_DCH
0%
Cell_FACH
Cell_PCH
RNC resources
utilization
For internal use
38
RN31575EN40GLA0
IDLE_Mode
UL_DL_activation_timer
Fast Dormancy Profiling General Description 1/2

Fast Dormancy:
UE informs network that it would like to go to low battery consumption mode
UE goes to Cell_PCH state instead of idle_mode
Fast Dormancy Profiling:
Identify Legacy Fast Dormancy (LFD) phones which cause unnecessary signaling load
Less signaling load because LFD Phones are prevented from going to Idle_mode
Better network resources utilization (due to shorter inactivity timers
Gain: Signaling load reduction:

On Iub, UU and Iu interfaces
in RNC
Longer UE battery life
SIB1 contains info
about T323
UE detects Fast Dormancy functionality via System

Information Block Type 1 (if T323 supported in RAN)
SCRI signaling Connection Release

Indication;
SCRI: UE requested
PS data session end
SCRI - Signaling Connection Release Indication
For internal use
39
RN31575EN40GLA0
Fast Dormancy Profiling General Description 2/2

Legacy Fast Dormancy (LFD) phone identification:
based on the signaling connection release triggered by the UE
UE sends SCRI to RNC without any cause then this UE is treated as LFD phone
UE is moved to Cell_PCH/URA_PCH state
if UEs do not accept the Cell_PCH/URA_PCH state transition command after SCRI message Idle
IMSI is stored
If the UE creates new RRC connection while the IMSI is still stored UE is LFD phone
LFD phone handling:

RNC uses shorter inactivity/idle timers for LFD and reacts faster than UE:
when this idle timer expires, RNC moves the UE to Cell_PCH/URA_PCH state
aim is to move these UEs to Cell_PCH/URA_PCH state before UE sends connection release
Based on LFD inactivity timer:
go to Cell_PCH/URA_PCH!
Before UE sends SCRI

For internal use
40
RN31575EN40GLA0
Fast Dormancy Profiling LFD phone handling 1/2

shorter inactivity timers are used for moving smartphones & LFD Phones to Cell_PCH state
New shorter inactivity timers
SmartHSPATputAveWin
SmartHSPATimeToTrigger
SmartHSPATputAveWin
SmartHSPATimeToTrigger
Default
Value
1s
0.2s
1s
0.2s
SmartInactivityTimerDCH
0.2s
SmartInactivityTimerFACH
1s
Name
HS-DSCH
Inactivity
E-DCH
Inactivity
DCH
Inactivity
Rel-99 FACH
inactivity
Legacy inactivity timers
MACdflowthroughputAveWin
MACdflowutilTimetoTrigger
EDCHMACdFlowThroughputAveWin
EDCHMACdFlowThroughputTimetoTrigger
InactivityTimerDownlinkDCH
InactivityTimerUplinkDCH
Default
Value
3s
0s
3s
5s
5s
5s
UL_DL_activation_timer
2s
Name
For internal use
41
RN31575EN40GLA0
Fast Dormancy Profiling LFD phone handling 2/2
Stored IMSI gives possibility to faster usage of higher traffic volume thresholds
Higher traffic volume thresholds are used to move smart phones & LFD Phones to Cell_DCH
state
To avoid unnecessary movement to Cell_DCH only for sending keep-alive message

New higher traffic volume thresholds
Name
Rel-99 FACH
SmartTrafVolThrUL
& RACH UL
Rel-99 FACH
SmartTrafVolThrDL
& RACH DL
HS-FACH &
SmartTrafVolThrUL
Rel-99 RACH
Default
Value
Legacy traffic volume thresholds

Name
256 bytes TrafVolThresholdULLow
128 bytes
256 bytes TrafVolThresholdDLLow
128bytes
256 bytes TrafVolThresholdULLow
128 bytes
For internal use
42
RN31575EN40GLA0
Default
Value
Fast Dormancy Profiling Network Performance 1/3

Without
feature
UE has to be moved to Cell_DCH
If UE was in IDLE_Mode then new
connection has to be established
higher amunt of signaling
Cell
Resources
are released
UE in Cell_DCH
Amount of data to send
UE has no more data to

send
Empty SCRI is sent
TrafVolThresholdULLo
w
128bytes
UE in IDLE_Mode
UE in
Cell_DCH
43
UE has to be moved to Cell_FACH
UE in Cell_DCH
With feature
Cell
Resources
are released
For internal use
UE in Cell_PCH
RN31575EN40GLA0
SmartTrafVolThrUL
256bytes
UE in Cell_FACH

Without
feature
UE has no more data to send

UE has been recognised as
LFD Phone - SCRI is not sent
UE has to be moved to Cell_DCH
If UE was in IDLE_Mode then new
connection has to be established
higher amunt of signaling
No PDUs in
MACdflowthroughputAve
Win (3s)
MACdflowThroughputTime
toTrigger start (0s)
UL_DL_activation_
timer start (2s)
Cell
Resources
are released
TrafVolThresholdULLow
128bytes
UE in
Cell_DCH
With feature
No PDUs in
SmartHSPATputAveWi
n(1s)
UE has to be moved to Cell_FACH
SmartHSPATimeToT
rigger start (0.2s)
Cell
Resources
are released
UE in Cell_DCH
44
UE in Cell_PCH or
IDLE_Mode
UE in
Cell_FACH
UE in
Cell_DCH
For internal use
UE in Cell_PCH
RN31575EN40GLA0
SmartTrafVolThrUL
256bytes
UE in Cell_FACH

Benefits:
1
is faster moved from Cell_DCH to Cell_PCH state lower utilization of cell resources and
lower UE power consumption (i.e. SmartHSPATimeToTrigger, SmartInactivityTimerDCH)
is kept in Cell_PCH instead of goes to IDLE_mode less signaling is required for moving to
Cell_FACH or Cell_DCH
higher amount of data could be sent in Cell_FACH/HS-Cell_FACH state (i.e.

SmartTrafVolThrUL threshold)
Value of timers and thresholds can be used for network performance optimisation
Shorter values of timers could be applied if we would like to release cell resources faster it will be useful in case with many smart phones application in network. In other cases it
could caused higher number of RRC States transitions
Value of traffic volume thresholds should allow to send small pieces of data via Cell_FACH
(i.e. Keep-alive messages)
For internal use
45
RN31575EN40GLA0
R99 Features
HSDPA
Fractional DPCH
Dynamic BLER
72 HSPA users per cell

HSPA 128 Users per Cell
HSUPA
HSDPA+
HSUPA+
For internal use
46
RN31575EN40GLA0
Fractional DPCH - Idea

Available since RU20
Mapping of SRB on HS-DSCH, not on associated DCH
DPCH than needed for UL power control only reduced to F-DPCH
Node B
RNC
Iub
For internal use
47
RN31575EN40GLA0
Fractional DPCH - Mechanism

SRB on associated DCH
Full configuration of DPCH needed
Dedicated to single user
SRB on HS-DSCH
No data on DPCH any more
TFCI field not needed any more
TPC used not only for power control, but also SIR measurements
pilot field not needed any more
Can be shared by 10 users by time multiplex
1 Slot = 2/3 ms = 2560 chip

TX OFF
TPC
F-DPCH slot: power control commands only

TX OFF
DPCH slot: full configuration

Data block 1
TFCI
TPC optional
Data block 2
Pilot
For internal use
48
RN31575EN40GLA0
Fractional DPCH - Limitations

Fractional DPCH requires good performance on air interface
CPICH coverage better than CPICHRSCPThreSRBHSDPA (Default -103 dBm)
CPICH quality better than CPICHECNOSRBHSPA (Default -6 dB)
Due to strict quality requirements fractional DPCH available only if

Low DL traffic
Little adjacent cell interference (UE close to BTS)
Normal
DPCH
UE
F-DPCH
BTS
distance
For internal use
49
RN31575EN40GLA0
Fractional DPCH - Limitations

Further restriction if F-DPCH shall be setup in SHO area
Ec/Io of non serving cell must not exceed Ec/Io of serving cell by
HSDPASRBWindow (Default 1 dB)
EC/I0
HSDPASRBWindow
CPICH 1 =
server
CPICH 2 =
non server
F-DPCH setup allowed
Normal DPCH only
For internal use
50
RN31575EN40GLA0
time
Fractional DPCH - DL Power Consumption

Consider radio link power for SRB on associated DCH
Total power = 8 Watt (low DL power, as otherwise Ec/Io = -6 dB not fulfilled)
CPICH power = 2 Watt
Ec/Io = -6 dB
Orthogonality = 0.6
R = 13.6 Kbit/s
Eb/No = 8 dB
RL power = 0.071 W = 18.5 dBm
R 1
Initial _ RL _ power
E CPICH_power total_power
W c I0
Eb
N0
For internal use
51
RN31575EN40GLA0
Fractional DPCH DL Power Consumption static

Consider radio link power for F-DPCH
No power control
Static power set relative to CPICH with PtxFDPCHMax (Default 9 dB)
In SHO area more power allocated according PtxOffsetFDPCHSHO (Default 1 dB)

RL power = 24 / 25 dBm outside / within SHO area
But shared among up to 10 users
Effectively 14 / 15 dBm per user gain of about 3-4 dB per user
PtxPrimaryCPICH (Default 33 dBm)
PtxFDPCHMax (Default 9 dB)
F-DPCH power within SHO area

(Default 25 dBm)
PtxOffsetFDPCHSHO (Default 1 dB)
F-DPCH power outside SHO area

(Default 24 dBm)
For internal use
52
RN31575EN40GLA0
Fractional DPCH Impact of RAN971: HSUPA Downlink

Physical Channel Power Control - dynamic
This feature adjusts the transmit powers according to the required power level at the UE for
the following HSUPA downlink control channels:
E-DCH Absolute Grant Channel (E-AGCH)
E-DCH Relative Grant Channel (E-RGCH)
E-DCH Hybrid ARQ Indicator Channel (E-HICH)
adapts the transmit power of the Fractional Dedicated Physical Channel (F-DPCH)
for each UE
The E-DCH serving BTS adjusts the downlink control channel transmit powers.
The control is achieved with:
1.
Inner loop algorithm, based on HS-DPCCH feedback information (CQI) when F-DPCH
is configured. DL TPC is used in case of non F-DPCH.
2.
Outer loop algorithm, based on Hybrid Automatic Repeat Request (HARQ)

acknowledgements (ACK/NACK), for adjusting the L1 BLER target.
For internal use
53
RN31575EN40GLA0
Fractional DPCH - Code and CE Consumption

Associated DCH (13.6 Kbit/s)
One SF128 per user 72 x SF128 for 72 users 9 codes with SF16 lost
One CE per user 72 CE for 72 users
F-DPCH
One SF256 per 10 users 8 x SF256 for 72 users 1 code with SF16 lost
One CE per 10 users 8 CE for 72 users
But in reality only few users get F-DPCH due to limitation Ec/Io -6 dB !
For internal use
54
RN31575EN40GLA0
72 HSPA Users per Cell - Idea

HSPA cells have high capacity of several Mbit/s
But for RT services often low data rate per user
AMR voice 4.75 - 12.2 Kbit/s
Streaming e.g. 64 Kbit/s
Many users can have HSPA session simultaneously
Feature available since RU20
72 users
72 users
72 users
For internal use
55
RN31575EN40GLA0
72 HSPA Users per Cell - Limitations

Role of scheduler
72 HSPA users per cell requires
Either RU20 dedicated scheduler (full baseband)

Or RU30 scheduler
Otherwise 72 HSPA users per shared scheduler only
Logical and physical connection

72 HSPA users referred to logical connection (MAC-d flow)
Number of users served with packets simultaneously
36 users
Shared scheduler
with 72 users
restricted by MaxNbrOfHSSCCHCodes ( 4)
12 users
24 users
For internal use
56
RN31575EN40GLA0
72 HSPA Users per Cell - HS-SCCH 1/2

72 HSPA cells per user usually combined with code multiplexing
Up to 4 HS-SCCH running simultaneously
Some 0.01 to 0.1 W needed per HS-SCCH in dependence on CQI
total loss of power about 0.1 to 1 W (0.5 to 5 % of capacity of 20 W cell)

Code with SF128 needed per HS-SCCH
maximum of 14 codes for HSDPA
SF16,0
SF16,1
SF 16
SF 32
SF 64
SF 128
SF 256
0
HS-SCCH2
HS-SCCH3
HS-SCCH4
For internal use
57
RN31575EN40GLA0
10
11
12
13
14
15
72 HSPA Users per Cell - HS-SCCH 2/2

The code space of HS-SCCH# 2, 3 and 4 code can be dynamically used for the 15th
HS-PDSCH if not needed for HS-SCCH
HS-SCCH# 2, 3, and 4 are mapped to the same code tree branch as the last HS-DSCH
SF16 code
If this SF16 code branch is not needed for any other channels, the BTS may use it for
HS-DSCH transmissions therefore allowing the full use of the DL HSDPA bandwidth
For internal use
58
RN31575EN40GLA0
72 HSPA Users per Cell - E-RGCH and E-HICH

For each HSUPA user individual E-RGCH and E-HICH signature needed
One channelization code can be shared by 40 signatures, i.e. 20 users
With 72 users 4 codes running simultaneously
By default 22 dBm = 0.158 W needed per E-RGCH and E-HICH
with 4 codes 0.634 W needed for E-RGCH and E-HICH

altogether 1.268 W needed (6.3 % of capacity of 20 W cell)
Code of SF128 needed for E-RGCH/E-HICH
still fits into second tree above SF16
SF16,0
SF16,1
SF 16
SF 32
SF 64
SF 128
SF 256
0
HS-SCCH2
For internal use
59
RN31575EN40GLA0
10
11
12
E-RGCH /
E-HICH2 E-RGCH /
HS-SCCH3
E-HICH3
E-RGCH /
HS-SCCH4
2013 Nokia Solutions and Networks. All rights reserved. E-HICH4
13
14
15
128 HSPA Users per Cell
provides support of high number of always on users on HSPA

creates pre-conditions for support for high number of voice users over HSPA
increased quality of experience for more HSPA end users
nnumber of users in other states remains unchanged
RU40:
128 users
maximum number of HSPA users per cell is 128

(both HSUPA and HSDPA).
the limit of E-RGCH/ E-HICH codes is removed
128 users
128 users
only serving HSUPA users are taken for the limit

(in RU10&RU20 serving and non-serving HSUPA
users are taken to the user limit)
For internal use
60
RN31575EN40GLA0
128 HSPA Users per Cell

Recommended features to achieve maximum number of HSPA users:
RAN971
- HSUPA Downlink Physical Channel Power Control
RAN1201 - Fractional DPCH (F-DPCH)

RAN1644 - Continuous Packet Connectivity (CPC)
RAN1308 - HSUPA Interference Cancellation Receiver (beneficial)
if the CPC is enabled, then the CPC for 128 HSPA Users license key must be On to
have both features effective
For internal use
61
RN31575EN40GLA0
R99 Features
HSDPA
HSUPA
2ms TTI
5.8 Mbit/s
HSDPA+
HSUPA+
For internal use
62
RN31575EN40GLA0
2ms TTI - Idea

Since RU20 HSUPA data channel E-DPDCH can operate on two time scales
10 ms TTI
Re-transmission after 40 ms
Peak data rate of 3.84 Mbit/s supported
2 ms TTI
Re-transmission after 16 ms (i.e. less re-transmission delay)
Peak data rate of 5.76 Mbit/s supported (i.e. higher peak data rate)
E-AGCH
E-RGCH
E-RGCH
E-HICH
E-HICH
Node
B
E-DPDCH
E - DPDCH
2 or 10 ms TTI
E-DPCCH
E-DPCCH
Associated
DCHDCH
associated
For internal use
63
RN31575EN40GLA0
UE
2ms TTI - UE Classes

E- DCH
Category
max.
E-DCH
Codes
min.
SF
2 & 10 ms
max. #. of
max. # of
TTI E-DCH E-DCH Bits* / E-DCH Bits* /
support
10 ms TTI
2 ms TTI
Modulation
Reference
combination
Class
10 ms only
7296
QPSK
0.73 Mbps
10 & 2 ms
14592
2919
QPSK
1.46 Mbps
10 ms only
14592
QPSK
1.46 Mbps
10 & 2 ms
20000
5772
QPSK
2.92 Mbps
10 ms only
20000
QPSK
2.0 Mbps
10 & 2 ms
20000
11484
QPSK
5.76 Mbps
10 & 2 ms
20000
22996
QPSK &
16QAM
11.5 Mbps
For internal use
64
RN31575EN40GLA0
2ms TTI - Limitations

E-DPDCH packet 2 or 10 ms time scale
Layer 1 signaling information always 2 ms time scale
10 ms TTI
Signaling content can be repeated 5 time per E-DPCH packet
Reliable signaling even at cell edge
1
1
E-DPDCH packet
Signaling information
2 ms TTI
Signaling content can be transmitted just once per E-DPCH packet
Reliable signaling at cell centre only
1
E-DPDCH packets
Signaling information
For internal use
65
RN31575EN40GLA0

UE coming from Cell_DCH state
Check of coverage
Path loss must remain below CPICHRSCPThreEDCH2MS (Default 136 dB)
Check includes following corrections
Cable loss (if MHA used)

UE power class P_MAX (if lower than maximum allowed UE power in cell UETxPowerMaxRef)
PtxPrimaryCPICH - CableLoss - measured CPICH RSCP <

CPICHRSCPThreEDCH2MS + MAX(0, UETxPowerMaxRef P_MAX)
With PtxPrimaryCPICH = 33 dBm, CableLoss = 3 dB and UE of high power class
RSCP = -106 dBm needed by default
10 ms TTI
UE
2 ms TTI
UE from Cell_DCH
For internal use
66
RN31575EN40GLA0
BTS

UE coming from Cell_FACH state
Check of quality
CPICH Ec/Io must be better than CPICHECNOThreEDCH2MS (Default -6 dB)
In practise stricter limitation than for user coming from Cell_DCH
10 ms TTI
UE
2 ms TTI
UE from
Cell_DCH
2 ms TTI
UE from
Cell_FACH
BTS
For internal use
67
RN31575EN40GLA0
2ms TTI - Example

Simulation performed by Qualcomm based on 3GPP TR 25.896 specifications
Network assumptions
Network with hexagonal cells of inter-site distance of 1000 m
Users uniformly distributed
Receiver assumptions
Rake receiver and 2Rx diversity at Node B
Rake receiver or equalizer at UE, without or with 2Rx diversity
Voice transmission assumptions

12.2 Kbit/s
VoIP with robust header compression
DTX cycle of 8 TTIs for TTI = 2 ms and of 2 TTIs for TTI = 10 ms
For internal use
68
RN31575EN40GLA0
2ms TTI - Example

Capacity results (UE per cell)
136 UE
95 UE
10 ms TTI
103 UE
106 UE
2 ms TTI
10 ms TTI
No DTX
DTX
(CPC not used)
(CPC used)
For internal use
69
2 ms TTI
RN31575EN40GLA0
Without CPC
about 10%
gain with 2ms
TTI due to
lower retransmission
delay;
With CPC
about 30%
gain with 2ms
TTI mainly due
to DTX;
5.8 Mbit/s - Mechanism

With 2ms TTI maximum HSUPA configuration available
2 codes SF2 + 2 codes SF4
1 code SF2 + 1 code SF4 on each branch of QPSK modulator
According 3GPP than no DPDCH
Thus SRB mapped onto E-DPDCH
Cch,2,1
Cch,4,3
E-DPDCH
(on I- and Q-branch
2SF2 + 2SF4)
Cch,4,2
Cch,4,1
Cch,2,0
Cch,4,0
SF2
SF4
SF8
For internal use
70
RN31575EN40GLA0
5.8 Mbit/s - Load per User

Consider load factor for 5.8 Mbit/s user under different conditions
Macro cell
Micro cell
Pico cell
i = 0.6
i = 0.2
i=0
User profile
L( E DPDCH ) j
1 i
W / Rj
Eb / N 0 j
R = 5.76 Mbit/s
Eb/No about 1.3 dB according NSN EXCEL network planning sheet
Activity factor = 1
Results
Macro cell
Micro cell
Pico cell
L = 1.07
L = 0.80
L = 0.67
> 1 service not available

close to 1 service just available
< 1 service clearly available
For internal use
71
RN31575EN40GLA0
R99 Features
HSDPA
HSUPA
HSDPA+
Flexible RLC
64QAM and MIMO
Dual cell HSDPA
Dual cell HSDPA with MIMO and 64QAM

HS Cell_FACH
CS voice over HSPA
Continuous packet connectivity
HSUPA+
For internal use
72
RN31575EN40GLA0
RLC - Static Handling

Prior to RU20 one IP packet segmented into many
small RLC packets of fixed size
Two options configurable by operator
336 bit RLC PDU (16 bit header + 320 bit user data)
656 bit RLC PDU (16 bit header + 640 bit user data)
Than several RLC packets concatenated into one
HSDPA packet
Number of concatenated RLC packets depends on CQI
Loss of capacity by following overheads
RLC header
Granularity
Example
Actual CQI = 8
Corresponds to HSDPA packet of 792 bit
Can be filled with 2 RLC PDUs of 336 bit = 672 bit
Remaining 792 - 672 = 120 bit remain unused
RNC
Segmentation
Node B
Concatenation /
Padding
MAC-hs Header
For internal use
73
RN31575EN40GLA0
Bad air interface

Good air interface
Padding
RLC - Flexible Handling

With RU20 size of RLC PDU adapted to size of IP packet
Than in dependence on CQI
If low one IP packet segmented into several HSDPA
packets
If high several IP packets concatenated into one
HSDPA packet
Much less loss of capacity

Just one RLC header per IP packet
Much less padding, as most HSDPA packets filled up to
the end with IP content
RNC
Maximum 1500 byte
Node B
Segmentation /
Concatenation
MAC-hs Header
Padding
Example for segmentation

of IP packet
For internal use
74
RN31575EN40GLA0
RNC
Maximum 1500 byte
Maximum 1500 byte
Node B
Segmentation /
Concatenation
MAC-hs Header
Maximum 1500 byte
Maximum 1500 byte
Example for concatenation

of IP packets
For internal use
75
RN31575EN40GLA0
Padding

RLC overhead almost negligible with big HSDPA
packet size (high CQI)
Very high gain especially for small HSDPA packet
size (low CQI) due to much less padding
overhead
50%
45%
Rel. 6 with RLC PDU Size of 336 bits
40%
Rel. 6 with RLC PDU Size of 656 bits
35%
Rel. 7 Flexible RLC
30%
25%
20%
15%
10%
5%
0%
0
100
200
300
400
500
600
700
800
900 1000 1100 1200 1300 1400 1500
HSDPA packet size in byte

For internal use
76
RN31575EN40GLA0
64QAM - Principles
QPSK
2 bits/symbol
16QAM
4 bits/symbol
R5/R6 HSDPA modulation

QPSK and 16QAM
64QAM
6 bits/symbol
R7 HSDPA modulation
QPSK, 16QAM and 64QAM
For internal use
77
RN31575EN40GLA0
64QAM - Principles
HSDPA peak rate up to 21.1 Mbps
UE categories 13,14,17 and 18 supported
Available since RU20

Modulation Coding rate 15 codes
QPSK
16QAM
HSDSCH
category
max. HSDSCH
Codes
min. *
Inter-TTI
interval
13
15
Peak
Rate
QPSK/16QAM/
64QAM
No
17.4 Mbps
No
Modulation
14
15
QPSK/16QAM/
64QAM
17
15
QPSK/16QAM/ 64QAM or
Dual-Stream MIMO
17.4 or 23.4
Mbps
18
15
Dual-Stream MIMO
21.1 or 28
Mbps
For internal use
78
MIMO
support
RN31575EN40GLA0
64QAM
21.1 Mbps
1/4
1.8 Mbps
2/4
3.6 Mbps
3/4
5.4 Mbps
2/4
7.2 Mbps
3/4
10.8 Mbps
4/4
14.4 Mbps
3/4
16.2 Mbps
5/6
18.0 Mbps
4/4
21.6 Mbps
64QAM - CQI Requirements
Good channel conditions required to apply / take benefit of 64QAM CQI 26 !
64QAM requires 10 dB higher SINR than 16QAM
Average CQI typically 20 in the commercial networks
1/6
1/4
2/4
3/4
QPSK
no gain from 64QAM
0 Mbps
79
2/4
RN31575EN40GLA0
3/4
5/6 4/4
CQI > 15
CQI > 25
16QAM
64QAM
some gain from only available

64QAM
with 64QAM
10 Mbps
For internal use
3/4
2/4
14 Mbps
21 Mbps

CQI
TB Size
136
# codes
Modulation
Power Offset
QPSK
176
QPSK
232
QPSK
320
QPSK
376
QPSK
464
QPSK
648
QPSK
792
QPSK
928
QPSK
10
1264
QPSK
11
1488
QPSK
12
1744
QPSK
13
2288
QPSK
Example
14
2592
QPSK
UE of category 13
15
3328
QPSK
3GPP 25.214 Annex Table 7F
For internal use
80
RN31575EN40GLA0

CQI
TB Size
16
3576
17
# codes
Modulation
Power Offset
16-QAM
4200
16-QAM
18
4672
16-QAM
19
5296
16-QAM
20
5896
16-QAM
21
6568
16-QAM
22
7184
16-QAM
23
9736
16-QAM
24
11432
16-QAM
25
14424
10
16-QAM
26
15776
10
64-QAM
27
21768
12
64-QAM
28
26504
13
64-QAM
Example
29
32264
14
64-QAM
UE of category 13
30
32264
14
64-QAM
-2
3GPP 25.214 Annex Table 7F
For internal use
81
RN31575EN40GLA0
64QAM - Throughput
UE Cat.14 (64QAM) Throughput, Flex. RLC, Flat030 channel
20
UE category 14
UE Cat. 10 (ref.)
18
UE Cat. 14
16
Throughput / Mbps
14
UE category 10
12
10
64QAM benefits
starts at 10 Mbps
0
-10
10
40
50
Min SINR of 28 dB
required for 64QAM
For internal use
82
20
30
Average HSDPA SINR / dB
RN31575EN40GLA0
64QAM - Usage
64QAM usage
In macro cell negligible
In micro cell significant
Usage improved, if UE supports Rx diversity
For internal use
83
RN31575EN40GLA0
MIMO - Principles
M transmit antennas and N receive antennas form MxN MIMO system
Huge data stream (input) distributed towards M spatial distributed antennas (M parallel
input bit streams 1..M)
Spatial multiplexing generate parallel virtual data pipes
MIMO uses multi-path effects instead of mitigating them
Input
T1
R1
T2
R2
Tm
MxN
MIMO
system
MIMO
Processor
Rn
For internal use
84
RN31575EN40GLA0
Output
MIMO - Principles
RU20 (3GPP R7) introduces 2x2 MIMO with 2 Tx / 2 Rx
Double transmit on BTS side, 2 receive antennas on UE side
System can operate in dual stream (MIMO) or single (SISO, non-MIMO) mode
MIMO 2x2 enables 28 Mbps peak data rate in HSDPA
28 Mbps peak rate in combination with 16QAM
No simultaneous support of 64QAM and MIMO with RU20, but with RU30
Not possible to enable MIMO and DC-HSDPA in parallel with RU20, but with RU30
UE categories for MIMO support are 15, 16, 17 and 18

WBTS: 2 Tx
antennas
HSDSCH
category
max. HSDSCH
Codes
min. *
Inter-TTI
interval
Modulation
MIMO
support
Peak
Rate
15
15
QPSK/16QAM
Yes
23.4 Mbps
16
15
QPSK/16QAM
Yes
28 Mbps
17
15
Dual-Stream MIMO
17.4 or 23.4
Mbps
18
15
Dual-Stream MIMO
21.1 or 28
Mbps
UE: 2 Rx
antennas
For internal use
85
RN31575EN40GLA0
MIMO - NSN Implementation

When using Spatial Diversity (single stream) only primary TB is sent
Weights w1 and w2 applicable
When using Spatial Multiplexing (dual stream) primary and secondary TB are sent
Weights w1, w2, w3 and w4 applicable
Contributions from both transport blocks sent via both antennas
For internal use
86
RN31575EN40GLA0
MIMO - NSN Implementation

With MIMO two CPICH are required
2nd CPICH orthogonal to first one
2nd CPICH has to operate with same power as first one
UE measures CQI for each CPICH individually
Both values reported via single HS-DPCCH
MIMO offered only, if CQI difference does not exceed mimoDeltaCQIThreshold (hardcoded to 2)
UE consideres sum of both CPICH at both Rx antennas
Should be zero due to orthogonality
But in reality at each Rx antenna non zero amplitude and phase due to multi-path
Preferred weights
w1, w3 and w4 fixed
Only w2 has to be estimated by UE on basis of downgraded orthogonality
w2 reported via HS-DPCCH
For internal use
87
RN31575EN40GLA0
MIMO - Throughput
Urban cell with radius = 400 m
HSDPA power = 30 dBm
Hardly any gain with 2Tx
But about 100% gain with 2x2 MIMO
Source
Christian Mehlfhrer, Sebastian Caban
and Markus Rupp
MIMO HSDPA Throughput Measurement
Results in an Urban Scenario
In: Proceedings of the IEEE, Anchorage,
USA, September 2009
2Tx
2Rx
2x2
2Tx+ 2x2
2x2
4x4
2Rx MIMO MIMO MIMO MIMO
+2Tx +2Rx
For internal use
88
RN31575EN40GLA0
64QAM AND MIMO - Principles

Peak throughput
MIMO alone with 16QAM 2 * 14 Mbps = 28 Mbps
64QAM alone without MIMO 6 / 4 * 14 Mbps = 21 Mbps
MIMO with 64QAM 2 * 21 Mbps = 42 Mpbs
UE categories
MIMO alone Category 15 + 16
64QAM alone Category 13 + 14
64 QAM OR MIMO Category 17 + 18
64 QAM AND MIMO Category 19 + 20
HS- DSCH
category
max. HSDSCH Codes
19
15
20
15
MIMO
support
Peak
Rate
QPSK/16QAM/
64QAM
Yes
35.3 Mbps
QPSK/16QAM/
64QAM
Yes
42.2 Mbps
Modulation
For internal use
89
RN31575EN40GLA0
64QAM AND MIMO - Feature Selection

Selection of MIMO mode and modulation
Both the MIMO mode and the modulation are offered in dependence on the air
interface
Bad conditions Single stream
Good conditions Dual stream
Excellent conditions Dual stream + 64QAM
If both MIMO AND 64QAM is not possible, but either MIMO OR 64QAM, then MIMO is
preferred
Dual stream + 64QAM
Dual stream
Single stream
For internal use
90
RN31575EN40GLA0
64QAM AND MIMO - Throughput

MIMO + 64QAM requires
Very high SINR > 25 dB
Uncorrelated multi-path
components
From Landre et al., realistic performance

of HSDPA MIMO in macro cell
environment, Orange 2009
For internal use
91
RN31575EN40GLA0
Dual Cell HSDPA - Principles
Prior to 3GPP R8 HSDPA channel bandwidth limited to 5 MHz
3GPP R8 allows 2 adjacent channels to be combined effective HSDPA channel

bandwidth of 10 MHz
3GPP R8 dual cell HSDPA (RU20) can be combined with 64QAM but not with MIMO
42 Mbps HSDPA peak rate
3GPP R9 (RU40) allows combination with both 64QAM and MIMO

Basic Approach
Dual Cell Approach
2 UE, each using 5 MHz RF Channel
1 UE, using 2 5 MHz RF Channels
Peak Connection Throughput = 28 Mbps Peak Connection Throughput = 42 Mbps
10 MHz
5 MHz
5 MHz
F1
F2
MIMO (28 Mbps) or

64QAM (21 Mbps)
F1
F2
DC-HSDPA and
64QAM (42 Mbps)
For internal use
92
RN31575EN40GLA0
Dual Cell HSDPA - Principles
Dual cell HSDPA provides greater flexibility to HSDPA Scheduler (can allocated
resources in the frequency domain as well as in the code and time domains)
UE categories for dual cell HSDPA support are 21, 22, 23 and 24
UE on top of ranking list
on both RF carriers

on RF carrier 1
F2
F1
F1
UE1
UEx
HSDSCH
category
max. HSDSCH
Codes
Modulation
MIMO
support
Peak
Rate
21
15
QPSK/16QAM
No
23.4
Mbps
22
15
QPSK/16QAM
No
28 Mbps
23
15
QPSK/16QAM/
64QAM
No
35.3
Mbps
24
15
QPSK/16QAM/
64QAM
No
42.2
Mbps
For internal use
93
UE1
RN31575EN40GLA0
F2

on RF carrier 2
F1
UEx
F2
UE1
Dual Cell HSDPA - Sector Configuration

Cells paired for dual cell HSDPA must obey the following rules
Belong to same sector
Have same Tcell value
Thus belong to same logical cell group
Dual cell HSDPA cells belonging to different sectors must fulfil the following rules
Belong to different logical cell groups
Thus have different Tcell value
SectorID = 3
SectorID = 1
Tcell = 0
Tcell = 6
SectorID = 2
Tcell = 3
RF Carrier 2
SectorID = 3
SectorID = 1
Tcell = 0
RF Carrier 1
Tcell = 6
SectorID = 2
Tcell = 3
For internal use
94
RN31575EN40GLA0
Dual Cell HSDPA - Physical Channel Configuration

Serving cell (primary carrier) provides full set of physical channels
Inner loop power control driven by serving cell by F-DPCH
HARQ ACK/NACK and CQI for both carriers reported to serving cell
Uplink data sent to serving cell
Secondary carrier provides only HS-SCCH and HS-PDSCH

The return channel must be HSUPA
Downlink
Channels
HS-SCCH
HS-PDSCH
F-DPCH
HS-SCCH
HS-PDSCH
Uplink
Channels
E-DPDCH
E-DPCCH
HS-DPCCH
DPCCH
Primary RF Carrier
Serving cell
Secondary RF Carrier
For internal use
95
RN31575EN40GLA0
Dual Cell HSDPA - Packet Scheduling

Scheduling metric calculated for each RF carrier individually
Same schedulers available as for single carrier HSDPA

Instantaneous Transport Block Size TBS generated for each carrier individually by
link adaptation
Average TBS based upon previously allocated TBS in both cells belonging to the
DC-HSDPA cell pair, i.e. the total average throughput allocated to the UE
An UE which is scheduled high throughput in cell 1 will have a reduced scheduling
metric for being allocated resources in cell 2
UE served by both carriers at the same time, if it has highest scheduling metric for
both simultaneously
MetricCell1
TBSCell1
Average TBSCell1Cell2
Shared Scheduler per

DC-HSDPA cell pair
MetricCell2
TBSCell2
Average TBSCell1Cell2
For internal use
96
RN31575EN40GLA0
DC-HSDPA
UE
Dual Cell HSDPA - Combination with MIMO

Peak throughput
Dual cell HSDPA alone 2 * 14 Mbps = 28 Mbps
Dual cell HSDPA with 64QAM 6 / 4 * 28 Mbps = 42 Mbps
Dual cell HSDPA with MIMO 2 * 28 Mbps = 56 Mbps
Dual cell HSDPA with 64QAM + MIMO 2 * 42 Mbps = 84 Mbps
UE categories
Dual cell HSDPA alone Category 21 + 22
Dual cell HSDPA with 64QAM alone Category 23 + 24
Dual cell HSDPA with MIMO Category 25 + 26
Dual cell HSDPA with 64 QAM + MIMO Category 27 + 28
For internal use
97
RN31575EN40GLA0

HS- DSCH
max. HScategory DSCH Codes
19
15
20
15
21
15
22
15
23
15
24
15
25
15
26
15
27
15
28
15
Modulation
QPSK/16QAM/
64QAM
QPSK/16QAM/
64QAM
MIMO
support
DCHSDPA
support
Yes
No
Peak
Rate
35.3 Mbps
42.2 Mbps
Yes
No
QPSK/16QAM
No
Yes
23.4 Mbps
QPSK/16QAM
No
Yes
28 Mbps
No
Yes
35.3 Mbps
No
Yes
42.2 Mbps
QPSK/16QAM
Yes
Yes
46.7 Mbps
QPSK/16QAM
Yes
Yes
56 Mbps
Yes
Yes
70.6 Mbps
Yes
Yes
84.4 Mbps
QPSK/16QAM/
64QAM
QPSK/16QAM/
64QAM
QPSK/16QAM/
64QAM
QPSK/16QAM/
64QAM
For internal use
98
RN31575EN40GLA0
Single cell
Dual cell

With RU30 dual cell HSDPA can be combined with MIMO for NRT services
4 HSDPA packets can be transmitted simultaneously to one UE

ACK/NACK for all of them transmitted to serving cell via single HS-DPCCH
Primary Cell
TBS1
HS-DSCH
TBS2
HS-DPCCH
Other common channels like
E-AGCH, E-RGCH, F-DPCH
HS-SCCH
Other common channels like

E-AGCH, E-RGCH, F-DPCH
UE
HS-SCCH
BTS
Secondary Cell
TBS3
TBS4
HS-DSCH
For internal use
99
RN31575EN40GLA0
Dual Cell HSDPA - Throughput

About 100%
gain of
throughput with
dual cell
HSDPA;
About 50%
additional gain
of throughput
with MIMO;
Small Overhead on HS-DPCCH
S-CPICH needed for MIMO
Huge impact on cell coverage as
compared to normal HSDPA mode (r = 1)
For internal use
100
RN31575EN40GLA0
Gains
With RAN1907 DC HSDPA and MIMO 64QAM single user maximum peak data rate of 84
Mbps can be provided (de facto in RU40)
Dual cell HSDPA
Provides network level capacity gain from 20*% to 100% depending on network load
MIMO
In PedA environment compared to normal 2RX terminals is giving a gain from 20% to 40%
MIMO and Dual Cell
Gains are expected to be mostly additive, resulting to a combined gain of 40% to 140%
*) Percentage values are with respect to Single Carrier HSDPA with 64QAM (21Mbps)
For internal use
101
RN31575EN40GLA0
HS Cell_FACH - Principles
RU20
Very low capacity available in Cell_FACH state only
32 kbps on DL (FACH, S-CCPCH)
16 kbps on UL (RACH, PRACH)
Causes problems in case of applications requiring frequent transmission of small
amount of data
High signaling load due to frequent state transitions
High battery power consumption for UE
Strong occupation of dedicated resources for low total throughput
RU30 - RAN1637
HSDPA available in Cell_FACH state, thus much higher capacity of 1.8 Mbps on DL
UEs downloading small amount of data need not to enter Cell_DCH any more
HSUPA in Cell_FACH NOT available yet
For internal use
102
RN31575EN40GLA0
HS Cell_FACH - Channel Mapping

All logical channels up to now mapped onto FACH now can be mapped onto HSDSCH
Even broadcast and paging information can be transmitted via HS-DSCH (to UEs
in Cell_PCH or URA_PCH)
For internal use
103
RN31575EN40GLA0
HS Cell_FACH - Air Interface Transmission RU30

HS Cell_FACH on DL, but not on UL (RAN1637)
Low UL performance (RACH used)
No ACK/NACK and CQI sending
Blind repetition for HARQ
Default CQI value for link adaptation
Mobility based on cell reselection as usual in Cell_FACH
Example:
4 retransmissions
Original
HS-DPSCH
transmissions
For internal use
104
RN31575EN40GLA0
HS Cell_FACH - Channel Type Selection

Like for R99
One can select for which RRC establishment cause HS Cell_FACH or HS Cell_DCH is
preferred
Transition Cell_FACH to Cell_DCH triggered by high activity, i.e. huge amount of data in DL
RLC buffer
In contradiction to R99
Cell_FACH can be offered, until no resource available in this state any more
Thresholds FachLoadThresholdCCH and PtxThresholdCCH are ignored
For internal use
105
RN31575EN40GLA0
HS Cell_FACH RAN1913 in RU40

Utilizes the 3GPP enhanced Cell_FACH state for the downlink (Rel7) and uplink (Rel8)
More users can be supported in Cell FACH state

Smooth data transmission can be provided for users not requiring large data volumes.
Services for sending frequent but small packets are handled more efficiently.
Fast Cell_PCH to Cell_FACH switch
<100ms (RAN1913)
Reduced signaling load UE <-> BTS & BTS <-> RNC

Code tree occupation reduction
BTS baseband resources saving
High number of smartphones can be supported

Higher throughputs possible on common channels 1.80 Mbps in DL & 1.45 Mbps in UL
For UEs 3GPP Rel. 8 (RAN1913)
For internal use
106
RN31575EN40GLA0
High Speed Cell_FACH in RU40 DL

No feedback information (RAN1637)
RACH channel not used for feedback information

Commissioning parameters:
Number of blind repetitions of MAC-ehs PDUs
in HS Cell_FACH state
Default CQI value for HS Cell_FACH state
For 2 retransmissions max achievable is
1.8Mbps / 2 = 900kbps
With feedback information (RAN1913)
If IE ACK/NACK support on HS-DPCCH ==

TRUE
ACKs and NACKs are sent on HSDPCCH
If IE Measurement Feedback info == TRUE
CQIs are sent on HS-DPCCH
For internal use
107
RN31575EN40GLA0
High Speed Cell_FACH in RU40 UL

E-DCH procedure (RAN1913)
Rel99 UL RACH procedure

AICH
response
AICH
response
AICH
response
Common E-DCH resource assigned

UE specific E-RNTI on E-AGCH
DL
AICH
AICH
10 ms
AICH
10 ms
E-AGCH
UL
PRACH
PRACH
PRACH
Collision
probability
PRACH
Collision
probability
RACH procedure performed before every data block

Possibility of collision during transmission
PRACH
E-DPDCH
E-DPCCH
Collision
probability
RN31575EN40GLA0
E-DPDCH
E-DPCCH
Common E-DCH resources

exclusively used by this
UE
RACH procedure performed once for data block sequence

Possibility of collision only in initial transmissions phase
For internal use
108
E-DPDCH
E-DPCCH
High Speed Cell_FACH in RU40 Channel mapping UL

In the uplink direction, the E-DCH can be used in the Cell_FACH state:
CCCH
DCCH
DTCH
Logical channels
Transport channels
RACH
E-DCH
3GPP Rel8
Physical channels
PRACH
E-DPDCH
For internal use
109
RN31575EN40GLA0
High Speed Cell_FACH in RU40 RNTI

With HS Cell_FACH DL:
Cell_DCH
H-RNTI assigned for HS-DSCH user

E-RNTI assigned for E-DCH user
Up to 128 HSPA users per cell (RU40)
RNTI = Radio Network Temporary

Identifier;
Cell_FACH
H-RNTI assigned for HS-DSCH user

E-RNTI assigned for E-DCH user (RAN1913)
All (active and inactive) users
No practical limitation
Verified values
Up to 1000 HS Cell_FACH users per cell
Up to 1024 HS Cell_FACH users per BTS
Up to 50.000 HS Cell_FACH users per RNC
Active users
Up to 10 HS Cell_FACH users per cell
Up to 160 HS Cell_FACH users per BTS
RRC connected
Up to 800.000 users per RNC in RRC connected state

For internal use
110
RN31575EN40GLA0
CS Voice over HSPA - Principles
Two different voice transmission scenarios are being considered with HSPA
VoIP
UE connects with network as for standard packed data transmission
Connection is established by using web communicators
Hard to establish appropriate charging schemes
CS voice over HSPA
AMR voice frames being carried by HSPA transport channels transparent for the user
[REF. WCDMA for UMTS HSPA Evolution and LTE, HH AT]
Assumed IP Header Compression

For internal use
111
RN31575EN40GLA0
CS Voice over HSPA - Principles
SRB must be mapped to HSPA
Supported RAB combinations:
Speech CS RAB
Speech CS RAB + PS streaming RAB
Speech CS RAB + 1...3 PS interactive / background RABs
Speech CS RAB + PS Streaming RAB + 1...3 PS interactive / background RABs
Codecs supported for CS voice over HSPA
AMR FR set (12.2, 7.95, 5.9, 4.75), AMR HR set (5.9, 4.75), AMR with 12.2 alone
AMR-WB set (12.65, 8.85, 6.6)
Load based AMR selection algorithm not used while CS Voice is mapped on HSPA
Priority class of CS voice over HSPA = 14
Lower than SRB (15)
Higher than streaming 13)
for voice, SRB and

other services
For internal use
112
RN31575EN40GLA0
CS Voice over HSPA - DL Admission Control

New load target for total non controllable traffic PtxTargetTot
Adjusted in dependence on DCH non controllable traffic PtxNCDCH
Adjusted within configurable limits PtxTargetTotMin and PtxTargetTotMax
Limitations
Lower threshold PtxTargetTotMin PtxTarget
Upper threshold PtxTargetTotMax PtxCellMax
Power
PtxCellMax (43 dBm)
HSDPA NRT
PtxNCHSDPA
HSDPA streaming
PtxTargetTotMax (41 dBm)
HSDPA voice + SRB
PtxTargetTotMin (40 dBm)
DCH NRT
PtxTarget (40 dBm)
DCH streaming
DCH voice + SRB
PtxNCDCH
For internal use
113
Common channels
RN31575EN40GLA0
Available
capacity for
total NCT
Available
capacity for
DCH NCT

PtxTargetTot depends on
Actual DCH non controllable traffic PtxNCDCH (e.g. 38/39dBm = 6.3/7.9 W)
Setting of maximum allowed target PtxTargetTotMax (e.g. 41 dBm = 12.6 W)
Setting of classical DCH load target PtxTarget (e.g. 40 dBm = 10 W)
PtxTargetTot = PtxTargetTotMax - PtxNCDCH
PtxTargetTotMax
-1
PtxTarget
Example
PtxNCDCH = 6.3 W PtxTargetTot = 12.6 W 6.3 W (12.6 W / 10 W 1) = 11.0 W = 40.4 dBm
PtxNCDCH = 7.9 W PtxTargetTot = 12.6 W 7.9 W (12.6 W / 10 W 1) = 10.5 W = 40.2 dBm
Conclusions
The higher the DCH non controllable traffic, the lower PtxTargetTot
PtxNCDCH = PtxTarget PtxTargetTot = PtxTarget
no capacity for CS voice over HSPA at all

PtxNCDCH = 0 PtxTargetTot = PtxTargetTotMax
maximum capacity for CS voice over HSPA
For internal use
114
RN31575EN40GLA0

To admit CS voice over HSPA, the following conditions must be fulfilled
Like for DCH voice, RT over NRT can be applied in case of lack of resources
PtxNCDCH + PtxNCHSDPA + Pnew < PtxTargetTot

PtxNCHSDPA + Pnew < PtxMaxHSDPA
The power Pnew needed for the new user is estimated as follows
Pnew = (GBR Activity Factor)
Existing HSDPA Power

Existing Throughput
Activity factor
Initial value set by parameter RRMULDCHActivityFactorCSAMR (Default 50 %)
Than measured on running connection
Example
GBR = 12.2 Kbit/s, activity factor = 0.5, HSDPA power = 6 W, throughput = 1 Mbit/s
Pnew For
= internal
12.2useKbit/s * 0.5 * (6 W / 1000 Kbit/s) = 0.037 W = 16 dBm
115
RN31575EN40GLA0
CS Voice over HSPA - UL Admission Control

Analogue to DL new load target for total non controllable traffic PtxTargetAMR
Adjusted in dependence on DCH non controllable traffic PrxNCDCH
Adjusted within configurable limits PtxTarget and PtxTargetMax
Limitations
Lower threshold given by classical DCH load target PrxTarget
Upper threshold PtxTargetMax PtxMaxTargetBTS
RTWP
PrxMaxTargetBTS (e.g. 6 dB)
HSUPA NRT
HSUPA streaming
PrxNCHSUPA
HSUPA voice + SRB
PtxTargetMax (e.g. 4 dB)
PrxTarget (e.g. 3 dB)
DCH NRT
Available
capacity for
DCH NCT
DCH streaming
PrxNCDCH
116
For internal use
DCH voice + SRB

RN31575EN40GLA0
Available
capacity for
total NCT
PrxNoise (e.g. -106 dBm)

According NSN documentation for PtxTargetAMR complex dependency on
Power situation
Throughput situation
Rearrangement of original NSN formulas gives, however, relationship analogue to DL
PrxTargetAMR = PrxTargetMax - PrxNCDCH
PrxTargetMax
PrxTarget
-1
Actual DCH non controllable traffic PrxNCDCH (e.g. 1/2 dB = 1.26/1.58)

Setting of maximum allowed target PrxTargetMax (e.g. 4 dB = 2.51)
Setting of classical DCH load target PrxTarget (e.g. 3 dB = 2.00)
Example
PrxNCDCH = 1 dB = 1.26 PtxTargetAMR = 2.51 1.26 (2.51 / 2.00 1) = 2.19 = 3.4 dB
PrxNCDCH = 2 dB = 1.58 PtxTargetAMR = 2.51 1.58 (2.51 / 2.00 1) = 2.11 = 3.2 dB
Same conclusions as for DL
For internal use
117
RN31575EN40GLA0

Noise Rise [dB]
PrxTargetMax -102 dBm
PrxTargetMax e.g. 4 dB
PrxTargetAMR -102.8 dBm
PrxTarget -103 dBm
PrxNCDCH -104 dBm
PrxTargetAMR 3.2 dB
PrxTarget e.g. 3 dB
PrxNCDCH e.g. 2 dB
Noise floor e.g. -106 dBm

Load factor () [0..1]
For internal use
118
RN31575EN40GLA0
Continuous Packet Connectivity - Principles
Discontinuous UL DPCCH transmission and reception during UE UL traffic inactivity

(UL DPCCH gating + DRX at BTS)
CQI reporting reduction (switched from periodical to synchronized with DPCCH burst)
Stopping E-DPCCH detection at NodeB during DPCCH inactivity
Discontinuous DL Reception (DRX at UE)
Faster response times
Stop receiving HS-SCCH, E-AGCH and E-RGCH when not needed
Increased number of low activity packet users in CELL_DCH state
Motivation and Benefits
Increased capacity for low data rate applications
Longer battery life
CPC Sub-features:
UL DPCCH Gating (UL DTX)
CQI Reporting reduction
Discontinuous UL Reception (MAC DTX)
Discontinuous DL Reception (DL DRX)
For internal use
119
RN31575EN40GLA0
Continuous Packet Connectivity - Principles

CPC eliminates the requirement for continuous transmission and reception during
periods when data is not transferred
Exploits discontinuities in packet data services
Designed to work with VoIP
Downlink
DRX
Reduced CQI
Reporting
New Uplink DPCCH

Slot Format
Uplink
DRX
HS-SCCH Less
Operation
Uplink DTX
USER GAIN
SYSTEM GAIN
UE Power Saving
Increased talk
time
Reduced delay
for re-starting
data transfer
Potential to keep
more inactive UE
in CELL_DCH
Inactive HSPA UE
require less resource
Increased
Capacity
For internal use
120
RN31575EN40GLA0
Continuous Packet Connectivity - UL Gating
UL Gating (UL DTX) reduces UL control channel (DPCCH) overhead
If no data to sent on E-DPDCH or HS-DPCCH UE switches off UL DPCCH
DPCCH Gating precondition for other CPC sub-features

R99 service
Voice (20ms)
R6 Voice 2ms
(R6 VoIP)
R7 Voice 2ms (R7 VoIP)

UL DPCCH Gating
DPDCH
DPCCH
E-DPDCH
DPCCH
E-DPDCH
DPCCH
For internal use
121
RN31575EN40GLA0
Continuous Packet Connectivity - UL Gating

E-DCH 2ms TTI example: CPCNRT2msTTI
CFN
10ms Radio Frame
10ms Radio Frame
N2msInacThrUEDTXCycl2
RNC; 1, 2, 4, 8, 16, 32, 64, 128, 256; 64 TTIs
10ms Radio Frame
Inactivity Threshold for UE cycle 2

E-DPDCH
Tx, 2ms TTI
no data on E-DPDCH
N2msUEDPCCHburst1
RNC; 1, 2, 5; 1 subframe
DPCCH
pattern
N2msUEDPCCHburst2
RNC; 1, 2, 5; 1 subframe
synch reference
UE_DTX_Cycle_1
UE_DTX_Cycle_2
N2msUEDTXCycle1
RNC; 1, 4, 5, 8, 10, 16, 20; 8 subframes
N2msUEDTXCycle2
RNC; 4, 5, 8, 10, 16, 20, 32, 40,
64, 80, 128, 160; 16 subframes
DPCCH with
E-DCH, 2ms TTI
cycle 1
2ms subframe
For internal use
122
UE_DTX_Cycle_2
cycle 2
CFN = Connection Frame Number

switch to UE cycle 2
Used for any synchronized procedure in UTRAN
Pre/Postambles not shown here
RN31575EN40GLA0
Continuous Packet Connectivity - Reduced CQI Reporting

CQI Reporting Reduction reduces the CQI reporting when
there are no data transmitted on HS-DSCH for a longer
period of time
N2msCQIDTXTimer
RNC; 0, 1, 2, 4, 8, 16, 32, 64, 128,
256, 512, infinity; 64 subframes
CQI_DTX_TIMER
HS-DSCH reception
ACK/NACK
transmission
7.5
slots
Reduced CQI reporting takes

place only if the CQI reporting
pattern defined by the last
HS-DSCH transmission and
CQI cycle overlaps the UL
DPCCH burst of the UE DTX
pattern
CQI_DTX_Priority set to 0
CQI_DTX_Priority set to 1
DPCCH
pattern
UE_DTX_cycle_1 UE_DTX_cycle_1
UE_DTX_cycle_2
UE_DTX_cycle_2
UE_DTX_cycle_2
CQI period 2ms

CQI period 4ms
CQI period 8ms
CQI transmission time defined by CQI period, but not overlapping with DPCCH transmission
no CQI transmission
N2msCQIFeedbackCPC
CQI Transmission
CQI feedback cycle (when CQI reporting not reduced)
For internal use
RNC; 0, 2, 4, 8, 10, 20, 40, 80, 160 ; 10 ms
123
RN31575EN40GLA0
Continuous Packet Connectivity - Discontinuous UL Reception
N2msMACInacThr
RNC; infinity, 1, 2, 4, 8, 16, 32, 64, 128,
256, 512; infinity subframes
DTX
UE can transmit E-DPDCH data only
at predefined time instances
N2msMACDTXCycle
length of MAC DTX Cycle
RNC; infinity, 1, 4, 5, 8, 10, 16, 20; 8 subframes
For internal use
124
RN31575EN40GLA0
Continuous Packet Connectivity - Battery Power Optimization

UE battery power
consumption
optimization for RTT measurements OR

CPC currently not active for UE
No delayed transition, as with Cell_PCH

lowest power consumption
Cell_DCH
No CPC
Cell_FACH
Cell_DCH
With CPC
optimization for battery power consumption AND
UE can NOT power down in Cell_PCH
Strong delay for transition
Cell_PCH
Cell_DCH with CPC better than Cell_FACH

optimization for battery power consumption AND
UE can power down in Cell_PCH
Moderate delay for transition

Cell_DCH with CPC better than Cell_FACH
But worse than Cell_PCH for power consumption
For internal use
125
RN31575EN40GLA0
R99 Features
HSDPA
HSUPA
HSDPA+
HSUPA+
Interference cancellation receiver
Frequency domain equalizer
Flexible RLC in UL
HSUPA 16QAM
Dynamic HSUPA BLER
For internal use
126
RN31575EN40GLA0
Interference Cancellation - Principles

RU20
Users with low level services (usually with 10ms TTI) strongly interfered by
users with high level services (usually with 2ms TTI)
RU30
Interference contribution of 2ms TTI users subtracted from total signal
arriving at BTS before demodulating and decoding the signals of 10ms TTI
users
Less power needed by 10ms TTI users due to cancelled interference of 2ms TTI
users
2ms TTI users less interfered by 10ms TTI users due to lower power
Optionally interference contribution of individual 2ms TTI users subtracted

before demodulating and decoding other 2ms TTI users
For internal use
127
RN31575EN40GLA0
Interference Cancellation - Principles

Types of users
IC users
Users whose interference contribution is cancelled from the total signal

Users mapped on E-DCH with 2ms TTI (usually those with highest power)
Do not get any direct benefit from interference cancellation
Non-IC users
Users for which interference is reduced, as the contribution of the non IC users is cancelled from the total
signal
Remaining users mapped on E-DCH with 2ms TTI (usually such ones with lower power)
All 10ms TTI E-DCH users
All DCH users
RTWP
IC Users = interferers to be
cancelled
Non IC Users = users for which

interference is reduced
For internal use
128
RN31575EN40GLA0
Time
Interference Cancellation - Basic Algorithm

Parallel interference cancellation PIC
Total UL signal received with rake receiver or frequency domain equalizer
Turbo decoding to obtain (strongest) 2 ms TTI E-DCH signals
Decoded data used to reconstruct original 2 ms TTI signals (= interferers for other
users). Reconstruction includes turbo encoding, spreading and modulation
Cancel interference from (strongest) 2 ms TTI user: Reconstructed signals are
summed up and subtracted from the original total antenna signal non-IC users
signal (residual signal)
Individual non-IC user signals demodulated on the residual signal, benefiting from
lower interference level improving cell coverage and capacity
Total UL signal from
antenna
Non-IC users
De-modulate
2ms HSUPA
Re-modulate
2ms HSUPA
IC users
2ms HSUPA
user data
For internal use
129
RN31575EN40GLA0
De-modulate
other
2ms HSUPA
Interference cancelled
Non-IC users signal
(Residual
2013
Nokia Solutionssignal)
and Networks. All rights reserved.
10ms HSUPA
DCH
user data
Interference Cancellation - Basic Algorithm

Benefit
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

Data rate of UE to be cancelled
Radio channel of the UE (multi-path profile, velocity)
RTWP
Residual
RTWP
HSUPA 2
ms
HSUPA 2 ms
HSUPA
10 ms
HSUPA
10 ms
R99 users
R99 users
Noise
Noise
For internal use
130
RN31575EN40GLA0
Interference Cancellation - PIC Pool

PIC pool handling
IC can be enabled only, if a cell belongs to a PIC pool
One pool supports up to 6 cells

3 cells may perform IC simultaneously
One BTS supports up to 4 pools
Basic IC requires 48 channel elements per pool
A cell is assigned to a specific PIC pool by the parameter

AssignedPICPool
f1 f2
Cells in PIC pool

Cells with IC
For internal use
131
RN31575EN40GLA0
Interference Cancellation - PIC Pool

With 2x diversity
Up to 6 cells per PIC pool (6x2 antennas)
Up to 3 of them can perform IC simultaneously (3x2 antennas)
With 4x diversity idea (not supported yet)
Up to 3 cells per PIC pool (3x4 antennas)
Only 1 of them can perform IC simultaneously (1x4 antennas)
2 Rx
f1
4 Rx
For internal use
132
RN31575EN40GLA0
Interference Cancellation - Modified Load Targets

The total traffic is checked against the following thresholds
Total RTWP before IC against PrxMaxOrigTargetBTS (Default 8 dB)
Residual RTWP after IC against PrxMaxTargetBTS (Default 6 dB)
The R99 RT traffic is checked against
PrxTargetOrig before IC (Default 4 dB) With interference cancellation 2dB
higher load target for total traffic,
PrxTarget after IC (Default 4 dB)
8dB corresponding to 84% load instead
of 6dB corresponding to 75% load;
RTWP
PrxMaxOrigTargetBTS
PrxMaxTargetBTS
HSUPA 2
ms
HSUPA 2 ms
HSUPA
10 ms
HSUPA
10 ms
R99 users
R99 users
PrxTargetOrig
PrxTarget
PrxNoise
For internal use
133
RN31575EN40GLA0
Interference Cancellation - Effective Noise Rise

Example
2 Rx diversity
10 users in HSUPA cell
With interference cancellation
user experiences about to 1
dB less noise rise effectively
Interference gain
From Sambhwani et al., UL interference

cancellation in HSPA, Qualcomm 2009
For internal use
134
RN31575EN40GLA0
Interference Cancellation - Throughput

Example
2 Rx diversity
10 users in HSUPA cell
With lower experienced
noise rise about 2 times
more throughput
From Sambhwani et al., UL interference

cancellation in HSPA, Qualcomm 2009
For internal use
135
RN31575EN40GLA0
Rake Receiver - Principles

Handling of multi-path propagation
Identify time delays at which significant energy arrives and allocation of the
rake fingers to those peaks
Track fast changes of phase and amplitude originating from fast fading by
each rake finger
Combine demodulated and phase adjusted symbols across all active fingers
and present them to decoder for further processing
For internal use
136
RN31575EN40GLA0
Rake Receiver - Problems

Problem
With HSUPA very short spreading codes (SF down to 2) introduced
Very sensitive to inter-symbol interference introduced by time delay
Maximum data rate of e.g. 5.8 Mbit/s not achieved, saturation at e.g. 4
Mbit/s even under very good signal-to-noise-ratio conditions
For internal use
137
RN31575EN40GLA0
Frequency Domain Equalizer - Principles

Idea
Reduce inter-symbol interference by combination of
Linear equalization
Fast convolution
Obtain peak data rates closer to the limits of
HSUPA 5.8 Mbit/s (2xSF2 + 2xSF4 with QPSK
HSUPA 11.5 Mbit/s (2xSF2 + 2xSF4 with 16QAM)
For internal use
138
RN31575EN40GLA0

Frequency domain equalizer is a combination of linear equalization and fast
convolution
Linear equalization current and the past values of received signal linearly
weighted by equalizer coefficients and summed up to produce output
Fast convolution filtering of signal not done in time domain, but after FFT by
multiplication in frequency domain (low pass filter)
Reduces effects of inter-symbol-interference arising from users own signal due to
multipath propagation
Applied to users with granted 2xSF2 + 2xSF4 (QPSK or 16-QAM)
Time domain
Frequency domain
FFT
signal
IFFT
pilot
Channel
estimation
MMSE filter
coefficient
calculation
For internal use
139
RN31575EN40GLA0
Despreading
bits
and detection
x(k)
h(k)
After filtering
High frequencies
removed by low
pass
Before
filtering
For internal use
140
RN31575EN40GLA0
Frequency Domain Equalizer - E-DPCCH Boosted Mode

Frequency domain equalizer requires reliable decoding of E-DPCCH
In case of 2xSF2 + 2xSF4 E-DPCCH very strongly interfered by E-DPDCH
Boosted mode
Power of E-DPCCH not related to power of DPCCH
But related to power of E-DPDCH
non-boosted mode
E-DPCCH power goes
parallel tonon-boosted
DPCCHm ode
power
boosted mode
E-DPCCH
power
boosted
mode proportional
to E-DPDCH power
E-DPDCH
E-DPDCH
E-DPDCH
E-DPDCH
E-DPCCH
E-DPCCH
E-DPCCH
DPCCH
DPCCH
DPCCH
DPCCH
low E-TFC
high E-TFC
low E-TFC
high E-TFC
E-DPCCH
For internal use
141
RN31575EN40GLA0
Frequency Domain Equalizer - Throughput

Throughput
CIR
(10%
BLER
after
Data rate vs versus
averageaverage
CIR @ 10%
BLER
after
1st Tx
(Pedfirst
A 3)
transmission) pedestrian fading channel A3
9000
FDE 16QAM boosted
FDE + 16QAM =>

77,8% higher
throughput achievable
8000
7000
FDE QPSK
Tp [kbits]
6000
RAKE QPSK
FDE + QPSK =>

22,2% higher
throughput achievable
5000
4000
FDE enables achieving

higher data rates for users
closer to the antenna
3000
2000
1000
0
-20.0
-15.0
-10.0
-5.0
0.0
CIR @ 10% BLER
5.0
10.0
15.0
For internal use
142
RN31575EN40GLA0
Flexible RLC in UL RU40

Fixed RLC PDU in UL (3GPP Rel-7) is a bottleneck:
HSUPA RLC peak rate is limited due to number of concatenated overheads
RLC PDU size is fixed and independent from the current radio conditions
Flexible RLC PDU in UL (3GPP Rel-8) allows :
RLC PDUs can be as large as IP packet
RLC PDU size reflects radio conditions
HSUPA RLC peak rate is increased
Average network throughput is increased
New functional entities of MAC-i and MAC-is are added to MAC layer to handle new variable
RLC PDUs
Less RLC processing since the number of packets to be processed is reduced
3GPP Rel-8 (NSN RAN1910)
3GPP Rel-7
PDCP
PDCP
Flexible RLC in UL
UE
RLC
RLC
For internal use
143
RN31575EN40GLA0
Flexible RLC in UL Gain 1/3

3GPP Rel-8 (NSN RAN1910)
3GPP Rel-7
TCP/IP
header
TCP/IP
header
TCP/IP Payload
TCP/IP Payload
MTU: 1500 bytes
MTU: 1500 bytes
RLC SDU
RLC SDU
MAC-is/i
headers
RLC
PDUs
MAC-es/e
headers
19 MAC-es/e
headers required
+ optional padding
One MAC-is/i
header required
+ optional padding
19 fixed RLC PDUs

(656 bits each) required
per 1500 bytes IP packet
RLC
PDU
Padding
One RLC PDU is

required per 1500
bytes IP packet
Control data = 0.27% of whole transport block
It corresponds to 93% drop of control data for typical IP packet

size of 1500 bytes
When the transmission errors occur one big RLC PDU needs to
be retransmitted
For internal use
144
RN31575EN40GLA0

The RLC throughput measures user data rate after excluding MAC-i/is headers
and paddings
The gains obtained from the feature are presented in the following table:
E-DCH
Cat.
Max.
TBS
[bits]
PDU size
[bits]
Number
of PDUs
RLC
TBS
[bits]
RLC
payload
[bits]
Overhead
and padding
Max. RLC
throughput
[Mbit/s]
Max. FTP
throughput
[Mbit/s]
Gain
11484
336
34
11424
10880
4.74%
5.440
4.624
22996
656
35
22960
22400
2.44%
11.200
9.520
11484
11480
11480
11448
0.28%
5.724
4.865
5.22%
22996
flexible*
22992
22928
0.28%
11.464
9.744
2.36%
It can be noted that the gain for the RLC peak bit rate is as follows:
E-DCH cat. 8: 5.22% gain
E-DCH cat. 9: 2.36% gain
Those gains are the consequence of the reduced overhead and padding relative to
payload
* - flexible PDU size denotes that there are two PDUs with different sizes
For internal use
145
RN31575EN40GLA0

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
Relative overhead and padding
25%
Length indicator changed
from 7 to 15 bits Flexible
RLC
20%
Fixed RLC PDU
RLC PDU changed

from 336 to 656 bits
Flexible RLC PDU

Relative overhead and
padding is equal to 3.72%
15%
Relative overhead and
padding is equal to 0.27%
10%
5%
0%
0
100
200
300
400
500
600
700
800
900
1000
1100
1200
RLC SDU size [bytes]
For internal use
146
RN31575EN40GLA0
1300
1400
1500
Flexible RLC in UL MAC-i/MAC-is

RNC
UE
RLC
RLC
BTS
MAC-d
MAC-d
MAC-is/i
MAC-i
Uu
MAC-is
Iub
MAC-i together with the E-DCH MAC-is handles E-DCH specific

scheduler handles HSUPA
specific functions:
E-DCH scheduling
E-DCH control
De-multiplexing of MAC-i PDUs
Reading UEs id
HARQ associated procedures
functionality:
Disassembly of MAC-is PDUs
Reordering queue distribution
Reordering of received MAC-is PDUs
Macro diversity selection
Reassembly of segmented MAC-d/c PDUs
CRC error detection (needs RAN1913)
For internal use
147
RN31575EN40GLA0
HSUPA 16QAM
3GPP Rel-7 introduces 16QAM modulation for HSUPA NSN RAN1645: HSUPA 16QAM is an optional feature for the
UE
The 16QAM modulation is supported by HSUPA terminal category 7
HSUPA peak data rate is increased to the maximum theoretical throughput 11.5 Mbit/s
Practical throughput achievable with this feature is limited by radio channel conditions, interference level, allowed noise
rise, and both receiver and transmitter imperfections.
16QAM symbols carry four bits of information allowing a higher peak rate at the cost of a reduction of the Euclidian
distance between adjacent symbols
A better SNR (signal-to-noise ratio) per symbol is required to achieve the same BER (bit error rate)
E- DCH
Category#
max.
E-DCH
Codes
min.
SF
2 & 10 ms
TTI E-DCH
support
max. #. of
E-DCH Bits* / 10
ms TTI
max. # of
E-DCH Bits* / 2
ms TTI
Modulation
Reference
combination
Class
10 ms only
7296
QPSK
0.73 Mbps
10 & 2 ms
14592
2919
QPSK
1.46 Mbps
10 ms only
14592
QPSK
1.46 Mbps
10 & 2 ms
20000
5772
QPSK
2.92 Mbps
10 ms only
20000
QPSK
2.0 Mbps
10 & 2 ms
20000
11484
QPSK
5.76 Mbps
10 & 2
ms
20000
22996
QPSK
&
16QAM
11.5 Mbps
For internal use
148
RN31575EN40GLA0
Catego
ry 7
(Rel.7)
4 SF2
10
msec/
2 msec
20000/
22996
2.0/
11.5;
HSUPA 16QAM Modulation

Eb
Es
SF=2
Cch,2,1
4 symbols
E-DPDCH1
SF=4
Cch,4,1
E-DPDCH3
bed,3
4PAM modulation
mapper
bec
Cch,256,1
E-DPCCH
bed,1
4PAM modulation
mapper
+
4 symbols
PAM Pulse Amplitude

Modulation;
Ec
BPSK modulation
mapper
I+jQ
S
SF=2
Cch,2,1
4 symbols
E-DPDCH2
4PAM modulation
mapper
SF=4
Cch,4,1
4 symbols
E-DPDCH4
bed,4
4PAM modulation
mapper
Cch,256,0
DPCCH
bed,2
bc
BPSK modulation
mapper
For internal use
149
RN31575EN40GLA0
= 16
symbols
=16QAM
HSUPA 16QAM BER over Link Quality
Probability of bit error versus Eb=N0 for M-ary PAM for M = 2; 4, and 8.
For internal use
150
RN31575EN40GLA0
HSUPA 16QAM Impact on Baseband Resources

16 QAM transmitting user requires 2x HSUPA BTS Processing Set License
One 16 QAM transmitting user requires reservation of one Subunit from available BB
capacity
1 subunit
Rel99 CE
Rel99
CE
HSUPA HSUPA16QAM
thr.,
transmitting
users
user
HSUPA
Non
16 QAM HSDPA thr.,
licensed
HSUPA
t-put/ users, HSDPA
cells
capacity
users
Exemplary figure
For internal use
151
NWS Network Engineering / Bartosz Wrobel

RN31575EN40GLA0
Dynamic HSUPA BLER

Dynamic HSUPA BLER (RAN2302) allows the operator to define different BLER targets for:
HSUPA peak rates
HSUPA cell capacity
HSUPA user throughput at cell edge
Improvements:
HSUPA peak rates
HSUPA cell capacity
HSUPA user throughput at the cell edge
HSUPA multi-user cell capacity is expected to improve by up to 20% and HSUPA coverage by up to
2 dB
In RU30 HSUPA BLER target in OLPC in RNC is fixed (10%) regardless of:
radio transmission conditions
traffic nature (Continuous, Bursty , Peak data rates)
E-DCH TTI length (2ms, 10 ms)
For internal use
152
RN31575EN40GLA0
Dynamic HSUPA BLER Functionality

Non Real Time (NRT) HSUPA BLER target is dynamically adapted based on HSUPA user transmission characteristics:
Nature of the UE traffic: Continuous data stream; Bursty traffic; close to Peak data rates;
E-DCH TTI: 2ms TTI, 10 ms TTI;
Number of Retransmissions (ReTx);
Peak throughput (close to BTS)

bursty traffic
2ms TTI Continuous data transmission

(not close to peak t-puts)
1% BLER target* on 1st ReTx*
10% BLER target* on 2nd ReTx*
Bursty data transmission

(not close to peak t-puts, mid cell)
10ms TTI Continuous data transmission

(not close to peak t-puts, cell edge)
Peak throughput
(close to BTS)
continuous data stream 2ms TTI
Peak throughput
(close to BTS)
continuous data stream 10ms TTI
1% BLER target * on 1st ReTx*
*Example values. BLER target and the target number of Retransmissions for Block Error detection are configurable for
each presented UE radio transmission constraints
For internal use
153
RN31575EN40GLA0
Dynamic HSUPA BLER Gain

HSUPA Capacity gain*: ~ 20%
HSUPA Coverage gain*: ~ 2dB
OLPC in RNC enhanced, BLER target optimized for different HSUPA NRT traffic and radio conditions:
Close to BTS: optimizing BLER to get peak data rates
Bursty data transmission not close to peak data rates: optimizing latency
Continuous data transmission not close to peak data rates: optimizing radio coverage and cell
capacity
HSUPA Non-Real Time traffic
2msTTI:
10%BLER on
2nd ReTx*
10ms TTI:
20%BLER on
1st ReTx*
1%BLER on
1st ReTx*
10%BLER on
1st ReTx*
*Example values. BLER target and the target number of Retransmissions for Block Error detection are configurable
*Preliminary gain figures from simulations, not commercially bounding
For internal use
154
RN31575EN40GLA0
Dynamic HSUPA BLER Selection of BLER Target 1/3

UE close to Peak rate (Bursty data or Continuous data).
Yes
BLER target to be used is L1PeakRateBLERTrgtEDCH
Is Data
Peak?
No
after DynHSUPABLERPeakRateRx retransmissions

No
UE has Bursty data transmission (not close to peak rates)

Yes
BLER target to be used is L1BurstDataBLERTrgtEDCH
Is Bursty
Data?
after DynHSUPABLERBurstDataRx retransmissions

No
UE has steady 2ms TTI data transmission (not close to

peak rates)
2ms
E-DCH TTI
BLER target to be used is L1ContBLERTrgtEDCH2 after

DynHSUPABLERContDataRx2 retransmissions
10ms
UE has steady 10ms TTI data transmission (not close to peak rates)
BLER target to be used is L1ContBLERTrgtEDCH10 after
DynHSUPABLERContDataRx10 retransmissions
For internal use
155
RN31575EN40GLA0

Detecting High Throughput (is data Peak?) EDCH Data Rate > Peak Rate threshold
Peak Rate threshold - depending on the current UE transmission constraints i.e.
Bursty data tramsmission, or
Continuous 10ms TTI transmission, or
Continuous 2ms TTI transmission
One of the following data rate thresholds is used by the Dynamic HSUPA BLER algorithm to decide
whether UE is close to Peak data rates,
Peak rate threshold for Bursty data rates (DynHSUPABLERMaxRateThrB), or
Peak rate threshold for Continuous 10ms TTI transmission (DynHSUPABLERMaxRateThrC10), or
Peak rate threshold for Continuous 2ms TTI transmission (DynHSUPABLERMaxRateThrC2)
Detecting Bursty Traffic (is Bursty Data?):

Number of frames per TTI < Bursty Data throughput threshold per TTI (10ms or 2ms)
Bursty traffic condition is based on the number of E-DCH Frame Protocol data frames within a time
window falling below a threshold
The threshold is defined by the DynHSUPABLERThrBurstyTP parameter
The time window is defined by the DynHSUPABLERFrameWinSiz parameter
The value of the threshold is applicable to the 10 ms TTI
The value of the threshold is multiplied by 5 when using the 2 ms TTI
For internal use
156
RN31575EN40GLA0
Dynamic HSUPA BLER algorithm is started after the Averaging Sliding Window for Frame
Measurement is full. Prior to that Dynamic HSUPA BLER algorithm is not used and BLER target for
OLPC is given with L1BurstDataBLERTrgtEDCH* parameter after DynHSUPABLERBurstDataRx
retransmissions
Size of Window for Frame Measurement is configurable via parameter
DynHSUPABLERFrameWinSiz. Within Measurement Window, the Frame Protocol (FP) frames are
counted and the measured average number of FP frames per TTI is compared to threshold
parameter (DynHSUPABLERThrBurstyTP) to decide whether transmission is bursty
Continuous traffic: >10 frames in Window Size
Bursty traffic: <10 frames in Window Size
Single
frame of
10ms
Window Size is 1 second
Window Size is 1 second

Averaging
Window size
< 10 frames in Averaging Window => traffic is Bursty, switch to Bursty BLER target
> 10 frames in Averaging Window => traffic is Continuous switch to Continuous BLER
* L1BurstDataBLERTrgtEDCH (Layer1 Bursty Data BLER target for E-DCH) is a BLER target used when Dynamic HSUPA BLER algorithm is in Bursty
state (not close to Peak Rates)
For internal use
157
RN31575EN40GLA0
R99 Features
HSDPA
HSUPA
HSDPA+
HSUPA+
Mass Event Handler management
Voice Call Prioritization during High Traffic Load
For internal use
158
RN31575EN40GLA0
Mass Event Handler

Mass Event Handler
Only detection of the high load will trigger the following special actions for traffic handling:
Longer TVM pending time if the initial capacity request is rejected.
Temporary maximum bit rate set to minimum, typical 16 kbps, bit rate for UL DCH.
Temporarily limited maximum number of HSUPA users.
Also the following special actions can be triggered for traffic handling:
E-DCH 2 ms TTI prohibition, which is triggered by the defined number of HSUPA users in the cell
CQI feedback cycle increase from 4 to 8, 10, 20 ms, which is triggered by the defined number of
HSDPA users in the cell.
Gain:
Improves the access to the networks during the events, and to decrease the uplink load caused by
the sequential service requests
Introduces an automatic control of the traffic load on high-loaded networks

Offers an automatic tuning of the system to prevent the cell collapses and to improve performance
of the high load cells by decreasing the uplink interference
TVM Traffic Volume Measurements;

For internal use
159
RN31575EN40GLA0
Voice Call Prioritization during High Traffic Load 1/2

Voice Call Prioritization during High Traffic Load (RAN2954)
Improves AMR success rate during the high traffic load by prioritizing the AMR over the
HSDPA SRBs on dedicated traffic channel (DCH)
Utilises prioritised downlink power AC where AMR CS DCH conversational call can be
admitted if (Ptx_nc + Ptx_nc) < (PtxTarget + PtxOffset) if there are simultaneous HSDPA
users in the cell
If AMR user is admitted based on the prioritised downlink power AC, the maximum number
of HDSPA users is started to be restricted
Prioritisation is applicable also to such an RRC connection request that can be rejected
due to downlink power and indicates an establishment cause: Originating Conversational

Call, Terminating Conversational Call or Terminating cause unknown
For internal use
160
RN31575EN40GLA0
Voice Call Prioritization during High Traffic Load 2/2

Ptx_Target_BS
Controllable load
Ptx_NC
Ptx_Target
Ptx_nc Ptx_nc Ptx_target Ptx _ offset

Ptx _ nc Ptx _ nc Ptx_target
Ptx_NC
With RAN2954 AMR accepted

If that situation happens than the maximum number of HDSPA users is started to be
restricted
For internal use
161
RN31575EN40GLA0

05 RN31575EN40GLA0 Capacity Enhancement

Загружено:

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

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

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

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

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

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

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

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

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

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

05 RN31575EN40GLA0 Capacity Enhancement

Загружено:

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

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

3G RANOP RU40

LTE Layering! A new Module Interworking;

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

Nokia Solutions and Networks Academy

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

Load Based AMR Codec Mode Selection

Throughput based optimization

Network load reduction features in RU40

2013 Nokia Solutions and Networks. All rights reserved.

Load Based AMR Codec Mode Selection Idea

For each criterion there is a load indicator having three thresholds

2013 Nokia Solutions and Networks. All rights reserved.

AMR - Role of Load

At least one load indicator exceeds target threshold

New calls start as HR

If no load indicator exceeds underload threshold

New calls start as FR

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

AMR - Role of Load

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

AMR - Selection of SF for HR Calls

AMRSF set relative to maximum allowed RL power determined by AC (default -2 dB)

2013 Nokia Solutions and Networks. All rights reserved.

BLER Target Settings - Idea

Strict BLER target (low BLER)

Less strict BLER target (high BLER)

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

BLER Target Settings - Role of Service

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

BLER Target Settings - Example

Consider DL bearer with 256 Kbit/s

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

BLER Target Settings - Example

Consider activity factor = 1 for NRT service

Small capacity gain obtained with less

10% BLER target

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

Eb/No Settings - Restrictions

High initial Eb/No

Low initial Eb/No

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

Eb/No Settings - Role of Service

For the following situations gain factors can be specified

For internal use

2013 Nokia Solutions and Networks. All rights reserved.

Eb/No Settings - Example

5% BLER initially (Eb/No = 3.6 and 7.3 dB)

Small power gain obtained with less strict

10% BLER initially (Eb/No = 3.4 and 6.9 dB)

2013 Nokia Solutions and Networks. All rights reserved.

Throughput Based Optimization - Idea

Throughput based optimization

For internal use