ru30 radio features

5/21/2018 RU30 Radio Features

1/229

Soc Classification level

1 Nokia Siemens Networks Presentation / Author / Date

RU30 Delta Radio Planning and

Dimensioning TrainingModule 1 Features

Version 1.0 (10.2.2010)


2/229



Related materials

3G Radio Network Planning Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Planning_Guidelines

Mobility planning and optimisation (+ Different Project related material )https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/Multilayer_Planning_Guidelines

RU30 Operating documentation in NOLS

NE WCDMA materialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448

(Right click and Open Hyperlink)
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Planning_Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/Multilayer_Planning_Guidelineshttps://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/allneds.do?PId=urn:nsn.com:mxpdm:133-000858&RId=&CId=&FId=&Poff=&Roff=&Coff=&Foff=https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/allneds.do?PId=urn:nsn.com:mxpdm:133-000858&RId=&CId=&FId=&Poff=&Roff=&Coff=&Foff=https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/Multilayer_Planning_Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/Multilayer_Planning_Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/Multilayer_Planning_Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Planning_Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Planning_Guidelineshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Planning_Guidelines


3/229



RU30 Delta Training Agenda Day 1-2 Features

HSPA+ features in RU30 MIMO 42Mbps UE

DC-HSDPA with MIMO 84MbpsEP UE

Dual-Band HSDPA 42MbpsEPUE HSUPA 16QAMEPUE Flexible RLC in ULEPUE DC-HSUPA 23 MbpsEPUE

Other RU30 features

HSUPA Interference Cancellation Receiver Frequency Domain Equalizer (4-way RX Diversity) HSUPA Inter-frequency Handover UE Multi-Band Load Balancing HSPA 128 users per cell

HSUPA Downlink Physical Channel Power Control Dynamic HSDPA BLEREP Dynamic HSUPA BLEREP High Speed Cell_FACHEPUE (Fast dormancy & Fast dormancy profilingEP) (SRVCC from LTEEPUE )

Day 1

Day 2

EP- RU30 EP releasesUE- UE support req.


4/229



Content

HSPA+ features in RU30 MIMO 42Mbps

DC-HSDPA with MIMO 84Mbps

Dual-Band HSDPA 42Mbps

HSUPA 16QAM

Flexible RLC in UL DC-HSUPA 23 Mbps

Other RU30 features


5/229



HSPA+

HSPA enhancements in 3GPP Release 7 and beyond

User data rates

Voice capacity

Battery life

Latency Network throughput

Flat architecture (iHSPA)


6/229



HSPA+ features

3GPP Features

Release 7 Continuous packet connectivity

F-DPCH (Rel 7 version)HSDPA 64-QAM

MIMO (16-QAM)

Flexible RLC (DL)

CS Voice over HSPA

Flat architecture (iHSPA)

Release 8 Flexible RLC (UL)MIMO & HSDPA 64-QAM

DC-HSUPADC-HSDPA (64-QAM)

Release 9 MIMO & DC-HSDPA (64-QAM)

DC-HSDPA Multi-bandHSPA (> 2 carriers?)

Release 10


7/229



Multicarrier HSPA Evolution in Release 9/10

1 x 5 MHz

Uplink Downlink

1 x 5 MHz

4 x 5 MHz

Uplink Downlink

4 x 5 MHz

HSPA release 7 UE can receive and transmit only on 1 frequency

even if the operator has total 3-4 frequencies

HSPA release 8 brought dual cell HSDPA

Further HSPA releases will bring multicarrier HSDPA and HSUPAwhich allows UE to take full benefit of operators spectrum


8/229



HSPA Data Rate Evolution

14 Mbps

21-28Mbps

3GPP R53GPP R6

3GPP R7

42 Mbps

84 Mbps

3GPP R83GPP R9

168 Mbps

3GPP R10+

14 Mbps

0.4 Mbps5.8 Mbps

11 Mbps11 Mbps 23 Mbps 54 Mbps

DC-HSDPA

MIMO64QAM

DC-HSDPA+ MIMO

4-carrierHSDPA

DC-HSUPA4-carrierHSUPA

16QAM

64QAM orMIMO16QAM

HSPA has data rate evolution beyond 100 Mbps

RU30


9/229



HSPA and LTE Spectral Efficiency Evolution

Evolution of HSPA efficiency

0.55

1.06 1.11

1.311.44 1.52

1.74

0.33 0.33 0.33

0.530.65 0.65

0.79

0.0

0.2

0.4

0.6

0.8

1.0

1.2

1.4

1.6

1.8

2.0

HSPAR6

HSPAR6+UE

equa

lizer

HSPAR7

64QAM

HSPAR8DC-

HSDPA+3i,UL

IC

HSPAR9DC-

HSDPA+MIMO,

ULprogress

ive

PC

HSPAR10QC-

HSDPA+MIMO

LTER8

bps/Hz/cell

Downlink

Uplink

Today RU20

RU20/30

RU30+


10/229



Content

HSPA+ features in RU30 MIMO 42Mbps



DC-HSUPA 23 Mbps

HSUPA 16QAM Flexible RLC in UL

Other RU30 features


11/229



Background

2x2 MIMO uses two parallel streams to transfer HSDPA datato the UE 2x2 MIMO with 16QAM was introduced in RU20 by the RAN1642

MIMO (28 Mbps) feature

The RU30 RAN1912 feature enables simultaneous operation

of 2x2 MIMO and 64QAM Using 64QAM on top of MIMO increases the peak rate to 42

Mbps (28 Mbps x 1.5)

16QAM transfers 4 bits per modulation symbol

64QAM transfers 6 bits per modulation symbol

The simultaneous operation of 2x2 MIMO and 64QAM isspecified by the release 8 version of the 3GPP specifications

MIMO 42 Mbps


12/229



RequirementsMIMO 42 Mbps

UE Requirements

Release 8, or newer

HSDPA Category 19 or 20

Network Hardware Requirements

Flexi Node B must have release 2 system module. RF module can berelease 1 but cannot be mixed release 1 and release 2 (release 1 single

RF module cannot be used for a MIMO cell)

UltraSite Node B must have EUBB, WTRB or WTRD

Double PA units and antenna lines

RNC must have CDSP-DH cards

Feature Requirements

The following features must be enabled:

Flexible RLC, Fractional DPCH, MIMO 28 Mbps, HSDPA 64QAM


13/229



Enabling the Feature (I)

MIMOWith64QAMUsage

(WCEL)

Name Range Description

0 (MIMO with64QAM disabled),

1 (MIMO with

64QAM enabled)

Default

The MIMOWith64QAMUsageparameter must be set to enabled

This parameter does not require object locking for modification

Parameter defines whether MIMO and64QAM modulation can be usedsimultaneously for the same UE. Bothfeatures must also be separatelyenabled in the cell in order to make

simultaneous usage possible for the UE.

0 (MIMO with64QAM disabled)

MIMO 42 Mbps


14/229



Node B Commissioning

Similar to RU20, the Node B commissioning parameter MIMOTypeshould beconfigured with a value of 1 (2xDL MIMO)

MIMOType

(LCEL)


0 (Single TX),

1 (2xDL MIMO)

Default

Parameter is used to select the static DL mimo type.Parameter value is defined first time when local cell iscreated. When a cell is created for a single TX

transmission, parameter value is 0. For a MIMO enabledcell, parameter value shall be 1 (2 x TX transmission).

0 (Single TX)

Supported Node B configurations are 1+1+1, 2+2+2 (and 3+3+3 where only onelayer has MIMO enabled)

Virtual Antenna Mapping (VAM) is supported for balancing the utilisation of powerampliers

MIMO 42 Mbps


15/229



UE Categories

64QAM with MIMOUE categories

introduced withinrelease 8 of the 3GPP

specifications

HSDPA UE categories19 and 20 support

64QAM with MIMO Maximum transport

block size is

supported by UE

category 20

Maximum transportblock size of 42192

bits corresponds to a

throughput of 42.192

Mbps when using dual

stream transmission

Extracted from Rel. 8 version of 3GPP TS 25.306

MIMO 42 Mbps

MIMO 42 Mb


16/229



Allocating MIMO with 64QAM

64QAM is allocated with MIMO whenever possible

Switching can occur when conditions change, i.e. when itbecomes possible to support MIMO with 64QAM, or when it isno longer possible to support MIMO with 64QAM

The conditions required to support MIMO with 64QAM are:

it must be possible to support MIMO it must be possible to support HSDPA 64QAM

The WCEL MIMOWith64QAMUsageparameter must be set to enabled

The BTS and UE must support simultaneous use of MIMO and 64QAM

If MIMO with 64QAM is not possible but MIMO without64QAM, or 64QAM without MIMO is possible, MIMO shall bepreferred

MIMO 42 Mbps

MIMO 42 Mb


17/229



HSPA Configurations

MIMO with 64QAM is supported for the following RB and SRB

mappings: RB mapped onto HS-DSCH in DL and E-DCH in UL

AND

