Ericsson Internal

SPEECH DROP CALL ANALYSIS 1 (13)

Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

Speech Drop Call Analysis

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 2 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

Contents
1 Introduction.........................................................................................3
2 Objective............................................................................................3
3 Counters:............................................................................................3
4 Procedure...........................................................................................5
4.1 Site intermittently down.......................................................................6
4.2 High drop rate due to missing neighbor:.............................................7
4.3 High drop rate due to Iur issue............................................................8
4.4 Uplink Interference case.....................................................................9
4.5 Faulty module Board case:...............................................................11

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 3 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

1 Introduction
One of the most important KPIs to maintain in any given network is the Speech Retainability rate. The
task of the optimization engineer is to troubleshoot the network to find the possible causes of the speech
drops and then to take action to bring the level of drops to the minimum possible

2 Objective
The objective of this document is to define a simple yet efficient walkthrough that goes step by step into
the analysis of the speech drop call through the statistical counters in order to reach the cause of the
drop and then to take the necessary action to avoid more drops in the future. Examples of some drop
call cases are presented below the procedure flowchart

3 Counters:
pmNoSystemrabReleaseSpeech: Number of system releases for CS Conversational
speech RABs. Includes AMR-NB, AMR-WB and AMR-NB Multi-rate RABs.
Incremented in the best cell in the active set.
Condition:
Incremented by one for each system release of a Speech RAB, due to a RANAP Iu Release
Command or RAB Assignment Request message.
A system RAB release has 'release cause' = anything except 'Normal Release', 'Successful
Relocation', 'Resource Optimization Relocation', 'User Inactivity' or 'release-due-to-UE-
generated-signaling-connection-release'.
Counter Type: PEG
Scanner: Primary (initial state = Active)
Context: SRNC, DRNC if IurLink:srncPmReporting = ON in SRNC
Counter is reset after measurement period: Yes

pmNonormalRabReleaseSpeech: Number of normal releases for CS Conversational

speech RABs. Includes AMR-NB, AMR-WB and AMR-NB Multi-rate RABs.
Incremented in the best cell in the active set.
Condition:
Incremented by one for each normal release of a Speech RAB, due to a RANAP Iu Release
Command or RAB Assignment Request message.

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 4 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

A normal release has 'release cause' = 'Normal Release', 'Successful Relocation', 'Resource
Optimization Relocation', 'User Inactivity', or 'release-due-to-UE-generatedsignalling-connection-
release'.
Counter Type: PEG
Scanner: Primary (initial state = Active)
Context: SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC
Counter is reset after measurement period: Yes

pmNoSysRelSpeechNeighbr: Number of system disconnections due to unknown measured

cell (missing neighbor relation) for CS Conversational speech RABs. Includes AMR-NB, AMR-
WB and AMR-NB Multi-rate RABs.
Incremented in the best cell in the active set.
Condition:
Incremented by one when a network initiated call is released for speech calls due to inability to
include an non-valid cell in the active set. The counter is incremented for the best cell in the
active set prior to the call release.
Counter Type: PEG
Scanner: Secondary (initial state = Active)
Context: SRNC
Counter is reset after measurement period: Yes

pmNoSysRelSpeechSoHo: Number of system disconnections due to Soft Handover action

for CS Conversational speech RABs. Includes AMR-NB, AMR-WB and AMR-NB Multi-rate
RABs.
Incremented in the best cell in the active set.
Condition:
Incremented by one when a network initiated call is released for speech calls due to inability to
include a non-valid or valid cell in the active set. The counter is incremented for the best cell in
the active set prior to the call release.
Counter Type: PEG
Scanner: Secondary (initial state = Active)
Context: SRNC
Counter is reset after measurement period: Yes

pmNoSysRelSpeechUlSynch: Number of system disconnections due to lost UL synch for

CS Conversational speech RABs. Includes AMR-NB, AMR-WB and AMR-NB Multi-rate RABs.
Incremented in the best cell in the active set.
Condition:
Incremented by one when the timer dchRcLostT expires and the RAB type is a CS
Conversational Speech 12.2 kbps RAB.
Note that the counter is applicable for CS Speech RAB and for Multi- RAB (Conversational
speech RAB).
Counter Type: PEG
Scanner: Secondary (initial state = Active)
Context: SRNC
Counter is reset after measurement period: Yes

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 5 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

Site is intermittently down or

has hardware problems 4YESProcedure
Contact front office or follow operator
Procedure to solve hardware problems

NO
NO Define Neighbours
pmNoSysRelSpeechNeighbr YES Check if distant
has a high value site is
Downtilit
overshooting YES Overshooting site
NO

Check if Iur has problems

pmNoSysRelSpeechSoHo
has a high value YES Check if neighbour sites have
enough capacity resources for
handover
NO

Improve coverage by tilting,

Poor coverage (bad CPICH YES azimuth change, CPICH power
Ec/No and/or bad CPICH increase, adding site. Change the
RSCP) parameters
usedFreqThresh2dEcno and
usedFreqThresh2dRscp and
NO SratSearch to make a 2G
handover earlier

