Kpi

Siemens
Information
System PM: SBS Key Performance Indicators (optional issue) A50016-G5100-A042-1-7618
Date Release
: 15.11.2006 : BR9.0
Information System Contents
PM: SBS Key Performance Indicators
Siemens .................................................................................................................................. 1 Information .............................................................................................................................1 System .................................................................................................................................... 1 PM: SBS Key Performance Indicators ................................................................................. 1 A50016-G5100-A042-1-7618 .................................................................................................. 1 Contents.................................................................................................................................. 2
1 INTRODUCTION ............................................................................................................................................. 5 1.1 Purpose.............................................................................................................................................. 5 1.2 Reference Documents ........................................................................................................................ 5 1.3 Issue History...................................................................................................................................... 5 1.4 Definition of Terms............................................................................................................................ 7 2 TOP LEVEL KPI.......................................................................................................................................... 10 3 IMMEDIATE ASSIGNMENT ANALYSIS.......................................................................................................... 12 3.1 Number of Immediate Assignment Attempts .................................................................................... 14 3.2 Number of Immediate Assignment Losses ....................................................................................... 14 3.3 Number of Immediate Assignments by BSC procedure ................................................................... 15 3.4 Number of AGCH Losses................................................................................................................. 16 3.5 Number of Immediate Assignment Commands sent to MS via AGCH............................................. 16 3.6 Number of Immediate Assignments without MS Seizure.................................................................. 17 3.7 Number of successful Immediate Assignments ................................................................................ 17 3.8 Immediate Assignment Loss Rate .................................................................................................... 18 3.9 AGCH Loss Rate CS ........................................................................................................................ 18 3.10 Immediate Assignment without MS Seizure Rate............................................................................. 19 3.11 Immediate Assignment Success Rate ............................................................................................... 19 4 SSS PROCEDURES ANALYSIS ..................................................................................................................... 20
Fig. 2 Message flow: SSS Procedures during Call Setup (MOC) .......................................... 20 Fig. 3 Traffic flow: SSS Procedures during Call Setup........................................................... 21
4.1 Number of successful Immediate Assignments related to Call Setups ............................................. 22 4.2 Number of Dropped SDCCH Connections related to Call Setups................................................... 23 4.3 Number of SSS Procedure Failures related to Call Setups ............................................................. 23 4.4 SDCCH Drop Rate related to Call Setups....................................................................................... 24 4.5 SSS Procedures Failure Rate related to Call Setups ....................................................................... 24 4.6 SSS Procedures Success Rate related to Call Setups....................................................................... 25 5 ASSIGNMENT ANALYSIS ............................................................................................................................. 26
Fig. 4 Message flow: Assignment Procedure (normal case).................................................. 26 Fig. 5 Traffic flow: Assignment Procedure ............................................................................. 27
5.1 Number of Assignment Attempts ...................................................................................................... 28 5.2 Number of Assignment Failures ...................................................................................................... 29 5.3 Number of successful Assignments .................................................................................................. 30 5.4 Assignment Failure Rate ................................................................................................................. 31 5.5 Assignment Success Rate ................................................................................................................. 32 5.6 Assignment success rate when radio resources available ............................................................... 32 5.7 Mean Number of Repeated Assignment Requests............................................................................ 32 5.8 Repeated Assignment Request Rate ................................................................................................. 33 5.9 Assignment Success Rate for receiver supporting ARP technology................................................. 33 6 CALL SETUP ANALYSIS .............................................................................................................................. 34 6.1 Number of Call Setup Attempts........................................................................................................ 35 6.2 Number of Successful Call Setups ................................................................................................... 35 6.3 Call Setup Success Rate................................................................................................................... 36 6.4 Number of Call Setup Failures ........................................................................................................ 36 6.5 Call Setup Failure Rate ................................................................................................................... 38 7 TCH DROP RELATED PERFORMANCE INDICATORS ..................................................................................... 39 7.1 Number of Dropped TCH Connections ........................................................................................... 39 7.2 TCH Drop Distribution ................................................................................................................... 40 7.3 TCH Drop Rate................................................................................................................................ 43 7.4 Call Drop Rate ................................................................................................................................ 44
A50016-G5100-A042-1-7618
Information System
7.5 Mean Time between TCH Drop....................................................................................................... 46 7.6 TCH Drops per Erlanghour............................................................................................................. 46 7.7 Rate of normal call releases of calls with bad radio quality ........................................................... 46 7.8 Rate of TCH Drops and normal call releases of calls with bad radio quality................................. 47 8 SDCCH DROP RELATED PERFORMANCE INDICATORS................................................................................ 49 8.1 Number of dropped SDCCH Connections ....................................................................................... 49 8.2 SDCCH Drop Rate .......................................................................................................................... 49 8.3 Mean Time between SDCCH Drop.................................................................................................. 50 8.4 SDCCH Drops per Erlanghour ....................................................................................................... 50 9 TCH LOAD RELATED PERFORMANCE INDICATORS..................................................................................... 51 9.1 TCH Load for Circuit Switched Traffic ........................................................................................... 51
Fig. 6 Overview Load related performance indicators............................................................ 51

9.2 10 10.1 Combined time slot utilization for CS and PO Traffic..................................................................... 60 DCCH RELATED PERFORMANCE INDICATORS ...................................................................................... 62 SDCCH Load related Performance Indicators................................................................................ 62
Fig. 7 Overview Dedicated Control Channels ........................................................................ 62 Fig. 8 Overview Load related performance indicators............................................................ 62
10.2 FACCH related Performance Indicators......................................................................................... 67 11 CCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................ 68
Fig. 9 Overview Common Control Channels.......................................................................... 68

11.1 PCH load of downlink CCCH channels .......................................................................................... 70 11.2 AGCH load of downlink CCCH channels........................................................................................ 70 11.3 CCCH load downlink....................................................................................................................... 71 11.4 CCCH load uplink ........................................................................................................................... 71 11.5 PCH Loss Rate ................................................................................................................................ 72 11.6 AGCH Loss Rate.............................................................................................................................. 72 11.7 Invalid RACH Rate .......................................................................................................................... 73 12 PCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................. 74
Fig. 11 Overview Packet Common Control Channels............................................................ 74 Fig. 12 Structure for an exemplary packet common control channel combination................. 75
12.1 12.2 12.3 12.4 12.5 12.6 12.7 13 13.1 13.2 13.3 14 14.1 14.2 14.3 15 15.1 15.2 15.3 15.4 15.5 15.6 16 16.1 16.2 16.3 16.4 16.5 16.6 16.7 16.8 PPCH load of downlink PCCCH channels...................................................................................... 76 PAGCH load of downlink PCCCH channels................................................................................... 76 PCCCH load downlink .................................................................................................................... 77 PCCCH load uplink......................................................................................................................... 77 PPCH Loss Rate .............................................................................................................................. 78 PAGCH Loss Rate ........................................................................................................................... 78 Invalid PRACH Rate........................................................................................................................ 79 SERVICE RELATED PERFORMANCE INDICATORS ................................................................................... 80 Total number of Service Requests.................................................................................................... 80 Service Request Distribution Rate ................................................................................................... 80 Rate of Service Requests served in the highest layer ....................................................................... 81 FEATURE RELATED PERFORMANCE INDICATORS .................................................................................. 82 Abis Pool Traffic Utilization............................................................................................................ 82 I-FRAME Discard Rate on Abis-Interface BSC side ....................................................................... 83 I-FRAME Discard Rate on Abis-Interface BTSE side ..................................................................... 84 HANDOVER RELATED PERFORMANCE INDICATORS ............................................................................... 85 General Handover performance...................................................................................................... 85 Intra Cell Handovers ....................................................................................................................... 86 Inter Cell Intra BSC Handovers ...................................................................................................... 92 Inter Cell Inter BSC Handovers .................................................................................................... 102 Inter System Handover between GSM and UMTS......................................................................... 108 Other Handover Performance Indicators...................................................................................... 113 POWER AND QUALITY MEASUREMENTS ............................................................................................. 119 Interference Band Rate on idle TCH ............................................................................................. 119 Quality Link for N% FER .............................................................................................................. 119 Mean FER UpLink......................................................................................................................... 120 Power and Quality limits for N% Percentile on busy TCH ........................................................... 121 Distribution of power control levels on busy TCH ........................................................................ 122 Mean Level and Quality on busy TCH........................................................................................... 123 TA Distribution.............................................................................................................................. 124 RXQUAL Distribution ................................................................................................................... 124
A50016-G5100-A042-1-7618
Information System
16.9 RXLEV Distribution....................................................................................................................... 125 16.10 FER Distribution ........................................................................................................................... 125 16.11 Mean FER UpLink per RXQUAL .................................................................................................. 126 16.12 Mean RXLEV per RXQUAL Band ................................................................................................. 127 16.13 Mean RXLEV per TA Band............................................................................................................ 128 16.14 High RXLEV with Low RXQUAL Rate .......................................................................................... 129 16.15 TCH Traffic Type Distribution ...................................................................................................... 130 16.16 SDCCH Traffic Type Distribution ................................................................................................. 131 16.17 Adaptive Multirate Distribution .................................................................................................... 132 16.18 Adaptive Multirate True Frame Erasure Rate............................................................................... 133 16.19 Effective Frequency Load .............................................................................................................. 134 16.20 AMR Frame Erasure Rate for ARP-type Receiver ........................................................................ 135 17 AVAILABILITY RELATED PERFORMANCE INDICATORS ........................................................................ 136 17.1 Transceiver Availability ................................................................................................................ 136 17.2 TCH Distribution Rate................................................................................................................... 136 17.3 TCH Availability............................................................................................................................ 137 17.4 SDCCH Availability ...................................................................................................................... 138 17.5 Soft Blocking Rate ......................................................................................................................... 138 18 GPRS RELATED PERFORMANCE INDICATORS ..................................................................................... 140 18.1 User oriented KPIs ........................................................................................................................ 140 18.2 Network planning (dimensioning) ................................................................................................. 157 18.3 Network optimization..................................................................................................................... 170 18.4 Cell Reselection ............................................................................................................................. 174 19 MISCELLANEOUS PERFORMANCE INDICATORS ................................................................................... 178 19.1 BSC1 Processor load..................................................................................................................... 178 19.2 Basic eBSC Processor load ........................................................................................................... 178 19.3 HighEnd eBSC Processor load...................................................................................................... 179 19.4 BTSE Processorload...................................................................................................................... 181 19.5 PCU Occupancy Rate.................................................................................................................... 181 19.6 Paging Response / Location Update Ratio per Cell ...................................................................... 182 19.7 BSC <-> MSC/SMLC CCS7 Load................................................................................................. 183 19.8 Frame Relay Link Utilization ........................................................................................................ 183 19.9 ARP-type Receiver Penetration ..................................................................................................... 184 20 BSS RELATED KPIS AT SIEMENS MSC ............................................................................................... 184 21 APPENDIX ........................................................................................................................................... 186 21.1 List of BSS Performance Measurements........................................................................................ 186
A50016-G5100-A042-1-7618
Information System
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 BR9.0 AFI0.1 Date of issue 03.05.2006 Reason for of issue First version for BR9.0, based on Measurement Layout Interface Specification V2.1 from 16.05.2006 Chapter Top Level KPI added Add AFI0.1 comments Update results from KPI Workshop with TPS and NE in Milan, 29.06.2006 Update acc. to BR9 IC0 features, based on Measurement Layout Interface Specification" BSCSIS-N0085-B90-04-76D6 Revision 3.1 Final version for BR9/IC0 - Alignment with customer KPIs, marked with violet. - Update by BR9/IC1 features, based on Measurement Layout Interface Specification V5.0 from 29.09.2006, marked with green.
BR9.0 AFI0.2
04.08.2006
BR9.0 IUS1.0 BR9.0 AFI1.1
17.08.2006 13.10.2006
A50016-G5100-A042-1-7618
Information System
BR9.0 IUS 2.0 15.11.2006

Add AFI1.1 comments Remove customer defined KPIs
A50016-G5100-A042-1-7618
Information System
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.
A50016-G5100-A042-1-7618
Information 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 KPIs 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 KPIs 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;
A50016-G5100-A042-1-7618
Information System
-
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]])
Standard 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):
Counter (n, m) =
Counter (i, t)
i,t
Counter (n, m) = Counter (i, t)
i t n m
2
elementary object elementary period object (sum of elementary objects) measurement period (sum of elementary periods)
The 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.
A50016-G5100-A042-1-7618
Information System
Top Level KPI
This chapter defines a set of top level KPI, which can be used by Field acceptance tests, Network performance analysis according to a new release or feature, Regular network performance trend analysis. The following KPI will focus on the supervision of performance and quality from the users perspective and as well as on the supervision of the same from a network perspective. Key Performance Indicator Circuit Switched KPIs based on GERAN PM Counters
Immediate Assignment Success Rate SDCCH Drop Rate SDCCH Traffic Carried SDCCH Block Rate TCH Assignment Success Rate TCH Block Rate Soft Blocking Rate TCH Drops per Erlanghour Call Drop Rate TCH Traffic Carried Combined time slot occupation rate for CS and PO Traffic Effective Frequency Load Call Setup Success Rate BSS Intercell Handover Attempts per Speech Call per Erlanghour Handover Success Rate Handover Success Rate 2G to 2G Handover Success Rate 2G to 3G RXQUAL Distribution RXLEV Distribution FER Distribution 3.11 8.2 10.1.2 10.1.5 5.5 5.4 (a) 17.5 7.6 7.4 9.1.4 9.2.1 16.19 6.3(b) 15.6.3 15.1.1 15.1.2 15.1.3 16.8 16.9 16.10 18.1.4 (a), (b) 18.1.5 (a), (b)
Definition Chapter
Packet Switched KPI based on GERAN PM Counters

TBF establishment success rate TBF Establishment Failure Rate for PDCH Congestion
10
A50016-G5100-A042-1-7618
Information System
Key Performance Indicator
TBF Drop frequency Total number of dropped TBFs Weighted LLC User Data Throughput Percent Timeslot Resources Achieved

Definition Chapter
18.1.11 (a), (b) 18.1.8 (a), (b) 18.1.25 18.2.15 18.2.11 18.2.14 18.4.4 18.2.2 19.8
Mean number of TBFs multiplexed on same PDCH Mean PDCH Bit Rate GPRS/EDGE Network controlled Intra BSC cell reselection success rate User Throughput on radio interface per cell Frame Relay Link Utilization
Other KPI based on GERAN PM Counters

Abis Pool Traffic Utilization BSC1 Processor load / TDPC BSC1 Processor load / PCU PCU Occupancy Rate 14.1(l) 19.1 (b) 19.1 (c) 19.5
11
A50016-G5100-A042-1-7618
Information System
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.
MS CHANNEL REQUEST [1] CHANNEL REQUIRED CHANNEL ACTIV CHANNEL ACTIV ACK CHANNEL ACTIV NACK IMM. ASS CMD IMM. ASS REJECT [5] DELETE INDICATION SABM UA [6] ESTABLISH INDIC. [3] [4] [5] IMM. ASS [2] SDCCH CONGESTIONS BTS BSC
Figure 1 Message flow: Immediate Assignment Procedure
SBS Counter [1] CHANNEL REQUIRED
ATIMASCA [1..14]
[2] SDCCH CONGESTIONS ATSDCMBS [1] (Congestions due to SDCCH HO are also counted) [3] IMM. ASS CMD (Abis Interface) (IMM. ASS. CMD. messages, which contain an IMM. ASS. REJ. message are not counted) [4] IMM. ASS CMD (Abis Interface) (including those IMM. ASS. CMD. messages that contain an IMM. ASS. REJ. message) [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) [6] ESTABLISH INDICATION SUIMASCA [1..6]
TACCBPRO [2]
NACSUCPR [2]
NSUCCHPC [1..22]
12
A50016-G5100-A042-1-7618
Information System
The following figure shows you the traffic flow.
[1] Number of Immediate Assignment Attempts [3] Number of Imm Ass. by BSC procedure [5] Imm Ass Command sent to MS via AGCH [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
Fig. 1 Traffic flow: Immediate Assignment Procedure
This chapter contains the following Number related KPIs: Number of Immediate Assignment Attempts: [1] Number of Immediate Assignment Losses : [2]= [1] [3] Number of Immediate Assignments by BSC procedure : [3] = [1] [2]) Number of AGCH Losses: [4] = [9] * [3] Number of Immediate Assignment Commands sent to MS via AGCH: [5] = [3] [4] = (1- [9]) * [3] Number of Immediate Assignments without MS Seizure: [6] = [5] [7] = [3] [4] - [7] Number of successful Immediate Assignments: [7]
And the following Rate related KPIs: Immediate Assignment Loss Rate: [8] = [2] / [1]
AGCH Loss Rate: [9] = [4] / [3])
Immediate Assignment without MS Seizure Rate: [10] = [6] / [5] Immediate Assignment Success Rate: [11] = [7] / ([1] [6])
(Phantom RACHs are not counted, because they are not related to MS)
The Immediate Assignment Failure Rate can be calculated as follows: Immediate Assignment Failure Rate = 1 - Immediate Assignment Success Rate or Immediate Assignment Failure Rate = Immediate Assignment Loss Rate * AGCH Block Rate * Immediate Assignment without MS Seizure Rate
13
A50016-G5100-A042-1-7618
Information System
3.1 Number of Immediate Assignment Attempts

Long name: Short name: Description: (a) Number of Immediate Assignment Attempts (a) ImmAssAtt 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) ImmAssAtt = ATIMASCA[1 ..14]
Formula:
Used param.: ATIMASCA[1..14] Elem. Object: Cell Unit: Remarks: None 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.
3.2 Number of Immediate Assignment Losses

Long name: Short name: Description: (a) Number of Immediate Assignment Losses (a) ImmAssLoss 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)
Formula:
ImmAssLoss = ImmAssAtt - ImmAssBSCp roc
Used param.: ImmAssAtt (3.1(a)) , ImmAssBSCproc (3.3(a)) Elem. Object: Cell Unit: Remarks: None 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.
14
A50016-G5100-A042-1-7618
Information System
3.3 Number of Immediate Assignments by BSC procedure

Long name: Short name: Description: (a) Number of Immediate Assignments by BSC internal procedure (a) ImmAssBSCproc 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)
Formula:
ImmAssBSCp roc = SUIMASCA[1 ..6]
Used param.: SUIMASCA[1..6] Elem. Object: Cell Unit: Remarks: None 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.
15
A50016-G5100-A042-1-7618
Information System
3.4 Number of AGCH Losses

Long name: Short name: Description: (a) Number of AGCH losses (a) AGCHLoss 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) AGCHLoss = AGCHBlockRateCS * ImmAssBSCproc
Formula:
Used param.: AGCHLossRateCS (3.9(a)), ImmAssBSCproc (3.3(a)) Elem. Object: Cell Unit: Remarks: None 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.
3.5 Number of Immediate Assignment Commands sent to MS via AGCH

Long name: Short name: Description: Formula: (a) Number of Immediate Assignments Commands sent to MS via AGCH (a) ImmAssCmdAGCH The KPI provides the number of Immediate Assignments Commands sent to MS via AGCH (a) ImmAssCmdAGCH = (1 AGCHLossRateCS) * ImmAssBSCproc
Used param.: ImmAssBSCproc (3.3(a)), AGCHLossRateCS (3.9(a)) Elem. Object: Cell Unit: Remarks: None 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.
16
A50016-G5100-A042-1-7618
Information System
3.6 Number of Immediate Assignments without MS Seizure

Long name: Short name: Description: (a) Number of Immediate Assignments without MS Seizure (a) ImmAssNoSeiz 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) ImmAssNoSe = ImmAssBSCp - AGCHLoss- ImmAssSucc iz roc
Formula:
Used param.: ImmAssBSCproc (3.3(a)), AGCHLoss (3.4(a)), ImmAssSucc (3.7(a)) Elem. Object: Cell Unit: Remarks: None 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.
3.7 Number of successful Immediate Assignments

Long name: Short name: Description: (a) Number of successful Immediate Assignments (a) ImmAssSucc These indicators will give you the number of successful Immediate Assignments from MS point of view. An Immediate Assignment procedure is successful if the BTS returns an establishment indication message on Abis. (a)
Formula:
ImmA ssSucc = NSUCCHPC[1 .. 6, 9 ..14, 17 .. 22]
Used param.: NSUCCHPC[1 .. 6, 9 .. 14, 17 .. 22] Elem. Object: Cell Unit: Remarks: None 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.
17
A50016-G5100-A042-1-7618
Information System
3.8 Immediate Assignment Loss Rate

Long name: Short name: Description: (a) Immediate Assignment Loss Rate (a) ImmAssLossRate 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. (a) ImmAssLossRate =
Im mAssLoss Im mAssAtt
Formula:
Used param.: ImmAssAtt (3.1(a)), ImmAssLoss (3.2(a)) Elem. Object: Cell Unit: Remarks: None 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).
3.9 AGCH Loss Rate CS

Long name: Short name: Description: (a) AGCH Loss Rate CS (a) AGCHLossRateCS These indicators will give you the AGCH Block 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 failures 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. (a) AGCHLossRa teCS =
TACCBPRO[2 ] - NACSUCPR[2 ] TACCBPRO[2 ]
Formula:
Used param.: TACCBPRO [2], NACSUCPR [2] Elem. Object: Cell Unit: Remarks: None 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.
18
A50016-G5100-A042-1-7618
Information System
3.10 Immediate Assignment without MS Seizure Rate

Long name: Short name: Description: (a) Immediate Assignment without MS Seizure Rate (a) ImmAssNoSeizRate 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. (a) ImmAssNoSeizRate =
Formula:
ImmAssNoSeiz ImmAssCmdAGCH
Used param.: ImmAssNoSeiz (3.6(a)), ImmAssCmdAGCH (3.5(a)) Elem. Object: Cell Unit: Remarks: None 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.
3.11 Immediate Assignment Success Rate

Long name: Short name: Description: (a) Immediate Assignment Success Rate (a) ImmAssSuccRate These indicators will give you the immediate assignment success rate from MS point of view. An Immediate Assignment procedure is successful if the BTS returns an establishment indication message. (a) ImmAssSuccRate =
ImmAssSucc Im mAssAtt Im mAssNoSeiz
Formula:
Used param.: ImmAssAtt (3.1(a)), ImmAssSucc (3.7(a)), ImmAssNoSeiz (3.6(a)) Elem. Object: Cell Unit: Remarks: None 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 Mobiles L2 SABMframe and therefore are not considered here.
19
A50016-G5100-A042-1-7618
Information System
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
MS SABM BTS [1] Establishment Ind. Authentification Request Authentification Response Identity Request Identity Response Ciphering Command Ciphering Complete Setup Call Proceeding [2] Assignment Req. Assignment Command Ciphering Command Ciphering Complete BSC MSC
CR(Compl Layer3Info) CC
Fig. 2 Message flow: SSS Procedures during Call Setup (MOC)
SBS Counter [1] ESTABLISH INDICATION (related to Call Setups) [2] ASSIGNMENT ATTEMPTS
NSUCCHPC[1..4,9..12,17..20] NSUCCHPC[8] 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.
20
A50016-G5100-A042-1-7618
Information System

[1]Successful Immediate Assignments
[2]SDCCH Drops
[3] SSS Procedure failures [4] Assignment Attempts
Fig. 3 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 Success Rate related to Call Setups = [4] / [1] Referenced KPI from chapter 5 Assignment Analysis Number of Assignment Attempts: [4]
21
A50016-G5100-A042-1-7618
Information System
4.1 Number of successful Immediate Assignments related to Call Setups

Long name: Short name: Description: (a) Number of successful Immediate Assignments related to Call Setups (a) ImmAssSuccCS These indicators will give you the number of successful Immediate Assignments related to Call Setups. An 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.
Formula:
..4,9..12,17..20]- NSUCCHPC[8 ] (a) ImmAssSuccCS = NSUCCHPC[1
Used param.: NSUCCHPC[1..4, 8 ..12,17..20] Elem. Object: Cell Unit: Remarks: None 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).
22
A50016-G5100-A042-1-7618
Information System
4.2 Number of Dropped SDCCH Connections related to Call Setups

Long name: Short name: Description: (a) Number of Dropped SDCCH Connections related to Call Setups (a) SDCCHDropCS 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. (a)
Formula:
SDCCHDropCS = SDCCHDrop *
ImmAssSuccCS ImmAssSucc
Used param.: SDCCHDrop(8.1(a)), ImmAssSucc (3.7(a)), ImmAssSuccCS (4.1(a)) Elem. Object: Cell Unit: Remarks: None
4.3 Number of SSS Procedure Failures related to Call Setups

Long name: Short name: Description: Formula: (a) Number of SSS Procedure Failures related to Call Setups (a) SSSProcFailCS This indicator will give you the number of SSS Procedure failures related to Call Setups. (a) SSSProcFai lCS = ImmAssSuccCS - AssAtt - SDCCHDropC S
Used param.: ImmAssSuccCS (4.1(a), AssAtt (5.1(a)), SDCCHDropCS (4.2(a)) Elem. Object: Cell Unit: Remarks: None 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.
23
A50016-G5100-A042-1-7618
Information System
4.4 SDCCH Drop Rate related to Call Setups

Long name: Short name: Description: (a) SDCCH Drop Rate related to Call Setups (a) SDCCHDropRateCS 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)
Formula:
SDCCHDropR ateCS =
SDCCHDropC S SDCCHDropR ate Im mAssSuccCS
Used param.: SDCCHDropCS (4.2(a)), ImmAssSuccCS (4.1(a)), SDCCHDropRate (8.2(a)) Elem. Object: Cell Unit: Remarks: SDCCH Handovers are not considered here. None
4.5 SSS Procedures Failure Rate related to Call Setups

Long name: Short name: Description: (a) SSS Procedures Failure Rate related to Call Setups (a) SSSProcFailRateCS 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). (a) SSSProcFai lRateCS =
SSS Pr ocFailCS Im mAssSuccCS
Formula:
Used param.: SSSProcFailCS (4.3(a)), ImmAssSuccCS (4.1(a)) Elem. Object: Cell Unit: Remarks: None 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.
24
A50016-G5100-A042-1-7618
Information System
4.6 SSS Procedures Success Rate related to Call Setups

