3G KNOWLEDGE

SHARING
BASICS
WCDMA Channels
UMTS Intra-Frequency Reselection
Qmeas,s = Serving Cell Ec/No
Qmeas,n = Neighbor Cell Ec/No
Concept Qoffset = offset for neighbor intra-frequency
Qhyst = hysteresis for serving Cell
Intra-frequency cell reselection is
based on the relative ranking of
the serving and the neighbor
cells

Step-1: Scell1 < SIntraSearch

Measurement is initiated

Step-2: RCell1 < RCell2

Step-3: RCell1 < RCell2 < RCell3

Step-4 criteria in step-3 is satisfied

SintraSearch for the duration of the reselection
timer (Treselection = 1 seconds)

Reselection to Cell3
1 2 3 4
UMTS Inter-RAT Reselection to GSM

Qmeas,s = Serving Cell RSCP

Qmeas,n = Neighbor Cell RSSI
Qoffset = offset for neighbor
frequency
Qhyst = hysteresis for serving Cell
UTRAN Intra-Frequency Handover
Procedure
UE RNC
RB Setup Complete

Measurement Control
UTRAN configures event 1a, 1b and 1c

Applies new measurement configuration

Starts intra-freq measurements

Event 1a triggered Measurement Report (1a)

Active Set Update UTRAN decides to add new cell into active set

UE adds new cell

Active Set Update Complete
in to active set

Measurement Report (1b)

Event 1b triggered

Active Set Update UTRAN decides to remove a cell from active set

UE removes a cell Active Set Update Complete

from active set
UTRAN to GERAN Inter-RAT Handover
UE RNC

RB Setup Complete

Inter-RAT MCM (2d, 2f)

Applies new measurement configuration

Starts intra-freq measurements
Measurement Report (2d)

Physical Channel Reconfig. (CM Config.)

Physical Channel Reconfig. Complete

3 CM Patterns:
Inter-RAT MCM (GSM cells, CM Act., 3a) GSM RSSI
BSIC Ident.
Applies new measurement configuration BSIC Reconfirm.
Starts inter-RAT measurements

Measurement Report (3a)

Handover from UTRAN command

UE connects to GSM
WCDMA Events

Event Description Event Type

Event 1a Active set Addition For SHO

Event 1b Active set deletion For SHO

For SHO
Event 1c Replacement of active set cell

For SHO
Event 1d Change of best cell

Event 2d Compressed mode trigger iRAT

iRAT
Event 2f Compressed mode exit

iRAT
Event 3a iRAT execution

Event 1d(HS) Change of serving HS cell HS cell Change

 GOLDEN
PARAMETERS
iRAT
Idle Mode Measurements

-6 dB
IdleQhyst, 2s

FDD_Qmin(Threshold
for GtoU re-selection)

-14 dB

Cell Selection & Re-selection parameters

 Idle Mode Parameters
Recommend
Parameter Description
Minimum acceptable Quallevel in the
qQualMin
cell, to perform cell selection
Minimum acceptable RX level in the
qRxlevMin
cell, to perform cell selection
Threshold (relative to Qqualmin) to
IdleSintrasearch enable intra-frequency
measurements.
The decision on when measurements
on GSM frequencies shall be
SsearchRat
performed is made using this
parameter in relation with Squal.
Hysteresis value in the cell ranking
IdleQhyst2s criteria for cell reselection when
EC/N0 is used
Hysteresis value in the cell ranking
IdleQhyst1s criteria for cell reselection when
RSCP is used
Control of cell selection/reselection.
tReselection
Time-to-trigger for cell reselection.
Current
Remarks
ed Setting Settings
If parameter is too small, the UE may camp on a cell with very low quality -18 dB
-18 dB
and may not be able to receive reliable service. If the parameter is too
large, the UE will prematurely declare the cell unsuitable and may not
-110 dBm
-115 dBm camp on to 3G cell.
If the parameter is too low, the UE will not perform intra-frequency
measurements and may miss the opportunity to perform cell
reselection. If parameter is too high, the UE will perform intra- 10 dB
10 dB
frequency measurements although the likelihood that the
neighboring cells will meet the cell reselection criteria is very small,
thereby wasting UE battery.
If the parameter is too small, the UE will not perform inter-RAT
measurements and may miss the opportunity to perform cell
2 dB reselection to another RAT. If parameter is too large, the UE will 4 dB
perform inter-RAT measurements very often, most likely leading to
unnecessary GSM reselections.
If parameter is too small, the UE may perform frequent cell 2 dB( Not
2 dB reselection to cells only marginally better than the current serving Applicable)
cell, which may lead to excessive battery consumption. If parameter
is too large, the UE may be camping on a relatively weak cell
2 dB although a significantly better cell is available 4 dB
If parameter is too large, the UE may be camping on a relatively
1s weak cell although a significantly better cell is available, or worse it 2 Sec
may suffer an outage in case of a neighboring cells rising CPICH.
 Contd..
Recommende
Parameter Description Remarks Current Settings
d Setting
Choice of measurement (CPICH EC/N0
or CPICH RSCP) to use as quality
qualmeas CPICH_ECNO CPICH_RSCP
measure Q for ranking candidate FDD
cells for cell reselection
Offset of neighboring cell CPICH
measurement value. This parameter is
used for RSCP measurement. The offset Idle mode neighbor cell re-selection will be delayed if the parameter is
idleQoffset1sn 0 0,2,4
is subtracted from the neighboring cell set to a value > 0
measurement value before cell
reselection
Defines idle mode 3G-2G cell re-selection. Too high value, will delay the
qOffset1sn(MO: Signal strength offset between source
5 dB 2G cell re-selection in bad RSCP condition and too low value will lead to 0 dB
GSM relation) and target cells
faster 2G cell re-selections
If the parameter is set too low, UTRAN FDD cells may be reselected too
Minimum RSCP threshold for UTRAN
FDD_RSCP_min -106 dBm early, leading to ping pong. If the parameter is set too high, UTRAN FDD -102 dBm
FDD cell reselection
cells may not be reselected compromising WCDMA coverage.
Minimum Ec/No threshold for UTRAN If the parameter is set too low, UTRAN FDD cells may be reselected to
FDD_Qmin FDD cell reselection. (4 dB difference -14 dB too early, leading to ping pong. If the parameter is set too high, UTRAN -12 dB
from Qualmin) FDD cells may not be reselected compromising WCDMA coverage

Current settings will almost disable the idle mode cell re-selection and UE will remain
camped onto poor Ec/No cell
iRAT Events Ec/No
CS & CS+ PS Multi RAB

Recommended Settings Current Settings

-13 dB 2f
HystFor2F/2
-14 dB -14 dB 2f

InterRATCSThd2FECNO InterRATCSThd2FECNO

-16 dB InterRATCSThd2DECNO
HystFor2D/2

-17 dB -17 dB InterRATCSThd2DECNO

2d 2d

3a 3a

If GSM RSSI > - If GSM RSSI > -

95 dBm 85 dBm
iRAT Events Ec/No
PS only RAB

Recommended Settings Current Settings

-17 dB 2f
HystFor2F/2
-18 dB -16dB 2f
InterRATR99PSThd2FECNO/
InterRATR99PSThd2FECNO/ InterRATHThd2FECNO
InterRATHThd2FECNO
InterRATR99PSThd2DECNO/
InterRATHThd2dECNO
-20 dB InterRATR99PSThd2DECNO/ -18 dB
InterRATHThd2dECNO 2d
HystFor2D/2

-21 dB 2d

3a
3a
If GSM RSSI > -
If GSM RSSI > - 85 dBm
95 dBm

Current settings will trigger early iRATs for PS only RABs but low thresholds for GSM RSSI
will prevent the UE to perform iRAT early and will remain more time in compressed mode
iRAT Events RSCP
CS & CS+ PS Multi RAB

Recommended Settings Current Settings

-104 dBm
2f
Hystfor2f/2
-105 dBm -104 dBm 2f

InterRATCSThd2FRSCP InterRATCSThd2FRSCP

-108 dBm InterRATCSThd2DRSCP

Hystfor2d/2

-109 dBm -106 dBm 2d InterRATCSThd2DRSCP

2d