SRB mapped onto

HS-DSCH in DL and E-DCH in UL (F-DPCH and E-DCH 2ms or 10 ms TTI)

OR

DCH in DL and E-DCH in UL (E-DCH 2 ms TTI)

MIMO 42 Mbps

MIMO 42 Mb


18/229



Serving Cell Change

MIMO with 64QAM is maintained during serving cell changes (SCC)

MIMO with 64QAM does not impact the triggering of the SCC procedure, i.e.

existing mechanisms are used The availability of MIMO with 64QAM is checked at the target cell when the SCC

is initiated

If the target cell does not support MIMO with 64QAM, the SCC is performedwithout simultaneous MIMO and 64QAM, i.e. MIMO with 64QAM shall bedeactivated during the SCC

If MIMO with 64QAM cannot be used in the target cell, MIMO without 64QAM or64QAM without MIMO is used if possible. MIMO is preferred to 64QAM

MIMO 42 Mbps

Iur

MIMO with 64QAM is not supported over the Iur interface

The Serving RNC does not configure MIMO with or without 64QAM if there is oneor more radio links over the Iur

MIMO with 64QAM can be configured immediately after an SRNS relocation

MIMO 42 Mb


19/229



MIMO with 64QAM Throughputs (I)

Physical Layer (based upon Physical Channel capability)

Chip Rate = 3.84 Mcps

Spreading Factor = 16

=> Symbol Rate = 240 ksps

Number of HS-PDSCH codes = 15

=> Aggregate Symbol Rate per RF Carrier = 3.6 Msps

Number of bits per Symbol = 6=> Aggregate Bit Rate = 21.6 Mbps

Number of Parallel Streams of Data = 2

=> Bit Rate = 43.2 Mbps (peak)

Physical Layer (based upon UE maximum transport block size) Category 20 maximum transport block size = 42 192 bits

Transmission Time Interval = 2 ms

=> Bit Rate per transport block = 21.096 Mbps

Number of Transport Blocks = 2

=> Bit Rate = 42.192 Mps (peak) coding rate of 0.98

MIMO 42 Mbps

64-QAM

MIMO

MIMO 42 Mb


20/229



MIMO with 64QAM Throughputs (II)

RLC Layer (based upon maximum transport block size payload)

Maximum transport block size payload = 42192[24 + (7 16)] = 42056 bits

RLC header size per transport block = 8 16 = 128 bits

=> RLC payload = 2 (42056128) = 83856 bits


=> Peak instantaneous bit rate = 41.928 Mbps

MAC-ehs re-transmission rate = 10 %

RLC re-transmissions rate = 1 %

=> Net Bit Rate = 37.35 Mbps

Application Layer (based upon TCP/IP protocol stack)

IP header size = 20 bytes

TCP header size = 36 bytes

MTU Size = 1500 bytes

=> TCP/IP overhead = 3.7 %

=> Application throughput = 35.98 Mbps

MIMO 42 Mbps

MAC-ehs header sizebased upon maximum RLCPDU payload of 5568 bits

MIMO 42 Mb


21/229



Performance

Usage of 64-QAM depends on channel quality High CQI

Good MIMO channel separation

Quality of secondary stream always lower (see example next

slide)

MIMO 42 Mbps

REF: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA Radio Test&Trials
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trials


22/229



Example: MIMO 16-QAM drive (64-QAM UE not available)Modulation for both streams

MIMO_20_drive - Secondary stream modulation

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

1 12 23 34 45 56 67 78 89 100 111 122 133 144 155 166 177 188 199 210 221 232 243 254 265 276 287

MIMO n/a %

MIMO QPSK%

MIMO 16QAM %

MIMO 64QAM %

MIMO_20_drive - M odulation vs. RSCP

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

1 9 17 25 33 41 49 57 65 73 81 89 97 105 113 121 129 137 145 153 161 169 177 185 193 201 209 217 225 233 241 249

Modulation%

-110.0

-100.0

-90.0

-80.0

-70.0

-60.0

-50.0

-40.0

-30.0

RSCP

n/a %

QPSK%

16QAM %

64QAM %

RSCP

Main stream

modulationalong the drive

Secondary Streammodulation along the

drive

16QAM

QPSK

p p _ _

MIMO 42 Mbps


23/229



Counters

The RRC Signalling counter table includes the counters shown below

M1006C245 RB_CONFIG_MIMO_SUCCM1006C246 RB_CONFIG_MIMO_FAIL

M1006C247 RB_CONFIG_64QAM_SUCC

M1006C248 RB_CONFIG_64QAM_FAIL

These counters are incremented independently for MIMO and 64QAM

Both the MIMO and 64QAM counters are incremented together when UE areallocated MIMO with 64QAM connections

The counters are incremented for the WCEL object that is the primary servingcell after reconfiguration

MIMO 42 Mbps


24/229



Content

HSPA+ features in RU30

MIMO 42Mbps



HSUPA 16QAM

Flexible RLC in UL DC-HSUPA 23 Mbps

Other RU30 features

DB DC HSDPA


25/229



Background (I)

RU30 introduces Dual Band Dual Cell HSDPA (DB-DC-HSDPA) for whichthe RF carriers can be in in different operating bands (like 900 & 2100)

Dual Cell HSDPA (DC-HSDPA) requires 3.8 to 5.2 MHz carrier separation The general concepts for DB-DC-HSDPA are the same as those for DC-

HSDPA

DB-DC-HSDPA

5 MHz

F1

MIMO + 64QAM

10 MHz

UE using 5 MHz RF ChannelPeak Throughput = 42 Mbps

UE using 25 MHz RF ChannelsPeak Throughput = 84 Mbps

F1 F2

Dual Cel l Appro achBas ic Approach

DC-HSDPA + MIMO + 64QAM

5 MHz

UE using 25 MHz RF ChannelsPeak Throughput = 42 Mbps

F1 F2

Dual Band A pproach

DB-DC-HSDPA + 64QAM

5 MHz

Band x Band yBand x Band x

DB DC HSDPA


26/229



Background (II)

DB-DC-HSDPA allows the benefits of DC-HSDPA to be achieved when a

contiguous 10 MHz frequency allocation is not available The maximum peak rate for DB-DC-HSDPA is 42 Mbps when 64QAM is enabled

and 15 codes are available on both RF carriers

3GPP Release 9 limits the feature so the two RF carriers cannot be non-adjacentcarriers within the same band

The uplink is restricted to Single Carrier HSUPA (SC-HSUPA)

MIMO is not supported simultaneously with DB-DC-HSDPA for an individual UE

DB-DC-HSDPA is not supported across the Iur-interface

BTS utilises proportional fair scheduling and optimizes the sector coverage andcapacity by favoring low frequency band for cell edge UEs and high frequencyband for UEs close to the BTS

This allows DB-DC-HSDPA to combine the gain of normal DC-HSDPA schedulingand the benefits of low frequency band for far away users

DB-DC-HSDPA

Might not be valid

DB DC HSDPA


27/229



Supported Operating Bands

The following band combinations are supported by DB-DC-HSDPA

DC-HSUPA is not supported in combination with DB-DC-HSDPA

DB-DC-HSDPA

DB-DC-HSDPAConfiguration

Uplink Band Downlink Band

1 I or VIII I and VIII

2 II or IV II and IV

3 I or V I and V

DB DC HSDPA


28/229



Revision

The serving cell provides the full set of physical channels

Inner loop power control is driven by the serving cell

HARQ ACK/NACK and CQI are reported to the serving cell Uplink data is sent to the serving cell

The secondary serving cell provides only the downlink HS-SCCH and HS-PDSCH

The return channel must be HSUPA

HS-SCCH

HS-SCCHHS-PDSCH

HS-PDSCHHS-DPCCHDPCCH

F-DPCH

E-DPDCHE-DPCCH

Downlink

Channels

Uplink

Channels

Primary RF Carrier

Serving cell

Secondary RF Carrier

Secondary Serving cell

DB-DC-HSDPA

DB DC HSDPA


29/229



Requirements

UE Requirements

HSDPA Category 21 to 28Network Hardware Requirements

Flexi Node B must have release 2 system module

UltraSite Node B must have EUBB

CDSP-DH card in RNC (RAN1226 HSPA Peak Rate Upgrade for RNC196and RCN450)


RAN1906 Dual Cell HSDPA 42 Mbps

Achieving 42 Mbps requires the HSDPA 64QAM feature although this is not amandatory requirement to use DB-DC-HSDPA

Multi-Band Load Balancing provides layering support for DB-DC-HSDPA butis not mandatory

DB-DC-HSDPA

DB DC HSDPA


30/229




DBandHSDPAEnabled

(WCEL)


0 (disabled),

1 (enabled)

Default

The DBandHSDPAEnabledparameter must be set to enabled

This parameter requires object locking for modification

Parameter enables / disables the Dual Band DualCell HSDPA (DB-DC-HSDPA) usage in the cell.Dual Cell HSDPA (DC-HSDPA) must be enabled inthe DB-DC-HSDPA cell.