Long name: Short name: Description: (a) SSS Procedures Success Rate related to Call Setups (b) Total SSS Procedures Success Rate related to Call Setups (a) SSSProcSuccRateCS (b) SSSProcSuccRateCStotal 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. (a) SSSProcSuccRateCS = 1 - SDCCHDropRateCS (b) SSSProcSuccRateCStotal =
Formula:
AssAtt or ImmAssSuccCS
SSSProcSuccRateCStotal = 1 SDCCHDropRateCS SSS Pr ocFailRateCS

Used param.: ImmAssSuccCS (4.1(a)), AssAtt (5.1(a)), SDCCHDropRateCS (4.4(a)), SSSProcFailRateCS (4.5(a)) Elem. Object: Cell Unit: Remarks: None 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.
25
A50016-G5100-A042-1-7618
Information System
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 message flow of the Assignment Procedure is listed below (normal case). The numbers in brackets will indicate available SBS performance measurements.
MS BTS BSC [1] TASSATT MSC
(MTCHBUTI)
ASSIGNMENT REQUEST
PHYS CONTEXT REQ PHYS CONTEXT CONF CHAN ACTIV CHAN ACTIV ACK CHANNEL ACTIV NEG ACK ASSIGNMENT COMMAND ASSIGNMENT COMMAND SABM UA ASSIGNMENT COMPLETE
(TNTCHCL)
[5] TASSFAIL
ASSIGNMENT FAILURE
ESTABLISH INDICATION
ASSIGNMENT COMPLETE
[4] TASSSUCC
ASSIGNMENT COMPLETE
Fig. 4 Message flow: Assignment Procedure (normal case)
BSS Counter: [1] ASSIGMENT ATTEMPS [2] INCOMING REDIRECTED [3] OUTGOING REDIRECTED CALLS TASSATT [2..3]
TASSSUCC [4..5]
SINTHINT [7] + SUINBHDO [11*n+7]; n = 0 ...31 (n= number of GSM ADJ-ids) + SUOISHDO[10 * m + 7] ; m = 0 ...63 (m= number of UMTS ADJ-ids)
[4] ASSIGMENT COMPLETE (normal Assignm.) [5] ASSIGMENT FAILURE [6] Queuing Failure
TASSSUCC [2..3] TASSFAIL [6,7,8,10,11,12,13,15] NMSGDISQ [1,2]
26
A50016-G5100-A042-1-7618
Information System

Single Cell / Observed Cell [1] Assignment Attempts
[3]+[4] Assignment success [2] Successful inc. redirected Calls
[5] Assignment Failure [6] Queuing Failure
[4] Assignment Complete
[3] Successful Outgoing redirected Calls
Fig. 5 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]
This chapter contains the following Number related KPIs: Number of Assignment Attempts: [1], see chapter 5.1. Number of Assignment Failures: [5] ,see chapters 5.2(a), (b), (c) Number of successful Assignments = [3]+[4], see chapter 5.3 Number of Queuing Failures: [6], see chapter 5.2(d) This chapter contains the following Rate related KPIs: Assignment Failure Rate, see chapter 5.4 Assignment Success Rate, see chapter 5.5 Assignment success rate when radio resources available, see chapter 5.6(a)
27
A50016-G5100-A042-1-7618
Information System
5.1 Number of Assignment Attempts

Long name: Short name: Description: Formula: (a) Number of Assignment Attempts (a) AssAtt These indicators will give you the number of Assignment procedures started by the MSC. (a)
AssAtt
= TASSATT[2, 3]
Used param.: TASSATT[2,3] Elem. Object: Cell Unit: Remarks: None 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.
28
A50016-G5100-A042-1-7618
Information System
5.2 Number of Assignment Failures

Long name: (a) (b) (c) (d) (e) (a) (b) (c) (d) (e) Number of TCH Losses Number of Assignment Failures by Message Number of Assignment Failures due to other Reason Number of Queuing Failures Total Number of Assignment Failures TCHLoss AssFailbyMess AssFailOther QueFail AssFail
= TASSFAIL[8,13]
Short name:
Description: Formula:
These indicators will give you the number of failed Assignments of a TCH. (a) TCHLoss (b) AssFailbyM ess = TASSFAIL[6 ,7,10,11,1 2,15] (c) AssFailOther (d) QueFail (e) AssFail
= AssAtt - AssSucc - TCHLoss - AssFailbyMess - QueFail
= NMSGDISQ[1 ,2] = TASSFAIL[6..8, 10..13,15] + NRCLRREQ[22]
Used param.: TASSFAIL [6,7,8,10,11,12,13,15], AssAtt (5.1(a)) , AssSucc (5.3(a)), NMSGDSIQ[1,2], NRCLRREQ[22] Elem. Object: Cell Unit: Remarks: None Directed Retries are not considered, because they are 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.
29
A50016-G5100-A042-1-7618
Information System
5.3 Number of successful Assignments

Long name: Short name: Description: (a) Number of successful Assignments (a) AssSucc 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)
AssSucc = TASSSUCC[2,3] + SINTHINT[7] + SUINBHDO[10 * n + 7] + SUOISHDO[10 * m + 7]

n =0 m =0 31 63
with n for the number of GSM neighbourcell relation (n=0..31) with m for the number of UMTS neighbourcell relation (m=0..63)
Used param.: TASSSUCC[2,3], SINTHINT[7], SUINBHDO[10 * n + 7], SUOISHDO[10 * m + 7] Elem. Object: Cell Unit: Remarks: None
Assignments of SDCCH are not considered. Intersystem Directed Retry to UMTS are considered
30
A50016-G5100-A042-1-7618
Information System
5.4 Assignment Failure Rate

Long name: (a) (b) (c) (d) (e) (a) (b) (c) (d) (e) TCH Blocking Rate Assignment Failure Rate by Message Assignment Failure Rate due to other Reason Queuing Failure Rate Assignment Failure Rate TCHBlockRate AssFailbyMessRate AssFailOtherRate QueFailRate AssFailRate
Short name:
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. (a) TCHBlockRate =
Formula:
TCHLoss AssAtt
AssFailbyMess AssAtt
(b) AssFailbyMessRate = (c) AssFailOtherRate = (d) QueFailRate =
AssFailOther AssAtt
QueFail AssAtt
(e) AssFailRate =
AssFail AssAtt
Used param.: AssAtt(5.1(a)), TCHLoss (5.2(a)), AssFailbyMess (5.2(b)), AssFailOther (5.2(c)), QueFail (5.2(d)), AssFail (5.2(d)), Elem. Object: Cell Unit: Remarks: None
Directed Retries are not considered, because they ares not related to assignment failures. Assignments of SDCCH are not considered
31
A50016-G5100-A042-1-7618
Information System
5.5 Assignment Success Rate

Long name: Short name: Description: (a) Assignment Success Rate (a) AssSuccRate 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. (a)
Formula:
AssSuccRate
AssSucc AssAtt
or 1 AssFailRate
Used param.: AssAtt(5.1(a)), AssSucc (5.3(a)), AssFailRate (5.4(e)) Elem. Object: Cell Unit: Remarks: None
Assignments of SDCCH are not considered. Inter System Directed Retry (e.g. UMTS) are also considered
5.6 Assignment success rate when radio resources available

Long name: Short name: Description: Formula: (a) Assignment success probability when radio resource available (a) SuccAssProbNoTCHBlocking This indicator provides the radio failures during the TCH assignment procedure
(a) SuccAssProbNoTCHBlocking = 1
AssFailbyMess AssAtt - TCHLoss
Used param.: AssAtt(5.1(a)), TCHLoss (5.2(a)), AssFailbyMess (5.2(b)) Elem. Object: Cell Unit Remarks: None 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
5.7 Mean Number of Repeated Assignment Requests

Long name: Short name: Description: Formula: (a) Mean number of repeated assignment requests (a) RepAssReq These indicators will give you the mean number of repeated Assignment procedures started by the MSC. (a)
RepAssReq
= AssAtt - (AssFail + AssSucc)
32
A50016-G5100-A042-1-7618
Information System
Elem. Object: Cell Unit: Remarks: None
Used param.: AssAtt(5.1(a)), AssSucc (5.3(a)), AssFail (5.2(e)),
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.
5.8 Repeated Assignment Request Rate

Long name: Short name: Description: Formula: (a) Repeated Assignment Request Rate (a) RepAssReqRate These indicators will give you the repeated Assignment Request Rate. (a) RepAssReqR ate
AssAtt AssFail + AssSucc
Used param.: AssAtt(5.1(a)), AssSucc (5.3(a)), AssFail (5.2(d)) Elem. Object: Cell Unit: Remarks: None None
5.9 Assignment Success Rate for receiver supporting ARP technology

Long name: Short name: Description: (a) Assignment Success Rate for ARP receiver (a) AssSuccRateARP This indicator will provide the Assignment Success Rate for receiver supporting the Advanced Receiver Performance (ARP) technology. The Assignment procedure is successful if the BSC returns an Assignment Complete message to the MSC. (a) AssSuccRateARP =
Formula:
NASSARP[1] SUCTCHARP [1,2]
Used param.: NASSARP[1], SUCTCHARP[1,2] Elem. Object: Cell Unit: Remarks: None
Assignments of SDCCH are not considered. Due to a lack of ARP specific counters for HO scenarios, output from this formula cannot be compared with output from the overall Assignment Success Rate formula AssSucc (5.5(a) ARP-type receivers will be a synonym for Single Antenna Interference Cancellation (SAIC) type receivers.
33
A50016-G5100-A042-1-7618
Information System
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 (6.3) CSSR Call Setup Success Rate BSS
(6.5) CSFR Call Setup Failure Rate Call Setup Failure Rate due to Immediate Assignment Losses Call Setup Failure Rate due to AGCH 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
34
A50016-G5100-A042-1-7618
Information System
6.1 Number of Call Setup Attempts

Long name: Short name: Description: Formula: (a) Number of Call Setup Attempts (a) CSAtt 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 (a) CSAtt =
ImmAssSuccCS ImmAssSuccRate
Used param.: ImmAssSuccCS (3.1a), ImmAssSuccRate (3.11) Elem. Object: Cell Unit: Remarks: None 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.
6.2 Number of Successful Call Setups

Long name: Short name: Description: Formula: (a) Number of Successful Call Setups (a) CSSucc 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. (a) CSSucc = AssSucc
Used param.: AssSucc (4.3a) Elem. Object: Cell Unit: Remarks: None Assignment of SDCCH are not considered
35
A50016-G5100-A042-1-7618
Information System
6.3 Call Setup Success Rate

Long name: Short name: Description: (a) Call Setup Success Rate (b) Call Setup Success Rate BSS (a) CSSuccRate (b) CSSuccRateBSS 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). (a) CSSuccRate = ImmAssSucc Rate * SSSProcSuc cRateCStot al * AssSuccRat e (b) CSSuccRateBSS = ImmAssSuccRate * ( 1 - SDCCHDropRateCS) * AssSuccRate Used param.: ImmAssSuccRate (3.11(a)), SSSProcSuccRateCStotal (4.6(b)), AssSuccRate (5.5(a)), SDCCHDropRateCS (4.4(a)) Elem. Object: Cell Unit: Remarks: None BR7: correction CSSuccRateBSS: factor (1-SDCCHDropRateCS) included in formula BR7: KPI CSSuccRateSSS cancelled (just another name for KPI SSSProcSuccRateCStotal (4.6(b)) Systematic errors can occur as described in the used KPIs.
Formula:
6.4 Number of Call Setup Failures

Long name: (a) (b) (c) (d) (e) (f) (g) (h) (i) (j) Short name: (a) (b) (c) (d) Number of Call Setup Failures Number of Call Setup Failures due to Immediate Assignment Losses Number of Call Setup Failures due to AGCH Blocking Number of Call Setup Failures due to Immediate Assignment without MS Seizure Number of Call Setup Failures due to SDCCH Drops Number of Call Setup Failures due to SSS Procedure Failure Number of Call Setup Failures due to TCH Loss Number of Call Setup Failures due to Assignment Failures by Message Number of Call Setup Failures due to Assignment Failures with other Reasons Number of Call Setup Failures due to Queuing Failures CSFail CSFailImmAssLoss CSFailAGCHLoss CSFailImmAssNoSeiz
36
A50016-G5100-A042-1-7618
Information System
(e) (f) (g) (h) (i) (j) Description: CSFailSDCCHDrop CSFailSSSProcFail CSFailTCHLoss CSFailAssFailbyMess CSFailAssFailOther CSFailQueFail
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). (a) (b) (c) (d) (e) (f) (g) (h) (i) (j) CSFail CSFailImmAssLoss CSFailAGCHLoss CSFailImmAssNoSeiz CSFailSDCCHDrop CSFailSSSProcFail CSFailTCHLoss CSFailAssFailbyMess CSFailAssFailOther CSFailQueFail = CSAtt - CSSucc = CSAtt * ImmAssLossRate = CSAtt * AGCHLossRateCS = CSAtt * ImmAssNoSeizRate = CSAtt * ImmAssSuccRate * SDCCHDropRateCS = CSAtt * ImmAssSuccRate * SSSProcFailRateCS = TCHLoss = AssFailbyMess = AssFailOther = QueFail
Formula:
Used param.: CSAtt (6.1(a)), CSSucc (6.2(a)), ImmAssLossRate(3.8(a)), AGCHLossRateCS(3.9(a)), ImmAssNoSeizRate(3.10(a)), ImmAssSuccRate (3.11(a)), SDCCHDropRateCS(4.4(a)), SSSProcFailRateCS(4.5(a)), TCHLoss(5.2(a)), AssFailbyMess(5.2(b)), AssFailOther(5.2(c)), QueFail(5.2(c)) Elem. Object: Cell Unit: Remarks: None See remarks in the referenced KPIs
37
A50016-G5100-A042-1-7618
Information System
6.5
Call Setup Failure Rate

(a) (b) (c) (d) (e) (f) (g) (h) (i) (j) (a) (b) (c) (d) (e) (f) (g) (h) (i) (j) Call Setup Failure Rate Call Setup Failure Rate due to Immediate Assignment Losses Call Setup Failure Rate due to AGCH Blocking 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 CSFailRate CSFailRateImmAssLoss CSFailRateAGCHLoss CSFailRateImmAssNoSeiz CSFailRateSDCCHDrops CSFailRateSSSProcFail CSFailRateTCHLoss CSFailRateAssFailbyMess CSFailRateAssFailOther CSFailRateQueFail
Long name:
Short name:
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). (a) (b) (c) (d) (e) (f) (g) (h) (i) (j) CSFailRate CSFailRateImmAssLoss CSFailRateAGCHLoss CSFailRateImmAssNoSeiz CSFailRateSDCCHDrops CSFailRateSSSProcFail CSFailRateTCHLoss CSFailRateAssFailbyMess CSFailRateAssFailOther CSFailRateQueFail = 1 CSSuccRate = ImmAssLossRate = AGCHLossRateCS = ImmAssNoSeizRate = SDCCHDropRateCS = SSSProcFailRateCS = TCHBlockRate = AssFailbyMessRate = AssFailOtherRate = QueFailRate
Formula:
Used param.: CSSuccRate (6.3(a)), ImmAssLossRate(3.8(a)), AGCHLossRateCS(3.9(a)), ImmAssNoSeizRate(3.10(a)), SDCCHDropRateCS(4.4(a)), SSSProcFailRateCS(4.5(a)), TCHBlockRate(5.4(a)), AssFailbyMessRate(5.4(b)), AssFailOtherRate(5.4(c)), QueFailRate(5.4(d)) Elem. Object: Cell Unit: Remarks: None See remarks in the referenced KPIs
38
A50016-G5100-A042-1-7618
Information System
TCH Drop related Performance Indicators

(a) Number of Dropped TCH Connections (a) TCHDrop 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) TCHDrop = NRCLRREQ[1.. 3, 5..12, 14 ..18] Observation of customer satisfaction
7.1 Number of Dropped TCH Connections

Long name: Short name: Description:
Formula: Use case:
Used param.: NRCLRREQ[1 .. 3, 5.. 12, 14 ..18] Elem. Object: Cell Unit: Remarks: None 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
39
A50016-G5100-A042-1-7618
Information System
7.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 (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 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. 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)
Short name:
Description: Use case:
40
A50016-G5100-A042-1-7618
Information System
Formula: (a) TCHDropDis t.T200 =

NRFLTCH[1, 10,19,28] TCHDrop
(b) TCHDropDist.UnsolDMRes = (c) TCHDropDist.SeqErr =
NRFLTCH[3,12,21,30] TCHDrop NRFLTCH[4, 13,22,31] TCHDrop
t.TMSRFPCI = (d) TCHDropDis

(e) TCHDropDist.Distance = (f) TCHDropDist.HOAccess= (g) TCHDropDist.RadLinkFail = (h) TCHDropDist.RemTranscFail =
NRFLTCH[5, 14,23,32] TCHDrop NRFLTCH[6, 15,24,33] TCHDrop

NRFLTCH[7,16,25,34] TCHDrop
NRFLTCH[8,17,26,35] TCHDrop
t.ConnOthe = r (i) TCHDropDis

(j) TCHDropDist.IntraCellHO = (k) TCHDropDist.InterCellHO = (l) TCHDropDist.InterBSCHO = (m) TCHDropDist.EquipFail = (n) TCHDropDis t.ProtErr = (o) TCHDropDis t.DistErr = (p) TCHDropDis t.Preempt = (q) TCHDropDis t.OAM = (r) TCHDropDis t.Other =

UNIHIALC[1 ] TCHDrop UNIHIRLC[1 ] TCHDrop
InterBSCHO Drop TCHDrop
NRCLRREQ[1 ,10] TCHDrop
NRCLRREQ[5 ,14] TCHDrop
NRCLRREQ[6 ,15] TCHDrop NRCLRREQ[7 ,16] TCHDrop NRCLRREQ[8 ,17] TCHDrop NRCLRREQ[9 ,18] TCHDrop
Used param.: NRFLTCH[1..36], UNIHIALC[1], UNIHIRLC[1], TCHDrop(7.1(a)), NRCLRREQ [1..18] Elem. Object: Cell Unit: Remarks: None
InterBSCHODrop(0(a)),
Handover Access failures are included in formulas TCHDropDist.HOAccess and
41
A50016-G5100-A042-1-7618
Information System

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.
42
A50016-G5100-A042-1-7618
Information System
7.3 TCH Drop Rate

Long name: Short name: Description: (a) TCH Drop Rate (a) TCHDropRate 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 (a) TCHDropRate =
TCHDrop SUCTCHSE[1..2]
Formula:
Used param.: TCHDrop(7.1(a)), SUCTCHSE[1..2] Elem. Object: Cell Unit: Remarks: None 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.
43
A50016-G5100-A042-1-7618
Information System
7.4 Call Drop Rate

Long name: Short name: Description: (a) Number of terminated calls (b) Call Drop Rate (a) NumTermCalls (b) CallDropRate 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) NumTermCalls = NRCLRCMD[1.. 2, 4 .. 8, 10 ..12] - NRCLRREQ[4,13] - TASSFAIL[6.. 8,11..13] (b) CallDropRate =
TCHDrop NumTermCalls
Used param.: TCHDrop(7.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: Remarks: None 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
44
A50016-G5100-A042-1-7618
Information System

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.
45
A50016-G5100-A042-1-7618
Information System
7.5 Mean Time between TCH Drop

Long name: Short name: Description: Formula: (a) Mean Time between TCH Drop (a) MTBTCHDrop 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. (a) MTBTCHDrop =
TCHTrafCarrDR * Granularity * 60s TCHDrop
Used param.: TCHDrop(7.1(a)), TCHTrafCarrDR(9.1.4(c)), Granularity in minutes Elem. Object: Cell Unit: Remarks: Seconds SDCCH Handovers are not considered and can therefore lead to systematic errors.
7.6 TCH Drops per Erlanghour

Long name: Short name: Description: Formula: (a) TCH Drops per Erlanghour (a) TCHDropErlh This indicator will give you TCH Drops per Erlanghour, by meaning the number of losses of TCH connections related to one Erlanghour. (a) TCHDropErlh =
TCHDrop 60 * TCHTrafCarrDR Granularity
Used param.: TCHDrop(7.1(a)), TCHTrafCarrDR(9.1.4(c)), Granularity in minutes Elem. Object: Cell Unit: Remarks: None SDCCH Handovers are not considered and can therefore lead to systematic errors.
7.7 Rate of normal call releases of calls with bad radio quality
Long name: (a) (b) (c) (d) (e) (f) Rate of normal call releases of calls with bad radio quality Rate of normal call releases of calls with bad radio quality, non AMR Rate of normal call releases of calls with bad radio quality, AMR Rate of normal call releases of calls with bad radio quality, non AMR, MS orig. Rate of normal call releases of calls with bad radio quality, AMR, MS orig. Rate of normal call releases of calls with bad radio quality, non AMR, Network orig.
46
A50016-G5100-A042-1-7618
Information System
Short name: (a) (b) (c) (d) (e) (f) (g)

(g) Rate of normal call releases of calls with bad radio quality, AMR, Network orig. BRQCRelRate BRQCRelRateNonAMR BRQCRelRateAMR BRQCRelRateNonAMRMsOrg BRQCRelRateAMRMsOrg BRQCRelRateNonAMRNwOrg BRQCRelRateAMRNwOrg
This KPI will give you the number of normal call releases of calls with bad radio quality in relation to all TCH connections of a cell. (a) BRQCRelRate =
NCRLBRQU[1..4] SUCTCHSE[1 ,2] NCRLBRQU[1,3] SUCTCHSE[1 ,2]
(b) BRQCRelRateNonAMR = (c) BRQCRelRateAMR =
NCRLBRQU[2,4] SUCTCHSE[1 ,2] NCRLBRQU[1] SUCTCHSE[1 ,2]
(d) BRQCRelRateNonAMRMsOrg = (e) BRQCRelRateAMRMsOrg =
NCRLBRQU[2] SUCTCHSE[1 ,2] NCRLBRQU[3] SUCTCHSE[1 ,2]
(f) BRQCRelRateNonAMRNwOrg = (g) BRQCRelRateAMRNwOrg =
NCRLBRQU[4] SUCTCHSE[1 ,2]
Used param.: NCRLBRQU[1..4], SUCTCHSE[1,2] Elem. Object: Cell Unit: Remarks: None None
7.8 Rate of TCH Drops and normal call releases of calls with bad radio quality
Long name: Short name: Description: Formula: (a) TCH drops by bad radio quality call release rate (a) TCHDropBRQCRelRat This indicator gives the percentage of all TCH drops and normal call releases of calls with bad radio quality related to TCH connections. (a) TCHDropBRQ CRelRat =
NRCLRREQ[1..3,5..12,14..18] + NCRLBRQU[1..4] SUCTCHSE[1 ,2]
Used param.: NRCLRREQ[1..3, 5..12, 14..18], NCRLBRQU[1..4], SUCTCHSE[1,2] Elem. Object: Cell Unit: None
47
A50016-G5100-A042-1-7618
Information System
Remarks:

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).
48
A50016-G5100-A042-1-7618
Information System
SDCCH Drop related Performance Indicators

(a) Number of dropped SDCCH Connections (a) SDCCHDrop This indicator will give you the number of dropped SDCCH Connections, which can occur for any call type (MOC, MTC, Locupd, SMS, ...). (a) SDCCHDrop = NRCLRREQ[19 .. 21, 23 .. 26] + TASSFAIL[1 ,6,11]
8.1 Number of dropped SDCCH Connections

Long name: Short name: Description: Formula:
Used param.: NRCLRREQ[19 .. 21, 23 .. 26], TASSFAIL[1,6,11] Elem. Object: Cell Unit: Remarks: None This KPI is based on NRCLRREQ counters, because drops caused by the BSC must be considered.
8.2 SDCCH Drop Rate

Long name: Short name: Description: Formula: (a) SDCCH Drop Rate (b) SDCCH Drop Rate per SDCCH connection (a) SDCCHDropRate (b) SDCCHDropConnRate This indicator will give you the rate of all losses of connections during a SDCCH Connection. (a) SDCCHDropRate =
SDCCHDrop NSUCCHPC[1..6] SDCCHDrop NRCLRCMD[13,14,16..18]
(b) SDCCHDropConnRate =
Used param.: SDCCHDrop(8.1(a)), NSUCCHPC[1..6], NRCLRCMD[13,14,16..18] Elem. Object: Cell Unit: Remarks: None 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.
49
A50016-G5100-A042-1-7618
Information System
8.3 Mean Time between SDCCH Drop

Long name: Short name: Description: Formula: (a) (a) Mean Time between SDCCH Drop (a) MTBSDCCHDrop 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.
MTBSDCCHDrop =
SDCCHTrafCarr * Granularity * 60s SDCCHDrop
Used param.: SDCCHDrop(8.1(a)), SDCCHTrafCarr(10.1.2(a)) , Granularity in minutes Elem. Object: Cell Unit: Remarks: Seconds SDCCH Handovers Drops are not considered.
8.4 SDCCH Drops per Erlanghour