3a 3a

If GSM RSSI > -

If GSM RSSI > -
85 dBm
95 dBm
 iRAT Events RSCP

PS only RAB

Recommended Settings Current Settings

-109 dB 2f
HystFor2F/2 -106 2f
dBm
-110 dB
InterRATR99PSThd2FRSCP/
InterRATR99PSThd2FRSCP/ InterHThd2FRSCP
InterHThd2FRSCP

InterRATR99PSThd2DRSCP/-108 InterRATR99PSThd2DRSCP/
-113 dB 2d
InterRATHThd2dRSCP dBm InterRATHThd2dRSCP
HystFor2D/2

-114 dB 2d

3a
3a
If GSM RSSI > -
If GSM RSSI > - 85 dBm
95 dBm

Current settings will trigger early iRATs for PS only RABs but low thresholds for GSM RSSI
will prevent the UE to perform iRAT early and will remain more time in compressed mode
 Connected Mode Parameters
Parameter Description Recommended Setting Current Settings

Threshold for event 2d for the used frequency when the measurement quantity is RSCP.
InterRATCSThd2DRSCP -108 -106
Event 2d is used to activate compressed mode

Threshold for event 2d for the used frequency when the measurement quantity is Ecno.
InterRATCSThd2DECNO -16 -17
Event 2d is used to activate compressed mode
The hysteresis parameter determines when any event is trigerred as well as re-trigerred
HystFor2D 2 dB 0 dB
and de-trigerred
Period of time during which the Event 2d triggering condition must be satisfied before
TimeToTrig2D 320 ms 640 ms
transmission of the MEASUREMENT REPORT message can occur
Period of time during which the Event 2d triggering condition must be satisfied before
TimeToTrig2D 320 ms 640 ms
transmission of the MEASUREMENT REPORT message can occur

Relative threshold for event 2f versus event 2d for the used frequency when the
InterRATCSThd2FRSCP 3 dB 2 dB
measurement quantity is RSCP. Event 2f is used to deactivate compressed mode

Relative threshold for event 2f versus event 2d for the used frequency when the
InterRATCSThd2FEcN0 measurement quantity is CPICH Ec/No. . Event 2f is used to deactivate compressed 2 dB 3 dB
mode
The hysteresis parameter determines when 2f event is triggered as well as re-trigerred
HystFor2F and de-trigerred. A relatively higher value of hysteresis helps to avoid re-trigerring the 2 dB 0
same event several times under fluctuating radio conditions

Period of time during which the Event 2f triggering condition must be satisfied before
TimeToTrig2F 640 ms 640 ms
transmission of the MEASUREMENT REPORT message can occur

Period of time during which the Event 2f triggering condition must be satisfied before
TimeToTrig2F 640 ms 640 ms
transmission of the MEASUREMENT REPORT message can occur

26( -85 dBm)

TargetRATThd It represents the minimum required GSM RSSI for reliable handover to GSM -95 dBm

Threshold for event 2d for HS, when the measurement quantity is RSCP
InterRATHThd2DRSCP -115 dBm -108

Threshold for event 2d for HS, when the measurement quantity is Ec/No
InterRATHThd2DEcN0 -21 dB -18
SOFT HANDOVER
 Soft Handover Parameters
Recommended Current
Parameter Description Remarks
Settings Settings
With too low value, cells of relatively good quality may not trigger an
Threshold used for Event 1a and will have no chance of inclusion in the active set, which
IntraRelThdFor1ACS addition-window in may lead to poor call quality and, ultimately, a call drop. If parameter is
3 dB 3 dB
NVP evaluation criteria for set to a value too large, cells of relatively poor quality may trigger an
event type 1a Event 1a and be unnecessarily included in the active set, therefore
degrading downlink capacity

Threshold used for With too large value, cells of relatively poor quality may not trigger an
IntraRelThdFor1BCS drop window in Event 1b and capacity will be degraded. If parameter is set to a value
10(5dB) 12 (6 dB)
NVP evaluation criteria for too small, cells of relatively good quality may trigger an Event 1b
event type 1b prematurely, thereby negatively affecting call quality

Hysteresis used in If parameter is set to a value too large, cells of relatively good quality
replacement may not trigger an Event 1c and will not replace cells of relatively poor
threshold in quality, therefore degrading downlink capacity. If parameter is set to a
HystFor1C 2(1dB) 8 (4 dB)
evaluation criteria for value too small, cells of quality only marginally better than that of an
event 1c to avoid active set cell may trigger an Event 1c, therefore increasing signaling
ping pong effects load without appreciably improving the combined active set cells quality

Hysteresis used for

Too low value will trigger frequent change of best cells causing UE to
change of best cell
HystFor1D 15(7.5dB) send measurement reports 8 (4 dB)
evaluation criteria for
event type 1d

If parameter is too small, monitored cells of relatively low average

Time between
quality, but whose received CPICH EC/N0 exhibits rapid and large
detection of event 1a
fluctuations, may trigger MEASUREMENT REPORT message
TrigTime1A and sending the 320 ms 320 ms
transmission and be added to the active set. If parameter is too large,
measurement report
the UE will delay transmission of MEASUREMENT REPORT message
for the same
corresponding to monitored or detected cells of relatively good quality.
 Contd
Recomme
Parameter Description
Time between detection of
event 1b and sending the
TrigTime1B
measurement report for the
same
Time between detection of
event 1c and sending the
TrigTime1C
measurement report for the
same
Time between detection of
event 1d and sending the
TrigTime1D
measurement report for the
same
Transmission period of
MEASUREMENT REPORT
ReportIntervalfor1
messages sent by the UE in
A
case of periodic reporting
triggered by an Event 1a
Transmission period of
MEASUREMENT REPORT
ReportIntervalfor1
messages sent by the UE in
C
case of periodic reporting
triggered by an Event 1c
Current
nded Remarks
Settings
Settings
Measurement reporting can be reduced significantly by increasing the time
1280 ms 640 ms
to trigger (TTT) of Event 1b
If parameter is too small, monitored cells of relatively poor average quality,
but whose received CPICH EC/N0 exhibits rapid and large fluctuations, may
trigger MEASUREMENT REPORT message transmission and be added to
320ms 640 ms
the active set. If parameter is too large, the UE will delay transmission of
MEASUREMENT REPORT message corresponding to monitored or
detected cells of relatively good quality
2560 ms Too low value trigger frequent change of best cells for soft handovers 640 ms
If the interval is chosen too short, the UE will transmit an unnecessarily
large amount of measurement reports, thereby consuming processing
1 sec power in the UTRAN. If the interval is chosen too long, the reporting might 4 sec
not reflect the UEs environment closely, thereby inhibiting the benefits of
periodic reporting after an Event 1a was detected
If the interval is chosen too short, the UE will transmit an unnecessarily
large amount of measurement reports, thereby consuming processing
1 sec power in the UTRAN. If the interval is chosen too long, the reporting might 4 sec
not reflect the UEs environment closely, thereby inhibiting the benefits of
periodic reporting after an Event 1c was detected
Coverage
 CPICH power Ratio and Ec/No

It has been observed that majority of cells having low CPICH to max power ratio have very high percentage of Ec/Io samples < -14dB.
As a rule of thumb, CPICH power should be in the range 8% to 10% of total power. Lower values may degrade EcIo distribution in the
cell, especially at high load and in the cell edge, causing problems for the UE to be able to decode Common Control Channels,
leading to accessibility and retainability issues.

CPICH Power Ratio = CPICH power/Total power ( @ antenna connector)

