Alcatel Call Drop Analysis

Alcatel Call Drop Reasons

Call Drop_Radio

Call Drop_BSS
Call Drop
Call Drop_HO

Call Drop_Preemption

In Robi Network, Call Preemption Option is not present.

 Call Drop Due to Radio Problems
• This kind of call drop happens mainly of TCH drops in TCH established phase
due to radio link failure per TRX.
• This counter takes TCH in traffic or in signaling mode into account.
• Typically this fault occurs with:
1) A 48.058 CONNECTION FAILURE INDICATION message with a cause value
of "radio link failure" is received on Abis interface for a TCH channel (after
successful seizure).
2) A 48.058 ERROR INDICATION message is received on Abis interface and
leads to a loss of call. 
Call drop due to radio problems can be classified into:

1) Call_drop_DL_Interference
2) Call_drop_DL_Level
3) Call_drop_DL_Quality
4) Call_drop_Long_Distance
5) Call_drop_Other_Causes
6) Call_drop_Short_Distance
7) Call_drop_UL_Interference
8) Call_drop_UL_Level
9) Call_drop_UL_Quality
 Call Drop Due to DL Interference
• Amount of drops due to DL Interference is generally low in Network (<1%).
• In this case, TCH drops due to high interference level in DL.
• Typically the fault occurs with:
1) The same reason of call drop of radio problems.
2) The timer supervising the handover procedure expires during the intra-
cell TCH handover.
 Call Drop Due to DL Level
• Amount of drops due to DL Level is generally high in Network (15-20%).
• In this case, number of TCH drop occurs due to low level in DL.
• It typically occurs with:
1) The same reason of radio problem.
2) Whenever the timer supervising the handover procedure expires during
the inter-cell TCH handover.
3) Whenever the timer supervising the handover procedure on the serving
cell expires during the external TCH handover.
• Average down link signal strength could be analyzed by MRR report.
• HO should have to be checked and defined properly. ( Confirm 2nd tier
target cell)
• Unnecessary cable bending create power loss.
• Jumper cable should be at standard length (3m) as it’s high loss cable.
• Connectors should be Okay. (Degraded connector creates high loss)
• VSWR to be checked.
• In rural area, Submerged and forest area creates DL level drop mostly.
• Antenna blockage also creates DL level drop.
 Call Drop Due to Call DL Quality
• 5-10% drop happens due to this reason.
• DL interference, Overshooting, missing neighbor, handover failure etc
cause TCH drops due to Bad Quality DL.
• High count of drops in this category should be analyzed with Handover
performance.
• Report – Receive Quality Measurement per TRX will give idea on Quality
distribution in cells.
• Frequency plan can be reviewed in MapInfo.
• Swapped feeder cables can be an issue – relationship wise HO
performance analysis or Drive test can identify the issue.
• Overshooting can be identified via TA analysis from measurement report.
 Call Drop Due to UL Interference
• Amount of drops due to UL Interference is generally very low in the
network (0.02%).
• In this case, number of TCH drops due to high interference in UL.
 Call Drop Due to UL Level
• 0-5% drop occurs due to that reason.
• In this case, number of PCH drop occurs due to low level in UL.
• Poor handover performance, missing neighbor will also lead to drop in UL.
• If a site is not serving open area but having high ratio of Low SS UL drops
then report - Uplink-and-Downlink Balance Measurement per TRX can be
evaluated to estimate fault with cabling.
 Call Drop Due to UL Quality
• Amount of drops due to UL Quality is the highest in the network (20-25%).
• When drops due to this category is high in MRP network frequency & HSN
plan must be checked. And, in most cases a distant interferer causes drops due
to Bad Quality in UL.
• In SFH network, conservative MS Power control may cause high amount of Bad
Quality UL drops with Traffic increase or in congestion scenario.
• For MRP network, report - Interference Band Measurement per TS analysis
would give idea on frequency plan – ratio of ICM band 3-5 (%) should be high
for cells with Bad Quality UL drops.
• Interference from CDMA/external sources may also cause Bad Quality UL
drops – when no reasons can be identified – external interference can be
suspected.
• BTS alarm, TRX alarm, RX alarm should have to be checked & rectified.
• Antenna performance should have to be checked.
• Combiner performance should have to be checked.
• All types of physical cables & connectors should have to be checked.
• Antenna partial blocking should have to be removed. ( At city now bill board
blockage crate it mostly)
• Cell and CHGR definition should have to be checked at all active TRXs
 Call Drop Due to other causes
