ru30 radio features

Soc Classification level Presentation / Author / Date 1 © Nokia Siemens Networks

RU30 Delta Radio Planning and Dimensioning Training

Module 1 – Features

Version 1.0 (10.2.2010)


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 materials –https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448

(Right click and Open Hyperlink)


RU30 Delta Training Agenda – Day 1-2 Features

• HSPA+ features in RU30– MIMO 42Mbps UE

– DC-HSDPA with MIMO 84Mbps EP UE

– Dual-Band HSDPA 42Mbps EP UE

– HSUPA 16QAM EP UE

– Flexible RLC in UL EP UE

– DC-HSUPA 23 Mbps EP UE

• 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 BLER EP

– Dynamic HSUPA BLER EP

– High Speed Cell_FACH EP UE

– (Fast dormancy & Fast dormancy profiling EP)– (SRVCC from LTE EP UE )

Day 1

Day 2

EP - RU30 EP releases

UE - UE support req.


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


HSPA+

HSPA enhancements in 3GPP Release 7 and beyond

• User data rates

• Voice capacity

• Battery life

• Latency

• Network throughput

• Flat architecture (iHSPA)


HSPA+ features3GPP 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-band

HSPA (> 2 carriers?)

Release 10


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 HSUPA which allows UE to take full benefit of operator’s spectrum


HSPA Data Rate Evolution

14 Mbps

21-28 Mbps

Downlink

3GPP R53GPP R6

3GPP R7

Uplink

42 Mbps84 Mbps

3GPP R83GPP R9

168 Mbps

3GPP R10+

14 Mbps

0.4 Mbps

5.8 Mbps

11 Mbps11 Mbps

23 Mbps

54 Mbps

DC-HSDPA

MIMO 64QAM

DC-HSDPA + MIMO

4-carrier HSDPA

DC-HSUPA 4-carrier HSUPA

16QAM

64QAM or MIMO 16QAM

• HSPA has data rate evolution beyond 100 Mbps

RU30


HSPA and LTE Spectral Efficiency Evolution

Evolution of HSPA efficiency

0.55

1.06 1.111.31

1.44 1.52

1.74

0.33 0.33 0.330.53

0.65 0.650.79

0.00.20.40.60.81.01.21.41.61.82.0

HS

PA

R6

HS

PA

R6

+ U

Eeq

ualiz

er

HS

PA

R7

64Q

AM

HS

PA

R8

DC

-H

SD

PA

+ 3

i, U

LIC

HS

PA

R9

DC

-H

SD

PA

+M

IMO

,U

L pr

ogre

ssiv

eP

C

HS

PA

R10

QC

-H

SD

PA

+M

IMO

LTE

R8

bp

s/H

z/ce

ll

DownlinkUplink

Today RU20

RU20 /30

RU30+


Content





– HSUPA 16QAM




Background

• 2x2 MIMO uses two parallel streams to transfer HSDPA data to 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 is specified by the release 8 version of the 3GPP specifications

MIMO 42 Mbps


Requirements MIMO 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 be release 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


Enabling the Feature (I)

MIMOWith64QAMUsage (WCEL)

Name Range Description

0 (MIMO with 64QAM disabled),

1 (MIMO with 64QAM enabled)

Default

• The MIMOWith64QAMUsage parameter must be set to enabled

• This parameter does not require object locking for modification

Parameter defines whether MIMO and 64QAM modulation can be used simultaneously for the same UE. Both features must also be separately enabled in the cell in order to make simultaneous usage possible for the UE.

0 (MIMO with 64QAM disabled)

MIMO 42 Mbps


Node B Commissioning

• Similar to RU20, the Node B commissioning parameter MIMOType should be configured 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 is created. When a cell is created for a single TX transmission, parameter value is 0. For a MIMO enabled cell, 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 one layer has MIMO enabled)

• Virtual Antenna Mapping (VAM) is supported for balancing the utilisation of power ampliers

MIMO 42 Mbps


UE Categories

• 64QAM with MIMO UE categories introduced within release 8 of the 3GPP specifications

• HSDPA UE categories 19 and 20 support 64QAM with MIMO

• Maximum transport block size is supported by UE category 20

• Maximum transport block 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


Allocating MIMO with 64QAM

• 64QAM is allocated with MIMO whenever possible

• Switching can occur when conditions change, i.e. when it becomes possible to support MIMO with 64QAM, or when it is no 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 MIMOWith64QAMUsage parameter 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 without 64QAM, or 64QAM without MIMO is possible, MIMO shall be preferred

MIMO 42 Mbps


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


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 performed without simultaneous MIMO and 64QAM, i.e. MIMO with 64QAM shall be deactivated during the SCC

• If MIMO with 64QAM cannot be used in the target cell, MIMO without 64QAM or 64QAM 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 one or more radio links over the Iur

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


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 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 × (42056 – 128) = 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 size based upon maximum RLC PDU payload of 5568 bits


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


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 - Modulation 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

Mo

du

lati

on

%

-110.0

-100.0

-90.0

-80.0

-70.0

-60.0

-50.0

-40.0

-30.0

RS

CP

n/a %

QPSK%

16QAM %

64QAM %

RSCP

Main stream modulation

along the drive

Secondary Stream modulation along the

drive

16QAM

QPSK

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


Counters

• The RRC Signalling counter table includes the counters shown below

M1006C245 RB_CONFIG_MIMO_SUCCM1006C246 RB_CONFIG_MIMO_FAILM1006C247 RB_CONFIG_64QAM_SUCCM1006C248 RB_CONFIG_64QAM_FAIL

• These counters are incremented independently for MIMO and 64QAM

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

• The counters are incremented for the WCEL object that is the primary serving cell after reconfiguration

MIMO 42 Mbps


Content




– HSUPA 16QAM





Background (I)

• RU30 introduces Dual Band Dual Cell HSDPA (DB-DC-HSDPA) for which the 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 2×5 MHz RF ChannelsPeak Throughput = 84 Mbps

F1 F2

Dual Cell ApproachBasic Approach

DC-HSDPA + MIMO + 64QAM

5 MHz

UE using 2×5 MHz RF ChannelsPeak Throughput = 42 Mbps

F1 F2

Dual Band Approach

DB-DC-HSDPA + 64QAM

5 MHz

Band x Band yBand x Band x


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-adjacent carriers 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 and capacity by favoring low frequency band for cell edge UEs and high frequency band for UEs close to the BTS

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

DB-DC-HSDPA

Might not be valid


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-HSDPA Configuration

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


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 CarrierServing cell

Secondary RF CarrierSecondary Serving cell

DB-DC-HSDPA


Requirements

UE Requirements

• HSDPA Category 21 to 28


• 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 RNC196 and RCN450)


• RAN1906 Dual Cell HSDPA 42 Mbps

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

• Multi-Band Load Balancing provides layering support for DB-DC-HSDPA but is not mandatory

DB-DC-HSDPA



DBandHSDPAEnabled (WCEL)


0 (disabled),

1 (enabled)

Default

• The DBandHSDPAEnabled parameter must be set to enabled

• This parameter requires object locking for modification

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

DB-DC-HSDPA cannot be used simultaneously with MIMO for the UE. DB-DC-HSDPA with the single cell HSUPA can be activated for the UE. MIMO configuration is not specifically restricted in the DB-DC-HSDPA cell but MIMO can be used irrespective of 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


Enabling the Feature (II)

DCellHSDPAEnabled

(WCEL)


0 (Disabled), 1 (Enabled)

Default

0 (Disabled)

• The DCellHSDPAEnabled parameter must be set to enabled for both cells belonging to the cell pair

The parameter indicates whether or not the DC HSDPA feature is enabled in the cell. Before the feature is enabled in the cell, the system checks that 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 cell setup 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

• SectorID and Tcell definitions follow the same principles as for DC-HSDPA


UE Capability (I)

• The UE signals its DB-DC-HSDPA operating band capability within the RRC Connection 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


UE Capability (II)

• The UE signals its HS-DSCH category within the RRC Connection Setup Complete message

• The UE must be category 21 to 28, i.e. a category which supports DC-HSDPA

DB-DC-HSDPA


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


Flexible Configuration

• The flexible configuration requires HSUPA to be enabled on both RF carriers 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-HSDPA UE1

DC-HSDPA UE2

HSPA UE1

HSPA UE2

Serving Cell

Serving Cell Serving Cell

Serving Cell

Sec. Serving Cell

Sec. Serving Cell

DB-DC-HSDPA


Fixed Configuration

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

DC-HSDPA UE1

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 enabled can act as:– primary serving HSDPA cell for DC-

HSDPA capable UE

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


• The RF carrier with HSUPA disabled can act as:– secondary serving HSDPA cell for DC-

HSDPA capable UE

– single carrier HSDPA serving cell for non DC-HSDPA capable UE



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 limited by the parameters:– WCEL-MaxNumberHSDPAUsers

– WCEL-MaxNumberHSDSCHMACdFlows

– WCEL-MaxNumbHSDPAUsersS

– WCEL-MaxNumbHSDSCHMACdFS

– Default value of all is 0 (not limited)

DB-DC-HSDPA


Mobility

• Switching between DB-DC-HSDPA and DC-HSDPA can be triggered by mobility– DB-DC-HSDPA to DC-HSDPA

– DC-HSDPA to DB-DC-HSDPA

• Switch occurs when selecting the secondary cell during the Serving 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


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 is selected if DC-HSUPA 16QAM can be used

2) DC-HSUPA capable cell is selected if DC-HSUPA can be used

3) DC-HSDPA with MIMO capable cell is selected if DC-HSDPA with MIMO can be used

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

5) the cell with the lowest number of existing 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


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 DCellVsMIMOPreference parameter defines the preference between 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 + MIMO

Cell 1: SC-HSDPA + MIMO



Primary cell Secondary cell

DB-DC-HSDPA


DCellVsMIMOPreference (RNC)


0 (DC-HSDPA preferred),

1 (MIMO preferred)

Default

• The DCellVsMIMOPreference parameter defines the preference between DB-DC-HSDPA and MIMO when both are enabled

This parameter determines whether the RNC primarily 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 and MIMO can be enabled in the same cell.

0

DB-DC-HSDPASimultaneous use of MIMO (II)


Simultaneous use of DC-HSUPA

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

• DC-HSUPA (RAN1905) is not supported in combination with DB-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 the primary serving cell, similar to DC-HSDPA.

DB-DC-HSDPA


FMCS Parameter Set

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

• The same DCellHSDPAFmcsId parameter 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 HSDPA allocated.

0


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 statistical multiplexing gains


Counters

• The corresponding counters as shown below are introduced within the RRC Signalling 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 updated along 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-1M1001Cx UE supporting DB-DC-HSDPA band combination Rel9-2M1001Cx UE supporting DB-DC-HSDPA band combination Rel9-3

DB-DC-HSDPA

NAMES???


Content


– Dual-Band HSDPA 42Mbps*

– DC-HSDPA with MIMO 84Mbps*

– HSUPA 16QAM*

– Flexible RLC in UL*

– DC-HSUPA 23 Mbps*



Background

• Maximum connection throughputs in RU20

DC + MIMO 84 Mbps

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 MbpsBoth supported by RAN1907

2 – carriers


Requirements

UE Requirements

• Release 9, or newer

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


• Flexi Node B must have release 2 system module. RF module can be release 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

DC + MIMO 84 Mbps



DCellAndMIMOUsage (WCEL)


0 (DC-HSDPA and MIMO disabled),

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

2 (DC-HSDPA and MIMO with 64QAM enabled)

Default

• The DCellAndMIMOUsage parameter must be set to a value of ‘2’ to achieve the peak connection throughput


Defines whether DC-HSDPA and MIMO can be used simultaneously for the same UE. Both features must be separately enabled in the cell in order to make simultaneous usage possible for the UE. The parameter also defines whether 64QAM can be used when DC-HSDPA and MIMO are simultaneously configured in use for the UE.

