Vous êtes sur la page 1sur 64

1/2

Document Type
Author
Unit/Dept.

Document Title
Date, Version
For internal use only

Nokia Siemens Networks

3G Radio Network Planning Guideline


Delta for RU20

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

REVISION HISTORY
Date

7.12.2009
30.07.2010

Rev.

v.1.0
v.1.1

Editors:
Date:
Version:

Summary of Change

Document created
Fast Dormancy and Direct Resource
Allocation featured added. F-DPCH
dependency for DC-HSDPA removed

Jarkko Itkonen, Chris Johnson,


Dalius Kaskelevicius
7.12.2009
v.1.1

Copyright Nokia Siemens Networks. This material, including documentation and any related
computer programs, is protected by copyright controlled by Nokia Siemens Networks. All rights are
reserved. Copying, including reproducing, storing, adapting or translating, any or all of this material
requires the prior written consent of Nokia Siemens Networks. This material also contains confidential
information which may not be disclosed to others without the prior written consent of Nokia Siemens
Networks.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 2 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Table of contents

1 Introduction ................................................................................................ 7
1.1

Summary of RU20 Features .................................................................................................... 7

2 General RRM and DCH features ............................................................... 9


2.1 24kbps Paging Channel...........................................................................................................9
2.1.1 24 kbps Paging Channel Parameters ................................................................................... 9
2.2 LTE Interworking .....................................................................................................................9
2.2.1 LTE Inter-working Parameters .............................................................................................. 9
2.3 Fast L1 synchronisation ......................................................................................................... 11
2.3.1 Fast Layer 1 Synchronisation Parameters .......................................................................... 12
2.4 Power Saving Mode for BTS ................................................................................................. 13
2.4.1 Power Saving Mode for BTS Parameters ........................................................................... 13
2.5 Common Channel Setup ....................................................................................................... 16
2.5.1 Common Channel Setup Parameters ................................................................................. 16
2.6 Fast Dormancy ...................................................................................................................... 18
2.6.1 Fast Dormancy Parameters ................................................................................................ 19
2.7 Changes to other features ..................................................................................................... 20

3 HSDPA features ...................................................................................... 22


3.1 HSDPA bit rates .................................................................................................................... 22
3.2 CS Voice over HSPA ............................................................................................................. 22
3.2.1 CS Voice over HSPA Parameters ....................................................................................... 23
3.3 MIMO .................................................................................................................................... 27
3.3.1 MIMO Parameters .............................................................................................................. 28
3.4 HSDPA 64 QAM .................................................................................................................... 29
3.4.1 HSDPA 64QAM Parameters ............................................................................................... 30
3.5 DC-HSDPA 42Mbps .............................................................................................................. 31
3.5.1 DC-HSPA Parameters ........................................................................................................ 32
3.6 Flexible RLC (DL) .................................................................................................................. 33
3.6.1 Downlink Flexible RLC Parameters .................................................................................... 34

4 HSUPA features ...................................................................................... 36


4.1 HSUPA bit rates .................................................................................................................... 36
4.2 HSUPA 5.8 Mbps .................................................................................................................. 36
4.2.1 HSUPA 5.8 Mbps Parameters ............................................................................................ 37
4.3 HSUPA 2ms TTI .................................................................................................................... 38
4.3.1 HSUPA 2 ms TTI Parameters ............................................................................................. 38

5 HSPA features ......................................................................................... 40


5.1 Fractional DPCH ................................................................................................................... 40
5.1.1 Fractional DPCH Parameters ............................................................................................. 40
5.2 Continuous Packet Connectivity ............................................................................................ 43
5.3 Continuous Packet Connectivity Parameters ......................................................................... 44
5.4 HSPA 72 Users per Cell ........................................................................................................ 48
5.4.1 HSPA 72 Users Per Cell Parameters.................................................................................. 48
5.5 Direct Resource Allocation for HSPA ..................................................................................... 49
5.5.1 Direct Resource Allocation for HSPA Parameters............................................................... 50

Copyright Nokia Siemens Networks 2008

Company confidential

Page 3 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

6 Air interface performance ......................................................................... 51


6.1 Performance and features ..................................................................................................... 51
6.1.1 CS Voice over HSPA .......................................................................................................... 52
6.1.2 HSDPA 64 QAM ................................................................................................................. 53
6.1.3 DC-HSDPA 42Mbps ........................................................................................................... 54
6.1.4 HSUPA 5.8 Mbps ............................................................................................................... 56

7 RU20 BTS Features................................................................................. 57


7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9

Enhanced UltraSite Base Band (EUBB) ................................................................................ 57


Multiradio BTS Concept ......................................................................................................... 58
RF Sharing WCDMA GSM ................................................................................................. 58
Flexi RF Modules................................................................................................................... 58
Multiradio Combiner 850MHz ................................................................................................ 60
Multiradio Combiner 900MHz ................................................................................................ 60
Smart Diplexer ....................................................................................................................... 61
RRH Chaining ....................................................................................................................... 62
Flexi WCDMA Software Download Capability for Antenna Line Devices ............................... 63

References ................................................................................................... 64

Copyright Nokia Siemens Networks 2008

Company confidential

Page 4 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

List of Figures

Figure 1 L1 sync time without and with Fast L1 Synchronisation .................................................................. 12


Figure 2 CS voice over HSPA compared to CS voice over DCH ..................................................................... 22
Figure 3 MIMO architecture .............................................................................................................................. 27
Figure 4 Signal constellations with different modulation types ......................................................................... 30
Figure 5 Comparison of DC-HSDPA and single cell configuration ................................................................... 31
Figure 6 HSUPA Code usage for HSUPA 5.8 Mbps bit rate ............................................................................ 37
Figure 7 HSPA connection channel usage with fractional DPCH..................................................................... 40
Figure 8 DPCCH gating .................................................................................................................................... 44
Figure 9 Concept of Direct Resource Allocation for HSPA............................................................................... 50
Figure 10 Features impact to coverage ............................................................................................................ 51
Figure 11 Features impact to capacity and baseband dimensioning ............................................................... 52
Figure 12 Noise rise with number UEs for UL .................................................................................................. 53
Figure 13 16-QAM vs. 64-QAM SINR requirements ........................................................................................ 54
Figure 14 DL throughput distribution over macro cell layout with DC-HSDPA compared to sum of two
separate WCDMA cells ..................................................................................................................................... 55
Figure 15 Gain of DC-HSDPA on cell throughput ............................................................................................ 55
Figure 16 HSUPA link level performance ......................................................................................................... 56
Figure 17 Multiradio BTS concept .................................................................................................................... 58
Figure 18 Multiradio combiner .......................................................................................................................... 60
Figure 19 Active multiradio combiner ............................................................................................................... 61
Figure 20 Smart diplexer................................................................................................................................... 62
Figure 21 RRH chaining.................................................................................................................................... 63

List of Tables
Table
1
RNC
Features
............................................................................................................................................................................ 7
Table 2 - RNC Features ...................................................................................................................................... 8
Table 3 Feature inter-dependency................................................................................................................... 8
Table 4 - Feature requirements 24kbps Paging Channel ................................................................................ 9
Table 5 Parameters associated with the 24 kbps Paging Channel feature ..................................................... 9
Table 6 Parameters associated with the LTE Inter-working feature .............................................................. 10
Table 7 - Feature requirements Fast L1 Synchronisation ............................................................................. 12
Table 8 Parameters associated with the Fast Layer 1 Synchronisation feature ........................................... 12
Table 9 - Feature requirements Power Saving Mode for BTS....................................................................... 13
Table 10 Parameters associated with the Power Saving Mode for BTS feature........................................... 14
Table 11 - Feature requirements Common Channel Setup........................................................................... 16
Table 12 Parameters associated with the Common Channel Setup feature................................................. 17
Table 13 Parameters associated with the Fast Dormancy feature ................................................................ 19
Table 14 Parameters associated with the Common Channel Setup feature................................................. 21
Table 15 - Maximum HSDPA bit rates with different features .......................................................................... 22
Table 16 - Feature requirements CS Voice over HSPA ................................................................................ 23
Table 17 Parameters associated with the CS Voice over HSPA feature ...................................................... 25
Table 18 - Feature requirements MIMO ........................................................................................................ 28
Table 19 Parameters associated with the MIMO feature .............................................................................. 29
Table 20 - Feature requirements HSDPA 64 QAM ....................................................................................... 30
Table 21 Parameters associated with the HSDPA 64QAM feature .............................................................. 30
Table 22 - Feature requirements DC-HSDPA ............................................................................................... 32
Table 23 Parameters associated with the Dual Cell HSDPA feature ............................................................ 32
Table 24 - Feature requirements Flexible RLC /DL) ...................................................................................... 34
Table 25 Parameters associated with the Downlink Flexible RLC feature .................................................... 34
Table 26 - HSUPA UE Categories with maximum supported bit rates ............................................................. 36
Table 27 - HSUPA bit rates with different RAN features .................................................................................. 36
Table 28 - Feature requirements HSUPA 5.8 Mbps ...................................................................................... 37
Table 29 Parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI features ...................... 37
Copyright Nokia Siemens Networks 2008

Company confidential

Page 5 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Table 30 - Feature requirements HSUPA 2 ms TTI ...................................................................................... 38


Table 31 Parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI features ...................... 39
Table 32 Feature requirements Fractional DPCH ......................................................................................... 40
Table 33 Parameters associated with the Fractional DPCH feature ............................................................. 42
Table 34 - Feature requirements Continuous Packet Connectivity ............................................................... 44
Table 35 Parameters associated with enabling the Continuous Packet Connectivity feature ...................... 45
Table 36 CPC parameters associated with the CS Voice over HSPA service (2ms HSUPA TTI)................ 45
Table 37 CPC parameters associated with other specific connection types ................................................. 47
Table 38 Extended inactivity timers for UE battery power optimisation ........................................................ 47
Table 39 Other parameters associated with the CPC feature ....................................................................... 47
Table 40 - Feature requirements HSPA 72 Users per Cell ........................................................................... 48
Table 41 Parameters associated with the HSPA 72 Users Per Cell feature ................................................. 49
Table 42 Parameters associated with the HSPA 72 Users Per Cell feature ................................................. 50
Table 43 - RNC Features .................................................................................................................................. 51
Table 44 - AMR modes and bit rates on HSPA ................................................................................................ 52
Table 45 - New BTS features ........................................................................................................................... 57
Table 46 - New Flexi Radio Modules ................................................................................................................ 59

Copyright Nokia Siemens Networks 2008

Company confidential

Page 6 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

1 Introduction
The purpose of this guide is to describe the features and parameters of RU20 WCDMA networks.
This document focuses on the key differences introduced by RU20 and their impact on planning
and performance. Prior knowledge of NSN HSPA RAN products and solutions is therefore
expected from the reader.
More detail on 3G radio dimensioning can be found in [1].
More detail on RAS6 / RU10 radio planning can be found in and [2].
RU20 delta training material can be found in [3].

1.1 Summary of RU20 Features


Table 1 lists the new features in RU20 (RN5.0) and RU20 On Top (RN5.0 EP1) releases with the
feature number and license type.
RNC Features

Feature
Number

RU20 License

RAN2067

On top, RNC ON/OFF

RAN1689

On top, RNC ON/OFF

RAN1202

RNC ON/OFF

RAN1642

On top, BTS ON/OFF

Mobility management
LTE Interworking
Voice
CS Voice over HSPA
Radio access bearer combinations
24kbps Paging Channel
HSDPA
MIMO
HSDPA 64 QAM

RAN1643

RNC ON/OFF

DC-HSDPA 42Mbps

RAN1906

On top, RNC capacity

HSUPA 5.8 Mbps

RAN981

RNC ON/OFF

HSUPA 2ms TTI

RAN1470

RNC ON/OFF

Fractional DPCH

RAN1201

RNC ON/OFF

Fast L1 synchronisation

RAN1322

Basic

Continuous Packet Connectivity

RAN1644

RNC ON/OFF

Flexible RLC(DL)

RAN1638

Basic

Power Saving Mode for BTS

RAN955

RNC ON/OFF

HSPA 72 Users per Cell

RAN1686

RNC ON/OFF

Common Channel Setup

RAN1797

RU10 on top, Basic

Fast Dormancy

RAN2136

RU10 on top, Basic

Direct Resource Allocation for HSPA

RAN1762

RU10 on top, Basic

User experience

Capacity and efficiency

Table 1 - RNC Features

Table 2 shows the features with the related 3GPP releases. Release 9 features are not included in
RU20

Copyright Nokia Siemens Networks 2008

Company confidential

Page 7 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
3GPP

Features

Release 7

Continuous packet connectivity


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-HSDPA (64-QAM)
Fast Dormancy

Release 9

MIMO & DC-HSDPA (64-QAM)


DC-HSDPA Multi-band, (> 2 carriers?)

Date: 30.07.2010
Version 1.1

Table 2 - RNC Features

Table 3 lists the main inter-dependencies between the new and existing RNC features together
with the HW requirement and UE release.

Table 3 Feature inter-dependency

The Fast Dormancy Feature requires release 8 or newer UE. The Direct Resource Allocation for
HSPA feature requires HSDPA and HSDPA Dynamic Resource Allocation to be enabled.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 8 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

2 General RRM and DCH features


2.1 24kbps Paging Channel
In RU10 and earlier the paging channel supports 8 kbps rate, in transport channel level TBS of 80
bits and TTI 10 ms. This provides a paging capacity of one paging per 10 ms TTI. Some network
with high paging load can benefit from higher paging capacity, which is provided in RU20 with 24
kbps Paging Channel feature. This feature enables the use of dedicated S-CCPCH with SF128 and
transport channel with 240 bits and 10 ms TTI for paging.
Requirements
UE requirements

None

Network Hardware Requirements

None

Feature Requirements

None

License

RNC ON/OFF license

Table 4 - Feature requirements 24kbps Paging Channel

2.1.1 24 kbps Paging Channel Parameters


The RNC databuild parameters associated with the 24 kbps Paging Channel feature are presented
in Table 5.
Parameter

New

Scope

Range

PCH24kbpsEnabled

WCEL

0 (Disabled), 1 (Enabled)

PtxSCCPCH2SF128

WCEL

35..15 dB, step 0.1 dB

Default

Recommended

0 (Disabled)

1 (Enabled)

-2 dB

-2 dB

Table 5 Parameters associated with the 24 kbps Paging Channel feature

The PCH24kbpsEnabled parameter switches the 24 kbps paging channel on and off, whereas
the PtxSCCPCH2SF128 parameter specifies the transmit power of the relevant S-CCPCH relative
to the transmit power of the CPICH. Increasing this transmit power will help to improve the
coverage of the 24 kbps paging channel. However, it will also reduce the remaining transmit power
available for traffic. The S-CCPCH transferring the FACH supports bit rates of up to 36 kbps so it
makes sense that the S-CCPCH transferring the 24 kbps PCH uses a similar transmit power.

2.2 LTE Interworking


LTE Interworking feature enables the cell reselection from 3G to LTE. LTE adjacencies are defined
in new ADJL objects and corresponding re-selection parameters on HOPL objects. Operators can
set the preference of LTE capable UE either to camp on 3G or LTE by setting of the RAT priority.

2.2.1 LTE Inter-working Parameters


The RNC databuild parameters associated with the LTE Inter-working feature are presented in
Table 6.
Parameter

New

Scope

Range

Default

Recommended

SIB19Priority

RNC

1 to 4, step 1

EUTRAdetection

RNC

Copyright Nokia Siemens Networks 2008

0 (false), 1 (true)

Company confidential

0 (false)

1 (true)

Page 9 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
LTECellReselecPSISHO

WCEL

0 (Disabled), 1 (Enabled)

AbsPrioCellReselec

WCEL

0 to 7, step 1

Sprioritysearch1

WCEL

Sprioritysearch2

Threshservlow

Date: 30.07.2010
Version 1.1

0 (Disabled)

1 (Enabled)

0 to 62, step 2 dB

0 dB

0 dB

WCEL

0 to 7, step 1 dB

0 dB

0 dB

WCEL

0 to 62, step 2 dB

0 dB

0 dB

LoadBasedCPICHEcNoSRB
HSPA

WCEL

-25 to 0, step 1 dB

-25 dB

-25 dB

LoadBasedCPICHEcNoThre
EDCH2MS

WCEL

-25 to 0, step 1 dB

-0 dB

-0 dB

ADJLId

ADJL

0 to 8, step 1

N/A

N/A

AdjLEARFCN

ADJL

0 to 65535

N/A

N/A

AdjLMeasBw

ADJL

6, 15, 25, 50, 75, 100

HopLIdentifier

ADJL

1 to 10, step 1

N/A

N/A

HOPLId

HOPL

1 to 10, step 1

N/A

N/A

AdjLAbsPrioCellReselec

HOPL

0 to 7, step 1

AdjLQrxlevminEUTRA

HOPL

-140 to -44, step 2 dBm

-140 dBm

-140 dBm

AdjLThreshigh

HOPL

0 to 62, step 2 dB

0 dB

0 dB

AdjLThreslow

HOPL

0 to 62, step 2 dB

0 dB

0 dB

Table 6 Parameters associated with the LTE Inter-working feature

The LTECellReselecPSISHO parameter enables/disables cell re-selection from UMTS to LTE.


This parameter has WCEL scope so cell re-selection can be enabled/disabled on a per cell basis.
When enabled, the UMTS network broadcasts the relevant content within SIB19. The
LTECellReselecPSISHO parameter also enables/disables incoming inter-system handover from
LTE to UMTS. The SIB19Priority parameter determines how often SIB19 is broadcast relative to
the other SIB. The size of the SIB also has an impact upon how often SIB are broadcast.
The EUTRAdetection parameter is used to instruct UE whether or not they are allowed to detect
the presence of LTE coverage for the purposes of end-user display information, e.g. the UE could
display an LTE symbol on its screen when within LTE coverage. This flag is broadcast within
SIB19.
LTE does not require the definition of individual neighbour cells. The ADJL parameter object is
used to specify LTE RF carriers (using the AdjLEARFCN parameter). These RF carriers are
broadcast within SIB19 and provide direction for UE completing inter-RAT cell re-selection towards
LTE. A maximum of 8 RF carriers can be specified. This corresponds to the maximum allowed by
3GPP within the release 8 version of TS 25.331. A measurement bandwidth is specified for each
LTE RF carrier using the AdjLMeasBw parameter. The 6 possible values for the measurement
bandwidth (6, 15, 25, 50, 75, 100 resource blocks) correspond to the 6 possible LTE channel
bandwidths (1.4, 3, 5, 10, 15, 20 MHz). Thus, the AdjLMeasBw parameter should be configured to
match the appropriate LTE channel bandwidth.
Each ADJL points toward a HOPL object which includes priority and minimum signal strength
requirement parameters. The AdjLAbsPrioCellReselec parameter allows LTE RF carriers to be
prioritised. If all ADJL point towards the same HOPL then all LTE RF carriers will have the same
Copyright Nokia Siemens Networks 2008