DB-DC-HSDPA cannot be used simultaneously withMIMO for the UE. DB-DC-HSDPA with the singlecell HSUPA can be activated for the UE. MIMOconfiguration is not specifically restricted in the DB-DC-HSDPA cell but MIMO can be used irrespectiveof the DB-DC-HSDPA configuration in the cell.

0 (disabled)

RAN2179 Dual Band HSDPA is an optional feature (application software) which

requires a long term RNC licence

DB-DC-HSDPA

DB DC HSDPA


31/229



Enabling the Feature (II)

DCellHSDPAEnabled

(WCEL)


0 (Disabled),1 (Enabled)

Default

0 (Disabled)

The DCellHSDPAEnabledparameter must be set to enabled for both cellsbelonging to the cell pair

The parameter indicates whether or not the DCHSDPA feature is enabled in the cell. Before thefeature is enabled in the cell, the system checksthat the maximum amount of DC HSDPA-capable cells is not exceeded. If it is not possible

to enable DC HSDPA for a new cell then the cellsetup does not succeed and error is printed out.

DB-DC-HSDPA

2 cells can form a DB-DC-HSDPA cell pair when they:

operate in different frequency bands (WCEL-UARFCN)

belong to the same sector (WCEL-SectorID)

have the same Tcell value (WCEL-Tcell) DB-DC-HSDPA is not supported for 2 non-contiguous frequencies within the

same operating band

SectorIDand Tcelldefinitions follow the same principles as for DC-HSDPA

DB DC HSDPA


32/229



UE Capability (I)

The UE signals its DB-DC-HSDPA operating band capability within the RRCConnection Setup Complete message

The band combination points towards a row in a table defined by 3GPP TS 25.101

Absence of this information indicates that the UE does not support DB-DC-HSDPA

DB-DC-HSDPA


33/229



UE Capability (II)

The UE signals itsHS-DSCH category

within the RRCConnection Setup

Complete message

The UE must becategory 21 to 28, i.e.

a category which

supports DC-HSDPA

DB-DC-HSDPA

DB DC HSDPA


34/229



RAB Combinations

DB-DC-HSDPA supports the same RAB combinations as DC-

HSDPA 1 to 3 NRT Interactive or Background RAB mapped to HSPA

DB-DC-HSDPA is not allocated to standalone SRB

Simultaneous RT PS RAB or CS RAB are not allowed establishment triggers the release of DB-DC-HSDPA

NRT RAB can be mapped to: DL HS-DSCH and UL E-DCH

SRB can be mapped to: DL HS-DSCH and UL E-DCH, or

DL DCH and UL E-DCH, or

DL DCH and UL DCH

DB-DC-HSDPA

C f DB DC HSDPA


35/229



Flexible Configuration

The flexible configuration requires HSUPA to be enabled on both RFcarriers belonging to a cell pair

The flexible configuration allows both cells to simultaneously act as: primary serving HSDPA cell for some DC-HSDPA capable UE

secondary HSDPA serving cell for other DC-HSDPA capable UE

single carrier HSDPA/HSPA serving cell for non DC-HSDPA capable UE

member of the Active Set for other UE

DC-HSDPAUE1

DC-HSDPAUE2

HSPA UE1

HSPA UE2

Serving Cell

Serving Cell Serving Cell

Serving Cell

Sec. Serving Cell

Sec. Serving Cell

DB-DC-HSDPA

Fi d C fi ti DB DC HSDPA


36/229



Fixed Configuration

The fixed configuration applies when HSUPA is enabled on only 1 of the 2RF carriers belonging to a cell pair

DC-HSDPAUE1

HSPA UE1

HSDPA UE2

Serving Cell

Serving Cell

Serving Cell

Sec. Serving Cell

DB-DC-HSDPA

In the case of the fixed configuration,the RF carrier with HSUPA enabledcan act as:

primary serving HSDPA cell for DC-HSDPA capable UE

single carrier HSDPA/HSPA serving cellfor non DC-HSDPA capable UE


The RF carrier with HSUPA disabledcan act as:

secondary serving HSDPA cell for DC-HSDPA capable UE

single carrier HSDPA serving cell for nonDC-HSDPA capable UE


M i N b f C ti DB-DC-HSDPA


37/229



Maximum Number of Connections

The number if DB-DC-HSDPA connections are limited in a

similar way to DC-HSDPA connections in both cases, connections are only counted in the serving cell

Similar to DC-HSDPA, the number of connections is limitedby the parameters:

WCEL-MaxNumberHSDPAUsers WCEL-MaxNumberHSDSCHMACdFlows

WCEL-MaxNumbHSDPAUsersS

WCEL-MaxNumbHSDSCHMACdFS

Default value of all is 0 (not limited)

DB-DC-HSDPA

M bilit DB-DC-HSDPA


38/229

Soc Classification level40 Nokia Siemens Networks Presentation / Author / Date

Mobility

Switching between DB-DC-HSDPA and DC-HSDPA can betriggered by mobility

DB-DC-HSDPA to DC-HSDPA

DC-HSDPA to DB-DC-HSDPA

Switch occurs when selecting the secondary cell during theServing Cell Change procedure, i.e. the secondary cell is in

the same band or a different band

DC-HSDPA

Serving Cell

Sec. Serving Cell

Band I

Band I

Band VIII

Band I

Band I

DB-DC-HSDPA

DB-DC-HSDPA

S l ti f S d C ll

DB-DC-HSDPA


39/229


Selection of Secondary Cell

Selection of the secondary cell determines whether DC-HSDPA or DB-DC-HSDPA is used

The priority order is shown below

1) DC-HSUPA 16QAM capable cell isselected if DC-HSUPA 16QAM can

be used

2) DC-HSUPA capable cell is selectedif DC-HSUPA can be used

3) DC-HSDPA with MIMO capable cellis selected if DC-HSDPA with MIMO

can be used

4) 64QAM capable cell is selected if64QAM can be used

5) the cell with the lowest number ofexisting HSDPA MAC-d flows is

selected

Accounts for DC-HSUPA capable

UE. DC-HSUPA has higher priority

than DB-DC-HSDPA

Accounts for DB-DC-HSDPA and DC-

HSDPA capable UE when DC-HSUPA or

DC-HSDPA with MIMO cannot be used

Accounts for DC-HSDPA with MIMO

capable UE. DC-HSDPA with MIMO has

higher priority than DB-DC-HSDPA

DB-DC-HSDPA

Si lt f MIMO (I) DB-DC-HSDPA


40/229


Simultaneous use of MIMO (I)

UE cannot be configured with both MIMO and DB-DC-HSDPA

simultaneously UE can be configured with both MIMO and DC-HSDPA (RAN1907)

The existing DCellVsMIMOPreferenceparameter defines the preferencebetween DB-DC-HSDPA and MIMO (without DC-HSDPA)

DC-HSDPA with MIMO has higher priority than DB-DC-HSDPA

MIMO can only be enabled on primary dual cell capable layers

Cell 1Band I

Band I

Band VIII

Cell 2

Cell 3 Cell 1 + Cell 2: DC-HSDPA + MIMO

Cell 2 + Cell 1: DC-HSDPA + MIMOCell 1: SC-HSDPA + MIMO

Cell 2: SC-HSDPA + MIMO

Cell 3: SC-HSDPA + MIMO

Primary cell Secondary cell

DB DC HSDPA

DB-DC-HSDPASi lt f MIMO (II)


41/229


DCellVsMIMOPreference

(RNC)


0 (DC-HSDPApreferred),

1 (MIMOpreferred)

Default

The DCellVsMIMOPreferenceparameter defines the preference betweenDB-DC-HSDPA and MIMO when both are enabled

This parameter determines whether the RNCprimarily activates DC-HSDPA or MIMO for the UE,which supports both DC-HSDPA and MIMO.Simultaneous usage of the DC-HSDPA and MIMO

for the same UE is not supported. DC-HSDPA andMIMO can be enabled in the same cell.

0

DB DC HSDPASimultaneous use of MIMO (II)

Si lt f DC HSUPA DB-DC-HSDPA


42/229


Simultaneous use of DC-HSUPA

DB-DC-HSDPA supports the use of SC-HSUPA

DC-HSUPA (RAN1905) is not supported in combination withDB-DC-HSDPA

would require a total of 3 RF carriers to be in use

If DC-HSUPA is allocated then DC-HSDPA is configured in

the downlink rather than DB-DC-HSDPA

In the case of DB-DC-HSDPA, SC-HSUPA is allocated in theprimary serving cell, similar to DC-HSDPA.

DB DC HSDPA

FMCS Parameter Set DB-DC-HSDPA


43/229


FMCS Parameter Set

DC-HSDPA introduced the DCellHSDPAFmcsIdparameter to allow control ofintra-frequency measurements, i.e. selection of an FMCS parameter set

The same DCellHSDPAFmcsIdparameter is applicable to DB-DC-HSDPA The parameter value from the primary DB-DC-HSDPA cell is applied

