Professional Documents
Culture Documents
Kpi BR10
Kpi BR10
Date Release
: 15.04.2008 : BR10.0
Contents.................................................................................................................................. 2
1 INTRODUCTION ............................................................................................................................................. 7 1.1 Purpose.............................................................................................................................................. 7 1.2 Reference Documents ........................................................................................................................ 7 1.3 Issue History...................................................................................................................................... 7 1.4 Definition of Terms............................................................................................................................ 8 TOP LEVEL KPI.......................................................................................................................................... 11 2.1 Accessibility..................................................................................................................................... 12 2.2 Retainability .................................................................................................................................... 12 2.3 Mobility ........................................................................................................................................... 13 2.4 Network usage ................................................................................................................................. 13 2.5 Quality / Integrity ............................................................................................................................ 14 IMMEDIATE ASSIGNMENT ANALYSIS.......................................................................................................... 15 3.1 Number of Immediate Assignment Attempts .................................................................................... 17 3.2 Number of Immediate Assignment Losses ....................................................................................... 17 3.3 Number of Immediate Assignments by BSC procedure ................................................................... 18 3.4 Number of AGCH Losses................................................................................................................. 19 3.5 Number of Immediate Assignment Commands sent to MS via AGCH............................................. 19 3.6 Number of Immediate Assignments without MS Seizure.................................................................. 20 3.7 Number of successful Immediate Assignments ................................................................................ 20 3.8 Immediate Assignment Loss Rate .................................................................................................... 21 3.9 AGCH Loss Rate During Call Setup Caused by AGCH Overload in BTS ...................................... 21 3.10 Immediate Assignment without MS Seizure Rate............................................................................. 22 3.11 Immediate Assignment Success Rate ............................................................................................... 22 3.12 SDCCH Congestion Rate during Call Setup ................................................................................... 22 3.13 Immediate Assignment Failure Rate................................................................................................ 23 SSS PROCEDURES ANALYSIS ..................................................................................................................... 24 4.1 Number of successful Immediate Assignments related to Call Setups ............................................. 26 4.2 Number of Dropped SDCCH Connections related to Call Setups................................................... 27 4.3 Number of SSS Procedure Failures related to Call Setups ............................................................. 27 4.4 SDCCH Drop Rate related to Call Setups....................................................................................... 28 4.5 SSS Procedures Failure Rate related to Call Setups ....................................................................... 28 4.6 SSS Procedures Success Rate related to Call Setups....................................................................... 29 ASSIGNMENT ANALYSIS ............................................................................................................................. 30 5.1 Number of Assignment Attempts ...................................................................................................... 32 5.2 Number of Assignment Failures ...................................................................................................... 33 5.3 Number of successful Assignments .................................................................................................. 34 5.4 Assignment Failure Rate ................................................................................................................. 35 5.5 Assignment Success Rate ................................................................................................................. 36 5.6 Assignment success rate when radio resources available ............................................................... 36 5.7 Mean Number of Repeated Assignment Requests............................................................................ 36 5.8 Repeated Assignment Request Rate ................................................................................................. 37 CALL SETUP ANALYSIS .............................................................................................................................. 38 6.1 Number of Call Setup Attempts........................................................................................................ 39 6.2 Number of Successful Call Setups ................................................................................................... 39 6.3 Call Setup Success Rate................................................................................................................... 40 6.4 Number of Call Setup Failures ........................................................................................................ 40 6.5 Call Setup Failure Rate ................................................................................................................... 42 6.6 Call Setup Failure Rate (Network View) ......................................................................................... 43 TCH DROP RELATED PERFORMANCE INDICATORS ..................................................................................... 44 7.1 Number of Dropped TCH Connections ........................................................................................... 44 7.2 TCH Drop Distribution ................................................................................................................... 45 7.3 TCH Drop Rate................................................................................................................................ 48 7.4 Call Drop Rate ................................................................................................................................ 49 7.5 Mean Time between TCH Drop....................................................................................................... 51 7.6 TCH Drops per Erlanghour............................................................................................................. 51 7.7 Rate of normal call releases of calls with bad radio quality ........................................................... 51
Information System
8
7.8 Rate of TCH Drops and normal call releases of calls with bad radio quality................................. 52 SDCCH DROP RELATED PERFORMANCE INDICATORS................................................................................ 54 8.1 Number of dropped SDCCH Connections ....................................................................................... 54 8.2 SDCCH Drop Rate .......................................................................................................................... 54 8.3 Mean Time between SDCCH Drop.................................................................................................. 55 8.4 SDCCH Drops per Erlanghour ....................................................................................................... 55 9 TCH LOAD RELATED PERFORMANCE INDICATORS..................................................................................... 56 9.1 TCH Load for Circuit Switched Traffic ........................................................................................... 56 9.1.1 TCH Traffic Distribution Rate .................................................................................................... 56 9.1.2 TCH Traffic Offered ................................................................................................................... 57 9.1.3 TCH Traffic Carried.................................................................................................................... 57 9.1.4 TCH Traffic Lost......................................................................................................................... 59 9.1.5 TCH Block Rate .......................................................................................................................... 60 9.1.6 TCH Loss Rate............................................................................................................................ 60 9.1.7 TCH Mean Holding Time ........................................................................................................... 62 9.1.8 TCH Traffic Utilization............................................................................................................... 63 9.1.9 DMA Loss Rate........................................................................................................................... 64 9.2 Combined time slot utilization for CS and PO Traffic..................................................................... 66 9.2.1 Combined time slot occupation rate for CS and PO Traffic........................................................ 66 10 DCCH RELATED PERFORMANCE INDICATORS ...................................................................................... 68 10.1 SDCCH Load related Performance Indicators................................................................................ 68 10.1.1 SDCCH Traffic Offered.......................................................................................................... 69 10.1.2 SDCCH Traffic Carried .......................................................................................................... 69 10.1.3 SDCCH Traffic Lost............................................................................................................... 69 10.1.4 SDCCH Blocking Rate ........................................................................................................... 70 10.1.5 SDCCH Loss Rate .................................................................................................................. 70 10.1.6 SDCCH Mean Holding Time.................................................................................................. 70 10.1.7 SDCCH Traffic Utilisation ..................................................................................................... 71 10.2 SACCH related Performance Indicators ......................................................................................... 71 10.2.1 Repeated SACCH Utilization ................................................................................................. 71 10.3 FACCH related Performance Indicators......................................................................................... 73 10.3.1 FACCH Repetition Rate ......................................................................................................... 73 11 CCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................ 74 11.1 PCH load of downlink CCCH channels .......................................................................................... 76 11.2 AGCH load of downlink CCCH channels........................................................................................ 76 11.3 CCCH load downlink....................................................................................................................... 77 11.4 CCCH load uplink ........................................................................................................................... 77 11.5 PCH Loss Rate ................................................................................................................................ 78 11.6 AGCH Loss Rate.............................................................................................................................. 78 11.7 Invalid RACH Rate .......................................................................................................................... 79 12 PCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................. 80 12.1 PPCH load of downlink PCCCH channels...................................................................................... 82 12.2 PAGCH load of downlink PCCCH channels................................................................................... 82 12.3 PCCCH load downlink .................................................................................................................... 83 12.4 PCCCH load uplink......................................................................................................................... 83 12.5 PPCH Loss Rate .............................................................................................................................. 84 12.6 PAGCH Loss Rate ........................................................................................................................... 84 12.7 Invalid PRACH Rate........................................................................................................................ 85 13 SERVICE RELATED PERFORMANCE INDICATORS ................................................................................... 86 13.1 Total number of Service Requests.................................................................................................... 86 13.2 Service Request Distribution Rate ................................................................................................... 86 13.3 Rate of Service Requests served in the highest layer ....................................................................... 87 14 FEATURE RELATED PERFORMANCE INDICATORS .................................................................................. 88 14.1 Abis Pool Traffic Utilization............................................................................................................ 88 14.2 Abis Pool Subchannel Distribution ................................................................................................. 89 14.3 I-FRAME Discard Rate on Abis-Interface BSC side ....................................................................... 90 14.4 I-FRAME Discard Rate on Abis-Interface BTSE side ..................................................................... 90 14.5 ARP-type Receiver Penetration ....................................................................................................... 91 15 HANDOVER RELATED PERFORMANCE INDICATORS ............................................................................... 92 15.1 General Handover performance...................................................................................................... 92 15.1.1 Handover Success Rate........................................................................................................... 92
Information System
15.1.2 Handover Success Rate 2G to 2G ........................................................................................... 92 15.1.3 Handover Success Rate 2G to 3G ........................................................................................... 93 15.2 Intra Cell Handovers ....................................................................................................................... 93 15.2.1 Handover Success Rate........................................................................................................... 93 15.2.2 Handover Failure Rate ............................................................................................................ 94 15.2.3 Handover Drop Rate ............................................................................................................... 95 15.2.4 Handover Distribution ............................................................................................................ 97 15.2.5 SDCCH Handover Success Rate............................................................................................. 98 15.2.6 SDCCH Handover Failure Rate.............................................................................................. 98 15.2.7 SDCCH Handover Drop Rate ................................................................................................. 99 15.3 Inter Cell Intra BSC Handovers .................................................................................................... 100 15.3.1 Handover Success Rate......................................................................................................... 100 15.3.2 Handover Failure Rate .......................................................................................................... 102 15.3.3 Handover Drop Rate ............................................................................................................. 103 15.3.4 Handover Distribution .......................................................................................................... 104 15.3.5 Incoming Handover Success Rate......................................................................................... 105 15.3.6 SDCCH Handover Success Rate........................................................................................... 106 15.3.7 SDCCH Handover Failure Rate............................................................................................ 107 15.3.8 SDCCH Handover Drop Rate ............................................................................................... 107 15.4 Inter Cell Inter BSC Handovers .................................................................................................... 108 15.4.1 Handover Success Rate......................................................................................................... 108 15.4.2 Handover Failure Rate .......................................................................................................... 109 15.4.3 Handover Drop Rate ............................................................................................................. 110 15.4.4 Handover Distribution .......................................................................................................... 111 15.4.5 SDCCH Handover Success Rate........................................................................................... 112 15.4.6 SDCCH Handover Failure Rate............................................................................................ 112 15.4.7 SDCCH Handover Drop Rate ............................................................................................... 113 15.5 Inter System Handover between GSM and UMTS......................................................................... 114 15.5.1 Outgoing Inter System Handover Success Rate.................................................................... 114 15.5.2 Outgoing Inter System Handover Failure Rate ..................................................................... 115 15.5.3 Outgoing Inter System Handover Drop Rate ........................................................................ 116 15.5.4 Outgoing Inter System Handover Distribution ..................................................................... 117 15.5.5 Incoming Inter System Handover Success Rate ................................................................... 118 15.6 Other Handover Performance Indicators...................................................................................... 119 15.6.1 Handovers per Erlanghour .................................................................................................... 119 15.6.2 Handovers per Call Rate ....................................................................................................... 119 15.6.3 Intercell Handover Attempts per Speech Call per Erlanghour.............................................. 120 15.6.4 Successful Directed Retries .................................................................................................. 121 15.6.5 Imperative Outgoing Handover Rate .................................................................................... 121 15.6.6 Incoming Handover Success Rate......................................................................................... 123 15.6.7 Handover Indication Rejection Rate ..................................................................................... 125 15.6.8 Total Handover Rates .......................................................................................................... 126 16 POWER AND QUALITY MEASUREMENTS ............................................................................................. 127 16.1 Interference Band Rate on idle TCH ............................................................................................. 127 16.2 Quality Link for N% FER .............................................................................................................. 128 16.3 Mean FER UpLink......................................................................................................................... 128 16.4 Power and Quality limits for N% Percentile on busy TCH ........................................................... 129 16.5 Distribution of power control levels on busy TCH ........................................................................ 130 16.6 Mean Level and Quality on busy TCH........................................................................................... 131 16.7 TA Distribution.............................................................................................................................. 132 16.8 RXQUAL Distribution ................................................................................................................... 132 16.9 RXLEV Distribution....................................................................................................................... 133 16.10 FER Distribution ........................................................................................................................... 133 16.11 Mean FER UpLink per RXQUAL .................................................................................................. 134 16.12 Mean RXLEV per RXQUAL Band ................................................................................................. 135 16.13 Mean RXLEV per TA Band............................................................................................................ 136 16.14 High RXLEV with Low RXQUAL Rate .......................................................................................... 137 16.15 TCH Traffic Type Distribution ...................................................................................................... 138 16.16 SDCCH Traffic Type Distribution ................................................................................................. 139 16.17 Adaptive Multirate Distribution .................................................................................................... 140 16.18 Adaptive Multirate True Frame Erasure Rate............................................................................... 141
Information System
16.19 Effective Frequency Load .............................................................................................................. 142 16.20 AMR Frame Erasure Rate for ARP-type Receiver ........................................................................ 143 17 AVAILABILITY RELATED PERFORMANCE INDICATORS ........................................................................ 145 17.1 Transceiver Availability ................................................................................................................ 145 17.2 TCH Distribution Rate................................................................................................................... 145 17.3 TCH Availability............................................................................................................................ 146 17.4 SDCCH Availability ...................................................................................................................... 147 18 GPRS RELATED PERFORMANCE INDICATORS ..................................................................................... 148 18.1 User oriented KPIs ........................................................................................................................ 148 18.1.1 Number of TBF establishment attempts ............................................................................... 148 18.1.2 Number of TBF establishment failures ................................................................................. 148 18.1.3 Number of successful TBF establishments ........................................................................... 149 18.1.4 TBF establishment success rate ............................................................................................ 149 18.1.5 TBF establishment failure rate (TBF loss rate)..................................................................... 150 18.1.6 Rate for successful TBF establishment with reduced PDCH assignment ............................. 150 18.1.7 Total number of normally released TBFs ............................................................................. 151 18.1.8 Total number of dropped TBFs............................................................................................. 151 18.1.9 TBF drop distribution on causes ........................................................................................... 152 18.1.10 TBF Drop rate....................................................................................................................... 153 18.1.11 TBF Drop frequency............................................................................................................. 153 18.1.12 Mean time between TBF drop .............................................................................................. 154 18.1.13 User data throughput per TBF on the air interface................................................................ 155 18.1.14 Packet resource reassignment attempts................................................................................. 157 18.1.15 Packet resource reassignment failures .................................................................................. 157 18.1.16 Packet resource reassignment success rate ........................................................................... 158 18.1.17 Packet resource reassignment failure rate ............................................................................. 158 18.1.18 TBF downgrade / upgrade frequency.................................................................................... 159 18.1.19 Mean TBF duration per traffic class ..................................................................................... 160 18.1.20 Link adaptation frequency .................................................................................................... 161 18.1.21 Total number of discarded LLC frames ................................................................................ 162 18.1.22 LLC Frame discard rate ........................................................................................................ 162 18.1.23 DTM establishment success rate........................................................................................... 163 18.1.24 DTM establishment failure rate ............................................................................................ 164 18.1.25 Weighted LLC User Data Throughput.................................................................................. 164 18.2 Network planning (dimensioning) ................................................................................................. 165 18.2.1 Total Throughput on air interface per cell ............................................................................ 165 18.2.2 User Throughput on radio interface per cell ......................................................................... 166 18.2.3 Uplink / Downlink distribution of user throughput on radio interface per cell..................... 167 18.2.4 Total packet volume transmitted on radio interface per cell ................................................. 167 18.2.5 Total packet Throughput on Gb interface per cell ................................................................ 168 18.2.6 User data Throughput on Gb interface per cell ..................................................................... 168 18.2.7 Mean number of busy PDCH per cell ................................................................................... 169 18.2.8 PDCH utilization rate............................................................................................................ 169 18.2.9 Mean Throughput per busy PDCH ....................................................................................... 170 18.2.10 Mean number of simultaneously active TBFs per cell.......................................................... 173 18.2.11 Mean number of TBFs multiplexed on same PDCH ............................................................ 173 18.2.12 Mean number of allocated PDCHs per TBF ......................................................................... 173 18.2.13 PDCH Bit Rate per Coding Scheme ..................................................................................... 175 18.2.14 Mean PDCH Bit Rate ........................................................................................................... 176 18.2.15 Percent Timeslot Resources Achieved.................................................................................. 177 18.2.16 Frame Relay Link Utilization ............................................................................................... 178 18.3 Network optimization..................................................................................................................... 179 18.3.1 Retransmission Rate on radio interface per cell per coding scheme ..................................... 179 18.3.2 Retransmitted user throughput on radio interface per cell per coding scheme ..................... 180 18.3.3 Distribution of user throughput on radio interface on Coding Schemes per cell .................. 181 18.3.4 Timely distribution of the coding scheme utilization on the radio interface......................... 182 18.4 Cell Reselection ............................................................................................................................. 183 18.4.1 Number of network controlled Intra BSC cell reselection attempts per cell......................... 183 18.4.2 Number of successful network controlled Intra BSC cell reselections per cell .................... 184 18.4.3 Number of network controlled Intra BSC cell reselection failures per cell per cause .......... 184 18.4.4 Network controlled Intra BSC cell reselection success rate.................................................. 185
Information System
18.4.5 Network controlled Intra BSC cell reselection failure rate ................................................... 185 18.4.6 Network controlled cell reselection failure rate .................................................................... 186 18.4.7 PS Handover Success Rate 2G to 2G.................................................................................... 187 18.4.8 PS Handover Success Rate 2G to 3G.................................................................................... 187 18.4.9 PS Handover Success Rate 3G to 2G.................................................................................... 187 19 MISCELLANEOUS PERFORMANCE INDICATORS ................................................................................... 188 19.1 BSC1 Processor load..................................................................................................................... 188 19.2 Basic eBSC Processor load ........................................................................................................... 188 19.3 HighEnd eBSC Processor load...................................................................................................... 190 19.4 BTSE Processorload...................................................................................................................... 192 19.5 PCU Occupancy Rate.................................................................................................................... 192 19.6 Paging Response / Location Update Ratio per Cell ...................................................................... 193 19.7 BSC <-> MSC/SMLC CCS7 Load................................................................................................. 194 20 APPENDIX ........................................................................................................................................... 195 20.1 List of BSS Performance Measurements........................................................................................ 195
Information System
Introduction
1.1 Purpose
The purpose of this document is the definitions of 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.
Information System
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 short identification of the used performance measurement counters or the short name of the used key performance indicators. The related long names of performance measurement counters you can find in the appendix under List of Performance Measurements. The 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.
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;
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
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.
10
Information System
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 CS and PS KPIs can be divided into the following categories: Category
Accessibility
Measurement targets
The ability of a service to be obtained, within specified tolerances and other given conditions, when requested by the user. Establishing a successful connection Establishing Success Rate
Retainability
The ability of a service, once obtained, to continue to be provided under given conditions for a requested duration. Maintaining an ongoing (dropped) connection. Connection Drop Rate
Handover Success Rate Information about the traffic utilization on all interfaces. Throughput measurements.
Quality / Integrity
The degree to which a service is provided without excessive impairments, once obtained. Connection Quality. Service experience during a connection
The following KPI are based on GERAN PM Counters and 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. KPIs supported by the Radio Commander MVI tool or by the Real Time Performance Monitoring (RTPM) feature are also listed.
11
Information System
2.1 Accessibility
Category Accessibility Key Performance Indicator Immediate Assignment Success Rate Immediate Assignment Failure Rate TCH Assignment Success Rate Chapter 3.11 3.13 5.5 X MVI QoS / RTPM
Call Setup Success Rate BSS Call Setup Failure Rate Call Setup Failure Rate (Network View)
TBF establishment failure rate (TBF loss 18.1.5 (e) rate) Packet resource reassignment failure rate 18.1.17(a)
2.2 Retainability
Category Retainability Key Performance Indicator Call Drop Rate TCH Drop Rate TCH Drops per Erlanghour SDCCH Drop Rate Total Handover Drop Rate TBF Drop rate TBF Drop frequency Total number of dropped TBFs Chapter 7.4 7.3 7.6 8.2 15.6.8(g) 18.1.10 18.1.11 (a), (b) 18.1.8 (a), (b) X X X X X X X X MVI QoS / RTPM
12
Information System
2.3 Mobility
Category Mobility Key Performance Indicator Handover Success Rate Handover Success Rate 2G to 2G Handover Success Rate 2G to 3G Chapter 15.1.1 15.1.2 15.1.3 MVI QoS / RTPM
Intercell Handover Attempts per Speech 15.6.3 Call per Erlanghour Total Handover Failure Rate 15.6.8(f) X X
BSC
cell 18.4.4 X
Combined time slot occupation rate for CS 9.2.1 and PO Traffic Abis Pool Traffic Utilization PCU Occupancy Rate Frame Relay Link Utilization BSC1 Processor load / TDPC BSC1 Processor load / PCU 14.1(l) 19.5 18.2.16 19.1 (b) 19.1 (c)
X2 X3
1 2
13
Information System
14
Information System
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 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
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,3]
NACSUCPR [2,3]
NSUCCHPC [1..22]
15
Information System
[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
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 During Call Setup Caused by AGCH Overload in BTS: [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
16
Information System
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.
Formula:
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.
17
Information System
Formula:
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.
18
Information System
Formula:
Used param.: AGCHLossRateCSAGCHLossesBTS (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.
Used param.: ImmAssBSCproc (3.3(a)), AGCHLossRateCSAGCHLossesBTS (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.
19
Information System
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.
Formula:
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.
20
Information System
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 During Call Setup Caused by AGCH Overload in BTS
Long name: Short name: Description: a) AGCH Loss Rate During Call Setup Caused by AGCH Overload in BTS (a) AGCHLossRateCSAGCHLossesBTS 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 failed, 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 be considered. (a) AGCHLossRateCSAGCHLossesBTS =
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.
21
Information System
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.
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.
22
Information System
Formula:
Used param.: TACCBPRO[2,3] Elem. Object: Cell Unit: Remarks: None The formula is valid only if the DirectAssignment procedure is not enabled in the observed cell.
Used param.: ImmAssAtt (3.1(a)), ImmAssSucc (3.7(a)) Elem. Object: Cell Unit: Remarks: None Phantom RACHs are included in this formula.
23
Information System
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
Counter [1] ESTABLISH INDICATION (related to Call Setups) [2] ASSIGNMENT ATTEMPTS
Sub-counters are listed in Brackets The different number of failures and failure rates can be evaluated with 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 performance measurement counter it is possible to calculate the SSS Procedure Success and Failure Rate related to Call Setups.
24
Information System
[2]SDCCH Drops
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]
25
Information System
Formula:
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).
26
Information System
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
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.
27
Information System
Formula:
SDCCHDropR ateCS =
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
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.
28
Information System
Formula:
AssAtt or ImmAssSuccCS
29
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 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
BSS Counter: [1] ASSIGMENT ATTEMPS [2] INCOMING REDIRECTED [3] OUTGOING REDIRECTED CALLS TASSATT [2..3]
TASSSUCC [4..5]
SINTHINT [7] + SUINBHDO [7]i; i = 0 ...31 (i = number of GSM ADJ-ids) + SUOISHDO[7] j ; j = 0 ...63 (j= number of UMTS ADJ-ids)
[4] ASSIGMENT COMPLETE (normal Assignm.) [5] ASSIGMENT FAILURE [6] Queuing Failure
30
Information System
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]
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)
31
Information System
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.
32
Information System
Short name:
Description: Formula:
These indicators will give you the number of failed Assignments of a TCH. (a) AssLoss
= TASSFAIL[8,13]
(b) AssFailbyM ess = TASSFAIL[6 ,7,10,11,1 2,15] (c) AssFailOther (d) QueFail (e) AssFail
Used param.: TASSFAIL [6,7,8,10,11,12,13,15], AssAtt (5.1(a)) , AssSucc (5.3(a)), NMSGDISQ[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.
33
Information System
Formula: (a)
with i for the number of GSM neighbourcell relation (n=0..31) with j for the number of UMTS neighbourcell relation (m=0..63)
Used param.: TASSSUCC[2,3], SINTHINT[7], SUINBHDO[7], SUOISHDO[7] Elem. Object: Cell Unit: Remarks: None
Assignments of SDCCH are not considered. Intersystem Directed Retry to UMTS are considered
34
Information System
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) AssLossRate =
Formula:
AssLoss AssAtt
AssFailbyMess AssAtt
AssFailOther AssAtt
QueFail AssAtt
(e) AssFailRate =
AssFail AssAtt
Used param.: AssAtt(5.1(a)), AssLoss (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
35
Information System
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
(a) SuccAssProbNoTCHBlocking = 1
Used param.: AssAtt(5.1(a)), AssLoss (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
RepAssReq
36
Information System
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.
Used param.: AssAtt(5.1(a)), AssSucc (5.3(a)), AssFail (5.2(d)) Elem. Object: Cell Unit: Remarks: None None
37
Information System
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
38
Information System
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.
Used param.: AssSucc (4.3a) Elem. Object: Cell Unit: Remarks: None Assignment of SDCCH are not considered
39
Information System
Formula:
40
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 * AGCHLossRateCSAGCHLossesBTS = CSAtt * ImmAssNoSeizRate = CSAtt * ImmAssSuccRate * SDCCHDropRateCS = CSAtt * ImmAssSuccRate * SSSProcFailRateCS = AssLoss = AssFailbyMess = AssFailOther = QueFail
Formula:
Used param.: CSAtt (6.1(a)), CSSucc (6.2(a)), ImmAssLossRate(3.8(a)), AGCHLossRateCSAGCHLossesBTS (3.9(a)), ImmAssNoSeizRate(3.10(a)), ImmAssSuccRate (3.11(a)), SDCCHDropRateCS(4.4(a)), SSSProcFailRateCS(4.5(a)), AssLoss(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
41
Information System
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) CSFailRateBSS CSFailRateImmAssLoss CSFailRateAGCHLoss CSFailRateImmAssNoSeiz CSFailRateSDCCHDrops CSFailRateSSSProcFail CSFailRateTCHLoss CSFailRateAssFailbyMess CSFailRateAssFailOther CSFailRateQueFail = 1 CSSuccRateBSS = ImmAssLossRate = AGCHLossRateCSAGCHLossesBTS = ImmAssNoSeizRate = SDCCHDropRateCS = SSSProcFailRateCS = AssLossRate = AssFailbyMessRate = AssFailOtherRate = QueFailRate
Formula:
Used param.: CSSuccRateBSS (6.3(b)), ImmAssLossRate(3.8(a)), AGCHLossRateCSAGCHLossesBTS (3.9(a)), ImmAssNoSeizRate(3.10(a)), SDCCHDropRateCS(4.4(a)), SSSProcFailRateCS(4.5(a)), AssLossRate(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
42
Information System
Used param.: ImmAssFailRate (3.13), SDCCHDropRate (8.2), AssSuccRate(5.5) Elem. Object: Cell Unit: Remarks: None The Call Setup Failure Rate (Network View) considers the so called "Phantom RACHes" whereas the KPI CSFailRate in chapter 6.5 excludes the "Phantom RACHes".
43
Information System
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
44
Information System
Short name:
45
Information System
Formula: (a) TCHDropDis t.T200 =
TCHDropDist.SeqErr =
(d)
TCHDropDis t.TMSRFPCI =
(e)
TCHDropDist.Distance = TCHDropDist.HOAccess =
(f)
(g)
TCHDropDist.RadLinkFail =
(h) TCHDropDist.RemTranscFail =
46
Information System
Used param.: NRFLTCH[1..90], 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 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.
47
Information System
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.
48
Information System
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(7.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
49
Information System
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.
50
Information System
Used param.: TCHDrop(7.1(a)), TCHTrafCarrDR(9.1.3(c)), Granularity in minutes Elem. Object: Cell Unit: Remarks: Seconds SDCCH Handovers are not considered and can therefore lead to systematic errors.
Used param.: TCHDrop(7.1(a)), TCHTrafCarrDR(9.1.3(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.
51
Information System
Short name: (a) (b) (c) (d) (e) (f) (g)
Description: Formula:
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]
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
52
Information System
Remarks:
53
Information System
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.
(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.
54
Information System
MTBSDCCHDrop =
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.
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.
55
Information System
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.
(b) HRT =
MEBUSTCH[1,2] are defined for standard cell, MEBUSTCH[3..6] are defined for the concentric cell and MEBUSTCH[7..10] are defined for the extended cell. Used param.: MEBUSTCH[1..10] Elem. Object: Cell
56
Information System
Unit: Remarks: None
This KPI can be used by network planning to calculate the number of needed TRX.
Short name:
Description:
Use case:
Formula:
MEBUSTCH [1, 3,5,7,9] 1 - TCHLossRateFR MEBUSTCH [2, 4,6,8,10] (b) TCHTrafOffHR = 1 - TCHLossRateHR (c) TCHTrafOffDR = TCHTrafOffFR + TCHTrafOffHR
(a) TCHTrafOffFR = MEBUSTCH[1,2] are defined for standard cell, MEBUSTCH[3..6] are defined for the concentric cell and MEBUSTCH[7..10] are defined for the extended cell.
Used param.: MEBUSTCH[1..10], TCHLossRateFR(9.1.6(a)),TCHLossRateHR(9.1.6(b)) Elem. Object: Cell Unit: Remarks: Erlang None
57
Information System
Short name: (a) TCHTrafCarrFR (b) TCHTrafCarrHR (c) TCHTrafCarrDR
Description: Formula:
This indicator will give you the amount of carried traffic in Erlang on TCH. (a) TCHTrafCarrFR = MEBUSTCH [1, 3,5,7,9] (b) TCHTrafCarrHR = MEBUSTCH [2, 4,6,8,10] (c) TCHTrafCar rDR = TCHTrafCar rFR + TCHTrafCar rHR MEBUSTCH[1,2] are defined for standard cell, MEBUSTCH[3..6] are defined for the concentric cell and MEBUSTCH[7..10] are defined for the extended cell
Used param.: MEBUSTCH[1..10] Elem. Object: Cell Unit: Remarks: Erlang None
58
Information System
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):
Formula:
Amount of circuit switched traffic (measured in Erlang), which was lost due to discard from the TCH waiting queue.
(a) TCHTrafLostFR = TCHTrafOffFR - TCHTrafCarrFR (b) TCHTrafLostHR = TCHTrafOffHR - TCHTrafCarrHR (c) TCHTrafLos tDR = TCHTrafOff DR - TCHTrafCar rDR
Used param.: TCHTrafOffFR(9.1.2(a)), TCHTrafOffHR(9.1.2(b)), TCHTrafOffDR(9.1.2(c)), TCHTrafCarrFR(9.1.3(a)), TCHTrafCarrHR(9.1.3(b)), TCHTrafCarrDR(9.1.3(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
59
Information System
Short name:
Description: Formula:
(b) TCHBlockRateHR =
(c) TCHBlockRateDR = TCHBlockRateFR * FRT + TCHBlockRateHR * 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
Short name:
60
Information System
Description:
Formula:
ATCHSMBS [1] is only used by Standard cells. ATCHSMBS [5,7] is only used by Concentric cells. ATCHSMBS [9,11] is only used by Extended cells.
(b) TCHLossRateHR =
ATCHSMBS [2] is only used by Standard cells. ATCHSMBS [6,8] is only used by Concentric cells. ATCHSMBS [10,12] is only used by Extended cells.
(c) TCHLossRateDR =
ATCHSMBS [all] ATTCHSEI [1,2] NMSGDISQ [1, 3] ATTCHSEI [1] NMSGDISQ [2,4] ATTCHSEI [2] NMSGDISQ [1..4] ATTCHSEI [1..2]
Used param.: ATCHSMBS[all], ATTCHSEI[1..2], NMSGDISQ[1..4] Elem. Object: Cell Unit: Remarks: 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.
61
Information System
9.1.7
Long name:
Short name:
Description: Formula:
MEBUSTCH[1,3,5,7,9] * Granularity * 60 TNTCHCL [1, 3,5,7,9] MEBUSTCH[2,4,6,8,10] * Granularity * 60 TNTCHCL [2, 4,6,8,10] MEBUSTCH[1..10] * Granularity * 60 TNTCHCL [1..10]
MEBUSTCH[1,2] and TNTCHCL[1,2] are defined for standard cell, MEBUSTCH[3..6] and TNTCHCL[3..6] are defined for the concentric cell, MEBUSTCH[7..10] and TNTCHCL[7..10] are defined for the extended cell Used param.: MEBUSTCH[1..10], TNTCHCL[all], 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.
62
Information System
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
TCHTrafUtilHR =
TCHTrafUti lDR =
TCHTrafUti lFRErl=
Erlang B formula:
MEBUSTCH[1 ,3,5,7,9] A
A = f(N, B) = f(NRDEFTCH[2,8,14,20,26], B)
Erlang C formula:
TCHTrafUtilHRErl =
Erlang B formula: Erlang C formula
MEBUSTCH[2,4,6,8,10] A
A = f(N, B) = f(NRDEFTCH[5,11,17,23,29], B)
TCHTrafUti lDRErl =
63
Information System
Erlang B formula:
A = f(N, B) = f(NRDEFTCH[2,5,8,11,14,17,20,23,26,29], B)
Erlang C formula:
A = f(N, B, Ql, Qd) = = f(NRDEFTCH [2,5,8,11, 14,17,20,2 3,26,29], B, MTCHQLEN[1 ,2], MDURTCRQ[1 ,2])
with
A = Offered Load in Erlang B = Blocking Probability (Planning Parameter) MEBUSTCH[1,2] andNRDEFTCH[2,5] are defined for standard cell, MEBUSTCH[3..6] and NRDEFTCH[8,11,14,17] are defined for the concentric cell, MEBUSTCH[7..10] and NRDEFTCH[20,23,26,29] are defined for the extended cell Used param.: MEBUSTCH[1..10], NRDEFTCH [2,5,8,11,14,17,20,23,26,29], 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.
64
Information System
Used param.: Elem. Object: Unit: Remarks: Cell %
This KPI can be used only in case Dynamic MAIO Allocation and Admission Control are activated.
65
Information System
Formula:
n depends on the channel configuration. Default n = 8; n = 4 shall be used in combination SDCCH with BCCH; n = 3 or n = 7 in combination additional with CBCH channel. NRDEFTCH[3,6], MEBUSTCH [1,2] is only used by Standard cell and dual band standard cells. NRDEFTCH[9,12,15,18], MEBUSTCH [3,4,5,6] is only used by Concentric cells. NRDEFTCH[21,24,27,30], MEBUSTCH [7,8,9,10] is only used by Extended cells.
number of defined PDCH, mean number of occupied PDCH UL and DL (active TBF)
NRDEFTCH[3,6,9,12,15,18,21,24,27,30]: mean number of defined TCH [3,9,15,21,27] full rate, [6,12,18,24,30] 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 [all]: 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. Mean Number of busy TCHs [1,3,5,7,9] full rate, [2,4,6,8,10] half rate (1/2 time slot) Mean Number of busy SDCCHs (1/8 time slots)
66
Information System
NDEFPDCH: Number of defined PDCH NDEFPDCH include also the packet channels used as PBCCH and PCCCH; traffic is counted in NALLPDCH too. If HRSPEECH (see CML: BSC document) is disabled, then the NDFTCHSD counts the resources as available for Full Rate (eg 3 TCHSD --> counter value=3). On the other hand if HRSPEECH is enabled, then the NDFTCHSD counts the resources as available for Half Rate (eg 3 TCHSD --> counter value=6) which can lead to a small systematic error.
67
Information System
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
Number of channels N
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.
68
Information System
Used param.: MBUSYSDC[1], SDCCHLossRate (10.1.5(a)) Elem. Object: Cell Unit: Remarks: Erlang None
Used param.: MBUSYSDC[1] Elem. Object: Cell Unit: Remarks: Erlang None
Used param.: SDCCHTrafOff(10.1.1(a)), SDCCHTrafCarr(10.1.2(a)) Elem. Object: Cell Unit: Remarks: Erlang None
69
Information System
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.
Formula:
70
Information System
Elem. Object: Cell Unit: Remarks: Seconds None
Formula:
MBUSYSDC[1] NDESDCCH[2]
MBUSYSDC[1 ] A
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
71
Information System
(b) RSU_UL [i] =
where i = 1, , 6 denotes the codec type and i = 7 denotes SIGNALING (SDCCH and TCH in signaling mode) for which R-SACCH has been enabled in the respective direction (DL / UL). Used param.: SACCHSUP[1,..,27] Elem. Object: Cell Unit: Remarks: None None
72
Information System
Formula:
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
73
Information System
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 BSS 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
74
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
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
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.
75
Information System
Formula:
CCCHLDPCH = CCCHLDPCH =
Number of accessed PCH frames downlink Number of all defined CCCH frames downlink NTDMPCH[5] NDEFCCCH[2]
Used param.: NTDMPCH[5], NDEFCCCH[2] Elem. Object: Cell Unit: Remarks: None None
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
76
Information System
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.
Formula:
CCCHLDUL = CCCHLDUL =
Number of received RACH frames uplink Number of all defined CCCH frames uplink NACSUCPR[4] + NINVRACH[1,2,3] NDEFCCCH[1]
Used param.: NACSUCPR[4], NINVRACH[1,2,3], NDEFCCCH[1] Elem. Object: Cell Unit: Remarks: None None
77
Information System
Formula:
Used param.: NTDMPCH[1..4] Elem. Object: Cell Unit: Remarks: None None
Formula:
NTDMAGCH[3..6] NTDMAGCH[1..6]
Used param.: NTDMAGCH [1,,6] Elem. Object: Cell Unit: Remarks: None None..
78
Information System
Formula:
InvRACHRat e =
Used param.: NINVRACH[1..3], NACSUCPR[4] 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:Counter'.
79
Information System
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 BSS 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:
80
Information System
0 1 2 3 4 5 6 7 8 9 10 11
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
9 10 11
Fig. 12 Structure for an exemplary packet common control channel combination The number of all defined PCCCH channels is dependent on the channel configuration defined by the parameter GDCH (GPRSDedicatedChannel). It can have the values PCCCH and PBCCH. If PCCCH is selected, then 12 blocks are available for PCCCH (see above figure). A block consists of 4 consecutive TDMA frames. If PBCCH is selected, then additionally the parameter BSPBBLK (number of blocks allocated for PBCCH) is relevant, because it reduces the number of available PCCCH blocks by the number of blocks reserved for PBCCH (see above figure). In downlink direction all defined PCCCH blocks can be used as PAGCH, PPCH, PNCH, PDTCH, PACCH. But with the parameter BPAGCHR (number of blocks reserved for PAGCH, PDTCH, PACCH) some blocks can be inhibited for paging. In uplink direction all defined PCCCH blocks can be used as PRACH, PDTCH, PACCH. But with the parameter BPRACHR (number of blocks reserved for the PRACH channel) the number of blocks being used for PRACH can be restricted.
Note:
The following channels are not considered: PNCH, since the Packet Notification message is currently not supported by the call processing SW. PDTCH, PACCH, since these channels are mapped onto PCCCH channels (uplink/downlink) only, if there is spare capacity, i.e. in case of PCCCH channels being not fully loaded with common control channels. Therefore, for dimensioning of the required capacity of PCCCH channels, only the load of the PAGCH and PPCH (downlink) and PRACH (uplink) is important.
81
Information System
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
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
82
Information System
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
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.
83
Information System
Formula:
Used param.: NTDMPPCH[1..4] Elem. Object: Cell Unit: Remarks: None None
Formula:
Used param.: NTDMPAGC[1..2] Elem. Object: Cell Unit: Remarks: None None
84
Information System
Formula:
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:Counter'.
85
Information System
Used param.: CHALNHLY[21..30] Elem. Object: BTS Unit Remarks: None None
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.
Formula:
CHALNHLY[2 1] ServReques ts
86
Information System
(b) SDCADistCS=
CHALNHLY[2 9] ServRequests
CHALNHLY[3 0] ServReques ts
Used param.: CHALNHLY[21..30], ServRequests(13.1(a)) Elem. Object: BTS Unit Remarks: None None
Used param.: CHALNHLY[1..20], ServRequests(13.1(a)) Elem. Object: BTS Unit Remarks: None Service requests not supported and not served in the highest layer are subtracted.
87
Information System
Short name:
Description: Formula:
AbisPAvail Ch = ABISPSUP[2 ]
ABISPSUP[2] ABISPSUP[1]
88
Information System
ABISPSUP[7] ABISPSUP[6]
(k) AbisPBlockRate = ABISPSUP[5] (l) AbisPTrafUtil = ABISPSUP[3] ABISPSUP[1] (m) AbisPTrafU tilPeak =
Granularity * 60s
ABISPSUP[4 ] ABISPSUP[1 ]
Used param.: ABISPSUP[1..7], Granularity in minutes Elem. Object: Cell Unit: Remarks: None None
ABISPDIS[i + 1] * i
i =1
ABISPDIS[i + 1] * i
i =1
ABISPDIS[1 ] +
ABISPDIS[i + 1] * i
i =1
Used param.: AbisPTrCar(14.1(h)), ABISPDIS[all] Elem. Object: Cell Unit Remarks: None None
89
Information System
Short name:
Description:
Formula:
Short name:
Description:
90
Information System
Formula:
Used param.: IFRMABIS [all], IFRMABSC[1] Elem. Object: BTSM Unit Remarks: None Only I-Frames with SAPI = 0 (radio signalling link) and SAPI = 62 (O&M connection) are considered.
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.
91
Information System
with n for the number of GSM neighbourcell relation (n=0..31) with m for the number of UMTS neighbourcell relation (n=0..63) i represents the adjacent relationship between the observed and i-th neighbour GSM cell j represents the adjacent relationship between the observed and j-th neighbour UMTS cell Used param.: SINTHINT[1..12], SUINBHDO[1..11], SUOISHDO[1..11], ATINHIRC[1..12], ATINBHDO[1..11], ATOISHDO[1..11] Elem. Object: Cell Unit: Remarks: None Intra Cell Handovers are not considered. For Total Handover Success Rate please refer to chapter 15.6.8.
92
Information System
Used param.: SINTHINT[1..12], SUINBHDO[1..11], ATINHIRC[1..12], ATINBHDO[1..11], Elem. Object: Cell Unit: Remarks: None None
SUOISHDO[ 1..11]
j =0 m
ATOISHDO[1..11]
j= 0
with m for the number of UMTS neighbourcell relation (n=0..63) j represents the adjacent relationship between the observed and j-th neighbour UMTS cell Used param.: SUOISHDO[1..11], ATOISHDO[1..11] Elem. Object: Cell Unit: Remarks: None None
Short name:
Description:
These indicators will give you the number and rate of successful Intra Cell
93
Information System
Formula:
IntraCellHOSucc IntraCellHOAtt
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 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 c=15 Handover from TCH/WFS to TCH/NHS (compression handover; switch to NB if TFO not possible) c=16 Handover from TCH/NHS to TCH/WFS (decompression handover) c=17 Handover from TCH/WFS to TCH/AFS (robustness handover; switch to NB if TFO not possible) c=18 Handover from TCH/AFS to TCH/WFS (homing handover)
Used param.: SINTHITA[1..18], ATINHIAC[1..18] Elem. Object: Cell Unit: Remarks: None SDCCH handovers are also incremented in this formulas.
Short name:
94
Information System
Description:
Formula: (a)
(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 c=15 Handover from TCH/WFS to TCH/NHS (compression handover; switch to NB if TFO not possible) c=16 Handover from TCH/NHS to TCH/WFS (decompression handover) c=17 Handover from TCH/WFS to TCH/AFS (robustness handover; switch to NB if TFO not possible) c=18 Handover from TCH/AFS to TCH/WFS (homing handover) Used param.: UNINHOIA[1..18], , ATINHIAC[1..18], IntraCellHOAtt (15.2.1(a)) Elem. Object: Cell Unit: Remarks: None SDCCH handovers are also incremented in this formula.
Short name:
95
Information System
(c) IntraCellHODropRateC Description:
These indicators will give you the number and rate of Intra Cell Handover Drops by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value (a) IntraCellHODrop = UNIHIALC[1] (b) IntraCellHODropRate =
IntraCellHODrop IntraCellHOAtt
ATINHIAC[c] - SINTHITA[c] - UNINHOIA[c] ATINHIAC[c]
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 c=15 Handover from TCH/WFS to TCH/NHS (compression handover; switch to NB if TFO not possible) c=16 Handover from TCH/NHS to TCH/WFS (decompression handover) c=17 Handover from TCH/WFS to TCH/AFS (robustness handover; switch to NB if TFO not possible) c=18 Handover from TCH/AFS to TCH/WFS (homing handover) Used param.: UNIHIALC[1], ATINHIAC[1..18], SINTHITA[1..18], UNINHOIA[1..18], IntraCellHOAtt (15.2.1(a)) 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.
96
Information System
Used param.: ATINHIAC[1..18], IntraCellHOAtt (15.2.1(a)) Elem. Object: Cell Unit: Remarks: None SDCCH handovers are also incremented in this formulas.
97
Information System
Short name:
Description: Formula:
IntraCellSDHOSucc IntraCellSDHOAtt
Formula:
IntraCellSDHOFail IntraCellSDHOAtt
Used param.: UISHINTR[1], IntraCellSDHOAtt (15.2.5(a)) Elem. Object: Cell Unit: Remarks: None None
98
Information System
Formula:
IntraCellSDHODrop IntraCellSDHOAtt
Used param.: UISHIALC[1], IntraCellHOAtt (15.2.5(a)) Elem. Object: Cell Unit: Remarks: None None
99
Information System
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)
12
(b)
12
(c)
InterCellH OSuccRate[ i] =
(d)
InterCellHOSuccRateC[i, c] =
SOUINRH[j + c]
j j
AOUINIRH[j+ c]
with i for the number of the neighbourcell relation (i=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 AOUINIRH[1..12], SOUINRH[1..12] are defined for complete-complete
100
Information System
means the sum over the following coefficients j: complete-complete area complete-inner area inner-complete area inner-inner area
AOUINIRH[j + c]
j c =1
12
is equivalent to
12
+ AOUINIRH[36 + c]i
c =1
12
Used param.: AOUINIRH[1..48], SOUINIRH[1..48] Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
101
Information System
Short name:
Description:
(b)
InterCellHOFailRate[i] =
InterCellHOFail[i] InterCellHOAtt[i]
UNINHOIE [c] AOUINIRH[c] i
(c) InterCellHOFailRateC[i, c] =
with i for the number of the neighbourcell relation (i=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 Used param.: UNINHOIE[1..12], AOUINIRH[1..12], InterCellHOAtt[all] (15.3.1(a)) Elem. Object: Neighbourcell Unit: Remarks: None SDCCH handovers are also incremented in these formulas.
102
Information System
Short name:
Description:
(b)
InterCellH ODropRate[ i] =
(c)
InterCellHODropRateC[i, c] =
with i for the number of the neighbourcell relation (i=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 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.
103
Information System
Formula: (a)
InterCellHODist[i, c] =
AOUINIRH[ j + c]
j
InterCellHOAtt[i]
InterCellH OAtt[i]
with i for the number of the neighbourcell relation (i=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 and
means the sum over the following coefficients j: complete-complete area complete-inner area inner-complete area inner-inner area
AOUINIRH[j + c]
j
is equivalent to
104
Information System
Elem. Object: Neighbourcell Unit: Remarks: None
InterCellIncHOSuccRa te[i] =
SININIRH[j + c]
j c =1 k j c =1
AININIRH[ j + c]
with i for the number of the neighbourcell relation (i=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 and
means the sum over the following coefficients j: complete-complete area complete-inner area inner-complete area inner-inner area
SININIRH[j + c]
j c =1
is equivalent to
+ SININIRH[36 + c]i
c =1
105
Information System
Used param.: Elem. Object: Unit: Remarks: 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.
Short name:
Description: Formula:
InterCellSDHOSucc InterCellSDHOAtt
106
Information System
Formula:
InterCellSDHOFail= UISHINTE[ 1]
InterCellSDHOFailRate = InterCellSDHOFail InterCellSDHOAtt
Used param.: UISHINTE[1], InterCellSDHOAtt (15.3.6(a)) Elem. Object: Cell Unit: Remarks: None None
Used param.: UISHIRLC[1], InterCellSDHOAtt (15.3.6(a)) Elem. Object: Cell Unit: Remarks: None None
107
Information System
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)
11
(b)
InterBSCHOSucc[i] =
SUINBHDO [c]i
c =1
11
(c)
InterBSCHOSuccRate[i ] =
InterBSCHOSucc[i] InterBSCHOAtt[i]
(d)
InterBSCHOSuccRateC[i, c] =
SUINBHDO[c]i ATINBHDO[c]i
with i for the number of the neighbourcell relation (i=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.
108
Information System
Short name:
Description:
11
(b)
InterBSCHOFailRate[i] =
InterBSCHOFail[i] InterBSCHOAtt[i]
(c)
InterBSCHOFailRateC[i, c] =
NRUNINHD[c]i ATINBHDO[c]i
with i for the number of the neighbourcell relation (i=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.
109
Information System
Short name:
Description:
Formula:
InterBSCHODropRate[i] =
InterBSCHODrop[i] InterBSCHOAtt[i]
(ATINBHDO - SUINBHDO - NRUNINHD)[c] i ATINBHDO[c] i with i for the number of the neighbourcell relation (i=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
(c) InterBSCHODropRateC[i, c] =
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.
110
Information System
Formula:
InterBSCHODist[i, c] =
ATINBHDO[c]i InterBSCHOAtt[i]
ATINBHDO[c]
c =1
+ ATINBHDO[ 9]i
InterBSCHOAtt[i]
with i for the number of the neighbourcell relation (i=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.
111
Information System
Short name:
Description: Formula:
InterBSCSDHOSucc InterBSCSDHOAtt
Formula:
Used param.: UOINTESH[1], InterBSCSDHOAtt (15.4.5(a)) Elem. Object: Cell Unit: Remarks: None None
112
Information System
Formula:
InterBSCDHODrop = UMCSHLC[1]
InterBSCSDHODropRate = InterBSCSDHODrop InterBSCSDHOAtt
Used param.: UMCSHLC[1], InterBSCSDHOAtt (15.4.5(a)) Elem. Object: Cell Unit: Remarks: None None
113
Information System
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:
(c)
(d)
with i for the number of the neighbourcell relation (i=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
114
Information System
Short name:
Description:
11
c =1
(b)
InterSysOtgHOFailRate[i] =
InterSysOtgHOFail[i] InterSysOtgHOAtt[i]
UNOISHDO[ c]i ATOISHDO[c]i
(c)
InterSysOtgHOFailRateC[i, c] =
with i for the number of the neighbourcell relation (i=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
115
Information System
Short name:
Description:
(b)
InterSysOtgHODropRate =
InterSysOtgHODrop InterSysOtgHOAtt
(ATOISHDO - SUOISHDO - UNOISHDO)[c] i ATOISHDO[c]
(c) InterSysOtgHODropRateC[nic] =
with i for the number of the neighbourcell relation (i=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
116
Information System
Formula:
InterSysOtgHODist[i, c] =
ATOISHDO[c]i InterSysOtgHOAtt[i]
(b)
ImpInterSysOtgHORate[i] =
ATOISHDO[c]
c =1
InterSysOtgHOAtt[i]
with i for the number of the neighbourcell relation (i=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
117
Information System
Short name:
Description: Formula:
InterSysIncHOAtt = RQIISHDO[1]
InterSysIncHOSuccRate = InterSysIncHOSucc InterSysIncHOAtt
RQIISHDO[1]: Number of requested incoming intersystem handovers SUIISHDO[1]: Number of successful incoming intersystem handovers BSC None
118
Information System
Formula:
SUOISHDO[1..11]
j= 0
MEBUSTCH [1..10]
60 Granularit y
with n for the number of GSM neighbourcell relation (n=0..31) with m for the number of UMTS neighbourcell relation (n=0..63) i represents the adjacent relationship between the observed and i-th neighbour GSM cell j represents the adjacent relationship between the observed and j-th neighbour UMTS cell MEBUSTCH[1,2] are defined for standard cell, MEBUSTCH[3..6] are defined for the concentric cell and MEBUSTCH[7..10] are defined for the extended cell Used param.: SINTHITA[1..18], SINTHINT [1..12], SUINBHDO[1..11], SUOISHDO[1..11], MEBUSTCH[1..10],, 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
119
Information System
Formula: (a) HOperCallRatio =
TASSSUCC[2 ..5]
with n for the number of GSM neighbourcell relation (n=0..31) with m for the number of UMTS neighbourcell relation (n=0..63) i represents the adjacent relationship between the observed and i-th neighbour GSM cell j represents the adjacent relationship between the observed and j-th neighbour UMTS cell 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
(a) HOAttErlh =
+ ATOISHDO[1 ..11] j
j= 0
MEBUSTCH [ 1..10 ]
60 Granularit y
with n for the number of GSM neighbourcell relation (n=0..31) with m for the number of UMTS neighbourcell relation (n=0..63) i represents the adjacent relationship between the observed and i-th neighbour GSM cell j represents the adjacent relationship between the observed and j-th neighbour UMTS cell MEBUSTCH[1,2] are defined for standard cell, MEBUSTCH[3..6] are defined for the concentric cell and MEBUSTCH[7..10] are defined for the extended cell. Used param.: ATINHIRC[1..12], ATINBHDO[1..11], ATOISHDO[1..11], MEBUSTCH[1..10], Granularity in minutes Elem. Object: Cell Unit: Remarks: None None
120
Information System
Formula:
SUINBHDO[7 ]k + SOUINIRH [j + 7 ]k
SUOISHDO[7]i
(b) NoSuccDirectedRetryUMTS[i] =
with i for the ith number of GSM neighbourcell relation (i=0..31) with k for the kth number of UMTS neighbourcell relation (k=0..63)
and
means the sum over the following coefficients j: complete-complete area complete-inner area inner-complete area inner-inner area
SOUINIRH[j + 7]
j
is equivalent to
SUINBHDO[7], SOUINIRH[7, 19, 31, 43], SUOISHDO[7] Neighbourcell None Intersystem HO to UMTS are considered
121
Information System
Formula: (a)
ImpOutgHORateGSM[i] =
with InterCellHOAttImp[i] =
+ ATINBHDO[ + 9]i j
ATOISHDO[c ]
(b) ImpOutgHORateUMTS[k]=
c =1
InterSysOt gHOAtt[k]
with i for the mth number of GSM neighbourcell relation (i=0..31) with k for the nth number of UMTS neighbourcell relation (k=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= 9/10 fast uplink with j for the type of cell area: j=0 complete-complete area j = 12 complete-inner area j = 24 inner-complete area j = 36 inner-inner area
122
Information System
5 c =1
(AOUINIRH[c] + AOUINIRH[10])
5 c =1 5
AOUINIRH[1..5,10] , ATINBHDO[1..5, 9], ATOISHDO[1..5],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
Short name:
Description: Formula:
(b)
(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(b)), IntraCellHOAtt(15.2.1(a)) Cell
Elem. Object:
123
Information System
Unit: Remarks: None
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
124
Information System
Formula:
HOIndRejRate =
NHOINRHA [ 1..4]
31 31 63
NHOINRHA [ 1..4] + IntraCellH OAtt + InterCellH OAtt + InterBSCHO Att + InterSysOt gHOAtt
i=0 i =0 k =0
with i for the mth number of GSM neighbourcell relation (i=0..31) with k for the nth number of UMTS neighbourcell relation (k=0..63)
Used param.: NHOINRHA [1..4], IntraCellHOAtt(15.2.1(a)), 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
125
Information System
Short name:
Description: Formula:
These indicators will give you Handover statistics related to (Intra Cell, Inter Cell, Inter BSC and Inter System) Handovers.
+ ATOISHDO[1..11] j
j =0
31
+ UNOISHDO[1..11] j
j =0
HODrops =
m
(d)
+ UNIHIALC[1] + UNIHIRLC[1]
(e) TotalHOSuc cRate = HOSucc
HOAtt
126
Information System
Used param.: ATINHIAC[1..18], SINTHITA[1..18], UNINHOIA[1..18], UNINHIALC[1], ATINHIRC[1..12], SINTHINT[1..12], UNINHOIE[1..12], UNIHIRLC[1], ATINBHDO[1..11], SUINBHDO[1..11], NRUNINHD[1..11], ATOISHDO[1..11], SUOISHDO[1..11], UNOISHDO[1..11] 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).
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
127
Information System
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
CFERRXQU [1..64]
128
Information System
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:
n (PWRUPDW [136 + i]) N = (d) RxQuNPercentileDL = n with n such that i=1 100 PWRUPDW [137..144]
129
Information System
Formula: (a)
PWContrDistrUL[n] =
PWContrDistrDL[n] =
(b)
with n = 0 , .. 63 for the power control level Used param.: Elem. Object: Unit: Remarks: PWRUPDW[all] Channel None None
130
Information System
Short name:
Description: Formula:
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 =
PWRUPDW [73..136] =
8
(c) MeanRxQuUL
PWRUPDW [65..72]
(d) MeanRxQuDL = Used param: Elem. Object: Unit: Remarks: PWRUPDW[all] Channel None None
PWRUPDW [137..144]
131
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
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.
132
Information System
Formula:
133
Information System
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.
134
Information System
CRXLVQUD [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.
135
Information System
CRXLVTAD [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.
136
Information System
Formula:
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.
137
Information System
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, adaptive multirate half rate speech and adaptive multirate full rate wideband speech TCHs. (a) TCHFSRate =
Formula:
MBTCHCHT [4] MBTCHCHT[1..7] MBTCHCHT [5] MBTCHCHT[1..7] MBTCHCHT [6] MBTCHCHT[1..7] MBTCHCHT [7] MBTCHCHT[1..7]
(f) TCHAHSRate =
(g) TCHAFSWBRate = Used param.: Elem. Object: Unit: Remarks: MBTCHCHT [1..7] Cell None None
138
Information System
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]
(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.
139
Information System
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) (AMR full rate wideband speech, 12.65 kbit/s, uplink) (AMR full rate wideband speech, 8.85 kbit/s, uplink) (AMR full rate wideband speech, 6.60 kbit/s, uplink) (AMR full rate wideband speech, 12.65 kbit/s, downlink) (AMR full rate wideband speech, 8.85 kbit/s, downlink) (AMR full rate wideband speech, 6.60 kbit/s, downlink)
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 27 for TCH/WFS 12.65 uplink 28 for TCH/WFS 8.85 uplink 29 for TCH/WFS 6.60 uplink 30 for TCH/WFS 12.65 downlink 31 for TCH/WFS 8.85 downlink 32 for TCH/WFS 6.60 downlink
AMRCHDIS must be divided by 100 in this formula, because the measured value is in percent and KPI`s shouldn`t be in percent.
140
Information System
Short name:
Description:
Formula: (a)
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.
AMRTFERUL =
n =1 29 13
n = 27
AMRFRMUL [n, n + 3] *
AMRFRMUL [n + 3]
(b) AMRTFERULC HT[n] = AMRFRMUL [n + 13] for n from 1 to 13 AMRFRMUL [n, n + 13]
AMRTFERULC HT[n] = AMRFRMUL [n + 3] for n from 27 to 29 AMRFRMUL [n, n + 3]
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 27 TCH/WFS 12.65 28 for TCH/WFS 8.85 29 for TCH/WFS 6.60
(c) AMRTFERDL = AMRFRMDL [2] AMRFRMDL [1,2] Used param.: Elem. Object: Unit: AMRFRMUL[1..32], AMRFRMDL[1..2], AMRCHDIS[1..13, 27..29] Cell None
141
Information System
Remarks:
AMRCHDIS is in units of percent and must therefore be divided by 100 to get the weighting factor per channel mode.
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)
MEBUTSLY [ n 3 + 1,n 3 + 1 + 36,n 3 + 1 + 72,n 3 + 1 + 108,n 3 + 1 + 144 ] + EFLNetwork = + 0.5 MEBUTSLY [ n 3 + 2 ,n 3 + 2 + 36 ,n 3 + 2 + 72,n 3 + 2 + 108,n 3 + 2 + 144 ] 100 8 moballoc
Formula:
(b)
MEBUTSLY [ n 3 + 1, n 3 + 1 + 36, n 3 + 1 + 72 , n 3 + 1 + 108, n 3 + 1 + 144 ] + + MEBUTSLY [ n 3 + 2 , n 3 + 2 + 36 , n 3 + 2 + 72 , n 3 + 2 + 108, n 3 + 2 + 144 ] EFLUser = 100 8 moballoc
(c)
EFLNetworkCell =
(d)
EFLUserCell =
8 moballoc
n
MEBUTSLY[1..36] are used for the standard cells, MEBUTSLY[37..108] are used
142
Information System
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 27 for TCH/WFS 12.65 28 for TCH/WFS 8.85 29 for TCH/WFS 6.60
NFRMDLARP[ 1,2]
143
Information System
Used param.: Elem. Object: Unit: Remarks:
144
Information System
FR =
HR =
NRDEFTCH[3,9,15,21,27] NRDEFTCH[3,6,9,12,15,18,21,24,27,30]
NRDEFTCH[6,12,18,24,30] NRDEFTCH[3,6,9,12,15,18,21,24,27,30]
(b)
NRDEFTCH[3,6] are defined for the standard cell, NRDEFTCH[9,12,15,18] are defined for the concentric cell, NRDEFTCH[21,24,27,30] are defined for the extended cell. Used param.: Elem. Object: Unit: Remarks: NRDEFTCH[3,6,9,12,15,18,21,24,27,30] 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.
145
Information System
Short name:
Description: Formula:
NAVTCH[3,6] and NRDEFTCH[3,6] are defined for stamdard cell, NAVTCH[9,12,15,18] and NRDEFTCH[9,12,15,18] are defined for concentric cell, NAVTCH[21,24,27,30] and NRDEFTCH[21,24,27,30] are defined for extended cell. Used param.: NAVTCH[3,6,9,12,15,18,21,24,27,30], NRDEFTCH[3,6,9,12,15,18,21,24,27,30] 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
146
Information System
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).
147
Information System
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],
148
Information System
Used param.: REJPDASS [7..9,19..21], SUCPDASA [all], SULACCEL[all] Elem. Object: Cell Unit: Remark: None
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..4]
(b) TBFEstSuccDL = SULACCEL[5..7] Used param.: SULACCEL[all]; Elem. Object: Cell Unit: Remark: None
SULACCEL[1..4] NUACATCL[1..3]
SULACCEL[5..7] NUACATCL[4..6]
149
Information System
Remark:
Short Name:
Description :
This indicator provides the TBF establishment failure rate per cause considering uplink and downlink directions. TBF loss rate (UL and DL combined) by meaning of the rate where new TBF request can not be handled
Formula:
REJPDASS[7..9]
NUACATCL[1..3]
REJPDASS[19..21]
NUACATCL[4..6]
SUCPDASA [1..4] - SULACCEL[1..4]
NUACATCL[1..3]
SUCPDASA [5..7] - SULACCEL[5..7]
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
150
Information System
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..4] (b) TBFEstSuccRedRateDL = UNSPDCSE[9..14] / SULACCEL[5..7]
Used param.: UNSPDCSE[1..6, 9..14], SULACCEL[all], Elem. Object: Cell Unit: Remark:
Formula:
151
Information System
34..36, 40..42, 46..48] Used param.: UNSTETBF[1..48] Elem. Object: Cell Unit: Remark: None
Dropped means that a TBF is terminated in an abnormal way. But a TBF drop does not necessarily indicate system misbehavior. E.g. UNSTETBF[1] (T3169 expiry) is not only counted when the MS is lost but is also counted in case of MS based cell reselection during uplink TBF and in case of circuit switched call setup during uplink TBF (and additionally in some other cases). Counter NRRFPDU [1..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.
Short Name:
Description : Formula:
This indicator provides the distribution of TBF drops per cause considering uplink and downlink directions.
UNSTETBF[1 ..3] TBFDrAllCa useUL UNSTETBF[4 ..6] (b) TBFDrShare TimerExpDL = TBFDrAllCa useDL UNSTETBF[7 ..9] (c) TBFDrShare Preemption UL = TBFDrAllCa useUL UNSTETBF[1 0..12] (d) TBFDrShare Preemption DL = TBFDrAllCa useDL
152
Information System
Used param.: UNSTETBF[1..12,25..30], TBFDrAllCauseUL (18.1.8(a)), TBFDrAllCauseDL (18.1.8(b))) Elem. Object: Cell Unit: Remark: None
18.1.10
Long Name: Short Name: Description : Formula:
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:
153
Information System
(b) TBFDrFrequDL Description : Formula: (a) TBFDrFrequUL =
This indicator provides the TBF drop frequency as the mean number of TBF drops per hour TBF duration. Uplink and downlink directions are considered.
60 gran
Used param.: (a) NACTTBF[5-8, 13-16]; 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.
TBFDrFrequUL = TBFDrAllCauseUL *
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
Long Name: Short Name: Description :
154
Information System
Formula: (a) TBFDrMeanTimeUL = (b) TBFDrMeanTimeDL =
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:
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 =
Formula:
155
Information System
(b) UserDataThrTBFAvDL = (c) UserDataThrTBFCSUL[c] =
(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
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
156
Information System
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.1.14
Long Name:
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]
18.1.15
Long Name:
157
Information System
Description : This indicator provides the mean number of unsuccessful packet resource reassignment procedures per cell separated for uplink and downlink TBFs. 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:
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 =
(b)
Used param.: NATPRRE[all], NSUPRRE[all] Elem. Object: Cell Unit: Remark: none
18.1.17
Long Name:
158
Information System
(b) ReasFailRateTBFUL (c) ReasFailRateTBFDL
Description : This indicator provides packet resource reassignment failure rate per cell, separated for uplink and downlink TBFs. Use case Formula: Network optimization (a) Re asFailRateTBF = 1
NSUPRRE[all] NATPRRE[all]
(b)
Re asFailRateTBFUL = 1 Re asFailRateTBFDL = 1
(c)
Used param.: NATPRRE[all], NSUPRRE[all] Elem. Object: Cell Unit: Remark: none
18.1.18
Long Name:
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] *
SERVUGDG [2] *
(b) TBFDowngrFrequUL =
SERVUGDG [3] *
(c) TBFUpgrFrequDL =
60 gran NALLPDCH[6]
159
Information System
(d) TBFDowngrFrequDL =
Used param.: SERVUGDG [1 .. 4], NALLPDCH[3,6] Elem. Object: Cell Unit: Remark: Occurrences per hour = (1 / hour)
18.1.19
Long Name:
Short Name:
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 =
160
Information System
(e) MeanTBFDurDL =
(f) MeanTBFDurDLInt =
(g) MeanTBFDurDLStream = (h) MeanTBFDurDLBg = Used param.: NACTTBF[all] Elem. Object: Cell Unit: Remark: Seconds
18.1.20
Long Name:
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 =
60 gran 60 gran
LADAPTUD [2,4,5] *
(b) LinkAdaptFrequDownwUL =
LADAPTUD [6,8] *
(c) LinkAdaptFrequUpwDL =
(d) LinkAdaptFrequDownwDL =
NALLPDCH[6]
161
Information System
Elem. Object: Cell Unit: Remark:
18.1.21
Long Name:
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]
18.1.22
Long Name:
162
Information System
Short Name: (a) (b) (c) (d) (e) (f) LLCIntFrDiscRateUL LLCStFrDiscRateUL LLCBgFrDiscRateUL LLCIntFrDiscRateDL LLCStFrDiscRateDL 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) LLCBgFrDis cRateDL =
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 ]
Used param.: DISCLPDU[all], NTRLLCFR[all] Elem. Object: Cell Unit: Remark: None
18.1.23
Long Name: Short Name: Description : Formula:
SUDTMREQ [1 + 2] ATDTMREQ[1 .. 4]
Used param.: SUDTMREQ[all]; ATDTMREQ[all] Elem. Object: Cell Unit: Remark: None
163
Information System
18.1.24
Long Name: Short Name: Description : Formula:
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:
Short Name:
Description : Formula:
This indicator provides the Weighted LLC User Data Throughput UL/DL per technique.
(a) WGprsLLCUsrThUL =
MUTLLC[i + 60]
i =1
(b) WEdgeLLCUsrThUL =
MUTLLC[i + 65]
i =1
(c) WGprsLLCUsrThDL =
MUTLLC[i + 70]
i =1
164
Information System
5
(d) WEdgeLLCUsrThDL =
MUTLLC[i + 75]
i =1
Used param.: MUTLLC [1..20, 61..80] Elem. Object: Cell Unit: Remark: Kbyte / sec Weighted LLC User Data Throughput is the throughput per user during Continuous Data Transmission
165
Information System
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).
166
Information System
18.2.3 Uplink / Downlink distribution of user throughput on radio interface per cell
Long Name: Short Name: Description : Formula: (d) Uplink share of user throughput on radio interface (e) 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.
Used param.: UserThrUmCellUL (18.2.2 (a)) UserThrUmCellDL (18.2.2 (c)) Elem. Object: Cell Unit: Remark: None None
Short Name:
Description :
Used param.: TotThrUmCellUL(18.2.1), TotThrUmCellDL (18.2.1), granularity period gran in minutes Elem. Object: Cell Unit: Remark: kbit
167
Information System
Used param.: MUTHBS[all]; MSTHBS[1,2]; Elem. Object: Cell Unit: Remark: kbit/sec None
168
Information System
Unit: Remark: kbit/sec None
Used param.: NALLPDCH [3,6] Elem. Object: Cell Unit: Remark: None None
169
Information System
Use case Formula: (a) Network planning
MeanBusyPdchUtilCellUL = (NTRAPDU[1..11] + NRETPDU [1 ..11]) + (NTRAPDU[11.13] + NRETPDU [11.13]) MSTHRF[1] 2*( + ) gran * 60 20 NALLPDCH [3]
(b)
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)
Short Name:
170
Information System
Description :
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:
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(f)),
171
Information System
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. 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
172
Information System
18.2.10
Long Name: Short Name: Description : Use case Formula:
Used param.: NACTTBF[5..8, 13..16]; Elem. Object: Cell Unit: Remark: None None
18.2.11
Long Name: Short Name: Description : Use case
Formula:
Used param.: NTBFPDC[2,4]; Elem. Object: Cell Unit: Remark: None None
18.2.12
Long Name:
173
Information System
Short Name: Description : Use case Formula: (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 = (b) MeanAllocPdchTbfDL =
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
174
Information System
MeanAllocPdchTbfDL =
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 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
Long Name: Short Name: Description :
Formula:
175
Information System
c=9 c=10 c=11 c=12 c=13 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
Please note that RLC/MAC signaling is included in this indicator. Also retransmissions are considered. 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:
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.
13
(b) MeanPDCHBitRateGprsUL =
PDCHBitRateULCS[c] * CSDistrCellUL[c]
c =1
176
Information System
PDCHBitRateULCS[c] * CSDistrCellUL[c]
c =5
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
18.2.15
Long Name:
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.
MUTLLC[i + 60]
i =1
(b) PercentEdgeTSLAchievedUL =
MUTLLC[i + 65]
i =1
177
Information System
(c) PercentGprsTSLAchievedDL =
MUTLLC[i + 70]
i =1
(d) PercentEdgeTSLAchievedDL =
MUTLLC[i + 75]
i =1
18.2.16
Long name: Short name: Description: Formula:
Used param.: MFRLDATA [all] Elem. Object: NSVC Unit: Remarks: kbit/s None
178
Information System
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
179
Information System
Remark:
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]
= 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
180
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
181
Information System
Remark:
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
182
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 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).
Used param.: ATCRORIG [1] Elem. Object: Cell Unit: Remarks: None None
183
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 MS in GMM standby state (f) Number of network controlled Intra BSC cell reselection failures per cell due to Forced to the standby state (a) (b) (c) (d) (e) (f) NumNCIntrBSCCellResFailFrequNotImpl NumNCIntrBSCCellResFailFrequNoRespTarget NumNCIntrBSCCellResFailAccessRejTarget NumNCIntrBSCCellResFailCSOngoing NumNCIntrBSCCellResFailGMMStandby NumNCIntrBSCCellResFailForcedStandby
Short name:
Description: Formula:
These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per cell per cause (a) NumNCIntrBSCCellResFailFrequNotImpl = UNCRORIG [1] (b) NumNCIntrBSCCellResFailFrequNoRespTarget = UNCRORIG [2] (c) NumNCIntrBSCCellResFailAccessRejTarget = UNCRORIG [3]
184
Information System
Used param.: UNCRORIG [1..6] Elem. Object: Cell Unit: Remarks: None None
Used param.: SUCRORIG[1], ATCRORIG [1] Elem. Object: Cell Unit: Remarks: None None
Short name:
185
Information System
Description: Formula:
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]
UNCRORIG[4] ATCRORIG[1]
UNCRORIG[5] ATCRORIG[1]
(e) NCIntrBSCResFailRateGMMStandby = (f) NCIntrBSCResFailRateForcedStandby = Used param.: UNCRORIG[1..6], ATCRORIG [1] Elem. Object: Cell Unit: Remarks: None None
UNCRORIG[6] ATCRORIG[1]
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.
186
Information System
Used param.: ATOPSHONC[all], SUOPSHONC [all] Elem. Object: Cell Unit: Remarks: None None.
SUOIPSHONC[all ] ATOIPSHONC[all]
Used param.: ATOIPSHONC[all], SUOIPSHONC [all] Elem. Object: Cell Unit: Remarks: None None.
SUIPSHOC[all ] ATIPSHOC[all]
187
Information System
Elem. Object: Cell Unit: Remarks: None None.
Short name:
Description:
Formula:
MPCCLoad =
(c) PPXULoad(x) =
BSCPRCLD[8 + x * 3] 100
Used param.: BSCPRCLD[2, 5, 8, 11, 14, 17, 20, 23, 26, 29, 32, 35, 38, 41] Elem. Object: BSC Unit: Remarks: None None
188
Information System
Short name:
Description:
These indicators provide the processor load at the Basic eBSC for the MCP (Administrative Processor), APM(Telephony Processor), SMAC (Ethernet Interface Processor), LIET(Interface Processor) (up to 9) and for the U-plane Module (UPM) (up to 10) (a)
Formula:
MCPLoad =
APMLoad =
BSCPRCLD[4 3] 100
(b)
BSCPRCLD[4 5] 100
BSCPRCLD[47 + j * 2] 100
(c) APDLoad(j) =
(d) SMACLoad(x) =
BSCPRCLD[61 + x * 2] 100
(e) LIETLoad(y) =
BSCPRCLD[65 + y * 2] 100
(f) UPMLoad(z) =
BSCPRCLD[8 + z * 3] 100
(g) SDHLoad(i) =
Used param.: BSCPRCLD Elem. Object: Basic eBSC Unit: Remarks: None None
189
Information System
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), SMAC (Ethernet Interface Processor) (up to 4), LIET(Interface Processor) (up to 9) U-plane Module (UPM) (up to 11) SDH (STM1 Interface Processor) (up to 4) ETH (Ethernet Processor) (up to 4) (a)
Formula:
(c) APDLoadHE(j) =
(d) SMACLoadHE(x) =
BSCPRCLD[6 5 + y * 2] 100
(f) UPMLoadHE(z) =
BSCPRCLD[8 + z * 3] 100
190
Information System
(g) SDHLoadHE(i) =
k = SDH number (Range=0..3) Used param.: BSCPRCLD Elem. Object: HighEnd eBSC Unit: Remarks: None None
191
Information System
(a) Used param.: BTSEPRLD[1] Elem. Object: BTSM Unit: Remarks: None None
BTSEPRLD =
BTSEPRLD[1 ] 100
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
192
Information System
BR9.0 Used param.: Elem. Object: Unit: Remarks: eBSC
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.
193
Information System
Short name:
Description: Formula:
NMSUTRAS[1] MSU _ Length 1Min Erl GRAN 8000byte / s 60 s NMSUREC[1] MSU _ Length 1Min Erl GRAN 8000byte / s 60s
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.
194
Information System
20 Appendix
20.1 List of BSS Performance Measurements
Short Name AALTCHTI ABCLOCRQ ABISPDIS ABISPSUP ABSCPTSM ACADMCDMA ACREJCDMA AININIRH AISHINTE AISHINTR AMRCHDIS AMRFRMDL AMRFRMUL AMRSIDUL AMRVAR AOINTESH AOUINIRH ARPAPDAS ARPSPDAS ASDCALTI ATCHSMBS ATCRORIG ATDTMREQ ATIMASCA ATINBHDO ATINHIAC ATINHIRC ATIPSHOC ATOISHDO ATSDCMBS ATTAGRRC ATTCHSEI ATTLOCRP ATTLOCRQ Long Name All available TCH allocated time Number of Abnormal Condition Location Requests per cause Abis Pool Distribution Abis Pool Supervision Number of Abnormal SCCP Termination by SMLC 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 Requested Incoming Intersystem PS Handovers per BSC Attempted Outgoing Intersystem Handover per neighbourcell per cause Attempted SDCCH seizure meeting an SDCCH blocked state Number of Attempted A-GPS/E-OTD RRLP Command Attempted TCH seizures (Fullrate/Halfrate) Number of Attempted Usage Location Requests per Positioning Method Number of Attempted Location Request
195
Information System
ATTTAPOS ATTUTREQ AVCESPW AVCPWBTS BSCPRCLD BTSEPRLD CFERRXQU CHALNHLY CNSPRCLD CRXLVQUD CRXLVQUU CRXLVTAD CRXLVTAU DISCLPDU DLKSERST DSLUNAV FACCHSUP HOFITABS IFRMABIS IFRMABSC ILUPLKIC JITBUFL JITBUFLEN LADAPTUD LAPDLOAD LAPDRTT LLCQULEV MAUSTCH MAXBUSDC MBTCHCHT MBTSPWR MBUSYSDC MBUSYSSP MDURTCRQ MDURTCSD MEBUSTCH MEBUTSLY MEITCHIB MFRLDATA MMADFLLC MMRARTT MSCOVL MSCSRG MSTHBS MSTHRF MTCHBUTI MTCHQLEN MUTHBS
196
Information System
MUTHRF NACSUCPR NACTTBF NALIPDCH NALLPDCH NASSARP NASUSDPE NATPRRE NATTSDPE NAVPDCH NAVSDCCH NAVTCH NAVTCHSD NCRLBRQU NDEFCCCH NDEFPCCC NDEFPDCH NDESDCCH NDFTCHSD NFLTCHARP NFRMDLARP NFRMULARP NHOINRHA NINVRACH NMSGDISQ NMSUREC NMSUTRAS NNNOTNCH NPDTBOR NPDTCONF NPDTPCU NPKCESETHBTS NPKCESETHIF NPKCESPW NPKCESTNL NPKCPWBTS NPKCTNLBTS NRCLRCMD NRCLRREQ NRDEFTCH NRETPDU NRFLSDCC NRFLTCH
197
Information System
NRINHDFL NRRFPDU NRUNINHD
Number of inter BSC Handover failures Number of received FLUSH-PDU on Gb per cell 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 NTRAPDU Number of transmitted PDUs (uplink/downlink) per coding scheme per cell on the RF interface 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 NUPAGAGB Measurement of the pagings on the A Interface and on the Gb interface PWRUPDW Power and quality measurements on uplink/downlink busy TCHs REJPDASS Number of rejected PDCH assignments (uplink/downlink) per cause REMUTHRF Retransmitted mean user data throughput (uplink/downlink) per coding scheme per cell on the RF interface RESAGRRP Number of Reset A-GPS/E-OTD RRLP Procedure RESTAPOS Number of Reset TA/E-CITA Positioning RESUTPOS Number of Reset U-TDOA Positionings RNDTDELAY Min, Max and Mean Round Trip Delay per BTSM per ABIS CES tunnel RNDTDELAYASUB Min, Max and Mean Round Trip Delay per ASUB CES tunnel RNDTDELAYHSL Min, Max and Mean Round Trip Delay per HSL CES tunnel RNDTDELBTS Min, Max and Mean Round Trip Delay per BTSE per CES tunnel RQIISHDO Number of Requested Incoming Intersystem Handover per BSC RXQUARP Quality Measurements Related to MS with ARP on Downlink Busy TCHs SACCHSUP Repeated SACCH Supervision SERVUGDG Service upgrade/downgrade measurements (uplink/downlink) per cell SINHOBSC Successful internal Handovers per cause SININIRH Successful incoming internal intercell Handovers per originating cell SINTHINT Successful internal Handovers, intercell, per cause SINTHITA Successful internal Handovers, intracell, per cause SISHINTE Successful Internal SDCCH Handovers Intercell SISHINTR Successful internal SDCCH Handovers Intracell SLFAILAL Signaling link failure SOINTESH Successful MSC controlled SDCCH Handovers SOUINIRH Successful outgoing intercell Handovers per cause, per neighbour cell relationship
198
Information System
SUCAGRRS SUCLOCRS SUCPDASA SUCRORIG SUCTAPOS SUCTCHARP SUCTCHSE SUCTETBF SUCUTDRS SUDTMREQ SUIISHDO SUIMASCA SUINBHDO SUIPSHOC SULACCEL SUOISHDO TACCBPRO TANRGPRS TASSATT TASSATVS TASSFAIL TASSSUCC TASSUCVS TBFRASSR TNMSCNCL TNSUDHSC TNTCHCL TRANAVTI UATTLOCP UISHIALC UISHINTE UISHINTR UISHIRLC UMCSHLC UNCRORIG UNIHIALC UNIHIRLC UNIISHDO UNINHOIA UNINHOIE UNIPSHOC UNOISHDO
199
Information System
UNSAGRRS UNSAUPOS UNSDTMREQ UNSLOCRS UNSPDCSE UNSRGRRS UNSRUPOS UNSTAPOS UNSTETBF UOINTESH WPSSUPV WUTHBS
200