Company confidential

Page 10 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

priority. 0 represents the lowest priority and 7 represents the highest priority. The WCEL
AbsPrioCellReselec parameter defines the absolute priority for the serving UMTS cell. This is
compared with the priority of neighbouring LTE cells during cell re-selection. Neighbouring cells
with higher priority are always measured by the UE. Neighbouring cells with lower priority are
measured when either the CPICH RSCP or CPICH Ec/Io becomes relatively weak. The
Sprioritysearch1 parameter defines a CPICH RSCP threshold relative to Qrxlevmin, whereas the
Sprioritysearch2 parameter defines a CPICH Ec/Io threshold relative to Qqualmin. The UE must
complete neighbour cell measurements if the measured CPICH RSCP Qrxlevmin falls below
Sprioritysearch1, or if the measured CPICH Ec/Io Qqualmin falls below Sprioritysearch2. The
UE may also chose to complete measurements prior to the CPICH falling below these thresholds.
Once measurements have started, the cell re-selection decision is dependent upon the absolute
priorities allocated to each network layer. The AdjLThreshigh parameter defines an RSRP margin
required for cell re-selection to a higher priority network layer. The RSRP margin is specified in
terms of Srxlev = Measured RSRP Qrxlevmin Pcompensation, where Pcompensation =
Max(UE_TXPWR_MAX_RACH P_MAX, 0). Ignoring the impact of Pcompensation,
AdjLThreshigh represents the number of dB that the RSRP must exceed Qrxlevmin before cell reselection is allowed. In the case of LTE neighbours with equal or lower priority, the measured
CPICH RSCP Qrxlevmin of the current serving cell must become less than the value
Threshservlow, or the measured CPICH Ec/Io Qqualmin of the current serving cell must
become less than 0, prior to cell re-selection. In addition, the AdjLThreslow parameter defines an
RSRP margin for cell re-selection to a network layer with equal or lower priority. Ignoring the impact
of Pcompensation, AdjLThreslow represents the number of dB that the RSRP must exceed
Qrxlevmin before cell re-selection is allowed. The use of these thresholds is described in greater
detail within the release 8 version of 3GPP TS 25.304. The AdjLQrxlevminEUTRA parameter
defines the minimum Received Signal Reference Power (RSRP) requirement for an LTE cell to be
acceptable for cell re-selection. RSRP represent the average power of a single LTE resource
element occupied by the reference signal. The default value for the AdjLQrxlevminEUTRA
parameter is set to its minimum. This minimum is consistent with the minimum specified by 3GPP
and means that it will be relatively easy for the UE to identify an LTE with sufficient signal strength.
The LoadBasedCPICHEcNoSRBHSPA parameter is applicable to incoming handovers from LTE.
It defines the coverage area for the SRB on HSPA. If the CPICH Ec/Io is greater than the value of
this parameter then the SRB is allocated HSPA. Otherwise it is allocated a DCH. Likewise, the
LoadBasedCPICHEcNoThreEDCH2MS parameter is also applicable to incoming handovers from
LTE. This parameter defines the coverage area for the HSUPA 2 ms TTI. If the CPICH Ec/Io is
greater than the value of this parameter then HSUPA is allocated the 2 ms TTI. Otherwise, HSUPA
is allocated the 10 ms TTI.

2.3 Fast L1 synchronisation


With the Fast L1 Synchronisation feature the initial DCH channel establishment is shortened by 40
ms. This is done by the network by instructing the UE to use so called post-verification instead of
pre-verification for the L1 synchronisation before starting UL transmission.
Requirements
UE requirements

Cat-6 or later

Network Hardware Requirements

None

Feature Requirements

None

License

None

Copyright Nokia Siemens Networks 2008

Company confidential

Page 11 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Table 7 - Feature requirements Fast L1 Synchronisation

Figure 1 present the different on the L1 synchronisation procedure without and with the Fast L1
Synchronisation feature.
> 90 ms

Node B starts transmitting

UE starts transmitting

10 ms radio
frames
40 ms window
1st in-sync
primitive

UE starts
receiving

4th in-sync
primitive

Delay while UE receives


RRC Connection Setup
message on the FACH

> 20 ms

Node B starts
transmitting

UE starts
transmitting

UE stops transmitting if
verification check fails

10 ms radio
frames
40 ms window
UE starts
receiving

Post verification
check

Figure 1 L1 sync time without and with Fast L1 Synchronisation

2.3.1 Fast Layer 1 Synchronisation Parameters


The RNC databuild parameters associated with the Fast Layer 1 Synchronisation feature are
presented in Table 8.
Parameter

New

Scope

Range

Default

Recommended

PostVerifPeriodDLSynch

RNC

0 (Post-verification period not used),


1 (Post-verification period used)

PCPreamble

RNC

0 to 7 frame, step 1 frame

0 frames

0 frames

SRBDelay

RNC

0 to 7 frame, step 1 frame

7 frames

7 frames

Table 8 Parameters associated with the Fast Layer 1 Synchronisation feature

The PostVerifPeriodDLSynch parameter defines whether or not post-verification is used during


downlink chip and frame synchronisation for release 6 and newer UE. The default value enables
the feature so changes to this parameter are not necessary unless there is a requirement to disable
the feature.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 12 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The previously hidden parameters for the Power Control Preamble and SRB Delay become
configurable with this feature. These are configured using the PCPreamble and SRBDelay
parameters. The Power Control Preamble defines the number of radio frames during which the
upink DPCCH is transmitted without the DPDCH/E-DPCCH/E-DPDCH. This is applied when the
UE establishes its first radio link (from RRC Idle mode or from CELL_FACH). The SRB delay
defines the number of radio frames after the Power Control Preamble during which SRB data
cannot be transferred.

2.4 Power Saving Mode for BTS


With the Power Saving Mode for BTS feature a cell (or multiple cells) can be shut down during low
load periods. A cell is activated on need basis if the traffic load of other active cells is increased.
When one power amplifier is shared among multiple cells, the cell shutdown needs to be done
simultaneously for all those cells. Otherwise this feature does not bring benefits and cannot be
used. RNC monitors the load in downlink and uplink directions and triggers the cell shutdown once
all the following operator adjustable conditions have been met in a cell:

time of day
no emergency calls or Wireless Priority Service calls in cell
traffic load in the cell going below the defined threshold
duration of low traffic
remaining cells not in high load

The feature requires only RNC ON/OFF license.


Requirements
UE requirements

None

Network Hardware Requirements

None

Feature Requirements

None

License

RNC ON/OFF license

Table 9 - Feature requirements Power Saving Mode for BTS

2.4.1 Power Saving Mode for BTS Parameters


The RNC databuild parameters associated with the Power Saving Mode for BTS feature are
presented in Table 10.
Parameter

New

Scope

Range

Default

Recommended

PWSMDuration

RNC

1 to 30 minutes, step 1 minutes

5 minutes

5 minutes

PWSMExceededTrafficDur

RNC

10 to 300 secs, step 10 secs

20 secs

20 secs

PWSMDriftAllowed

RNC

0 (no), 1 (yes)

PWSMInUse

WBTS

0 (off), 1 (on)

PWSMShutdownBeginHour

WBTS

0 to 23 hours, step 1 hours

22 hours

22 hours

PWSMShutdownBeginMin

WBTS

0 to 59 minutes, step 1 minutes

0 minutes

0 minutes

PWSMShutdownEndHour

WBTS

0 to 23 hours, step 1 hours

6 hours

6 hours

PWSMShutdownEndMin

WBTS

0 to 59 minutes, step 1 minutes

0 minutes

0 minutes

PWSMWeekday

WBTS

0 (None), 1 (Saturday),

Copyright Nokia Siemens Networks 2008

Company confidential

0 (no)
0 (off)

0 (None)

0 (no)
1 (on)

0 (None)

Page 13 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

2 (Sunday), 3 (Saturday and


Sunday)
PWSMRemCellSDBeginHour

WBTS

0 to 23 hours, step 1 hours

22 hours

22 hours

PWSMRemCellSDBeginMin

WBTS

0 to 59 minutes, step 1 minutes

0 minutes

0 minutes

PWSMRemCellSDEndHour

WBTS

0 to 23 hours, step 1 hours

6 hours

6 hours

PWSMRemCellSDEndMin

WBTS

0 to 59 minutes, step 1 minutes

0 minutes

0 minutes

PWSMCellGroup

WCEL

0 to 6, step 1

N/A

PWSMShutdownOrder

WCEL

0 to 3, step 1

N/A

PWSMShutdownRemCell

WCEL

0 (NO), 1 (YES)

N/A

PowerSaveHSPAType

WCEL

0 (NoHSPA05ReConf),
1 (HSPA0), 2 (HSPA5)

N/A

PWSMAVPwrNRTHSDPA

WCEL

0 to 50 dBm, step 1 dBm

31

31

PWSMAVLimitNRTHSDPA

WCEL

0 to 300, step 1

10

10

PWSMAVPwrRTHSDPA

WCEL

0 to 50 dBm, step 1 dBm

37 dBm

37 dBm

PWSMAVLimitRTHSDPA

WCEL

0 to 300, step 1

PWSMAVLimitRTDCH

WCEL

0 to 50 dBm, step 1 dBm

37 dBm

37 dBm

PWSMEXPwrLimit

WCEL

0 to 50 dBm, step 1 dBm

37 dBm

37 dBm

PWSMEXUsrLimit

WCEL

0 to 300, step 1

PWSMSDPwrNRTHSDPA

WCEL

0 to 50 dBm, step 1 dBm

34 dBm

34 dBm

PWSMSDLimitNRTHSDPA

WCEL

0 to 300, step 1

PWSMSDPwrRTHSDPA

WCEL

0 to 50 dBm, step 1 dBm

34 dBm

34 dBm

PWSMSDLimitRTHSDPA

WCEL

0 to 300, step 1

PWSMSDLimitNRTDCH

WCEL

0 to 128, step 1

10

10

PWSMSDPwrRTDCH

WCEL

0 to 50 dBm, step 1 dBm

34 dBm

34 dBm

PWSMSDLimitRTDCH

WCEL

0 to 128, step 1

10

10

Table 10 Parameters associated with the Power Saving Mode for BTS feature

The PWSMInUse parameter enables/disables the Power Saving Mode for BTS feature on a per
Node B basis. The default value is OFF so the feature is disabled unless the parameter is changed.
When using this feature, the cells belonging to the Node B need to be organised into PWSM cell
groups. The cell group to which a cell belongs is defined by the WCEL PWSMCellGroup
parameter. The default value of 0 means that the cell does not belong to a cell group so this
parameter requires configuration prior to enabling the feature. The normal strategy is to define one
cell group per sector, i.e. cells belonging to the same sector belong to the same PWSM cell group.
The PWSMShutdownOrder parameter defines the order in which the cells belonging to a specific
cell group are shutdown. Every cell group must have at least one cell which is configured with a
shutdown order value of 0. This value indicates that the cell is a remaining cell and is not targeted
for low traffic shutdown. The value of 1 means that the cell is the first cell within the group to be
targeted for shutdown, while the value of 2 means that the cell is the second cell within the group to
be targeted for shutdown.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 14 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The WCEL PWSMShutdownRemCell parameter defines whether or not a remaining cell can be
shutdown. Remaining cells can be shutdown on the days defined by the PWSMWeekday
parameter. Otherwise, they can be shutdown during the time window defined by the
PWSMRemCellSDBeginHour, PWSMRemCellSDBeginMin, PWSMRemCellSDEndHour and
PWSMRemCellSDEndMin parameters. Remaining cells can only be shutdown when all nonremaining cells within a cell group have already been shutdown. The shutdown of remaining cells
does not depend upon traffic levels (with the exception of emergency calls - which prevent
remaining cells from being shutdown).
In general, the feature is aimed for use during periods of low network activity, i.e. during the night.
Once
the
feature
has
been
enabled,
the
PWSMShutdownBeginHour,
PWSMShutdownBeginMinute, PWSMShutdownEndHour and PWSMShutdownEndMinute
parameters define the time window during which the feature is able to shutdown a cell.
There is a relatively large group of parameters associated with triggering cell shutdown due to low
traffic. The PWSMSDLimitRTDCH and PWSMSDPwrRTDCH parameters define triggering
thresholds for Real Time DCH connections, whereas the PWSMSDLimitNRTDCH parameter
defines a triggering threshold for Non-Real Time DCH. The PWSMSDPwrRTHSDPA and
PWSMSDLimitRTHSDPA parameters define triggering thresholds for Real Time HSPA
connections, whereas the PWSMSDPwrNRTHSDPA and PWSMSDLimitNRTHSDPA parameters
define triggering thresholds for Non-Real Time HSPA connections. A cell shutdown due to low
traffic is attempted if all of the above triggering mechanisms are satisfied for a period of time
defined by the PWSMDuration parameter.
Shutting down a non-remaining cell also involves an admission control check on the target cell to
help ensure that there is sufficient capacity to support the traffic from the cell to be shutdown. This
admission control check is based upon the PWSMEXPwrLimit and PWSMEXUsrLimit parameters.
The PWSMEXUsrLimit parameter is only applicable if HSDPA is enabled at the target cell.
The PWSMDriftAllowed parameter with scope RNC, defines whether or not a cell can be
shutdown due to low traffic when the controlling RNC is a drift RNC for one or more UE. The
default value of this parameter is NO, meaning that cells cannot be shutdown when they have
connected UE for which the controlling RNC is a drift RNC.
Non-Remaining cells can be re-activated after cell shutdown if levels of traffic start to increase. The
PWSMAVLimitRTDCH parameter defines a threshold for Real Time DCH connections, whereas
there is no re-activation triggering threshold based upon Non-Real Time DCH connections. The
PWSMAVPwrRTHSDPA and PWSMAVLimitRTHSDPA parameters define thresholds for Real
Time HSPA connections, whereas the PWSMAVPwrNRTHSDPA and PWSMAVLimitNRTHSDPA
parameters define thresholds for Non-Real Time HSPA connections. A cell re-activation due to
increasing traffic is attempted if all of the above triggering mechanisms are satisfied for a period of
time defined by the PWSMExceededTrafficDur parameter.
The PowerSaveHSPAType parameter defines the HSPA configuration of a cell and whether or not
that configuration can change, or trigger changes when cells are shutdown. Configuring a value of
1 (HSPA0) means that the cell does not normally support HSPA. However, if a cell which is
configured with a value of 2 (HSPA5) is shutdown, then this triggers the enabling of HSPA within
the HSPA0 cell. If a cell is configured as HSPA0 then there must be at least one cell within the
same cell group which is configured as HSPA5. If an HSPA5 cell is re-activated then HSPA can be
re-disabled at the HSPA0 cell. The PowerSaveHSPAType parameter can also be configured with
a value of 0 (NoHSPA05ReConf) which means that the cell does not trigger HSPA to be enabled
in another cell when shutdown, and likewise, does not have HSPA enabled if another cell is
shutdown.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 15 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

2.5 Common Channel Setup


Common Channel Setup feature is introduced in RU10 On Top release CD2. This feature enables
the use of RACH and FACH common channels for RRC connection setups instead of dedicated
channel. Signalling link for the RRC connection setup can be selected between RACH/FACH
common channels, DCH 13.6 kbps or DCH 3.4 kbps according to operator's defined preferences.
Operator defines the preferred signalling link type depending on the UE establishment cause, UE
measurement results (CPICH EC/N0) and common channel load.
Requirements
UE requirements

none

Network Hardware Requirements

None

Feature Requirements

None

License

None

Table 11 - Feature requirements Common Channel Setup

2.5.1 Common Channel Setup Parameters


The Common Channel Setup feature is available as part of RU10. However, the RU10 version of
the feature does not include any configurable parameters within the RNC databuild (parameters
are configured within the PRFILE). The RNC databuild parameters associated with the RU20
version of the Common Channel Setup feature are presented in Table 12.
Parameter

New

Scope

RRCSetupCCHEnabledR99

RNC

SRBMapRRCSetupEC

WCEL

Bit 0: Orig. conv. call


Bit 1: Orig. stream call
Bit 2: Orig. interactive call
Bit 3: Orig. background call
Bit 4: Orig. sub. traffic call
Bit 5: Term. conv. call
Bit 6: Term.stream call
Bit 7: Term.interactive call
Bit 8: Term.background call
Bit 9: Emerg.call,
Bit 10: Inter-RAT cell re-sel.
Bit 11: Inter-RAT CCO
Bit 12: Registration
Bit 13: Detach
Bit 14: Orig. high priority sig.
Bit 15: Orig. low priority sig.
Bit 16: Call re-establishment
Bit 17: Term. high pri. sig.
Bit 18: Term. low pri. sig.
Bit 19: Term. cause unknown
Bit 20: MBMS reception
Bit 21: MBMS ptp RB req.

0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
0
1
1
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
0
1
1
0
0
0

SRBBitRateRRCSetupEC

WCEL

Bit 0: Orig. conv. call


Bit 1: Orig. stream call
Bit 2: Orig. interactive call
Bit 3: Orig. background call
Bit 4: Orig. sub. traffic call

1
1
1
1
1

1
1
1
1
1

Copyright Nokia Siemens Networks 2008