0

• RAN1907 DC-HSDPA with MIMO 84 Mbps is an optional feature but does not have it’s 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 but the peak connection throughput is then limited to 56 Mbps

DC + MIMO 84 Mbps



MIMOWith64QAMUsage (WCEL)


0 (MIMO with 64QAM disabled),

1 (MIMO with 64QAM enabled)

Default

• The MIMOWith64QAMUsage parameter must be set to a value of ‘1’ to allow 64QAM to be used with MIMO


This parameter defines whether MIMO and 64QAM modulation can be used simultaneously for the same UE. Both features must also be separately enabled in the cell in order to make simultaneous usage possible for the UE.

0

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

DC + MIMO 84 Mbps


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 RAB feature 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 be mapped onto HSPA then DC-HSDPA with MIMO is deactivated

DC + MIMO 84 Mbps


UE Capability (I)

• The UE signals its HS-DSCH category within the RRC Connection Setup Complete message

• The UE must be category 25 to 28 to support both MIMO and DC-HSDPA

• Only categories 27 and 28 support 64QAM, MIMO and DC-HSDPA

3GPP Release 9, TS 25.306

DC + MIMO 84 Mbps


UE categories and network features16-QAM 64-QAM enabled

(MAC-es)MIMO Enabled DC Enabled DC + MIMO

enabled

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)


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 as above

Cat 25-28

DRAFT!


UE Capability (II)

• The UE also signals its support for DC-HSDPA with MIMO within the RRC Connection 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 Connection Setup


DC-HSDPA with MIMO Throughputs (I)





• 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








coding rate of 0.98

64-QAM

MIMO + DC


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 × (42056 – 128) = 167712 bits



• MAC-ehs re-transmission rate = 10 %









MAC-ehs header size based upon maximum RLC PDU payload of 5568 bits


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 the primary 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 maximum achievable 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

• 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 if HSUPA is enabled

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

• The restrictions above are checked by O&M when DCellHSDPAEnabled, MIMOEnabled, HSUPAEnabled or SectorID parameters are modified

DC + MIMO 84 Mbps


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 with

64QAM can be used in the primary cell

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

3. The secondary cell, where the number of existing HSDPA MAC-d flows 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

DC + MIMO 84 Mbps


Selection of DC-HSDPA Secondary Cell (II)

• If DC-HSDPA with MIMO cannot 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 the primary cell

2. The secondary cell, where the number of existing HSDPA MAC-d flows 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 in general, e.g. when a site has DC-HSDPA enabled but MIMO disabled

• The secondary serving cell is only changed if the primary serving cell changes

DC + MIMO 84 Mbps


Allowing use of DC-HSDPA with MIMO

• DC-HSDPA with MIMO is used in both the primary and secondary cell whenever possible based upon normal criteria for 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 the primary cell

• When conditions change, DC-HSDPA with MIMO can be activated/de-activated during an ongoing connection

• If DC-HSDPA with MIMO is not possible but DC-HSDPA w/o MIMO or MIMO w/o DC-HSDPA is possible, the choice between DC-HSDPA and MIMO is based on the parameter DCellVsMIMOPreference

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

DC + MIMO 84 Mbps


Mobility

• DC-HSDPA with MIMO can be maintained, activated or de-activated during mobility (serving cell change and hard handover)

• The availability of DC-HSDPA with MIMO is checked in the target cell when the serving cell change or hard handover is initiated

• If DC-HSDPA with MIMO cannot be used in the target cell mobility proceeds 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 completed before inter-frequency measurements can start– DC-HSDPA with MIMO is deactivated at the same time

• DC-HSDPA with MIMO is not supported across the Iur• SRNC does not configure DC-HSDPA with MIMO if there are radio links

over the Iur in the active set

DC + MIMO 84 Mbps


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 RFcarriers are transferred in a TimeDivision Multiplexing (TDM) manner– differs to CQI reporting for DC-HSDPA

without MIMO in which case both CQIreports 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

w0…w9

HARQ-ACK

Concatenation

pci0,pci1

Type A CQI

cqi0…cqi7

PCI

a0…a9 or a0…a6

Type B CQI

cqi0…cqi4

Channel Coding

b0…b19

or

DC + MIMO 84 Mbps


CQI for MIMO (I)

• MIMO connections report CQI values on the HS-DPCCH

• MIMO connections use two types of CQI– Type A – applicable to dual stream, with support for single stream

– Type B – applicable 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

CQI1 corresponds to TBS which could be received using the preferred primary precoding vector (range 0 to 14)

CQI2 corresponds to TBS which could be received using the precoding vector which is orthogonal to the preferred primary precoding vector (range 0 to 14)

CQIS corresponds to TBS which could be received using the preferred primary precoding vector (0 to 30)

CQI = CQIs (range 0 to 30)

Type B

DC + MIMO 84 Mbps


CQI for MIMO (II)

• 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 current channel 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

DC + MIMO 84 Mbps


CQI Mapping Tables

• CQI mapping tables applicable to UE categories 25 to 28 are shown

• UE categories 25 and 26 do not support 64QAM

DC + MIMO 84 Mbps


MaxBitRateNRTMACDFlow

• 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 MaxBitRateNRTMACDFlow during 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 in earlier releases– The value 0 (RN6.0) / 65535 (RN5.0 and before) means that the

HSDPA peak rate is not limited by the RNC

– The value 0 is the new default and special value

DC + MIMO 84 Mbps


Theoretical performanceThe 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-DPCCH

S-CPICH needed for MIMO

DC + MIMO 84 Mbps


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)

Th

rou

gh

pu

t [M

bp

s]

MIMO

64QAM

16QAM

Practical performance of Single cell 64-QAM and MIMO• In a good RF conditions, there is clear benefit of using MIMO or 64QAM instead of

16QAM. In cell edge conditions, the benefit is less.– NOTE: Some SW improvement done to BTS after test, MIMO performance to be verified.

16QAM modulation used instead of 64QAM in Loc6



Practical performance of Dual cell 64-QAM, single cell 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.39.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..-85dBm)

Loc5 (-55..-60dBm)

DL

ap

p t

p (

Mb

ps

)

DC HSDPA

MIMO

64QAM



Counters (I)

• The Service Level table includes the counters shown below

M1001C707 UE_SUPP_HSDSCH_CLASS_25_26M1001C708 UE_SUPP_HSDSCH_CLASS_27_28M1001C709 ACCESS_STRATUM_REL_IND_9

• The Packet Call table includes the counters shown below

M1022C223 SUCC_SWI_DCHSDPA_TO_SCHSDPAM1022C224 SUCC_SWI_SCHSDPA_TO_DCHSDPA

• These counters are not specific for DC-HSDPA with MIMO, but also apply to basic DC-HSDPA

DC + MIMO 84 Mbps


Counters (II)

• 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_S M5000C431 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

DC + MIMO 84 Mbps


Content




– HSUPA 16QAM





Background

• 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 and

maximum 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 defined by 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 is not available

HSUPA 16QAM


Requirements

UE Requirements

• HSUPA Category 7




• CDSP-DH card in RNC (RAN1226 HSPA Peak Rate Upgrade for RNC196 and 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 rise for the peak data rate

HSUPA 16QAM


UE Categories

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

• Signalled to the RNC within the RRC Connection Setup Complete message

HSUPA 16QAM


Bit Rates (I)





• Number of E-DPDCH codes = 2

=> Aggregate Symbol Rate = 5.76 Msps

• Number of bits per Symbol = 2 (generated by 4PAM modulation)






coding rate of 0.998




HSUPA 16QAM



• 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 %









Bit Rates (II) HSUPA 16QAM



• 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













Bit Rates (III) – F-RLC HSUPA 16QAM + FLEX RLC UL



HSUPA16QAMAllowed (WCEL)


0 (disabled),

1 (enabled)

Default

• The HSUPA16QAMAllowed parameter must be set to enabled


This parameter is used to define whether the RNC allows the usage of 16QAM modulation for HSUPA. If the parameter is enabled, then the RNC can use the HSUPA 16QAM feature in a cell. If the parameter is disabled, then the RNC cannot use the HSUPA 16QAM feature in a cell. The HSUPA 16QAM is allowed in the cell if the MaxTotalUplinkSymbolRate 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

HSUPA 16QAM



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 MaxTotalUplinkSymbolRate parameter 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 in the cell. The lowest parameter value among the parameter values of the cells that belong to the E-DCH active set is used when the E-DCH is allocated. The signaled value is updated when a soft handover branch addition or deletion occurs and the lowest value changes. Note: Upgrade is not always possible due to capacity reasons in the RNC.

In case "HSUPA 2 Mbps" feature is active (state "On" and exist) but "HSUPA 5.8 Mbps" feature is not active, 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.

HSUPA 16QAM


Allocation of 16QAM HSUPA

• 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 value defined by HSUPAUserLimit16QAM

HSUPA 16QAM


Maximum Number of 16QAM Users

HSUPAUserLimit16QAM

(WCEL)


1 to 10, step 2

Default

• The HSUPAUserLimit16QAM parameter defines the maximum allowed number of HSUPA 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 active HSUPA users in a cell in determining the usage of HSUPA 16QAM with both fixed and flexible UL RLC. It is also used in determining the fixed UL RLC PDU size with MAC-es.

For flexible UL RLC: If the amount of active HSUPA users in a cell is lower than or equal to the threshold, defined by this parameter, the HSUPA 16QAM usage is allowed 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, defined by this parameter, the fixed UL RLC PDU size shall be 656 bits. Otherwise an UL RLC PDU size of 336 bits shall be used. The HSUPA 16QAM usage is allowed if the UL RLC PDU size is 656 bits.

2

HSUPA 16QAM


Modulation

• Modulation applied to each individual E-DPDCH is BPSK or 4PAM (Pulse Amplitude Modulation)

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

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

HSUPA 16QAM

QPSK 16QAM

2 bits per symbol 4 bits per symbol

BPSK

BP

SK

4PA

M

4PAM


Modulation Switching

• The E-DPDCH configuration is increased to 2SF2 + 2SF4 prior to switching modulation scheme

• The UE then automatically switches to 16QAM when the quantity 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 scheme when the transport block size defined by the E-TFCI is sufficiently 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)

HSUPA 16QAM


Transport Block Size Table (I)

• 3GPP TS 25.321 specifies transport block size tables 2 and 3 for the 2 ms TTI 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

HSUPA 16QAM


RLC PDU Size

• 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 rate is 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

HSUPA 16QAM


Serving Grant Table

• Serving Grant Table 2 has been introduced within 3GPP TS 25.321 for the purposes of 16QAM

• Allows increased power offsets

HSUPA 16QAM

Table 1 Table 2


E-AGCH• The table used to map the signalled E-AGCH values to a power offset is

changed when 16QAM is used

HSUPA 16QAM


Uplink Interference Power

• Uplink interference power generated by 16QAM HSUPA throughputs is relatively high

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

HSUPA 16QAM

23456789

10111213141516171819202122232425

3840 5760 6600 7600 8990 10900

L1 Bitrate [kbps]

No

ise

Ris

e [d

B]

Rake

GRake


Counters

• The counters shown below are introduced for HSUPA 16QAM

M5000C359 EDCH_16QAM_UE_ACT_SUMM5000C360 MACE_PDU_RX_COR_16QAMM5000C361 MACE_PDU_RX_INCORR_16QAM

HSUPA 16QAM


Content




– HSUPA 16QAM*





Background (I)

Segmentation

UE - Pre-Release 8

RLC

MAC-e/es

RLC

Segmentation / Concatenation

MAC-i/is

UE - Flexible RLC

Concatenation / Padding

UL FLEX RLC

• Prior to 3GPP Rel. 8, the RLC layer within the UE segmented large higher layer packets into many small packets

• The MAC-e/es layer then had to concatenate and pad these small packets to fit within the variable size HSUPA transport block