Long name: Short name: Description: Formula: (a) SDCCH Drops per Erlanghour (a) SDCCHDropErlh This indicator will give you SDCCH Drops per Erlanghour, by meaning the number of losses of SDCCH connections related to one Erlang. (a) SDCCHDropE rlh =
SDCCHDrop 60 * SDCCHTrafC arr Granularit y
Used param.: SDCCHDrop(8.1(a)), SDCCHTrafCarr(10.1.2(a)), Granularity in minutes Elem. Object: Cell Unit: Remarks: None SDCCH Handovers Drops are not considered.
50
A50016-G5100-A042-1-7618
Information System
TCH Load related Performance Indicators
9.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 Traffic Carried Y [Erl Calls Carried CC
Number of channels N
Traffic Lost R [Erl] Calls Rejected CR Loss B [%] Fig. 6 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.
9.1.1 TCH Traffic Distribution Rate

Long name: Short name: Description: Formula: (a) TCH Full Rate Traffic (b) TCH Half Rate Traffic (a) FRT (b) HRT This indicator will give you the Rate of Full Rate and Half Rate traffic on TCH compared to the total traffic. (a) FRT = (b) HRT =
MEBUSTCH [1, 3] MEBUSTCH [1..4] MEBUSTCH [2, 4] MEBUSTCH [1..4]
Used param.: MEBUSTCH[1..4] Elem. Object: Cell Unit: Remarks: None This KPI can be used by network planning to calculate the number of needed TRX.
51
A50016-G5100-A042-1-7618
Information System
9.1.2 TCH Loss Rate

Long name: (a) (b) (c) (d) (e) (f) (g) (a) (b) (c) (d) (e) (f) (g) TCH seizure blocked Rate Full Rate TCH seizure blocked Rate Half Rate TCH seizure blocked Rate Dual Rate TCH seizure blocked Rate Waiting System Full Rate TCH seizure blocked Rate Waiting System Half Rate TCH seizure blocked Rate Waiting System Dual Rate TCH seizure blocked Rate TCHSeizBlckRateFR TCHSeizBlckRateHR TCHSeizBlckRateDR TCHSeizBlckRateWSFR TCHSeizBlckRateWSHR TCHSeizBlckRateWSDR TCHSeizBlckRate
Short name:
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. (a) TCHSeizBlckRateFR =
Formula:
ATCHSMBS [1, 3, 5] ATTCHSEI [1] ATCHSMBS [2, 4, 6] ATTCHSEI [2]
ATCHSMBS[5] is only used by Concentric or Extended cells.
(b) TCHSeizBlckRateHR =
ATCHSMBS[6] is only used by Concentric or Extended cells.
(c) TCHSeizBlckRateDR =
ATCHSMBS [all] ATTCHSEI [1,2]
(d) TCHSeizBlckRateWSFR = (e) TCHSeizBlckRateWSHR = (f) TCHSeizBlckRateWSDR = (g) TCHSeizBlc kRate =
NMSGDISQ [1, 3] ATTCHSEI [1] NMSGDISQ [2,4] ATTCHSEI [2] NMSGDISQ [1..4] ATTCHSEI [1..2]
ATCHSMBS[a ll] + NMSGDISQ [1..4] ATTCHSEI [1..2]
52
A50016-G5100-A042-1-7618
Information System
Elem. Object: Cell Unit: Remarks:
Used param.: ATCHSMBS[1..6], ATTCHSEI[1..2], NMSGDISQ[1..4] Subscriber redial behaviour influences the blocking rate. Further the HO periodicity timer influences the TCH blocking rate 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.
9.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 (a) TCHTrafOffFR (b) TCHTrafOffHR (c) TCHTrafOffDR 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. 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 6.5 (g): Call Setup Failure Rate due to TCH Loss)
Short name:
Description:
Use case:
Formula:
MEBUSTCH [1, 3] 1 - TCHSeizBlckRateFR MEBUSTCH [2, 4] (b) TCHTrafOffHR = 1 - TCHSeizBlckRateHR (c) TCHTrafOffDR = TCHTrafOffFR + TCHTrafOffHR
(a) TCHTrafOffFR =
Used param.: MEBUSTCH[1..4] ,TCHSeizBlckRateFR(9.1.2(a)),TCHSeizBlckRateHR(9.1.2(b)) Elem. Object: Cell Unit: Remarks: Erlang None
53
A50016-G5100-A042-1-7618
Information System
9.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 (a) TCHTrafCarrFR (b) TCHTrafCarrHR (c) TCHTrafCarrDR This indicator will give you the amount of carried traffic in Erlang on TCH. (a) TCHTrafCarrFR = MEBUSTCH [1, 3] (b) TCHTrafCarrHR = MEBUSTCH [2, 4] (c) TCHTrafCarrDR = TCHTrafCarrFR + TCHTrafCarrHR Used param.: MEBUSTCH[1..4] Elem. Object: Cell Unit: Remarks: Erlang None
Short name:
54
A50016-G5100-A042-1-7618
Information System
9.1.5 TCH Traffic Lost

Long name: (a) (b) (c) (d) (e) (f) (a) (b) (c) (d) (e) (f) TCH Traffic Lost Full Rate TCH Traffic Lost Half Rate TCH Traffic Lost Dual Rate TCH Traffic Lost Waiting System Full Rate TCH Traffic Lost Waiting System Half Rate TCH Traffic Lost Waiting System Dual Rate TCHTrafLostFR TCHTrafLostHR TCHTrafLostDR TCHTrafLostWSFR TCHTrafLostWSHR TCHTrafLostWSDR
Short name:
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) TCHTrafLostFR = TCHTrafOffFR - TCHTrafCarrFR (b) TCHTrafLostHR = TCHTrafOffHR - TCHTrafCarrHR (c) TCHTrafLos tDR = TCHTrafOff DR - TCHTrafCar rDR
, (d) TCHTrafLostWSFR = NMSGDISQ[13] *

(e) TCHTrafLostWSHR = NMSGDISQ[2,4] * (f)
TCHMHTFR Granularity * 60s
TCHMHTHR Granularity * 60s TCHMHTDR Granularit * 60s y
TCHTrafLos tWSDR = NMSGDISQ[1 ..4] *
Used param.: TCHTrafOffFR(9.1.3(a)), TCHTrafOffHR(9.1.3(b)), TCHTrafOffDR(9.1.3(c)), TCHTrafCarrFR(9.1.4(a)), TCHTrafCarrHR(9.1.4(b)), TCHTrafCarrDR(9.1.4(c)) NMSGDISQ[1..4], TCHMHTFR (9.1.7(a)), TCHMHTHR(9.1.7(b)), TCHMHTDR(9.1.7(c)), Elem. Object: Cell Unit: Remarks: Erlang None
55
A50016-G5100-A042-1-7618
Information System
9.1.6 TCH Occupied Rate

Long name: (a) TCH Occupied Rate Full Rate (b) TCH Occupied Rate Half Rate (c) TCH Occupied Rate Dual Rate (a) TCHOccRateFR (b) TCHOccRateHR (c) TCHOccRateDR This indicator will give you the TCH Blocking Rate by meaning the rate were all traffic channels were occupied. (a) TCHOccRateFR =
AALTCHTI[1] Granularity * 60s
Short name:
(b) TCHOccRateHR =
AALTCHTI[4] Granularity * 60s
(c) TCHOccRateDR = TCHOccRateFR * FRT + TCHOccRateHR * HRT Used param.: AALTCHTI[1,4], FRT(9.1.1(a)), HRT(9.1.1(b)), Granularity in Minutes Elem. Object: Cell Unit: Remarks: None For Dual Rate Channels (formula c) the Full Rate and Half be weighted with the TCH Traffic distribution Rate. Due Channel Modification the measurement type AALTCHTI number of timeslots belonging to the TCH_Pool, SDCCH_Backup Pool. Rate channels must to feature Smooth keeps track of the TCH/SD_Pool and
56
A50016-G5100-A042-1-7618
Information System
9.1.7
TCH Mean Holding Time

(a) TCH Mean Holding Time Full Rate (b) TCH Mean Holding Time Half Rate (c) TCH Mean Holding Time Dual Rate (a) TCHMHTFR (b) TCHMHTHR (c) TCHMHTDR This indicator will give you the mean holding Time in seconds for occupied TCHs in a cell. (a) TCHMHTFR = (b) TCHMHTHR = (c) TCHMHTDR =
MEBUSTCH[1,3] * Granularity * 60 TNTCHCL [1, 3] MEBUSTCH[2,4] * Granularity * 60 TNTCHCL [2, 4]
MEBUSTCH[1..4] * Granularity * 60 TNTCHCL [1..4]
Long name:
Short name:
Used param.: MEBUSTCH[1..4], TNTCHCL[1..4], Granularity in minutes Elem. Object: Cell Unit: Remarks: Seconds A weighting with the TCH Traffic distribution Rate is not necessary here, because Erlang values are used.
57
A50016-G5100-A042-1-7618
Information System
9.1.8 TCH Traffic Utilization

Long name: (a) (b) (c) (d) (e) (f) (a) (b) (c) (d) (e) (f) 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 TCHTrafUtilFR TCHTrafUtilHR TCHTrafUtilDR TCHTrafUtilFRErl TCHTrafUtilHRErl TCHTrafUtilDRErl
Short name:
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:
TCHTrafUti = lFR
MEBUSTCH[1 ,3] NRDEFTCH[2 ,8]

MEBUSTCH[2 ,4] NRDEFTCH[5 ,11]
TCHTrafUti lHR =
TCHTrafUti lDR =
MEBUSTCH[1..4] NRDEFTCH[2,5,8,11]
TCHTrafUti lFRErl=
MEBUSTCH[1 ,3] A
Erlang B formula: A = f(N, B) = f(NRDEFTCH[2,8], B) Erlang C formula:
A = f(N, B, Ql, Qd) = f(NRDEFTCH [2,8], B, MTCHQLEN[1 MDURTCRQ[1 ], ])
TCHTrafUtilHRErl =
Erlang B formula:
MEBUSTCH[2,4] A
A = f(N, B) = f(NRDEFTCH[5,11], B)
Erlang C formula A = f(N, B, Ql, Qd) = f(NRDEFTCH[5,11], B, MTCHQLEN[2], MDURTCRQ[2])
TCHTrafUti lDRErl =
Erlang B formula:
MEBUSTCH[1 ..4] A
A = f(N, B) = f(NRDEFTCH[2,5,8,11], B)
Erlang C formula:
A = f(N, B, Ql, Qd) = f(NRDEFTCH [2,5,8,11] , B, MTCHQLEN[1 ,2], MDURTCRQ[1 ,2])
58
A50016-G5100-A042-1-7618
Information System
with A B

= Offered Load in Erlang = Blocking Probability (Planning Parameter)
Used param.: MEBUSTCH[1..4], NRDEFTCH [2,5,8,11], MTCHQLEN[1,2], MDURTCRQ[1,2] Elem. Object: Cell Unit: Remarks: None 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.
59
A50016-G5100-A042-1-7618
Information System
9.2 Combined time slot utilization for CS and PO Traffic

9.2.1 Combined time slot occupation rate for CS and PO Traffic
Long name: Short name: Description: (a) Mean overall time slot occupation rate for CS and PO Traffic (a) MeaOcTsC 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. (a) MeaOcTsC =
max{NALLPD CH [3], NALLPDCH [6]} + MEBUSTCH [1,3] + MEBUSTCH [2,4]/2 + MBUSYSDC [1]/8 NDEFPDCH[3 ] + NRDEFTCH[3 ,9] + NRDEFTCH[6 ,12] / 2 + NDFTCHSD[1 ] + NDESDCCH[3 ]/8
Formula:
Used param.: NDEFPDCH[3]: NALLPDCH [3,6]:
number of defined PDCH, 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]: MBUSYSDC [1]: Elem. Object: Cell Unit: Remarks: None NALLPDCH: Mean number of active TBF PDCH Term NALLPDCH[3,6] leads to a systematic error, since the same PDCH can carry a DL and an UL TBF at the same time. NDEFPDCH: Number of defined PDCH NDEFPDCH include also the packet channels used as PBCCH and PCCCH; traffic is counted in NALLPDCH too. Mean Number of busy TCHs [1,3] full rate, [2,4] half rate (1/2 time slot) Mean Number of busy SDCCHs (1/8 time slots)
60
A50016-G5100-A042-1-7618
Information System
9.2.2 Combined time slot availability rate for CS and PO Traffic

Long name: Short name: Description: (a) Mean overall time slot availability rate for CS and PO Traffic (a) MeaAvTsC 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. (a) MeaAvTsC =
NAVPDCH[3] + NAVTCH[3,9] + NAVTCH[6,12] /2 + NAVSDCCH[3]/8 NDEFPDCH[3] + NRDEFTCH[3,9] + NRDEFTCH[6,12] / 2 + NDFTCHSD[1] + NDESDCCH[3]/8
Formula:
Used param.: NDEFPDCH[3]: NAVPDCH[3]:
number of defined PDCH, 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]: NAVSDCCH[3]: NDFTCHSD[1]: NAVTCHSD[3]: Elem. Object: Cell Unit: Remarks: None None mean number of defined SDCCHs (1/8 time slots) mean number of available SDCCHs (1/8 time slots) mean number of defined TCH/SD mean number of available TCH/SD
61
A50016-G5100-A042-1-7618
Information System
10 DCCH related Performance Indicators

The dedicated control channels DCCH consist of a set of logical channels. The DCCH are bidirectional.
SDCCH DCCH Dedicated Control Channels
Stand Alone DCCH
Call setup, location update and IMSI attach/detach Exchange immediately signaling data Measurement values MS -> BTS
FACCH
Fast Associated Control Channel
SACCH
Slow Associated Control Channel
Fig. 7 Overview Dedicated Control Channels
10.1 SDCCH Load related Performance Indicators

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 Carried Y [Eel] Calls Carried CC
Traffic Lost [Erl] Calls Rejected CR Loss B
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.
62
A50016-G5100-A042-1-7618
Information System
10.1.1 SDCCH Traffic Offered

Long name: Short name: Description: Formula: (a) SDCCH Traffic Offered (a) SDCCH TrafOff This indicator will give you the amount of traffic in Erlang on SDCCH the MS subscribers wanted to have due to the traffic theorie. (a) SDCCHTrafOff =
MBUSYSDC [1] 1 - SDCCHBlockRate
Used param.: MBUSYSDC[1], SDCCHBlockRate (10.1.5(a)) Elem. Object: Cell Unit: Remarks: Erlang None
10.1.2 SDCCH Traffic Carried

Long name: Short name: Description: Formula: (a) SDCCH Traffic Carried (a) SDCCH TrafCarr This indicator will give you the amount of carried traffic in Erlang on SDCCH. (a) SDCCHTrafCarr = MBUSYSDC [1]
Used param.: MBUSYSDC[1] Elem. Object: Cell Unit: Remarks: Erlang None
10.1.3 SDCCH Traffic Lost

Long name: Short name: Description: Formula: (a) SDCCH Traffic Lost (a) SDCCHTrafLost This indicator will give you the amount of traffic in Erlang on SDCCH which were lost (e.g. Blockings). (a) SDCCHTrafLost = SDCCHTrafOff - SDCCHTrafCarr
Used param.: SDCCHTrafOff(10.1.1(a)), SDCCHTrafCarr(10.1.2(a)) Elem. Object: Cell Unit: Remarks: Erlang None
63
A50016-G5100-A042-1-7618
Information System
10.1.4 SDCCH Occupied Rate

Long name: Short name: Description: Formula: (a) SDCCH Occupied Rate (a) SDCCHOccRate This indicator will give you the SDCCH Blocking Rate by meaning the rate where all SDCCH were occupied. (a) SDCCHOccRa te =
ASDCALTI [1] Granularit y * 60s
Used param.: ASDCALTI[1], Granularity in minutes Elem. Object: Cell Unit: Remarks: None 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.
10.1.5 SDCCH Block Rate

Long name: Short name: Description: (a) SDCCH Block Rate (a) SDCCHBlockRate 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. (a) SDCCHBlockRate =
Formula: Used param.: Elem. Object: Unit: Remarks:
ATSDCMBS [1] NATTSDPE [1]
ATSDCMBS[1], NATTSDPE[1] Cell None None
10.1.6 SDCCH Mean Holding Time

Long name: Short name: Description: Formula: (a) SDCCH Mean Holding Time (a) SDCCHMHT This indicator will give you the mean holding Time in seconds for occupied SDCCH in a cell. (a) SDCCHMHT =
MBUSYSDC [1] * Granularity * 60s NSUCCHPC[1..6]
Used param.: MBUSYSDC[1], NSUCCHPC[1..6], Granularity in minutes
64
A50016-G5100-A042-1-7618
Information System
Elem. Object: Cell Unit: Remarks: Seconds None
65
A50016-G5100-A042-1-7618
Information System
10.1.7 SDCCH Traffic Utilisation

Long name: Short name: Description: SDCCH Traffic Utilisation SDCCH Traffic Utilisation based on Erlang formula SDCCHTrafUtil SDCCHTrafUtilErl 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. (a) SDCCHTrafUtil =
Formula:
MBUSYSDC[1] NDESDCCH[2]
MBUSYSDC[1 ] A
(b) SDCCHTrafU tilErl = Erlang B formula:
A = f(N, B) = f(NDESDCCH[2], B)
with A = Offered Load in Erlang B = Blocking Probability (Planning Parameter) Used param.: Elem. Object: Unit: Remarks: MBUSYSDC[1], NDESDCCH[2] Cell None None
66
A50016-G5100-A042-1-7618
Information System
10.2 FACCH related Performance Indicators

10.2.1 FACCH Repetition Rate
Long name: Short name: Description: (a) FACCH Repetition Rate (a) FACCHRR This indicator will give you the rate of transmitted I(ASSHOCMD) and UI(PHYS_INFO) frames versus the number of transmitted FACCH-blocks used to send over the radio interface the I(ASSHOCMD) and UI(PHYS_INFO) frames. (a) FACCHRR(k) = 1
Formula:
FACCHSUP [k] FACCHSUP[k + 5]
with k 1,,5 defines the used codec types: TCH/AFS, TCH/AHS, TCH/EFS, TCH/FS, TCH/HS. Used param.: FACCHSUP[all] Elem. Object: Cell Unit: Remarks: % None
67
A50016-G5100-A042-1-7618
Information System
11 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:
UL CCCH Common Control Channels RACH
Random Access Channel
MS requests a dedicated channel from network answer to RACH, dedicated signaling channel allocation paging of a MS in a location area (MTC) paging of MSs in a voice group call area
AGCH DL
Access Grant Channel
PCH
Paging Channel
NCH
Notification Channel
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: FCCH + SCH + BCCH + CCCH + 4 (SDCCH + SACCH) The timeslot will then run in the 51-Multiframe organization:
MBCCHC
68
A50016-G5100-A042-1-7618
Information System
1. 2.
F S 0 1 F S 0 1 BCCH 2 3 4 5 BCCH 2 3 4 5
CCCH F S CCCH CCCH F S SDCCH0 SDCCH1 F S SDCCH2 SDCCH3 F S SACCH0 SACCH1 I 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 CCCH F S CCCH CCCH F S SDCCH0 SDCCH1 F S SDCCH2 SDCCH3 F S SACCH2 SACCH3 I 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
downlink BCCH + CCCH + 4 SDCCH / 4, F = FCCH, S = SCH
1. 2.
SDCCH3 0 1 2 3 SDCCH3 0 1 2 3
R R SACCH2 4 5 6 7 8 9 R R SACCH0 4 5 6 7 8 9
SACCH3 R R R R R R R R R R R R R R R R R R R R R R R SDCCH0 SDCCH1 R R SDCCH2 10 11 1213 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 SACCH1 R R R R R R R R R R R R R R R R R R R R R R R SDCCH0 SDCCH1 R R SDCCH2 10 11 1213 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
uplink R = RACH + SDCCH / 4
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.
69
A50016-G5100-A042-1-7618
Information System
11.1 PCH load of downlink CCCH channels

Long name: Short name: Description: PCH load of downlink CCCH channels 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.
Formula:
CCCHLDPCH =
Number of accessed PCH frames downlink Number of all defined CCCH frames downlink NTDMPCH[5]
CCCHLDPCH =
NDEFCCCH[2]
Used param.: NTDMPCH[5], NDEFCCCH[2] Elem. Object: Cell Unit: Remarks: None None
11.2 AGCH load of downlink CCCH channels

Long name: Short name: Description: AGCH load of downlink CCCH channels 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.
Formula:
CCCHLDAGCH = CCCHLDAGCH =
Number of accessed AGCH frames downlink Number of all defined CCCH frames downlink NTDMAGCH[1,2] NDEFCCCH[2]
Used param.: NTDMAGCH[1,2], NDEFCCCH[2] Elem. Object: Cell Unit: Remarks: None None
70
A50016-G5100-A042-1-7618
Information System
11.3 CCCH load downlink

Long name: Short name: Description: CCCH load downlink 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.
Formula:
CCCHLDDL = CCCHLDDL =
Number of accessed CCCH frames downlink Number of all defined CCCH frames downlink NTDMPCH[5]+ NTDMAGCH[1,2] NDEFCCCH[2]
Used param.: NTDMPCH[5], NTDMAGCH[1,2], NDEFCCCH[2] Elem. Object: Cell Unit: Remarks: 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.
11.4 CCCH load uplink

Long name: Short name: Description: CCCH load uplink 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.
Formula:
CCCHLDUL = CCCHLDUL =
Number of received RACH frames uplink Number of all defined CCCH frames uplink NACSUCPR[3] + NINVRACH[1,2,3] NDEFCCCH[1]
Used param.: NACSUCPR[3], NINVRACH[1,2,3], NDEFCCCH[1] Elem. Object: Cell Unit: Remarks: None None
71
A50016-G5100-A042-1-7618
Information System
11.5 PCH Loss Rate

Long name: Short name: Description: PCH Loss Rate PCHLossRate 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.
PCHLossRat e = NTDMPCH[3, 4] NTDMPCH [1 .. 4 ]
Formula:
Used param.: NTDMPCH[1..4] Elem. Object: Cell Unit: Remarks: None None
11.6 AGCH Loss Rate

Long name: Short name: Description: AGCH Loss Rate 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.
AGCHLossRa te = NTDMAGCH[3 ,4] NTDMAGCH [1 .. 4 ]
Formula:
Used param.: NTDMAGCH[1..4] Elem. Object: Cell Unit: Remarks: None None
72
A50016-G5100-A042-1-7618
Information System
11.7 Invalid RACH Rate

Long name: Short name: Description: Invalid RACH Rate 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.
InvRACHRat e = NINVRACH[1 ..3] NINVRACH [1 .. 3] + NACSUCPR [ 3]
Formula:
Used param.: NINVRACH[1..3], NACSUCPR[3] Elem. Object: Cell Unit: Remarks: None 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'.
73
A50016-G5100-A042-1-7618
Information System
12 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:
UL PCCCH Packet Common Control Channels PRACH
Packet Random Access Channel
GPRS-MS access request for UL packet data transmission answer to PRACH, dedicated signaling channel allocation paging of a GPRSMS in a location area (MTC) notification for GPRS-MSs for PtM transaction
PAGCH DL
Packet Access Grant Channel
PPCH
Packet Paging Channel
PNCH
Packet Notification Channel
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:
74
A50016-G5100-A042-1-7618
Information System
0 1 2 3 4 5 6 7 8 9 10 11

PDCH with the 52-Multiframe Structure
13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50
Block 0 Block 1 Block 2 T Block 3 Block 4 Block 5 I Block 6 Block 7 Block 8 T Block 9 Block 10 Block 11 I A A TA Timing Advance control frame I Search frame for measurements
Example for a PCCCH Configuration

BSPBBLK = 2 (PBCCH blocks)
9 10 11
Available Paging Blocks
BPAGCHR = 3 (no paging on these blocks)
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.
75
A50016-G5100-A042-1-7618
Information System
12.1 PPCH load of downlink PCCCH channels

Long name: Short name: Description: PPCH load of downlink PCCCH channels 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.
Formula:
PCCCHLDPPCH = PCCCHLDPPCH =
Number of accessed PPCH frames downlink Number of all defined PCCCH frames downlink NTDMPPCH[1,2] NDEFPCCC[2]
Used param.: NTDMPPCH[1,2], NDEFPCCC[2] Elem. Object: Cell Unit: Remarks: None None
12.2 PAGCH load of downlink PCCCH channels

Long name: Short name: Description: PAGCH load of downlink PCCCH channels 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.
Formula:
PCCCHLDPAGCH = PCCCHLDPAGCH =
Number of accessed PAGCH frames downlink Number of all defined PCCCH frames downlink NTDMPAGC[1,2] NDEFPCCC[2]
Used param.: NTDMPAGC[1,2], NDEFPCCC[2] Elem. Object: Cell Unit: Remarks: None None
76
A50016-G5100-A042-1-7618
Information System
12.3 PCCCH load downlink

Long name: Short name: Description: PCCCH load downlink 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.
Formula:
PCCCHLDDL = PCCCHLDDL =
Number of accessed PCCCH frames downlink Number of all defined PCCCH frames downlink NTDMPPCH[1,2] + NTDMPAGC[1,2] NDEFPCCC[2]
Used param.: NTDMPPCH[1,2], NTDMPAGC[1,2], NDEFPCCC[2] Elem. Object: Cell Unit: Remarks: None 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
12.4 PCCCH load uplink

Long name: Short name: Description: PCCCH load uplink 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.
Formula:
PCCCHLDUL = PCCCHLDUL =
Number of received PRACH frames uplink Number of all defined PCCCH frames uplink NSAPRACH[1] NDEFPCCC[1]
Used param.: NSAPRACH[1], NDEFPCCC[1] Elem. Object: Cell Unit: Remarks: None 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.
77
A50016-G5100-A042-1-7618
Information System
12.5 PPCH Loss Rate

Long name: Short name: Description: PPCH Loss Rate PPCHLossRate 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.
PPCHLossRa te = NTDMPPCH[3 ,4] NTDMPPCH [1 .. 4 ]
Formula:
Used param.: NTDMPPCH[1..4] Elem. Object: Cell Unit: Remarks: None None
12.6 PAGCH Loss Rate

Long name: Short name: Description: PAGCH Loss Rate 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.
PAGCHLossR ate = NTDMPAGC[2 ] NTDMPAGC [1 .. 2 ]
Formula:
Used param.: NTDMPAGC[1..2] Elem. Object: Cell Unit: Remarks: None None
78
A50016-G5100-A042-1-7618
Information System
12.7 Invalid PRACH Rate

Long name: Short name: Description: Invalid PRACH Rate 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. (a) InvPRACHRa te =
Formula:
NSAPRACH [ 2 .. 4 ] NSAPRACH[1 ..4]
Used param.: NSAPRACH[1..4] Elem. Object: Cell Unit: Remarks: None 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'.
79
A50016-G5100-A042-1-7618
Information System
13 Service related Performance Indicators

13.1 Total number of Service Requests
Long name: Short name: Description: Formula: (a) Total number of service requests (a) ServRequests This indicator provides the total number of Service requests including all service types, triggered by CHANNEL ALLOCATION REQUEST. (a) ServRequests = CHALNHLY[19..27]
Used param.: CHALNHLY[19..27] Elem. Object: BTS Unit Remarks: None None
13.2 Service Request Distribution Rate