For Ex:
Total TX power = 40W Ec/No @ 2.8W CPICH = 34.47 43 dBm = -9 dB (own cell)
Feeder loss = 0.5 dB Net Ec/No considering 3dB inter cell interference = -12 dB
Required CPICH power ratio = 8%
Avg DL Power utilization = 50%
CPICH pwr = 8%*(35.48W( equivalent of 45.5 dBm) = 2.8W
Ec/No CPICH power ratio

Currently around 60% cells are configured with 40W Tx power, but CPICH power ratio in these cells is only 5%
 Power Mapping for R99 Services

Relative RL power

RLMaxDLPwr
4 dB

RLMaxDLPwr
3.5 dB

RLMaxDLPwr
0 dB

Min Rate Max Rate

<= 15.9 Kbps > 64 Kbps RL Rate
Inter-Rate
<= 64 Kbps

If the max power for each DCH is set too high, the capacity of the cell might be severely limited in case multiple
UEs are at the cell edge, and if it is set too low, the coverage for that service might be severely limited
compared to the CPICH
Current R99 power settings

LID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200, RLMAXDLPWR=0, RLMINDLPWR=-150,

ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=23850, RLMAXDLPWR=0, RLMINDLPWR=-150,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=28800, RLMAXDLPWR=-20, RLMINDLPWR=-170,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=32000, RLMAXDLPWR=-20, RLMINDLPWR=-170,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=56000, RLMAXDLPWR=0, RLMINDLPWR=-150,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=57600, RLMAXDLPWR=-10, RLMINDLPWR=-160
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=CS_DOMAIN, MAXBITRATE=64000, RLMAXDLPWR=30, RLMINDLPWR=-120,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=0, RLMAXDLPWR=-20, RLMINDLPWR=-170,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=8000, RLMAXDLPWR=-40, RLMINDLPWR=-230
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=16000, RLMAXDLPWR=-20, RLMINDLPWR=-210,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=32000, RLMAXDLPWR=0, RLMINDLPWR=-190,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=64000, RLMAXDLPWR=0, RLMINDLPWR=-170,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=128000, RLMAXDLPWR=0, RLMINDLPWR=-150,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=144000, RLMAXDLPWR=0, RLMINDLPWR=-150,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=256000, RLMAXDLPWR=40, RLMINDLPWR=-130,
ADD UCELLRLPWR:CELLID=61001, CNDOMAINID=PS_DOMAIN, MAXBITRATE=384000, RLMAXDLPWR=40, RLMINDLPWR=-110,

Too low max power for higher data rates ranging from 64 kbps to 144 kbps will limit the coverage for these
services
 Other Control Channel Parameters

Recommended
Parameter Description Remarks Current Settings
Settings

It defines the maximum power used for
transmitting the logical channels (BCCH,
maxFachPower
CCCH, and DCCH control signaling) relative
to the primaryCpichPower value.
Too high value may cause high capacity
blockings.The value can be increased after
18(1.8dB) 1,3,4,5 dB
identification of cells having poor RRC
success rate due to bad coverage

It is the power used for transmitting on the

At Too low value UE can miss System
bchPower BCH, relative to the primaryCpichPower -31(-3.1dB) -20 (-2 dB)
information send on BCCH
value
It is the power used for transmitting on the At Too low value UE may not be able to
PSchPower Primary SCH, relative to the -18(-1.8dB) detect Primary SCH for cell search -50 (-5 dB)
primaryCpichPower value. procedure
It is the power used for transmitting on the At Too low value UE may not be able to
SSchPower Secondary SCH, relative to the -35(-3.5 dB) detect Secondary SCH for cell search -50 (-5 dB)
primaryCpichPower value procedure

If parameter is too small, the probability of

acquisition indicator misdetection and false
alarm increase. Indicator misdetection leads
Power level of the AICH relative to that of the
aichPoweroffset -7 to -5dB to increased access time and to increased -6 dB
primary CPICH.
uplink interference caused by the access
attempt.If parameter is too large, downlink
capacity is unnecessarily consumed.

If set too low, the probability of miss-

PICH transmit power relative to that of the detection and probability of false alarm
pichPoweroffset -7 to -6 dB -7 dB
CPICH increase. If set too high, downlink capacity
is wasted.

Too high value of maxfachpower relative to CPICH will lead capacity blockings and too less values for
Psch & Ssch power may lead to misdetection of primary & secondary SCH channel.
Throughput
 HSPA throughput related parameters
Recommen
Parameter Description ded Remarks Current Settings
Settings
The parameter should be set to produce CQI
reports that are centered with respect to the
Measurement power offset, sent to the UE to obtain CQI reporting range. If the parameter is set
total received HS-PDSCH power. too low, it may not appropriately represent the
6 to 8 dB 7.5 dB ( 2.5 dB
MeasurePowerOffset Measure Power Offset = Max(-6, power allocation to the HS-PDSCH, resulting
MPO)
Min(13,CellMaxPower - PcpichPower - Measure in the UE reporting CQI=0 across a large SNR
Power OffsetConstant)) range in cell edge conditions. In this situation,
the Node-B cannot schedule any data to the
user.
2/3 UE will be scheduled in the same TTI,
Parameter determines how many HS-SCCHs that
HsScchCodeNum 2,3 increasing HSSCCH codes will increase 2,4
must be configured
power utilization & code
Used as a switch to turn, the Dynamic Code
Allocation feature, on or off by setting its value to true
AllocCodeMode Automatic Will improve scheduling traffic between users Automatic
or false enable code multiplexing between users in
the same TTI
AllocCodeMode parameter in the RNC and
HsPdschMaxCodeNu Parameter that defines the maximum number of HS- Dynamic code allocation in the Node-B
15 15
m PDSCH codes that are allocated in a cell should be set to " TRUE" to enable max
code usage for HSDPA
HsPdschMinCodeNu It determines the number of codes of SF=16
5 5
m reserved for the HS-PDSCH
It is the power margin, the HSDPA scheduler is using
when allocating remaining power. It is the reserved Too high value will lead to very low HS
PwrMgn 5%
power as a percentage of the maximum transmit throughput
power of the cell
HSPAPLUS_DL_64Q
Support for 64QAM 1 1
AM_SUPPORT
L1 TIMERS
RLS procedure timeout

CSRLReEstCellUpdateTmr = 15
PSRLRestCellUpdateTmr = 35
T313= 3 Sec/ RlRstrTmr=10sec

TRLFailure
NOutsyncInd = 50 =3 sec
=0.5 sec

n313=50
(0.5 sec) t313= 3 sec t314= 12 sec
t315= 30 sec

Poor UL RSSI and EC/No leads to high no. of RLS procedure timeouts and call drops
Current L1 Timer Settings in Chennai

CSRLReEstCellUpdateTmr = 23
PSRLRestCellUpdateTmr = 23
T313 = 5 sec/ RlRstrTmr=11 sec

TRLFailure
=5 sec

NOutsyncInd = 50
=0.5 sec

n313=100
(1 sec) t313= 5 sec t314= 6 sec
t315= 10 sec
UL-RSSI
 Other Parameters to improve UL RSSI
Recommen
Parameter Description ded Remarks Chennai Settings
Settings

Constant used to
determine the initial
ConstantValue PRACH transmitted power
(transmit power of
preamble sent on PRACH)
If set too small, the preamble initial transmit power may be insufficient
for reliable detection at the Node B. This leads to a delay in the
-23 to -27 access procedure. If set too large, the preamble initial transmit power -20
may be larger than needed for reliable detection at the Node B. This
causes unnecessary uplink interference

Maximum number of
If parameter is too small, the probability of successful preamble ramping
preamble transmissions in
PreambleRetransMax 6 to 10 cycle decreases. If parameter is too large, the uplink interference increases. 20
one preamble ramping
cycle

Maximum number of
Mmax
preamble ramping cycles.
If parameter is too small, the RACH access may not take full advantage of
the time diversity provided by preamble ramping cycle repetition. If
3 to 6 8
parameter is too large, the uplink capacity consumption may unnecessarily
increase.

Power offset of the control

If parameter is too small, decoding of the RACH message part may be
part of the message
PowerOffsetPpm 0 dB unreliable. If parameter is too large, too much uplink capacity may be -3 dB
relative to the last
consumed
transmitted preamble
UE transmit power
increase between
This parameter should be set to relatively small value if
subsequent transmissions
PowerRampStep 2 to 3 dB preambleRetransMax is set to a relatively large value, and vice versa, as 2 dB
on the RACH when no
their effect on access latency and uplink interference is compounded
acquisition indicator is
received
KEY FEATURES
Capacity and
Performance
Enhancement
Features
 CPC CONTINUOUS PACKET CONNECTIVITY
Description

With the introduction of CPC, the DPCCH channel in UL and HS-SCCH channel in DL is sent and received discontinuously by the UE,
resulting in the reduction of UL RSSI and improved battery life.

CPC capable UE can now remain inactive in Cell_DCH state for longer time, and can restart transmission with much shorter delay and
also reduces the # of channel switching between DCH and FACH.

A new HSDPA inactivity timer: hsdschInactivityTimerCpc is introduced for CPC users and its value can be set higher than
hsdschinactivity Timer which is for non-CPC users.

By setting the hsdschInactivityTimerCpc parameter to a high value, the CPC UE stays longer on CELL_DCH before switching down to
CELL_FACH at inactivity

Implementation Status : Not Implemented

 SRB ON HSDPA

With SRB on HSDPA feature, SRBs can be mapped to HSDPA at call setup. The main impact and advantage is that less DL code and
hardware resources are needed for SRB on HSDPA, when it replaces the normal A-DCH channel.
Up to 10 separate SRB on HSDPA connections can be mapped onto one SF256 in DL, compared to that each A-DCH connection
requires one DL SF256. Internally this is implemented by each connection using different time positions, using F- DPCH function

Recommended
Parameter Description
Settings
extraHsScchPowerForSrbOnH Extra power used for HS-SCCH for a user with SRB on HS. Relative to the output
2dB
sdpa from the HS-SCCH power control.

Extra power used for sending the data during a HSDPA TTI which includes SRB
extraPowerForSrbOnHsdpa 2dB
data. Relative to the output from the HS scheduler.

HS cell change failures and procedure timeouts can increase with SRB on HS.
HsHysteresis1d 3dB
Decreasing the value will make early cell change before Ec/No severly degrades

Implementation Status : Not Implemented

Enhanced Fast Dormancy

HS-DCH
RlcBufUpswitch Hs-DSCH inactivity Timer : 2 Sec
Downswitch threshold
256 B Current Setting : 4 sec
5 Kbps
(2048 B)
64 Bytes)