YES If applicable, switch to another

Uplink Interference is high frequency to make sure that the
interference resource is external.
If this is the case, follow operator
NO procedure to remove the
interference

A large number of cells Try to find a common resource that is faulty ex

showing constant high speech YES module board, transmission link, MSC
drop rate

NO
/conversion/tmp/scratch/358795708.doc Follow operator procedure to solve the problem
Drops happening on the same YES
type of UEs
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 6 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

4.1 Site intermittently down

The counters to monitor are pmCellDowntimeAuto and pmCellDownTimeMan to know if the cell
is down:

Using MOshell, login to the node and type al to have the instant alarm on the RBS:

Nr of active alarms are: 1

===============================================================================
=================
Sever Specific Problem Cause Mo-Reference

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 7 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

===============================================================================
=================
Maj OpticalInterfaceLink_OpticalInterfaceLinkFailure equipment_malfunction OpticalInterfaceLink=1-
UL
>>> Total: 1 Alarms (0 Critical, 1 Major)

4.2 High drop rate due to missing neighbor:

Speech Drop Call

UCell Id Date pmNoSystemRabReleaseSpeech pmNoSysRelSpeechNeighbr rate drop calls due to missing neighbors %
11963 7/16/2009 10 9 0.08 90
11963 7/17/2009 7 5 0.06 71.42857143
11963 7/18/2009 5 5 0.08 100
11963 7/19/2009 4 2 0.11 50

Cell 11963 has undefined neighbours. When the Ec/No of the undefined neighbour is 6dB stronger than
the best cell in the active set, the call drops due to release connection offset.
It is important to check first if the undefined neighbour causing the drops is overshooting.
The maximum number of allowed neighbour relations per cell is 32. If adding a new relation is needed, it
is important to check if that limit is not reached. If it is reached, use the counters
pmRlAddAttemptsBestCellSpeech and pmRlAddSuccessBestCellSpeech to have data about the usage
of the already defined neighbour relations

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 8 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

4.3 High drop rate due to Iur issue

After P6 upgrade of a neighbouring RNC, the drops due to soft handover increased. This was due to a
misconfiguration in the Iur interface. After performing an RNC restart, the problem was solved

/conversion/tmp/scratch/358795708.doc
 Approved

-95.00
-90.00
-85.00
-80.00
-75.00
-70.00

-115.00
-110.00
-105.00
-100.00
4/17/2009 12.00
4/18/2009 21.00
6.00
15.00
4/19/2009 0.00

4.4
9.00
Ahmad El-Chidiac

18.00
4/20/2009 3.00
12.00

/conversion/tmp/scratch/358795708.doc
4/21/2009 21.00
Prepared (also subject responsible if other)

6.00
15.00
4/22/2009 0.00
9.00
18.00
4/23/2009 3.00

Impact of changing the frequency:

12.00
4/24/2009 21.00
6.00
15.00
4/25/2009 0.00
9.00
Checked

18.00
4/26/2009 3.00
12.00

UL Interference
4/27/2009 21.00
6.00
15.00
Uplink Interference case
No.

4/28/2009 0.00
Date

9.00
18.00
4/29/2009 3.00
12.00
Gaph last month of cell U012543
2009-07-20

4/30/2009 21.00
6.00
15.00
Ericsson Internal

5/1/2009 0.00
9.00
Rev

18.00
PA1

5/2/2009 3.00
12.00
5/3/2009 21.00
6.00
15.00
5/4/2009 0.00
SPEECH DROP CALL ANALYSIS

Reference

9.00
18.00
5/5/2009 3.00
12.00
5/6/2009 21.00
6.00
15.00
5/7/2009 0.00
9.00
18.00
9 (13)
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 10 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

-70.00

-75.00

-80.00

-85.00

-90.00 Change to 2nd Revert to old

Frequency Frequency
-95.00

-100.00

-105.00

-110.00
10.00

12.00
14.00
16.00

18.00

20.00
22.00

10.00
12.00

14.00
16.00
18.00
20.00

22.00

10.00
12.00

14.00

16.00
18.00
20.00
22.00
0.00
2.00

2.00
4.00

6.00

6.00

8.00
4.00
6.00
8.00

0.00

8.00

0.00
2.00
4.00
5/5/2009

5/6/2009

5/7/2009

UL Interference

REMARK: On the 6th of May the cell was retuned to the another carrier: 1930.1 Mhz 1935.1 Mhz On this
frequency no interference was present;

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 11 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

4.5 Faulty module Board case:

Using MOshell, login to the RNC node and type the command pmr to get the latest statistics for the
KPIs on RNC level:

Choose number 4 to have data on the different module boards:

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 12 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

Check if there is a particular module with high speech drop call rate. If yes then most probably the
module has a faulty board

/conversion/tmp/scratch/358795708.doc
 Ericsson Internal
SPEECH DROP CALL ANALYSIS 13 (13)
Prepared (also subject responsible if other) No.

Ahmad El-Chidiac
Approved Checked Date Rev Reference

2009-07-20 PA1

/conversion/tmp/scratch/358795708.doc