KPIs_SBS_BR_7

8/13/2019 KPIs_SBS_BR_7

http://slidepdf.com/reader/full/kpissbsbr7 1/151

Siemens

Information

System

PM: SBS Key Performance Indicators(optional issue)

A30808-X3247-B912-2-7618

Date : 18.10.2004Version : BR7, version 2

8/13/2019 KPIs_SBS_BR_7


Information PM: SBS Key Performance Indicators

System

2 A30808-X3247-B912-1-7618

Contents

1 I NTRODUCTION ..............................................................................................................................................................4 1.1 Purpose............................................................................................................................................................... 4

1.2 Reference Documents.......................................................................................................................................4 1.3 Issue History ......................................................................................................................................................4 1.4 Definition of Terms ........................................................................................................................................... 5

2 IMMEDIATE ASSIGNMENT A NALYSIS .........................................................................................................................7 2.1 Number of Immediate Assignment Attempts...............................................................................................10 2.2 Number of Immediate Assignment Losses ..................................................................................................10 2.3 Number of Immediate Assignments by BSC procedure............................................................................11 2.4 Number of AGCH Losses ...............................................................................................................................12 2.5 Number of Immediate Assignment Commands sent to MS via AGCH...................................................12 2.6 Number of Immediate Assignments without MS Seizure..........................................................................13 2.7 Number of successful Immediate Assignments ..........................................................................................13 2.8 Immediate Assignment Loss Rate.................................................................................................................14 2.9 AGCH Loss Rate .............................................................................................................................................14

2.10 Immediate Assignment without MS Seizure Rate......................................................................................15 2.11 Immediate Assignment Success Rate...........................................................................................................15

3 SSS PROCEDURES A NALYSIS.....................................................................................................................................16 3.1 Number of successful Immediate Assignments related to Call Setups...................................................18 3.2 Number of Dropped SDCCH Connections related to Call Setups.........................................................18 3.3 Number of SSS Procedure Failures related to Call Setups.....................................................................20 3.4 SDCCH Drop Rate related to Call Setups..................................................................................................21 3.5 SSS Procedures Failure Rate related to Call Setups................................................................................21 3.6 SSS Procedures Success Rate related to Call Setups...............................................................................22

4 ASSIGNMENT A NALYSIS.............................................................................................................................................23 4.1 Number of Assignment Attempts ..................................................................................................................25 4.2 Number of Assignment Failures...................................................................................................................25 4.3 Number of successful Assignments ..............................................................................................................26

4.4 Assignment Failure Rate ...............................................................................................................................26 4.5 Assignment Success Rate...............................................................................................................................28 4.6 Assignment success rate when radio resources available.......................................................................28

5 CALL SETUP A NALYSIS ..............................................................................................................................................29 5.1 Number of Call Setup Attempts....................................................................................................................30 5.2 Number of Successful Call Setups................................................................................................................30 5.3 Call Setup Success Rate.................................................................................................................................31 5.4 Number of Call Setup Failures.....................................................................................................................31 5.5 Call Setup Failure Rate .................................................................................................................................33

6 TCH DROP RELATED PERFORMANCE I NDICATORS................................................................................................34 6.1 Number of Dropped TCH Connections.......................................................................................................34 6.2 TCH Drop Distribution..................................................................................................................................35 6.3 TCH Drop Rate ...............................................................................................................................................38

6.4 Call Drop Rate................................................................................................................................................39 6.5 Mean Time between TCH Drop....................................................................................................................41 6.6 TCH Drops per Erlanghour..........................................................................................................................41

7 SDCCH DROP RELATED PERFORMANCE I NDICATORS..........................................................................................42 7.1 Number of dropped SDCCH Connections..................................................................................................42 7.2 SDCCH Drop Rate .........................................................................................................................................42 7.3 Mean Time between SDCCH Drop..............................................................................................................43 7.4 SDCCH Drops per Erlanghour....................................................................................................................43

8 TCH LOAD RELATED PERFORMANCE I NDICATORS................................................................................................44 8.1 TCH Load for Circuit Switched Traffic ......................................................................................................44 8.2 Combined time slot utilisation for CS and PO Traffic .............................................................................52

9 SDCCH LOAD RELATED PERFORMANCE I NDICATORS..........................................................................................54 9.1 SDCCH Traffic Offered .................................................................................................................................54 9.2 SDCCH Traffic Carried.................................................................................................................................55 9.3 SDCCH Traffic Lost .......................................................................................................................................56 9.4 SDCCH Blocking Rate...................................................................................................................................56

8/13/2019 KPIs_SBS_BR_7



System

3 A30808-X3247-B912-1-7618

9.5 SDCCH Loss Rate...........................................................................................................................................57 9.6 SDCCH Mean Holding Time ........................................................................................................................57 9.7 SDCCH Traffic Utilisation............................................................................................................................58

10 OTHER LOAD RELATED PERFORMANCE I NDICATORS......................................................................................59 10.1 PCH Accesses ..................................................................................................................................................59 10.2 PCH Rejection Rate........................................................................................................................................59

10.3 PPCH Accesses ...............................................................................................................................................59 10.4 PPCH Rejection Rate.....................................................................................................................................60 10.5 AGCH Accesses...............................................................................................................................................60 10.6 AGCH Rejection Rate ....................................................................................................................................61 10.7 PAGCH Accesses ............................................................................................................................................61 10.8 PAGCH Rejection Rate..................................................................................................................................62 10.9 RACH Accesses ...............................................................................................................................................62 10.10 Invalid RACH Signal Rate.............................................................................................................................62 10.11 Abis pool supervision.....................................................................................................................................63

11 HANDOVER RELATED PERFORMANCE I NDICATORS.........................................................................................66 11.1 Intra Cell Handovers......................................................................................................................................66 11.2 Inter Cell Intra BSC Handovers...................................................................................................................71 11.3 Inter Cell Inter BSC Handovers ...................................................................................................................78

11.4 Inter System Handover between GSM and UMTS ....................................................................................82 11.5 Other Handover Performance Indicators...................................................................................................88 12 POWER AND QUALITY MEASUREMENTS............................................................................................................94

12.1 Interference Band Rate on idle TCH ...........................................................................................................94 12.2 Quality Link for N% FER ..............................................................................................................................94 12.3 Mean FER UpLink ..........................................................................................................................................95 12.4 Power and Quality limits for N% Percentile on busy TCH.....................................................................96 12.5 Distribution of power control levels on busy TCH...................................................................................96 12.6 Mean Level and Quality on busy TCH........................................................................................................97 12.7 TA Distribution................................................................................................................................................99 12.8 RXQUAL Distribution....................................................................................................................................99 12.9 RXLEV Distribution.....................................................................................................................................100 12.10 FER Distribution...........................................................................................................................................100

12.11 Mean FER UpLink per RXQUAL ...............................................................................................................101 12.12 Mean RXLEV per RXQUAL Band .............................................................................................................102 12.13 Mean RXLEV per TA Band .........................................................................................................................103 12.14 High RXLEV with Low RXQUAL Rate .....................................................................................................104 12.15 TCH Traffic Type Distribution ...................................................................................................................105 12.16 Adaptive Multirate Distribution.................................................................................................................106 12.17 Adaptive Multirate True Frame Erasure Rate .........................................................................................107

13 AVAILABILITY RELATED PERFORMANCE I NDICATORS................................................................................. 108 13.1 Transceiver Availability...............................................................................................................................108 13.2 TCH Distribution Rate.................................................................................................................................108 13.3 TCH Efficiency..............................................................................................................................................109 13.4 SDCCH Efficency .........................................................................................................................................110

14 GPRS R ELATED PERFORMANCE I NDICATORS............................................................................................... 111

14.1 User oriented KPIs .......................................................................................................................................111 14.2 Network planning (dimensioning)..............................................................................................................125 14.3 Network optimization ...................................................................................................................................135 14.4 Cell Reselection.............................................................................................................................................139

15 MISCELLANEOUS PERFORMANCE I NDICATORS ............................................................................................. 143 15.1 BSC Processorload.......................................................................................................................................143 15.2 BTSE Processorload ....................................................................................................................................145 15.3 Paging Response / Location Update Ratio per Cell...............................................................................145 15.4 BSC <-> MSC/SMLC CCS7 Load.............................................................................................................146

16 BSS RELATED KPIS AT SIEMENS MSC........................................................................................................... 147 17 APPENDIX............................................................................................................................................................ 148

17.1 List of BSS Performance Measurements...................................................................................................148

8/13/2019 KPIs_SBS_BR_7



System

4 A30808-X3247-B912-1-7618

1 Introduction

1.1 Purpose

The purpose of this document is the definitions of SBS Key Performance Indicators,which can be used in a uniform way. It is possible to compare Key Performance

Indicators of different networks or to give statements about Quality, Performance,Capacity and more.

This document will describe the most important Key Performance Indicators relevant

for GSM Mobile Networks. All listed formulas are valid for one elementary object andfor one elementary measurement period. Evaluation of multiple objects and for

multiple measurement periods can be done as described in chapter 1.4..

This KPI document does not provide planning rules for network dimensioning. It only

provides input data used for planning tools.

1.2 Reference Documents

You can find further information about Performance Measurement in the followingdocuments :

• PM:SBS Counter (A30308-X3247-L40-2-7618)

• PM:SBS Message Flow, A30808-X3247-L41-2-7618

• Training Documentation 1736 : BSS Performance Measurement

• GSM Recommendation 12.04 V7.0.0 Release 99

1.3 Issue History

IssueVersion

Date of issue Reason for of issue

BR6 03/2002 First version for new release 6.0

BR7, version 1 02/2004 Update to BR7.0

Main changes:

• Utilization of new (E)GPRS PM counters

• Utilization of new counters for intersystem HO toUMTS

• HO: in the KPI formulas no aggregation onneighbor cells takes place

BR7, version 2 10/2004 Correction of formulas and inconsistencies in thedescription parts

8/13/2019 KPIs_SBS_BR_7



System

5 A30808-X3247-B912-1-7618

1.4 Definition of Terms

Long name

This is the full name of the described key performance indicator (KPI).

Short n ame

This is an abbreviation of the described key performance indicator.

Description

The description will give you a short explanation of the described key performanceindicator.

Formula

The formula will deliver the exact calculation of the described key performanceindicator. The formula is related to one elementary object and to one elementaryperiod. Multiple objects and multiple elementary periods can be added as described

under ‘Evaluation of multiple objects for multiple elementary periods‘.

Used pa rameter

Here you can find either the SBS short identification of the used SBS performancemeasurement counters or the short name of the used key performance indicators.

The related long names of SBS performance measurement counters you can find inthe appendix under ‘List of Performance Measurements‘. The SBS short identification

is a combination of measurement type and sub-counter. A measurement type canhave several sub-counters. Therefore the used sub-counters are listed in bracketswith following meaning:

• [1] sub-counter 1 has to be taken.

• [1,2,4] sub-counters 1, 2 and 4 have to be added.

• [1..4] sub-counters 1, 2, 3 and 4 have to be added.

• [1..4, 7..10] sub-counters 1, 2, 3, 4, 7, 8, 9 and 10 have to be added.

• [all] all sub-counters have to be added.

It is also possible that key performance indicators can have sub-indicators. In this

case they are also listed in brackets.

8/13/2019 KPIs_SBS_BR_7



System

6 A30808-X3247-B912-1-7618

Elementary object

This is the smallest measurement object, which can be used for a KPI (e.g. BSC,Cell, TRX).

Unit

- The unit is related to a key performance indicator e.g. seconds, percent ornone.

- The unit “kbit” expresses 1000 bit. Same for “kbit/s”

Remark

Here you will find additional important information for the key performance indicator.

Aggregation

The aggregation field will show you how to evaluate the KPI for multiple objects andfor multiple elementary periods. There are:

• Daily aggregation: for every KPI we can calculate:

- MAX/min value: the KPI value for the granularity period of one day is recorded.These values are processed to find the peak value, maximum (MAX) or the

minimum value (min);

- MAX/min Time provides the starting time of the granularity period of the peak

value (MAX and min);

- Mean/Sum daily value represents the mean/sum of the counter value, used inKPI’s formula, collected for the granularity period; it is the aggregation

standard

1

.- SPBH (Sample at Peak Busy Hour 2) is the value of the KPI at reference BH

and is calculated only in the busy hour;

- SPBH Time provides the starting time of the hour of SPBH;

• Several days aggregation:

- MAX/MIN value: all the KPI values recorded for each granularity period foreach day are processed to find the highest value (MAX) or the minimum value

(min);

- MAX/MIN Time provides the starting time and date of the granularity period ofthe MAX/min value;

- TCMAX/TCMIN (Time Coherent MAX/min): for a number of days, countervalues for each granularity period for each day are recorded. The values for

the same granularity period for each day are averaged, determining theaverage day. The counter value in the granularity period in this average daygive the highest value (TCMAX) or the lower value (TCmin) is taken;

- TCMAX/TCMIN Time provides the starting time related to TCMAX/TCminvalue;

- Mean/Sum value: all the counter values, used in KPI’s formula, recorded forgranularity periods for each day are processed to find the mean/sum value, itis the aggregation standard (refer to note 1);

- ASPBH (Average Sample at Peak Busy Hour): each day the sample at peakbusy hour is recorded and then these values are averaged;

8/13/2019 KPIs_SBS_BR_7



System

7 A30808-X3247-B912-1-7618

- SPBH is the value of the KPI at reference BH and is calculated only in thebusy hour on the number of considered days;

- SPBH Time and Date provides the starting time of the hour and the date of

SPBH;

- TCSPBH (Time Coherent Sample at Peak Busy Hour): on average day it can

be defined the busy hour, and in this peak busy hour the sample is recorded;

- TCSPBH Time (Time Coherent Sample at Peak Busy Hour Time): providesthe starting time of the hour of TCSPBH;

- Mean daily represents the average over a number of days of the mean dailyvalue;

- MAX_SPBH : each day the sample at peak busy is recorded and then the max

of these values is considered.

For example it can be required to calculate the Handover Success Rate with SPBH

aggregation Function referring to BSC Processor Load measurement:- KPI(Aggregation Function[Reference variable])

- InterCellHOSuccRate(SPBH[BSCPRCLD[2]])

1Standard means that the evaluation can be done by adding or averaging thecounter values for single objects and single periods in the following way (standard

aggregation):

∑=t,i

t)(i,Counterm)(n,Counter t)(i,Counterm)(n,Counter =

i elementary objectt elementary periodn object (sum of elementary objects)m measurement period (sum of elementary periods)

2The busy hour is the hour in which the reference variable assumes the highest

value within one day for a measured object for any performance indicator. When thegranularity period is smaller than 1 hour, this value is calculated with the slidingwindow algorithm.

Not in any case it makes sense to evaluate the busy hour for each singleperformance indicator. It is also possible to make an assumption, that for Randomtraffic the busy hour for most different measurement objects will correlate. Thatmeans the busy hour is derived from a particular performance indicator and can beused for other performance indicators. E.g. the busy hour could be derived from theperformance indicator ‘BSC Processor load‘ and could than be used for all otherperformance indicators.

2 Immediate Assignment Analysis

The KPIs of this section are mainly used for deriving the the Call Setup Success Rate(CSSR) and Call Setup Failure Rate (CSFR). The Key Performance Indicators (KPIs)

8/13/2019 KPIs_SBS_BR_7



System

8 A30808-X3247-B912-1-7618

are mostly related to the Mobile Station point of view, by meaning they will count theevents related to Mobile Stations. The messageflow of the Immediate AssignmentProcedure is listed below. The numbers in brackets will indicate available SBS

performance measurements.

Fig. 1 Message flow: Immediate Assignment Procedure

SBS Counter

[1] CHANNEL REQUIRED ATIMASCA [1..14]

[2] SDCCH CONGESTIONS(Congestions due to SDCCH HO are also counted)

ATSDCMBS [1]

[3] IMM. ASS CMD (Abis Interface)

(IMM. ASS. CMD. messages, which contain anIMM. ASS. REJ. message are not counted)

SUIMASCA [1..6]

[4] IMM. ASS CMD (Abis Interface)(including those IMM. ASS. CMD. messages thatcontain an IMM. ASS. REJ. message)

TACCBPRO [2]

[5] IMM. ASS CMD / IMM. ASS. REJ. (Um Interface)

(difference between IMM. ASS.CMD and Del. Ind.,including those IMM. ASS. CMD. messages thatcontain an IMM. ASS. REJ. message)

NACSUCPR [2]

[6] ESTABLISH INDICATION NSUCCHPC [1..22]

BTS BSC MS

CHANNEL REQUEST

[1] CHANNEL REQUIRED

CHANNEL ACTIV

CHANNEL ACTIV ACK

CHANNEL ACTIV NACK

[3] [4] [5] IMM. ASS

[5] DELETE INDICATION

IMM. ASS CMD

IMM. ASS REJECT

SABM

[6] ESTABLISH INDIC.UA

[2] SDCCH

CONGESTIONS

8/13/2019 KPIs_SBS_BR_7



System

9 A30808-X3247-B912-1-7618

The following figure shows you the traffic flow.

Fig. 2 Traffic flow: Immediate Assignment Procedure

This chapter contains the following ‘Number related’ KPIs:

• Number of Immediate Assignment Attempts: [1]

• Number of Immediate Assignment Losses : [2]= [1] – [3]

• Number of Immediate Assignments by BSC procedure : [3] = [1] – [2])

• Number of AGCH Losses: [4] = [9] * [3]

• Number of Immediate Assignment Commands sent to MS via AGCH: [5] = [3] – [4] = (1- [9]) * [3]

• Number of Immediate Assignments without MS Seizure: [6] = [5] – [7] = [3] – [4] - [7]

• Number of successful Immediate Assignments: [7]

And the following ‘Rate related’ KPIs:• Immediate Assignment Loss Rate: [8] = [2] / [1]• AGCH Loss Rate: [9] = [4] / [3])

• Immediate Assignment without MS Seizure Rate: [10] = [6] / [5]

• Immediate Assignment Success Rate: [11] = [7] / ([1] – [6])(Phantom RACHs are not counted, because they are not related to MS)

The Immediate Assignment Failure Rate can be calculated as follows:

Immediate Assignment Failure Rate = 1 - Immediate Assignment Success Rate or

Immediate Assignment Failure Rate = Immediate Assignment Loss Rate *

AGCH Loss Rate * Immediate Assignment without MS Seizure Rate

[2] Number of Immediate Assignment Losses

[4] Number of AGCH Losses

[6] Number of Immediate Assignments

without MS Seizure[7] Number of successful

Immediate Assignments

[1] Number of Immediate

Assignment Attempts

[3] Number of Imm Ass. by

BSC procedure

[5] Imm Ass Command

sent to MS via AGCH

8/13/2019 KPIs_SBS_BR_7



System

10 A30808-X3247-B912-1-7618

2.1 Number of Immediate Assignment Attempts

Long name: (a) Number of Immediate Assignment Attempts

Short name: (a) ImmAssAtt

Description: These indicators will give you the number of started Immediate Assignmentprocedures from MS point of view by counting the number of Channel Requiredmessages.