FACH
Direct Upswitch to
DCH
(256 Bytes) Inactivity Timer: 15 Sec
Current Setting : 6 sec

URA_PCH

Inactivity TimerPch: 30 Min

Current Setting : 30 min

Idle
 HIGH SPEED CELL_FACH
This feature enables the HSDPA usage in
Cell_FACH state. The logical channels mapped in
previous releases to the FACH transport channel
can be now mapped to HS-DSCH for improving
the performance.

Benefits

Reduction of channel switching between

CELL_FACH and DCH

Improved capacity as more number of active users

in the CELL FACH state per cell

Enabler for the Battery efficiency for HS FACH

feature, which enables UEs in CELL_FACH state
to save battery power by not having to decode the
HS-SCCH channel continuously.
Load Based Features
Inter System Direct Retry & Inter
System Redirect
Description

Inter System Direct Retry is executed at the time of RAB assignment procedure, when a new Voice
call fails to access the system in the admission procedure.

If the RAB ASSIGNMENT procedure fails during admission, the RNC will respond with the RAB
ASSIGNEMNT RESPONSE message with the cause "Direct Retry". Then, a relocation procedure
will be initiated by RNC with the cause of "Direct Retry"

Parameter : DR_INTER_RAT_DRD_SWITCH = 1

Inter System Redirect is executed at the time of RRC Connection Set up procedure, when a new
Voice call fails to access the system in the admission procedure.

If a new speech call is blocked by RRC admission control, then UE is redirected to GSM via
idle mode cell reselection procedure.
Parameter : RedirSwitch = 1

Implementation Status : Not Implemented

Both these features can reduce the RRC and RAB access failure rate for voice calls during
admission control
Measurement based Direct Retry to GSM
Directed Retry will off-load traffic from the WCDMA RAN to a co-sited GSM RAN

A speech call that has no ongoing packet connection is the only service that is targeted since it
is also the only one that is safe to divert to GSM.

 After an RRC connection setup, the RNC determines whether to establish services in inter-RAT
cells based on the current cell load. RNC sends the UE an inter-RAT measurement control
message, instructing the UE to measure the signal quality of the target cell. If the signal quality
of the target cell meets the specified requirements, the RNC establishes services in the target
cell.

Parameters:
PERFENH_MBDR_LOADCOND_OPT_SWITCH: ON
PERFENH_MBDR_TARCELLSEL_OPT_SWITCH: Preferentially select a cell with the optimum
signal quality as the target cell.
Flag of MBDR Cell to TRUE

Example: 85% of pwradm

Offloading starts as soon as the cell load rises above the 85% of pwradm
LoadSharingGSMfraction specifies the %age of Directed retry candidates to be diverted to GSM
while the cell load is above the specified load threshold.
 Load Based HO
Load Based Handover feature provides the possibility to move
speech users to GSM or another UMTS carrier when the load in
a cell is at admission level or above.
If admission control algorithm detects high load when evaluating
an admission request in a cell, then LBHO to GSM for speech
users will be triggered.
The following load quantities are evaluated:

 Power load
 Codes
 DL/UL CE
 Iub

If the high load is detected for at least one of the load quantities
in the cell and there is new incoming call, one or several
ongoing speech connections will be selected for GSM HO
attempts.
Selected UE will be instructed to perform measurements for
these GSM cells (i.e. non-blind HO). If the UE detects and
reports a good-enough GSM cell, the handover attempts will be
triggered.

Implementation Status : Not Implemented

 Interference
Cancellation Features
 Control Channel Parallel Interference Cancellation
A UE in cell DCH state has to continuously transmit the uplink DPCCH. This causes significant increase
in the Uplink interference affecting system capacity.
CCPIC cancels this interference generated by DPCCH.
CCPIC Ph-2 which is a RAN 14.0 feature is an enhancement over basic CCPIC and supports inter board
interference cancellation.
CCPCI Ph-3 which is a RAN 16 feature also supports interference regeneration and cancellation of the
HS-DPCCH and E-DPCCH, therefore increasing the gains in cancellation of control channel interference

HSUPA Interference Cancellation

HSUPA IC regenerates demodulated E-DPDCH signals for HSUPA UEs and cancels interference from
the regenerated signals. This feature therefore reduces the UL RTWP and increases the uplink system
capacity.
HSUPA IC works only for EUL 10ms TTI users

Turbo IC RAN 15.0

Turbo IC improves E-DPDCH IC efficiency for HSUPA 2 ms TTI UEs, thereby reducing interference
between UEs and significantly increasing the uplink system capacity.

Dependency for HSUPA IC and Turbo IC : WBBPd/f or higher boards are IC enabled

Implementation Status : Not Implemented

 EUL TD SCHEDULING
Overview

This feature applies to a cell with multiple high-

speed HSUPA 2 ms TTI UEs. This feature
allocates the eight HARQ processes of 2 ms TTI
HSUPA to different UEs to perform data
transmission. During each 2 ms TTI, only one
UE is transmitting data. This reduces the
interference caused by simultaneous data
transmission of the UEs and improves the cell
uplink throughput.

This feature is not applicable to UEs in SHO mode

 Turbo IC Ph2 RAN 16.0
This feature enables the NodeB to schedule a single HARQ process for a 2 ms TTI HSUPA UE with low-
speed data transmission ,when the uplink load in a cell is greater than the value of the
MaxTargetUlLoadFactor parameter. These UEs each use only one HARQ process to transmit data,
which reduces their minimum data rate from 160 kbit/s to 20 kbit/s. This decreases the inter-UE
interference and increases the number of 2 ms TTI HSUPA UEs in a cell

The minimum rate of 2 ms TTI HSUPA UEs at the RLC layer is 160 kbit/s without this feature and 20
kbit/s with this feature.
 Adaptive Adjustment of HSUPA Small Target Re-transmissions

Description

In earlier versions than RAN15.0, the small target number of retransmissions cannot be adaptively adjusted. When
the uplink load is limited, a small target number of retransmissions will require a high signal-to-interference ratio
(SIR) on the DPCCH, and the DPCCH must have a higher power. This leads to decreased available power on the
E-DCH and E-DPDCH, a lower UE throughput, and a lower cell throughput.