Range
0 (Disabled), 1 ((Enabled)

Company confidential

Default
0 (Disabled)

Recommended
0 (Disabled)

Page 16 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
Bit 5: Term. conv. call
Bit 6: Term.stream call
Bit 7: Term.interactive call
Bit 8: Term.background call
Bit 9: Emerg.call,
Bit 10: Inter-RAT cell re-sel.
Bit 11: Inter-RAT CCO
Bit 12: Registration
Bit 13: Detach
Bit 14: Orig. high priority sig.
Bit 15: Orig. low priority sig.
Bit 16: Call re-establishment
Bit 17: Term. high pri. sig.
Bit 18: Term. low pri. sig.
Bit 19: Term. cause unknown
Bit 20: MBMS reception
Bit 21: MBMS ptp RB req.
CPICHEcNoSRBMapRRC

WCEL

-24 to 0 dB, step 0.5 dB

CCHSetupEnabled

WCEL

0 (Disabled), 1 (Enabled)

RachLoadThresholdCCH

WCEL

FachLoadThresholdCCH

WCEL

PtxThresholdCCH

WCEL

RACHCapacity

WCEL

0 to 100, step 1 %
0 to 100, step 1 %
-5 to 0, step 0.1 dB
1 to 4, step 1

Date: 30.07.2010
Version 1.1

1
1
1
1
1
1
1
0
0
0
0
1
0
0
0
0
0

1
1
1
1
1
1
1
0
0
0
0
1
0
0
0
0
0

-8 dB

-8 dB

0 (Disabled)

1 (Enabled)

75 %

75 %

75 %

75 %

-1 dB

-1 dB

Table 12 Parameters associated with the Common Channel Setup feature

The CCHSetupEnabled parameter is used to enable and disable the feature on a per cell basis.
The parameter in online so can be changed without object locking.
The RRCSetupCCHEnabledR99 parameter is used to determine whether or not release 99 UE
are permitted to establish connections in CELL_FACH rather than CELL_DCH. By default, this
parameter is set to disabled, so release 99 UE are always directed from RRC Idle mode to
CELL_DCH. This parameter is included in case older UE do not support the transition from RRC
Idle mode to CELL_FACH.
The SRBMapRRCSetupEC parameter specifies the set of RRC Connection Request cause values
which trigger the RRC Idle mode to CELL_FACH transition, rather than the RRC Idle mode to
CELL_DCH transition. A value of 1 indicates that the transition to CELL_FACH is used. Bit 9 for
emergency calls does not have any impact because emergency calls are always directed to
CELL_DCH. By default, the registration, detach, originating high priority signaling, originating low
priority signaling, terminating high priority signaling and terminating low priority signaling cause
values are selected as those which trigger the transition to CELL_FACH. This selection of cause
values means that signaling procedures can be completed entirely in CELL_FACH without
requiring a transition to CELL_DCH, i.e. the sequence would be RRC Idle mode -> CELL_FACH ->
RRC Idle mode. Some UE use the high priority signaling cause value for PS data connections.
These connections may or may not make a subsequent transition to CELL_DCH. If the data
transfer is small, e.g. a keep-alive, then the UE is likely to remain in CELL_FACH before returning
to RRC Idle mode or moving into CELL_PCH. If the data transfer is larger then the UE is likely to
trigger an upgrade from CELL_FACH to CELL_DCH. The benefit of completing signaling
procedures in CELL_FACH is a reduction of the CNBAP signaling at the Node B, i.e. the radio link
setup procedure is not required. This is important because Node B are limited in terms of the rate
at which radio link setup procedures which can be processed. Completing signaling on the
common channels also helps to reduce RNC ICSU load. The drawback of establishing connections
Copyright Nokia Siemens Networks 2008

Company confidential

Page 17 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

in CELL_FACH is an increased common channel load, i.e. the utilization of the RACH and FACH
increases.
The CPICHEcNoSRBMapRRC parameter defines the minimum CPICH Ec/Io required for
connection establishment in CELL_FACH. Connections are established in CELL_DCH if the
CPICH Ec/Io reported within the RRC Connection Request message is less than the value of this
parameter. This parameter can effectively be disabled by configuring it with its smallest value.
However, the objective is to ensure that UE are only allowed to establish connections in
CELL_FACH when the coverage conditions are relatively good.
The SRBBitRateRRCSetupEC parameter specifies the set of RRC Connection Request cause
values which use the 13.6 kbps standalone SRB when connections are established in CELL_DCH
rather than CELL_FACH, i.e. this parameter does not impact connections which are directed from
RRC Idle mode to CELL_FACH. A value of 1 indicates that the 13.6 kbps standalone SRB is
allocated in CELL_DCH. The default value of this parameter allows a relatively large set of
establishment causes to use the 13.6 kbps standalone SRB. This provides the benefit of decreased
connection establishment time at the cost of a greater Iub bandwidth reservation. Note that the
previously used StandAloneDCCHBitRate parameter is deleted in RU20.
The RachLoadThresholdCCH parameter defines a threshold for the RACH load. Connections are
established in CELL_DCH if the RACH load exceeds the value of this threshold. The RACH load is
quantified as the average number of acknowledged PRACH preambles over 2 radio frames,
relative to the value of the RACHCapacity parameter multiplied by 2. The factor of 2 is included
because the RACHCapacity parameter defines the number of messages which can be decoded
per 10 ms radio frame. The default value for this parameter is 75 %, corresponding to 3 out of 4 (or
6 out of 8) RACH messages per 20 ms.
The RACHCapacity parameter specifies the maximum number of RACH messages which are
decoded during a 10 ms radio frame. This parameter requires object locking for modification. The
default value is 2 messages but it is recommended to increase this to 4 messages when the
common channel setup feature is enabled. Using a larger value increases the capacity of the
RACH to handle the increased load generated by establishing connections in CELL_FACH.
The FachLoadThresholdCCH parameter defines a threshold for the FACH load. Connections are
established in CELL_DCH if the FACH load exceeds the value of this threshold. The FACH load is
quantified as the S-CCPCH throughput measured at the bottom of the physical layer relative to the
maximum capability of the S-CCPCH. The default value for this parameter is 75 %, corresponding
to a S-CCPCH activity factor of 75 %.
The PtxThresholdCCH parameter defines a threshold relative to PtxTarget for the total downlink
transmit power. Connections are established in CELL_DCH if the total downlink transmit power
exceeds the value of this threshold. The default value is -1 dB corresponding to a threshold of 41
dBm when PtxTarget is configured with a value of 42 dBm. Connections are established in
CELL_DCH rather than CELL_FACH when the total downlink transmit power is high because
DPCH connections are more efficient on the air-interface as a result of using inner loop power
control.

2.6 Fast Dormancy


Fast Dormancy feature is introduced in RU20 On Top. The Fast Dormancy feature modifies the
system behaviour associated with the original Fast Dormancy introduced by UE vendors. UE
vendors originally introduced Fast Dormancy as a means to increase UE battery life. The original
Fast Dormancy procedure allows UE to release themselves to RRC Idle mode by sending a
Signalling Connection Release Indication (SCRI) after completing their data transfer. The RNC is
Copyright Nokia Siemens Networks 2008

Company confidential

Page 18 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

forced to release the UE to RRC Idle mode (to comply with the 3GPP specifications). UE power
consumption is minimised in RRC Idle mode so battery life is prolonged. However, the transition to
Idle mode defeats the purpose of having CELL_PCH and URA_PCH. UE power consumption in
these RRC states is only slightly greater than that in RRC Idle mode (potentially shorter DRX cycle
and Cell or URA updates required). A major drawback of the original Fast Dormancy introduced by
UE vendors is that the signalling load can increase significantly. Smart phones can send frequent
polls or keep-alives causing UE to ping-pong between RRC Idle mode and RRC Connected
mode (typically every 60 to 90 seconds). The Common Channel Setup feature helps to some
extent by avoiding the use of CELL_DCH.
The issues associated with the UE vendor version of Fast Dormancy were raised within 3GPP.
3GPP agreed to modify the specifications from release 8 such that the RNC can keep the UE in
RRC Connected mode after receiving a SCRI. A cause value was introduced which could be
included within the SCRI message. This cause value of UE Requested PS Data Session End
informs the RNC that the UE can be moved out of CELL_DCH because the data transfer has
finished. Instead of being released to RRC Idle mode, the RNC moves the UE into CELL_PCH or
URA_PCH. UE battery life remains prolonged because power consumption in CELL_PCH and
URA_PCH is low. Also, the signalling load is reduced because UE remain in RRC Connected
mode. Polls and keep alives can be sent in CELL_FACH without making the transition to
CELL_DCH.
An SCRI message with cause UE Requested PS Data Session End allows the RNC to overide the
normal inactivity timers. The RNC instructs the UE to make the state change to CELL_PCH or
URA_PCH. If the RNC receives an SCRI without a cause value then the existing legacy
functionality is applied and the UE is moved to RRC Idle mode.

2.6.1 Fast Dormancy Parameters


The RNC databuild parameters associated with the Fast Dormancy feature are presented in Table
13
Parameter

New

Scope

Range

Default

FastDormancyEnabled

RNC

0 (Disabled), 1 ((Enabled)

0 (Disabled)

1 (Enabled)

T323 (hard coded)

RNC

0, 5, 10, 20, 30, 60, 90,


120 secs

0 secs

0 secs

FastDormOverCpcPri

RNC

0 (Fast Dormancy has


higher priority), 1 (CPC
has higher priority)

0 (Fast
Dormancy has
higher priority),

Recommended

0 (Fast
Dormancy has
higher priority),

Table 13 Parameters associated with the Fast Dormancy feature

The FastDormancyEnabled parameter is used to enable and disable the feature on a per RNC
basis. The parameter in online so can be changed without object locking. Enabling the feature also
requires the existing MSActivitySupervision parameter to be configured with a value > 0 to
enable the PCH states. Enabling the feature results in T323 being broadcast within SIB1. The
inclusion of T323 within SIB1 allows the UE to detect that the network supports Fast Dormancy.
The T323 parameter is hard coded with a value of 0 seconds. This parameter does not belong to
the normal RNC databuild and is not configurable. The T323 timer is used as a guard timer to avoid
too frequent transmissions of the Signalling Connection Release Indicator (SCRI) message. It is
started when the UE sends a SCRI which includes the Cause information element. UE are not
permitted to send a subsequent SCRI which includes the Cause information element until T323
expires.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 19 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The FastDormOverCpcPri parameter allows priority to be given to either the Fast Dormancy
feature or the Continuous Packet Connectivity (CPC) feature. Fast Dormancy acts to move UE into
PCH states, whereas CPC acts to hold UE in CELL_DCH. If FastDormOverCpcPri is set to 0 and
the UE is requesting Fast Dormancy then the UE is moved into CELL_PCH or URA_PCH.
Otherwise, if FastDormOverCpcPri is set to 1 and the UE is requesting Fast Dormancy then the
UE state is not changed.

2.7 Changes to other features


RU20 introduces possibility to restrict the bitrate of the HSDPA UL DCH return channel. The new
WCEL-parameter HSDPAMaxBitrateUL defines the maximum bitrate for HSDPA UL DCH return
channel. Restriction will be effective to the PS NRT RAB. Existing WCEL-parameter
MaxBitRateULPSNRT shall not affect the HSDPA UL DCH return channel anymore but it is
applicable to the UL DCH channel only when DL DCH is allocated.
In case of multiple PS RABs, the total bit rate of the radio link shall be balanced between radio
bearers in order to guarantee DCH bit rate to all established NRT PS RABs. Balancing shall be
targeted at NRT PS RAB(s), not RT PS RAB. DCH bit rate balancing shall be controlled by the new
RNW-parameter DCHBitRateBalancing (RNC object class). Bit rate of the existing DCH shall not
be downgraded lower than the initial bit rate. DCH bit rate balancing shall be applied to the HSDPA
UL DCH return channel.
HSUPA user (PS RBs on HSPA + SRBs on DCH) can be selected as target for RT-over-(N)RT or
pre-emption actions in case of BTS congestion for R99 user (existing functionality). In these cases
the cell specific admission control can select a HSPA user as target for RT-over-(N)RT or preemption actions, if the license 1754 HSUPA Pre-emption exists and the state is On. PRFILE
parameter RN40_MAINT_007 (007:276) is not used anymore for this purpose, but it is replaced
with this new license.
RNC20 introduces a possibility transfer A-GPS in system information block SIB15 (new). This will
enable the A-GPS capable UEs to receive this data without dedicated signalling.
In RU10 the HSDPA capable UEs can be directed from the HSDPA capable cell to another HSDPA
capable cell for load balancing reasons if HSDPALayeringCommonChEnabled is enabled in the
source cell, the UE is requesting interactive or background service, the HSDPA capable cell is in
the same sector and the HSDPA load of the target cell is suitable. In RU20 the requested services
are separately enabled with ServBtwnHSDPALayers parameter.
RU20 introduces multiple improvements which enhance the signalling performance. The first
improvements were already included in the Common Channel Setup feature in RU10 CD2 and
RU20 adds other improvements. In RU20 the SRB4 not used anymore, which simplifies the
messaging. Reduced Radio Bearer mapping (same info utilised for multiple bearers etc.)
information decreases the message sizes. The impacted procedures in L3 are:

RRC Connection setup


Non-Real-Time PS RAB setup
State Transition Cell_FACH->Cell_DCH
Any Radio Bearer and Transport Channel reconfigurations

These changes together with the Common Channel Setup feature will shorten message delays and
improve success rate, reduce resource usage in Iub, RNC ICSU and BTS.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 20 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
Parameter

Date: 30.07.2010
Version 1.1

New

Scope

Range

Default

Recommen
ded

WCEL

1 (16 kbps), 3 (64 kbps), 4


(128 kbps), 6 (384 kbps)

6 (384 kbps)

6 (384
kbps)

InacUserNbrXXXOverNRT

RNC

SIB15_priority

RNC

1..4, step 1

4 (lowest)

BroadcastSIB15

WBTS

0 (Disabled), 1 (Enabled)

0 (Disabled)

BroadcastSIB15_2

WBTS

0 (Disabled), 1 (Enabled)

0 (Disabled)

BroadcastSIB15_3

WBTS

0 (Disabled), 1 (Enabled)

0 (Disabled)

ServBtwnHSDPALayers

RNC

Bit 0: Background Call , Bit


1: Interactive Call , Bit 2: PS
Streaming Call , Bit 3: CS
voice Call

3 (BG and
I/A)

HSDPAMaxBitrateUL
HSDPACapUEInServiceHO

3 (BG and
I/A)

Table 14 Parameters associated with the Common Channel Setup feature

Copyright Nokia Siemens Networks 2008

Company confidential

Page 21 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

3 HSDPA features
3.1 HSDPA bit rates
The maximum HSDPA bit rates supported by the RAN depend on the RAN configuration and active
features. Table 15 lists the maximum user bit rates with different features. The DC-HSDPA bit rate
is double of 64-QAM user bit rate and the transport block size is the total of two transport blocks.
The MIMO bit rate is similarly double of 14.4 Mbps per user bit rate. The 64-QAM, DC-HSDPA and
MIMO features require usage of Flexible RLC, thus the number of TB for these features is not
integer value (see more in ??).
Features

16-QAM
Cat-6
16-QAM
5
4.8
7168
3.58

+ 10/15
code
Cat-8
16-QAM
10
9.6
13904
6.95

+10 Mbps/
user
Cat-9
16-QAM
15
14.4
19891
9.95

+14.4 Mbps/
user
Cat-10
16-QAM
15
14.4
27952
14.0

HSDPA
64-QAM
Cat-14
64-QAM
15
21.6
42192
21.1

DC-HSDPA
(2 flows)
Cat-24
64-QAM
30
43.2
84384
42.2

MIMO
(2 flows)
Cat-16
16-QAM
30
28.8
55904
28.0

Min. UE Category
Modulation
Number of HS-PDSCH codes
Air interface bit rate (Mbps)
Max. transport block size (bits)
Max. transport channel (HSDSCH) bit rate (Mbps)
RLC PDU (bits)
RLC blocks/TTI
RLC bit rate (Mbps)
RLC payload (Mbps)
RLC payload (Mbps) - 10%
HARQ retrans.
TCP/IP payload (Mbps)

336
21
3.53
3.36
3.02

656
21
6.89
6.72
6.05

656
30
9.84
9.60
8.64

656
42
13.8
13.4
12.1

11216
3.76
21.1
21.0
18.9

22432
7.51
42.1
42.1
37.9

1312
84
27.6
26.9
24.2

2.94

5.89

8.41

11.8

18.4

36.8

23.5

Table 15 - Maximum HSDPA bit rates with different features

3.2 CS Voice over HSPA


With the CS Voice over HSPA feature the transport channels of the AMR RAB are mapped to the
HSPA bearer type (HSDPA in DL and HSUPA in UL). There are no changes on the RAB level, but
the L2 RLC and transport channel is different from AMR over DCH channel type (see Figure 2).
This feature supports both NB-AMR and WB-AMR together with various CS+ PS multirab
combinations over HSPA channel type.

Figure 2 CS voice over HSPA compared to CS voice over DCH

Copyright Nokia Siemens Networks 2008

Company confidential

Page 22 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Table 16 lists the required features and HW. The QoS aware HSPA scheduling feature is required
in order to prioritise the CS Voice traffic over the PS traffic in the HSPA schedulers.
Requirements
UE requirements

3GPP Rel-7 (late release) or Rel-8

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB
RNC with CDSP-DH cards
HSPA Peak Rate Upgrade in RNC196 and RNC450

Feature Requirements

HSUPA basic
HSDPA Dynamic Resource Allocation
HSDPA with Simultaneous AMR Voice Call
HSUPA with Simultaneous AMR Voice Call
Fractional DPCH
QoS aware HSPA scheduling
Flexible RLC
Continuous Packet Connectivity

License

RNC ON/OFF license

Table 16 - Feature requirements CS Voice over HSPA

3.2.1 CS Voice over HSPA Parameters


The RNC databuild parameters associated with the CS Voice over HSPA feature are presented in
Table 17.
Parameter

New

Scope

Range

Default

Recommended

HSPAQoSEnabled

WCEL

0 (QoS prioritization is not


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

PriForConvOnHSPA

RNC

0 to 14, step 1

14

14

MaxNbrOfHSSCCHCodes

WCEL

1 to 4, step 1

UsersPerHSSCCHCode

WCEL

1 to 40, step 1

30

30

PtxTargetTotMin

WCEL

-10 to 50 dBm, step 0.1 dBm

40 dBm

40 dBm

PtxTargetTotMax

WCEL

-10 to 50 dBm, step 0.1 dBm

41 dBm

41 dBm

RRMULDCHActivityFactorCS
AMR

WBTS

0 to 100 %, step 1 %

50 %

50 %

PrxTargetMax

WCEL

0 to 30 dB, step 0.1 dB

4 dB

4 dB

VoiceOverrideSTHSUPA

WCEL

0 (Override not allowed),


1 (Override allowed)

MaxSetOfEDPDCHCSAMR2

RNC

0 (SF8), 1 (SF4)

MaxSetOfEDPDCHCSAMR10

RNC

0 (SF32), 1 (SF16)

Copyright Nokia Siemens Networks 2008

Company confidential

Page 23 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

MaxEHARQReTxCSAMR2

RNC

0 to 5, step 1

MaxEHARQReTxCSAMR10

RNC

0 to 3, step 1

EDCHMuxVoiceTTI10

RNC

Bit 0: Signaling link


Bit 1: PS streaming
Bit 2: PS interactive THP 1
Bit 3: PS interactive THP 2
Bit 4: PS interactive THP 3
Bit 5: PS Background

63

63

EDCHMuxVoiceTTI2

RNC

Bit 0: Signaling link


Bit 1: PS streaming
Bit 2: PS interactive THP 1
Bit 3: PS interactive THP 2
Bit 4: PS interactive THP 3
Bit 5: PS Background

63

63

PowerOffsetEHARQVoice

RNC

0 to 6 dB, step 1 dB

0 dB

0 dB

EbNoEDCHCSAMR

WRAB

-11 to 20 dB, step 0.1 dB

4 dB

4 dB

DiscardTimerHSCSVoice

RNC

0 (Discard Timer not used), 1


(20 ms), 2 (40 ms), 3 (60 ms),
4 (80 ms), 5 (100 ms), 6 (120
ms), 7 (140 ms), 8 (160 ms), 9
(180 ms), 10 (200 ms)

T1HSCSVoice

RNC

0 (10 ms), 1 (20 ms), 2 (30


ms), 3 (40 ms), 4 (50 ms), 5
(60 ms), 6 (70 ms), 7 (80 ms),
8 (90 ms), 9 (100 ms), 10 (120
ms), 11 (140 ms), 12 (160 ms),
13 (180 ms), 14 (200 ms)

MaxCSDelayUE

RNC

20 to 200 ms, step 10 ms

60 ms

60 ms

MaxCSDelayRNCETTI2

RNC

20 to 200 ms, step 10 ms

80 ms

80 ms

MaxCSDelayRNCETTI10

RNC

20 to 200 ms, step 10 ms

50 ms

50 ms

HSPAForPriEnabled

RNC

0 (HSPA support disabled),


1 (HSPA support enabled)

DRRCForHSDPALayerServic
es

RNC

Bit 0: Conversational Call , Bit


1: Streaming Call , Bit 2:
Interactive Call , Bit 3:
Background Call , Bit 4:
Subscribed traffic Call , Bit 5:
Emergency Call , Bit 6: InterRAT cell re-selection , Bit 7:
Inter-RAT cell change order ,
Bit 8: Registration , Bit 9: High
Priority Signalling , Bit 10: Low
Priority Signalling , Bit 11: Call
re-establishment , Bit 12:
Terminating cause unknown ,
Bit 13: MBMS reception , Bit
14: MBMS ptp RB request , Bit
15: Other , Bit 16: Conv Call
with F-DPCH

204

204

ServBtwnHSDPALayers

RNC

Bit 0: Background Call


Bit 1: Interactive Call
Bit 2: PS Streaming Call
Bit 3: CS voice Call

HSCAHORabCombSupport

RNC

Bit 0: PS I/B RAB (always 1),

Copyright Nokia Siemens Networks 2008

Company confidential

Page 24 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Bit 1: PS Streaming , Bit 2: 2/3


NRT PS RAB , Bit 3: PS
Streaming+1/2/3
NRT
PS
RAB's , Bit 4: CS AMR + 1 PS
I/B RAB , Bit 5: CS AMR + 2/3
PS I/B RAB's , Bit 6: CS AMR
+ PS Streaming , Bit 7: CS
AMR + PS Streaming+1/2/3
NRT RAB's , Bit 8: CS AMR
RAB
PBSHSMinAllocHigher

WCEL

0 to 60 s, step 1 s

30 s

30 s

PBSHSMinAllocEqual

WCEL

0 to 60 s, step 1 s

20 s

20 s

PBSHSMinAllocLower

WCEL

0 to 60 s, step 1 s

15 s

15 s

Table 17 Parameters associated with the CS Voice over HSPA feature

The HSPAQoSEnabled parameter is used to enable and disable the feature on a per WCEL basis.
This parameter must be configured with a value of either 3 or 4, and requires object locking for
modification. The HSPAQoSEnabled parameter is an existing parameter from RU10 which has
had its range extended for RU20.
The PriForConvOnHSPA parameter belongs to the QoSPriorityMapping parameter structure. Its
used to define a Scheduling Priority Indicator (SPI) for the CS Voice over HSPA service. The SPI
allocated to the CS Voice over HSPA service should be greater than that for PS streaming but less
than that for the SRB. The SPI impacts traffic handling on the Iub as well as on the air-interface.
The RNC limits the number of conversational connections using HSDPA to the value defined by
MaxNbrofHSSCCHCodes UsersPerHSSCCHCode. The value of MaxNbrofHSSCCHCodes is
determined by whether or not code multiplexing is enabled. Enabling code multiplexing increases
the number of supported CS Voice over HSPA connections. MaxNbrofHSSCCHCodes is an
existing RAS06 parameter although its maximum value is increased from 3 to 4 in RU10.
UsersPerHSSCCHCode is a new parameter for RU20 with a maximum value of 40 users per HSSCCH.
The PtxTargetTotMin and PtxTargetTotMax parameters define the dynamic range for the load
control threshold, PtxTargetTot. PtxTargetTot is used for admission decisions when there is noncontrollable load on HSDPA. PtxTargetTotMin must be greater than or equal to PtxTarget i.e. if
PtxTarget has been increased to 42 dBm then both PtxTargetTotMin and PtxTargetTotMax must
be increased from their default values. PtxTargetTotMax should not be set greater than
PtxCellMax.
The RRMULDCHActivityFactorCSAMR parameter is an existing parameter used to estimate the
downlink transmit power requirement of a new CS voice connection. The parameter name implies
that it is used only for the uplink (includes UL) but the parameter is also used for downlink power
estimation.
The PrxTargetMax parameter defines the upper limit for the dynamic range of the load control
threshold, PrxTargetAMR. The lower limit is defined by the PrxTarget parameter. This means that
the value of PrxTargetMax must be increased from its default if PrxTarget has been allocated a
high value. The PrxTargetAMR threshold is applicable to SRB and speech connections. This
threshold is applied irrespective of whether or not the CS Voice over HSPA feature is enabled.
The VoiceOverrideSTHSUPA parameter impacts the definition of the RSSI within the uplink
admission control decision for CS Voice over HSPA connections. If configured with a value of
Copyright Nokia Siemens Networks 2008

Company confidential

Page 25 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Override not allowed then RSSI = MAX(PrxTotal, PrxNonEDCHST). Otherwise, if configured with
a value of Override allowed then RSSI = PrxNonEDCHST. This means that a smaller value is
potentially used when override is allowed.
The MaxSetOfEDPDCHCSAMR2 and MaxSetOfEDPDCHCSAMR10 parameters define the
maximum E-DPDCH configuration for the 2 and 10 ms TTI. In both cases, only a single E-DPDCH
is allocated so these parameter define the spreading factor of that E-DPDCH. Smaller spreading
factors are allowed for the 2 ms TTI to permit higher instantaneous throughputs, i.e. to allow the
same quantity of data to be transferred in 2 ms rather than 10 ms.
The MaxEHARQReTxCSAMR2 and MaxEHARQReTxCSAMR10 parameters define the maximum
number of HSUPA re-transmissions allowed for CS voice over HSPA connections. In both cases,
the default value is relatively small because speech data quickly becomes obsolete, i.e. there is no
point in completing too many retransmissions because the delay becomes too great.
The EDCHMuxVoiceTTI2 and EDCHMuxVoiceTTI10 parameters define whether or not other EDCH MAC-d flow data can be multiplexed within the same MAC-e PDU as CS Voice. The default
values for these parameters allow multiplexing. In general, the SRB has a higher SPI than CS
Voice so is prioritised during E-TFC selection. However, the maximum SRB bit rate is limited to
ensure that at least 1 CS Voice frame can always be transmitted together with the SRB.
The PowerOffsetEHARQVoice parameter allows a power offset to be applied to the HARQ
process used to transfer the CS Voice. The parameter is only applicable if another E-DCH MAC-d
flow is multiplexed within the same MAC-e PDU as CS Voice. Otherwise the power offset is 0 dB.
The EbNoEDCHCSAMR parameter belongs to the WRAB object. This HSUPA Eb/No requirement
is used by the RNC when estimating the uplink load generated by an HSUPA connection
transferring CS voice. The same parameter is applicable to both 2 ms and 10 ms TTI, and to all
AMR CODEC sets.
The DiscardTimerHSCSVoice parameter is used by the Node B to ensure that data is not
buffered for too long, i.e. data is discarded by the Node B if a positive HARQ acknowledgement is
not received before the timer expires. Similarly, the T1HSCSVoice parameter defines the T1 timer
used by the UE to determine when received data should be forwarded to the higher layers despite
there being missing data with lower sequence numbers. The T1HSCSVoice parameter defines the
T1 timer for CS voice over HSPA connections. The non-configurable T1 parameter with a value of
120 ms is used for other connection types.
The MaxCSDelayUE parameter defines the maximum buffering time for CS voice frames within the
UE de-jittering buffer. The dejitter buffer helps to remove the impact of delay variation. The
MaxCSDelayRNCETTI2 and MaxCSDelayRNCETTI2 parameters define the equivalent maximum
buffering time for CS voice frames within the RNC.
The HSPAForPriEnabled parameter indicates whether or not conversational RAB capable of preemption can be mapped onto HSPA. The priority of the user for pre-emption is defined by the RAB
pre-emption parameters. Conversational HSPA connections can trigger pre-emption, while
conversational DCH and standalone SRB can trigger pre-emption of conversational HSPA users.
The existing DRRCForHSDPALayerServices parameter is updated to include a cause value of
Conversational Call with F-DPCH. This parameter is applied when enhanced Directed RRC
Connection Setup for HSDPA is enabled.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 26 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The ServBtwnHSDPALayers parameter is introduced in RU20 and is not specific to the CS Voice
over HSPA feature, i.e. it is always used when HSDPA Common Channel Layering is enabled. It
specifies the connection types which should be re-directed between HSDPA layers when making
the CELL_FACH to CELL_DCH transition. This parameter does not impact Directed RRC
Connection Setup from RRC Idle mode.
The existing HSCAHORabCombSupport parameter is updated to include a cause value of CS
AMR RAB. Allows Capability based Handover to be triggered for CS Voice over HSPA
connections.
In the case of NRT-over-NRT, the RNP parameter IurPriority defines how own users and users of
other RNC are prioritized. The existing PBSPolicy parameter defines the way in which the priority
of the new service and existing services are used during victim selection. Victim selection also
depends upon their connection allocation duration. An existing connection can only be selected as
a victim if the allocation time exceeds the value of the relevant parameter: PBSHSMinAllocHigher,
PBSHSMinAllocEqual, PBSHSMinAllocLower. When the potential victims are found, then a
selection is done in order of QoS priority (QoSPriorityMapping) of the victims.

3.3 MIMO
MIMO feature introduces the support for MIMO technology for HSDPA in DL. MIMO utilises
combination of two antennas and two receive antennas (2x2 MIMO) together with BTS and MIMO
pre-coding in BTS and de-coding in terminal side (see Figure 3). The pre-coding utilises channel
information received from the terminal in HS-DPCCH channel.

Figure 3 MIMO architecture

BTS scheduler can transmit either same data or different data in the two parallel MIMO channels
depending on the channel quality information received from the UE. There two modes are called
single stream and dual stream correspondingly. With dual stream mode the BTS can transmit two
different transport blocks in the parallel MIMO channels. This enables up to double data rates. This
means up to 28 Mbps (see Table 15) in RU20, as the MIMO is enabled only with 16 QAM, not 64QAM modulation. In single stream MIMO mode the same data is transmitted over the two MIMO
channels and combination of transmit and receive diversity can be achieved enabling higher bit
rates over radio channel.
It should be noted that MIMO utilises very distinct spatial properties of the radio channel in order to
be able to separate the two different MIMO channels. These radio channel properties are highly
Copyright Nokia Siemens Networks 2008

Company confidential

Page 27 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

variable and dependent on the propagation environment. Thus the maximum radio link
performance can be achieved only in specific conditions. See ?? for more details on the MIMO
performance.
MIMO operation has some limitations

MIMO can not be enabled simultaneously with DC-HSDPA feature and does not
support 64-QAM HSDPA.
MIMO can be used only with NRT PS services, also NRT HSPA .??
MIMO is preferred over 64-QAM when both supported.
Only one layer can be configured MIMO capable in the BTS.

The mobility of the UEs between the MIMO layer and the other layers is handled by combination of
multiple features:

MIMO Capability Based Handover shall move MIMO UE to MIMO layer and nonMIMO UEs away from MIMO layer.
Service and load based HO, and Directed RRC connection setup (for HSDPA) do
not direct any UE to MIMO layer
Directed RRC connection setup and HSPA layering for UEs in common channels
features shall move non-MIMO services from the MIMO layer

Table 18 lists the required features and HW.


Requirements
UE requirements

3GPP Rel-7 (Cat-15, Cat-16, Cat-17, Cat-18) and


Rel-8 (Cat-19, Cat-20) with 16-QAM only

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB
Double PA units and antenna lines
RNC with CDSP-DH cards
HSPA Peak Rate Upgrade in RNC196 and RNC450

Feature Requirements

HSUPA basic
HSDPA Dynamic Resource Allocation
HSDPA 14 Mbps per user
Fractional DPCH
Flexible RLC
Continuous Packet Connectivity

License

RNC Capacity (Cell) license

Table 18 - Feature requirements MIMO

3.3.1 MIMO Parameters


The RNC databuild parameters associated with the MIMO feature are presented in Table 19.
Parameter

New

Scope

MIMOEnabled

WCEL

MIMOHSDPACapaHO

NonMIMOPrevention

Copyright Nokia Siemens Networks 2008

Range

Default

Recommended

0 (Disabled), 1 (Enabled)

WCEL

0 (Disabled), 1 (Enabled)

WCEL

0 (Disabled), 1 (Enabled)

Company confidential

Page 28 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
MIMOCapaHORABSupport

RNC

PtxPrimaryCPICH

WCEL

MaxBitRateNRTMACDFlow

RNC

128 to 42112, step 128 kbps,


65535 (not restricted)

MaxIurNRTHSDSCHBitRate

IUR

128 to 42112, step 128 kbps,


0 (not restricted)

Date: 30.07.2010
Version 1.1

Bit 0: PS NRT RAB,


Bit 1: 2/3 PS NRT RAB,
Bit 2: PS Streaming,
Bit 3: PS Stre + 1-3 PS NRT RAB,
Bit 4: Other services
-10 to 50, step 0.1 dBm

33 dBm

33 dBm

65535

65535

Table 19 Parameters associated with the MIMO feature

The MIMOEnabled parameter enables and disables MIMO on a per cell basis. This parameter
requires object locking for modification so the cell must be locked prior to enabling MIMO. The
MIMOHSDPACapaHO parameter enables and disables MIMO HSDPA Capability based
Handover. If this parameter is set to enabled then HSPA Capability based Handover is
automatically disabled, i.e. either MIMO HSDPA Capability based Handover or HSPA Capability
based Handover can be enabled. This parameter does not require object locking for modification.
The NonMIMOPrevention parameter enables and disables the functionality used to prohibit the
use of non-MIMO HSDPA connections within a cell. This parameter can be set to enabled within
both MIMO enabled cells and MIMO disabled cells. In the latter case, the parameter does not
prohibit the use of non-MIMO connections. When the parameter is enabled within a MIMO cell then
non-MIMO connections are allocated DCH rather than HS-DSCH. MIMO HSDPA Capability based
Handover can then be used to move those connections onto a non-MIMO RF carrier. The
NonMIMOPrevention parameter requires object locking for modification.
The MIMOCapaHORABSupport parameter is only applied if the NonMIMOPrevention parameter
is enabled. In that case, the parameter defines the set of services which are targeted by MIMO
HSDPA Capability based Handover, i.e. a MIMO capable UE using one of the specified services is
moved onto the MIMO HSDPA RF carrier.
The PtxPrimaryCPICH parameter remains the same as for previous RAN software releases with
the exception that when MIMO is enabled, it defines the transmit power of the secondary CPICH as
well as the primary CPICH, i.e. it defines the CPICH transmit power from each antenna element.
The MaxBitRateNRTMacdflow parameter allows the operator to limit the maximum rate at which
HSDPA data is transferred from the RNC to the Node B. In general, it is not necessary to define a
limit and the default value of 65535 should be configured. The parameter has an RNC scope so
any bit rate limit defined by this parameter will impact all cells parented by that RNC.
Similarly, the MaxIurNRTHSDSCHBitRate parameter allows the operator to limit the maximum
rate at which HSDPA data is transferred across the Iur. In general, it is not necessary to define a
limit and the default value of 0 should be configured. The parameter has an Iur scope so any bit
rate limit defined only impacts connections using a specific Iur.

3.4 HSDPA 64 QAM


HSDPA 64 QAM feature adds the support for 64-QAM modulation introduced in 3GPP Rel7 to
HSDPA. This increases the number of transmitted bits per symbol from 4 in 16-QAM to 6 in 64QAM, thus increasing the air-interface rate by 50% to 21 Mbps. The use of 64-QAM is supported
by the UE categories 13, 14, 17 and 18. More detailed calculation of the theoretical user bit rates is
presented in Section 3.1.
Copyright Nokia Siemens Networks 2008

Company confidential

Page 29 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The usage of HSDPA 64-QAM extends the range of the HSDPA link adaption to the larger
transport block sizes. When channel conditions are sufficiently good, and Node B has sufficient
data within its buffer, then 64QAM is selected by the link adaptation rather than 16QAM.

QPSK

16QAM

64QAM

2 bits per symbol

4 bits per symbol

6 bits per symbol

poor to moderate
channel conditions

good
channel conditions

very good
channel conditions

Figure 4 Signal constellations with different modulation types

The require features and HW is listed in Table 20.


Requirements
UE requirements

3GPP Rel-7; Cat-13, Cat-14, Cat-17, Cat-18

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB
RNC with CDSP-DH cards
HSPA Peak Rate Upgrade in RNC196 and RNC450

Feature Requirements

HSUPA basic
HSDPA Dynamic Resource Allocation
HSDPA 16QAM
HSDPA 14 Mbps per User
HSDPA 15 codes
QoS aware HSPA scheduling
Flexible RLC

License

RNC ON/OFF license

Table 20 - Feature requirements HSDPA 64 QAM

3.4.1 HSDPA 64QAM Parameters


The RNC databuild parameters associated with the HSDPA 64QAM feature are presented in Table
21.
Parameter

New

Scope

HSDPA64QAMallowed

WCEL

MaxBitRateNRTMacdflow

RNC

Range
0
(Disabled),
(Enabled)

Default
1

128 to 42112, step 128,


65535 (Does not Limit)

Recommended

0 (Disabled)

1 (Enabled)

65535 (Does not


Limit)

65535 (Does not


Limit)

Table 21 Parameters associated with the HSDPA 64QAM feature

Copyright Nokia Siemens Networks 2008

Company confidential

Page 30 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The parameters associated with the HSDPA 64QAM feature do not offer scope for optimisation.
The HSDPA64QAMallowed parameter allows the feature to be enabled/disabled on a per cell
basis. The feature can be enabled using this parameter if the license exists within the RNC. It is an
online parameter so does not require cell locking. The MaxBitRateNRTMacdflow parameter
allows the operator to limit the maximum rate at which HSDPA data is transferred from the RNC to
the Node B. In general, it is not necessary to define a limit and the default value of 65535 should be
configured. The parameter has an RNC scope so any bit rate limit defined by this parameter will
impact all cells parented by that RNC.
Achieving high HSDPA throughputs from the 64QAM feature relies upon having areas of good
coverage. HSDPA coverage can be improved by increasing the transmit power available to HSDPA.
This can be achieved by increasing the value allocated to the PtxMaxHSDPA parameter.
Alternatively, HSDPA coverage can be improved by allocating an RF carrier which is dedicated to
HSDPA connections, i.e. reducing the transmit power used by other connection types. In each case,
the implications upon other connection types should be considered, e.g. increasing the value of
PtxMaxHSDPA can generate larger rises in the downlink interference floor and thus impact the
downlink coverage of speech connections.

3.5 DC-HSDPA 42Mbps


The release 8 version of the specifications allows 2 adjacent channels to be combined to generate
an effective HSDPA channel bandwidth of 10 MHz. This is known as Dual Cell HSDPA. RU20
implementation of Dual Cell HSDPA is based upon release 8 of 3GPP. Release 8 version of the
specifications allow Dual Cell HSDPA to be combined with 64QAM but not with MIMO (Release 9
allows combination with MIMO). This version of the specification does not allow CS Voice over
HSPA, Streming QoS, or non-HSUPA UEs on DC-HSDPA connections.
The combination of multiple RF carriers provides greater flexibility to the HSDPA Scheduler, i.e. the
scheduler can allocated resources in the frequency domain as well as in the code and time
domains. This will improve the cell and user throughputs. Figure 5 present a comparison of DCHSDPA to single cell configuration.

Figure 5 Comparison of DC-HSDPA and single cell configuration

It should be noted that from the non DC-HSDPA UE point of view the RRM functionality remains
the same.??
The require features and HW is listed in Table 22.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 31 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Requirements
UE requirements

3GPP Rel-8: Cat-21 to Cat-24

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB
RNC with CDSP-DH cards
HSPA Peak Rate Upgrade in RNC196 and RNC450

Feature Requirements

HSUPA basic
HSDPA Dynamic Resource Allocation
HSDPA 16QAM
HSDPA 14 Mbps per User
HSDPA 15 codes
Flexible RLC
Shared Scheduler for Baseband Efficiency

License

RNC capacity (cell) license

Table 22 - Feature requirements DC-HSDPA

3.5.1 DC-HSPA Parameters


The RNC databuild parameters associated with the Dual Cell HSDPA feature are presented in
Table 23.
Parameter

New

Scope

Range

Default

Recommended

DCellHSCAHORabComp

RNC

Bit0: PS I/B RAB (always 1)


Bit1: PS Streaming
Bit2: 2/3 NRT PS RAB
Bit3: PS Str + 1-3 NRT PS
RAB
Bit4: CS AMR + 1 PS I/B RAB
Bit5: CS AMR + 2/3 PS I/B
RAB
Bit6: CS AMR + PS Streaming
Bit7: CS AMR + PS Streaming
+ 1-3 NRT RAB

MaxBitRateNRTMACDFlow

RNC

128 to 42112, step 128 kbps,


65535 (not restricted)

65535

MaxIurNRTHSDSCHBitRate

IUR

128 to 42112, step 128 kbps,


0 (not restricted)

DCellHSDPAEnabled

WCEL

0 (Disabled),
1 (Enabled)

UARFCN

WCEL

0 to 16383, step 1

N/A

N/A

SectorID

WCEL

0 to 12, step 1

N/A

Tcell

WCEL

0 to 9, step 1

N/A

N/A

MaxNumbHSDPAUsersS

WCEL

1 to 511, step 1,
0 (does not limit)

MaxNumbHSDSCHMACdF
S

WCEL

1 to 1023, step 1
0 (does not limit)

DCellHSDPAFmcsId

WCEL

1 to 100, step 1

N/A

N/A

DCellHSDPACapaHO

WCEL

0 (Disabled), 1 (Enabled)

65535

Table 23 Parameters associated with the Dual Cell HSDPA feature


Copyright Nokia Siemens Networks 2008

Company confidential

Page 32 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The DCellHSDPAEnabled parameter is used to enable and disable the feature on a per cell basis.
This parameter must be set to enabled for both cells belonging to the dual cell pair. The cells
belonging to the same dual cell pair must be configured with adjacent RF carriers, the same sector
ID and the same Tcell value. These properties are defined using the UARFCN, SectorID and Tcell
parameters.
The MaxBitRateNRTMacdflow parameter allows the operator to limit the maximum rate at which
HSDPA data is transferred from the RNC to the Node B. In general, it is not necessary to define a
limit and the default value of 65535 should be configured. The parameter has an RNC scope so
any bit rate limit defined by this parameter will impact all cells parented by that RNC.
Similarly, the MaxIurNRTHSDSCHBitRate parameter allows the operator to limit the maximum
rate at which HSDPA data is transferred across the Iur. In general, it is not necessary to define a
limit and the default value of 0 should be configured. The parameter has an Iur scope so any bit
rate limit defined only impacts connections using a specific Iur.
The MaxNumbHSDPAUsersS parameter defines the maximum allowed number of HSDPA
connections per scheduler. The parameter has a scope of WCEL so an HSDPA scheduler serving
multiple cells adopts the lowest value configured across its cells. The parameter limits both single
cell and dual cell HSDPA connections. Dual cell HSDPA connections are counted only once, i.e.
they are not double counted as a result of using resources from two cells. The default and
recommended values for this parameter are 0 which means that the maximum number of HSDPA
connections is not limited by this parameter.
The MaxNumbHSDSCHMACdFS parameter defines the maximum number of HSDPA MAC-d
flows per scheduler. Similar to the MaxNumbHSDPAUsersS parameter, this parameter has a
scope of WCEL so an HSDPA scheduler serving multiple cells adopts the lowest value configured
across its cells. The parameter limits both single cell and dual cell HSDPA MAC-d flows. Dual cell
HSDPA MAC-d flows are counted only once, i.e. they are not double counted as a result of using
resources from two cells. The default and recommended values for this parameter are 0 which
means that the maximum number of HSDPA MAC-d flows is not limited by this parameter.
The DCellHSDPACapaHO parameter defines whether or not dual cell HSDPA Capability based
Handover is enabled in a cell. The dual cell Capability based Handover feature is used to direct
dual cell HSDPA capable UE to a primary serving HS-DSCH cell within a dual cell pair, i.e. away
from a cell which can act only as a secondary serving cell, and away from cells which do not
belong to a dual cell pair. The DCellHSCAHORabComp parameter defines the set of services
which are supported by the Dual Cell Capability based Handover feature.
The DCellHSDPAFmcsId parameter identifies the FMCS parameter set applied to connections
with dual cell HSDPA allocated. This parameter has a scope of WCEL so different dual cell FMCS
parameter sets can be applied to each cell belonging to a dual cell pair.

3.6 Flexible RLC (DL)


Flexible RLC (DL) feature is a part of the basic software. With this feature the RLC layer supports
Flexible RLC PDU size instead of fixed PDU size (currently either 336 or 656 bits). It reduces the
processing requirements and RLC layer overhead. Flexible RLC enables achieving of significantly
larger RLC PDU sizes (up to 1502 bytes according to 3GPP specifications) comparing to the
maximum fixed RLC PDU size of 82 bytes (656 bits).
The larger RLC PDU size enables to achieve higher HSPA+ bit rate and reduces RLC overhead
from about 7% to less than 5%. The reduced overhead is a benefit for all bit rates.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 33 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The require features and HW is listed in Table 24.


Requirements
UE requirements

Mandatory in 3GPP Rel-7 UE

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB

Feature Requirements

HSUPA basic

License

Basic in RU20 SW

HSDPA Dynamic Resource Allocation

Table 24 - Feature requirements Flexible RLC /DL)

3.6.1 Downlink Flexible RLC Parameters


The RNC databuild parameters associated with the Downlink Flexible RLC feature are presented in
Table 25.
Parameter

New

Scope

Range

Default

Recommended

FRLCEnabled

RNC

0 (Disabled),
1 (Enabled)

0
(Disabled)

1 (Enabled)

FRLCPDUMaxSize

RNC

320 to 12000, step 1 bit

11200 bit

11200 bit

AMRLCmaximumBufferUE300

RNC

200 to 500, step 5 kB

300 kByte

300 kByte

AMRLCmaximumBufferUE400

RNC

200 to 600, step 5 kB

350 kByte

350 kByte

AMRLCmaximumBufferUE500

RNC

200 to 700, step 5 kB

450 kByte

450 kByte

AMRLCmaximumBufferUE750

RNC

200 to 900, step 5 kB

550 kByte

550 kByte

AMRLCmaximumBufferUE1k

RNC

200 to 1500, step 5 kB

550 kByte

550 kByte

AMRLCmaximumBufferUE2k

RNC

200 to 2500, step 5 kB

550 kByte

550 kByte

AMRLCRelatTXWindowRate1

RNC

8 to 28000, step 8 kbps

8 kbps

8 kbps

AMRLCRelatTXWindowRate2

RNC

8 to 28000, step 8 kbps

32 kbps

32 kbps

AMRLCRelatTXWindowRate3

RNC

8 to 28000, step 8 kbps

64 kbps

64 kbps

AMRLCRelatTXWindowRate4

RNC

8 to 28000, step 8 kbps

384 kbps

384 kbps

AMRLCRelatTXWindowRate5

RNC

8 to 28000, step 8 kbps

1376 kbps

1376 kbps

AMRLCRelatTXWindowRate6

RNC

8 to 28000, step 8 kbps

1600 kbps

1600 kbps

AMRLCRelatTXWindowRate7

RNC

8 to 28000, step 8 kbps

3840 kbps

3840 kbps

AMRLCRelatTXWindowRate8

RNC

8 to 28000, step 8 kbps

9600 kbps

9600 kbps

HSDSCHStrPSTriggers

RNC

0 to 65535, step 1

65041

65041

AMRLCOnHSDSCHOfNRTPSTrigger
s

RNC

0 to 131071, step 1

122385

122385

AMRLCmaximumBufferUE50

RNC

50 to 100, step 5 kB

70 kB

70 kB

AMRLCmaximumBufferUE100

RNC

100 to 200, step 5 kB

125 kB

125 kB

AMRLCmaximumBufferUE150

RNC

150 to 300, step 5 kB

175 kB

175 kB

AMRLCmaximumBufferUE200

RNC

200 to 400, step 5 kB

250 kB

250 kB

Table 25 Parameters associated with the Downlink Flexible RLC feature

The FRLCEnabled parameter allows the feature to be enabled/disabled on a per RNC basis.
Downlink Flexible RLC is a basic software feature so a license is not necessary. The
Copyright Nokia Siemens Networks 2008

Company confidential

Page 34 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

FRLCEnabled parameter can be modified online without any cell locking. The FRLCPDUMaxSize
parameter defines the maximum size of the RLC PDU payload. This parameter is necessary
because the maximum size of the Frame Protocol data frame used to transfer the RLC PDU across
the Iub is limited. 3GPP allows a maximum RLC PDU size of 1504 bytes but Flexi release 2
hardware supports a maximum Frame Protocol data frame size of 1428 bytes. The default value of
FRLCPDUMaxSize is 11200 bits (1400 bytes). This default allows 28 bytes for the RLC and Frame
Protocol data frame headers. The default value of this parameter should not be increased
otherwise there is a danger that the Frame Protocol data frame size will exceed the capability of
the Flexi hardware.
The remaining parameters associated with the Downlink Flexible RLC feature are linked to the
configuration of Acknowledged Mode RLC. In general, it is not necessary to adjust these
parameters unless recommended by a Technical Note or suggested as part of an investigative
performance improvement trial.
The AMRLCmaximumBufferUExx parameters define the RLC buffer size assumed by the RNC
depending upon the RLC buffer size reported by the UE capability information. The RNC can
assume a smaller RLC buffer size when the UE reports that it has a large RLC buffer, i.e. it is not
necessary to use the complete RLC buffer size reported by the UE.
The AMRLCRelatTXWindowRatex parameters exist in RU10 but have been modified for RU20 to
increase their range to 28000 kbps. However, the default values of these parameters have not
changed. The HSDSCHStrPSTriggers and AMRLCOnHSDSCHOfNRTPSTriggers parameters
also exists in RU10 but have been modified for RU20 to support a change to the Acknowledged
Mode RLC polling mechanisms. A new bit has been introduced within the bitmap belonging to each
parameter to provide support for the new POLL SUFI which is only applicable to Flexible RLC. This
POLL SUFI allows the sender to request a status report without having to set the POLL bit within
the header of a data frame. A further new bit has been introduced to provide support for the
special interpretation of the HE field within the RLC header. The special interpretation is
configured by the RRC layer and is used to indicate that the last byte of data within the RLC PDU is
the end of a higher layer packet. This helps to reduce the requirement for length indicators. The
HSDSCHStrPSTriggers and AMRLCOnHSDSCHOfNRTPSTriggers parameters have also been
modified to allow the Last transmission PDU poll and Last retransmission PDU poll mechanisms
to be configurable rather than always enabled.
RU20 introduces only minor changes to the AMRLCmaximumBufferUExx parameters. The 50,
100 and 150 versions only have changes to their description while the 200 version has its range
increased to 400 kbytes, while the default value remains unchanged.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 35 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

4 HSUPA features
4.1 HSUPA bit rates
The maximum bit rates supported by different HSUPA UE Categories are listed in Table 26. It lists
also the used code number and spreading factors.
UE Category
Used codes
Air interface bit rate (Mbps)
Max. transport block size (bits)
TTI (ms)
Max. transport channel (E-DCH)
bit rate (Mbps)
RLC PDU (bits)
MAC-e/es Header Size (bits)
RLC blocks/TTI
RLC bit rate (Mbps)
RLC header (bits)
RLC payload (Mbps)

Cat - 1
SF4
0.96
7110
10
0.71

Cat - 2
2xSF4
1.92
2798
2
1.40

Cat - 3
2xSF4
1.92
14484
10
1.45

Cat - 4
2xSF2
3.84
5772
2
2.89

Cat - 5
2xSF2
3.84
20000
10
2.00

Cat - 6
2xSF2+2xSF4
5.76
11484
2
5.74

Cat - 7
2xSF2+2xSF4
11.52
22996
2
11.50

336
18
21
0.706
16
0.672

336
18
8
1.34
16
1.28

336
18
43
1.44
16
1.38

336
18
17
2.86
16
2.72

336
18
59
1.98
16
1.89

336
18
34
5.71
16
5.44

336
18
68
11.42
16
10.9

Table 26 - HSUPA UE Categories with maximum supported bit rates

The HSUPA bit rates supported by different RAN features are listed in Table 27.
Features

Basic

2 ms TTI

Cat - 3
2xSF4
1.92
14484
10
1.45

HSUPA
2.0 Mbps
Cat - 5
2xSF2
3.84
19950
10
2.00

Cat - 4
2xSF2
3.84
5772
2
2.89

HSUPA
5.8 Mbps
Cat - 6
2xSF2+2xSF4
5.76
11484
2
5.74

Min. UE HSUPA Category


Used codes
Air interface bit rate (Mbps)
Max. transport block size (bits)
Minimum TTI (ms)
Max. transport channel (E-DCH)
bit rate (Mbps)
RLC PDU (bits)
MAC-e/es Header Size (bits)
RLC blocks/TTI
RLC bit rate (Mbps)
RLC header (bits)
RLC payload (Mbps)
RLC payload (Mbps) - 10%
HARQ retrans.
TCP/IP payload (Mbps)

336
18
43
1.44
16
1.38
1.24

336
18
59
1.98
16
1.89
1.70

336
18
17
2.86
16
2.72
2.45

336
18
34
5.71
16
5.44
4.90

1.21

1.65

2.38

4.77

Table 27 - HSUPA bit rates with different RAN features

4.2 HSUPA 5.8 Mbps


This feature adds the support for HSUPA Cat-6 and Cat-7 UEs increasing the maximum HSUPA bit
rate to 5.8 Mbps. This is the maximum theoretical bit rate when QPSK modulation is used and it
can be achieved by using 2xSF2 + 2xSF4 codes.
The channelization code usage with HSUPA 5.8 Mbps is presented in Figure 6. It shows that the bit
rate is achieved by using SF2 and SF4 codes in both I and Q branches (total 2xSF2+2xSF4) of the
QPSK modulation.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 36 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

E-DPDCH
(on I- and Q-branches
2SF2 + 2SF4 max)

Cch,2,1

Date: 30.07.2010
Version 1.1

Cch,4,3

Cch,4,2

Cch,4,1
Cch,2,0
Cch,4,0
SF2

SF4

SF8

Figure 6 HSUPA Code usage for HSUPA 5.8 Mbps bit rate

The HSUPA bit rates with different features are presented in Table 27.
Table 28 lists the requirements for this feature.
Requirements
UE requirements

HSUPA Cat-6 or Cat-7

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB
RNC with CDSP-DH cards

Feature Requirements

HSUPA basic
HSUPA 2ms TTI

License

RNC ON/OFF license

Table 28 - Feature requirements HSUPA 5.8 Mbps

4.2.1 HSUPA 5.8 Mbps Parameters


The RNC databuild parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI
features are presented in Table 31.
Parameter

New

Scope

Range

Default

Recommended
2048 kbps

ThresholdMaxEDPDCHSR3840kbps

RNC

0 to 16000, step 64 kbps

2048 kbps

HSUPA2MSTTIEnabled

WCEL

0 (Disabled), 1 (Enabled)

0 (Disabled)

MaxTotalUplinkSymbolRate

WCEL

0 (960 kbps, SF4),


1 (1920 kbps, 2*SF4),
2 (3840 kbps, 2*SF2),
3 (5760 kbps, 2*SF2 +
2*SF4)

1 (Enabled)

Table 29 Parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI features

Copyright Nokia Siemens Networks 2008

Company confidential

Page 37 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The MaxTotalUplinkSymbolRate parameter enables/disables the feature on a per cell basis. This
parameter must be configured with a value of 3 (5760 kbps, 2*SF2 + 2*SF4) to enable the feature.
Otherwise, HSUPA connections will not be able to use the 2*SF2 + 2*SF4 configuration. In
addition, the 2 ms TTI must be enabled using the HSUPA2MSTTIEnabled parameter. This is
necessary because the 5.8 kbps bit rate is not supported by the 10 ms TTI.
The
ThresholdMaxEDPDCHSR3840kbps
parameter
compliments
the
existing
ThresholdMaxEDPDCHSR960kbps and ThresholdMaxEDPDCHSR1920kbps parameters. This
new parameter introduces an additional threshold to determine when the 2*SF2 + 2*SF4
configuration can be allocated as a maximum configuration. If the HLR QoS profile maximum uplink
bit rate multiplied by the value of the FactorEDCHMaxBitRate parameter exceeds the value of the
ThresholdMaxEDPDCHSR3840kbps parameter then the 2*SF2 + 2*SF4 configuration is
allocated as a maximum allowed configuration. Otherwise the product of the HLR QoS profile
maximum uplink bit rate and the value of the FactorEDCHMaxBitRate parameter is compared
against the ThresholdMaxEDPDCHSR960kbps and ThresholdMaxEDPDCHSR1920kbps
parameters.

4.3 HSUPA 2ms TTI


This feature enables HSUPA 2ms TTI (Transmission Time Interval). It also maps the SRBs
(Signalling Radio Bearer) on HSUPA, if 2ms TTI is assigned to the UE. Mapping of SRBs on UL EDCH enables the use of 2xSF2 + 2xSF4 code in UE to support uplink HSUPA bit rate up to
5.8Mbps. 3GPP Release 6 introduces both 10 ms and 2 ms TTI for HSUPA. NSN RAS06 and
RU10 support only the 10 ms TTI, which is optimum for improved cell edge performance. 2 ms TTI
introduced in RU20 reduces latency (original transmission and re-transmissions) and supports
increased peak throughputs of up to 5.8 Mbps.
Table 30 lists the requirements for this feature.
Requirements
UE requirements

HSUPA Cat-6 or Cat-7

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB
RNC with CDSP-DH cards

Feature Requirements

HSUPA basic
HSUPA 2ms TTI

License

RNC ON/OFF license

Table 30 - Feature requirements HSUPA 2 ms TTI

4.3.1 HSUPA 2 ms TTI Parameters


The RNC databuild parameters associated with the HSUPA 2 ms TTI features are presented in
Table 31.
Parameter

New

Scope

EDCHMaxHarqReTxSRB2MS

RNC

CPICHRSCPThreEDCH2MS

RNC

50 to 160, step 1 dB

CPICHECNOThreEDCH2MS

RNC

-24 to 0 dB, step 1 dB

EDCHMuxSRBTTI2MS

Copyright Nokia Siemens Networks 2008

RNC

Range
0 to 5, step 1

Bit 0: CS Voice
Bit 1: PS streaming

Company confidential

Default
4

Recommended
4

136 dB

136 dB

-6 dB

-6 dB

1
1

1
1
Page 38 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Bit 2: PS inter. THP 1


Bit 3: PS inter. THP 2
Bit 4: PS inter. THP 3
Bit 5: PS Background

0
0
0
0

0
0
0
0

120 ms

120 ms

0.1

0.1

MaxReWaitTime2msTTI

RNC

16 to 120 ms, step 2 ms

ProbabilityFactorMax2msTTI

WBTS

0 to 1, step 0.0001

DelayThresholdMax2msTTI

WBTS

0 to 320 ms, step 0.01 ms

100 ms

100 ms

DelayThresholdMid2msTTI

WBTS

0 to 320 ms, step 0.01 ms

70 ms

70 ms

DelayThresholdMin2msTTI

WBTS

0 to 320 ms, step 0.01 ms

50 ms

50 ms

HSUPA2MSTTIEnabled

WCEL

0 (Disabled), 1 (Enabled)

0 (Disabled)

1 (Enabled)

Table 31 Parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI features

The HSUPA2MSTTIEnabled parameter enables/disables the HSUPA 2 ms TTI feature on a per


cell basis. The default value is disabled so the parameter requires modification to enable the
feature. This feature is required to allow the SRB to be transferred using HSUPA.
The DelayThresholdMin2msTTI, DelayThresholdMid2msTTI, DelayThresholdMax2msTTI and
ProbabilityFactorMax2msTTI parameters are associated with HSUPA congestion control. The
represent the 2 ms TTI equivalent of the existing DelayThresholdMin, DelayThresholdMid,
DelayThresholdMax, ProbabilityFactorMax parameters used for the 10 ms TTI.
The MaxReWaitTime2msTTI parameter defines the maximum allowed PDU re-ordering wait time
at the MAC-es layer within the RNC. PDU are forwarded to the higher layers if this timer expires
while waiting for a missing PDU. This parameter represents the 2 ms TTI equivalent of the existing
MaxReWaitTime parameter used for the 10 ms TTI.
The EDCHMaxHarqReTxSRB2MS, CPICHRSCPThreEDCH2MS, CPICHECNOThreEDCH2MS
and EDCHMuxSRBTTI2MS parameters are the same as those described within the Fractional
DPCH parameter set section. They are repeated within this section because they are relevant to
the 2 ms TTI.
SPI value for the MAC-d flow of SRBs on E-DCH shall be always read from the
PriForSRBsOnHSPA child parameter of the QoSPriorityMapping RNP parameter instead of QoS
Aware HSPA Scheduling feature is activated or not.??

Copyright Nokia Siemens Networks 2008

Company confidential

Page 39 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

5 HSPA features
5.1 Fractional DPCH
With Fractional DPCH feature one DL channellisation code is shared between up to 10 users for
carrying UL power control commands from Node-B to UE. This feature includes also the mapping
of signalling radio bearers (SRBs) to HSPA (see Figure 7). The main benefit of Fractional DPCH
comes as saving of the DL code capacity. Usage of HSPA channels for SRB will also decrease the
signalling times and make the call setups faster.

Fractional DPCH
Dedicated channels

DPCCH
HS-DPCCH
1,2,4 x E-DPDCH
E-DPCCH

SRB + Data

E-DCH RGCH
E-DCH HICH
Common channels

F-DPCH (PC)
1-15 x HS-PDSCH
1-3 x HS-SCCH

SRB + Data

E-DCH AGCH
Figure 7 HSPA connection channel usage with fractional DPCH

Table 28 lists the requirements for this feature.


Requirements
UE requirements

Rel-7 UE with
support

Network Hardware Requirements

Flexi Rel. 2 HW

F-DPCH

Ultrasite with EUBB


Feature Requirements

HSUPA basic
HSDPA

License

RNC ON/OFF license


Included

Table 32 Feature requirements Fractional DPCH

5.1.1 Fractional DPCH Parameters


Copyright Nokia Siemens Networks 2008

Company confidential

Page 40 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The RNC databuild parameters associated with the Fractional DPCH feature are presented in
Table 33. This feature also introduces support for transferring the SRB on HSPA so some of the
parameters within Table 33 are linked to the HSPA SRB.
Parameter

New

Scope

Range

Default

Recommended

FDPCHAndSRBOnHSPATC

RNC

Bit 0: Background
Bit 1: Interactive THP=3
Bit 2: Interactive THP=2
Bit 3: Interactive THP=1
Bit 4: PS Streaming
Bit 5: PS Convers.
Bit 6: CS Convers.

1
1
1
1
1
1

1
1
1
1
1
1

FDPCHAllocMinInterval

RNC

0 to 10 s, step 1 s

AMRLCRespTimeSRBHSPA

RNC

AMRLCSRBHSPAPeriodMax

RNC

AMRLCSRBHSPATriggers

RNC

2047

AMRLCSRBHSPAPeriodMin

RNC

10 to 1000, step 10 ms

AMRLCSRBHSPAPollPDU

RNC

1 to 100 %, step 1 %

AMRLCSRBHSPAPollSDU

RNC

1 to 64, step 1

AMRLCSRBHSPAPollWindow

RNC

50 to 99 %, step 1 %

AMRLCSRBHSPAMaxDAT

RNC

1 to 60, step 1

HSDPASRBWindow

RNC

0 to 6, step 0.5 dB

CPICHRSCPThreSRBHSDPA

RNC

-115 to -25, step 1 dBm

CPICHECNOSRBHSPA

RNC

-24 to 0, step 1 dB

PriForSRBsOnHSPA

RNC

0 to 15, step 1

ATOSRBsOnHSPA

RNC

10 to 1000, step 10 ms

EDCHMaxHarqReTxSRB

RNC

EDCHMaxHarqReTxSRB2MS

EDCHMuxSRBTTI10MS

0 to 1500, step 10 ms

0
3s
100 ms

1 to 600, step 1 %

3s
100 ms

116 %
1988

116 %
1988

40 ms
23 %

40 ms
23 %

70 %

70 %

30

30

1 dB

1 dB

-103 dBm

-103 dBm

-6 dB

-6 dB

15

15

300 ms

300 ms

0 to 5, step 1

RNC

0 to 5, step 1

RNC

Bit 0: CS Voice
Bit 1: PS streaming
Bit 2: PS inter. THP 1
Bit 3: PS inter. THP 2
Bit 4: PS inter. THP 3
Bit 5: PS Background

1
1
1
1
1
1

1
1
1
1
1
1

EDCHMuxSRBTTI2MS

RNC

Bit 0: CS Voice
Bit 1: PS streaming
Bit 2: PS inter. THP 1
Bit 3: PS inter. THP 2
Bit 4: PS inter. THP 3
Bit 5: PS Background

1
1
0
0
0
0

1
1
0
0
0
0

AfSRBOnHSDPA

RNC

0 to 1, step 0.01

FDPCHEnabled

WCEL

Copyright Nokia Siemens Networks 2008

0 (Disabled),
1 (Enabled)

Company confidential

Page 41 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

FDPCHSetup

WCEL

0 (Immediate)
1 (after RRC setup)
2 (with UP allocation)

FDPCHCodeChangeEnabled

WCEL

0 to 8, step 1

PtxFDPCHMax

WCEL

-5 to 30, step 0.1 dB

9 dB

9 dB

PtxFDPCHMin

WCEL

-5 to 30, step 0.1 dB

20 dB

20 dB

PtxOffsetFDPCHSHO

WCEL

0 to 10, step 0.5 dB

TPCCommandERTarget

WCEL

0.01 to 0.1, step 0.01

CIRForFDPCH

WCEL

-40 to 0, step 0.5 dB

1 dB
0.04
-22 dB

1 dB
0.04
-22 dB

Table 33 Parameters associated with the Fractional DPCH feature

The FDPCHEnabled parameter allows the F-DPCH and HSPA SRB to be enabled/disabled on a
per cell basis. This parameter can be changed online without having to lock the cell. The
FDPCHAndSRBOnHSPATC parameter defines the set of traffic classes which are permitted to
use the F-DPCH and to map the SRB onto HSPA. The default value allows all traffic classes
except CS conversational to use the F-DPCH and HSPA SRB.
The FDPCHSetup parameter defines the allocation procedure for the F-DPCH. A value of 0
instructs the RNC to allocate the F-DPCH to release 7 UE during RRC setup. A value of 1 instructs
the RNC to allocate the F-DPCH to release 7 UE immediately after receiving the RRC Connection
Setup Complete message. A value of 2 instructs the RNC to allocate the F-DPCH at the same time
as configuring the user plane radio bearers.
The FDPCHAllocMinInterval parameter defines the minimum interval between two consecutive FDPCH allocations for a specific UE. A timer is started whenever a F-DPCH is switched to a DPCH.
A subsequent F-DPCH cannot then be allocated to that UE until the timer expires.
The PtxFDPCHMax parameter is used to calculate both the initial and maximum F-DPCH transmit
powers, i.e. the initial and maximum transmit powers are given by PtxPrimaryCPICH
PtxFDPCHMax. If the UE is in E-DCH soft handover, the PtxOffsetFDPCHSHO parameter is
added to the result to increase both the initial and maximum transmit powers. The PtxFDPCHMin
parameter defines the minimum transmit power of the F-DPCH, i.e. the minimum transmit power is
given by PtxPrimaryCPICH PtxFDPCHMin. If the UE is in E-DCH soft handover, the
PtxOffsetFDPCHSHO parameter is added to the result to increase the minimum transmit
power. However, RU20 does not apply inner loop power control to the F-DPCH and the maximum
transmit power is always used.
The TPCCommandERTarget parameter defines the TPC command error rate target signalled to
the UE. This target replaces the DCH BLER target which is used for outer loop power control when
a DPDCH is present. Its necessary to replace the DCH BLER target when using the F-DPCH
because a downlink DCH is no longer present. The UE has to estimate the actual TPC error rate by
measuring the SIR from the TPC commands.
The FDPCHCodeChangeEnabled parameter specifies whether or not a channelisation code
change can be applied to the F-DPCH. Code changes are used for code tree optimisation, i.e. to
avoid fragmentation within the code tree. A value of 0 means that code changes are not permitted.
Values greater than 0 define the maximum number of allocated F-DPCH slot formats when
triggering a code change. Code changes are not permitted when the number of allocated F-DPCH
slot formats is greater than the value of the FDPCHCodeChangeEnabled parameter.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 42 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The CIRForFDPCH parameter defines the Carrier to Interference Ratio (CIR) for the F-DPCH. The
value of the parameter is used during the estimation of power required by a new HSDPA streaming
user. This parameter is not relevant if streaming QoS for HSDPA is disabled.
The CPICHECNOSRBHSPA parameter defines the minimum CPICH Ec/Io requirement for an
HSPA SRB to be allocated. The CPICHRSCPThreSRBHSDPA and HSDPASRBWindow
parameters are also used during SRB channel type selection. There must be at least one cell in the
active set which has a CPICH RSCP which exceeds the value of the
CPICHRSCPThreSRBHSDPA parameter. If HSDPA is already allocated to the UE, the serving cell
must have a CPICH RSCP which exceeds the value of this parameter. The HSDPASRBWindow
defines the maximum allowed difference in CPICH Ec/Io between the best cell in the active set and
the cell upon which the HSPA SRB is allocated. These parameters are also used during the
serving cell change and active set update procedures, i.e. cells supporting the HSPA SRB must
have sufficiently good CPICH RSCP and Ec/Io.
The EDCHMaxHarqReTxSRB parameter defines the maximum number of HARQ re-transmissions
for the SRB E-DCH MAC-d flow when the TTI is 10 ms. The EDCHMaxHarqReTxSRB2MS
parameter defines the maximum number of HARQ re-transmissions for the SRB E-DCH MAC-d
flow when the TTI is 2 ms. In general, an increased number of re-transmissions is allowed for the 2
ms TTI because the delay associated with each re-transmission is significantly less, i.e. 16 ms
compared to 40 ms.
The EDCHMuxSRBTTI10MS parameter defines the set of services which are permitted to be
multiplexed within the same 10 ms TTI as the SRB, i.e. included within the same MAC-e PDU. The
default value allows all service types to be multiplexed within the same MAC-e PDU. The
corresponding parameter for the 2 ms TTI is EDCHMuxSRBTTI2MS. The default value for this
parameter limits the services which can be multiplexed within the same MAC-e PDU as the SRB to
the CS voice and PS streaming services, i.e. high priority services. It is assumed that other
services are able to wait until the following TTI.
The ATOSRBsOnHSPA parameter defines the activation time offset which is applied when the
SRB are on HSPA. It is used to define the CFN during which a reconfiguration is applied, i.e. it
works in the same way as the activation time offset for when the SRB are on DCH.
The afSRBOnHSDPA parameter forms part of the ActivityFactorForHSPA parameter structure.
This parameter structure is used when the Transport Bearer Tuning feature is enabled. It is used to
determine the size of the Iub transport CAC reservation by scaling the average transport bearer
throughput.
The PriForSRBsOnHSPA parameter forms part of the QoSPriorityMapping parameter structure.
It defines the Scheduling Priority Indicator (SPI) for HSPA SRB which is used for prioritisation on
both the Iub and air-interface. SRB are allocated the highest priority of 15 by default.
The AM RLC parameters form part of the AMRLCSRBHSPA parameter structure. In general, it is
not necessary to adjust these parameters unless recommended by a Technical Note or suggested
as part of an investigative performance improvement trial.

5.2 Continuous Packet Connectivity


Continuous Packet Connectivity feature implements a set of features specified in 3GPP release 7
specifications. The target of this feature set is to decrease the unnecessary activity of the UE on
HSPA in CELL_DCH and thus enable the UE to stay in that state for longer times with even
decreased power consumption compared to the default functionality. It also increases the

Copyright Nokia Siemens Networks 2008

Company confidential

Page 43 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

maximum number of active HSPA users in cell as it is always used together with Fractional DPCH
feature. Continuous Packet Connectivity includes the following subfeatures:

DPCCH Gating (UL DTX)


CQI Reporting reduction
Discontinuous UL Reception (MAC DTX)
Discontinuous DL Reception (DL DRX)

Figure 8 presents the main functionality of the DPCCH gating. It shows that the DPCCH activity
can be reduced substantially by utilising a discontinuous DPCCH transmission, especially with low
activity HSUPA traffic. This reduces the UE activity and power consumption.

Figure 8 DPCCH gating

Discontinuous DL reception enables the UE to stop receiving the HS-SCCH, E-AGCH and ERGCH when it is not needed to do so. Also this reduces the UE activity and power consumption.
Table 34 lists the requirements for this feature.
Requirements
UE requirements

Rel-7 UE with CPC support

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB

Feature Requirements

Basic HSUPA
HSDPA
Fractional DPCH

License

RNC ON/OFF license

Table 34 - Feature requirements Continuous Packet Connectivity

5.3 Continuous Packet Connectivity Parameters


The RNC databuild parameters associated with the Continuous Packet Connectivity (CPC) feature
are presented in Table 35.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 44 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
Parameter
CPCEnabled

New

Scope

RNC

Range
0 (Disabled), 1 (Enabled)

Date: 30.07.2010
Version 1.1

Default
0
(Disabled)

Recommended
1 (Enabled)

Table 35 Parameters associated with enabling the Continuous Packet Connectivity feature

The CPCEnabled parameter is used to enable and disable the feature on a per RNC basis. This
parameter can be reconfigured online without the requirement for object locking.
The CPC parameters specifically associated with CS Voice over HSPA connections when using a
2 ms TTI for HSUPA are presented in Table 36.
Parameter

New

Scope

Range

Default

V2msCPCOptObjective

RNC

0 (RTT), 1 (Battery)

1 (Battery)

1 (Battery)

V2msInacThrUEDTXCycl2

RNC

0 (1), 1 (2), 2 (4), 3 (8), 4 (16), 5


(32), 6 (64), 7 (128), 8 (256)

5 (32)

5 (32)

V2msUEDTXLongPreamble

RNC

0 (2), 1 (4), 2 (15)

1 (4)

1 (4)

V2msUEDPCCHburst1

RNC

0 (1), 1 (2), 2 (5)

0 (1)

0 (1)

V2msUEDPCCHburst2

RNC

0 (1), 1 (2), 2 (5)

0 (1)

0 (1)

V2msUEDTXCycle1

RNC

0 (1), 1 (4), 2 (5), 3 (8), 4 (10), 5


(16), 6 (20)

3 (8)

3 (8)

V2msUEDTXCycle2

RNC

0 (4), 1 (5), 2 (8), 3 (10), 4 (16), 5


(20), 6 (32), 7 (40), 8 (64), 9 (80),
10 (128), 11 (160)

4 (16)

4 (16)

V2msUEDRXCycle

RNC

0 (0.5), 1 (1), 2 (2), 3 (3), 4 (4)

1 (1)

1 (1)

V2msInacThrUEDRXCycle

RNC

0 (0), 1 (1), 2 (2), 3 (4), 4 (8), 5


(16), 6 (32), 7 (64), 8 (128), 9
(256), 10 (512)

6 (32)

V2msMACInacThr

RNC

0 (Infinity), 1 (1), 2 (2), 3 (4), 4


(8), 5 (16), 6 (32), 7 (64), 8 (128),
9 (256), 10 (512)

0 (Infinity)

0 (Infinity)

V2msMACDTXCycle

RNC

0 (1), 1 (4), 2 (5), 3 (8), 4 (10), 5


(16), 6 (20)

3 (8)

3 (8)

V2msCQIDTXTimer

RNC

0 (0), 1 (1), 2 (2), 3 (4), 4 (8), 5


(16), 6 (32), 7 (64), 8 (128), 9
(256), 10 (512), 11 (Infinity)

V2msCQIFeedbackCPC

RNC

0 (0), 1 (2), 2 (4), 3 (8), 4 (10), 5


(20), 6 (40), 7 (80), 8 (160)

6 (32)

4 (10)

Recommended

6 (32)

6 (32)

4 (10)

Table 36 CPC parameters associated with the CS Voice over HSPA service (2ms HSUPA TTI)

The V2msCPCOptObjective parameter is used to indicate whether or not UE battery power


optimisation should be applied. Battery power optimisation applies shorter inactivity timers prior to
moving a connection to CELL_FACH or RRC Idle mode.
The
V2msInacThrUEDTXCycl2,
V2msUEDTXLongPreamble,
V2msUEDPCCHburst1,
V2msUEDPCCHburst2, V2msUEDTXCycle1 and V2msUEDTXCycle2 parameters are used to
configure the timing for uplink DTX (uplink gating). The V2msInacThrUEDTXCycl2 parameter
defines the number of TTI of E-DCH inactivity after which the UE switches from the cycle 1 DTX
burst pattern to the cycle 2 DTX burst pattern. The V2msUEDTXLongPreamble parameter defines
the number of slots used as a DPCCH preamble for the cycle 2 DTX burst pattern. The DPCCH
preamble always has a duration of 2 slots for the cycle 1 DTX burst pattern. The
Copyright Nokia Siemens Networks 2008

Company confidential

Page 45 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

V2msUEDPCCHburst1 and V2msUEDPCCHburst2 parameters define the DPCCH burst


durations in terms of 2 ms subframes for the cycle 1 and cycle 2 DTX burst patterns respectively.
The V2msUEDTXCycle1 and V2msUEDTXCycle2 parameters defines the period between
consecutive DPCCH bursts in terms of 2 ms subframes for the cycle 1 and cycle 2 DTX burst
patterns respectively.
The V2msUEDRXCycle and V2msInacThrUEDRXCycle parameters are used to configure the
timing for downlink DRX. The V2msUEDRXCycle parameter defines the HS-SCCH reception
pattern in terms of 2 ms subframes. This parameter should be an integer multiple or divisor of the
V2msUEDTXCycle1 parameter. If the configured parameter value is not an integer multiple or
divisor then its value is decreased until a valid value is reached. The V2msInacThrUEDRXCycle
parameter defines the number of 2 ms subframes after an HS-SCCH reception, or after the first slot
of an HS-PDSCH reception, during which the UE is required to continuously monitor the HS-SCCH.
The V2msMACInacThr and V2msMACDTXCycle parameters are used to configure the timing for
uplink DRX. The V2msMACInacThr parameter defines the E-DCH period of inactivity in terms of
TTI, after which the UE is limited to starting new E-DCH transmissions only at specific times, i.e. at
the times when the Node B will be receiving. The V2msMACDTXCycle parameter defines the
uplink DRX cycle length in terms of 2 ms subframes.
The V2msCQIDTXTimer and V2msCQIFeedbackCPC parameters are used to configure the
timing for CQI reporting reduction. The V2msCQIDTXTimer parameter defines the number of 2 ms
subframes after an HS-DSCH reception during which the CQI reports have greater priority than the
DTX pattern. The V2msCQIFeedbackCPC parameter defines the CQI feedback cycle when the
CQI reporting interval is not reduced due to DTX. Its not recommended to use feedback cycles
greater than 10 ms.
Table 37 presents similar sets of parameters as Table 36 but for other connection types. The other
connections types are PS streaming over HSPA and NRT data over HSPA. In each case,
parameters are defined separately for the 2 ms and 10 ms HSUPA TTI.

Connection Type

Parameter Set

CS Voice over HSPA


(10 ms HSUPA TTI)

V10msCPCOptObjective,
V10msCQIDTXTimer,
V10msCQIFeedbackCPC,
V10msInacThrUEDRXCycle,
V10msInacThrUEDTXCycl2,
V10msMACDTXCycle,
V10msMACInacThr,
V10msUEDPCCHburst1,
V10msUEDPCCHburst2,
V10msUEDRXCycle,
V10msUEDTXCycle1,
V10msUEDTXCycle2, V10msUEDTXLongPreamble

PS Streaming over HSPA


(2 ms HSUPA TTI)

S2msCPCOptObjective,
S2msCQIDTXTimer,
S2msCQIFeedbackCPC,
S2msInacThrUEDRXCycle, S2msInacThrUEDTXCycl2, S2msMACDTXCycle,
S2msMACInacThr,
S2msUEDPCCHburst1,
S2msUEDPCCHburst2,
S2msUEDRXCycle,
S2msUEDTXCycle1,
S2msUEDTXCycle2,
S2msUEDTXLongPreamble

PS Streaming over HSPA


(10 ms HSUPA TT

S10msCPCOptObjective,
S10msCQIDTXTimer,
S10msCQIFeedbackCPC,
S10msInacThrUEDRXCycle,
S10msInacThrUEDTXCycl2,
S10msMACDTXCycle,
S10msMACInacThr,
S10msUEDPCCHburst1,
S10msUEDPCCHburst2,
S10msUEDRXCycle,
S10msUEDTXCycle1,
S10msUEDTXCycle2, S10msUEDTXLongPreamble

NRT Data over HSPA


(2 ms HSUPA TTI)

N2msCPCOptObjective,
N2msCQIDTXTimer,
N2msCQIFeedbackCPC,
N2msInacThrUEDRXCycle, N2msInacThrUEDTXCycl2, N2msMACDTXCycle,
N2msMACInacThr,
N2msUEDPCCHburst1,
N2msUEDPCCHburst2,
N2msUEDRXCycle,
N2msUEDTXCycle1,
N2msUEDTXCycle2,
N2msUEDTXLongPreamble

NRT Data over HSPA


(10 ms HSUPA TTI)

N10msCPCOptObjective,
N10msCQIDTXTimer,
N10msCQIFeedbackCPC,
N10msInacThrUEDRXCycle,
N10msInacThrUEDTXCycl2,
N10msMACDTXCycle,
N10msMACInacThr,
N10msUEDPCCHburst1,

Copyright Nokia Siemens Networks 2008

Company confidential

Page 46 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

N10msUEDPCCHburst2,
N10msUEDRXCycle,
N10msUEDTXCycle2, N10msUEDTXLongPreamble

N10msUEDTXCycle1,

Table 37 CPC parameters associated with other specific connection types

Table 38 presents the set of parameters associated with UE battery power optimization. The
InactCPCBatOptT and InactCPCNoBatOptT parameters are applicable when CPC is enabled
while the InactNonCPCBatOptT and InactNonCPCNoBatOptT parameters are applicable when
CPC is disabled.
Parameter

New

Scope

Range

Default

Recommended

InactCPCBatOptT

RNC

0 (0 s) to 96 (infinitely)

36 (1 min 30 s)

36 (1 min 30 s)

InactCPCNoBatOptT

RNC

0 (0 s) to 96 (infinitely)

48 (3 min)

48 (3 min)

InactNonCPCBatOptT

RNC

0 (0 s) to 96 (infinitely)

0 (0 s)

0 (0 s)

InactNonCPCNoBatOptT

RNC

0 (0 s) to 96 (infinitely)

0 (0 s)

0 (0 s)

Table 38 Extended inactivity timers for UE battery power optimisation

The default values of the parameters mean that extended inactivity timers are not applied when
CPC is disabled, i.e. UE are not maintained in CELL_DCH for longer than normal. When CPC is
enabled, the extended inactivity timer defined by the InactCPCBatOptT parameter is applied if the
UE signals to the RNC that it benefits from UE battery power optimisation. The extended inactivity
timer defined by the InactCPCNoBatOptT parameter is applied if the UE signals to the RNC that it
does not benefit from UE battery power optimisation. Based upon the default values, the extended
inactivity timer is greater when the UE does not benefit from UE battery power optimization.
Table 39 presents the remaining parameters associated with the CPC feature.
Parameter

New

Scope

Range

Default

Recommended

EnablDelayStand

RNC

0 (0), 1 (1), 2 (2), 3 (4), 4 (8), 5


(16), 6 (32), 7 (64), 8 (128)

5 (16)

5 (16)

EnablDelayHHO

RNC

0 (0), 1 (1), 2 (2), 3 (4), 4 (8), 5


(16), 6 (32), 7 (64), 8 (128)

6 (32)

6 (32)

UEDRXGrantMonit

RNC

0 (True), 1 (False)

0 (True)

0 (True)

InacUsersOverloadFact

RNC

0 to 1, step 0.01

InactUsersCACThreshold

WBTS

InactUsersCIDThreshold

WBTS

InacUserNbrXXXOverNRT

RNC

1 to 5, step 1

DLInLoopPCStepSizeCPC

RNC

0 (0.5 dB), 1 (1.0 dB), 2 (1.5 dB),


3 (2.0 dB)

0.9

0.9

0 to 100 %, step 1 %

90 %

90 %

0 to 100 %, step 1 %

90 %

90 %

2 (1.5 dB)

2 (1.5 dB)

Table 39 Other parameters associated with the CPC feature

The EnablDelayStand and EnablDelayHHO parameters define activation times for CPC following
a radio link setup. The parameter values define a delay in terms of 10 ms radio frames. The
EnablDelayStand parameter is applied after a radio link setup procedure which provides the Node
B with propagation delay information, e.g. CELL_FACH to CELL_DCH state transition. The
EnablDelayHHO parameter is applied to radio link setup procedures which do not provide the
Node B with propagation delay information, e.g. inter-frequency handover and inter-RNC intra-

Copyright Nokia Siemens Networks 2008

Company confidential

Page 47 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

frequency handover. A delay is not applied during a soft/softer handover nor during a serving cell
change.
The UEDRXGrantMonit parameter determines whether or not UE should monitor the E-AGCH and
R-EGCH during periods of downlink DRX. When this parameter is set to True, UE monitor the
grant channels are specific times rather than monitoring them continuously.
The InacUsersOverloadFact, InactUsersCACThreshold and InactUsersCIDThreshold
parameters are applicable to Preventative Overload Control. Increasing the time that connections
spend in CELL_DCH increases the probability of reaching the maximum allowed number of
connections. Preventative Overload Control starts to release inactive connections prior to reaching
the maximum number of connections. The InacUsersOverloadFact parameter is applicable to
helping to prevent reaching the maximum number of HSDPA MAC-d flows, maximum number of
HSDPA users, maximum number of HSUPA users per cell, maximum number of HSUPA users per
Local Cell Group (LCG) and maximum number of HSUPA users per Node B. The
InactUsersCACThreshold parameter is applicable to helping to avoid fully loading the Iub
transport bandwidth. The InactUsersCIDThreshold parameter is applicable to helping to avoid
reaching the maximum number of AAL2 Connection Identifiers (CID).
The InacUserNbrXXXOverNRT parameter defines the number of connections which are targeted
during the RT-over-NRT and RT-over-RT procedures. Targeting more than a single inactive
connection reduces the probability that the RT-over-NRT and RT-over-RT procedures are triggered
again.
The DLInLoopPCStepSizeCPC parameter defines the step size for downlink inner loop power
control when CPC is activated. The default value of 1.5 dB is in contrast to the default value of 1.0
dB which is applied when CPC is deactivated.

5.4 HSPA 72 Users per Cell


The maximum number of HSPA users per cell is increased to 72 with this feature.
Requirements
UE requirements

Rel-7 UE with CPC support

Network Hardware Requirements

Flexi Rel. 2 HW
Ultrasite with EUBB

Feature Requirements

Basic HSUPA
Basic HSDPA
Dynamic
allocation

resource

HSDPA 15 codes
License

RNC ON/OFF license

Table 40 - Feature requirements HSPA 72 Users per Cell

5.4.1 HSPA 72 Users Per Cell Parameters


The RNC databuild parameters associated with the HSPA 72 Users per Cell feature are presented
in Table 41.
Parameter

New

Scope

Range

Default

WCEL

0 (Not enabled),

HSPA72UsersPerCell

Copyright Nokia Siemens Networks 2008

Company confidential

Recommended
1 (Enabled)

Page 48 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20
1 (Enabled)
MaxNumberHSDPAUsers

Date: 30.07.2010
Version 1.1

(Not
enabled)

WCEL

1 to 255, step 1,
0 (unrestricted)

0
(unrestricted)

0 (unrestricted)

MaxNumberHSDSCHMACdflow
s

WCEL

1 to 255, step 1,
0 (unrestricted)

0
(unrestricted)

0 (unrestricted)

MaxNumberEDCHCell
MaxNumberEDCHLCG

WCEL

1 to 72, step 1

WBTS

1 to 160, step 1

NumberEDCHReserved

WCEL

0 to 10, step 1

SHOBranchAdditions
MaxNbrOfHSSCCHCodes
RsrvdSignaturesOffset
HSUPACtrlChanAdjPeriod

20
60

72
160

WCEL

1 to 4, step 1

WCEL

5 to 11, step 1

10

10

RNC

15 s

15 s

10 to 30 s, step 1 s

Table 41 Parameters associated with the HSPA 72 Users Per Cell feature

The HSPA72UsersPerCell parameter enables/disables the HSPA 72 Users per Cell feature. The
default value is disabled, so the feature is disabled unless the parameter is changed. Enabling this
feature allows a maximum of 72 HSDPA connections per cell plus 72 HSUPA connections per cell.
These figures can be overridden using the existing MaxNumberHSDPAUsers and
MaxNumberEDCHCell parameters. The maximum number of HSDPA and HSUPA connections
can also be limited by the MaxNumberHSDSCHMACdflows, MaxNumberEDCHLCG and
NumberEDCHReservedSHOBranchAdditions parameters.
If the HSPA72UsersPerCell parameter is set to disabled then the number of E-RGCH/E-HICH
channelisation codes is fixed at 1. If the HSPA72UsersPerCell parameter is set to enabled then up
to 4 E-RGCH/E-HICH channelisation codes can be allocated. The RNC periodically checks
whether or not an additional code is required. The HSUPACtrlChanAdjPeriod parameter defines
the period between consecutive checks. An additional E-RGCH/E-HICH code is allocated if the
number of free signatures within the cell becomes less than the value of the
RsrvdSignaturesOffset parameter. The RsrvdSignaturesOffset parameter is also used to trigger
the release of E-RGCH/E-HICH codes. If the number of available signatures becomes greater than
39 + 2 RsrvdSignaturesOffset then a code is released. If the number of available signatures
becomes greater than 78 + 2 RsrvdSignaturesOffset then 2 codes are released.
The MaxNbrOfHSSCCHCodes parameter is also associated with this feature although its
increased range in RU20 is enabled by the HSDPA code multiplexing license. If the code
multiplexing license is present then this parameter has a range from 1 to 4 rather than from 1 to 3.

5.5 Direct Resource Allocation for HSPA


Direct Resource Allocation for HSPA feature is introduced in RU20 On Top. Prior to enabling this
feature, user plane resources for NRT PS RAB are allocated in two steps. When UE establish an
NRT PS RAB in CELL_DCH, a 0/0 kbps DCH is allocated during RAB establishment. Traffic
volume measurements are then configured and a subsequent capacity request is required to
trigger the allocation of a non-zero DCH, HSDPA or HSPA. Likewise, user plane resource
allocation from CELL_FACH is completed in two steps with no resources being allocated during
RAB establishment.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 49 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The Direct Resource Allocation for HSPA feature allocates HSPA or HSDPA during RAB
establishment. The feature is not applicable to DCH connections. It can be enabled for CELL_DCH,
CELL_FACH or both CELL_DCH and CELL_FACH. Direct resource allocation helps to reduce
connection establishment delay and improves the end-user experience. The concept of direct
resource allocation is illustrated in Figure 9.

Figure 9 Concept of Direct Resource Allocation for HSPA

5.5.1 Direct Resource Allocation for HSPA Parameters


The RNC databuild parameter associated with the Direct Resource Allocation for HSPA feature is
presented in Table 42.
Parameter
RABDRAEnabled

New

Scope

Range

RNC

0 (Disabled),
1 (Enabled in CELL_FACH)
2 (Enabled in CELL_DCH)
3 (Enabled in CELL_FACH
and CELL_DCH)

Default
0
(Disabled)

Recommended
3 (Enabled in
CELL_FACH
and
CELL_DCH)

Table 42 Parameters associated with the HSPA 72 Users Per Cell feature

The RABDRAEnabled parameter is used to enable/disable the Direct Resource Allocation for
HSPA feature. It also provides the choice of enabling the feature for UE in CELL_DCH, enabling
the feature for UE in CELL_FACH, or enabling the feature for UE in CELL_DCH and CELL_FACH.
Dynamic Resource Allocation must be enabled using the HSDPADynamicResourceAllocation
parameter prior to enabling Direct Resource Allocation for HSPA.
Note that direct resource allocation is applied in the case of full HSPA (HSDPA, HSUPA & FDPCH) irrespective of the value of the RABDRAEnabled parameter.
Copyright Nokia Siemens Networks 2008

Company confidential

Page 50 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

6 Air interface performance


6.1 Performance and features
Table 43 lists the most important RU20 features which have effect on the cell range or capacity.
This chapter gathers the available information related to performance with these features.
RNC Features

Link budget

Cell capacity

Yes

Yes

MIMO

Yes

Yes

HSDPA 64 QAM

Yes

Yes

DC-HSDPA 42Mbps

Yes

Yes

HSUPA 5.8 Mbps

Yes

Yes

HSUPA 2ms TTI

??

??

Voice
CS Voice over HSPA
HSDPA

User experience

Fractional DPCH

No

Yes

Continuous Packet Connectivity

No

Yes

Table 43 - RNC Features

Impact on Coverage Dimensioning


Figure 10 Features impact to coverage

Copyright Nokia Siemens Networks 2008

Company confidential

Page 51 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Influence on capacity dimensioning


Influence on BB dimensioning

Figure 11 Features impact to capacity and baseband dimensioning

6.1.1 CS Voice over HSPA


With CS Voice over HSPA the AMR radio bearers are mapped to HSPA transport channel, HSDSCH and E-DCH. In HSPA transport channel carries MAC-d and MAC-e PDUs respectively
between BTS and RNC. Table 44 lists the number of bits and corresponding bit rates for each AMR
codec mode and in SDU, MAC PDU and MACe/ehs PDU level.

AMR mode
AMR mode
AMR mode
AMR mode
AMR SID
AMR-WB mode
AMR-WB mode
AMR-WB mode
AMR-WB SID
SRB

AMR rate
12200
7950
5900
4750
1950
12650
8850
6600
2000

Class A
SDU
81
75
55
42
39
72
64
54
40

Class B
SDU
103
84
63
53
0
181
113
78
0

Class C
SDU
60
0
0
0
0
0
0
0
0

MAC-d
PDU size
264
176
136
112
56
272
200
152
56
144

MAC-d
rate
13200
8800
6800
5600
2800
13600
10000
7600
2800
7200

MAC-e
PDU size
282
194
154
130
74
290
218
170
74
162

MAC-e
rate
14100
9700
7700
6500
3700
14500
10900
8500
3700
8100

MAC-ehs
size
288
200
160
136
80
296
224
176
80
168

MAC-ehs
rate
(GBR)
14400
10000
8000
6800
4000
14800
11200
8800
4000
8400

Table 44 - AMR modes and bit rates on HSPA

When considering the effect of CS Voice over AMR on the link budget and cell range, the used
MAC-d and MAC-e PDU sizes should be considered.
In DL the UE must be capable of receiving the MAC-d PDU with size of 264 bits (12.2 AMR) in cell
border with max. of 10% HARQ rate(??). This corresponds to an average (20 ms speech frame)
MAC-d rate of 13200 bps and instantaneous (2 ms TTI) rate of 132 kbps. The DL link budget is
calculated for the instantaneous rate of 132 kbps.
In UL the UE will transmit a MAC-e PDU of 282 bits (12.2 AMR) and BTS have to be able to
receive this with max 10% HARQ rate. This corresponds an average (20 ms speech frame) MAC-d
rate of 14100 bps and instantaneous () rate of 141 kbps (2 ms TTI) or 28.2 kbps (10 ms TTI). The
DL link budget is calculated for the instantaneous rate of 28.2 kbps (10 ms TTI is used at cell edge).

Copyright Nokia Siemens Networks 2008

Company confidential

Page 52 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

The effect of CS Voice over HSDPA on cell capacity is two way. The AMR call capacity is
increases due to more efficient usage of physical layer resources with HSPA, usage of F-DPCH
and UL gating. Figure 12 shows the effect of CS voice over HSPA with UL gating on UL capacity.

Gating, with 8 ms cycle1&2


12
Normal 2Tx/1Proc 5.9 kbps
Gating 2Tx/1Proc 5.9 kbps
Gating 2Tx/1Proc 12.2 kbps
Normal 2Tx/1Proc 12.2 kbps

RoT in dB

10
8
6
4
2
0
20

40

60
80
# of UEs per cell

100

120

Figure 12 Noise rise with number UEs for UL

On the other hand AMR is delivered on CS bearer with guaranteed bit rate, which can decrease the
HSPA cell throughput due to unequal resource sharing between users. Users in bad conditions will
get higher proportion of resources and lower the cell throughput.

6.1.2 HSDPA 64 QAM


The 64-QAM modulation is not used in cell edge conditions due to high SINR requirement (see
Figure 13), thus it does not have any effect on the cell range.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 53 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Figure 13 16-QAM vs. 64-QAM SINR requirements

The effect of 64-QAM usage on cell capacity depends on the probability of its usage. This
probability can be estimated by looking at the SINR definition of the HSDPA signal on cell. In an
isolated cell (f = 0) and close to transmitter the SINR of the HSDPA signal can be approximated as
below. We can see that is defined directly by the relative power of HSDPA and total BTS power
and orthogonllity.

PtxHSDPA
tot
P
SINR = SF16 tx
1
This indicates that the usage of 64-QAM requires orthogonality of 0.99 or above. In practice this
requires usage on advanced receiver algorithms like equaliser??

6.1.3 DC-HSDPA 42Mbps


DC-HSDPA improves user bit rates and cell capacity by allowing dynamic usage of two HSDPA
carriers for a HSDPA user. This improvement is due to multiple mechanisms:

Higher peak bit rate via combination of bit rate of two carriers
Performance improvement in fading conditions by frequency selective scheduling
and carrier specific link adaptation (separate CQI for both carriers, selection of
best carrier)
Cell capacity gain via statistical multiplexing of larger number of users

Figure 14shows example of simulated DC-HSDPA performance compared to configuration of two


separate carriers. The 10th percentile indicates the performance at cell edge conditions where the
DC-HSDPA gives 28% higher throughput than combination of two separate sectors.
Copyright Nokia Siemens Networks 2008

Company confidential

Page 54 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Throughput Gain over entire Cell Range (8 users)


1
0.9
0.8
0.7

cdf

0.6
0.5

Percentile

PedA, 2xSC
(Mbps)

PedA, DC
(Mbps)

DC Gain
(%)

0.4

10th

0,374

0,480

28

50th

0,950

1,219

28

90th

3,114

3,672

18

0.3
0.2

PedA,
PedA,
PedB,
PedB,

0.1
0

0.5

1.5

2.5

DC; mean = 1.64


2xSC; mean = 1.35
DC; mean = 1.23
2xSC; mean = 1.04

3.5

4.5

DL user throughput (Mbps)

Figure 14 DL throughput distribution over macro cell layout with DC-HSDPA compared to sum of two
separate WCDMA cells

Figure 15 shows the affect of the DC-HSDPA on the cell throughput with about 18-24% cell
throughput increase when compared to two separate carriers.
Receiver Diversity Gain (1Rx MMSE vs. 2Rx MMSE)
14

mean DL cell throughput (Mbps)

12

10

18-24% cell
throughput gain
from DC at 20
PedA UEs

(ca. 1.8-2 Mbps


throughput
increase)

10

PedA
PedA
PedA
PedA
12

14

16

1Rx,
1Rx,
2Rx,
2Rx,

18

DC
2xSC
DC
2xSC
20

number of users

Figure 15 Gain of DC-HSDPA on cell throughput

Copyright Nokia Siemens Networks 2008

Company confidential

Page 55 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

6.1.4 HSUPA 5.8 Mbps


HSUPA 5.8 Mbps increases the theoretical peak bit rate for HSUPA. This does not have any effect
on the cell edge performance and cell range as the UE will not have enough power to reach the
required SINR at BTS.. Some effect is expected to be seen on cell throughput in cells with low
number of simultaneous users. Figure 16 present the results of HSUPA link level performance
simulations. It shows that the throughputs above 4 Mbps require SINR (CIR) above 10 dB at base
station receiver, which requires a maximum noise rise of 10 dB in practice??.

Figure 16 HSUPA link level performance

Copyright Nokia Siemens Networks 2008

Company confidential

Page 56 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

7 RU20 BTS Features


Table 45 lists the new BTS HW introduced in RU20 and RU20 On Top releases.
BTS solutions

Feature
Number

RU20 License

RAN1671

Flexi 3-sector RF Module 1500

RAN1870

Flexi 3-sector RF Module 900

RAN1768

On top

Flexi 3-sector RF Module 2100

RAN2062

On top

Flexi 3-sector RF Module 1.7/2.1

RAN1871

On top, BTS LK

BTS Solution
Enhanced UltraSite Base Band (EUBB)
Flexi WCDMA BTS Products

Multiradio Combiner 850MHz

Multiradio Combiner 900MHz

RRH chaining

On top

Flexi WCDMA BTS Site Solutions and


Features
Flexi WCDMA Software Download Capability
for Antenna Line Devices

RAN2111

On top

RF Sharing WCDMA - GSM

RAN1770

On top, BTS LK

Smart Diplexer

RAN1876

Table 45 - New BTS features

7.1 Enhanced UltraSite Base Band (EUBB)


EUBB will extend UltraSite WCDMA BTS capability to support HSPA+, native IP and future
features. With EUBB UltraSite WCDMA BTS baseband platform is similar to Flexi WCDMA BTS.
EUBB consists of following plug-in units:

WSPF - New baseband processing unit.


WSMF - New routing, summing & multiplexing unit.
AXCF - New transmission unit.

The capacity of EUBB is the same as the capacity of Flexi WCDMA BTS Multimode System
Module with following rules:

EUBB with one WSPF unit equals the capacity of FSMC (250 HW CE's).
EUBB with two WSPF units equals the capacity of FSMD (500 HW CE's).
EUBB with three WSPF units equals the capacity of FSME (750 HW CE's).

Second EUBB sub-rack can be taken in use if more capacity is required (max. 1500 HW CE's).
Existing WSPA/C capacity is pooled normally with logical cell grouping and can be used as of
today. EUBB also includes HW support for connecting the Flexi RF Modules and Remote Radio
Heads via optical OBSAI interface allowing, for example, dual band configurations and new
frequency bands.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 57 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

7.2 Multiradio BTS Concept


Operator will be able to run GSM, WCDMA and LTE concurrently by the same Flexi Multiradio RF
Module. Multiradio BTS concept simplifies the antenna system complexity, no additional external
combiners are required and multiple Radio Access technologies can share the same feeders and
antennas in the same band. When operating in RF sharing mode, a single RF Module can be
connected up to 2 System Modules simultaneously. The picture Figure 17 below shows possible
multiradio scenarios.

Figure 17 Multiradio BTS concept

7.3 RF Sharing WCDMA GSM


With this feature WCDMA and GSM systems can share the same radio module, i.e. multiradio
concept can be enabled in the network.

7.4 Flexi RF Modules

The following table summarises Flexi Multiradio RF Modules available in RU20


and RU20 on Top.

Module Name

Dedicated
Capacity

Flexi 3-sector RF
Module
1500

WCDMA:

Mode

Copyright Nokia Siemens Networks 2008

Concurrent
Capacity

Mode

WCDMA:

Company confidential

Operation Mode

Release

WCDMA, LTE.

RU20

Page 58 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

(FRKA)

Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up
to
3+3+3
@20W*.
Up
to
4+4+4
@15W*.
LTE: Up to 20
MHz/sector.

Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W*.
Up to 4+4+4 @15W*.
LTE: Up
to
20
MHz/sector.

Flexi 3-sector RF
Module
900
(FXDA)

WCDMA:
Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W
*
GSM/EDGE: Up to
6+6+6 @10W
LTE: up to 15
MHz/sector.

GSM/EDGE Up to
4+4+4 +WCDMA Up
to 1+1+1.
GSM/EDGE Up to
3+3+3 +WCDMA Up
to 2+2+2.
LTE:
up
to
10
MHz/sector.

GSM, WCDMA, LTE.

RU20
Top

on

Flexi 3-sector RF
Module
2100
(FRGP)

WCDMA:
Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W
*.
Up to 4+4+4 @15W
*.
LTE: Up to 20
MHz/sector.

WCDMA:
Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W *.
Up to 4+4+4 @15W *.
LTE: Up
to
20
MHz/sector.

WCDMA, LTE.

RU20
Top

on

Flexi 3-sector RF
Module
850
(FXCA)

WCDMA:
Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W
*.
GSM/EDGE: up to
6+6+6 @10W
LTE: Up to 15
MHz/carrier.

Concurrent mode not


supported.

GSM, WCDMA, LTE.


Supports
following
frequencies:
UL:806849MHz,
DL:851894MHz.

RU20
Top

on

Flexi 3-sector RF
Module
1.7/2.1
(FRIE)

WCDMA:
Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W
*.
Up to 4+4+4 @15W
*.
LTE: Up to 20
MHz/sector.

WCDMA:
Up to 1+1+1 @60W.
Up to 2+2+2 @30W.
Up to 3+3+3 @20W *.
Up to 4+4+4 @15W *.
LTE: Up
to
20
MHz/sector.

WCDMA,
LTE
in
dedicated/concurrent
mode
Supports
following
frequencies: UL 17101770MHz, DL 21102170 MHz.

RU20
Top

on

Flexi 1-sector RF
Module
2100
(FRGR)

WCDMA:
Up to 1@60W.
Up to 2@30W.

Concurrent mode not


supported.

WCDMA

RU20
Top

on

* When more than 6 carriers (1Tx/2RX) in use two optical OBSAI links needed between RF module and System
Module. With this feature the WCDMA dedicated operation is activated.

Table 46 - New Flexi Radio Modules

Copyright Nokia Siemens Networks 2008

Company confidential

Page 59 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

7.5 Multiradio Combiner 850MHz


Passive Multiradio combiner (MRC) 850 MHz allows using of common feeders and antennas for
GSM and WCDMA systems operating on the same frequency band. DL insertion loss of 0.5 dB has
only minor impact on transmit power. MRC insertion loss of 4.5dB in UL is compensated with a
MHA, therefore MHA is recommended in this configuration.
When MRC is used, all TX signals of GSM BTS need to be combined into one antenna line when
there are more than one TRX per sector. This is done with an additional wideband combining
(WBC), which introduces a 3.5dB loss to GSM downlink.
The downlink loss caused by the additional WBC may result decreased coverage of the GSM cell.

Shared antenna

Shared MHA

Shared antenna
lines

DL=0.5dB
UL=4.5dB
(W/o MHA)

Flexi Multiradio
Combiner

DL=3.5dB

GSM BTS

Flexi WCDMA
BTS

Additional WBC required due to


MRC (N/A with RTC)

Figure 18 Multiradio combiner

7.6 Multiradio Combiner 900MHz


Multiradio combiner (MRC) 900 MHz is active and contains integrated low noise amplifiers (LNA),
therefore no extra MHA is required. Like MRC 850 MHz, it has DL 0.5dB insertion loss for WCDMA
and additional wideband combining (WBC) 3.5dB loss for GSM downlink.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 60 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Figure 19 Active multiradio combiner

7.7 Smart Diplexer


Smart diplexer is used to co-site low (700-900 MHz) and high (1700-2100 MHz) band BTSs, using
same feeders. Solution supports current alarming for low and high band BTS or both, and devices
can operate independent for Non AISG supported BTS setups.
Smart diplexer solution includes two new hardware units:

FAWA low/high band combiner located near the BTS. It incorporates a wide band
low pass filter with a wide band high pass filter. One unit can be used to combine
the TX and RX bands for a high band base station and low band base station on
the same RF cable. FAWA adds 0.5 dB insertion loss.
FDWA low/high band diplexer is designed to be outdoor mounted and located
after the feeder cables just before the Antenna Line equipment. It incorporates a
wide band low pass filter with a wide band high pass filter. One unit can be used
to separate the TX and RX bands for a high band base station and low band base
station from the same RF cables. FDWA adds 0.5 dB insertion loss.

Total FAWA and FDWA insertion loss is 1 dB in UL and DL. UL loss can be MHA compensated.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 61 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

1 SECTOR

MHAs CAN
BE ANY
LEGACY NSN
OR NEW
DUAL UNITS
WITH AISG
SUPPORT

ANT 2

ANT 1

900
MHz
BTS 1

FDWA
RET
ANTENNA
DOWN TILT
CAN BE
CONTROLLED

RET

FEEDER
IN 1

1710-2170
MHz WITH
CONTROL

698-960
MHz WITH
CONTROL

FDWA

698-960
MHz

FEEDER
IN 2

RET

1710-2170
MHz

EXTRA
RET
CONNECTORS

RF FEEDER
CONTAINS:
TX/RX SIGNALS
DC POWER AND
CONTROL
SIGNAL

FAWA

1800
MHz
BTS

BTS 2

698-960
MHz WITH
CONTROL

ANT 2

ANT 1

BTS 2

DIVERSITY
RF FEEDER
CONTAINS:
TX/RX
SIGNALS
ONLY

EXISTING
BIAS TEES
FOR DC POWER
AND LEGACY
ALARMING.

FEEDER 1710-2170
OUT 1
MHz WITH
CONTROL

DC -48V

FEEDER
698-960 OUT 21710-2170
MHz
MHz

FAWA

NEW 3G
FLEXI
900 MHz
BTS WITH
AISG
SUPPORT

EXISTING
1800 MHz
BTS

Note: -48VDC needed to


bottom unit if MHA in use
Figure 20 Smart diplexer

7.8 RRH Chaining


RRH Radio Chaining feature provides RF-module (RRH) chaining. The main requirements are as
follows:

There can be up to 4 RRH per chain, up to 3 chains per system module.


Maximum 6 RRH in one LCG per BTS.
The maximum distance between RRH is 15km and about 40km distance between
system module and the last RRH. The minimum distance between FSM and first
RRH is 2m.
Flexi Rel.2 Multimode system modules FSMC/FSMD/FSME.
Flexi 1-sector RF module (FRGR 2100MHz).

Copyright Nokia Siemens Networks 2008

Company confidential

Page 62 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

Figure 21 RRH chaining

7.9 Flexi WCDMA Software Download Capability for Antenna Line


Devices
Feature introduces software download capability for antenna line devices (ALD) like Mast Head
Amplifiers, Remote Electrical Tilt actuators and Smart Diplexers via BTS Manager. This feature
minimizes the service interruption, eliminates the need for site visits in case of ALD software
upgrade. Several antenna line devices utilize software upgrades as part of current and future
growth. This SW download capability of Flexi WCDMA BTS allows an upload to occur through the
BTS Manager, which can be used also remotely.

Copyright Nokia Siemens Networks 2008

Company confidential

Page 63 (64)

NPO/NSO Capability Management


3G Radio Network Planning Guideline Delta
for RU20

Date: 30.07.2010
Version 1.1

References
[1]
[2]
[3]

RU20 Dimensioning guidelines https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/379351448


3G Radio Network Planning Guidelines for RAS06 and RU10, https://sharenet-

ims.inside.nokiasiemensnetworks.com/Overview/3G_Radio_Network_Planning_Guideline, https://sharenetims.inside.nokiasiemensnetworks.com/Overview/HSPA_Radio_Network_Planning_Guideline
RU20 training materials https://sharenetims.inside.nokiasiemensnetworks.com/Open/RU20_Delta_Radio_Planning_and_Dimension

Copyright Nokia Siemens Networks 2008

Company confidential

Page 64 (64)