Formula: (a) ..14]ATIMASCA[1ImmAssAtt =

Used param.: ATIMASCA[1..14]

Elem. Object: Cell

Unit: None

Remarks: Phantom RACHs are channel required messages not foreseen for the observedcell. The Immediate Assignment procedure to allocate an SDCCH/TCH is thenstarted, but will not be successful, because no MS will reply with a SABM messageand therefore a BTS Timer will expire. These unforeseen messages will also becounted.

In BR 7.0 a note was added in counter ATIMASCA. This fact does not affect themeaning or definition of the KPI.

2.2 Number of Immediate Assignment Losses

Long name: (a) Number of Immediate Assignment Losses

Short name: (a) ImmAssLoss

Description: These indicators will give you the number of SDCCH/TCH request, which wererejected, because no SDCCH/TCH was available or because of BTS channelactivation failures.

Formula: (a) rocImmAssBSCp -ImmAssAttImmAssLoss =

Used param.: ImmAssAtt (2.1(a)) , ImmAssBSCproc (2.3(a))

Elem. Object: Cell

Unit: None


In BR 7.0 a note was added in counters ATIMASCA(1,9) and SUIMASCA8(1,10).This fact does not affect the meaning or definition of the KPI.

8/13/2019 KPIs_SBS_BR_7



System

11 A30808-X3247-B912-1-7618

2.3 Number of Immediate Assignments by BSCprocedure

Long name: (a) Number of Immediate Assignments by BSC internal procedure

Short name: (a) ImmAssBSCproc

Description: These indicators will give you the number of successful Immediate Assignments ofa channel by BSC internal procedure

I. e. the indicator counts the cases when the Immediate Assignment Attempts(RACH) can be satisfied by an according idle channel.

Formula:(a) ..6]SUIMASCA[1rocImmAssBSCp =

Used param.: SUIMASCA[1..6]

Elem. Object: Cell

Unit: None


8/13/2019 KPIs_SBS_BR_7



System

12 A30808-X3247-B912-1-7618

2.4 Number of AGCH Losses

Long name: (a) Number of AGCH losses

Short name: (a) AGCHLoss

Description: These indicators will give you the number AGCH losses by meaning of nottransmitted Immediate Assignment Command messages over the AGCH on the

Air Interface. Reason for AGCH failures are mainly AGCH overload. This formulais related to MS point of view, by meaning each MS related immediate assignmentprocedure should be stepped once.

Therefore events, where no SDCCH/TCH was available or BTS channel activationfailured are counted in the formula ‘Number of Immediate Assignment Losses’.=> Only Delete Indication messages related to Immediate Assignment Commandmessages not containing an Immediate Assignment reject messages will rightly becounted.

Formula:(a) rocImmAssBSCp*teAGCHLossRaAGCHLoss =

Used param.: AGCHLossRate (2.9(a)) ,ImmAssBSCproc (2.3(a))

Elem. Object: Cell

Unit: None


2.5 Number of Immediate Assignment Commands sentto MS via AGCH

Long name: (a) Number of Immediate Assignments Commands sent to MS via AGCH

Short name: (a) ImmAssCmdAGCH

Description: The KPI provides the number of Immediate Assignments Commands sent to MSvia AGCH

Formula: (a) rocImmAssBSCp*te)AGCHLossRa1(GCHImmAssCmdA −=

Used param.: ImmAssBSCproc (2.3(a)), AGCHLossRate (2.9(a))

Elem. Object: Cell

Unit: None


8/13/2019 KPIs_SBS_BR_7



System

13 A30808-X3247-B912-1-7618

2.6 Number of Immediate Assignments without MSSeizure

Long name: (a) Number of Immediate Assignments without MS Seizure

Short name: (a) ImmAssNoSeiz

Description: These indicators will give you the number of immediate assignments withoutseizure by MS. The main reasons for this behavior are Phantom RACHs,messages not foreseen for the observed cell. Other reasons are not receivedSABM messages due to air interface problems. This formula will count thedifference between Immediate Assignment Command messages sent to the MSand the number of Establishment Indication messages. => not answeredImmediate Assignment Commands.

Formula: (a) ImmAssSucc-AGCHLoss-rocImmAssBSCpiImmAssNoSe =

Used param.: ImmAssBSCproc (2.3(a)), AGCHLoss (2.4(a)), ImmAssSucc (2.7(a))Elem. Object: Cell

Unit: None

Remarks: The formula will mainly detect Phantom RACHs. Phantom RACHs are channelrequired messages not foreseen for the observed cell. The Immediate Assignmentprocedure to allocate an SDCCH/TCH is started, but will not be successful,because no MS will reply with a SABM message. A BTS Timer will expire.In case of RACH repetitions (abnormal amount of time => Expiry of timerNSLOTST), it can happen that subsequent Immediate Assignment Commands willnot receive a positive reply from the MS. Nevertheless from MS point of view thecall setup was successful.

2.7 Number of successful Immediate Assignments

Long name: (a) Number of successful Immediate Assignments

Short name: (a) ImmAssSucc

Description: These indicators will give you the number of successful Immediate Assignmentsfrom MS point of view. A Immediate Assignment procedure is successful if the BTSreturns an establishment indication message on Abis.

Formula: (a) 22]..1714,..96,.. NSUCCHPC[1 ssSuccImmA =

Used param.: NSUCCHPC[1 .. 6, 9 .. 14, 17 .. 22]

Elem. Object: Cell

Unit: None

Remarks: BR7 update: new SMS related counters in NSUCCHPC; these are not beconsidered in the KPI formula

8/13/2019 KPIs_SBS_BR_7



System

14 A30808-X3247-B912-1-7618

2.8 Immediate Assignment Loss Rate

Long name: (a) Immediate Assignment Loss Rate

Short name: (a) ImmAssLossRate

Description: These indicators will give you the SDCCH/TCH Loss Rate, which were rejected,because no SDCCH/TCH was available or because of BTS channel activationfailures.

Formula:(a)

mAssAttIm

mAssLossIm RateImmAssLoss =

Used param.: ImmAssAtt (2.1(a)), ImmAssLoss (2.2(a))

Elem. Object: Cell

Unit: None

Remarks: Phantom RACHs are channel required messages not foreseen for the observedcell. The Immediate Assignment procedure to allocate an SDCCH/TCH is thenstarted, but will not be successful, because no MS will reply with a SAB M messageand therefore a BTS Timer will expire. These unforeseen messages will also becounted (in ImmAssAtt).

2.9 AGCH Loss Rate

Long name: (a) AGCH Loss Rate

Short name: (a) AGCHLossRate

Description: These indicators will give you the AGCH Loss Rate by meaning of not transmittedImmediate Assignment Command messages over the AGCH on the Air Interface.Reason for AGCH failures are mainly AGCH overload. This formula is related toMS point of view, by meaning each MS related immediate assignment procedureshould be stepped once.

Therefore events, where no SDCCH/TCH was available or BTS channel activationfailured are counted in the formula ‘Number of Immediate Assignment Losses’.=> Only Delete Indication messages related to Immediate Assignment Commandmessages not containing an Immediate Assignment reject messages will rightly beconsidered.

Formula:

(a) ]TACCBPRO[2

] NACSUCPR[2 - ]TACCBPRO[2 teAGCHLossRa =

Used param.: TACCBPRO [2], NACSUCPR [2]

Elem. Object: Cell

Unit: None


8/13/2019 KPIs_SBS_BR_7



System

15 A30808-X3247-B912-1-7618

2.10 Immediate Assignment without MS Seizure Rate

Long name: (a) Immediate Assignment without MS Seizure Rate

Short name: (a) ImmAssNoSeizRate

Description: These indicators will give you the immediate assignment without MS seizure rate .The main reasons for this behaviour are Phantom RACHs, messages not foreseenfor the observed cell. Other reasons are not received SABM messages due to airinterface problems. This formula will count number of not answered Immediate

Assignment Command messages related to the Immediate Assignment Commandmessages sent to the MS.

Formula:(a)

GCHImmAssCmdA

izImmAssNoSe izRateImmAssNoSe =

Used param.: ImmAssNoSeiz (2.6(a)), ImmAssCmdAGCH (2.5(a))

Elem. Object: Cell

Unit: None

Remarks: The formula will mainly detect Phantom RACHs. Phantom RACHs are channelrequired messages not foreseen for the observed cell. The Immediate Assignmentprocedure to allocate an SDCCH/TCH is started, but will not be successful,because no MS will reply with a SABM message. A BTS Timer will expire.

2.11 Immediate Assignment Success Rate

Long name: (a) Immediate Assignment Success Rate

Short name: (a) ImmAssSuccRate

Description: These indicators will give you the immediate assignment success rate from MSpoint of view. A Immediate Assignment procedure is successful if the BTS returnsan establishment indication message.

Formula:(a)

mAssNoSeizImmAssAttIm

ImmAssSucc RateImmAssSucc

−=

Used param.: ImmAssAtt (2.1(a)), ImmAssSucc (2.7(a)), ImmAssNoSeiz (2.6(a))

Elem. Object: Cell

Unit: NoneRemarks: Phantom RACHs are not included in this formula, because they are not related to

MS of the observed cell.

Um-Interface problems may lead to decoding errors of the Mobile’s L2 SABM-frame and therefore are not considered here.

8/13/2019 KPIs_SBS_BR_7



System

16 A30808-X3247-B912-1-7618

3 SSS Procedures Analysis

The KPIs of this section are mainly used for the derivation of the Call Setup Success

Rate (CSSR) and Call Setup Failure Rate (CSFR). The Key Performance Indicators(KPIs) are mostly related to the Mobile Station point of view, by meaning they willcount the events related to Mobile Stations. There exists the following SSS

Procedures which used during Call Setup related to the parameter setting in theMSC: Identity Check (IMEI), Authentication (IMSI), Ciphering, Call Control: Setup

Fig. 3 Message flow: SSS Procedures during Call Setup (MOC)

SBS Counter

[1] ESTABLISH INDICATION NSUCCHPC[1..4,8..12,17..20]

[2] ASSIGNMENT ATTEMPTS TASSATT [2..3]

Sub-counters are listed in Brackets

The different number of failures and failure rates can be evaluated with Siemens

MSC counter per MSC. All events are cell independent. Therefore it is sufficient tocalculate them for the elementary object MSC.

It is also very important to evaluate the number of SDCCH drops during call setup.SDCCH drops mainly occur in the time when SSS Procedures are running. Therefore

they can be evaluated together with the SSS Procedure formulas. With SBSperformance measurement counter it is possible to calculate the SSS Procedure

Success and Failure Rate related to Call Setups.

BTS BSC MS

SABM[1] Establishme nt Ind.

CCAuthentification Request

Authentification Response

Ciphering Complete

Ciphering Command

MSC

CR(Compl Layer3Info)

Identity RequestIdentity Response

Ciphering CommandCi herin Com lete

Setup

[2] Assignme nt Req.

Assignment Command

Call Proceeding

8/13/2019 KPIs_SBS_BR_7



System

17 A30808-X3247-B912-1-7618


Fig. 4 Traffic flow: SSS Procedures during Call Setup

SDCCH Drops can occur before SSS Procedure Failure and vice versa.

This chapter contains the following ‘Number related’ KPIs:• Number of successful Immediate Assignments related to Call Setups: [1]• Number of Dropped SDCCH Connections related to Call Setups: [2]

• Number of SSS Procedure Failures related to Call Setups: [3] = [1] - [4] - [2]

And the following ‘Rate related’ KPIs:

• SDCCH Drop Rate related to Call Setups = [2] / [1]

• SSS Procedures Failure Rate related to Call Setups = [3] / [1]• SSS Procedures Failure Rate related to Call Setups = [4] / [1]

Referenced KPI from chapter 4 Assignment Analysis

• Number of Assignment Attempts: [4]

[2]SDCCH Drops[3] SSS Procedure failures

[4] Assignment Attempts

[1]Successful Immediate Assignments

8/13/2019 KPIs_SBS_BR_7



System

18 A30808-X3247-B912-1-7618

3.1 Number of successful Immediate Assignmentsrelated to Call Setups

Long name: (a) Number of successful Immediate Assignments related to Call Setups

Short name: (a) ImmAssSuccCS

Description: These indicators will give you the number of successful Immediate Assignmentsrelated to Call Setups. A Immediate Assignment procedure related to a Call Setupis successful if the BTS returns an establishment indication message related toMobile Originated Calls (MOC), Mobile Terminated Calls (MTC), Emergency Callsor Call Reestablishment.

Formula: (a) ] NSUCCHPC[8-17..20]..4,9..12, NSUCCHPC[1 ssSuccCSImmA =

Used param.: NSUCCHPC[1..4, 8 ..12,17..20]

Elem. Object: Cell

Unit: None

Remarks: BR7:

• partly elimination of systematic error in formula by subtracting the SMS-MTrelated counter values NSUCCHPC[8] (SDCCH assigned for SMS-MT). Thenew SMS counters are triggered on arrival of Establish Confirm (SAPI 3)

• Remark (background information)The counters NSUCCHPC [16,24] must not be subtracted since they mainlyare triggered where an SMS MT arrives when the MS has an ongoing TCHcall. In that case no immediate TCH assignment in connection with the SMSMT takes place at all and thus an elimination of SMSes in formula 3.1 by

subtracting "- NSUCCHPC [16,24]" is not necessary.• Remaining systematic error:

The formula has a small systematic error when "Direct TCH Assignment” isenabled. For that scenario the counters NSUCCHPC [16,24] might also betriggered when an SMT MT arrives for an idle MS, which requests animmediate TCH assignment as paging response. The number of theseconcurrencies has in principle to be subtracted in formula 3.1. ButNSUCCHPC [16,24] does no distinguish between arrival of SMS MT for an idleMS and for an MS with ongoing TCH call (the call processing trigger point usedfor NSUCCHPC [16,24] has no knowledge about the history of the existingTCH assignment).

3.2 Number of Dropped SDCCH Connections related toCall Setups

Long name: (a) Number of Dropped SDCCH Connections related to Call Setups

Short name: (a) SDCCHDropCS

Description: This indicator will give you the number of dropped SDCCH connections related toCall Setups. SDCCH drops mainly occur during running SSS Procedures. Thisformula is related to the assumption that the number of dropped SDCCHconnections is random distributed to all kind of assignment causes (MOC, MTC,

8/13/2019 KPIs_SBS_BR_7



System

19 A30808-X3247-B912-1-7618

Locupd, …). Therefore this formula contains a factor for the ratio of MOC and MTCto all kind of assignment causes to get the relation to Call Setups.

Formula:

(a)ImmAssSucc

CSImmAssSucc *SDCCHDrop SSDCCHDropC =

Used param.: SDCCHDrop(7.1(a)), ImmAssSucc (2.7(a)), ImmAssSuccCS (3.1(a))

Elem. Object: Cell

Unit: None

Remarks:

8/13/2019 KPIs_SBS_BR_7



System

20 A30808-X3247-B912-1-7618

3.3 Number of SSS Procedure Failures related to CallSetups

Long name: (a) Number of SSS Procedure Failures related to Call SetupsShort name: (a) SSSProcFailCS

Description: This indicator will give you the number of SSS Procedure failures related to CallSetups.

Formula: (a) SSDCCHDropC-AssAtt- CSImmAssSucclCSSSSProcFai =

Used param.: ImmAssSuccCS (3.1(a), AssAtt (4.1(a)), SDCCHDropCS (3.2(a))

Elem. Object: Cell

Unit: None

Remarks: Please note that Authentication-, Identity-, Ciphering- and MSC failures arecounted in this formula although they are not related to the BSS. User Releasebefore assignment of a TCH is also included in this formula. Assignments ofSDCCH are not considered.

8/13/2019 KPIs_SBS_BR_7



System

21 A30808-X3247-B912-1-7618

3.4 SDCCH Drop Rate related to Call Setups

Long name: (a) SDCCH Drop Rate related to Call Setups

Short name: (a) SDCCHDropRateCS

Description: This indicator will give you the SDCCH Drop Rate related to Call Setups. SDCCHdrops mainly occur during running SSS Procedures. This formula is related to theassumption that the number of dropped SDCCH connections is random distributedto all kind of assignment causes (MOC, MTC, Locupd, …). Therefore this formulais equal to the SDCCH Drop Rate.

Formula:(a) ateSDCCHDropR

mAssSuccCS

S SDCCHDropC ≈=Im

ateCSSDCCHDropR

Used param.: SDCCHDropCS (3.2(a)), ImmAssSuccCS (3.1(a)), SDCCHDropRate (7.2(a))

Elem. Object: Cell

Unit: None

Remarks:

SDCCH Handovers are not considered here.

3.5 SSS Procedures Failure Rate related to Call Setups

Long name: (a) SSS Procedures Failure Rate related to Call SetupsShort name: (a) SSSProcFailRateCS

Description: This indicator will give you the SSS Procedures Failure Rate by meaning thenumber of failures during SSS Procedures compared to the number of successfulImmediate Assignment Procedures (Establishment Indication).

Formula:(a)

mAssSuccCSIm

ocFailCSPr SSS lRateCSSSSProcFai =

Used param.: SSSProcFailCS (3.3(a)), ImmAssSuccCS (3.1(a))

Elem. Object: Cell

Unit: None

Remarks: Please note that Authentication-, Identity-, Ciphering- and MSC failures arecounted in this formula although they are not related to the BSS. User Releasebefore assignment of a TCH is also included in this formula. Assignments ofSDCCH are not considered.

8/13/2019 KPIs_SBS_BR_7



System

22 A30808-X3247-B912-1-7618

3.6 SSS Procedures Success Rate related to CallSetups

Long name: (a) SSS Procedures Success Rate related to Call Setups

(b) Total SSS Procedures Success Rate related to Call Setups

Short name: (a) SSSProcSuccRateCS

(b) SSSProcSuccRateCStotal

Description: The first Indicator will give you the SSS Procedures Success Rate related to CallSetups by meaning the rate for successful allocated Timeslots from MSC point ofview (Assignment Request Message) minus the SDCCH Drop Rate related to CallSetups. This indicator is related to the Radio Network and is thereforerecommended to find out Radio Network failures.

The second indicator will give you the SSS Procedures Success Rate related toCall Setups by meaning the number of started Assignment Procedures

(Assignment Requests) compared to the number of successful Immediate Assignment Procedures (Establishment Indications) related to Call Setups. Authentication-, Identity-, Ciphering- and MSC failures are among others countedwithin this indicator although they are not related to the BSS.

Formula: (a) ateCSSDCCHDropR -1cRateCSSSSProcSuc =

(b)CSImmAssSucc

AssAtt alcRateCStotSSSProcSuc = or

CSocFailRatePr SSSateCSSDCCHDropR 1alcRateCStotSSSProcSuc −−=

Used param.: ImmAssSuccCS (3.1(a)), AssAtt (4.1(a)), SDCCHDropRateCS (3.4(a)),

SSSProcFailRateCS (3.5(a))Elem. Object: Cell

Unit: None

Remarks: SSSProcSuccRateCStotal:

Please note that Authentication-, Identity-, Ciphering- and MSC failures will lead toa worse Success Rate although they are not related to the BSS. User Releasebefore assignment of a TCH is also included in the second formula. Assignmentsof SDCCH are not considered.

8/13/2019 KPIs_SBS_BR_7



System

23 A30808-X3247-B912-1-7618

4 Assignment Analysis

The KPIs of this section are mainly used for the derivation of the Call Setup Success

Rate (CSSR) and Call Setup Failure Rate (CSFR). The Key Performance Indicators(KPIs) are mostly related to the Mobile Station point of view, by meaning they willcount the events related to Mobile Stations. The messageflow of the Assignment

Procedure is listed below (normal case). The numbers in brackets will indicateavailable SBS performance measurements.

Fig. 5 Message flow: Assignment Procedure (normal case)

BSS Counter

[1] ASSIGMENT ATTEMPS TASSATT [2..3]

[2] INCOMING REDIRECTED TASSSUCC [4..5]

[3] OUTGOING REDIRECTED CALLS SINTHINT [7] +SUINBHDO [10*n+7]; n = 0 ...31(n= number of GSM ADJ-ids) +

7]m*0SUOISHDO[1 + ; m = 0 ...63

(m= number of UMTS ADJ-ids)

[4] ASSIGMENT COMPLETE (normal Assignm.) TASSSUCC [2..3]

[5] ASSIGMENT FAILURE TASSFAIL [6,7,8,10,11,12,13,15]

[6] Queuing Failure NMSGDISQ [1,2]

MS BTS BSC MSC

ASSIGNMENT REQUEST

CHAN ACTIV

ASSIGNMENT COMMAND

CHAN ACTIV ACK

SABM

CHANNEL ACTIV NEG ACK

ASSIGNMENT COMMAND

ASSIGNMENT FAILURE

ASSIGNMENT COMPLETE

[5] TASSFAIL

UA

ASSIGNMENT COMPLETE

ESTABLISH INDICATION(TNTCHCL)

ASSIGNMENT COMPLETE

1 TASSATT

4 TASSSUCC

PHYS CONTEXT REQ

PHYS CONTEXT CONF

(MTCHBUTI)

8/13/2019 KPIs_SBS_BR_7



System

24 A30808-X3247-B912-1-7618


Fig. 6 Traffic flow: Assignment Procedure

The observed cell is the cell where the call establishment has been started

(immediate assignment procedure). By aid of the feature Directed Retry a TCH maybe assigned in a cell different from the observed cell. Also in that case the “success”is counted for the observed cell.

The Assignment procedure is used to allocate a TCH. Because of new feature the

Assignment Success Rate is not easy to evaluate. The Directed Retries have also to

be considered. The concept how to evaluate Directed Retries for the AssignmentSuccess Rate is comparable with the Handover Success Rate, where only outgoing

Handover will be considered. Therefore all Directed Retries for an observed cell haveto be counted, which where started in the observed cell and were successful in any

target cell with neighbor cell measurements.

Under this assumption the Assignment Success Rate can be evaluated as follows:

Assignment Success Rate = (Assignment Complete [4] + Successful outgoing

redirected Calls [3]) / Assignment Attempts [1]

This chapter contains the following ‘Number related’ KPIs:• Number of Assignment Attempts: [1], see chapter 4.1.

• Number of Assignment Failures: [5] ,see chapters 4.2(a), (b), (c)• Number of successful Assignments = [3]+[4], see chapter 4.3

• Number of Queuing Failures: [6], see chapter 4.2(d)

This chapter contains the following ‘Rate related’ KPIs:• Assignment Failure Rate, see chapter 4.4

• Assignment Success Rate, see chapter 4.5• "Assignment success rate when radio resources available, see chapter 4.6(a)

Single Cell / Observed Cell

[1] Assignment Attempts

[4] Assignment

Complete [3] Successful Outgoing

redirected Calls

[2] Successful inc.

redirected Calls

[5] Assignment

[6] Queuing Failure

[3]+[4] Assignment success

8/13/2019 KPIs_SBS_BR_7



System

25 A30808-X3247-B912-1-7618

4.1 Number of Assignment Attempts

Long name: (a) Number of Assignment Attempts

Short name: (a) AssAtt

Description: These indicators will give you the number of Assignment procedures started by theMSC.

Formula:(a) 3]TASSATT[2, AssAtt =

Used param.: TASSATT[2,3]

Elem. Object: Cell

Unit: None

Remarks: Only TCH assignments are considered. Assignments of SDCCHs are notconsidered.

Only the assignment procedure triggered by the MSC is considered but not theImmediate Assignment procedure.

Incoming handovers are also not considered.

4.2 Number of Assignment Failures

Long name: (a) Number of TCH Losses

(b) Number of Assignment Failures by Message

(c) Number of Assignment Failures due to other Reason

(d) Number of Queuing Failures

Short name: (a) TCHLoss

(b) AssFailbyMess

(c) AssFailOther

(d) QueFail

Description: These indicators will give you the number of failed Assignments of a TCH.

Formula: (a) ,13]TASSFAIL[8 TCHLoss =

(b) 2,15],7,10,11,1TASSFAIL[6 essAssFailbyM =

(c) QueFail-essAssFailbyM-TCHLoss-AssSucc-AssAtterAssFailOth =

(d) ,2] NMSGDISQ[1 QueFail =

Used param.: TASSFAIL [6,7,8,10,11,12,13,15], AssAtt (4.1(a)) , AssSucc (4.3(a)),NMSGDSIQ[1,2]

Elem. Object: Cell

Unit: None

Remarks: Assignments of SDCCH are not considered. Subcounters TASSFAIL[10] andTASSFAIL[15] ('All other causes') used in formula (b) includes the A-interface andequipment related causes (see GSM 08.08). Formula (c) AssFailOther contains all

other causes related to internal and transmission failures.

8/13/2019 KPIs_SBS_BR_7



System

26 A30808-X3247-B912-1-7618

4.3 Number of successful Assignments

Long name: (a) Number of successful Assignments

Short name: (a) AssSucc

Description: These indicators will give you the number of successful completed Assignmentprocedures. Successful completed Assignment procedures are incremented evenwith successful outgoing directed retry, because it represents an assignment ofTCH for the originating cell.

Formula:

(a) ∑∑==

+++++

=63

0m

31

0n

7]m*0SUOISHDO[17]n*0SUINBHDO[1]SINTHINT[7

,3]TASSSUCC[2AssSucc

with n for the number of GSM neighbourcell relation (n=0..31)

with m for the number of UMTS neighbourcell relation (m=0..63)

Used param.: TASSSUCC[2,3], SINTHINT[7], 7]*0SUOISHDO[1 7],n*0SUINBHDO[1 ++

Elem. Object: Cell

Unit: None

Remarks: Assignments of SDCCH are not considered.

BR7 correction: numbers of the used counters of measurement SUINBHDO

BR7: intersystem Directed Retry to UMTS considered

4.4 Assignment Failure Rate

Long name: (a) TCH Loss Rate

(b) Assignment Failure Rate by Message

(c) Assignment Failure Rate due to other Reason

(d) Queuing Failure Rate

Short name: (a) TCHLossRate(b) AssFailbyMessRate

(c) AssFailOtherRate

(d) QueFailRate

Description: These indicators will give you the Assignment Failure Rates. The Assignmentprocedure is unsuccessful if the BSC returns a Assignment Failure message to theMSC or if the directed retry in the target cell was not successful.

Formula:(a)

AssAtt

TCHLoss eTCHLossRat =

(b)AssAtt

essAssFailbyM essRateAssFailbyM =

8/13/2019 KPIs_SBS_BR_7



System

27 A30808-X3247-B912-1-7618

(c)AssAtt

er AssFailOth erRateAssFailOth =

(d)AssAtt

QueFail eQueFailRat =

Used param.: AssAtt(4.1(a)), TCHLoss (4.2(a)), AssFailbyMess (4.2(b)), AssFailOther (4.2(c)),

QueFail (4.2(d))

Elem. Object: Cell

Unit: None

Remarks: Assignments of SDCCH are not considered.

8/13/2019 KPIs_SBS_BR_7



System

28 A30808-X3247-B912-1-7618

4.5 Assignment Success Rate

Long name: (a) Assignment Success Rate

Short name: (a) AssSuccRate

Description: These indicators will give you the Assignment Success Rate. The Assignmentprocedure is successful if the BSC returns an Assignment Complete message tothe MSC or if the directed retry in the target cell was successful.

Formula:(a)

AssAtt

AssSucc eAssSuccRat =

Used param.: AssAtt(4.1(a)), AssSucc (4.3(a))

Elem. Object: Cell

Unit: None

Remarks: Assignments of SDCCH are not considered.Inter System Directed Retry (e.g. UMTS) are also considered

4.6 Assignment success rate when radio resourcesavailable

Long name: (a) Assignment success probability when radio resource available

Short name: (a) SuccAssProbNoTCHBlocking

Description: This indicator provides the radio failures during the TCH assignment procedure

Formula:(a)

TCHLoss-AssAtt

essAssFailbyM1king bNoTCHBlocSuccAssPro −=

Used param.: AssAtt(4.1(a)), TCHLoss (4.2(a)), AssFailbyMess (4.2(b))

Elem. Object: Cell

Unit None

Remarks: The indicator only considers radio failures but no TCH losses (blockings) duringthe assignment procedure, i.e. it is assumed that enough TCH resources are

available

8/13/2019 KPIs_SBS_BR_7



System

29 A30808-X3247-B912-1-7618

5 Call Setup Analysis

The KPIs of the previous sections are mainly used for the derivation of the Call Setup

Success Rate (CSSR) and Call Setup Failure Rate (CSFR). The Call Setup SuccessRate and Call Setup Failure Rate are related to the Mobile Station point of view, bymeaning they will count the events related to Mobile Stations.

Overview Call Setup Analysis

CS

(5.3) CSSR

Call Setup Success Rate BSS

(5.5) CSFRCall Setup Failure Rate

Call Setup Failure Rate due to Immediate Assignment Losses

Call Setup Failure Rate due to AGCH Loss

Call Setup Failure Rate due to Immediate Assignment without MS Seizure

Call Setup Failure Rate due to SDCCH Drops

Call Setup Failure Rate due to SSS Procedure Failure

Call Setup Failure Rate due to TCH Loss

Call Setup Failure Rate due to Assignment Failures by Message

Call Setup Failure Rate due to Assignment Failures with other Reasons

Call Setup Failure Rate due to Queuing Failures

Comparable Overview can also be done for the ‘Number Related KPIs’

This chapter contains the following ‘Number related’ KPIs:

• Number of Call Setup Attempts• Number of Successful Call Setups

• Number of Call Setup Failures

And the following ‘Rate related’ KPIs:• Call Setup Success Rate

• Call Setup Failure Rate

8/13/2019 KPIs_SBS_BR_7



System

30 A30808-X3247-B912-1-7618

5.1 Number of Call Setup Attempts

Long name: (a) Number of Call Setup Attempts

Short name: (a) CSAtt

Description: This indicator counts all attempts at the BSS to setup up an end to end connection.

The indicator deals with the call setup attempts from the perspective of the MS

Formula:(a)

RateImmAssSucc

CSImmAssSucc CSAtt =

Used param.: ImmAssSuccCS (3.1a), ImmAssLossRate (2.6a), AGCHLossRate (2.7a),ImmAssNoSeizRate (2.8a)

Elem. Object: Cell

Unit: None

Remarks: Phantom RACHs are channel required messages not foreseen for the observedcell. The Immediate Assignment procedure to allocate an SDCCH/TCH is thenstarted, but will not be successful, because no MS will reply with a SABM messageand therefore a BTS Timer will expire.

Phantom RACHs are not considered as call setup attempts.

Systematic error

A mobile station may also not answer to an IMM ASS Command due to bad radioconditions. Such radio events will not be considered as call setup attempts

Be aware of parameter settings for RACHBT and RXLEVAMI

The Immediate Assignment failures are independent to the different call types(MOC, MTC, Locupd, SMS, ...). Therefore the Immediate Assignment FailureRates for any call type are used in the above formula.

5.2 Number of Successful Call Setups

Long name: (a) Number of Successful Call Setups

Short name: (a) CSSucc

Description: This indicator counts all successful Call Setups at the BSS to setup up an end toend connection. A Call Setup was successful if the MS was able to seize a TCH.

Formula: (a) AssSuccCSSucc =

Used param.: AssSucc (4.3a)

Elem. Object: Cell

Unit: None

Remarks: Assignment of SDCCH are not considered

8/13/2019 KPIs_SBS_BR_7



System

31 A30808-X3247-B912-1-7618

5.3 Call Setup Success Rate

Long name: (a) Call Setup Success Rate

(b) Call Setup Success Rate BSS

Short name: (a) CSSuccRate

(b) CSSuccRateBSS

Description: This indicator will give you the BSS observed Call Setup Success Rate to setup upan end to end connection. Two indicators are available, one that takes into accountall Call Setup rejections (BSS immediate assignment, SSS security and TCHassignment), one that only takes into account BSS related Call Setup rejections(BSS immediate assignment and TCH assignment).

Formula: (a) eAssSuccRat*alcRateCStotSSSProcSuc*RateImmAssSuccCSSuccRate =

(b) eAssSuccRat*ateCS)SDCCHDropR -1(* RateImmAssSuccBSSCSSuccRate =

Used param.: ImmAssSuccRate (2.11(a)), SSSProcSuccRateCStotal (3.6(b)), AssSuccRate(4.5(a)), SDCCHDropRateCS (3.4(a))

Elem. Object: Cell

Unit: None

Remarks: BR7: correction CSSuccRateBSS: factor (1-SDCCHDropRateCS) included informula

BR7: KPI CSSuccRateSSS cancelled (just another name for KPISSSProcSuccRateCStotal (3.6(b))

Systematic errors can occur as described in the used KPIs.

5.4 Number of Call Setup Failures

Long name: (a) Number of Call Setup Failures

(b) Number of Call Setup Failures due to Immediate Assignment Losses

(c) Number of Call Setup Failures due to AGCH Loss

(d) Number of Call Setup Failures due to Immediate Assignment without MSSeizure

(e) Number of Call Setup Failures due to SDCCH Drops

(f) Number of Call Setup Failures due to SSS Procedure Failure

(g) Number of Call Setup Failures due to TCH Loss

(h) Number of Call Setup Failures due to Assignment Failures by Message

(i) Number of Call Setup Failures due to Assignment Failures with other Reasons

(j) Number of Call Setup Failures due to Queuing Failures

Short name: (a) CSFail

(b) CSFailImmAssLoss

(c) CSFailAGCHLoss(d) CSFailImmAssNoSeiz

8/13/2019 KPIs_SBS_BR_7



System

32 A30808-X3247-B912-1-7618

(e) CSFailSDCCHDrop

(f) CSFailSSSProcFail

(g) CSFailTCHLoss

(h) CSFailAssFailbyMess

(i) CSFailAssFailOther

(j) CSFailQueFail

Description: These indicators will give you the number of unsuccessful Call Setups. Differentindicators distinguish between different causes used in the different procedures(Immediate Assignment, SSS Procedures and Assignment).

Formula: (a) CSFail = CSAtt - CSSucc

(b) CSFailImmAssLoss = CSAtt * ImmAssLossRate

(c) CSFailAGCHLoss = CSAtt * AGCHLossRate

(d) CSFailImmAssNoSeiz = CSAtt * ImmAssNoSeizRate

(e) CSFailSDCCHDrop = CSAtt * ImmAssSuccRate * SDCCHDropRateCS

(f) CSFailSSSProcFail = CSAtt * ImmAssSuccRate * SSSProcFailRateCS(g) CSFailTCHLoss = TCHLoss

(h) CSFailAssFailbyMess = AssFailbyMess

(i) CSFailAssFailOther = AssFailOther

(j) CSFailQueFail = QueFail

Used param.: CSAtt (5.1(a)), CSSucc (5.2(a)), ImmAssLossRate(2.8(a)), AGCHLossRate(2.9(a)), ImmAssNoSeizRate(2.10(a)), ImmAssSuccRate (2.11(a)),SDCCHDropRateCS(3.4(a)), SSSProcFailRateCS(3.5(a)), TCHLoss(4.2(a)),

AssFailbyMess(4.2(b)), AssFailOther(4.2(c)), QueFail(4.2(c))

Elem. Object: Cell

Unit: None

Remarks: See remarks in the referenced KPIs

8/13/2019 KPIs_SBS_BR_7



System

33 A30808-X3247-B912-1-7618

5.5 Call Setup Failure Rate

Long name: (a) Call Setup Failure Rate

(b) Call Setup Failure Rate due to Immediate Assignment Losses

(c) Call Setup Failure Rate due to AGCH Loss

(d) Call Setup Failure Rate due to Immediate Assignment without MS Seizure

(e) Call Setup Failure Rate due to SDCCH Drops

(f) Call Setup Failure Rate due to SSS Procedure Failure

(g) Call Setup Failure Rate due to TCH Loss

(h) Call Setup Failure Rate due to Assignment Failures by Message

(i) Call Setup Failure Rate due to Assignment Failures with other Reasons

(j) Call Setup Failure Rate due to Queuing Failures

Short name: (a) CSFailRate

(b) CSFailRateImmAssLoss(c) CSFailRateAGCHLoss

(d) CSFailRateImmAssNoSeiz

(e) CSFailRateSDCCHDrops

(f) CSFailRateSSSProcFail

(g) CSFailRateTCHLoss

(h) CSFailRateAssFailbyMess

(i) CSFailRateAssFailOther

(j) CSFailRateQueFail

Description: These indicators will give you the Call Setup Failure Rate. Different indicatorsdistinguish between different causes used in the different procedures (Immediate

Assignment, SSS Procedures and Assignment).

Formula: (a) CSFailRate = 1 – CSSuccRate

(b) CSFailRateImmAssLoss = ImmAssLossRate

(c) CSFailRateAGCHLoss = AGCHLossRate

(d) CSFailRateImmAssNoSeiz = ImmAssNoSeizRate

(e) CSFailRateSDCCHDrops = SDCCHDropRateCS

(f) CSFailRateSSSProcFail = SSSProcFailRateCS

(g) CSFailRateTCHLoss = TCHLossRate

(h) CSFailRateAssFailbyMess = AssFailbyMessRate(i) CSFailRateAssFailOther = AssFailOtherRate

(j) CSFailRateQueFail = QueFailRate

Used param.: CSSuccRate (5.3(a)), ImmAssLossRate(2.8(a)), AGCHLossRate(2.9(a)),ImmAssNoSeizRate(2.10(a)), SDCCHDropRateCS(3.4(a)),SSSProcFailRateCS(3.5(a)), TCHLossRate(4.4(a)), AssFailbyMessRate(4.4(b)),

AssFailOtherRate(4.4(c)), QueFailRate(4.4(d))

Elem. Object: Cell

Unit: None

Remarks: See remarks in the referenced KPIs

8/13/2019 KPIs_SBS_BR_7



System

34 A30808-X3247-B912-1-7618

6 TCH Drop related Performance Indicators

6.1 Number of Dropped TCH Connections

Long name: (a) Number of Dropped TCH Connections

Short name: (a) TCHDrop

Description: This indicator will give you the number of dropped TCH connections related toMobile Stations. Only drops related to the BSS including the radio interface areconsidered. But drops detected by the MSC call processing reasons areexcluded. (Therefore among others drops arising from the remote BSS and theremote radio interface are not considered)

Formula: (a) ..18]1412,5..3,.. NRCLRREQ[1TCHDrop =

Use case: Observation of customer satisfactionUsed param.: NRCLRREQ[1 .. 3, 5.. 12, 14 ..18]

Elem. Object: Cell

Unit: None

Remarks: TCH drops during pending incoming inter BSC handover are not counted in themeasurement NRCLRREQ. This avoids double counting of drops during pendingHO (during pending HO the TCH drops are only counted in the originating cell).

Therefore NRCLRREQ in fact counts the number of dropped TCH calls from theperspective of the Mobile Station (customer dissatisfaction)

There is a small systematic error in case of expiry of timer T_MSRFPCI duringassignment; in that case NRCLRREQ (“Radio interface message failure”) istriggered. This can only occur when T_MSRFPCI is not well adjusted (< T10).Remark: in case of expiry of T10 the BSC sends ASS FAIL to the MSC in thatcase NRCLRREQ is not triggered

8/13/2019 KPIs_SBS_BR_7



System

35 A30808-X3247-B912-1-7618

6.2 TCH Drop Distribution

Long name: (a) TCH drop distribution due to expiry of timer T200

(b) TCH drop distribution due to unsolicited DM response

(c) TCH drop distribution due to sequence error

(d) TCH drop distribution due to expiry of timer T_MSRFPCI

(e) TCH drop distribution due to distance limit exceeded

(f) TCH drop distribution due to handover access failures

(g) TCH drop distribution due to radio link failures

(h) TCH drop distribution due to remote transcoder failures

(i) TCH drop distribution due to other connection failures

(j) TCH drop distribution due to intra cell handovers

(k) TCH drop distribution due to inter cell intra bsc handovers

(l) TCH drop distribution due to inter bsc handovers(m) TCH drop distribution due to equipment failure

(n) TCH drop distribution due to protocol error

(o) TCH drop distribution due to distance error

(p) TCH drop distribution due to preemption

(q) TCH drop distribution due to O&M intervention

(r) TCH drop distribution due to other reasons

Short name: (a) TCHDropDist.T200

(b) TCHDropDist.UnsolDMRes

(c) TCHDropDist.SeqErr

(d) TCHDropDist.TMSRFPCI

(e) TCHDropDist.Distance

(f) TCHDropDist.HOAccess

(g) TCHDropDist.RadLinkFail

(h) TCHDropDist.RemTranscFail

(i) TCHDropDist.ConnOther

(j) TCHDropDist.IntraCellHO

(k) TCHDropDist.InterCellHO

(l) TCHDropDist.InterBSCHO

(m) TCHDropDist.EquipFail(n) TCHDropDist.ProtErr

(o) TCHDropDist.DistErr

(p) TCHDropDist.Preempt

(q) TCHDropDist.OAM

(r) TCHDropDist.Other

Description: This indicator will give you the TCH Drop Distribution showing the particular TCHdrops related to the total number of drops related to TCH connections.

Use case: Detection of network problems: e.g. insufficient coverage

For network optimization normally additional KPIs would be considered, e.g. KPIsfor the supervision of transmission power, interference and HO)

8/13/2019 KPIs_SBS_BR_7



System

36 A30808-X3247-B912-1-7618

Formula:(a)

TCHDrop

10,19,28] NRFLTCH[1, t.T200TCHDropDis =

(b)TCHDrop

11,20,29] NRFLTCH[2, est.UnsolDMR TCHDropDis =

(c)TCHDrop

12,21,30] NRFLTCH[3, t.SeqErr TCHDropDis =

(d)TCHDrop

13,22,31] NRFLTCH[4, t.TMSRFPCITCHDropDis =

(e)TCHDrop

14,23,32] NRFLTCH[5, t.DistanceTCHDropDis =

(f)TCHDrop

15,24,33] NRFLTCH[6, t.HOAccessTCHDropDis =

(g) TCHDrop

16,25,34] NRFLTCH[7, ailt.RadLinkFTCHDropDis =

(h)TCHDrop

17,26,35] NRFLTCH[8, cFailt.RemTransTCHDropDis =

(i)TCHDrop

18,27,36] NRFLTCH[9, r t.ConnOtheTCHDropDis =

(j)TCHDrop

]UNIHIALC[1 lHOt.IntraCelTCHDropDis =

(k) TCHDrop

]UNIHIRLC[1 lHOt.InterCelTCHDropDis =

(l)TCHDrop

DropInterBSCHO HOt.InterBSCTCHDropDis =

(m)TCHDrop

,10] NRCLRREQ[1 lt.EquipFaiTCHDropDis =

(n)TCHDrop

,14] NRCLRREQ[5 t.ProtErr TCHDropDis =

(o)TCHDrop

,15] NRCLRREQ[6 t.DistErr TCHDropDis =

(p)TCHDrop

,16] NRCLRREQ[7 t.PreemptTCHDropDis =

(q)TCHDrop

,17] NRCLRREQ[8 t.OAMTCHDropDis =

(r)TCHDrop

,18] NRCLRREQ[9 t.Other TCHDropDis =

Used param.: NRFLTCH[1..36], UNIHIALC[1], UNIHIRLC[1], InterBSCHODrop(11.3.3(a)),TCHDrop(6.1(a)), NRCLREQ[1..18]

Elem. Object: Cell

Unit: None

Remarks: Handover Access failures are included in formulas TCHDropDist.HOAccess and

8/13/2019 KPIs_SBS_BR_7



System

37 A30808-X3247-B912-1-7618

TCHDropDist.InterBSCHO. If the feature SDCCH Handover is activated, then thiswill lead to a systematic error.

8/13/2019 KPIs_SBS_BR_7


8/13/2019 KPIs_SBS_BR_7


8/13/2019 KPIs_SBS_BR_7



System

40 A30808-X3247-B912-1-7618

NRCLRREQ[4,13]; this also lead to triggering of NRCLRCMD[1,7] (“BSSinitiated”)

• Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENTCOMMAND (T10 Expiry): In that case the BSC sends Assignment Failureto the MSC and triggers TASSFAIL[6,11]; this also leads to triggering of

NRCLRCMD[2,8] (“Call Control”)• Unsuccessful Directed Retry, Intra-BSC, with Reversion to SDCCH

(T3124 Expiry): In that case the BSC sends Assignment Failure to theMSC and triggers TASSFAIL[7,12]; this also leads to triggering ofNRCLRCMD[2,8] (“Call Control”)

• No TCH available (no queuing): In that case the BSC sends AssignmentFailure to the MSC and triggers TASSFAIL[8,13]; this also leads totriggering of NRCLRCMD[2,8] (“Call Control”)

Systematic failures in the formulas:

• Inter BSC handover with reversion to old cell:

In that case the MSC receives HO_Failure from the old BSC and sendsClear Command (“equipment failure”) the target BSC which triggersNRCLRCMD[4] for the target cell-> this effect slightly improve the CallDropRate by pretending that morecall have existed than in reality.

• Inter BSC directed retry with no successful TCH seizure:In that case the BSC send assignment Failure and triggers Tassfail[9,14];this lead also to a Clear Command (“Call Control”) which triggersNRCLRCMD[2]-> this effect slightly improve the CallDropRate by pretending that morecall have existed than in reality.

• Expiry of timer T_MSRFPCI during assignment:In that case NRCLRREQ is triggered. This can only occur whenT_MSRFPCI is not well adjusted (< T10)-> this effect slightly deteriorates the call drop rate (numerator anddenominator are increased)

• There can be systematic errors caused by timer settings (Ny1, T3105,

TTrau, TSync, T_MSRFPCI, T8). If the feature SDCCH Handover isactivated, then this will lead to a systematic error.-> this effect slightly deteriorates the call drop rate (numerator anddenominator are increased)

Recommendation:Drop per Erlang/hour is recommended to be used for quality assessment of radionetwork performance. Reason: the call drop rate is depending on the average callduration. The call drop rate is proportional to the call duration.

8/13/2019 KPIs_SBS_BR_7



System

41 A30808-X3247-B912-1-7618

6.5 Mean Time between TCH Drop

Long name: (a) Mean Time between TCH Drop

Short name: (a) MTBTCHDrop

Description: This indicator will give you mean time between TCH Drop, by meaning the time inseconds until the occurrence of the loss of a TCH connection.

Formula:(a)

TCHDrop

60s*yGranularit*rDR TCHTrafCar MTBTCHDrop =

Used param.: TCHDrop(6.1(a)), TCHTrafCarrDR(8.1.4(c)), Granularity in minutes

Elem. Object: Cell

Unit: Seconds

Remarks: SDCCH Handovers are not considered and can therefore lead to systematic

errors.

6.6 TCH Drops per Erlanghour

Long name: (a) TCH Drops per Erlanghour

Short name: (a) TCHDropErlh

Description: This indicator will give you TCH Drops per Erlanghour., by meaning the numberof losses of TCH connections related to one Erlanghour.

Formula:(a) yGranularit

60*rDR TCHTrafCar

TCHDrop hTCHDropErl =

Used param.: TCHDrop(6.1(a)), TCHTrafCarrDR(8.1.4(c)), Granularity in minutes

Elem. Object: Cell

Unit: None

Remarks: SDCCH Handovers are not considered and can therefore lead to systematicerrors.

8/13/2019 KPIs_SBS_BR_7



System

42 A30808-X3247-B912-1-7618

7 SDCCH Drop related PerformanceIndicators

7.1 Number of dropped SDCCH Connections

Long name: (a) Number of dropped SDCCH Connections

Short name: (a) SDCCHDrop

Description: This indicator will give you the number of dropped SDCCH Connections, which canoccur for any call type (MOC, MTC, Locupd, SMS, ...).

Formula: (a) ,6,11]TASSFAIL[126]..2321,..9 NRCLRREQ[1 SDCCHDrop +=

Used param.: NRCLRREQ[19 .. 21, 23 .. 26], ,6,11]TASSFAIL[1

Elem. Object: Cell

Unit: None

Remarks: BR7 modification: KPI based on NRCLRREQ counters instead of NRCLRCMD.Reason: KPI shall indicate the drops caused by the BSC.

7.2 SDCCH Drop Rate

Long name: (a) SDCCH Drop Rate

(b) SDCCH Drop Rate per SDCCH connectionShort name: (a) SDCCHDropRate

(b) SDCCHDropConnRate

Description: This indicator will give you the rate all losses of connections during a SDCCHConnection.

Formula:(a)

..6] NSUCCHPC[1

SDCCHDrop ateSDCCHDropR =

(b)8]3,14,16..1 NRCLRCMD[1

SDCCHDrop onnRateSDCCHDropC =

Used param.: SDCCHDrop(7.1(a)), NSUCCHPC[1..6], NRCLRCMD[13,14,16..18]

Elem. Object: Cell

Unit: None

Remarks: MSC controlled SDCCH Handover drops are also counted (Expiry of Timer T8).BSC controlled SDCCH Handover drops are not counted and will lead to smallsystematic errors.

8/13/2019 KPIs_SBS_BR_7



System

43 A30808-X3247-B912-1-7618

7.3 Mean Time between SDCCH Drop

Long name: (a) Mean Time between SDCCH Drop

Short name: (a) MTBSDCCHDrop

Description: This indicator will give you mean time between SDCCH Drop, by meaning thetime in seconds until the occurrence of the loss of a SDCCH connection.

Formula:

(a)SDCCHDrop

60s*yGranularit*arrSDCCHTrafC opMTBSDCCHDr =

Used param.: SDCCHDrop(7.1(a)), SDCCHTrafCarr(9.2(a)) , Granularity in minutes

Elem. Object: Cell

Unit: Seconds

Remarks: SDCCH Handovers Drops are not considered.

7.4 SDCCH Drops per Erlanghour

Long name: (a) SDCCH Drops per Erlanghour

Short name: (a) SDCCHDropErlh

Description: This indicator will give you SDCCH Drops per Erlanghour., by meaning thenumber of losses of SDCCH connections related to one Erlang.

Formula:(a)

yGranularut

60*

arr SDCCHTrafC

SDCCHDrop rlhSDCCHDropE =

Used param.: SDCCHDrop(7.1(a)), SDCCHTrafCarr(9.2(a)), Granularity in minutes

Elem. Object: Cell

Unit: None

Remarks: SDCCH Handovers Drops are not considered.

8/13/2019 KPIs_SBS_BR_7



System

44 A30808-X3247-B912-1-7618

8 TCH Load related Performance Indicators

8.1 TCH Load for Circuit Switched Traffic

The following figure will give you an overview about the load related performanceindicators used in the traffic theory.

Fig. 7 Overview Load related performance indicators

For the estimation of the Load of GSM Telecom Systems the Erlang B formula fornon queuing Telefon Systems and the Erlang C formula for Queuing Telefon

Systems can be used. Further information about the traffic theory can be found in the‘Siemens Tabellenbuch Fernsprechtheorie ISBN 3-8009-1343-7’.

8.1.1 TCH Traffic Distribution Rate

Long name: (a) TCH Full Rate Traffic

(b) TCH Half Rate Traffic

Short name: (a) FRT

(b) HRT

Description: This indicator will give you the Rate of Full Rate and Half Rate traffic on TCHcompared to the total traffic.

Formula:(a)

[1..4]MEBUSTCH

3][1,MEBUSTCH FRT =

(b)[1..4]MEBUSTCH

4][2,MEBUSTCH HRT =

Used param.: MEBUSTCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: This KPI can be used by network planning to calculate the number of neededTRX.

8/13/2019 KPIs_SBS_BR_7



System

45 A30808-X3247-B912-1-7618

8.1.2 TCH Loss Rate

Long name: (a) TCH seizure blocked rate Full Rate

(b) TCH seizure blocked Rate Half Rate

(c) TCH seizure blocked Rate Dual Rate

(d) TCH seizure blocked Rate Waiting System Full Rate

(e) TCH seizure blocked Rate Waiting System Half Rate

(f) TCH seizure blocked Rate Waiting System Dual Rate

Short name: (a) TCHSeizBlckRateFR

(b) TCHSeizBlckRateHR

(c) TCHSeizBlckRateDR

(d) TCHSeizBlckRateWSFR

(e) TCHSeizBlckRateWSHR

(f) TCHSeizBlckRateWSDR

Description: This indicator will give you the TCH seizure blocked rate by meaning the ratewhere new TCH Seizure Attempts could not be handled by the observed cell,because all traffic channels were occupied / blocked.

TCH seizure attempts for HO and Directed Retry are included in the formulas.

Therefore from the perspective of a mobile subscriber, the call setup mightbecome successful by assigning a TCH in another cell through (e.g. by applyingthe feature Directed Retry) even when a TCH blocking is counted. I.e. the KPIs

consider the TCH access on cell level but not on connection level.

Performance Indicators for waiting systems are also provided and will consideronly the TCH Seizure attempts discarded from the TCH queue.

Formula:(a)

[1]ATTCHSEI

3][1,ATCHSMBS kRateFR TCHSeizBlc =

(b)[2]ATTCHSEI

4][2,ATCHSMBS kRateHR TCHSeizBlc =

(c)[1,2]ATTCHSEI

4]..[1ATCHSMBS kRateDR TCHSeizBlc =

(d)[1]ATTCHSEI

3][1, NMSGDISQ kRateWSFR TCHSeizBlc =

(e)[2]ATTCHSEI

[2,4] NMSGDISQ kRateWSHR TCHSeizBlc =

(f)[1..2]ATTCHSEI

[1..4] NMSGDISQ kRateWSDR TCHSeizBlc =

Used param.: ATCHSMBS[1..4], ATTCHSEI[1..2], NMSGDISQ[1..4]

Elem. Object: Cell

Unit: Subscriber redial behaviour influences the blocking rate.

8/13/2019 KPIs_SBS_BR_7



System

46 A30808-X3247-B912-1-7618

Further the HO periodicity timer influences the TCH blocking rate

Remarks: For Dual Rate Channels (formula c) the Full Rate and Half Rate channels mustbe weighted with the TCH Traffic distribution Rate.

Please note, after expiry of Timer THORQST an intercell or intracell handover willbe re-attempted and counter ATCHSMBS can be pegged again, if no resource is

still available.In BR 7.0 the measurement ATCHSMBS was modified to count also in case of

Abis pool congestion (extension of Trigger events-list). This fact does not affectthe meaning or definition of the KPI.

8.1.3 TCH Traffic Offered

Long name: (a) TCH Traffic Offered Full Rate

(b) TCH Traffic Offered Half Rate

(c) TCH Traffic Offered Dual RateShort name: (a) TCHTrafOffFR

(b) TCHTrafOffHR

(c) TCHTrafOffDR

Description: This indicator will give you the theoretical amount of traffic in Erlang which wasoffered to a cell.

The indicators comprise the traffic explicitly induced by mobile subscribers andalso additional virtual traffic emerged from radio network internal features likeDirected retry and Handover. In the course of the performance of these twofeatures a traffic demand my be offered successively to more than one possible

target cell.Use case: Radio network capacity planning:

The indicators may be used for radio network capacity planning. But they shouldnot be used isolated since they pretend a higher demand of TCH resources asneeded in reality for mobile subscriber satisfaction. The indicators should ratherbe used in connection with subscriber satisfaction oriented indicators (e.g. referto chapter 5.5 (g): Call Setup Failure Rate due to TCH Loss)

Formula:(a)

eFR TCHLossRat-1

3][1,MEBUSTCH FR TCHTrafOff =

(b)eHR TCHLossRat-1

4][2,MEBUSTCH HR TCHTrafOff =

(c) HR TCHTrafOff FR TCHTrafOff DR TCHTrafOff +=

Used param.: MEBUSTCH[1..4] , TCHLossRateFR(8.1.2(a)), TCHLossRateHR(8.1.2(b))

Elem. Object: Cell

Unit: Erlang

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

47 A30808-X3247-B912-1-7618

8.1.4 TCH Traffic Carried

Long name: (a) TCH Traffic Carried Full Rate

(b) TCH Traffic Carried Half Rate

(c) TCH Traffic Carried Dual Rate

Short name: (a) TCHTrafCarrFR

(b) TCHTrafCarrHR

(c) TCHTrafCarrDR

Description: This indicator will give you the amount of carried traffic in Erlang on TCH.

Formula: (a) 3][1,MEBUSTCHrFR TCHTrafCar =

(b) 4][2,MEBUSTCHrHR TCHTrafCar =

(c) rHR TCHTrafCar rFR TCHTrafCar rDR TCHTrafCar +=

Used param.: MEBUSTCH[1..4]Elem. Object: Cell

Unit: Erlang

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

48 A30808-X3247-B912-1-7618

8.1.5 TCH Traffic Lost

Long name: (a) TCH Traffic Lost Full Rate

(b) TCH Traffic Lost Half Rate

(c) TCH Traffic Lost Dual Rate(d) TCH Traffic Lost Waiting System Full Rate

(e) TCH Traffic Lost Waiting System Half Rate

(f) TCH Traffic Lost Waiting System Dual Rate

Short name: (a) TCHTrafLostFR

(b) TCHTrafLostHR

(c) TCHTrafLostDR

(d) TCHTrafLostWSFR

(e) TCHTrafLostWSHR

(f) TCHTrafLostWSDR

Description: This indicator will give you the amount of circuit switched traffic (measured inErlang), which was lost for a cell due to lack of TCH resources.

The indicators are not related to the loss of traffic a subscriber experiences. If forexample during HO execution a certain target cell candidate is fully occupied thissituation is counted as lost traffic for that target cell; but from the perspective ofthe subscriber the HO might become successful in another target cell.

Additional indicator deal with waiting systems (queuing):

• Amount of circuit switched traffic (measured in Erlang), which was lostdue to discard from the TCH waiting queue.

Formula: (a) rFR TCHTrafCar -FR TCHTrafOff tFR TCHTrafLos =

(b) rHR TCHTrafCar -HR TCHTrafOff tHR TCHTrafLos =

(c) rDR TCHTrafCar -DR TCHTrafOff tDR TCHTrafLos =

(d)60s*yGranularit

TCHMHTFR *3], NMSGDISQ[1tWSFR TCHTrafLos =

(e) ,4] NMSGDISQ[2tWSHR TCHTrafLos =60s*yGranularit

TCHMHTHR *

(f) ..4] NMSGDISQ[1tWSDR TCHTrafLos =60s*yGranularit

TCHMHTDR *

Used param.: TCHTrafOffFR(8.1.3(a)), TCHTrafOffHR(8.1.3(b)), TCHTrafOffDR(8.1.3(c)),

TCHTrafCarrFR(8.1.4(a)), TCHTrafCarrHR(8.1.4(b)), TCHTrafCarrDR(8.1.4(c))

NMSGDISQ[1..4], TCHMHTFR (8.1.7(a)), TCHMHTHR(8.1.7(b)),TCHMHTDR(8.1.7(c)),

Elem. Object: Cell

Unit: Erlang

Remarks: BR7: correction of TCHTrafLostxx formulas

8/13/2019 KPIs_SBS_BR_7



System

49 A30808-X3247-B912-1-7618

8.1.6 TCH Blocking Rate

Long name: (a) TCH Blocking Rate Full Rate

(b) TCH Blocking Rate Half Rate

(c) TCH Blocking Rate Dual RateShort name: (a) TCHBlockRateFR

(b) TCHBlockRateHR

(c) TCHBlockRateDR

Description: This indicator will give you the TCH Blocking Rate by meaning the rate were alltraffic channels were occupied.

Formula:(a)

60s*yGranularit

]AALTCHTI[1 teFR TCHBlockRa =

(b) 60s*yGranularit

]AALTCHTI[4

teHR TCHBlockRa =

(c) HRT*teHR TCHBlockRaFRT*teFR TCHBlockRateDR TCHBlockRa +=

Used param.: AALTCHTI[1,4], FRT(8.1.1(a)), HRT(8.1.1(b)), Granularity in Minutes

Elem. Object: Cell

Unit: None

Remarks: For Dual Rate Channels (formula c) the Full Rate and Half Rate channels mustbe weighted with the TCH Traffic distribution Rate. Due to feature ‘SmoothChannel Modification’ the measurement type AALTCHTI keeps track of thenumber of timeslots belonging to the TCH_Pool, TCH/SD_Pool and

SDCCH_Backup Pool.

8/13/2019 KPIs_SBS_BR_7



System

50 A30808-X3247-B912-1-7618

8.1.7 TCH Mean Holding Time

Long name: (a) TCH Mean Holding Time Full Rate

(b) TCH Mean Holding Time Half Rate

(c) TCH Mean Holding Time Dual Rate

Short name: (a) TCHMHTFR

(b) TCHMHTHR

(c) TCHMHTDR

Description: This indicator will give you the mean holding Time in seconds for occupied TCHsin a cell.

Formula:(a)

3][1,TNTCHCL

60*yGranularit*,3]MEBUSTCH[1 TCHMHTFR =

(b)

4][2,TNTCHCL

60*yGranularit*,4]MEBUSTCH[2 TCHMHTHR =

(c)[1..4]TNTCHCL

60*yGranularit*..4]MEBUSTCH[1 TCHMHTDR =

Used param.: MEBUSTCH[1..4], TNTCHCL[1..4], Granularity in minutes

Elem. Object: Cell

Unit: Seconds

Remarks: A weighting with the TCH Traffic distribution Rate is not necessary here, becauseErlang values are used.

8/13/2019 KPIs_SBS_BR_7



System

51 A30808-X3247-B912-1-7618

8.1.8 TCH Traffic Util ization

Long name: (a) TCH Traffic Utilisation Full Rate

(b) TCH Traffic Utilisation Half Rate

(c) TCH Traffic Utilisation Dual Rate

Short name: (a) TCHTrafUtilFR

(b) TCHTrafUtilHR

(c) TCHTrafUtilDR

Description: This indicator will give you the theoretical TCH Traffic Utilization Rate by meaningof the carried traffic divided through the Erlang B function.

Formula:(a)

A

,3]MEBUSTCH[1 lFR TCHTrafUti =

Erlang B formula:

B)[2,8],f(NRDEFTCHB)f(N,A == Erlang C formula:

])MDURTCRQ[1],MTCHQLEN[1B,[2,8],f(NRDEFTCH)Q,QB,f(N,A dl ==

(b)A

,4]MEBUSTCH[2 lHR TCHTrafUti =

Erlang B formula:

B)[5,11],f(NRDEFTCHB)f(N,A ==

Erlang C formula

])MDURTCRQ[2],MTCHQLEN[2B,[5,11],f(NRDEFTCH)Q,QB,f(N,A dl ==

(c) A

..4]MEBUSTCH[1 lDR TCHTrafUti =

Erlang B formula:

B),[2,5,8,11]f(NRDEFTCHB)f(N,A ==

Erlang C formula:,2])MDURTCRQ[1,2],MTCHQLEN[1B,,[2,5,8,11]f(NRDEFTCH)Q,QB,f(N,A dl ==

with A = Offered Load in ErlangB = Blocking Probability (Planning Parameter)

Used param.: MEBUSTCH[1..4], NRDEFTCH [2,5,8,11], MTCHQLEN[1,2], MDURTCRQ[1,2]

Elem. Object: Cell

Unit: None

Remarks: If Queuing is activated, Erlang C instead of Erlang B formula has to be taken. Aweighting with the TCH Traffic distribution Rate is not necessary here, becauseErlang values are used.

8/13/2019 KPIs_SBS_BR_7



System

52 A30808-X3247-B912-1-7618

8.2 Combined time slot ut ilisation for CS and PO Traffic

8.2.1 Combined time slot occupation rate for CS and PO Traffic

Long name: (a) Mean overall time slot occupation rate for CS and PO Traffic

Short name: (a) MeaOcTsC

Description: This KPI provided the mean occupation rate of those timeslots of a cell, whichcan be assigned to users.

All timeslots are considered independent if they are dedicated to CS or PO Traffic

or if they can be used for both types of traffic.

Only those timeslots are considered, which bear logical channels, which areunder control of radio resource management (TCH, SDCCH, PDTCH); i.e. thetimeslot consumption for common control channels and broadcast controlchannels is not considered.

Formula: (a) MeaOcTsC =

]/8 NDESDCCH[3] NDFTCHSD[12/,12] NRDEFTCH[6,9] NRDEFTCH[3] NDEFPDCH[3

[1]/8MBUSYSDC[2,4]/2MEBUSTCH[1,3]MEBUSTCH[3,6] NALLPDCH

+++++++

Used param.: NDEFPDCH[3]: number of defined PDCH,

NALLPDCH [3,6]: mean number of occupied PDCH UL and DL

(active TBF)

NRDEFTCH[3,6,9,12]: mean number of defined TCH

[3,9] full rate, [6,12] half rate (1/2 time slot)

NDESDCCH[3]: mean number of defined SDCCHs (1/8 time slots)

NDFTCHSD[1]: mean number of defined TCH/SD

MEBUSTCH [1 .. 4]: Mean Number of busy TCHs

[1,3] full rate, [2,4] half rate (1/2 time slot)MBUSYSDC [1]: Mean Number of busy SDCCHs (1/8 time slots)

Elem. Object: Cell

Unit: None

Remarks: NALLPDCH: Mean number of active TBF PDCH

NDEFPDCH (and NAVPDCH) include also the packet channels used as PBCCHand PCCCH; but NALLPDCH does not contain these channels. This leads to asystematic error. Improvement by BR8 FRS 86899:

8/13/2019 KPIs_SBS_BR_7



System

53 A30808-X3247-B912-1-7618

8.2.2 Combined time slo t availabil ity rate for CS and PO Traffic

Long name: (b) Mean overall time slot availability rate for CS and PO Traffic

Short name: (b) MeaAvTsC

Description: This KPI provided the availability rate of those timeslots of a cell, which can beassigned to users.

All timeslots are considered independent if they are dedicated to CS or PO Trafficor if they can be used for both types of traffic.

Only those timeslots are considered, which bear logical channels, which areunder control of radio resource management (TCH, SDCCH, PDTCH); i.e. thetimeslot consumption for common control channels and broadcast control

channels is not considered.

Formula: (b) MeaAvTsC =

]/8 NDESDCCH[3] NDFTCHSD[12/,12] NRDEFTCH[6,9] NRDEFTCH[3] NDEFPDCH[3

]/8 NAVSDCCH[3/22] NAVTCH[6,1] NAVTCH[3,9 NAVPDCH[3]

+++++++

Used param.: NDEFPDCH[3]: number of defined PDCH,

NAVPDCH[3]: number of available PDCH,

NRDEFTCH[3,6,9,12]: mean number of defined TCH

[3,9] full rate, [6,12] half rate (1/2 time slot)

NAVTCH[3,6,9,12]: mean number of Available TCHs[3,9] full rate, [6,12] half rate (1/2 time slot)

NDESDCCH[3]: mean number of defined SDCCHs (1/8 time slots)

NAVSDCCH[3]: mean number of available SDCCHs (1/8 time slots)

NDFTCHSD[1]: mean number of defined TCH/SD

NAVTCHSD[3]: mean number of available TCH/SD

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

54 A30808-X3247-B912-1-7618

9 SDCCH Load related PerformanceIndicators

The following figure will give you an overview about the load related performanceindicators used in the traffic theory.

Fig. 8 Overview Load related performance indicators

For the estimation of the Load of GSM Telecom Systems the Erlang B formula canbe used. Further information about the traffic theory you can find in the ‘Siemens

Tabellenbuch Fernsprechtheorie ISBN 3-8009-1343-7’.

9.1 SDCCH Traffic OfferedLong name: (a) SDCCH Traffic Offered

Short name: (a) SDCCH TrafOff

Description: This indicator will give you the amount of traffic in Erlang on SDCCH the MSsubscribers wanted to have due to the traffic theorie.

Formula:(a)

ateSDCCHLossR -1

[1]MBUSYSDC ff SDCCHTrafO =

Used param.: MBUSYSDC[1], SDCCHLossRate(9.5(a))

Elem. Object: Cell

Unit: Erlang

Remarks: None

Number ofchannels N

Traffic Offered A [Erl]Call Attempts CA

Traffic Carried Y [Eel]Calls Carried CC

Traffic Lost [Erl]Calls Rejected CRLoss B

8/13/2019 KPIs_SBS_BR_7



System

55 A30808-X3247-B912-1-7618

9.2 SDCCH Traffic Carried

Long name: (a) SDCCH Traffic Carried

Short name: (a) SDCCH TrafCarr

Description: This indicator will give you the amount of carried traffic in Erlang on SDCCH.

Formula: (a) [1]MBUSYSDCarrSDCCHTrafC =

Used param.: MBUSYSDC[1]

Elem. Object: Cell

Unit: Erlang

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

56 A30808-X3247-B912-1-7618

9.3 SDCCH Traffic Lost

Long name: (a) SDCCH Traffic Lost

Short name: (a) SDCCHTrafLost

Description: This indicator will give you the amount of traffic in Erlang on SDCCH which werelost (e.g. Blockings).

Formula: (a) arr SDCCHTrafC-ff SDCCHTrafOostSDCCHTrafL =

Used param.: SDCCHTrafOff(9.1(a)), SDCCHTrafCarr(9.2(a))

Elem. Object: Cell

Unit: Erlang

Remarks: None

9.4 SDCCH Blocking Rate

Long name: (a) SDCCH Blocking Rate

Short name: (a) SDCCHBlockRate

Description: This indicator will give you the SDCCH Blocking Rate by meaning the rate whereall SDCCH were occupied.

Formula:(a)

60s*yGranularit

[1]ASDCALTI RateSDCCHBlock =

Used param.: ASDCALTI[1], Granularity in minutes

Elem. Object: Cell

Unit: None

Remarks: Due to feature ‘Smooth Channel Modification’ the measurement type ASDCALTIkeeps track of the number of timeslots belonging to the SDCCH_Pool andSDCCH_Backup_Pool and TCH/SD_Pool.

8/13/2019 KPIs_SBS_BR_7



System

57 A30808-X3247-B912-1-7618

9.5 SDCCH Loss Rate

Long name: (a) SDCCH Loss Rate

Short name: (a) SDCCHLossRate

Description: This indicator will give you the SDCCH Traffic Loss Rate by meaning the ratewhere new SDCCH Seizure Attempts could not be handled, because all SDCCHwere occupied / blocked.

Formula:(a)

[1] NATTSDPE

[1]ATSDCMBS ateSDCCHLossR =

Used param.: ATSDCMBS[1], NATTSDPE[1]

Elem. Object: Cell

Unit: None

Remarks: None

9.6 SDCCH Mean Holding Time

Long name: (a) SDCCH Mean Holding Time

Short name: (a) SDCCHMHT

Description: This indicator will give you the mean holding Time in seconds for occupiedSDCCH in a cell.

Formula: (a)..6] NSUCCHPC[1

60s*yGranularit*[1]MBUSYSDC SDCCHMHT =

Used param.: MBUSYSDC[1], NSUCCHPC[1..6], Granularity in minutes

Elem. Object: Cell

Unit: Seconds

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

58 A30808-X3247-B912-1-7618

9.7 SDCCH Traffic Utilisation

Long name: (a) SDCCH Traffic Utilisation

Short name: (a) SDCCHTrafUtil

Description: This indicator will give you the SDCCH Traffic Utilisation by meaning of thecarried traffic divided through the number of available SDCCH.

Formula:(a)

A

]MBUSYSDC[1 tilSDCCHTrafU =

Erlang B formula:

B)[2],f(NDESDCCHB)f(N,A ==

with A = Offered Load in ErlangB = Blocking Probability (Planning Parameter)

Used param.: MBUSYSDC[1], NDESDCCH[2]

Elem. Object: CellUnit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

59 A30808-X3247-B912-1-7618

10 Other Load related Performance Indicators

10.1 PCH Accesses

Long name: (a) Number of Paging Channel Accesses

Short name: (a) PCHAcc

Description: This indicator will give you the number of paging commands received by the BTSand transmitted via paging request message over the air interface.

Formula: a) PCHAcc = NTDMPCH[1,2]

Used param.: NTDMPCH[1..2]

Elem. Object: Cell

Unit: None

Remarks: In BR 7.0 the counter NTDPMAIN(2,1) was renamed to NTDMPCH(2,1). Also twonew subcounters were added in order to distinguish between CS traffic and PStraffic.

10.2 PCH Rejection Rate

Long name: (a) PCH Rejection Rate

Short name: (a) PCHRejRate

Description: This indicator will give you the PCH Rejection Rate by meaning the number ofdiscarded paging commands' from the paging queue divided by the total numberof paging commands received by the BTS.

Formula: (a)]4..1[ NTDMPCH

4] NTDMPCH[3,PCHRejRate =

Used param.: NTDMPCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: In BR 7.0 the counter NTDPMAIN(2,1) was renamed to NTDMPCH(2,1). Also twonew subcounters were added in order to distinguish between CS traffic and PS

traffic.

10.3 PPCH Accesses

Long name: (a) Number of Packet Paging Channel Accesses

Short name: (a) PPCHAcc

Description: This indicator will give you number of transmitted messages over the packet

paging channel (PPCH) at the air interface.

Formula: a) PPCHAcc = NTDMPPCH[1,2]

