siemens - definicion kpis

Siemens

Information System PM: SBS Key Performance Indicators (optional issue) A30808-X3247-M47-1-7618 Date : 06.10.2005 Release : BR8.0

Information PM: SBS Key Performance Indicators System Contents

1 INTRODUCTION............................................................................................................................................. 5 1.1 Purpose.............................................................................................................................................. 5 1.2 Reference Documents ........................................................................................................................ 5 1.3 Issue History...................................................................................................................................... 5 1.4 Definition of Terms............................................................................................................................ 6

2 IMMEDIATE ASSIGNMENT ANALYSIS............................................................................................................ 9 2.1 Number of Immediate Assignment Attempts .................................................................................... 11 2.2 Number of Immediate Assignment Losses ....................................................................................... 11 2.3 Number of Immediate Assignments by BSC procedure ................................................................... 12 2.4 Number of AGCH Losses................................................................................................................. 13 2.5 Number of Immediate Assignment Commands sent to MS via AGCH............................................. 13 2.6 Number of Immediate Assignments without MS Seizure.................................................................. 14 2.7 Number of successful Immediate Assignments ................................................................................ 14 2.8 Immediate Assignment Loss Rate .................................................................................................... 15 2.9 AGCH Loss Rate.............................................................................................................................. 15 2.10 Immediate Assignment without MS Seizure Rate............................................................................. 16 2.11 Immediate Assignment Success Rate ............................................................................................... 16

3 SSS PROCEDURES ANALYSIS ..................................................................................................................... 17 3.1 Number of successful Immediate Assignments related to Call Setups............................................. 19 3.2 Number of Dropped SDCCH Connections related to Call Setups................................................... 20 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 ANALYSIS............................................................................................................................. 23 4.1 Number of Assignment Attempts ...................................................................................................... 25 4.2 Number of Assignment Failures ...................................................................................................... 26 4.3 Number of successful Assignments .................................................................................................. 27 4.4 Assignment Failure Rate ................................................................................................................. 28 4.5 Assignment Success Rate ................................................................................................................. 29 4.6 Assignment success rate when radio resources available ............................................................... 29

5 CALL SETUP ANALYSIS .............................................................................................................................. 30 5.1 Number of Call Setup Attempts........................................................................................................ 31 5.2 Number of Successful Call Setups ................................................................................................... 31 5.3 Call Setup Success Rate................................................................................................................... 32 5.4 Number of Call Setup Failures ........................................................................................................ 32 5.5 Call Setup Failure Rate ................................................................................................................... 34

6 TCH DROP RELATED PERFORMANCE INDICATORS..................................................................................... 35 6.1 Number of Dropped TCH Connections ........................................................................................... 35 6.2 TCH Drop Distribution ................................................................................................................... 36 6.3 TCH Drop Rate................................................................................................................................ 39 6.4 Call Drop Rate ................................................................................................................................ 40 6.5 Mean Time between TCH Drop....................................................................................................... 42 6.6 TCH Drops per Erlanghour............................................................................................................. 42

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

8 TCH LOAD RELATED PERFORMANCE INDICATORS .................................................................................... 45 8.1 TCH Load for Circuit Switched Traffic ........................................................................................... 45 8.2 Combined time slot utilisation for CS and PO Traffic..................................................................... 54

9 SDCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................... 56 9.1 SDCCH Traffic Offered ................................................................................................................... 56 9.2 SDCCH Traffic Carried................................................................................................................... 57 9.3 SDCCH Traffic Lost ........................................................................................................................ 57 9.4 SDCCH Blocking Rate..................................................................................................................... 57

2 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System

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

10 CCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................ 60 10.1 PCH load of downlink CCCH channels .......................................................................................... 62 10.2 AGCH load of downlink CCCH channels........................................................................................ 62 10.3 CCCH load downlink....................................................................................................................... 63 10.4 CCCH load uplink ........................................................................................................................... 63 10.5 PCH Loss Rate ................................................................................................................................ 64 10.6 AGCH Loss Rate.............................................................................................................................. 64 10.7 Invalid RACH Rate .......................................................................................................................... 65

11 PCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................ 66 11.1 PPCH load of downlink PCCCH channels...................................................................................... 68 11.2 PAGCH load of downlink PCCCH channels................................................................................... 68 11.3 PCCCH load downlink .................................................................................................................... 69 11.4 PCCCH load uplink......................................................................................................................... 69 11.5 PPCH Loss Rate .............................................................................................................................. 70 11.6 PAGCH Loss Rate ........................................................................................................................... 70 11.7 Invalid PRACH Rate........................................................................................................................ 71

12 SERVICE RELATED PERFORMANCE INDICATORS ................................................................................... 72 12.1 Total number of Service Requests.................................................................................................... 72 12.2 Service Request Distribution Rate ................................................................................................... 72 12.3 Rate of Service Requests served in the highest layer ....................................................................... 73

13 FEATURE RELATED PERFORMANCE INDICATORS .................................................................................. 74 13.1 Abis pool supervision....................................................................................................................... 74

14 HANDOVER RELATED PERFORMANCE INDICATORS............................................................................... 76 14.1 Intra Cell Handovers ....................................................................................................................... 76 14.2 Inter Cell Intra BSC Handovers ...................................................................................................... 82 14.3 Inter Cell Inter BSC Handovers ...................................................................................................... 90 14.4 Inter System Handover between GSM and UMTS........................................................................... 96 14.5 Other Handover Performance Indicators...................................................................................... 101

15 POWER AND QUALITY MEASUREMENTS ............................................................................................. 107 15.1 Interference Band Rate on idle TCH ............................................................................................. 107 15.2 Quality Link for N% FER .............................................................................................................. 107 15.3 Mean FER UpLink......................................................................................................................... 107 15.4 Power and Quality limits for N% Percentile on busy TCH ........................................................... 109 15.5 Distribution of power control levels on busy TCH ........................................................................ 110 15.6 Mean Level and Quality on busy TCH........................................................................................... 111 15.7 TA Distribution.............................................................................................................................. 112 15.8 RXQUAL Distribution ................................................................................................................... 112 15.9 RXLEV Distribution....................................................................................................................... 113 15.10 FER Distribution ........................................................................................................................... 113 15.11 Mean FER UpLink per RXQUAL .................................................................................................. 114 15.12 Mean RXLEV per RXQUAL Band ................................................................................................. 115 15.13 Mean RXLEV per TA Band............................................................................................................ 116 15.14 High RXLEV with Low RXQUAL Rate .......................................................................................... 117 15.15 TCH Traffic Type Distribution ...................................................................................................... 118 15.16 SDCCH Traffic Type Distribution ................................................................................................. 119 15.17 Adaptive Multirate Distribution .................................................................................................... 120 15.18 Adaptive Multirate True Frame Erasure Rate............................................................................... 121

16 AVAILABILITY RELATED PERFORMANCE INDICATORS .......... FEHLER! TEXTMARKE NICHT DEFINIERT. 16.1 Transceiver Availability ................................................................................................................ 122 16.2 TCH Distribution Rate................................................................................................................... 122 16.3 TCH Availability............................................................................................................................ 122 16.4 SDCCH Availability ...................................................................................................................... 124

17 GPRS RELATED PERFORMANCE INDICATORS .................................................................................... 125 17.1 User oriented KPIs ........................................................................................................................ 125 17.2 Network planning (dimensioning) ................................................................................................. 140 17.3 Network optimization..................................................................................................................... 152 17.4 Cell Reselection ............................................................................................................................. 156

18 MISCELLANEOUS PERFORMANCE INDICATORS ................................................................................... 160

3 A30808-X3247-B912-1-7618


18.1 BSC Processorload........................................................................................................................ 160 18.2 BTSE Processorload...................................................................................................................... 161 18.3 Paging Response / Location Update Ratio per Cell ...................................................................... 161 18.4 BSC <-> MSC/SMLC CCS7 Load................................................................................................. 162

19 BSS RELATED KPIS AT SIEMENS MSC............................................................................................... 163 20 APPENDIX ........................................................................................................................................... 164

20.1 List of BSS Performance Measurements........................................................................................ 164

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 and for 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 Further information about Performance Measurements can be found in the following documents: • PM:SBS Counters, A30808-X3247-M40-# • PM:SBS Message Flow, A30808-X3247-M41-# • Training Documentation 1736 : BSS Performance Measurement • 3GPP TS52.402 Telecommunication management; Performance Management

(PM); Performance measurements - GSM

1.3 Issue History Issue Version

Date of issue Reason for of issue

BR8.0 AFI0.1 23.6.2005 First version for new release 8.0 BR8.0 AFI0.2 11.8.2005 Second version for new release 8.0

- Modifications related to review comments - New KPIs added in chapter 10 and 13

BR8.0 IUS 1.0 06.10.2005 SDCA KPI’s added, chapter 12

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 name This is an abbreviation of the described key performance indicator. Description The description will give you a short explanation of the described key performance indicator. Formula The formula will deliver the exact calculation of the described key performance indicator. The formula is related to one elementary object and to one elementary period. Multiple objects and multiple elementary periods can be added as described under ‘Evaluation of multiple objects for multiple elementary periods‘. Used parameter Here you can find either the SBS short identification of the used SBS performance measurement counters or the short name of the used key performance indicators. The related long names of SBS performance measurement counters you can find in the appendix under ‘List of Performance Measurements‘. The SBS short identification is a combination of measurement type and sub-counter. A measurement type can have several sub-counters. Therefore the used sub-counters are listed in brackets with 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.

6 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System 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 or none.

- 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 and for 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 in KPI’s formula, collected for the granularity period; it is the aggregation standard1 .

- SPBH (Sample at Peak Busy Hour2) 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 for each 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 of the MAX/min value;

- TCMAX/TCMIN (Time Coherent MAX/min): for a number of days, counter values for each granularity period for each day are recorded. The values for the same granularity period for each day are averaged, determining the average day. The counter value in the granularity period in this average day give the highest value (TCMAX) or the lower value (TCmin) is taken;

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

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

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

7 A30808-X3247-B912-1-7618


- SPBH is the value of the KPI at reference BH and is calculated only in the busy 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): provides the starting time of the hour of TCSPBH;

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

- 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 the counter values for single objects and single periods in the following way (standard aggregation):

∑=t,i

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

i elementary object t elementary period n 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 the granularity period is smaller than 1 hour, this value is calculated with the sliding window algorithm. Not in any case it makes sense to evaluate the busy hour for each single performance indicator. It is also possible to make an assumption, that for Random traffic the busy hour for most different measurement objects will correlate. That means the busy hour is derived from a particular performance indicator and can be used for other performance indicators. E.g. the busy hour could be derived from the performance indicator ‘BSC Processor load‘ and could than be used for all other performance indicators.

8 A30808-X3247-B912-1-7618


2 Immediate Assignment Analysis The KPIs of this section are mainly used for deriving 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 will count the events related to Mobile Stations. The message flow of the Immediate Assignment Procedure 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 an IMM. ASS. REJ. message are not counted)

SUIMASCA [1..6]

[4] IMM. ASS CMD (Abis Interface) (including those IMM. ASS. CMD. messages that contain 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 that contain an IMM. ASS. REJ. message)

NACSUCPR [2]

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

MS BTS BSC CHANNEL REQUEST

[2] SDCCH CONGESTIONS

[1] CHANNEL REQUIREDCHANNEL ACTIV

CHANNEL ACTIV ACK

CHANNEL ACTIV NACK

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

IMM. ASS REJECT [5] DELETE INDICATION

SABM UA

[6] ESTABLISH INDIC.

9 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System The following figure shows you the traffic flow. Fig. 2 Traffic flow: Immediate Assignment Procedure

[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

[5] Imm Ass Command sent to MS via AGCH

[3] Number of Imm Ass. by BSC 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

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 Assignment procedures from MS point of view by counting the number of Channel Required messages.

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

ATIMASCA[1..14] Used param.:

Elem. Object: Cell

Unit: None

Remarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted. In BR 7.0 a note was added in counter ATIMASCA. This fact does not affect the meaning 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 were rejected, because no SDCCH/TCH was available or because of BTS channel activation failures.

(a) rocImmAssBSCp - ImmAssAtt ImmAssLoss = Formula:

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

Elem. Object: Cell

Unit: None

Remarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted. 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.

11 A30808-X3247-B912-1-7618


2.3 Number of Immediate Assignments by BSC procedure

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 of a 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.

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

Used param.: SUIMASCA[1..6]

Elem. Object: Cell

Unit: None

Remarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted.

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 not transmitted Immediate Assignment Command messages over the AGCH on the Air Interface. Reason for AGCH failures are mainly AGCH overload. This formula is related to MS point of view, by meaning each MS related immediate assignment procedure should be stepped once. Therefore events, where no SDCCH/TCH was available or BTS channel activation failured are counted in the formula ‘Number of Immediate Assignment Losses’. => Only Delete Indication messages related to Immediate Assignment Command messages not containing an Immediate Assignment reject messages will rightly be counted.

(a) rocImmAssBSCp * teAGCHLossRa AGCHLoss =Formula:

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

Elem. Object: Cell

Unit: None


2.5 Number of Immediate Assignment Commands sent to 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 MS via AGCH

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

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

Elem. Object: Cell

Unit: None


13 A30808-X3247-B912-1-7618


2.6 Number of Immediate Assignments without MS Seizure

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 without seizure by MS. The main reasons for this behavior are Phantom RACHs, messages not foreseen for the observed cell. Other reasons are not received SABM messages due to air interface problems. This formula will count the difference between Immediate Assignment Command messages sent to the MS and the number of Establishment Indication messages. => not answered Immediate Assignment Commands.

(a) ImmAssSucc - AGCHLoss - rocImmAssBSCp izImmAssNoSe = Formula:

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 channel required messages not foreseen for the observed cell. The Immediate Assignment procedure 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 timer NSLOTST), it can happen that subsequent Immediate Assignment Commands will not receive a positive reply from the MS. Nevertheless from MS point of view the call 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 Assignments from MS point of view. A Immediate Assignment procedure is successful if the BTS returns an establishment indication message on Abis.

