Problem detection:
TCH assign. Congestion max. > 2 % (Critical , action needed)
TCH Load BH (Erlang / capacity ) > 90 % (forecast)
Investigation:
Any TRXs
down or not
carrying
traffic?
Yes
NO
NO
Any neighbor
site(s) down
not carrying
traffic?
Yes
couple.
Check High HO Inc execution failure on
All neighbors
are loaded
(> 80%) + High
Inc HO
congestion
Yes
NO
NO
Yes
Traffic sharing
Enable FDR on serving cell
Enable Traffic HO for each couple and adjust
relevant parameters according to drive test
analysis. (or leave default values according to # of
TRX)
Enable Fast traffic HO, but monitor HO/call
rate and call drop HO specially for cells with
many inter BSC adjacencies
Radio drops
> 40% of
total drops
NO
HO drops >
40% of total
drops
NO
Yes
Yes
Yes
TS for alarms
Check TCU handling TRX
High TCH
call drop HO
Yes
Same
investigation
should be
followed
Extreme
queueing
?
Check if TRX carrying SD is
NO
NO
High TCH
drop radio
NO
Yes
Reduce queuing
Solve TCH blocking prob.
(refer to TCH congestion
solving sheet)
Reduce T11 value (TCH
Yes
Call drop radio investigation
should be followed
NO
High
signaling
load? > 4
Yes
Yes
Isolated
cell
NO
Densification
sites are needed
Yes
Hardware
Problem
Check HO
causes
No
Report to
BSS team
Yes
High %
UL level
missing relations
Check if No HO if
High %
DL level
NO
NO
possible due to
1. congestion on
neighbors
2. High rate of outgoing
HO failures (follow HO
drop investigation)
Yes
HO per call
rate (>10%)
NO
High % DL quality
Check Frequency
plan
Check drive test
for overshooting
problem
Yes
Check for
unbalanced
path loss
(RMS)
Call drop HO
Problem detection:
1. High call drop rate on the cell > 1 %.
2. % HO drops > 30% of total dropped calls on the cell.
Investigation:
No
High HO out
execution failure
rate? >40 %
Yes
NO
Good % of better
condition (>40%)
NO
Yes
High
% ROC?
Yes
NO
Majority of
failure is
Inter BSC?
Yes
Check for
BCCH/BSIC duplication
in cell adjacencies
duplication in cell
adjacencies
inconsistency between
OMC-R and BSC
problems
unnecessary (Far) neighbor
declarations.