8/13/2019 KPIs_SBS_BR_7



System

60 A30808-X3247-B912-1-7618

Used param.: NTDMPPCH[1..2]

Elem. Object: Cell

Unit: None

Remarks: None

10.4 PPCH Rejection Rate

Long name: (b) PPCH Rejection Rate

Short name: (b) PPCHRejRate

Description: This indicator will give you the PPCH Rejection Rate by meaning the number ofdiscarded paging commands' from the packet paging queue divided by the totalnumber of paging commands treated in total by the PCU

Formula: (b)]4..1[

,4] NTDMPPCH[3ePPCHRejRat NTDMPPCH =

Used param.: NTDMPPCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: None

10.5 AGCH Accesses

Long name: (a) Number of AGCH Accesses

Short name: (a) AGCHAcc

Description: This indicator will give you number of sent AGCH (Access Grant Channel)messages on the air interface.

Formula: AGCHAcc = NTDMAGCH [1,2]

Used param.: NTDMAGCH [1,2]

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

61 A30808-X3247-B912-1-7618

10.6 AGCH Rejection Rate

Long name: (a) AGCH Rejection Rate

Short name: (a) AGCHRejRate

Description: This indicator will give you the AGCH Rejection Rate by meaning the number ofdiscarded AGCH commands' from the AGCH queue divided by the total number of

AGCH commands received by the BTS.

Formula:(a)

]4..1[ NTDMAGCH

]4,3[ NTDMAGCHeAGCHRejRat =

Used param.: NTDMAGCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: None

10.7 PAGCH Accesses

Long name: (a) Number of PAGCH Accesses

Short name: (a) PAGCHAcc

Description: This indicator will give you number of sent PAGCH (Packet Access Grant Channel)messages on the air interface.

Formula: (a) PAGCHAcc = NTDMPAGC [1]

Used param.: NTDMPAGC [1]

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

62 A30808-X3247-B912-1-7618

10.8 PAGCH Rejection Rate

Long name: (a) PAGCH Rejection Rate

Short name: (a) PAGCHRejRate

Description: This indicator will give you the PAGCH (packet access grant channel) Rejectionrate by meaning the number of PAGCH commands discarded from the PAGCHqueue divided by the number of PAGCH commands treated in total by the PCU.

Formula:(a) P

]2,1[

]2[eAGCHRejRat

NTDMPAGC

NTDMPAGC =

Used param.: NTDMPAGC[1,2]

Elem. Object: Cell

Unit: None

Remarks: None

10.9 RACH Accesses

Long name: (a) Number of RACH Accesses

Short name: (a) RACHAcc

Description: This indicator will give you number of successful detected RACH (Random AccessChannel) messages on the air interface.

Formula: (a) RACHAcc = NACSUCPR[3]Used param.: NACSUCPR[3]

Elem. Object: Cell

Unit: None

Remarks: None

10.10 Invalid RACH Signal Rate

Long name: (a) Invalid RACH Signal RateShort name: (a) RACHInvSigRate

Description: This indicator will give you the ‘Invalid RACH Signal Rate’ by meaning the numberof 'invalid' RACH signals received on the RACH (i.e. RACH signals that wereclassified as 'not noisy' but were discarded as 'invalid' due to excessive distance,invalid CRC checksum, or a too weak signal level) divided by the sum of1. the number of the discarded ‘invalid’ RACH signals (as described above) and2. the number of RACH signals that lead to a CHANNEL REQUIRED procedure.

Formula:

(a)

]3[..3] NINVRACH[1

..3] NINVRACH[1RateRACHInvSig

NACSUCPR+

=

Used param.: NINVRACH [1..3], NACSUCPR[3]

8/13/2019 KPIs_SBS_BR_7



System

63 A30808-X3247-B912-1-7618

Elem. Object: Cell

Unit: None

Remarks: Attention:

It has to be considered that the NINVRACH does not represent the total amount ofall RACH signals that are discarded by the BTS!

The Um layer 1 SW subsystem of the BTS continuously observes the signalsreceived on the RACH slots. As even without any real MS RACH access there arealways at least some ‘noise’ signals on the RACH, the task of the BTS layer 1 SWsubsystem is to evaluate the received signal with respect to specific criteria thatclassify as signal as 'noisy' or 'not noisy'. These checks are performed prior to theevaluation of the criteria 'excessive distance', 'signal level too weak' and 'CRCchecksum error'. Signals classified as 'not noisy' are immediately discarded andare not counted by NINVRACH (!).

An increase of the NINVRACH counts and thus an increase of the ‘Invalid RACHSignal Rate’ as calculated by the above formula does not mean a worseperformance of the BTS. Instead, variations of the NINVRACH counts and

variations of the 'Invalid RACH Signal Rate' between the different sites mainlydepend on the radio environment conditions, i.e. increased values of NINVRACHand the KPI ‘Invalid RACH Signal Rate’ are no indication for a poor systemperformance. Moreover, both figures depend on characteristics of the used TRXHW (old HW usually shows lower counter values, although the performance of thenewer HW is better !).

For this r eason the above formula cannot be regarded as a ‘SystemPerformance Indicator’ but rather provides, taking into account which TRXHW is used, a rough idea about the radio conditions that influence the RACHperformance!

For further details please refer to the NINVRACH counter description in the

document 'PM:SBS Counter'.

10.11 Abis pool supervision

Abis Pool Evaluation (background information)

With the above measurements it is possible to evaluate the most important load related keyperformance indicators for the Abis Pool. The following figure will give you an overview aboutthe load related performance indicators used in the traffic theory and mapped to the AbisPool.

8/13/2019 KPIs_SBS_BR_7



System

64 A30808-X3247-B912-1-7618

For planning of the Abis capacity and the estimation of the expected load on the AbisInterface the Erlang B formula can be taken. Further information about the traffic theory canbe found in the ‘Siemens Tabellenbuch Fernsprechtheorie ISBN 3-8009-1343-7’.

The following key performance indicators can be evaluated for the Abis Pool:

(a) N = Mean number of defined Abis subchannels = ABISPSUP[1]

(b) Mean number of available Abis subchannels = ABISPSUP[2]

(c) Abis subchannel availability rate = (b) / (a)

(d) CA = Number of att. Abis subchannel seizures = (e) + (f)

(e) CC = Number of suc. Abis subchannel seizures = ABISPSUP[6]

(f) CR = Number of unsuc. Abis subchannel seizure att. = ABISPSUP[7]

(g) A = Abis Pool Traffic offered = (h) + (i)

(h) Y = Abis Pool Traffic carried = ABISPSUP[3]

(i) A = Y + A*B

R = A*Bó

A = Y/(1-B)è R = Y/(1-B) * B = Y * B / (1-B)

R = Abis Pool Traffic lost = ((h) * (j) / (1 - (j))

(j) B = Abis Pool Loss Rate = (f) / ( (e) + (f) )

(k) Abis Pool Blocking Probability = ABISPSUP[5]/ gran

(l) Abis Pool Traffic Utilisation = (h) / (a)

(m) Abis Pool Peak Traffic Utilisation = ABISPSUP[4] / (a)

Abis Pool KPI formal definition

Long name: (a) Mean number of defined Abis subchannels

(b) Mean number of available Abis subchannels

(c) Abis subchannel availability rate

(d) Number of attempted Abis subchannel seizures

(e) Number of successful Abis subchannel seizures

(f) Number of unsuccessful Abis subchannel seizure attempts

(g) Abis Pool Traffic offered

(h) Abis Pool Traffic carried

(i) Abis Pool Traffic lost(j) Abis Pool Loss Rate

(k) Abis Pool Blocking Probability

(l) Abis Pool Traffic Utilisation

(m) Abis Pool Peak Traffic Utilisation

Short name: (a) AbisPDefCh

(b) AbisPAvailCh

(c) AbisPAvailRate

(d) AbisPAttSeiz

(e) AbisPSuccSeiz

(f) AbisPUnsuccSeiz

(g) AbisPTrOff

8/13/2019 KPIs_SBS_BR_7



System

65 A30808-X3247-B912-1-7618

(h) AbisPTrCar

(i) AbisPTrLost

(j) AbisPLossRate

(k) AbisPBlockProb

(l) AbisPTrafUtil

(m) AbisPTrafUtilPeak

Description: Key performance indicators for the Abis Pool:

Formula: (a) ]ABISPSUP[1AbisPDefCh =

(b) ]ABISPSUP[2ChAbisPAvail =

(c)]ABISPSUP[1

]ABISPSUP[2 RateAbisPAvail =

(d) ]ABISPSUP[7]ABISPSUP[6izAbisPAttSe +=

(e) ]ABISPSUP[6eizAbisPSuccS = (f) ]ABISPSUP[7cSeizAbisPUnsuc =

(g) )]ABISPSUP[6

]ABISPSUP[7(1*]ABISPSUP[3AbisPTrOff +=

(h) ]ABISPSUP[3AbisPTrCar =

(i)]ABISPSUP[6

]ABISPSUP[7 *]ABISPSUP[3tAbisPTrLos =

(j)]ABISPSUP[7]ABISPSUP[6

]ABISPSUP[7 ateAbisPLossR

+=

(k)gran

]ABISPSUP[5 ProbAbisPBlock =

(l)]ABISPSUP[1

]ABISPSUP[3 tilAbisPTrafU =

(m)]ABISPSUP[1

]ABISPSUP[4 tilPeakAbisPTrafU =

Used param.: ABISPSUP[1 - 7]

Elem. Object: Cell

Unit: NoneRemarks: BR7: New KPIs

8/13/2019 KPIs_SBS_BR_7



System

66 A30808-X3247-B912-1-7618

11 Handover related Performance Indicators

11.1 Intra Cell Handovers

11.1.1 Handover Success Rate

Long name: (a) Number of Intra Cell Handover Attempts

(b) Number of Intra Cell Handover Successes

(c) Intra Cell Handover Success Rate

(d) Intra Cell Handover Success Rate per cause

Short name: (a) IntraCellHOAtt

(b) IntraCellHOSucc

(c) IntraCellHOSuccRate

(d) IntraCellHOSuccRateC

Description: These indicators will give you the number and rate of successful Intra CellHandovers.

The indicators on the HO success rate are provided as an aggregation over all HOcauses and are provided in addition separated per HO cause value

Formula: (a) ..12]ATINHIAC[1OAttIntraCellH = (b) ..12]SINTHITA[1OSuccIntraCellH =

(c)OAttIntraCellH

OSuccIntraCellH OSuccRateIntraCellH =

(d)]ATINHIAC[c

]SINTHITA[c [c]OSuccRateCIntraCellH =

with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 inner to complete areac=4 complete to inner areac=5 near to far areac=6 far to near areac=7 forced handover due to O&Mc=8 TCH/F to TCH/H due to AMRc=9 TCH/H to TCH/F due to AMRc=10 forced intracell handover due to enhanced pairingc=11 forced intracell handover due to preferred TRXc=12 forced HO due to Multislot calls

Used param.: SINTHITA[1..12], ATINHIAC[1..12]

Elem. Object: Cell

Unit: None

8/13/2019 KPIs_SBS_BR_7



System

67 A30808-X3247-B912-1-7618

Remarks: SDCCH handovers are also incremented in this formulas.

8/13/2019 KPIs_SBS_BR_7



System

68 A30808-X3247-B912-1-7618

11.1.2 Handover Failure Rate

Long name: (a) Number of Intra Cell Handover Failures

(b) Intra Cell Handover Failure Rate

(c) Intra Cell Handover Failure Rate per Handover CauseShort name: (a) IntraCellHOFail

(b) IntraCellHOFailRate

(c) IntraCellHOFailRateC

Description: These indicators will give you the number and rate of Intra Cell HandoverFailures by meaning of unsuccessful Handovers without loss of MS connectionbecause of reversion to old cell.

The indicators on the HO failure rate are provided as an aggregation over allHO causes and are provided in addition separated per HO cause value

Formula: (a) 1..12]UNINHOIA[OFailIntraCellH =

(b)OAttIntraCellH

OFailIntraCellH OFailRateIntraCellH =

(c)]ATINHIAC[c

]UNINHOIA[c [c]OFailRateCIntraCellH =

with c for the HO cause number:c=1 uplink qualityc=2 downlink qualityc=3 inner to complete areac=4 complete to inner area

c=5 near to far areac=6 far to near areac=7 forced handover due to O&Mc=8 TCH/F to TCH/H due to AMRc=9 TCH/H to TCH/F due to AMRc=10 forced intracell handover due to enhanced pairingc=11 forced intracell handover due to preferred TRXc=12 forced HO due to Multislot calls

Used param.: UNINHOIA[1..12], , ATINHIAC[1..12], IntraCellHOAtt (11.1.1(a))

Elem. Object: CellUnit: None


8/13/2019 KPIs_SBS_BR_7



System

69 A30808-X3247-B912-1-7618

11.1.3 Handover Drop Rate

Long name: (a) Number of Intra Cell Handover Drops

(b) Intra Cell Handover Drop Rate(c) Intra Cell Handover Drop Rate per Handover Cause

Short name: (a) IntraCellHODrop

(b) IntraCellHODropRate

(c) IntraCellHODropRateC

Description: These indicators will give you the number and rate of Intra Cell Handover Drops bymeaning of unsuccessful Handovers with loss of MS connection.

The indicators on the HO drop rate are provided as an aggregation over all HOcauses and are provided in addition separated per HO cause value

Formula: (a) 1]UNIHIALC[ODropIntraCellH =

(b)OAttIntraCellH

ODropIntraCellH ODropRateIntraCellH =

(c)]ATINHIAC[c

]UNINHOIA[c-]SINTHITA[c-]ATINHIAC[c [c]ODropRateCIntraCellH =

with c for the HO cause number:c=1 uplink qualityc=2 downlink quality

c=3 inner to complete areac=4 complete to inner areac=5 near to far areac=6 far to near areac=7 forced handover due to O&Mc=8 TCH/F to TCH/H due to AMRc=9 TCH/H to TCH/F due to AMRc=10 forced intracell handover due to enhanced pairingc=11 forced intracell handover due to preferred TRXc=12 forced HO due to Multislot calls

Used param.: UNIHIALC[1], ATINHIAC[1..12], SINTHITA[1..12], UNINHOIA[1..12],IntraCellHOAtt (11.1.1(a))

Elem. Object: Cell

Unit: None

Remarks: SDCCH handovers are also incremented in this formulas. User release duringHandover will lead to very small systematic errors.

8/13/2019 KPIs_SBS_BR_7



System

70 A30808-X3247-B912-1-7618

11.1.4 Handover Distribut ion

Long name: (a) Intra Cell Handover Distribution per Handover cause

Short name: (a) IntraCellHODist

Description: These indicators will give you the Intra Cell Handover Distribution for analyzing thereason (=cause) for started Intra Cell Handovers.

Formula:(a)

OAttIntraCellH

]ATINHIAC[c ODist[c]IntraCellH =

with c for the HO cause number:c=1 uplink qualityc=2 downlink qualityc=3 inner to complete areac=4 complete to inner area

c=5 near to far areac=6 far to near areac=7 forced handover due to O&Mc=8 TCH/F to TCH/H due to AMRc=9 TCH/H to TCH/F due to AMRc=10 forced intracell handover due to enhanced pairingc=11 forced intracell handover due to preferred TRXc=12 forced HO due to Multislot calls

Used param.: ATINHIAC[1..12], IntraCellHOAtt (11.1.1(a))

Elem. Object: Cell

Unit: None


11.1.5 SDCCH Handover Success Rate

Long name: Intra Cell SDCCH Handover Success Rate

Short name: IntraCellSDHOSuccRate

Description: These indicators will give you the rate of successful Intra Cell SDCCH

Handovers.Formula:

]AISHINTR[1

]SISHINTR[1 eDHOSuccRatIntraCellS =

Used param.: SISHINTR[1], AISHINTR[1]

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

71 A30808-X3247-B912-1-7618

11.2 Inter Cell Intra BSC Handovers


Long name: (a) Number of Inter Cell Intra BSC Handover Attempts

(b) Number of Inter Cell Intra BSC Handover Successes

(c) Inter Cell Intra BSC Handover Success Rate

(d) Inter Cell Intra BSC Handover Success Rate per cause

Short name: (a) InterCellHOAtt

(b) InterCellHOSucc

(c) InterCellHOSuccRate

(d) InterCellHOSuccRateC

Description: These indicators will give you the number and rate of successful Inter Cell Intra

BSC Handovers per neighbor cell relation.

The indicators are provided as an aggregation over all HO causes and areadditionally provided per HO cause value (latter only for HO success rate)

Formula:

(a) ∑ ∑= =

++=11

1C

3

0

c]11*44*AOUINIRH[nOAtt[n]InterCellHi

i

(b) ∑∑= =

++=11

1C

3

0

c]11*44*SOUINIRH[nOSucc[n]InterCellHi

i

(c)OAtt[n]InterCellH

OSucc[n]InterCellH n]OSuccRate[InterCellH =

(d)

∑

∑

=

=

++

++=

3

0

3

0

c]11*44*AOUINIRH[n

c]11*44*SOUINIRH[n

c][n,OSuccRateCInterCellH

i

i

i

i

with n for the number of the neighbourcell relation (n=0..31)

with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to O&Mc=9 trafficc=10 fast uplinkc=11 forced handover due to preemption

with i for the type of cell area:i = 0 complete-complete areai = 1 complete-inner area

8/13/2019 KPIs_SBS_BR_7



System

72 A30808-X3247-B912-1-7618

i = 2 inner-complete areai = 3 inner-inner area

Used param.: AOUINIRH[all], SOUINIRH[all]

Elem. Object: Neighbourcell

Unit: None


8/13/2019 KPIs_SBS_BR_7



System

73 A30808-X3247-B912-1-7618


Long name: (a) Number of Inter Cell Intra BSC Handover Failures

(b) Inter Cell Intra BSC Handover Failure Rate(c) Inter Cell Intra BSC Handover Failure Rate per Handover Cause

Short name: (a) InterCellHOFail

(b) InterCellHOFailRate

(c) InterCellHOFailRateC

Description: These indicators will give you the number and rate of Inter Cell Intra BSCHandover Failures by meaning of unsuccessful Handovers without loss of MSconnection because of reversion to old cell.

The indicators on the HO failure rate are provided as an aggregation over all HO

causes and are additionally provided per HO cause value

Formula:

(a) ∑=

+=11

1C

c]11*[nUNINHOIEOFail[n]InterCellH

(b)OAtt[n]InterCellH

OFail[n]InterCellH n]OFailRate[InterCellH =

(c)

∑

=

++

+=3

0

c]11*44*AOUINIRH[n

c]11*[nUNINHOIE c][n,OFailRateCInterCellH

i

i



with i for the type of cell area:i = 0 complete-complete areai = 1 complete-inner areai = 2 inner-complete areai = 3 inner-inner area

Used param.: UNINHOIE[all], AOUINIRH[all], InterCellHOAtt[all] (11.2.1(a))


Unit: NoneRemarks: SDCCH handovers are also incremented in this formulas.

8/13/2019 KPIs_SBS_BR_7



System

74 A30808-X3247-B912-1-7618


Long name: (a) Number of Inter Cell Intra BSC Handover Drops

(b) Inter Cell Intra BSC Handover Drop Rate(c) Inter Cell Intra BSC Handover Drop Rate per cause

Short name: (a) InterCellHODrop

(b) InterCellHODropRate

(c) InterCellHODropRateC

Description: These indicators will give you the number and rate of Inter Cell Handover Drops perneighbour cell by meaning of unsuccessful Handovers with loss of MS connection.


Formula: (a) OFail[n]InterCellH-OSucc[n]InterCellH-OAtt[n]InterCellHODrop[n]InterCellH =


ODrop[n]InterCellHn]ODropRate[InterCellH =

(c)

∑∑

=

=

++

++ +

=

3

0

3

0

c]11*44*AOUINIRH[n

-c]11*44*[n-(AOUINIRH c]11*[nUNINHOIESOUINIRH)

c][n,ODropRateCInterCellH

i

i

i

i



with i for the type of cell area:i = 0 complete-complete areai = 1 complete-inner area

i = 2 inner-complete areai = 3 inner-inner area

8/13/2019 KPIs_SBS_BR_7



System

75 A30808-X3247-B912-1-7618

Used param.: AOUINIRH[all], SOUINIRH[all], UNINHOIE[all], InterCellHOAtt[all] (11.2.1(a)),InterCellHOSucc[all] (11.2.1(b)), InterCellHOFail[all] (11.2.2(a))


Unit: None

Remarks: SDCCH handovers are also incremented in this formulas. User release duringHandover will lead to systematic errors.

8/13/2019 KPIs_SBS_BR_7



System

76 A30808-X3247-B912-1-7618


Long name: (a) Inter Cell Intra BSC Handover Distribution

(b) Imperative Inter Cell Handover RateShort name: (a) InterCellHODist

(b) ImpInterCellHORate

Description: These indicators will give you the Inter Cell Intra BSC Handover Distribution foranalyzing the reason (cause) for started Inter Cell Intra BSC Handovers.

Imperative handovers are not whished but rather reflect possible problems in thenetwork topology

Formula:

(a) OAtt[n]InterCellH

c]11*44*AOUINIRH[n

c]ODist[n,InterCellH

3

0

∑=

++

= i

i


c]11*44*AOUINIRH[n

]llHORate[nImpInterCe

5

1C

3

0

∑ ∑= =

++= i

i



with i for the type of cell area:i = 0 complete-complete area

i = 1 complete-inner areai = 2 inner-complete areai = 3 inner-inner area

Used param.: AOUINIRH[all], InterCellHOAtt (11.2.1a)


Unit: None


8/13/2019 KPIs_SBS_BR_7



System

77 A30808-X3247-B912-1-7618

11.2.5 Incoming Handover Success Rate

Long name: Inter Cell Intra BSC Incoming Handover Success Rate

Short name: InterCellIncHOSuccRate

Description: This indicator will give you the rate of successful Inter Cell Intra BSC IncomingHandovers per neighbour cell relation.

Formula:

]AININIRH[n

]SININIRH[n te[n]ncHOSuccRaInterCellI =

with n for the nth number of neighbourcell relation (n=0..31)

Used param.: SININIRH[1..32], AININIRH[1..32]


Unit: None

Remarks: SDCCH handovers are also increment in the counters used for this formula andthat fact can lead to systematic errors.


Long name: Inter Cell Intra BSC SDCCH Handover Success Rate

Short name: InterCellSDHOSuccRate

Description: This indicator will give you the rate of successful Inter Cell Intra BSC SDCCHHandovers.

Formula:

]AISHINTE[1

]SISHINTE[1 eDHOSuccRatInterCellS =

Used param.: SISHINTE[1], AISHINTE[1]

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

78 A30808-X3247-B912-1-7618

11.3 Inter Cell Inter BSC Handovers


Long name: (a) Number of Inter Cell Inter BSC Handover Attempts

(b) Number of Inter Cell Inter BSC Handover Successes

(c) Inter Cell Inter BSC Handover Success Rate

(d) Inter Cell Inter BSC Handover Success Rate per cause

Short name: (a) InterBSCHOAtt

(b) InterBSCHOSucc

(c) InterBSCHOSuccRate

(d) InterBSCHOSuccRateC

Description: These indicators will give you the rate and number of successful Inter Cell Inter

BSC Handovers.


Formula:

(a) ∑=

+=10

1C

c]10*[nATINBHDOAtt[n]InterBSCHO

(b) ∑=

+=10

1C

c]10*[nSUINBHDO Succ[n]InterBSCHO

(c)Att[n]InterBSCHO

Succ[n]InterBSCHO ]SuccRate[nInterBSCHO =

(d)c]10*ATINBHDO[n

c]10*SUINBHDO[n c]n,SuccRateC[InterBSCHO

++=


with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strength

c=4 downlink strengthc=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to O&Mc=9 fast uplinkc=10 forced handover due to preemption

Used param.: ATINBHDO [all], SUINBHDO[all]


Unit: None


8/13/2019 KPIs_SBS_BR_7



System

79 A30808-X3247-B912-1-7618


Long name: (a) Number of Inter Cell Inter BSC Handover Failures

(b) Inter Cell Inter BSC Handover Failure Rate(c) Inter Cell Inter BSC Handover Failure Rate per cause

Short name: (a) InterBSCHOFail

(b) InterBSCHOFailRate

(c) InterBSCHOFailRateC

Description: These indicators will give you the rate and number of Inter Cell Inter BSCHandover. Failures by meaning of unsuccessful Handovers without loss of MSconnection because of reversion to old cell.


causes and are provided in addition separated per HO cause value

Formula:

(a) ∑=

+=10

1C

c]10*[n NRUNINHDFail[n]InterBSCHO

(b)Att[n]InterBSCHO

Fail[n]InterBSCHO ]FailRate[nInterBSCHO =

(c)c]10*ATINBHDO[n

]10* NRUNINHD[n c]n,FailRateC[InterBSCHO

++

= c


with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to O&Mc=9 fast uplink

c=10 forced handover due to preemption

Used param.: NRUNINHD[all], ATINBHDO[all], InterBSCHOAtt[all] (11.3.1(a))


Unit: None


8/13/2019 KPIs_SBS_BR_7



System

80 A30808-X3247-B912-1-7618


Long name: (a) Number of Inter Cell Inter BSC Handover Drops

(b) Inter Cell Inter BSC Handover Drop Rate

(c) Inter Cell Inter BSC Handover Drop Rate per cause

Short name: (a) InterBSCHODrop

(b) InterBSCHODropRate

(c) InterBSCHODropRateC

Description: These indicators will give you the rate and number of Inter Cell Inter BSCHandover Drops per neighbour cell by meaning of unsuccessful Handovers withloss of MS connection.


Formula: (a) Fail[n]InterBSCHO-Succ[n]InterBSCHO-Att[n]InterBSCHODrop[n]InterBSCHO =

(b)[n]

[n][n]

AttInterBSCHO

DropInterBSCHODropRateInterBSCHO =

(c)c]10*ATINBHDO[n

c]10*n NRUNINHD)[-SUINBHDO-(ATINBHDOc]n,DropRateC[InterBSCHO

+

+=


with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to O&Mc=9 fast uplinkc=10 forced handover due to preemption

Used param.: ATINBHDO[all], SUINBHDO[all], NRUNINHD[all], InterBSCHOAtt[all] (11.3.1(a)),InterBSCHOSucc[all] (11.3.1(b)), InterBSCHOFail[all] (11.3.2(a))


Unit: None

Remarks: SDCCH handovers are also incremented in this formulas. User release duringHandover will lead to very small systematic errors.

8/13/2019 KPIs_SBS_BR_7



System

81 A30808-X3247-B912-1-7618


Long name: (a) Inter Cell Inter BSC Handover Distribution

(b) Imperative Inter Cell Inter BSC Handover Rate

Short name: (a) InterBSCHODist(b) ImpInterBSCHORate

Description: These indicators will give you the Inter Cell Inter BSC Handover Distribution foranalysing the reason for started Inter Cell Inter BSC Handovers.

Imperative handovers are not whished but reflect possible problems in the networktopology

Formula:

(a)Att[n]InterBSCHO

c]10*ATINBHDO[n c]Dist[n,InterBSCHO

+=

(b)Att[n]InterBSCHO

c]10*ATINBHDO[n

CHORate[n]ImpInterBS

5

1

∑=

+= c


with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strength

c=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to O&Mc=9 fast uplinkc=10 forced handover due to preemption

Used param.: ATINBHDO[all], InterBSCHOAtt[all] (11.3.1(a)),


Unit: None


8/13/2019 KPIs_SBS_BR_7



System

82 A30808-X3247-B912-1-7618


Long name: (a) Inter Cell Inter BSC SDCCH Handover Success Rate

Short name: (a) InterBSCSDHOSuccRate

Description: This indicator will give you the rate of successful Inter Cell Inter BSC SDCCHHandovers.

Formula:

(a)]AOINTESH[1

]SOINTESH[1 HOSuccRateInterBSCSD =

Used param.: SOINTESH[1], AOINTESH[1]

Elem. Object: Cell

Unit: None

Remarks: None

11.4 Inter System Handover between GSM and UMTS

BR7: new chapter according FRS 1973 (HO to UMTS) and FRS 1981 (HO from

UMTS)

11.4.1 Outgoing Inter System Handover Success Rate

Long name: (a) Outgoing Inter System Handover Attempts

(b) Outgoing Inter System Handover Successes

(c) Outgoing Inter System Handover Success Rate

(d) Outgoing Inter System Handover Success Rate per cause

Short name: (a) InterSysOtgHOAtt

(b) InterSysOtgHOSucc

(c) InterSysOtgHOSuccRate

(d) InterSysOtgHOSuccRateC

Description: These indicators will give you the rate and number of successful outgoing Inter

System Handovers.


Formula:

(a) ∑=

+=10

1cc]10*[nATOISHDOgHOAtt[n]InterSysOt

(b) ∑

=

+=10

1c

c]10*[nSUOISHDOgHOSucc[n]InterSysOt

8/13/2019 KPIs_SBS_BR_7



System

83 A30808-X3247-B912-1-7618

(c)gHOAtt[n]InterSysOt

gHOSucc[n]InterSysOt e[n]gHOSuccRatInterSysOt =

(d)

c]10*ATOISHDO[n

c]10*SUOISHDO[n c]eC[n,gHOSuccRatInterSysOt

+

+=


with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distancec=6 better cellc=7 directed retry

c=8 forced handover due to pre-emptionc=9 forced handover due to O&M interventionc=10 sufficient UMTS coverage

Used param.: ATOISHDO [all], SUOISHDO[all]


Unit: None

Remarks:

8/13/2019 KPIs_SBS_BR_7



System

84 A30808-X3247-B912-1-7618

11.4.2 Outgoing Inter System Handover Failure Rate

Long name: (a) Outgoing Inter System Handover Failure

(b) Outgoing Inter System Handover Failure Rate(c) Outgoing Inter System Handover Failure Rate per cause

Short name: (a) InterSysOtgHOFail

(b) InterSysOtgFailRate

(c) InterSysOtgFailRateC

Description: These indicators will give you the rate and number of Outgoing Inter SystemHandover Failures by meaning of unsuccessful Handovers without loss of MSconnection because of reversion to old cell.


causes and are provided in addition separated per HO cause value

Formula:

(a) ∑=

+=10

1c

c]10*[nUNOISHDOgHOFail[n]InterSysOt

(b)gHOAtt[n]InterSysOt

gHOFail[n]InterSysOt e[n]gHOFailRatInterSysOt =

(c)c]10*ATOISHDO[n

]10*UNOISHDO[n c]eC[n,gHOFailRatInterSysOt

++

= c

with n for the number of the neighbourcell relation (n=0..63)with c for the cause number:

c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to pre-emptionc=9 forced handover due to O&M interventionc=10 sufficient UMTS coverage

Used param.: UNOISHDO[all], ATOISHDO[all], InterSysOtgHOAtt[all] (11.4.1(a))


Unit: None

Remarks:

8/13/2019 KPIs_SBS_BR_7



System

85 A30808-X3247-B912-1-7618

11.4.3 Outgoing Inter System Handover Drop Rate

Long name: (a) Outgoing Inter System Handover Drops

(b) Outgoing Inter System Handover Drop Rate

(c) Outgoing Inter System Handover Drop Rate per cause

Short name: (a) InterSysOtgHODrop

(b) InterSysOtgHODropRate

(c) InterSysOtgHODropRateC

Description: These indicators will give you the rate and number of Outgoing Inter SystemHandover Drops per neighbour cell by meaning of unsuccessful Handovers withloss of MS connection.

The indicators on the HO drop rate are provided as an aggregation over all HOcauses and are provided in addition separated per HO cause value.

Formula: (a) HOFailInter -HOSuccInter -HOAttInter HODropInter SysOtgSysOtgSysOtgSysOtg =

(b)gHOAttInterSysOt

gHODropInterSysOtegHODropRatInterSysOt =

(c)c]10*ATOISHDO[n

c]10*nUNOISHDO)[-SUOISHDO-(ATOISHDOc]C[n,HODropRateInter SysOtg

+

+=


with c for the cause number:

c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distancec=6 better cellc=7 directed retryc=8 forced handover due to pre-emptionc=9 forced handover due to O&M interventionc=10 sufficient UMTS coverage

Used param.: ATOISHDO[all], SUOISHDO[all], UNOISHDO[all], InterSysOtgHOAtt[all]

(11.4.1(a)), InterSYSHOSucc[all] (11.4.1(b)), InterSYSHOFail[all] (11.4.2(a))


Unit: None

Remarks: Systematic error: call release during HO is included in the formula

8/13/2019 KPIs_SBS_BR_7



System

86 A30808-X3247-B912-1-7618

11.4.4 Outgoing Inter System Handover Distribution

Long name: (a) Outgoing Inter Cell Inter System Handover Distribution

(b) Outgoing Imperative Inter Cell Inter System Handover Rate

Short name: (a) InterSysOtgHODist(b) ImpInterSysOtgHORate

Description: These indicators will give you the Inter Cell Inter System Handover Distribution foranalyzing the reason for started Inter Cell Inter System Handovers.

Imperative handovers are not whished but reflect possible problems in the networktopology

Formula:

(a)gHOAtt[n]InterSysOt

c]10*ATOISHDO[n c]gHODist[n,InterSysOt

+=

(b)gHOAtt[n]InterSysOt

c]10*ATOISHDO[n

[n]sOtgHORateImpInterSy

5

1∑=+

= c


with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strengthc=5 distance

c=6 better cellc=7 directed retryc=8 forced handover due to pre-emptionc=9 forced handover due to O&M interventionc=10 sufficient UMTS coverage

Used param.: ATOISHDO[all], InterSysOtgHOAtt[all] (11.4.1(a))


Unit: None

Remarks:

11.4.5 Incoming Inter System Handover Success Rate

Long name: (a) Successful Incoming Inter System HO from UMTS

(b) Attempted Incoming Inter System HO from UMTS

(c) Success Rate for Incoming Inter System HO from UMTS

Short name: (a) InterSysIncHOSucc(b) InterSysIncHOAtt

8/13/2019 KPIs_SBS_BR_7



System

87 A30808-X3247-B912-1-7618

(c) InterSysIncHOSuccRate

Description: These indicators will give you the rate and number of successful Incoming InterSystem HO from UMTS.

Formula:(a) [1]SUIISHDOcHOSuccInterSysIn =

(b) [1]RQIISHDOcHOAttInterSysIn =

(c)cHOAttInterSysIn

cHOSuccInterSysIn ecHOSuccRatInterSysIn =

Used param.: RQIISHDO[1]: Number of requested incoming intersystem handovers

SUIISHDO[1]: Number of successful incoming intersystem handovers

Elem. Object: BSC

Unit: None

Remarks:

8/13/2019 KPIs_SBS_BR_7



System

88 A30808-X3247-B912-1-7618

11.5 Other Handover Performance Indicators

11.5.1 Handovers per Erlanghour

Long name: (a) Handover per ErlanghourShort name: (a) HOperErlh

Description: This indicator will give you the ratio between successful Handovers and the trafficin Erlanghour per cell.

Aggregation over all neighbors of the observed cell and all HO causes isperformed

Formula: (a) HOperErlh =

[ ] yGranularit

60*

allMEBUSTCH

ll]SUOISHDO[all]SUINBHDO[all]SINTHINT[all]SINTHITA[a

+++

Used param.: SINTHITA[all], SINTHINT [all], SUINBHDO[all], SUOISHDO[all], MEBUSTCH[all],Granularity in minutes

Elem. Object: Cell

Unit: None

Remarks: SDCCH handovers are also incremented in these counters used for this formulaand that fact can lead to systematic errors.

BR7:

• Intersystem HO to UMTS considered (FRS 1973)

• Correction: Usage of the measurements SINTHITA and SINTHINT insteadof SINHOBSC

11.5.2 Handovers per Call Rate

Long name: (a) Handovers per Call Rate

Short name: (a) HOperCallRatio

Description: This indicator will give you the ratio between Handovers and successful CallSetups per cell.

Aggregation over all neighbors of the observed cell and all HO causes isperformed

Formula: (a) HoperCallRatio =

..5]TASSSUCC[2

ll]SUOISHDO[all]SUINBHDO[all]SINTHINT[all]SINTHITA[a

+++

Used param.: SINTHITA[all], SINTHINT [all], SUINBHDO[all], SUOISHDO[all], TASSSUCC[2..5],

8/13/2019 KPIs_SBS_BR_7



System

89 A30808-X3247-B912-1-7618

Elem. Object: Cell

Unit: None

Remarks: The Handovers per Call Rate is related to the Assignment Procedure. SDCCHhandovers are also incremented in these counters used for this formula and thatfact can lead to systematic errors.

BR7: Intersystem HO to UMTS considered (FRS 1973)

8/13/2019 KPIs_SBS_BR_7



System

90 A30808-X3247-B912-1-7618

11.5.3 Successful Directed Retries

Long name: (a) Number of Successful Directed Retries to GSM target cell

(b) Number of Successful Directed Retries to UMTStarget cellShort name: (a) NoSuccDirectedRetryGSM

(b) NoSuccDirectedRetryUMTS

Description: This indicator will give you the number of successful outgoing Handovers due todirected retry (Inter and Intra BSC and Inters System) per GSM and per UMTSneighbour cell.

Formula: (a) NoSuccDirectedRetryGSM[m]

= [ ] [ ]∑=

++++3

0i

711*i44*mSOUINIRH710*mSUINBHDO

(b) NoSuccDirectedRetryUMTS[n] = 7]10*SUOISHDO[n +

with m for the mth number of GSM neighbourcell relation (m=0..31)

with n for the nth number of UMTS neighbourcell relation (n=0..63)

with i for the type of cell area:i = 0 complete-complete areai = 1 complete-inner areai = 2 inner-complete areai = 3 inner-inner area

Used param.: SUINBHDO[m*10+7], SOUINIRH[m*44+i*11+7], SUOISHDO[n*10+7],Elem. Object: Neighbourcell

Unit: None

Remarks: BR7: Intersystem HO to UMTS considered (FRS 1973)

11.5.4 Imperative Outgoing Handover Rate

Long name: (a) Imperative Outgoing Handover Rate for GSM target cell

(b) Imperative Outgoing Handover Rate for UMTS target cell

Short name: (a) ImpOutgHORateGSM

(b) ImpOutgHORateUMTS

Description: This indicator will give you the rate of handovers due to Imperative reasons(namely UpLink/DownLink Strength and UpLink/DownLink Quality and Distance)from the total number of outgoing Handovers (Inter and Intra BSC and intersystem HO to UMTS).

The indicator is per GSM resp. per UMTS neighbour cell

Formula: (a) ImpOutgHORateGSM[m]=

8/13/2019 KPIs_SBS_BR_7



System

91 A30808-X3247-B912-1-7618

OAtt[m]InterCellHAtt[m]InterBSCHO

c]11*i44*AOUINIRH[mc]10*ATINBHDO[m

5

1c

3

0

+

++++∑ ∑

= =i

(b) ImpOutgHORateUMTS[n]= gHOAtt[n]InterSysOt

c]10*ATOISHDO[n

5

1c∑= +



with c for the cause number:c=1 uplink qualityc=2 downlink qualityc=3 uplink strengthc=4 downlink strength

c=5 distancewith i for the type of cell area:

i = 0 complete-complete areai = 1 complete-inner areai = 2 inner-complete areai = 3 inner-inner area

Used param.: AOUINIRH[m*44+i*11+c] , ATINBHDO[m*10+c], ATOISHDO[n*10+c],InterCellHOAtt[m] (11.2.1(a)), InterBSCHOAtt[m] (11.3.1(a)),InterSysOtgHOAtt[n] (11.4.1(a))

Elem. Object: NeighbourcellUnit: None


BR7:

• Intersystem HO to UMTS considered (FRS 1973)

• Correction: cause 5 (distance) now considered in the formula

11.5.5 Incoming Handover Success Rate

Long name: (a) Number of Successful Inter BSC Incoming HO

(b) Number of Attempted Inter BSC Incoming HO

(c) Inter Cell Inter BSC Incoming Handover Success Rate

Short name: (a) InterBSCIncHOSucc

(b) InterBSCIncHOAtt

(c) InterBSCIncHOSuccRate

Description: These indicators will give you the rate and number of successful Inter Cell InterBSC Incoming Handovers including incoming HO from UMTS.

8/13/2019 KPIs_SBS_BR_7



System

92 A30808-X3247-B912-1-7618

Formula: (a)

..44SININIRH[1-22]..1714,.. NSUCCHPC[9-OSuccIntraCellH

-,3]TASSSUCC[2-,2]SUCTCHSE[1cHOSuccInterBSCIn =

(b)

..44]AININIRH[1-..14]ATIMASCA[7-OAttIntraCellH

-3]TASSATT[2,-,2]ATTCHSEI[1cHOAttInterBSCIn =

(c)cHOAttInterBSCIn

cHOSuccInterBSCIn ecHOSuccRatInterBSCIn =

Used param.: SUCTCHSE[1,2], TASSSUCC[2,3], NSUCCHPC[9...14,17...22],

SININIRH[1..44], ATTCHSEI[1,2], TASSATT[2,3], ATIMASCA[7..14], AININIRH[1..44], IntraCellHOSucc(11.1.1(b)), IntraCellHOAtt(11.1.1(a))

Elem. Object: Cell

Unit: None


BR7: KPIs includes also incoming HO from UMTS

8/13/2019 KPIs_SBS_BR_7



System

93 A30808-X3247-B912-1-7618

11.5.6 Handover Indication Rejection Rate

Long name: (a) Handover Indication Rejection Rate

Short name: (a) HOIndRejRate

Description: This indicator will give you the Handover Indication Rejection Rate by meaning thenumber of Handover indications not resulting in a Handover Attempt divided by thenumber of all Handover indications. Reasons for this can be congestions orcoverage problems.

The KPI considers all types of outgoing HO: Inter and Intra BSC and inter systemHO to UMTS.

Formula: (a) HOIndRejRate =

∑∑∑===

++++63

0

31

0

31

0

gHOAttInterSysOt]4..1[

]4..1[

nmm

Att InterBSCHOOAtt InterCellH OAtt IntraCellH NHOINRHA

NHOINRHA



Used param.: NHOINRHA [1..4], IntraCellHOAtt(11.1.1(a)), InterCellHOAtt[m] (11.2.1(a)),InterBSCHOAtt[m] (11.3.1(a)), InterSysOtgHOAtt[n] (11.4.1(a))

Elem. Object: Cell

Unit: None

Remarks: Please note: With counter NHOINRHA[1] it is also possible to measure the number

of Handover indications not resulting in an Handover Attempt due to emptyneighbour cell list. The reason for this is mainly related to coverage problems.

BR7: Intersystem HO to UMTS considered (FRS 1973)

8/13/2019 KPIs_SBS_BR_7



System

94 A30808-X3247-B912-1-7618

12 Power and Quality Measurements

12.1 Interference Band Rate on idle TCH

Long name: (a) Interference Band Rate on idle TCH

Short name: (a) IfBandRate[n]

Description: This indicator will give you Interference Band Rate on idle TCH. Severalindicators distinguish between different interference bands.

Formula:(a)

[1..5]MEITCHIB

[n]MEITCHIB [n]IfBandRate =

with n=1 for Interference band 1with n=2 for Interference band 2

with n=3 for Interference band 3with n=4 for Interference band 4with n=5 for Interference band 5

Used param.: MEITCHIB[1..5]

Elem. Object: Cell

Unit: None

Remarks: None

12.2 Quality Link for N% FER

Long name: (a) Quality Link for N% FER

Short name: (a) QualityLinkNFER

Description: This indicator will give you the total reported FER uplink values that were underthe threshold FER=N%. It is an indicator of the speech quality provided to theTRX users.

Formula:

(a)

[1..64]CFERRXQU

8]8*1..i8*[iCFERRXQU

kNFER QualityLin

n

0i

∑=

++

=

Where n is the FER band that has it’s upper limit equal or lower to N%

Used param,: CFERRXQU[1..64]

Elem. Object: TRX

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

95 A30808-X3247-B912-1-7618

12.3 Mean FER UpLink

Long name: (a) Mean FER UpLink

Short name: (a) MeanFERUL

Description: This indicator provides the average FER Band on the Uplink.

Formula:

(a)

( )( )

[1..64]CFERRXQU

8]8*1..i8*[iCFERRXQU*1i

MeanFERUL

7

0i

∑=

+++

=


Elem. Object: TRX

Unit: FER Band

Remarks: None.

8/13/2019 KPIs_SBS_BR_7



System

96 A30808-X3247-B912-1-7618

12.4 Power and Quality limits for N% Percentile on busyTCH

Long name: (a) RXLEV for N% Percentile Uplink on busy TCH(b) RXLEV for N% Percentile Downlink on busy TCH

(c) RXQUAL for N% Percentile Uplink on busy TCH

(d) RXQUAL for N% Percentile Downlink on busy TCH

Short name: (a) RxLvNPercentileUL

(b) RxLvNPercentileDL

(c) RxQuNPercentileUL

(d) RxQuNPercentileDL

Description: These indicators will give you the information that N% of the measurements onbusy channels registered a received Power Level below a certain Level Band and

that N% of the measurements on busy channels registered a received Qualitybelow a certain Quality Band. Two indicators distinguish between uplink anddownlink.

Formula:

(a)100

N

[1..64]PWRUPDW

n

1i[i])(PWRUPDW

such thatnn withntileULRxLvNPerce =∑==

(b)100

N

[73..136]PWRUPDW

n

1ii])[72(PWRUPDW

such thatnn withntileDLRxLvNPerce =∑=

+=

(c)100

N

[65..72]PWRUPDW

n

1i i])[64(PWRUPDWsuch thatnn withntileULRxQuNPerce =∑= +=

(d)100

N

[137..144]PWRUPDW

n

1ii])[136(PWRUPDW

such thatnn withntileDLRxQuNPerce =∑=

+=

Used param.: PWRUPWD[all]

Elem. Object: Channel

Unit: None

Remarks: BR7 correction: PWRUPDW measurement has no longer 288 counters becauseof the removal of sub-timeslot related ones

12.5 Distribution of power control levels on busy TCH

Long name: (a) Power Control level distribution on busy TCH in UL direction

(b) Power Control level distribution on busy TCH in DL direction

Short name: (a) PWContrDistrUL

(b) PWContrDistrDL

Description: This indicator provides the distribution of the registered power control levels per

TCH for UL and DL direction.Use case: Network optimization:

8/13/2019 KPIs_SBS_BR_7



System

97 A30808-X3247-B912-1-7618

Evaluation of the Power Control efficiency and detection of planning problems(e.g. unintended intensive usage of the highest power control values for a TCH)

Formula:

(a)[1..64]PWRUPDW

1][nPWRUPDWtrUL[n]PWContrDis

+=

(b)136]..[73PWRUPDW

73][nPWRUPDWtrDL[n]PWContrDis

+=

with n = 0 , .. 63 for the power control level

Used param.: PWRUPWD[all]


Unit: None

Remarks: BR7: new indicators

12.6 Mean Level and Quality on busy TCH

Long name: (a) Mean RXLEV Uplink on busy TCH

(b) Mean RXLEV Downlink on busy TCH

(c) Mean RXQUAL Uplink on busy TCH

(d) Mean RXQUAL Downlink on busy TCH

Short name: (a) MeanRxLvUL

(b) MeanRxLvDL(c) MeanRxQuUL

(d) MeanRxQuDL

Description: These indicators will give you the mean RXLEV and RXQUAL on busy TCH. Twoindicators distinguish between uplink and downlink.

Formula:

(a)[1..64]PWRUPDW

[i])PWRUPDW*(i

MeanRxLvUL

64

1i

∑==

(b)[73..136]PWRUPDW

i])[72PWRUPDW*(i MeanRxLvDL

64

1i∑= +=

(c)[65..72]PWRUPDW

i])[64PWRUPDW*(i

MeanRxQuUL

8

1i

∑=

+=

(d)[137..144]PWRUPDW

i])[136PWRUPDW*(i

MeanRxQuDL

8

1i

∑=

+=

Used param: PWRUPWD[all]


8/13/2019 KPIs_SBS_BR_7



System

98 A30808-X3247-B912-1-7618

Unit: None

Remarks: BR7 correction: PWRUPDW measurement has no longer 288 counters becauseof the removal of sub-timeslot related ones

8/13/2019 KPIs_SBS_BR_7



System

99 A30808-X3247-B912-1-7618

12.7 TA Distribution

Long name: (a) TA Distribution

Short name: (a) TADist[n]

Description: These indicators provide the rate of received samples having timing advance inTA Band equal to ‘n’ .

Formula:

(a)[1..64]CRXLVTAU)(CRXLVTAD

1]n8[iCRXLVTAU)(CRXLVTAD

TADist[n]

7

0i

+

++×+

=∑

=

Where n=0..7

Used param.: CRXLVTAD[1..64], CRXLVTAU[1..64]

Elem. Object: TRX

Unit: None

Remarks: The range of the used measurements (SCANCTRX measurements) can beconfigured and is therefore relevant for the analysis of the results.

12.8 RXQUAL Distribution

Long name: (a) RXQUAL Distribution DownLink

(b) RXQUAL Distribution UpLink

Short name: (a) RxQuDistDL[n]

(b) RxQuDistUL[n]

Description: These indicators provide the rate of received samples having the received BER inQuality Band equal to ‘n’. Two indicators distinguish between uplink anddownlink.

Formula:

(a)[1..64]CRXLVQUD

1]n8[iCRXLVQUD

[n]RxQuDistDL

7

0i

∑=

++×

=

(b) [1..64]CRXLVQUU

1]n8[iCRXLVQUU

[n]RxQuDistUL

7

0i

∑=

++×

=

Where n=0..7

Used param.: CRXLVQUD[1..64], CRXLVQUU[1..64]

Elem. Object: TRX

Unit: None


8/13/2019 KPIs_SBS_BR_7



System

100 A30808-X3247-B912-1-7618

12.9 RXLEV Distribution

Long name: (a) RXLEV Distribution DownLink

(b) RXLEV Distribution UpLink

Short name: (a) RxLvDistDL[n]

(b) RxLvDistUL[n]

Description: These indicators provide the rate of received samples having the received Levelin Level Band equal to ‘n’. Two indicators distinguish between uplink anddownlink.

Formula:(a)

[1..64]CRXLVQUD

8]81..n8[nCRXLVQUD[n]RxLvDistDL

+×+×=

(b)[1..64]CRXLVQUU

]88n..18[nCRXLVQUU[n]RxLvDistUL

+×+×=

Where n=0..7

Used param.: CRXLVQUD[1..64], CRXLVQUU[1..64]

Elem. Object: TRX

Unit: None


12.10 FER Distr ibut ion

Long name: (a) FER Distribution

Short name: (a) FERDist[n]

Description: These indicators provide the rate of received samples having the uplink FER inFER Band equal to ‘n’.

Formula:(a)

[1..64]CFERRXQU

8]8n..18[nCFERRXQUFERDist[n]

+×+×=

Where n=0..7

Used param.: CFERRXQU[1..64]

Elem. Object: TRX

Unit: None


8/13/2019 KPIs_SBS_BR_7



System

101 A30808-X3247-B912-1-7618

12.11 Mean FER UpLink per RXQUAL

Long name: (a) Mean FER UpLink per RXQUAL Band

Short name: (a) MeanFERULforRxQu[n]

Description: These indicators provide the average FER Band on the uplink for each QualityBand. The implementation of certain features like frequency hoping improves theFER for the same RXQUAL values and therefore, FER is more accurate indicatorfor analysing the quality of the connection or speech quality.

Formula:

(a)

( )( )

∑

∑

=

=

++×

++××+

=7

0i

7

0i

1]n8[iCFERRXQU

1]n8[iCFERRXQU1i

[n]orRxQuMeanFERULf

Where n =0..7


Elem. Object: TRX

Unit: FER Band


8/13/2019 KPIs_SBS_BR_7



System

102 A30808-X3247-B912-1-7618

12.12 Mean RXLEV per RXQUAL Band

Long name: (a) Mean RXLEV per RXQUAL Band DownLink

(b) Mean RXLEV per RXQUAL Band UpLink

Short name: (a) MeanRxLvforRxQuDL[n]

(b) MeanRxLvforRxQuUL[n]

Description: These indicators provide the average RXLEV Band for each Quality Band eitherUplink or Downlink. High interference levels can be associated to high RXLEVaverages in the higher Quality Bands.

Formula:

(a)

( )( )

∑

∑

=

=

++×

++××+

=7

0i

7

0i

1]n8[iCRXLVQUD

1]n8[iCRXLVQUD1i

[n]rRxQuDLMeanRxLvfo

(b)

( )( )

∑

∑

=

=

++×

++××+

=7

0i

7

0i

1]n8[iCRXLVQUU

1]n8[iCRXLVQUU1i

[n]rRxQuULMeanRxLvfo

Where n =0..7

Used param,: CRXLVQUU[1..64], CRXLVQUD[1..64]

Elem. Object: TRX

Unit: Level Band


8/13/2019 KPIs_SBS_BR_7



System

103 A30808-X3247-B912-1-7618

12.13 Mean RXLEV per TA Band

Long name: (a) Mean RXLEV per TA Band DownLink

(b) Mean RXLEV per TA Band UpLink

Short name: (a) MeanRxLvforTADL

(b) MeanRxLvforTAUL

Description: These indicators provide the average RXLEV Band for each Timing AdvanceBand either Uplink or Downlink.

Formula:

(a)

( )( )

∑

∑

=

=

++

+++

=7

0i

7

0i

1]n8*[iCRXLVTAD

1]n8*[iCRXLVTAD*1i

[n]rTADLMeanRxLvfo

(b)

( )( )

∑∑

=

=

++

+++=

7

0i

7

0i

1]n8*[iCRXLVTAU

1]n8*[iCRXLVTAU*1i

[n]rTAULMeanRxLvfo

Where n =0..7

Used param.: CRXLVTAD[1..64], CRXLVTAU[1..64]

Elem. Object: TRX

Unit: Level Band

Remarks: The range of the used measurements (SCANCTRX measurements) can be

configured and is therefore relevant for the analysis of the results.

8/13/2019 KPIs_SBS_BR_7



System

104 A30808-X3247-B912-1-7618

12.14 High RXLEV with Low RXQUAL Rate

Long name: (a) High RXLEV With Low RXQUAL Rate DownLink

(b) High RXLEV With Low RXQUAL Rate UpLink

Short name: (a) HighLvLowQuRateDL

(b) HighLvLowQuRateUL

Description: These indicators will give the rate of RXLEVs that were reported for the twohighest Level Bands (i.e. Level Bands: RXLEV_6 and RXLEV_7) and for the fourhighest Quality Bands (i.e. Quality Bands: RXQUAL_4, RXQUAL_5, RXQUAL_6and RXQUAL_7) from the total samples for the four highest Quality Bands. Highvalues for this indicator are usually related to interference problems.

Formula: (a)..64],53..56,61.40,45..4829..32,37.16,21..24,[5..8,13..CRXLVQUD

..64][53..56,61CRXLVQUDuRateDLHighLvLowQ =

(b)..64],53..56,61.40,45..4829..32,37.16,21..24,[5..8,13..CRXLVQUU

..64][53..56,61CRXLVQUUuRateULHighLvLowQ =

Used param.: CRXLVQUD [5..8,13..16,21..24,29..32,37..40,45..48,53..56,61..64],CRXLVQUU [5..8,13..16,21..24,29..32,37..40,45..48,53..56,61..64]

Elem. Object: TRX

Unit: None

Remarks: - The range of the used measurements (SCANCTRX measurements) can beconfigured and is therefore relevant for the analysis of the results.

- BR7: Correction KPI HighLvLowQuRateUL: reference to UL correlatedmeasurement (CRXLVQUU ) but not downlink

8/13/2019 KPIs_SBS_BR_7



System

105 A30808-X3247-B912-1-7618

12.15 TCH Traffic Type Distribution

Long name: (a) TCH full rate speech traffic channel Rate

(b) TCH enhanced full rate speech traffic channel Rate

(c) TCH adaptive multirate full rate speech traffic channel Rate(d) TCH full rate data traffic channel Rate

(e) TCH half rate speech traffic channel Rate

(f) TCH adaptive multirate half rate speech traffic channel Rate

Short name: (a) TCHFSRate

(b) TCHEFSRate

(c) TCHAFSRate

(d) TCHFDRate

(e) TCHHSRate

(f) TCHAHSRateDescription: These indicators provide the TCH Traffic Type Distribution, by meaning the traffic

for a individual traffic type compared to the total traffic for all traffic channels.Different indicators distinguish between full rate speech, enhanced full ratespeech, adaptive multirate full rate speech, full rate data, half rate speech andadaptive multirate half rate speech TCHs.

Formula:(a)

..6]MBTCHCHT[1

[1]MBTCHCHT TCHFSRate =

(b)..6]MBTCHCHT[1

[2]MBTCHCHT TCHEFSRate =

(c)..6]MBTCHCHT[1

[3]MBTCHCHT TCHAFSRate =

(d)..6]MBTCHCHT[1

[4]MBTCHCHT TCHFDRate =

(e)..6]MBTCHCHT[1

[5]MBTCHCHT TCHHSRate =

(f)..6]MBTCHCHT[1

[6]MBTCHCHT TCHAHSRate =

Used param.: MBTCHCHT [1..6]

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

106 A30808-X3247-B912-1-7618

12.16 Adaptive Multirate Distribution

Long name: (a) Adaptive Multirate channel type usage

Short name: (a) AMRCHTUsage

Description: These indicators provide the Adaptive Multirate channel type usage and will giveyou an overview about the quality of the feature Adaptive multirate (AMR).Separate counters distinguish between the different adaptive multirate channeltypes (8 for adaptive multirate full rate speech, and 5 for adaptive multirate halfrate speech) and between uplink / downlink transmission. These indicatorsprovide how often a specific adaptive multirate channel type was used related toall adaptive multirate channel types for one direction (uplink / downlink).

Formula:(a)

100

]AMRCHDIS[n e[n]AMRCHTUsag =

with n =

1 for TCH/AFS 12.2 uplink (AMR full rate speech, 12.2 kbit/s, uplink)2 for TCH/AFS 10.2 uplink (AMR full rate speech, 10.2 kbit/s, uplink)

3 for TCH/AFS 7.95 uplink (AMR full rate speech, 7.95 kbit/s, uplink)






9 for TCH/AHS 7.4 uplink (AMR half rate speech, 7.4 kbit/s, uplink) (new BR7)

10for TCH/AHS 6.7 uplink (AMR half rate speech, 6.7 kbit/s, uplink)

11 for TCH/AHS 5.9 uplink (AMR half rate speech, 5.9 kbit/s, uplink)



14 for TCH/AFS 12.2 downlink (AMR full rate speech, 12.2 kbit/s, downlink)15 for TCH/AFS 10.2 downlink (AMR full rate speech, 10.2 kbit/s, downlink)

16 for TCH/AFS 7.95 downlink (AMR full rate speech, 7.95 kbit/s, downlink)






22 for TCH/AHS 7.4 downlink (AMR half rate speech, 7.4 kbit/s, downlink) (new BR7)

23 for TCH/AHS 6.7 downlink (AMR half rate speech, 6.7 kbit/s, downlink)




Used param.: AMRCHDIS[1..26]

Elem. Object: Cell

Unit: None

Remarks: - AMRCHDIS must be divided by 100 in this formula, because the measuredvalue is in percent and KPI`s shouldn`t be in percent.

- BR7: new counters for AMR rate speech, 7.4 kbit/s

8/13/2019 KPIs_SBS_BR_7



System

107 A30808-X3247-B912-1-7618

12.17 Adapt ive Multirate True Frame Erasure Rate

Long name: (a) Adaptive Multirate Average Frame Erasure Rate Uplink

(b) Adaptive Multirate Average Frame Erasure Rate Uplink per channel type

(c) Adaptive Multirate Average Frame Erasure Rate Downlink

Short name: (a) AMRTFERUL

(b) AMRTFERULCHT

(c) AMRTFERDL

Description: These indicators provide the Adaptive Multirate True Frame Erasure Rate FER:

• The True FER is provided as an average over all channel types (codedmodes) for the uplink and downlink directions

• In addition for the uplink direction the True FER is provided for each channeltype separately.

Formula: (a) ∑= ++=13

1 100]AMRCHDIS[n*

13]n[n,13][n AMRTFERUL

n AMRFRMUL AMRFRMUL

(b)13]n[n,

13][n HT[n]AMRTFERULC

++

= AMRFRMUL

AMRFRMUL

with n =

1 for TCH/AFS 12.2

2 for TCH/AFS 10.2

3 for TCH/AFS 7.95

4 for TCH/AFS 7.4

5 for TCH/AFS 6.7

6 for TCH/AFS 5.97 for TCH/AFS 5.15

8 for TCH/AFS 4.75

9 for TCH/AHS 7.4

10for TCH/AHS 6.7

11 for TCH/AHS 5.9

12 for TCH/AHS 5.15

13 for TCH/AHS 4.75

(c)[1,2]

[2] AMRTFERDL AMRFRMDL

AMRFRMDL=

Used param.: AMRFRMUL[1..26], AMRFRMDL[1..2], AMRCHDIS[1..13]

Elem. Object: Cell

Unit: None

Remarks: - BR7: new KPI

- AMRCHDIS is in units of percent and must therefore be divided by 100 to getthe weighting factor per channel mode

8/13/2019 KPIs_SBS_BR_7



System

108 A30808-X3247-B912-1-7618

13 Availability related Performance Indicators

13.1 Transceiver AvailabilityLong name: (a) Tranceiver Availability

Short name: (a) TRXAvail

Description: This indicator will give you the TRX Availability.

Formula:(a)

60s*yGranularit

[1]TRANAVTI TRXAvail =

Used param.: TRANAVTI[1], Granularity in minutes

Elem. Object: TRXUnit: None

Remarks: None

13.2 TCH Distribution Rate

Long name: (a) TCH Full Rate

(b) TCH Half Rate

Short name: (a) FR

(b) HR

Description: This indicator will give you the Rate of configured Full Rate and Half Rate trafficchannels compared to the total number of traffic channels.

Formula:(a)

,6,9,12] NRDEFTCH[3

,9] NRDEFTCH[3 FR =

(b),6,9,12] NRDEFTCH[3

,12] NRDEFTCH[6 HR =

Used param.: NRDEFTCH[1..12]

Elem. Object: Cell

Unit: None

Remarks: • Static GPRS channels (configured with GMAPERTCHRES) are not

considered into NRDEFTCH measurement

• Due to feature ‘Smooth Channel Modification’ now all timeslots configuredas TCH and or TCH/SD with pooltype 'TCH_Pool' or TCH/SD withpooltype 'TCH_SD_Pool' are considered for measurement NRDEFTCH.

8/13/2019 KPIs_SBS_BR_7



System

109 A30808-X3247-B912-1-7618

13.3 TCH Efficiency

Long name: (a) TCH Efficiency Full Rate

(b) TCH Efficiency Half Rate

(c) TCH Efficiency Dual Rate

Short name: (a) TCHEffFR

(b) TCHEfflHR

(c) TCHEffDR

Description: This indicator will give you the TCH Efficiency (Rate).

Formula:(a)

,9] NRDEFTCH[3

] NAVTCH[3,9 TCHEffFR =

(b)

,12] NRDEFTCH[6

2] NAVTCH[6,1 TCHEffHR =

(c),12] NRDEFTCH[6*5,0,9] NRDEFTCH[3

2] NAVTCH[6,1*5,0] NAVTCH[3,9 TCHEffDR

++

=

Used param.: NAVTCH[3,6,9,12], NRDEFTCH[3,6,9,12]

Elem. Object: Cell

Unit: None

Remarks: • Static GPRS channels (configured with GMAPERTCHRES) are notconsidered into NRDEFTCH and NAVTCH measurements

• Due to feature ‘Smooth Channel Modification’ now all timeslots configuredas TCH and or TCH/SD with pooltype 'TCH_Pool' or TCH/SD withpooltype 'TCH_SD_Pool' are considered for measurement NRDEFTCH.

• Due to feature ‘Smooth Channel Modification’ now all configuredtimeslots possible to use as TCH are considered for measurementNAVTCH (Timeslots configured as TCH or TCH/SD with pooltypeTCH_Pool' or TCH/SD with pooltype 'TCH_SD_Pool').

8/13/2019 KPIs_SBS_BR_7



System

110 A30808-X3247-B912-1-7618

13.4 SDCCH Efficency

Long name: (a) SDCCH Efficency

Short name: (a) SDCCHEff

Description: This indicator will give you the SDCCH Efficiency (Rate).

Formula:

(a)] NDESDCCH[3

[3] NAVSDCCH SDCCHEff =

Used param.: NAVSDCCH[3], NDESDCCH[3]

Elem. Object: Cell

Unit: None

Remarks: Due to feature ‘Smooth Channel Modification’ now all timeslots configured asSDCCH and TCH/SD with pooltype 'SDCCH_Pool' are considered formeasurement NRDESDCCH.

Due to feature ‘Smooth Channel Modification’ now all configured timeslotspossible to use as SDCCH, belonging to the SDCCH _Pool and theTCH/SD_Pool, are considered for measurement NAVSDCCH (Timeslotsconfigured as SDCCH or TCH/SD with pooltype ‘SDCCH_Pool’).

8/13/2019 KPIs_SBS_BR_7



System

111 A30808-X3247-B912-1-7618

14 GPRS Related Performance Indicators

14.1 User oriented KPIs

14.1.1 Number of TBF establishment attempts

Long Name: (a) TBF establishment attempts uplink

(b) TBF establishment attempts downlink

Short Name: (a) TBFEstAttUL

(b) TBFEstAttDL

Description : This indicator provides the number of TBF establishments for uplink anddownlink.

Formula: (a) TBFEstAttUL = NUACATCL[1]

(b) TBFEstAttDL = NUACATCL[2]

Used param.: NUACATCL[1,2]]

Elem. Object: Cell

Unit: None

Remark:

14.1.2 Number of TBF establishment failures

Long Name: (a) TBF establishment failed due to PDCH Congestion uplink

(b) TBF establishment failed due to PDCH Congestion downlink

(c) TBF establishment failed due to no reaction from mobile station uplink

(d) TBF establishment failed due to no reaction from mobile station downlink

Short Name: (a) TBFEstFailConUL

(b) TBFEstFailConDL

(c) TBFEstFailNoReacUL

(d) TBFEstFailNoReacDL

Description : This indicator provides the number of TBF establishment failures per cause.This indicator will measure in uplink and downlink direction.

Formula: (a) TBFEstFailConUL = REJPDASS [1],

(b) TBFEstFailConDL = REJPDASS [3],

(c) TBFEstFailNoReactUL = SUCPDASA [1] - SULACCEL[1]

(d) TBFEstFailNoReacDL = SUCPDASA [2] - SULACCEL[2]

8/13/2019 KPIs_SBS_BR_7



System

112 A30808-X3247-B912-1-7618

Used param.: REJPDASS [1,3], SUCPDASA [1,2], SULACCEL[1,2]

Elem. Object: Cell

Unit: None

Remark:

14.1.3 Number of successful TBF establishments

Long Name: (a) TBF establishment Success Uplink

(b) TBF establishment Success Downlink

Short Name: (a) TBFEstSuccUL

(b) TBFEstSuccDL

Description : This indicator calculates the total number of successfully established TBFs in acell for the uplink and downlink direction.

Formula: (a) TBFEstSuccUL = SULACCEL[1]

(b) TBFEstSuccDL = SULACCEL[2]

Used param.: SULACCEL[1,2];

Elem. Object: Cell

Unit: None

Remark:

14.1.4 TBF establishment success rate

Long Name: (a) TBF establishment Success Rate Uplink

(b) TBF establishment Success Rate Downlink

Short Name: (a) TBFEstSuccRateUL

(b) TBFEstSuccRateDL

Description : This indicator provides the TBF establishment success probabilityconsidering uplink and downlink directions.

Formula:(a)

] NUACATCL[1

]SULACCEL[1RateULTBFEstSucc =

(b)] NUACATCL[2

]SULACCEL[2RateDLTBFEstSucc =

Used param.: SULACCEL[1,2]; NUACATCL[1,2]

Elem. Object: Cell

Unit: NoneRemark:

8/13/2019 KPIs_SBS_BR_7



System

113 A30808-X3247-B912-1-7618

14.1.5 TBF establishment failure rate (TBF loss rate)

Long Name: (a) TBF establishment failure rate for PDCH congestion Uplink

(b) TBF establishment failure rate for PDCH congestion Downlink

(c) TBF establishment failure rate for no reaction from mobile Uplink

(d) TBF establishment failure rate for no reaction from mobile Downlink

Short Name: (a) TBFEstFailRateConUL

(b) TBFEstFailRateConDL

(c) TBFEstFailRateNoReacUL

(d) TBFEstFailRateNoReacDL

Description : This indicator provides the TBF establishment failure rate per cause

considering uplink and downlink directions.

Formula:(a)

] NUACATCL[1

]REJPDASS[1RateConULTBFEstFail =

(b)] NUACATCL[2

]REJPDASS[3RateConDLTBFEstFail =

(c)] NUACATCL[1

]SULACCEL[1-[1]SUCPDASAULRateNoReacTBFEstFail =

(d)

] NUACATCL[2

]SULACCEL[2-[2]SUCPDASADLRateNoReacTBFEstFail =

Used param.: REJPDASS [1,3], NUACATCL[1,2], SUCPDASA[1,2], SULACCEL[1,2]

Elem. Object: Cell

Unit: None

Remark:

14.1.6 Rate for successful TBF establishment with reduced PDCH

assignment

Long Name: (a) Rate of successful UL TBF establishment with reduced PDCH assignment

(b) Rate of successful DL TBF establishment with reduced PDCH assignment

Short Name: (a) TBFEstSuccRedRateUL

(b) TBFEstSuccRedRateDL

Description : This indicator provides the mean rate of successful TBF establishment whereonly a reduced number of PDCHs was assigned to the mobile due to lack ofPDCH resources. The indicator distinguishes uplink and downlink direction.

Formula: (a) TBFEstSuccRedRateUL = UNSPDCSE[1] / SULACCEL[1](b) TBFEstSuccRedRateDL = UNSPDCSE[2] / SULACCEL[2]

8/13/2019 KPIs_SBS_BR_7



System

114 A30808-X3247-B912-1-7618

Used param.: UNSPDCSE[1,2], SULACCEL[1,2],

Elem. Object: Cell

Unit:

Remark:

14.1.7 Total number of normally released TBFs

Long Name: a) Normal Uplink TBF release

b) Normal Downlink TBF release

Short Name: (a) TBFNormRelUl

(b) TBFNormRelDL

Description : This indicator provides the number of normally released TBFs consideringuplink and downlink directions.

Formula: (a) TBFNormRelUl = SUCTETBF[1,2]

(b) TBFNormRelDL = SUCTETBF[3,4]

Used param.: SUCTETBF[1…4]

Elem. Object: Cell

Unit: NoneRemark:

14.1.8 Total number of dropped TBFs

Long Name: a) Uplink TBF dropped due to any cause