(a) 22] .. 17 14, .. 9 6, .. NSUCCHPC[1 ssSuccImmA =Formula:

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

Elem. Object: Cell

Unit: None

Remarks: SMS related counters in NSUCCHPC have not to be considered in the KPI formula, because they are also included in other sub-counters of measurement NSUCCHPC.

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 activation failures.

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 observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted (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 transmitted Immediate Assignment Command messages over the AGCH on the Air Interface. Reason for AGCH failures are mainly AGCH overload. This formula is related to MS point of view, by meaning each MS related immediate assignment procedure should be stepped once. Therefore events, where no SDCCH/TCH was available or BTS channel activation failured are counted in the formula ‘Number of Immediate Assignment Losses’. => Only Delete Indication messages related to Immediate Assignment Command messages not containing an Immediate Assignment reject messages will rightly be considered.

Formula: (a)

]TACCBPRO[2]NACSUCPR[2 - ]TACCBPRO[2 teAGCHLossRa =

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

Elem. Object: Cell

Unit: None


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 foreseen for the observed cell. Other reasons are not received SABM messages due to air interface problems. This formula will count number of not answered Immediate Assignment Command messages related to the Immediate Assignment Command messages sent to the MS.

Formula: (a)

GCHImmAssCmdAizImmAssNoSe izRateImmAssNoSe =

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

Elem. Object: Cell

Unit: None

Remarks: The formula will mainly detect Phantom RACHs. Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure 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 MS point of view. A Immediate Assignment procedure is successful if the BTS returns an establishment indication message.

Formula: (a) mAssNoSeizImmAssAttIm

ImmAssSucc RateImmAssSucc−

=

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

Elem. Object: Cell

Unit: None

Remarks: 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.

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 will count the events related to Mobile Stations. There exists the following SSS Procedures which used during Call Setup related to the parameter setting in the MSC: Identity Check (IMEI), Authentication (IMSI), Ciphering, Call Control: Setup BSC MSC MS BTS

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

[1] ESTABLISH INDICATION (related to Call Setups)

NSUCCHPC[1..4,9..12,17..20] – NSUCCHPC[8]

[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 to calculate 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 SBS performance measurement counter it is possible to calculate the SSS Procedure Success and Failure Rate related to Call Setups.

SABM [1] Establishment Ind.CC

Authentification RequestAuthentification Response

Ciphering Complete

Ciphering Command

CR(Compl Layer3Info)

Identity RequestIdentity Response

Ciphering CommandCiphering Complete

Setup

[2] Assignment Req. Call Proceeding

Assignment Command

17 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System The following figure shows you the traffic flow.

[2]SDCCH Drops [3] SSS Procedure failures

[4] Assignment Attempts

[1]Successful Immediate Assignments

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]

18 A30808-X3247-B912-1-7618


3.1 Number of successful Immediate Assignments related 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 Assignments related to Call Setups. A Immediate Assignment procedure related to a Call Setup is successful if the BTS returns an establishment indication message related to Mobile Originated Calls (MOC), Mobile Terminated Calls (MTC), Emergency Calls or Call Reestablishment.

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

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

Elem. Object: Cell

Unit: None

Remarks: • Partly elimination of systematic error in formula by subtracting the SMS-MT related counter values NSUCCHPC[8] (SDCCH assigned for SMS-MT). The new 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 mainly are triggered where an SMS MT arrives when the MS has an ongoing TCH call. In that case no immediate TCH assignment in connection with the SMS MT 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” is enabled. For that scenario the counters NSUCCHPC [16,24] might also be triggered when an SMT MT arrives for an idle MS, which requests an immediate TCH assignment as paging response. The number of these concurrencies has in principle to be subtracted in formula 3.1. But NSUCCHPC [16,24] does no distinguish between arrival of SMS MT for an idle MS and for an MS with ongoing TCH call (the call processing trigger point used for NSUCCHPC [16,24] has no knowledge about the history of the existing TCH assignment).

19 A30808-X3247-B912-1-7618


3.2 Number of Dropped SDCCH Connections related to Call 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 to Call Setups. SDCCH drops mainly occur during running SSS Procedures. This formula is related to the assumption that the number of dropped SDCCH connections is random distributed to all kind of assignment causes (MOC, MTC, Locupd, …). Therefore this formula contains a factor for the ratio of MOC and MTC to 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:

3.3 Number of SSS Procedure Failures related to Call Setups

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

Short name: (a) SSSProcFailCS

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

Formula: (a) SSDCCHDropC -AssAtt - CSImmAssSucc lCSSSSProcFai =

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

Elem. Object: Cell

Unit: None

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

20 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. SDCCH drops mainly occur during running SSS Procedures. This formula is related to the assumption that the number of dropped SDCCH connections is random distributed to all kind of assignment causes (MOC, MTC, Locupd, …). Therefore this formula is equal to the SDCCH Drop Rate.

(a) ateSDCCHDropRmAssSuccCS

SSDCCHDropC≈=

Im ateCSSDCCHDropR

Formula:

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 Setups

Short name: (a) SSSProcFailRateCS

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

Formula: (a) mAssSuccCSIm

ocFailCSPrSSS 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 are counted in this formula although they are not related to the BSS. User Release before assignment of a TCH is also included in this formula. Assignments of SDCCH are not considered.

21 A30808-X3247-B912-1-7618


3.6 SSS Procedures Success Rate related to Call Setups

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 Call Setups by meaning the rate for successful allocated Timeslots from MSC point of view (Assignment Request Message) minus the SDCCH Drop Rate related to Call Setups. This indicator is related to the Radio Network and is therefore recommended to find out Radio Network failures. The second indicator will give you the SSS Procedures Success Rate related to Call 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 counted within this indicator although they are not related to the BSS.

Formula: (a) ateCSSDCCHDropR - 1 cRateCSSSSProcSuc =

(b) CSImmAssSucc

AssAtt alcRateCStotSSSProcSuc = or

CSocFailRatePrSSSateCSSDCCHDropR1 alcRateCStotSSSProcSuc −−=

Used param.: ImmAssSuccCS (3.1(a)), AssAtt (0(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 to a worse Success Rate although they are not related to the BSS. User Release before assignment of a TCH is also included in the second formula. Assignments of SDCCH are not considered.

22 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 will count the events related to Mobile Stations. The messageflow of the Assignment Procedure is listed below (normal case). The numbers in brackets will indicate available SBS performance measurements.

MS BTS BSC MSC

ASSIGNMENT REQUEST

CHAN ACTIV

ASSIGNMENT COMMAND

CHAN ACTIV ACK

SABM

CHANNEL ACTIV NEG ACK

ASSIGNMENT COMMANDASSIGNMENT FAILURE

ASSIGNMENT COMPLETE

[5] TASSFAIL

UA

ASSIGNMENT COMPLETE

ESTABLISH INDICATION(TNTCHCL)

ASSIGNMENT COMPLETE

[1] TASSATT

[4] TASSSUCC

PHYS CONTEXT REQ

PHYS CONTEXT CONF

(MTCHBUTI)

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]

23 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System The following figure shows you the traffic flow.

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

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 may be 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 Assignment Success Rate is comparable with the Handover Success Rate, where only outgoing Handover will be considered. Therefore all Directed Retries for an observed cell have to 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] T his chapter contains the following ‘Number related’ KPIs: • Number of Assignment Attempts: [1], see chapter 0. • 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)

24 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 the MSC.

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

Used param.: TASSATT[2,3]

Elem. Object: Cell

Unit: None

Remarks: Only TCH assignments are considered. Assignments of SDCCHs are not considered. Only the assignment procedure triggered by the MSC is considered but not the Immediate Assignment procedure. Incoming handovers are also not considered.

25 A30808-X3247-B912-1-7618


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 (e) Total Number of Assignment Failures

Short name: (a) TCHLoss (b) AssFailbyMess (c) AssFailOther (d) QueFail (e) AssFail

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 -AssAtt er AssFailOth =

(d) ,2]NMSGDISQ[1 QueFail =

(e) 2]NRCLRREQ[210..13,15] ..8,TASSFAIL[6 AssFail +=

TASSFAIL [6,7,8,10,11,12,13,15], AssAtt (0(a)) , AssSucc (4.3(a)), NMSGDSIQ[1,2], NRCLRREQ[22]

Used param.:

Elem. Object: Cell

Unit: None

Remarks: • Directed Retries are not considered, because they ares not related to assignment failures

• Assignments of SDCCH are not considered. • Sub-counters TASSFAIL[10] and TASSFAIL[15] ('All other causes') used in

formula (b) includes the A-interface and equipment related causes (see GSM 08.08).

• Queuing failures are completely covered in formula (e). Measurement NMSDISQ[1,2] must not be added. But measurement NRCLRREQ[22] is included in case a queued subscriber is pre-empted before expiry of timer T11.

• Formula (c) AssFailOther contains all other causes related to internal and transmission failures.

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 Assignment procedures. Successful completed Assignment procedures are incremented even with successful outgoing directed retry, because it represents an assignment of TCH for the originating cell.

Formula:

(a) ∑∑==

+++++

=63

0m

31

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

,3]TASSSUCC[2 AssSucc

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

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

Elem. Object: Cell

Unit: None

Remarks: • Assignments of SDCCH are not considered. • Intersystem Directed Retry to UMTS are considered

27 A30808-X3247-B912-1-7618


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 (e) Assignment Failure Rate

Short name: (a) TCHLossRate (b) AssFailbyMessRate (c) AssFailOtherRate (d) QueFailRate (e) AssFailRate

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

Formula: (a) AssAtt

TCHLoss eTCHLossRat =

(b) AssAtt

essAssFailbyM essRateAssFailbyM =

(c) AssAtt

erAssFailOth erRateAssFailOth =

(d) AssAttQueFail eQueFailRat =

(e) AssAttAssFail eAssFailRat =

Used param.: AssAtt(0(a)), TCHLoss (4.2(a)), AssFailbyMess (4.2(b)), AssFailOther (4.2(c)), QueFail (4.2(d)), AssFail (4.2(d)),

Elem. Object: Cell

Unit: None

Remarks: • Directed Retries are not considered, because they ares not related to assignment failures.

• Assignments of SDCCH are not considered

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 Assignment procedure is successful if the BSC returns an Assignment Complete message to the MSC or if the directed retry in the target cell was successful.

Formula: (a) eAssFailRat1or

AssAttAssSucc eAssSuccRat −=

AssAtt(0(a)), AssSucc (4.3(a)), AssFailRate (4.4(e)) Used param.:

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 resources available

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-AssAttessAssFailbyM1kingbNoTCHBlocSuccAssPro −=

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

Elem. Object: Cell

Unit None

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

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 Success Rate and Call Setup Failure Rate are related to the Mobile Station point of view, by meaning they will count the events related to Mobile Stations. Overview Call Setup Analysis CS

(5.3) CSSR

Call Setup Success Rate BSS

(5.5) CSFR

Call 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

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) RateImmAssSuccCSImmAssSucc 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 observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and 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 radio conditions. 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 Failure Rates 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 to end connection. A Call Setup was successful if the MS was able to seize a TCH.

Formula: (a) AssSucc CSSucc =

Used param.: AssSucc (4.3a)

Elem. Object: Cell

Unit: None

Remarks: Assignment of SDCCH are not considered

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 up an end to end connection. Two indicators are available, one that takes into account all Call Setup rejections (BSS immediate assignment, SSS security and TCH assignment), one that only takes into account BSS related Call Setup rejections (BSS immediate assignment and TCH assignment).

Formula: (a) eAssSuccRat * alcRateCStotSSSProcSuc * RateImmAssSucc CSSuccRate =(b)