Long name: (a) (b) (c) (d) (e) (f) (g) (h) (i) (a) (b) (c) (d) (e) (f) (g) (h) (i) SDCA Distribution for Signaling (SDCCH) SDCA Distribution for CS speech SDCA Distribution for CS speech AMR FR SDCA Distribution for CS speech AMR HR SDCA Distribution for CS data SDCA Distribution for HSCSD SDCA Distribution for GPRS SDCA Distribution for EGPRS SDCA Distribution for ASCI SDCADistSignal SDCADistCS SDCADistAMRFR SDCADistAMRHR SDCADistCSData SDCADistHSCSD SDCADistGPRS SDCADistEGPRS SDCADistASCI
Short name:
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. (a) SDCADistSignal = (b) SDCADistCS=
Formula:
CHALNHLY[1 9] ServRequests
CHALNHLY[2 0] ServReques ts
80
A50016-G5100-A042-1-7618
Information System
(c) SDCADistAM RFR =

CHALNHLY[2 1] ServReques ts CHALNHLY[2 2] ServReques ts
RHR = (d) SDCADistAM Data = (e) SDCADistCS CSD = (f) SDCADistHS RS (g) SDCADistGP =
PRS = (h) SDCADistEG CI (i) SDCADistAS =
CHALNHLY[2 7] ServReques ts
Used param.: CHALNHLY[19..27], ServRequests(13.1(a)) Elem. Object: BTS Unit Remarks: None 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
13.3 Rate of Service Requests served in the highest layer

Long name: Short name: Description: Formula: (a) Rate of Service Requests served in highest layer (a) ServRequestsRate These indicators will give you the Service Request Success Rate. All Service Channel Requests served in the highest layer are considered.
tRate =1 (a) ServReques
CHALNHLY[1 ..18] ServReques ts
Used param.: CHALNHLY[1..18], ServRequests(13.1(a)) Elem. Object: BTS Unit Remarks: None Service requests not supported and not served in the highest layer are subtracted.
81
A50016-G5100-A042-1-7618
Information System
14 Feature related Performance Indicators

14.1 Abis Pool Traffic Utilization
Long name: (a) Mean number of defined Abis subchannels (b) Mean number of available Abis subchannels (c) Abis subchannel availability rate (d) Number of attempted Abis subchannel seizures (e) Number of successful Abis subchannel seizures (f) Number of unsuccessful Abis subchannel seizure attempts (g) Abis Pool Traffic offered (h) Abis Pool Traffic carried (i) Abis Pool Traffic lost (j) Abis Pool Loss Rate (k) Abis Pool Blocking Probability (l) Abis Pool Traffic Utilisation (m) Abis Pool Peak Traffic Utilisation (a) AbisPDefCh (b) AbisPAvailCh (c) AbisPAvailRate (d) AbisPAttSeiz (e) AbisPSuccSeiz (f) AbisPUnsuccSeiz (g) AbisPTrOff (h) AbisPTrCar (i) AbisPTrLost (j) AbisPLossRate (k) AbisPBlockProb (l) AbisPTrafUtil (m) AbisPTrafUtilPeak With the Abis Pool Supervision measurements it is possible to evaluate the most important load, capacity and quality related KPIs for the Abis Interface. (a) AbisPDefCh = ABISPSUP[1] (b)
Short name:
AbisPAvail Ch = ABISPSUP[2 ]
ABISPSUP[2] ABISPSUP[1]
(c) AbisPAvailRate = (d) (e)
AbisPAttSeiz = ABISPSUP[6] + ABISPSUP[7] AbisPSuccSeiz = ABISPSUP[6]
(f) AbisPUnsuccSeiz = ABISPSUP[7] (g) AbisPTrOff = ABISPSUP[3] * (1 + ABISPSUP[7] ) ABISPSUP[6]
82
A50016-G5100-A042-1-7618
Information System

(h) AbisPTrCar = ABISPSUP[3] (i) AbisPTrLost = ABISPSUP[3] * (j) AbisPLossRate = (k) AbisPBlockProb =
ABISPSUP[7] ABISPSUP[6]
ABISPSUP[7] ABISPSUP[6] + ABISPSUP[7]
ABISPSUP[5] Granularity Period
(l) AbisPTrafUtil = ABISPSUP[3] ABISPSUP[1] (m) AbisPTrafU tilPeak = Used param.: ABISPSUP[1..7] Elem. Object: Cell Unit: Remarks: None None
ABISPSUP[4 ] ABISPSUP[1 ]
14.2 I-FRAME Discard Rate on Abis-Interface BSC side

Long name: (a) Loss rate of transmitted I-Frames on BSC side (b) Loss rate of received I-Frames on BSC side (c) I-Frame Error Rate on Abis at BSC side (a) IFramesDiscRateBSCTransmitted (b) IFramesDiscRateBSCReceived (c) IFramesErrorRateBSE (a,b) This indicator will give you the I-Frame Loss Rate by meaning the number of discarded or badly received I-Frames related to the total number of transmitted IFrames of the LAPD protocol on the Abis-Interface on BSC side. (c) This indicator will give you the LAPD I-Frame Error Rate on Abis at BSC, by meaning the difference of the number of transmitted I-Frames at BTSE and the number of correctly received I-Frames at BSC in relation to the total number of transmitted I-Frames at BTSE. (a) IFramesDis cRateBSCTr ansmitted = (b) IFramesDis cRateBSCRe ceived = (c) IFramesErrorRateBSC = Used param.: IFRMABSC [all] Elem. Object: BSC Unit None
IFRMABSC[2 ] IFRMABSC[1 ,2]
Short name:
Description:
Formula:
IFRMABSC[4 ] IFRMABSC[3 ,4]
IFRMABIS[1 ] - IFRMABSC[3 ,4] IFRMABIS[1 ]
83
A50016-G5100-A042-1-7618
Information System
Remarks:

Only I-Frames with SAPI = 0 (radio signalling link) and SAPI = 62 (O&M connection) are considered.
14.3 I-FRAME Discard Rate on Abis-Interface BTSE side

Long name: (a) Loss rate of transmitted I-Frames on BTSE side (b) Loss rate of received I-Frames on BTSE side (c) I-Frame Error Rate on Abis at BTSE (a) IFramesDiscRateBTSETransmitted (b) IFramesDiscRateBTSEReceived (c) IFramesErrorRateBTSE (a,b) This indicator will give you the I-Frame Loss Rate by meaning the number of discarded or badly received I-Frames related to the total number of transmitted IFrames of the LAPD protocol on the Abis-Interface on BTSE side. (c) This indicator will give you the LAPD I-Frame Error Rate on Abis at BTSE, by meaning the difference of the number of transmitted I-Frames at BSC and the number of correctly received I-Frames at BTSE in relation to the total number of transmitted I-Frames at BSC. IFRMABIS[2 ] (a) IFramesDis cRateBTSET ransmitted = IFRMABIS[1 ,2] (b) IFramesDis cRateBTSER eceived = (c) IFramesErrorRateBTSE =
IFRMABIS[4 ] IFRMABIS[3 ,4]
Short name:
Description:
Formula:
IFRMABSC[1 ] - IFRMABIS[3 ,4] IFRMABSC[1 ]
Used param.: IFRMABIS [all], IFRMABSC[1] Elem. Object: BSC Unit Remarks: None Only I-Frames with SAPI = 0 (radio signalling link) and SAPI = 62 (O&M connection) are considered.
84
A50016-G5100-A042-1-7618
Information System
15 Handover related Performance Indicators

15.1 General Handover performance
15.1.1 Handover Success Rate
Long name: Short name: Description: Formula: (a) Handover Success Rate (a) HOSuccRate These indicators will give you the general HO success rate as an aggregation over all HO causes. (a) HOSuccRate =
SINTHINT [ all ] + SUINBHDO[all ] + SUOISHDO[ all ] ATINHIRC[all] + ATINBHDO[all] + ATOISHDO[all]
Used param.: SINTHINT[all], SUINBHDO[all], SUOISHDO[all], ATINHIRC[all], ATINBHDO[all], ATOISHDO[all] Elem. Object: Cell Unit: Remarks: None Intra Cell Handovers are not considered. For for Total Handover Success Rate please refer to chapter 15.6.8.
15.1.2 Handover Success Rate 2G to 2G

Long name: Short name: Description: Formula: (a) Handover Success Rate 2G to 2G (a) HOSuccRate2G2G These indicators will give you the general HO success rate as an aggregation over all HO causes from 2G to 2G systems. (a) HOSuccRate2G 2G =
SINTHINT [all ] + SUINBHDO[all ] ATINHIRC[all] + ATINBHDO[all]
Used param.: SINTHINT[all], SUINBHDO[all], ATINHIRC[all], ATINBHDO[all], Elem. Object: Cell Unit: Remarks: None None
15.1.3 Handover Success Rate 2G to 3G

Long name: Short name: Description: (a) Handover Success Rate 2G to 3G (a) HOSuccRate2G3G These indicators will give you the general HO success rate as an aggregation over
85
A50016-G5100-A042-1-7618
Information System
Formula: (a) HOSuccRate2G3G =

all HO causes from 2G to 3G systems.
SUOISHDO[all ] ATOISHDO[all]
Used param.: SUOISHDO[all], ATOISHDO[all] Elem. Object: Cell Unit: Remarks: None None
15.2 Intra Cell Handovers

Long name: (b) (c) (d) (e) (b) (c) (d) (e) Number of Intra Cell Handover Attempts Number of Intra Cell Handover Successes Intra Cell Handover Success Rate Intra Cell Handover Success Rate per cause IntraCellHOAtt IntraCellHOSucc IntraCellHOSuccRate IntraCellHOSuccRateC
Short name:
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 (b) IntraCellHOAtt = ATINHIAC[1..14] (c) IntraCellHOSucc = SINTHITA[1..14] (d) IntraCellHOSuccRate =
Formula:
IntraCellHOSucc IntraCellHOAtt
(e) IntraCellH OSuccRateC [c] =
SINTHITA[c ] ATINHIAC[c ]
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
86
A50016-G5100-A042-1-7618
Information System
c=12 c=13 c=14

forced HO due to Multislot calls compression HO from FR/EFR to HR decompression HO from HR to FR/EFR
Used param.: SINTHITA[1..14], ATINHIAC[1..14] Elem. Object: Cell Unit: Remarks: None SDCCH handovers are also incremented in this formulas.
15.2.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 (a) IntraCellHOFail (b) IntraCellHOFailRate (c) IntraCellHOFailRateC 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
Short name:
Description:
Formula: (a)
IntraCellHOFail = UNINHOIA[1..14]
IntraCellHOFail IntraCellHOAtt
UNINHOIA[c] ATINHIAC[c]
(b) IntraCellHOFailRate =
(c) IntraCellHOFailRateC[c] =
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 (15.2.1(b))
87
A50016-G5100-A042-1-7618
Information System
Elem. Object: Cell Unit: Remarks: None
SDCCH handovers are also incremented in this formula.
15.2.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 (a) IntraCellHODrop (b) IntraCellHODropRate (c) IntraCellHODropRateC 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 (a) IntraCellHODrop = UNIHIALC[1] (b) IntraCellHODropRate =
IntraCellHODrop IntraCellHOAtt
ATINHIAC[c] - SINTHITA[c] - UNINHOIA[c] ATINHIAC[c]
Short name:
Description:
Formula:
(c) IntraCellHODropRateC[c] =
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.: UNIHIALC[1], ATINHIAC[1..14], SINTHITA[1..14], UNINHOIA[1..14], IntraCellHOAtt (15.2.1(b)) Elem. Object: Cell Unit: Remarks: None SDCCH handovers are also incremented in this formulas. User release during Handover will lead to very small systematic errors.
88
A50016-G5100-A042-1-7618
Information System
15.2.4 Handover Distribution

Long name: Short name: Description: Formula: (a) Intra Cell Handover Distribution per Handover cause (a) IntraCellHODist These indicators will give you the Intra Cell Handover Distribution for analyzing the reason (=cause) for started Intra Cell Handovers.
ATINHIAC[c ] IntraCellH OAtt 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
(a) IntraCellH ODist[c] =
Used param.: ATINHIAC[1..14], IntraCellHOAtt (15.2.1(b)) Elem. Object: Cell Unit: Remarks: None SDCCH handovers are also incremented in this formulas.
89
A50016-G5100-A042-1-7618
Information System
15.2.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 (a) IntraCellSDHOAtt (b) IntraCellSDHOSucc (c) IntraCellSDHOSuccRate These indicators will give you the rate of successful Intra Cell SDCCH Handovers. (a) IntraCellSDHOAtt = AISHINTR[1] (b) IntraCellSDHOSucc = SISHINTR[1] (c) IntraCellSDHOSuccRate = Used param.: Elem. Object: Unit: Remarks: AISHINTR[1], SISHINTR[1] Cell None None
Short name:
IntraCellSDHOSucc IntraCellSDHOAtt
15.2.6 SDCCH Handover Failure Rate

Long name: Short name: Description: (a) Number of Intra Cell SDCCH Handover Failures (b) Intra Cell SDCCH Handover Failure Rate (a) IntraCellSDHOFail (b) IntraCellSDHOFailRate 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:
DHOFail = UISHINTR[ 1] (a) IntraCellS

(b) IntraCellSDHOFailRate =
IntraCellSDHOFail IntraCellSDHOAtt
Used param.: UISHINTR[1], IntraCellSDHOAtt (15.2.5(a)) Elem. Object: Cell Unit: Remarks: None None
90
A50016-G5100-A042-1-7618
Information System
15.2.7 SDCCH Handover Drop Rate

Long name: Short name: Description: (a) Number of Intra Cell SDCCH Handover Drops (b) Intra Cell SDCCH Handover Drop Rate (a) IntraCellSDHODrop (b) IntraCellSDHODropRate 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. (a) IntraCellSDHODrop = UISHIALC[1] (b) IntraCellSDHODropRate =
Formula:
IntraCellSDHODrop IntraCellSDHOAtt
Used param.: UISHIALC[1], IntraCellHOAtt (15.2.5(a)) Elem. Object: Cell Unit: Remarks: None None
91
A50016-G5100-A042-1-7618
Information System
15.3 Inter Cell Intra BSC Handovers

Long name: (a) (b) (c) (d) (a) (b) (c) (d) Number of Inter Cell Intra BSC Handover Attempts Number of Inter Cell Intra BSC Handover Successes Inter Cell Intra BSC Handover Success Rate Inter Cell Intra BSC Handover Success Rate per cause InterCellHOAtt InterCellHOSucc InterCellHOSuccRate InterCellHOSuccRateC
Short name:
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) InterCellHOAtt[n] =
AOUINIRH[n * 48 + i *12 + c]
c =1 i = 0 12
12
(b) InterCellHOSucc[n] =
SOUINIRH[n * 48 + i *12 + c]
c =1 i = 0
(c)
InterCellH OSuccRate[ n] =
InterCellH OSucc[n] InterCellH OAtt[n]
(d) InterCellHOSuccRateC[n, c] =
SOUINIRH[n * 48 + i *12 + c] AOUINIRH[n * 48 + i *12 + c]

i =0 i =0 3
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 c=12 forced handover due to DTM with i for the type of cell area:
92
A50016-G5100-A042-1-7618
Information System
i=0 i=1 i=2 i=3

complete-complete area complete-inner area inner-complete area inner-inner area
Used param.: AOUINIRH[all], SOUINIRH[all] Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
93
A50016-G5100-A042-1-7618
Information System

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 (a) InterCellHOFail (b) InterCellHOFailRate (c) InterCellHOFailRateC 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) InterCellHOFail[n] = UNINHOIE [n *12 + c]
C =1 12
Short name:
Description:
(b)
InterCellHOFailRate[n] =
InterCellHOFail[n] InterCellHOAtt[n]
UNINHOIE [n * 12 + c] 3 AOUINIRH[n * 48 + i * 12 + c] i=0
(c) InterCellHOFailRateC[n, c] =
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 c=12 forced handover due to DTM 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] (15.3.1(a)) Elem. Object: Neighbourcell Unit: None
94
A50016-G5100-A042-1-7618
Information System
Remarks:

SDCCH handovers are also incremented in these formulas.
95
A50016-G5100-A042-1-7618
Information System

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 (a) InterCellHODrop (b) InterCellHODropRate (c) InterCellHODropRateC 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) InterCellHODrop[n] = InterCellHOAtt[n] - InterCellHOSucc[n] - InterCellHOFail[n]
Short name:
Description:
(b)
InterCellH ODropRate[ n] =
InterCellH ODrop[n] InterCellH OAtt[n]
InterCellHODropRateC[n, c] =
(c)
(AOUINIRH - SOUINIRH)[n * 48 + i *12 + c] - UNINHOIE[n *12 + c]

i =0
AOUINIRH[n* 48 + i *12 + c]
i =0
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 c=12 forced handover due to DTM 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
96
A50016-G5100-A042-1-7618
Information System
Used param.: AOUINIRH[all], SOUINIRH[all], UNINHOIE[all], InterCellHOAtt[all] (15.3.1(a)), InterCellHOSucc[all] (15.3.1(b)), InterCellHOFail[all] (15.3.2(a)) Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas. User release during Handover will lead to systematic errors.
97
A50016-G5100-A042-1-7618
Information System

Long name: Short name: Description: (a) Inter Cell Intra BSC Handover Distribution (b) Imperative Inter Cell Handover Rate (a) InterCellHODist (b) ImpInterCellHORate 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)
InterCellHODist[n, c] =
AOUINIRH[n* 48 + i *12 + c]
i =0
InterCellHOAtt[n]
(b) ImpInterCellHORate =
(AOUINIRH[ n * 48 + i *12 + 10] + AOUINIRH[n * 48 + i *12 + c])

i=0 c =1
InterCellH OAtt[n]
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 c=12 forced handover due to DTM 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.: AOUINIRH[all], InterCellHOAtt (15.3.1(a)) Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
98
A50016-G5100-A042-1-7618
Information System
15.3.5 Incoming Handover Success Rate

Long name: Short name: Description: Formula: Inter Cell Intra BSC Incoming Handover Success Rate InterCellIncHOSuccRate This indicator will give you the rate of successful Inter Cell Intra BSC Incoming Handovers per neighbour cell relation.
InterCellIncHOSuccRa te[n] =
SININIRH[n * 48 + i *12 + c] AININIRH[n * 48 + i *12 + c]

c =1 i = 0 c =1 i = 0 12 3
12
Used param.: Elem. Object: Unit: Remarks:
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 c=12 forced handover due to DTM 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 SININIRH[all], AININIRH[all] Neighbourcell None SDCCH handovers are also increment in the counters used for this formula and that fact can lead to systematic errors.

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 (a) InterCellSDHOAtt (b) InterCellSDHOSucc
Short name:
99
A50016-G5100-A042-1-7618
Information System

(c) InterCellSDHOSuccRate These indicators will give you the rate of successful Inter Cell SDCCH Handovers. (a) InterCellSDHOAtt = AISHINTE[1] (b) InterCellSDHOSucc = SISHINTE[1] (c) InterCellSDHOSuccRate =
InterCellSDHOSucc InterCellSDHOAtt
AISHINTE[1], SISHINTE[1] Cell None None
100
A50016-G5100-A042-1-7618
Information System

Long name: Short name: Description: Number of Inter Cell SDCCH Handover Failures Inter Cell SDCCH Handover Failure Rate InterCellSDHOFail InterCellSDHOFailRate 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:
InterCellSDHOFail= UISHINTE[ 1]
InterCellSDHOFailRate = InterCellSDHOFail InterCellSDHOAtt
Used param.: UISHINTE[1], InterCellSDHOAtt (15.3.6(a)) Elem. Object: Cell Unit: Remarks: None None

Long name: Short name: Description: Formula: Number of Inter Cell SDCCH Handover Drops Inter Cell SDCCH Handover Drop Rate InterCellSDHODrop InterCellSDHODropRate 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.
InterCellSDHODrop = UISHIRLC[1] InterCellSDHODropRate = InterCellSDHODrop InterCellSDHOAtt
Used param.: UISHIRLC[1], InterCellSDHOAtt (15.3.6(a)) Elem. Object: Cell Unit: Remarks: None None
101
A50016-G5100-A042-1-7618
Information System
15.4 Inter Cell Inter BSC Handovers

Long name: (a) (b) (c) (d) (a) (b) (c) (d) Number of Inter Cell Inter BSC Handover Attempts Number of Inter Cell Inter BSC Handover Successes Inter Cell Inter BSC Handover Success Rate Inter Cell Inter BSC Handover Success Rate per cause InterBSCHOAtt InterBSCHOSucc InterBSCHOSuccRate InterBSCHOSuccRateC
Short name:
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)
InterBSCHOAtt[n] = ATINBHDO [n *11 + c]

c =1
11
(b)
InterBSCHOSucc[n] =
SUINBHDO [n *11 + c]
c =1
11
(c)
InterBSCHOSuccRate[n ] =
InterBSCHOSucc[n] InterBSCHOAtt[n]
SUINBHDO[n *11 + c] ATINBHDO[n *11 + c]
(d) InterBSCHOSuccRateC[n, c] =
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 fast uplink c=10 forced handover due to preemption c=11 forced handover due to DTM Used param.: ATINBHDO [all], SUINBHDO[all] Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
102
A50016-G5100-A042-1-7618
Information System

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 (a) InterBSCHOFail (b) InterBSCHOFailRate (c) InterBSCHOFailRateC 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)
Short name:
Description:
InterBSCHOFail[n] =
NRUNINHD [n *11 + c]
c =1
11
(b)
InterBSCHOFailRate[n] =
InterBSCHOFail[n] InterBSCHOAtt[n]
NRUNINHD[n *11 + c] ATINBHDO[n *11 + c]
(c)
InterBSCHOFailRateC[n, c] =
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 fast uplink c=10 forced handover due to preemption c=11 forced handover due to DTM Used param.: NRUNINHD[all], ATINBHDO[all], InterBSCHOAtt[all] (15.4.1(a)) Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
103
A50016-G5100-A042-1-7618
Information System

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 (a) InterBSCHODrop (b) InterBSCHODropRate (c) InterBSCHODropRateC 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. (a) InterBSCHODrop[n] = InterBSCHOAtt[n] - InterBSCHOSucc[n] - InterBSCHOFail[n] (b)
Short name:
Description:
Formula:
InterBSCHODropRate[n] =
InterBSCHODrop[n] InterBSCHOAtt[n]
ATINBHDO[n * 11 + c]
(c) InterBSCHODropRateC[n, c] =
(ATINBHDO - SUINBHDO - NRUNINHD)[n * 11 + c]
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 fast uplink c=10 forced handover due to preemption c=11 forced handover due to DTM Used param.: ATINBHDO[all], SUINBHDO[all], NRUNINHD[all], InterBSCHOAtt[all] (15.4.1(a)), InterBSCHOSucc[all] (15.4.1(b)), InterBSCHOFail[all] (15.4.2(a)) Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas. User release during Handover will lead to very small systematic errors.
104
A50016-G5100-A042-1-7618
Information System

Long name: Short name: Description: (a) Inter Cell Inter BSC Handover Distribution (b) Imperative Inter Cell Inter BSC Handover Rate (a) InterBSCHODist (b) ImpInterBSCHORate 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. (a)
Formula:
InterBSCHODist[n, c] =
ATINBHDO[n *11 + c] InterBSCHOAtt[n]
(b) ImpInterBSCHORate =
ATINBHDO[n *11 + c] + ATINBHDO[n *11 + 9]

c =1
InterBSCHOAtt[n]
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 fast uplink c=10 forced handover due to preemption c=11 forced handover due to DTM Used param.: ATINBHDO[all], InterBSCHOAtt[all] (15.4.1(a)), Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
105
A50016-G5100-A042-1-7618
Information System

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 (a) InterBSCSDHOAtt (b) InterBSCSDHOSucc (c) InterBSCSDHOSuccRate These indicators will give you the rate of successful Inter Cell Inter BSC SDCCH Handovers. (a) InterBSCSDHOAtt = AOINTESH[1] (b) InterBSCSDHOSucc = SOINTESH[1] (c) InterBSCSDHOSuccRate = Used param.: Elem. Object: Unit: Remarks: AOINTESH[1], SOINTESH[1] Cell None None
Short name:
InterBSCSDHOSucc InterBSCSDHOAtt

Long name: Short name: Description: Number of Inter Cell Inter BSC SDCCH Handover Failures Inter Cell Inter BSC SDCCH Handover Failure Rate InterBSCSDHOFail InterBSCSDHOFailRate 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:
InterBSCSDHOFail = UOINTESH[ 1] InterBSCSDHOFailRate = InterBSCSDHOFail InterBSCSDHOAtt
Used param.: UOINTESH[1], InterBSCSDHOAtt (15.4.5(a)) Elem. Object: Cell Unit: Remarks: None None
106
A50016-G5100-A042-1-7618
Information System

Long name: Short name: Description: Number of Inter Cell Inter BSC SDCCH Handover Drops Inter Cell Inter BSC SDCCH Handover Drop Rate InterBSCSDHODrop InterBSCSDHODropRate 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:
InterBSCDHODrop = UMCSHLC[1]
InterBSCSDHODropRate = InterBSCSDHODrop InterBSCSDHOAtt
Used param.: UMCSHLC[1], InterBSCSDHOAtt (15.4.5(a)) Elem. Object: Cell Unit: Remarks: None None
107
A50016-G5100-A042-1-7618
Information System
15.5 Inter System Handover between GSM and UMTS

15.5.1 Outgoing Inter System Handover Success Rate
Long name: (a) (b) (c) (d) (a) (b) (c) (d) Outgoing Inter System Handover Attempts Outgoing Inter System Handover Successes Outgoing Inter System Handover Success Rate Outgoing Inter System Handover Success Rate per cause InterSysOtgHOAtt InterSysOtgHOSucc InterSysOtgHOSuccRate InterSysOtgHOSuccRateC
Short name:
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:
11 InterSysOtgHOAtt[n] = ATOISHDO [n *11 + c] (a) c =1

(b)
(c)
11 InterSysOtgHOSucc[n] = SUOISHDO [n *11 + c] c =1 InterSysOtgHOSucc[n] InterSysOtgHOSuccRat e[n] = InterSysOtgHOAtt[n]