b) Downlink TBF dropped due to any cause

Short Name: (a) TBFDrAllCauseUL

(b) TBFDrAllCauseDL

Description : This indicator provides the number of dropped TBFs for all causesconsidering uplink and downlink directions.

Formula: (a) TBFDrAllCauseUL = UNSTETBF[1] + ABRELTBF[3]

(b) TBFDrAllCauseDL = UNSTETBF[2] + ABRELTBF[6]

Used param.: UNSTETBF[1,2], ABRELTBF[3,6]

Elem. Object: Cell

Unit: None

Remark: • “Dropped” means that a TBF is terminated in an abnormal way. But aTBF drop does not necessarily indicate system misbehavior.

8/13/2019 KPIs_SBS_BR_7



System

115 A30808-X3247-B912-1-7618

E.g. UNSTETBF[1] (T3169 expiry) is not only counted when the MSis “lost” but is also counted in case of MS based cell reselectionduring uplink TBF and in case of circuit switched call setup duringuplink TBF (and additionally in some other cases).

• Remarks on the not used counters of ABRELTBF

o ABRELTBF[2,5]: (“Radio link quality insufficient …”):In BR7 that counter is never triggered due to the concept ofCS/MSC downgrading

o ABRELTBF[1]: (“Radio contact lost …”, UL)In BR7 that counter is never triggered