eAssSuccRat * ateCS)SDCCHDropR - 1 (* RateImmAssSucc BSSCSSuccRate =

ImmAssSuccRate (2.11(a)), SSSProcSuccRateCStotal (3.6(b)), AssSuccRate (4.5(a)), SDCCHDropRateCS (3.4(a))

Used param.:

Elem. Object: Cell

Unit: None

Remarks: BR7: correction CSSuccRateBSS: factor (1-SDCCHDropRateCS) included in formula BR7: KPI CSSuccRateSSS cancelled (just another name for KPI SSSProcSuccRateCStotal (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 MS

Seizure (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

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. Different indicators 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

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 indicators distinguish 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

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 to Mobile Stations. Only drops related to the BSS including the radio interface are considered. But drops detected by the MSC call processing reasons are excluded. (Therefore among others drops arising from the remote BSS and the remote radio interface are not considered)

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

Use case: Observation of customer satisfaction

Used 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 the measurement NRCLRREQ. This avoids double counting of drops during pending HO (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 the perspective of the Mobile Station (customer dissatisfaction) There is a small systematic error in case of expiry of timer T_MSRFPCI during assignment; in that case NRCLRREQ (“Radio interface message failure”) is triggered. 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 that case NRCLRREQ is not triggered

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 TCH drops 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. KPIs for the supervision of transmission power, interference and HO)

36 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Formula:

(a) TCHDrop

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

(b) TCHDrop

11,20,29]NRFLTCH[2, est.UnsolDMRTCHDropDis =

(c) TCHDrop

12,21,30]NRFLTCH[3, t.SeqErrTCHDropDis =

(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, rt.ConnOtheTCHDropDis =

(j) TCHDrop

]UNIHIALC[1 lHOt.IntraCelTCHDropDis =

(k) TCHDrop

]UNIHIRLC[1 lHOt.InterCelTCHDropDis =

(l) TCHDropDropInterBSCHO HOt.InterBSCTCHDropDis =

(m) TCHDrop

,10]NRCLRREQ[1 lt.EquipFaiTCHDropDis =

(n) TCHDrop

,14]NRCLRREQ[5 t.ProtErrTCHDropDis =

(o) TCHDrop

,15]NRCLRREQ[6 t.DistErrTCHDropDis =

(p) TCHDrop

,16]NRCLRREQ[7 t.PreemptTCHDropDis =

(q) TCHDrop

,17]NRCLRREQ[8 t.OAMTCHDropDis =

(r) TCHDrop

,18]NRCLRREQ[9 t.OtherTCHDropDis =

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

Elem. Object: Cell

Unit: None

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

37 A30808-X3247-B912-1-7618


TCHDropDist.InterBSCHO. TCH drops during pending incoming inter BSC handover are not counted in formulas TCHDropDist.HOAccess. This avoids double counting of drops during pending HO (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 the perspective of the Mobile Station (customer dissatisfaction) If the feature SDCCH Handover is activated, then this will lead to a systematic error.

38 A30808-X3247-B912-1-7618


6.3 TCH Drop Rate Long name: (a) TCH Drop Rate

Short name: (a) TCHDropRate

Description: This indicator will give you the rate of all drops of TCH connections. Drops comprise all BSC caused terminations of TCH connection. I.e. connection termination induced by an MSC is not counted as TCH drop within the scope of the present radio network related document. The TCH drops are related to all seizures of a TCH in the observed cell. A TCH may be seized during call setup and additionally for handover (including Directed Retry). Therefore on call in the view of a mobile subscriber may cause the seizure of more than one TCH spread over several cells

Formula: (a)

..2]SUCTCHSE[1TCHDrop eTCHDropRat =

TCHDrop(6.1(a)), SUCTCHSE[1..2] Used param.:

Elem. Object: Cell

Unit: None

Remarks: Please note that there can be systematic errors caused by timer settings (Ny, T3105, TTrau, TSync, T_MSRFPCI, T8). If the feature SDCCH Handover is activated, then this will lead to a systematic error. This KPI is not only related to Call Setups. It is related to any TCH seizure (e.g. incoming Handovers). Therefore for network optimization it is recommended to use KPI ‘TCH Drops per Erlanghour ‘, because increasing number of Handovers (e.g. Ping Pong Handovers) will decrease the TCH Drop Rate.

39 A30808-X3247-B912-1-7618


6.4 Call Drop Rate Long name: (a) Number of terminated calls

(b) Call Drop Rate

Short name: (a) NumTermCalls (b) CallDropRate

Description: This indicator provides the number of terminated calls and the call drop rate from the view of the MS (customer satisfaction). Preconditions:

1. A call is established when the MS has seized the TCH • Ass Failure in connection with a following Clear Command is not

considered as call, since the MS has not yet seized a TCH. (e.g. AssFail: No radio resource available, MSC controlled Directed Retry)

• Queuing timer expiry is not considered • Expiry of timer T_MSRFPCI is not considered

2. Call termination (and especially call drop) is counted for that cell, where the TCH was seized by the MS at the time of the call termination (especially call drop) • Call termination (and especially call drop) during pending HO is

counted for the old cell 3. Only call drops initiated by the BSS are considered

• Drops comprise all BSC caused terminations of calls. I.e. call termination induced by an MSC is not counted as call drop within the scope of the present radio network related document

• Release of TCH in connection with HO reversion to old cell is not considered (e.g.: Inter BSC HO -> HO access failure -> Clear Command). Reason: no TCH drop from the MS perspective.

•

Formula: (a) ..13] 8,11 .. TASSFAIL[6 - ,13]NRCLRREQ[4 -12] .. 10 8, .. 4 2, .. NRCLRCMD[1 lsNumTermCal =

(b) lsNumTermCal

TCHDrop teCallDropRa =

Used param.: TCHDrop(6.1(a)), NRCLRCMD[1 .. 2, 4 .. 8, 10..12], TASSFAIL[6.. 8,11 .. 13], NRCLRREQ[4,13], NumTermCalls(6.4(a))

Elem. Object: Cell

Unit: None

Remarks: Remark for understanding the formula on the number of terminated calls: Clear Commands may also be received by the MSC at call state when the MS has not yet seized the TCH during TCH assignment, i.e. when no call is yet established. Therefore the following cases are not considered as established calls:

• No TCH available after Queuing: In that case the BSC sends Clear Request (“Radio resource not available”) which triggers

40 A30808-X3247-B912-1-7618


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

• Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COMMAND (T10 Expiry): In that case the BSC sends Assignment Failure to 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 the MSC and triggers TASSFAIL[7,12]; this also leads to triggering of NRCLRCMD[2,8] (“Call Control”)

• No TCH available (no queuing): In that case the BSC sends Assignment Failure to the MSC and triggers TASSFAIL[8,13]; this also leads to triggering 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 sends Clear Command (“equipment failure”) the target BSC which triggers NRCLRCMD[4] for the target cell -> this effect slightly improve the CallDropRate by pretending that more call 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 triggers NRCLRCMD[2] -> this effect slightly improve the CallDropRate by pretending that more call have existed than in reality.

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

• There can be systematic errors caused by timer settings (Ny1, T3105, TTrau, TSync, T_MSRFPCI, T8). If the feature SDCCH Handover is activated, then this will lead to a systematic error. -> this effect slightly deteriorates the call drop rate (numerator and denominator are increased)

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

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 in seconds until the occurrence of the loss of a TCH connection.

Formula: (a) TCHDrop

60s *y Granularit* rDRTCHTrafCar 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 number of losses of TCH connections related to one Erlanghour.

Formula: (a) yGranularit

60*rDRTCHTrafCar

TCHDrop hTCHDropErl =

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

Elem. Object: Cell

Unit: None

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

42 A30808-X3247-B912-1-7618


7 SDCCH Drop related Performance Indicators

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 can occur for any call type (MOC, MTC, Locupd, SMS, ...).

Formula: (a) ,6,11]TASSFAIL[1 26] .. 23 21, .. 9NRCLRREQ[1 SDCCHDrop +=

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

Elem. Object: Cell

Unit: None

Remarks: This KPI is based on NRCLRREQ counters, because drops caused by the BSC must be considered.

7.2 SDCCH Drop Rate Long name: (a) SDCCH Drop Rate

(b) SDCCH Drop Rate per SDCCH connection

Short name: (a) SDCCHDropRate (b) SDCCHDropConnRate

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

Formula: (a)

..6]NSUCCHPC[1SDCCHDrop ateSDCCHDropR =

(b) 8]3,14,16..1NRCLRCMD[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 small systematic errors.

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 the time in seconds until the occurrence of the loss of a SDCCH connection.

Formula: (a) SDCCHDrop

60s *y Granularit*arr SDCCHTrafC opMTBSDCCHDr =

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

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 the number of losses of SDCCH connections related to one Erlang.

Formula: (a) yGranularut

60*arrSDCCHTrafC

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.

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 performance indicators used in the traffic theory.

Traffic Offered A [Erl] Call Attempts CA

Number of channels N

Traffic Lost R [Erl] Calls Rejected CR Loss B [%]

Traffic Carried Y [ErCalls Carried CC

Fig. 7 Overview Load related performance indicators For the estimation of the Load of GSM Telecom Systems the Erlang B formula for non 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 TCH compared to the total traffic.

Formula: (a)

[1..4] MEBUSTCH3] [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 needed

45 A30808-X3247-B912-1-7618


TRX.

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 (g) TCH seizure blocked Rate

Short name: (a) TCHSeizBlckRateFR (b) TCHSeizBlckRateHR (c) TCHSeizBlckRateDR (d) TCHSeizBlckRateWSFR (e) TCHSeizBlckRateWSHR (f) TCHSeizBlckRateWSDR (g) TCHSeizBlckRate

Description: This indicator will give you the TCH seizure blocked rate by meaning the rate where 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 might become successful by assigning a TCH in another cell through (e.g. by applying the 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 consider only the TCH Seizure attempts discarded from the TCH queue.

Formula: (a)

[1] ATTCHSEI3] [1, ATCHSMBS kRateFRTCHSeizBlc =

(b) [2] ATTCHSEI

4] [2, ATCHSMBS kRateHRTCHSeizBlc =

(c) [1,2] ATTCHSEI

4] .. [1 ATCHSMBS kRateDRTCHSeizBlc =

(d) [1] ATTCHSEI

3] [1, NMSGDISQ kRateWSFRTCHSeizBlc =

(e) [2] ATTCHSEI[2,4] NMSGDISQ kRateWSHRTCHSeizBlc =

(f) [1..2] ATTCHSEI[1..4] NMSGDISQ kRateWSDRTCHSeizBlc =

(g) [1..2] ATTCHSEI

[1..4] NMSGDISQ ..4]ATCHSMBS[1 kRateTCHSeizBlc +=

46 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Used param.: ATCHSMBS[1..4], ATTCHSEI[1..2], NMSGDISQ[1..4]

Elem. Object: Cell

Unit: Subscriber redial behaviour influences the blocking rate. Further the HO periodicity timer influences the TCH blocking rate

Remarks: For Dual Rate Channels (formula c) the Full Rate and Half Rate channels must be weighted with the TCH Traffic distribution Rate. Please note, after expiry of Timer THORQST an intercell or intracell handover will be 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 affect the 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 Rate

Short name: (a) TCHTrafOffFR (b) TCHTrafOffHR (c) TCHTrafOffDR

Description: This indicator will give you the theoretical amount of traffic in Erlang which was offered to a cell. The indicators comprise the traffic explicitly induced by mobile subscribers and also additional virtual traffic emerged from radio network internal features like Directed retry and Handover. In the course of the performance of these two features 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 should not be used isolated since they pretend a higher demand of TCH resources as needed in reality for mobile subscriber satisfaction. The indicators should rather be used in connection with subscriber satisfaction oriented indicators (e.g. refer to chapter 5.5 (g): Call Setup Failure Rate due to TCH Loss)

Formula: (a)

eFRTCHLossRat-13] [1, MEBUSTCH FRTCHTrafOff =

(b) eHRTCHLossRat-1

4] [2, MEBUSTCH HRTCHTrafOff =

(c) HRTCHTrafOffFRTCHTrafOff DRTCHTrafOff +=

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

Elem. Object: Cell

Unit: Erlang

Remarks: None

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, MEBUSTCH rFRTCHTrafCar =

(b) 4] [2, MEBUSTCH rHRTCHTrafCar =

(c) rHRTCHTrafCarrFRTCHTrafCar rDRTCHTrafCar +=

Used param.: MEBUSTCH[1..4]

Elem. Object: Cell

Unit: Erlang

Remarks: None

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 in Erlang), 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 for example during HO execution a certain target cell candidate is fully occupied this situation is counted as lost traffic for that target cell; but from the perspective of the 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 lost due to discard from the TCH waiting queue.

Formula: (a) rFRTCHTrafCar - FRTCHTrafOff tFRTCHTrafLos =(b) rHRTCHTrafCar - HRTCHTrafOff tHRTCHTrafLos = (c) rDRTCHTrafCar - DRTCHTrafOff tDRTCHTrafLos =

(d) 60s *y Granularit

TCHMHTFR* 3],NMSGDISQ[1 tWSFRTCHTrafLos =

(e) ,4]NMSGDISQ[2 tWSHRTCHTrafLos =60s *y Granularit

TCHMHTHR*

(f) ..4]NMSGDISQ[1 tWSDRTCHTrafLos =60s *y Granularit

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: None

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 Rate

Short name: (a) TCHBlockRateFR (b) TCHBlockRateHR (c) TCHBlockRateDR

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

Formula: (a)

60s *y Granularit]AALTCHTI[1 teFRTCHBlockRa =

(b) 60s *y Granularit]AALTCHTI[4 teHRTCHBlockRa =

(c) HRT* teHRTCHBlockRaFRT * teFRTCHBlockRa teDRTCHBlockRa +=

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 must be weighted with the TCH Traffic distribution Rate. Due to feature ‘Smooth Channel Modification’ the measurement type AALTCHTI keeps track of the number of timeslots belonging to the TCH_Pool, TCH/SD_Pool and SDCCH_Backup Pool.

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 TCHs in a cell.

Formula: (a) 3] [1, TNTCHCL

60 *y Granularit * ,3]MEBUSTCH[1 TCHMHTFR =

(b) 4] [2, TNTCHCL

60 *y Granularit * ,4]MEBUSTCH[2 TCHMHTHR =

(c) [1..4] TNTCHCL

60 *y Granularit * ..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, because Erlang values are used.

51 A30808-X3247-B912-1-7618


8.1.8 TCH Traffic Utilization Long name: TCH Traffic Utilisation Full Rate

TCH Traffic Utilisation Half Rate TCH Traffic Utilisation Dual Rate TCH Traffic Utilisation Full Rate based on Erlang TCH Traffic Utilisation Half Rate based on Erlang TCH Traffic Utilisation Dual Rate based on Erlang

Short name: TCHTrafUtilFR TCHTrafUtilHR TCHTrafUtilDR TCHTrafUtilFRErl TCHTrafUtilHRErl TCHTrafUtilDRErl

Description: This indicator will give you the TCH Traffic Utilization Rate by meaning of the carried traffic divided through number of defined TCH. Formula d), e) and f) is based on the Erlang function.

Formula:

,8]NRDEFTCH[2,3]MEBUSTCH[1 lFRTCHTrafUti =

,11]NRDEFTCH[5,4]MEBUSTCH[2 lFRTCHTrafUti =

,5,8,11]NRDEFTCH[2..4]MEBUSTCH[1 lFRTCHTrafUti =

A,3]MEBUSTCH[1 lFRErlTCHTrafUti =

Erlang B formula:

Erlang C formula:

B) [2,8],f(NRDEFTCH B)f(N, A ==

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

A,4]MEBUSTCH[2 lHRErlTCHTrafUti =

Erlang B formula:

Erlang C formula

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

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

A..4]MEBUSTCH[1 lDRErlTCHTrafUti =

Erlang B formula:

Erlang C formula:

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

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

with A = Offered Load in Erlang

52 A30808-X3247-B912-1-7618


B = 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. A weighting with the TCH Traffic distribution Rate is not necessary here, because Erlang values are used.

53 A30808-X3247-B912-1-7618


8.2 Combined time slot utilisation 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, which can 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 are under control of radio resource management (TCH, SDCCH, PDTCH); i.e. the timeslot consumption for common control channels and broadcast control channels is not considered.

Formula: (a) MeaOcTsC =

]/8NDESDCCH[3 ]NDFTCHSD[1 2/,12]NRDEFTCH[6,9]NRDEFTCH[3 ]NDEFPDCH[3[1]/8 MBUSYSDC [2,4]/2 MEBUSTCH[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 PBCCH and PCCCH; but NALLPDCH does not contain these channels. This leads to a systematic error. Improvement by BR8 FRS 86899:

54 A30808-X3247-B912-1-7618


8.2.2 Combined time slot availability 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 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 are under control of radio resource management (TCH, SDCCH, PDTCH); i.e. the timeslot consumption for common control channels and broadcast control channels is not considered.

Formula: (b) MeaAvTsC =

]/8NDESDCCH[3 ]NDFTCHSD[1 2/,12]NRDEFTCH[6,9]NRDEFTCH[3 ]NDEFPDCH[3]/8NAVSDCCH[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

55 A30808-X3247-B912-1-7618


9 SDCCH Load related Performance Indicators

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

Number of channels N

Traffic Carried Y [Eel] Calls Carried CC

Traffic Lost [Erl] Calls Rejected CR Loss B

Traffic Offered A [Erl] Call Attempts CA

Fig. 8 Overview Load related performance indicators For the estimation of the Load of GSM Telecom Systems the Erlang B formula can be used. Further information about the traffic theory you can find in the ‘Siemens Tabellenbuch Fernsprechtheorie ISBN 3-8009-1343-7’.

9.1 SDCCH Traffic Offered Long 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 MS subscribers wanted to have due to the traffic theorie.

Formula: (a)

ateSDCCHLossR-1[1] MBUSYSDC ffSDCCHTrafO =

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

Elem. Object: Cell

Unit: Erlang

Remarks: None

56 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.

(a) [1] MBUSYSDC arr SDCCHTrafC = Formula:

Used param.: MBUSYSDC[1]

Elem. Object: Cell

Unit: Erlang

Remarks: None

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 were lost (e.g. Blockings).

(a) arrSDCCHTrafC - ffSDCCHTrafO ost SDCCHTrafL = Formula:

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 where all SDCCH were occupied.

Formula: (a)

60s *y Granularit[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 ASDCALTI keeps track of the number of timeslots belonging to the SDCCH_Pool and SDCCH_Backup_Pool and TCH/SD_Pool.

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 rate where new SDCCH Seizure Attempts could not be handled, because all SDCCH were 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 occupied SDCCH in a cell.

(a) ..6]NSUCCHPC[1

60s *y Granularit * [1] MBUSYSDC SDCCHMHT = Formula:

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

Elem. Object: Cell

Unit: Seconds

Remarks: None

58 A30808-X3247-B912-1-7618


9.7 SDCCH Traffic Utilisation Long name: SDCCH Traffic Utilisation

SDCCH Traffic Utilisation based on Erlang formula

Short name: SDCCHTrafUtil SDCCHTrafUtilErl

Description: This indicator will give you the SDCCH Traffic Utilisation by meaning of the carried traffic divided through the number of available SDCCH. Formula b) is based on the Erlang B function.

Formula: (a)

]NDESDCCH[2]MBUSYSDC[1 tilSDCCHTrafU =

(b) A

]MBUSYSDC[1 tilErlSDCCHTrafU =

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

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

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

Elem. Object: Cell

Unit: None

Remarks: None

59 A30808-X3247-B912-1-7618


10 CCCH Load related Performance Indicators The common control channels CCCH consist of a set of logical channels, which are used for common control signaling to start a connection setup:

CCCH Common Control Channels

RACHRandom Access Channel

NCHNotification Channel

PCHPaging Channel

AGCHAccess Grant Channel

UL

DL

MS requests a dedicated channel from network

paging of MSs in a voice group call area

paging of a MS in a location area (MTC)

answer to RACH, dedicated signaling channel allocation

Fig. 9 Overview Common Control Channels The SBS supports several channel combinations resulting in different capacities for the CCCHs. Although a certain channel combination can serve the expected RACH traffic load, another channel combination may be necessary. The RACH is only the uplink part of the CCCH. The downlink parts (AGCH, PCH) may need a higher capacity. Therefore, the configuration of CCCH is determined by the capacity needed for the downlink channels. The RACH configuration is not critical. The PCH and the AGCH share the same TDMA frame mapping (modulo 51) when combined onto a basic physical radio channel. PCH channels may be used as AGCH channels but not vice versa. However, to ensure a mobile a satisfactory access to the system, there is a control parameter (NBLKACGR) to define a fixed number of AGCH blocks in the 51 multiframe (a block consists of 4 consecutive TDMA frames). This number reduces the number of available paging blocks. In all cells where the advanced speech call item (ASCI) service is enabled, a notification channel (NCH) is defined. A parameter (NOCHBLKN) indicates the number of CCCH blocks to be used for the NCH channel. This logical channel is mapped onto contiguous blocks reserved for AGCHs, i.e. if this NCH is used, it takes capacity from the blocks reserved for AGCH channels. For the number of available CCCH frames, the following is defined: If for example a radio timeslot is configured as MBCCHC (main BCCH combined), then the allocated channel combination looks like this:

MBCCHC FCCH + SCH + BCCH + CCCH + 4 (SDCCH + SACCH) The timeslot will then run in the 51-Multiframe organization:

60 A30808-X3247-B912-1-7618


61 A30808-X3247-B912-1-7618

S11

S1

F10

F0

BCCH 2 3 4 5

CCCH 6 7 8 9

CCCH12 13 14 15

CCCH16 17 18 19

S21

S31

F30

F20

SDCCH022 23 24 25

SDCCH126 27 28 29

SDCCH232 33 34 35

SDCCH336 37 38 39

S41

I50

F40

SACCH042 43 44 45

SACCH146 47 48 49

1.

1.S11

S1

F10

F0

BCCH 2 3 4 5

CCCH 6 7 8 9

CCCH12 13 14 15

CCCH16 17 18 19

S21

S31

F30

F20

SDCCH022 23 24 25

SDCCH126 27 28 29

SDCCH232 33 34 35

SDCCH336 37 38 39

S41

I50

F40

SACCH242 43 44 45

SACCH346 47 48 492.

‘uplink’ R = RACH + SDCCH / 4

‘downlink’ BCCH + CCCH + 4 SDCCH / 4, F = FCCH, S = SCH

R5

R4

SDCCH30 1 2 3

SACCH26 7 8 9

SACCH310 11 1213

R15

R14

R17

R16

R19

R18

R21

R20

R23

R22

R25

R24

R27

R26

R29

R28

R31

R30

R33

R32

R36

R35

R34

SDCCH037 38 39 40

SDCCH141 42 43 44

R46

R45

SDCCH247 48 49 50

2. R5

R4

SDCCH30 1 2 3

SACCH06 7 8 9

SACCH110 11 1213

R15

R14

R17

R16

R19

R18

R21

R20

R23

R22

R25

R24

R27

R26

R29

R28

R31

R30

R33

R32

R36

R35

R34

SDCCH037 38 39 40

SDCCH141 42 43 44

R46

R45

SDCCH247 48 49 50

Fig. 10 Structure for an exemplary common control channel combination In the downlink direction, for this example, there are 12 frames available for CCCH, which can be used as PCH, NCH, AGCH frames. But with the parameter NBLKACGR (number of blocks reserved for AGCH) some blocks can be inhibited for paging. A CCCH block consists of 4 consecutive TDMA frames (see above figure). In the uplink direction, for this example, there are 27 frames available for CCCH, which can be used as RACH frames. Note: The NCH channel is not considered, since Notification messages are used only by a very limited number of customers. Additionally, the portion of NCH channels is fixed by configuration and does not depend on any traffic load situations. Therefore, for dimensioning of the required downlink capacity of CCCH channels, only the load of the AGCH and PCH is important. If NCH channels are configured but not used (accessed), this capacity is available for AGCH channels.


10.1 PCH load of downlink CCCH channels Long name: PCH load of downlink CCCH channels

Short name: CCCHLDPCH This indicator will give you the PCH load of downlink CCCH channels, by meaning the number of accessed PCH frames over the air interface in relation to the number of defined CCCH frames downlink.

Description:

Formula:

downlink frames CCCH defined all ofNumber

downlink frames PCH accessed ofNumber CCCHLDPCH =

]NDEFCCCH[2

NTDMPCH[5]CCCHLDPCH =

Used param.: NTDMPCH[5], NDEFCCCH[2]

Elem. Object: Cell

Unit: None

Remarks: None

10.2 AGCH load of downlink CCCH channels Long name: AGCH load of downlink CCCH channels

Short name: CCCHLDAGCH This indicator will give you the AGCH load of downlink CCCH channels, by meaning the number of accessed AGCH frames over the air interface in relation to the number of defined CCCH frames downlink.

Description:

Formula:


downlink frames AGCH accessed ofNumber CCCHLDAGCH=

]NDEFCCCH[2

,2]NTDMAGCH[1CCCHLDAGCH=

Used param.: NTDMAGCH[1,2], NDEFCCCH[2]

Elem. Object: Cell

Unit: None

Remarks: None

62 A30808-X3247-B912-1-7618


10.3 CCCH load downlink Long name: CCCH load downlink

Short name: CCCHLDDL This indicator will give you the CCCH load downlink, by meaning the number of accessed frames (PCH, AGCH) over the air interface in relation to the number of defined CCCH frames downlink.

Description:

Formula:


downlink frames CCCH accessed ofNumber CCCHLDDL =

]NDEFCCCH[2

,2]NTDMAGCH[1 NTDMPCH[5]CCCHLDDL

+=

Used param.: NTDMPCH[5], NTDMAGCH[1,2], NDEFCCCH[2]

Elem. Object: Cell

Unit: None The NCH channel is not considered, since Notification messages are used only by a very limited number of customers. Additionally, the portion of NCH channels is fixed by configuration and does not depend on any traffic load situations. Therefore, for dimensioning of the required downlink capacity of CCCH channels, only the load of the AGCH and PCH is important. If NCH channels are configured but not used (accessed), this capacity is available for AGCH channels.

Remarks:

10.4 CCCH load uplink Long name: CCCH load uplink

Short name: CCCHLDUL This indicator will give you the CCCH load uplink, by meaning the number of received (RACH) over the air interface in relation to the number of defined CCCH frames uplink.

Description:

Formula:

uplink frames CCCH defined all ofNumber

uplink frames RACH received ofNumber CCCHLDUL =

]NDEFCCCH[1

,2,3]NINVRACH[1 ]NACSUCPR[3CCCHLDUL

+=

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

Elem. Object: Cell

Unit: None

Remarks: None

63 A30808-X3247-B912-1-7618


10.5 PCH Loss Rate Long name: PCH Loss Rate

Short name: PCHLossRate

Description: This indicator will give you the PCH Loss Rate by meaning the number of discarded subscriber pagings from the PCH queue related to the total number of subscriber pagings for transmission at the BTS. Each paging queue place in the BTS can be seized by one PAGING REQUEST message, which itself can contain the mobile subscriber identities (IMSI or TMSI) of up to 4 mobile subscribers simultaneously. This means that the PAGING REQUEST message can contain the mobile subscriber identities from up to 4 PAGING commands that were received from the BSC before. Whereas a discarded paging is always represented by one PAGING command message, that includes one TMSI or IMSI, which could not be placed in any BTS paging queue and therefore had to be discarded.

Formula: ]4..1[NTDMPCH

4]NTDMPCH[3,ePCHLossRat =

Used param.: NTDMPCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: None

10.6 AGCH Loss Rate Long name: AGCH Loss Rate

Short name: AGCHLossRate This indicator will give you the AGCH Loss Rate by meaning the number of discarded messages from the AGCH queue related to the total number of messages for transmission over the AGCH at the BTS.

Description:

Formula: ]4..1[NTDMAGCH

,4]NTDMAGCH[3teAGCHLossRa =

Used param.: NTDMAGCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: None

64 A30808-X3247-B912-1-7618


10.7 Invalid RACH Rate Long name: Invalid RACH Rate

Short name: InvRACHRate This indicator will give you the invalid RACH Rate by meaning the number of messages received on the RACH, which did not result in a CHANNEL REQUIRED message toward the BSC (e.g. Signal level too week) and therefore did not result in an SDCCH assignment attempt.

Description:

Formula: ]3[NACSUCPR]3..1[NINVRACH

..3]NINVRACH[1eInvRACHRat

+=

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

Elem. Object: Cell

Unit: None

Remarks: It has to be considered that the NINVRACH does not represent the total amount of all RACH signals that are discarded by the BTS! The Um layer 1 SW subsystem of the BTS continuously observes the signals received on the RACH slots. As even without any real MS RACH access there are always at least some ‘noise’ signals on the RACH, the task of the BTS layer 1 SW subsystem is to evaluate the received signal with respect to specific criteria that classify a signal as 'noisy' or 'not noisy'. These checks are performed prior to the evaluation of the criteria 'excessive distance', 'signal level too weak' and 'CRC checksum error'. Signals classified as 'noisy' are immediately discarded and are not counted by NINVRACH (!). An increase of the NINVRACH counts and thus an increase of the ‘Invalid RACH Rate’ as calculated by the above formula does not mean a worse performance of the BTS. Instead, variations of the NINVRACH counts and variations of the 'Invalid RACH Rate' between the different sites mainly depend on the radio environment conditions, i.e. increased values of NINVRACH and this KPI are no indication for a poor system performance. Moreover, both figures depend on characteristics of the used TRX HW (old HW usually shows lower counter values, although the performance of the newer HW is better!). For this reason the above formula cannot be regarded as a ‘System Performance Indicator’ but rather provides, taking into account which TRX HW is used, a rough idea about the radio conditions that influence the RACH performance! For further details please refer to the NINVRACH counter description in the document 'PM:SBS Counter'.

65 A30808-X3247-B912-1-7618


11 PCCH Load related Performance Indicators The packet common control channels PCCCH consist of a set of logical channels, which are used for common control signaling to start a GPRS-connection setup:

PCCCH Packet Common Control Channels

PRACHPacket Random Access Channel

PNCHPacket Notification Channel

PPCHPacket Paging Channel

PAGCHPacket Access Grant Channel

UL

DL

GPRS-MS access request for UL packet data transmission

notification for GPRS-MSs for PtM transaction

paging of a GPRS-MS in a location area (MTC)

answer to PRACH, dedicated signaling channel allocation

Fig. 11 Overview Packet Common Control Channels The SBS supports several channel combinations resulting in different utilization for the PCCCHs. The PRACH is the uplink part of the PCCCH. The downlink parts (PAGCH, PPCH) may need a different capacity. For packet oriented (PO) services the configuration of PCCCH is independent for uplink and downlink channels. The PRACH configuration is uncritical. The PPCH, PNCH and the PAGCH share the same TDMA frame mapping (modulo 52) when combined onto a basic physical radio channel. The message header distinguishes them. Blocks available for PPCHs may be used as PAGCHs, PNCHs but not vice versa. However, to ensure a mobile a satisfactory access to the system, there is a control parameter to define a fixed number of PAGCH blocks in the 52 multiframe. This number reduces the number of available paging blocks. A packet notification channel (PNCH), belonging to PCCCHs, is defined for notifying a group of MSs of an upcoming Point-to-Multipoint (PtM) transaction. This logical channel is mapped onto contiguous blocks, which can also be used for PPCHs. In contrast to the circuit switched (CS) services, for packet oriented (PO) services the free (not accessed) blocks of the PCCCHs can be used also as packet data traffic channels (PDTCHs). This is because PCCCH, PDTCH and PACCH can be operated in frame stealing mode on the same PDCH. For the number of defined PCCCH frames, the following is defined:

66 A30808-X3247-B912-1-7618


67 A30808-X3247-B912-1-7618

0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 501 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51

Block 1Block 0 Block 2 Block 3 Block 4 Block 5 Block 6 Block 7 Block 8 Block 9 Block 10 Block 11T

A

T

AI I

Timing Advance control frameTASearch frame for measurementsI

BSPBBLK = 2(PBCCH blocks)

BPAGCHR = 3 (no paging on these blocks)

Available Paging Blocks

PDCH with the 52-Multiframe Structure

Example for a PCCCH Configuration

0 1 2 3 4 5 6 7 8 9 10 11

Fig. 12 Structure for an exemplary packet common control channel combination The number of all defined PCCCH channels is dependent on the channel configuration defined by the parameter GDCH (GPRSDedicatedChannel). It can have the values PCCCH and PBCCH. If PCCCH is selected, then 12 blocks are available for PCCCH (see above figure). A block consists of 4 consecutive TDMA frames. If PBCCH is selected, then additionally the parameter BSPBBLK (number of blocks allocated for PBCCH) is relevant, because it reduces the number of available PCCCH blocks by the number of blocks reserved for PBCCH (see above figure). In downlink direction all defined PCCCH blocks can be used as PAGCH, PPCH, PNCH, PDTCH, PACCH. But with the parameter BPAGCHR (number of blocks reserved for PAGCH, PDTCH, PACCH) some blocks can be inhibited for paging. In uplink direction all defined PCCCH blocks can be used as PRACH, PDTCH, PACCH. But with the parameter BPRACHR (number of blocks reserved for the PRACH channel) the number of blocks being used for PRACH can be restricted. Note: The following channels are not considered: PNCH, since the Packet Notification message is currently not supported by the call processing SW. PDTCH, PACCH, since these channels are mapped onto PCCCH channels (uplink/downlink) only, if there is spare capacity, i.e. in case of PCCCH channels being not fully loaded with common control channels. Therefore, for dimensioning of the required capacity of PCCCH channels, only the load of the PAGCH and PPCH (downlink) and PRACH (uplink) is important.


11.1 PPCH load of downlink PCCCH channels Long name: PPCH load of downlink PCCCH channels

Short name: PCCCHLDPPCH This indicator will give you the PPCH load of downlink PCCCH channels, by meaning the number of accessed PPCH frames over the air interface in relation to the number of defined PCCCH frames downlink.

Description:

Formula:

downlink frames PCCCH defined all ofNumber

downlink frames PPCH accessed ofNumber HPCCCHLDPPC =

]NDEFPCCC[2

,2]NTDMPPCH[1HPCCCHLDPPC =

Used param.: NTDMPPCH[1,2], NDEFPCCC[2]

Elem. Object: Cell

Unit: None

Remarks: None

11.2 PAGCH load of downlink PCCCH channels Long name: PAGCH load of downlink PCCCH channels

Short name: PCCCHLDPAGCH This indicator will give you the PAGCH load of downlink PCCCH channels, by meaning the number of accessed PAGCH frames over the air interface in relation to the number of defined PCCCH frames downlink.

Description:

Formula:


downlink frames PAGCH accessed ofNumber CHPCCCHLDPAG =

]NDEFPCCC[2

,2]NTDMPAGC[1CHPCCCHLDPAG =

Used param.: NTDMPAGC[1,2], NDEFPCCC[2]

Elem. Object: Cell

Unit: None

Remarks: None

68 A30808-X3247-B912-1-7618


11.3 PCCCH load downlink Long name: PCCCH load downlink

Short name: PCCCHLDDL This indicator will give you the PCCCH load downlink, by meaning the number of accessed frames (PPCH, PAGCH) over the air interface in relation to the number of defined PCCCH frames downlink.

Description:

Formula:


downlink frames PCCCH accessed ofNumber PCCCHLDDL =

]NDEFPCCC[2

,2]NTDMPAGC[1 ,2]NTDMPPCH[1PCCCHLDDL

+=

Used param.: NTDMPPCH[1,2], NTDMPAGC[1,2], NDEFPCCC[2]

Elem. Object: Cell

Unit: None

Remarks: The following channels are not considered: PNCH, since the Packet Notification message is currently not supported by the call processing SW. PDTCH, PACCH, since these channels are mapped onto PCCCH channels (uplink/downlink) only, if there is spare capacity, i.e. in case of PCCCH channels being not fully loaded with common control channels.

Only the load of the PAGCH and PPCH is important

11.4 PCCCH load uplink Long name: PCCCH load uplink

Short name: PCCCHLDUL This indicator will give you the PCCCH load uplink, by meaning the number of received (PRACH) over the air interface in relation to the number of defined PCCCH frames uplink.

Description:

Formula:

uplink frames PCCCH defined all ofNumber

uplink frames PRACH received ofNumber PCCCHLDUL =

]NDEFPCCC[1

]NSAPRACH[1PCCCHLDUL =

Used param.: NSAPRACH[1], NDEFPCCC[1]

Elem. Object: Cell

Unit: None

Remarks: The following channels are not considered: PDTCH since these channels are mapped onto PCCCH channels (uplink/downlink) only, if there is spare capacity, i.e. in case of PCCCH channels being not fully loaded with common control channels.

Only the load of the PRACH is important.

69 A30808-X3247-B912-1-7618


11.5 PPCH Loss Rate Long name: PPCH Loss Rate

Short name: PPCHLossRate

Description: This indicator will give you the PPCH Loss Rate by meaning the number of discarded subscriber pagings from the PPCH queue related to the total number of subscriber pagings for transmission at the BSC. Each Packet Paging Request message contains one or more mobile subscriber identities (IMSI or TMSI), by meaning the number of discarded paging messages correspond to the minimum number of discarded subscriber pagings.

Formula: ]4..1[NTDMPPCH

,4]NTDMPPCH[3tePPCHLossRa =

Used param.: NTDMPPCH[1..4]

Elem. Object: Cell

Unit: None

Remarks: None

11.6 PAGCH Loss Rate Long name: PAGCH Loss Rate

Short name: PAGCHLossRate This indicator will give you the PAGCH Loss Rate by meaning the number of discarded messages from the PAGCH queue related to the total number of messages for transmission over the PAGCH at the BTS.

Description:

Formula: ]2..1[NTDMPAGC

]NTDMPAGC[2atePAGCHLossR =

Used param.: NTDMPAGC[1..2]

Elem. Object: Cell

Unit: None

Remarks: None

70 A30808-X3247-B912-1-7618


11.7 Invalid PRACH Rate Long name: Invalid PRACH Rate

Short name: InvPRACHRate This indicator will give you the invalid PRACH Rate by meaning the number of messages received on the PRACH, which did not result in a Packet CHANNEL REQUIRED message toward the BSC (e.g. Signal level too week) and therefore did not result in an assignment of a TBF.

Description:

Formula: (a)

..4]NSAPRACH[1]4..2[teInvPRACHRa NSAPRACH

=

Used param.: NSAPRACH[1..4]

Elem. Object: Cell

Unit: None

Remarks: This formula will be valid starting with late BR8.0, due to a correction for measurement type NINVPRACH and NSAPRACH. For the second It has to be considered that the NSAPRACH does not represent the total amount of all PRACH signals that are discarded by the BTS! The Um layer 1 SW subsystem of the BTS continuously observes the signals received on the PRACH slots. As even without any real MS PRACH access there are always at least some ‘noise’ signals on the PRACH, the task of the BTS layer 1 SW subsystem is to evaluate the received signal with respect to specific criteria that classify a signal as 'noisy' or 'not noisy'. These checks are performed prior to the evaluation of the criteria 'excessive distance', 'signal level too weak' and 'CRC checksum error'. Signals classified as 'noisy' are immediately discarded and are not counted by NSAPRACH (!). An increase of the NSAPRACH counts and thus an increase of the ‘Invalid PRACH Rate’ as calculated by the above formula does not mean a worse performance of the BTS. Instead, variations of the NSAPRACH counts and variations of the 'Invalid PRACH Rate' between the different sites mainly depend on the radio environment conditions, i.e. increased values of NSAPRACH and this KPI are no indication for a poor system performance. Moreover, both figures depend on characteristics of the used TRX HW (old HW usually shows lower counter values, although the performance of the newer HW is better!). For this reason the above formula cannot be regarded as a ‘System Performance Indicator’ but rather provides, taking into account which TRX HW is used, a rough idea about the radio conditions that influence the PRACH performance! For further details please refer to the NSAPRACH counter description in the document 'PM:SBS Counter'.

71 A30808-X3247-B912-1-7618


12 Service related Performance Indicators 12.1 Total number of Service Requests Long name: (a) Total number of service requests

Short name: (a) ServRequests

Description: This indicator provides the total number of Service requests including all service types, triggered by CHANNEL ALLOCATION REQUEST.

Formula: (a) ServRequests = CHALNHLY[19..27]

Used param.: CHALNHLY[19..27]

Elem. Object: BTS

Unit None

Remarks: None

12.2 Service Request Distribution Rate Long name: (a) SDCA Distribution for Signaling (SDCCH)

(b) SDCA Distribution for CS speech (c) SDCA Distribution for CS speech AMR FR (d) SDCA Distribution for CS speech AMR HR (e) SDCA Distribution for CS data (f) SDCA Distribution for HSCSD (g) SDCA Distribution for GPRS (h) SDCA Distribution for EGPRS (i) SDCA Distribution for ASCI

Short name: (a) SDCADistSignal (b) SDCADistCS (c) SDCADistAMRFR (d) SDCADistAMRHR (e) SDCADistCSData (f) SDCADistHSCSD (g) SDCADistGPRS (h) SDCADistEGPRS (i) SDCADistASCI

Description: This indicator will give you the Service Dependent Channel Allocation Distribution rate, showing the particular service dependent channel allocation requests related to the total number of Channel Allocations Requests.

Formula: (a)

tsServReques9]CHALNHLY[1gnalSDCADistSi =

(b) tsServReques

0]CHALNHLY[2SDCADistCS=

72 A30808-X3247-B912-1-7618


(c) tsServReques

1]CHALNHLY[2RFRSDCADistAM =

(d) tsServReques

2]CHALNHLY[2RHRSDCADistAM =

(e) tsServReques

3]CHALNHLY[2DataSDCADistCS =

(f) tsServReques

4]CHALNHLY[2CSDSDCADistHS =

(g) tsServReques

5]CHALNHLY[2RSSDCADistGP =

(h) tsServReques

6]CHALNHLY[2PRSSDCADistEG =

(i) tsServReques

7]CHALNHLY[2CISDCADistAS =

Used param.: CHALNHLY[19..27], ServRequests(12.1(a))

Elem. Object: BTS

Unit None

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

12.3 Rate of Service Requests served in the highest layer Long name: (a) Rate of Service Requests served in highest layer

Short name: (a) ServRequestsRate

Description: These indicators will give you the Service Request Success Rate. All Service Channel Requests served in the highest layer are considered.

Formula: (a)

tsServReques..18]CHALNHLY[11tRateServReques −=

Used param.: CHALNHLY[1..18], ServRequests(12.1(a))

Elem. Object: BTS

Unit None

Remarks: Service requests not supported and not served in the highest layer are subtracted.

73 A30808-X3247-B912-1-7618


13 Feature related Performance Indicators 13.1 Abis pool supervision Long name: Mean number of defined Abis subchannels

Mean number of available Abis subchannels Abis subchannel availability rate Number of attempted Abis subchannel seizures Number of successful Abis subchannel seizures Number of unsuccessful Abis subchannel seizure attempts Abis Pool Traffic offered Abis Pool Traffic carried Abis Pool Traffic lost Abis Pool Loss Rate Abis Pool Blocking Probability Abis Pool Traffic Utilisation Abis Pool Peak Traffic Utilisation

Short name: AbisPDefCh AbisPAvailCh AbisPAvailRate AbisPAttSeiz AbisPSuccSeiz AbisPUnsuccSeiz AbisPTrOff AbisPTrCar AbisPTrLost AbisPLossRate AbisPBlockProb AbisPTrafUtil AbisPTrafUtilPeak

Description: With the Abis Pool Supervision measurements it is possible to evaluate the most important load, capacity and quality related KPIs for the Abis Interface.

Formula: ]ABISPSUP[1 AbisPDefCh =

]ABISPSUP[2 Ch AbisPAvail =

]ABISPSUP[1]ABISPSUP[2 RateAbisPAvail =

]ABISPSUP[7 ]ABISPSUP[6 izAbisPAttSe +=

]ABISPSUP[6 eizAbisPSuccS =

]ABISPSUP[7 cSeizAbisPUnsuc =

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

74 A30808-X3247-B912-1-7618


]ABISPSUP[3 AbisPTrCar =

]ABISPSUP[6]ABISPSUP[7 * ]ABISPSUP[3 t AbisPTrLos =

]ABISPSUP[7 ]ABISPSUP[6]ABISPSUP[7 ateAbisPLossR

+=

Periody Granularit]ABISPSUP[5 ProbAbisPBlock =

]ABISPSUP[1]ABISPSUP[3 tilAbisPTrafU =

]ABISPSUP[1]ABISPSUP[4 tilPeak AbisPTrafU =

Used param.: ABISPSUP[1..7]

Elem. Object: Cell

Unit: None

Remarks: None

75 A30808-X3247-B912-1-7618


14 Handover related Performance Indicators

14.1 Intra Cell Handovers 14.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 Cell Handovers. The indicators on the HO success rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

Formula: (a) ..14]ATINHIAC[1 OAtt IntraCellH =

(b) ..14]SINTHITA[1 OSuccIntraCellH =

(c) OAttIntraCellH

OSuccIntraCellH OSuccRateIntraCellH =

(d) ]ATINHIAC[c]SINTHITA[c [c]OSuccRateCIntraCellH =

with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 inner to complete area c=4 complete to inner area c=5 near to far area c=6 far to near area c=7 forced handover due to O&M c=8 TCH/F to TCH/H due to AMR c=9 TCH/H to TCH/F due to AMR c=10 forced intracell handover due to enhanced pairing c=11 forced intracell handover due to preferred TRX c=12 forced HO due to Multislot calls c=13 compression HO from FR/EFR to HR c=14 decompression HO from HR to FR/EFR

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

76 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Elem. Object: Cell

Unit: None

Remarks: SDCCH handovers are also incremented in this formulas.

14.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 Cause

Short name: (a) IntraCellHOFail (b) IntraCellHOFailRate (c) IntraCellHOFailRateC

Description: These indicators will give you the number and rate of Intra Cell Handover Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old channel. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

Formula:

(a) 1..14] UNINHOIA[ OFailIntraCellH =

(b) OAttIntraCellHOFailIntraCellH OFailRateIntraCellH =

(c) ]ATINHIAC[c]UNINHOIA[c [c]OFailRateCIntraCellH =

with c for the HO cause number: c=1 uplink quality c=2 downlink quality c=3 inner to complete area c=4 complete to inner area c=5 near to far area c=6 far to near area c=7 forced handover due to O&M c=8 TCH/F to TCH/H due to AMR c=9 TCH/H to TCH/F due to AMR c=10 forced intracell handover due to enhanced pairing c=11 forced intracell handover due to preferred TRX c=12 forced HO due to Multislot calls c=13 compression HO from FR/EFR to HR c=14 decompression HO from HR to FR/EFR

Used param.: UNINHOIA[1..14], , ATINHIAC[1..14], IntraCellHOAtt (14.1.1(a))

Elem. Object: Cell

Unit: None


77 A30808-X3247-B912-1-7618


14.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 by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes 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 =


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

Elem. Object: Cell

Unit: None

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

78 A30808-X3247-B912-1-7618


14.1.4 Handover Distribution 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 the reason (=cause) for started Intra Cell Handovers.

Formula: (a)

OAttIntraCellH]ATINHIAC[c ODist[c]IntraCellH =


Used param.: ATINHIAC[1..14], IntraCellHOAtt (14.1.1(a))

Elem. Object: Cell

Unit: None


79 A30808-X3247-B912-1-7618


14.1.5 SDCCH Handover Success Rate Long name: (a) Number of Intra Cell SDCCH Handover Attempts

(b) Number of Intra Cell SDCCH Handover Successes (c) Intra Cell SDCCH Handover Success Rate

Short name: (a) IntraCellSDHOAtt (b) IntraCellSDHOSucc (c) IntraCellSDHOSuccRate

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

Formula: (a) ]AISHINTR[1 DHOAtt IntraCellS =

(b) ]SISHINTR[1 DHOSuccIntraCellS =

(c) DHOAttIntraCellS

DHOSuccIntraCellS eDHOSuccRatIntraCellS =

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

Elem. Object: Cell

Unit: None

Remarks: None

14.1.6 SDCCH Handover Failure Rate Long name: (a) Number of Intra Cell SDCCH Handover Failures

(b) Intra Cell SDCCH Handover Failure Rate

Short name: (a) IntraCellSDHOFail (b) IntraCellSDHOFailRate

Description: These indicators will give you the number and rate of Intra Cell SDCCH Handover Failures by meaning of unsuccessful SDCCH Handovers without loss of MS connection because of reversion to old cell.

Formula: (a) 1] UISHINTR[ DHOFailIntraCellS =

(b) DHOAttIntraCellSDHOFailIntraCellS eDHOFailRatIntraCellS =

UISHINTR[1], IntraCellSDHOAtt (14.1.5(a)) Used param.:

Elem. Object: Cell

Unit: None

Remarks: None

80 A30808-X3247-B912-1-7618


14.1.7 SDCCH Handover Drop Rate Long name: (a) Number of Intra Cell SDCCH Handover Drops

(b) Intra Cell SDCCH Handover Drop Rate

Short name: (a) IntraCellSDHODrop (b) IntraCellSDHODropRate

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

Formula: (a) 1] UISHIALC[ DHODropIntraCellS =

(b) DHOAttIntraCellS

DHODropIntraCellS eDHODropRatIntraCellS =

Used param.: UISHIALC[1], IntraCellHOAtt (14.1.5(a))

Elem. Object: Cell

Unit: None

Remarks: None

81 A30808-X3247-B912-1-7618


14.2 Inter Cell Intra BSC Handovers 14.2.1 Handover Success Rate 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 are additionally provided per HO cause value (latter only for HO success rate)

Formula: (a) ∑∑

= =

++=11

1C

3

0c]11*44*AOUINIRH[n OAtt[n]InterCellH

ii

(b) ∑∑= =

++=11

1C

3

0c]11*44*SOUINIRH[n OSucc[n]InterCellH

ii

(c) OAtt[n]InterCellHOSucc[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 quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 traffic c=10 fast uplink c=11 forced handover due to preemption

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

82 A30808-X3247-B912-1-7618


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

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

Elem. Object: Neighbourcell

Unit: None


83 A30808-X3247-B912-1-7618


14.2.2 Handover Failure Rate 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 BSC Handover Failures by meaning of unsuccessful Handovers without loss of MS connection 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

1Cc]11*[n UNINHOIE OFail[n]InterCellH

(b) OAtt[n]InterCellHOFail[n]InterCellH n]OFailRate[InterCellH =

(c) ∑=

++

+=3

0c]11*44*AOUINIRH[n

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

ii



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

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


Unit: None


84 A30808-X3247-B912-1-7618


14.2.3 Handover Drop Rate 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 per neighbour cell by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

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

(b) OAtt[n]InterCellHODrop[n]InterCellHn]ODropRate[InterCellH =

(c)

∑

∑

=

=

++

++ +

=

3

0

3

0

c]11*44*AOUINIRH[n

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

c][n,ODropRateCInterCellH

i

i

i

i




85 A30808-X3247-B912-1-7618


AOUINIRH[all], SOUINIRH[all], UNINHOIE[all], InterCellHOAtt[all] (14.2.1(a)), InterCellHOSucc[all] (14.2.1(b)), InterCellHOFail[all] (14.2.2(a))

Used param.:


Unit: None

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

86 A30808-X3247-B912-1-7618


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

(b) Imperative Inter Cell Handover Rate

Short name: (a) InterCellHODist (b) ImpInterCellHORate

Description: These indicators will give you the Inter Cell Intra BSC Handover Distribution for analyzing the reason (cause) for started Inter Cell Intra BSC Handovers. Imperative handovers are not whished but rather reflect possible problems in the network topology

Formula:

(a) OAtt[n]InterCellH

c]11*44*AOUINIRH[n c]ODist[n,InterCellH

3

0∑

=

++= i

i

(b) OAtt[n]InterCellH

c]11*44*AOUINIRH[n ]llHORate[nImpInterCe

5

1C

3

0∑∑

= =

++= i

i




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


Unit: None


87 A30808-X3247-B912-1-7618


14.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 Incoming Handovers 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 and that fact can lead to systematic errors.

14.2.6 SDCCH Handover Success Rate Long name: (a) Number of Inter Cell SDCCH Handover Attempts

(b) Number of Inter Cell SDCCH Handover Successes (c) Inter Cell SDCCH Handover Success Rate

Short name: (a) InterCellSDHOAtt (b) InterCellSDHOSucc (c) InterCellSDHOSuccRate

Description: These indicators will give you the rate of successful Inter Cell SDCCH Handovers.

Formula: (a) ]AISHINTE[1 DHOAtt InterCellS =

(b) ]SISHINTE[1 DHOSuccInterCellS =

(c) DHOAttInterCellS

DHOSuccInterCellS eDHOSuccRatInterCellS =

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

Elem. Object: Cell

Unit: None

Remarks: None

88 A30808-X3247-B912-1-7618


14.2.7 SDCCH Handover Failure Rate Long name: Number of Inter Cell SDCCH Handover Failures

Inter Cell SDCCH Handover Failure Rate

Short name: InterCellSDHOFail InterCellSDHOFailRate

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

Formula: 1] UISHINTE[ DHOFailInterCellS =

DHOAttInterCellSDHOFailInterCellS eDHOFailRatInterCellS =

Used param.: UISHINTE[1], InterCellSDHOAtt (14.2.6(a))

Elem. Object: Cell

Unit: None

Remarks: None

14.2.8 SDCCH Handover Drop Rate Long name: Number of Inter Cell SDCCH Handover Drops

Inter Cell SDCCH Handover Drop Rate

Short name: InterCellSDHODrop InterCellSDHODropRate

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

Formula: 1] UISHIRLC[ DHODropInterCellS =

DHOAttInterCellSDHODropInterCellS eDHODropRatInterCellS =

Used param.: UISHIRLC[1], InterCellSDHOAtt (14.2.6(a))

Elem. Object: Cell

Unit: None

Remarks: None

89 A30808-X3247-B912-1-7618


14.3 Inter Cell Inter BSC Handovers 14.3.1 Handover Success Rate 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. The indicators on the HO success rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

Formula: (a) ∑

=

+=10

1Cc]10*[n ATINBHDO Att[n]InterBSCHO

(b) ∑=

+=10

1Cc]10*[n SUINBHDO Succ[n]InterBSCHO

(c) Att[n]InterBSCHOSucc[n]InterBSCHO ]SuccRate[nInterBSCHO =

(d) c]10*ATINBHDO[nc]10*SUINBHDO[n c]n,SuccRateC[InterBSCHO

++

=


c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 fast uplink c=10 forced handover due to preemption

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


Unit: None


90 A30808-X3247-B912-1-7618


14.3.2 Handover Failure Rate 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 BSC Handover. Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old cell. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

Formula:

(a) ∑=

+=10

1Cc]10*[n NRUNINHD Fail[n]InterBSCHO

(b) Att[n]InterBSCHOFail[n]InterBSCHO ]FailRate[nInterBSCHO =

(c) c]10*ATINBHDO[n] 10*NRUNINHD[n c]n,FailRateC[InterBSCHO

++

=c



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


Unit: None


91 A30808-X3247-B912-1-7618


14.3.3 Handover Drop Rate 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 BSC Handover Drops per neighbour cell by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

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

(b) [n][n]

[n]AttInterBSCHO

DropInterBSCHODropRateInterBSCHO =

(c) c]10*ATINBHDO[n

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

+

+=



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

InterBSCHOSucc[all] (14.3.1(b)), InterBSCHOFail[all] (14.3.2(a))


Unit: None

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

92 A30808-X3247-B912-1-7618


14.3.4 Handover Distribution 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 for analysing the reason for started Inter Cell Inter BSC Handovers. Imperative handovers are not whished but reflect possible problems in the network topology

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



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


Unit: None

Remarks: SDCCH handovers are also incremented in these formulas.

93 A30808-X3247-B912-1-7618


14.3.5 SDCCH Handover Success Rate Long name: (a) Number of Inter Cell Inter BSC SDCCH Handover Attempts

(b) Number of Inter Cell Inter BSC SDCCH Handover Successes (c) Inter Cell Inter BSC SDCCH Handover Success Rate

Short name: (a) InterBSCSDHOAtt (b) InterBSCSDHOSucc (c) InterBSCSDHOSuccRate

Description: These indicators will give you the rate of successful Inter Cell Inter BSC SDCCH Handovers.

Formula: (a) ]AOINTESH[1 HOAtt InterBSCSD =

(b) ]SOINTESH[1 HOSuccInterBSCSD =

(c) HOAttInterBSCSD

HOSuccInterBSCSD HOSuccRateInterBSCSD =

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

Elem. Object: Cell

Unit: None

Remarks: None

14.3.6 SDCCH Handover Failure Rate Long name: Number of Inter Cell Inter BSC SDCCH Handover Failures

Inter Cell Inter BSC SDCCH Handover Failure Rate

Short name: InterBSCSDHOFail InterBSCSDHOFailRate

Description: These indicators will give you the number and rate of Inter Cell Inter BSC SDCCH Handover Failures by meaning of unsuccessful SDCCH Handovers without loss of MS connection because of reversion to old cell.

Formula: 1] UOINTESH[ HOFailInterBSCSD =

HOAttInterBSCSDHOFailInterBSCSD HOFailRateInterBSCSD =

UOINTESH[1], InterBSCSDHOAtt (14.3.5(a)) Used param.:

Elem. Object: Cell

Unit: None

Remarks: None

94 A30808-X3247-B912-1-7618


14.3.7 SDCCH Handover Drop Rate Long name: Number of Inter Cell Inter BSC SDCCH Handover Drops

Inter Cell Inter BSC SDCCH Handover Drop Rate

Short name: InterBSCSDHODrop InterBSCSDHODropRate

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

Formula: ] UMCSHLC[1 ODropInterBSCDH =

HOAttInterBSCSDHODropInterBSCSD HODropRateInterBSCSD =

Used param.: UMCSHLC[1], InterBSCSDHOAtt (14.3.5(a))

Elem. Object: Cell

Unit: None

Remarks: None

95 A30808-X3247-B912-1-7618


14.4 Inter System Handover between GSM and UMTS 14.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. The indicators on the HO success rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

Formula: (a) ∑

=+=

10

1cc] 10*[n ATOISHDO gHOAtt[n]InterSysOt

(b) ∑=

+=10

1cc] 10*[n SUOISHDO gHOSucc[n]InterSysOt

(c) gHOAtt[n]InterSysOtgHOSucc[n]InterSysOt e[n]gHOSuccRatInterSysOt =

(d) c]10*ATOISHDO[nc]10*SUOISHDO[n c]eC[n,gHOSuccRatInterSysOt

++

=


c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to pre-emption c=9 forced handover due to O&M intervention c=10 sufficient UMTS coverage

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


Unit: None

Remarks: None

96 A30808-X3247-B912-1-7618


14.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 System Handover Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old cell. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value

Formula: (a) ∑

=+=

10

1cc] 10*[n UNOISHDO gHOFail[n]InterSysOt

(b) gHOAtt[n]InterSysOtgHOFail[n]InterSysOt e[n]gHOFailRatInterSysOt =

(c) c]10*ATOISHDO[n

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

=c



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


Unit: None

Remarks: None

97 A30808-X3247-B912-1-7618


14.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 System Handover Drops per neighbour cell by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes 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,HODropRateInterSysOtg

+

+=



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

(14.4.1(a)), InterSYSHOSucc[all] (14.4.1(b)), InterSYSHOFail[all] (14.4.2(a))


Unit: None

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

98 A30808-X3247-B912-1-7618


14.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 for analyzing the reason for started Inter Cell Inter System Handovers. Imperative handovers are not whished but reflect possible problems in the network topology

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



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


Unit: None

Remarks:

99 A30808-X3247-B912-1-7618


14.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 (c) InterSysIncHOSuccRate

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

Formula: (a) [1] SUIISHDO cHOSuccInterSysIn =

(b) [1] RQIISHDOcHOAttInterSysIn =

(c) cHOAttInterSysIncHOSuccInterSysIn 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:

100 A30808-X3247-B912-1-7618


14.5 Other Handover Performance Indicators 14.5.1 Handovers per Erlanghour Long name: (a) Handover per Erlanghour

Short name: (a) HOperErlh

Description: This indicator will give you the ratio between successful Handovers and the traffic in Erlanghour per cell. Aggregation over all neighbors of the observed cell and all HO causes is performed

Formula: (a) HOperErlh =

[ ] yGranularit60*

allMEBUSTCHll]SUOISHDO[all]SUINBHDO[a ll]SINTHINT[a ll]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 formula and that fact can lead to systematic errors.

• Intersystem HO to UMTS are considered

14.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 Call Setups per cell. Aggregation over all neighbors of the observed cell and all HO causes is performed

Formula: (a) HoperCallRatio =

..5]TASSSUCC[2 ll]SUOISHDO[all]SUINBHDO[a ll]SINTHINT[a ll]SINTHITA[a +++

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

Elem. Object: Cell

Unit: None

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


101 A30808-X3247-B912-1-7618


14.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 cell

Short name: (a) NoSuccDirectedRetryGSM (b) NoSuccDirectedRetryUMTS

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

Formula: (a) NoSuccDirectedRetryGSM[m]

= [ ] [∑=

++++3

0i711*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)


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


Unit: None

Remarks: Intersystem HO to UMTS are considered

102 A30808-X3247-B912-1-7618


14.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 inter system HO to UMTS). The indicator is per GSM resp. per UMTS neighbour cell

Formula: (a) ImpOutgHORateGSM[m]=

OAtt[m]InterCellH Att[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 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 c for the cause number:

c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance


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


Unit: None

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

• Intersystem HO to UMTS considered (FRS 1973) • Correction: cause 5 (distance) now considered in the formula

103 A30808-X3247-B912-1-7618


14.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 Inter BSC Incoming Handovers including incoming HO from UMTS.

Formula: (a)

..44]SININIRH[1 -22] .. 17 14, .. NSUCCHPC[9 -OSuccIntraCellH -,3]TASSSUCC[2-,2]SUCTCHSE[1 cHOSuccInterBSCIn =

(b)

..44]AININIRH[1-..14]ATIMASCA[7-OAttIntraCellH - 3]TASSATT[2,-,2]ATTCHSEI[1cHOAttInterBSCIn =

(c) cHOAttInterBSCIncHOSuccInterBSCIn 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(14.1.1(b)), IntraCellHOAtt(14.1.1(a))

Elem. Object: Cell

Unit: None

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


104 A30808-X3247-B912-1-7618


14.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 the number of Handover indications not resulting in a Handover Attempt divided by the number of all Handover indications. Reasons for this can be congestions or coverage problems. The KPI considers all types of outgoing HO: Inter and Intra BSC and inter system HO to UMTS.

Formula: (a) HOIndRejRate =

∑∑∑===

++++63

0

31

0

31

0

gHOAttInterSysOt]4..1[

]4..1[

nmm

AttInterBSCHOOAttInterCellHOAttIntraCellHNHOINRHA

NHOINRHA

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)

Used param.: NHOINRHA [1..4], IntraCellHOAtt(14.1.1(a)), InterCellHOAtt[m] (14.2.1(a)), InterBSCHOAtt[m] (14.3.1(a)), InterSysOtgHOAtt[n] (14.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 empty neighbour cell list. The reason for this is mainly related to coverage problems.


105 A30808-X3247-B912-1-7618


14.5.7 Total Handover Rate’s Long name: (a) Total Number of Handover Attempts

(b) Total Number of Handover Successes (c) Total Number of Handover Failures (d) Total Number of Handover Drops (e) Total Handover Success Rate (f) Total Handover Failure Rate (g) Total Handover Drop Rate

Short name: (a) HOAtt (b) HOSucc (c) HOFail (d) HODrop (e) HOSuccRate (f) HOFailRate (g) HODropRate

Description: These indicators will give you Handover statistics related to (Intra Cell, Inter Cell, Inter BSC and Inter System) Handovers.

Formula: (a) ll]ATOISHDO[a ll]ATINBHDO[a ll]ATINHIRC[a ll]ATINHIAC[a HOAtt +++=

(b) ll]SUOISHDO[a ll]SUINBHDO[a ll]SINTHINT[a ll]SINTHITA[a HOSucc +++=

(c) all] UNOISHDO[ ll]NRUNINHD[a all] UNINHOIE[ all] UNINHOIA[ HOFail +++=

(d)

ll])UNOISHDO[a- ll]SUOISHDO[a - all](ATOISHDO[ ) ll]NRUNINHD[a ll]SUINBHDO[a - all](ATINBHDO[

1] UNIHIRLC[ ]UNIHIALC[1 HODrop+−

++=

(e) HOAtt

HOSucc HOSuccRate=

(f) HOAttHOFail HOFailRate=

(g) HOAtt

HODrop HODropRate =

Used param.: ATINHIAC[all], SINTHITA[all], UNINHOIA[all], UNINHIALC[all], ATINHIRC[all], SINTHINT[all], UNINHOIE[all], UNIHIRLC[all], ATINBHDO[all], SUINBHDO[all], NRUNINHD[all], ATOISHDO[all], SUOISHDO[all], UNOISHDO[all]

Elem. Object: Cell

Unit: None

Remarks: It can happen, that during a running Handover procedures the user will terminate the call and the call will be released before completion of the Handover procedure..Therefore the number of Handover Successes can be smaller than the difference of HO Attempts – HO Failures – HO Drops. This will lead to a small systematic error for formula (d) and (g).

106 A30808-X3247-B912-1-7618


15 Power and Quality Measurements 15.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. Several indicators distinguish between different interference bands.

Formula: (a) [1..5] MEITCHIB[n] MEITCHIB [n]IfBandRate =

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

Used param.: MEITCHIB[1..5]

Elem. Object: Cell

Unit: None

Remarks: None

15.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 under the threshold FER=N%. It is an indicator of the speech quality provided to the TRX users.

Formula:

(a) [1..64] CFERRXQU

8]8*1..i8*[i CFERRXQU kNFERQualityLin

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

15.3 Mean FER UpLink Long name: (a) Mean FER UpLink

107 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Short name: (a) MeanFERUL

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

Formula:

(a)

( )( )

[1..64] CFERRXQU

8]8*1..i8*[i CFERRXQU*1i MeanFERUL

7

0i∑

=

+++

=


Elem. Object: TRX

Unit: FER Band

Remarks: None.

108 A30808-X3247-B912-1-7618


15.4 Power and Quality limits for N% Percentile on busy TCH

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 on busy channels registered a received Power Level below a certain Level Band and that N% of the measurements on busy channels registered a received Quality below a certain Quality Band. Two indicators distinguish between uplink and downlink.

Formula:

(a) 100N

[1..64]PWRUPDW

n

1i[i])(PWRUPDW

such that n n with ntileULRxLvNPerce =∑==

(b) 100N

[73..136]PWRUPDW

n

1ii])[72(PWRUPDW

such that n n with ntileDLRxLvNPerce =∑=

+=

(c) 100N

[65..72]PWRUPDW

n

1ii])[64(PWRUPDW

such that n n with ntileULRxQuNPerce =∑=

+=

(d) 100N

[137..144]PWRUPDW

n

1ii])[136(PWRUPDW

such that n n with ntileDLRxQuNPerce =∑=

+=

Used param.: PWRUPWD[all]

Elem. Object: Channel

Unit: None

Remarks: None

109 A30808-X3247-B912-1-7618


15.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: 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][nPWRUPDW trUL[n]PWContrDis +

=

(b) 136] .. [73PWRUPDW

73][nPWRUPDW trDL[n]PWContrDis +

=

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

Used param.: PWRUPWD[all]


Unit: None

Remarks: None

110 A30808-X3247-B912-1-7618


15.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. Two indicators 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]


Unit: None

Remarks: None

111 A30808-X3247-B912-1-7618


15.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 in TA Band equal to ‘n’ .

Formula:

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

1]n8[i CRXLVTAU)(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 be configured and is therefore relevant for the analysis of the results.

15.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 in Quality Band equal to ‘n’. Two indicators distinguish between uplink and downlink.

Formula:

(a) [1..64] CRXLVQUD

1]n8[i CRXLVQUD

[n]RxQuDistDL

7

0i∑

=

++×

=

(b) [1..64] CRXLVQUU

1]n8[i CRXLVQUU

[n]RxQuDistUL

7

0i∑

=

++×

=

Where n=0..7

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

Elem. Object: TRX

Unit: None


112 A30808-X3247-B912-1-7618


15.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 Level in Level Band equal to ‘n’. Two indicators distinguish between uplink and downlink.

Formula: (a) [1..64] CRXLVQUD

8]81..n8[n CRXLVQUD[n]RxLvDistDL +×+×=

(b) [1..64] CRXLVQUU

]88n..18[n CRXLVQUU[n]RxLvDistUL +×+×=

Where n=0..7

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

Elem. Object: TRX

Unit: None


15.10 FER Distribution Long name: (a) FER Distribution

Short name: (a) FERDist[n]

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

Formula: (a)

[1..64] CFERRXQU8]8n..18[n CFERRXQUFERDist[n] +×+×

=

Where n=0..7

Used param.: CFERRXQU[1..64]

Elem. Object: TRX

Unit: None


113 A30808-X3247-B912-1-7618


15.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 Quality Band. The implementation of certain features like frequency hoping improves the FER for the same RXQUAL values and therefore, FER is more accurate indicator for analysing the quality of the connection or speech quality.

Formula:

(a) ( )( )

∑

∑

=

=

++×

++××+

=7

0i

7

0i

1]n8[i CFERRXQU

1]n8[i CFERRXQU1i

[n]orRxQu MeanFERULf

Where n =0..7


Elem. Object: TRX

Unit: FER Band


114 A30808-X3247-B912-1-7618


15.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 either Uplink or Downlink. High interference levels can be associated to high RXLEV averages in the higher Quality Bands.

Formula:

(a) ( )( )

∑

∑

=

=

++×

++××+

=7

0i

7

0i

1]n8[i CRXLVQUD

1]n8[i CRXLVQUD1i

[n] rRxQuDLMeanRxLvfo

(b) ( )( )

∑

∑

=

=

++×

++××+

=7

0i

7

0i

1]n8[i CRXLVQUU

1]n8[i CRXLVQUU1i

[n] rRxQuULMeanRxLvfo

Where n =0..7

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

Elem. Object: TRX

Unit: Level Band


115 A30808-X3247-B912-1-7618


15.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 Advance Band either Uplink or Downlink.

Formula:

(a) ( )( )

∑

∑

=

=

++

+++

= 7

0i

7

0i

1]n8*[i CRXLVTAD

1]n8*[i CRXLVTAD*1i [n] rTADLMeanRxLvfo

(b) ( )( )

∑

∑

=

=

++

+++

= 7

0i

7

0i

1]n8*[i CRXLVTAU

1]n8*[i CRXLVTAU*1i [n] rTAULMeanRxLvfo

Where n =0..7

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

Elem. Object: TRX

Unit: Level Band


116 A30808-X3247-B912-1-7618


15.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 two highest Level Bands (i.e. Level Bands: RXLEV_6 and RXLEV_7) and for the four highest Quality Bands (i.e. Quality Bands: RXQUAL_4, RXQUAL_5, RXQUAL_6 and RXQUAL_7) from the total samples for the four highest Quality Bands. High values 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,61 CRXLVQUDuRateDLHighLvLowQ =

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

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

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 The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.

Remarks:

117 A30808-X3247-B912-1-7618


15.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) TCHAHSRate

Description: 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 rate speech, adaptive multirate full rate speech, full rate data, half rate speech and adaptive 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

118 A30808-X3247-B912-1-7618


15.16 SDCCH Traffic Type Distribution Long name: (a) SDCCH Load caused by speech signaling

(b) SDCCH Load caused by SMS signaling (c) SDCCH Load caused by USSD signaling (d) SDCCH Load caused by SS signaling (e) SDCCH Load caused by other signaling procedures (f) SDCCH Load caused by abnormal cases

Short name: (a) SDCCHLoadSpeech (b) SDCCHLoadSMS (c) SDCCHLoadUSSD (d) SDCCHLoadSS (e) SDCCHLoadOther (f) SDCCHLoadAbnormal

Description: These indicators provide the SDCCH Traffic Type Distribution, by meaning the SDCCH Load for a individual signaling procedure compared to the total SDCCH Load. Different indicators distinguish between the signaling procedures for speech, SMS, USSD, SS, others signaling procedures and abnormal cases. These indicators can be used for supervision and verification of the SDCCH resources.

Formula: (a)

all]MBUSYSSP1[1]MBUSYSSP1[ peech SDCCHLoadS =

(b) all]MBUSYSSP1[2]MBUSYSSP1[ MSSDCCHLoadS =

(c) all]MBUSYSSP1[3]MBUSYSSP1[ SSDSDCCHLoadU =

(d) all]MBUSYSSP1[4]MBUSYSSP1[ SSDCCHLoadS =

(e) all]MBUSYSSP1[5]MBUSYSSP1[ ther SDCCHLoadO =

(f) all]MBUSYSSP1[6]MBUSYSSP1[ bnormalSDCCHLoadA =

Used param.: MBUSYSSP[all]

Elem. Object: Cell

Unit: None Formula c) is only valid, if attribute TRANSPM is enabled. Remarks: Formula d) will not consider SDCCH traffic caused by USSD signaling, if attribute TRANSPM is enabled. In the other case USSD signaling is included.

119 A30808-X3247-B912-1-7618


15.17 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 give you an overview about the quality of the feature Adaptive multirate (AMR). Separate counters distinguish between the different adaptive multirate channel types (8 for adaptive multirate full rate speech, and 5 for adaptive multirate half rate speech) and between uplink / downlink transmission. These indicators provide how often a specific adaptive multirate channel type was used related to all 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) 4 for TCH/AFS 7.4 uplink (AMR full rate speech, 7.5 kbit/s, uplink) 5 for TCH/AFS 6.7 uplink (AMR full rate speech, 6.7 kbit/s, uplink) 6 for TCH/AFS 5.9 uplink (AMR full rate speech, 5.9 kbit/s, uplink) 7 for TCH/AFS 5.15 uplink (AMR full rate speech, 5.15 kbit/s, uplink) 8 for TCH/AFS 4.75 uplink (AMR full rate speech, 4.75 kbit/s, uplink) 9 for TCH/AHS 7.4 uplink (AMR half rate speech, 7.4 kbit/s, uplink) 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) 12 for TCH/AHS 5.15 uplink (AMR half rate speech, 5.15 kbit/s, uplink) 13 for TCH/AHS 4.75 uplink (AMR half rate speech, 4.75 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) 17 for TCH/AFS 7.4 downlink (AMR full rate speech, 7.5 kbit/s, downlink) 18 for TCH/AFS 6.7 downlink (AMR full rate speech, 6.7 kbit/s, downlink) 19 for TCH/AFS 5.9 downlink (AMR full rate speech, 5.9 kbit/s, downlink) 20 for TCH/AFS 5.15 downlink (AMR full rate speech, 5.15 kbit/s, downlink) 21 for TCH/AFS 4.75 downlink (AMR full rate speech, 4.75 kbit/s, downlink) 22 for TCH/AHS 7.4 downlink (AMR half rate speech, 7.4 kbit/s, downlink) 23 for TCH/AHS 6.7 downlink (AMR half rate speech, 6.7 kbit/s, downlink) 24 for TCH/AHS 5.9 downlink (AMR half rate speech, 5.9 kbit/s, downlink) 25 for TCH/AHS 5.15 downlink (AMR half rate speech, 5.15 kbit/s, downlink) 26 for TCH/AHS 4.75 downlink (AMR half rate speech, 4.75 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 measured value is in percent and KPI`s shouldn`t be in percent.

120 A30808-X3247-B912-1-7618


15.18 Adaptive 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 (coded

modes) for the uplink and downlink directions • In addition for the uplink direction the True FER is provided for each channel

type separately.

Formula: (a) ∑= +

+=

13

1 100]AMRCHDIS[n*

13]n [n,13][n AMRTFERUL

n AMRFRMULAMRFRMUL

(b) 13]n [n,

13][n HT[n]AMRTFERULC+

+=

AMRFRMULAMRFRMUL

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.9 7 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

AMRFRMDLAMRFRMDL

=

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

Elem. Object: Cell

Unit: None

Remarks: • AMRCHDIS is in units of percent and must therefore be divided by 100 to get the weighting factor per channel mode

121 A30808-X3247-B912-1-7618


16 Availability related Performance Indicators

16.1 Transceiver Availability Long name: (a) Tranceiver Availability

Short name: (a) TRXAvail

Description: This indicator will give you the TRX Availability.

Formula: (a) 60s *y Granularit

[1] TRANAVTI TRXAvail =

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

Elem. Object: TRX

Unit: None

Remarks: None

16.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 traffic channels 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 configured as TCH and or TCH/SD with pooltype 'TCH_Pool' or TCH/SD with pooltype 'TCH_SD_Pool' are considered for measurement NRDEFTCH.

16.3 TCH Availability Long name: (a) TCH Availability Full Rate

122 A30808-X3247-B912-1-7618


(b) TCH Availability Half Rate (c) TCH Availability Dual Rate

Short name: (a) TCHAvailFR (b) TCHAvailHR (c) TCHAvailDR

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

Formula: (a)

,9]NRDEFTCH[3]NAVTCH[3,9 TCHAvailFR =

(b) ,12]NRDEFTCH[62]NAVTCH[6,1 TCHAvailHR =

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

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

=

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

Elem. Object: Cell

Unit: None

Remarks: • Reserved GPRS channels (defined by parameters GMANPRESPRM and GMANPRESCOM in the PTPPKF object) are not considered into NRDEFTCH and NAVTCH measurements.

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

• Due to feature ‘Smooth Channel Modification’ now all available timeslots possible to use as TCH are considered for measurement NAVTCH (Timeslots configured as TCH or TCH/SD with pooltype TCH_Pool' or TCH/SD with pooltype 'TCH_SD_Pool').

123 A30808-X3247-B912-1-7618


16.4 SDCCH Availability Long name: (a) SDCCH Availability

Short name: (a) SDCCHAvail

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

Formula: (a)

]NDESDCCH[3[3] NAVSDCCH SDCCHAvail =

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

Elem. Object: Cell

Unit: None

Remarks: Due to feature ‘Smooth Channel Modification’ now all timeslots configured as SDCCH and TCH/SD with pooltype 'SDCCH_Pool' are considered for measurement NDESDCCH. Due to feature ‘Smooth Channel Modification’ now all available timeslots to be used as SDCCH are considered for measurement NAVSDCCH (Timeslots configured as SDCCH or TCH/SD with pooltype ‘SDCCH_Pool’) .

124 A30808-X3247-B912-1-7618


17 GPRS Related Performance Indicators

17.1 User oriented KPIs

17.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 and downlink.

Formula: (a) TBFEstAttUL = NUACATCL[1] (b) TBFEstAttDL = NUACATCL[2]

Used param.: NUACATCL[1,2]]

Elem. Object: Cell

Unit: None

Remark:

17.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]