• Flexible RLC helps to avoid this requirement for segmentation and subsequent concatenation

• The MAC-i/is layer segments the higher layer packets such that they fit within the HSUPA transport block

• There is a reduced requirement for RLC headers and padding


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

Background (II)

• Graph below illustrates the difference in RLC overhead (header and padding) 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 all cases, i.e. does not account for the Length Indicator

Higher Layer Packet Size (bytes)

RLC

Ove

rhea

dUL FLEX RLC


Background (III)

• The RLC layer uses a 12 bit Sequence Number (SN) for Acknowledged Mode (AM) RLC (range from 0 to 4095)

• RLC layer stalls if the sequence number 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 of 656 bits

• Increasing the HSUPA throughput further, 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

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

UL FLEX RLC


Requirements

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

UL FLEX RLC


RNC Configuration

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

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

UL FLEX RLC

SRB NRT PS RT PS CS Voice over 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 FP Type 2

E-DCH FP Type 2

E-DCH FP Type 1

E-DCH FP Type 2

E-DCH FP Type 1

E-DCH FP Type 2

Interactive & background Streaming


Enabling Flexible RLC in Uplink

FlexULRLCEnabled

(RNC)

This parameter enables/disables use of feature Flexible UL RLC. If the parameter is enabled (1), then feature Flexible UL RLC is used in the RNC. If the parameter is disabled (0), then feature Flexible UL RLC is not used in the RNC.



Default

0

• RNC databuild parameter FlexULRLCEnabled used to enable/disable


UL FLEX RLC

• 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

• 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 indicate support of uplink flexible RLC (in contrast to MAC-ehs for downlink flexible RLC)


Selecting Uplink Flexible RLC UL FLEX RLC

• The following criteria must be satisfied for all cells within the E-DCH Active Set:– the cell is flexible UL RLC capable– the UE is flexible UL RLC capable– the FlexULRLCEnabled parameter 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 FRAME type 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 connections are released


Protocol Stack Changes

Without Uplink Flexible RLC

With Uplink Flexible RLC

WCDMA L1

UE SRNC

Node B

MAC-e/es

RLCMAC-d

WCDMA L1

MAC-e

Transport

Frame Protocol

Transport

Frame Protocol

RLCMAC-d

IubUu

MAC-es

WCDMA L1

UE SRNC

Node B

MAC-i/is

RLCMAC-d

WCDMA L1

MAC-i

Transport

Frame Protocol

Transport

Frame Protocol

RLCMAC-d

IubUu

MAC-is

UL FLEX RLC


RLC Layer (I)

• 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 the maximum RLC PDU size

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

• Non-configurable RNC databuild parameter, MaxULRLCPDUSize defines the maximum size in RU30

MaxULRLCPDUSize

(RNC)


16 to 12040 bit, step 8 bit

Default

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

Non-Configurable

UL FLEX RLC


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, MinULRLCPDUSize defines the minimum size in RU30

The minimum size for uplink RLC PDU. The minimum UL RLC PDU size is used with flexible UL RLC and MAC-is. The minimum size consists of payload size and header of 16 bits (Length Indicator is not included).

Non-Configurable

RLC Layer (II)

AM RLC PDU• AM RLC PDU structure remains the same with Flexible RLC

• header has a minimum length of 16 bits

• Sequence number has a length of 12 bits (compared to 7 bits for Unacknowledged Mode RLC). Larger range required to allow a larger transmit window.

• If MaxULRLCPDUSize > 1008 bits, the Length Indicator size is 15-bits

UL FLEX RLC


RRC Layer UL FLEX RLC

• The RRC layer provides the UE with information regarding uplink 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 Confirm messages


SRB Configuration

• 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


UL FLEX RLC


PS Streaming Configuration

• 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:

UL FLEX RLC


MAC-i PDU

• Segmentation Status (SS) (2 bits)

