02 RN3008 RU30 RU30 Feature Overview E01

Soc Classification level

1 © Nokia Siemens Networks

Module 2

RU30 Feature Overview



Agenda

Introduction and overview1) RU20 RECAP

2) RU30 Feature overview

Features enhancing already existing concepts3) HSDPA enhancement

4) HSUPA enhancement

5) Hardware enhancement

Introducing of new concepts6) State machine concepts

7) Mobility concepts

8) Enhanced HSPA concepts

Performance features9) New PM features




Features enhancing already existing concepts

Overview HSDPA128 HSPA users per cell

MIMO AND 64 QAM

Dual cell HSDPA with MIMO AND 64QAM

Dual band HSDPA

Overview HSUPAInter-frequency handover

Flexible RLC on UL

HSUPA 16 QAM 11.5 M

Dual cell HSUPA 23 M

Introduction Hardware4 Rx diversity

Flexi RRH 2 Tx 1800 MHz

Flexi 3 sector RF module 1900 MHz

180 W multi radio remote RF

Features introducing new concepts

New performance measurements



HSDPA - 128 Users per Cell

HSDPA RU20

• 16 users per cell offered by basic package

• > 16 users per cell available by additional licenses

• 48 users per cell


• 72 users per cell (includes also 72 users for HSUPA)

HSUPA RU20

• 20 users per cell offered by basic package

• > 20 users per cell available by additional license


HSPA RU30

• New license option 128 users per cell (both HSDPA and HSUPA)



HSDPA - MIMO and 64QAM

HSDPA RU20

• MIMO available by RAN 1642 OR

• 64QAM available by RAN 1643

• But NOT both simultaneously

HSDPA RU30

• MIMO AND 64QAM simultaneously availably by RAN 1912

RAN1912 RAN1642 RAN1643= +



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. HS-

DSCH CodesModulation

MIMO

support

Peak

Rate

19 15 QPSK/16QAM/ 64QAM

Yes 35.3 Mbps

20 15 QPSK/16QAM/ 64QAM

Yes 42.2 Mbps

HSDPA - MIMO and 64QAM



HSDPA - Dual Cell + 64QAM + MIMO

HSDPA RU20

• Dual cell available by RAN 1906 AND

• 64QAM available by RAN 1643

• But NOT with MIMO (RAN 1642)

HSDPA RU30

• Dual cell AND 64QAM AND MIMO simultaneously availably by RAN 1907

RAN1907 RAN1906 RAN1643= +

RAN1642+



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

HSDPA - Dual Cell + 64QAM + MIMO

HS- DSCH

category

max. HS-

DSCH CodesModulation

MIMO

support

DC-

HSDPA

support

Peak

Rate

25 15 QPSK/16QAM Yes Yes 46.7 Mbps

26 15 QPSK/16QAM Yes Yes 56 Mbps

27 15QPSK/16QAM/

64QAMYes Yes 70.6 Mbps

28 15QPSK/16QAM/

64QAMYes Yes 84.4 Mbps



HSDPA – Dual Band

Dual Cell HSDPA RU20

• Two adjacent carriers under the same frequency band required

HSDPA RU30

• Two carriers under different frequency bands allowed

• Two non adjacent carriers under the same frequency band NOT allowed

F1 F2

F1 F2

Band x

Band x Band y

F1

Band x

F2



Peak throughput

• Dual band HSDPA alone → 2 * 14 Mbps = 28 Mbps

• Dual band HSDPA with 64QAM → 6 / 4 * 28 Mbps = 42 Mbps

UE categories

• Dual band HSDPA alone → Category 21 + 22, 25 + 26

• Dual band HSDPA with 64QAM → Category 23 + 24, 27 + 28

HSDPA – Dual Band



HSUPA - IFHO

RU20

• Inter-frequency HO, i.e. compressed mode, available for HSDPA

• But NOT for HSUPA, i.e. compressed mode requires channel type switch

form E-DCH to DCH

RU30

• Inter-frequency HO, i.e. compressed mode, available for HSUPA also

• No channel type switch from E-DCH to DCH required any more

• Less throughput degradation for user

• Less signaling required (no transition E-DCH to DCH in source cell, and DCH to

E-DCH in target cell any more)

• Faster execution of IFHO (gain of up to 1.5 s)



HSUPA - Flexible RLC

RU20

• Flexible RLC available for HSDPA

• But NOT for HSUPA

RU30

• Flexible RLC available for HSUPA also

• Less overhead due to RLC header

• Less overhead due to padding (granularity of standard RLC packets with 336 or

656 bit)



HSUPA - 16QAM

RU20

• Only QPSK

• Peak data rate of 5.8 Mbps

RU30

• QPSK or 16QAM in dependence on the available

resources and the quality of the air interface

• Peak data rate of 11.5 Mbps