125 A30808-X3247-B912-1-7618


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

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

Elem. Object: Cell

Unit: None

Remark:

17.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 a cell 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:

17.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 probability considering 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: None

126 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Remark:

17.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]SUCPDASA ULRateNoReacTBFEstFail =

(d) ]NUACATCL[2

]SULACCEL[2 - [2]SUCPDASA DLRateNoReacTBFEstFail =

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

Elem. Object: Cell

Unit: None

Remark:

17.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 where only 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]

127 A30808-X3247-B912-1-7618


(b) TBFEstSuccRedRateDL = UNSPDCSE[2] / SULACCEL[2]

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

Elem. Object: Cell

Unit:

Remark:

17.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 considering uplink and downlink directions.

Formula: (a) TBFNormRelUl = SUCTETBF[1,2] (b) TBFNormRelDL = SUCTETBF[3,4]

Used param.: SUCTETBF[1…4]

Elem. Object: Cell

Unit: None

Remark:

17.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 causes considering uplink and downlink directions.

Formula: (a) TBFDrAllCauseUL = UNSTETBF[1,3,4,5,6,10,12,14,16] (b) TBFDrAllCauseDL = UNSTETBF[2,7,8,9,11,13,15,17]

Used param.: UNSTETBF[all]

Elem. Object: Cell

