TCH assign failure congestion

 Problem detection:
 TCH assign. Congestion max. > 2 % (Critical , action needed)

 TCH Load BH (Erlang / capacity ) > 90 % (forecast)

 Investigation:

Check for hardware availability by

Any TRXs
comparing: Yes Report to BSS support
down or not
RTCH_nb (TCRRN) with carrying
team
RTCH_available_avg (TCAVAN)
(TCAVAN) traffic?

NO

Check through thematic map

NO Any neighbor
 TCH load BH on cell neighbors. Yes
site(s) down
 HO Inc congestion on neighbors.
not carrying
traffic?
 Check better condition parameters for each
couple.
 Check High HO Inc execution failure on
neighbors, if yes  follow same investigation in
call drop HO sheet.
Check with RNP if  Check through drive test (RMS) coverage for
All neighbors
neighbors
are loaded NO planned coverage Yes serving loaded cell vs. neighbor free cell.
(> 80%) + High overlap with  Antenna optimization needed?
Inc HO neighbors is sufficient  Hardware check needed?
con
con esti
estion
on for smooth HO flow.

Yes
NO Traffic sharing
 Enable FDR on serving cell
 Request for upgrades,  Enable Traffic HO for each couple and adjust
Calculate # of combiners needed and check with Densification sites needed relevant parameters according to drive test
RNP if there will be no coverage problem if analysis. (or leave default values according to # of
additional combiner is used TRX)
 Request for Densification sites  RNP  Enable Fast traffic HO, but monitor HO/call
rate and call drop HO specially for cells with
many inter BSC adjacencies
SDCCH drop rate
 Problem detection:
High SDCCH drop rate > 0.5 %
 Investigation:

BSS drop > Radio drops HO drops >

NO NO
40% of total > 40% of 40% of total
drops total drops drops

Yes
Yes
Yes
Check for Extreme queueing Situation
i.e.:
 RTCH_assign_queued_rate >50%? High TCH Same
 Check TRX carrying SD  T11 is set to values higher than Yes investigation
call drop HO
TS for alarms default ( > 6 seconds) ? should be
 High SD duration average (> 5 s) followed
 Check TCU handling TRX
with SD TS for alarms

 Reset TCU
Yes NO
Extreme
queueing
?
 Disable SDCCH HO,
Reduce queuing
 Check if TRX carrying SD is but with careful monitor of
 Solve TCH blocking prob.
problematic , if Yes move SD TS to NO SD drop radio
(refer to TCH congestion
another good TRX
solving sheet)
 Move SDCCH TS to
 Check value of cell_reselect_hyst, see if another TRX preferably
NO High TCH  Reduce T11 value (TCH
it was set previously to high values (> 6db) handled by different TCU
drop radio congestion should be monitored)
(to reduce # of LU, but can increase SD
Drop)
 Enable SD HO
Reduce averaging window
 LU procedure leads to higher duration
Yes Reduce HO margin (optional)
on SD (4s). Apply # LU reduction
procedure in SDCCH Congestion sheet Call drop radio investigation
should be followed
SDCCH assign failure congestion
 Problem detection:
 SDCCH assign. congestion > 0.5 %

 SDCCH Load BH (Erlang / capacity ) > 90 %

 Investigation:

High
NO Yes Check SDCCH traffic model
signaling
for split of services
load? > 4

 SDCCH capacity is not

optimized.
High % LU (> 50%) High % other services:
Action: a) IMSI attach
 Recalculate SD/TCH time slots
b) IMSI detach
needed using traffic model to
 Check HO flow to study if cell needs to c) SMS
reach optimum situation.
be downtilted to reduce overlap with d) Supplementary
neighbors in different LAC services
 Check the value of
Action:
BTS_Q_LENGTH:
 Increase cell_reslect_hyst on LAC 1-Increase SD capacity if
for values > default
border cells to reduce # of LU (monitor of possible:
2 TRX 4 TRX 6 TRX SDCCH drop radio is necessary)  Consider TCU load
4 6 10  Consider TCH blocking
Check % RTCH requests queued:  Check with architecture the possibility 2- Make sure all neighbor
high percentage (> 40%) can lead to re-design LAC plan to minimize as relations are defined handover
to SDCCH resources blocking for much as possible LU and reselection
T11 period of time. 3- Use the parameter
 Check value of T3101 and see if it is set cell_reselect_offset to increase
to default value neighbor’s re-selection.
4- Densification site – Request
Increase SD capacity if possible: for RNP study.
 Consider TCU load
 Consider TCH blocking

Signaling load = SDCCH requests / TCH requests

Call drop radio
 Problem detection:
1. High call drop rate on the cell > 1 %.
2. % Radio drops > 40% of total dropped calls on the cell.
 Investigation:

No Yes
HO per call
rate (>10%)

Yes Densification NO Yes

Isolated Hardware
sites are needed
cell Problem

Check HO Report to
No causes BSS team

 Check adjacencies for Yes NO Check for

missing relations High % High % unbalanced
UL level DL level path loss
 Check if No HO if NO (RMS)
possible due to
NO Yes
1. congestion on
neighbors
2. High rate of outgoing High % DL quality High %UL interference
HO failures (follow HO  Check Frequency & quality *Check for coverage
drop investigation) plan  Check for antenna, problems (holes)
 Check drive test feeder or connections prob. *Check missing
for overshooting  Check external interferer neighbors
problem (idle interference)
 UL level threshold

HO per call rate = number of “outgoing Handovers success / TCH seizures”

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 Yes

execution failure
rate? >40 %

Identify critical pair of

cells, (with Out HO
drop > 5 %) using NO
Type 26 (on demand Majority of Yes
counter) failure is
Inter BSC?

 Check for  Check for BCCH/BSIC

*Check better conditions BCCH/BSIC duplication duplication in cell
parameters. in cell adjacencies adjacencies
Good % of better NO *Check for severe
condition (>40%) interference on serving cell  Check for database  For neighbors in different
* Check for coverage inconsistency between OMC-R , check if relation is
continuity OMC-R and BSC defined correctly (external
cells)
Yes
 Check DL Qual / UL Qual  Check for synchronization
on target cell to locate problems
High interference problem.
% ROC?  Check DL Lev /UL Lev on
 Check neighbor plan for
Yes
unnecessary (Far) neighbor
target cell for coverage problem
declarations.

NO

 Check DL Qual / UL Qual on both

serving & target cell to locate
interference problem.
 Check DL Lev /UL Lev on both
serving & target cell for coverage
problem