• Transmission Sequence Number (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 used in CELL_FACH to signal E-RNTI

• Scheduling Information (SI) (18 bits)

UL FLEX RLC


Segmentation Status (SS)

• 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 segmentation in payload

Final packet is segmented

First packet is segmented

First and final packets are segmented

SI

00

01

10

11

UL FLEX RLC

















Bit Rates – 16-QAM + F-RLC HSUPA 16QAM + FLEX RLC UL


Switching between Flexible and Fixed UL FLEX RLC

• 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

• The counter shown below is introduced within the RRC Signalling table

M1006C233 RB_CONFIG_FLEXIBLE_RLC_UL

• The existing M1006C202 RB_CONFIGURED_FLEXIBLE_RLC counter is incremented when downlink Flexible RLC is configured

• The counter shown below is introduced within the Service Level table

M1001C706 UE_SUPP_FLEX_RLC_UL

UL FLEX RLC


Content




– HSUPA 16QAM*





Background

• 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 and16QAM (23 Mbps)

2 UE, each using 5 MHz RF ChannelPeak Connection Throughput = 11.5 Mbps

1 UE, using 2 × 5 MHz RF ChannelsPeak Connection Throughput = 23 Mbps

F1 F2

Dual Cell ApproachBasic Approach

DC HSUPA


Requirements

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

DC HSUPA

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



• The DCellHSDPAEnabled parameter must be set to enabled for both cells belonging to the cell pair

• Two cells form a potential DC HSUPA cell pair when they have adjacent RF carriers, belong to the same sector and have the same Tcell value

• WCEL - UARFCN parameter defines the downlink channel number and the downlink carrier frequency of the cell

• WCEL - SectorID parameter gives a unique identifier to a sector of the base station where the cell belongs to

• WCEL - Tcell parameter defines the start of SCH, CPICH, Primary CCPCH and DL Scrambling Code(s) in a cell relative to BFN

• WCEL - HSUPA2MSTTIEnabled must be set ‘Enabled’

• WCEL - FDPCHEnabled always set ‘Enabled’ when DC-HSUPA is enabled in cell, not modifiable

• WCEL - DCellHSDPAEnabled must be set ‘Enabled’

• RNC - FlexULRLCEnabled must be set ‘Enabled’

DC HSUPA

Name Range Default Description

DCellHSUPAEnabled

(WCEL)


0 (Disabled) The parameter indicates whether or not the DC HSUPA feature is enabled in the cell.


Other parameters

• The MaxNumberEDCHCell, MaxNumberEDCHLCG and new parameter MaxNumberEDCHS parameters define the maximum allowed number of SC-E-DCH and DC-E-DCH users in the cell, LCG and scheduler respectively– By default not limited

– DC-E-DCH user is counted only in the primary cell and once per local cell group

– Parameters MaxNumberHSDSCHMACdFlows, MaxNumberHSDPAUsers, MaxNumbHSDPAUsersS and MaxNumbHSDSCHMACdFS can also limit the number of users

• New PFLDCHSUNRT, PFLDCHSUStr, PFLDCHSUAMR and PFLDCHSUAMRNRT parameters used to define preferred DC-HSUPA layer for Multi Band Load Balancing feature (To be confirmed)

DC HSUPA


UE Categories

• UE E-DCH category is signalled to the RNC within the RRC Connection Setup Complete message

• Cat 1-6: QPSK

• Cat 7: 16-QAM

• Cat-8: QPSK + DC-HSUPA

• Cat-9: 16-QAM + DC-HSUPA

DC HSUPA


Channel type selection, DC-HSUPAactivation• Allocation of DC HUDPA is tried always when it is possible

– When existing algorithms trigger channel type switch from DCH to E-DCH (UL)– HSUPA is possible to allocate in the all the cells in the active sets in both primary and

secondary carrier– DC-E-DCH is possible to allocate in the all the cells in the active sets in both primary and

secondary carrier – Allowed service combination used– No links over Iur in active set– DC-HSDPA allocation is possible

• DC HSUPA can be configured to the UE by including Uplink secondary cell info FDD IE into one of the following messages– Active Set Update – Cell Update Confirm– Radio Bearer Setup/Reconfiguration/Release

• DC HSUPA configuration is removed from the UE by leaving out the Uplink secondary cell info FDD IE from the RRC messages

• DC HSUPA is activated/deactivated by the serving BTS– Uses HS-SCCH orders to deactivate (respectively activate) the secondary serving E-DCH

radio link – Serving BTS informs RNC after successful activation, RNC send request to non-serving

BTSs

DC HSUPA


Examplesignalling (1/2)• Example of DC-HSUPA

setting when UE is in Cell_FACH state when UL (Measurement Report from UE) or DL (RNC internal message) capacity request is received

BTS RNCUE

UE in (HS-)Cell_FACH state

UL or DL capacity request, criterias to allocate DC-HSUPA filled.

SRB on HSPA, Flexible RLC UL, 2 MS TTI, DC-HSDPA to be allocated

Radio Link Setup Request

(DC-HSUPA parameters, DC deactivated)

Radio Link Setup Response (DC-HSUPA parameters)

Radio Bearer Reconfiguration(DC-HSUPA parameters)

Radio Bearer Reconfiguration Complete

NBAP: Secondary UL Frequency Update Indication(Activated)

Radio Link Restoration

BTS decides when DC HSUPA activated

No actions in RNC (no SHO branches)

NBAP: Secondary UL Frequency Update Indication(De-Activated)

BTS decides when DC HSUPA de-activated

No actions in RNC (no SHO branches)

Transport setup, IP or ATM

DC HSUPA

HS-SCCH order activation

HS-SCCH order de-activation


Example signalling (2/2)

• During the initial radio link set up, the secondary carrier of DC capable UE is in de-activated state (state is signaled by RNC)

• In order to activate secondary carrier: – Firstly, RNC configures dual carrier by NBAP and RRC signalling,

– Secondly, Secondary carrier may be activated (and also deactivated) in two ways: By the Node-B using HS-SCCH orders (fast way) By the RNC by RL reconfiguration (slow way)

2. HS-SCCH order activation

3.Acknowledge

1. Configuration of dual carrier mode by NBAP/RRC signalling

UE Serving Node B SRNC

4.RL activation indication

7. Proceed to request

activation for Non Serving

Cells5. UE acquires sync in secondary cell

6. RL Restore Indication

DC HSUPA


Supported RAB Combinations

• Supported services– 1-3 NRT PS RABs + SRB on DC-HSUPA

– 1-3 NRT PS RABs on DCH0/0 + SRB on DC-HSUPA

• DC-HSUPA is not allocated with services– Standalone SRB

– Conversational service (like AMR)

– Streaming service

• No parallel operation on DPDCH (HSPA only connection)

• Iur-not supported in current RU 30 timeframe

DC HSUPA


Connection Establishment

• RRC Connection Request message does not indicate whether or not the UE supports DC-HSUPA

• RRC Connection Setup Complete message includes UE HSUPA Category information

DC HSUPA

If the UE supports Dual Cell E-DCH operation


Physical Channels• CQIs are reported only to the primary serving cell

– HS-DPCCH only on primary serving cell (same config as with DC-HSDPA)

• Otherwise both cells provide the full set of physical channels– HSPA data UL & DL in both cells– UL/DL Inner loop power control in both cell– HARQ ACK/NACK on both cells– HSUPA scheduling in both cells

DC HSUPA

HS-SCCH

HS-SCCH

HS-PDSCH

HS-PDSCH

HS-DPCCH

DPCCH

F-DPCH

E-DPDCH

E-DPCCH

Downlink Channels

Uplink Channels

Primary RF CarrierServing cell

Secondary RF CarrierSecondary Serving cell

F-DPCH

E-AGCH, RGCH, HICH

E-AGCH, RGCH, HICH DPCCH

E-DPDCH

E-DPCCH


Scheduling in BTS and max bit rate

• HSUPA scheduling is independent on both carriers– BTS sends E-AGCH and E-RGCH in both carriers

• UE divides transmission power between carriers (even??)

• Maximum total uplink symbol rate– BTS and cell capability of all active set cells in both primary and

secondary layer shall be checked (minimum used??)

• Maximum uplink user bit rate of the RAB limitation shall be defined only in the primary layer– Bit rate allowed in both primary and secondary layer Double max bit

rate when DC-HSUPA used

DC HSUPA


Mobility

• Serving cell change (SCC) on the basis of measured results on primary frequency

• Primary and secondary E-DCH active sets controlled based on measured CPICH Ec/No results (Events 1A, 1B, 1C) on primary layer– Active set on secondary layer updated simultaneously with primary layer

• HSUPA radio link sets of primary and secondary carrier can be different– Primary and Secondary E-DCH active set– Serving E-DCH cells are always in same sector

Same as DC-HSDPA cell pair

– Non-serving radio links can be in different sectors or BTSs

• Compressed mode is supported during DC-HSUPA when HSUPA Inter-frequency Handover feature is enabled– Not when UL quality or UE power triggered IFHO

• Overall UL bitrate of SHO branches limited to 46 Mbps – Softer HO branched not counted– Limited by frame protocol layer throughput per user

DC HSUPA


Layering

• DC-HSUPA has no effect on layering features:– HSPA Capability Based Handover (HSCAHO)

– DC HSDPA Capability Based Handover (DCellCAHO)

– MIMO Capability Based Handover (MIMOCAHO)

– Directed RRC connection setup for HSDPA layer

– HSDPA layering for UEs in common channels

• Own preferred layer definition in Multi-Band Load Balancing (not confirmed)– PFLDCHSUNRT, PFLDCHSUStr, PFLDCHSUAMR and

PFLDCHSUAMRNRT parameters used to define preferred DC-HSUPA layer

DC HSUPA


Bit Rates (I)Physical Layer (based upon Physical Channel capability)





=> Aggregate Symbol Rate = 5.76 Msps

• Number of bits per Symbol = 2 (generated by 4PAM modulation)

=> Aggregate Symbol Rate = 11.52 Mbps

• Number of carriers = 2







=> Bit Rate = 22.996 Mps (peak)coding rate of 0.998




DC HSUPA





=> RLC payload = 2 x 22932 bits












Bit Rates (II) DC HSUPA


Performance

• DC-HSDPA improves user bit rates and cell capacity by allowing dynamic usage of two HSDPA carriers for a HSDPA user

• Improvement is due to multiple mechanisms– Higher peak bit rate via combination of bit rate of two carriers

– Cell capacity gain via statistical multiplexing of larger number of users

– Performance improvement in fading conditions by frequency selective scheduling and carrier specific link adaptation separate power control loops for both carriers

DC HSDPA


Performance - Sector t-put gain

Av. # of users per sector Av DC Sector TP Av. SC Sector TP Av Sector TP Gain1.00 4.1875 1.7 1.461.48 5 2 1.502.00 5 2 1.504.00 4.875 1.875 1.608.00 3.875 1.6875 1.30

-3 -2 -1 0 1 2 3 40

1

2

3

4

5

6

Average number of users per sector 2x

Ave

rag

e S

ect

or

Th

rou

gh

pu

t [M

bit/

s]EUL Full Buffer Results

Single Carrier

Dual CarrierDouble Single Carriers

146%

130%

160%

150%

[Graph source: 3GPP TSG RAN WG1 Meeting #55bis R1-090411]

Gain from DC-HSUPA is

assumed to be 30% per sector,

i.e. 15% per carrier

19 NodeB/3 sectors with wrap around

Full buffer traffic model

Inter site distance 1000m

10 dB indoor penetration

No of users per sector (av.) 0.2, 0.4, 0.6, 0.8, 1, 1.5, 2, 4, 6, 10.

In general, the gain results from doubling the bandwidth and also from statistical multiplexing & frequency diversity.


• Service Level table (M1001)– Cxx1: Number of RRC connection establishments by UEs supporting DC-HSUPA– Cxx1: Number of RRC connection establishments by UEs supporting E-DCH category-8.– Cxx2: Number of RRC connection establishments by UEs supporting E-DCH category-9

• The RRC Signalling counter table (M1006) includes the counters– Cxx1: Number of Radio Bearers successfully configured to use DC-HSUPA

• Packet call table (M1022) – Cxx1: Number of successful switches from DC-HSUPA to SC-HSUPA– Cxx2: Number of successful switches from SC-HSUPA to DC-HSUPA

• Cell throughput table (M1023)– Cxx1: DC-HSUPA primary carrier Iub data volume– Cxx2: DC-HSUPA secondary carrier Iub data volume– Old E-DCH counter count the total data volume

• The counters are incremented for the WCEL object that is the primary serving frequency• BTS counter

– 1. SUM OF DC HSUPA USERS – 2. MAX NUMBER OF DC HSUPA USERS– 3. SUM OF ACTIVE DC HSUPA USERS USING 2C– 4. SUM OF ACTIVE DC HSUPA USERS USING 1C

Counters DC HSUPA


Content

• HSPA+ features in RU30

• Other RU30 features– Frequency Domain Equalizer

– HSUPA Interference Cancellation Receiver

– HSUPA Inter-frequency Handover

– Multi-Band Load Balancing

– HSPA 128 users per cell

– HSUPA Downlink Physical Channel Power Control

– Dynamic HSDPA BLER*

– Dynamic HSUPA BLER*

– High Speed Cell_FACH*

– SRVCC from LTE*


Background (I)

• Prior to RU30 the Node B receiver was based upon RAKE receiver technology

• RU30 introduces:– Frequency Domain Equaliser (FDE) (RAN1702)

– HSUPA Interference Cancellation (RAN1308)

• These features are most effective when used in combination but can also be enabled individually

• Without these features, the noise rise generated by the uplink throughputs associated with HSPA+ becomes prohibitively high

FDE

PrxMaxTargetBTS

Uplink Noise Power PrxMaxTargetBTS

Uplink Noise Power

4 Mbps 8 Mbps

RAKE FDE


Background (II)

• FDE is simpler to implement than a traditional time domain equalizer

• FDE captures the energy from all multipath components and allows up to 2x higher 16QAM data rates compared to a RAKE receiver

• FDE efficiently removes inter-symbol interference arising from user's own signal due to multipath propagation

• RAKE is unable to receive high data rates even in total absence of other cell interference– short spreading codes used for high HSUPA data rates are vulnerable to inter-

symbol interference

• FDE can remove inter-symbol interference, leaving other users of the same cell and surrounding cells to be the main limiting factors for UL data rates

• Interference from other users of the own cell can be alleviated using RAN1308 HSUPA interference cancellation

FDE


Requirements

UE Requirements

• None

Network Hardware Requirements• Flexi Node B must have release 2 system module




• Basic HSUPA, HSUPA BTS Packet Scheduler, HSUPA Basic RRM

FDE

• Prerequisite for HSUPA 16QAM

• Performance improved when used in combination with Interference Cancellation


Enabling the Feature

fdeEnabled (BTSSC)


False (0),

True (1)

Default

• FDE is enabled during Node B commissioning

• The Node B commissioning parameter fdeEnabled must be set to ‘True’

Parameter selects whether Frequency Domain Equalizer feature is activated in the BTS.

Note: If parameter missing from the SCF, then feature is disabled.

False (0)

• RAN1702 Frequency Domain Equaliser is an optional feature which requires a WBTS licence

FDE


Radio Propagation Challenges

• The propagation channel introduces:– multipath delay – delay spread components arrive at the receiver

– phase changes – each delay spread component has a different phase

– amplitude changes – each delay spread component has a different amplitude

FDE


RAKE Receiver

• RAKE receiver synchronises with each delay spread component

• RAKE fingers are allocated to the strongest delay spread components

• RAKE fingers– track and compensate for phase changes prior to combining

– weight the amplitude of delay spread components prior to combining

• Outputs from RAKE fingers are combined and the result is forwarded for further physical layer processing

• RAKE delivers adequate performance for data rates below 2 Mbps

FDE


Frequency Domain Equaliser (FDE)

• FDE is a combination of linear equalisation and fast convolution

• HSUPA 16QAM requires FDE to achieve data rates up to 11.5 Mbps with 2 x SF2 + 2 x SF4

• The Linear Minimum Mean Square Error (LMMSE) approach for FDE provides an optimal linear estimate of the transmitted signal accounting for both the radio channel and interference plus noise

FDE


Distortive channel effects have to be handled

channel

noise

h(k)

y(k)x(k)

transmitted signal

noise

)()()()( knkhkxky

)(~)()(~)()()()()()( knkxknkekhkxkekykr

filter filtered noise

Linear Equaliser

• Convolution can be used to compensate for the radio channel

• Convolution linearly weights samples of the received time domain signal using equaliser coefficients and subsequently sums to generate the output

• Convolution is relatively demanding in terms of computation

• Convolution can be replaced by multiplication if completed in the frequency domain

received signal

FDE


FDE scheme

signal FFT

pilotChannel

estimation

MMSE filter coefficient calculation

IFFTDespreding

and detection

bits

Time domain

Frequency domain

Linear Equaliser & Fast Convolution FDE

• FDE is a combination of linear equalisation and fast convolution

• FDE reduces the impact of inter-symbol interference arising from a user’s own signal due to multi-path propagation

• FDE is applied to connections with 2SF2 + 2SF4 (QPSK or 16QAM)


non-boosted mode

DPCCH DPCCH

E-DPCCH E-DPCCH

E-DPDCH

E-DPDCH

low E-TFC high E-TFC

boosted mode

DPCCH DPCCH

E-DPCCH

E-DPCCHE-DPDCH

E-DPDCH

low E-TFC high E-TFC

non-boosted mode boosted mode

FDEE-DPCCH Boosted Mode (I)

• The performance of FDE is dependent upon accurate channel estimation– E-DPCCH boosted mode allows improved channel estimation

• E-DPCCH boosted mode links the transmit power of the E-DPCCH to the transmit power of the E-DPDCH instead of the DPCCH


E-DPCCH Boosted Mode (II) FDE

• It is not mandatory for UE to support E-DPCCH power boosting

• UE signal their support for E-DPCCH power boosting within the RRC Connection Setup Complete message

Requires release 7 or newer UE


Data rate vs average CIR @ 10% BLER after 1st Tx (Ped A 3)

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

-20.0 -15.0 -10.0 -5.0 0.0 5.0 10.0 15.0

CIR @ 10% BLER

Tp

[kb

its]

FDE 16QAM -boosted

FDE QPSK

RAKE QPSK

Throughput vs average CIR @ 10% BLER after 1st Tx (PA3) -> to be used for coverage dimensioning purposes

FDE + 16QAM => 77,8% higher Tp is achievable

FDE + QPSK => 22,2% higher Tp is achievable

FDE allows higher data rates for users closer to

the antenna

Link Level Simulations – PA3 FDE


Throughput vs avearage CIR @ 10% BLER after 1st transmission (VA 3)

0

1000

2000

3000

4000

5000

6000

7000

8000

-20 -15 -10 -5 0 5 10 15

CIR @ 10% BLER

Tp

[kb

its]

RAKE QPSK

FDE 16QAM - boosted

FDE QPSK

FDE allows higher data rates for users

closer to the antenna

FDE + 16QAM =>75% higher Tp is achievable

FDE + QPSK => 25% higher Tp is achievable

Throughput vs average CIR @ 10% BLER after 1st Tx (VA3) -> to be used for coverage dimensioning purposes

Link Level Simulations – VA3 FDE


Data rate vs average CIR @ 10% BLER after 1st Tx (Veh A 30)

0

1000

2000

3000

4000

5000

6000

7000

-15 -10 -5 0 5 10 15CIR @ 10% BLER

Tp

[k

bit

s]

FDE 16 QAM -boosted

FDE QPSK

RAKE QPSK

FDE allows higher data rates for users

closer to the antenna

FDE + 16QAM => 50% higher Tp is achievable

FDE + QPSK => 25% higher Tp is achievable

Throughput vs average CIR @ 10% BLER after 1st Tx (VA30) -> to be used for coverage dimensioning purposes

Link Level Simulations – VA30 FDE


RAKE + QPSK 0% 0% 0%FDE + QPSK 14.57% 8.45% 5.33%

FDE + 16QAM 29.11% 10% 6.11%Receiver+modulation

Ped A3 Veh A3 Veh A30Pole capacity gain

Channel model

Cell Capacity FDE

• The capacity benefit (increase in cell throughput) has been quantified for both the QPSK and 16QAM modulation schemes

• The increase in capacity is greatest for 16QAM in a Pedestrian environment


Counters

• This feature does not introduce new counters

• Existing HSUPA throughput KPI should experience an increase

FDE


Content











– SRVCC from LTE*


Background (I) HSUPA IC

• Target of the HSUPA interference cancellation is to– Decrease interference from HSUPA 2 ms TTI users on other UL

channels (Basic PIC, RAN1308) Improved coverage e.g. for AMR calls existing in parallel with peak rate

users

– Decrease interference from HSUPA 2 ms TTI users on each other (Enhanced PIC, RAN2250) Enable for large peak HSUPA data rates (also 16-QAM)

• HSUPA interference cancellation is implemented on the BTS SW and it utilises non-linear interference cancellation method called PIC (parallel interference cancellation)– RAN1308 implements basic PIC

– RAN2250 implements enhanced PIC


Basic PIC method

• High bit rate HSUPA 2ms connections are demodulated first

• Interference from HSUPA 2ms connections is cancelled from incoming signal and other connections are demodulated from the resulting signal

HSUPA IC

Re-modulate2ms HSUPA

De-modulate2ms HSUPA

2ms HSUPA

user data

UL signal fromantenna

De-modulateother

10ms HSUPA

DCHuser data

2ms HSUPAinterferencecancelled

“IC users”

“Non IC users”


Enhanced PIC method

• Also HSUPA 2ms connections are demodulated after interference cancellation and residual stream reconstruction (RSR) process

HSUPA IC

Re-modulate2ms HSUPA

De-modulate2ms HSUPA

2ms HSUPA

user data

UL signal fromantenna

De-modall

10ms HSUPA

DCHuser data

2ms HSUPAinterferencecancelled

RSR De-mod2ms HS“IC users”

“Non IC users”

“IC users”


Effect of interference cancellation• Part of received total wideband power is cancelled

– RTWP = PNoise + PR99 + P10ms + P2ms

– Residual RTWP = PNoise + PR99 + P10ms + (1-β) * P2ms

• Achievable interference reduction factor β is highly dependent on the– Quality of the signal that should be cancelled, that is the 2ms TTI UEs

– Data rate of the UE to be canceled

– Radio channel of the UE: Multi-path profile, Velocity of the UE

Noise

R99 users

HSUPA 10 ms

HSUPA 2 ms

Noise

R99 users

HSUPA 10 ms

HSUPA 2 ms

HSUPA IC


HSUPA scheduling with IC

• BTS uses two scheduling targets for HSUPA– RTWP < PrxMaxOrigTargetBTS

– Residual RTWP < PrxMaxTargetBTS

• Variations in interference reduction factor or even loss of IC can cause fast changes in Residual RTWP– Emergency control in BTS: Modify SIR targets

, decrease grants

Noise

R99 users

HSUPA 10 ms

HSUPA 2 ms

Noise

R99 users

HSUPA 10 ms

HSUPA 2 ms

PrxMaxOrigTargetBTS

PrxMaxTargetBTS

RTWP

RRTWP,Residual RTWP

Noise

R99 users

HSUPA 10 ms

HSUPA 2 ms

Lossof IC

ResidualRTWP

HSUPA IC


UL power measurements with HSUPA IC

• The BTS shall support the following additional measurements:– Residual received total wide band power

BTS sends this power value in private RRI message, IE 'Residual Received Total Wide Band Power Value'

• Other UL measurements as without HSUPA IC– E-DCH load for IC users on original stream

IE ‘ E-DCH Load Value’

– Received Total Wide Band Power IE 'Received Total Wide Band Power value'

HSUPA IC


UL load control with HSUPA IC ??

• RRM shall use value of the new management parameter PrxMaxOrigTargetBTS for target Prx_target_EDCH if basic PIC is used in the cell– Used in PrxTargetPS adjustment for R99 PS NRT UL scheduling

• When basic PIC is applied, LC uses the received interference power before a part of the interference is cancelled (stored in IE 'Received Total Wide Band Power Value' of private message) for calculation of the averaged received total non-EDCH interference power

HSUPA IC


UL load control with Enhanced HSUPA IC??

• RRM shall use value of the management parameter PrxMaxTargetBTS for target Prx_target_EDCH

• RRM shall consider PrxTotal as common residual stream power in the detection of E-DCH congestion relating to adjustment of the Prx_target_PS

• RRM shall detect level of used interference cancellation based on value of IE ‘PIC Level’

• LC shall consider RTWP as common residual stream power when LC produces the averaged received total non-EDCH interference power of the E-DCH cell for UL NRT DCH resource allocation

• RRM shall consider PrxTotal as common residual stream power in PrxNoise adjustment

• RRM shall calculate the Received E-DCH Power share on residual stream from BTS measured and reported received E-DCH Power Share on original stream

• RRM shall use the Received E-DCH Power share on residual stream when RRM calculates the load factor LEDCH,CELL.

HSUPA IC


Requirements

UE Requirements


• Flexi Node B must have release 2 hardware




• HSUPA 2 ms TTI

• The HSUPA IC feature is optional and requires a BTS license key

HSUPA IC


PIC pool and state

• A PIC (Parallel Interference Cancellation) pool represents a set of cells within one BTS that are candidates for interference cancellation– PIC pool configuration is done by the operator via BTS configuration

– Maximum number PIC pools is 4 and cells in PIC pool is 6

– The PIC functionality will take a fixed number of CE per PIC pool, that is 72 CE ?? (one faraday device) (Basic PIC)

• The PIC-state of a cell in a PIC-Pool can be changed by WCEL parameter AdminPICState– “PIC-deactivated”, “PIC-activated”, “PIC-automatic”

– PIC state change of cells with “PIC-Automatic” is controlled by BTS Cells with highest traffic shall be selected for interference cancellation Cell are deselected for interference cancellation if traffic has decreased

HSUPA IC


Enabling the Feature (I)• Feature is activated by BTS license key

• The AdminPICState parameter must be set to ‘Activate’ or ‘Automatic’ for the cells where HSUPA IC is activated


AdminPICState

(WCEL)

0 (Activate),

1 (Deactivated),

2 (Automatic)

1 (Deactivated) With this parameter it is possible to change PIC state of a cell from deactivated to activate or automatic. There may be restriction in WBTS for changing the PICState. If the change is not possible, then the PICState remains. Parameter WCEL-PICState indicates the PICState of the cell.


PICState

(WCEL)

0 (Activate),

1 (Deactivated),

2 (Automatic)

Value set by system

Each cell in a PIC pool has one state. There are three different states: 'Deactivated', 'Activated'and 'Automatic'. The parameter indicates whether the cell supports HSUPA interference cancellation or not. The default value is 'Deactivated'.

HSUPA IC


Enabling the Feature (II)• The PICState, AdminPICState and MaxNumPICActCells parameters are used to

indicated PIC configuration in BTS


MaxNumPICActCells

(WCEL)

1..24, step 1 Value set by system

Maximum number of simultaneous PIC-activated cells in a pool. BTS informs the value of this parameter in PIC pool Mapping Information (in private NBAP message). RNC NBAP layer forwards this information to RNC O&M. RNC O&M shall set parameter MAXNumPICActCells to be equal with the value sent by BTS. RNC O&M shall check that number of simultaneously PIC-activated cells in a pool does not exceed the value of the parameter MAXNumPICActCells . RNC O&M shall allow PIC-activated state for a cell if and only if number of simultaneously PIC-activated cells in the pool is less than value of the parameter MAXNumPICActCells.


AssignedPICPool

(WCEL)

0 (off), 1 (PICpool1), 2 (PICpool2), 3 (PICpool3), 4 (PICpool4)

Value set by system

The parameter indicates which PIC pool the cell belongs to. The default value of the parameter is 'Off', and it indicates that the cell does not belong to any PIC pool i.e. HSUPA interference cancellation is not applied in the cell.

HSUPA IC


Other parameters

• The AdminPICState parameter must be set to ‘Activate’ or ‘Automatic’


PrxMaxOrigTargetBTS

(WCEL)

0..30 dB, step 0.1 dB

8 dB The parameter defines the maximum target wide band power for BTS on original signal together with parameter WCEL-PrxMaxTargetBTS, when HSUPA interference cancellation is applied. The value of the parameter is relative to the system noise. It gives an upper threshold for the noise rise (the ratio of total received uplink power to system noise).

HSUPA IC


10 15 20 25 30 35 40 45 500

200

400

600

800

1000

1200

1400

1600

no. of AM R UEs

Ce

ll T

hro

ug

pu

t in

kb

ps

EDCHEDCH w ith ICDCHDCH w ith ICDCH+EDCHDCH+EDCH w ith IC

Performance

• HSUPA IC gives capacity and coverage gain

• Below example of capacity gain os basic PIC in mixed traffic AMR+HSUPA case– Cell capacity gain highest with optimum share of UL capacity

Only interference from HSUPA to AMR is cancelled Also HSUPA gains from lower AMR interference power

HSUPA IC

1 0 2 0 3 0 4 0 5 01 0

2 0

3 0

4 0

5 0

6 0

7 0

n o . A M R U E s

Ce

ll T

hro

ug

pu

t G

ain

in

%

o v e r a ll T h r o u g h p u t g a inE - D C H t h r o u g h p u t g a in


Counters

• New counters for– WCEL

Residual stream fractional load in BTS UnHappy residual stream Fractional load Total Interference Reduction factor PICpool indication

– PICpool level Sum of different cancelled users Number of cancelled users Number of cancelled fingers

• Online monitoring– PrxTotal shows the received total transmission wide band power from BTS, raw value not averaged

by BRM – PrXLC is the power value used for uplink load control. When basicPIC or enhancedPIC is in use, the

value is PrxNonEDPCHST,orig. When basicPIC or enhanced PIC is not in use, it is PrxNonEDPCH.– PrxTotalRes is Prx_total,res,common when basicPIC or enhancedPIC is in use.

Prx_total,res,common is received power where a part of the interference (caused by IC users) is removed from the original signal power. In other cases the value shall be PrxTotal.

M1006C245 RB_CONFIG_MIMO_SUCCM1006C246 RB_CONFIG_MIMO_FAILM1006C247 RB_CONFIG_64QAM_SUCCM1006C248 RB_CONFIG_64QAM_FAIL

HSUPA IC


Content











– SRVCC from LTE*


Background

• Prior to RU30, only DCH and HSDPA compressed mode measurements were supported

• This feature provides support for inter-frequency compressed mode measurements while configured with HSUPA

• Avoids the requirement for HSUPA -> Uplink DCH channel type switching when an inter-frequency handover is triggered

• Allows faster inter-frequency handover and greater throughput during handover procedure

• Handovers can be:– HSPA -> HSPA

– HSPA -> DCH/HSDPA

– HSPA -> DCH/DCH

• Applicable to coverage, quality, HSPA capability and IMSI based inter-frequency handovers

• Not applicable to inter-system handover

HSUPA IFHO


Requirements

UE Requirements

• Release 6, or newer (support for HSUPA)





• HSDPA Inter-Frequency Handover

HSUPA IFHO



BTSSupportForHSPACM (WBTS)


0 (HSPA CM not supported),

1 (HSDPA CM supported),

2 (HSPA CM supported)

Default

• The feature is enabled using the BTSSupportForHSPACM parameter

• Existing parameter from RU20 but with its range extended to include HSPA

• Parameter can be modified online

This parameter defines whether the BTS supports HSDPA or HSPA compressed mode. If it is supported, the RNC can start the HSDPA or HSPA compressed mode in this BTS if it is needed. If HSPA CM not supported, the RNC can start the DCH compressed mode only. The HSDPA or HSPA compressed mode can be utilised only when the RNC configuration parameter CMmasterSwitch is enabled

0

• RAN1668 HSUPA Inter-Frequency Handover is an optional feature which requires an RNC licence

HSUPA IFHO


Admitting HSPA Compressed Mode

• The RNC admits HSPA compressed mode for inter frequency handover if:– RNC licence key 'HSPA inter frequency handover’ exists

– HSPA serving and non-serving E-DCH active set cells support HSPA compressed mode based upon the BTSSupportForHSPACM parameter

– compressed mode is enabled with RNC configuration parameter CMmasterSwitch

– HSDPA mobility is enabled with the HSDPAMobility parameter

• In case HSPA compressed mode activation is not possible then:– HSDPA compressed mode is attempted

– otherwise DCH compressed mode is attempted

• HSUPA IFHO can be intra or inter BTS

• HSUPA IFHO can be intra or inter RNC

HSUPA IFHO


Compressed Mode Parameters - Revision

• Transmission Gap Pattern defines the position and duration of each compressed mode transmission gap

Transmission Gap Pattern

Transmission Gap Pattern Length

Transmission Gap Length

Transmission Gap Start Number

HSUPA IFHO


Maximum Number of UE in Compressed Mode

• The maximum number of HSPA UE in a cell with compressed mode is limited by the parameters:– MaxNumberUEHSPACmHO – applicable to critical handovers

– MaxNumberUEHSPACmNCHO – applicable to non-critical handovers

• Critical handover mechanisms can steal capacity from non-critical handover mechanisms if necessary

• If the threshold is reached UE are not reconfigured from HSPA or HSDPA to DCH and compressed mode is not started

• Note that HSDPA and HSPA compressed mode is counted using the same variable

• The maximum number of HSPA UE in compressed mode is temporarily allowed to exceed the limit when a new soft handover branch is added for a UE which is already in HSPA compressed mode

HSUPA IFHO


Triggering HSUPA IFHO

• The triggers for IFHO with HSUPA are based upon those for IFHO without HSUPA:

• Coverage and Quality– CPICH RSCP or Ec/Io

– UE Transmit Power

• HSPA Triggers– HSPA Capability based Handover

– Multi-band Load Balancing due to Inactivity

– Multi-band Load Balancing due to Mobility

• IMSI Triggers

• IMSI based IFHO

• The HSDPA specific measurement control parameter sets are used for HSPA IFHO, e.g. identified by HSDPAFmciIdentifier

HSUPA IFHO


Signalling

RRC: Measurement Report

UE RNCServing Node B Non-Serving Node B

CM Admission

NBAP: Radio Link Reconfigure Prepare

NBAP: Radio Link Reconfiguration Ready

NBAP: Radio Link Reconfigure Prepare

NBAP: Radio Link Reconfiguration Ready

NBAP: Radio Link Reconfiguration Commit

NBAP: Radio Link Reconfiguration Commit

RRC: Physical Channel Reconfiguration

RRC: Physical Channel Reconfiguration Complete

RRC: Measurement Control

RRC: Measurement Report

HO Decision

IFHO Procedure

HSUPA IFHO


UE Not Supporting HSUPA Compressed Mode

• Compressed mode for HSUPA is mandatory for all 3GPP release 6 UE that support HSUPA

• However, some early release 6 HSUPA UE based upon Qualcomm chipsets do not support HSUPA compressed mode

• Qualcomm have implemented an indication for early release 6 UE which do not support HSUPA compressed mode– indication is not explicitly specified by 3GPP but is allowed

• The release 5 information element ‘supportOfDedicatedPilotsForChannelEstimationOfHSDSCH’ is used to identify release 6 HSUPA UE which do not support HSUPA compressed mode

• This IE is not used for any other purpose and can be included within the RRC Connection Setup Complete message

• If this ‘dummy’ bit is set to true then the RNC assumes that the UE does not support compressed mode for HSUPA

HSUPA IFHO


Counters

• RU30 introduces the counters shown below within the M1002 Traffic table

M1002C676 ALLO_CM_HSUPA_IFHOM1002C677 ALLO_DURA_CM_HSUPA_IFHOM1008C678 REJ_CM_HSUPA_IFHO

• RU30 introduces the counters shown below within the M1008 Intra-System Hard Handover table

M1008C294 ATT_HSUPA_IFHOM1008C295 SUCC_HSUPA_IFHO

• The existing HSDPA IFHO counters within the M1002 and M1008 counter tables are incremented along with the new HSUPA IFHO counters

• The HSDPA IFHO M1008 counters are M1008C247-M1008C261

• The HSDPA IFHO M1002 counters are M1002C623-M1002C625

HSUPA IFHO


Content











– SRVCC from LTE*


Material

Please see a separate slide set in (open links):

Multilayer Related Material in IMS

Community Official Guidelines

Dimensioning and Planning

Mobility Planning & Optimisation


Content











– SRVCC from LTE*


Background

• RU10 provides support for:– 64 HSDPA users per cell– 20 HSUPA users per cell

• RU20 provides support for:– 72 HSDPA users per cell– 72 HSUPA users per cell

• RU30 provides support for:– 128 HSDPA users in CELL_DCH per cell– 128 HSUPA users in CELL_DCH per cell

• In RU30, HSUPA connections are only counted by the serving cell (prior to RU30 they are counted in both the serving and non-serving cells)

• The maximum number of HS-DSCH MAC-d flows per cell is 1024

128 HSPA Users

Becomes relevant in RU30 after HS-FACH is supported


Requirements

UE Requirements

• None





• HSDPA, HSUPA, HSPA 72 Users per Cell

• To help reduce air-interface load, it is also recommended to use

• Continuous Packet Connectivity (CPC)

• F-DPCH

• HSUPA Downlink Physical Channel Power Control

128 HSPA Users



HSPA128UsersPerCell

(WCEL)


Not Enabled (0),

Enabled (1)

Default

• The HSPA128UsersPerCell parameter must be set to ‘Enabled’

• This parameter requires object locking for modification

This parameter determines whether the “HSPA 128 users per cell“ feature is enabled in the cell or not. If this feature is enabled, maximum 128 HSDPA and 128 serving HSUPA users can be admitted per cell, if BTS also supports 128 HSPA users per cell (Rel2 baseband HW).

It is recommended to have features Continuous Packet Connectivity (CPCEnabled) and Fractional DPCH (FDPCHEnabled) enabled in the cell so that high amount of HSPA users is possible. Also feature HSUPA Downlink Physical Channel Power Control should be in use in BTS so that DL control channel power consumption is in lower level so that more resources is left for user data (more RT users an more user data).

Not Enabled (0)

• RAN2124 HSPA 128 Users per Cell is an optional feature which requires an RNC licence

128 HSPA Users


E-HICH/E-RGCH Signatures 128 HSPA Users

• A single E-RGCH/E-HICH code has 40 signatures

• Each UE requires either 1 or 2 dedicated signatures and all signatures for a single UE must be allocated from the same E-RGCH/E-HICH code

The signature requirements per UE are:

• Serving E-DCH cell with 10 ms TTI– Scheduled Transmission: 2 signatures per UE (E-HICH + E-RGCH)– Non-Scheduled Transmission: 1 signature per UE (E-HICH)

• Serving E-DCH RLS with 2 ms TTI– Both Scheduled Transmission or Non-Scheduled Transmission: 1 signature per

UE (E-HICH)

• Non-Serving E-DCH cell with 10 ms or 2 ms TTI– 1 signature is allocated for a common non-serving E-RGCH– 1 signature per UE for E-HICH


Maximum Number of E-RGCH/E-HICH

• If the HSPA128UsersPerCell parameter is set to 'enabled', then the quantity of allocated E-RGCH/E-HICH codes is not limited

• If the HSPA128UsersPerCell parameter is set 'disabled' and the HSPA72UsersPerCell parameter is set to 'enabled', then the quantity of E-RGCH/E-HICH codes is limited to 4

• If both the HSPA128UsersPerCell and HSPA72UsersPerCell parameters are set to 'disabled' and HS CELL_FACH feature is not in use, then the quantity of E-RGCH/E-HICH codes is limited to 1

• The HSUPACtrlChanAdjPeriod parameter is deleted in RU30. This timer previously triggered checks for E-RGCH/E-HICH code upgrades/downgrades

128 HSPA Users


E-HICH/E-RGCH Code Allocations

• A single E-RGCH/E-HICH code is allocated during cell start-up

• Further E-RGCH/E-HICH codes are allocated/released dynamically

SF16,0 SF16,1

CP

ICH

P-C

CP

CH

AIC

H

PIC

H

S-C

CP

CH

HS

-SC

CH

1

E-R

GC

H/

E-H

ICH

1

HS

-SC

CH

2

HS

-SC

CH

3

HS

-SC

CH

4

E-A

GC

H 1

0 m

s

E-A

GC

H 2

ms

128 HSPA Users


• The RNC checks the requirement for a new E-RGCH/E-HICH code every time an HSUPA connection is allocated

• The condition used to allocate an additional code is:

Number of free signatures <= RsrvdSignaturesOffset

128 HSPA Users

Allocating Additional E-HICH/E-RGCH Codes

RsrvdSignaturesOffset

(WCEL)


5 to 11, step 1

Default

10 This parameter indicates the number of free E-RGCH and E-HICH signatures which have to be reserved in the cell to avoid too much increase/decrease of E-RGCH and E-HICH codes and unavailability of signatures during dynamic allocation/de-allocation of E-RGCH/ E-HICH codes. That is, this parameter acts as an offset.

When the available free E-RGCH/E-HICH signatures per cell is equal to less than the value of this parameter, additional E-RGCH/E-HICH channel has to be allocated. Similarly this parameter is used in case of releasing existing E-RGCH/E-HICH codes also.


• The RNC checks the requirement for releasing an existing E-RGCH/E-HICH code every time an HSUPA connection is released

• The condition used to release an existing code is:

Number of free signatures > 39 + 2 RsrvdSignaturesOffset

128 HSPA UsersReleasing E-HICH/E-RGCH Codes

• The order of releasing E-RGCH/E-HICH codes is from the right to the left of the code tree

• Releasing E-RGCH/E-HICH codes may involve re-allocation of signatures from one code to another


Admission Control

• The limit of 128 defined by the feature includes only serving connections– The feature does not limit the number of non-serving HSUPA connections

• The quantity of HSDPA connections can be limited using existing parameters:– WCEL - MaxNumberHSDPAUsers– WCEL - MaxNumberHSDSCHMACdFlows– WCEL - MaxNumbHSDPAUsersS– WCEL - MaxNumbHSDSCHMACdFS– Default of all 0 (Not Limited)

• The quantity of HSUPA connections can be limited using existing parameters:– WCEL - MaxNumberEDCHCell– WCEL - MaxNumberEDCHLCG– Default of all 0 (Not Limited)

• The limits defined by the HSUPA parameters above include both serving and non-serving connections

• If HSPA 128 Users Per Cell feature is enabled, the NumberEDCHReservedSHOBranchAdditions parameter is ignored (handled as though a value of 0 is configured)

128 HSPA Users


Preventative Overload Control - HSUPA

• Similar to RU20, Preventive Overload is triggered to help ensure that the maximum number of connections is not reached while there are inactive users

• ‘HSPA 128 users’ and ‘HSPA 72 users’ disabled:

#all_HSUPA_users_in_cell >= InacUsersOverloadFact * MaxNumberEDCHCell

#all_HSUPA_users_in_LCG >= InacUsersOverloadFact * MaxNumberEDCHLCG

• ‘HSPA 128 users’ disabled and ‘HSPA 72 users’ enabled:

#all_HSUPA_users_in_cell >= InacUsersOverloadFact * 20 #all_HSUPA_users_in_LCG >= InacUsersOverloadFact * 24

#serving_HSUPA_users_in_cell >= InacUsersOverloadFact * 128 #serving_HSUPA_users_in_LCG >= InacUsersOverloadFact * 1024

#all_HSUPA_users_in_cell >= InacUsersOverloadFact * 72 #all_HSUPA_users_in_LCG >= InacUsersOverloadFact * 160

128 HSPA Users

• ‘HSPA 128 users’ enabled:

• All cases:


Preventative Overload Control - HSDPA

• Preventive overload actions can be triggered by the parameters which limit the maximum number of connections (Default of all 0 = Not Limited):

#HSDPA_users_in_cell >= InacUsersOverloadFact * 128

#all_HSDPA_usrs_cell >= InacUsersOverloadFact * MaxNumberHSDPAUsers

#all_HSDPA_usrs_scheduler >= InacUsersOverloadFact * MaxNumbHSDPAUsersS

#all_MACds_in_cell >= InacUsersOverloadFact * MaxNumberHSDSCHMACdFlows

#all_MACds_in_scheduler >= InacUsersOverloadFact * MaxNumbHSDSCHMACdFS

• It can also be triggered by the maximum number of connections defined by the feature itself:

128 HSPA Users


InacUsersOverloadFact

(RNC)


0 to 1,

step 0.01

Default

0.9 The parameter defines the factor for maximum number of HSPA users when preventive overload control is started by releasing inactive users MAC-d flows and moving them from Cell_DCH.

The parameter is applied for following HSPA user amount related maximum values:

- MaxNumberHSDSCHMACdFlows

- MaxNumberHSDPAUsers

- MaxNumberEDCHCell

- MaxNumberEDCHLCG

- HSUPAXUsersEnabled

Preventative Overload Control Parameter

128 HSPA Users


Performance

• UL capacity will be limited due to high L1 overhead caused by large number of users in CELL_DCH– All features required to increase UL capacity: CPC, FDE, HSUPA IC

– UL parameter optimisation required (see TN159)

– Dynamic HSUPA power offset (CR419, RU20 MP3) Enable usage of high symbol rates

• L1 control channels– DPCCH

– HS-DPCCH

– E-DPCCH


Counters

• RU30 introduces the counters shown below within the M1000 Cell Resource table

M1000C384 DURA_HSUPA_USERS_73_TO_80M1000C385 DURA_HSUPA_USERS_81_TO_96M1000C386 DURA_HSUPA_USERS_97_TO_112M1000C387 DURA_HSUPA_USERS_113_OR_MORE

M1000C388 MAX_HSUPA_USERS_IN_SERV_CELL

M1000C389 SUM_HSUPA_USERS_IN_SERV_CELL

M1000C390 DURA_HSDPA_USERS_73_TO_80M1000C391 DURA_HSDPA_USERS_81_TO_96M1000C392 DURA_HSDPA_USERS_97_TO_112M1000C393 DURA_HSDPA_USERS_113_OR_MORE

128 HSPA Users


Content











– SRVCC from LTE*


Background (I) HSPA DL PC

• When power control is not used, a relatively high fixed transmit power must be used to ensure that UE towards cell edge are able to receive successfully

• This results in excessive transmit power used for UE which are in good coverage– wastes downlink transmit power (downlink capacity)– increases downlink interference levels (downlink coverage)

• This feature introduces power control for the following physical channels:– E-AGCHE-DCH Absolute Grant Channel– E-HICH E-DCH HARQ Acknowledgement Indicator Channel– E-RGCHE-DCH Relative Grant Channel– F-DPCH Fractional Dedicated Physical Channel

• Controlling the downlink transmit power of these channels helps to reduce both downlink power consumption and downlink interference levels

• Reducing downlink interference levels can increase the coverage of HSUPA 2ms TTI, reducing the number of reconfigurations and increasing throughput.


Background (II)

• The BTS adjusts the downlink physical channel transmit power using both inner loop and outer loop algorithms– inner loop based upon CQI reports and TPC commands

– outer loop based upon HARQ acknowledgements

HSPA DL PC

Tx Power F-DPCH

Tx Power E-HICH

Tx Power E-RGCH

Tx Power E-AGCH

CQI

DL TPC

L1 HSPA ACK & NACK

Power offsets from RNC databuild

DL Power Control

Inner Loop & Outer Loop


Requirements

UE Requirements

• None




• HSDPA, HSUPA

• It is not mandatory to have F-DPCH enabled for this feature

• if disabled, the F-DPCH component of this feature is not applied

HSPA DL PC



• This feature is always enabled when using RU30

• There is not a parameter enable/disable this feature

• The feature is included as part of the basic software and does not require a license

HSPA DL PC


E-HICH, E-RGCH, E-AGCH Transmit Powers

• Transmit powers are defined using the equations shown to the right

• Transmit powers are fixed by the RNC databuild

PE-AGCH = PCPICH + PtxOffsetEAGCH

PE-RGCH = PCPICH + PtxOffsetERGCH

PE-HICH = PCPICH + PtxMaxEHICH

RAS06 and RU10

PtxOffsetEAGCH

(WCEL)


-32 to 31.75, step 0.25 dB

Default

This parameter defines the transmission power of the E-DCH Absolute Grant Channel. E-AGCH power is related to the transmission power of the primary CPICH.

- 5 dB

PtxOffsetERGCH

(WCEL)


-32 to 31.75, step 0.25 dB

Default

This parameter defines the transmission power of the E-DCH Relative Grant Channel. E-RGCH power is related to the transmission power of the primary CPICH.

- 11 dB

PtxMaxEHICH

(WCEL)


-32 to 31.75, step 0.25 dB

Default

This parameter defines the transmission power of the E-DCH HARQ Ack Indicator Channel. E-HICH power is related to the transmission power of the primary CPICH.

- 11 dB



• BTS which do not support the 2 ms TTI for HSUPA e.g. Flexi with FSMB, calculate the transmit powers in the same way as in RU10

RU20

E-AGCH Power Offset =

-8 dB + PtxOffsetEAGCHDPCCH + PtxOffsetExxCH2ms + PtxOffsetExxCHSHO

E-RGCH Power Offset =

-14 dB + PtxOffsetERGCHDPCCH + PtxOffsetExxCH2ms + PtxOffsetExxCHSHO

E-HICH Power Offset =

-14 dB + PtxOffsetEHICHDPCCH + PtxOffsetExxCH2ms + PtxOffsetExxCHSHO

• BTS which support the 2 ms TTI for HSUPA e.g. Flexi with FSME, calculate the transmit powers using the equations below

PE-AGCH = PCPICH + E-AGCH Power Offset

PE-RGCH = PCPICH + E-RGCH Power Offset

PE-HICH = PCPICH + E-HICH Power Offset

• Default parameter values lead to same results as RU10 when UE is in soft handover and 10 ms TTI is used

• Transmit powers are reconfigured as UE move in and out of soft handover


E-HICH, E-RGCH, E-AGCH Parameters (I)

PtxOffsetEAGCHDPCCH (WCEL)


-32 to 31.75, step 0.25 dB

Default

This parameter defines the tx power of the E-AGCH. E-AGCH power is defined in relation to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the E-AGCH power is defined in relation to the power of transmitted TPC bits on the F-DPCH.

0 dB

PtxOffsetERGCHDPCCH (WCEL)


-32 to 31.75, step 0.25 dB

Default

This parameter defines the tx power of the E-RGCH. E-RGCH power is defined in relation to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the E-RGCH power is defined in relation to the power of transmitted TPC bits on the F-DPCH.

0 dB

PtxOffsetERGCHDPCCH (WCEL)


-32 to 31.75, step 0.25 dB

Default

This parameter defines the tx power of the E-RGCH. E-RGCH power is defined in relation to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the E-RGCH power is defined in relation to the power of transmitted TPC bits on the F-DPCH.

0 dB

HSPA DL PC


E-HICH, E-RGCH, E-AGCH Parameters (II)

PtxOffsetExxCH2ms (WCEL)


-5 to 15, step 0.25 dB

Default

This parameter defines power offset to E-xxCH power offsets for E-DCH TTI 2 ms case. If E-DCH TTI is 2 ms, the value of this parameter is added to the signaled value of E-AGCH power offset, ERGCH power offset and E-HICH power offset.

5 dB

PtxOffsetExxCHSHO

(WCEL)


-5 to 10, step 0.25 dB

Default

This parameter defines power offset to E-xxCH power offsets for E-DCH soft handover case. If UE is in E-DCH soft handover (that is non-serving EDCH RLS exists) and F-DPCH does not exist in the connection, the value of this parameter is added to the signaled value of E-AGCH power offset, ERGCH power offset and E-HICH power offset.

3 dB

HSPA DL PC



PE-AGCH = Pref + E-AGCH Power Offset

PE-RGCH = Pref + E-RGCH Power Offset

PE-HICH = Pref + E-HICH Power Offset

RU30

E-AGCH Power Offset =

-8 dB - Ptx,max_CPICH + PtxOffsetEAGCHDPCCH + PtxOffsetExxCH2ms + PtxOffsetExxCHSHO

E-RGCH Power Offset =

-14 dB - Ptx,max_CPICH + PtxOffsetERGCHDPCCH + PtxOffsetExxCH2ms + PtxOffsetExxCHSHO

E-HICH Power Offset =

-14 dB - Ptx,max_CPICH + PtxOffsetEHICHDPCCH + PtxOffsetExxCH2ms + PtxOffsetExxCHSHO

• The equations below are similar to those used for RU20 but include Ptx,max_CPICH

• Ptx,max_CPICH is the maximum downlink transmit power of the dedicated radio link relative to the CPICH (could be a standalone SRB, SRB + AMR or F-DPCH)

• BTS which support the 2 ms TTI for HSUPA e.g. Flexi with FSME, calculate the transmit powers using the equations below

• Pref is calculated dynamically by the BTS

• Power offsets are calculated using the equations below


Reference Power Calculation (I)

• Within the serving cell, the Reference Power is calculated as:

Pref = PCPICH + + ACQI + ATPC + Asignaling_error + ADTX

HSPA DL PC

• PCPICH is the CPICH transmit power

is the HSDPA Measurement Power Offset (MPO) signalled to the UE

• ACQI is a obtained from a BTS internal look-up table indexed by reported CQI

• high CQI values are associated with large negative power offsets

• low CQI values are associated with small negative power offsets

• ATPC is adjusted according to Transmit Power Control (TPC) commands received from the UE (driven by SIR measurements from the DPCCH/F-DPCH)

• Asignalling_error is adjusted according to whether or not an E-HICH signalling error is detected (re-transmission is received after sending a +ve acknowledgment)

• ADTX is increased during periods of uplink DPCCH DTX, i.e. uplink gating component of Continuous Packet Connectivity (CPC)

• ATPC and ADTX are reset to 0 each time a CQI report is received

Outer Loop


Reference Power Calculation (II)

• Within non-serving cells, the Reference Power is calculated as:

HSPA DL PC

Pref = Maximum Downlink Transmit Power

Common E-RGCH Transmit Power

• A common E-RGCH is used to limit HSUPA resource allocations in non-serving cells

PE-RGCH = Pref + E-RGCH Power Offset

• where Pref is the highest Maximum Downlink Transmit Power from all the non-serving UE in the cell

• E-RGCH Power Offset is then taken from the same UE as the Maximum Downlink Transmit Power


F-DPCH Transmit Power

RU20

HSPA DL PC

• The F-DPCH transmit power is set equal to the maximum transmit power

• The maximum transmit power is calculated as:

Max. Tx Power = PtxPrimaryCPICH - PtxFDPCHMax + PtxOffsetFDPCHSHO

e.g. = 33 – 9 + 1 = 25 dBm

• The PtxOffsetFDPCHSHO parameter is applied when UE are in E-DCH SHO

• The transmit power is adjusted when the UE enters and leaves soft handover

PtxFDPCHMax

(WCEL)


-5 to 30 dB, step 0.1 dB

Default

9 dB This parameter defines maximum power for TPC bits of Fractional DPCH (F-DPCH). Value of the parameter is subtracted from RNP parameter PtxPriCPICH. If value of the parameter is equal to value of the parameter PtxFDPCHMin, BTS deactivates power control of HSPA DL control channels.

PtxOffsetFDPCHSHO

(WCEL)


0 to 10 dB, step 0.5 dB

Default

1 dB The power offset to Fractional DPCH (F-DPCH) power for E-DCH soft handover case. If UE is in E-DCH soft handover (that is non-serving E-DCH RLS exists), the value of this parameter is added to the signaled NBAP value of Initial DL Transmission Power, Maximum DL Power and Minimum DL Power.


F-DPCH Transmit Power

RU30• The F-DPCH transmit power is defined as:

PF-DPCH = Pref

HSPA DL PC

• The maximum transmit power is calculated as:

Max. Tx Power = PtxPrimaryCPICH - PtxFDPCHMax + PtxOffsetFDPCHSHO

e.g. = 33 – 9 + 1 = 25 dBm

• The minimum transmit power is calculated as:

Min. Tx Power = PtxPrimaryCPICH - PtxFDPCHMin + PtxOffsetFDPCHSHO

e.g. = 33 – 20 +1 = 14 dBm

PtxFDPCHMin

(WCEL)


-5 to 30 dB, step 0.1 dB

Default

20 dB This parameter defines minimum power for TPC bits of Fractional DPCH (F-DPCH). Value of the parameter is subtracted from RNP parameter PtxPriCPICH. If value of the parameter is equal to value of the parameter PtxFDPCHMax, BTS deactivates power control of HSPA DL control channels.


RNC Counters

• The counters shown below are added to the HSPA counter table within the Node B

M5000C293 HSUPA_PWR_RATIO_DISTR_CLASS_01 M5000C294 HSUPA_PWR_RATIO_DISTR_CLASS_02M5000C295 HSUPA_PWR_RATIO_DISTR_CLASS_03M5000C296 HSUPA_PWR_RATIO_DISTR_CLASS_04M5000C297 HSUPA_PWR_RATIO_DISTR_CLASS_05M5000C298 AVG_HSUPA_DL_PWR_CONTR_CHN

HSPA DL PC


Content








– Dynamic HSDPA BLER

– Dynamic HSUPA BLER

– High Speed Cell_FACH

– SRVCC from LTE


Background

• RU20 uses HSDPA BLER Targets of 10 % and 25 %– 10 % is applied in static channel conditions– 25 % is applied in fading channel conditions

• In RU20, these BLER targets are not configurable and are independent of whether high or low CQI values are reported

• RU30 allows the use of HSDPA BLER Targets of 2 %, 6 %, 10 % and 25 %

• In RU30, the BLER Target is a function of the– the channel conditions (static vs fading)– the CQI

• Thresholds defining high, medium and low CQI ranges are configurable• Upper and lower BLER target limits for each CQI range are configurable

• Expected benefits: cell and end-user HSDPA throughputs improved by up to 8 %

DYN HSDPA BLER


Requirements

UE Requirements

• HSDPA capable UE





• HSDPA

DYN HSDPA BLER


Enabling the Feature DYN HSDPA BLER

• RAN2171 Dynamic HSDPA BLER is a basic software feature which does not require a licence

• The feature is installed as part of the BTS software and is always enabled

• Fallback to RU20 behaviour can be achieved by configuring the BLER Target parameter set appropriately

• The parameters associated with this feature are Node B commissioning parameters rather than RNC databuild parameters


BLER Target – Starting Point

• The BLER Target is a function of the variance of the reported CQI

• A low variance indicates that the UE is experiencing static channel conditions– Low BLER target is appropriate

• A high variance indicates that the UE is experiencing fading channel conditions– High BLER target is appropriate

• The look-up table below is defined within the Node B

• Values within this table can be overwriten by defining upper and lower BLER target limits within the RNC databuild

DYN HSDPA BLER

Variance of Reported CQI

BLER Target

Channel Type

0 to 1 2 % Static

1 to 1.5 6 % Fading

1.5 to 2.5 10 %

>2.5 25 %


BLER Target – Look-Up Table DYN HSDPA BLER

• For example, if the lower limit is defined as 6% and the upper limit is defined as 10% then the look-up table becomes:

• The RNC databuild also allows the BLER Target to be defined as a function of the CQI, e.g. smaller BLER Targets can be defined for higher CQI values


BLER Target

Channel Type

0 to 1 6 % Static

1 to 1.5 6 % Fading

1.5 to 2.5 10 %

>2.5 10 %


Low CQI Range

Medium CQI Range

High CQI Range

0 to 1 BLERLOW,1 BLERMED,1 BLERHIGH,1

1 to 1.5 BLERLOW,2 BLERMED,2 BLERHIGH,2

1.5 to 2.5 BLERLOW,3 BLERMED,3 BLERHIGH,3

>2.5 BLERLOW,4 BLERMED,4 BLERHIGH,4


BLER Target – Parameter Set DYN HSDPA BLER

• The table below presents the RNC databuild parameters used to define:

– the set of 3 CQI ranges

– the upper and lower BLER Target limits for each CQI range

Condition for each CQI range Upper and Lower BLER Target Limits

Low CQI Range Reported CQI < medCQIRangeStart targetBLERLowCQIStaCh

targetBLERLowCQIFadCh

Medium CQI Range

medCQIRangeStart ≤ Reported CQI < highCQIRangeStart targetBLERMedCQIStaCh

targetBLERMedCQIFadCh

High CQI Range highCQIRangeStart ≤ Reported CQI targetBLERHighCQIStaCh

targetBLERHighCQIFadCh

• For example,

– targetBLERLowCQIStaCh defines the lower BLER Target limit for the low CQI range

– targetBLERLowCQIFadCh defines the upper BLER Target limit for the low CQI range


BLER Targets – Default Values DYN HSDPA BLER

• The default parameter set generates the look-up table shown below


Low CQI Range

Medium CQI Range

High CQI Range

0 to 1 6 % 2 % 2 %

1 to 1.5 6 % 6 % 6 %

1.5 to 2.5 10 % 10 % 10 %

>2.5 25 % 25 % 25 %

• Configuration for fallback to RU20 behaviour is shown below


Low CQI Range

Medium CQI Range

High CQI Range

0 to 1 10 % 10 % 10 %

1 to 1.5 10 % 10 % 10 %

1.5 to 2.5 10 % 10 % 10 %

>2.5 25 % 25 % 25 %


Counters

• There are no counters specifically associated with this feature

• Existing HSDPA throughput counters can be used to help quantify the gains

DYN HSDPA BLER


Content











– SRVCC from LTE


Background

• RU20– uses an HSUPA Layer 1 BLER Target of 10%

• RU30– dynamically selects the HSUPA Layer 1 BLER Target

– selects the BLER target to suite the individual connection

DYN HSUPA BLER

Connections with high throughput

Connections with bursty activity

Other connections

Apply Low BLER Target to allow a further increase in throughput

Apply Moderate BLER Target to help improve latency, i.e. reduced requirement for re-transmissions

Apply Higher BLER Target to optimise cell capacity and coverage


Requirements

UE Requirements

• HSUPA capable UE


• None


• HSUPA

DYN HSUPA BLER


Enabling the Feature DYN HSUPA BLER

HSUPADynBLEREnabled

(RNC)


0 (disabled), 1 (enabled)

Default

This parameter Enables/Disables the Dynamic adjustment of HSUPA BLER.

0

• The HSUPADynBLEREnabled parameter must be set to ‘Enabled’


• RAN2302 Dynamic HSUPA BLER is a basic software feature which does not require a licence

Parameters for this feature do not yet appear in PDDB


Selection of HSUPA BLER Target DYN HSUPA BLER

• New state machine in OLPC module shall be implemented, so that OLPC can choose if (UE PDUs in FP frame > 90% of UE max data-rate) /* to get the peak data-rates */

Connection Throughput > 90% of maximum

1% BLER Target after 0 re-transmissions

FP frames per second

< 10 (10 ms TTI)

< 50 (2 ms TTI)

10% BLER Target after 0 re-transmissions

10% BLER Target after 1 re-transmission

Start

Allows peak connection throughput to be achieved

Data is bursty so optimise latency

Optimise throughput and coverage

Yes

Yes

No

No


Adjusting BLER Target• RNC Outer Loop Power Control adjusts the previously defined

BLER targets when a UE has a combination of E-DCH and DCH transport channels– If DCH is not achieving its BLER target then E-DCH BLER target is

reduced– If E-DCH is not achieving its BLER target then DCH BLER target is

reduced

• Additional parameters define the maximum BLER targets for the E-DCH

• Existing MaxBLERTargetDCH parameter defines the maximum BLER target for the DCH

DYN HSUPA BLER

BLER_Target_EDCH = Ideal_BLER_Target_EDCH +EDCHSlopeOfTheCurve (Ideal_BLER_target_DCH – BLER_DCH)

BLER_Target_DCH = Ideal_BLER_Target_DCH +DCHSlopeOfTheCurve (Ideal_BLER_target_EDCH – BLER_EDCH)


MaxL1PeakDataRateBLERTrgtEDCH

(RNC)


-4 to -0.3, step 0.1

Default

This parameter defines maximum L1 BLER target for E-DCH. It is used by the outer loop power control of the RNC for peak data rate. Value of the parameter equals to the log10 of the BLER value

-2 (1%

BLER)

Non-Configurable

MaxL1BurstyDataBLERTrgtEDCH

(RNC)


-4 to -0.3, step 0.1

Default

This parameter defines maximum L1 BLER target for E-DCH. It is used by the outer loop power control of the RNC for bursty data. Value of the parameter equals to the log10 of the BLER value.

-1 (10%

BLER)

Non-Configurable

MaxL1ContBLERTrgtEDCH

(RNC)


-4 to -0.3, step 0.1

Default

This parameter defines maximum L1 BLER target for E-DCH. It is used by the outer loop power control of the RNC for peak data rate. Value of the parameter equals to the log10 of the BLER value.

-1 (10%

BLER)

Non-Configurable

Maximum BLER Targets

DYN HSUPA BLER


MaxL1PeakDataRateBLERTarEDCHSRB2MS

(RNC)


-4 to -0.3, step 0.1

Default

This parameter defines the maximum L1 BLER target for SRBs on E-DCH TTI 2ms. It is used by the outer loop power control of the RNC for peak data rate. A value of the parameter equals to the log10 of the BLER value.

-2 (1%

BLER)

DYN HSUPA BLER

Non-Configurable

MaxL1BurstyDataBLERTarEDCHSRB2MS

(RNC)


-4 to -0.3, step 0.1

Default

This parameter defines the maximum L1 BLER target for SRBs on E-DCH TTI 2ms. It is used by the outer loop power control of the RNC for bursty data. A value of the parameter equals to the log10 of the BLER value.

-1 (10%

BLER)

Non-Configurable

MaxL1ContBLERTarEDCHSRB2MS

(RNC)


-4 to -0.3, step 0.1

Default

This parameter defines the maximum L1 BLER target for SRBs on E-DCH TTI 2ms. It is used by the outer loop power control of the RNC for continuous data. A value of the parameter equals to the log10 of the BLER value.

-1 (10%

BLER)

Non-Configurable

Maximum BLER Targets for 2ms TTI SRB


Counters

• There are no counters specifically associated with this feature

• Existing HSUPA throughput counters can be used to help quantify the gains

DYN HSUPA BLER


Content











– SRVCC from LTE


Separate slide set in material folder


Content











– SRVCC from LTE*


End of Module 1

ru30 radio features

Documents