Scribd
Upload
44 views

High in Call Drop Rate

The document provides steps to analyze the root cause of high call drop rates on a WCDMA network, including checking for faulty alarms, performance issues, path loss problems, neighbor cell interference, core network parameters, and physical channel failures that could be contributing to call drops. Key areas to examine are radio parameters, neighboring cells, interference, synchronization, handovers, power levels, and alarms on the different network elements. The goal is to identify the main failure contributor whether it is issues with the radio network, core network, or individual network elements.

Uploaded by

Deepak Kashyap
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
44 views

High in Call Drop Rate

The document provides steps to analyze the root cause of high call drop rates on a WCDMA network, including checking for faulty alarms, performance issues, path loss problems, neighbor cell interference, core network parameters, and physical channel failures that could be contributing to call drops. Key areas to examine are radio parameters, neighboring cells, interference, synchronization, handovers, power levels, and alarms on the different network elements. The goal is to identify the main failure contributor whether it is issues with the radio network, core network, or individual network elements.

Uploaded by

Deepak Kashyap
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

High in call drop rate - - WCDMA (Nokia)

1. Check high call drop cells and its neighbouring cells of any faulty alarms
2. Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS, Iur, S, !"C# $ Ser%ices &'
!S!(")*+
,. Check S-. /0I if performance 1 +)2 ( leads to radio failure#
Check if cells are at !"C border (check Iur capacity and S!"C relocation problem#
3etect badly performing neighbours using -. success rate per ad4acency counters (1)1,#
-igh incoming -. failure rate in all ad4s $ check sync alarms
(ssessing neighbor list plan and %isuali5ation check 6ith map
7%aluate -. control parameters and trigger threshold
8. Check IS-. /0I if !T IS-. 1 +)2 or "!T 1 9)2 (leads to radio failure#
Check missing neighbour (1)1:#, ;S fre<uency plan neighbour !"C and SC database consistency audit,
check alarm of reference clock in ,; or in 2;, check 2; TC- congestion
Check !!C 3rop IS-. !T = "!T
:. 3etecting 3> or ?> path loss problem if !(B drop due to radio (dominant call
drop cause ' :)2#
Check ?> >ost (cti%e /0I from Iub counters (acti%e >1 synchroni5ation failure# to check ?>=3> path loss problem
Check (S? failure rate (?"S?C@(S?# 6hich link to ". !7S0."S7 A!. !>C
apping radio failures 6ith TB po6er and C0IC- related parameters &' C0IC-To!ef!(B.ffset, 0TC30C- (C
Check Call reestablishment timer &' T,1:
7cno distribution for bad co%erage issue (1))*C,9&1))*C8*#
D. Check core net6ork parameter setting if !(B@(CT@A(I>@CCC@I?
Check SCC0 S;S"=!"C Iu0S Tias=Tiar if !(B@(CT@A(I>@B(C/;@I?
*. If high !(B@(CT@A(I>@CCC@BTS
Check if any BTS faulty alarm (*D:, cell faulty alarm#
If no alarms, C.C. detach=attach
9. If high !(B@(CT@A(I>@CCC@S
Check physical channel reconfiguration failure rate (IA-., IS-., code optimisation#

You might also like