DB DC HSDPA

DCellHSDPAFmcsId

(WCEL)


1 to 100,

0 (not defined)

Default

This parameter identifies the measurement control

parameter set (FMCS object) controlling the intra-frequency measurements of a user having DC HSDPAallocated.

0

Performance vs DC HSDPA


44/229


Performance vs. DC-HSDPA

Higher frequency diversity can be achieved in environments

with low multipath spread (Micro cells, indoor) Also lower slow fading correlation

Fast resource sharing will provide some statisticalmultiplexing gains

Counters DB-DC-HSDPA


45/229


Counters

The corresponding counters as shown below are introduced within the RRCSignalling Table

M1006Cx ATT_RB_SETUP_DCHSDPA

M1006Cx SUCC_RB_SETUP_DCHSDPA

M1006Cx FAIL_RB_SETUP_DCHSDPA_NOREP

M1006Cx FAIL_RB_SETUP_DCHSDPA_UE

Also existing DC-HSDPA counters M1006C209-M1006C212 shall be updatedalong with these new DB-HSDPA counters

DC names

DB-DC not in RISE

The counters shown below are introduced within the Service Level Table

M1001Cx UE supporting DB-DC-HSDPA band combination Rel9-1



DB DC HSDPA

NAMES???

Content


46/229


Content


MIMO 42Mbps Dual-Band HSDPA 42Mbps*

DC-HSDPA with MIMO 84Mbps*

HSUPA 16QAM*

Flexible RLC in UL* DC-HSUPA 23 Mbps*

Other RU30 features

Background DC + MIMO 84 Mbps


47/229


Background

Maximum connection throughputs in RU20

p

64QAM3GPP Rel. 7

MIMO3GPP Rel. 7

DC-HSDPA + 64QAM3GPP Rel. 8

21 Mbps 28 Mbps 42 Mbps

MIMO + 64QAM3GPP Rel. 8

DB-DC-HSDPA + 64QAM3GPP Rel. 9

DC-HSDPA + MIMO3GPP Rel. 9

42 Mbps 42 Mbps 56 Mbps

Maximum connection throughputs in RU30

DC-HSDPA + MIMO + 64QAM3GPP Rel. 9

84 Mbps

Both supportedby RAN1907

2carriers

Requirements DC + MIMO 84 Mbps


48/229


Requirements

UE Requirements

Release 9, or newer

HSDPA Category 27 or 28 (categories 25 and 26 support DC-HSDPA andMIMO without 64QAM)


Flexi Node B must have release 2 system module. RF module can berelease 1 but cannot be mixed release 1 and release 2 (release 1 single

RF module cannot be used for a MIMO cell)

UltraSite Node B must have EUBB, WTRB or WTRD

Double PA units and antenna lines

RNC must have CDSP-DH cards



HSDPA 64QAM, Dual-Cell HSDPA 42 Mbps, MIMO, MIMO with 64QAM, HSUPA

p

Enabling the Feature (I) DC + MIMO 84 Mbps


49/229



DCellAndMIMOUsage

(WCEL)


0 (DC-HSDPA and MIMOdisabled),

1 (DC-HSDPA and MIMOw/o 64QAM enabled),

2 (DC-HSDPA and MIMOwith 64QAM enabled)

Default

The DCellAndMIMOUsageparameter must be set to a value of 2 to achievethe peak connection throughput


Defines whether DC-HSDPA and MIMO canbe used simultaneously for the same UE.Both features must be separately enabled inthe cell in order to make simultaneoususage possible for the UE. The parameter

also defines whether 64QAM can be usedwhen DC-HSDPA and MIMO aresimultaneously configured in use for the UE.

0

RAN1907 DC-HSDPA with MIMO 84 Mbps is an optional feature but does nothave its own licence. It requires the following to be licensed:

RAN1642 MIMO (28 Mbps)

RAN1643 HSDPA 64QAM

RAN1906 Dual-Cell HSDPA 42 Mbps

DC-HSDPA with MIMO can be enabled without RAN1643 HSDPA 64QAM butthe peak connection throughput is then limited to 56 Mbps

p

Enabling the Feature (II) DC + MIMO 84 Mbps


50/229


Enabling the Feature (II)

MIMOWith64QAMUsage

(WCEL)


0 (MIMO with 64QAMdisabled),

1 (MIMO with 64QAMenabled)

Default

The MIMOWith64QAMUsageparameter must be set to a value of 1 to allow64QAM to be used with MIMO


This parameter defines whether MIMOand 64QAM modulation can be usedsimultaneously for the same UE. Bothfeatures must also be separately enabled

in the cell in order to make simultaneoususage possible for the UE.

0

64QAM must be enabled in both the primary and secondary cells

p

RAB Combinations DC + MIMO 84 Mbps


51/229


RAB Combinations

DC-HSDPA with MIMO supports the same RAB combinations as the

parent features: NRT (Interactive and Background) PS services only are supported

3 simultaneous PS NRT RAB are supported if the HSPA Multi-NRT RABfeature is enabled

simultaneous CS RAB or RT PS RAB are not allowed

DC-HSDPA with MIMO supports only full HSPA configurations:

User plane RB mapped onto HS-DSCH in DL and E-DCH in UL

If RB cannot be mapped onto HSPA, DC-HSDPA with MIMO cannot be used

SRB mapped onto HS-DSCH in DL and E-DCH in UL

If SRB cannot be mapped onto HSPA, DC-HSDPA with MIMO cannot be used

If DC-HSDPA with MIMO is used, but the RB or SRB can no longer bemapped onto HSPA then DC-HSDPA with MIMO is deactivated

p

UE Capability (I) 3GPP Release

9 TS 25 306


52/229


UE Capability (I)

The UE signals itsHS-DSCH category

within the RRCConnection Setup

Complete message

The UE must becategory 25 to 28 to

support both MIMO

and DC-HSDPA

Only categories 27 and28 support 64QAM,

MIMO and DC-HSDPA

3GPP Release 9, TS 25.306

DC + MIMO 84 Mbps

UE categories and network features


53/229


UE categories and network features

16-QAM 64-QAM enabled(MAC-es)

MIMO Enabled DC Enabled DC + MIMOenabled

Cat-21 10 Mbps (Cat-9) 10 Mbps (Cat-9)64-QAM: 18 Mbps(Cat-13)

16-QAM: (Cat-15)

64-QAM (Cat-17)

10 Mbps (Cat-9)64-QAM (Cat-13)

MIMO + 16 QAM (Cat-15/17)

Cat-21/22

14.4 Mbps (Cat-10)

14.4 Mbps (Cat-10)

64-QAM: 21 Mbps(Cat-14)

16-QAM: (Cat-16)64-QAM (Cat-18)

14.4 Mbps (Cat-10)

64-QAM (Cat-14)

MIMO + 16 QAM (Cat-

16/18)

16-QAM: (Cat-22)

Cat-23 10 Mbps (Cat-9) 64-QAM: 18 Mbps(Cat-13)

MIMO + 64-QAM (Cat-19)


Cat-23/24

14.4 Mbps (Cat-10)


64-QAM (Cat-14)

MIMO + 16 QAM (Cat-18)

MIMO + 64-QAM (Cat-20)


Cat-25to28

Cat 21-24 asabove

Cat 25-28

DRAFT!

UE Capability (II)


54/229


UE Capability (II)

The UE also signals its support for DC-HSDPA with MIMO within the RRCConnection Request

DC + MIMO 84 Mbps

This information is not currently used by the RNC

Multi-Band Load balancing is used for layering rather than Directed RRC ConnectionSetup

DC-HSDPA with MIMO Throughputs (I)


55/229


DC-HSDPA with MIMO Throughputs (I)



Spreading Factor = 16=> Symbol Rate = 240 ksps

Number of HS-PDSCH codes = 15

=> Aggregate Symbol Rate per stream = 3.6 Msps

Number of bits per Symbol = 6

=> Aggregate Bit Rate = 21.6 Mbps

Number of Parallel Streams of Data = 4

=> Bit Rate = 86.4 Mbps (peak)

Physical Layer (based upon UE maximum transport block size)

Category 20 maximum transport block size = 42 192 bits


=> Bit Rate per transport block = 21.096 Mbps

Number of Transport Blocks = 4

=> Bit Rate = 84.384 Mps (peak) coding rate of 0.98

64-QAM

MIMO + DC

DC-HSDPA with MIMO Throughputs (II)


56/229


DC-HSDPA with MIMO Throughputs (II)


Maximum transport block size payload = 42192[24 + (7 16)] = 42056 bits

RLC header size per transport block = 8 16 = 128 bits

=> RLC payload = 4 (42056128) = 167712 bits



MAC-ehs re-transmission rate = 10 % RLC re-transmissions rate = 1 %








MAC-ehs header sizebased upon maximum RLCPDU payload of 5568 bits

MIMO within Primary and Secondary Cells


57/229