SUOISHDO[n *11 + c] ATOISHDO[n *11 + c]
(d) InterSysOtgHOSuccRat eC[n, c] =
with n for the number of the 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 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 c=11 forced handover due to DTM Used param.: ATOISHDO [all], SUOISHDO[all] Elem. Object: Neighbourcell Unit: Remarks: None None
108
A50016-G5100-A042-1-7618
Information System
15.5.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 (a) InterSysOtgHOFail (b) InterSysOtgFailRate (c) InterSysOtgFailRateC 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) InterSysOtgHOFail[n] = UNOISHDO [n *11 + c]
Short name:
Description:
11
c =1
(b)
InterSysOtgHOFailRate[n] =
InterSysOtgHOFail[n] InterSysOtgHOAtt[n]
(c) InterSysOtgHOFailRateC[n, c] =
UNOISHDO[n *11 + c] ATOISHDO[n *11 + c]
with n for the number of the 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 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 c=11 forced handover due to DTM Used param.: UNOISHDO[all], ATOISHDO[all], InterSysOtgHOAtt[all] (15.5.1(a)) Elem. Object: Neighbourcell Unit: Remarks: None None
109
A50016-G5100-A042-1-7618
Information System
15.5.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 (a) InterSysOtgHODrop (b) InterSysOtgHODropRate (c) InterSysOtgHODropRateC 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) InterSysOtgHODrop = InterSysOtgHOAtt - InterSysOtgHOSucc - InterSysOtgHOFail
Short name:
Description:
(b)
InterSysOtgHODropRate =
InterSysOtgHODrop InterSysOtgHOAtt
(ATOISHDO - SUOISHDO - UNOISHDO)[n * 11 + c] ATOISHDO[n * 11 + c]
(c) InterSysOtgHODropRateC[n, c] =
with n for the number of the 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 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 c=11 forced Handover due to DTM Used param.: ATOISHDO[all], SUOISHDO[all], UNOISHDO[all], InterSysOtgHOAtt[all] (15.5.1(a)), InterSYSHOSucc[all] (15.5.1(b)), InterSYSHOFail[all] (15.5.2(a)) Elem. Object: Neighbourcell Unit: Remarks: None Systematic error: call release during HO is included in the formula
110
A50016-G5100-A042-1-7618
Information System
15.5.4 Outgoing Inter System Handover Distribution

Long name: Short name: Description: (a) Outgoing Inter Cell Inter System Handover Distribution (b) Outgoing Imperative Inter Cell Inter System Handover Rate (a) InterSysOtgHODist (b) ImpInterSysOtgHORate 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 (a)
Formula:
InterSysOtgHODist[n, c] =
ATOISHDO[n *11 + c] InterSysOtgHOAtt[n]
(b)
ImpInterSysOtgHORate[n] =
ATOISHDO[n *11 + c]
c =1
InterSysOtgHOAtt[n]
with n for the number of the 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 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 c=11 forced handover due to DTM Used param.: ATOISHDO[all], InterSysOtgHOAtt[all] (15.5.1(a)) Elem. Object: Neighbourcell Unit: Remarks: None
111
A50016-G5100-A042-1-7618
Information System
15.5.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 (a) InterSysIncHOSucc (b) InterSysIncHOAtt (c) InterSysIncHOSuccRate These indicators will give you the rate and number of successful Incoming Inter System HO from UMTS. (a) (b) (c)
Short name:
InterSysIncHOSucc = SUIISHDO [1]
InterSysIncHOAtt = RQIISHDO[1]
InterSysIncHOSuccRate = InterSysIncHOSucc InterSysIncHOAtt
RQIISHDO[1]: Number of requested incoming intersystem handovers SUIISHDO[1]: Number of successful incoming intersystem handovers BSC None
112
A50016-G5100-A042-1-7618
Information System
15.6 Other Handover Performance Indicators

15.6.1 Handovers per Erlanghour
Long name: Short name: Description: (a) Handover per Erlanghour (a) HOperErlh 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 (a) HOperErlh =
Formula:
SINTHITA[all] + SINTHINT[all] + SUINBHDO[all] + SUOISHDO[all] 60 * MEBUSTCH [all] Granularit y

Used param.: SINTHITA[all], SINTHINT [all], SUINBHDO[all], SUOISHDO[all], MEBUSTCH[all], Granularity in minutes Elem. Object: Cell Unit: Remarks: None
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
15.6.2 Handovers per Call Rate

Long name: Short name: Description: (a) Handovers per Call Rate (a) HOperCallRatio 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 (a) HOperCallRatio =
Formula:
SINTHITA[all] + SINTHINT[all] + SUINBHDO[all] + SUOISHDO[all] TASSSUCC[2..5]

Used param.: SINTHITA[all], SINTHINT [all], SUINBHDO[all], SUOISHDO[all], TASSSUCC[2..5], Elem. Object: Cell Unit: Remarks: None
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. Intersystem HO to UMTS are considered
113
A50016-G5100-A042-1-7618
Information System
15.6.3 Intercell Handover Attempts per Speech Call per Erlanghour

Long name: Short name: Description: Formula: (a) Intercell Handover Attempts per Erlanghour (a) HOAttperErlh This KPI gives the number of inter-cell (intra and inter-BSC and inter-system) HO attempts in relation to the amount of traffic carried in the cell. (a) HOAttErlh =
ATINHIRC[a ll] + ATINBHDO[a ll] + ATOISHDO[a ll] 60 MEBUSTCH [ 1..4 ] Granularit y
Used param.: ATINHIRC[all], ATINBHDO[all], ATOISHDO[all], MEBUSTCH[1..4], Granularity in minutes Elem. Object: Cell Unit: Remarks: None None
15.6.4 Successful Directed Retries

Long name: Short name: Description: (a) Number of Successful Directed Retries to GSM target cell (b) Number of Successful Directed Retries to UMTS target cell (a) NoSuccDirectedRetryGSM (b) NoSuccDirectedRetryUMTS 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. (a) NoSuccDirectedRetryGSM[m] =
Formula:
SUINBHDO [m * 11 + 7 ] +
SOUINIRH[m * 48 + i *12 + 7]
i =0
(b) NoSuccDirectedRetryUMTS[n] = SUOISHDO[n *11 + 7]

with m for the mth number of GSM neighbourcell relation (m=0..31) with n for the nth number of UMTS neighbourcell relation (n=0..63)
with i for the type of cell area: i=0 complete-complete area i=1 complete-inner area i=2 inner-complete area i=3 inner-inner area Used param.: Elem. Object: Unit: SUINBHDO[m*11+7], SOUINIRH[m*48+i*12+7], SUOISHDO[n*11+7], Neighbourcell None
114
A50016-G5100-A042-1-7618
Information System
Remarks:

Intersystem HO to UMTS are considered
15.6.5 Imperative Outgoing Handover Rate

Long name: Short name: Description: (a) Imperative Outgoing Handover Rate for GSM target cell (b) Imperative Outgoing Handover Rate for UMTS target cell (a) ImpOutgHORateGSM (b) ImpOutgHORateUMTS This indicator will give you the rate of handovers due to Imperative reasons (namely UpLink/DownLink Strength and UpLink/DownLink Quality and Distance and Fast Uplink) 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 (a)
Formula:
ImpOutgHORateGSM[m] =
InterBSCHO Att Im p[ m] + InterCellH oAtt Im p[ m] InterBSCHOAtt[m] + InterCellHOAtt[m]
with InterCellHOAttImp[m] =
AOUINIRH[m * 48 + i *12 + c]) + AOUINIRH[m * 48 + i *12 + 10]

(
i =0 c =1
InterBSCHO AttImp[m] ( =
* * ATINBHDO[m11+ c]) + ATINBHDO[m11+ 9]

c=0
ATOISHDO[n *11 + c]
(b) ImpOutgHORateUMTS[n]=
c =1
InterSysOt gHOAtt[n]
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= 9/10 fast uplink 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
115
A50016-G5100-A042-1-7618
Information System
Used param.:

AOUINIRH[m*48+i*12+c] , ATINBHDO[m*11+c], ATOISHDO[n*11+c], InterCellHOAtt[m] (15.3.1(a)), InterBSCHOAtt[m] (15.4.1(a)), InterSysOtgHOAtt[n] (15.5.1(a)) Neighbourcell None 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
Elem. Object: Unit: Remarks:
15.6.6 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 (a) InterBSCIncHOSucc (b) InterBSCIncHOAtt (c) InterBSCIncHOSuccRate These indicators will give you the rate and number of successful Inter Cell Inter BSC Incoming Handovers including incoming HO from UMTS. (a)
Short name:
InterBSCIncHOSucc = SUCTCHSE[1,2] - TASSSUCC[2,3] IntraCellHOSucc - NSUCCHPC[9..14, 17 .. 22] - SININIRH[1..48]
(b)
InterBSCIncHOAtt = ATTCHSEI[1,2] - TASSATT[2,3] IntraCellHOAtt - ATIMASCA[7 ..14] - AININIRH[1 ..48]
(c)
InterBSCIncHOSuccRate =
InterBSCIncHOSucc InterBSCIncHOAtt
Used param.:
SUCTCHSE[1,2], TASSSUCC[2,3], NSUCCHPC[9...14,17...22], SININIRH[1..48], ATTCHSEI[1,2], TASSATT[2,3], ATIMASCA[7..14], AININIRH[1..48], IntraCellHOSucc(15.2.1(c)), IntraCellHOAtt(15.2.1(b)) Cell None
Elem. Object: Unit: Remarks:
SDCCH handovers are also increment in the counters used for this formula and that fact can lead to systematic errors. Intersystem HO to UMTS are considered
116
A50016-G5100-A042-1-7618
Information System
15.6.7 Handover Indication Rejection Rate

Long name: Short name: Description: (a) Handover Indication Rejection Rate (a) HOIndRejRate 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.
(a)
Formula:
HOIndRejRate =
NHOINRHA [1..4]
31 31 63
NHOINRHA [1..4] + IntraCellH OAtt + InterCellH OAtt + InterBSCHO Att + InterSysOt gHOAtt
m=0 m=0 n=0
Used param.: NHOINRHA [1..4], IntraCellHOAtt(15.2.1(b)), InterCellHOAtt[m] (15.3.1(a)), InterBSCHOAtt[m] (15.4.1(a)), InterSysOtgHOAtt[n] (15.5.1(a)) Elem. Object: Cell Unit: Remarks: None
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. Intersystem HO to UMTS are considered
117
A50016-G5100-A042-1-7618
Information System
15.6.8 Total Handover Rates

Long name: (a) (b) (c) (d) (e) (f) (g) (a) (b) (c) (d) (e) (f) (g) Total Number of Handover Attempts Total Number of Handover Successes Total Number of Handover Failures Total Number of Handover Drops Total Handover Success Rate Total Handover Failure Rate Total Handover Drop Rate HOAtt HOSucc HOFail HODrop TotalHOSuccRate HOFailRate HODropRate
Short name:
These indicators will give you Handover statistics related to (Intra Cell, Inter Cell, Inter BSC and Inter System) Handovers. (a) HOAtt = ATINHIAC[all] + ATINHIRC[all] + ATINBHDO[all] + ATOISHDO[a ll] (b) HOSucc = SINTHITA[all] + SINTHINT[a ll] + SUINBHDO[all] + SUOISHDO[a ll] (c) HOFail = UNINHOIA[all] + UNINHOIE[all] + NRUNINHD[all] + UNOISHDO[all]
HODrop = UNIHIALC[1] + UNIHIRLC[1] +
(d)
(ATINBHDO[all] - SUINBHDO[all] NRUNINHD[all] ) + (ATOISHDO[all] - SUOISHDO[all] - UNOISHDO[all])

HOAtt
(e) TotalHOSuc cRate = HOSucc (f) HOFailRate = HOFail HOAtt (g) HODropRate = HODrop
HOAtt
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: Remarks: None 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).
118
A50016-G5100-A042-1-7618
Information System
16 Power and Quality Measurements

16.1 Interference Band Rate on idle TCH
Long name: Short name: Description: Formula: (a) Interference Band Rate on idle TCH (a) IfBandRate[n] This indicator will give you Interference Band Rate on idle TCH. Several indicators distinguish between different interference bands. (a) IfBandRate[n] =
MEITCHIB [n] MEITCHIB [1..5]
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.: Elem. Object: Unit: Remarks: MEITCHIB[1..5] Cell None None
16.2 Quality Link for N% FER

Long name: Short name: Description: (a) Quality Link for N% FER (a) QualityLinkNFER 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) QualityLinkNFER =
CFERRXQU [i * 8 + 1..i * 8 + 8]
i =0
CFERRXQU [1..64]
Where n is the FER band that has its upper limit equal or lower to N% Used param,: Elem. Object: Unit: Remarks: CFERRXQU[1..64] TRX None None
119
A50016-G5100-A042-1-7618
Information System
16.3 Mean FER UpLink

Long name: Short name: Description: Formula: (a) MeanFERUL = Used param,: Elem. Object: Unit: Remarks: CFERRXQU[1..64] TRX FER Band None (a) Mean FER UpLink (a) MeanFERUL This indicator provides the average FER Band on the Uplink.
((i + 1)* CFERRXQU [i * 8 + 1..i * 8 + 8])

i =0
CFERRXQU [1..64]
120
A50016-G5100-A042-1-7618
Information System
16.4 Power and Quality limits for N% Percentile on busy TCH

Long name: (a) (b) (c) (d) (a) (b) (c) (d) RXLEV for N% Percentile Uplink on busy TCH RXLEV for N% Percentile Downlink on busy TCH RXQUAL for N% Percentile Uplink on busy TCH RXQUAL for N% Percentile Downlink on busy TCH RxLvNPercentileUL RxLvNPercentileDL RxQuNPercentileUL RxQuNPercentileDL
Short name:
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. (a) RxLvNPercentileUL = n with n such that
n (PWRUPDW [i]) N i =1 = PWRUPDW [1..64] 100 n (PWRUPDW [72 + i]) N i =1 = 100 PWRUPDW [73..136] n (PWRUPDW [64 + i]) N i=1 = PWRUPDW [65..72] 100
Formula:
(b) RxLvNPercentileDL = n with n such that
(c) RxQuNPercentileUL = n with n such that
n (PWRUPDW [136 + i]) N = (d) RxQuNPercentileDL = n with n such that i=1 100 PWRUPDW [137..144]
PWRUPDW[all] Channel None None
121
A50016-G5100-A042-1-7618
Information System
16.5 Distribution of power control levels on busy TCH

Long name: Short name: Description: Use case: (a) Power Control level distribution on busy TCH in UL direction (b) Power Control level distribution on busy TCH in DL direction (a) PWContrDistrUL (b) PWContrDistrDL This indicator provides the distribution of the registered power control levels per TCH for UL and DL direction. 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)
PWContrDistrUL[n] =
PWContrDistrDL[n] =
PWRUPDW [n + 1] PWRUPDW [1..64]

PWRUPDW [n + 73] PWRUPDW [73 ..136]
(b)
with n = 0 , .. 63 for the power control level Used param.: Elem. Object: Unit: Remarks: PWRUPDW[all] Channel None None
122
A50016-G5100-A042-1-7618
Information System
16.6 Mean Level and Quality on busy TCH

Long name: (a) (b) (c) (d) (a) (b) (c) (d) Mean RXLEV Uplink on busy TCH Mean RXLEV Downlink on busy TCH Mean RXQUAL Uplink on busy TCH Mean RXQUAL Downlink on busy TCH MeanRxLvUL MeanRxLvDL MeanRxQuUL MeanRxQuDL
Short name:
These indicators will give you the mean RXLEV and RXQUAL on busy TCH. Two indicators distinguish between uplink and downlink.
(a) MeanRxLvUL
=
64
(i * PWRUPDW [i])
i =1
64
PWRUPDW [1..64]
(b) MeanRxLvDL =
(i * PWRUPDW [72 + i])

i =1
PWRUPDW [73..136] =
8
(i * PWRUPDW [64 + i])

i =1
(c) MeanRxQuUL
PWRUPDW [65..72]
(d) MeanRxQuDL = Used param: Elem. Object: Unit: Remarks: PWRUPDW[all] Channel None None
(i * PWRUPDW [136 + i])

i =1
PWRUPDW [137..144]
123
A50016-G5100-A042-1-7618
Information System
16.7 TA Distribution
Long name: Short name: Description: Formula: (a) TADist[n] = Where n=0..7 Used param.: Elem. Object: Unit: Remarks: CRXLVTAD[1..64], CRXLVTAU[1..64] TRX None The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results. (a) TA Distribution (a) TADist[n] These indicators provide the rate of received samples having timing advance in TA Band equal to n .
(CRXLVTAD + CRXLVTAU) [i 8 + n + 1]
i =0
(CRXLVTAD + CRXLVTAU) [1..64]
16.8 RXQUAL Distribution

Long name: Short name: Description: (a) RXQUAL Distribution DownLink (b) RXQUAL Distribution UpLink (a) RxQuDistDL[n] (b) RxQuDistUL[n] 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) RxQuDistDL[n] =
CRXLVQUD [i 8 + n + 1]
i =0
CRXLVQUD [1..64]
(b) RxQuDistUL[n] = Where n=0..7 Used param.: Elem. Object: Unit: Remarks:
CRXLVQUU [i 8 + n + 1]
i =0
CRXLVQUU [1..64]
CRXLVQUD[1..64], CRXLVQUU[1..64] TRX None The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.
124
A50016-G5100-A042-1-7618
Information System
16.9 RXLEV Distribution

Long name: Short name: Description: (a) RXLEV Distribution DownLink (b) RXLEV Distribution UpLink (a) RxLvDistDL[n] (b) RxLvDistUL[n] 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. (a) RxLvDistDL[n] = (b) RxLvDistUL[n] = Where n=0..7 Used param.: Elem. Object: Unit: Remarks: CRXLVQUD[1..64], CRXLVQUU[1..64] TRX None The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.
CRXLVQUD [n 8 + 1..n 8 + 8] CRXLVQUD [1..64]
CRXLVQUU [n 8 + 1..n 8 + 8] CRXLVQUU [1..64]
Formula:
16.10 FER Distribution

Long name: Short name: Description: Formula: (a) FER Distribution (a) FERDist[n] These indicators provide the rate of received samples having the uplink FER in FER Band equal to n. (a) FERDist[n] = Where n=0..7 Used param.: Elem. Object: Unit: Remarks: CFERRXQU[1..64] TRX None The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results. This KPI is not applicable to AMR calls since AMR codec mode adaptation keeps FER at low level.
CFERRXQU [n 8 + 1..n 8 + 8] CFERRXQU [1..64]
125
A50016-G5100-A042-1-7618
Information System
16.11 Mean FER UpLink per RXQUAL

Long name: Short name: Description: (a) Mean FER UpLink per RXQUAL Band (a) MeanFERULforRxQu[n] 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) MeanFERULforRxQu [n] =
((i + 1) CFERRXQU [i 8 + n + 1])

i =0
CFERRXQU [i 8 + n + 1]
i =0
Where n =0..7 Used param,: Elem. Object: Unit: Remarks: CFERRXQU[1..64] TRX FER Band The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.
126
A50016-G5100-A042-1-7618
Information System
16.12 Mean RXLEV per RXQUAL Band

Long name: Short name: Description: (a) Mean RXLEV per RXQUAL Band DownLink (b) Mean RXLEV per RXQUAL Band UpLink (a) MeanRxLvforRxQuDL[n] (b) MeanRxLvforRxQuUL[n] 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) MeanRxLvforRxQuDL [n] =
((i ) CRXLVQUD [i 8 + n + 1])

i =0
CRXLVQUD [i 8 + n + 1]
i =0
(b) MeanRxLvforRxQuUL [n] =
((i ) CRXLVQUU [i 8 + n + 1])

i =0
CRXLVQUU [i 8 + n + 1]
i =0
Where n =0..7 Used param,: Elem. Object: Unit: Remarks: CRXLVQUU[1..64], CRXLVQUD[1..64] TRX Level Band The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.
127
A50016-G5100-A042-1-7618
Information System
16.13 Mean RXLEV per TA Band

Long name: Short name: Description: Formula: (a) MeanRxLvforTADL [n] = (a) Mean RXLEV per TA Band DownLink (b) Mean RXLEV per TA Band UpLink (a) MeanRxLvforTADL (b) MeanRxLvforTAUL These indicators provide the average RXLEV Band for each Timing Advance Band either Uplink or Downlink.
((i )* CRXLVTAD [i * 8 + n + 1])

i =0
CRXLVTAD [i * 8 + n + 1]
i =0
(b) MeanRxLvforTAUL [n] =
((i)* CRXLVTAU [i * 8 + n + 1])

i =0
CRXLVTAU [i * 8 + n + 1]
i =0
Where n =0..7 Used param.: Elem. Object: Unit: Remarks: CRXLVTAD[1..64], CRXLVTAU[1..64] TRX Level Band The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.
128
A50016-G5100-A042-1-7618
Information System
16.14 High RXLEV with Low RXQUAL Rate

Long name: Short name: Description: (a) High RXLEV With Low RXQUAL Rate DownLink (b) High RXLEV With Low RXQUAL Rate UpLink (a) HighLvLowQuRateDL (b) HighLvLowQuRateUL 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. (a) HighLvLowQuRateDL = (b) HighLvLowQuRateUL =
CRXLVQUD [53..56,61..64] CRXLVQUD [5..8,13..16,21..24,29..32,37..40,45..48,53..56,61..64]
Formula:
CRXLVQUU [53..56,61..64] CRXLVQUU [5..8,13..16,21..24, 29..32,37. .40,45..48 ,53..56,61 ..64]
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] TRX None The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.
129
A50016-G5100-A042-1-7618
Information System
16.15 TCH Traffic Type Distribution

Long name: (a) (b) (c) (d) (e) (f) (a) (b) (c) (d) (e) (f) TCH full rate speech traffic channel Rate TCH enhanced full rate speech traffic channel Rate TCH adaptive multirate full rate speech traffic channel Rate TCH full rate data traffic channel Rate TCH half rate speech traffic channel Rate TCH adaptive multirate half rate speech traffic channel Rate TCHFSRate TCHEFSRate TCHAFSRate TCHFDRate TCHHSRate TCHAHSRate
Short name:
Description:
These indicators provide the TCH Traffic Type Distribution, by meaning the traffic for an 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. (a) TCHFSRate =
Formula:
MBTCHCHT [1] MBTCHCHT[1..6] MBTCHCHT [2] MBTCHCHT[1..6] MBTCHCHT [3] MBTCHCHT[1..6]
(b) TCHEFSRate = (c) TCHAFSRate = (d) TCHFDRate = (e) TCHHSRate =
MBTCHCHT [4] MBTCHCHT[1..6] MBTCHCHT [5] MBTCHCHT[1..6] MBTCHCHT [6] MBTCHCHT[1..6]
(f) TCHAHSRate = Used param.: Elem. Object: Unit: Remarks: MBTCHCHT [1..6] Cell None None
130
A50016-G5100-A042-1-7618
Information System
16.16 SDCCH Traffic Type Distribution

Long name: (a) (b) (c) (d) (e) (f) (a) (b) (c) (d) (e) (f) SDCCH Load caused by speech signaling SDCCH Load caused by SMS signaling SDCCH Load caused by USSD signaling SDCCH Load caused by SS signaling SDCCH Load caused by other signaling procedures SDCCH Load caused by abnormal cases SDCCHLoadSpeech SDCCHLoadSMS SDCCHLoadUSSD SDCCHLoadSS SDCCHLoadOther SDCCHLoadAbnormal
Short name:
Description:
These indicators provide the SDCCH Traffic Type Distribution, by meaning the SDCCH Load for an 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. (a) SDCCHLoadSpeech = (b) SDCCHLoadSMS =
Formula:
MBUSYSSP[1] MBUSYSSP[all]
MBUSYSSP[2] MBUSYSSP[all] MBUSYSSP[3] MBUSYSSP[all]
(c) SDCCHLoadUSSD = (d) SDCCHLoadSS =
MBUSYSSP[4] MBUSYSSP[all] MBUSYSSP[5] MBUSYSSP[all] MBUSYSSP[6] MBUSYSSP[all]
(e) SDCCHLoadOther =
(f) SDCCHLoadAbnormal = Used param.: Elem. Object: Unit: Remarks: MBUSYSSP[all] Cell
None Formula c) is only valid, if attribute TRANSPM is enabled. Formula d) will not consider SDCCH traffic caused by USSD signaling, if attribute TRANSPM is enabled. In the other case USSD signaling is included.
131
A50016-G5100-A042-1-7618
Information System
16.17 Adaptive Multirate Distribution