Peak throughput

• QPSK

• 1xSF4 → 3.840 / 4 = 0.96 Mbps

• 2xSF4 → 2 * 0.96 = 1.92 Mbps

• 2xSF2 → 2 * 3.840 / 2 = 3.84 Mbps

• 2xSF2 + 2xSF4 → 3.84 + 1.92 = 5.76 Mbps

• 16QAM

• 2xSF2 + 2xSF4 → 2 * 5.76 = 11.5 Mbps

UE categories

• QPSK

• 1xSF4 → category 1

• 2xSF4 → categories 2 + 3

• 2xSF2 → categories 4 + 5

• 2xSF2 + 2xSF4 → category 6

• 16QAM

• 2xSF2 + 2xSF4 → category 7

HSUPA - 16QAM

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

Modu-

lation

Reference

combination

Class

7 4 2 10 & 2 ms 20000 22996 QPSK & 16QAM

11.5 Mbps



HSUPA - Dual Cell

RU20

• Transmission on single carrier only

• Peak data rate of 5.8 Mbps (QPSK)

RU30

• Transmission on two carriers possible

• Peak data rate of 23 Mbps (16 QAM)



Peak throughput

• Single carrier

• QPSK 5.76 Mbps

• 16 QAM 2 * 5.76 = 11.5 Mbps

• Dual cell

• QPSK 2 * 5.76 = 11.5 Mbps

• 16 QAM 2 * 11.5 = 23 Mbps

UE categories

• Single carrier

• QPSK 5.76 Mbps → category 6

• 16 QAM 11.5 Mbps → category 7

• Dual cell

• QPSK 11.5 Mbps → category 8

• 16 QAM 23 Mbps → category 9

HSUPA - Dual Cell

E- DCH

Category

max.

E-DCH

Codes

min.

SF

2 & 10 ms

TTI E-DCH

support

max. # of

E-DCH Bits* /

2 ms TTI

Modu-

lation

Reference

combination

Class

8 4 2 10 & 2 ms 11484 QPSK 11.5 Mbps

9 4 2 10 & 2 ms 22996 QPSK & 16QAM

23 Mbps



Hardware - 4Rx 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

Combined space

and polarization

diversity

Pure space

diversity



Hardware - Flexi RRH 2 Tx 1800 MHz

• With RU20, the following variants of Flexi RRH 2Tx have been introduced

• 900 MHz

• 2100 MHz

• The new RU30 variant operates in 3GPP band III

• UL: 1710-1785 MHz

• DL: 1805-1880 MHz



Hardware - Flexi 3 Sector RF Module 1900 MHz

• With RU20, the following variants of Flexi 3 sector RF module have been

introduced

• 850 MHz

• 900 MHz

• 1500 MHz

• 1800 MHz

• 1700 MHz UL / 2100 MHz DL

• 2100 MHz

• The new RU30 variant operates in 3GPP band II

• UL: 1710-1785 MHz

• DL: 1805-1880 MHz



Hardware - 180 W Multi Radio Remote RF

• With RU20, up to 60 W are available per sector

• With RU30, up to 180 W are available per sector shared among

WCDMA/LTE and GSM

• Up to 120 W for WCDMA/LTE

• Up to 60 W for GSM

WCDMA or LTE

GSM

60 W60 W 60 W

60 W60 W 60 W

120 W120 W 120 W

RU20 RU30






State machine

HS Cell_FACH

Fast Dormancy

Mobility concepts

HSDPA Serving Cell Enhancements

Multi-band load balancing and blind IFHO

Single radio voice call continuity from LTE

HSPA

Dynamic HSDPA BLER

Dynamic HSUPA BLER

HSUPA DL physical channel power control

HSUPA interference cancellation receiver

Frequency domain equalizer




State Machine - HS Cell_FACH

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

• HSPA available in Cell_FACH state, thus much higher capacity

• 1.8 Mbps on DL (HS-DSCH, HS-PDSCH)

• 1.4 Mbps on UL (E-DCH, E-DPDCH)

• UEs transmitting small amount of data need not to enter Cell_DCH any more



State Machine - Fast Dormancy

Fast Dormancy

• UE requests from network to be shifted to state of low battery power consumption

because data session ended

• UE sends signaling connection release indication, “simulating” this way signaling

connection failure

RU20

• RRC connection is released, i.e. UE shifted to idle state

• RRC connection, RAB and radio bearer have to be re-established, if new data shall be

sent

• High signaling load introduced by UEs frequently transmitting small amount of data

RU30

• RNC tries to shift UE to Cell_PCH, i.e. to keep the RRC connection and the RAB

• No “ping-pong” between release and reestablishment, if new data shall be sent



Mobility Concepts - HSDPA Serving Cell Enhancements

RU20 (standard feature)

• In SHO area HS UE sends periodic measurement reports to RNC