MIMO within Primary and Secondary Cells

Whenever possible, MIMO is used in both the primary and

secondary cells. Otherwise, MIMO can be used only in theprimary cell.

MIMO can be used in both the primary and secondary DC-HSDPA cells

MIMO with DC-HSDPA can be used only in the primary DC-HSDPA cell

MIMO with DC-HSDPA cannot be used only in the secondary DC-HSDPA cell

If MIMO is used only in the primary cell, the maximumachievable throughput is:

63 Mbps (primary 42 Mbps + secondary 21 Mbps) if 64QAM is enabled 42 Mbps (primary 28 Mbps + secondary 14 Mbps) if 64QAM is disabled

DC + MIMO 84 Mbps

Configuring the use of MIMO DC + MIMO 84 Mbps


58/229


Configuring the use of MIMO

If DC-HSDPA is enabled in any cell of the sector:

MIMO can be enabled in primary DC-HSDPA capable cells MIMO can not be enabled in secondary DC-HSDPA only capable cells

MIMO can not be enabled in any other cell than a DC-HSDPA cell

A cell is considered as a primary DC-HSDPA capable cell ifHSUPA is enabled

If DC-HSDPA is not enabled in any cell of the sector then theMIMO layer configuration is not restricted by the RNC

The restrictions above are checked by O&M whenDCellHSDPAEnabled, MIMOEnabled, HSUPAEnabled orSectorIDparameters are modified

Selection of DC-HSDPA Secondary Cell (I)


59/229


Selection of DC HSDPA Secondary Cell (I)

There may be more than a single candidate for the

secondary serving cell, e.g. on a site with 3 RF carriers Selection of the secondary cell uses the criteria:

1. MIMO with 64QAM capable secondary cell is chosen if MIMO with64QAM can be used in the primary cell

2. MIMO capable secondary cell is chosen if MIMO can be used in theprimary cell

3. The secondary cell, where the number of existing HSDPA MAC-dflows is lowest

if the number of existing HSDPA MAC-d flows is the same, candidates areconsidered equal and the secondary cell is selected at random

DC + MIMO 84 Mbps

Selection of DC-HSDPA Secondary Cell (II)


60/229


Selection of DC HSDPA Secondary Cell (II)

If DC-HSDPA with MIMOcannot be used in the primary cell

then the secondary cell is selected using the criteria:1. 64QAM capable secondary cell is chosen if 64QAM can be used in theprimary cell

2. The secondary cell, where the number of existing HSDPA MAC-dflows is lowest

if the number of existing HSDPA MAC-d flows is the same, candidates are

considered equal and the secondary cell is selected at random

These selection criteria are applicable to DC-HSDPA ingeneral, e.g. when a site has DC-HSDPA enabled but MIMOdisabled

The secondary serving cell is only changed if the primaryserving cell changes

DC + MIMO 84 Mbps

Allowing use of DC-HSDPA with MIMO


61/229


Allowing use of DC HSDPA with MIMO

DC-HSDPA with MIMOis used in both the primary and

secondary cell whenever possible based upon normal criteriafor DC-HSDPA and MIMO MIMO is used in the secondary cell whenever the simultaneous usage

of the DC-HSDPA and MIMO is possible and if MIMO is used in theprimary cell

When conditions change, DC-HSDPA with MIMOcan beactivated/de-activated during an ongoing connection

If DC-HSDPA with MIMOis not possible but DC-HSDPA w/oMIMO or MIMO w/o DC-HSDPA is possible, the choice

between DC-HSDPA and MIMO is based on the parameterDCellVsMIMOPreference

If neither DC-HSDPA nor MIMO is possible anymore, SC-HSDPA without MIMO is used if possible

DC + MIMO 84 Mbps

Mobility


62/229


Mobility

DC-HSDPA with MIMOcan be maintained, activated or de-activatedduring mobility (serving cell change and hard handover)

The availability of DC-HSDPA with MIMOis checked in the target cellwhen the serving cell change or hard handover is initiated

If DC-HSDPA with MIMOcannot be used in the target cell mobilityproceeds without it:

DC-HSDPA or MIMO is used if possible, according to the parameter

DCellVsMIMOPreference If HSUPA IFHO can be used DC-HSDPA and MIMO is not be deactivated

but is maintained during inter-frequency measurements

If HSUPA IFHO cannot be used, E-DCH to DCH switch is completedbefore inter-frequency measurements can start

DC-HSDPA with MIMO is deactivated at the same time

DC-HSDPA with MIMOis not supported across the Iur

SRNC does not configure DC-HSDPA with MIMOif there are radio linksover the Iur in the active set

DC + MIMO 84 Mbps

HS-DPCCH DC + MIMO 84 Mbps


63/229


HS DPCCH

HS-DPCCH used to transfer

HARQ acknowledgements for all 4 data streams Precoding Control Information (PCI) for MIMO

CQI reports (Type A and Type B)

As with normal DC-HSDPA, theHS-DPCCH is only sent on the

primary RF carrier The CQI reports for the 2 RF

carriers are transferred in a TimeDivision Multiplexing (TDM) manner

differs to CQI reporting for DC-HSDPAwithout MIMO in which case both CQI

reports are sent in same TTI

When repetition is used, repetitionsfor the first RF carrier are sent priorto repetitions for the second RF carrier

Channel Coding

Map onto HS-DPCCH

w0w9

HARQ-ACK

Concatenation

pci0,pci1

Type ACQI

cqi0cqi7

PCI

a0a9or a0a6

Type BCQI

cqi0cqi4

Channel Coding

b0b19

or

CQI for MIMO (I) DC + MIMO 84 Mbps


64/229


CQ o O ( )

MIMO connections report CQI values on the HS-DPCCH

MIMO connections use two types of CQI

Type Aapplicable to dual stream, with support for single stream

Type Bapplicable to single stream

CQI =

CQIs when 1 TB preferred by UE (range 0 to 30)

15 CQI1+ CQI2+ 31 when 2 TB preferred by UE (range 31 to 255)

Type A

CQI1corresponds to TBS which could be received using the preferred primaryprecoding vector (range 0 to 14)

CQI2corresponds to TBS which could be received using the precoding vector

which is orthogonal to the preferred primary precoding vector (range 0 to 14)

CQIScorresponds to TBS which could be received using the preferred primary

precoding vector (0 to 30)

CQI = CQIs (range 0 to 30)

Type B

CQI for MIMO (II) DC + MIMO 84 Mbps


65/229


Q ( )

The RNC informs the UE of:

CQI feedback cycle (range: 0,2,4,8,10,16,20,32,40,64,80 ms)

CQI repetition factor (range: 1,2,3,4)

N_cqi_typeA/M_cqi ratio (range: 1/2, 2/3, 3/4, 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 1/1)

These parameters define the pattern with which the CQI reports are sent

UE indicates dual stream or single stream within type A according to the currentchannel conditions

Type B is sent periodically for single stream fall back in case the Node B decides

to use single stream while the UE is reporting a dual stream

Complete cycle of 10 4 = 40 TTI = 80 ms

New CQI sent every 4 TTI = 8 ms

Type A CQI Type B CQI

Example:

CQI feedback cycle = 8 ms

CQI repetition factor = 2

N CQI type A / M = 9/10

New for MIMO

CQI Mapping Tables

DC + MIMO 84 Mbps


66/229


Q pp g

CQI mapping tables

applicable to UEcategories 25 to 28

are shown

UE categories 25 and26 do not support

64QAM

MaxBitRateNRTMACDFlow DC + MIMO 84 Mbps


67/229


This slide is applicable to RN6.0 in general and is not limited

to the DC-HSDPA and MIMO feature O&M converts the default and special value of

MaxBitRateNRTMACDFlowduring the software upgrade

value is changed from 65535 to 0, if 65535 was previously used

value is not changed if any other value was previously used

The RN6.0 value of 0 corresponds with the value 65535 inearlier releases

The value 0 (RN6.0) / 65535 (RN5.0 and before) means that theHSDPA peak rate is not limited by the RNC

The value 0 is the new default and special value

Theoretical performance

DC + MIMO 84 Mbps


68/229


p

The graph shows increase in User-TP due to DC+MIMO against DC HSDPA &

HSDPA

MIMO impact

on Cell

coverage as

compared to

normal HSDPA

mode

Small Overhead on HS-DPCCHS-CPICH needed for MIMO

Practical performance of Single cell 64-QAM and


69/229


MIMO, 64QAM & 16QAM application throughput

0.0

5.0

10.0

15.0

20.0

25.0

Loc1 (-52 dBm) Loc2 (-60 dBm) Loc3 (-67dBm) Loc5 (-85 dBm) Loc6 (-95 dBm)

Throughput[Mbps]

MIMO

64QAM

16QAM

p gMIMO

In a good RF conditions, there is clear benefit of using MIMO or 64QAM instead of16QAM. In cell edge conditions, the benefit is less.

NOTE: Some SW improvement done to BTS after test, MIMO performance to be verified.

