Call Drop Rate (explanation):

As per analysis and comparison of Mobily definition formula with industry leading practices below
mentioned interfaces drops are missing in the Formula, hence explanation and importance of those
interfaces are explained in details.

Missing interfaces:

1- TCH_TR_FAIL [Transcoder Drops]

2- TCH_A_IF_FAIL [A-interface Drops]
3- TCH_ABIS_FAIL [Abis-Drops]

Counter
Explanation
Name
TCH_ABIS_FAIL Number of TCH transactions that are ended because of a failure in the Abis interface.
TCH_TR_FAIL Number of TCH transactions that are ended because of a transcoder failure.
TCH_A_IF_FAIL Number of TCH transactions that are ended because of a failure in the A interface.

Factors that Affect Call Drop Rate:

According to user complaints and network optimization experience, the major factors that affect the
TCH call drop rate are as follows:
Hardware failure (BTS, TRX, TS faulty)
Transmission problem (Abis & A-ter interface)
Transcoder Problem (A-interface issue, TRAU issue)
Version upgrade (BTS SW upgrade, BSC upgrade)
Parameter setting
Intra-network and inter-network interference
Coverage problem
Antenna system problem
Imbalance between uplink and downlink
Repeater problem

TCH Drop Radio:

MS BTS BSC MSC

Alerting Connection Phase or Communication : at any time

Radio Problem CONNECTION FAILURE INDICATION

(cause : radio link failure)
CLEAR REQUEST
(cause : radio interface failure)

TCH Drop BSS:

MS BTS BSC MSC

Alerting Connection Phase or Communication : at any time

Radio Problem CONNECTION FAILURE INDICATION

(Remote transcoder failure)
CLEAR REQUEST
(Equipment failure)
 Transcoder reported problem
Abis transmission Problem: Microwave, Microwave antenna, fixed line problems.
Problem on TC boards (hardware problem)

GSM Architecture:

Transcoder Function:
The primary function of TRAU is to convert the 16kbps (inc signaling) GSM speech channels to
64kbps PCM channels in the uplink direction and the reverse in the downlink direction. The
reason this process is necessary is because MSCs only switch at the 64kbps channel level.
Case 1, TRAU at BTS:
If TRAU installed at the BTS, each 16kbps GSM channel would need to be mapped to its own 64kbps
PCM channel. This result in 75% of the Transmission bandwidth being wasted across both (BTS-BSC) and
A(BSC-MSC) interface.

Case 2, TRAU at BSC:

If the TRAU is installed at the BSC, 16kbps GSM channel mapped to 64kbps at the A(BSC-MSC) interface,
which increases the requirement of Transmission trunks.

Case 3, TRAU at MSC:

If the TRAU is placed at the MSC, as is generally the case in most of the networks, a multiplexer can be
placed at the BTS which enables 4x16kbps GSM channel to be multiplexed onto one configuration, only
at arrival at the MSC is the 16-64kbps channel conversion necessary thereby maximizing the efficiency of
transmission medium by increasing GSM channel throughput per PCM 2048 bearer from 30 to 120
channels.

A-Interface:
Its an interface between NSS (comprises of MSC and associated register) & BSS (comprises of BSC and
several BTSs).

Abis-Interface:
Its an interface between BSC and BTSs within the BSS.

Conclusion:
Hence if we need to monitor E2E KPIs for Mobily network then we have to consider the missing
interfaces drops in the Mobily definition formula.

Call Setup Success Rate (Explanation):

In CSSR formula as per Mobily Definition we are not taking the Immediate Assignment part even we
are monitoring SD & TCH blocking as a separate KPI which may not give us the actual E2E performance
of the KEY network KPI i.e. CSSR.

KPI formula:
BSS Call Setup Success Rate = (([Immediate Assignment Success Rate]*[TCH Assignment Success
Rate])*(1-[SDCCH Drop Rate]))*{100}

The CSSR combines 3 other KPIs:

- Immediate Assignment Success Rate = ([Call Setup Indications (Circuit Service)]/[Channel Requests
(Circuit Service)])*{100}
- TCH Assignment Success Rate = ([Successful Assignments]/[Assignment Requests])*{100}
- SDCCH Drop Rate = ([Call Drops on SDCCH]/[Successful SDCCH Seizures])*{100}
Analysis for each Part of Formula:
1. Each of the 3 component-KPIs will affect CSSR:
- Low Immediate Assignment Success Rate will decrease CSSR [This Part is missing in Mobily Formula]
- Low TCH Assignment Success Rate will decrease CSSR
- High SDCCH Drop Rate will decrease CSSR