• RNC evaluates reports to decide about serving cell change

• Problems

• High signaling traffic due to periodic reporting

• If F-DPCH used, serving cell change command of RNC might not be decoded by UE, as

SRB on HS-PDSCH less robust than on DPDCH

RU30 (enhanced feature)

• No periodic reporting in SHO area any more, but serving cell change triggered by

event 1D

• Better robustness for SRB on HS-PDSCH

• RNC sends pre-information about potential target cells during active set update already

• Serving cell change commands transmitted both in source and target cell



Mobility Concepts – Layering RU20

DCH cell

DCH cell

Non HSPA

capable UE

HSPA

capable UE

HSDPA cell

Redirection or

handover at:

RRC connection

setup only

DCH cell

HSDPA cell

HSDPA cellConnection setup or

transition FACH to DCH

RAN 502

Directed RRC Connection

Setup for HSDPA Layer

RAN 1011

HSPA Layering for UEs in

Common Channels

RAN 1596

HSPA Capability Based

Handover

Anytime during CELL_DCH

or on HSPA traffic inactivity DCH cell

HSPA cell

HSPA cell

i-HSPA cell

Redirection with HSDPA load balancing

Same / different

band

Same / different

band



Support of more mobility scenarios

• HSPA capable UE with CS RAB in HSDPA cell moved to DCH cell (extension of RAN 502 and RAN 1011)

• Target and source cell load checked prior HSDPA inactivity triggered HO (extension of RAN 1596)

• Load based HO triggered by HSPA traffic overload (extension of RAN140)

Load sharing / balancing between HSPA cells / bands

• Better frequency resource utilization by directing UE to different frequency bands or layers in multi-band

networks

• Supports of service versus band strategy in multi-band networks (e.g. 2.1 GHz and 900 MHz)

More HO trigger

• UE capability

• Service type

• Load

• Distance

More criteria for target cell selection

• UE capability

• Service type

• Frequency band

• Load of target / source cell load

• Distance of UE from source / target cell




• Each carrier and frequency band can be differently prioritised

• Carrier frequency layer priority (preference score) effected by

• Preferred frequency weight: Selection of carrier preferred for configurations on basis of UE capability

and used RAB

• Band weight: Selection of one preferred frequency band on RNC level

• RSCP weight: High / low band preference depending on UE distance from source cell

• Load weight: HSDPA cell or carrier / frequency layer preference based on load balance / overload

• Each factor represented by weight is configurable.

• Candidates for multi-layer load balancing are IF neighbours on layers higher prioritised

then source cell layer, in bands supported by UE

Freq layer priority

(Preference Score)=

Preferred Freq

weight

Freq Band

weight

RSCP

weight

Load

weight+ + +

= = = =

0

or

LaySelWeightPrefLayer

0

or

LaySelWeightBand

0

or

LaySelWeightRSCP

0

or

>=LaySelWeightLoad

Not considered for

fast moving UEs

Not considered for non-

HSPA UEs or other with

CS RAB in DCH cell




Mobility Concepts – ISHO WCDMA / LTE RU20 / RL10

• From WCDMA to LTE

• Only cell re-selection in RRC idle, Cell_PCH or URA_PCH, but NOT in Cell_FACH

• No handover supported in Cell_DCH

• From LTE to WCDMA

• Cell re-selection in RRC idle + EMM registered

• Coverage based redirection in RRC connected (no seaming less mobility, as RAB

released under LTE and re-establishment under WCDMA)

LTEWCDMA

Cell reselection

RRC idle / Cell_PCH / URA_PCH

Cell reselection

RRC idle + EMM registered

Redirection

RRC connected



• From WCDMA to LTE

• No changes in comparison to RU20

• From LTE to WCDMA

• Cell re-selection in RRC idle + EMM registered

• Coverage based intersystem handover in RRC connected

LTEWCDMA

Cell reselection

RRC idle / Cell_PCH / URA_PCH

Cell reselection

RRC idle + EMM registered

Intersystem handover

PS Voce over IP becomes CS AMR

RRC connected

Mobility Concepts – ISHO WCDMA / LTE RU30 / RL20



HSPA - Dynamic BLER Target on DL

RU20

• Non configurable BLER target, independent on the CQI

• 10% for static channel

• 25% for fading channel

RU30

• BLER target configurable, in dependence on

• fading

• CQI

• With lower BLER target under good conditions up to 8 % more throughput can be

achieved



RU20

• Non configurable BLER targets applied by outer loop power control, independent on

the transmission characteristics and the service class

• 10% ideal BLER target

• 16% maximum BLER target

RU30

• BLER targets still not configurable in most cases, but transmission characteristic as

well as service class taken into account

• The following transmission scenarios are considered

• Peaky transmission

• Bursty transmission

• Continuous transmission