16QAM modulationused instead of64QAM in Loc6

REF: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trials

Practical performance of Dual cell 64-QAM, single


70/229


p , gcell MIMO 16-QAM and 64-QAM MIMO DC HSDPA show best performance in each location when compared to single cell

MIMO or 64QAM features

NOTE: Low DC-HSDPA performance is under investigation, most probably UE issue

Static test comparison of HSPA+ feature performance (NSN Espoo

11.10.2010)

27.4

9.611.2

13.6

27.7

11.39.4

10.6 10.3

18.7

11.8

8.3 9.5

10.8

15.0

0.0

5.0

10.0

15.0

20.0

25.0

30.0

Loc1 (-75..-

83dBm)

Loc2(-90 dBm) Loc3 (-87 dBm) Loc4 -80..-85

dBm)

Loc5 (-55..-60

dBm)

D

Lapptp(Mbps)

DC HSDPA

MIMO

64QAM

REF: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trials

Counters (I)DC + MIMO 84 Mbps
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trialshttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/WCDMA_Radio_Test&Trials


71/229


( )

The Service Level table includes the counters shown below

M1001C707 UE_SUPP_HSDSCH_CLASS_25_26

M1001C708 UE_SUPP_HSDSCH_CLASS_27_28

M1001C709 ACCESS_STRATUM_REL_IND_9

The Packet Call table includes the counters shown below

M1022C223 SUCC_SWI_DCHSDPA_TO_SCHSDPA

M1022C224 SUCC_SWI_SCHSDPA_TO_DCHSDPA

These counters are not specific for DC-HSDPA with MIMO, but also apply tobasic DC-HSDPA

Counters (II)DC + MIMO 84 Mbps


72/229


( )

The Node B HSPA table includes the counters shown below

M5000C424 ACTIVE_DC_MIMO_USERS_2C_SUMM5000C425 ACTIVE_DC_MIMO_USERS_1C_SUM

M5000C426 CAPABLE_DC_MIMO_USERS_SUM

M5000C427 TTI_DCMIMO_HSDPA_PC_1C_D

M5000C428 TTI_DCMIMO_HSDPA_PC_1C_S

M5000C429 TTI_DCMIMO_HSDPA_SC_1C_D

M5000C430 TTI_DCMIMO_HSDPA_SC_1C_SM5000C431 TTI_DCMIMO_HSDPA_2C_D_D

M5000C432 TTI_DCMIMO_HSDPA_2C_D_S

M5000C433 TTI_DCMIMO_HSDPA_2C_S_D

M5000C434 TTI_DCMIMO_HSDPA_2C_S_S

Content


73/229



MIMO 42Mbps Dual-Band HSDPA 42Mbps


HSUPA 16QAM

Flexible RLC in UL

DC-HSUPA 23 Mbps

Other RU30 features

Background HSUPA 16QAM


74/229


3GPP Release 6 introduced HSUPA with QPSK maximum connection throughput of 5.76 Mbps

3GPP Release 7 introduces HSUPA with 16QAM maximum connection throughput of 11.52 Mbps

HSUPA category 7 UE support 16QAM

The actual achievable throughput is limited by the radio conditions andmaximum allowed uplink noise rise

Performance benefits from: Frequency Domain Equaliser (FDE)

Parallel Interference Cancellation (PIC)

UE selects 16QAM once the throughput reaches a specific level definedby 3GPP

Uplink Flexible RLC is applicable to HSUPA with 16QAM 3GPP Release 8 capability so may not be available

RLC PDU size of 656 bits is introduced for when uplink Flexible RLC isnot available

Requirements HSUPA 16QAM


75/229


UE Requirements

HSUPA Category 7




CDSP-DH card in RNC (RAN1226 HSPA Peak Rate Upgrade for RNC196and RCN450)


RAN981 HSUPA 5.8 Mbps and RAN1470 HSUPA 2 ms TTI

In practice, FDE and PIC are also required to allow a large enough noise risefor the peak data rate

UE Categories HSUPA 16QAM


76/229


HSUPA Category 7 UE support 16QAM with the 2ms TTI

Signalled to the RNC within the RRC Connection Setup Complete message

Bit Rates (I)

HSUPA 16QAM


77/229






Number of E-DPDCH codes = 2

=> Aggregate Symbol Rate = 5.76 Msps

Number of bits per Symbol = 2 (generated by 4PAM modulation)=> Bit Rate = 11.52 Mbps (peak)

Physical Layer (based upon UE maximum transport block size)

Category 7 maximum transport block size = 22 996 bits


=> Bit Rate = 11.498 Mps (peak)

coding rate of 0.998



Number of E-DPDCH codes = 2

Bit Rates (II)

HSUPA 16QAM


78/229



Maximum transport block size = 22996 bits, MAC e/es header = 18 bits

Maximum number of RLC PDU of size 656 bits = 35 Header 35*16

=> RLC payload = 22436 bits



MAC-e re-transmission rate = 10 % RLC re-transmissions rate = 1 %








Bit Rates (III) F-RLC

HSUPA 16QAM +FLEX RLC UL


79/229




Maximum transport block size = 22996 bits, MAC i/is header = 24 bits

Maximum number of RLC PDU of size 12040 bits = 1.91 Header 2*32




MAC-e re-transmission rate = 10 % RLC re-transmissions rate = 1 %



IP header size = 20 bytes TCP header size = 36 bytes




Enabling the Feature (I) HSUPA 16QAM


80/229



HSUPA16QAMAllowed

(WCEL)


0 (disabled),

1 (enabled)

Default

The HSUPA16QAMAllowedparameter must be set to enabled


This parameter is used to define whether theRNC allows the usage of 16QAM modulation forHSUPA. If the parameter is enabled, then theRNC can use the HSUPA 16QAM feature in acell. If the parameter is disabled, then the RNCcannot use the HSUPA 16QAM feature in a cell.The HSUPA 16QAM is allowed in the cell if theMaxTotalUplinkSymbolRate has value "3"indicating the max symbol rate of 5760 kbps.

0 (disabled)

RAN1645 HSUPA 16QAM is an optional feature (application software) which

requires a long term RNC licence

Enabling the Feature (II) HSUPA 16QAM


81/229



MaxTotalUplinkSymbolRate

(WCEL)

Name Range

0 (960 kbps, SF4)

1 (1920 kbps, 2*SF4)

2 (3840 kbps, 2*SF2)

3 (5760 kbps, 2*SF2+2*SF4)

Default

0 (960 kbps, SF4)

The existing MaxTotalUplinkSymbolRateparameter must be set to 3

Parameter requires object locking for modification

This parameter determines the planned maximum total uplink symbol rate of the E-DPDCH(s) of the UE inthe cell. The lowest parameter value among the parameter values of the cells that belong to the E-DCHactive set is used when the E-DCH is allocated. The signaled value is updated when a soft handoverbranch addition or deletion occurs and the lowest value changes. Note: Upgrade is not always possible dueto capacity reasons in the RNC.

In case "HSUPA 2 Mbps" feature is active (state "On" and exist) but "HSUPA 5.8 Mbps" feature is notactive, the maximum value of this parameter is "2". In case "HSUPA 5.8 Mbps" feature is active (state "On"and exist), the maximum value of this parameter is "3" and also the value "2" is allowed although the"HSUPA 2 Mbps" feature is not active. If not active, the parameter value change to "3" is not allowed.

Allocation of 16QAM HSUPA HSUPA 16QAM


82/229



The RNC allocates an HSUPA 16QAM connection if all E-

DCH active set cells satisfy: HSUPA 16QAM license is available and set ON

HSUPA 16QAM is enabled in each cell

UE is HSUPA 16QAM capable

Cells are HSUPA 16QAM capable

Features required by HSUPA 16QAM are in use

NRT PS Radio Bearer is mapped onto the E-DCH

2ms TTI and 5.8 Mbps (2*SF2+2*SF4) are used for E-DCH

All cells of the active set are handled by the SRNC i.e. drifting is not

allowed Uplink flexible RLC is used, or fixed PDU size of 656 bits is used

Number of HSUPA 16QAM connections does not exceed the valuedefined by HSUPAUserLimit16QAM

Maximum Number of 16QAM Users HSUPA 16QAM


83/229



HSUPAUserLimit16QAM

(WCEL)


1 to 10,

step 2

Default

The HSUPAUserLimit16QAMparameter defines the maximum allowed number ofHSUPA connections using 16QAM within a cell

It is also used when selecting between fixed PDU sizes of 336 and 656 bits

This parameter defines the limit for the amount of activeHSUPA users in a cell in determining the usage ofHSUPA 16QAM with both fixed and flexible UL RLC. Itis also used in determining the fixed UL RLC PDU sizewith MAC-es.

For flexible UL RLC: If the amount of active HSUPAusers in a cell is lower than or equal to the threshold,defined by this parameter, the HSUPA 16QAM usage isallowed with flexible UL RLC PDU size.

For fixed UL RLC: If the amount of active HSUPA users