Long name: Short name: Description: (a) Adaptive Multirate channel type usage (a) AMRCHTUsage 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). (a) AMRCHTUsage[n] =
with n = 1 for TCH/AFS 12.2 uplink 2 for TCH/AFS 10.2 uplink 3 for TCH/AFS 7.95 uplink 4 for TCH/AFS 7.4 uplink 5 for TCH/AFS 6.7 uplink 6 for TCH/AFS 5.9 uplink 7 for TCH/AFS 5.15 uplink 8 for TCH/AFS 4.75 uplink 9 for TCH/AHS 7.4 uplink 10for TCH/AHS 6.7 uplink 11 for TCH/AHS 5.9 uplink 12 for TCH/AHS 5.15 uplink 13 for TCH/AHS 4.75 uplink 14 for TCH/AFS 12.2 downlink 15 for TCH/AFS 10.2 downlink 16 for TCH/AFS 7.95 downlink 17 for TCH/AFS 7.4 downlink 18 for TCH/AFS 6.7 downlink 19 for TCH/AFS 5.9 downlink 20 for TCH/AFS 5.15 downlink 21 for TCH/AFS 4.75 downlink 22 for TCH/AHS 7.4 downlink 23 for TCH/AHS 6.7 downlink 24 for TCH/AHS 5.9 downlink 25 for TCH/AHS 5.15 downlink 26 for TCH/AHS 4.75 downlink
Formula:
AMRCHDIS[n] 100
(AMR full rate speech, 12.2 kbit/s, uplink) (AMR full rate speech, 10.2 kbit/s, uplink) (AMR full rate speech, 7.95 kbit/s, uplink) (AMR full rate speech, 7.5 kbit/s, uplink) (AMR full rate speech, 6.7 kbit/s, uplink) (AMR full rate speech, 5.9 kbit/s, uplink) (AMR full rate speech, 5.15 kbit/s, uplink) (AMR full rate speech, 4.75 kbit/s, uplink) (AMR half rate speech, 7.4 kbit/s, uplink) (AMR half rate speech, 6.7 kbit/s, uplink) (AMR half rate speech, 5.9 kbit/s, uplink) (AMR half rate speech, 5.15 kbit/s, uplink) (AMR half rate speech, 4.75 kbit/s, uplink) (AMR full rate speech, 12.2 kbit/s, downlink) (AMR full rate speech, 10.2 kbit/s, downlink) (AMR full rate speech, 7.95 kbit/s, downlink) (AMR full rate speech, 7.5 kbit/s, downlink) (AMR full rate speech, 6.7 kbit/s, downlink) (AMR full rate speech, 5.9 kbit/s, downlink) (AMR full rate speech, 5.15 kbit/s, downlink) (AMR full rate speech, 4.75 kbit/s, downlink) (AMR half rate speech, 7.4 kbit/s, downlink) (AMR half rate speech, 6.7 kbit/s, downlink) (AMR half rate speech, 5.9 kbit/s, downlink) (AMR half rate speech, 5.15 kbit/s, downlink) (AMR half rate speech, 4.75 kbit/s, downlink)
AMRCHDIS[1..26] Cell None
AMRCHDIS must be divided by 100 in this formula, because the measured value is in percent and KPI`s shouldn`t be in percent.
132
A50016-G5100-A042-1-7618
Information System
16.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 (a) AMRTFERUL (b) AMRTFERULCHT (c) AMRTFERDL 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.
13 (a) AMRTFERUL = AMRFRMUL [n + 13] * AMRCHDIS[n ] 100 n =1 AMRFRMUL [n, n + 13]
Short name:
Description:
Formula:
(b) AMRTFERULC HT[n] = AMRFRMUL [n + 13] AMRFRMUL [n, n + 13]

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) AMRTFERDL = AMRFRMDL [2] AMRFRMDL [1,2] Used param.: Elem. Object: Unit: Remarks: AMRFRMUL[1..26], AMRFRMDL[1..2], AMRCHDIS[1..13] Cell None
AMRCHDIS is in units of percent and must therefore be divided by 100 to get the weighting factor per channel mode.
133
A50016-G5100-A042-1-7618
Information System
16.19 Effective Frequency Load

Long name: (a) (b) (c) (d) Effective Frequency Load representing network view Effective Frequency Load representing users view Effective Frequency Load representing network view on cell level Effective Frequency Load representing users view on cell level
Short name:
Description:
(a) EFLNetwork (b) EFLUser (c) EFLNetworkCell (d) EFLUserCell The estimation of Effective Frequency Load is based on measurements of the mean number of busy channels per layer (MEBUTSLY) and the mean number of speech calls in a cell. The mean number of busy channels is measured separately and the following model for counting a channel as busy is underlying: Each CS FR call counts as 1 busy channel Each CS HR call counts as 1/2 busy channel Each PDCH in charge to the PCU counts as 1 busy channel In case the observed cell is a dual area/dual band standard cell, the measurement distinguishes between timeslots belonging to different areas/band. This measurement determines in intervals of 500 ms the number of channels busy for CS FR, CS HR and for PO. At the end of the granularity period the arithmetic mean value of the samples is calculated for each sub counter. (a)
EFLNetwork = MEBUTSLY [n 3 + 1, n 3 + 1 + 36] + 0.5 MEBUTSLY [ n 3 + 2, n 3 + 2 + 36] 100 8 moballoc
Formula:
(b)
EFLUser = MEBUTSLY [ n 3 + 1, n 3 + 1 + 36] + MEBUTSLY [ n 3 + 2, n 3 + 2 + 36] 100 8 moballoc
(c)
EFLNetworkCell =
(MEBUTSLY [n 3 + 1, n 3 + 1 + 36] + 0.5 MEBUTSLY [n 3 + 2, n 3 + 2 + 36]) 100 8 moballoc

n n
(d)
(MEBUTSLY [n 3 + 1, n 3 + 1 + 36] + MEBUTSLY [n 3 + 2, n 3 + 2 + 36]) EFLUserCell = 8 moballoc

n n
where: n=0..11 for certain layer moballoc the mobile allocation (the number of hopping frequencies used to carry traffic from numerator) can be evaluated basing on CM data; MEBUTSLY [all], cell % MEBUTSLY shall be measured during busy hour.
134
A50016-G5100-A042-1-7618
Information System
16.20 AMR Frame Erasure Rate for ARP-type Receiver

Long name: (a) Adaptive Multirate Average Frame Erasure Rate for ARP-type Receiver Uplink per channel type (b) Adaptive Multirate Average Frame Erasure Rate for ARP-type Receiver Downlink (a) AMRFERARPULCHT (b) AMRFERARPDL These indicators provide the Adaptive Multirate Frame Erasure Rate FER for ARP-type receiver. (a) AMRFERARPU LCHT[n] = NFRMULARP[ n + 13]
NFRMULARP[ n, n + 13]
Short name: Description: Formula:
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
(b) AMRFERARPD L = NFRMDLARP[ 2]
NFRMDLARP[ 1,2]
NFRMULARP [1..26], NFRMDLARP [1..2] Cell None ARP-type receivers will be a synonym for Single Antenna Interference Cancellation (SAIC) type receivers.
135
A50016-G5100-A042-1-7618
Information System
17 Availability related Performance Indicators

17.1 Transceiver Availability
Long name: Short name: Description: Formula: Used param.: Elem. Object: Unit: Remarks: (a) Tranceiver Availability (a) TRXAvail This indicator will give you the TRX Availability. (a) TRXAvail =
TRANAVTI [1] Granularity * 60s
TRANAVTI[1], Granularity in minutes TRX None None
17.2 TCH Distribution Rate

Long name: Short name: Description: Formula: (a) TCH Full Rate (b) TCH Half Rate (a) FR (b) HR This indicator will give you the Rate of configured Full Rate and Half Rate traffic channels compared to the total number of traffic channels. (a) FR = (b) HR = Used param.: Elem. Object: Unit: Remarks:
NRDEFTCH[3,9] NRDEFTCH[3,6,9,12]
NRDEFTCH[6,12] NRDEFTCH[3,6,9,12]
NRDEFTCH[1..12] Cell None
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.
136
A50016-G5100-A042-1-7618
Information System
17.3 TCH Availability

Long name: (a) TCH Availability Full Rate (b) TCH Availability Half Rate (c) TCH Availability Dual Rate (a) TCHAvailFR (b) TCHAvailHR (c) TCHAvailDR This indicator will give you the TCH Availability (Rate). (a) TCHAvailFR = (b) TCHAvailHR = (c) TCHAvailDR =
Short name:
NAVTCH[3,9 ] NRDEFTCH[3 ,9]

NAVTCH[6,12] NRDEFTCH[6 ,12]
NAVTCH[3,9] + 0,5 * NAVTCH[6,12] NRDEFTCH[3,9] + 0,5 * NRDEFTCH[6,12]
Used param.: NAVTCH[3,6,9,12], NRDEFTCH[3,6,9,12] Elem. Object: Cell Unit: Remarks: None
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'. Formula is based on mean values
137
A50016-G5100-A042-1-7618
Information System
17.4 SDCCH Availability

Long name: Short name: Description: Formula: (a) SDCCH Availability (a) SDCCHAvail This indicator will give you the SDCCH Availability (Rate). (a) SDCCHAvail =
NAVSDCCH [3] NDESDCCH[3]
NAVSDCCH[3], NDESDCCH[3] Cell None 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).
17.5 Soft Blocking Rate

Long name: Short name: Description: (a) Soft Blocking Rate (a) SoftBlockingRate The estimation of soft blocking rate is based on measurements of the number of calls admitted (counters ACADMCDMA) and rejected (counters ACREJCDMA) on the DMA layer. The ACADMCDMA counter provides the number of admitted CS speech calls on the DMA layer. It supervises the performance of the admission control (AC) on the DMA layer. Precondition for DMA admission control is an enabled DMA (Dynamic MAIO Allocation). For each DMA layer configured in the cell a separate counter is generated. This measurement is triggered by admitted CS speech calls on the DMA layer. The ACREJCDMA counter provides the number of rejected CS speech calls by AC on the DMA layer due to soft blocking (SBQ=TRUE) and/or due to too high load (EFL_DMA > max.EFL_DMA), i.e. if enableSoftBlocking=TRUE. Precondition for DMA admission control is an enabled DMA (Dynamic MAIO Allocation). The counter is not incremented if the call has been rejected for any other reasons. For each DMA layer configured in the cell a separate counter is generated. This measurement is triggered by rejected CS speech calls by AC on the DMA layer, i.e. enableSoftBlocking=TRUE. (a) SoftBlocki ngRate =
Formula: Used param.: Elem. Object: Unit:
ACREJCDMA [1,2] 100 ACADMCDMA [1, 2] + ACREJCDMA [1, 2]
ACREJCDMA, ACADMCDMA Cell %
138
A50016-G5100-A042-1-7618
Information System
Remarks:

This KPI can be used only in case Dynamic MAIO Allocation and Admission Control are activated.
139
A50016-G5100-A042-1-7618
Information System
18 GPRS Related Performance Indicators

18.1 User oriented KPIs
18.1.1 Number of TBF establishment attempts
Long Name: Short Name: Description : Formula: (a) TBF establishment attempts uplink (b) TBF establishment attempts downlink (a) TBFEstAttUL (b) TBFEstAttDL This indicator provides the number of TBF establishments for uplink and downlink. (a) TBFEstAttUL = NUACATCL[1..3] (b) TBFEstAttDL = NUACATCL[4..6]
Used param.: NUACATCL[all] Elem. Object: Cell Unit: Remark: None
18.1.2 Number of TBF establishment failures

Long Name: (a) (b) (c) (d) (a) (b) (c) (d) TBF establishment failed due to PDCH Congestion uplink TBF establishment failed due to PDCH Congestion downlink TBF establishment failed due to no reaction from mobile station uplink TBF establishment failed due to no reaction from mobile station downlink TBFEstFailConUL TBFEstFailConDL TBFEstFailNoReacUL TBFEstFailNoReacDL
Short Name:
Description : Formula:
This indicator provides the number of TBF establishment failures per cause. This indicator will measure in uplink and downlink direction. (a) TBFEstFailConUL = REJPDASS [7..9], (b) TBFEstFailConDL = REJPDASS [19..21],
140
A50016-G5100-A042-1-7618
Information System

(c) TBFEstFailNoReactUL = SUCPDASA [1..3] - SULACCEL[1..3] (d) TBFEstFailNoReacDL = SUCPDASA [4..6] - SULACCEL[4..6]
Used param.: REJPDASS [7..9,19..21], SUCPDASA [all], SULACCEL[all] Elem. Object: Cell Unit: Remark: None
18.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..3]
(b) TBFEstSuccDL = SULACCEL[4..6] Used param.: SULACCEL[all]; Elem. Object: Cell Unit: Remark: None
18.1.4 TBF establishment success rate

Long Name: Short Name: Description : Formula: (a) TBF establishment Success Rate Uplink (b) TBF establishment Success Rate Downlink (a) TBFEstSuccRateUL (b) TBFEstSuccRateDL This indicator provides the TBF establishment considering uplink and downlink directions. (a) TBFEstSuccRateUL = (b) TBFEstSuccRateDL = success probability
SULACCEL[1..3] NUACATCL[1..3]
SULACCEL[4..6] NUACATCL[4..6]
Used param.: SULACCEL[all]; NUACATCL[all] Elem. Object: Cell Unit: None
141
A50016-G5100-A042-1-7618
Information System
Remark:
18.1.5 TBF establishment failure rate (TBF loss rate)

Long Name: (a) (b) (c) (d) (a) (b) (c) (d) TBF establishment failure rate for PDCH congestion Uplink TBF establishment failure rate for PDCH congestion Downlink TBF establishment failure rate for no reaction from mobile Uplink TBF establishment failure rate for no reaction from mobile Downlink TBFEstFailRateConUL TBFEstFailRateConDL TBFEstFailRateNoReacUL TBFEstFailRateNoReacDL
Short Name:
This indicator provides the TBF establishment failure rate per cause considering uplink and downlink directions. (a) TBFEstFailRateConUL = (b) TBFEstFailRateConDL =
REJPDASS[7..9]
NUACATCL[1..3]
REJPDASS[19..21]
NUACATCL[4..6]
SUCPDASA [1..3] - SULACCEL[1..3]
(c) TBFEstFailRateNoReacUL = (d) TBFEstFailRateNoReacDL =
NUACATCL[1..3]
SUCPDASA [4..6] - SULACCEL[4..6]
NUACATCL[4..6]
Used param.: REJPDASS [7..9,19..21], NUACATCL[all], SUCPDASA[all], SULACCEL[all] Elem. Object: Cell Unit: Remark: None
18.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 of resources. The indicator distinguishes uplink and downlink direction. Formula: (a) TBFEstSuccRedRateUL = UNSPDCSE[1..6] / SULACCEL[1..3]
142
A50016-G5100-A042-1-7618
Information System

(b) TBFEstSuccRedRateDL = UNSPDCSE[9..14] / SULACCEL[4..6]
Used param.: UNSPDCSE[1..6, 9..14], SULACCEL[all], Elem. Object: Cell Unit: Remark:
18.1.7 Total number of normally released TBFs

Long Name: Short Name: Description : Formula: a) Normal Uplink TBF release b) Normal Downlink TBF release (a) TBFNormRelUl (b) TBFNormRelDL This indicator provides the number of normally released TBFs considering uplink and downlink directions. (a) TBFNormRelUl = SUCTETBF[1..3] (b) TBFNormRelDL = SUCTETBF[4..6]
Used param.: SUCTETBF[all] Elem. Object: Cell Unit: Remark: None
18.1.8 Total number of dropped TBFs

Long Name: Short Name: Description : a) Uplink TBF dropped due to any cause b) Downlink TBF dropped due to any cause (a) TBFDrAllCauseUL (b) TBFDrAllCauseDL This indicator provides the number of dropped TBFs for all causes considering uplink and downlink directions. (a) TBFDrAllCauseUL = UNSTETBF[1..3,7..9,13..15,19..21,25..27,31..33, 37..39, 43..45] (b) TBFDrAllCauseDL = UNSTETBF[4..6,10..12,16..18,22..24,28..30, 34..36, 40..42, 46..48]
Formula:
Used param.: UNSTETBF[1..48] Elem. Object: Cell Unit: Remark: None
Dropped means that a TBF is terminated in an abnormal way. But a
143
A50016-G5100-A042-1-7618
Information System

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..3] 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.
18.1.9 TBF drop distribution on causes

Long Name: Share of UL TBF drop due to expiry of supervision timer (T3169) Share of DL TBF drop due to expiry of supervision timer (T3195) Share of UL TBF drop due to preemption Share of DL TBF drop due to preemption 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) (a) (b) (c) (d) (e) (f) TBFDrShareTimerExpUL TBFDrShareTimerExpDL TBFDrSharePreemptionUL TBFDrSharePreemptionDL TBFDrShareCellResOrdUL TBFDrShareCellResOrdDL (a) (b) (c) (d) (e)
Short Name:
This indicator provides the distribution of TBF drops per cause considering uplink and downlink directions. (a) TBFDrShare TimerExpUL = (b) (c) (d) (e)
UNSTETBF[1 ..3] TBFDrAllCa useUL UNSTETBF[4 ..6] TBFDrShare TimerExpDL = TBFDrAllCa useDL UNSTETBF[7 ..9] TBFDrShare Preemption = UL TBFDrAllCa useUL UNSTETBF[1 0..12] TBFDrShare Preemption = DL TBFDrAllCa useDL UNSTETBF[2 5..27] TBFDrShare CellResOrd UL = TBFDrAllCa useUL
(f) TBFDrShare CellResOrd DL =
UNSTETBF[2 8..30] TBFDrAllCa useDL
Used param.: UNSTETBF[1..12,25..30], TBFDrAllCauseUL (18.1.8(a)), TBFDrAllCauseDL
144
A50016-G5100-A042-1-7618
Information System
(18.1.8(b))) Elem. Object: Cell Unit: Remark: None
18.1.10
Long Name: Short Name: Description : Formula:
TBF drop rate

(a) Uplink TBF drop rate (b) Downlink TBF drop rate (a) TBFDropRateUL (b) TBFDropRateDL This indicator provides the total TBF drop rate form MS point of view considering uplink and downlink directions. (a) TBFDropRat eUL = (b) TBFDropRat eDL =
UNSTETBF[1 ..3,13..15 ,19..21] SULACCEL[1 ..3]
UNSTETBF[4 ..6,16..18 ,22..24] SULACCEL[4 ..6]
Used param.: SULACCEL[all], UNSTETBF[1..6,13..24] Elem. Object: Cell Unit: Remark: None
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.
18.1.11
Long Name: Short Name: Description :
TBF Drop frequency

(a) Uplink TBF drops frequency (b) Downlink TBF drops frequency (a) TBFDrFrequUL (b) TBFDrFrequDL This indicator provides the TBF drop frequency as the mean number of TBF drops per hour TBF duration. Uplink and downlink directions are considered.
145
A50016-G5100-A042-1-7618
Information System
Formula: (a) TBFDrFrequUL =

TBFDrAllCauseUL * NACTTBF[5 - 8] TBFDrAllCauseDL *
(b) TBFDrFrequDL =
60 gran
60 gran NACTTBF[13 - 16]
Used param.: (a) NACTTBF[1-4, 9-12]; TBFDrAllCauseUL (18.1.8(a)), TBFDrAllCauseDL (18.1.8(b)) Elem. Object: Cell Unit: Remark: Occurrences per hour = (1 / hour) 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[5-8, 13-16] is sampled on a second basis (GMM and SM related TBFs might be shorter) NACTTBF[5-8, 13-16] is a real number with 4 digits after decimal point (x.yyyy). In case of low number (and short duration) of TBFs during a granularity period the result might be 0.01 or 0.001. Alternative formula (proposal):
TBFDrFrequUL = TBFDrAllCauseUL *
3600 NACTTBF[1 - 4] * MeanTBFDurUL
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 assigned (triggering of NACTTBF[5-8, 13-16]) and are seizured (triggering of NACTTBF[1-4, 9-12]) in different measurement intervals.
18.1.12
Mean time between TBF drop

(a) Mean time between TBF drop of uplink TBF (b) Mean time between TBF drop of downlink TBF (a) TBFDrMeanTimeUL (b) TBFDrMeanTimeDL This indicator provides the mean time between TBF drops related to one hour TBF duration. Uplink and downlink directions are considered. (a) TBFDrMeanTimeUL =
3600 TBFDrFrequUL
146
A50016-G5100-A042-1-7618
Information System

(b) TBFDrMeanTimeDL =
3600 TBFDrFrequDL
Used param.: TBFDrFrequUL (18.1.11(a)), TBFDrFrequDL(18.1.11(b)) Elem. Object: Cell Unit: Remark: Seconds Possible inaccuracy of formula: See remark on KPI 18.1.11 TBF Drop frequency
18.1.13
Long Name:
User data throughput per TBF on the air interface

(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 UserDataThrTBFAvUL UserDataThrTBFAvDL UserDataThrTBFCSUL UserDataThrTBFCSDL
Short Name: (a) (b) (c) (d)
Description : This indicator provides the mean LLC throughput on the air interface per active user, i.e. per TBF. Retransmissions are excluded; therefore only the amount of data transmitted on behalf of the application layer (here LLC) is considered The indicator provides the mean throughput related to a single subscriber, i.e. it provides the throughput the subscriber (or the application in the subscribers mobile) will experience. The uplink\downlink directions are separated. Indicators are provided for the throughput depending on the used Coding Scheme and in addition for the throughput averaged over all Coding Schemes. The KPI for the throughput depending on the used Coding Scheme is based on the model that an observed TBF has used that Coding Scheme throughout its life time complete granularity period. This is the achieved throughput if a TBF were 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 (a) UserDataThrTBFAvUL = (b) UserDataThrTBFAvDL =
Formula:
MUTHRF[1..13] 8 * NACTTBF [5..8] 1000 MUTHRF[14.. 26] - REMUTHRF[14.. 26] 8 * NACTTBF [13 .. 16] 1000
147
A50016-G5100-A042-1-7618
Information System
(c) UserDataThrTBFCSUL[c] =

MUTHRF[c] 8 * NACTTBF [5..8] * CSDistrCellUL[c] 1000
(d) UserDataThrTBFCSDL[c] = MUTHRF[c + 13] - REMUTHRF[c + 13] * 8 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
NACTTBF [13 .. 16] * CSDistrCellDL[c] 1000
Used param.: (a) NACTTBF [5-8, 13-16], MUTHRF[all], REMUTHRF[14 .. 26], CSDistrCellUL (18.3.4(a)), CSDistrCellDL (18.3.4(b)): weighting factors for the distribution of transmission durations for the different Coding Schemes. Elem. Object: Cell Unit: Remark: kbit per second
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).
148
A50016-G5100-A042-1-7618
Information System

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 (DL); therefore REMUTHRF (DL) 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 18.2.2 User Throughput on radio interface per cell Possible inaccuracy of formula: See remark on KPI 18.1.11 TBF Drop frequency
18.1.14
Long Name:
Packet resource reassignment attempts