• The following service classes are considered

• NRT

• Streaming

• Voice 2ms and 10ms TTI (BLER targets configurable)

• SRB 2ms and 10ms TTI

HSPA - Dynamic BLER Target on UL



HSPA - HSUPA DL CCH Power Control RU20

Static power for E-AGCH, E-RGCH, E-HICH and F-DPCH

• Power of all channels set relative to a reference power

• PChannel = PRef + general offset

• Additional offsets can be applied under the following conditions

• E-DCH in SHO

• 2 ms TTI used (not for F-DPCH)

• Total power budget

• PChannel = PRef + general offset + SHO offset + 2ms TTI offset

• The reference power is fixed relative to the CPICH

• PRef = PCPICH - 8 dB for E-AGCH

• PRef = PCPICH - 14 dB for E-RGCH

• PRef = PCPICH - 14 dB for E-HICH

• PRef = PCPICH - 9 dB default for F-DPCH



Dynamic power for E-AGCH, E-RGCH, E-HICH and F-DPCH

• Reference power not fixed anymore, but adjusted by a similar way as that of the HS-

SCCH

• DL quality taken into account by CQI

• Less power needed under good conditions

• More power available for user data

HSPA - HSUPA DL CCH Power Control RU30



HSPA - HSUPA Interference Cancellation Receiver

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



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

Time

IC Users = interferers to be cancelled

Non IC Users = users for which

interference is reduced

HSPA - HSUPA Interference Cancellation Receiver



HSPA - Frequency Domain Equalizer

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

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



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)

HSPA - Frequency Domain Equalizer

x(k) h(k)

Before filtering After filtering

High frequencies

removed by low pass







Periodic measurements

Automatic object list update in RNC measurements

End user experienced throughput

Bandwidth utilization class counters for IP and Ethernet



Periodic Measurements

UE measurements

• RU20 provides reporting only in case of certain events, i.e. in SHO or HHO area

• RU30 provides periodic reporting like in GSM, independent from the situation on the air interface

• The following properties already known from RU20 can be reported periodically for HSPA calls

(not R99 ones)

• EC/I0 (any visible cell)

• RSCP (any visible cell)

• UE power

• The following new properties introduced by RU30 can be reported periodically for any call

• Rx-Tx time difference (active cells only)

RNC

UE measurements: - CPICH Ec/No - CPICH RSCP - UE Tx Power - UE Rx-Tx

500m

s

500m

s

500m

s

500m

s



BTS measurements

• According RU20 reporting according slow cycle = 10 * radio resource indication period, if there is

no event

• Reporting according fast cycle = radio resource indication period, in case of high air interface

load or strong change of load

• RU30 provides periodic reporting, independent from the load situation

• The following properties already known from RU20 can be reported

• Transmitted carrier power and R99 power (per cell)

• Received total wideband power (per cell)

• Radio link power (per link)

• The following new properties introduced by RU30 can be reported also

• Round trip time (per link)BTS measurements: - DL RL power - UL RTWP- DL Total Carrier Power - DL R99 power- RTT

RNC500m

s

500m

s

500m

s

500m

s

Periodic Measurements



• If the transport network is modified, the list of objects handled by the following

measurements is updated automatically, no manual update required anymore

• RNC transport measurements

• RNC hardware measurement

RNC transport / HW measurements

RU30

ZT2 command group

MML

RNW Measurement

Management

Start measurements with “all objects”

option to monitor all objects

Automatic Object List Update in RNC Measurements



End User Experienced Throughput

RU20

• Information about throughput available per scheduling priority indicator, i.e. per

service class

Counters M5002C5..C20 consider throughput for SPI 0..15

• Information about number of users available per cell only, not per service class

Counters M1000C167..C175, M1000C240..C247, M1000C314..C317 and

M1000C390..C393 consider time the total number of HSDPA users is within certain

interval

• One cannot determine the throughput experienced by users with a specific service

class

RU30

• New counters considering the number of HSDPA users per service class

• One can determine the throughput experienced by users with specific service class



Bandwidth Utilization Class Counters for IP and Ethernet

• For each IP route, RU20 counters M568C0 to M568C9 give information about

• IP datagram volume sent and received

• Configured bandwidth

• Minimum, average and maximum bandwidth reserved by IP CAC

• Minimum, average and maximum number of IP/UDP connections reserved by IP CAC

• New RU30 counters M568C10 to M568C17 give information about

• Utilization → clearer picture about congestion situations

• Bandwidth used for shaping

• Outgoing and incoming peak throughput

RNC

IP data volume

IP bandwidthIP/UDP connections

IP utilization

Traffic as % of configured bandwidth

44 © Nokia Siemens Networks RU30 for Network Planners 2011

Thank You !

02 RN3008 RU30 RU30 Feature Overview E01

Documents