Unit: None

Remark: • “Dropped” means that a TBF is terminated in an abnormal way. But

128 A30808-X3247-B912-1-7618


a TBF drop does not necessarily indicate system misbehavior. E.g. UNSTETBF[1] (T3169 expiry) is not only counted when the MS is “lost” but is also counted in case of MS based cell reselection during uplink TBF and in case of circuit switched call setup during uplink TBF (and additionally in some other cases).

• Counter NRRFPDU [1] Number of Received FLUSH-PDUs on Gb per Cell has not been considered in the formulas:Reason: The reception of a FLUSH-PDU is counted regardless if a TBF is active for the affected TLLI or not. Therefore the counter NRRFPDU does not necessarily count the number of lost TBFs due to cell reselection, but also reselection during GMM Ready State without an active packet transfer.

17.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 preemption (d) Share of DL TBF drop due to preemption (e) Share of UL TBF drop due to ordering of cell reselection (network

controlled cell reselection) (f) Share of DL TBF drop due to ordering of cell reselection (network

controlled cell reselection)

Short Name: (a) TBFDrShareTimerExpUL (b) TBFDrShareTimerExpDL (c) TBFDrSharePreemptionUL (d) TBFDrSharePreemptionDL (e) TBFDrShareCellResOrdUL (f) TBFDrShareCellResOrdDL