(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 Formula: Network optimization (a) ReasAttTBFUL = NATPRRE[1] (b) ReasAttTBFDL = NATPRRE[2]
Used param.: NATPRRE[all] Elem. Object: Cell Unit: Remark: none
18.1.15
Long Name:
Packet resource reassignment failures

(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 reassignment procedures per cell separated for uplink and downlink TBFs.
149
A50016-G5100-A042-1-7618
Information System
Use case Formula: Network optimization
(a) ReasFailTBFUL = NATPRRE[1] - NSUPRRE[1] (b) ReasFailTBFDL = NATPRRE[2] - NSUPRRE[2]
Used param.: NATPRRE[all], NSUPRRE[all] Elem. Object: Cell Unit: Remark: none
18.1.16
Long Name:
Packet resource reassignment success rate

(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 cell separated for uplink and downlink TBFs. Use case Formula: (a) Network optimization
ReasSuccRateTBFUL = ReasSuccRateTBFDL =
NSUPRRE[1] NATPRRE[1] NSUPRRE[2] NATPRRE[2]
(b)
18.1.17
Long Name:
Packet resource reassignment failure rate

(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 separated for uplink and downlink TBFs.
150
A50016-G5100-A042-1-7618
Information System
Use case Formula: (a) Network optimization
Re asFailRateTBFUL = 1 Re asFailRateTBFDL = 1
NSUPRRE [1] NATPRRE[1] NSUPRRE [2] NATPRRE[2]
(b)
18.1.18
Long Name:
TBF downgrade / upgrade frequency

(a) (b) (c) (d) Uplink TBF upgrade frequency Uplink TBF downgrade frequency Downlink TBF upgrade frequency Downlink TBF downgrade frequency TBFUpgrFrequUL TBFDowngrFrequUL TBFUpgrFrequDL TBFDowngrFrequDL
Description : This indicator provides the TBF downgrade / upgrade frequency as the mean number of TBF downgrades / upgrades per one hour busy PDCH. Uplink and downlink directions are considered. Formula: (a) TBFUpgrFrequUL =
SERVUGDG [1] *
60 gran NALLPDCH[3] 60 gran NALLPDCH[3]
SERVUGDG [2] *
(b) TBFDowngrFrequUL =
SERVUGDG [3] *
(c) TBFUpgrFrequDL =
SERVUGDG [4] *
(d) TBFDowngrFrequDL =
Used param.: SERVUGDG [1 .. 4], NALLPDCH[3,6] Elem. Object: Cell
151
A50016-G5100-A042-1-7618
Information System
Unit: Remark:

Occurrences per hour = (1 / hour)
18.1.19
Long Name:
Mean TBF duration per traffic class

(a) (b) (c) (d) (e) (f) (g) (h) (a) (b) (c) (d) (e) (f) (g) (h) Mean Uplink TBF duration Mean Uplink TBF duration acc. to Interactive traffic class Mean Uplink TBF duration acc. to Streaming traffic class Mean Uplink TBF duration acc. to Background traffic class Mean Downlink TBF duration Mean Downlink TBF duration acc. to Interactive traffic class Mean Downlink TBF duration acc. to Streaming traffic class Mean Downlink TBF duration acc. to Background traffic class MeanTBFDurUL MeanTBFDurULInt MeanTBFDurULStream MeanTBFDurULBg MeanTBFDurDL MeanTBFDurDLInt MeanTBFDurDLStream MeanTBFDurDLBg
Short Name:
Description : Use case Formula:
This indicator provides the average TBF duration considering uplink and downlink directions. Network planning and optimization (a) MeanTBFDurUL =
NACTTBF [5 - 8] * gran NACTTBF[1 - 4] NACTTBF [6] * gran NACTTBF[2] NACTTBF [7] * gran NACTTBF[3]
(b) MeanTBFDurULInt =
(c) MeanTBFDurULStream = (d) MeanTBFDurULBg = (e) MeanTBFDurDL =
NACTTBF [8] * gran NACTTBF[4]
NACTTBF [13 - 16] * gran NACTTBF[9 - 12] NACTTBF [14] * gran NACTTBF[10] NACTTBF [15] * gran NACTTBF[11]
(f) MeanTBFDurDLInt =
(g) MeanTBFDurDLStream = (h) MeanTBFDurDLBg =
NACTTBF [16] * gran NACTTBF[12]
152
A50016-G5100-A042-1-7618
Information System
Used param.: NACTTBF[all] Elem. Object: Cell Unit: Remark: Seconds
18.1.20
Long Name:
Link adaptation frequency

(a) (b) (c) (d) Upward link adaptation frequency for uplink TBF Downward link adaptation frequency for uplink TBF Upward link adaptation frequency for downlink TBF Downward link adaptation frequency for downlink TBF LinkAdaptFrequUpwUL LinkAdaptFrequDownwUL LinkAdaptFrequUpwDL LinkAdaptFrequDownwDL
Description : This indicator provides the link adaptations frequency as the mean number of upward and downward link adaptations per one hour busy PDCH. Uplink and downlink directions are considered. Use Case Formula: (a) LinkAdaptFrequUpwUL =
LADAPTUD [1] *
LADAPTUD [2] *
(b) LinkAdaptFrequDownwUL =
LADAPTUD [3] *
(c) LinkAdaptFrequUpwDL =
60 gran NALLPDCH[6]
LADAPTUD [4] *
(d) LinkAdaptFrequDownwDL =
60 gran NALLPDCH[6]
Used param.: LADAPTUD [1 .. 4], NALLPDCH[3,6] Elem. Object: Cell Unit: Remark: Occurrences per hour (= 1 / hour)
153
A50016-G5100-A042-1-7618
Information System
18.1.21
Long Name:
Total number of discarded LLC frames

(a) (b) (c) (d) (e) (f) (a) (b) (c) (d) (e) (f) Total number of discarded Uplink LLC Frames per Interactive class Total number of discarded Uplink LLC Frames per Streaming class Total number of discarded Uplink LLC Frames per Background class Total number of discarded Downlink LLC Frames per Interactive class Total number of discarded Downlink LLC Frames per Streaming class Total number of discarded Downlink LLC Frames per Background class LLCIntFrDiscTotUL LLCStFrDiscTotUL LLCBgFrDiscTotUL LLCIntFrDiscTotDL LLCStFrDiscTotDL LLCBgFrDiscTotDL
Short Name:
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. network optimization from operator view, trouble shooting (a) (b) (c) (d) (e) (f) LLCIntFrDiscTotUL= DISCLPDU[11, 12] LLCStFrDiscTotUL= DISCLPDU[24, 25] LLCBgFrDiscTotUL= DISCLPDU[37,38] LLCIntFrDiscTotDL= DISCLPDU[1..10, 13] LLCStFrDiscTotDL= DISCLPDU[14..23, 26] LLCBgFrDiscTotDL= DISCLPDU[27..36, 39]
Use case Formula:
Used param.: DISCLPDU[all] Elem. Object: Cell Unit: Remark: None
18.1.22
Long Name:
LLC Frame discard rate

(a) (b) (c) (d) (e) (f) (a) (b) (c) (d) (e) Rate for Uplink LLC Frame Discard per Interactive class Rate for Uplink LLC Frame Discard per Streaming class Rate for Uplink LLC Frame Discard per Background class Rate for Downlink LLC Frame Discard per Interactive class Rate for Downlink LLC Frame Discard per Streaming class Rate for Downlink LLC Frame Discard per Background class LLCIntFrDiscRateUL LLCStFrDiscRateUL LLCBgFrDiscRateUL LLCIntFrDiscRateDL LLCStFrDiscRateDL
Short Name:
154
A50016-G5100-A042-1-7618
Information System
(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. network optimization from operator view, trouble shooting (a) LLCIntFrDi scRateUL = (b) LLCStFrDis cRateUL = (c) LLCBgFrDiscRateUL = (d) LLCIntFrDiscRateDL = (e) LLCStFrDis cRateDL = (f) LLCBgFrDiscRateDL =
DISCLPDU[1 1,12] NTRLLCFR[1 ] DISCLPDU[2 4,25] NTRLLCFR[2 ] DISCLPDU[3 7, 38] NTRLLCFR[3 ] DISCLPDU[1..10, 13] NTRLLCFR[4] DISCLPDU[1 4..23, 26] NTRLLCFR[5 ] DISCLPDU[2 7..36, 39] NTRLLCFR[6 ]
Use case Formula:
Used param.: DISCLPDU[all], NTRLLCFR[all] Elem. Object: Cell Unit: Remark: None
18.1.23
DTM establishment success rate

(a) DTM establishment Success Rate (a) DTMEstSuccRate This indicator provides the DTM establishment success probability. (a) DTMEstSuccRate =
SUDTMREQ [1 + 2] ATDTMREQ[1 .. 4]
Used param.: SUDTMREQ[all]; ATDTMREQ[all] Elem. Object: Cell Unit: Remark: None
18.1.24
Long Name: Short Name:
DTM establishment failure rate

(a) DTM establishment failure rate (a) DTMEstFailRate
155
A50016-G5100-A042-1-7618
Information System
Description : Formula: (a) DTMEstFail Rate =

This indicator provides the DTM establishment failure rate.
UNSDTMREQ [ 1 .. 3 ]
ATDTMEREQ [1 .. 4]
Used param.: UNSDTMREQ [all], ATDTMREQ[all] Elem. Object: Cell Unit: Remark: None Cause DTM Power Budget HO to another cell will not be considered as failure.
18.1.25
Long Name:
Weighted LLC User Data Throughput

(a) (b) (c) (d) (a) (b) (c) (d) Weighted GPRS LLC User Data Throughput, UL Weighted EDGE LLC User Data Throughput, UL Weighted GPRS LLC User Data Throughput, DL Weighted EDGE LLC User Data Throughput, DL WGprsLLCUsrThUL WEdgeLLCUsrThUL WGprsLLCUsrThDL WEdgeLLCUsrThDL
Short Name:
This indicator provides the Weighted LLC User Data Throughput UL/DL per technique.
(a) WGprsLLCUsrThUL =
MUTLLC[i] MUTLLC[i + 60]

i =1
MUTLLC[i + 60]
i =1
(b) WEdgeLLCUsrThUL =
MUTLLC[i + 5] MUTLLC[i + 65]

i =1
MUTLLC[i + 65]
i =1
(c) WGprsLLCUsrThDL =

i =1
MUTLLC[i + 70]
i =1
(d) WEdgeLLCUsrThDL =

i =1
MUTLLC[i + 75]
i =1
Used param.: MUTLLC [1..20, 61..80] Elem. Object: Cell
156
A50016-G5100-A042-1-7618
Information System
Unit: Remark: Kbyte / sec
Weighted LLC User Data Throughput is the throughput per user during Continuous Data Transmission
18.2 Network planning (dimensioning)

18.2.1 Total Throughput on air interface per cell
Long Name: Short Name: Description : (a) Total packet Throughput per cell on radio interface in uplink direction (b) Total packet Throughput per cell on radio interface in downlink direction (a) TotThrUmCellUL (b) TotThrUmCellDL 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. Network capacity planning. (a) TotThrUmCellUL = (MUTHRF[1..13] + REMUTHRF[1..13] + MSTHRF[1]) * 8 (b) TotThrUmCellDL = (MUTHRF[14..26] + MSTHRF[2] ) * 8 Used param.: MUTHRF[all], REMUTHRF[1 .. 13], MSTHRF[1,2] Elem. Object: Cell Unit: Remark: kbit/sec The DL retransmitted throughput is included in MUTHRF but not the UL retransmitted throughput
1000
Use Case Formula:
1000
18.2.2 User Throughput on radio interface per cell

Long Name: Short Name: Description : (a) User Data Throughput per cell on radio interface uplink (b) User Data Throughput per cell on radio interface downlink (b) UserThrUmCellUL (c) UserThrUmCellDL This indicator provides the mean LLC throughput on the air interface per cell. Retransmissions are excluded; therefore only the amount of data transmitted
157
A50016-G5100-A042-1-7618
Information System

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 a cell is accumulated over the whole granularity period and afterwards divided by the length of granularity period
Use Case Formula:
Network capacity planning. (a) UserThrUmCellUL = MUTHRF[1..13] *
8 1000
8 1000
(b) UserThrUmCellDL = (MUTHRF[14..26] - REMUTHRF[14..26]) * Used param.: MUTHRF[all], REMUTHRF[14 .. 26], Elem. Object: Cell Unit: Remark: kbit/sec
DL throughput: The retransmitted throughput in DL direction is included in the measurement MUTHRF (DL); therefore REMUTHRF (DL) has to be subtracted 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).
18.2.3 Uplink / Downlink distribution of user throughput on radio interface per cell
Long Name: Short Name: Description : Formula: (c) Uplink share of user throughput on radio interface (d) Downlink share of user throughput on radio interface (a) UserThrUmCellULShare (b) UserThrUmCellDLShare This indicator provides the uplink and downlink distribution of user packet data transmission per cell on radio interface. (a) UserThrUmCellULShare =
UserThrUmCellUL UserThrUmCellUL + UserThrUmCellDL
158
A50016-G5100-A042-1-7618
Information System

(b) UserThrUmCellDLShare =
UserThrUmCellDL UserThrUmCellUL + UserThrUmCellDL
Used param.: UserThrUmCellUL (18.2.2 (a)) UserThrUmCellDL (18.2.2 (c)) Elem. Object: Cell Unit: Remark: None None
18.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 (a) TotVolUmCellUL (b) TotVolUmCellDL 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. Network capacity planning. (a) TotVolUmCellUL = TotThrUmCellUL * gran * 60 (b) TotVolUmCellDL = TotThrUmCellDL * gran * 60
Short Name:
Description :
Use Case Formula:
Used param.: TotThrUmCellUL(18.2.1), TotThrUmCellDL (18.2.1), granularity period gran in minutes Elem. Object: Cell Unit: Remark: kbit
18.2.5 Total packet Throughput on Gb interface per cell

Long Name: Short Name: Description : (a) Total packet throughput on Gb uplink (b) Total packet throughput on Gb downlink (a) TotThrGbCellUL (b) TotThrGbCellDL This indicator provides the total packet throughput per cell on the Gb interface in the uplink/downlink direction.
159
A50016-G5100-A042-1-7618
Information System
The total packet throughput comprises user data (LLC layer) from traffic classes (interactive, streaming, background services) including BSSGP header and BSSGP signaling Formula:
8 1000 8 (b) TotThrGbCellDL = (MUTHBS[4..6] + MSTHBS[2]) * 1000

(a) TotThrGbCellUL = (MUTHBS[1..3] + MSTHBS[1]) *
Used param.: MUTHBS[all]; MSTHBS[1,2]; Elem. Object: Cell Unit: Remark: kbit/sec None
18.2.6 User data Throughput on Gb interface per cell

Long Name: Short Name: Description : Formula: (a) User Data Throughput on Gb uplink (b) User Data Throughput on Gb downlink (a) UserThrGbCellUL (b) UserThrGbCellDL This indicator provides the mean user data throughput on LLC layer per cell on the Gb interface in the uplink/downlink direction. (a) UserThrGbCellUL = MUTHBS[1..3] *
8 1000 8 (b) UserThrGbCellDL = MUTHBS[4..6] * 1000
Used param.: MUTHBS[all] Elem. Object: Cell Unit: Remark: kbit/sec None
18.2.7 Mean number of busy PDCH per cell

Long Name: Short Name: (a) Mean number of PDCHs busy per cell for UL transmission (b) Mean number of PDCHs busy per cell for DL transmission (a) MeanPDCHBusyCellUL
160
A50016-G5100-A042-1-7618
Information System
Description : Use case Formula:

(b) MeanPDCHBusyCellDL This KPI provides the mean number of PDCHs per cell with at least one UL TBF respectively at least one downlink TBF in progress Network planing (a) MeanPDCHBusyCellUL = NALLPDCH [3] (b) MeanPDCHBusyCellDL = NALLPDCH [6]
Used param.: NALLPDCH [3,6] Elem. Object: Cell Unit: Remark: None None
18.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 (a) MeanBusyPdchUtilCellUL (b) MeanBusyPdchUtilCellDL 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 Formula: (a)
MeanBusyPdchUtilCellUL = 2*( (NTRAPDU[1..11] + NRETPDU [1 ..11]) + (NTRAPDU[11.13] + NRETPDU [11.13]) MSTHRF[1] + ) gran * 60 20 NALLPDCH [3]
Short Name: Description :
Network planning
161
A50016-G5100-A042-1-7618
Information System
(b)
MeanBusyPdchUtilCellDL = NTRAPDU[14..23] + NTRAPDU[24..26] MSTHRF[2] 2*( + ) gran * 60 20 NALLPDCH[6]
Used param.: NTRAPDU [all], NRETPDU [1 .. 13], MSTHRF[1,2], NALLPDCH [3,6] Elem. Object: Cell Unit: Remark: percentage It is noted that for CS1 .. CS4 and MSC1 .. MSC6 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)
18.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 (a) (b) (c) (d) MeanUserThrBusyPdchUL MeanUserThrBusyPdchDL MeanUserThrBusyPdchCSUL MeanUserThrBusyPdchCSDL
Short Name:
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
162
A50016-G5100-A042-1-7618
Information System

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 (a) MeanUserThrBusyPdchUL = (b) MeanUserThrBusyPdchDL =
Formula:
MeanPDCHBitRateUL NALLPDCH[3] MeanPDCHBitRateDL NALLPDCH[6]

PDCHBitRateULCS[c] NALLPDCH [3] * CSDistrCellUL [c]
(c) MeanUserThrBusyPdchCSUL[c] = (d) MeanUserThrBusyPdchCSDL[c] =
PDCHBitRateDLCS[c] NALLPDCH [6] * CSDistrCellDL [c]
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 (18.3.4(a)), CSDistrCellDL (18.3.4(b)): weighting factors for the distribution of transmission durations for the different Coding Schemes. MeanPDCHBitRateUL(18.2.14(a)), MeanPDCHBitRateDL (18.2.14(d)), PDCHBitRateULCS (18.2.13(a)), PDCHBitRateDLCS (18.2.13(b)) Elem. Object: Cell Unit: Remark: kbit/sec
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 per PDCH is higher.
163
A50016-G5100-A042-1-7618
Information System

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 beginning 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) 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 (DL); therefore REMUTHRF (DL) 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 18.2.2 User Throughput on radio interface per cell Possible inaccuracy of formula: See remark on KPI 18.1.11 TBF Drop frequency
18.2.10
Mean number of simultaneously active TBFs per cell

(a) Mean number of simultaneously active TBF per cell uplink (b) Mean number of simultaneously active TBF per cell downlink (a) MeanActTbfUL (b) MeanActTbfDL This indicator provides the mean number of simultaneously active TBFs for the uplink and downlink direction.
164
A50016-G5100-A042-1-7618
Information System
Use case Formula:

Network planning: how many MS have data transmission simultaneously in a cell. (a) MeanActTbfUL = NACTTBF[5 .. 8]; (b) MeanActTbfDL = NACTTBF[13 ..16];
Used param.: NACTTBF[5..8, 13..16]; Elem. Object: Cell Unit: Remark: None None
18.2.11
Long Name: Short Name: Description : Use case
Mean number of TBFs multiplexed on same PDCH

(a) Mean number of uplink TBFs multiplexed on the same PDCH (b) Mean number of downlink TBFs multiplexed on the same PDCH (a) MeanTBFMultiplPDCHUL (b) MeanTBFMultiplPDCHDL This indicator provides the mean number of TBFs multiplexed on the same PDCH (horizontal allocation) for the uplink and downlink direction. Network optimization. E.g. tuning of the parameters for PDCH allocation (in connection with the KPIs for packet throughput per user, see chapter 18.1.13) (a) MeanTBFMultiplPDCHUL = NTBFPDC[2]; (b) MeanTBFMultiplPDCHDL = NTBFPDC[4];
Formula:
Used param.: NTBFPDC[2,4]; Elem. Object: Cell Unit: Remark: None None
18.2.12
Long Name: Short Name: Description : Use case Formula:
Mean number of allocated PDCHs per TBF

(a) Mean number of allocated PDCHs per uplink TBF (b) Mean number of allocated PDCHs per downlink TBF (a) MeanAllocPdchTbfUL (b) MeanAllocPdchTbfDL This indicator provides the mean number of PDCHs assigned to a TBF for the uplink and downlink direction (horizontal allocation) Monitoring of MS behavior: penetration of the MS multi slot classes (a) MeanAllocPdchTbfUL =
NTBFPDC[2] * NALLPDCH [3] NACTTBF[5..8],
165
A50016-G5100-A042-1-7618
Information System

(b) MeanAllocPdchTbfDL =
NTBFPDC[4] * NALLPDCH [6] NACTTBF[13..16]
Used param.: NACTTBF[5..8, 13..16]; NALLPDCH [3,6]; NTBFPDC[2,4] Elem. Object: Cell Unit: Remark: None 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
MeanAllocPdchTbfDL =
NTBFPDC[4] * NALLPDCH [6] NACTTBF[13..16]
NTBFPDC[4] = 2.5 NALLPDCH[6] = 4 PDCH * 3 min / 15min = 0.8 PDCH NACTTBF[13..16] = (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 mean value of the samples is calculated.
MeanAllocPdchTbfDL = 2.5 * 0.8/0.6 = 3.33 PDCHs/TBF
166
A50016-G5100-A042-1-7618
Information System
There is the possibility that the evaluation of these formulas gives unreliable results in function of GPRS traffic typology, since UL and DL TBF can be allocated on same PDCH, but, at the moment, this is the best it can be done in BR90 with the existing counters.
18.2.13
PDCH Bit Rate per Coding Scheme

(a) PDCH Bit Rate per cell per coding scheme in uplink direction (b) PDCH Bit Rate per cell per coding scheme in downlink direction (a) PDCHBitRateULCS (b) PDCHBitRateDLCS 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) PDCHBitRateULCS[c] = (b) PDCHBitRateDLCS[c] =
BlocSize NTRAPDU[c] * NTRAPDU[c]+ NRETPDU[c] 20(ms)
NTRAPDU [c + 13] NRETPDU [c + 13] BlocSize * 20(ms ) NTRAPDU [c + 13]

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= c=1 c=2 c=3 c=4 c=5 c=6 c=7 c=8 c=9 c=10 c=11 c=12 c=13 Coding scheme CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9 BlocSize (bits) 160 240 288 400 176 224 296 352 448 592 896 1088 1184
Elem. Object: Cell Unit: Remark: kbit/sec
Please note that RLC/MAC signaling is included in this indicator. Also retransmissions are considered.
167
A50016-G5100-A042-1-7618
Information System

Different treatment of UL and DL direction in the formula DL throughput: o The retransmitted throughput in DL direction is included in the 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).
18.2.14
Long Name:
Mean PDCH Bit Rate

(a) (b) (c) (d) (a) (b) (c) (d) Mean PDCH Bit Rate for GPRS per cell in uplink direction Mean PDCH Bit Rate for EDGE per cell in uplink direction Mean PDCH Bit Rate for GPRS per cell in downlink direction Mean PDCH Bit Rate for EDGE per cell in downlink direction MeanPDCHBitRateGprsUL MeanPDCHBitRateEdgeUL MeanPDCHBitRateGprsDL MeanPDCHBitRateEdgeDL
Short Name:
Description :
This indicator provides the average LLC packet throughput per PDCH. The uplink and downlink directions are separated. Indicators are provided for the throughput cumulated over all Coding Schemes.
Use case Formula: (a) MeanPDCHBitRateGprsUL = (b) MeanPDCHBitRateEdgeUL = (c) MeanPDCHBitRateGprsDL = (d) MeanPDCHBitRateEdgeDL =
PDCHBitRateULCS[c] * CSDistrCellUL[c]
c =1
PDCHBitRateULCS[c] * CSDistrCellUL[c]
c =5 4
13
PDCHBitRateDLCS[c] * CSDistrCellDL[c]
c =1 13
PDCHBitRateDLCS[c] * CSDistrCellDL[c]
c =5
Used param.: PDCHBitRateULCS[all] (18.2.13(a)), PDCHBitRateDLCS[all] (18.2.13(b)) CSDistrCellUL (18.3.4(a)), CSDistrCellDL (18.3.4(b)): weighting factors for the distribution of transmission durations for the different Coding Schemes. Elem. Object: Cell Unit: Remark: kbit/sec None
168
A50016-G5100-A042-1-7618
Information System
18.2.15
Long Name:
Percent Timeslot Resources Achieved

(a) (b) (c) (d) Percent Timeslot Resources Achieved for GPRS in uplink direction Percent Timeslot Resources Achieved for EDGE in uplink direction Percent Timeslot Resources Achieved for GPRS in downlink direction Percent Timeslot Resources Achieved for EDGE in downlink direction
Short Name:
Description :
(a) PercentGprsTSLAchievedUL (b) PercentEdgeTSLAchievedUL (c) PercentGprsTSLAchievedDL (d) PercentEdgeTSLAchievedDL This KPI provides the number of Assigned Timeslots to the number of Optimum CAA Timeslots Requested. The Assigned Timeslots are timeslots, which are assigned by the RRM to a MS for a real TBF. The number of Optimum CAA Timeslots Requested is the highest prioritized timeslot configuration calculated by the Minimum Square Method of the CAA MS Configuration block.
Formula: (a) PercentGprsTSLAchievedUL =

i =1
MUTLLC[i + 60]
i =1
(b) PercentEdgeTSLAchievedUL =

i =1
MUTLLC[i + 65]
i =1
(c) PercentGprsTSLAchievedDL =

i =1
MUTLLC[i + 70]
i =1
(d) PercentEdgeTSLAchievedDL =

i =1
MUTLLC[i + 75]
i =1
Used param.: MUTLLC[41..80]. Elem. Object: Cell Unit: Remark: % None
169
A50016-G5100-A042-1-7618
Information System
18.3 Network optimization

18.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 (a) RetransRateUmCellULCS (b) RetransRateUmCellDLCS 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 KPI used for Network quality optimization: -> optimize C/I thresholds for coding scheme selection (a) RetransRateUmCellULCS[c] = (b) RetransRateUmCellDLCS[c] =
Use case Formula:
NRETPDU[c] NTRAPDU[c] + NRETPDU[c] NRETPDU[13+ c] NTRAPDU[13+ c]
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 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], NRETPDU[all], Elem. Object: Cell Unit: none
170
A50016-G5100-A042-1-7618
Information System
Remark:

In DL direction NTRAPDU contains the retransmitted PDUs. But in UL directions retransmission is not included in NTRAPDU.
18.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 (a) UserThrRetrCellUmULCS (b) UserThrRetrCellUmDLCS This indicator provides the retransmitted user Throughput on the radio interface per cell per coding scheme. The uplink\downlink directions are separated. KPI used for Network quality optimization: -> optimize C/I thresholds for coding scheme selection (a) UserThrRetrCellUmULCS[c] (b) UserThrRetrCellUmDLCS[c]
Use Case Formula:
= REMUTHRF[c] *
8 1000 8 1000
= REMUTHRF[13 + c] *
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.: REMUTHRF[all], Elem. Object: Cell Unit: Remark: kbit/sec
171
A50016-G5100-A042-1-7618
Information System
18.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 (a) UserDataUmCellULCSDistr (b) UserDataUmCellDLCSDistr 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 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) (a) UserDataUmCellULCSDistr[c] = (b) UserDataUmCellDLCSDistr[c] =
Use Case
Formula:
MUTHRF[c] MUTHRF[1..13]
MUTHRF[13+ c] MUTHRF[14..26]
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.: MUTHRF[all], Elem. Object: Cell Unit: none
172
A50016-G5100-A042-1-7618
Information System
Remark:

Remarks In DL directions the retransmission is included in MUTHRF[14 .. 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.
18.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 (a) CSDistrCellUL (b) CSDistrCellDL 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 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) (a) CSDistrCellUL[c] = for c = 1 .. 10
Use Case
Formula:
NTRAPDU[c] NTRAPDU[1..10] + * NTRAPDU[11..13] * NTRAPDU[c] NTRAPDU[1..10] + * NTRAPDU[11..13] NTRAPDU[c + 13] NTRAPDU[14.. 23] + * NTRAPDU[24.. 26] * NTRAPDU[c + 13] NTRAPDU[14.. 23] + * NTRAPDU[24.. 26]
CSDistrCellUL[c] =
for c = 11 .. 13 (b) CSDistrCellDL[c] = for c = 1 .. 10
CSDistrCellDL[c] =
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
173
A50016-G5100-A042-1-7618
Information System
c=5 c=6 c=7 c=8 c=9 c = 10 c = 11 c = 12 c = 13 Used param.: NTRAPDU[all] Elem. Object: Cell Unit: Remark: none

coding scheme MCS1 coding scheme MCS2 coding scheme MCS3 coding scheme MCS4 coding scheme MCS5 coding scheme MCS6 coding scheme MCS7 coding scheme MCS8 coding scheme MCS9
Remarks In DL directions the retransmission is included in NTRAPDU[14 .. 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).
18.4 Cell Reselection

18.4.1 Number of network controlled Intra BSC cell reselection attempts per cell
Long name: Short name: Description: Formula: (a) Number of network controlled Intra BSC cell reselection attempts per cell (a) NumNCIntrBSCCellResAtt This indicator provides the number of network controlled Intra BSC cell reselection attempts per cell (a) NumNCIntrBSCCellResAtt = ATCRORIG [1]
Used param.: ATCRORIG [1] Elem. Object: Cell Unit: Remarks: None None
174
A50016-G5100-A042-1-7618
Information System
18.4.2 Number of successful network controlled Intra BSC cell reselections per cell
Long name: Short name: Description: Formula: (a) Number of successful network controlled Intra BSC cell reselections per cell (a) NumNCIntrBSCCellResSuc This indicator provides the number of successful network controlled Intra BSC cell reselections per cell (a) NumNCIntrBSCCellResSuc = SUCRORIG[1]
Used param.: SUCRORIG[1] Elem. Object: Cell Unit: Remarks: None None
18.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 (a) (b) (c) (d) (e) (f) (g) NumNCIntrBSCCellResFailFrequNotImpl NumNCIntrBSCCellResFailFrequNoRespTarget NumNCIntrBSCCellResFailAccessRejTarget NumNCIntrBSCCellResFailCSOngoing NumNCIntrBSCCellResFailAnonyAccess NumNCIntrBSCCellResFailGMMStandby NumNCIntrBSCCellResFailForcedStandby
Short name:
Description:
These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per cell per cause
175
A50016-G5100-A042-1-7618
Information System
Formula: (a) (b) (c) (d) (e) (f) (g)