o ABRELTBF[4]: (“Radio contact lost …”, DL)Counter is triggered, but in that case also UNSTETBF[1] istriggered

• The formulas contain systematic errors, since not all causes for TBFdrop are considered in the BR7 (E)GPRS PM counters.Improvement from BR8: UNSTETBF will be enhanced at BR8 (FRS:

86898) in order to include all cases of non-standard TBF release.• Further systematic error since ABRELTBF[3] is not incremented in

case a concurrent DL TBF exists when Radio Status is sent. In thatcase only ABRELTBF[6] (UL counter) is incremented.

• Counters NRLTBFCR [1,2] Number of lost TBF due to cell reselection(uplink/downlink) has not been considered in the formulas:Reason: NRLTBFCR is related to FLUSH_LL but does not consider ifTBF(s) still exist(s) when FLUSH_LL arrives from the SGSN. Furtherthe counter in UL direction is always 0. In fact the measurementNRLTBFCR is not strictly related to TBFs

14.1.9 TBF drop distribution on causes

Long Name: (a) Share of UL TBF drop due to expiry of supervision timer (T3169)

(b) Share of DL TBF drop due to expiry of supervision timer (T3195)

(c) Share of UL TBF drop due to ordering of cell reselection (networkcontrolled cell reselection)

(d) Share of DL TBF drop due to ordering of cell reselection (network

controlled cell reselection)Short Name: (a) TBFDrShareTimerExpUL