Description : This indicator provides the distribution of TBF drops per cause considering uplink and downlink directions.

Formula: (a)

useULTBFDrAllCa ]UNSTETBF[1 TimerExpULTBFDrShare =

(b) useDLTBFDrAllCa

]UNSTETBF[2 TimerExpDLTBFDrShare =

(c) useULTBFDrAllCa

,4,5,6]UNSTETBF[3 ULPreemptionTBFDrShare =

(d) useDLTBFDrAllCa

,8,9]UNSTETBF[7 DLPreemptionTBFDrShare =

(e) useULTBFDrAllCa

4]UNSTETBF[1 ULCellResOrdTBFDrShare =

(f) useDLTBFDrAllCa

5]UNSTETBF[1 DLCellResOrdTBFDrShare =

129 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Used param.: UNSTETBF[1..9,14,15], TBFDrAllCauseUL (17.1.8(a)), TBFDrAllCauseDL

(17.1.8(b)))

Elem. Object: Cell

Unit: None

Remark:

17.1.10 TBF drop rate Long Name: (a) Uplink TBF drop rate

(b) Downlink TBF drop rate

Short Name: (a) TBFDropRateUL (b) TBFDropRateDL

Description : This indicator provides the total TBF drop rate form MS point of view considering uplink and downlink directions.

Formula: (a)

]SULACCEL[1,10,12]UNSTETBF[1 eULTBFDropRat =

(b) ]SULACCEL[2

,11,13]UNSTETBF[2 eDLTBFDropRat =

Used param.: SULACCEL[1,2], UNSTETBF[1,2,10,11,12,13]

Elem. Object: Cell

Unit: None

Remark: • SULACCEL shall be taken as denominator because only TBFs shall be considered which are assigned from MS point of view and because also UNSTETBF start counting in BR8.0 after the TBF is assigned from MS point of view.

• Preemption, Packet Cell Change Order and Flush_LL counters shall not be considered.

• There will be a systematic error if Timer T3169 or T3195 expires in case a cell reselection was executed.

• Phantom (P)RACHs (spurious (P)RACHs) shall not be considered.

17.1.11 TBF Drop frequency Long 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 TBF drops per hour TBF duration. Uplink and downlink directions are considered.

130 A30808-X3247-B912-1-7618


(a) NACTTBF[2]

gran 60 * useULTBFDrAllCa

ULTBFDrFrequ =

(b) NACTTBF[4]

gran 60 * useDLTBFDrAllCa

DLTBFDrFrequ =

Used param.: (a) NACTTBF[2,4]; TBFDrAllCauseUL (17.1.8(a)), TBFDrAllCauseDL (17.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 GMM and SM) related data transfer on radio interface the formulas produce an inaccurate result under certain circumstances. Reasons:

• NACTTBF[2,4] is sampled on a second basis (GMM and SM related TBFs 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 a granularity 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 TBF

duration Disadvantage: • Formula might produce inaccurate result when considerable amount

of TBFs are established (triggering of NACTTBF[1,3]) and released (triggering of MEANTBFL[1,2]) in different measurement intervals.

17.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 one hour TBF duration. Uplink and downlink directions are considered.

Formula: (a)

ULTBFDrFrequ3600 imeULTBFDrMeanT =

131 A30808-X3247-B912-1-7618


(b) DLTBFDrFrequ

3600 imeDLTBFDrMeanT =

Used param.: TBFDrFrequUL (17.1.11(a)), TBFDrFrequDL(17.1.11(b))

Elem. Object: Cell

Unit: Seconds

Remark: Possible inaccuracy of formula: See remark on KPI 17.1.11 TBF Drop frequency

17.1.13 User data throughput per TBF on the air interface Long Name: (a) Mean user data throughput per uplink TBF averaged over all Coding

Schemes (b) Mean user data throughput per downlink TBF averaged over all Coding

Schemes (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. itprovides 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 its life 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)

10008*

[2] NACTTBF13]MUTHRF[1.. rTBFAvULUserDataTh =

(b) 1000

8*[4] NACTTBF

26] 4..REMUTHRF[1 - 26] .MUTHRF[14. rTBFAvDLUserDataTh =

132 A30808-X3247-B912-1-7618


(c) 1000

8* lUL[c]CSDistrCel * [2] NACTTBF

MUTHRF[c] ]rTBFCSUL[cUserDataTh =

(d) 1000

8* lDL[c]CSDistrCel * [4] NACTTBF13] REMUTHRF[c - 13] MUTHRF[c ]rTBFCSDL[cUserDataTh ++

=

With parameter c for the observed coding scheme: c = 1 coding scheme CS1 c = 2 coding scheme CS2 c = 3 coding scheme CS3 c = 4 coding scheme CS4 c = 5 coding scheme MCS1 c = 6 coding scheme MCS2 c = 7 coding scheme MCS3 c = 8 coding scheme MCS4 c = 9 coding scheme MMS5 c = 10 coding scheme MCS6 c = 11 coding scheme MCS7 c = 12 coding scheme MCS8 c = 13 coding scheme MCS9

Used param.: (a) NACTTBF [2,4], MUTHRF[all], REMUTHRF[14 .. 26], CSDistrCellUL (17.3.4(a)), CSDistrCellDL (17.3.4(b)): weighting factors for the distribution of transmission 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 the following phenomenon: • The release of a DL TBF is normally delayed for 1,5 seconds

(default value of configuration parameter TIMTBFREL). o During its lifetime a DL TBF may contain once or several times 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 high compared to TBF which serve for transmission of end-to-end user data 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/MAC signaling takes place: e.g. MS confirmation of TBF establishment, 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 data transmission)

133 A30808-X3247-B912-1-7618

http://dict.leo.org/se?p=/Mn4k.&search=phenomenon


• Different treatment of UL and DL direction in the formula

DL throughput: o The retransmitted throughput in DL direction is included in the

measurement MUTHRF (UL); therefore REMUTHRF (UL) has to be subtracted

UL throughput: o Retransmissions due to bad radio link quality are not included in

measurement MUTHRF (UL). • Systematic error on formula:

See remark on KPI 17.2.2 User Throughput on radio interface per cell • Possible inaccuracy of formula:

See remark on KPI 17.1.11 TBF Drop frequency

17.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 reassignment attempts 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:

17.1.15 Packet resource reassignment failures Long Name: (a) Number of unsuccessful packet resource reassignment procedures for

uplink TBFs (b) Number of unsuccessful packet resource reassignment procedures for

downlink TBFs

Short Name: (a) ReasFailTBFUL (b) ReasFailTBFDL

Description : This indicator provides the mean number of unsuccessful packet resource

134 A30808-X3247-B912-1-7618


reassignment procedures per cell separated for uplink and downlink TBFs.


Formula: (a) ReasFailTBFUL = NATPRRE[1] - NSUPRRE[1] (b) ReasFailTBFDL = NATPRRE[2] - NSUPRRE[2]

Used param.: NATPRRE[all], NSUPRRE[all]

Elem. Object: Cell

Unit: none

Remark:

17.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:

17.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 cell

135 A30808-X3247-B912-1-7618


separated for uplink and downlink TBFs.


Formula: (a) NATPRRE[1]

[1] NSUPRRE1Re −=TBFULasFailRate

(b) NATPRRE[2][2] NSUPRRE1Re −=TBFDLasFailRate


Elem. Object: Cell

Unit: none

Remark:

17.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: (a) TBFUpgrFrequUL (b) TBFDowngrFrequUL (c) TBFUpgrFrequDL (d) 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[3gran

60 * [1]SERVUGDG quULTBFUpgrFre =

(b) ]NALLPDCH[3gran

60 * [2]SERVUGDG requULTBFDowngrF =

(c) ]NALLPDCH[6gran

60 * [3]SERVUGDG quDLTBFUpgrFre =

(d) ]NALLPDCH[6gran

60 * [4]SERVUGDG requDLTBFDowngrF =

Used param.: SERVUGDG [1 .. 4], NALLPDCH[3,6]

136 A30808-X3247-B912-1-7618


Unit: Occurrences per hour = (1 / hour)

Remark:

17.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:

17.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

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.

Description :

Use Case

Formula:

(a) ]NALLPDCH[3gran

60 * [1] LADAPTUD requUpwULLinkAdaptF =

137 A30808-X3247-B912-1-7618


(b) ]NALLPDCH[3gran

60 * [2] LADAPTUD LrequDownwULinkAdaptF =

(c) ]NALLPDCH[6gran

60 * [3] LADAPTUD requUpwDLLinkAdaptF =

(d) ]NALLPDCH[6gran

60 * [4] LADAPTUD LrequDownwDLinkAdaptF =

Used param.: LADAPTUD [1 .. 4], NALLPDCH[3,6]

Elem. Object: Cell

Unit: Occurrences per hour (= 1 / hour)

Remark:

17.1.21 Total number of discarded LLC frames Long Name: (a) Total number of discarded Uplink LLC Frames per Interactive class

(b) Total number of discarded Uplink LLC Frames per Streaming class (c) Total number of discarded Uplink LLC Frames per Background class (d) Total number of discarded Downlink LLC Frames per Interactive class (e) Total number of discarded Downlink LLC Frames per Streaming class (f) Total number of discarded Downlink LLC Frames per Background class

Short Name: (a) LLCIntFrDiscTotUL (b) LLCStFrDiscTotUL (c) LLCBgFrDiscTotUL (d) LLCIntFrDiscTotDL (e) LLCStFrDiscTotDL (f) LLCBgFrDiscTotDL

Description : This indicator provides the total number of LLC frame discards for all causes per cell and per traffic class (interactive, streaming, background services). Uplink and downlink directions are considered.

Use case network optimization from operator view, trouble shooting

Formula: (a) LLCIntFrDiscTotUL= DISCLPDU[11..13] (b) LLCStFrDiscTotUL= DISCLPDU[25..27] (c) LLCBgFrDiscTotUL= DISCLPDU[39..41] (d) LLCIntFrDiscTotDL= DISCLPDU[1..10, 14] (e) LLCStFrDiscTotDL= DISCLPDU[15..24, 28] (f) LLCBgFrDiscTotDL= DISCLPDU[29..38, 42]

Used param.: DISCLPDU[all]

138 A30808-X3247-B912-1-7618


Unit: None

Remark:

17.1.22 LLC Frame discard rate Long Name: (a) Rate for Uplink LLC Frame Discard per Interactive class

(b) Rate for Uplink LLC Frame Discard per Streaming class (c) Rate for Uplink LLC Frame Discard per Background class (d) Rate for Downlink LLC Frame Discard per Interactive class (e) Rate for Downlink LLC Frame Discard per Streaming class (f) Rate for Downlink LLC Frame Discard per Background class

Short Name: (a) LLCIntFrDiscRateUL (b) LLCStFrDiscRateUL (c) LLCBgFrDiscRateUL (d) LLCIntFrDiscRateDL (e) LLCStFrDiscRateDL (f) LLCBgFrDiscRateDL

Description : This indicator provides the LLC frame discard rate for all causes per traffic class (interactive, streaming, background services). Uplink and downlink directions are considered.

Use case network optimization from operator view, trouble shooting

Formula: (a)

]NTRLLCFR[1 1..13]DISCLPDU[1 scRateULLLCIntFrDi =

(b) ]NTRLLCFR[2

5..27]DISCLPDU[2 cRateULLLCStFrDis =

(c) ]NTRLLCFR[3

9..41]DISCLPDU[3 cRateULLLCBgFrDis =

(d) ]NTRLLCFR[4

14] ..10,DISCLPDU[1 scRateDLLLCIntFrDi =

(e) ]NTRLLCFR[5

28] 5..24,DISCLPDU[1 cRateDLLLCStFrDis =

(f) ]NTRLLCFR[6

42] 9..38,DISCLPDU[2 cRateDLLLCBgFrDis =

Used param.: DISCLPDU[all], NTRLLCFR[all]

Elem. Object: Cell

Unit: None

Remark:

139 A30808-X3247-B912-1-7618


17.2 Network planning (dimensioning)

17.2.1 Total Throughput on air interface per cell Long 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 terms of throughput The signaling and retransmission loads are included. The uplink\downlink directions are separated.

Use Case Network capacity planning.

Formula: (a) 1000

8 *MSTHRF[1]) ..13]REMUTHRF[1 13]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 UL retransmitted throughput