NumNCIntrBSCCellResFailFrequNotImpl = UNCRORIG [1] NumNCIntrBSCCellResFailFrequNoRespTarget = UNCRORIG [2] NumNCIntrBSCCellResFailAccessRejTarget = UNCRORIG [3] NumNCIntrBSCCellResFailCSOngoing = UNCRORIG [4] NumNCIntrBSCCellResFailAnonyAccess = UNCRORIG S [5] NumNCIntrBSCCellResFailGMMStandby = UNCRORIG [6] NumNCIntrBSCCellResFailForcedStandby = UNCRORIG [7]
Used param.: UNCRORIG [all] Elem. Object: Cell Unit: Remarks: None None
18.4.4 Network controlled Intra BSC cell reselection success rate

Long name: Short name: Description: Formula: (a) Success rate for network controlled Intra BSC cell reselections (a) NCIntrBSCCellSucRate This indicator provides the success rate for network controlled Intra BSC cell reselection per cell (a) NCIntrBSCCellSucRate =
SUCRORIG [ 1,3 ] ATCRORIG [ 1,9 ]
Used param.: SUCRORIG[1], ATCRORIG [1] Elem. Object: Cell Unit: Remarks: None None
18.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
176
A50016-G5100-A042-1-7618
Information System
the standby state Short name: (a) (b) (c) (d) (e) (f)
NCIntrBSCResFailRateFrequNotImpl NCIntrBSCResFailRateNoRespTarget NCIntrBSCResFailRateAccessRejTarget NCIntrBSCResFailRateCSOngoing NCIntrBSCResFailRateGMMStandby NCIntrBSCResFailRateForcedStandby
These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per cause (a) NCIntrBSCResFailRateFrequNotImpl = (b) NCIntrBSCResFailRateNoRespTarget =
UNCRORIG[1] ATCRORIG[1]
UNCRORIG[2] ATCRORIG[1] UNCRORIG[3] ATCRORIG[1]
(c) NCIntrBSCResFailRateAccessRejTarget = (d) NCIntrBSCResFailRateCSOngoing =
UNCRORIG[4] ATCRORIG[1]
(e) NCIntrBSCResFailRateGMMStandby = (f) NCIntrBSCResFailRateForcedStandby = Used param.: UNCRORIG[1..6], ATCRORIG [1] Elem. Object: Cell Unit: Remarks: None None
UNCRORIG[5] ATCRORIG[1] UNCRORIG[6] ATCRORIG[1]
18.4.6 Network controlled cell reselection failure rate

Long name: Short name: Description: Formula: (a) Network controlled cell reselection failure rate (a) NCResFailRate This indicator provides the number of unsuccessful network controlled cell reselections. (a) NCResFailRate =
UNCRORIG[all] ATCRORIG[1,2,3,9,10]
Used param.: UNCRORIG[all], ATCRORIG [1,2,3,9,10] Elem. Object: Cell Unit: Remarks: None In general this formula count as far as possible from network point of view.
177
A50016-G5100-A042-1-7618
Information System
19 Miscellaneous Performance Indicators

19.1 BSC1 Processor load
Long name: (a) Mean BSC1 MPCC Processor load (b) Mean BSC1 TDPC Processor load (c) Mean BSC1 PPXU / PCU Processor load (x) (a) MPCCLoad (b) TDPCLoad (c) PPXULoad(x) These indicators provide the processor load at the BSC1 for the MPCC (Administrative Processor), TDPC (Telephony Processor) and for the Packet Control Units (PCUs / PPXUs) (up to 12)
Short name:
Description:
Formula:
BSCPRCLD[2 ] 100 BSCPRCLD[5 ] (b) TDPCLoad = 100

(a)
MPCCLoad =
(c) PPXULoad(x) =
BSCPRCLD[8 + x * 3] 100
x = PPXU / PCU number (Range=0..11)
Used param.: BSCPRCLD[2, 5, 8, 11, 14, 17, 20, 23, 26, 29, 32, 35, 38, 41] Elem. Object: BSC Unit: Remarks: None None
19.2 Basic eBSC Processor load

Long name: (a) (b) (c) (d) (e) (a) (b) (c) (d) (e) Mean Basic eBSC MCP Processor load Mean Basic eBSC APM Processor load Mean Basic eBSC SMAC Processor load(x) Mean Basic eBSC LIET Processor load(y) Mean Basic eBSC PCU Processor load (z) MCPLoad APMLoad SMACLoad(x) LIETLoad(y) PCULoad(z)
Short name:
Description:
These indicators provide the processor load at the Basic eBSC for the MCP
178
A50016-G5100-A042-1-7618
Information System

(Administrative Processor), APM(Telephony Processor), SMAC (Ethernet Interface Processor), LIET(Interface Processor) (up to 9) and for the Packet Control Units (PCUs) (up to 10)
Formula:
BSCPRCLD[1 ] 100 BSCPRCLD[3 ] (b) AMPLoad = 100

(a)
MCPLoad =
(c) SMACLoad(x) =
BSCPRCLD[5 + x * 2] 100
x = SMAC number (Range=0..1)
(d) LIETLoad(y) =
BSCPRCLD[9 + y * 2] 100 BSCPRCLD[27 + z * 2] 100
y = LIET number (Range=0..8)
(e) PCULoad(z) =
z = PCU number (Range=0..9)
Used param.: BSCPRCLD[1, 3, 5, 7, 9, ..., 45] Elem. Object: Basic eBSC Unit: Remarks: None None
19.3 HighEnd eBSC Processor load

Long name: (a) (b) (c) (d) (e) (f) (g) (a) (b) (c) (d) (e) (f) (g) Mean HighEnd eBSC MCP Processor load Mean HighEnd eBSC APM Processor load Mean HighEnd eBSC APD Processor load(v) Mean HighEnd eBSC SMAC Processor load(w) Mean HighEnd eBSC LIET Processor load(x) Mean HighEnd eBSC PCU Processor load (y) Mean HighEnd eBSC SDH Processor load(z) MCPLoadHE APMLoadHE APDLoadHE(v) SMACLoadHE(w) LIETLoadHE(x) PCULoadHE(y) SDHLoadHE(z)
Short name:
Description:
These indicators provide the processor load at the HighEnd eBSC for MCP (Administrative Processor), APM(Telephony Processor), APD(Telephony Processor) (up to 5),
179
A50016-G5100-A042-1-7618
Information System

SMAC (Ethernet Interface Processor) (up to 4), LIET(Interface Processor) (up to 9) Packet Control Units (PCUs) (up to 24 slots) and for the SDH (STM1 Interface Processor) (up to 4)
Formula:
(a)
BSCPRCLD[1 ] 100 BSCPRCLD[3 ] (b) AMPLoadHE = 100 MCPLoadHE =

BSCPRCLD[5 + v * 2] 100 BSCPRCLD[15 + w * 2] 100
(c) APDLoadHE(v) =
x = APD number (Range=0..4)
(d) SMACLoadHE(w) =
w = SMAC number (Range=0..3)
(e) LIETLoadHE(x) =
BSCPRCLD[23 + x * 2] 100 BSCPRCLD[41 + y * 2] 100 BSCPRCLD[89 + z * 2] 100
x = LIET number (Range=0..8)
(f) PCULoadHE(y) =
y = PCU slot number (Range=0..23)
(g) SDHLoadHE(z) =
z = SDH number (Range=0..3) Used param.: BSCPRCLD[1, 3, 5, 7, 9, ..., 95] Elem. Object: HighEnd eBSC Unit: Remarks: None None
180
A50016-G5100-A042-1-7618
Information System
19.4 BTSE Processorload

Long name: Short name: Description: Formula: (a) Mean BTSE Processor load (a) BTSEPRLD This indicator provides the mean BTSE processor load.
BTSEPRLD =
(a) Used param.: BTSEPRLD[1] Elem. Object: BTSM Unit: Remarks: None None
BTSEPRLD[1 ] 100
19.5 PCU Occupancy Rate

Long name: (a) (b) (c) (d) (a) (b) (c) (d) PCU Occupancy Rate PCU Occupancy Peak Rate PCU Occupancy BSC Rate PCU Occupancy BSC Peak Rate PCUOccRate PCUOccPeakRate PCUOccBSCRate PCUOccBSCPeakRate
Short name:
Description:
This indicator will give you the PCU Occupancy Rate, by meaning the rate of used PDT compared to the available PDTs for a certain PCU. The main use is the supervision of the PCU occupancy for preventing PCU congestions in time e.g. by reconfiguring the network to get almost balanced load for the different PCUs or by increasing the number of PCUs. (a) PCUOccRate[n] = NPDTPCU[n*3+3] / PDTcapacity (b) PCUOccPeakRate [n] = NPDTPCU[n*3+2] / PDTcapacity n = PCU number (Range= 0, 1, 2, .., 11) (c) PCUOccBSCRate =
NPDTPCU[3, 6,9,12,15,18,21,24,27,30,33,36] BSCPDTCapacity NPDTPCU[2, 5,8,11,14,17,20,23,26,29,32,35] BSCPDTCapacity
Formula:
(d) PCUOccBSCPeakRate =
Related to the BSC hardware, the BSC can have different number of PCUs with a certain PDT capacity as follows: BSS Release BR9.0 BSC type BSC1 PCU HW type PPXU # PCU per BSC 12* # PDT per PCU 256
181
A50016-G5100-A042-1-7618
Information System
BR9.0 Used param.: Elem. Object: Unit: Remarks: eBSC

UPM 11* 850
* 1 UPM can be used as central NS router NPDTPCU[1..36] PCU None None
19.6 Paging Response / Location Update Ratio per Cell

Long name: Short name: Description: Formula: (a) Paging Response / Location Update Ratio per Cell (a) PagRespLocUpdRatioPerCell This indicator will give you the ratio between Pagings and Location Updates within a single cell. (a) PagRespLocUpdRatioPer Cell =
NSUCCHPC [1, 9, 17] NSUCCHPC [5,13,21]
Used param.: NSUCCHPC [1,5,9,13,17,21] Elem. Object: Cell Unit: Remarks: None The Paging Response Ratio / Location Update Ratio per cell is related to the Immediate Assignment Procedure.
182
A50016-G5100-A042-1-7618
Information System
19.7 BSC <-> MSC/SMLC CCS7 Load

Long name: (a) BSC -> MSC CCS7 Load (b) MSC -> BSC CCS7 Load (c) Total BSC <-> MSC CCS7 Load (a) Y_BSC->MSC (b) Y_MSC->BSC (c) Y_BSC<->BSC Approximate load on the Link Set between BSC and MSC, which were caused of MSUs sent by BSC, vice versa and total. (a) Y _ BSC > MSC = (b) Y _ MSC > BSC =
Short name:
NMSUTRAS [1] MSU _ Length 1Min Erl GRAN 8000byte / s 60 s NMSUREC[1] MSU _ Length 1Min Erl GRAN 8000byte / s 60s
(c) Y_BSC < - > MSC =
Y_BSC- > MSC + Y_MSC- > BSC Erl 2
Used param.: NMSUTRAS[1], NMSUREC[1], Granularity in minutes Elem. Object: Cell Unit: Remarks: Erlang
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.
19.8 Frame Relay Link Utilization

Long name: Short name: Description: Formula: (a) FRL Utilization (a) FRLUtil This indicator will give you the Frame Relay Link Utilization on the Gb interface by meaning of the carried Frame Relay data per NSVC. (a) FRLUtil = MFRLDATA [1,2] / Capacity FRL Capacity FRL: The FRL is an n X 64 kbit/s physical channel, created over a PCM line, represented by PCMG/PCMA objects. Used param.: MFRLDATA [all] Elem. Object: NSVC Unit: Remarks: kbit/s None
183
A50016-G5100-A042-1-7618
Information System
19.9 ARP-type Receiver Penetration

Long name: Short name: Description: Formula: (a) ARP-type Receiver Penetration Rate (a) ARPPenetrationRate This indicator will give you the penetration of Advance Receiver Performance (ARP) - type receiver and conventional receiver. (a) ARPPenetrationRate =
SUCTCHARP[1,2] SUCTCHSE [1,2]
Used param.: SUCTCHARP[1,2], SUCTCHSE[1,2] Elem. Object: cell Unit: Remarks: none ARP-type receivers will be a synonym for Single Antenna Interference Cancellation (SAIC) type receivers.
20 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,
184
A50016-G5100-A042-1-7618
Information System

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.
185
A50016-G5100-A042-1-7618
Information System
21 Appendix
21.1 List of BSS Performance Measurements
Short Name AALTCHTI ABISPDIS ABISPSUP ACADMCDMA ACREJCDMA AININIRH AISHINTE AISHINTR AMRCHDIS AMRFRMDL AMRFRMUL AMRSIDUL AMRVAR AOINTESH AOUINIRH ARPAPDAS ARPSPDAS ASDCALTI ATCHSMBS ATCRORIG ATDTMREQ ATIMASCA ATINBHDO ATINHIAC ATINHIRC ATOISHDO ATSDCMBS ATTCHSEI BSCPRCLD BTSEPRLD CFERRXQU CHALNHLY CNSPRCLD CRXLVQUD CRXLVQUU Long Name All available TCH allocated time Abis Pool Distribution Abis Pool Supervision Number of Calls Admitted on the DMA Layer Number of Calls Rejected on the DMA Layer Attempted incoming internal intercell Handovers per originating cell Attempted Internal SDCCH Handovers Intercell Attempted internal SDCCH Handovers Intracell Adaptive Multirate channel type uplink/downlink distribution Frame measurements for Adaptive Multi-Rate (AMR) on uplink busy TCHs Frame measurements for Adaptive Multi-Rate (AMR) on downlink busy TCHs SID_UPDATE frame measurements for Adaptive Multi-Rate (AMR) on uplink busy TCHs Voice Activity Rate for Adaptive Multi-Rate (AMR) on uplink/downlink busy TCHs Attempted MSC controlled SDCCH Handovers Attempted outgoing intercell Handovers per cause, per neigh-bourcell relationship Number Of Attempted PDCH Assignments (UP/DL) with ARP priority Number Of Successful PDCH Assignments (UP/DL) with ARP priority All available SDCCH allocated time Attempted TCH seizures meeting a TCH blocked state (Fullrate/Halfrate) Attempted network supported cell reselections per cause. Number of attempts to establish a DTM (UL/DL) per Cell Attempted immediate assignment procedures, per cause Attempted outgoing inter BSC Handovers per neighbour cell relationship Attempted internal Handovers, intracell, per cause Attempted internal Handovers, intercell, per cause Attempted Outgoing Intersystem Handover per neighbourcell per cause Attempted SDCCH seizure meeting an SDCCH blocked state Attempted TCH seizures (Fullrate/Halfrate) BSC processor load BTSE processor load Correlated FER to RXQUAL measurements Number of Channel Allocation Requests Not Served in the Highest Layer or at all Central NS functionality load Correlated RXLEV to RXQUAL measurements (downlink) Correlated RXLEV to RXQUAL measurements (uplink)
186
A50016-G5100-A042-1-7618
Information System
CRXLVTAD CRXLVTAU DASPUNT DISCLPDU DLKSERST DLKUNCON DSLUNAV FACCHSUP HOFITABS IFRMABIS IFRMABSC ILUPLKIC LADAPTUD LLCQULEV LOCAUTCH MAXBUSDC MBTCHCHT MBTSPWR MBUSYSDC MBUSYSSP MDURTCRQ MDURTCSD MEBUSTCH MEBUTSLY MEITCHIB MFRLDATA MMADFLLC MMRARTT MSTHBS MSTHRF MTCHBUTI MTCHQLEN MUTHBS MUTHRF NACSUCPR NACTTBF NALIPDCH NALLPDCH NASPAVUN NASSARP NASUSDPE NATPRRE NATTSDPE NAVPDCH NAVSDCCH NAVTCH

Correlated RXLEV to Time Advance measurements (downlink) Correlated RXLEV to Time Advance measurements (uplink) Duration of Adjacent Signalling Point (ASP) unavailable condition Number of discarded LLC PDU per cell per cause per traffic class Duration of link in-service state Duration of the linkset unavailable conditions Duration of signaling link unavailability FACCH Supervision Total number of Handover failures, intra BSC I-Frame Measurement on Abis Interface on BTSE side I-Frame Measurement on Abis Interface on BSC side Interference measurements on idle TCHs Link adaptation measurements (uplink/downlink) per cell DL LLC PDU Queues Filling Level per Cell Number of locally generated automatic changeovers Maximum number of busy SDCCHs per cell Mean number of busy TCH per channel type BTS Power Measurements on Downlink Busy TCHs Mean number of busy SDCCHs Mean Number of Busy SDCCHs per Signalling Procedure Mean duration a TCH is queued (Fullrate/Halfrate) Mean Duration a TCH/SD with TCH_SD_Pool can be used as SDCCH Mean number of busy TCHs (Fullrate/Halfrate) Mean Number of Busy Channels Mean number of idle TCHs per interference band Mean frame relay data on the Gb interface per NSVC Min, Max and Mean Access Delay of a first LLC PDU per traffic class per cell Radio Access RTT for DL RLC PDU's per cell Mean signaling data throughput (uplink/downlink) per cell on the BSSGP Layer Gb interface Mean signaling data throughput (uplink/downlink) per cell on the RF interface Mean TCH busy time (Fullrate/Halfrate) Mean TCH queue length (Fullrate/Halfrate) Mean user data throughput (uplink/downlink) per cell per Traffic class on the BSSGP Layer Gb interface Mean user data throughput (uplink/downlink) per cell on the RF Interface Number of accesses with a successful result by procedure (PCH, AGCH and RACH) Total, Mean number of active TBF Min, max, mean number of activated PDCHs per cell Min, max, mean number of used (active TBF) PDCHs (uplink/downlink) per cell Number of transitions of the Adjacent Signalling Point (ASP) from available to unavailable Number of Successful Assignments Related to MS with ARP Number of successful SDCCH seizures in a period Number of attempted packet resource reassignment procedures per cell Number of attempted SDCCH seizures in a period Number of available PDCH per cell Number of available SDCCHs Number of available TCHs (Fullrate/Halfrate)
187
A50016-G5100-A042-1-7618
Information System
NAVTCHSD NCRLBRQU NDEFCCCH NDEFPCCC NDEFPDCH NDESDCCH NDFTCHSD NFLTCHARP NFRMDLARP
Number of available TCH/SD per Cell Normal call releases of calls with bad radio quality Number of All Defined CCCH Channels Number of Defined PCCCH Frames Min, max, mean number of defined (configured) PDCHs per cell Number of defined SDCCHs Number of defined TCH/SD Number of Lost Radio Links while using a TCH related to MS with ARP Frame Measurements for AMR only for MS with ARP capability on Downlink Busy TCHs. NFRMULARP Frame Measurements for AMR only for MS with ARP capability on Uplink Busy TCHs NHOINRHA Number of handover indications not resulting in a handover at-tempt 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) NPDTPCU Min, Max, Mean number of activated PDTs per PCU 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 cell NTCHLOEV Number of TCH load events on Um and Abis per cell NTCHSDCM 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 NUMPFCADMREJ Number of Real Time PFC admitted and rejected NTRAPDU Number of transmitted PDUs (uplink/downlink) per coding scheme per cell on the RF interface
188
A50016-G5100-A042-1-7618
Information System
PWRUPDW REJPDASS REMUTHRF RFDBCUN RFSUBUN RQIISHDO RXQUARP SERVUGDG SINHOBSC SININIRH SINTHINT SINTHITA SISHINTE SISHINTR SLFAILAL SOINTESH SOUINIRH SUCPDASA SUCRORIG SUCTCHARP SUCTCHSE SUCTETBF SUDTMREQ SUIISHDO SUIMASCA SUINBHDO SULACCEL SUOISHDO TACCBPRO TANRGPRS TASSATT TASSATVS TASSFAIL TASSSUCC TASSUCVS TBFRASSR TCMSGREC TCMSGSND TMSGREC TMSHHDL TNMSCNCL TNSUDHSC TNTCHCL TRANAVTI UISHIALC

Power and quality measurements on uplink/downlink busy TCHs Number of rejected PDCH assignments (uplink/downlink) per cause Retransmitted mean user data throughput (uplink/downlink) per coding scheme per cell on the RF interface Routing failure, DPC unavailable Routing failure, subsystem unavailable Number of Requested Incoming Intersystem Handover per BSC Quality Measurements Related to MS with ARP on Downlink Busy TCHs Service upgrade/downgrade measurements (uplink/downlink) per cell Successful internal Handovers per cause Successful incoming internal intercell Handovers per originating cell Successful internal Handovers, intercell, per cause Successful internal Handovers, intracell, per cause Successful Internal SDCCH Handovers Intercell Successful internal SDCCH Handovers Intracell Signaling link failure Successful MSC controlled SDCCH Handovers Successful outgoing intercell Handovers per cause, per neighbour cell relationship Number of successful PDCH assignments (uplink/downlink) per cell Successful network supported cell reselections per cell Successful TCH Seizures by ARP capable MS per channel type Successful TCH seizures (Fullrate/Halfrate) Number of successful terminated TBFs (uplink/downlink) per cell Number of successful requests to establish a DTM (UL/DL) Number of Successful Incoming Intersystem Handover per BSC Successful immediate assignment procedures, per cause Successful outgoing inter BSC Handovers per neighbour cell relationship Number of successful PDCH seizures (uplink/downlink) per cell Successful Outgoing Intersystem Handover per neighbourcell per cause Total number of accesses by procedures (PCH, AGCH) Number of attempted GPRS accesses per cell with no GPRS radio resources allocated Total number of assignment attempts per cell per channel type Total number of assignment attempts relevant to VBS/VGCS Broadcast/Group Channels, per cell Total number of assignment failures per cell, per cause, per channel type Total number of successful assignments per cell per channel type Total number of successful assignments relevant to VBS/VGCS Broadcast/Group Channels, per cell TBF resource assignment rate Total number of connectionless messages received Total number of connectionless messages sent Total number of messages received Total number of messages handled Total number of multislot (HSCSD) connections per cell Number of service upgrades/downgrades for HSCSD calls Total number of TCH connections, per cell (Fullrate/Halfrate) Transceiver available time Unsuccessful Internal SDCCH Handovers Intracell with Loss of Connection
189
A50016-G5100-A042-1-7618
Information System
UISHINTE UISHINTR UISHIRLC UMCSHLC UNCRORIG UNIHIALC UNIHIRLC UNIISHDO UNINHOIA UNINHOIE UNOISHDO UNSDTMREQ UNSPDCSE UNSTETBF UOINTESH WPSSUPV WUTHBS

Unsuccessful Internal SDCCH Handovers Intercell Unsuccessful internal SDCCH Handovers Intracell Unsuccessful Internal SDCCH Handovers Intercell with Loss of Connection Unsuccessful MSC-Controlled SDCCH Handovers with Loss of Connection Unsuccessful network controlled cell reselections per cell per cause Unsuccessful internal Handover, intracell, with loss of MS Unsuccessful internal Handovers, intercell, with loss of MS Number of Unsuccessful Incoming Intersystem Handover per BSC Unsuccessful internal Handovers, intracell Unsuccessful internal HOs, intercell, with reconnection to the old channel, cause, per target cell Unsuccessful Outgoing Intersystem Handover per neighbourcell per cause Number of unsuccessful requests to establish a DTM (UL/DL) Number of degraded PDCH seizures (uplink/downlink) per cell Number of unsuccessful terminated TBFs (uplink/downlink) per cell per cause Unsuccessful MSC controlled SDCCH Handovers Wireless Priority Services (WPS) Supervision Weighted User Data Throughput (Uplink/Downlink) per Traffic Class per Cell on the BSSGP Layer Gb Interface
190
A50016-G5100-A042-1-7618

Kpi

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Kpi

Hochgeladen von

Copyright:

Verfügbare Formate

Siemens

Information System Contents

PM: SBS Key Performance Indicators

PM: SBS Key Performance Indicators

Fig. 6 Overview Load related performance indicators............................................................ 51

Fig. 9 Overview Common Control Channels.......................................................................... 68

PM: SBS Key Performance Indicators

PM: SBS Key Performance Indicators

1.2 Reference Documents

1.3 Issue History

BR9.0 IUS1.0 BR9.0 AFI1.1

PM: SBS Key Performance Indicators

PM: SBS Key Performance Indicators

1.4 Definition of Terms

PM: SBS Key Performance Indicators

PM: SBS Key Performance Indicators

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

PM: SBS Key Performance Indicators

Top Level KPI

Packet Switched KPI based on GERAN PM Counters

PM: SBS Key Performance Indicators

Other KPI based on GERAN PM Counters

PM: SBS Key Performance Indicators

Immediate Assignment Analysis

Figure 1 Message flow: Immediate Assignment Procedure

SBS Counter [1] CHANNEL REQUIRED

PM: SBS Key Performance Indicators

The following figure shows you the traffic flow.

[7] Number of successful Immediate Assignments

Fig. 1 Traffic flow: Immediate Assignment Procedure

PM: SBS Key Performance Indicators

3.1 Number of Immediate Assignment Attempts

3.2 Number of Immediate Assignment Losses

ImmAssLoss = ImmAssAtt - ImmAssBSCp roc

PM: SBS Key Performance Indicators

3.3 Number of Immediate Assignments by BSC procedure

ImmAssBSCp roc = SUIMASCA[1 ..6]

PM: SBS Key Performance Indicators

3.4 Number of AGCH Losses

3.5 Number of Immediate Assignment Commands sent to MS via AGCH

PM: SBS Key Performance Indicators

3.6 Number of Immediate Assignments without MS Seizure

3.7 Number of successful Immediate Assignments

ImmA ssSucc = NSUCCHPC[1 .. 6, 9 ..14, 17 .. 22]

PM: SBS Key Performance Indicators

3.8 Immediate Assignment Loss Rate

3.9 AGCH Loss Rate CS

PM: SBS Key Performance Indicators

3.10 Immediate Assignment without MS Seizure Rate

3.11 Immediate Assignment Success Rate

PM: SBS Key Performance Indicators

SSS Procedures Analysis

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

NSUCCHPC[1..4,9..12,17..20] NSUCCHPC[8] TASSATT [2..3]

PM: SBS Key Performance Indicators

The following figure shows you the traffic flow.

[3] SSS Procedure failures [4] Assignment Attempts

PM: SBS Key Performance Indicators

4.1 Number of successful Immediate Assignments related to Call Setups

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

PM: SBS Key Performance Indicators

4.2 Number of Dropped SDCCH Connections related to Call Setups

4.3 Number of SSS Procedure Failures related to Call Setups