(b) TBFDrShareTimerExpDL

(c) TBFDrShareCellResOrdUL

(d) TBFDrShareCellResOrdDL

Description : This indicator provides the distribution of TBF drops per cause consideringuplink and downlink directions.

Formula:(a)

useULTBFDrAllCa

]UNSTETBF[1 TimerExpULTBFDrShare =

(b)useDLTBFDrAllCa

]UNSTETBF[2 TimerExpDLTBFDrShare =

8/13/2019 KPIs_SBS_BR_7



System

116 A30808-X3247-B912-1-7618

(c)useULTBFDrAllCa

]ABRELTBF[3 ULCellResOrdTBFDrShare =

(d)useDLTBFDrAllCa

]ABRELTBF[6 DLCellResOrdTBFDrShare =

Used param.: UNSTETBF[1,2], ABRELTBF[3,6], TBFDrAllCauseUL (14.1.8(a)),TBFDrAllCauseDL (14.1.8(b)))

Elem. Object: Cell

Unit: None

Remark:

14.1.10 TBF drop rate

Long Name: (a) Uplink TBF drop rate due to any cause

(b) Downlink TBF drop rate due to any cause

Short Name: (a) TBFDrRateAllCauseUL

(b) TBFDrRateAllCauseDL

Description : This indicator provides the total TBF drop rate for all causes consideringuplink and downlink directions.

