Beruflich Dokumente
Kultur Dokumente
December 2011
Preliminary Voice performance report
A and IuCS interfaces: focus on call drop
Order acknowledgement: AR20001119
This document is the property of Astellia and can not be reproduced in any form or conveyed to a
third party without the prior written permission of Astellia.
All trademarks, service marks, registered trademarks or registered service marks mentioned in this
document are the property of their respective owners.
Written by
Yann LE GAL / Jerme JAMIN
ASTELLIA
Telecom Engineer
13/12/2011
Name
Company
Job title
Date
Signature
Reviewed by
Eric GATEL
ASTELLIA
Consulting Project Manager
13/12/2011
Recipients
Telenor
-
Peter FEKETE
Lszl TOBIAS
Bela NAGY
Jerme JAMIN
Yann LE GAL
Jean-Pierre THOMAS
Enrico BASSO
Eric GATEL
Astellia :
Releases
Release
A
Date
13/12/2011
Author
Yann LE GAL
Jrme JAMIN
Purpose
Creation
This document is the property of Astellia and can not be reproduced in any form or conveyed to a
third party without the prior written permission of Astellia.
All trademarks, service marks, registered trademarks or registered service marks mentioned in this
document are the property of their respective owners.
1.
1.
2.
3.
Page: 3 / 33
TABLE OF CONTENTS
2.
Page: 4 / 33
INTRODUCTION
TELENOR HUNGARY has selected Astellia to perform an E2E audit in order to evaluate the quality of
performances of its both 2G &nd 3G networks.
Objective of this audit is to assist TELENOR HUNGARY in improving its 3G, 2G and 2.5G network after the
swap to ZTE. Despite good results providing by ZTE OSS counters, Telenor is now facing an increase of the
customer complaints
This first preliminary report focuses on the call drop part, based on A and IuCS interfaces,. An additional
analysis for handovers is also included in this report.
This audit is based on the analysis of raw data captured through Astellia probe on A and IuCS interfaces,
for the BSC ZBSC51 and RNC ZRNC11.
Node name
Capture Begin
Capture End
Duration
Comments
Capture of A and IuCS
Budapest
ZBSC51
ZRNC11
25/11/2011
17:00
27/11/2011
23:59
55H
3.
3.1.
Page: 5 / 33
3.1.2.
Page: 6 / 33
This graph displays the call drop rate. On the left Y-axis you have the call drop rate and on the right Y-axis you can see the number of CS voice calls.
The call drop efficiency is good. During the busiest periods of the day the call drop rate is around 0.8% if we dont take User causes into account.
The main source of drop inefficiency is due to NSS/CN causes and more details about the causes are provided on the next pages.
3.1.3.
Page: 7 / 33
This graph displays the call drop causes. On the left Y-axis you have the percentage of RNS call drop causes and on the right Y-axis you can see the number of
established calls.
The Call Drop due to RNS causes is lower than 0.3%. This value is constant during the whole day. The two main causes are Failure in the Radio
Interface Procedure and Radio Connection With UE Lost.
Page: 8 / 33
This graph displays the call drop causes. On the left Y-axis you have the percentage of CN call drop causes and on the right Y-axis you can see the number of
established calls.
The Call Drop due to NSS/CN causes is around 0.4%. This value is constant during the whole day. The two main causes are Destination Out Of order
Page: 9 / 33
This graph displays the top 40 cells with highest call drop rates. On the left Y-axis you have the percentage of call drop causes and on the right Y-axis you can see
the number of established calls (filter > 50 occurrences).
The worst cell is the SAI 2902 with around 15.5% of call drop rate. Its interesting to investigate each cell in order to understand high call drop rates.
Page: 10 / 33
When the mobile goes out of radio coverage the connection is released with this cause.
No specific cell is concerned.
Page: 11 / 33
This graph displays the 40 cells having highest cause radio interface failure drop rate (RIF). On the left Y-axis you have the call drop rate and on the right Yaxis you can see the number of established calls (>50 occurrences).
If we focus on the Failure in the Radio interface procedure, we can see the following call flow showing the loss of the radio link during the call.
Page: 12 / 33
When the radio connection is not good enough to maintain the communication, the node B when one single radio link is available will release the
connection with the Mobile.
No specific cell is concerned.
Page: 13 / 33
Page: 14 / 33
In the last 2 lines, the calling party A has changed of cell; the customer A is now in cell 4853 and the calls is a success. So bad radio quality is
responsible of such a message for the mobile A. For B this cause is the consequence of the loss of the radio link for the side party.
This cause is generated when a radio problem on the other side during the call.
3.2.
Page: 15 / 33
3.2.2.
Page: 16 / 33
This graph displays the call drop rate. On the left Y-axis you have the call drop rate and on the right Y-axis you can see the number of established calls.
The call drop efficiency is good. During the busiest periods of the day the call drop rate is lower than 1.5%.
The main source of drop inefficiency is due to NSS causes and more details about the causes are provided on the next page.
3.2.3.
Page: 17 / 33
This graph displays the call drop causes. On the left Y-axis you have the percentage of call drop causes and on the right Y-axis you can see the number of
established calls.
Around 0.3% of the inefficiency is due to the causes Radio Interface Failure (RIF) and Radio Interface Message Failure (RIMF), in other words due to
bad radio condition (classified as BSS inefficiency).
It is also important to note than 0.3% of the established calls are dropped due to the cause Destination Out Of Order (classified as NSS inefficiency)
and 0.5% of the established calls are dropped due to the cause Normal Unspecified (classified as a NSS inefficiency).
Page: 18 / 33
CLREQ Radio Interface Failure (RIF) and Radio Interface Message Failure (RIMF)
This graph displays the 20 cells having highest radio call drop rate (RIF & RIMF). On the left Y-axis you have the call drop rate and on the right Y-axis you can see
the number of established calls.
The highlighted cells above have an important call drop rate and we recommend checking the global radio condition for these cells. Deeper Abis
investigations could be useful to understand the issue.
Analysing Outgoing handover causes, Astellia KPI could help to focus on the radio problem.
Page: 19 / 33
Here are more details about radio condition based on Outgoing handover causes:
Causes of outgoing handover
Cell
Nb of established calls Drops RIF+RIMF(%)
dujvatanq8_3512_15498
2139
2,9453
UQ
2,69%
US
2,78%
DQ
0,15%
DS
0,38%
BC
94,00%
kvolwest3_3511_7823
dujvatan3_3512_15493
721
882
2,91262
2,60771
2,52%
1,46%
9,63%
1,01%
5,45%
1,34%
6,85%
2,10%
75,54%
94,09%
kvolwest1_3511_7821
603
2,32172
5,94%
20,18%
8,66%
4,85%
60,37%
biatorbag2_3511_21012
ormezo2_3511_1882
1249
518
2,08167
1,5444
1,34%
1,73%
2,77%
1,15%
1,07%
0,93%
6,66%
2,18%
88,16%
94,00%
rokales1_3511_7471
1050
1,2381
7,16%
8,84%
4,27%
10,24%
69,49%
dujvaros2_3512_15112
kikoto7_3512_7947
725
646
1,10345
0,928793
5,23%
7,40%
7,53%
10,91%
7,81%
4,46%
6,13%
1,44%
73,28%
75,80%
bfokwest3_3511_5793
soroksmil2_3512_7322
761
563
0,919842
0,888099
4,45%
1,49%
7,80%
2,38%
3,67%
11,38%
8,74%
6,60%
75,31%
78,12%
erdeszak1_3511_61181
menyecsk2_3511_6812
borstesc1_3511_41471
571
916
581
0,875657
0,873362
0,860585
3,16%
1,35%
1,34%
2,03%
0,40%
0,93%
4,97%
2,04%
1,48%
14,15%
0,78%
2,58%
75,69%
95,42%
93,67%
szhalwat3_3512_61233
2114
0,851466
4,37%
2,47%
4,52%
7,82%
80,43%
szoborpar1_3511_3381
budaors3_3511_21153
highwayq8_3511_1828
707
1071
601
0,848656
0,840336
0,831947
8,36%
3,32%
1,04%
2,30%
2,06%
3,17%
8,72%
1,62%
0,86%
8,83%
4,26%
3,10%
71,74%
88,71%
91,78%
m7m02_3511_41972
970
0,824742
2,64%
2,80%
4,89%
11,38%
78,29%
harbor3_3511_7563
981
0,815494
1,48%
10,47%
5,55%
9,06%
73,44%
Possible radio
problem
/
Radio signal strength
in both ways
/
Uplink strength
problem
Downlink strength
problem
/
Radio Quality and
Strength problem
Quality problem in
both ways
Uplink way problem
Radio strength
problem in both ways
Downlink problem
Downlink strength
problem
/
/
Quality problem in
both ways
Quality problem in
both ways
/
/
Downlink strength
problem
Radio strength
problem
Page: 20 / 33
During the conversation phase a disconnect message associated with the cause Normal Unspecified is sent from the MSC site.
The following pie show the state when the disconnect message is sent:
Here are some established calls CDRs which have been dropped with the cause Normal Unspecified:
Page: 21 / 33
Page: 22 / 33
During the conversation phase a disconnect message associated with the cause Destination Out Of Order is sent from the MSC site.
Here is an end to end procedure based on the A interfaces capture:
It was possible to match the outgoing and terminating procedures thanks to a specific feature implemented on your network illustrated below:
For terminating call procedures, the setup message contains the MSISDN of the calling and the called parties.
Page: 23 / 33
Here are the flow charts of the analyzed end to end case:
Calling party:
Called party:
3.3.
Page: 24 / 33
HANDOVERS
3.3.1.
Page: 25 / 33
Page: 26 / 33
Page: 27 / 33
Page: 28 / 33
next
page),
we
can
find
that
with
Page: 29 / 33
focus
on
preparation
phase
with
problem
of
During the 3G to 2G mobility, we can see a handover failure on the A interface with the cause NO RADIO RESOURCE AVAILABLE
o GSM resources are not available for the 3G call
So the mobile cant go to the 2G, a handover failure is sent to the CN with the cause nor resource available
The mobile must continue its communication on 3G but the Core Networks sends a DISCONNECT with the cause Normal clearing
o
Page: 30 / 33
Page: 31 / 33
The number of HO is quite important in Telenors networks. An interruption during the call can be suspected (An interruption of around 2s during the
communication can be estimated) and this high number needs explanation, bad radio threshold? Bad radio coverage? (Iub analysis could help for
better understanding)
We have around 0.9% of failure during the preparation phase.
Most of the problems during the preparation Phase are due to a lack of GSM resources.
The Call drop rate must be impacted by the couple Disconnect- Normal Clearing sends to drop the call when mobility fails. Investigation is
needed with the vendor to understand such behaviour.
Page: 32 / 33
The main cause of failure for the Completion phase is RANAP ReLOCation CANcel , cause: MISCellaneous UnspecifiedFailure
Page: 33 / 33
We observe around 0.7 % of failure during the Completion phase. Most of the problem is due to the cause unspecified. Additional investigation on
UTRAN/IUB is needed.