17.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) UserThrUmCellDL

Description : This indicator provides the mean LLC throughput on the air interface per cell. Retransmissions are excluded; therefore only the amount of data transmitted on behalf of the application layer (here LLC) is considered The uplink\downlink directions are separated. The KPI does not indicate the packet throughput experienced by a single subscriber. Instead the KPI refers to the mean user packet load of a whole cell according to the following model: The user packet volume transmitted for

140 A30808-X3247-B912-1-7618


a cell is accumulated over the whole granularity period and afterwards divided by the length of granularity period


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 the


UL throughput: • Retransmissions due to bad radio link quality are not included in

measurement MUTHRF (UL). • Systematic error in formula:

The MS may also retransmit a previously transmitted RLC/MAC block when nothing else has to be transmitted in UL direction. In that case the BSC will receive certain RLC/MAC block more than once. The counter MUTHRF (UL ) registers each of these receipts. Therefore UserThrUmCellUL contains a systematic error. For short duration TBF (GMM/SM activities) the error is larger than for medium or long duration TBFs (e,g, TBF for WAP session or ftp).

17.2.3 Uplink / Downlink distribution of user throughput on radio interface 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 packet data transmission per cell on radio interface.

Formula: (a) CellDLUserThrUmellULUserThrUmC

ellULUserThrUmC ellULShareUserThrUmC+

=

(b) CellDLUserThrUmellULUserThrUmC

ellDLUserThrUmC ellDLShareUserThrUmC+

=

UserThrUmCellUL (17.2.2 (a)) UserThrUmCellDL (17.2.2 (c)) Used param.:

Elem. Object: Cell

Unit: None

141 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Remark: None

17.2.4 Total packet volume transmitted on radio interface per cell

Long Name: (a) Total packet volume transmitted on radio interface per cell in uplink direction including retransmitted throughput

(b) Total packet volume transmitted on radio interface per cell in downlink direction including retransmitted throughput

Short Name: (a) TotVolUmCellUL (b) TotVolUmCellDL

Description : The indicators measure the air interface related packet load of a cell in terms of transmitted data volume. The signaling and retransmission loads are included. The uplink\downlink directions are separated.


Formula: (a) TotVolUmCellUL = TotThrUmCellUL * gran * 60 (b) TotVolUmCellDL = TotThrUmCellDL * gran * 60

TotThrUmCellUL, TotThrUmCellDL (17.2.1), granularity period “gran” in minutes

Used param.:

Elem. Object: Cell

Unit: kbit

Remark:

17.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 Gb interface in the uplink/downlink direction. The total packet throughput comprises user data (LLC layer) from traffic classes (interactive, streaming, background services) including BSSGP header and BSSGP signaling

142 A30808-X3247-B912-1-7618


(a) 1000