This feature supports an alternative small target number of retransmissions for each typical type of service. The
actual small target number of retransmissions can dynamically shift between the original fixed number and the
alternative number based on the cell uplink load and UE rates, which are configured by the
EdchTargetLittleRetransNum(BSC6900,BSC6910) and EdchAltTarLittleRetransNum (BSC6900,BSC6910)
parameters, respectively. This improves the system capacity when the uplink load is limited

With the Adaptive Adjustment of HSUPA Small Target Retransmissions feature, when the uplink load is limited,
multiple UEs are selected for adjustment to the small target number of retransmissions. This further improves the
cell throughput.

Implementation Status : Not Implemented

Features Activation status in Chennai
FEATURES Status
Pre Release 15.0 Features
SRB over HSDPA Not Activated
CPC (DTX/DRX) Not Activated
High Speed FACH Not Activated
High Speed RACH Not Activated
Load Based Handover Not Activated
Dynamic HSDPA CQI feedback Not Activated
Inter System Direct Retry and inter system re-direct Not Activated
Layered paging in URA Not Activated
RAN 15.0
Adaptive Adjustment of HSUPA Small Target Retransmissions Not Activated
Load Based Dynamic Adjustment of PCPICH Not Activated
Layered Paging in Idle Mode Not Activated
Narrowband interference Suppression Not Activated
HSUPA Time Division Scheduling Not Activated
Platinum User Prioritization Not Activated
USE CASES
Dataset required for troubleshooting
Performance counters and KPIs: Used for identifying worst cells and high level
causes of degraded KPIs

WMRR(2 hour Busy hour): Was used to get coverage and quality estimations for
the network for each RAB configuration separately

Parameter dump: Was used for getting network parameters and configuration
settings. Was used to see the licensed and activation status of various features
of the RAN release.

GPEH(2 hour busy data): GPEH data was used for in-depth analysis of all issues
by looking at Internal events and external signaling messages.

INVH dump/Hardware configurations: was used for baseline check of some of the
hardware dependent parameters.
ECIO DISTRIBUTION- 4 RNCS

In DLGGN01: 34 % cells having more than 25 % samples( < -14 dB) during busy hour
In DLVKP01: 38 % cells having more than 25 % samples( < -14 dB) during busy hour
In DLOKL01 : Only 10 % cells having more than 25 % samples( < -14 dB) during busy hour
In DLGGN02: 13.11 % cells having more than 25 % samples( < -14 dB) during busy hour

This shows that DLGGN01 and DLVKP01 RNCs have very high poor EcIo samples than other
two RNCs
RSCP Distribution- 4 RNCs

In DLGGN01: 25 % cells having more than 15 % samples( < -99 dBm) during busy hour
In DLVKP01: 44 % cells having more than 15 % samples( < -99 dBm) during busy hour
In DLOKL01 : 46 % cells having more than 15 % samples( < -99 dBm) during busy hour
In DLGGN02: 40 % cells having more than 15 % samples( < -99 dBm) during busy hour

RSCP of DLGGN01 is good as compared to other 3 RNCs.

UL RSSI Distribution- 4 RNCs

In DLGGN01: 25% cells in RNC is having average RSSI > -95dBm in busy hour
In DLVKP01: 9.3 % cells in RNC is having average RSSI > -95dBm in busy hour
In DLOKL01 : Only 1.4 % cells in RNC is having average RSSI > -95dBm in busy hour
In DLGGN02: 5.2 % cells in RNC is having average RSSI > -95dBm in busy hour
Summary-IRAT Rate
In DLGGN01, DLVKP01 and DLGGN02 majority of compressed mode are
triggered because of poor EcIo
In DLOKL01 majority of compressed modes are triggered because of poor RSCP
For CS+PS multiRAB configurations, % of Compressed modes due to UE Tx
power are very high.
Very low CPICH power settings are observed for the cells having high IRAT rate
Serviceoffset for EcIo for PS only services has been recently changed in the
network from -7 to -4. This has increased the % of EcIo driven compressed
modes and no of IRATs for PS only configuration which were earlier RSCP
driven.
Current IRAT trigger thresholds for CS is -15 dB for EcIo and -110 dBm for RSCP.
At very low CPICH settings and at very high loading, EcIo degradation will be
high and hence the IRAT rate.
Lower CPICH settings will also increase RSCP based trigger.
 Summary-CS DCR Rate
CS DCR of all 4 RNCs are very good. CS call drop rate is about 0.46 % & 0.51 % in RNC
DLOKL01 & RNC DLVKP01 respectively
CS call drop rate is about 0.67 % & 0.49% in RNC DLGGN01 & RNC DLGGN02
respectively
CS-DCR From Network Counters & GPEH logs (Analysis on 4 RNCs)
About 54 % to 63 % of call drops are due to other reason category across all 4 RNCs
About 17 % to 25 % of call drops are accounted for Uplink Sync across all 4 RNCs
DLGGN01 is having very poor UL RSSI.
25% cells in RNC is having average RSSI > -95dBm in busy hour
DLOKL01 is having high percentage of poor RSCP samples than other RNCs
46 % cells having more than 15 % samples( < -99 dBm) during busy hour
DLGGN01 and DLOKL01 is also having high number of drops due to missing neighbors
DLGGN02 is having cells which contributes to very high drops due to congestions
66% of CS drops in network is happening in MultiRAB calls. Out of 66% MultiRAB drops, 42
%drops are captured in CS+PS(0/0).
DLGGN01 is having very high unspecified drops. Analysis of those drops points to the very
high UL RSSI in the cells of DLGGN01
There are very high number of unspecified drops in MultiRAB due to network configuration
issue.
Besides physical optimization , UL RSSI, IRAT related parameters and call reestablishment
parameters might need tuning.
Summary-HS DCR
It has been observed that poor UL and DL coverage
is the main cause for HS drops. So L3, L2 and L1
timeouts are very high in the network
GGN01 and VKP01 are having high HS DCR than
other two RNCs
Only 4 cells in GGN02 and OKL01 RNC is having
average HS DCR > 3%. Also number of days in
measurement period(7days) where HS DCR was >
3% are less.
54% of HS drops in the network are due to channel
switching
78% of total channel switching drops are due
to L3 procedure timeouts. Out of these L3
procedure timeouts, 84% of procedure
timeouts happened during transition from HS
to FACH alone
~20% of HS drops are due to Layer 2 timeout with
RLC unrecoverable error
~15 % of HS drops are due to hsDschRcLost (L1)
timer expiry
L3 timers for synchronization and non
synchronization procedures is 18 sec and L1 timer is
9 second. It has been observed that RNC is keeping
the session alive even after L1 timeouts till 18
seconds
RRC and Iu resources will be wasted
It might cause MT call failures
Summary- CS & PS CSSR
CS CSSR for all 4 RNCs are very good. All RNCs have CS CSSR > 99%. Both CS RRC and CS RAB success rate is > 99%.

PS CSSR for all 4 RNCs are good. All 4 RNCs have PS CSSR > 98%.

In all the RNCs PS RRC success rate is main contributor for PS CSSR degradation.

DLGGN01 has lowest PS RRC success rate: 97.07%

Out of all call setup failures detected in the RNCs for RRC and RAB, resources admission failures are very less.

Majority of failures are pegged under After admission category.

92% of total RRC and RAB failures in DLGGN01 and DLVK01 are pegged in After admission category

75% of total RRC and RAB failures in DLGGN02 and DLOKL01 are pegged in After admission category

Unspecified RRC failures are very high in the network and distributed almost all cells in the RNC. These failures are
pointing towards netwok issue.

Same observation like in HS and CS DCR that L3 timers are keeping context in the RNC too long after L1 timer
expiry is also observed for RAB failures after admission.

There are few Iub related failures are also observed but those are contributed by 2 sites.
IRAT Rate(Key findings)
Compressed mode Trigger distribution

In DLGGN01 ~64 % of
Compressed modes are
triggered because of poor
EcIo
In DLVKP01 ~55 % of
Compressed modes are
triggered because of poor
EcIo
In DLGGN02 ~48% of
Compressed modes are
triggered because of poor
EcIo while in DLOKL01,
majority of CM triggered
because of poor RSCP
Compressed mode Triggers: (DLGGN01-GPEH stats)

For CS+PS MultiRAB