• 8-10% drop occurs due to that reason.
• A drop did not exceed thresholds of any Radio parameters (TA, Qual, SS)
are categorized as other reason drops. Sudden appearance of Log normal
fading may contribute drops due to other reason.
• In addition, counters related with Equipment faults, Abis terrestrial link
failure etc can be used to identify Drops due to other reason.
• HW alarm, E1 SES/ES can be checked to identify drops due to other
reason.
• If no alarm is found then replace the HW.
• Immediate Blockage, High raise buildings area create Sudden drop.
• Cell MAIO value should have to be checked.
• TRX configuration should have to be checked.
 Call Drop Due to Long and Short Distance
• These two features are not available in the network.
• Call drop due to short and long distance occurs due to short and long
distance between MS and BS distance respectively.
 Call Drop Due to BSS Problems
• In this case, number of TCH drop occurs due to system problem.
• It can be classified into two categories:
1) Call Drop Due to Internal BSS Failure.
2) Call Drop due to Remote Transcoder Failure.
 Call Drop Due to BSS Internal Failure
• 0-5% of drop occurs due to this reason.
• It typically occurs with:
1) Whenever a 48.058 ERROR REPORT message with a cause value of
"OandM intervention" is received on Abis interface after TCH seizure and leads
to a loss of call.
2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with a cause value
of "message sequence error" is received on Abis interface after TCH seizure
and leads to a loss of call.
3) Whenever a LAPD failure is reported to the Layer 3 of the BSC (for an RSL
supporting a TCH transaction after successful TCH seizure) and leads to a loss
of call
4) Whenever a TCH call release is initiated by the BSS OandM FAULT
MANAGEMENT application part or by the BSS TELECOM application part as the
result of a system defense action which may be due to BSS equipment failures
external to the BSC (e.g. RSL failure or CU recovery failure), or due to BSC
internal hardware problems (e.g. TCU failure or DTC failure) or due to BSC
internal software problems (e.g. inconsistencies detected between software
modules or lack of software resources (memory, timer reference, file
reference...) or communication problems between different processor
boards).. 
Call Drop due to Remote Transcoder Failure

• 10-15% of drop occurs due to this reason.

• In this case, number of TCH (in HR or FR usage) drops in TCH established
phase due to remote transcoder failures (per TRX).
• The counter is incremented whenever a 48.058 CONNECTION FAILURE
INDICATION message with cause "Remote Transcoder Failure" is received
on Abis interface for an established TCH connection.
• The BSC considers a TCH connection as "established" once a 44.018
ASSIGNMENT COMPLETE message (in case of normal assignments or an
internal intra-cell handovers) or a 44.018 HANDOVER COMPLETE message
(in case of an internal inter-cell incoming HO or an external inter-cell
incoming HO) has been received for the TCH connection.
 Call Drop Due to Handover
• 13.76% of drop occurs due to this reason.
• Number of TCH drops during the execution of any TCH outgoing handover,
per TRX.
• There are 4 types of handover:
1) Inter-cell TCH handover: whenever the timer supervising the handover
procedure expires.
2) External TCH handover (2G -> 2G): whenever the timer supervising the
handover procedure on the serving cell (T8) expires, except if a 48.008
CLEAR COMMAND with "normal event/call control" cause was received
from the MSC, leading to a normal call release. In such a case, the
handover is considered as successful.
3) Intra-cell TCH handover: whenever the timer supervising the handover
procedure expires.
4) 2G -> 3G HO: whenever the timer supervising the 2G-3G handover
procedure on the serving cell expires, except if a 48.008 CLEAR
COMMAND with "normal event/call control" cause was received from the
MSC, leading to a normal call release. In such a case, the 2G->3G
handover is considered as successful. 
Reports required for TCH Drop RCA
• Call drop measurements per cell
• TCH call fail per cell
• Uplink-and-Downlink Balance Measurement per TRX
• Radio Link Failure measurement per TRX
• Receive Quality measurement per TRX
• TCHF receive level measurement per TRX
• TCHH receive level measurement per TRX
• GSM Cell to Cell Incoming HO measurement
• GSM cell to cell Outgoing HO measurement
• MR measurement upon HO per cell
• Channel seizure measurement per TRX (Most important)
• Number of MR based on TA per TRX
 Identifying Bad cells
KPI Threshold KPI Threshold

Load on PCH > 40% Call Drop rate ( Drop count at >1%
BH< 20)
RACH Success rate <85%
Incoming HO to Assignments >50%
MTC/MOC ratio >30%
Outgoing HO to Assignments >50%
SMS >5%
HOSR <96%
Load on AGCH >40%
HO reversion rate >4%
SDCCH seizure for Location >35%
Update DL Strength HO ratio >5%
MHT of SDCCH >10%

SDCCH Congestion >0.5%

CSSR <96%