Basic Immediate Assignment signaling procedure.

If Immediate Assignment failures are due to no channel available (point A in Figure 2), this
means that there is SDCCH congestion.
If Immediate Assignment failures are due to channel activation failure or channel activation
timeout (points B, C in Figure 2) check hardware/software alarms.

Conclusion:

Hence if we need to monitor E2E KPIs for Mobily network then we have to consider the missing
Immediate assignment (SDCCH) counters in the Mobily definition formula.
 - Call Drop Rate Formula [As per Mobily Definition]

100*DECODE((TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL
+TRAFFIC.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+TRAFFIC.TCH_NETW_ACT
+TRAFFIC.TCH_ACT_FAIL_CALL
+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+SERVICE.TCH_NORM_RELEASE), 0,
0,(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT
+TRAFFIC.TCH_BCSU_RESET+TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABI
S_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD)/(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+
TRAFFIC.TCH_BCSU_RESET+TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+SERVICE.TCH_NORM_RELEASE))

- Call Drop Rate Formula [As per industry leading Practices] , differences highlighted in blue:

100*DECODE((TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+
TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL+TRAFFIC.TCH_A_IF_FAIL+
TRAFFIC.TCH_ABIS_FAIL+SERVICE.TCH_NORM_RELEASE), 0, 0,(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+
TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+TRAFFIC.TCH_TR_FAIL+
TRAFFIC.TCH_A_IF_FAIL+TRAFFIC.TCH_ABIS_FAIL)/(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+
TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+TRAFFIC.TCH_TR_FAIL+
TRAFFIC.TCH_A_IF_FAIL+TRAFFIC.TCH_ABIS_FAIL+SERVICE.TCH_NORM_RELEASE))

From: Imran Ali - DEL

Sent: Thursday, November 26, 2015 12:24 PM
To: Saleh Abdullah S. Fayyad
Cc: AbdulRehman Shaikh; Bilal El-Skafi; Sohail Atique - DEL; Noel P. Doller
Subject: RE: Formulas Benchmarking

Dear Saleh,

In existing formula it only contains the OLD HO counters, please see the definition below of both the
counters.

Counter Name Explanation

TCH_ABIS_FAIL_OLD Number of TCH transactions ended because of a failure in the Abis interface on the source channel during a TCH HO.
TCH_ABIS_FAIL Number of TCH transactions that are ended because of a failure in the Abis interface.

TCH_TR_FAIL Number of TCH transactions that are ended because of a transcoder failure.

TCH_TR_FAIL_OLD Number of TCH transactions that are ended because of a transcoder failure on the source channel during a handover on a TCH

Legends:
missing
exist in formula.

However for CSSR formula as explained you in details this morning Mobliy Definition formula doesnt
contains the SD part.

--
Thanks and Regards
Imran Ali

From: Saleh Abdullah S. Fayyad

Sent: Thursday, November 26, 2015 10:51 AM
To: Imran Ali - DEL
Cc: AbdulRehman Shaikh; Bilal El-Skafi; Sohail Atique - DEL; Noel P. Doller
Subject: RE: Formulas Benchmarking

Dear Imran
As a quick scan for the formulas of drop rate I can see Abis and transcoders failure are part of existing
formula, is there any duplication in the formula that you did (A int is not included)

Also for CSSR

Can you please provide the logic that you are trying to emphases

Best Regards

Saleh A. Fayyad
Network Performance Management

2nd Flr. Sulimaniah Bldg CT5, Riyadh

Saudi Arabia
Tel: +96656031 5175
Mobile: +966 546655321
email: s.fayyad@mobily.com.sa

From: Imran Ali - DEL

Sent: Tuesday, November 24, 2015 2:22 PM
To: Saleh Abdullah S. Fayyad
Cc: AbdulRehman Shaikh; Bilal El-Skafi; Sohail Atique - DEL
Subject: Formulas Benchmarking

Dear Saleh,

As per my discussion with you last week regarding formulas benchmarking with industry leading
practices and looking each formula from E2E network performance perspective.
We have found some counters missing at CSSR and CDR formulas in order to view the network end to
end KPI/performance.