calls, % of CM triggers
due to UE TX power are
very high. UL MAPL for
CS+PS multiRAB will be
lower than CS only, this
might have caused
significantly higher UE Tx
power based trigger for
MultiRAB

For DLOKL01, poor RSCP

initiated CM triggers are
also very high
Top cells- IRAT rate(DLGGN01 &
DLVKP01)

Very high % of EcIo samples< -14dB

Very low CPICH power with respect At 100%
to Max power loading

Too low CPICH power ratio(some cells have less than 2 %) is the major reason of very poor EcIo.
CPICH power needs to be tuned in these cells to reduce the IRAT rate. Increase in CPICH should be done with down
tilting and on cluster of cells to minimize the overshooting and capacity blockings.
High UE Tx Power triggered CM in CS+PS
multiRAB states but no IRAT
For CS+PS multiRAB configurations, high number of compressed mode were
triggered due to high UE Tx power % of UE (event 6D)
IRAT handover wasnt always triggered and UE was continuously transmitted at
max power, because RSCP of current used frequency has to be below: -108 + (-
4) + 5 = -107dBm for 3a event to trigger. This indicates that the UE was not at
edge of coverage and UE Tx power is high due to UL RSSI
Current network configuration to trigger IRAT HO due to Poor UE Tx power is
below:
Serviceoffset2d for CS+PS multiRABs are: -4( for RSCP)
2d threshold RSCP: -108 dBm
utranRelThreshRscp(offset for UE Tx power): 5
As a result of the above configuration UE stays in CM for longer duration and
keeps transmitting at max power

Recommendation is to reduce serviceoffset2drscp for CS + PS multiRABs, so

that possibility of UE trigger early IRAT HO is higher. This will improve UL RSSI
and UEs will stay for shorter time in compressed mode
Serviceoffset for PS services
It has been observed that serviceoffsetecno for PS only
RAB combinations has been recently changed from -7
to -4 which has resulted in very high early compressed
mode trigger at EcIo: -19dB for PS RABs.
It is recommended to delay or disabled the IRAT
handover for PS services.

Trigger quantity No of CMs Percentage RAB combination

Ecio Trigger for serviceoffset: 0 1056 19.40463065 CS

Rscp Trigger for serviceoffset: -2 361 6.633590592 CS
UE TX Pwr Trigger for serviceoffset: -2 153 2.811466373 CS
Rscp Trigger for serviceoffset: -4 140 2.572583609 CS +PS MultiRAB
Ecio Trigger for serviceoffset: -2 325 5.972069092 CS+PS MultiRAB
UE TX Pwr Trigger for serviceoffset: -4 309 5.678059537 CS+PS MultiRAB
Ecio Trigger for serviceoffset: -4 1552 28.51892687 PS
Rscp Trigger for maximum service offset(at -115dBm) 1032 18.96361632 PS
Rscp Trigger for serviceoffset: -10 5 0.091877986 PS
UE TX Pwr Trigger for serviceoffset: -10 474 8.710033076 PS
Frequent 2d and 2f

Frequent 2d and 2fs

events are observed
in the network even
within in compressed
mode.
Current settings of
hysteresis2d and
hysteresis2f are 0
HS DCR(KEY FINDINGS)
HS drop cause distribution- all 4 RNCs
No of
HS Drop causes
drops
Channel Switching Drops 4460
Maximum number of RLC retransmissions is reached 1628
Radio Connection Supervision - expiry of timer
hsDschRcLostT 1221
Unspecified 804
Radio link failure indication leading to a release with
cause other than transport 73
Active Set Update complete message not received -
addition 42
High Speed-Downlink Shared Channel (HS-DSCH)
Cell Change failure 35
Active Set Update complete message not received -
replacement 27
Missing neighbor 22
Cell change outgoing failure Timer T_cellchange
expires 11
Other Radio Link Control (RLC) unrecoverable error. 10
Active Set Update complete message not received -
deletion. 8
Cell lock indication. 3
Transport issue 3
Congestion Failure 2
IRAT outgoing failure - Timer T_reloc_overall expires 2
Measurement control faiure 1
Total 8352

~54 % of HS drops are during state transition

L1 and L2 timeouts contribution is 14.6% and 19.5% resp.
Cause 1: Channel Switching
Drops
Sub causes: Channel Switching drops

Total no of
Channel switching failure: Sub causes
drops

PROCEDURE_TIMEOUT 4329

CELL_UPDATE_IN_DRNC 109

Unspecified channel switch failure 6

NODE_INTERNAL_FAILURE_6 5

GENERAL_FAILURE_IN_PROCEDURE 4

REQUESTED_REQUEST_TYPE_NOT_SUPPORTED 4

NODE_INTERNAL_FAILURE_2 1

NODE_RESOURCE_NOT_AVAILABLE_1 1
PROCEDURE_EXECUTION_TERMINATED_EXTERN
AL 1

Total 4460

Out of all Channel switch drops 78% of drops are purely Layer 3 procedure timeouts
Sub causes: Channel Switching drops
Procedure timeout
Percentage of
Cause: Procedure Timeout
drops

INACTIVITY(expiry of
83.8
hsdschinactivityTimer)

INCREASE_ACTIVITY_UL 8.8

INCREASE_ACTIVITY_DL 6.2

EUL/HS to EUL/HS(Mobility) 0.8

DECREASE_ACTIVITY_UL 0.3

UL_SOFT_CONGESTION 0.1

FALLBACK_TO_R99 0.1

Out of all L3 procedure timeouts, 83.8% drops are happening during HS to FACH transition
~ 15 % of procedure timeouts are during FACH to HS transition
24.8 % of L3 procedure timeouts are happened at UL RSSI< -95 dBm
Procedure Timeout- Inactivity(Poor UL RSSI)
UE was on EUL/HS and due to
inactivity and expiry of
hsdschinactivityTimer, RNC
RBR for triggered transition from HS to
reconfiguring to
FACH FACH by sending RBR message to
UE and started tRrcChSwitch1:
15 sec
Since RNC didnt receive any RRC
Cell Update message from UE
during transition So after 15
seconds Channel switching
There was no cell
update received procedure failed and call was
from the UE released.
probably because
of high UL RSSI This cell was having very high UL
RSSI samples as seen from the
GPEH for that hour. Probably UE
has sent cellupdate but it was
not decoded by RNC due to very
high UL RSSI.
Cause 2: Impact of SRB on HS
Maximum number of RLC
retransmissions is reached
Case study-HS cell change failures due to RLC timeout(
Very poor EcIo in serving cell)

Averge EcIo(Source cell): -19.18 dB Averge RSCP(Source cell): -92.4 dB

Average EcIo(Target cell): -13.6 dB Average RSCP(Target cell): -86.21 dB

Since hsQualityestimate: RSCP and hsHysteresis1d: 5dB so HS cell change is performed if

