Call Performance Issues

Behaviour
Call set-up
failure

Problem
Poor coverage area

Call drop

Description

Possible solutions
Check Antenna line
If problem is poor
coverage, this means poor installation (antenna position
and quality, cable length and
RSCP (<-95 dBm) thus quality).

also the EcNo derades

very rapidly (< -12 dB) Check that CPICH powers are
when the coverage border balanced between the studied
cells.
is reached.
Check presence of shadowing
obstacles.

Call set-up
failure

Poor dominance area.

Call drop

Add a site to the area.

No main server in the area, too Use buildings and other
many cells with weak CPICH environmental structures to
level.
isolate cell(s) coverage.
CPICH EcNo is usually very Down tilt antennas to make
bad even the RSCP is good e.q. cells dominant and limit effects
RSCP 80-90 dBm but
of interfering cell(s).
EcNo about 10 dB
Check antenna bearing.

Call set-up
failure

Pilot Pollution

Call drop

Dropped
Missing neighbour
call/SHO failure

Add a site.
Find interfering cell
fromScanner results.

Bad CPICH Ec/Io (<-12 dB)

level although CPICH RSCP
level is good. High site in the
neighbourhood may cause
Adjust antenna bearing and
interference.
down tilt or lower the antenna
height (too much tilt will break
the dominance).
Add interfering cell to the
neighbour of the serving cell.
A good usable neighbour is
Check scanner data and look
present within cells coverage for missing neighbours.
area, can cause DL interference
Check the cabling in antenna
if it is not in the active set.
line.
Swapped sectors in WBTS.

Behaviour
Call set-up
Failure
Call drop

Problem
Description
High PrxTotal due to UL The PrxTotal level is
External interference
significantly higher than
expected in no/low load
conditions.

Possible solutions
Try to figure the possible
area/direction of the
interference by checking
PrxTotal level on neighbouring
cells.
Alternatively use spectrum
analyser & directive antenna to
locate interferer.
Inform operator/regulator
about the found conditions.

Call set-up
failure

High PrxToatal due to

wrong MHA settings

Call drop

The PrxTotal level is

significantly higher than
expected in no/low load
conditions.
MHA settings should be
checked, see more in
reference [7]

Call set-up
failure
Call drop
Cell set-up
failure

Long call set-up

time

High Prxtotal due

toInstallationproblems

Check if auto tuning range is

large enough (20 dB).
In case of MHA is used in BTS
check MHA and cables loss
parameters, otherwise PrxTotal
value will be too high.
(If MHA parameter is set to
ON, Cable loss parameter is
used, Cable loss = Real MHA
gain = Feeder loss parameter)
Check the antenna installation
as the last alternative in high
PrxNoise case.

The PrxTotal level is

significantly higher than
expected in no/low load
conditions.
Bad RRC connection set- RRC connection set-up
Set parameters so that
up success rate due to
complete message not heard by reselection process will start
slow Ue cell reselection BTS.
earlier:

Long time interval for

sync between RNC and
BTS before connection

Qqualmin, Sintrasearch and

Qhyst2 as per latest
recommendation [8]
The value of Parameter N312 Use smaller value N312 (2,
is too high: maximum number recommendation is 4).
of in sync indications
received from L1 during the Use Actix for checking the call
establishment of a physical
set-up delay (L3 messages).
channel
Use call set-up time
optimisation feature Dynamic
setting of
ActivationTimeOffset
(possible in RAN1.5.2 ED2)
enables 200 to 500ms
reduction for set up delay.

Behaviour
Dropped call

Dropped call

Dropped call

Dropped call

Problem
SHO to wrong cell will
cause drop call.

Description
Possible solutions
Overshooting cell come
Pan away overshooting cell if
temporarily into active set and it is too close to the serving
forces a suitable serving cell to cell, otherwise apply down
be dropped out. Later RSCP tilting as well.
suddenly drops in the wrong
cell and causes a dropped call
because there is no neighbour
defined.
Cell suffering from UL As the UE Tx power is not
Use cell individual offset
interference = DL
enough for target cell
(negative value) parameter to
(CPICH) coverage much synchronisation, the SHO fails balance the DL and UL
bigger than UL coverage which will cause call drop
coverage.
later.
Check traffic direction of incar UEs to decide which cell
requires offsets.
DL CPICH coverage <> Cell with lower CPICH power Use cell individual offset
than the surrounding is having (positive value) parameter to
too good UL performance, asbalance the DL and UL
this cells UL cannot be used coverage.
efficiently due to SHO is
Note: Cell individual offsets
decided upon DL (CPICH
are not taken into account
Ec/No).
when calculating the added cell
Tx power.
Round the corner effect The call drops due to too rapid Use cell individual offset
CPICH coverage degradation (positive value) parameter to
for Cell A, and therefore there balance the DL and UL
is not enough time for SHO. coverage.

Dropped
Too many neighbours
call/SHO failure

Note: Cell individual offsets

are not taken into account
when calculating the added cell
Tx power.
In SHO area the number of
Delete unnecessary
combined neighbouring cells neighbours.
become more than 31. HO list
Improve dominance.
is created using RNC
algorithm in the final stage
some of the neighbours will
randomly be removed.