Please have a look into this, tomorrow we will be in CT5 in order to conclude this subject.

Call Drop Rate (explanation):

As per the current CDR formula in Mobily there is NO core counters included which may not give us the
actual E2E performance of the network.

- Call Drop Rate Formula [As per Mobily Definition]

100*DECODE((TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL
+TRAFFIC.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+TRAFFIC.TCH_NETW_ACT
+TRAFFIC.TCH_ACT_FAIL_CALL
+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+SERVICE.TCH_NORM_RELEASE), 0,
0,(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT
+TRAFFIC.TCH_BCSU_RESET+TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABI
S_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD)/(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+
TRAFFIC.TCH_BCSU_RESET+TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+SERVICE.TCH_NORM_RELEASE))
 - Call Drop Rate Formula [As per industry leading Practices] , differences highlighted in blue:

100*DECODE((TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+
TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL+TRAFFIC.TCH_A_IF_FAIL+
TRAFFIC.TCH_ABIS_FAIL+SERVICE.TCH_NORM_RELEASE), 0, 0,(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+
TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+TRAFFIC.TCH_TR_FAIL+
TRAFFIC.TCH_A_IF_FAIL+TRAFFIC.TCH_ABIS_FAIL)/(TRAFFIC.TCH_RADIO_FAIL-
TRAFFIC.TCH_REL_DUE_RAD_FAIL_PH_2_3+TRAFFIC.TCH_RF_OLD_HO+TRAFFIC.TCH_LAPD_FAIL+TRAFFI
C.TCH_BTS_FAIL+TRAFFIC.TCH_USER_ACT+TRAFFIC.TCH_BCSU_RESET+
TRAFFIC.TCH_NETW_ACT+TRAFFIC.TCH_ACT_FAIL_CALL+TRAFFIC.TCH_ABIS_FAIL_OLD+TRAFFIC.TCH_TR
_FAIL_OLD+TRAFFIC.TCH_TR_FAIL_OLD+TRAFFIC.TCH_TR_FAIL+
TRAFFIC.TCH_A_IF_FAIL+TRAFFIC.TCH_ABIS_FAIL+SERVICE.TCH_NORM_RELEASE))

Call Setup Success Rate (Explanation):

In CSSR formula we are not including the SD & TCH blocking even we are monitoring SD & TCH blocking
as a separate KPI which may not give us the actual E2E performance of the network.

- Call Setup Success Rate Formula [As per Mobily Definition]

[1 - SDCCH_DROP_LU_EXCLUDED (C1226)/SDCCH_ESTAB_SUCC_LU_EXCLUDED (C1225)] *

TCH_NEW_CALL_ASSIGN(C57033)/TCH_CALL_REQ(C1026)

- Call Setup Success Rate Formula [As per Mobily Definition]

100*(DECODE(TRAFFIC.SDCCH_SEIZ_ATT,0,0,1-(TRAFFIC.SDCCH_BUSY_ATT-
TRAFFIC.TCH_SEIZ_DUE_SDCCH_CON)/
(TRAFFIC.SDCCH_SEIZ_ATT))*DECODE((TRAFFIC.SDCCH_ASSIGN+TRAFFIC.SDCCH_HO_SEIZ),0,0, 1-
(TRAFFIC.SDCCH_RADIO_FAIL+TRAFFIC.SDCCH_RF_OLD_HO+TRAFFIC.SDCCH_USER_ACT+TRAFFIC.SDCC
H_BCSU_RESET+TRAFFIC.SDCCH_NETW_ACT+TRAFFIC.SDCCH_BTS_FAIL+TRAFFIC.SDCCH_LAPD_FAIL)/
(TRAFFIC.SDCCH_ASSIGN+TRAFFIC.SDCCH_HO_SEIZ))*DECODE((TRAFFIC.TCH_NORM_SEIZ+HO.MSC_I_S
DCCH_TCH_AT+HO.BSC_I_SDCCH_TCH_AT),0,0,
(TRAFFIC.MS_TCH_SUCC_SEIZ_ASSIGN_CMPLT+HO.MSC_I_SDCCH_TCH+HO.BSC_I_SDCCH_TCH)/
(TRAFFIC.TCH_NORM_SEIZ+HO.MSC_I_SDCCH_TCH_AT+HO.BSC_I_SDCCH_TCH_AT)))

Regards,
Imran Ali