RSCP of target cell is 2.5(ie.5/2) dB higher than source cell which can be seen from the
above RSCP comparison chart. But in the network at the same time EcIo of source cells
was too low(average: -19.18 dB) that UEs didnt acknowledge Physical channel
reconfiguration and the RLC timed out during HS CC procedures. Since SRB on HS is
activated, there is not any SHO gain for SRB in DL.
Case study-HS cell change failures due to
RLC timeout
MR: 1a
UE was on Cellid:58759(EcIo:
-17dB and RSCP: -84 dBm. It
was only cell in the Aset. UE
triggered measurement report
for 1a for cell: 23869(EcIo:-12
Addition dB, RSCP: -78dBm). SHO:
successful addition was successful
UE now triggered change of
MR: 1d
serving cell on the basis of
HS serving
RSCP and sent measurement
cell change report for 1d
started
RNC initiated change of
serving cell by sending
EcIo of
PhysicalChannel
current Reconfiguration, but
serving cell: -
19dB meanwhile EcIo of current cell
became too low( -19dB) that
Physical Channel
Reconfiguration might have
not decoded by the UE.
RNC tried maximum
retransmission before
Call
dropped declaring RLC timeout.
Ongoing Cell change was also
failed and call dropped.
 Cause 3:
Radio Connection
Supervision - Expiry of
timer hsDschRcLostT
 Radio Connection Supervision - Expiry of timer
hsDschRcLostT
These drops are due to UL/DL coverage
Current procedure running while hsDschRcLostT
Total drops issue
expired(Total contribution to HS drops: 14.6%)
Radio link Failure without any procedure running 529
These drops are pegged due to
HS_CELL_CHANGE_EXECUTED 160
L1(hsDschRcLost) timeout
Poor quality detected(2d): EUL2ms to EUL 10ms 141 43% of these drops captured were
RAB failure after successful admission 139 happened when there was not any L3
RL_ADDITION 100 procedure was going on
RL_REPLACEMENT 61 It has also been observed that except
INCREASE_ACTIVITY_UL 33 Radio link failure without any procedure
RL_DELETION 23 running, in all other calls some L3
INCREASE_ACTIVITY_DL 12 procedure was ongoing. L3 timer(18sec)
FALLBACK_TO_R99 6 values are higher than L1 timer(9sec).
INACTIVITY(HS to FACH) 6 But after L1 timer expiry network is not
RANAP_CAUSE_NORMAL 5 releasing the call till L3 timer expiry of
DECREASE_ACTIVITY_UL 1 18 sec. This is leading to extended call
UL_SOFT_CONGESTION 1 sessions maintained for the UEs in the
network keeping Iu resources, UE
31.4 % of RCS drops are happened at UL context etc. It may also impact paging
RSSI< -95 dBm for voice because UE seems to be in idle
There were also very high number of HS while network will page via DCH as its
cell change executions failed during
these L1 procedure timeouts
session is alive in the RNC.
L3 timer keeping context in RNC too long
Measurement
report 1a UE triggered SHO for 1a
for cell id: 6165(RSCP -
98dBm, EcIo: -13dB)
Since added cell is also
better than serving cell
by 2.5 dB (hshteresis1d)
so RNC tried to change
the serving cell also, but
cell change failed because
Successful
SHO of max EUL 2ms users in
the cell
Failed Cell
change RNC reconfigured the
2ms connection to 10 ms
Then RNC initiated
Channel serving cell change by
switching
from EUL sending Physical channel
2ms to 10 reconfiguration and
ms
initiated L3 timer(18 sec)
Change of
serving cell
L3 timer keeping context in RNC too long

But since DL was too bad probably UE didnt

receive the physical channel reconfiguration. Poor
DL also triggered RL supervision in UL after
stopped transmission from UE(N313 indication)
First Internal RC supervision gives Radio link
failure (rLFailureT: 1sec expires) indication for all
radio links
Second Internal RC supervision gives the
rlFailureT expired indication of hsDschRcLost timer: 9 sec in the
RNC. It generates the cause code: overall RRC
connection should be released. Third Internal RC
supervision is the periodic event generated after
expiry of hsDschRcLost and gives the same cause
hsdschRcLost
code. But RNC has not released the call at this
expired
point and waiting for L3 timer(18 sec) to expire.
Finally after expiry of L3 timer(18 sec), RNC
generated failed HS cell change indication and
released the call.
Serving cell
change failed and
dropped call

RNC has released this call with cause : L1 timer expiry(from its internal event), but from the
signaling, we can see that RNC didnt release the call after L1 expiry but at L3 expiry. Needs to
check with vendor about this behavior. Since these types of HS drops are high in number, it might
impact paging type 2 success rate.
 CS DCR
(KEY FINDINGS)
 CS Call Drop Reasons Distribution per each RNC
RNC DLGGN01 CS Call Drop Reasons RNC DLOKL01 CS Call Drop
RNC DLGGN02 CS Call Drop
Distribution Reasons Distribution
Reasons Distribution Drop call Drop call
Drop call soft missing
soft handover nbr
Drop call Drop call
Drop call IRAT handover Drop call 3%
Drop call 4%
missing nbr congestion
6% Drop2%
call missing nbr IRAT Drop call
6% 0% 9%
Drop call soft IRAT 5% congestio
handover 7% n
3% Drop call Drop call 0%
congestion uplink
Drop call 8% sync
17% Drop call
uplink sync Drop call other
18% uplink sync 67%
Drop call
19% other
Drop call 59%
other
67%

RNC DLVKP01 CS Call Drop

About 58 % to 63 % of call drops are not defined (other) Reasons Distribution
Drop call
across all 4 RNCs soft Drop call
handover missing
About 17 % to 25 % of call drops are accounted for Uplink Drop call
2% nbr
IRAT
Sync across all 4 RNCs 12%
2%
Drop call
congestion
RNC DLVKPO1 has 12 % of call drops due to IRAT 1%

RNC DLGGN01 has 9 % of call drops due to Soft handover &

missing neighbor Drop call
RNC DLGGN02 has 8 % of call drops due to call congestion uplink sync Drop call
25% other
58%
Worst cell missing neighbors
(DLGGN01) N01 missing nbrs

Cell Average of Speech call drop rate % Drop call congestion % Drop call missing nbr % Drop call uplink sync % Drop call IRAT % Drop call soft handover % Drop call other

DLFP3BX 2.193977444 0% 28% 10% 10% 2% 50%

There were 4
CS call drop
captured during
the recording
period for
DLFP3BX due
to missing
neighbors.
There were 4
different PSCs
detected for
each drop.
Drop due to congestion- Top cell:
DLGGN02

mimimumRate of 3.7 kbps is for ADCH signaling. For cells with high HSDPA
load (many HSDPA users) the A-DCH power can constitute of a large part
of the used downlink. minpwrmax for these two cells are set to 3 dB
higher than CPICH power(34 dBm). This might be creating high congestion
ADCH in these two cells.
signaling
Counter stats for these cells shows, these cells have very high HS traffic
and HS RAB attempts. CS traffic is also high in these cells.
HS traffic: ~4 GB per day
HS RAB attempts: ~13000 per day

Recommendation: set minPwrMax

for these 2 cells: 0 dB
CS drops due to IRAT failures
Two RNCs: DLVKP01 and DLOKL01 has high IRAT
drops. DLVKP01 has 12% of drops and DLOKL01 has
9% of drops due to IRAT.
Analysis of these drops have common signature that
after triggering IRAT(3G to 2G), UE doesnt
successfully established call in the 2G and also not
able to return back to 3G with in 5 sec of (RNC timer:
tRelocoverall). So RNC releases the call.
RSSI of the target GSM cell in all the failures at the
time of handover is very good(average: -74dBm)
These IRAT failures are distributed across the RNCs
and not only happening in certain cell relations.
Possible reasons for this issue are
UE took longer time to synchronize / remains in
3G for longer time before synchronizing to 2G
and tRelocoverall(5sec) timer expired
Never went to 2G because IRAT HO command
not decoded due to poor DL and after expiry of *Attached is the list of all IRAT Ho failures captured in the
tRelocoverall(5sec) call released GPEH for 3 worst RNCs(DLGGN01,DLVKP01,DLOKL01)
Co BCCH/BSIC (ie. BSC has reserved the
resources in wrong cell having same BCCH/BSIC
but UE tried to synchronize on different cell
 CS drops due to IRAT(abnormal call)
MR :
3a
UE detected poor DL and
triggered MR for 3a for 2G
Resource
reservation in 2G cell
cell BSC reserved the resources
in the 2G cell and sent
Relocation Command.
RNC sent HANDOVER_FROM
Measurement UTRAN_COMMAND and
reports 3a
started trelocoverall timer of
5sec.
Serving cell EcIo: -
19dB, RSCP: -94 But UE probably didnt
5
dBm receive the IRAT HO
sec command due to poor DL
Measurement
and continuously sending
reports 3a Measurement reports: 3a
UE didnt leave 3G channel
till 5sec so after 5 sec, since
RNC didnt receive Handover
Dropped
complete from 2G BSC, it
call released the call abnormally
Recommendation
Co BCCH/BSIC needs to be checked for the cells having IRAT failures at
very good 2G RSSI
Since IRAT HO threshold for CS+PS(0/0) -17dB/-112dBm, possibility of
decoding failure of IRAT HO command from the network is higher. IRAT
HO threshold for CS+ PS(0/0) can be aligned with CS only .
Probability of successful IRAT handover in poor coverage can be
improved by increasing trelocoverall to 7 sec, if UE took longer time to
decode IRAT HO command from the network
CS call & MRAB drop distribution
GPEH CS
CS CALL & MRAB DROPS DISTRIBUTION CAPTURED
CS Conv--Speech FROM GPEH
12.2 + PS Interactive
64--HS CS Conv.--Speech
3% (12.2--12.2) + PS
Interact. (16--HS)
21%
CS Conv--Speech
12.2 + PS Interactive
0--0
42%

CS Conv--Speech
12.2
34%

Majority of MRAB call drops captured from GPEH are from CS +PS 0/0
66% of CS drops in network is happening in MultiRAB calls. Out of 66% MultiRAB drops,
42 %drops are captured in CS+PS(0/0).
MRAB analysis

MRAB drops: Below are the major causes of MRAB drops:

Channel Switching: 26.6 %
Procedure Timeout(L1): 20.1 %
Unspecified(majority of CS normal release in high UL
RSSI scenario) : 17.3 %
IRAT trelocoverall (5sec) expiry: 12 %
 L1 Procedure timeouts
UTRAN RL failure detection is controlled by the Radio Connection Supervision
(RCS) and Radio Link Set (RLS) Supervision functions: after receiving
nOutSyncInd consecutive frames, UTRAN starts timer rlFailureT. If rlFailureT
expires, the RLS function considers the connection as out-of-sync and report RL
Failure to RNC. When RL Failure is received, the SRNC starts timer dchRcLostT
and if this timer expires the connection is considered lost by RCS. The total time
for UTRAN to detect RL Failure: nOutSyncInd * 10msec + rlFailureT +
dchRcLostT
These drops are due to UL/DL coverage issue
These drops are pegged due to L1(dchRcLostT) timeout
It has also been observed like in HS DCR RCS drops , after L1 timer expiry
network is not releasing the call till L3 timer expiry of 18 sec. This is leading to
extended call sessions maintained for the UEs in the network keeping Iu
resources, UE context etc. It may also impact paging for voice because UE
seems to be in idle while network will page via DCH (paging type2) as its session
is alive in the RNC. These L3 procedures are identified as Active set update,
Radio bearer reconfiguration(multiRAB), HS cell change(multiRAB).
 L3 timer keeping context in RNC too long

UE was in Poor DL EcIo: -20dB and RSCP -

112dBm and triggered event 1a. Network
sent Active set Update.
But since DL was too bad probably UE didnt
decode the Active Set Update. Poor DL also
triggered RL supervision in UL after stopped
transmission from UE(N313 indication)
First Internal RC supervision gives Radio link
18
failure (rLFailureT: 1sec expires) indication
sec for all radio links
Other Internal RC supervision gives the
indication of dchrclostT timer: 10 sec in the
RNC. It generates the cause code: overall
RRC connection should be released. But RNC
has not released the call at this point and
waiting for L3 timer(18 sec) to expire.
Finally after expiry of L3 timer(18 sec), RNC
generated failed Soft Handover execution
and released the call.

RNC has released this call with cause: L1 timer expiry(from its internal event). But from signaling, we can see that RNS didnt
release the call after L1 expiry but L3 expiry. Need to check behavior with vendor. Since these types of HS drops are higher in
number, it might impact paging type 2 success rate.
 CS & PS CSSR
(KEY FINDINGS)
Admission Vs After Admission Failures
Count of After Count of
RNC Admission Admission
Failures Failures

DLGGN01 19334 1734

DLGGN02 9125 2836

DLOKL01 19910 6909

DLVKP01 18748 1626

After admission failures

are distributed in all
cells across the RNCs
but majority of
Admission failures are
contributed by few cells
in each RNC.
ADMISSION FAILURES
Admission Failures contribution
 Cell- WPROTCX (Admission failure due to lack of
DL CE)
UCell Id WPROTCX numHsCodeResources: This parameter reserves the
resource ids available for HSDPA in DUW board. Each
resource id provides-
RNC DLGGN01
30 HS-PDSCH codes per site
128 CEs for DL R99 including ADCH
Total RRC and RAB attempts
1959.45 Each DUW 20 board provides 5 resource ids out of which 1
resource id is reserved for EUL
Total Admission Failure Out of remaining 4 resource ids, numHsCodeResources
786.55
reserve the resource id for HS which provides codes for HS.
Admission failures rate Remaining resource ids will be available for R99 which
40.14 provides CEs for DL R99 including ADCH.
Since 1 sector site has 16 HS PDSCH codes, so
Admission Resource contributor DL CE numHsCodeResources for single sector site should not be
set greater than 1. If value is set greater than 1 then there
Cell: WPROTCX will be shortage of DL CEs in the DL
Current site is having only one sector
All Failures are happening because of shortage of DL CE
availableRbsChannelElementsDownlink parameter is showing
value 83. This means that only 83 DL CEs are available from
Hardware limit of 384 DL CEs. Recommendation: Set numHsCodeResources:1
Wrong parameter setting of numHsCodeResources is found in the
cell. Current setting of numHsCodeResources is 3. Recommended
value of numHsCodeResources is 1 for single sector site.
Since site is having DUW 20 board having 5 resource ids. 1
Resource id is reserved for EUL. 3 resource ids are reserved for
HS(numHsCodeResources is 3), So only 1 resource id is left for
R99 service which can provide only 128 CEs in the DL. After
subtracting ADCH reservation CEs, only 83 DL CEs are available
which is too less for a site.
 Cell- CENTRAX and CENTRAY(Admission failure due to
lack of DL Power)
UCell Id
RNC
Total RRC and RAB attempts
Total Admission Failure
Admission failures rate
Admission Resource contributor
Recommendation: set minPwrMax for these 2 cells: 0 dB
CENTRAX
DLGGN02
5402.45 mimimumRate of 3.7 kbps is for ADCH signaling. For cells with high
HSDPA load (many HSDPA users) the A-DCH power can constitute of a
402.18
large part of the used downlink. minpwrmax for these two cells are set
7.44
to 3 dB higher than CPICH power(34 dBm). This might be creating high
congestion in these two cells.
Power
Counter stats for these cells shows, these cells have very high HS traffic
and HS RAB attempts. CS traffic is also high in these cells.
HS traffic: ~4 GB per day
HS RAB attempts: ~13000 per day
ADCH
signaling
AFTER ADMISSION FAILURES
After admission failures: RRC(GPEH
analysis)
PS and CS RRC Failures

Majority of RRC and RAB failures were in the

Failure after admission category. Since
there are not any specific counters are
available to distinguish among these failures,
analysis of these has been done on GPEH
data.
RRC: Unspecified failures are pointing
towards network issue in which without
waiting for the response from the UE, network
is releasing the call after successful
admission.
RRC: Procedure Timeouts are purely
coverage related failures
All Iub setup failures in DLVKP01 and
DLOKL01 are contributed by 1 site in each DLVKP0 DLGGN DLGGN DLOKL0
After admission cause
RNC. 1 01 02 1

Unspecified 655 1037 380 786

Procedure Timeout 204 457 147 199
IUB_AAL2_SETUP_FA
45 0 0 30
ILURE
RRC: Unspecified
Call 1
These type of failures are
very high in the network and
these are not coverage
dependent. RNC is
releasing the calls itself
without waiting the response
of RRC_Connection_Setup
Call 2 from UE.

UL RSSI: -98 dBm and DL

EcIo: -13dB are also very
good.

Need to check with Ericsson regarding these failures

L2 RLC timeout
RNC initiated the RAB
procedure by sending Radio
Bearer Setup to UE but RBS
Complete message is not
received from the UE. UL
RSSI at the time of failure
was: -82 dBm
RNC tried maximum
retransmission before
declaring RLC timeout and
RAB setup was failed
RCS- L1 Timeout
L3 timer keeping context alive despite L1 timeout RNC initiated the RAB
procedure by sending Radio
Bearer Setup to UE and
started L3 timer of 18sec
but RBS Complete
message is not received
from the UE.
L1 supervision shows that
after getting nOutSync
frames and after expiry
hsdschRcLostT(9sec), RNC
generated event which says
RRC connection should be
released. But RNC is not
releasing the call at this
time and releasing the call
after L3 timer(18 sec).
THANK YOU