in a cell is lower than or equal to the threshold, definedby this parameter, the fixed UL RLC PDU size shall be656 bits. Otherwise an UL RLC PDU size of 336 bitsshall be used. The HSUPA 16QAM usage is allowed ifthe UL RLC PDU size is 656 bits.

2

Modulation HSUPA 16QAM


84/229



Modulation applied to each individual E-DPDCH is BPSK or 4PAM (PulseAmplitude Modulation)

BPSK and 4PAM appear as QPSK and 16QAM when E-DPDCH are mapped toboth the in-phase and quadrature branches of the modulation constellation

Some 3GPP specifications refer to QPSK and 16QAM, other 3GPP specificationsrefer to BPSK and 4PAM

QPSK 16QAM

2 bits per symbol 4 bits per symbol

BPSK

BP

SK

4P

AM

4PAM

Modulation Switching HSUPA 16QAM


85/229



The E-DPDCH configuration is increased to 2SF2 + 2SF4

prior to switching modulation scheme The UE then automatically switches to 16QAM when thequantity of puncturing becomes relatively high 3GPP specifies a puncturing threshold of 0.468 (meaning that 46.8 % of

the channel coded bits remain after puncturing)

In practice, this corresponds to switching modulation schemewhen the transport block size defined by the E-TFCI issufficiently large, i.e. the throughput becomes relatively high E-TFCI of 103 when using 2ms TTI E-DCH Transport Block Size Table

2

8450 bits (4.225 Mbps)

Transport Block Size Table (I) HSUPA 16QAM


86/229



3GPP TS 25.321 specifies transport block size tables 2 and 3 for the 2 msTTI which have maximum transport block sizes of 22995 and 22996 bits

Maximum throughput of 11.50 Mbps

NSN implementation uses Table 2 for 16QAM HSUPA connections

RLC PDU Size HSUPA 16QAM


87/229



Uplink flexible RLC is a 3GPP release 8 feature

16QAM HSUPA is a 3GPP release 7 feature If flexible RLC is not available then a fixed PDU size of 656 bits is used if:

UE, BTS and RNC support uplink data rates exceeding 5.8Mbps

the selected data service allows data rates exceeding 5.8Mbps

the number of active HSUPA users within the serving cell is

HSUPAUserLimit16QAM Otherwise a fixed PDU size of 336 bits is used and 16QAM is not allowed

If a fixed PDU size of 336 bits is configured, the maximum uplink data rateis limited to 5.8Mbps

The fixed PDU size of 656 bits has disadvantages of:

increased step size less control at low throughputs

increased noise rise with each step

increased BTS processing requirement

Serving Grant Table Table 1 Table 2


88/229



Serving Grant Table 2 has beenintroduced within 3GPP TS 25.321 for the

purposes of 16QAM Allows increased power offsets

HSUPA 16QAM

E-AGCH HSUPA 16QAM


89/229



The table used to map the signalled E-AGCH values to a power offset ischanged when 16QAM is used

Uplink Interference Power HSUPA 16QAM


90/229



Uplink interference power generated by 16QAM HSUPA throughputs isrelatively high

Uplink interference power can be reduced by using advanced receiverswithin the Node B (Frequency Domain Equaliser feature)

234567

89

101112131415161718

19202122232425

3840 5760 6600 7600 8990 10900

L1 Bitrate [kbps]

NoiseRise[dB]

Rake

GRake

Counters HSUPA 16QAM


91/229



The counters shown below are introduced for HSUPA 16QAM

M5000C359 EDCH_16QAM_UE_ACT_SUM

M5000C360 MACE_PDU_RX_COR_16QAM

M5000C361 MACE_PDU_RX_INCORR_16QAM

Content


92/229




MIMO 42Mbps DC-HSDPA with MIMO 84Mbps*

Dual-Band HSDPA 42Mbps*

HSUPA 16QAM*

Flexible RLC in UL*

DC-HSUPA 23 Mbps*

Other RU30 features

Background (I)UE Pre Release 8 UE Flexible RLC

UL FLEX RLC


93/229



Segmentation

UE - Pre-Release 8

RLC

MAC-e/es

RLC

Segmentation /Concatenation

MAC-i/is

UE - Flexible RLC

Concatenation /Padding

Prior to 3GPP Rel. 8, theRLC layer within the UEsegmented large higher layerpackets into many smallpackets

The MAC-e/es layer then hadto concatenate and padthese small packets to fitwithin the variable sizeHSUPA transport block

Flexible RLC helps to avoidthis requirement forsegmentation andsubsequent concatenation

The MAC-i/is layer segmentsthe higher layer packets suchthat they fit within the

HSUPA transport block There is a reducedrequirement for RLC headersand padding

Background (II) UL FLEX RLC


94/229



0%

5%

10%

15%

20%

25%

30%

35%

40%

45%

50%

0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500

Rel. 7 with RLC PDU Size of 336 bits

Rel. 7 with RLC PDU Size of 656 bits

Rel. 8 Flexible RLC

Graph below illustrates the difference in RLC overhead (header andpadding) when using:

Fixed RLC PDU sizes of 336 bits and 656 bits

Flexible RLC

Overhead is significantly less for Flexible RLC

Assumes 16 bit

RLC header in allcases, i.e. does notaccount for theLength Indicator

Higher Layer Packet Size (bytes)

R

LC

Overhead

Background (III)Pre Release 7 Approach Flexible RLC Approach

Example below is based upon a maximum transmit windowsize of 52. In practice, the maximum window size would begreater but the principle remains the same

UL FLEX RLC


95/229



The RLC layer uses a 12 bitSequence Number (SN) for

Acknowledged Mode (AM) RLC

(range from 0 to 4095)

RLC layer stalls if the sequencenumber range is used too rapidly

(transmit window size is reached)

Stalling is most likely while re-

transmissions are ongoing

Lower HSUPA throughputs(QPSK) use an RLC PDU size of

336 bits

Higher HSUPA throughputs

(16QAM) use an RLC PDU size of656 bits

Increasing the HSUPA throughputfurther, e.g. using DC-HSUPA,

requires larger PDU sizes

Pre-Release 7 Approach Flexible RLC Approach

1 2 3 4 5 6 7

8 9 10 11 12 13 14

15 16 17 18 19 20 21

22 23 24 25 26 27 28

29 30 31 32 33 34 34

36 37 38 39 40 41 42

1 2 3 4 5 6 7

43 44 45 46 47 48 49

50 51 52

1 2 3 4 5 6 7

1

2

1

3

4

5

6

7

8

9

10

11

1

12

13

Original

Transmission

RLC Layer

Stalled

Re-

Transmission

Requirements UL FLEX RLC


96/229



UE Requirements

UE must support Flexible RLC (optional within 3GPP release 8)




RNC CDSP-DH cards are required to fully utilise feature (see next slide)



Flexible RLC in DL, Basic HSUPA

Feature itself is included as basic software and is not licensed

RNC Configuration UL FLEX RLC


97/229



Flexible RLC is only applied to NRT PS RAB, and only whena CDSP-DH card is available

MAC-i/is layers can be configured with fixed RLC PDU sizesfor SRB, RT PS and CS Voice over HSPA RAB (requiresCDSP-DH card with exception of SRB)

SRB NRT PS RT PS CS Voiceover HSPA

CDSP-DH

CDSP-C

CDSP-DH CDSP-C CDSP-DH CDSP-C CDSP-DH

RLC Fixed RLC

(UM & AM)

Flexible RLC

(AM)

Fixed RLC

(AM)

Fixed RLC

(AM)

Fixed RLC

(AM)

Fixed RLC

(UM)

MAC MAC-is MAC-is MAC-es MAC-is MAC-es MAC-is

FP E-DCH FPType 2

E-DCH FPType 2

E-DCH FPType 1

E-DCH FPType 2

E-DCH FPType 1

E-DCH FPType 2

Interactive & background Streaming

Enabling Flexible RLC in Uplink UL FLEX RLC


98/229



FlexULRLCEnabled

(RNC)

This parameter enables/disables use offeature Flexible UL RLC. If the parameter isenabled (1), then feature Flexible UL RLCis used in the RNC. If the parameter is

disabled (0), then feature Flexible UL RLCis not used in the RNC.


0 (Disabled), 1 (Enabled)

Default

0

RNC databuild parameter FlexULRLCEnabledused to enable/disable


Uplink Flexible RLC is only applicable when mapping onto HSUPA(specified by 3GPP)

Downlink Flexible RLC is only applicable when mapping onto HSDPA(specified by 3GPP)

UE Capability UL FLEX RLC


99/229



UE signals its support for uplink flexible RLC within

RRC CONNECTION REQUEST RRC CONNECTION SETUP COMPLETE

UE CAPABILITY INFORMATION

Support of MAC-i/is information element is used to indicatesupport of uplink flexible RLC (in contrast to MAC-ehs fordownlink flexible RLC)

Selecting Uplink Flexible RLC UL FLEX RLC