Formula:(a)

]SUCPDASA[1

useULTBFDrAllCa llCauseULTBFDrRateA =

(b)]SUCPDASA[2

useDLTBFDrAllCa llCauseDLTBFDrRateA =

Used param.: SUCPDASA[1,2], TBFDrAllCauseUL (14.1.8(a)), TBFDrAllCauseDL(14.1.8(b))

Elem. Object: Cell

Unit: None

Remark:

14.1.11 TBF Drop frequencyLong Name: (a) Uplink TBF drops frequency

(b) Downlink TBF drops frequency

Short Name: (a) TBFDrFrequUL

(b) TBFDrFrequDL

Description : This indicator provides the TBF drop frequency as the mean number of TBFdrops per hour TBF duration. Uplink and downlink directions are considered.

Formula:

(a) NACTTBF[2]

gran

60 *useULTBFDrAllCa

ULTBFDrFrequ =

8/13/2019 KPIs_SBS_BR_7



System

117 A30808-X3247-B912-1-7618

(b) NACTTBF[4]

gran

60 *useDLTBFDrAllCa

DLTBFDrFrequ =

Used param.: (a) NACTTBF[2,4]; TBFDrAllCauseUL (14.1.8(a)), TBFDrAllCauseDL

(14.1.8(b))Elem. Object: Cell

Unit: Occurrences per hour = (1 / hour)

Remark: In case of low number of TBFs and short TBF duration (e.g. mainly GMMand SM) related data transfer on radio interface the formulas produce aninaccurate result under certain circumstances.

Reasons:

• NACTTBF[2,4] is sampled on a second basis (GMM and SM relatedTBFs might be shorter)

• NACTTBF[2,4] is a real number with 2 digits after decimal point

(x.yy). In case of low number (and short duration) of TBFs during agranularity period the result might be 0.01 or 0.00.

Alternative formula (proposal):

]MEANTBFL[1* NACTTBF[1]

3600 *useULTBFDrAllCa ULTBFDrFrequ =

Advantage:

• Formula works also In case of low number of TBFs and short TBFduration

Disadvantage:• Formula might produce inaccurate result when considerable amountof TBFs are established (triggering of NACTTBF[1,3]) and released(triggering of MEANTBFL[1,2]) in different measurement intervals.

14.1.12 Mean time between TBF drop

Long Name: (a) Mean time between TBF drop of uplink TBF

(b) Mean time between TBF drop of downlink TBF

Short Name: (a) TBFDrMeanTimeUL

(b) TBFDrMeanTimeDL

Description : This indicator provides the mean time between TBF drops related to onehour TBF duration. Uplink and downlink directions are considered.

Formula:(a)

ULTBFDrFrequ

3600 imeULTBFDrMeanT =

(b)

DLTBFDrFrequ

3600 imeDLTBFDrMeanT =

Used param.: TBFDrFrequUL (14.1.11(a)), TBFDrFrequDL(14.1.11(b))

8/13/2019 KPIs_SBS_BR_7



System

118 A30808-X3247-B912-1-7618

Elem. Object: Cell

Unit: Seconds

Remark: Possible inaccuracy of formula:

See remark on KPI 14.1.11 TBF Drop frequency

14.1.13 User data throughput per TBF on the air interface

Long Name: (a) Mean user data throughput per uplink TBF averaged over all CodingSchemes

(b) Mean user data throughput per downlink TBF averaged over all CodingSchemes

(c) Mean user data throughput per uplink TBF depending on Coding Scheme(d) Mean user data throughput per downlink TBF depending on Coding Scheme

Short Name: (a) UserDataThrTBFAvUL

(b) UserDataThrTBFAvDL

(c) UserDataThrTBFCSUL

(d) UserDataThrTBFCSDL

Description : This indicator provides the mean LLC throughput on the air interface per activeuser, i.e. per TBF. Retransmissions are excluded; therefore only the amount ofdata transmitted on behalf of the application layer (here LLC) is considered

The indicator provides the mean throughput related to a single subscriber, i.e. it

provides the throughput the subscriber (or the application in the subscriber’smobile) will experience.

The uplink\downlink directions are separated.

Indicators are provided for the throughput depending on the used CodingScheme and in addition for the throughput averaged over all Coding Schemes.

The KPI for the throughput depending on the used Coding Scheme is based onthe model that an observed TBF has used that Coding Scheme throughout itslife time complete granularity period. This is the achieved throughput if a TBFwere operated exclusively in that Coding Scheme during its life time

Use case Network planning

- comparison of user throughput between cells- comparison of user throughput between Coding Schemes

- monitoring of trends

Formula:(a)

1000

8*

[2] NACTTBF

13]MUTHRF[1.. rTBFAvULUserDataTh =

(b)1000

8*

[4] NACTTBF

26]4..REMUTHRF[1-26].MUTHRF[14. rTBFAvDLUserDataTh =

(c)1000

8*

lUL[c]CSDistrCel*[2] NACTTBF

MUTHRF[c] ]rTBFCSUL[cUserDataTh =

(d)1000

8* lDL[c]CSDistrCel*[4] NACTTBF

13]REMUTHRF[c-13]MUTHRF[c ]rTBFCSDL[cUserDataTh ++=

8/13/2019 KPIs_SBS_BR_7



System

119 A30808-X3247-B912-1-7618

With parameter c for the observed coding scheme:

c = 1 coding scheme CS1




c = 5 coding scheme MCS1




c = 9 coding scheme MMS5





Used param.: (a) NACTTBF [2,4], MUTHRF[all], REMUTHRF[14 .. 26], CSDistrCellUL

(14.3.4(a)), CSDistrCellDL (14.3.4(b)): weighting factors for the distribution oftransmission durations for the different Coding Schemes.

Elem. Object: Cell

Unit: kbit per second

Remark: • Interpretation of KPI result:The observed throughput per user might be unexpectedly low due to thefollowing phenomenon:

• The release of a DL TBF is normally delayed for 1500 seconds(default value of configuration parameter TIMTBFREL).

o During its lifetime a DL TBF may contain once or several times inthe state “delayed TBF release”.

o During that TBF state no LLC data are transmitted.

• The amount of short duration TBFs for GMM (GPRS Mobilitymanagement) and SM (Session management) might be highcompared to TBF which serve for transmission of end-to-end userdata

o The duration of GMM and SM TBFs is typically 0.3 seconds.During that time typically only one ore two RLC/MACC blocks are

transmitted (i.e. 20ms or 40ms of LLC PDU transmission time).o Background: At the begin an at the end of the TBF lifetime no

LLC data are transmitted. During these periods only RLC/MACsignaling takes place: e.g. MS confirmation of TBFestablishment, confirmation of last received RLC/MAC block.

o This effect has more affect on the throughput of short-lived TBFs(GMM, SM) as on long-lived TBFs (end-to-end datatransmission)

• Different treatment of UL and DL direction in the formula

DL throughput:

o The retransmitted throughput in DL direction is included in themeasurement MUTHRF (UL); therefore REMUTHRF (UL) has to

8/13/2019 KPIs_SBS_BR_7



System

120 A30808-X3247-B912-1-7618

be subtracted

UL throughput:

o Retransmissions due to bad radio link quality are not included inmeasurement MUTHRF (UL).

• Systematic error on formula:See remark on KPI 14.2.2 User Throughput on radio interface per cell

• Possible inaccuracy of formula:


14.1.14 Packet resource reassignment attempts

Long Name: (a) Number of packet resource reassignment attempts for uplink TBFs

(b) Number of packet resource reassignment attempts for downlink TBFs

Short Name: (a) ReasAttTBFUL

(b) ReasAttTBFDL

Description : This indicator provides the mean number of packet resource reassignmentattempts per cell separated for uplink and downlink TBFs.

Use case Network optimization

Formula: (a) ReasAttTBFUL = NATPRRE[1]

(b) ReasAttTBFDL = NATPRRE[2]

Used param.: NATPRRE[all]

Elem. Object: Cell

Unit: none

Remark:

14.1.15 Packet resource reassignment failures

Long Name: (a) Number of unsuccessful packet resource reassignment procedures foruplink TBFs

(b) Number of unsuccessful packet resource reassignment procedures fordownlink TBFs

Short Name: (a) ReasFailTBFUL

(b) ReasFailTBFDL

Description : This indicator provides the mean number of unsuccessful packet resourcereassignment procedures per cell separated for uplink and downlink TBFs.


Formula: (a) ReasFailTBFUL = NATPRRE[1] - NSUPRRE[1](b) ReasFailTBFDL = NATPRRE[2] - NSUPRRE[2]

8/13/2019 KPIs_SBS_BR_7



System

121 A30808-X3247-B912-1-7618

Used param.: NATPRRE[all], NSUPRRE[all]

Elem. Object: Cell

Unit: none

Remark:

14.1.16 Packet resource reassignment success rate

Long Name: (a) Packet resource reassignment success rate for uplink TBFs

(b) Packet resource reassignment success rate for downlink TBFs

Short Name: (a) ReasSuccRateTBFUL

(b) ReasSuccRateTBFDL

Description : This indicator provides packet resource reassignment success rate per cellseparated for uplink and downlink TBFs.


Formula:

(a) NATPRRE[1]

NSUPRRE[1] teTBFULReasSuccRa =

(b) NATPRRE[2]

NSUPRRE[2] teTBFDLReasSuccRa =


Elem. Object: Cell

Unit: none

Remark:

14.1.17 Packet resource reassignment failure rate

Long Name: (a) Packet resource reassignment failure rate for uplink TBFs

(b) Packet resource reassignment failure rate for downlink TBFs

Short Name: (a) ReasFailRateTBFUL

(b) ReasFailRateTBFDL

Description : This indicator provides packet resource reassignment failure rate per cellseparated for uplink and downlink TBFs.


8/13/2019 KPIs_SBS_BR_7



System

122 A30808-X3247-B912-1-7618

Formula:

(a) NATPRRE[1]

NSUPRRE[1]- NATPRRE[1] teTBFULReasFailRa =

(b) NATPRRE[2]

NSUPRRE[2]- NATPRRE[2] teTBFDLReasFailRa =


Elem. Object: Cell

Unit: none

Remark:

14.1.18 TBF downgrade / upgrade frequency

Long Name: (a) Uplink TBF upgrade frequency

(b) Uplink TBF downgrade frequency

(c) Downlink TBF upgrade frequency

(d) Downlink TBF downgrade frequency

Short Name: (e) TBFUpgrFrequUL

(f) TBFDowngrFrequUL

(g) TBFUpgrFrequDL

(c) TBFDowngrFrequDL

Description : This indicator provides the TBF downgrade / upgrade frequency as the meannumber of TBF downgrades / upgrades per one hour busy PDCH. Uplink anddownlink directions are considered.

Formula:

(a)] NALLPDCH[3

gran

60 * [1]SERVUGDG

quULTBFUpgrFre =

(b)] NALLPDCH[3

gran

60 * [2]SERVUGDG

requULTBFDowngrF =

(c)] NALLPDCH[6

gran

60 * [3]SERVUGDG

quDLTBFUpgrFre =

(d)] NALLPDCH[6

gran

60 * [4]SERVUGDG

requDLTBFDowngrF =

Used param.: SERVUGDG [1 .. 4], NALLPDCH[3,6]

Elem. Object: Cell

8/13/2019 KPIs_SBS_BR_7



System

123 A30808-X3247-B912-1-7618

Unit: Occurrences per hour = (1 / hour)

Remark:

14.1.19 Mean TBF duration

Long Name: (a) Mean Uplink TBF duration

(b) MeanDownlink TBF duration

Short Name: (a) MeanTBFDurUL

(b) MeanTBFDurDL

Description : This indicator provides the average TBF duration considering uplink anddownlink directions.

Use case Network planning and optimization

Formula: (a) MeanTBFDurUL = MEANTBFL[1]

(b) MeanTBFDurDL = MEANTBFL[2]

Used param.: MEANTBFL[1,2]

Elem. Object: Cell

Unit: Seconds

Remark:

14.1.20 Link adaptation frequency

Long Name: (a) Upward link adaptation frequency for uplink TBF

(b) downward link adaptation frequency for uplink TBF

(c) Upward link adaptation frequency for downlink TBF

(d) downward link adaptation frequency for downlink TBF

Short Name: (a) LinkAdaptFrequUpwUL

(b) LinkAdaptFrequDownwUL(c) LinkAdaptFrequUpwDL

(d) LinkAdaptFrequDownwDL

Description : This indicator provides the link adaptations frequency as the mean number ofupward and downward link adaptations per one hour busy PDCH. Uplink anddownlink directions are considered.

Use Case

Formula:

(a)

] NALLPDCH[3

gran

60 * [1]LADAPTUD

requUpwULLinkAdaptF =

8/13/2019 KPIs_SBS_BR_7


8/13/2019 KPIs_SBS_BR_7



System

125 A30808-X3247-B912-1-7618

Used param.: DISCLPDU[1], NTRLLCFR[2]

Elem. Object: Cell

Unit: None

Remark:

14.2 Network planning (dimensioning )

14.2.1 Total Throughput on air interface per cellLong Name: (a) Total packet Throughput per cell on radio interface in uplink direction

(b) Total packet Throughput per cell on radio interface in downlink direction

Short Name: (a) TotThrUmCellUL

(b) TotThrUmCellDL

Description : The indicators measure the air interface related packet load of a cell in termsof throughput

The signaling and retransmission loads are included.


Use Case Network capacity planning.

Formula: (a)1000

8 *MSTHRF[1])..13]REMUTHRF[113]MUTHRF[1..( llULTotThrUmCe ++=

(b)1000

8 *)MSTHRF[2].26]MUTHRF[14.( llDLTotThrUmCe +=

Used param.: MUTHRF[all], REMUTHRF[1 .. 13], MSTHRF[1,2]

Elem. Object: Cell

Unit: kbit/sec

Remark: The DL retransmitted throughput is included in MUTHRF but not the ULretransmitted throughput

14.2.2 User Throughput on radio interface per cell

Long Name: (a) User Data Throughput per cell on radio interface uplink

(b) User Data Throughput per cell on radio interface downlink

Short Name: (b) UserThrUmCellUL

(c) UserThrUmCellDLDescription : This indicator provides the mean LLC throughput on the air interface per

cell. Retransmissions are excluded; therefore only the amount of data

8/13/2019 KPIs_SBS_BR_7



System

126 A30808-X3247-B912-1-7618

transmitted on behalf of the application layer (here LLC) is considered


The KPI does not indicate the packet throughput experienced by a singlesubscriber. Instead the KPI refers to the mean user packet load of a whole

cell according to the following model: The user packet volume transmitted foa cell is accumulated over the whole granularity period and afterwardsdivided by the length of granularity period

Use Case Network capacity planning.

Formula:(a)

1000

8 *13]MUTHRF[1.. ellULUserThrUmC =

(b)1000

8 *4..26])REMUTHRF[1-..26](MUTHRF[14 ellDLUserThrUmC =

Used param.: MUTHRF[all], REMUTHRF[14 .. 26],

Elem. Object: Cell

Unit: kbit/sec

Remark: DL throughput:

• The retransmitted throughput in DL direction is included in themeasurement MUTHRF (UL); therefore REMUTHRF (UL) has to besubtracted

UL throughput:

• Retransmissions due to bad radio link quality are not included inmeasurement MUTHRF (UL).

• Systematic error in formula:

The MS may also retransmit a previously transmitted RLC/MAC blockwhen nothing else has to be transmitted in UL direction. In that casethe BSC will receive certain RLC/MAC block more than once. Thecounter MUTHRF (UL ) registers each of these receipts. ThereforeUserThrUmCellUL contains a systematic error. For short duration TBF(GMM/SM activities) the error is larger than for medium or longduration TBFs (e,g, TBF for WAP session or ftp).

14.2.3 Uplink / Downlink distribution of user throughput on radiointerface per cell

Long Name: (c) Uplink share of user throughput on radio interface

(d) Downlink share of user throughput on radio interface

Short Name: (a) UserThrUmCellULShare

(b) UserThrUmCellDLShare

Description : This indicator provides the uplink and downlink distribution of user packetdata transmission per cell on radio interface.

Formula:(a)

CellDLUserThrUmellULUserThrUmC

ellULUserThrUmC ellULShareUserThrUmC

+=

8/13/2019 KPIs_SBS_BR_7



System

127 A30808-X3247-B912-1-7618

(b)CellDLUserThrUmellULUserThrUmC

ellDLUserThrUmC ellDLShareUserThrUmC

+=

Used param.: UserThrUmCellUL (14.2.2 (a)) UserThrUmCellDL (14.2.2 (c))

Elem. Object: Cell

Unit: None

Remark: None

14.2.4 Total packet volume transmitted on radio interface per cell

Long Name: (a) Total packet volume transmitted on radio interface per cell in uplinkdirection including retransmitted throughput

(b) Total packet volume transmitted on radio interface per cell in downlinkdirection including retransmitted throughput

Short Name: (a) TotVolUmCellUL

(b) TotVolUmCellDL

Description : The indicators measure the air interface related packet load of a cell in termsof transmitted data volume.

The signaling and retransmission loads are included.


Use Case Network capacity planning.Formula: (a) TotVolUmCellUL = TotThrUmCellUL * gran * 60

(b) TotVolUmCellDL = TotThrUmCellDL * gran * 60

Used param.: TotThrUmCellUL, TotThrUmCellDL (14.2.1), granularity period “gran” inminutes

Elem. Object: Cell

Unit: kbit

Remark:

14.2.5 Total packet Throughput on Gb interface per cell

Long Name: (a) Total packet throughput on Gb uplink

(b) Total packet throughput on Gb downlink

Short Name: (a) TotThrGbCellUL

(b) TotThrGbCellDL

Description : This indicator provides the total packet throughput per cell on the Gbinterface in the uplink/downlink direction.

8/13/2019 KPIs_SBS_BR_7



System

128 A30808-X3247-B912-1-7618

The total packet throughput comprises user data (LLC layer) includingBSSGP header and BSSGP signaling

Formula:(a)

1000

8 *MSTHBS[1])(MUTHBS[1] llULTotThrGbCe +=

(b)1000

8 *MSTHBS[2])(MUTHBS[2] llDLTotThrGbCe +=

Used param.: MUTHBS[1,2];MSTHBS[1,2];

Elem. Object: Cell

Unit: kbit/sec

Remark: None

14.2.6 User data Throughput on Gb interface per cell

Long Name: (a) User Data Throughput on Gb uplink

(b) User Data Throughput on Gb downlink

Short Name: (a) UserThrGbCellUL

(b) UserThrGbCellDL

Description : This indicator provides the mean user data throughput on LLC layer per cellon the Gb interface in the uplink/downlink direction.

Formula:(a)

1000

8 * MUTHBS[3] ellULUserThrGbC =

(b)1000

8 * MUTHBS[4] ellDLUserThrGbC =

Used param.: MUTHBS[3,4]

Elem. Object: Cell

Unit: kbit/secRemark: None

14.2.7 Mean number of busy PDCH per cell

Long Name: (a) Mean number of PDCHs busy per cell for UL transmission

(b) Mean number of PDCHs busy per cell for DL transmission

Short Name: (a) MeanPDCHBusyCellUL

8/13/2019 KPIs_SBS_BR_7



System

129 A30808-X3247-B912-1-7618

(b) MeanPDCHBusyCellDL

Description : This KPI provides the mean number of PDCHs per cell with at least one ULTBF respectively at least one downlink TBF in progress

Use case Network planing

Formula: (a) MeanPDCHBusyCellUL = NALLPDCH [3](b) MeanPDCHBusyCellDL = NALLPDCH [6]

Used param.: NALLPDCH [3,6]

Elem. Object: Cell

Unit: None

Remark: None

14.2.8 PDCH util ization rate

Long Name: (a) Average utilization rate of UL busy PDCHs in terms of used transmissiontime

(b) Average utilization rate of DL busy PDCHs in terms of used transmissiontime

Short Name: (a) MeanBusyPdchUtilCellUL

(b) MeanBusyPdchUtilCellDL

Description : This KPI provides the average utilisation of busy PDCHs in terms of thenumber of transmitted PDUs relative to the possible PDUs.

In order to measure the overall utilization the retransmissions and thesignaling PDUs are included.

The KPI is for uplink and downlink direction.

Difference to TCH utilization:

- A TCH is fully utilized by a single CS connection.

- The capacity of a PDCH is normally not fully occupied when one ormore TBFs are allocated to that PDCH. The TBFs will in most cases

occupy only a part of the PDCHs transmission capacity.

Use case Network planning

Formula:(a)

]3[

) 20

MSTHRF[1]

60*gran

13])[11. NRETPDU1.13](NTRAPDU[1½11])..[1 NRETPDU..11](NTRAPDU[1(*2

ULchUtilCellMeanBusyPd

NALLPDCH

++++

=

8/13/2019 KPIs_SBS_BR_7



System

130 A30808-X3247-B912-1-7618

(b)

]6[

) 20

MSTHRF[2]

60*gran

..26] NTRAPDU[24½..23] NTRAPDU[14(*2

DLchUtilCellMeanBusyPd

NALLPDCH

++

=

Used param.: NTRAPDU [all], NRETPDU [1 .. 13], MSTHRF[1,2], NALLPDCH [3,6]

Elem. Object: Cell

Unit: percentage

Remark: It is noted that for CS1 .. CS4 and MSC1 .. MSC7 a PDCH can transport 50RCL/MAC PDUs per second in each direction (UL and DL). I.e. one PDUrepresents a transmission time of 20ms. In other words: one PDU pesecond equals to 2% occupation time of a PDCH.

For MSC7 .. MSC 9 an RLC/MAC PDU occupies only half a radio block. I.e.in that case one RLC/MAC PDU represents a transmission time of only10ms. In other words: one PDU per second equals to 1% occupation time ofa PDCH.

For BR7 NTRAPDU does not include the RLC/MAC signaling. Therefore thenumber of signaling PDUs has to be added. That number will be calculatedfrom the signaling throughput (MSTHRH) by assuming that each signalingPDU has exactly a length of 20bytes (maximum length of CS1 frame)

14.2.9 Mean User Throughput per busy PDCH

Long Name: (a) Mean User Throughput Uplink per busy PDCH cumulated on all CodingSchemes

(b) Mean User Throughput Downlink per busy PDCH cumulated on allCoding Schemes

(c) Mean User Throughput Uplink per busy PDCH depending on the CodingScheme

(d) Mean User Throughput Downlink per busy PDCH depending on the

Coding SchemeShort Name: (a) MeanUserThrBusyPdchUL

(b) MeanUserThrBusyPdchDL

(c) MeanUserThrBusyPdchCSUL

(d) MeanUserThrBusyPdchCSDL

Description : This indicator provides the mean LLC packet throughput per busy PDCH percell.

The uplink and downlink directions are separated.

Indicators are provided for the throughput depending on the used Coding

Scheme and in addition for the throughput cumulated over all CodingSchemes

8/13/2019 KPIs_SBS_BR_7



System

131 A30808-X3247-B912-1-7618

The KPI for the throughput depending on the used Coding Scheme is basedon the model that an observed busy PDCH has used that Coding Schemethroughout the complete granularity period. This is the achieved throughput ia PDCH were operated exclusively in that Coding Scheme during thegranularity period

Use case Network planning (network extension): KPI provides the capacity, which canbe provided per PDCH. Assume the user traffic model is given by means ofdata volume per subscriber and number of subscribers per cell. For thatscenario the present KPIs aids to calculate the number of needed PDCHs forthe concerned cell

Formula:

(a)]3[

1000

8 *13]MUTHRF[1..

LrBusyPdchUMeanUserTh NALLPDCH

=

(b)

]6[

1000

8 *4..26])REMUTHRF[1-..26](MUTHRF[14

LrBusyPdchDMeanUserTh

NALLPDCH

=

(c)[c]lULCSDistrCel*]3[

1000

8*MUTHRF[c]

SUL[c]rBusyPdchCMeanUserTh NALLPDCH

=

(d)

[c]lDLCSDistrCel*6][

1000

8*13])REMUTHRF[c-13](MUTHRF[c

SDL[c]rBusyPdchCMeanUserTh NALLPDCH

++=








c = 7 coding scheme MCS3c = 8 coding scheme MCS4






Used param.: NALLPDCH [3,6], MUTHRF[all], REMUTHRF[14 .. 26]

CSDistrCellUL (14.3.4(a)), CSDistrCellDL (14.3.4(b)): weighting factors for

the distribution of transmission durations for the different Coding Schemes.

Elem. Object: Cell

8/13/2019 KPIs_SBS_BR_7



System

132 A30808-X3247-B912-1-7618

Unit: kbit/sec

Remark:

• Please note that no RLC/MAC signaling and no RLC/MAC headersand are included in this indicator. Also retransmissions are excluded.Therefore the total amount of data transmitted via RLC/MAC layers

per PDCH is higher.

• Interpretation of KPI result:The observed throughput per user might be unexpectedly low due tothe following phenomenon:

• The release of a DL TBF is normally delayed for 1500 seconds(default value of configuration parameter TIMTBFREL).

o During its lifetime a DL TBF may contain once or severaltimes in the state “delayed TBF release”.

o During that TBF state no LLC data are transmitted.

• The amount of short duration TBFs for GMM (GPRS Mobility

management) and SM (Session management) might be highcompared to TBF which serve for transmission of end-to-end userdata

o The duration of GMM and SM TBFs is typically 0.3 seconds.During that time typically only one ore two RLC/MACC blocksare transmitted (i.e. 20ms or 40ms of LLC PDU transmissiontime).

o Background: At the begin an at the end of the TBF lifetime noLLC data are transmitted. During these periods onlyRLC/MAC signaling takes place: e.g. MS confirmation of TBFestablishment, confirmation of last received RLC/MAC block.

o This effect has more affect on the throughput of short-livedTBFs (GMM, SM) as on long-lived TBFs (end-to-end datatransmission)

• Different treatment of UL and DL direction in the formula

DL throughput:

o The retransmitted throughput in DL direction is included in themeasurement MUTHRF (UL); therefore REMUTHRF (UL) hasto be subtracted

UL throughput:

o Retransmissions due to bad radio link quality are not includedin measurement MUTHRF (UL).

• Systematic error on formula:See remark on KPI 14.2.2 User Throughput on radio interface per cell

• Possible inaccuracy of formula:


14.2.10 Mean number of simultaneously active TBFs per cell

Long Name: (a) Mean number of simultaneously active TBF per cell uplink

8/13/2019 KPIs_SBS_BR_7



System

133 A30808-X3247-B912-1-7618

(b) Mean number of simultaneously active TBF per cell downlink

Short Name: (a) MeanActTbfUL

(b) MeanActTbfDL

Description : This indicator provides the mean number of simultaneously active TBFs fothe uplink and downlink direction.

Use case Network planning: how many MS have data transmission simultaneously in acell.

Formula: (a) MeanActTbfUL = NACTTBF[2];

(b) MeanActTbfDL = NACTTBF[4];

Used param.: NACTTBF[2,4];

Elem. Object: Cell

Unit: None

Remark: None

14.2.11 Mean number of TBFs multiplexed on same PDCH

Long Name: (a) Mean number of uplink TBFs multiplexed on the same PDCH

(b) Mean number of downlink TBFs multiplexed on the same PDCH

Short Name: (a) MeanTBFMultiplPDCHUL

(b) MeanTBFMultiplPDCHDL

Description : This indicator provides the mean number of TBFs multiplexed on the samePDCH (horizontal allocation) for the uplink and downlink direction.

Use case Network optimization. E.g. tuning of the parameters for PDCH allocation (inconnection with the KPIs for packet throughput per user, see chapte14.1.13)

Formula: (a) MeanTBFMultiplPDCHUL = NTBFPDC[2];

(b) MeanTBFMultiplPDCHDL = NTBFPDC[4];

Used param.: NTBFPDC[2,4];

Elem. Object: Cell

Unit: None

Remark: None

14.2.12 Mean number of allocated PDCHs per TBF

Long Name: (a) Mean number of allocated PDCHs per uplink TBF

(b) Mean number of allocated PDCHs per downlink TBF

Short Name: (a) MeanAllocPdchTbfUL(b) MeanAllocPdchTbfDL

8/13/2019 KPIs_SBS_BR_7



System

134 A30808-X3247-B912-1-7618

Description : This indicator provides the mean number of PDCHs assigned to a TBF fothe uplink and downlink direction (horizontal allocation)

Use case Monitoring of MS behavior: penetration of the MS multi slot classes

Formula:(a)

, NACTTBF[2]

[3] NALLPDCH* NTBFPDC[2] dchTbfULMeanAllocP =

(b) NACTTBF[4]

[6] NALLPDCH* NTBFPDC[4] dchTbfDLMeanAllocP =

Used param.: NACTTBF[2,4]; NALLPDCH [3,6]; NTBFPDC[2,4]

Elem. Object: Cell

Unit: None

Remark: Eplanation of the formula:

How to calculate the the mean number of PDCHs assigned to a TBF for e.g.

downlink direction (horizontal allocation)

NTBFPDC (9,26): Max, Mean Number of TBFs Allocated per PDCH(Uplink/Downlink) per Cell

NACTTBF[4]

[6] NALLPDCH* NTBFPDC[4] dchTbfDLMeanAllocP =

à NTBFPDC[4] = 2.5

8/13/2019 KPIs_SBS_BR_7



System

135 A30808-X3247-B912-1-7618

à NALLPDCH[6] = 4 PDCH * 3 min / 15min = 0.8 PDCHà NACTTBF[4] = (3min * 60 * 3TBFs / (15min * 60) = 0.6Note: NACTTBF = = The measurement determines in intervals of 1 second the

number of TBFs currently active. At the end of the granularity period the arithmeticmean value of the samples is calculated.

è MeanAllocPdchTbfDL = 2.5 * 0.8/0.6 = 3.33 PDCHs/TBF

14.3 Network optimization

14.3.1 Retransmission Rate on radio interface per cell per codingscheme

Long Name: (a) Uplink retransmission Rate on radio interface per cell per coding scheme

(b) Downlink retransmission Rate on radio interface per cell per codingscheme

Short Name: (a) RetransRateUmCellULCS

(b) RetransRateUmCellDLCS

Description : This indicator provides the retransmission rate on the radio interface percoding scheme by the ratio of the number of RLC/MAC PDUs needed foruser data retransmission and the overall number of transmitted user dataPDUs.

The uplink and downlink directions are considered separatelyUse case KPI used for Network quality optimization:

-> optimize C/I thresholds for coding scheme selection

Formula:(a)

NRETPDU[c] NTRAPDU[c]

NRETPDU[c] S[c]eUmCellULCRetransRat

+=

(b)c] NTRAPDU[13

c] NRETPDU[13 S[c]eUmCellDLCRetransRat

++

=












8/13/2019 KPIs_SBS_BR_7



System

136 A30808-X3247-B912-1-7618



Used param.: NTRAPDU[all], NRETPDU[all],

Elem. Object: CellUnit: none

Remark: In DL direction NTRAPDU contains the retransmitted PDUs. But in ULdirections retransmission is not included in NTRAPDU.

14.3.2 Retransmitted user throughput on radio interface per cell percoding scheme

Long Name: (a) Retransmitted user Throughput on radio interface per cell per codingscheme in uplink direction

(b) Retransmitted user Throughput on radio interface per cell per codingscheme in downlink direction

Short Name: (a) UserThrRetrCellUmULCS

(b) UserThrRetrCellUmDLCS

Description : This indicator provides the retransmitted user Throughput on the radiointerface per cell per coding scheme.


Use Case KPI used for Network quality optimization:-> optimize C/I thresholds for coding scheme selection

Formula:(a)

1000

8 *]REMUTHRF[c S[c]rCellUmULCUserThrRet =

(b)1000

8 *c]3REMUTHRF[1 S[c]rCellUmDLCUserThrRet +=

With parameter c for the observed coding scheme:c = 1 coding scheme CS1











8/13/2019 KPIs_SBS_BR_7


8/13/2019 KPIs_SBS_BR_7



System

138 A30808-X3247-B912-1-7618




Used param.: MUTHRF[all],

Elem. Object: Cell

Unit: none

Remark: Remarks

In DL directions the retransmission is included in MUTHRF[13 .. 26] but in ULdirection the retransmission is excluded from MUTHRF[1.. 13]. For simplicityit is assumed that the throughput distribution on coding schemes is mainlyindependent from the inclusion or exclusion of retransmissions.

14.3.4 Timely distribution of the coding scheme utilization on theradio interface

Long Name: (a) Timely distribution of the coding scheme utilization in uplink direction percell

(b) Timely distribution of the coding scheme utilization in uplink direction percell

Short Name: (a) CSDistrCellUL

(b) CSDistrCellDL

Description : This indicator provides the timely distribution of the utilization of the variouscoding schemes during the observed granularity period

The uplink and downlink directions are considered separately

Use Case During the planning phase of a radio network (i.e. before deployment) thedistribution of the user data transmission on Coding Schemes is predicted bysimulation results. By aid of the presents KPIs these simulation results maybe replaced by the experiences of an operating network. This could help e.g.for the planning of future network expansions (capacity enhancements or

expansion of the coverage area of the network)

Formula:(a)

13]1.. NTRAPDU[1*½10].. NTRAPDU[1

NTRAPDU[c] lUL[c]CSDistrCel

+=

for c = 1 .. 10

13]1.. NTRAPDU[1*½10].. NTRAPDU[1

NTRAPDU[c]*½ lUL[c]CSDistrCel

+=

for c = 11 .. 13

(b)26].. NTRAPDU[24*½23].. NTRAPDU[14

13] NTRAPDU[c lDL[c]CSDistrCel

++

=

for c = 1 .. 10

26].. NTRAPDU[24*½23].. NTRAPDU[14

13] NTRAPDU[c*½ lDL[c]CSDistrCel

++=

8/13/2019 KPIs_SBS_BR_7



System

139 A30808-X3247-B912-1-7618

for c = 11 .. 13














Used param.: NTRAPDU[all]

Elem. Object: Cell

Unit: none

Remark: Remarks

• In DL directions the retransmission is included in NTRAPDU[13 .. 26]

but in UL direction the retransmission is excluded from NTRAPDU[1..13]. For simplicity it is assumed that the timely CS distribution ismainly independent from the inclusion or exclusion of retransmissions

• An RLC/MAC PDU for coding schemes MSC7 .. MSC9 occupies halof a radio block (i.e. the duration is ½ * 20ms). Whereas for all othercoding schemes an RLC/MAC PDU occupies a full radio block (i.e.the duration is 20ms).

14.4 Cell Reselection

14.4.1 Number of network controlled Intra BSC cell reselectionattempts per cell

Long name: (a) Number of network controlled Intra BSC cell reselection attempts per cell

Short name: (a) NumNCIntrBSCCellResAttDescription: This indicator provides the number of network controlled Intra BSC cell

8/13/2019 KPIs_SBS_BR_7



System

140 A30808-X3247-B912-1-7618

reselection attempts per cell

Formula: (a) NumNCIntrBSCCellResAtt = ATINCCRS[1]

Used param.: ATINCCRS [1]

Elem. Object: Cell

Unit: None

Remarks: None

14.4.2 Number of successful network controlled Intra BSC cellreselections per cell

Long name: (a) Number of successful network controlled Intra BSC cell reselections per cellShort name: (a) NumNCIntrBSCCellResSuc

Description: This indicator provides the number of successful network controlled Intra BSCcell reselections per cell

Formula: (a) NumNCIntrBSCCellResSuc = SUINCCRS[1]

Used param.: SUINCCRS[1]

Elem. Object: Cell

Unit: None

Remarks: None

14.4.3 Number of network control led Intra BSC cell reselectionfailures per cell per cause

Long name: (a) Number of network controlled Intra BSC cell reselection failures per cell dueto Frequency not implemented

(b) Number of network controlled Intra BSC cell reselection failures per cell due

to No response on target cell

(c) Number of network controlled Intra BSC cell reselection failures per cell dueto Imm. Assignment Reject or Packet Access Reject on target cell

(d) Number of network controlled Intra BSC cell reselection failures per cell dueto Ongoing CS connection

(e) Number of network controlled Intra BSC cell reselection failures per cell dueto Anonymous Access

(f) Number of network controlled Intra BSC cell reselection failures per cell dueto MS in GMM standby state

(g) Number of network controlled Intra BSC cell reselection failures per cell due

to Forced to the standby stateShort name: (a) NumNCIntrBSCCellResFailFrequNotImpl

8/13/2019 KPIs_SBS_BR_7



System

141 A30808-X3247-B912-1-7618

(b) NumNCIntrBSCCellResFailFrequNoRespTarget

(c) NumNCIntrBSCCellResFailAccessRejTarget

(d) NumNCIntrBSCCellResFailCSOngoing

(e) NumNCIntrBSCCellResFailAnonyAccess

(f) NumNCIntrBSCCellResFailGMMStandby

(g) NumNCIntrBSCCellResFailForcedStandby

Description: These indicators provides the number of unsuccessful network controlled IntraBSC cell reselections per cell per cause

Formula: (a) NumNCIntrBSCCellResFailFrequNotImpl = UNINCCRS [1]

(b) NumNCIntrBSCCellResFailFrequNoRespTarget = UNINCCRS [2]

(c) NumNCIntrBSCCellResFailAccessRejTarget = UNINCCRS [3]

(d) NumNCIntrBSCCellResFailCSOngoing = UNINCCRS [4]

(e) NumNCIntrBSCCellResFailAnonyAccess = UNINCCRS [5]

(f) NumNCIntrBSCCellResFailGMMStandby = UNINCCRS [6]

(g) NumNCIntrBSCCellResFailForcedStandby = UNINCCRS [7]

Used param.: UNINCCRS[all]

Elem. Object: Cell

Unit: None

Remarks: None

14.4.4 Network controlled Intra BSC cell reselection success rate

Long name: (a) Success rate for network controlled Intra BSC cell reselections

Short name: (a) NCIntrBSCCellSucRate

Description: This indicator provides the success rate for network controlled Intra BSC cellreselection per cell

Formula:(a)

]ATINCCRS[1

]SUINCCRS[1 ellSucRate NCIntrBSCC =

Used param.: SUINCCRS[1], ATINCCRS[1]

Elem. Object: Cell

Unit: None

Remarks: None

14.4.5 Network controlled Intra BSC cell reselection failure rate

Long name: (a) Network controlled Intra BSC cell reselection failure rate for cause Frequencynot implemented

(b) Network controlled Intra BSC cell reselection failure rate for cause No

8/13/2019 KPIs_SBS_BR_7



System

142 A30808-X3247-B912-1-7618

response on target cell

(c) Network controlled Intra BSC cell reselection failure rate for cause Imm. Assignment Reject or Packet Access Reject on target cell

(d) Network controlled Intra BSC cell reselection failure rate for cause OngoingCS connection

(e) Network controlled Intra BSC cell reselection failure rate for cause Anonymous Access

(f) Network controlled Intra BSC cell reselection failure rate for cause MS inGMM standby state

(g) Network controlled Intra BSC cell reselection failure rate for cause Forced tothe standby state

Short name: (a) NCIntrBSCResFailRateFrequNotImpl

(b) NCIntrBSCResFailRateNoRespTarget

(c) NCIntrBSCResFailRateAccessRejTarget

(d) NCIntrBSCResFailRateCSOngoing

(e) NCIntrBSCResFailRateAnonymAccess(f) NCIntrBSCResFailRateGMMStandby

(g) NCIntrBSCResFailRateForcedStandby

Description: These indicators provides the number of unsuccessful network controlled IntraBSC cell reselections per cause

Formula:(a)

]ATINCCRS[1

]UNINCCRS[1 plFrequNotImesFailRate NCIntrBSCR =

(b)]ATINCCRS[1

]UNINCCRS[2et NoRespTargesFailRate NCIntrBSCR =

(c)]ATINCCRS[1

]UNINCCRS[3argetAccessRejTesFailRate NCIntrBSCR =

(d)]ATINCCRS[1

]UNINCCRS[4 CSOngoingesFailRate NCIntrBSCR =

(e)]ATINCCRS[1

]UNINCCRS[5 ssAnonymAcceesFailRate NCIntrBSCR =

(f)]ATINCCRS[1

]UNINCCRS[6 GMMStandbyesFailRate NCIntrBSCR =

(g)]ATINCCRS[1

]UNINCCRS[7dbyForcedStanesFailRate NCIntrBSCR =

Used param.: UNINCCRS[all], ATINCCRS[1]

Elem. Object: Cell

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

143 A30808-X3247-B912-1-7618

15 Miscellaneous Performance Indicators

15.1 BSC ProcessorloadLong name: (a) Mean BSC MPCC Processor load

(b) Mean BSC TDPC Processor load

(c) Mean BSC PPXU0 / PCU0 Processor load

(d) Mean BSC PPXU1 / PCU1 Processor load

(e) Mean BSC PPXU2 Processor load

(f) Mean BSC PPXU3 Processor load

(g) Mean BSC PPXU3 Processor load

(h) Mean BSC PPXU4 Processor load

Short name: (a) MPPCLoad

(b) TDPCLoad

(c) PPXU0Load

(d) PPXU1Load

(e) PPXU2Load

(f) PPXU3Load

(g) PPXU4Load

(h) PPXU5Load

Description: These indicators provide the processor load at the BSC for the MPCC

(Administrative Processor), TDPC (Telephony Processor) and the processors forthe Packet Control Units (PPCUs / PPXUs)

Formula:(a)

100

]BSCPRCLD[2 MPPCLoad =

(b)100

]BSCPRCLD[4 TDPCLoad =

(c)100

]BSCPRCLD[6 PPXU0Load =

(d)100

]BSCPRCLD[8 PPXU1Load =

(e)100

0]BSCPRCLD[1 PPXU2Load =

(f)100


(g)100


(h)

100


Used param.: BSCPRCLD[2, 4, 6, 8, 10, 12, 14, 16]

8/13/2019 KPIs_SBS_BR_7



System

144 A30808-X3247-B912-1-7618

Elem. Object: BSC

Unit: None

Remarks: None

8/13/2019 KPIs_SBS_BR_7



System

145 A30808-X3247-B912-1-7618

15.2 BTSE Processorload

Long name: (a) Mean BTSE Processor load

Short name: (a) BTSEPRLD

Description: This indicator provides the mean BTSE processor load.

Formula:

(a) 100

]BTSEPRLD[1 BTSEPRLD=

Used param.: BTSEPRLD[1]

Elem. Object: BTSM

Unit: None

Remarks: None

15.3 Paging Response / Location Update Ratio per Cell

Long name: (a) Paging Response / Location Update Ratio per Cell

Short name: (a) PagRespLocUpdRatioPerCell

Description: This indicator will give you the ratio between Pagings and Location Updates withina single cell.

Formula:(a)

[5,13,21] NSUCCHPC

17]9,[1, NSUCCHPC CellrUpdRatioPePagRespLoc =

Used param.: clause on "Interpretation of KPI result" added to Remarks [1,5,9,13,17,21]

Elem. Object: Cell

Unit: None

Remarks: The Paging Response Ratio / Location Update Ratio per cell is related to theImmediate Assignment Procedure.

8/13/2019 KPIs_SBS_BR_7



System

146 A30808-X3247-B912-1-7618

15.4 BSC <-> MSC/SMLC CCS7 Load

Long name: (a) BSC -> MSC CCS7 Load

(b) MSC -> BSC CCS7 Load

(c) Total BSC <-> MSC CCS7 Load

(d) BSC -> SMLC CCS7 Load

(e) SMLC -> BSC CCS7 Load

(f) Total BSC <-> SMLC CCS7 Load

Short name: (a) Y_BSC->MSC

(b) Y_MSC->BSC

(c) Y_BSC<->BSC

(d) Y_BSC->SMLC

(e) Y_SMLC->BSC

(f) Y_BSC<->SMLCDescription: Approximate load on the Link Set between BSC and MSC, which were caused of

MSUs sent by BSC, vice versa and total.

Formula:(a) Erl

s sbyteGRAN

Min Length MSU NMSUTRAS MSC BSC Y

60/8000

1 _ ]1[ _

⋅⋅⋅∅⋅

=>−

(b) Erl s sbyteGRAN

Min Length MSU NMSUREC BSC MSC Y

60/8000

1 _ ]1[ _

⋅⋅⋅∅⋅

=>−

(c) Erl2

BSCY_MSC-MSCY_BSC- MSC-Y_BSC

>+>=><

(d) Erl s sbyteGRAN

Min Length MSU NMSUTRAS SMLC BSC Y

60/8000

1 _ ]2[ _

⋅⋅⋅∅⋅=>−

(e) Erl s sbyteGRAN

Min Length MSU NMSUREC BSC SMLC Y

60/8000

1 _ ]2[ _

⋅⋅⋅∅⋅

=>−

(f) Erl2

BSCY_SMLC-SMLCY_BSC- MSC-Y_BSC

>+>=><

Used param.: NMSUTRAS[1,2], NMSUREC[1,2], Granularity in minutes

Elem. Object: Cell

Unit: Erlang

Remarks: ∅MSU_Length : Average length of a MSU. This value cannot be measured withthe existing scanners. An assumption has to be made with the help of trafficmodels. At the present message structure the MSU has an average length about35byte. With introduction or extension of services (for example SMS) this value willincrease in future.

BR7: additional formulas for BSC -> SMLC CCS7 load. SMLC: Serving MobileLocation Center

8/13/2019 KPIs_SBS_BR_7



System

147 A30808-X3247-B912-1-7618

16 BSS related KPIs at Siemens MSC

At the Siemens MSC/VLR it is also possible to start the following measurement jobs

for BSS specific measurements:• REC INTCELL: BSS specific measurements per cell

• REC LOCAREA: BSS specific measurements per Location Area

• RECMSC: MSC and BSS specific measurements per MSC

With the above Siemens performance measurements it is possible to evaluate atleast the following key performance indicators:

• Location Update Success Rate per Location Area

• Paging Success Rate per Location Area

• Paging Ratio / Location Update Ratio per Location Area• Handover Failures per Cell

• Handover Successes per Cell

• Dropped Calls per Cell

• Call Setup Failures per Cell

• Assignment Failures per Cell

• TCH Requests per Cell

• Busy Hour Call Attempts (BHCA) per MSC

• Mean Holding Time per MSC

• MOC / MTC / MTM distribution

For more information please refer to the SSS customer documentation.

8/13/2019 KPIs_SBS_BR_7



System

148 A30808-X3247-B912-1-7618

17 Appendix

17.1 List of BSS Performance Measurements

Short Name Long Name

AALTCHTI All available TCH allocated time

ABRELTBF Number of abnormal released TBFs (BSSGP) per cell per cause ABISPDIS Abis Pool Distribution

ABISPSUP Abis Pool Supervision AININIRH Attempted incoming internal intercell Handovers per originating cell

AISHINTE Attempted Internal SDCCH Handovers Intercell AISHINTR Attempted internal SDCCH Handovers Intracell

AMRCHDIS Adaptive Multirate channel type uplink/downlink distribution AMRFRMDL Frame measurements for Adaptive Multi-Rate (AMR) on uplink busyTCHs’

AMRFRMUL Frame measurements for Adaptive Multi-Rate (AMR) on downlink busyTCHs’

AMRSIDUL SID_UPDATE frame measurements for Adaptive Multi-Rate (AMR) onuplink busy TCHs’

AMRVAR Voice Activity Rate for Adaptive Multi-Rate (AMR) on uplink/downlink busyTCHs’

AOINTESH Attempted MSC controlled SDCCH Handovers AOUINIRH Attempted outgoing intercell Handovers per cause, per neigh-bourcell

relationship

ASDCALTI All available SDCCH allocated time ATCHSMBS Attempted TCH seizures meeting a TCH blocked state (Full-rate/Halfrate)

ATIMASCA Attempted immediate assignment procedures, per cause ATINBHDO Attempted outgoing inter BSC Handovers per neighbour cell re-lationship

ATINCCRS Attempted internal network controlled reselections per cell

ATINHIAC Attempted internal Handovers, intracell, per cause ATINHIRC Attempted internal Handovers, intercell, per cause

ATOISHDO Attempted Outgoing Intersystem Handover per neighbourcell per cause ATSDCMBS Attempted SDCCH seizure meeting an SDCCH blocked state

ATTCHSEI Attempted TCH seizures (Fullrate/Halfrate)BSCPRCLD BSC processor load

BTSEPRLD BTSE processor loadCFERRXQU Correlated FER to RXQUAL measurements

CRXLVQUD Correlated RXLEV to RXQUAL measurements (doenlink)CRXLVQUU Correlated RXLEV to RXQUAL measurements (uplink)

CRXLVTAD Correlated RXLEV to Time Advance measurements (downlink)CRXLVTAU Correlated RXLEV to Time Advance measurements (uplink)

DASPUNT Duration of Adjacent Signalling Point (ASP) unavailable condi-tionDISCLPDU Number of discarded LLC PDU per cell

DLKSERST Duration of link in-service state

DLKUNCON Duration of the linkset unavailable conditionsDSLUNAV Duration of signaling link unavailability

HOFITABS Total number of Handover failures, intra BSCIFRMABIS I-frame measurements

ILUPLKIC Interference measurements on idle TCHs

8/13/2019 KPIs_SBS_BR_7



System

149 A30808-X3247-B912-1-7618

LADAPTUD Link adaptation measurements (uplink/downlink) per cellLOCAUTCH Number of locally generated automatic changeovers

MAXBUSDC Maximum number of busy SDCCHs per cellMBTCHCHT Mean number of busy TCH per channel type

MBUSYSDC Mean number of busy SDCCHs

MDURTCRQ Mean duration a TCH is queued (Fullrate/Halfrate)MDURTCSD Mean Duration a TCH/SD with TCH_SD_Pool can be used as SDCCHMEANTBFL Mean TBF length (uplink/downlink) per cell

MEBUSTCH Mean number of busy TCHs (Fullrate/Halfrate)MEITCHIB Mean number of idle TCHs per interference band

MSTHBS Mean signaling data throughput (uplink/downlink) per cell on the BSSGPLayer Gb interface

MSTHRF Mean signaling data throughput (uplink/downlink) per cell on the RFinterface

MTCHBUTI Mean TCH busy time (Fullrate/Halfrate)MTCHQLEN Mean TCH queue length (Fullrate/Halfrate)

MUTHBS Mean user data throughput (uplink/downlink) per cell on the BSSGP Layer

Gb interfaceMUTHRF Mean user data throughput (uplink/downlink) per cell on the RF Interface

NACSUCPR Number of accesses with a successful result by procedure (PCH, AGCHand RACH)

NACTTBF Total, Mean number of active TBF

NALIPDCH Min, max, mean number of activated PDCHs per cellNALLPDCH Min, max, mean number of used (active TBF) PDCHs (uplink/downlink)

per cellNASPAVUN Number of transitions of the Adjacent Signalling Point (ASP) from

available to unavailable

NASUSDPE Number of successful SDCCH seizures in a period

NATPRRE Number of attempted packet resource reassignment procedures per cellNATTSDPE Number of attempted SDCCH seizures in a periodNAVPDCH Number of available PDCH per cell

NAVSDCCH Number of available SDCCHs

NAVTCH Number of available TCHs (Fullrate/Halfrate)NAVTCHSD Number of available TCH/SD per Cell

NDEFPDCH Min, max, mean number of defined (configured) PDCHs per cellNDESDCCH Number of defined SDCCHs

NDFTCHSD Number of defined TCH/SDNHOINRHA Number of handover indications not resulting in a handover at-tempt

NINVPRACH Number of invalid PRACH messages per cell per causeNINVRACH Number of invalid RACH messages per cause

NMSGDISQ Number of messages discarded from the TCH queue per cell(Fullrate/Halfrate)

NMSUREC Number of Message Signal Units (MSUs) received

NMSUTRAS Number of Message Signal Units (MSUs) transmittedNNNOTNCH Number of new Notifications to be sent on the Notification Channel (NCH)

NPDCHPCU Min, max, mean number of activated PDCHs per BSCNRCLRCMD Number of Clear Command messages per cell per cause per channel

type

NRCLRREQ Number of Clear Request messages per cell per cause per channel typeNRDEFTCH Number of defined TCHs (Fullrate/Halfrate)

NRETPDU Number of retransmitted PDUs (uplink/downlink)

NRFLSDCC Number of lost radio links while using an SDCCHNRFLTCH Number of lost radio links while using a TCH (Fullrate/Halfrate)NRINHDFL Number of inter BSC Handover failures

8/13/2019 KPIs_SBS_BR_7



System

150 A30808-X3247-B912-1-7618

NRLTBFCR Number of lost TBFs due to cell reselection (uplink/downlink) per cellNRUNINHD Number of unsuccessful outgoing inter BSC Handovers per neighbour cell

relationshipNSUCCHPC Successful immediate assignments of signalling channels per cause

NSUGPPAG Number of successful GPRS paging procedures

NSUPRRE Number of successful packet resource reassignment procedure attemptsper cell

NTBFPDC Max, mean number of TBFs allocated per PDCH (uplink/downlink) per cellNTCHSDCM Number of TCH-SDCCH channel modifications

NTDMAGCH Number of transmitted and discarded messages on the AGCH per cell

NTDMPAGC Number of transmitted and discarded messages on the PAGCH per cellNTDMPCH Number of transmitted and discarded Paging messages on the PCH per

cellNTDMPPCH Number of transmitted and discarded Paging messages on the PPCH per

cell

NTRLLCFR Number of transmitted LLC frames (uplink/downlink) per cell on theBSSGP layer GB interface

NUACATCL Number of attempted PDCH assignments (uplink/downlink) per cellNTRAPDU Number of transmitted PDUs (uplink/downlink) per coding scheme per cell

on the RF interfacePWRUPDW Power and quality measurements on uplink/downlink busy TCHs

REJPDASS Number of rejected PDCH assignments (uplink/downlink) per causeREMUTHRF Retransmitted mean user data throughput (uplink/downlink) per coding

scheme per cell on the RF interface

RFDBCUN Routing failure, DPC unavailableRFSUBUN Routing failure, subsystem unavailable

RQIISHDO Number of Requested Incoming Intersystem Handover per BSCSERVUGDG Service upgrade/downgrade measurements (uplink/downlink) per cell

SINHOBSC Successful internal Handovers per causeSININIRH Successful incoming internal intercell Handovers per originating cell

SINTHINT Successful internal Handovers, intercell, per causeSINTHITA Successful internal Handovers, intracell, per cause

SISHINTE Successful Internal SDCCH Handovers IntercellSISHINTR Successful internal SDCCH Handovers Intracell

SLFAILAL Signalling link failureSOINTESH Successful MSC controlled SDCCH Handovers

SOUINIRH Successful outgoing intercell Handovers per cause, per neighbour cellrelationship

SUCPDASA Number of successful PDCH assignments (uplink/downlink) per cell

SUCTCHSE Successful TCH seizures (Fullrate/Halfrate)

SUCTETBF Number of successful terminated TBFs (uplink/downlink) per cellSUIISHDO Number of Successful Incoming Intersystem Handover per BSC

SUIMASCA Successful immediate assignment procedures, per causeSUINBHDO Successful outgoing inter BSC Handovers per neighbour cell relationship

SUINCCRS Successful internal network controlled cell reselections per cellSULACCEL Number of successful PDCH seizures (uplink/downlink) per cell

SUOISHDO Successful Outgoing Intersystem Handover per neighbourcell per causeTACCBPRO Total number of accesses by procedures (PCH, AGCH)

TANRGPRS Number of attempted GPRS accesses per cell with no GPRS radioresources allocated

TASSATT Total number of assignment attempts per cell per channel type

TASSATVS Total number of assignment attempts relevant to VBS/VGCSBroadcast/Group Channels, per cell

TASSFAIL Total number of assignment failures per cell, per cause, per channel type

8/13/2019 KPIs_SBS_BR_7



System

TASSSUCC Total number of successful assignments per cell per channel typeTASSUCVS Total number of successful assignments relevant to VBS/VGCS

Broadcast/Group Channels, per cellTCMSGREC Total number of connectionless messages received

TCMSGSND Total number of connectionless messages sent

TMSGREC Total number of messages receivedTMSHHDL Total number of messages handled

TNMSCNCL Total number of multislot (HSCSD) connections per cellTNSUDHSC Number of service upgrades/downgrades for HSCSD calls

TNTCHCL Total number of TCH connections, per cell (Fullrate/Halfrate)TRANAVTI Transceiver available time

UISHINTE Unsuccessful Internal SDCCH Handovers IntercellUISHINTR Unsuccessful internal SDCCH Handovers Intracell

UNIHIALC Unsuccessful internal Handover, intracell, with loss of MSUNIHIRLC Unsuccessful internal Handovers, intercell, with loss of MS

UNIISHDO Number of Unsuccessful Incoming Intersystem Handover per BSCUNINCCRS Unsuccessful internal network controlled cell reselections per cell per

causeUNINHOIA Unsuccessful internal Handovers, intracellUNINHOIE Unsuccessful internal HOs, intercell, with reconnection to the old channel,

cause, per target cell

UNOISHDO Unsuccessful Outgoing Intersystem Handover per neighbourcell percause

UNSPDCSE Number of degraded PDCH seizures (uplink/downlink) per cell

UNSTETBF Number of unsuccessful terminated TBFs (uplink/downlink) per cell percause

UOINTESH Unsuccessful MSC controlled SDCCH Handovers

Date post:	04-Jun-2018
Category:	Documents
Upload:	hasnatreza-alam
View:	224 times
Download:	2 times