8 * MSTHBS[1]) .3](MUTHBS[1. llULTotThrGbCe +=

(b) 1000

8 * MSTHBS[2]) .6](MUTHBS[4. llDLTotThrGbCe +=

Used param.: MUTHBS[all];MSTHBS[1,2];

Elem. Object: Cell

Unit: kbit/sec

Remark: None

17.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 cell on the Gb interface in the uplink/downlink direction.

Formula: (a)

1000 8 * 3]MUTHBS[1.. ellULUserThrGbC =

(b) 1000

8 * 6]MUTHBS[4.. ellDLUserThrGbC =

Used param.: MUTHBS[all]

Elem. Object: Cell

Unit: kbit/sec

Remark: None

17.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 (b) MeanPDCHBusyCellDL

Description : This KPI provides the mean number of PDCHs per cell with at least one UL TBF respectively at least one downlink TBF in progress

143 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System 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

17.2.8 PDCH utilization rate Long Name: (a) Average utilization rate of UL busy PDCHs in terms of used transmission

time (b) Average utilization rate of DL busy PDCHs in terms of used transmission

time

Short Name: (a) MeanBusyPdchUtilCellUL (b) MeanBusyPdchUtilCellDL

Description : This KPI provides the average utilisation of busy PDCHs in terms of the number of transmitted PDUs relative to the possible PDUs. In order to measure the overall utilization the retransmissions and the signaling 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 or

more 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. NRETPDU 1.13](NTRAPDU[1 ½ 11]) .. [1 NRETPDU ..11](NTRAPDU[1(*2

ULchUtilCellMeanBusyPd

NALLPDCH

++++

=

144 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 50 RCL/MAC PDUs per second in each direction (UL and DL). I.e. one PDU represents a transmission time of 20ms. In other words: one PDU per second 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 only 10ms. In other words: one PDU per second equals to 1% occupation time of a PDCH. For BR7 NTRAPDU does not include the RLC/MAC signaling. Therefore the number of signaling PDUs has to be added. That number will be calculated from the signaling throughput (MSTHRH) by assuming that each signaling PDU has exactly a length of 20bytes (maximum length of CS1 frame)

17.2.9 Mean Throughput per busy PDCH Long Name: (a) Mean User Throughput Uplink per busy PDCH cumulated on all Coding

Schemes (b) Mean User Throughput Downlink per busy PDCH cumulated on all

Coding Schemes (c) Mean User Throughput Uplink per busy PDCH depending on the Coding

Scheme (d) Mean User Throughput Downlink per busy PDCH depending on the

Coding Scheme

Short Name: (a) MeanUserThrBusyPdchUL (b) MeanUserThrBusyPdchDL (c) MeanUserThrBusyPdchCSUL (d) MeanUserThrBusyPdchCSDL

Description : This indicator provides the mean RLC packet throughput per busy PDCH per cell. 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 Coding Schemes

145 A30808-X3247-B912-1-7618


The KPI for the throughput depending on the used Coding Scheme is based on the model that an observed busy PDCH has used that Coding Scheme throughout the complete granularity period. This is the achieved throughput if a PDCH were operated exclusively in that Coding Scheme during the granularity period

Use case Network planning (network extension): KPI provides the capacity, which can be provided per PDCH. Assume the user traffic model is given by means of data volume per subscriber and number of subscribers per cell. For that scenario the present KPIs aids to calculate the number of needed PDCHs for the concerned cell

Formula: (a)

]3[tRateULAvgRadioBi LrBusyPdchUMeanUserTh

NALLPDCH=

(b) ]6[

tRateDLAvgRadioBi LrBusyPdchDMeanUserThNALLPDCH

=

(c) [c] lULCSDistrCel * ]3[

teULCS[c]RadioBitRa SUL[c]rBusyPdchCMeanUserThNALLPDCH

=

(d) [c] lDLCSDistrCel * 6][

teDLCS[c]RadioBitRa SDL[c]rBusyPdchCMeanUserThNALLPDCH

=

With parameter c for the observed coding scheme:

c = 1 coding scheme CS1 c = 2 coding scheme CS2 c = 3 coding scheme CS4 c = 4 coding scheme CS5 c = 5 coding scheme MCS1 c = 6 coding scheme MCS2 c = 7 coding scheme MCS3 c = 8 coding scheme MCS4 c = 9 coding scheme MCS5 c = 10 coding scheme MCS6 c = 11 coding scheme MCS7 c = 12 coding scheme MCS8 c = 13 coding scheme MCS9

Used param.: NALLPDCH [3,6], CSDistrCellUL (17.3.4(a)), CSDistrCellDL (17.3.4(b)): weighting factors for the distribution of transmission durations for the different Coding Schemes. AvgRadioBitRateUL (17.2.14(a)), AvgRadioBitRateDL (17.2.14(b)), RadioBitRateULCS (17.2.13(a)), RadioBitRateDLCS (17.2.13(b))

Elem. Object: Cell

Unit: kbit/sec

Remark: • Please note that no RLC/MAC signaling and no RLC/MAC headers

and are included in this indicator. Also retransmissions are excluded. Therefore the total amount of data transmitted via RLC/MAC layers

146 A30808-X3247-B912-1-7618


per PDCH is higher. • Interpretation of KPI result:

The observed throughput per user might be unexpectedly low due to the following phenomenon: • The release of a DL TBF is normally delayed for 1,5 seconds

(default value of configuration parameter TIMTBFREL). o During its lifetime a DL TBF may contain once or several

times 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 high compared to TBF which serve for transmission of end-to-end user data 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 and at the end of the TBF lifetime no LLC data are transmitted. During these periods only RLC/MAC signaling takes place: e.g. MS confirmation of TBF establishment, 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 data transmission)




UL throughput: o Retransmissions due to bad radio link quality are not included

in measurement MUTHRF (UL). • Systematic error on formula:

See remark on KPI 17.2.2 User Throughput on radio interface per cell

• Possible inaccuracy of formula: See remark on KPI 17.1.11 TBF Drop frequency

17.2.10 Mean number of simultaneously active TBFs per cell Long Name: (a) Mean number of simultaneously active TBF per cell uplink

(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 for

147 A30808-X3247-B912-1-7618

http://dict.leo.org/se?p=/Mn4k.&search=phenomenon


the uplink and downlink direction.

Use case Network planning: how many MS have data transmission simultaneously in a cell.

Formula: (a) MeanActTbfUL = NACTTBF[2]; (b) MeanActTbfDL = NACTTBF[4];

Used param.: NACTTBF[2,4];

Elem. Object: Cell

Unit: None

Remark: None

17.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 same PDCH (horizontal allocation) for the uplink and downlink direction.

Use case Network optimization. E.g. tuning of the parameters for PDCH allocation (in connection with the KPIs for packet throughput per user, see chapter 17.1.13)

Formula: (a) MeanTBFMultiplPDCHUL = NTBFPDC[2]; (b) MeanTBFMultiplPDCHDL = NTBFPDC[4];

Used param.: NTBFPDC[2,4];

Elem. Object: Cell

Unit: None

Remark: None

17.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

This indicator provides the mean number of PDCHs assigned to a TBF for the uplink and downlink direction (horizontal allocation)

Description :

Use case Monitoring of MS behavior: penetration of the MS multi slot classes

148 A30808-X3247-B912-1-7618


(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 NALLPDCH[6] = 4 PDCH * 3 min / 15min = 0.8 PDCH NACTTBF[4] = (3min * 60 * 3TBFs / (15min * 60) = 0.6

Note: NACTTBF = = The measurement determines in intervals of 1 second the number of TBFs currently active. At the end of the granularity period the arithmetic

149 A30808-X3247-B912-1-7618


mean value of the samples is calculated.

MeanAllocPdchTbfDL = 2.5 * 0.8/0.6 = 3.33 PDCHs/TBF

17.2.13 PDCH Bit Rate per Coding Scheme Long Name: (a) PDCH Bit Rate per cell per coding scheme in uplink direction

(b) PDCH Bit Rate per cell per coding scheme in downlink direction

Short Name: (a) PDCHBitRateULCS (b) PDCHBitRateDLCS

Description : This indicator provides the LLC packet throughput per coding scheme per cell. The uplink and downlink directions are separated. Indicators are provided for the throughput depending on the used Coding Scheme.

Formula: (a)

)(20*

NRETPDU[c] NTRAPDU[c]NTRAPDU[c] eULCS[c]PDCHBitRat

msBlocSize

+=

(b) PDCHBitRateDLCS[c] =

[ 13] [ 13] *

[ 13] 20( )NTRAPDU c NRETPDU c BlocSize

NTRAPDU c ms⎡ ⎤+ − +⎢ ⎥+⎣ ⎦

Used param.: NTRAPDU[all], NRETPDU[all], with parameter c for the observed coding scheme. BlocSize: the size of the RLC/MAC data bloc depending on the coding scheme in bits

c = Coding scheme BlocSize (bits) c=1 CS-1 160 c=2 CS-2 240 c=3 CS-3 288 c=4 CS-4 400 c=5 MCS-1 176 c=6 MCS-2 224 c=7 MCS-3 296 c=8 MCS-4 352 c=9 MCS-5 448 c=10 MCS-6 592 c=11 MCS-7 896 c=12 MCS-8 1088 c=13 MCS-9 1184

Elem. Object: Cell

Unit: kbit/sec

Remark: • Please note that RLC/MAC signaling is included in this indicator. Also retransmissions are considered.


150 A30808-X3247-B912-1-7618



measurement NTRAPDU(DL); therefore NRETPDU (DL) has to be subtracted

UL throughput: o Retransmissions due to bad radio link quality are not included

in measurement NTRAPDU (UL).

17.2.14 Mean PDCH Bit Rate Long Name: (a) Mean PDCH Bit Rate per cell in uplink direction

(b) Mean PDCH Bit Rate per cell in downlink direction

Short Name: (a) MeanPDCHBitRateUL (b) MeanPDCHBitRateDL

Description : This indicator provides the average LLC packet throughput per cell. The uplink and downlink directions are separated. Indicators are provided for the throughput cumulated over all Coding Schemes.

Use case

Formula: (a) ∑

=

=13

1

][*][tRateULMeanPDCHBic

clULCSDistrCelceULPDCHBitRat

(b) ∑=

=13

1

][*][tRateDLMeanPDCHBic

clDLCSDistrCelceDLPDCHBitRat

Used param.: PDCHBitRateULCS[all], PDCHBitRateDLCS[all] CSDistrCellUL (17.3.4(a)), CSDistrCellDL (17.3.4(b)): weighting factors for the distribution of transmission durations for the different Coding Schemes.

Elem. Object: Cell

Unit: kbit/sec None Remark:

151 A30808-X3247-B912-1-7618


17.3 Network optimization

17.3.1 Retransmission Rate on radio interface per cell per coding scheme

Long Name: (a) Uplink retransmission Rate on radio interface per cell per coding scheme(b) Downlink retransmission Rate on radio interface per cell per coding

scheme

Short Name: (a) RetransRateUmCellULCS (b) RetransRateUmCellDLCS

Description : This indicator provides the retransmission rate on the radio interface per coding scheme by the ratio of the number of RLC/MAC PDUs needed for user data retransmission and the overall number of transmitted user data PDUs. The uplink and downlink directions are considered separately

Use 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[13c]NRETPDU[13 S[c]eUmCellDLCRetransRat

++

=



Used param.: NTRAPDU[all], NRETPDU[all],

Elem. Object: Cell

Unit: none

152 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Remark: In DL direction NTRAPDU contains the retransmitted PDUs. But in UL

directions retransmission is not included in NTRAPDU.

17.3.2 Retransmitted user throughput on radio interface per cell per coding scheme

Long Name: (a) Retransmitted user Throughput on radio interface per cell per coding scheme in uplink direction

(b) Retransmitted user Throughput on radio interface per cell per coding scheme in downlink direction

Short Name: (a) UserThrRetrCellUmULCS (b) UserThrRetrCellUmDLCS

Description : This indicator provides the retransmitted user Throughput on the radio interface per cell per coding scheme. The uplink\downlink directions are separated.

Use Case KPI used for Network quality optimization: -> optimize C/I thresholds for coding scheme selection

Formula: (a)

10008 * ]REMUTHRF[c S[c]rCellUmULCUserThrRet =

(b) 1000

8 * c]3REMUTHRF[1 S[c]rCellUmDLCUserThrRet +=



Used param.: REMUTHRF[all],

Elem. Object: Cell

Unit: kbit/sec

Remark:

153 A30808-X3247-B912-1-7618


17.3.3 Distribution of user throughput on radio interface on Coding Schemes per cell

Long Name: (a) Distribution of Uplink radio interface User Throughput per cell on coding schemes

(b) Distribution of Downlink radio interface User Throughput per cell on coding schemes

Short Name: (a) UserDataUmCellULCSDistr (b) UserDataUmCellDLCSDistr

Description : This indicator provides the distribution of the user data throughput on the radio interface on Coding Schemes. The uplink and downlink directions are considered separately

Use Case During the planning phase of a radio network (i.e. before deployment) the distribution of the user throughput on Coding Schemes is predicted by simulation results. By aid of the presents KPIs these simulation results may be 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]MUTHRF[1..MUTHRF[c] str[c]CellULCSDiUserDataUm =

(b) .26]MUTHRF[14.

c]MUTHRF[13 str[c]CellDLCSDiUserDataUm +=



Used param.: MUTHRF[all],

Elem. Object: Cell

Unit: none

154 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Remark: Remarks

In DL directions the retransmission is included in MUTHRF[13 .. 26] but in UL direction the retransmission is excluded from MUTHRF[1.. 13]. For simplicity it is assumed that the throughput distribution on coding schemes is mainly independent from the inclusion or exclusion of retransmissions.

17.3.4 Timely distribution of the coding scheme utilization on the radio interface

Long Name: (a) Timely distribution of the coding scheme utilization in uplink direction per cell

(b) Timely distribution of the coding scheme utilization in downlink direction per cell

Short Name: (a) CSDistrCellUL (b) CSDistrCellDL

Description : This indicator provides the timely distribution of the utilization of the various coding 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) the distribution of the user data transmission on Coding Schemes is predicted by simulation results. By aid of the presents KPIs these simulation results may be 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

++

=

for c = 11 .. 13 With parameter c for the observed coding scheme:

c = 1 coding scheme CS1 c = 2 coding scheme CS2 c = 3 coding scheme CS4 c = 4 coding scheme CS5

155 A30808-X3247-B912-1-7618


c = 5 coding scheme MCS1 c = 6 coding scheme MCS2 c = 7 coding scheme MCS3 c = 8 coding scheme MCS4 c = 9 coding scheme MCS5 c = 10 coding scheme MCS6 c = 11 coding scheme MCS7 c = 12 coding scheme MCS8 c = 13 coding scheme MCS9

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 is mainly independent from the inclusion or exclusion of retransmissions

• An RLC/MAC PDU for coding schemes MSC7 .. MSC9 occupies half of a radio block (i.e. the duration is ½ * 20ms). Whereas for all other coding schemes an RLC/MAC PDU occupies a full radio block (i.e. the duration is 20ms).

17.4 Cell Reselection

17.4.1 Number of network controlled Intra BSC cell reselection attempts per cell

Long name: (a) Number of network controlled Intra BSC cell reselection attempts per cell

Short name: (a) NumNCIntrBSCCellResAtt

Description: This indicator provides the number of network controlled Intra BSC cell reselection attempts per cell

Formula: (a) NumNCIntrBSCCellResAtt = ATCRORIG [1]

Used param.: ATCRORIG [1]

Elem. Object: Cell

Unit: None

Remarks: None

156 A30808-X3247-B912-1-7618


17.4.2 Number of successful network controlled Intra BSC cell reselections per cell

Long name: (a) Number of successful network controlled Intra BSC cell reselections per cell

Short name: (a) NumNCIntrBSCCellResSuc

Description: This indicator provides the number of successful network controlled Intra BSC cell reselections per cell

Formula: (a) NumNCIntrBSCCellResSuc = SUCRORIG[1]

Used param.: SUCRORIG[1]

Elem. Object: Cell

Unit: None

Remarks: None

17.4.3 Number of network controlled Intra BSC cell reselection failures per cell per cause

Long name: (a) Number of network controlled Intra BSC cell reselection failures per cell due to 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 due to Imm. Assignment Reject or Packet Access Reject on target cell

(d) Number of network controlled Intra BSC cell reselection failures per cell due to Ongoing CS connection

(e) Number of network controlled Intra BSC cell reselection failures per cell due to Anonymous Access

(f) Number of network controlled Intra BSC cell reselection failures per cell due to MS in GMM standby state

(g) Number of network controlled Intra BSC cell reselection failures per cell due to Forced to the standby state

Short name: (a) NumNCIntrBSCCellResFailFrequNotImpl (b) NumNCIntrBSCCellResFailFrequNoRespTarget (c) NumNCIntrBSCCellResFailAccessRejTarget (d) NumNCIntrBSCCellResFailCSOngoing (e) NumNCIntrBSCCellResFailAnonyAccess (f) NumNCIntrBSCCellResFailGMMStandby (g) NumNCIntrBSCCellResFailForcedStandby

Description: These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per cell per cause

157 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System Formula: (a) NumNCIntrBSCCellResFailFrequNotImpl = UNCRORIG [1]

(b) NumNCIntrBSCCellResFailFrequNoRespTarget = UNCRORIG [2] (c) NumNCIntrBSCCellResFailAccessRejTarget = UNCRORIG [3] (d) NumNCIntrBSCCellResFailCSOngoing = UNCRORIG [4] (e) NumNCIntrBSCCellResFailAnonyAccess = UNCRORIG S [5] (f) NumNCIntrBSCCellResFailGMMStandby = UNCRORIG [6] (g) NumNCIntrBSCCellResFailForcedStandby = UNCRORIG [7]

Used param.: UNCRORIG [all]

Elem. Object: Cell

Unit: None

Remarks: None

17.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 cell reselection per cell

Formula: (a)

[1]ATCRORIG ]SUCRORIG[1 ellSucRateNCIntrBSCC =

Used param.: SUCRORIG[1], ATCRORIG [1]

Elem. Object: Cell

Unit: None

Remarks: None

17.4.5 Network controlled Intra BSC cell reselection failure rate

Long name: (a) Network controlled Intra BSC cell reselection failure rate for cause Frequency not implemented

(b) Network controlled Intra BSC cell reselection failure rate for cause No 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 Ongoing CS connection

(e) Network controlled Intra BSC cell reselection failure rate for cause MS in GMM standby state

(f) Network controlled Intra BSC cell reselection failure rate for cause Forced to

158 A30808-X3247-B912-1-7618


the standby state

Short name: (a) NCIntrBSCResFailRateFrequNotImpl (b) NCIntrBSCResFailRateNoRespTarget (c) NCIntrBSCResFailRateAccessRejTarget (d) NCIntrBSCResFailRateCSOngoing (e) NCIntrBSCResFailRateGMMStandby (f) NCIntrBSCResFailRateForcedStandby

Description: These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per cause

Formula: (a)

]ATCRORIG[1]UNCRORIG[1 plFrequNotImesFailRateNCIntrBSCR =

(b) ]ATCRORIG[1]UNCRORIG[2et NoRespTargesFailRateNCIntrBSCR =

(c) ]ATCRORIG[1]UNCRORIG[3arget AccessRejTesFailRateNCIntrBSCR =

(d) ]ATCRORIG[1]UNCRORIG[4 CSOngoingesFailRateNCIntrBSCR =

(e) ]ATCRORIG[1]UNCRORIG[5 GMMStandbyesFailRateNCIntrBSCR =

(f) ]ATCRORIG[1]UNCRORIG[6dby ForcedStanesFailRateNCIntrBSCR =

Used param.: UNCRORIG[1..6], ATCRORIG [1]

Elem. Object: Cell

Unit: None

Remarks: None

17.4.6 Network controlled cell reselection failure rate

Long name: (a) Network controlled cell reselection failure rate

Short name: (a) NCResFailRate

Description: This indicator provides the number of unsuccessful network controlled cell reselections.

Formula: (a)

,2,3,9,10]ATCRORIG[1ll]UNCRORIG[a ateNCResFailR =

Used param.: UNCRORIG[all], ATCRORIG [1,2,3,9,10]

Elem. Object: Cell

Unit: None

Remarks: In general this formula count as far as possible from network point of view.

159 A30808-X3247-B912-1-7618


18 Miscellaneous Performance Indicators 18.1 BSC Processorload Long name: (a) Mean BSC MPCC Processor load

(b) Mean BSC TDPC Processor load (c) Mean BSC PPXU / PCU Processor load (x)

Short name: (a) MPPCLoad (b) TDPCLoad (c) PPXULoad(x)

Description: These indicators provide the processor load at the BSC for the MPCC (Administrative Processor), TDPC (Telephony Processor) and for the Packet Control Units (PPCUs / PPXUs) (up to 12)

Formula: (a) 100

]BSCPRCLD[2 MPPCLoad =

(b) 100]BSCPRCLD[4 TDPCLoad =

(c) 100

x]1BSCPRCLD[3 )PPXULoad(x +=

x = PPXU / PCU number (Range=0..11)

Used param.: BSCPRCLD[2, 4, 31..42]

Elem. Object: BSC

Unit: None

Remarks: None

160 A30808-X3247-B912-1-7618


18.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

18.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 within a single cell.

Formula: (a)

[5,13,21] NSUCCHPC17] 9, [1, NSUCCHPC Cellr UpdRatioPePagRespLoc =

Used param.: NSUCCHPC [1,5,9,13,17,21]

Elem. Object: Cell

Unit: None

Remarks: The Paging Response Ratio / Location Update Ratio per cell is related to the Immediate Assignment Procedure.

161 A30808-X3247-B912-1-7618


18.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<->SMLC

Description: 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

ssbyteGRANMinLengthMSUNMSUTRASMSCBSCY

60/80001_]1[_

⋅⋅⋅∅⋅

=>−

(b) ErlssbyteGRAN

MinLengthMSUNMSURECBSCMSCY60/8000

1_]1[_⋅⋅

⋅∅⋅=>−

(c) Erl 2

BSCY_MSC- MSCY_BSC- MSC-Y_BSC >+>=><

(d) ErlssbyteGRAN

MinLengthMSUNMSUTRASSMLCBSCY60/8000

1_]2[_⋅⋅

⋅∅⋅=>−

(e) ErlssbyteGRAN

MinLengthMSUNMSURECBSCSMLCY60/8000

1_]2[_⋅⋅

⋅∅⋅=>−

(f) Erl 2

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 with the existing scanners. An assumption has to be made with the help of traffic models. At the present message structure the MSU has an average length about 35byte. With introduction or extension of services (for example SMS) this value will increase in future.

162 A30808-X3247-B912-1-7618


19 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 at least 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.

163 A30808-X3247-B912-1-7618


20 Appendix 20.1 List of BSS Performance Measurements Short Name Long Name AALTCHTI All available TCH allocated time ABISPDIS Abis Pool Distribution ABISPSUP Abis Pool Supervision ACADMCDMA Number of Calls Admitted on the DMA Layer ACREJCDMA Number of Calls Rejected on the DMA Layer 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 busy

TCHs’ AMRFRMUL Frame measurements for Adaptive Multi-Rate (AMR) on downlink busy

TCHs’ AMRSIDUL SID_UPDATE frame measurements for Adaptive Multi-Rate (AMR) on

uplink busy TCHs’ AMRVAR Voice Activity Rate for Adaptive Multi-Rate (AMR) on uplink/downlink busy

TCHs’ 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) ATCRORIG Attempted network supported cell reselections per cause. ATIMASCA Attempted immediate assignment procedures, per cause ATINBHDO Attempted outgoing inter BSC Handovers per neighbour cell re-lationship 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 load CFERRXQU Correlated FER to RXQUAL measurements CHALNHLY Number of Channel Allocation Requests Not Served in the Highest Layer

or at all CRXLVQUD Correlated RXLEV to RXQUAL measurements (downlink) 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 condition DISCLPDU Number of discarded LLC PDU per cell per cause per traffic class DLKSERST Duration of link in-service state DLKUNCON Duration of the linkset unavailable conditions

164 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System DSLUNAV Duration of signaling link unavailability HOFITABS Total number of Handover failures, intra BSC IFRMABIS I-frame measurements ILUPLKIC Interference measurements on idle TCHs LADAPTUD Link adaptation measurements (uplink/downlink) per cell LLCQULEV DL LLC PDU Queues Filling Level per Cell LOCAUTCH Number of locally generated automatic changeovers MAXBUSDC Maximum number of busy SDCCHs per cell MBTCHCHT Mean number of busy TCH per channel type MBUSYSDC Mean number of busy SDCCHs MBUSYSSP Mean Number of Busy SDCCHs per Signalling Procedure MDURTCRQ Mean duration a TCH is queued (Fullrate/Halfrate) MDURTCSD Mean Duration a TCH/SD with TCH_SD_Pool can be used as SDCCH MEANTBFL Mean TBF length (uplink/downlink) per cell MEBUSTCH Mean number of busy TCHs (Fullrate/Halfrate) MEBUTSLY Mean Number of Busy Channels MEITCHIB Mean number of idle TCHs per interference band MSTHBS Mean signaling data throughput (uplink/downlink) per cell on the BSSGP

Layer Gb interface MSTHRF Mean signaling data throughput (uplink/downlink) per cell on the RF

interface MTCHBUTI Mean TCH busy time (Fullrate/Halfrate) MTCHQLEN Mean TCH queue length (Fullrate/Halfrate) MUTHBS Mean user data throughput (uplink/downlink) per cell per Traffic class on

the BSSGP Layer Gb interface MUTHRF Mean user data throughput (uplink/downlink) per cell on the RF Interface NACSUCPR Number of accesses with a successful result by procedure (PCH, AGCH

and RACH) NACTTBF Total, Mean number of active TBF NALIPDCH Min, max, mean number of activated PDCHs per cell NALLPDCH Min, max, mean number of used (active TBF) PDCHs (uplink/downlink)

per cell NASPAVUN 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 cell NATTSDPE Number of attempted SDCCH seizures in a period NAVPDCH 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 NDEFCCCH Number of All Defined CCCH Channels NDEFPCCC Number of Defined PCCCH Frames NDEFPDCH Min, max, mean number of defined (configured) PDCHs per cell NDESDCCH Number of defined SDCCHs NDFTCHSD Number of defined TCH/SD NHOINRHA Number of handover indications not resulting in a handover at-tempt NINVPRACH Number of invalid PRACH messages per cell per cause NINVRACH 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) transmitted NNNOTNCH Number of new Notifications to be sent on the Notification Channel (NCH)

165 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System NPDCHPCU Min, max, mean number of activated PDCHs per BSC NRCLRCMD Number of Clear Command messages per cell per cause per channel

type NRCLRREQ Number of Clear Request messages per cell per cause per channel type NRDEFTCH Number of defined TCHs (Fullrate/Halfrate) NRETPDU Number of retransmitted PDUs (uplink/downlink) NRFLSDCC Number of lost radio links while using an SDCCH NRFLTCH Number of lost radio links while using a TCH (Fullrate/Halfrate) NRINHDFL Number of inter BSC Handover failures NRRFPDU Number of received FLUSH-PDU on Gb per cell NRUNINHD Number of unsuccessful outgoing inter BSC Handovers per neighbour cell

relationship NSAPRACH Number of Accesses to the PRACH Channel NSUCCHPC Successful immediate assignments of signalling channels per cause NSUGPPAG Number of successful GPRS paging procedures NSUPRRE Number of successful packet resource reassignment procedure attempts

per cell NSUSDSUS Number of Successful Seizures for USSD Signalling 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 cell NTDMPCH Number of transmitted and discarded messages on the PCH per cell NTDMPPCH Number of transmitted and discarded Paging messages on the PPCH per

cell NTRLLCFR Number of transmitted LLC frames (uplink/downlink) per cell per Traffic

Class on the BSSGP layer GB interface NUACATCL Number of attempted PDCH assignments (uplink/downlink) per cell NTRAPDU Number of transmitted PDUs (uplink/downlink) per coding scheme per cell

on the RF interface PWRUPDW Power and quality measurements on uplink/downlink busy TCHs REJPDASS Number of rejected PDCH assignments (uplink/downlink) per cause REMUTHRF Retransmitted mean user data throughput (uplink/downlink) per coding

scheme per cell on the RF interface RFDBCUN Routing failure, DPC unavailable RFSUBUN Routing failure, subsystem unavailable RQIISHDO Number of Requested Incoming Intersystem Handover per BSC SERVUGDG Service upgrade/downgrade measurements (uplink/downlink) per cell SINHOBSC Successful internal Handovers per cause SININIRH Successful incoming internal intercell Handovers per originating cell SINTHINT Successful internal Handovers, intercell, per cause SINTHITA Successful internal Handovers, intracell, per cause SISHINTE Successful Internal SDCCH Handovers Intercell SISHINTR Successful internal SDCCH Handovers Intracell SLFAILAL Signalling link failure SOINTESH Successful MSC controlled SDCCH Handovers SOUINIRH Successful outgoing intercell Handovers per cause, per neighbour cell

relationship SUCPDASA Number of successful PDCH assignments (uplink/downlink) per cell SUCRORIG Successful network supported cell reselections per cell SUCTCHSE Successful TCH seizures (Fullrate/Halfrate) SUCTETBF Number of successful terminated TBFs (uplink/downlink) per cell SUIISHDO Number of Successful Incoming Intersystem Handover per BSC SUIMASCA Successful immediate assignment procedures, per cause

166 A30808-X3247-B912-1-7618

Information PM: SBS Key Performance Indicators System SUINBHDO Successful outgoing inter BSC Handovers per neighbour cell relationship SULACCEL Number of successful PDCH seizures (uplink/downlink) per cell SUOISHDO Successful Outgoing Intersystem Handover per neighbourcell per cause TACCBPRO Total number of accesses by procedures (PCH, AGCH) TANRGPRS Number of attempted GPRS accesses per cell with no GPRS radio

resources allocated TASSATT Total number of assignment attempts per cell per channel type TASSATVS Total number of assignment attempts relevant to VBS/VGCS

Broadcast/Group Channels, per cell TASSFAIL Total number of assignment failures per cell, per cause, per channel type TASSSUCC Total number of successful assignments per cell per channel type TASSUCVS Total number of successful assignments relevant to VBS/VGCS

Broadcast/Group Channels, per cell TCMSGREC Total number of connectionless messages received TCMSGSND Total number of connectionless messages sent TMSGREC Total number of messages received TMSHHDL Total number of messages handled TNMSCNCL Total number of multislot (HSCSD) connections per cell TNSUDHSC Number of service upgrades/downgrades for HSCSD calls TNTCHCL Total number of TCH connections, per cell (Fullrate/Halfrate) TRANAVTI Transceiver available time UISHIALC Unsuccessful Internal SDCCH Handovers Intracell with Loss of

Connection UISHINTE Unsuccessful Internal SDCCH Handovers Intercell UISHINTR Unsuccessful internal SDCCH Handovers Intracell UISHIRLC Unsuccessful Internal SDCCH Handovers Intercell with Loss of

Connection UMCSHLC Unsuccessful MSC-Controlled SDCCH Handovers with Loss of

Connection UNCRORIG Unsuccessful network controlled cell reselections per cell per cause UNIHIALC Unsuccessful internal Handover, intracell, with loss of MS UNIHIRLC Unsuccessful internal Handovers, intercell, with loss of MS UNIISHDO Number of Unsuccessful Incoming Intersystem Handover per BSC UNINHOIA Unsuccessful internal Handovers, intracell UNINHOIE Unsuccessful internal HOs, intercell, with reconnection to the old channel,

cause, per target cell UNOISHDO Unsuccessful Outgoing Intersystem Handover per neighbourcell per

cause UNSPDCSE Number of degraded PDCH seizures (uplink/downlink) per cell UNSTETBF Number of unsuccessful terminated TBFs (uplink/downlink) per cell per

cause UOINTESH Unsuccessful MSC controlled SDCCH Handovers WPSSUPV Wireless Priority Services (WPS) Supervision WUTHBS Weighted User Data Throughput (Uplink/Downlink) per Traffic Class per

Cell on the BSSGP Layer Gb Interface

167 A30808-X3247-B912-1-7618