100/229



The following criteria must be satisfied for all cells within the E-DCH ActiveSet:

the cell is flexible UL RLC capable the UE is flexible UL RLC capable

the FlexULRLCEnabledparameter is set to enabled

the criteria for downlink flexible RLC are satisfied

the cell is handled by the Serving RNC i.e. drifting is not allowed

Otherwise, fixed RLC PDU sizes with MAC-e/es and FP DATA FRAMEtype 1 are used

The criteria above are checked when establishing connections for: NRT PS RB

RT PS RB

SRB

CS voice over HSPA

They are also checked during active set updates and when connectionsare released

Protocol Stack Changes UL FLEX RLC


101/229



Without Uplink Flexible RLC

With Uplink Flexible RLC

WCDMA L1

UE SRNC

Node B

MAC-e/es

RLCMAC-d

WCDMA L1

MAC-e

Transport

FrameProtocol

Transport

FrameProtocol

RLCMAC-d

IubUu

MAC-es

WCDMA L1

UE SRNC

Node B

MAC-i/is

RLC

MAC-d

WCDMA L1

MAC-i

Transport

FrameProtocol

Transport

FrameProtocol

RLC

MAC-d

IubUu

MAC-is

RLC Layer (I) UL FLEX RLC


102/229



3GPP specifies that Uplink Flexible RLC is applicable to Acknowledged Mode(AM) and Unacknowledged Mode (UM) RLC

In contrast to Downlink Flexible RLC which is only applicable to AM RLC RU30 applies Uplink Flexible RLC to AM only (although MAC-i/is layer can be

used by UM RLC)

Flexible RLC reduces the requirement for segmentation

Segmentation is still necessary when the higher layer packet size exceeds themaximum RLC PDU size

3GPP supports a maximum RLC PDU size of 1505 bytes (12040 bits)

Non-configurable RNC databuild parameter, MaxULRLCPDUSizedefines themaximum size in RU30

MaxULRLCPDUSize

(RNC)


16 to 12040 bit,step 8 bit

Default

12040 bits The maximum size for uplink RLC PDU. Themaximum UL RLC PDU size is used with flexibleUL RLC and MAC-is. The maximum sizeconsists of payload size and header of 24/32 bits(7bit or 15bit Length Indicator is included).

Non-Configurable

RLC Layer (II) UL FLEX RLC


103/229



MinULRLCPDUSize

(RNC)


16 to 12040 bit,step 8 bit

Default

336 bits

3GPP supports a minimum RLC PDU size of 2 bytes (16 bits)

Non-configurable RNC databuild parameter, MinULRLCPDUSizedefines theminimum size in RU30

The minimum size for uplink RLC PDU. Theminimum UL RLC PDU size is used with flexibleUL RLC and MAC-is. The minimum size consistsof payload size and header of 16 bits (LengthIndicator is not included).

Non-Configurable

AM RLC PDU AM RLC PDU structure remains the same withFlexible RLC

header has a minimum length of 16 bits

Sequence number has a length of 12 bits

(compared to 7 bits for Unacknowledged ModeRLC). Larger range required to allow a larger

transmit window.

If MaxULRLCPDUSize> 1008 bits, the LengthIndicator size is 15-bits

RRC Layer UL FLEX RLC


104/229



The RRC layer provides the UE with information regardinguplink Flexible RLC

Length Indicator Size Minimum Uplink RLC PDU Size

Maximum Uplink RLC PDU Size

Can be included within RRC Connection Setup, Radio Bearer

Setup, Radio Bearer Reconfiguration, Cell Update Confirmmessages

SRB Configuration UL FLEX RLC


105/229



Fixed Uplink RLC PDU size is configured with MAC-is for SRB

UL MAC header type is MAC-i/is

RLC PDU size is signalled with a fixed value of 18 bytes (144 bits)

NRT Configuration

Flexible Uplink RLC PDU size is configured with MAC-is for NRT RAB

Minimum UL RLC PDU Size = MinULRLCPDUSize+ 16

Maximum UL RLC PDU Size = MaxULRLCPDUSize


PS Streaming Configuration UL FLEX RLC


106/229



Fixed Uplink RLC PDU size is configured with MAC-is for PS Streaming


RLC PDU size is signalled with a fixed value of 42 bytes (336 bits)

CS Voice over HSPA Configuration

AMR mode or SID (kbps): 12.2 7.95 5.9 4.75 SID

UMD PDU size (bits): 264 176 136 112 56

AMR WB mode or SID (kbps): 12.65 8.85 6.6 SID

UMD PDU size (bits): 272 200 152 56

Fixed Uplink RLC PDU size is configured with MAC-is for PS Streaming


RLC PDU sizes are signalled with a fixed values according to the codec:

MAC-i PDUMAC-is PDU 1

UL FLEX RLC


107/229



Segmentation Status (SS)(2 bits)

Transmission SequenceNumber (TSN) (6 bits)

SS1

MAC-is SDU

TSN1

MAC is PDU 1

MAC-d PDU for a single logical channel

MAC-is SDU MAC-is SDU

MAC-is PDU

SI (opt.)

Padding (opt.)MAC-i Headers

MAC-i Header 0 (opt.)

LCH Id1,1

MAC-i Header 1

L11,1

F11,1

LCH Id1,k

L11,k

F11,k

Logical Channel Identity (4 bits)

Length in Bytes (L) (11 bits) Flag (1 bit)

repeated for each MAC-is SDU

MAC-is SDU is a complete, or a part of a MAC-d PDU

MAC-i PDU

MAC-i header 0 is usedin CELL_FACH to signalE-RNTI

Scheduling Information(SI) (18 bits)

Segmentation Status (SS) UL FLEX RLC


108/229



Segementation Status is included within the MAC-is header

Provides information regarding whether or not the higher layer packets have

been segmented

Example of 3 higher layer packets

No segmentationin payload

Final packet is

segmented

First packet issegmented

First and final packetsare segmented

SI00

01

10

11

Bit Rates 16-QAM + F-RLC

HSUPA 16QAM +FLEX RLC UL


109/229




Maximum transport block size = 22996 bits, MAC i/is header = 24 bits

Maximum number of RLC PDU of size 12040 bits = 1.91 Header 2*32




MAC-e re-transmission rate = 10 %

RLC re-transmissions rate = 1 %



IP header size = 20 bytes TCP header size = 36 bytes




Switching between Flexible and Fixed UL FLEX RLC


110/229



The criteria for Flexible RLC are checked when:

a new cell is added to the active set an existing cell is removed from the active set

switching between 2ms and 10ms TTI

channel type switching from DCH to E-DCH

making a state change to CELL_DCH

Fixed RLC PDU size is used after: channel type switching from E-DCH to DCH

making a state change from CELL_DCH to CELL_FACH

Counters UL FLEX RLC


111/229



The counter shown below is introduced within the RRC Signalling table

M1006C233 RB_CONFIG_FLEXIBLE_RLC_UL

The existing M1006C202RB_CONFIGURED_FLEXIBLE_RLCcounter isincremented when downlink Flexible RLC is configured

The counter shown below is introduced within the Service Level table

M1001C706 UE_SUPP_FLEX_RLC_UL

Content


112/229




MIMO 42Mbps Dual-Band HSDPA 42Mbps*

DC-HSDPA with MIMO 84Mbps*

HSUPA 16QAM*

Flexible RLC in UL*

DC-HSUPA 23 Mbps*

Other RU30 features

Background

DC HSUPA i i d d i 3GPP R l 9

DC HSUPA


113/229


125 Nokia Siemens Networks /

DC-HSUPA is introduced in 3GPP Rel.9

In UL UE sends the data over two parallel E-DCHs channels,

each one on a separate adjacent carriers In DL UE receives the data over DC-HSDPA

5 MHz 5 MHz

F1 F2

HSUPA 16QAM (11.5

Mbps)

10 MHz

DC HSUPA and

16QAM (23 Mbps)

2 UE, each using 5 MHz RF Channel

Peak Connection Throughput = 11.5 Mbps

1 UE, using 2 5 MHz RF Channels

Peak Connection Throughput = 23 Mbps

F1 F2

Dual Cel l Appro achBas ic Approach

Requirements

UE R i t

DC HSUPA


114/229



UE Requirements

UE must support E-DCH category 8 or 9


Flexi Node B must have release 2 hardware


RNC must be equipped with CDSP-DH cards


The following features must be enabled in both carriers:

DC-HSDPA, F-DPCH, Flexible RLC in UL and 2ms TTI

HSUPA 16-QAM in both carriers required for 23 Mbps

The DC-HSUPA 23 Mbps feature is optional and requires a long termRNC license for a specific number of cells


The DCellHSDPAEnabled parameter must be set to enabled for both cells

DC HSUPA

ru30 radio features

Documents

features hspa features

ru30 mimo

comopenw ru30 radio

mbps hsupa

mbpsepue hsupa

mbps dchsdpa

mbps ue dchsdpa

ulepue dchsupa